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
Salt
Score 6.3 out of 10
N/A
Built on Python, Salt is an event-driven automation tool and framework to deploy, configure, and manage complex IT systems. Salt is used to automate common infrastructure administration tasks and ensure that all the components of infrastructure are operating in a consistent desired state.
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).
SaltStack is a very well architected toolset and framework for reliably managing distributed systems' complexity at varied scale. If the diversity of kind or number of assets is low, or the dependencies are bounded and simple, it might be overkill. Realization that you need SaltStack might come in the form of other tools, scripts, or jobs whose code has become difficult, unreliable, or unmaintainable. Rather than a native from-scratch SaltStack design, be aware that SaltStack can be added on to tools like Docker or Chef and optionally factor those tools out or other tools into the mix.
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).
Targeting is easy and yet extremely granular - I can target machines by name, role, operating system, init system, distro, regex, or any combination of the above.
Abstraction of OS, package manager and package details is far advanced beyond any other CRM I have seen. The ability to set one configuration for a package across multiple distros, and have it apply correctly no matter the distrospecific naming convention or package installation procedure, is amazing.
Abstraction of environments is similarly valuable - I can set a firewall rule to allow ssh from "management", and have that be defined as a specific IP range per dev, test, and prod.
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.
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 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
We haven't had to spend a lot of time talking to support, and we've only had one issue, which, when dealing with other vendors is actually not that bad of an experience.
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.
We moved to SaltStack from Puppet about 3 years ago. Puppet just has too much of a learning curve and we inherited it from an old IT regime. We wanted something we could start fresh with. Our team has never looked back. SaltStack is so much easier for us to use and maintain.
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 manage two complex highly available self-healing (all infrastructure and systems) environments using SaltStack. Only one person is needed to run SaltStack. That is a HUGE return on investment.
Building tooling on top of SaltStack has allowed us to share administrative abilities by role - e.g. employee X can deploy software Y. No need to call a sysadmin and etc.
Recovery from problems, or time to stand-up new systems is now counted in minutes (usually under eight) rather than hours. This is a strategic advantage for rolling out new services.
