June 2020 - openstack-discuss - lists.openstack.org

[tc][networking-l2gw] Finish the retirement for networking-l2gw and networking-l2gw-tempest-plugin
by Ghanshyam Mann 26 Jun '20

26 Jun '20

Hello Everyone, networking-l2gw and networking-l2gw-tempest-plugin projects were retired in Ocata[1] but their retirement was not completed. I have started the retirement completion as discussed in TC and neutron team. - https://review.opendev.org/#/q/topic:complete-retirement-networking-l2gw+(s… Please let me know any injection to that. Their development can be continued under opendev as mentioned in this doc - https://governance.openstack.org/tc/reference/dropping-projects.html#contin… [1] https://review.opendev.org/#/c/392010/2 -gmann

5 9

[blazar] Broken CI
by Pierre Riteau 26 Jun '20

26 Jun '20

Hello, The blazar devstack CI jobs are currently failing due to issues related to uwsgi. logs/screen-blazar-a.txt shows: Jun 25 09:26:47.037179 ubuntu-bionic-limestone-regionone-0017387278 systemd[1]: Starting Devstack devstack(a)blazar-a.service... Jun 25 09:26:47.038997 ubuntu-bionic-limestone-regionone-0017387278 systemd[18254]: devstack(a)blazar-a.service: Failed to execute command: No such file or directory Jun 25 09:26:47.039047 ubuntu-bionic-limestone-regionone-0017387278 systemd[18254]: devstack(a)blazar-a.service: Failed at step EXEC spawning /usr/local/bin/uwsgi: No such file or directory Jun 25 09:26:47.039445 ubuntu-bionic-limestone-regionone-0017387278 systemd[1]: devstack(a)blazar-a.service: Main process exited, code=exited, status=203/EXEC Jun 25 09:26:47.039454 ubuntu-bionic-limestone-regionone-0017387278 systemd[1]: devstack(a)blazar-a.service: Failed with result 'exit-code'. Jun 25 09:26:47.039734 ubuntu-bionic-limestone-regionone-0017387278 systemd[1]: Failed to start Devstack devstack(a)blazar-a.service. I think it's our devstack plugin that needs fixing. In the meantime no need to recheck patches, they will keep failing until resolved. Pierre Riteau (priteau)

2 2

[all][tc][goals] Migrate CI/CD jobs to new Ubuntu LTS Focal: Week R-16 Update
by Ghanshyam Mann 26 Jun '20

26 Jun '20

Hello Everyone, Please find the updates on Ubuntu Focal migration community goal. Tracking: https://storyboard.openstack.org/#!/story/2007865 Progress: ======= * devstack and tempest base patches are ready for testing on projects side. Thanks frickler for doing the base work. * neutron, nova project started the testing. Bugs: ==== 1. There is open bug for nova/cinder where three tempest tests are failing for volume detach operation. There is no clear root cause found yet -https://bugs.launchpad.net/cinder/+bug/1882521 We have skipped the tests in tempest base patch to proceed with the other projects testing but this is blocking things for the migration. 2. We encountered the nodeset name conflict with x/tobiko, i have proposed it to consume it form devstack -https://review.opendev.org/#/c/738128/ What work to be done on project side: ============================= This goal is more of testing the jobs on focal and fixing bugs if any otherwise migrate jobs by switching the nodeset to focal node sets defined in devstack. 1. Start a patch in your repo by making depends-on on either of below: devstack base patch if you are using only devstack base jobs not tempest: https://review.opendev.org/#/c/731207/ OR tempest base patch if you are using the tempest base job (like devstack-tempest): https://review.opendev.org/#/c/734700/ Example: https://review.opendev.org/#/c/738126/ 2. If none of your project jobs override the nodeset then above patch will be testing patch(do not merge) otherwise change the nodeset to focal. Example: https://review.opendev.org/#/c/737370/ 3. If the jobs are defined in branchless repo like tempest plugins then you need to override the branches variant to adjust the nodeset on jobs so that only Victoria onwards those jobs run on focal not old stable. Once we finish the testing on projects side and no failure then we will merge the devstack and tempest base patches. Important things to note: =================== * Do not forgot to add the story and task link to your patch so that we can track it smoothly. * Use gerrit topic 'migrate-to-focal' * Do not backport any of the patch. References: ========= Goal doc: https://governance.openstack.org/tc/goals/selected/victoria/migrate-ci-cd-j… Storyboard tracking: https://storyboard.openstack.org/#!/story/2007865 -gmann

1 0

[tc] Monthly meeting
by Mohammed Naser 25 Jun '20

25 Jun '20

Hi everyone, Our monthly TC meeting is scheduled for next Thursday, July 2nd, at 1400 UTC. If you would like to add topics for discussion, please go to https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting and fill out your suggestions by Wednesday, July 1st, at 1900 UTC. Thank you, Regards, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

[cinder] priorities for the next 2 weeks
by Brian Rosmaita 25 Jun '20

25 Jun '20

