Skip to content
This repository has been archived by the owner on Jul 16, 2020. It is now read-only.

Commit

Permalink
Merge pull request #1078 from mcastelino/topic/documentation
Browse files Browse the repository at this point in the history 
Documentation: Documentation update
  • Loading branch information
@markdryan
markdryan committed Jan 30, 2017
2 parents f6611c3 + 5893817 commit db312ec
Showing 1 changed file with 138 additions and 68 deletions.
206 changes: 138 additions & 68 deletions DeveloperQuickStart.md
View file
Original file line number Diff line number Diff line change
@@ -1,28 +1,51 @@
# Ciao Single Machine Development and Test Environment

Developing cluster software is complicated if you must actually run a whole cluster on a set of physical machines. This begs for a development environment that is self contained and can be run without any setup.
Developing cluster software is complicated if you must actually run a whole
cluster on a set of physical machines. This begs for a development environment
that is self contained and can be run without any setup.

The goals for the Ciao development environment are that it:

- Requires very minimal setup by the user
- Does not affect the user's development system in any manner (i.e. the user can keep the firewall rules, selinux setup,... intact)
- Supports modes that allow it to run on a range of devices from powerful workstations to less powerful laptops
- Provides the ability to validate all code changes the user makes against the Ciao release criterion

This page documents a way to set up an entire Ciao cluster inside a single machine. This cluster-in-a-machine mode is ideal for developers that desire the ability to build Ciao from sources, make changes and perform quick end to end functional integration testing without requiring multiple machines/VM's, creating a custom networking environment or maintaining a bevy of physical machines and a physical network.
- Does not affect the user's development system in any manner (i.e. the user
can keep the firewall rules, selinux setup,... intact)
- Supports modes that allow it to run on a range of devices from powerful
workstations to less powerful laptops
- Provides the ability to validate all code changes the user makes against
the Ciao release criterion

This page documents a way to set up an entire Ciao cluster inside a single
machine. This cluster-in-a-machine mode is ideal for developers that desire
the ability to build Ciao from sources, make changes and perform quick end to
end functional integration testing without requiring multiple machines/VM's,
creating a custom networking environment or maintaining a bevy of physical
machines and a physical network.

We support two modes of operation:

- ciao-down mode: Where a virtual machine is automatically created and launched, and the virtual cluster is setup and tested within the virtual machine
- bare metal mode: Where the virtual cluster is setup on the host machine itself
- ciao-down mode: Where a virtual machine is automatically created and
launched, and the virtual cluster is setup and tested within the virtual
machine
- bare metal mode: Where the virtual cluster is setup on the host machine
itself

The ciao-down mode is the preferred mode of development on systems that have the resources and CPU capabilities needed, as it fully isolates the Ciao virtual cluster and sets up an environment in which Ciao is known to work seamlessly. In addition, the ciao-down mode does not require any changes to the user's network firewall setup. However, ciao-down mode does require VT-x nesting to be supported by the host.
The ciao-down mode is the preferred mode of development on systems that have
the resources and CPU capabilities needed, as it fully isolates the Ciao
virtual cluster and sets up an environment in which Ciao is known to work
seamlessly. In addition, the ciao-down mode does not require any changes to
the user's network firewall setup. However, ciao-down mode does require
VT-x nesting to be supported by the host.

The bare metal mode is the highest performance mode, but may require some network firewall modification. It also uses less resources and can run on machines whose CPUs do not support VT-x nesting.
The bare metal mode is the highest performance mode, but may require some
network firewall modification. It also uses less resources and can run on
machines whose CPUs do not support VT-x nesting.

In both modes Ciao is configured in a special all in one development mode where cluster nodes have dual roles (i.e launcher can be a Network Node and a Compute Node at the same time)
In both modes Ciao is configured in a special all in one development mode
where cluster nodes have dual roles (i.e launcher can be a Network Node and
a Compute Node at the same time)

In the text below **machine** refers to the ciao-down VM in the case of the ciao-down mode, it refers to the host system in the case of the bare metal mode.
In the text below **machine** refers to the ciao-down VM in the case of the
ciao-down mode, it refers to the host system in the case of the bare metal mode.

## Components running on the Machine
1. Controller
Expand All @@ -34,65 +57,57 @@ In the text below **machine** refers to the ciao-down VM in the case of the ciao
7. Machine Local DHCP Server
...

The machine acts as the Ciao compute node, network node, ciao-controller, ciao-scheduler and also hosts the ciao-webui as well as other openstack and dhcp services.
The machine acts as the Ciao compute node, network node, ciao-controller,
ciao-scheduler and also hosts the ciao-webui as well as other openstack
and dhcp services.

## Graphical Overview

When the system is functioning the overall setup manifests as follows:

