kolla/compose/nova-compute-network.yml
Steven Dake f4fd47dc2c Make nova-compute-network use a data volume container
A data volume container is far superior to bind mounting the
host's shared directories.  It preserves the idempotency,
immutability and declarative properties of the containers.

The way this works in practice is that a data volume container is
created.  Then when the containers start they use LVM to access
the filesystem where /var/lib/docker is contained.  Then the
container startup logic bindmounts the data volume stored on the
host filesystem in /var/lib/docker/vfs/dir/ID.  This prevents
people with access to the host operating system from damaging
the contents of the data container.

It does mean that now we must use tools/stop to stop our containers
rather than tools/cleanup-containers -f.

This is a containers best practice.  For more details see:

https://docs.docker.com/userguide/dockervolumes/

Big credit goes to Danyeon Hansen for seeding this idea in the
mariadb containers.

Note occasionally docker-compose start/stop seems to not want to stop
a container.  This bug needs to be addressed upstream separately
from our utilization of this best practice.

Change-Id: Iaa1419f606e1b1b7a7560a095c49e79d643164f1
2015-03-22 08:54:53 -07:00

47 lines
879 B
YAML

computedata:
image: kollaglue/centos-rdo-nova-compute-data
name: computedata
libvirt:
image: kollaglue/centos-rdo-nova-libvirt
name: libvirt
net: host
pid: host
privileged: true
restart: always
env_file:
- openstack.env
volumes:
- /run:/run
- /sys/fs/cgroup:/sys/fs/cgroup
volumes_from:
- computedata
novanetwork:
image: kollaglue/centos-rdo-nova-network
name: nova-network
net: host
privileged: true
restart: always
env_file:
- openstack.env
volumes:
- /run:/run
- /sys/fs/cgroup:/sys/fs/cgroup
volumes_from:
- computedata
novacompute:
image: kollaglue/centos-rdo-nova-compute
name: nova-compute
net: host
privileged: true
restart: always
env_file:
- openstack.env
volumes:
- /run:/run
- /sys/fs/cgroup:/sys/fs/cgroup
volumes_from:
- computedata