January 2019 - openstack-discuss - lists.openstack.org

[neutron][python3] Help needed
by Slawomir Kaplonski 21 Jan '19

21 Jan '19

Hi, Since some time we are trying to move our neutron-functional job to be run with python 3 - see patch [1]. Unfortunately we are still hitting same issue, some subunit parser error with message like "Parser Error: {{{Short read - got 4090 bytes, wanted 4376 bytes}}}”. See for example here: [2]. That cause that only around half of tests are executed and our job is failed. We found similar bug in Cinder [3] and we were trying to limit number of output produced by tests but this doesn’t help much. I don’t know how to move forward with this issue. Maybe someone more familiar with ostestr/subunit can take a look at it and help us to make this job finally working :) [1] https://review.openstack.org/#/c/577383/ [2] http://logs.openstack.org/83/577383/28/check/neutron-functional/649ba74/log… [3] https://bugs.launchpad.net/cinder/+bug/1728640 — Slawek Kaplonski Senior software engineer Red Hat

1 0

[all] Come and join us @ FOSDEM 2019, BXL, Belgium (Feb 2-3)
by Jean-Philippe Evrard 21 Jan '19

21 Jan '19

Hello everyone, Like the last year(s), the OpenStack community has a booth during FOSDEM in Brussels! Everyone is welcome to come by, and a little help by taking a shift at our stand would be super appreciated! I've written the event's details in an Etherpad [0]. This year is a little different, as the booth will have more topics than usual: - We are now welcoming distributions to talk about their way to distribute OpenStack. You could see RDO information there, for example. - We will have marketing material for the OpenInfrastructure pilot projects too. I look forward to see you there! Regards, Jean-Philippe Evrard (evrardjp) [0]: https://etherpad.openstack.org/p/fosdem-2019

1 0

Patch needs to be re-approved
by Ni, Qi 21 Jan '19

21 Jan '19

Hey guys, Please take a look at my patch https://review.openstack.org/#/c/626109/. Since there are two code review +2 and workflow +1, why hasn't it been merged yet? Best regards, Nicky.

2 1

Pre-Denver Summit [OFFTOPIC]
by David Medberry 19 Jan '19

19 Jan '19

FYI, There is a Denver traditional sci-fi fest the weekend prior to the Open Infra Summit. It is called "StarFest" and has been running for decades. https://starfestdenver.com/ So, if interested in such things, just come a couple days early. I don't expect this to interest many, but feel it is worthwhile to advertise it a tiny bit. I did bracket tag it offtopic.

1 0

[CFP-Denver] Co-Speaker for Hands-on Session in Denver Summit (Prinz Elvis Noudjeu)
by Prinz Elvis N 19 Jan '19

19 Jan '19

Hi All, Just want to ask if someone needs a Co-Speaker in his team for CFP Denver Summit. For Hands-on Session with Topics around: Kolla, zun, Monitoring, Cinder or HPC. Cheers Elvis from Germany freenode: PrinzElvis tw: @PrinzElvis

1 0

[neutron]How to ease congestion at neutron server nodes?
by Cody 18 Jan '19

18 Jan '19

Hi Stackers, What solution(s) other than DVR could I use to avoid north-south traffic congestion at the neutron server nodes? Basically, I wish to let VMs with floating IPs to route directly from their respective hypervisor hosts to the Internet. Thank you very much. Regards, Cody

5 5

[ironic] Mid-cycle call times
by Julia Kreger 18 Jan '19

18 Jan '19

Greetings everyone, During our ironic team meeting in December, we discussed if we should go ahead and have a "mid-cycle" call in order to try sync up on where we are at during this cycle, and the next steps for us to take as a team. With that said, I have created a doodle poll[1] in an attempt to identify some days that might work. Largely the days available on the poll are geared around my availability this month. Ideally, I would like to find three days where we can schedule some 2-4 hour blocks of time. I've gone ahead and started an etherpad[2] to get us started on brainstorming. Once we have some ideas, we will be able to form a schedule and attempt to identify the amount of time required. -Julia [1]: https://doodle.com/poll/uqwywaxuxsiu7zde [2]: https://etherpad.openstack.org/p/ironic-stein-midcycle

