Cisco Intersight is an operations platform that helps IT operations teams control and automate Cisco UCS, converged, and hyperconverged infrastructure. Intersight consolidates and automates infrastructure lifecycle management from data centers to the edge in one solution delivered as-a-service.
N/A
IBM Terraform
Score 8.8 out of 10
N/A
IBM Terraform (formerly Hashicorp Terraform) is a cloud infrastructure automation tool used to create, change, and improve production infrastructure, and it allows infrastructure to be expressed as code. It is available Open Source, and via Cloud and Self-Hosted editions.
Since Cisco Intersight Infrastructure Service is cloud-delivered, there is a great deal of flexibility found in this platform, including the ability to manage infrastructure from anywhere at any time. Cisco is also able to continually upgrade, modify, and enhance this platform, …
It is highly suited for an organisation pushing for a standardised and centralised configuration of settings using policies, profiles and templates. It is highly suited for customers used to legacy UMM that need to refresh their environment, but instead of deploying them in UMM (which is still possible), to take the time and effort to learn Cisco Intersight Infrastructure Service and IMM as well as familiarise themselves with the differences between UMM and IMM, and the issues in UMM which IMM addresses and improves upon. We deployed in UMM initially then transitioned to IMM with the transition too. I cannot think of a scenario where Cisco Intersight Infrastructure Service would not be suited. Even for small-scale deployments, it provides significant benefits. Maybe if you come from another server vendor management environment, the learning curve may feel steep (e.g. many new concepts and constructs that one has to master).
Anything that needs to be repeated en masse. Terraform is great at taking a template and have it be repeated across your estate. You can dynamically change the assets they're generating depending on certain variables. Which means though templated assets will all be similar, they're allowed to have unique properties about them. For example flattening JSON into tabular data and ensuring the flattening code is unique to the file's schema.
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).
It is difficult to spot an added or removed VLAN in an Ethernet Network Group Policy or VLAN Policy. The comparison widget will show you that something has changed, but if you have 100s of VLANs, the difference does not stand out. Workaround: we copy the data out and compare it in a text editor.
If you are transitioning from UMM to IMM, you lose some functionality like vNIC redundancy pairs.
It is not easy to map the UMM version 4.x server firmware version to the equivalent IMM version 5.x firmware version.
It is not possible to configure out-of-band management IP addresses on a per-domain basis. You have to configure these ranges via an IMC Access policy (which contains the IP address range/pool) on the server profile. This leads to "server profile template sprawl" where we have to maintain multiple server profile templates since our domains sit on different ranges, even though the servers are for the most part configured identically.
UCS domains in IMM only support one Ethernet Network Group Policy (VLAN group) per vNIC template.
The language itself is a bit unusual and this makes it hard for new users to get onboarded into the codebase. While it's improving with later releases, basic concepts like "map an array of options into a set of configurations" or "apply this logic if a variable is specified" are possible but unnecessarily cumbersome.
The 'Terraform Plan' operation could be substantially more sophisticated. There are many situations where a Terraform file could never work but successfully passes the 'plan' phase only to fail during the 'apply' phase.
Environment migrations could be smoother. Renaming/refactoring files is a challenge because of the need to use 'Terraform mv' commands, etc.
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.
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.)
I love Terraform and I think it has done some great things for people that are working to automate their provisioning processes and also for those that are in the process of moving to the cloud or managing cloud resources. There are some quirks to HCL that take a little bit of getting used to and give picking up Terraform a little bit of a learning curve, thus the rating
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.
I have had servers TAC cases open for issues with Cisco Intersight. Some have yet to be resolved. One case that is still open is where the HCL status ( Hardware Compatibility List ) shows not validated when It should be. We have several servers that have the exact same hardware, OS, and the same firmware. One server will show the HCL is not validated but all others will
I have yet to have an opportunity to reach out directly to HashiCorp for support on Terraform. However, I have spent a great deal of time considering their documentation as I use the tool. This opinion is based solely on that. I find the Terraform documentation to have great breadth but lacking in depth in many areas. I appreciate that all of the tool's resources have an entry in the docs but often the examples are lacking. Often, the examples provided are very basic and prompt additional exploration. Also, the links in the documentation often link back to the same page where one might expect to be linked to a different source with additional information.
I personally think that Cisco Intersight Infrastructure Service is at the top of its class when it comes to managing data center hardware. The cloud-connected design feels very modern and easy to use. The mobile app is something I wouldn't expect to get in a server management tool. The way it can update, monitor, and manage our servers is very nice. Overall, we are very happy with it.
Terraform is the solid leader in the space. It allows you to do more then just provisioning within a pre-existing servers. It is more extensible and has more providers available than it competitors. It is also open source and more adopted by the community then some of the other solutions that are available in the market place.
The negative thing is that we prefer to use the UCS Manager in our company because this bare metal is integrated into the FI and no extra appliance is required. SaaS is generally not viewed favorably in Germany.
Telling the user that they have to buy Intersight licenses even if they use UCS Manager annoys our customers.
we are able to deploy our infrastructure in a couple of ours in an automated and repeatable way, before this could take weeks if the work was done manually and was a lot of error prone.
having the state file, you can see a diff of what things have changed manually out side of Terraform which is a huge plus
if state file gets corrupted, it is very hard to debug or restore it without an impact or spending hours ..
writing big scale code can be very challenging and hard to be efficient so it's usable by the whole team