As you can see below the Cluster runs on a isolated virtual network resident inside the machine.
Hence the cluster is invisible outside the machine and completely self contained.
As you can see below the Cluster runs on a isolated virtual network resident
inside the machine. Hence the cluster is invisible outside the machine and
completely self contained.

```
___________________________________________________________________________________________________
| |
| |
| |
| [Tenant VMs] [CNCI VMs] |
| | | | || |
| Tenant Bridges ---------- || |
| | || |
| | || |
| [ciao-webui] [scheduler] [controller] [keystone] [CN+NN Launcher] | || |
| || || || || || | || |
| || || || || || | || |
| || || || || || | || |
| || || || || || | || |
| || || || || || | || |
| || || || || || [DHCP/DNS | || |
| || || || || || Server] | || |
| || || || || || || | || |
| ---------------------------------------------------------------------------------------- |
| Host Local Network Bridge + macvlan (ciao_eth, ciaovlan) |
| |
| |
|___________________________________________________________________________________________________|
____________________________________________________________________________________________
| |
| |
| |
| [Tenant VMs] [CNCI VMs] |
| | | | || |
| Tenant Bridges ---------- || |
| | || |
| | || |
| [ciao-webui] [scheduler] [controller] [keystone] [CN+NN Launcher] | || |
| || || || || || | || |
| || || || || || | || |
| || || || || || | || |
| || || || || || | || |
| || || || || || | || |
| || || || || || [DHCP/DNS | || |
| || || || || || Server] | || |
| || || || || || || | || |
| -------------------------------------------------------------------------------------- |
| Host Local Network Bridge + macvlan (ciao_br, ciaovlan) |
| |
| |
|____________________________________________________________________________________________|
Development Machine
```

----

# Cluster External Network Access

If you desire to provide external network connectivity to the workloads then the host needs to act as gateway to the Internet. The host needs to enable ipv4 forwarding and ensure all traffic exiting the cluster via the host is NATed.

This assumes the host has a single network interface. For multi homed systems, the setup is more complicated and needs appropriate routing setup which is outside the scope of this document. If you have a custom firewall configuration, you will need set things up appropriately.

Very simplistically this can be done by
```
iptables -t nat -A POSTROUTING -o $device -j MASQUERADE #$device is the network interface on the host
echo 1 > /proc/sys/net/ipv4/ip_forward
```

