December 2020 - openstack-discuss

[tripleo] next meeting Tuesday Dec 08 @ 1400 UTC in #tripleo
by Marios Andreou 03 Dec '20

03 Dec '20

The next scheduled TripleO irc meeting is ** Tuesday 08th December at 1400 UTC in #tripleo. ** ** https://etherpad.opendev.org/p/tripleo-meeting-items ** Please add anything you want to raise at https://etherpad.opendev.org/p/tripleo-meeting-items This could be anything including review requests, blocking issues or to socialise ongoing or planned work. Our last meeting was held on Nov 24th - you can find the logs there http://eavesdrop.openstack.org/meetings/tripleo/2020/tripleo.2020-11-24-14.… thanks, marios

1 0

[ussuri] [neutron] deploy an additional compute node that resides in a different network
by Pavlos Basaras 03 Dec '20

03 Dec '20

1 1

[neutron] Drivers meeting agenda for 04.12.2020
by Slawek Kaplonski 03 Dec '20

03 Dec '20

Hi, Agenda for drivers meeting [1] this week have to new RFEs to discuss: * https://bugs.launchpad.net/neutron/+bug/1905115 * https://bugs.launchpad.net/neutron/+bug/1905295 And there is also "on demand" topic added by Rodolfo: "Smart-Nic Management Overall Design" (Nova spec). Neutron needs to add a new extension to provide to Nova the device profile information. This is a new string parameter added to the port blob and should be included when the port is created. Reference: https://review.opendev.org/c/openstack/nova-specs/+/742785/12/specs/wallaby… Rodolfo - is Your topic related to the RFE https://bugs.launchpad.net/neutron/+bug/1906602 ? See You tomorrow on the meeting :) [1] https://wiki.openstack.org/wiki/Meetings/NeutronDrivers#Agenda -- Slawek Kaplonski Principal Software Engineer Red Hat

2 1

Re: [all] Dynamic Zuul results table in Gerrit 3
by Radosław Piliszek 03 Dec '20

03 Dec '20

On Thu, Dec 3, 2020 at 10:33 AM Marcin Juszkiewicz <marcin.juszkiewicz(a)linaro.org> wrote: > > W dniu 03.12.2020 o 10:22, Radosław Piliszek pisze: > > Hello Fellow OpenStack and OpenDev Folks! > > > > TL;DR click on [3] and enjoy. > > Rename to *.user.js so Tampermonkey will recognize it as userscript and > add window around with Install button. > I, personally, hate this "feature" of Tampermonkey but sure - if it makes it easier for you. ;-) Done. Anyone - just click on "Raw" and you will be pestered by Tampermonkey to install the script. > > 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. > > Firefox with Tampermonkey - script works. > Yay, thanks for confirming! > > I hope you will enjoy this little helper (I do). > > Nice job! > Well, thank you! :-) > It does not catch all Zuul jobs. For Kolla patches AArch64 jobs are not > listed. I have already replied on IRC but will repeat here for others. The dynamic part includes all the running queues. However, the static part parses only a single comment and AArch64 is in a different one. I am obviously biased (being x86-only folk) but I find it more problematic than worth it to hack it any further. I hope a proper solution arrives sooner. :-) > > 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. > > YW. > -yoctozepto

1 0

[CLOUDKITTY] - Prometheus metrics.yml sample?
by Gaël THEROND 02 Dec '20

02 Dec '20

Hi everyone, I'm currently finishing our cloudkitty implementation, but I'm facing an issue. For now, our cloudkitty-processor process raise a traceback like this: http://paste.openstack.org/show/Y2ZiYPtZSKzvZk93yNWC/ I can't find any reliable documentation describing how to use prometheus with cloudkitty, so I'm kind of using the guess/read the code way to integrate it, but I'm a bit confused so far. My current metric.yml look like this: http://paste.openstack.org/show/6X23ZfVm1iDMruGy3Gpp/ I've created the appropriate group/service/threshold etc but it still continues to raise the same error. I'm using this openstack_exporter: https://github.com/openstack-exporter/openstack-exporter/releases/tag/v1.1.0 I'm running a Train release Openstack platform if it can help. So, if anyone is having a successful cloudkitty/prometheus integration willing to give a hand, I'll be more than happy ;-) Thanks!

1 0

[largescale-sig] Next meeting: December 2, 15utc
by Thierry Carrez 02 Dec '20

02 Dec '20

Hi everyone, We'll have a Large Scale SIG meeting this Wednesday in #openstack-meeting-3 on IRC, at 15UTC. You can doublecheck how it translates locally at: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20201202T15 Our main topic will be to discuss how to best collect operator scaling experiences. Feel free to add other topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting Talk to you all later, -- Thierry Carrez

1 1

IRONIC BAREMETAL partitioned image not spawning.
by Akshay 346 02 Dec '20

