- openstack-discuss - lists.openstack.org

[Neutron][vxlan][nsx-v]
by Ignazio Cassano 17 Sep '19

17 Sep '19

Hello, I have a vmware vcenter installatiom with nsx-v and an openstack installation with kvm and openvswitch. I am looking for a method for realizing a vxlan shared between nsx-v and openvswitch. I know vmware released nsx-t but I prefer to use an opensource solution. Anyone could suggest a solution? Thanks Ignazio

1 0

[dev] [glance] proposal for S3 store driver re-support as galnce_store backend
by Naohiro Sameshima 17 Sep '19

17 Sep '19

Hi all, I know that glance_store had supported S3 backend until version OpenStack Mitaka, and it has already been removed due to lack of maintainers [1][2]. I started refactoring the S3 driver to work with version OpenStack Stein and recently completed it. (e.g. Add Multi Store Support, Using the latest AWS SDK) So, it would be great if glance_store could support the S3 driver again. However, I'm not familiar with the procedure for that. Would it be possible to discuss this? Thanks, Naohiro [1] https://docs.openstack.org/releasenotes/glance/newton.html [2] https://opendev.org/openstack/glance_store/src/branch/master/releasenotes/n…

4 3

[placement] update 19-35
by Chris Dent 17 Sep '19

17 Sep '19

HTML: https://anticdent.org/placement-update-19-36.html Here's placement update 19-36. There won't be one next week, I will be away. Because of my forthcoming "less time available for OpenStack" I will also be stopping these updates at some point in the next month or so so I can focus the limited time I will have on reviewing and coding. There will be at least one more. # Most Important The big news this week is that after returning from a trip (that meant he was away during the nomination period) Tetsuro has stepped up to be the PTL for placement in Ussuri. Thanks very much to him for taking this up, I'm sure he will be excellent. We need to work on useful documentation for the features developed this cycle. I've also made a [now worklist](https://storyboard.openstack.org/#!/worklist/754) in StoryBoard to draw attention to placement project stories that are relevant to the next few weeks, making it easier to ignore those that are not relevant now, but may be later. # Stories/Bugs (Numbers in () are the change since the last pupdate.) There are 23 (-1) stories in [the placement group](https://storyboard.openstack.org/#!/project_group/placement). 0 (0) are [untagged](https://storyboard.openstack.org/#!/worklist/580). 5 (0) are [bugs](https://storyboard.openstack.org/#!/worklist/574). 4 (0) are [cleanups](https://storyboard.openstack.org/#!/worklist/575). 10 (-1) are [rfes](https://storyboard.openstack.org/#!/worklist/594). 5 (1) are [docs](https://storyboard.openstack.org/#!/worklist/637). If you're interested in helping out with placement, those stories are good places to look. * Placement related nova [bugs not yet in progress](https://goo.gl/TgiPXb) on launchpad: 17 (0). * Placement related nova [in progress bugs](https://goo.gl/vzGGDQ) on launchpad: 6 (0). # osc-placement * <https://review.opendev.org/666542> Add support for multiple member_of. There's been some useful discussion about how to achieve this, and a consensus has emerged on how to get the best results. # Main Themes ## Consumer Types Adding a type to consumers will allow them to be grouped for various purposes, including quota accounting. * <https://review.opendev.org/#/q/topic:bp/support-consumer-types> This has some good comments on it from melwitt. I'm going to be away next week, so if someone else would like to address them that would be great. If it is deemed fit to merge, we should, despite feature freeze passing, since we haven't had much churn lately. If it doesn't make it in Train, that's fine too. The goal is to have it ready for Nova in Ussuri as early as possible. ## Cleanup Cleanup is an overarching theme related to improving documentation, performance and the maintainability of the code. The changes we are making this cycle are fairly complex to use and are fairly complex to write, so it is good that we're going to have plenty of time to clean and clarify all these things. Performance related explorations continue: * <https://review.opendev.org/#/c/679385/> Refactor initialization of research context. This puts the code that might cause an exit earlier in the process so we can avoid useless work. One outcome of the performance work needs to be something like a _Deployment Considerations_ document to help people choose how to tweak their placement deployment to match their needs. The simple answer is use more web servers and more database servers, but that's often very wasteful. * <https://review.opendev.org/#/q/owner:"Chris+Dent+%253Ccdent%2540anticdent.org%253E"+topic:build-pdf-docs> These are the patches for meeting the build pdf docs goal for the various placement projects. # Other Placement Miscellaneous changes can be found in [the usual place](https://review.opendev.org/#/q/project:openstack/placement+status:op…. There are three [os-traits changes](https://review.opendev.org/#/q/project:openstack/os-traits+status:… being discussed. And two [os-resource-classes changes](https://review.opendev.org/#/q/project:openstack/os-resource-class…. The latter are docs-related. # Other Service Users New reviews are added to the end of the list. Reviews that haven't had attention in a long time (boo!) or have merged or approved (yay!) are removed. * <https://review.opendev.org/662229> helm: add placement chart * <https://review.opendev.org/670112> Nova: WIP: Add a placement audit command * <https://review.opendev.org/670696> tempest: Add placement API methods for testing routed provider nets * <https://review.opendev.org/#/q/topic:bp/cross-cell-resize> Nova: cross cell resize * <https://review.opendev.org/674524> Nova: Scheduler translate properties to traits * <https://review.opendev.org/623558> Nova: single pass instance info fetch in host manager * <https://review.opendev.org/#/q/topic:bp/provider-config-file> Nova: using provider config file for custom resource providers * <https://review.opendev.org/681955> Nova: clean up some lingering placement stuff * <https://review.opendev.org/664867> OSA: Add nova placement to placement migration * <https://review.opendev.org/681343> Charms: Disable nova placement API in Train * <https://review.opendev.org/#/q/topic:bug/1841481> Nova: stop using @safe_connect in report client # End 🐈 -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent

