<div dir="ltr"><div dir="ltr"><div dir="ltr">Additional comments in-line.</div><div dir="ltr"><br></div><div>I am open to restructuring things around the tools and repos that they are managed in. As previously mentioned please include me in the list of folks who want to be a part of the team.<br></div><div dir="ltr"><br></div><div dir="ltr">On Tue, Oct 16, 2018 at 8:45 AM Erik McCormick <<a href="mailto:emccormick@cirrusseven.com">emccormick@cirrusseven.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Tue, Oct 16, 2018 at 5:19 AM Miguel Angel Ajo Pelayo<br>
<<a href="mailto:majopela@redhat.com" target="_blank">majopela@redhat.com</a>> wrote:<br>
><br>
> Hi,<br>
><br>
> Matthias and I talked this morning about this topic, and we came to realize<br>
> that there's room for/would be beneficial to have a common place for:<br>
><br>
> a) Documentation about second day operator tools which can be<br>
> useful with OpenStack, links to repositories or availability for every distribution.<br>
><br>
Sounds like a Natural extension to the Ops Guide [1] which we've been<br>
working to return to relevance. I suppose this could also be a wiki<br>
like [2], but we should at least reference it in the guide. In any<br>
event, massive cleanup of old, outdated content really needs to be<br>
undertaken. That should be the other part of the mission I think.<br></blockquote><div><br></div><div><a href="https://wiki.openstack.org/wiki/Operation_Docs_SIG">https://wiki.openstack.org/wiki/Operation_Docs_SIG</a><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> b) Deployment documentation/config snippets/deployment scripts for those tools<br>
> in integration with OpenStack.<br>
><br>
> c) Operator tools and bits which are developed or maintained on OpenStack repos,<br>
> specially the OpenStack related bits of those tools (plugins, etc),<br>
><br>
We should probably try and revive [3] and make use of that more<br>
effectively to address b and c. We've been trying to encourage<br>
contribution to it for years, but it needs more contributors and some<br>
TLC<br></blockquote><div><br></div><div>Ops Tools SIG could facilitate this. Being involved particularly here I think it would be great to have more folks involved and with the addition of OpenLab we have a space to do a bit more around e2e and integration testing of the tools.<br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
> d) Home the organisation of ops-related rooms during OpenStack events, general<br>
> ones related to OpenStack, and also the distro-specific ones for the distros interested<br>
> in participation.<br>
><br>
I'm not exactly sure what you mean by this item. We currently have a<br>
team responsible for meetups and pushing Ops-related content into the<br>
Forum at Summits. Do you propose merging the Ops Meetup Team into this<br>
SIG?<br></blockquote><div><br></div><div>Yes, there is already the Ops Meetup Team which facilitates this and of course anyone is encouraged to join and get involved:</div><div><a href="https://wiki.openstack.org/wiki/Ops_Meetups_Team">https://wiki.openstack.org/wiki/Ops_Meetups_Team</a><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
><br>
> Does this scope for the SIG make sense to everyone willing to participate?<br>
><br>
><br>
> Best regards,<br>
> Miguel Ángel.<br>
><br>
[1] <a href="https://docs.openstack.org/operations-guide/" rel="noreferrer" target="_blank">https://docs.openstack.org/operations-guide/</a><br>
[2] <a href="https://wiki.openstack.org/wiki/Operations" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Operations</a><br>
[3] <a href="https://wiki.openstack.org/wiki/Osops#Code" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Osops#Code</a><br>
<br>
-Erik<br>
<br>
><br>
> On Mon, Oct 15, 2018 at 11:12 AM Matthias Runge <<a href="mailto:mrunge@redhat.com" target="_blank">mrunge@redhat.com</a>> wrote:<br>
>><br>
>> On 12/10/2018 14:21, Sean McGinnis wrote:<br>
>> > On Fri, Oct 12, 2018 at 11:25:20AM +0200, Martin Magr wrote:<br>
>> >> Greetings guys,<br>
>> >><br>
>> >> On Thu, Oct 11, 2018 at 4:19 PM, Miguel Angel Ajo Pelayo <<br>
>> >> <a href="mailto:majopela@redhat.com" target="_blank">majopela@redhat.com</a>> wrote:<br>
>> >><br>
>> >>> Adding the mailing lists back to your reply, thank you :)<br>
>> >>><br>
>> >>> I guess that +<a href="mailto:melvin.hillsman@huawei.com" target="_blank">melvin.hillsman@huawei.com</a> <<a href="mailto:melvin.hillsman@huawei.com" target="_blank">melvin.hillsman@huawei.com</a>> can<br>
>> >>> help us a little bit organizing the SIG,<br>
>> >>> but I guess the first thing would be collecting a list of tools which<br>
>> >>> could be published<br>
>> >>> under the umbrella of the SIG, starting by the ones already in Osops.<br>
>> >>><br>
>> >>> Publishing documentation for those tools, and the catalog under<br>
>> >>> <a href="http://docs.openstack.org" rel="noreferrer" target="_blank">docs.openstack.org</a><br>
>> >>> is possibly the next step (or a parallel step).<br>
>> >>><br>
>> >>><br>
>> >>> On Wed, Oct 10, 2018 at 4:43 PM Rob McAllister <<a href="mailto:lawnboy11@gmail.com" target="_blank">lawnboy11@gmail.com</a>><br>
>> >>> wrote:<br>
>> >>><br>
>> >>>> Hi Miguel,<br>
>> >>>><br>
>> >>>> I would love to join this. What do I need to do?<br>
>> >>>><br>
>> >>>> Sent from my iPhone<br>
>> >>>><br>
>> >>>> On Oct 9, 2018, at 03:17, Miguel Angel Ajo Pelayo <<a href="mailto:majopela@redhat.com" target="_blank">majopela@redhat.com</a>><br>
>> >>>> wrote:<br>
>> >>>><br>
>> >>>> Hello<br>
>> >>>><br>
>> >>>> Yesterday, during the Oslo meeting we discussed [6] the possibility<br>
>> >>>> of creating a new Special Interest Group [1][2] to provide home and release<br>
>> >>>> means for operator related tools [3] [4] [5]<br>
>> >>>><br>
>> >>>><br>
>> >> all of those tools have python dependencies related to openstack such as<br>
>> >> python-openstackclient or python-pbr. Which is exactly the reason why we<br>
>> >> moved osops-tools-monitoring-oschecks packaging away from OpsTools SIG to<br>
>> >> Cloud SIG. AFAIR we had some issues of having opstools SIG being dependent<br>
>> >> on openstack SIG. I believe that Cloud SIG is proper home for tools like<br>
>> >> [3][4][5] as they are related to OpenStack anyway. OpsTools SIG contains<br>
>> >> general tools like fluentd, sensu, collectd.<br>
>> >><br>
>> >><br>
>> >> Hope this helps,<br>
>> >> Martin<br>
>> >><br>
>> ><br>
>> > Hey Martin,<br>
>> ><br>
>> > I'm not sure I understand the issue with these tools have dependencies on other<br>
>> > packages and the relationship to SIG ownership. Is your concern (or the history<br>
>> > of a concern you are pointing out) that the tools would have a more difficult<br>
>> > time if they required updates to dependencies if they are owned by a different<br>
>> > group?<br>
>> ><br>
>> > Thanks!<br>
>> > Sean<br>
>> ><br>
>><br>
>> Hello,<br>
>><br>
>> the mentioned sigs (opstools/cloud) are in CentOS scope and mention<br>
>> repository dependencies. That shouldn't bother us here now.<br>
>><br>
>><br>
>> There is already a SIG under the CentOS project, providing tools for<br>
>> operators[7], but also documentation and integrational bits.<br>
>><br>
>> Also, there is some overlap with other groups and SIGs, such as<br>
>> Barometer[8].<br>
>><br>
>> Since there is already some duplication, I don't know where it makes<br>
>> sense to have a single group for this purpose?<br>
>><br>
>> If that hasn't been clear yet, I'd be absolutely interested in<br>
>> joining/helping this effort.<br>
>><br>
>><br>
>> Matthias<br>
>><br>
>><br>
>><br>
>> [7] <a href="https://wiki.centos.org/SpecialInterestGroup/OpsTools" rel="noreferrer" target="_blank">https://wiki.centos.org/SpecialInterestGroup/OpsTools</a><br>
>> [8] <a href="https://wiki.opnfv.org/collector/pages.action?key=fastpath" rel="noreferrer" target="_blank">https://wiki.opnfv.org/collector/pages.action?key=fastpath</a><br>
>><br>
>> --<br>
>> Matthias Runge <<a href="mailto:mrunge@redhat.com" target="_blank">mrunge@redhat.com</a>><br>
>><br>
>> Red Hat GmbH, <a href="http://www.de.redhat.com/" rel="noreferrer" target="_blank">http://www.de.redhat.com/</a>, Registered seat: Grasbrunn,<br>
>> Commercial register: Amtsgericht Muenchen, HRB 153243,<br>
>> Managing Directors: Charles Cachera, Michael Cunningham,<br>
>> Michael O'Neill, Eric Shander<br>
>><br>
>> _______________________________________________<br>
>> OpenStack-operators mailing list<br>
>> <a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
>> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
><br>
><br>
><br>
> --<br>
> Miguel Ángel Ajo<br>
> OSP / Networking DFG, OVN Squad Engineering<br>
> _______________________________________________<br>
> OpenStack-operators mailing list<br>
> <a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
<br>
_______________________________________________<br>
OpenStack-operators mailing list<br>
<a href="mailto:OpenStack-operators@lists.openstack.org" target="_blank">OpenStack-operators@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators</a><br>
</blockquote></div><br clear="all"><br>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div style="font-size:small"><div dir="ltr"><div dir="ltr">Kind regards,<br><br>Melvin Hillsman</div><div dir="ltr"><a href="mailto:mrhillsman@gmail.com" style="color:rgb(17,85,204)" target="_blank">mrhillsman@gmail.com</a><br>mobile: (832) 264-2646<br></div></div></div></div></div></div></div></div></div></div></div></div>