Wednesday, 2016-08-17

mark-caseyI know you can just pass a regex as the last parameter of kolla-build after passing --no-cache, but I don't remember if a new image of the same tag will automatically superceed as the latest for that image00:00
*** zhurong has quit IRC00:04
*** dwalsh has quit IRC00:05
Pavois there a log of the output of the build process? because I could have sworn as I was watching it build images I seen some errors on the horizon build00:06
mark-caseyother than scrollback I don't think so, you may be able to pass a file name for logging but I don't think there is an implicit one00:07
Pavoah ok00:08
*** jamesdenton has quit IRC00:08
*** kbaegis has left #openstack-kolla00:13
*** kbaegis has joined #openstack-kolla00:28
*** diogogmt has quit IRC00:28
kbaegisHuh00:28
kbaegisAccidentally left apparently00:28
kbaegisDid I miss anything?00:28
*** duonghq has joined #openstack-kolla00:29
mark-caseycomings and goings only00:29
kbaegishey duonghq00:29
duonghqmorning kbaegis00:29
kbaegismorning!00:29
duonghqI'm looking at yesterday IRC log00:30
duonghqwhere are you kbaegis?00:31
duonghqSeem that our Horizon container is messed up?00:34
kbaegisUS00:34
kbaegisWake up at 3:00am local though :)00:34
Pavowell I have done so many edits, guess it best to just start from the beginning lol again00:34
kbaegisStill stuck on horizon00:34
duonghqhaha00:34
kbaegisEverything else works00:34
duonghqso I think I'll checkout horizon back some commit00:35
kbaegisI can make images, networks, vms, etc00:35
kbaegisBut the damn gui doesn't work00:35
kbaegisIt was miscoded in kolla :)00:35
duonghqIt was a pretty GUI huh?00:35
Pavowell now I am having deployment issues again but oh well practice makes perfection right00:35
kbaegisHorizon is pretty00:35
kbaegisEsp. the neutron portion00:35
kbaegisHeat too, I suppose00:35
duonghqhah00:36
duonghqkbaegis: I heart that Heat has trouble itself00:38
duonghq*heard00:38
Pavoso is there away to save my registry offline so I do not have to go through building images again?00:38
duonghqPavo: you can setup a Docker local registry00:39
*** thumpba_ has quit IRC00:39
PavoI was talking about my local registry lol00:39
kbaegisYou can create an image from the container00:39
*** thumpba has joined #openstack-kolla00:39
mark-caseyPavo: on your mac or on a target node that doubles as a deploy host?00:39
duonghqso it should persist?00:39
mark-casey(that is, where is the registry)00:39
kbaegisYes, but the cleanup images will remove it00:40
Pavoregistry is on the deployer node, but about to blow that VM away00:40
duonghqPavo: so you can setup it elsewhere00:40
kbaegisYou can backup containers to tar files as well00:40
mark-caseyyeah, and actually if you're replicating a multinode setup I've usually seen the deployer be a separate host00:40
duonghqjust a Docker container00:40
kbaegisIt'll be large00:40
duonghqPavo: an insecure-registry setting is appropriate00:41
Pavosize no issue, 27Tb here00:41
Pavoand using TLS not insecure00:41
duonghqStill does not got your point, Pavo00:41
Pavoso export or save00:41
duonghqjust grab your volume and backup it?00:42
kbaegissave creates an image, export copies the running container -I think00:43
*** thumpba has quit IRC00:44
duonghqsave is for image and export is for container00:45
duonghqso I think export is the answer00:45
Pavoso to take a container and turn into a image I need to commit then save that image right00:47
duonghqI think its right, but why you need it be a image00:47
Pavobecause export doesn't keep the data, ie.... images pushed to it00:48
Pavobut just commit the registry container and the size looks WAY to small to have all the images pushed in it00:49
Pavolol00:49
Pavo33MB00:49
Pavocan not be right00:49
duonghqyou can check the underlying fs for the right size00:50
duonghq(approvimately)00:50
Pavotrue00:51
mark-caseyPavo: https://github.com/docker/distribution/blob/master/docs/deploying.md#storage00:54
mark-caseyso... if you copy /var/lib/registry to new VM perhaps it will only explode a little? :D00:54
Pavolol00:56
mark-casey:) but I may have read the mount backwards. that may be the in-container path00:57
duonghqkbaegis: does the latest git code it work?00:57
kbaegisI can test00:57
kbaegisHorizon's doesn't00:58
duonghqokay00:58
*** jamesdenton has joined #openstack-kolla01:01
*** jamesden_ has joined #openstack-kolla01:02
*** HyperJohnGraham has joined #openstack-kolla01:03
*** jamesdenton has quit IRC01:06
*** zhurong has joined #openstack-kolla01:09
kbaegisholy &$#!01:19
kbaegisI have horizon01:19
mark-caseywoot01:20
kbaegis:)01:20
*** dave-mccowan has joined #openstack-kolla01:21
*** diogogmt has joined #openstack-kolla01:25
*** daneyon has joined #openstack-kolla01:26
kbaegisNewton is pretty01:26
*** jamesden_ has quit IRC01:27
*** jamesdenton has joined #openstack-kolla01:28
*** daneyon has quit IRC01:30
*** huikang has joined #openstack-kolla01:33
*** jamesdenton has quit IRC01:33
*** fragatina has quit IRC01:34
Pavohow?01:35
Pavolatest git pull?01:36
duonghqkbaegis: nice01:39
duonghqkbaegis: how can you get this01:39
kbaegisNo idea why it's working now01:40
kbaegisI rebuilt from centos source01:40
Pavolol thats awesome01:40
duonghqlol,01:40
kbaegisNo 500s from anything now except nova-compute :)01:40
duonghqPavo: which base do you use? centos or ubuntu01:40
duonghqkbaegis: expect *nova-compute*??? oops01:41
Pavonow using latest git pull01:41
Pavothink its 3.0.001:41
kbaegisIDK.  I'm getting scheduling errors :)01:41
duonghqits 3.0.0 for a while01:41
kbaegisI'll check the api logs and let you know01:41
duonghqyou should get the devxxx revision01:41
duonghqor better if  git revision01:42
kbaegisTotal usable vcpus: 32, total allocated vcpus: 001:44
kbaegisOh! :)01:44
kbaegisJust a neutron issue01:44
kbaegisovs is restarting (1)01:44
kbaegisI can fallback to bridging01:44
kbaegishttp://hastebin.com/ufixumetik.vbs in case it's interesting01:45
kbaegistracebacks from neutron error01:45
duonghqoh01:46
kbaegisneutron-server log http://hastebin.com/olotecimod.py01:47
duonghqjust got Running command: 'start-ovsdb-server 10.164.180.76 '01:48
duonghq error01:48
kbaegisSaying that there's no l2 agent01:48
duonghqah, l2 agent fails you01:48
kbaegisYes01:48
kbaegisneutron-agent-list still around?01:48
duonghqkbaegis: after you do git pull01:48
duonghqjust pip install kolla and rebuild the image?01:48
duonghqanything else?01:49
duonghq(given that I use local registry)01:49
kbaegisFrom current master?  clean images, clean host, rebuild kolla01:49
kbaegisI'll give you a paste of the commands I used01:50
duonghqah, you clean image too?01:50
duonghqso you rebuild your registry, too?01:51
kbaegishttp://hastebin.com/wogiducofa.hs01:51
kbaegisCorrect01:51
kbaegisDefinitely changing tags now that I have a 3.0.0 chain running01:51
duonghqoh, the proress is time consuming?01:51
kbaegisCertainly :)01:52
duonghqthanks01:52
kbaegisUsing centos-source01:52
kbaegisI run in screen so that timeouts don't end the procedure01:52
kbaegistmux, just as good or better01:52
duonghqme tmux,01:52
kbaegisNice01:53
kbaegisI was forced to learn devstack/screen01:53
kbaegisI always liked tmux better01:53
kbaegisScreen splitting and whatnot01:53
kbaegisBut never used it vocationally01:53
kbaegisMuch like dvorak :01:53
kbaegis:)01:53
duonghqdevstack doesn't support tmux well but kolla is not this case01:53
duonghqI use dvorak :)01:54
kbaegisYup.  Everything can support screen too01:54
kbaegisReally?01:54
kbaegisSee, that's awesome01:54
kbaegisdvorak for the win01:54
kbaegisI got up to 80wps on dvorak01:54
kbaegisAnd I haven't used it since01:54
duonghqactually I use drorak and its programmer variant01:55
duonghqmuch easier for my finger then qwerty01:55
kbaegishere's the new and lovely way in which neutron-ovs L2 is broken on gentoo :) http://hastebin.com/odujapizip.vbs01:55
kbaegisOh, I need br-int?01:56
duonghq:)01:56
kbaegisPresumably on host01:56
kbaegisHmm02:02
kbaegisI guess I get to find the lovely way in which ovs can be run INSIDE a container02:02
kbaegisOr simply revert02:02
kbaegisI'm guessing this is one of those times it matters that I'm running linux 4.8 w/ ovs 2.5.002:03
*** unicell has quit IRC02:04
kbaegisOh.  Actually, exactly same version of ovs02:05
kbaegisWell, if anyone was curious- kolla CAN run on gentoo.  It just requires an insane sysadmin with 2 days on their hands02:06
kbaegis*Evil laugh*02:07
mark-caseykbaegis: lol. fwiw I believe ovs is the reason docker daemon runs with MountFlags=shared. I think some ovs config is there and different containers related to ovs needs to see one another updating it in realtime02:07
mark-caseywith MountFlags=shared when using Kolla, I mean02:08
kbaegisGotcha.  Weird solution02:09
mark-caseyI assume only way to do single-process containers02:09
kbaegisWell I mean, its fine for logs.  I think it's weird for proc/sys/dev02:10
kbaegisThat's just because I'm new to containers :)02:10
*** sdake has quit IRC02:13
*** sdake has joined #openstack-kolla02:13
*** zhurong_ has joined #openstack-kolla02:19
*** huikang has quit IRC02:21
Pavogrrrrr now having docker issues02:22
Pavomy luck is horribad02:23
*** zhurong has quit IRC02:23
Pavodocker service will not start on deployer02:23
openstackgerritLeon Zachery proposed openstack/kolla: Simplify install process for faster quickstart execution  https://review.openstack.org/35618102:23
Pavoanyone know what this is level=fatal msg="Error starting daemon: error initializing graphdriver: prerequisites for driver not satisfied (wrong filesystem?)"02:23
*** mewald1 has joined #openstack-kolla02:25
*** haplo37 has quit IRC02:26
*** mewald has quit IRC02:26
openstackgerritLeon Zachery proposed openstack/kolla: Simplify install process for faster quickstart execution  https://review.openstack.org/35618102:27
Pavowait wth how did it set this ExecStart=/usr/bin/dockerd --storage-driver btrfs02:27
openstackgerritDuong Ha-Quang proposed openstack/kolla: Port with_ loop variable syntax to Ansbile 2  https://review.openstack.org/35618302:27
Pavohow do I fix that02:27
*** haplo37 has joined #openstack-kolla02:28
openstackgerritDuong Ha-Quang proposed openstack/kolla: Port with_ loop variable syntax to Ansbile 2 (finish)  https://review.openstack.org/35618302:30
kbaegisPavo You may be able to just remove —storage-driver02:31
Pavofrom what file?02:31
mark-caseysudo systemctl status docker02:32
mark-caseywill say which02:32
Pavohttps://paste.pound-python.org/show/b26OEv9trAVACv7FeNnU/02:33
Pavoso... /usr/lib/systemd/system/docker.service?02:33
mark-caseyshould be /usr/lib/systemd/system/docker.service02:33
kbaegisHmmm. >:(02:33
Pavook02:33
kbaegislinuxbridge still isn't02:34
Pavonot seeing that storage in that file though02:34
Pavofound it02:34
Pavowas in /etc/systemd/system/docker.service.d/kolla.conf02:35
mark-caseyah, that makes more sense02:35
kbaegis Stdout: ; Stderr: iptables-restore: line 36 failed02:35
Pavohave no clue how it got there02:35
duonghqPavo: it is on kolla-kubernetes docs already02:35
duonghqiirc02:35
mark-caseywell, it's a common setting used here. makes more sense than the default suddenly changing02:35
kbaegisHere's the fun way in which linux bridging is broken http://hastebin.com/opuruwowom.vbs02:38
*** zhurong_ has quit IRC02:39
mark-caseykbaegis: so, what you're saying is that super-intense iptables rules that probably took a while to cumulate need to function slightly differently on Gentoo?02:39
*** zhurong has joined #openstack-kolla02:39
kbaegisI think it's not interpreting lines prefixed by #02:40
*** huikang has joined #openstack-kolla02:40
kbaegisappropriately02:40
mark-caseyare those special? like # Completed by ...   # Generated by?02:41
kbaegisThey shouldn't be, but possibly :)02:41
kbaegisIt's saying it fails on the first line with that02:41
kbaegisLast line, line 3602:41
kbaegishttp://hastebin.com/okurusiref.avrasm02:41
*** g3ek has quit IRC02:42
mark-caseyis the localhost interface named differently on Gentoo? look at the stacktrace at the top of the second-to-last paste02:43
*** haplo37_ has quit IRC02:43
mark-caseythat trace at least shows the same "Error in agent loop. Devices info"02:43
*** haplo37 has quit IRC02:43
mark-caseyoh, n/m. I see. that's iptables_manager exploding02:44
mark-caseyso of course its the same02:44
kbaegisYeah02:46
kbaegisIt says line 3602:46
kbaegisWhich is the first one with a hash comment/escape02:46
kbaegisWhat file is that reading?02:46
mark-caseydunno. but I wonder if it's just choking on the COMMIT and the error is in the commands staged above02:47
mark-caseyI think you're missing the command ipset02:48
mark-caseyhttp://heavenkong.blogspot.com/2016/04/resolved-mitaka-linux-bridge-agent.html02:49
mark-caseyhrm... except, isn't that happening inside a container?02:49
*** yuanying has quit IRC02:50
kbaegisYes02:52
kbaegisIncidentally, the hypervisor doesn't have ipset02:53
kbaegisHypervisor/docker host whatever :)02:54
kbaegisNice find02:54
kbaegistyvvvm02:54
mark-caseykbaegis: ty. must either be that or perhaps centos' ipset not running when container is on Gentoo02:54
sdakertnetlink interface02:54
kbaegisI mean maybe different versions of the linux kernel02:55
sdakeioctl interface02:55
sdakecould be different02:55
kbaegisShouldn't break it like that though02:55
sdakehere is the deal02:55
mark-caseyheh. the most common failure building centos on ubuntu is for httpd to not install ;?02:55
sdakea number is assigned in a header somewhere02:55
mark-casey:/02:55
sdakethe kernel compiles that number02:55
sdakesomeone changes the order of how the number is passed or the nubmer itself02:55
sdakebam, you just broke container portability02:56
sdakekernel developers are doing this02:56
sdakeand even something inaquaious such as a change in behavior (such as bug removal) could change the behavior of the underlying libraries02:56
sdake10's of layers of code between openstack and the kernel on the host os02:56
sdakeanything out of alignment - bad things happen02:57
kbaegisYou're talking about mknod numbers?02:57
sdakethis is one type of magic number but those are fixed02:57
sdakei am talking about rtnetlink and ioctl interfaces02:58
sdakethe underlying c interfacess in the kernel02:58
sdakethere are other interfaces as well02:58
sdakedbus02:58
kbaegisI still need to read up on those02:58
kbaegisYeah, gentoo 4.8 w/ sysvinit could be problematic02:58
kbaegiswho knows :)02:58
sdakethe problem with container portability is the APIs change ;)02:58
sdakethats why when you buy software, its compiled  for a specific distro02:59
sdakeor if you download softwrae, you compiel it for that specific distro02:59
*** fragatina has joined #openstack-kolla03:00
mark-caseysdake: what's the current thought on coreos in kolla?03:01
mark-caseyI got prechecks/deploy and pulled up horizon the other day... but it's whole thing is to have next-to-nothing installed and bring everything in via container03:02
mark-caseyubuntu is cross building on it now, but seems fragile03:02
mark-caseyerr... I assume it fragile for the convo just now03:03
kbaegisThe compiler checks and catches that though right?03:03
*** fragatina has quit IRC03:04
mark-caseykbaegis: starting to guess a bit here, but centos is installing a binary bit for bit to disk... may not know it 'splodes until it is later run03:05
kbaegisRight, but how about source?03:08
kbaegisThat seems to work for me :)03:08
mark-caseyyes, I think if you had tools like that compiling from source hacked into container build it would be more compatible with the running kernel (I think). whether that is a good idea is another matter03:09
kbaegisWell, no one ever accused my style of system management of being a good idea :)03:11
kbaegisIt's GREAT experience for break/fix though03:11
mark-caseyfunny, me either :D03:11
*** daneyon has joined #openstack-kolla03:14
sdakemark-casey no idea on coreos03:16
sdakemark-casey i'd sort of like to implement it03:16
sdakemark-casey but the portability is an issue if coreos provides no userspace packaging03:16
sdakewe could do coreos from source of course03:16
mark-caseyaren't non-openstack packages still binary in that case?03:17
sdakenot if coreos provides them03:17
mark-caseynot in the least. it doesn't even have a package manager03:17
sdakeor they are binary - but in a compatible way03:17
sdakeyes I know03:17
kbaegisIs coreos bsd licensed?03:17
sdakeno idea on license03:18
mark-caseynot sure. but it is based on gentoo.03:18
mark-caseyI don't even think they ship a compiler03:18
sdakeoh well no compiler would be nog ood03:18
*** satya has joined #openstack-kolla03:18
*** daneyon has quit IRC03:18
*** thumpba has joined #openstack-kolla03:19
mark-caseywell... it's passing so far with ubuntu containers. I'll give a holler if I get a vm running normally but I'm now rather scared of supporting it and wish I'd checked before heh03:19
duonghqsdake: it seem that nobody take care the #322384 commit?03:22
duonghqhttps://review.openstack.org/#/c/322384/03:23
patchbotduonghq: patch 322384 - kolla - Check 127.0.1.1 in /etc/hosts on Ubuntu03:23
*** satya has quit IRC03:23
*** diogogmt has quit IRC03:28
*** mark-casey has quit IRC03:30
*** sdake has quit IRC03:34
*** zhurong has quit IRC03:35
*** zhurong has joined #openstack-kolla03:36
*** dave-mccowan has quit IRC03:38
duonghqPavo, kbaegis: now I got Horizon 500 too03:39
duonghqlol03:39
Pavolol03:39
Pavowelcome to the club03:41
duonghqPavo: do you get out of this error?03:42
Pavonop03:42
Pavonope03:42
duonghqI guess that I should rollback to find some luck03:42
Pavohow do you rollback?03:43
duonghqjust check out horizon docker and horizon ansible some commit03:43
duonghqif I have enough luck03:43
*** caowei has joined #openstack-kolla03:45
duonghqPavo: https://bugs.launchpad.net/searchlight/+bug/1612268 sound familiar?03:49
openstackLaunchpad bug 1612268 in OpenStack Search (Searchlight) "searchlight-ui settings.py out of date" [Undecided,Fix released]03:49
*** yuanying has joined #openstack-kolla03:49
Pavoyeap03:49
openstackgerritLeon Zachery proposed openstack/kolla: Simplify install process for faster quickstart execution  https://review.openstack.org/35618103:51
*** yuanying has quit IRC03:55
*** rminmin has joined #openstack-kolla04:01
*** huikang has quit IRC04:01
*** kbaegis has quit IRC04:02
*** coolsvap has joined #openstack-kolla04:04
*** huikang has joined #openstack-kolla04:11
*** zhurong has quit IRC04:14
*** zhurong has joined #openstack-kolla04:16
*** yuanying has joined #openstack-kolla04:16
Pavoare the setup scripts in kolla/tools suppose to get the nodes ready for openstack or for kolla?04:24
duonghqPavo: seem that for Kolla04:27
Pavooh ok04:28
Pavocould be very useful to make get it ready for target nodes04:28
*** unicell has joined #openstack-kolla04:30
*** unicell has quit IRC04:31
*** unicell has joined #openstack-kolla04:32
*** unicell has quit IRC04:34
*** unicell has joined #openstack-kolla04:34
Pavowhat was that heka cmd again to check logs04:36
Pavofinish the deployment and seems horizon still broke04:37
Pavoand rabbitmq container restarting04:37
PavoERROR: epmd error for host 192: badarg (unknown POSIX error)04:38
*** unicell has quit IRC04:44
openstackgerritDuong Ha-Quang proposed openstack/kolla: Add guide to auto mount /run as shared  https://review.openstack.org/35622204:44
duonghqPavo: can you paste the rabbitmq log, it is quite critical04:45
Pavoyeah trying to04:46
Pavonothing under /var/lib/docker/volumes/kolla_logs/_data/rabbitmq/04:47
*** unicell has joined #openstack-kolla04:47
Pavodocker logs show this https://paste.pound-python.org/show/v0gXwTUhSkE8gyYLhypS/04:48
*** jtriley has quit IRC04:51
openstackgerritDuong Ha-Quang proposed openstack/kolla: Add guide to auto mount /run as shared  https://review.openstack.org/35622204:57
*** huikang has quit IRC05:03
Pavook going to bed, will try some more tomorrow05:04
Pavonight05:04
duonghqhttp://lists.rabbitmq.com/pipermail/rabbitmq-discuss/2014-March/034269.html05:04
duonghqnight Pavo05:04
*** yuanying_ has joined #openstack-kolla05:29
*** yuanying has quit IRC05:29
openstackgerritDuong Ha-Quang proposed openstack/kolla: Fix guide formating errors  https://review.openstack.org/35623505:36
*** thumpba has quit IRC05:40
*** unicell1 has joined #openstack-kolla05:43
*** unicell has quit IRC05:43
*** jtriley has joined #openstack-kolla05:48
*** thumpba has joined #openstack-kolla05:51
*** jtriley has quit IRC05:53
*** thumpba has quit IRC05:56
*** daneyon has joined #openstack-kolla05:56
*** daneyon has quit IRC06:01
*** gfidente has quit IRC06:18
*** egonzalez90 has joined #openstack-kolla06:28
*** egonzalez has joined #openstack-kolla06:33
*** egonzalez90 has quit IRC06:36
*** egongu90 has joined #openstack-kolla06:36
*** caowei has quit IRC06:36
*** egonzalez has quit IRC06:40
*** caowei has joined #openstack-kolla06:41
duonghqkbaegis: do you got ssh unreachable error when deploy multinode06:41
*** egonzalez has joined #openstack-kolla06:41
*** dasTor has joined #openstack-kolla06:44
*** caowei has quit IRC06:45
*** caowei has joined #openstack-kolla06:45
*** caowei has quit IRC06:45
*** egongu90 has quit IRC06:45
*** caowei has joined #openstack-kolla06:46
duonghqcoolsvap:  do you got ssh unreachable error when deploy multinode06:46
coolsvapduonghq: i have not deployed multinode recently06:47
duonghqthask06:48
*** jtriley has joined #openstack-kolla06:48
*** egonzalez has quit IRC06:49
*** Jeffrey4l has joined #openstack-kolla06:49
openstackgerritDuong Ha-Quang proposed openstack/kolla: Add guide to auto mount /run as shared  https://review.openstack.org/35622206:51
*** thumpba has joined #openstack-kolla06:52
*** belmoreira has joined #openstack-kolla06:53
*** jtriley has quit IRC06:53
duonghqDaviey do you got ssh unreachable error when deploy multinode06:55
duonghqmewald1: are you there06:56
*** b_bezak has joined #openstack-kolla06:56
*** thumpba has quit IRC06:56
duonghqmntdevops: has you deployed multinode?06:59
*** gfidente has joined #openstack-kolla07:00
duonghqcoolsvap: it seem that in https://review.openstack.org/#/c/322384/ V.Hosakote does active for a while07:06
patchbotduonghq: patch 322384 - kolla - Check 127.0.1.1 in /etc/hosts on Ubuntu07:06
duonghqcan I take over07:06
openstackgerritzhongshengping proposed openstack/kolla: Fix service_type of mistral  https://review.openstack.org/35627107:08
coolsvapduonghq: seems like it, can you ask on the review and wait for couple of days ?07:09
duonghqcoolsvay: okay07:11
*** b_bezak has quit IRC07:17
*** bootsha has joined #openstack-kolla07:19
*** athomas has joined #openstack-kolla07:24
*** b_bezak has joined #openstack-kolla07:24
*** b_bezak has quit IRC07:29
*** b_bezak has joined #openstack-kolla07:35
mntdevopsduonghq: not yet07:39
duonghqthanks07:39
mntdevopswork projects in the way07:39
mntdevopswhy, what's up07:39
mntdevopsif you're getting ssh unreachable, that's an ansible issue07:41
mntdevopsadd a -vvvv right after the "ansible-playbook" command in question07:41
mntdevopsand rerun07:41
mntdevopsheaded to sleep07:42
mntdevopsttyl07:42
openstackgerritzhongshengping proposed openstack/kolla: ironic.conf file missing enabled_drivers info  https://review.openstack.org/35629007:44
*** daneyon has joined #openstack-kolla07:45
*** caowei has quit IRC07:47
*** jtriley has joined #openstack-kolla07:49
*** daneyon has quit IRC07:49
*** thumpba has joined #openstack-kolla07:52
openstackgerritDuong Ha-Quang proposed openstack/kolla: Add guide to auto mount /run as shared  https://review.openstack.org/35622207:55
*** jtriley has quit IRC07:56
*** thumpba has quit IRC07:57
*** thumpba has joined #openstack-kolla08:01
*** ad_rien_ has joined #openstack-kolla08:06
*** thumpba has quit IRC08:06
*** coolsvap is now known as coolsvap_08:09
*** Serlex has joined #openstack-kolla08:14
*** belmoreira has quit IRC08:18
*** bootsha_ has joined #openstack-kolla08:23
*** bootsha has quit IRC08:24
*** matrohon has joined #openstack-kolla08:26
*** anbehl has joined #openstack-kolla08:35
openstackgerritJeffrey Zhang proposed openstack/kolla: Bump the ansible version to 2.1.1.0 in kolla-toolbox  https://review.openstack.org/35631108:39
rstarmerFor those that are interested, I've created an ansible script that seems to be fairly reasonable at getting the base Kolla environmet built (and works reasonably well on centos and ubuntu systems). https://github.com/rstarmer/openstack-kolla-ansible08:43
*** jtriley has joined #openstack-kolla08:51
openstackgerritJeffrey Zhang proposed openstack/kolla: Move the keystone_*_url variable from common role to group vars  https://review.openstack.org/35631908:56
openstackgerritMd Nadeem proposed openstack/kolla: Added Dockerfile for congress  https://review.openstack.org/30562608:57
*** jtriley has quit IRC08:57
*** thumpba has joined #openstack-kolla09:02
pbourkecoolsvap_: ping09:06
*** gfidente has quit IRC09:07
openstackgerritMd Nadeem proposed openstack/kolla: Added Dockerfile for congress  https://review.openstack.org/30562609:08
*** thumpba has quit IRC09:08
pbourkeany core team around this morning09:08
pbourkecould use some reviews09:08
openstackgerritMerged openstack/kolla: Add jq  https://review.openstack.org/35500309:08
*** gfidente has joined #openstack-kolla09:26
*** bootsha_ has quit IRC09:28
*** vbel has quit IRC09:28
*** rminmin has quit IRC09:29
*** anbehl has quit IRC09:29
*** bootsha has joined #openstack-kolla09:30
openstackgerritMd Nadeem proposed openstack/kolla: Added Dockerfile for congress  https://review.openstack.org/30562609:35
*** jtriley has joined #openstack-kolla09:52
*** HyperJohnGraham has quit IRC09:56
*** openstack has joined #openstack-kolla10:16
*** sdake_ has quit IRC10:18
*** sdake_ has joined #openstack-kolla10:19
*** sdake has quit IRC10:19
sdake_did anyone fix the horizon problem10:19
sdake_i was in the midst of looking into it10:19
sdake_before ptfoing10:19
sdake_pbourke did you do any work on horizon?10:20
sdake_Jeffrey4l ?10:20
pbourkewhich one10:20
pbourkethe css on osic prob?10:20
sdake_moment log will helpl10:21
Jeffrey4lsdake_, yep10:21
Jeffrey4li fixed the horizon issue10:21
Jeffrey4lsdake_, pbourke https://review.openstack.org/35523210:22
pbourkeJeffrey4l: sdake_: any way we can tackle the gates before merging much more patches10:23
*** Mr_Broken has joined #openstack-kolla10:23
pbourkehttps://review.openstack.org/#/c/353942/10:24
patchbotpbourke: patch 353942 - kolla - Fix bandit gate jobs10:24
pbourkehttps://review.openstack.org/#/c/355808/10:24
patchbotpbourke: patch 355808 - kolla - Fix Neutron bootstrap failure due to missing fixtu...10:24
Mr_BrokenHey guys10:24
Mr_Brokenanyone had simmiliar issue during deployment ?10:24
Mr_Brokenhttp://paste.openstack.org/show/558995/10:24
Mr_Brokenrabbitmq keeps failing me :/10:24
Mr_BrokenI was thinking ntp issue, but have the same ntp server setup on all hosts10:25
Mr_Broken(its stable/mitaka , ubuntu/binary, multinode topology )10:25
sdake_moment let me look at gates10:26
sdake_didn't know they were busted10:26
pbourkeMr_Broken: im not familiar with that error but I would start by running the getent command on your control nodes10:26
pbourkeMr_Broken: see what it outputs and why its not matching up to what the deploy expects10:27
sdake_Jeffrey4l that fix - that fixes the panel backtrace?10:27
Jeffrey4lhttps://review.openstack.org/#/c/355808/  this is a bug from neutron and it is fixed.10:27
patchbotJeffrey4l: patch 355808 - kolla - Fix Neutron bootstrap failure due to missing fixtu...10:27
Jeffrey4lplease do not merge it.10:27
sdake_Jeffrey4l so abandon change then?10:28
Jeffrey4lsdake_, yep. please.10:28
sdake_you can abandon10:28
sdake_;)10:28
*** bootsha has quit IRC10:28
Jeffrey4lthe deploy gate is successful now.10:28
Jeffrey4lno fixture issue.10:28
sdake_oh pbourke is the patch author10:28
sdake_you can still abandon it but pbourke really should10:28
openstackgerritPaul Bourke proposed openstack/kolla: Add force flag to cleanup-images  https://review.openstack.org/35636410:29
Jeffrey4li -2 on it with some comments.10:29
Mr_Broken@pbourke: thanks m8, my /etc/hosts were cleaned after reboot by cloud-init :P10:30
pbourkethanks Jeffrey4l have abandoned10:30
Jeffrey4lthanks.10:30
pbourkeJeffrey4l: can you check the bandit patch?10:31
Jeffrey4lok.np10:31
sdake_Jeffrey4l read this log http://eavesdrop.openstack.org/irclogs/%23openstack-horizon/%23openstack-horizon.2016-08-16.log.html#t2016-08-16T19:49:5810:32
sdake_there is a link to locals_conf.j2 line 8010:32
sdake_several horizon experts have said we are doing it wrong10:33
* Jeffrey4l is checking10:33
sdake_from ust now: [03:25:29]  <sdake_>looks like regression on our end..10:34
sdake_[03:25:39]  <sdake_>we have no ci for horizon unfortunately :(10:34
sdake_[03:26:07]  <@robcresswell>That looks like a different issue no?10:34
sdake_[03:26:25]  <@robcresswell>The issue you have will be caused by L80 in that local_settings.j210:34
sdake_[03:26:36]  <@robcresswell>Overwriting that dict is a no-no :)10:34
sdake_[03:27:45]  <+tsufiev>+110:34
sdake_[010:34
sdake_i got impressio nline 80 should be entirely removed10:35
Jeffrey4lhmm no idea about that dict.10:35
sdake_are you in openstack-horizon?10:35
sdake_#openstack-horizon10:35
Jeffrey4li am in10:36
*** bootsha has joined #openstack-kolla10:37
*** bootsha has quit IRC10:39
sdake_cool so durign the day10:41
sdake_there were 5+ peopel complaing about that particular problem10:42
sdake_if its as smple as deleting some lines10:42
sdake_shouldl make it happen asap10:42
sdake_unfortunately my test box is being redeploeyd atm10:42
Jeffrey4lsdake_, how the issue is happened? what the people did caused this issue?10:42
sdake_no idea why it just started happening10:44
sdake_not sure what the scenario was - it hink horizon was backtracing on startup10:44
sdake_with centos binary10:44
sdake_maybe it was backtracing during runtime10:44
sdake_it wasn't clear to me10:45
sdake_the other problem people constantly coplain about - someone has fixed!10:45
sdake_https://review.openstack.org/#/c/356181/10:45
patchbotsdake_: patch 356181 - kolla - Simplify install process for faster quickstart exe...10:45
sdake_pbourke Jeffrey4l can you both review that pls10:45
Jeffrey4lok10:48
*** Mr_Broken has quit IRC10:53
*** jtriley has joined #openstack-kolla10:53
*** Mr_Broken has joined #openstack-kolla10:53
sdake_pbourke arey ou sure about the operation from inside git repo?10:53
*** Mr_Broken has joined #openstack-kolla10:53
pbourkesdake_: which one10:53
sdake_pbourke i am 99% sure that doen't work as you claim10:53
sdake_your first comment on that last review10:53
pbourke'pip install .' ?10:54
sdake_kolla (atleast used to) always default to the pip installed version even if working out of a gi trepo10:54
pbourkeoh10:54
pbourkeit depends on the commands you use10:54
*** duonghq has quit IRC10:54
pbourkeif you use tools/kolla-ansible it use the git repo10:55
pbourkeif you use 'kolla-ansible' it uses the installed location10:55
pbourkethat's my experience10:55
sdake_can you double check that10:55
pbourkeok10:55
sdake_from the past, and constant support in channel, people run into problem where their git content (such as dockerfiles and ansible) are not being used inside the git repo10:56
sdake_the solution is pip remove kolla10:56
*** bootsha has joined #openstack-kolla10:56
sdake_kolla-ansible binary and python runtime work correctly - but ansible and dockerfilels not so much10:57
pbourkesdake_: http://paste.openstack.org/show/558997/10:57
pbourkelook at the location of site.yml that's being used in each case10:57
*** Mr_Broken has quit IRC10:58
*** jtriley has quit IRC10:58
sdake_yup10:58
sdake_you convinced me kolla-ansible is working correctly10:58
sdake_what about build?10:58
pbourkesdake_: same behaviour10:58
pbourkesdake_: just tested I wont bother pasting10:58
sdake_that bug must have recenty been fixed11:00
sdake_i wonder why we see the tagging problems11:00
sdake_3.0.0 gets tagged if pip installed11:01
sdake_even when working rom a stable/mitaka branch11:01
sdake_from git11:01
sdake_can you verify that is not the case?11:01
* sdake_ needs to go setup his testbed11:01
sdake_perhaps the python runtime is not running from the git cwd11:02
sdake_well thanks pbourke - that solves alot of my problems :)11:06
sdake_pbourke i'll be back in a bit - need to finish ceentos install11:06
pbourkesdake_: ok cool11:06
sdake_i think the tagging problem either needs to be fixed or those docs can go in sort of as is11:06
sdake_but i need to verify there is actualy a tagging problem  :)11:07
pbourkeyeah Im not quite following you on what that problem is11:08
pbourkeis it in the gate or elsewhere11:08
pbourke?11:08
sdake_pbourke elsewhere11:11
sdake_pbourke here is the deal11:11
sdake_people follow the quickstart guide11:12
sdake_and then i tell them "ok now install stable branch"11:12
sdake_they install stable branch11:12
sdake_and the tags are 3..0.011:12
sdake_perhaps the issue is more simply they are not running the commands from the tools directory11:12
sdake_rather not install stable branch11:13
pbourkehmm11:13
sdake_i mean check otu stable branch11:13
sdake_while master branch is installed11:13
sdake_sorry brain wrming up11:13
sdake_warming up11:13
sdake_if you check out stable branch while master branch is installed, a build will produce 3.0.0 tags11:13
sdake_but i am not sure if its only when using kolla-build or also when using tools/build.py11:13
sdake_need testbed :)11:14
sdake_brb11:14
pbourkewell if they checked out the stable branch it should be the same11:14
pbourkecode in both places11:14
*** ad_rien_ has quit IRC11:15
pbourkethe issue seems to be the source of all my pain in life11:15
pbourkepbr11:16
openstackgerritMerged openstack/kolla: Fix the memcache location value in horizon local settings  https://review.openstack.org/35523211:19
openstackgerritMerged openstack/kolla: Add guide to auto mount /run as shared  https://review.openstack.org/35622211:20
*** daneyon has joined #openstack-kolla11:21
sdake_pbourke stable branch is different htten master11:21
sdake_centos installing11:21
sdake_i should know in about 10 mins :)11:21
pbourkesdake_: the issue is pbr is returning 3.0.011:21
pbourkesdake_: likely from the latest git tag its finding11:22
pbourkesdake_: pbr is the worst thing ever, its never worked correctly for me11:22
sdake_but correct content is used?11:22
pbourkeyes11:22
sdake_pbr returns 3.0.0 even without a  pip install of master?11:23
pbourkeyes11:24
* sdake_ GROANS11:24
*** sdake_ is now known as sdake11:24
sdakedaviey had a solution to fix the pbr problem using "current"11:24
sdaketo represent master11:25
sdakenot sure how he planned  to solve the stable branches11:25
sdakeok well here is the deal - I spend like 3 hrs a day explaining how to workaround this problem11:25
*** daneyon has quit IRC11:25
sdakeI asked leon to look at one of our irc logs where it was explained and turn it into docs11:25
sdakeso I can see how he got to where he is11:26
sdakei'd like suggestions for doc fixes in the interim11:26
sdakethat leon can integrate - simple as a --tag?11:26
*** jtriley has joined #openstack-kolla11:27
*** bootsha has quit IRC11:27
sdakeit may take awhile to sort out this actual pbr problem11:27
*** bootsha has joined #openstack-kolla11:27
sdakeand endless days of answering the same questions over and over is not a good use of our time :)11:27
pbourkesdake: maybe im wrong, a fresh install of stable in a virtualenv is showing tag 2.0.311:31
*** jtriley has quit IRC11:32
pbourkesdake: tbh, Im staying out of pbr, there are clearly some people out there who grok it but im not one11:32
sdakepbourke - house on fire - lets put out the fire first - which is via doc changes11:32
sdakemy box shoudl be up in about 5 mins11:33
sdakei'll let daviey sort out pbr - he seems to understand it :)11:33
sdake(i.e. the long term fix)11:33
sdakeso just to clarify - content is always run from either git location or global location depending on where tools are run11:34
sdakeso this is just a tag return issue?11:34
sdakeor your uncertain now?11:34
pbourkeim pretty confident content is depending on where tools are run11:35
sdakewht about kolla/kolla/*py11:35
pbourkeso yeah its just a pbr issue11:35
sdakethat is where the tag is hardcoded11:35
pbourkethe tag isn't hardcoded - it's figured out with pbr magic11:36
*** bootsha has quit IRC11:37
Jeffrey4lpython -c 'import pbr.version; print(pbr.version.VersionInfo("kolla").release_string())'11:38
Jeffrey4lpython -c 'import pbr.version; print(pbr.version.VersionInfo("kolla").cached_version_string())'11:38
Jeffrey4lhere is the pbr magic11:38
Jeffrey4lkolla using cached_version_string now. I think we should move to the release_string11:39
sdakeits hardcoded somewhere - pretty sure11:40
sdakelet me check11:40
*** narasimha_SV_ has joined #openstack-kolla11:42
narasimha_SV_after deploying ironic using kolla11:42
narasimha_SV_when i try to do pxe boot of a baremetal11:42
narasimha_SV_http://paste.openstack.org/show/559000/11:42
narasimha_SV_i am getting this issue11:42
*** kbaegis has joined #openstack-kolla11:42
narasimha_SV_i dont see a folder called /var/lib/ironic in ironic-conductor container11:42
sdakehmm i thought there was one in common/config.py11:43
sdakebut git show shows no such change about that11:43
* sdake needs to do more reviewing...11:44
kbaegisMorning11:44
sdakeJeffrey4l mind giving me a tldr on the delta between release_string and cached_version_string11:44
*** bootsha has joined #openstack-kolla11:45
sdakenarasimha_SV_ ironic implementation is on the way11:46
*** dave-mccowan has joined #openstack-kolla11:46
sdakenarasimha_SV_ - intel cats got it working a few days ago11:46
sdakenarasimha_SV_ not sure who exactly - one of sean-k-mooney teammates11:46
wznoinskmiau11:46
sdakenarasimha_SV_ it will still be tech preview in newton11:46
sdakebut it hould be working :)11:47
wznoinskor english: meow11:47
sdakebut it is not workign now11:47
sdakehey wznoinsk11:47
wznoinskhi sdake11:47
*** dwalsh has joined #openstack-kolla11:47
wznoinskI plan to get my working ironic tested on master in next few days, I'm about a click away from giving myself a baremetal to do it ;-)11:48
sdakewznoinsk hot - apologies for not recalling who does the work11:49
wznoinsknarasimha_SV_: https://bugs.launchpad.net/kolla/+bug/161175811:49
openstackLaunchpad bug 1611758 in kolla mitaka "ironic_conductor - Permission denied: '/var/lib/ironic'" [High,Confirmed] - Assigned to Waldemar Znoinski (wznoinsk)11:49
sdakewznoinsk there are a whole lotta poeple working on this project ;)11:49
wznoinsksdake: no worries, it's my job to get my name recognized11:50
sdakeit just got recognized :)11:50
kbaegisYes it did :)11:50
wznoinskthanks guys11:50
kbaegisVery cool work11:50
wznoinsknarasimha_SV_: let me know if you have further ironic issues in kolla, if you can't find them at https://bugs.launchpad.net/kolla (I've reported a couple and my colleagues did too) then ping me11:51
sdakeJeffrey4l - i rtfm'ed and can't find any description of those two methods11:52
sdakeJeffrey4l - reading the code will be painful - mind giving me a  tldr ;)11:52
*** jeh has quit IRC11:54
narasimha_SV_Thanks wznoinsk11:54
narasimha_SV_can I have your personal mail id11:55
sdakenarasimha_SV_ - mailing list11:55
sdakenarasimha_SV_ all discussions should be public on mailing list - its part of the 4 opens - a  foundation of openstack guiding principles11:55
wznoinsknarasimha_SV_: I don't mind sharing knowledge here or on the mailing list11:55
sdakeyup 4 opens require recording of all knowledge transfer in essence11:56
sdakeirc, mailing list, team meetings, those are all good to go11:56
coolsvap_hi sdake pbourke morning11:56
kbaegissdake horizon started working last night. Was that your doing?11:56
narasimha_SV_no no not like that I just want to talk11:56
sdakekbaegis Jeffrey4l is sorting out the proboel mthe openstack-horizon folks pointed out11:57
sdakewhether it works or not, it is broken atm :)11:57
*** jeh has joined #openstack-kolla11:57
*** jeh has quit IRC11:57
*** jeh has joined #openstack-kolla11:57
coolsvap_just came from a PTO today, sorry for the delayed response11:57
pbourkewelcome back coolsvap_11:58
* coolsvap_ just busy with some other work11:58
sdakecoolsvap_ all good - i was on pto friday->modnay :)11:58
kbaegisJeffery4l Thanks for the new local_settings!11:58
*** ad_rien_ has joined #openstack-kolla11:58
*** Mr_Broken has joined #openstack-kolla11:58
coolsvap_sdake: yeah, give me couple of hours, I will be bit more active just around the meeting time and onwards11:58
sdakecoolsvap_ roger - pbourke working on a rallly script of some sort11:58
* sdake behind11:59
sdakecoolsvap_ so we can have repeatable runs of rally - coould probably use your help on conig there11:59
sdakeconfig there11:59
*** ad_rien_ has quit IRC12:00
coolsvap_sdake: roger that12:00
sdakecentos finally up12:00
*** ad_rien_ has joined #openstack-kolla12:00
sdakeoff to try Jeffrey4l 's suggestion bbiaf12:00
coolsvap_are we having any config issues with rally deployment on the node?12:00
*** sdake_ has joined #openstack-kolla12:01
pbourkecoolsvap_: none that I know of12:01
pbourkecoolsvap_: give me a shout when you have a minute and we'll have a look at where its at12:02
Davieypbourke: Hey.. Who found that the VLAN issue was kernel releated?12:02
pbourkeDaviey: me, inc0 and Jeffrey4l12:02
*** bjolo has joined #openstack-kolla12:03
*** coolsvap_ is now known as coolsvap12:03
*** sdake has quit IRC12:05
*** sdake_ is now known as sdake12:05
coolsvappbourke: ack12:05
*** rhallisey has joined #openstack-kolla12:06
sdakeDaviey can you give me a tldr on the delta between these two mthods - docs show nothing12:07
sdake04:38:45]  <Jeffrey4l>python -c 'import pbr.version; print(pbr.version.VersionInfo("kolla").release_string())'12:07
sdake[04:38:50]  <Jeffrey4l>python -c 'import pbr.version; print(pbr.version.VersionInfo("kolla").cached_version_string())'12:07
sdake[04:38:57]  <Jeffrey4l>here is the pbr magic12:07
sdake[04:39:16]  <Jeffrey4l>kolla using cached_version_string now. I think we should move to the release_string12:07
*** rhallisey_ has joined #openstack-kolla12:08
sdakemorning rhallisey12:09
rhallisey_morning12:10
*** rhallisey has quit IRC12:12
*** rhallisey_ is now known as rhallisey12:13
sdakeJeffrey4l Daviey - looks like tag is correct in either case without master installed -> http://paste.fedoraproject.org/409562/14714359/ -> http://paste.fedoraproject.org/409562/1471435912:13
NachoDuckHi, following the instructions here - http://docs.openstack.org/developer/kolla/swift-guide.html#rings it seems to be searching for an image at docker.io/kolla/centos-binary-swift-base which doesn't exist?12:15
sdakeNachoDuck - working on that problem now with a docs fix12:16
sdakeNachoDuck - mind running a few commands - i can get you rollling12:16
sdakepbourke ^^ see what i'm talking about ;)12:17
NachoDucksdake: Sure thing, I'm trying this multinode btw12:17
sdakeNachoDuck - run pip show kolla12:17
pbourke:)12:17
NachoDucksdake: https://gist.github.com/anonymous/7a5c4cdf764cbd56c0e876dfa18605c212:18
sdakeNachoDuck are you doing an eval or want to develop for kolla?12:18
NachoDuckeval12:18
sdakenice you hae teh stable branch installed12:18
sdakethats a new one :)12:18
NachoDuckheh :)12:18
sdakeok our code is incompatible with pbr at present12:18
sdakewe are sorting that out - but want to provide doc fix in short term to put out the fire ;)12:19
sdakecan you run docker images -> paste12:19
NachoDuckhttps://gist.github.com/anonymous/3acd0b30ca21f8c2f3395c8f741cc9ad12:20
sdakeset openstack_version: 2.0.2" in globals.yml12:20
sdakeopenstack_version: "2.0.2" inglobals.yml12:21
NachoDuckYep already had that set12:21
NachoDuckah wait12:22
sdakeDaviey the problem I see with the current mechanism you propose is around the stable branches12:23
sdakeDaviey - in one case people can build their own images - current would work - in another case people pull from ddocker hub - in which case current would not work12:23
NachoDucksdake: Ok done, had confused it with openstack_release: "2.0.2"12:23
sdakesorry openstack_releae12:23
sdakenot version12:23
NachoDuckah, well its set either way12:23
sdakedo you have openstack_releae: "2.0.2"12:23
NachoDuckyep12:23
sdakepaste your globals.yml pls ;)12:23
sdakeNachoDuck -  did you ahe a running install previously?12:24
NachoDucksdake: Yes got it working fine eventually with Ceph but I'd like to include Swift in our eval too12:25
NachoDuckhttps://gist.github.com/anonymous/37afdff3f91498b76c50641926acd56f12:25
sdakegot it12:25
sdakemoment12:25
sdakethis may be a different problem12:26
NachoDuckOk no worries12:26
sdakeNachoDuck - not sure why your trying to pull swift-base - tag is set in dockerhub: https://hub.docker.com/r/kolla/centos-binary-swift-base/tags/12:28
sdakeNachoDuck can you paste your deploy operation for me?12:28
NachoDuckSure, one sec12:28
* sdake feels like a squirrel sometimes...12:29
NachoDuckMight be a mistake I made when I chopped this together as included that add commands from Oracle's documentation to facilitate the multinode deployment - https://gist.github.com/anonymous/79d9a8e48526d9e9a181fdca151512ce12:29
sdakeoh - that is where your getting the error - when running that script?12:30
sdakepbourke didn't we get rid of ringbuilder?12:31
sdakerather you iirc ;)12:31
NachoDuckyeh12:31
pbourkesdake: yeah12:32
sdakethe docker run commands are missing tags NachoDuck12:32
pbourkeis that causing issues12:32
sdakepbourke - ithink there must have been a docimpact there12:32
sdakepbourke - NachoDuck is running a script in oracle's documentation that depends on it12:33
sdakepbourke - https://gist.github.com/anonymous/79d9a8e48526d9e9a181fdca151512ce12:33
pbourkesdake: actually it seems to still be referenced in our doc12:33
pbourkemy bad :/12:33
sdakepbourke - right doc impact ;)12:33
NachoDuckFor reference, its quite similar to what you have http://docs.oracle.com/cd/E73172_01/E73174/html/setup-swift.html12:33
pbourkeI better re-instate it12:33
pbourkeNachoDuck: that's a mistake by me, sorry. Will re-instate the script12:34
sdakeNachoDuck - yup - working on it ;)12:34
NachoDuckNo worries, thanks :)12:34
sdakeis the long term answer to remove that from the docs as well?12:34
sdakepbourke ^12:35
sdakepbourke - I recall seeing your change, but don't recall the rationale - but it seemed fine at the time12:35
pbourkesdake: I dont think so as it appears to be the easiest way to create rings12:35
pbourkesdake: I haven't looked at swift in ages12:35
sdakepbourke ya me either12:35
sdakepretty sure sbezverk looks at it regularly tho12:36
sdakeif our gate wasnt so leaky - we would knwo for sure ;)12:36
pbourkewait hang on12:36
pbourkewe're getting confused12:36
pbourkeswift-ring-builder is a swift command12:36
Jeffrey4lsdake, you need install kolla to make the pbr works or run the script in the kolla folder.12:36
pbourkethe script I removed is no longer used, and that patch hasn't even merged yet12:36
sdakepbourke thanks for clarification12:37
sdakeJeffrey4l - playing around with it - before chasing another nut :)12:37
pbourkeso NachoDuck, what exact error are you seeing?12:37
pbourkeNachoDuck: doing a lot of things at once, sometimes get wires crossed12:37
sdake[05:15:42]  <NachoDuck>Hi, following the instructions here - http://docs.openstack.org/developer/kolla/swift-guide.html#rings it seems to be searching for an image at docker.io/kolla/centos-binary-swift-base which doesn't exist?12:38
NachoDuckpbourke: This is the sort of output I get when running that script  - https://gist.github.com/anonymous/6a0c6e54244c1e366ff80f07794d2b8112:38
sdakeNachoDuck ya that script needs tags12:38
NachoDuckrightio12:39
sdakeor the docs do12:39
sdakeor both :)12:39
pbourkeNachoDuck: ok that's easy, yeah its what sdake said12:39
pbourkeNachoDuck: you need to tweak the vars at the top to match your environment12:39
pbourkedocker images | grep swift-base12:39
sdakepbourke - there is no tags in the vars12:39
pbourkethat also12:39
sdakeour documentaiton is wrong12:39
NachoDuckpbourke: gotcha, will see what I can do12:39
pbourkewe could probably write a playbook to do this12:40
sdakeprobably someday :)12:40
sdakeNachoDuck do you have neoug hto work with or need further guidance?12:41
sdaketag should be 2.0.212:41
sdakejust add :2.0.2 after each image name12:41
sdakein the docker run commands12:41
NachoDucksdake: Ok thanks, wasn't too sure. Will give it a go12:42
sdakeNachoDuck if you run into trouble - i'll be here12:42
*** jamesdenton has joined #openstack-kolla12:42
NachoDuckAwesome, thanks both12:42
sdakei guess that tells us nobody is using swift... :(12:44
sdakethat script and docs have been broken for months12:44
sdakecontext switching at 5am = ftl :(12:45
sdakeJeffrey4l http://paste.fedoraproject.org/409593/14714382/ -> http://paste.fedoraproject.org/409593/1471438212:50
sdakethat is with master installed12:50
sdakeit is showing 3.0.0 tags even on stable branch from pbr12:50
sdakewith both incantations12:51
Jeffrey4lsdake, so 1. install the kolla   2. checkout to mitaka   3 print the version?12:51
Jeffrey4lsdake, so 1. install the kolla master  2. checkout to mitaka   3 print the version?12:51
sdakethat is exactly what i did12:51
Jeffrey4lright?12:51
Jeffrey4lsdake, how did you installed the kolla?12:52
Jeffrey4lpip install .?12:52
sdakesudo pip install kolla/12:52
Jeffrey4lthat's it12:52
Jeffrey4lpbr load the kolla version from the python side-packages.12:52
Jeffrey4leven u change the kolla code base from master to mitaka. it do not affect the kolla version12:53
Jeffrey4lu can check by using `pip freeze | grep kolla`12:53
Jeffrey4lin the python env, u still have the kolla 3.012:53
sdakei am more concerned about the content that the tools run12:53
sdakesuch as the ansible and dockerfiles12:53
Jeffrey4lhmm?12:54
sdakei think pbourke confirmed the content was run was the correct content -12:54
sdakeif from git, running git content12:54
sdakeif from non-git dir, running system content12:54
pbourkeperhaps the version is a hole in the mechanism12:55
pbourkeas in it's the only part that comes from the installed version regardless12:55
sdakepossible - if we are certain the content is run correctlly from git :)12:55
Jeffrey4lyou can try pip install -e .12:55
Jeffrey4ladd the `-e` parameter.12:55
sdakei know pp -e will work12:55
Jeffrey4lOK.12:56
sdakebut pip -e doesn't work on some folks environments for whatever rason12:56
sdakemoment - running a tet12:56
sdaketest12:56
*** rstarmer has joined #openstack-kolla13:00
*** rstarmer has quit IRC13:00
sdakepython content run from git repo is run from git repo13:01
sdakei put a raise in build.py main in master installed version - which shoudl have triggered a crater13:01
sdakeso its simply an issue of pbr doing the wrong thing13:01
*** jtriley has joined #openstack-kolla13:03
openstackgerritJosh Lothian proposed openstack/kolla: Customizations for heka  https://review.openstack.org/34686113:04
openstackgerritJeffrey Zhang proposed openstack/kolla: Move to transport_url for rabbitmq configuration  https://review.openstack.org/35644913:04
sdakepower supplyy not working13:04
sdakebbiaf13:04
sdakeboy not really waht i needed today13:05
*** zhurong has joined #openstack-kolla13:05
*** jamesdenton has left #openstack-kolla13:05
sdakegot it13:06
sdakewiggling ftl13:06
sdakebad sign13:06
*** zhurong has quit IRC13:07
*** zhurong has joined #openstack-kolla13:09
sdakeDaviey - any idea how to fix this pbr issue?13:11
NachoDuckThe swift deployment appears to have gone smoothly, in case you were wondering. Thanks again :)13:11
*** coolsvap is now known as _coolsvap_13:11
sdakeNachoDuck was wondering - thanks for the confirmation!13:11
sdakeNachoDuck could you also confirm if its functiona lfor you?13:12
*** bootsha has quit IRC13:12
NachoDucksdake: Yep just going to start playing with it a bit now, have been able to create a container and upload. So far so good13:12
sdakethats good news :)13:12
sdakesince it looks like this code path hasn't been tested in a few months..13:13
sdakeour ci doesn't test it approprateily13:13
*** duonghq has joined #openstack-kolla13:14
NachoDuckAh I see, well perhaps testament to good work that it's still functional despite that13:14
sdakeNachoDuck thanks :)13:14
sdakeNachoDuck - we keep our default configs very minnimal or this exact reason13:14
sdakeNachoDuck just enough to work out of the box and nothign more13:15
sdakesometimes upstream changes config options - this is when things break13:15
*** bootsha has joined #openstack-kolla13:15
sdakeand sometimes master is plan broken in various parts of openstack ;-)13:15
sdakeplain13:15
NachoDucksdake: It's been refreshing to work with so far after looking at our other deployment options, I can't say I was looking forward to customising Heat templates and the like13:16
sdakei haven' tevaled other options for quite awhile13:17
sdakeits very time consuming13:17
sdakebut thanks fo the positive feedback!13:17
*** inc0 has joined #openstack-kolla13:17
NachoDuckYeah, it took me a while to arrive at this point. No problem!13:17
*** sean-k-mooney has quit IRC13:18
sdakeNachoDuck if I haven't already asked in the past - mind telling your top 3 pain points with kolla?13:18
inc0good morning13:22
sdakesup inc013:23
*** Guest52040 has joined #openstack-kolla13:23
duonghqmorning inc013:24
*** bootsha has quit IRC13:27
kbaegisgood morning13:28
kbaegisSo with the registry- even if docker images doesn't show anything (i.e. after a cleanup), those images will still be cached and available inside the registry w/ appropriate tags, correct?13:29
kbaegisIt will implicitly pull as long as kolla-build pushed the images there, right?13:29
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Glance bootstrap to create service/project/role  https://review.openstack.org/34621513:30
duonghqwhat do you mean "implicitly pull?13:31
kbaegiswhen I do a kolla-ansible deploy13:31
kbaegisIt checks the local docker images, else pulls from registry?13:31
duonghqyes13:31
kbaegisI have a kolla-build.conf which is tagging with "alpha", and I wanted to be sure about behavior13:31
kbaegistyvm13:31
NachoDucksdake: Sure, sorry all of these at the moment are related to docs, there might be more but I've been trying to get Kolla working for us for a while so I've probably forgot some :) To be honest once I got around these issues I've found very little issues with the deployment itself, which is good I suppose!13:33
NachoDuck1) Might just be me but maybe some of the basics is missing from the documentation that can be forgotten, it was a while before I thought of disabling selinux and the firewall and instead was chasing around what I assume were either misconfigurations on my part or issues with the version of the project I was using.13:34
NachoDuck2) Again with documentation some key points are missing in places, for example it wasn't until I happend to catch in here that I need to use Ansible 1.9 for a stable branch deployment and that tripped me up for a while13:34
NachoDuck3) Bit of a weak one but I might come up with something better later on - It wasn't clear to me for multinode whether or not I had to build my own images to begin with, so I wasted a bit of time there where I didn't have to either. The docs might be a bit too develop orientated in places I guess?13:34
*** narasimha_SV_ has quit IRC13:34
Davieysdake: Sorry, i've been distrated with meetings all morning13:35
*** bootsha has joined #openstack-kolla13:35
Davieysdake: Stable should be OK.  If kolla continues to build images for all tagged releases, then if i pip install kolla, it will work13:35
*** ad_rien_ has quit IRC13:35
Davieysdake: If i choose to install from git, stable/* - then i need to build my own images.  That seams like a reasonable compromise13:36
duonghqah, anybody try multinode deployment?13:36
*** caowei has joined #openstack-kolla13:36
Davieysdake: We should probably be supporting people installing from releases (both distro and pip), rather than from git?13:36
openstackgerritJeffrey Zhang proposed openstack/kolla: Sync the local_settings.j2 with horizon  https://review.openstack.org/35647113:37
NachoDuckduonghq: Yep, got it working eventually13:37
duonghqNachoDuck: Did you got ansible cannot established connection error?13:38
NachoDuckduonghq: That's new to me unfortunately I think. If it's just general ansible connection errors, make sure you've setup your public key auth?13:40
*** ad_rien_ has joined #openstack-kolla13:40
duonghqyes, I can ssh with public key13:40
duonghqI used ansible 1.9 before and does not get any error13:42
duonghqbut I havenot had much experience with ansible 2.x13:42
NachoDuckYou need to use 1.9 if you're running from stable iirc13:42
duonghqI use master13:42
duonghqjust Ansible error13:42
*** dwalsh has quit IRC13:42
*** dwalsh has joined #openstack-kolla13:45
NachoDuckI see, what's the full error message you get?13:46
duonghq: UNREACHABLE! => {"changed": false, "msg": "Failed to connect to the host via ssh.", "unreachable": true}13:48
duonghqlike this13:48
duonghqI google this13:48
duonghqi tried some result but cannot got it run13:48
*** sdake has quit IRC13:50
*** thumpba has joined #openstack-kolla13:52
NachoDuckOdd if you're able to connect with that same user using your key as that's pretty much what Ansible is doing anyway13:53
*** egonzalez90 has joined #openstack-kolla13:54
*** egonzalez90 has quit IRC13:54
Serlexhello, how may i change the timezone of the containers?13:56
*** egonzalez90 has joined #openstack-kolla13:57
*** b_bezak has quit IRC13:57
duonghqNachoDuck: I'm retrying13:57
*** huikang has joined #openstack-kolla13:58
*** lrensing_ has joined #openstack-kolla13:58
*** sdake_ has joined #openstack-kolla14:01
*** daneyon has joined #openstack-kolla14:03
sdake_NachoDuck - 1 - ya actually kolla runs with selinux but the version thing is a real problem we are trying to solve rapidly :) - 2 there is a review in the queue to fix this dependency list for stable vs nonstable branches - 3 yup hear ya docs are developer oriented14:04
sdake_NachoDuck i htink the key thing you point out is our docs are weak - which we know - and are working to fix :)14:04
*** Pavo has quit IRC14:04
*** bootsha has quit IRC14:05
sdake_Daviey the issue with supporting people only from releases rather then a git checkout is people sometimes want to use master (for example to join the kolla developer community)14:05
*** bootsha has joined #openstack-kolla14:06
sdake_people use master for other reasons as well14:06
*** Pavo has joined #openstack-kolla14:06
sdake_inc0 - they should really just start out everyone at level 70, no? :)14:07
inc0sdake_, well, first time off it's fun to go through story14:08
sdake_i guess buid your own images is a reasonable compromise14:08
inc0but I doubt there are much first timers around now14:08
*** daneyon has quit IRC14:08
sdake_not sure how to document that tho14:08
sdake_ya when they made it hard and then DOUBLED it, it was unbearable to get through cts 1-4 solo14:09
duonghqNachoDuck: when I retry at home, it's ok, tomorrow I'll recheck at work,14:09
*** hrito has joined #openstack-kolla14:09
*** hrito has left #openstack-kolla14:10
*** bootsha has quit IRC14:11
*** hrito has joined #openstack-kolla14:11
*** hrito has left #openstack-kolla14:13
inc0pbourke, any news on osic cluster?14:13
pbourkeinc0: noone working on it since yesterday14:14
inc0ok, I'll try to run rally on top of what we have14:14
pbourkeinc0: i can show you what we have in progress14:14
inc0yes plz14:14
inc0give me a sec14:14
pbourkeinc0: connecting14:14
*** hrito has joined #openstack-kolla14:14
inc0to get on tmux14:14
pbourkeinc0:14:15
pbourkeso two files14:15
pbourkeinc0: all-scenarios are all the rally scenarios. Then we've commented out the ones that aren't relevant14:16
pbourkeinc0: the second script then runs each scenario, and stores the results in some sort of db14:16
inc0kk14:16
pbourkeinc0: its pretty simple. there's one more command needed to dump the results to json14:17
inc0yeah, dump json something14:17
pbourkeinc0: other thing that needs to be done is - _coolsvap_ has mentioned the settings in some of these scenarios are appropriate for the scale of our cluster14:17
pbourkeI dont quite understand what needs to change there though14:17
pbourkepossibly examples there in that diff14:17
pbourkebut i dont know where those numbers are coming from (e.g. 3 -> 25)14:18
pbourkeonce we nail down the script though it will make rally after each deploy scenario a doddle14:18
pbourkeso that's it basically, I want to finish but no time right now14:18
inc0ok14:19
inc0I'll play with it14:19
*** caowei has quit IRC14:21
*** haplo37 has joined #openstack-kolla14:22
*** haplo37_ has joined #openstack-kolla14:22
*** caowei has joined #openstack-kolla14:22
*** g3ek has joined #openstack-kolla14:23
sdake_pbourke - think tht will be helpful14:33
sdake_pbourke thanks!14:33
pbourkenp14:34
*** ad_rien_ has quit IRC14:34
openstackgerritPaul Bourke proposed openstack/kolla: Set 'balance source' for Horizon in haproxy  https://review.openstack.org/35651414:35
*** michauds has joined #openstack-kolla14:40
*** diogogmt has joined #openstack-kolla14:47
*** zhurong has quit IRC14:59
*** _coolsvap_ is now known as coolsvap15:01
*** openstackgerrit has quit IRC15:03
*** openstackgerrit has joined #openstack-kolla15:04
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Start using orchestration_engine variable  https://review.openstack.org/35653815:12
openstackgerritVladislav Belogrudov proposed openstack/kolla: Cinder cannot use external non-LVM iSCSI storage  https://review.openstack.org/35654015:15
hritoHello, I want to propose additional functions to kolla. for that, what steps are required? after writing blueprint, need specs?15:16
rhalliseyhrito, a blueprint in launchpad is perfect15:17
rhalliseyassign it to yourself and desrcibe it15:17
rhalliseyhrito, then you're good to go :)15:18
openstackgerritPaul Bourke proposed openstack/kolla: Allow Neutron to be run in DVR mode  https://review.openstack.org/35654415:18
rhalliseyand feel free to ask questions if you get stuck15:18
*** vbel has joined #openstack-kolla15:20
*** huikang has quit IRC15:21
openstackgerritPaul Bourke proposed openstack/kolla: Allow Neutron to be run in DVR mode  https://review.openstack.org/35654415:21
*** huikang has joined #openstack-kolla15:21
*** HyperJohnGraham has joined #openstack-kolla15:22
hritorhallisey: you meen after writing blueprint, just push patches?15:23
sdake_hrito at this point in time we do not require specs15:23
rhalliseyhrito, ya15:23
sdake_that may change in the future especially to facilitate the new ptg structure15:23
hritosdake_: rhallisey: ok! thanks!15:24
kbaegisdvr would be very nice15:24
sdake_hrito - our team meeting is in 30 minutes if you want to find out more about ptg15:24
*** huikang has quit IRC15:26
hritosdake_: ok, i'll join meeting :)15:26
*** caowei has quit IRC15:29
jrich523should i be using kolla to build a node as well, or is it strictly contoller based?15:33
sdake_build a node - which type15:35
sdake_I dont understand the Q:)15:35
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: WIP- openvswitch ip  https://review.openstack.org/35611415:35
kfox1111grr.15:35
jrich523sorry, compute15:35
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: WIP- openvswitch ip  https://review.openstack.org/35611415:36
sdake_jrich523 kolla will deploy controller, compute, and storage nodes for you15:36
sdake_all you ahve to do is specify the machines in the inventory file15:36
openstackgerritKevin Fox proposed openstack/kolla: Add crudini  https://review.openstack.org/35615515:36
jrich523oh, well where is this inventory file?15:36
sdake_jrich523 - it will also operate them afterwards :)15:36
jrich523well thats ideal :)15:36
sdake_ansible/inventory directory15:37
sdake_it can be overridden with kolla-ansible -i inventoryfile15:37
sdake_thosse in there are just samples15:37
jrich523let me go poke15:37
jrich523thanks15:37
kfox1111awesome... k8s scheduledjobs made it in for 1.4 :)15:37
kfox1111we may want kolla-kubernetes to depend on 1.4 :)15:38
kfox1111would give us a nice mechanism to do fernet key updating.15:38
sdake_kfox1111 we have a release indepndent release schedule15:38
sdake_and at this point its not 1.0.015:38
sdake_so we can do whatever we like with changing things and have no concern for backward compatibility15:38
sdake_or following any deprecation policy15:39
rhalliseykfox1111, considering how new this all is, we'll be constantly chasing the newest until we hit a release15:39
sdake_i think the time to lock down a version is when kolla-ansible==1.0.015:39
sdake_rhallisey can probably define what that looks like for us in our team meeting15:39
jrich523sdake_: do you mean hosts? I found a /etc/ansible/hosts file, which seems to have the info in it15:39
sdake_jrich523 oh you pip isntalled a stable version?15:40
jrich5231.9.415:40
jrich523i cant remember if it was pip or yum15:40
jrich523but yeah15:40
sdake_it should be in the /usr/include/kolla/ansible/inventory directory15:40
kfox1111rhallisey: I'd argue the other direction. due to how new kolla-kubernetes is, its better to get it working with a good archetecture, even thougth the features might be a little green as by the time we stabalize, so will the k8s features.15:40
jrich523k, thanks15:40
*** dmueller-evoila has joined #openstack-kolla15:40
jrich523god files are all over the place lol15:40
sdake_jrich523 ya ansible unfortunately is a bit messy - /usr/share i mean15:41
sdake_ /usrs/hare is where we store the dockerfiles and ansible code that is run15:41
kfox1111by kolla-kubernetes 1.0, k8s will probably be at least 1.615:41
rhalliseykfox1111, kolla-kube won't be 1.0 for a bit15:41
ntpttr___hey inc0, you there?15:41
kfox1111exactly.15:41
kfox1111so lets kind of target where kubernetes will be when kolla-kubernetes is ready.15:42
rhalliseywhen we hit 1.0 we will develop features that are appropriate  for the kube release15:42
sdake_             jrich523 fwiw - we follow fhs standaards :)15:42
kfox1111otherwise, we'd be obsolete before we're ready.15:42
rhalliseywe will be continuing to move the kube version as we add new features that require a new cube15:42
rhalliseyreleases will define what version that is15:42
kfox1111by 1.0, init containers, deployments, petsets, and scheduledjobs should all be stable.15:43
rhalliseybut I'm not sure yet when that will be so we can continue to roll15:43
sdake_rhallisey i can provide some insight here - once 1.0.0 is created, we createe a stable branch15:43
jrich523im not sure what fhs is :-/15:43
sdake_new features go in master, stable left alone :)15:43
sdake_filesystem hiearchy standard15:43
rhalliseymy estimate will be O15:43
sdake_i think so too15:43
jrich523yeah, im a windows guy, the linux structure has always confused me15:43
rhalliseyfor a stable branch15:43
jrich523not that windows is straight forward, but you know... its what i use15:43
sdake_that is when 1.0.0 happens15:43
rhalliseyroger15:44
sdake_1.0.0 = stable branch15:44
kfox1111jrich523: I generally like the fhs, but the problem with it is so few folks know it, there are are far to many exceptions.15:44
jrich523well, i mean really, what does /etc or /var really mean... as far as i know they dont relate to a word that describes what they are15:44
kfox1111the fhs defines that.15:44
jrich523at least in windows you have 'program data', 'program files' fairly obvious15:44
kfox1111 /etc is basically for config files.15:44
*** thumpba has quit IRC15:44
kfox1111 /var is stuff that needs to change as the machine runes.15:45
sdake_jrich523 /var = writeable /usr = readonly15:45
kfox1111runs15:45
kfox1111 /usr/ readonly.15:45
jrich523well, yeah but why do i need a decoder ring? i guess back in the day went folder length mattered... or tab complete didnt exist :)15:45
kfox1111so if you nfs mount and share your root file system, /usr goes in there.15:45
sbezverkrhallisey kfox1111 it is nice to version planning :-) but we have bunch of reviews in the queue15:45
sdake_jrich523 it really does help to have these things standard across distros15:45
kfox1111jrich523: because unlike windows, you can take one os install and spread it across 2000 machines. :)15:45
sdake_so we dont have to figure out 15 different ways to install the ODM15:45
*** matrohon has quit IRC15:46
kfox1111sbezverk: +115:46
jrich523im not sure i follow kfox1111, i spew windows all over the place :)15:46
rhallisey:)15:46
sdake_ya the review queue is in overload15:46
kfox1111jrich523: for linux clusters, you take a nfs server (smb equivilent) install linux on that one share,15:48
jrich523so there are two files in the inventory folder, all-in-one and multinode, looking at both of them, they look like config types15:48
kfox1111and pxe boot a kernel pointing to that share as the root.15:48
jrich523oh a shared os, gotcha... guess you could do that with windows... but... probably not cool :)15:48
kfox1111there is no install. there is one os install running across 2000 nodes.15:49
kfox1111windows can't do that. you have to install windows on each individual machine.15:49
kfox1111doing that way lets you make one change to the share and instantaniously all 2000 nodes are updated.15:49
lrensing_hey guys- when running kolla-ansible deploy i started getting this error and can't seem to resolve it:15:49
lrensing_Hostname has to resolve to IP address of api_interface15:49
duonghqlrensing_ do you run Ubuntu/Debian-based?15:50
lrensing_ubuntu, yes15:50
duonghqyou should remove 127.0.1.1 in /etc/hosts15:50
duonghqreplace with real ip15:50
lrensing_doh15:51
duonghqthe 127.0.1.1 is placed as as fallback for some software but cause trouble to Kolla15:51
jrich523sdake_: so it looks like the inventory folder you sent me to, contains configs (all-in-one, and multinode) and the place to add a new host is in the /etc/ansible/hosts file i found15:51
jrich523with those two configs tho, it seems like i'd need to build another for a compute only node?15:52
sdake_you need to make your own or edit the all-in-one15:52
sdake_the all-in-one is default15:52
sdake_but it can be overidden with the -i flag15:52
jrich523ok15:52
sdake_how I'd like to see this work in teh future is invetory files stored in /etc15:52
sdake_since its a configuration file nto a read only file :)15:53
jrich523so copy that to computenode (lets say) and modify it, do i need to import that file after or is the location good enough?15:53
kfox1111rhallisey: is there an example of launching the same service template with different args defined in the serservice_resources file?15:53
jrich523that does make sense :)15:53
sdake_jrich523 keep it on the deployment node15:53
sdake_nothing needs to be copied to the compute nodes15:53
sdake_jrich523 if you open that file up it has a [compute] section15:53
jrich523no i mean, to a new file (deployment config)15:54
sdake_just add your ips in15:54
jrich523so cp all-in-one computenote15:54
jrich523edit computenode15:54
sdake_oh right, i'd copy all-in-one to /etc/kolla15:54
kfox1111rhallisey: oh, I think I see it. vars: ...15:54
jrich523add my box to the hosts file15:54
sdake_right that will do it15:54
jrich523so if i do it in /etc/kolla i have to do the kolla-ansible -i computenode15:54
rhalliseykfox1111, I think var's may be what you're after15:54
jrich523which, basically just copies it to the inventory folder?15:54
duonghqjrich523: I think you should take a scratch course about ansible, this will help15:54
jrich523duonghq: yeah reading their docs now15:55
sdake_jrich523 you have to specify the full path to the inventory file with kolla-ansible15:55
jrich523k15:55
kfox1111sbezverk: I think in the case of different interfaces on different types of hardware, we need a way to run multiple daemonsets with overrides of the interface. :/15:55
kfox1111I think we can use the templating to do that though.15:55
kfox1111we really need to discuss node selectors15:55
jrich523i think i've got enough to go break some things, thanks :)15:55
kfox1111though.15:55
sdake_jrich523 happy to help15:56
kfox1111rhallisey: sbezverk: what do you think about kolla-compute=v1 and kolla-controller=v1 for now?15:56
*** dmueller-evoila has quit IRC15:57
rhalliseykfox1111, as long as it's templated15:57
rhalliseywe can default those however15:58
*** ajpower has joined #openstack-kolla15:58
inc0you know what time is it? Its meeeeeeting time!15:58
rhalliseys/v1/<something_more_descriptive>/15:58
duonghqcount down15:58
sdake_big countdown atleast 120 numbers to count :)15:59
duonghq64sec actually :)16:00
ajpower#startmeeting kolla16:00
*** lrensing_ has quit IRC16:00
openstackMeeting started Wed Aug 17 16:00:25 2016 UTC and is due to finish in 60 minutes.  The chair is ajpower. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
openstackThe meeting name has been set to 'kolla'16:00
*** sdake_ is now known as sdake16:00
rhalliseyajafo, wrong location16:00
*** sdake is now known as sdake_16:00
rhalliseyajpower, , #openstack-meeting-416:01
rhalliseyajafo, sorry wrong person16:01
*** egonzalez has joined #openstack-kolla16:02
*** ajpower has quit IRC16:03
*** ajpower has joined #openstack-kolla16:04
*** dmueller-evoila has joined #openstack-kolla16:04
ajpower #openstack-meeting-416:04
*** egonzalez90 has quit IRC16:05
*** egonzalez is now known as egonzalez9016:05
openstackgerritMerged openstack/kolla: Replace horizon default config with custom config  https://review.openstack.org/30692816:05
*** dmueller-evoila_ has joined #openstack-kolla16:07
rhalliseyajafo, `/join #openstack-meeting-4`16:07
rhalliseyajpower, ^16:07
rhalliseysorry ajafo16:07
rhallisey:/16:07
*** mark-casey has joined #openstack-kolla16:08
ajpowerjoin #openstack-meeting-416:08
*** dmueller-evoila has quit IRC16:08
rhalliseyajafo, add a /16:08
*** dmueller-evoila_ has quit IRC16:13
*** Serlex has quit IRC16:17
kbaegisSo what's the procedure/strategy in kolla to upgrade a single container?16:17
*** vhosakot has joined #openstack-kolla16:18
*** v1k0d3n has joined #openstack-kolla16:20
*** ChanServ changes topic to "Kolla IRC meetngs on Wednesdays @ 16:00 UTC - see agenda @ https://goo.gl/OXB0DL - Community Submitted Talks for Occata https://goo.gl/s8Wldv - OSIC cluster testing etherpad https://goo.gl/vAMGB6 - IRC channel is *LOGGED* @ http://goo.gl/3mzZ7b (old logs from #kolla http://goo.gl/VKpPzA)"16:27
kbaegisIs there an individual runbook I can deploy to move horizon between versions, for example?16:33
*** unicell1 has quit IRC16:33
rhalliseykbaegis, you can run play specific for a service with tags16:33
rhalliseyso you can run the upgrade play with the horizon tags and that should get what you want16:33
*** HyperJohnGraham has quit IRC16:34
kbaegisso the command would be kolla-ansible upgrade horizon?16:35
kbaegisor would I alter globals and select a horizon version?16:35
rhalliseykbaegis, kolla-ansible upgrade --tags horizon16:36
kbaegisOh, nice :)16:37
*** JoseMello has joined #openstack-kolla16:37
kbaegisLatest issue: http://hastebin.com/pijeqimofi.vbs16:47
kbaegisAnyone played around with non-cooperative iptables implementations and willing to help?16:47
*** ajpower has quit IRC16:48
kbaegisTap device is created successfully, bridge too16:48
kbaegisIt's just these dang iptables rules :)16:48
*** huikang has joined #openstack-kolla16:49
kbaegisRunning the commands from the log against iptables manually I get errors like16:50
kbaegisiptables: No chain/target/match by that name.16:50
kbaegisor iptables: Index of insertion too big16:50
*** Jeffrey4l has quit IRC16:52
kbaegisHuh.  Maybe it needs CONFIG_INET_DIAG_DESTROY16:53
inc0coolsvap, so ad rally16:53
* britthouser listens in16:53
inc0it should work now, we just need to change deployments16:53
duonghqhey sdake_, the bug, do we have any replacement for deprecated tag option?16:53
inc0cuz access creds are invalid16:53
ntpttr___hey inc0 I'm running into an issue with my cinder/ceph deployment in kolla, do you have a moment?16:54
inc0sure16:54
inc0what's up Nate?16:54
sdake_duonghq i dont have a clear picture of the issue yet duonghq16:54
ntpttr___inc0: so everything is starting up fine and I can create and attach volumes and all, but the backup service isn't working16:54
sdake_duonghq - but there are docs in teh queue addressing it16:54
sdake_they are just wrong16:54
ntpttr___inc0: basically whenever I try to backup a volume, it hangs in the 'creating' phase forever16:54
sdake_duonghq so the solution first is to document a workaround16:54
coolsvapinc0: hi16:54
inc0and no errors?16:54
sdake_duonghq then to fix the pbr issue16:54
ntpttr___and it seems like privsep just isn't starting up16:54
coolsvapinc0: where are we currently wrt rally16:55
ntpttr___in the logs, here's mine: http://paste.openstack.org/show/558606/ and here's one where it works: http://paste.openstack.org/show/558537/16:55
ntpttr___the privsep daemon isn't starting, but there's no errors16:55
duonghqsdake_: I look through the code and cannot find any replacement for deprecated option, I don't think its normal16:55
inc0coolsvap, can you fix deployments in rally? our creds are wrong16:56
duonghqsdake_ fix me if I wrong :)16:56
*** bootsha has joined #openstack-kolla16:56
inc0ntpttr___, it might be a bug16:56
coolsvapinc0: sure let me connect to vpn16:56
inc0I haven't seen this before16:56
ntpttr___inc0: it looks like that might be the case, this is on a clean install with no errors or anything16:56
ntpttr___has anyone here deployed cinder w/ ceph and then successfully used the backup service before?16:57
inc0our tests on osic cluster should show that16:57
duonghqsdake_: I think it should be a option in kolla-build.conf for tagging?16:58
sdake_i dont think --tag should be a deprecated option at all16:59
ntpttr___inc0: do you think I should go ahead and file a bug against kolla?16:59
sdake_i dont know why it is16:59
coolsvapinc0: we can update the credentials in osic.json file on the node17:00
inc0ntpttr___, yeah, file it17:00
duonghqsdake_: somebody marked it deprecated?17:00
*** HyperJohnGraham has joined #openstack-kolla17:00
inc0coolsvap, might doing that?17:01
coolsvapinc0: i am updating it from /etc/kolla/admin-openrc.sh17:01
inc0I dunno where it is17:01
coolsvapyes17:01
inc0tmux a plz17:01
inc0I'll watch it17:01
coolsvapyeah sorry17:01
coolsvapjust a min17:01
inc0np:)17:01
*** rstarmer has joined #openstack-kolla17:02
*** egonzalez90 has quit IRC17:03
ntpttr___okay got the bug report up https://bugs.launchpad.net/kolla/+bug/161418017:03
openstackLaunchpad bug 1614180 in kolla "Backup w/ ceph hangs when creating a backup" [Undecided,New]17:03
*** fragatina has joined #openstack-kolla17:05
*** hrito has left #openstack-kolla17:07
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: WIP- openvswitch ip  https://review.openstack.org/35611417:09
ntpttr___inc0: do we need to be installing oslo.privsep somewhere? I don't see it anywhere in the kolla repo, or in this file where I see a lot of other oslo libraries https://github.com/openstack/kolla/blob/5f4ef0d84bf1d1f5f72f245a0dc9e95d25e0b92d/docker/openstack-base/Dockerfile.j217:10
ntpttr___in devstack they're installing it https://github.com/openstack-dev/devstack/blob/06f3639a70dc5884107a4045bef5a9de1fb725a5/lib/oslo17:10
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: WIP- openvswitch ip  https://review.openstack.org/35611417:11
*** inc0 has quit IRC17:13
*** HyperJohnGraham has quit IRC17:16
*** bootsha has quit IRC17:18
Pavoevening everyone17:19
*** Guest52040 has quit IRC17:20
openstackgerritSwapnil Kulkarni (coolsvap) proposed openstack/kolla: Update cirros image visibility in init-runonce  https://review.openstack.org/35393317:20
*** bootsha has joined #openstack-kolla17:21
*** bootsha has quit IRC17:22
*** bootsha has joined #openstack-kolla17:23
kbaegisgah.  Linuxbridging broken still on gentoo17:26
*** unicell has joined #openstack-kolla17:26
*** bootsha has quit IRC17:26
coolsvappbourke: do yo uwhave the kolla-rally-tests.sh script open in your terminal?17:27
*** fragatina has quit IRC17:30
kfox1111sbezverk: rhallisey: so, for the glance bootstrap one. we postponed talking about dealing with the init-container templating thing for dealing with the json as we didn't have access to jq. that patch just merged though.17:31
*** unicell has quit IRC17:31
*** fragatina has joined #openstack-kolla17:31
sbezverkkfox1111: I would suggest to merge what I have now as I tested it multiple times and it is working17:32
kfox1111can we reconsider this: https://review.openstack.org/#/c/353740/4..6/services/neutron/neutron-bootstrap-job.yml.j217:32
patchbotkfox1111: patch 353740 - kolla-kubernetes - Neutron bootstrap to create service/project/role17:32
Pavokbaegis was it you asking about deploying only 1 of the images with kolla-ansible yesterday?17:32
*** duonghq has left #openstack-kolla17:32
rhalliseykfox1111, I mean we can iterate on it17:32
sbezverkif you feel like modifying it, please submit PS and we can have discussion17:32
*** bootsha has joined #openstack-kolla17:32
kfox1111k.17:32
sbezverkit is just so many things are hanging because of this17:33
kfox1111sure. but I just want to avoid having to do more when we add more bootstrapping to nova and friends too.17:34
sbezverkkfox1111: I do not think we add more than just nova17:34
sbezverkany time soon17:34
kfox1111we can merge these 2 as is.17:34
kfox1111cinder?17:34
kfox1111heat?17:34
sbezverkso if you propose PS after, I will help you to apply on other components17:34
kfox1111k17:35
sbezverkIf I undersatand the primary goal is get VM17:35
kfox1111ah. we can claim vm without cinder/heat, true.17:36
sbezverkkfox1111 yep, I think it make sense17:36
*** rstarmer has quit IRC17:37
kfox1111one more thing and I think the glance one's good then.17:37
kfox1111do we actually need the pvc in the bootstrap?17:37
kfox1111I don't really see where its used, and it shouldn't be there if using the ceph backend.17:38
kfox1111I think we can probably just drop it all together.17:38
*** bootsha has quit IRC17:39
sbezverkkfox1111: I will need to retest it17:39
sdake_pbourke you still around?17:40
sdake_i dont blame ya17:40
sdake_sweet dreams :)17:40
kfox1111wait..17:42
kfox1111its used here:17:43
*** bootsha has joined #openstack-kolla17:43
kfox1111https://review.openstack.org/#/c/346215/11/services/glance/glance-bootstrap-job.yml.j2 line 7617:43
patchbotkfox1111: patch 346215 - kolla-kubernetes - Glance bootstrap to create service/project/role17:43
kfox1111whats the api container being used for?17:43
sbezverkkfox1111: it looks like it is used during bootstrap process.17:44
kfox1111where?17:44
kfox1111I see database creation, and keystone registration. but not much else?17:44
sbezverkkfox1111: it does this     sudo chown -R glance: /var/lib/glance/17:46
kfox1111hmm....17:47
*** HyperJohnGraham has joined #openstack-kolla17:47
kfox1111oh. cause the KOLLA_BOOTSTRAP.17:47
sbezverkkfox1111: if we do not have it mounted, it will be done against virtual directory17:47
sbezverkkfox1111: right17:47
kfox1111k.17:48
sbezverkkfox1111: it is not much but please do not ask me to move it somewhere else17:48
kfox1111so then I think we just need to do something like: https://review.openstack.org/#/c/354895/4/services/glance/glance-api-pod.yml.j217:48
patchbotkfox1111: patch 354895 - kolla-kubernetes - WIP - Deployment, Safe Shutdown, & Scaling for gla...17:48
kfox1111with glance_backend_ceph17:48
kfox1111around the volume and volumeMount.17:49
kbaegisPavo Yes :)17:49
sbezverkkfox1111: can you add it on top after it is merged?17:49
sbezverkI will not be able to test it17:49
sbezverkI just do not have means17:50
kfox1111k.17:50
Pavoyou can use the --tags argument to only deploy whatever containers you want17:50
kfox1111+217:50
sbezverkkfox1111: thank you, as soon as it is merged please submit your patch17:51
kfox1111I guess I can just rebase and fix in https://review.openstack.org/#/c/354895/4/services/glance/glance-api-pod.yml.j2 once merged.17:51
patchbotkfox1111: patch 354895 - kolla-kubernetes - WIP - Deployment, Safe Shutdown, & Scaling for gla...17:51
kbaegisPavo Or so I've been told :)17:51
kbaegisIt's a cool feature17:51
*** inc0 has joined #openstack-kolla17:52
*** HyperJohnGraham has quit IRC17:52
Pavoexample kolla-ansible deploy -i ansible/inventory/multinode --tags horizon, will only redeploy horizon on the node thats in your inventory list17:52
*** HyperJohnGraham_ has joined #openstack-kolla17:53
*** HyperJohnGraham_ is now known as HyperJohnGraham17:53
sbezverkkfox1111: rhallisey: we need to decide what to do with secret generator. All these bootstraps are consuming secrets. So it would make sense to include it now just for a timebeing as a separate tool..17:55
rhalliseysbezverk, I think we might  be putting the cart ahead of the horse a little17:55
kfox1111I'm ok merging the secret generator as is for now.17:56
rhalliseywe need to focus on a few things, accomplish them, and tackle new ones17:56
rhalliseywe have a bunch of efforts happening and it's hard to track17:56
sbezverkkfox1111: did not want to ack without it ;-)17:56
kfox1111sbezverk: makes sense.17:56
rhallisey1) lets get the core services working17:56
rhallisey2) CLI/ansible17:56
rhalliseyso hold on to this script for noew17:57
*** HyperJohnGraham_ has joined #openstack-kolla17:57
rhalliseythe secrets bit let's handle after we get the services working17:57
inc0coolsvap, O17:57
inc0I'm backl17:57
rhalliseykfox1111, sbezverk is that ok?17:57
rhalliseywe need to focus on the big tasks first17:58
sbezverkthen we need to revert bootstrap changes17:58
kfox1111rhallisey: the secrets are already staring to land. we just need a way to get them into k8s now.17:58
coolsvapinc0: i am logging off17:58
kfox1111the script is less then ideal, but pretty simple and works.17:58
rhalliseykfox1111, I'm saying let's not block on that17:58
kfox1111we can just merge it and then refactor it later when we have more time.17:58
rhalliseyservice can land17:58
rhalliseythen we can do that17:58
inc0coolsvap, did you move anything forward?17:58
coolsvapi validate the scenarios, some amount of work is needed17:58
kfox1111ah.17:58
coolsvapvalidated the scenarios17:58
*** HyperJohnGraham has quit IRC17:58
kfox1111ok. that works too.17:58
kfox1111we can review the generator independendly then.17:59
rhalliseykfox1111, ya let's tackle these problems in smaller bits17:59
kfox1111its just weird to leave trunk unusable. without other patches.17:59
*** papacz has quit IRC17:59
kfox1111though we have the same issue with kolla.17:59
rhalliseykfox1111, it17:59
rhalliseyit's the nature of master in a new project to be a little unstbale17:59
kfox1111yup. I get that.18:00
rhalliseycool cool18:00
kfox1111kk.18:00
sbezverkkfox1111: rhallisey: we need to revert back to old bootstraps if you do not want to use the script..18:00
*** HyperJohnGraham has joined #openstack-kolla18:00
rhalliseysbezverk, is there a way we can have it for one service?18:01
rhalliseyglance has it right?18:01
kfox1111sbezverk: he's saying we should just note that you need the extra script from review xxx to work.18:01
sbezverkglance, neutron and keystone18:01
rhalliseysbezverk, we can doc it18:01
kfox1111we're already doing that with kolla too.18:01
openstackgerritMerged openstack/kolla-kubernetes: Glance bootstrap to create service/project/role  https://review.openstack.org/34621518:02
rhalliseywe're getting close to landing the core services so we can return to this soon18:02
sbezverkrhallisey eitherway works for me as lons as we move forward :-)18:02
rhalliseykfox1111, yes true, it will be growing pains for now18:02
kfox1111rhallisey: thoughts on https://review.openstack.org/#/c/35611418:02
patchbotkfox1111: patch 356114 - kolla-kubernetes - WIP- openvswitch ip18:02
*** HyperJohnGraham_ has quit IRC18:02
rhalliseywe won't really get a sense of stability until we have all the core services in place with our CLI/workflow done18:02
kfox1111I think we can probably pull the WIP off of it, but I haven't really been able to test it yet.18:03
rhalliseybrb guys18:03
kfox1111yeah, I was alittle afraid of that... all the json stuff in the kolla-config all conflict with each other.18:05
kfox1111so neutron/keystone bootstrap secret reviews now have merge issues.18:05
*** HyperJohnGraham has quit IRC18:05
*** bootsha has quit IRC18:07
*** unicell has joined #openstack-kolla18:07
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Neutron bootstrap to create service/project/role  https://review.openstack.org/35374018:12
sbezverkkfox1111: resolved it18:13
kfox1111+2'ed it. :)18:13
*** Pavo has quit IRC18:17
*** Pavo has joined #openstack-kolla18:19
kfox1111rhallisey: sbezverk: we should probably talk more about https://review.openstack.org/#/c/354895 too.18:19
patchbotkfox1111: patch 354895 - kolla-kubernetes - WIP - Deployment, Safe Shutdown, & Scaling for gla...18:20
*** tummy has joined #openstack-kolla18:20
kfox1111I think we will need to set the api address to 127.0.0.1 for it to work properly, but then all services will need similar patches as there is only one var for api ip right now.18:20
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: WIP - Deployment, Safe Shutdown, & Scaling for glance-api  https://review.openstack.org/35489518:21
*** tummy has quit IRC18:21
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: WIP - Deployment, Safe Shutdown, & Scaling for glance-api  https://review.openstack.org/35489518:23
*** gfidente has quit IRC18:24
sbezverkkfox1111: have you tested this patch with other services communicating between each other?18:29
sbezverkcause this approach chnages also interprocess communication if I undersatnd correctly the idea18:30
kfox1111I have not yet, as I need a solution to configuring it to listen on 127.0.0.1 instead of 0.0.0.018:31
kfox1111I didn't think glance did rpc. does it?18:31
kfox1111I think for now, so I don't break everything to test, I can use an init container and override the config from 0.0.0.0 to 127.0.0.1.18:32
kfox1111but I need the crudini patch to land in kolla.18:32
kfox1111then we should be able to apply the same pattern to the other apis.18:33
kfox1111we probably want to split the rpc services from the api services anyway.18:33
kfox1111mostly I think thats already done, except maybe neutron-server I think does both.18:34
kfox1111the neutron-server api's should be deployments and the neutron-server rpc's should be petsets I think.18:34
kfox1111thought neturon did say its safe to restart a neutron-server these days.18:35
kfox1111so the rpc stuff should in theory be safe to do mixed up in the api server with a deployment if that actually is true.18:35
*** bmace has joined #openstack-kolla18:36
*** inc0 has quit IRC18:37
*** tummy has joined #openstack-kolla18:44
*** tummy has quit IRC18:45
*** egonzalez has joined #openstack-kolla18:46
*** egonzalez is now known as egonzalez9018:47
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: WIP - Deployment, Safe Shutdown, & Scaling for glance-api  https://review.openstack.org/35489518:52
kfox1111k. once the crudini kolla patch lands, I think that one should probably work. needs a bit of testing once landed.18:52
kfox1111we should then be able to apply the pattern to the other api services.18:52
*** egonzalez90 has quit IRC18:59
*** athomas has quit IRC19:01
*** thumpba has joined #openstack-kolla19:05
*** wznoinsk has quit IRC19:07
*** egonzalez90 has joined #openstack-kolla19:08
sdake_30 mintes afk19:08
sdake_bbiaf19:08
kbaegisSo I'm getting timeouts19:14
kbaegisbetween ovsdb and openvswitch19:14
openstackgerritLeon Zachery proposed openstack/kolla: Simplify install process for faster quickstart execution  https://review.openstack.org/35618119:15
*** inc0 has joined #openstack-kolla19:19
kbaegishttp://hastebin.com/xiyenufera.vbs19:24
*** ad_rien_ has joined #openstack-kolla19:24
kbaegisLinux bridging isn't working for me because of the iptables implementation, ovs is having timeouts between ovsdb and ovs-vswitchd19:25
kbaegisSo I can create volumes, upload images, spawn instances, but the network doesn't work for the L2 agents available19:25
*** wznoinsk has joined #openstack-kolla19:26
kbaegisAll devices are getting created just fine (taps and bridges).19:26
kbaegisOVS isn't up for more than 10 seconds due to not being able to reach ovsdb19:26
*** britthou_ has joined #openstack-kolla19:27
*** britthouser has quit IRC19:27
*** ayoung has quit IRC19:27
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: WIP - Deployment, Safe Shutdown, & Scaling for glance-api  https://review.openstack.org/35489519:29
sdake_kbaegis my bet is rtnetlink19:30
sdake_but it could be the iptables integration with gentoo - which there probabyl sin't any19:31
kbaegissdake_ I need to become an authority on rtnetlink then.  :)19:32
sdake_i think my second guess might yield more results19:32
sdake_but not sure19:32
kbaegissdake_ Like I said, it's able to create functioning tap devices19:32
sdake_they are both speculation19:32
kbaegisAnd they'll be plugged into the bridge19:33
sdake_i missed that part19:33
sdake_probably some iptables issue19:33
sdake_do you hae iptables enabled by default in gentoo?19:33
kbaegisIt fails on the secgroup rules, yes19:33
kbaegisHere's the traceback http://hastebin.com/pijeqimofi.vbs19:33
kbaegisAnd yes, iptables is fully implemented in the kernel (all opts), and installed with all use-flags19:34
kbaegisI rebuilt/repushed centos from source after19:34
kbaegisI can validate that this is the only remaining issue for a base deployment on gentoo19:34
kbaegisSo if I can crack this, I don't have to use fuel-cpp on k8s19:35
kbaegisWhich is my personal preference :)19:35
sdake_not sure - it could be either rtnetlink or iptables implementation in neutron19:36
sdake_it is debuggable19:36
sdake_since you can get a backtrace19:36
sdake_protip print ftw :)19:36
sdake_before doing that though, did you have iptables enabled by default in gentoo?19:37
sdake_not built into the kernel19:37
sdake_but enabled in the sysv scripts19:37
sdake_or systemd or whatever one your using19:37
kbaegisHmm19:38
kbaegisyikes. https://wiki.gentoo.org/ is down19:39
sdake_wfm19:39
*** ad_rien_ has quit IRC19:39
kbaegisHuh. Did /etc/init.d/iptables restart and now I'm getting a new error- modprobe: FATAL: Module openvswitch not found19:41
sdake_ya19:41
kbaegisIs ovs required as a module, not as a builtin?19:41
sdake_dont do that19:41
sdake_not sure on ovs being a module19:41
sdake_iptables should be disabled19:41
sdake_not in an enabled state19:42
sdake_i wanted to know if you had it enabled previously19:42
sdake_chkconfig status iptables ought to do it19:42
kbaegisI hadn't19:43
sdake_so it wasn't enabled?19:43
kbaegisI just saved the default rules and19:43
sdake_ok19:43
kbaegisIt wasn't setup by sysvinit19:43
sdake_lets start fresh19:44
sdake_reboot your boxes19:44
sdake_cleanup first19:44
kbaegis:'( okay19:44
openstackgerritLeon Zachery proposed openstack/kolla: Simplify install process for faster quickstart execution  https://review.openstack.org/35618119:44
sdake_but dont delete your image19:44
sdake_s19:44
sdake_all we are going to do is iptables --flush19:44
sdake_prior to deploy19:44
kbaegisOkay19:44
sdake_on the reboot19:44
sdake_so whtaever you ahve eto do to make that happen, i'm sure you know by now :)19:44
sdake_do on all nodes19:45
-openstackstatus- NOTICE: The volume for logs.openstack.org filled up rather suddenly, causing a number of jobs to fail with a POST_FAILURE result and no logs; we're manually expiring some logs now to buy breathing room, but any changes which hit that in the past few minutes will need to be rechecked and/or approved again19:45
kbaegiskolla-ansible destroy runs all the cleanup scripts, correct?19:45
kbaegisSo just do that, reboot, iptables —flush, deploy?19:45
sdake_remind me - your aio atm?19:45
sdake_if multinode - need to specify an inventory file19:46
kbaegisI don't know what aio stands for :)19:46
kbaegisOh, all-in-one19:46
sdake_aio = all in one19:46
kbaegisYes.  That's step 119:46
kbaegisThen I'm going to spin the controllers up on 2 additional nodes (primarily into swap)19:46
sdake_if your aio then destroy will do the job19:46
kbaegisSince I only have 4gigs ram on those two19:46
sdake_it may not be iptables --flush as well19:47
sdake_i have a meeting in 10 mins to prep for, so i don't have time to read the manual page19:47
kbaegisokay19:47
sdake_ill be back in an hourish19:47
kbaegisgood prepping, ty for all the help19:48
sdake_ya19:48
sdake_if you could write down what you did to make it all work that might come in handy19:48
kbaegisI will.19:48
sdake_for others that follow in your path19:48
sdake_etherpad is good19:48
sdake_or an email to the mailing list19:49
kbaegisThere's a lot of dependencies for those compiling everything from source.  Assumptions you get to make w/ distros :)19:49
kbaegisI think this will help the Kolla community as well.  When Ubuntu decides to change something in the kernel, for instance.19:49
sdake_quetion, did the buildl keepalived binary work for you?19:49
kbaegisI have it disabled at present19:49
sdake_i see19:49
sdake_so two things to solve not 1 :)19:49
kbaegisI could workaround earlier (centos-bin)19:49
sdake_you will need keepalived for step 219:49
kbaegisby manually assigning the vip19:49
kbaegisBut that's a hack against your checking scripts19:50
kbaegisIt was iptables —flush20:00
kbaegisRedeploying, fingers crossed :)20:01
*** bmace has quit IRC20:11
*** bmace has joined #openstack-kolla20:11
*** coolsvap has quit IRC20:11
Pavoanyone know what this error means? https://paste.pound-python.org/show/tXwye4n3DaYxKl95Rv20/20:12
kbaegisPavo I'm guessing it's a pip problem.  Not able to find files20:13
kbaegisDid you do pip2 install -U git/20:14
kbaegisand pip2 install -U ansible20:14
Pavono, the docs only say pip install -U docker-py20:14
kbaegisIt's in there20:14
Pavoinstalled ansible using yum20:14
*** rhallisey_ has joined #openstack-kolla20:15
kbaegisCould work :)20:15
kbaegisidk20:15
*** ayoung has joined #openstack-kolla20:18
*** rhallisey_ has quit IRC20:20
kbaegisWell, I have an ovsdb-server.log now at least20:20
kbaegisEvidently it requires ovs as a module20:22
kbaegisBreaks on compiling it in.  You guys may want to fix that, idk20:23
kbaegisEasy enough for me to change; I don't personally care for managing kernel modules20:24
kbaegisMore concerningly, this may actually tie the host and guest kernel versions together by necessity.  idk20:26
Pavothis error doesn't make sense20:30
*** egonzalez90 has quit IRC20:32
sdake_kbaegis - that is the openvswitch project's domain20:35
sdake_kbaegis we have no input into their development20:35
sdake_they are pretty much not directly part of openstack20:35
sdake_i mean i could dsend a message to them20:35
sdake_but i'm not sure it would do much :)20:35
sdake_kbaegis we load kernel modules from the host - iirc20:36
Pavosdake mind taking a look at my error20:37
Pavohttps://paste.pound-python.org/show/tXwye4n3DaYxKl95Rv20/20:37
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Start using orchestration_engine variable  https://review.openstack.org/35653820:38
*** bootsha has joined #openstack-kolla20:41
openstackgerritMerged openstack/kolla-kubernetes: Neutron bootstrap to create service/project/role  https://review.openstack.org/35374020:58
kbaegisrecompiled;rebooted;checking to see if ovs will start without redeploy now20:58
*** pbourke has quit IRC21:01
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Adding NOTE for Kubernetes Secret Generator  https://review.openstack.org/35671921:03
*** pbourke has joined #openstack-kolla21:03
*** rhallisey has quit IRC21:04
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Adding NOTE for Kubernetes Secret Generator  https://review.openstack.org/35671921:06
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Adding NOTE for Kubernetes Secret Generator  https://review.openstack.org/35671921:08
*** bootsha has quit IRC21:10
*** jtriley_ has joined #openstack-kolla21:12
*** jtriley has quit IRC21:15
*** michauds has quit IRC21:15
*** ad_rien_ has joined #openstack-kolla21:16
*** jtriley_ has quit IRC21:17
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Modifying Keystone bootstrap to use secrets  https://review.openstack.org/35609821:19
*** kbaegis has quit IRC21:24
sdake_pavo21:25
sdake_i'm beat21:25
sdake_been up since 4am21:25
sdake_need power nap - can it wait21:25
openstackgerritSerguei Bezverkhi proposed openstack/kolla-kubernetes: Adding NOTE for Kubernetes Secret Generator  https://review.openstack.org/35671921:26
*** gfidente has joined #openstack-kolla21:27
Pavosure21:28
kfox1111weird... they make symlinks for configmaps...21:29
*** dwalsh has quit IRC21:31
*** kbaegis has joined #openstack-kolla21:32
*** kbaegis1 has joined #openstack-kolla21:36
*** kbaegis has quit IRC21:37
*** ad_rien_ has quit IRC21:42
*** huikang has quit IRC21:49
*** huikang has joined #openstack-kolla21:50
*** huikang has quit IRC21:55
*** sdake_ has quit IRC22:06
openstackgerritKevin Fox proposed openstack/kolla-kubernetes: Deployment, Readiness, Safe Shutdown, & Scaling for glance-api  https://review.openstack.org/35489522:14
*** jeh has quit IRC22:14
*** inc0 has quit IRC22:14
*** ayoung has quit IRC22:14
kfox1111sbezverk: I think that one's ready for review now.22:15
*** huikang has joined #openstack-kolla22:16
*** tummy has joined #openstack-kolla22:16
kbaegis1sdake_ do you know where the openvswitch module is expected to be found?22:16
*** jeh has joined #openstack-kolla22:17
*** jeh has quit IRC22:17
*** jeh has joined #openstack-kolla22:17
kfox1111sbezverk: with that review, and a ceph backed glance, you should be able to do a no downtime minor version rolling upgrade.22:20
*** JoseMello has quit IRC22:20
*** ad_rien_ has joined #openstack-kolla22:20
*** sdake has joined #openstack-kolla22:21
*** severion has joined #openstack-kolla22:22
*** v1k0d3n has quit IRC22:25
*** tummy has quit IRC22:28
*** huikang has quit IRC22:29
*** huikang has joined #openstack-kolla22:29
*** ad_rien_ has quit IRC22:31
*** huikang has quit IRC22:34
*** sdake has quit IRC22:38
*** egonzalez has joined #openstack-kolla22:48
*** inc0 has joined #openstack-kolla22:49
kbaegis1lol22:51
kbaegis1"modprobe: ERROR: could not insert 'openvswitch': Exec format error"22:51
kbaegis1Great22:51
kbaegis1Falling back to linuxbridging, trying the iptables —flush option22:52
*** vhosakot has quit IRC22:53
*** HyperJohnGraham has joined #openstack-kolla23:12
*** ayoung has joined #openstack-kolla23:19
*** mark-casey has quit IRC23:20
kbaegis1Sadly, no.  iptables —flush didn't work :'(23:27
*** kbaegis1 has quit IRC23:27
*** kbaegis has joined #openstack-kolla23:27
kbaegisOh well23:28
kbaegisis there a way to manually insert those rules?23:33
kbaegisTo see rejections/conflicts?23:33
kbaegisAlright, I'm going to cave and install centos23:34
kbaegis:/23:34
kbaegisNot happy about it, but it'll to in a pinch23:35
kbaegis:)23:35
kbaegisAnd I'd rather have a functioning lab than one done right :)23:35
*** egonzalez has quit IRC23:38
kbaegisWish I knew more than that iptables.manager generically fails on COMMIT23:45
kbaegisI feel like that's solvable23:46
*** zhurong has joined #openstack-kolla23:51
*** diogogmt has quit IRC23:56

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