[openstack-dev] [tripleo] PTG session about All-In-One installer: recap & roadmap

Paul Grist pgrist at redhat.com
Fri Mar 30 12:44:33 UTC 2018

On Thu, Mar 29, 2018 at 5:32 PM, Emilien Macchi <emilien at redhat.com> wrote:

> Greeting folks,
> During the last PTG we spent time discussing some ideas around an
> All-In-One installer, using 100% of the TripleO bits to deploy a single
> node OpenStack very similar with what we have today with the containerized
> undercloud and what we also have with other tools like Packstack or
> Devstack.
> https://etherpad.openstack.org/p/tripleo-rocky-all-in-one
> One of the problems that we're trying to solve here is to give a simple
> tool for developers so they can both easily and quickly deploy an OpenStack
> for their needs.
> Big +1 on the concept,  thanks to all those putting effort into this.

> "As a developer, I need to deploy OpenStack in a VM on my laptop, quickly
> and without complexity, reproducing the same exact same tooling as TripleO
> is using."
> "As a Neutron developer, I need to develop a feature in Neutron and test
> it with TripleO in my local env."
> "As a TripleO dev, I need to implement a new service and test its
> deployment in my local env."
> "As a developer, I need to reproduce a bug in TripleO CI that blocks the
> production chain, quickly and simply."
Would this also be an opportunity for CI to enable lighter weight sanity
and preliminary tests?
"As a project, I want to implement a TripleO CI gate to detect regressions
early, but have resource and test execution time constraints"

> Probably more use cases, but to me that's what came into my mind now.
> Dan kicked-off a doc patch a month ago: https://review.openstack.org/#
> /c/547038/
> And I just went ahead and proposed a blueprint:
> https://blueprints.launchpad.net/tripleo/+spec/all-in-one
> So hopefully we can start prototyping something during Rocky.
> Before talking about the actual implementation, I would like to gather
> feedback from people interested by the use-cases. If you recognize yourself
> in these use-cases and you're not using TripleO today to test your things
> because it's too complex to deploy, we want to hear from you.
> I want to see feedback (positive or negative) about this idea. We need to
> gather ideas, use cases, needs, before we go design a prototype in Rocky.
> Thanks everyone who'll be involved,
> --
> Emilien Macchi
> __________________________________________________________________________
> 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180330/ce0f85b9/attachment.html>

More information about the OpenStack-dev mailing list