Wednesday, 2022-02-16

opendevreviewMerged openstack/openstack-ansible stable/victoria: Bump SHA for openstack_hosts to pick up centos repos fix  https://review.opendev.org/c/openstack/openstack-ansible/+/82916901:02
ygk_12345i am facing this issue with OSA wallaby08:36
ygk_12345libvirt.libvirtError: unsupported configuration: interface fa:16:3e:42:20:3e - bandwidth settings are not supported for hostdev interfaces08:36
ygk_12345for sr-iov vms08:37
ygk_12345any workaround ?08:39
ygk_12345libvirt.libvirtError: unsupported configuration: interface fa:16:3e:42:20:3e - bandwidth settings are not supported for hostdev interfaces08:49
ygk_12345for wallaby OSA08:49
ygk_12345anyone ?08:49
ygk_12345is that a bug in wallaby ?08:56
andrewbonneyI'm not sure which settings it's referring to, but we ran SRIOV VMs in wallaby and now xena without issue08:57
ygk_12345andrewbonney: when I spin up a vm on sr-iov hosts, it is reporting the above error08:59
andrewbonneyI guess I'd be taking a look in the SRIOV config to see if any variables were perhaps removed in the W release, assuming they worked in V09:00
ygk_12345andrewbonney: which config file to be exact ?09:00
andrewbonneyIf your deploy is close to ours then I'd guess /etc/neutron/plugins/ml2/sriov_nic_agent.ini, but as the error is from libvirt it might be in a nova config file09:01
ygk_12345andrewbonney: i find no setting in the sriov*.ini file09:04
ygk_12345andrewbonney: i only see this in ova.conf : live_migration_bandwidth09:06
ygk_12345andrewbonney: nova.conf09:06
ygk_12345any workaround ?09:12
ygk_12345andrewbonney: any workaround ?09:22
ygk_12345libvirt.libvirtError: unsupported configuration: interface fa:16:3e:42:20:3e - bandwidth settings are not supported for hostdev interfaces09:22
opendevreviewJames Gibson proposed openstack/openstack-ansible-os_glance master: Add support for TLS to Glance  https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/82101109:28
opendevreviewJames Gibson proposed openstack/openstack-ansible-os_glance master: Add support for TLS to Glance  https://review.opendev.org/c/openstack/openstack-ansible-os_glance/+/82101109:41
andrewbonneyygk_12345: I haven't seen the error before so I'm not sure. Searching suggests it might be QoS related, but someone more familiar with libvirt might be able to suggest how to debug further09:42
opendevreviewMerged openstack/openstack-ansible-galera_server stable/xena: Use unix socket while granting access for the backup service  https://review.opendev.org/c/openstack/openstack-ansible-galera_server/+/82925910:10
opendevreviewMerged openstack/openstack-ansible stable/xena: Fix behaviour of OSA_CONFIG_DIR  https://review.opendev.org/c/openstack/openstack-ansible/+/82925611:20
opendevreviewMerged openstack/openstack-ansible stable/wallaby: Fix behaviour of OSA_CONFIG_DIR  https://review.opendev.org/c/openstack/openstack-ansible/+/82925711:20
*** dviroel|out is now known as dviroel11:21
opendevreviewMerged openstack/openstack-ansible-os_horizon stable/xena: Move Listen definition to VHosts  https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/82925412:20
opendevreviewMerged openstack/openstack-ansible-os_horizon stable/wallaby: Move Listen definition to VHosts  https://review.opendev.org/c/openstack/openstack-ansible-os_horizon/+/82925512:20
admin1hi guys .. so i am using gnocchi and redis incoming driver .. from inside the virtualenv, i did pip install redis and the driver is there .. but gnocchi is stuk on the logs saying there is no redis driver ..  ... here is the logs ..12:26
admin1https://gist.githubusercontent.com/a1git/14a2744c2995ffaf87b8e59cdd0bdcb9/raw/36f74dfda603fbb76cdc6dbb3db8bc102a3cb912/gistfile1.txt12:26
admin1sorry .. correct one: https://gist.githubusercontent.com/a1git/9e4ea9b08ecc4a24f8cc6e583220a6f5/raw/ca4d370de7057cd4ccc53539515005e3b45a2214/gistfile1.txt12:27
noonedeadpunkand what about `from redis import sentinel`?12:36
noonedeadpunkas I see it also needs `hiredis` package installed12:37
noonedeadpunkhttps://github.com/gnocchixyz/gnocchi/blob/master/setup.cfg#L72-L7312:38
admin1from redis import sentinel works fine .... hiredis is also installed 13:04
chandankumarjrosser: hello, please have a look at https://review.opendev.org/c/openstack/ansible-config_template/+/828295 https://review.opendev.org/c/openstack/openstack-ansible-os_tempest/+/828449 and https://review.opendev.org/c/openstack/ansible-role-python_venv_build/+/829164 when free, thanks!13:22
jrosserchandankumar: sure - I can look later today13:25
lowercaseHello, a req at work is having us use Fluentd in our openstack environment. After researching a bit I discovered kolla-ansible has fluentd compatibility and openstack-ansible does not. I checked the board and there are no fluentd. Has this ever been brought up before or requested?14:00
admin1You are not building wheels while running role against multiple hosts. This might result in DOS-ing OpenDev infrustructure servers. In order to proceed, please ensure that you have repo servers for selected OS version and architecture. If you want to avoid building wheel on purpose, ensure that you run playbook in serial manner. In case of causing14:10
admin1unreasonable load on the opendev.org git servers, your access may be blocked to protect other users and the OpenDev CI infrastructure which are reliant on this service. Found venv_build_targets: {'20.04': {'x86_64': 'r1c1_repo_container-87e33efa'}}"14:10
admin1is this a remote message or a osa error message ? 14:10
admin1all i am doing is running setup-openstack.yml14:10
lowercaseadmin1: i think the channel you want to join is #opendev and chat with them14:15
damiandabrowski[m]lowercase: we have ELK stack in our openstack-ansible-ops repo, but it uses logstash instead of fluentd: https://opendev.org/openstack/openstack-ansible-ops/src/branch/master/elk_metrics_7x14:19
admin1they ask me to go back and ask in this channel 14:20
damiandabrowski[m]@admin1 it's osa error message: https://opendev.org/openstack/ansible-role-python_venv_build/commit/de731e7f9e15a99e9587b42de175531bab3f401e14:20
lowercaseadmin1: sorry14:20
lowercasedamiandabrowski[m]: i am using Loki 14:21
admin1so .. i am setting up a new cluster .. it worked till gnocchi .. where i had to do some extra packages for redis, then i #  the rest of the setup and continuing only the failed playbooks14:21
admin1but now this fails with this error message all the time 14:22
admin1i need to run the full setup-openstack starting with keystone to not have this error ? 14:22
fungilowercase: it's an error message added by the openstack-ansible maintainers to help prevent openstack-ansible users from accidentally launching a giant ddos attack against the opendev git server farm14:22
lowercasefungi: i know, i am the one who did the original ddos'ng14:23
fungijrosser is familiar with the details and can probably explain more from the openstack-ansible side once he's around14:23
admin1but now its blocking my playbook runs .. so how do i proceed ? 14:23
lowercaseadmin1: one sec14:23
fungithe opendev sysadmins don't know (and shouldn't need to know) how to tell you how to properly configure openstack-ansible, but hopefully the maintainers of openstack-ansible can if their documentation isn't clear enough14:24
admin1-e venv_wheel_build_skip_check=true 14:24
jrosseradmin1: only do that if you’re happy to bypass the giant warning14:26
fungiif that ends up causing you to perform a massive number of git clone operations against opendev.org, the server admins for opendev will block your ip addresses and thus your playbooks14:26
jrosseradmin1: I think you need to take a moment to understand why you get that message14:27
admin1jrosser, this is my setup-openstack now .. https://gist.githubusercontent.com/a1git/85fb28075866cedd04bf96c9ecbc97de/raw/1c919131199476c6dfedb0effc25a805573b4452/gistfile1.txt14:27
admin1it should not clone it 14:27
jrosserI’m not following, tbh14:28
admin1ok .. i am setting up a new cluster .. it went till gnocchi .. and failed due to radius .. i control C ..   install the radius stuff and gnocchi is done .. then i # the rest and re-run the setup-openstack playbook 14:29
jrosserlowercase: regarding fluentd, we dont directly integrate any particular monitoring stack directly14:29
admin1and now getting this error 14:29
lowercasejrosser: would you be interested in having a monitoring stack in the playbooks?14:29
admin1i brb in 30 min .. 14:30
jrosserlowercase: you should look in the openstack-ansible-ops repo where we have a bunch of “3rd party” stuff like that14:30
lowercaselooks like there is just elk and graylog in there. no fluentd sauce 14:33
lowercasewelp, guess ill continue copying all the code out of kolla-ansible and adapting it for my use case.14:34
jrosserlowercase: the openstack-ansible-ops repo is really a collection of useful stuff that operators have contributed that doesnt want to sit permanently in OSA14:38
jrosserit is almost certainly the case that not everyone wants fluentd, just like not everyone wants ELK so the maintenance overhead of having it all integrated would be too much14:38
jrosserfor exmaple, my team has put most of the work into the elk stack in openstack-ansible-ops becasue thats what we use in our deployment14:39
noonedeadpunklowercase: eventually indeed we do miss fluentd output and support for oslo. I was thinking about making journald usage onfigurable with variable. As it's basically matter of 1 setting, so patch should be trivial I guess?14:41
lowercasethat would be helpful, I am going to investigate how to integrate the kolla-ansible curated filters against journal. Afaik its still possible, i just haven't figured it out.14:43
lowercaseCause at the end of the day, its just a source with a tag. Now is there a way i can discriminate which filter gets applied based on a key word element in the log? idk. 14:45
lowercaseNow truly this would be a copy paste job if the log files were written to a file.14:45
spatelkolla-ansible dump logs in flat file where we can easily tail log for issue etc.. that kind of feature would be good in OSA 14:49
spatelcurrently if i don't have ELK then its little difficult to debig14:50
spateldebug*14:50
noonedeadpunklowercase: well log files is poor thing imo14:50
noonedeadpunkit don't have metadata avaialble and should be managed hevaily14:51
lowercaseabsolutely agreed, but if there is centralized logging you're not looking at logs on a server anyway.14:51
noonedeadpunkat the same time if you want fluentd you still don't need files14:51
mgariepyjouirnactl -f -u unit-file.service or slice works ok14:51
noonedeadpunkyou can't really parse plain text files. But if you forward or transofrm journald to syslog, you have metadata avialble14:52
noonedeadpunkAs example - I used that to forward journal to graylog https://opendev.org/openstack/openstack-ansible-ops/src/branch/master/graylog/graylog-forward-logs.yml14:52
spatelnoonedeadpunk i am also doing journalbeat to push logs to graylog. (This is for big deployment) 14:53
noonedeadpunkand for fluent you still want to use https://docs.openstack.org/oslo.log/latest/reference/formatters.html#oslo_log.formatters.FluentFormatter I bet14:53
lowercasenoonedeadpunk: fluentd has one thing i haven't figured out. Journal has logs for everything, I need fluentd to be able to discriminate which service it is and apply different regex filters on it to get the awesome clean fluentd json format.14:53
spatelWe have couple of small deployment like 20 or 30 node stack where we don't want to run ELK 14:53
noonedeadpunkso openstack services can be configured to send logs natively to fluent14:54
noonedeadpunkI haven't used that in prod a lot though14:54
lowercasewell how the eff do i use that14:54
lowercasethats amazing 14:55
noonedeadpunkI _think_ that instead of `use_journal` `use_json` should be used with some other set of options...14:58
noonedeadpunkI can recall somebody using that tbh...14:59
noonedeadpunkoh, here's some config sample for oslo https://docs.openstack.org/oslo.log/latest/admin/example_nova.html15:00
noonedeadpunklowercase: ^15:01
noonedeadpunkI believe this should be applicable for any service15:01
noonedeadpunkBut you would need to use config_overrides everywhere as of today to make it happen15:01
noonedeadpunkAs no neat variable is present15:02
jrosserfeels like we should have some global stuff for setting that15:02
jrosseras it looks super useful15:02
noonedeadpunkoh yes15:02
noonedeadpunkI'm thinking about it for a while indeed :)15:02
jrossernice low-hanging fruit contribution there for someone :)15:02
noonedeadpunkbut still it's doable as of today, just with more effort15:02
lowercasecertainly, and this a better solution than laying out flat config files for fluentd. So much less transformation that needs to happen15:03
jrosserlowercase: you're familiar with our config overrrides?15:03
lowercaseyea15:03
jrossercool, like noonedeadpunk says you can make a whole bunch of those to add this in15:03
jrosserjust beware that you can only define them once per service unless you are really knowing whats going on15:04
lowercasenice. Once i do figure it out. I'm not saying i will make a point to feature request and PR some sauce for you. 15:04
jrosserso if you already override something for nova, you need to add to that, rather than make another15:05
lowercaseoh yea no worries there15:05
noonedeadpunkalso with that I dunno if you might want to set `use_journald = False`15:05
lowercasehmm.. good point15:06
noonedeadpunkstill doable with same override15:06
noonedeadpunkdoh.. .according to doc each venv would require `fluent-logger` to be installed...15:08
noonedeadpunkand that is more tricky thing to do tbh...15:08
jrosseri am having memories of osprofiler15:08
jrosserthat was similar, and i think there are vars for extra pip packages?15:09
noonedeadpunkum, not really?15:10
noonedeadpunkor well, dunno..15:10
lowercasepip_extra_packages ?15:11
jrosserhttps://github.com/openstack/openstack-ansible-os_keystone/blob/master/defaults/main.yml#L49415:11
jrosserthat sort of thing15:11
noonedeadpunkI'm not sure it's around for all roles tbh15:11
noonedeadpunkOr well, I;'m pretty sure it's not15:12
lowercasenova_user_pip_packages: []15:12
lowercaseyeah15:12
noonedeadpunkwell, core roles at least does...15:12
lowercasei dont think so either because ive ran into it where i think it was cinder needed an additional ceph package and i couldn't add it15:12
lowercasehmm its in cinder15:13
noonedeadpunkcinder has it https://opendev.org/openstack/openstack-ansible-os_cinder/src/branch/master/defaults/main.yml#L31115:13
noonedeadpunkall core roles does from what I see https://codesearch.opendev.org/?q=_user_pip_packages&i=nope&literal=nope&files=&excludeFiles=&repos=15:14
lowercasethat's a handy tool15:15
noonedeadpunkit really is :)15:23
noonedeadpunkthe missing thing is search for branches :(15:23
noonedeadpunkas you see only master15:23
admin1jrosser, noonedeadpunk .. i am back .. ok ..so assuming something is wrong with the playbooks or deployment, how to not load opendev ? 15:24
admin1can we proxy the packages in a local repo ? 15:24
noonedeadpunkreplace opendev with github for openstack_services.yml ? :D15:27
noonedeadpunkBut, well, IMO, it's worth fixing issue why wheels build fails imo15:27
noonedeadpunkit's kind of almost always easier thing to do15:28
lowercasewhat is the reason thats still the default. I know i have ddos'd you guys before cause thats the default lol15:28
noonedeadpunk`replace opendev with github` -> and we don't care about loading Microsoft lol15:28
noonedeadpunklowercase: well, it's not really default tbh. It was us trying to recover things when they went unexpected which lead to such possibility of ddos15:30
noonedeadpunknow we added failure message that makes you aware that things going wrong15:30
noonedeadpunkas dos happens when you run things against all computes for instance15:31
noonedeadpunkwhile it could be valid behaviour for single controller during OS upgrade for example15:31
*** dviroel is now known as dviroel|lunch15:31
noonedeadpunkSo we merged and backported that https://opendev.org/openstack/ansible-role-python_venv_build/commit/de731e7f9e15a99e9587b42de175531bab3f401e15:31
noonedeadpunkit was more that we haven't thought through that ppl will upgrade computes before getting controllers upgraded :)15:32
fungiyeah, the past incidents were mostly when there were dozens (or hundreds) of servers all being told to deploy openstack software at the same time and couldn't find a cache (pre-built wheels, i suppose?) in the local environment so every server independently pulled the source code over the internet. changing your git remotes to github may avoid creating a flood for opendev, but it15:36
fungidoesn't solve the problem that your entire environment just decided to download many redundant copies of the exact same things15:36
fungiand independently run identical compilation of the source repositories into wheel form, and so on15:37
jrosseradmin1: best to look at the conditions on the task that has failed15:41
jrosserand then look ad the values you get in your deployment, and understand the reason why, then fix15:41
spateladmin1 are you sure that your playbook overload opendev15:46
opendevreviewJames Denton proposed openstack/openstack-ansible-ops master: Update MNAIO for Focal  https://review.opendev.org/c/openstack/openstack-ansible-ops/+/82448615:47
fungispatel: it didn't, the error from the playbooks was prophylactic15:47
spatel+115:48
jrosserspatel: the error is triggered when the conditions in the deployment are not as expected15:48
jrossersadly no-one who encouters this has debugged sufficiently to get to the root cause, other than doing "computes before infra" upgrades15:49
jrosserso ultimately it may be actually a documentation ambiguity, or we handle something wrong at upgrade, or something entirely else......15:50
fungiand switching the git remote to github isn't really an ideal solution either. as anyone who's run a ci system for testing software on github can attest, even github will block you for performing excessive git operations15:51
noonedeadpunkwell, basically there were 2 options - either to fully remove fallback when repo host couldn't be found, which is not great as we assume that the role to build vevn is re-usable outside of the osa, so having container with wheels is not always good assumption15:59
noonedeadpunkor to add check that we don't run without wheels agaist set of hosts15:59
noonedeadpunkso if it's ran against single host or with serial - it won't really cause load. Yes, traffic still will be insane, but end of the day this will take internity for deployer and likely motivate to fix things on their side16:00
*** dviroel|lunch is now known as dviroel16:39
admin1spatel, i don't think my playbooks overload opendev .. i almost never tinker with the playbooks .. just use them as-is 17:11
admin1the max i change is the variables 17:11
jrosseradmin1: it would be really helpful to us to understand the conditions in your deployment which cause that error17:27
admin1so variables ? 17:30
admin1and config 17:30
admin1jrosser, https://gist.githubusercontent.com/a1git/4c6376ede6b65993fd1e55c251fc0d00/raw/43322ef837ab7774f160151003a6186d9b81f8cc/gistfile1.txt17:37
jrosserI mean looking at the values you get for the conditionals in the task that failed17:38
opendevreviewMerged openstack/ansible-config_template master: Move zuul jobs layout to centos9 only for master branch  https://review.opendev.org/c/openstack/ansible-config_template/+/82829517:38
jrosserand the working out why that is the case17:38
jrosserthe config doesn’t really help17:38
admin1setup-hosts =pass,  setup-infra = pass .. 17:39
admin1let me try to get the logs for setup-openstack17:39
admin1jrosser, not sure if this helps ..  ( this much i could get from tmux ) .. https://gist.githubusercontent.com/a1git/bbdef3bc0c11a20f243b27f958b627b9/raw/90ca16b7a4a6d44770d56cf9c4ecceecc055c152/gistfile1.txt     -- basically if i return, except utility and ceilometer .. everything else is good 17:42
admin1i am now running again openstack-ansible  setup-openstack.yml  -vvvv    to a log file so that i can pass  the logs 17:43
spateladmin1 openstack-ansible default logs all output in /openstack/ansible/log file.. i don't correct path but it does put stuff somewhere there 17:45
jrosseryou can also delete/move the log file to get one only containing the latest run17:46
admin1err.. in the deployment host ? 17:53
admin1got it .. got it17:54
spatelwhat is wrong with my command:  openstack role list --user spatel --user-domain ostack2 --project production19:35
spatelopenstack role list: error: unrecognized arguments: --user spatel --project production 19:36
spatelgetting error 19:36
jrosserit's not an expected parameter?19:37
jrosser`usage: openstack role list [-h] [-f {csv,df-to-csv,json,table,value,yaml}] [-c COLUMN] [--format-config-file FORMAT_CONFIG] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--sort-ascending | --sort-descending] [--domain <domain>]`19:37
spatelhmm, same command working with my other openstack running in stein 19:38
spatelmay be in recent openstack this thing changed 19:39
spateli want to see my role in production project19:39
spateljrosser they replaced that command with openstack role assignment list :(19:47
spatelcrap! 19:47
admin1ok .. i have the full log .. trying to upload it somewhere 19:52
admin1its over my head on why this is happening19:53
admin1will try to arrange an url 19:53
admin1jrosser, spatel .. sorry for the full log . but here it is => http://admin0.nl/build.txt20:01
spatelomg! this is massive file. you should just port error section20:02
spatelin bottom its saying failed=0 so what is the wrong here? everything looks good to me20:03
admin1search failed=1 20:05
admin1there are 4 failed services ..  3x  utility and 1x ceilometer20:05
admin1and then just above is the DOS message20:05
jrosseryou say it's the utlity container, yes that is the host with the failed task20:06
jrosserbut which playbook are we in?20:06
jrosserrally?20:06
admin1setup-openstack.yml 20:06
admin1its the whole output of setup-openstack wtih -vvvv 20:07
jrossersure, i see that20:07
admin1sorry for the big file .. wget and   opening via code/sublime might be faster 20:07
admin1my question is .. what can i do to not have this issue .. and also why exactly this issue is 20:08
jrosserthat is what i want to find20:08
jrosseryour config will not say20:08
jrosseryou know that setup-openstack.yml is just a playbook which includes many others?20:08
admin1which is why i included -vvvv  20:09
jrosserand you can run all of those others individually to try to narrow down20:09
jrosser-vvvv just adds a whole heap of extra info about each task SSH connection20:09
jrosseryou can run openstack-ansible playbooks/<whatever-you-need>.yml20:10
admin1as far as i have recalled, the error comes during ceilometer 20:11
admin1so just run ceilometer role and capture logs  ? 20:11
jrosserwhen i scroll back from the end of your file the last thing it was trying to do was install rally20:12
jrosserand then when i go look in the code, i see this https://github.com/openstack/openstack-ansible-os_rally/blob/master/tasks/main.yml#L6020:12
jrosserso i understand why that DDOS warning is produced when installing rally20:12
admin1i will comment out rally .. don't really use it .. 20:13
jrosserif you have another error when installing ceilometer, then you can run just the ceilometer playbook on it's own20:13
jrosserand you can also rename the giant log file so that you get a fresh one20:13
admin1it took a while to take out the log .. multiple ssh and a remote desktop :D20:14
admin1so the rally thing ...  that line .. what does it acutally mean ? 20:15
admin1since i made zero changes, does this mean everyone else doign the same playbooks as me will face that issue20:15
admin1or i am facing issue coz i don't have rally, and thus its just triggering it since i am running the playbook but not using it ? 20:15
jrosser"when installing rally into the virtualenv, do not use the repo server to build wheels"20:15
admin1oh .. that means take it direct from opendev ? 20:16
jrosserand that then makes this fail https://github.com/openstack/ansible-role-python_venv_build/blob/master/tasks/main.yml#L5720:17
jrosserit always takes it direct from opendev20:17
jrosserso this is a bug which we need to fix20:17
jrosseri would like to know what happens for ceilometer20:19
admin1now i know. i am going to dig deeper 20:19
admin1many thanks 20:19
jrosseri think that the condition that makes a failure is maybe too strict20:20
admin1i have gnocchi with redis.. and ceilometer needs to initialize db .. so i am moving towards that 20:20
jrosserif it were checking for >3 hosts rather than >2 hosts then you would not get this fail on rally20:20
jrossernoonedeadpunk: ^20:20
jrosserwhat is is really trying to prevent is you running os_nova against 100s of compute nodes in parallel20:21
jrosserwhen wheel building is for some reason disabled or broken20:21
admin1is there a way to mirror local repo so that  no matter what happens, opendev is only used ones and then cached 20:22
admin1that way, it might be future proof 20:22
jrosserwell, in the same group of stuff we use for dhcp/tftp/pxe is a server running apache + gitweb and a bunch of cron jobs to keep all the repos OSA needs fresh20:24
jrosserand then we override the relevant variables to point to those instead of opendev20:24
jrosserbut thats pretty much up to you if you want to do that / how you do it20:24
admin1thank you for the hint .. 20:25
admin1i will look into it 20:25
admin1or maybe contribute to host a repo mirror ? 20:26
admin1is that also allowed ? 20:26
jrosserthe repo server used to do this20:26
jrosserbut it was not helpful as deployments wanting an internal git mirrror generally had their own already20:27
jrosserand it's complicated with the loadbalancer and upgrades20:27
jrosserso imho this is something that best sits outside OSA, like whatever you have for host provisioning20:28
opendevreviewMerged openstack/openstack-ansible-ops master: Update MNAIO for Focal  https://review.opendev.org/c/openstack/openstack-ansible-ops/+/82448621:24
*** dviroel is now known as dviroel|out21:26
*** prometheanfire is now known as Guest222:59
*** Guest2 is now known as prometheanfire23:05

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