Friday, 2017-12-08

*** threestrands has joined #openstack-kolla00:01
*** itlinux has joined #openstack-kolla00:03
*** hongbin has quit IRC00:08
*** TxGirlGeek has quit IRC00:11
*** manheim has quit IRC00:13
*** JinVan_ has joined #openstack-kolla00:14
*** Pavo has joined #openstack-kolla00:14
*** JinVan_ has quit IRC00:15
*** genek has quit IRC00:37
*** unicell has joined #openstack-kolla00:40
*** manheim has joined #openstack-kolla00:43
*** mkrai has joined #openstack-kolla00:46
*** manheim has quit IRC00:47
*** kiennt26 has joined #openstack-kolla00:50
*** nhlfr has joined #openstack-kolla00:54
*** bachp has joined #openstack-kolla00:54
*** retr0h has joined #openstack-kolla00:54
*** tovin07_ has joined #openstack-kolla00:55
*** yangyapeng has joined #openstack-kolla01:09
*** zhangfei has joined #openstack-kolla01:10
*** david-lyle has joined #openstack-kolla01:18
masbermorning01:19
*** mikal has quit IRC01:24
*** Pavo has quit IRC01:26
*** mikal has joined #openstack-kolla01:30
*** caowei has joined #openstack-kolla01:34
SamYaplemorning01:34
hrwhttp://people.linaro.org/~marcin.juszkiewicz/kolla/ refreshed to show build status of queens on aarch64 and x86-64 architectures. inc0 sdake Jeffrey4l rwellum: take a look01:36
*** david-lyle has quit IRC01:36
*** Pavo has joined #openstack-kolla01:41
*** rhallisey has quit IRC01:45
*** genek has joined #openstack-kolla01:46
Jeffrey4lhrw, this table is cool.01:46
*** Pavo has quit IRC01:58
*** Pavo has joined #openstack-kolla02:01
*** harlowja has quit IRC02:03
*** Pavo has quit IRC02:05
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Remove the unnecessary register.yml from upgrade.yml for Nova  https://review.openstack.org/52656602:06
*** jascott1 has quit IRC02:08
*** Zara has joined #openstack-kolla02:13
lxdongBuild of instance 9e22969e-f94a-42fd-859c-dd72ad8c5c85 aborted: The server has either erred or is incapable of performing the requested operation.02:24
*** pbourke has quit IRC02:29
*** pbourke has joined #openstack-kolla02:30
*** jascott1 has joined #openstack-kolla02:42
openstackgerritJeffrey Zhang proposed openstack/kolla master: [DNM]Test squash docker images layers for current built image  https://review.openstack.org/52587102:42
*** zhurong has joined #openstack-kolla02:47
*** genek has quit IRC02:52
*** genek has joined #openstack-kolla02:54
*** unicell has quit IRC02:55
*** janonymous has joined #openstack-kolla02:55
*** lukepatrick has joined #openstack-kolla02:59
inc0nice hrw :)03:00
inc0great stuff03:00
*** jascott1 has quit IRC03:06
*** zhangfei_ has joined #openstack-kolla03:16
*** genek has quit IRC03:19
*** genek has joined #openstack-kolla03:21
*** dave-mccowan has quit IRC03:26
*** genek_ has joined #openstack-kolla03:26
*** genek has quit IRC03:27
openstackgerritJeremy Liu proposed openstack/kolla-ansible master: Remove kolla_internal_address variable  https://review.openstack.org/51758003:31
openstackgerritzenghui.shi proposed openstack/kolla-ansible master: Add ptp ansible role  https://review.openstack.org/51921903:47
SamYapleinc0: you know there is suppsoed to be a deprecation cycle for this kind of thing https://review.openstack.org/#/c/517580/03:56
*** goldyfruit has joined #openstack-kolla04:09
*** goldyfruit has quit IRC04:22
*** Pavo has joined #openstack-kolla04:22
*** zhurong has quit IRC04:26
*** genek_ has quit IRC04:36
*** genek has joined #openstack-kolla04:36
*** hieulq has quit IRC04:43
Jeffrey4lSamYaple, yes. forgot that. should deprecated now.04:43
*** hieulq has joined #openstack-kolla04:44
openstackgerritJeffrey Zhang proposed openstack/kolla-ansible master: Implement ceph-mgr service  https://review.openstack.org/52549504:46
*** zhangfei_ has quit IRC04:50
*** zhangfei has quit IRC04:50
openstackgerritJeffrey Zhang proposed openstack/kolla master: [DNM]Test squash all the layers  https://review.openstack.org/52589204:50
openstackgerritJeffrey Zhang proposed openstack/kolla master: [DNM] Test without squash  https://review.openstack.org/52588204:51
*** ArminderSingh has quit IRC04:52
*** zhangfei has joined #openstack-kolla05:02
*** zhangfei_ has joined #openstack-kolla05:03
*** caowei has quit IRC05:06
*** Pavo has quit IRC05:14
*** caowei has joined #openstack-kolla05:19
*** threestrands has quit IRC05:24
*** harlowja has joined #openstack-kolla05:37
*** threestrands has joined #openstack-kolla05:39
*** threestrands has quit IRC05:39
*** threestrands has joined #openstack-kolla05:39
*** zhurong has joined #openstack-kolla05:40
*** lukepatrick has quit IRC05:44
*** mikal has quit IRC05:57
*** mikal has joined #openstack-kolla05:59
*** janki has joined #openstack-kolla05:59
*** unicell has joined #openstack-kolla06:10
*** harlowja has quit IRC06:14
*** caowei has quit IRC06:14
*** caowei has joined #openstack-kolla06:15
*** xinliang has quit IRC06:22
openstackgerritzenghui.shi proposed openstack/kolla-ansible master: Add ptp ansible role  https://review.openstack.org/51921906:26
*** threestrands has quit IRC06:28
*** xinliang has joined #openstack-kolla06:35
*** xinliang has joined #openstack-kolla06:35
*** ArminderSingh has joined #openstack-kolla06:42
*** zhurong has quit IRC06:47
*** skramaja has joined #openstack-kolla06:48
*** cah_link has joined #openstack-kolla07:01
-openstackstatus- NOTICE: Due to some unforseen Zuul issues the gate is under very high load and extremely unstable at the moment. This is likely to persist until PST morning07:03
*** ChanServ changes topic to "Due to some unforseen Zuul issues the gate is under very high load and extremely unstable at the moment. This is likely to persist until PST morning"07:03
*** mpansky has joined #openstack-kolla07:04
*** alanmeadows has quit IRC07:06
*** serverascode has quit IRC07:07
*** alanmeadows has joined #openstack-kolla07:07
*** genek has quit IRC07:07
*** serverascode has joined #openstack-kolla07:07
*** kencjohnston has quit IRC07:08
*** vkmc has quit IRC07:08
*** harmw has quit IRC07:08
*** pron has quit IRC07:08
openstackgerritcaoyuan proposed openstack/kolla-ansible master: Remove the unnecessary register.yml from upgrade.yml for Nova  https://review.openstack.org/52656607:09
*** harmw has joined #openstack-kolla07:09
*** vkmc has joined #openstack-kolla07:10
*** vkmc has quit IRC07:10
*** vkmc has joined #openstack-kolla07:10
*** pron has joined #openstack-kolla07:11
*** genek has joined #openstack-kolla07:12
*** kencjohnston has joined #openstack-kolla07:13
*** retr0h has quit IRC07:14
*** bachp has quit IRC07:14
*** nhlfr has quit IRC07:15
*** mkrai has quit IRC07:15
openstackgerritSaravanan KR proposed openstack/kolla master: Add the new user and group for OpenvSwitch 2.8 version  https://review.openstack.org/52633207:17
*** genek has quit IRC07:19
*** Arminder has joined #openstack-kolla07:20
*** Arminder- has quit IRC07:21
*** mdnadeem has joined #openstack-kolla07:25
*** Zophar has quit IRC07:40
*** david-lyle has joined #openstack-kolla07:52
*** shardy has joined #openstack-kolla07:58
*** genek has joined #openstack-kolla07:58
*** unicell has quit IRC08:02
*** b_bezak has joined #openstack-kolla08:04
openstackgerritzenghui.shi proposed openstack/kolla-ansible master: Add ptp ansible role  https://review.openstack.org/51921908:07
lxdonghow to configure non-default ssh port for kolla-ansible ?08:08
*** zhangfei_ has quit IRC08:10
*** zhangfei has quit IRC08:11
SamYaplelxdong: its ansible, so use your ssh/config file08:12
*** zhurong has joined #openstack-kolla08:16
lxdongok,thanks.08:21
*** mgoddard has joined #openstack-kolla08:26
*** zhangfei has joined #openstack-kolla08:27
*** zhangfei_ has joined #openstack-kolla08:28
*** shardy is now known as shardy_afk08:31
*** mgoddard has quit IRC08:46
*** shardy_afk is now known as shardy08:48
*** manheim has joined #openstack-kolla08:56
*** zhangfei_ has quit IRC08:59
*** itlinux has quit IRC09:01
*** zhangfei has quit IRC09:05
*** bbc1__ has joined #openstack-kolla09:07
cah_linkHey all together: I have a question. It seems like kolla build always pulls the "master" tarball. So if i want to have 4.0.0 i get what? 6.0.0.0b2?09:08
cah_linkhow could i install a containerized  ocata openstack09:09
cah_link?09:09
*** owalsh has quit IRC09:10
*** bbc1__ has left #openstack-kolla09:11
*** zhangfei_ has joined #openstack-kolla09:11
*** owalsh has joined #openstack-kolla09:12
*** k_mouza has joined #openstack-kolla09:12
*** jbadiapa has joined #openstack-kolla09:14
*** athomas has joined #openstack-kolla09:15
*** mkrai has joined #openstack-kolla09:18
*** zhangfei has joined #openstack-kolla09:18
*** mgoddard has joined #openstack-kolla09:18
*** jbadiapa has quit IRC09:21
openstackgerritJianghua Wang proposed openstack/kolla-ansible master: XenAPI: Support neutron configuration  https://review.openstack.org/52599909:26
*** nhlfr has joined #openstack-kolla09:26
*** retr0h has joined #openstack-kolla09:26
*** bachp has joined #openstack-kolla09:26
*** affie has joined #openstack-kolla09:27
*** affie_ has joined #openstack-kolla09:28
*** manheim has quit IRC09:29
*** affie has quit IRC09:32
*** genek has quit IRC09:33
*** affie__ has joined #openstack-kolla09:36
*** genek has joined #openstack-kolla09:36
*** affie has joined #openstack-kolla09:38
*** affie_ has quit IRC09:40
*** affie__ has quit IRC09:41
openstackgerritzhangfei gao proposed openstack/kolla-ansible master: ironic-pxe: support pxe uefi mode  https://review.openstack.org/51335309:44
dasTorcah_link, what did you set for openstack_release in zour globals.yml ?09:44
*** genek has quit IRC09:44
dasTorif you set for example: openstack_release: "4.0.0" - you should get 4.0.009:45
*** numans has quit IRC09:45
openstackgerritJianghua Wang proposed openstack/kolla-ansible master: XenAPI: Support neutron configuration  https://review.openstack.org/52599909:46
*** genek has joined #openstack-kolla09:48
*** numans has joined #openstack-kolla09:50
*** dardelean has joined #openstack-kolla09:53
*** genek has quit IRC10:08
*** caowei has quit IRC10:12
cah_linkdasTor: i set 4.0.0 in the globals.yml. But i create the images with kolla-build -t source ...10:15
cah_linkdasTor: now i realize that in kolla-build.conf by default all used tarballs are "master"10:16
cah_linkdasTor: so you say if i build from binary i should get the correct version?10:19
cah_linkdasTor: and if I do from source i have to specify the source first because if I don't do that i get master10:21
*** duonghq_ has quit IRC10:22
*** tovin07_ has quit IRC10:23
*** manheim has joined #openstack-kolla10:27
*** lebauce_ has quit IRC10:28
*** daidv has quit IRC10:38
*** zhurong has quit IRC10:40
*** zhangfei has quit IRC10:42
*** zhangfei_ has quit IRC10:42
*** lebauce has joined #openstack-kolla10:45
manheimmorning10:53
*** manheim is now known as dardelean_10:53
*** kiennt26 has quit IRC10:54
*** openstackgerrit has quit IRC11:17
*** k_mouza_ has joined #openstack-kolla11:26
*** k_mouza has quit IRC11:26
*** gfidente has joined #openstack-kolla11:33
*** dave-mccowan has joined #openstack-kolla11:45
*** ansmith has joined #openstack-kolla12:07
*** janki has quit IRC12:07
*** DosBarbos has joined #openstack-kolla12:11
*** rhallisey has joined #openstack-kolla12:12
*** rhallisey has quit IRC12:16
*** rhallisey has joined #openstack-kolla12:17
*** lvdombrkr has joined #openstack-kolla12:20
*** yangyapeng has quit IRC12:24
*** genek has joined #openstack-kolla12:31
*** mpansky has left #openstack-kolla12:38
*** salv-orlando has joined #openstack-kolla12:42
*** yangyapeng has joined #openstack-kolla12:55
*** rhallisey has quit IRC13:04
*** rhallisey has joined #openstack-kolla13:04
*** jaosorior has quit IRC13:12
*** jaosorior has joined #openstack-kolla13:13
*** k_mouza_ has quit IRC13:15
*** k_mouza has joined #openstack-kolla13:15
*** openstackgerrit has joined #openstack-kolla13:19
openstackgerritDan Ardelean proposed openstack/kolla-ansible master: Implement cinder-smb-hyperv ansible role  https://review.openstack.org/50853013:19
*** janonymous has quit IRC13:24
*** salv-orlando has quit IRC13:29
*** salv-orlando has joined #openstack-kolla13:30
*** trozet has quit IRC13:31
*** salv-orlando has quit IRC13:34
*** lpetrut has joined #openstack-kolla13:39
cah_linkhi together. If I create kolla-build.conf with tox and copy it to /etc/kolla, I get "oslo_config.cfg.NoSuchOptError: no such option almanach-user in group [DEFAULT]" on kolla-build.13:43
*** ChanServ changes topic to "support: ask.openstack.org | New to Kolla: docs @ https://docs.openstack.org/kolla/latest/ | | Kolla IRC meetngs on Wednesdays @ 16:00 UTC - see agenda @ https://goo.gl/OXB0DL - IRC channel is *LOGGED* @ http://goo.gl/3mzZ7b"13:59
-openstackstatus- NOTICE: The issues have been fixed, Zuul is operating fine again but has a large backlog. You can recheck jobs that failed.13:59
openstackgerritMichal Rostecki proposed openstack/kolla-ansible master: dev mode: Add support for neutron  https://review.openstack.org/52646613:59
rwellumcah_link: have you read the build images doc yet?14:03
*** Pavo has joined #openstack-kolla14:03
rwellumcah_link: https://docs.openstack.org/kolla/latest/admin/image-building.html14:03
*** trozet has joined #openstack-kolla14:11
cah_linkrwellum: yeah I read this multiple times. Could you please tell me what part of that site i have missed?14:14
cah_linkor where i got something missunderstood14:15
*** goldyfruit has joined #openstack-kolla14:16
cah_linkrwellum: As far as i see. I have done that is said on this site.... install tox, create kolla-build.conf, kolla-build ...14:19
rwellumThe part about pulling master tarballs I am not sure about. Maybe inc0 can help there. The other part - maybe14:21
rwellumcah_link: so you can checkout kolla to the correct branch - i.e ocata - then it will source ocata tarballs afaik14:21
rwellumI make the changes directly to kolla project then run ./tools/build.py - because I too have had similar issues with finding the correct config files.14:22
rwellumcah_link: I can share my exact steps if you want?14:23
cah_linkrwellum: I have tested switching to ocata branch and create the kolla-build.conf new. there now these is no almanach part. so i think it would run14:29
cah_linkbut why if i want to have pike?14:30
rwellumPike works for me.14:30
cah_linkon Pike there i got the error "oslo_config.cfg.NoSuchOptError: no such option almanach-user in group [DEFAULT]"14:31
rwellumcah_link: check and see if you have all these steps?  https://www.irccloud.com/pastebin/GpLwAXnB/14:32
cah_linkrwellum: aww d... ok now i got a clue14:34
rwellumNote I'm pushing to dockerhub - but you can build them locally, or to a local registry14:35
rwellumHTH14:35
rwellumI think the doc should be updated a bit - I prefer my description above, but the above is specific to a few cases, the doc tries to cover them all.14:36
*** trozet has quit IRC14:38
kolla-slack<aslancimbom100> `171208 17:40:29 [ERROR] WSREP: gcs/src/gcs.cpp:gcs_open():1404: Failed to open channel 'openstack' at 'gcomm://192.168.10.54:4567,192.168.10.55:4567,192.168.10.56:4567': -110 (Connection timed out)`14:40
kolla-slack<aslancimbom100> anyone seen that before on mariadb container?14:41
cah_linkrwellum: yeah there it is... i didnt check out otaca before. 'I still was at master so in the kolla-build.cond all tarbals are master14:43
cah_linkwith ocata branch now i see the correct tarballs14:44
cah_linkmany thx14:44
rwellumcah_link: sweet14:44
rwellumcah_link: now you can build and run onkolla-kubernetes :)14:44
cah_linkrwellum: haha you are funny.... noooo ....i have to build it with chef..... don't ask14:46
cah_linkwith kolla-kubernetes this would be too easy... haha14:46
rwellumUgh ruby14:47
* rwellum cries a little14:47
*** pbourke has quit IRC14:50
kolla-slack<aslancimbom100> @egonzalez https://bugs.launchpad.net/kolla-ansible/+bug/169250714:54
openstackLaunchpad bug 1692507 in kolla-ansible ocata "mariadb multinode upgrade broken ocata-pike" [Critical,Triaged]14:54
kolla-slack<aslancimbom100> Is there a non-upgrade fix?14:54
*** pbourke has joined #openstack-kolla14:55
dardelean_is there something build-in kolla to pull images from dockerhub and dump them in a local registry?14:57
rwellumdardelean: of course. :)14:59
rwellumkolla build with --pull and --push to registery15:00
*** salv-orlando has joined #openstack-kolla15:04
dardelean_rwellum great, ty15:05
*** hongbin has joined #openstack-kolla15:07
*** Pavo has quit IRC15:07
dardelean_that is the exact difference between kolla-ansible pull and kolla-build --pull? kolla-build --pull will only update my existing images?15:10
*** signed8bit has joined #openstack-kolla15:10
dardelean_I have no images atm15:10
*** Pavo has joined #openstack-kolla15:13
*** livelace-link has joined #openstack-kolla15:15
*** trozet has joined #openstack-kolla15:20
*** gfidente has quit IRC15:25
*** salv-orlando has quit IRC15:34
*** salv-orlando has joined #openstack-kolla15:35
sdakemoring peeps15:36
sdakejascott around?15:37
*** salv-orlando has quit IRC15:40
*** shardy has quit IRC15:47
rwellumdardelean_: don't use kolla-ansible  - but I expect that's a deployment pull - just getting the images to run.15:48
dardelean_rwellum I am already building the images myself...will push to local registry afterwards15:49
rwellumdardelean_: aiui - kolla-build --pull will update your images, if there's a change in source, or --nocache15:49
rwellumdardelean_: yeah - you could do it in one step I htink.15:50
rwellumMorning sdake15:51
rwellumkubecon makes this channel very quiet I think15:51
dardelean_this a bit confusing16:00
dardelean_so I build the images16:00
dardelean_and how I want t opush them to my local repo with "kolla-build --registry 192.168.100.51:5000 --push"16:01
dardelean_but how it's rebuilding centos images, in globals.yml I have ubuntu as type16:01
dardelean_but now*16:01
*** lukepatrick has joined #openstack-kolla16:04
*** vhosakot has joined #openstack-kolla16:07
*** affie has quit IRC16:11
*** jaosorior has quit IRC16:13
*** itlinux has joined #openstack-kolla16:14
*** dardelean_ has quit IRC16:20
*** MasterOfBugs has joined #openstack-kolla16:22
*** pramodrj07 has joined #openstack-kolla16:22
sdakesup rwellum16:23
sdakerwellum ya - conference time makes everything quiet16:24
sdakei've had about enough of travel :) so just having a breakfast and will likely be late toe the conf today16:24
*** vhosakot has quit IRC16:25
k_mouzadardelean_, from the documentation:16:27
k_mouzaBy default, the above command would build all images based on CentOS image.16:27
k_mouzaThe operator can change the base distro with the -b option:16:27
k_mouzakolla-build -b ubuntu16:27
*** yangyape_ has joined #openstack-kolla16:36
*** yangyapeng has quit IRC16:36
inc0good morning16:37
kfox1111morning.16:39
kfox1111sdake: anything interesting going on at the conference?16:39
kfox1111there was a bunch of anouncements wed, and then they all went quiet.16:40
sdakeyou remember how kubernetes sort of took over openstack summits16:40
sdakeistio is sort of doing that now16:40
kfox1111interesting.16:40
kfox1111its kind of an important piece that wasn't solved.16:40
kfox1111so glad its getting momentum.16:40
sdakethere is also this: https://twitter.com/robcresswell/status/93913246509611827616:41
kfox1111anything on celium? I've been curious on that one.16:41
sdakeya some discussion16:41
sdakenot really following celium much16:41
sdakethere is an additional service mesh called conduit16:41
kfox1111me neither, but looks promising.16:41
kfox1111hmm. hadnt heard of that one.16:41
sdakeamusingly enough I laid some conduit this last weekend ;-)16:41
sdakethere are 4 or 5 service mesh talks16:42
*** itlinux has quit IRC16:42
sdakeI can say one thing, and you can quote me on this one16:42
sdakeThe sponsors of this event are spending money like drunken sailors ;-)16:42
kfox1111rust and go. interestign choices.16:42
cah_linkrwellum: this wasn't my idea... we got a complete openstack instalation deployed with chef (bare-metal). now I try to get this dockerized one by one16:42
kfox1111sdake: yeah. I think most just took their money going into openstack and shifted it to k8s.16:43
sdakekfox1111 nah - these are mostly startups16:43
*** itlinux has joined #openstack-kolla16:43
kfox1111ah. new round of startups. gotcha16:43
sdakekfox1111 the big cos work in both cncf and openstack16:44
sdakekfox1111 they may adjust their spending in openstack - however - the chuchu train of money hasn't ended for these confs :)16:45
kfox1111ah, so conduit is from Buoyant too.16:45
kfox1111that makes sence.16:45
kfox1111they are loosing out to istio for good reason, so they gotta drop java.16:46
*** lukepatrick has quit IRC16:46
sdakei found out kubernetes has not left incubation in cncf16:46
kfox1111hmm. interesting.16:46
sdakeno project has graduated the incubation stage16:46
sdakemust be a high bar16:46
kfox1111though I don't think they have figured out gradutation really yet.16:46
kfox1111yeah.16:46
kfox1111probably high in that they haven't fully figured out what graduation means yet.16:47
sdakei thought incubation was a high bar in openstack16:47
sdakevery high16:47
sdakehere for cncf projects it appears the project must have a corporate sponsor16:47
*** Pavo has quit IRC16:47
sdakerather than "here is my open source project with a whole slew of corporate sponsors"16:47
sdakeIOW - one throat to choke16:47
inc0yay for communities16:48
kfox1111thats kind of a problem. :/16:48
sdakei could be misinformed16:48
sdakeentirely possible ;)16:48
kfox1111fair enough.16:48
sdakealthough every project that enters cncf has a company behidn it16:49
kfox1111I'm kind of weirded out by the hyper+cc thing being in openstack.16:49
sdakerather than a motley crew of devs (sort of like kolla) :)16:49
sdakehyper+cc is not in openstack16:49
sdakeits a separate thing16:49
inc0it is16:49
inc0well in openstack foundation16:49
sdakeopenstack simply provides legal/trademark/etc16:49
kfox1111why not the cncf though? openstack seems like an odd place.16:49
*** niedbalski has quit IRC16:49
sdakekfox1111 openstack creating strategic focus areas16:50
kfox1111it very clearly touches their stack.16:50
inc0politics16:50
sdakekfox1111 this is the first one16:50
kfox1111how does the foundation think this will effect openstack/cncf relations?16:50
sdakei think inc0's answer is simplisitic - the real answer is nobody knows :)16:50
*** niedbalski has joined #openstack-kolla16:50
inc0also I wouldn't be surprised if part of it is to keep cncf on it's toes16:50
inc0things like that also matter16:50
sdakewhen we setup the strategic focus areas in the board, it was NOT TO COMPETE with CNCF16:51
sdakeit was to redefine the core of openstack a bit more tidely16:51
*** dciabrin_ has joined #openstack-kolla16:51
kfox1111yeah, but a cri compatable container engine is very close to what cncf's about, and not what openstack thus far has provided at all.16:51
sdakeand provide better marketing/legal support/business support at the board level to folks16:51
*** dciabrin__ has joined #openstack-kolla16:51
kolla-slack<aslancimbom100> Anyone that can assist me?16:51
kfox1111it feels like compitition.16:51
inc0maybe it's because what you said?;) there is no singular corporate sponsor for kata16:51
*** dciabrin_ has quit IRC16:51
*** lukepatrick has joined #openstack-kolla16:51
kfox1111inc0: yeah, if t hat was true, then openstack is a better fit still.16:52
sdakehey felals - that was just my read on the conference - I don't think anyone has officially stated that16:52
*** dciabrin has quit IRC16:52
sdakeIOW, I dont' see any project which doesn't have 1 or 2 corporate sponsors driving a project forward16:53
inc0well truth is that cncf seems to be way more corporate than openstack ever was16:53
inc0for me kind of red light was invite-only "k8s leadership summit"16:53
kfox1111thats hard to believe. ;)16:53
inc0and invites went to companies not people16:53
sdakeinvite-only events are troublesome, I'll give you that inc016:53
inc0afair16:53
kfox1111ah. yeah, that is a problem.16:54
inc0we'll see how it goes16:54
kfox1111a lot of openstacks current problems were from being too corperate friendly and not user friendly enough.16:54
kfox1111yeah.16:54
inc0also foundation != community16:55
kfox1111yeah.16:55
kfox1111they completely sidestepped the normal openstack community on the hyper+cc thing.16:56
inc0yeah that's an interesting news16:56
inc0I wonder what's next16:56
*** david-lyle has quit IRC16:57
sdakekfox1111 re hyper+cc, how do you mean sidestepped the normal openstack community?16:58
sdakethese strategic focusw areas were announced at Sydney summit16:58
sdakeI know you weren't there :)16:58
inc0this is first non-openstack project in openstack foundation isn't it?16:58
sdakehowever it was sort of big news16:58
kolla-slack<aslancimbom100> @inc016:58
sdakeinc0 indeed it is a pilot16:58
inc0aslancimbom I'd really need more details regarding your problem;)16:58
openstackgerritDmitry Tantsur proposed openstack/kolla master: ironic-conductor: update list of drivers  https://review.openstack.org/52673416:59
sdakeinc0 details - who needs those :)16:59
sdakeinc0 if I have my way, whats next is zuul16:59
sdakealthough who knows :)16:59
inc0zuul is already openstack community16:59
openstackgerritMichal Rostecki proposed openstack/kolla-ansible master: dev mode: Add support for neutron  https://review.openstack.org/52646617:00
openstackgerritMichal Rostecki proposed openstack/kolla-ansible master: dev mode: Add support for kuryr  https://review.openstack.org/52673517:00
sdakeci/cd was one of the focus areas17:00
sdakezuul naturally fits in that17:00
inc0right17:00
*** itlinux has quit IRC17:00
kolla-slack<aslancimbom100> my mariadb containers have stopped working with the same error in the bug, but im not upgrade, would like to start mariadb as it was.17:00
inc0did you restart all mariadb containers at once?17:01
kolla-slack<aslancimbom100> yes, I now realize that was a big nonono, we all make mistakes :(17:01
inc0it happens, but you need to do some manual work afterwards17:02
inc0http://galeracluster.com/documentation-webpages/restartingcluster.html17:02
inc0this is doc you need17:02
kolla-slack<aslancimbom100> i'm suppose to start db with wsrep-new-cluster, no sure how to do that with docker+ansible17:02
inc0also fact that all mariadb files can be found in /var/lib/docker/volumes/mariadb/_data17:02
openstackgerritDmitry Tantsur proposed openstack/kolla master: ironic-conductor: update driver dependencies for Queens  https://review.openstack.org/52673417:03
inc0you should have grastate.dat there17:03
kolla-slack<aslancimbom100> yeah I've tried editing grastate.dat and setting safe_to_bootstrap=1, I guess I then need to initiate bootstrap17:03
*** lrensing has joined #openstack-kolla17:04
kfox1111sdake: I mean, if you look at their governence page, it is a project completely seperated from the regular openstack community except for the foundation.17:04
kfox1111none of the community developed governence stuff applies.17:04
clarkbyes its not part of openstack17:04
kfox1111yeah.17:04
sdakeclarkb is correct17:04
clarkb(so the openstack tc doesn't apply etc)17:05
*** itlinux has joined #openstack-kolla17:05
*** b_bezak has quit IRC17:05
inc0I wonder if this will be part of opesntack summit and whatnot17:05
kfox1111still not sure why the foundation is supporting it then.17:05
clarkbkfox1111: I think jbryce did a qa in the tc room last week? there was metnion of it in a mailing list thread, I'd be surprised if that wasn't covered17:06
inc0it was announced this week17:06
kfox1111k. I'll go back through the list. I think I missed it.17:06
clarkber must've been this week then17:06
*** dardelean_ has joined #openstack-kolla17:06
clarkbhttp://eavesdrop.openstack.org/irclogs/%23openstack-tc/%23openstack-tc.2017-12-05.log.html#t2017-12-05T14:11:33 is the link I have from cdents email thread17:07
clarkbinc0: the effort was announced in sydney fwiw17:07
inc0ahh I'd know if I go :(17:07
clarkbthe specific pilot project got announced this week though17:08
kfox1111clarkb: thanks for the link.17:09
kfox1111don't get me wrong, I think kata is a good project. glad to see the two forces merge.17:09
kfox1111I've been trying to get the cncf and openstack closer together and it feels weird to have something that seems to fit cncf in the openstck umbrella, but especially only sort of kind of.17:10
kfox1111I guess there is one angle though that it might it...17:11
*** dardelean_ has quit IRC17:11
kfox1111if cncf's really targetting public clouds, and openstack the ability to do private clouds,17:11
inc0sdake: if you are still up, might revieweing? https://review.openstack.org/#/c/525470/17:11
kfox1111kata kind of fits the private cloud use case closer.17:11
*** Pavo has joined #openstack-kolla17:15
dardeleank_mouza i built ubuntu images17:16
kolla-slack<aslancimbom100> brilliant, all mariadb seqno-1...good job =.17:19
*** serlex has joined #openstack-kolla17:24
*** lrensing has quit IRC17:26
*** mdnadeem has quit IRC17:26
kfox1111arg.. kata containers has its own slack. :(17:27
* kfox1111 signs up for yet another org...17:27
jbrycekfox1111: all mirrored to IRC though if you don't want to add another slack17:29
kfox1111I use slack for pings though. so I won't see them unless subscribed. :(17:30
*** lpetrut has quit IRC17:30
jbryceIn terms of why here, the project teams came to us and asked us to help build a real community that was open and multi-vendor and in touch with operators17:30
kfox1111+1 to that. :)17:30
jbryceFor me personally why I think it fits it kata provides a low level container infrastructure component17:30
rwellumdardelean: what's the issue, building or deploying?17:31
kfox1111but its similar to rkt and containerd which are both cncf.17:31
rwelluminc0: remarkable number of questions lately on kolla build process. I know I complained that the doc wasn't that helpful - I now think its better than the initial read, but I think it needs like a 'scenarios' chapter.17:32
jbryceYou've got all the dev oriented container components (images and orchestration tools) and then you have the execution environment that is probably more of an operator deployment decision by the person running the cloud infrastructure itself rather than those consuming it17:32
kfox1111just having a hard time distinguishing the boundry between cncf and openstack now.17:32
inc0rwellum: yeah, I'll get to it :) good call17:32
kfox1111yeah, you could look at it that way. I agree with that.17:32
jbryceIt plugs under containerd, but I get your point too17:32
inc0jbryce: will kata consume openstack infra nodepools?17:33
kfox1111k8s is rather op focused though too, which is in cncf.17:33
jbryceI also like the fact that it bridges the tech living in both places. I also want to see more connections and collaboration17:33
rwelluminc0: you can't do it all - I feel bad. I can submit a few thoughts17:33
kfox1111+1 to that too. I'm just worried it will make either camp pull away from each other as they might see it as compititiion.17:34
rwellumjbryce: what is the bridge? I asked this yesterday and got some interesting view points - would like to know.17:34
kfox1111just gotta get the messaging very clear on why its not compitition.17:34
jbryceUltimately it's all a continuum, so nearly impossible and I think artificial to draw a single bright line17:34
kfox1111true.17:35
inc0once I start and do first few, others will have easier time17:35
jbryceinc0: they are looking at that for testing. Do run some of the pieces for the project through infra now17:35
rwelluminc0: I presented one of those at the summit.17:35
*** david-lyle has joined #openstack-kolla17:36
*** k_mouza has quit IRC17:36
jbrycerwellum: the bridge for me is that this actually enables more cloud operators (including existing OpenStack users) to take containers into production for more workloads. That will drive more usage of the rest of the cncf toolkit17:37
inc0jbryce: soo, let say there would be next project that has thematic connection to kata, do you think it makes sense to create TC equivalent to that branch or all projects do their own stuff?17:37
inc0if the latter, do you try to ensure that things work well together? (it'd be shame if they didn't)17:38
jbryceI've talked to a number of e.g. banks and govs who are hesitant to run containers without VMs still because of audits and regulations they can't pass without that level of isolation. That destroys their ability to go as fast and as efficient on hardware usage as they'd like to be and slows their adoption of the rest of the stack17:38
dardelean<rwellum> so I successfully built the images with kolla-build17:39
*** serlex has quit IRC17:39
*** bmace has quit IRC17:40
*** bmace has joined #openstack-kolla17:40
inc0OpenStack has a TC for that, cncf has it's flagship project k8s and everything else plays to it17:40
inc0kata doesn't have scope or push of k8s, so if we want to ensure that things works well together, we need something else17:40
jbryceinc0: yes that's the idea17:41
dardelean<rwellum> ubuntu source, i also have that in globals.yml17:41
jbryceI'm driving now so may need to discuss in more detail later, but happy to keep talking about it17:41
dardelean<rwellum> the issues is when I push, kolla-build --registry 192.168.100.51:5000 --push, this does not push the built images17:41
inc0sure, thanks for dropping by jbryce!17:42
rwellumThat was very cool :)17:42
rwellumdardelean: you push then how are you verifying?17:42
rwellumdardelean: it helped me, when I build to add --tag "something unique" - then I could be sure.17:43
dardelean for profile in infra main aux default; do kolla-build --base ubuntu --type source --profile $profile; done17:43
dardeleanthis is how I built17:43
dardeleanabout verifiction, I can see that the push command starts to built centos images rwellum17:44
*** cah_link has quit IRC17:44
rwellumdardelean: sudo docker images - you see your new images?17:45
*** signed8bit is now known as signed8bit_Zzz17:45
*** signed8bit_Zzz has quit IRC17:45
dardeleani can see the base centos images, i stopped the built process of the push command17:45
dardeleanother than that, I see my ubuntu images rwellum17:45
rwellumok dardelean - sorry - so i am a little confused what the issue is. Have to pop out now for a bit. But inc0 is like 1000x better at this than me - I'm probably not understanding the issue.17:47
dardeleannp rwellum, thanks for the good help, as always :D17:47
inc0dardelean: that's strange...17:48
inc0--push means that after build it will jsut push17:48
dardeleanthis is master btw17:48
dardeleani run push in a separate command17:49
dardeleanwhen I run " kolla-build --registry 192.168.100.51:5000 --push", I already have the ubuntu images17:49
inc0ahh17:50
inc0well17:50
inc0as I said17:50
inc0push will build and push;)17:50
inc0not try to use existing images17:50
dardeleanso this is an atomic operation17:50
inc0yeah17:50
dardeleani see, from the docs I did not get this17:50
dardeleananother thing17:50
*** salv-orlando has joined #openstack-kolla17:50
inc0if you want to push separately do sth like this17:51
dardeleaneven so, shouldn't the kolla-built command check the image type from globals.yml?17:51
inc0kolla-build -b ubuntu -t source --registry 192...17:51
inc0then docker push images17:51
inc0no, globals.yml is ansible conf17:51
dardeleanoh, coz the images are already built it will skip image building17:52
dardeleanright?17:52
inc0but you can prepare kolla_build.conf17:52
inc0well it will use docker cache17:52
inc0so technically no, but it will be quite fast:)17:52
inc0kolla-build always builds.17:52
inc0--push means it will do more than that17:52
inc0but it will always build fresh images17:53
dardeleani do a tools/cleanup-images and do a " for profile in infra main aux default; do kolla-build --base ubuntu --type source --profile $profile --registry 192.168.100.51:5000 --push; done"17:54
dardeleansound right with you?17:54
inc0you can do kolla-build --profile aus --profile main --profile default17:55
inc0aux17:55
dardeleanah, ok17:55
inc0then it won't rebuild images present in 2 or more profiles17:55
inc0other than that looks good17:56
dardeleanok, doing so17:57
dardeleanthanks for the help inc017:59
inc0np17:59
*** salv-orlando has quit IRC18:01
*** mgoddard has quit IRC18:03
*** openstackgerrit has quit IRC18:03
yankcrimeinc0 do you know if anyone's working on this already: https://blueprints.launchpad.net/kolla/+spec/database-backup-recovery18:07
yankcrime(also hi)18:07
*** lukepatrick has quit IRC18:09
*** lukepatrick has joined #openstack-kolla18:14
inc0yankcrime: hey:) not that I know of18:14
*** yangyape_ has quit IRC18:16
yankcrimeinc0 ok, thanks18:16
*** yangyapeng has joined #openstack-kolla18:16
dardeleaninc0 works now, I can see images on the registry, eg "192.168.100.51:5000/kolla/ubuntu-source-redis-base"18:19
dardeleanand not on localhost18:19
inc0cool, great to hear that18:19
inc0well18:20
inc0they will be in registry itself too18:20
inc0(I hope;))18:20
*** david-lyle has quit IRC18:21
*** billp has joined #openstack-kolla18:21
*** Arminder- has joined #openstack-kolla18:22
*** Arminder has quit IRC18:23
dardeleanthat is the IP of the registry18:24
dardeleanbefore they appered differently18:24
inc0--registry did that18:25
*** Pavo has quit IRC18:37
rwellumdardelean: cool good news. Yeah that's why i asked you if this was build or deploy as you mentioned globals.yaml a couple of times.18:40
*** signed8bit has joined #openstack-kolla18:40
*** openstackgerrit has joined #openstack-kolla18:41
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla master: [WIP] Publisher pipeline with testing  https://review.openstack.org/52646918:41
*** Pavo has joined #openstack-kolla18:41
rwelluminc0: my kolla build pain is usually that I point at my local source and then push somewhere and I don't see my local source code. I usually have to add a peice of bad code inside my Service to make sure it's picking it up. I wish the log would show more clearly where the source code is coming from rather than /horzon/blah.18:49
inc0well, thing is we download code outside of regular docker build18:50
inc0https://github.com/openstack/kolla/blob/master/kolla/image/build.py#L39818:51
inc0it's kolla-build that will download tarball not docker build18:51
inc0you may want to add some logging to it18:52
*** mgoddard has joined #openstack-kolla18:52
*** niedbalski has quit IRC18:54
*** niedbalski has joined #openstack-kolla18:54
rwellumyeah can do inc018:55
*** vincent_vdk has joined #openstack-kolla18:57
rwellumkfox1111: did you see my question to Jonathon on the bridge to openstack he mentioned?18:57
kfox1111no18:58
kfox1111what was the question/response?18:58
inc0I'm sure we'll learn soon:)18:59
rwellumHe said: "I also like the fact that it bridges the tech living in both places. I also want to see more connections and collaboration"19:00
rwellumI aasked what that bridge was...19:01
rwellumHe said: "rwellum: the bridge for me is that this actually enables more cloud operators (including existing OpenStack users) to take containers into production for more workloads. That will drive more usage of the rest of the cncf toolkit"19:01
*** pramodrj07 has quit IRC19:13
*** MasterOfBugs has quit IRC19:13
sdakeinc0 back- will ook19:19
*** harlowja has joined #openstack-kolla19:21
*** jascott1 has joined #openstack-kolla19:22
sdakejascott1 bro19:22
sdakejascott1 quick question about guitar amps19:22
jascott1yassir19:22
sdakethe sales dude ended up selling us a black*something19:22
sdakeblackstar I think19:22
sdakeit looked good and sounded good when he played it19:23
sdake5watt tube19:23
jascott1ive never used them but seem good19:23
sdakegood to hear19:23
sdakethey have a knob that makes em US or UK sounding19:23
jascott1"UK 60s Boutique"19:23
jascott1just guessing, thats a popular sound19:24
*** MasterOfBugs has joined #openstack-kolla19:27
*** pramodrj07 has joined #openstack-kolla19:27
*** mgoddard has quit IRC19:29
jascott1shouldnt I see output from `ip netns` on kolla compute nodes?19:32
SamYaplejascott1: nope19:35
SamYaplejascott1: unless *maybe* with dvr19:35
SamYaplenot possitive19:35
*** DosBarbos has quit IRC19:36
mwynneSamYaple: If I'm doing a single controller, multiple compute node deployment, is that considered to be "Multiple node deployment"? Or is that only when you're deploying service containers to multiple nodes?19:38
SamYapleits not highly-available, but it would be multinode19:40
SamYaplehighly-available is thegood thing though19:40
jascott1SamYaple thanks!19:40
mwynneSamYaple: I'm just looking to get my feet wet with kolla right now so I'm planning on following the quick start guide to get something basic going, and get an understanding of how it all works.19:40
mwynneI'm assuming the quick start guide is the best for that?19:41
jascott1hey SamYaple any pointers for resolving this "[Error: Binding failed for port 20143fd1-87c5-45aa-b676-a28b6df468a4, please check neutron logs for more information.]."19:51
jascott1Im looking thru logs but not seeing anything so far19:52
mwynnejascott1: Probably missing/mismatching tunnel_types if you're using ovs19:53
jascott1mwynne thank you for the hint!19:56
SamYaplejascott1: yea just general "go look through the logs" error there. there is a stacktrace somewhere19:58
mwynneI don't think there's a stacktrace for that one. If I remember correctly it's a pretty well hidden debug message :(20:06
*** lpetrut has joined #openstack-kolla20:07
*** affie has joined #openstack-kolla20:08
*** sbezverk has joined #openstack-kolla20:14
*** david-lyle has joined #openstack-kolla20:16
*** ChanServ has quit IRC20:17
openstackgerritMerged openstack/kolla master: Fix deployment of ceph  https://review.openstack.org/52547020:17
*** lpetrut has quit IRC20:18
*** ChanServ has joined #openstack-kolla20:24
*** barjavel.freenode.net sets mode: +o ChanServ20:24
*** sbezverk has quit IRC20:29
*** affie has quit IRC20:30
*** sbezverk has joined #openstack-kolla20:31
*** david-lyle has quit IRC20:32
mwynnejascott1: was that it?20:41
jascott1mwynne not sure yet :)20:42
rwellumSamYaple: I guess it's not true HA unless you have bonded interfaces either?20:45
*** dgonzalez has left #openstack-kolla20:46
*** dgonzalez has joined #openstack-kolla20:46
openstackgerritGaëtan Trellu proposed openstack/kolla-ansible master: Nova upgrade fail because of missing condition  https://review.openstack.org/52677120:47
SamYaplerwellum: nah. because HA is about multiple services running, bonded interfaces is about keeping a single service online20:47
rwellumHmm interesting.20:47
rwellumsdake: 'a knob to make them us or uk sounding'....20:48
inc0it automatically translates "pants" in lyrics to "trousers"20:49
rwellumAnd cigarette to fag, check-mark to tick-mark... lol inc020:50
rwellumYou hit the UK knob and the weather turns to sh&t and everyone starts pouring salad dressing on their food.20:51
inc0lol20:52
inc0and better don't install this knob in your car. At least not on roads where lanes go both directions20:53
*** itlinux has quit IRC20:55
rwellumlol yeah20:56
rwellumFirst 'roundabout' I hit in the States I went the wrong way around.20:56
inc0you're Brit Rich?20:58
*** itlinux has joined #openstack-kolla20:58
rwellumYeah21:01
rwellumGlaswegian technically.21:01
kfox1111SamYaple: technically no. ha is availablity of the service. not nessiarily scaling.21:01
kfox1111though usually the best way to achieve ha is scaling.21:02
inc0cool, I need to visit Scotland at some point:)21:02
kfox1111quick failover to the point where it isn't noticed is another way to solve it.21:02
*** sbezverk has quit IRC21:02
kfox1111vrrp takes that route to ha for example.21:03
SamYaplekfox1111: yea sure. were really getting into the technical defintion21:03
SamYaplebut if youve only got one copy of the service... its not ha in my opinion21:03
kfox1111yup. scaling an ha are seperate but sometimes related things.21:03
SamYaplethough it could be argued as such i suppose21:03
SamYaple:+1:21:03
mwynneI'm getting a weird error during prechecks: hostvars[inventory_hostname]['ansible_' + api_interface]['ipv4']['address'] }}: 'dict object' has no attribute u'ansible_ens3'21:03
mwynneglobals.yaml contains -> api_interface: "ens3"21:04
mwynnewtf? haha21:04
kfox1111semantics on that one  I guess. one active copy with a backup copy is just one copy?21:04
inc0do you have interface ens3?21:04
inc0on all nodes?21:04
SamYaplekfox1111: thats still two copies though21:04
kfox1111ok. under that definition we're in full agreement. :)21:04
inc0and ens3 on all nodes has IPv4?21:04
mwynneinc0: 99% sure I do, but I'll double check :)21:04
mwynneinc0: Yeah, they all have an ens3 interface with ipv4 addresses21:05
SamYaplekfox1111: as always :) we tend to be on the same page at the core21:06
kfox1111yup. :)21:06
rwelluminc0: you should it's amazing.21:06
kfox1111language/definitions/communication often is more difficult then logic. :)21:07
rwellumI set up Openstack deployment last year and they insisted it wasn't HA until I bonded everything. Pain in the rear as apparently RH heat templates think there's only one sequence that interfaces are instantiated.21:08
mwynneinc0: Any other ideas? It's failing during the check for an open memcached port on my controller, which definitely has an addressed ens3 interface.21:09
kfox1111heh. thats one way to get ha.21:09
kfox1111but there are others.21:09
inc0mwynne: yeah that's strange, try running ansible -m setup -i your-inventory control21:10
inc0and see if ansible_ens3 is there21:10
kfox1111ah network attachment, but not ha switches is lesser of ha then replicated nodes and no multi attach with 3 top switches.21:10
kfox1111ha is like security. there is aways more you can do at a greater expense. :)21:10
mwynneinc0: http://paste.openstack.org/show/628480/21:11
mwynne:S21:11
inc0and ansible_ens3?21:12
kfox1111dual nic connections to a switch is rarely the best solution IMO though.21:12
mwynnehttp://paste.openstack.org/show/628481/21:12
mwynneinc0: ^21:12
*** unicell has joined #openstack-kolla21:13
inc0uhh...beats me:/21:13
inc0dunno mwynne21:13
mwynnehaha of course21:13
inc0https://github.com/openstack/kolla-ansible/blob/master/ansible/site.yml#L7 :(21:15
inc0this shoudl work...21:15
mwynneinc0: http://paste.openstack.org/show/628482/21:16
mwynneFull error there21:16
*** Pavo has quit IRC21:16
mwynneI don't think there's an undefined variable in there...21:17
*** k_mouza has joined #openstack-kolla21:17
mwynneSamYaple: Any ideas here?21:18
mwynneI just pip installed kolla-ansible. Do I need to specify a version? Did I somehow get a buggy version or something?21:19
inc0unlikely21:19
inc0well21:19
inc0what version of ansible you have?21:19
mwynneinc0: https://pastebin.com/pfzFkUeE21:21
inc0hmm that's a stretch, but try to install ansible 2.321:22
inc0it's better tested21:22
inc0that being said, there is no reason why 2.4+ shouldn't work...I mean I really don't know21:22
*** k_mouza has quit IRC21:22
inc0basically this error happens if your node woudln't have ens3 or fatch gathering didn't catch ens3 for whatever reason21:22
mwynnepip uninstall ansible21:23
mwynnewhoops :)21:23
*** david-lyle has joined #openstack-kolla21:24
*** dave-mccowan has quit IRC21:25
mwynneinc0: that seems to have fixed it.21:26
inc0hmm good to know21:26
*** david-lyle has quit IRC21:29
mwynneinc0: Is there a recommended tag version to use?21:30
mwynneI'm using 4.0.0 right now21:30
mwynneHow can I map those to specific versions of OS?21:30
inc0well 4.0 is ocata21:33
inc05.0 is pike21:33
inc0that's how it works21:33
mwynneah ok21:33
inc0if you install kolla 4.0 it will install ocata and tag it with 4.021:34
inc0I highly recommend to use kolla-ansible and kolla versions in sync21:34
inc0as they're tested together and there are gimmicks that might differ version to version21:34
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla master: [WIP] Publisher pipeline with testing  https://review.openstack.org/52646921:39
mwynneinc0: so I should be doing pip install kolla==4.0 and pip install ansible==2.3 and using a tag of 4.0?21:42
rwelluminc0: master worked for me btw - with kolla-k8s (from dockerhub). Pike still not there correct?21:42
rwellummwynne: I think you should checkout the version of kolla that matches your image version, then do: "pip install -r requirements.txt"21:43
rwellummwynne: been the most stable way to go for me21:44
mwynnerwellum: Ah, good to know.21:45
inc0rwellum: right, zuul hickup this night prevented it from merging:(21:46
inc0https://review.openstack.org/#/c/526421/1 trying again21:47
inc0but I'm glad master works, we'll be able to add kolla-k8s testing of images before publishing21:47
inc0I'm working on testing pipeline for publishing and it seems to be going well21:48
rwelluminc0: it's a conspiracy to keep me away from official pike images so my user story never completes...21:55
inc0lmao21:55
inc0whole world is in it21:55
rwellumIt is...21:55
inc0you've discovered us, now I have to send hitman squad...sorry man nothing personal21:56
rwellumUrgh - not again...21:56
* rwellum switches country yet again21:56
*** Pavo has joined #openstack-kolla21:56
*** goldyfruit has quit IRC21:57
*** Pavo has quit IRC21:59
*** itlinux has quit IRC22:01
mwynneinc0: How can I kill all containers/images etc to start from scratch?22:09
mwynneI need to change versions etc and want to blow away the stuff I have right now22:09
mwynnekolla-ansible destroy didn't wipe it all?22:10
inc0kolla-ansible destroy22:10
inc0it should22:10
mwynneinc0: Ignore me. helps if you give it a manifest file :)22:10
inc0manifest? you mean inventory? yeah it's definetly helpful22:11
mwynneinventory, yeah.22:12
*** itlinux has joined #openstack-kolla22:16
*** itlinux has quit IRC22:18
rwelluminc0: if i want to add two section to cinder.conf - and one over-ride (different enabled_backend) - how is the best way to do this? This is in k8s, but it's pure ansible.22:22
rwellumRight now I am hacking the cinder.conf.j2 - but that's obviously not the way to go22:23
mwynneinc0 or SamYaple: Either of you know what may be causing this: "FAILED - RETRYING: Waiting for nova-compute service up (XX retries left)."22:30
inc0mwynne: check nova-compute lgos22:30
mwynneinc0: My nova_compute container doesn't have a compute log..22:34
inc0how so?22:36
mwynneinc0: Oh, it's just not in /var/log/nova/, it's in /var/log/kolla/nova22:36
inc0yup22:36
inc0or /var/lib/docker/volumes/kolla_logs/_data22:37
inc0if you want to access it from host22:37
mwynneIt can't contact my rabbitmq, because the container apparently isn't up, or it's continuously rebooting: Error response from daemon: Container 635eb4da2563edb593a554752817c22c5ed54900e06dda97d715b19082ad966e is restarting, wait until the container is running22:38
inc0sooo one of common issues with rabbitmq is that it will require hostnames22:38
inc0so all control nodes needs to be able to resolve all each other22:38
mwynnethey can22:38
inc0and IP it resolves to needs to be api_iinterface22:39
*** skramaja has quit IRC22:39
mwynneinc0: I think the issue is: 635eb4da2563edb593a554752817c22c5ed54900e06dda97d715b19082ad966e is restarting, wait until the container is running22:42
mwynneI can't connect to the container22:42
mwynneso obviously nothing else will be able to contact services running inside it22:42
inc0question is why it's restartng22:43
inc0restarting means something is wrong with it22:43
*** jascott1 has quit IRC22:43
mwynneyup22:43
*** hawi has quit IRC22:46
*** lukepatrick has quit IRC22:51
mwynneinc0: overlayfs: upperdir is in-use by another mount, accessing files from both mounts will result in undefined behavior.22:54
mwynneI managed to get that from dmesg before the container restarts again22:54
mwynneI have MountFlags=shared in my service file. I assumed that was maybe the issue.22:54
inc0well, MountFlags=shared is required by neutron22:57
mwynneSorry, I meant that not having that might have been the issue, but I do have it.22:59
*** hawi has joined #openstack-kolla23:03
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla master: [WIP] Publisher pipeline with testing  https://review.openstack.org/52646923:04
*** Pavo has joined #openstack-kolla23:09
mwynneinc0: I think there's a kernel/docker issue with my versions23:11
*** signed8b_ has joined #openstack-kolla23:12
inc0lol you're not very lucky today;) fyi best tested versions of docker are 1.12 and 1.1323:12
*** Pavo has quit IRC23:12
mwynneinc0: how do those docker versions connect to: Docker version 17.11.0-ce, build 1caf76c23:12
inc0docker has a track record of breaking stuff so I'd try sticking to these23:12
inc0older23:12
mwynnehow do you know? haha23:12
inc0right after 1.13 docker changed model of versioning to 17.04 and so on23:13
inc0don't ask me why23:13
mwynneoh ok23:13
inc01.13 was last semver one23:13
mwynneCome on docker!23:13
mwynnehaha23:13
*** signed8bit has quit IRC23:15
*** Pavo has joined #openstack-kolla23:15
*** jascott1 has joined #openstack-kolla23:16
*** signed8b_ has quit IRC23:16
mwynneinc0: what's the best way to get an older version of docker?23:23
mwynneI downgraded my kernel, but that didn't help..23:24
inc0if you use apt or yum, I think 1.13 is newest non-docker repos carry23:24
*** jemcevoy has joined #openstack-kolla23:24
inc0you can also use our bootstrap-servers playbook23:24
inc0kolla-ansible bootstrap-servers23:24
inc0it will install all the things in correct versions23:25
inc0I'm off for now, going for early dinner, I'll be back later23:25
inc0good luck mwynne :)23:25
mwynneThanks23:27
*** japestinho has quit IRC23:35
*** unicell has quit IRC23:42
kfox1111yeah. distro's are at 1.12 or 1.13.23:45
kfox1111just avoid docker inc's repos.23:45
mwynnekfox1111: the 4.0.0 rabbit container is teh only one giving me problems23:46
mwynnethe rest all come up fine23:46
mwynnerabbit's rebooting constantly23:47
kfox1111anything in the logs?23:47
mwynnewhich logs?23:47
kfox1111kubectl logs ....23:48
mwynnei'm not using kubernetes...23:48
kfox1111oh. nm then.23:48
kfox1111can't help too much then.23:48
kfox1111docker logs?23:49
mwynnewhere are those?23:49
mwynnenothing in /var/log/23:49
kfox1111on the host, docker logs xxxx23:49
mwynnekfox1111: http://paste.openstack.org/show/628487/23:52
mwynneover and over again23:52
kfox1111inc0: does kolla-ansible use a hostpath or a volume for its logs?23:53
kfox1111docker exec -it xxxxx cat /var/log/kolla/*/*  maybe?23:53
kfox1111doh.... lets encrypt has been saying january for wildcard certs for a while... now they are saying:23:55
kfox1111"We are planning to have a public test API endpoint up by January 4, and we’ve set a date for the full launch: Tuesday, February 27."23:55
kfox1111:_(23:56
mwynnekfox1111: telling me no such file or dir23:58
mwynneit doesn't like the wildcards I think23:58
kfox1111yeah. then I guess we'll have to wait for someone to answer the where question.23:58
*** dardelean_ has joined #openstack-kolla23:59

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