Skip to content
Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Cisco ACI Ports Autoload 2G Shell

Release date: January 2019

Shell version: 1.0.0

Document version: 1.0

In This Guide


A shell integrates a device model, application or other technology with CloudShell. A shell consists of a data model that defines how the device and its properties are modeled in CloudShell, along with automation that enables interaction with the device via CloudShell.

Networking Shells

CloudShell's networking shells provide L2 or L3 connectivity between resources.

Cisco ACI Ports Autoload 2G Shell

The Cisco ACI Ports Autoload 2G shell provides you with connectivity and management capabilities such as device structure discovery for the Cisco ACI.

For more information on the Cisco ACI, see the official Cisco product documentation.

Standard version

The Cisco ACI Ports Autoload 2G shell is based on the Cloudshell Cisco ACI Standard version 1.0.0.


Release: Cisco ACI Ports Autoload 2G Shell

CloudShell version: 8.0 and above

Cisco ACI version: 3.0 and above

Note: If your CloudShell version does not support this shell, you should consider upgrading to a later version of CloudShell or contact customer support.

Data Model

The shell's data model includes all shell metadata, families, and attributes.

Cisco ACI Ports Autoload 2G Shell Families and Models

The Cisco ACI Ports families and models are listed in the following table:

Family Model Description
CS_CiscoACIPod CiscoACIPod Cisco ACI Pod
CS_CiscoACINode CiscoACINode Nodes located on the Pods
CS_CiscoACISlot CiscoACISlot Slots located on the Nodes
CS_CiscoACIPort CiscoACIPort Interfaces located on the Slot
CS_CiscoACIFex CiscoACIFex FEXs located on the Nodes
CS_CiscoACIFexSlot CiscoACIFexSlot Slots located on the FEXs
CS_CiscoACIFexPort CiscoACIFexPort Interface located on the FEXs

Cisco ACI Ports Autoload 2G Shell Attributes

Cisco ACI Ports Controller

Attribute Name Data Type User input? Description Family Attribute?
User String Yes No
Password Password Yes No
Model Name String No The Controller model/vendor in a readable format (used by the GUI for display). This information is typically used for abstract resource filtering. Yes
Controller TCP Port Integer Yes Default is 443. No
Scheme String Yes Options include: HTTP, HTTPS No


This section describes the automation (drivers) associated with the data model. The shell’s driver is provided as part of the shell package. There are two types of automation processes, Autoload and Resource. Autoload is executed when creating the resource in the Inventory dashboard, while resource commands are run in the sandbox.

Downloading the Shell

The Cisco ACI Ports Autoload 2G shell is available from the Quali Community Integrations page.

Download the files into a temporary location on your local machine.

The shell comprises:

File name Description Cisco ACI Ports Autoload shell package Shell Python dependencies (for offline deployments only)

Importing and Configuring the Shell

This section describes how to import the Cisco ACI Ports Autoload 2G shell and configure and modify the shell’s devices.

Importing the shell into CloudShell

To import the shell into CloudShell:

  1. Make sure you have the shell’s zip package. If not, download the shell from the Quali Community's Integrations page.

  2. In CloudShell Portal, as Global administrator, open the Manage – Shells page.

  3. Click Import.

  4. In the dialog box, navigate to the shell's zip package, select it and click Open.

The shell is displayed in the Shells page and can be used by domain administrators in all CloudShell domains to create new inventory resources, as explained in Adding Inventory Resources.

Offline installation of a shell

Note: Offline installation instructions are relevant only if CloudShell Execution Server has no access to PyPi. You can skip this section if your execution server has access to PyPi. For additional information, see the online help topic on offline dependencies.

In offline mode, import the shell into CloudShell and place any dependencies in the appropriate dependencies folder. The dependencies folder may differ, depending on the CloudShell version you are using:

Adding shell and script packages to the local PyPi Server repository

If your Quali Server and/or execution servers work offline, you will need to copy all required Python packages, including the out-of-the-box ones, to the PyPi Server's repository on the Quali Server computer (by default C:\Program Files (x86)\QualiSystems\CloudShell\Server\Config\Pypi Server Repository).

For more information, see Configuring CloudShell to Execute Python Commands in Offline Mode.

