<div dir="ltr">Just a note for reviews... for all OpenStack services, I'm waiting on Juno packages from distributions using systemd before updating service names and start/enable instructions.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Sep 12, 2014 at 10:20 PM, Steve Gordon <span dir="ltr"><<a href="mailto:sgordon@redhat.com" target="_blank">sgordon@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">----- Original Message -----<br>
> From: "Matt Kassawara" <<a href="mailto:mkassawara@gmail.com">mkassawara@gmail.com</a>><br>
> To: "Nicholas Chase" <<a href="mailto:nchase@mirantis.com">nchase@mirantis.com</a>><br>
><br>
> I created a wiki page covering necessary changes (so far) for Juno based on<br>
> a combination of the following:<br>
><br>
> 1) Configuration file changes from the configuration reference.<br>
> 2) Installation of "core" services on Ubuntu using Juno milestone 2<br>
> packages. Both the neutron and nova-network environments appear to work.<br>
> However, the milestone 2 packages don't fully support the [neutron] section<br>
> in nova.conf so the neutron environment uses a mixture of old and new<br>
> locations.<br>
><br>
> Surprisingly, I didn't have to peek at gate configurations for hints. Also,<br>
> I'm still waiting on packages for RH/CentOS/Fedora and hope someone<br>
> familiar with SUSE and Debian can validate these changes well ahead of<br>
> release on 16 October.<br>
<br>
</span>We're currently running CI on M-3 based packages for RDO. Unfortunately there has still been a heavy skew towards feature delivery in the last milestone in Juno (e.g. M-1: 4 blueprints, M-2: 8 blueprints, M-3 26: blueprints in Nova) so I would expect there is quite some potential for change there.<br>
<span class="HOEnZb"><font color="#888888"><br>
-Steve<br>
</font></span></blockquote></div><br></div>