2 5

Retiring openstack-infra/puppet-storyboard
by Andreas Jaeger 18 Jan '19

18 Jan '19

The repo openstack-infra/puppet-storyboard has been created with the intent to host storyboard by the OpenStack Infra team - and this did not happen. We will therefore retire the repository, I'm proposing patches now with topic retire-puppet-storyboard, Andreas -- Andreas Jaeger aj(a){suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 1

[placement] update 19-02
by Chris Dent 18 Jan '19

18 Jan '19

HTML: https://anticdent.org/placement-update-19-02.html Hi! It's a placement update! The main excitement this week is we had a meeting to check in on the state of extraction and figure out the areas that need the most attention. More on that in the extraction section within. # Most Important Work to complete and review changes to deployment to support extracted placement is the main thing that matters. # What's Changed * Placement is now able to publish release notes. * Placement is running python 3.7 unit tests in the gate, but not functional (yet). * We had that meeting and [Matt made some notes](http://lists.openstack.org/pipermail/openstack-discuss/2019-January/…. # Bugs * Placement related [bugs not yet in progress](https://goo.gl/TgiPXb): 15. +1. * [In progress placement bugs](https://goo.gl/vzGGDQ) 16. Stable. # Specs Last week was spec freeze so I'll not list all the specs here, but for reference, there were 16 specs listed last week and all 16 of them are neither merged nor abandoned. # Main Themes The reshaper work was restarted after discussion at the meeting surfaced its stalled nature. The libvirt side of things is due some refactoring while the xenapi side is waiting for a new owner to come up to speed. Gibi has proposed a related functional test. All of that at: * <https://review.openstack.org/#/q/topic:bp/reshape-provider-tree+status:open> Also making use of nested is this spectacular stack of code at bandwidth-resource-provider: * <https://review.openstack.org/#/q/topic:bp/bandwidth-resource-provider> Eric's in the process of doing lots of cleanups to how often the ProviderTree in the resource tracker is checked against placement, and a variety of other "let's make this more right" changes in the same neighborhood: * Stack at: <https://review.openstack.org/#/c/615677> That stuff is very close to ready and will make lots of people happy when it merges. One of the main areas of concern is making sure it doesn't break things for Ironic. ## Extraction As noted above, there was a meeting which resulted in [Matt's Notes](http://lists.openstack.org/pipermail/openstack-discuss/2019-January/…, an updated [extraction etherpad](https://etherpad.openstack.org/p/placement-extract-stein-5), and an improved understanding of where things stand. The critical work to ensure a healthy extraction is with getting deployment tools working. Here are _some_ of the links to that work: * [TripleO](https://review.openstack.org/#/q/topic:tripleo-placement-extractio… * [OpenStack Ansible](https://review.openstack.org/#/q/project:openstack/openstack-ansib… * [Kolla and Kolla Ansible](https://review.openstack.org/#/q/topic:split-placement) and [kolla upgrade](https://review.openstack.org/#/q/topic:upgrade-placement) We also worked out that getting the online database migrations happening on the placement side of the world would help: * [in placement](https://review.openstack.org/#/c/624942/) * [use in grenade](https://review.openstack.org/#/c/631614/) Documentation is mostly in-progress, but needs some review from packagers. A change to [openstack-manuals](https://review.openstack.org/#/c/628324/) depends on the [initial placement install docs](https://review.openstack.org/628220). There is a patch to [delete placement](https://review.openstack.org/#/c/618215/) from nova on which we've put an administrative -2 until it is safe to do the delete. # Other There are 13 [open changes](https://review.openstack.org/#/q/project:openstack/placement+statu… in placement itself. Several of those are easy win cleanups. Of those placement changes, the [online-migration-related](https://review.openstack.org/#/q/topic:bug/180392… ones are the most important. Outside of placement (I've decided to trim this list to just stuff that's seen a commit in the last two months): * <https://review.openstack.org/#/q/topic:minimum-bandwidth-allocation-placeme…> Neutron minimum bandwidth implementation * <https://review.openstack.org/#/c/621645/> WIP: add Placement aggregates tests (in tempest) * <https://review.openstack.org/627326> blazar: Consider the number of reservation inventory * <https://review.openstack.org/622316> Add placement client for basic GET operations (to tempest) # End Because I wanted to see what it might look like, I made a toy VM scheduler and placer, using etcd and placement. Then I wrote a [blog post](https://anticdent.org/etcd-placement-virt-install-compute.html). I wish there was more time for this kind of educational and exploratory playing. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