2 1

[neutron] [neutron-lib] Change of in neutron-lib lead
by Miguel Lavalle 17 Sep '19

17 Sep '19

Dear Neutrinos, Many of you might have heard the Russel Boden's employer is changing his focus. As a consequence, Boden won't be able to continue leading our neutron-lib efforts. We want to thank you for the great job he has done over many cycles in advancing this sub-project. We are also looking for a volunteer to lead neutron-lib. Boden put together an etherpad with what needs to be done in the near future: https://etherpad.openstack.org/p/neutron-lib-volunteers-and-punch-list Regards Miguel

2 1

Open Infrastructure Summit Shanghai: Forum Submissions Open
by Jimmy McArthur 16 Sep '19

16 Sep '19

Hello Everyone! We are now accepting Forum [1] submissions for the 2019 Open Infrastructure Summit in Shanghai [2]. Please submit your ideas through the Summit CFP tool [3] through September20th. Don't forget to put your brainstorming etherpad up on the Shanghai Forum page [4]. This is not a classic conference track with speakers and presentations. OSF community members (participants in development teams, operators, working groups, SIGs, and other interested individuals) discuss the topics they want to cover and get alignment on and we welcome your participation. The Forum is your opportunity to help shape the development of future project releases. More information about the Forum [1]. Keep in mind, Forum submissions are for discussions, not presentations. The timeline for submissions is as follows: Sep 4th | Formal topic submission tool opens: https://cfp.openstack.org. Sep 20th | Deadline for proposing Forum topics. Scheduling committee meeting to make draft agenda. Sep 30th | Draft Forum schedule published. Crowd sourced session conflict detection. Forum promotion begins. Oct 7th | Scheduling committee final meeting Oct 14th | Forum schedule final Nov 4-6| Forum Time! If you have questions or concerns, please reach out to speakersupport(a)openstack.org <mailto:speakersupport@openstack.org>. Cheers, Jimmy [1] https://wiki.openstack.org/wiki/Forum [2] https://www.openstack.org/summit/shanghai-2019/ [3] https://cfp.openstack.org [4] https://wiki.openstack.org/wiki/Forum/Shanghai2019

1 1

[charms] no irc meeting today
by James Page 16 Sep '19

16 Sep '19

Hi Team Due to travel + events for most of the team there will be no Charms IRC meeting today. Cheers James

1 0

[cloudkitty] 13/09 meeting summary
by Luka Peschke 16 Sep '19

16 Sep '19

Hi everyone, This is the recap of the cloudkitty team IRC meeting that happened on 13/09. The logs can be found at [1]. All features patches we wanted to integrate have been merged for the feature freeze dealine. An experimental v2 storage driver for Elasticsearch has also been merged. Concerning the community goals: python3-first has been implemented early, however we're late for PDF docs generation, as we've got several issues when trying to generate PDF documentation, especially with tabs. A patch for cloudkitty has been proposed today [2]. Patches for the client and specs repos are to be done. They're our current top priority. From now on, the IRC meeting will be held twice every month, on the first and third monday at 14h UTC. This means that the next meeting will happen on october 7th. We plan to send a recap to this mailing list for each meeting. For the U cycle, we'd like to use storyboard a lot more. For now, it's been used for features and major bugs only, but we'll use it for every non-trivial patch from now on. Our temporary roadmap for U is the following: * Design and implement a new rating module. * Support time-based grouping in the /v2/summary endpoint. This would allow to easily create charts with cloudkitty's API. * [To be discussed] Stop differenciating "groupby" and "metadata" attributes, as these seem to be confusing for admins. * Port as many v1 API endpoints as possible to v2. Best regards, Luka Peschke (peschk_l) [1] http://eavesdrop.openstack.org/meetings/cloudkitty/2019/cloudkitty.2019-09-… [2] https://review.opendev.org/#/c/682364/

