- openstack-discuss - lists.openstack.org

Placement governance switch
by Ed Leafe 14 Feb '19

14 Feb '19

With PTL election season coming up soon, this seems like a good time to revisit the plans for the Placement effort to become a separate project with its own governance. We last discussed this back at the Denver PTG in September 2018, and settled on making Placement governance dependent on a number of items. [0] Most of the items in that list have been either completed, are very close to completion, or, in the case of the upgrade, is no longer expected. But in the time since that last discussion, much has changed. Placement is now a separate git repo, and is deployed and run independently of Nova. The integrated gate in CI is using the extracted Placement repo, and not Nova’s version. In a hangout last week [1], we agreed to several things: * Placement code would remain in the Nova repo for the Stein release to allow for an easier transition for deployments tools that were not prepared for this change * The Placement code in the Nova tree will remain frozen; all new Placement work will be in the Placement repo. * The Placement API is now unfrozen. Nova, however, will not develop code in Stein that will rely on any newer Placement microversion than the current 1.30. * The Placement code in the Nova repo will be deleted in the Train release. Given the change of context, now may be a good time to change to a separate governance. The concerns on the Nova side have been largely addressed, and switching governance now would allow us to participate in the next PTL election cycle. We’d like to get input from anyone else in the OpenStack community who feels that a governance change would impact them, so please reply in this thread if you have concerns. [0] http://lists.openstack.org/pipermail/openstack-dev/2018-September/134541.ht… [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-February/002451… -- Ed Leafe

3 7

[infra] StoryBoard Maintenance 2019-02-15 at 20:00 UTC
by Jeremy Stanley 13 Feb '19

13 Feb '19

We're planning to perform a quick server upgrade/replacement and database move for the StoryBoard service at https://storyboard.openstack.org/ this Friday, 2019-02-15 starting at 20:00 UTC and hopefully only lasting 5-10 minutes. Please find us in the #openstack-infra channel on the Freenode IRC network or follow up to this message if you have any questions or concerns. -- Jeremy Stanley

1 0

[ops][nova] Heads-up: Upcoming version bump for libvirt and QEMU in 'Stein'
by Kashyap Chamarthy 13 Feb '19

13 Feb '19

Heya folks, This is a gentle reminder to note that we are about to[1] bump the minimum required versions for libvirt and QEMU in "Stein" to: libvirt : 3.0.0 QEMU : 2.8.0 We've picked[1][2] these "next" minimum versions for "Stein" in April 2018. And the last time we did a minimum libvirt / QEMU version bump was during the "Pike" release. So we hope the intervening one year's time since the last version change is sufficient enough to prepare for this upcoming version bump. If there aren't any valid objections to this in a week, we intend to go ahead and bump the versions, as we planned[1][2]. * * * PS: Ccing the zKVM CI maintainers to check if they're okay with this, as the zKVM CI isn't running anymore. [1] https://review.openstack.org/#/c/632507/ — libvirt: Bump MIN_{LIBVIRT,QEMU}_VERSION for "Stein" [2] http://lists.openstack.org/pipermail/openstack-dev/2018-April/129048.html — RFC: Next minimum libvirt / QEMU versions for "Stein" release [3] http://git.openstack.org/cgit/openstack/nova/commit/?id=28d337b — Pick next minimum libvirt / QEMU versions for "Stein" -- /kashyap

1 0

User Committee Elections - call for candidates
by Melvin Hillsman 13 Feb '19

13 Feb '19

The candidacy period for the upcoming UC election is open. Three seats will be filled. If you are an AUC and are interested in running for one of them, now is the time to announce it. Here are the important dates: February 04 - February 17, 05:59 UTC: Open candidacy for UC positions February 18 - February 24, 11:59 UTC: UC elections (voting) Special thanks to our election officials - Mohamed Elsakhawy and Jonathan Proulx! You can find all the info for the election here: https://governance.openstack.org/uc/reference/uc-election-feb2019.html You announce your candidacy by sending an email to user-committee(a)lists.openstack.org with the subject line UC Candidacy. Here are some great examples of previous candidate letters if you are having difficulty: http://lists.openstack.org/pipermail/user-committee/2018-August/002700.html http://lists.openstack.org/pipermail/user-committee/2018-August/002713.html http://lists.openstack.org/pipermail/user-committee/2018-February/002556.ht… http://lists.openstack.org/pipermail/user-committee/2018-February/002563.ht… -- Kind regards, Melvin Hillsman mrhillsman(a)gmail.com mobile: (832) 264-2646