1 0

[sig][upgrades] 2019 reboot/irc meeting on Monday
by James Page 18 Jan '19

18 Jan '19

Hi All During the PTG in Denver we agreed to move the Upgrades SIG IRC meeting to a 4 week cadence. I completed the re-scheduling shortly after the PTG, but we've failed to actually hold a meeting to date! The next scheduled meetings are 0900 and 1600 UTC this coming Monday; we'll go with the standing agenda that we had before: https://etherpad.openstack.org/p/upgrades-sig-meeting Have a great weekend and look forward to chatting with interested parties on Monday! Cheers James

1 0

[dev] [infra] [devstack] [qa] [kuryr] DevStack's etcd performance on gate VM's
by Michał Dulko 18 Jan '19

18 Jan '19

Hi, In Kuryr-Kubernetes we're using the DevStack-installed etcd as a backend store for Kubernetes that we run on our gates. For some time we can see its degraded performance manifesting like this [1] in the logs. Later on this leads to various K8s errors [2], [3], up to missing notifications from the API, which causes failures in Kuryr-Kubernetes tempest tests. From what I've seen those etcd warnings normally mean that disk latency is high. This seems to be mostly happening on OVH and RAX hosts. I've looked at this with OVH folks and there isn't anything immediately alarming about their hosts running gate VM's. Upgrading the etcd version doesn't seem to help, as well as patch [4] which increases IO priority for etcd process. Any ideas of what I can try next? I think we're the only project that puts so much pressure on the DevStack's etcd. Help would really be welcomed, getting rid of this issue will greatly increase our gates stability. Thanks, Michał [1] http://logs.openstack.org/49/624749/1/check/kuryr-kubernetes-tempest-daemon… [2] http://logs.openstack.org/49/624749/1/check/kuryr-kubernetes-tempest-daemon… [3] http://logs.openstack.org/49/624749/1/check/kuryr-kubernetes-tempest-daemon… [4] https://review.openstack.org/#/c/624730/

3 5

[tripleo] LP bug bash
by Juan Antonio Osorio Robles 18 Jan '19

18 Jan '19

Hello folks! It has come to our attention that our Launchpad bug list has been growing and some bugs have gone stale. We have decided to go through the list weekly and triage or update bugs as needed in order to address this. This would be done one hour before our weekly meeting (so Tuesday at 13:00 UTC). Volunteers or people interested are welcome! There will be more details on the medium (video or IRC) on that day in the #tripleo channel. Best regards!

2 2

Neutron tagging
by cmnfths 17 Jan '19

17 Jan '19

Hi everyone! Recently I've encountered a neutron issue related to port tagging mechanism, and wonder if anyone else ever did. The initial source of the issue was, as it seems, identical numeration of external VLANs' tags and OVS (exactly br-int) port tags. The VLAN tagged 222 was added to bridge br-ex and everything worked, but at some point firewall reported unusual traffic. Thus I'd found that there was a loop and 2 qr-* ports with the same tag 222 attached to br-int. After that I deleted them and the loop was gone. So the question is what exactly these tags are? The same ethernet frame bits as 802.1Q tags? Where is a pool or something they're taken from? Is there any possibility to form such pool via configs or patches? Has anyone ever encountered such situation? Thanks, Andrew Th.

2 1

[oslo] Parallel Privsep is Proposed for Release
by Ben Nemec 17 Jan '19

17 Jan '19

