April 2021 - openstack-discuss - lists.openstack.org

Fwd: DPDK+OVS with OpenStack
by Mark Wittling 23 Apr '25

23 Apr '25

Looking for someone who knows OpenStack with OpenVSwitch, and in addition to that, DPDK with OpenStack and OVS.I am using OpenStack Queens, with OpenVSwitch. The architecture I am using is documented here: https://docs.openstack.org/neutron/queens/admin/deploy-ovs-provider.htmlThe OVS I am using on the Compute Node, is compiled with DPDK, and I have enabled the datapath to netdev (DPDK) on br-prv (provider network bridge), and br-tun (tunneling bridge). But these two bridges, br-tun and br-prv, are patched into another OpenStack bridge, called br-int. I wasn’t actually sure about whether to tinker with this bridge, and wondered what datapath it was using.Then, I realized there is a parameter in the openvswitch_agent.ini file, which I will list here: # OVS datapath to use. 'system' is the default value and corresponds to the # kernel datapath. To enable the userspace datapath set this value to 'netdev'. # (string value) # Possible values: # system - <No description provided> # netdev - <No description provided> #datapath_type = system datapath_type = netdev So in tinkering with this, what I realized, is that when you set this datapath_type to system or netdev, it will adjust the br-int bridge to that datapath type.So here is my question. How can I launch a non-DPDK VM, if all of the bridges are using the netdev datapath type?Here is another question. What if one of the flavors don’t have the largepages property set on them? I assumed OpenStack would revert to a system datapath and not use DPDK for those VM interfaces. Well, I found out in testing, that is not the case. If you set all your bridges up for netdev, and you don’t set the property on the Flavor of the VM (largepages), the VM will launch, but it simply won’t work.Is there no way, on a specific Compute Host, to support both DPDK (netdev datapaths) and non-DPDK (system datapaths)?Either on a VM interface level (VM has one interface that is netdev DPDK and another that is system datapath non-DPDK)?Or on a VM by VM basis (VM 1 has 1 or more netdev datapath interfaces and VM 2 has 1 or more system datapath interfaces)?Am I right here? Once you set up a Compute Host for DPDK, it’s DPDK or nothing on that Compute Host? (edited)

3 2

How to config DPDK compute in OVN
by dangerzone ar 22 Apr '25

22 Apr '25

Hi....as far I understand ovs does support dpdk compute to be deployed. I'm referring to the guideline ' *https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html <https://docs.openstack.org/networking-ovn/queens/admin/dpdk.html>* ' ... It's too brief.. May I know how to config dpdk compute in OVN networking openstack? Hope someone could help what is the config to be done.... Currently compute is run without dpdk over openstack train ovn based. Please need some info on how I can proceed. Thank you

2 1

Live migration fails
by Szabo, Istvan (Agoda) 07 Aug '24

07 Aug '24

Hi, I have couple of compute nodes where the live migration fails with existing vms. When I quickly spawn a vm and try live migration it works so I assume shouldn't be a big problem with the compute node. However I have many existing vms where it fails with a servername not found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 ERROR nova.conductor.tasks.migrate [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Unable to find record for source node servername on servername: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Failed to compute_task_migrate_server: Compute host servername could not be found.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.605 227612 WARNING nova.scheduler.utils [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] [instance: 1517a2ac-3b51-4d8d-80b3-89a5614d1ae0] Setting instance to ACTIVE state.: ComputeHostNotFound: Compute host servername could not be found. /var/log/nova/nova-conductor.log:2021-04-21 14:47:12.672 227612 ERROR oslo_messaging.rpc.server [req-f4067a26-a233-4673-8c07-9a8a290980b0 dce35e6eceea4312bb0baa0510cef363 ca7e35079f4440c78bd9870724b9638b - default default] Exception during message handling: ComputeHostNotFound: Compute host am-osfecn-4025 Tried with this command: nova live-migration --block-migrate id. Any idea? Thank you. ________________________________ This message is confidential and is for the sole use of the intended recipient(s). It may also be privileged or otherwise protected by copyright or other legal rules. If you have received it by mistake please let us know by reply email and delete it from your system. It is prohibited to copy this message or disclose its content to anyone. Any confidentiality or privilege is not waived or lost by any mistaken delivery or unauthorized disclosure of the message. All messages sent to and from Agoda may be monitored to ensure compliance with company policies, to protect the company's interests and to remove potential malware. Electronic messages may be intercepted, amended, lost or deleted, or contain viruses.

5 16

[all] Dynamic Zuul results table in Gerrit 3
by Radosław Piliszek 04 Aug '22

04 Aug '22

Hello Fellow OpenStack and OpenDev Folks! TL;DR click on [3] and enjoy. I am starting this thread to not hijack the discussion happening on [1]. First of all, I would like to thank gibi (Balazs Gibizer) for hacking a way to get the place to render the table in the first place (pun intended). I have been a long-time-now user of [2]. I have improved and customised it for myself but never really got to share back the changes I made. The new Gerrit obviously broke the whole script so it was of no use to share at that particular state. However, inspired by gibi's work, I decided to finally sit down and fix it to work with Gerrit 3 and here it comes: [3]. Works well on Chrome with Tampermonkey. Not tested others. I hope you will enjoy this little helper (I do). I know the script looks super fugly but it generally boils down to a mix of styles of 3 people and Gerrit having funky UI rendering. Finally, I'd also like to thank hrw (Marcin Juszkiewicz) for linking me to the original Michel's script in 2019. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-November/019051… [2] https://opendev.org/x/coats/src/commit/444c95738677593dcfed0cfd9667d4c4f0d5… [3] https://gist.github.com/yoctozepto/7ea1271c299d143388b7c1b1802ee75e Kind regards, -yoctozepto

5 7

Nova not updating to new size of an extended in-use / attached cinder volume (Ceph RBD) to guest
by Christian Rohmann 28 Jun '22

28 Jun '22

Hello Openstack-Discuss, after some digging I found out that cinder learned to resize attached (in-use) volumes quite a while ago with the introduction of the initial "extend 'in-use' volume" feature: https://review.opendev.org/c/openstack/cinder/+/454287/ The support was then extended to also cover Ceph RBD backed volumes with: https://review.opendev.org/c/openstack/nova/+/613039/ Since this is only about the cinder part, I was wondering if nova would ever find out and would actively rescan the device / volume and quintessentially present an increased new size to the guest. Apparently this is where a certain volume-extended event comes into play: https://review.opendev.org/c/openstack/nova/+/454322/ that is to be emitted by cinder when a volume had been extened. I then went head and tried this with the openstack cli (as Horizon does not seem to support / offer to resize in-use volumes. I run Openstack Train with Ceph RBD as storage. First I ran into an issue with the openstack cli (https://bugs.launchpad.net/cinder/+bug/1871759/comments/2 <https://bugs.launchpad.net/cinder/+bug/1871759/comments/2>) but using cinder extend $volumeid $newsize I was able to resize in-use volumes just fine. The only thing missing was the propagation to the guest. I played around with SCSI rescans, but that did not work, reboots also failed to do anyting in this regards. Stopping and starting the VM did work, but why having the capability to online-resize an attached volume when not being able to resize the guest volume as well? Apparently there seems to be an old and somewhat similar observation / bug with https://bugs.launchpad.net/nova/+bug/1369465 So I was simply wondering if this is expected to be working? Are there any special settings / options I need to set to enable this feature? Thanks and with kind regards Christian

4 9

[nova][dev] Revisiting qemu emulation where guest arch != host arch
by Apsey, Christopher 05 Jan '22

05 Jan '22

All, A few years ago I asked a question[1] about why nova, when given a hw_architecture property from glance for an image, would not end up using the correct qemu-system-xx binary when starting the guest process on a compute node if that compute nodes architecture did not match the proposed guest architecture. As an example, if we had all x86 hosts, but wanted to run an emulated ppc guest, we should be able to do that given that at least one compute node had qemu-system-ppc already installed and libvirt was successfully reporting that as a supported architecture to nova. It seemed like a heavy lift at the time, so it was put on the back burner. I am now in a position to fund a contract developer to make this happen, so the question is: would this be a useful blueprint that would potentially be accepted? Most of the time when people want to run an emulated guest they would just nest it inside of an already running guest of the native architecture, but that severely limits observability and the task of managing any more than a handful of instances in this manner quickly becomes a tangled nightmare of networking, etc. I see real benefit in allowing this scenario to run natively so all of the tooling that exists for fleet management 'just works'. This would also be a significant differentiator for OpenStack as a whole. Thoughts? [1] http://lists.openstack.org/pipermail/openstack-operators/2018-August/015653… Chris Apsey Director | Georgia Cyber Range GEORGIA CYBER CENTER 100 Grace Hopper Lane | Augusta, Georgia | 30901 https://www.gacybercenter.org

2 2

Help with eventlet 0.26.1 and dnspython >= 2
by Thomas Goirand 04 Oct '21

04 Oct '21

Hi, As you may know, eventlet is incompatible with dnspython >= 2.0.0.0rc1. See [1] for the details. However, Debian unstable has 2.0.0. Would there be some good soul willing to help me fix this situation? I would need a patch to fix this, but I'm really not sure how to start. Cheers, Thomas Goirand (zigo)

8 15

[all]Introduction to venus which is the project of log management and has been contributed to the OpenStack community
by Liye Pang(逄立业) 10 Sep '21

10 Sep '21

Hello everyone, after feedback from a large number of operations and maintenance personnel in InCloud OpenStack, we developed the log management project “Venus” for the OpenStack projects and that has contributed to the OpenStack community. The following is an introduction to “Venus”. If there is interest in the community, we are interested in proposing it to become an official OpenStack project in the future. Background In the day-to-day operation and maintenance of large-scale cloud platform, the following problems are encountered： l Time-consuming for log querying while the server increasing to thousands. l Difficult to retrieve logs, since there are many modules in the platform, e.g. systems service, compute, storage, network and other platform services. l The large amount and dispersion of log make faults are difficult to be discovered. l Because of distributed and interaction between components of the cloud platform, and scattered logs between components, it will take more time to locate problems. About Venus According to the key requirements of OpenStack in log storage, retrieval, analysis and so on, we introduced Venus project, a unified log management module. This module can provide a one-stop solution to log collection, cleaning, indexing, analysis, alarm, visualization, report generation and other needs, which involves helping operator or maintainer to quickly solve retrieve problems, grasp the operational health of the platform, and improve the management capabilities of the cloud platform. Additionally, this module plans to use machine learning algorithms to quickly locate IT failures and root causes, and improve operation and maintenance efficiency. Application scenario Venus played a key role in the following scenarios： l Retrieval: Provide a simple and easy-to-use way to retrieve all log and the context. l Analysis: Realize log association, field value statistics, and provide multi-scene and multi-dimensional visual analysis reports. l Alerts：Convert retrieval into active alerts to realize the error finding in massive logs. l Issue location: Establish a chain relationship and knowledge graphs to quickly locate problems. Overall structure The architecture of log management system based on Venus and elastic search is as follows: Diagram 0: Architecture of Venus venus_api: API module，provide API、rest-api service. venus_manager: Internal timing task module to realize the core functions of the log system. Current progress The current progress of the Venus project is as follows: l Collection：Develop fluentd collection tasks based on collectd to read, filter, format and send plug-ins for OpenStack, operating systems, and platform services, etc. l Index：Dealing with multi-dimensional index data in elasticsearch, and provide more concise and comprehensive authentication interface to return query results. l Analysis：Analyzing and display the related module errors, Mariadb connection errors, and Rabbitmq connection errors. l Alerts：Develop alarm task code to set threshold for the number of error logs of different modules at different times, and provides alarm services and notification services. l Location：Develop the call chain analysis function based on global_requested series, which can show the execution sequence, time and error information, etc., and provide the export operation. l Management：Develop configuration management functions in the log system, such as alarm threshold setting, timing task management, and log saving time setting, etc. Application examples Two examples of Venus application scenarios are as follows. 1. The virtual machine creation operation was performed on the cloud platform and it was found that the virtual machine was not created successfully. First, we can find the request id of the operation and jump to the virtual machine creation call chain page. Then, we can query the calling process, view and download the details of the log of the call. 2. In the cloud platform, the error log of each module can be converted into alarms to remind the users. Further, we can retrieve the details of the error log and error log statistics. Next step The next step of the Venus project is as follows: * Collection：In addition to fluent, other collection plugins such as logstash will be integrated. * Analysis: Explore more operation and maintenance scenarios, and conduct statistical analysis and alarm on key data. * display: The configuration, analysis and alarm of Venus will be integrated into horizon in the form of plugin. * location: Form clustering log and construct knowledge map, and integrate algorithm class library to locate the root cause of the fault. Venus Project Registry Venus library: https://opendev.org/inspur/venus You can grab the source code using the following git command: git clone https://opendev.org/inspur/venus.git Venus Demo Youtu.be: <https://youtu.be/mE2MoEx3awM> https://youtu.be/mE2MoEx3awM

7 15

placement service issue (placement-status upgrade check failure)
by Deepak Mohanty 12 Jul '21

12 Jul '21

I need your help with installation of placement service on Ubuntu 20.04. I have followed the steps in: https://docs.openstack.org/placement/wallaby/install/install-ubuntu.html I am facing the following issue when I try to verify the installation: $ placement-status upgrade check Error: Traceback (most recent call last): File "/usr/lib/python3/dist-packages/oslo_upgradecheck/upgradecheck.py", line 196, in run return conf.command.action_fn() File "/usr/lib/python3/dist-packages/oslo_upgradecheck/upgradecheck.py", line 104, in check result = func_name(self, **kwargs) File "/usr/lib/python3/dist-packages/oslo_upgradecheck/common_checks.py", line 41, in check_policy_json policy_path = conf.find_file(conf.oslo_policy.policy_file) File "/usr/lib/python3/dist-packages/oslo_config/cfg.py", line 2543, in find_file raise NotInitializedError() oslo_config.cfg.NotInitializedError: call expression on parser has not been invoked I did a bit of debugging and found that the policy file is: policy.json. I could not find any policy.json on my machine. I created an empty policy.json at: /etc/placement/policy.json (user and group = placement). That too did not work. I have followed the steps in the install guide twice, deleting the placement database and other resources and recreating them. I continue to see the same issue. Thank you for your time.

5 6

[all][stable] Ocata - End of Life
by Előd Illés 09 Jun '21

09 Jun '21

Hi, Sorry, this will be long :) as there are 3 topics around old stable branches and 'End of Life'. 1. Deletion of ocata-eol tagged branches With the introduction of Extended Maintenance process [1][2] some cycles ago, the 'End of Life' (EOL) process also changed: * branches were no longer EOL tagged and "mass-deleted" at the end of maintenance phase * EOL'ing became a project decision * if a project decides to cease maintenance of a branch that is in Extended Maintenance, then they can tag their branch with $series-eol However, the EOL-tagging process was not automated or redefined process-wise, so that meant the branches that were tagged as EOL were not deleted. Now (after some changing in tooling) Release Management team finally will start to delete EOL-tagged branches. In this mail I'm sending a *WARNING* to consumers of old stable branches, especially *ocata*, as we will start deleting the *ocata-eol* tagged branches in a *week*. (And also newer *-eol branches later on) 2. Ocata branch Beyond the 1st topic we must clarify the future of Ocata stable branch in general: tempest jobs became broken about ~ a year ago. That means that projects had two ways forward: a. drop tempest testing to unblock gate b. simply don't support ocata branch anymore As far as I see the latter one happened and stable/ocata became unmaintained probably for every projects. So my questions are regarding this: * Is any project still using/maintaining their stable/ocata branch? * If not: can Release Team initiate a mass-EOL-tagging of stable/ocata? 3. The 'next' old stable branches Some projects still support their Pike, Queens and Rocky branches. These branches use Xenial and py2.7 and both are out of support. This results broken gates time to time. Especially nowadays. These issues suggest that these branches are closer and closer to being unmaintained. So I call the attention of interested parties, who are for example still consuming these stable branches and using them downstream to put effort on maintaining the branches and their CI/gates. It is a good practice for stable maintainers to check if there are failures in their projects' periodic-stable jobs [3], as those are good indicators of the health of their stable branches. And if there are, then try to fix it as soon as possible. [1] https://governance.openstack.org/tc/resolutions/20180301-stable-branch-eol.… [2] https://docs.openstack.org/project-team-guide/stable-branches.html#maintena… [3] http://lists.openstack.org/pipermail/openstack-stable-maint/2021-April/date… Thanks, Előd

1 2

[neutron][interop][refstack] New tests and capabilities to track in interop
by Martin Kopec 07 Jun '21

07 Jun '21

Hi everyone, I would like to further discuss the topics we covered with the neutron team during the PTG [1]. * adding address_group API capability It's tested by tests in neutron-tempest-plugin. First question is if tests which are not directly in tempest can be a part of a non-add-on marketing program? It's possible to move them to tempest though, by the time we do so, could they be marked as advisory? * Shall we include QoS tempest tests since we don't know what share of vendors enable QoS? Could it be an add-on? These tests are also in neutron-tempest-plugin, I assume we're talking about neutron_tempest_plugin.api.test_qos tests. If we want to include these tests, which program should they belong to? Do we wanna create a new one? [1] https://etherpad.opendev.org/p/neutron-xena-ptg Thanks, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA

4 8

Question regarding the production status of DB2 in Trove
by Bekir Fajkovic 01 Jun '21

01 Jun '21

Hello! One question regarding the development status of DB2 inside Trove. I see that DB2 is still in experimental phase, when could it be expected for that datastore type to get production ready status? Best Regards. Bekir Fajkovic Senior DBA Mobile: +46 70 019 48 47 www.citynetwork.eu | www.citycloud.com INNOVATION THROUGH OPEN IT INFRASTRUCTURE ISO 9001, 14001, 27001, 27015 & 27018 CERTIFIED

3 8

[simplification] Making ask.openstack.org read-only
by Thierry Carrez 27 May '21

27 May '21

Hi everyone, This has been discussed several times on this mailing list in the past, but we never got to actually pull the plug. Ask.openstack.org was launched in 2013. The reason for hosting our own setup was to be able to support multiple languages, while StackOverflow rejected our proposal to have our own openstack-branded StackExchange site. The Chinese ask.o.o side never really took off. The English side also never really worked perfectly (like email alerts are hopelessly broken), but we figured it would get better with time if a big community formed around it. Fast-forward to 2020 and the instance is lacking volunteers to help run it, while the code (and our customization of it) has become more complicated to maintain. It regularly fails one way or another, and questions there often go unanswered, making us look bad. Of the top 30 users, most have abandoned the platform since 2017, leaving only Bernd Bausch actively engaging and helping moderate questions lately. We have called for volunteers several times, but the offers for help never really materialized. At the same time, people are asking OpenStack questions on StackOverflow, and sometimes getting answers there[1]. The fragmentation of the "questions" space is not helping users getting good answers. I think it's time to pull the plug, make ask.openstack.org read-only (so that links to old answers are not lost) and redirect users to the mailing-list and the "OpenStack" tag on StackOverflow. I picked StackOverflow since it seems to have the most openstack questions (2,574 on SO, 76 on SuperUser and 430 on ServerFault). We discussed that option several times, but I now proposed a change to actually make it happen: https://review.opendev.org/#/c/746497/ It's always a difficult decision to make to kill a resource, but I feel like in this case, consolidation and simplification would help. Thoughts, comments? [1] https://stackoverflow.com/questions/tagged/openstack -- Thierry

10 18

[telemetry] Retire panko
by Matthias Runge 25 May '21

25 May '21

Hi there, over the past couple of cycles, we have seen decreasing interest on panko. Also it has some debts, which were just carried over from the early days. We discussed over at the PTG and didn't really found a reason to keep it alive or included under OpenStack. With that, it also makes sense to retire puppet-panko. I'll wait for 1-2 weeks and propose appropriate patches to get it retired then, if I don't hear anything against it or if there are any takers. Matthias

1 2

[all][qa][cinder][octavia][murano] Devstack dropping support for Ubuntu Bionic 18.04
by Ghanshyam Mann 20 May '21

20 May '21

Hello Everyone, As per the testing runtime since Victoria [1], we need to move our CI/CD to Ubuntu Focal 20.04 but it seems there are few jobs still running on Bionic. As devstack team is planning to drop the Bionic support you need to move those to Focal otherwise they will start failing. We are planning to merge the devstack patch by 2nd week of May. - https://review.opendev.org/c/openstack/devstack/+/788754 I have not listed all the job but few of them which were failing with ' rtslib-fb-targetctl error' are below: Cinder- cinder-plugin-ceph-tempest-mn-aa - https://opendev.org/openstack/cinder/src/commit/7441694cd42111d8f24912f03f6… python-cinderclient - python-cinderclient-functional-py36 - https://review.opendev.org/c/openstack/python-cinderclient/+/788834 Octavia- https://opendev.org/openstack/octavia-tempest-plugin/src/branch/master/zuul… Murani- murano-dashboard-sanity-check -https://opendev.org/openstack/murano-dashboard/src/commit/b88b32abdffc171e6650450273004a41575d2d68/.zuul.yaml#L15 Also if your 3rd party CI is still running on Bionic, you can plan to migrate it to Focal before devstack patch merge. [1] https://governance.openstack.org/tc/reference/runtimes/victoria.html -gmann

10 24

[stein][neutron] gratuitous arp
by Ignazio Cassano 14 May '21

14 May '21

Hello, I have a problem on stein neutron. When a vm migrate from one node to another I cannot ping it for several minutes. If in the vm I put a script that ping the gateway continously, the live migration works fine and I can ping it. Why this happens ? I read something about gratuitous arp. Please, help me ? Any workaround , please ? Best Regards Ignazio

3 33

[octavia] victoria - loadbalancer works but its operational status is offline
by apps＠mossakowski.ch 13 May '21

13 May '21

Hello, I have stable/victoria baremetal openstack with octavia installed on centos8 using openvswitch mechanism driver: octavia api on controller, health-manager,housekeeping,worker on 3 compute/network nodes. Official docs include only ubuntu with linuxbridge mechanism but I used https://github.com/prastamaha/openstack-octavia as a reference to get it working on centos8 with ovs. I will push those docs instructions for centos8 soon: https://github.com/openstack/octavia/tree/master/doc/source/install. I created basic http scenario using https://docs.openstack.org/octavia/victoria/user/guides/basic-cookbook.html…. Loadbalancer works but its operational status is offline (openstack_loadbalancer_outputs.txt). On all octavia workers I see the same warning message in health_manager.log: Health Manager experienced an exception processing a heartbeat message from ('172.31.255.233', 1907). Ignoring this packet. Exception: 'NoneType' object has no attribute 'encode' I've searched for related active bug but all I found is this not related in my opinion: https://storyboard.openstack.org/#!/story/2008615 I'm attaching all info I've gathered: - octavia.conf and health_manager debug logs (octavia_config_and_health_manager_logs.txt) - tcpdump from amphora VM (tcpdump_from_amphora_vm.txt) - tcpdump from octavia worker (tcpdump_from_octavia_worker.txt) - debug amphora-agent.log from amphora VM (amphora-agent.log) Can you point me to the right direction what I have missed? Thanks! Piotr Mossakowski https://github.com/moss2k13