1 0

[requirements] [ironic] Bumping test-requirements on stable/train for the PDF goal?
by Dmitry Tantsur 16 Sep '19

16 Sep '19

Hi all, we (ironic) have a few deliverables that got the PDF goal fulfilled after stable/train was branched. Is it reasonable to still pursue the goal on stable/train even if it requires raising the openstackdoctheme requirement? An example is https://review.opendev.org/#/c/682274/ Thanks, Dmitry

2 1

[neutron] DevStack with IPv6
by Lucio Seki 16 Sep '19

16 Sep '19

Hi folks, I'm having troubles to ping6 a VM running over DevStack from its hypervisor. Could you please help me troubleshooting it? I deployed DevStack with NEUTRON_CREATE_INITIAL_NETWORKS=False, and manually created the networks, subnets and router. Following is my router: $ openstack router show router1 -c external_gateway_info -c interfaces_info +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | Field | Value | +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | external_gateway_info | {"network_id": "b87048ed-1be9-4f31-8d7e-fe74921aeec4", "enable_snat": true, "external_fixed_ips": [{"subnet_id": "28a00bc3-b30b-456f-b26a-44b50d37183f", "ip_address": "10.2.0.199"}, {"subnet_id": "a9729beb-b297-4fec-8ec3-7703f7f6f4bc", "ip_address": "fd12:67:1::3c"}]} | | interfaces_info | [{"subnet_id": "081e8508-4ceb-4aaf-bf91-36a1e22a768c", "ip_address": "fd12:67:1:1::1", "port_id": "75391abd-8ac8-41f8-acf8-3dfaf2a6b08f"}] | +-----------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ I'm trying to ping6 the following VM: $ openstack server list +--------------------------------------+---------+--------+------------------------------------------+--------+--------+ | ID | Name | Status | Networks | Image | Flavor | +--------------------------------------+---------+--------+------------------------------------------+--------+--------+ | 938854d0-80e9-45b2-bc29-8fe7651ffa93 | manila1 | ACTIVE | private1=fd12:67:1:1:f816:3eff:fe0e:17c3 | manila | manila | +--------------------------------------+---------+--------+------------------------------------------+--------+--------+ I intend to reach it via br-ex interface of the hypervisor: $ ip a show dev br-ex 9: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 0e:82:a1:ba:77:4c brd ff:ff:ff:ff:ff:ff inet6 fd12:67:1::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::c82:a1ff:feba:774c/64 scope link valid_lft forever preferred_lft forever The hypervisor has the following routes: $ ip -6 route fd12:67:1:1::/64 via fd12:67:1::3c dev br-ex metric 1024 pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium fe80::/64 dev br-ex proto kernel metric 256 pref medium fe80::/64 dev br-int proto kernel metric 256 pref medium fe80::/64 dev tapa5cf4799-9f proto kernel metric 256 pref medium And within the VM has the following routes: root@ubuntu:~# ip -6 route root@ubuntu:~# ip -6 route fd12:67:1::/64 via fd12:67:1:1::1 dev ens3 metric 1024 pref medium fd12:67:1:1::/64 dev ens3 proto kernel metric 256 expires 86360sec pref medium fe80::/64 dev ens3 proto kernel metric 256 pref medium default via fe80::f816:3eff:feb3:bd56 dev ens3 proto ra metric 1024 expires 260sec hoplimit 64 pref medium Though the ping6 from VM to hypervisor doesn't work: root@ubuntu:~# ping6 fd12:67:1::1 -c4 PING fd12:67:1::1 (fd12:67:1::1): 56 data bytes --- fd12:67:1::1 ping statistics --- 4 packets transmitted, 0 packets received, 100% packet loss I'm able to tcpdump inside the router1 netns and see that request packet is passing there, but can't see any reply packets: $ sudo ip netns exec qrouter-5172472c-bbe7-4907-832a-e2239c8badb4 tcpdump -l -i any icmp6 tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on any, link-type LINUX_SLL (Linux cooked), capture size 262144 bytes 21:29:29.351358 IP6 fd12:67:1:1:f816:3eff:fe0e:17c3 > fd12:67:1::1: ICMP6, echo request, seq 0, length 64 21:29:30.033316 IP6 fe80::f816:3eff:feb3:bd56 > fe80::f816:3eff:fe0e:17c3: ICMP6, neighbor solicitation, who has fe80::f816:3eff:fe0e:17c3, length 32 21:29:30.035807 IP6 fe80::f816:3eff:fe0e:17c3 > fe80::f816:3eff:feb3:bd56: ICMP6, neighbor advertisement, tgt is fe80::f816:3eff:fe0e:17c3, length 24 21:29:30.353646 IP6 fd12:67:1:1:f816:3eff:fe0e:17c3 > fd12:67:1::1: ICMP6, echo request, seq 1, length 64 21:29:31.355410 IP6 fd12:67:1:1:f816:3eff:fe0e:17c3 > fd12:67:1::1: ICMP6, echo request, seq 2, length 64 21:29:32.357239 IP6 fd12:67:1:1:f816:3eff:fe0e:17c3 > fd12:67:1::1: ICMP6, echo request, seq 3, length 64 The same happens from hypervisor to VM. I only acan see the request packets, but no reply packets. Thanks in advance, Lucio Seki