Yay alliteration! :-) I wanted to draw attention to this release[1] in particular because it includes the parallel privsep change[2]. While it shouldn't have any effect on the public API of the library, it does significantly affect how privsep will process calls on the back end. Specifically, multiple calls can now be processed at the same time, so if any privileged code is not reentrant it's possible that new race bugs could pop up. While this sounds scary, it's a necessary change to allow use of privsep in situations where a privileged call may take a non-trivial amount of time. Cinder in particular has some privileged calls that are long-running and can't afford to block all other privileged calls on them. So if you're a consumer of oslo.privsep please keep your eyes open for issues related to this new release and contact the Oslo team if you find any. Thanks. -Ben 1: https://review.openstack.org/628019 2: https://review.openstack.org/#/c/593556/

5 14

Infra team upgrading review.openstack.org Gerrit from 2.13.9 to 2.13.12 January 18 at about 1700UTC
by Clark Boylan 17 Jan '19

17 Jan '19

We will be performing a minor Gerrit upgrade to version 2.13.12 tomorrow (January 18, 2019) at 1700UTC. We've tested this upgrade on our dev server, https://review-dev.openstack.org, and expect it to be a quick upgrade. Any outage shouldn't last more than 10 minutes. We will let our configuration management tooling manage the upgrade so we won't have an exact time, but will try to get it as close to 1700UTC as possible. Feel free to test out the new version on the dev server. We are happy to answer any questions you might have as well. Sorry for the short notice and the cross post, Clark

1 0

[ALL] Train TC Election Season (Yes, TC not PTL)
by Kendall Nelson 17 Jan '19

17 Jan '19

Hello All! TC and not PTL you might ask? Yes! Due to the timing of the summit and release and optimizing timing so that they don't overlap, the technical elections this cycle will trade places and we will have the TC election first and then the PTL election. If you're curious about how this decision was made, feel free to check out the conversation during TC office hours here[1]. Election details: https://governance.openstack.org/election/ Please read the stipulations and timelines for candidates and electorate contained in this governance documentation. There will be further announcements posted to the mailing list as action is required from the electorate or candidates. This email is for information purposes only. If you have any questions which you feel affect others please reply to this email thread. If you have any questions that you which to discuss in private please email any of the election officials[2] so that we may address your concerns. Thank you, -Kendall (diablo_rojo) [1] http://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2019… [2] https://governance.openstack.org/election/#election-officials

1 0

[ironic] boot.ipxe input/output error
by Zufar Dhiyaulhaq 17 Jan '19

17 Jan '19

