December 2023 - openstack-discuss

[neutron] Bug Deputy Report December 4 - December 10
by Lajos Katona 11 Dec '23

11 Dec '23

Hi Neutrinos, I was the Neutron bug deputy last week, and I send the report of last week's bugs. - High prio bugs - Unassigned: https://bugs.launchpad.net/neutron/+bug/2045549 (OVS jobs randomly fails as Guest VMs not(or delayed) configured with DHCP) - https://bugs.launchpad.net/neutron/+bug/2045725 (scenario jobs randomly fails downloading ubuntu image) - related devstack patch: https://review.opendev.org/c/openstack/devstack/+/901699 - Medium prio bugs: - https://bugs.launchpad.net/neutron/+bug/2045811 (neutron-ovn-db-sync-util can fail with KeyError) - https://review.opendev.org/c/openstack/neutron/+/902841 - https://bugs.launchpad.net/neutron/+bug/2045889 ([OVN] ML2/OVN mech driver does not set the OVS bridge name in the port VIF details) - related mail thread: https://lists.openstack.org/archives/list/openstack-discuss@lists.openstack… - https://bugs.launchpad.net/neutron/+bug/2045950 (Security group performance issue for iptables driver due to "stateless feature") - performance issue with stateless security-groups. Best wishes Lajos Katona (lajoskatona)

1 0

[all] Ussuri and Train EOL
by Elõd Illés 11 Dec '23

11 Dec '23

Hi, With the new TC resolution '2023-07-24 Unmaintained status replaces Extended Maintenance' [1] the last 3 EM branches (Xena, Wallaby, Victoria) will transition to Unmaintained, but older branches (Ussuri, Train) should move to End of Life unless someone steps up as maintainer of this branch for this project. (In that case the branch of that project will transition to unmaintained/{ussuri,train}) To signal this, please add a -1 for the given generated EOL patch [2][3] if you or the team want to keep this branch open for further maintenance. If there is no response from anyone within a reasonable time frame, then PTLs/release liaisons will be asked to confirm the EOL transition with their +1. Thanks, Előd Illés irc: elodilles @ #openstack-stable / #openstack-release [1] https://governance.openstack.org/tc/resolutions/20230724-unmaintained-branc… [2] https://review.opendev.org/q/topic:train-eol [3] https://review.opendev.org/q/topic:ussuri-eol

1 0

[docs]OpenStack compatible list
by steven.wang＠gigacomputing.com 11 Dec '23

11 Dec '23

Hi, For OpenStack compatible check, how should we know the connection with base OS? Example; If the machine support RHEL9 and OpenStack Wallaby, can we say it is compatible to the newest OpenStack than Wallaby? So it should be no problem with Xena, Yoga, Zed, Antelope and Bobcat? Or please kindly let me know where can find the similar document? Thanks. Steven

2 2

System configuration in OpenStack
by lostghost1 10 Dec '23

10 Dec '23

Hi all, Sorry if this has been asked already, but is it feasible to use OpenStack to configure running systems - including virtual instances, containers, and the physical nodes themselves. I know that conceptually OpenStack takes a hands-off approach - it deals with images in abstract and further configuration is delegated to tools such as Ansible. Same for bare metal nodes - you provision them with Ironic, flash an image to them, and that's where configuaration ends for OpenStack. At least this is how I understand it, may be wrong. I was thinking about introducing systems configuration as a first-class concept into OpenStack - that means integration with the package manager, writing of config files from templates, filesystem management in general. The most well thought-out "solution" that there is for systems configuration is Nix in my opinion. I could intergrate it into OpenStack, I could write my own package manager. I haven't decided yet, these are just ideas for a pet project. So if I were to do such a thing, how would I go about achieving it? Obviously I would need to write a Horizon console module for the web UI. But beyond that I'd also need integration with other components. What do you all think?

1 0

Redundancy and high availability of basic services...
by Jorge Visentini 09 Dec '23

09 Dec '23

Hello everybody. I've been studying for some time now, reading official and third-party documentation about deploying and day-to-day maintenance of openstack. What I don't usually read about is the redundancy and high availability of basic services, such as the database, keystone, neutron... I wanted to better understand how it works in a small deployment scenario... I mean... 5 or 10 nodes and 3 controllers, for example... Here we use block storage fiber channel, so we won't use ceph... Of course, I won't implement it in production overnight, but I would like to hahaha but I would like to better understand this part of service redundancy. Thank you all for the emails sent every day. I learn a lot from them. -- Att, Jorge Visentini +55 55 98432-9868

