October 2020 - openstack-discuss - lists.openstack.org

[heat] propose to move meeting time to Wednesday at 1400 UTC in #heat
by Rico Lin 29 Oct '20

29 Oct '20

Hi all as our current members are changed, I would like to propose we move our meeting time [1] one hour later. >From Weekly on Wednesday at *1300* UTC in #heat to Weekly on Wednesday at *1400* UTC in #heat Which I believe will be easier for US forks to join. [1] http://eavesdrop.openstack.org/#Heat_(Orchestration)_Team_Meeting -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

2 1

[nova] Weekly meeting canceled
by Balázs Gibizer 29 Oct '20

29 Oct '20

Hi, Today's meeting is canceled in favor of the PTG session. See you there. Cheers, gibi

1 0

[Openstack][Queens] iscsi unity driver
by Ignazio Cassano 28 Oct '20

28 Oct '20

Hello, I installed queens on centos7 with cinder unity iscsi driver. When volume are detached for example for a live migration, faulty devices are left on compute nodes. Must I configure iscsi initiator on both compute and controllers nodes? At this time I configured it only on compute nodes. Faulty could be an os brick module issue ? Thanks Ignazio

1 0

[ironic] Reviewing changes post-gerrit admin account compromise
by Julia Kreger 28 Oct '20

28 Oct '20

Greetings folks, Per the opendev notice that was published on the gerrit outage and compromise[0], I believe it is only prudent to sift through the changes published and verify if their content looks okay and that they were published as we expect. As we have a number of repositories, branches, and ultimately change sets to check, I've created a spreadsheet to help us track and coordinate the work[1]. In the interest of transparency, it is publicly viewable, but I've only shared editing ability with the members of ironic-core. Arne, unfortunately I don't see a google account for yourself, if you have an account you want me to add, let me know! Ironic-cores: If someone wishes to help, I personally think that is okay, but if you feel the need to update editing privileges on the document, please just reply to the mailing list so we have it on the record that this is the case. If I missed a branch that needs to be checked, just add it to the list. Same for any project repositories. And same goes for tabs. Copy/paste is likely easiest. Thanks everyone! -Julia [0]: http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html [1]: https://docs.google.com/spreadsheets/d/1-_on0DOpS4gRriAnpdoLf2B7K98RZN7hNAP…

1 1

[policy] Wallaby Virtual Forum & PTG Summary
by Ghanshyam Mann 28 Oct '20

28 Oct '20

Hello Everyone, 'policy' popup team hosted 2 sessions in Wallaby Virtual PTG to discuss the progress and next steps. Forum: ===== https://etherpad.opendev.org/p/consistent-and-secure-default-policies-walla… Progress: * Three projects completed till now - Keystone, Nova and, Cyborg * One in progress - Barbican * Planning in Wallaby - Neutron, Manila We discussed the current and possible future challenges while migrating to the new policy. policy file in JSON format is one know and we talked about a current workaround and long term plan. Deprecation warnings are still an issue and a lot of warnings are logged. This is logged as a bug in nova[1]. Also, the HTML version of the policy doc does not have the deprecation rule and reason. Example: https://docs.openstack.org/nova/latest/configuration/policy.html We need to add it in these docs too. A clear step by step document about how to use system scope in cloud.yaml as well as in general with all migration steps are much needed. We also asked if any deployment is migrated to new policy but there is none yet. PTG: ==== https://etherpad.opendev.org/p/policy-popup-wallaby-ptg We carried the Forum sessions discussion in PTG with few extra topics. Migrate Default Policy Format from JSON to YAML (All projects) -------------------------------------------------------------------------------- We talked about it and decided that it will be great to do this in advance before projects start moving towards the new policy. and having this as a community goal in wallaby will help this effort to move faster. I have proposed this as a goal in TC PTG and it was agreed to select it for wallaby. - Goal proposal: https://review.opendev.org/#/c/759881/2 We also need to update devstack for the neutron policy file which is policy.json. Deprecation warning on-demand based on config option? ----------------------------------------------------------------------- There is no best solution for deprecation warnings when it is a lot in case of new policy work. We cannot stop logging warnings completely. We discussed an option to provide a config option to disable the warnings (enable by default) and only for default value change, not the policy name change. The policy name change is a little critical even in policy overridden case also that is why we should not make it switchable. This way operators can disable warnings after seeing it for the first time and if it is too noisy. New policy in Horizon ---------------------------- It is challenging to adopt new policy in Horizon when some projects have new policies and some not. We left this for now and will continue brainstorming once we do some investigation on the usage of system token for new policy and old one. For now, amotoki proposed a workaround to keep the policy file with the deprecated rule as the overridden rules. - https://review.opendev.org/#/c/750134/ What are the expectations from project teams? ----------------------------------------------------------- In the end, we discussed what all things to be targeted as part of new policy work and what all as a separate effort. Below is the list and I will be documenting it on wiki. Things to do as part of new policy effort: - Migrating JSON to YAML (in advance though) - Policy Tests coverage - System scoped administrator policy support and "reader" role support - upgrade-check support when changing the default policy As separate effort: - Remove hard-coded admin checks in the API/DB/"Views" - Standardizing policy names (depends on projects) [1] https://bugs.launchpad.net/nova/+bug/1900451 -gmann

1 0

[qa] Wallaby Virtual PTG Summary
by Ghanshyam Mann 28 Oct '20

28 Oct '20

