<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Feb 18, 2015 at 6:18 AM, Matt Riedemann <span dir="ltr"><<a href="mailto:mriedem@linux.vnet.ibm.com" target="_blank">mriedem@linux.vnet.ibm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5"><br>
<br>
On 2/16/2015 9:57 PM, Jay Pipes wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Mikal, sorry for top-posting. What was the final decision regarding<br>
the instance tagging work?<br>
<br>
Thanks,<br>
-jay<br>
<br>
On 02/16/2015 09:44 PM, Michael Still wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
<br>
we had a meeting this morning to try and work through all the FFE<br>
requests for Nova. The meeting was pretty long -- two hours or so --<br>
and we did in in the nova IRC channel in an attempt to be as open as<br>
possible. The agenda for the meeting was the list of FFE requests at<br>
<a href="https://etherpad.openstack.org/p/kilo-nova-ffe-requests" target="_blank">https://etherpad.openstack.<u></u>org/p/kilo-nova-ffe-requests</a><br>
<br>
I recognise that this process is difficult for all, and that it is<br>
frustrating when your FFE request is denied. However, we have tried<br>
very hard to balance distractions from completing priority tasks and<br>
getting as many features into Kilo as possible. I ask for your<br>
patience as we work to finalize the Kilo release.<br>
<br>
That said, here's where we ended up:<br>
<br>
Approved:<br>
<br>
vmware: ephemeral disk support<br>
API: Keypair support for X509 public key certificates<br>
<br>
We were also presented with a fair few changes which are relatively<br>
trivial (single patch, not very long) and isolated to a small part of<br>
the code base. For those, we've selected the ones with the greatest<br>
benefit. These ones are approved so long as we can get the code merged<br>
before midnight on 20 February 2015 (UTC). The deadline has been<br>
introduced because we really are trying to focus on priority work and<br>
bug fixes for the remainder of the release, so I want to time box the<br>
amount of distraction these patches cause.<br>
<br>
Those approved in this way are:<br>
<br>
ironic: Pass the capabilities to ironic node instance_info<br>
libvirt: Nova vif driver plugin for opencontrail<br>
libvirt: Quiescing filesystems with QEMU guest agent during image<br>
snapshotting<br>
libvirt: Support vhost user in libvirt vif driver<br>
libvirt: Support KVM/libvirt on System z (S/390) as a hypervisor<br>
platform<br>
<br>
It should be noted that there was one request which we decided didn't<br>
need a FFE as it isn't feature work. That may proceed:<br>
<br>
hyperv: unit tests refactoring<br>
<br>
Finally, there were a couple of changes we were uncomfortable merging<br>
this late in the release as we think they need time to "bed down"<br>
before a release we consider stable for a long time. We'd like to see<br>
these merge very early in Liberty:<br>
<br>
libvirt: use libvirt storage pools<br>
libvirt: Generic Framework for Securing VNC and SPICE<br>
Proxy-To-Compute-Node Connections<br>
<br>
Thanks again to everyone with their patience with our process, and<br>
helping to make Kilo an excellent Nova release.<br>
<br>
Michael<br>
<br>
</blockquote>
<br>
______________________________<u></u>______________________________<u></u>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.<u></u>openstack.org?subject:<u></u>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
<br>
</blockquote>
<br></div></div>
There are notes in the etherpad,<br>
<br>
<a href="https://etherpad.openstack.org/p/kilo-nova-ffe-requests" target="_blank">https://etherpad.openstack.<u></u>org/p/kilo-nova-ffe-requests</a><br>
<br>
but I think we wanted to get cyeoh and Ken'ichi's thoughts on the v2 and/or v2.1 question about the change, i.e. should it be v2.1 only with microversions or if that is going to block it, is it fair to keep out the v2 change that's already in the patch?<span class="HOEnZb"><font color="#888888"><br>
<br></font></span></blockquote><div><br></div><div>So if it can be fully merged by end of week I'm ok with it going into v2 and v2.1. Otherwise I think it needs to wait for microversions. I'd like to see v2.1 enabled next Monday (I don't want it go in just before a weekend). And the first microversion change (which is ready to go) a couple of days after). And we want a bit of an API freeze while that is happening.</div><div><br></div><div>Chris</div><div><br></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="HOEnZb"><font color="#888888">
-- <br>
<br>
Thanks,<br>
<br>
Matt Riedemann</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
<br>
______________________________<u></u>______________________________<u></u>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.<u></u>openstack.org?subject:<u></u>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/<u></u>cgi-bin/mailman/listinfo/<u></u>openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>