August 2020 - openstack-discuss - lists.openstack.org

[nova][ops] Live migration and CPU features
by Belmiro Moreira 21 Aug '20

21 Aug '20

Hi, in our infrastructure we have always compute nodes that need a hardware intervention and as a consequence they are rebooted, bringing a new kernel, kvm, ... In order to have a good compromise between performance and flexibility (live migration) we have been using "host-model" for the "cpu_mode" configuration of our service VMs. We didn't expect to have CPU compatibility issues because we have the same hardware type per cell. The problem is that when a compute node is rebooted the instance domain is recreated with the new cpu features that were introduced because of the reboot (using centOS). If there are new CPU features exposed, this basically blocks live migration to all the non rebooted compute nodes (those cpu features are not exposed, yet). The nova-scheduler doesn't know about them when scheduling the live migration destination. I wonder how other operators are solving this issue. I don't like stopping OS upgrades. What I'm considering is to define a "custom" cpu_mode for each hardware type. I would appreciate your comments and learn how you are solving this problem. Belmiro

5 6

[glance][horizon][ops] Dashboard show Forbidden 403 but openstack cli works fine
by Amjad Kotobi 21 Aug '20

21 Aug '20

Hi, We are running Train release, currently facing below error when change to “Images” panel on the project which I have “User” role. The image is visibility is public. Error: Forbidden. Insufficient permissions of the requested operation Error: Unable to retrieve the project. By using openstack-cli everything works and I do not face “Forbidden” 403, but in dashboard “access.log” it shows "GET /dashboard/api/keystone/projects/7331defd55ef479fbf0a9a1ac3fe9055 HTTP/1.1” 403 http://xxxxxx/dashboard/project/images” I checked: 1. glance: policy.json from both dashboard and api/registry hosts are same. 2. From dashboard API images is 2 As soon as I change the OWNER of image to the project which my role = USER the error disappears. Any ideas or previous encounter similar to this issue? Thanks Amjad

1 0

Using os_token
by Eric K. Miller 21 Aug '20

21 Aug '20

Hi, It looks like the OS_TOKEN environment variable can be set so a token can be re-used instead of a new authentication for each CLI command with the OpenStack Client. I'm a little confused as to how this works and haven't found any good documentation on the subject. I would have expected to be able to: 0) set appropriate OS_* variables for password authentication 1) create a token using "openstack token issue" 2) unset all OS_* environment variables 3) set OS_TOKEN to the token's value provided in #1 4) set OS_AUTH_TYPE to "v3token" 5) set OS_AUTH_URL to the respective KeyStone endpoint 6) set OS_IDENTITY_API_VERSION to "3" 7) use the CLI as normal However, I get a "The service catalog is empty." message. Maybe I'm missing something above or am I completely misunderstanding the purpose of the OS_TOKEN variable? >From examples I have seen, it looks like the token can be used in a REST API call. Is there a way to use an existing token with the CLI, instead, so a new token is not issued for every CLI command instantiation? Thanks! Eric

1 0

Re: [requirements][oslo] Inclusion of CONFspirator in openstack/requirements
by Adrian Turjak 21 Aug '20

21 Aug '20

On 21/08/20 9:16 am, Ben Nemec wrote: > > In general, given the complexity of what you're talking about I think > a driver plugin would be the way to go, as opposed to trying to fit > this all in with the core oslo.config functionality (assuming you/we > decide to pursue integrating at all). > > There were a few other things you mentioned as features of the > library. The following are some off-the-cuff thoughts without having > looked too closely at the library, so if they're nonsense that's my > excuse. > > "because I have plugins that need to dynamically load config on > startup, which then has to be lazy_loaded" > > Something like this could probably be done. I believe this is kind of > how the castellan driver in oslo.config works. Config values are > looked up and cached on-demand, as opposed to all at once. This one is a little weird, but essentially the way this works this in Adjutant: I load the config so I can start the app and go through base logic and loading plugins, but the config groups that are pulled from plugins aren't added to my config group tree until AFTER the config has already been loaded. So part of the config is usable, but some hasn't yet fully been loaded until after the plugins are done, and then that subtree will lazy_load itself when first accessed. It means that until a given lazy_loaded group is actually accessed as config, the config tree underneath it can still have config options added. It's likely not too crazy to do this in oslo, and have groups only read from the cached source (loaded file dict) when first accessed. > > "I also have weird overlay logic for defaults that can be overridden" > > My knee-jerk reaction to this is that oslo.config already supports > overriding defaults, so I assume there's something about your use case > that didn't mesh with that functionality? Or is this part of > oslo.config that you reused? Sooo, this one is a little special because what this feature lets you do is take any group in the config tree once loaded, and call the overlay function on it with either a dict, or another group. The returned value will be a deep copy of the config tree with the values present in the given dict/group overlaid on that original group. As in a depth first dict update, where only keys that exist on the overriding dict will be updated in the copy of the original dict. I need to write the docs for this... with a sane example, but here is my unit test for it: https://gitlab.com/catalyst-cloud/confspirator/-/blob/master/confspirator/t… I use this in Adjutant by having some config groups which are a default for something, and another place where many things can override that default via another group in the config, so I create an overlay copy and pass that to the place that needs the config it it's most specific case when the code actually pulls values from the conf group I passed it. See: https://opendev.org/openstack/adjutant/src/branch/master/adjutant/actions/v… I hope that helps, because it is in my mind a little odd to explain, but it allows some useful things when reusing actions in different tasks. > "I also have nested config groups that need to be named dynamically to > allow plugin classes to be extended without subclasses sharing the > same config group name." > > Minus the nesting part, this is also something being done with > oslo.config today. The config driver feature actually uses dynamically > named groups, and I believe at least Cinder is using them too. They do > cause a bit of grief for some config tools, like the validator, but it > is possible to do something like this. Cool! yeah I implemented that feature in my code because I ran into a case of confliciting namespaces and needed to find a better way to handle subclasses that needed to have different dynamic names for their config groups. > > Now, as to the question of whether we should try to integrate this > library with oslo.config: I don't know. Helpful, right? That's mostly where we got to last time I asked in #openstack-oslo! > > I think answering that question definitively would take a deeper dive > into what the new library is doing differently than I can commit to. > As I noted above, I don't think the things you're doing are so far out > in left field that it would be unreasonable to consider integrating > into oslo.config, but the devil is in the details and there are a lot > of details here that I don't know anything about. For example, will > the oslo.config data model even accommodate nested groups? I suspect > it doesn't now, but could it? Probably, but I can't say how > difficult/disruptive it would be. I looked into it briefly, and to do what I wanted, while also maintaining oslo.config how it was... ended up a bit messy, so I gave up because it would take too long and the politics of trying to get it merged/reviewed wouldn't be worth the effort most likely. > > If someone wanted to make incremental progress toward integration, I > think writing a basic YAML driver for oslo.config would be a good > start. It would be generally useful even if this work doesn't go > anywhere, and it would provide a basis for a hypothetical future > YAML-based driver providing CONFspirator functionality. From there we > could start looking to integrate more advanced features one at a time. > > Apologies for the wall of text. I hope you got something out of this > before your eyes glazed over. > > -Ben > Thanks for the wall of text! It was useful! I think ultimately it may be safer just maintaining my own separate library. For people who don't want to use .ini and prefer yaml/toml it's simpler, and for people who prefer .ini and don't need nesting etc, it's safer to keep oslo.config as it is. If someone does find anything I've done that makes sense in oslo.config I'd be happy to work porting it over, but I don't want to make structural changes to it. I'll always keep an eye on oslo.config, and may occasionally steal the odd idea if you add something cool, but I think other than my use of types.py and some of the Opt classes as a base, my code has diverged quite a bit.

1 0

per user quota not working properly
by its-openstack＠zohocorp.com 21 Aug '20

21 Aug '20

Dear openstack, We are facing a peculiar issue with regards to users quota of resources. e.g: s.no project user instance quota no instance created 1 test - 10 2 test user1 2 2 3 test user2 2 error "quota over" 4 test user3 3 able to create only 1 instance 5 test user4 no user quota defined able to create 10 instance As you see from mentioned table. when user1,user2, has instance quota of 2 and when user1 has created 2 instance, user2 unable to create instance. but user3 able to create only 1 more instance, user 4 has no quota applied so project quota 10 will be applied and he can create 10 instance. the quota is applied to each user but not tracked for each user, so this defeats the purpose of per user quota. Please help us with resolving this issue. Regards, sysadmin team

1 0

[largescale-sig] RPC ping
by Arnaud Morin 20 Aug '20

20 Aug '20

Hey all, TLDR: I propose a change to oslo_messaging to allow doing a ping over RPC, this is useful to monitor liveness of agents. Few weeks ago, I proposed a patch to oslo_messaging [1], which is adding a ping endpoint to RPC dispatcher. It means that every openstack service which is using oslo_messaging RPC endpoints (almosts all OpenStack services and agents - e.g. neutron server + agents, nova + computes, etc.) will then be able to answer to a specific "ping" call over RPC. I decided to propose this patch in my company mainly for 2 reasons: 1 - we are struggling monitoring our nova compute and neutron agents in a correct way: 1.1 - sometimes our agents are disconnected from RPC, but the python process is still running. 1.2 - sometimes the agent is still connected, but the queue / binding on rabbit cluster is not working anymore (after a rabbit split for example). This one is very hard to debug, because the agent is still reporting health correctly on neutron server, but it's not able to receive messages anymore. 2 - we are trying to monitor agents running in k8s pods: when running a python agent (neutron l3-agent for example) in a k8s pod, we wanted to find a way to monitor if it is still live of not. Adding a RPC ping endpoint could help us solve both these issues. Note that we still need an external mechanism (out of OpenStack) to do this ping. We also think it could be nice for other OpenStackers, and especially large scale ops. Feel free to comment. [1] https://review.opendev.org/#/c/735385/ -- Arnaud Morin

10 31

[requirements][oslo] Inclusion of CONFspirator in openstack/requirements
by Adrian Turjak 20 Aug '20

20 Aug '20

Hey OpenStackers! I'm hoping to add CONFspirator to openstack/requirements as I'm using it Adjutant: https://review.opendev.org/#/c/746436/ The library has been in Adjutant for a while but I didn't add it to openstack/requirements, so I'm trying to remedy that now. I think it is different enough from oslo.config and I think the features/differences are ones that are unlikely to ever make sense in oslo.config without breaking it for people who do use it as it is, or adding too much complexity. I wanted to use oslo.config but quickly found that the way I was currently doing config in Adjutant was heavily dependent on yaml, and the ability to nest things. I was in a bind because I didn't have a declarative config system like oslo.config, and the config for Adjutant was a mess to maintain and understand (even for me, and I wrote it) with random parts of the code pulling config that may or may not have been set/declared. After finding oslo.config was not suitable for my rather weird needs, I took oslo.config as a starting point and ended up writing another library specific to my requirements in Adjutant, and rather than keeping it internal to Adjutant, moved it to an external library. CONFspirator was built for a weird and complex edge case, because I have plugins that need to dynamically load config on startup, which then has to be lazy_loaded. I also have weird overlay logic for defaults that can be overridden, and building it into the library made Adjutant simpler. I also have nested config groups that need to be named dynamically to allow plugin classes to be extended without subclasses sharing the same config group name. I built something specific to my needs, that just so happens to also be a potentially useful library for people wanting something like oslo.config but that is targeted towards yaml and toml, and the ability to nest groups. The docs are here: https://confspirator.readthedocs.io/ The code is here: https://gitlab.com/catalyst-cloud/confspirator And for those interested in how I use it in Adjutant here are some places of interest (be warned, it may be a rabbit hole): https://opendev.org/openstack/adjutant/src/branch/master/adjutant/config https://opendev.org/openstack/adjutant/src/branch/master/adjutant/feature_s… https://opendev.org/openstack/adjutant/src/branch/master/adjutant/core.py https://opendev.org/openstack/adjutant/src/branch/master/adjutant/api/v1/op… https://opendev.org/openstack/adjutant/src/branch/master/adjutant/actions/v… https://opendev.org/openstack/adjutant/src/branch/master/adjutant/actions/v… https://opendev.org/openstack/adjutant/src/branch/master/adjutant/tasks/v1/… https://opendev.org/openstack/adjutant/src/branch/master/adjutant/tasks/v1/… If there are strong opinions about working to add this to oslo.config, let's chat, as I'm not against merging this into it somehow if we find a way that make sense, but while some aspects where similar, I felt that this was cleaner without being part of oslo.config because the mindset I was building towards seemed different and oslo.config didn't need my complexity. Cheers, Adrian

2 1

[cloudkitty] Resuming CloudKitty IRC meetings
by Pierre Riteau 20 Aug '20

20 Aug '20

Hello, We are resuming IRC meetings for the CloudKitty project using the existing calendar schedule. The first meeting will be on Monday August 24 at 1400 UTC in #cloudkitty on freenode, then every two weeks. Everyone is welcome: contributors, users, and anyone who would like to contribute or use CloudKitty but doesn't know how to get started. The agenda is available on Etherpad [1]. The meeting description [2] was stating that meetings were on the first and third Monday of the month, but the calendar schedule was using odd weeks. I've submitted a change [3] to synchronise the description: let's meet on odd weeks instead of using a month-based schedule. Thanks in advance to all of you helping to keep the project going. Pierre Riteau (priteau) [1] https://etherpad.opendev.org/p/cloudkitty-meeting-topics [2] http://eavesdrop.openstack.org/#CloudKitty_Team_Meeting [3] https://review.opendev.org/#/c/747256/

3 6

[Neutron] Drivers meeting agenda
by Slawek Kaplonski 20 Aug '20

20 Aug '20

Hi, Here is agenda for tomorrow's drivers meeting. We have 2 RFEs to discuss: * https://bugs.launchpad.net/neutron/+bug/1891334 - [RFE] Enable change of CIDR on a subnet * https://bugs.launchpad.net/neutron/+bug/1892200 - Make keepalived healthcheck more configurable There are also some points from Rodolfo on the on demand agenda but Rodolfo is on PTO this week so probably we will discuss those topics finally next week. See You on the meeting tomorrow and have a nice day :) -- Slawek Kaplonski Principal software engineer Red Hat

1 0

[release] Release countdown for week R-7 Aug 24 - 28
by Sean McGinnis 20 Aug '20

20 Aug '20

Development Focus ----------------- We are entering the last weeks of the Victoria development cycle. From now until the final release, we'll send a countdown email like this every week. It's probably a good time for teams to take stock of their library and client work that needs to be completed yet. The non-client library freeze is coming up, followed closely by the client lib freeze. Please plan accordingly to avoid any last minute rushes to get key functionality in. General Information ------------------- Next week is the Extra-ATC freeze, in preparation for future elections. All contributions to OpenStack are valuable, but some are not expressed as Gerrit code changes. Please list active contributors to your project team who do not have a code contribution this cycle, and therefore won't automatically be considered an Active Technical Contributor and allowed to vote. This is done by adding extra-atcs to https://opendev.org/openstack/governance/src/branch/master/reference/projec… before the Extra-ATC freeze on August 28. A quick reminder of the upcoming freeze dates. Those vary depending on deliverable type: * General libraries (except client libraries) need to have their last feature release before Non-client library freeze (Sept 3). Their stable branches are cut early. * Client libraries (think python-*client libraries) need to have their last feature release before Client library freeze (Sept 10) * Deliverables following a cycle-with-rc model (that would be most services) observe a Feature freeze on that same date, Sept 10. Any feature addition beyond that date should be discussed on the mailing-list and get PTL approval. After feature freeze, cycle-with-rc deliverables need to produce a first release candidate (and a stable branch) before RC1 deadline (Sept 24) * Deliverables following cycle-with-intermediary model can release as necessary, but in all cases before Final RC deadline (Oct 8) Finally, now is also a good time to start planning what highlights you want for your deliverables in the cycle highlights. The deadline to submit an initial version for those is set to Feature freeze (Sept 10). Background on cycle-highlights: http://lists.openstack.org/pipermail/openstack-dev/2017-December/125613.html Project Team Guide, Cycle-Highlights: https://docs.openstack.org/project-team-guide/release-management.html#cycle… knelson [at] openstack.org/diablo_rojo on IRC is available if you need help selecting or writing your highlights Upcoming Deadlines & Dates -------------------------- Non-client library freeze: September 3 (R-6 week) Client library freeze: September 10 (R-5 week) Victoria-3 milestone: September 10 (R-5 week) Victoria release: October 14

1 0

[all] Proposed Wallaby cycle schedule
by Sean McGinnis 20 Aug '20

20 Aug '20

