- openstack-discuss - lists.openstack.org

Openstack with Nginx Support
by HARISH KUMAR Ivaturi 25 Aug '20

25 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

1 0

[ironic] RFC: deprecate the iSCSI deploy interface?
by Dmitry Tantsur 25 Aug '20

25 Aug '20

Hi all, Side note for those lacking context: this proposal concerns deprecating one of the ironic deploy interfaces detailed in https://docs.openstack.org/ironic/latest/admin/interfaces/deploy.html. It does not affect the boot-from-iSCSI feature. I would like to propose deprecating and removing the 'iscsi' deploy interface over the course of the next 2 cycles. The reasons are: 1) The iSCSI deploy is a source of occasional cryptic bugs when a target cannot be discovered or mounted properly. 2) Its security is questionable: I don't think we even use authentication. 3) Operators confusion: right now we default to the iSCSI deploy but pretty much direct everyone who cares about scalability or security to the 'direct' deploy. 4) Cost of maintenance: our feature set is growing, our team - not so much. iscsi_deploy.py is 800 lines of code that can be removed, and some dependencies that can be dropped as well. As far as I can remember, we've kept the iSCSI deploy for two reasons: 1) The direct deploy used to require Glance with Swift backend. The recently added [agent]image_download_source option allows caching and serving images via the ironic's HTTP server, eliminating this problem. I guess we'll have to switch to 'http' by default for this option to keep the out-of-box experience. 2) Memory footprint of the direct deploy. With the raw images streaming we no longer have to cache the downloaded images in the agent memory, removing this problem as well (I'm not even sure how much of a problem it is in 2020, even my phone has 4GiB of RAM). If this proposal is accepted, I suggest to execute it as follows: Victoria release: 1) Put an early deprecation warning in the release notes. 2) Announce the future change of the default value for [agent]image_download_source. W release: 3) Change [agent]image_download_source to 'http' by default. 4) Remove iscsi from the default enabled_deploy_interfaces and move it to the back of the supported list (effectively making direct deploy the default). X release: 5) Remove the iscsi deploy code from both ironic and IPA. Thoughts, opinions, suggestions? Dmitry

6 11

[cliff] [dev] Cliff auto completion not working inside interactive mode
by sandeep 25 Aug '20

25 Aug '20

Hi Team, In my system, I am trying auto completion for my CLI application. CLIFF version - cliff==3.4.0 Auto complete works fine on bash prompt. But inside the interactive shell, auto complete does not work. Below is the output for the help command inside the interactive shell. (appcli) help Miscellaneous help topics: ========================== help Application commands (type help <topic>): ========================================= complete snapshot list reports service restart service-object-type app2 service restart service-object-type app3 service restart service-object-type app4 service show state service-object-type app1 service show state service-object-type app2 service show state service-object-type app3 service show state service-object-type app4 swm rollback node swm cancel sw-update swm downgrade node swm list sw-info swm show sw-info swm start sw-update file swm start sw-downgrade help Now, if I type swm and press tab, it lists all the sub commands under it. (appcli) swm cancel sw-update list sw-info start sw-update file downgrade node rollback node show sw-info start sw-downgrade But if i type, (appcli) swm s<tab> gives below output, (appcli) swm "s It stops at this point and further pressing tab does not autocomplete. Could you please let me know what could be the problem? Is this a known issue? or Am i missing something? Thanks, Sandeep

1 0

Scaling control nodes
by Benjamin Zapiec 25 Aug '20

25 Aug '20

Hello everyone, while trying openstack i referred to the red hat installation documentation which is okay but lead to one question. It looks like there is no problem in scaling compute nodes if you run out of resources. But scaling the controller nodes is not supported by red hat. Since I'm using the official tripleo openstack version and not the red hat version i was wondering if this is not supported by the openstack project. Having in mind that red hat doesn't support this i was looking for something that tells me that it is supported (or not) by the tripleo openstack project. But i didn't found anything explicit. So may you tell me if it is possible to scale up Controller Nodes? And if not which component is not scalable by tripleo? Is it possible to create an controller profile that is scalable? Best regards -- Benjamin Zapiec <benjamin.zapiec(a)gonicus.de> (System Engineer) * GONICUS GmbH * Moehnestrasse 55 (Kaiserhaus) * D-59755 Arnsberg * Tel.: +49 2932 916-0 * Fax: +49 2932 916-245 * http://www.GONICUS.de * Sitz der Gesellschaft: Moehnestrasse 55 * D-59755 Arnsberg * Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder * Vorsitzender des Beirats: Juergen Michels * Amtsgericht Arnsberg * HRB 1968 Wir erfüllen unsere Informationspflichten zum Datenschutz gem. der Artikel 13 und 14 DS-GVO durch Veröffentlichung auf unserer Internetseite unter: https://www.gonicus.de/datenschutz oder durch Zusendung auf Ihre formlose Anfrage.

