September 2020 - openstack-discuss

[neutron] CI meeting 09/09/2020 cancelled
by Slawek Kaplonski 09 Sep '20

09 Sep '20

Hi, I'm off today and I will not be able to chair our CI meeting this week. So lets cancel it and see You on the meeting next week. -- Slawek Kaplonski Principal software engineer Red Hat

1 0

[blazar] Wallaby PTG
by Pierre Riteau 08 Sep '20

08 Sep '20

Hello, As mentioned in a recent IRC meeting [1], I likely won't be able to attend the PTG this year. Tetsuro Nakamura who is the only other active core reviewer at the moment said he won't have time either. Given that we still have lots of pending tasks on Blazar from the last PTG [2], I propose that we don't plan to meet during the PTG in October 2020. Best wishes, Pierre Riteau (priteau) [1] http://eavesdrop.openstack.org/meetings/blazar/2020/blazar.2020-08-18-09.00… [2] https://etherpad.opendev.org/p/blazar-ptg-victoria

1 0

Tripleo Standalone Deployment Issues - Reproduceable
by yuuta.takanashi＠aol.com 08 Sep '20

08 Sep '20

Hi Experts, I am facing on below issues while following guide of Tripleo Standalone Deployment: https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deploym… Issue 1) Using custom domain will cause vm instantiation error after machine reboot Description =========== After Openstack installed, it's adding centos82.localdomain on /etc/hosts and causing OVN Southbound (ovn-sbctl show) using this centos82.localdomain. But after the machine rebooted, "ovn-sbctl show" is showing the correct fqdn: centos82.domain.tld, and it is causing VM instantiate error (Refusing to bind port <UUID> due to no OVN chassis for host: centos82.localdomain). Steps to reproduce ================== Base installation: https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deploym… Tested on Centos 8.2 latest, tested several times on Train and Ussuri. 100% reproduceable. Set the custom FQDN hostname hostnamectl set-hostname centos82.domain.tld hostnamectl set-hostname centos82.domain.tld --transient (also tested with or without this line) cat /etc/hosts 127.0.0.1 centos82.domain.tld localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 centos82.domain.tld localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.156.82 centos82.domain.tld also tested with hostnamectl set-hostname centos82.domain.tld hostnamectl set-hostname centos82.domain.tld --transient (also tested with or without this line) cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.156.82 centos82.domain.tld centos82 also tested with hostnamectl set-hostname centos82.domain.tld hostnamectl set-hostname centos82.domain.tld --transient (also tested with or without this line) cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.156.82 centos82.domain.tld Part of standalone_parameters.yaml for domain: # domain name used by the host NeutronDnsDomain: domain.tld Follow the guide to install (without ceph) (Issue 1B) with ceph was having another error, just tested once on Train: fatal: [undercloud]: FAILED! => { "ceph_ansible_std_out_err": [ "Using /home/stack/standalone-ansible-huva1ccw/ansible.cfg as config file", "ERROR! the playbook: /usr/share/ceph-ansible/site-container.yml.sample could not be found" ], "failed_when_result": true } All will be installed successfully, and able to instantiate VMs and these VMs are able to ping to each other. Then do "reboot" on this standalone host/server. Do instantiate a new VM, and then this new VM status will be ERROR. On Neutron logs: Refusing to bind port <UUID> due to no OVN chassis for host: centos82.localdomain bind_port Found the cause on OVN: Previous after installed (before reboot) [root@centos82 /]# ovn-sbctl show Chassis "<UUID>" hostname: centos82.localdomain Encap geneve ip: "192.168.156.82" options: {csum="true"} [root@centos82 /]# After reboot [root@centos82 /]# ovn-sbctl show Chassis "<UUID>" hostname: centos82.domain.tld Encap geneve ip: "192.168.156.82" options: {csum="true"} [root@centos82 /]# So that the OVN seems could not bind the port to different hostname (that already changed). Environment =========== 1. Exact version of OpenStack you are running: Any, tested Train and Ussuri 2. Centos 8.2 latest update Others (without ceph): https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deploym… Workaround ========== Don't use custom domain, instead use "localdomain" as on the document hostnamectl set-hostname centos82.localdomain [root@centos82 ~]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.156.82 centos82.localdomain centos82 Deploy, test instantiate, reboot, test instantiate, and working perfectly fine. Question: For custom domain, where did I do wrongly? Is it expected or kind of bugs? Issue 2) This is not Openstack issue, perhaps bugs or perhaps my issue, but it is still related with the topic on Tripleo Standalone Deployment. On the same Standalone Deployment Guide (https://docs.openstack.org/project-deploy-guide/tripleo-docs/latest/deploym…) with Centos 7.6 or 7.7 with "python-tripleoclient" and this has dependency of Docker 1.13.1, encounters kind of Dns querying issue which I posted here: https://serverfault.com/questions/1032816/centos-7-and-docker-1-13-1-error-… Perhaps if anybody knows how to resolve this. Also, just wondering is there any way for "python-tripleoclient" to use newer docker-ce 1.19.x instead of docker 1.13.1? ThanksBest regards, TY

2 1

Windows 10 instance hostname not updating
by its-openstack＠zohocorp.com 08 Sep '20

08 Sep '20

Dear openstack, I have installed openstack train branch, I am facing issue with windows image. all windows 10 instance dosen't get its hostname updated from the metadata, but able to get the metadata(hostname) from inside the instance using powershell. ``` $ Invoke-WebRequest http://169.254.169.254/latest/meta-data/hostname -UseBasicParsing ``` windows2016 instance no issue. using the stable cloudbase-init package for preparation of windows 10. if you would so kindly help us with this issue Regards sysadmin

1 0

[cloudkitty] Virtual PTG planning
by Pierre Riteau 08 Sep '20

08 Sep '20

Hi, You may know that the next PTG will be held virtually during the week of October 26-30, 2020. I will very likely *not* be available during that time, so I would like to hear from the CloudKitty community: - if you would like to meet and for how long (a half day may be enough depending on the agenda) - what day and time is preferred (see list in https://ethercalc.openstack.org/7xp2pcbh1ncb) - if anyone is willing to chair the discussions (I can help you prepare an agenda before the event) Thanks in advance, Pierre Riteau (priteau)

2 2

Create Application Credential not appearing in Horizon
by Alexander Dibbo - UKRI STFC 08 Sep '20

08 Sep '20

Hi All, I'm having an issue where users with the "user" role in my deployment are not seeing the "Create Application Credential" button in horizon although users with the "admin" role can. I have tried modifying the keystone policy a couple of different ways to fix this but none have worked: "identity:create_application_credential": "user_id:%(user_id)s", "identity:create_application_credential": "role: user", "identity:create_application_credential": "rule:owner", "identity:create_application_credential": "", Could anyone point me in the right direction? My deployment is running the Train release of OpenStack Thanks, Alex Regards Alexander Dibbo - Cloud Architect / Cloud Operations Group Leader For STFC Cloud Documentation visit https://stfc-cloud-docs.readthedocs.io<https://stfc-cloud-docs.readthedocs.io/> To raise a support ticket with the cloud team please email cloud-support(a)gridpp.rl.ac.uk<mailto:cloud-support@gridpp.rl.ac.uk> To receive notifications about the service please subscribe to our mailing list at: https://www.jiscmail.ac.uk/cgi-bin/webadmin?A0=STFC-CLOUD To receive fast notifications or to discuss usage of the cloud please join our Slack: https://stfc-cloud.slack.com/ This email and any attachments are intended solely for the use of the named recipients. If you are not the intended recipient you must not use, disclose, copy or distribute this email or any of its attachments and should notify the sender immediately and delete this email from your system. UK Research and Innovation (UKRI) has taken every reasonable precaution to minimise risk of this email or any attachments containing viruses or malware but the recipient should carry out its own virus and malware checks before opening the attachments. UKRI does not accept any liability for any losses or damages which the recipient may sustain due to presence of any viruses. Opinions, conclusions or other information in this message and attachments that are not related directly to UKRI business are solely those of the author and do not represent the views of UKRI.

2 2

[release] Release countdown for week R-5 Sept 7 - 11
by Sean McGinnis 08 Sep '20

08 Sep '20

We are getting close to the end of the Victoria cycle! Next week on September 10 is the victoria-3 milestone, also known as feature freeze. It's time to wrap up feature work in the services and their client libraries, and defer features that won't make it to Wallaby. General Information ------------------- This coming week is the deadline for client libraries: their last feature release needs to happen before "Client library freeze" on September 3. Only bugfix releases will be allowed beyond this point. When requesting those library releases, you can also include the stable/victoria branching request with the review. As an example, see the "branches" section here: https://opendev.org/openstack/releases/src/branch/master/deliverables/pike/… September 10 is also the deadline for feature work in all OpenStack deliverables following the cycle-with-rc model. To help those projects produce a first release candidate in time, only bugfixes should be allowed in the master branch beyond this point. Any feature work past that deadline has to be raised as a Feature Freeze Exception (FFE) and approved by the team PTL. Finally, feature freeze is also the deadline for submitting a first version of your cycle-highlights. Cycle highlights are the raw data hat helps shape what is communicated in press releases and other release activity at the end of the cycle, avoiding direct contacts from marketing folks. See https://docs.openstack.org/project-team-guide/release-management.html#cycle… for more details. Upcoming Deadlines & Dates -------------------------- Client library freeze: September 10 (R-5 week) Victoria-3 milestone: September 10 (R-5 week) Cycle Highlights Due: September 10 (R-5 week) Final Victoria release: October 14 Open Infra Summit: October 19-23 Wallaby PTG: October 26-30

1 0

[neutron] Wallaby PTG planning
by Slawek Kaplonski 08 Sep '20

08 Sep '20

Hi, It's again that time of the cycle (time flies) when we need to start thinking about next cycle already. As You probably know, next virtual PTG will be in October 26-30. I need to book some space for the Neuton team before 11th of September so I prepared doodle [1] with possible time slots. Please reply there what are the best days and hours for You so we can try to schedule our sessions in the time slots which fits best most of us :) Please fill this doodle before 4.09 so I will have time to summarize it and book some slots for us. I also prepared etherpad [2]. Please add Your name if You are going to attend the PTG sessions. Please also add proposals of the topics which You want to discuss during the PTG. [1] https://doodle.com/poll/2ppmnua2nuva5nyp [2] https://etherpad.opendev.org/p/neutron-wallaby-ptg -- Slawek Kaplonski Principal software engineer Red Hat

1 1

[tripleo] docker.io rate limiting
by Wesley Hayutin 08 Sep '20

08 Sep '20

Greetings, Some of you have contacted me regarding the recent news regarding docker.io's new policy with regards to container pull rate limiting [1]. I wanted to take the opportunity to further socialize our plan that will completely remove docker.io from our upstream workflows and avoid any rate limiting issues. We will continue to upload containers to docker.io for some time so that individuals and the community can access the containers. We will also start exploring other registries like quay and newly announced github container registry. These other public registries will NOT be used in our upstream jobs and will only serve the communities individual contributors. Our test jobs have been successful and patches are starting to merge to convert our upstream jobs and remove docker.io from our upstream workflow. [2]. Standalone and multinode jobs are working quite well. We are doing some design work around branchful, update/upgrade jobs at this time. Thanks 0/ [1] https://hackmd.io/ermQSlQ-Q-mDtZkNN2oihQ [2] https://review.opendev.org/#/q/topic:new-ci-job+(status:open+OR+status:merg…

7 13

[tripleo] Proposing Takashi Kajinami to be core on puppet-tripleo
by Emilien Macchi 08 Sep '20

08 Sep '20

Hi people, If you don't know Takashi yet, he has been involved in the Puppet OpenStack project and helped *a lot* in its maintenance (and by maintenance I mean not-funny-work). When our community was getting smaller and smaller, he joined us and our review velicity went back to eleven. He became a core maintainer very quickly and we're glad to have him onboard. He's also been involved in taking care of puppet-tripleo for a few months and I believe he has more than enough knowledge on the module to provide core reviews and be part of the core maintainer group. I also noticed his amount of contribution (bug fixes, improvements, reviews, etc) in other TripleO repos and I'm confident he'll make his road to be core in TripleO at some point. For now I would like him to propose him to be core in puppet-tripleo. As usual, any feedback is welcome but in the meantime I want to thank Takashi for his work in TripleO and we're super happy to have new contributors! Thanks, -- Emilien Macchi

12 12

who is running RabbitMQ HiPE mode?
by Satish Patel 08 Sep '20

08 Sep '20

Folks, I was reading about HiPE mode and thinking to give it a shot but i would like to know feedback from the community? Is it safe to enable HiPE for rabbitMQ to boost performance?

2 1

[Kolla Ansible] Unable to connect to external network after Initial deployment
by Lukasluedke＠web.de 07 Sep '20

07 Sep '20

1 0

[sdk/cli] virtual PTG planning
by Artem Goncharov 07 Sep '20

07 Sep '20

Hi all, I’ve booked a slot for SDK/CLI PTG on 28th of Oct 14:00-17:00 UTC time. Please fill in the etherpad [1] if you want to come in. Regards, Artem (gtema) [1] https://meetpad.opendev.org/etherpad/p/wallaby_sdk_cli <https://meetpad.opendev.org/etherpad/p/wallaby_sdk_cli>

1 0

[nova] virtual PTG and Forum planning
by Balázs Gibizer 07 Sep '20

07 Sep '20

Hi, As you probably know the next virtual PTG will be held between October 26-30. I need to book time slots for Nova [1] so please add your availability to the doodle [2] before 7th of September. I have created an etherpad [3] to collect the PTG topics for the Nova sessions. Feel free to add your topics. Also there will be a Forum between October 19-23 [4]. You can use the PTG etherpad [3] to brainstorm forum topics before the official CFP opens. Cheers, gibi [1] https://ethercalc.openstack.org/7xp2pcbh1ncb [2] https://doodle.com/poll/a5pgqh7bypq8piew [3] https://etherpad.opendev.org/p/nova-wallaby-ptg [4] https://wiki.openstack.org/wiki/Forum/Virtual202

1 1

[ironic] [stable] Bifrost stable/stein is broken (by eventlet?): help needed
by Dmitry Tantsur 07 Sep '20

07 Sep '20

Hi folks, I'm trying to revive the Bifrost stable/stein CI, and after fixing a bunch of issues in https://review.opendev.org/749014 I've hit a wall with what seems an eventlet problem: ironic-inspector fails to start with: Exception AttributeError: "'_SocketDuckForFd' object has no attribute '_closed'" in <bound method _SocketDuckForFd.__del__ of _SocketDuckForFd:16> ignored I've managed to find similar issues, but they should have been resolved in the eventlet version in stein (0.24.1). Any ideas? If we cannot fix it, we'll have to EOL stein and earlier on bifrost. Dmitry -- Red Hat GmbH, https://de.redhat.com/ , Registered seat: Grasbrunn, Commercial register: Amtsgericht Muenchen, HRB 153243, Managing Directors: Charles Cachera, Brian Klemm, Laurie Krebs, Michael O'Neill

3 4

watchdog fed successfully event of 6300esb
by ligang (P) 07 Sep '20

07 Sep '20

Hi folks, I have an question to discuss about the 6300esb watchdog. I think is it possible that qemu can send an event while the watchdog successfully fed by the vm at the first time. Here is the situation: Qemu will send an VIR_DOMAIN_EVENT_ID_WATCHDOG event while watch dog timeout, and if the action of the watchdog in xml of the vm was set to "reset", the vm will be rebooted while timeout. I have an monitor process that register callback function of the VIR_DOMAIN_EVENT_ID_WATCHDOG event, the callback function will send an alarm to my upper layer monitor platform indicate that the vm is fault, and the cluster deployed business on the vm will isolate the vm by the alarm. And after the vm rebooted , the monitor process will receive an reboot event and send it to the platform, the upper layer monitor platform will clear the alarm, and business continue to run on the vm. In most cases ,the watch dog process in vm will feed the watchdog after vm rebooted and all things go back on track. In some other cases,the guestos may failed to start (in my environment vm start failed by io error), but the reboot event will still be received and the alarm will be cleared and the vm is still fault. So the this may not a good idea to clear the alarm by the reboot event. So, I think it will be helpful that the qemu can send an event while the watchdog successfully fed by the vm at the first time. So I can exactly know that the guest os go back on running and the watch dog initialized successfully. Or any other opintion about this situation. Thanks.

1 0

New deployed packstack openstack, Failed create instance due to volume failed to created
by dangerzone ar 07 Sep '20

07 Sep '20

Hi, my clean install openstack queens are not able to create simple instance. Got error *Error: Failed to perform requested operation on instance "test1", the instance has an error status: Please try again later [Error: Build of instance 18c607fd-e919-4022-be7d-d178d7ab410e aborted: Volume 8a3b3e80-1593-46e5-8aa8-a5083bfbb46f did not finish being created even after we waited 9 seconds or 4 attempts. And its status is error.].* Filesystem Size Used Avail Use% Mounted on devtmpfs 3.9G 0 3.9G 0% /dev tmpfs 3.9G 4.0K 3.9G 1% /dev/shm tmpfs 3.9G 25M 3.8G 1% /run tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup /dev/mapper/centos-root 48G 34G 15G 71% / /dev/sda1 1014M 182M 833M 18% /boot /dev/mapper/centos-home 24G 33M 24G 1% /home tmpfs 783M 0 783M 0% /run/user/1000 /dev/loop1 1.9G 6.1M 1.7G 1% /srv/node/swiftloopback tmpfs 783M 0 783M 0% /run/user/0 pvs PV VG Fmt Attr PSize PFree /dev/loop0 cinder-volumes lvm2 a-- <20.60g 1012.00m /dev/sda2 centos lvm2 a-- <79.00g 4.00m vgs VG #PV #LV #SN Attr VSize VFree centos 1 3 0 wz--n- <79.00g 4.00m cinder-volumes 1 1 0 wz--n- <20.60g 1012.00m seems my cinder volume no free space. I install VM with 80G storage but cinder volume no space. I tried extend cinder volume as follows *lvm vgextend "cinder-volumes" /dev/loop3 Physical volume "/dev/loop3" successfully created. Volume group "cinder-volumes" successfully extendedpvscan PV /dev/loop0 VG cinder-volumes lvm2 [<20.60 GiB / 1012.00 MiB free] PV /dev/loop3 VG cinder-volumes lvm2 [<30.00 GiB / <30.00 GiB free] PV /dev/sda2 VG centos lvm2 [<79.00 GiB / 4.00 MiB free] Total: 3 [<129.59 GiB] / in use: 3 [<129.59 GiB] / in no VG: 0 [0 ]* *vgs VG #PV #LV #SN Attr VSize VFree centos 1 3 0 wz--n- <79.00g 4.00m cinder-volumes 2 1 0 wz--n- 50.59g 30.98g* When try to create new instance I keep getting the same volume error... Please help and advise what should I do...Please help...why 80G still not enough for cinder volume. Appreciate help. Thank you

3 5

[kolla] Kolla klub break
by Mark Goddard 07 Sep '20

07 Sep '20

Hi, We agreed in Wednesday's IRC meeting to take a short summer break from the klub. Let's meet again on 10th September. Thanks to everyone who has taken part in these meetings so far, we've had some really great discussions. As always, if anyone has ideas for topics, please add them to the Google doc. Looking forward to some more great sessions in September. https://docs.google.com/document/d/1EwQs2GXF-EvJZamEx9vQAOSDB5tCjsDCJyHQN5_… Thanks, Mark

1 1

[kolla] virtual PTG
by Mark Goddard 07 Sep '20

07 Sep '20

Hi, The next PTG will be virtual again, and held from Monday October 26th to Friday October 30th. For those who have not attended before, the PTG is where we discuss various aspects of the project, and eventually decide on priorities for the next development cycle. I have provisionally booked the same slots as last time: * Monday 26th 13:00 - 17:00 UTC (kolla & kolla ansible) * Tuesday 27th 13:00 - 17:00 UTC (kolla & kolla ansible) * Wednesday 28th 13:00 - 15:00 UTC (kayobe) Please get in touch if you would like to attend but these slots are not suitable for you. In particular, if you are in a time zone where these times are unsociable, we could consider running some sessions during a different 4 hour block. Thanks, Mark

1 0

[neutron][policy] Admin user can do anything without the control of policy.json?
by Zhi CZ Chang 07 Sep '20

07 Sep '20

2 1

[neutron] Bug deputy report (week starting on 2020-08-31)
by Bernard Cafarelli 07 Sep '20

07 Sep '20

Hello neutrinos, back to school week in some parts of the world, and new bug deputy rotation for us! Here is the bug list for week 36 A relatively quiet week on the new numbers count, all urgent bugs were handled Critical * openstack-tox-py36-with-ovsdbapp-master periodic job is failing everyday since 28.08.2020 - https://bugs.launchpad.net/neutron/+bug/1893965/ Patch merged in neutron https://review.opendev.org/#/c/749537/ High * [OVN Octavia Provider] OVN provider fails during listener delete - https://bugs.launchpad.net/neutron/+bug/1894136 Assigned to Brian Medium * [ovn] Limit the number of metadata workers - https://bugs.launchpad.net/neutron/+bug/1893656 Aims to use a separate config option than metadata_workers one, unassigned in neutron (working in tripleo and fixed in charm) * neutron-ovn-db-sync-util: Unhandled error: oslo_config.cfg.NoSuchOptError: no such option keystone_authtoken in group [DEFAULT] - https://bugs.launchpad.net/neutron/+bug/1894048 This was fixed previously in bug 1882020, but is observed again, unassigned * ovn: filtering hash ring nodes is not time zone aware - https://bugs.launchpad.net/neutron/+bug/1894117 Timezone fun, unassigned Wishlist * For neutron-l3-agent, after the execution of the linux command fails, it is not displayed which command failed to execute - https://bugs.launchpad.net/neutron/+bug/1893627 Add failed command to error log Patch merged: https://review.opendev.org/#/c/749076/ Incomplete * Upgrading from train(el7) to ussuri(el8): Packet sequence number wrong - got 2 expected 1 - https://bugs.launchpad.net/neutron/+bug/1894077 Migration error on port forwarding description Undecided * Get domain name for dhcp from neutron db - https://bugs.launchpad.net/neutron/+bug/1893802 This one needs confirmation from subject experts, but as described in comment I think this was attempted and reverted before - and this marked as invalid (or to fix in another way) -- Bernard Cafarelli

1 0

[mq][mariadb] What kind of reasons are considered when choosing the mq/mariadb version
by Brin Zhang(张百林) 07 Sep '20

07 Sep '20

Hi all We are using kolla to build the OpenStack, use kolla-ansible to deploy rabbitmq is v3.7.10, mariadb is v10.1.x when building Rocky release rabbitmq is v3.8.5, mariadb is v10.3.x when building Ussuri release what kind of reasons are considered as rabbitmq version is changed from v3.7.10 to v3.8.5 ? what kind of reasons are considered as mariadb version is changed from v10.1.x to v10.3.x ? If you can provide an explanation, or key explanation, we would be very grateful. Thanks. brinzhang

5 8

[kolla-ansible] prometheus.yml is empty
by Tony Liu 07 Sep '20

07 Sep '20

Hi, I deployed Prometheus with Kolla Ansible (10.1.0.dev36 from PIP). Given the following log, the change has been made on nodes. ============================= TASK [prometheus : Copying over prometheus config file] ************************ skipping: [os-control-2] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) skipping: [os-control-1] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) skipping: [os-control-3] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) skipping: [compute-1] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) changed: [monitor-2] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) changed: [monitor-1] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) changed: [monitor-3] => (item=/usr/local/share/kolla-ansible/ansible/roles/prometheus/templates/prometheus.yml.j2) ============================= But the /etc/kolla/prometheus-server/prometheus.yml on monitor-* nodes is empty. ============================= {} ============================= Anything I am missing here? Thanks! Tony