4 5

[ops][victoria][cinder] Import volume?
by DHilsbos＠performair.com 11 May '21

11 May '21

All; I'm looking to transfer several VMs from XenServer to an OpenStack Victoria cloud. Finding explanations for importing Glance images is easy, but I haven't been able to find a tutorial on importing Cinder volumes. Since they are currently independent servers / volumes it seems somewhat wasteful and messy to import each VMs disk as an image just to spawn a volume from it. We're using Ceph as the storage provider for Glance and Cinder. Thank you, Dominic L. Hilsbos, MBA Director - Information Technology Perform Air International Inc. DHilsbos(a)PerformAir.com www.PerformAir.com

3 5

[zun][horizon] How to display containers among VMs on network topology ?
by Maxime d'Estienne 11 May '21

11 May '21

Hello, I installed Zun on my stack and it works very well, I have a few containers up and running. I also added the zun-ui plugin for Horizon wich allows me to see the list of containers and to create them. But I often use the network topology view, wich I found very clean sometimes. I wondered if there is a solution to display the containers as are Vm's ? Thank you ! Maxime

2 2

Re: [ironic] IPA image does not want to boot with UEFI
by Julia Kreger 10 May '21

10 May '21

Adding the list back and trimming the message. Replies in-band. Well, that is good that the server is not signed, nor other esp images are not working. On Thu, Apr 1, 2021 at 11:20 AM Vuk Gojnic <vuk.gojnic(a)gmail.com> wrote: > > Hey Julia, > > Thanks for asking. I have tried with several ESP image options with same effect (one taken from Ubuntu Live ISO that boots on that node, another downloaded and third made with grub tools). None of them was signed. Interesting. At least it is consistent! Have you tried to pull down the iso image and take it apart to verify it is UEFI bootable against a VM or another physical machine? I'm wondering if you need both uefi parameters set. You definitely don't have properties['capabilities']['boot_mode'] set which is used or... maybe a better word to use is drawn in for asserting defaults, but you do have the deploy_boot_mode setting set. I guess a quick manual sanity check of the actual resulting iso image is going to be critical. Debug logging may also be useful, and I'm only thinking that because there is no logging from the generation of the image. > > The server is not in UEFI secure boot mode. Interesting, sure sounds like it is based on your original message. :( > Btw. I will be on holidays for next week so I might not be able to follow up on this discussion before Apr 12th. No worries, just ping us on irc.freenode.net in #openstack-ironic if a reply on the mailing list doesn't grab our attention. > > Bests, > Vuk > > On Thu, Apr 1, 2021 at 4:20 PM Julia Kreger <juliaashleykreger(a)gmail.com> wrote: >> >> Greetings, >> >> Two questions: >> 1) Are the ESP image contents signed, or are they built using one of >> the grub commands? >> 2) Is the machine set to enforce secure boot at this time? >> >> [trim]

2 3

[puppet] Propose retiring puppet-glare
by Takashi Kajinami 09 May '21

09 May '21

Hello, I'd like to propose retiring puppet-galre project, because the Glare[1] project looks inactive for a while based on the following three points - No actual development is made for 2 years - No release was made since the last Rocky release - setup.cfg is not maintained and the python versions listed are very outdated [1] https://opendev.org/x/glare I'll wait for 1-2 weeks to hear opinions from others. If anybody is interested in keeping the puppet-glare project or has intention to maintain Glare itself then please let me know. Thank you, Takashi

4 5

[devstack][infra] POST_FAILURE on export-devstack-journal : Export journal
by Martin Kopec 09 May '21

09 May '21

Hi, one of our jobs (python-tempestconf project) is frequently failing with POST_FAILURE [1] during the following task: export-devstack-journal : Export journal I'm bringing this to a broader audience as we're not sure where exactly the issue might be. Did you encounter a similar issue lately or in the past? [1] https://zuul.opendev.org/t/openstack/builds?job_name=python-tempestconf-tem… Thanks for any advice, -- Martin Kopec

4 10

Proposing Cédric Jeanneret (Tengu) for tripleo-core
by James Slagle 07 May '21

07 May '21

I'm proposing we formally promote Cédric to full tripleo-core duties. He is already in the gerrit group with the understanding that his +2 is for validations. His experience and contributions have grown a lot since then, and I'd like to see that +2 expanded to all of TripleO. If there are no objections, we'll consider the change official at the end of next week. -- -- James Slagle --

24 24

[ptl][release][stable][EM] Extended Maintenance - Train
by Előd Illés 05 May '21

05 May '21

Hi, As Wallaby was released the day before yesterday and we are in a less busy period, it is a good opportunity to call your attention to the following: In less than a month Train is planned to transition to Extended Maintenance phase [1] (planned date: 2021-05-12). I have generated the list of the current *open* and *unreleased* changes in stable/train for the follows-policy tagged repositories [2] (where there are such patches). These lists could help the teams who are planning to do a *final* release on Train before moving stable/train branches to Extended Maintenance. Feel free to edit and extend these lists to track your progress! * At the transition date the Release Team will tag the*latest* (Train) *releases* of repositories with *train-em* tag. * After the transition stable/train will be still open for bug fixes, but there won't be any official releases. NOTE: teams, please focus on wrapping up your libraries first if there is any concern about the changes, in order to avoid broken releases! Thanks, Előd [1] https://releases.openstack.org/ [2] https://etherpad.opendev.org/p/train-final-release-before-em

1 1

[TripleO] stable/wallaby branching
by Marios Andreou 05 May '21

05 May '21

Hello TripleO, quick update on the plan for stable/wallaby branching. The goal is to release tripleo stable/wallaby just after PTG i.e. last week of April. The tripleo-ci team have spent the previous sprint preparing and we now have the integration and component pipelines in place [1][2]. As of today we should also have the upstream check/gate multinode branchful jobs. We are planning to use this current sprint to resolve issues and ensure we have the CI coverage in place so we can safely release all the tripleo things. As we usually do, we are going to first branch python-tripleoclient and tripleo-common so we can exercise and sanity check the CI jobs. The stable/wallaby for client and common will appear after we merge [3]. *** PLEASE AVOID *** posting patches to stable/wallaby python-tripleoclient or tripleo-common until the CI team has completed our testing. Basically until we are ready to create a stable/wallaby for all the tripleo things (which will be announced in due course). Obviously as always please speak up if you disagree with any of the above or if something doesn't make sense or if you have any concerns about the proposed timings regards, marios [1] https://review.rdoproject.org/zuul/builds?pipeline=openstack-periodic-integ… [2] https://review.rdoproject.org/zuul/builds?pipeline=openstack-component-trip… [3] https://review.opendev.org/c/openstack/releases/+/785670

1 1

[release][ironic] ironic-python-agent-builder release model change
by Riccardo Pittau 04 May '21

04 May '21

Hello fellow openstackers! During the recent xena ptg, the ironic community had a discussion about the need to move the ironic-python-agent-builder project from an independent model to the standard release model. When we initially split the builder from ironic-python-agent, we decided against it, but considering some problems we encountered during the road, the ironic community seems to be in favor of the change. The reasons for this are mainly to strictly align the image building project to ironic-python-agent releases, and ease dealing with the occasional upgrade of tinycore linux, the base image used to build the "tinyipa" ironic-python-agent ramdisk. We'd like to involve the release team to ask for advice, not only on the process, but also considering that we need to ask to cut the first branch for the wallaby stable release, and we know we're a bit late for that! :) Thank you in advance for your help! Riccardo

5 8

Openstack Stack issues
by Premkumar Subramaniyan 04 May '21

04 May '21

Hi, I am using the Openstack *USURI *version in *Centos7*. Due to some issues my disk size is full,I freed up the space. Afte that some service went down. After that I have issues in creating the stack and list stack. Attached the Screenshot for your reference [opnfv@aio1 ~]$ openstack stack list --debug START with options: stack list --debug options: Namespace(access_token='***', access_token_endpoint='', access_token_type='', application_credential_id='', application_credential_name='', application_credential_secret='***', auth_methods='', auth_type='', auth_url='http://10.200.134.218:5000/v3', cacert=None, cert='', client_id='', client_secret='***', cloud='', code='', debug=True, default_domain='default', default_domain_id='', default_domain_name='', deferred_help=False, discovery_endpoint='', domain_id='', domain_name='', endpoint='', identity_provider='', insecure=None, interface='public', key='', log_file=None, openid_scope='', os_beta_command=False, os_compute_api_version='', os_identity_api_version='3', os_image_api_version='', os_network_api_version='', os_object_api_version='', os_orchestration_api_version='1', os_project_id=None, os_project_name=None, os_volume_api_version='', passcode='', password='***', project_domain_id='default', project_domain_name='', project_id='0e75229392c54a398ab302a8e43aebe6', project_name='admin', protocol='', redirect_uri='', region_name='RegionOne', remote_project_domain_id='', remote_project_domain_name='', remote_project_id='', remote_project_name='', service_provider='', system_scope='', timing=False, token='***', trust_id='', user_domain_id='', user_domain_name='Default', user_id='', username='admin', verbose_level=3, verify=None) Auth plugin password selected auth_config_hook(): {'api_timeout': None, 'verify': True, 'cacert': None, 'cert': None, 'key': None, 'baremetal_status_code_retries': '5', 'baremetal_introspection_status_code_retries': '5', 'image_status_code_retries': '5', 'disable_vendor_agent': {}, 'interface': 'public', 'floating_ip_source': 'neutron', 'image_api_use_tasks': False, 'image_format': 'qcow2', 'message': '', 'network_api_version': '2', 'object_store_api_version': '1', 'secgroup_source': 'neutron', 'status': 'active', 'auth': {'user_domain_name': 'Default', 'project_domain_id': 'default', 'project_id': '0e75229392c54a398ab302a8e43aebe6', 'project_name': 'admin'}, 'verbose_level': 3, 'deferred_help': False, 'debug': True, 'region_name': 'RegionOne', 'default_domain': 'default', 'timing': False, 'username': 'admin', 'password': '***', 'auth_url': ' http://10.200.134.218:5000/v3', 'beta_command': False, 'identity_api_version': '3', 'orchestration_api_version': '1', 'auth_type': 'password', 'networks': []} defaults: {'api_timeout': None, 'verify': True, 'cacert': None, 'cert': None, 'key': None, 'auth_type': 'password', 'baremetal_status_code_retries': 5, 'baremetal_introspection_status_code_retries': 5, 'image_status_code_retries': 5, 'disable_vendor_agent': {}, 'interface': None, 'floating_ip_source': 'neutron', 'image_api_use_tasks': False, 'image_format': 'qcow2', 'message': '', 'network_api_version': '2', 'object_store_api_version': '1', 'secgroup_source': 'neutron', 'status': 'active'} cloud cfg: {'api_timeout': None, 'verify': True, 'cacert': None, 'cert': None, 'key': None, 'baremetal_status_code_retries': '5', 'baremetal_introspection_status_code_retries': '5', 'image_status_code_retries': '5', 'disable_vendor_agent': {}, 'interface': 'public', 'floating_ip_source': 'neutron', 'image_api_use_tasks': False, 'image_format': 'qcow2', 'message': '', 'network_api_version': '2', 'object_store_api_version': '1', 'secgroup_source': 'neutron', 'status': 'active', 'auth': {'user_domain_name': 'Default', 'project_domain_id': 'default', 'project_id': '0e75229392c54a398ab302a8e43aebe6', 'project_name': 'admin'}, 'verbose_level': 3, 'deferred_help': False, 'debug': True, 'region_name': 'RegionOne', 'default_domain': 'default', 'timing': False, 'username': 'admin', 'password': '***', 'auth_url': ' http://10.200.134.218:5000/v3', 'beta_command': False, 'identity_api_version': '3', 'orchestration_api_version': '1', 'auth_type': 'password', 'networks': []} compute API version 2.1, cmd group openstack.compute.v2 identity API version 3, cmd group openstack.identity.v3 image API version 2, cmd group openstack.image.v2 network API version 2, cmd group openstack.network.v2 object_store API version 1, cmd group openstack.object_store.v1 volume API version 3, cmd group openstack.volume.v3 orchestration API version 1, cmd group openstack.orchestration.v1 command: stack list -> heatclient.osc.v1.stack.ListStack (auth=True) Auth plugin password selected auth_config_hook(): {'api_timeout': None, 'verify': True, 'cacert': None, 'cert': None, 'key': None, 'baremetal_status_code_retries': '5', 'baremetal_introspection_status_code_retries': '5', 'image_status_code_retries': '5', 'disable_vendor_agent': {}, 'interface': 'public', 'floating_ip_source': 'neutron', 'image_api_use_tasks': False, 'image_format': 'qcow2', 'message': '', 'network_api_version': '2', 'object_store_api_version': '1', 'secgroup_source': 'neutron', 'status': 'active', 'auth': {'user_domain_name': 'Default', 'project_domain_id': 'default', 'project_id': '0e75229392c54a398ab302a8e43aebe6', 'project_name': 'admin'}, 'additional_user_agent': [('osc-lib', '2.3.1')], 'verbose_level': 3, 'deferred_help': False, 'debug': True, 'region_name': 'RegionOne', 'default_domain': 'default', 'timing': False, 'username': 'admin', 'password': '***', 'auth_url': 'http://10.200.134.218:5000/v3', 'beta_command': False, 'identity_api_version': '3', 'orchestration_api_version': '1', 'auth_type': 'password', 'networks': []} Using auth plugin: password Using parameters {'auth_url': 'http://10.200.134.218:5000/v3', 'project_id': '0e75229392c54a398ab302a8e43aebe6', 'project_name': 'admin', 'project_domain_id': 'default', 'username': 'admin', 'user_domain_name': 'Default', 'password': '***'} Get auth_ref REQ: curl -g -i -X GET http://10.200.134.218:5000/v3 -H "Accept: application/json" -H "User-Agent: openstacksdk/0.55.0 keystoneauth1/4.3.1 python-requests/2.25.1 CPython/3.6.8" Starting new HTTP connection (1): 10.200.134.218:5000 http://10.200.134.218:5000 "GET /v3 HTTP/1.1" 200 254 RESP: [200] Connection: close Content-Length: 254 Content-Security-Policy: default-src 'self' https: wss:; Content-Type: application/json Date: Thu, 29 Apr 2021 05:26:21 GMT Server: nginx/1.18.0 Vary: X-Auth-Token X-Content-Type-Options: nosniff X-Frame-Options: DENY X-XSS-Protection: 1; mode=block x-openstack-request-id: req-5e95ffe0-5fde-4234-9e7c-f79287e539a0 RESP BODY: {"version": {"id": "v3.14", "status": "stable", "updated": "2020-04-07T00:00:00Z", "links": [{"rel": "self", "href": " http://10.200.134.218:5000/v3/"}], "media-types": [{"base": "application/json", "type": "application/vnd.openstack.identity-v3+json"}]}} GET call to http://10.200.134.218:5000/v3 used request id req-5e95ffe0-5fde-4234-9e7c-f79287e539a0 Making authentication request to http://10.200.134.218:5000/v3/auth/tokens Resetting dropped connection: 10.200.134.218 http://10.200.134.218:5000 "POST /v3/auth/tokens HTTP/1.1" 201 6037 {"token": {"methods": ["password"], "user": {"domain": {"id": "default", "name": "Default"}, "id": "b3c6351eb7d841678297401969eb01c7", "name": "admin", "password_expires_at": null}, "audit_ids": ["-pXpoN1cRyS5ioGPNOEdkg"], "expires_at": "2021-04-29T17:26:22.000000Z", "issued_at": "2021-04-29T05:26:22.000000Z", "project": {"domain": {"id": "default", "name": "Default"}, "id": "0e75229392c54a398ab302a8e43aebe6", "name": "admin"}, "is_domain": false, "roles": [{"id": "5123dc78efec436dad719099e4979536", "name": "admin"}, {"id": "6ddb974942354b53a6cc1dfe10cc58a9", "name": "member"}, {"id": "24de7013b1124fcd99c31482ede6a855", "name": "reader"}], "catalog": [{"endpoints": [{"id": "9ef24c86cb5e49f6aecb882adfe8b8be", "interface": "admin", "region_id": "RegionOne", "url": "http://172.29.236.100:5000", "region": "RegionOne"}, {"id": "c43060c06da940ab9c9de47d96efca5f", "interface": "internal", "region_id": "RegionOne", "url": " http://172.29.236.100:5000", "region": "RegionOne"}, {"id": "ff7a8af4a859400584fc2f4025f8110a", "interface": "public", "region_id": "RegionOne", "url": "http://10.200.134.218:5000", "region": "RegionOne"}], "id": "0177ada716b8496390b53f88de002762", "type": "identity", "name": "keystone"}, {"endpoints": [{"id": "01dcd05263a5499a9222459614c19099", "interface": "admin", "region_id": "RegionOne", "url": " http://172.29.236.100:8776/v2/0e75229392c54a398ab302a8e43aebe6", "region": "RegionOne"}, {"id": "8f8d9172c7b94baf8971d6fce50c3c22", "interface": "public", "region_id": "RegionOne", "url": " http://10.200.134.218:8776/v2/0e75229392c54a398ab302a8e43aebe6", "region": "RegionOne"}, {"id": "abe2895da1fc47e2a795136a0f154dad", "interface": "internal", "region_id": "RegionOne", "url": " http://172.29.236.100:8776/v2/0e75229392c54a398ab302a8e43aebe6", "region": "RegionOne"}], "id": "2a8111a2e7224baaa928ba19545754cd", "type": "volumev2", "name": "cinderv2"}, {"endpoints": [{"id": "027033523daf4adc8d1a180e41f57c00", "interface": "admin", "region_id": "RegionOne", "url": " http://172.29.236.100:8004/v1/0e75229392c54a398ab302a8e43aebe6", "region": "RegionOne"}, {"id": "765c7ea8a9c4456bb23ba5d519ffa033", "interface": "internal", "region_id": "RegionOne", "url": " http://172.29.236.100:8004/v1/0e75229392c54a398ab302a8e43aebe6", "region": "RegionOne"}, {"id": "f3a264f72c0a4960b9740e466eb52d83", "interface": "public", "region_id": "RegionOne", "url": " http://10.200.134.218:8004/v1/0e75229392c54a398ab302a8e43aebe6", "region": "RegionOne"}], "id": "31803d9d7a3e4d4e92d9522459526a68", "type": "orchestration", "name": "heat"}, {"endpoints": [{"id": "1183338890744524b28c274ca61e93ff", "interface": "admin", "region_id": "RegionOne", "url": "http://172.29.236.100:8780", "region": "RegionOne"}, {"id": "21bcc1ebb4de44d2931f0220d6fa1576", "interface": "internal", "region_id": "RegionOne", "url": "http://172.29.236.100:8780", "region": "RegionOne"}, {"id": "70f912ca1dc44c3a826e987d1ea9f5b4", "interface": "public", "region_id": "RegionOne", "url": "http://10.200.134.218:8780", "region": "RegionOne"}], "id": "5c4974e041d34241bc7edf17f8ce07ae", "type": "placement", "name": "placement"}, {"endpoints": [{"id": "3c105203c90845d0a523f34cf6bc037b", "interface": "public", "region_id": "RegionOne", "url": "http://10.200.134.218:8000/v1", "region": "RegionOne"}, {"id": "cf77bee702da43d68aee3863d4fa68f0", "interface": "internal", "region_id": "RegionOne", "url": "http://172.29.236.100:8000/v1", "region": "RegionOne"}, {"id": "deda0fe9872d472e8ad04bf9cf65caab", "interface": "admin", "region_id": "RegionOne", "url": " http://172.29.236.100:8000/v1", "region": "RegionOne"}], "id": "675d604be05245e38156198a2e0c955c", "type": "cloudformation", "name": "heat-cfn"}, {"endpoints": [{"id": "0f358e9c8a9e4d4aa87ba5827c5612a7", "interface": "public", "region_id": "RegionOne", "url": " http://10.200.134.218:9696", "region": "RegionOne"}, {"id": "e0fda98441e442ad84ad9638b97fb5a9", "interface": "admin", "region_id": "RegionOne", "url": "http://172.29.236.100:9696", "region": "RegionOne"}, {"id": "f63223fe921a44e48fffaa90a22619b2", "interface": "internal", "region_id": "RegionOne", "url": "http://172.29.236.100:9696", "region": "RegionOne"}], "id": "679d6c52473b4b87867b0839238a2533", "type": "network", "name": "neutron"}, {"endpoints": [{"id": "04618143b8764565bd1f292c481ec9fc", "interface": "internal", "region_id": "RegionOne", "url": "http://172.29.236.100:9292", "region": "RegionOne"}, {"id": "131339c1c9564d0d9f0cfdf6311c2893", "interface": "admin", "region_id": "RegionOne", "url": "http://172.29.236.100:9292", "region": "RegionOne"}, {"id": "f0725b46e74549d1b3d58efaa46dbf02", "interface": "public", "region_id": "RegionOne", "url": "http://10.200.134.218:9292", "region": "RegionOne"}], "id": "df050da4381c4209968693e4aca92da5", "type": "image", "name": "glance"}, {"endpoints": [{"id": "7cb5429849d741238e31f929132b224d", "interface": "admin", "region_id": "RegionOne", "url": "http://172.29.236.100:8774/v2.1", "region": "RegionOne"}, {"id": "ab640e3d4ccf4d66832b0d2d38f30be9", "interface": "internal", "region_id": "RegionOne", "url": " http://172.29.236.100:8774/v2.1", "region": "RegionOne"}, {"id": "d707d5092628423397cb02a46cb1deca", "interface": "public", "region_id": "RegionOne", "url": "http://10.200.134.218:8774/v2.1", "region": "RegionOne"}], "id": "e807659ac4f74b78805b0f9e605081f0", "type": "compute", "name": "nova"}, {"endpoints": [{"id": "152f11cd02de47069bb7fee11954395d", "interface": "public", "region_id": "RegionOne", "url": " http://10.200.134.218:8776/v3/0e75229392c54a398ab302a8e43aebe6", "region": "RegionOne"}, {"id": "71b96d9f9b994d72bf21c10810a532f9", "interface": "admin", "region_id": "RegionOne", "url": " http://172.29.236.100:8776/v3/0e75229392c54a398ab302a8e43aebe6", "region": "RegionOne"}, {"id": "935b1c8e4da547ca891334fe476291b6", "interface": "internal", "region_id": "RegionOne", "url": " http://172.29.236.100:8776/v3/0e75229392c54a398ab302a8e43aebe6", "region": "RegionOne"}], "id": "ff62f9bcded14444bbb4f1e1cdcaf60b", "type": "volumev3", "name": "cinderv3"}]}} run(Namespace(all_projects=False, columns=[], deleted=False, fit_width=False, formatter='table', hidden=False, limit=None, long=False, marker=None, max_width=0, nested=False, noindent=False, print_empty=False, properties=None, quote_mode='nonnumeric', short=False, sort=None, sort_columns=[], sort_direction=None, tag_mode=None, tags=None)) take_action(Namespace(all_projects=False, columns=[], deleted=False, fit_width=False, formatter='table', hidden=False, limit=None, long=False, marker=None, max_width=0, nested=False, noindent=False, print_empty=False, properties=None, quote_mode='nonnumeric', short=False, sort=None, sort_columns=[], sort_direction=None, tag_mode=None, tags=None)) Instantiating orchestration client: <class 'heatclient.v1.client.Client'> REQ: curl -g -i -X GET http://10.200.134.218:8004/v1/0e75229392c54a398ab302a8e43aebe6/stacks? -H "Accept: application/json" -H "Content-Type: application/json" -H "User-Agent: python-heatclient" -H "X-Auth-Token: {SHA256}a0ae405fe8fdb29acbcc65b1ce4feb9a304448592d6a8ae982955e903f45f3c0" -H "X-Region-Name: RegionOne" Starting new HTTP connection (1): 10.200.134.218:8004 http://10.200.134.218:8004 "GET /v1/0e75229392c54a398ab302a8e43aebe6/stacks HTTP/1.1" 503 None RESP: [503] Cache-Control: no-cache Connection: close Content-Type: text/html RESP BODY: Omitted, Content-Type is set to text/html. Only application/json responses have their bodies logged. ERROR: b'<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n' Traceback (most recent call last): File "/usr/local/lib/python3.6/site-packages/cliff/app.py", line 401, in run_subcommand result = cmd.run(parsed_args) File "/usr/local/lib/python3.6/site-packages/osc_lib/command/command.py", line 39, in run return super(Command, self).run(parsed_args) File "/usr/local/lib/python3.6/site-packages/cliff/display.py", line 115, in run column_names, data = self.take_action(parsed_args) File "/usr/local/lib/python3.6/site-packages/heatclient/osc/v1/stack.py", line 577, in take_action return _list(client, args=parsed_args) File "/usr/local/lib/python3.6/site-packages/heatclient/osc/v1/stack.py", line 691, in _list data = list(data) File "/usr/local/lib/python3.6/site-packages/heatclient/v1/stacks.py", line 136, in paginate stacks = self._list(url, 'stacks') File "/usr/local/lib/python3.6/site-packages/heatclient/common/base.py", line 114, in _list body = self.client.get(url).json() File "/usr/local/lib/python3.6/site-packages/keystoneauth1/adapter.py", line 395, in get return self.request(url, 'GET', **kwargs) File "/usr/local/lib/python3.6/site-packages/heatclient/common/http.py", line 323, in request raise exc.from_response(resp) heatclient.exc.HTTPServiceUnavailable: ERROR: b'<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n' clean_up ListStack: ERROR: b'<html><body><h1>503 Service Unavailable</h1>\nNo server is available to handle this request.\n</body></html>\n' END return value: 1 Warm Regards, Premkumar Subramaniyan Technical staff M: +91 9940743669 *CRN Top 10 Coolest Edge Computing Startups of 2020 <https://www.crn.com/slide-shows/networking/the-10-coolest-edge-computing-st…>*

