Software and Versions FAQ

Metacloud is a complex platform with many components and many ways to perform various operations. Questions about versions and compatibility are common. This page provides answers to frequently asked questions about versions of the following:

Metacloud and OpenStack version FAQ

What is the most currently supported version of Metacloud?

Metacloud 4.x (Liberty) is the most currently supported version. Icehouse is also supported.

Where can I learn about the latest Liberty release, updates, and features?

See Release Notes in the Metacloud Docs.

Does the Metacloud Support team update my cloud to the latest Metacloud point release, as in from 4.x to 4.x?

Yes. Before performing the update, Metacloud Support creates a ticket to notify your Metacloud Administrator of a new release and to ask you to schedule a maintenance window.

How can I find out which Metacloud release I currently have?

Submit a P4 request to Metacloud Support.

If I'm on an earlier version of Metacloud, such as Icehouse, can I upgrade to Liberty?

An upgrade path to Liberty from earlier versions is currently in development. Until then, you can have Liberty deployed as a completely new build. Submit a request to Metacloud Support using the Build Request priority.

OpenStack clients

These questions concern the command-line interface (CLI) clients for performing Metacloud operations.

Should I use openstack commands in the CLI or legacy commands for individual OpenStack services, such as nova, cinder, or heat?

The OpenStack client conveniently standardizes commands for all OpenStack services, so it is recommended that you use openstack commands, rather than try to keep track of all the commands for individual services. You may find, on occasion, that the OpenStack client does not yet provide an equivalent for a particular command available in a service CLI. Use the OpenStack Mapping Guide to compare the OpenStack client with legacy CLIs for equivalent commands.

Which version of the OpenStack client should I use?

Version 3.8 of the OpenStack client is currently supported.

How do I install the OpenStack client?

Follow the instructions at Installing OpenStack CLI Tools on Mac OS X or Installing OpenStack CLI Tools on Windows. After completing the installation, make sure to follow the instructions at Providing Metacloud Credentials to CLI Tools for giving your CLI access to Metacloud.

How do I install individual service CLIs if I want to use them? 

The OpenStack client installation also includes legacy commands for Cinder, Glance, and Nova, so no additional installation is required for these services.

For other services, such as Heat, after creating and activating your virtual environment as instructed in Metacloud documentation (see preceding question), use the command:

pip install python-<PROJECT>client


pip install python-heatclient

After installing the client, follow the instructions in the Metacloud documentation to give your CLI access to Metacloud if you have not previously done so (see previous question).

Note: The CLIs for Keystone and Neutron are deprecated. Use the OpenStack Client for the Identity and Networking services.

What information is contained in the OpenStack RC file that I downloaded to access Metacloud from the CLI?

This file contains variables that allow your virtual environment to communicate with Metacloud. Variables identify your user account, the Metacloud project in which the file was generated, and the domain in which your cloud is deployed. Another variable indicates the version of the Identity service (Keystone) API, which can be useful for troubleshooting issues with authentication or authorization.

How do I upgrade a client? 

Use the command:

pip install --upgrade python-<PROJECT>client


pip install --upgrade python-openstackclient
pip install --upgrade python-heatclient

How do I find out which services I have in my virtual environment?

Use pip list, which generates a list of installed software, including the services.

How do I know what version of OpenStack client or an OpenStack project client I'm using?

Use the command:

<CLIENT> --version


openstack --version

heat --version

Python and Other Virtual Environment Dependencies

These questions concern tools for installing and updating virtual environments to support the CLI. 

Which version of Python do I need for my OpenStack virtual environment?

Metacloud supports Python 2.7 or later.

How do I know which version of Python I'm using?

Use the command:

python --version

I have a Mac, which shipped with Python 2.7 already installed. Do I still need to install Python?

The Python version installed on your Mac is likely to be an earlier version than the current Python release. As with any software, updating to the latest version is a best practice to maximize performance and security. It is recommended that you do a fresh Python installation using a package manager such as Homebrew, which makes it easy to perform updates. See Installing OpenStack CLI Tools on Mac OS X for more information.

Can I use a Python package manager other than PIP? 

You can use any Python package manager that is appropriate for your needs. For example, if you are using a Python distribution such as Anaconda or Miniconda, you can use conda. 

Note: Different package managers entail different commands, rules, and directory structures. Follow the instructions for your preferred package manager.

Why do I have to install a virtual environment before installing the CLI?

Installing a virtual environment allows you to isolate a set of tools with specific dependencies. This can be useful if you are using multiple versions of a resource for different applications, for example, different versions of Python.

How do I find out quickly what software and versions are running in my virtual environment?

Use pip list, which generates a list of software and version numbers running in your environment.

How can I restore the state of my virtual environment if something accidentally changes?

1. Create requirements file that captures a snapshot of your current virtual environment: 

$ pip freeze > requirements.txt

2. Reload the virtual environment based on the requirements file:

$ pip install -r requirements.txt  
Have more questions? Submit a request
Powered by Zendesk