Replace outdated instruction with link to upstream doc

Beside it's historical value, the instruction in the README-containers
file served no purpose and confused users. Link to upstream
documentation instead.

Change-Id: I86753a613f3d405fc919bb3cc5bd94f29449184d
Martin André 2017-07-10 16:32:58 +02:00
parent 83defdbdbf
commit 910ad64971
1 changed files with 2 additions and 57 deletions

View File

@ -1,58 +1,3 @@
# Using Docker Containers With TripleO
# Containers based OpenStack deployment
## 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:
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 script up until the point of running the Overcloud.
You will want to set up the runtime puppet script delivery system described here:
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.