Build a SUSE OpenStack Cloud 4 lab on AWS or GCE with Ravello Systems | SUSE Communities

Build a SUSE OpenStack Cloud 4 lab on AWS or GCE with Ravello Systems


SUSE Cloud 4 is powered by OpenStack, the leading community driven, open source, cloud infrastructure project, and packaged with SUSE Linux Enterprise Server 11 SP3. The product is fully integrated with SUSE maintenance and support infrastructure. It is an ideal solution for customers looking to deploy a cloud with enterprise levels of stability and support.

Ravello allows users to run OpenStack with KVM instead of qemu in AWS or GCE leading to higher performance.  This solution allows users to deploy SUSE Openstack Cloud 4 in either AWS (Amazon Web Services) or GCE (Google Compute Engine) to build a lab environment.

In order to deploy SUSE OpenStack Cloud 4 with Ravello, first of all, you will need to create an account with Ravello Systems and request from the Ravello Support team to share the SUSE OpenStack Cloud 4 Blueprint called “SUSE OPENSTACK Cloud 4 -Final Release!” from your user account.  We are in the process of making the Blueprint publicly available in the Ravello library in the near future.

Once you have the Blueprint in your library, you will need to create an application with SUSE OpenStack Cloud 4 option selected as shown.



After creating your Ravello application based on SUSE OpenStack Cloud 4 Blueprint, your canvas should have the following nodes available for you as shown.



These nodes are ready to be deployed and no changes are needed. SUSE OpenStack Cloud 4 Infrastructure is shown below just to give you and idea of what has been done.



Furthermore, SUSE OpenStack Cloud is deployed to four different types of machines:

  • One Administration Server for node deployment and management
  • One or more Control Nodes hosting the cloud management services
  • Several Compute Nodes on which the instances are started
  • Several Storage Nodes for block and object storage

This Blueprint has one admin, one control, and one compute node available but you can add as many compute nodes as necessary.

If you decide to add more compute nodes, follow the steps described in the Ravello document on Enabling Nested Virtualization.  The compute node in this Blueprint has nested virtualization enabled as well.

The next step is publishing your Blueprint application on either AWS or GCE.  The network topology should look as shown.



The instances have external access enabled by default.  We added a new interface on the Control Node with IP which is our floating IP along with the router  We then changed openvswitch config and added a public bridge interface using the following command lines:

d2c-­‐c2-­‐60-­‐5e-­‐bd-­‐51:~ # ovs-­‐vsctl del-­‐port br-­‐public eth0.300
d2c-­‐c2-­‐60-­‐5e-­‐bd-­‐51:~ # ovs-­‐vsctl add-­‐port br-­‐public eth2

Before the change, the control node had the following configuration

ovs-­‐vsctl show

Bridge br-­‐public
Port “qg-­‐5d3051b3-­‐e1”
Interface “qg-­‐5d3051b3-­‐e1”
type: internal
Port br-­‐public
Interface br-­‐public
type: internal
Port “eth0.300”
Interface “eth0.300”

After running the above command lines, the public bridge configuration was changed to:

Bridge br-­‐public
Port “qg-­‐5d3051b3-­‐e1”
Interface “qg-­‐5d3051b3-­‐e1”
type: internal
Port br-­‐public
Interface br-­‐public
type: internal
Port “eth2”
Interface “eth0.300”

With these changes, from now on you will be able to add additional IPs to the floating pool quite easily.  You just need to make sure every floating IP has an associated IP address in the Ravello user interface as the following shows for the floating IP address.



Your Floating IP public range starts at and goes to

After you have published your SUSE OpenStack Cloud 4 environment with Ravello, make sure the following services are working based on the Ravello Public IP addresses assigned to your nodes.

1 – Admin dashboard can be accessed at http://admin_ravello_public_IP_dns:3000 – (user and password are “crowbar”)


Barclamps are deployed as well:


2 – Controller Horizon Dashboard can be accessed at http://controller_ravello_public_IO_dns (user and password are “crowbar”)


3 – There is also a SUSE Linux Enterprise Server JeOS 11 SP3 instance available to be deployed in your SUSE OpenStack Cloud and all you need to do is click on the “Start Instance” button.


4 – After your instance is up and running the VNC console can be accessed by clicking on the instance name and switching to Console tab. Make sure you replace IP for the Ravello Public IP assigned to your Controller Node as shown below to be able to see your instance VNC console. You need to do this because we are running SUSE Openstack Cloud 4 with Ravello on either AWS or GCE. This step is NOT needed when using a bare metal hardware.


As additional information, the default root password for this instance is
“SUS3*2015”. The Admin root account has the same password. The other nodes (controller and compute) have the root account password disabled but you can ssh into them from the admin node. You can also disable the instance root password and use key pair authentication as well. We have created a video demonstrating this process and it’s available in the SUSE YouTube channel and more details about SUSE Openstack Cloud can be found in the SUSE Documentation.


(Visited 1 times, 1 visits today)

Leave a Reply

Your email address will not be published.

No comments yet

Darren DavisDirector Public Cloud & ISV Engineering SUSE