As mentioned at yesterday's virtual mid-cycle, our top priority right now is to get the milestone-1 items reviewed and re-reviewed. And the specs freeze is next week ... so our *two* top priorities are to get the milestone-1 items reviewed and also review specs. Here is a handy list: volume-local-cache - https://review.opendev.org/#/c/663549/ os-brick - https://review.opendev.org/#/c/700799/ cinder - https://review.opendev.org/#/c/715762/ tempest test case NFS encrypted volume support - https://review.opendev.org/#/c/597148/ brick gpg encryption support - https://review.opendev.org/#/c/709432/ new backend driver - Hitachi - https://review.opendev.org/#/c/712832/ specs: https://review.opendev.org/#/q/project:openstack/cinder-specs+status:open

1 0

[cinder] victoria mid-cycle part 1 summary available
by Brian Rosmaita 25 Jun '20

25 Jun '20

In case you missed yesterday's R-16 virtual mid-cycle session, I've posted a summary: https://wiki.openstack.org/wiki/CinderVictoriaMidCycleSummary It includes a link to the recording (in case you want to see what you missed or if you want to re-live the excitement). Part 2 of the mid-cycle will be held the week of R-9. cheers, brian

1 0

OSF Community Meeting 1 Recording & Slides
by Allison Price 25 Jun '20

25 Jun '20

Hi everyone, Thank you for joining today’s OSF Community Meeting. If you missed the meeting, you have a few options on getting updated on what was covered. You can listen to the recording [1] and check out the slides [2] that were presented this morning. I have also attached a PDF of the slides if that’s easier to access. There will be a second OSF Community Meeting covering the same material tomorrow, Friday, June 26 at 0200 UTC (today, June 25 at 7pm PT). You can find the lineup of speakers and dial-in information here [3]. Stay tuned for the next OSF Community Meeting in July that will cover the OpenStack 10th birthday, and the next all project, quarterly update that will be held in September. Cheers, Allison [1] https://zoom.us/rec/share/vJF_FqPgxGJJQ9bntR7vaqM7N7i_X6a81yQa8vtcxU06amK9p… <https://zoom.us/rec/share/vJF_FqPgxGJJQ9bntR7vaqM7N7i_X6a81yQa8vtcxU06amK9p…> Password: 7W!T*i74 [2] https://docs.google.com/presentation/d/16V82OIYfthb3fFlVoes9jZGKMgDIJZ55F8f… [3] https://etherpad.opendev.org/p/OSF_Community_Meeting_Q2 <https://etherpad.opendev.org/p/OSF_Community_Meeting_Q2> Allison Price OpenStack Foundation allison(a)openstack.org

1 0

Python OpenStack SDK does not return Hypervisor hostname
by Anil Jangam 25 Jun '20

25 Jun '20