Hello Everyone, I am summarizing the discussion QA team had in PTG and action items for quick ref. Victoria Retrospective: ----------------------------- We talked about the retrospective of the last cycle, one main challenge we discussed is the slow review in QA due to fewer contributors. Below are the action items that came up from improving things: * Action: - microversion need more work also when you try more combination or latest (gmann). - Triage bugs in the office hour as 30 min -> update agenda - Speed up the review. Office hour schedule: --------------------------- With daylight ending in Nov, we decided to shift the QA office hour by an hour late which is at 14 UTC. Move back the single horizon test in tempest tree from tempest-horizon: ------------------------------------------------------------------------------------------- Tempest and Horizon team decided to bring back the single horizon test to Tempest tree and retire the tempest-horizon plugins which was too much maintenance for single tests. It is unlikely to happen but if Tempest team in future plan to remove this test then it needs to be consulted with Horizon team first. * Action: - Move test back to Tempest - gmann - Deprecate and retire tempest-horizon - amotoki - Check with the release team if any other release needed. (amotoki + gmann) - modify the 'horizon-dsvm-tempest-plugin' job to direct to tests' new location Add run_validation as a centralized point for Tempest scenario tests: ------------------------------------------------------------------------------------- For now, validation resources automation and skip ssh part via run_validation is done in API test only and this proposal is to extend it to scenario tests also. There is no reason not to do that which will help to run tempest scenario tests on images where ssh is not allowed. There is a most possible situation where complete tests need to be skipped but we will see case by case and at least skipping automatically will help tester to avoid explicitly excluding the scenario tests to the skip list. *Action: - Implement it in scenario tests - paras333 - Refactor scenario manager's create_server method to consume common/compute.py - paras333 Patrole stable release: ---------------------------- We are lacking the maintainer in Patrole project which is a big challenge to release a stable version of it. Sonia and doug (already helping) will try to spend more bandwidth in Patrole. Another thing to reduce the Patrole tests execution time. We discussed a few options like policy engine to return the API based on the flag or use fake driver etc but we did not conclude any option yet as they need more investigation. * Action: - Keep eyes on gate and how tests are running and based on that we can make a stable release for Wallaby. - gmann - Keep exploring the options for making patrole lightweight. - gmann, doug Grenade: extending the testing for zero downtime upgrade testing: ------------------------------------------------------------------------------------ This is just a thought. There is TC tag 'assert:supports-zero-downtime-upgrade' which is not used by any of the projects and also we do not have any testing framework which can verify this tag. We talked about it if we can do such testing in grenade or not. Before moving forward on discussion and investigation we checked if anyone can volunteer for this work. As of now, no volunteer. Use different guest image for gate jobs to run tempest tests: --------------------------------------------------------------------------- We only test cirros guest image to create the test VM and all proposal from Paras is to try more images to enhance the different configuration scenarios in upstream testing. This will help to able to catch more failure/scenario at the upstream gate itself compare to the current situation where most of them are reported from downstream testing. * Action: - Add a job as experimental - paras333 Tempest Cred Manager proposed changes: ----------------------------------------------------- 'primary' and 'alt_promary' credentials in Tempest are hardcoded to non-admin and they are assigned configured 'tempest_role'. There is no way we can assign a different role to both of these creds. The idea here is to make 'primary' and 'alt_promary' credentials configurable so that different deployment can configure these with different roles in various combinations. We will be adding two config option similar to 'tempest_role' and default to an empty list so that we continue the default behavior with what we have currently. So that there is no backward-incompatible change instead it is an additional new thing provided. * Action: - Doug needs to propose the patch. Tempest Scenario manager stable version brainstorming: ----------------------------------------------------------------------- We talked about a few method changes to make the scenario manager stable. If any method is used among plugins only and not in Tempest then we do not actually need to move it to Tempest and they can stay on the side of the plugin itself. We ran out of time here and will continue the brainstorming in office hours or so. (this etherpad - https://etherpad.opendev.org/p/tempest-scenario-manager) * Action: - Sonia and Martin will continue working on this. Wallaby Priority & Planning: ------------------------------------ We did not prioritize the things as such but listed all working items in below etherpad along with Victoria cycle backlogs. - https://etherpad.opendev.org/p/qa-wallaby-ptg Detailed discussions are in this Etherpad: https://etherpad.opendev.org/p/qa-wallaby-ptg -gmann

1 0

[openstack-ansible] Gerrit breach and auditing all commits since Oct 01
by Dmitriy Rabotyagov 28 Oct '20

28 Oct '20

Hi! Most of you already know that Gerrit has been compromised a while ago [1]. Infra team has dealed with it very efficiently and I can assure you that this issue hasn't touched openstack-ansible project. I have looked through all commits that were merged in period from Oct 1 - Oct 21 (and we've got more than 200 of them during this timeframe, wow!), and all of them look valid and were properly approved. I have also double checked our releases and didn't found any extra or malicious ones. So we are pretty safe and can sleep calm [1] http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html -- Kind Regards, Dmitriy Rabotyagov

1 0

[gate] many jobs failing for nova-compute libvirt driver error
by melanie witt 28 Oct '20

28 Oct '20

Hey all, This is just a FYI that we've got another gate failure where nova-compute is failing with the following error raised from the libvirt driver [1]: "TypeError: Parameterized generics cannot be used with class" which was raised from the eventlet.tpool code. (I don't yet understand what this error means exactly.) Because of this, we suspect this is related to the eventlet package version bump from 0.26.1 to 0.28.0 that happened in the upper-constraints change to openstack/requirements that merged earlier today: https://review.opendev.org/#/c/750084/47/upper-constraints.txt@150 But we're not certain yet exactly what is happening and whether this ^ is indeed the cause. I am currently investigating to find the root cause of failure and how to fix it/confirm which package we should pin for now. I am trying out a DNM nova patch to pin eventlet to 0.26.1 to see what happens, while I look into more depth at what the error means and whether it's something we should fix in the nova code. If anyone can help, it would be appreciated. Best, -melanie [1] https://zuul.opendev.org/t/openstack/build/20f1d309663347c28112b711b82b9c03…

4 7

[qa] Wallaby PTG Wrap-up and office hour was changed to Tue 1400 UTC
by Masayuki Igawa 28 Oct '20

28 Oct '20

Hi, Thank you for attending our sessions! We had discussed many things during the virtual PTG. Topics are the following. And as we discussed our office hour office time 1 hour earlier than the current time. So, the office hour starts at 1400 UTC on every Tuesday. ========= Topics: Mon: @ Juno Greetings and ordering the topics Victoria Retrospective Move back the single horizon test in tempest tree from tempest-horizon Add run_validation as a centralised point for Tempest scenario tests Tue: @Juno Patrole stable release Grenade: extending the testing for zero downtime upgrade testing Use different guest image for gate jobs to run tempest tests Tempest Cred Manager proposed changes Tempest Scenario manager stable version brainstorming Bug triaging -> moved to the office hour Wallaby priority items https://etherpad.opendev.org/p/qa-wallaby-priority Etherpad: https://etherpad.opendev.org/p/qa-wallaby-ptg You can find the recording video files on the etherpad. ========= -- Masayuki Igawa

2 1

[Neutron] no L3 meeting this week (2020-June-01)
by LIU Yulong 28 Oct '20

28 Oct '20

Hi there, Due to the PTG meetings this week, we will cancel the L3 meeting this week. See you guys online next week. Regards, LIU Yulong

1 2

[masakari][ptg] I cannot attend the 2nd Masakari PTG session
by Radosław Piliszek 28 Oct '20

28 Oct '20

