Thursday, 2018-11-01

*** masber has quit IRC00:32
*** masber has joined #openstack-kolla00:33
masbergood morning, I put new config in /etc/kolla/config/nova-scheduler/nova.config and then ran kolla-ansible reconfigure -i multinode. but I can't see the new config in the controller node grep -i "filter" -r /etc/kolla/*00:36
masberany idea?00:36
masberreconfigure finish successfully00:36
*** zul has quit IRC01:04
*** xinliang has quit IRC01:06
*** hongbin has joined #openstack-kolla01:24
openstackgerritwangwei proposed openstack/kolla master: Support multipath disk for bluestore in kolla  https://review.openstack.org/59996101:28
*** phuoc has joined #openstack-kolla01:28
openstackgerritwangwei proposed openstack/kolla-ansible master: Support multipath disk for bluestore in kolla-ansible  https://review.openstack.org/59996201:30
openstackgerritwangwei proposed openstack/kolla-ansible master: Support multipath disk for bluestore in kolla-ansible  https://review.openstack.org/59996201:57
*** unicell has quit IRC02:00
*** Pavo has joined #openstack-kolla02:00
*** Pavo has quit IRC02:11
adrianrezamasber: I think it should be /etc/kolla/config/nova/nova-scheduler.conf then run kolla-ansible reconfigure command03:46
masberadrianreza, I just tried that and I still can't get it to work http://paste.openstack.org/show/733749/04:06
masberhold on, why /etc/kolla/config/nova/nova-scheduler.conf and not /etc/kolla/config/nova/nova-scheduler/nova.conf?04:07
*** unicell has joined #openstack-kolla04:24
adrianrezamasber: you can read here https://docs.openstack.org/kolla-ansible/latest/admin/advanced-configuration.html#openstack-service-configuration-in-kolla I just follow from there04:27
adrianrezamasber: the example in there is exactly for nova-scheduler.conf04:28
*** hongbin has quit IRC04:37
*** unicell has quit IRC04:39
*** ducnv has quit IRC05:10
*** letrangg has quit IRC05:10
*** ducnv has joined #openstack-kolla05:11
*** letrangg has joined #openstack-kolla05:11
masberadrianreza, you are totally right! thank you!05:20
masberdo i need to restart the services after kolla-ansible reconigure?05:51
*** opMD has joined #openstack-kolla06:09
*** masuberu has joined #openstack-kolla06:30
*** masber has quit IRC06:33
adrianrezamasber: you can check from docker ps, if you didnt see any related container restarted, you may restart them manually06:33
adrianrezamasber: kolla-ansible reconfigure restart related container automatically06:34
*** cah_link has joined #openstack-kolla06:42
*** xinliang has joined #openstack-kolla06:45
opMDGood morning, I was wondering if someone here could help. We have deployed the core of Openstack using Kolla-Ansible and now are trying to add Ceilometer with Gnocchi. We've run into an issue where the deployment of Ceilometer fails while bootstrapping. The ceilometer-upgrade command in the ceilometer-bootstrap container fails with a 500 error connecting the gnocchi api.06:50
opMDThe error in the gnocchi-api logs:06:50
opMDmod_wsgi (pid=19): Target WSGI script '/usr/bin/gnocchi-api' cannot be loaded as Python module.06:50
opMDmod_wsgi (pid=19): Exception occurred processing WSGI script '/usr/bin/gnocchi-api'.06:50
opMD Traceback (most recent call last):06:50
opMD   File "/usr/bin/gnocchi-api", line 20, in <module>06:50
opMD     from gnocchi.cli import api06:51
opMDImportError: No module named gnocchi.cli06:51
opMDany ideas?06:51
*** gkadam has joined #openstack-kolla06:58
*** mattgo has joined #openstack-kolla07:35
*** pcaruana|elisa| has joined #openstack-kolla07:40
*** hamzaachi has joined #openstack-kolla07:53
*** lvdombrkr has joined #openstack-kolla07:57
*** pcaruana|elisa| has quit IRC07:59
lvdombrkrfolks who used cinder.volume.drivers.netapp.common.NetAppDriver wih kolla?08:03
*** pcaruana has joined #openstack-kolla08:05
*** shardy has joined #openstack-kolla08:08
*** shardy_ has joined #openstack-kolla08:08
*** shardy_ has quit IRC08:10
*** shardy_ has joined #openstack-kolla08:11
*** jmccarthy has joined #openstack-kolla08:21
*** serlex has joined #openstack-kolla08:43
*** mgoddard has joined #openstack-kolla08:50
*** dougsz has joined #openstack-kolla09:00
masuberuadrianreza, yes I also thought reconfigure would restart the containers but it is not happening09:05
masuberuor maybe I am still not doing thing right09:05
*** k_mouza has joined #openstack-kolla09:24
*** PagliaccisCloud has quit IRC09:34
*** PagliaccisCloud has joined #openstack-kolla09:34
*** chrizl has quit IRC09:37
masuberugood afternoon, I want to edit nova.conf on my compute nodes. I have created this file /etc/kolla/config/nova/nova.conf but reconfigure is not changing the compute nodes. Any idea?09:40
*** ducnv has quit IRC09:40
*** ducnv has joined #openstack-kolla09:44
*** yan0s has joined #openstack-kolla09:47
*** lvdombrkr has quit IRC09:50
*** serlex has quit IRC10:01
openstackgerritSurya Prakash (spsurya) proposed openstack/kolla-ansible master: [WIP] Fast Forward Upgrade spec  https://review.openstack.org/61450810:03
*** lvdombrkr has joined #openstack-kolla10:08
openstackgerritSurya Prakash (spsurya) proposed openstack/kolla-ansible master: [WIP] Fast Forward Upgrade spec  https://review.openstack.org/61450810:09
*** hamzaachi has quit IRC10:14
*** k_mouza has quit IRC10:16
*** ducnv has quit IRC10:17
*** k_mouza has joined #openstack-kolla10:18
*** k_mouza has quit IRC10:19
*** k_mouza has joined #openstack-kolla10:20
openstackgerritSurya Prakash (spsurya) proposed openstack/kolla-ansible master: [WIP] Fast Forward Upgrade spec  https://review.openstack.org/61450810:20
*** jaosorior has quit IRC10:23
*** dpascheka has joined #openstack-kolla10:26
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla-ansible master: Remove deprecated compute groups  https://review.openstack.org/61447510:38
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla-ansible master: Remove deprecated compute groups  https://review.openstack.org/61447510:40
*** k_mouza has quit IRC10:40
openstackgerritMerged openstack/kolla-ansible master: Add Zun scenario job for ubuntu  https://review.openstack.org/56524010:42
*** k_mouza has joined #openstack-kolla10:44
*** hamzaachi has joined #openstack-kolla11:00
openstackgerritSurya Prakash (spsurya) proposed openstack/kolla-ansible master: [WIP] Fast Forward Upgrade spec  https://review.openstack.org/61450811:04
*** pcaruana has quit IRC11:05
*** k_mouza has quit IRC11:07
*** k_mouza has joined #openstack-kolla11:26
*** zul has joined #openstack-kolla11:28
*** jaosorior has joined #openstack-kolla11:35
*** gkadam has quit IRC11:46
*** gkadam has joined #openstack-kolla11:50
*** yan0s has quit IRC11:51
*** pcaruana has joined #openstack-kolla11:52
*** hamzaachi has quit IRC11:54
*** hamzaachi has joined #openstack-kolla11:55
*** Pavo has joined #openstack-kolla11:55
*** yan0s has joined #openstack-kolla11:56
*** Pavo has quit IRC11:56
*** gkadam_ has joined #openstack-kolla12:04
*** gkadam has quit IRC12:07
*** pbourke has quit IRC12:09
*** pbourke has joined #openstack-kolla12:10
*** tolisbar has joined #openstack-kolla12:21
*** yan0s has quit IRC12:23
*** robbbe has joined #openstack-kolla12:26
robbbehi all - i've got a couple of basic questions. hopefully someone can help...12:27
robbbeBifrost - i assume it can be used to deploy the whole cloud from a control host? i'm not sure the documentaiton is correct though - does anyone have a dummies guide?12:27
robbbealso, how do you 'bootstrap' the deployment/control node given none of the others exist?12:29
tolisbarHey robbe. Not much experienced with openstack. Just joined the channel as well so think twice before following what I suggest. I am using MAAS on a vagrant vm from my laptop to deploy ubuntu on the baremetal cluster nodes, ansible to perform the basic host configuration and then ansible-kolla to spin up the cluster. I want to use bifrost as well to manage the rest of my infrastructure that is why I12:35
tolisbaruse MAAS to only deploy the initial openstack cluster nodes and then I destroy it12:35
robbbetolisbar> interesting, but i guess there should be no need for MAAS12:50
robbbethe other question i have is can you use kolla-ansible to ONLY deploy the control node12:51
robbbenot AIO, but just a single control node12:51
opMDrobbbe> yes, kolla-ansible can deploy the required nodes12:51
opMDyou can have an inventory file that just contains a control node12:52
*** zul has quit IRC12:52
robbbeopMD thanks, is that just a case of commenting out the rest?12:52
robbbeperfect, thanks12:52
robbbethat will certainly simplify getting a basic system up and running!12:52
opMDjust add the node into the [controller] section and it will sort out the rest12:52
openstackgerritMerged openstack/kolla master: Disable init lastlog and faillog database for created user  https://review.openstack.org/61379012:53
robbbewhat if that node is going to be deployed via Bifrost?12:53
opMDin the globals.yml file you uncomment the services that you want12:53
opMDnot sure about Bifrost12:53
opMDwe use Kolla-Ansible12:53
*** hamzaachi has quit IRC12:53
robbbehow do you get from bare metal?12:53
opMDWe use Cobbler to provision our bare metal hosts12:54
robbberight, ok. my understanding is that bifrost should be a direct replacement for that process12:54
opMDwould Bifrost not need Ironic running beforehand? I'm not sure how it works12:56
*** zul has joined #openstack-kolla12:56
*** gkadam_ has quit IRC12:57
egonzalezbifrost is an standalone ironic deployment12:57
opMDAh cool, will look into it12:57
*** yan0s has joined #openstack-kolla12:58
tolisbarHello from me as well :)12:59
tolisbarYesterday I just managed to successfully run through the multinode deployment guide for ansible-kolla 7.0.0 and openstack rocky. I use internal(10.0.4/24) and external(10.0.3/24) networking and my internal/external VIPs are 10.0.4.251 and 10.0.3.251 respectively. My globals are these (https://pastebin.com/HicQXYaC)13:00
egonzaleztolisbar will need a node deployed with x tool to deploy the rest of things13:00
tolisbarand for each openstack node I define the network_interface, neutron_external_interface, kolla_external_vip_interface variables because my interface names differ between h13:00
tolisbarardware nodes. kolla-ansible deploy finishes successfully but when I try to access http://10.0.4.251 (internal VIP) I get redirected to http://10.0.4.251/horizon/auth/login/?next=/ which is a 404 (outputing the openstack logo and the message "Sorry, the page you were looking for does not exist"). I tried to access the horizon service dire13:00
tolisbarctly through a node that rans the container and got the same result. I checked the log output of the nova container but didn't find any error, just the warning "AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 10.0.4.1. Set the 'ServerName' directive globally to suppress this message" which se13:00
tolisbarems ok since I haven't set up FQDNs(it seems optional according to the kolla docs). I entered the container, and checked horizon-access.log(https://pastebin.com/u9E8hLF0) and horizon.log(https://pastebin.com/AN4rM9N6). It seems to me like an apache route handling issue but thought to ask here first before start digging deeper. Any help would be much appreciated.13:00
tolisbarapologies for the long post.. had to precompose it13:00
egonzalezrobbbe i meant13:00
*** zul has quit IRC13:04
*** zul has joined #openstack-kolla13:05
egonzalezspsurya took a brief view of the FFU spec, will add some comments tomorrow (today is a bank day in spain)13:06
spsuryaegonzalez: np, sure whenever possible13:07
*** rgogunskiy has quit IRC13:07
spsuryai will also be on vacation on next week13:07
egonzalezspsurya just a main question, should we call ffu or offline, the behavior to upgrade a single release is the same as a ffu but with multiple13:07
spsuryaegonzalez:  actually we trying to achieve main goal of FFU13:08
robbbeanyone working on internal TLS support for Kolla?13:08
egonzalezis ok to me the spec be ffu as main goal, but tje upgrade phase is an offline migration13:08
egonzalezrobbbe not now afik13:08
egonzaleza few patches are to redirect all to public, but haven't seen much progress recently13:08
spsuryaegonzalez:  it would be offline but term can be FFU as stated in https://wiki.openstack.org/wiki/Fast_forward_upgrades#What_is_a_Fast_Forward_Upgrade.3F13:09
spsurya             A fast-forward upgrade is an offline upgrade which effectively runs the upgrade processes for all versions of openstack components from your originating version to your desired final version.13:09
egonzalezyep, is just a variable naming thing13:10
spsuryaso i think FFU is fine, also term is more popular and understood in OpenStack community13:10
egonzalezto make a clear definition of what the upgrade type does13:10
spsuryayeah. same is stated in spec as well as on OpenStack wiki page13:12
*** mchlumsky has joined #openstack-kolla13:12
spsuryaAlso FFU is a goal from community side as well as popular topic of discussion in various summits and PTG13:13
spsuryaso i think keeping name FFU and changes around offline upgrade should be fine13:13
egonzalezagree13:14
egonzalezwill revisit my PS to see how can improve them with mgoddard comments13:14
spsuryaegonzalez: thanks13:15
spsuryayes we can check for that13:15
spsuryaplease free to update and review https://review.openstack.org/#/c/614508/13:15
spsuryawhichever section you feels need improvement13:15
*** rgogunskiy has joined #openstack-kolla13:16
spsuryameanwhile i keep updating with more information and investigation13:16
egonzalezspsurya thanks for rebump the ffu topic, was focusing on some Opendaylight improvements and placement split recently13:18
spsuryaegonzalez: yeah, targeted for Stein13:19
spsuryain parallel we will also keep eye on Opendaylight improvements and placement split recently13:19
spsuryaas time permit13:19
*** k_mouza has quit IRC13:20
spsuryaegonzalez: FFU would be great work from Kolla side if its completed in Stein13:20
spsuryaegonzalez: thanks for the initial patch13:20
jrollrobbbe: an easier way to deploy only the control node is to pass `--limit control` to kolla-ansible13:21
robbbejroll - thanks13:22
*** Pavo has joined #openstack-kolla13:22
*** k_mouza has joined #openstack-kolla13:25
spsuryajroll: robbbe sup13:27
jrollhi13:27
spsuryayou guys planning to contribute to Kolla13:29
spsuryaany guy nic name akhila pinged me for Kolla contribution13:29
jrollspsurya: I'm using it and will contribute as needed, yes13:29
spsuryajroll: nice13:29
tolisbarIs there some other communication channel I should prefer instead of irc to get some help with the horizon issue I am facing ? I didn't see much activity on stack overflow or server-fault and couldn't find a related mailing list13:31
spsuryatolisbar: yes #openstack-horizon13:33
spsuryaalso on #openstack-dev13:33
tolisbarthank you13:34
robbbespsurya : yes13:35
spsuryarobbbe: nice13:36
robbbejust eval at the moment, but intend to standardise and sell as a private cloud solution13:36
opMDI don't know if this was seen earlier today, I may have posted it when it was a bit quiet here. We have deployed the core of Openstack using Kolla-Ansible and now are trying to add Ceilometer with Gnocchi. We've run into an issue13:36
opMDwhere the deployment of Ceilometer fails while bootstrapping. The ceilometer-upgrade command in the ceilometer-bootstrap container fails with a 500 error connecting the gnocchi api13:36
opMDThe error in the gnocchi-api logs:13:36
opMDmod_wsgi (pid=19): Target WSGI script '/usr/bin/gnocchi-api' cannot be loaded as Python module.13:37
opMDmod_wsgi (pid=19): Exception occurred processing WSGI script '/usr/bin/gnocchi-api'.13:37
opMD  Traceback (most recent call last):13:37
opMD    File "/usr/bin/gnocchi-api", line 20, in <module>13:37
opMD      from gnocchi.cli import api13:37
opMDImportError: No module named gnocchi.cli13:37
opMDHas anyone come across this before?13:37
spsuryarobbbe: good to hear that13:38
egonzalezopMD what release and images version?13:45
egonzalezi recall a fix was merged recently13:46
PavoAnyone know away to separate Kolla-ansible internal REST APIs and admin REST APIs?13:50
opMDegonzalez> It's Queens and using the binary docker containers available on the docker hub. The build was done yesterday13:51
opMDI'll get the build numbers shortly13:51
opMDgnocchi 7.0.113:57
opMDceilometer 10.0.113:57
openstackgerritCédric Jeanneret proposed openstack/kolla master: Do not load iscsi_tcp from within a container.  https://review.openstack.org/60545114:01
openstackgerritCédric Jeanneret proposed openstack/kolla master: Do not load ip_vs module from the container  https://review.openstack.org/60544814:02
openstackgerritCédric Jeanneret proposed openstack/kolla master: Do not load dm-multipath module from the container  https://review.openstack.org/60545314:02
openstackgerritHongbin Lu proposed openstack/kolla-ansible stable/rocky: Add Zun scenario job for ubuntu  https://review.openstack.org/61477414:03
*** spiette has quit IRC14:11
*** gkadam has joined #openstack-kolla14:13
*** Luzi has joined #openstack-kolla14:27
*** spiette has joined #openstack-kolla14:28
*** dciabrin has quit IRC14:30
*** spiette has quit IRC14:31
*** spiette has joined #openstack-kolla14:33
tolisbarI had a further look at the container configuration and it is indeed related with the way that requests gets passed from apache to the app server. It seems that the /horizon prefix is not needed and that all resources are available at /14:38
tolisbarI was using the ubuntu images and now I am trying the same configuration with the centos one to see if I hit the same issue14:40
tolisbarThis is kolla related; right ?14:41
tolisbarAre some images considered more stable/well tested than others ?14:41
*** Luzi has quit IRC14:44
*** rgogunskiy has quit IRC15:05
*** gkadam has quit IRC15:09
*** chrizl has joined #openstack-kolla15:09
*** k_mouza has quit IRC15:10
*** kukacz has quit IRC15:12
*** itlinux has quit IRC15:13
*** kukacz has joined #openstack-kolla15:19
*** JamesBenson has joined #openstack-kolla15:21
*** JamesBenson has quit IRC15:22
*** JamesBenson has joined #openstack-kolla15:22
*** k_mouza has joined #openstack-kolla15:22
lvdombrkrfolks to use floating ips there is no any special customizations in globals.yml? (setup with 3 controllers)15:27
*** k_mouza has quit IRC15:27
tolisbarlvdombrkr: check kolla_internal_vip_address and kolla_external_vip_address15:33
tolisbarit's covered in the documentation15:33
lvdombrkrtolisbar: sure that vip addreses are somehow related with flaoting ips?15:37
lvdombrkri have issue, that i cant ping my floatings ips and other ports on external network15:37
lvdombrkrseems problems with mappings15:38
lvdombrkretc15:38
*** hamzaachi has joined #openstack-kolla15:56
*** k_mouza has joined #openstack-kolla16:10
*** itlinux has joined #openstack-kolla16:14
tolisbarThe issue that I was facing was indeed only affecting the ubuntu images. It seems to work fine with the centos images16:20
*** k_mouza has quit IRC16:24
*** sshnaidm|ruck is now known as sshnaidm|afk16:48
*** k_mouza has joined #openstack-kolla16:53
*** k_mouza has quit IRC16:59
*** mgoddard has quit IRC17:02
*** hamzaachi has quit IRC17:03
*** jmccarthy has left #openstack-kolla17:15
*** robbbe has quit IRC17:15
*** lvdombrkr has quit IRC17:15
*** spiette has quit IRC17:18
*** k_mouza has joined #openstack-kolla17:20
*** hamzaachi has joined #openstack-kolla17:20
*** chrizl has quit IRC17:22
*** hadrianweb has joined #openstack-kolla17:25
*** spiette has joined #openstack-kolla17:26
*** chrizl has joined #openstack-kolla17:29
*** chrizl has quit IRC17:34
*** tolisbar has quit IRC17:37
*** k_mouza_ has joined #openstack-kolla17:40
jrollso I'm looking at configuring gpu passthrough in nova. I would assume node_custom_config is the best way to do this. however, I only want to configure it for some hosts, not all. is there a good way to handle this without changing kolla-ansible source, or should I propose a passthrough feature type thing?17:41
*** k_mouza has quit IRC17:43
*** k_mouza_ has quit IRC17:45
*** chrizl has joined #openstack-kolla17:52
*** sshnaidm|afk is now known as sshnaidm|off18:00
*** chrizl has quit IRC18:01
*** chrizl has joined #openstack-kolla18:02
eanderssonAnyone using Kolla and Magnum by any chance?18:04
*** hamzaachi_ has joined #openstack-kolla18:05
*** chrizl has quit IRC18:06
*** hamzaachi has quit IRC18:08
*** dougsz has quit IRC18:09
*** chrizl has joined #openstack-kolla18:11
*** cah_link has quit IRC18:12
*** chrizl has quit IRC18:20
*** chrizl has joined #openstack-kolla18:29
*** mattgo has quit IRC18:32
*** chrizl has quit IRC18:34
*** hadrianweb has quit IRC18:34
*** chrizl has joined #openstack-kolla18:39
*** chrizl has quit IRC18:43
*** chrizl has joined #openstack-kolla18:44
*** chrizl has quit IRC18:48
*** yan0s has quit IRC18:53
*** spiette has quit IRC18:53
*** chrizl has joined #openstack-kolla18:53
*** lvdombrkr has joined #openstack-kolla18:58
*** itlinux has quit IRC19:01
lvdombrkrmasuberu: put files just under /etc/kolla/config19:01
lvdombrkrwihout nova folder19:02
lvdombrkrand check file permissions19:02
*** chrizl has quit IRC19:02
*** chrizl has joined #openstack-kolla19:02
*** pcaruana has quit IRC19:05
*** chrizl has quit IRC19:06
*** chrizl has joined #openstack-kolla19:13
*** spiette has joined #openstack-kolla19:17
*** chrizl has quit IRC19:18
*** chrizl has joined #openstack-kolla19:23
*** hamzaachi_ has quit IRC19:26
*** hamzaachi has joined #openstack-kolla19:28
*** chrizl has quit IRC19:32
*** chrizl has joined #openstack-kolla19:32
*** itlinux has joined #openstack-kolla19:39
*** chrizl has quit IRC19:41
*** chrizl has joined #openstack-kolla19:41
*** chrizl has quit IRC19:46
lvdombrkrfolks what are reasons that external network ports not pingable19:47
*** chrizl has joined #openstack-kolla19:51
gary_perkinslvdombrkr: I've had this issue too. How I've fixed it, is to move the external IP from the physical interface and assign it to br-ex. Not sure if this is the best way of solving the issue but it's worked fine for me :)19:51
*** chrizl has quit IRC19:55
*** chrizl has joined #openstack-kolla19:57
lvdombrkrgary_perkins: what you mean by external IP? external_neutron interface should be without any ip19:58
lvdombrkrthis interface are mapped to br-ex19:59
lvdombrkrbut there is no ip on it19:59
lvdombrkri mean shouldnt be19:59
*** chrizl has quit IRC20:01
*** chrizl has joined #openstack-kolla20:02
*** hamzaachi has quit IRC20:04
*** chrizl has quit IRC20:12
*** chrizl has joined #openstack-kolla20:13
*** itlinux has quit IRC20:14
*** itlinux has joined #openstack-kolla20:14
*** Pavo has quit IRC20:20
*** chrizl has quit IRC20:23
*** chrizl has joined #openstack-kolla20:28
*** negronjl has quit IRC20:28
*** negronjl has joined #openstack-kolla20:32
*** chrizl has quit IRC20:33
*** chrizl has joined #openstack-kolla20:52
*** chrizl has quit IRC20:56
*** jmcevoy has joined #openstack-kolla20:57
*** jmcevoy has quit IRC20:58
*** jmcevoy has joined #openstack-kolla21:00
*** chrizl has joined #openstack-kolla21:02
*** chrizl has quit IRC21:12
*** jmcevoy has quit IRC21:19
emccormickHey all. Doing my Rocky upgrade, and kolla-ansible wants PyYAML 3.12 which means I"m likely going to need to upgrade Ansible. I feel like I already downgraded Ansible to avoid some Kolla issue before. Is there a new stated good version to use for Rocky?21:19
emccormickI'm using 2.4.4 presently21:19
*** mattgo has joined #openstack-kolla21:19
*** chrizl has joined #openstack-kolla21:23
*** chrizl has quit IRC21:28
*** chrizl has joined #openstack-kolla21:29
*** chrizl has quit IRC21:33
*** chrizl has joined #openstack-kolla21:42
*** chrizl has quit IRC21:47
*** chrizl has joined #openstack-kolla21:52
*** lvdombrkr has quit IRC21:53
*** chrizl has quit IRC21:56
*** JamesBenson has quit IRC22:01
*** chrizl has joined #openstack-kolla22:15
*** threestrands has joined #openstack-kolla22:17
*** chrizl has quit IRC22:19
*** chrizl has joined #openstack-kolla22:20
*** chrizl has quit IRC22:25
*** chrizl has joined #openstack-kolla22:26
*** chrizl has quit IRC22:31
*** chrizl has joined #openstack-kolla22:41
*** chrizl has quit IRC22:45
*** chrizl has joined #openstack-kolla22:45
*** chrizl has quit IRC22:50
*** chrizl has joined #openstack-kolla22:52
*** chrizl has quit IRC22:56
*** chrizl has joined #openstack-kolla22:57
*** unicell has joined #openstack-kolla23:01
*** chrizl has quit IRC23:02
*** chrizl has joined #openstack-kolla23:03
*** JamesBen_ has joined #openstack-kolla23:05
*** chrizl has quit IRC23:08
*** JamesBen_ has quit IRC23:10
*** dpascheka has quit IRC23:13
*** owalsh_ has joined #openstack-kolla23:14
*** owalsh has quit IRC23:15
*** chrizl has joined #openstack-kolla23:31
*** chrizl has quit IRC23:40
*** chrizl has joined #openstack-kolla23:55
*** chrizl has quit IRC23:59

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!