76c5d9a6c8
This is a complete DNS solution, with hidden master and bind9 slave. It lacks the designate-sink service, because there is no true specification to implement that. It listens for Nova/Neutron events and creates records though adding those to just 1 domain isn't helping much in an environment with multiple tenants. Change-Id: I500fb6058b118d25a4ccfd1d3479830c36af7e2a Blueprint: designate-container |
||
|---|---|---|
| .. | ||
| README.md | ||
| designate.yml | ||
| glance-api-registry.yml | ||
| heat-api-cfn.yml | ||
| heat-api-engine.yml | ||
| horizon.yml | ||
| keystone.yml | ||
| magnum-api-conductor.yml | ||
| mariadb.yml | ||
| neutron-agents.yml | ||
| neutron-server.yml | ||
| nova-api-compute-network.yml | ||
| nova-api-conductor-scheduler-consoleauth-novncproxy.yml | ||
| nova-compute-network.yml | ||
| nova-compute.yml | ||
| rabbitmq.yml | ||
README.md
Docker compose
These scripts and docker compose files can be used to stand up a simple installation of openstack. Running the 'tools/genenv' script creates an 'openstack.env' suitable for running on a single host system as well as an 'openrc' to allow access to the installation.
Once you have run that you can either manually start the containers using the 'docker-compose' command or try the 'tools/kolla start' script which tries to start them all in a reasonable order, waiting at key points for services to become available. Once stood up you can issue the typical openstack commands to use the installation. If using nova networking use:
# source openrc
# tools/init-runonce
# nova boot --flavor m1.medium --key_name mykey --image puffy_clouds instance_name
# ssh cirros@<ip>
Else if using neutron networking use:
# source openrc
# tools/init-runonce
# nova boot --flavor m1.medium --key_name mykey --image puffy_clouds instance_name --nic net-id:<net id>
# ssh cirros@<ip>