Dears, I regret to inform that, due to personal matters (augmented by the pandemic and the current situation in my country), I will not be able to attend the 2nd Masakari PTG session: Thursday October 29, 2020 13:00 - 15:00 (UTC) The good news is we don't have that many topics to go through and I am generally able to get more time from later slots if we need to have it. -yoctozepto

1 0

[nova-scheduler] always the same compute was selected?
by Tony Liu 27 Oct '20

27 Oct '20

Hi, I have a Ussuri setup with 5 compute nodes (same resource spec). When launch 5 Cirros VMs in a batch, they are all launched on the same compute node. All 5 nodes have sufficient resource. AWIK, Nova scheduler picks a compute randomly after going through filtering. But 5 VMs all on the same compute is quite coincidental. Could it be something missing? Is there any control to such random pick? Any way to make a better balancing? >From the below log, could anyone let me know how compute-4 was selected? I tried a few more launches, it's always compute-4 was selected. ========================================= 2020-10-27 13:56:45.484 24 DEBUG nova.scheduler.filter_scheduler [req-e2c6bf4b-7512-4ff0-9899-2a24bffa9131 113ee63a9ed0466794e24d069efc302c 32be191b3ec9497eaec108a22220890b - default default] Filtered [(compute-4, compute-4) ram: 131698MB disk: 14251008MB io_ops: 0 instances: 17, (compute-5, compute-5) ram: 232050MB disk: 14251008MB io_ops: 0 instances: 2, (compute-2, compute-2) ram: 367785MB disk: 14252032MB io_ops: 0 instances: 5, (compute-1, compute-1) ram: 298665MB disk: 14251008MB io_ops: 0 instances: 9, (compute-3, compute-3) ram: 259753MB disk: 14251008MB io_ops: 0 instances: 19] _get_sorted_hosts /usr/lib/python3.6/site-packages/nova/scheduler/filter_scheduler.py:443 2020-10-27 13:56:45.485 24 DEBUG nova.scheduler.filter_scheduler [req-e2c6bf4b-7512-4ff0-9899-2a24bffa9131 113ee63a9ed0466794e24d069efc302c 32be191b3ec9497eaec108a22220890b - default default] Weighed [WeighedHost [host: (compute-4, compute-4) ram: 131698MB disk: 14251008MB io_ops: 0 instances: 17, weight: 2.315526126088031], WeighedHost [host: (compute-2, compute-2) ram: 367785MB disk: 14252032MB io_ops: 0 instances: 5, weight: -999997.0], WeighedHost [host: (compute-1, compute-1) ram: 298665MB disk: 14251008MB io_ops: 0 instances: 9, weight: -999997.2171186721], WeighedHost [host: (compute-3, compute-3) ram: 259753MB disk: 14251008MB io_ops: 0 instances: 19, weight: -999997.3362949106], WeighedHost [host: (compute-5, compute-5) ram: 232050MB disk: 14251008MB io_ops: 0 instances: 2, weight: -999997.371492924]] _get_sorted_hosts /usr/lib/python3.6/site-packages/nova/scheduler/filter_scheduler.py:462 2020-10-27 13:56:45.486 24 DEBUG nova.scheduler.utils [req-e2c6bf4b-7512-4ff0-9899-2a24bffa9131 113ee63a9ed0466794e24d069efc302c 32be191b3ec9497eaec108a22220890b - default default] Attempting to claim resources in the placement API for instance ac10e5df-7e55-4c88-a682-df25cb6dd535 claim_resources /usr/lib/python3.6/site-packages/nova/scheduler/utils.py:1175 2020-10-27 13:56:45.657 24 DEBUG nova.scheduler.filter_scheduler [req-e2c6bf4b-7512-4ff0-9899-2a24bffa9131 113ee63a9ed0466794e24d069efc302c 32be191b3ec9497eaec108a22220890b - default default] [instance: ac10e5df-7e55-4c88-a682-df25cb6dd535] Selected host: (compute-4, compute-4) ram: 131698MB disk: 14251008MB io_ops: 0 instances: 17 _consume_selected_host /usr/lib/python3.6/site-packages/nova/scheduler/filter_scheduler.py:354 ========================================= Thanks! Tony

2 2

[tc][all] Wallaby Cycle Community Goals
by Graham Hayes 27 Oct '20

27 Oct '20

Hi All It is that time of year / release again - and we need to choose the community goals for Wallaby. Myself and Nate looked over the list of goals [1][2][3], and we are suggesting one of the following: - Finish moving legacy python-*client CLIs to python-openstackclient - Move from oslo.rootwrap to oslo.privsep - Implement the API reference guide changes - All API to provide a /healthcheck URL like Keystone (and others) provide Some of these goals have champions signed up already, but we need to make sure they are still available to do them. If you are interested in helping drive any of the goals, please speak up! We need to select goals in time for the new release cycle - so please reply if there is goals you think should be included in this list, or not included. Next steps after this will be helping people write a proposed goal and then the TC selecting the ones we will pursue during Wallaby. Additionally, we have traditionally selected 2 goals per cycle - however with the people available to do the work across projects Nate and I briefly discussed reducing that to one for this cycle. What does the community think about this? Thanks, Graham 1 - https://etherpad.opendev.org/p/community-goals 2 - https://governance.openstack.org/tc/goals/proposed/index.html 3 - https://etherpad.opendev.org/p/community-w-series-goals 4 - https://governance.openstack.org/tc/goals/index.html#goal-selection-schedule

7 16

[ops][cinder] ceph version survey for operators
by Brian Rosmaita 27 Oct '20

27 Oct '20

Hello Cinder operators, tl;dr - if you use Ceph with your Cinder installation, please fill out this short (4 question) survey before 18:00 UTC on Wednesday 28 October 2020: https://rosmaita.wufoo.com/forms/ceph-version-survey/ Cinder currently contains an RBD driver that supports a Ceph backend, but it does not restrict Ceph to a particular range of versions. We'd like to take advantage of recent developments in Ceph to make some improvements to the RBD driver, but first want to gather data on what versions of Ceph are actually being used with Cinder so we can figure out backward compatibility issues we may face. (Basically, keeping backward compatibility for Ceph versions that don't have the new features will add complexity to the driver code, and more complex code is more likely to have bugs, and nobody likes bugs. Hence, we don't want to carry compatibility code for Ceph versions that no one is using.) If you manage multiple clouds, please fill out a separate survey for each cloud. We plan to discuss this issue at the PTG next week, so please respond before 18:00 UTC on Wednesday 28 October 2020. Here's the survey: https://rosmaita.wufoo.com/forms/ceph-version-survey/ Thank you!