02 Dec '20

Hello Team, I hope you all are keeping safe and doing good. I have a OpenStack setup up and running with ironic enabled. I am able to spawn a bare metal node with centos8.2 whole-disk image but when I spawn bare metal with partitioned image, it fails to spawn it stating the following trace ( Full trace back attached in the email): "2020-12-01 12:35:34.603 1 ERROR ironic.conductor.utils [req-0d3a375e-90a3-485d-a7c3-895c97c88006 - - - - -] Deploy failed for instance 463bd844-7f80-4c57-98dd-6ca8cfdb6121. Error: [Errno 2] No such file or directory: 'sgdisk': 'sgdisk': FileNotFoundError: [Errno 2] No such file or directory: 'sgdisk': 'sgdisk'". I have also installed sgdisk (yum install gdisk) on the qcow2 from which I build the partitioned image. Can anyone please guide how to debug it? Regards Akshay DISCLAIMER: This electronic message and all of its contents, contains information which is privileged, confidential or otherwise protected from disclosure. The information contained in this electronic mail transmission is intended for use only by the individual or entity to which it is addressed. If you are not the intended recipient or may have received this electronic mail transmission in error, please notify the sender immediately and delete / destroy all copies of this electronic mail transmission without disclosing, copying, distributing, forwarding, printing or retaining any part of it. Hughes Systique accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus.

2 4

[kolla] cannot pull docker public hub images
by Adrian Andreias 02 Dec '20

02 Dec '20

Hi, None of the Kolla images on the Docker public registry are tagged. E.g. https://hub.docker.com/r/kolla/centos-source-nova-api Images don't even have the "latest" tag, though they were updated 15 hours ago. And therefore they can't be pulled: $ docker pull kolla/centos-source-nova-api Using default tag: latest Error response from daemon: manifest for kolla/centos-source-nova-api:latest not found: manifest unknown: manifest unknown Is there another public registry where ready-built Kolla images are available? Thanks Regards, Adrian Andreias https://fleio.com

4 6

Re: [neutron][openstack-ansible] Instances can only connect to provider-net via tenant-net but not directly
by Oliver Wenz 02 Dec '20

02 Dec '20