1 0

[kolla] Today meeting cancelled Feb-13-2019
by Eduardo Gonzalez 13 Feb '19

13 Feb '19

Hi team, Due to job responsabilities i won't be able to hold today's meeting. Meeting topics haven't changed since last week. If have something wanna discuss please add to next week meeting or raise in the main IRC channel. Regards

1 0

[nova][dev] Which response code should be returned when migrate is called but the src host is offline?
by Lee Yarwood 13 Feb '19

13 Feb '19

Hello all, I can't seem to settle on an answer for $subject as part this bugfix: compute: Reject migration requests when source is down https://review.openstack.org/#/c/623489/ 409 suggests that the user is able to address the issue while 503 suggests that n-api itself is at fault. I'd really appreciate peoples thoughts on this given I hardly ever touch n-api. Thanks in advance, -- Lee Yarwood A5D1 9385 88CB 7E5F BE64 6618 BCA6 6E33 F672 2D76

4 5

How *-conductor (database accessor) assure concurrency?
by 양유석 13 Feb '19

13 Feb '19

Hi, guys. Today, I encountered strange behaviors and it raise me a simple question which I never concerned about. It's about 'how database accessors like *-conductor assure DB data consistency?' What I've seen is ModelsNotFound in Trove which meaning there is no sqlalchemy query result for the Trove DB model. I'm not sure what's happening before, but what I found is DB entry is actually existed but trove-conductor could not find it emitting exception continuously. At the same time, different trove-conductor would be working normally after restart. First, I thought that sqlalchemy ensures concurrency but after reading related document ( https://docs.sqlalchemy.org/en/latest/orm/session_basics.html#is-the-sessio…) it does not guarantee at all, and user should take all responsibility to manage session. After, I thought oslo.concurrency is promising to ensure consistency by making lock inter process in that the name tells me. But I could not find any related code for locking. So.. What happens internally for *-manage? Any hints would be appreciated. Thanks.

1 0

[cinder][dev] Bug for deferred deletion in RBD
by Jae Sang Lee 13 Feb '19

13 Feb '19

Hello, I recently ran a volume deletion test with deferred deletion enabled on the pike release. We experienced a cinder-volume hung when we were deleting a large amount of the volume in which the data was actually written(I make 15GB file in every volumes), and we thought deferred deletion would solve it. However, while deleting 200 volumes, after 50 volumes, the cinder-volume downed as before. In my opinion, the trash_move api does not seem to work properly when removing multiple volumes, just like remove api. If these test results are my fault, please let me know the correct test method.

3 14

[scientific-sig] IRC Meeting 1100UTC: ISC participation, Summit Forum, GPFS follow-up
by Stig Telfer 13 Feb '19

13 Feb '19

Hi All - We have a Scientific SIG IRC meeting at 1100 UTC (just over an hour away) in channel #openstack-meeting. Everyone is welcome. This week’s agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_February_13th_20… <https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_February_13th_20…> We’d like to continue the discussions on SIG participation in up-and-coming conferences, and also follow up on user experiences of the GPFS/Manila driver. If anyone has other items to raise, please do add them to the agenda. Cheers, Stig

1 0

Re: [kolla][mariadb] Multinode deployment fails due to bootstrap_mariadb or mariadb errors (Giuseppe Sannino)
by Viktor Shulhin 13 Feb '19

13 Feb '19

Hi Giuseppe, Seems like deployments with Ubuntu base distros are broken. I didn't find any solution for that. I have deployed Rocky with Centos based distro on Ubuntu 16.04 host recently. Some parameters from /etc/kolla/globals.yml are: kolla_base_distro: "centos" kolla_install_type: "binary" openstack_release: "rocky" >Hi all, >need your help. >I'm trying to deploy Openstack "Queens" via kolla on a multinode system (1 >controller/kolla host + 1 compute). >I tried with both binary and source packages and I'm using "ubuntu" as >base_distro.

1 0