To add Python packages to the local PyPi Server repository:

  1. If you haven't created and configured the local PyPi Server repository to work with the execution server, perform the steps in Add Python packages to the local PyPi Server repository (offline mode).

  2. For each shell or script you add into CloudShell, do one of the following (from an online computer):

    • Connect to the Internet and download each dependency specified in the requirements.txt file with the following command: pip download -r requirements.txt. The shell or script's requirements are downloaded as zip files.

    • In the Quali Community's Integrations page, locate the shell and click the shell's Download link. In the page that is displayed, from the Downloads area, extract the dependencies package zip file.

  3. Place these zip files in the local PyPi Server repository.

Setting the python PythonOfflineRepositoryPath configuration key

Before PyPi Server was introduced as CloudShell’s python package management mechanism, the PythonOfflineRepositoryPath key was used to set the default offline package repository on the Quali Server machine, and could be used on specific Execution Server machines to set a different folder.

To set the offline python repository:

  1. Download the file, see Downloading the Shell.

  2. Unzip it to a local repository. Make sure the execution server has access to this folder.

  3. On the Quali Server machine, in the ~\CloudShell\Server\customer.config file, add the following key to specify the path to the default python package folder (for all Execution Servers):
    <add key="PythonOfflineRepositoryPath" value="repository full path"/>

  4. If you want to override the default folder for a specific Execution Server, on the Execution Server machine, in the ~TestShell\Execution Server\customer.config file, add the following key:
    <add key="PythonOfflineRepositoryPath" value="repository full path"/>

  5. Restart the Execution Server.

Configuring a new resource

This section explains how to create a new resource from the shell.

In CloudShell, the component that models the device is called a resource. It is based on the shell that models the device and allows the CloudShell user and API to remotely control the device from CloudShell.

You can also modify existing resources, see Managing Resources in the Inventory.

To create a resource for the device:

  1. In the CloudShell Portal, in the Inventory dashboard, click Add New.

  2. From the list, select Cisco ACI Ports Autoload 2G.

  3. Enter the Name and IP address of the Cisco ACI Controller.

  4. Click Create.

  5. In the Resource dialog box, enter the device's settings, see Cisco ACI Ports Autoload 2G Shell Attributes.

  6. Click Continue.

CloudShell validates the device’s settings and updates the new resource with the device’s structure.

Updating Python Dependencies for Shells

This section explains how to update your Python dependencies folder. This is required when you upgrade a shell that uses new/updated dependencies. It applies to both online and offline dependencies.

Updating offline Python dependencies

To update offline Python dependencies:

  1. Download the latest Python dependencies package zip file locally.

  2. Extract the zip file to the suitable offline package folder(s).

  3. Terminate the shell’s instance, as explained here.

Updating online Python dependencies

In online mode, the execution server automatically downloads and extracts the appropriate dependencies file to the online Python dependencies repository every time a new instance of the driver or script is created.

To update online Python dependencies:

  • If there is a live instance of the shell's driver or script, terminate the shell’s instance, as explained here. If an instance does not exist, the execution server will download the Python dependencies the next time a command of the driver or script runs.

Typical Workflows

Workflow 1 - Add Cisco ACI Port to the EndPointGroup

  1. Create a physical connection between the Cisco ACI Port and some DUT/Switch

    1. In Resource Manager, Resource Explorer pane, open the Cisco ACI Ports Autoload resource.
    2. Right-click the resource, select Configuration from the context menu and click on the Connections button at the bottom of the Resource Configuration page
    3. Connect the Cisco ACI Port to some DUT/Switch:       
    4. Save your changes
  2. In CloudShell Portal, add the Cisco ACI EPG Autoload resource and the DUT/Switch resource (where you connected the Cisco ACI Ports) to your blueprint.

  3. In the diagram view of the blueprint toolbar, click App/Service>Networking and drag the VLAN AUTO service into the diagram.


  1. Create a connection between the DUT/Switch port (which you connected earlier to the Cisco ACI Port) and the Cisco ACI EPG Autoload resource. Select the EndPoint Group you want to associate with the Cisco ACI Port.       

  2. Create a connection between the DUT/Switch port and the VLAN Auto Service.       


  1. Reserve the blueprint.


To download and share integrations, see Quali Community's Integrations.

For instructional training and documentation, see Quali University.

To suggest an idea for the product, see Quali's Idea box.

To connect with Quali users and experts from around the world, ask questions and discuss issues, see Quali's Community forums.

Release Notes

For release updates, see the shell's GitHub releases page.


No description, website, or topics provided.






No packages published