1 1

[PTG] [Diversity] Extra session for Divisive Language discussions
by Amy Marrich 27 Oct '20

27 Oct '20

During the Monday session there were some questions in regards to technical writing and how things should be worded. I have invited Joanne O'Flynn, a Technical Writer from Red Hat to join us on Thursday at 17:00 UTC to help address these questions. This is not a normal PTG time slot but it was the only option due to time zones and already booked sessions for some of the participants from Monday. Thanks, Amy Marrich (spotz)

1 1

[TripleO] [ptg] deployment flow
by Kanevsky, Arkady 27 Oct '20

27 Oct '20

After today's PTG meeting want to make sure I have the right understanding of deployment flow. After deploying undercloud, are these the steps need to be done that are partially outside TripleO (https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/provisi… ): 1. Ironic discovery to discover all nodes. (networking for ironic must be in place for all nodes) 2. Metalsmith will provision baremetal machines - https://docs.openstack.org/metalsmith/latest/ 3. Metalsmith provisions OS on provisioned nodes 4. Something(???) optionally provisions Ceph (based on appropriate roles) 5. Something(???) optionally provisions other 3rd party services, like switch provisioning (based on appropriate roles) 6. Metalsmith optionally provisions Glance (may require Ceph or other 3rd party storage) 7. Metalsmith optionally provisions Neutron (may require switch provisioning) 8. TripleO deploys overcloud Is this the correct flow? Do we still need "openstack overcloud node provision" call or metalsmith already handles it? Or this call uses metalsmith under the cover? Thanks, Arkady

2 3

[requirements] Gerrit breach and commit audit
by Thierry Carrez 27 Oct '20

27 Oct '20

Following the recent gerrit breach, I manually audited all recent changes to the openstack/requirements repository, and could not find suspicious activity. Cheers, -- Thierry Carrez (ttx)

1 0

[cinder] qemu-img info is called as root even if nas_secure_file_operations is set to true
by Jonas Schäfer 27 Oct '20

27 Oct '20

Hi list, We’ve got a curious issue here. We’re trying to configure Cinder for use with NetApp NFS. The NetApp has been configured to disallow superuser access and cinder has been set up with nas_secure_file_operations set to true. While operations like creating volumes work, attaching a volume to an instance fails with the following traceback: Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/cinder/volume/manager.py", line 4369, in _connection_create conn_info = self.driver.initialize_connection(volume, connector) File "/usr/lib/python2.7/dist-packages/cinder/volume/drivers/nfs.py", line 134, in initialize_connection volume['name']) File "/usr/lib/python2.7/dist-packages/cinder/volume/drivers/nfs.py", line 543, in _qemu_img_info run_as_root=True) File "/usr/lib/python2.7/dist-packages/cinder/volume/drivers/remotefs.py", line 765, in _qemu_img_info_base run_as_root=run_as_root) File "/usr/lib/python2.7/dist-packages/cinder/image/image_utils.py", line 111, in qemu_img_info prlimit=QEMU_IMG_LIMITS) File "/usr/lib/python2.7/dist-packages/cinder/utils.py", line 126, in execute return processutils.execute(*cmd, **kwargs) File "/usr/lib/python2.7/dist-packages/oslo_concurrency/processutils.py", line 425, in execute cmd=sanitized_cmd) ProcessExecutionError: Unexpected error while running command. Command: /usr/bin/python -m oslo_concurrency.prlimit --as=1073741824 --cpu=30 -- sudo cinder-rootwrap /etc/cinder/rootwrap.conf env LC_ALL=C qemu-img info --force-share /var/lib/cinder/mnt/1be0f17801f5c315c80d99a59518e26e/volume- ae4bba9b-2ab3-4234-8f86-352f1a20e086 Exit code: 1 Stdout: u'' Stderr: u"qemu-img: Could not open '/var/lib/cinder/mnt/ 1be0f17801f5c315c80d99a59518e26e/volume-ae4bba9b-2ab3-4234-8f86-352f1a20e086': Could not open '/var/lib/cinder/mnt/1be0f17801f5c315c80d99a59518e26e/volume- ae4bba9b-2ab3-4234-8f86-352f1a20e086': Permission denied\n" It seems as if cinder executes qemu-img as root. This is confirmed by looking at the code [3]. Looking at the superclass [4], we see that the superclass would’ve decided based on the setting of nas_secure_file_operations if [3] would not pass execute_as_root as True. To us, it makes no sense whatsoever. While [1] mentions something about incorrect permissions on volumes, it does not seem to consider the case of running with NFS Security enabled at all. However, it also seems as if this change went through completely uncontested. Hence, we assume that we are in the wrong here and wanted to ask on the mailing list instead of filing a bug. Does anyone have insight on what we’re doing wrong / missing here? kind regards, Jonas [1]: https://review.opendev.org/#/c/461134/ [2]: https://github.com/openstack/cinder/commit/dbc9c7ca [3]: https://github.com/openstack/cinder/blob/stable/queens/cinder/volume/ drivers/nfs.py#L537-L543 [4]: https://github.com/openstack/cinder/blob/stable/queens/cinder/volume/ drivers/remotefs.py#L753-L761 [5]: https://github.com/openstack/cinder/blob/stable/queens/cinder/volume/ drivers/nfs.py#L431-L432 -- Jonas Schäfer DevOps Engineer Cloud&Heat Technologies GmbH Königsbrücker Straße 96 | 01099 Dresden +49 351 479 367 37 jonas.schaefer(a)cloudandheat.com | www.cloudandheat.com New Service: Managed Kubernetes designed for AI & ML https://managed-kubernetes.cloudandheat.com/ Commercial Register: District Court Dresden Register Number: HRB 30549 VAT ID No.: DE281093504 Managing Director: Nicolas Röhrs Authorized signatory: Dr. Marius Feldmann Authorized signatory: Kristina Rübenkamp

1 0

[masakari] PTG starting Thursday
by Radosław Piliszek 27 Oct '20

27 Oct '20

Hello Everyone! A kind reminder that Masakari has PTG scheduled for the upcoming Thursday and Friday. First session: Thursday October 29, 2020 06:00 - 08:00 (UTC) Feel free to get acquainted with the etherpad [1] in the meantime. [1] https://etherpad.opendev.org/p/masakari-wallaby-vptg Cheers! -yoctozepto

1 0

Overcloud fatal error TASK [Ensure system is NTP time synced]
by dangerzone ar 27 Oct '20

