April 2019 - openstack-discuss - lists.openstack.org

[nova] XenProject and XenServer CIs not running
by Stephen Finucane 05 Apr '19

05 Apr '19

I've proposed a patch to remove the 'devstack/tempest-dsvm-tempest-xen- rc' from nova [1]. Matt Riedemann pointed out that this may have been used by the XenProject or XenServer CIs. However, it appears that these CIs are not currently running and haven't been in the past 7 days [2]. Could anyone advise if this is a temporary glitch or if the CIs are offline for the foreseeable future? Similarly, could anyone say if that file is safe to remove and, if not, what's using it? Thanks, Stephen [1] https://review.openstack.org/650018 [2] http://ciwatch.mmedvede.net/project?project=nova&time=7+days

2 1

[dev][keystone] Keystone Team Update - Week of 1 April 2019
by Colleen Murphy 05 Apr '19

05 Apr '19

# Keystone Team Update - Week of 1 April 2019 ## News ### RC2 and Stein Release We landed everything we had planned for RC2 and released it this week[1]. The final release is scheduled for next week[2]. [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/004526.ht… [2] https://review.openstack.org/650362 ### Train Planning In advance of the PTG, I've started prepping keystone specs we already know we want to work on in Train[3] and started the Train Roadmap Trello board[4]. Please take a look at both to refresh your memory on what we had planned but didn't finish in past cycles so that we can discuss what to keep and what to scrap for this cycle. We should also talk about our specs backlog[5] and prune it if there are specs that are no longer relevant. [3] https://review.openstack.org/650126 [4] https://trello.com/b/ClKW9C8x/keystone-train-roadmap [5] http://specs.openstack.org/openstack/keystone-specs/specs/keystone/backlog/ ### PTG Planning I've proposed a rough agenda for the PTG[6]. Since our schedule doesn't start until Thursday afternoon, we won't formally meet Thursday morning but we will have time to meet with the QA team and Edge groups who are having sessions at that time. Thursday afternoon we will meet and recap the Forum sessions and decide if we want to change the agenda schedule meetings with other teams. [6] https://etherpad.openstack.org/p/keystone-train-ptg ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 18 changes this week, which included everything we had planned for RC2. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 40 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ## Bugs This week we opened 1 new bug and closed 2. Bugs opened (1) Bug #1823258 (keystone:Undecided) opened by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1823258 Bugs fixed (2) Bug #1808859 (keystone:High) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1808859 Bug #1801873 (keystone:Medium) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1801873 ## Milestone Outlook https://releases.openstack.org/stein/schedule.html The final release for Stein was proposed today[7] and the actual release will take place next week. [7] https://review.openstack.org/650362 ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

[nova] retire a flavor
by Florian Engelmann 05 Apr '19

05 Apr '19

Hi, I would like to retire old flavors we don't want to be use any more. I guess deleting is the wrong way to retire flavors? I was not able to find any documentation about how the life-cycle of a flavor works. Any help is very welcome. All the best, Florian

6 15

[nova] Train Runways Etherpad Is Live!
by Eric Fried 05 Apr '19

05 Apr '19

Nova contributors and reviewers- I have seeded the runways etherpad for Train [1] (by copying from the Stein version [2]). As of this writing, I see six approved Train blueprints [3]. If you own one of these, and your code is ready, please register it in the Queue section of the etherpad and alert us in #openstack-nova. Thanks, efried [1] https://etherpad.openstack.org/p/nova-runways-train [2] https://etherpad.openstack.org/p/nova-runways-stein [3] https://blueprints.launchpad.net/nova/train

1 0

Integration with GuardianKey
by Paulo Angelo 05 Apr '19

05 Apr '19

Hi all, We are trying to integrate OpenStack (Horizon or Keystone) with GuardianKey. However, we have doubts related to the best way to do this and the best point in the code for this integration. GuardianKey is a solution to protect systems against authentication attacks. It uses Machine Learning and analyses the user's behavior, threat intelligence and psychometrics (or behavioral biometrics). The protected system (in the concrete case, OpenStack admin interface) must send an event via REST for the GuardianKey on each login attempt. More info at https:// guardiankey.io . The best way to integrate would be on having a hook in the procedure that process the user credentials submission in OpenStack (the script that receives the POST), something such as: if(<POST IN AUTH FORM>) { boolean loginFailed = checkLogin(); GuardianKeyEvent event = createEventForGuardianKey(username,loginFailed); boolean GuardianKeyValidation = checkGuardianKeyViaREST(event); if(GuardianKeyValidation){ // Allow access } else { // Deny access } } Where is the best place to create this integration? Horizon or Keystone? Is there a way to create a hook for this purpose? Should we create an extension? Any help is welcome. Thank you in advance. Best regards, Paulo Angelo