5 12

[openstack-dev] [neutron]IPv6 Prefix Delegation could not activated in newest version Neutron
by Shuai Zhao 16 Sep '19

16 Sep '19

Hi All, I'm working on validate the IPv6 PD in newest Neutron. What I want is to offer the Global Unified address to the VM and I find PD is the good solutions for me. I follow the guide *https://docs.openstack.org/neutron/latest/admin/config-ipv6.html <https://docs.openstack.org/neutron/latest/admin/config-ipv6.html> *to setup PD and dibbler-server and devstack, but I find I could not to trigger the PD process. The Dibbler server print nothing when attach the Subnet to router has external gateway. All procedure has recorded to the bug: https://bugs.launchpad.net/neutron/+bug/1844123. Thanks for your action and help in advance!

1 0

[neutron] Bug deputy report week of September 9th
by Miguel Lavalle 15 Sep '19

15 Sep '19

Hi, I was the bug deputy for the week of September 9th. Here's the list of what we got reported: Critical: - https://bugs.launchpad.net/neutron/+bug/1843413 neutron-tempest-iptables_hybrid-fedora job is failing with RETRY_LIMIT constantly Status: Assigned to slaweq. Job was made non-voting temporarily while bug is fixed High: - https://bugs.launchpad.net/neutron/+bug/1843478 Mitigate frequent fixtures._fixtures.timeout.TimeoutException in UTs and FTs Status: Assigned to ralonsoh: Proposed fix: https://review.opendev.org/#/c/681432/ Medium: - https://bugs.launchpad.net/neutron/+bug/1843418 Functional tests shouldn't fail if kill command will have "no such process" during cleanup Status: Assigned to ralonsoh. Proposed fix: https://review.opendev.org/#/c/681671/ - https://bugs.launchpad.net/neutron/+bug/1843425 br-int lose flows ephemerally due to unnecessary flow operation Status: In progress. Proposed fix: https://review.opendev.org/#/c/681462/ - https://bugs.launchpad.net/neutron/+bug/1843428 List port by mac address is case sensitive Status: Fix in progress. Proposed fix: https://review.opendev.org/#/c/681390 - https://bugs.launchpad.net/neutron/+bug/1843446 Implement "kill" operation using python method os.kill() Status: Assigned to ralonsoh: Proposed fix: https://review.opendev.org/#/c/681671/ - https://bugs.launchpad.net/neutron/+bug/1843870 ovsdb monitor ignores modified ports Status: proposed fix: https://review.opendev.org/#/c/681984 - https://bugs.launchpad.net/neutron/+bug/1843889 Windows: IPv6 tunnel endpoints Status: proposed fix: https://review.opendev.org/#/c/682031 Incomplete: - https://bugs.launchpad.net/neutron/+bug/1843359 The iptables rules are covered when add a port from the FW group Status: requested more data from submitter - https://bugs.launchpad.net/neutron/+bug/1843801 metadata-proxy process stops listening on port 80 Status: Incomplete. Submitter was directed to use haproxy >= 1.8.15 Invalid: - https://bugs.launchpad.net/neutron/+bug/1843379 Tagging is not work for tags of QoS Policy Status: submitter was using invalid resource for the request RFE: - https://bugs.launchpad.net/neutron/+bug/1843165 RFE: Adding support for direct ports with qos in ovs Status: Under discussion with submitter - https://bugs.launchpad.net/neutron/+bug/1843924 [RFE] Create optional bulk resource_extend Status: Under discussion with submitter

1 0

RE: Rabbitmq error report
by Md. Farhad Hasan Khan 15 Sep '19

15 Sep '19

