Difference between revisions of "Vnx-labo-openstack"

From VNX
Jump to: navigation, search
(Installation)
(Starting the scenario)
Line 85: Line 85:
  
 
  vnx_config_nat ExtNet eth0
 
  vnx_config_nat ExtNet eth0
 +
 +
== Stopping or releasing the scenario ==
 +
 +
To stop the scenario preserving the configuration and the changes made:
 +
 +
vnx -f openstack_tutorial-4nodes.xml -v --shutdown
 +
 +
To start it again use:
 +
 +
vnx -f openstack_tutorial-4nodes.xml -v --start
 +
 +
To stop the scenario destroying all the configuration and changes made:
 +
 +
vnx -f openstack_tutorial-4nodes.xml -v --destroy
 +
 +
To unconfigure the NAT, just execute:
 +
 +
vnx_config_nat -d ExtNet eth0

Revision as of 18:56, 8 December 2015

VNX Openstack laboratory

Introduction

This is an Openstack tutorial scenario designed to experiment with Openstack free and open-source software platform for cloud-computing.

The scenario is made of four virtual machines: a controller based on LXC and a network node and two compute nodes based on KVM. Optionally, a third compute node can be added once the scenario is started.

All virtual machines use Ubuntu 14.04.3 LTS and Openstack Kilo.

The scenario has been inspired by the ones developed by Raul Alvarez to test OpenDaylight-Openstack integration, but instead of using Devstack to configure Openstack nodes, the configuration is done by means of commands integrated into the VNX scenario following Openstack installation recipes in http://docs.openstack.org/kilo/install-guide/install/apt/content/

Requirements

To use the scenario you need a Linux computer (Ubuntu 14.04 or later recommended) with VNX software installed. At least 4Gb of memory are needed to execute the scenario.

See how to install VNX here: http://vnx.dit.upm.es/vnx/index.php/Vnx-install

If already installed, update VNX to the latest version with:

vnx_update

To make startup faster, enable one-pass-autoconfiguration for KVM virtual machines in /etc/vnx.conf:

[libvirt]
...
one_pass_autoconf=yes

Check that KVM nested virtualization is enabled:

cat /sys/module/kvm_intel/parameters/nested
Y

If not enabled, check, for example, http://docs.openstack.org/developer/devstack/guides/devstack-with-nested-kvm.html to enable it.

Installation

Download the scenario with the virtual machines images included and unpack it:

wget http://idefix.dit.upm.es/cnvr/openstack_tutorial-v013-with-rootfs.tgz
vnx --unpack openstack_tutorial-v013.tgz

Alternatively, you can download the much lighter version without the images and create the root filesystems from scratch in your computer:

wget http://idefix.dit.upm.es/cnvr/openstack_tutorial-v013-with-rootfs.tgz
vnx --unpack openstack_tutorial-v013.tgz
cd openstack_tutorial-v013/filesystems
./create-kvm_ubuntu64-ostack-compute
./create-kvm_ubuntu64-ostack-network
./create-lxc_ubuntu64-ostack-controller

Starting the scenario

Start the scenario and configure it and load an example cirros image with:

vnx -f openstack_tutorial-4nodes.xml -v -t
vnx -f openstack_tutorial-4nodes.xml -v -x start-all
vnx -f openstack_tutorial-4nodes.xml -v -x load-img

Once started, you can connect to Openstack Dashboard (admin/xxxx) starting a browser and pointing it to the controller horizon page. For example:

firefox 10.0.10.11/horizon

Access Dashboard page "Project|Network|Network topology" and create a simple demo scenario inside Openstack:

vnx -f openstack_tutorial-4nodes.xml -v -x create-demo-scenario

You should see the simple scenario as it is being created through the Dashboard.

Once created you should be able to access vm1 console, to ping or ssh from the host to the vm1 or the opposite (see the floating IP assigned to vm1 in the Dashboard, probably 10.0.10.102).

Finally, to allow external Internet access from vm1 you hace to configure a NAT in the host. You can easily do it using vnx_config_nat command distributed with VNX. Just find out the name of the public network interface of your host (i.e eth0) and execute:

vnx_config_nat ExtNet eth0

Stopping or releasing the scenario

To stop the scenario preserving the configuration and the changes made:

vnx -f openstack_tutorial-4nodes.xml -v --shutdown

To start it again use:

vnx -f openstack_tutorial-4nodes.xml -v --start

To stop the scenario destroying all the configuration and changes made:

vnx -f openstack_tutorial-4nodes.xml -v --destroy

To unconfigure the NAT, just execute:

vnx_config_nat -d ExtNet eth0