openstack team mailing list archive

["Debo Dutta (dedutta)" <dedutta@xxxxxxxxx>]

Then you might want to start with some of the chef cookbooks people use.
Ask Jay Pipes, he was planning to consolidate them!

debo

-----Original Message-----
From: Aniruddha Khadkikar [mailto:askhadkikar@xxxxxxxxx] 
Sent: Wednesday, March 14, 2012 9:37 PM
To: Debo Dutta (dedutta)
Cc: openstack@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openstack] User experience and simplified configurations

On Thu, Mar 15, 2012 at 9:46 AM, Debo Dutta (dedutta)
<dedutta@xxxxxxxxx> wrote:
>
> Have you tinkered with devstack .... Its simplifies some of the issues
you
> raised for a dev guy.

No, I have not used Devstack as the purpose is to simulate a close to
production type POC and not a deployment on a single machine. Also we
wanted
to go through the documentation in detail to increase our understanding
of the
platform and implement the steps manually.

Regards,
Aniruddha

>
>
>
> From: openstack-bounces+dedutta=cisco.com@xxxxxxxxxxxxxxxxxxx
> [mailto:openstack-bounces+dedutta=cisco.com@xxxxxxxxxxxxxxxxxxx] On
Behalf
> Of Aniruddha Khadkikar
> Sent: Wednesday, March 14, 2012 9:03 PM
> To: openstack@xxxxxxxxxxxxxxxxxxx
> Subject: [Openstack] User experience and simplified configurations
>
>
>
> Hi,
>
> Its only recently that I have started exploring openstack and the
first
> thing that comes to my mind is the nature and amount of configuration
> required for the various components.
> The managed IT Deb packages for Diablo were very helpful in reaching a
poc
> level implementation involving a separate cloud controller, volume and
> glance with swift and with a compute node.
>
> Are there any plans to simplify the configuration files and develop
> command line wizards for a better user experience?
>
> I believe that with every release an incrementally better experience
will
> help in greater adoption of the platform. For example I could only get
> things working on my third trial. That too led to problems due to EC2
not
> working till a project was added using nova manage. I still remain
confused
> between tenants and projects in Diablo. Logically one customer
(tenant)
> should be able to run multiple projects. So I was a bit surprised at
them
> being treated as equivalent.
>
> First target for simplification could be the various pipeline settings
and
> the nova configuration. I have found these a bit complicated to
understand.
>
> I have not started testing Essex yet.
>
> Regards
> Aniruddha