- openstack-discuss - lists.openstack.org

[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

[dev][puppet] Register PTG team attendance
by Tobias Urdin 16 Jan '19

16 Jan '19

Dear Puppeteers, The foundation would like all projects to report if they will be attending the PTG and I'm in charge of reporting that for the Puppet OpenStack project. I'm now reaching out to hear if you are attending and would like the Puppet OpenStack project to have an official attendance and therefore possible requirements of rooms etc? I personally is not sure that I will attend the PTG even though it's directly after the Summit which I'm hoping to be able to attend this year. Earlier years we haven't had any real reasons to have dedicated rooms or events from what I know but please let me know if you have any plans. I don't think not placing our team as attending prevents anybody from actually being at the PTG, I hope not atleast (maybe somebody can shine in on that part). I need to fill in the survey by January 20th, 2019 at 7:00 UTC so please let me know urgently, sorry for the short timespan, it's entirely my fault on that part. Please get back to me if you will be attending and need to register the Puppet OpenStack team. Best regards Tobias

1 0

[openstack-discuss] [stackalytics] Stackalytics facelift
by Boris Renski 16 Jan '19

16 Jan '19

Folks, Happy New Year! We wanted to start the year by giving a facelift to stackalytics.com (based on stackalytics openstack project). Brief summary of updates: - We have new look and feel at stackalytics.com - We did away with DriverLog <http://stackalytics.com/report/driverlog> and Member Directory <http://stackalytics.com/report/members>, which were not very actively used or maintained. Those are still available via direct links, but not in the menu on the top - BIGGEST CHANGE: You can now track some of the CNCF and Unaffiliated project commits via a separate subsection accessible via top menu. Before this was all bunched up in Project Type -> Complimentary Happy to hear comments or feedback. -Boris

9 12

[publiccloud-wg][sigs] Reminder weekly meeting Public Cloud WG
by Tobias Rydberg 16 Jan '19

16 Jan '19

Hi everyone, Time for a new meeting for Public Cloud WG - tomorrow 1400 UTC in #openstack-publiccloud! Agenda found at https://etherpad.openstack.org/p/publiccloud-wg Cheers, Tobias -- Tobias Rydberg Senior Developer Twitter & IRC: tobberydberg www.citynetwork.eu | www.citycloud.com INNOVATION THROUGH OPEN IT INFRASTRUCTURE ISO 9001, 14001, 27001, 27015 & 27018 CERTIFIED

1 0

Re: [Release-job-failures] Release of openstack/puppet-* failed
by Thierry Carrez 16 Jan '19

16 Jan '19

Puppet-OpenStack Stein M2 release job (triggered after https://review.openstack.org/#/c/629753/ merged) failed for all modules with errors similar to: zuul(a)openstack.org wrote: > Build failed. > > - release-openstack-puppet http://logs.openstack.org/b1/b1434f41935eb5c4cb50fc5aea2b6406a6d0f63d/relea… : POST_FAILURE in 2m 58s > - announce-release announce-release : SKIPPED This is due to the recent introduction of a puppetforge upload job: https://review.openstack.org/#/c/627573/5/zuul.d/jobs.yaml That job tries to install a few gems and that fails because the ruby header files are not available (missing ruby-dev / ruby-devel package). Tarball upload jobs are then skipped, as well as announcement or releases.o.o documentation. Solution is probably to add that missing package to the "build" bindep.txt profile (for every affected puppet-* repository) that is loaded in pre-run of that publication job. Currently that profile only contains "puppet" and that stops short of installing the ruby development header package (at least on Ubuntu hosts). Once that's done, I recommend pushing a new Stein release for Puppet-OpenStack (similar to https://review.openstack.org/#/c/629753/, bumping .Z for all packages) so that we can test that it properly works before end-of-release crush. -- Thierry Carrez (ttx)

2 2

[neutron]
by Masha Atakova 16 Jan '19

16 Jan '19

1 0

[neutron] Patch fails to build after rechecking.
by Ni, Qi 16 Jan '19

16 Jan '19

Hello guys, I've been working on a patch of neutron https://review.openstack.org/#/c/626109/11 and it keeps failing when building. I'm sure my code is bug free and I found Liu Yulong's patch has a similar condition like mine. https://review.openstack.org/#/c/627285/. He rechecks many times and fails every time. His code is nearly the same as previous except a line of comment. I'm not sure if there's any bug on this checking system and please take a look at our issue, thank you.

2 1

[pctavia][heat] queens loadbalancer issue
by Ignazio Cassano 16 Jan '19

16 Jan '19

Hello All, I am facing an issue with octavia loadbalancer on queens. Attached here there is the heat stack I am using for frating a loadbalancer between 2 virtual machines. I launched the stack 4 times. First, second and third work fine. The forth gives a lot of errors in octavia worker log attached here. It seems to loop . Please help me. Ignazio

1 1

[heat]meeting cancelled this week
by Rico Lin 15 Jan '19

15 Jan '19

Dear team, due to some personal stuff, I will not join meeting today. Let’s resume meeting next week. -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[meta-sig][docs] new section for SIG documentation on docs.o.o
by Adam Spiers 15 Jan '19

15 Jan '19

For the Stein release there is now a new section for SIGs on the documentation home page: https://docs.openstack.org/stein/ Currently only the self-healing SIG has a link but if other SIGs have links to add, it won't feel so lonely ;-)

2 3