<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; color: rgb(0, 0, 0); font-size: 14px; font-family: Calibri, sans-serif;">
<div>
<pre style="margin-top: 1.5em; margin-bottom: 1.5em; padding: 0px; border: 0px; font-size: 12px; font-family: 'andale mono', 'lucida console', monospace; vertical-align: baseline; white-space: pre-wrap; line-height: 18.0017986297607px; color: rgb(83, 83, 83); background-color: rgb(255, 255, 255);"><span style="font-weight: bold;">SNIP</span></pre>
<pre style="margin-top: 1.5em; margin-bottom: 1.5em; padding: 0px; border: 0px; font-size: 12px; font-family: 'andale mono', 'lucida console', monospace; vertical-align: baseline; white-space: pre-wrap; line-height: 18.0017986297607px; color: rgb(83, 83, 83); background-color: rgb(255, 255, 255);">Examples of existing repositories which I suspect won't be copied to
osops repository:
* <a href="https://github.com/krislindgren/openstack-logstash/tree/master" style="margin: 0px; padding: 0px; border: 0px; font-style: inherit; font-family: inherit; vertical-align: baseline; color: rgb(188, 21, 24); text-decoration: none;">https://github.com/krislindgren/openstack-logstash/tree/master</a></pre>
</div>
<div>
<div>
<div>Actually, that one has been in the osops repo for a few months. Mike Dorman put it there.</div>
<div><br>
</div>
<div>But, to be fair, I am also worried about fire and forget contributions. </div>
<div><br>
</div>
<div>But I think most of us are solving the same problems and collectively burning time addressing the same issues. I would like to see some collaboration between operators on how builds/maintains/upgrades/monitors their environments. I know the tool chains
wont match up, however most of us are smart enough to take what other people have done and either reverse engineer it or use it as a starting point to make something similar work in our environment. Then hopefully contribute those changes back to the community.
Be that a shell script to do some sort of cleanup, a configuration for stats.d/graphite that gives insight into whats going on in openstack, or a ansible playbook to help automate certain routine tasks.</div>
<div><br>
</div>
<div>Either way as a formal project or just an mailing list and repo to contribute stuff to, I welcome any increase in sharing of code/tools sets/scripts/configs between operators so that we all can at least have a starting point to try and solve the problems
that we face as cloud operators. I personally am rooting for an operator openstack project.</div>
<div>____________________________________________</div>
<div> </div>
<div>Kris Lindgren</div>
<div>Senior Linux Systems Engineer</div>
<div>GoDaddy, LLC.</div>
</div>
<div><br>
</div>
</div>
</body>
</html>