AWS CloudFormation vs. Cisco Intersight vs. IBM Terraform

I still give it an 8 because it's one of those tools that just quietly does the heavy lifting for you but it can really test your patience when it breaks esp with deep nested stacks. It's perfect for projects where we need clean consistent environments every time. It's less ideal for quick experimental setups like new EC2 configs or Lambda permission tweaks.

Incentivized

Cisco Intersight is very well suited for doing firmware upgrades across all of your cisco hardware. So far we have had no problems pushing out new firmware. It's also well suited for hardware management. Cisco TAC has the ability to pull logs for the IMC for themselves, which saves you from having to pull the logs yourself and then uploading them to the case. It may or may not be appropriate for upgrading operating systems. I have not been able to test it.

Incentivized

8 because it's currently best-in-class and is completely essential to use in contrast to not expressing your infrastructure as code. That said, new contenders are nipping at its heels, and I expect stronger tools to emerge in the coming years. Hopefully the Terraform team is able to keep pace.

Incentivized

• IaC, transactional on top of that
• Support for "mainstream" general programming languages
• Sharable IaC "snippets" that can setup standardized environments for individuals quickly
• OOP techniques are available thanks to OOP languages

Incentivized

• Standardising the environment by enforcing use of updating templates.
• Show the difference on a profile between what has changed and what setting was last deployed.
• Perform bulk deploy operation on profiles (like server profiles).
• Policies underpin all settings (e.g. no more defining individual VLANs before being able to use them, or having to clean them up manually when they are no longer in use. You deploy a Domain VLAN policy that states which VLANs are configured on a domain (either standalone) or a domain profile template (if domains profiles are bound to an updating domain profile template).

Incentivized

• Terraform is cloud agnostic. Just select the suitable provider for the cloud and it will do the job.
• Templating is possible to make the Terraform templates reusable.
• Variables can be created to make the templates generic so that it can be reused for different environments or resources.

Incentivized

• Error Description upon Failure Needs to be Improved.
• Slow to create, delete or update.
• Need to delete resources manually. It can ask before starting deletion whether to skip those resources or delete them.

Incentivized

• It would be great to not having to create EVERY profile within a deployment. since some items can be done be default, the defaults should be set and the deployment can be much faster.
• When adding Rack servers, indicating that the CIMC interface should not being connected before powering on the system and they it will be managed by Cisco Intersight can reduce down times. We had to manually reset our CIMC after disconnecting from our OOBM switches.

Incentivized

• The errors generated by the plan and preview commands are pretty cryptic, it can be hard for newcomers to the scripting language to understand how to address problems.
• Access controls around workspaces is limited which makes it harder to secure reduce the scope of teams ability.
• Analytics around user usage, applies and plans would be helpful for managemenet.

Incentivized

Been using Cisco Software as a service (SaaS) platform in a production environment for a large medical and health professionals that has critical healthcare and patients care dependency.

Support team is very helpful getting system updated as needed, and vendor support is fantastic. Also get a dedicated Cisco networking engine to review and advise system health and recommendations.

Incentivized

Still the best provisioning tool out there and good support from the community as well in terms of shared knowledge

Incentivized

You just have to learn how it thinks then you'll be set. That however comes with a learning curve. Writing YAML or jSON templates feels natural now but early on, even a small syntax mistake could break a whole stack.

Incentivized

Usability of Cisco Intersight is highly dependent on the licensing purchased. The default (free) license level provides a lot of value for the minimal amount of effort to implement. The paid license levels provide additional features (detailed inventory, configuration management and deployment, etc.)

Incentivized

The syntax itself is pretty straightforward. The documentation is well-maintained & easy to follow. Most cloud providers, even smaller ones, maintain official provider libraries, making discovery & learning a breeze. Some, like GCP, even provide high-level libraries on top of their own more primitive provider, making building complex infra much more manageable. The language itself is cloud-agnostic, so you can literally manage resources from multiple providers in a single Terraform repo.

So far over the past 4 years we have not experienced any issues with the servers being available.

Incentivized

Could need some more refinement. It takes some time getting used to where different settings are being defined.

Incentivized

Terraform's performance is quite amazing when it comes to deployment of resources in AWS. Of course, the deployment times depend on various parameters like the number of resources to deploy and different regions to deploy. Terraform cannot control that. The only minor drawback probably shows up when a terraform job is terminated mid way. Then in many cases, time-consuming manual cleanup is required.

Incentivized

Every time we need Cisco Intersight support it takes weeks until we get a solution. We have to change the tac 2 to 3 times every time because none of the engineers have any idea about Intersight. Cisco has not trained their engineers. one has the impression that they are often seeing Intersight for the first time.

Incentivized

Terraform is community driven but does offer support for it's Enterprise product. When contacting the team at HashiCorp we have always gotten resolution to our issues. They have been very responsive in returning our calls and answering our questions as they come up. We are currently using the open source model.

Incentivized

You really need a lab to get hands on but it was useful

Incentivized

Very smooth process and we did it for 2 data centers

Incentivized

Implementation is straight forward. Never had issues as the team is already very familiar with Terraform installation from previous projects and roles

Incentivized

Since the product I'm involved is primarily hosted on AWS we use CloudFormation but in some other products where we have hybrid cloud deployments we prefer Terraform which is opensource.

Incentivized

Our organisation has some experience with Dell OME (the centralised management plane for Dell PowerEdge server, equivalent to Cisco Intersight Infrastructure Service and UCS Manager, but not enough to contrast the two or say why one is better than the other.

Incentivized

dbt was fine, but you end up with an extremely bloated repo/project. Often where all of the models are the same, named similarly, and generally just doesn't adhere to the concept of DRY coding. In Terraform we're able to template a lot of this work and dynamically generate assets based on variables instead.

Incentivized

Easy to add new services into it. Having everything policy driven makes it a lot easier to add new hardware into the solution and get setup.

Incentivized

• + We can standup a VPC in minutes
• - It took a lot of inital time to set up
• + With logging/rollback, made testing much easier.

Incentivized

• It has positively impacted our business by having a validated architecture that is repeating, redeploy able that scales.
• Some of the TAC tickets could have been solved with more detailed KB's. (ie. CIMC is managed by Cisco Intersight and not be our OOBM with rack servers)

Incentivized

• Using code, we are able to build and deploy cloud resources faster and more consistently than producing the same resources in the console manually.
• For applications that share architectures, we can reuse code to expedite development. We can also do the same with modules that are shared across the organization.
• By defining all of our resources as code, we can deploy complete environments with "batteries included." For example, we can use code that spins up servers in a cloud provider and at the same time, creates monitors with in our monitoring provider. Likewise, when the servers are decommissioned, the monitors are decommed along with them. In the past, the creation and decom of the monitors would have been a disjointed, manual step. With Terraform we get it all with one "terraform apply."

Incentivized