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

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

27 Oct '20

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

2 1

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

27 Oct '20

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

2 1

Help about openstack Storlets
by ghasemir 27 Oct '20

27 Oct '20

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

2 1

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

27 Oct '20

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

4 6

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

27 Oct '20

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

1 0

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

27 Oct '20

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

1 0

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

26 Oct '20

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

1 0

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

26 Oct '20

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

3 2

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

26 Oct '20

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

1 0

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

26 Oct '20

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

1 0

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

26 Oct '20

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

1 0

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

26 Oct '20

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

3 3

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

26 Oct '20

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

1 0

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

26 Oct '20

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

2 1

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

26 Oct '20

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

1 2

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

25 Oct '20

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

2 2

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

25 Oct '20

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

1 0

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

25 Oct '20

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

2 3

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

24 Oct '20

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

1 0

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

24 Oct '20

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

1 0

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

24 Oct '20

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

1 0

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

24 Oct '20

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

1 1

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

24 Oct '20

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

2 1

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

24 Oct '20

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

2 2

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

24 Oct '20

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

1 0