Hi, [root@controller1 ~]# rabbitmqctl list_queues |grep notification notifications.debug 0 notifications.critical 0 notifications.error 0 notifications.info 0 notifications.warn 0 notifications.audit 0 notifications.sample 0 versioned_notifications.error 6 [root@controller1 ~]# From: Md. Farhad Hasan Khan Sent: Thursday, September 12, 2019 3:29 PM To: 'OpenStack Discuss' Subject: Rabbitmq error report Hi, I'm getting this error continuously in rabbitmq log. Though all operation going normal, but slow. Sometimes taking long time to perform operation. Please help me to solve this. rabbitmq version: rabbitmq_server-3.6.16 =ERROR REPORT==== 12-Sep-2019::13:04:55 === Channel error on connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672, vhost: '/', user: 'openstack'), channel 1: operation queue.declare caused a channel exception not_found: failed to perform operation on queue 'versioned_notifications.info' in vhost '/' due to timeout =WARNING REPORT==== 12-Sep-2019::13:04:55 === closing AMQP connection <0.8105.3> (192.168.21.56:60116 -> 192.168.21.11:5672 - nova-compute:3493037:e6757c9b-1cdc-43cd-bfd3-dcb58aa4974a, vhost: '/', user: 'openstack'): client unexpectedly closed TCP connection Thanks & B'Rgds, Rony

1 0

[keystone] Keystone Team Update - Week of 9 September 2019
by Colleen Murphy 14 Sep '19

14 Sep '19

# Keystone Team Update - Week of 9 September 2019 ## News ### Feature Freeze Status We have a number of policy changes and one spec implementation still crawling through the gate[1]. Since these have all been reviewed and approved we'll continue to babysit them until they have made it. Federated user attributes[2] and expiring group membership[3] are being deferred until next cycle due to insufficient reviews/incomplete implementation. [1[ https://etherpad.openstack.org/p/keystone-train-feature-freeze-todo [2] https://review.opendev.org/#/q/topic:bp/support-federated-attr [3] https://review.opendev.org/#/q/topic:bug/1809116 ## Office Hours When there are topics to cover, the keystone team holds office hours on Tuesdays at 17:00 UTC. The topic for next week's office hour will be: bug triage and prioritizing bugs for RC. The location for next week's office hour will be: https://meet.jit.si/keystone-office-hours Add topics you would like to see covered during office hours to the etherpad: https://etherpad.openstack.org/p/keystone-office-hours-topics ## Recently Merged Changes Search query: https://bit.ly/2pquOwT We merged 41 changes this week. ## Changes that need Attention Search query: https://bit.ly/2tymTje There are 51 changes that are passing CI, not in merge conflict, have no negative reviews and aren't proposed by bots. ### Priority Reviews https://etherpad.openstack.org/p/keystone-train-feature-freeze-todo ## Bugs This week we opened 5 new bugs and closed 7. Bugs opened (5) Bug #1843609 (keystone:High) opened by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1843609 Bug #1843464 (keystone:Medium) opened by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1843464 Bug #1843925 (keystone:Undecided) opened by Ben Nemec https://bugs.launchpad.net/keystone/+bug/1843925 Bug #1843903 (python-keystoneclient:Undecided) opened by Andrew Berezovskiy https://bugs.launchpad.net/python-keystoneclient/+bug/1843903 Bug #1843931 (oslo.policy:Medium) opened by Ben Nemec https://bugs.launchpad.net/oslo.policy/+bug/1843931 Bugs closed (1) Bug #1843903 (python-keystoneclient:Undecided) https://bugs.launchpad.net/python-keystoneclient/+bug/1843903 Bugs fixed (6) Bug #1750669 (keystone:High) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1750669 Bug #1805368 (keystone:Medium) fixed by Lance Bragstad https://bugs.launchpad.net/keystone/+bug/1805368 Bug #1805371 (keystone:Medium) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1805371 Bug #1818846 (keystone:Low) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1818846 Bug #1818850 (keystone:Low) fixed by Colleen Murphy https://bugs.launchpad.net/keystone/+bug/1818850 Bug #1805409 (keystone:Wishlist) fixed by Vishakha Agarwal https://bugs.launchpad.net/keystone/+bug/1805409 ## Milestone Outlook https://releases.openstack.org/train/schedule.html We're now past feature freeze and entering the RC period. Development focus should be on fixing bugs and helping to stabilize CI. RC1 will be cut in 2 weeks. We're also at requirements freeze, which means no new dependencies can be added and versions can't be changed. We're also at soft string freeze, so be mindful of checking that changes are not modifying strings. ## Help with this newsletter Help contribute to this newsletter by editing the etherpad: https://etherpad.openstack.org/p/keystone-team-newsletter

