Monday, 2021-07-05

*** rpittau|afk is now known as rpittau07:45
opendevreviewMark Goddard proposed openstack/kolla-ansible master: CI: stop setting ceph_nova_user  https://review.opendev.org/c/openstack/kolla-ansible/+/79891009:43
ignaziocassanohello, please I need help for using new images on kolla10:46
ignaziocassanoI modified the nova_compute images on my local registry putting a new manger.py 10:46
mgoddardignaziocassano: kolla-ansible pull10:47
ignaziocassanothen I ran kolla-ansible deply but on nova compute the container does not have the new manager.py 10:47
ignaziocassanoI tried also with kolla-ansible pull10:48
ignaziocassanolet me show10:48
mgoddardignaziocassano: if the tag is the same, deploy will not pull a new image10:48
ignaziocassanokolla deplyment host: docker images |grep compute10:48
mgoddardpull will overwrite existing tags10:49
ignaziocassanolocalhost:4000/kolla/ubuntu-source-nova-compute                 wallaby   f32f30b39a77   About an hour ago   1.4GB10:49
ignaziocassanoon compute host10:49
ignaziocassanoroot@tst2-kvm01:/home/ansible# docker images|grep compute 10.102.184.160:4000/kolla/ubuntu-source-nova-compute                 wallaby   a8a5f333a8e6   2 weeks ago   1.38GB10:49
ignaziocassanoahhh10:50
ignaziocassanoMust I change the tag ?10:50
ignaziocassanoLike mywallaby ?10:50
ignaziocassanoPlease, could anyone explain the corect procedure step by step ?10:54
priteauDid you push the image to the registry?10:56
ignaziocassanoyes10:58
ignaziocassanoI tagget it with newwallaby10:58
priteauThen if you've tagged it with a new tag name, you can set `nova_tag: newwallaby` and run a reconfigure11:01
priteauBut even keeping the tag as `wallaby`, you could do a pull followed by a deploy/reconfigure11:02
ignaziocassanosorry, where I must set nova_tag ?11:02
ignaziocassanoOk11:03
ignaziocassanoI returned to wallaby tag11:04
ignaziocassanoI ran  kolla-ansible -i /etc/kolla/multinode -e ansible_user=ansible -e ansible_become=true --limit  compute -t nova pull11:04
ignaziocassanobut on compute node my images remains with "two weeks ago" time11:05
priteaunova_tag belongs in your globals.yml 11:07
priteauThat may suggest that your image is not updated on the registry maybe?11:08
priteauhow did you run kolla-build?11:09
ignaziocassanoI did not run kolla-buold11:11
ignaziocassanoI created a container from local registry and I updtated files on it11:12
ignaziocassanothen I committed changes 11:12
ignaziocassanoProbably my procedure is wrong :-(11:13
ignaziocassanoany case on my deployment host I have: 11:14
ignaziocassanoocalhost:4000/kolla/ubuntu-source-nova-compute                 wallaby     f07482f9edfb   26 hours ago   1.4GB11:14
priteauSee, it says localhost11:14
ignaziocassanoafter pulling again on compute node I have:11:15
priteauyou need to tag it with your registry IP and push to it11:15
ignaziocassanoOK11:15
ignaziocassanoI will try again11:15
ignaziocassanoa question please: if the procedure is correct the time of the image on compute host must be the same of the deploymento host?11:16
priteauyes11:16
ignaziocassanoon compute I continue to have "two weeks ago" while on deployment I have "27 hours ago"11:20
ignaziocassanoNo I tried without modifying the image but pulling it from kolla repo and pusing on local registry11:21
ignaziocassanook11:27
ignaziocassanonow it works11:27
ignaziocassanothanks11:27
ignaziocassanoI forgot to push11:27
opendevreviewMerged openstack/kayobe stable/wallaby: Prevent matching unrelated images  https://review.opendev.org/c/openstack/kayobe/+/79924612:20
jingvarI can't find where can be enabled hostname configuration (fqdn, like controller1.my.cloud) and filling out  hostnames for all hosts12:52
jingvarIs the feature exist?12:53
jingvarhmm, /etc/hosts is ok12:56
jingvarif I right understand kolla_internal_fqdn should set domain name , "   kolla_external_fqdn: mykolla.example.net" 13:11
jingvarbut etc/kayobe/ doesn't have this variable13:12
jingvaretc/kolla/globals.yml:kolla_internal_fqdn: "192.168.37.2" - looks strange for me13:13
priteaujingvar: in kayobe fqdn are set via networks.yml13:52
opendevreviewMerged openstack/kayobe stable/victoria: Prevent matching unrelated images  https://review.opendev.org/c/openstack/kayobe/+/79924713:59
jingvar<priteau> thanks, i've found it.  interesting. Does it generate /etc/hosts like controller1 192.168.0.1 - controller1.internal 192.168.222.1 controller1.external 10.10.10.1? 14:13
priteauI don't think it does14:14
jingvarIs some example as look hostnames and endpoints with enabled fqdn without external DNS server14:16
jingvarCan I get somethinп similar with my cloud  /etc/hosts " 192.168.100.101 control01.stage.cloud control01" ? 14:20
mchlumskyHello! We are interested in deploying Adjutant in our clouds which are deployed using kolla-ansible. Adjutant isn't deployable via kolla-ansible (yet) but there are 2 unapproved blueprints for adding Adjutant to kolla/kolla-ansible: https://blueprints.launchpad.net/kolla-ansible/+spec/adjutant  https://blueprints.launchpad.net/kolla/+spec/adjutant14:49
mchlumsky. I can work on these blueprints but I'd like to make sure they are approved first.14:49
opendevreviewMaksim Malchuk proposed openstack/kolla-ansible master: Fix usage of Subject Alternative Name for TLS  https://review.opendev.org/c/openstack/kolla-ansible/+/79951115:00
opendevreviewMaksim Malchuk proposed openstack/kolla-ansible master: Blazar: Fix support for external keystone in multiregion deploy  https://review.opendev.org/c/openstack/kolla-ansible/+/79735915:07
opendevreviewMaksim Malchuk proposed openstack/kolla-ansible master: Blazar: Fix support for external keystone in multiregion deploy  https://review.opendev.org/c/openstack/kolla-ansible/+/79735915:09
opendevreviewMaksim Malchuk proposed openstack/kolla-ansible master: Fix the Tempest image url variable  https://review.opendev.org/c/openstack/kolla-ansible/+/78032815:44
*** rpittau is now known as rpittau|afk16:20

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