<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">+1 and big thanks for bringing this up!</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">OpenStack Chef will most likely use Ansible as an orchestrator for multi node deployments in the near future and i love the idea about sharing “common configuration options”.</div> <br> <div id="bloop_sign_1489751081340979968" class="bloop_sign"></div> Cheers,<div>Jan<br><p class="airmail_on">On 14 March 2017 at 21:39:19, Emilien Macchi (<a href="mailto:emilien@redhat.com">emilien@redhat.com</a>) wrote:</p> <blockquote type="cite" class="clean_bq"><span><div><div></div><div>OpenStack community has been a welcoming place for Deployment tools.
<br>They bring great value to OpenStack because most of them are used to
<br>deploy OpenStack in production, versus a development environment.
<br>
<br>Over the last few years, deployment tools project have been trying
<br>to solve similar challenges. Recently we've seen some desire to
<br>collaborate, work on common topics and resolve issues seen by all
<br>these tools.
<br>
<br>Some examples of collaboration:
<br>
<br>* OpenStack Ansible and Puppet OpenStack have been collaborating on
<br> Continuous Integration scenarios but also on Nova upgrades orchestration.
<br>* TripleO and Kolla share the same tool for container builds.
<br>* TripleO and Fuel share the same Puppet OpenStack modules.
<br>* OpenStack and Kubernetes are interested in collaborating on configuration
<br> management.
<br>* Most of tools want to collect OpenStack parameters for configuration
<br> management in a common fashion.
<br>* [more]
<br>
<br>The big tent helped to make these projects part of OpenStack, but no official
<br>group was created to share common problems across tools until now.
<br>
<br>During the Atlanta Project Team Gathering in 2017 [1], most of current active
<br>deployment tools project team leaders met in a room and decided to start actual
<br>collaboration on different topics.
<br>This resolution is a first iteration of creating a new working group
<br>for Deployment Tools.
<br>
<br>The mission of the Deployment Working Group would be the following::
<br>
<br> To collaborate on best practices for deploying and configuring OpenStack
<br> in production environments.
<br>
<br>
<br>Note: in some cases, some challenges will be solved by adopting a technology
<br>or a tool. But sometimes, it won't happen because of the deployment tool
<br>background. This group would have to figure out how we can increase
<br>this adoption and converge to the same technologies eventually.
<br>
<br>
<br>For now, we'll use the wiki to document how we work together:
<br>https://wiki.openstack.org/wiki/Deployment
<br>
<br>The etherpad presented in [1] might be transformed in a Wiki page if
<br>needed but for now we expect people to update it.
<br>
<br>[1] https://etherpad.openstack.org/p/deployment-pike
<br>
<br>
<br>Let's make OpenStack deployments better and together ;-)
<br>Thanks,
<br>--
<br>Emilien Macchi
<br>
<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></div></div></span></blockquote></div></body></html>