Thursday, 2016-02-11

*** jtriley has quit IRC00:03
*** thumpba has joined #kolla00:13
*** thumpba has quit IRC00:17
*** jtriley has joined #kolla00:26
*** aginwala has quit IRC00:42
*** aginwala has joined #kolla00:45
*** aginwala has quit IRC00:46
*** aginwala has joined #kolla00:46
*** neilus has joined #kolla00:49
*** neilus has quit IRC00:54
*** Jeffrey4l has joined #kolla00:56
*** Jeffrey4l has quit IRC01:07
*** jtriley has quit IRC01:09
*** aginwala has quit IRC01:13
*** Jeffrey4l has joined #kolla01:20
*** aginwala has joined #kolla01:20
*** achanda has quit IRC01:21
*** jtriley has joined #kolla01:32
*** achanda has joined #kolla01:33
*** aginwala has quit IRC01:35
*** jasonsb has joined #kolla01:35
*** dims_ has joined #kolla01:37
*** dims has quit IRC01:38
*** dims_ has quit IRC01:41
*** ssurana has quit IRC01:44
*** alisonh has quit IRC01:46
*** dims has joined #kolla01:49
*** alisonh has joined #kolla01:51
SamYaplestvnoyes: ack02:06
SamYapleAJaeger: nope. review them both, makes complete sense. openstack-ansible also made the switch to linters so you may want to ping them02:07
*** Jeffrey4l has quit IRC02:08
*** jasonsb has quit IRC02:10
*** Jeffrey4l has joined #kolla02:11
*** jasonsb has joined #kolla02:13
*** jasonsb has quit IRC02:14
*** unicell has quit IRC02:14
*** ByPasS_ has joined #kolla02:14
*** openstackgerrit has quit IRC02:15
*** ByPasS has quit IRC02:15
*** ByPasS_ is now known as ByPasS02:15
*** openstackgerrit has joined #kolla02:23
*** Jeffrey4l has quit IRC02:25
*** neilus has joined #kolla02:37
*** neilus has quit IRC02:43
*** Jeffrey4l has joined #kolla02:49
*** haplo37 has joined #kolla03:06
*** Marga_ has quit IRC03:21
*** haplo37 has quit IRC03:25
*** haplo37 has joined #kolla03:26
openstackgerritJeffrey Zhang proposed openstack/kolla: Do not pull rabbitmq-data image  https://review.openstack.org/27885103:29
openstackgerritJeffrey Zhang proposed openstack/kolla: Do not pull rabbitmq-data image  https://review.openstack.org/27885103:31
openstackgerritRuslan Kamaldinov proposed openstack/kolla: Output image statuses to log instead of return value of main function  https://review.openstack.org/27885303:43
*** jasonsb has joined #kolla03:52
*** aginwala has joined #kolla04:04
*** jtriley has quit IRC04:21
*** neilus has joined #kolla04:26
*** Marga_ has joined #kolla04:30
*** neilus has quit IRC04:30
*** Marga_ has quit IRC04:32
*** Marga_ has joined #kolla04:33
*** aginwala has quit IRC04:34
*** salv-orl_ has joined #kolla04:41
*** dims has quit IRC04:43
*** salv-orlando has quit IRC04:44
*** haplo37 has quit IRC04:44
*** chandankumar has joined #kolla04:47
*** chandankumar has quit IRC04:49
*** chandankumar has joined #kolla04:51
*** tzn has joined #kolla05:01
*** tzn has quit IRC05:06
*** aginwala has joined #kolla05:08
*** aginwala has quit IRC05:12
*** dave-mcc_ has quit IRC05:15
*** chandankumar has quit IRC05:36
*** chandankumar has joined #kolla05:36
*** opennode has joined #kolla05:48
*** chandankumar has quit IRC05:55
*** chandankumar has joined #kolla05:57
*** chandankumar has joined #kolla05:58
*** chandankumar has quit IRC06:01
*** chandankumar has joined #kolla06:02
*** opennode has quit IRC06:03
*** chandankumar has quit IRC06:08
*** neilus has joined #kolla06:14
*** neilus has quit IRC06:18
*** unicell has joined #kolla06:37
*** opennode has joined #kolla06:39
*** unicell has quit IRC06:42
*** unicell has joined #kolla06:43
*** aginwala has joined #kolla07:02
ajafoo/07:57
*** fgimenez has joined #kolla08:02
*** fgimenez has quit IRC08:02
*** fgimenez has joined #kolla08:02
*** aginwala_ has joined #kolla08:09
*** achanda has quit IRC08:11
*** aginwala has quit IRC08:11
*** achanda has joined #kolla08:14
openstackgerritAndreas Jaeger proposed openstack/kolla-mesos: Make pep8 *the* linting interface  https://review.openstack.org/27861908:19
openstackgerritAndreas Jaeger proposed openstack/kolla: Make pep8 *the* linting interface  https://review.openstack.org/27861608:20
*** athomas has joined #kolla08:21
*** chandankumar has joined #kolla08:23
AJaegerSamYaple: openstack-ansible is not a python project, so no problem with them...08:23
AJaegerthanks, SamYaple08:24
*** chandankumar has quit IRC08:28
*** chandankumar has joined #kolla08:29
*** macsz has joined #kolla08:30
*** tzn has joined #kolla08:35
*** shardy has joined #kolla08:40
*** shardy has quit IRC08:41
*** shardy has joined #kolla08:42
*** tzn has quit IRC08:42
*** aginwala_ has quit IRC08:43
*** achanda has quit IRC08:44
*** aginwala has joined #kolla08:44
*** openstackgerrit has quit IRC08:47
*** openstackgerrit_ has joined #kolla08:47
*** kproskurin has joined #kolla08:47
*** openstackgerrit_ is now known as openstackgerrit08:48
*** aginwala has quit IRC08:49
*** alisonh has quit IRC08:52
*** rmart04 has joined #kolla08:54
*** mbound has joined #kolla09:02
*** rmart04 has left #kolla09:05
*** Serlex has joined #kolla09:15
Serlex--include-header .header --include-footer .footer09:15
Serlexis that the correct format to bypass proxy server?09:15
*** alisonh has joined #kolla09:17
*** AJaeger has left #kolla09:20
*** ccesario has quit IRC09:50
Serlexanyone?09:51
*** gfidente has joined #kolla09:55
*** gfidente has joined #kolla09:55
openstackgerritAndreas Jaeger proposed openstack/kolla: Make pep8 *the* linting interface  https://review.openstack.org/27861609:55
*** tzn has joined #kolla09:57
*** kklimonda has quit IRC10:00
*** ccesario has joined #kolla10:01
*** macsz1 has joined #kolla10:06
*** macsz has quit IRC10:07
*** opennode has quit IRC10:07
*** akwasnie has joined #kolla10:13
*** akwasnie has quit IRC10:14
openstackgerritMarek Zawadzki proposed openstack/kolla: Small fix in doc: root permissions for 'pip install kolla/'  https://review.openstack.org/27853210:14
*** akwasnie has joined #kolla10:14
*** macsz1 has quit IRC10:18
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Fix ubuntu config path search  https://review.openstack.org/27896310:21
openstackgerritMarek Zawadzki proposed openstack/kolla: Added note about root permissions, removed sudos.  https://review.openstack.org/27853210:26
*** macsz has joined #kolla10:33
*** salv-orlando has joined #kolla10:42
*** achanda has joined #kolla10:44
*** salv-orl_ has quit IRC10:45
*** fgimenez has quit IRC10:47
*** dims has joined #kolla10:48
*** fgimenez has joined #kolla10:49
*** fgimenez has quit IRC10:49
*** fgimenez has joined #kolla10:49
*** achanda has quit IRC10:51
*** chandankumar has quit IRC11:21
*** shardy has quit IRC11:26
*** jmccarthy has quit IRC11:27
*** jmccarthy has joined #kolla11:28
*** shardy has joined #kolla11:28
*** Marga_ has quit IRC11:36
*** Marga_ has joined #kolla11:37
*** chandankumar has joined #kolla11:42
*** shardy has quit IRC11:46
*** achanda has joined #kolla11:48
*** achanda has quit IRC11:52
*** chandankumar has quit IRC12:04
*** fgimenez has quit IRC12:13
*** fgimenez has joined #kolla12:13
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Improve logging of cleaup script  https://review.openstack.org/27900612:15
*** chandankumar has joined #kolla12:17
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: We forgot to add mesos section to config  https://review.openstack.org/27901212:22
*** chandankumar has quit IRC12:22
*** dims has quit IRC12:40
*** akwasnie has quit IRC12:41
*** akwasnie has joined #kolla12:44
*** jtriley has joined #kolla12:54
*** jtriley has quit IRC13:00
*** shardy has joined #kolla13:14
*** dims has joined #kolla13:20
*** Guest57497 is now known as zeus13:22
*** zeus has joined #kolla13:22
*** akwasnie has quit IRC13:26
*** akwasnie has joined #kolla13:32
openstackgerritJeffrey Zhang proposed openstack/kolla: Ensuring the rsyslog service to be ready  https://review.openstack.org/27906413:41
*** jpeeler has joined #kolla13:46
*** achanda has joined #kolla13:50
*** rhallisey has joined #kolla13:51
*** jtriley has joined #kolla13:54
*** achanda has quit IRC13:55
*** rhallisey has quit IRC13:56
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: We forgot to add mesos section to config  https://review.openstack.org/27901213:59
*** jtriley has quit IRC13:59
*** dave-mccowan has joined #kolla14:08
*** dave-mcc_ has joined #kolla14:11
*** dave-mccowan has quit IRC14:14
ajafoI've sthg like this CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Unable to establish connection to https://127.0.0.1:3535714:16
ajafodoes anyone know from which place is this address taken?14:17
ajafoI've in neutron.conf other one :/14:17
*** rhallisey has joined #kolla14:18
*** rhallisey has quit IRC14:22
*** akwasnie has quit IRC14:22
*** rhallisey has joined #kolla14:26
*** rhallisey has quit IRC14:30
*** rhallisey has joined #kolla14:30
*** JoseMello has joined #kolla14:34
*** rhallisey has quit IRC14:35
*** rhallisey has joined #kolla14:36
*** jtriley has joined #kolla14:38
*** rhallisey has quit IRC14:41
*** fgimenez has quit IRC14:45
elemoine_how did you get that error? what command did you run?14:46
*** fgimenez has joined #kolla14:47
*** jtriley_ has joined #kolla14:50
*** macsz has quit IRC14:50
*** jtriley has quit IRC14:53
ajafoelemoine_: its in neutron_server log14:58
ajafoelemoine_: and it's after try of log in to horizon14:58
*** alyson_ has joined #kolla15:02
openstackgerritJeffrey Zhang proposed openstack/kolla: [WIP] Ensuring the openvswitch_db is ready before creating bridges  https://review.openstack.org/27557315:04
elemoine_ajafo: isn't tihis related to kolla_internal_address?15:04
elemoine_I don't know for sure15:05
*** sdake_ has joined #kolla15:11
ajafoI've right internal adress 10.10.10.254 :/15:11
elemoine_strange15:11
sdake_morning15:11
sdake_so beat ass tired15:11
elemoine_hi15:12
sdake_midcycle was alot of work ;)15:12
ajafomorning15:12
openstackgerritSteve Noyes proposed openstack/kolla-mesos: Add state info to commands  https://review.openstack.org/27142215:12
brittho__morning!15:13
openstackgerritMerged openstack/kolla-mesos: Updated from global requirements  https://review.openstack.org/27867915:15
elemoine_sdake_: it would be good to know the outcomes15:16
sdake_everything is in the etherpad15:16
sdake_but one thing in particular, the stablke branch managemnt, is coming to the mailing list15:16
*** sdake_ is now known as sdake15:16
elemoine_ok15:17
sdakewe cancelled hte session on diags because both you and akscram were not able to make it15:17
sdakesorry akwasnie15:17
sdakebut that doesn't mean its not important15:17
*** rhallisey has joined #kolla15:18
sdakemorning rhallisey15:18
*** rhallisey has quit IRC15:23
*** blahRus has joined #kolla15:32
*** achanda has joined #kolla15:34
*** macsz has joined #kolla15:35
*** rhallisey has joined #kolla15:35
*** dave-mcc_ has quit IRC15:37
*** dave-mccowan has joined #kolla15:37
*** rhallisey has quit IRC15:39
openstackgerritJeffrey Zhang proposed openstack/kolla: Ensuring the rsyslog service to be ready  https://review.openstack.org/27906415:42
*** achanda has quit IRC15:42
sdakeelemoine_ i will send a summary email - like a trip report - of the Kolla midcycle15:46
sdakei think thats a good idea15:46
*** rhallisey has joined #kolla15:46
sdakeI think paul did that last time for the main ODS in Tokyo15:46
sdakepbourke that is15:46
elemoine_cool15:48
*** jtriley_ has quit IRC15:48
*** macsz has quit IRC15:50
*** rhallisey has quit IRC15:51
*** jtriley has joined #kolla15:54
*** rhallisey has joined #kolla15:55
*** iNeilus has joined #kolla15:57
*** iNeilus has quit IRC15:57
*** iNeilus has joined #kolla15:58
*** limamauricio has joined #kolla15:59
*** fthiagogv has joined #kolla15:59
*** rhallisey has quit IRC15:59
*** achanda has joined #kolla15:59
limamauricioSamYaple, i'm trying to deploy kolla binary on centos and running kolla-ansible deploy i have this error fatal: [localhost -> localhost] => error while evaluating conditional: database_api.stdout.split()[2] != 'SUCCESS'; More details ->http://pastebin.com/6eJxsLk716:01
*** achanda has quit IRC16:02
claytonDoes Kolla support HA routers with keepalived ?16:02
*** stvnoyes has quit IRC16:06
*** stvnoyes has joined #kolla16:07
*** sbezverk has joined #kolla16:08
sdakelimamauricio looking16:09
*** shardy has quit IRC16:10
sdakeclayton roger with keepalived, VRRP HA-ifys our HAProxy which is sort o fa "HA Router"16:10
sdakewe run haproxy on every controller node16:10
sdakeclayton does that answer your Q?16:10
claytonyeah, I meant for L3 HA routers though, which I think is separate16:10
claytonthe neutron l3 agent starts them in that case I believe16:10
claytonfor tenant networking routers, not API access16:11
sdakeoh that  type of ha router16:11
sdakethe plugins for Neutron related to load balancing are not implemented16:11
sdakeplugins -> Newton16:11
sdakethat said, you could probably hack something together if it was a priority for you16:12
sdakewe want to soslve it in a correct general way16:12
sdakeand there is not enoug htime left in Mitaka to get to it16:12
sdakeSlower please give me operator thanks :)16:12
sdakelimamauricio are you on master or stable/liberty?16:13
limamauriciomaster16:13
sdakebuilding ffrom source or packaging?16:13
limamauriciopack16:13
sdakeoh ya kolla_toolbox, duh I should have seen that16:13
sdakeRDO packaging then?16:13
sdakeCentos distribution?16:13
*** haplo37 has joined #kolla16:13
limamauricioyes16:14
limamauricioCentos, binary16:14
sbezverkhello, I am trying to bring up kolla deployment node inside of a Ubuntu 14.04.3 VM, kind of bare metal deployment scenario. I see partial success of kolla-build, most of images are correctly built, but some failed. Appreciate some guidance in troubleshooting.16:14
*** rhallisey has joined #kolla16:14
sdakesbezverk can you paste the list of vms that build vs dont build (the tail of the build log)16:15
sdakelimamauricio your using ansible 1.9.4 correct?16:15
limamauricioyes16:15
sdakelimamauricio your using latest master, not something  from a couple weeks ago?16:16
sdakethe nova-api stuff is new, its possible it was implemented incorrectly or is broken16:16
limamauriciomaybe16:16
limamauricioomg16:16
sdakeits not our fault nova implemented a ddatabase :)16:16
sdakein the api16:16
limamauriciook16:16
sdakeit makes no sense but we have to adapt to it unfortunately16:16
*** Serlex has quit IRC16:17
limamauriciook, I'll16:17
limamauricio:)16:17
sdakeok so give mea  few minutes16:17
sdaketo look at the git blame16:17
limamauriciooh,16:17
limamauriciookay16:17
sbezverksdake INFO:kolla.cmd.build:Images that failed to build16:17
sbezverkINFO:kolla.cmd.build:===========================16:17
sbezverkERROR:kolla.cmd.build:murano-base Failed with status: error16:17
sbezverkERROR:kolla.cmd.build:murano-engine Failed with status: parent_error16:17
sbezverkERROR:kolla.cmd.build:mistral-engine Failed with status: parent_error16:17
sbezverkERROR:kolla.cmd.build:gnocchi-base Failed with status: error16:17
sbezverkERROR:kolla.cmd.build:murano-api Failed with status: parent_error16:17
sbezverkERROR:kolla.cmd.build:keystone Failed with status: error16:17
sbezverkERROR:kolla.cmd.build:mistral-executor Failed with status: parent_error16:17
sbezverkERROR:kolla.cmd.build:gnocchi-api Failed with status: parent_error16:17
sbezverkERROR:kolla.cmd.build:mistral-base Failed with status: error16:17
sdakeand see which patches should be there16:17
sbezverkERROR:kolla.cmd.build:gnocchi-statsd Failed with status: parent_error16:17
sdakeyikes16:17
sdakesbezverk can you paste that in a paste service paste.openstack.org16:17
sdakeor paste.fedoraproject.org please16:17
sdakedont paste into the channel unless its a 1-2 liner thanks :)16:18
sbezverksdake Sorry, my bad..16:18
sdakemultitasking ftl16:18
sdakelimamauricio do me a solid and type git status and tell me which commit your on16:18
*** macsz has joined #kolla16:19
sdakeno git status wont do that16:19
sdaketry git log16:19
sdakeand tell me last commit id16:19
sbezverksdake Paste #48671816:19
sdakesbez paste the link please16:20
sdakesbezverk16:20
limamauricioMerge: 1b3480e 5a251ca16:20
limamauricio Merge "Fix manila perms"16:20
sbezverksdake http://paste.openstack.org/show/486718/16:20
limamauricio7 days ago16:20
limamauriciocan i do a pull on my repo?16:20
limamauriciogit pull16:20
sdakelima you can do a git pull --rebase16:20
limamauriciook16:21
sdakegit pull will work too, it will just cause merging which is not ideal16:21
limamauricioso, can i run deploy now?16:22
sdakelimamauricio there was a commit on 2/5 to that area of hte codebase16:25
sdakesince bootstrap failed, it may make sense to cleanup16:25
sdakei'm unclear if our bootstrap with these new playbooks in master works well16:25
sdakebut you can try a deploy16:25
limamauriciook16:25
sdakeebez see your paste, looking now16:26
sdakesbezverk16:26
sdakesbezverk  are you on centos-binary?16:26
*** thumpba has joined #kolla16:26
sdakeoh yes i see you are16:26
sdakeok murano not buildign - totally normal16:27
sdakegnocchi not building - totally normal16:27
sdakemistral not building - totally normal16:27
sdakethe reason these 3 don't build is RDO doesn't contain these packages, so we just error out16:27
sdakeduring the build process, a message is printed indicating this16:27
sdakebut you may miss it along the way16:27
sdakethe fact that neither keystone nor horizon build is a serious problem16:27
sdakekeystone needs to build16:28
sdakeare you running master or stable/liberty sbezverk16:28
sdakejust rampant speculation, the thing keystone and horizon have in common is they use httpd to provide service16:28
*** absubram has joined #kolla16:28
sdakethese containers should always build16:29
sdakesbezverk tell me which version of kolla your running so I can try the build myself of these two containers16:29
*** akwasnie has joined #kolla16:33
sdakesbezverk  just run git status in the git repo16:35
sdakeit will say master or stable/liberty16:35
sdakeif you downloaded a tarball from a tag, which tag you downloaded from woudl be helpful16:36
sbezverksdake I followed baremetal deployment guide16:36
sbezverkstep by step without any modifications.16:37
*** pbourke has joined #kolla16:38
*** tpeoples has quit IRC16:38
*** JoseMello has quit IRC16:39
*** ayoung has quit IRC16:39
sdakesbezverk where did you get kolla from16:41
sdakegit clone http://github.com/openstack/kolla?16:41
sdakeor something else16:41
*** salv-orl_ has joined #kolla16:41
sdakedamn let me go read the docs again16:41
sdaketehy change all the time (for thebetter)b16:41
*** unicell1 has joined #kolla16:42
sdakeut I don't recall what they are atm16:42
sdakesbezverk  thse docs? http://docs.openstack.org/developer/kolla/quickstart.html16:42
sdakesbezverk  please link the docs you used or confirm the above doc link16:43
*** tpeoples has joined #kolla16:43
*** JoseMello has joined #kolla16:43
*** akwasnie has quit IRC16:43
*** unicell has quit IRC16:43
sdakelimamauricio  did using master help16:43
sbezverksdake yes16:44
limamauriciomaster help?16:44
*** salv-orlando has quit IRC16:44
sdakelimamauricio  did a git pull --rebase with a redeploy fix the problem?16:45
limamauricioi'm running build again16:45
*** Marga_ has quit IRC16:46
sdakelimamauricio fwiw current master is passing the gate per commit atm on your distro and type choices16:46
sdakethe gate woudl definately pick up that ansible failreu you saw16:46
sdakewhile your building16:46
*** Marga_ has joined #kolla16:46
haplo37Hi, to install liberty with ubuntu. What is the best git repo to use. Master or stable/liberty ?16:46
sdakecan you run pip show ansible16:46
limamauriciook16:46
sdakehaplo37 very complex question16:46
sdakelet me give you a ink for you to read later16:47
sdakebut then I'll explain what I'd do at present16:47
sdakehttps://etherpad.openstack.org/p/kolla-mitaka-midcycle16:47
*** akwasnie has joined #kolla16:47
limamauricioMetadata-Version: 1.0 Name: ansible Version: 1.9.4 Summary: Radically simple IT automation Home-page: http://ansible.com/ Author: Ansible, Inc. Author-email: michael@ansible.com License: GPLv3 Location: /usr/lib/python2.7/site-packages Requires: paramiko, jinja2, PyYAML, setuptools, pycryptoMetadata-Version: 1.0 Name: ansible Version: 1.9.4 Summary: Radically simple IT automation Home-page: http://ansible.com/ Author: Ansible, In16:48
*** guillaume__ has joined #kolla16:48
sdakehaplo37 https://etherpad.openstack.org/p/kolla-mitaka-midcycle-backport16:48
sdakelima thanks16:48
*** akwasnie has quit IRC16:48
sdakelimamauricio  let me know how the deploy goes with a rebased masster16:48
limamauriciook16:48
sdakehaplo first question, do you plan to evaluate or actually deploy into production?16:49
haplo37sdake: Thanks you16:49
haplo37sdake: Yes i plan to evaluate if we can deploy Kolla in production.16:49
sdakehaplo37 ok so basically, stable/liberty does not meet the definition of a stable branch16:50
sdakethis is mostly triggered by two things16:50
rhalliseysdake, that email coming out soon?16:50
guillaume__sdake: that stange to name it stable then, no?16:50
sdakerhallisey as soon as the foam is gone16:50
rhallisey:)16:50
sdakeguillaume__ getting there :)16:50
rhalliseyguillaume__, there is an explanation16:51
sdakehaplo37 the first thing its triggered by the fact that ansible and docker do not play well together16:51
sdakehaplo37 the second thing with stable is that the data containers and ansible do not play well together, which could result in DATA LOSS16:51
sdakealmost all of these problems are unfortunately caused by the way ansible and docker manage their mdoules we depend on16:52
sdakein master, we wrote our own module to take control of our own destiny16:52
sdakethis fixes all of the docker problems in stable/liberty16:52
sdakethat module needs to be backported16:52
sbezverksdake http://paste.openstack.org/show/486732/16:52
*** ayoung has joined #kolla16:52
sdakethe nthe playbooks need to be changed to match module16:53
sdakehaplo37 this iis probably about 5-10 patches to stable/liberty16:53
sdakehaplo37 its being worked on, but its not ready to go yet16:53
sdakehaplo37 if you want to evaluate kolla, I'd highly recommend using master for eval16:53
sdakeand then deploy stable/liberty once we fix the mess docker and ansible have created with their module16:54
sdakewe will tag a 1.1.0 release in kolla16:54
sdakethis will meet our definition of stable16:54
sdakeand not have data loss16:54
sdakeguillaume__ make sense?16:54
haplo37sdake: Ok thank you sdake for your help :-). I try this right know16:54
sdakehaplo37 i'm from the federal government, and I'm here to help :)16:55
sdakesbezverk thanks your on master16:56
sdakejust a moment, let me try buidling master keystone16:56
*** jmccarthy1 has joined #kolla16:57
*** jmccarthy1 has quit IRC16:57
sdakeis inc0 about ?16:58
*** akwasnie has joined #kolla16:59
*** pbourke has quit IRC17:01
guillaume__sdake: I understand now thank you17:03
sdakeguillaume__ cool17:03
sdakei do plan to post this to the mialing list17:03
sdakeas soon as I get folks rolling this morning17:03
openstackgerritEric Lemoine proposed openstack/kolla: Make Heka collect kolla-toolbox logs  https://review.openstack.org/27919117:06
openstackgerritEric Lemoine proposed openstack/kolla: Add Heka log decoder for Keystone/Apache  https://review.openstack.org/27919217:06
openstackgerritEric Lemoine proposed openstack/kolla: Make Heka collect Keystone logs  https://review.openstack.org/27919317:06
*** akwasnie has quit IRC17:06
*** ChanServ sets mode: +o rhallisey17:08
*** rhallisey sets mode: -o sdake17:08
*** rhallisey sets mode: +o sdake17:08
rhalliseysdake, there you are17:08
*** rhallisey sets mode: -o rhallisey17:08
*** britthou_ has joined #kolla17:09
*** macsz has quit IRC17:10
sdakefolks i have to run for about 45 mins to put my daughter's room back together since it just got tiled17:12
sdakeif i'm working with you on debug, work with rhallisey or i'll be back in about 1 hour17:12
*** sdake has quit IRC17:12
*** brittho__ has quit IRC17:12
*** fgimenez has quit IRC17:14
*** fgimenez has joined #kolla17:16
*** fgimenez has quit IRC17:16
*** fgimenez has joined #kolla17:16
*** jmccarthy1 has joined #kolla17:19
*** iNeilus has quit IRC17:19
*** fgimenez has quit IRC17:22
fthiagogvHi guys. Trying deploy kolla multinode occured an error: """ 500 Server Error: Internal Server Error for url: http+docker://localunixsocket/v1.22/images/create?tag=2.0.0&fromImage=control%3A4000%2Fkollaglue%2Fcentos-source-rsyslog' """. I am using 3 nodes, a compute(also storage), a network, a control. This error was shown for nework and compute. In control node I have the docker images built. Someone have any ideia?17:24
rhalliseyfthiagogv, where are u getting this from a container?17:28
rhalliseydont understand what your hitting17:28
*** athomas has quit IRC17:28
*** iNeilus has joined #kolla17:31
*** iNeilus has quit IRC17:32
*** iNeilus has joined #kolla17:32
*** unicell1 has quit IRC17:33
*** iNeilus has quit IRC17:42
*** kproskurin has quit IRC17:44
*** iNeilus has joined #kolla17:44
*** iNeilus has quit IRC17:44
*** iNeilus has joined #kolla17:44
fthiagogvrhallisey, the container are in local registry. But, I think that I made a mistake. I think that my registry are not available out of it machine. Thanks for attention. I will look this now.17:45
rhalliseyfthiagogv, ok cool17:47
*** ssurana has joined #kolla17:55
*** shardy has joined #kolla18:02
openstackgerritJeffrey Zhang proposed openstack/kolla: Ensuring the openvswitch_db is ready before creating bridges  https://review.openstack.org/27557318:02
*** unicell has joined #kolla18:06
sbezverkkeystone building is failing with these errors: INFO:kolla.cmd.build:keystone:error: unpacking of archive failed on file /usr/sbin/suexec: cpio: cap_set_file18:13
sbezverkINFO:kolla.cmd.build:keystone:Error unpacking rpm package httpd-2.4.6-40.el7.centos.x86_6418:13
sbezverkINFO:kolla.cmd.build:keystone:error: httpd-2.4.6-40.el7.centos.x86_64: install failed18:13
*** aginwala has joined #kolla18:14
rhalliseysbezverk, centos base distro ?18:14
sbezverkrhallisey yes18:15
rhalliseysbezverk, trying building it from source18:15
rhalliseyI'm gussing your using binary18:16
sbezverkrhallisey Yep18:16
openstackgerritJeffrey Zhang proposed openstack/kolla: Do not pull rabbitmq-data image  https://review.openstack.org/27885118:17
rhalliseysometimes the binary does break on packages18:17
rhalliseynot our fault, but it happens18:17
openstackgerritJeffrey Zhang proposed openstack/kolla: Ensuring the rsyslog service to be ready  https://review.openstack.org/27906418:18
sbezverkrhallisey any suggestions what should I do then?18:18
rhalliseysbezverk, build using source18:19
rhalliseyfor keystone or all of the container18:19
rhalliseyif you are having issues with others18:19
sbezverkrhallisey ok, will give it a try, thank you18:19
rhalliseysbezverk, no problem18:20
*** rmart04 has joined #kolla18:22
*** rmart04 has quit IRC18:27
*** Jeffrey4l has quit IRC18:30
*** sdake has joined #kolla18:31
sdakehey folks18:35
sdakeback18:35
sdakerhallisey op me plz so i can change topic18:35
rhalliseysure one sec18:35
*** rhallisey has quit IRC18:35
*** alyson_ has quit IRC18:36
*** mbound has quit IRC18:36
*** alyson_ has joined #kolla18:37
*** rhallisey has joined #kolla18:37
*** rhallisey has quit IRC18:41
*** dwalsh has joined #kolla18:45
*** gtt116__ has joined #kolla18:49
*** gtt116_ has quit IRC18:51
guillaume__sdake: is it normal that when I use kolla-build, it never use value from /etc/kolla/globals.yml to build images? I always need to add --base ubuntu -t source --tag liberty-rc1 .....18:55
*** tzn has quit IRC18:56
sdakeguillaume__ globals.yml is not used to build18:59
sdakethere is a file called build-conf.ini IIRC that does build config though18:59
sdakeit may be build-config.conf18:59
sdakeI dont recall exactly its definately in the etc directory18:59
sdakeit works fantastically well, all the devs use it19:00
sdakeI dont use it because I like to change around what I'm building all the time so I can make sure the whole thing works rathre then one set of limited options19:00
sdakeand i know there is test coverage on the oslo config for build-conf from other developers19:00
guillaume__sdake the file is not by default in the install ? I dont see it on the latest version of git19:01
sdakemoment19:02
haplo37./etc/oslo-config-generator/kolla-build.conf i think19:02
haplo37i dont think is that :)19:03
guillaume__ohh ok, sry though it would be in /etc/kolla sry. Thanks! So I just have to add all default value into it ? ^^19:03
*** rhallisey has joined #kolla19:10
rhalliseyfixed it..19:10
rhalliseyman my client was messed up19:10
rhalliseysdake, k opts coming19:10
*** ChanServ sets mode: +o rhallisey19:11
*** rhallisey sets mode: -o sdake19:11
*** rhallisey sets mode: +o sdake19:11
*** iNeilus has quit IRC19:15
*** rhallisey changes topic to "Kolla IRC meetings on Wednesday 16:30 UTC (Day light savings doesn't apply) - Agenda @ https://wiki.openstack.org/wiki/Meetings/Kolla - IRC channel is *LOGGED* @ http://eavesdrop.openstack.org/irclogs/%23kolla/"19:16
*** limamauricio has quit IRC19:17
*** iNeilus has joined #kolla19:17
*** iNeilus has quit IRC19:22
*** dwalsh has quit IRC19:31
guillaume__Do anybody know where can I get 1.9.4 on ansible ?19:32
sdakewhich distro?19:33
sdakeubuntu or centos?19:34
guillaume__ubuntu 14.0419:34
sdakecentos packages 1.9.4 by default19:34
guillaume__trusty19:34
sdakeubuntu trusty - our docs recommend installing via pip19:34
sdakepip install ansible==1.9.419:34
guillaume__will try19:34
sdakeif you already have ansible installed, pip remove ansible19:34
sdakeit mayb epip uninstall ansible19:34
sdaketrusty has a super old version of ansible and they dont update their packages19:35
guillaume__thanks a lot, it finnaly working!!! the deploy is running ^^19:39
*** shardy has quit IRC19:41
sbezverkrhallisey as per you suggestion I started "kolla-build --type source --registry 192.168.84.10:4000 --push"19:41
sbezverkthe script got stuck and not moving forward after completeling INFO:kolla.cmd.build:gnocchi-api:Successfully built 9553bb5e492319:42
sbezverkINFO:kolla.cmd.build:gnocchi-api:Built19:42
rhalliseysbezverk, I would not build that container19:42
rhalliseyyou only need core services19:42
sbezverkrhallisey is there a way to specify all cores services in one parameter, or I need to build one by one?19:43
rhalliseysbezverk, ya use regex19:47
rhallisey./tools/build.py regex nova neutron ...19:47
*** tzn has joined #kolla19:51
*** athomas has joined #kolla19:54
*** tzn has quit IRC19:55
*** aginwala has quit IRC19:56
*** unicell has quit IRC20:04
*** aginwala has joined #kolla20:04
*** unicell has joined #kolla20:04
*** tzn has joined #kolla20:05
ajafoI've sthg like this in neutron_server logs: CRITICAL keystonemiddleware.auth_token [-] Unable to validate token: Unable to establish connection to https://127.0.0.1:3535720:06
sbezverkrhallisey here is command I used: kolla-build regex nova neutron glance heat cinder ceph heat keystone horizon ceilometer --type source --registry 192.168.84.10:4000 --push, it got stuck too but before spitted: Exception in thread Thread-9: ReadTimeoutError: UnixHTTPConnectionPool(host='localhost', port=None): Read timed out.20:06
ajafodoes anyone know from which place is this address taken?20:06
*** ayoung has quit IRC20:06
sbezverkERROR:kolla.cmd.build:keystone:Error'd with the following message20:07
sbezverkERROR:kolla.cmd.build:keystone:The command '/bin/sh -c yum -y install         httpd         mod_wsgi     && yum clean all     && sed -i -r 's,^(Listen 80),#\1,' /etc/httpd/conf/httpd.conf' returned a non-zero code: 120:07
*** jasonsb has quit IRC20:09
rhalliseysbezverk, I'm going to try locally.. that build error is weird20:11
rhalliseynot sure what it's getting hung up on20:11
rhalliseysbezverk, you are on master right?20:13
sbezverkrhallisey yes20:13
*** tpot has quit IRC20:17
*** dwalsh has joined #kolla20:21
*** ayoung has joined #kolla20:22
haplo37I have some issue with starting neutron-dhcp-agent-container. I have this error : msg: APIError(HTTPError(u'500 Server Error: Internal Server Error for url: http+docker://localunixsocket/v1.22/containers/neutron_dhcp_agent/start',),).Does it tell you something ?20:25
*** rmart04 has joined #kolla20:28
*** slagle has quit IRC20:28
*** slagle has joined #kolla20:29
*** athomas has quit IRC20:31
*** rmart04 has quit IRC20:32
rhalliseysbezverk, so I didn't have any issues building keystone from source using master20:35
sbezverkrhallisey I guess, something wrong then with the way deployment host is setup.. I will try to re-build it and re-try..20:37
*** gfidente has quit IRC20:38
rhalliseysbezverk, ya I'm not sure what state your in.. Reset, clone kolla master, pip install -r requirements.txt, start docker, and you should be good to go20:38
*** aginwala has quit IRC20:40
*** aginwala has joined #kolla20:40
sdakeyou have to pip install test-requiremetns.txt fwiw20:41
sdakefor the build node20:41
sdakeour requirements file is clearly not correct20:41
*** cloudnau_ has joined #kolla20:42
sdakethanks for changing the topic whoever did that :)20:42
rhalliseysdake, :)20:42
*** rhallisey sets mode: -o rhallisey20:42
rhalliseysdake, hows the home improvement20:42
sdakeon room 6 of 620:42
sdakeon closet 2 of 320:42
rhalliseynice20:43
sdakeone of the closets is a 2 hour job20:43
sdakethe other closet is a 2 day job20:43
sdakeroom 6 of  6 is a 3-4 day job on my own20:43
sdaketrying to get robyn to throw me a bone on that one :)20:43
sbezverksdake what is interesting, if I run kolla-build with individual packet example, glance, it is working fine. As soon as I try to kolla-build many, it gets stuck..20:49
*** blahRus has quit IRC20:57
sdakegets stuck?20:57
sdakei have a meeting in 3 minutes20:58
sdakebut we need to get to the bottom of the getting stuck20:58
sdakethat is not good20:58
sdakenote a container will try to rebuidl itself 3 times20:58
sdakethis is because the mirrors sometimes fail20:58
sdakeit is possible you have a firewall issue20:58
sdakewhat would help the most is to do the following20:59
sdakerun20:59
sdakescript20:59
sdaketools/build.py --debug21:00
sdakeexit21:00
sdakepaste the typescrpit file21:00
sdakeback in 45 mins21:00
*** blahRus has joined #kolla21:00
haplo37What mean shared on starting neutron-dhcp-agent : /run/netns/:/run/netns/:shared. Because when i try to start the container, i have this issue : Path /run/netns is mounted on /run but it is not a shared mount.21:02
*** aginwala has quit IRC21:02
*** aginwala has joined #kolla21:03
d_codeso, I haven’t gotten kolla to fully deploy a node yet….  should all-in-one work on a CentOS 7 box if I build from RDO?  should I build from Source?21:05
guillaume__I'm just starting yet, but I had lots of trouble to get it from other than source (some package seems to be missing)21:06
d_codeor should I build on Liberty, since that’s a stable release21:06
guillaume__it's not stable tough21:06
guillaume__you need to use master version21:07
guillaume__of git21:07
guillaume__and than specified the version 1.0.0 in /etc/globals.yml (I don't know if it's 1.0.0 or liberty-rc1)21:07
guillaume__openstack_release: "liberty-rc1"21:07
d_codeand then do the source build21:08
*** mfalatic has joined #kolla21:08
guillaume__the source will not use the of the globals.yml21:09
guillaume__for that run the kolla-build with --base DISTRO_NAME (ubuntu, centos oraclelinux) -t source --tag 1.0.0 OR --tag liberty-rc121:09
*** aginwala has quit IRC21:11
guillaume__I had lots of trouble to build all images without errors ^^ I finaly fix it with this method21:13
*** aginwala has joined #kolla21:16
d_codeso:21:17
d_codekolla-build --base centos -t source --tag liberty-rc121:17
d_codethen deploy with setting openstack_release: “liberty-rc1"21:17
d_codeand build_type to source in the globals.yml21:18
guillaume__yeah, kindof. If centos --base is not needed21:18
d_codeand I have the local registry21:18
guillaume__nope21:18
haplo37or --tag 1.0.021:18
guillaume__I explain it to you21:18
guillaume__kolla-ansible use /etc/kolla/globals.yml21:18
guillaume__kolla-build use /etc/oslo-config-generator/kolla-build.conf21:19
guillaume__if you specified something into globals it will not use it for the build command. Just for the kolla-ansible21:19
guillaume__so you need to specified all correctly into globals21:19
guillaume__but allso give all the args to the build command (or add them to the oslo/kolla-build.conf21:20
guillaume__so to use you own registry21:20
guillaume__add --registry 0.0.0.0:5000 to the build command21:20
d_codewow…I’ve read through the quick start several times…first time I’ve seen to use oslo-config-generator21:20
guillaume__hahaha21:20
rhalliseyd_code, recommend building from master21:20
guillaume__me too21:20
guillaume__Learn it from sdake21:21
d_codethis is what I’ve done so far: https://gist.github.com/anonymous/51d9b51613c9913b6a8821:23
d_codeon fresh CentOS 7.2 minimal install w/ all updates21:23
d_codeI’d like to do all-in-one for starters (I have a second box currently, can retry once I have this working)21:23
guillaume__seems good to me21:24
d_codesame box is also hosting the registry21:24
guillaume__lots of stuff I never did to make it work, but seems good21:24
rhalliseyd_code, docker 1.9 is a needed to use master21:24
guillaume__yeah and ansible 1.9.421:24
d_codeso….what the hell do I do with /etc/oslo-config-generator ? :p21:24
d_codeah yes, rhallisey21:25
guillaume__registry = 0.0.0.0:500021:25
d_codeI upgraded to 1.1021:25
guillaume__tag = liberty-rc121:25
rhalliseyd_code, ok good21:25
guillaume__install_type = source21:25
rhalliseyd_code, so next you can build21:26
d_codeand I should add —tag=liberty-rc1 to the build command21:26
guillaume__and after that if you start the build then open a new tab with `watch -n3 docker images` you should see that the registry used is 0.0.0.0:5000/kollaglue/*21:26
d_codeso it tags in the registry, right?21:26
rhalliseyrecommend building from source and using regex in your build cmd21:26
*** britthouser has quit IRC21:27
*** iNeilus has joined #kolla21:27
rhalliseybrb21:28
*** britthou_ has quit IRC21:28
*** britthouser has joined #kolla21:32
d_codek…  here’s what I’m doing now: https://gist.github.com/dcode/aea450c1648034067637 (added globals and oslo config)21:32
d_codehere we go….21:33
d_codedefinitely a really nice thing about kolla is…I can screw up the build and install, all I really have to do is wipe out docker and the registry using the clean-* scripts and I’m good to go21:34
guillaume__if you put values to the oslo/kolla-build.conf you dont need to give the ARGS to the kolla-build script anymore21:34
d_codeinstall using packstack and screw it up…well….rebuild the host, basically21:34
*** iNeilus has quit IRC21:34
guillaume__d_code : check last reply21:35
d_codeguillaume__: good to know…but the values I put there are accurate?  I’m using port 4000 since I can’t install keystone if the registry is on 500021:35
d_codeI’m doing the watch command…so far just centos21:35
guillaume__ normaly yeah, check if your find for all port with kolla-ansible prechecks21:35
guillaume__where are you in the build ?21:36
guillaume__which steps21:36
d_codeINFO:kolla.cmd.build:mongodb21:37
guillaume__means that alot of the images have failed to load21:38
guillaume__have you disable https from the registry ?21:38
elemoine_d_code: indeed, I use cleanup-containers a lot during development21:39
d_codeI disabled https21:39
d_codewait…so…if I’m on the master branch21:40
d_codebut I set tag “liberty-rc1”21:40
d_codeshould I be running docker 1.8.2 or 1.10?21:40
haplo37What mean shared on starting neutron-dhcp-agent : /run/netns/:/run/netns/:shared. Because when i try to start the container, i have this issue : Path /run/netns is mounted on /run but it is not a shared mount.21:40
sdakeback folks21:40
sdakeguillaume__ i see you found the conf file, apologies for saying i'd find for you and didn't - got distracted by house emergency21:41
sdaked_code please don't use liberty-rc121:42
sdaked_code liberty runs on 1.8.2 only, master runs on 1.10.0 only21:42
sdake(and later)21:43
sdakewe are fixing liberty/stble so it will run with more modern versions of docker21:43
rhalliseyhaplo37, can you paste the error?21:43
sdakehaplo37 are you trying to make your own container?  Kolla should set up the shared mount points for you21:43
d_codesdake: alright…  I just want a build to succeed so that I can start playing with the API and such21:44
rhalliseysdake, d_code is on master21:44
sdakeliberty-rc1 is a release candidate21:44
d_codewhat should I set https://gist.github.com/dcode/aea450c1648034067637#file-etc-kolla-globals-yml-L70 to?21:44
rhalliseyd_code, tag name is arbirtraty21:44
haplo37i do kolla-build --base ubuntu --tag 1.0.0 -t binary21:44
d_codeokay…that’s what I thought rhallisey21:45
rhalliseyd_code, your on master so run lastest docker, which is 1.1021:45
haplo37and next do i kolla-ansible deploy21:45
d_coderhallisey: thanks21:45
rhalliseyd_code, sure thing21:45
d_codehaplo37: yeah….  I can’t run ubuntu as my base21:45
sdakehaplo are you o nteh stable/liberty branch or master branch?21:45
haplo37i am on master branch21:45
sdakethe tag for master is 2.0.0 ;)21:45
sdakeor possibly latest21:46
sdakeso just leave the --tag option out21:46
d_codesdake: so I set “openstack_release” to 2.0.0 ?21:46
rhalliseyhaplo37, so ansible is returning that? Can you paste it for us to see21:46
sdakeyou can change the tag that kolla deploys in globals.yml21:46
haplo37I have this error : msg: APIError(HTTPError(u'500 Server Error: Internal Server Error for url: http+docker://localunixsocket/v1.22/containers/neutron_dhcp_agent/start',),21:46
sdaked_code either that is the default or "latest" is the default I dont recall21:46
sdakehaplo37 you have an old version of docker-py or docker-engine21:46
haplo37ok so the tag is not for the version of openstack ?21:47
sdakethe instructions contain the minimum versions required21:47
sdakethe tag is for the version of kolla21:47
haplo37i use docker 1.10.021:47
rhalliseyhaplo37, what docker-py do you have?21:47
sdake1.0.0=liberty, 2.0.0 = mitaka21:47
sdakepip show docker-py21:47
sdakeor whatever its called in ubuntu :)21:47
haplo371.7.021:47
haplo37for docker-py21:48
sdakehaplo how long ago did you pull your repo?21:49
sdakehaplo37 type the command docker --version and paste results21:50
d_codek…building using tag 2.0.0 from source on CentOS 7.2, docker 1.10, docker-py 1.7.021:50
rhalliseyhaplo37, so you saw the API error from ansible, where were you seeing the other issue involving 'Path /run/netns is mounted on /run but it is not a shared mount.21:50
d_codeon git master pulled 30 minutes ago21:50
rhalliseyd_code, good stuff21:50
guillaume__taf 2.0.0 is for mitaka d_code, for liberty its 1.0.021:51
haplo37the last commit for my repo is commit 571f4b97f62142e2d18438631548e2ae10d9044e. I installed it a few hour ago.21:51
rhalliseyguillaume__, ya we recommend you use master at the moment21:51
d_coderight…sdake threatened me if I used 1.0.0 :p21:51
rhalliseyhehe21:51
sdakei made no threats ?21:51
d_codejust kidding, man21:51
sdakeok21:51
d_codeI was strongly encouraged to use 2.0.021:52
guillaume__rhallisey, our compagny (haplo and me) want us to install kolla for liberty and not for mitaka21:52
haplo37# docker --version Docker version 1.10.0, build 590d510821:52
rhalliseyguillaume__, gotcha.  Kolla needs to do a critial backport before we recommend you do that21:52
sdakehaplo37 i explained this earlier and wont repeat myself in irc justyet21:52
d_codesdake: do you expect the kolla release to line up with Mitaka release of openstack?21:52
guillaume__ok I will told the boss the n^^21:52
d_codeApril-ish?21:52
sdakebut i'll find thte discussion in the logs if you like21:52
*** ayoung has quit IRC21:52
rhalliseyguillaume__, the work should be complete by the middle of next week is the estimate21:53
sdakeand i am making a patch to explain our plans in docs.openstack.org/developer/kolla/quickstart.rst21:53
d_codecool21:53
sdakerhallisey i dont reecall a date being mentioned21:53
rhalliseyI'm guessing based on what sam said21:53
sdakebut I think it will land in the next 2-3 weeks21:53
sdakeand stable will be stable21:53
sdakewe dont guess on schedules or commited dates21:53
sdakebecause when we don't deliver because we speculated, people get pissed ;)21:54
*** aginwala has quit IRC21:54
rhalliseyjust a estimate :)21:54
rhalliseyfair enough21:54
sdakethe dates we are committed to atm is mitaka-3 march 2-4th21:54
sdakei will get a commitment on the stable branch, but i can't get it without the proper peopela round21:54
sdakeand they are on pto21:54
*** thumpba has quit IRC21:54
d_codeis mitaka generally usable for development purposes? or are there gaping functionality holes?21:56
rhalliseykk21:56
sdakeour priorities are here: https://etherpad.openstack.org/p/kolla-mitaka-midcycle-priorities21:56
d_codeI’m just tinkering with deploying VMs on a couple distinct networks and such….I’m more concerned with a functional API21:56
sdakei would not deplloy in production until mitaka is released21:56
d_codefunctional-ish21:56
sdakebut for dev it should work like a champ21:56
sdakethe bug your running into, i am not certain of21:57
d_codeour “production” time target, which is still a “production prototype”…whatever that means…is like June21:57
sdakeif you want to deploy in production, use 1.1.0 (not yet tagged) for liberty, use 2.0.0 for mitaka (not yet tagged)21:57
*** aginwala has joined #kolla21:57
sdaked_code we are going to absolutely make june for 1.1.0 and 2.0.021:58
*** sdake has quit IRC21:58
d_code:)22:00
*** ayoung has joined #kolla22:00
*** sdake has joined #kolla22:01
sdakelaptop ran out of juice, back now22:01
d_codeshould I manually run oslo-config-generator ?  or does that happen with kolla-build?22:02
*** Serlex has joined #kolla22:02
sdakeif you want ot evaluate, ou can use either stable/liberty or mitaka22:02
sdakethere is likely a pip operation to do the job d_code22:02
d_codeI’ll roll with whatever I can get running, with a preference towards mitaka22:02
sdakewhat config  file are you after?22:02
sdaked_code use master then :)22:02
d_codewell…had a exception during build after memcached was pushed22:03
Serlex"ERROR:kolla.cmd.build:unable to ping registry endpoint https://10.0.3.15:4000/v0/" any ideas what I'm doing wrong? its a bare-metal singlenode setup22:03
sdakeare you pushing to a registry?22:03
d_codeyes….local registry on port 400022:03
sdakeyes you need to specify --insecure-registry=10.0.3.15:4000 in the docker command line22:03
sdakethis goes in teh systemd file22:04
d_codeyup22:04
sdakeserlex ^^22:04
d_codefrom ps -ef -> /usr/bin/docker daemon -H fd:// --insecure-registry 192.168.4.210:400022:04
sdaked_code you had an exception with that with master during push?22:04
Serlexhaha22:04
Serlexare we asking the same question?22:04
sdakeserlex not sure22:05
d_codelol…no22:05
d_codeProtocolError: ('Connection broken: IncompleteRead(0 bytes read)', IncompleteRead(0 bytes read))22:05
d_codeI had a python exception22:05
d_codein urllib322:05
Serlex"--insecure-registry 10.0.3.15:4000 --push" is what i should run?22:05
Serlexwait --insecure-registry isn't a flag lol22:06
d_codeSerlex: that goes into your docker daemon in systemd22:07
Serlexyep ok22:07
*** aginwala_ has joined #kolla22:10
*** aginwala has quit IRC22:10
*** iNeilus has joined #kolla22:11
*** opennode has joined #kolla22:13
sdakeserlinux no22:14
sdake--insecure-registry is a docker option22:14
sdakethis is all documented in the instructions ;)22:14
sdakehttp://docs.openstack.org/developer/kolla/22:15
sdakeDeploy a registry (required for multinode)¶22:15
sdakein the quickstart guide22:15
sdakeit shows which commands to use and how to use them to get it rolling22:15
*** iNeilus has quit IRC22:16
Serlexcheers dude22:19
*** dwalsh has quit IRC22:19
SerlexI'm trying to get bare-metal kolla to work22:19
Serlexgot another error after supplying insecure-registry22:20
SerlexProtocolError: ('Connection broken: IncompleteRead(0 bytes read)', IncompleteRead(0 bytes read))22:20
sdakedocker 1.10?22:21
Serlexye22:21
sdakehow are you running the registry?22:21
*** bmace has quit IRC22:21
sdakethere are a couple different ways documented22:21
sdakeand the docs need to be updated22:21
Serlexroot     10177 31.5  0.5 498340 43384 ?        Ssl  22:20   0:12 /usr/bin/docker daemon -H fd:// --insecure-registry 10.0.3.15:400022:21
*** bmace has joined #kolla22:21
sdakeno, I mean the registry software not the docker daemon22:21
sdakethat part looks correct serlex22:22
sdakedocker 1.10 is incompatible with docker registry v122:22
sdakefortunately docker registry v2 has fixed the performance issues22:22
Serlexoh is it, i'm sure I setup v122:22
sdakethat is why you are receiving hat error22:22
Serlexbut is the error actually because of that22:22
sdakei'll get someone to fix the docs tomorrrow22:22
Serlexok22:22
sdakebut for now22:22
sdakelets get you running docker registry 2.3.022:22
Serlexhit me22:23
*** dims has quit IRC22:23
sdakesudo yum remove docker-registry22:23
sdakedocker run -d -p 4000:5000 --restart=always --name registry registry:2.3.0 (I think)22:23
sdakeor maybe its just 2.322:23
Serlexok tryhing22:24
Serlexdocs says registry:222:24
*** dims has joined #kolla22:26
SerlexCONTAINER ID        IMAGE               COMMAND                  CREATED             STATUS                        PORTS                    NAMES22:27
Serlexd7372e9814b4        registry:2.3        "/bin/registry /etc/d"   2 minutes ago       Up 53 seconds                 0.0.0.0:4000->5000/tcp   registry22:27
*** fthiagogv has quit IRC22:31
sdakeserlex 2.3 performs well, 2 does not22:32
sdakeyou will want to stab your eyeballs with 2.0 :)22:32
guillaume__that's probably why I never make it work with registry:2 ^^ Always having an error ^^ I finnaly choose to not push it to my own registry hahaha22:33
sdakeserlex now do tools.py --registry IP:4000 --push22:34
sdakewhere IP was your machine's registry ip address that you specified in --insecure-registry to the docker daemon22:34
*** mfalatic has quit IRC22:34
sdakeserlex any questions? :)22:35
SerlexI did kolla-build22:36
sdakewith --registry and --push?22:36
Serlexyep22:36
sdakewhat happened22:36
SerlexStill going22:36
Serlexno errors yet22:36
sdakeit should take about 14 minutes and push the containers22:36
Serlexso looks good22:36
sdakeoh22:36
sdakei thought you meant pasat tense :)22:36
Serlexno its still going22:37
sdakegot it22:37
sdakei need to make a phone call, brb22:37
*** ayoung has quit IRC22:37
SerlexI wouldn't bother wasting your time upgrading the docs, I seemt o be only one trying them :D. I was tearing my hair out with vagrant doc yesterday22:37
SerlexI will just ping here :p22:37
sdakeserlex no docs need to be fantastic22:37
sdakevagrant docs are less fantastic22:37
sdakeif the docs are good, you can self serve :)22:38
SerlexI think someone should determine what is best for the kolla project. Maybe time can be used more wisely somewhere else...22:39
d_code Serlex I’m with you on trying the docs22:40
*** jtriley has quit IRC22:40
sdakeserlex i dont understand what you mean22:40
SerlexI'm not what the best approach to testing kolla, if vagrant or bare-metal are favoured, then sure, docs should be well presented22:40
SerlexI'm not sure*22:40
sdakeserlex the community determiens what is best for the kolla project22:41
d_codeSerlex: thing is, if the docs are solid, you can run it in vagrant or on bare-metal22:42
d_codebeing able to reproduce positive results is ideal22:42
*** salv-orlando has joined #kolla22:42
d_code(I’m still working on that)22:42
SerlexMy goal was to test it in the quickest and easiest way possible...like devstack I guess...which is very popular with beginners22:42
SerlexIf I wanted to test it properly then I would invest into actual servers and setup a proper environment with nodes22:44
*** iNeilus has joined #kolla22:44
*** salv-orl_ has quit IRC22:44
SerlexI thought --profile default suppose to help me out here, this build is still going :D22:45
*** opennode has quit IRC22:47
*** JoseMello has quit IRC22:48
*** iNeilus has quit IRC22:49
sdakeserlex we get setup questions about 10-15 times a day in the channel from new users22:50
sdakethe fact that the quickstart has incorrect documentation about the registry is a legitimate problem22:51
sdakeits only incorrect as of about 3 days ago22:51
sdakebut its still wrong and needs to be fixed22:51
Serlexok that makes sense22:52
sdakethe vagrant docs, I dont know what to tell you22:52
sdakeI dont use vagrant22:52
sdakeso I dont document it :)22:52
SerlexI still intend to get my vagrant working, I think I failed with the same missing insecure-registry flag22:53
*** sdake_ has joined #kolla22:54
sdake_bare metal with registry AIO is easiest way to evaluate kolla single node IMO22:54
sdake_but alot of folks use VMs22:55
sdake_or vagrant22:55
sdake_or whatever22:55
*** aginwala_ has quit IRC22:56
*** aginwala has joined #kolla22:56
*** sdake has quit IRC22:57
guillaume__sdake, I spoke with the boss ^^ We finaly will go directly to mitaka since the stable/liberty is broken for 1-2 week :P23:00
guillaume__I know that Mitaka is still in dev, is it still "stable" for trying to start some new production recepies?23:01
*** cloudna__ has joined #kolla23:14
*** cloudnau_ has quit IRC23:17
*** cloudna__ has quit IRC23:18
*** iNeilus has joined #kolla23:21
*** macsz has joined #kolla23:22
*** ayoung has joined #kolla23:25
*** macsz has quit IRC23:29
*** macsz has joined #kolla23:29
*** macsz has left #kolla23:30
*** blahRus has quit IRC23:31
*** Serlex has quit IRC23:49
*** ayoung has quit IRC23:50
*** guillaume__ has quit IRC23:51
*** haplo37 has quit IRC23:51
*** absubram has quit IRC23:57
*** iNeilus has quit IRC23:59

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