Thursday, 2018-01-04

kfox1111embargo lifted.... https://spectreattack.com/ :/00:01
*** daidv has quit IRC00:24
*** goldyfruit has joined #openstack-kolla00:26
harlowjawe all screwed00:32
harlowjalol00:32
*** ipsecguy has quit IRC00:41
*** duonghq has joined #openstack-kolla00:48
openstackgerritzhongshengping proposed openstack/kolla-ansible stable/pike: Prevent cinder conf from copy nfs_shares to unrelated nodes  https://review.openstack.org/53104300:49
openstackgerritzhongshengping proposed openstack/kolla-ansible stable/ocata: Prevent cinder conf from copy nfs_shares to unrelated nodes  https://review.openstack.org/53104400:50
*** goldyfruit has quit IRC00:50
kfox1111heh.00:55
*** kevinz has quit IRC01:31
openstackgerritXinliang Liu proposed openstack/kolla master: Fix MariaDB bootstrap for 10.1 version  https://review.openstack.org/52919901:35
openstackgerritzhongshengping proposed openstack/kolla-ansible master: Kuryr not starting  https://review.openstack.org/53105001:35
*** threestrands has joined #openstack-kolla01:55
*** zhurong has joined #openstack-kolla02:13
*** Daviey has quit IRC02:14
*** jascott1 has joined #openstack-kolla02:22
jascott1"no agent of type Open vSwitch agent registered on host blah-node-2"02:23
inc0ovs - eternal nemesis of jascott102:23
inc0Jeffrey4l: thanks for taking care about todays meeting, I fell sick over night and just slept through02:24
jascott1inc0 which service is it complaining about?02:24
inc0well, you'll need to check logs of neutron-openvswitch-agent02:25
jascott1inc0 not seeing anything in there. seems like Im missing a service on compute nodes02:28
inc0that'd be service02:28
jascott1inc0 is it 'neutron-openvswitch-agent-network-' or 'openvswitch-vswitchd-network' ?02:30
*** ljjjustin has joined #openstack-kolla02:31
inc0vswitchd - actual ovs process, neutron agent is what's missing02:32
inc0although agent might be missing because it broke because vswitchd is borked02:32
jascott1ok this guy 'neutron-openvswitch-agent-network' is not running on compute node02:33
inc0it should02:33
inc0so should vswitchd02:34
jascott1ok thanks02:35
jascott1inc0 but not ovsdb right?02:35
inc0ovsdb to02:36
inc0too02:36
jascott1oh i remember now (vacation is a mofo) I had labeled everything kolla_node and changed that selector to that. mustve lost that somewhere02:39
*** daidv has joined #openstack-kolla02:43
openstackgerritJustin Scott proposed openstack/kolla-kubernetes master: WIP deploy with ansible inside orchestration container  https://review.openstack.org/52084702:44
openstackgerritDai Dang Van proposed openstack/kolla-ansible master: Support policy.yaml file for Aodh  https://review.openstack.org/51456502:49
jascott1oh i had it in arboreal and it never made it over :/02:51
*** caowei has joined #openstack-kolla02:52
openstackgerritJustin Scott proposed openstack/kolla-kubernetes master: WIP deploy with ansible inside orchestration container  https://review.openstack.org/52084702:54
*** masber has joined #openstack-kolla02:55
masbergood afternoon, is there a way to tell openstack-kolla to deploy vlan network instead of vxlan?02:55
jascott1masber you mean kolla-ansible?02:56
masberkolla-ansible yes sorry02:56
jascott1np just making sure :)02:56
jascott1so many projects these days02:57
masberthe reason I need vlan network is because I am looking forward using SR-IOV02:57
masberwhich does not work with vxlan02:57
jascott1my guess is somewhere in /etc/kolla/globals.yml02:58
inc0masber: I think we have guide for that03:00
inc0let me check03:00
inc0jascott1: a bit more to that03:00
masberthank you03:01
inc0https://docs.openstack.org/kolla-ansible/latest/reference/networking-guide.html03:02
inc0you might need also write vlan ranges to ml2.conf03:03
inc0some notes here too https://docs.openstack.org/kolla-ansible/latest/reference/ironic-guide.html03:05
inc0hmm...I'll need to double check all that03:05
inc0masber: let me know if you run into problems and I'll write proper docs for it afterwards03:06
masberinc0, so I understand that the only thing I need to do is to add this neutron_tenant_network_types: "vxlan,vlan,flat" to the gloobals.yml file?03:07
masberok, let me try03:08
masberinc0, is ironic still in techpreview?03:08
masber*tech-preview03:08
inc0I think it's fairly stable now03:09
inc0so about just globals I can't see it in docs but you might need to write template override for vlan ranges and whatnot03:09
inc0config override*03:09
masberok03:11
*** unicell has quit IRC03:14
*** coolsvap has joined #openstack-kolla03:26
openstackgerritChason Chan proposed openstack/kolla master: Migrate neutron-vpnaas-agent to neutron-l3-agent  https://review.openstack.org/53020803:30
*** strgout has joined #openstack-kolla03:35
*** unicell has joined #openstack-kolla03:40
strgoutok so i started asking about this last night and there was no beer involved at all.03:46
strgouti'm not getting how you populate the local registery if i'm not bulding the images myself.03:46
strgoutshouldn't kolla-ansible pull -i inventory populate the local docker reg?03:48
*** janonymous has joined #openstack-kolla03:51
adrianrezastrgout, if you want skip building your own images you can download old images from https://tarballs.openstack.org/kolla/images/ and then deploy your local insecure registry04:09
adrianrezastrgout, this is the example04:11
adrianrezahttps://www.irccloud.com/pastebin/cy0bZrrM/04:11
adrianrezastrgout, and then in your /etc/kolla/globals.yml add docker_registry: "10.10.10.1:4000", docker_namespace: "lokolla" in docker section04:13
*** ansmith has quit IRC04:18
strgouthey sorry didn't see this. So do all the docs assume your going to build your own images in all cases?04:20
*** caowei has quit IRC04:28
*** strgout has quit IRC04:57
*** caowei has joined #openstack-kolla05:14
*** janki has joined #openstack-kolla05:43
openstackgerritQi Peng proposed openstack/kolla-ansible master: kolla-ansible bootstrap-servers failed because of docker restart failed  https://review.openstack.org/53107705:50
*** markmcclain has quit IRC05:51
*** markmcclain has joined #openstack-kolla05:54
openstackgerritJustin Scott proposed openstack/kolla-kubernetes master: WIP deploy with ansible inside orchestration container  https://review.openstack.org/52084706:26
*** namnh has joined #openstack-kolla06:36
*** zhurong has quit IRC06:47
*** zhurong has joined #openstack-kolla06:52
*** masuberu has joined #openstack-kolla06:59
xinliangHi , CI seems broken.07:00
xinliangmany jobs failed looks the same:  http://logs.openstack.org/95/529795/1/check/kolla-ansible-centos-source/e358e45/job-output.txt.gz07:00
xinliangcp: cannot stat ‘/var/lib/docker/volumes/kolla_logs/_data/*’: No such file or directory07:01
*** jaosorior has quit IRC07:01
*** egonzalez has joined #openstack-kolla07:02
openstackgerritChason Chan proposed openstack/kolla master: Migrate neutron-vpnaas-agent to neutron-l3-agent  https://review.openstack.org/53020807:05
*** jaosorior has joined #openstack-kolla07:11
*** jaosorior has quit IRC07:13
*** jaosorior has joined #openstack-kolla07:14
*** jaosorior has quit IRC07:14
*** jaosorior has joined #openstack-kolla07:14
*** kristaps_ has quit IRC07:15
namnhhi everyone, i am using docker version 17, and i created a local registry like this command [1]. But docker on target node cannot push/pull image from the local registry, it allways raise an error like this [2]. is there anyone encounter this error.07:19
namnh[1] http://paste.openstack.org/show/637583/07:19
namnh[2] http://paste.openstack.org/show/637585/07:19
namnhi am trying to deploy kolla on multi nodes.07:20
openstackgerritMerged openstack/kolla-ansible master: Update READEME  https://review.openstack.org/53042407:20
*** sbezverk has quit IRC07:21
*** threestrands has quit IRC07:25
*** jrist has quit IRC07:29
*** pcaruana has joined #openstack-kolla07:32
xinliangJerrey4l: CI seems broken07:33
xinliangmany jobs failed looks the same:  http://logs.openstack.org/95/529795/1/check/kolla-ansible-centos-source/e358e45/job-output.txt.gz07:33
xinliang cp: cannot stat ‘/var/lib/docker/volumes/kolla_logs/_data/*’: No such file or directory07:33
*** cah_link has joined #openstack-kolla07:34
*** unicell has quit IRC07:35
*** cah_link has quit IRC07:37
*** cah_link has joined #openstack-kolla07:37
*** tovin07_ has joined #openstack-kolla07:53
egonzaleznamnh, need to configure insecure registry to point your registry07:54
egonzaleznamnh, the port exposed by docker is 443 -p 443:44307:56
egonzaleznot 5000007:56
openstackgerritJustin Scott proposed openstack/kolla-kubernetes master: WIP deploy with ansible inside orchestration container  https://review.openstack.org/52084707:57
*** ljjjustin has quit IRC08:02
namnhegonzalez: yead, i will try it.08:06
openstackgerritzhouya proposed openstack/kolla-ansible master: Support assigning HA traffic to dedicated interface  https://review.openstack.org/48150308:09
*** shardy has joined #openstack-kolla08:16
daidvegonzalez, Hi08:17
*** kiennt26 has joined #openstack-kolla08:20
egonzalezdaidv, hi08:20
daidvegonzalez, thank for your review, I want to dicuss with u a little bit more.08:23
egonzalezdaidv, what review?08:24
daidvegonzalez, #link https://review.openstack.org/#/c/514565/08:24
hrwrwellum: one step at time. I managed to understand how to build (kolla) so time for deploy (k-a).08:25
hrwmorning08:25
egonzalezdaidv, if i put an empty /etc/kolla/config/aodh/somethingwrong.json, it will copy to aodh hosts breaking the service08:26
daidv1. I'm using first_found to only get yaml or json policy file because we can not merged them08:26
daidvegonzalez, no, we just find policy.json or policy.yaml08:26
egonzalezright, missed that part08:26
daidvFor your question about aodh_policy.results, when we don't have policy.json and policy.yaml, aodh_policy.results = []08:27
daidvSo, I think we can use it to check if users are customizing policies.08:28
egonzalezdaidv, how about aodh_policy.results.0.stat.exists?08:30
daidvegonzalez, It will raise an error in case user didn't put any policy file08:31
egonzalezshouldnt, because policies are optionals08:31
daidvbecause as I said above, aodh.results will be empty list, we can call aodh_policy.results.0.stat.exists08:31
egonzalezgotcha08:31
daidvOk, the last point is about optional": true08:32
daidvIn old flow, we are using "optional": true to pass the case that user didn't have policy.json08:33
*** b_bezak has joined #openstack-kolla08:33
daidvbut now, we need to know aodh_policy_file (policy.json or policy.yaml) to copy from source to dest08:33
*** b_bezak has quit IRC08:34
daidvSo I think we shouldn't use optional: true any more, and just check if aodh_policy_file is defined08:34
daidvegonzalez, is it Ok?08:35
egonzalezok, then remove optional to ensure the file is there to copy. We do not have jinja trimmers in other json files, please remove them, smth like http://paste.openstack.org/show/637657/08:36
egonzalezother lgtm08:36
daidvegonzalez, ah, I have test with that but using an "{%-" with an "-" is better for us08:38
daidvit with clear white spaces for us08:38
daidvs/with/will08:38
egonzalezyeah, but we do not have it in other json files, just for consistency with other roles08:39
openstackgerritChason Chan proposed openstack/kolla master: Migrate neutron-vpnaas-agent to neutron-l3-agent  https://review.openstack.org/53020808:39
daidvegonzalez, I think we can do the same thing with other roles.08:40
daidvwhich are supporting policy files.08:40
daidvand we only it for check if policy_file is defined in json files.08:41
*** cduchesne has quit IRC08:43
daidvegonzalez, Ah other thing, I just see your comment about order of "Check if policies shall be overwritten"08:43
egonzalezfor me is harder to review if there is a missing minus in the middle of a trimmer and know is going to render correctly the json (only my preferences, not others, not a hard requirement)08:43
daidvI need to move it up, because we need to know which policy format are using before we render config file with [oslo_policy] policy_file = which_one08:45
openstackgerritMerged openstack/kolla-ansible stable/ocata: Prevent cinder conf from copy nfs_shares to unrelated nodes  https://review.openstack.org/53104408:46
egonzalezahh, got it, ok then08:46
*** cduchesne has joined #openstack-kolla08:48
openstackgerritMerged openstack/kolla-ansible stable/pike: Prevent cinder conf from copy nfs_shares to unrelated nodes  https://review.openstack.org/53104308:49
daidvegonzalez, so can I make your recommendation in a follow up patch? I will use that patch as an example to complete my blue print ASAP with other similar path for other roles?08:49
egonzalezdaidv, i prefer in this one as is the first of a series, then replicate the final patch to all roles, not having to look into 2 different changes08:50
*** b_bezak has joined #openstack-kolla08:52
*** b_bezak has quit IRC08:52
*** b_bezak has joined #openstack-kolla08:53
*** b_bezak has quit IRC08:54
*** b_bezak has joined #openstack-kolla08:55
daidvegonzalez, Ah, I tested your suggestion about trimmer, but if with "{%-" we will have better output format.08:55
daidv#link http://paste.openstack.org/show/637657/08:55
*** b_bezak has quit IRC08:59
*** b_bezak has joined #openstack-kolla09:03
openstackgerritMartin André proposed openstack/kolla-ansible master: Use local cirros image if available  https://review.openstack.org/49844909:06
daidvegonzalez, Oops, my bad, you're right, it is not really need. Thank for your support, I will update my patch now.09:13
*** jrist has joined #openstack-kolla09:13
openstackgerritDai Dang Van proposed openstack/kolla-ansible master: Support policy.yaml file for Aodh  https://review.openstack.org/51456509:16
*** ktibi has joined #openstack-kolla09:19
openstackgerritTudosoiu Marian proposed openstack/kolla-ansible master: Related-Bug: 1682153  https://review.openstack.org/53111509:22
openstackbug 1682153 in kolla-ansible "mariadb_recovery is prone to data loss" [Critical,Confirmed] https://launchpad.net/bugs/1682153 - Assigned to Tudosoiu Marian (mtudosoiu)09:22
hrwcan someone take a look at https://review.openstack.org/#/c/530897/ one? it checks is installed python-openstackclient is at least 3.1209:22
openstackgerritMerged openstack/kolla-ansible master: Add tempurl to swift pipeline  https://review.openstack.org/52767709:23
openstackgerritMerged openstack/kolla-ansible master: Fix failure handling in prechecks  https://review.openstack.org/52709509:25
*** tovin07_ has quit IRC09:25
openstackgerritTaeha Kim proposed openstack/kolla-ansible master: Use local cirros image if available  https://review.openstack.org/49844909:26
*** mgoddard has joined #openstack-kolla09:26
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible stable/pike: Remove the unnecessary register.yml from upgrade.yml for Nova  https://review.openstack.org/52879909:27
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible stable/ocata: Remove extra configuration item in solum.conf.j2  https://review.openstack.org/47264709:28
openstackgerritMerged openstack/kolla-ansible master: fix the tempest failure for external ceph  https://review.openstack.org/53089209:39
*** kiennt26 has quit IRC09:49
*** pbourke has quit IRC10:10
*** namnh has quit IRC10:27
openstackgerritTudosoiu Marian proposed openstack/kolla-ansible master: Related-Bug: 1682153  https://review.openstack.org/53112210:35
openstackbug 1682153 in kolla-ansible "mariadb_recovery is prone to data loss" [Critical,Fix committed] https://launchpad.net/bugs/1682153 - Assigned to Tudosoiu Marian (mtudosoiu)10:35
*** duonghq has quit IRC10:37
egonzalezdaidv, missed one json file, otherwise will +2ed10:44
*** markmcclain has quit IRC10:51
*** markmcclain has joined #openstack-kolla10:59
*** robbbe has joined #openstack-kolla11:03
openstackgerritMichal Rostecki proposed openstack/kolla-ansible master: dev mode: Add support for magnum  https://review.openstack.org/52932311:05
openstackgerritMichal Rostecki proposed openstack/kolla-ansible master: dev mode: Add support for keystone  https://review.openstack.org/52932411:05
openstackgerritMichal Rostecki proposed openstack/kolla-ansible master: [WIP] dev mode: Add support for neutron  https://review.openstack.org/52646611:05
*** nhlfr has joined #openstack-kolla11:05
*** jstramka89 has joined #openstack-kolla11:14
jstramka89hello folks11:15
*** semoac has quit IRC11:15
jstramka89trying to deploy ocata tag 4.0.0 but get this error : http://paste.openstack.org/raw/637818/11:17
jstramka89any ideas?11:17
jstramka89seems problem with docker version11:17
egonzalezjstramka89, what python docker version have installed, pip freeze |  grep -i docker11:24
jstramka89egonzalez: docker-py==1.10.611:24
-openstackstatus- NOTICE: zuul seems to have gotten stuck and will probably need a restart, please be patient11:27
*** openstackstatus has quit IRC11:28
*** openstack has quit IRC11:28
*** openstack has joined #openstack-kolla13:10
*** ChanServ sets mode: +o openstack13:10
*** janonymous has quit IRC13:11
cah_linkok. i have found it in /var/lib/kolla/venv/bin/glance-wsgi-api13:11
*** b_bezak has joined #openstack-kolla13:13
*** n0isyn0ise has joined #openstack-kolla13:33
*** pengdake has joined #openstack-kolla13:53
*** nhlfr has quit IRC13:57
*** mrostecki has joined #openstack-kolla13:59
*** tvignaud has quit IRC14:01
kfox1111morning.14:03
*** diranerpi has quit IRC14:12
n0isyn0isehi and happy new year everyone14:17
ktibiCan we configure AvailabilityZone for a compute with kolla ?14:18
n0isyn0iseI'm experiencing some trouble trying to deploy kolla-ansible 6.0.0.0b2, neutron_l3_agent is restarting in loop, and neutron-server.log complains about privsep helper command14:18
n0isyn0isedid anyone else experience this trouble ?14:18
kolla-slack1<aslancimbom100> n0isyn0ise please paste the exact log entries for someone to have a good idea of the problem14:20
n0isyn0isethere it is : https://pastebin.com/eRVui80B14:24
*** vincent_vdk has left #openstack-kolla14:35
*** goldyfruit has joined #openstack-kolla14:36
*** gema has quit IRC14:38
*** pmisiak has joined #openstack-kolla14:42
pmisiakhi guys, i'm thinking about migration from Mitaka to Pike14:43
pmisiakwhat is a suggested path?14:43
pmisiakis it any doc describing openstack release update?14:43
pmisiakcan i jump directly from mitaka to pike?14:44
-openstackstatus- NOTICE: zuul has been restarted, all queues have been reset. please recheck your patches when appropriate14:47
*** goldyfruit has quit IRC14:47
egonzalezktibi, yep, you can do it with nova commands, there is not any limitation, maybe need to add nova filters to the scheduler if they arent in the nova defaults14:58
egonzalezpmisiak, only can jump from release to release, cannot do multiple version jump15:03
*** masuberu has quit IRC15:04
openstackgerritJuan Badia Payno proposed openstack/kolla master: Fluentd plugins rpm installation on CentOS  https://review.openstack.org/52980615:05
*** goldyfruit has joined #openstack-kolla15:06
pmisiakegonzalez: thanks, what is the workflow? I build containers for next release and do kolla upgrade ?15:10
pmisiakand which kolla-ansible version I should use? I suppose for the next release?15:10
pmisiakso I take kolla-ansible and kolla for neuton, build containers and run kolla upgrade?15:11
egonzalezn0isyn0ise, logs from l3 agent?15:11
egonzalezpmisiak, update kolla and kolla-ansible to next release, build next release containers, pull on the hosts, make appropiate changes (read release notes), db backups and stuff like that, kolla-ansible upgrade, test, repeat again with next release15:13
*** jbrooks has quit IRC15:13
*** jbrooks has joined #openstack-kolla15:15
egonzalezn0isyn0ise, i dont see any error in n-server or n-l3-agent, what versions you using, distro, install_type?15:15
pmisiakegonzalez: great, which release notes I should read? OpenStack release notes? or Kolla release notes? or both?15:15
egonzalezpmisiak, i'd do both since we only notify our changes, not other projects changes (ie, neutron changed some config)15:17
pmisiakegonzalez: I suppose that you took account of config changes developing kolla for a particular openstack release15:21
egonzalezpmisiak, yep, but we do not control custom configs or overrides by users15:21
pmisiakegonzalez: yes, sure :)15:21
pmisiakegonzalez: perfectly fine15:22
n0isyn0iseegonzalez: i finally succeed by re-deploying and didn't meet the issue anew, so sorry for wrong alert15:24
pmisiakegonzalez: If i want do multiple upgrades during one maintenance windows can I just do intermediate upgrades on controllers? And on computes only the last one?15:42
openstackgerritDai Dang Van proposed openstack/kolla-ansible master: Support policy.yaml file for Aodh  https://review.openstack.org/51456515:45
*** pengdake has quit IRC15:53
*** jascott1 has quit IRC16:02
*** egonzalez has quit IRC16:07
*** pmisiak has quit IRC16:14
*** b_bezak has quit IRC16:19
*** cah_link has quit IRC16:20
*** mgoddard has quit IRC16:21
*** snuffkin has quit IRC16:22
*** b_bezak has joined #openstack-kolla16:24
*** b_bezak has quit IRC16:25
*** b_bezak has joined #openstack-kolla16:25
*** b_bezak has quit IRC16:30
ktibiAnyone have already test kolla with 3 nodes controllers ? because when I try to shutdown one, the VIP is on the remaining two.16:31
*** zshi has quit IRC16:38
*** ChanServ sets mode: -r 16:49
*** mcnanci has joined #openstack-kolla16:49
n0isyn0isektibi: unless I misunderstood, the VIP is used for that, HA cluster16:51
*** pcaruana has quit IRC16:52
*** kristaps has joined #openstack-kolla16:53
hrwhttps://marcin.juszkiewicz.com.pl/2018/01/04/today-i-was-fighting-with-nova-no-idea-who-won/16:54
*** jstramka89 has quit IRC16:54
*** wojdec has joined #openstack-kolla16:57
*** wojdec has quit IRC17:01
*** wojdec has joined #openstack-kolla17:02
inc0good mornign17:07
hrwinc0: read ^^ in free time17:09
inc0hahah17:09
rwellumGood read hrw17:12
hrwthx17:12
kfox1111morning.17:13
inc0hrw: that reminds me my presentation from vancouver summit - deep dive into live migration17:15
inc0this cpu features thingy is painful17:15
hrwinc0: link to video?17:16
inc0https://www.openstack.org/videos/vancouver-2015/dive-into-vm-live-migration17:16
inc0basically unless you have exactly homogenous env (hardware wise) and not have access to host-model or selecting cpu features from libvirt, you're screwed17:17
*** wojdec1 has joined #openstack-kolla17:21
hrwinc0: o! I see dulek as cospeaker ;D17:22
inc0yup17:22
inc0you work together now right?17:22
hrwsame company17:22
hrwnever met17:22
inc0cool guy, you should meet, you're from around Gdansk as well right?17:23
hrwSzczecin17:23
*** wojdec has quit IRC17:23
hrw~5h by car17:23
inc0ah, well, ok, far away;)17:23
* hrw off17:23
inc0good night17:23
hrwNova won.17:23
inc0haha17:24
inc0or lost17:24
inc0we don't know17:24
inc0what we know is that you lost;)17:24
inc0there will be other battles in this endless war, fear not17:24
*** mdorman has joined #openstack-kolla17:26
*** ntpttr_laptop has joined #openstack-kolla17:29
*** wojdec has joined #openstack-kolla17:33
*** wojdec1 has quit IRC17:35
*** mgoddard has joined #openstack-kolla17:40
*** ntpttr_laptop has quit IRC17:49
*** ntpttr_laptop has joined #openstack-kolla17:52
*** ntpttr_laptop has quit IRC17:53
*** david-lyle has quit IRC18:00
*** david-lyle has joined #openstack-kolla18:01
*** jascott1 has joined #openstack-kolla18:13
*** gkadam has joined #openstack-kolla18:23
*** shardy has quit IRC18:25
*** dardelean has joined #openstack-kolla18:35
*** numans_afk is now known as numans18:36
kfox1111ok... got fluent-bit to forward to elasticsearch managed by elasticsearch-operator. :)18:39
*** dardelean has quit IRC18:40
*** mchlumsky has quit IRC18:40
*** DosIK has quit IRC18:42
*** mchlumsky has joined #openstack-kolla18:46
*** n0cat has quit IRC18:49
*** robbbe has quit IRC18:52
*** mchlumsky has quit IRC18:57
jascott1excellent!18:59
*** dardelean has joined #openstack-kolla19:01
*** dardelean has quit IRC19:02
*** dardelean has joined #openstack-kolla19:03
*** mchlumsky has joined #openstack-kolla19:04
*** wojdec1 has joined #openstack-kolla19:05
*** wojdec has quit IRC19:06
*** mchlumsky_ has joined #openstack-kolla19:07
*** dardelean has quit IRC19:07
*** wojdec has joined #openstack-kolla19:09
*** mchlumsky has quit IRC19:09
*** wojdec1 has quit IRC19:10
*** dardelean has joined #openstack-kolla19:11
rwellumSo you'd helm install two new containers kfox1111  - FB and ES?19:11
*** dardelean has quit IRC19:11
*** cduchesne has quit IRC19:11
*** dardelean has joined #openstack-kolla19:12
rwellumkfox1111: be cool if you end up with a doc on how you created a new operator...19:12
rwellumThen jascott1 can use it to create a deploy operator :)19:12
*** cduchesne has joined #openstack-kolla19:14
*** dardelean has quit IRC19:16
*** jascott1 has quit IRC19:26
openstackgerritChristopher Nipper proposed openstack/kolla-ansible master: Add support for Neutron SRIOV agent container  https://review.openstack.org/48761019:26
openstackgerritChristopher Nipper proposed openstack/kolla-ansible master: Add details about SRIOV enablement to the networking guide  https://review.openstack.org/49811219:26
*** jascott1 has joined #openstack-kolla19:26
*** jascott1 has quit IRC19:28
*** jascott1 has joined #openstack-kolla19:29
*** jascott1 has quit IRC19:30
*** mdorman_ has joined #openstack-kolla19:30
*** mdorman has quit IRC19:31
*** mdorman_ is now known as mdorman19:31
*** jascott1 has joined #openstack-kolla19:33
*** scheuk has joined #openstack-kolla19:34
*** dardelean has joined #openstack-kolla19:36
*** dardelean has quit IRC19:37
*** dardelean has joined #openstack-kolla19:38
*** unicell has joined #openstack-kolla19:39
*** dardelean has quit IRC19:42
kfox1111rwellum: there isn't too much to creating an operator.19:43
kfox11111. you have some code that runs in a container.19:43
kfox11112. you create a crd definition.19:43
kfox11113. you write some code that watches for your crd's and do something when one gets created/changed.19:43
*** mgoddard has quit IRC19:45
kfox1111#2 looks something like this: https://github.com/kfox1111/charts/blob/kube-dhcp/incubator/kube-dhcp/templates/kubedhcp-crd.yaml19:45
openstackgerritChristopher Nipper proposed openstack/kolla-ansible master: Add details about SRIOV enablement to the networking guide  https://review.openstack.org/49811219:48
*** gkadam has quit IRC19:49
*** jascott1 has quit IRC20:02
*** jascott1 has joined #openstack-kolla20:02
*** jascott1 has quit IRC20:03
*** jascott1 has joined #openstack-kolla20:04
*** jascott1 has quit IRC20:08
*** jascott1 has joined #openstack-kolla20:10
*** markmcclain has quit IRC20:10
*** markmcclain has joined #openstack-kolla20:11
*** jascott1 has quit IRC20:13
*** dardelean has joined #openstack-kolla20:25
*** dardelean has quit IRC20:26
*** mgoddard has joined #openstack-kolla20:28
*** dardelean has joined #openstack-kolla20:32
*** dardelean has quit IRC20:32
*** dardelean has joined #openstack-kolla20:33
*** jascott1 has joined #openstack-kolla20:34
*** dardelean has quit IRC20:37
*** jascott1 has quit IRC20:38
*** jascott1 has joined #openstack-kolla20:41
*** jascott1 has quit IRC20:43
*** ktibi has quit IRC20:45
*** kristaps has quit IRC20:46
*** jascott1 has joined #openstack-kolla20:47
openstackgerritMark Goddard proposed openstack/kolla-ansible master: Fix ironic inspector public endpoint  https://review.openstack.org/52827820:48
*** wojdec has quit IRC20:48
*** mchlumsky has joined #openstack-kolla20:48
*** mchlumsky_ has quit IRC20:50
*** jascott1 has quit IRC20:50
*** jascott1 has joined #openstack-kolla20:54
*** jascott1 has quit IRC20:56
*** jascott1 has joined #openstack-kolla20:58
*** mgoddard has quit IRC21:05
kfox1111interesting... github seems to be starting to security scan code in repos hosted there...21:12
*** jascott1 has quit IRC21:29
*** jascott1 has joined #openstack-kolla21:29
*** jascott1 has quit IRC21:30
*** jascott1 has joined #openstack-kolla21:30
*** jascott1 has quit IRC21:34
*** jascott1 has joined #openstack-kolla21:35
*** threestrands has joined #openstack-kolla21:35
*** threestrands has quit IRC21:35
*** threestrands has joined #openstack-kolla21:35
*** jascott1 has quit IRC21:37
*** jascott1 has joined #openstack-kolla21:38
rwellumkfox1111: are you having to patch your clouds for the CPU bugs this week?21:39
kfox1111inc: https://review.openstack.org/#/c/528724/21:40
kfox1111rwellum: as soon as possible, yeah.21:40
*** jascott1 has quit IRC21:42
*** sbezverk has joined #openstack-kolla21:43
*** dmellado has quit IRC21:43
*** dmellado has joined #openstack-kolla21:46
inc0kfox1111 rwellum playbook orchestration incoming soon:)21:52
inc0my personal request, let's merge it asap in it's rough, but functional, state, rewrite quickstart to become managable21:53
inc0and then gradually improve it both on gate and general quality fields21:53
rwelluminc0: +1 sounds good.21:53
inc0reason I'm asking for it is we need onboarding mechanism21:53
inc0for new people21:53
rwellumThis works inc0 :  curl https://raw.githubusercontent.com/RichWellum/k8s/master/ko.py | python - ens3 ens4 --image_version pike -cni weave21:54
rwellumjk tbh21:54
rwellumPrefer a playbook and looking forward to playing with it.21:54
inc0at the end it's going to be playbook running in container21:55
rwellumNow that's interesting - what do we gain?21:56
inc0helm install compute-kit21:56
inc0that will start a job on k8s21:57
inc0which will build all microcharts21:57
inc0setup all that's needed21:57
inc0and run ansible-playbook to deploy thing21:57
rwellumAre you feeling better btw inc0 ? I'm in a conference and I swear 50% are hacking coughs and sneezes into the air...21:57
kfox1111inc0: sure. though still want to see the seperation before I'm good with it.21:58
inc0think of it as ansible-driven ioeratir21:58
inc0operator21:58
rwellumThe first part - helm install compute-kit - that works already?21:58
kfox1111perfectly happy with an ansible driven operator. :)21:58
inc0kfox1111: there is little overlap really since we don't have orch at all now;)21:58
inc0well not fully21:58
kfox1111inc0: so, simple enough to rename it operator/xxxx21:58
inc0you still need to create secrets/configmaps21:58
inc0build charts21:58
kfox1111the charts should be prebuilt into the container I think.21:59
kfox1111no reason to build them every time.21:59
inc0after that helm install compute-kit will just throw it all with entrypoint21:59
inc0ansible will be more sane workload and will do all the manual thingys21:59
kfox1111would rather it not use the service charts. those have always been a bit sketchy.21:59
inc0well, container has to be built21:59
rwellumkfox1111: +1 - this is the longest step in the whole process.21:59
inc0whether it's us -> dockerhub or user22:00
kfox1111yeah. but the charts don't need to be rebuilt on every launch.22:00
inc0well, or both22:00
inc0yeah I agree22:00
inc0we can have periodic job much like kolla jobs22:00
inc0that builds orch image and pushes to dockerhub22:00
inc0then really you barely need to do anything besides running one yaml we document;)22:01
kfox1111it should basically be a ansibleification of whats in tests/bin/ceph_workflow.sh22:01
kfox1111+1.22:01
inc0curl docs.openstack.org/kolla-k8s-compute-kit | kubectl create22:01
inc0kfox1111: yeah pretty much22:01
kfox1111like elasticsearc-operator or rook-operator.22:01
inc0and making it non gate specific22:01
kfox1111helm install rook-operator,22:01
inc0yup22:02
kfox1111kubectl create -f mycluster.yaml22:02
kfox1111done. :)22:02
inc0you can create globals.yml like you do for kolla-ansible and create configmap22:02
inc0to control your os installation22:02
inc0and bam, it installs22:02
kfox1111globals.yaml overrides should probably be in mycluster.yaml.22:02
kfox1111some flag saying:22:03
inc0well whatever you want to pass it, it's fine22:03
kfox1111ansible-genconfig:22:03
kfox1111  globals.yaml stuff here22:03
kfox1111then there is only one document the operator has to pull.22:03
inc0well, no reason we need both globals and cloud.yml22:03
kfox1111right.22:03
inc0just squash it to one file/configmap22:03
inc0to govern all the things22:03
kfox1111well, kind of depends what we're talking about I guess.22:04
rwellumYeah that's always been confusing/overlapping22:04
kfox1111globals.yml is mostly about config of the openstack ini stuff.22:04
inc0in any case, that's for later22:04
inc0now yes22:04
kfox1111while cloud.yaml was just k8s specific archetecture bits.22:04
inc0but if we squash it it also can do things like enable_cinder: true22:04
kfox1111the k8s specific stuff is absolutelyl critical.22:04
kfox1111the rest, is optional.22:04
kfox1111you could generate config entirely yourself and skip the rest.22:05
inc0I'm thinking of globals.yml in kolla-ansible standard - that also affects deployment22:05
inc0however we name file, I don't care22:05
kfox1111hmm.. well, for operator I don't really care so much. since it is a clean seperation at the microservice level.22:06
kfox1111so wathever the devs think.22:06
inc0yeha we'll figure it out22:06
kfox1111kk.22:06
kfox1111just be careful. we spent a lot of work making everything very customizable via the cloud.yaml stuff.22:07
kfox1111far more I think then kolla-ansible is.22:07
openstackgerritMerged openstack/kolla-kubernetes master: Cinder is missing the v3 API endpoints.  https://review.openstack.org/52872422:07
kfox1111so please don't just revert to the kolla-ansible way.22:07
inc0ofc22:08
inc0I'm saying we can do it22:08
rwellum^^^ Woot thanks inc0 kfox1111  (for the merge)22:08
inc0idea I mean22:08
kfox1111yup. just giving you a heads up.22:08
inc0idea being one file to rule dem all22:08
kfox1111the config layout is probably one of the easiest parts of it. so not too big a deal until closer to 1.0.22:08
kfox1111yup.22:09
inc0I think we can arrive to "edit globals.yml, fill it with options -> kubectl create configmap --from-file globals.yml -> kubectl create -f deply_me_openstack.yml -> wait for it -> wait for it -> this is how you spawn vm"22:10
*** markmcclain has quit IRC22:10
*** markmcclain has joined #openstack-kolla22:11
rwellumThat is using ansible behind the scenes?22:11
inc0yeah22:12
inc0deploy me openstack would run a job from image published in hub22:12
inc0image will have microcharts built and ansible playbook22:12
inc0ansible playbook will read configmap and deploy openstack accordingly22:12
kfox1111inc0: no configmap.22:14
kfox1111kubectl create -f myopenstack.yaml22:14
kfox1111shoudl be kind=OpenStackComputeKit or something like that.22:15
inc0well, configmap can be part of it;) but ok, however we model input file, up to us22:15
kfox1111under a spec section can be all the config.22:15
inc0that works as well22:16
kfox1111up to you, but I'm just telling you how operators work.22:16
inc0then gate scenario would be just this one ifle22:16
inc0file22:16
kfox1111yeah.22:16
kfox1111should look something like this:22:18
kfox1111https://github.com/upmc-enterprises/elasticsearch-operator/blob/master/example/example-es-cluster-minikube.yaml22:18
inc0wfm22:19
*** markmcclain has quit IRC22:19
kfox1111the operator then looks at the current state, the requested state in the doc, and launches/upgrades helm charts from within its own container as needed to get the desired state.22:20
*** markmcclain has joined #openstack-kolla22:20
kfox1111aka, dump out the spec section to an ansible compatible format and run asible on the roles.22:20
inc0yeah somethign like that22:21
*** ipsecguy_ has joined #openstack-kolla22:21
*** ManoX has joined #openstack-kolla22:27
*** jistr has quit IRC22:29
*** dardelean has joined #openstack-kolla22:33
openstackgerritJustin Scott proposed openstack/kolla-kubernetes master: Deploy with ansible inside orchestration container  https://review.openstack.org/52084722:34
inc0yay22:35
inc0let the festivities commence!22:35
kfox1111still needs stuff moved to orchestration22:35
*** dardelean has quit IRC22:38
*** spiette has joined #openstack-kolla22:40
*** dardelean has joined #openstack-kolla22:46
*** jascott1 has joined #openstack-kolla22:46
jascott1kfox1111 are you saying move 'ansible' dir or just the new piece? It uses the same var file so seems we would want to move it all...22:50
*** dardelean has quit IRC22:50
kfox1111just the new pieces.22:53
kfox1111the existing ansible dir is for genconfig only.22:53
kfox1111and temporary. (hopefully)22:53
kfox1111we reached an agreement a while ago that rather then add more to it, making it harder for someone to tackle genconfig reworking,22:54
kfox1111we would keep orchestration code seperate.22:54
kfox1111if you wanted to move the genconfig stsuff from ansible to genconfig/ansible or something like that for consistency, that would be ok too.22:55
jascott1the orchestration piece uses the existing ansible to generate config and then creates configmaps from the resulting files23:01
kfox1111can it just exec out to do the genconfig?23:02
kfox1111will make it easier to replace with helm for genconfig when that gets done too.23:02
jascott1its currently sharing the var file from ansible/23:02
jascott1it looks like one can pass in a var file now so maybe that would work23:03
kfox1111whats it need from there?23:03
jascott1i will have to check but not much iirc23:03
kfox1111k.23:03
inc0ansible isn't great about reusing code from outside your role23:06
inc0so moving orch out of ansible could potentially end up with lots of duplication, and that'd be bad23:06
*** dave-mccowan has joined #openstack-kolla23:07
jascott1looks like mostly interfaces and IPs23:07
kfox1111inc0: today, you can do all of genconfig with an external command. why would that be hard to do via ansible calling the external command?23:08
kfox1111jascott1: those should come from the CRD. so can skip them?23:08
inc0what I'm saying is it's easier to keep genconfig command operable while having other tasks for deploy in same role23:09
inc0than moving deploy and genconfig totally disconnected23:09
inc0because deploy won't be able to access genconfigs default and vice versa23:09
kfox1111inc0: but harder in other ways, like if someone pops up and is willing to work on genconfig to not ansible, now they have to troll through  a lot of non genconfig code.23:10
inc0so potentially duplication if particular value would be needed in both - for example in keystone endpoint scenrario23:10
inc0it can be config.yml file in role neutron23:10
kfox1111inc0: its going to not work anyway once its not an ansible file. so don't assume out of the box it will work.23:10
inc0and only look at config.yml ignoring deploy.yml23:10
kfox1111user should be pushing config through the CRD, the operator conversts that to an ansible vars that the ansible operator reads then drives genconfig / helm via that.23:11
inc0yeah, but what I'm saying is if we separate roles completely (put it into different dir) this process ^ will potentially need to generate same var twice to 2 different places23:12
inc0ansible is stupid and can't do things like inheritance of roles23:12
kfox1111unavoidable I think.23:12
inc0avoidable if we will keep role neutron as singular role23:13
inc0with multiple sub-parts23:13
kfox1111we have a case where openstack ini's and kube need to know some things and they are currently in two different languages.23:13
inc0one for config and another for deploy23:13
kfox1111helm and ansible.23:13
inc0right, but we don't need to add 3rd way23:13
inc0because ansible and ansible is same language23:13
inc0I just don't think it will make any harder moving genconfig out of ansible really23:14
inc0I mean, you look at config.yaml file and templates23:14
kfox1111yeah. it will. for anyone but you I think. :/23:14
inc0and ignore all the rest23:14
kfox1111and as soon as we do, then we are back in the same boat.23:15
inc0you can keep them logically separate within same file23:15
inc0role*23:15
inc0no, I don't see why23:15
kfox1111we're talking forking like 6 default vars? thats not a huge maintenence burdon.23:15
inc0o say role "nova" config.yaml templates nova.conf23:15
inc0and role "nova" deploy.yml runs helm install23:16
kfox1111inc0: we're just phyilisophically in a very different place with reguards to repo layout.23:16
kfox1111I want totally seperate repos for tasks like config and orchestration.23:16
kfox1111you want to throw it all into /ansible.23:16
inc0you want to move it out of ansible? remove conf.yaml from nova, add it to helm chart, deploy.yaml stays the same23:16
kfox1111we agreed to agree earily to share 1 repo, but 2 different dirs.23:16
kfox1111dont' weltch on the agreement now.23:16
inc0right23:16
inc01 repo different dirs23:16
inc0ansible and non-ansible23:17
inc0I don't want ansible in 2 places23:17
kfox1111no, that is not what we agreed to.23:17
kfox1111split by task type.23:17
jascott1i can try the CRD/operator approach23:18
jascott1if so I need to create operator that reacts to CRD, passes those vars to playbook invocation23:18
kfox1111those of us that don't want to run orchestration want to make very sure when we use some parts we arn't accidently getting more then what we bargened for.23:18
kfox1111jascott1: yeay. that. :)23:18
kfox1111yeah.23:18
inc0so reason I think it's going to be duplicate work is taht Justin will need to examine every variable from defaults.yml and see if it belongs only in config, only in deploy or both23:18
inc0otherwise we have chaps23:18
inc0chaos23:18
jascott1do we automate the the creation of the CRD from ansible vars file?23:19
jascott1that would keep one origin23:19
kfox1111inc0: again, hopefully ansible genconfig is very short lived. gotta deal with this problem.23:19
kfox1111user provides crd.23:19
jascott1yes but we could gen it for them23:19
kfox1111we can provide some exmple ones.23:19
*** jistr has joined #openstack-kolla23:19
jascott1a script to create it, they still add it23:20
kfox1111then they need tooling to gen it, which has deps,23:20
kfox1111which should probably be in a container,23:20
kfox1111and we go around the loop again. turtles all the way down.23:20
jascott1so provide a template?23:20
kfox1111we provide some example crd's on a website for users to pull?23:20
kfox1111templates requrie template engine. same problem. :/23:21
jascott1ok lemme see if I got this23:21
kfox1111though could use helm for that.23:21
kfox1111for example, see:23:22
kfox1111https://github.com/upmc-enterprises/elasticsearch-operator/tree/master/charts23:22
jascott1CRD is just what we need for deploy or we moving genconfig vars too?23:22
kfox1111under the elasticsearch chart is a chart that just does come generic config of a single CRD resource.23:22
kfox1111both I think.23:22
kfox1111it is a specific request for a cluster.23:22
jascott1that makes it simpler23:23
kfox1111"give me an openstack taht looks like this"23:23
jascott1so 2 CRDs?23:23
kfox11111 crd.23:23
jascott1ok23:23
kfox1111there should be a program that watches for those types of cruds, converts the settings in them to ansible and runs the orchestration ansible code on it.23:24
kfox1111that ansible code should do stuff like: look to see if config is launched. if not, do genconfig. look to see if nova is launched. if not, call helm to launch each missing bit, etc.23:24
jascott1based on <service>_enabled: in CRD23:25
kfox1111yeah.23:25
kfox1111no idea what exactly that schema should look like.23:25
kfox1111the elasticsearch example again is a good starting point.23:25
kfox1111https://github.com/upmc-enterprises/elasticsearch-operator/blob/master/example/example-es-cluster-minikube.yaml23:26
kfox1111well..23:26
kfox1111they do it like this in the chart:23:27
kfox1111https://github.com/upmc-enterprises/elasticsearch-operator/blob/master/charts/elasticsearch/templates/cluster.yaml#L1023:27
kfox1111you can enable/disable kibana from being in the cluster in the crd.23:27
kfox1111their example I guess doesn't enable it unless you specifiy an image.23:27
kfox1111but I like your idea much better of having an enable flag. more like what the helm chart is doing.23:28
kfox1111one use case to consider is the one I posted to the helm issue tracker.23:28
kfox1111say you have 3 types of compute nodes for nova.23:28
kfox1111maybe nova.compute.xxxxx should be a list of settings rather then an enable/disable,23:29
kfox1111so the user can specify 3 instances of nova-compute helm chart, with the particular settings for each.23:29
kfox1111cinder-volume is probably in the same boat.23:29
jascott1hmmm23:29
kfox1111nova.compute[{nodeLabel: type1, other:...}, {nodeLabel: type2, other:...}]23:30
*** goldyfruit has quit IRC23:31
kfox1111(we have at least 3 unique types of hardware in our one cloud, and at least 2 in another)23:31
kfox1111nics are all different for sure. some have gpu's, etc.23:31
jascott1inc0 how is that scenario handled in kolla-ansible?23:31
*** dave-mccowan has quit IRC23:31
kfox1111node overrides I think. but relies on ansible pushing out settings directly to specific nodes during the deployment.23:32
kfox1111becuase k8s is in the middle, the same trick wont work.23:32
kfox1111we need individual instances of the microservice charts targeted to the hardware classes via node selectors to do the same.23:33
inc0jascott1: you can do either per-node config overrides or override any ansible var in inventory23:33
inc0node selectors would work, but I wonder if you can specify node label and pass it to ansible inventory for orch23:34
*** dardelean has joined #openstack-kolla23:34
inc0or however you want to say "nodes with these labels, use vlan tags 200:300"23:34
kfox1111inc0: thats what I'm talkign about I think. specing out the CRD in such a way as the operator knows it will have 3 node selectors and needs 3 helm instances.23:34
*** dardelean has quit IRC23:34
inc0we23:34
inc0we'd need to have configmap per node class23:35
*** dardelean has joined #openstack-kolla23:35
kfox1111hmm.. ultimately, yeah, I guess thats true.23:35
inc0or base configmap and override per node class23:35
kfox1111yeah.23:35
kfox1111I vaguely recall we decided something like that during a summit.23:35
kfox1111but taht was like a year ago?23:35
inc0this is what we discussed in ATL I think, nova-compute --config-file base.conf --config-file nodelabel.conf23:36
kfox1111yeah. that.23:36
kfox1111which kind of matches up with the way the helm charts are layed out. they can share more generic config and each instance has overrides if you want to override the more generic things.23:36
jascott1where nova-compute is "helm install nova-compute -f <file>"?23:36
kfox1111jascott1: no, thats the command inside the container.23:37
inc0no, nova-compute is acutal nova-compute command23:37
kfox1111there could be an overarching helm config package for base.conf. and then an optional one per instance of the nova-compute helm chart23:38
kfox1111same happens I guess with the neutron packages too.23:38
inc0or we can just assume user would create them manually23:38
kfox1111you need nutron-l3-agent configured differently for netwokr nodes and compute nodes for exmaple.23:39
kfox1111inc0: for now, thats probably just fine for the configmaps.23:39
inc0and orch would check "this node has label foo, is there nova-compute-foo configmap available? if yes, pass it"23:39
kfox1111just the helm instance settinsg are unavoidable.23:39
*** dardelean has quit IRC23:39
kfox1111inc0: yeah. there is an 'optional' configmap flag in the pod that could handle that.23:39
inc0right23:39
inc0and that'd also have to be pass to config.json for command23:40
kfox1111but regardless, we need as part of the crd, some iterated sets of config that loop over and launch multiple instances of the helm chart.23:40
inc0so here's my very personal request23:40
inc0let's merge base ansible23:40
kfox1111with overrides to the helm config for that particular chart.23:40
inc0and worry about crd later23:40
kfox1111crd's the api. ansibles the implementation.23:41
kfox1111the api is the real critical part.23:41
inc0good idea, let's not make it requirement for base patch because we can do it later23:41
inc0I agree23:41
inc0but I just want quickstart asap23:41
inc0better than we have today23:41
inc0then it will incresingly be better, with crd and all23:41
inc0but we need quickstart asap23:41
kfox1111fair enough. move it to /orchestration, and I'm good with it.23:41
inc0ok, I guess we can do that23:42
jascott1aright will do23:42
inc0jascott1: let's just copy defaults.yaml23:42
kfox1111k. thx.23:42
inc0we'll clean it up later23:42
kfox1111+123:42
jascott1ansible seems to have var file flag23:43
kfox1111that works.23:43
kfox1111its a temporary thing for a user to ever call it directly.23:43
jascott1cool I will give it a shot23:43
inc0jascott1: roles will not23:43
inc0but you can check how much of role is new23:43
kfox1111the operator will be calling it. so the extra little bit of cli isn't too bad.23:43
kfox1111inc0: going to the helm conference?23:45
inc0yeah23:45
kfox1111sweet. I got permission today.23:45
inc0too close to pass;)23:45
kfox1111so will see you there. :)23:45
kfox1111indeed.23:46
inc0we can ride share with jascott1 ;)23:46
jascott1yeah I volunteered to do misc grunt work23:46
jascott1like shuttle organizers etc if need be23:46
inc0is there more than 2 of us driving there?23:47
jascott1idk23:48
kfox1111not sure.23:53
kfox1111I offered to drive but mgmt is leaning towards flying. they panic when ice could be involved.23:53
SamYaplemmm flying through ice sounds safe23:53
* kfox1111 chuckles23:53
*** jistr has quit IRC23:54
*** jistr has joined #openstack-kolla23:55
*** mdorman has quit IRC23:55

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