<div dir="ltr">comments inline.<div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Feb 27, 2017 at 9:02 AM, Steven Hardy <span dir="ltr"><<a href="mailto:shardy@redhat.com" target="_blank">shardy@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
Over the recent PTG, and previously at the design summit in Barcelona,<br>
we've had some productive cross-project discussions amongst the various<br>
deployment teams.<br>
<br>
It's clear that we share many common problems, such as patterns for major<br>
version upgrades (even if the workflow isn't identical we've all duplicated<br>
effort e.g around basic nova upgrade workflow recently), container images<br>
and other common building blocks for configuration management.<br>
<br>
Here's a non-exhaustive list of sessions where we had some good<br>
cross-project discussion, and agreed a number of common problems where<br>
collaboration may be possible:<br>
<br>
<a href="https://etherpad.openstack.org/p/ansible-config-mgt" rel="noreferrer" target="_blank">https://etherpad.openstack.<wbr>org/p/ansible-config-mgt</a><br>
<br>
<a href="https://etherpad.openstack.org/p/tripleo-kolla-kubernetes" rel="noreferrer" target="_blank">https://etherpad.openstack.<wbr>org/p/tripleo-kolla-kubernetes</a><br>
<br>
<a href="https://etherpad.openstack.org/p/kolla-pike-ptg-images" rel="noreferrer" target="_blank">https://etherpad.openstack.<wbr>org/p/kolla-pike-ptg-images</a><br>
<br>
<a href="https://etherpad.openstack.org/p/fuel-ocata-fuel-tripleo-integration" rel="noreferrer" target="_blank">https://etherpad.openstack.<wbr>org/p/fuel-ocata-fuel-tripleo-<wbr>integration</a><br>
<br>
If there is interest in continuing the discussions on a more regular basis,<br>
I'd like to propose we start a cross-project working group:<br>
<br>
<a href="https://wiki.openstack.org/wiki/Category:Working_Groups" rel="noreferrer" target="_blank">https://wiki.openstack.org/<wbr>wiki/Category:Working_Groups</a><br>
<br>
If I go ahead and do this is "deployment" a sufficiently project-neutral<br>
term to proceed with?<br>
<br></blockquote><div><br></div><div>WFM. Anything longer such as "openstack-deployment-tools" doesn't show up very well in IRC clients. Forgive the bikeshedding; "openstack-deploy-tools" is very project-neutral and shows up well in IRC clients.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'd suggest we start with an informal WG, which it seems just requires an<br>
update to the wiki, e.g no need for any formal project team at this point?<br>
<br></blockquote><div><br></div><div>WFM. Since we aren't really a project team but a collection of projects working together, I don't think we need further formalization.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Likewise I know some folks have expressed an interest in an IRC channel<br>
(openstack-deployment?), I'm happy to start with the ML but open to IRC<br>
also if someone is willing to set up the channel.<br>
<br></blockquote><div><br></div><div>+1 - I think an IRC channel would be the best way for real time communication.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Perhaps we can start by using the tag "deployment" in all cross-project ML<br>
traffic, then potentially discuss IRC (or even regular meetings) if it<br>
becomes apparrent these would add value beyond ML discussion?<br>
<br></blockquote><div><br></div><div>[deploy-tools] may be better unless that breaks people's email clients.</div><div><br></div><div>I am out of bandwidth personally for meetings, although others may be interested in a meeting. I'm not sure what value a regular meeting would have and would need a chair, which may result in an inability to obtain neutral ground.</div><div><br></div><div>IMO IRC and ML would be sufficient for this CP effort, however others may have different viewpoints.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Please follow up here if anyone has other/better ideas on how to facilitate<br>
ongoing cross-team discussion and I'll do my best to help move things<br>
forward.<br>
<br></blockquote><div><br></div><div>Sounds good to me. Waiting 3 months to see everyone face to face to discuss cross-project deployment tool collaboration doesn't seem ideal.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks!<br>
<br>
Steve<br>
<br>
______________________________<wbr>______________________________<wbr>______________<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">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
</blockquote></div><br></div></div></div>