1 0

Execute a script on every object upload event (Swift+aodh)
by Anmar Salih 14 Sep '19

14 Sep '19

Hey all, Need help to configure swift and aodh. The idea is to trigger aodh alarm on very object upload event on swift. Once the alarm triggered, a small script should be executed. So the sequence of operations should be like this: 1- Object just uploaded to swift container 2- Alarm triggered by aodh 3- Once alarm triggered , execute python script. I am using Devstack Stein release installed on virtual box. Best regards. Anmar Salih

2 1

[all][PTL] Call for Cycle Highlights for Train
by Kendall Nelson 14 Sep '19

14 Sep '19

Hello Everyone! As you may or may not have read last week in the release update from Sean, its time to call out 'cycle-highlights' in your deliverables! As PTLs, you probably get many pings towards the end of every release cycle by various parties (marketing, management, journalists, etc) asking for highlights of what is new and what significant changes are coming in the new release. By putting them all in the same place it makes them easy to reference because they get compiled into a pretty website like this from Rocky[1] or this one for Stein[2]. We don't need a fully fledged marketing message, just a few highlights (3-4 ideally), from each project team. *The deadline for cycle highlights is the end of the R-5 week [3] on Sept 13th.* How To Reminder: ------------------------- Simply add them to the deliverables/train/$PROJECT.yaml in the openstack/releases repo similar to this: cycle-highlights: - Introduced new service to use unused host to mine bitcoin. The formatting options for this tag are the same as what you are probably used to with Reno release notes. Also, you can check on the formatting of the output by either running locally: tox -e docs And then checking the resulting doc/build/html/train/highlights.html file or the output of the build-openstack-sphinx-docs job under html/train/ highlights.html. Thanks :) -Kendall Nelson (diablo_rojo) [1] https://releases.openstack.org/rocky/highlights.html [2] https://releases.openstack.org/stein/highlights.html [3] https://releases.openstack.org/train/schedule.html <https://releases.openstack.org/train/schedule.html#t-cycle-highlights>

1 2

Re: [Release-job-failures] release-post job for openstack/releases for ref refs/heads/master failed
by Sean McGinnis 14 Sep '19

14 Sep '19

On Fri, Sep 13, 2019 at 04:07:54PM +0000, zuul(a)openstack.org wrote: > Build failed. > > - tag-releases https://zuul.opendev.org/t/openstack/build/c95672e425294127821c55ddf1176218 : RETRY_LIMIT in 1m 18s > - publish-tox-docs-static https://zuul.opendev.org/t/openstack/build/None : SKIPPED > > _______________________________________________ > Release-job-failures mailing list > Release-job-failures(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/release-job-failures Just to make sure there is a record of it - this was a temporary infrastructure sync issue that was quickly resolved. The job was reenqueued and everything completed fine. Looks like everything is now good and no further action is needed, but of course if anything odd is seen related to this, please let us know. Sean

1 0

[release][freezer][karbor][kuryr][magnum][manila][monasca][neutron][senlin][tacker][winstackers] Missing releases for some deliverables
by Thierry Carrez 13 Sep '19

13 Sep '19

Hi everyone, Quick reminder that we'll need a release very soon for a number of deliverables following a cycle-with-intermediary release model but which have not done *any* release yet in the Train cycle: - freezer and freezer-web-ui - karbor and karbor-dashboard - kuryr-kubernetes - magnum-ui - manila-ui - monasca-agent, monasca-api, monasca-ceilometer, monasca-events-api, monasca-log-api, monasca-notification, monasca-persister and monasca-transform - networking-hyperv - neutron-fwaas-dashboard and neutron-vpnaas-dashboard - senlin-dashboard - tacker-horizon Those should be released ASAP, and in all cases before September 26th, so that we have a release to include in the final Train release. Thanks in advance, -- Thierry Carrez (ttx)

3 2

[release] Release countdown for week R-4, September 16-20
by Sean McGinnis 13 Sep '19

13 Sep '19

