Friday, 2017-03-31

*** caoyuan has joined #openstack-kolla00:01
openstackgerritMonty Taylor proposed openstack/kolla-ansible master: Add clouds.yaml file and use it  https://review.openstack.org/45200500:02
kfox1111hmm.. is that right? .... 172.17.0.2:5300:05
kfox1111seems out of range...00:06
kfox1111yeah, that sees wrong..00:08
kfox1111I bet the other host cant get to that.00:08
kfox1111darn... I bet thats due to the workaround.00:09
*** shashank_t_ has quit IRC00:10
sbezverkkfox1111: where do you see it?00:10
sbezverkkfox111100:10
kfox1111http://logs.openstack.org/91/451391/49/check/gate-kolla-kubernetes-deploy-centos-binary-2-ceph-multi-nv/d2b6aa7/logs/pods.yaml00:10
sbezverkkubectl get nodes -n kube-system00:10
sbezverkNAME            STATUS    AGE       VERSION00:10
sbezverkkube-ubuntu     Ready     3h        v1.6.000:10
sbezverkkube-ubuntu-2   Ready     2m        v1.6.000:10
kfox1111grep for podI00:10
kfox1111grep for podIP00:10
*** shashank_t_ has joined #openstack-kolla00:10
sbezverkkfox1111: hm, how come it pings then?00:11
kfox1111kube-dns is the one with the bad ip.00:12
kfox1111its hanging off docker0 I think.00:12
sbezverkwait it is dockers ip not?00:12
kfox1111yeah. docker0 wouild be 172.17.0.100:12
kfox1111so it works locally, but not across the network.00:12
sbezverkI see the same ip on my local setup00:14
kfox1111maybe because it comes up before cni.00:14
kfox1111can you kill the pod after canal starts?00:14
kfox1111it might get a proper ip then.00:14
*** shashank_t_ has quit IRC00:15
sbezverkkfox1111: sure I can start00:15
sbezverkkfox1111: still the same00:16
sbezverkip00:16
kfox1111very weird...00:16
kfox1111its not net=host right?00:17
sbezverkwe need to provide fixed ip to the container, maybe then it will work00:17
kfox1111I'm thinking its avoiding cni...00:17
kfox1111if you kubectl run a pod that lands on the first node, does it get a 172.17 address?00:18
kfox1111its not net=host.00:21
kfox1111we should see if we can undo the workaround.00:22
sbezverkkfox1111: yeah it gets ip from docker's range00:22
kfox1111can you reenable it on your primary, systemctl daemon-reload; systemctl restart kubelet;00:23
kfox1111and kill the kube-dns pod?00:23
kfox1111maybe the problem was kube-dns was sticking around.00:23
sbezverkkfox1111: I mean I can try but I think dns pod is not relevant00:24
sbezverkevery pod gets wrong ip address00:24
sbezverkI brought up centos pod00:24
sbezverkand it got ip from docker range00:24
kfox1111interesting...00:24
kfox1111 podIP: 172.17.0.3 on the other test-dns pod.00:25
kfox1111so that would make sense it would work.00:25
kfox1111sbezverk: which host did it land on?00:25
*** adrian_otto has quit IRC00:26
sbezverkon 2nd node00:27
kfox1111ok. so we'd have to reenable the cni plugin on both nodes...00:28
kfox1111or change the workaround to only apply on the first node,00:28
kfox1111then we only need to clean up the first node.00:28
sbezverkkfox1111: ok I will try to revert workaround on "master: for now00:28
kfox1111yeah, confirmed. I'm seeing docker0 ip's on both nodes too.00:28
*** zhurong has joined #openstack-kolla00:29
*** caoyuan has quit IRC00:32
sbezverkkfox1111: reverting workaround fixed00:34
sbezverknew pod got right ip address00:34
*** MasterOfBugs has quit IRC00:35
sbezverkkfox1111: deleting kube-dns pod and then re-creating it, fixes it as well00:36
sbezverk kfox1111: so we have to revert after all init/join are completed00:37
*** sayantan_ has joined #openstack-kolla00:40
*** tovin07_ has joined #openstack-kolla00:44
kfox1111easiest would be to put a conditional around the network removal so it only happens on the master.00:44
kfox1111then we only need to fix it there.00:45
sbezverkkfox1111: not sure if it is on the master00:45
masberhi, need some clarification, has anyone here deployed openstack control plane using kolla on a vmware environment? because I am trying to do it but my router namespace is not able to ping outside and I am wondering if there is an issue with vmware00:45
sbezverki did it on both00:45
kfox1111sbezverk: the workaround is only needed to get kubeadm to boot.00:46
kfox1111I think.00:46
*** yangyape_ has joined #openstack-kolla00:46
kfox1111if we start the slave with the cni driver flag still enabled,  Ithink it will be fine.00:46
sbezverkkfox1111: ont exactly, it chnages kubelet behavior00:46
sbezverkit might also impact join00:47
kfox1111pretty sure it will work. but don't know for sure.00:47
sbezverkkfox1111: if you want to take a stab at it on the latest version of ps, go for it..00:48
*** KTJ has joined #openstack-kolla00:48
sbezverkI will try to clean up slave and try it locally00:49
*** yangyapeng has quit IRC00:49
*** KTJ has quit IRC00:49
*** cuongnv has joined #openstack-kolla00:49
*** KTJ has joined #openstack-kolla00:50
*** yangyape_ has quit IRC00:50
kfox1111kk00:51
*** yingjun has joined #openstack-kolla00:54
sbezverkkfox1111: it looks like it worked00:56
sbezverkI did kubeadm reset then reboot00:56
kfox1111cool.00:57
*** yuanying has quit IRC00:58
*** eanylin has quit IRC01:02
*** KTJ has quit IRC01:03
kfox1111almost done...01:04
kfox1111close.01:07
kfox1111sbezverk: can you please find a label selector for kube-dns?01:07
kfox1111to identify the pod for deletion.01:07
sbezverkkfox1111: one sec01:07
sbezverkk8s-app: kube-dns01:08
kfox1111kubectl get pods -l k8s-app=kube-dns -n kube-system -o json | jq .items[].metadata.name ?01:09
*** yuanying has joined #openstack-kolla01:10
sbezverkyep, but is quoted01:10
kfox1111kubectl get pods -l k8s-app=kube-dns -n kube-system -o json | jq -r .items[].metadata.name ?01:10
sbezverk"kube-dns-1080222536-zk7th"01:10
*** caoyuan has joined #openstack-kolla01:11
kfox1111lets see if it will be recreated on restart.01:12
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: Changes for kubernetes 1.6.0 upgrade  https://review.openstack.org/45139101:14
*** yangyapeng has joined #openstack-kolla01:15
sbezverkkfox1111: where do you save original network settings?01:18
kfox1111the file itself. :)01:19
kfox1111 I just tag a # to the front of the line, then remove it. :)01:19
sbezverkkfox1111: I see, cool01:20
openstackgerritcaoyuan proposed openstack/kolla master: Install zun ui into horizon image  https://review.openstack.org/45201901:23
*** zhubingbing_ has joined #openstack-kolla01:24
*** yangyapeng has quit IRC01:29
*** yangyapeng has joined #openstack-kolla01:30
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Enable zun ui when zaqar enabled  https://review.openstack.org/45202001:30
*** eanylin has joined #openstack-kolla01:33
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Enable zun ui when zaqar enabled  https://review.openstack.org/45202001:34
*** yangyapeng has quit IRC01:35
*** ubuntu__ has joined #openstack-kolla01:38
*** eanylin has quit IRC01:40
*** manheim has joined #openstack-kolla01:43
Jeffrey4lsup mnaser01:44
Jeffrey4lsdake, re k8s doc change gate, i know how. i will push a fix today.01:44
*** lucasxu has joined #openstack-kolla01:45
kfox1111sbezverk: success01:48
*** manheim has quit IRC01:48
kfox1111some random failures still, but multinode's passing.01:48
*** oanson has quit IRC01:55
*** oanson has joined #openstack-kolla01:56
*** yangyapeng has joined #openstack-kolla01:56
*** dixiaoli has joined #openstack-kolla01:58
*** yangyapeng has quit IRC02:07
*** eaguilar has quit IRC02:08
duonghqsdake, ping02:10
*** lucasxu has quit IRC02:10
*** lucasxu has joined #openstack-kolla02:11
*** yangyapeng has joined #openstack-kolla02:13
sbezverkkfox1111: congrats!!!02:13
*** yangyapeng has quit IRC02:14
kfox1111sbezverk: you too!! :)02:15
openstackgerritSurya Prakash (spsurya) proposed openstack/kolla-kubernetes master: README.txt character improvement  https://review.openstack.org/45165402:18
*** lucasxu has quit IRC02:19
*** goldyfruit has joined #openstack-kolla02:29
openstackgerritSurya Prakash (spsurya) proposed openstack/kolla-kubernetes master: README.rst character improvement  https://review.openstack.org/45165402:30
*** jrobinson has quit IRC02:30
*** caoyuan has quit IRC02:33
openstackgerritDuong Ha-Quang proposed openstack/kolla master: Spec - Zero-downtime upgrade in Kolla  https://review.openstack.org/40959802:38
*** yangyapeng has joined #openstack-kolla02:43
*** caoyuan has joined #openstack-kolla02:57
*** yangyapeng has quit IRC02:57
*** yangyapeng has joined #openstack-kolla03:02
sdakeduonghq sup03:07
duonghqsdake, why we need unsigned package for k8s 1.5.4 in centos? the official ones are removed?03:08
*** jrobinson has joined #openstack-kolla03:09
*** yuanying has quit IRC03:11
*** britthouser has quit IRC03:14
*** yuanying has joined #openstack-kolla03:14
*** britthouser has joined #openstack-kolla03:14
*** shashank_t_ has joined #openstack-kolla03:16
*** yangyape_ has joined #openstack-kolla03:16
*** yangyapeng has quit IRC03:17
*** yangyapeng has joined #openstack-kolla03:17
*** yangyapeng has quit IRC03:20
sdakeJeffrey4l thanks :)03:20
*** yangyape_ has quit IRC03:21
*** caoyuan has quit IRC03:22
*** manheim has joined #openstack-kolla03:30
*** prameswar has joined #openstack-kolla03:30
*** manheim has quit IRC03:35
*** caoyuan has joined #openstack-kolla03:40
*** lamt has joined #openstack-kolla03:42
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Fix the check.yml of Zun does not exist  https://review.openstack.org/45203803:43
*** dixiaoli has quit IRC03:48
*** dixiaoli has joined #openstack-kolla03:52
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: Changes for kubernetes 1.6.0 upgrade  https://review.openstack.org/45139103:58
sbezverksdake: sdake03:59
sbezverksdake: nv http://logs.openstack.org/91/451391/50/check/gate-kolla-kubernetes-deploy-centos-binary-2-ceph-multi-nv/de00799/04:00
*** dixiaoli has quit IRC04:00
*** britthouser has quit IRC04:06
*** britthouser has joined #openstack-kolla04:06
*** zhurong has quit IRC04:09
*** n0isyn0i1e has joined #openstack-kolla04:10
*** goldyfruit has quit IRC04:11
*** ubuntu__ has quit IRC04:12
*** ubuntu__ has joined #openstack-kolla04:13
*** n0isyn0ise has quit IRC04:13
*** eanylin has joined #openstack-kolla04:14
*** gkadam has joined #openstack-kolla04:17
*** japestinho has quit IRC04:20
*** dixiaoli has joined #openstack-kolla04:24
*** yangyapeng has joined #openstack-kolla04:24
*** dixiaoli has quit IRC04:25
openstackgerritzhubingbing proposed openstack/kolla-kubernetes master: Fix problem with kollakube res create configmap  https://review.openstack.org/43974004:28
*** zhurong has joined #openstack-kolla04:30
*** prameswar has quit IRC04:32
*** duonghq has quit IRC04:40
*** skramaja has joined #openstack-kolla04:43
*** bmace has quit IRC04:44
*** bmace has joined #openstack-kolla04:44
*** yangyapeng has quit IRC04:55
*** yangyapeng has joined #openstack-kolla04:56
openstackgerritzhubingbing proposed openstack/kolla-kubernetes master: Fix problem with kollakube res create configmap  https://review.openstack.org/43974004:58
*** yangyapeng has quit IRC05:00
*** lamt has quit IRC05:19
*** targon has joined #openstack-kolla05:23
*** jrobinson has quit IRC05:23
*** jrobinson has joined #openstack-kolla05:28
*** dixiaoli has joined #openstack-kolla05:35
*** zhurong has quit IRC05:41
*** lamt has joined #openstack-kolla05:42
*** dixiaoli has quit IRC05:43
*** yangyapeng has joined #openstack-kolla05:52
*** prameswar has joined #openstack-kolla05:52
*** adrian_otto has joined #openstack-kolla05:52
*** jaosorior has joined #openstack-kolla05:56
*** dixiaoli has joined #openstack-kolla05:59
*** dixiaoli has quit IRC06:00
*** zhurong has joined #openstack-kolla06:05
openstackgerritjimmygc proposed openstack/kolla-ansible master: Add VMware NSXV support to neutron  https://review.openstack.org/45009206:05
*** duonghq has joined #openstack-kolla06:07
*** yangyapeng has quit IRC06:08
*** yangyapeng has joined #openstack-kolla06:08
openstackgerritSurya Prakash (spsurya) proposed openstack/kolla-kubernetes master: Deployment Guide Documentation  https://review.openstack.org/44735606:13
*** yangyapeng has quit IRC06:13
*** dixiaoli has joined #openstack-kolla06:14
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Update "always_run" to "check_mode"  https://review.openstack.org/45205606:23
*** yangyapeng has joined #openstack-kolla06:26
*** Serlex has joined #openstack-kolla06:29
*** yangyapeng has quit IRC06:31
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Update "always_run" to "check_mode"  https://review.openstack.org/45205606:40
*** jmccarthy has joined #openstack-kolla06:43
*** satyar has joined #openstack-kolla06:45
openstackgerritjimmygc proposed openstack/kolla-ansible master: Add Glance Swift backend support  https://review.openstack.org/45205906:47
duonghqJeffrey4l, are you there?06:50
duonghqabout this ps: https://review.openstack.org/#/c/452056/206:51
openstackgerritshaofeng cheng proposed openstack/kolla-ansible master: Fix secure_proxy_ssl_header option in nova  https://review.openstack.org/45206206:51
Jeffrey4lduonghq, yep.06:51
duonghqis it right time to do the migration?06:51
duonghqwe revert it once it the past06:51
Jeffrey4lduonghq, before doing this. we need bump the min ansible version to 2.1 or 2.2.06:51
duonghq*reverted06:51
Jeffrey4li think bump the ansible version is OK.06:52
Jeffrey4lin this cycle.06:52
Jeffrey4lbut this patch shouldn't be merged until bump ansible version is merged.06:52
*** jrobinson has quit IRC06:52
duonghqJeffrey4l, got it, can you do the dump when you feel convenient?06:52
duonghq*bmp06:52
duonghq*bump06:53
Jeffrey4lnp.06:53
Jeffrey4lbtw, i -1 for that patch.06:53
duonghqJeffrey4l,  ok06:54
openstackgerritSurya Prakash (spsurya) proposed openstack/kolla-kubernetes master: Deployment Guide Documentation  https://review.openstack.org/44735606:57
*** imcsk8 has joined #openstack-kolla06:58
*** imcsk8_ has quit IRC06:58
*** yangyapeng has joined #openstack-kolla07:05
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible master: Bump min Ansible version to 2.2.0  https://review.openstack.org/45206707:05
*** japestinho has joined #openstack-kolla07:07
*** jimmygc has joined #openstack-kolla07:15
*** matrohon has joined #openstack-kolla07:16
*** yingjun has quit IRC07:18
*** lamt has quit IRC07:20
*** pcaruana has joined #openstack-kolla07:27
*** sayantan_ has quit IRC07:28
duonghqJeffrey4l, why we do not have ansible in requirement07:28
Jeffrey4lduonghq, hrm.. the items in requirements.txt should be exist in requirements project first, iirc.07:29
*** dixiaoli has quit IRC07:29
Jeffrey4lotherwise, the gate jobs will be red.07:29
Jeffrey4lBut you can add it to have a try.07:30
*** caoyuan_ has joined #openstack-kolla07:30
*** prameswar has quit IRC07:30
*** mgoddard has joined #openstack-kolla07:30
duonghqJeffrey4l, ok07:31
*** n0isyn0i1e is now known as n0isyn0ise07:31
*** dixiaoli has joined #openstack-kolla07:32
openstackgerritDuong Ha-Quang proposed openstack/kolla-ansible master: Add ansible to requirement  https://review.openstack.org/45207507:33
*** caoyuan has quit IRC07:33
*** shashank_t_ has quit IRC07:33
*** shashank_t_ has joined #openstack-kolla07:34
openstackgerritSurya Prakash (spsurya) proposed openstack/kolla master: Fix oslo_debug_helper  https://review.openstack.org/44439807:37
*** Deys has joined #openstack-kolla07:38
*** shashank_t_ has quit IRC07:38
openstackgerritSurya Prakash (spsurya) proposed openstack/kolla master: Fix oslo_debug_helper not working  https://review.openstack.org/44439807:40
*** yangyapeng has quit IRC07:41
*** yangyapeng has joined #openstack-kolla07:41
-openstackstatus- NOTICE: Jobs in gate are failing with POST_FAILURE. Infra roots are investigating07:43
*** ChanServ changes topic to "Jobs in gate are failing with POST_FAILURE. Infra roots are investigating"07:43
*** sayantan_ has joined #openstack-kolla07:48
*** egonzalez has joined #openstack-kolla07:48
*** matrohon has quit IRC07:55
*** matrohon has joined #openstack-kolla07:56
*** caowei has joined #openstack-kolla08:01
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Enable zun ui when zun enabled  https://review.openstack.org/45202008:01
*** gfidente has joined #openstack-kolla08:02
*** dixiaoli has quit IRC08:05
*** dixiaoli has joined #openstack-kolla08:05
*** athomas has joined #openstack-kolla08:06
*** manheim has joined #openstack-kolla08:07
*** manheim has quit IRC08:12
*** sayantan_ has quit IRC08:15
openstackgerritjimmygc proposed openstack/kolla-ansible master: Make glance filesystem_store_datadir configurable.  https://review.openstack.org/45209408:20
*** jimmygc_ has joined #openstack-kolla08:22
-openstackstatus- NOTICE: logs.openstack.org has corrupted disks, it's being repaired. Please avoid rechecking until this is fixed08:23
*** ChanServ changes topic to "logs.openstack.org has corrupted disks, it's being repaired. Please avoid rechecking until this is fixed"08:23
*** jimmygc has quit IRC08:24
*** shardy has joined #openstack-kolla08:26
*** papacz has joined #openstack-kolla08:29
openstackgerritJames McCarthy proposed openstack/kolla-ansible master: Change default permissions in jinja templates.  https://review.openstack.org/44579708:34
*** shashank_t_ has joined #openstack-kolla08:36
*** shardy has quit IRC08:37
*** eaguilar has joined #openstack-kolla08:38
*** shardy has joined #openstack-kolla08:38
*** sayantan_ has joined #openstack-kolla08:44
*** dixiaoli has quit IRC08:45
*** eaguilar has quit IRC08:47
*** shashank_t_ has quit IRC08:48
*** sayantan_ has quit IRC08:49
*** ipsecguy has quit IRC08:51
*** ipsecguy has joined #openstack-kolla08:51
*** matrohon has quit IRC08:51
*** matrohon has joined #openstack-kolla08:52
*** pbandark has joined #openstack-kolla08:59
*** matrohon has quit IRC08:59
*** manheim has joined #openstack-kolla09:03
*** yangyape_ has joined #openstack-kolla09:04
*** blallau has joined #openstack-kolla09:05
*** dixiaoli has joined #openstack-kolla09:05
*** yangyapeng has quit IRC09:07
satyarhi inc009:12
satyarhow are you?09:12
*** matrohon has joined #openstack-kolla09:17
*** varto has joined #openstack-kolla09:21
*** rmart04 has joined #openstack-kolla09:21
*** caoyuan_ has quit IRC09:25
*** caoyuan has joined #openstack-kolla09:26
*** yangyape_ has quit IRC09:26
*** matrohon_ has joined #openstack-kolla09:28
*** matrohon has quit IRC09:30
*** caoyuan_ has joined #openstack-kolla09:30
hrwmorning09:30
openstackgerritPaul Bourke (pbourke) proposed openstack/kolla-ansible master: Update Keystone haproxy config to balance based on source ip  https://review.openstack.org/45135809:31
*** yangyapeng has joined #openstack-kolla09:31
*** mgoddard has quit IRC09:32
*** caoyuan has quit IRC09:33
*** zhuzeyu has quit IRC09:37
sdakemorning folks09:38
*** sayantan_ has joined #openstack-kolla09:39
sdakeegonzalez since you modified the review directly you can remove your-109:39
sdakefor https://review.openstack.org/#/c/346455/09:40
egonzalezsdake, done09:40
*** sayantan_ has quit IRC09:43
*** rmart04 has quit IRC09:48
*** adrian_otto has quit IRC09:53
*** yangyapeng has quit IRC09:54
*** yangyapeng has joined #openstack-kolla09:54
*** mgoddard has joined #openstack-kolla10:00
*** athomas has quit IRC10:01
*** duonghq has quit IRC10:04
vartoHaving issue with installing multinode kolla cinder block storage working just fine (creates volumes), but when starting vm getting error can't connect to any Iscsi portal?10:07
*** matrohon_ has quit IRC10:08
*** matrohon_ has joined #openstack-kolla10:08
vartoredeploying currently and double checking nova-compute configs, but just haven't found way to fix this.10:09
*** athomas has joined #openstack-kolla10:09
*** athomas has quit IRC10:09
*** athomas has joined #openstack-kolla10:09
*** caoyuan_ has quit IRC10:11
openstackgerritshaofeng cheng proposed openstack/kolla-ansible master: Add VMware DataStore support to cinder  https://review.openstack.org/45213110:13
*** zhubingbing_ has quit IRC10:13
egonzalezvarto, can you please check if iscsi and tgtd containers are running and bind to the correct IP address? share config, globals and error logs10:17
vartotgtd and iscsi was running, but I'll check those again after redeploy.10:18
*** zhurong has quit IRC10:18
*** tovin07_ has quit IRC10:22
*** sambetts|afk is now known as sambetts10:25
*** satyar has quit IRC10:28
*** caoyuan has joined #openstack-kolla10:30
*** pbourke has quit IRC10:30
*** pbourke has joined #openstack-kolla10:32
*** sayantan_ has joined #openstack-kolla10:33
openstackgerritEduardo Gonzalez proposed openstack/kolla master: WIP: Add nginx image  https://review.openstack.org/45213410:33
*** kolla-slack1 has quit IRC10:36
openstackgerritEduardo Gonzalez proposed openstack/kolla master: WIP: Add nginx image  https://review.openstack.org/45213410:36
*** kolla-slack has joined #openstack-kolla10:36
*** varto has quit IRC10:37
*** sayantan_ has quit IRC10:37
*** matrohon_ has quit IRC10:38
*** cuongnv has quit IRC10:40
*** zhurong has joined #openstack-kolla10:41
*** dixiaoli has quit IRC10:49
*** dixiaoli has joined #openstack-kolla10:51
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Karbor services restarting issue on conf update  https://review.openstack.org/45173510:52
*** manheim has quit IRC10:52
openstackgerritBertrand Lallau proposed openstack/kolla-ansible master: Trove services restarting issue on conf update  https://review.openstack.org/45172010:56
*** rhallisey has joined #openstack-kolla10:59
*** manheim has joined #openstack-kolla11:08
*** shardy is now known as shardy_lunch11:14
targonHi! Quick question. I installed openstack 4.0.0. (all-in-one) to Ubuntu 16.10 running in KVM. Othervise ok, but all static content missing when logged into Horizon. Only icon I see is Openstack icon in top left corner. I can start cirros instances there etc. but dasboard layout is total mess without static content (and propably scripts).11:14
targonAny idea what I have missed? I followed instructions in https://docs.openstack.org/project-deploy-guide/kolla-ansible/ocata/quickstart.html . When tried 3.0.2 release i got icons, but there were other problems. Which version I should install?11:14
hrwhttp://people.linaro.org/~marcin.juszkiewicz/kolla/11:17
hrwnice table with effects of builds for different architectures11:18
*** jtriley has quit IRC11:19
hrwwhat do you think? egonzalez sdake pbourke11:22
sdakehrw looks cool11:23
sdakehrw ought to post to te mailing list for wider audience11:23
hrwsure11:23
sdakehrw  can i ask - are ou getting reviews on your work in sufficient time?11:23
hrwsdake: I took time two days ago and split whole patchset into separate ones + one main one. so far reviews are quite ok11:24
hrwsdake: I think that random gates failures are bigger issue than review speed11:25
*** sayantan_ has joined #openstack-kolla11:27
*** sayantan_ has quit IRC11:31
*** matrohon has joined #openstack-kolla11:38
*** matrohon has quit IRC11:41
*** jimmygc_ has quit IRC11:41
*** srwilkers has joined #openstack-kolla11:42
*** jimmygc has joined #openstack-kolla11:45
*** yangyapeng has quit IRC11:45
*** yangyapeng has joined #openstack-kolla11:46
*** skramaja_ has joined #openstack-kolla11:50
*** yangyapeng has quit IRC11:51
*** skramaja has quit IRC11:52
openstackgerritjimmygc proposed openstack/kolla-ansible master: Add Glance Swift backend support  https://review.openstack.org/45205911:53
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Fix Haproxy reconfigure  https://review.openstack.org/45216611:53
*** dixiaoli has quit IRC11:54
*** magicboiz has quit IRC11:55
*** bjolo has joined #openstack-kolla11:59
*** zhurong has quit IRC11:59
sdakehrw ya - no solution for those random gate failures yet11:59
sdakehrw annoying as they are11:59
hrwyep12:00
*** schwicht has quit IRC12:00
sdakeJeffrey4l kfox1111 sort of had an idea about uploading kubernetes rpms to tarballs.oo - and I had a riff on that idea which was to upload all RPM dependencies (from a squid cache possibly?) used for each build to tarballs.oo12:01
sdakethis would permit the ability to completely reproduce the build from what was gated12:01
*** shardy_lunch is now known as shardy12:03
*** goldyfruit has joined #openstack-kolla12:04
*** goldyfruit has quit IRC12:04
openstackgerritshaofeng cheng proposed openstack/kolla-ansible master: Add VMware DataStore support to glance  https://review.openstack.org/45217612:08
mnasermorning o/12:09
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: WIP: Split keepalived own role  https://review.openstack.org/45217712:11
Jeffrey4lsdake, for squid solution is hard. squid can not save every. imo.12:11
Jeffrey4leverything*12:11
sdakeJeffrey4l well you get hte idea12:11
sdakesquid was just something that popped out as an implementation idea12:12
Jeffrey4lwhy we need upload rpm to tarballs?12:12
sdakepeople comain the build is not reproducible12:12
sdakewhat yo ubuild today may not work tomorrow12:12
Jeffrey4li do not think this is caused by *rpm*12:12
*** rwellum has joined #openstack-kolla12:12
sdakeits caused by changing dependencies in the host os12:12
sdakerather container os12:13
Jeffrey4lfor example? if so devstack will be failed more often.12:13
sdakeprobably the pip stuff needs to be uploaded as well for source installs?12:13
*** dciabrin has quit IRC12:13
sdakewhat do you think it is caused by12:13
Jeffrey4lsdake, there is a mirror in infra env. pip/centos repo/ ubuntu etc12:14
Jeffrey4li need to know which issue we are talking about.12:14
Jeffrey4lbut i am sure, lots of gate failure is caused by rpm dependency.12:14
Jeffrey4lis not* ( sorry)12:15
sdakeJeffrey4l i lost a msg there could you repeat12:15
Jeffrey4li need to know which issue we are talking about.     but i am sure, lots of gate failure are not caused by rpm dependency.12:16
sdakeJeffrey4l just a suggestion on how to generate reproducible builds12:16
sdakeoh right - this isnt' about gate failures - completely orthogonal12:16
sdakei htink in terms of priorities making gate reliable is higher priority12:17
Jeffrey4lwe need to know what is changed between gate and local env. and which change is necessary.12:17
sdakeonlly something i want to pass along from a discussion i had yesterday or the day before12:17
Jeffrey4lrpm dependency / repo shouldn't be the necessary.12:18
sdakeproblem: we are not offering a way for operators to reproduce the builds we generate in the gate.  We cannot reproduce the builds ourselves as the entire distro chain and all binaries used to build containers change constantly12:18
Jeffrey4lfor making the gate more reliable, we'd better capture more and more logs/env/variable from gate for analysis.  more failed only happen in gate, imo.12:19
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Fix designate prechecks  https://review.openstack.org/45218012:19
sdakethis isn't about reliability - this is about reproducibility12:19
sdakelet me make a simpler example12:20
Jeffrey4l" reproduce the builds we generate in the gate"  - hrm, are you not talking the success or failure. are you talking the exact rpm version in the images?12:20
sdakelets say i have a file called dothis.py on my hard disk12:20
sdakei run it12:20
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Fix designate prechecks  https://review.openstack.org/45218012:20
sdakethen later i edit it12:20
sdakei run it after editing12:20
sdakethe old version is long gone12:21
sdakehow do i get the results from the old dothis.py?12:21
Jeffrey4lno way if you are not using git.12:21
sdakeright12:21
sdakeand git does what?12:21
Jeffrey4lback and get the old dothis.py file12:22
sdakeright - git stores every version of the dothis.py file12:22
sdakeor atleast evey version you care to store12:22
sdakewe need the same thing for gate dependencies for tagged builds12:22
Jeffrey4lwhy?12:23
sdakewe can't reproduce our builds12:23
sdakea build that works today may not work in 3 months12:23
Jeffrey4lyou can get the same image from the running container or you old registry.12:23
sdakebecause the RPMS change or DEBs change or xyz changes12:23
sdakeneed archive of all the build dependencies12:23
Jeffrey4lyep rpms change.12:23
*** schwicht has joined #openstack-kolla12:23
Jeffrey4lyou can get the exact docker images. why you wanna build it again?12:24
sdakeif rpms change and there is no archive, how do you build an old version?12:24
sdakedocker images dont contain the rpms12:24
Jeffrey4li do not need build an old version.12:24
sdakeits a genreal requirement thta keeps popping up12:24
Jeffrey4lfirst of all, the old images should be saved in docker registry. you can get the old image from there.12:24
Jeffrey4lsecond, you can get the old images from the running container.( which is ran from the old images)12:25
Jeffrey4li can get the old images in two ways. why i need build it agains?12:25
sdakewhat if you wan tto change the container in some way (add a plugin) but keep all other things equal?12:26
mnaserhi guys12:26
mnaserhttp://paste.openstack.org/show/605048/ and http://paste.openstack.org/show/604927/12:26
sdakesup mnaser12:26
Jeffrey4lhey mnaser12:26
mnaserimages which failed to build12:26
mnaser(so far)12:26
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Fix designate prechecks  https://review.openstack.org/45218012:26
*** ccesario has quit IRC12:26
mnaserive reran the build twice and they failed in both of these scenarios.12:26
mnaserim building ubuntu source now but can i get an ok to push even if those failed?12:27
sdakemnaser binary doesn't have all things paackaged12:27
sdakemnaser some things fail normally12:27
sdakemnaser the logs could be more helpful about this point12:27
Jeffrey4lsdake, hrm, you can build a new set of images to upgrade ;)12:27
sdakemnaser the exceptions list is in the tests dir12:27
mnasersdake i figured, but when i saw some of them say "error" instead of "matched" .. it was a bit concerning12:28
mnaserokay, i'll double check that12:28
mnaseri guess the exception list when running kolla-build isnt shared12:28
Jeffrey4lmnaser, some images are failed for sure.12:28
Jeffrey4lyou may need check test_build.py file.12:28
*** signed8bit_Zzz is now known as signed8b_12:28
sdakemnaser ya that whole output thing is confusing12:28
sdakeit should be more straightforward12:28
sdakeThis container buildt; X"12:28
mnaserthe list should be shared as well, i'll see what we can do to clear that out12:28
sdakeThis container didn't build because (reason): X"12:28
mnaserJeffrey4l in other news ive made progress from your patch to run tempest smoke tests12:29
mnaserubuntu has this weird issue that is failing (but seems to be tempest related) because centos and oraclelinux both run ok12:30
Jeffrey4lmnaser, great.12:30
mnaserid show the logs but logs.openstack.org is not feeling good12:30
Jeffrey4lmnaser, do u have a patch link?12:31
mnaserJeffrey4l https://review.openstack.org/#/c/402122/ still a wip12:31
Jeffrey4laha, you re-used mine. let me check.12:31
mnaseroh and i made some tempest changes so we dont have to blacklist checks12:32
mnaseryep :)12:32
mnaserthe blacklist file is not used so ill have to remove that12:32
Jeffrey4lnice.12:32
*** schwicht has quit IRC12:32
*** schwicht_at_work has joined #openstack-kolla12:32
mnasersorry for overchecking most likely but i want ot make sure things are a-ok12:33
mnaserfor ubuntu source and binary, does this seem like it's reasonable to push? http://paste.openstack.org/show/605050/12:33
mnaserjust a short "hey this seems like its the right set of images with the right tags" is enough12:33
Jeffrey4lmnaser, let me check the test_build.py file.12:33
Jeffrey4l1sec12:33
mnaserthank you12:34
Jeffrey4lmnaser, for ubuntu + binary, all failed are expected except watcher.12:35
Jeffrey4lbut i think it is OK to push.12:35
Jeffrey4lfyi, this is another point which we should improve for build.py script.12:35
Jeffrey4lsome container will failed for sure.12:36
sbezverksdake: ping12:37
sdakesbezverk morning12:37
*** rwallner has joined #openstack-kolla12:37
sbezverksdake: good morning, we need to get 1.6.0 ps merged.12:37
sbezverkI am running recheck and almost all jobs are green12:38
sdakelooking12:38
sbezverkeven multinodes ones12:38
*** ccesario has joined #openstack-kolla12:38
sdakei saw something about post failures from infra - see subject ;)12:38
sdakesbezverk don't recheck until infra fixes logs.oo plz12:39
*** caoyuan has quit IRC12:39
mnaserubuntu kolla for 3.0.3 (latest newton release) are being pushed at the moment, should be done shortly12:39
sbezverksdake: sure, but still you can ack this ps12:40
sdakesbezverk i am12:40
sdakei had a question - not questioning your networking skills - just ramping up mine12:40
sdakehttps://review.openstack.org/#/c/451391/50/tests/bin/setup_canal.sh12:40
sdakeis 130.0 not in a /22?12:40
*** dmsimard|afk is now known as dmsimard12:41
sdakesbezverk looks good once inra disks are fixed and we can get a clean gate run12:42
sdakesbezverk the double kubeadm join needs to be looked at imo12:42
sdakesbezverk i am pretty sure tht awould confuse most software devs (as in they probably dont' test for a double registration and handle it improperly)12:43
sdakemay make the mulitnode jobs more reliable or may do nothing12:43
sbezverksdake: the gate is green, menaing the code is good and does what it is supposed to, we use it in other parts of the code too. I do not see any technical reason to change it..12:44
sdakesbezverk its redundant12:44
sdakesbezverk it doesn't need to be changed for this patch12:45
sdakei'd +2 the change but all the jobs are in POST_FAILURE12:45
sbezverksdake: just one12:45
mnaserwelp12:45
mnaseri just stopped the ubuntu source builds12:45
sbezverkcheck current state on zuul12:45
mnaseri mean centos source builds12:45
sdakei count 612:45
sbezverkhttp://status.openstack.org/zuul/12:45
mnasertarballs.o.o is affected by the outage :(12:46
sbezverk451391 in filter12:46
sdakehttps://review.openstack.org/#/c/45139112:46
sdakesbezverk lets wiat for logs.oo to be fixed and then get a proper recheck12:46
*** schwicht_at_work has quit IRC12:47
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Fix Haproxy reconfigure  https://review.openstack.org/45216612:48
*** signed8b_ is now known as signed8bit_Zzz12:48
sdake[05:40:45]  <sdake>is 130.0 not in a /22?12:48
sdakesbezverk ^^12:48
sbezverkwill answer in review12:49
sdakejust out of curiosity12:49
sdakewant ot learn a little more about networking12:49
sdakedon't understand how 13.0 worked prior based upon your answer on 132 change12:49
sdakerather 130.012:50
*** goldyfruit has joined #openstack-kolla12:51
*** dciabrin has joined #openstack-kolla12:54
targonFYI: I solved my dashboard problem in 4.0.0 by the following:12:57
targon$ sudo docker exec -it horizon bash12:57
targon(horizon)[root@oskollau01 /]# ln -s /var/lib/openstack-dashboard/static /usr/share/openstack-dashboard/static && exit12:57
targon$ sudo docker restart horizon && sudo docker ps | grep horizon12:57
targonThis is of cource ugly  hack, so still wondering why standard kolla-ansible install failed to insert correct Alias to dashboard.conf12:57
*** gkadam has quit IRC12:57
sbezverksdake: replied12:57
sdakesbezverk how did 130 work prior?12:58
sbezverksdake: no idea, why it is that  important? we usually do not investigate why somebody made a bug right? Also the explanation I provided is it not sufficient?13:00
sdakesbezverk i was just curious - no idea is a fine answer ;)13:00
sdakesbezverk the reason I want to know is i am developing a deployment doc13:01
sdakeand i want to get it right :)13:01
sdakesbezverk i must use the words "no idea" 5 or 6 times in the deployment guide13:02
rwellumsdake: I'm at the business end of the deployment documentation, with some networking questions. Just posted them.13:02
rwellumsdake: 'ni' is more efficient. :p13:02
sdakerwellum infra is busted atm - can't do any updates13:02
sdakei am hesitent to touch anything related to gerrit/etc as to not perturb the recovery13:03
sdakerwellum infra has asked for no submissions/rechecks until logs.oo is fixed13:03
*** caoyuan has joined #openstack-kolla13:03
sdakerwellum see subject set by infra team13:04
rwellumsdake: well they are mainly questions for clarity - they can be updated when things are working.13:04
sdakeJeffrey4l see targon 's workaround for horizon dashboard above13:05
rwellum"set 'ext_interface_name': name of the interface or bridge which will be used by neutron's provider interface" - how do we determine this?13:05
sdakeJeffrey4l i seem to recall we have gone around and around on this13:05
sdakerwellum no idea13:05
sdakerwellum sbezverk knows - he provided the answer to that question :)13:06
rwellum"set 'tunnel_interface': interface name used for connectivity between nodes in kubernetes cluster, in most of cases it matches the name of the kubernetes host management interface" - how do we determine this?13:06
*** esharao has joined #openstack-kolla13:06
rwellumRight.13:06
sdakerwellum on that second one, that should be your "eth0" or your main interface in globals.yaml13:07
*** schwicht has joined #openstack-kolla13:07
rwellumThanks - I'll suggest that as an update to the doc.13:07
sdakenetwork_interface in globals.yaml13:07
*** jtriley has joined #openstack-kolla13:08
sdakerwellum that is a 90% confidence guess :)13:08
sdakerwellum i think ext_interface_name shoudl be br-ex13:08
sdakerwellum how br-ex is created - unclear13:08
rwellumyeah that one you explain already13:08
sdakerwellum nah, i explained tunnel-interface13:09
sdake"host management interface" = network_interface in globals.yaml13:09
rwellumRight - sorry13:09
*** eanylin has quit IRC13:10
sdakerwellum its ok i was unclear - as its a bit early here and my brain hasn't booted13:10
*** gfidente has quit IRC13:10
rwellumnp. So the main unknown is ext_interface_name13:11
rwellumWhich is the bridge used by neutron's provider interface13:11
rwellum50-50 it has to be eth113:12
sbezverkrwellum: that is correct13:15
*** caoyuan_ has joined #openstack-kolla13:15
rwellumty sbezverk13:15
sbezverkrwellum: it is the interface you want to use for your instances external connectivity13:15
rwellumsdake: the two ext_* params are not referenced in your sample cloud.yaml13:16
*** lamt has joined #openstack-kolla13:17
*** caoyuan has quit IRC13:18
*** dave-mccowan has joined #openstack-kolla13:19
*** caoyuan_ has quit IRC13:19
*** caoyuan has joined #openstack-kolla13:20
sdakerwellum didn't say the doc was perfect :)  - leave a comment and i'll address as best as poisslbe :)13:20
sdakerwellum i have a cloud.yaml that works but is a big blob of stuff many of which are defaults13:20
*** signed8bit_Zzz is now known as signed8b_13:20
sdakekfox1111 had asked me to reduce it to the things that are not defaults13:20
sdakekfox1111 we are discovering what those deltas are - I think we have most of them discovered - although if sbezverk could take a look at the review it might be helpful :)13:21
rwellumsdake: I have added all this as comments.13:22
sdakesbezverk if you could review the following for correctness - it would be appreciated: https://review.openstack.org/#/c/447356/13:23
*** Deys has quit IRC13:23
sdakeI think i have everyone's comments collated as the editor of the document13:23
sdakealthough there have been alot of comments13:23
sdakeso I may have got some wrong :)13:23
*** caoyuan has quit IRC13:24
*** eanylin has joined #openstack-kolla13:27
rwellumFrom your sample cloud.yaml you dropped the openvswitch config section, which is where those two missing params would below. E.g.13:27
rwellumhttps://www.irccloud.com/pastebin/StZWy54b/13:27
rwellumI'll add this as a comment.13:28
*** caoyuan has joined #openstack-kolla13:30
sdakesbezverk note i parsed fungi's response to indicate that accessing zuul.openstack.org probably is slowing down the fsck of the disk13:34
sdakezuul.openstack.org reads logs from logs.oo vhost13:35
*** Deys has joined #openstack-kolla13:35
*** skramaja_ is now known as skramaja13:36
openstackgerritMark Goddard proposed openstack/kolla master: Use separate sudoers for ironic conductor modprobe  https://review.openstack.org/45220713:43
esharaoGM Guys..13:47
esharaohttp://paste.openstack.org/show/605069/13:48
esharaosdake got all the pods running13:48
*** gfidente has joined #openstack-kolla13:48
*** gfidente has quit IRC13:48
*** gfidente has joined #openstack-kolla13:48
sdakeesharao morning fine sir13:50
sdakeesharao which version of k8s areyou running13:50
*** manheim has quit IRC13:50
sdakeesharao nice job btw :)13:51
*** manheim has joined #openstack-kolla13:51
esharaokubeadm version13:51
esharaokubeadm version: version.Info{Major:"1", Minor:"6+", GitVersion:"v1.6.0-alpha.0.2074+a092d8e0f95f52", GitCommit:"a092d8e0f95f5200f7ae2cba45c75ab42da36537", GitTreeState:"clean", BuildDate:"2016-12-13T17:03:18Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"13:51
sdakeesharao your using the RPMs on fedorapeople then?13:51
esharaoi followed your guide13:51
esharaoyes..13:51
sdakecool13:51
*** Pavo has joined #openstack-kolla13:51
esharaoi had a comment on the change of order for installation of rpms13:51
sdakeany deviation from the guide?13:51
esharaoyes13:52
esharaoi had comments in revision 23 of your guide ;)13:52
sdakeesharao - just a heads up - I cannot update the guide until logs.oo is operational again13:52
esharaosure13:52
sdakelogs.oo = logs.openstack.org = broken with a corrupted disk - all openstack dev is blocked at present and I don't want to make the problem worse by submitting a review13:53
sdakeesharao did you record all deviations from the guide?13:53
esharaoyes...13:53
*** Serlex has quit IRC13:54
*** manheim has quit IRC13:55
*** manheim has joined #openstack-kolla13:55
*** Pavo has quit IRC13:57
esharaosdake: should i re-add my comments?14:01
*** manheim has quit IRC14:01
*** manheim has joined #openstack-kolla14:02
*** lucasxu has joined #openstack-kolla14:03
*** gfidente has quit IRC14:05
*** shashank_t_ has joined #openstack-kolla14:06
*** manheim has quit IRC14:06
*** Pavo has joined #openstack-kolla14:07
*** shashank_t_ has quit IRC14:07
*** shashank_t_ has joined #openstack-kolla14:08
*** shashank_t_ has quit IRC14:09
*** shashank_t_ has joined #openstack-kolla14:09
*** caoyuan has quit IRC14:10
*** caoyuan has joined #openstack-kolla14:11
sdake@esharao I guess if I missed them14:13
sdakeesharao there are so many comments on that review it is possible I have missed something14:14
*** nathharp has joined #openstack-kolla14:14
esharaook.. i will re-add them.. its mainly the order of installation of fedorerpms and i think rwellum had similar commnets on git am..14:14
sdakeesharao the latest review I will rev as soon as logs.oo is operational - and publish a new version14:14
*** Pavo has quit IRC14:14
esharaogot it14:14
sdakeesharao git am is no longer needed14:14
sdakeesharao rwellum fixed that problem :)14:15
esharaokool14:15
esharaoin general.. can we get some more explanation on the network ip's that folks can use and need to configure.. i feel that is always the confusing part14:16
esharaolike what should be the ip in the cloud.yaml and what should be in globals.yaml14:16
*** manheim has joined #openstack-kolla14:22
*** Pavo has joined #openstack-kolla14:23
*** lamt has quit IRC14:23
*** gfidente has joined #openstack-kolla14:23
*** gfidente has quit IRC14:23
*** gfidente has joined #openstack-kolla14:23
*** Pavo has quit IRC14:24
*** satyar has joined #openstack-kolla14:24
*** targon has quit IRC14:25
*** zhubingbing has joined #openstack-kolla14:26
*** shashank_t_ has quit IRC14:27
*** shashank_t_ has joined #openstack-kolla14:28
*** new2kolla has joined #openstack-kolla14:28
*** skramaja has quit IRC14:29
hrwtopic is still current?14:30
*** zhubingbing__ has joined #openstack-kolla14:32
*** jroll has quit IRC14:32
*** shashank_t_ has quit IRC14:32
*** Pavo has joined #openstack-kolla14:33
nathharpHi all - got an 8 node cluster running now, but running into some strange issues when deploying larger numbers of instances (~50-60).   Any following instances fail to be created properly, with errors in nova compute:14:33
nathharpBuildAbortException: Build of instance 42651c02-9991-4a01-a5cc-102ea91b4e5e aborted: Failed to allocate the network(s), not rescheduling.14:33
nathharpVirtualInterfaceCreateException: Virtual Interface creation failed14:34
*** jroll has joined #openstack-kolla14:34
nathharpany ideas?14:34
*** zhubingbing has quit IRC14:35
egonzaleznathharp, kolla-ansible or kolla-k8s?14:35
nathharpegonzalez - kolla-ansible14:35
egonzaleznathharp, any error in neutron logs? check quotas, nova had issues with quotas in the first ocata release14:36
nathharpegonzalez - nothing sticks out in the neutron logs, and I’ve set the quotas artificially high14:38
egonzaleznathharp, instances fails in all compute nodes or just in a few?14:39
nathharpegonzalez - with the last test, failed on all but one compute node14:39
nathharpegonzalez - but a previous test it failed on all14:40
nathharpegonzalez - but sometimes it succeeds without problem, and I could run up 120 instances flawlessly14:40
egonzaleznathharp, if you have enabled central logging, try searching for req-<ID> https://github.com/openstack/kolla-ansible/blob/master/doc/central-logging-guide.rst#example-using-kibana-to-diagnose-a-common-failure14:42
sdakehrw indeed14:42
egonzalezmaybe that can lead you to where is failing14:43
nathharpok - I’ll give that a go - I don’t have central logging on at the moment, but I can do14:43
nathharpon that note - is there any documentation for adding nodes or new services etc - ie when ‘deploy’ should be used vs ‘reconfigure’14:44
*** williamwang has joined #openstack-kolla14:44
egonzaleznathharp, bte, how are you creating that big amount of instances? heat?14:44
egonzalez*btw14:44
egonzaleznathharp, deploy14:45
nathharpjust via horizon  - creating identical instances booting from image and giving 60 as a quantity14:45
egonzaleznathharp, is failing when creating all  together or also individual instances?14:46
zhubingbing__hey guys14:48
zhubingbing__egonzalez hi14:48
nathharpegonzalez - very inconsistent, but generally will follow the pattern:  create 1 instance (works), create 5 instances (works), create 50 instances (works), delete all instances, create 50 instances (fails), create 1 instance (failes)14:48
*** jtriley has quit IRC14:52
*** Pavo has quit IRC14:54
*** manheim has quit IRC14:54
*** manheim has joined #openstack-kolla14:55
*** jtriley has joined #openstack-kolla14:55
*** egonzalez has quit IRC14:55
sdakefungi gave us green light to submit changes - but to avoid rechecks14:56
sdakehrw sbezverk ^^14:56
*** Deys has quit IRC14:56
sbezverksdake: before pushing any other reviews or changes, we need to merge the gate fix..14:58
sdakesbezverk i am submitting not pushing14:58
*** lamt has joined #openstack-kolla14:58
sdakesbezverk in any regard my change is a docs change14:58
sdakehrw  is working on the kolla repo14:59
sbezverkand I did not detect in fungi reply anything about re-checks14:59
sdakethat is right in the subject sbezverk14:59
zhubingbing__hi sdake14:59
SamYaplesbezverk: yea rechecks are fine too14:59
sdakelogs.openstack.org has corrupted disks, it's being repaired. Please avoid rechecking until this is fixed14:59
zhubingbing__sbezverk hi14:59
*** manheim has quit IRC14:59
sdakesup zhubingbing__14:59
sbezverkzhubingbing__: hey14:59
zhubingbing__jenkins look bad ;(15:00
*** jmccarthy has left #openstack-kolla15:00
sbezverkzhubingbing__: yeah infra needs to beefup a bit their servers, I suspect I have more horse power in my home lab ;)15:03
zhubingbing__roger15:03
*** klindgren__ has joined #openstack-kolla15:04
*** klindgren_ has quit IRC15:07
*** schwicht has quit IRC15:09
openstackgerritAlicja Kwasniewska proposed openstack/kolla-kubernetes master: Move heat config to kolla-kubernetes  https://review.openstack.org/45224315:09
*** eaguilar has joined #openstack-kolla15:10
*** shashank_t_ has joined #openstack-kolla15:12
*** new2openstack has joined #openstack-kolla15:12
*** new2openstack has quit IRC15:12
hrwsdake: I ended week. only rechecks are waiting15:12
*** manheim has joined #openstack-kolla15:13
* hrw off - have a nice weekend15:13
*** sayantan_ has joined #openstack-kolla15:24
*** adrian_otto has joined #openstack-kolla15:26
*** zhubingbing__ has quit IRC15:27
*** jaosorior has quit IRC15:28
*** lucasxu has quit IRC15:31
*** sayantan_ has quit IRC15:33
*** shashank_t_ has quit IRC15:34
*** sayantan_ has joined #openstack-kolla15:35
*** hrw has quit IRC15:35
*** hrw has joined #openstack-kolla15:37
*** pbandark has quit IRC15:37
kfox1111morning.15:37
kfox1111sbezverk: I think the last gate issue is due to placement getting enabled for 3.15:39
*** zhubingbing_ has joined #openstack-kolla15:41
sbezverkkfox1111: good morning, possibly, I cannot access logs any more due to issues with zuul and infra logging15:42
kfox1111sbezverk: last I got to look at it, it was a rabbit communication issue.15:42
kfox1111I figured it was a bum run, but hten it occurred to me this morning,15:42
kfox1111its probably trying to talk to the placement api now that the kolla-ansible patch went in.15:43
kfox1111just gotta add the placement stuff for 3 as well as 2 I think.15:44
sbezverkkfox1111:  and we do not start placement components for this job15:44
kfox1111right.15:44
kfox1111sorry. mean,t add 3 as well as 4.15:44
sbezverkkfox1111: as another ps?15:44
kfox1111probably can tack it on here real quick. as it is a gate fix too.15:45
kfox1111do you want to do it, or shoudl I?15:45
sbezverkkfox1111: sure, go ahead. I would suggest to do it in a separate ps, this way we can restore gates faster..15:46
*** pcaruana has quit IRC15:46
kfox1111gates are broken without the fix though.15:46
sbezverkkfox1111: cause right now all we need is working zuul15:46
sbezverkto restore 90% of gate jobs15:47
kfox1111depends I guess on how long it will take them to fix zuul.15:47
kfox1111I think we can get the fix in in the next 10 minutes.15:47
sbezverkkfox1111: ok15:47
kfox1111(for the 3.x issue)15:47
*** deadnull has joined #openstack-kolla15:48
kfox1111is it just the placement api? or do we need cell stuff too?15:49
deadnullIf I make a change to the globals.yml after a deply, do I need to run deploy, upgrade, or reconfigure?15:49
deadnulldeploy*15:49
sbezverkkfox1111: right for 3.X it is just placement15:51
kfox1111k.15:51
kfox1111so, I just need to copy the placement stuff from the iscsi job to the ceph one I think.15:52
*** shashank_t_ has joined #openstack-kolla15:52
*** lucasxu has joined #openstack-kolla15:55
openstackgerritAlicja Kwasniewska proposed openstack/kolla-kubernetes master: Move heat config to kolla-kubernetes  https://review.openstack.org/45224315:56
*** caoyuan has quit IRC15:57
*** srwilkers has quit IRC15:58
*** shashank_t_ has quit IRC15:58
openstackgerritKevin Fox proposed openstack/kolla-kubernetes master: Changes for kubernetes 1.6.0 upgrade  https://review.openstack.org/45139116:00
kfox1111sbezverk: k. this should do it I think.16:00
*** fooliouno has joined #openstack-kolla16:01
*** zhubingbing_ has quit IRC16:02
*** zhubingbing_ has joined #openstack-kolla16:12
*** new2kolla has quit IRC16:13
*** shashank_t_ has joined #openstack-kolla16:14
*** manheim has quit IRC16:14
*** nathharp has quit IRC16:16
sdakekfox1111 i admit i am not a shell wizard16:20
sdakegrep 'kubeadm join --token' /tmp/kubeout | awk '{print $4}' > /etc/kubernetes/token.txt16:20
sdakeis /tmp/kubeout the output of kubeadm join --token?16:20
rwellumesharao: I have some comments in the latest version of the deploy documentation on the networking in globals and cloud16:20
kfox1111look for the string 'kubeadm join --token' in the file /tmp/kubeout, and print out the 4th column.16:20
sdakeyup i got the awk part :)16:21
esharaogreat rwellum will take a look16:21
sdakethanks for answering thatquestion16:21
sdakehas anyone booted a vm yet?16:21
sdakeand had a ping out to the internets?16:21
esharaoeanylin did get a vm booted but running into issues with ping16:23
sdakemaybe rwellum 's changes fix that16:23
sdakeeanylin can you try rwellum's suggestions?16:23
eanylinsdake: In a meeting, ok, will take a look16:24
sdakeeanylin thanks - hopefully i'll have the review integrated prior to your meeting ocnclusion16:24
eanylinactually I wasnt able to ping the VM from the host machine16:24
eanylinor SSH to it16:24
sdakeeanylin did you add a floating ip?16:24
eanylinsdake: Yes, I did16:25
inc0how is my favorite community doing today?16:25
eanylinsdake: I got busy with work these 2 days, didnt really look into the ping/SSH issue16:25
sdakeinc0 TGIF16:25
sdakeeanylin thats ok eanylin your pioneering all the deployment guide work ;)16:26
sdakeI have trouble keeping up with all the comments as an editor :)16:26
sdakemuch less personally testing them16:26
sdakewhich I hane't done since wednesday16:26
sdakeinc0 after that goland course do you feel smarter?16:27
eanylinsdake: Glad I helped :)16:27
fooliounoI entered a comment on the deployment guide and it stays in a "draft" state. Is that how its supposed to be?16:27
inc0negative, stupider is more accurate16:27
inc0but I learned a lot so that's good16:27
sdakeinc0 yup i thought you'd say soething like that :)16:28
sdakeeanylin any help you can provide in the future is valued :)16:28
sdakeinc0 as soon as this kubenertes 1.6.0 change is passing its giongto need an ack from you and me16:28
sbezverkkfox1111: I do not recall if I had to use source, to get placement working..16:29
*** lucasxu has quit IRC16:29
inc0sdake: link plz16:29
eanylinsdake: Yeah, I will continue to help16:29
*** srwilkers has joined #openstack-kolla16:30
kfox1111sbezverk: oh. you think its broken in 3?16:31
sdakehttps://review.openstack.org/#/c/451391/16:31
*** satyar has quit IRC16:32
sbezverkkfox1111: there were a couple of breakage which forced me to use source, I just do not recall if placement was one of them16:32
sdakeinc0 add yourself as a review and keep an eye on that - we need to merge it as soon as infra is runningagain16:32
*** Pavo has joined #openstack-kolla16:32
kfox1111sbezverk: ah. ook. well, I guess we'll have to see.16:32
kfox1111worst case, we can just cut out the placement stuff from the nova config.16:32
sdakekfox1111 we need the placement api for 4.0.0 images16:33
sbezverkkfox1111: or switched to source ;)16:33
kfox1111sdake: yeah. it would be conditional.16:33
kfox1111sbezverk: -116:33
sdakekfox1111 wfm :)16:33
sdakeya we want to gate on binary and source16:33
kfox1111sdake: I got gate jobs for 4.x into zuul, so wenever the gate's stable, we can start making 4.x jobs.16:34
sdakekfox1111 nice16:34
sdakekfox1111 experimental or check jobs?16:35
*** rwallner has quit IRC16:35
sdakeok - sine we pretty much treat the gate as voting16:35
sdakewhy nto make it voting for all current check jobs?16:36
kfox1111sdake: experimental until they are written/stable.16:36
sdakewe had this discussion briefly before16:36
*** Pavo has quit IRC16:36
*** rwallner has joined #openstack-kolla16:36
sdakeand i heard conflicting reports on what the core reviewers wanted16:36
kfox1111sdake: you said you would submit that patch I think.16:36
sdakekfox1111 sbezverk said no to 2.0.0 images16:36
sdakeand i htink binary as well although i dont recall16:36
sdakei will submit the patch after i get clear consensus on what should be voting16:37
kfox1111k16:37
kfox1111mitaka's our most well tested stuff. and a lot of ops are still using it.16:37
kfox1111I think we should be user servey based until we hit 1.x.16:37
sdakeuser survey based - expand?16:38
fooliounokfox1111: Did you (or anyone you know on this channel) try bringing up odl on kolla-kubernetes16:38
kfox1111our focus is on making it easy for operators to adopt our stuff, right?16:38
kfox1111fooliouno: not yet.16:38
fooliounook .. was going to look into that.16:39
kfox1111sdake: as such, we should focus on what operator data is telling us from the user servey.16:39
sbezverkkfox1111: with 2.X images we have very limitted feature support and only ceph backend, so basically we re testing old stuff which is not even supported any more16:39
sdakekfox1111 are you suggesting people will migrate from bare metal to kubernetes?16:39
sbezverkkfox1111: I get your point of upgrade etc, but it should not be the main testing image16:40
sbezverkmaybe as experimental job for upgrade, yes, but main gate must bed 4.X16:40
*** mgoddard has quit IRC16:40
kfox1111sdake: yes. I know of at least 3 clouds planning on it.16:41
kfox1111sdake: fuel left a lot of clouds behind too.16:41
sdakekfox1111 is that a thing that can be done?16:41
sdakenewton is currently a branch in kolla repo16:42
kfox1111sdake: non trivial for sure, but I'm going to do it, as I think one of my coworkers is looking at it.16:42
sdake(kolla=containers)16:42
kfox1111sbezverk: I agree, we shoudl move stuff to 4. but that doesn't mean we shoulnt vote on 2.16:42
kfox1111operators hardly ever run N. thats what the user servey says.16:43
kfox1111they ofen run N-1, N-2,16:43
sdakekfox1111 once newton is unmaintained (things become EOLed in openstack) I have a tough time rationalizing keeping that in the gate16:43
kfox1111and if somethings just released, even N-3 for abit.16:43
sbezverkkfox1111: if having 2 and 4 do not extend gate job running time, then it should be ok16:43
sdakesbezverk they run almost in parallel16:44
kfox1111sbezverk: yeah. should be parallel deploys.16:44
sbezverkbecause the most of breakage will be on more recent versions16:44
kfox1111yeah.16:44
sdakei am more concerned about not being able to ship stable newton kolla container security updates16:44
kfox1111sdake: I think thats the operators concern.16:44
kfox1111operators do choose to run less then secure systems at times, due to nessesity.16:45
kfox1111we have mechanisms in place to mitigate the issues.16:45
kfox1111kolla though should try and provide as much as possible, up to date containers though.16:46
kfox1111brb16:46
sdakeok well lets separate the discussion of gating from what is shippable as a security update16:47
sdakewe dont know precisely when newton eols16:47
sdakewhen inc0 lets us know, we can have a wider discussion on that topic16:47
sdakefor the moment, are there negatives to making all the current check gates voting?16:47
* inc0 reading up16:48
inc0I think that will also resonate with "better tagging" discussion16:49
inc0and automatic infra push jobs16:49
inc0and frankly? I think this is spec-worthy16:50
sdakethink which is spec worthy16:50
sdakeall we are talking about is making votes gating16:50
inc0ok, I misunderstood then16:50
inc0votes gating or voting gates?;)16:51
* sdake run ragged by his children16:52
sdakeinc0 voting gates16:52
inc0in kk8s?16:52
sdakeyup16:52
inc0I'd say we need to move kk8s to master images then16:53
inc0and make sure they're stable16:53
sdakeas soon as we have dockerhub images that are master, we can start the process of making master checks16:54
inc0or use tarballs.o.o16:54
*** lucasxu has joined #openstack-kolla16:54
sdaketarballs.oo is not viable for master images16:55
sdake(without a whole lot of work)16:55
sdakeanyway lets stay focused on the gates we have16:55
sdakegating or not gating that is the question :)16:55
inc0to me master images are must have for voting gates16:56
inc0because if something goes wrong, we need to be able to fix stuff easily16:56
inc0that's 116:56
inc02 not whole lot of work16:57
inc0literally 3 commands + k8s config16:57
sdakeok well in the meantime while that master gating gets sorted out (by who?)16:57
inc0download tarball -> untar somewhere -> docker run registry -v /var/lib/regisstry:somewhere16:58
sdakethe question is which of the 2.0.0/3.0.0/4.0.0 gates should be voting16:58
inc0none, again either we don't mechanism to ship upgrades and our gates are worthless as operators won't use what's in dockerhub16:58
inc0(and I don't want to push change to kolla-k8s gates every time we release z)16:59
sdakeone change every 45 days is not that significant16:59
inc0or we gate on stale images and gates are worthless because real world scenerio will not use stale images16:59
inc0it's more than doing it properly in the first place16:59
sdakeinc0 i think we need to wait for kfox1111 to return17:00
sdakewhere we are currently is working on 4.0.0 gating17:00
sdakewhich is a necessary thing17:01
inc0great, but not voting17:01
sdakewhy not voting?17:01
inc0and temporary17:01
*** signed8b_ is now known as signed8bit_Zzz17:01
sdakethey are treated as voting17:01
inc0because if something goes wrong we have a lot of work to get gates back into order17:01
inc0treated is fine, blocked on infra is not17:01
sdakekolla-kubernetes has a different set of gating problems then either kolla or kollaansible17:01
inc0I'm well aware17:02
sdakewe have blocked on infra for the last 4 days waiting for kubernete 1.6 to get merged17:02
sdakemaybe 3 days17:02
inc0I'm also well aware how many times we had to hacky-upload something to dockerhub because kk8s needed it17:02
inc0that's outside of our control17:02
inc0images aren't17:02
inc0I think we need to get rid of this mix and match of images in kk8s asap17:03
sbezverkI think voting on binary is wrong, because in this case we rely our decision on vendor packaging17:03
sbezverkwhich we have no control over at all17:03
inc0that's why we don't have voting binary in kolla itself17:03
sbezverkwith source, at least we have access to openstack developers for this specific component17:04
sdakeinc0 that decision (no voting on binary in kolla) makes sense but is orthognoal to this discussion17:04
sbezverkinc0: agree, I think it makes sense17:04
inc0commenting on sbezverk's note17:04
sdakewhich hacky workarounds did we upload to dockerhub to fix the check gates?17:05
inc0so yes, I'm all for voting gates as long as they follow same methodology as all other deliverables17:05
sdakethe only example I can think of is to implement *experimental* gates17:05
*** srwilkers has quit IRC17:05
inc0from zen of python Special cases aren't special enough to break the rules.17:05
*** athomas has quit IRC17:06
rwellumHas anyone had this issue before?17:06
rwellumhttps://www.irccloud.com/pastebin/LFwtnU85/17:07
rwellumI do have that namespace created17:07
rwellumhttps://www.irccloud.com/pastebin/HWRAzoGW/17:07
sdakerwellum are you using kubernets 1.6.0?17:07
rwellumy17:07
sdake1.5.4 works for others17:08
sdakeare you really keen to get 1.6.0 kubernetes running?17:08
rwellumI got further with 1.6.0 than 1.5.417:09
sdakesbezverk hvae you seen rwellum 's bug during the kubernetes 1.6.0 changes?17:10
sdakerwellum note the guide doesn' thave the correct information to deploy kolla-kubernetes on 1.6.017:10
sdakeversion madness ftw :)17:11
rwellumYeah I have a mashup of your doc and sbezverk fixes17:11
rwellumIt's easy to try 1.5.4 again but I was making progress17:12
*** sambetts is now known as sambetts|afk17:12
rwellumsbezverk: has stepped out for a couple hrs fyi sdake17:12
sdakerwellum i'd suggest we hammer out 1.5.4 first, then we can do 1.6.0 next :)17:15
*** signed8bit_Zzz is now known as signed8b_17:16
rwellumAck sdake  - I thought with sbezverk work on the gate 1.6 was ready. esharao what have you been trying? You are further than me...17:16
esharaorwellum, i gave up on 1.6 got now.. went back to older one.. will try 1.6 over hte weekend17:17
*** shardy has quit IRC17:17
*** mliima__ has joined #openstack-kolla17:17
rwellumfair enough esharao17:18
*** mliima_ has quit IRC17:19
*** mgoddard has joined #openstack-kolla17:20
sdakerwellum we dont know if its ready or not as infra is busted17:21
openstackgerritMarcus Williams proposed openstack/kolla-ansible master: Add OpenDaylight role  https://review.openstack.org/41636717:22
kolla-slack<jascott1> o/17:28
*** shashank_t_ has quit IRC17:34
*** shashank_t_ has joined #openstack-kolla17:34
*** sayantan_ has quit IRC17:39
openstackgerritOpenStack Proposal Bot proposed openstack/kolla-kubernetes master: Updated from global requirements  https://review.openstack.org/45101817:41
*** new2kolla has joined #openstack-kolla17:43
openstackgerritMarcus Williams proposed openstack/kolla-ansible master: Split Openvswitch into own role  https://review.openstack.org/41679317:44
*** eaguilar has quit IRC17:45
*** MasterOfBugs has joined #openstack-kolla17:48
openstackgerritMarcus Williams proposed openstack/kolla-ansible master: Add OpenDaylight role  https://review.openstack.org/41636717:48
*** srwilkers has joined #openstack-kolla17:53
*** Pavo has joined #openstack-kolla17:54
*** Pavo has quit IRC17:55
*** zhubingbing_ has quit IRC17:57
*** unicell has joined #openstack-kolla17:58
*** schwicht has joined #openstack-kolla18:00
*** new2kolla_ has joined #openstack-kolla18:00
*** new2kolla has quit IRC18:01
*** bswartz has joined #openstack-kolla18:03
kfox1111back18:09
*** lucasxu has quit IRC18:12
*** mgoddard has quit IRC18:13
mnaserFYI 3.0.3 images for ubuntu binary and source have been published18:15
mnasercentos is still waiting becaus i cant build source images18:15
mnasertarballs.o.o is having issues because of the logs issues18:16
kfox1111inc0: I think we need to focus on getting image building in gate at the summit.18:16
*** Pavo has joined #openstack-kolla18:19
inc0kfox1111: please dont...18:19
inc0you want to build images in deploy gates? that'll raise complexity of gates a lot18:19
kfox1111inc0: no. release gates.18:19
inc0what's a release gate? what do you mean?18:20
kfox1111like, we build, test, and release to docker hub in a job.18:20
*** Pavo has quit IRC18:20
mnaserkfox1111 the work that i hope to finish regarding getting a publisher should help with this18:20
mnaserbut thats a lot of traffic to do for each commit18:20
kfox1111mnaser: yeah, but not per commimt. per release.18:21
mnaseroh yeah18:21
mnaserright now its done manually, but i started some work to give us the ability to do it per release18:21
kfox1111we tag 3.0.3, and it builds all the thigns. :)18:21
mnaserhttps://review.openstack.org/#/c/447524/18:21
kfox1111right. :)18:21
mnaserim letting the discussion brew18:21
mnaserand send a revision18:21
kfox1111yeah. that review. :)18:21
kfox1111we should work on it at the summit.18:21
mnaserim hoping people come to terms with the "but zuulv3 will solve this"18:21
mnaser(i dont want to be the person who asks "when will zuulv3 be out to know if we can justify this")18:21
mnaser:p18:21
kfox1111corner some infra folks. :)18:21
kfox1111right.18:22
kfox1111zuul3 has been promiced for a while.18:22
kfox1111though I think they have a version in place now. just not everythign migrated.18:22
mnaserthey do18:22
kfox1111so we might be able to start a new job type over there.18:22
mnaseri believe zuul self tests with zuulv318:22
kfox1111we could be earlier adopters potentially.18:22
kfox1111cool.18:22
mnaseryeah18:24
mnaseri dont mind that, as an experimental thing18:24
mnaserwe could setup a separate testing namespace for kolla for that job18:24
kfox1111:)18:25
*** jascott1_ has joined #openstack-kolla18:26
rwellumsdake: 1.5.x - mixed bag, quite a few of the helm charts succeeded, quite a few are not up yet, about 30m in. https://www.irccloud.com/pastebin/ekEIFgUH/18:29
kfox1111+18:34
sbezverkso what have you decided ;) ?18:35
*** sayantan_ has joined #openstack-kolla18:35
*** manheim has joined #openstack-kolla18:37
kfox1111sbezverk: who was that directed at?18:37
sbezverkkfox1111: to the universal wisdon ;)18:37
sbezverkwisdom sorry18:37
kfox1111ah. :)18:38
sbezverkkfox1111: I left when we were talking about binary voting, which I personally hate18:38
kfox1111oh. my random keystroke? :)18:38
kfox1111sbezverk: yeah. I feel the same way about source.18:38
kfox1111I feel more comfortable with redhat/ubuntu tested stuff, then upstream only tested stuff.18:39
sbezverkkfox1111: cool, then here is the scenario centos binary fails ubuntu binary broken, do we fail the change?18:39
kfox1111absolutely. :)18:39
kfox1111because our users will absolutely be trying it themselves, and we don't want to break them.18:39
sbezverkbut why? in thi case we can get stuck for long long time18:39
kfox1111then we better work with upstream for the binaries to fix it.18:40
kfox1111because thats what our users will need.18:40
sbezverkuntil centos fixes18:40
sbezverkits packaging18:40
kfox1111thats one reason we should tag our releases and keep them around.18:40
kfox1111if 3.0.3-1 works, and 3.0.3-2 breaks due to upstream package,18:40
sbezverkyeah, but it is not18:40
kfox1111we can keep using 3.0.3-1 until upstream fixes, and we cut a final, workable 3.0.3-2.18:41
*** manheim has quit IRC18:41
kfox1111I think most of the problems we've hit with binaries were lack of release procedure around building the containers.18:41
kfox1111that should be solvable.18:42
kfox1111allowing us to break against binaries though when users rely on binaries isn't a good plan.18:42
sbezverkkfox1111: well, our primary goal is develop and delay this process based on unrelated to our works things does not sound right to me. I would suggest to put it on vote..18:47
kfox1111ah. dev vs ops battle. :)18:48
kfox1111our primary goal is to produce something operators would like to use. ;)18:48
kfox1111further development is an important goal.18:48
sbezverkkfox1111: we should test binaries, but it should not be decisive especially if the same change fopr source passes18:48
kfox1111but not alienating the users is also another important goal.18:49
kfox1111non voting gates tend to regress into alwasy broken.18:49
kfox1111and non tested=broken.18:49
kfox1111not a good place to be.18:49
kfox1111caching known good binaries should mostly eliviate the issue.18:50
kfox1111as will, post 1.x, doing older versions in branches.18:50
kfox1111until 1.x though, I think its better to keep all the versions working/advancing together.18:50
kfox1111we need build pipelines too before we split them off.18:51
sbezverkkfox1111: I am ok with building more jobs for better testing since number does not extend job's running time, but I do not want to end up in situation, that the change I need to merge, does not getting merge for the reason that has absolutely nada with me :)18:53
kfox1111sbezverk: I understand that. very sympothetic to it.18:53
kfox1111but also sympotentic to operators not wanting broken stuff pushed to them all the time. :/18:54
kfox1111like the 1.6.0 feasco.18:54
kfox1111what we need to do is figure out a nice middle ground where the chances of binaries breaking things is minimal.18:55
kfox1111I think most issues we have hit were things not in the source build?18:55
kfox1111sorry... let me rephrase that...18:55
kfox1111issues were with specific builds of containers, not whether the source of openstack came from rpm or pip.18:55
kfox1111so we need more control over our own building of containers process.18:56
kfox1111which is what I've been pushing for.18:56
kfox1111right now its very very manual.18:57
kfox1111and very uncommon.18:58
sbezverkkfox1111: past showed that most of issue with container were wrong versions of software packages18:58
kfox1111we need frequent container building.18:58
kfox1111sbezverk: yeah. but again, stuff like libvirt. ddidn't matter if its centos-source or centos-binary?18:58
kfox1111the real issue is we're not frequiently updating the containers I think, to get binary bug fixes.18:58
sbezverkif repo has outdated version of rabbitmq and it breaks everything else, good luck, it could be days before it gets changed18:59
kfox1111why would it spontaniously break?18:59
kfox1111if the outdated container use to work, why would it suddenly stop working?18:59
kfox1111I'm maybe not following something.19:00
sbezverkkfox1111: because somebody else, let's say neuton pushed new rpm which is using 'new' rabbitmq feature19:00
*** lucasxu has joined #openstack-kolla19:00
kfox1111binary woudlnt do that. in fact, often source does.19:00
kfox1111cause binaries test the whole set together.19:00
kfox1111which is why I like them.19:00
sbezverkwell I have first hand experience19:01
kfox1111that specific senerio?19:01
sbezverkbinary centos ironic 3 worked19:01
sbezverkubuntu binary failed19:01
sdakerwellum im not sure - i need to head out for a bit - I'll work on getting that patch tested in my environment when i submit the new rev19:01
sbezverkbut both sources worked like a charm19:01
kfox1111I'd attribute that to an outdated 3 build, not binaries.19:01
kfox1111it wasn't source that fixed it,19:02
*** lucasxu has quit IRC19:02
kfox1111it was when it was built.19:02
sdakekfox1111 ubuntu binary is always a pile of garb19:02
sdakekfox1111 has been since day one19:02
kfox1111disagree. its worked pretty reliably in the gate.19:02
sdakethe core services work fine19:02
sdakeanything outside what ubuntu considers core (such as ironic) does not work well19:03
sdakewhereas source alwaysworks well with kolla19:03
kfox1111that may be. no experience with it.19:03
kfox1111if that proves to be the case with ubuntu in kolla-kubernetes, I would vote to not gate the binaries for that stuff.19:03
sdakeanyway you guys shoudl have a death match battle with inc0 and make a decision19:03
sdakeinc0 doens't want any voting gating at all19:03
sdakeso YMMV :)19:03
kfox1111heh.19:03
*** imcsk8 has quit IRC19:03
kfox1111if core ubuntu binaries are stable though, we should gate them.19:04
*** Pavo has joined #openstack-kolla19:04
*** Pavo has quit IRC19:04
kfox1111redhats binaries are stable. so lets gate them too.19:04
kfox1111the main issue is really stale containers.19:04
kfox1111lets fix that.19:04
inc0it's not that I don't want voting gates19:04
inc0I want voting based of master and stable branches19:05
inc0not dockerhub pulled mix19:05
kfox1111inc0: I agree with that, long term.19:05
inc0so yes, tarballs.o.o is an answer to that19:05
inc0and instead of spending time hacking some uploading script19:05
inc0let's just finish tarballs-pulled gates19:05
*** jascott1_ has quit IRC19:06
kfox1111inc0: yeah. was almost done with that.19:06
inc0exactl719:06
inc0it's not a big deal to get it working19:06
kfox1111was hoping to finish that, but 1.6 landed. :/19:06
inc0ofc19:06
kfox1111and that fixes the thing I've been squawking about. we need a way to refresh containers.19:06
kfox1111that gives us a mechanism for it.19:06
inc0exactly my point19:07
kfox1111tarballs.o.o has the most up to date, built and tested containers.19:07
inc0and local to nodepools so we're lowering bandwidth requirement of gates19:07
inc0and issues due to it19:07
kfox1111that woudl be nice.19:07
inc0that's how it works19:07
kfox1111to lower bandwidth, we need container fingerprinting too.19:08
inc0well in gates we need to pull whole stack anyway19:08
kfox1111yeah, but to upload updated containers, while minimizing bandwidth,19:08
kfox1111we need fingerprints.19:08
inc0let's not concern ourselves with that yet19:08
inc0we're uploading whole stack19:08
inc0all the time19:08
inc0not a huge deal19:09
kfox1111yeah, but sooner rather hten later.19:09
inc0I want dockerhup autopublish too19:09
kfox1111+119:09
kfox1111we should work on that at the summit.19:09
inc0just frankly? lower priority than stable gates for kolla k8s19:09
kfox1111+119:09
kfox1111the only reason we should start now on it thoguh,19:09
kfox1111is its wall clock expensive.19:10
inc0http://tarballs.openstack.org/kolla/images/ <- we have master and ocata19:10
kfox1111might take months of simmering to finish.19:10
openstackgerritMarcus Williams proposed openstack/kolla-ansible master: Add OpenDaylight role  https://review.openstack.org/41636719:10
inc0well good alternative (or even better) would be registry.openstack.org19:10
kfox1111inc0: http://tarballs.openstack.org/kolla-kubernetes/gate/containers/ <--- we have 2 and 3 also. ;)19:10
kfox1111tested by kolla-kubernetes.19:11
kfox1111along with a tested set of k8s containers. :)19:11
inc0can we narrow it down to single dir please19:11
inc0also I'd stick to ocata19:11
inc0with kolla-k8s19:11
kfox1111inc0: once cross repo gating is done, that may be possible.19:12
inc0with all the nova-placement stuff19:12
*** imcsk8 has joined #openstack-kolla19:12
kfox1111kolla's stuff isn't kolla-kubernetes tested.19:12
kfox1111the kolla-kubernetes/gate containers are fully tested.19:12
inc0yeah, that's importnant19:12
kfox1111-1 to just ocata.19:12
inc0but not kolla-tested ;)19:12
kfox1111inc, kolla tested too.19:12
kfox1111they come from kolla.19:12
inc0as in uploaded to dockerhub19:12
inc0but potentially stale19:13
kfox1111right. they are sourced from dockerhub.19:13
inc0that's my point19:13
kfox1111right.19:13
inc0to me stale = soft-broken19:13
kfox1111we need to smooth out the workflow quite a bit.19:13
kfox1111yeah, but less then hard broken which often comes out. :/19:13
inc0I'd start by adding non-voting gates on master and ocata tarballs19:13
inc0fix if need fixing19:13
inc0then add cross-repo to kolla and make gates voting19:13
kfox1111inc0: thats in progress.19:13
inc0this order of business19:14
kfox1111yup.19:14
inc0as for gates on newton we might just manually create+upload tarball for images19:14
inc0we're not backporting auto-upload code19:14
kfox1111so....19:15
inc0so...can we restart https://review.openstack.org/#/c/418550/19:15
inc0?19:15
kfox1111I'm mostly interested in older versions, as the user survey says most people are runningn older versions.19:15
kfox1111they do that, because its a pain to upgrade.19:15
inc0stable branches are most important19:15
kfox1111support, although with stale containers,19:15
kfox1111can be used as a stepping stone to migrate forward.19:15
inc0but changing underlay to k8s will be harder than upgrade..19:15
kfox1111to a supported container set.19:16
inc0or rather...equally as hard for worst case19:16
kfox1111yes. but a sideways upgrade from non k8s to k8s is way easier then an upgrade from not k8s to k8s, + a n+1 upgrade at the same time.19:16
Mech422inc0: got a minute to talk about the etcd/confd stuff ?19:17
kfox1111so continued support of mitaka for example, just with stale containers is a stepping stone to onboarding brownfield users.19:17
inc0a minute, need to drive my wife to airport soon19:17
Mech422inc0: Ohh! baching it!  Weekend Blowout at inc0's house!!19:17
inc0kfox1111: yeah...that being said, I'd rather onboard brownfield when we're better tested on greenfield19:17
* Mech422 lives the brownfield life.... :-(19:18
inc0brownfield will be good use case for kolla-ansible tbh19:18
kfox1111I know of 3 brownfield clouds thinking about kolla-kubernetes.19:18
inc0kfox1111: while you can handle migrating to kolla-k8s because you know this stuff in and out19:18
inc0well I'm not saying not a priority19:19
kfox1111yup. but operators are a resilient bunch.19:19
inc0I'm saying I'm afraid to push it19:19
inc0brownfield is much harder than greenfield19:19
kfox1111agreed.19:19
inc0and we didn't solve greenfield yet19:19
kfox1111but if we can't handle brownfield, we won't properlty handle greenfield either.19:19
inc0I'd be more comfortable to push kolla-ansible or kolla-your-config-mgmt19:19
kfox1111no other distro that focused on just greenfield has. :/19:19
Mech422inc0, kfox1111 so far, my experience with brownfield has been the politics are harder then the tech...19:20
kfox1111Mech422: yeah. agreed.19:20
inc0hehe ain't that true19:20
kfox1111brownfield is easier/harder in someways.19:20
kfox1111depends on the skill of the op.19:20
inc0we have brownfield notes for kolla-ansible I'm quite fond of19:20
inc0which can be reused for most part19:20
inc0but will require lots and lots of hacking on k8s19:21
kfox1111sure.19:21
kfox1111my focus on brownfield is for ops that built their own snowflakes at this point.19:21
Mech422kfox1111: special snowflak Mech reporting for duty!19:22
kfox1111if they know enough to do that, then they will be in pretty good shape.19:22
kfox1111:)19:22
inc0and you are assurance that we'll not break this use case:P19:22
kfox1111they don't nneed complex greenfield level orchestration tools that are buggy/incomplete.19:22
*** jascott1_ has joined #openstack-kolla19:22
kfox1111they need a solid base of k8s wrapped openstack building blocks.19:22
kfox1111to swithc out the ones they already have running.19:22
inc0it's data migration I'm worried about19:23
srwilkersafternoon19:24
inc0and state migration like iptables rules19:24
inc0hey Steve:)19:24
kfox1111inc0: those are solvable. probably much more easiliy solvable then orcestrating greenfield.19:24
inc0like...k8s will crap on iptables19:24
inc0will that break what's there already19:24
kfox1111if we don't have a db dump/restore option, we're hosed anyway.19:24
openstackgerritMarcus Williams proposed openstack/kolla-ansible master: Add OpenDaylight role  https://review.openstack.org/41636719:24
inc0yeah19:24
kfox1111iptables is a pain, but managable.19:25
inc0well we don't need tools build into kolla as long as we keep it documented tbh19:25
inc0ops know how to dump/restore dbs19:25
kfox1111I've had to hand roll iptables for pretty much every system I've deployed.19:25
kfox1111yeah.19:25
*** nathharp has joined #openstack-kolla19:26
kfox1111brownfield upgrades for snowflake systems should work today I think.19:26
kfox1111but is easiest if there is a sideways migration path.19:26
inc0yeah, in general19:26
kfox1111which is more probable if we keep mitaka working.19:26
inc0it's details that bites you19:26
kfox1111so far, there's no real reason to drop it. its not making forward progres stop.19:27
inc0so hold on, I'm not saying break it19:27
kfox1111yeah. devils always in the details. :)19:27
inc0let's just keep gates we have today for mitaka19:27
kfox1111+119:27
inc0and newton maybe19:27
kfox1111+119:27
inc0mitaka is closing to eol by the time we release19:27
kfox1111once we get feature completeness in all the objects at 1.x,19:27
inc0I'm saying not spend more time on it19:27
kfox1111then we start forking off stable branches, and dropping suport in trunk for all but trunk.19:28
inc0and do proper voting gates on tarballs on ocata+19:28
kfox1111I think the main effort left for 1.x in that space is, fluentd support, and prometheus support.19:28
kfox1111I agree, once the fluentd/prometheus support is in.19:29
kfox1111that should still work with older containers I think.19:29
inc0yeah, we won't backport them to stable branches19:29
inc0but you can install these few from dockerhub/tarballs19:29
kfox1111yeah. thats kind of the point I'm trying to make. once we make stable branches, we don't backport to them.19:30
kfox1111until then, I think we should not make stable branches until the k8s objects are feature complete.19:30
*** manheim has joined #openstack-kolla19:30
inc0stable branches in kolla-k8s or kolla?19:30
kfox1111kolla-k8s.19:30
inc0in kolla-k8s agree19:30
inc0on kolla proper, we already have stable19:30
inc0when I'm talking about stable branches I'm talking about kolla proper19:31
inc0anyway, gtg to airport, be back in few hrs19:31
kfox1111right.19:31
sbezverkinc0: wait19:31
kfox1111I'm only talking kolla-kubernetes.19:31
sbezverkcould you please ack gate ps?19:31
sbezverksince kfox1111 and myself cannot +2 it now19:32
sbezverkzuul looks better now so there is a chance it will pass this time19:32
kfox1111not sure if its needing more work or not...19:32
kfox1111true.19:32
kfox1111couldn't hurt to +2 it.19:32
sbezverkkfox1111: even if 3.X job still failing I think we need to merge it to unblock the gate19:33
kfox1111sbezverk: I agree. but we may need to revert to get to that state.19:33
kfox1111I think I got placement working, and tagged appropriately. but a slight chance it breaks something.19:34
sbezverkkfox1111: unless it is again binary vs source issue19:34
*** manheim has quit IRC19:35
kfox1111that could be too.19:35
kfox1111jsut not 100% sure I didn't typo an if in the ceph code.19:35
kfox1111until  Isee a gate run.19:35
kfox1111worst case, we could disable placement in the nova config on 3.x19:36
kfox1111then we would be operating like we use to.19:36
mnaserokay so19:38
mnaseran interesting problem regarding this (and binary)19:38
mnaseris the fact that packages are not pinned.19:38
mnaserbuilding kolla tag 3.0.3 now and in 3 months will not result in the same image19:38
mnaseri dont think thats right19:38
mnaserand that would eliminate much of the problems regarding any potential packages issues breaking gate19:38
kfox1111mnaser: yeah. thats a problem.19:39
kfox1111but a huge amount of effort to keep up with the pins.19:39
kfox1111I'd rather gate test individual builds constantlyh refreshing and pushing to dockerhub.19:39
kfox1111and have users pull from that most of the time.19:39
mnasercrazy idea: drop the whole kolla versions and have images get tagged by the openstack version which they are running for example19:40
kfox1111the exact artefacts used at the users site are then the same ones we validated worked with a full test cloud suite.19:40
kfox1111mnaser: yeah. I've agued for that.19:40
kfox1111but there are other versions too involved.19:40
mnaserbut thats a lot of work and the base layers cause an issue19:40
kfox1111like openssl version, etc.19:40
mnaserthere are some simple pinning plugins for yum19:40
mnaserbut the issue is keeping up with the releases19:40
mnaserwe could have something similar to openstack proposal bot19:41
kfox1111not really sure if it matters if the container is versioned off of mitaka = 2, or nova-api's mitaka version.19:41
kfox1111the imporant bit is having a revision number that increments every time a change is made.19:41
kfox1111so, centos-binary-nova-api:2.0.2-419:41
kfox1111    centos-binary-nova-api:2.0.2-519:41
kfox1111etc.19:41
kfox1111and we provide helm packages versioned similarly, that when a user upgrades, does a rolling upgrade to the new container.19:42
mnaseryeah that makes sense too19:42
mnaserits a very tricky subject19:42
kfox1111yeah.19:42
mnaserbut you still have to do some sort of pinning if you're going to let $user pin their own stuff19:42
kfox1111yeah. we can support that toda with helm values.19:42
* mnaser lives in kolla-ansible world19:43
kfox1111I'm more focused on making it so the user most of the ime doesn't have to. :)19:43
kfox1111ah.19:43
dmsimardmnaser: I was told containers would fix all of my problems19:43
kfox1111kolla-ansible might need a similar thing.19:43
dmsimardwe live in a world of lies19:43
kfox1111dmsimard: ;)19:43
dmsimard</friday>19:43
mnaserdocker run openstack19:43
mnaseramirite19:43
kfox1111heh. thats not a docker way to do things. ;)19:44
dmsimardright, it's docker run -it openstack /bin/bash19:45
kfox1111no, I mean, thats a very very fat container. :)19:46
kfox1111which is not how docker operates. :)19:46
dmsimardare you trying to say that openstack is fat19:46
kfox1111yes. yes I am. :)19:46
dmsimard¯\_(ツ)_/¯19:46
sbezverkdmsimard: do you have this sequence as copy and paste or you memorized it ;)19:47
sbezverk?19:47
dmsimardsbezverk: it's macro'ed :)19:47
dmsimardI have a few.19:47
sbezverkdmsimard: cool19:48
dmsimard<3 weechat19:48
dmsimardhttps://github.com/cmurphy/weechat-shrug/issues/119:48
mnaserlol19:49
dmsimardIt's a bit more ugly in python :) https://github.com/cmurphy/weechat-shrug/blob/master/shrug.py#L1019:49
kfox1111logs.o.o still broken. :/19:51
mnaseryeah they're running a big fsck on a giant 12tb volume kfox111119:51
mnasernot a fun time19:51
sbezverkmnaser: do you know any eta when it is going to be completed?19:52
mnasersbezverk i believe 3 hours ago it was at around 89%19:52
mnaserso i think end of day today... dont think much more stuff will go in today19:52
kfox1111wow.19:52
sbezverkmnaser: wow19:52
mnaserthis fsck has been running since like19:53
mnaser3am est19:53
mnaserso almost 12 hours now19:53
kfox1111ok. I'll go work on non kolla-kubernetes thigns I guess.19:53
mnaseryeah.. its going to be a little while before things clear out19:53
hawihi there. i have question regarding freezer - it gives me "Unable to get a job" error on ocata19:55
-openstackstatus- NOTICE: lists.openstack.org will be offline from 20:00 to 23:00 UTC for planned upgrade maintenance19:58
*** mliima__ has quit IRC20:02
kfox1111busy day for infra.20:03
sdakepoor folks20:05
*** shashank_t_ has quit IRC20:06
*** shashank_t_ has joined #openstack-kolla20:07
*** rhallisey has quit IRC20:09
kfox1111so... kubeadm has gate tests. they just weren't working. :/20:09
*** shashank_t_ has quit IRC20:12
openstackgerritSayantani Goswami proposed openstack/kolla master: [WIP] Added snap-telemetry container  https://review.openstack.org/44616420:15
*** shashank_t_ has joined #openstack-kolla20:16
*** srwilkers has quit IRC20:22
*** rwallner has quit IRC20:24
*** rwallner has joined #openstack-kolla20:24
*** jtriley has quit IRC20:26
jascott1_ugh my halycon vagrant has decided to give up on life20:29
kfox1111bummer.20:29
*** Pavo has joined #openstack-kolla20:29
jascott1_yeah idk worked monday..  sometimes it goes out to lunch and i just do a destroy/up and am back in business. now k8s is complaining about 8080 not accessible20:31
kfox1111did it go to k8s 1.6 on you?20:31
jascott1_nah i checked and its at 1.5.120:31
sbezverkjascott1_: it must be cosmic radiation, kubernetes, zuul and now your vagrant ;)20:32
jascott1_^this checks out20:32
kfox1111sbezverk: its been a horible week for system uptime.20:32
kfox1111had some  of my systems spontaniously explode too.20:32
kfox1111not sure whats going on. :)20:32
kfox1111planitary alinement, gremins, etc. :)20:33
sbezverk:)20:33
kfox1111I did notice jupiter's nice and brite in the sky right now. :)20:33
*** rwallner has quit IRC20:34
openstackgerritSayantani Goswami proposed openstack/kolla-ansible master: [WIP] Added playbooks for snap deployment  https://review.openstack.org/44616520:37
jascott1_all dem monolifs20:41
kfox1111:)20:41
jascott1_btw the golang class was great, hope I retained enough og it20:43
jascott1_og/of20:43
sbezverkkfox1111: wow, you can see planets during  the day time?!?!?20:50
sbezverkjascott1_: which one, I mean class?20:50
*** Pavo has quit IRC20:51
jascott1_sbezverk https://github.com/ardanlabs/gotraining20:51
jascott1_Bill Kennedy that wrote "Go in Action"20:51
jascott1_what I liked is that it wasn't a run thru of the syntax (that you can get anywhere) but more of a 'why they did it that way'20:53
sdakejascott1_ nice - i looked into go trianing at cisco - 15k per head20:53
sdakejascott1_ needless to say, I decided to pass20:53
jascott1_sdake you mean 1.5K ?20:53
sdakeno i mean 15k20:54
jascott1_our was approx 2K20:54
jascott1_per head20:54
sdakeyup20:54
sdake15k is rediculous20:54
sbezverkjascott1_: I would go for 2k training20:54
sdakei'm in the wrong business20:54
jascott1_weird.. maybe they have  minimum20:54
jascott1_sdake i hear ya20:54
sdakesbezverk buying 3 of these: http://www.cisco.com/c/dam/en/us/products/collateral/servers-unified-computing/ucs-c-series-rack-servers/c220m4-lff-spec-sheet.pdf20:55
sdakethoughts?20:55
sbezverk15k training was probably held in Hawaii or Bora-Bora20:55
jascott1_its some nice math when you look around and count the students20:55
jascott1_in your bedroom! stay in your pjs!20:55
sdakejascott1_ nobody really understands how expensive it is to run a business20:55
sdakeinsurance, attorneys, accountants, cleaning people, the list goes on20:56
jascott1_agree20:56
sbezverksdake: I have two of these very happy20:56
sdakesbezverk at your house or work provided20:56
sbezverkat my house work rpovided20:56
sbezverkprovided20:56
sdakehow did you hook that up?: )20:56
openstackgerritSayantani Goswami proposed openstack/kolla master: Install InfluxDB Plugin in Grafana  https://review.openstack.org/44662420:57
*** Pavo has joined #openstack-kolla20:57
sdakewhat i want is an employee discount on that gear20:57
sbezverkI could run about 15 servers lab, but then my electricity bill would go through the roof20:57
sdakesince, you know, I'm an EMPLOYEE20:57
sbezverkso I run 1 or 2 at the time20:57
*** rwallner has joined #openstack-kolla20:59
sdakesbezverk do you have a 2557 vic?20:59
openstackgerritSayantani Goswami proposed openstack/kolla master: Install InfluxDB Plugin in Grafana  https://review.openstack.org/44662420:59
sbezverkhmmm, never heard this part number20:59
sdakeits a nic on the board you mount21:00
sdakeiLOM21:00
sdakehave to buy this stuff myself - time to replace the minidells21:00
sdakeor atleast add to them21:00
jascott1_dang helm plugin 'template' doesnt really show computed values21:00
sdakesbezverk how is their volume level21:00
sbezverksdake: I keep them in the basement21:01
sdakesbezverk page 3 of that spec sheet - there are 8 nics on the thing21:01
sdakewhat are all those nics for?21:01
sdakenm i just got to page 5:)21:02
*** rwallner has quit IRC21:03
sbezverkyou got vic wrong21:03
*** nathharp has quit IRC21:03
sbezverkvin usually is 1227 or 138721:03
sbezverkvic I meant21:03
sdakesbezverk sorry 1227 is what i meant21:04
sdakei apparently need to get a RJ45 version to fit in with my 100$/port switch21:04
sdakecisco switches (nexus 9k) are 1k/port21:04
sbezverkyou should be careful with vic models21:04
sdakeplease expand :)21:04
sbezverkas they usually21:04
sbezverkuse sfp for connectors21:05
sdakeyup i know21:05
*** shashank_t_ has quit IRC21:05
sdakei found an rj45 version21:05
sdakeits 900 bucks21:05
sdakethe server is 180021:05
sdakerediculous the nic is 1/3rd the price of the server21:05
sdakeso how is the noise level when your in the basement?21:05
sdakeloud or quiet?21:06
sdakemy minidells are super loud21:06
sbezverkit is smart card, you can slice it on multiple logical nics21:06
sdakeyup i know21:06
sdakeup to 256 nics or hba21:06
sbezverkI can still hear it21:06
sbezverkbut very low21:06
sdakei can hear mine from the other side of the house21:06
sdakeand have no basement21:06
sdakeminidell is tight on space21:06
sdakeso hae to turn fans on max so my intel nics dont overheat21:07
sdakei think 2 of my servers are dead21:07
sdakedo you run cimc3.0?21:07
sbezverkthese are pizza box rack width, 1U and full lengthj21:07
sbezverkyes21:07
sbezverkuse 3.021:07
*** gfidente has quit IRC21:07
sdakeya 2.z has the terrible interface21:08
sdakefor the console21:08
sdakei've found this one: http://www.provantage.com/cisco-systems-ucs-spr-c220m4-bs1~7CSC8AUR.htm21:08
sdakewhich is SFF21:09
sdakeat 170021:09
sdaketrouble finding a LFF21:09
*** Pavo has quit IRC21:10
sbezverkhm, I thought sff is more difficult to find21:10
sdakethis is a good deal http://www.provantage.com/cisco-systems-ucs-spr-c220m4-bs2~7CSC8AUN.htm21:10
sdakewtb in lff21:11
sbezverk8 cores?!?! per processor, that sucks21:12
sdakeya - 16 hyperthreads = 32 cpus total21:13
sdakeplenty for me21:14
sdake(for persona luse)21:14
openstackgerritMohammed Naser proposed openstack/kolla stable/newton: Fix magnum [DEFAULT] configuration.  https://review.openstack.org/45232621:14
sdakesbezverk i am paying out of pocket21:14
sdakeI have a lab internally I can use already21:14
*** pramodrj07 has joined #openstack-kolla21:15
*** sayantan_ has quit IRC21:18
sbezverksdake: well you are rich man, you can afford it ;) I cannot, I need to rely on what my employer can give me :)21:21
*** esharao has quit IRC21:21
sdakesbezverk im just as broke as the rest of america :)21:21
sdake31" deep21:22
* sdake groans21:22
sbezverkit is nice server, but not great for house interrior design21:24
sbezverksome people might not appreciate it is technical beauty21:24
*** goldyfruit has quit IRC21:26
sdakesbezverk IDC :)21:27
sdakesbezverk re the SFF vs the LFF21:27
sdakesbezverk I can't seem to find an LFF at an acceptable price21:27
sdakeor an LFF at all21:28
sdakeI guess my SSDs are all SFF21:28
*** schwicht has quit IRC21:28
sdakewould you go with SFF or LFF?21:28
sbezverklff is more noisy21:31
sbezverkbut you can get more disk space with lff21:31
sbezverk4tb per lff21:31
sbezverksff I think can go up 2 tb but they are very expensive21:32
*** shashank_t_ has joined #openstack-kolla21:38
*** nathharp has joined #openstack-kolla21:40
*** nathharp has quit IRC21:41
Mech422sbezverk: if you want bargin stuff - I'm happy with my HP blades, and mostly happy with my Dell C6100 blades21:42
Mech422sbezverk: both clock in around $200/node for 16-32G RAM, and I think dual quad cores21:42
Mech422sbezverk: both are noiser then jet engine though21:43
sbezverkMech422: nah I am ok with my cisco ucs boxes, I just love them ;)21:43
Mech422sbezverk: ahh - I thought you guys were looking for new gear...21:43
sbezverkMech422: that was sdake21:43
Mech422sbezverk: sdake likes his 'quiet' stuff - I already tried to corrupt him :-)21:43
Mech422sbezverk: thing thats annoying me now is the cost of KVM cables21:44
Mech422sbezverk: you can get some NICE deals on Raritan IP KVMs on ebay atm21:44
Mech422but the cables cost a fortune21:44
sdakeMech422 with these servers you dont need any kvm cable at all21:44
sdakeMech422 the console is completey virtual21:44
sbezverksdake: you do, but they come with it21:45
sdakehtmlv521:45
sdakesbezverk you can't run the server without a keyboard/mouse/etc?21:45
sbezverksdake: you can, but you need first to setup IP for cimc access, after that you are ok21:46
sdakeok i can live with that21:46
sdakedoes cimc ip support DHCP?21:46
Mech422ahh - the IPMI consoles on mine are either crap (Dell) or too expensive to license (HP)21:46
sbezverksdake: most likely, I always use fixed ip21:46
sbezverksdake: how do you find out which ip it took ;) ??21:47
sdakesbezverk dns resolution via eero21:47
sbezverkunles you start browing dhcp server logs21:47
sdakei can assign a name to an ip address21:47
sdakeand then telnet xyz and my eero dns resolves for me to hte correct ip21:47
sdakesbezverk does the vic mandate a cisco switch?21:48
sdakeor will it work with any switch21:48
sbezverkI prefer to connect to the server, setup ip and then no headache21:48
sbezverksdake: nope but you need trunking capability on the switch21:49
sbezverkso what ever switch you use it must be 802.1q compatible21:49
-openstackstatus- NOTICE: The upgrade maintenance for lists.openstack.org has been completed and it is back online.21:50
*** schwicht has joined #openstack-kolla21:52
sdakesbezverk this is what I've got: https://www.amazon.com/NETGEAR-ProSAFE-10-Gigabit-Ethernet-XS708E-200NES/dp/B01ELW0QM4/ref=sr_1_7?ie=UTF8&qid=1490997028&sr=8-7&keywords=netgear%2B8%2Bport%2B10%2Bgigabit%2Bswitch&th=121:52
sdakeMind you, I am not using this switch in a commercial production setting, but in a home setting with a probably overly complicated network topology. That said, it replaced a much larger switch with extremely noisy fans with a unit that's barely bigger than the ports themselves, and draws a nominal 6 watts in normal use. All without losing the features I had to have, 802.3ad, 802.1q, etc.21:53
sdakein one of hte reviews21:53
sdakeso theoretially should work21:54
sbezverkyeah, looks like it should work since 802.1q is mentioned in specs21:54
sdakeannoying windows only utility21:58
sdakei have used this tool before21:58
mnaserman22:13
mnaserthis feels so dirty22:13
mnasermagnum had a missing dependency in ocata22:13
mnaserwhich openstack/rdo addressed22:13
mnaserand all im doing is running kolla-build and im getting a fixed image.  but i made no changes to kolla.22:13
mnasertagging them 4.0.0.1 but... this cant be right :<22:13
sbezverkjascott1_: still around?22:14
dmsimardmnaser: so the way I see that22:14
dmsimardmnaser: is that 4.0.0.1 is the kolla version, not the magnum version22:14
jascott1_sbezverk yes sir22:14
dmsimardmnaser: the magnum version is probably like 1a2b3c22:15
dmsimardyou can call your container 4.0.0.1-1a2b3c if you want22:15
mnaserdmsimard yeah.  in build time, we should detect the installed version and tag accordingly (but then it introduces the "how do i detect what to install" in kolla-ansible)22:15
sbezverkjascott1_: strange problem, getting this error : ./main.go:18: undefined: ssh.FixedHostKey22:15
dmsimardFWIW in RDO (trunk) I purposefully label the hash of the repository the container was built with22:16
sbezverkI do import "golang.org/x/crypto/ssh"22:16
sbezverkwhere the doc says it's defined22:16
sbezverkany clues/suggestions?22:16
jascott1_hmm22:16
mnaserdmsimard yeah.. this has to be addressed.  4.0.0 bits of kolla should always give you the same bits22:17
jascott1_could you pastebin?22:17
sbezverkthe error?22:17
mnasernot different images depending on the day/time its built22:17
dmsimardmnaser: I see where you're going but I'd argue the contrary22:17
dmsimardmnaser: 4.0.0 is the version of the Kolla docker files22:17
dmsimardnot the resulting version of the docker images22:17
mnaserdmsimard fair, then we shouldn't be tagging them in dockerhub as 4.0.022:18
dmsimardpoint taken22:18
jascott1_sbezverk dump the ssh to stdout to see whats in it22:18
dmsimardthe version of the docker image != the version of the docker file22:18
mnaseri agree with that 100% dmsimard .. so i guess how to decide whats the 'appropriate' tag22:18
dmsimardthe version of the docker image should be a derivative of the git sha1 (source) or rpm/dpkg version (binary) + kolla version22:18
dmsimardmnaser: probably something something pbr22:19
jascott1_sbezverk make sure you are looking at right docs for package, ive been looking at the wrong ones before with same name but different namespace22:19
jascott1_and you get 'wheres my method? etc'22:19
mnaserdmsimard and then the second (maybe not so fun part) is how to get kolla-ansible and co to find out what tag to use22:20
sbezverkjascott1_: http://paste.openstack.org/show/605112/22:20
sbezverkjascott1_: https://godoc.org/golang.org/x/crypto/ssh#FixedHostKey22:20
dmsimardmnaser: tag them latest and 4.0.0-1a2b3c22:20
dmsimardpeople who care use the pinned tag, people who don't use latest22:21
*** sayantan_ has joined #openstack-kolla22:21
dmsimardnot unlike pip install ansible=2.2.2.0 vs pip install ansible22:21
*** rwellum has quit IRC22:21
*** signed8b_ is now known as signed8bit_Zzz22:21
*** sayantan_ has quit IRC22:22
jascott1_sbezverk its a func, you are calling it?22:22
jascott1_its buried in the docs amongst types22:22
dmsimardbut anyway I'm not going to pretend I'm knowledgeable about this, I'm bad at docker :)22:22
*** sayantan_ has joined #openstack-kolla22:22
mnaserdmsimard that's actually good insight, i am going to give it a bit more thought22:22
dmsimardmnaser: but that's a bit what we're (trying) to do in RDO22:22
mnaserno this is really useful, the decoupling and the multiple tags to identify different releases, allowing a user to pin to specific images to specific releases (if they want) or stick to latest of a branch (master/ocata/newton)22:23
sbezverkjascott1_: it is called as callback                 HostKeyCallback: ssh.FixedHostKey(hostKey),22:23
dmsimardmnaser: so we have delorean trunk repository hashes, right, https://trunk.rdoproject.org/centos7/ed/de/edde55febc7ec2284e1f1475964da07d1ac127ab_1c6d669122:23
jascott1_sbeverk log that ssh object22:23
dmsimardmnaser: when we build the "latest" images, we recover that hash -- and the image is tagged with that hash and latest22:23
jascott1_%v22:23
dmsimardmnaser: https://hub.docker.com/r/rdoproject/centos-binary-swift-proxy-server/tags/22:24
dmsimard(Don't use those :D)22:24
sbezverkjascott1_: do you mean, commented out whole thing and just print out element of the object?22:24
mnaserdmsimard thats an interesting approach, maybe having different streams for branches (i.e. newton/ocata) and that seems like an ideal way of doing things22:25
mnaserat least in $rdo world22:25
dmsimardmnaser: we also add labels inside the container https://gist.github.com/dmsimard/585e8af3a676db666c333a88e8f07d71#file-patched_overrides-j2-L35-L3622:25
jascott1_import (  "log") then log.Fatal(ssh)22:25
jascott1_if that method isnt there then what have you got?22:25
*** signed8bit_Zzz is now known as signed8b_22:26
*** schwicht has quit IRC22:26
dmsimardmnaser: gotta go o/22:26
jascott1_oh sorry22:26
mnaserlater man, be safe out there, thanks for the talk dmsimard22:26
mnasersnow tonight :(22:26
sbezverkmnaser: where are you located?22:28
mnasermontreal canada sbezverk22:28
*** fooliouno has quit IRC22:28
*** williamwang has quit IRC22:28
sbezverkmnaser: me too, but I do not see any snow22:29
sbezverkat least yet22:29
mnasersbezverk oh no way22:29
mnaseri dont either but it looks like it's on its way22:29
mnaserpretty cool, didnt know this whole time you lived here :-P22:29
inc0back22:29
*** shashank_t_ has quit IRC22:29
sbezverkmnaser: right, me too22:30
*** shashank_t_ has joined #openstack-kolla22:30
mnasersbezverk were you at the openstack canada day by any chance?22:30
sbezverkmnaser: nope, by some reason I do not get any notification about local events22:31
mnaseroh bummer, i'll ping you if there's one coming up soon!22:31
mnasersome people expressed interest in hearing a talk about how we migrated to kolla so i might be doing a talk about that next meetu p22:32
sbezverkmnaser: sure, would appreciate it22:32
*** bjolo has quit IRC22:33
*** new2kolla_ has quit IRC22:33
*** shashank_t_ has quit IRC22:35
jascott1_sbezverk kfox1111 fyi they have changed some kubeadm params in 1.622:42
*** signed8b_ is now known as signed8bit_Zzz22:42
*** adrian_otto has quit IRC22:43
sbezverkjascott1_: yeah we know, we have already addressed it in new gate ps22:43
jascott1_halycon can get mismatched apparently22:44
sbezverkwe just cannot merge it because of dying zuul22:44
jascott1_i think its installing latest kubeadmin and fixed k8s22:44
*** adrian_otto has joined #openstack-kolla22:52
jascott1_sbezverk was that indeed the package you were looking for? :)23:06
sbezverkjascott1_: if you mean ssh, then yes23:07
jascott1_where was your method?23:07
jascott1_er.. Func23:07
*** goldyfruit has joined #openstack-kolla23:08
kfox1111sbezverk: now as in these days, not now as in this second. :)23:14
*** unicell has quit IRC23:14
*** adrian_otto has quit IRC23:15
sbezverkjascott1_: I figured out23:15
kfox1111logs back yet?23:16
sbezverkthat parameter exists only in go 1.823:16
jascott1_ah23:16
sbezverkbut I use go 1.7.5 here it is not defined23:16
jascott1_1.8 is stable iirc23:16
jascott1_yeah file that next to what i said about versions of the docs :)23:17
jascott1_the last two people that asked me a go related thing ended up being doc version mismatch related23:18
*** adrian_otto has joined #openstack-kolla23:18
*** manheim has joined #openstack-kolla23:22
*** adrian_otto has quit IRC23:25
*** manheim has quit IRC23:26
*** sayanta__ has joined #openstack-kolla23:30
*** sayantan_ has quit IRC23:30
*** caoyuan has joined #openstack-kolla23:39
*** deadnull has quit IRC23:44
jascott1_sbezverk know if 1.6 requires changes to CNI version?23:45
jascott1_sbezverk haha i found the issue on github and you were already there sharing the workaround23:47
kfox1111jascott1_: I believe so.23:48
kfox1111theres 0.5.x in the repo.23:48
*** unicell has joined #openstack-kolla23:52
kfox1111who is this coeki person? https://github.com/kubernetes/kubernetes/issues/43815#issuecomment-29086333023:53
jascott1_oh see you are on the thread there...23:53
jascott1_idk23:53
kfox1111yeah. github doesn't have much to say. drive by reviewer I guess.23:54
kfox1111I'm going to just ignore him... The clue bat's not working. :)23:54
jascott1_yeah i dont get his last comment23:55
jascott1_well thought i had halycon patched up until i hit this :/23:55
jascott1_sounds like music and beer time to me23:55
kfox1111:)23:55
kfox1111sounds like logs.o.o is a ways out still.23:56
kfox1111music and beer it is. :)23:57
jascott1_lol if you want to make the 3hr trek, beer is on me :)23:57
kfox1111yeah... thats a costly free beer.  :)23:58
kfox1111if it wasn't for the 3 hours though, would be happy to hang out.23:58
*** goldyfruit has quit IRC23:59
jascott1_no doubt next time you are in town we cant paint it any colour you like23:59

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