1 1

[sdk][python-openstackclient] Request the code review about the story: openstack CLI - Create an instance using --image-property filtering not working.
by Myeong Chul Chae 06 Sep '20

06 Sep '20

Hi. I researched the story 'openstack CLI - Create an instance using --image-property filtering not working' and modified the code to solve it. This is the issue that I opened. - Link <https://review.opendev.org/#/c/746405/> And the hyperlink of the story is here <https://storyboard.openstack.org/#!/story/2007860>. In addition, there is a review <https://review.opendev.org/#/c/740455/> posted before my review of the same story, so conflict resolution is necessary. Please check the commit message and history of the two reviews and continue the discussion.

1 0

[kolla-ansible] Difference between deploy and reconfigure?
by Tony Liu 06 Sep '20

06 Sep '20

Hi, What's the difference between deploy and reconfigure? I checked some roles, reconfigure.yml just include_tasks deploy.yml. And I didn't find reconfigure as a condition for any tasks or handlers. I checked kolla-ansible script, the difference is ANSIBLE_SERIAL is specified by reconfigure. I also see comment saying "Serial is not recommended and disabled by default.". Here are some cases. I'd like to know which should be used. #1 Add compute. After updating inventory with the new compute node, "deploy --limit new-compute" and "reconfigure --limit new-compute", do they have the same result? If not, what's the difference? #2 Change configuration. In case configuration is changed in global.yml or inventory, which of "deploy" or "reconfigure" should be executed to update the cluster? Same or any difference? #3 Fix the cluster I was told to rerun playbook to fix some problems, like a container was deleted. "deploy --limit host" or "reconfigure --limit host"? Same or any difference? Thanks! Tony

2 1