27 Oct '20

Hi, I'm facing overcloud failure at the same line related with 'Ensure system is NTP time synced' *The error below refer:-* *TASK [Ensure system is NTP time synced] ****************************************fatal: [overcloud-controller-0]: FAILED! => {"changed": true, "cmd": ["chronyc", "waitsync", "20"], "delta":......* *controller timedatectl:-* *[heat-admin@overcloud-controller-0 ~]$ timedatectl Local time: Tue 2020-10-27 08:53:19 UTC Universal time: Tue 2020-10-27 08:53:19 UTC RTC time: Tue 2020-10-27 08:53:19 Time zone: UTC (UTC, +0000) NTP enabled: yesNTP synchronized: no RTC in local TZ: no DST active: n/a* *undercloud timedatectl:-* * Local time: Tue 2020-10-27 17:36:11 +08 Universal time: Tue 2020-10-27 09:36:11 UTC RTC time: Tue 2020-10-27 09:36:11 Time zone: Asia/Singapore (+08, +0800) NTP enabled: yesNTP synchronized: yes RTC in local TZ: no DST active: n/a* Tripleo deployment for 1compute and 1controller. I have run few times and end-up with the same error. Seems it's all related to chrony. No more ntp in rocky release and all change to chrony to handle time synchronization. Based on my reading the issue should be resolved in rocky but clearly my overcloud deployment failed at this stage. Please advise how to resolve this problem. Thank you all.

1 0

[cyborg] [ptg] cyborg Wallaby PTG schedule and topics
by yumeng bao 26 Oct '20

26 Oct '20

Hi all, Please check the cyborg PTG schedule below, and here are all the topics[0] that we've proposed, can't wait to see you tomorrow! And we plan to have a team photo on the first day at our internal meeting, come and join! ^^ Tuesday (27th ) 6:00 UTC - 8:00 UTC, Cyborg internal discussion Tuesday (27th) 13:00 - ?, Edge group discussion Wednesday (28th ) 6:00 UTC - 8:00 UTC, Cyborg internal Wednesday (28th): 13:00 - 14:00: Nova-Cyborg cross project session Tuesday (29th ) 6:00 UTC - 8:00 UTC, Cyborg internal [0]https://etherpad.opendev.org/p/cyborg-wallaby-goals Regards， Yumeng

2 1

[tacker] PTG planning
by Yasufumi Ogawa 26 Oct '20

26 Oct '20

Hi Tacker team, I've updated our vPTG etherpad for topics you've proposed [1]. We will start it from 27 Oct 6am UTC. So, I would like to skip the next IRC meeting this week. You can find Tacker's room on Zoom from schedule tracks here [2]. I'd also like to ask you to join in taking team photo on our 2nd day, although it's not mandatory. Thanks, Yasufumi [1] https://etherpad.opendev.org/p/Tacker-PTG-Wallaby [2] http://ptg.openstack.org/ptg.html

2 2

[ptg][swift][ops] Operator feedback session 28 Oct 21:00-22:00 UTC
by Tim Burke 26 Oct '20

26 Oct '20

Later this week, the Swift community will have an operator feedback session during our PTG slot [0]. If you're running a swift cluster, large or small, we'd love to see you there! As we've done in the past [1], we'll have an etherpad going [2] -- feel free to start filling it in and adding discussion items today! Even if you won't make the meeting, we'd appreciate your feedback. Looking forward to hearing from you! Tim [0] 28 Oct at 2100 UTC in https://www.openstack.org/ptg/rooms/kilo [1] https://wiki.openstack.org/wiki/Swift/Etherpads#List_of_Ops_Feedback_Etherp… [2] https://etherpad.opendev.org/p/swift-wallaby-ops-feedback

1 0

[keystone][ptg] Keystone vPTG Planning
by Kristi Nikolla 26 Oct '20

26 Oct '20

Hi all, I have started a doodle poll for scheduling our sessions during the vPTG. Please fill it out by September 10. [0] The etherpad that we are using for brainstorming the topics is [1]. Please fill it out with anything you would like us to schedule time for. More information on the vPTG and links to register can be found at [2]. [0]. https://doodle.com/poll/czgyuwepxk348vqq [1]. https://etherpad.opendev.org/p/keystone-wallaby-ptg [2]. https://www.openstack.org/ptg/

2 1

Help with meetpad needed
by Slawek Kaplonski 26 Oct '20

26 Oct '20

Hi, In Neutron sessions we are successfully using meetpad. But I have one question about it, maybe You will be able to help me somehow. When I click "open shared document" in the meetpad, etherpad is displayed but only until someone will start talking or someone new will join the call. Is it possible somehow to force display of the etherpad always? Thx in advance for any help with that. -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

How to use condition for resource creation via heat template
by Md. Hejbul Tawhid MUNNA 26 Oct '20

26 Oct '20

~~~ heat_template_version: 2017-02-24 ...... ...... ...... conditions: port_security_enabled: equals: - { get_param: port_security_enabled } - "true" resources: port: type: OS::Neutron::Port properties: admin_state_up: true network_id: { get_param: internal_net } port_security_enabled: { get_param: port_security_enabled } security_groups: { get_param: security_group } I want to create a condition , so if I set "port_security_enabled = false" security group will not apply in port.properties . If I set "port_security_enabled = true" then security group will applied. Please help me

2 1

[tripleo][overcloud] Deployment templates and command
by dangerzone ar 26 Oct '20

26 Oct '20

Hi, after exploring openstack via tripleo deployment, I encountered several issues especially during overcloud deployment. Most of the time I'm referring to openstack official web guideline and some other blogs resources. From my experiences I face problems identifying the right templates and the right command for my deployment. I have seen templates created in guideline web and some other examples. Even the command line to deploy overcloud is also a bit different from one example to another. I understand it is because of different requirements and setup. So many templates and several ways of deployment always made me puzzle and endup with deployment failure. I would like some advice to know what are the common or important templates/yaml files and overcloud command to use if I just want to deploy 3 controllers (ha) and several computes only. I also have plan to get dpdk in my deployment but...this will be later as I would like to successfully establish simple deployment with controllers and computes for now. Appreciate your good advice and support. Thank you all. This is some web link I use to refer:- ** https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/feature… ** https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/13… ** https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/ Regards, daz

2 1

Help about openstack Storlets
by ghasemir 26 Oct '20

26 Oct '20

