online Juju Charm Store<\/a> and searching for the charm using the search box in the top left-hand-side of the page. the configuration settings are then detailed under “Configuration” in the main page, as shown:<\/p>\n![\"enter](\"https:\/\/i.stack.imgur.com\/DDbGu.png\")
<\/p>\n
Deploying OpenStack with Juju<\/h2>\n
Now that the configuration is defined, we can use Juju to deploy and relate the services.<\/p>\n
Initialising Juju<\/h3>\n
Juju requires a minimal amount of setup. Here we assume it has already been configured to work with your MAAS cluster (see the [Juju Install Guide][juju_install] for more information on this.<\/p>\n
Firstly, we need to fetch images and tools that Juju will use:<\/p>\n
juju sync-tools --debug\r\n<\/code><\/pre>\nThen we can create the bootstrap instance:<\/p>\n
juju bootstrap --upload-tools --debug\r\n<\/code><\/pre>\nWe use the upload-tools switch to use the local versions of the tools which we just fetched. The debug switch will give verbose output which can be useful. This process may take a few minutes, as Juju is creating an instance and installing the tools. When it has finished, you can check the status of the system with the command:<\/p>\n
juju status\r\n<\/code><\/pre>\nThis should return something like:<\/p>\n
environment: maas\r\nmachines:\r\n \"0\":\r\n agent-state: started\r\n agent-version: 1.18.1.1\r\n dns-name: localhost\r\n instance-id: localhost\r\n series: trusty\r\n<\/code><\/pre>\nDeploy the OpenStack Charms<\/h3>\n
Now that the Juju bootstrap node is up and running we can deploy the services required to make our OpenStack installation. To configure these services properly as they are deployed, we will make use of the configuration file we defined earlier, by passing it along with the --config<\/code> switch with each deploy command. Substitute in the name and path of your config file if different.<\/p>\nIt is useful but not essential to deploy the services in the order below. It is also highly reccommended to open an additional terminal window and run the command juju debug-log<\/code>. This will output the logs of all the services as they run, and can be useful for troubleshooting.<\/p>\nIt is also recommended to run a juju status<\/code> command periodically, to check that each service has been installed and is running properly. Juju will automatically try to fetch the best possible version of the charm from online Charm Store. If you are installing from within a restricted or closed network, it is possible to pre-fetch the required charms. See [the documentation for offline charms][charms-offline].<\/p>\njuju deploy --to=0 juju-gui\r\njuju deploy rabbitmq-server\r\njuju deploy mysql\r\njuju deploy --config openstack-config.yaml openstack-dashboard\r\njuju deploy --config openstack-config.yaml keystone\r\njuju deploy --config openstack-config.yaml ceph -n 3 \r\njuju deploy --config openstack-config.yaml nova-compute -n 3\r\njuju deploy --config openstack-config.yaml quantum-gateway\r\njuju deploy --config openstack-config.yaml cinder\r\njuju deploy --config openstack-config.yaml nova-cloud-controller\r\njuju deploy --config openstack-config.yaml glance\r\njuju deploy --config openstack-config.yaml ceph-radosgw\r\n<\/code><\/pre>\nAdd relations between the OpenStack services<\/h3>\n
Although the services are now deployed, they are not yet connected together. Each service currently exists in isolation. We use the juju add-relation<\/code> command to make them aware of each other and set up any relevant connections and protocols. This extra configuration is taken care of by the individual charms themselves.<\/p>\nWe should start adding relations between charms by setting up the Keystone authorization service and its database, as this will be needed by many of the other connections:<\/p>\n
juju add-relation keystone mysql\r\n<\/code><\/pre>\nWe wait until the relation is set. After it finishes check it with juju status:<\/p>\n
juju status mysql\r\njuju status keystone\r\n<\/code><\/pre>\nIt can take a few moments for this service to settle. Although it is certainly possible to continue adding relations (Juju manages a queue for pending actions) it can be counterproductive in terms of the overall time taken, as many of the relations refer to the same services.<\/p>\n
The following relations also need to be made:<\/p>\n
juju add-relation nova-cloud-controller mysql\r\njuju add-relation nova-cloud-controller rabbitmq-server\r\njuju add-relation nova-cloud-controller glance\r\njuju add-relation nova-cloud-controller keystone\r\njuju add-relation nova-compute mysql\r\njuju add-relation nova-compute rabbitmq-server\r\njuju add-relation nova-compute glance\r\njuju add-relation nova-compute nova-cloud-controller\r\njuju add-relation glance mysql\r\njuju add-relation glance keystone\r\njuju add-relation cinder keystone\r\njuju add-relation cinder mysql\r\njuju add-relation cinder rabbitmq-server\r\njuju add-relation cinder nova-cloud-controller\r\njuju add-relation openstack-dashboard keystone\r\njuju add-relation swift-proxy swift-storage\r\njuju add-relation swift-proxy keystone\r\n<\/code><\/pre>\nFinally, the output of juju status should show the all the relations as complete. The OpenStack cloud is now running, but it needs to be populated with some additional components before it is ready for use.<\/p>\n
<\/p>\n
SOURCE: http:\/\/askubuntu.com\/questions\/78314\/how-do-i-deploy-an-openstack-cloud-with-juju<\/p>\n","protected":false},"excerpt":{"rendered":"
Scope The OpenStack platform is powerful and its uses diverse. This section of documentation is primarily concerned with deploying a “standard” running OpenStack system using, but not limited to, Canonical components such as MAAS, Juju and Ubuntu. Where appropriate other methods and software will be mentioned. Assumptions Use of MAAS – follow these intructions first. Use of Juju Local network configuration – This document assumes that you have an adequate local network configuration, including separate interfaces for access to the…<\/p>\n
Read More Read More<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[11,3],"tags":[],"class_list":["post-487","post","type-post","status-publish","format-standard","hentry","category-openstack","category-virtualization"],"_links":{"self":[{"href":"https:\/\/www.rickyadams.com\/wp\/wp-json\/wp\/v2\/posts\/487","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.rickyadams.com\/wp\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.rickyadams.com\/wp\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.rickyadams.com\/wp\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.rickyadams.com\/wp\/wp-json\/wp\/v2\/comments?post=487"}],"version-history":[{"count":2,"href":"https:\/\/www.rickyadams.com\/wp\/wp-json\/wp\/v2\/posts\/487\/revisions"}],"predecessor-version":[{"id":489,"href":"https:\/\/www.rickyadams.com\/wp\/wp-json\/wp\/v2\/posts\/487\/revisions\/489"}],"wp:attachment":[{"href":"https:\/\/www.rickyadams.com\/wp\/wp-json\/wp\/v2\/media?parent=487"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.rickyadams.com\/wp\/wp-json\/wp\/v2\/categories?post=487"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.rickyadams.com\/wp\/wp-json\/wp\/v2\/tags?post=487"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}