3 2

[PTL][release] Final releases for Stein proposed
by Sean McGinnis 05 Apr '19

05 Apr '19

Greetings! With yesterday's final RC deadline past, I have now proposed a patch for the final releases for all cycle-with-rc projects for Stein. https://review.openstack.org/#/c/650362/ We would love to have all PTLs provide a +1 on that patch. While not strictly necessary, it is great to see everyone's acknowledgement of the patch. Plus you will all get included in the metedata for the final tag, so it makes a great record. Thanks! Sean

1 0

kolla-ansible 8.0.0.0rc1 (stein)
by no-reply＠openstack.org 05 Apr '19

05 Apr '19

Hello everyone, A new release candidate for kolla-ansible for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/kolla-ansible/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/kolla-ansible/log/?h=stable/stein Release notes for kolla-ansible can be found at: https://docs.openstack.org/releasenotes/kolla-ansible/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/kolla-ansible/+bugs and tag it *stein-rc-potential* to bring it to the kolla-ansible release crew's attention.

1 0

kolla 8.0.0.0rc1 (stein)
by no-reply＠openstack.org 05 Apr '19

05 Apr '19

Hello everyone, A new release candidate for kolla for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/kolla/ Unless release-critical issues are found that warrant a release candidate respin, this candidate will be formally released as the final Stein release. You are therefore strongly encouraged to test and validate this tarball! Alternatively, you can directly test the stable/stein release branch at: https://git.openstack.org/cgit/openstack/kolla/log/?h=stable/stein Release notes for kolla can be found at: https://docs.openstack.org/releasenotes/kolla/ If you find an issue that could be considered release-critical, please file it at: https://bugs.launchpad.net/kolla/+bugs and tag it *stein-rc-potential* to bring it to the kolla release crew's attention.

1 0

[placement] update 19-13
by Chris Dent 05 Apr '19

05 Apr '19

