Friday, 2017-07-07

*** manheim has quit IRC00:00
*** ductta___ has quit IRC00:08
*** yangyapeng has quit IRC00:14
*** yangyapeng has joined #openstack-kolla00:14
*** Pavo has quit IRC00:14
*** jamesbenson has joined #openstack-kolla00:16
*** yangyapeng has quit IRC00:18
*** jamesbenson has quit IRC00:21
*** klindgren has quit IRC00:32
openstackgerritzhongshengping proposed openstack/kolla master: Switch to Cryptography over pycrypto  https://review.openstack.org/47370200:34
*** emccormick has quit IRC00:40
*** zhurong has joined #openstack-kolla00:43
*** vhosakot has quit IRC00:46
*** dixiaoli has joined #openstack-kolla00:53
*** dixiaoli has quit IRC00:55
*** jamesbenson has joined #openstack-kolla00:57
*** manheim has joined #openstack-kolla01:01
*** jamesbenson has quit IRC01:02
sdakekfox1111 ceph is fantastic until it eats your babies the first time01:03
*** tovin07_ has joined #openstack-kolla01:05
duonghqinc0, sdake morning guys, I'm sorry, last afternoon I forgot disconnect from work-pc01:12
larsks /buffer #rhos-dev01:16
*** caoyuan has joined #openstack-kolla01:16
larsksWhoops.01:16
*** yeyon has joined #openstack-kolla01:17
*** yangyapeng has joined #openstack-kolla01:20
yeyonhttps://docs.openstack.org/developer/kolla/ this web page does not exist01:21
yeyon?01:21
*** zhubingbing_ has joined #openstack-kolla01:21
*** yangyapeng has quit IRC01:21
*** yangyapeng has joined #openstack-kolla01:21
*** itlinux has joined #openstack-kolla01:23
*** itlinux has quit IRC01:23
*** lyang__ has joined #openstack-kolla01:24
*** itlinux has joined #openstack-kolla01:24
larsksyeyon: it does for me (it redirects to https://docs.openstack.org/kolla/latest/).  I think maybe the docs site has been underoing some sort of maintenance recently, because I've also hit a numer of unexpected 404 errors.01:26
dmsimardNeed a last +2 on a small review: https://review.openstack.org/#/c/479881/01:29
*** manheim has quit IRC01:35
*** unicell has quit IRC01:37
*** jamesbenson has joined #openstack-kolla01:39
Seyongyeyon: try it again it works for me. https://docs.openstack.org/kolla/latest/01:41
*** jamesbenson has quit IRC01:44
*** caowei has joined #openstack-kolla01:49
sdakequery kfox111101:51
sdakekfox1111 see PM plz01:51
sdakeduonghq can you ck dmsimard 's review plz01:52
dmsimardsdake: btw the use case01:52
sdakeyeyon  use the refresh button on your browser01:52
dmsimardsdake: tbh it's super awesome that kolla-build can build a million things super fast01:52
dmsimardsdake: I've also said before that troubleshooting that when *something* goes wrong usually sucks, a lot01:53
dmsimardsdake: I am trying a more granular approach while also trying to keep builds asynchronous and concurrent01:54
dmsimardBut I found an edge case where it would try to build a layer that was already built01:54
dmsimardThat granular approach would allow to easily profile and troubleshoot each individual image build easily01:54
sdakedmsimard you do know you can output the logs of each build separatey?01:55
sdakeeach container that is01:55
*** eaguilar has joined #openstack-kolla01:56
dmsimardsdake: been there done that, in our case things are in foreground and ran with ansible (thus available through ARA :p)01:57
dmsimardIt's something I'll need to consider if this doesn't work out though, but it seemed like a sensible and easy improvement01:57
sdakeok well i dont understand why yu need it - but it doesn't seem to cause any harm01:57
sdakewe are past the point where adding another API to the build is all that damaging01:57
dmsimardsdake: I'll share it if it works :)01:57
sdakedmsimard i guess if it doesn't you can revert the patch prior to release :)01:58
dmsimardsdake: bah, if you insist -- like I said, I still think this is useful. We have ephemeral build machines that are discarded after the containers are pushed to a docker registry. We aren't interested in even attempting to build layers that have already been built.01:59
duonghqsdake, dmsimard done, I just come back from meeting02:00
sdakeduonghq thanks02:03
duonghqhow about you these days?02:04
sdakeduonghq was very busy with internal work + had couple falls because of clumsiness02:04
sdakethe falls injured arms/hands, so took few weeks pto to recover02:04
duonghqoops, I'm sorry to hear that02:05
masberhi, I use kolla-ansible for deployment and I am trying to use ironic, where is the tftp location?02:05
sdakeduonghq shit happens02:06
sdakedmsimard i see that makes sense02:06
*** eaguilar has quit IRC02:07
*** eaguilar has joined #openstack-kolla02:08
*** jamesbenson has joined #openstack-kolla02:21
*** eaguilar has quit IRC02:22
*** jamesbenson has quit IRC02:25
*** goldyfruit has quit IRC02:33
*** goldyfruit has joined #openstack-kolla02:35
*** hieulq_ has joined #openstack-kolla02:52
*** lucasxu has joined #openstack-kolla02:53
*** hieulq_ has quit IRC02:58
*** hieulq_ has joined #openstack-kolla02:58
openstackgerritMerged openstack/kolla master: Add new --skip-existing option to kolla-build  https://review.openstack.org/47988102:58
*** hieulq_ has quit IRC02:59
*** lucasxu has quit IRC02:59
*** jamesbenson has joined #openstack-kolla03:02
spsuryamorning03:05
*** negronjl has quit IRC03:06
spsuryasdake: sorry to hear that :(03:06
sdakespsurya shit happens03:06
spsuryasdake: hope you are fine now03:06
sdake80-90%03:06
sdakecatching up on backlog03:06
spsuryagood to hear that03:06
*** jamesbenson has quit IRC03:07
*** hieulq_ has joined #openstack-kolla03:07
spsuryahmmm03:10
openstackgerritMerged openstack/kolla-ansible master: Adds NTP sync process to account for ceph time sync requirements. Removes precheck portion of NTP. Corrects for redhat Fixes typo  https://review.openstack.org/47760503:11
openstackgerritNoboru Iwamatsu proposed openstack/kolla-ansible master: change fernet-key repository permissions to 0750  https://review.openstack.org/48138803:14
openstackgerritjimmygc proposed openstack/kolla-ansible master: Add vSphere support to nova_compute  https://review.openstack.org/44952903:30
*** hieulq_ has quit IRC03:32
*** vhosakot has joined #openstack-kolla03:35
*** jamesbenson has joined #openstack-kolla03:44
*** MarginHu has joined #openstack-kolla03:47
*** jamesbenson has quit IRC03:48
*** jascott1 has joined #openstack-kolla03:55
*** goldyfruit has quit IRC04:03
*** unicell has joined #openstack-kolla04:25
*** jamesbenson has joined #openstack-kolla04:25
*** jamesbenson has quit IRC04:30
*** janki has joined #openstack-kolla04:35
openstackgerritjimmygc proposed openstack/kolla-ansible master: Add vmware DVS support to kolla-ansible  https://review.openstack.org/45927004:39
*** lyang__ has quit IRC04:42
openstackgerritjimmygc proposed openstack/kolla-ansible master: Add vmware DVS support to kolla-ansible  https://review.openstack.org/45927004:42
openstackgerritjimmygc proposed openstack/kolla-ansible master: Add vmware support to ceilometer  https://review.openstack.org/46284204:46
*** Seyong has quit IRC04:47
*** lyang__ has joined #openstack-kolla04:55
*** dixiaoli has joined #openstack-kolla04:56
openstackgerritjimmygc proposed openstack/kolla-ansible master: Fix fwaas options  https://review.openstack.org/46388205:00
*** jamesbenson has joined #openstack-kolla05:07
*** jamesbenson has quit IRC05:12
*** prateek has joined #openstack-kolla05:25
*** jamesbenson has joined #openstack-kolla05:28
*** jascott1 has quit IRC05:30
*** jascott1 has joined #openstack-kolla05:31
*** jamesbenson has quit IRC05:32
*** yangyape_ has joined #openstack-kolla05:33
*** yangyapeng has quit IRC05:35
*** mdnadeem has joined #openstack-kolla05:37
*** skramaja has joined #openstack-kolla05:47
*** jamesbenson has joined #openstack-kolla05:49
*** jamesbenson has quit IRC05:53
*** vhosakot has quit IRC05:55
openstackgerritMerged openstack/kolla-kubernetes master: Update deployment guide to use 1.6.4.  https://review.openstack.org/48121805:58
*** junbo has quit IRC06:01
*** jamesbenson has joined #openstack-kolla06:10
*** yangyape_ has quit IRC06:10
*** yangyapeng has joined #openstack-kolla06:11
*** yangyape_ has joined #openstack-kolla06:13
*** jamesbenson has quit IRC06:14
*** yangyapeng has quit IRC06:16
*** aolwas28 has quit IRC06:24
*** lpetrut has joined #openstack-kolla06:25
*** ajafo has quit IRC06:26
*** ajafo has joined #openstack-kolla06:26
*** yangyape_ has quit IRC06:30
*** MarginHu has quit IRC06:30
*** yangyapeng has joined #openstack-kolla06:30
*** jamesbenson has joined #openstack-kolla06:30
*** yangyapeng has quit IRC06:32
*** yangyapeng has joined #openstack-kolla06:33
*** yangyapeng has quit IRC06:33
*** yangyapeng has joined #openstack-kolla06:34
*** jamesbenson has quit IRC06:35
*** caowei has quit IRC06:36
*** caowei has joined #openstack-kolla06:36
*** mcnanci has joined #openstack-kolla06:36
*** thomasem_ has quit IRC06:36
*** sayantani01 has quit IRC06:38
*** cinerama has quit IRC06:38
*** hawi has quit IRC06:38
*** thomasem_ has joined #openstack-kolla06:38
openstackgerritTaeha Kim proposed openstack/kolla master: Fixed the invalid link in the kolla/image/build.py  https://review.openstack.org/48145706:38
*** aolwas28 has joined #openstack-kolla06:39
*** hawi has joined #openstack-kolla06:39
*** cinerama has joined #openstack-kolla06:40
*** sayantani01 has joined #openstack-kolla06:42
*** jbadiapa has quit IRC06:43
*** jamesbenson has joined #openstack-kolla06:51
duonghqanybody try to deploy multinode cluster and poweroff and start one of the nodes?06:55
*** jamesbenson has quit IRC06:56
*** jbadiapa has joined #openstack-kolla06:58
*** shardy has joined #openstack-kolla07:06
*** magicboiz has joined #openstack-kolla07:09
*** athomas has joined #openstack-kolla07:10
*** jamesbenson has joined #openstack-kolla07:12
*** lpetrut has quit IRC07:13
*** itlinux has quit IRC07:16
*** jamesbenson has quit IRC07:16
*** unicell1 has joined #openstack-kolla07:24
*** Seyong has joined #openstack-kolla07:25
*** unicell has quit IRC07:26
*** jamesbenson has joined #openstack-kolla07:33
*** reidrac_ has joined #openstack-kolla07:34
*** reidrac_ has quit IRC07:34
*** reidrac has joined #openstack-kolla07:35
*** manheim has joined #openstack-kolla07:37
*** jamesbenson has quit IRC07:37
*** egonzalez has joined #openstack-kolla07:38
duonghqegonzalez, hi07:39
*** manheim has quit IRC07:41
*** gfidente has joined #openstack-kolla07:41
*** manheim has joined #openstack-kolla07:41
*** manheim has joined #openstack-kolla07:41
*** serlex has joined #openstack-kolla07:48
*** manheim_ has joined #openstack-kolla07:50
*** jamesbenson has joined #openstack-kolla07:53
*** manheim has quit IRC07:54
*** jamesbenson has quit IRC07:58
openstackgerritEduardo Gonzalez proposed openstack/kolla master: Implement blazar Docker images  https://review.openstack.org/45474508:02
*** jascott1 has quit IRC08:06
*** jascott1 has joined #openstack-kolla08:08
openstackgerritEduardo Gonzalez proposed openstack/kolla-ansible master: Finish/fix neutron sfc service  https://review.openstack.org/46174508:14
openstackgerritJeffrey Zhang proposed openstack/kolla master: Fix wrong extra name for glance_store  https://review.openstack.org/48149308:14
*** jamesbenson has joined #openstack-kolla08:14
*** mgoddard_ has joined #openstack-kolla08:16
*** athomas has quit IRC08:16
openstackgerritYotaro Konishi proposed openstack/kolla-ansible master: Prevent unexpected abort when initializing fernet key authentication  https://review.openstack.org/47781808:17
*** athomas has joined #openstack-kolla08:17
*** jamesbenson has quit IRC08:18
*** david-lyle has quit IRC08:19
*** david-lyle has joined #openstack-kolla08:19
*** yangyap__ has joined #openstack-kolla08:25
*** yangyapeng has quit IRC08:26
*** YuYangWang has joined #openstack-kolla08:27
*** jascott1 has quit IRC08:31
*** jascott1 has joined #openstack-kolla08:32
*** jamesbenson has joined #openstack-kolla08:35
*** jascott1 has quit IRC08:36
openstackgerritzhouya proposed openstack/kolla-ansible master: Support assigning HA traffic to dedicated interface  https://review.openstack.org/48150308:37
*** jamesbenson has quit IRC08:39
openstackgerritzhouya proposed openstack/kolla-ansible master: Support assigning HA traffic to dedicated interface  https://review.openstack.org/48150308:40
*** dixiaoli has quit IRC08:45
*** dixiaoli has joined #openstack-kolla08:45
*** lyang__ has quit IRC08:45
*** jamesbenson has joined #openstack-kolla08:56
*** mandre_away is now known as mandre08:56
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible master: Support cinder backend for glance  https://review.openstack.org/48151708:56
*** tvignaud has quit IRC08:57
*** jamesbenson has quit IRC09:00
*** lyang__ has joined #openstack-kolla09:01
*** tvignaud has joined #openstack-kolla09:11
*** lpetrut has joined #openstack-kolla09:14
*** jamesbenson has joined #openstack-kolla09:16
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible stable/ocata: Fix the incompatible of docker-py 2.0.0  https://review.openstack.org/48153709:18
*** yangyapeng has joined #openstack-kolla09:19
*** jamesbenson has quit IRC09:21
openstackgerritMerged openstack/kolla-ansible master: Standardize Keystone domain variables  https://review.openstack.org/47928709:21
*** yangyap__ has quit IRC09:22
openstackgerritzhouya proposed openstack/kolla-ansible master: Support assigning HA traffic to dedicated interface  https://review.openstack.org/48150309:24
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible master: Use latest docker engine in gate  https://review.openstack.org/48021209:25
*** yeyon has quit IRC09:27
*** YuYangWang has quit IRC09:27
*** jamesbenson has joined #openstack-kolla09:37
*** jamesbenson has quit IRC09:42
*** dixiaoli_ has joined #openstack-kolla09:42
*** dixiaoli_ has quit IRC09:42
*** YuYangWang has joined #openstack-kolla09:42
*** YuYangWang has quit IRC09:43
*** YuYangWang has joined #openstack-kolla09:44
*** dixiaoli has quit IRC09:46
*** openstackgerrit has quit IRC09:48
*** caoyuan has quit IRC10:05
*** sambetts|afk is now known as sambetts10:06
*** egonzalez has quit IRC10:07
*** tovin07_ has quit IRC10:07
*** egonzalez has joined #openstack-kolla10:09
*** caowei has quit IRC10:11
*** duonghq has quit IRC10:14
*** mgoddard_ has quit IRC10:19
*** iniazi_ has joined #openstack-kolla10:43
*** iniazi has quit IRC10:46
*** zhurong has quit IRC10:46
*** mgoddard_ has joined #openstack-kolla10:51
*** pbourke has quit IRC10:52
*** pbourke has joined #openstack-kolla10:54
manheim_hi, I have an ansible question11:03
manheim_http://paste.ubuntu.com/25038692/11:03
manheim_can I use a conditional set in the globals.yml file to install or nor an item from a with_items?11:04
manheim_I don't want to create a separate task only for this11:04
*** yangyapeng has quit IRC11:44
*** pcaruana has joined #openstack-kolla11:49
*** rwallner has joined #openstack-kolla11:51
*** rwallner has quit IRC11:51
*** rwallner has joined #openstack-kolla11:52
*** rhallisey has joined #openstack-kolla11:53
*** rwsu has quit IRC12:05
*** rwsu has joined #openstack-kolla12:12
*** shardy has quit IRC12:18
*** schwicht has joined #openstack-kolla12:20
*** emccormick has joined #openstack-kolla12:25
*** ansmith has joined #openstack-kolla12:26
*** hrw has quit IRC12:26
*** skramaja has quit IRC12:29
*** schwicht has quit IRC12:30
*** hrw has joined #openstack-kolla12:32
*** goldyfruit has joined #openstack-kolla12:35
*** awiddersheim has quit IRC12:36
*** awiddersheim has joined #openstack-kolla12:36
*** YuYangWang has quit IRC12:45
*** schwicht has joined #openstack-kolla12:49
*** schwicht has quit IRC12:51
*** goldyfruit has quit IRC12:56
*** goldyfruit has joined #openstack-kolla12:57
*** goldyfruit has quit IRC12:58
*** ducttape_ has joined #openstack-kolla12:59
*** lucasxu has joined #openstack-kolla12:59
*** goldyfruit has joined #openstack-kolla13:01
*** ducttape_ has quit IRC13:01
*** janki has quit IRC13:03
*** schwicht has joined #openstack-kolla13:06
*** mdnadeem has quit IRC13:14
*** mdnadeem has joined #openstack-kolla13:14
*** zhurong has joined #openstack-kolla13:23
*** magicboiz has quit IRC13:24
egonzalezmanheim_, yep you can but is somekind ugly http://paste.openstack.org/show/614770/13:27
manheim_isee13:28
manheim_one other question13:28
manheim_so in juju for example, nova-compute services run directly on the bare metal compute host, not in containers13:29
manheim_but the nova kvm services for nova all run in containers13:29
manheim_even libvirt13:29
manheim_how does this work?13:29
egonzalezno idea about juju13:30
sbezverkegonzalez : qq when I try to build the image I get error  :base:manifest unknown: manifest unknown13:31
manheim_it's just an example, it's a deployer that puts OS services in LXDs13:31
manheim_but for some services you have to put them on localhost13:31
manheim_like cinder-volumes, nova-comute etc13:32
sbezverkegonzalez any idea what I do wrong?13:32
egonzalezsbezverk, never seen that error, is a new image o failing building existing images?13:32
sbezverkegonzalez : new image13:33
sbezverkegonzalez : here is my command line: ./build.py --base centos --base-tag 4.0.1 --type source --namespace kolla targetd13:34
sbezverkit used to work in the past13:35
sbezverkegonzalez just checked and even old image is failing to build with the same error. :( I guess something got broken with my kolla setup13:37
manheim_i mean how can you run libvirt in a container and not on baremetal node13:37
egonzalezsbezverk, are you able to do a direct pull from any image in dockerhub?13:39
egonzalezor, is the parent image pulling from a hash instead of a tag?13:40
sbezverkegonzalez : yep, just pulled centos:latest13:40
*** jtriley has joined #openstack-kolla13:40
egonzalezmanheim_, libvirt container shares processes with the baremetal, VMs really runs in the host13:41
sbezverkegonzalez after removing --base-tag it started working..13:41
egonzalezsbezverk, base-tag is the centos tag to use, not kolla tag13:44
sbezverkegonzalez : cool, thanks for clarification13:45
egonzalez ./build.py --base centos --tag 4.0.1 --base-tag <CENTOS_TAG(latest,7.3) --type source --namespace kolla targetd13:45
egonzalezsbezverk, ^^ that would be the command to build the image, if want to use centos:7 not need to use base-tag because will use 7 by default13:46
sbezverkegonzalez thanks!13:50
*** eaguilar has joined #openstack-kolla13:56
*** vhosakot has joined #openstack-kolla14:03
*** hongbin has joined #openstack-kolla14:08
*** jtriley has quit IRC14:12
*** jtriley has joined #openstack-kolla14:14
*** jtriley has quit IRC14:14
*** prateek has quit IRC14:14
*** itlinux has joined #openstack-kolla14:19
*** pradk has joined #openstack-kolla14:22
*** zhurong has quit IRC14:26
*** jtriley has joined #openstack-kolla14:26
*** lrensing has joined #openstack-kolla14:27
*** mdnadeem has quit IRC14:31
*** duonghq has joined #openstack-kolla14:31
duonghqevening guys14:31
*** mdnadeem has joined #openstack-kolla14:32
*** mdnadeem has quit IRC14:32
*** jamesbenson has joined #openstack-kolla14:34
manheim_hello14:39
*** ducttape_ has joined #openstack-kolla14:39
vhosakotinc0: rwellum ping14:42
vhosakotduonghq: I'll create an etherpad for the rolling upgrade talk and send it to you soon for feedback.14:42
inc0I'm here vhosakot14:43
inc0good morning14:43
vhosakotinc0: rwellum:  I think we need to separate the DOckerHub+gate talk and custom images talk as two separate talks so we double our probability of getting accepted :)14:43
vhosakotinc0: morning!14:43
inc0vhosakot: that doesn't work this way14:44
vhosakotinc0: :)14:44
*** YuYangWang has joined #openstack-kolla14:44
vhosakotinc0: rwellum does the custom images have anything to do with gates?  isn't it a buildtime thing/tweak?14:44
inc0I was thinking of doing talk about images in general14:45
inc0when to download and when to build14:45
inc0downloading - how it works and why and when14:45
inc0building - how it works and why and when14:45
vhosakotinc0: ah I see, general talk about images (including customizing them and publishing to DocerkHUb from gate).. got it14:45
*** iniazi has joined #openstack-kolla14:45
inc0do you agree?14:46
rwellumWell - sort of. There's building them, and then running them?14:46
rwellumdeploying14:46
vhosakotinc0: yes, if the talk is about the "usability of kolla images in the best possible way for ops", then, yes, I agree, we can combine DockerHub+gate and custom images, and both are about building and running....14:47
inc0and I think it's going to be useful talk14:47
vhosakotsure, one talk (DockerHub publisher) emphasizes on a strong/intelligent gate, while the other (custom images) has nothing to do with upstream gates and involves custom gating in any company.14:48
vhosakotso, both topics are about building, running, gating...14:49
*** iniazi_ has quit IRC14:49
vhosakotdo you agree inc0 rwellum ^^^ ?14:49
inc0yeah14:49
inc0we can explain how to build CI like ours, as ideas14:49
inc0what is our current coverage14:50
vhosakotrwellum: yes, the DockerHub talk totally involves running images... in fact, it is all about the easiness/comfort of running tested/golden images without worrying about building images from scratch.14:50
rwellumSo little confused, vhosakot you proposing one talk or two?14:51
inc0one talk rwellum14:51
vhosakotrwellum: I first thought two, now I'm thinking one.. what do you think?14:51
inc0you me and Vikram about images (dockerhub and build your own, including customizations)14:51
rwellum I just think there's a lot of content there for 45m talk.14:51
inc0and vhosakot we could have second talk with duonghq about upgrades14:51
rwellumBut basically yes.14:51
vhosakotyeah, all three of us of course...14:52
inc0rwellum: we don't need to get to technical details on talk14:52
vhosakotyeah, to cover them in 45 mins is what I'm thinking, plus a demo?14:52
rwellumThats what I asked yesterday - does this include a demo?14:52
inc0I think it's better to explain ideas and point to correct places to find more information14:52
vhosakotI've seen speakers play pre-recorded demo as a video..14:52
inc0not sure about demo, we could build one image and show full customizations14:53
inc0or do full build, record, and cut "watching grass grow" in the middle14:53
*** itlinux has quit IRC14:53
vhosakotDockerHub is about awesome gates, while custom images is about awesome buildtime-tweak, both could take like 20+ mins each may be?14:53
vhosakotinc0: right, we can cut the boring ("growing beard grow part")14:54
inc0we'll figure it out as we go vhosakot14:54
rwellumSo the title I proposed yesterday is probably not accurate:  OpenStack Deployment using Custom/Home Grown Kolla Containers - with Ansible and Kubernetes14:54
inc0right now we just need titile and abstract14:54
vhosakotrwellum: yes, we need a title to cover the DockerHub publisher topic too14:55
jamesbensonThanks inc0 and duonghq for the +2's and merge :-)14:55
inc0hehe welcome to official club of Kolla commiters jamesbenson ;)14:55
inc0next step - do reviews;)14:55
jamesbensonthe cherrypick is still on the cutting board whenever you get around to it ;-)14:57
jamesbensonreviews coming up. ;-)14:57
vhosakotrwellum: a company can use the DockerHub publisher idea to push tested/golden images to an internal registry and the devs in the company can just pull custom tested/golden images and deploy without deploying.. so, this is how we can overlap/form a segway between talks.14:57
vhosakotrwellum: tested/golden custome images to an internal registry, I meant14:57
rwellumvhosakot: yes agreed14:57
inc0Images to your imagination. Advanced image usage in Kolla14:58
vhosakotinc0: rwellum: the key here is when and build and push, once pushed, things are self-explanatory/easy.14:58
inc0(not sure about english, so native speakers feel free to correct me please)14:58
inc0I think key messages is *when* you should download and when to build14:59
inc0explain what our "golden images" are and what they are not14:59
inc0and then we can finish up with building one image, something quick, with a lot of customizations15:00
vhosakotinc0: rwellum; by combining the two talks, both topics kinda complement each other... DockerHub publisher topic can touch about doing it for customized images, and the custom image topic can touch about doing it with in internal regitry so devs do not have to build custom images everyday.15:00
inc0yeah I like that15:00
rwellumAgreed15:00
rwellumTo both15:01
rwellumI get this a lot when I talk about Kolla btw - what IS a kolla image? Where do they come from? How to I get them and customize? Etc.15:01
vhosakotthe idea is basically: "I don't have to build" (DockerHub topic) and "I can use custom/interal images" (custom image topic)15:01
vhosakotrwellum: I think the answer for "Where do they come from? How to I get them" shuold be found in the DockerHub topic15:03
*** lucasxu has quit IRC15:04
*** egonzalez has quit IRC15:04
vhosakotI bet ops want to do both - 1) not build images.. 2) use custom images.... we just need to find a nice segway and compliment the two topics and show how both topics can totally do the other using Kolla.15:04
*** duonghq has quit IRC15:05
*** gfidente has quit IRC15:05
*** gfidente has joined #openstack-kolla15:05
rwellumYeah agreed.15:09
*** duonghq has joined #openstack-kolla15:09
vhosakotinc0: rwellum: good chat, now we need a title :)15:09
rwelluminc0: is kolla image tag 4.0.0 - newton?15:09
inc0ocata rwellum15:10
rwellumso 3.x?15:10
inc03x is newton, but it's eol already15:10
inc0sorry15:10
inc0I take that back15:10
inc0newton is not EOL15:10
*** sudipto has joined #openstack-kolla15:10
*** sudipto_ has joined #openstack-kolla15:10
vhosakotyeah 4.0.0 is Ocata15:11
rwellummitaka is - but 2.x?15:11
rwellumIs this documented?15:11
vhosakotyes, Liberty was 1.1.0 I know15:11
rwellumWhat I;ve found online seems wrong.15:11
vhosakotrwellum: https://releases.openstack.org/teams/kolla.html15:14
vhosakotrwellum: Mitaka (2.x) - https://docs.openstack.org/releasenotes/kolla/mitaka.html15:14
duonghqvhosakot, sorry, I'm late, my bad15:15
inc0no you're not;)15:15
rwellumty vhosakot15:16
inc0duonghq: so, upgrade talk?15:16
inc0didn't you have talk like that in Boston?15:16
duonghqnot yet :)15:16
duonghqI have some thought: the gate: it's more like Kolla's workflow for image building and CI15:17
duonghqsmt like that15:17
duonghqI mean the topic vhosakot talked above15:17
duonghqI mean we share our ideas on maintaining a set of Docker image15:17
inc0I see, 4 presenters is a bit too much and I thought you wanted to do upgrade talk:(15:17
inc0sorry15:18
vhosakotinc0: duonghq: upgrade is totally away/opposite of building images.  I'd say upgrade is all about runtime, rolling, in-place activity with min downtime, and how Kolla can do this.15:18
duonghqya, upgrade is totally different thing15:18
inc0yeah, I agree vhosakot and we can do upgrade talk too15:18
inc0as separate15:18
inc0btw duonghq are you going to openstack days china?15:18
rwellumUpgrade - ansible and k8s?15:18
vhosakotduonghq, inc0 and I can do it... upgrade talk was duonghq's idea right?15:18
duonghqya, I hope that I can join in upgrade talk in Sydney15:18
duonghqrwellum, ansible first15:19
inc0I'd focus on ansible and I'd focus on Ocata->Pike15:19
duonghqinc0, no, I'm Vietnamese :)15:19
vhosakotrwellum: mostly Kolla-ansible... k8s upgrade is kinda indepedant/differnet than kolla-ansible's upgrade playbook/arch.15:19
inc0I know, but it's closer than Australia;)15:19
inc0just asking, lots of Kolla will be present there afaik15:20
duonghqhmm, not even know that, it's not official event from OpenStack foundation so I cannot get fund for go to that15:20
rwellumAre we testing Pike? :)15:20
inc0we will, extensively15:21
inc0and hopefully in gate before summit << looking at Vikram >>15:21
inc0;)15:21
duonghqso, inc0  and vhosakot will have topic about gating and CI?15:21
inc0anyway, we can do full deep dive, explain all the issues with upgrading O -> P15:22
vhosakotrwellum: k8s' upgrade (kubectl rolling-update <image name> --image=image:<new version/tag>) is a k8s feature and we do not plan to cover that... the upgrade talk is how kolla-ansible's ansible playbook can use used to upgrade Kolla images (minor-to-minor, major-to-major release) in a rolling fashion.15:22
duonghqI'm not sure I've catched up with you guys :P15:22
vhosakotyes, I"m ready to start upgrade gate inc0 :)15:22
*** eaguilar has quit IRC15:22
inc0duonghq: no, I was thinking we could put CI for upgrdaes into upgrade talk15:22
inc0duonghq: ok, so to summarize15:22
inc0we'll have 2 talks:15:22
vhosakotinc0: duonghq yes, testing upgrades in CI is nice.15:22
inc01. me, vhosakot and rwellum - images, dockerhub pushing, building custom images etc15:23
*** eaguilar has joined #openstack-kolla15:23
inc02. duonghq vhosakot and me - upgrades, deep dive into O->P, upgrade gate architecture etc15:23
duonghqawesome15:24
inc0I think if we promise to talk about O->P and promise to explain all the special cases for this release, operators will join en masse15:24
inc0and at the end of talk we'll make live demo of upgrade15:24
vhosakotI'd talk about what upgrade does - stop existing containers, back them up, pull next release, start them, migrate DB, usual OpenSTack upgrade path15:24
rwellum+115:24
duonghqya, if we can make sure it will be done successfully, we need really big room15:25
inc0vhosakot: that too15:25
inc0we usually get big rooms:)15:25
duonghqvhosakot, I hope that I can make rolling upgrade asap, so we can bring up to the demo15:25
inc0yeah would be cool15:26
inc0ok, I think that's a good plan guys15:26
duonghqI've done some work on ansible strategy but some work need to be done15:26
vhosakotduonghq: let's do it, I can work with you.15:26
duonghqvhosakot, https://review.openstack.org/#/c/480081/ -> it's my proposal15:26
rwellumhttps://etherpad.openstack.org/p/kolla-sydney-custom-repo-talk - feel free to hack this up guys.15:26
duonghqrwellum, nice, can I join in idea drafting?15:27
rwellumYes please15:27
duonghqvhosakot, I think the strategy is almost done, but something happen so the restart container handler is not triggered15:27
vhosakotduonghq: I see, I'll test it, thanks for the pointer.15:28
inc0brb15:29
duonghqvhosakot, it'd be better if I add restarting percentage to the strategy, but I'm kept on busy on figure out why handler is not invoked15:29
vhosakotif not a rolling upgrade, customers must do some pre-upgrade day-0 stuff... like stop their apps in VMs, back them up, backup VMs' volumes, shutdown VMs.15:30
duonghqya, cold upgrade is always an option15:30
duonghqbtw, did you test bring an cluster up by Kolla, and restart some node(s) in the cluster?15:31
duonghqbrb in ~10mins15:31
duonghq:P15:31
*** jascott1 has joined #openstack-kolla15:33
*** manheim_ has quit IRC15:33
vhosakotduonghq: I'll first manually run the keystone upgrade play in the review, and then post comments.15:33
*** manheim has joined #openstack-kolla15:34
* duonghq back 15:35
duonghqvhosakot, thanks15:35
vhosakotthe last time I ran upgrade, some nova VMs went to error state after the new nova-compute container was restarted, I'll check it15:37
inc0back15:37
*** jascott1 has quit IRC15:38
duonghqI got trouble even with running cluster15:38
duonghqjust restart one node and it's kicked out from cluster when backed15:38
inc0vhosakot rwellum "Images that fit your imagination. Deep dive into container images in Kolla"15:38
inc0thoughts? ^:)15:38
*** manheim has quit IRC15:38
vhosakotinc0: rwellum: that's nice... how about "Gate-love gone wild".... lol15:40
vhosakotI'll also think some titles15:40
duonghqinc0, how do you think slim down image on this cycle, or it should take lower priority than rolling upgrade in this cycle?15:40
inc0duonghq: for me upgrades are almost top priority always, that's what ops care about15:41
inc0and cycle ends soon15:41
vhosakotduonghq: I've seen you mention slim images in a meeting too.. what is a slim image basically?  aren't kolla images already slim per-service with a big parent layer with common packages?15:41
inc0however we can meet up at Denver and have PTG discussion about slim images15:41
inc0vhosakot: slim == smaller15:41
inc0I want slim images, I just don't have good idea how to do it in a way that will be significant15:42
rwellum"Kolla Image Wizardry: Pull, Use, Customize, - imagination is your only limit."15:42
duonghqinc0, ya, if I can catch up with you guys on Denver15:42
vhosakotinc0: I see nothing unwanted in a kolla image to be removed to make it smaller, is there?15:42
inc0and doing arch change to gain insignificant optmization isn't worth it imo15:42
duonghqvhosakot, it's more likely image refactoring subtopic15:43
inc0duonghq: PTG is way more interesting to us than summit15:43
inc0us = devs15:43
duonghqyes, I'm waiting for TSP result15:43
vhosakotwhat'd be removed to make a kolla image slimmer?15:45
rwellumduonghq: https://en.wikipedia.org/wiki/Trisodium_phosphate (TSP)15:45
inc0vhosakot: thing is removing (rm -rf stuff) will have opposite result15:45
inc0because images have CoW layers15:46
duonghqrwellum,  lol15:46
inc0how much of it do you need to get to PTG?15:46
vhosakotwell, I used the "removed" incorrectly... how can the size of a kolla image be reduced/slimmed down?15:46
inc0there are few ideas15:47
inc01. docker --squash15:47
duonghqinc0,  I'm not even estimate that, ticket, flight, hotel....15:47
inc0yeah it's expensive15:47
inc0as for hotel, I'm volunteering to share my room with someone15:48
inc0but that's for later15:48
inc0duonghq: did you try travel support program?15:48
duonghqinc0, I applied for it, but still waiting for result15:49
*** itlinux has joined #openstack-kolla15:49
inc0ahh...TSP15:49
inc0that's what tsp stands for;)15:49
vhosakotinc0: I see, remove intermediate stuff using compress/squash so registry size is less... I'm getting the idea15:49
inc0but that's slow and experimental15:50
duonghqgood news is it seem that I can use my Visa for Denver15:50
inc0we can use lightweight distro instead of ubuntu/centos15:50
vhosakotinc0: should we unsquash/uncomress before deploying Kolla?15:50
inc0no need vhosakot15:50
vhosakotyeah, a light base is alwasy a good option15:50
rwelluminc0: possibly unrelated - but you've seen the LOCI effort right? Any lessons we can learn there?15:50
inc0I've seen it15:51
vhosakotyeah, I'm thinking of LOCI now too15:51
duonghqrwellum, what is LOCI?15:51
inc0SamYaple made it15:51
inc0and portdirect15:51
sdakeinc0 newton eoling is happening soon15:51
inc0loci uses single layer so they can rm -rf unneeded things like apt cache after image build15:52
inc0but we use layers in our images15:52
inc0so that's not feasable without --squash15:52
sdakei think the big delta reallly between loci and kolla isn't the image flatness - it is the ABI15:52
duonghqah, okay15:53
rwellumABI?15:53
sdakeyes kolla contianers have an ABI for communication with them15:53
inc0kolla images has some kolla-specific stuff in it15:53
sdakeloci does not15:53
inc0like set_configs or startup scripts15:53
sdakerwellum let me explain15:53
inc0LOCI only has source code (no binary) and minimum required packages to run it15:54
*** yangyapeng has joined #openstack-kolla15:54
sdakerwellum https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/neutron/templates/neutron-server.json.j215:54
vhosakotsdake: ABI = Application Binary INterface?15:54
sdakevhosakot ya - i guess it may be considered an API - although its pretty binary :)15:54
sdakeapi/abi - call it what you want15:55
sdakeits a commonized industry standardized interface to openstack containers15:55
vhosakotI see.. cool :) basically, an interface between two binary programs at runtime15:55
sdakerwellum if you look at that file, that is fed into every container15:55
sdakeand does all the magic of securing and configuring the container15:56
sdakethis makes kolla containers idempotent15:56
sdakeas well as provides other benefits15:56
rwellumidempotent but not immutable15:56
sdakewrong15:57
sdakeits also immutable15:57
sdakethe config files are loaded once15:57
sdakeand then not loaded again15:57
sdakeonce the container is started - its contents dont change15:57
rwellumInteresting...15:57
portdirectits not immutable i think - as i would define that at somthing whos contents never change15:57
sdakeunless using COPY_ALWAYS - whcih is of course the operator's choice15:57
portdirectso you can/could run with a read only rootfs15:58
*** mgoddard_ has quit IRC15:58
sdakeya - running with a read only root fs should be on kolla's roadmap15:59
sdakehowever, the fact that kolla does not run with a read only rootfs does nto make it not immutable15:59
portdirectno - but its a pretty good acid test of how far towards being immutable it is :)16:00
vhosakotno container is read-only is it.. app will write something (logs for example) to container at some point?16:00
sdakevhosakot no - they write them to either docker volumes or kubernetes pvcs16:00
sdakevhosakot it is possible to implement read only containers16:00
portdirector to sdout16:00
vhosakotI can wrote an app to touch a file in a container without volumes, can;t I sdake?16:01
portdirectsdake: is on point here16:01
sdakeportdirect - right - more addressing the persistent storage aspect ;)16:01
sdakevhosakot containers may be launched with read only filesystems16:01
vhosakotdoesn't immutability come into picture when the container _restarts_ as everything not in a volume is lost and container goes back to known golden state.16:02
sdakedocker run -d --read-only --tmpfs /run --tmpfs /tmp IMAGE16:02
vhosakotsdake: read-only container with read-only fs means, read-only app?16:02
sdakevhosakot no - it means putting your persistent data on PVCs in the kubernetes case or docker volumes in the docker case16:03
vhosakotright, use volumes to write, or do read-only stuff if no volumes..16:03
sdakerwellum anyway back on the original point rwellum16:03
portdirectand your temp files in to somting like the tmpfs vols created in sdakes example above16:03
sdakerwellum that config file instructs the container how to bheave16:03
sdakei am not sure if kubernetes has read only volume support yet or not16:04
inc0images are RO by default;) containers are instantiated, therefore they're not16:04
sdakerather container support16:04
sdakea read only instantion o a container image is the ultimate security tool16:05
inc0still, we can get some of LOCI stuff in once --squash becomes stable16:05
sdakeit didn't become a feature unitl 1.1016:05
inc0it will make builds longer, but containers will be smaller16:06
sdakeor it would have likely meandered its way into the code base16:06
inc0however *all* of containers will consume more space due to lack of sharing16:06
sdakeinc0 also large compute farms will take longer to launch16:07
vhosakothttps://github.com/openstack/loci16:07
inc0with our env not that much longer - sharing of layers is our ally in this case16:07
sdakeinc0 i mean with squash ;)16:07
inc0a yeah16:08
sdakesquash was integrated at the most inoopportune time16:08
sdake1.13 feature16:08
sdake1.13 = dead to me16:08
vhosakotinc0: sdake so, LOCI does not have kolla_start concept and no startup/entrypoint mechanism?16:08
inc0it's in experimental branch16:08
inc0so as far as I'm concenrned, it's not implemented yet16:08
sdakevhosakot its been awhile since i've looked at the code - but as of 3-4 moonths ago that is correct16:08
inc0no vhosakot, idea behind LOCI is to overlay all your custom stuff on top of LOCI images16:09
inc0which are supposed to just give you binaries16:09
*** manheim has joined #openstack-kolla16:09
sdakethe key thing here is - kolla doesn''t really have custom stuff16:09
inc0so for us to use LOCI in kolla-ansible for example we'd still need to create image FROM loci/nova:latest -> ADD extended start16:09
sdakewe have stuff that implements our abi16:10
inc0sdake: we have, just not ansible-specific16:10
vhosakotright, kolla bakes extended start into the image16:10
inc0and our abi is custom;)16:10
sdakeinc0 i'd say industry standard is a better way of putting it :)16:10
inc0if industry means people who use kolla images;)16:10
inc0still, I think it's great value16:11
inc0and you could simulate something like this on k8s by mounting configmaps with scritps in them16:11
inc0but I personally think it's very ugly, even if k8s folk do it16:11
vhosakotusing Kolla is easier than LOCI right since ops must figure out the overlay part (proper base, extended start/entrypoint)?16:11
*** jascott1 has joined #openstack-kolla16:12
kfox1111+1. injecting python/shell scripts via configmaps is hackuy.16:12
kfox1111hacky.16:12
kfox1111should be used very sparingly, not as the base of your whole archetecture.16:13
inc0it does put some bootstrapping logic into container, LOCI doesn't, LOCI on the other hand is significantly smaller and images don't share anything so they're independent from each othere16:13
inc0tradeoffs16:13
inc0we had this discussion on PTG16:13
kfox1111you can still have kolla containers all b e independent of each other and still have a well defined entrypoint.16:13
*** manheim has quit IRC16:14
kfox1111there is no tradeoff there.16:14
inc0yeah16:14
inc0well, size is tradeoff16:14
inc0want independent - it's going to be big16:14
vhosakotI like Kolla images, because it comes with the startup mechanism (kolla_start, extended start) baked into the image, all I need to do is carry the right config16:14
inc0want shared layers - it's not independent16:14
vhosakotimagine figuring out the entrypoint/extended start for neutron as ops16:14
kfox1111I think they are papering over "share nothing".16:14
kfox1111it still shares a common base image.16:14
kfox1111so you still have dependeies in the tree. just fewer.16:15
*** openstackgerrit has joined #openstack-kolla16:16
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169016:16
sdakekfox1111 see pm16:16
*** klindgren has joined #openstack-kolla16:17
vhosakotas an ops guy treating a kolla container as my "unit of deployment", I prefer kolla as it starts an OpenStack service when I start a kolla container... as ops, I don;t want to figure out the overlay part (what to start inside my container and what entrypoint should I overlay).16:17
*** eaguilar has quit IRC16:25
duonghqsee you later guys16:26
inc0good night duonghq16:27
duonghqbye inc016:27
*** duonghq has quit IRC16:27
*** reidrac has quit IRC16:32
*** janki has joined #openstack-kolla16:38
*** jascott1 has quit IRC16:44
*** unicell1 has quit IRC16:51
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169016:59
*** janki has quit IRC17:00
*** athomas has quit IRC17:01
SamYaplevhosakot: remember, LOCI started as a POC for changing the Kolla build process. it only "forked" into its own project when the build process couldnt be done in Kolla with the existing bits17:08
openstackgerritMerged openstack/kolla-kubernetes master: Make wait_for_pods.py work inside kubernetes cluster  https://review.openstack.org/47894117:10
*** daidv has quit IRC17:10
*** eaguilar has joined #openstack-kolla17:11
*** hieulq has quit IRC17:12
*** unicell has joined #openstack-kolla17:15
openstackgerritMarcus Williams proposed openstack/kolla-ansible master: Add OpenDaylight role  https://review.openstack.org/41636717:16
openstackgerritMarcus Williams proposed openstack/kolla-ansible master: Add OpenDaylight role  https://review.openstack.org/41636717:19
vhosakotSamYaple: ah I see, thanks for the info :)17:20
sdakeSamYaple i'm not sure anyone said you did anything wrong  - no need to give an explination17:20
sdakefwiw I dont think loci is a fork - seems like new original work to me17:20
sdakeand as always SamYaple - your highly creative17:20
vhosakot^^^17:21
vhosakot:)17:21
vhosakotyeah, I like the concept of lightweight/slim images17:21
*** unicell1 has joined #openstack-kolla17:22
SamYaplevhosakot: yea it was made as a POC to fix the external build tool/shared layer problem with kolla that makes kolla really hard to work with in CICD. when it was clear that it wasnt going to land that methodology went its own way and we have been growing it with a focus on CICD and upstream compatible builing aproaches (like building in dockerhub)17:23
SamYaplevhosakot: with the new docker 17.06 FROM image stuff, kolla might be able to achieve a similiar result in size at a significantly greater cost in time, but it would retain the set_config stuff17:23
*** dave-mccowan has joined #openstack-kolla17:24
SamYapleinc0: you have seen the build-args FROM stuff, yes?17:25
*** unicell has quit IRC17:25
*** daidv has joined #openstack-kolla17:25
*** jascott1 has joined #openstack-kolla17:25
jascott1inc0 I sent that email17:25
*** hieulq has joined #openstack-kolla17:26
vhosakotSamYaple: cool, yeah set_config is a grest feature17:26
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169017:27
rwellumsbezverk or kfox1111: have you tried kolla-k8s with docker 17.x?17:28
sdakerwellum last i tried - kubeadm does not support that version of docker17:29
sdakenor did it work when i tried anyway17:29
*** ducttape_ has quit IRC17:31
*** sambetts is now known as sambetts|afk17:34
*** sudipto has quit IRC17:35
*** sudipto_ has quit IRC17:35
sbezverkrwellum nope17:37
sbezverkI heard somebody tried and failed17:37
*** gfidente has quit IRC17:43
*** tonanhngo has joined #openstack-kolla17:44
*** jascott1 has quit IRC17:44
*** jascott1 has joined #openstack-kolla17:45
sdakerwellum kolla-k8s may work with a different installation tool17:48
sdakewith docker 17.x17:48
sdakesuch as kargo (or kubespray?)17:48
kfox1111rwellum: I've been avoiding it.17:50
kfox1111I think the distro's are going to drop docker soon and switch to containerd.17:50
kfox1111over the whole docker swarm -> docker fieasco.17:51
rwellumYeah kfox1111, sdake, sbezverk - I just mention it because SamYaple did above.17:54
kfox1111yeah. not sure how thats going to effect kolla-ansible/kolla-kubernetes.17:54
sdakekfox1111 that is a kubernetes centric world view17:54
kfox1111the paths could potentially diverge a bit there.17:54
sdakered hat fwiw wants to moe to OCID i beieve17:55
kfox1111sdake: its a community centric worldview.17:55
sdakekfox1111 what i mean is there is nthing to replace docker in bare metal at present17:55
sdakecontainerd doesn't do the full job17:55
kfox1111the general community is focused around containerd, not docker inc.17:55
kfox1111why do you say that?17:55
sdakelots of people use docker's apis17:55
sdakein a kubernetes world using docker's apis can be abstracted away17:56
kfox1111Sure. but most of that api is been renamed to containerd.17:56
kfox1111by docker inc.17:56
sdakeok - well i guess I'm out of the loop :)17:56
kfox1111ah.17:56
kfox1111yeah, docker inc did a shell game a couple months ago.17:56
kfox1111"docker" now means something very different then "docker" then.17:57
kfox1111"docker" now is what use to be called docker swarm for the most part.17:57
rwellumBut I believe you need containerd + something though kfox1111  - containerd is not a 1-to-1 of the 'old' docker.17:57
kfox1111and what use to be docker is now containerd.17:57
kfox1111see containerd.io17:57
kfox1111yeah, its not 100% yet. but they are working hard on 1.0. should be out this month I think, the way they are going.17:58
kfox1111this is way the community basically stopped at 1.12/1.13.17:58
kfox1111because containerd's what the community wants, not docker swarm.17:58
rwellumAh it contains runc - that starts to make a little more sens.e17:58
kfox1111but docker inc wants to keep the docker trademark for their product.17:58
kfox1111and their product now is swarm.17:59
vhosakotdocker does not exist anymore :)  https://github.com/docker/docker  goes to  https://github.com/moby/moby :)    all container runtime upstream is CNCF's containerd now... I heard about it too17:59
kfox1111but "docker" has all the praise from users for years.17:59
rwellumRight - deliberate obfuscation?17:59
kfox1111so they are redirecting that praise to docker swarm.17:59
vhosakotdocker is legacy :)17:59
kfox1111oh, docker exists.17:59
*** serlex has quit IRC17:59
kfox1111docker is basically the rhel of docker swarm.17:59
kfox1111moby is now the fedora of docker swarm.18:00
rwellumOk what is moby :)18:00
rwellumArgh!18:00
kfox1111and containderd is what use to be called docker.18:00
kfox1111yeah. they did a huge terminology shift to claim the docker name. :)18:00
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169018:00
vhosakotdocker exists as the non-open-source (commercial) bit18:00
kfox1111right.18:00
kfox1111docker is now all locked up.18:00
rwellumSo is the k8s community working towards containerd then?18:01
kfox1111containerd is what redhat/ubuntu/google/etc cared about in docker of old.18:01
kfox1111yup.18:01
kfox1111thats why they enabled cri by default in 1.6 even though it was beta.18:01
kfox1111they were so anoyed at dockerinc that they pushed hard to put in an abstraction quick.18:01
vhosakotwhat confuses me is, why did docker fork  https://github.com/docker/containerd  from  https://github.com/containerd/containerd...  which of the two is the greatest/newest/best container runtime?18:01
*** bit_lySLH2uSZHed has joined #openstack-kolla18:02
kfox1111it was https://github.com/docker/containerd18:02
kfox1111then it was given over to the cncf,18:02
kfox1111and then became https://github.com/containerd/containerd18:02
sbezverkkfox1111: do you know when containerd will be published in repos?18:02
vhosakotso, both will be developed?18:02
*** bit_lySLH2uSZHed has left #openstack-kolla18:02
kfox1111sbezverk: as soon as its deamed stable by redhat/ubuntu.18:02
kfox1111they have a vested interest in getting off of docker 1.12. so I'd think as soon as possible.18:03
sbezverkkfox1111: ok so in next few years then ;)18:03
*** ducttape_ has joined #openstack-kolla18:03
kfox1111no, I think docker's much more toxic then that.18:03
sbezverkkfox1111 : oh ok18:03
kfox1111I would be really shocked if it wasnt this year.18:04
vhosakotkfox1111: haha, you're not the only one that thinks docker is becoming toxic (money-minded) :)18:04
kfox1111docker inc burned a huge amount of bridges with docker swarm -> docker.18:04
kfox1111it means any company selling swarms competitor (k8s) now has to support swarm too or drop docker support.18:04
kfox1111the community wouldn't stand for that. so its making changes as fast as possible to get docker out.18:05
vhosakotha, why would a k8s' seller support docker swarm too, interesting...18:05
*** stvnoyes has joined #openstack-kolla18:05
*** stvnoyes has left #openstack-kolla18:06
kfox1111yeah. having to install swarm just to install k8s seems bad.18:06
vhosakotI wouldn't need swarm _with_ k8s, when k8s can do everything swarm can and even more.18:07
*** lpetrut has quit IRC18:08
kfox1111yeah. that really rubbed all the k8s supperters wrong.18:09
kfox1111we saw traces of this when docker kept duplicating systemd functionality.18:09
kfox1111but most distros weren't supporting microdistro's yet, so not many cared about it exept CoreOS. thats why that bridge was burned first.18:10
kfox1111then docker inc relized people want to pay for COE, not for individual container launching support.18:10
kfox1111and k8s was providing that, not docker.18:10
kfox1111so they had to push swarm as hard as possibe.18:10
kfox1111so they reclaimed the name to trick people into going with swarm instead of k8s,18:10
kfox1111due to so many people not knowing docker but hearing good devs/ops saying "docker is great"18:11
sdakekfox1111 you use the term "pay' looszely above kfox1111 :)18:11
kfox1111sdake: there are more then one way of paying. ;)18:11
kfox1111$ is just one form.18:11
rwellumUm - I was at a presentation recently where they claimed docker swarm was 5x faster than k8s. :)18:11
kfox1111devs time, kudo's, documentation, blog articles, etc are others.18:11
kfox1111rwellum: at what? faster at failing to be flexible enough to deploy my apps? :)18:12
kfox1111really, with the new nomenclature, they are claiming 5x faster at doing COE things I guess.18:13
kfox1111http://containerd.io/images/chart-f.png shows what the community will look like when the migration is done.18:14
rwellumhttps://blog.docker.com/2016/03/swarmweek-docker-swarm-exceeds-kubernetes-scale/ - it was along these lines.18:15
kfox1111"The study and article, commissioned by Docker"18:17
kfox1111ah. they are doing stuff like benchmarking api calls too.18:18
kfox1111yeah. older article. k8s has better scaling now. also has focused on devs with minikube.18:19
kfox1111so small to huge just like swarm.18:19
kfox1111I'd focus more on articles that come from independent third parties, not from docker inc. they produce a lot of stuff very slanted in their favor. (its their job to do so. I don't blame them)18:20
rwellumYeah - working for a vendor - I get all sorts of customers pitching me stuff.18:21
kfox1111the issue is kind of bad right now in that, a lot of people are saying,18:26
kfox1111"I heard docker is great, I need docker training"18:26
kfox1111so they go and hire someone to do docker training.18:26
kfox1111and then they get all trained up on swarm. :/18:26
kfox1111cause they didn't know to ask.18:27
*** itlinux has quit IRC18:27
sdakekfox1111 thats sort of amusing18:29
kfox1111amusing is one word for it.18:30
kfox1111I've seen it first hand a copule of times now. :/18:30
sdakewhat does this eman18:31
sdakela/'], u'container_name': u'neutron_vpnaas_agent', u'privileged': True}})18:31
sdakeAn exception occurred during task execution. To see the full traceback, use -vvv. The error was: TemplateRuntimeError: {{ service_plugins|selectattr('enabled', 'equalto', true)|list }}: no test named 'equalto'18:31
sdakefatal: [localhost]: FAILED! => {"failed": true, "msg": "Unexpected failure during module execution.", "stdout": ""}18:31
sdakei've seen it and fixed it a bunch of times18:31
sdakei dont recall waht i did to fix it18:31
sdakeinc0 ^^18:31
vhosakotrwellum: yeah, I did some POCs to research comparing the post-day-1 capacities of swarm vs k8s, yes, swarm is pretty cool too with k8s-ish feature (LB, rolling upgrades, auto scaling, storage volume, resiliency manager, etc).18:32
sdakethe fact is swarm isn't hip18:32
sdakeso it is already done for18:32
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169018:32
vhosakotsdake: I've seen that 'equalto' error.  'equalto' is in jinja 2.8.   https://github.com/ansible/ansible/issues/10123#issuecomment-7194973118:33
kfox1111sdake: the problem is, with COE's still relatively new, the docker swarm-> docker rename might actually work to get them primary market share.18:33
kfox1111basically taking advantage of all the good will the community put into docker before the rename. and throwing out the communities solution.18:33
kfox1111rubs me the wrong way. :/18:34
vhosakotI've heard people say they do k8s instead of swarm just because Google started k8s.18:34
rwellumsdake: point jinja2 installation to 2.8.118:34
sdakerwellum thanks18:34
kfox1111I tried early swarm and early k8s.18:34
sdakeearly k8s was a pile of fgarb18:34
kfox1111swarm/compose couldn't do a huge amount of things that k8s could.18:34
sdakeearly swarm was worse18:34
kfox1111the whole problem I had was k8s has pods, and swarm didnt.18:35
sdakecompose was simpel and elegant but ultimately useless18:35
kfox1111pods really are critical for most of my workloads.18:35
sdakealso I submitted a 2 line change upstream and it took 6 months to merge18:35
kfox1111yeah, k8s is slow at times. :/18:35
sbezverksdake: there is a positive side to this, less garbage gets in :)18:36
sdakei was talking about compose (2 line patch)18:36
kfox1111compose worked ok. k8s worked so much better.18:37
kfox1111k8s was a bit more complicated to get into.18:37
sdakesbezverk also fwiw that is a very limited viewpoint - nearly every major innovation was considered "garbage" by those that came before18:37
rwellumWhich solution is more secure?18:37
kfox1111but overall, complexity is down.18:37
kfox1111I think both have pretty good security these days.18:38
sdakekfox1111 if you think kubernetes isn't complex - well - i got some ocean front property in arizona to sell ya :)18:38
vhosakotrwellum: both k8s and swarm can do TLS at nerwork-level.18:38
kfox1111sdake: thats not what I said.18:38
sdakeapologies then18:38
kfox1111the overall system I'm maintaining, I think complexity is down due to adding k8s.18:38
kfox1111as k8s's added complexity was offset by the removal of complexity elsewhere in the system.18:39
vhosakotdon't about container-native security features in the two tho.18:39
kfox1111as k8s matures, that complexity also keeps shrinking.18:39
kfox1111k8s 1.7 just gained the big security feature I was after.18:39
rwellumwhat is that?18:39
kfox1111only allowing secrets to be downloaded by a kubelet if it has a pod scheduled for that node that references the secret.18:39
rwellumAh...18:40
kfox1111then a comped node can't access anything it shouldnt secret wise.18:40
sbezverksdake: I think there is no issue with k8s complexity, the issue is with people who does not want to learn, they want to jump/hump and run away.. ;)18:43
*** itlinux has joined #openstack-kolla18:47
*** lpetrut has joined #openstack-kolla18:54
jascott1jump/hump and run away... lol18:56
rwellumStill on the 'jump18:56
rwellum personally...18:56
rwellumkfox1111, inc0: stupid question.... With configs bloating kolla images. Why not attach a hash to each individual config, store the actual config somewhere else and just the hash in the image. When the config is needed - access it via the hash - use it dynamically?19:01
jamesbensonhow do you build specific docker images in kolla? kolla-build -t source -b ubuntu --registry 127.0.0.1:4000 --push kolla-toolbox ?19:01
vhosakotnothing is complex...  I don't mind getting stuck in the fail-redo-fail-redo-fail-redo-fail-redo-fail-redo-fail-redo loop.. sometimes, I like that loop :)19:01
kfox1111rwellum: not sure I follow.19:01
kfox1111in k8s, we use configmaps to inject the config into the container.19:01
kfox1111so the config lives in k8s, not the container.19:02
rwellumReferring to the large image conversation above. I thought it was the intelligence that is added to the kolla image that is chewing up the space.19:03
rwellumjamesbenson: that looks correct to me - if you're using dockerhub images.19:04
jamesbensonthanks :-)19:04
rwellumkfox1111: so wondering if it can be stored outside the container19:05
kfox1111rwellum: no, the other way around. loci isn't sharing common images, so the same packages have to be added to seperate images.19:05
kfox1111it makes their images bigger when multiple are used on the same host.19:05
kfox1111kolla shares some common base that all inherit from. the config stuff talked about above is shell scripts for processing the config, not the config itself.19:06
kfox1111and its in the base layer, so it is only added one.19:06
rwellumOk that helps - but the same question - can we store the shell scripts outside the image?19:06
kfox1111philosophy question.19:07
kfox1111some of us believe the image is the distribution mechanism. it should provide a well tested/stable api for launching the thing in question.19:08
kfox1111others want the container to be a blob of stuff,19:08
kfox1111and something injected into it at runtime makes sense of the blob and provides a standard api.19:08
vhosakotjamesbenson: just pass the name/regex of the name of the container to be built to kolla-build -->  https://github.com/openstack/kolla/blob/master/kolla/image/build.py#L82419:08
kfox1111I think the former is cleaner and the latter is playing with fire. but thats just me.19:08
vhosakotjamesbenson: https://github.com/openstack/kolla/blob/master/doc/image-building.rst19:09
rwellumkfox1111: so if instead of the scripts in the image, but a hash to the scripts, does that break the former? To me it's the same.19:09
kfox1111if it doesnt have the scripts built in, but has to fetch them,19:10
kfox1111it goes against the phylosophy of the image being the tested/binary identicle image shipped everywhere.19:10
kfox1111I don't think the container should change during runtime.19:11
kfox1111like, "you don't run yum install xxxx"19:11
vhosakotkfox1111: I'm a fan of not injecting anything to a container apart from passing a good config file at runtime.  I think the container built must already have the mechanism to run the thing in question and be a sensible blob.19:11
kfox1111if that happens, then things can drift/break.19:11
kfox1111vhosakot: yeah.19:11
kfox1111makes it easy to mirror locally when you have a firewall in the way, or ensure what you tested on the test system is exactly the same as whats being deployed to the prod system.19:12
vhosakotkfox1111: All I want to do is start a container and pass it some config.  I know want to know what/how to start things at runtime when I start the container.  I start a neutron container, I expect a golden neutron-server up waiting for my config.19:12
kfox1111+119:12
vhosakotI meant. I _dont_ know want to know what/how to start things at runtime when I start the container19:12
kfox1111yeah. the provider of the container should provide that.19:12
kfox1111as part of the container.19:13
vhosakot"something injected into it at runtime makes sense of the blob and provides a standard api" - wonder if this has a valid usecase kfox1111?19:15
kfox1111I've had to do it in kolla-kubernetes as a workaround while we get some stuff standardized in the kolla containers.19:16
kfox1111generally feel uneasy about it.19:17
vhosakotah I see19:17
kfox1111I think the k8s pods should be pure instruction to k8s on how to orchestrate the pod.19:17
kfox1111not how to manage the container processes.19:17
vhosakotyeah, I agree too19:18
kfox1111like, "hook to safely shut down neutron-server"19:18
kfox1111that should be a standard part of the api.19:18
kfox1111or haproxy, or apache. etc.19:18
kfox1111so then the orchestration piece doesn't have to know if the right shutdown for the container is actually apachectl xxxx or kill -SIGUSR1 foo19:19
kfox1111it just calls kolla_safe_shutdown or something.19:19
kfox1111and the container writer implements the right behavior for the right implementation of the container.19:19
kfox1111openstack-helm side steps it with loci and does it:19:20
kfox1111make a configmap containing shell scripts that probe if neutron-server is running under python, or apache, or whatever, and what version of neutron, and try and figure out the right way to safely shut it down.19:20
kfox1111so they check the box on having the logic not be in the k8s orchestration object,19:21
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169019:21
kfox1111but the logic for safe shutdown of the container is not written by the folks writing the container. so there is risk of mismatch.19:21
vhosakotyeah, I like the hook being part of the standard API concept, helps debuggin/remote cases when troubleshooting...19:22
*** ducttap__ has joined #openstack-kolla19:23
*** ducttape_ has quit IRC19:27
rwellumI get what you're saying kfox1111. Thing is -  hashes/keys etc are a very trusted mechanism to validate information is sane. So if you trusted the hash/key then it's as if the script themselves are in the container. It's just as tested, secure, trust-worthy etc. Without the bloating.19:27
rwellumI've done this before. When memory is limited, hash it down, store the hash, pull it back in when needed.19:28
vhosakotrwellum: how would the stuff (configs/scripts) behind the hash pulled at runtime?  from a remote box over the network when the container starts?19:29
*** ducttape_ has joined #openstack-kolla19:30
rwellumvhosakot: yes - along those lines.19:30
rwellumHaven't thought it through - just curious.19:30
vhosakotor mounted from the host at runtime, if not thryu network, in which case the host must carry per-hash stuff , not so portable if container needs stuff on host..19:31
vhosakotover the network is a portable idea.. yeah19:32
*** ducttap__ has quit IRC19:32
*** goldyfruit has quit IRC19:37
sdakehey quick q- my resolvc.conf is not being honored by kubernetes 1.7.019:38
sdakeany suggestions19:38
*** goldyfruit has joined #openstack-kolla19:39
jamesbensoninc0, fyi: centos7 with binary 4.0.0 images fails as well at the same ceph bootstrap stage.19:39
inc0jamesbenson: host ubuntu or host centos?19:45
jamesbensoncentos7 with cent images19:45
jamesbensonI tried both host os's19:46
inc0lol so it's something on the hardware lvl? oO19:46
inc0mtu?19:46
inc0what's your networking look like?19:46
jamesbensonso it seems to fail with host os Ubuntu16 or centos7 and with docker images ubuntu-source and cent-binary19:46
kfox1111rwellum: its adistribution issue, not an issue of trust.19:47
kfox1111putting all the runable code together ensures its shipped together with the same mechanism.19:47
jamesbensonhave time to videochat?  might be easier...19:47
kfox1111you could put in a hash, and a curl in the container, and then it launches then curls the exact hashed files down.19:48
kfox1111but then you have 2 distribution mechanisms. the docker one, and an additional one.19:48
sdakekfox1111 - resolv.conf workaround seems not to work with 1.7.019:48
sdakekfox1111 any suggestions19:48
kfox1111sdake: hmm...19:48
sdakeglance-api or e.g. is not resolvable19:48
kfox1111resolve_conf_net_host_workaround=false work?19:49
kfox1111if not, we may need to put in a patch set that sets the 1.6+ setting for fixing net=host and resolv...19:50
sdakekfox1111 where does that resolve_conf_net_host_woraround=false go19:52
kfox1111its a helm argument.19:53
kfox1111or values file.19:53
kolla-slack<portdirect> how are you finding k8s 1.7.0 with helm?19:53
*** Teck7 has joined #openstack-kolla19:53
kolla-slackAction: portdirect is still to kick the tyres properly19:53
inc0haven't tried it yet19:54
*** rfxn has quit IRC19:55
kfox1111if that doesn't work, we will need to add this attribute to all the pods with the workaround: https://github.com/kubernetes/kubernetes/issues/1740619:55
jamesbensoninc0: 2 nic's, here's my ifconfig: http://paste.openstack.org/show/614809/19:55
jamesbensoninc0: neutron_external_interface: "veno1"; kolla_external_vip_interface: "br0"; network_interface: "eno1"19:56
inc0and it fails on osd bootstrap because timeout?19:57
*** Teck72 has joined #openstack-kolla19:57
*** serlex has joined #openstack-kolla19:58
sdakekfox1111 should I not run setup-resolve-conf?20:00
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169020:00
*** serlex has left #openstack-kolla20:00
*** Teck7 has quit IRC20:01
kfox1111sdake: shouldn't have to if thats off.20:01
jamesbensoninc0, ceph_mon can't reach other nodes or itself I think20:01
jascott1sdake have we installed the services at this point? maybe its not resovling cause they are not there yet?20:02
jamesbensoninc0: http://paste.openstack.org/show/614810/20:02
jamesbensonbut if I do a one node, it fails too unless I'm missing somehting when I modified ceph.conf20:02
sdakejascott1 no - that resolv.conf sh file replaces resolv.conf in each ocntainer20:02
sdakejascott1 in every container loaded20:03
inc0damn, what's so special about your stuff?:/20:03
sdakejascott1 that doesn't appear to be happening with the default settings20:03
sdakeinc0 deploy in progress20:03
sdakeif your interetedin watching20:03
jamesbensoninc0: old dell r410/r610/r710 junk?20:04
inc0jamesbenson: my suggestion now would be - try to use ceph deploy20:05
inc0it's nice on it's own20:05
inc0and deploy kolla with external ceph20:05
inc0http://docs.ceph.com/docs/master/rados/deployment/20:05
jamesbensonyeah, I'm thinking that as well now that I've exhausted all of my options.20:05
sdakekfox1111 ok - well turning that off in cloud.yaml and not running resolv.conf results in the same thing20:06
jamesbensonjust don't understand why this doesn't work...20:06
inc0me neither...20:06
inc0if ceph deploy fails in similar fashon20:06
inc0then it's something deeper20:06
inc0if it succeed, it's something with kolla20:06
jamesbensonokay20:06
*** ducttape_ has quit IRC20:07
sdakekfox1111 even this step which I would expect to work does not20:07
jamesbensoninc0: if kolla, that's going to be fun to debug...20:08
inc0right20:08
sdake[sdake@localhost deploy]$ kubectl run -i -t $(uuidgen) --image=busybox --restart=Never20:08
sdakensloIf you don't see a command prompt, try pressing enter.20:08
sdakeServer:    10.3.3.1020:08
sdakeAddress 1: 10.3.3.10 kube-dns.kube-system.svc.cluster.local20:08
sdakenslookup: can't resolve 'glance-api'20:08
sdakeoh nm, it does seem to work as you described it20:09
sdakealthough deployment doesnt20:09
* sdake groans20:09
jamesbensonquestion, after bootstrap, kolla doesn't do anything with the disk images, correct?  Because I do a reboot afterwards.  I'm thought I remember someone mentioning something with the disk id or something?  ::memory fails me::20:10
jamesbensonjust wondering if a reboot between bootstrap and deploy can impact anything20:11
inc0well, with external ceph it's not relevant20:11
inc0ntp jamesbenson? ;)20:11
jamesbensonlol, fixed that ;-)20:11
jamesbensonhey, you're welcome to dig around into these machines if you want...20:12
inc0brain no worky today:(20:12
jamesbensontell me about it, fighting near migraines for the past 2 days... hard to focus...20:14
sdakejascott1 - sadly have a meeting shortly20:14
sdakejascott1 if you want ot continue poking at it, you hae seen my workflow - feel free20:15
*** ducttape_ has joined #openstack-kolla20:15
jascott1sdake im going to take a look around the tiller source20:15
jascott1but yeah I will give it a go when I get an idea of wtf to do next ;)20:15
sdakejascott1 not sure how tha twill be hepful but up to you :)20:15
jascott1im convinced out ultimate problem is tiller going out to lunch20:16
sdakethis is failing:20:16
sdake  Args:20:16
sdake      /usr/bin/openstack endpoint create --region "RegionOne" "image" "admin" "http://glance-api:9292";20:16
sdake    State:              Waiting20:16
sdake      Reason:           CrashLoopBackOff20:16
sdake    Last State:         Terminated20:16
sdake      Reason:           Error20:16
sdake      Exit Code:        120:16
jamesbensoninc0, ceph-deploy (https://github.com/ceph/ceph-deploy) should be equivalent right?20:16
inc0not sure, I think sl20:16
inc0so20:16
jamesbensonlooks like it's ceph deploy just automated20:17
sdakeok whoever figured out what the problem was - feel free to deploy :)20:23
sdakelets see if she works20:23
*** ansmith has quit IRC20:25
sdakeok deploy away :)20:29
sdakei gotta jet for about 1.5 hrs20:29
sdakeremember remove /var/lib/kollavolumes/*20:29
sdake :)20:29
jascott1thanks20:29
*** jtriley has quit IRC20:32
*** lrensing has quit IRC20:36
Reepicheepansible question?  If I want to override the openstack-infra.conf for the karbor-protection container should this have a "vint20:38
Reepicheepoops .. fingers got off20:38
Reepicheepshould it have a "with_first_found" or something like that?20:39
Reepicheephttps://github.com/openstack/kolla-ansible/blob/master/ansible/roles/karbor/tasks/config.yml20:39
jascott1sdake image kolla/cnetos-source-kolla-toolbox:3.0.2 not found20:41
*** sambetts|afk has quit IRC20:42
*** sambetts has joined #openstack-kolla20:43
sdakejascott1 looks like deploy is working to me20:45
sdakeoh - thats because my network ided :)20:45
jascott1oh20:45
jascott1but the other containers failed previously20:46
sdakereadiness probe failed on glance- registry20:49
sdake    Readiness:          http-get http://:9191/healthcheck delay=5s timeout=5s period=10s #success=1 #failure=320:49
sdakedoesn't look correct20:50
sdakesame thing on neutron-server20:51
sdakeneed to enable haproxy I think20:51
sdakeor disable it20:52
sdakesoeone changed teh docs20:52
sdakethe docs dont work20:52
sdakepretty sure kfox1111 changed that iirc - i recall reviewing it20:52
kfox1111haproxy should be turned on by default.20:53
kfox1111it is on in the gates too.20:53
kfox1111so well tested.20:53
sdakedoesn't work with the docs20:55
sdakeprobably an ansible implementation gap20:57
*** ducttape_ has quit IRC21:09
*** ducttape_ has joined #openstack-kolla21:09
*** klindgren has quit IRC21:11
jamesbensoninc0 I think I found part of the problem, selinux21:13
inc0on ubuntu?21:14
inc0hmm21:14
jamesbensoncentos right now21:14
inc0yeah21:14
inc0makes total sense21:14
jamesbensonbut still having issues with ceph-deploy21:14
inc0try kolla ceph with setenforce 021:14
inc0on all nodes21:15
jamesbensonthat's the command?21:15
vhosakotReepicheep: template override is when a child block inherits/extends a parent template and overrides parent's blocks/sections.  I think what you're looking for is to reconfigure/tweak openstack-infra.conf.   You can just update the jinja file https://github.com/openstack/kolla-ansible/blob/master/ansible/roles/karbor/templates/providers.d/openstack-infra.conf.j2 before deploying, or update it in /etc/kolla, and run "k21:15
vhosakotolla-ansible reconfigure".21:15
jamesbensonsorry, being stupid.21:16
jamesbensonansible -i ./multinode -m shell -a "setenforce 0" all21:16
jascott1uh where is tillers configmap?21:17
vhosakotinc0: I see kolla-ansible does not have stable/newton branch, but kolla repo still has stable/newton branch.  is there a plan to remove stable/newton in kolla repo?21:17
jamesbensonI'm running deploy again now...21:17
inc0vhosakot: kolla-ansible was created in ocata21:18
vhosakotah, somebody asked me about it... so, kolla's newton branch should have the ansible playbooks as well then right?21:18
vhosakotyes I see it, thanks for the info inc021:19
*** Pavo has joined #openstack-kolla21:20
*** ducttape_ has quit IRC21:24
*** itlinux has quit IRC21:26
*** iniazi_ has joined #openstack-kolla21:26
jamesbensoninc0: still fails...21:29
*** iniazi has quit IRC21:29
*** klindgren has joined #openstack-kolla21:32
*** lpetrut has quit IRC21:34
*** ansmith has joined #openstack-kolla21:36
Reepicheepvhosakot: that is basicly what I did and it didn't work as expected21:38
ReepicheepI put my own openstack-infra.conf file in /etc/kolla/config/karbor/providers.d/openstack-infra.conf which did not get deployed when I ran a "reconfigure"21:39
Reepicheepidealy for karbor we would be able to add more providers, files in providers.d/21:40
*** dave-mccowan has quit IRC21:41
*** goldyfruit has quit IRC21:46
*** openstackgerrit has quit IRC21:47
*** schwicht has quit IRC21:49
*** jamesbenson has quit IRC21:49
*** tonanhngo has quit IRC21:51
*** JamesBenson-mobi has joined #openstack-kolla21:53
JamesBenson-mobiInc0: leaving my office now, but ceph deploy just gave me a health ok status....21:54
*** openstackstatus has quit IRC21:56
*** openstack has joined #openstack-kolla22:00
*** JamesBenson|phon has joined #openstack-kolla22:00
*** iniazi_ has quit IRC22:01
*** Pavo has quit IRC22:01
*** jamesPR has joined #openstack-kolla22:02
*** JamesBenson-mobi has quit IRC22:03
*** jamesPR has quit IRC22:04
*** JamesBenson-mobi has joined #openstack-kolla22:09
*** JamesBenson|phon has quit IRC22:12
*** rhallisey has quit IRC22:12
*** JamesBenson|phon has joined #openstack-kolla22:29
*** JamesBenson-mobi has quit IRC22:33
*** manheim has joined #openstack-kolla22:34
*** openstackgerrit has joined #openstack-kolla22:36
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169022:36
*** JamesBenson|phon has quit IRC22:49
*** Pavo has joined #openstack-kolla22:50
sbezverkkfox1111: ping22:55
kolla-slack<kfox1111> Hi22:55
kolla-slack<kfox1111> What's up?22:56
kolla-slack<kfox1111> [Not at a computer]22:57
*** Pavo has quit IRC23:02
sbezverkkfox1111: got it.. will ping you later then or next week23:03
kolla-slack<kfox1111> K23:03
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes master: WIP Adding alternative iscsi_helper support  https://review.openstack.org/48169023:12
*** JamesBenson-mobi has joined #openstack-kolla23:14
*** schwicht has joined #openstack-kolla23:15
*** manheim has quit IRC23:38
*** ducttape_ has quit IRC23:38
*** bmace has quit IRC23:41
*** bmace has joined #openstack-kolla23:41
*** manheim has joined #openstack-kolla23:41
*** jtriley has joined #openstack-kolla23:44
*** ducttape_ has joined #openstack-kolla23:47
*** jtriley has quit IRC23:50
JamesBenson-mobiInc0 I think I know why it is failing....23:52
kfox1111sbezverk: ping23:52
kfox1111back at a computer.23:52

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