Hello,
I would like to re-iterate my interest in having a SIG in CentOS to provide all kinds of tools for operators providing infrastructure by using CentOS.
The scope should be more than just simply packaging applications. Another part should be to provide puppet manifests or ansible playbooks to get things quicker up and running.
Ideally, I would start with providing something like * elsasticsearch/fluentd/kibana for centralised logging * collectd/graphite/grafana for performance monitoring * sensu/uchiwa for availability monitoring
We have already seen around 10 persons interested in helping, testing, trying out and providing feedback.
For communcations etc. I would propose to start small, and to share already existent CentOS channels (email-lists, irc-channel). This decision should be revisited, once amount of SIG related communication becomes annoying in general channels.
Questions? Thoughts? Additions?
Best, Matthias
On 05/13/2016 01:12 AM, Matthias Runge wrote:
Hello,
I would like to re-iterate my interest in having a SIG in CentOS to provide all kinds of tools for operators providing infrastructure by using CentOS.
+1
The scope should be more than just simply packaging applications. Another part should be to provide puppet manifests or ansible playbooks to get things quicker up and running.
+1 - should ideally provide a standalone installer, and puppet manifests/ansible playbooks that can be included in other projects (puppet manifests for RDO TripleO, ansible playbooks for openshift-ansible, etc.)
Ideally, I would start with providing something like
- elsasticsearch/fluentd/kibana for centralised logging
+1
- collectd/graphite/grafana for performance monitoring
- sensu/uchiwa for availability monitoring
We have already seen around 10 persons interested in helping, testing, trying out and providing feedback.
For communcations etc. I would propose to start small, and to share already existent CentOS channels (email-lists, irc-channel).
Emails should use the [opstools] prefix?
This decision should be revisited, once amount of SIG related communication becomes annoying in general channels.
Questions? Thoughts? Additions?
Best, Matthias
On 13/05/16 08:12, Matthias Runge wrote:
Hello,
I would like to re-iterate my interest in having a SIG in CentOS to provide all kinds of tools for operators providing infrastructure by using CentOS.
The scope should be more than just simply packaging applications. Another part should be to provide puppet manifests or ansible playbooks to get things quicker up and running.
Ideally, I would start with providing something like
- elsasticsearch/fluentd/kibana for centralised logging
- collectd/graphite/grafana for performance monitoring
- sensu/uchiwa for availability monitoring
We have already seen around 10 persons interested in helping, testing, trying out and providing feedback.
For communcations etc. I would propose to start small, and to share already existent CentOS channels (email-lists, irc-channel). This decision should be revisited, once amount of SIG related communication becomes annoying in general channels.
Questions? Thoughts? Additions?
Best, Matthias
how much of this overlaps with the config management SIG ?
On 24/05/16 15:20, Karanbir Singh wrote:
On 13/05/16 08:12, Matthias Runge wrote:
Hello,
I would like to re-iterate my interest in having a SIG in CentOS to provide all kinds of tools for operators providing infrastructure by using CentOS.
The scope should be more than just simply packaging applications. Another part should be to provide puppet manifests or ansible playbooks to get things quicker up and running.
Ideally, I would start with providing something like
- elsasticsearch/fluentd/kibana for centralised logging
- collectd/graphite/grafana for performance monitoring
- sensu/uchiwa for availability monitoring
We have already seen around 10 persons interested in helping, testing, trying out and providing feedback.
For communcations etc. I would propose to start small, and to share already existent CentOS channels (email-lists, irc-channel). This decision should be revisited, once amount of SIG related communication becomes annoying in general channels.
Questions? Thoughts? Additions?
Best, Matthias
how much of this overlaps with the config management SIG ?
I would state, it doesn't overlap, which is not *entirely* true. Opstools SIG could provide scripts/configs to the other SIG. At least both should cooperate on getting things installed.
Best, Matthias
I'm interested in contributing to this SIG.
Cheers, Adam
On Tue, May 24, 2016 at 2:48 PM, Matthias Runge mrunge@matthias-runge.de wrote:
On 24/05/16 15:20, Karanbir Singh wrote:
On 13/05/16 08:12, Matthias Runge wrote:
Hello,
I would like to re-iterate my interest in having a SIG in CentOS to provide all kinds of tools for operators providing infrastructure by using CentOS.
The scope should be more than just simply packaging applications. Another part should be to provide puppet manifests or ansible playbooks to get things quicker up and running.
Ideally, I would start with providing something like
- elsasticsearch/fluentd/kibana for centralised logging
- collectd/graphite/grafana for performance monitoring
- sensu/uchiwa for availability monitoring
We have already seen around 10 persons interested in helping, testing, trying out and providing feedback.
For communcations etc. I would propose to start small, and to share already existent CentOS channels (email-lists, irc-channel). This decision should be revisited, once amount of SIG related communication becomes annoying in general channels.
Questions? Thoughts? Additions?
Best, Matthias
how much of this overlaps with the config management SIG ?
I would state, it doesn't overlap, which is not *entirely* true. Opstools SIG could provide scripts/configs to the other SIG. At least both should cooperate on getting things installed.
Best, Matthias _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 05/24/2016 07:48 AM, Matthias Runge wrote:
On 24/05/16 15:20, Karanbir Singh wrote:
On 13/05/16 08:12, Matthias Runge wrote:
Hello,
I would like to re-iterate my interest in having a SIG in CentOS to provide all kinds of tools for operators providing infrastructure by using CentOS.
The scope should be more than just simply packaging applications. Another part should be to provide puppet manifests or ansible playbooks to get things quicker up and running.
Ideally, I would start with providing something like
- elsasticsearch/fluentd/kibana for centralised logging
- collectd/graphite/grafana for performance monitoring
- sensu/uchiwa for availability monitoring
We have already seen around 10 persons interested in helping, testing, trying out and providing feedback.
For communcations etc. I would propose to start small, and to share already existent CentOS channels (email-lists, irc-channel). This decision should be revisited, once amount of SIG related communication becomes annoying in general channels.
Questions? Thoughts? Additions?
Best, Matthias
how much of this overlaps with the config management SIG ?
I would state, it doesn't overlap, which is not *entirely* true. Opstools SIG could provide scripts/configs to the other SIG. At least both should cooperate on getting things installed.
Right. I think tools like fluentd, elasticsearch, kibana, etc. don't overlap with config, and we will work with the Config SIG on configuration management best practices for the OpsTools SIG packages.
Best, Matthias _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 27/05/16 22:49, Rich Megginson wrote:
how much of this overlaps with the config management SIG ?
I would state, it doesn't overlap, which is not *entirely* true. Opstools SIG could provide scripts/configs to the other SIG. At least both should cooperate on getting things installed.
Right. I think tools like fluentd, elasticsearch, kibana, etc. don't overlap with config, and we will work with the Config SIG on configuration management best practices for the OpsTools SIG packages.
Any other comments, remarks, questions here?
Matthias