Open Stack

On 08/30/2018 04:28 PM, Honza Pokorny wrote:
> Hello!
> 
> Over the last few months, it seems that tripleo-quickstart has evolved
> into a CI tool.  It's primarily used by computers, and not humans.
> tripleo-quickstart is a helpful set of ansible playbooks, and a
> collection of feature sets.  However, it's become less useful for
> setting up development environments by humans.  For example, devmode.sh
> was recently deprecated without a user-friendly replacement. Moreover,
> during some informal irc conversations in #oooq, some developers even
> mentioned the plan to merge tripleo-quickstart and tripleo-ci.
> 
> I think it would be beneficial to create a set of defaults for
> tripleo-quickstart that can be used to spin up new environments; a set
> of defaults for humans.  This can either be a well-maintained script in
> tripleo-quickstart itself, or a brand new project, e.g.
> tripleo-quickstart-humans.  The number of settings, knobs, and flags
> should be kept to a minimum.
> 
> This would accomplish two goals:
> 
> 1.  It would bring uniformity to the team.  Each environment is
>     installed the same way.  When something goes wrong, we can
>     eliminate differences in setup when debugging.  This should save a
>     lot of time.
> 
> 2.  Quicker and more reliable environment setup.  If the set of defaults
>     is used by many people, it should container fewer bugs because more
>     people using something should translate into more bug reports, and
>     more bug fixes.
> 
> These thoughts are coming from the context of tripleo-ui development.  I
> need an environment in order to develop, but I don't necessarily always
> care about how it's installed.  I want something that works for most
> scenarios.
> 
> What do you think?  Does this make sense?  Does something like this
> already exist?

Hello,

As an exercise in order to learn a bit more ansible and refresh my
deploy knowledge, I've create that simple thing:
https://github.com/cjeanner/tripleo-lab
It's "more or less generic", but it was probably never deployed outside
my home infra - its aim is to provide a quick'n'dropable libvirt env,
allowing some tweaking in a convenient way.
That's not at quickstart level - but in order to boostrap an undercloud
or a more complete env, it's more than enough.

The other reason I made this was the feeling quickstart is a beast, not
really easy to master - apparently I'm not the only one """fearing""""
it. I probably didn't dig deep enough. And I wanted to get my own thing,
with some proxy/local mirror support in order to alleviate network
traffic on my home line (it's fast, but still... it's faster on the LAN
;) ).

Cheers,

C.

> 
> Thanks for listening!
> 
> Honza
> 
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 

-- 
Cédric Jeanneret
Software Engineer
DFG:DF

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180831/18ba2e90/attachment.sig>