Juju on Rackspace Cloud Server is a test drive in real time. It is some what like driving a F1 car on a busy avenue for the first time in life. Start the Cloud. And the ride is too without wearing helmet – on an Operating System without any smartness – Windows 7 with PuTTY. We deliberately used Windows as both Mac and Ubuntu PC is configured for Ubuntu Cloud. Otherwise there is no reason to show Juju on Rackspace Cloud Server testdrive on Windows. The peoples will test Juju on Rackspace Cloud Server will obviously use Linux PC, if not Mac.
Juju on Rackspace Cloud Server : History, Geography and Others
History about Juju on Rackspace Cloud Server can be found here. The geography of Juju Package Manager for Cloud Computing configuration is :
We have used Ubuntu 12.04 LTS (Precise Pangolin) with 2048 MB RAM, 80 GB Disk on Chicago (ORD) on Next Generation Server from The Rackspace Cloud. Screen shots are minimum as it is actually for the Advanced Users.
Juju on Rackspace Cloud Server : Test Drive
First I opened the sources.list file with nano :
1 | nano /etc/apt/sources.list |
Uncommented two lines (extra packages) at the end of the list :
The mostly used command :
1 | sudo add-apt-repository ppa:juju/pkgs |
will not work. So to activate sudo add-apt-repository command, use this :
1 | sudo apt-get install python-software-properties |
It worked :
Advertisement ---
I proceeded with pressing the accelerator and honking to add Juju and Charm tools :
1 | sudo apt-get update && sudo apt-get -y install juju charm-tools |
It nicely worked ! Many says Juju on Rackspace Cloud Server does not work. The honk worked !
Now there is a big mob, I have to honk out to proceed faster, we need to edit :
1 | ~/.juju/environments.yaml |
Change directory to :
1 | cd .juju/ |
If you list files using ls command, you will find the environments.yaml file. This is after running this command :
1 | nano environments.yaml |
And here is the document for OpenStack provider :
1 | https://juju.ubuntu.com/docs/provider-configuration-openstack.html |
I have used Chicago (ORD) .
Basic configaration should be like this :
1 2 3 4 5 6 7 8 9 10 | environment: dict deploy: default: type: cloudserversOpenStack provider: rackspace rackspace_username: your_username rackspace_api_key: your_key admin-secreat: (do not change) default-series: precise ssl-hostname-verification: true |
But unfortunately, the point of problem is the environment. With juju status command, it is throwing this error :
environments: expected dict, got dict.
Let us see what can be done with Juju on Rackspace Cloud Server in next time !