Development Focus ----------------- We just passed feature freeze! Until release branches are cut, you should stop accepting featureful changes to deliverables following the cycle-with-rc release model, or to libraries. Exceptions should be discussed on separate threads on the mailing-list, and approved by the team's PTL. Focus should be on finding and fixing release-critical bugs, so that release candidates and final versions of the Train deliverables can be proposed, well ahead of the final Train release date. General Information ------------------- We are still finishing up processing a few release requests, but the Train release requirements are now frozen. If new library releases are needed to fix release-critical bugs in Train, you must request a Feature Freeze Exception (FFE) from the requirements team before we can do a new release to avoid having something released in Train that is not actually usable. This is done by posting to the openstack-discuss mailing list with a subject line similar to: [$PROJECT][requirements] FFE requested for $PROJECT_LIB Include justification/reasoning for why a FFE is needed for this lib. If/when the requirements team OKs the post-freeze update, we can then process a new release. A soft String freeze is now in effect, in order to let the I18N team do the translation work in good conditions. In Horizon and the various dashboard plugins, you should stop accepting changes that modify user-visible strings. Exceptions should be discussed on the mailing-list. By September 26 this will become a hard string freeze, with no changes in user-visible strings allowed. Actions --------- stable/train branches should be created soon for all not-already-branched libraries. You should expect 2-3 changes to be proposed for each: a .gitreview update, a reno update (skipped for projects not using reno), and a tox.ini constraints URL update. Please review those in priority so that the branch can be functional ASAP. The Prelude section of reno release notes is rendered as the top level overview for the release. Any important overall messaging for Train changes should be added there to make sure the consumers of your release notes see them. Finally, if you haven't proposed Train cycle-highlights yet, you are already late to the party. Please see http://lists.openstack.org/pipermail/openstack-discuss/2019-September/00913… for details. Upcoming Deadlines & Dates -------------------------- RC1 deadline: September 26 (R-3 week) Final RC deadline: October 10 (R-1 week) Final Train release: October 16 Forum+PTG at Shanghai summit: November 4

1 0

[goal][python3] Train unit tests weekly update (goal-0)
by Corey Bryant 13 Sep '19

13 Sep '19

This is the goal-0 weekly update for the "Update Python 3 test runtimes for Train" goal [1]. Today is the final day for completion of Train community goals [2]. == How can you help? == If your project has failing tests please take a look and help fix. Python 3.7 unit tests will be self-testing in Zuul. Failing patches: https://review.openstack.org/#/q/topic:python3-train +status:open+(+label:Verified-1+OR+label:Verified-2+) If your project has patches with successful tests please help get them merged. Open patches needing reviews: https://review.openstack.org/#/q/topic:python3 -train+is:open Patch automation scripts needing review: https://review.opendev.org/#/c/666934 == Ongoing Work == We're down to 3 projects with failing tests, and 2 projects with successful tests. Barbican and PowerVM are actively working on getting patches landed. I've not been successful in making contact with the Freezer PTL. Thank you to all who have contributed their time and fixes to enable patches to land! == Completed Work == All patches have been submitted to all applicable projects for this goal. Merged patches: https://review.openstack.org/#/q/topic:python3-train +is:merged == What's the Goal? == To ensure (in the Train cycle) that all official OpenStack repositories with Python 3 unit tests are exclusively using the 'openstack-python3-train-jobs' Zuul template or one of its variants (e.g. 'openstack-python3-train-jobs-neutron') to run unit tests, and that tests are passing. This will ensure that all official projects are running py36 and py37 unit tests in Train. For complete details please see [1]. == Reference Material == [1] Goal description: https://governance.openstack.org/tc/goals/train/ python3-updates.html [2] Train release schedule: https://releases.openstack.org/train /schedule.html (see R-5 for "Train Community Goals Completed") Storyboard: https://storyboard.openstack.org/#!/story/2005924 Porting to Python 3.7: https://docs.python.org/3/whatsnew/3.7.html#porting-to-python-3-7 Python Update Process: https://opendev.org/openstack/governance/src/branch/master/resolutions/2018… Train runtimes: https://opendev.org/openstack/governance/src/branch/master/reference/runtim… train.rst Thanks, Corey

1 0

[tc][uc][meta-sig] How to help SIGs to have a better life? (Needs feedback for SIGs guideline)
by Rico Lin 13 Sep '19

13 Sep '19