1 0

[all] [ironic] Heads-up: another eventlet-related issue on Stream 8
by Dmitry Tantsur 08 Dec '23

08 Dec '23

Hi stackers, I've noticed this some time ago, but somehow decided that it wouldn't affect OpenStack upstream. Early sign of burn-out? Anyway... Red Hat has fixed CVE 2023-40217 in its Python 3.6 packages (used by default on CentOS Stream 8). Unfortunately, it was done in a way that breaks TLS in eventlet (more details in https://issues.redhat.com/browse/OCPBUGS-20486) It manifests in the following traceback: Traceback (most recent call last): File "/usr/lib64/python3.6/ssl.py", line 754, in __init__ self.getpeername() OSError: [Errno 107] Transport endpoint is not connected During handling of the above exception, another exception occurred: Traceback (most recent call last): <... SNIP ...> File "/usr/lib/python3.6/site-packages/oslo_service/wsgi.py", line 173, in start self.dup_socket = sslutils.wrap(self.conf, self.dup_socket) File "/usr/lib/python3.6/site-packages/oslo_service/sslutils.py", line 104, in wrap return ssl.wrap_socket(sock, **ssl_kwargs) # nosec File "/usr/lib/python3.6/site-packages/eventlet/green/ssl.py", line 422, in wrap_socket return GreenSSLSocket(sock, *a, **kw) File "/usr/lib/python3.6/site-packages/eventlet/green/ssl.py", line 117, in __init__ ca_certs, do_handshake_on_connect and six.PY2, *args, **kw) File "/usr/lib64/python3.6/ssl.py", line 759, in __init__ blocking = (self.gettimeout() != 0) File "/usr/lib/python3.6/site-packages/eventlet/green/ssl.py", line 145, in gettimeout return self._timeout AttributeError: 'GreenSSLSocket' object has no attribute '_timeout' The fix should be rather simple IMO: just remove the condition on Python 2 from here: https://github.com/eventlet/eventlet/blob/master/eventlet/green/ssl.py#L108. But I'm not sure, given the state of eventlet community, we can land anything these. The issue affects, for example. ironic-python-agent on stable/yoga. We're considering our options, the most likely is to use a non-default Python, which is 3.9. Xena and older did not support 3.9, so they're probably out in the cold... Thoughts, ideas? Dmitry

3 5

[goals][kolla][tripleo][all] Migrating from WSGI scripts to module paths
by Stephen Finucane 08 Dec '23

08 Dec '23

o/ For anyone that hasn't been following along, there are changes coming down the line in the Python packaging world that look likely to break pbr's 'wsgi_scripts' entrypoint functionality. As things stand, if we do nothing then at some point these auto-generated scripts will no longer end up in 'bin' when pip installed (as we do with e.g. DevStack). From where I'm standing, we appear to have two options: we can either invest time in pbr to re-implement this functionality from scratch, or we can drop the idea of auto-generating wsgi scripts from our packaging tool and instead start using module paths. Having looked at the former, I suspect it is going to be a *lot* of work that will require implementing our own PEP-517 compatible build backend instead of cribbing setuptools' one as we do now. Personally, I don't think this is a good investment of anyone's time, and it gives us more stuff to maintain for the many years ahead (Did you know that pbr *still* technically supports Python 2. Fun story that). As such, I think we should instead look to the former. I've proposed some patches for Nova [1][2], which I am hoping will provide a blueprint for the other services, and patch for DevStack to enable the new Nova functionality [3]. As you'll see, these patches are relatively small and hopefully easy to grok. The biggest downside I see to this approach is that tooling which deploys Apache+mod_wsgi rather than uWSGI used by e.g. DevStack will need to start packaging their own wsgi script. This is because mod_wsgi does not appear to support configuration by module paths. On the flipside, gunicorn does not support configuration by wsgi script so we get that for free. I would like to hear other's opinions on this approach. As this is something that likely affects all services, I suspect that if there's consensus that this is the correct way to go, there should probably be a small goal drafted for the current cycle. In my opinion, it would be good to do the migration consistently: in nova's case, I have proposed placing wsgi objects in the 'nova.wsgi' module and IMO if all projects could adopt the same convention we would make the lives of our deployment tooling colleagues easier. Please do let me know if you have any questions or concerns. Cheers, Stephen [1] https://review.opendev.org/c/openstack/nova/+/902687/2 [2] https://review.opendev.org/c/openstack/nova/+/902688/2 [3] https://review.opendev.org/c/openstack/devstack/+/902758/1

10 23

[keystone] Reviewathon canceled today
by Dave Wilde 08 Dec '23

08 Dec '23

Hi folks, I'm on PTO today and will be canceling the reviewathon unless someone else would like to run it. The Google Meet link will still work but I won't be there to run the meeting. Thanks! /Dave

1 0

Cyborg nova reports mdev-capable resource is not available
by Karl Kloppenborg 08 Dec '23

08 Dec '23

Hi Cyborg Team! Karl from Helm Team. When creating a VM with the correct flavor, the mdev gets created by cyborg agent and I can see it in the nodedev-list --cap mdev. However Nova then fails with: nova.virt.libvirt.driver [<removed>- - default default] Searching for available mdevs... _get_existing_mdevs_not_assigned /var/lib/openstack/lib/python3.10/site-packages/nova/virt/libvirt/driver.py :8357 2023-09-21 14:34:47.808 1901814 INFO nova.virt.libvirt.driver [<removed> - - default default] Available mdevs at: set(). 2023-09-21 14:34:47.809 1901814 DEBUG nova.virt.libvirt.driver [<removed> - - default default] No available mdevs where found. Creating an new one... _allocate_mdevs /var/lib/openstack/lib/python3.10/site-packages/nova/virt/libvirt/driv er.py:8496 2023-09-21 14:34:47.809 1901814 DEBUG nova.virt.libvirt.driver [<removed> - - default default] Attempting to create new mdev... _create_new_mediated_device /var/lib/openstack/lib/python3.10/site-packages/nova/virt/libvirt/driver.py:8385 2023-09-21 14:34:48.455 1901814 INFO nova.virt.libvirt.driver [<removed> - - default default] Failed to create mdev. No free space found among the following devices: ['pci_0000_4b_03_1', … <truncated list>]. 2023-09-21 14:34:48.456 1901814 ERROR nova.compute.manager [<removed> - - default default] [instance: 2026e2a2-b17a-43ab-adcb-62a907f58b51] Instance failed to spawn: nova.exception.ComputeResourcesUnavailable: Insufficient compute resources: mdev-capable resource is not available. Once this happened, ARQ removes the mdev and cleans up. I’ve got Cyborg 2023.2 running and have a device profile like so: karl@Karls-Air ~ % openstack accelerator device profile show e2b07e11-fe69-4f33-83fc-0f9e38adb7ae +-------------+---------------------------------------------------------------------------+ | Field | Value | +-------------+---------------------------------------------------------------------------+ | created_at | 2023-09-21 13:30:05+00:00 | | updated_at | None | | uuid | e2b07e11-fe69-4f33-83fc-0f9e38adb7ae | | name | VGPU_A40-Q48 | | groups | [{'resources:VGPU': '1', 'trait:CUSTOM_NVIDIA_2235_A40_48Q': 'required'}] | | description | None | +-------------+---------------------------------------------------------------------------+ karl@Karls-Air ~ % I can see the allocation candidate: karl@Karls-Air ~ % openstack allocation candidate list --resource VGPU=1 | grep A40 | 41 | VGPU=1 | 229bf15f-5689-3d2c-b37b-5c8439ea6a71 | VGPU=0/1 | OWNER_CYBORG,CUSTOM_NVIDIA_2235_A40_48Q | karl@Karls-Air ~ % Am I missing something critical here? Because I cannot seem to figure this out… have I got a PCI address wrong, or something? Any help from the Cyborg or Nova teams would be fantastic. Thanks, Karl.

4 9

RE: openstack-discuss Digest, Vol 62, Issue 5 Netwok Configuration Isssue | Urgent
by Asma Naz Shariq 07 Dec '23

07 Dec '23

Hi openstack community, I have deployed Multinode cluster of Openstack through kolla-ansible zed release. The problem I am facing is instances created cannot pick any Ip addresses from the assigned networks which I have created provider and self-service flat network type. Hence, I may not be able to ping and ssh instance from the controller node and these instances won’t be able to connect to the internet. Can anyone guide me how to resolve this issue by pinpointing the initial network configurations settings. -----Original Message----- From: Asma Naz Shariq <asma.naz(a)techavenue.biz> Sent: Wednesday, December 6, 2023 10:42 AM To: 'openstack-discuss(a)lists.openstack.org' <openstack-discuss(a)lists.openstack.org> Subject: RE: openstack-discuss Digest, Vol 62, Issue 5 Netwok Configuration Isssue | Urgent Hi openstack community, I have deployed Multinode cluster of Openstack through kolla-ansible zed release. The problem I am facing is instances created cannot pick any Ip addresses from the assigned networks which I have created provider and self-service flat network type. Hence, I may not be able to ping and ssh instance from the controller node and these instances won’t be able to connect to the internet. Can anyone guide me how to resolve this issue by pinpointing the initial network configurations settings. -----Original Message----- From: openstack-discuss-request(a)lists.openstack.org <openstack-discuss-request(a)lists.openstack.org> Sent: Tuesday, December 5, 2023 9:30 PM To: openstack-discuss(a)lists.openstack.org Subject: openstack-discuss Digest, Vol 62, Issue 5 Send openstack-discuss mailing list submissions to openstack-discuss(a)lists.openstack.org To subscribe or unsubscribe via email, send a message with subject or body 'help' to openstack-discuss-request(a)lists.openstack.org You can reach the person managing the list at openstack-discuss-owner(a)lists.openstack.org When replying, please edit your Subject line so it is more specific than "Re: Contents of openstack-discuss digest..." Today's Topics: 1. Re: [Neutron] - Getting bridge_name of the port from Java sdk (smooney(a)redhat.com) 2. Re: [cinder][nova][glance][ironic] restricting image metadata values to 255 chars (Jorge Merlino) 3. [nova] Spec review day is TOMORROW (Sylvain Bauza) ---------------------------------------------------------------------- Message: 1 Date: Tue, 05 Dec 2023 11:41:06 +0000 From: smooney(a)redhat.com Subject: Re: [Neutron] - Getting bridge_name of the port from Java sdk To: Rodolfo Alonso Hernandez <ralonsoh(a)redhat.com> Cc: Mahudeeswaran Palanisamy <mahudees(a)gmail.com>, openstack-discuss(a)lists.openstack.org Message-ID: <dc8b7b75904590a3124212668e89129080e3aaf9.camel(a)redhat.com> Content-Type: text/plain; charset="UTF-8" On Tue, 2023-12-05 at 11:53 +0100, Rodolfo Alonso Hernandez wrote: > Ok, I'll raise this issue in the Neutron team today during the > networking meeting. just to be clear we have not deprecated the options in nova yet i have been to busy with other work so we wont be removing this in nova in the near term. i may propose a depercation patch depending on your disucssion but we are in no rush. long term however it would be preferabel if neutron alwasy told use what bridge to use and we nolonger had to keep the nova.conf and neutron.conf/ovsdb in sync to have this work. > On Tue, Dec 5, 2023 at 11:45 AM <smooney(a)redhat.com> wrote: > > > On Tue, 2023-12-05 at 09:04 +0100, Rodolfo Alonso Hernandez wrote: > > > Hello Sean: > > > > > > The bridge name in the port VIF details was added for the VLAN > > > aware VMs feature. [1] is the patch adding this functionality in > > > Nova. This is also used with bridge type ports (for hybrid plug). > > yes but we then asked for this to always be set so we coudl > > eventually remove our config options for this. > > > > https://github.com/openstack/neutron/commit/995744c576503b1de90c922d > > becf690ad49f244f > > https://bugs.launchpad.net/neutron/+bug/1788009 > > > > this change is requried to eventualy allow live migration between > > ml2/ovs and ml2/ovn when using vlan networkign > > https://lists.openstack.org/pipermail/openstack-dev/2018-August/1335 > > 46.html > > > > i have 0 time to accutually fix all th things to make that work > > generically sicne that would also like need use to make it work for geneve too. > > > > > But there is no requirement > > > to include the name of the OVS bridge in this dictionary and we > > > are not doing that for any other directly attached ports, not in > > > ML2/OVS nor in ML2/OVN. If Nova requires that, then it should be > > > needed to create an RFE in Neutron to always include it. > > we have discuss this in the past and asked that this alwasy be set > > for ml2/ovn and any other ml2 driver that manage ovs. > > if ml2/ovs does not always set it even when trunk port are not used > > then > > https://bugs.launchpad.net/neutron/+bug/1788009 hwas been regressed > > and we shoudl fix that. > > > > > > Regards. > > > > > > [1]https://review.opendev.org/c/openstack/nova/+/260700 > > > > > > On Mon, Dec 4, 2023 at 6:55 PM <smooney(a)redhat.com> wrote: > > > > > > > On Mon, 2023-12-04 at 16:13 +0100, Rodolfo Alonso Hernandez wrote: > > > > > Hello Mahudeeswaran: > > > > > > > > > > This topic is being discussed in [1]. The patch [2] you are > > referring to > > > > is > > > > > not changing the previous code related to the mentioned > > > > > parameter > > "bridge > > > > > name". Please check [3]. > > > > > > > > > > Also consider that this value was populated when using Trunk > > > > > ports, > > to > > > > > store the Trunk bridge name created on the port description. > > > > > In > > ML2/OVN, > > > > > all ports are attached to the integration bridge (there is a > > > > configuration > > > > > parameter to define the integration name bridge called > > > > > "integration_bridge", that by default is "br-int"). > > > > just to be clear from a nova perspective i would expect the > > > > value to always be populated when ovn binds the prot normally. > > > > > > > > nova may have config options for the default bridge name to use > > > > but we should not be relying on them. so as apart of the ml2/ovs > > > > to ml2/ovn migration the bridge_name > > in > > > > the port binding should get > > > > update to the correct value for the current cloud. > > > > > > > > we have not formally deprcated > > > > > > https://docs.openstack.org/nova/latest/configuration/config.html#neu > > tron.ovs_bridge > > > > but > > > > we likely shold do that now that we can rely on neutron ml2 > > > > backend > > that > > > > supprot ovs always settign this. > > > > > > > > > > > > > > Regards. > > > > > > > > > > [1] > > > > > > > > > > > https://lists.openstack.org/archives/list/openstack-discuss@lists.op > > enstack.org/thread/X4GT7LA523FZWJCGEF2IKTG7VF5WSZWK/ > > > > > [2] > > > > > > > > > > > https://github.com/openstack/neutron/commit/569bafbbd5f90a458d781f1e > > 49f099f96c363683#diff-3fb0e47430c01037fddef45c2ce7314f50a3df5ac41dbd > > 604f9581d90f2985bb > > > > > [3] > > > > > > > > > > > https://github.com/openstack/neutron/commit/569bafbbd5f90a458d781f1e > > 49f099f96c363683#diff-3fb0e47430c01037fddef45c2ce7314f50a3df5ac41dbd > > 604f9581d90f2985bbR33 > > > > > > > > > > > > > > > > > > > > On Mon, Dec 4, 2023 at 3:50 PM Mahudeeswaran Palanisamy < > > > > mahudees(a)gmail.com> > > > > > wrote: > > > > > > > > > > > Hi All, > > > > > > > > > > > > Looks like as part of the below commit, bridge_name info has > > > > > > been removed from port binding vif_details dictionary. Is > > > > > > there any way that we can get the bridge_name info of a port? > > > > > > > > > > > > As far as checked we can get this info by checking if port > > > > > > UUID is part of the “ports” array in “sudo ovs-vsctl list > > > > > > br” output. But there is no equivalent way to get from Java SDK. > > > > > > > > > > > > > > > > > > > > > > > > https://github.com/openstack/neutron/commit/569bafbbd5f90a458d781f1e > > 49f099f96c363683#diff-3fb0e47430c01037fddef45c2ce7314f50a3df5ac41dbd > > 604f9581d90f2985bb > > > > > > > > > > > > Thanks, > > > > > > Mahudees > > > > > > > > > > > > > > > > > > > > > > > > ------------------------------ Message: 2 Date: Tue, 5 Dec 2023 13:27:49 -0300 From: Jorge Merlino <jorge.merlino(a)canonical.com> Subject: Re: [cinder][nova][glance][ironic] restricting image metadata values to 255 chars To: Erno Kuvaja <ekuvaja(a)redhat.com> Cc: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Message-ID: <4da4c94e-81bf-4660-887b-53c2a00e25f4(a)canonical.com> Content-Type: text/plain; charset=UTF-8; format=flowed On 30/11/23 19:34, Erno Kuvaja wrote: > On Thu, 30 Nov 2023 at 20:55, Jorge Merlino > <jorge.merlino(a)canonical.com <mailto:jorge.merlino@canonical.com>> wrote: > > Hello stackers, > > > It has come to our attention recently that nova, cinder, and glance > treat image properties differently. This came up in a discussion on a > patch to extend the allowable length of image metadata values in > cinder [0]. > > > Briefly: > > - glance allows image property values to be unrestricted in the > schema, but effectively limited to 65535 bytes by the database. > > - cinder restricts the length of an image property value to 255 > chars > (by request schema) if you try to update the volume_image_properties on > a volume, but if you create a volume from an image, cinder happily > copies over all the image properties from glance, giving them an > effective limit of 65535 bytes. > > - nova mostly truncates image properties values to 255 chars > (it's a > bit more complicated, but we can consider that to be nova's behavior > for > the purposes of this discussion). > > (We're not sure what ironic does, but they're in the subject line as a > consumer of images and volumes.) > > Note that we're talking about metadata *values* here; the metadata keys > are already restricted by charset to basically US-ASCII and 255 length. > Values are allowed to be unicode. > > The point of this email is that it would be good for the services to be > consistent about image metadata values. Thus, we propose that all > services should restrict image metadata values to 255 unicode > characters. (Which is sort of happening already, but not > consistently.) > > The further point of this email is to find out what the impact of this > restriction would be on current users. So please respond if you have a > use case that would be affected by this change, and could not be > addressed by, for example, instead of having one enormous value for a > single key, the metadata was broken into a number of key/value pairs > that would satisfy the 255 char restriction. > > > Thanks for your attention to this! > > > [0] https://review.opendev.org/c/openstack/cinder/+/868485 > <https://review.opendev.org/c/openstack/cinder/+/868485> > > > Hi Jorge & all, > > To be very frank here, this sounds like a nova problem and your > approach to fix the issue in Cinder seemed to be sensible and > generally accepted there. > > The metadefs basic concepts are explained in [0], Compute defines > subsection of that, all predefined metadefs can be found from [1] > > The very arrogant and false claim from your patch reviews that Nova > would define all image properties and that definition would limit it > to > 255 characters is, well, hilarious. > > Even the field definitions in the code do not specify such max size > for most of those properties Nova _expects_ it might see and knows how > to use, like Sean pointed out, it just happens to be limited how much > of that Nova is able to store in their own database due to the field > restriction at their DB layer. Lots of them properties are things like > booleans or enumerations of values for Nova and thus have practical > limitations. There are also fields like ListOfStrings, no max length > defined. > > Restricting the image properties from all the other consumers because > Nova can't handle storing the copies of them, and thus breaking the > Images API v2 and any use cases that uses image properties outside of > Nova's fairly narrow scope would just be unacceptable. Either Nova > should overcome their internal limitations and figure out how to deal > with the resources or at very least understand to ignore them > properties they have no capacity or interest handling. > > Good luck and thanks for your patience to fight the windmills trying > to get a simple fix in, Erno "jokke" Kuvaja > > [0] > https://docs.openstack.org/glance/latest/user/metadefs-concepts.html > <https://docs.openstack.org/glance/latest/user/metadefs-concepts.html> > [1] https://github.com/openstack/glance/tree/master/etc/metadefs > <https://github.com/openstack/glance/tree/master/etc/metadefs> I'll tend to agree with you, but I see some consistency problems from the user's point of view. For example, if they create a server from an image with long metadata values and then create an image (snapshot) from that server, the new image gets the same metadata parameters as the original image but truncated to 255 chars. Thinking from the perspective of a Openstack user (that does not care what particular service implements what) it would be nice if there was some kind of global policy regarding this. As the shortest length supported right now is nova's, a simple (but maybe not the best?) solution would be to adapt to that length everywhere. Regards Jorge ------------------------------ Message: 3 Date: Tue, 5 Dec 2023 17:21:49 +0100 From: Sylvain Bauza <sbauza(a)redhat.com> Subject: [nova] Spec review day is TOMORROW To: OpenStack Discuss <openstack-discuss(a)lists.openstack.org> Message-ID: <CALOCmumwKP9ifF10P91QZP4AkbyybBZAjnxAPaZCkVW=LHRRzA(a)mail.gmail.com> Content-Type: multipart/alternative; boundary="0000000000005bff15060bc5a231" Hi folks, We'll run our second spec review day tomorrow. Please make sure that your specs are online and in a reviewable state if you want us to look at them. Please also check your Gerrit emails or be around on IRC in case we have any questions. Cores, you know your duty. Thanks, -Sylvain

1 0