Monday, 2020-05-25

« Sunday, 2020-05-24 Index Tuesday, 2020-05-26 »
*** Torel has joined #openstack-kolla00:23
*** Torel has quit IRC00:30
*** Torel has joined #openstack-kolla00:31
*** hongbin_ has joined #openstack-kolla00:52
*** hongbin has quit IRC00:52
*** wuchunyang has joined #openstack-kolla01:24
*** wuchunyang has quit IRC01:35
*** jcmdln has joined #openstack-kolla03:18
*** evrardjp has quit IRC04:33
*** evrardjp has joined #openstack-kolla04:33
*** threestrands has joined #openstack-kolla04:38
*** e0ne has joined #openstack-kolla05:10
*** e0ne has quit IRC05:15
*** hongbin_ has quit IRC05:16
*** e0ne has joined #openstack-kolla05:22
*** e0ne has quit IRC05:26
*** cah_link has joined #openstack-kolla05:45
*** e0ne has joined #openstack-kolla05:46
*** e0ne has quit IRC05:51
*** e0ne has joined #openstack-kolla06:10
*** e0ne has quit IRC06:15
*** muhaha has joined #openstack-kolla06:16
*** sorin-mihai has quit IRC06:16
*** sorin-mihai has joined #openstack-kolla06:20
*** sorin-mihai has quit IRC06:26
yoctozeptomorning06:51
muhahaanyone tried kolla in k8s? with kubevirt/virtlet ?06:53
*** zijlboot has joined #openstack-kolla06:59
*** zijlboot has quit IRC07:03
mnasiadkamuhaha: control plane in kubevirt, or you plan to run compute nodes in kubevirt?07:05
*** zijlboot has joined #openstack-kolla07:05
mnasiadkamorning yoctozepto07:05
muhahamnasiadka  compute nodes, will it work with nested virtualization ? like kubernetes->kubevirt(kvm)->openstack->vm07:06
mnasiadkamuhaha: might be, but it's a health danger like skydiving without a parachute07:07
muhahai have already heard about kubernetes->openstack->kubernetes implementation07:07
muhahano sure why its dangerous, kubevirt is izolated vm, its not pod alike concept07:08
*** nikparasyr has joined #openstack-kolla07:09
mnasiadkamuhaha: it doesn't matter if it's kubernetes or not - if this is some research and not intended for production - sure, go for the extreme complexity, if it's for production - I think you're not aware of nested hypervisor cons...07:13
*** iniazi_ has joined #openstack-kolla07:14
*** iniazi has quit IRC07:16
muhahaof course its a lab07:16
*** sean-k-mooney has joined #openstack-kolla07:18
*** rpittau|afk is now known as rpittau07:21
*** k_mouza has joined #openstack-kolla07:23
*** jbadiapa has joined #openstack-kolla07:23
*** sorin-mihai has joined #openstack-kolla07:24
*** k_mouza has quit IRC07:28
*** amoralej|off is now known as amoralej07:32
*** arxcruz|off is now known as arxcruzz07:37
*** arxcruzz is now known as arxcruz07:37
*** kevko has quit IRC07:42
openstackgerritMerged openstack/kolla-ansible master: Make openstack_release more obvious  https://review.opendev.org/73049807:42
openstackgerritMerged openstack/kolla-ansible master: Remove confusing docs  https://review.opendev.org/73049907:43
muhahawhat are you recommending for creating ceph cluster ? is there anyting similar to kolla? like ceph-ansible ? does it use docker aswell ?07:47
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/train: Remove post_config from the Kibana role  https://review.opendev.org/73056807:51
yoctozeptomorning mnasiadka07:52
*** gkadam has joined #openstack-kolla08:03
*** gkadam has quit IRC08:03
openstackgerritMerged openstack/kolla master: Revert "Switch to Ussuri release of networking-l2gw tarball"  https://review.opendev.org/73051908:07
*** e0ne has joined #openstack-kolla08:07
*** e0ne has quit IRC08:12
*** e0ne has joined #openstack-kolla08:27
*** jonaspaulo has quit IRC08:27
mnasiadkamuhaha: we don't recommend anything, but most common tools to use are ceph-deploy and ceph-ansible08:29
muhahaand personally ?08:29
mnasiadkapersonally I don't recommend anything, but ceph-ansible should work - although it's not ideal :)08:29
mnasiadkahuh, ptg next week - time passes faster than usually I see08:36
*** gfidente has joined #openstack-kolla08:40
*** kevko has joined #openstack-kolla08:43
*** kevko has quit IRC08:48
yoctozeptomnasiadka: yeah, time flies nowadays08:48
openstackgerritRadosław Piliszek proposed openstack/kolla stable/ussuri: CI: Ignore more  https://review.opendev.org/73058208:49
openstackgerritRadosław Piliszek proposed openstack/kolla stable/train: CI: Ignore .zuul.d  https://review.opendev.org/73058508:51
openstackgerritRadosław Piliszek proposed openstack/kolla stable/train: CI: Ignore more  https://review.opendev.org/73058608:52
openstackgerritRadosław Piliszek proposed openstack/kolla stable/stein: CI: Ignore .zuul.d  https://review.opendev.org/73058708:52
openstackgerritRadosław Piliszek proposed openstack/kolla stable/stein: CI: Ignore more  https://review.opendev.org/73058808:53
openstackgerritRadosław Piliszek proposed openstack/kolla stable/ussuri: [Community goal] Update the contributor guide  https://review.opendev.org/73058908:59
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/ussuri: Check that used Ansible can see Kolla Ansible  https://review.opendev.org/73059209:14
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/train: Check that used Ansible can see Kolla Ansible  https://review.opendev.org/73059309:18
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/stein: Check that used Ansible can see Kolla Ansible  https://review.opendev.org/73059509:22
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/train: Make openstack_release more obvious  https://review.opendev.org/73059609:28
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/stein: Make openstack_release more obvious  https://review.opendev.org/73059709:29
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/ussuri: Fix kolla_source_version for stable  https://review.opendev.org/73059809:31
*** msalo has joined #openstack-kolla09:33
*** wuchunyang has joined #openstack-kolla09:36
*** wuchunyang has quit IRC09:38
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible master: Safeguard kolla_source_version  https://review.opendev.org/73060409:45
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/ussuri: Remove confusing docs  https://review.opendev.org/73060509:54
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/train: Remove confusing docs  https://review.opendev.org/73060609:54
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/stein: Remove confusing docs  https://review.opendev.org/73060810:06
*** rpittau is now known as rpittau|bbl10:12
hrwpci monring10:42
hrwyoctozepto: stable/stein is in a need of fixing10:43
*** muhaha has quit IRC10:59
*** Torel has quit IRC11:01
*** Torel has joined #openstack-kolla11:02
*** e0ne has quit IRC11:11
*** threestrands has quit IRC11:11
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: WIP: introduce non-infra-base image  https://review.opendev.org/70759911:15
openstackgerritMarcin Juszkiewicz proposed openstack/kolla master: WIP: Create 'infra' type of images  https://review.opendev.org/69875311:15
*** wuchunyang has joined #openstack-kolla11:18
*** wuchunyang has quit IRC11:26
sorin-mihaisean-k-mooney, yoctozepto, i'm still facing the same issue with cinder and nova. i tried source/ussuri, source/master and locally built source/master images, same kind of error "Database schema file with version doesn't exist". any other ideas, please? :)12:01
sean-k-mooneycan you share your kolla build config for the source/master12:02
sean-k-mooneywell sepcficlay the nova-base and cinder-base sections12:02
sorin-mihaididn't make any changes12:03
sean-k-mooneyyou need to update it to poing to master12:04
sean-k-mooneyhttps://github.com/openstack/kolla/blob/master/kolla/common/config.py#L3612:04
sean-k-mooneykolla pins to ussuri by changing OPENSTACK_RELEASE to ussuri on master12:05
sean-k-mooneywhile it is pinned12:05
sean-k-mooneyso to build master you need to set that to master12:05
sean-k-mooneyhttps://github.com/openstack/kolla/commit/4e41d1416e6a4d4296b4b27f447e58973b34a9c412:05
sean-k-mooneysorin-mihai: you can spcify it on the command line with --openstack-release=master12:06
*** mwhahaha has quit IRC12:07
sorin-mihaiwhile building changing the tag to something like 'local' is ok, i suppose?12:08
sean-k-mooneyyep12:08
sean-k-mooneyjust make sure you set the same tag in your global.yaml12:08
sorin-mihaiyeah12:09
*** e0ne has joined #openstack-kolla12:10
*** mwhahaha has joined #openstack-kolla12:10
*** rpittau|bbl is now known as rpittau12:11
sean-k-mooneysorin-mihai: if your doing it in production by the way i would proably do someing like "${branch}-${year}-${month}-${day}" for the tag12:27
sean-k-mooneythat way you can keep multiple version and have a knonw good tag you can role back too12:28
sean-k-mooneyid depens on your patch cycle if you do weekly patche or monthly patch you can use the week or month number instead12:28
sorin-mihaithanks, good idea. i wonder if i could track the git tag in the local branch that way12:32
sean-k-mooneywell there are multiple git tags so not really12:35
sean-k-mooneyif you are building from tarballs the tarball info i think will be added as metadata to the image12:36
sean-k-mooneyif you are building form git then you will have the git repo in the container and can check it12:36
sean-k-mooneyit might be nice to enhance kolla build to optionally generate a manifest file with all the inputs and souce repos/tarbs used for a given build12:37
*** wuchunyang has joined #openstack-kolla12:38
openstackgerritMichal Nasiadka proposed openstack/kolla-ansible master: Initial jinja2 templates syntax checks  https://review.opendev.org/72889412:40
sean-k-mooneyone think i allways taught was lacking but never urgent enough to add was integration with the releases repo. so instead of building form stable/<whatever> it would be nice to build using the latest released tag form that using the releases repo to corordinate that. anyway back to debuging networkign things12:41
*** wuchunyang has quit IRC12:43
*** born2bake has joined #openstack-kolla12:43
*** amoralej is now known as amoralej|lunch12:46
*** sorin-mihai_ has joined #openstack-kolla12:47
*** sorin-mihai has quit IRC12:48
*** wuchunyang has joined #openstack-kolla12:54
*** e0ne has quit IRC12:54
*** e0ne has joined #openstack-kolla12:54
*** Torel has quit IRC12:56
*** wuchunyang has quit IRC12:58
*** Torel has joined #openstack-kolla12:59
sorin-mihai_sean-k-mooney, that didn't work either, same error12:59
sorin-mihai_maybe i forgot something... changed .virtualenv/kolla/kolla/common/config.py to master, pip install ./kolla, built images with 'kolla-build -t source -b centos --openstack-release=master', changed tag to 'local' in globals13:01
openstackgerritChristian Berendt proposed openstack/kolla master: README: mark kolla-cli as deprecated & add kayobe  https://review.opendev.org/73045113:04
sean-k-mooneydid you try running an instance of the contianer image you build and chekcing the  contents of the file systemt to see if you have the migrations13:08
sean-k-mooneye.g. docker run --rm -it ...nova_base:local bash13:11
sean-k-mooneythen check the nova source directory to see if it has the migration files13:12
sean-k-mooneyif you have a multi node deployment you need to push the images to a local registry and pull them before you redeploy too13:12
yoctozeptosean-k-mooney: we actually do use releases on stable branches ;-)13:13
yoctozeptothe revert on master is messy but proceeding13:13
yoctozeptoboy, we need that made simpler13:14
sean-k-mooneyyoctozepto: when building from souce? im not just talking about libaryies by the way i mean of every project13:15
yoctozeptohrw: do you know what stein is grumpy about now?13:15
sean-k-mooneyyoctozepto: when we do the build from tabals or git it should be using the head of the branch for the srvice project when doing a source build13:15
yoctozeptosean-k-mooney: yes13:15
yoctozeptono, it uses releases13:16
yoctozeptoexcept on master branch13:16
sean-k-mooneyit should not be13:16
sean-k-mooneythat is not what it used to mean13:16
yoctozeptowell, it was already when I joined the party :-)13:16
sean-k-mooneystable/train on nova should when buidling form git should pull the tip of the stable train branch13:16
yoctozeptowell, it does not13:16
yoctozeptouses the hardcoded release version13:17
yoctozeptoinstead ;p13:17
sean-k-mooneywhere?13:17
yoctozeptoit bit me once13:17
yoctozeptowhen downloading the tarballs13:17
sean-k-mooneyyou mean this https://github.com/openstack/kolla/blob/stable/train/kolla/common/config.py#L307-L31013:18
yoctozeptothere is a huge dictionary in config py13:18
sean-k-mooneythat is not what i ment13:18
sean-k-mooneythere are 2 ways to build from source using a stable branch13:18
yoctozeptolook below, it has all sources pinned there13:18
sean-k-mooney*form souce tarballs13:19
sean-k-mooney1 you can checkout the stable/X branch an build13:19
sean-k-mooneyor you can checkout master and set openstck_release=stable/X13:19
sean-k-mooneythey have two different behaviors13:19
yoctozeptoyeah, but they might be incompatible this way13:20
sean-k-mooneywhat might be?13:20
yoctozeptoand master atm is still reverting to that behaviour13:20
yoctozeptotemplates change13:21
yoctozeptodifferent bases, pythons...13:21
sean-k-mooneyi personablly perfer to build using master and setting openstack_relsease13:21
yoctozeptoextra deps13:21
sean-k-mooneyya13:21
yoctozeptohardcore13:21
sean-k-mooneythat is true13:21
sean-k-mooneywell my orginal prefernce was to use git repos instead of tarbals by default for souce builds13:22
sean-k-mooneybut when i brough that up at the ptg i was overuled based on contianer size which is fair13:22
yoctozeptoI guess it would be nice13:22
sean-k-mooneynow im just lazy and pull them from docker hub13:22
sean-k-mooneyyoctozepto: we support building from git still13:22
yoctozeptoand then also have depends-on really working13:22
sean-k-mooneyyou just have to manually set type=git13:23
yoctozeptoone could optimize to not keep the repo but checkout files13:23
sean-k-mooneyand a few other things13:23
hrwyoctozepto: no idea. not even looked13:23
yoctozeptoor many13:23
yoctozeptohrw: ack13:23
sean-k-mooneyyoctozepto: if you havent use kolla to build form git there is an example here https://github.com/openstack/kolla/blob/stable/train/doc/source/admin/image-building.rst#build-openstack-from-source13:24
sean-k-mooney[keystone-base]13:24
sean-k-mooneytype = git13:24
sean-k-mooneylocation = https://opendev.org/openstack/keystone13:24
sean-k-mooneyreference = stable/mitaka13:24
sean-k-mooneyfor the short period of time i used kolla for dev that was how i used to do it13:25
yoctozeptosean-k-mooney: yeah, i know, but it has to be set for each deployed project13:27
yoctozeptoso not very simple13:27
sean-k-mooneyyep which is a pain13:27
sean-k-mooneyi was orginally arguing when that big config dict was added that we should be using git or adding both13:27
sean-k-mooneyi just went back to devstack in the end13:28
sean-k-mooneyrunning on a kolla deployed openstack13:28
sean-k-mooneyso if devstack messes up my enve i just spawn a new vm13:28
yoctozeptoI guess we can discuss that in the kolla ptg this time13:28
sean-k-mooneyit happens rearly enough that its fine13:28
*** e0ne has quit IRC13:29
sean-k-mooneyim sure ye have more imporant things to discuss13:29
sean-k-mooneyits why i never really pused for it after the inital change was merged13:29
*** e0ne has joined #openstack-kolla13:29
yoctozeptofwiw, i also run devstack on openstack deployed by kolla ;p13:29
yoctozeptoyeah, that is true13:29
yoctozeptobut having the ability to test incoming changes13:29
yoctozeptowould be nice13:30
sean-k-mooneyyep well i use devtack for that using its abilyt to deploy gerrit patches drectly13:30
sean-k-mooneybut that is the way i break my deployment most offten. swapping between branches to test random changes13:30
yoctozeptowell, the whole ci uses devstack for that reason :D13:31
sean-k-mooneyit uses it in a different way13:31
sean-k-mooneythe ci use prestaged git repos13:31
sean-k-mooneyand disable downlaoding of the git repos via git clone13:31
yoctozeptobut devstack can easily pick them up13:32
sean-k-mooneybut locally you can set NOVA_REPO to gerrit and NOVA_BRANCE to ref/for/whatever13:32
yoctozeptoand kolla not... yet13:32
sean-k-mooneyyoctozepto: so kolla could13:32
yoctozeptoyeah, yeah13:32
yoctozeptoindeed it couls13:32
sean-k-mooneykolla has the local install option or the git option13:32
sean-k-mooneyso you could use zull to premerge and prestage the repos13:32
yoctozeptojust someone to sit down and write that part13:32
sean-k-mooneythen point kolla build to those git treees13:33
yoctozeptoexactlt13:33
sean-k-mooneyno new code is need in kolla13:33
yoctozeptoexcept for pointing at proper places13:33
sean-k-mooneya change to how the image are built in the job13:33
sean-k-mooneyyes13:33
yoctozepto;p13:33
sean-k-mooneybut that is just a new kolla-build.conf file13:33
sean-k-mooneyif you did that then kolla could partly supprot depends-on13:34
sean-k-mooneythe other aspect of depends on would be for kolla and kolla ansible13:34
yoctozeptothat one does work13:35
yoctozeptobut only same branch13:35
sean-k-mooneye.g. makeing sure that if a patch to kolla-ansibel deplend on a a change to kolla that that patched kolla was used to build the image for the kolla ansible job13:35
sean-k-mooneyya not sure that different branches really makes sense although it might in limited cases13:35
sorin-mihai_what file should i look for?13:36
sean-k-mooneyim not 100% sure where nova will be in the image but you are looking for the migrations13:37
sean-k-mooneyso this directory https://github.com/openstack/nova/tree/master/nova/db/sqlalchemy/api_migrations/migrate_repo/versions13:37
sean-k-mooneyso $nova_source/nova/db/sqlalchemy/api_migrations/migrate_repo/versions13:38
*** amoralej|lunch is now known as amoralej13:38
sean-k-mooneyok so nova should be at /nova-base-source13:39
sean-k-mooneyhttps://github.com/openstack/kolla/blob/stable/train/docker/nova/nova-base/Dockerfile.j2#L12213:39
sean-k-mooneyso do "ls /nova-base-source/nova/db/sqlalchemy/api_migrations/migrate_repo/versions"13:40
sean-k-mooneyif you see   077_placeholder.py13:41
sean-k-mooneythen its master if you only see   072_placeholder.py13:41
sean-k-mooneyits ussuri13:41
sorin-mihai_nova-base-source/nova-21.0.0/nova/db/sqlalchemy/api_migrations/migrate_repo/versions/072_placeholder.py13:43
sean-k-mooneysorin-mihai_: how did you install kolla13:45
sean-k-mooneywas it from a package or from souces13:45
sorin-mihai_pip install ./kolla13:45
sean-k-mooneyok and what branch of kolla have you checked out13:46
sorin-mihai_master, then branched to a local one, but it's in sync with master13:46
sean-k-mooneynova-21.0.0 is not master13:47
sorin-mihai_i suppose that doing a git clone https://opendev.org/openstack/kolla.git and then changing kolla/common/config.py should do, right?13:50
*** nikparasyr has quit IRC13:51
sean-k-mooneyno you should do this properly13:52
sean-k-mooneyuse kolla build ot generate the config file and set the location to https://tarballs.opendev.org/openstack/nova/nova-master.tar.gz13:52
sean-k-mooneyif you are building image you should avoid the command line arge and allways prefer the config file13:52
sean-k-mooneythe command line argurement are fine but they are hard to use correctly and they dont really work well for contoling the souce locations13:53
yoctozeptosean-k-mooney: sry for the delay - it would be useful for upgrade jobs13:55
sean-k-mooneyyoctozepto: ya that was the edgecase i was thinking of too. although im not sure its totally required but yes13:56
sean-k-mooneyi have not been active in kolla for about 2 years so not really familar with how everything works on the ci front13:56
yoctozeptosean-k-mooney: yeah, it's rarely required13:56
*** rpittau is now known as rpittau|brb13:56
sorin-mihai_so, git clone, tox -e genconfig, and i see now that it has #location = $tarballs_base/openstack/nova/nova-21.0.0.tar.gz14:02
sorin-mihai_i guess i should force all images to the master tarballs just to make sure everything is in sync?14:04
openstackgerritMerged openstack/kolla stable/ussuri: CI: Ignore more  https://review.opendev.org/73058214:12
*** rpittau|brb is now known as rpittau14:30
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/train: Check that used Ansible can see Kolla Ansible  https://review.opendev.org/73059314:33
openstackgerritRadosław Piliszek proposed openstack/kolla-ansible stable/stein: Check that used Ansible can see Kolla Ansible  https://review.opendev.org/73059514:33
*** e0ne has quit IRC14:58
*** e0ne_ has joined #openstack-kolla14:58
openstackgerritMerged openstack/kolla stable/train: CI: Ignore .zuul.d  https://review.opendev.org/73058514:59
openstackgerritMerged openstack/kolla stable/train: CI: Ignore more  https://review.opendev.org/73058614:59
*** also_stingrayza has joined #openstack-kolla15:03
openstackgerritEmilien Macchi proposed openstack/kolla master: Revert "base: use en_US.UTF-8 locale on all distros"  https://review.opendev.org/73063315:04
*** stingrayza has quit IRC15:06
*** hamzy has quit IRC15:06
*** e0ne has joined #openstack-kolla15:07
*** e0ne_ has quit IRC15:07
openstackgerritMerged openstack/kolla-ansible stable/stein: Remove confusing docs  https://review.opendev.org/73060815:14
openstackgerritMerged openstack/kolla-ansible stable/train: Remove confusing docs  https://review.opendev.org/73060615:14
openstackgerritMerged openstack/kolla-ansible stable/ussuri: Remove confusing docs  https://review.opendev.org/73060515:17
*** seco has joined #openstack-kolla15:20
sorin-mihai_sean-k-mooney, thank you!15:30
sean-k-mooneysorry was on a call15:37
sean-k-mooneybut forceing all of them to be master is more or less up to you. in generall its a good idea but openstack service should be able to work with other services from sinilar releases15:38
sean-k-mooneye.g. ussuri nova can work with train neutron15:38
sean-k-mooneybut your better to keep thinks like nova and placement in sync15:39
sorin-mihai_deploying just nova worked, if cinder works the same way i'll just force them all to master for now to be sure they are all in sync and then wait some more until next upgrade15:42
*** e0ne_ has joined #openstack-kolla15:49
*** e0ne has quit IRC15:49
*** e0ne has joined #openstack-kolla15:51
*** e0ne_ has quit IRC15:51
*** jbadiapa has quit IRC16:10
*** e0ne has quit IRC16:18
*** e0ne has joined #openstack-kolla16:18
*** e0ne has quit IRC16:32
r3ap3ryoctozepto: I saw your comment on https://bugs.launchpad.net/kolla-ansible/train/+bug/1878412 and just wanted to ask here before proceeding. Was the intent for me to go ahead and try running a "reconfigure" with `central-logging` and `monasca` enabled in globals now or should I still wait for 9.1.1?16:32
openstackLaunchpad bug 1878412 in kolla-ansible train "CentOS 8 Failure of Restart elasticsearch container" [High,In progress] - Assigned to Mark Goddard (mgoddard)16:32
*** rpittau is now known as rpittau|afk16:48
*** stingrayza has joined #openstack-kolla16:51
*** jonaspaulo has joined #openstack-kolla16:51
*** also_stingrayza has quit IRC16:54
*** amoralej is now known as amoralej|off17:05
*** gfidente is now known as gfidente|afk17:09
yoctozeptor3ap3r: 9.1.117:10
yoctozeptor3ap3r: really as soon as those (or more) patches merge in the stable branch you could use it17:17
yoctozeptobut we are still in progress on that17:17
r3ap3ryoctozepto: Ok, I will hold off for now. Don't want to arbitrarily jump the gun on something right now. Thanks for yall's work on it. Very much appreciated. :-)17:19
openstackgerritMerged openstack/kolla stable/stein: CI: Ignore .zuul.d  https://review.opendev.org/73058717:21
openstackgerritMerged openstack/kolla stable/stein: CI: Ignore more  https://review.opendev.org/73058817:23
*** eliaswimmer has joined #openstack-kolla17:38
*** seco has quit IRC17:47
*** seco has joined #openstack-kolla18:20
*** seco has quit IRC18:25
*** Torel has quit IRC18:26
openstackgerritMerged openstack/kolla-ansible stable/train: Remove post_config from the Kibana role  https://review.opendev.org/73056818:30
*** seco has joined #openstack-kolla18:33
*** Torel has joined #openstack-kolla18:35
*** EmilienM has quit IRC18:39
*** EmilienM has joined #openstack-kolla18:41
*** wuchunyang has joined #openstack-kolla18:55
*** wuchunyang has quit IRC19:00
*** eliaswimmer has quit IRC19:02
*** Limech has joined #openstack-kolla20:15
r3ap3rQuick question, if I wanted to enable the `nested virtualization` capability, would I just set `cpu_mode=host-passthrough` in the  /etc/kolla/config/nova.conf before deployment right? Could I set this and do a `kolla-ansible reconfigure` to add the capability after the fact? I have already done everything required on the compute nodes to allow for nested virtualization, I just need to configure the option within20:17
r3ap3rOpenstack. Thanks.20:17
*** msalo has quit IRC21:07
*** Torel has quit IRC21:30
*** Torel has joined #openstack-kolla21:31
*** seco has quit IRC22:21
*** Torel has quit IRC22:30
*** Limech has quit IRC22:44
*** jonaspaulo has quit IRC22:45
*** ab-a has quit IRC23:24
« Sunday, 2020-05-24 Index Tuesday, 2020-05-26 »

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