1 0

[Kolla Ansible] host maintenance
by Tony Liu 25 Aug '20

25 Aug '20

Hi, I wonder if it's supported by Kolla Ansible to deploy a specific host and add it into existing cluster, like replace a control host or compute host? Thanks! Tony

5 10

[Monasca] Kolla docker image on Docker Hub
by Tony Liu 25 Aug '20

25 Aug '20

Hi, Are those Monasca Kolla container images kolla/centos-binary-monasca-* on Docker Hub? I only see kolla/centos-binary-monasca-grafana. I am running Kolla Ansible to deploy Monasca and got this failure. ======== docker.errors.ImageNotFound: 404 Client Error: Not Found (\"pull access denied for kolla/centos-binary-monasca-api, repository does not exist or may require \\'docker login\\': denied: requested access to the resource is denied\") ======== Thanks! Tony

3 2

Cliff auto completion not working inside interactive mode
by sandeep 24 Aug '20

24 Aug '20

Hi Team, In my system, I am trying auto completion for my CLI application. *CLIFF version - cliff==3.4.0* Auto complete works fine on bash prompt. But inside the interactive shell, auto complete does not work. Below is the screenshot for the help command inside the interactive shell. [image: image.png] Now, if I type swm and press tab, it lists all the sub commands under it. But, swm s<tab> gives swm "s and further command auto completion does not work. [image: image.png] Could you please let me know what could be the problem? Is this a known issue? or Am i missing something? Thanks, Sandeep

1 1

[neutron][ops] q-agent-notifier exchanges without bindings.
by Fabian Zimmermann 24 Aug '20

24 Aug '20

Hi, im currently on the way to analyse some rabbitmq-issues. atm im taking a look on "unroutable messages", so I * created an Alternative Exchange and Queue: "unroutable" * created a policy to send all unroutable msgs to this exchange/queue. * wrote a script to show me the msgs placed here.. currently I get Seems like my neutron is placing msgs in these exchanges, but there is nobody listening/binding to: -- 20 Exchange: q-agent-notifier-network-delete_fanout, RoutingKey: 226 Exchange: q-agent-notifier-port-delete_fanout, RoutingKey: 88 Exchange: q-agent-notifier-port-update_fanout, RoutingKey: 388 Exchange: q-agent-notifier-security_group-update_fanout, RoutingKey: -- Is someone able to give me a hint where to look at / how to debug this? Fabian

2 2

[tacker] IRC meeting
by Yasufumi Ogawa 24 Aug '20

24 Aug '20

Hi tacker team, I am not available to join IRC meeting today unfortunately. I would like to suggest to anyone host the meeting, or skip it if no items. Thanks, Yasufumi

2 1

[blazar] IRC meetings cancelled this week
by Pierre Riteau 24 Aug '20

24 Aug '20

Hello, Apologies for the short notice: due to scheduling conflicts, I am not available to chair either of the Blazar IRC meetings this week. I propose that we cancel them. Thanks, Pierre Riteau (priteau)

1 0

[nova][neutron][oslo][ops] rabbit bindings issue
by Arnaud Morin 24 Aug '20

24 Aug '20

Hey all, I would like to ask the community about a rabbit issue we have from time to time. In our current architecture, we have a cluster of rabbits (3 nodes) for all our OpenStack services (mostly nova and neutron). When one node of this cluster is down, the cluster continue working (we use pause_minority strategy). But, sometimes, the third server is not able to recover automatically and need a manual intervention. After this intervention, we restart the rabbitmq-server process, which is then able to join the cluster back. At this time, the cluster looks ok, everything is fine. BUT, nothing works. Neutron and nova agents are not able to report back to servers. They appear dead. Servers seems not being able to consume messages. The exchanges, queues, bindings seems good in rabbit. What we see is that removing bindings (using rabbitmqadmin delete binding or the web interface) and recreate them again (using the same routing key) brings the service back up and running. Doing this for all queues is really painful. Our next plan is to automate it, but is there anyone in the community already saw this kind of issues? Our bug looks like the one described in [1]. Someone recommands to create an Alternate Exchange. Is there anyone already tried that? FYI, we are running rabbit 3.8.2 (with OpenStack Stein). We had the same kind of issues using older version of rabbit. Thanks for your help. [1] https://groups.google.com/forum/#!newtopic/rabbitmq-users/rabbitmq-users/zF… -- Arnaud Morin

9 29

[security] Security SIG Meeting Aug 27th Cancelled
by Gage Hugo 24 Aug '20

24 Aug '20

Good morning, The security SIG meeting for Thursday, Aug 27th 2020 will be cancelled. We will meet next week at the usual time.

1 0

[openstack-helm] OpenStack-Helm Meeting Aug 25th Cancelled
by Gage Hugo 24 Aug '20

24 Aug '20

Good morning, The openstack-helm meeting for tomorrow, Aug 25th 2020 will be cancelled, we will see you all next week!

1 0

[ovn][neutron][ussuri] DPDK support on OVN Openstack? Openstack Doc contradictive Information?
by Popoi Zen 24 Aug '20

24 Aug '20

I want to implement DPDK on my Openstack using OVN as mechanism driver. I read 2 documentation: [1] https://docs.openstack.org/neutron/ussuri/admin/ovn/dpdk.html [2] https://docs.openstack.org/neutron/ussuri/admin/config-ovs-dpdk.html In first doc [1], it is said that DPDK has been supported on OVN. But in second doc [2] it is said `The support of this feature is not yet present in ML2 OVN and ODL mechanism drivers.` Which one is true? because I have TCP checksum issue when implement DPDK on OVN same like this: https://bugs.launchpad.net/neutron/+bug/1832021. It has patched on OVS but not work on OVN. Regards,

3 3

About Devstack
by 李志远 24 Aug '20

24 Aug '20

I'm sorry to disturb you. Recently, I tried to install openstack through devstack. When I input "./stack.sh". I can install openstack successfully. Then I tried to create a cloud instance and use the public network 172.24.4.0/24 which is created during installation( this subnet is created by default, I didn't configure network informartion in local.conf before installation). And the instance can access to the Internet smoothly. But the instance will not access the Internet when I reboot my server  (physical machine). After rebooting, I input "sudo ifconfig br-ex 172.24.4.1/24 up", the instance can access my server IP, but it can't PING the gateway addresses of my server. Of course, the instance also can't access the Internet. But my server can PING it's gateway and access to the Internet. Finally, the cloud instance can only communicate with my server. I tried many methods to restore the network environment of my openstack. But I can't find the reason. So I need your help. I install the version of devstack is stable/train. Thank you very much!

