Juju for Deployment on Rackspace OpenStack

Juju for Deployment on Rackspace OpenStack demand configarations.yml file. Many asks us for Rackspace OpenStack Juju guide, as we have shown before – it is yet not available. You can see the article where we have shown the test drive with Juju on Rackspace Cloud Server. Here are some mentions, some reasons why we and all are looking for the support or rather want Juju for Deployment on Rackspace OpenStack.

Juju for Deployment on Rackspace OpenStack : Why The Heck We Need it?

If you point your browser to :

and do a Try with various configurations, you will understand how easy it is to configure the Open to Public deployments – it is just GUI based excellent drive. You can see this video for the usage :

Obviously, it is not Rackspace.

Juju for Deployment on Rackspace OpenStack : Why The Problem is Present

Why Juju for Deployment on Rackspace OpenStack is not possible is difficult to answer – definitely the authentication part creates the issue, however it is abnormal that Rackspace being the Pioneer of OpenStack can not solve it months after months. Most of us are very long loyal premium customers of Rackspace, honestly the support and Rackspace is more than what can be expected. There is open suggestion too, please vote it :

and latest at the time of writing this article :

Wrongly written for Rackspace :

By the way, we are talking about Public Cloud, not baremetal, Co-location or even Dedicated configurations. May be some security settings from networking level blocks the authentication (it is likely, search with Richard Stallman+Ubuntu on YouTube to get an idea about Ubuntu aka Canonical – their desktop OS does a kind of spyware work). So, Rackspace might not be blamed directly. However, the newly introduced Rackspace Deployments although not like Juju but has the easiness to work fast.

What we want to say is – do not wast time behind Juju for Deployment on Rackspace OpenStack configuration. All of us have enough experience of working with UNIX and Networking and all of us failed multiple times, its unlikely that you can configure properly. However if you can fix, please let us know and give the configarations.xml file as Gist on GitHub.