September 2020 - openstack-discuss

[ops][neutron]: Anyone using Calico with neutron in production?
by Imtiaz Chowdhury 21 Sep '20

21 Sep '20

Hi all, I have some Calico related questions and am wondering if any operators in this forum have experience in running Calico with OpenStack in production environment. Thanks and regards, Imtiaz

1 0

[nova] update field cpu_info.features value
by Alexander Usov 21 Sep '20

21 Sep '20

Hi guys, Several servers in the cluster have an older version of Intel microcode. I updated one of the servers and rebooted it. After reboot: root@xxx3:~# cat /proc/cpuinfo | grep flags | tail -1 flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cdp_l3 invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm cqm rdt_a rdseed adx smap intel_pt xsaveopt cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local dtherm ida arat pln pts flush_l1d root@xxx3:~# cat /proc/cpuinfo | grep micro | tail -1 microcode : 0xb000038 But the value on the controller didn't update: ~$ nova hypervisor-show 99 | grep ssbd xxx@admin:~$ I updated the value in the database, but it was immediately reverted If the way to update cpu_info.features value without deleting and adding the hypervisor? Nova version: 2:16.1.0 Thanks

2 1

[all] Forum Schedule is now LIVE!
by Kendall Nelson 21 Sep '20

21 Sep '20

Hello Everyone! The forum schedule is now live: https://www.openstack.org/summit/2020/summit-schedule/global-search?t=forum Please let myself or Jimmy McArthur know as soon as possible if you see any conflicts. Speakers will be contacted shortly (if not already) with more details about the event and your sessions. Thanks! -Kendall Nelson (diablo_rojo)

1 0

[tc] weekly update
by Mohammed Naser 21 Sep '20

21 Sep '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. # Patches ## Open Reviews - Retire devstack-plugin-pika project https://review.opendev.org/748730 - Clarify impact on releases for SIGs https://review.opendev.org/752699 - Define TC-approved release in a resolution https://review.opendev.org/752256 - Add assert:supports-standalone https://review.opendev.org/722399 - Add election schedule exceptions in charter https://review.opendev.org/751941 - Remove tc:approved-release tag https://review.opendev.org/749363 ## Project Updates - Add openstack/osops to Ops Docs and Tooling SIG https://review.opendev.org/749835 - Add python-dracclient to be owned by Hardware Vendor SIG https://review.opendev.org/745564 - Retire the devstack-plugin-zmq project https://review.opendev.org/748731 - Migrate rpm-packaging to a SIG https://review.opendev.org/752661 ## General Changes - Reinstate weekly meetings https://review.opendev.org/749279 - Resolution to define distributed leadership for projects https://review.opendev.org/744995 - Add exception for Sept 2020 term election https://review.opendev.org/751936 # Other Reminders - PTG Brainstorming: https://etherpad.opendev.org/p/tc-wallaby-ptg Thanks for reading! Mohammed & Kendall -- Mohammed Naser VEXXHOST, Inc.

1 0