I have written a client code as follows. # Get Hypervisor details try: print(f"+----------------------------------------------------------+") print(f"| Hypervisor details |") print(f"+----------------------------------------------------------+") for hypervisor in conn.list_hypervisors(): print(f"Hypervisor is: {hypervisor}") print(f"Hypervisor status: {hypervisor.status}") print(f"Hypervisor vcpus: {hypervisor.vcpus_used}") print(f"Hypervisor type: {hypervisor.hypervisor_type}") print(f"Hypervisor id: {hypervisor.id}") print(f"Hypervisor state: {hypervisor.state}") print(f"Hypervisor host IP: {hypervisor.host_ip}") print(f"Hypervisor running VMs: {hypervisor.running_vms}") print(f"Hypervisor running VMs: {hypervisor.vcpus}") print(f"Hypervisor hostname: {hypervisor.hypervisor_hostname}") print(f"") except EndpointNotFound as exp: print("Error: {}".format(exp)) print(f"") When I print the 'hypervisor' object itself, most of the values are printed as shown below, however when I try to access 'hypervisor.hypervisor_hostname', it throws an exception. +----------------------------------------------------------+ | Hypervisor details | +----------------------------------------------------------+ Hypervisor is: openstack.compute.v2.hypervisor.Hypervisor(status=enabled, service={'host': 'cl3-Compute3', 'disabled_reason': None, 'id': '34db399d-25b9-4004-98b9-2d8bbce7b228'}, vcpus_used=0, hypervisor_type=QEMU, local_gb_used=0, vcpus=52, hypervisor_hostname=cl3-Compute3, memory_mb_used=25600, memory_mb=262032, current_workload=0, state=up, host_ip=192.168.10.116, cpu_info={'arch': 'x86_64', 'model': 'Broadwell', 'vendor': 'Intel', 'features': ['pge', 'avx', 'xsaveopt', 'clflush', 'sep', 'rtm', 'tsc_adjust', 'tsc-deadline', 'dtes64', 'invpcid', 'tsc', 'fsgsbase', 'xsave', 'smap', 'vmx', 'erms', 'xtpr', 'cmov', 'hle', 'smep', 'pcid', 'est', 'pat', 'monitor', 'smx', 'pbe', 'lm', 'msr', 'adx', '3dnowprefetch', 'nx', 'fxsr', 'syscall', 'tm', 'sse4.1', 'pae', 'sse4.2', 'pclmuldq', 'acpi', 'fma', 'vme', 'popcnt', 'mmx', 'osxsave', 'cx8', 'mce', 'de', 'rdtscp', 'ht', 'dca', 'lahf_lm', 'abm', 'rdseed', 'pdcm', 'mca', 'pdpe1gb', 'apic', 'sse', 'f16c', 'pse', 'ds', 'invtsc', 'pni', 'tm2', 'avx2', 'aes', 'sse2', 'ss', 'ds_cpl', 'arat', 'bmi1', 'bmi2', 'ssse3', 'fpu', 'cx16', 'pse36', 'mtrr', 'movbe', 'rdrand', 'x2apic'], 'topology': {'cores': 14, 'cells': 2, 'threads': 2, 'sockets': 1}}, running_vms=0, free_disk_gb=852, hypervisor_version=2012000, disk_available_least=849, local_gb=852, free_ram_mb=236432, id=1130407d-5afd-41f9-bc0c-2d7babda3ce7, location=Munch({'cloud': 'defaults', 'region_name': 'RegionOne', 'zone': None, 'project': Munch({'id': '6d4f1b107bbf4b94832f7ef72df61ef2', 'name': '5g', 'domain_id': None, 'domain_name': 'default'})})) Hypervisor status: enabled Hypervisor vcpus: 0 Hypervisor type: QEMU Hypervisor id: 1130407d-5afd-41f9-bc0c-2d7babda3ce7 Hypervisor state: up Hypervisor host IP: 192.168.10.116 Hypervisor running VMs: 0 Hypervisor running VMs: 52 Traceback (most recent call last): File "/Users/workspace/testprogs/python/opsviz/ops_worker.py", line 321, in <module> main() File "/Users/workspace/testprogs/python/opsviz/ops_worker.py", line 317, in main print_servers() File "/Users/workspace/testprogs/python/opsviz/ops_worker.py", line 115, in print_servers print(f"Hypervisor hostname: {hypervisor.hypervisor_hostname}") File "/Users/inventory/lib/python3.7/site-packages/openstack/resource.py", line 588, in __getattribute__ raise e File "/Users/inventory/lib/python3.7/site-packages/openstack/resource.py", line 582, in __getattribute__ return object.__getattribute__(self, name) AttributeError: 'Hypervisor' object has no attribute 'hypervisor_hostname' Is there anything wrong with the use of the API? How do I get the hypervisor hostname in my application code? Thank you.

3 6

[kolla] Introducing Kolla Kalls
by Radosław Piliszek 25 Jun '20

25 Jun '20

Hi fellow OpenStackers! During yesterday's Kolla meeting [1] I have proposed to have more focused, voice-based sessions related to Kolla development, similarly to what we have for operators with Kolla Klub [1]. The immediate response was rather positive and the name Kolla Kalls has been coined. Since Kolla Klub is running every other Thursday at 15:00 UTC, we decided to use the alternate weeks slot for Kolla Kalls but this can change if need arises. Kolla Kalls got their wiki page already [3] where the agenda will be posted. The first Kall is scheduled on July 9, 15:00 UTC (i.e. in two weeks time from today). The agenda for the first Kall is mostly about trying this meeting approach out. The hottest topic from our PTG is the quality/completeness of our documentation so it is a good topic for our first few sessions. It is likely going to involve CI testing discussions as well. The platform has not been decided on yet. We plan to give OpenDev's Meetpad a test ride and fall back to Google Meet which we practiced well with Kolla Klub and similar events - if Jitsu breaks for us. I learnt Meetpad does not (yet) support recording but we plan to document the meeting in a text form anyhow so we should be fine. Everyone interested in developing Kolla projects, that is Kolla, Kolla-Ansible and/or Kayobe is welcome to join the Kalls. The Kalls will be development-oriented and focus on topics such as implementation discussion, change planning, release planning and housekeeping. [1] http://eavesdrop.openstack.org/meetings/kolla/2020/kolla.2020-06-24-15.01.h… [2] https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_… [3] https://wiki.openstack.org/wiki/Meetings/Kolla/Kall -yoctozepto

1 0

[neutron] Drivers meeting agenda - 26.06.2020
by Slawek Kaplonski 25 Jun '20

25 Jun '20

Hi Neutron drivers, Below is agenda for tomorrow’s meeting. We have 2 RFE to discuss: https://bugs.launchpad.net/neutron/+bug/1882804 - RFE: allow replacing the QoS policy of bound port This one is follow-up after virtual PTG and discussions with Nova team, https://bugs.launchpad.net/neutron/+bug/1828494 - L3 agent’s capacity lets discuss again this proposal with “routers_max” parameter instead of bandwidth (See last comment there) There is also proposed spec (https://review.opendev.org/#/c/729532/) for: https://bugs.launchpad.net/neutron/+bug/1880532 - [RFE]L3 Router should support ECMP Please review it if You can and we will get back to this RFE next week. Ok, that’s all for today. See You all tomorrow on the meeting. — Slawek Kaplonski Senior software engineer Red Hat

1 0