Enrich Your DevOps Environment: Tools for Accelerating and Integrating Your Application Development with AWS and NetApp
1. Enrich Your DevOps Environment:
Tools for Accelerating and Integrating
Your Application Development with
AWS and NetApp
Jan. 31, 2017
AWS Pop-Up Loft – San Francisco
Shift your service delivery life cycle to include smaller and faster releases: The new modern service delivery life cycle consists of small and quick releases to achieve a continuous delivery cycle that enables organization to deliver business technology solutions quickly to their customers. As Jez Humble states: Continuous Delivery is about making deployments boring.
Your participation across the development life cycle is the key to business success: Operations professional previously only participated in the run portion of the life cycle. By inserting feedback loops into the entire life cycle of solutions development, operation professionals play a key role in the quality and speed of service delivery to the business.
Lead or be gone: Because business technology is critical to your organization’s success, you must adopt a faste4 cadence for modern service delivery. Take charge and contribute your key expertise to enable the business, or the business will find others to support it.
Conversation starter, exploratory slide.
Based on extensive interviews with Field Operations exec staff and field reps, we know most NetApp customers—and many partners--do not understand the breadth of our market presence and leadership. Even if it’s a customer or partner you think knows us well, please spend some time exploring the various data points on this slide.
This slide will be re-assessed and updated quarterly.
BUILD SLIDE NARRATIVE:
1. (First 5 clicks) Via Git, sync the source code from the repository to the new volume that has been created for Dev Branch1 as illustrated on the code branch to the right of the slide. Every Dev Branch referenced in the picture on the right will have it’s own volume. Depending upon the code base you can have any number of code branches.
- Sync all the dependencies, like Tools, Compilers, Libraries and RPM in the Dev Branch1 volume.
2. (2 clicks) Run a build on Dev Branch1.
3. (3 clicks) Upon successful completion of the build, create a SnapShot.
4. (2 clicks) This SnapShot is used by the developer to clone a pre-packaged workspace that includes the source code, the compiled objects and all the dependencies. The clone is then taken. The developer makes changes to the code in the workspace and submits the changes to Git Repository. The new change triggers another developer build and updated the Dev Branch1 volume with the changes.
5. (2 clicks) Depending upon the frequency of successful developer builds, the CI test are triggered as scheduled. This stage is typically automated.
6. (5 clicks) Upon completion of the CI test, a Docker image is created and moved to a different NetApp volume where each Docker image represents the changes that happened to the code repository.
7. (3 clicks) Repeat the process to update Dev Branch 1 volume. Dev Branch1.2 is created.
8. (4 clicks) Build is run again and workspace is cloned and tested.
9. (1 click) New Docker instance is created with code changes.
10. (2 clicks) Changes in workspace 1.2 are submitted to the code respository.
11. (1 click) All this work is done by the Jenkins Plug-in seamlessly to the user.
12. (2 clicks) The QA (or staging) can spin up the Docker image to run regression tests. If the QA test passes, the build is promoted to be deployed.
<END OF SLIDE>