Hey everyone, The Victoria cycle is going by fast, and it's already time to start planning some of the early things for the Wallaby release. One of the first steps for that is actually deciding on the release schedule. Typically we have done this based on when the next Summit event was planned to take place. Due to several reasons, we don't have a date yet for the first 2021 event. The current thinking is it will likely take place in May (nothing is set, just an educated guess, so please don't use that for any other planning). So for the sake of figuring out the release schedule, we are targeting a release date in early May. Hopefully this will then align well with event plans. I have a proposed release schedule up for review here: https://review.opendev.org/#/c/744729/ For ease of viewing (until the job logs are garbage collected), you can see the rendered schedule here: https://0e6b8aeca433e85b429b-46fd243db6dc394538bd0555f339eba5.ssl.cf1.rackc… There are always outside conflicts, but I think this has aligned mostly well with major holidays. But please feel free to comment on the patch if you see any major issues that we may have not considered. Thanks! Sean

1 2

[tripleo] Moving tripleo-ansible-inventory script to tripleo-common?
by Cédric Jeanneret 20 Aug '20

20 Aug '20

Hello there! I'm wondering if we could move the "tripleo-ansible-inventory" script from the tripleo-validations repo to tripleo-common. The main motivation here is to make things consistent: - that script calls content from tripleo-common, nothing from tripleo-validations. - that script isn't only for the validations, so it makes more sense to install it via tripleo-common - in fact, we should probably push that inventory thing as an `openstack tripleo' sub-command, but that's another story So, is there any opposition to this proposal? Cheers, C. -- Cédric Jeanneret (He/Him/His) Sr. Software Engineer - OpenStack Platform Deployment Framework TC Red Hat EMEA https://www.redhat.com/

4 5

[neutron] Disable dhcp drop rule
by Eugen Block 20 Aug '20

20 Aug '20

Hi *, we recently upgraded our Ocata Cloud to Train and also switched from linuxbridge to openvswitch. One of our instances within the cloud works as DHCP server and to make that work we had to comment the respective part in this file on the compute node the instance was running on: /usr/lib/python2.7/site-packages/neutron/agent/linux/iptables_firewall.py Now we tried the same in /usr/lib/python3.6/site-packages/neutron/agent/linux/openvswitch_firewall/firewall.py /usr/lib/python3.6/site-packages/neutron/agent/linux/iptables_firewall.py but restarting openstack-neutron-openvswitch-agent.service didn't drop that rule, the DHCP reply didn't get through. To continue with our work we just dropped it manually, so we get by, but since there have been a couple of years between Ocata and Train, is there any smoother or better way to achieve this? This seems to be a reoccuring request but I couldn't find any updates on this topic. Maybe someone here can shed some light? Is there more to change than those two files I mentioned? Any pointers are highly appreciated! Best regards, Eugen

2 3

OpenStack with Nginx
by HARISH KUMAR Ivaturi 19 Aug '20

19 Aug '20

Hi I am Harish Kumar, Master Student at BTH, Karlskrona, Sweden. I am working on my Master thesis at BTH and my thesis topic is Performance evaluation of OpenStack with HTTP/3. I have successfully built curl and nginx with HTTP/3 support and I am performing some commands using curl for generating tokens so i could access the services of OpenStack. OpenStack relies with the Apache web server and I could not get any results using Nginx HTTP/3 . I would like to ask if there is any official documentation on OpenStack relying with Nginx?, I have searched in the internet reg. this info but could not get any, I would like to use nginx instead of apache web server , so I could get some results by performing curl and commands and nginx web server (with http/3 support). Please let me know and if there is any content please share with me. I hope you have understood this. It would be helpful for my Master Thesis. BR Harish Kumar

2 1

[upstream-institute] Virtual training sign-up and planning
by Ildiko Vancsa 19 Aug '20

19 Aug '20

Hi mentors, I’m reaching out to you as the next Open Infrastructure Summit is approaching quickly so it is time to start planning for the next OpenStack Upstream Institute. As the next event will be virtual we will need to re-think the training format and experience to make sure our audience gets the most out of it. I created a new entry on our training occasions wiki page here: https://wiki.openstack.org/wiki/OpenStack_Upstream_Institute_Occasions#Virt… Please __sign up on the wiki__ if you would like to participate in the preparations and running the virtual training. As it is still vacation season I think we can target the last week of August or first week of September to have the first prep meeting and can collect ideas here or discuss them on the #openstack-upstream-institute IRC channel on Freenode in the meantime. Please let me know if you have any questions or need any help with signing up on the wiki. Thanks and Best Regards, Ildikó

1 1

[neutron][ops] API for viewing HA router states
by Mohammed Naser 19 Aug '20

19 Aug '20

Hi all, Over the past few days, we were troubleshooting an issue that ended up having a root cause where keepalived has somehow ended up active in two different L3 agents. We've yet to find the root cause of how this happened but removing it and adding it resolved the issue for us. As we work on improving our monitoring, we wanted to implement something that gets us the info of # of active routers to check if there's a router that has >1 active L3 agent but it's hard because hitting the /l3-agents endpoint on _every_ single router hurts a lot on performance. Is there something else that we can watch which might be more productive? FYI -- this all goes in the open and will end up inside the openstack-exporter: https://github.com/openstack-exporter/openstack-exporter and the Helm charts will end up with the alerts: https://github.com/openstack-exporter/helm-charts Thanks! Mohammed -- Mohammed Naser VEXXHOST, Inc.

5 12

[cinder][ops] "Berlin" 2020 Virtual Forum - Cinder brainstorming
by Brian Rosmaita 19 Aug '20

19 Aug '20

This message is aimed at anyone with an interest in the OpenStack Block Storage Service, whether as an operator, a user, or a developer. Like all the other teams, Cinder would like to get feedback from operators and users about the current state of the software, get some ideas about what should be in the next release, and have some strategic discussion about The Future. So if you have some ideas you'd like to be considered, feel free to propose a topic: https://etherpad.opendev.org/p/2020-Wallaby-cinder-brainstorming You only need to add a sentence or two describing your topic and it doesn't have to be very polished, so if you have an idea, just go to the etherpad and slap it down now while you're thinking about it. The deadline for proposals to the Foundation is 14 September, so if you could get your idea down on the etherpad before the Cinder weekly meeting on Wednesday 9 September 14:00 UTC, that will give the Cinder team time to look them over. thanks! brian

1 0

[tripleo][ci] container pulls failing
by Wesley Hayutin 19 Aug '20

19 Aug '20

FYI... If you find your jobs are failing with an error similar to [1], you have been rate limited by docker.io via the upstream mirror system and have hit [2]. I've been discussing the issue w/ upstream infra, rdo-infra and a few CI engineers. There are a few ways to mitigate the issue however I don't see any of the options being completed very quickly so I'm asking for your patience while this issue is socialized and resolved. For full transparency we're considering the following options. 1. move off of docker.io to quay.io 2. local container builds for each job in master, possibly ussuri 3. parent child jobs upstream where rpms and containers will be build and host artifacts for the child jobs 4. remove some portion of the upstream jobs to lower the impact we have on 3rd party infrastructure. If you have thoughts please don't hesitate to share on this thread. Very sorry we're hitting these failures and I really appreciate your patience. I would expect major delays in getting patches merged at this point until things are resolved. Thank you! [1] HTTPError: 429 Client Error: Too Many Requests for url: http://mirror.ca-ymq-1.vexxhost.opendev.org:8082/v2/tripleotrain/centos-bin… [2] https://bugs.launchpad.net/tripleo/+bug/1889122

8 20

[neutron] CI meeting cancelled
by Slawek Kaplonski 19 Aug '20

19 Aug '20

Hi, I have today some internal meeting in the same time as Neutron CI meeting is. Also, some of the team members who are usually attending this meeting are on pto this week so lets cancel it. If You see any CI related issue, please open LP and ping me on IRC. -- Slawek Kaplonski Principal software engineer Red Hat

1 0

[cloudkitty][tc] Cloudkitty abandoned?
by Sean McGinnis 19 Aug '20

19 Aug '20

Posting here to raise awareness, and start discussion about next steps. It appears there is no one working on Cloudkitty anymore. No patches have been merged for several months now, including simple bot proposed patches. It would appear no one is maintaining this project anymore. I know there is a need out there for this type of functionality, so maybe this will raise awareness and get some attention to it. But barring that, I am wondering if we should start the process to retire this project. From a Victoria release perspective, it is milestone-2 week, so we should make a decision if any of the Cloudkitty deliverables should be included in this release or not. We can certainly force releases of whatever is the latest, but I think that is a bit risky since these repos have never merged the job template change for victoria and therefore are not even testing with Python 3.8. That is an official runtime for Victoria, so we run the risk of having issues with the code if someone runs under 3.8 but we have not tested to make sure there are no problems doing so. I am hoping this at least starts the discussion. I will not propose any release patches to remove anything until we have had a chance to discuss the situation. Sean

11 20

[cloudkitty][rdo] Broken cloudkitty RPMs on CentOS8
by Pierre Riteau 19 Aug '20

19 Aug '20

Hello, This issue was discovered on Kolla train-centos8 images, but I assume it applies to both Train and Ussuri for CentOS 8 in general, not just to Kolla. CloudKitty became timezone-aware in Train: https://review.opendev.org/#/c/669192/ This code references tz.UTC from the dateutil library. However, this was added only in dateutil 2.7.0, while train-centos8 Kolla images use package python3-dateutil-2.6.1-6.el8.noarch.rpm, causing the error captured at the end of this message [2]. I submitted a patch to raise the minimum requirement for dateutil in cloudkitty: https://review.opendev.org/#/c/742477/ However, how are those requirements taken into consideration when packaging OpenStack in RDO? RDO packages for CentOS7 provide python2-dateutil-2.8.0-1.el7.noarch.rpm, but there is no such package in the CentOS8 repository. Would it be better to just remove the use of tz.UTC? I believe we could use dateutil.tz.tzutc() instead. Thanks, Pierre Riteau (priteau) [1] http://mirror.centos.org/centos/8/cloud/x86_64/openstack-train/Packages/p/ [2] Error trace below: 2020-07-22 16:33:11.207 26 ERROR wsme.api [req-3c49884a-1412-42bb-a57e-e7c731360148 ef450a969a2945928d3ade785eaae860 19df0f36ede14c29be9ca476222f8ba9 default - -] Server-side error: "module 'dateutil.tz' has no attribute 'UTC'". Detail: Traceback (most recent call last): File "/usr/lib/python3.6/site-packages/wsmeext/pecan.py", line 85, in callfunction result = f(self, *args, **kwargs) File "/usr/lib/python3.6/site-packages/cloudkitty/api/v1/controllers/storage.py", line 71, in get_all paginate=False) File "/usr/lib/python3.6/site-packages/cloudkitty/storage/v2/influx.py", line 311, in retrieve begin, end = self._check_begin_end(begin, end) File "/usr/lib/python3.6/site-packages/cloudkitty/storage/v2/influx.py", line 271, in _check_begin_end end = tzutils.get_next_month() File "/usr/lib/python3.6/site-packages/cloudkitty/tzutils.py", line 150, in get_next_month return add_delta(start, datetime.timedelta(days=month_days)) File "/usr/lib/python3.6/site-packages/cloudkitty/tzutils.py", line 104, in add_delta return utc_to_local(local_to_utc(dt, naive=True) + delta) File "/usr/lib/python3.6/site-packages/cloudkitty/tzutils.py", line 52, in local_to_utc output = dt.astimezone(tz.UTC) AttributeError: module 'dateutil.tz' has no attribute 'UTC'

1 0

[openstack-helm] openstack-helm-images release stable/ussuri loci images building issue
by Hemant Sonawane 19 Aug '20

19 Aug '20

Hello, I am trying to build a *loci openstack-helm-images release stable/ussuri *but there is an issue with each image I am building which could be related to the python version and pip package but I am really not sure about it. I also tried to update the python version for each package in requirements repo but it didn't help. Is there any way to upgrade the python version and pip as well in requirements? or does anybody know how to resolve this issue while building openstack-helm-images? I have attached logs for your ready reference. Help will be much appreciated thanks :) -- Thanks and Regards, Hemant Sonawane

1 0

VM doesn't have internet - OpenStack Ussuri with OVN networking
by Reza Bakhshayeshi 19 Aug '20

19 Aug '20

Hi all, I've set up OpenStack Ussuri with OVN networking manually, VMs can ping each other through an internal network. I've created a provider network with valid IP subnet, and my problem is VMs don't have internet access before and after assigning floating IP. I've encountered the same problem on TripleO (with dvr), and I just wanted to investigate the problem by manual installation (without HA and DVR), but the same happened. Everything seems working properly, I can't see any error in logs, here is agent list output: [root@controller ~]# openstack network agent list +--------------------------------------+------------------------------+------------------------+-------------------+-------+-------+-------------------------------+ | ID | Agent Type | Host | Availability Zone | Alive | State | Binary | +--------------------------------------+------------------------------+------------------------+-------------------+-------+-------+-------------------------------+ | 1ade76ae-6caf-4942-8df3-e3bc39d2f12d | OVN Controller Gateway agent | controller.localdomain | n/a | :-) | UP | ovn-controller | | 484f123f-5935-44ce-aee7-4102271d9f11 | OVN Controller agent | compute.localdomain | n/a | :-) | UP | ovn-controller | | 01235c13-4f32-4c4f-8cf6-e4b8d59a438a | OVN Metadata agent | compute.localdomain | n/a | :-) | UP | networking-ovn-metadata-agent | +--------------------------------------+------------------------------+------------------------+-------------------+-------+-------+-------------------------------+ On the controller I got br-ex with a valid IP address. here is the external-ids table on controller and compute node: [root@controller ~]# ovs-vsctl get Open_vSwitch . external-ids {hostname=controller.localdomain, ovn-bridge=br-int, ovn-cms-options=enable-chassis-as-gw, ovn-encap-ip="10.0.0.11", ovn-encap-type=geneve, ovn-remote="tcp:10.0.0.11:6642", rundir="/var/run/openvswitch", system-id="1ade76ae-6caf-4942-8df3-e3bc39d2f12d"} [root@compute ~]# ovs-vsctl get Open_vSwitch . external-ids {hostname=compute.localdomain, ovn-bridge=br-int, ovn-encap-ip="10.0.0.31", ovn-encap-type=geneve, ovn-remote="tcp:10.0.0.11:6642", rundir="/var/run/openvswitch", system-id="484f123f-5935-44ce-aee7-4102271d9f11"} and I have: [root@controller ~]# ovn-nbctl show switch 72fd5c08-6852-4d7e-b9b4-7e0a1ccdd976 (neutron-b8c66c3d-f47a-42a5-bd2d-c40c435c0376) (aka net01) port cf99f43b-0a18-4b91-9ca5-b6ed3f86d994 type: localport addresses: ["fa:16:3e:d0:df:82 192.168.0.100"] port 4268f511-bee3-4da0-8835-b9a8664101c4 addresses: ["fa:16:3e:35:f2:02 192.168.0.135"] port 846919e8-cde5-4ba3-b003-0c06e73676ed type: router router-port: lrp-846919e8-cde5-4ba3-b003-0c06e73676ed switch bb22224e-e1d1-4bb2-b57e-1058e9fc33a7 (neutron-9614546f-b216-4554-9bfe-e8d6bb11d927) (aka provider) port 2f05c7bc-ad0f-4a41-bbd8-5fef1f5bfd2c type: localport addresses: ["fa:16:3e:17:7b:5b X.X.X.X"] port provnet-9614546f-b216-4554-9bfe-e8d6bb11d927 type: localnet addresses: ["unknown"] port 23fcdc9d-2d11-40c9-881e-c78e871a3314 type: router router-port: lrp-23fcdc9d-2d11-40c9-881e-c78e871a3314 router 0bd35585-b0a3-4c8f-b71b-cb87c9fad060 (neutron-8cdcd0d2-752c-4130-87bb-d2b7af803ec9) (aka router01) port lrp-846919e8-cde5-4ba3-b003-0c06e73676ed mac: "fa:16:3e:4d:c3:f9" networks: ["192.168.0.1/24"] port lrp-23fcdc9d-2d11-40c9-881e-c78e871a3314 mac: "fa:16:3e:94:89:8e" networks: ["X.X.X.X/22"] gateway chassis: [1ade76ae-6caf-4942-8df3-e3bc39d2f12d 484f123f-5935-44ce-aee7-4102271d9f11] nat 8ef6167a-bc28-4caf-8af5-d0bf12a62545 external ip: " X.X.X.X " logical ip: "192.168.0.135" type: "dnat_and_snat" nat ba32ab93-3d2b-4199-b634-802f0f438338 external ip: " X.X.X.X " logical ip: "192.168.0.0/24" type: "snat" I replaced valid IPs with X.X.X.X Any suggestion would be grateful. Regards, Reza

1 1

[scientific-sig] IRC meeting starting shortly
by Stig Telfer 18 Aug '20

18 Aug '20

Hi All - We have a Scientific SIG IRC meeting starting shortly in channel #openstack-meeting. Everyone is welcome. This week's agenda is here: https://wiki.openstack.org/wiki/Scientific_SIG#IRC_Meeting_August_18th_2020 We'd like to cover some upcoming (virtual) events - Supercomputing 2020 and the OpenStack PTG. Cheers, Stig

1 0

[monasca] Setup Monasca from scratch
by Antonios Dimtsoudis 18 Aug '20

18 Aug '20

Hi all, i am trying to set up Monasca from scratch. Is there a good introduction / point to start of you would recommend? Thanks in advance, Antonios.

2 1

[tripleo] Help needed to write a Third Party integration guide
by Emilien Macchi 18 Aug '20

18 Aug '20

Hi people, We have been requested several times (for good reasons) about how to write out-of-tree files for TripleO integration (Heat templates, Ansible roles, Container Images layouts, etc). For example, Dell has an external repository ( https://github.com/dell/tripleo-powerflex) where they have pretty much all they need to install their services in out-of-tree fashion (I'm sure there are more examples, this one is just the most recent in my knowledge). This model is recommended for the third party services that aren't part of TripleO but still want to be integrated with it. This usually fits when the service can't be maintained by the TripleO team but there is a desire from outside of the community to maintain some integration (e.g. vendors). We haven't done a good job at providing a full end to end guide on how to achieve this and very often asked people to just do it. I propose that we work on this guide together and today I'm gathering for volunteers who have knowledge on that field or are interested to learn about it and contribute it back directly into a new guide, hosted on tripleo-docs repo. https://bugs.launchpad.net/tripleo/+bug/1892072 This will probably involve a bunch of linking to existing docs but also a good opportunity to update what is outdated in our content and provide more information where needed. Thanks for letting us know if you're interested to be actively contributing into that effort, -- Emilien Macchi

2 1

GHC Mentors Needed for OpenStack
by Amy Marrich 18 Aug '20

18 Aug '20

Grace Hopper Conference is going virtual this year and once again OpenStack is participating as one of the Open Source Day projects. We are hoping to do some peer programming (aka mentees shadowing folks while they work through a patch) as part of the day. Mentors receive a full conference pass and AnitaB.org membership. Please check out the requirements <https://ghc.anitab.org/get-involved/volunteer/committee-members-and-scholar…>{0} and apply <https://ghc.anitab.org/get-involved/volunteer/committee-members-and-scholar…>(1) by August 19, 2020. We are also figuring a way for more folks to be able to mentor, so if you'd like to help but aren't interested in the conference please reach out to me or Victoria(vkmc) by email or on IRC. Thanks and apologies for the short deadline though I can probably get let additions in:) Amy (spotz) 0- Grace Hopper mentorship requirements: https://ghc.anitab.org/get-involved/volunteer/committee-members-and-scholar… 1- Grace Hopper mentorship application: https://ghc.anitab.org/get-involved/volunteer/committee-members-and-scholar…

2 2

[all][PTL][TC] Forum Brainstorming
by Kendall Nelson 17 Aug '20

17 Aug '20

Hello Everyone! The Virtual Forum is approaching. We would love 1 volunteer from the community for the Forum Selection Committee. Ideally, the volunteer would already be serving in some capacity in a governance role for your project. In addition to calling for volunteers for the Forum selection committee, this email kicks off the brainstorming period before the CFP tool opens for formal Forum submissions. The categories for brainstorming etherpads have already been setup here[1]. Please add your etherpads and ideas there! The CFP tool will open on August 31st and will close September 14th. For information on the upcoming virtual Summit[2]. For more information on the Forum[3]. Please reach out to jimmy(a)openstack.org or knelson(a)openstack.org if you're interested. Volunteers should respond on or before August 31, 2020. Thanks! Kendall (diablo_rojo) [1] Virtual Forum 2020 Wiki: https://wiki.openstack.org/wiki/Forum/Virtual2020 [2] Virtual Open Infra Summit Site: https://www.openstack.org/summit/2020 [3] General Forum Wiki: https://wiki.openstack.org/wiki/Forum

1 0

[tc] weekly update
by Mohammed Naser 17 Aug '20

17 Aug '20

Hi everyone, Here’s an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. We've also included a few references to some important mailing list threads that you should check out. # Patches ## Open Reviews - Move towards single office hour https://review.opendev.org/745200 - Drop all exceptions for legacy validation https://review.opendev.org/745403 - Create starter-kit:kubernetes-in-virt tag https://review.opendev.org/736369 - Fix names inside check-review-status https://review.opendev.org/745913 - Resolution to define distributed leadership for projects https://review.opendev.org/744995 - Move towards dual office hours in diff TZ https://review.opendev.org/746167 - [draft] Add assert:supports-standalone https://review.opendev.org/722399 ## Project Updates - Add python-dracclient to be owned by Hardware Vendor SIG https://review.opendev.org/745564 ## General Changes - Add legacy repository validation https://review.opendev.org/737559 - Clean up expired i18n SIG extra-ATCs https://review.opendev.org/745565 - Sort SIG names in repo owner list https://review.opendev.org/745563 - Drop neutron-vpnaas from legacy projects https://review.opendev.org/745401 - Pierre Riteau as CloudKitty PTL for Victoria https://review.opendev.org/745653 - Declare supported runtimes for Wallaby release https://review.opendev.org/743847 ## Abandoned Changes - Move towards dual office hours https://review.opendev.org/745201 # Email Threads - Zuul Native Jobs Goal Update #2: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016561.h… - Masakari Project Aliveness: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016520.h… - vPTG October 2020 Signup: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016497.h… - OpenStack Client vs python-*clients: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016409.h… # Other Reminders - Virtual Summit Community voting closes Monday, August 17 at 11:59pm Pacific Time Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[oslo] Feature Freeze is approaching
by Ben Nemec 17 Aug '20

17 Aug '20

Hi Oslo contributors, Oslo observes a feature freeze that is earlier than other projects. This is to allow time for features in Oslo to be adopted in the services before their feature freeze. And it's coming up soon. Aug. 28th is the Oslo feature freeze date for this cycle. That leaves about two weeks for features to be merged in Oslo libraries. After that, any features to be merged will require a feature freeze exception, which can be requested on the list. If you have any questions about this feel free to contact me here or on IRC (bnemec in #openstack-oslo). Thanks! -Ben

1 0

cross-team action items
by Corey Bryant 17 Aug '20

17 Aug '20

These were the items from the cross team today that need action from our team: Bootstack: What’s the plan for Ceph-osd w/ openstack-on-lxd for Bluestore? Can we give an answer as to whether we plan to deprecate or solve this, one way or another? Bootstack: Gnocchi thread - can we respond to thread to make official decision so they can plan accordingly? ie. if upstream is not supported, we likely won't support, so if we can clarify then bootstack can remove from standard deploys. SEG: LP#1891096 <https://bugs.launchpad.net/charm-ceph-mon/+bug/1891096> - configuration database support for mimic+: Any value that exists in the configuration database will no longer receive updates from ceph.conf. Will be subscribed to field-high. Thanks, Corey

1 0

[all][goals] Switch legacy Zuul jobs to native - update #2
by Luigi Toscano 17 Aug '20

17 Aug '20

Hi, Much progress has happened since the first report, almost 4 weeks ago. Let's summarize the main documents: - the goal: https://governance.openstack.org/tc/goals/selected/victoria/native-zuulv3-j… - the document above now includes the reference to the up-to-date Zuul v3 porting guide: https://docs.openstack.org/project-team-guide/zuulv3.html - the etherpad which tracks the current status: https://etherpad.opendev.org/p/goal-victoria-native-zuulv3-migration - the previous report: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016058.html If you still have legacy jobs around, please prioritize this porting work. Victoria branching is not far away (actually, quite close for client libraries). This is the list of projects which still need to complete the work. Most of the legacy jobs derive from legacy-dsvm-base, and those are the most important ones. There is a limited amount of jobs which derive from legacy-base that should be taken into account as well, though. - barbican (*) - blazar (*) - cinder (/) (-> yes, this is my fault for the record :) - designate (+) - ec2-api (*) - freezer (*) - heat (/) - infra (/) - ironic (*) - karbor (*) - magnum (*) - manila (/) - but only devstack-base - monasca (+) - murano (/) - neutron (*) - nova (*) - oslo (*) - senlin - trove (+) - vitrage - zaqar The symbol close to the project name provides more detals about the status: (+) means that the project cores are at least aware of the issue, (*) means that there was active pending reviews for some of the remaining jobs, (/) means that there was past activity but no open reviews currently I'd just like to remind everyone that, while not part of the main goal, backporting the new jobs to the older branches when possible will make future maintenance easier. Ciao -- Luigi

1 0

[neutron] bug deputy report for week of 2020-08-10
by Bence Romsics 17 Aug '20

17 Aug '20

Hi, This is last week's buglist. Probably due to summer vacations but we have a few bugs without an owner. High: * https://bugs.launchpad.net/neutron/+bug/1891307 SSH fails in neutron-ovn-tripleo-ci-centos-8-containers-multinode job gate-failure, unassigned * https://bugs.launchpad.net/neutron/+bug/1891309 Designate integration - internal server error in Neutron gate-failure, unassigned * https://bugs.launchpad.net/neutron/+bug/1891517 neutron.tests.unit.common.test_utils.TimerTestCase.test__enter_with_timeout fails once in a while gate-failure, proposed fix: https://review.opendev.org/746154 * https://bugs.launchpad.net/neutron/+bug/1891673 qrouter ns ip rules not deleted when fip removed from vm proposed fix: https://review.opendev.org/746336 Needs further triage by someone knowing the designate integration better than I do: * https://bugs.launchpad.net/neutron/+bug/1891333 strange behavior of dns_domain with designate multi domain * https://bugs.launchpad.net/neutron/+bug/1891512 neutron designate DNS dns_domain assignment issue Low: * https://bugs.launchpad.net/neutron/+bug/1891243 neutron tempest failure: neutron_tempest_plugin.api.test_extensions.ExtensionsTest.test_list_extensions_includes_all OVN sample devstack conf did not enable all service plugins needed for tempest tests proposed fix: https://review.opendev.org/745829 Whishlist: * https://bugs.launchpad.net/neutron/+bug/1891360 Floating IP agent gateway IP addresses not released when deleting dead DVR L3 agents unassigned * https://bugs.launchpad.net/neutron/+bug/1891448 L3 agent mode transition between dvr and dvr_no_external unassigned RFE: * https://bugs.launchpad.net/neutron/+bug/1891334 [RFE] Enable change of CIDR on a subnet Best regards, Bence (rubasov)

1 0

[glance] Virtual PTG October 2020
by Abhishek Kekane 17 Aug '20

17 Aug '20

Hi Team, There is a project signup process going on for virtual PTG October 2020. I will like to book slots for the same between 1400 UTC to 1700 UTC. Please let me know your convenience for the same. Thanks & Best Regards, Abhishek Kekane

1 0

[neutron] How to specify overlay network interface when using OVN and Geneve?
by Popoi Zen 16 Aug '20

16 Aug '20

Hi, I have used my google fu but I cant find any reference. Just want to know how to specify overlay network when Im using geneve as my overlay protocol?

4 4

[neutron][ovn][sfc] Is it possible to use SFC (Service Function Chaining) on provider network?
by Popoi Zen 16 Aug '20

16 Aug '20

I have look some guide about SFC, but it seems that SFC only used on private/selfservice network. Is it possible to steer traffic between instance when they use provider network? I always getting error when using provider network. Maybe, can I push flow rule direct on OVN database or something like that?

1 0

[Interop-WG] Inviting cross-projects discussions for new re-branding efforts (Oct 26)
by prakash RAMCHANDRAN 15 Aug '20

15 Aug '20

Hi all, I have booked for two hours slot to enable re-branding efforts we are looking to unleash in early 2021.As part of "Open Infrastructure Summit" we kick-start with Inter-op for next decade. Monday October 26 13UTC - 15UTC InteropWG We would like to encourage Open Infrastructure Projects to enlighten the stage with Out-of-Box thinking & requests for Interop in Marketplace in OSF. - Integrated Projects in OpenStack have well served thru last decades dream team, that has stood the Tempest tests for RefStackV1 being base for OPNFV-CNTT / ONAP/ and CVP/OVP1 of LFN - Its the turn to the Open Infra Projects like Kata, Airship, Zuul, StarlingX and potential https://openinfralabs.org/ to innovate and suggest the world How OSF can leverage next-gen Infra with k8s cluster as baseline for Milt-cluster , Hybrid Cloud, Muti-cloud RefStackV2 for upstream usage for Telco and Edge Clouds We need all Graduated and Incumbent Projects to propose how we can Re-Brand them for Open Infra Containerized workloads. Do you want to use Magnum, Zun, Kolla & Kuryer - refer https://etherpad.opendev.org/p/interop Should we collaborate with LFN re-imagining efforts via our RefStack2 plans as base for Open Infra Summit efforts to give Industry a wake up call to collaborate? Please reply with comments below, where are the global innovators hiding behind Alps & Himalaya, come and swing your ping pongs balls or Cricket Bats. The Rocky mountains curve balls will always haunt you if you don't speak-up./*================================================================================================================Your comments +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*/ Lets join the collaboration for unfinished transition to Containers world with Interoperability. Our committee members are all aligned to back you on our journey and ensure we bring the ideas that matter and execution that lits fire.https://www.openstack.org/summit/2020/vote-for-presentations#/24735 ThanksPrakash RamchandranFor Interop WG / OSF

2 1

[openstack-ansible] New core on board!
by Dmitriy Rabotyagov 15 Aug '20

15 Aug '20

Hey everyone! Today we have several reasons to celebrate! First of all, we have released OSA Ussuri with tag 21.0.0 (better late than never :p). And even more exciting announcement, that Andrew Bonney is our new OpenStack-Ansible Core reviewer! Even though usual proposal process has been skipped this time, I think everyone will agree that Andrew deserved it and it's high time we congratulated him with becoming part of our team. Welcome on board, Andrew! -- Kind Regards, Dmitriy Rabotyagov

3 2

Trouble to launch a instance in open stack
by Midhunlal Nb 15 Aug '20

15 Aug '20

Hi all, --> I created an openstack set up in my networking lab. ---> Vmware installed in one of the blade server then ubuntu 18.04 installed as OS. ---> openstack 5.3.1 version successfully installed in this os ---> In my lab we are using 192.168.x.x/16 network ---> In openstack I created an external network with 192.168.x.x/16 ----> In openstack I created an internal network with 172.16.x.x/16(for testing) -----> then I created 1 external network(provider network),1 router,1 private cloud . ------> In internal network I created 2 instance (172.16.0.2&172.16.0.3)this two instance pinging each other and i am able assign floating ip(192.168.x.x) to this instance ----> Now my problem is I created a original instance with my network(192.168.x.x)in provider network(that instance directly attached to external (provider network)) --->This instance launched successfully and interface ip also our internal ip and dns also showing correct but i am not able to ping our any one of the lab network ip,internet also not available. please help me on this Thanks & Regards Midhunlal N B +918921245637

1 0

[release] Release countdown for week R-8 Aug 17 - 21
by Sean McGinnis 14 Aug '20

14 Aug '20

General Information ------------------- We are getting close to some of the end of cycle deadlines. Please be aware of the upcoming non-client library freeze on September 3. The following cycle-with-intermediary deliverables only did one release during the ussuri cycle, and have not done any intermediary release yet during this cycle. The cycle-with-rc release model is more suited for deliverables that plan to be released only once per cycle. As a result, we have suggested [1] as a potential release model change for the following deliverables: adjutant-ui adjutant cloudkitty heat-agents magnum-ui monasca-thresh monasca-ui [1] https://review.opendev.org/#/q/topic:victoria-cwi PTLs and release liaisons for each of those deliverables can either +1 the release model change, or propose an intermediary release for that deliverable. In absence of answer by the end of R-8 week we'll abandon the patch. We also published a couple of options for a proposed release schedule for the upcoming Wallaby cycle. Please check out the separate thread: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016391.h… 26 week schedule: https://review.opendev.org/745911/ 29 week schedule: https://review.opendev.org/744729/ Upcoming Deadlines & Dates -------------------------- Non-client library freeze: September 3 (R-6 week) Client library freeze: September 10 (R-5 week) Victoria-3 milestone: September 10 (R-5 week) Victoria release: October 14

1 0

Re: [Telemetry] Error when sending to prometheus pushgateway
by Samuel Mutel 14 Aug '20

14 Aug '20

Hello, I didn't find the issue. Somebody could help me ? Thanks. Le mer. 8 juil. 2020 à 17:55, Samuel Mutel <samuel.mutel(a)gmail.com> a écrit : > Hello, > > Thanks for your help. I tried to test the pushgateway manually and it > seems to work fine. The pushgateway wrote some things on the stdout. > But when I start the ceilometer, nothing happens. I tried to change the IP > to use 127.0.0.1 but nothing. > > Here is my ceilometer.conf: > >> [DEFAULT] >> auth_strategy = keystone >> debug = False >> event_dispatchers = gnocchi >> meter_dispatchers = gnocchi >> transport_url = rabbit://openstack:xxxxxx@xx.xx.x.xx >> ,openstack:xxxxxxx@xx.xx.x.xx,openstack:xxxxxxxxx@xx.xx.x.xx/ >> >> [cache] >> backend = dogpile.cache.memcached >> enabled = True >> memcache_servers = xx.xx.x.xx:11211,xx.xx.x.xx:11211,xx.xx.x.xx:11211 >> >> [keystone_authtoken] >> auth_type = password >> auth_uri = https://xxxxxxxxxxxx:5000/v3 >> auth_url = https://xxxxxxxxxxxx:5000 >> memcached_servers = xx.xx.x.xx:11211,xx.xx.x.xx:11211,xx.xx.x.xx:11211 >> password = xxxxxx >> project_domain_id = default >> project_name = service >> region_name = RegionOne >> user_domain_id = default >> username = ceilometer >> www_authenticate_uri = https://xxxxxxxxxxxx:5000 >> >> [notification] >> pipelines = meter >> >> [oslo_messaging_notifications] >> driver = messagingv2 >> >> [oslo_middleware] >> enable_proxy_headers_parsing = True >> >> [publisher] >> telemetry_secret = xxxxxxxxx >> >> [service_credentials] >> auth_type = password >> auth_url =https://xxxxxxxxxxxx:5000 >> password = xxxxxxxxx >> project_domain_id = default >> project_name = service >> region_name = RegionOne >> user_domain_id = default >> username = ceilometer >> > > Here is my event_pipeline.yaml: > >> sources: >> - name: meter_file >> events: >> - "*" >> sinks: >> - prometheus >> >> sinks: >> - name: prometheus >> publishers: >> - prometheus://127.0.0.1:9091/metrics/job/ceilometer >> > > Here is my pipeline.yaml: > >> sources: >> - name: meter_file >> interval: 30 >> meters: >> - "*" >> sinks: >> - prometheus >> >> sinks: >> - name: prometheus >> publishers: >> - prometheus://127.0.0.1:9091/metrics/job/ceilometer >> > > Here is my polling.yaml: > >> --- >> sources: >> - name: some_pollsters >> interval: 300 >> meters: >> - cpu >> - cpu_l3_cache >> - memory.usage >> - network.incoming.bytes >> - network.incoming.packets >> - network.outgoing.bytes >> - network.outgoing.packets >> - disk.device.read.bytes >> - disk.device.read.requests >> - disk.device.write.bytes >> - disk.device.write.requests >> - hardware.cpu.util >> - hardware.memory.used >> - hardware.memory.total >> - hardware.memory.buffer >> - hardware.memory.cached >> - hardware.memory.swap.avail >> - hardware.memory.swap.total >> - hardware.system_stats.io.outgoing.blocks >> - hardware.system_stats.io.incoming.blocks >> - hardware.network.ip.incoming.datagrams >> - hardware.network.ip.outgoing.datagrams >> > > Here is my ceilometer-rootwrap: > >> # Configuration for ceilometer-rootwrap >> # This file should be owned by (and only-writeable by) the root user >> >> [DEFAULT] >> # List of directories to load filter definitions from (separated by ','). >> # These directories MUST all be only writeable by root ! >> filters_path=/etc/ceilometer/rootwrap.d,/usr/share/ceilometer/rootwrap >> >> # List of directories to search executables in, in case filters do not >> # explicitely specify a full path (separated by ',') >> # If not specified, defaults to system PATH environment variable. >> # These directories MUST all be only writeable by root ! >> exec_dirs=/sbin,/usr/sbin,/bin,/usr/bin,/usr/local/sbin,/usr/local/bin >> >> # Enable logging to syslog >> # Default value is False >> use_syslog=False >> >> # Which syslog facility to use. >> # Valid values include auth, authpriv, syslog, user0, user1... >> # Default value is 'syslog' >> syslog_log_facility=syslog >> >> # Which messages to log. >> # INFO means log all usage >> # ERROR means only log unsuccessful attempts >> syslog_log_level=ERROR >> > > What configuration is wrong ? > > Le ven. 3 juil. 2020 à 13:53, Matthias Runge <mrunge(a)matthias-runge.de> a > écrit : > >> Okay, that doesn't really help with debugging though. >> >> Method not allowed is returned eg. when the endpoint expected an http >> push where your browser did an http get (that's correct). >> >> What I'd do next is to configure ceilometer to send to a different http >> endpoint (like a webserver on your workstation, just for debugging >> purposes). >> >> Verify that the push gateway works as expected, >> https://github.com/prometheus/pushgateway >> has some curl commands mentioned for debugging purposes. >> >> >> Matthias >> >> On 03/07/2020 13:07, Samuel Mutel wrote: >> > If I go to http://10.60.4.11:9091/metrics/job/ceilometer with the web >> > browser I receive: Method Not Allowed but i think it's normal. >> > http://10.60.4.11:9091/metrics is working with metrics. >> > >> > The pushgateway and the ceilometer is working on the same host for my >> > test so no network/firewall issue. >> > >> > Logs of the pushgateway is only these ones: >> > level=info ts=2020-07-03T11:04:35.907Z caller=main.go:83 msg="starting >> > pushgateway" version="(version=1.2.0, branch=HEAD, >> > revision=b7e0167e9574f4f88404dde9653ee1d3c940f2eb)" >> > level=info ts=2020-07-03T11:04:35.908Z caller=main.go:84 >> > build_context="(go=go1.13.8, user=root@0e823ccfff84, >> > date=20200311-18:51:01)" >> > level=info ts=2020-07-03T11:04:35.911Z caller=main.go:137 >> > listen_address=:9091 >> > >> > Le ven. 3 juil. 2020 à 12:14, Matthias Runge <mrunge(a)matthias-runge.de >> > <mailto:mrunge@matthias-runge.de>> a écrit : >> > >> > On 03/07/2020 11:25, Samuel Mutel wrote: >> > > Hello, >> > > >> > > I have two questions about ceilometer (openstack version rocky). >> > > >> > > * First of all, it seems that ceilometer is sending metrics >> > every hour >> > > and I don't understand why. >> > > * Next, I am not able to setup ceilometer to send metrics to >> > > prometheus pushgateway. >> > > >> > > Here is my configuration: >> > > >> > > sources: >> > > - name: meter_file >> > > interval: 30 >> > > meters: >> > > - "*" >> > > sinks: >> > > - prometheus >> > > >> > > sinks: >> > > - name: prometheus >> > > publishers: >> > > - >> > prometheus://10.60.4.11:9091/metrics/job/ceilometer >> > <http://10.60.4.11:9091/metrics/job/ceilometer> >> > > <http://10.60.4.11:9091/metrics/job/ceilometer> >> > > >> > > >> > > Here is the error I received: >> > > >> > > vcpus{resource_id="7fab268b-ca7c-4692-a103-af4a69f817e4"} 2 >> > > # TYPE memory gauge >> > > memory{resource_id="7fab268b-ca7c-4692-a103-af4a69f817e4"} >> 2048 >> > > # TYPE disk.ephemeral.size gauge >> > > >> > >> disk.ephemeral.size{resource_id="7fab268b-ca7c-4692-a103-af4a69f817e4"} >> > > 0 >> > > # TYPE disk.root.size gauge >> > > >> > disk.root.size{resource_id="7fab268b-ca7c-4692-a103-af4a69f817e4"} >> 0 >> > > : HTTPError: 400 Client Error: Bad Request for url: >> > > http://10.60.4.11:9091/metrics/job/ceilometer >> > > 2020-07-01 17:00:12.272 11375 ERROR ceilometer.publisher.http >> > > Traceback (most recent call last): >> > > 2020-07-01 17:00:12.272 11375 ERROR ceilometer.publisher.http >> > File >> > > >> "/usr/lib/python2.7/dist-packages/ceilometer/publisher/http.py", >> > > line 178, in _do_post >> > > 2020-07-01 17:00:12.272 11375 ERROR ceilometer.publisher.http >> >> > > res.raise_for_status() >> > > 2020-07-01 17:00:12.272 11375 ERROR ceilometer.publisher.http >> > File >> > > "/usr/lib/python2.7/dist-packages/requests/models.py", line >> > 935, in >> > > raise_for_status >> > > 2020-07-01 17:00:12.272 11375 ERROR ceilometer.publisher.http >> >> > > raise HTTPError(http_error_msg, response=self) >> > > 2020-07-01 17:00:12.272 11375 ERROR ceilometer.publisher.http >> > > HTTPError: 400 Client Error: Bad Request for url: >> > > http://10.60.4.11:9091/metrics/job/ceilometer >> > > 2020-07-01 17:00:12.272 11375 ERROR ceilometer.publisher.http >> > > >> > > >> > > Thanks for your help on this topic. >> > >> > >> > Hi, >> > >> > first obvious question: >> > >> > are you sure that there is something listening under >> > http://10.60.4.11:9091/metrics/job/ceilometer ? >> > >> > Would you have some error logs from the other side? It seems that >> > ceilometer is trying to dispatch as expected. >> > >> > Matthias >> > >> >>

1 0

[neutron] Implementing BGP over network:routed for IPv6 in Neutron, with DVR capabilities
by Thomas Goirand 14 Aug '20

14 Aug '20

Hi, When these patches are approved: https://review.opendev.org/486450 https://review.opendev.org/669395 we will effectively have BGP announcing for floating IPs and router gateways, with a provider network as next BGP HOP. I tested in experimentally, and it does work. There's more work to be done on it to make it better (like, eliminating GARP requests and getting neutron-dynamic-routing to know when a floating moves from one segment to another), as seen in the commends of #669395, but it works. Now, I'd like to have the same feature for IPv6. Having a segmented IPv6 L2 network already works, though isn't this always going through the network nodes still? I see no reason why IPv6 would always go through network nodes, and I would like to eliminate this SPOF. Has anyone worked on this? Or is there anyone with some advice on how to start? Is there some blueprints somewhere? I'm not sure what this implies, and where to start my research on this. But I really would love, moving forward, to have such a feature. Would anyone (try to) contribute this with me? Cheers, Thomas Goirand (zigo)

1 0

[tripleo] Specify different interface name in single nic vlans without external network installation
by Marco Marino 14 Aug '20

14 Aug '20

Hi, I'm trying to install openstack using tripleo on preprovisioned servers. My (desired) environment is quite simple: 1 controller and 1 compute node. Here is what I did: - Installed undercloud with 192.168.25.0/24 as a ctlplan subnet. local_ip = 192.168.25.2; undercloud_public_host=192.168.25.4; undercloud_admin_host = 192.168.25.3 - Installed 2 servers (compute and controller) with centos 8. Hardware requirements are satisfied (32 GB of ram, 100GB disk....) - Manually created user stack on compute and controller and added it to the sudoers list. - Manually Installed openstack repositories (sudo -E tripleo-repos -b ussuri current-tripleo-rdo) - Manually installed openstack required openstack packages: sudo yum install python3-heat-agent* -y Now I'd like to use 192.168.25.0/24 as "installation network" (network used by ansible) and I'm trying to configure one single nic with vlans. Please note that on all servers (undercloud included) I have 2 physical interfaces with the same name: enp1s0 and enp7s0. enp1s0 is used for a completely openstack-detached network: 192.168.2.0/24 and enp7s0 is used for 192.168.25.0/24 More precisely: Controller-0 = 192.168.25.10 Compute-0 = 192.168.25.20 Furthermore, I confirm that I can reach <local_ip> from both nodes using ping and curl (on port 8004). And I added 2 lines in /etc/hosts on undercloud: 192.168.25.10 controller-0 192.168.25.20 compute-0 Now I'm really confused about what to do. I tried with: openstack overcloud deploy --templates --disable-validations -e /usr/share/openstack-tripleo-heat-templates/environments/deployed-server-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml -e templates/network-environment-overrides.yaml -e templates/ctlplane-assignment.yaml -e templates/nameservers.yaml -e templates/node-info.yaml -e templates/hostnamemap.yaml -n templates/network_data.yaml node-info.yaml: http://paste.openstack.org/show/796840/ hostnamemap.yaml: http://paste.openstack.org/show/796841/ network-environment-overrides.yaml: http://paste.openstack.org/show/796842/ ctlplane-assignment.yaml: http://paste.openstack.org/show/796843/ nameservers.yaml: http://paste.openstack.org/show/796844/ network_data.yaml: http://paste.openstack.org/show/796845/ How can I specify nic2 for single nic vlans without external network? Please can you provide an example with "openstack overcloud deploy" complete command? I'm reading documentation but I do not understand how to do and it's really frustrating. Thank you, Marco

1 0

Openstack-Train VCPU issue in Hyper-V
by its-openstack＠zohocorp.com 14 Aug '20

14 Aug '20

Dear Team, We are using Openstack-Train in our organization.We have created windows server 2016 Std R2 instances with this flavor m5.xlarge ( RAM - 65536 , Disk - 500 , VCPUs - 16 ).Once Hyper-V future enabled in this instances VCPU count is automatically reduced to 1 core after restart.Even we have enabled nested virtualisation in openstack compute server.Please help us to short out this issue. #cat /sys/module/kvm_intel/parameters/nested Y Regards, Sysadmin.

2 1

[masakari] Meetings
by Radosław Piliszek 14 Aug '20

14 Aug '20

Hello Fellow cloud-HA-seekers, I wanted to attend Masakari meetings but I found the current schedule unfit. Is there a chance to change the schedule? The day is fine but a shift by +3 hours would be nice. Anyhow, I wanted to discuss [1]. I've already proposed a change implementing it and looking forward to positive reviews. :-) That said, please reply on the change directly, or mail me or catch me on IRC, whichever option sounds best to you. [1] https://blueprints.launchpad.net/masakari/+spec/customisable-ha-enabled-ins… -yoctozepto

2 2

[Ocata][Heat] Strange error returned after stack creation failure -r aw template with id xxx not found
by Laurent Dumont 14 Aug '20

14 Aug '20

Hi! We are currently troubleshooting a Heat stack issue where one of the stack (one of 25 or so) is failing to be created properly (seemingly randomly). The actual error returned by Heat is quite strange and Google has been quite sparse in terms of references. The actual error looks like the following (I've sanitized some of the names): Resource CREATE failed: resources.potato: Resource CREATE failed: resources[0]: raw template with id 22273 not found heat resource-list STACK_NAME_HERE -n 50 > > +------------------+--------------------------------------+-------------------------+-----------------+----------------------+--------------------------------------------------------------------------+ > | resource_name | physical_resource_id | resource_type > | resource_status | updated_time | stack_name > | > > +------------------+--------------------------------------+-------------------------+-----------------+----------------------+--------------------------------------------------------------------------+ > | potato | RESOURCE_ID_HERE | OS::Heat::ResourceGroup | > CREATE_FAILED | 2020-07-18 T19:52:10Z | nested_stack_1_STACK_NAME_HERE > | > | potato_server_group | RESOURCE_ID_HERE | OS::Nova::ServerGroup | > CREATE_COMPLETE | 2020-07-21T19:52:10Z | nested_stack_1_STACK_NAME_HERE > | > | 0 | | potato1.yaml > | CREATE_FAILED | 2020-07-18T19:52:12Z | nested_stack_2_STACK_NAME_HERE > | > | 1 | | potato1.yaml > | INIT_COMPLETE | 2020-07- 18 T19:52:12Z | > nested_stack_2_STACK_NAME_HERE | > > +------------------+--------------------------------------+-------------------------+-----------------+----------------------+--------------------------------------------------------------------------+ > The template itself is pretty simple and attempts to create a ServerGroup and 2 VMs (as part of the ResourceGroup). My feeling is that one the creation of those machines fails and Heat get's a little cooky and returns an error that might not be the actual root cause. I would have expected the VM to show up in the resource list but I just see the source "yaml". Has anyone seen something similar in the past? Thanks!

2 3

[cinder] driver maintainers: 3rd party CI checkpoint reminder
by Brian Rosmaita 14 Aug '20

14 Aug '20

Hello Cinder driver maintainers, Around the time of the Feature Freeze (10 September), the Cinder team will be looking at the Third Party CIs to assess compliance [0]. Out of compliance drivers will be marked as 'unsupported' in the Victoria release. We can avoid a lot of unpleasantness if you take this opportunity to review the current situation of your driver's CI [1] and, if necessary, take appropriate steps to get it back into compliance before 10 September. cheers, brian [0] https://docs.openstack.org/cinder/latest/drivers-all-about.html#driver-comp… [1] http://cinderstats.ivehearditbothways.com/cireport.txt

1 0

[cinder] driver features declaration for victoria next week
by Brian Rosmaita 14 Aug '20

14 Aug '20

Hello Cinder driver maintainers, This is a reminder that new features added to Cinder drivers for the Victoria release must be merged at the time of the OpenStack-wide Feature Freeze, which is coming up soon (10 September, to be specific). In order to avoid the Festival of Insane Driver Reviewing that we had last cycle, if you have un-merged driver features that you would like to land in Victoria, please post a blueprint in Launchpad listing the Gerrit reviews of the associated patches before the next Cinder weekly meeting (that is, before 19 August at 1400 UTC). This will help the team prioritize reviews and give you candid early feedback on whether the features look ready. You can look among the Ussuri blueprints for examples; contact me in IRC if you have any questions. Due to the 7 September holiday in the USA, there will be reduced reviewing bandwidth right around the Feature Freeze, so that's why I'm asking you to plan ahead. cheers, brian

1 0

[cinder] victoria new feature status checkpoint next week
by Brian Rosmaita 14 Aug '20

14 Aug '20

If you are working on a Cinder feature for Victoria that hasn't merged yet, please add it to the agenda for next week's cinder weekly meeting on 19 August at 1400 UTC: https://etherpad.opendev.org/p/cinder-victoria-meetings If your feature requires client support, keep in mind that the final release for client libraries is in four weeks. Any client changes must be reviewed, tested, and merged before 10 September. Keep in mind that 7 September is a holiday for many Cinder core reviewers, so it is likely that we will have reduced reviewer bandwidth around the time of the Feature Freeze. So please plan ahead. cheers, brian

1 0

[cinder] victoria os-brick release coming soon
by Brian Rosmaita 13 Aug '20

13 Aug '20

Just a quick reminder that the victoria os-brick release is 3 weeks away. Reviews may be a bit slower than usual given that people may be taking some end-of-the-summer vacation, so if you have an important patch for os-brick, please take the initiative to raise awareness in the #openstack-cinder IRC channel if it's not getting the attention it deserves. cheers, brian

1 0

[cinder] victoria mid-cycle part 2 summary available
by Brian Rosmaita 13 Aug '20

13 Aug '20

In case you missed yesterday's R-9 virtual mid-cycle session, I've updated the victoria mid-cycle wiki with a summary: https://wiki.openstack.org/wiki/CinderVictoriaMidCycleSummary It will eventually include a link to the recording (in case you want to see what you missed or if you want to re-live the excitement). We had a productive meeting yesterday, thanks to all who participated. Unfortunately, some people had trouble connecting to the videoconference. Please contact me off-list so we can figure out whether this was a one-time fail or if we need to look at some other videoconf solution for future meetings. cheers, brian

1 0

[charms] OpenStack Charms 20.08 release is now available
by Alex Kavanagh 13 Aug '20

13 Aug '20

The 20.08 release of the OpenStack Charms is now available. This release brings several new features to the existing OpenStack Charms deployments for Queens, Rocky, Stein, Train, Ussuri, and many stable combinations of Ubuntu + OpenStack. Please see the Release Notes for full details: https://docs.openstack.org/charm-guide/latest/2008.html == Highlights == * New charm: neutron-api-plugin-arista There is a new supported subordinate charm that provides Arista switch ML2 plugin support to the OpenStack Neutron API service: neutron-api-plugin-arista. * New charms: Trilio The Trilio charms (trilio-data-mover, trilio-dm-api, trilio-horizon-plugin, and trilio-wlm) have been promoted to supported status. These charms deploy TrilioVault, a commercial snapshot and restore solution for OpenStack. * New charm: keystone-kerberos The keystone-kerberos subordinate charm allows for per-domain authentication via a Kerberos ticket, thereby providing an additional layer of security. It is used in conjunction with the keystone charm. * MySQL InnoDB Cluster TLS communication TLS communication between MySQL InnoDB Cluster and its cloud clients is now supported. Due to the circular dependency between the vault and mysql-innodb-cluster applications, this is a post-deployment feature. * Gnocchi S3 support The gnocchi charm can now be configured to use S3 as a storage backend. This feature is available starting with OpenStack Stein. * Charm cinder-ceph supports a new relation When both the nova-compute and cinder-ceph applications are deployed a new relation is now required. This should not affect most currently deployed clouds. * Glance Simplestreams Sync The glance-simplestreams-sync charm now installs simplestreams as a snap. As such, the 'channel' configuration option should be used in place of the ‘source’ option. == OpenStack Charms team == The OpenStack Charms team can be contacted on the #openstack-charms IRC channel on Freenode. == Thank you == Lots of thanks to the below 37 charm contributors who squashed 114 bugs*, enabled support for a new release of OpenStack, improved documentation, and added exciting new functionality! Alex Kavanagh Aurelien Lourot James Page Peter Matulis Liam Young Hervé Beraud Corey Bryant Frode Nordahl David Ames Ryan Beisner Chris MacNaughton Dmitrii Shcherbakov Drew Freiberger Edward Hope-Morley Facundo Ciccioli Andreas Jaeger Pedro Guimarães Nobuto Murata Arif Ali Felipe Reyes Ponnuvel Palaniyappan Brett Alvaro Uria Marco Filipe Moutinho da Silva Alejandro Santoyo Gonzalez Camille Rodriguez oliveiradan Tiago Pasqualini Erlon R. Cruz Trent Lloyd Nikolay Vinogradov Andrew McLeod Mauricio Faria de Oliveira Vern Hart Jeff Hillman Rodrigo Barbieri Nicolas Bock * The contributor and bug numbers are based on the OpenStack Victoria development cycle. -- OpenStack Charms Team

1 0

[oslo] vPTG scheduling
by Ben Nemec 13 Aug '20

13 Aug '20

Continuing my policy of EAFP scheduling, I've signed us up for two hours starting at our regular meeting time. This has worked well for our past couple of virtual events so I didn't see any reason to change it. If that time doesn't work for you, please let me know ASAP so we can make alternate arrangements. Thanks. -Ben

1 0

[PTL][SIG][TC] vPTG October 2020 Team Signup
by Kendall Nelson 13 Aug '20

13 Aug '20

Greetings! As you hopefully already know, our next PTG will be virtual again, and held from Monday October 26th to Friday October 30th. We will have the same schedule set up available as last time with three windows of time spread across the day to cover all timezones with breaks in between. *To signup your team, you must complete **BOTH** the survey[1] AND reserve time in the ethercalc[2] by September 11th at 7:00 UTC.* We ask that the PTL/SIG Chair/Team lead sign up for time to have their discussions in with 4 rules/guidelines. 1. Cross project discussions (like SIGs or support project teams) should be scheduled towards the start of the week so that any discussions that might shape those of other teams happen first. 2. No team should sign up for more than 4 hours per UTC day to help keep participants actively engaged. 3. No team should sign up for more than 16 hours across all time slots to avoid burning out our contributors and to enable participation in multiple teams discussions. Again, you need to fill out BOTH the ethercalc AND the survey to complete your team's sign up. If you have any issues with signing up your team, due to conflict or otherwise, please let me know! While we are trying to empower you to make your own decisions as to when you meet and for how long (after all, you know your needs and teams timezones better than we do), we are here to help! Once your team is signed up, please register! And remind your team to register! Registration is free, but since it will be how we contact you with passwords, event details, etc. it is still important! Continue to check back for updates at openstack.org/ptg. -the Kendalls (diablo_rojo & wendallkaters) [1] Team Survey: https://openstackfoundation.formstack.com/forms/june2020_virtual_ptg_survey [2] Ethercalc Signup: https://ethercalc.openstack.org/126u8ek25noy [3] PTG Registration: https://october2020ptg.eventbrite.com

2 3

Running OpenStack? Take the 2020 User Survey now!
by Allison Price 13 Aug '20

13 Aug '20

Hi everyone, There is only one week left before we are closing the 2020 OpenStack User Survey [1]! If you are running OpenStack, please take a few minutes to log your deployment—all information will remain anonymous unless you indicate otherwise. If you have completed a User Survey before, all you have to do is update your information and answer a few new questions. Anonymous feedback will be passed along to the upstream project teams, and anonymized data will be available in the analytics dashboard [2]. The deadline to add your deployment to this round of analysis is Thursday, August 20. Let me know if you have any questions or issues completing. Thanks! Allison [1] https://www.openstack.org/user-survey/survey-2020 <https://www.openstack.org/user-survey/survey-2020> [2] https://www.openstack.org/analytics <https://www.openstack.org/analytics>

1 0

Community Voting for The Virtual Summit Sessions is Open!
by Ashlee Ferguson 13 Aug '20

13 Aug '20

Community voting for the virtual Open Infrastructure Summit sessions is open! You can VOTE HERE <https://www.openstack.org/summit/2020/vote-for-presentations>, but what does that mean? Now that the Call for Presentations has closed, all submissions are available for community vote and input. After community voting closes, the volunteer Programming Committee members will receive the results to review to help them determine the final selections for Summit schedule. While community votes are meant to help inform the decision, Programming Committee members are expected to exercise judgment in their area of expertise and help ensure diversity of sessions and speakers. View full details of the session selection process <https://www.openstack.org/summit/2020/vote-for-presentations/selection-proc…>. In order to vote, you need an OSF community membership. If you do not have an account, please create one by going to openstack.org/join <https://www.openstack.org/join>. If you need to reset your password, you can do that here <https://www.openstack.org/Security/lostpassword>. Hurry, voting closes Monday, August 17 at 11:59pm Pacific Time. Don’t forget to Register for the Summit <https://openinfrasummit2020.eventbrite.com/> for free! Visit https://www.openstack.org/summit/2020/ <https://www.openstack.org/summit/2020/> for all other Summit-related information. Interested in sponsoring? Visit this page <https://www.openstack.org/summit/2020/sponsors/>. If you have any questions, please email summit(a)openstack.org <mailto:summit@openstack.org>. Cheers, Ashlee Ashlee Ferguson Community & Events Coordinator OpenStack Foundation

1 0

DNS server instead of /etc/hosts file on Infra Server
by pwm 13 Aug '20

13 Aug '20

Hi, Anyone interested in replacing the /etc/hosts file entry with a DNS server on the openstack-ansible deployment? Thank you

2 3

[openstackclient] Implementing nova migration cmds in OSC
by jayaditya gupta 13 Aug '20

13 Aug '20

Hello , i am trying to implement some nova migrations commands to openstackclient. Commands 1. migration-list : list all migrations ever happened 2. server-migration-list : Get the migrations list of specified server 3. server-migration-show : show currently going on migration of specified server. 4. live migration abort feature 5.live-migration-force-complete Please have a look at this patch : https://review.opendev.org/#/c/742210/ and share your insight, what should be the correct way to implement it ? should it be a root command or part of the openstack server migrate command? Best Regards Jayaditya Gupta

1 0

[gate][keystone] *-grenade-multinode jobs failing with UnicodeDecodeError in keystone
by melanie witt 13 Aug '20

13 Aug '20

Howdy all, FYI the *-grenade-multinode gate jobs are currently failing with the following error in keystone: UnicodeDecodeError: 'utf-8' codec can't decode byte 0x87 in position 3: invalid start byte This appears to be an issue with a new default data format in msgpack v1.0 [1] which was brought in by a recent bump of upper constraints [2]. *-grenade-multinode jobs are affected because they test a rolling upgrade where the controller is upgraded to the N release version but one compute node is on the N-1 release version. It looks like cached keystone tokens being used by the N-1 node are erroring out during msgpack unpacking because they are in the old data format and msgpack v1.0 has a new default data format. I've opened a bug [3] about and I'm trying out the following keystone patch to fix it: https://review.opendev.org/745752 Reviews appreciated. If this is not the best approach or if this affects other projects as well, alternatively we could revert the upper constraint bump to msgpack v1.0 while we figure out the best fix. Cheers, -melanie [1] https://github.com/msgpack/msgpack-python/blob/v1.0.0/README.md#major-break… [2] https://review.opendev.org/#/c/745437/2/upper-constraints.txt@373 [3] https://launchpad.net/bugs/1891244

2 4

[tc][oslo] Move etcd3gw to OpenStack?
by Radosław Piliszek 12 Aug '20

12 Aug '20

Hey, Folks! I see it has been kinda proposed already [1] so that's mostly why I am asking about that now. >From what I understand, etcd3gw is our best bet when trying to get coordination with etcd3. However, it has recently released a broken release [2] due to no testing (not to mention gating with tooz). I think it could benefit from OpenDev's existing tooling. And since OpenStack is an important client of it and OpenStack preferring this client, it might be wise to put it in that namespace already. I guess the details would have to be discussed with dims (current owner) himself but he seemed happy about it in [1]. I'm notifying oslo as well as this would probably live best finally under oslo governance. Please let me know if any of the above is not true, so that I can amend my knowledge. :-) [1] https://github.com/dims/etcd3-gateway/issues/29 [2] https://bugs.launchpad.net/kolla-ansible/+bug/1891314 -yoctozepto

2 1

[largescale-sig] Next meeting: August 12, 16utc
by Thierry Carrez 12 Aug '20

12 Aug '20

Hi everyone, In order to accommodate US members, the Large Scale SIG recently decided to rotate between an EU-APAC-friendly time and an US-EU-friendly time. Our next meeting will be the first US-EU meeting, on Wednesday, August 12 at 16 UTC[1] in the #openstack-meeting-3 channel on IRC: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20200812T16 Feel free to add topics to our agenda at: https://etherpad.openstack.org/p/large-scale-sig-meeting A reminder of the TODOs we had from last meeting, in case you have time to make progress on them: - amorin to add some meat to the wiki page before we push the Nova doc patch further - all to describe briefly how you solved metrics/billing in your deployment in https://etherpad.openstack.org/p/large-scale-sig-documentation Talk to you all on Wednesday, -- Thierry Carrez

2 2

[tc] weekly summary
by Mohammed Naser 12 Aug '20

12 Aug '20

Hi everyone, Here’s an update for what happened in the OpenStack TC this week. You can get more information by checking for changes in openstack/governance repository. We've also included a few references to some important mailing list threads that you should check out. # Patches ## Open Reviews - Create starter-kit:kubernetes-in-virt tag https://review.opendev.org/736369 - Move towards dual office hours https://review.opendev.org/745201 - Clean up expired i18n SIG extra-ATCs https://review.opendev.org/745565 - Resolution to define distributed leadership for projects https://review.opendev.org/744995 - Move towards single office hour https://review.opendev.org/745200 - Add legacy repository validation https://review.opendev.org/737559 - Drop all exceptions for legacy validation https://review.opendev.org/745403 - [draft] Add assert:supports-standalone https://review.opendev.org/722399 - Clean up expired i18n SIG extra-ATCs https://review.opendev.org/745565 - Add legacy repository validation https://review.opendev.org/737559 - Pierre Riteau as CloudKitty PTL for Victoria https://review.opendev.org/745653 - Resolution to define distributed leadership for projects https://review.opendev.org/744995 - Create starter-kit:kubernetes-in-virt tag https://review.opendev.org/736369 - Move towards dual office hours https://review.opendev.org/745201 - Move towards single office hour https://review.opendev.org/745200 ## Project Updates - Deprecate os_congress project https://review.opendev.org/742533 - Add Ceph iSCSI charm to OpenStack charms https://review.opendev.org/744480 - Add Keystone Kerberos charm to OpenStack charms https://review.opendev.org/743769 - Add python-dracclient to be owned by Hardware Vendor SIG https://review.opendev.org/745564 ## General Changes - Reverse sort series in selected goals https://review.opendev.org/744897 - Declare supported runtimes for Wallaby release https://review.opendev.org/743847 - Sort SIG names in repo owner list https://review.opendev.org/745563 - Drop neutron-vpnaas from legacy projects https://review.opendev.org/745401 ## Abandoned Changes - Migrate testing to ubuntu focal https://review.opendev.org/740851 # Email Threads - CloudKitty Status: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016171.html - OSC vs python-*clients: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016409.h… - Proposed Wallaby Schedule: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016391.h… - New Office Hour Plans: http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016372.h… # Other Reminders - Cycle-Trailing Release Deadline Aug 13 Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[tc] monthly meeting summary
by Mohammed Naser 12 Aug '20

12 Aug '20

Hi everyone, Here’s a summary of what happened in our TC monthly meeting last Thursday, August 6. # ATTENDEES (LINES SAID) - mnaser (100) - gmann (43) - diablo_rojo (20) - jungleboyj (16) - belmoreira (10) - evrardjp (8) - fungi (6) - zaneb (4) - knikolla (4) - njohnston (3) # MEETING SUMMARY 1. Rollcall (mnaser, 14:00:21) 2. Follow up on past action items (mnaser, 14:02:16) - https://review.opendev.org/#/c/744995/ (diablo_rojo, 14:03:14) - http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016336.h… (gmann, 14:03:24) 3. OpenStack User-facing APIs and CLIs (belmoreira) (mnaser, 14:25:52) 4. W cycle goal selection start (mnaser, 14:34:39) 5. Completion of retirement cleanup (gmann) (mnaser, 14:40:48) - https://etherpad.opendev.org/p/tc-retirement-cleanup (mnaser, 14:41:02) - https://review.opendev.org/#/c/739291/1 (gmann, 14:42:17) - https://review.opendev.org/#/q/topic:cleanup-retirement+(status:open+OR+sta… (gmann, 14:42:51) # ACTION ITEMS - TC members to follow up and review "Resolution to define distributed leadership for projects" - mnaser schedule session with sig-arch and k8s steering committee - gmann continue to audit and clean-up tags - mnaser propose change to implement weekly meetings - njohnston and mugsie to work on getting goals groomed/proposed for W cycle - belmoreira start discussion around openstack user-facing apis & clis - gmann to merge changes to properly retire projects To read the full logs of the meeting, please refer to http://eavesdrop.openstack.org/meetings/tc/2020/tc.2020-08-06-14.00.log.html Thank you, Mohammed -- Mohammed Naser VEXXHOST, Inc.

1 0

Re: [Release-job-failures] Release of openstack/python-glanceclient for ref refs/tags/3.1.2 failed
by Sean McGinnis 12 Aug '20

12 Aug '20

On 8/12/20 4:36 AM, zuul(a)openstack.org wrote: > Build failed. > > - openstack-upload-github-mirror https://zuul.opendev.org/t/openstack/build/cba5dda29e8744059d637a97f358c59f : SUCCESS in 43s > - release-openstack-python https://zuul.opendev.org/t/openstack/build/b9628cf4f28d4bea95844539295ff520 : SUCCESS in 2m 54s > - announce-release https://zuul.opendev.org/t/openstack/build/9f9a5910815247049bf02ab612781620 : FAILURE in 24m 20s > - propose-update-constraints https://zuul.opendev.org/t/openstack/build/44353ec832794af2965e7e2d05d63442 : SUCCESS in 3m 28s announce-release job appears to have failed due to a temporary network issue accessing PyPi packages. Since the release announcement is not critical, no further action is needed. Sean

1 0

[oslo.cache][keystonemiddleware] enable-sasl-protocol
by Brin Zhang(张百林) 12 Aug '20

12 Aug '20

Hi all, we would like to enable sasl protocol to oslo.cache and keystonemiddleware<https://review.opendev.org/#/projects/openstack/keystonemiddleware,dashboar…> project to improve the security of authority. SASL(Simple Authentication and Security Layer): is a memchanism used to extend the verification ability of C/S mode. SASL is only the authentication process, which integrates the application layer and the system authentication mechanism. Need to review patches: https://review.opendev.org/#/q/status:open++branch:master+topic:bp/enable-s… brinzhang

2 1

[horizon][dashboard] Disable admin and identity dashboard panel for user role
by Amjad Kotobi 12 Aug '20

12 Aug '20

Hi, I’m trying to customise view level of dashboard to users with “User” role in keystone, by that I meant to disable “admin” + “identity” panels for users, but when I’m adding “DISABLED = True” to admin panel, it will disable panel for admin and user roles. Is there any way to disable “admin” & “identity” panels only for user role? Installed openstack-dashboard openstack-dashboard-16.2.0-1.el7 Thanks Amjad

2 1

[keystone] Weekly meeting cancelled today
by Nikolla, Kristi 11 Aug '20

11 Aug '20

Hi all, There are no items in today's weekly meeting agenda, and I'm unavailable to host/attend it due to a scheduling conflict. Therefore we can go ahead and cancel today's meeting. Thank you, and sorry for any inconvenience Kristi Nikolla

1 0

[all] [dev&ops] Early warning about new "stable" ansible releases
by Radosław Piliszek 11 Aug '20

11 Aug '20

Hiya Folks, Ansible 2.8.14 and 2.9.12 change the default mode, that created files will get, from 0666 (with umask; which would usually produce 0644) to 0600. [1] Kolla-Ansible got hit by it, and Zuul relies on Ansible so might pick it up at some point, possibly causing some little havoc for all of us. [1] https://github.com/ansible/ansible/issues/71200 -yoctozepto

1 0

[sigs][vendors] Proposal to create Hardware Vendor SIG
by Sean McGinnis 11 Aug '20

11 Aug '20

Hey everyone, OpenStack is a community for creating open source software, but by the nature of infrastructure management, there is a strong intersection with hardware, and therefore hardware vendors. Nova, Cinder, Neutron, Ironic, and many others need to interact with hardware and support vendor specific drivers for this interaction. There is currently a spectrum where some of this hardware interaction is done as openly as possible, while others develop their integration "glue" behind closed doors. Part of this is the disconnect between the fully open development of OpenStack, and the traditionally proprietary development of many products. For those that do want to do their vendor-specific development as openly as possible - and hopefully attract the involvement of customers, partners, and others in the community - there hasn't been a great venue for this so far. Some vendors that have done open development have even had difficulty finding a place in the community and ended up deciding to just develop behind closed doors. I would like to try to change this, so I am proposing the creation of the Hardware Vendor SIG as a place where we can collaborate on vendor specific things, and encourage development to happen in the open. This would be a place for any vendors and interested parties to work together to fix bugs, implement features, and overall improve the quality of anything that helps provide that glue to bridge the gap between our open source services and vendor hardware. This would include servers, storage, networking, and really anything else that plays a role in being able to set up an OpenStack cloud. This is a call out to any others interested in participating. If you are interested in this effort, and if you have any existing code (whether hosted on OpenDev, hosted on GitHub, or hosted on your own platform) that you think would be a good fit for this, please add your contact information and any relevant details here: https://etherpad.opendev.org/p/HardwareVendorSIG Also, please feel free to show your support by voting on the proposal to create this SIG here: https://review.opendev.org/#/c/745185/ Thanks! Sean

3 2

[Ironic] User Survey question
by Julia Kreger 11 Aug '20

11 Aug '20

Greetings awesome Artificial Intelligences and fellow humanoid carbon units! This week I need to submit the question for the 2021 user survey. We discussed this some during our weekly IRC meeting today.[0] Presently, the question is: "Ironic: What would you find most useful if it was part of ironic?" I'd like to propose we collect more data in order to enable us to make informed decisions for features and maintenance work moving forward. While this is long term thinking, I'm wondering if operators would be interested in collecting and submitting some basic data or using a tool, to submit anonymous usage data so we can gain insight into hardware types in use, numbers of machines, which interfaces are used, etc. So I'm thinking something along the lines of: "Ironic: Would you be willing to submit anonymous usage statistics (Number of nodes, conductors, which drivers are in use, etc) if such a tool existed? Yes/No/Not Applicable" Thoughts? Feelings? Concerns? Other ideas? -Julia [0]: http://eavesdrop.openstack.org/meetings/ironic/2020/ironic.2020-08-10-15.00…

7 8

[neutron] bug deputy report August 3 - 9
by Miguel Lavalle 11 Aug '20

11 Aug '20

Critical ====== https://bugs.launchpad.net/neutron/+bug/1890445 [ovn] Tempest test test_update_router_admin_state failing very often. NEEDS OWNER https://bugs.launchpad.net/neutron/+bug/1890493 Periodic job neutron-ovn-tempest-ovs-master-fedora is failing 100% of times. SEEMS TO NEED AN OWNER High ==== https://bugs.launchpad.net/neutron/+bug/1890269 Fullstack test neutron.tests.fullstack.test_logging.TestLogging is failing on Ubuntu Focal. Proposed fix: https://review.opendev.org/#/c/734304/ https://bugs.launchpad.net/neutron/+bug/1890297 CI grenade jobs failing. Proposed fix: https://review.opendev.org/#/c/744753/1. Fix released https://bugs.launchpad.net/neutron/+bug/1890400 Default gateway in HA router namespace not set if using Keepalived 1.x. Awaiting patch from Slawek https://bugs.launchpad.net/neutron/+bug/1890353 support pyroute2 0.5.13. Awaiting patch from Rodolfo https://bugs.launchpad.net/neutron/+bug/1890432 Create subnet is failing under high load with OVN. WIP fix: https://review.opendev.org/#/c/745330/ Medium ====== https://bugs.launchpad.net/neutron/+bug/1890539 failed to create port with security group of other tenant. Proposed fix: https://review.opendev.org/#/c/745089

1 0

Re: [Openstack-mentoring] Neutron subnet with DHCP relay - continued
by Amy Marrich 11 Aug '20

11 Aug '20

Hey Tom, Adding the OpenStack discuss list as I think you got several replies from there as well. Thanks, Amy (spotz) On Mon, Jul 13, 2020 at 5:37 PM Thomas King <thomas.king(a)gmail.com> wrote: > Good day, > > I'm bringing up a thread from June about DHCP relay with neutron networks > in Ironic, specifically using unicast relay. The Triple-O docs do not have > the plain config/neutron config to show how a regular Ironic setup would > use DHCP relay. > > The Neutron segments docs state that I must have a unique physical network > name. If my Ironic controller has a single provisioning network with a > single physical network name, doesn't this prevent my use of multiple > segments? > > Further, the segments docs state this: "The operator must ensure that > every compute host that is supposed to participate in a router provider > network has direct connectivity to one of its segments." (section 3 at > https://docs.openstack.org/neutron/pike/admin/config-routed-networks.html#p… - > current docs state the same thing) > This defeats the purpose of using DHCP relay, though, where the Ironic > controller does *not* have direct connectivity to the remote segment. > > Here is a rough drawing - what is wrong with my thinking here? > Remote server: 10.146.30.32/27 VLAN 2116<-----> Router with DHCP relay > <------> Ironic controller, provisioning network: 10.146.29.192/26 VLAN > 2115 > > Thank you, > Tom King > _______________________________________________ > openstack-mentoring mailing list > openstack-mentoring(a)lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-mentoring >

3 12

[tripleo][ansible] the current action plugins use patterns are suboptimal?
by Bogdan Dobrelya 10 Aug '20

10 Aug '20

There is a trend of writing action plugins, see [0], for simple things, like just calling a module in a loop. I'm not sure that is the direction TripleO should go. If ansible is inefficient in this sort of tasks without custom python code written, we should fix ansible. Otherwise, what is the ultimate goal of that trend? Is that having only action plugins in roles and playbooks? Please kindly asking the community to stop that, make a step back and reiterate with the taken approach. Thank you. [0] https://review.opendev.org/716108 -- Best regards, Bogdan Dobrelya, Irc #bogdando

5 7

[all] Virtual PTG October 2020 Dates & Registration
by Kendall Nelson 10 Aug '20

10 Aug '20

Hello Everyone! I'm sure you all have been anxiously awaiting the announcement of the dates for the next virtual PTG! After polling the community[1] and balancing the pros and cons, we have decided the PTG will take place the week after the Open Infrastructure Summit[2][3] from October 26th to October 30th, 2020. PTG registration is now open[4]. Like last time, it is free, but we will again be using it to communicate details about the event (schedules, passwords, etc), so please register! Later this week we will send out info about signing up teams. Also, the same as last time, we will have an ethercalc signup and a survey to gather some other data about your team. -the Kendalls (diablo_rojo & wendallkaters) [1] ML Poll for PTG Dates: http://lists.openstack.org/pipermail/openstack-discuss/2020-July/016098.html [2] Summit Site: https://www.openstack.org/summit/2020/ [3] Summit Registration: https://openinfrasummit2020.eventbrite.com [4] PTG Registration: https://october2020ptg.eventbrite.com

1 0

Re: [openstack-community] Octavia :; Unable to create load balancer
by Fabian Zimmermann 10 Aug '20

10 Aug '20

Seems like the flavor is missing or empty '' - check for typos and enable debug. Check if the nova req contains valid information/flavor. Fabian Monika Samal <monika.samal(a)outlook.com> schrieb am Mo., 3. Aug. 2020, 15:46: > It's registered > > Get Outlook for Android <https://aka.ms/ghei36> > ------------------------------ > *From:* Fabian Zimmermann <dev.faz(a)gmail.com> > *Sent:* Monday, August 3, 2020 7:08:21 PM > *To:* Monika Samal <monika.samal(a)outlook.com>; openstack-discuss < > openstack-discuss(a)lists.openstack.org> > *Subject:* Re: [openstack-community] Octavia :; Unable to create load > balancer > > Did you check the (nova) flavor you use in octavia. > > Fabian > > Monika Samal <monika.samal(a)outlook.com> schrieb am Mo., 3. Aug. 2020, > 10:53: > > After Michael suggestion I was able to create load balancer but there is > error in status. > > > > PFB the error link: > > http://paste.openstack.org/show/meNZCeuOlFkfjj189noN/ > ------------------------------ > *From:* Monika Samal <monika.samal(a)outlook.com> > *Sent:* Monday, August 3, 2020 2:08 PM > *To:* Michael Johnson <johnsomor(a)gmail.com> > *Cc:* Fabian Zimmermann <dev.faz(a)gmail.com>; Amy Marrich <amy(a)demarco.com>; > openstack-discuss <openstack-discuss(a)lists.openstack.org>; > community(a)lists.openstack.org <community(a)lists.openstack.org> > *Subject:* Re: [openstack-community] Octavia :; Unable to create load > balancer > > Thanks a ton Michael for helping me out > ------------------------------ > *From:* Michael Johnson <johnsomor(a)gmail.com> > *Sent:* Friday, July 31, 2020 3:57 AM > *To:* Monika Samal <monika.samal(a)outlook.com> > *Cc:* Fabian Zimmermann <dev.faz(a)gmail.com>; Amy Marrich <amy(a)demarco.com>; > openstack-discuss <openstack-discuss(a)lists.openstack.org>; > community(a)lists.openstack.org <community(a)lists.openstack.org> > *Subject:* Re: [openstack-community] Octavia :; Unable to create load > balancer > > Just to close the loop on this, the octavia.conf file had > "project_name = admin" instead of "project_name = service" in the > [service_auth] section. This was causing the keystone errors when > Octavia was communicating with neutron. > > I don't know if that is a bug in kolla-ansible or was just a local > configuration issue. > > Michael > > On Thu, Jul 30, 2020 at 1:39 PM Monika Samal <monika.samal(a)outlook.com> > wrote: > > > > Hello Fabian,, > > > > http://paste.openstack.org/show/QxKv2Ai697qulp9UWTjY/ > > > > Regards, > > Monika > > ________________________________ > > From: Fabian Zimmermann <dev.faz(a)gmail.com> > > Sent: Friday, July 31, 2020 1:57 AM > > To: Monika Samal <monika.samal(a)outlook.com> > > Cc: Michael Johnson <johnsomor(a)gmail.com>; Amy Marrich <amy(a)demarco.com>; > openstack-discuss <openstack-discuss(a)lists.openstack.org>; > community(a)lists.openstack.org <community(a)lists.openstack.org> > > Subject: Re: [openstack-community] Octavia :; Unable to create load > balancer > > > > Hi, > > > > just to debug, could you replace the auth_type password with v3password? > > > > And do a curl against your :5000 and :35357 urls and paste the output. > > > > Fabian > > > > Monika Samal <monika.samal(a)outlook.com> schrieb am Do., 30. Juli 2020, > 22:15: > > > > Hello Fabian, > > > > http://paste.openstack.org/show/796477/ > > > > Thanks, > > Monika > > ________________________________ > > From: Fabian Zimmermann <dev.faz(a)gmail.com> > > Sent: Friday, July 31, 2020 1:38 AM > > To: Monika Samal <monika.samal(a)outlook.com> > > Cc: Michael Johnson <johnsomor(a)gmail.com>; Amy Marrich <amy(a)demarco.com>; > openstack-discuss <openstack-discuss(a)lists.openstack.org>; > community(a)lists.openstack.org <community(a)lists.openstack.org> > > Subject: Re: [openstack-community] Octavia :; Unable to create load > balancer > > > > The sections should be > > > > service_auth > > keystone_authtoken > > > > if i read the docs correctly. Maybe you can just paste your config > (remove/change passwords) to paste.openstack.org and post the link? > > > > Fabian > >

5 16

[puppet][congress] Retiring puppet-congress
by Takashi Kajinami 10 Aug '20

10 Aug '20

Hello, As you know, Congress project has been retired already[1], so we will retire its puppet module, puppet-congress in openstack puppet project as well. [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-April/014292.ht… Because congress was directly retired instead of getting migrated to x namespace, we'll follow the same way about puppet-congress retirement and won't create x/puppet-congress. Thank you for the contribution made for the project ! Please let us know if you have any concerns about this retirement. Thank you, Takashi Kajinami

2 1

[openstack-community] Keystone and DBNonExistent Errors
by Divya K Konoor 10 Aug '20

10 Aug '20

Hi, I am using OpenStack Keystone Stein and run into the below error often where Keystone public process(listening to 5000) is running inside Apache httpd runs into the below. This problem is resolved with a restart of httpd service. Has anyone run into a similar issue ? This is seen soon after httpd is restarted and does not happen all the time. My environment has MariaDB backend. This problem is not limited to the assignment table and is seen across all other tables in Keystone. MariaDB service is functional and all the tables are in place. [Fri Aug 07 08:20:59.936087 2020] [:info] [pid 1420287] mod_wsgi (pid=1420287, process='keystone-public', application=''): Loading WSGI script '/usr/bin/keystone-wsgi-public'. [Fri Aug 07 08:20:59.936089 2020] [:info] [pid 1420288] mod_wsgi (pid=1420288, process='keystone-admin', application=''): Loading WSGI script '/usr/bin/keystone-wsgi-admin'. [Fri Aug 07 08:20:59.943431 2020] [ssl:info] [pid 1420290] [client 1.2.3.95:35762] AH01964: Connection to child 1 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:00.009317 2020] [ssl:info] [pid 1420291] [client 1.2.3.113:60132] AH01964: Connection to child 2 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:01.243594 2020] [ssl:info] [pid 1420289] [client 1.2.3.50:53996] AH01964: Connection to child 0 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:01.386329 2020] [ssl:info] [pid 1420293] [client x.x.x.x:38645] AH01964: Connection to child 4 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:01.824041 2020] [ssl:info] [pid 1420349] [client 1.2.3.101:42974] AH01964: Connection to child 5 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:02.949166 2020] [ssl:info] [pid 1420378] [client 1.2.3.50:54014] AH01964: Connection to child 9 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:02.949172 2020] [ssl:info] [pid 1420379] [client 1.2.3.80:46924] AH01964: Connection to child 10 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:03.286057 2020] [:info] [pid 1420287] mod_wsgi (pid=1420287): Create interpreter '1.2.3.50:5000|'. [Fri Aug 07 08:21:03.287286 2020] [:info] [pid 1420287] [remote 1.2.3.95:156] mod_wsgi (pid=1420287, process='keystone-public', application='1.2.3.50:5000|'): Loading WSGI script '/usr/bin/keystone-wsgi-public'. [Fri Aug 07 08:21:04.675059 2020] [ssl:info] [pid 1420436] [client 1.2.3.50:54032] AH01964: Connection to child 12 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:04.705975 2020] [ssl:info] [pid 1420437] [client 1.2.3.107:59554] AH01964: Connection to child 13 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:06.960940 2020] [ssl:info] [pid 1420438] [client 1.2.3.80:46970] AH01964: Connection to child 14 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:07.661670 2020] [ssl:info] [pid 1420349] [client 1.2.3.50:54124] AH01964: Connection to child 5 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:07.683383 2020] [ssl:info] [pid 1420292] [client x.x.x.x:30065] AH01964: Connection to child 3 established (server 1.2.3.50:5000) [Fri Aug 07 08:21:08.442956 2020] [:error] [pid 1420287] [remote x.x.x.x:144] mod_wsgi (pid=1420287): Exception occurred processing WSGI script '/usr/bin/keystone-wsgi-public'. [Fri Aug 07 08:21:08.443002 2020] [:error] [pid 1420287] [remote x.x.x.x:144] Traceback (most recent call last): [Fri Aug 07 08:21:08.443017 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/flask/app.py", line 2309, in __call__ [Fri Aug 07 08:21:08.443509 2020] [:error] [pid 1420287] [remote x.x.x.x:144] return self.wsgi_app(environ, start_response) [Fri Aug 07 08:21:08.443525 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/werkzeug/contrib/fixers.py", line 152, in __call__ [Fri Aug 07 08:21:08.443630 2020] [:error] [pid 1420287] [remote x.x.x.x:144] return self.app(environ, start_response) [Fri Aug 07 08:21:08.443644 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/webob/dec.py", line 129, in __call__ [Fri Aug 07 08:21:08.443746 2020] [:error] [pid 1420287] [remote x.x.x.x:144] resp = self.call_func(req, *args, **kw) [Fri Aug 07 08:21:08.443756 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/webob/dec.py", line 193, in call_func [Fri Aug 07 08:21:08.443773 2020] [:error] [pid 1420287] [remote x.x.x.x:144] return self.func(req, *args, **kwargs) [Fri Aug 07 08:21:08.443781 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/oslo_middleware/base.py", line 131, in __call__ [Fri Aug 07 08:21:08.443844 2020] [:error] [pid 1420287] [remote x.x.x.x:144] response = req.get_response(self.application) .. ... .... .. [Fri Aug 07 08:21:08.450055 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/dogpile/cache/region.py", line 1216, in creator [Fri Aug 07 08:21:08.450071 2020] [:error] [pid 1420287] [remote x.x.x.x:144] return fn(*arg, **kw) [Fri Aug 07 08:21:08.450080 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/keystone/assignment/core.py", line 128, in get_roles_for_user_and_project [Fri Aug 07 08:21:08.450975 2020] [:error] [pid 1420287] [remote x.x.x.x:144] user_id=user_id, project_id=project_id, effective=True) [Fri Aug 07 08:21:08.450985 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/keystone/common/manager.py", line 116, in wrapped [Fri Aug 07 08:21:08.451001 2020] [:error] [pid 1420287] [remote x.x.x.x:144] __ret_val = __f(*args, **kwargs) [Fri Aug 07 08:21:08.451009 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/keystone/assignment/core.py", line 999, in list_role_assignments [Fri Aug 07 08:21:08.451025 2020] [:error] [pid 1420287] [remote x.x.x.x:144] strip_domain_roles) [Fri Aug 07 08:21:08.451033 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/keystone/assignment/core.py", line 845, in _list_effective_role_assignments [Fri Aug 07 08:21:08.451049 2020] [:error] [pid 1420287] [remote x.x.x.x:144] domain_id=domain_id, inherited=inherited) [Fri Aug 07 08:21:08.451057 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/keystone/assignment/core.py", line 780, in list_role_assignments_for_actor [Fri Aug 07 08:21:08.451072 2020] [:error] [pid 1420287] [remote x.x.x.x:144] group_ids=group_ids, inherited_to_projects=False) [Fri Aug 07 08:21:08.451081 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib/python2.7/site-packages/keystone/assignment/backends/sql.py", line 248, in list_role_assignments [Fri Aug 07 08:21:08.451599 2020] [:error] [pid 1420287] [remote x.x.x.x:144] return [denormalize_role(ref) for ref in query.all()] [Fri Aug 07 08:21:08.451609 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/query.py", line 2925, in all [Fri Aug 07 08:21:08.451632 2020] [:error] [pid 1420287] [remote x.x.x.x:144] return list(self) [Fri Aug 07 08:21:08.451641 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/query.py", line 3081, in __iter__ [Fri Aug 07 08:21:08.451656 2020] [:error] [pid 1420287] [remote x.x.x.x:144] return self._execute_and_instances(context) [Fri Aug 07 08:21:08.451665 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib64/python2.7/site-packages/sqlalchemy/orm/query.py", line 3106, in _execute_and_instances [Fri Aug 07 08:21:08.451683 2020] [:error] [pid 1420287] [remote x.x.x.x:144] result = conn.execute(querycontext.statement, self._params) [Fri Aug 07 08:21:08.451691 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 980, in execute [Fri Aug 07 08:21:08.451711 2020] [:error] [pid 1420287] [remote x.x.x.x:144] return meth(self, multiparams, params) [Fri Aug 07 08:21:08.451720 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib64/python2.7/site-packages/sqlalchemy/sql/elements.py", line 273, in _execute_on_connection [Fri Aug 07 08:21:08.451736 2020] [:error] [pid 1420287] [remote x.x.x.x:144] return connection._execute_clauseelement(self, multiparams, params) [Fri Aug 07 08:21:08.451745 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1099, in _execute_clauseelement [Fri Aug 07 08:21:08.451762 2020] [:error] [pid 1420287] [remote x.x.x.x:144] distilled_params, [Fri Aug 07 08:21:08.451771 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1240, in _execute_context [Fri Aug 07 08:21:08.451786 2020] [:error] [pid 1420287] [remote x.x.x.x:144] e, statement, parameters, cursor, context [Fri Aug 07 08:21:08.451795 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1456, in _handle_dbapi_exception [Fri Aug 07 08:21:08.451810 2020] [:error] [pid 1420287] [remote x.x.x.x:144] util.raise_from_cause(newraise, exc_info) [Fri Aug 07 08:21:08.451818 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib64/python2.7/site-packages/sqlalchemy/util/compat.py", line 296, in raise_from_cause [Fri Aug 07 08:21:08.451834 2020] [:error] [pid 1420287] [remote x.x.x.x:144] reraise(type(exception), exception, tb=exc_tb, cause=cause) [Fri Aug 07 08:21:08.451843 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/base.py", line 1236, in _execute_context [Fri Aug 07 08:21:08.451858 2020] [:error] [pid 1420287] [remote x.x.x.x:144] cursor, statement, parameters, context [Fri Aug 07 08:21:08.451866 2020] [:error] [pid 1420287] [remote x.x.x.x:144] File "/usr/lib64/python2.7/site-packages/sqlalchemy/engine/default.py", line 536, in do_execute [Fri Aug 07 08:21:08.451882 2020] [:error] [pid 1420287] [remote x.x.x.x:144] cursor.execute(statement, parameters) [Fri Aug 07 08:21:08.451923 2020] [:error] [pid 1420287] [remote x.x.x.x:144] DBNonExistentTable: (sqlite3.OperationalError) no such table: assignment [SQL: u'SELECT assignment.type AS assignment_type, assignment.actor_id AS assignment_actor_id, assignment.target_id AS assignment_target_id, assignment.role_id AS assignment_role_id, assignment.inherited AS assignment_inherited \\nFROM assignment \\nWHERE assignment.actor_id IN (?) AND assignment.target_id IN (?) AND assignment.type IN (?) AND assignment.inherited = 0'] [parameters: ('15c2fe91e053af57a997c568c117c908d59c138f996bdc19ae97e9f16df12345', '12345978536e45ab8a279e2b0fa4f947', 'UserProject')] (Background on this error at: http://sqlalche.me/e/e3q8) Regards, Divya

1 0

[ironic][tripleo][ussuri] Problem with bare metal provisioning and old RAID controllers
by Marco Marino 10 Aug '20

10 Aug '20

Hi, I'm trying to install openstack Ussuri on Centos 8 hardware using tripleo. I'm using a relatively old hardware (dell PowerEdge R620) with old RAID controllers, deprecated in RHEL8/Centos8. Here is some basic information: # lspci | grep -i raid 00:1f.2 RAID bus controller: Intel Corporation C600/X79 series chipset SATA RAID Controller (rev 05) 02:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS 2008 [Falcon] (rev 03) I'm able to manually install centos 8 using DUD driver from here -> https://elrepo.org/linux/dud/el8/x86_64/dd-megaraid_sas-07.710.50.00-1.el8_… (basically I add inst.dd and I use an usb pendrive with iso). Is there a way to do bare metal provisioning using openstack on this kind of server? At the moment, when I launch "openstack overcloud node introspect --provide controller1" it doesn't recognize disks (local_gb = 0 in properties) and in inspector logs I see: Jun 22 11:12:42 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:42.261 1543 DEBUG root [-] Still waiting for the root device to appear, attempt 1 of 10 wait_for_disks /usr/lib/python3.6/site-packages/ironic_python_agent/hardware.py:652 Jun 22 11:12:45 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:45.299 1543 DEBUG oslo_concurrency.processutils [-] Running cmd (subprocess): udevadm settle execute /usr/lib/python3.6/site-packages/oslo_concurrency/processutils.py:372 Jun 22 11:12:45 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:45.357 1543 DEBUG oslo_concurrency.processutils [-] CMD "udevadm settle" returned: 0 in 0.058s execute /usr/lib/python3.6/site-packages/oslo_concurrency/processutils.py:409 Jun 22 11:12:45 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:45.392 1543 DEBUG ironic_lib.utils [-] Execution completed, command line is "udevadm settle" execute /usr/lib/python3.6/site-packages/ironic_lib/utils.py:101 Jun 22 11:12:45 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:45.426 1543 DEBUG ironic_lib.utils [-] Command stdout is: "" execute /usr/lib/python3.6/site-packages/ironic_lib/utils.py:103 Jun 22 11:12:45 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:45.460 1543 DEBUG ironic_lib.utils [-] Command stderr is: "" execute /usr/lib/python3.6/site-packages/ironic_lib/utils.py:104 Jun 22 11:12:45 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:45.496 1543 WARNING root [-] Path /dev/disk/by-path is inaccessible, /dev/disk/by-path/* version of block device name is unavailable Cause: [Errno 2] No such file or directory: '/dev/disk/by-path': FileNotFoundError: [Errno 2] No such file or directory: '/dev/disk/by-path' Jun 22 11:12:45 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:45.549 1543 DEBUG oslo_concurrency.processutils [-] Running cmd (subprocess): lsblk -Pbia -oKNAME,MODEL,SIZE,ROTA,TYPE execute /usr/lib/python3.6/site-packages/oslo_concurrency/processutils.py:372 Jun 22 11:12:45 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:45.647 1543 DEBUG oslo_concurrency.processutils [-] CMD "lsblk -Pbia -oKNAME,MODEL,SIZE,ROTA,TYPE" returned: 0 in 0.097s execute /usr/lib/python3.6/site-packages/oslo_concurrency/processutils.py:409 Jun 22 11:12:45 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:45.683 1543 DEBUG ironic_lib.utils [-] Execution completed, command line is "lsblk -Pbia -oKNAME,MODEL,SIZE,ROTA,TYPE" execute /usr/lib/python3.6/site-packages/ironic_lib/utils.py:101 Jun 22 11:12:45 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:45.719 1543 DEBUG ironic_lib.utils [-] Command stdout is: "" execute /usr/lib/python3.6/site-packages/ironic_lib/utils.py:103 Jun 22 11:12:45 localhost.localdomain ironic-python-agent[1543]: 2018-06-22 11:12:45.755 1543 DEBUG ironic_lib.utils [-] Command stderr is: "" execute /usr/lib/python3.6/site-packages/ironic_lib/utils.py:104 Is there a way to solve the issue? For example, can I modify ramdisk and include DUD driver? I tried this guide: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/16… but I don't know how to include an ISO instead of an rpm packet as described in the example. Thank you, Marco

2 3

Openstack VMmachine internet connectivity issue
by Bhartendu 08 Aug '20

08 Aug '20

Hi All, I need help or any pointer to solve Openstack VM machine internet connectivity issue. I am successfully able to create VM machines on Openstack cloud. Facing following Openstack VM machine internet connectivity issues: 1) There is no internet connectivity from Openstack VM machine. 2) ping is successful till Openstack machine (192.168.0.166), but Gateway ip (192.168.0.1) not reachable from Openstack VM machine. 3) No website reachable from Openstack VM machine. Openstack is installed on Virtualbox VM machine (CentOS 8.2). Connectivity information: Internet<=====>Router(192.168.0.1)<=====>Oracle VM machine (CentOS 8.2; 192.168.0.166)<=====>Openstack VM Machine (192.168.0.174) Any help or trigger is much appreciated. ----------------------------------------------- Openstack VM Machine (192.168.0.174) Logs ----------------------------------------------- $ ip route default via 192.168.0.1 dev eth0 169.254.169.254 via 192.168.0.171 dev eth0 192.168.0.0/24 dev eth0 scope link src 192.168.0.174 $ ping 192.168.0.166 PING 192.168.0.166 (192.168.0.166): 56 data bytes 64 bytes from 192.168.0.166: seq=0 ttl=64 time=2.657 ms 64 bytes from 192.168.0.166: seq=1 ttl=64 time=1.196 ms 64 bytes from 192.168.0.166: seq=2 ttl=64 time=1.312 ms 64 bytes from 192.168.0.166: seq=3 ttl=64 time=0.875 ms 64 bytes from 192.168.0.166: seq=4 ttl=64 time=0.782 ms ^C --- 192.168.0.166 ping statistics --- 5 packets transmitted, 5 packets received, 0% packet loss round-trip min/avg/max = 0.782/1.364/2.657 ms $ ping 192.168.0.1 PING 192.168.0.1 (192.168.0.1): 56 data bytes ^C --- 192.168.0.1 ping statistics --- 3 packets transmitted, 0 packets received, 100% packet loss $ ping google.com ping: bad address 'google.com' $ $ sudo cat /etc/resolv.conf nameserver 192.168.0.1 nameserver 192.168.0.166 nameserver 8.8.8.8 $ $ ip route default via 192.168.0.1 dev eth0 169.254.169.254 via 192.168.0.171 dev eth0 192.168.0.0/24 dev eth0 scope link src 192.168.0.174 $ $ ifconfig eth0 Link encap:Ethernet HWaddr FA:16:3E:17:F2:F9 inet addr:192.168.0.174 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::f816:3eff:fe17:f2f9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:572 errors:0 dropped:0 overruns:0 frame:0 TX packets:571 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:51697 (50.4 KiB) TX bytes:46506 (45.4 KiB) lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:35 errors:0 dropped:0 overruns:0 frame:0 TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:3764 (3.6 KiB) TX bytes:3764 (3.6 KiB) $ ----------------------------------------------------- Oracle VM machine (CentOS 8.2; 192.168.0.166) Logs ----------------------------------------------------- [root@openstack ~]# ovs-vsctl show 6718c4ce-6a58-463c-95e4-20a34edbe041 Manager "ptcp:6640:127.0.0.1" is_connected: true Bridge br-int fail_mode: secure datapath_type: system Port br-int Interface br-int type: internal Port "tap50a66e3f-00" Interface "tap50a66e3f-00" Port "patch-br-int-to-provnet-27804412-47c0-497d-8f2e-8c0bf8b04df1" Interface "patch-br-int-to-provnet-27804412-47c0-497d-8f2e-8c0bf8b04df1" type: patch options: {peer="patch-provnet-27804412-47c0-497d-8f2e-8c0bf8b04df1-to-br-int"} Port "tap6ea42aaf-80" Interface "tap6ea42aaf-80" Port "tap743cdf36-c8" Interface "tap743cdf36-c8" Port "tap2a93518d-90" Interface "tap2a93518d-90" Bridge br-ex fail_mode: standalone Port "patch-provnet-27804412-47c0-497d-8f2e-8c0bf8b04df1-to-br-int" Interface "patch-provnet-27804412-47c0-497d-8f2e-8c0bf8b04df1-to-br-int" type: patch options: {peer="patch-br-int-to-provnet-27804412-47c0-497d-8f2e-8c0bf8b04df1"} Port br-ex Interface br-ex type: internal Port "enp0s3" Interface "enp0s3" ovs_version: "2.12.0" [root@openstack ~]# ip a s enp0s3 2: enp0s3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel master ovs-system state UP group default qlen 1000 link/ether 08:00:27:cd:fc:4f brd ff:ff:ff:ff:ff:ff [root@openstack ~]# ip a s br-ex 13: br-ex: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000 link/ether 08:00:27:cd:fc:4f brd ff:ff:ff:ff:ff:ff inet 192.168.0.166/24 brd 192.168.0.255 scope global br-ex valid_lft forever preferred_lft forever inet6 fe80::f057:6bff:fe69:1f47/64 scope link valid_lft forever preferred_lft forever [root@openstack ~]# [root@openstack ~]# cat /etc/resolv.conf # Generated by NetworkManager search example.com nameserver 192.168.0.1 nameserver 8.8.8.8 [root@openstack ~]# [root@openstack ~]# ip route default via 192.168.0.1 dev br-ex 169.254.0.0/16 dev br-ex scope link metric 1013 192.168.0.0/24 dev br-ex proto kernel scope link src 192.168.0.166 [root@openstack ~]# [root@openstack ~]# ifconfig br-ex: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 192.168.0.166 netmask 255.255.255.0 broadcast 192.168.0.255 inet6 fe80::f057:6bff:fe69:1f47 prefixlen 64 scopeid 0x20<link> ether 08:00:27:cd:fc:4f txqueuelen 1000 (Ethernet) RX packets 2781 bytes 505203 (493.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1441 bytes 159474 (155.7 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 08:00:27:cd:fc:4f txqueuelen 1000 (Ethernet) RX packets 94856 bytes 111711956 (106.5 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 33859 bytes 15114156 (14.4 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 1741807 bytes 441610166 (421.1 MiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1741807 bytes 441610166 (421.1 MiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tap2a93518d-90: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::681d:e6ff:fe1d:963f prefixlen 64 scopeid 0x20<link> ether 6a:1d:e6:1d:96:3f txqueuelen 1000 (Ethernet) RX packets 55 bytes 6540 (6.3 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2950 bytes 916693 (895.2 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tap50a66e3f-00: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1442 ether fe:16:3e:06:df:bf txqueuelen 1000 (Ethernet) RX packets 689 bytes 59074 (57.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 703 bytes 58933 (57.5 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tap6ea42aaf-80: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet6 fe80::745b:6aff:fe1c:d270 prefixlen 64 scopeid 0x20<link> ether 76:5b:6a:1c:d2:70 txqueuelen 1000 (Ethernet) RX packets 63 bytes 7332 (7.1 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 126 bytes 10692 (10.4 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 tap743cdf36-c8: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether fe:16:3e:17:f2:f9 txqueuelen 1000 (Ethernet) RX packets 1005 bytes 91770 (89.6 KiB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 3555 bytes 902987 (881.8 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 [root@openstack ~]# Thanks & Regards

1 0

[TC] New Office Hour Plans
by Kendall Nelson 07 Aug '20

07 Aug '20

Hello! After taking a look at the poll results, Mohammed and I have two proposed plans for office hours: Plan A: Two office hours instead of three. This gives us slightly more coverage than one office hour without overextending ourselves to cover three office hours. Mohammed and I were thinking that one of the reasons why three office hours wasn't working was that it was kind of a big time commitment and TC members could easily rationalize not going to ones later in the week if they had already attended one earlier in the week. The two times that enable most TC members to attend at least one, if not both, would be Monday @14:00 UTC (TC members available: Belmiro, Rico, Kristi, Jay, Mohammed, myself, and Nate + non members) and Wednesday @ 15:00 UTC (TC members available: Rico, Kristi, Jay, Mohammed, myself, Ghanshyam, and Nate + non members). Plan B: Move to a single office hour on Wednesday @ 15:00 UTC (TC members available: Rico, Kristi, Jay, Mohammed, myself, Ghanshyam, and Nate + non members). Having only one office hour gives it more weight and importance and that should hopefully encourage more attendance from both community members and TC members alike. I guess Plan C is to go ahead with Plan A and then if we don't see activity during the Monday time slot, to reduce down to one office hour and go with Plan B. Please check out the patches Mohammed posted [1][2] and vote on what you'd prefer! -Kendall (diablo_rojo) [1] Dual Office Hour: https://review.opendev.org/#/c/745201/ [2] Single Office Hour: https://review.opendev.org/#/c/745200/

4 3

Helping out with CloudKitty maintenance
by Pierre Riteau 07 Aug '20

07 Aug '20

Hello, Following the discussion about the state of CloudKitty [1], I would like to volunteer my help with maintaining the project, as no one of the core team appears to be active at the moment. I have been working with CloudKitty for about a year and have used both the Gnocchi and Monasca collectors. Being a core reviewer on two other OpenStack projects, I am familiar with the process of maintaining OpenStack code. Would it be possible to get core reviewer privileges to help? I would initially focus on keeping CI green and making sure bug fixes are merged and backported. Thanks in advance, Pierre Riteau (priteau) [1] http://lists.openstack.org/pipermail/openstack-discuss/2020-August/016384.h…

2 1

[nova] Nova PTL is on PTO until 24th of Aug
by Balázs Gibizer 07 Aug '20

07 Aug '20

Hi, I will be on vacation during the next two weeks. Cheers, gibi

1 0

[openstack-community] [infra] Problem with ask.openstack.org
by Bernd Bausch 07 Aug '20

07 Aug '20

While ask.openstack.org is not necessarily loved by many, it continues to be used, and there are still people who answer questions. Recently, one of its features ceased working. I am talking about the "responses" page that lists all responses to questions that I have answered or commented on. This makes it very hard to follow up on such questions; I don't have a tool to see if somebody anwered my question or is the person who asked a question has provided updates. Is there anybody who can fix this? I know that some people would like to do away with ask.openstack.org entirely, since the software is bug-ridden and nobody manages the site. My personal opinion is that the current situation is worse than no "ask" site at all, since people might ask questions, get partial answers and no follow-up. This can create a negative view of the OpenStack community. In short, either fix it or remove it. Unfortunately I don't have the means to do either. Bernd.

4 4

[neutron][OVS firewall] Multicast non-IGMP traffic is allowed by default, not in iptables FW (LP#1889631)
by Rodolfo Alonso Hernandez 07 Aug '20

07 Aug '20

Hello all: First of all, the link: https://bugs.launchpad.net/neutron/+bug/1889631 To sum up the bug: in iptables FW, the non-IGMP multicast traffic from 224.0.0.x was blocked; this is not happening in OVS FW. That was discussed today in the Neutron meeting today [1]. We face two possible situations here: - If we block this traffic now, some deployments using the OVS FW will experience an unexpected network blockage. - Deployments migrating from iptables to OVS FW, now won't be able to explicitly allow this traffic (or block it by default). This also breaks the current API, because some rules won't have any effect (those ones allowing this traffic). A possible solution is to add a new knob in the FW configuration; this config option will allow to block or not this traffic by default. Remember that the FW can only create permissive rules, not blocking ones. Any feedback is welcome! Regards. [1] http://eavesdrop.openstack.org/meetings/networking/2020/networking.2020-08-…

2 2

[tacker] PTL on vacation
by Yasufumi Ogawa 07 Aug '20

07 Aug '20

I will be on vacation from 10th to 17th Aug. I would like to skip the next IRC meeting because many of tacker members are also on vacation next week. Thanks, Yasufumi

1 0

Openstack-Train VCPU issue in Hyper-V
by its-openstack＠zohocorp.com 07 Aug '20

07 Aug '20

Dear Team, We are using Openstack-Train in our organization.We have created windows server 2016 Std R2 instances with this flavor m5.xlarge ( RAM - 65536 , Disk - 500 , VCPUs - 16 ).Once Hyper-V future enabled in this instances VCPU count is automatically reduced to 1 core after restart.Even we have enabled nested virtualisation in openstack compute server.Herewith attached screenshot for your references.Please help us to short out this issue. #cat /sys/module/kvm_intel/parameters/nested Y Regards, Sysadmin.

1 0

[ironic] [infra] bifrost-integration-tinyipa-opensuse-15 broken
by Dmitry Tantsur 06 Aug '20

06 Aug '20

Hi folks, Our openSUSE CI job has been broken for a few days [1]. It fails on the early bindep stage with [2] <download url=" https://mirror.mtl01.inap.opendev.org/opensuse/distribution/leap/15.1/repo/…" percent="-1" rate="-1"/> <download url=" https://mirror.mtl01.inap.opendev.org/opensuse/distribution/leap/15.1/repo/…" rate="-1" done="0"/> <message type="error">File './suse/x86_64/libJudy1-1.0.5-lp151.2.2.x86_64.rpm' not found on medium ' https://mirror.mtl01.inap.opendev.org/opensuse/distribution/leap/15.1/repo/… ;</message> I've raised it on #openstack-infra, but I'm not sure if there has been any follow up. Help is appreciated Dmitry [1] https://zuul.openstack.org/builds?job_name=bifrost-integration-tinyipa-open… [2] https://zuul.openstack.org/build/f4c7d174d171482394d1d0754c863ae1/console

3 2

[cinder] Could you help me review the reimage feature?
by Rambo 06 Aug '20

06 Aug '20

Hi,all:         I have a spec which is support volume backed server rebuild[0].This spec was accepted in Stein, but some of the work did not finish, so repropose it for Victoria.  I sincerely wish this spec will approved in Victoria, so I make an exception for this, and the Nova team will approved this if the cinder reimage question is solved this week[1].  This spec is depend on the cinder reimage api [2], and the reimage api has a question. We just need to know if cinder are ok with the change in polling to event like the volume extend. More clearly, Cinder reimage should add a new 'volume-reimage' external event like the volume extend, so that nova can wait for cinder to complete the reimage[3].        The Cinder code is[4], if you have some ideas, you can comments on it.Thank you very much! Ref: [0]:https://blueprints.launchpad.net/nova/+spec/volume-backed-server-rebuild [1]:http://eavesdrop.openstack.org/irclogs/%23openstack-meeting-3/%23opensta… [2]:https://blueprints.launchpad.net/cinder/+spec/add-volume-re-image-api [3]:https://review.opendev.org/#/c/454287/ [4]:https://review.opendev.org/#/c/606346/ Best Regards Rambo

2 1

[TripleO] "bundle install" in puppet-tripleo
by Pete Zaitcev 06 Aug '20

06 Aug '20

Hello: Due to some circumstances, I started looking at running unit tests in puppet-tripleo. The official document[1] tells me to start by running "bundle install". This results in: [zaitcev@suzdal puppet-tripleo-c744015]$ bundle install Fetching https://git.openstack.org/openstack/puppet-openstack_spec_helper Fetching gem metadata from https://rubygems.org/........ Resolving dependencies........ Fetching rake 13.0.1 ....... Installing netaddr 1.5.1 Using pathspec 0.2.1 <--------------------- in black, not green Fetching pry 0.12.2 ....... Installing webmock 3.8.3 Using puppet-openstack_spec_helper 17.0.0 from https://git.openstack.org/openstack/puppet-openstack_spec_helper (at master@273d24f) Updating files in vendor/cache Could not find pathspec-0.2.1.gem for installation [zaitcev@suzdal puppet-tripleo-c744015]$ Anyone got an idea what the above means? -- Pete [1] https://docs.openstack.org/puppet-openstack-guide/latest/contributor/testin…

1 0

[tripleo][ci] Make tripleo-ci-centos-8-containerized-undercloud-upgrades voting again
by Sergii Golovatiuk 06 Aug '20

06 Aug '20

Hi, tripleo-ci-centos-8-containerized-undercloud-upgrades has been improved significantly in terms of stability [1]. To improve CI coverage for upgrades I propose to make it voting. That will help to make upgrades more stable and catch bugs as early as possible. To keep it stable, Upgrade team is going to add it to their own triage process and dedicate the engineer to fix it if it's red for 2-3 days in a row. [1] https://zuul.opendev.org/t/openstack/builds?job_name=tripleo-ci-centos-8-co… -- Sergii Golovatiuk Senior Software Developer Red Hat <https://www.redhat.com/> <https://www.redhat.com/>

3 2

[tripleo] Overcloud without provisioning error: os-net-config command not found
by Marco Marino 06 Aug '20

06 Aug '20

Hi, I'm trying to deploy an overcloud using pre-provisioned nodes. I have only 2 nodes, 1 compute and 1 controller and here is the command I'm using: openstack overcloud deploy --templates --disable-validations -e /usr/share/openstack-tripleo-heat-templates/environments/deployed-server-environment.yaml -e /home/stack/templates/node-info.yaml -e /home/stack/templates/ctlplane-assignments.yaml -e /home/stack/templates/hostname-map.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-isolation.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/network-environment.yaml -e /usr/share/openstack-tripleo-heat-templates/environments/net-single-nic-with-vlans.yaml -n /home/stack/os-deploy-custom-config/network_data.yaml --overcloud-ssh-user stack --overcloud-ssh-key /home/stack/.ssh/id_rsa Here is the content of custom files: (undercloud) [stack@undercloud ~]$ cat templates/node-info.yaml parameter_defaults: OvercloudControllerFlavor: control OvercloudComputeFlavor: compute ControllerCount: 1 ComputeCount: 1 (undercloud) [stack@undercloud ~]$ cat templates/ctlplane-assignments.yaml resource_registry: OS::TripleO::DeployedServer::ControlPlanePort: /usr/share/openstack-tripleo-heat-templates/deployed-server/deployed-neutron-port.yaml parameter_defaults: DeployedServerPortMap: controller-0-ctlplane: fixed_ips: - ip_address: 192.168.199.200 subnets: - cidr: 192.168.199.0/24 network: tags: 192.168.199.0/24 compute-0-ctlplane: fixed_ips: - ip_address: 192.168.199.210 subnets: - cidr: 192.168.199.0/24 network: tags: 192.168.199.0/24 (undercloud) [stack@undercloud ~]$ cat templates/hostname-map.yaml parameter_defaults: HostnameMap: overcloud-controller-0: controller-0 overcloud-novacompute-0: compute-0 http://paste.openstack.org/show/796634/ <-- Here is the complete output for overcloud deploy command. It seems that the error is /var/lib/tripleo-config/scripts/run_os_net_config.sh: line 59: os-net-config: command not found" os-net-config is provided by "delorean-component-tripleo" repository. So my question is: should I pre install Openstack repositories on pre-provisioned nodes in addition to operating system installation and network configuration? Thank you, Marco

2 1

[horizon] Victoria virtual mid-cycle poll
by Ivan Kolodyazhny 06 Aug '20

06 Aug '20

Hi team, As discussed at Horizon's Virtual PTG [1], we'll have a virtual mid-cycle meeting around Victoria-2 milestone. We'll discuss Horizon current cycle development priorities and the future of Horizon with modern JS frameworks. Please indicate your availability to meet for the first session, which will be held during the week of July 27-31: https://doodle.com/poll/3neps94amcreaw8q Please respond before 12:00 UTC on Tuesday 4 August. [1] https://etherpad.opendev.org/p/horizon-v-ptg Regards, Ivan Kolodyazhny, http://blog.e0ne.info/

1 3

[cinder][nova] Local storage in compute node
by Eric K. Miller 06 Aug '20

06 Aug '20

Hi, I'm research methods to get around high storage latency for some applications where redundancy does not matter, so using local NVMe drives in compute nodes seems to be the practical choice. However, there does not appear to be a good solution from what I have read. For example, BlockDeviceDriver has been deprecated/removed, LVM is only supported via iSCSI (which is slow) and localization of LVM volumes onto the same compute node as VMs is impossible, and other methods (PCI pass-through, etc.) would require direct access to the local drives, where device cleansing would need to occur after a device was removed from a VM, and I don't believe there is a hook for this. Ephemeral storage appears to be an option, but I believe it has the same issue as PCI pass-through, in that there is no abiilty to automatically cleanse a device after it has been used. In our default configuration, ephemeral storage is redirected to use Ceph, which solves the cleansing issue, but isn't suitable due to its high latency. Also, ephemeral storage appears as a second device, not the root disk, so that complicates a few configurations we have. Is there any other way to write an operating system image onto a local drive and boot from it? Or preferably assign an LVM /dev/mapper path as a device in libvirt (no iSCSI) after configuring a logical volume? or am I missing something? Thanks! Eric

4 14

[ops] [keystone] "Roles are not immutable"
by Massimo Sgaravatto 06 Aug '20

06 Aug '20

After updating to Train from rocky (on stein we just performed the db-sync), we tried the new "keystone-status update check" command which says that the admin role is not immutable [*]. As far as I understand this is something that was done to prevent deleting/modifying the default roles (that could cause major problems). But how am I supposed to fix this? The "--immutable" option for the "openstack role set" command, documented at: https://docs.openstack.org/python-openstackclient/latest/cli/command-object… is not available in Train. Thanks, Massimo [*] +-------------------------------------------+ | Check: Check default roles are immutable | | Result: Failure | | Details: Roles are not immutable: admin | +-------------------------------------------+

1 0

[tripleo] Deploy overcloud without provisioning
by Marco Marino 06 Aug '20

06 Aug '20

Hi, I'm trying to deploy an overcloud using tripleo with pre provisioned nodes. My configuration is quite simple: - 1 controller and 1 compute nodes on which I already installed CentOS 8.2 - Both nodes have a dedicated idrac interface with an ip in 192.168.199.0/24. Please note that this interface is not visible with "ip a" or "ifconfig". It's a dedicated IDRAC interface - Both nodes have a NIC configured in the subnet 192.168.199.0/24 (192.168.199.200 and 192.168.199.201) - Undercloud uses 192.168.199.0/24 as pxe/provisioning network (but I don't need provisioning) Question: should I import nodes with "openstack overcloud node import nodes.yaml" even if I don't need the provisioning step? Furthermore, on the undercloud I created one file: /home/stack/templates/node-info.yaml with the following content parameter_defaults: OvercloudControllerFlavor: control OvercloudComputeFlavor: compute ControllerCount: 1 ComputeCount: 1 Question: How can I specify that "node X with ip Y should be used as a controller and node Z with ip K should be used as a compute"?? Should I set the property with the following command? openstack baremetal node set --property capabilities='profile:control' controller1 Thank you, Marco

2 3

[horizon] patternfly?
by Mohammed Naser 06 Aug '20

06 Aug '20

Hi everyone, I was wondering if anyone in the community has explored the idea of implementing PatternFly inside Horizon. It seems like it shares a lot of the similar ideas that we use and we could really benefit from using a common library that already exists with a lot of good UX thought behind it. I know it's based on React which is a bit of a leap from where Horizon is today. However, I'd be curious if the Horizon team is interested in figuring out a plan to make a migration to something like this happen. Personally, I think I would be able to provide resources to have someone do this work. However, if this seems like a huge stretch and architecture change where it actually makes more sense to stand this up from scratch (and implement an architecture where the dashboard talks directly to the APIs?), perhaps we should explore that. I also would like to hear more from our extended community too, as I think we really need to improve our user interface experience. Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

11 31

[TC] [PTG] Victoria vPTG Summary of Conversations and Action Items
by Kendall Nelson 06 Aug '20

06 Aug '20

Hello Everyone! I hope you all had a productive and enjoyable PTG! While it’s still reasonably fresh, I wanted to take a moment to summarize discussions and actions that came out of TC discussions. If there is a particular action item you are interested in taking, please reply on this thread! For the long version, check out the etherpad from the PTG[1]. Tuesday ====== Ussuri Retrospective ---------------------------- As usual we accomplished a lot. Some of the things we accomplished were around enumerating operating systems per release (again), removing python2 support, and adding the ideas repository. Towards the end of the release, we had a lot of discussions around what to do with leaderless projects, the role of PTLs, and what to do with projects that were missing PTL candidates for the next release. We discussed office hours, their history and reason for existence, and clarified how we can strengthen communication amongst ourselves, the projects, and the larger community. TC Onboarding -------------------- It was brought up that those elected most recently (and even new members the election before) felt like there wasn’t enough onboarding into the TC. Through discussion about what we can do to better support returning members is to better document the daily, weekly and monthly tasks TC members are supposed to be doing. Kendall Nelson proposed a patch to start adding more detail to a guide for TC members already[2]. It was also proposed that we have a sort of mentorship or shadow program for people interested in joining the TC or new TC members by more experienced TC members. The discussion about the shadow/mentorship program is to be continued. TC/UC Merge ------------------ Thierry gave an update on the merge of the committees. The simplified version is that the current proposal is that UC members are picked from TC members, the UC operates within the TC, and that we are already setup for this given the number of TC members that have AUC status. None of this requires a by-laws change. One next step that has already begun is the merging of the openstack-users ML into openstack-discuss ML. Other next steps are to decide when to do the actual transition (disbanding the separate UC, probably at the next election?) and when to setup AUC’s to be defined as extra-ATC’s to be included in the electorate for elections. For more detail, check out the openstack-discuss ML thread[3]. Wednesday ========= Help Wanted List ----------------------- We settled on a format for the job postings and have several on the list. We talked about how often we want to look through, update or add to it. The proposal is to do this yearly. We need to continue pushing on the board to dedicate contributors at their companies to work on these items, and get them to understand that it's an investment that will take longer than a year in a lot of cases; interns are great, but not enough. TC Position on Foundation Member Community Contributions ---------------------------------------------------------------------------------- The discussion started with a state of things today - the expectations of platinum members, the benefits the members get being on the board and why they should donate contributor resources for these benefits, etc. A variety of proposals were made: either enforce or remove the minimum contribution level, give gold members the chance to have increased visibility (perhaps giving them some of the platinum member advantages) if they supplement their monetary contributions with contributor contributions, etc. The #ACTION that was decided was for Mohammed to take these ideas to the board and see what they think. OpenStack User-facing APIs -------------------------------------- Users are confused about the state of the user facing API’s; they’ve been told to use the OpenStackClient(OSC) but upon use, they discover that there are features missing that exist in the python-*clients. Partial implementation in the OSC is worse than if the service only used their specific CLI. Members of the OpenStackSDK joined discussions and explained that many of the barriers that projects used to have behind implementing certain commands have been resolved. The proposal is to create a pop up team and that they start with fully migrating Nova, documenting the process and collecting any other unresolved blocking issues with the hope that one day we can set the migration of the remaining projects as a community goal. Supplementally, a new idea was proposed- enforcing new functionality to services is only added to the SDK (and optionally the OSC) and not the project’s specific CLI to stop increasing the disparity between the two. The #ACTION here is to start the pop up team, if you are interested, please reply! Additionally, if you disagree with this kind of enforcement, please contact the TC as soon as possible and explain your concerns. PTL Role in OpenStack today & Leaderless Projects --------------------------------------------------------------------- This was a veeeeeeeerrrry long conversation that went in circles a few times. The very short version is that we, the TC, are willing to let project teams decide for themselves if they want to have a more deconstructed kind of PTL role by breaking it into someone responsible for releases and someone responsible for security issues. This new format also comes with setting the expectation that for things like project updates and signing up for PTG time, if someone on the team doesn’t actively take that on, the default assumption is that the project won’t participate. The #ACTION we need someone to take on is to write a resolution about how this will work and how it can be done. Ideally, this would be done before the next technical election, so that teams can choose it at that point. If you are interested in taking on the writing of this resolution, please speak up! Cross Project Work ------------------------- -Pop Up Teams- The two teams we have right now are Encryption and Secure Consistent Policy Groups. Both are making slow progress and will continue. -Reducing Community Goals Per Cycle- Historically we have had two goals per cycle, but for smaller teams this can be a HUGE lift. The #ACTION is to clearly outline the documentation for the goal proposal and selection process to clarify that selecting only one goal is fine. No one has claimed this action item yet. -Victoria Goal Finalization- Currently, we have three proposals and one accepted goal. If we are going to select a second goal, it needs to be done ASAP as Victoria development has already begun. All TC members should review the last proposal requesting selection[4]. -Wallaby Cycle Goal Discussion Kick Off- Firstly, there is a #ACTION that one or two TC members are needed to guide the W goal selection. If you are interested, please reply to this thread! There were a few proposed goals for VIctoria that didn’t make it that could be the starting point for W discussions, in particular, the rootwrap goal which would be good for operators. The OpenStackCLI might be another goal to propose for Wallaby. Detecting Unmaintained Projects Early --------------------------------------------------- The TC liaisons program had been created a few releases ago, but the initial load on TC members was large. We discussed bringing this program back and making the project health checks happen twice a release, either the start or end of the release and once in the middle. TC liaisons will look at previously proposed releases, release activity of the team, the state of tempest plugins, if regular meetings are happening, if there are patches in progress and how busy the project’s IRC channel is to make a determination. Since more than one liaison will be assigned to each project, those liaisons can divvy up the work how they see fit. The other aspect that still needs to be decided is where the health checks will be recorded- in a wiki? In a meeting and meeting logs? That decision is still to be continued. The current #ACTION currently unassigned is that we need to assign liaisons for the Victoria cycle and decide when to do the first health check. Friday ===== Reducing Systems and Friction to Drive Change ---------------------------------------------------------------- This was another conversation that went in circles a bit before realizing that we should make a list of the more specific problems we want to address and then brainstorm solutions for them. The list we created (including things already being worked) are as follows: - TC separate from UC (solution in progress) - Stable releases being approved by a separate team (solution in progress) - Making repository creation faster (especially for established project teams) - Create a process blueprint for project team mergers - Requirements Team being one person - Stable Team - Consolidate the agent experience - Figure out how to improve project <--> openstack client/sdk interaction. If you feel compelled to pick one of these things up and start proposing solutions or add to the list, please do! Monitoring in OpenStack (Ceilometer + Telemetry + Gnocchi State) ----------------------------------------------------------------------------------------- This conversation is also ongoing, but essentially we talked about the state of things right now- largely they are not well maintained and there is added complexity with Ceilometers being partially dependent on Gnocchi. There are a couple of ideas to look into like using oslo.metrics for the interface between all the tools or using Ceilometer without Gnocchi if we can clean up those dependencies. No specific action items here, just please share your thoughts if you have them. Ideas Repo Next Steps ------------------------------- Out of the Ussuri retrospective, it was brought up that we probably needed to talk a little more about what we wanted for this repo. Essentially we just want it to be a place to collect ideas into without worrying about the how. It should be a place to document ideas we have had (old and new) and keep all the discussion in one place as opposed to historic email threads, meetings logs, other IRC logs, etc. We decided it would be good to periodically go through this repo, likely as a forum session at a summit to see if there is any updating that could happen or promotion of ideas to community goals, etc. ‘tc:approved-release’ Tag --------------------------------- This topic was proposed by the Manila team from a discussion they had earlier in the week. We talked about the history of the tag and how usage of tags has evolved. At this point, the proposal is to remove the tag as anything in the releases repo is essentially tc-approved. Ghanshyam has volunteered to document this and do the removal. The board also needs to be notified of this and to look at projects.yaml in the governance repo as the source of truth for TC approved projects. The unassigned #ACTION item is to review remaining tags and see if there are others that need to be modified/removed/added to drive common behavior across OpenSack components. Board Proposals ---------------------- This was a pretty quick summary of all discussions we had that had any impact on the board and largely decided who would mention them. Session Feedback ------------------------ This was also a pretty quick topic compared to many of the others, we talked about how things went across all our discussions (largely we called the PTG a success) logistically. We tried to make good use of the raising hands feature which mostly worked, but it lacks context and its possible that the conversation has moved on by the time it’s your turn (if you even remember what you want to say). OpenStack 2.0: k8s Native ----------------------------------- This topic was brought up at the end of our time so we didn’t have time to discuss it really. Basically Mohammed wanted to start the conversation about adding k8s as a base service[5] and what we would do if a project proposed required k8s. Adding services that work with k8s could open a door to new innovation in OpenStack. Obviously this topic will need to be discussed further as we barely got started before we had to wrap things up. So. The tldr; Here are the #ACTION items we need owners for: - Start the User Facing API Pop Up Team - Write a resolution about how the deconstructed PTL roles will work - Update Goal Selection docs to explain that one or more goals is fine; it doesn’t have to be more than one - Two volunteers to start the W goal selection process - Assign two TC liaisons per project - Review Tags to make sure they are still good for driving common behavior across all openstack projects Here are the things EVERYONE needs to do: - Review last goal proposal so that we can decide to accept or reject it for the V release[4] - Add systems that are barriers to progress in openstack to the Reducing Systems and Friction list - Continue conversations you find important Thanks everyone for your hard work and great conversations :) Enjoy the attached (photoshopped) team photo :) -Kendall (diablo_rojo) [1] TC PTG Etherpad: https://etherpad.opendev.org/p/tc-victoria-ptg [2] TC Guide Patch: https://review.opendev.org/#/c/732983/ [3] UC TC Merge Thread: http://lists.openstack.org/pipermail/openstack-discuss/2020-May/014736.html [4] Proposed V Goal: https://review.opendev.org/#/c/731213/ [5] Base Service Description: https://governance.openstack.org/tc/reference/base-services.html

3 2

Re: [nova] If any spec freeze exception now?
by yumeng bao 06 Aug '20

06 Aug '20

Hi gibi and all, I wanna mention the SRIOV SmartNIC Support Spec https://review.opendev.org/#/c/742785 This spec is proposed based on feedback from our PTG discussion, yet there are still open questions need to be nailed down. Since this spec involves nova neutron and cyborg, it will probably take a long time to get ideas from different aspects and reach an agreement. Can we keep this as an exception and keep review it to reach closer to an agreement? Hopefully we can reach an agreement in Victoria, and start to land in W. Xinran and I were trying to attend nova’s weekly meeting to discuss this spec, but the time too late for us. :( We will find if there is any other way to sync and response more actively to all your comments and feedback. And just to point out, nova operations support are still one of cyborg’s high priority goals in Victoria, we will keep focus on it and won’t sacrifice time of this goal. Regards， Yumeng

3 3

[swift][ceph] Container ACLs don't seem to be respected on Ceph RGW
by Jason Anderson 06 Aug '20

06 Aug '20

Hi all, Just scratching my head at this for a while and though I’d ask here in case it saves some time. I’m running a Ceph cluster on the Nautilus release and it’s running Swift via the rgw. I have Keystone authentication turned on. Everything works fine in the normal case of creating containers, uploading files, listing containers, etc. However, I notice that ACLs don’t seem to work. I am not overriding "rgw enforce swift acls”, so it is set to the default of true. I can’t seem to share a container or make it public. (Side note, confusingly, the Ceph implementation has a different syntax for public read/write containers, ‘*’ as opposed to ‘*:*’ for public write for example.) Here’s what I’m doing (as admin) swift post —write-acl ‘*’ —read-acl ‘*’ public-container swift stat public-container Account: v1 Container: public-container Objects: 1 Bytes: 5801 Read ACL: * Write ACL: * Sync To: Sync Key: X-Timestamp: 1595883106.23179 X-Container-Bytes-Used-Actual: 8192 X-Storage-Policy: default-placement X-Storage-Class: STANDARD Last-Modified: Wed, 05 Aug 2020 03:42:11 GMT X-Trans-Id: tx000000000000000662156-005f2a2bea-23478-default X-Openstack-Request-Id: tx000000000000000662156-005f2a2bea-23478-default Accept-Ranges: bytes Content-Type: text/plain; charset=utf-8 (as non-admin) swift upload public-container test.txt Warning: failed to create container 'public-container': 409 Conflict: BucketAlreadyExists Object HEAD failed: https://ceph.example.org:7480/swift/v1/public-container/README.md 403 Forbidden swift list public-container Container GET failed: https://ceph.example.org:7480/swift/v1/public-container?format=json 403 Forbidden [first 60 chars of response] b'{"Code":"AccessDenied","BucketName”:”public-container","RequestId":"tx0' Failed Transaction ID: tx000000000000000662162-005f2a2c2a-23478-default What am I missing? Thanks in advance! /Jason

1 2

[tc][ptl] Proposal: Distributed Project Leadership
by Nate Johnston 06 Aug '20

06 Aug '20

The governing structure for OpenStack projects has long been for a Project Technical Lead (PTL) to be elected to serve as a singular focus for that project. While the PTL role varies significantly from project to project, the PTL has many responsibilities for managing the development and release process for a project as well as representing the project both internally and externally. There have been a number of projects that have expressed an interest in functioning in a mode that would not require a PTL, but would rather devolve the responsibilities of the PTL into various liaison roles, that could in turn be held by one or more contributors. This topic was discussed by the TC at the recent virtual PTG, and we now have a proposal to put forth to the community for comment. Jean-Phillipe Evrard and I worked up a more detailed proposal for everyone to comment on and review. We are calling this the 'distributed project leadership model'. Most importantly, this is an opt-in process where projects interested in pursuing a distributed project leadership model should opt in to it, but for projects satisfied with the status quo nothing would change. I encourage everyone who is interested to examine the proposal and comment: https://review.opendev.org/744995 Thank you, Nate Johnston

1 0