5 11

[ironic] Announcing deprecation of the iSCSI deploy interface
by Dmitry Tantsur 04 May '21

04 May '21

Hi all, Following up to the previous mailing list [1] and virtual meetup [2] discussions, I would like to announce the plans to deprecate the 'iscsi' deploy interface. This is the updated plan discussed on the virtual meetup: 1) In the Victoria cycle (i.e. right now): - Fill in the detected feature gaps [3]. - Switch off the iscsi deploy interface by default. - Change [agent]image_dowload_source to HTTP by default. - Give the direct deploy a higher priority, so that it's used by default unless disabled. - Mark it as deprecated in the code (causing warnings when enabled). - Release a major version of ironic to highlight the defaults changes. 2) In the W cycle: - Keep the iscsi deploy deprecated. - Listen to operators' feedback. 3) In the X cycle - Remove the iscsi deploy completely from ironic and IPA. - Remove support code from ironic-lib with a major version bump. Please let us know if you have any questions or concerns. Dmitry [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016681.h… [2] https://etherpad.opendev.org/p/Ironic-Victoria-midcycle [3] https://storyboard.openstack.org/#!/story/2008075 -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

1 1

[release] Meeting Time Poll
by Herve Beraud 03 May '21

03 May '21

Hello We have a few regular attendees of the Release Management meeting who have conflicts with the current meeting time. As a result, we would like to find a new time to hold the meeting. I've created a Doodle poll[1] for everyone to give their input on times. It's mostly limited to times that reasonably overlap the working day in the US and Europe since that's where most of our attendees are located. If you attend the Release Management meeting, please fill out the poll so we can hopefully find a time that works better for everyone. For the sake of organization and to allow everyone to schedule his agenda accordingly, the poll will be closed on April 5th. On that date, I will announce the time of this meeting and the date on which it will take effect. Thanks! [1] https://doodle.com/poll/ip6tg4fvznz7p3qx -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 5

[barbican][oslo][nova][glance][cinder] cursive library status
by Brian Rosmaita 03 May '21

03 May '21

Hello Barbican team, Apologies for not including barbican in the previous thread on this topic: http://lists.openstack.org/pipermail/openstack-discuss/2020-December/019430… The situation is that cursive is used by Nova, Glance, and Cinder and we'd like to move it out of the 'x' namespace into openstack governance. The question is then what team would oversee it. It seems like a good fit for Oslo, and the Oslo team seems OK with that, but since barbican-core is currently included in cursive-core, it make sense to give the Barbican team first dibs. From the consuming teams' side, I don't think we have a preference as long as it's clear who we need to bother about approvals if a bugfix is posted for review. Thus my ask is that the Barbican team indicate whether they'd like to move cursive to the 'openstack' namespace under their governance, or whether they'd prefer Oslo to oversee the library. Thank you! brian

5 5

[Diversity] Diversity & Inclusion WG Meeting reminder
by Amy Marrich 01 May '21

01 May '21

The Diversity & Inclusion WG invites members of all OSF projects to our meeting Monday May 3rd, at 17:00 UTC in the #openinfra-diversity channel. The agenda can be found at https://etherpad.openstack.org/p/diversity -wg-agenda. Please feel free to add any topics you wish to discuss at the meeting. Thanks, Amy (spotz)

1 0

[interop] Weekly meeting is at Fridays 4:00pm UTC
by Kanevsky, Arkady 30 Apr '21

30 Apr '21

Every Fridays at 16:00 UTC <16:00%20UTC > on https://meetpad.opendev.org/Interop-WG-weekly-meeting Current Meeting Logs on etherpad - https://etherpad.opendev.org/p/interop Wiki is updated with the latest info. https://wiki.openstack.org/wiki/Governance/InteropWG Arkady Kanevsky, Ph.D. SP Chief Technologist & DE Dell Technologies office of CTO Dell Inc. One Dell Way, MS PS2-91 Round Rock, TX 78682, USA Phone: 512 7204955

1 0

[tripleo] removing myself from tripleo-core
by Emilien Macchi 29 Apr '21

29 Apr '21

Hi people, If you didn't notice, I am not working on TripleO anymore (as a developer, but still a heavy user) and therefore my amount of contribution and awareness in the project makes me think I shouldn't be considered a maintainer anymore. I'll remove myself from tripleo-core in Gerrit. I just want to let you know that I'm not far, I'm still on IRC and sometimes participate in the chat. I can also provide support for the crappy code that I wrote (Alex made me do it most of the time). However don't expect me to be heavily involved like it used to be the case. I just want to say that I already miss a lot working on TripleO and in OpenStack in general. The Community, the maturity of the project and all that we built is something that can't be compared to anything else out there. My focus is now "Kubernetes (OpenShift) on top of OpenStack", heavily consuming what OpenStack has to offer and connecting the two worlds. It's a lot of fun and a lot of new things to learn! But I'm sure OpenStack won't go too far away from my plate, so let's keep in touch. Take care, -- Emilien Macchi

2 1

[glance][ceph] Openstack Wallaby and Ceph Pacific- ERROR cinder.scheduler.flows.create_volume
by Tecnologia Charne.Net 29 Apr '21

29 Apr '21

Hello! I'm working with Openstack Wallaby (1 controller, 2 compute nodes) connected to Ceph Pacific cluster in a devel environment. With Openstack Victoria and Ceph Pacific (before last friday update) everything was running like a charm. Then, I upgraded Openstack to Wallaby and Ceph to version 16.2.1. (Because of auth_allow_insecure_global_id_reclaim I had to upgrade many clients... but that's another story...) After upgrade, when I try to create a volume from image, openstack volume create --image f1df058d-be99-4401-82d9-4af9410744bc debian10_volume1 --size 5 with "show_image_direct_url = True", I get "No valid backend" in /var/log/cinder/cinder-scheduler.log 2021-04-26 20:35:24.957 41348 ERROR cinder.scheduler.flows.create_volume [req-651937e5-148f-409c-8296-33f200892e48 c048e887df994f9cb978554008556546 f02ae99c34cf44fd8ab3b1fd1b3be964 - - -] Failed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No valid backend was found. Exceeded max scheduling attempts 3 for resource 56fbb645-2c34-477d-9a59-beec78f4fd3f: cinder.exception.NoValidBackend: No valid backend was found. Exceeded max scheduling attempts 3 for resource 56fbb645-2c34-477d-9a59-beec78f4fd3f and 2021-04-26 20:35:24.968 41347 ERROR oslo_messaging.rpc.server [req-651937e5-148f-409c-8296-33f200892e48 c048e887df994f9cb978554008556546 f02ae99c34cf44fd8ab3b1fd 1b3be964 - - -] Exception during message handling: rbd.InvalidArgument: [errno 22] RBD invalid argument (error creating clone) in /var/log/cinder/cinder-volume.log If I disable "show_image_direct_url = False", volume creation from image works fine. I have spent the last four days googling and reading lots of docs, old and new ones, unlucly... Does anybody have a clue, (please)? Thanks in advance! Javier.-

2 2

[Cinder] Problem in iSCSI Portal
by Taha Adel 29 Apr '21

29 Apr '21

Hello, The situation is, I have one storage node that has cinder-volume service up and running on top of it and has a dedicated physical NIC for storage traffic. I have set the following configuration in /etc/cinder/cinder.conf file at the storage node: volume_driver = cinder.volume.drivers.lvm.LVMVolumeDriver volume_group = cinder-volumes target_protocol = iscsi target_helper = lioadm iscsi_ip_address = 10.0.102.11 (different than the management ip) The service is able to create the volume and attach it as a backstore for iSCSI, but it can't create a Portal for iSCSI service. Should I create the portal entry by myself? or is there a mistake I have made in the config file? Thanks in advance

2 1

Fwd: cinder + Unity
by Rajat Dhasmana 29 Apr '21

29 Apr '21

Hi Albert, On Mon, Apr 19, 2021 at 11:45 PM Albert Shih <Albert.Shih(a)obspm.fr> wrote: > Hi everyone, > > I'm a total newbie with openstack, currently I'm trying to put a POC with a > Unity storage element, 4 computes, and few servers (cinder, keystone, > glance, neutron, nova, placement and horizon). > > I think my keystone, glance, placement are working (at least they past the > test). > > Currently I'm trying to make cinder working with my Unity (480), the > objectif are to use iSCSI. > > Here the configuration of my /etc/cinder/cinder.conf > > [DEFAULT] > rootwrap_config = /etc/cinder/rootwrap.conf > api_paste_confg = /etc/cinder/api-paste.ini > iscsi_helper = tgtadm > volume_name_template = volume-%s > volume_group = cinder-volumes > verbose = True > auth_strategy = keystone > state_path = /var/lib/cinder > lock_path = /var/lock/cinder > volumes_dir = /var/lib/cinder/volumes > enabled_backends = unity > transport_url = rabbit://openstack:XXXXXX@amqp-cloud.private.FQDN > /openstack > auth_strategy = keystone > debug = True > verbose = True > > [database] > connection = mysql+pymysql://cinder:XXXXXXX@mariadb-cloud.private.FQDN > /cinder > > [keystone_authtoken] > www_authenticate_uri = http://keystone.private.FQDN:5000/v3 > auth_url = http://keystone.private.FQDN:5000 > identity_uri = http://keystone.private.FQDN:5000 > memcached_servers = memcached-cloud.private.FQDN:11211 > auth_type = password > project_domain_name = default > user_domain_name = default > project_name = service > username = cinder > password = XXXXXX > > [oslo_concurrency] > lock_path = /var/lib/cinder/tmp > > [unity] > # Storage protocol > storage_protocol = iSCSI > # Unisphere IP > san_ip = onering-remote.FQDN > # Unisphere username and password > san_login = openstack > san_password = "XXXXX" > # Volume driver name > volume_driver = cinder.volume.drivers.dell_emc.unity.Driver > # backend's name > volume_backend_name = Unitiy_ISCSI > This might be something to look at with the wrong spelling causing mismatch. > unity_io_ports = *_enp1s0 > unity_storage_pool_names = onering > > When I'm trying to create a storage through a > > openstack volume create volumetest --type thick_volume_type --size 100 > > I don't even see (with tcpdump) the cinder server trying to connect to > > onering-remote.FQDN > > Inside my /var/log/cinder/cinder-scheduler.log I have > > 2021-04-19 18:06:56.805 21315 INFO cinder.scheduler.base_filter > [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee > b1d58ebae6b84f7586ad63b94203d7ae - - -] Filtering removed all hosts for the > request with volume ID '06e5f07d-766f-4d07-b3bf-6153a2cf6abd'. Filter > results: AvailabilityZoneFilter: (start: 0, end: 0), CapacityFilter: > (start: 0, end: 0), CapabilitiesFilter: (start: 0, end: 0) > This log mentions that no host is valid to pass the 3 filters in the scheduler. > 2021-04-19 18:06:56.806 21315 WARNING cinder.scheduler.filter_scheduler > [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee > b1d58ebae6b84f7586ad63b94203d7ae - - -] No weighed backend found for volume > with properties: {'id': '5f16fc1f-76ff-41ee-8927-56925cf7b00f', 'name': > 'thick_volume_type', 'description': None, 'is_public': True, 'projects': > [], 'extra_specs': {'provisioning:type': 'thick', > 'thick_provisioning_support': 'True'}, 'qos_specs_id': None, 'created_at': > '2021-04-19T15:07:09.000000', 'updated_at': None, 'deleted_at': None, > 'deleted': False} > 2021-04-19 18:06:56.806 21315 INFO cinder.message.api > [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee > b1d58ebae6b84f7586ad63b94203d7ae - - -] Creating message record for > request_id = req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 > 2021-04-19 18:06:56.811 21315 ERROR cinder.scheduler.flows.create_volume > [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee > b1d58ebae6b84f7586ad63b94203d7ae - - -] Failed to run task > cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: > No valid backend was found. No weighed backends available: > cinder.exception.NoValidBackend: No valid backend was found. No weighed > backends available > > > It seem (for me) cinder don't try to use unity.... > > The cinder-volume service is responsible for communicating with the backend and this create request fails on scheduler only, hence no sign of it. > Any help ? > > Regards > > Looking at the scheduler logs, there are a few things you can check: 1) execute ``cinder-manage service list`` command and check the status of cinder-volume service if it's active or not. If it shows an X sign then check in cinder-volume logs for any startup failure. 2) Check the volume type properties and see if ``volume_backend_name`` is set to the right value i.e. Unitiy_ISCSI (which looks suspicious because the spelling is wrong and there might be a mismatch somewhere) Also it's good to mention the openstack version you're using since the code changes every cycle and it's hard to track the issues with every release. Thanks and regards Rajat Dhasmana > > -- > Albert SHIH > Observatoire de Paris > Heure local/Local time: > Mon Apr 19 08:01:37 PM CEST 2021 > >

3 2

[release] Release countdown for week R-23, April 26-30
by Herve Beraud 29 Apr '21

29 Apr '21

Welcome back to the release countdown emails! These will be sent at major points in the Xena development cycle, which should conclude with a final release on 06 October, 2021. Development Focus ----------------- At this stage in the release cycle, focus should be on planning the Xena development cycle, assessing Xena community goals and approving Xena specs. General Information ------------------- Xena is a 25 weeks development cycle. In case you haven't seen it yet, please take a look over the schedule for this release: https://releases.openstack.org/xena/schedule.html By default, the team PTL is responsible for handling the release cycle and approving release requests. This task can (and probably should) be delegated to release liaisons. Now is a good time to review release liaison information for your team and make sure it is up to date: https://opendev.org/openstack/releases/src/branch/master/data/release_liais… By default, all your team deliverables from the Xena release are continued in Xena with a similar release model. Upcoming Deadlines & Dates -------------------------- Xena-1 milestone: 27 May, 2021 Hervé Beraud and the Release Management team -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

[oslo] Team meetings updates for Xena
by Herve Beraud 29 Apr '21

29 Apr '21

Hi Osloers, Please notice the following updates concerning the team's meetings during Xena. Meetings are now scheduled the first and the third Monday of each month. No longer weekly meetings. Meeting's courtesy ping list will be updated soon for Xena. If you want to continue to be called at the beginning of each meeting please add you nick here: https://wiki.openstack.org/wiki/Meetings/Oslo#Xena_Courtesy_Ping Thanks for your attention. -- Hervé Beraud Senior Software Engineer at Red Hat irc: hberaud https://github.com/4383/ https://twitter.com/4383hberaud -----BEGIN PGP SIGNATURE----- wsFcBAABCAAQBQJb4AwCCRAHwXRBNkGNegAALSkQAHrotwCiL3VMwDR0vcja10Q+ Kf31yCutl5bAlS7tOKpPQ9XN4oC0ZSThyNNFVrg8ail0SczHXsC4rOrsPblgGRN+ RQLoCm2eO1AkB0ubCYLaq0XqSaO+Uk81QxAPkyPCEGT6SRxXr2lhADK0T86kBnMP F8RvGolu3EFjlqCVgeOZaR51PqwUlEhZXZuuNKrWZXg/oRiY4811GmnvzmUhgK5G 5+f8mUg74hfjDbR2VhjTeaLKp0PhskjOIKY3vqHXofLuaqFDD+WrAy/NgDGvN22g glGfj472T3xyHnUzM8ILgAGSghfzZF5Skj2qEeci9cB6K3Hm3osj+PbvfsXE/7Kw m/xtm+FjnaywZEv54uCmVIzQsRIm1qJscu20Qw6Q0UiPpDFqD7O6tWSRKdX11UTZ hwVQTMh9AKQDBEh2W9nnFi9kzSSNu4OQ1dRMcYHWfd9BEkccezxHwUM4Xyov5Fe0 qnbfzTB1tYkjU78loMWFaLa00ftSxP/DtQ//iYVyfVNfcCwfDszXLOqlkvGmY1/Y F1ON0ONekDZkGJsDoS6QdiUSn8RZ2mHArGEWMV00EV5DCIbCXRvywXV43ckx8Z+3 B8qUJhBqJ8RS2F+vTs3DTaXqcktgJ4UkhYC2c1gImcPRyGrK9VY0sCT+1iA+wp/O v6rDpkeNksZ9fFSyoY2o =ECSj -----END PGP SIGNATURE-----

1 0

An compute service hang issue
by Yingji Sun 29 Apr '21

29 Apr '21

