aboutsummaryrefslogtreecommitdiffstats
path: root/docker/README-containers.md
blob: 5a9f6f3cf559d7b4938dcd294ae05e12ccc2484a (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
# Using Docker Containers With TripleO

## Configuring TripleO with to use a container based compute node.

Steps include:
- Adding a base OS image to glance
- Deploy an overcloud configured to use the docker compute heat templates

## Getting base OS image working.

Download the fedora atomic image into glance:

```
wget https://download.fedoraproject.org/pub/fedora/linux/releases/22/Cloud/x86_64/Images/Fedora-Cloud-Atomic-22-20150521.x86_64.qcow2
glance image-create --name atomic-image --file Fedora-Cloud-Atomic-22-20150521.x86_64.qcow2 --disk-format qcow2 --container-format bare
```

## Configuring TripleO

You can use the tripleo.sh script up until the point of running the Overcloud.
https://github.com/openstack/tripleo-common/blob/master/scripts/tripleo.sh

You will want to set up the runtime puppet script delivery system described here:
http://hardysteven.blogspot.ca/2016/08/tripleo-deploy-artifacts-and-puppet.html

Create the Overcloud:
```
$ openstack overcloud deploy --templates=tripleo-heat-templates -e tripleo-heat-templates/environments/docker.yaml -e tripleo-heat-templates/environments/docker-network.yaml --libvirt-type=qemu
```

Using Network Isolation in the Overcloud:
```
$ openstack overcloud deploy --templates=tripleo-heat-templates -e tripleo-heat-templates/environments/docker.yaml -e tripleo-heat-templates/environments/docker-network-isolation.yaml --libvirt-type=qemu
```

Source the overcloudrc and then you can use the overcloud.

## Debugging

You can ssh into the controller/compute nodes by using the heat key, eg:
```
nova list
ssh heat-admin@<compute_node_ip>
```

You can check to see what docker containers are running:
```
sudo docker ps -a
```

To enter a container that doesn't seem to be working right:
```
sudo docker exec -ti <container name> /bin/bash
```

Then you can check logs etc.

You can also just do a 'docker logs' on a given container.
>type: 'irc' agenda: 'https://wiki.opnfv.org/display/functest/Functest+5.+Meeting' url: 'http://ircbot.wl.linuxfoundation.org/meetings/opnfv-functest/' server: 'freenode.net' channel: '#opnfv-meeting' repeats: 'weekly' time: '08:00 UTC' repositories: - 'functest' - 'functest-kubernetes' - 'functest-requirements' - 'functest-xtesting' committers: - <<: *opnfv_functest_ptl - name: 'Morgan Richomme' email: 'morgan.richomme@orange.com' company: 'orange' id: 'mrichomme' timezone: '' - name: 'valentin boucher' email: 'valentin.boucher@kontron.com' company: 'kontron' id: 'boucherv' timezone: '' - name: 'Viktor Tikkanen' email: 'viktor.tikkanen@nokia.com' company: 'nokia' id: 'vitikkan' timezone: '' - name: 'Juha Kosonen' email: 'juha.kosonen@nokia.com' company: 'nokia' id: 'jukosone' timezone: '' - name: 'Linda Wang' email: 'wangwulin@huawei.com' company: 'huawei' id: 'wangwulin' timezone: '' tsc: # yamllint disable rule:line-length approval: 'http//meetbot.opnfv.org/meetings/opnfv-meeting/2015/opnfv-meeting.2015-01-20-14.57.html' # yamllint enable rule:line-length