[tripleo][ansible-ceph[ussuri][rdo][centos8] fails on ansible-ceph execution.
by Ruslanas Gžibovskis 21 Sep '20

21 Sep '20

Hi all, using tripleo 13.4.0-1.el8 and ceph-ansible 4.0.25-1.el8 on CentOS8 from @centos-openstack-ussuri repo. but get [1] error. I thought it was due to not found python exec, but I saw later, when added verbosity 4, that it is able to find python3. It looks like output in paste.openstack.org is too short, not sure what was an issue, but here is a second place [2] for same full output [1] http://paste.openstack.org/show/i2XpSBiSVjuL69Ahm1sl/ [2] https://proxy.qwq.lt/ceph-ansible.html -- Ruslanas Gžibovskis +370 6030 7030

2 12

Re: Re: [openstack-ansible] OpenStack Ansible deployment fails due to lxc containers not having network connection
by Oliver Wenz 21 Sep '20

21 Sep '20

Hi Jonathan, thank you for your reply! I probably should have specified that I already changed some default values in /etc/ansible/roles/lxc_hosts/defaults/main.yml to prevent a conflict with my storage network. Here's the part that I changed: ``` lxc_net_address: 10.255.255.1 lxc_net_netmask: 255.255.255.0 lxc_net_dhcp_range: 10.255.255.2,10.255.255.253 ``` Could there be some other reference to the original default address range which causes the error? I'm also confused about dnsmasq: Running 'apt-get install dnsmasq' I discovered that it wasn't installed on the infra host yet (though installing it also didn't solve the problem). Moreover, I couldn't find dnsmasq in the prerequisites in the OSA deployment guide. Kind regards, Oliver On 03/09/2020 18:38, openstack-discuss-request(a)lists.openstack.org wrote: > Message: 1 > Date: Thu, 3 Sep 2020 16:51:51 +0100 > From: Jonathan Rosser <jonathan.rosser(a)rd.bbc.co.uk> > To: openstack-discuss(a)lists.openstack.org > Subject: Re: [openstack-ansible] OpenStack Ansible deployment fails > due to lxc containers not having network connection > Message-ID: <e6746294-ada6-0f29-cdfb-59538396a0e0(a)rd.bbc.co.uk> > Content-Type: text/plain; charset=utf-8; format=flowed > > Hi Oliver, > > The default route would normally be via eth0 in the container, which I > suspect has some issue. > > This is given an address by dnsmasq/dhcp on the host and attached to > lxcbr0. This is where I would start to look. I am straight seeing that > the default address range used for eth0 is in conflict with your storage > network, so perhaps this is also something to look at. See > https://github.com/openstack/openstack-ansible-lxc_hosts/blob/master/defaul… > <https://github.com/openstack/openstack-ansible-lxc_hosts/blob/master/defaul…> > > You join us on irc at #openstack-ansible for some 'real-time' assistance > if necessary. > > Regards, > Jonathan. > > On 03/09/2020 16:18, Oliver Wenz wrote: >> I'm trying to deploy OpenStack Ansible. When running the first playbook >> ```openstack-ansible setup-hosts.yml```, there are errors for all >> containers during the task ```[openstack_hosts : Remove the blacklisted >> packages]``` (see below) and the playbook fails. >> >> ``` >> fatal: [infra1_repo_container-1f1565cd]: FAILED! => {"changed": false, >> "cmd": "apt-get update", "msg": "E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer has a >> Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> Release' no longer has a Release file.", "rc": 100, "stderr": "E: The >> repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer >> has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> Release' no longer has a Release file. >> E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> Release' no longer has a Release file. >> ", "stderr_lines": ["E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic Release' no longer has a >> Release file.", "E: The repository 'http://ubuntu.mirror.lrz.de/ubuntu >> bionic-updates Release' no longer has a Release file.", "E: The >> repository 'http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release' >> no longer has a Release file.", "E: The repository >> 'http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release' no longer >> has a Release file."], "stdout": "Ign:1 >> http://ubuntu.mirror.lrz.de/ubuntu bionic InRelease >> Ign:2 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates InRelease >> Ign:3 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports InRelease >> Ign:4 http://ubuntu.mirror.lrz.de/ubuntu bionic-security InRelease >> Err:5 http://ubuntu.mirror.lrz.de/ubuntu bionic Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:6 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:7 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Err:8 http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release >> Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable) >> Reading package lists... >> ", "stdout_lines": ["Ign:1 http://ubuntu.mirror.lrz.de/ubuntu bionic >> InRelease", "Ign:2 http://ubuntu.mirror.lrz.de/ubuntu bionic-updates >> InRelease", "Ign:3 http://ubuntu.mirror.lrz.de/ubuntu bionic-backports >> InRelease", "Ign:4 http://ubuntu.mirror.lrz.de/ubuntu bionic-security >> InRelease", "Err:5 http://ubuntu.mirror.lrz.de/ubuntu bionic Release", >> " Cannot initiate the connection to 192.168.100.6:8000 (192.168.100.6). >> - connect (101: Network is unreachable)", "Err:6 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-updates Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Err:7 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-backports Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Err:8 >> http://ubuntu.mirror.lrz.de/ubuntu bionic-security Release", " Cannot >> initiate the connection to 192.168.100.6:8000 (192.168.100.6). - connect >> (101: Network is unreachable)", "Reading package lists..."]} >> >> ``` >> >> When I attach to any container and run ```ping 192.168.100.6``` (local >> DNS), I get the same error (```connect: Network is unreachable```). >> However, when I specify an interface by running ```ping -I eth1 >> 192.168.100.6``` there is a successful connection. >> Running ```ip r``` on the infra_cinder container yields: >> ``` >> 10.0.3.0/24 dev eth2 proto kernel scope link src 10.0.3.5 >> 192.168.110.0/24 dev eth1 proto kernel scope link src 192.168.110.232 >> ``` >> so there seems to be no default route which is why the connection fails >> (similar for the other infra containers). Shouldn't OSA automatically >> configure this? I didn't find anything regarding a default route on >> containers in the Docs. >> >> Here's my openstack_user_config.yml: >> >> ``` >> cidr_networks: >> container: 192.168.110.0/24 >> tunnel: 192.168.32.0/24 >> storage: 10.0.3.0/24 >> >> used_ips: >> - "192.168.110.1,192.168.110.2" >> - "192.168.110.111" >> - "192.168.110.115" >> - "192.168.110.117,192.168.110.118" >> - "192.168.110.131,192.168.110.140" >> - "192.168.110.201,192.168.110.207" >> - "192.168.32.1,192.168.32.2" >> - "192.168.32.201,192.168.32.207" >> - "10.0.3.1" >> - "10.0.3.11,10.0.3.14" >> - "10.0.3.21,10.0.3.24" >> - "10.0.3.31,10.0.3.42" >> - "10.0.3.201,10.0.3.207" >> >> global_overrides: >> # The internal and external VIP should be different IPs, however they >> # do not need to be on separate networks. >> external_lb_vip_address: 192.168.100.168 >> internal_lb_vip_address: 192.168.110.201 >> management_bridge: "br-mgmt" >> provider_networks: >> - network: >> container_bridge: "br-mgmt" >> container_type: "veth" >> container_interface: "eth1" >> ip_from_q: "container" >> type: "raw" >> group_binds: >> - all_containers >> - hosts >> is_container_address: true >> - network: >> container_bridge: "br-vxlan" >> container_type: "veth" >> container_interface: "eth10" >> ip_from_q: "tunnel" >> type: "vxlan" >> range: "1:1000" >> net_name: "vxlan" >> group_binds: >> - neutron_linuxbridge_agent >> - network: >> container_bridge: "br-ext1" >> container_type: "veth" >> container_interface: "eth12" >> host_bind_override: "eth12" >> type: "flat" >> net_name: "ext_net" >> group_binds: >> - neutron_linuxbridge_agent >> - network: >> container_bridge: "br-storage" >> container_type: "veth" >> container_interface: "eth2" >> ip_from_q: "storage" >> type: "raw" >> group_binds: >> - glance_api >> - cinder_api >> - cinder_volume >> - nova_compute >> - swift-proxy >> >> ### >> ### Infrastructure >> ### >> >> # galera, memcache, rabbitmq, utility >> shared-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> # repository (apt cache, python packages, etc) >> repo-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> # load balancer >> haproxy_hosts: >> infra1: >> ip: 192.168.110.201 >> >> ### >> ### OpenStack >> ### >> >> os-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> identity_hosts: >> infra1: >> ip: 192.168.110.201 >> >> network_hosts: >> infra1: >> ip: 192.168.110.201 >> >> compute_hosts: >> compute1: >> ip: 192.168.110.204 >> compute2: >> ip: 192.168.110.205 >> compute3: >> ip: 192.168.110.206 >> compute4: >> ip: 192.168.110.207 >> >> storage-infra_hosts: >> infra1: >> ip: 192.168.110.201 >> >> storage_hosts: >> lvm-storage1: >> ip: 192.168.110.202 >> container_vars: >> cinder_backends: >> lvm: >> volume_backend_name: LVM_iSCSI >> volume_driver: cinder.volume.drivers.lvm.LVMVolumeDriver >> volume_group: cinder_volumes >> iscsi_ip_address: "{{ cinder_storage_address }}" >> limit_container_types: cinder_volume >> >> ``` >> >> I also asked this question on the server fault stackexchange: >> https://serverfault.com/questions/1032573/openstack-ansible-deployment-fail… >> >> >> Kind regards, >> Oliver >> >> >> >

