[Openstack-sigs] [openstack-dev] [Openstack-operators] [SIGS] Ops Tools SIG

Martin Magr mmagr at redhat.com
Fri Oct 12 09:25:20 UTC 2018


Greetings guys,

On Thu, Oct 11, 2018 at 4:19 PM, Miguel Angel Ajo Pelayo <
majopela at redhat.com> wrote:

> Adding the mailing lists back to your reply, thank you :)
>
> I guess that +melvin.hillsman at huawei.com <melvin.hillsman at huawei.com> can
> help us a little bit organizing the SIG,
> but I guess the first thing would be collecting a list of tools which
> could be published
> under the umbrella of the SIG, starting by the ones already in Osops.
>
> Publishing documentation for those tools, and the catalog under
> docs.openstack.org
> is possibly the next step (or a parallel step).
>
>
> On Wed, Oct 10, 2018 at 4:43 PM Rob McAllister <lawnboy11 at gmail.com>
> wrote:
>
>> Hi Miguel,
>>
>> I would love to join this. What do I need to do?
>>
>> Sent from my iPhone
>>
>> On Oct 9, 2018, at 03:17, Miguel Angel Ajo Pelayo <majopela at redhat.com>
>> wrote:
>>
>> Hello
>>
>>     Yesterday, during the Oslo meeting we discussed [6] the possibility
>> of creating a new Special Interest Group [1][2] to provide home and release
>> means for operator related tools [3] [4] [5]
>>
>>
  all of those tools have python dependencies related to openstack such as
python-openstackclient or python-pbr. Which is exactly the reason why we
moved osops-tools-monitoring-oschecks packaging away from OpsTools SIG to
Cloud SIG. AFAIR we had some issues of having opstools SIG being dependent
on openstack SIG. I believe that Cloud SIG is proper home for tools like
[3][4][5] as they are related to OpenStack anyway. OpsTools SIG contains
general tools like fluentd, sensu, collectd.


Hope this helps,
Martin


>
>>     I continued the discussion with M.Hillsman later, and he made me
>> aware of the operator working group and mailing list, which existed even
>> before the SIGs.
>>
>>     I believe it could be a very good idea, to give life and more
>> visibility to all those very useful tools (for example, I didn't know some
>> of them existed ...).
>>
>>    Give this, I have two questions:
>>
>>    1) Do you know or more tools which could find home under an Ops Tools
>> SIG umbrella?
>>
>>    2) Do you want to join us?
>>
>>
>> Best regards and have a great day.
>>
>>
>> [1] https://governance.openstack.org/sigs/
>> [2] http://git.openstack.org/cgit/openstack/governance-
>> sigs/tree/sigs.yaml
>> [3] https://wiki.openstack.org/wiki/Osops
>> [4] http://git.openstack.org/cgit/openstack/ospurge/tree/
>> [5] http://git.openstack.org/cgit/openstack/os-log-merger/tree/
>> [6] http://eavesdrop.openstack.org/meetings/oslo/
>> 2018/oslo.2018-10-08-15.00.log.html#l-130
>>
>>
>>
>> --
>> Miguel Ángel Ajo
>> OSP / Networking DFG, OVN Squad Engineering
>>
>> _______________________________________________
>> OpenStack-operators mailing list
>> OpenStack-operators at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>
>>
>
> --
> Miguel Ángel Ajo
> OSP / Networking DFG, OVN Squad Engineering
>
> __________________________________________________________________________
> 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
>
>


-- 
Martin Mágr
Senior Software Engineer
Red Hat Czech
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-sigs/attachments/20181012/5b7a7754/attachment-0001.html>


More information about the openstack-sigs mailing list