<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Apr 5, 2017 at 9:14 PM Sean Dague <<a href="mailto:sean@dague.net">sean@dague.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">At the PTG clayg brought up an excellent question about what the<br class="gmail_msg">
expected flow was to restart a bunch of services in devstack after a<br class="gmail_msg">
code changes that impacts many of them (be it common code, or a<br class="gmail_msg">
library). People had created a bunch of various screen hacks over the<br class="gmail_msg">
years, but screen is flakey, and this is definitely not an ideal workflow.<br class="gmail_msg">
<br class="gmail_msg">
Over lunch clayg, clarkb, and I chatted about some options. Clark<br class="gmail_msg">
brought up the idea of doing systemd units for all of the services. A<br class="gmail_msg">
couple of weeks ago I decided it was time for me to understand systemd<br class="gmail_msg">
better anyway, and started playing around with what this might look like.<br class="gmail_msg">
<br class="gmail_msg">
The results landed here <a href="https://review.openstack.org/#/c/448323/" rel="noreferrer" class="gmail_msg" target="_blank">https://review.openstack.org/#/c/448323/</a>.<br class="gmail_msg">
Documentation is here<br class="gmail_msg">
<a href="http://git.openstack.org/cgit/openstack-dev/devstack/tree/SYSTEMD.rst" rel="noreferrer" class="gmail_msg" target="_blank">http://git.openstack.org/cgit/openstack-dev/devstack/tree/SYSTEMD.rst</a><br class="gmail_msg">
<br class="gmail_msg">
This is currently an opt in. All the services in base devstack however<br class="gmail_msg">
do work in this new model, and I and a few others have been using this<br class="gmail_msg">
mode the last week or so. It's honestly really great. Working on<br class="gmail_msg">
oslo.log changes it's now:<br class="gmail_msg">
<br class="gmail_msg">
pip install -U .<br class="gmail_msg">
sudo systemctl restart devstack@*<br class="gmail_msg">
<br class="gmail_msg">
And the change is now in all your services.<br class="gmail_msg">
<br class="gmail_msg">
There is also an oslo.log change for native systemd journal support<br class="gmail_msg">
(<a href="https://review.openstack.org/#/c/451525/" rel="noreferrer" class="gmail_msg" target="_blank">https://review.openstack.org/#/c/451525/</a>), which once that has landed<br class="gmail_msg">
and been released, will let us do some neat query of the journal during<br class="gmail_msg">
development to see slices across services like this<br class="gmail_msg">
<a href="https://dague.net/2017/03/30/in-praise-of-systemd/" rel="noreferrer" class="gmail_msg" target="_blank">https://dague.net/2017/03/30/in-praise-of-systemd/</a>.<br class="gmail_msg"></blockquote><div><br></div><span style="font-size:13px">I just want to say thank you! to you clarkb clayg and everyone involved :)</span><div style="font-size:13px">This is so much better!</div><div style="font-size:13px"><br></div><div><span style="font-size:13px">andreaf</span> </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="gmail_msg">
ACTION REQUIRED:<br class="gmail_msg">
<br class="gmail_msg">
If you maintain a devstack plugin that starts any services, now would be<br class="gmail_msg">
a great time to test to see if this works for them. The biggest issue is<br class="gmail_msg">
that the commands sent to run_process need to be absolute pathed.<br class="gmail_msg">
<br class="gmail_msg">
<br class="gmail_msg">
My hope is that by end of cycle this is going to be the default mode in<br class="gmail_msg">
devstack for *both* the gate and development, which eliminates one major<br class="gmail_msg">
difference between the two. I'm also hoping that we'll be able to keep<br class="gmail_msg">
and archive the journals from the runs, so you can download and query<br class="gmail_msg">
those directly. Especially once the oslo.log enhancements are there to<br class="gmail_msg">
add the additional structured data.<br class="gmail_msg">
<br class="gmail_msg">
-Sean<br class="gmail_msg">
<br class="gmail_msg">
--<br class="gmail_msg">
Sean Dague<br class="gmail_msg">
<a href="http://dague.net" rel="noreferrer" class="gmail_msg" target="_blank">http://dague.net</a><br class="gmail_msg">
<br class="gmail_msg">
__________________________________________________________________________<br class="gmail_msg">
OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" class="gmail_msg" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="gmail_msg">
</blockquote></div></div>