July 2020 - openstack-discuss - lists.openstack.org

[cinder] monthly video meeting poll results
by Brian Rosmaita 11 Jul '20

11 Jul '20

tl;dr - our first video meeting will be Wednesday 29 July connection info will be on the agenda etherpad, https://etherpad.opendev.org/p/cinder-victoria-meetings For those who didn't see the poll, this is what it was about: We're considering holding the Cinder weekly meeting as a video conference once each month. It will be the last meeting of each month and will take place at the regularly scheduled meeting time (1400 UTC for 60 minutes). Video Meeting Rules: * Everyone will keep IRC open during the meeting. * We'll take notes in IRC to leave a record similar to what we have for our regular IRC meetings. * Some people are more comfortable communicating in written English. So at any point, any attendee may request that the discussion of the current topic be conducted entirely in IRC. The results: Do it? - 50% in favor, 33% in strong favor, 17% don't care, no one opposed. Record? - 50% yes, 50% don't care Conferencing software? - Bluejeans: first choice of 70% of respondents Comments - Let's work hard to write what we speak! - people who don't want to be recorded can turn their camera off - video conference plus IRC is for sure better than IRC only - Zoom is shady and possibly not appropriate for an open source project that wants to welcome contributors from all countries. I think we're better off avoiding it. Conclusion: We'll hold the Cinder weekly meeting for 29 July in BlueJeans *and* IRC following the ground rules laid out above, and continue doing the same for the last meeting of each month through the end of the Victoria cycle. The meetings will be recorded.

2 1

[kolla] PTL holiday
by Mark Goddard 11 Jul '20

11 Jul '20

Hi, I will be on holiday next Tuesday (14th) to Thursday (16th). I will therefore miss both the IRC meeting and Kolla Klub. If someone is able to chair the IRC meeting, please reply here. There is currently nothing on the agenda for the Klub, so anyone looking to chair that meeting will also need to find some topics to cover. We have suggestions in [1]. Cheers, Mark [1] https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_…

2 1

[loci][helm][k8s] When do images on docker.io get updated
by info＠dantalion.nl 10 Jul '20

10 Jul '20

Hello, the images on docker.io have last been updated 9 months ago https://hub.docker.com/u/loci, I was wondering when do they get updated? As I am currently waiting for the image for Watcher to be available, this image has recently been added as gate job. I require this image in order for the OpenStack helm charts to test https://review.opendev.org/#/c/720140/. Kind regards, Corne lukken

2 2

[blazar] IRC meetings cancelled next week
by Pierre Riteau 10 Jul '20

10 Jul '20

Hello, As I will be on holiday next week (July 13-17), I have proposed that both IRC meetings are cancelled. We will meet again on Tuesday July 21 for EMEA and Thursday July 30 for Americas. Cheers, Pierre (priteau)

1 0

OpenStack cluster event notification
by Anil Jangam 10 Jul '20

10 Jul '20

Hi All, So far, based on my understanding of OpenStack Python SDK, I am able to read the Hypervisor, Servers instances, however, I do not see an API to receive and handle the change notification/events for the operations that happens on the cluster e.g. A new VM is added, an existing VM is deleted etc. I see a documentation, which talks about emitting notifications over a message bus that indicate different events that occur within the service. Notifications in OpenStack <https://docs.openstack.org/ironic/latest/admin/notifications.html> https://docs.openstack.org/ironic/latest/admin/notifications.html 1. Does Openstack Python SDK support notification APIs? 2. How do I receive/monitor notifications for VM related changes? 3. How do I receive/monitor notifications for compute/hypervisor related changes? 4. How do I receive/monitor notifications for Virtual Switch related changes? Thanks in advance for any help in this regard. /anil.

3 4

[all][InteropWG] weekly Friday call - request for Partciapation
by prakash RAMCHANDRAN 10 Jul '20

10 Jul '20

Hi all, We have the agenda listed on https://etherpad.opendev.org/p/interop Call is now moved to meetpad and will be easy to acess and try it out today in next 10-15 minutes if you find time and interest. OpenStack / Open Infra -interopWGInterop Working Group - Weekly Friday 10-11 AM or UTC 17-18 Lnink: https://meetpad.opendev.org/Interop-WG-weekly-meeting ThanksPrakash

1 0

[release] Release countdown for week R-13 July 13 - July 17
by Sean McGinnis 10 Jul '20

10 Jul '20

