March 2019 - openstack-discuss - lists.openstack.org

[vitrage] Problem when execute mistral with get_atrr() function
by hoanq13＠viettel.com.vn 24 Mar '19

24 Mar '19

I try doing use case with vitrage notification execute mistral but got a problem: In my use case, i try evacuate host with 2 instance "vm_1" and "vm_2" on it, when host have alarm -then evacuate instance: ``` condition: nova_compute_down_on_host and host_contain_instance actions: - action: action_type: execute_mistral properties: workflow: evacuate_vm input: vm_name: get_attr(instance, name) ``` I expect m istral workflow will then be: execute workflow 2 times with input: ```vm_name: vm_1``` and ```vm_name: vm_2``` But i alway get : mistral execute that workflow 2 times with input: ```vm_name: vm_1``` and ```vm_name: vm_1``` When i turn on debug log, to see the line "Function get_attr called with template_id..." follow " https://github.com/openstack/vitrage/blob/stable/queens/vitrage/evaluator/t… " I saw that line appear only one time! I don't know it is bug or not, can u help me? (my vitrage in queens version) Best regards.

4 5

[Neutron] Question on uwsgi based web server support for neutron
by Le, Huifeng 24 Mar '19

24 Mar '19

Miguel, During STX deployment process, it is found the current neutron eventlet based web server has some unexpected behavior for multiple long live clients and it is also verified that apache WSGI/uwsgi based web server can solve such issues. the detail information of this issue can be found at https://bugs.launchpad.net/neutron/+bug/1800599. So is there any plan or roadmap to switch to the new apache WSGI/uswgi based web server for Neutron in Stein release? Thanks much! Best Regards, Le, Huifeng

3 6

openstack-dev@lists.openstack.org bounces
by Fox, Kevin M 23 Mar '19

23 Mar '19

Is it time to setup openstack-dev(a)lists.openstack.org to bounce emails rather then send them to a list where the community isn't listening anymore on? I still see folks use it occasionally by mistake. Thanks, Kevin

2 2

[dev][keystone] Keystone Team Update - Week of 18 March 2019
by Colleen Murphy 23 Mar '19

23 Mar '19

# Keystone Team Update - Week of 18 March 2019 ## News ### Release Candidates We released our Stein RC1 this week[1]! Please test it and report any issues ASAP. We've concluded that we'll be going for an RC2. I've tagged bugs that are either fairly critical or close to done for RC2[2]. We're also tracking patches we want to have merged for RC2[3]. We can submit a new release candidate proposal either when those are closed and merged or in time for the final release deadline[4], whichever comes first. There is also now a stable/stein branch, so please remember that all changes that are intended for RC2 need to be backported to stable/stein. [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/004093.ht… [2] https://launchpad.net/keystone/+milestone/stein-rc2 [3] https://etherpad.openstack.org/p/keystone-stein-rc2-tracking [4] https://releases.openstack.org/stein/schedule.html#s-finalrc ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 35 changes this week, including some important Python3 fixes, some system scope updates and several Rocky backports. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 47 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. Please give particular attention to the reviews that are fixing RC bugs or implementing system scope/default roles functionality. ## Bugs This week we opened 1 new bugs and closed 4. Bugs opened (1) Bug #1820367 (keystone:Undecided) opened by srinig81 https://bugs.launchpad.net/keystone/+bug/1820367 Bugs closed (1) Bug #1820367 (keystone:Undecided) https://bugs.launchpad.net/keystone/+bug/1820367 Bugs fixed (3) Bug #1750660 (keystone:High) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1750660 Bug #1819036 (keystone:High) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1819036 Bug #1820333 (keystone:High) fixed by Corey Bryant https://bugs.launchpad.net/keystone/+bug/1820333 ## Milestone Outlook https://releases.openstack.org/stein/schedule.html The final RC is due in two weeks and the Stein release will follow that. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

Re: [openstack-dev] [nova] Volunteer needed to write reshaper FFU hook
by Eric Fried 23 Mar '19

