<html><body><div style="font-family: times new roman, new york, times, serif; font-size: 12pt; color: #000000"><div><br></div><div><br></div><hr id="zwchr"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><div dir="ltr"><br><div><br></div><div class="gmail_quote"><div dir="ltr">On Tue, 3 Apr 2018 at 10:00 Javier Pena <<a href="mailto:jpena@redhat.com" target="_blank" data-mce-href="mailto:jpena@redhat.com">jpena@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" data-mce-style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;"><br> > Greeting folks,<br> ><br> > During the last PTG we spent time discussing some ideas around an All-In-One<br> > installer, using 100% of the TripleO bits to deploy a single node OpenStack<br> > very similar with what we have today with the containerized undercloud and<br> > what we also have with other tools like Packstack or Devstack.<br> ><br> > <a href="https://etherpad.openstack.org/p/tripleo-rocky-all-in-one" rel="noreferrer" target="_blank" data-mce-href="https://etherpad.openstack.org/p/tripleo-rocky-all-in-one">https://etherpad.openstack.org/p/tripleo-rocky-all-in-one</a><br> ><br><br> I'm really +1 to this. And as a Packstack developer, I'd love to see this as a<br> mid-term Packstack replacement. So let's dive into the details.<br><br> > One of the problems that we're trying to solve here is to give a simple tool<br> > for developers so they can both easily and quickly deploy an OpenStack for<br> > their needs.<br> ><br> > "As a developer, I need to deploy OpenStack in a VM on my laptop, quickly and<br> > without complexity, reproducing the same exact same tooling as TripleO is<br> > using."<br> > "As a Neutron developer, I need to develop a feature in Neutron and test it<br> > with TripleO in my local env."<br> > "As a TripleO dev, I need to implement a new service and test its deployment<br> > in my local env."<br> > "As a developer, I need to reproduce a bug in TripleO CI that blocks the<br> > production chain, quickly and simply."<br> ><br><br> "As a packager, I want an easy/low overhead way to test updated packages with TripleO bits, so I can make sure they will not break any automation".<br></blockquote><div><br></div><div>I suspect we need to not only update packages, but also update containers, wdyt?</div></div></div></blockquote><div>I'm being implementation-agnostic in my requirement on purpose :). It could be either a new container including the updates, or updating the existing container with the new packages.<br></div><div><br></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;" data-mce-style="border-left: 2px solid #1010FF; margin-left: 5px; padding-left: 5px; color: #000; font-weight: normal; font-style: normal; text-decoration: none; font-family: Helvetica,Arial,sans-serif; font-size: 12pt;"><div dir="ltr"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex" data-mce-style="margin: 0 0 0 .8ex; border-left: 1px #ccc solid; padding-left: 1ex;"><br> > Probably more use cases, but to me that's what came into my mind now.<br> ><br> > Dan kicked-off a doc patch a month ago:<br> > <a href="https://review.openstack.org/#/c/547038/" rel="noreferrer" target="_blank" data-mce-href="https://review.openstack.org/#/c/547038/">https://review.openstack.org/#/c/547038/</a><br> > And I just went ahead and proposed a blueprint:<br> > <a href="https://blueprints.launchpad.net/tripleo/+spec/all-in-one" rel="noreferrer" target="_blank" data-mce-href="https://blueprints.launchpad.net/tripleo/+spec/all-in-one">https://blueprints.launchpad.net/tripleo/+spec/all-in-one</a><br> > So hopefully we can start prototyping something during Rocky.<br> ><br> > Before talking about the actual implementation, I would like to gather<br> > feedback from people interested by the use-cases. If you recognize yourself<br> > in these use-cases and you're not using TripleO today to test your things<br> > because it's too complex to deploy, we want to hear from you.<br> > I want to see feedback (positive or negative) about this idea. We need to<br> > gather ideas, use cases, needs, before we go design a prototype in Rocky.<br> ><br><br> I would like to offer help with initial testing once there is something in the repos, so count me in!<br><br> Regards,<br> Javier<br><br> > Thanks everyone who'll be involved,<br> > --<br> > Emilien Macchi<br> ><br> > __________________________________________________________________________<br> > OpenStack Development Mailing List (not for usage questions)<br> > Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank" data-mce-href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br> > <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" data-mce-href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br><br> __________________________________________________________________________<br> OpenStack Development Mailing List (not for usage questions)<br> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank" data-mce-href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" data-mce-href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br></blockquote></div></div><br>__________________________________________________________________________<br>OpenStack Development Mailing List (not for usage questions)<br>Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe<br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote><div><br></div></div></body></html>