> Neutron sends this notification to the nova-api so You should check in nova-api > logs. > Whole workflow for that process of spawning vm is more or less like below: > 1. nova-compute asks neutron for port, > 2. neutron creates port and binds it with some mechanism driver - so it has > vif_type e.g. "ovs" or "linuxbridge" or some other, > 3. nova, based on that vif details plugs port to the proper bridge on host and > pauses instance until neutron will not do its job, > 4. neutron-l2-agent (linuxbrige or ovs) starts provisioning port and reports > to neutron-server when it is done, > 5. if there is no any provisioning blocks for that port in neutron db (can be > also one from the dhcp agent), neutron sends notification to nova-api that port > is ready, > 6. nova unpauses vm. > > In Your case it seems that on step 5 nova reports some error and that You > should IMO check. > Hi Slawek, thanks for the information and suggestion! I checked the nova-api-os-compute logs and it seems like there are network problems and an issue with wrong token scope: Dec 02 11:15:49 infra1-nova-api-container-83af52a6 nova-api-wsgi[84]: 2020-12-02 11:15:49.074 84 INFO nova.api.openstack.requestlog [req-1d56ad1c-03ea-4dcc-b9da-e4f6e73ccc52 920e739127a14018a55fb4422b0885e7 0f14905dab5546e0adec2b56c0f6be88 - default default] 192.168.110.201 "GET /v2.1/servers/2a1f6fbf-48f8-4e7f-bc36-7162bdaf7e20" status: 200 len: 1358 microversion: 2.1 time: 0.500669 Dec 02 11:15:49 infra1-nova-api-container-83af52a6 nova-api-wsgi[86]: 2020-12-02 11:15:49.256 86 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: [Errno 104] Connection reset by peer Dec 02 11:15:49 infra1-nova-api-container-83af52a6 uwsgi[48]: Wed Dec 2 11:15:49 2020 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /v2.1/flavors/7c20746e-f6db-4344-9aa1-be926696ecf4 (ip 192.168.110.201) !!! Dec 02 11:15:49 infra1-nova-api-container-83af52a6 nova-api-wsgi[86]: 2020-12-02 11:15:49.318 86 INFO nova.api.openstack.requestlog [req-832f794d-db9b-4690-bb0c-8320e7beed47 920e739127a14018a55fb4422b0885e7 0f14905dab5546e0adec2b56c0f6be88 - default default] 192.168.110.201 "GET /v2.1/flavors/7c20746e-f6db-4344-9aa1-be926696ecf4" status: 200 len: 473 microversion: 2.1 time: 0.095833 Dec 02 11:15:57 infra1-nova-api-container-83af52a6 nova-api-wsgi[79]: 2020-12-02 11:15:57.000 79 INFO nova.api.openstack.requestlog [req-2c061260-88f4-4183-a74a-ea59d1ff1ae0 b044fe42a4644837a3bd40beec378876 226e9c9f1fb94c8ab271490ad79c6873 - default default] 192.168.110.201 "HEAD /" status: 200 len: 417 microversion: - time: 0.001837 Dec 02 11:15:57 infra1-nova-api-container-83af52a6 nova-api-wsgi[88]: 2020-12-02 11:15:57.214 88 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: [Errno 104] Connection reset by peer Dec 02 11:15:57 infra1-nova-api-container-83af52a6 uwsgi[48]: Wed Dec 2 11:15:57 2020 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /v2.1/os-server-external-events (ip 192.168.110.201) !!! Dec 02 11:15:57 infra1-nova-api-container-83af52a6 uwsgi[48]: /openstack/venvs/nova-21.1.0/lib/python3.6/site-packages/oslo_policy/policy.py:1007: UserWarning: Policy os_compute_api:os-server-external-events:create failed scope check. The token used to make the request was project scoped but the policy requires ['system'] scope. This behavior may change in the future where using the intended scope is required Dec 02 11:15:57 infra1-nova-api-container-83af52a6 uwsgi[48]: warnings.warn(msg) Dec 02 11:15:57 infra1-nova-api-container-83af52a6 nova-api-wsgi[88]: 2020-12-02 11:15:57.715 88 INFO nova.api.openstack.compute.server_external_events [req-759c5752-c80b-46f2-b3df-0fa126605895 d9a2e96567ec4670bc60dbcc8f66305f 474b7aa9b7894d6782402135c6ef4c2a - default default] Creating event network-changed:ed4a9455-a33c-454c-b74f-b314751cce3d for instance 2a1f6fbf-48f8-4e7f-bc36-7162bdaf7e20 on bc1blade15 Dec 02 11:15:57 infra1-nova-api-container-83af52a6 nova-api-wsgi[88]: 2020-12-02 11:15:57.734 88 INFO nova.api.openstack.requestlog [req-759c5752-c80b-46f2-b3df-0fa126605895 d9a2e96567ec4670bc60dbcc8f66305f 474b7aa9b7894d6782402135c6ef4c2a - default default] 192.168.110.201 "POST /v2.1/os-server-external-events" status: 200 len: 179 microversion: 2.1 time: 0.533910 Dec 02 11:16:09 infra1-nova-api-container-83af52a6 nova-api-wsgi[82]: 2020-12-02 11:16:09.007 82 INFO nova.api.openstack.requestlog [req-064600c9-196e-4388-978c-00b0f5560b2e 745ecbee83d041c6ba92f9e07ba744d5 a2fd11a3bfdd47c8893e18a6f3b7dfa3 - default default] 192.168.110.201 "HEAD /" status: 200 len: 417 microversion: - time: 0.001638 Dec 02 11:16:16 infra1-nova-api-container-83af52a6 nova-api-wsgi[77]: 2020-12-02 11:16:16.432 77 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: [Errno 104] Connection reset by peer Dec 02 11:16:16 infra1-nova-api-container-83af52a6 uwsgi[48]: Wed Dec 2 11:16:16 2020 - SIGPIPE: writing to a closed pipe/socket/fd (probably the client disconnected) on request /v2.1/os-server-external-events (ip 192.168.110.201) !!! Dec 02 11:16:16 infra1-nova-api-container-83af52a6 uwsgi[48]: /openstack/venvs/nova-21.1.0/lib/python3.6/site-packages/oslo_policy/policy.py:1007: UserWarning: Policy os_compute_api:os-server-external-events:create failed scope check. The token used to make the request was project scoped but the policy requires ['system'] scope. This behavior may change in the future where using the intended scope is required Dec 02 11:16:16 infra1-nova-api-container-83af52a6 uwsgi[48]: warnings.warn(msg) Dec 02 11:16:16 infra1-nova-api-container-83af52a6 nova-api-wsgi[77]: 2020-12-02 11:16:16.939 77 INFO nova.api.openstack.compute.server_external_events [req-71a40ea1-cf64-46d5-9675-d00d539f1922 d9a2e96567ec4670bc60dbcc8f66305f 474b7aa9b7894d6782402135c6ef4c2a - default default] Creating event network-vif-plugged:5cbc8608-8545-4eb3-a745-23ca912347ec for instance ea72988b-83eb-4640-adaa-e24e0c3d018d on bc1blade15 Dec 02 11:16:16 infra1-nova-api-container-83af52a6 nova-api-wsgi[77]: 2020-12-02 11:16:16.958 77 INFO nova.api.openstack.requestlog [req-71a40ea1-cf64-46d5-9675-d00d539f1922 d9a2e96567ec4670bc60dbcc8f66305f 474b7aa9b7894d6782402135c6ef4c2a - default default] 192.168.110.201 "POST /v2.1/os-server-external-events" status: 200 len: 183 microversion: 2.1 time: 0.526920 Dec 02 11:16:17 infra1-nova-api-container-83af52a6 nova-api-wsgi[71]: 2020-12-02 11:16:17.422 71 INFO oslo.messaging._drivers.impl_rabbit [-] A recoverable connection/channel error occurred, trying to reconnect: [Errno 104] Connection reset by peer Kind regards, Oliver