3 2

[Nova] We are dropping the 'delete_instance_files' virt driver interface
by Zhong, Luyao 24 Aug '20

24 Aug '20

Hi all especially maintainers of out-of-tree drivers, Please pay attention to this change. https://review.opendev.org/#/c/714653/ We are dropping 'delete_instance_files' virt driver interface, and will use "cleanup_instance" to take charge of lingering instance cleanup, including instance files deleting and whatever we add in the future. Best Regards, Luyao

1 0

[MURANO] Murano Class error when try to deploy WordPress APP
by İzzettin Erdem 24 Aug '20

24 Aug '20

Hello everyone, WordPress needs Mysql, HTTP and Zabbix Server/Agent. These apps run individually with succes but when I try to deploy WordPress App on Murano it gives the error about Apache HTTP that mentioned below. How can I fix this? Do you have any suggestions? Error: http://paste.openstack.org/show/796980/ http://paste.openstack.org/show/796983/ (cont.)

2 1

[neutron] Bug Deputy Report Aug 17-24
by Lucas Alvares Gomes 24 Aug '20

24 Aug '20

Hi, This is the Neutron bug report of the week of 2020-08-17. High: * https://bugs.launchpad.net/neutron/+bug/1891673 - "qrouter ns ip rules not deleted when fip removed from vm" Assigned to: hopem * https://bugs.launchpad.net/neutron/+bug/1892017 - "Neutron server logs are too big in the gate jobs" Assigned to: slaweq * https://bugs.launchpad.net/neutron/+bug/1892477 - "[OVN] Avoid nb_cfg update notification flooding during agents health check" Assigned to: lucasagomes * https://bugs.launchpad.net/neutron/+bug/1892489 - "[Prefix delegation] When subnet with PD enabled is added to the router, L3 agent fails on waiting for LLAs to be available" Assigned to: slaweq Needs further triage: * https://bugs.launchpad.net/neutron/+bug/1892405 - "Removing router interface causes router to stop routing between all" Unassigned * https://bugs.launchpad.net/neutron/+bug/1892496 - "500 on SG deletion: Cannot delete or update a parent row" Unassigned Medium: * https://bugs.launchpad.net/neutron/+bug/1892364 - "L3 agent prefix delegation - adding new subnet to the router fails" Assigned to: brian-haley * https://bugs.launchpad.net/neutron/+bug/1892362 - "Restarting L3 agent when PD is used fails due to IPAddressAlreadyExists error" Assigned to: slaweq Wishlist: * https://bugs.launchpad.net/neutron/+bug/1892200 - "Make keepalived healthcheck more configurable" Unassigned