hi I am working on Openstack Storlets. I ran Swift in a Docker(container) and I want to put it in the Storlet midleware. How can that be? Can you help? My main question: Is there a place or activity group about Storlet to share comments and get helps? Thanks a lot Best regards Reza Ghasemi Department of Computer Engineering,Sharif University of Technology

2 1

[ptg][kolla] Please stop translating Etherpads
by Mark Goddard 26 Oct '20

26 Oct '20

Hi, Over the weekend, the Kolla Etherpad [1] has had various sections replaced with (what I think is) a Chinese translation, twice. This replaces the original English text for everyone. I guess that this is some browser based translator that does not realise it is modifying the page content for everyone. The export/import procedure I used to restore the etherpad loses some formatting, attributions, and may have lost content if changes were made in between. Please, we need to find another solution for translation. If you need to make translations, please copy text to another window, or at least provide translations for specific text *next to the English*. If this happens again we will need to move to another tool, such as Google docs. I would much prefer not to do this, and rather use an open source tool that is widely accessible, but we do need to be able to collaborate this week without disruption. I look forward to working with you this week. I hope this does not discourage non-native English speakers, of which there is generally a majority. If I can provide any assistance to make the sessions more accessible, please get in touch. Cheers, Mark [1] https://etherpad.opendev.org/p/kolla-wallaby-ptg

4 6

[First Contact] [SIG] [PTG] Meeting Reminder
by Kendall Nelson 26 Oct '20

26 Oct '20

Hello Everyone! Just wanted to remind you all that we have time scheduled at the PTG for Thursday October 29th at 23:00 UTC. Also, feel free to add agenda items here[1] in the meantime. Hope to see you there! -Kendall Nelson (diablo_rojo) [1] https://etherpad.opendev.org/p/wallaby-ptg-first-contact

1 0

[octavia] Weekly IRC meeting is cancelled this week due to the PTG
by Michael Johnson 26 Oct '20

26 Oct '20

Hello Octavia community, As we will be meeting for the PTG this week, I am cancelling the weekly IRC meeting on October 28th. Looking forward to seeing you all at the PTG! Michael

1 0

[neutron] bug deputy report October 19th - 25th
by Miguel Lavalle 26 Oct '20

26 Oct '20

Hi Neutrinos, Here's the bug report for the week of October 19th - 25th. It was a very quiet week High ==== https://bugs.launchpad.net/neutron/+bug/1900763 [OVN Octavia Provider] OVN provider status update failures can leave orphaned resources. It has an owner already (haleyb) RFE === https://bugs.launchpad.net/neutron/+bug/1900934 [RFE][DHCP][OVS] flow based DHCP. Will be discussed during PTG

1 0

[Glance] create image by downloading/importing from UI vs. CLI
by Tony Liu 26 Oct '20

26 Oct '20

Hi, The initial issue I saw was "The Store URI was malformed." from Horizon when creating image by URL [1]. It works fine with Glance CLI as the following. ======== glance image-create --container-format bare --disk-format qcow2 --name cirros-test glance image-import --import-method web-download --uri https://download.cirros-cloud.net/0.5.1/cirros-0.5.1-x86_64-disk.img cirros-test ======== When I look into it, I see that UI and CLI work differently, they are handled by different workflow in Glance. Why is that? Why not UI follows the same workflow as CLI? The root cause is that, [1] redirect to [2] and redirect to [3]. One issue here is that, query is not supported in [4]. pieces.query is dropped. When I attached query parameters, I got 403. And that's because, the workflow for UI is checking quota policy when adding location. It needs to get the size of image by HEAD request. But the signature in [3] is for GET request. So that HEAD request is forbidden by S3. I don't think we can get an URL with signature for HEAD request in such case. So I go for an ugly workaround to skip the size check. Any ideas to make it work better? Is quota policy involved in CLI workflow? Again, can we make UI work the same way as CLI? [1] https://download.cirros-cloud.net/0.5.1/cirros-0.5.1-x86_64-disk.img [2] https://github.com/cirros-dev/cirros/releases/download/0.5.1/cirros-0.5.1-x… [3] https://github-production-release-asset-2e65be.s3.amazonaws.com/219785102/6… [4] https://github.com/openstack/glance_store/blob/488d3e2fe31e4fc7a461e9de8b20… Thanks! Tony

3 2

[heat] PTG on this wednesday 13-15 UTC
by Rico Lin 26 Oct '20

26 Oct '20

Hi all Heat PTG room reserved on Wednesday 13-15 UTC at Juno room Feel free to update our PTG etherpad [1] [1] https://etherpad.opendev.org/p/wallaby-ptg-heat -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

[multi-arch SIG] PTG plan this week
by Rico Lin 26 Oct '20

26 Oct '20

Hi all, Multi-arch SIG will have our PTG on 10/27 Tuesday 07-08 UTC, and 15-16 UTG This week at room Juno Feel free to update our etherpad [1] [1] https://etherpad.opendev.org/p/wallaby-ptg-multiarch-sig -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0

linux.conf.au 2021 - Call for Sessions and Miniconfs Open
by Joshua Hesketh 26 Oct '20

26 Oct '20