2 1

[Openstack][CFP] Virtualization & IaaS Devroom
by Piotr Kliczewski 02 Dec '20

02 Dec '20

We are excited to announce that the call for proposals is now open for the Virtualization & IaaS devroom at the upcoming FOSDEM 2021, to be hosted virtually on February 6th 2021. This year will mark FOSDEM’s 21th anniversary as one of the longest-running free and open source software developer events, attracting thousands of developers and users from all over the world. Due to Covid-19, FOSDEM will be held virtually this year on February 6th & 7th, 2021. About the Devroom The Virtualization & IaaS devroom will feature session topics such as open source hypervisors and virtual machine managers such as Xen Project, KVM, bhyve, and VirtualBox, and Infrastructure-as-a-Service projects such as KubeVirt, Apache CloudStack, Foreman, OpenStack, oVirt, QEMU and OpenNebula. This devroom will host presentations that focus on topics of shared interest, such as KVM; libvirt; shared storage; virtualized networking; cloud security; clustering and high availability; interfacing with multiple hypervisors; hyperconverged deployments; and scaling across hundreds or thousands of servers. Presentations in this devroom will be aimed at users or developers working on these platforms who are looking to collaborate and improve shared infrastructure or solve common problems. We seek topics that encourage dialog between projects and continued work post-FOSDEM. Important Dates Submission deadline: 20th of December Acceptance notifications: 25th of December Final schedule announcement: 31st of December Recorded presentations upload deadline: 15th of January Devroom: 6th February 2021 Submit Your Proposal All submissions must be made via the Pentabarf event planning site[1]. If you have not used Pentabarf before, you will need to create an account. If you submitted proposals for FOSDEM in previous years, you can use your existing account. After creating the account, select Create Event to start the submission process. Make sure to select Virtualization and IaaS devroom from the Track list. Please fill out all the required fields, and provide a meaningful abstract and description of your proposed session. Submission Guidelines We expect more proposals than we can possibly accept, so it is vitally important that you submit your proposal on or before the deadline. Late submissions are unlikely to be considered. All presentation slots are 30 minutes, with 20 minutes planned for presentations, and 10 minutes for Q&A. All presentations will need to be pre-recorded and put into our system at least a couple of weeks before the event. The presentations should be uploaded by 15th of January and made available under Creative Commons licenses. In the Submission notes field, please indicate that you agree that your presentation will be licensed under the CC-By-SA-4.0 or CC-By-4.0 license and that you agree to have your presentation recorded. For example: "If my presentation is accepted for FOSDEM, I hereby agree to license all recordings, slides, and other associated materials under the Creative Commons Attribution Share-Alike 4.0 International License. Sincerely, <NAME>." In the Submission notes field, please also confirm that if your talk is accepted, you will be able to attend the virtual FOSDEM event for the Q&A. We will not consider proposals from prospective speakers who are unsure whether they will be able to attend the FOSDEM virtual event. If you are experiencing problems with Pentabarf, the proposal submission interface, or have other questions, you can email our devroom mailing list[2] and we will try to help you. Code of Conduct Following the release of the updated code of conduct for FOSDEM, we'd like to remind all speakers and attendees that all of the presentations and discussions in our devroom are held under the guidelines set in the CoC and we expect attendees, speakers, and volunteers to follow the CoC at all times. If you submit a proposal and it is accepted, you will be required to confirm that you accept the FOSDEM CoC. If you have any questions about the CoC or wish to have one of the devroom organizers review your presentation slides or any other content for CoC compliance, please email us and we will do our best to assist you. Call for Volunteers We are also looking for volunteers to help run the devroom. We need assistance with helping speakers to record the presentation as well as helping with streaming and chat moderation for the devroom. Please contact devroom mailing list [2] for more information. Questions? If you have any questions about this devroom, please send your questions to our devroom mailing list. You can also subscribe to the list to receive updates about important dates, session announcements, and to connect with other attendees. See you all at FOSDEM! [1] <https://penta.fosdem.org/submission/FOSDEM17>https://penta.fosdem .org/submission/FOSDEM21 [2] iaas-virt-devroom at lists.fosdem.org

2 1