2 1

Openstack version 18.04
by ops＠clustspace.com 21 Sep '20

21 Sep '20

Hello, We are decided to change Apache CloudStack to OpenStack. Trying to install, but only Stein....As you can see we have repositories ussuri root@ops:~# apt update Hit:1 http://ubuntu-cloud.archive.canonical.com/ubuntu bionic-updates/ussuri InRelease Hit:2 http://us.archive.ubuntu.com/ubuntu bionic InRelease Hit:3 http://security.ubuntu.com/ubuntu bionic-security InRelease Hit:4 http://us.archive.ubuntu.com/ubuntu bionic-updates InRelease Hit:5 http://us.archive.ubuntu.com/ubuntu bionic-backports InRelease Reading package lists... Done Building dependency tree Reading state information... Done All packages are up to date. root@ops:~# But after installation we got only Stein root@ops:~# openstack --version openstack 5.2.0 Do'es anyone have idea why we can install only Stein?

3 2

[tripleo][ansible-ceph][ussuri]ceph-ansiible fails at chown stack: /tmp/ceph_ansible_tmp on distributed compute HCI node
by Ruslanas Gžibovskis 21 Sep '20

21 Sep '20

Hi all, using tripleo 13.4.0-1.el8 and ceph-ansible 4.0.25-1.el8 on CentOS8 from @centos-openstack-ussuri repo. I get error [1]. When ansi playbook tries to chown to stack user dir: /tmp/ceph_ansible_tmp, but not able to find user stack. As I understand the deployment process, should it have tripleo-admin user? Also executed ansible.sh file with ansible-playbook -vvvv [2] it also has /home/stack/config-download/v3/ceph-ansible/create_ceph_ansible_remote_tmp.log I see in default file, it has the correct things set: owner: "{{ ansible_user | default('tripleo-admin', true) }}" In undercloud.conf I do not have deployment user set, that option is commented out. I have not set any in overcloud config files... [1] http://paste.openstack.org/show/798126/ [2] http://paste.openstack.org/show/798127 -- Ruslanas Gžibovskis +370 6030 7030

2 3

[tc] weekly meeting time
by Mohammed Naser 21 Sep '20

21 Sep '20

Hi folks: Given that we've landed the change to start having weekly meetings again, it's time to start picking a time: https://doodle.com/poll/xw2wiebm2ayqxvki A few people also mentioned they wouldn't mind taking the current office hours time towards that, I guess we can try and come to an agreement if we want to do that here (or simply by voting that time on the Doodle). Thanks, Mohammed -- Mohammed Naser VEXXHOST, Inc.

2 2

[tc][heat] PTL not available next week
by Rico Lin 19 Sep '20

19 Sep '20

Dear all Due to some personal matters, I'm not available next week 9/21-9/25. for releases, I already propose the patch [1]. And I'm fine with any renew on the patch as long as there's no new feature included (will try to keep update [1] too). [1] https://review.opendev.org/#/c/752809/ -- May The Force of OpenStack Be With You, *Rico Lin*irc: ricolin

1 0