Thursday, 2016-02-25

*** Jeffrey4l has joined #kolla00:00
openstackgerritMartin AndrĂ© proposed openstack/kolla: Pin ceph-radosgw  https://review.openstack.org/28447500:03
mandresbezverk: ^ this will fix your build issue00:03
*** sdake has joined #kolla00:07
*** diogogmt has quit IRC00:10
*** blakec has joined #kolla00:18
*** sdake has quit IRC00:23
*** blakec has quit IRC00:46
*** kzaitsev_mb has quit IRC00:54
openstackgerritMerged openstack/kolla: Remove information about downgrading docker  https://review.openstack.org/28438400:59
*** iceyao has joined #kolla01:06
*** iceyao has quit IRC01:11
*** iceyao_ has joined #kolla01:11
*** iceyao has joined #kolla01:14
*** iceyao_ has quit IRC01:16
*** blakec has joined #kolla01:20
*** jasonsb has joined #kolla01:33
*** blakec has quit IRC01:34
*** blahRus has quit IRC01:34
*** tfukushima has joined #kolla01:44
*** Liuqing has joined #kolla01:51
*** dims has quit IRC01:52
*** iceyao_ has joined #kolla02:01
*** iceyao has quit IRC02:03
*** diogogmt has joined #kolla02:05
*** rhallisey has quit IRC02:22
*** iceyao has joined #kolla02:37
*** iceyao_ has quit IRC02:41
*** tfukushima has quit IRC02:54
*** tfukushima has joined #kolla03:03
*** alger has joined #kolla03:08
openstackgerritJeffrey Zhang proposed openstack/kolla: Reconfigure keystone service  https://review.openstack.org/28138003:09
openstackgerritJeffrey Zhang proposed openstack/kolla: Add the default empty reconfigure.yml file to all roles  https://review.openstack.org/28355103:09
openstackgerritJeffrey Zhang proposed openstack/kolla: Import module rather than funciton in the set_configs.py file  https://review.openstack.org/28450703:09
openstackgerritAllen Gao proposed openstack/kolla: Move ironic-discoverd to ironic-inspector  https://review.openstack.org/28065503:14
*** yuanying has quit IRC03:16
openstackgerritAsha proposed openstack/kolla: Fixed a typo in quickstart.rst  https://review.openstack.org/28451103:18
*** alger has quit IRC03:19
openstackgerritJeffrey Zhang proposed openstack/kolla: Reconfigure keystone service  https://review.openstack.org/28138003:21
*** diogogmt has quit IRC03:23
*** diogogmt has joined #kolla03:26
*** salv-orlando has joined #kolla03:27
*** salv-orlando has quit IRC03:28
*** salv-orl_ has quit IRC03:30
*** alger has joined #kolla03:31
*** Liuqing has quit IRC03:37
*** Liuqing has joined #kolla03:38
*** diogogmt has quit IRC03:43
openstackgerritMatthew Montgomery proposed openstack/kolla: Quick spelling/grammar fix  https://review.openstack.org/28452203:55
*** mandre has quit IRC03:56
*** mandre has joined #kolla03:56
*** dtturner has joined #kolla04:07
*** yuanying has joined #kolla04:07
*** Liuqing has quit IRC04:21
*** Liuqing has joined #kolla04:22
*** salv-orlando has joined #kolla04:29
*** achanda has quit IRC04:35
*** salv-orlando has quit IRC04:39
*** Marga__ has joined #kolla04:40
*** Marga__ has quit IRC04:44
*** Marga_ has quit IRC04:44
*** iceyao has quit IRC04:47
*** iceyao_ has joined #kolla04:47
*** alisonh has quit IRC04:55
*** achanda has joined #kolla04:55
*** Marga_ has joined #kolla04:56
*** Marga_ has quit IRC05:00
*** Marga_ has joined #kolla05:01
*** Marga_ has quit IRC05:01
*** Marga_ has joined #kolla05:01
*** Marga_ has quit IRC05:02
*** Marga_ has joined #kolla05:02
*** Liuqing has quit IRC05:08
*** Liuqing has joined #kolla05:08
*** alisonh has joined #kolla05:13
*** sdake has joined #kolla05:17
*** sdake has quit IRC05:22
*** alisonh has quit IRC05:32
*** alisonh has joined #kolla05:37
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Add explicit calls to extend_start and skip the default  https://review.openstack.org/28335605:39
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Fix the running of apache based services  https://review.openstack.org/28397205:39
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Move nova bootstrap into nova-api  https://review.openstack.org/28397105:39
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: start.py: catch NoNodeError on delete  https://review.openstack.org/28454305:39
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Add /var/log/kolla volume to koll_toolbox  https://review.openstack.org/28454405:39
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Add missing ENV to neutron-linubridge-agent  https://review.openstack.org/28454505:39
*** chandankumar has joined #kolla05:47
*** yuanying has quit IRC05:47
*** dims has joined #kolla05:52
*** salv-orlando has joined #kolla05:58
*** salv-orlando has quit IRC06:03
*** mbound has joined #kolla06:30
*** mbound has quit IRC06:34
*** dims has quit IRC06:43
*** achanda_ has joined #kolla06:45
*** dave-mccowan has quit IRC06:45
*** achanda has quit IRC06:46
*** Liuqing has quit IRC06:53
*** yuanying has joined #kolla06:54
*** salv-orlando has joined #kolla07:02
*** jasonsb has quit IRC07:02
*** salv-orlando has quit IRC07:07
*** alger has quit IRC07:11
*** salv-orlando has joined #kolla07:25
*** salv-orl_ has joined #kolla07:26
*** salv-orlando has quit IRC07:26
*** alger has joined #kolla07:28
*** tfukushima has quit IRC07:31
*** tfukushi_ has joined #kolla07:32
*** alger has quit IRC07:33
*** alger has joined #kolla07:35
*** mbound has joined #kolla07:43
*** daneyon_ has quit IRC07:55
*** jmccarthy1 has joined #kolla08:01
*** yuanying has quit IRC08:01
openstackgerritLin Cai proposed openstack/kolla: Fix hard coded keystone user for nova Edit  https://review.openstack.org/28457508:03
*** mbound has quit IRC08:04
*** fgimenez has joined #kolla08:06
*** fgimenez has joined #kolla08:06
*** jmccarthy1 has quit IRC08:08
*** yuanying has joined #kolla08:11
*** athomas has joined #kolla08:15
*** yuanying has quit IRC08:16
*** yuanying has joined #kolla08:18
*** alger has quit IRC08:19
*** britthouser has quit IRC08:21
*** jmccarthy1 has joined #kolla08:21
*** mikelk has joined #kolla08:23
*** yuanying has quit IRC08:26
*** yuanying has joined #kolla08:32
openstackgerritEric Lemoine proposed openstack/kolla: [WIP] Make Heka send logs to Elasticsearch  https://review.openstack.org/28418808:33
*** yuanying has quit IRC08:38
*** yuanying has joined #kolla08:41
*** kproskurin has joined #kolla08:43
*** alger has joined #kolla08:46
*** yuanying has quit IRC08:47
*** rtmie has joined #kolla08:48
*** tfukushi_ has quit IRC08:51
ajafoo/08:56
*** athomas has quit IRC08:59
*** achanda_ has quit IRC09:00
*** achanda has joined #kolla09:04
*** tfukushima has joined #kolla09:04
*** athomas has joined #kolla09:06
*** tfukushima has quit IRC09:09
*** tfukushima has joined #kolla09:11
*** achanda has quit IRC09:19
*** achanda has joined #kolla09:24
*** salv-orlando has joined #kolla09:27
*** achanda has quit IRC09:29
openstackgerritProskurin Kirill proposed openstack/kolla-mesos: Fix typo in dhcp-agent  https://review.openstack.org/28461009:30
*** salv-orl_ has quit IRC09:30
*** pbourke has quit IRC09:32
*** pbourke has joined #kolla09:32
openstackgerritwangtianfa proposed openstack/kolla: A hard-coded keystone username for neutron in the neutron.conf template. Changed to use the var.  https://review.openstack.org/28461209:33
*** alger has quit IRC09:35
elemoine_o/09:35
*** prithiv has joined #kolla09:42
*** salv-orlando has quit IRC09:43
*** gfidente has joined #kolla09:57
*** gfidente has joined #kolla09:57
jmccarthy1Morning !09:57
*** chandankumar has quit IRC09:58
*** kzaitsev_mb has joined #kolla10:14
*** tfukushima has quit IRC10:17
*** achanda has joined #kolla10:29
*** achanda has quit IRC10:35
jmccarthy1Question about multiple networks, I'm sure it's been discussed at some point - what is the status ? i.e. multiple neutron_bridge_names and related ?10:39
*** bmace has quit IRC10:40
*** bmace has joined #kolla10:41
*** kzaitsev_mb has quit IRC10:47
*** kzaitsev_mb has joined #kolla10:54
*** iceyao_ has quit IRC10:56
*** sdake has joined #kolla10:58
*** salv-orlando has joined #kolla10:59
*** salv-orlando has quit IRC10:59
*** macsz has joined #kolla10:59
*** salv-orlando has joined #kolla10:59
*** slotti has joined #kolla11:00
*** macsz has quit IRC11:07
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Require nova-libvirt in nova-compute  https://review.openstack.org/28464211:09
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: [WIP] Customize number of instances  https://review.openstack.org/28464311:09
*** chandankumar has joined #kolla11:09
*** chandankumar has quit IRC11:11
*** chandankumar has joined #kolla11:11
*** britthouser has joined #kolla11:13
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Add explicit calls to extend_start and skip the default  https://review.openstack.org/28335611:14
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Add missing ENV to neutron-linubridge-agent  https://review.openstack.org/28454511:14
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: start.py: catch NoNodeError on delete  https://review.openstack.org/28454311:14
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Fix the running of apache based services  https://review.openstack.org/28397211:14
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Move nova bootstrap into nova-api  https://review.openstack.org/28397111:14
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Add ANSIBLE_NOCOLOR to chronos job  https://review.openstack.org/28464811:14
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Customize number of instances  https://review.openstack.org/28464311:21
sdakeyo11:22
openstackgerritEric Lemoine proposed openstack/kolla: [WIP] Make Heka send logs to Elasticsearch  https://review.openstack.org/28418811:25
*** sdake_ has joined #kolla11:29
*** sdake has quit IRC11:30
openstackgerritEric Lemoine proposed openstack/kolla: [WIP] Make Heka send logs to Elasticsearch  https://review.openstack.org/28418811:31
*** sdake_ has quit IRC11:37
openstackgerritAngus Salkeld proposed openstack/kolla-mesos: Restart daemons if their config changes  https://review.openstack.org/28466411:50
*** mdnadeem has quit IRC11:50
*** mdnadeem has joined #kolla11:51
openstackgerritRodolfo Alonso Hernandez proposed openstack/kolla: Adjust package name for Ubuntu Ironic  https://review.openstack.org/28467212:03
openstackgerritRodolfo Alonso Hernandez proposed openstack/kolla: Fix configuration files deployment in ironic-base project  https://review.openstack.org/28467312:03
*** Liuqing has joined #kolla12:03
*** prithiv has quit IRC12:06
*** fthiagogv has quit IRC12:10
*** fgimenez has quit IRC12:16
*** Liuqing has quit IRC12:16
*** iceyao has joined #kolla12:18
*** fgimenez has joined #kolla12:20
*** fgimenez has quit IRC12:20
*** fgimenez has joined #kolla12:20
*** rhallisey has joined #kolla12:32
*** achanda has joined #kolla12:33
*** achanda has quit IRC12:40
*** prithiv has joined #kolla12:46
*** dwalsh has joined #kolla12:46
*** diogogmt has joined #kolla12:46
*** prithiv has quit IRC12:51
*** prithiv has joined #kolla12:53
*** fthiagogv has joined #kolla12:53
*** salv-orlando has quit IRC12:56
*** dave-mccowan has joined #kolla12:56
*** prithiv has quit IRC12:57
ccesarioHello.... is there any document about design structure with when using kolla ?!12:57
rhalliseyccesario, what do you mean by design structure?12:58
rhalliseyfor a deployment?12:59
limamauriciohello guys, anyone else have this error when  run the build on ubuntu? http://pastebin.com/e6uLuGdW12:59
*** prithiv has joined #kolla12:59
ccesariorhallisey, yes ... a deployment for a production environment ....13:01
rhalliseyccesario, we only really have the quickstart so far.  This will be under advanced-configuration when we fill it out13:03
rhalliseyit just hasn't been yet https://github.com/openstack/kolla/blob/master/doc/advanced-configuration.rst13:04
sbezverkHello, Adding 1:ceph-radosgw-0.94.5-0.el7.centos.* into versionlock.list did not help building ceph containers is still failing, how do I activate the new version lock list?13:07
*** diogogmt has quit IRC13:10
ccesariorhallisey, ahh ok.... thanks by info....  I 'm asking because I 'm  thinking in usage kolla in a new project to be developed... kolla it seems a best tool to deployment and maintenance.13:16
ccesariolimamauricio, are you building using  "binary"  mode ?  kolla_install_type13:17
limamauriciosource13:18
rhalliseyccesario, sure I think it's a great fit.  I think the best way for you to proceed is to get a feel for it and ask in channel for any advanced deployment questions you might have13:18
rhalliseyand we will get to the docs eventually13:18
limamauriciosource ccesario13:20
ccesariorhallisey, yes yes... I already did some tests using all in one deployment...... now I 'm looking for by advanced docs, as HA by example.... and the best way to usage the hardware and do not spent resources as physical deployments.... if you understand me...13:23
rhalliseyyes13:24
rhalliseywoops.. thought I was in terminal13:25
rhalliseyccesario, ya I gotcha13:25
ccesariolimamauricio, look at... there are some comments and errors  like yours https://bugs.launchpad.net/kolla/+bug/1500245/13:26
openstackLaunchpad bug 1500245 in kolla "Consistently Failing - Deploy OpenStack all in one node using Ansible" [Wishlist,Triaged] - Assigned to Manoj (manoj-kumar-jainman)13:26
ccesariorhallisey, :)13:27
rhalliseyccesario, SamYaple is probably you best bet for some of advice.  He dev environment likely has a lot of what your looking for13:28
ccesariorhallisey,  is there planned any kind of kolla-ui  to control how and where OpenStack services are deployed across the datacenter ....!?13:29
ccesariorhallisey, thanks by info :)13:30
rhalliseyccesario, I think someone came along and was looking at it.. Right now we're trying to nail down upgrades so it hasn't been our primary focus13:31
ccesarionice  to know....  yes yes, I read several articles about kolla where "upgrade" it was one excellent feature...13:35
ccesarioatomic upgrades :)13:35
*** achanda has joined #kolla13:37
*** achanda has quit IRC13:41
*** dims has joined #kolla13:47
openstackgerritAsha proposed openstack/kolla: Fixed a typo in quickstart.rst  https://review.openstack.org/28451113:55
*** JoseMello has joined #kolla13:55
openstackgerritAsha proposed openstack/kolla: Fixed a typo in quickstart.rst  https://review.openstack.org/28451113:56
*** salv-orlando has joined #kolla13:58
*** salv-orlando has quit IRC14:03
*** fgimenez has quit IRC14:07
*** slotti has quit IRC14:08
*** fgimenez has joined #kolla14:09
openstackgerritVikram Hosakote proposed openstack/kolla: Add timeout to requests.get() in kolla/cmd/build.py  https://review.openstack.org/28384414:10
sbezverkHow do you build heka container? it seems kolla-ansible build, does not do it automatically... Now when I run deployment it fails with The requested image does not exist: 192.168.80.240:4000/kollaglue/centos-source-heka:2.0.014:11
openstackgerritAbe Music proposed openstack/kolla: General improvements to quickstart  https://review.openstack.org/28430514:12
elemoine_sbezverk: how did you build the other containers?  the heka container has nothing special, it is build like any other containers14:17
sbezverkelemoine_ I used this command to build all other containers: kolla-build --type source --base centos --registry 192.168.80.240:4000 --push14:22
sbezverkbut then I tried to use this: kolla-build --type source --base centos --registry 192.168.80.240:4000 --push regex heka and it created this container14:23
elemoine_sbezverk: that should have built the heka container14:23
elemoine_sbezverk: unless there's a bug14:24
*** mikelk has quit IRC14:25
*** vhosakot has joined #kolla14:25
sbezverkelemoine_ another issue during deployment, VIP is not comming up, here is logs collected from keepalive container http://paste.openstack.org/show/488188/, could you please check?14:28
elemoine_sbezverk: might be related to the previous deploy error14:28
elemoine_sbezverk: you can do tools/cleanup-containers to clean things up, and then redeploy the whole thing14:29
elemoine_sbezverk: can you confirm that a simple kolla-build (with no regex) does not build the heka container?14:30
sbezverkelemoine_ the thing is I use VM with kolla to deploy all-in-one on another baremetal server, so there is no tools/cleanup-containers available on a baremetal box..14:31
sbezverkelemoine_ I usually just delete everything under /var/lib/docker/*14:31
elemoine_sbezverk: you can copy the cleanu-containers script on the target host and run it there14:32
sbezverkelemoine_ if it does not have any dependecies like ansible or something which is not part of a minimla OS image then yes..14:32
*** Jeffrey4l has quit IRC14:33
*** jtriley has joined #kolla14:33
elemoine_sbezverk: I think it's a standalone script, so copying should work14:33
*** chandankumar has quit IRC14:33
*** vhosakot has quit IRC14:34
*** mikelk has joined #kolla14:35
sbezverkelemoine_ will do that in a few minutes, but check this "Waiting for virtual IP to appear" on my deployment VM, but baremetal box has VIP up and listening: tcp        0      0 192.168.80.205:3306     0.0.0.0:*               LISTEN      9640/haproxy14:35
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Support dependencies inside one host  https://review.openstack.org/28473714:35
elemoine_sbezverk: hmm14:36
sbezverkelemoine_ and deployment still is waiting..14:37
elemoine_sbezverk: have you done the cleanup already?14:37
elemoine_sbezverk: just for me to know…14:38
sbezverkelemoine_ waiting for it to fail and then will do clean up14:38
elemoine_ok14:38
*** signed8bit has joined #kolla14:38
elemoine_is kolla_internal_address correct in your globals.yml file?14:39
elemoine_sbezverk: that should be your vip , and it should be available from your deploy box14:40
elemoine_sbezverk: also do you use two vips?  in other words, did you set kolla_external_address as well?14:41
sbezverkelemoine_ after clean up, the same thing.. collected proof for you: http://paste.openstack.org/show/488194/14:43
elemoine_sbezverk: I trust you14:43
elemoine_sbezverk: see my other comments14:43
sbezverkelemoine_ I use kolla_internal_address: "192.168.80.205" and I also use: kolla_external_address: "192.168.80.25" external address is the one used to access openstack..14:46
*** Jeffrey4l has joined #kolla14:47
sbezverkand it is bound to my management interface..14:48
elemoine_can you edit ansible/roles/haproxy/tasks/start.yml and replace kolla_internal_address by kolla_external_address in the "Waiting for virtual IP to appear" task/block?14:51
elemoine_sbezverk: I am not sure that's the problem but it might be14:51
sbezverkelemoine_ hm it does not make sense, I mean changing it as internal address will be used to bind mariadb..14:54
sbezverkelemoine_ do you know how deploy check for port up condition?14:54
elemoine_sbezverk: see ansible/roles/haproxy/tasks/start.yml14:57
elemoine_sbezverk: the Ansible wait_for module is used in there14:58
*** diogogmt has joined #kolla14:59
elemoine_sbezverk: is your deploy node able to ping the internal vip (192.168.80.205)?14:59
sbezverkelemoine_ no I cannot ping, but I am not sure if haproxy offers this functionality..15:03
elemoine_sbezverk: and can you ping the external vip? (192.168.80.25)15:04
elemoine_sbezverk: if you cannot ping the vip the wait_for task cannot do its job15:04
sbezverkI can ping 80.25. Well you cannot really rely on ping when you wait for a specifc TCP port?!?!?15:05
*** chandankumar has joined #kolla15:05
elemoine_sbezverk: not what I am saying15:06
elemoine_sbezverk: but if ping does not work then wait_for will probably do not work either15:06
elemoine_sbezverk: did you try to change the wait_for host from internal_address to external_address as I suggested?15:07
*** salv-orlando has joined #kolla15:08
*** stvnoyes has quit IRC15:08
*** stvnoyes has joined #kolla15:09
sbezverkelemoine_ no, but it does not make sense as internal address is used to bind mariadb, anyway I will try..15:09
openstackgerritMerged openstack/kolla: Quick spelling/grammar fix  https://review.openstack.org/28452215:10
sbezverkelemoine_ I understand what you mean though15:10
elemoine_sbezverk: I don't understand your comment15:10
elemoine_sbezverk: I don't understand why it doesn't make sense to you15:10
sbezverkelemoine_ never mind, you need a pingable address15:11
elemoine_sbezverk: this wait_for thing is just to stop the deploy process until the haproxy is available, but this step will not work if your deploy does not have access to the wait_for host15:12
sbezverkelemoine_ changed, still the sme thing15:13
elemoine_on the target host can you confirm with netstat -nlp that there is a process bound/listening to <kolla_external_address>:<mariadb_port>?15:15
*** salv-orlando has quit IRC15:15
sbezverknetstat -tunlp | grep 330615:15
sbezverktcp        0      0 192.168.80.205:3306     0.0.0.0:*               LISTEN      23176/haproxy15:15
elemoine_no entry for the external_address?15:16
sbezverkelemoine_ no15:16
elemoine_strange isn't it?15:16
*** inc0 has joined #kolla15:17
sbezverkelemoine_ funny thing is 4 days ago exactly the same deployment wokred like a charm..15:18
elemoine_sbezverk: external_address is new, right?15:18
sbezverkelemoine_ the only thing changed was version of kolla, I cloned new version this morning..15:19
sbezverkelemoine_ not sure I follow, what do you mean new?15:19
elemoine_https://github.com/openstack/kolla/commit/34c2cb8e64c4758ec9e834dc3fabc9f5835fe9ac15:20
elemoine_sbezverk: I am pretty sure this the commit that affects you15:21
rhalliseySamYaple, for multinode, do you set control0, 1, 2 addresses in /etc/ansible/hosts ?15:21
openstackgerritMerged openstack/kolla: Fixed a typo in quickstart.rst  https://review.openstack.org/28451115:21
inc0holla15:22
*** blahRus has joined #kolla15:22
elemoine_sbezverk: so haproxy is bound to 192.168.80.205:3306 (based on netstat)15:23
sbezverkelemoine_ correct and this is VIP (internal)15:24
sbezverkelemoine_ the issue here is for 80.205 haproxy does not do arp reply..15:25
elemoine_sbezverk: ok, so I don't know right now15:25
elemoine_I thought that wait_for was executed on your deploy machine, but I now think that I may be wrong15:26
sbezverkelemoine_ what ever outside of bare metal host will not be able to communicate until something starts sending arp replies15:26
sbezverkfor this VIP address15:26
rhalliseyyo yo15:26
*** asalkeld has quit IRC15:27
*** asalkeld has joined #kolla15:27
elemoine_sbezverk: I'd suggest creating a kolla bug explaining your problem15:27
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Support dependencies inside one host  https://review.openstack.org/28473715:27
sbezverkelemoine_ sure, will do, thank you for your help..15:27
elemoine_sbezverk: you can also try to discuss your problem w/ someone else on the channel15:28
elemoine_sbezverk: in any way i'm interested to know what the problem when you get the answer15:29
*** Jeffrey4l has quit IRC15:31
*** iceyao_ has joined #kolla15:31
*** iceyao has quit IRC15:32
sbezverkelemoine_ I will let you know for sure.. and I just filed a new bug to track this issue..15:33
elemoine_sbezverk: thanks15:33
*** prithiv has quit IRC15:34
*** sdake has joined #kolla15:37
inc0SamYaple, around?15:37
inc0I see strange behaviour. Outside docker networking works great, from inside container even requesting keys from apt takes minutes15:37
inc0ubuntu 15.10 with ubuntu kolla15:37
inc0anyone saw anything like that15:38
inc0?15:38
*** iceyao_ has quit IRC15:38
inc0during build stage15:38
SamYapleinc0: yup15:39
inc0what's that?15:39
inc0it's horrible.15:39
*** achanda has joined #kolla15:39
SamYapleno i mean im around15:39
inc0ok15:39
inc0well then ^^15:39
SamYaplerhallisey: i do not set hosts like that15:39
inc0I just spawned 3 brand new vms15:39
SamYapleany slowness ive seen on that has been 1 of two things15:40
SamYapleslow disk, bad firewall15:40
nihiliferor bad storage backend for docker, but i'm not sure that's exactly that15:41
*** sdake_ has joined #kolla15:41
SamYaplenihilifer: what do yo umean "bad storage"?15:41
inc0with net-host it's just fine15:42
inc0can you run build over net-host?15:42
*** sdake has quit IRC15:42
SamYaplebuild doesnt use --net=host15:42
inc0I'm running aufs, it should be good15:42
SamYapleit uses docker proxy15:42
inc0I know, I'm asking if you can;) seems like docker proxy issue15:43
inc0maybe just too slow vm15:43
SamYapleoh no you cant15:43
nihiliferSamYaple: i mean aufs - it doesn't always work well on ubuntu. but well, we can be sure now that's not causing inc0's problem15:43
SamYapleare you using apt-key? or like a python library?15:43
SamYaplenihilifer: nah inc0 is using 15.10, thats teh 4.2 kernel15:43
SamYapleit should be fine15:43
openstackgerritMerged openstack/kolla: Pin ceph-radosgw  https://review.openstack.org/28447515:44
inc0SamYaple, I'm running our build15:44
inc0so apt-key15:44
*** achanda has quit IRC15:45
SamYapleinc0: `docker run --rm -it ubuntu bash` then try the apt-key15:45
SamYaplethen llaunch one with --net=host15:45
inc0doing it, same stuff15:46
inc0with net host it's good15:46
inc0without it's dead slow15:46
SamYaplei blame your iptables rules then15:47
inc0top doesn't show anything strange, it doesn't seem to be CPU issue15:47
inc0nothing bad there, it's clean ubuntu 15.1015:47
sbezverkSamYaple should haproxy  send arp replies for VIP?15:50
inc0why haproxy?15:50
openstackgerritMerged openstack/kolla: Adjust package name for Ubuntu Ironic  https://review.openstack.org/28467215:50
*** jmccarthy has quit IRC15:51
*** jmccarthy has joined #kolla15:51
*** dtturner has quit IRC15:52
limamauricioSamYaple, Manila does not works without /run http://pastebin.com/w7Aw5WLS15:52
*** dtturner has joined #kolla15:52
SamYaplesbezverk: haproxy nor keepalived sends arp replies15:55
SamYaplethats the kernel15:55
SamYaplelimamauricio: ok, is that because of the openvswitch socket it needs to talk to?15:55
*** daneyon has joined #kolla15:56
*** daneyon_ has joined #kolla15:57
*** sdake has joined #kolla15:57
*** sdake_ has quit IRC15:58
limamauricioI think so, theoretically should not be necessary add the /run, but it is needed.15:58
SamYaple"i think so" isnt really a good answer here, can you figure out exactly what it needs please?15:58
*** jasonsb has joined #kolla15:59
*** daneyon has quit IRC16:00
limamauricioit needs just /run16:01
SamYaplewhy though?16:01
sbezverkSamYaple the reason I asked about ARP, is that I hit an issue during deploy, deploy script gets stuck waiting for VIP, but on the target host I do see VIP and port is up and in listen mode16:05
*** prithiv has joined #kolla16:05
*** dims has quit IRC16:06
limamauricioSamYaple, the /run is necessary for create this directory "/var/run/ openvswitch/" within manila containers16:07
SamYapleso keepalived will place a VIP in the form of x.x.x.x/32 on the api interface sbezverk16:07
limamauriciowithout /run I have this error "ERROR oslo_messaging.rpc.dispatcher Stderr: u'ovs-vsctl: unix: /var/run/openvswitch/db.sock: database connection failed (No such file or directory) '"16:07
SamYaplesbezverk you must also have another ip that has the vip in its subnet range on that same interface16:08
SamYapleotherwise you have to do other routing stuff16:08
SamYapleso, for example, vip is 192.168.10.254, you must have 192.168.10.10/24 on the same interface16:08
*** diogogmt has quit IRC16:08
limamauricioI not yet studied how openvswitch works in kolla, but the fact is that the manila needs this directory inside your container.16:08
SamYaplelimamauricio: currently openvswitch is part of the neutron role. thats the only place it deploys16:09
SamYaplewhere is manila meant to run?16:09
*** sdake_ has joined #kolla16:11
*** sdake_ has quit IRC16:11
*** daneyon_ has quit IRC16:11
*** sdake has quit IRC16:11
*** sdake_ has joined #kolla16:12
sdake_morning yet again16:12
*** jmccarthy1 has quit IRC16:13
sbezverkSamYaple that is exactly what I have my VIP is 192.168.80.205, my external interface is 192.168.80.25..16:13
*** spisarski has joined #kolla16:13
limamauricioall is running localhost16:16
limamauriciomy deployment is aio16:16
limamauriciomanila does not needs to deploy openvswitch16:17
SamYaplesbezverk: if you can't ping from node1 to node2 where node2 holds the vip, you likely have a networking issue16:18
SamYapleit could be caused by your configuration16:18
limamauricioit just needs use it16:18
SamYapleelemoine_: regression caused by https://github.com/openstack/kolla/commit/ede53b1dcbd475aa0dff339ee8dffaa9008247a916:20
SamYaplelimamauricio: using a socket means openvswitch must be deployed on the host manila is16:20
sbezverkSamYaple I can ping external address, what I cannot ping is VIP address, it is interesting, how you can say it is networking issue is this happens in the middle of a deployment process??  BTW here is what I see in logs of haproxy container: RRP_Instance(kolla_internal_vip) Now in FAULT state16:21
limamauricio Oh, so we're talking about the same thing.16:21
limamauricio:)16:21
elemoine_SamYaple: I was away, what's the problem?16:22
SamYapleelemoine_: im going to fix it16:22
SamYaplesimple mistake16:22
SamYaplenova_libvirt is not based on nova_base16:22
limamauricioSamYaple, we're talking about the same thing hahaha16:22
elemoine_SamYaple: oops16:22
SamYaplesbezverk: i can say its a networking issue because thats waht it is. does the vip exist on a node? thats all kolla can ensure16:23
SamYaplesbezverk: im happy to help you out here, but more info is needed16:23
inc0hmm..I found one thing that looks bad16:23
SamYaplelets start with `ip a` and `ip r`16:23
elemoine_SamYaple: indeed, I can fix it if you want16:23
SamYapleelemoine_: nah testing my patch now16:24
elemoine_SamYaple: sorry about that mistake16:24
SamYapleit didnt show in the gate because we dont use kvm in the gate elemoine_16:24
SamYapleits an understandable thing to miss16:24
limamauricioSamYaple, sorry, all this talk was just because I did not understand your question. : /16:24
inc0normal vm address is 172.16.24.58/22, docker created its network on 172.17.0.1/16...it should be exclusive but thing to consider16:24
SamYaplelimamauricio: its ok :)16:24
SamYaplelimamauricio: im not the best communicator over IRC apparently16:25
SamYapleinc0: im curious to see how you end that since those networks dont overlap...16:26
limamauricioI did not know that using a socket means openvswitch must be deployed on the host manila haha16:26
SamYapleyea openvswitch creates the socket16:26
limamauricioI learned something new today ^^16:26
inc0I know they don't, that's why I'm still looking16:26
inc0I tcpdumped docker0 and it seems ok16:26
inc0which would suggest something is doing stuff later16:27
inc0brb16:27
sbezverkSamYaple here is requested info: http://paste.openstack.org/show/488218/ VIP address does not exist, I suspect because VRRP_Instance(kolla_internal_vip) Now in FAULT state16:27
inc0or rather not doing stuff16:27
SamYaplesbezverk: thats a single node without a vip. i cant help you there16:28
*** kzaitsev_mb has quit IRC16:28
SamYaplesbezverk: its possible some upstream device is filtering multicast16:28
openstackgerritSam Yaple proposed openstack/kolla: nova-libvirt is not a child of nova-base  https://review.openstack.org/28479316:29
limamauricioSamYaple, my last patch is ok, if it is not necessary do a rebase. The pacth is ready16:30
limamauricio:)16:30
sbezverkSamYaple this testbed was used 4 days ago for exactly the same deployment which was successful, the only change is noew version of Kolla I cloned this morning.. No, there is nothing filtering multicast..16:30
*** inc0 has quit IRC16:31
*** vhosakot has joined #kolla16:31
SamYaplelimamauricio: what manila agent talks to openvswitch?16:31
*** inc0 has joined #kolla16:31
SamYaplesbezverk: mind you i have done a successful deployment on mutlinode (several times) this morning. so i doubt its the kolla code16:32
SamYaplemore likely its a configuration issue16:32
openstackgerritRodolfo Alonso Hernandez proposed openstack/kolla: Fix /etc files location for ironic-base building from sources  https://review.openstack.org/28479516:32
sdake_samyaple: [09:25:24]  <SamYaple>limamauricio: im not the best communicator over IRC apparently16:33
sdake_lol16:33
SamYaplei know exatly what im saying :/16:33
sdake_well fwiw, you are improving16:33
*** inc0 has quit IRC16:33
sdake_keep working at it :)16:33
sbezverkSamYaple Is there a way to see why VRRP went into a failed state? Maybe it cold give some clues what is wrong..16:33
*** inc0 has joined #kolla16:34
SamYaplei answer questions the way they are asked sdake_ . people should improve the asked quesstions16:34
sdake_SamYaple sometimes it takes multiple questsions to get at an answer16:36
rhalliseylol16:36
*** sdake_ is now known as sdake16:36
SamYaplehey people can i get a quick merge on https://review.openstack.org/#/c/284793/16:36
sdakeyou have improved your patience though when eople ask teh same question a different way :)16:36
SamYaplei just asnwer the same question in a different way :)16:37
SamYaplewithout new information my answer remains constant16:37
sdakeand sometimes that helps !16:37
sdakesometime it takes me 4 or 5 goes at someone to get a question answered ;)16:37
sdakeirc is really slow form of communication16:37
sdakeits like "fast group email16:38
sdake"16:38
sdakemy job would be impossible without irc16:38
*** salv-orlando has joined #kolla16:38
*** JoseMello has quit IRC16:38
vhosakotThanks for all the comments about the patch set to add timeout for requests.get() in build.py... I will add the unit test ti test the timeout! :)16:39
vhosakotIs there a sample ? I will refer test_build.py and the mock library16:39
*** JoseMello has joined #kolla16:41
*** salv-orlando has quit IRC16:41
*** chandankumar has quit IRC16:41
*** salv-orlando has joined #kolla16:41
rhalliseySamYaple, why would libvirt be the only service logging to /var/log/kolla16:42
rhalliseyas opposing to being under nova or libvirt16:42
SamYaplerhallisey: its not the only one16:43
*** absubram has joined #kolla16:43
sbezverkSamYaple, is there a way to change logging level for haproxy process?16:43
SamYaplethe only reason we have folders is for multiple logs16:43
SamYaplesbezverk: in the haproxy conf16:43
SamYaplerhallisey: libvirt only spits out libvirtd.conf16:43
rhalliseywhat other services log to /var/log/kolla .  I feel like we should have dirs regardless if there are multiple services or not16:45
sbezverkSamYaple is it a right file? /usr/share/kolla/ansible/roles/haproxy/templates/haproxy.cfg.j216:46
SamYaplerhallisey: how does that make sense? i mean there are lots of services that log to /var/log/ directly16:47
SamYaplesbezverk: yea16:47
rhalliseySamYaple, what openstack service does that?16:49
rhalliseykeystone mariadb log to /var/log/keystone/ and /var/log/mariadb16:50
rhalliseywith just a single log16:50
SamYaplelibvirt isn't an openstack service though16:50
SamYapleand honestly i dont like the fact its called nova_libvirt16:51
SamYaplethis isnt the first time weve had a bug due to this16:51
elemoine_SamYaple: that confused me16:51
rhalliseysalv-orlando, legacy naming16:51
rhalliseySamYaple,16:51
elemoine_SamYaple: the fact that it's called nova_libvirt16:51
SamYaplerhallisey: sure, but no reaason we have to keep it that way16:51
SamYapleit hurts nothing to change it16:51
salv-orlandorhallisey: np I'm legacy in many ways ;)16:51
rhalliseyI'm not arguing for it, but that's why it is16:51
SamYapleyea i know what, i dont like it16:52
rhalliseysalv-orlando, :D16:52
SamYaplelol16:52
rhalliseysalv-orlando, legendary naming16:52
rhalliseythere we go16:52
*** kzaitsev_mb has joined #kolla16:52
limamauricioSamYaple, manila does not have agents16:53
limamauricioopenvswitch connects manila-share service host to neutron networks16:53
limamauricioto be able to talk to service VMs16:53
*** dims has joined #kolla16:54
*** mikelk has quit IRC16:54
limamauricioand sdake, SamYaple people should improve the asked quesstions :)16:56
sdakelimamauricio its a two way street - a dance if you will16:56
sdakecommunication is hard - i've been at it 41 years and still struggle with younger folks ;)16:56
limamauriciohaha16:57
sdakelimamauricio  btw, rockstar job on manilla16:57
sdakelimamauricio  can you estimate the amount of time it took yo uto come up to speed on kolla?16:57
limamauriciosdake, you're right, communication is hard16:57
limamauricio I count the time I took to do ceph work? haha16:59
sdakei want to understand how long it took you to become familiar with the code enough to develop with it16:59
sdakenot the amount of time you spent getting your first deploy going16:59
limamauricio15 - 20 days17:02
limamauricioi'm not sure17:02
limamauriciosdake ^17:02
*** fgimenez has quit IRC17:03
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Customize number of instances  https://review.openstack.org/28464317:03
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Support dependencies inside one host  https://review.openstack.org/28473717:03
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Dependency between nova-libvirt and nova-compute inside host  https://review.openstack.org/28481517:03
*** fgimenez has joined #kolla17:03
sdakelimamauricio ok, so 80-160 hours?17:04
sdakeat what point in the hour curve did you feel confortable wiht the code base enough to feel like you knew whatyou were doing?17:05
openstackgerritMichal Rostecki proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968817:06
openstackgerritMichal Rostecki proposed openstack/kolla: Playbook for Manila upgrade  https://review.openstack.org/27804517:06
nihiliferummm.. sorry for that17:07
nihiliferi'll restore your patchset...17:07
limamauricio...17:08
sdakenihilifer what happened there?17:09
openstackgerritMichal Rostecki proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968817:10
limamauricionihilifer, no problem i do it :)17:10
nihiliferi had my patch about upgrading manila on top of that17:10
nihiliferand well, i just did "git review" after resolving my merge conflicts17:11
nihiliferwithout regarding limamauricio's changes17:11
nihilifersorry, patchset 17 should have your newest code limamauricio17:11
limamauriciosdake, 120-140 hours, i felt confortable with 60-70 hours17:12
sdakethanks lima17:13
sdakeso 120-140 hours is where you felt how?17:13
sdakecomfortable at 60-70 hours I heard17:13
sdakebut what was your feeling at the doubling of  that time?17:13
sbezverkSamYaple could you please check this error: http://paste.openstack.org/show/488228/17:13
sdakesbezverk did you do any customization with the number 80?17:14
*** prithiv has quit IRC17:16
sbezverksdake nope, I have not done any customization :-( All I did is to removed current kolla folder, cloned a new one and run pip install kolla/ --upgrade..17:16
sbezverksdake is it possible to have conflicts if docker containers were built with older version of kolla? example 4 days ago?17:18
*** rhallisey has quit IRC17:19
*** rhallisey has joined #kolla17:19
*** dwalsh has quit IRC17:20
openstackgerritMauricio Lima proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968817:21
limamauricionihilifer, i update my patch :)17:22
limamauricioupdated*17:22
limamauricio:)17:22
limamauricionow i saw that you had already restored ... my bad17:23
*** haplo37 has joined #kolla17:25
sdakesbezverk here is the feature slide in this deck: https://github.com/sdake/slides/tree/master/sdake-openstacksummit-kolla-2015-1017:29
sdakejust cut and paste that one if you like - its fairly accurate for mitaka as well17:31
sdakei will have more slides hitting  that repo this morning17:31
sdakeslide decks i mean17:32
*** sdake_ has joined #kolla17:34
limamauriciosdake, i think this bug is invalid https://bugs.launchpad.net/kolla/+bug/154473617:35
openstackLaunchpad bug 1544736 in kolla "Glance: Creating the Glance service and endpoint fails" [High,Triaged]17:35
*** achanda has joined #kolla17:36
*** sdake has quit IRC17:36
sdake_limamauricio I just triaged it, if its invalid add a comment17:37
limamauricioit use kolla_ansible17:38
sdake_the state is triaged means it is assigned a priority based upon the description of theproblem, and targeted to a release17:38
sdake_when it goes to confirmed, that means antoher person has confirmed it17:38
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Allow to override resources in global.yml  https://review.openstack.org/28483617:38
sdake_bugs should only be marked invalid if it is indeed invalid - otherwise, they should be marked not enough info17:39
limamauriciomake sense17:39
openstackgerritMichal Rostecki proposed openstack/kolla-mesos: Allow to override resources in globals.yml  https://review.openstack.org/28483617:39
limamauriciosdake, i believe it is invalid because it still use kolla_ansible, the right would use kolla_toolbox17:40
limamauriciosdake_ ^17:41
*** jasonsb has quit IRC17:41
sdake_limamauricio oh so you think it needs a retest on master?17:41
sdake_limamauricio  anyone can add comments to bugs, and comments are highly welcomed :)17:42
limamauriciosdake_, no need to test, it does not happen on the master.17:43
limamauricioi'll comment there17:43
sdake_thanks17:44
sdake_ask him to retest on masster as we think we have fixed that bug ;)17:44
sdake_thats the go to I use ;)17:44
SamYaplesdake_: you have to stop moving al the bugs forward to the next point17:44
SamYapleyou dont give them long enough to timeout when makes "needs more info"17:44
SamYapleitsl ike a 60 day timeout before they autoclose17:44
sdake_I can not move the bugs that are in invalid state17:45
sdake_but otherwise the bugs need to move17:45
SamYapleyou can...17:45
SamYapleand you do17:45
sdake_they only autoclose in the invalid state17:45
SamYapleyou are wrong17:45
SamYaplethe close in imcomplete17:46
SamYapleinvalid _is_ clsoed17:46
sdake_right17:46
sdake_incomplete17:46
sdake_ya mispoke apologies17:46
sdake_i can not move the incomplete bugs to the next release17:46
sdake_as in, will not17:46
sdake_that way they time out17:46
sdake_or are provided additional information if you like17:46
*** sdake_ is now known as sdake17:46
SamYapleyou do...17:46
SamYaplehttps://bugs.launchpad.net/kolla/+bug/150085817:46
openstackLaunchpad bug 1500858 in kolla "Config changes do not cause a container restart when using COPY_ALWAYS" [Wishlist,Incomplete]17:46
sdakeyes I have been17:47
sdakebut I can cease doing so17:47
sdakethe rest of the bugs need to be moved forward17:47
SamYapleyea thats what i was asking17:47
sdakesure that is no problem17:47
*** dwalsh has joined #kolla17:47
sdakeif bugs are in incomplete state i wont move them forward in teh future17:47
SamYaplethe rest i get17:47
SamYaplethough i disagree with them all being targeted somewhere17:47
SamYaplethey should only be targeted if we are going to fix them17:48
SamYapleas in actively going to fix them17:48
sdakethe downsie of that is they don't show up in the tracker list of bugs17:48
sdakethey show up in the full bug list17:48
SamYapletracker is what we are goign to finish17:48
sdakebut they get lost17:48
SamYaplethe fulll bug list is what we should be going by17:48
sdakei've moved bugs forward for oh, 2 years now ;)17:49
limamauricioSamYaple, manila does not have agents, openvswitch connects manila-share service host to neutron networks to be able to talk to service VMs17:49
SamYaplei know...17:49
SamYaplelimamauricio: manila-share servie runs where?17:49
sdakeif they dont get targeted, then nobody sees them and can know what to work on17:49
SamYaplethats not true17:49
SamYaplei never use that list17:49
SamYapleits not always valid17:49
SamYaplestuff falls through the crask17:50
SamYapleyou should never trust that list17:50
SamYaplethat list is for "we are doing these"17:50
sdakeit wouldn't fall through the cracks if people targeted it properly17:50
limamauricioin the host SamTaple17:50
limamauricioSamYaple :)17:50
SamYaplesdake: thats not doing it correctly....17:50
SamYapleno other group follows that practice just fyi17:50
sdakeSamYaple we can have a further discussion about how to manage bug triage, but what we have been doing works  well so far17:50
SamYapleare you sure anyone actually does it the way you are saying? :)17:51
sdakewhat you prpose is only confirmed bugs go into the tracker17:51
SamYapleive never done it that way17:51
SamYaplethats not what i purpose17:51
sdakebut nobody actually ever confirms a bug in most cases17:51
SamYaplethey shouldnt be targeted unless they are going to be fixed17:51
sdakethey should be targeted if they are confirmed17:51
sdakebecause they need to be fixed17:51
sdakeprioritized from high to low17:52
SamYapleright, but not _that_ _cycle_17:52
SamYaplenot that release17:52
sdakepeople don't use the "bug" top level17:52
SamYapleif you are pushing bugs forward you are failing17:52
SamYapleall bugs in the tracker should be completed17:52
SamYapleor they shouldnt have been targeted17:52
*** fgimenez has quit IRC17:52
SamYapleim just telling you how launchpad projects typically work17:52
sdakerecommend adding a session to the austin summit - we can discuss further there how to handle bug triage17:53
SamYaplelimamauricio: i meant the manila-share container, where does it run?17:53
SamYaplehey rhallisey i need a quick merge on this https://review.openstack.org/#/c/284793/17:54
SamYapleyour comments can be addressed when we set up logging for libvirt17:54
SamYaplethat is breaking compute for kvm17:54
*** rmart04 has joined #kolla17:55
inc0duh...1999 Bps is not a fast networking17:55
SamYaplemtu issue inc0 ?17:56
inc0hmm17:58
inc0might be17:59
inc0eth0 mtu 1450, in docker its 150017:59
limamauricioSamYale, it runs on storage node17:59
*** kproskurin has quit IRC18:00
SamYapleinc0: lol yea thats it18:00
SamYaplelimamauricio: storage node is not going to have openvswitch running18:00
SamYapleit _can_ in the case of AIO, but there is no assurance it will have openvswitch18:00
*** sdake_ has joined #kolla18:01
*** athomas has quit IRC18:02
*** sdake has quit IRC18:03
SamYapleinc0: you can tcpdump for fragmented files18:07
SamYaplei bet youll see alot18:07
limamauricioSamYaple, /run create an openvswitch dir within manila_share container, it's that it needs. do the communication is a work for neutron18:07
SamYapleor better yet turn _off_ fragmented files and youll see no connectivity18:07
SamYaplelimamauricio: openvswitch isnt gauranteed to run on the storage node therefore the socket may not exist18:08
limamauriciobut only one driver needs it, generic share driver that uses Nova and Cinder18:09
limamauricioSamYaple ^18:09
limamauricioSamyaple it connects manila-share service host to neutron networks18:10
SamYaplelimamauricio: i suggest trying to deploy multinode where storage is its own node, youll see this doesnt work18:10
limamauricioin theory ;)18:12
*** rmart04 has quit IRC18:12
openstackgerritMauricio Lima proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968818:14
SamYapleinc0: hey18:18
SamYaplenova upgrade18:18
SamYaplesighup crashes container18:18
SamYaplefor nova-api18:18
limamauricioSamYaple, the role of ansible files is not guarantee that the openvswitch will be running on the node, I think it is a role of Dockerfile18:18
SamYaplelimamauricio: youre wrong, its ansible18:18
SamYapleand openvswtich _shouldnt_ be on all nodes18:19
SamYaplejsut nodes where its needed18:19
limamauriciowhere?18:19
limamauriciowhere ansible do it18:19
limamauricio:/18:19
SamYapleneutron role18:20
limamauriciook18:20
openstackgerritRajath Agasthya proposed openstack/kolla: Recommend vagrant and heat for development only  https://review.openstack.org/28485618:21
SamYapleinc0: major issue with the nova upgrade18:22
SamYaplethat sighup stuff is not working18:22
*** rhallisey has quit IRC18:22
inc0duh18:22
*** rhallisey has joined #kolla18:22
inc0SamYaple, you mean configs are not reloaded?18:23
SamYaple| 60  | nova-consoleauth | ubuntu1 | internal | enabled | up    | 2016-02-25T18:22:53.000000 | -               |18:23
SamYaple| 78  | nova-consoleauth | ubuntu3 | internal | enabled | down  | 2016-02-25T18:11:12.000000 | -               |18:23
SamYaple| 96  | nova-consoleauth | ubuntu2 | internal | enabled | down  | 2016-02-25T18:11:24.000000 | -               |18:23
SamYaple| 114 | nova-scheduler   | ubuntu1 | internal | enabled | up    | 2016-02-25T18:22:50.000000 | -               |18:23
SamYaple| 117 | nova-scheduler   | ubuntu2 | internal | enabled | down  | 2016-02-25T18:11:29.000000 | -               |18:23
SamYaple| 120 | nova-scheduler   | ubuntu3 | internal | enabled | down  | 2016-02-25T18:11:20.000000 | -               |18:23
SamYaplei mean that, stuff isnt coming back18:23
SamYapleit crashed nova-api18:23
inc0-.-18:23
inc0hail nova18:23
SamYaplei think that sighup stuff is a bad idea18:24
SamYaplewe should remove it18:24
SamYaplei dont think its needed anyway18:24
inc0according to dansmith it is18:25
SamYapleno we already od a contaienr restart18:25
SamYapleso that a full process reload18:25
SamYaplei dont think its needed18:25
sdake_inc018:26
sdake_can you do me a solid18:26
sdake_i know its a little annoing18:26
sdake_can you add the PI for kolla-upgrade here https://review.openstack.org/#/c/283278/18:26
limamauricioSamYaple, i think you still do not understand, maybe I did not explain in the best way. manila_share not needs openvswitch, only one driver needs it.18:26
limamauricioso, i'll do it on multinode to confirm18:26
SamYaplelimamauricio: the logs you posted before showed manila-share trying to talk to the unix socket for openvswitch18:27
*** kzaitsev_mb has quit IRC18:29
sbezverksdake_ I still get that error even with re-build containers. any debugging suggestions? 'AnsibleUndefinedVariable: One or more undefined variables: float object has no element 80', 'failed': True}18:30
sdake_did you answer if you have 80 set somewhere in your config options in the /etc directory?18:31
SamYaplesbezverk: did you modify the harpxoy.cfg file?18:31
sbezverksdake_ I do not have it SamYaple no I have not modified anything .18:32
sdake_inc0 did you see my request above fine sir?18:32
*** salv-orlando has quit IRC18:32
inc0sdake_, yeah, I'm on call now, will do in few minutes18:33
sdake_tia18:33
sdake_sbezverk reading irc log, you mentioend you were going to modify teh haproxy.cfg..j2 file18:34
sdake_sbezverk I suggest double checking you didn't actuall modify it ;)18:35
*** inc0 has quit IRC18:35
sbezverksdake_ correct, but I was just run 'cat'18:36
openstackgerritMichal Rostecki proposed openstack/kolla: Playbook for magnum upgrade  https://review.openstack.org/27579818:36
sdake_sbezverk how did you install kolla, via the pip method?18:36
sbezverksdake_ yes18:38
sdake_uninstall it18:38
sdake_and reinstall it18:38
*** jtriley has quit IRC18:38
sdake_and remove /var/lib/kolla inbetween18:38
*** salv-orlando has joined #kolla18:39
sdake_SamYaple do you think that will get him back an original haproxy file?18:39
SamYaplegit checkout master -- ansible/roles/haproxy/templates/haproxy.cfg.j218:39
sbezverkSamYaple sdake_ done, do I need to re-build containers?18:43
sdake_you dont need to rebuild containers18:44
sdake_just deploy again18:44
sdake_you might clean up inbetween tho ;)18:44
sdake_SamYaple he is using the instructions which pip install the ansible code18:44
sdake_i am not sure if kolla-ansible reads the ansible files rom /usr/share or not18:45
sbezverksdake_ I ran cleanup_containers on the target box18:45
sdake_good - and cleanup-host18:46
sbezverksdake_ same error :-(18:46
*** jtriley has joined #kolla18:46
limamauricioSamYaple, i'll deploy a multinode environment to test it18:46
limamauricio:)18:46
sdake_sbez do following18:47
sdake_sudo updatedb18:47
sdake_sudo locate haproxy.cfg.j218:47
sdake_sbezverk ^18:47
limamauricioSamYaple, you've done this deployment?18:47
sdake_sbezverk then replace that file with the one in master repo18:47
sbezverksdake_ I am on centos, do not see updatedb18:49
*** jtriley has quit IRC18:49
*** jtriley has joined #kolla18:49
sdake_sudo yum install mlocate18:49
limamauricioSamYaple, openvswitch runs on compute node??18:53
sbezverksdake please see log: http://paste.openstack.org/show/488247/ haproxy in master is identical the one I am using..18:53
SamYaplelimamauricio: yes18:56
limamauricioSamYaple, oh god, you are right. i need to ensure that the storage node also do it18:58
limamauricio:)18:58
*** inc0 has joined #kolla18:59
*** Marga_ has quit IRC19:00
*** daneyon has joined #kolla19:02
*** blahRus1 has joined #kolla19:02
sdake_sbezverk you didn't diff the /usr/share file19:02
sdake_in our paste19:02
sdake_our/your19:02
inc0SamYaple, so reason we have sighup is to re-read update levels19:02
inc0and restarting containers won't do it because by the time they restart lowest version will be still Liberty19:03
inc0sighup will update it to mitaka19:03
inc0so you're saying that it breaks nova services? that's crappy.19:03
*** blahRus has quit IRC19:04
SamYapleinc0: it does indeed break nova19:05
SamYaplenova-api completely crashes19:05
sdake_sbezverk nevemrind apparently i'm blind19:05
SamYaplefully restarting the container would upgrade to mitaka though19:05
sdake_(nearly am actually :)19:05
openstackgerritMichal Jastrzebski (inc0) proposed openstack/kolla: HAProxy and Keepalived upgrade  https://review.openstack.org/28327819:05
SamYapleinc0: ^^19:05
inc0we can do it as restart with serial I think19:05
SamYapleyou would have already fixed conductor so that would be the upgrade levels19:06
SamYapleso if conductors are mitaka (they would be) then we would restart all other services19:06
SamYaplewe can just drop the sighup stuff entirely19:06
*** daneyon has quit IRC19:06
SamYapleat that point all containers are upt to dat19:06
SamYapledate*19:06
inc0SamYaple, sdake_ https://review.openstack.org/#/c/283278/ plz19:06
dave-mccowanquestion on idempotency.... for the certificate generator: is the correct behavior:  if (any file that the script makes exists): bail.  else: continue  ?19:07
inc0SamYaple, join me in #openstack-nova plz19:07
sdake_inc0 i already hti +2 on it bro ;)19:07
inc0thanks m819:07
rhalliseyinc0, what's left to go on upgrades?19:08
inc0rhallisey, if you're done with cinder19:09
rhalliseyneutron prolly19:10
inc0mariadb and ceph is on SamYaple  (Sam, do you need help?)19:10
SamYapleinc0: ill push patches for neutron and ceph tonight19:10
SamYaplemariadb should mirror rabbitmq19:10
inc0so find master node and tear it down last?19:11
SamYaplewell not quite, just pick a node thats up to date and tear down last19:11
SamYapledifference with mariadb is you must start that node first19:11
sbezverksdake_ anything else to check??19:11
sdake_sbezverk no the assumption that you modified your haproxy.cfg.j2 file is proven incorrect19:12
sdake_try git diff, and see if any files are different in your repo19:12
sdake_I sitll think perhaps you set something in your globals.yml which is breaking things19:12
sdake_SamYaple if you see sbezverk paste above, you will see he has not modified his haproxy.cfg.j2 file19:13
sbezverksdake_ here is my globals: http://paste.openstack.org/show/488253/19:17
sbezverksdake_ maybe you can spot something..19:17
SamYapleinc0: looks like we can drop the sighup stuff this cycle19:18
limamauricioSamYaple, the configuration to run opencswitch on storage node should be on roles/neutron or roles/manila?19:18
sdake_kolla_external_address: "{{ 192.168.80.25 }}"19:18
sdake_why the {{ }}?19:18
SamYaplesdake_: that would be wrong19:18
inc0but we still need restart of everything after process is done19:18
sdake_sbezverk i am pretty sure that is wrong19:18
SamYapleit would try to parse as a variable19:18
SamYapleinc0: we do19:18
SamYapleinc0: new images19:18
inc0which means after last compute node is upgraded19:18
inc0no, that's not it19:18
SamYapleso all contaienr would be restarted19:18
sdake_sbezverk kolla_external_vip_address: "{{ 192.168.80.205 }}"19:18
*** JoseMello has quit IRC19:18
sdake_I am also pretty sure that is wrong19:18
inc0we need to restart all containers AFTER we upgrade19:18
SamYapleinc0: we need to restart all the compute nodes again too?19:19
inc0don't forget it's asyncronous19:19
sdake_sbezverk out of curiosity, why did you put the {{ }} in those variables?19:19
inc0yeah, that's what Dan said one day19:19
sdake_is it because they were already present?19:19
inc0so instead of calling sighup we can call restart, but well19:20
sbezverksdake_ yes19:20
inc0it's more disruptive19:20
sdake_is {{ 192.168.z.z }} an ip address? :-)19:20
sdake_remove the {{ }} in the variable definition and yo should be good to go19:20
elemoine_what's strange is that sbezverk said it was working for him a few days ago19:20
sdake_elemoine_ he repulled master it looks like19:21
SamYapleinc0: it will be alright19:21
sdake_after the vip work hit19:21
SamYapleso we do all the nova-compute at the same time19:21
SamYaplethen all the others serial, then nova-compute restart19:21
inc0what do you mean by all the nova compute at same time19:21
inc0?19:22
sbezverksdake_ so I remove {{}}?19:22
elemoine_sdake_: Yes I know, but with this in his config file how could it work before he pulled from master...19:22
SamYaplei meant upgrade condcutor. restart nova-coputes serially, restart all otehr nova services serially, restart nova-compute serially19:22
SamYaplenova-computes appear to be the only ones that need to restart twice19:22
SamYapleelemoine_: kolla_external_vip_address is a new value19:23
sdake_sb from those two lines i pasted above yes19:23
SamYaplelike i said initial, mostly wrong config here19:23
elemoine_SamYaple: oh right, I thought we were talking about kolla_external_address here19:24
inc0SamYaple, no, all of them needs 2 restarts19:25
inc0we upgrade conductors as first step19:25
inc0then we upgrade control plane19:25
inc0then we upgrade compute19:26
inc0then we reload configs when all of it is up-to-date19:26
inc0reload configs on every service19:26
inc0which means we can restart in serial19:26
SamYapleim saying upgrade conductors then compute19:26
SamYaplethe the control plane stuff neds single restart19:26
sdake_inc0 that approach sounds correct to me19:27
inc0I mean it needs restart during container redeployment and forced restart19:27
sdake_SamYaple could you expand on why control palne needs single restart19:27
inc0so 2 restarts total19:27
SamYapleinc0: right, thats my point, lets skip the 2 restarts. single restart only19:27
SamYapleupgrade conductors, upgrade compute, upgrade control plan restart contductors and compute19:28
SamYapleno restart needed on control plane since computes will have been upgraded19:28
inc0not really19:28
SamYaple19:21:07 < SamYaple> dansmith: to clear up some confusion. we would need to restart/sighup all nova services after the last nova-compute node is upgraded. does that mean _also_ the nova-compute services again?19:28
inc0because upgrade will always be async19:28
SamYaplehe said yes19:28
SamYapleit just means we need ot upgrade nova-compute after conductors19:29
SamYaplethen the other services will restart at the newest level19:29
*** salv-orlando has quit IRC19:29
sbezverksdake_ after removing {} It went further but got stuck again at the waiting for VIP place..19:29
inc0hold on19:30
inc0if we have 2 APIs19:30
sdake_sbezverk you need to provide more data then that19:30
sdake_how about a paste of where its sstuck19:30
sbezverksdake_ so I am back to the original issue from this morning :-(19:30
inc0and restart one then restart other because ansible doesn't sync this stuff19:30
sdake_i dont know what original issue you had19:30
sdake_but the {{ }} is wrong19:30
inc0one we restart first will still consider itself to be Liberty19:30
inc0because other one was Liberty on the moment it restarts19:30
SamYapleinc0: oh i see the confustion here19:30
SamYapleyea we need multiple steps for the serial launching19:31
SamYaplenot just one big serial playbook like you have now19:31
sbezverksdake_ it would probably a good idea to get rid of {{}} in the original files, it is a bit confusing whther you need them or not..19:31
inc0so we need to ensure everything is up to date and then restart again19:31
limamauricioSamYaple, to deploy openvswitch in storage node add inventory_hostname in groups['storage'] in neutron roles files would be correct?19:31
inc0it is serial now19:31
SamYaplewe only need to ensure conductors and compute are up to date inc019:31
inc0what we can't do is to have reload as single step19:31
SamYaplethen upgrade/restart the api/scheduler stuff19:32
SamYaplethen restart the conductors and compute again19:32
SamYapleso api/scheduler only restarts ones19:32
SamYaplethe conductor and compute restart twice19:32
inc0so I'm not sure how upgrade_levels are implemented19:32
inc0but if scheduler controls version of coputes as well19:33
inc0we need 2 restarts19:33
sbezverksdake_ when I start deploy it get stuck on [haproxy | Waiting for virtual IP to appear] and then script fails after time out gets expired.. but on the target system I do see VIP address and port in listen..19:33
inc0if it does not, just one19:33
SamYapleinc0: ok sounds like you have to question to ask19:33
sdake_sbezverk paste your globals.ymla gain plz19:33
SamYaplei agree with your assesment19:33
sbezverksdake_ here you go: http://paste.openstack.org/show/488256/19:35
*** vhosakot has quit IRC19:35
sdake_sbezverk I am pretty sure but not positivey our external and internal VIPs need to be separate IPs19:35
sdake_what is located at ip address .205?19:35
inc0SamYaple, no, now when I think about it, we need 2 restarts whatsoever19:35
inc0however*19:35
sdake_the target node or nothing?19:35
inc0because of this async thing I mentioned before19:35
limamauricioopenvswitch is deployed on compute node through inventory_hostname in groups['compute'] in neutron roles files?19:36
inc0if you have 2 apis, there is no guarantee that container upgrade will trigger correct upgrade_version detection19:36
*** Marga_ has joined #kolla19:36
inc0even if all APIs care about are APIs19:36
*** salv-orlando has joined #kolla19:36
inc0because upgrade between nodes might be async19:36
inc0so we need 2 restarts, and since we do, we might do it after all is done19:37
*** vhosakot has joined #kolla19:37
sbezverksdake_ 80.205 is VIP19:39
sdake_so an unused IP address on your network?19:39
sdake_you need a .206 VIP as well for external vip address19:39
sbezverksdake_ I collected logs from haproxy and keepalive containers http://paste.openstack.org/show/488257/19:39
sdake_sbezverk thanks for doing that, but until you have separate ips for kolla_internal_address and kolla_external_vip_address it doesn't help :)19:40
sdake_what is 192.168.80.25?19:40
openstackgerritEric Lemoine proposed openstack/kolla: [WIP] Make Heka send logs to Elasticsearch  https://review.openstack.org/28418819:41
inc0SamYaple, let's do this, just to be on the safe side: refactor reload.yml to reload controllers and reload compute19:41
*** pbourke- has joined #kolla19:41
sbezverkit is ip on my management interface and it is used to access opensatck?19:41
inc0and reload compute first with serial 10% and then reload controllers with serial 30%19:41
inc0reload will restart each container, no upgrade, just docker restart19:41
sbezverksdake_ let me try to add 80.20619:41
sdake_you can't just blindly add 20619:42
sdake_you hav eto make sure 206 is not an address in use19:42
sdake_sbezverk are you deploing from one node to another?19:42
sbezverksdake_ That is correct, I use deployment VM and pushing containers to a baremetal server.19:44
sbezverksdake_ new globals.yml, same result http://paste.openstack.org/show/488259/19:45
sdake_sbez what is on .25?19:45
sdake_is that your baremetal server?19:46
sbezverksdake_ .25 yes19:46
sdake_kolla_external_address should be .20619:46
sdake_or .20519:47
sdake_but definately not .2519:47
sdake_the docs seem to indicate it should be .20519:47
sdake_but I think it should be .2019:47
sdake_.20619:47
sdake_dave-mccowan any thoughts ^^19:47
SamYapleinc0: thats the quickest solution. we will optimize later19:49
sbezverksdake_ 80.25 is bound to management interface, which is supposed to be used to access horizon on baremetal server, I thought 80.205 will be used for internal opensatck services.. not understand why would I need and 80.206, but if it help to make things working, then why not..19:49
inc0optimize would mean we need to figure out sighup19:49
inc0that's the end solutio19:49
inc0n19:49
SamYapleinc0: eh whatever. lets just get it working19:49
sdake_sbezverk the idea is you ahve an internal management network, and an external API network19:50
inc0yeah, that's my point19:50
openstackgerritMauricio Lima proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968819:50
sdake_dave-mccowan can probably do a better job of explaining then I can19:51
sdake_or the docs explain it19:51
sdake_but the external_address should not be .2519:51
*** ayoung has quit IRC19:51
sbezverksdake_ in all_in_one scenario everything should be able to collapse to three interface 1 - management including internal openstack services, 2- neutron external/provider interface 3 - tenants19:51
sdake_inc0 re the 20 node setup19:51
SamYaplesbezverk: please post your globals.yml, inventory, and `ip a` and `ip r` from each node19:51
sdake_inc0 did you haea chance to get kolla deployed on it19:51
dave-mccowanunless you have a reason to use two VIPs, you're probably better off not using two VIPs19:52
SamYaplesbezverk: AIO can be single interface, or easily two interfaces19:52
sdake_there is no tenant interface19:52
inc0just get access to it, I'll deploy 1.1.019:52
SamYaplesdake_: tehre is a tenant interface19:52
sdake_i know19:52
sdake_but he doesn't need to muck with that19:52
sdake_sbezverk look at the original configuration file19:53
inc0and then, after Mitaka release I'll upgrade it to mitaka19:53
sdake_any thing with interface in it that wa commented out, recommend out :)19:53
sdake_recomment out :)19:53
inc0but I will have 20 nodes for our talk19:53
dave-mccowanunless you're using NAT or DNS, leave out kolla_external_address, and all.yaml will take care it for you.19:53
sdake_inc0 i'm just curious what the time is to deploy on 20 nodes19:53
inc0will let you know19:53
sdake_dave-mccowan and klla_external_vip_address correct?19:54
sbezverkSamYaple Here is requested info: http://paste.openstack.org/show/488261/19:54
sdake_sbezverk kolla will choose smart defaults for anything in the globals.yml that is commented out19:54
sdake_sbezverk anything that isnt' commented out must be set19:54
sdake_that should probably go at the top of globals.yml ;_)19:54
SamYaplesbezverk: external_adress should be dns name that maps to 192.168.80.20619:55
dave-mccowanunless you want two vips for a reason (like security in production), comment out kolla_external_vip_address and defaults will do the right thing.19:55
dave-mccowanif you want two vips, set kolla_internal_address and kolla_external_vip_address to different IPs that are not in use anywhere else.  set network_interface and external_vip_interface appropriately.19:56
SamYaplesbezverk: kolla_external_address conflicts with address on mgmt_br019:56
sdake_sbezverk back to basics here, don't use the second VIP19:57
sbezverkSamYaple ok if I set  kolla_external_address conflicts to 192.168.80.205 and do not use any reference to 80.25, the issue should be resolved right?19:57
SamYaplesbezverk: i mean yea i suppose so. i would just recommend commenting out the kolla_external_address and kolla_external_vip_address variables19:58
SamYaplethe defaults are what you want19:58
openstackgerritMauricio Lima proposed openstack/kolla: Add ansible support for Manila  https://review.openstack.org/26968819:58
SamYaplelimamauricio: can you point me to some docs as to what manila-share needs to interact with openvswitch for?19:59
sdake_sbezverk take sam's recommendation of commenting out kolla_external_address and kolla_external_vip-address, sdake and dave-mccowan agree19:59
sdake_sbezverk dont forget to cleanup your containers ;-)20:00
limamauricioSamYaple, I thought I'd add a condition to implement "ovs" in the storage node only when the enable_manila = yes20:02
SamYaplelimamauricio: and if you just run with manila, it wont deploy openvswitch20:03
SamYapleno what needs to happen is openvswitch needs to be its own role if more than just neutron needs it20:03
SamYaplehowever i would like some docs as to its interaction20:03
sbezverkSamYaple with new kolla_internal_address 192.168.80.205, I see the same issue. http://paste.openstack.org/show/488265/20:04
sbezverkSamYaple but VIP address and ports show as LIsten on target host: see this: http://paste.openstack.org/show/488267/20:06
limamauricioSamYaple https://review.openstack.org/#/c/273724/20:08
limamauricioif you see it better can use it http://52.34.178.242:8000/html/manila-share-install.html20:08
SamYaplelimamauricio: that says the neutron agent must be running on the same node as manila-share20:10
limamauricioyes20:10
SamYaplethats a whole different situation20:10
limamauriciobut manila-share should run in storage-node20:10
SamYaplei frankly dont have time to look into this but this make neutron a required role to run before manila20:11
limamauricioI tried to explain this to you, but I could not. sorry :/20:11
dave-mccowansdake_ question on idempotency.... for the certificate generator: is the correct behavior:  if (any file that the script makes exists): bail.  else: continue  ?20:13
SamYapledave-mccowan: not quite20:13
SamYapleits not any file it makes, its what does that particular action make20:13
SamYapleso if you break after creating file1, but the end result is file1 file2 file3, running again should generate file2 and file320:14
limamauricioneutron agent is required to generic driver manage a share server20:14
dave-mccowanSamYaple.  i'm worried about ending up with mismatched certificates... where the CA.crt doesn't match the Server.pem.20:14
sdake_afk helping on sbezverk in a screen share dave-mccowan20:15
SamYapledave-mccowan: youd need to write checks for that then20:15
sdake_my take is sort of - but I'll have to get back to you20:15
SamYaplealright guys. i have a bit of an issue :/20:15
*** Marga_ has quit IRC20:15
SamYaplei think we need to update kolla_internal_address to kolla_internal_vip_address20:15
*** Marga_ has joined #kolla20:15
SamYapleand make kolla_intenral_address a dns name20:15
SamYapleor we need to rename kolla_external_vip_address20:15
SamYapleits just to confusing20:16
*** inc0 has quit IRC20:16
dave-mccowanSamYaple I agree.   trade off between backward compatible and confusing.  maybe we can make the current names aliases that we deprecate?20:17
SamYaplei think we need to keep kolla_internal_address the same20:17
dave-mccowani like kolla_internal_vip_address and kolla_external_vip_adress.20:17
limamauricioSamYaple, I thought I'd add a condition to implement "ovs" in the storage node only when the enable_manila = yes, it will resolve20:17
SamYapleyea but least impactful change is changing the other ones20:18
*** pbourke- has quit IRC20:18
SamYapledave-mccowan: im not sure yet20:18
SamYaplebut we need to do something20:18
limamauriciojust deploy ovs on storage node if enable_manila = yes SamYaple20:18
SamYaplelimamauricio: its not just ovs, its neutron agent and ovs20:18
*** salv-orlando has quit IRC20:18
limamauricioyes yes20:18
limamauricioboth20:18
limamauricioso you think you add inventory_hostname in groups [ 'storage'] and check condition is not the right way? SamYaple20:20
*** salv-orlando has joined #kolla20:20
dave-mccowanSamYaple part of the solution will be a section of document with examples of the different possibilities20:20
SamYapledave-mccowan: what about kolla_internal_dns_name and kolla_external_dns_name20:24
SamYaplekolla_internal_address and kolla_extnerla_address20:24
SamYaplewhere the later two are teh vip20:24
*** Marga_ has quit IRC20:25
dave-mccowando you think it's common to use a NAT address as kolla_external_address today?  or is steve the only one who does that?20:25
*** kzaitsev_mb has joined #kolla20:26
*** Marga_ has joined #kolla20:26
SamYapleactually i think i have it for backwards compatibility20:26
SamYaplelet me submit a patch20:26
*** Marga_ has quit IRC20:27
*** gfidente has quit IRC20:39
*** daneyon has joined #kolla20:40
openstackgerritEric Lemoine proposed openstack/kolla: Make Heka send logs to Elasticsearch  https://review.openstack.org/28418820:42
*** JoseMello has joined #kolla20:42
*** haplo37 has quit IRC20:43
openstackgerritMerged openstack/kolla: Fix /etc files location for ironic-base building from sources  https://review.openstack.org/28479520:52
*** Marga_ has joined #kolla20:55
*** Marga_ has quit IRC20:59
*** pbourke- has joined #kolla21:02
*** haplo37 has joined #kolla21:06
sdake_dave-mccowan pretty sure i'm the only one who does that ;-)21:12
openstackgerritEric Lemoine proposed openstack/kolla: Make Heka send logs to Elasticsearch  https://review.openstack.org/28418821:14
daneyonSamYaple are you there?21:16
*** pbourke- has quit IRC21:20
sdake_sbezverk I had another thought, perhaps your network device is bokred in some way21:21
sdake_a recycle could do the trick21:21
sdake_sbezverk another option is to use the address .20721:21
sdake_since the arp tables wouldn't have been corruptd by 205/20621:21
*** Marga_ has joined #kolla21:22
*** achanda has quit IRC21:23
SamYapledaneyon: here i am!21:25
daneyonSamYaple thx21:25
*** pbourke- has joined #kolla21:25
sdake_yo pbourke21:25
pbourke-sdake_: hey!21:25
daneyoni'm presenting kolla to a meetup group tonight... scary :-o21:25
SamYapledaneyon: oh that is scary21:25
SamYapledoes it work?21:25
pbourke-course it does21:26
daneyonSamYaple do you have a kolla demo machine or a recorded demo of kolla? My recording is super ld and the one you and sdake did in Tokyo is a bit much for my audience21:26
SamYapledaneyon: I do not have a recording or a remotely accessable demo machine at this time21:27
*** Marga_ has quit IRC21:27
daneyonSamYaple OK21:27
SamYapleone of the other folks here might21:27
daneyonSamYaple sdake does this doc still work: http://docs.openstack.org/developer/kolla/heat-dev-env.html21:29
*** achanda has joined #kolla21:31
*** achanda has quit IRC21:33
SamYapledaneyon: i dont think so. but wait for sdake to confirm. i dont think anyones used it in a long time21:34
SamYaplei never have successfully used it21:35
sdake_SamYaple does this change make any sense to you https://review.openstack.org/#/c/284836/221:35
*** sdake_ is now known as sdake21:35
sbezverksdake_ if going to the older version does not help, I will start moving physical things around.. I am still rebuilding containers..21:35
SamYaplesdake: you know thats mesos right?21:37
sdakeSamYaple yes for some reason I thought it was in kolla repo21:37
*** achanda has joined #kolla21:37
*** pbourke- has quit IRC21:37
SamYaplesdake: can you respond to daneyon ?21:38
sdakeSamYaple i already did21:38
sdakehe followed that up by asking you21:38
SamYaplehmm i dont see that in my logs ok.21:39
daneyonsdake my latest question is related to http://docs.openstack.org/developer/kolla/heat-dev-env.html21:39
SamYapleright21:39
daneyonsdake is the above doc accurate?21:39
sdakedaneyon i see, well heat and vagrant, I'd say are bust21:39
sdakedaneyon so I doubt that heat works at all, and YMMV with vagrant21:40
daneyonsdake ok21:40
sdakenobody maintains it21:40
*** limamauricio_ has joined #kolla21:43
*** opennode has joined #kolla21:45
*** Marga_ has joined #kolla21:51
openstackgerritMerged openstack/kolla: General improvements to quickstart  https://review.openstack.org/28430521:52
openstackgerritMerged openstack/kolla: Import module rather than funciton in the set_configs.py file  https://review.openstack.org/28450721:53
daneyonsdake SamYaple is docker hub still the place where the official kolla images live? It looks like it, but just want to double-check.21:55
sdakedaneyon we don't push official images at this time21:55
sdakedaneyon i am working to get it done in the gate21:56
sdakethere are crednetial issues which need to be sorted out21:56
*** rhallisey has quit IRC21:57
daneyonsdake ok... so no official repo to pull, users need to build their own from src.21:58
sdakeor from binary21:58
sdakeeither works21:58
sdakemore or less21:58
limamauricio_SamYaple, i'm thinking revert my patch and create a new one to solve the problem of Manila, neutron agent and openvswitch21:58
openstackgerritMerged openstack/kolla: Add the default empty reconfigure.yml file to all roles  https://review.openstack.org/28355121:58
limamauricio_What do you think about this? SamYaple21:59
*** dwalsh has quit IRC22:00
*** macsz has joined #kolla22:09
*** achanda has quit IRC22:09
openstackgerritYathiraj Udupi proposed openstack/kolla: Added a Nova guide  https://review.openstack.org/28496122:18
openstackgerritYathiraj Udupi proposed openstack/kolla: Added a Nova guide  https://review.openstack.org/28496122:22
*** opennode has quit IRC22:22
*** vhosakot has quit IRC22:23
*** vhosakot has joined #kolla22:31
*** macsz has quit IRC22:32
openstackgerritRicha proposed openstack/kolla: Fixed grammatical error in ceph-guide.rst  https://review.openstack.org/28496822:32
*** jtriley has quit IRC22:32
sdakesbezverk found a legimiate keepalived bug22:34
sdakegit blame shows keepalived was changed feb 16 to use socat22:34
*** rhallisey has joined #kolla22:35
sbezverksdake Here is the bug I did I filed this morning.. https://bugs.launchpad.net/kolla/+bug/154985722:37
openstackLaunchpad bug 1549857 in kolla "deployment waiting for VIP address until timed out" [Undecided,New]22:37
openstackgerritRicha proposed openstack/kolla: Fixed grammatical error in ceph-guide.rst  https://review.openstack.org/28496822:37
sdakesbezverk are you going t o fix that bug or wnat someone else  to take care of it?22:42
sbezverksdake if you do not mind and have a bit of time to walk me through the process, I would like to fix it, if it is urgent then I guess somebody else should do it22:43
sdakei can work with you friday to get setup22:44
sdakeif your available then22:44
sdakeint he afternoon22:44
sdakeyou found the bug and found the fix, ou should get credit f or it ;)22:44
sdakei would have never thought of running keepalived separately from a container22:45
sdakenever is a long time, i mean I may have got there eventually22:45
sbezverksdake sure I have time tomorrow or tonight22:45
sbezverkit is up to you22:46
*** absubram has quit IRC22:48
sdaketonight then22:48
sdakei usually work quite a bit22:49
sdakeso i'll be around22:49
openstackgerritRicha proposed openstack/kolla: Fixed grammatical error in ceph-guide.rst  https://review.openstack.org/28496822:49
sdakeI find it fascinating how much our docs improve in the last 2-3 weeks prior to a cycle ending22:52
sdakeSamYaple  ^^22:52
openstackgerritRicha proposed openstack/kolla: Fixed grammatical error in ceph-guide.rst  https://review.openstack.org/28496822:53
openstackgerritRicha proposed openstack/kolla: Fixed grammatical error in ceph-guide.rst  https://review.openstack.org/28496822:54
vhosakotdoc merge blast :)22:54
*** ayoung has joined #kolla23:03
*** achanda has joined #kolla23:04
openstackgerritMerged openstack/kolla: HAProxy and Keepalived upgrade  https://review.openstack.org/28327823:05
SamYaplesdake: feb 16.... 2015 it was changed to use socat23:07
SamYapleits been like that for a long fine23:07
SamYaplei mean its possible centos _never_ worked... i guess?23:08
*** salv-orl_ has joined #kolla23:08
sdakeperhaps socat isnt' it23:09
sdakei was reading 201623:09
sdakenot 2015 ;)23:09
SamYapleyea socat has been there since inc0 initially implemented keepalived23:09
SamYaplei known because i fought him on it23:09
SamYaplenothing has changed recently at all23:10
SamYaplesocat exists in teh centos container23:10
SamYaplei really dont know what you think youve found23:10
sdakepossible i am wrong23:11
sdakewe are looking into it, will let you know23:11
sdakethe ^^ was for the doc comment ;)23:11
*** blahRus1 has quit IRC23:11
SamYapleyea im jsut letting you know. this is likely user error....23:11
*** salv-orlando has quit IRC23:12
sdakeya socat is in the keepalived container not the base container23:13
sdakethe odd thing is, he took the keepalived config and runs it baremetal, that works23:13
sdakehe runs in container, that doesn't work23:13
sdakenot sure how thats user error ;)23:14
SamYapleselinux likes to break that container23:14
SamYapleyou sure thats not turned on?23:14
sdakeselinux permissive23:14
SamYapleand mind you, it could be an outdated container23:14
SamYaplewhen was the last rebuild?23:14
openstackgerritDave McCowan proposed openstack/kolla: Add Ansible scripts to generate TLS certificates for testing  https://review.openstack.org/28273323:14
sdake37 minutes ago23:14
SamYapleI am doubtful this is a problem with Kolla, or rather one Kolla can fix with a change to its repo23:15
dave-mccowansdake ^^^ idempotency for the win23:15
sdakehas something to do with the check_alive script23:16
SamYaplesure. its probably looking in the wrong location/wrong volume23:17
SamYapleonly thing thats chaged there is named volume usage for the socket, but that was over a week ago23:17
sdakeyup23:17
SamYaplelike i said probably outdated image/repo23:17
sdakehe has an updated repo - i took control of his machine23:17
sdakeand its not out of date23:17
sdakecheck script isn't working23:17
*** pbourke- has joined #kolla23:18
SamYapleim fairly certain you are wrong and I could tell you the issue in about 5 seconds23:18
sdake123:18
sdake223:18
sdake323:18
sdake423:18
sdake523:18
SamYaplethat was 6 seconds23:18
SamYaplehey dave-mccowan are you duplicating the kolla-ansible script?23:19
dave-mccowanyea, to address code review comments from patch 1 to keep this out of kolla-ansible23:20
SamYapledave-mccowan: yea thats not going to work23:20
SamYaplelet me read the comment again23:20
SamYaplebut this duplication is a no go23:20
dave-mccowani'm open to anything.  i figured this way would be extensible, in case there were other things in the future that didn't belong in kolla-ansible.23:21
SamYapleno dave-mccowan i dont see why this shouldnt be in kolla-ansible23:21
dave-mccowanworks for me.23:22
*** haplo37 has quit IRC23:25
*** pbourke- has quit IRC23:26
SamYaplesdake: just fyi if keepalived worked on the host you were most definetely not running the latest harpxoy and keepalived code23:28
sdakeso something odd happened23:28
SamYapleyou were running mixed versions, thats what happened23:28
*** JoseMello has quit IRC23:28
sdakeafter he ran keepalived on the host, and then stopped keepalived, a deployment worked23:28
SamYapleno it didnt work like you think23:29
SamYaplehe stopped keepalived and the vip stuck around23:29
sdakesuspicion is the arp table held he ip address still in cache23:29
SamYaplenope not it at all23:29
SamYaplethis is old out dated code23:29
sdakewhat is old and oudated?23:29
SamYaplewhat you were running and building23:29
sdakeit is definately master23:29
SamYapleyou may have git cloned master, but if there was an old pip install then you likely werent building and/or deploying master23:30
SamYaplemy guess is you built new containers, but deployed old code23:30
sdakei removed the pip installed version23:30
SamYaplejust a guess though23:30
SamYaplebut again, 100% positive you were running old code somewhere if you say keepalived worked on the host23:31
sdakekeepalived worked on bare metal23:31
SamYapleyup then you certainly were running old code womewhere23:31
sdakei think you assume without a basis23:31
sdakethe code is not old23:31
SamYaplealright. well see23:32
sdakethe code is master, the containers are master, i built them myself23:32
SamYaplei bet it will be like all those other time we disagreed and i showed you why23:32
sdakethe one time you mean regarding ntpd?23:32
sdakeyou win on ntpd23:32
sdakefix this one :)23:32
SamYapleand heat config23:32
sdakeSamYaple do you ahve a windows machine around?23:32
SamYapleI do not but as it turns out i need one for this stupid switch23:33
SamYapleactually you know what i think i do...23:33
*** yuanying has joined #kolla23:33
*** yuanying has quit IRC23:34
*** yuanying has joined #kolla23:34
dtturnerHi folks.  Has anyone ever seen the following error during keystone bootstrap?  http://paste.openstack.org/show/488290/23:35
dtturner I'm testing a multinode deploy using images build from trunk last week (kolla==2.0.0.0b3.dev219).23:35
sdakeok SamYaple23:36
sdakehere is what I think happened23:36
sdakeyour right he had old images23:36
sdakeon the deployed target cache23:36
sdakeduring deployment, new images are not deployed23:36
sdakeso we need to add cleanup-images to the docs23:37
sdakeso the registry doesn't deploy new images if images already exists23:37
SamYaplenope23:37
SamYaplenever has23:37
SamYaplenot even the ansible docker module23:38
sdakeya i think everyone thinks they do23:38
SamYapleits never worked like that23:38
sdakefor multinode23:38
SamYaplein fact the pull playbooks were only needed _because_ its never worked like that23:38
*** achanda has quit IRC23:38
SamYaplebut anyway. yea. old code23:39
*** salv-orl_ has quit IRC23:39
limamauricio_SamYaple, i'm thinking revert my patch and create a new one to solve the problem of Manila, neutron agent and openvswitch23:42
SamYaplelimamauricio_: what is the reason a revert is needed?23:42
openstackgerritSteven Dake proposed openstack/kolla: Add NB about cleanup-images  https://review.openstack.org/28499123:43
limamauricio_I think it was very mixed, neutron role, manila role23:43
sdakelimamauricio_ don't forget our friends linuxbridge ;-)23:44
limamauricio_yes yes23:44
limamauricio_Manila will switch to using linux bridge by default23:44
SamYaplelimamauricio_: kolla is openvswitch by default23:45
sdakeenough fun for one day, I'm off23:45
SamYaplesdake: all solved then?23:45
limamauricio_yes23:45
sdakeyup look at last review23:45
SamYapleok ill review in a bit23:45
SamYaplesetting up 10gb switch23:45
limamauricio_Manila will still support ovs, just will not be the default23:46
sdakedid you get that netgear brand?23:46
SamYapleyea23:46
SamYaplesame one you have23:46
sdakei didn't do anything  to config it23:46
sdakejust plugged it in23:46
SamYaplenet to get to web interface to lock down vlans23:46
SamYapleneed*23:46
*** vhosakot has quit IRC23:47
sdakeoh I thought it was completely dumb didn't knwo it had vlans23:47
limamauricio_I'll need a bit of your help SamYaple, i do not know if my last updates in the patch are the best way;23:47
sdakelimamauricio_ we typically dont revert patches that have gone through a thorough review23:47
SamYapleits got a full on web interface with LACP LAG and al lkinds of stuff sdake23:47
sdakeif there is a bug in the implementation, fix it please with a new patch ;)23:47
sdakecool23:47
sdakei'll have to check it out23:47
sdakewhen i gets plugged back in23:48
limamauricio_ok sdake23:48
limamauricio_but if you put a check to check that enable_manila = yes, I believe that this will ensure that neutron agents and openvswitch will only be deployed in the storage node is enable_manila = yes23:49
limamauricio_what do you think SamYaple? ^^23:49
*** achanda has joined #kolla23:49
limamauricio_your opinion is important, I'm looking for the best way to do this23:50
SamYaplelimamauricio_: ill look at the review later23:55
SamYapleshould be simple enough23:55
*** dtturner has quit IRC23:57

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