1 0

[keystone] openstack token auth scpore system Question
by Mingi Jo 23 Aug '20

23 Aug '20

Hi, I'm studying OpenStack.If you use OpenStack and use it with a keystone token on all computers,If there is a project in the endpoint URL, the api request cannot be made properly.The error message is output at 400, and the request fails. We've looked into this, and I've found out,https://bugs.launchpad.net/cinder/+bug/1745905Here's the bug reporting, and I think it's done with the paperwork.However, various services such as cinder, swift, and probe are required to include projects in the endpoint url of the installation guide, which is considered contradictory.Is there any way to fix this?

1 0

python-zunclient
by mahdi abbasi 22 Aug '20

22 Aug '20

Hi openstack development team, I installed python-zunclient successfully but openstack appcontainer command steal return not found. Please help me. Best regards Mahdi

2 2

RE: Using os_token
by Eric K. Miller 21 Aug '20

21 Aug '20

I happened to run across an unrelated github issue: https://github.com/terraform-providers/terraform-provider-openstack/issu es/271 which gave me a clue to what I was missing. I needed to include some additional variables (see steps 7 through 9 below). Revised steps - which works fine with the OpenStack Client: 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) set OS_PROJECT_DOMAIN_ID as appropriate 8) set OS_PROJECT_NAME as appropriate 9) set OS_REGION_NAME as appropriate 10) use the CLI as normal This shaves anywhere from 0.2 to 0.6 seconds off of a test command I'm running when compared to password authentication (which normally takes about 2.5 seconds to run), where a new token is issued each time. openstack token revoke works as expected too. Eric

2 2

Nova Docker
by mahdi abbasi 21 Aug '20

21 Aug '20

Hi openstack development team, Given that the nova-docker peoject is np longer availble, is there any solution for creating a docker instanace in openstack? Best regards Mahdi

2 2

Can't fetch from opendev.
by Daniel Bengtsson 21 Aug '20

21 Aug '20

Hi everyone, I have tried to fetch the repository tripleo-heat-templates from opendev. I was not able to do that: http://paste.openstack.org/show/796882/ With github it works. I have asked to another colleague to try, he have the same problem.

3 7

[cinder] reviewing priorities for next few weeks
by Brian Rosmaita 21 Aug '20

21 Aug '20

Hello Cinderinos, We're near the end of week R-8, and people are getting antsy about having their changes reviewed. So here are the Cinder project reviewing priorities over the next few weeks. (1) os-brick The Victoria release of os-brick must take place during week R-6 (i.e., by 31 August). Hence, os-brick reviews are the project's TOP PRIORITY right now. Among os-brick reviews, these are the most important changes: - support for volume-local-cache feature https://review.opendev.org/663549 - support for cinderlib RBD use https://review.opendev.org/#/q/topic:cinderlib-changes+status:open - code cleanup (should be quick reviews) https://review.opendev.org/#/q/status:open+project:openstack/os-brick+branc… There are some other open reviews in master; if they interest you, go for it. But the above are release-critical. (2) cinder features requiring python-cinderclient support The Victoria release of python-cinderclient must take place during week R-5 (i.e., by 7 September). - project-level default volume-types cinder: https://review.opendev.org/737707 cinderclient: https://review.opendev.org/739223/ - active-active support https://review.opendev.org/#/q/topic:a-a-support+status:open There are other open reviews in master for python-cinderclient that could use some eyes. I didn't see anything major, but it would be good to look in case I missed something. (3) other features (including drivers) The feature freeze is the end of R-5 (i.e., 8 September) - Use the blueprints to find these: https://blueprints.launchpad.net/cinder/victoria And we'll be reviewing everything else also, but items in the 3 categories above get priority. If your patch is in category (3) or not-prioritized, you can always help speed things up by reviewing the higher-priority items. We're almost at the end of the Victoria cycle. Let's have a productive few weeks! brian

1 0

[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 20 Aug '20

20 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 20 Aug '20

20 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 18 Aug '20

18 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