Hi all, The question I would like to ask is, what else we can do here to help SIGs to have a better life? What can we do from here? And is there any feedback regarding on experience of participate a SIG or chairing one? For some work in progress (or completed) actions: I'm working on a guideline for SIGs ( https://etherpad.openstack.org/p/SIGs-guideline ) because I believe it might provide some value for SIGs, especially new-formed SIGs. Please kindly provide your feedback on it. Will send a patch to update current document under governance-sigs once we got good enough confident on it. On the other hand, the reason I start this work is because we're thinking `How to help SIGs to have a better life?` There're some actions I can think of and the most easier answers are to get SIGs status, update guidelines and explain why we need SIG in general. So actions: I'm working on SIG guideline ( https://etherpad.openstack.org/p/SIGs-guideline ) and document `Comparison of Official Group Structures` ( https://review.opendev.org/#/c/668093/ ). Also, reach out to SIGs earlier this year to collect help most needed information for SIGs and WGs ( https://etherpad.openstack.org/p/DEN-help-most-needed-for-sigs-and-wgs ) Also, I know Belmiro Moreira (UC member) has reached out to SIGs too, so there are some up to date information. I will try to put all the above information together for share. And now, back to the question, what can we do from here? Or is there any other feedback? Before I start to disturb everyone with crazy ideas in my mind, would like to hear feedback from all of you. Finally, feedback on SIG guideline is desired. Thanks! -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

2 1

[openstack-dev] [neutron] Cancelling Neutron Drivers meeting on September 13th
by Miguel Lavalle 13 Sep '19

13 Sep '19

Dear Neutrinos, We don't have RFEs ready to be discussed during this week's drivers meeting. As a consequence, let's skip it. However, last week we discussed https://bugs.launchpad.net/neutron/+bug/1837847 and asked the submitter to write a spec, which he did: https://review.opendev.org/#/c/680990/. Please review it and let's be ready to go back the this RFE during the meeting on the 20th Best regards Miguel

1 0

Re: [nova] Deprecating the XenAPI driver
by James Benson 13 Sep '19

13 Sep '19

Matt, I am currently working on trying to deploy Xen OpenStack. Currently I have been trying to get it working on Rocky with Xen6.0 and will code fix for Stein/Train as well if possible. Trying to get a working solution with Rocky then will patch up the line. I have reached out to the last person who submitted a bug fix in Xen (with no response), but I am actively trying to get this working. Unfortunately it is a one-man job, so it is taking a lot of time. Currently facing issues with Nova and Neutron. James

3 2

Re: [Openstack-stable-maint] Stable check of openstack/swift for ref refs/heads/stable/pike failed
by Tim Burke 12 Sep '19

12 Sep '19

Wrote up https://bugs.launchpad.net/swift/+bug/1843816 to describe the issue; tl;dr is that python's http.client/httplib got more picky about sending only RFC-compliant HTTP requests, but Swift's proxy was happy to accept non-compliant query strings and try to forward them on to backend servers. Fix for master is up at https://review.opendev.org/#/c/681875/, and a backport for pike is up at https://review.opendev.org/#/c/681879/. Once I see passing checks there, I'll propose backports for everyone in between, plus ocata. Tim On Wed, 2019-09-11 at 06:43 +0000, A mailing list for the OpenStack Stable Branch test reports. wrote: > Build failed. > > - build-openstack-sphinx-docs > https://zuul.opendev.org/t/openstack/build/d7030406f5224d78baebbe5dbe80b4d5 > : SUCCESS in 6m 39s > - openstack-tox-py27 > https://zuul.opendev.org/t/openstack/build/a4ee29fb61684505995fda21718fcd89 > : FAILURE in 7m 15s > > _______________________________________________ > Openstack-stable-maint mailing list > Openstack-stable-maint(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-stable-maint

1 0

[oslo][release][requirements] FFE request for oslo.policy, privsep, and service
by Ben Nemec 12 Sep '19

12 Sep '19

Hi, As discussed in the release meeting today, I'm requesting an FFE for oslo.policy, oslo.privsep, and oslo.service. The latter two are only release notes for things that landed late in the cycle, and oslo.policy is a small bugfix in sample policy generation. These should all be backportable if necessary, but for convenience we'd like to get them out now. Thanks. -Ben

2 1

[openstack-ansible] office hours update
by Mohammed Naser 12 Sep '19

12 Sep '19

Hi everyone, Here’s the update of what happened in this week’s OpenStack Ansible Office Hours. We finished installing the Python3 for ansible-runtime virtual environment. We discussed how Centos 7.7 wasn’t out yet but we want to move to Python 3 so we’ll start using the CR repository. The placement extract and upgrade jobs are in progress. We clarified the whole definition around freezing a milestone and features and what it implies. The roles for Train milestones were frozen. We’ll wait for Python3, placement and bind-to-mgmt before proposing the milestone. Galera is still having issues and we’re having trouble understanding and fixing them but it has something to do with listening to localhost. We tested Ansible 2.9 and are trying to figure out if we want to use it for Train. We’re having issues with bumping up os-vif for Stein because they seem to be only for testing according to OpenStack Requirements. We talked about maybe using the in-repository local constraints or creating a tag, but we don’t think they can be bumped. It seems later that it was clarified that we can do that, and os-vif made a new release today so we can check it out. Finally, we discussed a journal logging error on Stein. There’s a case of python-systemd missing for logging. Thanks! Regards, Mohammed -- Mohammed Naser — vexxhost ----------------------------------------------------- D. 514-316-8872 D. 800-910-1726 ext. 200 E. mnaser(a)vexxhost.com W. http://vexxhost.com

1 0