Import and deploy an image from the OpenStack Community App Catalog in minutes

Share this post:

You probably have seen articles highlighting the benefits of a cloud built on open technologies.  Before you dismiss this as just another forgettable blog post, take a few minutes to experience one of these benefits.

We will highlight two offerings in this article:

  • The OpenStack Community App Catalog is simply a “community driven catalog” of content.  This content is contributed by the diverse membership of the OpenStack community to run on OpenStack environments.
  • IBM Bluemix is a cloud platform used to quickly turn innovative ideas into real applications using a broad palette of open technologies.

We will use the OpenStack-powered Virtual Machines service in Bluemix to import an image from the OpenStack Community App Catalog and then provision an instance—all in a matter of minutes.

OpenStack Community App Catalog

Let’s get started! First explore the at OpenStack Community App Catalog:

Fedora 23

The following steps use the Fedora 23 image contributed to the OpenStack Community App Catalog by the Fedora Project.

Import and Deploy to Bluemix

If you don’t have a Bluemix account, register now. It takes less than a minute and costs you nothing.

Step #1: Login to the Bluemix Dashboard and click RUN VIRTUAL MACHINES:

Note that at the time of this post, the virtual machines beta in the US South region were closed to new users, but they’re available in the United Kingdom region.

Step #2: Under Image Settings, select NEW and click the Upload arrow:

Step #3: Enter an Image Name, select Location(URL) from the How to upload option, then paste the link to the Fedora 23 image from the catalog under Attributes > url into the Image Location field:

Then click UPLOAD.

The image will be added to your Bluemix organization’s private catalog. Import times will vary by image. The Fedora 23 image imported for me in less than 15 seconds.

Step #4: Back on the Create Virtual Machine page, click EXISTING, and then select your newly imported image from the drop-down menu:

See Configuring a VM to use key-pair authentication for ssh options, then fill in the additional deployment parameters and click CREATE. Within minutes you are up and running!

You can log into the running VM by providing the private key generated in the previous step, similar to the command below (fedora-test.pem is the RSA private key generated following the VM authentication documentation):

$ ssh -i fedora-test.pem fedora@


Community content, running on a service built with community open source. To learn more about the OpenStack Community Application Catalog, see App-Catalog in the OpenStack wiki or directly access the catalog at To see more detailed steps, see Creating a VM in a public cloud in the official docs.

Comments or questions? Free free to post questions below, e-mail me, or contact me via Twitter @kelmmatt.

More How-tos stories
May 2, 2019

Seamless Integration: Istio and External Services

By defining our own MCP server, we allow users to move to the Istio service mesh without any code and deployment model changes. This means we can easily use Istio to control, observe, connect, and secure services running outside Kubernetes clusters.

Continue reading

April 26, 2019

Help Shape the Future of Cloud Foundry

Are you a Cloud Foundry user? If so, here's your opportunity to influence the future of Cloud Foundry with the 2019 user survey.

Continue reading

April 25, 2019

Java Licensing Has Changed, but There’s Good News

If you downloaded your Java SE binary from and are using it for commercial purposes, you have probably heard that they’ve introduced a new pricing model. Fortunately, the Eclipse OpenJ9 project delivers a no-cost JVM on AdoptOpenJDK, even for commercial use. As an added bonus, OpenJ9 is faster and leaner than other JVMs.

Continue reading