Hi, I try to install ironic but get error boot.ipxe input/output error when trying to cleaning the node (error image: https://ibb.co/mhN5GYc) This is my ironic configuration : *[DEFAULT]enabled_drivers=pxe_ipmitoolenabled_hardware_types = ipmilog_dir=/var/log/ironictransport_url=rabbit://guest:guest@10.60.60.10:5672/ <http://guest:guest@10.60.60.10:5672/>auth_strategy=keystonenotification_driver = messaging[conductor]send_sensor_data = trueautomated_clean=true[swift]region_name = RegionOneproject_domain_id = defaultuser_domain_id = defaultproject_name = servicespassword = IRONIC_PASSWORDusername = ironicauth_url = http://10.60.60.10:5000/v3 <http://10.60.60.10:5000/v3>auth_type = password[pxe]tftp_root=/tftpboottftp_server=10.60.60.10ipxe_enabled=Truepxe_bootfile_name=undionly.kpxeuefi_pxe_bootfile_name=ipxe.efipxe_config_template=$pybasedir/drivers/modules/ipxe_config.templateuefi_pxe_config_template=$pybasedir/drivers/modules/ipxe_config.templateipxe_use_swift=True[deploy]http_root=/httpboothttp_url=http://10.60.60.10:8080 <http://10.60.60.10:8080>[service_catalog]insecure = Trueauth_uri=http://10.60.60.10:5000/v3 <http://10.60.60.10:5000/v3>auth_type=passwordauth_url=http://10.60.60.10:35357 <http://10.60.60.10:35357>project_domain_id = defaultuser_domain_id = defaultproject_name = servicesusername = ironicpassword = IRONIC_PASSWORDregion_name = RegionOne[database]connection=mysql+pymysql://ironic:IRONIC_DBPASSWORD@10.60.60.10/ironic?charset=utf8 <http://ironic:IRONIC_DBPASSWORD@10.60.60.10/ironic?charset=utf8>[keystone_authtoken]auth_url=http://10.60.60.10:35357 <http://10.60.60.10:35357>www_authenticate_uri=http://10.60.60.10:5000 <http://10.60.60.10:5000>auth_type=passwordusername=ironicpassword=IRONIC_PASSWORDuser_domain_name=Defaultproject_name=servicesproject_domain_name=Default[neutron]www_authenticate_uri=http://10.60.60.10:5000 <http://10.60.60.10:5000>auth_type=passwordauth_url=http://10.60.60.10:35357 <http://10.60.60.10:35357>project_domain_name=Defaultproject_name=servicesuser_domain_name=Defaultusername=ironicpassword=IRONIC_PASSWORDcleaning_network = 461a6663-e015-4ecf-9076-d1b502c3db25provisioning_network = 461a6663-e015-4ecf-9076-d1b502c3db25[glance]region_name = RegionOneproject_domain_id = defaultuser_domain_id = defaultproject_name = servicespassword = IRONIC_PASSWORDusername = ironicauth_url = http://10.60.60.10:5000/v3 <http://10.60.60.10:5000/v3>auth_type = passwordswift_endpoint_url = http://10.60.60.10:8080/v1/AUTH_%(tenant_id)sswift_account = AUTH_f3bb39ae2e0946e1bbf812bcde6e08a7swift_container = glanceswift_temp_url_key = secret* I try to open the URL which is http://10.60.60.10:8080/boot.ipxe but always get BAD URL error. Are the Baremetal node cannot download the boot.ipxe? are my swift is broken? Thank you. Best Regards, Zufar Dhiyaulhaq

1 0

[release] Release countdown for week R-11, January 21-25
by Sean McGinnis 17 Jan '19

17 Jan '19

Welcome to the weekly countdown email. Development Focus ----------------- Teams should be focused on implementing planned work for the cycle. It is also a good time to review those plans and reprioritize anything if needed based on the what progress has been made and what looks realistic to complete in the next few weeks. General Information ------------------- Looking ahead to Stein-3, please be aware of the various freeze dates. This varies for deliverable type, starting with non-client libraries, then client libraries, then finally services. This is to ensure we have time for requirements updates and resolving any issues prior to RC. Just as a reminder, we have freeze dates ahead of the first RC in order to stabilize our requirements. Updating global requirements close to overall code freeze increases the risk of an unforeseen side effect being introduced too late in the cycle to properly fix. For this reason, we first freeze the non-client libraries that may be used by service and client libraries, followed a week later by the client libraries. This minimizes the ripple effects that have caused projects to scamble to fix last minute issues. Please keep these deadlines in mind as you work towards wrapping up feature work that may require library changes to complete. Upcoming Deadlines & Dates -------------------------- Non-client library freeze: February 28 Client library freeze: March 7 Stein-3 milestone: March 7 -- Sean McGinnis (smcginnis)

1 0

[all] Etcd as DLM
by Ben Nemec 17 Jan '19

17 Jan '19

Hi, I wanted to revisit this topic because it has come up in some downstream discussions around Cinder A/A HA and the last time we talked about it upstream was a year and a half ago[1]. There have certainly been changes since then so I think it's worth another look. For context, the conclusion of that session was: "Let's use etcd 3.x in the devstack CI, projects that are eventlet based an use the etcd v3 http experimental API and those that don't can use the etcd v3 gRPC API. Dims will submit a patch to tooz for the new driver with v3 http experimental API. Projects should feel free to use the DLM based on tooz+etcd3 from now on. Others projects can figure out other use cases for etcd3." The main question that has come up is whether this is still the best practice or if we should revisit the preferred drivers for etcd. Gorka has gotten the grpc-based driver working in a Cinder driver that needs etcd[2], so there's a question as to whether we still need the HTTP etcd-gateway or if everything should use grpc. I will admit I'm nervous about trying to juggle eventlet and grpc, but if it works then my only argument is general misgivings about doing anything clever that involves eventlet. :-) It looks like the HTTP API for etcd has moved out of experimental status[3] at this point, so that's no longer an issue. There was some vague concern from a downstream packaging perspective that the grpc library might use a funky build system, whereas the etcd3-gateway library only depends on existing OpenStack requirements. On the other hand, I don't know how much of a hassle it is to deploy and manage a grpc-gateway. I'm kind of hoping someone has already been down this road and can advise about what they found. Thanks. -Ben 1: https://etherpad.openstack.org/p/BOS-etcd-base-service 2: https://github.com/embercsi/ember-csi/blob/5bd4dffe9107bc906d14a45cd819d9a6… 3: https://github.com/grpc-ecosystem/grpc-gateway

11 20

[tripleo] OVB is now on Gerrit
by Ben Nemec 17 Jan '19

17 Jan '19

Just a heads up that the import of OVB to Gerrit is complete. If you're using OVB you should switch your clones from the Github repo to https://git.openstack.org/cgit/openstack/openstack-virtual-baremetal I've marked the Github repo deprecated so please don't submit issues or PRs there anymore. For the moment the approval process won't meaningfully change. I'll still be reviewing and single-approving patches, and the core reviewer list for OVB is the same as it was on Github, with the addition of Juan (as TripleO PTL) and Harald (as someone who has recently done a ton of good work in OVB). See the full list here: https://review.openstack.org/#/admin/groups/1993,members Once we have E2E testing set up on the repo (that isn't me manually testing changes against my local cloud) I expect we'll open that list up more and can discuss moving to a more typical 2 +2 model. Thanks. -Ben