The best F/OSS conference in the southern hemisphere is back again - this time virtualised and without a 20+ hour flight! -, January 23-25. The CFP is open until November 6. Submit early, submit often! -------- Forwarded Message -------- Subject: [lca-announce] linux.conf.au 2021 - Call for Sessions and Miniconfs Open Date: Thu, 15 Oct 2020 20:43:24 +1000 From: linux.conf.au Announcements <lca-announce(a)lists.linux.org.au> <lca-announce(a)lists.linux.org.au> Reply-To: lca-announce(a)lists.linux.org.au To: lca-announce(a)lists.linux.org.au We're excited! The linux.conf.au 2021 Call for Sessions and Call for Miniconfs are now open. They will stay open until 6th November 2020 Anywhere on Earth (AoE) (https://en.wikipedia.org/wiki/Anywhere_on_Earth) This is only 3 weeks away - so don't delay, get your talks in early! Our theme is "So what's next?". We all know we're living through unprecedented change and uncertain times. How can open source play a role in creating, helping and adapting to this ongoing change? What new developments in software and coding can we look forward to in 2021 and beyond? If you have ideas or developments you'd like to share with the open source community at linux.conf.au, we'd love to hear from you. Call for Sessions The main conference runs on Sunday 24 and Monday 25 January, with multiple streams catering for a wide range of interest areas. We invite you to submit a session (https://linux.conf.au/programme/sessions/) proposal for a talk. Talks are generally 35-45 minute presentations on a single topic presented in lecture format. Call for Miniconfs Miniconfs are dedicated day-long streams focusing on single topics, creating a more immersive experience for delegates than a session. We encourage you to get creative with how you could deliver your Miniconf virtually! Running a Miniconf (https://linux.conf.au/programme/miniconfs/) is a great way to gain experience, provide exposure for your project or topic, and raise your professional profile. They're a crowd favourite and an awesome way to kick off the conference. Miniconfs will run on Saturday 23 January, before the main conference commences on Sunday. No need to book flights or hotels Don't forget: the conference will be a fully online, virtual experience. This means our speakers will be beaming in from their own homes or workplaces. The organising team will be able to help speakers with their tech set-up. Each accepted presenter will have a tech check prior to the event to smooth out any difficulties and there will be an option to pre-record presentations. Have we piqued your interest? You can find out how to submit your session or miniconf proposals at https://linux.conf.au/programme/proposals/. If you have any other questions you can contact us via email at contact(a)lca2021.linux.org.au. Timeline 16th October: Call for sessions opens 6th November: Call for sessions closes January 23 2021: Miniconfs! January 24-25 2021: Main conference presentations Tickets will go on sale in the coming weeks. We'll keep you posted. We're looking forward to reading your submissions. linux.conf.au 2021 Organising Team About linux.conf.au 2021 Running since 1999, linux.conf.au is the largest linux and open source conference in the Asia-Pacific region. The conference provides deeply technical presentations from industry leaders and experts on a wide array of subjects relating to open source projects, data and open government and community engagement.

1 0

[oslo] PTG Update
by Ben Nemec 26 Oct '20

26 Oct '20

Hi, Based on the lack of topic proposals in the etherpad[0], we are currently planning to skip the Oslo PTG session for this cycle. If you have something to discuss please contact the team ASAP so we have time to set something up. Thanks. -Ben 0: https://etherpad.opendev.org/p/oslo-wallaby-topics

3 3

[largescale-sig] Two PTG meetings
by Thierry Carrez 26 Oct '20

26 Oct '20

Hi everyone, Following a well-attended forum session last week on sharing your scaling story[1], the Large Scale SIG have *two* meetings this week during the PTG: Wednesday Oct 28, 7:00 UTC Wednesday Oct 28, 16:00 UTC To join either of those, please register for the PTG[2] and click on "largescale-sig" on the schedule[3]. I hope to see you there! [1] https://etherpad.opendev.org/p/vSummit2020_OpenStackScalingStory [2] https://www.openstack.org/ptg [3] http://ptg.openstack.org/ptg.html -- Thierry Carrez (ttx)

1 0

[docs][Zaqar]Zaqar API reference is missing from doc.openstack.org
by hao wang 26 Oct '20

26 Oct '20

Hi， I'm Hao Wang, the PTL of Zaqar project. I found that Zaqar API reference is missing from https://docs.openstack.org/victoria/api/. Is there something wrong or what I can help to fix it, please let me know. Thank you.

2 1

[tripleo] proposed schedule TripleO meetup @ Wallaby PTG
by Marios Andreou 25 Oct '20

25 Oct '20

Hello tripleOs o/ I would like to share a proposed schedule for the TripleO meetup at the coming PTG. The proposal is at [1]. First I'd like to give a huge thank you to everybody for taking the time to volunteer and lead those sessions. We are lucky to have folks bringing a wide array of topics including deployment, edge, upgrades, high-availability, ci, storage and networking. The schedule has 5 fourty minute sessions per day (we have 4 hours/day 1300-1700 UTC) with 10 mins breaks between them. If you would like to propose an alternative structure or have suggestions/improvements etc then let's discuss it here. If you want to make changes to your session time please reach out directly to the person running the time slot you wish to change with. If there are no objections then please go ahead and swap the sessions in the schedule (please let me know too). If you can't reach that person or there are any other problems please message me and we will work it out together. If you have added (or plan to add) a new discussion topic in [2] and you don't see it in [1] then please let me know so I can add it. If you are leading a session then please remember to prepare the session etherpad over the next few days and link it at [1]. Of course, make sure you are registered for the PTG :) at [3] thank you for reading and for sharing any thoughts/suggestions/improvement to the proposed schedule [1], regards (+ happy friday !) marios [1] https://etherpad.opendev.org/p/tripleo-ptg-wallaby [2] https://etherpad.opendev.org/p/tripleo-wallaby-topics [3] https://october2020ptg.eventbrite.com/

1 2

[cinder][grenade][neutron] Gate failure in grenade jons
by Slawek Kaplonski 25 Oct '20

25 Oct '20

Hi Cinder team, I saw in Neutron CI in last few days that all our grenade jobs (multinode if that is important) are failing with error which seems to be related to Cinder. I opened bug [1] for that. Please take a look at it as it seems pretty serious issue because our gate is now broken because of that. Sorry if there is already another bug reported for the same problem and I created duplicate :) If bug is somehow hard to fix or there is nobody who can take a look, I will be also greatful for such info so we can temporary mark those grenade jobs as non-voting to unblock our gate :) Thx a lot in advance for Your help. [1] https://bugs.launchpad.net/cinder/+bug/1901384 -- Slawek Kaplonski Principal Software Engineer Red Hat

2 2

[scientific-sig] Scientific SIG at the PTG
by Stig Telfer 24 Oct '20

24 Oct '20

Hi All - The Scientific SIG will be at the PTG this coming week, and everyone is welcome. We have two sessions on Monday: - 15:00-17:00 UTC to discuss use cases and requirements for SIG members. - 21:00-23:00 UTC to include lightning talks from SIG members and further discussions. We would love to have participants contribute lightning talks for the second session. It’s easy to do, particularly if you’ve just presented on something at the summit, or have new material to try out before SC :-) Our PTG Etherpad is available here: https://etherpad.opendev.org/p/wallaby-ptg-scientific-sig Remember to register for PTG attendance here: https://october2020ptg.eventbrite.com <https://october2020ptg.eventbrite.com/> Cheers, Stig

1 0

[nova] PTG schedule
by Balázs Gibizer 24 Oct '20

24 Oct '20

Hi, I did a bit of reordering of the topics in the PTL etherpad[1] to move similar topics closer to each other. I did not try to assign specific timing to each topic. We will use the ptgbot during the PTG to notify the audience what we are talk about and what is the next topic. See you next week! Cheers, gibi [1]https://etherpad.opendev.org/p/nova-wallaby-ptg

2 3

[cinder] PTG schedule
by Brian Rosmaita 23 Oct '20