23 Mar '19

Is it time to resurrect this now that we're getting close to having a release which reshapes when you upgrade to it? Eric Fried > On Oct 29, 2018, at 22:29, Zhenyu Zheng <zhengzhenyulixi(a)gmail.com> wrote: > > I would like to help since I have now finished all the downstream works. But I may need to take some time understanding all the background information > >> On Mon, Oct 29, 2018 at 11:25 PM Matt Riedemann <mriedemos(a)gmail.com> wrote: >> Given the outstanding results of my recruiting job last week [1] I have >> been tasked with recruiting one of our glorious and most talented >> contributors to work on the fast-forward-upgrade script changes needed >> for the reshape-provider-tree blueprint. >> >> The work item is nicely detailed in the spec [2]. A few things to keep >> in mind: >> >> 1. There are currently no virt drivers which run the reshape routine. >> However, patches are up for review for libvirt [3] and xen [4]. There >> are also functional tests which exercise the ResourceTracker code with a >> faked out virt driver interface to test reshaping [5]. >> >> 2. The FFU entry point will mimic the reshape routine that will happen >> on nova-compute service startup in the ResourceTracker [6]. >> >> 3. The FFU script will need to run per-compute service rather than >> globally (or per cell) since it actually needs to call the virt driver's >> update_provider_tree() interface which might need to inspect the >> hardware (like for GPUs). >> >> Given there is already a model to follow from the ResourceTracker this >> should not be too hard, the work will likely mostly be writing tests. >> >> What do you get if you volunteer? The usual: fame, fortune, the respect >> of your peers, etc. >> >> [1] >> http://lists.openstack.org/pipermail/openstack-dev/2018-October/136075.html >> [2] >> https://specs.openstack.org/openstack/nova-specs/specs/stein/approved/resha… >> [3] https://review.openstack.org/#/c/599208/ >> [4] https://review.openstack.org/#/c/521041/ >> [5] >> https://github.com/openstack/nova/blob/a0eacbf7f/nova/tests/functional/test… >> [6] >> https://github.com/openstack/nova/blob/a0eacbf7f/nova/compute/resource_trac… >> >> -- >> >> Thanks, >> >> Matt >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

1 0

[dev][ptl][tempest-plugins][release] Reminder to release Tempest-plugins for stein if not done yet
by Ghanshyam Mann 22 Mar '19

22 Mar '19

Hello Everyone, you might have seen the release countdown email from Sean[1]. All tempest-plugins follow 'cycle-with-intermediary' release model and if you have not done the release for your tempest-plugin for stein, or want to do final release, it's time to push the release before Monday (25th). NOTE: you do not need to cut the stable/stein in the release as tempest-plugins are branchless. In case of any query, ping me or release team or follow these example - https://review.openstack.org/#/c/645399/ - https://review.openstack.org/#/c/645237/ [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-March/004100.ht… -gmann

1 0

mistral-extra 8.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for mistral-extra for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral-extra/ 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/mistral-extra/log/?h=stable/stein Release notes for mistral-extra can be found at: https://docs.openstack.org/releasenotes/mistral-extra/

1 0

mistral 8.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for mistral for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral/ 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/mistral/log/?h=stable/stein Release notes for mistral can be found at: https://docs.openstack.org/releasenotes/mistral/

1 0

mistral-dashboard 8.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for mistral-dashboard for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/mistral-dashboard/ 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/mistral-dashboard/log/?h=stable/st… Release notes for mistral-dashboard can be found at: https://docs.openstack.org/releasenotes/mistral-dashboard/

1 0

storlets 3.0.0.0rc1 (stein)
by no-reply＠openstack.org 22 Mar '19

22 Mar '19

Hello everyone, A new release candidate for storlets for the end of the Stein cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/storlets/ 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/storlets/log/?h=stable/stein Release notes for storlets can be found at: https://docs.openstack.org/releasenotes/storlets/

1 0