Development Focus ----------------- The Victoria-2 milestone will happen in a few weeks, on July 30. Victoria-related specs should now be finalized so that teams can move to implementation ASAP. Some teams observe specific deadlines on the second milestone (mostly spec freezes): please refer to https://releases.openstack.org/victoria/schedule.html for details. General Information ------------------- Please remember that libraries need to be released at least once per milestone period. At milestone 2, the release team will propose releases for any library that has not been otherwise released since milestone 1. Other non-library deliverables that follow the cycle-with-intermediary release model should have an intermediary release before milestone-2. Those who haven't will be proposed to switch to the cycle-with-rc model, which is more suited to deliverables that are released only once per cycle. At milestone-2 we also freeze the contents of the final release. If you have a new deliverable that should be included in the final release, you should make sure it has a deliverable file in: https://opendev.org/openstack/releases/src/branch/master/deliverables/victo… You should request a beta release (or intermediary release) for those new deliverables by milestone-2. We understand some may not be quite ready for a full release yet, but if you have something minimally viable to get released it would be good to do a 0.x release to exercise the release tooling for your deliverables. See the MembershipFreeze description for more details: https://releases.openstack.org/victoria/schedule.html#v-mf Finally, now may be a good time for teams to check on any stable releases that need to be done for your deliverables. If you have bugfixes that have been backported, but no stable release getting those. If you are unsure what is out there committed but not released, in the openstack/releases repo, running the command "tools/list_stable_unreleased_changes.sh <cycle_name>" gives a nice report. Upcoming Deadlines & Dates -------------------------- Victoria-2 milestone: July 30

1 0

[neutron] Team meeting - day change proposal
by Slawek Kaplonski 10 Jul '20

10 Jul '20

Hi, During our last Monday team meeting I proposed to cancel this bi-weekly Monday meeting and have weekly meeting on Tuesday always. It is officially proposed in https://review.opendev.org/#/c/739780/ - if You usually attends those meetings and You didn’t check it yet, please do and give +1 if You are ok with such change. Thx in advance. — Slawek Kaplonski Principal software engineer Red Hat

1 0

Neutron Agent Migration
by Johannes Scheuermann 10 Jul '20

10 Jul '20

Hi together, currently we exploring how we can reboot a compute node without any interruptions for the networking stack. We run Openstack Train with ml2 driver Linux bridge and dnsmasq for DHCP and internal DNS. The DHCP setup runs as high availability setup with 3 replicas. During our tests we identified the following challenges: 1.) If we reboot the machine without doing anything on the network layer all ports will be rescheduled. Also the networks will be removed from the (dead) agent and will be reassigned to another agent. But for each reboot we have some leftover ports with the device-id "reserved_dhcp_port". These ports can safely deleted (we haven't figured out where the issue in the neutron code is). 2.) If we disable the network agent like described here: https://docs.openstack.org/neutron/train/admin/config-dhcp-ha.html and then remove the disabled agent from all networks we have an even worse behaviour since the neutron scheduler doesn't reschedule the network to a different agent. So what is the correct way to ensure that the reboot of a node has no (or only small) interruptions to the networking service? The current issue is that if we remove one agent we might remove the port that is the first entry in the clients (VM's) resolv.conf which means that each request will be delayed by the default timeout. And is there any option to "migrate" a network from one agent to another? Thanks in advance, Johannes Scheuermann

2 1

[manila][stable] moving some stable branches to EOL
by Goutham Pacha Ravi 10 Jul '20

10 Jul '20

Hello Stackers, There have been no changes to the stable/ocata [1], driverfixes/mitaka [2], driverfixes/newton [3] and driverfixes/ocata [4] branches of openstack/manila in a year [1] and the manila team today decided [2] that it was time to close this branches. While we routinely get requests from users, vendors and distributions to backport bug fixes to older releases, no one seems to want any further changes in these branches. We'd also like stable/pike to be EOL'ed, the last change to that branch was a CVE fix made three months ago. Keeping these branches open may give the impression that we'd continue to take backports in, and support them with bugfixes, when the reality is that we're struggling to keep meaningful testing in stable/queens and stable/rocky branches - something we've seen most bugfix/backport requests for. If there are no objections, I'll propose an EOL patch and request the infra team to help delete these branches. Thanks, Goutham [1] https://opendev.org/openstack/manila/commits/branch/stable/ocata [2] https://opendev.org/openstack/manila/src/branch/driverfixes/mitaka [3] https://opendev.org/openstack/manila/src/branch/driverfixes/newton [4] https://opendev.org/openstack/manila/src/branch/driverfixes/ocata [2] http://eavesdrop.openstack.org/meetings/manila/2020/manila.2020-07-09-15.01…

1 0