diff --git a/resources/bc-dev-team-guide-to-success-on-the-platform/01-intro.md b/resources/bc-dev-team-guide-to-success-on-the-platform/01-intro.md new file mode 100644 index 0000000..9804f60 --- /dev/null +++ b/resources/bc-dev-team-guide-to-success-on-the-platform/01-intro.md @@ -0,0 +1,34 @@ +--- +description: We've seen and heard the community. One of the key things missing for teams developing on the platform is a clear and definitive journey. This guide aims to clarify that. +--- + +## The BC Developer Team Guide to Openshift + +Welcome all! You have found yourself here because you are: + +- a new team trying to figure out how to navigate their way through this landscape +- an individual interested in the BC Gov Openshift DevOps Journey +- an existing team member who hasn't had the chance to benefit from this journey yet + +This guide serves to outline many of the key components, tools, processes, and training that a team will +need to navigate their selves through to be successful in this new way of development. + +> This is a living document that exists on Github. If there are any issues with this document please [make an issue or pull request](https://developer.gov.bc.ca) + +## How To Navigate Through This Journey + +This journey's main focus is on the 'Developer' or 'Product Team' persona. Therefor, the main line +of this journey will focus on __Delivering and Maintaining an Application__. There will be several +side-stations along the line for helpful resources. + + +## Persona Specific Roles + +Some stops along this journey require a specific action to be done. These will be identified by a persona. + +For example, there will be discussion on an __'Alignment Meeting'__ shortly which will require whoever +is the __Product Owner__ to attend. + + + + diff --git a/resources/bc-dev-team-guide-to-success-on-the-platform/02-understanding-the-platform.md b/resources/bc-dev-team-guide-to-success-on-the-platform/02-understanding-the-platform.md new file mode 100644 index 0000000..c2084fc --- /dev/null +++ b/resources/bc-dev-team-guide-to-success-on-the-platform/02-understanding-the-platform.md @@ -0,0 +1,37 @@ +--- +description: Get Clarity on Working on the Openshift Platform. Learn about its cost structure and upgrade plans. +--- + +## Understanding The Platform + +The Platform is comprised of __Three Pillars__ that work together to allow Teams to deliver applications. + +1. __The People__: + - Platform Teams that Deliver their Business Applications through Openshift + - Platform Service and Developer Experience Teams that are continuously working to improve the platforms capabilities and support Platform Teams + - Partners that support the infrastructure of the platform as well as performing the OCP 4.2 upgrade + +2. __The Technology__: + - This is primarily about Openshift. A platform that allows teams to cloud-ready/cloud-native applications effectively and with speed. This platform is best suited to Agile teams. + +3. __The Process__: + - Government process, although needed, can be a hinderance to modern app development. + - Product Teams, as well as Platform Services and Partners are working to shape processes that work better for teams, developers to deliver __top notch__ applications to the Citizens of BC. + +## More Than Just Openshift + +As you can see there is a lot going on in order to support a __Hybrid Cloud Containerized Platform__ like Openshift. Working on this platform requires the __DevOps__ mindset. The idea that products should be continuously improved. The idea that people need to be brought together to solve common problems. The idea that the status-quo is not good enough and that there should be a drive to be innovative and creative. + + +## BC Gov Openshift Platform Myths + +1. It is a Hosting Platform + +No! It is not just a hosting platform. In other words, Openshift is not a place for a team to dump their application. It will not be maintained for the team by Platform Service members. Applications like plants, pets, and humans need care and feeding. The deployable unit of an application is ___not the application itself__ it is the ___the Team__. The team has the knowledge, the background, and the expertise to support the application for its lifetime. The expectation is that there will be __at least one__, if not two, members dedicated to supporting their applications for their lifetime. + +2. It is Free and therefor the obvious choice for my ministry + +Openshift and its support is maintained through the __OCIO's__ budget. There is not an __additional cost__ +placed forward to teams or their ministry at this time. That being said, the main driver for joining this platform should be along: "I have a business need and want to enable a team to deliver this need as quickly and as effectively as possible. In addition, the team will learn and or improve their skills with +modern cloud-based app development and operation." + diff --git a/resources/community/my-first-openshift-project.md b/resources/community/my-first-openshift-project.md new file mode 100644 index 0000000..febcbd2 --- /dev/null +++ b/resources/community/my-first-openshift-project.md @@ -0,0 +1,13 @@ +# My First Openshift Project + +You've had an alignment meeting and the Team has been procured. The next task is to have a set of +Openshift Projects (AKA Namespaces) provisioned. How does one get that started? How can one leveage +shared components principles when building out their applications. + +This guide aims to provide examples/and demonstrations of how to get an Openshift project provisioned +as well as how to set up a simple __Hello World__ application in Openshift with __Jenkins__ as a +continuous deployment tool. + + +- provisioning projects with rocket chat +- \ No newline at end of file