Metapod and OpenStack Terminology

Common terms used by the Cisco team and throughout the Metacloud system are:

  • API: The RESTful API for interacting with your cloud. Both the Dashboard and the CLI provide interfaces into the API, which is where all functionality appears first.

  • Availability Zone (AZ): A distinct grouping of servers forming a cloud environment. Each AZ is accessed using a distinct API and Dashboard instance, independent from other AZs.

  • Dashboard: The web-based GUI for interacting with your cloud. Please note, the Dashboard represents a subset of the functionality available via the API and CLI.

  • Flavor: A virtual hardware profile applied to instances at creation time. Flavors control the number of vCPUs, memory, root disk size and ephemeral storage size of an instance.

  • Floating IP: An IP address (usually public) which is mapped to a specific instance to allow external connectivity into that instance. Technically speaking, a one-to-one NAT is dynamically created from a floating IP address to the fixed IP address of your instance.

  • Instance: A virtual machine running in the cloud, sometimes referred to as a VM or a guest.

  • Metapod Control Plane (MCP): Servers which handle the scheduling and orchestration functions of your cloud. Additionally, in some environments they act as routers for tenant traffic.

  • Metapod Hypervisor (MHV): Servers that run the instances created in your environment.

  • Security Group: A collection of firewall rules applied to an instance.

  • Tenant: A logical subdivision of an Availability Zone consisting of an 802.1Q VLAN and a unique network address space. The term tenant is used interchangeably with project.

  • VLAN: IEEE 802.1Q tagged VLANs.

  • Volume: The volume service allows for the attachment of additional block storage to instances. Volumes can be attached and detached from instances as needed.