Buddies, Have you ever met such issue that the nova-compute service looks hanging there and not able to boot instance? When creating an instance, we can only see logs like below and there is NOT any information. 2021-04-23 02:39:00.252 1 DEBUG nova.compute.manager [req-a2ed90b6-792f-48e1-ba7f-e1e35d9537c2 373cb863547407cf3b99034b3b66395e76c137b40f905e7a61e25b1f97df4f3e 1ee7955a2eaf4c86bcc3e650f2a8e2a7 - fc86abb50a684911a30f7955d386a3ea fc86abb50a684911a30f7955d386a3ea] [instance: e0e77edc-99b4-473e-b318-8e6f04428cda] Starting instance... _do_build_and_run_instance /usr/lib/python3.7/site-packages/nova/compute/manager.py:2202^[[00m 2021-04-23 03:03:04.927 1 DEBUG oslo_concurrency.lockutils [req-50659582-ad9b-4c17-bbb2-254d5e1141f9 373cb863547407cf3b99034b3b66395e76c137b40f905e7a61e25b1f97df4f3e 1ee7955a2eaf4c86bcc3e650f2a8e2a7 - fc86abb50a684911a30f7955d386a3ea fc86abb50a684911a30f7955d386a3ea] Lock "a3619b50-3704-4f3e-b908-d525a41756eb" acquired by "nova.compute.manager.ComputeManager.build_and_run_instance.<locals>._locked_do_build_and_run_instance" :: waited 0.001s inner /usr/lib/python3.7/site-packages/oslo_concurrency/lockutils.py:327 There is NO other messages, including the periodically tasks. If I sent a request to create another instance, I can only see another _do_build_and_run_instance log. 2021-04-23 03:03:05.061 1 DEBUG nova.compute.manager [req-50659582-ad9b-4c17-bbb2-254d5e1141f9 373cb863547407cf3b99034b3b66395e76c137b40f905e7a61e25b1f97df4f3e 1ee7955a2eaf4c86bcc3e650f2a8e2a7 - fc86abb50a684911a30f7955d386a3ea fc86abb50a684911a30f7955d386a3ea] [instance: a3619b50-3704-4f3e-b908-d525a41756eb] Starting instance... _do_build_and_run_instance /usr/lib/python3.7/site-packages/nova/compute/manager.py:2202^[[00m 2021-04-23 03:32:44.718 1 DEBUG oslo_concurrency.lockutils [req-c7857cb3-02ae-4c7b-92d7-b2ec178c1b13 373cb863547407cf3b99034b3b66395e76c137b40f905e7a61e25b1f97df4f3e 1ee7955a2eaf4c86bcc3e650f2a8e2a7 - fc86abb50a684911a30f7955d386a3ea fc86abb50a684911a30f7955d386a3ea] Lock "3b07a6eb-12bb-4d19-9302-25ea3e746944" acquired by "nova.compute.manager.ComputeManager.build_and_run_instance.<locals>._locked_do_build_and_run_instance" :: waited 0.001s inner /usr/lib/python3.7/site-packages/oslo_concurrency/lockutils.py:327 I am sure the compute service is still running as I can see the heart-beat time changes correctly. From the rabbitmq message, It looks the code goes here nova/compute/manager.py def _build_and_run_instance(self, context, instance, image, injected_files, admin_password, requested_networks, security_groups, block_device_mapping, node, limits, filter_properties, request_spec=None): image_name = image.get('name') self._notify_about_instance_usage(context, instance, 'create.start', extra_usage_info={'image_name': image_name}) compute_utils.notify_about_instance_create( context, instance, self.host, phase=fields.NotificationPhase.START, bdms=block_device_mapping) as I can see a message with "event_type": "compute.instance.create.start" INFO:root:Body: {'oslo.version': '2.0', 'oslo.message': '{"message_id": "0ef11509-7a65-46b8-ac7e-ed6482fc527d", "publisher_id": "compute.compute01", "event_type": "compute.instance.create.start", "priority": "INFO", "payload": {"tenant_id": "1ee7955a2eaf4c86bcc3e650f2a8e2a7", "user_id": "373cb863547407cf3b99034b3b66395e76c137b40f905e7a61e25b1f97df4f3e", "instance_id": "3b07a6eb-12bb-4d19-9302-25ea3e746944", "display_name": "yingji-06", "reservation_id": "r-f8iphdcf", "hostname": "yingji-06", "instance_type": "m1.tiny", "instance_type_id": 15, "instance_flavor_id": "4d5644e1-c561-4b6c-952c-f4dd93c87948", "architecture": null, "memory_mb": 512, "disk_gb": 1, "vcpus": 1, "root_gb": 1, "ephemeral_gb": 0, "host": null, "node": null, "availability_zone": "nova", "cell_name": "", "created_at": "2021-04-23 03:32:39+00:00", "terminated_at": "", "deleted_at": "", "launched_at": "", "image_ref_url": "https://192.168.111.160:9292//images/303a325f-048 This issue is not always reproducible and restarting the compute service can work around this. Could you please give any suggestion on how to resolve this issue or how I can investigate ? Yingji.

2 5

[neutron] Drivers meeting agenda - 30.04.2021
by Slawek Kaplonski 29 Apr '21

29 Apr '21

Hi, Agenda for our tomorrow's drivers meeting is available at https://wiki.openstack.org/wiki/ Meetings/NeutronDrivers[1] We have 1 RFE to discuss: - https://bugs.launchpad.net/neutron/+bug/1922716[2] It was already discussed briefly during the PTG last week but let's get it official during the drivers meeting :) Have a great day and see You all tomorrow. -- Slawek Kaplonski Principal Software Engineer Red Hat -------- [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers [2] https://bugs.launchpad.net/neutron/+bug/1922716

1 0

[wallaby][trove] MySQL 8.0 Support
by Ammad Syed 29 Apr '21

29 Apr '21

Hi, I am using trove wallaby release and trying to create a database instance with MySQL 8.0. I have created a mysql datastore version 8.0. The instance deployment failed with ERROR. Digging it further in guest agent logs, it is found that MySQL 8.0 container is not booting up and getting failed with below errors. 2021-04-28 09:35:27+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 8.0.24-1debian10 started. 2021-04-28T09:35:28.496216Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 8.0.24) starting as process 1 2021-04-28T09:35:28.574978Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2021-04-28T09:35:29.318823Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended. mysqld: Table 'mysql.plugin' doesn't exist 2021-04-28T09:35:29.566920Z 0 [ERROR] [MY-010735] [Server] Could not open the mysql.plugin table. Please perform the MySQL upgrade procedure. 2021-04-28T09:35:29.568058Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables 2021-04-28T09:35:29.569103Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables 2021-04-28T09:35:29.570029Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables 2021-04-28T09:35:29.570986Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables 2021-04-28T09:35:29.571894Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables 2021-04-28T09:35:29.572835Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables 2021-04-28T09:35:29.573939Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables 2021-04-28T09:35:29.576559Z 0 [System] [MY-011323] [Server] X Plugin ready for connections. Bind-address: '::' port: 33060, socket: /var/run/mysqld/mysqlx.sock 2021-04-28T09:35:29.665764Z 0 [Warning] [MY-010015] [Repl] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened. 2021-04-28T09:35:29.705075Z 0 [Warning] [MY-010015] [Repl] Gtid table is not ready to be used. Table 'mysql.gtid_executed' cannot be opened. 2021-04-28T09:35:29.718900Z 0 [Warning] [MY-010068] [Server] CA certificate ca.pem is self signed. 2021-04-28T09:35:29.719698Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel. 2021-04-28T09:35:29.724833Z 0 [Warning] [MY-010441] [Server] Failed to open optimizer cost constant tables 2021-04-28T09:35:29.725997Z 0 [ERROR] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-001146 - Table 'mysql.component' doesn't exist 2021-04-28T09:35:29.726837Z 0 [Warning] [MY-013129] [Server] A message intended for a client cannot be sent there as no client-session is attached. Therefore, we're sending the information to the error-log instead: MY-003543 - The mysql.component table is missing or has an incorrect definition. 2021-04-28T09:35:29.727818Z 0 [ERROR] [MY-000067] [Server] unknown variable 'ignore-db-dir=lost+found'. 2021-04-28T09:35:29.729297Z 0 [ERROR] [MY-010119] [Server] Aborting 2021-04-28T09:35:31.237003Z 0 [System] [MY-010910] [Server] /usr/sbin/mysqld: Shutdown complete (mysqld 8.0.24) MySQL Community Server - GPL. get_actual_db_status /opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/mysql_common/service.py:80 2021-04-28 09:35:31.266 930 DEBUG trove.guestagent.datastore.service [-] Waiting for DB status to change from running to healthy. wait_for_status /opt/guest-agent-venv/lib/python3.6/site-packages/trove/guestagent/datastore/service.py:319 I think this requires some changes in config.template of mysql. -- Regards, Syed Ammad Ali

1 1

[tc][all][ Xena Virtual PTG Summary
by Ghanshyam Mann 29 Apr '21

29 Apr '21

Hello Everyone, I am summarizing the Technical Committee discussion that happened in the Xena cycle PTG. Pop Up Team Check-In --------------------------- Currently, we have two pop-up teams 1. policy-popup 2. Encryption, as per checks, both are active, and we will continue on both teams in the Xena cycle. policy pop-up team almost served its purpose and ready to be converted as community-wide goal as next step which can happen in Y cycle. Community-wide goals Check-In --------------------------------------- *In the Wallaby cycle, we selected two community-wide goals. In PTG we checked the progress and any blocker. 1. Migrate RBAC Policy Format from JSON to YAML[1] This is almost completed, only heat and few patches in openstack-ansible are pending. Tracking etherpad[2]. Action Items: Finish the pending patches to merge. Assignee: gmann 2. Migrate from oslo.rootwrap to oslo.privsep[3] ralonsoh could not join this session due to conflict with neutron sessions, but this needs more work and will continue in Xena cycle too. Action Items: Continue this work in Xena cycle Assignee: ralonsoh * Along with the above goals, we checked a few previous cycle goals pending work also, and the below two are pretty simple and important to complete. We will spend some time finishing these in Xena cycle. 1. offline pdf doc: https://storyboard.openstack.org/#!/story/list?tags=pdf-doc-enabled Assignee: gmann 2. Contributor guide: https://storyboard.openstack.org/#!/story/2007236 Assignee: gmann, diablo_rojo *Y cycle goal selection. As per the community-wide goal schedule[4], we need to start the goal selection for the Y cycle. We have two TC members volunteer to drive this work. Assignee: ricolin, diablo_rojo TC tag advertising and encourage project adoption. -------------------------------------------------------------- We discussed the TC tags[5] adoption and if it is worth continuing it or who actually gets benefit from these. It is not so clear if they are being checked by users or anyone. Projects are adopted in production by their stability and feature, not just by tag. We decided to review each tag for its usefulness and cleanup. Based on what left, we can make a decision on whether to continue the tag concept or not. Action Items: Review each tag for its usefulness and cleanup Assignee: yoctozepto, jungleboyj Discussion on moving OpenStack to a yearly release cycle -------------------------------------------------------------------- This topic has been discussed before also and it was live-streamed on youtube too, which you can watch[6]. Discussion is about if the current 6-month release cycle is fine/fast for consumers to adopt the releases/upgrade etc. There were both side arguments about moving OpenStack release to 1-year cycle and it was not so clear if that actually solve the upgrade/consuming feature or not. Also, there are few points on developer perspective and being a long 1-year release can slow down the community activeness and developer time for upstream work. But there were more important points also which I did not summarize here but you to watch the youtube video for details. In summary, there is no consensus on this and we gathered some of the action items to continue this get feedback or educating about upgrade operation guides& best practices. Action Items: * Reach out to the Project team + operators about feedback via ML. * Encourage "Operation Docs and Tooling" SIG to add upgrades and operational education guideline Assignee: I forgot to ask the volunteer for this, please let me know if anyone would like to help with this. Wallaby Retrospective --------------------------- Below is what we discussed in the previous cycle retrospective * TC is more productive with the weekly meetings which helped to speed up the review and discussions. * Happy to see TC engagement on the gate and infra stuff. We will be continuing this as our weekly meeting agenda too. Thanks to dansmith to initiate this * Did not promote election well. We discussed this in detail as a separate topic, I am writing the summary for this in the below section. * We need more interaction with project/SIG(and also popups?:) ) team. Ditto, I am writing the summary for this in the below section. * Doing great with settling projects to DPL and also we have zero projects left behind as leaderless. * Landed the TC stance on SDK/OSC Patch * Started SIG audit too in terms of health checks which is good to keep SIG list active and maintained Thanks to ricolin and diablo_rojo. * Thanks to mnaser and diablo_rojo for serving as Chair/Vice-chair and running the show in a great way. Getting projects to broadcast out/mentor ++ ---------------------------------------------------- This topic is about encouraging projects to broadcast out successes, wins, and possibly get people in projects to engage in some public speaking of their work, why it is important to them, the change they see it making in the world, team values, what does the team find important. We discussed the various way to achieve that and some of part is about marketing the things. There is openinfra live tv which broadcast the live sessions every Thursday, take more help from the foundation or reach out to local user groups. Apart from marketing stuff, TC will definitely encourage projects to start talking about the more and more technical stuff in public speaking. Action Items: * TC to reachout to board/foundation to provide an exact platform for broadcast these, existing or any new platform * TC to document this as best practice to do by projects in project team guide. Assignee: spotz, belmoreira How do we not break cross-vendor drivers? --------------------------------------------------- This discussion was about cross-vendor drivers. In Ironic, w recent change to redfish drivers was found to break in one case on another vendor. Even current stable policy state in appropriate-fixes section[7]on taking the best decision on backport fixes. Projects can take decisions as per the project and user's best interest which will help everyone. We talked about the stable policy process in the next topic which is going to help projects in such cases. Stable core team process ----------------------------- We have talked about this in shanghai PTG also but did not proceed with any resolution. We are facing a few issues with the stable backport merges. The stable maintenance team is not so active as it used to be. There is a delay in adding more core in stable project groups or merging the backports. Elod mentioned that right now that generally when people have questions, they refer them to the policy documents and make a decision. We definitely want to fix the current issues and the good news is that we agreed to do few changes on stable policy like let the project core team manages the project side stable team and also policy they would like to define as per the project's use case. Action Items: * Add a resolution and modify stable policy doc for the below changes: ** Let the project team manage the project's stable core team, Global stable maintenance core team is continuing on general advice and help. ** Projects are allowed to define any addition or own policy on top of general stable policy guidelines. Assignee: jungleboyj, mnaser/gmann (gmann to check if mnaser is ok with this item) Stable EM to EOL transition --------------------------------- There are 9 stable branches currently (will be 8 soon after ocata moves to EOL) including EM or maintained stable. Discussion is about the maintenance effort for these many stable branches. how we can handle the supporting team load for EM branches like QA, infra etc. Many projects gate on EM stable branches is broken. QA team or elod end up spending lot of time during py2 drop time on EM branch even we still fix those. But in future, we might not have that much volume on EM branch maintenance. With that, we did not conclude on reducing the number of EM branch and continue as it is. But as 'unmaintained phase is not so clear and not real phase branch transition to, we agreed to remove this phase and let EM branch directly move to EOL state based on their current lifecycle or maintenance. Action Items: Remove the "Unmaintained" phase Assignee: gmann Next, we talked about the TC process & workflow things. Meeting time check ------------------------ As we have two new TC members, we checked on the current meeting time. The current time Thursday 15 UTC is ok for all TC members and we will continue that. Office Hour continuation ------------------------------ TC office hours are still inactive and we discussed if we want to continue on these or we can remove especially when we have weekly meetings. The consensus on this is to continue with the one office hour which is in Asia TZ. Action Items: Keep one office hour Assignee: gmann Charter revision for election vacant seat ----------------------------------------------- This was the first time in the TC election that we had one vacant seat. There was discussion on reducing the TC seats (this requires the charter change but we did not have full TC members to do the charter change) or doing a special election which we went with a special election. This is something we tool as an action item to make our charter handle this situation in future if occur. We also talked about how we can engage AUC in election or voting and decided to add a way for them to be extra ATC. Action Items: * Charter change to write the process to handle these vacant seat situations and how to make a charter change in absence of complete TC or so. * Document the process for adding SIG+project contributors, AUC as extra ATC. Assignee: dansmith How we can improve our election promotion ----------------------------------------------------- In past couple of elections, we have noticed that many members miss the nomination deadline also fewer members step up for the leadership role. We discussed few ways to improve the election promotion but there is no concrete things we agreed on Another but important thing we discussed is how to add more members to the election official team. Every time it's fungi or diablo_rojo helping in front. We decided that we will have two TC members volunteer for every cycle election official or encourage community members to be part of this wG. Action Items: Make a process to ask two TC volunteers for an election official in addition to existing election officials. Assignee: spotz, diablo_rojo Project Health checks -------------------------- We tried a few ways in past to improve the interaction between TC and the project side. TC liaison is our current way to check project health and interaction but that is not so active or helpful. Rico suggested trying some automatic way to check the contribution stats. But apart from that we did not decide any conclusion on that and will continue this discussion in the TC meeting. Action Items: * automate the process to check the health in term of contribution/review/release/gate * Continue this topic in the weekly meetings. Assignee: belmoreira, ricolin Mechanism to define the TC track-able targets per cycle (or redefine the TC tracker) ------------------------------------------------------------------------------------------------- This is to try a mechanism for TC working items per cycle. We agreed to track these in etherpad and check status in our weekly meeting. Action Items: Create the etherpad for Xena cycle tracker: https://etherpad.opendev.org/p/tc-xena-tracker Assignee: gmann [1] https://governance.openstack.org/tc/goals/selected/wallaby/migrate-policy-f… [2] https://etherpad.opendev.org/p/migrate-policy-format-from-json-to-yaml [3] https://governance.openstack.org/tc/goals/selected/wallaby/migrate-to-privs… [4] https://governance.openstack.org/tc/goals/#goal-selection-schedule [5] https://governance.openstack.org/tc/reference/tags/index.html [6] https://www.youtube.com/watch?v=s4HOyAdQx8A [7] https://docs.openstack.org/project-team-guide/stable-branches.html#appropri… -gmann

1 0

[all][tc] Technical Committee next weekly meeting on April 29th at 1500 UTC
by Ghanshyam Mann 29 Apr '21

29 Apr '21

Hello Everyone, Below is the agenda for tomorrow's TC meeting schedule on April 29th at 1500 UTC in #openstack-tc IRC channel. == Agenda for tomorrow's TC meeting == * Roll call * Follow up on past action items * PTG ** https://etherpad.opendev.org/p/tc-xena-ptg * TC tracker for Xena cycle (gmann) ** https://etherpad.opendev.org/p/tc-xena-tracker * Gate performance and heavy job configs (dansmith) ** http://paste.openstack.org/show/jD6kAP9tHk7PZr2nhv8h/ * TC's context, name, and documenting formal responsibilities (TheJulia) * Open Reviews ** https://review.opendev.org/q/project:openstack/governance+is:open -gmann

1 0

Xena PTG Policy Summary
by Lance Bragstad 28 Apr '21

28 Apr '21

Hey all, Last week we spent a lot of time discussing RBAC, where everything stands, and where we need to go to offer a consistent experience for operators and users. We kept track of all the sessions in a single etherpad, which also served as a place for daily summaries [0]. There is a lot of information in there, but we started working through the action items and correlating them to bugs or opening new bugs. Hopefully this helps us track progress through Xena. One of the biggest outcomes from last week was the discussion about how system users should interact with project-owned resources. For context, administrators have always been able to do things for project users because they both have project-scoped tokens. That's no longer going to be the case as services adopt system-scope. We came up with an interesting way to solve the problem and we compared it to other approaches. This all starts at about line 136 in the etherpad [0]. Ultimately, we think it will be the least invasive approach, we have a specification up for review [1], and a PoC in flight [2]. Please look over the summary and links to any actionables for your project. We can use this thread to discuss any questions if you have them. Thanks again for all the dedication and focus on policy last week. I know the discussions aren't easy and it's a tough problem to work through, but landing something this big across OpenStack services will be a huge win for operators and users. Lance [0] https://etherpad.opendev.org/p/policy-popup-xena-ptg [1] https://review.opendev.org/c/openstack/keystone-specs/+/787640 [2] https://review.opendev.org/c/openstack/keystonemiddleware/+/787822

1 0

[all][requirements] sqlalchemy 1.4.x release/upgrade
by Matthew Thode 28 Apr '21

28 Apr '21

Looks like a new release of sqlalchemy is upon us and is breaking tests in openstack (1.4.11 for now). Please test against https://review.opendev.org/788339 to get your project working against the newest version. currently failing are cinder ironic keystone masakari neutron and nova cross gates Thanks, -- Matthew Thode

6 8

[openstack-ansible-modules] Openstack Ansible collections PTG session summary
by Sagi Shnaidman 28 Apr '21

28 Apr '21

Hi, all Highlights from Openstack Ansible collection/modules PTG session[1] In the last cycle we had 68 commits, 3 released versions, 5 new contributors, 14 solved issues. The roadmap for next cycle: All modules in Xena should convert SDK output to a dictionary to match last SDK changes. CI tasks: 1. Automatic release jobs 2. Docs generation and publishing jobs - docs.openstack.org and readthedocs will be evaluated. 3. Gating jobs for projects starting to use the collections, like TripleO. Bugtracker - to evaluate Launchpad for bugs and issues submission. We continue to convert modules to use a standard OpenstackModule class. Features coverage for Openstack Ansible modules would help us to see how good we cover the current functionality. It would be useful to have roles in collection which will run specific and common tasks, which can be used by OPs easily. (Like Terraform "modules" concept) For fetching Openstack SDK logs during the tasks execution we may have a specific role or/and OpenstackModule class modifications. Ansible-test is used now for sanity testing only, we'll evaluate it for integration tests next cycle. Thanks [1] https://etherpad.opendev.org/p/xena-ptg-os-ansible-collections -- Best regards Sagi Shnaidman

1 0

[openstack-ansible][osa][PTG] OpenStack-Ansible Xena PTG summary
by Dmitriy Rabotyagov 28 Apr '21

28 Apr '21

Hi everyone! First of all I would like to thank everyone for attendance. We have discussed a lot of topics both regarding things that we need to merge before releasing Wallaby (we are trailing behind and may release in up to 3 month after official release) and regarding plans for the Xena. First comes list of things that we agreed to land for W in descending priority: 1. ansible-role-pki. Gerrit topic [1] 2. Centos8-Stream. Gerrit topic [2] 3. Move neutron-server to standalone group in env.d 4. Debian Bullseye. We're currently blocked with infra [3] 5. Senlin tempest test [4] 6. Fix broken roles 7. Implement send_service_user_token and service_token_roles_required Also we agreed to keep ansible-base 2.11.* release for Wallaby, and not switch to the ansible-core yet. List of descisions that were taken for the Xena release: 1. Deprecate Ubuntu Bionic at the beggining of X cycle 2. Deprecate Centos-8 (classic) at the beginning of X cycle 3. Switch MariaDB balancing frontend from HAproxy to MaxScale 4. Drop Nginx for the Keystone and use Apache is all scenarios as most unified solution. 5. Add option to roles to configure systemd timers for cleaning up soft-deleted records in DB 6. Create operating systems support table to clear out possible upgrade paths between releases 7. Replace dashes with underscores in group names and dynamic inventory and stop ignoring TRANSFORM_INVALID_GROUP_CHARS. 8. Adding ability to enable prometheus support for MariaDB and HAproxy 9. Revise possibility to support deployments on top of arm64 10. Look into creation common roles for Ansible OpenStack collection. At least write a blueprint/spec regarding scope of these roles. 11. Deploy ARA on localhost for OSA logging, configured by variables [1] https://review.opendev.org/q/topic:%22osa%252Fpki%22+(status:open) [2] https://review.opendev.org/q/topic:%22osa-stream%22+(status:open) [3] https://review.opendev.org/q/topic:%22debian_bullseye%22+(status:open) [4] https://review.opendev.org/c/openstack/openstack-ansible-os_senlin/+/754045 -- Kind Regards, Dmitriy Rabotyagov

3 4

internet not working in instance
by cloud learner 28 Apr '21

28 Apr '21

Hi All, Have installed rocky on centos 7 with 2 node controller and compute, used linuxbridge as mentioned in the document used self service network. My question is, as we have to create the br-ex and attach it to eth when we use OVS, so as I am using linuxbridge there is need to create the bridge. If there are any doc kindly suggest. Thanks

1 0

[wallaby][neutron] Neuton Server Upgrade
by Ammad Syed 28 Apr '21

28 Apr '21

Hi, I have upgraded neutron server from victoria to wallaby. Everytime I restart neutron server, I see below errors in neutron-server.log. Can you guys please advise on it. 2021-04-28 06:34:12.144 1767 INFO ovsdbapp.backend.ovs_idl.vlog [req-cc4f309f-1851-47cd-bab1-de0445964d56 - - - - -] tcp:172.16.30.51:6641: connecting... 2021-04-28 06:34:12.145 1767 INFO ovsdbapp.backend.ovs_idl.vlog [req-cc4f309f-1851-47cd-bab1-de0445964d56 - - - - -] tcp:172.16.30.51:6641: connected 2021-04-28 06:34:12.214 1770 INFO neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.impl_idl_ovn [-] Getting OvsdbNbOvnIdl for MaintenanceWorker with retry 2021-04-28 06:34:12.238 1770 INFO ovsdbapp.backend.ovs_idl.vlog [-] tcp: 172.16.30.51:6641: connecting... 2021-04-28 06:34:12.238 1770 INFO ovsdbapp.backend.ovs_idl.vlog [-] tcp: 172.16.30.51:6641: connected 2021-04-28 06:34:12.248 1767 ERROR ovsdbapp.event [-] Unexpected exception in notify_loop: AttributeError: 'NoneType' object has no attribute 'db_find_rows' 2021-04-28 06:34:12.248 1767 ERROR ovsdbapp.event Traceback (most recent call last): 2021-04-28 06:34:12.248 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/ovsdbapp/event.py", line 159, in notify_loop 2021-04-28 06:34:12.248 1767 ERROR ovsdbapp.event match.run(event, row, updates) 2021-04-28 06:34:12.248 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovsdb_monitor.py", line 443, in run 2021-04-28 06:34:12.248 1767 ERROR ovsdbapp.event self.driver.delete_mac_binding_entries(row.external_ip) 2021-04-28 06:34:12.248 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 1058, in delete_mac_binding_entries 2021-04-28 06:34:12.248 1767 ERROR ovsdbapp.event mac_binds = self._sb_ovn.db_find_rows( 2021-04-28 06:34:12.248 1767 ERROR ovsdbapp.event AttributeError: 'NoneType' object has no attribute 'db_find_rows' 2021-04-28 06:34:12.248 1767 ERROR ovsdbapp.event 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event [-] Unexpected exception in notify_loop: AttributeError: 'NoneType' object has no attribute 'db_find_rows' 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event Traceback (most recent call last): 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/ovsdbapp/event.py", line 159, in notify_loop 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event match.run(event, row, updates) 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovsdb_monitor.py", line 443, in run 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event self.driver.delete_mac_binding_entries(row.external_ip) 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 1058, in delete_mac_binding_entries 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event mac_binds = self._sb_ovn.db_find_rows( 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event AttributeError: 'NoneType' object has no attribute 'db_find_rows' 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event [-] Unexpected exception in notify_loop: AttributeError: 'NoneType' object has no attribute 'db_find_rows' 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event Traceback (most recent call last): 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/ovsdbapp/event.py", line 159, in notify_loop 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event match.run(event, row, updates) 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovsdb_monitor.py", line 443, in run 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event self.driver.delete_mac_binding_entries(row.external_ip) 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 1058, in delete_mac_binding_entries 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event mac_binds = self._sb_ovn.db_find_rows( 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event AttributeError: 'NoneType' object has no attribute 'db_find_rows' 2021-04-28 06:34:12.250 1767 ERROR ovsdbapp.event 2021-04-28 06:34:12.251 1767 ERROR ovsdbapp.event [-] Unexpected exception in notify_loop: AttributeError: 'NoneType' object has no attribute 'db_find_rows' 2021-04-28 06:34:12.251 1767 ERROR ovsdbapp.event Traceback (most recent call last): 2021-04-28 06:34:12.251 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/ovsdbapp/event.py", line 159, in notify_loop 2021-04-28 06:34:12.251 1767 ERROR ovsdbapp.event match.run(event, row, updates) 2021-04-28 06:34:12.251 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/ovsdb/ovsdb_monitor.py", line 443, in run 2021-04-28 06:34:12.251 1767 ERROR ovsdbapp.event self.driver.delete_mac_binding_entries(row.external_ip) 2021-04-28 06:34:12.251 1767 ERROR ovsdbapp.event File "/usr/lib/python3/dist-packages/neutron/plugins/ml2/drivers/ovn/mech_driver/mech_driver.py", line 1058, in delete_mac_binding_entries 2021-04-28 06:34:12.251 1767 ERROR ovsdbapp.event mac_binds = self._sb_ovn.db_find_rows( 2021-04-28 06:34:12.251 1767 ERROR ovsdbapp.event AttributeError: 'NoneType' object has no attribute 'db_find_rows' 2021-04-28 06:34:12.251 1767 ERROR ovsdbapp.event 2021-04-28 06:34:12.251 1767 INFO neutron.plugins.ml2.drivers.ovn.mech_driver.mech_driver [-] OVN reports status down for port: 3d040d1d-c3d5-49da-9103-8ab4f9a8ab01 2021-04-28 06:34:12.252 1767 INFO neutron.plugins.ml2.drivers.ovn.mech_driver.ovsdb.impl_idl_ovn [req-cc4f309f-1851-47cd-bab1-de0445964d56 - - - - -] Getting OvsdbSbOvnIdl for WorkerService with retry Secondly after upgrade, I can only see upgraded network agents in openstack network agent list. The other agents that are on victoria release are not showing up. Need your help. -- Regards, Syed Ammad Ali

1 0

[victoria][ha]Rabbitmq HA configuration in victoria
by Shalabh Goel 28 Apr '21

28 Apr '21

Hi, I have been trying to configure HA for rabbitmq service for my Openstack installation. I found varying options on the Internet. I am facing some issues with rabbitmq with HAproxy. Option 1. I want to know if victoria supports the following configuration directive for openstack services. rabbit_hosts=rabbit1:5672,rabbit2:5672,rabbit3:5672 as told in this guide https://docs.openstack.org/ha-guide/control-plane-stateful.html Option 2. Can we configure as follows: transport_url = rabbit://RABBIT_USER:RABBIT_PASS@rabbit1:5672,RABBIT_USER:RABBIT_PASS@rabbit2:5672,RABBIT_USER:RABBIT_PASS@rabbit3:5672 Option 3. I have been using this configuration in haproxy listen rabbitmq_cluster_openstack bind controllers:5672 mode tcp balance roundrobin server controller1 controller1:5672 check inter 2000 rise 2 fall 5 server controller2 controller2:5672 backup check inter 2000 rise 2 fall 5 I am getting the following error in my log files for all the services. 2021-04-28 09:59:05.857 129188 INFO oslo.messaging._drivers.impl_rabbit [-] [bbf40d1a-e095-47ad-8629-931af485d4cf] Reconnected to AMQP server on controllers:5672 via [amqp] client with port 44818. I have set transport_url as follows: > transport_url = rabbit://openstack:rabbit123@controllers:5672 > The error goes away if I change host to controller1 or controller. Please suggest which is the recommended one of the 3. Thanks in advance -- Shalabh Goel

2 1

cyborg launchpad suppport
by Alex Song (宋文平) 28 Apr '21

28 Apr '21

Hi, We change to use launchpad to track cyborg bugs and features, with this patch merged: https://review.opendev.org/c/openstack/project-config/+/787306. But we cannot count on the website: https://www.stackalytics.io/ Please help us with this problem. Thanks.

3 4

[Interop][PTG] highlights from Interop PTG
by Kanevsky, Arkady 27 Apr '21

27 Apr '21

Fellow stackers, Thank you for successful Xena PTG. The PTG agenda and notes are at https://etherpad.opendev.org/p/april2021-ptg-interop-refstack Highlights: 1. Ghanshayam and Goutham are now co-chair of Interop along with Arkady 2. Superuser article for Interop is in progress highlighting major changes to Interop program including Rfestack transitioning to Python3, support of refstack of add-on projects, and adding share file system as add-on program. 3. Working on updated to Interop processes, and specifically no need for Board to approve new guidelines, only process changes. * See https://review.opendev.org/c/osf/interop/+/787646 * Discuss updates to all wiki pages starting from https://wiki.openstack.org/wiki/Governance/InteropWG - expect changes in Xena cycle 4. Agreed on how we will list add-on Logo to marketplace listing 5. Working on how to handle in automated matter in refstack admin privileges for setting up for tempest user testing, Manila in particular. 6. Starting discussion on how to handle microiservice versions of APIs. 7. Interlocks with all projects under interop guidelines, except Swift and Keystone. 8. Discussed several possible add-on projects Happy to provide more details. Thanks, Arkady Kanevsky, Ph.D. SP Chief Technologist & DE Dell Technologies office of CTO Dell Inc. One Dell Way, MS PS2-91 Round Rock, TX 78682, USA Phone: 512 7204955

1 0

OS X install openstackclient 10.15.7
by Michael STFC 27 Apr '21

27 Apr '21

Hi I know this is a forum for openstack but I have some issues with OS X and upgrading or reinstalling openstackclient. Any advise welcome. —— Regards, Michael Tint System Administrator

2 2

OS X install openstackclient 10.15.7
by Michael STFC 27 Apr '21

27 Apr '21

Hi I know this is a forum for openstack but I have some issues with OS X and upgrading or reinstalling openstackclient. Any advise welcome. Regards, Michael Tint System Administrator

1 0

[venus][ptg]Venus vPTG Summary April 2021
by Liye Pang(逄立业) 27 Apr '21

27 Apr '21

Hi all, Thanks for all your participation! We've conducted the first meeting of venus last week and it is successful. Here's the summary of the topics we have discussed: *Progress in the past six months: - Develop devstack-based deployment for venus - Add log retrieval of modules such as vitrage - Develop the configuration, based on which you can retrieve the chain log of the call *Next step: - Develop alarm task code to set threshold for the number of error logs of different modules at different times, and provides alarm services and notification services - The configuration, analysis and alarm of Venus will be integrated into horizon in the form of plugin. - Develop a deployment method based on kolla-ansible - (discuss)Summarize the log specifications of some typical scenarios and develop them to venus - Evaluate whether to collect event data (considering usage, pressure, etc.We will continue to discuss with the telemetry project team) *Promblem: - Many projects's log records are not standardized, so they can only support full-text retrieval, not multi-dimensional analysis Full discussion (PTG etherpad): [1] https://etherpad.opendev.org/p/venus-xena-ptg Introduction of venus: [2] https://youtu.be/mE2MoEx3awM

4 4

[Vitrage] Cannot delete old entities on graph
by Adam Tomas 27 Apr '21

27 Apr '21

Hi, I’ve deployed Kolla-Ansible (Victoria) and after using it for some time I have errors from Vitrage service: 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init [-] Got Exception for event {'vitrage_entity_type': 'consistency', 'vitrage_datasource_action': 'update', 'vitrage_sample_date': '2021-03-18T13:30:19Z', 'vitrage_event_type': 'delete_entity', 'vitrage_id': 'a19330f1-49c1-4a97-9787-c80b645f51a6', 'id': '93c1df77-dbb5-4ba7-9b7d-16fad97169f1', 'vitrage_type': 'cinder.volume', 'vitrage_category': 'RESOURCE', 'is_real_vitrage_id': True}: KeyError: 'vitrage_is_placeholder' 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init Traceback (most recent call last): 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init File "/var/lib/kolla/venv/lib/python3.8/site-packages/vitrage/entity_graph/graph_init.py", line 146, in do_work 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init return do_work_func(event) 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init File "/var/lib/kolla/venv/lib/python3.8/site-packages/vitrage/entity_graph/graph_init.py", line 111, in process_event 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init self.processor.process_event(event) 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init File "/var/lib/kolla/venv/lib/python3.8/site-packages/vitrage/entity_graph/processor/processor.py", line 63, in process_event 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init self.actions[entity.action](entity.vertex, entity.neighbors) 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init File "/var/lib/kolla/venv/lib/python3.8/site-packages/vitrage/entity_graph/processor/processor.py", line 149, in delete_entity 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init PUtils.delete_placeholder_vertex(self.entity_graph, vertex) 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init File "/var/lib/kolla/venv/lib/python3.8/site-packages/vitrage/entity_graph/processor/processor_utils.py", line 68, in delete_placeholder_vertex 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init if not vertex[VProps.VITRAGE_IS_PLACEHOLDER]: 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init File "/var/lib/kolla/venv/lib/python3.8/site-packages/vitrage/graph/driver/elements.py", line 24, in __getitem__ 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init return self.properties[key] 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init KeyError: 'vitrage_is_placeholder' 2021-03-18 13:30:19.873 7 ERROR vitrage.entity_graph.graph_init As I can see in Horizon, there are some old volumes , which in Cinder database have proper (DELETED/DETACHED) status, but they’re still visible on Entity Graph, and as in error message above - cannot be deleted by vitrage-graph. How to delete such entities? Best regards, Adam Tomas

2 7

[tacker] IRC meeting cancelled on 4th May
by Yasufumi Ogawa 27 Apr '21

27 Apr '21

Hi tacker team, It's a holiday season next week in Japan, and most of us are not going to join the next IRC meeting. We will cancel the meeting on 4th May. Cheers, Yasufumi

1 0

[Multi-arch SIG][sig][PTG] PTG Summary. Next meeting: May, 11.
by Rico Lin 27 Apr '21

27 Apr '21

Dear all Before we starts, just like to notify that we're not running meeting this week, but will run meeting at May, 11. So please join and provide topics if you got any: https://etherpad.opendev.org/p/Multi-Arch-agenda As we just have our PTG meeting last week, and I thank everyone who joins our PTG session. Here are some summaries from PTG: - Success to run full tempest tests on Arm64 env. What's next? - ML: http://lists.openstack.org/pipermail/openstack-discuss/2021-April/021600.ht… - Job patch: https://review.opendev.org/c/openstack/devstack/+/708317 - Job status: https://zuul.openstack.org/builds?job_name=devstack-platform-arm64+ - actions: - propose to add swift arm64 UT job: Swift is one of services directly touch file system or basic storage services. - pushing forward for integrating Ceph with current CI job to test more similar to user's environment - tunning volume backup/restore on the current job: - we might try to use POSIX as volume backup backend to testing performance issue. - ricolin and kevinz will take action to run tests locally for debugging - Also will try to switch to OSUOSL environment to check what kind of result we will face. - propose a periodic task for current CI job (once landed): as current job performance is not suitable for gating every patch set, I believe it will make sense to at least have a periodic job running. After performance issue is fixed, we can consider adding gating job or post-merge job. - We should also consider having multi-node job to test cross node. - SIG report (https://www.openstack.org/multi-arch-sig-report) - As general agreement that we definitely will generate report out to keep update the community with works related to multi-arch supports. Also hope to get use cases for share around. - We found some error in SIG report, but they are fixed now. - SIG video meeting - We discuss about the chances to run a video meeting. Once we have more material collected or topics ready. - Check libvirt 7 and cpu stuff - as libvirt 7 released this year, we should check if behavior changes: - There was code added for CPU features on migration - Need to check does 'cpu_mode' different than host-passthrough work now Please reference our PTG etherpad for more detailed discussion: https://etherpad.opendev.org/p/xena-ptg-multi-arch-sig *Rico Lin* OIF Board director, OpenStack TC, Multi-arch SIG chair, Heat PTL, Senior Software Engineer@EasyStack

1 0

Masakari meeting on 2021-05-04 *cancelled*
by Radosław Piliszek 27 Apr '21

27 Apr '21

Dears, We are cancelling the Masakari meeting on 2021-05-04 as there are holidays in China. We will meet again on 2021-05-11. -yoctozepto

1 0

[neutron]Really need some help in network aspect
by Rey 27 Apr '21

27 Apr '21

Hello, I'm not sure this is the right place, but I want to try whether if can I get any useful help. I stuck in some network problem for couple of days, and the problem I listed in https://github.com/projectcalico/calico/issues/4563 In short, the environment is kubernetes over openstack vm, and calico is kubernetes network componenet. However, the container to container network is very very slowly than host to host. So, I confused in questions: 1. Does kernel support double virturalization network? Like container network in vm 2. Is there any way to dig more? Sincerely, Yuan

1 0

[cyborg][ptg]Cyborg vPTG Summary April 2021
by Wang, Xin-ran 27 Apr '21

27 Apr '21

Hi all, Please ignore my previous message, it is sent to wrong person. Sorry about this. Thanks for all your participation! We've conducted a successful meeting last week. Here is the aggregated summary from Cyborg vPTG discussion. Please check it out and feel free to feedback any concerns you might have. We did a retrospective of Wallaby release, including: * We supports more operations supported for a VM with accelerator attached. * We introduced new drivers for Intel x710 NIC and Inspur's NVMe SSD Card. * We implemented a new configuration file allowing more flexible device configuration. Topic discussion: Here's some major discussion and conclusion of Cyborg vPTG. For more details, please refer to the etherpad[1]. * More nova operation supporting: - We prioritized the tasks: 1. suspend/resume. 2. cold migration. 3. live migration. * vGPU support: - We reached an internal agreement on whole workflow which can be apply as a generic framework for mdev device. * API enhancement: Some of the following items requires a new micro-version. - Add refresh policy check for all APIs. - Add device profile update API. - Add ARQ query by multiple instances API. - Add disable/enable device API, this one requires a spec first. - Enhance device profile show API with more information. * Cleanup issue: - This issue comes from the case where one compute node shutdown accidently, and the accelerator records in placement and cyborg DB remains as the orphaned resources. We agreed to implement a mechanism to clean up the orphaned resources, this one also need a spec. [1] https://etherpad.opendev.org/p/cyborg-xena-ptg Thanks, Xin-Ran Wang

2 2

[sdk]: compute service create_server method, how to create multiple servers
by dmeng 27 Apr '21

27 Apr '21

Hello there, Hope this email finds you well. We are currently using the openstacksdk for developing our product, and have a question about the openstacksdk compute service create_server() method. We are wondering if the "max_count" and "min_count" are supported by openstackskd for creating multiple servers at once. I tried both the max_count and the min_count, and they both only create one server for me, but I'd like to create multiple servers at once. The code I'm using is like the following: conn = connection.Connection( session=sess, region_name=None, compute_api_version='2') nova = conn.compute nova.create_server( name='sdk-test-create', image_id=image_id, flavor_id=flavor_id, key_name=my_key_name, networks=[{"uuid": network_id}], security_groups=[{'name':security_group_name}], min_count=3, ) The above code will create one server "sdk-test-create", but I'm assuming it should create three. Wondering did I miss anything, or if we have any other option to archive this? Thanks for your help and have a great day! Catherine

2 1

[Watcher] Datasource plugins?
by Jing Geng (BLOOMBERG/ 120 PARK) 27 Apr '21

27 Apr '21

Hi There, Currently Watcher supports many kinds of plugins, including actions, cluster data model collector, goals... In fact, it seems everything has plugins except for datasources (metrics). I wonder if there is any reason that so far Watcher doesn't provide plugins for datasources? Another question is, if I'd like to build plugin infrastructure for datasources, which means changing this DataSourceBase class so it extends loadable.Loadable and abc.ABCMeta, like other base classes for plugins, will this be supported by the community? I hope this idea will be supported, especially when there have already been several projects that tried to make datasources more flexible (Formal Datasource Interface, File based Metric Map, Grafana proxy datasource...). It seems to me that we should just provide plugins for datasources so Watcher can work with any metric system that has been deployed. If I missed something and it isn't a good idea, please also let me know why. Looking forward to contributing to the community! Regards, Jing Geng

1 0

[telemetry][ptg] Summary of the discussed topics
by Matthias Runge 26 Apr '21

26 Apr '21

Hi there, last week, we had two days of PTG sessions for telemetry. There were a couple of topics discussed, and here's the summary. - the CI situation for telemetry is not very satisfying. There are a couple of repositories interacting with each other. telemetry gates have been blocked for over a month on the external dependency gnocchi. - We talked about the use (or not using) storyboard for the case of tracking bugs etc. for telemetry. It is/was not very user friendly to report bugs. - for the future, we'll go back and use launchpad for tracking bugs etc. - We had a collab session with the folks from venus, talked about what they are doing, and if there is a room for collaboration. - we also decided to drop panko from OpenStack. A separate mail will follow. Best, Matthias

1 0

RE: [kolla] VM build fails after Train-Ussuri upgrade
by Braden, Albert 26 Apr '21

26 Apr '21

Can anyone help with this upgrade issue? From: Braden, Albert Sent: Monday, April 19, 2021 8:20 AM To: openstack-discuss(a)lists.openstack.org Subject: [kolla] VM build fails after Train-Ussuri upgrade I upgraded my Train test cluster to Ussuri following these instructions: OpenStack Docs: Operating Kolla<https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html#u…> The upgrade completed successfully with no failures, and the existing VMs are fine, but new VM build fails with rados.Rados.connect\nrados.PermissionDeniedError: Ubuntu Pastebin<https://paste.ubuntu.com/p/MJhzgjYbW8/> I'm running external ceph so I looked at this document: OpenStack Docs: External Ceph<https://docs.openstack.org/kolla-ansible/latest/reference/storage/external-…> It says that I need the following in /etc/kolla/config/glance/ceph.conf: auth_cluster_required = cephx auth_service_required = cephx auth_client_required = cephx I didn't have that, so I added it and then redeployed, but still can't build VMs. I tried adding the same to all copies of ceph.conf and redeployed again, but that didn't help. Does anything else need to change in my ceph config when upgrading from Train to Ussuri? I see some cryptic talk about ceph in the release notes but it's not obvious what I'm being asked to change: OpenStack Docs: Ussuri Series Release Notes<https://docs.openstack.org/releasenotes/kolla-ansible/ussuri.html#relnotes-…> I read the bug that it refers to: Bug #1904062 "external ceph cinder volume config breaks volumes ..." : Bugs : kolla-ansible (launchpad.net)<https://bugs.launchpad.net/kolla-ansible/+bug/1904062> But I already have "backend_host=rbd:volumes" so I don't think I'm hitting that. Also I read these sections but I don't see anything obvious here that needs to be changed: * For cinder (cinder-volume and cinder-backup), glance-api and manila keyrings behavior has changed and Kolla Ansible deployment will not copy those keys using wildcards (ceph.*), instead will use newly introduced variables. Your environment may render unusable after an upgrade if your keys in /etc/kolla/config do not match default values for introduced variables. * The default behavior for generating the cinder.conf template has changed. An rbd-1 section will be generated when external Ceph functionality is used, i.e. cinder_backend_ceph is set to true. Previously it was only included when Kolla Ansible internal Ceph deployment mechanism was used. * The rbd section of nova.conf for nova-compute is now generated when nova_backend is set to "rbd". Previously it was only generated when both enable_ceph was "yes" and nova_backend was set to "rbd". My ceph keys have the default name and are in the default locations. I have cinder_backend_ceph: "yes". I don't have a nova_backend setting but I have nova_backend_ceph: "yes" I added nova_backend: "rbd" and redeployed and now I get a different error: rados.Rados.connect\nrados.ObjectNotFound Ubuntu Pastebin<https://paste.ubuntu.com/p/2kdKCW7npw/> I apologize for the nonsense below. I have not been able to stop it from being attached to my external emails. E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

2 2

[TripleO] Xena PTG session summaries
by Marios Andreou 26 Apr '21

26 Apr '21

Hello folks, I sent out some stats and links on our PTG meetup with http://lists.openstack.org/pipermail/openstack-discuss/2021-April/021999.ht… already, but, as a couple of different people asked me about it, I took the time to write a summary for each session today. Of course you can find all etherpad links and recordings via https://etherpad.opendev.org/p/tripleo-ptg-xena (which seems to be down right now but I have backups if it isn't resolved by tomorrow I can try sharing that content somewhere else). Below is a (very) concise summary of the main points in each session and I hope that is useful to someone (especially since it took far longer than I expected ;)). Please reply here (or ping privately if you prefer) for any glaring omissions or obvious issues that should be revised (I originally intended to put this in an etherpad for easier collaboration but as I wrote above, etherpad.opendev.org seems down right now at least for me). regards, marios MON: * https://etherpad.opendev.org/p/tripleo-ptg-retrospective Retrospective of the Wallaby cycle - there are some community and team level 'headlines' on the main items worked on during this cycle on the etherpad. Some identified ideas for improvement include targeting another older branch for end-of-life likely Queens, improving upstream documentation especially removal of stale content, and creating a tag in Launchpad for teams so we can more easily identify which squad is currently assigned. * Topic: Plan/Swift removal update Presentation link: https://drive.google.com/file/d/1igOW4XuAbU55Tat73DwLqO4UGZu8MiNi/view?usp=… An update of the work completed in the W allay cycle to remove the Swift service and the deployment plan (which is no longer used as part of our deployments) from the undercloud. From wallaby onward by default there is no undercloud Swift. There may be a revision of the spec https://opendev.org/openstack/tripleo-specs/commit/e83d8aba3a950da83a33c23b… as the original plan didn't explicitly consider removal of the deployment plan. * https://etherpad.opendev.org/p/tripleo-ephemeral-heat Update on the ephemeral heat work (i.e. no permanent heat process on the undercloud). There has been very strong progress made in this cycle and there are still some outstanding patches https://review.opendev.org/q/topic:%22ephemeral-heat%22+(status:open) to be merged. Goal is to make this the default in Xena deployments and backport to Wallaby as optional. Besides the main feature, some related planned work includes consolidation of the python-tripleoclient "overcloud deploy" and "tripleo deploy" (eg standalone) commands. Note that this work depends on the tripleo-network-v2 work (next session below). * https://etherpad.opendev.org/p/tripleo-network-v2 Update on the network ports v2 work (moving network port creation out of the heat stack) https://opendev.org/openstack/tripleo-specs/src/branch/master/specs/wallaby… - again good progress on this during Wallaby but there is still some ongoing work there https://review.opendev.org/q/topic:%2522network-data-v2%2522+(status:open) . The goal for Xena is to make this the default (i.e. no node/networking config in deploy-steps-playbook.yaml). One main area of work for X in this topic is integration of the baremetal network config in the overcloud deployment (i.e. allow a single command). * https://etherpad.opendev.org/p/tripleo-ceph-xena Update from the ceph team about the main work items completed in Wallaby including the tripleo-ceph-client and tripleo-ceph in place of ceph-ansible for RBD ( https://specs.openstack.org/openstack/tripleo-specs/specs/wallaby/tripleo-c… and https://specs.openstack.org/openstack/tripleo-specs/specs/wallaby/tripleo-c… ). The main work planned for Xena is to continue trying to achieve feature parity with ceph-ansible - including resolving cephadm blockers, , Ganesha & https://specs.openstack.org/openstack/tripleo-specs/specs/wallaby/tripleo-c… . One major consideration is how to move ceph creation/config outside of the heat stack - some parts such as pools, keyrings and haproxy config will have to remain as part of the tripleo deployment. Note that this work depends on the network ports v2 (previous session above). TUE: * https://etherpad.opendev.org/p/tripleo-xena-whole-disk-images A proposal to move to whole disk images instead of the current overcloud-full.qcow+overcloud-full.initrd+overcloud-full.vmlinuz. There were many compelling arguments made for the proposal including: with the overcloud-full.qcow2 partition image, as of centos 8.4 grub2 no longer supports UEFI boot, there will be much less for ironic-python-agent to do during deployment with a single disk image, there will be just one file to distribute (vs 3), we will no longer need to define and build a separate 'hardened' image (and also remove the related CI jobs). One of the main technical issues that needs to be addressed first is the grow partition for /var which is where we are storing containers and config for deployment. * https://etherpad.opendev.org/p/tripleo-xena-drop-healthchecks Proposal to drop the container health check since are using deployment resources but aren't providing value. There was no push back against this proposal and the details are being discussed in the newly posted spec @ https://review.opendev.org/c/openstack/tripleo-specs/+/787535. * https://etherpad.opendev.org/p/ci-tripleo-repos Proposal to consolidate the various ways and places that tripleo-ci is using to configure the repos in the CI jobs. There is a spec proposed @ https://review.opendev.org/c/openstack/tripleo-specs/+/772442 - some of the work here is split into sub items which are ongoing (tripleo-get-hash there https://review.opendev.org/c/openstack/tripleo-ci/+/784392) The main outstanding blocking item here is to agree on the common data format for the various personas upstream downstream and product that we need to support eg https://github.com/mwhahaha/rhos-bootstrap/blob/main/versions/centos.yaml vs https://review.opendev.org/c/openstack/tripleo-repos/+/785593/1/tripleo_rep… * openstack tempest skiplist https://docs.google.com/presentation/d/1aCiV35IYNhPV7SRmi4_A9vkIjZ89pwfC4Vv… Update on the tempest skiplist effort during Wallaby to consolidate the skipped Tempest tests in a central location with the ability to specify particular jobs and or branches for which specific skips will apply. * https://etherpad.opendev.org/p/tripleo-next One of the main items discussed here was the 'first principles' proposal at https://review.opendev.org/c/openstack/tripleo-specs/+/786980 - these are meant to guide us when discussing changes to our deployment tooling and architecture. The proposal will merge in Xena specs once we've reached consensus on the review. Another topic discussed in this session was an update on exploratory work to replace "heat & ansible" in our deployment tooling with 'something else' - some ongoing work here is at https://github.com/cloudnull/director & https://github.com/mwhahaha/task-core. More info and pointers (also discussed Kube/OCP with an operator to deploy tripleo) on the etherpad. WED: * https://etherpad.opendev.org/p/tripleo-xena-inventory-script This was a proposal to remove the "tripleo-ansible-inventory script" @ https://github.com/openstack/tripleo-common/blob/ccd990b58b6583dda3a0e0f341… and instead generate it from the deployment data (e.g. metalsmith or user data from deployed-server deployments). The consensus reached was that instead of removing it we should instead use it in a better way, for example make sure static inventories are generated and exported to known locations (especially for the ephemeral heat case) and re-used. * https://etherpad.opendev.org/p/vf-ui-output This was an update from the validations squad about the main items worked on during Wallaby (integrated the validation framework into the component CI pipelines, enabled the standalone job in upstream check/gate and increased adoption especially by the upgrades squad). Followed by discussions for planned Xena work, including changes in the UI/CLI (eg jq queries can be handled better and various other UI improvements more on the etherpad). Some of the other topics raised here were to make the validations themselves component aware (run all validations related to a given component) and discussion around the requirement for a molecule test on all validation additions (especially the example of mocking out OpenStack services like keystone); the compromise could be to instead use a standalone job for such cases. * https://etherpad.opendev.org/p/Validation-Framework-Next-Generation In this session the validations squad introduced ideas for the future direction of the validation framework. Some of the main proposals are to remove the validations repos - validations-common and validations-libs out of tripleo governance but still within openstack and establishing a new validations project (discussion but no clear consensus on this point), to re-merge the two repos into one consolidated validations repo and fixup the CLI (see previous session) - more items and other considerations on the etherpad. * https://etherpad.opendev.org/p/tripleo-frr-integration Update on Wallaby progress from the cross-squad team looking at FRR/BGP integration in the tripleo deployment (https://opendev.org/openstack/tripleo-specs/src/branch/master/specs/wallaby…) Some of the main items discussed for Xena work included how we might approximate some part of this feature in upstream CI (high resource requirements - downstream CI has 9 nodes) and backport considerations (no backport to upstream/train). * https://etherpad.opendev.org/p/update-upgrade-consolidation In this session the upgrades squad outlined their proposal for consolidation of the minor update and major upgrade workflows - without any blockers or objections coming out of the discussion. One of the main considerations was around how we can decouple the operating system updates/upgrades from the tripleo container upgrade - one action item is to de-containerize those containers that are tied to the kernel version (ABI) such as libvirt and openvswitch. THU: * https://etherpad.opendev.org/p/policy-popup-xena-ptg In this session the security squad gave an update on progress during Wallaby on the Role Based Access Control (RBAC) - many services have completed implementation (Keystone, Nova, Ironic - more on the etherpad). Then there was a discussion around potential integration points during the tripleo deployment, for example https://review.opendev.org/c/openstack/tripleo-heat-templates/+/781571/7/en… . One of the considerations was around how we can test this in CI (possibly the standalone job is a good fit) as well as the use of multiple clouds.yaml for project specific operations during the deployment (with the root clouds yaml having the system-admin profile). * https://etherpad.opendev.org/p/centos-stream-9-upstream In this session the CI squad lead a discussion around centos9 stream (possibly coming Apr/May) and what we should consider/prepare for with respect to upstream CI. Some of the main changes and discussion items included NetworkManager and firewalld replacing iptables, ansible version (2.11/2.12?/?). Mainly this effort is blocked on the actual 9-stream release and getting the relevant nodepool node. Another main discussion point here was whether we would support both stream-8 and stream-9 on particular branches - consensus here is that wallaby has both 8/9 and for X can have only 9 - but this is all dependent on when 9 becomes available with respect to when Xena is released. * https://etherpad.opendev.org/p/os-migrate This session was an update from the upgrades squad around the os-migrate tool ( https://github.com/os-migrate/os-migrate ) - which aims to 'copy' your openstack deployment and in particular the end-user workloads (i.e. user data, vms etc, but not the controlplane) onto new hardware, as an alternative to the in-place upgrade. More information and slides @ https://docs.google.com/presentation/d/1UYGOI89MBLHLpS89mPp0VK1yvTYtb2BamUL…

1 1

[TripleO] next irc meeting Tuesday Apr 27 @ 1400 UTC in #tripleo
by Marios Andreou 26 Apr '21

26 Apr '21

Reminder that the next TripleO irc meeting is: ** Tuesday 27 April at 1400 UTC in #tripleo ** ** https://wiki.openstack.org/wiki/Meetings/TripleO ** ** https://etherpad.opendev.org/p/tripleo-meeting-items ** Please add anything you want to highlight at https://etherpad.opendev.org/p/tripleo-meeting-items This can be recently completed things, ongoing review requests, blocking issues, or anything else tripleo you want to share. Our last meeting was on Mar 13 - you can find the logs there http://eavesdrop.openstack.org/meetings/tripleo/2021/tripleo.2021-04-13-14.… Hope you can make it on Tuesday, regards, marios

1 0

[Interop]: Interop Working Group Meeting
by Kanevsky, Arkady 26 Apr '21

26 Apr '21

1 0

RE: [Interop] Proposal to move weekly meeting 1 hour earlier
by Kanevsky, Arkady 26 Apr '21

26 Apr '21

Thanks Dmitry. You are correct it is for Interop WG not Ironic. Thanks for catching it. That is for Friday weekly Interop Meeting. Arkady From: Dmitry Tantsur <dtantsur(a)redhat.com> Sent: Friday, April 23, 2021 9:12 AM To: Kanevsky, Arkady Cc: openstack-discuss(a)lists.openstack.org Subject: Re: [Ironic] Proposal to move weekly meeting 1 hour earlier [EXTERNAL EMAIL] I suspect you wanted to use [interop] tag, not [ironic] :) On Fri, Apr 23, 2021 at 4:10 PM Kanevsky, Arkady <Arkady.Kanevsky(a)dell.com<mailto:Arkady.Kanevsky@dell.com>> wrote: Team, On today’s PTG Interop meeting we proposed to move weekly Friday meeting 1 hour earlier to 16:00 UTC. Please, respond if the proposed time will or not will work for you. Thanks, Arkady Kanevsky, Ph.D. SP Chief Technologist & DE Dell Technologies office of CTO Dell Inc. One Dell Way, MS PS2-91 Round Rock, TX 78682, USA Phone: 512 7204955 -- Red Hat GmbH, https://de.redhat.com/ [de.redhat.com]<https://urldefense.com/v3/__https:/de.redhat.com/__;!!LpKI!wCVrafnGLyCBhmrC…> , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

4 4

[TripleO] overcloud node introspect failed
by Vinesh N 26 Apr '21

26 Apr '21

hi, i am facing an issue while introspect the bare metal nodes, *error message* "*4bdd55bd-c4d9-4af0-b619-2e0b7b0107cf | 2021-04-22T01:41:32 | 2021-04-22T01:41:35 | Failed to set boot device to PXE: Failed to set boot device for node 4bdd55bd-c4d9-4af0-b619-2e0b7b0107cf: Client Error for url: http://10.0.1.202:6385/v1/nodes/4bdd55bd-c4d9-4af0-b619-2e0b7b0107cf/manage… <http://10.0.1.202:6385/v1/nodes/4bdd55bd-c4d9-4af0-b619-2e0b7b0107cf/manage…>, Node 4bdd55bd-c4d9-4af0-b619-2e0b7b0107cf is locked by host undercloud.localdomain, please retry after the current operation is completed*" *(undercloud) [stack@undercloud ~]$ cat /etc/*release* CentOS Linux release 8.3.2011 *ussuri version* *(undercloud) [stack@undercloud ~]$ openstack image list* /usr/lib/python3.6/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.26.4) or chardet (3.0.4) doesn't match a supported version! RequestsDependencyWarning) +--------------------------------------+------------------------+--------+ | ID | Name | Status | +--------------------------------------+------------------------+--------+ | 8ddcd168-cc18-4ce2-97c5-c3502ac471a4 | overcloud-full | active | | 8d9cfac9-400b-4570-b0b1-baeb175b16c4 | overcloud-full-initrd | active | | c561f1d5-41ae-4599-81ea-de2c1e74eae7 | overcloud-full-vmlinuz | active | +--------------------------------------+------------------------+--------+ *Using the command to introspect the node, it was able to discover the node and I could provision the node boot via pxe, and load the image on the node. I could see the login prompt on the server, after some time of provision shut the node down.* *openstack overcloud node discover --range 10.0.40.5 --credentials admin:XXXX --introspect --provide* /usr/lib/python3.6/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.26.4) or chardet (3.0.4) doesn't match a supported version! RequestsDependencyWarning) Successfully probed node IP 10.0.40.5 Successfully registered node UUID 4bdd55bd-c4d9-4af0-b619-2e0b7b0107cf /usr/lib/python3.6/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.26.4) or chardet (3.0.4) doesn't match a supported version! RequestsDependencyWarning) PLAY [Baremetal Introspection for multiple Ironic Nodes] *********************** 2021-04-22 07:04:28.978299 | 002590fe-0d22-76eb-1a70-000000000008 | TASK | Check for required inputs 2021-04-22 07:04:29.002729 | 002590fe-0d22-76eb-1a70-000000000008 | SKIPPED | Check for required inputs | localhost | item=node_uuids 2021-04-22 07:04:29.004468 | 002590fe-0d22-76eb-1a70-000000000008 | TIMING | Check for required inputs | localhost | 0:00:00.069134 | 0.0 .... .... .... 2021-04-22 07:11:43.261714 | 002590fe-0d22-76eb-1a70-000000000016 | TASK | Nodes that failed introspection 2021-04-22 07:11:43.296417 | 002590fe-0d22-76eb-1a70-000000000016 | FATAL | Nodes that failed introspection | localhost | error={ "msg": " 4bdd55bd-c4d9-4af0-b619-2e0b7b0107cf" } 2021-04-22 07:11:43.297359 | 002590fe-0d22-76eb-1a70-000000000016 | TIMING | Nodes that failed introspection | localhost | 0:07:14.362025 | 0.03s NO MORE HOSTS LEFT ************************************************************* PLAY RECAP ********************************************************************* localhost : ok=4 changed=1 unreachable=0 failed=1 skipped=5 rescued=0 ignored=0 2021-04-22 07:11:43.301553 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Summary Information ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2021-04-22 07:11:43.302101 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Total Tasks: 10 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2021-04-22 07:11:43.302609 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Elapsed Time: 0:07:14.367265 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2021-04-22 07:11:43.303162 | UUID | Info | Host | Task Name | Run Time 2021-04-22 07:11:43.303740 | 002590fe-0d22-76eb-1a70-000000000014 | SUMMARY | localhost | Start baremetal introspection | 434.03s 2021-04-22 07:11:43.304248 | 002590fe-0d22-76eb-1a70-000000000015 | SUMMARY | localhost | Nodes that passed introspection | 0.04s 2021-04-22 07:11:43.304814 | 002590fe-0d22-76eb-1a70-000000000016 | SUMMARY | localhost | Nodes that failed introspection | 0.03s 2021-04-22 07:11:43.305341 | 002590fe-0d22-76eb-1a70-000000000008 | SUMMARY | localhost | Check for required inputs | 0.03s 2021-04-22 07:11:43.305854 | 002590fe-0d22-76eb-1a70-00000000000a | SUMMARY | localhost | Set node_uuids_intro fact | 0.02s 2021-04-22 07:11:43.306397 | 002590fe-0d22-76eb-1a70-000000000010 | SUMMARY | localhost | Check if validation enabled | 0.02s 2021-04-22 07:11:43.306904 | 002590fe-0d22-76eb-1a70-000000000012 | SUMMARY | localhost | Fail if validations are disabled | 0.02s 2021-04-22 07:11:43.307379 | 002590fe-0d22-76eb-1a70-00000000000e | SUMMARY | localhost | Set concurrency fact | 0.02s 2021-04-22 07:11:43.307913 | 002590fe-0d22-76eb-1a70-00000000000c | SUMMARY | localhost | Notice | 0.02s 2021-04-22 07:11:43.308417 | 002590fe-0d22-76eb-1a70-000000000011 | SUMMARY | localhost | Run Validations | 0.02s 2021-04-22 07:11:43.308926 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ End Summary Information ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2021-04-22 07:11:43.309423 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ State Information ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 2021-04-22 07:11:43.310021 | ~~~~~~~~~~~~~~~~~~ Number of nodes which did not deploy successfully: 1 ~~~~~~~~~~~~~~~~~ 2021-04-22 07:11:43.310545 | The following node(s) had failures: localhost 2021-04-22 07:11:43.311080 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Ansible execution failed. playbook: /usr/share/ansible/tripleo-playbooks/cli-baremetal-introspect.yaml, Run Status: failed, Return Code: 2 Exception occured while running the command Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/tripleoclient/command.py", line 34, in run super(Command, self).run(parsed_args) File "/usr/lib/python3.6/site-packages/osc_lib/command/command.py", line 41, in run return super(Command, self).run(parsed_args) File "/usr/lib/python3.6/site-packages/cliff/command.py", line 187, in run return_code = self.take_action(parsed_args) or 0 File "/usr/lib/python3.6/site-packages/tripleoclient/v1/overcloud_node.py", line 462, in take_action retry_timeout=parsed_args.retry_timeout, File "/usr/lib/python3.6/site-packages/tripleoclient/workflows/baremetal.py", line 193, in introspect "retry_timeout": retry_timeout, File "/usr/lib/python3.6/site-packages/tripleoclient/utils.py", line 728, in run_ansible_playbook raise RuntimeError(err_msg) RuntimeError: Ansible execution failed. playbook: /usr/share/ansible/tripleo-playbooks/cli-baremetal-introspect.yaml, Run Status: failed, Return Code: 2 Ansible execution failed. playbook: /usr/share/ansible/tripleo-playbooks/cli-baremetal-introspect.yaml, Run Status: failed, Return Code: 2 *(undercloud) [stack@undercloud ~]$ openstack baremetal introspection list* /usr/lib/python3.6/site-packages/requests/__init__.py:91: RequestsDependencyWarning: urllib3 (1.26.4) or chardet (3.0.4) doesn't match a supported version! RequestsDependencyWarning) +--------------------------------------+---------------------+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | UUID | Started at | Finished at | Error | +--------------------------------------+---------------------+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | 4bdd55bd-c4d9-4af0-b619-2e0b7b0107cf | 2021-04-22T01:41:32 | 2021-04-22T01:41:35 | Failed to set boot device to PXE: Failed to set boot device for node 4bdd55bd-c4d9-4af0-b619-2e0b7b0107cf: Client Error for url: http://10.0.1.202:6385/v1/nodes/4bdd55bd-c4d9-4af0-b619-2e0b7b0107cf/manage…, Node 4bdd55bd-c4d9-4af0-b619-2e0b7b0107cf is locked by host undercloud.localdomain, please retry after the current operation is completed. | | 3d091348-e9c7-4e99-80e3-df72d332d935 | 2021-04-21T12:36:30 | 2021-04-21T12:36:32 | Failed to set boot device to PXE: Failed to set boot device for node 3d091348-e9c7-4e99-80e3-df72d332d935: Client Error for url: http://10.0.1.202:6385/v1/nodes/3d091348-e9c7-4e99-80e3-df72d332d935/manage…, Node 3d091348-e9c7-4e99-80e3-df72d332d935 is locked by host undercloud.localdomain, please retry after the current operation is completed. | +--------------------------------------+---------------------+---------------------+--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

2 2

[neutron] April 2021 - PTG Summary
by Slawek Kaplonski 26 Apr '21

26 Apr '21

Hi, Below is my summary of the Neutron sessions during the PTG last week. Etherpad with agenda and all notes from the sessions is available at https:// etherpad.opendev.org/p/neutron-xena-ptg If You want to discuss some topic in more details, please start new thread for it to keep this one clean. ## Day 1 (Monday) ### Retrospective of the Wallaby cycle Good things: * we accomplished our community goals this cycle, like e.g. rootwrap to privsep migration, * migration to the secure RBAC, * many performance improvements, * CI improvements and the job simplification/reducing, * stable team, and a lot of small patches from all around the world, * OVN feature gap with OVS is shrinking, * team support to implement address groups, including RBAC support. In the list of not so good things we mentioned: * During the previous PTG we were talking about some OVN related guides/sessions but we didn't made any, * networking-midonet - (yet another) stadium project deprecated due to lack of maintainers, but it's better to have them clearly marked as out of stadium, than false expectations - we can bring such projects back when needed anyway, * still unstable CI, mainly tempest and tempest-plugin jobs, also during this release functional tests. As for action items for the _Xena_ cycle, we listed couple of things: * Miguel wants to do the ovn knowledge share internally in his company and later share the material, * we will keep working on the improvements for our CI, list of all opened, CI related bugs can be found at https://tinyurl.com/neutron-gate-failures and we will work on reducing that list in next months. * Rodolfo and Miguel will follow up on Nova's plans to drop eventlet and move to the threading and will investigate if we can try to do something similar in the Neutron, * Akihiro raised good point about ML2/OVN and stadium projects. We should clarify the support plan for OVN in all of our stadium projects. Lajos and Lucas volunteered to work on that. ### Secure RBAC - testing - discussion with QA team As next session in the first day, we attended QA team's session about testing new secure RBAC policies. Summary of that discussion can be found in the etherpad: https://etherpad.opendev.org/p/qa-xena-ptg. QA team wants to switch each project to enforce new defaults and the system scope tokens in the Devstack. We will have to monitor that and check what needs to be fixed on our side to accomplish that. ### Deprecated hybrid plug and the iptables_hybrid firewall driver Bence proposed discussion about potential deprecation of the iptables_hybrid firewall driver as we have now native openvswitch driver too. After discussion we decided that we are not going to deprecate it, at least for now. There are known differences between those two drivers and there is still many usecases where people wants to use iptables_hybrid driver. ### Future of the Linuxbridge backend As the last topic of the first day we discussed future of the Linuxbridge backend and ML2 driver. The same topic was discussed in the http://kaplonski.pl/ blog/shanghai_ptg_summary/ and then, based on the feedback from operators we decided that we are not going to deprecate this backend anytime soon as many people are still using it. But now we are couple of cycle later and things didn't change a lot. We still don't have anyone who would like to maintain it. In most cases it works fine but there are also pretty many bugs reported for that backend, which don't have owners - see https://tinyurl.com/linuxbridge-bugs. But things may change in the future and e.g. removal of the legacy iptables from the main distributions may makes things harder to work. We again had feedback, e.g. from Jon that NASA is using that driver and want's to keep using it. But from the other hand in the core Neutron we don't have anyone interested in maintaining it currently. The outcome of the discussion is that we will again raise that topic and ask operators about: - who is using it and what are the use cases addressed by that driver - maybe we can help with proposing another solution, - who is willing to help with maintenance of that backend. If You are using Linuxbridge backend, please give us such feedback. For Xena status is that we still do our best to keep Linuxbridge backend to be running and fully supported but we will also revisit its status again in the next PTG. ## Day 2 (Tuesday) ### Continuation of "L3 feature improvements" During the second day of the PTG we had very interesting discussions about L3 improvements. We discussed bunch of the RFEs proposed by Bence, Lajos and Manu: * [RFE] Add BFD support for Neutron https://bugs.launchpad.net/neutron/+bug/ 1907089 and the spec: https://review.opendev.org/c/openstack/neutron-specs/+/767337 * [RFE] Allow explicit management of default routes: https://bugs.launchpad.net/ neutron/+bug/1921126) and the spec: https://review.opendev.org/c/openstack/neutron-specs/+/781475 * Allow multiple external gateways on a router: https://bugs.launchpad.net/neutron/ +bug/1905295 and the spec: https://review.opendev.org/c/openstack/neutron-specs/+/779511 * [RFE] Enhancement to Neutron BGPaaS to directly support Neutron Routers & bgp-peering from such routers over internal & external Neutron Networks https:// bugs.launchpad.net/neutron/+bug/1921461 and the spec: https://review.opendev.org/c/openstack/neutron-specs/+/783791 * [RFE] BFD for BGP Dynamic Routing: https://bugs.launchpad.net/neutron/+bug/ 1922716 and the spec: https://review.opendev.org/c/openstack/neutron-specs/+/785349. That one still needs to be discussed and approved during the drivers meeting. General outcome from the discussion is that during the Xena cycle we at least wants to have all those specs merged to have agreement about implementation details. When that will be done, Bence, Lajos and others from Ericsson will work on the implementation of those RFEs. ### Tap-as-a-service (taas) project Next topic which we discussed during Tuesday's session was about Tap-as-a-service: https://opendev.org/x/tap-as-a-service project. Few cycle back we were thinking about including it in the Neutron stadium but finally that

1 0

[keystone] Token
by Adam Tomas 26 Apr '21

26 Apr '21

Hi Which CLI setting sets domain_id field in a token? I tried openstack —os-domain-id SOME_OS_COMMAND, openstack —os-default-domain SOME_OS_COMMAND, openstack —os-default-domain_id SOME_OS_COMMAND but none of them sets this field and policies checking domain_id:%(domain_id) don’t work because of that. Interesting thing is that horizon somehow generates token with domain_id set and everything works with the same policies, I have a problem only with CLI. Can user_domain_id (which is inside of every token is see for particular user) be used instead of domain_id? Example token from CLI: 2021-04-23 12:16:38.090 700 DEBUG keystone.server.flask.request_processing.middleware.auth_context [req-117bc600-490e-46ae-a857-0c8d09dc1dbc 9adbxxxxb02ef 61d4xxxx9c0f - 3a08xxxx82c1 3a08xxxx82c1] RBAC: auth_context: {'token': <TokenModel (audit_id=BLWXSpdbTvqc0YS9WzStjQ, audit_chain_id=['BLWXSpdbTvqc0YS9WzStjQ']) at 0x7f8c390aaca0>, 'domain_id': None, 'trust_id': None, 'trustor_id': None, 'trustee_id': None, 'domain_name': None, 'group_ids': [], 'user_id': '9adbxxxx02ef', 'user_domain_id': '3a08xxxx82c1', 'system_scope': None, 'project_id': '61d4xxxx9c0f', 'project_domain_id': '3a08xxxx82c1', 'roles': ['member', 'project_admin', 'reader', 'domain_admin'], 'is_admin_project': True, 'service_user_id': None, 'service_user_domain_id': None, 'service_project_id': None, 'service_project_domain_id': None, 'service_roles': []} fill_context /var/lib/kolla/venv/lib/python3.8/site-packages/keystone/server/flask/request_processing/middleware/auth_context.py:478 Example token from Horizon: 2021-04-23 12:48:21.009 704 DEBUG keystone.server.flask.request_processing.middleware.auth_context [req-d6d89d3e-c3c1-48c0-b3ed-b3dcedb54db3 9adbxxxx02ef - 3a08xxxx82c1 3a08xxxx82c1 -] RBAC: auth_context: {'token': <TokenModel (audit_id=ZHltw2esTJyTRnFlgHetog, audit_chain_id=['ZHltw2esTJyTRnFlgHetog', 'iJGq-E9fQKKXdZaZq72MQw']) at 0x7f8c3a1b4460>, 'domain_id': '3a08xxx82c1', 'trust_id': None, 'trustor_id': None, 'trustee_id': None, 'domain_name': ‚xxxx', 'group_ids': [], 'user_id': '9adbxxxx02ef', 'user_domain_id': '3a08xxxx82c1', 'system_scope': None, 'project_id': None, 'project_domain_id': None, 'roles': ['project_admin', 'member', 'reader', 'domain_admin'], 'is_admin_project': False, 'service_user_id': None, 'service_user_domain_id': None, 'service_project_id': None, 'service_project_domain_id': None, 'service_roles': []} fill_context /var/lib/kolla/venv/lib/python3.8/site-packages/keystone/server/flask/request_processing/middleware/auth_context.py:478 Best regards Adam

1 1

[cinder] festival of mypy reviews 30 April 2021
by Brian Rosmaita 26 Apr '21

26 Apr '21

Hello Cinder community members, As discussed at last week's PTG, we will be holding a special Cinder Festival of mypy Reviews at the end of this week on Friday 30 April. what: Cinder Festival of mypy Reviews when: Friday 30 April 2021 from 1400-1600 UTC where: https://meetpad.opendev.org/cinder-festival-of-reviews See you there! brian

1 0

[cinder] reminder: this week's meeting in video+IRC
by Brian Rosmaita 26 Apr '21

26 Apr '21

Quick reminder that this week's Cinder team meeting on Wednesday 28 April, being the final meeting of the month, will be held in both videoconference and IRC at the regularly scheduled time of 1400 UTC. These are the video meeting rules we've agreed to: * 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 meeting will be recorded. connection info: https://bluejeans.com/3228528973 meeting agenda: https://etherpad.opendev.org/p/cinder-xena-meetings cheers, brian

1 0

[neutron] bug deputy report for week of 2021-04-19
by Rodolfo Alonso Hernandez 26 Apr '21

26 Apr '21

Hello Neutrinos: This is the list of bugs opened during the last week. I would like to remark the two critical bugs and the high one, that are not assigned. Critical: - https://bugs.launchpad.net/neutron/+bug/1925451: “[stable/rocky] grenade job is broken”. Unassigned. - https://bugs.launchpad.net/neutron/+bug/1926109: “SSH timeout (wait timeout) due to potential paramiko issue“. Unassigned. High: - https://bugs.launchpad.net/neutron/+bug/1925498: “SNAT is not working“. Unassigned. - NOTE: I didn't have time to test if this issue is legit. IMO that's something that should have been detected years ago but I'm until this bug is triaged, I'll set it as "high". Medium: - https://bugs.launchpad.net/neutron/+bug/1925406: “[functional] run dsvm-functional locally will need ovn no matter the running cases are”. Unassigned. - https://bugs.launchpad.net/neutron/+bug/1916428: “dibbler tool for dhcpv6 is concluded“. Unassigned. - NOTE: I’m adding this bug into this list because this week a duplicate of this bug was filled. Worth mentioning it again. - https://bugs.launchpad.net/neutron/+bug/1925836: “[OVN] OVN metadata should not need to monitor the enterily Chassis table”. Assigned to Lucas. - https://review.opendev.org/c/openstack/neutron/+/787780 Low: - https://bugs.launchpad.net/neutron/+bug/1925218: “[OVN] BW limit QoS rules assigned to networks with SR-IOV ports are created on NBDB”. Assigned to Rodolfo. - https://review.opendev.org/c/openstack/neutron/+/787351 - https://bugs.launchpad.net/neutron/+bug/1925368: “[L3] Router GW can be removed with routes defined”. Unassigned. - NOTE: I would like to know if this is a valid issue or not. - https://bugs.launchpad.net/neutron/+bug/1925433: “[doc] SR-IOV config documentation has not been updated when SRIOV attach got implemented”. Assigned to Balazs. - https://review.opendev.org/c/openstack/neutron/+/787500 - https://bugs.launchpad.net/neutron/+bug/1925841: “"backref" warnings for "QosNetworkPolicyBinding.port" and "StandardAttribute.tags"“. Assigned to Rodolfo. - https://review.opendev.org/c/openstack/neutron/+/787782 Whishlist: - https://bugs.launchpad.net/neutron/+bug/1925528: “Improve "NeutronDbObject.objects_exist" performance“. Assigned to Rodolfo. - https://review.opendev.org/c/openstack/neutron/+/787681 Incomplete: - https://bugs.launchpad.net/neutron/+bug/1925213: “o-api seems to leak memory when ovn-octavia-provider is used” - https://bugs.launchpad.net/neutron/+bug/1926045: “Restrictions on FIP binding” - https://bugs.launchpad.net/neutron/+bug/1926049: “check_changed_vlans failed“ Undecided/unconfirmed: - https://bugs.launchpad.net/neutron/+bug/1925789: “neutron fwaas2 l3 - inconsistent order of jump rules“. FWaaS bug in Train. Regards.

1 0

[qa][ptg] Summary of the discussed topics
by Martin Kopec 26 Apr '21

26 Apr '21

Hi all, here's a summary of the topics we have discussed during QA sessions: * Migration of devstack and Tempest tests to new secure RBAC There was a great discussion about this goal, many good points raised. See the PTG etherpad for more details. * Patrole execution time improvement This is up for a few cycles already and is missing a volunteer. We will discuss next steps towards this goal during one of the following QA office hour meetings. * What FeatureFreeze means for QA projects We have discussed the types of changes we should avoid merging during Feature Freeze. * Tempest plugins should use master tempest in their testing jobs We have noticed that many check/gate CI jobs use latest tempest tag (downloaded form pip) instead of the master branch we may potentially lead to approving changes which are not compatible with the master branch of tempest. * Fix backward compatibility of run-tempest role We deprecated couple of tempest's CLI args and replaced them by new ones in 26.1.0, however, as it turns out the backward compatibility conditions in run-tempest role are not sufficient. We will try to create a stable job variant to be used in jobs with older tempest versions. * Cleanup of duplicated scenario.manager Announcing tempest.scenario.manager a stable interface in tempest 27.0.0 raises a question when to remove the duplicated scenario.manager in plugins' codebase. * Whether to branch tempest No, we won't. We wrote down all pros and cons. The main fact against is that per an agreement all stable releases + master should be tested with the same set of tests. However, we will discuss branching for EM with the release team. Full discussion (PTG etherpad): https://etherpad.opendev.org/p/qa-xena-ptg QA's priority items for Xena cycle: https://etherpad.opendev.org/p/qa-xena-priority Regards, -- Martin Kopec Senior Software Quality Engineer Red Hat EMEA <https://red.ht/sig>

1 0

rocky 2 node installation unable to access internet in instance
by cloud learner 26 Apr '21

26 Apr '21

Dear All, I am new to this, installed rocky on centos 7 with 2 node controller and compute nodes, followed https://docs.openstack.org/neutron/rocky/install/environment-networking-con… as mentioned in the document used vxlan and the Networking option 2: Self service network and used linuxbridge, verified all the steps as mentioned in the document and all things are working fine but i am unable to access the internet in instances. The network layout image attached herewith for reference there are two ports, one is for management and another is a provider network through which the internet is accessible. The provider network is 10.1.0.0/16 and the gateway is 10.1.1.1 which I have set in the external network.. When i run # ip netns command on controller node it shows qdhcp and qrouter [root@controller ~]# ip netns qrouter-2f84ff08-7293-4822-a4c1-57278d80f1cf (id: 2) qdhcp-186cc689-267b-49ca-90a7-b312fd0367f3 (id: 1) qdhcp-513292db-3eb8-4902-974f-4bb9c4757652 (id: 0) but when I run # ip netns command on compute it shows nothing. [root@controller ~]# openstack network agent list +--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+ | ID | Agent Type | Host | Availability Zone | Alive | State | Binary | +--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+ | 0286adac-2a32-4866-8b75-95f190c2c310 | Linux bridge agent | compute1 | None | :-) | UP | neutron-linuxbridge-agent | | 47728860-d7b0-4b15-b3dc-1f8a6bf81125 | Metadata agent | controller | None | :-) | UP | neutron-metadata-agent | | 4957d1b2-ea33-4034-9869-8518438416b0 | L3 agent | controller | nova | :-) | UP | neutron-l3-agent | | a81e4138-0190-41ef-b0a1-bd1b66c01343 | DHCP agent | controller | nova | :-) | UP | neutron-dhcp-agent | | ea43868d-8394-4cf5-a104-edc5ecbaff9e | Linux bridge agent | controller | None | :-) | UP | neutron-linuxbridge-agent | +--------------------------------------+--------------------+------------+-------------------+-------+-------+---------------------------+ Is there any need to create br-int or br-ex on nodes because that is not mentioned in the link which i have followed, if need kindly guide the steps to do that and on which node these steps need to follow.

1 0

How do I delete my account of review.opendev.org?
by Rikimaru Honjo 26 Apr '21

26 Apr '21

Hi, How do I delete my account of review.opendev.org? I couldn't find the UI or documents for it. I'm sorry if I overlooked it. Best regards,

2 4

audit middleware logs
by Basireddy Hanumantha Reddy 25 Apr '21

25 Apr '21

Hi, I am using pike version. I have configured nova service as mentioned in https://docs.openstack.org/keystonemiddleware/pike/audit.html 1. added in api-paste.ini file [ filter : audit ] paste . filter_factory = keystonemiddleware . audit : filter_factory audit_map_file = / etc / nova / api_audit_map . conf 2. verified composite:openstack_compute_api_v2 section. 3. Copied the api_audit_map.conf file to the /etc/nova/ After that I have restared all openstack services. But I couldn't find any audit logs with oslo.messaging.notification.audit.http.request in nova.log file I can see only logs related to oslo.messaging as openstack nova-scheduler[17534]: INFO oslo.messaging.notification.scheduler.select_destinations.start [None req-01612e5a-37d9-4b62-970a-fcf7d3c409ad admin admin] {"event_type": "scheduler.select_destinations.start", "timestamp": "2021-04-25 11:10:40.249260", "payload": {"request_spec": {"instance_properties": {"root_gb": 1, "uuid": "ee4ddae2-9397-401c-b80f-543061e75dd2", "availability_zone": null, "ephemeral_gb": 0, "numa_topology": null, "memory_mb": 512, "vcpus": 1, "project_id": "d078fd26a1204e6abede5faca777da8b", "pci_requests": {"requests": []}}, "instance_type": {"disabled": false, "root_gb": 1, "name": "m1.tiny", "flavorid": "1", "deleted": false, "created_at": "2021-04-22T17:34:26.000000", "ephemeral_gb": 0, "updated_at": null, "memory_mb": 512, "vcpus": 1, "extra_specs": {}, "swap": 0, "rxtx_factor": 1.0, "is_public": true, "deleted_at": null, "vcpu_weight": 0, "id": 6}, "image": {"status": "active", "name": "cirros-0.3.5-x86_64-disk", "container_format": "bare", "created_at": "2021-04-22T17:32:54.000000", "disk_format": "qcow2", "updated_at": "2021-04-22T17:32:55.000000", "id": "e0d062fa-2b3c-4a6e-90e4-3ef796c3a594", "min_disk": 0, "min_ram": 0, "checksum": "f8ab98ff5e73ebab884d80c9dc9c7290", "owner": "d078fd26a1204e6abede5faca777da8b", "properties": {}, "size": 13267968}, "num_instances": 1}}, "priority": "INFO", "publisher_id": "scheduler.openstack", "message_id": "3128ed95-1599-46f8-b110-93fcb0776812"} what I understood that as part of audit middleware, logs should contain oslo.messaging.notification.audit.http.request and oslo.messaging.notification.audit.http.response. Please suggest what I am missing. Thanks, Hanumantha Reddy.

1 0

Recall: [cyborg][ptg] Cyborg vPTG Summary April 2021
by Wang, Xin-ran 25 Apr '21

25 Apr '21

Wang, Xin-ran would like to recall the message, "[cyborg][ptg] Cyborg vPTG Summary April 2021".

1 0

Recall: [cyborg][ptg] Cyborg vPTG Summary April 2021
by Wang, Xin-ran 25 Apr '21

25 Apr '21

Wang, Xin-ran would like to recall the message, "[cyborg][ptg] Cyborg vPTG Summary April 2021".

1 0

[cyborg][ptg] Cyborg vPTG Summary April 2021
by Wang, Xin-ran 25 Apr '21

25 Apr '21

Hi all, Thanks for all your participation! We've conducted a successful meeting last week. Here is the aggregated summary from Cyborg vPTG discussion. Please check it out and feel free to feedback any concerns you might have. We did a retrospective of Wallaby release, including: * We supports more operations supported for a VM with accelerator attached. * We introduced new drivers for Intel x710 NIC and Inspur's NVMe SSD Card. * We implemented a new configuration file allowing more flexible device configuration. Topic discussion: Here's some major discussion and conclusion of Cyborg vPTG. For more details, please refer to the etherpad[1]. * More nova operation supporting: - We prioritized the tasks: 1. suspend/resume. 2. cold migration. 3. live migration. * vGPU support: - We reached an internal agreement on whole workflow which can be apply as a generic framework for mdev device. * API enhancement: Some of the following items requires a new micro-version. - Add refresh policy check for all APIs. - Add device profile update API. - Add ARQ query by multiple instances API. - Add disable/enable device API, this one requires a spec first. - Enhance device profile show API with more information. * Cleanup issue: - This issue comes from the case where one compute node shutdown accidently, and the accelerator records in placement and cyborg DB remains as the orphaned resources. We agreed to implement a mechanism to clean up the orphaned resources, this one also need a spec. [1] https://etherpad.opendev.org/p/cyborg-xena-ptg Thanks, Xin-Ran Wang

1 0

[Ironic] Proposal to move weekly meeting 1 hour earlier
by Kanevsky, Arkady 24 Apr '21

24 Apr '21

Team, On today's PTG Interop meeting we proposed to move weekly Friday meeting 1 hour earlier to 16:00 UTC. Please, respond if the proposed time will or not will work for you. Thanks, Arkady Kanevsky, Ph.D. SP Chief Technologist & DE Dell Technologies office of CTO Dell Inc. One Dell Way, MS PS2-91 Round Rock, TX 78682, USA Phone: 512 7204955

4 3

[nova][placement] Xena PTG results
by Balazs Gibizer 24 Apr '21

24 Apr '21

Hi, Thank you for joining the nova PTG! We recorded our agreements in the etherpad[1]. And I made an export of that etherpad (see attached) to avoid loosing the information. Cheers, gibi [1] https://etherpad.opendev.org/p/nova-xena-ptg

1 0

[keystone][victoria] keystone fernet token not found/recognized
by Shalabh Goel 23 Apr '21

23 Apr '21

Hi, I have installed Openstack victoria on Ubuntu server 20.04. The issue is that other services like nova and neutron are not able to authenticate with the keystone service. In the keystone log, the following lines are appearing. 2021-04-23 13:24:53.217 23331 WARNING keystone.server.flask.application [req-2b575a77-2f9f-444b-9f31-061de41fd602 f3571e3ee8d84fb0ba14bdbe2542916d 930b9693e7694aa68370352c7b911168 - default default] Could not recognize Fernet token: keystone.exception.TokenNotFound: Could not recognize Fernet token Also, I am able to run openstack client commands related to keystone on the server which tells me that keystone related things are working fine. But I am not able to execute commands like openstack compute service list. I am not able to find anything on this after searching online. Can this be an issue with the way haproxy is configured? Since there are 2 servers with keystone installed on them with pacemaker and haproxy. Please tell me what I can do to solve this issue. Thanks Shalabh

2 1

Create OpenStack VMs in few seconds
by open infra 23 Apr '21

23 Apr '21

Hi, I was looking for a way to provision and connect to VMs within a few seconds and ended up in the OpenStack Summit demo on 'OpenStack Virtual Machine Quickly Available in One Second'. I highly appreciate if someone can provide a tutorial or related documentation on how to achieve this? Regards, Danishka

6 16

[TripleO] Xena PTG wrapup and links
by Marios Andreou 23 Apr '21

23 Apr '21

On Friday, April 23, 2021, Marios Andreou <marios(a)redhat.com> wrote: > On Fri, Apr 23, 2021 at 3:37 PM Marios Andreou <marios(a)redhat.com> wrote: > > > > Hello TripleO o/ > > > > a massive ** THANK YOU! ** to everyone that took part in our PTG > meeting and especially the folks that prepared for 18 sessions across four > days. Participants were variable but at most I saw/noticed these numbers: > Monday:54, Tuesday:49, Wednesday:46, Thursday:42 > > > > I've included a condensed listing below [3] for convenience and you can > find the full schedule at [1] > > with session descriptions, links to individual topic etherpads and links > to the daily recordings. Note there is a problem with day 1 recording, I am > waiting to hear back but otherwise that's all we have right now (day 2/3/4 > are complete as far as i can see - didn't watch it all again!). > > > > Our "team photo" from Monday is at [2] apologies to the person who is > hidden behind the jitsi controls. In my defense we did this when we just > switched to meetpad after the initial zoom issues. For what it's worth, if > you send me a link to an updated photo I can add you in again ;) > > > > regards, marios > > > > [1] https://etherpad.opendev.org/p/tripleo-ptg-xena > > > > [2] https://i.imgur.com/mxaGaSf.jpg > > > > [3] DAY 1: > > Topic: Wallaby cycle community retrospective Proposer: marios > > Topic: Plan/Swift removal update Proposer: cloudnull and dropped ramishra here ^^^ sorry ! folks better just refer directly to https://etherpad.opendev.org/p/tripleo-ptg-xena for the correct info seems my copy pasta in this email was not very good i dropped names from the presenters thanks > > Topic: Ephemeral Heat Update Proposer: slagle > > Topic: update and planned work networks & ports v2 "no heat" Proposer: > hjensas > Topic: Ceph Integration Update Proposer: gfidente, fmount > > apologies John: I dropped ", fultonj" on the ceph session in my copy/pasta > > thanks > -- _sent from my mobile - sorry for spacing spelling etc_

1 0

[TripleO] Xena PTG wrapup and links
by Marios Andreou 23 Apr '21

23 Apr '21

Hello TripleO o/ a massive ** THANK YOU! ** to everyone that took part in our PTG meeting and especially the folks that prepared for 18 sessions across four days. Participants were variable but at most I saw/noticed these numbers: Monday:54, Tuesday:49, Wednesday:46, Thursday:42 I've included a condensed listing below [3] for convenience and you can find the full schedule at [1] with session descriptions, links to individual topic etherpads and links to the daily recordings. Note there is a problem with day 1 recording, I am waiting to hear back but otherwise that's all we have right now (day 2/3/4 are complete as far as i can see - didn't watch it all again!). Our "team photo" from Monday is at [2] apologies to the person who is hidden behind the jitsi controls. In my defense we did this when we just switched to meetpad after the initial zoom issues. For what it's worth, if you send me a link to an updated photo I can add you in again ;) regards, marios [1] https://etherpad.opendev.org/p/tripleo-ptg-xena [2] https://i.imgur.com/mxaGaSf.jpg [3] DAY 1: Topic: Wallaby cycle community retrospective Proposer: marios Topic: Plan/Swift removal update Proposer: cloudnull Topic: Ephemeral Heat Update Proposer: slagle Topic: update and planned work networks & ports v2 "no heat" Proposer: hjensas Topic: Ceph Integration Update Proposer: gfidente, fmount DAY2: Topic: Lets move to whole disk overcloud-full images by default Proposer: sbaker Topic: Get rid of the service healthchecks Proposer: Tengu Topic: Tripleo Repos - single sourcing repo setup Proposer: sshaidm, marios, chkumar, rlandy Topic: One yaml to rule all tempest tests Proposer: arxcruz Topic: TripleO.Next Proposer: mwhahaha DAY3: Topic: Get rid of the terrible tripleo-ansible-inventory script Proposer: Tengu Topic: Validation Framework UI Output Proposer: dpeacock/strider/matbu/jpodivin Topic Validation Framework Next Generation Proposer: dpeacock Topic: BGP Routing with FRR Proposer: dsneddon Topic: Consolidate Update/Upgrade Proposer: holser DAY4: Topic: RBAC and TripleO Proposer: LBragstad, HRybacki Topic: What and when to expect w/ CentOS-Stream-9 Proposer: Wes Hayutin Topic: os-migrate brief introduction Proposer: jistr, ccamacho

1 1

Re: [openstack-community] Error in downloading Devstack
by Amy Marrich 23 Apr '21

23 Apr '21

Jean, I'm including the OpenStack Discuss list as it is the appropriate list. In order to help we'll need to know what issues you're seeing. We are finishing up our Project Team Gathering today so it may be a few days to get a response. Thanks, Amy (spotz) On Fri, Apr 23, 2021 at 1:50 AM Jean Richard <wilrichard00(a)gmail.com> wrote: > Dear Openstack Community, > > I am new to Openstack and I am having problems downloading Devstack. I > followed the instructions of "DevStack Docs" and some books. But I am > getting a lot of error messages. Can someone please help me with a good > reference. > I am looking forward to hearing from you. > _______________________________________________ > Community mailing list > Community(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/community >

1 0

OpenStack Wallaby for Ubuntu 21.04 and Ubuntu 20.04 LTS
by Corey Bryant 23 Apr '21

23 Apr '21

The Ubuntu OpenStack team at Canonical is pleased to announce the general availability of OpenStack Wallaby on Ubuntu 21.04 (Hirsute Hippo) and Ubuntu 20.04 LTS (Focal Fossa) via the Ubuntu Cloud Archive. Details of the Wallaby release can be found at: https://www.openstack.org/software/wallaby. To get access to the Ubuntu Wallaby packages: == Ubuntu 21.04 == OpenStack Wallaby is available by default for installation on Ubuntu 21.04. == Ubuntu 20.04 LTS == The Ubuntu Cloud Archive for OpenStack Wallaby can be enabled on Ubuntu 20.04 by running the following command: sudo add-apt-repository cloud-archive:wallaby The Ubuntu Cloud Archive for Wallaby includes updates for: aodh, barbican, ceilometer, ceph (16.2.0), cinder, designate, designate-dashboard, dpdk (20.11.1), glance, gnocchi, heat, heat-dashboard, horizon, ironic, ironic-ui, keystone, magnum, magnum-ui, manila, manila-ui, masakari, mistral, murano, murano-dashboard, networking-arista, networking-bagpipe, networking-baremetal, networking-bgpvpn, networking-hyperv, networking-l2gw, networking-mlnx, networking-odl, networking-sfc, neutron, neutron-dynamic-routing, neutron-vpnaas, nova, octavia, octavia-dashboard, openstack-trove, openvswitch (2.15.0), ovn (20.12.0), ovn-octavia-provider, panko, placement, sahara, sahara-dashboard, senlin, swift, trove-dashboard, vmware-nsx, vitrage, watcher, watcher-dashboard, zaqar, and zaqar-ui. For a full list of packages and versions, please refer to: http://reqorts.qa.ubuntu.com/reports/ubuntu-server/cloud-archive/wallaby_ve… == Reporting bugs == If you have any issues please report bugs using the ‘ubuntu-bug’ tool to ensure that bugs get logged in the right place in Launchpad: sudo ubuntu-bug nova-conductor Thank you to everyone who contributed to OpenStack Wallaby. Enjoy and see you in Xena! Corey (on behalf of the Ubuntu OpenStack Engineering team)

2 4

[kuryr] vPTG April 2021
by Maysa De Macedo Souza 23 Apr '21

23 Apr '21

Hello, Two sessions were scheduled for Kuryr on the upcoming PTG: - 7-8 UTC on April 20 - 2-3 UTC on April 22 Everyone is more than welcome to join the sessions and check our future plans, give feedback or discuss anything regarding Kuryr. Even though participation is free registration is needed[1]. Regards, Maysa Macedo. [1] https://april2021-ptg.eventbrite.com

2 2

[largescale-sig] PTG meeting: April 21, 15utc
by Thierry Carrez 23 Apr '21

23 Apr '21

Hi everyone, Our next Large Scale SIG meeting will be this Wednesday at 15utc in the Ocata meeting room from the virtual PTG[1]. You can doublecheck how it translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20210421T15 Please register[2] to the PTG if you haven't already, it will give you access to communications explaining how to join. We'll do a general presentation of the Large Scale SIG activities, show off our "Large Scale Journey" documentation, and discuss the topics of our next video meeting(s). Feel free to add other topics to our PTG meeting agenda at: https://etherpad.opendev.org/p/apr2021-ptg-large-scale See you there! [1] http://ptg.openstack.org/ptg.html [2] https://www.openstack.org/ptg/ Regards, -- Thierry Carrez

1 1

[ironic] Ironic Whiteboard v2 call for reviews
by Jay Faulkner 23 Apr '21

23 Apr '21

Hi all, Iury and I spent some time this morning updating the Ironic whiteboard etherpad to include more immediately useful information to contributors. We placed this updated whiteboard at https://etherpad.opendev.org/p/IronicWhiteBoardv2 -- our approach was to prune any outdated/broken links or information, and focus on making the first part of the whiteboard an easy one-click place for folks to see easy ways to contribute. All the rest of the information was carried over and reformatted. Once there is consensus from the team about this being a positive change, we should either replace the existing IronicWhiteBoard with the contents of the v2 page, or just update links to point to the new one instead. What do you all think? Thanks, Jay Faulkner

4 6

Placement service error on one of the controller nodes
by Shalabh Goel 23 Apr '21

23 Apr '21

Hi, I am setting up an Openstack environment with 2 controller nodes. I have installed placement service on both by following the steps from https://docs.openstack.org/placement/victoria/install/install-ubuntu.html#c… My first node is 192.168.2.14 and second is 192.168.2.15 with the virtual IP as 192.168.2.100 on which haproxy is used for listening. After restarting apache2 service, placement service is running on one first node ( 192.168.2.14) but is giving the following error on second one ( 192.168.2.15): 2021-04-23 10:39:03.314524 2021-04-23 10:39:03.314 8299 WARNING placement.db_api [-] TransactionFactory already started, not reconfiguring.\x1b[00m 2021-04-23 10:39:03.322774 2021-04-23 10:39:03.322 8299 WARNING keystonemiddleware.auth_token [-] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Pl ease set this to True.\x1b[00m 2021-04-23 10:39:03.391538 2021-04-23 10:39:03.391 8299 WARNING keystonemiddleware.auth_token [-] Configuring www_authenticat e_uri to point to the public identity endpoint is required; clients may not be able to authenticate against an admin endpoint \x1b[00m 2021-04-23 10:39:03.394729 mod_wsgi (pid=8299): Failed to exec Python script file '/usr/bin/placement-api'. 2021-04-23 10:39:03.394771 mod_wsgi (pid=8299): Exception occurred processing WSGI script '/usr/bin/placement-api'. The second issue is that I am not able to use openstack compute command. It throws authentication error but I am able to use other openstack commands. I found this line on placement-api log in apache directory 2021-04-23 10:46:08.450216 2021-04-23 10:46:08.449 1421 WARNING keystonemiddleware.auth_token [req-f17428d0-183f-4e3d-8343-74b04dad7944 - - - - -] Authorization failed for token: keystonemiddleware.auth_token._exceptions.InvalidToken\x1b[00 How can I solve these issues. Are any other details needed? Thanks -- Shalabh Goel

1 0

Regarding whether sushy will support etag
by hus.fnst＠fujitsu.com 23 Apr '21

23 Apr '21

Dear maintainers: Hello, I am Hu Shuai from FNST. I am sending this email to know if sushy<https://opendev.org/openstack/sushy> will support etag<http://redfish.dmtf.org/schemas/DSP0266_1.11.0.html#etags>. For now sushy does not support etag. However etag is useful for reducing network data and redfish dmtf organization also recommends redfish to support etag. In addition, I raised an issue<https://storyboard.openstack.org/#!/story/2008810> about this question before but I have not received a reply. Thanks for your reading and I am looking forward to your opinions about this question. Best regards! Hu Shuai

1 0

Diversity & Inclusion Social Hour at the PTG sponsored by RDO
by Kendall Waters 22 Apr '21

22 Apr '21

Hey everyone, On behalf of the RDO Community, please join us for an hour of Trivia on Thursday April 22 at 17:00 UTC. We will have trivia related to OpenStack and the other OIF projects as well as the cities we've held events. Time permitting we'll have some Pop Culture trivia as well. Prizes for the first 3 placings and registration is Free! https://eventyay.com/e/5f05de57 <https://eventyay.com/e/5f05de57> Cheers, Kendall Kendall Waters Perez Community Partnerships Manager Open Infrastructure Foundation

1 0

RE: [kolla] VM build fails after Train-Ussuri upgrade
by Braden, Albert 22 Apr '21

22 Apr '21

Can anyone help with this upgrade issue? From: Braden, Albert Sent: Monday, April 19, 2021 8:20 AM To: openstack-discuss(a)lists.openstack.org Subject: [kolla] VM build fails after Train-Ussuri upgrade I upgraded my Train test cluster to Ussuri following these instructions: OpenStack Docs: Operating Kolla<https://docs.openstack.org/kolla-ansible/latest/user/operating-kolla.html#u…> The upgrade completed successfully with no failures, and the existing VMs are fine, but new VM build fails with rados.Rados.connect\nrados.PermissionDeniedError: Ubuntu Pastebin<https://paste.ubuntu.com/p/MJhzgjYbW8/> I'm running external ceph so I looked at this document: OpenStack Docs: External Ceph<https://docs.openstack.org/kolla-ansible/latest/reference/storage/external-…> It says that I need the following in /etc/kolla/config/glance/ceph.conf: auth_cluster_required = cephx auth_service_required = cephx auth_client_required = cephx I didn't have that, so I added it and then redeployed, but still can't build VMs. I tried adding the same to all copies of ceph.conf and redeployed again, but that didn't help. Does anything else need to change in my ceph config when upgrading from Train to Ussuri? I see some cryptic talk about ceph in the release notes but it's not obvious what I'm being asked to change: OpenStack Docs: Ussuri Series Release Notes<https://docs.openstack.org/releasenotes/kolla-ansible/ussuri.html#relnotes-…> I read the bug that it refers to: Bug #1904062 "external ceph cinder volume config breaks volumes ..." : Bugs : kolla-ansible (launchpad.net)<https://bugs.launchpad.net/kolla-ansible/+bug/1904062> But I already have "backend_host=rbd:volumes" so I don't think I'm hitting that. Also I read these sections but I don't see anything obvious here that needs to be changed: * For cinder (cinder-volume and cinder-backup), glance-api and manila keyrings behavior has changed and Kolla Ansible deployment will not copy those keys using wildcards (ceph.*), instead will use newly introduced variables. Your environment may render unusable after an upgrade if your keys in /etc/kolla/config do not match default values for introduced variables. * The default behavior for generating the cinder.conf template has changed. An rbd-1 section will be generated when external Ceph functionality is used, i.e. cinder_backend_ceph is set to true. Previously it was only included when Kolla Ansible internal Ceph deployment mechanism was used. * The rbd section of nova.conf for nova-compute is now generated when nova_backend is set to "rbd". Previously it was only generated when both enable_ceph was "yes" and nova_backend was set to "rbd". My ceph keys have the default name and are in the default locations. I have cinder_backend_ceph: "yes". I don't have a nova_backend setting but I have nova_backend_ceph: "yes" I added nova_backend: "rbd" and redeployed and now I get a different error: rados.Rados.connect\nrados.ObjectNotFound Ubuntu Pastebin<https://paste.ubuntu.com/p/2kdKCW7npw/> I apologize for the nonsense below. I have not been able to stop it from being attached to my external emails. E-MAIL CONFIDENTIALITY NOTICE: The contents of this e-mail message and any attachments are intended solely for the addressee(s) and may contain confidential and/or legally privileged information. If you are not the intended recipient of this message or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message and any attachments. If you are not the intended recipient, you are notified that any use, dissemination, distribution, copying, or storage of this message or any attachment is strictly prohibited.

1 0

[nova][placement] introducing review priority label in gerrit
by Balazs Gibizer 22 Apr '21

22 Apr '21

Hi, As we discussed yesterday in the retro we would like to start using the review priority label in gerrit as a replacement of the runway process. Sean proposed the project config changes for this[1]. I added couple of questions / suggestions to that patch to start a discussion about the process. Let's try to agree in the review. Then I will document the process in tree. Cheers, gibi [1] https://review.opendev.org/c/openstack/project-config/+/787523

1 0

unable to access internet in instance
by cloud learner 22 Apr '21

22 Apr '21

Dear All, I have installed rocky on centos 7, as documented at openstack with 2 node controller and compute nodes, as mentioned in the document used vxlan and verified all the steps as mentioned in the document and all things are working fine but i am unable to access the internet in instances. kindly help me sort out this issue. Thanks

2 1

RE: cinder + Unity
by Huang, Yong 22 Apr '21

22 Apr '21

Hi Albert, Could you execute the `cinder get-pools` command to check if Unity driver report the valid pools correctly? the output should be: -------------------------------------------------- stack@ubuntu-xenial:/opt/stack/cinder$ cinder get-pools +----------+--------------------------------+ | Property | Value | +----------+--------------------------------+ | name | ubuntu-xenial@unity#Flash_Pool | +----------+--------------------------------+ +----------+---------------------------------+ | Property | Value | +----------+---------------------------------+ | name | ubuntu-xenial@unity#Manila_Pool | +----------+---------------------------------+ +----------+---------------------------------+ | Property | Value | +----------+---------------------------------+ | name | ubuntu-xenial@unity#Cinder_Pool | +----------+---------------------------------+ -------------------------------------------------- If no valid pools, one possibility is Unity driver not initialized successfully, if the driver initialized successfully, there should be a log in cinder-volume.log like: -------------------------------------------------- Apr 21 03:20:07 ubuntu-xenial cinder-volume[29607]: INFO cinder.volume.manager [None req-4b345a29-0d78-4cf7-8bae-ae541a48aaf3 None None] Driver post RPC initialization completed successfully. -------------------------------------------------- Did you install the storops library which Unity driver relies on? Please check the version info of storops: -------------------------------------------------- stack@ubuntu-xenial:/opt/stack/cinder$ pip show storops Name: storops Version: 1.2.8 Summary: Python API for VNX and Unity. Home-page: https://github.com/emc-openstack/storops Author: Cedric Zhuang Author-email: cedric.zhuang(a)gmail.com<mailto:cedric.zhuang@gmail.com> License: Apache Software License Location: /usr/local/lib/python2.7/dist-packages Requires: requests, python-dateutil, persist-queue, cachez, bitmath, enum34, six, PyYAML, retryz -------------------------------------------------- Thanks Yong Huang [EXTERNAL EMAIL] Hi Albert, On Mon, Apr 19, 2021 at 11:45 PM Albert Shih <Albert.Shih(a)obspm.fr<mailto:Albert.Shih@obspm.fr>> wrote: Hi everyone, I'm a total newbie with openstack, currently I'm trying to put a POC with a Unity storage element, 4 computes, and few servers (cinder, keystone, glance, neutron, nova, placement and horizon). I think my keystone, glance, placement are working (at least they past the test). Currently I'm trying to make cinder working with my Unity (480), the objectif are to use iSCSI. Here the configuration of my /etc/cinder/cinder.conf [DEFAULT] rootwrap_config = /etc/cinder/rootwrap.conf api_paste_confg = /etc/cinder/api-paste.ini iscsi_helper = tgtadm volume_name_template = volume-%s volume_group = cinder-volumes verbose = True auth_strategy = keystone state_path = /var/lib/cinder lock_path = /var/lock/cinder volumes_dir = /var/lib/cinder/volumes enabled_backends = unity transport_url = rabbit://openstack:XXXXXX@amqp-cloud.private.FQDN/openstack auth_strategy = keystone debug = True verbose = True [database] connection = mysql+pymysql://cinder:XXXXXXX@mariadb-cloud.private.FQDN/cinder [keystone_authtoken] www_authenticate_uri = http://keystone.private.FQDN:5000/v3 [keystone.private.fqdn]<https://urldefense.com/v3/__http:/keystone.private.FQDN:5000/v3__;!!LpKI!x3…> auth_url = http://keystone.private.FQDN:5000 [keystone.private.fqdn]<https://urldefense.com/v3/__http:/keystone.private.FQDN:5000__;!!LpKI!x37Ut…> identity_uri = http://keystone.private.FQDN:5000 [keystone.private.fqdn]<https://urldefense.com/v3/__http:/keystone.private.FQDN:5000__;!!LpKI!x37Ut…> memcached_servers = memcached-cloud.private.FQDN:11211 auth_type = password project_domain_name = default user_domain_name = default project_name = service username = cinder password = XXXXXX [oslo_concurrency] lock_path = /var/lib/cinder/tmp [unity] # Storage protocol storage_protocol = iSCSI # Unisphere IP san_ip = onering-remote.FQDN # Unisphere username and password san_login = openstack san_password = "XXXXX" # Volume driver name volume_driver = cinder.volume.drivers.dell_emc.unity.Driver # backend's name volume_backend_name = Unitiy_ISCSI This might be something to look at with the wrong spelling causing mismatch. unity_io_ports = *_enp1s0 unity_storage_pool_names = onering When I'm trying to create a storage through a openstack volume create volumetest --type thick_volume_type --size 100 I don't even see (with tcpdump) the cinder server trying to connect to onering-remote.FQDN Inside my /var/log/cinder/cinder-scheduler.log I have 2021-04-19 18:06:56.805 21315 INFO cinder.scheduler.base_filter [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee b1d58ebae6b84f7586ad63b94203d7ae - - -] Filtering removed all hosts for the request with volume ID '06e5f07d-766f-4d07-b3bf-6153a2cf6abd'. Filter results: AvailabilityZoneFilter: (start: 0, end: 0), CapacityFilter: (start: 0, end: 0), CapabilitiesFilter: (start: 0, end: 0) This log mentions that no host is valid to pass the 3 filters in the scheduler. 2021-04-19 18:06:56.806 21315 WARNING cinder.scheduler.filter_scheduler [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee b1d58ebae6b84f7586ad63b94203d7ae - - -] No weighed backend found for volume with properties: {'id': '5f16fc1f-76ff-41ee-8927-56925cf7b00f', 'name': 'thick_volume_type', 'description': None, 'is_public': True, 'projects': [], 'extra_specs': {'provisioning:type': 'thick', 'thick_provisioning_support': 'True'}, 'qos_specs_id': None, 'created_at': '2021-04-19T15:07:09.000000', 'updated_at': None, 'deleted_at': None, 'deleted': False} 2021-04-19 18:06:56.806 21315 INFO cinder.message.api [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee b1d58ebae6b84f7586ad63b94203d7ae - - -] Creating message record for request_id = req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 2021-04-19 18:06:56.811 21315 ERROR cinder.scheduler.flows.create_volume [req-4808cc9d-b9c3-44cb-8cae-7503db0b0256 f5e5c9ea20064b17851f07c276d71aee b1d58ebae6b84f7586ad63b94203d7ae - - -] Failed to run task cinder.scheduler.flows.create_volume.ScheduleCreateVolumeTask;volume:create: No valid backend was found. No weighed backends available: cinder.exception.NoValidBackend: No valid backend was found. No weighed backends available It seem (for me) cinder don't try to use unity.... The cinder-volume service is responsible for communicating with the backend and this create request fails on scheduler only, hence no sign of it. Any help ? Regards Looking at the scheduler logs, there are a few things you can check: 1) execute ``cinder-manage service list`` command and check the status of cinder-volume service if it's active or not. If it shows an X sign then check in cinder-volume logs for any startup failure. 2) Check the volume type properties and see if ``volume_backend_name`` is set to the right value i.e. Unitiy_ISCSI (which looks suspicious because the spelling is wrong and there might be a mismatch somewhere) Also it's good to mention the openstack version you're using since the code changes every cycle and it's hard to track the issues with every release. Thanks and regards Rajat Dhasmana -- Albert SHIH Observatoire de Paris Heure local/Local time: Mon Apr 19 08:01:37 PM CEST 2021

1 0