23 Oct '20

Hello Cinder folks and fellow travelers, I've updated the official Cinder Wallaby PTG etherpad with discussion topics: https://etherpad.opendev.org/p/wallaby-ptg-cinder It's organized by days to give you a rough idea of what will be discussed when. As always, we will be flexible about moving things around if we have to. Friday has a little bit of slack built in, so I anticipate that we'll be able to discuss everything on the schedule. Please take a look at the schedule as soon as you can to identify the discussions you are leading and let me know right away if you anticipate any conflicts. Info for connecting to the Cinder sessions is on the etherpad. The plan is that we'll have discussions from 1300-1600 UTC Tuesday-Friday, and have optional "hallway time" from 1700-1800 UTC Tuesday-Friday to try to reproduce the useful informal encounters we'd be having at a face-to-face event. (This time is not ideal for APAC developers; we could additionally have "hallway time" from 1200-1300 UTC if there is interest. Let me know.) Don't forget that we decided to have Happy Hour the *first* day of meeting (Tuesday) so that people can get to know each other a bit. Hopefully this will make everyone more comfortable for participating in the discussions. Happy Hour is at 1500 UTC on Tuesday 27 October. Monday is open for you to attend non-cinder events; some are noted on the etherpad. Please add other sessions that Cinder people might find of interest. Looking forward to seeing everyone next week! brian

1 0

[openstack-ansible][osa] Ubuntu based deployments issue
by Dmitriy Rabotyagov 23 Oct '20

23 Oct '20

Hi, We have to announce, that due to Ubuntu has removed base images for all non-current point releases (ie 18.04.3) [1], all current or new OSA deployments will fail during base image retrievement process, which is part of the lxc_hosts role (playbook containers-lxc-host.yml which is included in setup-hosts.yml). This mean, that attempt of the new deployment, minor and major upgrade or container re-creation will fail. This won't influence already running containers in any manner. This affects ubuntu 16.04, 18.04 and 20.04 deployments for all OSA releases. At the moment we are actively working on the proper solution to prevent this from happening in the future (or at least minimize risk as much as we can). You can keep track about the progress in bug reports [2] and [3] In the meanwhile there are several workarounds, that you may easily apply locally to make your deployments working: 1. Set proper URL to the relevant Ubuntu images by setting variable `lxc_hosts_container_image_url` in user_variables.yml Relevant URL at the moment are folowing: - Ubuntu 20.04: http://cdimage.ubuntu.com/ubuntu-base/releases/20.04/release/ubuntu-base-20… - Ubuntu 18.04: http://cdimage.ubuntu.com/ubuntu-base/releases/18.04/release/ubuntu-base-18… - Ubuntu 16.04: http://cdimage.ubuntu.com/ubuntu-base/releases/16.04/release/ubuntu-base-16… 2. Use images provided by LXC team. To do this you will need to set `lxc_hosts_container_image_download_legacy: true` in your user_variables.yml Once we will have a reliable solution, we will backport it back to all supported releases and make new OSA release right afterwards. Right after that I will write an update to this notification with information about stable release number that fixes this issue. [1] https://lists.ubuntu.com/archives/ubuntu-release/2020-October/005113.html [2] https://bugs.launchpad.net/openstack-ansible/+bug/1900884 [3] https://bugs.launchpad.net/openstack-ansible/+bug/1900975 -- Kind Regards, Dmitriy Rabotyagov

1 0

[swift] Gerrit breach and commit audit
by Tim Burke 23 Oct '20

23 Oct '20

By now, I'm sure you've sen a lot of emails like these, but I've manually verified that all commits and tags across all branches are correct and proper for * swift, * python-swiftclient, and * liberasurecode following the recent gerrit security incident. PyEClib and swift-bench saw no activity during that time, so had nothing to verify. I'd just like to thank the infra team for their quick response and transparency throughout all of this; the notifications during the incident and final write-up [0] were really top-notch. Tim [0] http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html

1 0

[horizon][glance] "The Store URI was malformed."
by Tony Liu 23 Oct '20

23 Oct '20

Hi, With Ussuri, when create image on Horizon with specified URL, I got error "The Store URI was malformed.". Here is the URL I put in "Location" box. https://download.cirros-cloud.net/0.5.1/cirros-0.5.1-x86_64-disk.img What I am missing here? Thanks! Tony

1 1

[neutron] [neutron-dynamic-routing] Gerrit breach and commit audit for neutron-dynamic-routing
by Tobias Urdin 23 Oct '20

23 Oct '20

Hello, Could not find a neutron thread on this, anyways, as per the announcement in [1] I have audited the neutron-dynamic-routing where I'm a reviewer. Best regards [1] http://lists.opendev.org/pipermail/service-announce/2020-October/000011.html

2 1

[Open Infrastructure Foundation] [InteropWG] Planning meeting at 10 AM PDT in an hr
by prakash RAMCHANDRAN 23 Oct '20

23 Oct '20

Hi all, Please joinInterop Working Group - Weekly Friday 10-11 AM PDT Lnink: https://meetpad.opendev.org/Interop-WG-weekly-meeting We have scheduled 4 Slots at PTG. We will have today's 10/23 10AM PDT / 12 Noon CDT / 1.00 PM EST / 18 UTC/22.30 IST / 10/24 1 AM BJT Main focus will bePrep for PTG Request add your suggestions to https://etherpad.opendev.org/p/interop-wallaby-ptg ----------------------------------------------Session 1,2 Monday 23rd OCThttp://ptg.openstack.org/ptg.html ---------------------------------------------Session 3,4 Friday 30th OTC http://ptg.openstack.org/ptg.html --------------------------------------------- With hectic engagements please do start with InteropWG and end PTG with InteropWG.We see with kubernetes as defacto interop for Cloud Native Infrastructure we have more opportunities leverage Hybrid Cloud in Open Infrastructure PTG ThanksPrakashFor Interop WG

2 2

[nova][gate] openstack-tox-docs job broken
by melanie witt 23 Oct '20

23 Oct '20

Hey all, The pygments package version was bumped from 2.6.1 to 2.7.1 in the following openstack/requirements upper-constraints change that merged earlier today: https://review.opendev.org/750084 And it broke our openstack-tox-docs job as pygments 2.7.x validates docs for valid JSON as of: https://github.com/pygments/pygments/commit/9514e794e0c2a5c7c048df97fcfef4a… The fix is proposed here: https://review.opendev.org/759466 Please hold your rechecks until ^ merges. Cheers, -melanie

1 0