Friday, 2016-06-03

*** vinkman has quit IRC00:00
*** sdake_ has joined #openstack-kolla00:02
*** jrist has quit IRC00:16
*** zhiwei has joined #openstack-kolla00:18
*** ayoung has joined #openstack-kolla00:20
*** rahuls has quit IRC00:20
*** jrist has joined #openstack-kolla00:21
*** zhiwei has quit IRC00:23
*** david-lyle has quit IRC00:25
*** rhallisey has joined #openstack-kolla00:26
*** david-lyle has joined #openstack-kolla00:26
*** david-lyle has quit IRC00:30
wirehead_rhallisey: I’ve got an updated https://review.openstack.org/#/c/320744/00:36
patchbotwirehead_: patch 320744 - kolla - Add kolla-kubernetes bootstrap capability to mariadb00:36
rhalliseywirehead_, go ahead an post over my patch00:36
wirehead_rhallisey: I’m not sure how to do that correctly. :D00:37
rhalliseywere you editing on top of my patch?00:37
wirehead_Yeah.00:37
rhalliseyso add the changes.  git commit --amend00:38
rhalliseyand git review that00:38
rhalliseyalso add yourself as a co-author00:38
wirehead_Err, I lied.  I’m editing on top of master.00:38
wirehead_Which of the options under “Download” is the right one?00:39
rhalliseywirehead_, is there massive change? Would it be painful to merge the commits?00:39
wirehead_Naw.  It’s 4 lines.00:39
rhalliseyya cherry pick under download00:39
wirehead_Okay, so I’m in detatched head.  So I just create a new branch on my end?00:40
rhalliseywait did you use the checkout link? or cherrypick?00:41
rhalliseyhere do this: git stash.  cherry-pick.  git stash pop00:41
rhalliseyand fix any conflicts00:41
wirehead_ok00:43
*** daneyon_ has joined #openstack-kolla00:43
wirehead_then I just ammend the change?00:43
wirehead_Too much time with Github has made my git-fu weak. :P00:43
rhalliseyyes amend it00:44
rhalliseyno worries00:45
ccesariohey folks....00:46
ccesariodoes soeone have any idea about this error ? http://paste.openstack.org/show/507417/00:46
ccesarioI 'm trying deploy using Ubuntu 16.04 as host.....00:47
*** daneyon_ has quit IRC00:47
*** phuongnh has joined #openstack-kolla00:48
openstackgerritKen Wronkiewicz proposed openstack/kolla: Add kolla-kubernetes bootstrap capability to mariadb  https://review.openstack.org/32074400:49
rhalliseywirehead_, nice00:49
wirehead_This means that the containers don’t need to know about etcd anymore. :)00:50
wirehead_And you can do `kubectl describe po mariadb` and get the status of the bootstrap.00:50
wirehead_(you can use the --v=8 flag with any kubectl command to see what API calls it’s doing)00:51
rhalliseysweet00:52
rhalliseyI'll try it out tmr00:56
*** rhallisey has quit IRC00:56
*** ssurana has quit IRC01:06
*** weiyu has joined #openstack-kolla01:09
*** asalkeld has quit IRC01:13
*** eaguilar has joined #openstack-kolla01:15
sdake_my note5 died so I bought a samsung galaxy s7 for 5$ a month :)01:23
*** zhiwei has joined #openstack-kolla01:30
*** vinkman1 has left #openstack-kolla01:35
openstackgerritJoshua Harlow proposed openstack/kolla: Make kolla-ansible a top level python command  https://review.openstack.org/32498202:04
*** mummer has quit IRC02:17
*** eaguilar has quit IRC02:17
*** eaguilar has joined #openstack-kolla02:17
sdake_harlowja quick question02:22
sdake_i just saw your python kolla-ansible command02:22
sdake_looksgood02:22
sdake_one issue is we have -vvv to get maximum output02:22
sdake_and -vv02:22
sdake_and -vvvv02:22
sdake_ansible has different levels by the number of vs iiuc02:23
*** eaguilar has quit IRC02:25
*** eaguilar has joined #openstack-kolla02:25
*** eaguilar has quit IRC02:25
*** unicell has quit IRC02:31
openstackgerritMerged openstack/kolla: Install missing package in spiceproxy container  https://review.openstack.org/32365002:32
*** inc0 has joined #openstack-kolla02:35
inc0good evening02:36
coolsvapgood morning folks02:36
inc0hey coolsvap rested well?02:36
coolsvapnot much but i have a good (or bad) habit of waking up early whatever time i sleep02:36
openstackgerritMerged openstack/kolla: Add .vimrc to .gitignore  https://review.openstack.org/32462802:37
openstackgerritMerged openstack/kolla: Fix the cinder backup permission issue when enable ceph  https://review.openstack.org/32333002:37
coolsvapso sometimes i even get up in couple of hrs but thats fine with me02:37
coolsvapi take cumulative sleep over weekends02:37
*** sacharya has joined #openstack-kolla02:37
openstackgerritSteven Dake proposed openstack/kolla-mesos: Fix typos in readme.rst  https://review.openstack.org/31179202:39
sdake_coolsvap can you approve that please so I can retire kolla-mesos02:39
sdake_inc0 cn you approve that please02:39
sdake_coolsvap lol02:39
sdake_jpeeler or Jeffrey4l_ can you approve 31179202:40
inc0done02:40
sdake_thanks02:40
sdake_coolsvap how about a workfklow on https://review.openstack.org/#/c/311792/02:41
patchbotsdake_: patch 311792 - kolla-mesos - Fix typos in readme.rst02:41
sdake_2 pages of outstanding reviews02:42
* sdake_ groans02:42
inc0yeah I just started reviews02:43
openstackgerritMerged openstack/kolla-mesos: Fix typos in readme.rst  https://review.openstack.org/31179202:43
Jeffrey4l_+workflow02:43
inc0tomorrow I'll do full review and bugfix day02:43
inc0since we have this DSL thing sorted out02:43
sdake_thanks :)02:44
inc0sdake_, check out harlowja patch series, you wanted build.py optimizations02:46
sdake_inc0 i have looked at some of them already02:47
sdake_i dont care about optimizaations02:47
sdake_i want to simplify what we have rather then make it more complex ;)02:47
sdake_the barrier change is good02:47
sdake_i also liked the change on the items thing02:47
sdake_but i haven't tested it02:47
sdake_and afraid to touch build.py :)02:47
sdake_so I will need to test it persoanlly02:48
sdake_before I +2 it02:48
inc0I'm testing full series now02:48
inc0seems cool and faster than usual build02:48
inc0also did you try customization thing?02:49
coolsvapinc0, sdake_ https://review.openstack.org/317240/ https://review.openstack.org/317256/02:49
inc0on my review list coolsvap ;)02:49
*** yuanying has quit IRC02:50
* coolsvap just wanted highlight, pending from along time, lot of rebases02:50
sdake_inc0 was that email representative of what we agreed to and discussed02:56
sdake_inc0 i've been trying to clean up my backlog today02:56
sdake_but friday I am going to spend all day working on that02:56
inc0sdake_, mail looks about right02:59
inc0not sure about 8 places per dockerfile but I don't knwo what you mean02:59
inc0so just make first set and we'll go from thee02:59
*** unicell has joined #openstack-kolla03:01
sdake_dmsimard quick q about ara03:02
dmsimardsdake_: wazza.03:02
sdake_dmsimard i am totallly slammed with work - i saw your announcement and wanted to try it out03:02
sdake_but I just dont have time and probably wont for atleast 2-3 weeks03:02
dmsimardsure.03:03
sdake_I'm wondering what the output looks like with kolla AIO if you ahve tried it03:03
sdake_or what it does preciesely :)03:03
dmsimardsdake_: I haven't, is kolla ansible >2 yet ?03:03
dmsimardif it is I can run it for you03:03
sdake_yup all the ansible bugs are fixed ;)03:03
inc0dmsimard, indeed it is03:03
sdake_dmsimard that would be great - I'd like to see the text03:03
sdake_or html03:03
sdake_or whatever03:03
sdake_i should just do it myself03:04
dmsimardsdake_: I can put it on a hosted demo03:04
sdake_but seriously 2 pages of outstanding reviews03:04
sdake_ahlf of them are in merge conflict03:04
dmsimardsdake_: I haven't touched kolla in a couple months, link to aio docs ?03:04
sdake_http://docs.openstack.org/developer/kolla/03:05
sdake_quickstart is sort of AIO :)03:05
sdake_the docs have been undergoing alot of changing03:05
dmsimardyeah that quickstart docs says <2.003:07
dmsimardI guess I should use master branch ?03:07
inc0dmsimard, master should be ansible 203:08
sdake_master is 2.0 or 2.103:11
sdake_stable branches are on 1.9.403:11
*** weiyu has quit IRC03:13
dmsimard2.1 is fine ?03:14
sdake_yup03:14
dmsimardk03:14
inc0there was some issues with 2.1, not sure tho what's it's about03:16
sdake_pretty sure 2.1 is fixxed03:17
sdake_according to ml03:17
inc0will test tomorrow03:27
inc0good night guys03:27
sdake_later dude03:27
*** inc0 has quit IRC03:27
dmsimardkolla-build is running03:29
dmsimardyou made me bump into a req mismatch issue between ara and openstack global-reqs :)03:29
dmsimardhttps://github.com/dmsimard/ara/issues/9703:29
dmsimardyay for finding bugs03:30
*** timonwong has joined #openstack-kolla03:30
sdake_coolsvap did we make a decision on :: on the line where the : should go, or on a separate line in the docs03:38
dmsimardI'm gonna fall asleep if those images don't finish building soon :p03:43
*** yuanying has joined #openstack-kolla03:49
*** mdnadeem has joined #openstack-kolla03:52
coolsvapsdake_, yes03:53
coolsvapif there is no trailing :03:53
coolsvapit should be on the same line03:53
sdake_so example03:54
sdake_Here is hte information:03:54
sdake_should be03:54
sdake_Here is the information::03:54
coolsvapno03:54
coolsvapin this case the :: should be no next line03:54
*** v1k0d3n has quit IRC03:54
*** mdnadeem_ has quit IRC03:55
coolsvapi think i wrote it wrong03:55
coolsvapno i did write it correctly03:55
coolsvapw.r.t. what you said, if there is trailing :03:56
coolsvap:: should not be on the same line, it should be on next line03:56
coolsvapsdake_, ^^03:56
*** dwalsh has quit IRC03:59
*** ssurana has joined #openstack-kolla04:04
*** tfukushima has joined #openstack-kolla04:05
*** diogogmt has quit IRC04:07
*** ssurana has quit IRC04:09
*** ayoung has quit IRC04:20
sdake_coolsvap so the docs should be04:20
sdake_"This is an example:04:20
sdake_<cr>04:20
sdake_::04:20
sdake_four spaces then text?04:21
coolsvapyes04:21
coolsvapno04:21
sdake_ok well one of your patches is busted04:21
coolsvapwhich one?04:21
sdake_coolsvap read review 3 https://review.openstack.org/#/c/31708404:22
sdake_Mauricio Lima04:23
sdake_put it on a single line.May 20 11:12 AM04:23
sdake_Steven Dake04:23
sdake_9:22 PM04:23
sdake_We made a documentation decision at some point in the last couple of weeks based upon reading the RST documentation that the above syntax is indeed correct.04:23
sdake_For example, this patch merged.04:23
sdake_https://review.openstack.org/#/c/320933/04:23
patchbotsdake_: patch 320933 - kolla - Update the image-building documentation (MERGED)04:23
*** v1k0d3n has joined #openstack-kolla04:24
sdake_I guess that was mandre's patch04:24
coolsvaplet me write explanation here04:24
sdake_here where04:24
sdake_respond on my unmerged patch please04:24
sdake_so i know what to fix :)04:24
coolsvapon the unmerged patch04:24
coolsvapyes04:24
sdake_http://docs.openstack.org/developer/kolla/image-building.html04:25
sdake_this renders correctly04:25
coolsvapyes04:26
coolsvapyour syntax is correct04:26
*** kbyrne has quit IRC04:32
*** cloudnautique has quit IRC04:33
*** kbyrne has joined #openstack-kolla04:35
openstackgerritSteven Dake proposed openstack/kolla: Document upgrading for operators  https://review.openstack.org/31708404:35
*** tfukushima has quit IRC04:40
*** tfukushima has joined #openstack-kolla04:41
*** tfukushima has quit IRC04:46
*** dave-mccowan has quit IRC04:47
dmsimardsdake_: seeing this error in the precheck http://paste.openstack.org/show/507488/04:55
dmsimard2.0.1.0 or 2.1.0.0, same error04:55
sdake_dmsimard not sure what would cause that - are ou using the same globals.yml from before or a new one?  if so can you paste it04:56
dmsimardsdake_: I'm using whatever came from master, did not edit it04:56
dmsimardbuilt centos binary and just did kolla-genpwd04:56
sdake_oh you have to modify globals.yml slightly04:56
sdake_to specify an internal vip address04:57
sdake_and your docker registry04:57
sdake_it should be in the documentation04:57
dmsimardit looks like it used the defaults04:57
dmsimardshrug, kolla-ansible deploy is going now04:57
dmsimardI don't plan on troubleshooting this tonight, just want to send you the results04:58
sdake_sounds good04:58
sdake_if its too hard I understand - I'll get to it eventuallly - i saw your demo - which was helpful04:58
*** timonwong has quit IRC05:01
dmsimardsdake_: nope, got it05:05
dmsimardsdake_: have a gift for you :)05:05
dmsimardsdake_: https://dmsimard.com/ara.tar.gz05:06
dmsimardgenerated static version of what I ran with kolla precheck and kolla deploy05:06
dmsimardif you have any feedback, email or https://github.com/dmsimard/ara/issues is fine, sleep for me now before I pass out :)05:07
*** tfukushima has joined #openstack-kolla05:17
*** yuanying has quit IRC05:17
openstackgerritMerged openstack/kolla: Use a task model and dumb workers  https://review.openstack.org/32131705:26
openstackgerritHui Kang proposed openstack/kolla: Build openvswitch image using source type  https://review.openstack.org/30972605:51
*** Mr_Broken has joined #openstack-kolla05:54
*** Mr_Broken has quit IRC06:00
*** yuanying has joined #openstack-kolla06:05
*** Mr_Broken has joined #openstack-kolla06:06
openstackgerritMerged openstack/kolla: add curlrc file to base image  https://review.openstack.org/30191106:12
*** openstackgerrit has quit IRC06:17
*** openstackgerrit has joined #openstack-kolla06:18
*** phuongnh has quit IRC06:21
*** phuongnh has joined #openstack-kolla06:22
*** yuanying has quit IRC06:28
*** yuanying has joined #openstack-kolla06:29
*** lmiccini has quit IRC06:29
*** mkoderer has quit IRC06:30
*** yuanying has quit IRC06:31
mdnadeemHello, is there anyone who face the issue  "IOError: [Errno 2] No such file or directory: '/var/lib/kolla/config_files/config.json'" while deploying mariadb service ?06:31
*** mkoderer has joined #openstack-kolla06:31
*** yuanying has joined #openstack-kolla06:31
mdnadeem>> https://github.com/openstack/kolla/blob/master/docker/base/set_configs.py#L15006:32
*** lmiccini has joined #openstack-kolla06:32
*** yuanying has quit IRC06:33
*** yuanying has joined #openstack-kolla06:34
*** harlowja has quit IRC06:35
mdnadeemJeffrey4l_,  could you please let me know how to generate /var/lib/kolla/config_files/config.json file or what value is need to set in env variable "KOLLA_CONFIG" ?06:47
*** unicell has quit IRC07:00
*** unicell1 has joined #openstack-kolla07:00
*** tyrola has joined #openstack-kolla07:02
*** openstackgerrit has quit IRC07:03
*** openstackgerrit has joined #openstack-kolla07:03
*** tyrola has quit IRC07:04
*** SiRiuS__ has joined #openstack-kolla07:06
*** tyrola has joined #openstack-kolla07:07
*** sacharya has quit IRC07:07
*** phuongnh has quit IRC07:11
*** phuongnh has joined #openstack-kolla07:12
*** mikelk has joined #openstack-kolla07:15
*** tyrola has quit IRC07:25
openstackgerritJoshua Harlow proposed openstack/kolla: Make kolla-ansible a top level python command  https://review.openstack.org/32498207:25
*** matrohon has joined #openstack-kolla07:30
*** reddydodda has quit IRC07:41
*** yuanying has quit IRC07:50
*** reddydodda has joined #openstack-kolla07:53
*** tyrola has joined #openstack-kolla07:54
*** daneyon_ has joined #openstack-kolla07:55
openstackgerritMerged openstack/kolla: Document upgrading for operators  https://review.openstack.org/31708407:56
*** elemoine_ has quit IRC07:58
*** tpeoples has quit IRC07:58
*** daneyon_ has quit IRC08:00
*** rmart04 has joined #openstack-kolla08:02
*** sdake_ has quit IRC08:03
*** mgoddard has joined #openstack-kolla08:04
*** sacharya has joined #openstack-kolla08:08
*** sacharya has quit IRC08:13
*** cu5 has joined #openstack-kolla08:27
*** jmccarthy has quit IRC08:32
*** bradjones has quit IRC08:39
*** cu5 has quit IRC08:39
*** tonyb has quit IRC08:39
*** dasm has quit IRC08:39
*** tonyb has joined #openstack-kolla08:39
*** huikang has joined #openstack-kolla08:39
*** yuanying has joined #openstack-kolla08:39
*** bradjones has joined #openstack-kolla08:39
*** bradjones has quit IRC08:39
*** bradjones has joined #openstack-kolla08:39
*** dasm has joined #openstack-kolla08:40
*** phuongnh has quit IRC08:48
*** phuongnh has joined #openstack-kolla08:48
openstackgerritHui Kang proposed openstack/kolla: Add vars to the merge_config task in config-neutron-fake.yml  https://review.openstack.org/32513909:04
*** huikang has quit IRC09:08
*** tpeoples has joined #openstack-kolla09:08
*** jmccarthy has joined #openstack-kolla09:09
*** elemoine_ has joined #openstack-kolla09:15
*** dwalsh has joined #openstack-kolla09:21
*** SiRiuS__ has quit IRC09:33
-openstackstatus- NOTICE: CI is experiencing issues with test logs, all jobs are currently UNSTABLE as a result. No need to recheck until this is fixed! Thanks for your patience.09:37
*** logan_ has joined #openstack-kolla09:57
*** logan_ is now known as Guest6297109:58
*** logan- has quit IRC09:59
*** Guest62971 is now known as logan-10:01
*** elemoine_ has quit IRC10:02
*** tpeoples has quit IRC10:02
-openstackstatus- NOTICE: CI is experiencing issues with test logs, all jobs are currently UNSTABLE as a result. No need to recheck until this is fixed! Thanks for your patience.10:08
*** ChanServ changes topic to "CI is experiencing issues with test logs, all jobs are currently UNSTABLE as a result. No need to recheck until this is fixed! Thanks for your patience."10:08
*** pbourke_ has quit IRC10:10
*** pbourke_ has joined #openstack-kolla10:11
*** tfukushima has quit IRC10:11
*** rhallisey has joined #openstack-kolla10:14
*** mkoderer has quit IRC10:16
*** slagle has quit IRC10:16
Jeffrey4l_mdnadeem, never saw this. is other container ok?10:30
*** tpeoples has joined #openstack-kolla10:32
mdnadeemJeffrey4l_, Actually i am trying to deploy mariadb using kolla-kubernetes : https://github.com/openstack/kolla-kubernetes/blob/master/doc/source/quickstart.rst10:33
Jeffrey4l_this file should be exist on `/etc/kolla/mariadb/config.json`, and then map to the container by using `-v`10:34
Jeffrey4l_the file in `/etc/kolla/mariadb/config.json` is generate by the ansible( in kolla ). it come from the templates folder in the mariadb role.10:35
Jeffrey4l_mdnadeem, ^10:35
mdnadeemJeffrey4l_, yes, this file is present at my host, however i dont know why set-config.py looks for /var/lib/kolla/config_files/conf.json ?10:37
*** rmart04 has quit IRC10:38
*** daneyon_ has joined #openstack-kolla10:38
Jeffrey4l_set_config will copy the config file to the right position in the container. the source and the dest info is wrote in the config.js10:38
Jeffrey4l_config.json10:38
*** rmart04 has joined #openstack-kolla10:38
mdnadeem>>  https://github.com/openstack/kolla/blob/master/docker/base/set_configs.py#L15010:39
*** elemoine_ has joined #openstack-kolla10:40
mdnadeemJeffrey4l_, source directory is /var/lib/kolla/config_files/galera.cnf, however on my host there is no /var/lib/kolla directory10:41
rhalliseymdnadeem, https://github.com/openstack/kolla-kubernetes/blob/master/kolla_kubernetes/common/file_utils.py#L4010:41
Jeffrey4l_mdnadeem, this file is in the containers.10:42
Jeffrey4l_mdnadeem,10:42
rhalliseymdnadeem, are you using tools/kolla-kubernetes.py ?10:42
rhalliseycurious how you're running it10:42
mdnadeemrhallisey, i run it directly  kolla-kubernetes run mariadb10:43
*** rmart04 has quit IRC10:43
mdnadeemas mentioned in guide : https://github.com/openstack/kolla-kubernetes/blob/master/doc/source/quickstart.rst10:43
rhalliseyrun it from tools. I'm wondering if that bit is broken10:43
*** daneyon_ has quit IRC10:43
mdnadeemok, let me try it10:44
*** phuongnh has quit IRC10:44
*** rmart04 has joined #openstack-kolla10:45
*** mkoderer has joined #openstack-kolla10:49
*** slagle has joined #openstack-kolla10:49
*** orwell.freenode.net changes topic to "Kolla IRC meetngs on Wednesdays @ 16:30 UTC even weeks, 23:00 UTC odd weeks - see agenda @ https://goo.gl/OXB0DL - IRC channel is *LOGGED* @ http://goo.gl/3mzZ7b (old logs from #kolla http://goo.gl/VKpPzA)"10:49
mdnadeemrhallisey, try as you say, the pods still show in pending state from last 3-4 minutes10:55
mdnadeemrhallisey, http://paste.openstack.org/show/507644/10:58
rhalliseymdnadeem, can you run with -d and paste the output11:00
mdnadeemrhallisey, >> http://paste.openstack.org/show/507645/11:03
mdnadeemrhallisey, Error from server: configmaps "mariadb-configmap" already exists11:03
rhalliseymdnadeem, ./tools/kolla-kubernetes kill mariadb11:07
rhalliseythen run it again11:07
rhalliseymdnadeem, bootstrap then run11:07
rhalliseymdnadeem, if you look at line 49, it's pick up the config files11:07
rhalliseybut I think you maraidb configmap is left over11:08
mdnadeemrhallisey, I have done the same thing, i had run kill mariadb11:08
rhalliseymdnadeem, kubectl describe configmap mariadb-configmap11:10
mdnadeem>> http://paste.openstack.org/show/507646/11:11
rhalliseyso it looks like it has config11:12
mdnadeemrhallisey, what you mean by bootstrap then run, is it mean first i run ./tools/kolla_kubernetes.py -d run mariadb-bootstrap and then again run ./tools/kolla_kubernetes.py -d run mariadb ?11:13
rhallisey ./tools/kolla_kubernetes.py -d bootstrap mariadb11:13
rhalliseyyes11:13
rhalliseybe sure to remove /var/lib/mysql11:14
rhalliseyor bootstrap will error11:14
mdnadeemok11:14
*** coolsvap_ has joined #openstack-kolla11:16
rhalliseymdnadeem, one more thing :)11:18
rhalliseyhttps://review.openstack.org/#/c/320744/11:18
patchbotrhallisey: patch 320744 - kolla - Add kolla-kubernetes bootstrap capability to mariadb11:18
rhalliseyyou need to build the mariadb container with that patch11:18
mdnadeemrhallisey, ok, i will try by this patch, Thanks11:19
rhalliseyno probelm11:19
rhalliseymdnadeem, I'll brb in 30 min11:19
rhalliseylet me know if it works for you11:19
mdnadeemsure11:19
*** rhallisey has quit IRC11:19
ccesariomorning guys!!11:22
*** coolsvap_ has quit IRC11:27
*** mliima has joined #openstack-kolla11:31
mliimamorning guys11:32
*** coolsvap_ has joined #openstack-kolla11:39
-openstackstatus- NOTICE: CI is experiencing issues with test logs, all jobs are currently UNSTABLE as a result. No need to recheck until this is fixed! Thanks for your patience.11:41
*** ChanServ changes topic to "CI is experiencing issues with test logs, all jobs are currently UNSTABLE as a result. No need to recheck until this is fixed! Thanks for your patience."11:41
*** rhallisey has joined #openstack-kolla11:54
*** coolsvap_ has quit IRC12:05
*** SiRiuS has joined #openstack-kolla12:07
*** sacharya has joined #openstack-kolla12:10
*** sacharya has quit IRC12:15
*** tyrola has quit IRC12:23
*** Mr_Broken has quit IRC12:26
*** tyrola has joined #openstack-kolla12:28
*** Mr_Broke_ has joined #openstack-kolla12:31
*** dave-mccowan has joined #openstack-kolla12:44
*** tyrola has quit IRC12:44
*** cu5 has joined #openstack-kolla12:46
*** sdake has joined #openstack-kolla12:49
sdakehey cats12:50
sdakesweet my upgrade doc merged12:50
Mech422sdake: Morning :-)12:52
Davieysdake: Have you thought about how to backup the control plane data, and restore/rollback in the event of upgrade failure?12:53
sdakeharmw around?13:01
sdakerestore/rollback13:01
sdakeits 6am13:01
sdakegive me 15 mins to get rolling pls13:01
sdakeharmw ignore, I was pingin gsomeone else13:01
Davieysdake: i'll give you 20 mins. :)13:02
*** stvnoyes has quit IRC13:05
*** stvnoyes has joined #openstack-kolla13:05
*** berendt has joined #openstack-kolla13:12
*** mark-casey has joined #openstack-kolla13:12
dmsimardsdake: did you retrieve that link I sent you last night ?13:17
sdakedmsimard not yet but its on my list for before 8am: )13:17
dmsimardsdake: ok, let me know when you got it, I'll delete it from my server :p13:18
*** daneyon_ has joined #openstack-kolla13:20
Mech422sdake: btw - the VLAN stuff works great with VETH devices.  Found an issue with OpenVSwitch that irc0 had a nice fix for13:23
sdakeMech422 fantastic13:23
sdakedmsimard i did download it13:24
sdakedmsimard lasst night13:24
sdakeI just haven't opened it up yet13:24
*** daneyon_ has quit IRC13:25
*** ppowell has joined #openstack-kolla13:27
mark-caseyMech422: is your VLAN mention for VLAN configured in Neutron by chance?13:30
mdnadeemrhallisey, Please have a look at this : http://paste.openstack.org/show/507667/13:33
*** ruhe has left #openstack-kolla13:34
*** inc0 has joined #openstack-kolla13:34
inc0good morning13:34
ccesariomorning inc0 :)13:35
inc0pbourke_, mandre DSL thing is concluded I think13:35
*** huikang has joined #openstack-kolla13:36
rhalliseymdnadeem, clear our any old python remnants of kolla-kubernetes13:36
pbourke_inc0: yeah I saw the email13:36
rhalliseyand reinstall it13:36
rhalliseyit's not picking up the bootstrap commnd13:36
mandreinc0: without even a drop of blood13:36
Mech422mark-casey: no - umm - I'm setting up Kolla host with OVS and vlans for the various nets (storage,internal,external) - then using VETH pairs to pass that to kolla13:36
inc0true mandre, I'm almost disapointed;)13:37
Mech422mark-casey: working really nicely - only thing is, Kolla starts new OpenVSwitch daemons in containers - so you need to comment out 3 tasks to prevent that13:37
inc0Mech422, ovs-db* 3 tasks you commented are about db;)13:38
ccesarioinc0, have tested kolla deploy  using ubuntu 16.04 ? I did not have success..13:38
inc0ccesario, hmm, not yet13:38
ccesariohttp://paste.openstack.org/show/507653/  http://paste.openstack.org/show/507654/13:38
inc0Lyncos tested it out tho afaik13:38
Mech422inc0: oh yeah - openvswitch-vswitchd is still running - my bad13:38
inc0you might want to talk to him when he appears13:39
inc0but he tested stable mitaka13:39
mandreinc0, pbourke_, sdake: what do you think of http://paste.openstack.org/show/507325/ as a way to simplify the configuration of the build?13:39
mdnadeemrhallisey, ok13:39
mandreall you have to pass to the build script in the end is a profile13:39
inc0mandre, looks good, we need to have long critical look at our build13:40
ccesarioinc0, http://paste.openstack.org/show/507668/13:40
inc0and refactor it greatly13:41
ccesarioinc0, rigth.... I will check with him13:41
pbourke_what is is simplifying13:41
inc0ccesario, check haproxy logs13:41
pbourke_*is it13:41
mdnadeemrhallisey, i should manually delete >> rm -rf /usr/local/share/kolla-kubernetes/ and again re-install it . right ?13:42
inc0pbourke_, we don't really have a way to add another dockerfile to our set13:42
inc0custom one I mean13:42
mark-caseyMech422: what does that allow? sounds very convenient but I'm trying to think why the Kolla host has to participate in those networks13:42
rhalliseymdnadeem, I think you just need to get rid of the python bits then reinstall13:42
openstackgerritVikram Hosakote proposed openstack/kolla: WIP: Updates Magnum for Mitaka  https://review.openstack.org/31480513:42
pbourke_we do you just drop it in13:42
pbourke_under docker/13:42
pbourke_I feel the kolla-build.conf is quite straight forward to use13:43
*** mbound has joined #openstack-kolla13:43
Mech422mark-casey: it allows me to use 1 pair of bonded 10GigE interfaces for all of Kolla/openstack13:43
mdnadeemrhallisey, can you please  provide command to do that, actually i am not getting it13:43
Mech422mark-casey: so I get HA on the nics13:43
rhalliseymdnadeem, sure.  rm -f /usr/lib/python2.7/site-packages/kolla-kubernetes*13:44
rhalliseys/-f/-rf/13:44
Mech422mark-casey: (I suppose it also protects against port failures on the swithc too)13:44
mdnadeemrhallisey,  ok, then un install kolla-kubernetes by executing command sudo pip uninstall .13:45
*** tyrola has joined #openstack-kolla13:45
*** mgoddard_ has joined #openstack-kolla13:45
ccesarioinc0, http://sprunge.us/JDjQ13:46
inc0uhh...dunno13:46
inc0will test it later on13:46
Mech422inc0: btw - since I'm manually configuring br-ex, I can use OVS patch connections instead of VETH for a bit more performance13:46
sdakeguys i've got a on fire email i need to deal with i will read scrollbakc in about 30 minutes whwen i' mdone and respond13:47
inc0well now technically you can do whatever13:47
rhalliseymdnadeem, yes13:47
sdakeDaviey i'll bbiaf13:47
*** mgoddard has quit IRC13:49
*** huikang has quit IRC13:49
mark-caseyMech422: cool. (was reading chat log and...) I would also love to see that in the advanced config doc. I've got two gige and two 10gig ports on my motherboard(s)13:49
*** huikang has joined #openstack-kolla13:50
Mech422mark-casey: http://pastebin.com/wfMEwTVC13:50
Mech422mark-casey: I haven't figured out the required hoops to jump to submit that for 'official' use13:50
Mech422mark-casey: I think my boss needs to sign some agreement13:51
Mech422mark-casey: also - sam yapple has some really good info on setting Ceph up to use partitions rather then whole devices on his blog - that should prolly be in the advanced docs too13:52
*** huikang has quit IRC13:52
*** huikang has joined #openstack-kolla13:52
*** tyrola has quit IRC13:52
Mech422mark-casey: basically - just tag whatever gpt partitions you want kolla/ceph to use with the name "KOLLA_CEPH_BOOTSTRAP_x" and "KOLLA_CEPH_BOOTSTRAP_x_J" to create a data/journal pair for ceph13:53
mdnadeemrhallisey, http://paste.openstack.org/raw/507669/13:53
mark-caseyMech422: someone may correct me (and I'm not a lawyer), but stackalytics is based on Affiliations you specify when signing the individual contributor agreement. you may or may not have to get the company version signed13:53
Mech422mark-casey: ('x' is just a incrementing number, and is unique per HOST - not cluster)13:53
Mech422mark-casey: dunno - it was boring legal crap - more fun to hack on the cluster :-P13:54
mdnadeemrhallisey, this time mariadb container name change to "mariadb-db6l5"13:54
rhalliseymdnadeem, ya it deploying a replication controller13:54
rhalliseymdnadeem, did you include the patch that split the cli?13:55
mark-caseyMech422: and yea. I think the gpt flags were used in the demo in Tokyo. really cool13:55
rhalliseymdnadeem, sorry, not everything has merged yet. There's bits and pieces all over the place13:55
Mech422mark-casey: yeah - its a really great feature. you can tag whole drives, or just the partitions you want :-)13:55
Mech422mark-casey: very handy when you don't want to have a custom provisioning setup just for OSD nodes13:56
mdnadeemrhallisey, please provide me the link, i will try with the patch13:56
rhalliseyhttps://review.openstack.org/#/c/324113/13:56
patchbotrhallisey: patch 324113 - kolla-kubernetes - Add bootstrap method to the quickstart doc13:56
mark-caseyrhallisey: latest maria bootstrap I saw looks slick. what is it talking to on localhost:8080?13:56
Mech422mark-casey: (Our provisioning sets up partition 2 as '/', which is why I had to go looking to begin with...)13:56
rhalliseymdnadeem, you need to pip uninstall then apply that13:56
rhalliseymark-casey, I need to ask wirehead_ about that13:57
mark-caseycool13:57
mdnadeemrhallisey, but this patch have changes only in doc13:57
rhalliseymdnadeem, oops sorry wrong patch13:58
openstackgerritMauricio Lima proposed openstack/kolla: [WIP] Implements elemental.yml DSL for nova  https://review.openstack.org/32531313:58
rhalliseyhttps://review.openstack.org/#/c/320668/13:58
patchbotrhallisey: patch 320668 - kolla-kubernetes - Break deployment procedure into two steps13:58
rhalliseymdnadeem, that one ^13:58
mdnadeemrhallisey, ok,13:59
*** mgoddard_ has quit IRC13:59
*** ChanServ changes topic to "Kolla IRC meetngs on Wednesdays @ 16:30 UTC even weeks, 23:00 UTC odd weeks - see agenda @ https://goo.gl/OXB0DL - IRC channel is *LOGGED* @ http://goo.gl/3mzZ7b (old logs from #kolla http://goo.gl/VKpPzA)"14:00
-openstackstatus- NOTICE: Cleanup from earlier block storage disruption on static.openstack.org has been repaired, and any jobs which reported an "UNSTABLE" result or linked to missing logs between 08:00-14:00 UTC can be retriggered by leaving a "recheck" comment.14:00
*** mgoddard has joined #openstack-kolla14:00
*** ayoung has joined #openstack-kolla14:00
mark-caseyrhallisey: with 'api/v1/namespaces/default/replicationcontrollers' in the path I'm pretty sure it's posting annotations for the RC to k8s itself (some part of it).14:01
mark-caseyquite cool14:02
*** huikang has quit IRC14:03
openstackgerritMauricio Lima proposed openstack/kolla: [WIP] Implements elemental.yml DSL for nova  https://review.openstack.org/32531314:03
openstackgerritChristian Berendt proposed openstack/kolla: Install keepalived in neutron_l3_agent container  https://review.openstack.org/32531614:03
rhalliseymark-casey, ya I'm trying it now14:03
rhalliseymark-casey, ok I get how it works14:04
openstackgerritChristian Berendt proposed openstack/kolla: Document the use of external Ceph journal drives  https://review.openstack.org/32453914:04
*** salv-orlando has joined #openstack-kolla14:05
*** b_bezak has joined #openstack-kolla14:09
*** Mr_Broke_ has quit IRC14:10
mdnadeemrhallisey, http://paste.openstack.org/show/507670/14:14
*** huikang has joined #openstack-kolla14:15
mdnadeemrhallisey, containers is in pending state, any idea how much time generally it will take to come to running state ?14:15
rhalliseymdnadeem, I think the latest addition to the mariadb container is breaking it. It's looking to append something to a replication controller that doesn't exist14:15
mdnadeemrhallisey, ohk, can i try on some other service like keystone or any other, please suggest ?14:17
rhalliseymdnadeem, https://review.openstack.org/#/c/320744/3 was working for me.  The newest patch not yet14:17
patchbotrhallisey: patch 320744 - kolla - Add kolla-kubernetes bootstrap capability to mariadb14:17
rhalliseyI think wirehead_ was running it without the split CLI14:17
rhalliseysince in that scenario it could signal the RC14:17
*** mbound has quit IRC14:18
*** Mr_Broken has joined #openstack-kolla14:19
*** egonzalez has joined #openstack-kolla14:19
*** jtriley has joined #openstack-kolla14:19
mdnadeemrhallisey, ohk, Thanks , its enogh for today, time to go home, will see u soon  :)14:20
rhalliseymdnadeem, no problem.  It will become more stable soon enough :)14:20
mdnadeemrhallisey, yah , very exiting to use it :)14:21
jmccarthyHiya, wondering about is there some work going on at the moment to use ansible 2.1 to do deploys ?14:33
inc0well, not sure if it's "going"14:34
*** reddydodda has quit IRC14:34
inc0but it's surely a priority14:34
*** matrohon has quit IRC14:35
jmccarthyOk, what version is expected to be used at the minute, 2.0 is it ?14:36
pbourke_isn't it just ceph that doesn't work with 2.1?14:37
*** pbourke_ is now known as pbourke14:38
sdakepbourke can we backup in kolla to swift?14:38
pbourkesdake: dont know. it may be possible to configure with augment files. I've never tried it14:39
*** egonzalez has quit IRC14:43
*** huikang has quit IRC14:44
jmccarthyinc0: Is there a bp or something tracking the ansible 2.1 work ? I'm wondering about how to know if or how it's going14:45
wirehead_rhallisey, mdnadeem : Yeah, the afforementioned mysterious call is the Kubernetes API.14:48
rhalliseywirehead_, ya I've been playing around with it14:48
rhalliseythe issue with calling the RC though is with the CLI split the RC doesn't exists14:49
wirehead_rhallisey, mdnadeem : It's bad practice to talk directly to etcd.14:49
wirehead_Yeah, I saw that.  Hrm.14:49
rhalliseywirehead_, is there a way to change the amount of replicas?14:49
wirehead_Yeah, you just update the replica key.14:49
rhalliseycould have bootstrap also be an rc14:49
wirehead_I was going to say that. :D14:49
wirehead_Bootstrap creates the RC, with replica count 0.14:50
wirehead_start sets replica count to 1.14:50
rhalliseyya that's what I'm trying now14:50
rhalliseyI'm just not getting it's key :)14:50
*** rmart04 has quit IRC14:51
rhalliseywirehead_, there's also something to consider.  If the key lives in the bootstrap data, will it be lost when the bootstrap container gets deleted?14:52
rhalliseyor does it even live with the bootstrap14:52
rhalliseythe lock could also live with the master14:53
wirehead_So, the reason why I put it in the RC in the first place is so that it's lifetime will match the lifetime of MariaDB.14:57
wirehead_If you do a `kolla-kubernetes kill mariadb` then any information about the bootstrap goes away.14:57
wirehead_(which is what motivated me to get that patched in the first place.  Got tired of reprovisioning my Vagrant box because mariadb only provisioned right on a fresh config)14:58
inc0jmccarthy, well, so I don't think we did much more besides get it running14:59
inc0for 2.014:59
inc0if it's not running for 2.1 then that's a bug14:59
*** mgoddard_ has joined #openstack-kolla15:01
rhalliseyI think we want it to last the lifetime of mariadb.  But for lights out recovery that won't work15:01
wirehead_Depends on what you mean by "lights out recovery".15:02
rhalliseynode gets unplugged15:02
*** zhiwei has quit IRC15:02
inc0wirehead_, lights out recovery is recovery from restart of all of galera cluster nodes15:03
inc0and we need to set them back up without losing data15:03
inc0that is non-trivial15:03
*** mgoddard has quit IRC15:04
rhalliseyhmm maybe we would recover15:04
rhalliseysince the bootstrap wouldn15:04
rhallisey'be run again15:04
*** mliima has quit IRC15:05
inc0rhallisey, talking about k8s?15:05
rhalliseyyes15:05
inc0you won't have this issue at all15:05
inc0as you don't run galera cluster, only single mariadb15:05
inc0issue appears when you have cluster out of it15:05
wirehead_So, my Kubernetes demo is aother piece of software we've been working on.  And we delete all of the nodes live and onstage.15:06
wirehead_As long as the contents of the etcd are preserved, the next time that k8s comes up, it'll try to re-schedule all of the RCs until it has nodes to schedule them on.15:06
rhalliseyI'm just worried about how we handle the locking so recovery works15:06
wirehead_Thus, outside of zapping things back to bare metal, the annotation will be preserved.15:06
wirehead_It's little more than a 'safe' proxy to etcd.15:07
sdakepbourke if I dind't already thank yu thanks for the resposne :)15:07
* sdake deep in fire email15:07
rhalliseyok so storing the lock with the rc should be fine15:08
mark-caseyinc0: rhallisey: with the patch to make haproxy consider donor and/or resyncing galera nodes, I think it's now less troublesome to run a cluster in k8s. Cluster now has more theoretical reliability than a single mariadb that gets restarted on fail15:09
wirehead_So, right now, if you zap a node, it's going to try to re-schedule the MariaDB RC to another node.15:09
inc0mark-casey, so in k8s it works differently15:09
inc0whole model15:09
inc0basically you run only single db node, mount storage over network15:09
wirehead_^ what inc0 said.15:10
inc0if node dies, k8s is responsible of rescheduling it somewhere else and reconnecting network15:10
inc0so you never really get net partition15:10
inc0as you never run cluster15:10
wirehead_It's sick as an angry greased armadillo in practice.15:10
inc0only caveat to that is situation when etcd loses node, but actual container works15:11
*** mgoddard has joined #openstack-kolla15:11
inc0(for example etcd uses mgmt network and storage uses stor network. interface of etcd dies and maria keeps running)15:11
inc0therefore before restarting k8s has to ensure that storage is fenced and supposedly down node will not write to it15:12
*** dwalsh has quit IRC15:12
inc0doable.15:12
wirehead_So, what I've heard from larger-scale ops is that k8s handles a control plane outage OK.15:12
inc0then it's really safe and your data is a lot safer than with galera15:12
inc0yeah, so I heard15:12
*** mgoddard_ has quit IRC15:12
inc0jmccarthy, so I'm deploying with ansible 2.1 now15:13
wirehead_Also, you can set up a resilient etcd cluster and there you get better guarantees on distributed database linearization than the usual yolo distributed database.15:13
inc0no issues so far15:13
mark-caseymounting storage over network adds overhead to new users. I don't run ceph with Kolla now and am not thrilled about being forced into it to use k8s. A restarting galera node wipes the datadir and replicates it from healthy node. This removes the need for any anchoring of db pods. As long as the k8s health check knows what a resyncing/donor node looks like you don't lose queries on fail/recover15:14
inc0mark-casey, so with k8s you think about ha a bit differently15:14
inc0mark-casey, you need to do this with k8s anyway15:14
inc0otherwise k8s is just a glorious restarter of containers15:14
mark-caseyemptydir volumes are persistent to pod deletion15:15
inc0you need to store data somewhere...15:15
jmccarthyinc0: Oh ! Ok cool I was just thinking to setup a vm or something and try a deploy as well, do you have ceph enabled ?15:16
rhalliseyya shared storage here is a must15:16
inc0well, it failer;)15:16
inc0on cinder15:16
mark-caseyright, as long as the pod isn't deleted from all k8s workers at the same time, your data is inside the container. which is exactly how kolla-ansible does it - without shared storage15:16
inc0and yeah, ceph enabled15:16
inc010 node + ceph15:17
wirehead_You can probably use a NAS or NAS-like thing15:17
inc0mark-casey, not exactly15:17
wirehead_I think that's kinda a NAS-ty solution by comparison. :D15:17
inc0right now data is in named volume15:17
inc0and I mean k8s becomes a restarter15:17
rhalliseymark-casey, it's on the host now15:17
inc0let me put it that way15:17
mark-caseyI may be missing a piece. I thought if you delete all db containers you have a bad day15:17
inc0mark-casey, no15:18
inc0it would be equivalent to service mariadb stop on nodes15:18
inc0if you redeploy containers, it'll work just fine15:18
rhalliseymark-casey, all of mariadb's data exists in /var/lib/docker15:18
inc0(if you follow recovery procedure)15:18
inc0no persistent data is ever stored in container15:18
inc0we used to do that in liberty and this huge backport was because of this15:19
mark-caseyok. but in that case the data in /var/lib/docker is not shared between hosts15:19
inc0it never is15:19
inc0so you have persistent data locally15:19
inc0if node dies, well, shame15:20
mark-caseyright. I think it would be better to do the same in k8s15:20
inc0I don't agree15:20
rhalliseymark-casey, then the db can't float15:20
inc0as 1. k8s manages volumes really well15:20
rhalliseyit would be tied to nodes15:20
inc0you don't need ceph for that, you have lots of options15:20
mark-caseyisn't it tied to nodes now outside of k8s15:20
mark-casey*?15:20
inc0and as Ryan say, you want k8s to manage and restart containers across cluster15:20
rhalliseymark-casey, yes, ansible will deploy to the nodes you specifcy15:21
rhalliseythe db data is stored on those nodes15:21
inc0mark-casey, yeah, but you get software that manages storage really well to manage storage instead of having every single thing managing it's own15:21
inc0some good, some not so good15:21
inc0as for new users...k8s is not really for new users imho15:22
rhalliseykube will abstract maraidb out so that it guarantees it be active somewhere15:22
inc0if you want k8s, you should be able to tell why you want it15:22
*** mliima has joined #openstack-kolla15:22
rhalliseyinc0, lol add that to the readme15:22
inc0:)15:22
inc0well, that's true to most of software15:23
inc0and a lot of times not met:)15:23
mark-caseyrhallisey: you'd said the db can't float. why was that?15:23
rhalliseymark-casey, no it can float15:23
inc0mark-casey, becasue storage will be local15:23
rhalliseyin kubne15:24
rhalliseyusuing ceph15:24
inc0it requires net mounted volumes to float15:24
rhalliseywithout ceph, so using hostMount, it can't float15:24
mark-caseysure it can15:24
rhalliseyhow would it, hostMount is relative to a node15:25
Mech422pbourke: on https://review.openstack.org/325316 - my understanding is its NOT a bug, but you need a 'tag' after KOLLA_CEPH_OSD_BOOTSTRAP ( eg KOLLA_CEPH_OSD_BOOTSTRAP_1, KOLLA_CEPH_OSD_BOOTSTRAP_1_J)15:25
mark-caseythe mysql datadir is evaluated on galera start and if the node is too far behind or has no data the datadir is explicitly rm -rf and resynced from a healthy node15:25
Mech422pbourke: basically, it uses the 'tag' to pair the data partition with a journal partition15:27
rhalliseyare you talking about clustering here? I'm talking about one mariadb service15:27
*** huikang has joined #openstack-kolla15:28
inc0mark-casey, again, no galera in k8s15:29
inc0you don't want galera in k8s15:29
rhalliseymark-casey, plus in your example, it would only be able to float between those 2 nodes15:29
rhalliseywe want it to float everywhere15:29
sdakeok scrollback15:29
inc0cuz it will float and if it floats away it will cause partition15:29
inc0a lot of partitions15:29
inc0a lot of replications15:29
sdakeDaviey still around?15:30
sdakemandre I withhold judgement on any changes to build.py until we finish the refactor we seem to be in agreement about relating to customization15:30
sdakemandre then th efloodgates open to fix kolla-build15:31
rhalliseywirehead_, have you figured out what the key is?15:32
*** vhosakot has joined #openstack-kolla15:32
rhalliseyto change replicas15:32
*** nilk has quit IRC15:33
sdakemark-casey what kind of gear has 10gig ethernet on motherboard?15:33
mark-caseyhttp://www.newegg.com/Product/Product.aspx?Item=2NS-000A-000B9http://www.newegg.com/Product/Product.aspx?Item=2NS-000A-000B915:33
mark-caseysdake:15:33
mark-caseyoops double paste15:33
mark-caseyhttp://www.newegg.com/Product/Product.aspx?Item=2NS-000A-000B915:33
rhalliseywow15:34
rhalliseyworth more than my laptop15:34
sdakemark-casey everyone has to sign the individual license agreement, even if a company has signed it - to contribute to openstack15:34
mark-caseysdake: right. I was trying to allude to the company not signing15:34
sdakeMech422 did sam make a parition patch availalbe, or does it work with kolla as is?15:35
sdakeMech422 sam and I had lots of conversations about partition support in ceph and he said it was difficult - i assume that means it requires a change15:35
Mech422sdake: it appears to be in the code...15:36
sdakemliima I think we are on to the plan we discussed on the google hangout last night, which means you dont need to do nova or neutron at this time15:36
Mech422sdake: though I'm still working on pulling up all the various services15:36
mark-caseyrhallisey: nvme slot, soldered-on octa Xeon-D that can be passively cooled, kvm over IPMI. I'm in love. we got three of them15:36
Mech422sdake: he has a blog post about how to use it - let me dig it up...15:36
rhalliseymark-casey, lol nice!15:36
sdakejmccarthy we are working on ansible 2.1, 2.0 works, and I think 2.1 works as well but not cetain15:37
sdakebut only in master15:37
inc0mark-casey, sounds like something I'd like under my desk15:37
*** dwalsh has joined #openstack-kolla15:37
inc0passively cooled including power supply? so it won't be noisy as fuck?15:37
mark-casey:D15:37
mark-caseyPSU has a fan15:37
mliimai did it yesterday sdake :/15:38
Mech422sdake: http://yaple.net/2016/03/20/deploying-openstack-mitaka-with-kolla-docker-and-ansible/ (the explanation is right above the first code snippet)15:38
mark-caseyand there is a version of the whole board with a fan15:38
sdakewirehead_ lights out recovery means that the datacenter has had a lights out scenario (power loss) and mariadb doesn't recover from that without manual (or in our case automated) intervention15:38
inc0so I'm going back to shitload of nucs idea15:38
sdakerhallisey please don't use any locking - it doesns't scale15:38
sdakeinc0 I agree with single db node approach - please use that ;)15:39
inc0sdake, for k8s15:39
rhalliseysdake, the locking has to do with determining if we're in bootstrap mode15:39
inc0http://www.amazon.com/Single-Computers-Intel-BoardM-2-pieces/dp/B0131V6F0S/ref=sr_1_11?ie=UTF8&qid=1464968352&sr=8-11&keywords=nuc+board&refinements=p_89%3AIntel15:39
Mech422inc0: I have 2xDell c6100's and 1 x HP 6500 8-node chassis15:40
rhalliseykube doesn't have dependancies15:40
Mech422inc0: noisy as all get out15:40
*** jtriley has quit IRC15:40
sdakeinc0 lol glorious restarter of ontainers15:40
Mech422inc0: but at $250/node with 24+G RAM, 2xquadcore, IPMI, etc - its dirt ass cheap15:40
rhalliseyinc0, that's what compute will be :)15:40
inc0so my plan is to buy several nucs, all passively cooled15:41
mark-caseyon k8s out of curiosity, thus far, what else requires shared storage?15:41
inc0or put 2 silent fans once I stack them together15:41
inc0mark-casey, rabbitmq15:41
Mech422inc0: the nucs are nice - but don't they 'kit out' at like $400/node ?15:42
inc0and that's about it15:42
inc0well, you can15:42
inc0depends on a nuc15:42
mark-caseyinc0: same situation with single node for rabbit or is it an IPC type issue?15:42
rhalliseywirehead_, so another idea15:42
inc0single node rabbit, same thing15:42
rhalliseywirehead_, we could probe the bootstrap pod/rc to see that it exited15:43
sdakemark-casey cool thanks - super cheap price for that15:43
rhalliseyor doesn't exist15:43
sdakemy 10gig nics in my minidells were 300$ a crack15:43
rhalliseythat would be a signal to run15:43
sdakemliima all good :)15:43
sdakemliima sorry for wasting yoru time :(15:43
Mech422sdake: I've been seeing 10g adapters on EBay for like $25...15:44
Mech422sdake: problem is the dam switches are still way expensive15:44
Mech422sdake: especially compared to how fast the infi-band switch prices dropped15:44
mark-caseysdake: for sure. the only nitpick I have so far is that the pcie channel the 10g nics are on (internally) isn't quite high enough bandwidth. though I suppose that may be an issue for addin cards too.15:44
sdakerhallisey no kube has a shitload of deps, they just get statitcally built - some form github master branches...15:44
mliimadon't worry sdake :)15:44
rhalliseysdake, no I mean dependencies on other tasks15:45
sdakeMech422 my switch was 850 bucks15:45
Mech422sdake: heh - yeah, too rich for my home setup - I get 4 full nodes populated for $1k15:46
*** absubram has joined #openstack-kolla15:46
sdakegood price15:46
sdakeI have 6 nodes total, 3 with 32gb ram core i7s ssd storage and 4tb of disk15:46
sdake1 with 1.2tb nvme ssd, 128gb ram15:46
Mech422sdake: yeah - the dell c6100's are decent - but I sorta prefer the hp 6500 chassis15:46
sdake2 with 12 gb ram15:46
sdakeall with 10gig dual nic cards15:46
*** jtriley has joined #openstack-kolla15:46
sdakeI have a netgear prosafe 8 port 10gig switch15:47
sdakeseems to work15:47
sdakelittle noisy15:47
sdakelittle/lot15:47
Mech422sdake: mine are 24/48G RAM, 2xquard core, 120G SSD per node15:47
sdakemy office sounds like a jet factory15:47
sdakeok all caught up on scrollback for the morning :)15:47
Mech422sdake: and 8 of my nodes have a mellanox 10G fiber card15:47
mark-caseyrhallisey: inc0: hey guys are you expecting the shared storage ahead of time or are you planning to deploy it to k8s first as part of deploy?15:47
sdakeDaviey still around?15:47
inc0mark-casey, shared storage will be requirement prior to deploy k8s15:48
inc0k8s doesn't really handle storage15:48
rhalliseymark-casey, good question.  Likely before15:48
inc0it needs to have some external storage15:48
rhalliseyif we leave that to be handled externally, it will make our lives easier15:48
mark-caseyinc0: I do get most of the persistence issues, but I still disagree :)15:48
inc0one idea I had is to use our current ansible to deploy ceph and k8s;)15:48
mark-caseyI like that15:49
rhalliseyagreed15:49
Mech422sdace: my real 'find' was an IBM 24U half rack for $300.... took me 6 months to find one for sale locally15:49
*** sacharya has joined #openstack-kolla15:49
sdakewirehead_ you ahve some work on ceph don't you?15:52
sdakeMech422 nice15:54
*** mikelk has quit IRC15:58
wirehead_sdake: David is doing the ceph work.16:01
wirehead_So, I am trying really really really really hard to not have a jet factory in my geekroom.16:01
*** dwalsh has quit IRC16:02
wirehead_It’s disruptive to my other obsessions in life besides code.  Such as music.16:02
wirehead_So, I’m actually going into the office today instead of wfh.  I haven’t gotten to looking at the patches yet.16:02
dmsimardfyi spotted an ansible 2.1 regression https://github.com/ansible/ansible/issues/1612516:03
Mech422wirehead_: yeah - I turned my son's old bedroom into a 'server room' - can still hear the servers thru the shared wall16:03
wirehead_dcwangmit01_ and I have been going back and forth about Ceph.  We’ve got our own cluster set up via Ansible.16:03
*** daneyon_ has joined #openstack-kolla16:03
sdakewirehead i hear you with the music16:03
wirehead_I like my NUC linux box.16:04
wirehead_It’s silent.16:04
sdakewirehead_ https://drive.google.com/open?id=0B8q6xDPETSkHcGNpdDVHbEpmcmc16:05
sdakeMech422 i did that to my daughter when we remodeled16:05
sdakeshe almost killed me i'm pretty sure :)16:05
openstackgerritMerged openstack/kolla: Enable HAProxy consider MariaDB wsrep_local_state  https://review.openstack.org/32220016:06
sdakewirehead_ dr feickert blackbird turntable, line magnetic 219ia SET tube amp, Audio Research phono se216:06
mark-caseyscore!  @ https://review.openstack.org/#/c/322200/16:06
patchbotmark-casey: patch 322200 - kolla - Enable HAProxy consider MariaDB wsrep_local_state (MERGED)16:06
sdakei am buying an axiom when vestmast hits16:06
mark-caseyso excited about that one16:07
Mech422wirehead_: yeah - quiet is definately nice.. but it would have double the cost - and I have 16 nodes, so it adds up16:07
Mech422sdake: LOL - mine moved cross country so he hasn't found out yet :-P16:07
sdakewirehead_ this is what the axiom looks like https://www.google.com/search?q=axiom+tonearm&espv=2&tbm=isch&imgil=b5VL3-1PM1H7VM%253A%253B-T_OdTOI4r3nfM%253Bhttp%25253A%25252F%25252Fwww.myhifilife.com%25252F2014%25252F06%25252F09%25252Fdiscovering-germanys-acoustical-systems%25252F&source=iu&pf=m&fir=b5VL3-1PM1H7VM%253A%252C-T_OdTOI4r3nfM%252C_&usg=__RZW8lYO8EgfAr7lbZZz1zohfASI%3D&biw=960&bih=475&ved=0ahUKEwjut_ndnozNAhVJ7mMKHRG0DigQyjcIKQ&ei=R6tRV674CM16:08
sdakencjwOR6LrAAg#imgrc=b5VL3-1PM1H7VM%3A16:08
sdakewoops16:08
sdakehttp://www.myhifilife.com/wp-content/uploads/2014/06/axiom.jpg16:08
sdakesuper excited about that16:08
*** daneyon_ has quit IRC16:08
sdakewirehead_ the gear on the second shelf is for digital musicand power distribution16:10
wirehead_So I’m very much a home recording nerd instead of an audiophile.16:10
wirehead_So I’ve got some Yamaha HS50M studio monitors: https://www.flickr.com/photos/cyberspace/8216074388/16:10
sdakewirehead_ oh i see :)16:10
wirehead_As well as some crappy Logitech speakers for testing on a ‘real’ setup.16:11
sdakewell for recording you need absolute silence16:11
wirehead_Which reminds me, I need to stop being lazy about soundproofing foam.16:11
*** tyrola has joined #openstack-kolla16:11
sdakehave you found a vendor for any?16:11
sdakei'd like to get some on my walls to absorb sound16:11
sdakesince i have tile now16:11
wirehead_http://www.foambymail.com/acoustical-foam-products.html16:12
sdakeand my audio gear sunds worse16:12
sdakebummer only comes in charcoal16:12
wirehead_Naw, it comes in colors too16:12
sdakethe one i want only has charcoal16:12
sdakeor would want16:12
sdakeI saw a really cool sound imrpovement board at my dealer16:13
sdakebut he said the company is out of business16:13
sdakeits basically like a picture with nothign on it :)16:13
wirehead_One of the Rackspace SF offices had noise problems, so we got a bunch of bright colored foam from there.  Eventually they got rid of it.  So I’ve got a lot of bright blue foam squares to reduce reflectivity.16:14
wirehead_Also bookshelves.16:15
sdakei may bite the bullet and get a rug16:15
wirehead_Bookshelves loaded with books are actually decent ersatz sound reflectivity dampers.16:16
sdakesomething cheap and thick16:16
*** ravig has joined #openstack-kolla16:16
sdakeyes bookshelves rock16:16
sdakebut i don't have pace in my listening room16:16
wirehead_That’s what real recording studios use.  Vibe + soundproofing.16:16
sdakewhat is vibe16:16
sdakei want some refelctions16:16
wirehead_Psychological vibe.16:16
sdakebut i have too many now16:16
sdakethe soundstage is muddled slightly from where it was16:16
sdakealthough it is still fantastic16:16
openstackgerritMerged openstack/kolla: Use an image object, recorder object and status constants  https://review.openstack.org/32184416:17
*** jmccarthy has left #openstack-kolla16:18
wirehead_Hm.  So I can’t find right now the geekroom arrangement panorama, from chair view.16:21
wirehead_Oh, there’s also http://www.auralex.com/ sdake16:23
sdakewirehead_ sweet thanks for the link16:24
sdakei've book maked thatone :)16:24
wirehead_They’ve got some interesting-looking things under the Diffusion lineup16:25
*** jmccarthy has joined #openstack-kolla16:25
sdakeagree16:25
wirehead_Well, if you come to the SF office, sdake, Andi Parker is a huge audiophile nerd, of your tribe.16:26
sdakenice16:26
inc0so in topic of sound16:26
inc0I found really good speakers for the buck16:26
wirehead_There’s a combination coffee shop and audiophile store in SF.16:26
inc0http://www.amazon.com/Micca-MB42X-Bookshelf-Speakers-Tweeter/dp/B00E7H8GG2?ie=UTF8&psc=1&redirect=true&ref_=oh_aui_detailpage_o02_s00 I was surprised by sound quality for that kind of money16:27
*** ssurana has joined #openstack-kolla16:27
wirehead_Well, given today’s technology, it takes dedicated research *COUGH*bose*COUGH* to sound truly bad.16:28
inc0well, bose doesn't sound super bad, but its so overpriced that for that kind of money you can get superb stuff16:29
inc0I actually was surprised that in Europe this stuff is cheaper16:29
inc0but maybe because I'm used to european brands and looked mostly at these16:30
inc0even with this it seems cheaper to get good quality stuff16:30
ccesarioinc0, Lyncos told me that he used 14.04 not 16.0416:30
inc0at host?16:31
inc0ok then I misunderstood him16:31
inc0anyway I'm more headphones guy than speakers16:31
*** esharao has joined #openstack-kolla16:33
wirehead_rhallisey: I mean, we could just create a file on the drive to signal that bootstrapping is complete.16:33
esharaohi guys.. quick question - I'm getting the following error..  404 Client Error: Not Found (\"Container command \\'kolla_start\\' not found or does not exist.\")\\n'"}16:33
inc0wirehead_, negative16:33
ccesarioinc0, eheheh well, I 'm confirming it with him (by email,he still not answer me)16:34
rhalliseywirehead_, no that would be host specific16:34
inc0this has to be available across the cluster16:34
*** Lyncos has joined #openstack-kolla16:34
wirehead_Yeah, that would only work for the mysql, mostly.16:34
rhalliseywirehead_, I'll have work on a patch after I finish lunch16:35
inc0even for mysql you want it in etcd16:35
rhalliseyI think it's better this way16:35
rhalliseydon't have to deal with passing around lock16:35
wirehead_So, there’s a thirdpartyresource that you could create to track the lifespan of the mysql cluster, but that’s beta.16:35
rhalliseyI also saw there are events16:35
*** inc0_ has joined #openstack-kolla16:35
wirehead_The other thing on my mental obsessiveness list was splitting the bootstrap into discrete pieces.16:36
LyncosHey guuys16:39
wirehead_rhallisey: OK, so, you are going to generate the next patch for mariadb bootstrap?  I had some stuff I wanted to do to Keystone and bootstrap.16:39
*** inc0 has quit IRC16:40
Lyncosnova-api-metadata is not implemented16:40
Lyncos?16:40
rhalliseywirehead_, ya let's work on the concept a little16:40
*** SiRiuS has quit IRC16:40
Lyncosthis was a question16:40
sdakewirehead_ re that other cat working on ceph16:45
sdakewirehead_ is he on irc?16:45
sdakewirehead_ if not, might as well get him here :)16:45
wirehead_sdake: dcwangmit01_16:45
inc0_Lyncos, isn't metadata served as normal nova api call?16:45
*** ravig has quit IRC16:46
sdakedcwangmit01_ mind sharing what your thinking is with ceph?  Kolla has a ceph implementation already built for bare metal but its not sacrosanct16:46
*** tyrola has quit IRC16:46
sbezverkrhallisey have you thought how to deal with keystone wsgi listen ip addresses?16:46
sdakeand by bare metal I mean it runs in containers on bare metal16:46
rhalliseysbezverk, remind me of the issue with it16:47
wirehead_I was thinking of setting mariadb and keystone to not use a host port but to be exposed merely as a kubernetes service and seeing what would happen.16:47
wirehead_Obviously this will break for some services.  :)16:48
wirehead_But at least mariadb and keystone ought to be more towards things that will be OK with kube networking.16:48
mag009_hey guys16:50
inc0_so folks important news16:50
inc0_just got email16:50
*** esimone has joined #openstack-kolla16:50
mag009_i believe you didn't test ansible 2.0.X with ceph16:50
inc0_we'll have 130 nodes from OSIC cluster between 7/22 and 8/1416:50
wirehead_But… there’s a clear use case for the control plane being on k8s.16:50
inc0_sdake,16:50
wirehead_How you set up the storage and compute nodes depends on the install.16:51
inc0_mag009_, I just failed on cinder conf so kinda yeah16:51
mag009_cinder I believe I fixed it16:51
mag009_the main problem is the ceph16:51
wirehead_Some folks are going to want to have the base layer be k8s, at which point ceph inside of k8s starts to make sense, albeit with a lot of potential circular dependencies.16:51
mag009_at the delegate part16:51
mag009_it try to ssh with no user16:52
mag009_I'm trying to figure this one out :)16:52
inc0_mag009_, ceph deployed no issues16:52
mag009_hm16:52
inc0_HEALTH_OK16:52
sdakeinc0_ midcycle is 7-12/7-1316:52
sbezverkrhallisey right now keystone wsgi file has two lines with ip address and ports where httpd will listen for authentications requests16:52
inc0_ansible 2.116:52
sdakeso that sounds great16:52
sdakeinc0 we can spend face to face time figuring out what to do with the nodes16:52
inc0_cool so at midcycle we can brainstorm all the tests16:53
sbezverkrhallisey current config generation put VIP there, which is not acceptable for k8s16:53
inc0_great16:53
sdakeinc0_ i'd like people to be prepared with ideas16:53
inc0_I'll send email on list16:53
sdakeinc0_ you read my mind :)16:53
sdakemention the midcycle, mention we are ogin  to brainstorm there, mention come prepared with ideas16:53
wirehead_Other folks are going to be OK with kicking off ansible to install ceph, k8s, and compute nodes.16:53
sbezverkrhallisey we need either to change it to 0.0.0.0:35357 or during the bootstrap process replace it with ip address assigned to keystone pod16:53
sdakemention the date of the midcycle as well pls16:53
sdakewirehead_ can't we use k8s to run compute nodes?16:54
wirehead_sdake: you can.16:54
sdakethere are already projects that install k8s16:54
sdakei'd prefer to just use them if they work and have a compatible license16:54
sdake(instal k8s using ansible)16:55
*** harlowja has joined #openstack-kolla16:55
wirehead_k8s using Ansible is going to be the standard installer in the future.16:55
sdakeright thatis the one i am tlaking about16:55
sdakeits called "saltstack 2.0" I guess ;)16:55
wirehead_Right now, it’s some messy salt stack where the best thing I can say about it is that it’s better than DevStack.16:55
sdakedeploying kubernetes is straightforward16:56
sdakea heat tempalte is already available for it16:56
sdakethat can be manually converted to ansible as a stopgap16:56
wirehead_sbezverk: see, that’s why I think we want to do 0.0.0.0 and a set port number, and then use kubernetes to map the port number of the container to the exposed port.16:56
*** huikang has quit IRC16:56
sdakei just dont want to be in the business of maintaining a k8s installer unless wee have to do so16:56
wirehead_Hell no.16:57
wirehead_That sounds like the worst of all possible futures. :D16:57
LyncosHeat template for  k8s  https://github.com/metral/corekube/blob/master/corekube-openstack.yaml16:57
Lyncos:-)16:57
sdakethe reason we don't bind to 0.0.0.0 is its a security risk16:57
sdakeLyncos i was talking about the one in magnum16:57
sdakei guess there is more then one :)16:57
sdakelike all good thigns in life16:57
wirehead_Does Keystone need to be HostNetwork?16:57
sdakedocker proxy is slower then a 28.8k modem16:58
inc0_mail sent16:58
sdakehttps://www.youtube.com/watch?v=PivpCKEiQOQ16:58
Lyncosahhh16:58
inc0_wirehead_, technically no16:58
mag009_inc0_: it worked if I remove delegate_to in distribute_keyrings.yml16:59
sbezverkwirehead_ if I remember right all pods are as per agreement16:59
inc0_so delegate to is there, because you might have external deploy host16:59
inc0_I'm not sure if it works this way16:59
sbezverkwirehead_ and specs17:00
wirehead_Yeah, I guess I’m going to wander in and play with the third rail, then. :D17:00
mag009_hm let me try something :)17:00
wirehead_For connecting to MariaDB and Keystone, my gut feel is that everything is going to go much more smoothly if we don’t make those HostNetwork.17:01
sbezverksdake since openstack services are internal to the cluster, maybe it is not that much of a risk?17:01
wirehead_For things like Nova and Swift, maybe other way around. :)17:01
sbezverkwirehead_ neutron as well17:02
wirehead_yah17:02
inc0_mag009_, one thing, I'm running ansible 2.117:03
inc0_maybe they fixed something17:03
mag009_same17:03
sdakehost networking is used for two reasons: performance and security17:03
sdakemany of the services could use a port bind17:03
sdakeand that would preserve security17:03
sdakebut performance would still be slower then the 28.8k modem linked above ;)17:03
sdakebut do whatever you think is right17:04
sdakewe can refactor later17:04
wirehead_They improved the proxy performance, after realizing that it was slower than a 28.8k modem.17:04
sdakeas long as we dont become religious about going to a hostnetworkingmode only later17:04
sdakewirehead_ it still blows17:04
sdakewirehead_ for a datapoint, mirantis uses ports in their docker implementation17:05
sdakeand all their customers complain about openstack performance17:05
inc0_so as for OSIC cluster one test I'd like to do is:17:06
sdake(not fuel performance)17:06
inc0_deploy kolla on 130 hardware17:06
mag009_I've found the problem17:06
inc0_run 1000 vms17:06
*** huikang has joined #openstack-kolla17:06
inc0_deploy kolla on 1k vms;)17:06
inc0_mag009_, do tell17:06
sdakeinc0 we should deploy at max capacity of the cluster17:06
sdakebut ya thats definately a test17:06
sean-k-mooneyinc0_: that would be cool to see.17:06
wirehead_docker networking != kubernetes networking.17:06
sdakewe could also use the gear to implement multi-region17:06
inc0_and cells17:06
mag009_i'm using a jenkins that create a docker with ansible on it as my deploy host17:06
sdakewirehead_ yes I know, I wrote the initial code for magnum17:07
sdakei am intimately familiar with kuberntes up to about 0.97 or so17:07
mag009_it fail that way17:07
mag009_but if I use the jenkins host as deploy host it work17:07
inc0_ahh shame, that was one thing I wanted to do too17:07
sean-k-mooneyinc0_: we are doning some testing with the fake driver currently. trying to emulate 250 fake nodes on a singel host and then run 2500 fake vms on top17:07
mag009_i don't know why it would fail tho... use to work with version 1.9.X17:07
mag009_seem they've changed the behaviour like you said17:08
inc0_sean-k-mooney, my real point is to run 1k node kolla cluster17:08
sdakeinc0 yu mean kolla on kolla?17:08
inc0_yeah17:08
sdakewe may have trobule getting ip addressing space17:08
sean-k-mooneyinc0_: yep that is why we are trying to get 250 fake compute nodes running so when we go to 4 physical nodes we can have 1K17:08
inc0_nah17:08
sdakebut that sounds good17:08
inc0_ip addresses will be all local17:09
sean-k-mooneyinc0_: when we had that running we want to then try it on the osic cluster17:09
inc0_sean-k-mooney, sounds like you want to participate in tests?;)17:09
inc0_(you are more than welcome to)17:09
mag009_inc0 i'll try to find a way to do it via a docker because it allow me to test different version of ansible etc.. in a docker17:10
sean-k-mooneyinc0_: perhaps. pritiv currently looking at this work17:10
*** sacharya_ has joined #openstack-kolla17:11
mag009_also i had some problem with the cleanup sometime the cleanup does not delete the ceph_mon_config volume17:11
*** salv-orlando has quit IRC17:11
sean-k-mooneyinc0_: we wanted to simulate the effect of controling nodes over a high latency link so after the kolla fake nodes are spawn we are in increaseing the latency using tc the using rally to spawn the fake vms17:11
*** salv-orlando has joined #openstack-kolla17:12
inc0_interesting, any good findings?17:13
*** sacharya has quit IRC17:13
sean-k-mooneynot yet but we will be happy to share when we do17:13
inc0_I'd expect rabbitmq to act up17:14
sean-k-mooneyam well we were haveing some good results initally17:14
inc0_mag009_, ad cinder.conf fail, did you publish any bugfix for that?17:14
sean-k-mooneywe have started hitting issue with running out of ram on the host17:14
*** esharao has quit IRC17:14
inc0_yeah, I'd expect that to be the case17:14
mag009_inc0: i'm testing it as we speak17:14
mag009_I think I have a fix17:15
mag009_not sure yet17:15
mag009_:D17:15
inc0_kk17:15
mark-caseyOSIC tests running kolla-ansible or k8s?17:16
inc0_I'd put priority on ansible17:16
inc0_but we might squeeze k8s in17:16
inc0_time permitting17:16
sean-k-mooneyinc0_: we got upto 250 fake compute nodes spawned on a singel host and were able to get 117:16
rhalliseyinc0_, if we're ready17:16
rhalliseywho knows17:17
inc0_yeha, that too17:17
sean-k-mooneyinc0_: we got upto 250 fake compute nodes spawned on a singel host and were able to get 1K fake vms spawned before we added latency17:17
sean-k-mooneyinc0_: but sorry did not want to derail the osic cluster topic17:21
inc0_sean-k-mooney, you didnt, anyway, we need to think how to make best use of this cluster17:22
sean-k-mooneyinc0_: out of interest did you make the request to use the cluster or was that done by someone else?17:23
inc0_I did17:24
sean-k-mooneycool i might ping you at some point about how to do that17:24
sdakefor access to gear time, k8s seems fine, I think the way we should approach it is people submit their ideas for tests with a time window, and we provide it - using the cluster around the clock since our team is highly distributed17:25
*** huikang has quit IRC17:25
sean-k-mooneythe osic cluster is part of the 2 500 node dataceneter intel and rackspace set up right? or is it a seperate cluster?17:26
*** dwalsh has joined #openstack-kolla17:27
sdakesean-k-mooney same thing17:30
sean-k-mooneysdake: cool thanks. i remeber hearing/reading about the anouchment but never really looked into it17:32
*** ravig has joined #openstack-kolla17:35
*** ravig has quit IRC17:38
wirehead_I watched the grand opening.17:43
*** d_code has joined #openstack-kolla17:43
*** v1k0d3n has quit IRC17:44
wirehead_sdake: The network improvements didn’t hit till 1.117:45
inc0_sean-k-mooney, yup, this one17:46
d_codeis Mauricio Lima or Paul Bourke or coolvsap here?17:46
d_codehad question on my patch17:46
inc0_mliima, pbourke ^17:47
d_codethanks17:47
d_codemliima or pbourke …regarding changing the SR-IOV patch to branch off master….  do I just rebase?17:48
d_codenevermind…I’ll just blow away my dir…then apply the patches to master and push back up17:50
d_codeI think17:50
sdaked_code do htis17:52
sdakegit  format-patch -117:52
sdakegit checkout master17:52
sdakegit am 0001*17:52
sdakegit review -s17:52
sdakegit review17:52
sdakeyou may need to rebase the other patch off of the stable branch17:52
sdaketo do that, git rebase -i17:52
sdakedelete the patch line17:52
sdaketype in "noop"17:52
sdakesave vi17:52
dcwangmit01_sdake: Are your referring to the ceph comment I made in https://review.openstack.org/#/c/304182/15 ?17:53
patchbotdcwangmit01_: patch 304182 - kolla - Spec: Deploy Kolla images using Kubernetes17:53
sdakedcwangmit01_ no I am talking to d_code17:54
sdakedcwangmit01_ oh you mean your ceph work17:54
sdakedcwangmit01_ wirehead_ said you were working on ceph in some indepenent fashion17:54
sdakeor maybe its part of kolla, I dont know17:54
*** eaguilar has joined #openstack-kolla17:55
mliimad_code, i'm here17:56
dcwangmit01_sdake: Yes.  I'm no expert on Ceph.  My work using it was to get ceph working for persistence, for my bare-metal kubernetes cluster.  Documented here: https://www.davidwang.com/2016/05/24/ceph-rbd-bare-metal-install-for-kubernetes-on-packet-net/ .  The existing ceph-ansible scripts work really well.17:56
d_codemliima: sdake gave me a direction….but I screwed up trying to do `git rebase -i master`….and….well….it’s a mess =)17:57
d_codebut…I”m working through it17:57
mliimad_code, ok :)17:57
mliimad_code, i'm sorry for the late17:58
dcwangmit01_sdake: The kolla-kubernetes spec mentioned Ceph, but it was unclear if it was a Ceph cluster on top of Kubernetes, or a distinct and separate cluster from Kubernetes17:58
openstackgerritMerged openstack/kolla: Use debian repos for debian base docker image  https://review.openstack.org/28893617:59
*** zhiwei has joined #openstack-kolla18:00
d_codeso…trying to apply that patch… looks like nova-libvirt and nova-compute now include mounting /dev completely....18:02
d_codefor SR-IOV we only need /dev/vfio18:03
d_codesoo….is it possible to backport that mount to mitaka?18:03
d_codeshould I skip that and just merge my docs for SR-IOV?18:03
*** zhiwei has quit IRC18:04
LyncosGuys.. how metadata is handled in kolla ?18:04
LyncosI don't see any metadata container18:05
d_codeLyncos: wrt to instance / flavor metadata?18:05
LyncosI'm talking about cloud-init stuff18:05
LyncosI think it need a  nova-api-metadata or something .. because sending the metadata requests to nova-api dosen't seems to work18:06
d_codeyeah…I believe all that goes into the mysql database18:06
d_codemariadb18:06
d_codeI know flavor metadata is stored in the database18:06
LyncosAnyone can do a test for me ?18:06
mark-caseysdake: inc0_: if you get time for k8s on OSIC I'd very highly recommend beating up the database a bit. I suppose I can get on board with the single node db plan :D, but keep in mind galera reads scale linearly to cluster size. Compared to a kolla-ansible cluster of the same size you're already down to a fraction of the query processing you had, and then running it over a distributed disk with a double-write penalty18:06
openstackgerritDerek Ditch proposed openstack/kolla: Adds documentation of how to perform SR-IOV  https://review.openstack.org/32544018:07
LyncosI would like someone to test deploying Coreos with a specific  cloud-init file to see if it works.... our deployment is a bit different as we are using calico I would like to know where it is failing18:07
LyncosPlease deploy Coreos instance with following cloud-init      http://paste.openstack.org/show/507811/     and paste me   /run/systemd/system/etcd2.service/20-....18:08
d_codemliima: kk..I pushed the docs to review off master18:08
d_codehttps://review.openstack.org/32544018:08
d_codenot sure….are the other patches just ignored?18:09
mliimad_code, we don't backport doc changes to stable branches in kolla18:10
d_codeso, it’s not the doc that needs backported…it is the same18:10
d_codethe issue is the mount18:10
mliimathis ps isn't needed https://review.openstack.org/#/c/322334/18:10
patchbotmliima: patch 322334 - kolla (stable/mitaka) - Adds documentation of how to perform SR-IOV18:10
d_codemitaka doesn’t have /dev/vfio mounted in nova-libvirt18:11
sean-k-mooneymark-casey: in the k8s setup will there be a single db per serivce or one total? similar question for rabbit18:11
mliimaok, i know d_code18:11
mark-caseyI dunno. I only kinda jumped in on another discussion. kinda been lurking on k8s18:12
mark-caseysean-k-mooney: ^^18:12
d_codek…I abandoned that change, mliima18:12
mliimabut you don't need do a backport of documentation18:12
mliima:)18:12
sean-k-mooneymark-casey: :) no worries same18:12
mark-caseysean-k-mooney: I think one total18:12
d_codemliima: agreed. it was a failure of my understanding of the process. That’s been fixed from the PS18:13
d_codes/fixed/removed/18:13
sean-k-mooneyinc0_: not sure if you are still about but in the summit discusstion you were suggesting using one rabit instance per servce for k8s. would we do the same for the db?18:13
d_codeI thought18:13
d_codedang18:14
mliimacan you abbandon this ps https://review.openstack.org/#/c/322334/ ?18:14
patchbotmliima: patch 322334 - kolla (stable/mitaka) - Adds documentation of how to perform SR-IOV18:14
mliimaThis ps https://review.openstack.org/#/c/325440/1 It will be the "official"18:15
patchbotmliima: patch 325440 - kolla - Adds documentation of how to perform SR-IOV18:15
d_codek.. fixed18:16
d_codeI’m a github guy…I like the organization Gerrit provides…but it’s a bit counter-intuitive for me at the moment18:16
kklimondawhat would be the correct way to add support for nfs backend for nova instances? the only nfs related work I see so far is https://blueprints.launchpad.net/kolla/+spec/nfs-support-in-cinder18:17
*** daneyon_ has joined #openstack-kolla18:19
*** MarMat has joined #openstack-kolla18:20
*** eaguilar has quit IRC18:20
mliimad_code, don't worry :)18:21
inc0_sean-k-mooney, here18:22
inc0_well, yeah18:22
inc0_that's the model we want to pursue with k8s18:22
*** huikang has joined #openstack-kolla18:22
inc0_for both db and rabbit18:22
*** d_code has left #openstack-kolla18:23
*** d_code has joined #openstack-kolla18:23
sean-k-mooneykklimonda: are you refering to adding support for nfs root or just having nova using an nfs share for its ephemeral instance storage?18:23
*** thumpba has joined #openstack-kolla18:23
kklimondasean-k-mooney: just nfs share for ephemeral instance storage18:24
inc0_kklimonda, well, you can do this by putting /var/lib/docker/volumes/nova_data on nfs18:24
inc0_on host level18:24
inc0_I don't think we'll support it in kolla anytime soon18:25
sean-k-mooneyinc0_: yep that was what i was thinking too18:25
inc0_still possible now with a bit of host tinkering18:25
inc0_nova_compute is the name of volume18:26
*** daneyon_ has quit IRC18:26
inc0_but that should work18:26
sean-k-mooneyinc0_: well it depends on the storage diriver you are using though correct18:26
inc0_I don't think so18:26
inc0_volumes are storage-agnostic I think18:26
sean-k-mooneyinc0_: if you are using aufs or overlay fs it should work18:26
inc0_it's just a dir18:26
kklimondaok, that's what I was thinking of doing in the first place - is there anything I should be aware of when doing that, or no one has done it yet and lived to tell the tale? ;)18:27
inc0_kklimonda, noone I know did that;)18:27
*** mgoddard has quit IRC18:27
inc0_but you're free to try;)18:27
mag009_inc0_: I've fixed the problem with cinder but i'm just trying to fix another problem before I submit the patch18:27
mag009_to retest it18:27
inc0_I'd say use ceph if on prod, but well...18:27
inc0_kk, thanks mag009_18:28
inc0_one thing I need to check out is if nova compute puts libvirt xmls in volume too18:28
kklimondaI don't really have hardware for ceph - it's a weird deployment where compute nodes have only 1 drive, and space for only one more, and yet there is no shared storage to speak of..18:29
*** cu5 has quit IRC18:29
inc0_kklimonda, so you can still play around it18:29
sean-k-mooneyinc0_: kklimonda  one ting to keep in mind is that placing /var/lib/docker on nfs probably wont work with the btrfs storage driver just incase you plan to use it18:29
inc0_not with vanilla kolla, but possible18:29
inc0_sean-k-mooney, might work still, just you'd need to have separate partition for /var/lib/docker/volumes18:30
kklimondasean-k-mooney: I'll be using aufs probably - seems to be working better than devicemapper, and I don't really have experience with btrfs to use it.18:30
inc0_put it in ln -s or sth18:30
inc0_not sure18:31
inc0_kklimonda, aufs is *way* better than devicemapper18:31
inc0_btrfs is a little better than aufs18:31
inc0_but aufs works well18:31
inc0_well enough18:31
sean-k-mooneykklimonda: ya aufs should work fine18:31
sean-k-mooneythe btrfs comment relates to the fact that the btrfs driver requires the file system of /var/lib/docker to be btrfs18:32
inc0_yeah, but agian you could mount /var/lib/docker/volumes on nfs I think18:32
inc0_it's hacky but works18:32
inc0_and kklimonda ceph can be configured to use file as OSD18:33
sean-k-mooneyinc0_: ya that might work just never tried it18:33
inc0_not right now with kolla, but should be doable with a bit of tinkering18:33
inc0_or a partition18:33
kklimondainc0_: but it's still going to be 42 7200rpm drives, I'm not sure how much performance I can get out of it18:33
inc0_well, sure18:34
inc0_but you get data persistence;)18:34
inc0_well, decision you guys need to make, just saying it's possible and I'd at least cosider it18:34
inc0_other than that, try nfs hack I described, should work just fine18:35
sean-k-mooneykklimonda: you would be serprised how well ceph works if you add an ssd cache teir even a small one in front of slow disks18:35
kklimondasean-k-mooney: I'd be surpsised, because all testing I've done so far wasn't that promising ;)18:35
inc0_that too, if you'd fill remaining disk slot with even small ssd it might go rocket18:35
inc0_kklimonda, issue is, you'd want journal on ssd18:36
kklimondaare we talking about ceph cache tier, or a journal on ssd?18:36
inc0_you can do both18:36
inc0_partition ssd for journal and cache18:36
kklimondamhm, that could work18:36
inc0_and use both over spindle18:36
sean-k-mooneykklimonda:  i was refering to a ssd cache tier18:37
inc0_sean-k-mooney, you want fast journal regardless18:37
sean-k-mooneybut moving the journal to an ssd also helps18:37
inc0_so issue with kolla currently is it only understands block devices18:37
inc0_because we use udev for that18:37
inc0_but I have it in my backlog to enable other options for OSD too18:38
kklimondahow many ceph nodes should I have to really test it out?18:38
inc0_well, you need at very least as much as replication factor18:38
inc0_so I believe 3 osd18:38
mag009_inc0_: did you had problem with neutron sysctl ?18:38
sean-k-mooneykklimonda:  you can test with one but its really depends on what you want to test.18:38
inc0_mag009_, not yet, I'm waiting for cinder fix;)18:38
inc0_one will not produce relevant data18:39
inc0_you can get it to stand up with 118:39
inc0_it will even work18:39
inc0_but replication changes things18:39
kklimondasean-k-mooney: I'd really like to see how well will performance scale as I keep adding nodes18:39
*** ppowell has quit IRC18:39
inc0_yeah, sure, ceph handles that well18:39
*** ppowell has joined #openstack-kolla18:40
inc0_so my suggestion, get an ssd for your nodes and deploy ceph18:40
sean-k-mooneyinc0_: you can change the replication policy to the osd level to have replication with a singel node but it sounds like kklimonda would be better with multinode18:40
inc0_you might want to put cgroup limit on cpu on OSD if you want same node to be shared with compute services18:40
inc0_OSD can be cpu hungry18:40
inc0_sean-k-mooney, as I said, you can make it work, just not a relevant data would come out of it;)18:41
inc0_I suggest playing with ceph more, I became a fan;)18:41
sean-k-mooneyinc0_: ceph experts would hate my home setup hehe but it works for my usecase :)18:42
inc0_it's a home setup;)18:43
inc0_what I'd like to see is ceph with NVMe cache18:43
inc0_sdake, you have NVMe right?18:43
sean-k-mooneyinc0_: what i want to see is ceph running on xpoint when that launches18:44
kklimondaheh, I have two nvme drives just lying around - but I can't get them into this cluster ;)18:44
inc0_yeah, that would go skyrocket18:44
inc0_<< storage porn >>18:45
sean-k-mooney:)18:45
*** stvnoyes has left #openstack-kolla18:45
openstackgerritMarc-Andre Gatien proposed openstack/kolla: adding else statement with empty string, starting ansible 2.X it require a else statement.  https://review.openstack.org/32548318:48
Mech422sean-k-mooney: thats why I only put a single small SSD on my nodes - waiting for xpoint...18:49
mag009_inc0_: i just submitted it18:49
sdakeinc0_ of coure - best tech i've bought in years18:49
sdakei have a 4tb disk in each machine and 400gb PCIE intel 750ssd18:50
inc0_sdake, we can do some crazy fast ceph with that18:50
*** eaguilar has joined #openstack-kolla18:50
sdakein my main workstation i have a 1.2tb pcie nvmessd18:50
sdakeinc0_ do you need to test?18:50
sdakeinc0_ if so I can givey ou an ssh login18:51
* Mech422 has storage envy...18:51
inc0_don't have time, but someday sure18:51
sdakeinc0_ cool ya I dont have time to do much - my review queue outstanding is down to 1 page ;)18:51
sdakeso I'd like to make progress on that18:51
inc0_dayjob takes its toll, but yeah someday I'd love to try out exactly how fast ceph can be18:52
sdakeinc0_ my gear also has intel 10gb nics18:52
sdakeonly one port is connected though as I have only 1 8 port switch18:52
inc0_yeah, vxoffloading <318:52
sdakeinc0_ ceph can be run single node18:52
inc0_sdake, can be run != should be run'18:53
inc0_it's as much value as aio k8s;)18:54
inc0_and I said today what's aio k8s;)18:54
sdakeinc0_ yees but it is testable as aio :)18:54
sean-k-mooneyinc0_: you can still have data redundency with singel node ceph18:54
sdakei have 3 nodes i can make immediately available if someone wntas to test18:54
sdakethe problem is my home partition is on the ssd18:54
sdakesorry the boot partition18:54
sean-k-mooneyinc0_: but if that one node goes down then its all offlien18:55
sdakeand last I heard, ceph doesnt work with partition tables18:55
inc0_sean-k-mooney, well...I know you can do that18:55
sdakealthough someone today linked a blog about making it work18:55
sdakebut sam said it was impossible18:55
sdakeand its sam's blog18:55
sdakeso who knows :)18:55
sean-k-mooneysdake: ceph can work with partitions but the kolla code does not supprot that currently18:56
sdakeyes that is what i mean18:56
sdakeI think sam's blog post has some info about making it work18:57
sdakebut I didn't read it18:57
mag009_mliima: i need to open a bug in the launchpad?18:57
sdakebecause frankly, I am tired of reading18:57
*** ppowell has quit IRC18:58
inc0_sean-k-mooney, it can even be run with file on disk18:59
sean-k-mooneyah the joys of waithing for devstack to finish. its almost as fun as watching code compile18:59
inc0_don't use devstack:(18:59
mliimamag009_, yes, but if it is not necessary to make a backport this ps, add only one TrivialFix.18:59
sean-k-mooneyinc0_: im a maintainer of a devstack plugin so i have to ocationally18:59
inc0_mliima, it is not as mitaka is ansible 1.919:00
inc0_and this is 2.0 issue19:00
mliimaoh19:00
sean-k-mooneyinc0_: if its any concilation its running in a vm hosted on kolla19:00
inc0_:D19:00
mag009_i just filled a bug report in the launchpad now -_-19:00
mag009_I was about to ammend my comment with it19:00
mliimaso, a TrivialFix is enough inc0_ mag009_19:00
inc0_mag009_, it's ok, it's always better to do it with bug19:00
mliimadon't worry mag009_19:01
inc0_TrivialFix is our kolla specific way to avoid creating bugs and such for every-single-thing19:01
inc0_however as mliima said, if you need to backport it, you need bug19:01
mag009_how do I tag it as trivialfix ?19:01
mliimadid you report a bug?19:02
inc0_mag009_, just add TrivialFix to commit message19:02
mag009_yes ah ok19:02
mag009_for this one I'll report it as a bug19:02
inc0_but if yuou added bug, make it Closes-bug: #numberofabug19:02
inc0_you'll get launchpad elo points for reporting and closing a bug;)19:02
openstackgerritMarc-Andre Gatien proposed openstack/kolla: adding else statement with empty string starting ansible 2.X it require a else statement.  https://review.openstack.org/32548319:03
mag009_lol19:03
mliimamag009_, follow inc0, he knows things19:03
inc0_hehe19:03
mag009_there you go19:03
mag009_I'll get it... the more I do19:03
openstackgerritRyan Hallisey proposed openstack/kolla: Add kolla-kubernetes bootstrap capability to mariadb  https://review.openstack.org/32074419:04
inc0_sure19:04
mag009_still a new problem now with neutron sysctl19:05
inc0_harlowja, ping19:06
inc0_mliima, I've put +w on mag009_ patch19:08
inc0_if gates fail, it won't merge anyway19:09
mliimaI did not know that inc0_19:09
mliimacool19:09
inc0_well, I take that back, we don't have voting gates19:09
inc0_but if we'd have it still goes through gates before merge19:10
*** mark-casey has quit IRC19:10
wirehead_Complaining about the OpenStack gate is pretty much how we start conversations.  Like complaining about the weather in London.19:10
inc0_wirehead_, I've been to London, now I'm in Texas19:10
inc0_trust me, latter is worse19:10
inc0_and I'm talking about rai19:10
inc0_n19:10
wirehead_Well, it’s always been beautiful when I’ve visited London.19:11
wirehead_By comparison, I was in San Antonio last year and drove through a torrential downpour that was the most rain I’ve ever traversed.19:11
wirehead_Given that it’s been nice ever time I’ve visited Seattle, I suspect the tourism boards are investing in weather control.19:12
inc0_mag009_, with your patch full deploy succeeded19:12
inc0_ubuntu 15.10 on host and ansible2.119:13
mag009_hm i'm still having issues..19:13
inc0_wirehead_, I live in San Antonio. We have storm every day at least19:13
inc0_yesterday we had 3 storms19:13
inc0_aaaand I see next one comming19:14
mliima3?19:14
inc0_yeah19:14
inc0_3 storms in same day19:14
inc0_full package, downpour, thunders, wind19:14
sean-k-mooneywe got pretty lucky for the summit so19:14
inc0_yeah you did19:14
inc0_like month before summit we got hailstorp19:14
wirehead_So, the entire time I worked at Rackspace and therefore had to visit SAT frequently, it was drought and thus no storms.19:14
inc0_size of tennis ball19:14
mliima3 in same day19:15
mliimaman19:15
mliimarun man, run!19:15
inc0_couple kms from San Antonio there was hail of size of grapefruit19:15
*** salv-orl_ has joined #openstack-kolla19:15
inc0_FUCKING GRAPERFUIT-SIZE CHUNKS OF ICE FALLING FROM THE SKY19:16
inc0_pardon my language19:16
wirehead_Hee hee hee.19:16
wirehead_Hail and freezing rain are mother nature giving you the middle finger.19:16
sean-k-mooneybeing in ireland we dont really ever get really bad weather but we also dont really get really great weather. its been in the mid 20's for the last week though so cant complain too much19:17
*** zhiwei has joined #openstack-kolla19:17
inc0_mid 20's is my favorite19:17
inc0_here it's already 30+19:17
wirehead_Rain, fine.  Snow, fine.  Hail hurts and freezing rain is really quite dangerous.19:17
inc0_gets up to 4519:17
inc0_in summer19:17
*** salv-orlando has quit IRC19:18
inc0_wirehead_, if hail makes holes in cars windshields it also might hurt19:18
inc0_https://www.google.com/search?q=san+antonio+hail&num=50&tbm=isch&tbo=u&source=univ&sa=X&ved=0ahUKEwjm85G4yYzNAhVS2GMKHZrZCDcQsAQIUA&biw=1920&bih=97119:18
wirehead_Yeah, I’ve had itty-bitty hail land on me and that was painful.19:19
wirehead_I do NOT want to get hit by grapefruit hail.19:19
wirehead_Also, tornadoes are a particularly American form of extreme weather.19:19
mliimapardon inc0_ https://www.google.com.br/search?q=jericoacoara+beach&source=lnms&tbm=isch&sa=X&ved=0ahUKEwjpyKHWyYzNAhXFKB4KHXfZB10Q_AUIBygB&biw=1920&bih=95519:19
mliima:P19:19
inc0_mliima, you live there?:P19:20
mliimasame state19:20
inc0_mhm...soooo...I think we have place for O midcycle19:21
mliimahahaha19:21
*** daneyon_ has joined #openstack-kolla19:21
sean-k-mooneyinc0_: +1 lol19:21
inc0_I don't even need venue, we'll buy a whiteboard and set it up on a beach19:22
*** zhiwei has quit IRC19:22
wirehead_I’m envisoning sunburned nerds.19:22
mliimainc0_, +219:22
mag009_+1 for the beach19:22
sean-k-mooneyinc0_: on a beach we just need a stick to draw in the sand19:22
wirehead_Also, season reversal.19:23
*** thumpba_ has joined #openstack-kolla19:26
*** daneyon_ has quit IRC19:26
wirehead_rhallisey: how’s that for rapid review turnaround? :)19:27
*** thumpba has quit IRC19:28
rhalliseywirehead_, I was going to ask19:28
rhalliseysince whatever I do , the hash gets added19:28
mag009_inc0_: do you pass vars in your inventory ?19:30
*** Jeffrey4l_ has quit IRC19:30
*** godleon has joined #openstack-kolla19:31
wirehead_rhallisey: Like, I’m wondering if we’re going to end up with a lightweight kube client, either the official kubectl, or somehing smaller and python, embedded in the Kolla images.19:33
rhalliseywirehead_, what would we being doing with the client?  Using the endpoint is fine so far at least19:34
*** Jeffrey4l_ has joined #openstack-kolla19:35
inc0_mag009_, I do not, but technically you could19:36
inc0_I think;)19:36
mag009_i know but I'm trying to find why it work on your end19:37
wirehead_rhallisey: If we reach the point where it isn’t.19:38
mag009_I'm stuck at neutron it fail at the when: condition of the start19:38
wirehead_rhallisey: At this stage of abstraction, we seem to be fine19:38
inc0_mag009_, did you rebuild containers lately?19:38
mag009_nop19:39
inc0_I have code from today and containers freshly19:39
inc0_built19:39
inc0_try that19:39
inc0_get lates greatest master and do full rebuild19:39
mag009_i'll try that on monday.. I did some patch to support calico19:40
mag009_i need to rebase stuff19:41
inc0_yeah19:41
inc0_it might be disconnect between container versions and code19:42
inc0_first thing you do when you hit somethign liek that is to make sure all containers are rebuilt and fresh19:42
inc0_also use --no-cache flag19:42
mag009_ok19:42
rhalliseywirehead_, ok19:46
rhalliseywirehead_, what do I need to do exactly get have the job get a name19:46
rhalliseyI've added mariadb-bootstrap everywhere I coudl19:47
wirehead_rhallisey: should be available as mariadb-bootstrap.19:47
wirehead_rhallisey: but remember, the job will delete itself after it completes.19:48
rhalliseyit sadly adds a hash19:48
rhalliseyidk if it's possible to have a job without a hash19:48
wirehead_hmmm19:48
openstackgerritMerged openstack/kolla: Add vars to the merge_config task in config-neutron-fake.yml  https://review.openstack.org/32513919:48
rhalliseyI mean the search I have works fine19:48
rhalliseybut ideally we would apply a known name19:49
rhalliseywirehead_, also re your comment, the point is to allow someone to come along later and run the bootstrap again19:50
rhalliseythat's how the upgrade will happen19:50
rhalliseyI mean I guess we could have some logic saying 'you're upgrading now so it's ok to bootstrap'19:50
rhalliseybut I think operators will want more control than that19:50
openstackgerritMerged openstack/kolla: Updated from global requirements  https://review.openstack.org/32545419:51
*** rahuls has joined #openstack-kolla19:51
openstackgerritRyan Hallisey proposed openstack/kolla: Add kolla-kubernetes bootstrap capability to mariadb  https://review.openstack.org/32074419:51
wirehead_rhallisey: http://localhost:8080/apis/extensions/v1beta1/namespaces/default/jobs/mariadb-bootstrap19:52
*** rahuls has quit IRC19:52
*** rahuls has joined #openstack-kolla19:53
rhalliseywirehead_, perfect thank you19:54
*** mliima has quit IRC19:54
openstackgerritMerged openstack/kolla: Install keepalived in neutron_l3_agent container  https://review.openstack.org/32531619:54
mag009_when its a new feature do I need to use TrivialFix?19:56
rhalliseywirehead_, I see, pod applies a hash. But if you search more specifically you get the name19:56
wirehead_rhallisey: Yeah, the hash changes as the pod gets rescheduled.19:56
mag009_inc0_: I was able to pass my problem by commenting out the when: in neutron19:57
mag009_everything when fine after19:57
mag009_went*19:57
wirehead_rhallisey: So when we kill nodes on our kube cluster, the rescheduled instances of our software get a different hash because it’s really a new instance19:57
mag009_I'll try on monday like you said19:57
wirehead_rhallisey: (emptyDir volumes cleared, for example)19:58
rhalliseywirehead_, there an issue though, this doesn't have state19:58
wirehead_rhallisey: So, this depends on how deep we want to go.19:59
rhalliseywe could add it..19:59
-openstackstatus- NOTICE: The infrastructure team is taking Gerrit offline for maintenance this afternoon, beginning shortly after 20:00 UTC. We aim to have it back online around 00:00 UTC.19:59
openstackgerritRyan Hallisey proposed openstack/kolla-kubernetes: Use the Kube endpoint to dictate state instead of etcd  https://review.openstack.org/32550320:00
*** ravig has joined #openstack-kolla20:01
rhalliseywirehead_, ya we need some form of state, otherwise we have to manage it ourselves20:01
wirehead_rhallisey: We can change the state after each operation and thus return to the macro-block where we were.20:01
*** absubram has quit IRC20:01
rhalliseyya :/20:01
wirehead_rhallisey: except that you’d better make the macro-block safe and idempotent.20:01
rhalliseythe hash bit could break is you had multiple bootstrap jobs running20:02
rhalliseythat might not be possible though because of naming20:02
rhalliseyI'm not sure what's better to go with here20:02
wirehead_rhallisey: Well, I think that you get some protections with the job.20:02
wirehead_rhallisey: Yeah, just verified.20:03
wirehead_If you try to create two jobs with the same name, the second one will fail.20:03
rhalliseyyou also get some protections from the pod.  Kubernetes manages the state vs the contianer20:03
wirehead_rhallisey: Yeah, we need to protect the user (potentially) form a hazardous opperation that is trying to bootstrap a running system.  And we need to make sure that the job completes fully.20:04
rhalliseywirehead_, well I think it's ok if the user bootstraps a running system20:04
rhalliseyI mean that would be an upgrade step20:04
rhalliseyI think we have to trust the operator on that one20:05
rhalliseybut also give them the freedom to handle a strange case that needs a bootstrap suddenly20:05
wirehead_rhallisey: Yeah20:06
wirehead_rhallisey: So, the main purpose of the patch we’re talking about is less about mariadb bootstrapping and more about only running the steps we need to if the bootstrap halts mid-process.20:07
openstackgerritMerged openstack/kolla: Use --subproject instead of deprecated --service option  https://review.openstack.org/32286220:07
*** eaguilar has quit IRC20:09
-openstackstatus- NOTICE: Gerrit is offline for maintenance until 00:00 UTC20:09
*** ChanServ changes topic to "Gerrit is offline for maintenance until 00:00 UTC"20:09
inc0_ok, going off then;)20:10
inc0_have a good weekend folks20:10
wirehead_rhallisey: GAH20:11
mag009_see you monday20:11
wirehead_rhallisey: OK, got it in just as they announced it.20:11
*** unicell1 has quit IRC20:12
*** unicell has joined #openstack-kolla20:12
sean-k-mooneyinc0_: enjoy the weekend20:13
wirehead_rhallisey: but, yeah, Kubernetes is careful about injecting it’s own config into the environment so we don’t have to.20:14
*** inc0_ has quit IRC20:14
mag009_question why the neutron-base include dnsmasq???20:20
mag009_shouldn't it be on the dhcp-agent image instead ?20:20
dcwangmit01_rhallisey: Gerrit is down, and I've got a few uncommitted comments to the kolla-kubernetes spec.  Hoping to get them into the current patch-set.20:31
*** ravig has quit IRC20:31
*** eaguilar has joined #openstack-kolla20:33
*** ravig has joined #openstack-kolla20:36
rhalliseydcwangmit01_, ok thx20:37
rhalliseywirehead_, I got to run.  I'll catch up later20:37
rhalliseyI'll be around tmr20:38
*** rhallisey has quit IRC20:38
*** jtriley has quit IRC20:39
*** ravig has quit IRC20:39
*** unicell has quit IRC20:41
*** unicell has joined #openstack-kolla20:42
*** ravig has joined #openstack-kolla20:44
*** ayoung has quit IRC20:44
*** ravig has quit IRC20:45
*** ravig has joined #openstack-kolla20:46
*** d_code has quit IRC20:46
*** ravig has quit IRC20:55
*** mbound has joined #openstack-kolla21:03
*** huikang has quit IRC21:04
*** dwalsh has quit IRC21:06
*** salv-orl_ has quit IRC21:06
*** salv-orlando has joined #openstack-kolla21:07
*** mbound has quit IRC21:11
*** eaguilar has quit IRC21:11
sdakemag009_ i think you are right but it woud require testing21:14
*** ravig has joined #openstack-kolla21:16
sdakewell i guess everyone is gone21:16
dmsimardI'm still here21:17
*** ravig has quit IRC21:17
sdakei was going to work on the customization this afternoon21:17
dmsimard:P21:17
sdakebut gerrit is bust21:17
sdakehey dmsimard21:17
sdakeoh to look at ara21:17
sdakemoment let me pull up that tarball21:17
sdakedmsimard why are some tsks missing names in the output?21:18
sdakelike .../share/kolla/ansible/site.hyml21:18
sdakea a whole buncho f tasknames are missing but it has the action21:18
sdakethe first one is setup for eg21:18
*** fragatin_ has joined #openstack-kolla21:19
dmsimardansible doesn't enforce naming tasks21:19
dmsimardyou can have - debug: msg: foo or - name: blah debug: msg: foo21:19
dmsimardthat looks weird inline, hope you understood that21:19
dmsimardso there's really nothing else to show in the name column if the task doesn't have a name21:20
*** harlowja has quit IRC21:20
sdakeso your syaing some of our tasks dont have names?21:20
* dmsimard nods21:21
sdakecommon patterns appear around include and setup21:21
sdakeshould those types be named?21:21
dmsimardsetup can be called from - name: blah setup: and this will be named21:22
*** fragatina has quit IRC21:22
dmsimardbut setup is also implicitely called from gather_facts: true21:22
dmsimardand that one can't be named21:22
dmsimardincludes can be named but are not commonly named21:22
dmsimardor at least I think they can21:22
sdakerecommended featuer - filter tasks21:22
sdakeonly display those with a name21:23
sdake(or specific actions)21:23
sdakejust brianstorming here :)21:23
dmsimardyeah sure, I'm all for feature ideas21:23
sdakei cnat help with implementation but it looks like an interesting tool21:23
dmsimardwe actually had something similar in the alpha21:23
dmsimardbut it was lost in refactoring stuff21:23
dmsimardyou could click on a particular task and you could see all the results for that task21:24
dmsimardacross playbook runs21:24
*** ravig has joined #openstack-kolla21:24
sdakeso this is sort of related to ara21:25
sdakewe at some point want to build a cli that produces some kind of useful output21:25
sdakethe current ansible run stuff produces absolute shit21:25
sdakeI mean i guess its thorough21:25
dmsimardwhat kind of useful output are you after ?21:26
dmsimardara has a CLI client as well21:26
sdakei am not exactly sure21:26
sdakesomething more concise21:26
dmsimardsec, I can show you.21:26
sdakewhen I run a playbook I don't wnat ot see 312 tasks21:26
sdakeI ust want to see "mariadb deployed - then nova deployed or whtever"21:27
sdakeso I'm wondering how you implemented ara21:27
sdakethis probably wouldn't be helpful for you21:28
sdakebut would be helpful for me21:28
sdakeInstead of seeing each speciic task, i just want to see each role21:29
*** ravig has quit IRC21:30
dmsimardsdake: here: https://asciinema.org/a/4a3zmdr8oyttjwzt7dowr7jor21:31
dmsimarda quick view21:31
dmsimardand it's built on the same framework as openstackclient, so you have things like "-c <column>" to filter by column and stuff like "-f <json>" to output in json instead out of the box21:32
*** ravig has joined #openstack-kolla21:32
*** zhiwei has joined #openstack-kolla21:33
dmsimardI wonder if there's a way for us to detect the roles that are used21:33
dmsimardThat would be helpful indeed.21:34
sdakehow I want to use it is to live output21:35
sdakeor use the tech you have21:35
dmsimardnot sure I follow21:37
dmsimardyou want to ditch the current ansible "streaming" output and replace it by something else ?21:37
sdakeas kolla runs, I want to do soething like [Deploying Openstack - Major area [20% done]]21:37
sdakeroger21:37
sdakei want oth21:37
sdakeboth21:37
dmsimardthe way to do that would be through a callback of sorts21:38
*** zhiwei has quit IRC21:38
dmsimardfor example we use this: https://github.com/rdo-infra/weirdo/blob/master/playbooks/library/human_log.py21:38
dmsimardthis takes the output that ansible prints and prettyprints it so it's not inline json nonsense21:38
dmsimardyou could have a callback that knows how many tasks there are in the playbook (somehow) and calculate progress21:39
dmsimardand print that progress.21:39
sdakedmsimard instead of a logging tool21:42
sdakecould this be turned into a gui to display progress?21:42
sdakeor could that be a feature?21:42
dmsimardyou mean if ara could somehow print the progress of the playbook ?21:43
sdakeyes21:43
dmsimardIt'd be a nice feature, I think, though out of scope21:43
sdakea one pager21:43
sdakeya - like I said you may not be interested :)21:43
dmsimardNo, don't get me wrong, I'm interested in something like that21:43
dmsimardBut not in ARA proper21:44
sdakewhere would it go?21:44
*** huikang has joined #openstack-kolla21:44
dmsimardAn ansible callback plugin by itself21:45
dmsimardhowever, I don't think it's possible for Ansible to know how many tasks it will have to run before going through the entire playbook21:45
dmsimardi.e, dynamic includes based on conditions that have not yet been evaluated21:45
dmsimardSo, perhaps there would be a use case for sneaking that into ara because once a playbook has been run once, we can reasonably estimate how long it will take and how many tasks there will be21:46
sdakednsso the plguin tells the web gui how?21:46
dmsimardbut ara wouldn't be able to tell on the first run21:47
sdakewell i'm good with a hardcode if we do something on our own21:47
sdakei am just trying to figure out how this thing works :)21:47
dmsimardCallbacks are hooks that Ansible calls on every event, there are hooks called like "task_on_ok", "task_on_failed" and so on. ara uses these to record events in a database but you can do anything you want with them, really21:48
dmsimardSo, when a task completes, you could print("%s/%s tasks complete" % current_task_number, total_task_number)21:48
dmsimardand it'd print that on top of the output ansible prints on every task output21:49
*** huikang has quit IRC21:49
sdakeso you write it to a database directly from ansible?21:49
*** huikang has joined #openstack-kolla21:49
*** ravig has quit IRC21:50
dmsimardthat's what ara does, yeah: https://github.com/dmsimard/ara/blob/master/ara/callback/log_ara.py21:50
dmsimardWe have sqlalchemy models and the callback adds and commits stuff21:50
sdakeplguin idea is alot cleaner then I had21:51
sdakewhich was to hardcode a number on every task21:51
sdakeand use tha to figure out wher ewe were in the deploy21:51
dmsimardthe hard part is knowing how many tasks you're going to run21:51
dmsimardwhich is not really possible21:51
sdakeyou mean because some are skipped21:52
dmsimardsome are skipped, some are dynamic (only included when certain parameters are set)21:52
dmsimardansible doesn't know ahead of time how many tasks it's going to run21:52
*** ravig has joined #openstack-kolla21:52
sdakei'd be satiified with an estimate - i.e. a hardcode21:52
dmsimardthat's why I said ara has a rough amount of knowledge after a playbook after it's been run at least once so it could provide some feedback *maybe*21:53
sdakei dont know how I feel about writin to a database though on the deploy host21:53
dmsimardin the context of kolla it could be sent to the logging container21:53
sdakespecifically for a GUI21:53
dmsimardbut you don't *need* to write to a database to do stuff like this21:53
sdakeyes i just jumped rom cli to gui21:54
*** dave-mccowan has quit IRC21:54
sdakedmsimard is this the ara plulgin https://github.com/dmsimard/ara/blob/master/ara/callback/log_ara.py21:56
sdakeor is ther emore to it21:56
dmsimardthat's the only ansible plugin we use to "interact" with ansible, yeah21:56
dmsimardthe rest of the ara source revolves around the flask application, cli, html, tests, etc.21:57
*** alyson_ has quit IRC21:57
sdakedmsimard these are the plugins? https://github.com/dmsimard/ara/blob/master/ara/callback/log_ara.py#L17421:59
*** vinkman has joined #openstack-kolla21:59
dmsimardthose are the hooks, yeah21:59
sdakeya hooks22:00
dmsimardthe actual "plugin" is actually this whole part: https://github.com/dmsimard/ara/blob/master/ara/callback/log_ara.py#L59-L25722:00
dmsimardthere's some simple callbacks upstream that might be easier to look at: https://github.com/ansible/ansible/tree/devel/lib/ansible/plugins/callback22:00
sdakedmsimard you write nice ansible22:00
dmsimardthat's python, sir :p22:01
sdakeya thats whta i meant22:02
sdakepython22:02
sdakelong day22:02
wirehead_Okat.  TIL, here’s how to pronunce MariaDB: https://www.tibetangeeks.com/technologies/database/mariadb/mariadb-info_and_links.txt22:02
sdakedmsimard the plugin directly writes the database (calls mysql api) on the local host?22:03
wirehead_Also, here’s how to pronounce Kubernetes: https://twitter.com/francesc/status/48741220293293670422:04
dmsimardsdake: the default config has ara configure and use a sqlite database at ~/.ara/ansible.sqlite22:04
sdakeok sqlite22:05
dmsimardsdake: but you could also configure it to use a mysql database without much effort22:05
sdakebut ansible calls sqlite directly?22:05
dmsimardhttp://ara.readthedocs.io/en/latest/configuration.html#ara-database22:05
sdakei would prefer to communicate with a rest api22:05
dmsimardthere's no rest api22:05
dmsimardthere are sqlalchemy models22:05
sdakei know in ara22:05
dmsimardand we use those22:05
sdakeI am thinking in my own world here ;)22:05
dmsimardif you want to control ansible over an api there are things like tower and semaphore22:05
sdakeI am thinking about how to come up with a gui for kolla22:05
sdakesemaphore?22:06
dmsimardhttps://github.com/ansible-semaphore/semaphore22:06
sdakei can't recommend proprietary products for use with kolla22:06
dmsimardI can't vouch for either tower or semaphore or other stuff, I haven't used them22:06
dmsimardI didn't know about semaphore until I was asked about ara vs semaphore :)22:07
wirehead_I have a halfassed notion, at least for kolla-k8s, of not having the user install ansible at all, but instead running that inside of the cluster in a container.22:07
sdakeme either22:07
wirehead_I haven’t thought of it enough22:07
sdakewirehead_ ya that is already done in kolla-toolbox22:07
sdakewirehead_ just add stuff to toolbox you need22:07
sdakedmsimard what does semaphore look like22:08
dmsimardI have absolutely no clue22:08
sdakedmsimard here is what I got out of ara, just for the sake of sharing22:08
sdakeoh righty ou couldn't vouch for i t22:08
sdakeara seems like a nice tool but what Kolla operators (atleast CIOs and sales droids) really want is a nice pretty status reporting GUI with actions attached22:09
*** fragatin_ has quit IRC22:09
sdakeso think of a gui with all of kolla's actions22:09
dmsimardara might have that pretty status reporting gui22:09
dmsimardif actual frontend-competent people would contribute22:10
dmsimardI'm not a UI/UX guy at all :)22:10
sdakewhats a frontend competent22:10
sdakeyou mean gui?22:10
*** unicell has quit IRC22:10
*** fragatina has joined #openstack-kolla22:10
sdakeI dont know anything about UI dev22:10
dmsimardyeah, stuff like javascript, ajax, nodejs, react, you know all those frontend buzzwords22:10
sdakethe lasst time i wrote html was in 1996 in vi22:10
dmsimardthe UI/UX of the web interface needs a ton of work from people that can do proper frontend22:11
dmsimardto make it pretty, functional, easy to browse, stuff like that22:11
wirehead_I do front-end for fun.  The advent of node.js and react actually makes it mostly fun.22:13
dmsimardcss, html and javascript makes me sad22:14
wirehead_And by “fun”, I mostly mean “with enough adequate abstractions layered atop each other such that it’s mostly smooth sailing, kind of like how if you put enough layers of paint on, everything’s smooth"22:14
dmsimardI have the utmost respect for people that can write nice frontend stuff, but I'd rather stay as far away from that kind of development as I can :)22:15
dmsimardHorizon is pretty cool, you know, internal popup dialogs, tabs, automatically refreshes, there's a lot of work behind the scenes and I'm sure it's not easy22:16
wirehead_My idea of fun is… unusual.22:16
*** berendt has quit IRC22:20
*** thumpba_ has quit IRC22:27
*** b_bezak has quit IRC22:29
*** mbound has joined #openstack-kolla22:30
*** b_bezak has joined #openstack-kolla22:30
*** b_bezak_ has joined #openstack-kolla22:33
*** b_bezak has quit IRC22:34
Davieysdake: sorry, i went afk22:40
*** vinkman has left #openstack-kolla22:40
sdakeDaviey no problem, i forgot your question22:42
sdakeif you remember, feel free to ask again22:43
*** b_bezak_ has quit IRC22:46
*** b_bezak has joined #openstack-kolla22:47
*** huikang has quit IRC22:47
*** b_bezak has quit IRC22:51
*** harlowja has joined #openstack-kolla22:51
*** daneyon_ has joined #openstack-kolla22:58
*** ravig has quit IRC22:58
*** jrist has quit IRC23:01
*** jrist has joined #openstack-kolla23:02
*** daneyon_ has quit IRC23:03
*** godleon has quit IRC23:09
*** harlowja has quit IRC23:10
*** harlowja has joined #openstack-kolla23:10
*** vhosakot has quit IRC23:21
*** mummer has joined #openstack-kolla23:25
*** mummer has quit IRC23:26
*** thumpba has joined #openstack-kolla23:28
*** b_bezak has joined #openstack-kolla23:29
*** b_bezak has quit IRC23:31
*** b_bezak has joined #openstack-kolla23:31
*** thumpba has quit IRC23:33
*** b_bezak has quit IRC23:36
*** mbound has quit IRC23:46
*** zhiwei has joined #openstack-kolla23:49
sdakeharlowja around?23:53
harlowjasup23:53
harlowjai didn't do it23:53
harlowjalol23:53
harlowjait was that other guy23:53
*** rahuls has quit IRC23:54
sdakeharlowja so re godaddy deploying kolla23:54
harlowjasoooo23:54
sdakeharlowja i ont know if thats a thing or your just playing around23:54
*** elemoine_ has quit IRC23:54
sdakebut i'm sure ou hae requirements that are unmet23:54
harlowjasoooo i'm working on it being a thing :-P23:54
sdakethat would rock :)23:54
*** zhiwei has quit IRC23:54
harlowjai'm working on a internal-spec that is gonna explain how the team will do it23:54
sdakewill do which23:55
harlowjabut ya, some things that we have that are weird that i can think of (active work in progress that i need to dump)23:55
sdakeyou mean have a ci/cd pipeline with kolla?23:55
harlowjathats part of it23:55
sdakeok23:55
sdakewell you dont have to tell me all your secrets :)23:55
harlowjanah, not secret23:55
sdakebut ou hae alot of nodes23:55
sdakei assume23:55
harlowjaya23:55
sdakekolla has been tested at 6423:55
sdakedo you do multi-region or cells?23:55
sdake(for scalability)23:56
harlowjaya, we do (both), just not sure yet how that will work, but its ok23:56
harlowjacells and multi-region :-P23:56
sdakewell how I recommend it working is we implement that code upstream23:57
harlowjaagreed23:57
sdakeand you can carry patches against an internal stable branch or some other option23:57
harlowjasome other random thinkings23:57
harlowjawe have patches :-/23:57
sdakepatches for openstack or patches for kolla23:57
harlowjaso do people typically say point kolla at internal git repos?23:57
harlowjafor openstack23:57
*** elemoine_ has joined #openstack-kolla23:58
harlowjaand/or some mixed mode of not patched repos (which are == public ones)23:58
sdakein your cae i'd recommend having your ci/cd pipeline build images using a custom list of git repos23:58
harlowjaright23:58
sdakethat works if your bulding rom source23:58
harlowjawe also have these other weird things (that yes, i'll eventually get the folks to get rid of)23:58
harlowjathat are called waffles23:58
harlowjai think its a rackspace originated concept23:58
sdakewould you like fries wit hthat23:58
harlowjasupersize it thx23:58
sdake;-)23:59
harlowjabut they are basically middleware components (wsgi middleware)23:59
harlowjathat do things with the request before it say gets to nova23:59
harlowjaone example23:59
wirehead_Oh those things.23:59
sdakeis it like a rate limiter?23:59
harlowjanot really23:59
harlowjamostly used for validation before a request gets to nova/other23:59
sdakeso it gets a requet and doews what with it?23:59

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