Tuesday, 2021-10-26

opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/wallaby: mariadb: Remove wsrep-notify.sh  https://review.opendev.org/c/openstack/kolla-ansible/+/81466806:05
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/wallaby: mariadb: Remove wsrep-notify.sh  https://review.opendev.org/c/openstack/kolla-ansible/+/81466806:06
eugenmayeris it known that using kolla_base_distro: with debian does not work when using neutron_plugin_agent: 'ovn' ... the docker images are missing for OVN06:08
jingvarmissed url or does't exist docker image?06:10
eugenmayerthe entire docker image does not exist (for xena)06:11
*** amoralej|off is now known as amoralej07:17
mnasiadkaeugenmayer: it will be soon there, let me check if we backported the patch.07:27
mnasiadkaeugenmayer: https://review.opendev.org/c/openstack/kolla/+/814945 - it's merging now, so if you are using our published images - it will be there tomorrow07:28
mnasiadkaor just wait for this to be merged, fetch the latest kolla code and build your own images07:28
eugenmayernice!07:45
eugenmayerthank you mnasiadka 07:45
eugenmayerIs this the final release for xena with kolla07:45
mnasiadkano, it's still rc1 - we should tag rc2 soon, and then most probably it will be the final release07:47
eugenmayergreat07:50
mgoddardmnasiadka: let's aim to have a list of release blockers by the end of weds meeting08:30
mnasiadkamgoddard: sure, good plan08:32
opendevreviewMichal Nasiadka proposed openstack/kolla-ansible stable/wallaby: mariadb: Remove wsrep-notify.sh  https://review.opendev.org/c/openstack/kolla-ansible/+/81466808:33
opendevreviewMark Goddard proposed openstack/kayobe master: CI: add Infra VM jobs  https://review.opendev.org/c/openstack/kayobe/+/81304808:35
opendevreviewMichal Nasiadka proposed openstack/kayobe master: Build overcloud host image directly with DIB  https://review.opendev.org/c/openstack/kayobe/+/77260908:50
yoctozeptoseemingly adjutant's fate is unknown again09:04
yoctozeptoon #openstack-tc today:09:04
yoctozepto05:38:19 <adriant> Not sure the best place to talk about this, but I'm leaving Catalystcloud, and while I plan to keep an eye on Adjutant stuff upstream a little (and may contract back for a short while) the project will ultimately not be something related to my new role, so either Catalystcloud will need to have someone step up eventually, or09:04
yoctozeptosomeone in the community will need to.09:04
yoctozepto05:38:33 <adriant> Not that I've had much time to work upstream in ages :(09:04
mnasiadkaBasically adjutant is dead, unless somebody picks that up - either from Catalyst Cloud or outside, fantastic09:06
hrwmnasiadka: Debian OpenStack team will build their repos for aarch64. We will have coverage.09:13
hrwmorning09:13
mnasiadkahrw: nice09:14
frickleryoctozepto: sad news, but good to know, thx for forwarding09:20
hrwmnasiadka: Linaro Developer Cloud still has resources. And is Kolla based ;D09:24
yoctozeptofrickler: sure thing!09:47
yoctozeptohrw: that is some really good news09:47
opendevreviewMerged openstack/kolla master: cinder-volume/ubuntu: add lsscsi and nvme  https://review.opendev.org/c/openstack/kolla/+/81361110:03
opendevreviewMerged openstack/kolla-ansible master: Fix wrong distro assumptions  https://review.opendev.org/c/openstack/kolla-ansible/+/81514010:03
opendevreviewMerged openstack/kolla stable/xena: monasca: enable for Debian/aarch64  https://review.opendev.org/c/openstack/kolla/+/81494310:20
opendevreviewMerged openstack/kolla stable/xena: ovn: Add Debian x86 images  https://review.opendev.org/c/openstack/kolla/+/81494510:20
opendevreviewMichal Nasiadka proposed openstack/kayobe master: Build overcloud host image directly with DIB  https://review.opendev.org/c/openstack/kayobe/+/77260910:31
opendevreviewMichal Nasiadka proposed openstack/kayobe master: Build overcloud host image directly with DIB  https://review.opendev.org/c/openstack/kayobe/+/77260910:35
opendevreviewMerged openstack/kayobe stable/xena: Update .gitreview for stable/xena  https://review.opendev.org/c/openstack/kayobe/+/81526710:50
opendevreviewMerged openstack/kayobe master: Update master for stable/xena  https://review.opendev.org/c/openstack/kayobe/+/81526810:50
opendevreviewMerged openstack/kayobe master: Add Python3 yoga unit tests  https://review.opendev.org/c/openstack/kayobe/+/81526910:50
opendevreviewMerged openstack/kayobe-config stable/xena: Update .gitreview for stable/xena  https://review.opendev.org/c/openstack/kayobe-config/+/81527010:50
opendevreviewMerged openstack/kayobe-config stable/xena: Update TOX_CONSTRAINTS_FILE for stable/xena  https://review.opendev.org/c/openstack/kayobe-config/+/81527110:50
opendevreviewMerged openstack/kayobe-config-dev stable/xena: Update .gitreview for stable/xena  https://review.opendev.org/c/openstack/kayobe-config-dev/+/81527210:50
opendevreviewMerged openstack/kayobe-config-dev stable/xena: Update TOX_CONSTRAINTS_FILE for stable/xena  https://review.opendev.org/c/openstack/kayobe-config-dev/+/81527310:50
*** amoralej is now known as amoralej|lunch11:08
em_when deploying (prechecking) on my production cluster if get a fail on 'Checking free port for OVN southbound'11:32
em_since i really build up the lap structure i'am not sure what this actually means11:32
em_got it, sorry. Configuration mistake11:43
*** amoralej|lunch is now known as amoralej12:24
opendevreviewMichal Nasiadka proposed openstack/kolla master: docs: weekly meetings page  https://review.opendev.org/c/openstack/kolla/+/81549413:05
opendevreviewRadosław Piliszek proposed openstack/kolla stable/xena: cinder-volume/ubuntu: add lsscsi and nvme  https://review.opendev.org/c/openstack/kolla/+/81544014:24
opendevreviewRadosław Piliszek proposed openstack/kolla stable/wallaby: cinder-volume/ubuntu: add lsscsi and nvme  https://review.opendev.org/c/openstack/kolla/+/81544114:25
opendevreviewRadosław Piliszek proposed openstack/kolla stable/victoria: cinder-volume/ubuntu: add lsscsi and nvme  https://review.opendev.org/c/openstack/kolla/+/81544214:25
opendevreviewRadosław Piliszek proposed openstack/kolla stable/ussuri: cinder-volume/ubuntu: add lsscsi and nvme  https://review.opendev.org/c/openstack/kolla/+/81544314:28
opendevreviewRadosław Piliszek proposed openstack/kolla-ansible stable/wallaby: mariadb: Do not use wsrep-notify.sh on Debian  https://review.opendev.org/c/openstack/kolla-ansible/+/81466814:29
opendevreviewPierre Riteau proposed openstack/kayobe master: Fix link syntax in release note  https://review.opendev.org/c/openstack/kayobe/+/81551515:35
opendevreviewMargaritaShakhova proposed openstack/kolla-ansible master: Placement/tasks/config: fix typo Closes-Bug: #1948835  https://review.opendev.org/c/openstack/kolla-ansible/+/81552416:18
opendevreviewMargaritaShakhova proposed openstack/kolla-ansible master: Placement/tasks/config: fix typo  https://review.opendev.org/c/openstack/kolla-ansible/+/81552416:38
*** amoralej is now known as amoralej|off17:16
EugenMayeri'am trying to deploy my prior home-lab build lab into the DC structure. I have 2 computes, 1 controller and 1 deployer. I'am using the same configuration exception host names and hypervisor type (kvm instead of qemu). When deploying (network type OVN) i suddently get an issue during verify with the task "TASK [ovn : Checking free port for OVN southbound db]"17:27
EugenMayeras far as i understand the soutbound should be on each network node ( or just on each compute node ) so it can recieve traffice from north (or send it there)17:28
EugenMayerfor all my 3 nodes (controller, compute1/2) it fails with "Checking free port for OVN southbound db\n  ^ here\n"17:28
EugenMayerlooking at the task, it is looked on the api_interface (which is set implicitly by the network_interface in my case), thus must be on the management lan. There is yet no single service running on those nodes, no firewall nothing so all ports should be actually availble17:30
EugenMayerany hint what i'am looking for?17:30
EugenMayeri found that the port is 6642 (/opt/kolla/share/kolla-ansible/ansible/group_vars/all.yml:ovn_sb_db_port: "6642") - scanning my management network address on e.g. compute1, i see that only 22 is take by ssh - thats it17:33
EugenMayerany hints were / what to look for?17:33
EugenMayerthe only possible difference to the lab is, that the mng interface in the lab is a pure interface (physical in terms of nic in openstack), while in the DC it is a VLAN interface bridging to thee (enp9s0.4002), so my network_interface is enp9s0.4002 - but i would not expect this to matter at all17:38
EugenMayer;/ found it, how ever, when moving the configuration to production into my chef cookbook i somehow stripped this 2 lines https://github.com/EugenMayer/openstack-lab/blob/master/config/multinode#L755 when copying it. That was stupid. Sorry17:46
jingvarmy OVN setup - admin_oc_net_name: mgmt  tunnel_net_name: tunnel provision_oc_net_name: provision_oc17:48
jingvarmgmt_vlan: 32217:48
jingvarprovision_oc - untugged(flat)17:48
jingvartunnel_vlan: 32617:48
jingvaron controllers -  ovn_controller, northd,sb_db, nb_db17:51
jingvaron compute nodes - only ovn controller17:54
EugenMayerjingvar, how did you configure your computes, are you using DVR or or not?17:54
jingvarDVR17:54
EugenMayerok, i'am planning to not use DVR for now17:54
jingvarno DVR for what?17:54
EugenMayernot sure what you mean - why i do not use DVR?17:55
jingvarkolla/globals.yaml 17:55
jingvarneutron_plugin_agent: "ovn"17:55
jingvarneutron_ovn_distributed_fip: "yes"17:55
EugenMayeri disabled distributed_fip - i want to route all floating ips through the northbridge (one) and then to the actual VMs17:58
jingvarAs I understand OVN itself works as OVS+DVR17:58
EugenMayerhttps://docs.openstack.org/networking-ovn/latest/admin/refarch/refarch.html - they see DVR / distributed fip as optional, if you need it, By default they seem to plan without it18:00
jingvarWhen using OVN - Kolla Ansible will not enable distributed floating ip functionality (not enable external bridges on computes) by default. 18:00
EugenMayeri have seen that, yes. Why do you use DVR - planning ahead for performance. Do you expect non DVR to be so much slower for usual traffic?18:02
jingvarfor external customers networks18:02
EugenMayerah you are working in a hosting company, i see. We do this for internal usage only18:04
jingvaranother usecase - when you need big traffic from an VM to external network - like backup, and don't want to do this through network node18:06
EugenMayerwhat are you using as an internal DNS? for the self-service LAN we plan to use powerDNS with integration to via openstack. Are there any better options? I usually use unbound for those split DNS setups, but i understand that powerDNS is better for IaaS with its rest APIs, including having the more conviniet GUIs18:07
jingvarIt outside my mind :) But our team use FreeIPA for some envs18:10
EugenMayerwell that might be a little oversized for us. But i see, it's a complete solution for multiple tings18:12
jingvaryep18:13
jingvarWe think about offline deployement18:14
jingvaras approach to get control on packaging - at first look there are many simple tools18:15
jingvar1 tool for clone repo , second one to docker images etc18:18
EugenMayerwell for now, it is now time to hit the trigger and deploy the cluster to the DC - let see :)18:18
jingvarwhat is DC? 18:19
EugenMayerwell you can easily pull the docker-images on an online instance, then use docker save to save each image into a file, package that, ship that to your offline instance and use docker-load to populate the docker-engine image registry18:19
EugenMayerDatacenter18:19
EugenMayerWith our software products we build, we offer entire offline deployments via docker18:20
jingvaryep, N - tools and how link that - control version- relaase18:20
EugenMayer(including maintenance and updates)18:21
jingvarI think it will be Pulp18:22
EugenMayeroh for that we use sonatype nexus and jfrog18:23
EugenMayerbut for packaging / distribution we have a lot more use cases and sure far more demand then a infrastrucutre company - but that is natural for sofware development18:23
EugenMayerwe host about 5 private docker registries, a couple of maven registries, gem/npm/composer registries, one conan (c++), raw registries, a couple of docker-mirror pull through caches and all of that18:24
jingvarI'll look at 18:24
EugenMayernever heard of pulp though18:24
EugenMayerfor pull through docker registry caches i would rahter supppose using registry - surely one can do this with jfrog/sonatype .. but usually you want several pull through caches, all over the place, near to your docker engines, to actually really save traffic. That is why we use this instead https://github.com/EugenMayer/docker-registry-cache-boilerplate18:28
EugenMayerof course you can use sonatype/jfrog/pulp for that, but they are probably too fat for 10 deployments in each sector. Still e.g. for maven group caches / compose / npm we use sonatype, since it's a lot less traffic then docker images18:28
opendevreviewMargaritaShakhova proposed openstack/kolla-ansible master: Fix broken deploy of placement service  https://review.opendev.org/c/openstack/kolla-ansible/+/81552421:45
opendevreviewMargaritaShakhova proposed openstack/kolla-ansible master: Fix broken deploy of placement service  https://review.opendev.org/c/openstack/kolla-ansible/+/81552421:49

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!