HTML: https://anticdent.org/placement-update-19-13.html Placement update 19-13 is brought to you by the letters P and U. # Most Important The [Virtual Pre-PTG](http://lists.openstack.org/pipermail/openstack-discuss/2019-March/… starts next week. Watch out for emails to start different threads throughout the week. Also next week there will be a Nova pre-PTG [spec review](http://lists.openstack.org/pipermail/openstack-discuss/2019-April/t…. Plenty of the pending work touches on placement. In the meantime here are a couple of etherpads for the PTG: * <https://etherpad.openstack.org/p/placement-ptg-train> * <https://etherpad.openstack.org/p/ptg-train-xproj-nova-placement> # What's Changed * There were some lingering docs and log fixes so we released an RC 3 of Placement. That candidate will become 1.0.0 on April 10th. * Microversion 1.32, for [forbidden aggregates](https://docs.openstack.org/placement/latest/placement-api-micro… merged. * We've decided it would be nice to a) release os-traits and os-resource-classes in an independent fashion and, b) make them available to both placement and nova as tox-siblings. We'll do (a) once release time settles. For (b) the strategy is still a bit up in the air. There's some [email discussion](http://lists.openstack.org/pipermail/openstack-discuss/2019-Apr…. # Specs/Features * Two traits related specs have been re-proposed to Train, following the [new process](https://docs.openstack.org/placement/latest/contributor/contributi…. * <https://review.openstack.org/649992> Spec: support any trait in allocation candidates * <https://review.openstack.org/649368> Spec: support mixing required traits with any traits * As before, the spec for [request group mapping](https://review.openstack.org/597601) will need to be revisited. # Bugs * StoryBoard stories in [the placement group](https://storyboard.openstack.org/#!/project_group/placement): 6. 0 are [untagged](https://storyboard.openstack.org/#!/worklist/580). * Placement related [bugs not yet in progress](https://goo.gl/TgiPXb): 13. -1. * [In progress placement bugs](https://goo.gl/vzGGDQ) 5. -2. Once Stein has settled, we'll figure out a good time to have a bug cleanup and consolidation. # osc-placement osc-placement is currently behind by 14 microversions. +1 since last week. Pending changes: * [support for 1.19](https://review.openstack.org/#/c/641094/) * [support for 1.21](https://review.openstack.org/#/c/641123/) * [aggregate allocation ratio tool](https://review.openstack.org/#/c/640898/) * [stack to fix docs and classifiers](https://review.openstack.org/650093) # Main Themes Be thinking about what you'd like the main themes to be. Put them on the [PTG etherpad](https://etherpad.openstack.org/p/placement-ptg-train). # Other Placement * <https://review.openstack.org/#/c/645255/> This is a start at unit tests for the PlacementFixture. It is proving a bit "fun" to get right, as there are many layers involved. Making sure seemingly unrelated changes in placement don't break the nova gate is important. Besides these unit tests, there's discussion on the PTG etherpad of running the nova functional tests, or a subset thereof, in placement's check run. On the one hand this is a pain and messy, but on the other consider what we're enabling: Functional tests that use the real functionality of an external service (real data, real web requests), not stubs or fakes. * <https://review.openstack.org/641404> Use ``code`` role in api-ref titles * <https://review.openstack.org/649618> Removing some unused code. # Other Service Users New discoveries are added to the end. Merged stuff is removed. Since last week 2 removals (by merge), 7 new discoveries. * <https://review.openstack.org/552924> Nova: Spec: Proposes NUMA topology with RPs * <https://review.openstack.org/622893> Nova: Spec: Virtual persistent memory libvirt driver implementation * <https://review.openstack.org/641899> Nova: Check compute_node existence in when nova-compute reports info to placement * <https://review.openstack.org/601596> Nova: spec: support virtual persistent memory * <https://review.openstack.org/#/q/topic:bug/1790204> Workaround doubling allocations on resize * <https://review.openstack.org/555081> Nova: Spec: Standardize CPU resource tracking * <https://review.openstack.org/646029> Nova: Spec: Use in_tree getting allocation candidates * <https://review.openstack.org/645316> Nova: Pre-filter hosts based on multiattach volume support * <https://review.openstack.org/606199> Ironic: A fresh way of looking at step retrieval * <https://review.openstack.org/647396> Nova: Add flavor to requested_resources in RequestSpec * <https://review.openstack.org/633204> Blazar: Retry on inventory update conflict * <https://review.openstack.org/640080> Nova: Use aggregate_add_host in nova-manage * <https://review.openstack.org/#/q/topic:bp/count-quota-usage-from-placement> Nova: count quota usage from placement * <https://review.openstack.org/#/q/topic:bug/1819923> Nova: nova-manage: heal port allocations * <https://review.openstack.org/624335> puppet-tripleo: Initial extraction of the Placement service from Nova * <https://review.openstack.org/#/q/topic:bug/1821824> Nova: bug fix prevent forbidden traits from working as expected * <https://review.openstack.org/648665> Nova: Spec for a new nova virt driver to manage an RSD * <https://review.openstack.org/#/c/642067/> Helm: Allow more generic overrides for nova placement-api * <https://review.openstack.org/647578> Nova: add spec for image metadata prefiltering * <https://review.openstack.org/609960> Support filtering of allocation_candidates by forbidden aggregates * <https://review.openstack.org/#/q/topic:bp/use-placement-in-tree> Enable in_tree allocation candidates from the nova side * <https://review.openstack.org/650143> openstack-ansible: Remove deprecated scheduler filters * <https://review.openstack.org/625284> Cyborg: Initially readme for nova pilot * <https://review.openstack.org/629142> Tempest: Add QoS policies and minimum bandwidth rule client * <https://review.openstack.org/641994> Nova-spec: Re-approve AMD SEV support for Train * <https://review.openstack.org/648687> Nova-spec: Add PENDING vm state # End Latency is the mind-killer. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent

1 0

[$cinder] Cinder Volume Active/Active Support
by vkalaitzis 05 Apr '19

05 Apr '19

I would like to ask if cinder-volume supports active/active setups. I found that there was a blueprint for adding support (https://blueprints.launchpad.net/cinder/+spec/cinder-volume-active-active-s…) but as far as I am concerned, no official documentation of such feature exists so far. Regards, Bill Vasilis Kalaitzis IT Systems Engineer Telefon: E-Mail: vasilis.kalaitzis(a)noris.gr

7 6