|
|
|
|
|
|
|
|
Application |
|
Development |
AUTO |
Unit Test |
AUTO |
Platform Tests |
AUTO |
Staging |
AUTO |
Acceptance |
AUTO |
|
|
|
|
|
|
|
|
Tests |
|
Deploy to Production
Continuous Development |
Continuous Integration |
Continuous Testing |
Continuous Deployment |
CloudOps |
Figure 2 : The DevOps process should span cloud and traditional platforms
ond , it further defines the DevOps process . Even though many say it shouldn ’ t change around the platform , it does change .
Needs for testing and deployment processes and automation change a lot between cloud platforms and even traditional platforms .
Selecting the right target cloud platform may mean selecting multiple platforms . Most DevOps processes I ’ m involved with use several public and private clouds . You may have OpenStack , AWS , Google , etc ., and the desired target for the DevOps process may shift based on the applications and corresponding requirements . Or , at some future date , you may do least-cost cloud brokering to determine the cheapest and most efficient cloud on the fly .
Step 6 : Select the Tools For Cloud and On-premise
DevOps tools aren ’ t easy to understand . They use the same terms , but the types of functionality they provide are often confusing and overlapping . To address this , list your platforms and requirements , including how you ’ re partitioning the DevOps processes between traditional platforms and the cloud .
Then compile a list of the categories of tools you ’ ll need . Look again at this list at a higher level , such as continuous development , integration , testing , deployment , etc ., and define the sub-patterns you ’ ll need . Sub-patterns might include automated testing that is appropriate for the type of code and data you ’ ll be employing . Finally , don ’ t forget about operational tools that will ensure things are running properly .
Step 7 : Define Security and Governance
Once again , these are systemic concepts . They ’ re part of every step in the process . So , how do you define security and governance within the development process ? How about testing and deployment ? Also , and most importantly , how do you define operations ?
This is the most neglected part of DevOps because it ’ s one more thing to think about in an already complex set of processes and tools . However , it ’ s important to figure out how to approach issues such as identity and access management ( IAM ) and how they fit into this process . What about data and service governance ? How will APIs and services be tracked for dependencies ? How do you select policies for data and service access ? You must address all these issues .
Step 8 : Test DevOps
This means exactly what it says : test the processes , tools , automation , skills , organization , and other components of DevOps by just doing DevOps . Flow a set of test applications through the process , and observe any fixes or improvements that need to be made .
You ’ re likely to find many hiccups , which makes it important to note these issues and work on fixes as
12 | THE DOPPLER | WINTER 2016