Implementing a Basic Openstack Cloud

Implementing a Basic Openstack Cloud

OpenStack is an open source IaaS type cloud computing solution. Its mission is to provide a flexible solution for both public and private clouds, whether of any size, and for this, two basic requirements are considered: clouds must be simple to implement and massively scalable. In this case, we have used a bundle provided by Canonical that installs Openstack Cloud (Release Liberty) on Ubuntu 14LTS to implement Dashboard, Compute, Network, Block Storage, Object Storage, Identity and Images services. The original bundle plans to provision physical machines using MAAS or physical resources from a public cloud, we have adapted the deployment so that we can use virtual machines in a VMWare vCloud environment. The components are distributed as follows.

  • A node for Neutron Gateway and Ceph, RabbitMQ and MySQL in lightweight containers.
  • Three nodes for Nova and Ceph with Keystone, Glance, Neutron, Nova, Cinder, Horizon, etc. In light containers.

Here is the script:












References for each command
1. We install the main Juju package, Juju is an orchestration tool, see:
2. We delete any packages we won’t need.
3. With this command, we see the state of the Juju boot environment, in this case we hope we will not find any started environment.
4. We add a key to install Chrome in the server environment
5. We add the Chrome repository to the local server repository
6. Report to the server about the new component in the repository.
7. We install Chrome
8. We add Chrome to the deployment user’s path (/ opt / google / Chrome)
9. We generate the boot configuration of juju, write files in the .juju directory
10. By default juju directs its orchestration elements to Amazon, in this case we move to a manual and local environment
11. Run the juju environment boot
12. We add by hand three servers (demo7, demo10 and demo11) that join demo4. In this case it is a manual process, for each user Ubuntu executed the command “ssh-copy-id ubuntu @ <host>”. Additionally a line was modified in / etc / sudoers to contain this configuration “% sudo ALL = (ALL: ALL) NOPASSWD: ALL”
13. The bundle is deployed with the command juju quickstart, because we found a bug in the command we downloaded it from launchpad directly.
14. Run the cloud deployment, the bundle is here:

Credentials to access the orchestration tool.

Juju GUI URL: https://demo6

username: admin

password: -encripted-

A screen of this type should be displayed:

Equipment and containers


By Uniqs

Dejá un comentario

Tu dirección de correo electrónico no será publicada. Los campos necesarios están marcados *