2 2

[TripleO] Scaling TripleO for Edge Computing
by James Slagle 17 Jan '19

17 Jan '19

Within the TripleO Edge squad, we've been collecting ideas and looking at other current in progress work as it relates to scaling TripleO. The high level goal is brainstorm about how we can scale to manage deployments that are of a order of magnitude larger than we do today (thousands of nodes instead of hundreds). We've been collecting these ideas in this google doc: https://docs.google.com/document/d/12tPc4NC5fo8ytGuFZ4DSZXXyzes1x3U7oYz9nea… As always, any feedback or other ideas are welcome. It should be open to view/comment/edit without any account required. Or, feel free to reply on the ML. Thanks! -- -- James Slagle --

1 0

[neutron] [upgrade] No meeting on Jan. 17th
by Lujin Luo 17 Jan '19

17 Jan '19

Hi team, I will not be able to chair the meeting tomorrow. And since from the review list, we do not have many updates. Let's resume next week. Sorry for any inconvenience caused. Best regards, Lujin

1 0

[bifrost][ironic-inspector] how could i use bifrost to inspector the server
by 谭明宵 17 Jan '19

17 Jan '19

Hi all: I use the bifrost to deploy ironic standalone，but I don’t know how to use it for ironic-inspector，Thanks for your help

1 0

[nova][placement][tripleo] Extracted Placement enablement status update #1
by Lee Yarwood 17 Jan '19

17 Jan '19

