StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. DevOps
  3. Continuous Deployment
  4. Server Configuration And Automation
  5. Cisco ACI vs Salt

Cisco ACI vs Salt

OverviewComparisonAlternatives

Overview

Salt
Salt
Stacks410
Followers449
Votes165
GitHub Stars14.9K
Forks5.6K
Cisco ACI
Cisco ACI
Stacks9
Followers7
Votes0

Cisco ACI vs Salt: What are the differences?

Introduction

Cisco ACI and Salt are two popular software solutions used in the IT industry. While both technologies offer benefits in managing and automating network infrastructure, they have key differences that set them apart. In this article, we will explore the key differences between Cisco ACI and Salt.

  1. Integration with Network Devices: Cisco ACI is a data center networking solution that provides a centralized policy-driven framework for managing network infrastructure. It integrates closely with Cisco networking devices, allowing administrators to define and enforce policies across the network fabric. On the other hand, Salt is an open-source software used for IT automation and configuration management. It offers the flexibility to work with a wide range of network devices, including Cisco devices, as well as devices from other vendors. This makes Salt a more versatile solution for heterogeneous network environments.

  2. Focus: Cisco ACI primarily focuses on providing a comprehensive solution for data center network automation and management. It offers features such as application-centric networking, security, and policy-driven automation. Salt, on the other hand, is a general-purpose automation and configuration management tool that can be used across various IT domains, including network automation, server management, and cloud orchestration. Salt's broad focus allows it to be used in a wider range of use cases beyond just network automation.

  3. Architecture: Cisco ACI adopts a leaf-spine architecture, where leaf switches connect to spine switches, forming a scalable and high-performance network fabric. It uses an Application Policy Infrastructure Controller (APIC) to manage the network fabric, define policies, and automate network operations. Salt follows a master-minion architecture, where a central Salt master server controls and manages multiple Salt minion agents deployed on network devices. The master server pushes configurations and commands to the minion agents, enabling centralized management and automation.

  4. Policy and Configuration Management: Cisco ACI offers a policy-based approach to network management. It allows administrators to define and enforce policies at various levels, including application, tenant, and security policies. Policies are defined centrally and applied consistently across the network fabric. Salt provides a declarative approach to configuration management, where infrastructure state is defined using Salt states. Salt states describe the desired configuration state of network devices, and Salt ensures that the actual state matches the desired state, enforcing consistency and automation.

  5. Community and Ecosystem: Cisco ACI is a proprietary technology developed by Cisco Systems, with a large and established community of users and developers. It has a robust ecosystem of Cisco-specific tools and integrations. Salt, on the other hand, is an open-source technology with a vibrant community and ecosystem. It is supported by a wide range of modules and extensions developed by the community, offering flexibility and extensibility.

  6. Scalability and Flexibility: Cisco ACI provides a highly scalable solution for large-scale data center deployments. It offers features like automatic fabric discovery, automatic path computation, and scale-out architecture to handle the growth and demands of data center networks. Salt is also highly scalable and flexible, supporting thousands of network devices. It offers flexible configuration management through pillars, allowing administrators to organize and manage configuration data in a hierarchical and flexible manner.

In summary, Cisco ACI offers a specialized and comprehensive solution for data center network automation, focusing on Cisco devices and providing a policy-driven approach. Salt, on the other hand, is a versatile open-source automation and configuration management tool that can work with a wide range of network devices and has a broader scope beyond just network automation.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Salt
Salt
Cisco ACI
Cisco ACI

Salt is a new approach to infrastructure management. Easy enough to get running in minutes, scalable enough to manage tens of thousands of servers, and fast enough to communicate with them in seconds. Salt delivers a dynamic communication bus for infrastructures that can be used for orchestration, remote execution, configuration management and much more.

It represents the industry's most comprehensive data center networking solution with flexible deployment options and the ability to deploy apps based on business needs, not by technology limitations.

Remote execution is the core function of Salt. Running pre-defined or arbitrary commands on remote hosts.;Salt modules are the core of remote execution. They provide functionality such as installing packages, restarting a service, running a remote command, transferring files, and infinitely more;Building on the remote execution core is a robust and flexible configuration management framework. Execution happens on the minions allowing effortless, simultaneous configuration of tens of thousands of hosts.
Automation and consistency; Multicloud acceleration; Protect your network with zero-trust; Assurance and insights
Statistics
GitHub Stars
14.9K
GitHub Stars
-
GitHub Forks
5.6K
GitHub Forks
-
Stacks
410
Stacks
9
Followers
449
Followers
7
Votes
165
Votes
0
Pros & Cons
Pros
  • 47
    Flexible
  • 30
    Easy
  • 27
    Remote execution
  • 24
    Enormously flexible
  • 12
    Great plugin API
Cons
  • 1
    No immutable infrastructure
  • 1
    Dangerous
  • 1
    Bloated
No community feedback yet

What are some alternatives to Salt, Cisco ACI?

Ansible

Ansible

Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use.

Chef

Chef

Chef enables you to manage and scale cloud infrastructure with no downtime or interruptions. Freely move applications and configurations from one cloud to another. Chef is integrated with all major cloud providers including Amazon EC2, VMWare, IBM Smartcloud, Rackspace, OpenStack, Windows Azure, HP Cloud, Google Compute Engine, Joyent Cloud and others.

Terraform

Terraform

With Terraform, you describe your complete infrastructure as code, even as it spans multiple service providers. Your servers may come from AWS, your DNS may come from CloudFlare, and your database may come from Heroku. Terraform will build all these resources across all these providers in parallel.

Capistrano

Capistrano

Capistrano is a remote server automation tool. It supports the scripting and execution of arbitrary tasks, and includes a set of sane-default deployment workflows.

Puppet Labs

Puppet Labs

Puppet is an automated administrative engine for your Linux, Unix, and Windows systems and performs administrative tasks (such as adding users, installing packages, and updating server configurations) based on a centralized specification.

Fabric

Fabric

Fabric is a Python (2.5-2.7) library and command-line tool for streamlining the use of SSH for application deployment or systems administration tasks. It provides a basic suite of operations for executing local or remote shell commands (normally or via sudo) and uploading/downloading files, as well as auxiliary functionality such as prompting the running user for input, or aborting execution.

AWS OpsWorks

AWS OpsWorks

Start from templates for common technologies like Ruby, Node.JS, PHP, and Java, or build your own using Chef recipes to install software packages and perform any task that you can script. AWS OpsWorks can scale your application using automatic load-based or time-based scaling and maintain the health of your application by detecting failed instances and replacing them. You have full control of deployments and automation of each component

cPanel

cPanel

It is an industry leading hosting platform with world-class support. It is globally empowering hosting providers through fully-automated point-and-click hosting platform by hosting-centric professionals

Webmin

Webmin

It is a web-based interface for system administration for Unix. Using any modern web browser, you can setup user accounts, Apache, DNS, file sharing and much more. It removes the need to manually edit Unix configuration files.

Mina

Mina

Mina works really fast because it's a deploy Bash script generator. It generates an entire procedure as a Bash script and runs it remotely in the server. Compare this to the likes of Vlad or Capistrano, where each command is run separately on their own SSH sessions. Mina only creates one SSH session per deploy, minimizing the SSH connection overhead.

Related Comparisons

GitHub
Bitbucket

Bitbucket vs GitHub vs GitLab

GitHub
Bitbucket

AWS CodeCommit vs Bitbucket vs GitHub

Kubernetes
Rancher

Docker Swarm vs Kubernetes vs Rancher

gulp
Grunt

Grunt vs Webpack vs gulp

Graphite
Kibana

Grafana vs Graphite vs Kibana