# Install Go
On the host install the latest release of go for your distribution
[Installing Go](https://golang.org/doc/install).

> NOTE: Go version 1.7 or later is required for Ciao. Ciao will not work with older version of Go. Hence it is best you download and install the latest version of Go if you distro is not on Go 1.7.
> NOTE: Go version 1.7 or later is required for Ciao. Ciao will not work with
older version of Go. Hence it is best you download and install the latest
version of Go if you distro is not on Go 1.7.

You should also ensure that your GOPATH environment variable is set.

Expand Down Expand Up @@ -158,21 +173,23 @@ same location as the directory appears on your host. You can then
modify the ciao-webui code on your host and build inside the VM.


For more details and full set of capabilities of ciao-down see the full [ciao-down documentation ](https://github.com/01org/ciao/blob/master/testutil/ciao-down/README.md)
For more details and full set of capabilities of ciao-down see the full
[ciao-down documentation ](https://github.com/01org/ciao/blob/master/testutil/ciao-down/README.md)


# Getting Started with Bare Metal

## Install Docker
Install latest docker for your distribution based on the instructions from Docker
Install latest docker for your distribution based on the instructions from
Docker
[Installing Docker](https://docs.docker.com/engine/installation/).

## Install ciao dependencies

Install the following packages which are required:
1. qemu-system-x86_64 and qemu-img, to launch the VMs and create qcow images
2. gcc, required to build some of the ciao dependencies
3. dnsmasq, required to setup a test DHCP server
1. qemu-system-x86_64 and qemu-img, to launch the VMs and create qcow images
2. gcc, required to build some of the ciao dependencies
3. dnsmasq, required to setup a test DHCP server

On clearlinux all of these dependencies can be satisfied by installing the following bundles:
```
Expand All @@ -182,6 +199,28 @@ swupd bundle-add cloud-control go-basic os-core-dev kvm-host os-installer

Setup passwordless sudo for the user who will be running the script below.

## Cluster External Network Access

If you desire to provide external network connectivity to the workloads then
the host needs to act as gateway to the Internet. The host needs to enable
ipv4 forwarding and ensure all traffic exiting the cluster via the host is
NATed.

This assumes the host has a single network interface. For multi homed systems,
the setup is more complicated and needs appropriate routing setup which is
outside the scope of this document. If you have a custom firewall
configuration, you will need set things up appropriately.

Very simplistically this can be done by
```
#$device is the network interface on the host
iptables -t nat -A POSTROUTING -o $device -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
```


## Download and build the sources

Download and build the ciao sources:
Expand All @@ -194,18 +233,23 @@ You should see no errors.

# Verify that Ciao is fully functional using the **machine**

Now that you have the machine setup (either a bare metal setup or a ciao-down VM setup).
Now that you have the machine setup (either a bare metal setup or a
ciao-down VM setup).

You can now quickly verify that all aspects of Ciao including VM launch,
container launch, and networking.

You can now quickly verify that all aspects of Ciao including VM launch, container launch, and networking.
These steps are performed inside the machine.

To do this simply run the following:
```
cd $GOPATH/src/github.com/01org/ciao/testutil/singlevm
. ~/local/demo.sh
#Cleanup any previous setup
./cleanup.sh
#Set up the test environment
./setup.sh
. ~/local/demo.sh
#Perform a full cluster test
./verify.sh
```
Expand All @@ -216,13 +260,32 @@ The ```verify.sh``` script will:
- Test for ssh reach ability into VMs with private and external IPs
- Delete all the VM's and Container that were created

If the script reports success, it indicates to the developer that any changes made have not broken any functionality across all the Ciao components.
If the script reports success, it indicates to the developer that any changes
made have not broken any functionality across all the Ciao components.

To quickly test any changes you make run verify.sh and observe no failures.

Prior to sumitting a change request to ciao, please run the BAT tests below
in addition to verify.sh to ensure your changes meet the ciao acceptance
criterion.

Meeting the goal originally outlined at the top of the page, build/setup/running your cluster all-in-one all transpires quickly and easily from the single script. The time needed for ./setup.sh and ./verify.sh to build ciao from source, configure it components into a virtual cluster, then launch and teardown containers and VMs is on the order of one minute total elapsed time.
Meeting the goal originally outlined at the top of the page, build/setup/running
your cluster all-in-one all transpires quickly and easily from the single
script. The time needed for ./setup.sh and ./verify.sh to build ciao from
source, configure it components into a virtual cluster, then launch and
teardown containers and VMs is on the order of one minute total elapsed time.

## Ongoing Usage
# Ongoing Usage

Once it's finished, the ```setup.sh``` script leaves behind a virtual cluster which can be used to perform manual tests. These tests are performed using the [ciao-cli](https://github.com/01org/ciao/blob/master/ciao-cli/README.md) tool. The ciao-cli tool requires that some environment variables be set up before it will work properly. These variables contain the URLs of the various ciao services and the credentials needed to access these services. The setup.sh script creates a shell source that contains valid values for the newly set up cluster. To initialise these variables you just need to source that file, e.g,
Once it's finished, the ```setup.sh``` script leaves behind a virtual cluster
which can be used to perform manual tests. These tests are performed using
the [ciao-cli](https://github.com/01org/ciao/blob/master/ciao-cli/README.md) tool.

The ciao-cli tool requires that some environment variables be set up before it
will work properly. These variables contain the URLs of the various ciao
services and the credentials needed to access these services. The setup.sh
script creates a shell source that contains valid values for the newly set up
cluster. To initialise these variables you just need to source that file, e.g,

```
. ~/local/demo.sh
Expand All @@ -236,9 +299,10 @@ ciao-cli workload list

# Running ciao-webui

The easiest way to develop and run the ciao-webui is inside a VM built by ciao-down.
Not only does ciao-down download the web-ui code for you but it also downloads and
configures all of the dependencies needed to develop the ciao-webui, such as npm.
The easiest way to develop and run the ciao-webui is inside a VM built by
ciao-down. Not only does ciao-down download the web-ui code for you but it
also downloads and configures all of the dependencies needed to develop the
ciao-webui, such as npm.

To run the webui in a ciao-down VM simply execute the following commands

Expand All @@ -258,7 +322,10 @@ to start managing your cluster.

# Running the BAT tests

The ciao project includes a set of acceptance tests that must pass before each release is made. The tests perform various tasks such as listing workloads, creating and deleting instances, etc. These tests can be run inside the machine
The ciao project includes a set of acceptance tests that must pass before each
release is made. The tests perform various tasks such as listing workloads,
creating and deleting instances, etc. These tests can be run inside the
machine

```
# Source the demo.sh file if you have not already done so
Expand All @@ -275,6 +342,7 @@ To cleanup and tear down the cluster:
```
cd $GOPATH/src/github.com/01org/ciao/testutil/singlevm
#Cleanup any previous setup
. ~/local/demo.sh
./cleanup.sh
```

Expand All @@ -283,7 +351,9 @@ cd $GOPATH/src/github.com/01org/ciao/testutil/singlevm
- Does not work on Fedora due to default firewall rules.
https://github.com/01org/ciao/issues/526

In order to allow the traffic required by the test cases you can add temporary rules like the ones show below
In order to allow the traffic required by the test cases you can add temporary
rules like the ones show below

```
#!/bin/bash
iptables -I INPUT 1 -p tcp -m tcp --dport 8888 -j ACCEPT
Expand Down

0 comments on commit db312ec

Please sign in to comment.