Hello, This is a brief status progress report on my work to enable the deployment of the extracted Placement service within TripleO ahead of the extraction check-in call later today. tl;dr TripleO isn't ready to switch to an extracted Placement service or for code to be removed from openstack/nova. # RDO (packaging) https://review.rdoproject.org/#/q/topic:placement-add This was started at the PTG in Denver and mostly completed some time ago now. I do however have a single change outstanding that includes the puppet-placement package as a dependency of puppet-tripleo but aside from that this is complete: puppet-tripleo: Require puppet-placement https://review.rdoproject.org/r/18330 FWIW in the context of the extraction check-in call, both RDO and TripleO are not ready to deal with the original placement code being deleted from the openstack/nova project at this point. This will continue to be the case until the following work is completed to enable deployments using the extracted project in TripleO. # Kolla (containers) https://review.openstack.org/#/q/topic:split-placement+OR+topic:upgrade-pla… The initial Kolla change to produce a placement-api container landed some time ago after some small delays due to the Stein UCA not being used for the Ubuntu binary jobs: Split placement-api from nova https://review.openstack.org/#/c/613589/ FWIW an additional change to copy across the DB migration script has also been posted and is pending a package promotion in RDO: Copy placement database migration script https://review.openstack.org/#/c/626382/ The above change isn't required by TripleO, I just wanted to highlight that kolla-ansible are looking to use the script during upgrades. Unfortunately due various issues with TripleO promotions the TripleO container for the placement-api was only uploaded yesterday after I manually built it: https://hub.docker.com/r/tripleomaster/centos-binary-placement-api # Puppet https://review.openstack.org/#/q/topic:tripleo-placement-extraction The initial and massive puppet-placement cookiecutter change has landed: Initial cookiecutter run and import from puppet-nova https://review.openstack.org/#/c/604182/ This is currently only tested on CentOS7 by the following POI or puppet-openstack-integration change that has itself been stuck behind a raft of Ubuntu py3 and Stein UCA issues: placement: Extract the service from Nova https://review.openstack.org/#/c/615568/ I'm attempting to unblock this by working my way through the following changes to support py3 and the Stein UCA within the Ubuntu jobs: https://review.openstack.org/#/q/status:open+topic:ubuntu-py3 https://review.openstack.org/#/q/status:open+topic:inherit_pyvers Help with these changes from any openstack-puppet Ubuntu users would obviously be appreciated here! Finally I'm currently working on the following puppet-tripleo change that makes this all usable within TripleO itself: WIP placement: Initial extraction of the Placement service from Nova https://review.openstack.org/#/c/624335/ # TripleO https://review.openstack.org/#/q/topic:tripleo-placement-extraction On the TripleO front I almost have undercloud deployment completing in a reproducer environment with various local hacks to workaround changes not being merged yet. The main tripleo-heat-template change can be found below: WIP placement: Extract the service from Nova https://review.openstack.org/#/c/630644/ # TODO Obviously there's still a lot to do here but to begin with I'll be focusing on the following tasks: - Landing the puppet-openstack-integration and puppet-tripleo changes. - Moving the tripleo-heat-templates change out of WIP. - Posting draft upgrade_tasks in a new change using the db migration script. Hopefully this is of some use to folks in the Placement and TripleO teams! Cheers, -- Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76

3 2

[nova][glance] Granting image member access for snapshots (bug 1675791)
by Matt Riedemann 16 Jan '19

16 Jan '19

I have a fix proposed for a pretty old bug (1675791 [1]). This originally came up because of a scenario where an admin shelves a server and then the owner of the shelved server cannot unshelve it since they do not have access to the shelve snapshot image. The same is true for normal snapshot and backup operations though, see this proposed spec for Stein [2]. It also came up during the cross-cell resize spec review [3] since that solution depends on snapshot to get the root disk from one cell to another. In a nutshell, when creating a snapshot now, the compute API will check if the project creating the snapshot is the same as the project owner of the server. If not, the image is created with visibility=shared and the project owner of the instance is granted member access to the image, which allows them to GET the image directly via the ID, but not list it by default (the tenant user has to accept the pending membership for that). I have tested this out in devstack today and everything seems to work well. I am posting this to (a) raise awareness of the bug and proposed fix since it is sort of a behavior change in the createImage/createBackup/shelve APIs and (b) to make sure the glance team is aware and acknowledges this is an OK thing to do, i.e. are there any kind of unforeseen side effects of automatically granting image membership like this (I would think not since the owner of the instance has access to the root disk of the server anyway - it is their data). Also note that some really crusty legacy code in most of the in-tree virt drivers had to be removed (some virt drivers would change the image visibility back to private during the actual data upload to glance) which could mean out of tree drivers have the same issue. [1] https://bugs.launchpad.net/nova/+bug/1675791 [2] https://review.openstack.org/#/c/616843/ [3] https://review.openstack.org/#/c/616037/3/specs/stein/approved/cross-cell-r… -- Thanks, Matt

4 6