<div dir="ltr">I completely agree with you here John. I still prefer to use screen for my devstack installs, it's just far far easier to use for development. systemd is a pain to use in comparison.<div>This is a major step backwards for developers.</div><div><br></div><div>:(</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 7, 2017 at 1:29 PM, John Griffith <span dir="ltr"><<a href="mailto:john.griffith8@gmail.com" target="_blank">john.griffith8@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace">Please don't, some of us have no issues with screen and use it extensively for debugging. Unless there's a viable option using systemd I fail to understand why this is such a big deal. I've been using devstack in screen for a long time without issue, and I still use rejoin that supposedly didn't work (without issue).</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">I completely get the "run like customers" but in theory I'm not sure how screen makes it much different than what customers do, it's executing the same binary at the end of the day. I'd also ask then is devstack no longer "dev" stack, but now a preferred method of install for running production clouds? Anyway, I'd just ask to leave it as an option, unless there's equivalent options for things like using pdb etc. It's annoying enough that we lost that capability for the API services, is there a possibility we can reconsider not allowing this an option?</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">Thanks,</div><div class="gmail_default" style="font-family:monospace,monospace">John</div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Sep 7, 2017 at 7:31 AM, Davanum Srinivas <span dir="ltr"><<a href="mailto:davanum@gmail.com" target="_blank">davanum@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">w00t!<br>
<div class="m_4311149374514741349HOEnZb"><div class="m_4311149374514741349h5"><br>
On Thu, Sep 7, 2017 at 8:45 AM, Sean Dague <<a href="mailto:sean@dague.net" target="_blank">sean@dague.net</a>> wrote:<br>
> On 08/31/2017 06:27 AM, Sean Dague wrote:<br>
>> The work that started last cycle to make devstack only have a single<br>
>> execution mode, that was the same between automated QA and local, is<br>
>> nearing it's completion.<br>
>><br>
>> <a href="https://review.openstack.org/#/c/499186/" rel="noreferrer" target="_blank">https://review.openstack.org/#<wbr>/c/499186/</a> is the patch that will remove<br>
>> screen from devstack (which was only left as a fall back for things like<br>
>> grenade during Pike). Tests are currently passing on all the gating jobs<br>
>> for it. And experimental looks mostly useful.<br>
>><br>
>> The intent is to merge this in about a week (right before PTG). So, if<br>
>> you have a complicated devstack plugin you think might be affected by<br>
>> this (and were previously making jobs pretend to be grenade to keep<br>
>> screen running), now is the time to run tests against this patch and see<br>
>> where things stand.<br>
><br>
> This patch is in the gate and now merging, and with it devstack now has<br>
> a single run mode, using systemd units, which is the same between test<br>
> and development.<br>
><br>
> Thanks to everyone helping with the transition!<br>
><br>
> -Sean<br>
><br>
> --<br>
> Sean Dague<br>
> <a href="http://dague.net" rel="noreferrer" target="_blank">http://dague.net</a><br>
><br>
> ______________________________<wbr>______________________________<wbr>______________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
<br>
<br>
<br>
</div></div><span class="m_4311149374514741349HOEnZb"><font color="#888888">--<br>
Davanum Srinivas :: <a href="https://twitter.com/dims" rel="noreferrer" target="_blank">https://twitter.com/dims</a><br>
</font></span><div class="m_4311149374514741349HOEnZb"><div class="m_4311149374514741349h5"><br>
______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.op<wbr>enstack.org?subject:unsubscrib<wbr>e</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi<wbr>-bin/mailman/listinfo/openstac<wbr>k-dev</a><br>
</div></div></blockquote></div><br></div>
</div></div><br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div>