Utilizing CI/CD Pipelines for Infrastructure Configuration and Administration

Steady Integration/Steady Supply, or Steady Deployment, pipelines have been used within the software program improvement business for years. For many groups, the times of manually taking supply code and manifest information and compiling them to create binaries or executable information after which manually distributing and putting in these functions are lengthy gone. In an effort to automate the construct course of and distribution of software program in addition to carry out automated testing, the business has repeatedly advanced in the direction of extra complete pipelines. Relying on how a lot of the software program improvement course of is automated, pipelines will be categorized into totally different teams and levels:

•  Steady Integration is the observe of integrating code that’s being produced by builders. On medium to giant software program initiatives is frequent to have a number of builders and even a number of groups of builders work on totally different options or parts on the identical time. Taking all this code and bringing it to a central location or repository is repeatedly executed utilizing a git based mostly model management system. When the code is merged right into a department on an hourly, every day, weekly or regardless of the cadence of the event staff is, easy to advanced exams will be setup to validate the modifications and flush out potential bugs at a really early stage. When carried out in an automatic trend, all these steps consist in a steady integration pipeline.
• Steady Supply takes the pipeline to the following degree by including software program constructing and launch creation and supply. After the software program has been built-in and examined within the steady integration a part of the pipeline, steady supply provides further testing and has the choice to deploy the newly constructed software program packages in a sandbox or stage atmosphere for shut monitoring and extra person testing. Much like steady integration, all steps carried out within the steady supply a part of the pipeline are automated.
• Steady Deployment takes the pipeline to its subsequent and final degree. By this stage, the applying has been built-in, examined, constructed, examined some extra, deployed in a stage atmosphere and examined much more. The continual deployment stage takes care of deploying the applying within the manufacturing atmosphere. A number of totally different deployment methods can be found with totally different threat components, price issues and complexity. For instance, within the primary deployment mannequin, all utility nodes are up to date on the identical time to the brand new model. Whereas this deployment mannequin is easy additionally it is the riskiest, it isn’t outage-proof and doesn’t present simple rollbacks. The rolling deployment mannequin because the title suggests takes an incremental strategy to updating the applying nodes. A sure variety of nodes are up to date in batches. This mannequin offers simpler rollback, it’s much less dangerous than the fundamental deployment however on the identical time requires that the applying runs with each new and outdated code on the identical time. In functions that use the micro-services structure, this final requirement should be given further consideration. A number of different deployment fashions can be found, together with canary, blue/inexperienced, A/B, and so forth.

The CI/CD pipeline part of GitLab CE

Why use CI/CD pipelines for infrastructure administration

Based mostly on the necessities of the event staff, software program improvement pipelines can take totally different varieties and use totally different parts. Model management programs are normally git based mostly nowadays (github, gitlab, bitbucket, and so forth.). Construct and automation servers similar to Jenkins, drone.io, Travis CI, to call just some, are additionally fashionable parts of the pipeline. The number of choices and parts make the pipelines very customizable and scalable

CI/CD pipelines have been developed and used for years and I believe it’s lastly time to contemplate them for infrastructure configuration and administration. The identical benefits that made CI/CD pipelines indispensable from any software program improvement enterprise apply additionally to infrastructure administration. These benefits embody:

• automation on the forefront of all steps of the pipeline
• model management and historic perception into all of the modifications
• intensive testing of all configuration modifications
• validation of modifications in a sandbox or take a look at atmosphere previous to deployment to manufacturing
• simple roll-back to a recognized good state in case a problem or bug is launched
• risk of integration with change and ticketing programs for true infrastructure Steady Deployment

On this sequence of blogs, I’ll display how you can use Gitlab CE as a foundational part for a CI/CD pipeline that manages and configures a easy CML simulated community. A number of different parts are concerned as a part of the pipeline:

• pyATS for creating and taking snapshots of the state of the community each prior and after the modifications have been utilized
• Ansible for performing the configuration modifications
• Cisco CML to simulate a 4 node community that may act because the take a look at infrastructure

Easy community simulation in Cisco CML

Keep tuned for a deeper dive

Subsequent up on this weblog sequence we’ll dive deeper into Gitlab CE, and the CI/CD pipeline part. When you’ve got any questions or feedback, please depart me a remark within the part under.

Within the meantime, if you need to study and observe among the newest strategies, please go to our Cisco Modeling Labs and the CML Sandbox. A world of community simulation awaits!

---

We’d love to listen to what you suppose. Ask a query or depart a remark under.
And keep linked with Cisco DevNet on social!

LinkedIn | Twitter @CiscoDevNet | Fb | Developer Video Channel

Share: