run Cisco Modeling Labs within the Cloud


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 entire pipeline, together with CML?

You may suppose one reply to those issues could be to make use of CML within the cloud. And also you’d be proper. Nevertheless, up till lately, the one supported platforms to run CML had been both on naked steel servers or on VMware vSphere.

Now we have heard requests to have CML Software program-as-a-Service (SaaS), and we’re working exhausting to make this a actuality sooner or later. Our first step on this route is to supply tooling and automation so you’ll be able to deploy your CML occasion into Amazon Internet Providers (AWS)! This tooling is on the market as of as we speak on GitHub.

Setting expectations

With this primary step of automation and tooling comes a number of limitations, together with:

  • Tooling is at present 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 might embody deployment of a number of situations to type a CML cluster.
  • This strategy wants a bare-metal taste to help all node varieties. Metallic flavors are costlier than virtualized situations; nonetheless, AWS doesn’t help virtualization extensions on their non-bare-metal flavors. That is completely different from Azure.
  • It is advisable to deliver your personal AWS occasion AND your personal CML license. No pay-as-you-go consumption mannequin is on the market as of as we speak.
  • 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, significantly a Linux machine with Terraform.

Because of the nature of CML’s operate, the power to run it within the cloud won’t ever be low-cost (as in free-tier). CML requires numerous sources, reminiscence, disk, and CPU, which comes at a price, no matter whether or not you run it regionally in your laptop computer, in your knowledge heart, or within the cloud. The thought 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 must efficiently use the tooling embody:

  • a Linux machine (also needs to work on a Mac with the identical packages put in through Homebrew)
  • a Bash shell (in case you employ the add software, 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 need to 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 help web site and duplicate it to the AWS S3 bucket.

Choose the distribution bundle circled within the following screenshot (the model is perhaps completely different, nevertheless it ends in .pkg.zip), and also you’ll must unzip it for the add software to acknowledge it

For extra element, check 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 elemental steps:

    1. Configure the required S3 bucket, consumer, insurance policies, secrets and techniques, and guidelines through AWS console (as soon as).
    2. Add the binary recordsdata (photos and software program) into the created bucket (as soon as or at any time when new software program is on the market).
    3. Configure the tooling by enhancing the config.json file (as soon as).
    4. Run terraform plan adopted by terraform apply to deliver up an occasion
    5. Wait 5-10 minutes for the system to develop into prepared; the handle of the controller is supplied consequently (“output” from Terraform)
    6. Use CML within the cloud and revenue!

When you’re carried out, tear down the cloud infrastructure by executing terraform destroy.

Word: Whereas no value is incurred when you’re not working CML situations, you’ll nonetheless must 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 may not suit your wants precisely due to value for bare-metal situations 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 suppose within the meantime. We’re extraordinarily thinking 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 difficulty tracker venture.

Assets

 

Be part of the Cisco Studying Community as we speak without spending a dime.

Comply with Cisco Studying & Certifications

Twitter | Fb | LinkedIn | Instagram | YouTube

Use #CiscoCert to affix the dialog.

Share:



Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles