Did you ever need to run Cisco Modeling Labs however didn’t have the {hardware} or software program to take action? Or have you ever wished to run a topology in your native deployment—however couldn’t since you didn’t have sufficient reminiscence out there regionally? What about integrating CML right into a CI/CD pipeline, which incorporates the creation and destruction of your complete pipeline, together with CML?
You may assume one reply to those issues could be to make use of CML within the cloud. And also you’d be proper. Nevertheless, up till just lately, the one supported platforms to run CML have been both on naked metallic servers or on VMware vSphere.
We’ve got heard requests to have CML Software program-as-a-Service (SaaS), and we’re working laborious to make this a actuality sooner or later. Our first step on this course is to supply tooling and automation so you possibly can deploy your CML occasion into Amazon Net Providers (AWS)! This tooling is on the market as of at this time on GitHub.
Setting expectations
With this primary step of automation and tooling comes a number of limitations, together with:
- Tooling is presently solely supported on AWS. We’re engaged on making this additionally out there on Azure in a subsequent launch.
- It solely helps an all-in-one deployment. Subsequent releases may embody deployment of a number of cases to type a CML cluster.
- This strategy wants a bare-metal taste to assist all node varieties. Steel flavors are costlier than virtualized cases; nonetheless, AWS doesn’t assist virtualization extensions on their non-bare-metal flavors. That is completely different from Azure.
- It’s worthwhile to convey your individual AWS occasion AND your individual CML license. No pay-as-you-go consumption mannequin is on the market as of at this time.
- CML software program and reference platform recordsdata from the “refplat ISO” should be made out there in a bucket.
- Automation should run regionally in your pc, notably a Linux machine with Terraform.
Because of the nature of CML’s perform, the power to run it within the cloud won’t ever be low-cost (as in free-tier). CML requires numerous assets, reminiscence, disk, and CPU, which comes at a price, no matter whether or not you run it regionally in your laptop computer, in your information heart, or within the cloud. The concept behind the cloud is to simplify operation and supply elasticity however not essentially to economize.
Assembly software program necessities
The software program necessities you’ll have to efficiently use the tooling embody:
- a Linux machine (must also work on a Mac with the identical packages put in through Homebrew)
- a Bash shell (in case you employ the add device, which is a Bash script)
- a Terraform set up
- the AWS CLI bundle (awscli with the aws command)
- the CML software program bundle (.pkg) and the CML reference platform ISO from CCO/cisco.com
An current CML controller satisfies the primary two necessities, and you should use that to put in Terraform and the AWS CLI. It additionally has the reference platform recordsdata out there to repeat to an AWS S3 bucket. You additionally should obtain the CML distribution bundle from the Cisco assist web site and duplicate it to the AWS S3 bucket.
For extra element, confer with the “Add script” part of the README.md that’s included within the cml-cloud repository.
Getting up and working
When you’ve put in the necessities and copied the recordsdata, you’ll discover the precise process straight ahead and meticulously documented within the README.md.
Listed here are the basic steps:
-
- Configure the required S3 bucket, person, insurance policies, secrets and techniques, and guidelines through AWS console (as soon as).
- Add the binary recordsdata (pictures and software program) into the created bucket (as soon as or each time new software program is on the market).
- Configure the tooling by modifying the config.json file (as soon as).
- Run terraform plan adopted by terraform apply to convey up an occasion
- Wait 5-10 minutes for the system to turn out to be prepared; the handle of the controller is supplied in consequence (“output” from Terraform)
- Use CML within the cloud and revenue!
When you’re accomplished, tear down the cloud infrastructure by executing terraform destroy.
Observe: Whereas no value is incurred when you find yourself not working CML cases, you’ll nonetheless have to pay for storing the recordsdata contained in the created S3 bucket.
Taking the following steps
Whereas CML AWS automation tooling is a primary step towards CML SaaS, the tooling in its present type won’t suit your wants precisely due to value for bare-metal cases or the present dependency on AWS. Or you may want a pay-as-you-go service or one thing else. Tell us!
Simply bear in mind subsequent steps are forward! Keep tuned, and inform us what you assume within the meantime. We’re extraordinarily excited about how helpful (or not) this primary iteration of cloud tooling is to you and your group and, going ahead, what your particular necessities are. Please attain out to us on the GitHub situation tracker undertaking.
Sources
Â
Be a part of the Cisco Studying Community at this time without spending a dime.
Comply with Cisco Studying & Certifications
Twitter | Fb | LinkedIn | Instagram | YouTube
Use #CiscoCert to hitch the dialog.
Share: