Thursday, 2015-07-23

*** akwasnie has quit IRC00:01
*** achanda has joined #kolla00:05
*** weiyu_ has quit IRC00:12
*** shadower has quit IRC00:23
*** shadower has joined #kolla00:23
*** bmace has quit IRC00:33
*** jruano has quit IRC00:36
*** bmace has joined #kolla00:45
sdakehttps://bugs.launchpad.net/kolla/+bug/147735100:53
openstackLaunchpad bug 1477351 in kolla "openvswitch-agent must have tty to run sudo" [Critical,Triaged]00:53
*** weiyu_ has joined #kolla01:01
*** erkules has joined #kolla01:10
*** erkules_ has quit IRC01:12
*** weiyu_ has quit IRC01:19
sdakesamyaple when you arise ping me01:31
sdakesamyaple neutron is busted - I think one problem besides we are not starting containers with tty=true, is that br-ex is not being created01:31
sdakein yaodu you create it, in kolla it is uncreated and isn't in the bridge list in ovs01:32
*** jruano has joined #kolla01:32
sdakeyou also create a port, when I try to do this manually I get an error01:32
sdakethe l3 agent needs the br-ex, but its in the namespace of the openvswitch container01:33
sdakealso getting error about ovs-vsctl not found in the neutron-agent container01:35
sdakeI think we probably need to merge the ovs agent into the neutron agents container01:35
sdakeso they run in the same namespace01:35
*** stvnoyes has left #kolla01:45
*** Haomeng|2 has quit IRC01:46
*** dolpher has quit IRC01:52
*** weiyu_ has joined #kolla01:56
*** blahRus has quit IRC02:07
openstackgerritSteven Dake proposed stackforge/kolla: Enable TTY mode for neutron agents for sudo use  https://review.openstack.org/20480902:11
*** unicell has quit IRC02:29
*** dolpher has joined #kolla02:54
*** bradjones has quit IRC03:03
*** bradjones has joined #kolla03:04
*** bradjones has quit IRC03:04
*** bradjones has joined #kolla03:04
sdakehttps://bugs.launchpad.net/kolla/+bug/147737503:14
openstackLaunchpad bug 1477375 in kolla "ERROR The external network bridge 'br-ex' does not exist" [Critical,Confirmed]03:14
openstackgerritSteven Dake proposed stackforge/kolla: Allows neutron-agents l3 agent to communicate with OVS  https://review.openstack.org/20483203:19
*** coolsvap|away is now known as coolsvap03:34
*** jasonsb has joined #kolla03:35
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Add Gnocchi service to kolla  https://review.openstack.org/18079003:43
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Removed unused hautoproxy code  https://review.openstack.org/20456703:51
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Glance installation from source  https://review.openstack.org/20166503:59
*** mordred has quit IRC04:11
*** weiyu_ has quit IRC04:13
*** unicell has joined #kolla04:14
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Removes Host Cleanup from Container Cleanup Script  https://review.openstack.org/18249304:18
*** unicell has quit IRC04:18
*** unicell has joined #kolla04:19
*** daneyon_ has joined #kolla04:22
sdakesamyaple awake yet?04:23
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Removes Host Cleanup from Container Cleanup Script  https://review.openstack.org/18249304:24
*** mordred has joined #kolla04:24
*** daneyon has quit IRC04:24
*** diga has quit IRC04:26
coolsvapsdake, around?04:28
sdakeshoot04:28
coolsvapsdake, regarding the horizon dependency, mod-wsgi, i am bit confused04:29
sdakein which way04:29
coolsvapi added a change set to update it from http-mod-wsgi -> mod-wsgi in binary04:29
coolsvapit was -104:29
coolsvapnow you are asking to change it in source04:29
sdakewho -1'ed it?04:30
coolsvapyou :) https://review.openstack.org/#/c/201497/04:30
sdakei am not perfect04:30
sdakeI wasn't sure so today I ran yum install mod-wsgi04:30
sdakeand it installs04:30
coolsvap:( :(04:30
sdakeyum install httpd-mod-wsgi does not04:30
coolsvapalright updating source and binary both04:31
sdakemaybe centos is different then fedora 2104:31
sdakecould you try building the container04:31
sdakeand see what it says04:31
sdakeit will tell you if it can't find the deepndency04:31
sdakebut it will *NOT* fail to build the container04:32
sdakewhich sucks04:32
sdakewhatever is correct is in keystone04:32
sdakeI know because I fixed keystone and got it working personally04:32
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Update horizon dockerfine for dependencies  https://review.openstack.org/20149704:33
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Add build from source for Horizon  https://review.openstack.org/20244604:35
coolsvapyes building it, it was working fine when i proposed the change, checkign it again04:35
*** diga has joined #kolla04:37
coolsvapyes does not fail while building the container04:44
sdakehttps://ask.openstack.org/en/question/30333/error-unexpected-vif_typebinding_failed/04:50
sdakecoolsvap what do yo uthink that sed command does?04:50
*** dolpher has quit IRC04:50
*** dolpher has joined #kolla04:52
coolsvapi think it changes the plugins/openvswitch/ovs_neutron_plugin.ini to plugin.ini, need to double check though04:54
*** dolpher has quit IRC04:57
*** gfidente has joined #kolla04:57
*** dolpher has joined #kolla04:58
*** diga has quit IRC04:59
* sdake wishes someone would get neutron working05:00
* sdake groans05:00
*** weiyu_ has joined #kolla05:11
* coolsvap having a look at it 05:11
sdakei'm pretty sure the mechanism driver isn't being set properly05:11
*** diga has joined #kolla05:11
coolsvapsdake, maybe a pretty dumb question, but how can i keep different versions of source and binary images in the same host?05:12
sdakewhat do you mean different versions05:12
sdakeyou can use the tag feature05:12
*** weiyu_ has quit IRC05:14
coolsvapi was thinking of adding a script which builds images only for a single service05:20
coolsvaprather than building all images or building each image individually in the service05:20
*** weiyu_ has joined #kolla05:27
sdakeexpand build.py05:27
coolsvaphmm05:32
sdakewe dont need more tools we need the tools weh ave to be better05:37
sdakethe only reason we went with a python builder is because the shell script was too complicated to comprehend ;)05:37
coolsvapyes, i see the TODOs in the build.py, will ask SamYaple if there's anything he's currently not working on05:38
coolsvapalso need to start with ansible05:39
sdakeyes we need ansible finished asap05:39
sdakethe main services are all more or less done although neutron is busted05:39
sdakemaking progress - got the ml2 config file loading now ;-)05:49
coolsvapi need to get my first ansible patch working, then i can build up on that05:51
sdakehttps://bugs.launchpad.net/kolla/+bug/147739905:53
openstackLaunchpad bug 1477399 in kolla "ml2_conf.ini was not being loaded into image" [Critical,Confirmed] - Assigned to Steven Dake (sdake)05:53
sdakeprobably the place to start is to deploy aio with ansible05:53
*** inc0 has joined #kolla05:53
openstackgerritSteven Dake proposed stackforge/kolla: Copy ml2_conf.ini to correct location  https://review.openstack.org/20489105:55
*** jruano has quit IRC06:06
harmwlol was that realy it sdake ?06:46
sdakeharmw its still busted06:47
harmwoh, your working on ansible06:47
sdakebut i'e fixed 3 problems so far06:47
sdakei keep hoping samyaple will show up to rescue me :)06:47
harmwi had that vif_bind issue last week06:48
sdakeyou fixed it?06:48
harmwcouldn't realy find where it was busted though06:48
harmwno06:48
harmwsad story06:48
sdakeit is broken in atlaest 3 places06:48
sdakethere are patches up for the 3 I know about06:48
harmwok06:48
harmwwell it made me move to checking out ansible instead :p06:49
harmwwhich brings completely different bugs on the table06:49
sdakeya that is what i'm using, ansible deosn't nova boot06:49
sdakevif bind problem06:49
harmwmechanism drivers were complaining in neutron logs iirc06:49
harmwbtw, barbican is failing to build because of some pip dependency issue06:50
harmwswift fails because it can't find files or whatever06:50
harmwall the others should be pushed06:50
harmw*centos-rdo-binary06:50
sdakenice06:50
sdakewould have been nice to just use linuxbridge since that worked ;(06:51
harmwnah, OVS should just work06:51
sdakeit does not even after the implementation bugs are fixed06:51
harmwI had it working in some old deployment like months ago :p06:51
sdakemust be a configuration prolem06:51
sdakeyes I mean we don't know how to configure ovs06:51
sdakewe have linuxbridge down06:51
*** bmace has quit IRC06:53
sdakeprior to my patches the openvswitch code wasn't even loading in the nasible implementation of neutron06:53
harmwhehe I can see that06:53
harmwnice06:53
harmwit realy is nice to see people start playing with the ansible code now06:54
harmwand uncovering bugs as they go06:54
sdakeid' prefer it just work06:55
sdakeI've ben throug this rpocess bout 3 or 4 times with various implementations06:55
* sdake tired of debugging neutron + nova integration06:55
harmwhehe06:55
harmwoh yes06:55
harmwarent' we all06:55
sdakethe worst part is i'm stuck, I don't know how to proceed06:56
sdakethe logs have nothing useful06:56
harmwthat was my issue aswell06:56
harmwhurray for neutron and nova06:57
sdakesee daneyon figured all this shit outwith linuxbridge ;)06:57
harmwlinuxbridge didn't have much shit, that also helps :p06:57
sdakeprecisely06:57
sdakehttp://openvswitch.org/pipermail/discuss/2010-November/004516.html07:01
sdakethis is where I'm at07:01
harmware the right OVS sockets shared between containers?07:02
inc0good morning07:03
harmwhi inc007:04
harmwgod I hate being behind a proxy07:04
inc0I know the pain07:04
*** bmace has joined #kolla07:05
inc0let me read through your discussion because it sounds interesting;)07:05
harmwcan't be07:05
harmwit involved sdake07:05
sdakethe annoying part is ovs-vsctl executed via docker exec works fantastically07:05
inc0how about having ovs-db outside container?07:06
inc0let me check how ovs is configured currently07:07
sdakeoh snap i figured something out07:07
sdakerunning ovs-vsctol works07:07
sdakerunning within neutron-rootwrap does not!07:07
sdakethis is the problem07:07
inc0does neutron-rootweap even have ovs-vsctl?07:07
harmwuhm, why isn't neutron complaining about that07:07
sdakethere apparently must be some filter files07:12
sdakeprobably not installed07:12
sdakedefinately not installed07:17
inc0so, installation of vsctl might help07:19
inc0I didn't know neutron rootwrap even uses it07:19
sdakei already installed openvswitch which includes ovsctl dude07:20
sdakethe filters come from the neutron-server package07:20
sdakei am just going to copy them in07:20
*** daneyon_ has quit IRC07:20
*** daneyon has joined #kolla07:21
sdakespending 4 minutes running ansible has the same feeling as building images........................07:30
sdakeharmw can you check if from source installs filters?07:32
sdake /etc/neutron/rootwrap.d07:33
*** jmccarthy has quit IRC07:33
*** jmccarthy has joined #kolla07:33
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Make variables in OVS container configurable  https://review.openstack.org/20493907:55
*** achanda has quit IRC08:13
*** achanda has joined #kolla08:16
*** zhiwei has joined #kolla08:18
*** achanda has quit IRC08:21
harmwhm, some docs on the whole build-from-source would be nice08:26
harmwgod I should just reset my LP password and start filing bugs this instant, instead of tonight08:26
openstackgerritSam Yaple proposed stackforge/kolla: Removed unused hautoproxy code  https://review.openstack.org/20456708:28
SamYaplesdake: ping08:29
sdakehey sam08:29
sdakei fixed 3 bugs with neutron08:29
SamYaplewhats up08:30
SamYapleoh yea08:30
sdakeand I have another one i'm working on08:30
sdakeya so it should actually work now vs not as it didn't before ;-)08:30
SamYaplethats probably right. i only tested the agents started08:30
sdakeya gotta tet nova boots08:30
SamYaplegotta get more timei n the day!08:31
SamYapleits my weekend now08:31
*** shardy_ has joined #kolla08:31
sdakerunning ansible over and over is like building images08:32
SamYaplefor fresh reruns, yea08:32
*** shardy has quit IRC08:32
sdake4 minutes 9 seconds08:33
sdakewait around08:33
sdakesamyaple is shade supposed tobe installed on every node inteh cluster?08:35
harmwyep08:35
SamYapleyea08:35
SamYaplebut i dont like that, i want a container that handles this08:36
sdakewe need to put it in a container in some way then, it has a million dependencies08:36
SamYapleyup08:36
*** shardy_ has quit IRC08:36
SamYapleissue is ansible modules wont work like that08:36
SamYaplewe would have to run an ssh server inside that container08:37
SamYapleim not sure how i want to solve it, but i really dont like that idea08:37
sdakeI think that is ok tradeoff comapredt o installing a ton of deps jus tfor 1 library08:37
*** shardy has joined #kolla08:37
SamYapleyou dont understand the implications08:37
inc0SamYaple, how about ssh to host and docker exec stuff?08:40
inc0instead of ssh to container?08:40
SamYaplethat breaks ansible modules inc008:41
sdakewell we dont want to install 100's of packages just to deploy openstack08:41
inc0why? I meant that ansible can do that08:41
sdakethat nullifies the entire point of containers08:42
SamYapleinc0: that breaks ansible modules. they cannot do that.08:42
inc0ansible modules can do docker exec...08:42
sdakesamyaple these commands need to be done08:42
sdake# ovs-vsctl add-br br-eth008:42
sdake# ovs-vsctl add-port br-eth0 eth008:42
SamYaplesdake: yea i just remembered about those08:42
SamYapleinc0: no we are speaking differently here. ansible modulescannot work like that08:43
sdakealso the interface for ml2_conf.ini is neutron_interface, but it needs to be a bridge08:43
sdakeI wasn't quite sure how to fix it08:43
SamYaplesdake: no it doesnt08:43
sdakeit does need to be a bridge I can assure you08:43
sdakeif it is not, the agent blows up08:44
SamYapleyou are wrong or we are talkign about different things08:44
*** achanda has joined #kolla08:44
sdakewhy dont you pull my patch stream and try a nova boot08:44
sdakethe docs say [ovs] bridge_interfaces has to be a bridge, not a regualr nic08:45
sdakethe code bombs out if its not a bridge08:45
SamYapleoh that. yea but neutron_interface is supposed to be a bridge08:45
SamYaplehow else would you be able to name it?08:46
SamYaplefyi guys i just woke up08:46
inc0sdake, which line of code checks that? Could you please point me to it?08:46
SamYaplehttps://github.com/stackforge/kolla/blob/master/ansible/roles/neutron/templates/ml2_conf.ini.j2#L3508:47
inc0because as I understand, it doesn't show as bridge in neutron container08:47
inc0even if it might be one due to net-host and ovs being configured in other container?08:47
SamYapleinc0: no that line needs to be a bridge08:47
SamYapleits the ovs bridge you create08:47
SamYapleneutron does not create that ovs bridge08:47
inc0yes, but in which container you create bridge?08:48
inc0manually?08:48
SamYaplethat is the way it goes, yes08:48
inc0let me answer that, ovs container08:48
SamYapleand not in the container08:48
inc0outside container?08:48
SamYaplei mean yea but it doesnt stay there08:48
*** mickt has joined #kolla08:48
inc0I know, net-ost08:48
SamYapleoh jeez ill be back in 1008:48
inc0and I'll run your code sdake - I want to see traceback;)08:49
micktQusetion regarding build versus build --release; What is the difference, i.e. what is "release" supposed to have above other?08:49
SamYaplefuck08:49
harmwmickt: it tags it as latest08:50
inc0mickt, it also marks your new image as latest08:50
sdakemickt --release tags with "latest"08:50
SamYaplesdake: i didnt have my latest neutron shit uploaded beforei t merged08:50
sdakewithout release, it tags with whatever the hash is08:50
inc0its equivalent to docker tag your-img-id latest08:50
SamYaplesdake: https://review.openstack.org/#/c/204891/08:50
sdakewell i've spent lsat 8 hours fixing bugs08:50
SamYaplecan i take over that patch? i have the code for it08:50
pbourkei think what mickt is asking is why not just tag everything latest08:50
SamYaplesdake: it needs 4 more ections08:50
micktso it just identifies it as latest, doesn't mean it's fully tested or better etc.08:50
sdakeknock yurself out08:51
sdakesamyaple there are other patches inthte stream08:51
inc0mickt, it just add tag, nothing more08:51
SamYaplesdake: yea ive reviewed them08:51
sdakethere is also one more patch I have08:51
SamYaplealready reviews08:51
sdakeletm e add it on08:51
sdakeso you can do what you like with it, i'm going to bed shortly08:51
harmwTASK: [nova | Cleaning up boostrap container] *********************************08:51
harmw<support01> REMOTE_MODULE docker state=absent name=bootstrap_nova image=kollaglue/centos-rdo-nova-api:latest08:51
harmwwonder why that takes forever08:52
openstackgerritSteven Dake proposed stackforge/kolla: Add filters so neutron rootwrap doesn't timeout  https://review.openstack.org/20495508:53
sdakesamyaple if you ilke you can take over that patch stream and get nova into booting state - i'd love you long time for it :)08:54
SamYapleyea this is all my screwup08:54
sdakeso I can do heat support08:54
SamYapletheres a bunch of code here i didnt git-review08:54
sdakeits all good I learned alot about how all this stuff works08:55
SamYaplei feel like a tool08:55
SamYapleall that wasted time08:55
micktto rephrase, why bother, why just not use latest as default08:55
micktdon't see much value08:55
SamYaplemickt: the new build script does use latest as the default08:55
harmwmickt: we can also tag our releases :)08:55
harmwkilo, juno, etc08:55
harmwthat way you can pull containers from a certain release08:55
sdakemickt I agree it would maek more sense to tag latest as default08:56
harmwinstead of the latest and gratest, which has a higer probability of failing08:56
inc0sdake, you use ansible all-in-one in your tests right?08:56
sdakemickt and offer the other type of tagging as non-default08:56
sdakehowever, that isn't how the code was written ;-)08:56
SamYaplesdake: the filters don't need to be hardcoded like that. those files exist in the container and can be copied08:56
SamYapleright?08:56
sdakeinc0 ya aio08:56
sdakesamyaple I couldn't find them in the container08:56
sdakesamyaple they come from the neutron-server package only08:57
sdakenot the agents package...08:57
sdakenot sure about from source, but from binary they have to be hard coded or neutron-server needs to be installed in all containers08:57
SamYaplesdake: /usr/share/neutron/rootwrap/08:57
sdakethat may be in neutron-server08:58
SamYaplenope08:58
sdakebut i didn't see it in the agent08:58
SamYapleits in the agents08:58
SamYaplefilters_path=/etc/neutron/rootwrap.d,/usr/share/neutron/rootwrap08:58
sdakepretty sure it isn't because once I put it in, i stopped having error 14 timeouts08:58
SamYapleand the filter paths already check that08:58
sdakeyes but there are no filter files in that directory08:58
SamYaplesdake: im looking at it08:58
sdakein which agent container?08:59
SamYapleroot@server02:~/kolla# docker run --rm -it kollaglue/centos-binary-neutron-agents bash08:59
SamYaple[root@6c3e3df11f18 /]# ls /usr/share/neutron/rootwrap/08:59
SamYapledebug.filters  dhcp.filters  ebtables.filters  ipset-firewall.filters  iptables-firewall.filters  l3.filters08:59
sdakewrong agent container08:59
sdaketry ovs agent container08:59
SamYapleah ok ill check08:59
SamYaplewe need thin containers08:59
SamYapleroot@server02:~/kolla# docker run --rm -it kollaglue/centos-binary-neutron-openvswitch-agent bash09:00
SamYaple[root@d6bffe6c8bb1 /]# ls /usr/share/neutron/rootwrap09:00
SamYapledebug.filters  ebtables.filters        iptables-firewall.filters  openvswitch-plugin.filters09:00
SamYapledhcp.filters   ipset-firewall.filters  l3.filters09:00
sdakeinteresting09:00
sdakewell i'm off to bed - 2am here :)09:00
sdakefeel free to rebase and drop patches/abandon patches as necessary09:00
sdakeif you get nova booting I'll love you long time :)09:00
SamYaplewill do09:01
SamYaplethanks for all the debug09:01
SamYaplesorry for missing code09:01
SamYaplenova should be up by morning09:01
SamYapleinc0: re: ansible modules ssh09:01
SamYapleansible modules run on the host they ssh to. you cannot docker exec and run the ansible module in that docker container09:02
SamYapleyou have to ssh into that docker container which we cannot do for a whole slew of reasons09:02
openstackgerritSam Yaple proposed stackforge/kolla: Copy ml2_conf.ini to correct location  https://review.openstack.org/20489109:14
openstackgerritSam Yaple proposed stackforge/kolla: Removed unused hautoproxy code  https://review.openstack.org/20456709:19
inc0SamYaple, but you can ssh to host and execute commands in docker using docker exec09:27
SamYapleinc0: that beaks modules09:27
SamYaplewhere is the disconnect here09:27
inc0thats how I hot reload configs in haproxy09:27
SamYapleyea, but thats not an ansible module you are using09:28
inc0I run ansible's command module09:28
SamYaplegreat. now how do you do this without the command module?09:28
SamYaplesay, for the modules that need to use the shade library?09:28
inc0why modules *need* to use shade?09:30
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Glance installation from source  https://review.openstack.org/20166509:30
SamYapleim not prepared to have this discussion again. the mailing list should hold all the answers for you09:31
inc0ok...I'll dig through this and we'll talk later09:31
inc0also I'll play around this neutron bug09:31
inc0afk for now09:31
SamYaplewhich one09:31
inc0lack of ovs bridge09:31
SamYapleyea i have that working. i just have to create teh bridge like i do in yaodu09:32
inc0cool, I'll take a look;)09:32
SamYaplealways good to have more eyes09:32
inc0brb for now09:32
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Update horizon dockerfile for dependencies  https://review.openstack.org/20149709:36
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Update service helper scripts for variable changes  https://review.openstack.org/20393509:38
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Update service helper scripts for variable changes  https://review.openstack.org/20393509:38
openstackgerritMerged stackforge/kolla: Add memcached image (required by Swift)  https://review.openstack.org/20249309:38
*** diga has quit IRC09:50
*** erkules has quit IRC09:53
*** erkules has joined #kolla09:53
*** weiyu_ has quit IRC09:53
*** weiyu_ has joined #kolla09:54
dolpherAnyone can take a look at this simple changes? it needs another +2 review.  https://review.openstack.org/#/c/203939/09:55
SamYapledolpher: done09:56
dolpherThanks SamYaple09:57
openstackgerritMerged stackforge/kolla: Add get_or_create_domain for designate sink  https://review.openstack.org/20393909:58
*** gfidente has quit IRC09:59
*** dolpher has quit IRC10:00
*** gfidente has joined #kolla10:01
*** athomas has quit IRC10:02
inc0SamYaple, merge_configs is not a legal parameter in an Ansible task or handler  - how do you add library dir to ansibles PATH?10:06
openstackgerritPaul Bourke proposed stackforge/kolla: Install correct crux in centos-source-base  https://review.openstack.org/20497710:06
SamYapleinc0: its a relative path (though i think there is a global)10:07
harmwinc0: ~/.ansible.cfg, or make sure the library folder lives in your .10:07
inc0hmm...it should10:08
harmwhttp://docs.ansible.com/ansible/intro_configuration.html#library10:08
inc0thanks10:08
harmwhe SamYaple, you've tested the multinode setup?10:08
harmw(ansible)10:08
inc0however, it is  in ./library so that should work too10:09
inc0debug time!10:09
harmwyep inc0 :)10:09
*** athomas has joined #kolla10:10
SamYapleharmw: yea. except for neutron. working on that now10:10
harmwany thoughts on when it'll be done?10:14
SamYapleyoull be able to boot an instance multinode by L210:14
*** zhiwei has quit IRC10:15
harmwah, thats probably not today :p10:15
SamYaplei plan on having it working today, but i wont promise it until L210:16
harmwI'm just eager to try it out10:16
SamYaplethis is the first chance ive had to work on it uninteruppted in almost 2 weeks10:16
vbelGood morning/afternoon/evening folks. I am going to fix naming error. Are we to use CONFIG_INTERNAL or CONFIG_INSIDE?10:18
SamYaplevbel: internal and external at the names10:19
vbelI mean:10:19
vbel> grep -r CONFIG_INSIDE .10:19
vbel./specs/ansible-multi.rst:CONFIG_INSIDE.10:19
vbel./specs/ansible-multi.rst:CONFIG_INSIDE model, the community will repair it.10:19
vbel./specs/ansible-multi.rst:The CONFIG_INSIDE model of configuration maintains the immutable,10:19
vbel./specs/ansible-multi.rst:    CONFIG_STRATEGY="CONFIG_INSIDE"10:19
vbel./specs/ansible-multi.rst:CONFIG_INSIDE will match the current crudini.sh implementation.10:19
vbel./specs/ansible-multi.rst:        CONFIG_INSIDE)10:19
vbel./specs/ansible-multi.rst:    CONFIG_INSIDE - no bind mount10:19
vbel> grep -r CONFIG_INTERNAL .10:19
vbel./compose/openstack.env:KOLLA_CONFIG_STRATEGY=CONFIG_INTERNAL10:19
vbel./docker/common/base/kolla-common.sh:        CONFIG_INTERNAL)10:19
vbel./docker/common/neutron/neutron-dhcp-agent/start.sh:        CONFIG_INTERNAL)10:19
vbel./docker/common/neutron/neutron-l3-agent/start.sh:        CONFIG_INTERNAL)10:19
vbel./docker/common/neutron/neutron-metadata-agent/start.sh:        CONFIG_INTERNAL)10:19
vbel./tools/genenv:KOLLA_CONFIG_STRATEGY=CONFIG_INTERNAL10:19
vbelSamYaple: ok!10:19
SamYaplevbel: yea the spec is outdated. done worry about fixing that10:20
SamYaplethe code is correct10:20
vbelok, great :)10:20
openstackgerritSam Yaple proposed stackforge/kolla: sudoers script was not properly running  https://review.openstack.org/20499410:21
openstackgerritPaul Bourke proposed stackforge/kolla: Install correct crux in centos-source-base  https://review.openstack.org/20497710:24
*** coolsvap is now known as coolsvap|away10:27
*** akscram has quit IRC10:33
*** zhiwei has joined #kolla10:34
*** akscram has joined #kolla10:35
inc0which version of ansible are you running?10:36
SamYaple1.9.210:40
SamYaple2.x is broked10:40
*** dims_ has joined #kolla10:52
*** zhiwei has quit IRC10:52
*** rhallisey has joined #kolla11:16
*** weiyu_ has quit IRC11:36
*** inc0_ has joined #kolla11:44
*** inc0 has quit IRC11:44
*** vbel has quit IRC11:50
*** vbel has joined #kolla11:50
*** dims_ has quit IRC12:02
*** dwalsh has joined #kolla12:04
openstackgerritSam Yaple proposed stackforge/kolla: Adds the appropriate tools to addin the ovs bridge  https://review.openstack.org/20502912:12
harmwSamYaple: why don't you just use $? on L7 of ovs_ensure_bla?12:15
openstackgerritSam Yaple proposed stackforge/kolla: Adds the appropriate tools to addin the ovs bridge  https://review.openstack.org/20502912:15
SamYapleharmw: thats really not best practice12:16
SamYapleif you do that and you refactor you can screw up the code its checking without knowing it12:16
harmwif thats the case one should be a bit more careful in their actions when refactoring12:18
harmwbut fair enough12:18
SamYapleor you can write better code like this12:18
SamYaplepreferably both happens12:18
harmwwith this neutron just works?12:19
SamYaplethis and 3-4 other patches12:19
SamYaplethey are sitting in review12:19
harmwcool12:19
harmwI didn't look into any of them yet though12:19
harmwdoes this involve multinode or is that a completely different set?12:20
SamYaplei have no clue. havent tested a clean system yet12:20
SamYaplethis should work with multinode12:20
SamYaplethere is no mutlinode specific code if thats what youre asking12:21
harmwill probably spin something up tonight12:21
harmwsee what happens12:21
SamYapleyea just document what breaks12:21
harmwofcourse12:21
harmwLP is my friend :)12:22
SamYaplealso youll probably want to wait for the patches to merge12:22
harmwoh I'll get them in first12:22
harmwnot gonna wait for a proper merge, because of $time12:22
SamYaplei feel bad for sdake12:23
harmwhehe12:24
SamYaplei made him test neutron when half the patchset was sitting in my local branch12:24
SamYaple:/12:24
SamYaplei never git reviewed12:24
*** weiyu has joined #kolla12:27
*** prad has joined #kolla12:41
*** diogogmt has quit IRC12:44
openstackgerritSteven Dake proposed stackforge/kolla: Add filters so neutron rootwrap doesn't timeout  https://review.openstack.org/20495512:54
openstackgerritSteven Dake proposed stackforge/kolla: Allows neutron-agents l3 agent to communicate with OVS  https://review.openstack.org/20483212:54
openstackgerritSteven Dake proposed stackforge/kolla: Enable TTY mode for neutron agents for sudo use  https://review.openstack.org/20480912:54
openstackgerritSteven Dake proposed stackforge/kolla: Copy ml2_conf.ini to correct location  https://review.openstack.org/20489112:54
SamYaplesdake: why are you breaking my patches?12:54
sdakemorning12:56
sdake4 hrs of ssleep = groan12:56
sdakeyou should feel bad for me samyaple12:57
SamYaplei only kinda do12:57
sdakesamyaple I was just putting https://review.openstack.org/#/c/204832/ at the front12:58
sdakeand then was going to abandon the others12:58
sdakewould you prefer some other course of action12:58
sdakeharmw if youw ant to ack https://review.openstack.org/#/c/204832/ that would work - or rhallisey if your around12:58
SamYapleor pbourke12:58
SamYaplei got your back pbourke12:58
SamYaplei wont forget about you12:58
sdakeit woudl make the most sense if you edited my change ids with your solutions to hte problems12:58
sdakelike the removing tty support requirement for sudo, I have no idea how to do that12:58
SamYaplesdake: i meant to, i accidentally made a new patchset ;)12:59
sdakesamyaple are you working on a rebase of that patch stream or your own patch stream12:59
pbourkewill ahve a look12:59
pbourke*have12:59
SamYaplesdake: as you can see, you overrode my patch here https://review.openstack.org/#/c/204891/12:59
sdakeoh my bad13:00
sdakecan you resubmit with that one patch reordered13:00
SamYaplei can indeed13:00
SamYapleeverything is functional, testing booting now btw13:00
openstackgerritSam Yaple proposed stackforge/kolla: Copy ml2_conf.ini to correct location  https://review.openstack.org/20489113:01
harmwsdake: I will ack stuff once I get home13:01
harmwsome hours from now13:02
SamYaplesdake: the tty thing we fixed in config-internal a long time ago13:02
SamYaplesdake: i just wasnt sourcing it properly. we share that code now13:02
sdakeok13:02
sdakeare all your patches in the review queue?13:02
SamYapleyup13:02
sdakecool i'll hit it13:02
sdakeand nova boots now?13:03
sdakeor still no boot13:03
SamYapleim checking it now13:03
SamYaplesetting up images and what not13:03
SamYapleports work and communicate properly13:03
sdakepbourke mind hitting the review queue with me so we can get this stuff merged13:04
pbourkesdake: sure13:04
pbourkecan I get a one liner of context? was scanning logs from last night but only picked up something something neutron13:06
pbourkejust beating it into shape?13:06
SamYapledamn vif_binding failed. lemme figure out why13:06
SamYaplei hate this error13:07
pbourkesdake: ^13:07
sdakepbourke related to neutron not working with nova booting an instance13:07
sdakeI spent about 8 hours debugging various problems with it13:07
sdakeand fixed about 3 or 4 things, apparently incorrectly :)13:08
SamYaplethat i had sitting in my local branch :(13:08
SamYaplei really feel bad about that one13:08
sdakewell if you fix the current vif binding failed, then no hard feelings :)13:08
sdakethe last place I got was that the agents kept restarting13:09
SamYaplenah thats all good now13:09
SamYapleno filters needed13:09
SamYaplewell filters needed, but they are in teh right place13:09
sdakepbourke https://review.openstack.org/#/c/204994/13:09
pbourkeok sounds good13:09
sdakepbourke you can do search field "owner:sam@yaple.net"13:09
SamYaplehttps://www.youtube.com/watch?v=Gtffv9bpB-U13:10
sdakesamyaple one of those containers I had to add openvswitch to to get ovs-vsctl13:11
sdakedid you do that?13:11
*** jruano has joined #kolla13:11
sdakethe openvswitch-agent container13:11
SamYaplesdake: yea its in one of those patches13:12
sdakeI see you fixed bridge_mappings :)13:13
SamYapleyea i realized you were right and that would get confusing13:13
sdakesamyaple that introduction of openvswitch.rpm is not present in any of your patches to the openvswitch_agent13:15
openstackgerritMerged stackforge/kolla: sudoers script was not properly running  https://review.openstack.org/20499413:15
SamYaplein the neutron-base13:16
sdakeyou only had  patches outstanding that I saw13:17
sdakeand neither of them modified neutron_base13:17
SamYaplelies at least the sudoers did. im looking for it13:17
sdakesudoers script just merged13:18
sdakepbourke https://review.openstack.org/#/c/204891/13:18
sdakethere is no change to any dockerfiles in 20499413:18
SamYapleits there sdake13:20
SamYapleits just in your patchset ;)13:20
SamYaplehttps://review.openstack.org/#/c/204832/13:20
sdakepbourke openvswitch is needed in that review because it brings in ovs-vsctl13:21
sdakeovs-vsctl is run via sudo rootwrap by the agent python code13:22
SamYaplesdake: i think he is saying we can remove it other places13:22
SamYaplebut we dont need to remove them other places13:22
SamYaplei understand its some dup right now, but it will be needed when we go to thin containers again13:22
sdakei think we dont want ipc we want rpc13:22
sdakebut anyway discussion for later13:22
SamYaplethats not the discussion13:23
sdakeI dont see how that agent is supposed to work on a different node13:23
SamYapleits not13:23
SamYaplethats not what were talking about13:23
sdakei know, I hanged subjects13:23
pbourkeSamYaple: if its in base it will work for thin13:23
SamYaplepbourke: but i dont want it in all containers13:23
pbourkeok13:24
SamYaplewhat you arre saying is not wrong pbourke, i just dontw want to remove it other places at this time13:24
pbourkethat's fine13:24
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Make variables in OVS container configurable  https://review.openstack.org/20493913:24
sdakepbourke can you chane your vote then on https://review.openstack.org/#/c/204832/213:25
pbourkedone13:27
openstackgerritMerged stackforge/kolla: Copy ml2_conf.ini to correct location  https://review.openstack.org/20489113:27
pbourkeopenvswitch_vswitchd13:27
pbourkeSamYaple: I'm trying to figure out where this container comes from?13:27
pbourkehttps://review.openstack.org/#/c/205029/2/ansible/roles/neutron/tasks/start.yml13:28
openstackgerritMerged stackforge/kolla: Allows neutron-agents l3 agent to communicate with OVS  https://review.openstack.org/20483213:28
sdakeits buit in the ovs directory13:28
SamYaplepbourke: thats the name of the container. the image is ovs-vswitchd13:29
pbourkewhere is it started13:30
SamYapleansible starts it13:30
pbourkekolla_openvswitch_vswitchd_container_name: "ovs-vswitchd"13:31
pbourkename is wrong?13:31
openstackgerritJames McCarthy proposed stackforge/kolla: Swift Containers  https://review.openstack.org/20217113:31
SamYaplepbourke: no13:31
*** inc0_ has quit IRC13:33
pbourkeok I can take your word on it13:33
pbourkefinal question - should you be using the variable for this command13:33
*** jtriley has joined #kolla13:34
SamYaple? which command13:36
pbourkethe docker exec in https://review.openstack.org/#/c/205029/2/ansible/roles/neutron/tasks/start.yml13:36
SamYapleno the container names are not configurable13:36
SamYaplethat variable should be "kolla_openvswitch_vswitchd_image_name"13:37
SamYaplei noticed that a while back but ill clean it up all at once13:37
sdakeall /usr/share and /opt needs to go in /var/lib while your about it ;)13:38
SamYaplesdake: what?13:38
SamYaple/opt/kolla is staying /opt/kolla or goign to /etc/kolla13:38
SamYaplethose are configs13:38
sdake /var/lib is where persistent data is stored13:39
sdake /usr/share is where shared data that doesn't change is stored13:39
SamYaple/usr/share is wrong13:39
SamYaplethere is a todo about that already13:39
sdake /var/lib would be better then /opt13:39
SamYapleits for configs that the enduser can modify13:39
SamYaple /etc13:39
sdakeyes I suppose although they are loaded on the remote system so they aren't exactly /etc files13:40
sdakebut anyway /opt is definately wrong ;)13:40
SamYaplethey are becaue you can modify them on the remote system13:40
SamYapleeh i dont disagree13:40
openstackgerritMerged stackforge/kolla: Adds the appropriate tools to addin the ovs bridge  https://review.openstack.org/20502913:40
SamYapleboth those changes are two lines in an ansible config13:41
SamYapleand probably a few hours of fighting13:41
*** shardy_ has joined #kolla13:42
*** pbourke has quit IRC13:43
*** pbourke has joined #kolla13:44
*** dims_ has joined #kolla13:44
*** shardy has quit IRC13:44
pbourkesdake: I think I've reviewed everything except the rootwrap filters which I will need to do some reading on to understand. ping me any I've missed13:44
sdakesam claims we dont need the rootwrap filters13:44
sdakeso i'lll test master now13:44
sdakeand likely find i still can't boot nova13:45
SamYaplesdake: i dont claim that!13:45
*** dims_ has quit IRC13:45
SamYaplei say they are already there13:45
SamYapleand they are13:45
sdakethats what i mean13:45
*** dims_ has joined #kolla13:45
SamYapleyou should check13:45
sdakewhere are they preciesely?13:45
SamYaple/etc/neutron/rootwrap.conf13:45
sdakethey need to be in /etc/neutron/rootwrap.d13:45
SamYaplethat will tell you where it looks13:45
SamYapleno they dont13:45
SamYaplethey _can_ be there13:46
sdakepretty sure that is what rootwrap.conf says13:46
sdakeor alternatelively /usr/share13:46
sdakeas I recall they were in neither place13:46
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Update scipts for variable changes  https://review.openstack.org/20393513:46
SamYaplethere are in /usr/share13:46
SamYapleyou shoudl ook13:46
sdakewill do13:46
SamYaplei showed you last night13:46
sdakewhen at 2am?13:46
SamYapleindeed13:46
SamYapleStderr: ip6tables-restore v1.4.21: ip6tables-restore: unable to initialize table 'raw'13:47
SamYapletis why vif_failed13:47
*** shardy_ has quit IRC13:48
*** shardy has joined #kolla13:48
sdakenice13:49
sdakewhich container was that in13:50
SamYapleneutron-openvswitch-agent13:50
sdakei am rebuilding atm13:51
sdakeyou need /lib/modules i suspect13:52
sdakesamyaple ^^13:52
SamYapleyea already added13:52
SamYaple(i cheated, i checked yaodu)13:52
sdakelol13:52
sdakeis openvswitch gent run on every compute node?13:53
SamYapleyes13:53
SamYaplewell unless they want linuxbridge of course13:53
*** prad has left #kolla13:53
sdakehow does it communicate with the db - ovs-vsctl expects to use unix sockets for comms13:54
SamYapleopenvswitch runs on every compute node13:54
sdakethe ovs db does as well?13:54
SamYaple /run is bound around13:54
SamYapleyes13:54
SamYaplethey are a pair13:54
sdakegot it thanks13:54
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Update service helper scripts for variable changes  https://review.openstack.org/20393513:55
sdakekolla requires setting 5 config values13:59
sdakewe ought to make password.yml autogenerate securely at oem point13:59
sdakeif someone is looking for work to do ;)13:59
openstackgerritJames McCarthy proposed stackforge/kolla: Swift Containers  https://review.openstack.org/20217114:00
SamYaplesdake: yea we really should14:03
SamYapleStderr:  execute /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:13514:03
SamYaple2015-07-23 14:01:51.880 1 DEBUG neutron.agent.linux.utils [req-dac20874-aa98-455c-9dc5-9ccbec26b805 - - - - -] Running command: ['ps', '--ppid', '178', '-o', 'pid='] create_process /usr/lib/python2.7/site-packages/neutron/agent/linux/utils.py:8514:03
SamYaple2015-07-23 14:01:51.911 1 DEBUG neutron.agent.linux.utils [req-dac20874-aa98-455c-9dc5-9ccbec26b805 - - - - -]14:03
SamYapleCommand: ['ps', '--ppid', '178', '-o', 'pid=']14:03
SamYaplethats breaking neutron openvsiwthc agent14:03
SamYapleExit code: 114:03
sdakewhich ps --ppid 178 -o pid=?14:03
*** inc0 has joined #kolla14:04
sdakehey inc014:04
SamYapleroot       178  0.0  0.0  45544  4416 ?        S    13:56   0:00 /bin/ovsdb-client monitor Interface name,ofport,external_ids --format=json14:04
inc0hello14:04
sdakewhy do you think its breaking the agent it didn't return an error14:04
SamYaple14:03 < SamYaple> Exit code: 114:05
SamYapleare you saying that is a good error code?14:05
* SamYaple doesnt know14:05
SamYapleits normally bad14:05
sdakei am not sure14:06
sdakeit should say "ERRROR" in big caps if there is a problem14:06
SamYaplelol14:07
SamYaplenot neutron14:07
sdakewhat happens when you run ps --ppid 178 -o pid=14:07
sdakeand type echo $?14:07
*** unicell1 has joined #kolla14:16
*** unicell has quit IRC14:17
*** stvnoyes has joined #kolla14:17
sdakerunning ainsible now samyaple14:18
SamYapleok14:18
SamYapleovs is being wierd14:18
SamYaplenot sure if its ovs thats the issue though14:18
sdakeman canonical never giong to give up on juju14:19
sdakegot to hand it to them, they got thier ass handed to them by heat and docker and still keep trying ;-)14:19
SamYaplethey really like juju14:20
sdakejuju had the same vision docker has executed14:20
vincent_vdkanyone who has actually used it?14:20
sdakelike 2 years before docker existed14:20
sdakejuju is highly unreliale14:20
SamYaplei tried it14:20
SamYapleit is bad14:20
vincent_vdk:)14:20
sdakeits a packaging format14:21
vincent_vdkhad to deal with Ubuntu today14:21
sdakethink what docker is14:21
vincent_vdkit;s a bit the same i guess14:21
sdakebut the thing is, it doesn't have a docker ecosystem14:21
*** diogogmt has joined #kolla14:22
openstackgerritJames McCarthy proposed stackforge/kolla: Swift Containers  https://review.openstack.org/20217114:23
sdakemaster no bueno14:25
SamYaple?14:25
sdakestill get binding_failed14:27
sdakeafter adding /lib/modules to hte bindmounts14:27
sdakeno errors in the ovs agent14:27
SamYapleyup14:27
SamYaplei think i have a thread on the issue14:28
* SamYaple checked all the leftover uncommited code14:28
*** diogogmt has quit IRC14:29
sdakepaste diff?14:29
SamYapleim not copying any of the l3_agent.ini dhcp_agent_ini metadata_agent.ini files ;)14:29
SamYaplei mean i am in the uncommited branch... but not on master xD14:29
sdakecan you git diff | paste?14:30
sdakecan't you I mean14:30
SamYaplewhy am i git diffiing?14:30
sdakeyou aid you had it fixed in your branch?14:31
SamYaplein the original neutron branch14:31
SamYaplei never git-reviewed the final commit i did14:31
sdakemy question is do you have a solution to nova booting or are we back in debug mode14:32
*** weiyu has quit IRC14:32
SamYaplei dont know im testing14:32
SamYapledo you see a clear problem?14:32
SamYaplebecause i dont14:32
sdakejust the vif thing14:33
sdakeother then that, I dont see anything helpful14:33
SamYaplethats not a clear problem :P14:33
SamYaplevif just means go check neutron14:33
sdakeml2.managers failed to bind port14:34
sdakethe "physical network" is "None" in the debug logs14:35
sdakethat could possibly be a problem14:35
SamYapleare you doing a flat network?14:36
*** weiyu has joined #kolla14:37
sdakei am diong whatever the default is for init-runonce14:38
SamYaplei dont know what that is so find out if you are doign a flat14:38
SamYapleflat is not configured14:38
sdaketools/init-runonce14:38
sdakeits the thing that sets up the network14:38
SamYapleok. as a flat or vlan?14:38
sdakesays flat14:39
SamYapleyea thats not configured14:39
SamYapleyou cant use the same interface for flat and vlan networks14:39
SamYaplevlan is whats configured, thats half the issue14:39
SamYaplefor oyu at least14:39
*** mickt has quit IRC14:39
sdakeso should i search and replace flat with vlan?14:40
SamYaplenah ill switch the default to flat ot match existing14:40
SamYapleive got a patch incoming14:40
sdakeok14:40
openstackgerritMark Duggan proposed stackforge/kolla: Adding cinder source image  https://review.openstack.org/20508614:41
SamYapleugh this config stuff is horrible14:41
sdakei noticed ovs-vswitch has a bunch of not found issues14:41
SamYaplei really need to clean it up14:41
sdakelike its not finding taps and stuff14:41
SamYaplewhen you purge your environment, do you `rmmod openvswitch`?14:42
sdakeno14:42
SamYapleoyu should14:42
sdakeok will do14:42
SamYapleitll cleanup all thos interfaces14:42
*** weiyu has quit IRC14:48
openstackgerritSwapnil Kulkarni (coolsvap) proposed stackforge/kolla: Make variables in OVS container configurable  https://review.openstack.org/20493914:49
sdakesamyapel the init-runonce script creates a flat lan and a vxlan14:52
SamYapleyep thats normal14:52
sdakeflat for public14:52
sdakeand vxlan for private14:52
SamYaplewere close. this new patch will fix more config issues14:55
SamYaplestill ahvent booted14:55
sdakecool well get it up and I'll pull it down and help debug14:56
*** jasonsb has quit IRC15:00
*** jasonsb has joined #kolla15:00
*** jasonsb has quit IRC15:05
SamYaplehey sdake did you see ML thread about neutron and the docker plugins?15:08
sdakeyes i did15:08
SamYaplei need more info15:08
sdakei think they want to do what we are doing with linuxbridge and ovs15:08
SamYaplelol15:08
sdakeexcept for all the agents15:08
SamYapledone15:08
sdakethere are a bunch of proprietary agents as well15:09
SamYapleI woudl expect more response to people who already do it... but no one has replied :(15:09
sdakeI was waiting for openstack namesapce to get into a battle over it15:10
sdakeif they want to duplicate the work wfm ;)15:10
sdakeI really dont care - waste of their time but its their time to allocate15:10
openstackgerritPaul Bourke proposed stackforge/kolla: Adding cinder source image  https://review.openstack.org/20508615:11
SamYaplethey even said they dont want to reinvent the wheel15:11
*** diogogmt has joined #kolla15:11
SamYapleand yet...15:11
sdakeopenstack is a busy space not everyone knows what everyone else is working on15:11
SamYaplebut i said we did it like 8 months ago, and no one responded :(15:12
sdakethey are going to do what they are going to do15:15
sdakesaying its already done probably isn't going to stop them from reinventing the wheel ;)15:15
sdakeand here its pure wheel reinvention - ther eisn't much wiggle room on containers15:16
pbourkeI would try and let them know more clearly15:16
pbourkethey probably have no idea, given a lot of the work is still in progress15:17
openstackgerritSam Yaple proposed stackforge/kolla: Properly use all configs with neutron  https://review.openstack.org/20511215:22
SamYaplesdake: that doesnt solve the issue. i know i know whtat this is...15:22
SamYapleanyway configs still need configing15:22
sdakehey guys15:23
sdakekolla has 1000 commits !15:23
bmacehappy 1000 commits day kolla!  you need a cake at the midcycle for that :)15:23
sdakeyes i'm informing now pbourke15:23
SamYapleI GOT the 1000th!15:23
*** pradk has joined #kolla15:23
rhalliseynice!15:24
sdakeno jenkins got the 1000th ;)15:24
SamYaplealright thats it for me15:24
SamYapletime to step down15:24
sdakesam15:24
bmacenite sam15:24
sdakereal quick15:24
sdakeany debug tip on neutron15:24
sdakeyou said you may hae an idea waht the problem is ?15:24
SamYapleoh im not leaving15:24
SamYaplei was making a joke at daneyon expense15:24
sdakeoh15:25
SamYapleive still got more debug left in me15:25
daneyoncongrats!!!15:26
SamYaplewe have the power to summon him at will people!15:26
SamYaplelets not abuse it15:26
rhalliseylol15:26
bmacejust say daneyon 3 times? :)15:27
SamYapleonce seems to do it15:27
daneyonhttps://www.google.com/url?sa=i&rct=j&q=&esrc=s&source=images&cd=&cad=rja&uact=8&ved=0CAcQjRxqFQoTCMzMg8zI8cYCFUoviAodagcCtw&url=http%3A%2F%2Fwww.scriptmag.com%2Ffeatures%2Fspecs-city-trickster-archetype-beetlejuice&ei=EwixVYz3M8reoATqjoi4Cw&bvm=bv.98476267,d.cGU&psig=AFQjCNHr9iF6KpdIil-yrCpn46lO1SAujg&ust=143775168926005815:28
pbourkecan somebody else +2 https://review.openstack.org/#/c/201665/ please15:28
SamYapledaneyon: come fix neutron for us. vif_binding issues15:32
openstackgerritMerged stackforge/kolla: Glance installation from source  https://review.openstack.org/20166515:34
daneyonSamYaple when I ran into that before, neutron-api was not actually reading the conf file. Have you enabled debug logging on neutron-api and actually observe the config file being loaded and read? I fixed the issue my specifying the conf file in the exec. Like here: https://github.com/stackforge/kolla/blob/stable/juno/docker/neutron/neutron-server/start.sh#L9815:38
SamYaplepretty srue we are doign that, ill check15:39
SamYapleyup we specify it on the command line15:40
SamYapleall the agents work ust fine15:40
SamYaplenova just vif_bind fials. no neutron bits have errors15:40
SamYapleugh wait. dont libvirt and nova_compute need to share volumes?15:42
SamYaplethey do15:42
*** bmace has quit IRC15:46
sdakehrm15:49
sdakethey need to share an /etc directory!15:49
sdakeand its networking related15:49
SamYapleno they dont15:49
SamYaplenova-net only15:49
sdakeoh15:50
sdakethey need to share /var/lib/nova, /var/lib/libvirt, and possibly some /etc/ directory for nova15:50
SamYaplesdake: they don't need to share libvirt15:51
SamYaple/var/lib/nova/instances only15:51
SamYaple /etc stuffs for nova-net15:52
SamYaplebut thats not whats causing the vif issues anyway15:52
sdakeso is it accurate that youdu works and can boot a nova vm?15:52
SamYapleon the 0.1 tag, yea15:52
openstackgerritMerged stackforge/kolla: Removes Host Cleanup from Container Cleanup Script  https://review.openstack.org/18249315:52
SamYaplebut that hanst been done in months15:53
SamYapledocker probably broke it by now15:53
sdakeone thing we can try is implement linuxbridge and use that ;-)15:54
SamYaplei have no experince with it in containers :( i dont know what would be needed from config-external to make it work15:54
sdakei was getting vif binding errors without the /etc dir shared in the past15:54
sdakebut not sure if I tried with nova net or neutron15:55
pbourkehow are Kuryr in the big tent already?15:56
sdakei am pretty sure you need dnsmasq.conf to operate15:56
SamYaplepbourke: i think enutron said yea we want that15:56
pbourkehave they been around for a while and keeping quiet or do I have no idea how big tent works15:56
sdakei think i got vif bidning errors there too15:56
SamYaplethey said they are neutron big-tent15:56
SamYaplesdake: you dont15:57
pbourkeso there are different tents15:57
SamYaplethat has nothing to do with vif-binding15:57
SamYaplelook at the port sdake15:57
SamYapleneutron port-list15:57
sdakeneutron has its own tent structure15:57
SamYapleneutron port-show <portid>15:57
SamYaplewhen the port gets created it bad15:57
SamYapleall neutron stuffs15:57
*** bmace has joined #kolla15:57
sdakelet me try taht with your patch15:58
sdake10 mins15:58
sdakewhy is vxlan in 239 address space?15:59
SamYaplethats multicast16:00
sdakeyes i know16:02
sdakeinit-runonce creates a vxlan interface, but its not in the 239 address space16:03
sdakerather a vxlan network16:03
* sdake fucking hates networking16:03
SamYaplethats not what that is16:03
SamYapleignore it16:03
sdakeas my wife says "Cisco didn't build its empire because networking is easy."16:03
sdakesamyaple can you ahe  a look at init-runonce16:04
sdakeand make sure it makes sense for ovs16:04
*** inc0 has quit IRC16:04
*** mstachow has quit IRC16:07
SamYaple2015-07-23 16:06:32.666 28 DEBUG neutron.plugins.ml2.db [req-ca48af2f-c916-41b5-9085-5c0b5b4840e4 562681f2e69a4d039290610d20b229da 9753a054c6cd4c089973224d00d248f1 - - -] Attempted to set empty binding levels set_binding_levels /usr/lib/16:07
SamYaplepython2.7/site-packages/neutron/plugins/ml2/db.py:16416:07
sdakethat looks problamtic16:09
sdakebecaue if levels is defined something is added to sessions.*16:10
sdakewhtaever that is16:10
sdakeok guys, debugging neutron and getting nova booting in ansible is job #1 for the next couple of days16:14
sdakeif folks could focus on that, I'd appreciate it (until its done :)16:14
SamYaplepff thats not optimistic16:14
SamYapleday16:14
SamYaplefew hours at most16:14
SamYapleargggg i think i found it16:17
SamYapleim just a dummy16:17
SamYapleneutron-server isnt reading ml2_conf16:17
*** Slower has quit IRC16:18
SamYaplerebuilding and checking now16:18
sdakei think daneyon suggested that ;-)16:18
SamYapleyea he said neutron.conf16:18
sdakeoh16:18
SamYapleactually he didnt say16:18
SamYaplebut yea we were reading neutron.conf just fine16:18
SamYaplenot ml2_confi.ini16:18
SamYaplei think i remember thinking about this and saying "why owuld neutron_server need this"16:19
* SamYaple sighs16:19
sdakeya doesit need it?16:19
SamYapleapparently16:19
SamYaplethe server logs were complaining about ml2 things16:19
SamYapleand thats why the binging was bad16:19
SamYaplebinding*16:20
SamYaple2015-07-23 16:15:02.243 32 DEBUG neutron.plugins.ml2.managers [req-a2563b0a-a643-4b1b-87b3-f7aad444548e 6e77bffc7d1b4f2b9e04273abf8e1c66 a7a80483976a48f49d553a003bfbf0f5 - - -] Attempting to bind port 495c824c-db4e-41ca-980c-6e52c47efc3c16:20
SamYaple on host server02 at level 0 using segmens [{'segmentation_id': None, 'physical_network': None, 'id': u'fc210d08-246c-4f44-ade6-7e39b3f8df1c', 'network_type': u'llocal'}] _bind_port_level /usr/lib/python2.7/site-packages/neutron/plugins/16:20
SamYapleml2/managers.py:65116:20
SamYaplenetwork_type would be ovs if it read ml2_conf.ini16:20
SamYaplebut hey this diversion made me see a few little bugs that would be hard to find16:21
SamYapleso not all lost16:21
sdakewhy are there empty ini files in /etc?16:21
sdakecan't we put those in /usr/share?16:21
sdakeor is the idea someone shoudl put something in them?16:22
sdakesamyaple can you paste a git diff so I can see how you fixed the ml2 config file read16:23
*** achanda_ has joined #kolla16:26
*** achanda has quit IRC16:26
*** absubram has joined #kolla16:27
*** unicell1 has quit IRC16:28
SamYaplesdake i have answered those questions for you many times before16:30
SamYaplelets not worry about them right now16:30
SamYaplethey are literally a single ansible variable to change16:30
SamYaplethey can be changed later16:30
sdakei guess I dont understand why there are empty files16:31
sdakeand you haven't explained that one ;)16:31
SamYaplei know and ive explained it before16:31
SamYaplei have16:31
SamYapleseveral times16:31
sdakewould you mind explaining one more - i'll pay attention this time16:31
sdakelike dhcp_blah.ini16:31
SamYaplethey are teh augment files. ansible requires the files to exist to use them for templating. i need to file them with comments and examples for how to use so they arent just blank16:32
SamYaplefor now its just blank16:32
sdakeI get the empty augementation files - those are meant to be changed16:32
SamYapledhcp_agent.ini is an autment file as well16:32
sdakei see16:32
sdakeok that wasn't clear16:32
SamYapleall those files are16:32
SamYaplethey need comments16:32
sdakeok etc makes sense then16:32
sdakei thought they were needed for implementation purpose16:33
sdakeas in, need a empty file to copy from16:33
SamYaplethe /usr/share stuff is16:33
sdakein which case they should go in /usr/share16:33
SamYaplebut that can move to /var/lib16:33
sdakethe current /usr/share shold def go to /var/lib16:33
SamYapleagreed16:33
sdakemy only concern is how does someone upgrade  the /etc path16:33
sdakewhen new files are added16:33
SamYaplethose files are modified by ansible only16:33
SamYaplethe /usr/share ones i mena16:34
sdakeyup16:34
sdakei understand how /usr/share and /opt work16:34
sdake10 hours of debugging neutron, remember ;)16:34
sdakeI have good indepth understanding of how ansible works in our implementation now16:34
sdakeall the cores should take on a ansible project to understand how the stuff works16:35
SamYapleyay16:35
*** Slower has joined #kolla16:36
sdakei think what would make sense is if a config file isnt' found, our merger treats it as an empty file16:38
sdakesince they are all empty anyway16:38
sdakethat way ansible doesn't bomb out on kolla upgrades16:38
SamYaplethat wont work16:39
SamYapleansible is the merger16:39
SamYapleit bombs16:39
sdakedoesn't it have python code that does the merging?16:39
sdakeif file not found - file = '' :)16:39
SamYapleits not like that16:39
sdakewell i can tlel upgrades of kolla will be painful16:40
SamYaplethis is the best way forlots of reasons. those files need comments16:40
SamYapleno16:40
SamYaplescript will update the yamls16:40
sdakeyou mentioned that prior16:40
sdakei guess that would work but seems fragile16:40
SamYapleits really not16:41
SamYaplepython yaml parser16:41
sdakesomeone very likely not to actuallly run the upgrade script and then bork their install16:41
SamYaplewell it wont break their data16:41
SamYapleit doesnt matter anyway. thats they way it is16:41
SamYaplesdake, you know this will all be dont with kolla start, right?16:44
SamYaplea check at the beginning for version/sanity?16:44
sdakethat is a workable approach16:45
sdakeI hadn't thought of  that though, no16:45
SamYapleoh then that explains the disconnect16:45
SamYaplethat is why im not worried16:45
sdakeok that wfm16:45
SamYaplei mean yea if they run the ansible stuff dircetly they might break things, but thats thier own fault is my point16:46
SamYapleSUCCESS16:47
SamYaplekinda16:47
SamYapleall ports are creating, but nova_compute needs ovs utils16:47
SamYaplewith the next 10 minutes i bet i have a successful boot16:49
*** unicell has joined #kolla16:55
sdakesamyaple I used your latest patch + made neutron-server load ml2_conf, port still says unbound16:57
sdakewith port-show16:57
sdakerather binding-failed16:58
SamYaplelibvirtError: internal error: process exited while connecting to monitor: Could not access KVM kernel module: Permission denied17:01
SamYapleweve solved this already17:01
SamYaplethat was root:kvm perm issues right17:01
sdakewow your gtting far17:02
sdakethere is a chmod in /dev/kvm in config-internal17:03
sdakebut probably not config-external17:03
SamYaplei see it17:03
SamYapleim also not binding /dev into the container17:03
sdakethe dev bind doesn't matter17:03
sdakewe use it for cinder17:03
SamYaplebut i need /dev/kvm17:04
sdake /dev/kvm is already in the container, it just has the wrong permissions17:05
SamYaplehmm17:05
SamYaplethats from devtmpfs17:05
sdakeyup17:05
sdakewe will want to bindmount /dev - so might as well do that anyway -for cinder17:05
*** absubram has quit IRC17:06
SamYapleare you sure we have to?17:06
sdakenot certain, rhallisey claims it is necessary17:06
SamYaplerhallisey: what was the verdict of that? do we have to bind host17:06
rhalliseyyes we have to17:06
SamYaplei refuse!17:07
rhalliseywithout it I was having issues17:07
SamYaplehmm ok so bind /dev from host17:09
SamYapleso the issue wit hthat is will the group 'kvm' in the container match the guid on the outside of the container?17:10
SamYaplethat seems dangerous17:10
*** dims_ has quit IRC17:12
SamYaplewhat was the reasoning for not tweaking the libvirt conf to run as root in the contaienr?17:12
sdakeno reasoning17:14
sdakebut ya the gid needs to match - agree its subotpimal as is17:15
sdakealthough libvirt really shouldn't run as root either17:15
SamYaplewhen we get around to dropping CAP itll be fine17:15
SamYaplei mean the whole contain is privileged anyway17:15
SamYapleconatiner*17:15
sdakeright17:15
SamYapleguid and uid mapping is coming for dokcer17:16
sdakecan you paste an updated patch17:17
sdakeor do a new git erview17:17
SamYapleim working on it17:17
sdakei want to see if there is something wrong with my environment that wont create ports17:17
sdakesince i think I've done what you did17:17
SamYapleyay its working17:18
sdakebooted a vm?17:18
SamYapleyep17:18
sdakevm have network connectivity?17:18
SamYapleno idea17:18
SamYapleim going to up the patch17:19
sdakeprobably not without the dnsmasq setup17:19
sdakecool i'll test it here17:19
SamYaplednsmasq works fine dammit17:19
SamYaplethat config file is just extra17:19
SamYaplewe need to add it but it wont break things17:19
sdakein linuxbridge I had to set dnsmasq to 1450 to get outside vm connectivity to work17:21
sdakebecauseof the vxlan overhead17:21
SamYapleyou dont have to17:21
openstackgerritSam Yaple proposed stackforge/kolla: Fix compute permissions and start params  https://review.openstack.org/20518317:21
sdakei definately had to do so17:21
SamYapleyou do not17:21
SamYapleim telling you17:21
SamYapleit just fragments17:21
SamYaplei know the issues and you can work around it17:22
SamYaplewithout dnsmasq17:22
*** coolsvap|away is now known as coolsvap17:22
sdakeis that the ony patch we should apply samyaple17:23
SamYaplesdake youll need https://review.openstack.org/#/c/205112/ and https://review.openstack.org/#/c/205183/17:23
sdakeor also apply your previous one?17:23
sdakeok17:23
SamYapleyea i forgot to depend them17:23
SamYapleon a clean enironment it gest stuck on BUILDING17:28
SamYapleprobably some external configuration i forgot17:28
*** absubram has joined #kolla17:31
openstackgerritJames McCarthy proposed stackforge/kolla: Swift Containers  https://review.openstack.org/20217117:33
*** Slower has quit IRC17:34
SamYaplehave you tried it yet sdake?17:37
sdakebuidling17:38
sdakeslow network17:38
sdakein a vm17:38
SamYapleawesome17:38
sdakeover wireless17:38
sdakejust finished cmopute now for libvirt ;-)17:41
jmccarthybaseline swift looks to be close (it was working!), seems like some new config dependencies got in for proxy server somehow, hopefully it'll be sorted tomorrow (and some other stuff can be bugged up from the todo)17:41
sdakejmccarthy if your in for an adventure, you could add ansible support for swift ;-)17:42
openstackgerritHarm Weites proposed stackforge/kolla: Don't try to chown root:root /tmp/kolla_mariadb_cluster  https://review.openstack.org/20519517:43
jmccarthyHehe :) I would give it a whirl but some of the supporting services might need sorting out first ? Depends I guess - I'll be coordinating with Paul tomorrow as I'm away on holidays next week17:44
sdakenice enjoy the holiday17:44
sdakeim getting ready to go hiking myself here shortly17:44
jmccarthyDon't bring any devices with you ;)17:45
sdakei'll take my phone in case i get lost17:45
harmwguys, please look at that review up above :) nothing big, but still17:45
*** dims has joined #kolla17:45
SamYaplei reviewed it harmw17:45
SamYaplethat was for security reasons17:45
jmccarthyHehe ok phone is allowed17:45
SamYapleand running as root is required for all kinds of kolla things17:45
harmwansible is doing it's tricks as root, ofcourse17:46
jmccarthylaters o/17:46
harmwbut I am running ansible, as me17:46
SamYaplethats not how that works harmw17:46
sdakeat minimum yo uwould hae ot run ansible as the kolla user17:46
sdakeso it could write to /var/lib and /usr/share and whatnot17:47
SamYaplethere is no kolla user17:47
sdakei recognize it17:47
sdakewhat i'm saying is it could be done without root17:47
harmwI'm just running as me sdake, which works great17:47
harmwansible_ssh_user=root17:47
harmwthats all17:47
SamYapleharmw: for now, but it wont when everything is in place17:47
harmwbut $USER is just me17:47
SamYaplewe chown lots of things17:47
harmwuhm yes, we do, but on the support and cluster nodes17:48
harmwright?17:48
SamYapleyea but this is a local_action17:48
SamYaplelook im ok with the change but sdake threw a security fit over it17:48
harmwindeed, which takes place on the operator node17:48
sdakei only care if the file is written as root :)17:49
harmwin that case it should be chmodded to 600 aswell17:49
SamYaplesdake: it never was17:49
SamYaplei explained that17:49
harmwit's written by $USER17:49
harmwso not root, atleast not here :p17:50
SamYapleharmw: the file is set as 060017:50
harmwoh ok, excuse that17:50
harmwI thought I saw a 660 there17:50
SamYaplehonestly i never saw this a a big security thing. the only issue was i used shell original which is not best practice anyway17:51
harmwI'm not seeing it either, all I know is I need my patch in order to have ansible deploy the database17:52
sdakewhat is written by user?17:53
harmwthat file, to /tmp17:53
sdakeI thought it was written by ansible as root17:53
harmw/tmp/kolla_mariadb_cluster17:53
SamYaplesdake: only if you run ansible as root17:53
harmwit's writing the file and doing a chown to root17:53
SamYapleso for your AIO stuff you are running ansible as root17:54
sdakedont we ned to run ansible as root?17:54
SamYapleonly for AIO17:54
harmwSamYaple: AHA17:54
harmwnow that makes sense17:54
harmwand I, ofcourse, am playing with multihost :)17:54
SamYapleAIO doesnt connect over ssh17:54
SamYapleyes17:54
sdakecan we make aio connect over ssh?17:54
sdakethen it wouldn't have to run as root?17:54
SamYaplethat would require additional setup17:55
sdakerunning ansible atm17:55
sdaket-3 minutes17:55
SamYapleyou would have to make a passwordless ssh key for the current user to ssh to root on the local host17:55
sdakeoh i did that already - i thought that was mandatory ;-)17:55
harmwso in it's current form you run as root and deploy using root, creating a file /tmp and chown to root (which is redundant)17:56
SamYapleharmw: dont complain to me. i had to fight to fix what i thought wasnt a big deal17:56
harmwall because AiO works on localhost, without ssh/sudo whatever17:56
harmwSamYaple: I never complain17:56
harmwonly to sdake :)17:56
harmwI didn't know about the consideration regarding AiO :)17:56
harmwI'm just seeing an issue when trying to play with multinode17:57
sdakedont blame me blame the hackers17:57
sdakeand the NSA17:57
SamYaplebut theres nothing to hack is my point17:57
SamYapleat the VERY WORST you could potentially start the database on the wrong host17:57
harmwplus, since AiO runs as root already (albeight just for now) I see no value in that additional chown to root (which ultimatly screws my multinode testing)17:57
SamYaplethats the worst17:58
harmwchmod 600 is already in place, as it should17:58
harmwI see no harm in accepting that patch :)17:58
sdakelisten here is the deal - I dont care but as soon as people start distributing our software they will audit it for security red flags17:59
sdakeso we will have to respond to those as they come in17:59
sdakei'd prefer not to have any audits come back negatively as it affects the project negatively17:59
SamYaplesdake: as i tried to explain before. there is no security risk here18:00
SamYaplei would argue this makes it less secure18:00
harmwI'm with SamYaple on this one :)18:01
sdakei haven't looked at the patch -busy atm18:01
sdakehang tight18:01
SamYaplesdake: i see the issue that i missed18:03
SamYapledont approve that patch just yet18:03
SamYaplewhy its stuck in building i mean18:04
sdakesay when we do upgrade, arew e going to make a site-upgrade.yml file?18:05
sdakeand have it basically do the same thing except force bootstrapping?18:06
SamYapleprobably, but not quite used like that18:06
SamYaple`kolla upgrade`18:06
sdakeright18:06
SamYapleit will have logics in it specific to that version of the upgrade18:06
sdakebut that will run a site-upgrade.yml playbook?18:06
SamYaplemaybe18:06
SamYaplei dont know. it will probably differ with each openstack upgrade too18:06
sdakeany time there is a new container we need to rerun the db migration18:07
SamYaplethe upgrade process changes18:07
SamYapleno18:07
SamYaplethe dont do db changes between versions18:07
SamYaplethey*18:07
sdakeon master ?  sure do18:07
SamYapleon master yea18:07
SamYaplethats not stable18:07
sdakethe 2015.1.1 thing is going byebye18:08
sdakepeople are going to maintain a stable branch and backport to it18:08
SamYapleyea but tags are sticking around18:08
sdakeno more tagging18:08
SamYapleso db upgraede new tag, yes not new container18:08
SamYaplelol yea theres still tagging sdake18:08
SamYapleits just whatever tagging scheme the project wants18:09
SamYapleunstead of openstack-wide18:09
sdakeya tagging only at db schema changes18:09
sdakewe are having a design sesision on upgrade I guess  we can tackle it then18:09
SamYaplethats probably best18:09
SamYaplei dont think anyone has thought it all out yet18:10
SamYaplei know i havent18:10
sdakeerror state18:11
sdakeport status = active tho!18:12
SamYaplew00t18:13
SamYaplegot ACTIVE again18:13
SamYaplegoing to test ping18:13
SamYapleno response :(18:14
SamYaplegoing to check the console18:14
SamYapleoh wait18:15
SamYapleresponse!18:15
SamYaplesecgroup rules18:15
SamYapleyay18:15
sdakei get "libvirtError: internal error: no supported architecture for os type 'hvm'18:15
SamYapleyoure running in a vm18:15
sdakei set qemu18:15
SamYapleidk what else youd have to set18:15
sdakewierd my libvirt settings went byebye18:16
sdakei must have erased it accidentally18:16
SamYapleprobably18:16
sdakehow do I set that again?18:16
SamYaplegoing to submit patchset t2o18:16
SamYaple[libvirt]18:17
SamYaplevirt_type=qemu18:17
SamYaplei think18:17
SamYaplein /etc/kolla/config/nova/nova-compute.conf18:17
sdakelets see if rerunning ansible will configure the new value18:18
SamYapleit wont18:18
SamYaplei dont have the 'if changed config restart container' logic in yet18:19
SamYapleplus the config method would prevent that anyway18:19
SamYaplebut you can rm the container18:19
SamYaplethgat woudl work18:19
sdakeya it doesn't18:20
openstackgerritSam Yaple proposed stackforge/kolla: Fix compute permissions and start params  https://review.openstack.org/20518318:20
SamYapledas what got me bootin18:20
sdakeis that a new patch or a rebase of an existing patch18:21
SamYaplerebase18:21
SamYapleer update18:21
SamYaplecan someone ack this https://review.openstack.org/#/c/204567/18:22
*** Slower has joined #kolla18:22
*** Slower has quit IRC18:22
*** Slower has joined #kolla18:22
harmwdone18:23
SamYapledanke18:23
harmwsdake: can you ack those other neutron bits?18:23
harmwand what to do with my ansible patch :p18:24
*** jtriley has quit IRC18:24
harmwSamYaple: you mind me changing your ansible_ssh_user=sam line to root?18:24
sdakei am going to test the neutron bits18:24
harmwone less file that needs tinkering with in demos18:24
sdakethen ack them18:24
SamYaplesdake: that would be recommended18:25
*** stvnoyes has quit IRC18:28
sdakerunning ansible twice breaks things18:29
SamYaplelies18:30
harmwlol no sdake ofcourse not18:30
SamYaplei consistently run it twice in a row18:30
SamYapleits habit now18:30
harmwthats the beauty18:30
harmwhttps://www.youtube.com/watch?v=7AlEvy0fJto woohoo!18:30
*** jtriley has joined #kolla18:30
SamYaplesdake: good respons from the ML18:30
SamYaplemy name holds no wieght18:31
*** stvnoyes has joined #kolla18:35
openstackgerritMerged stackforge/kolla: Removed unused hautoproxy code  https://review.openstack.org/20456718:36
sdakewell I'd probably win a popularity contest18:37
sdakebut so what :)18:37
SamYapledepends on whos there18:37
harmwwho's winning?18:38
harmwsdake: done with neutron?18:38
sdakenearly18:38
sdakealmost ready to boot18:38
harmw20:24:40 < harmw> SamYaple: you mind me changing your ansible_ssh_user=sam line to root?18:38
sdakeso my public network is not being created samyaple18:39
sdakeonly the demo network18:39
sdakefrom init-runonce18:39
*** absubram has quit IRC18:39
harmwhm, is there no matching physnet sdake ?18:39
SamYapleharmw: changing it to what?18:39
harmwto root18:39
harmw(or completely removing it)18:40
SamYapleyea, cause this is all meant to be sudo'd and not run directly as root18:40
SamYaplewere just not there yet18:40
sdakevm went active yay ;-)18:40
SamYaple:)18:40
harmwnice sdake18:41
SamYaplei told you it would be done today18:41
harmwand SamYaple, also18:41
harmwnow18:41
harmwack!18:41
harmwand I'll start pushing again :p18:41
harmwand run some multinode tests18:41
SamYapleharmw: you are pushing from the L1 tagged branch right?18:41
sdakeconsole-log gets stuck at sending discover...18:41
harmwno SamYaple latest18:41
harmwsdake: thats not stuck, its dhcp that fails18:42
SamYapleuhh thats not what were supposed to be doing18:42
SamYaplewe only push 3 times a cycle18:42
harmwwe do?18:42
SamYaplethats why we had the stablility push for L118:42
SamYapleyea18:42
harmwthats not what sdake told me...18:42
harmwso sry, I guess18:42
SamYapleoh then im on a differnet page18:42
SamYaplewhen i was pushing it was supposed to be from L118:43
SamYaplelike i said half this stuff is broken18:43
sdakeya we have l1 l2 l318:43
harmwI thought we were just pushing master to latest every now and then18:43
sdakeya i guess we should hae pushed l118:43
sdakeoh well18:43
sdakel1 was never pushed iirc18:43
SamYaplecorrect18:43
harmwhm, so I did bad18:43
SamYaplewe can just hold off and push L218:44
harmwindeed18:44
SamYaplei mean honestly18:44
harmwclose anyway18:44
SamYapleL2 should have a working ansible deploy too18:44
sdakesamyaple dhcp no worky18:44
SamYaplesdake: ill look at init-runonce18:44
sdakebut looking much better so i'll approve the two changes18:44
sdakeyes please do18:44
sdakethis stuff is all black magic to me18:44
SamYapledhcp works for me ;)18:44
sdakedaneyon wrote that script18:44
SamYapleim going to hammer on multinode now18:45
SamYaplehopeflly no changes18:45
sdakeinit-runonce also doesn't create the public network18:45
sdakeour public network is called public, but the compose has physnet1 iirc18:45
harmwyep18:45
sdakeso we shoudl probably change that18:45
SamYaplesdake: no18:45
SamYaplethats not what that is18:45
SamYaplei wish i could transfer my network knowlege into your brain18:46
sdakeme too18:46
SamYapleyea that neutron line wont work18:46
sdakesamyaple i'm going off what harmw said18:46
sdakeit works on compose ;-)18:47
harmwwait wut18:47
harmwwhat'd I say?18:47
SamYaplei mean it _can_ work but i have to change the defaults18:47
SamYaplebut we can just drop that param18:47
SamYapleits not required18:47
SamYaplethen it woudl work for both i suppose18:47
sdakei dont know which your tlaking about18:47
SamYaple--provider:physical_network physnet118:48
SamYaplethats not required18:48
harmwit isn't?18:48
SamYaplewell not required when there is only one mapping18:48
harmwuhm yes18:48
SamYapleum no18:48
harmwwas about to say that :)18:48
SamYapleits not required for two either18:48
SamYapleyou just cant select the one you want ;)18:48
SamYaple --provider:network_type vxlan --provider:segmentation_id 1018:49
SamYaplealso not required18:49
harmwbut if we leave it out, then how it works?18:49
SamYaplemagic!18:49
harmwit won't select vxlan by itself?18:49
harmwah18:49
SamYapleit will18:49
harmwwe have defaults set?18:49
SamYapleno it selects tenant network types when not explicitly set18:50
SamYaplevxlan is the only one configured18:50
harmwyep18:50
SamYaplecause gre be bad18:50
harmwthats default enough for me18:50
harmw:p18:50
SamYaplebut again, if would select one for you if you dont specify18:50
harmwgot it18:51
harmwdid today's fixes merge yet sdake? :p18:51
SamYaplejust rebuilt all containers on fresh host18:51
SamYaplegoing to reattmept18:51
harmwI'll be doing that as well, later tonight18:51
harmwonce all is merged :P18:51
SamYaplei need to test multinode18:52
sdakethey hae been approved but haven't gone through zuul yet18:52
harmwSamYaple: you could you Vagrant for that18:52
SamYapleugh no18:53
harmwwhy not18:53
SamYaplei have real hardware for multihost :P18:53
SamYapleplus i do most of my testing on Openstack18:53
harmwah18:53
SamYapleopenstack on openstack on openstack18:53
harmwI don't have that luxury :p18:53
SamYapleive done it, dont laugh18:53
SamYapleyea well i paid out for this luxury18:54
SamYapleit didnt come cheap18:54
harmwehe18:54
*** bitblt has joined #kolla18:55
SamYapleoh jeez18:56
SamYaplelol sdake dhcp is busted on a clean host18:56
SamYaplelet me figure out why18:56
sdakefix init-runonce while yoru at it iplz18:57
SamYaplei dont wanna18:57
SamYapleit aint broke18:57
openstackgerritMerged stackforge/kolla: Fix compute permissions and start params  https://review.openstack.org/20518318:57
openstackgerritMerged stackforge/kolla: Properly use all configs with neutron  https://review.openstack.org/20511218:57
openstackgerritHarm Weites proposed stackforge/kolla: [WIP] Vagrantfile and docs  https://review.openstack.org/20423818:58
*** bitblt has quit IRC18:58
SamYaplesdake: nvm dhcp works fine. i setup the network with --disable-dhcp19:00
sdaketry with init-runonce19:01
SamYapleno thats busted19:01
sdakeI would really like one network setup script19:01
sdakeso that eveyrone is doing the same thing re neutron19:01
sdakeyou said above its nto busted19:02
SamYaplebut i am not going to use that...19:02
sdakeyou dont have to use it19:02
SamYaplei said dhcp is not busted19:02
sdakebut i use it all the time19:02
sdakeand most other devs do as well19:02
SamYapleyea but that doesnt even use the proper client19:02
sdake[11:57:09]  <sdake>fix init-runonce while yoru at it iplz19:02
sdake[11:57:20]  <SamYaple>i dont wanna19:02
sdake[11:57:27]  <SamYaple>it aint broke19:02
sdakeyou said right there it aint broke19:03
SamYaplefor compose ;)19:03
SamYapleand you can change the neutron config to make it wrok....19:03
sdakei would like one script for both models if that is at all possible19:03
SamYapleit is19:03
SamYapleim already working on it19:03
SamYapleBUT19:03
sdakeI dont know *how* to do it19:03
sdakethanks :)19:03
SamYapleif you want it done you file a bug19:03
sdakewill file19:04
SamYaplegood. i hate that lol19:04
harmwso the init-runonce differs between ansible and compose?19:04
SamYaplenah just the bridge_mapping name19:04
SamYaplesdake could just update his config but eh19:05
harmwthen the fix is to use the same name in both setups.. right?19:05
SamYapleno19:05
SamYapleits not not call the name out explicitly19:05
sdakehttps://bugs.launchpad.net/kolla/+bug/147772519:05
openstackLaunchpad bug 1477725 in kolla "init-runonce doesn't work with ansible neutron" [High,Confirmed] - Assigned to Sam Yaple (s8m)19:05
SamYaplethat init-runonce is a basics barebones script not meant to be run in a production deployment19:05
sdakeits absolutely a development only tool19:06
sdakean argument could be made we need something to get people rolling that is production worthy19:06
sdakebut that isn't a priority atm ;-)19:06
sdakerhallisey how is tripleo integration coming along19:08
rhalliseysdake, it going19:08
rhalliseyit's going19:08
sdakeusing config external or config internal?19:08
harmwsdake: which containers need rebuilding after those merges?19:08
sdakeharmw neutron* nova*19:09
harmwok19:09
sdakeand the ovs* I thiink ;-)19:09
harmwah19:09
harmwnova-compute and neutron*19:09
sdakeand nova-libvirt19:09
harmwso nova*19:10
harmwfair enough :p19:10
sdaketheere  may be a base file edit in there,  i dont  recall19:10
SamYaplei need to change the keystone client to openstack client in init-runonce19:10
sdakei just rebuilt em all19:10
SamYaplekeystone is deprecated and unusable19:10
sdakesamyaple sounds good19:10
sdakethe main reason i need init-runonce is because i am going to implement heat in ansible19:11
*** achanda_ has quit IRC19:14
rhalliseysdake, external19:17
openstackgerritSam Yaple proposed stackforge/kolla: Update init-runonce  https://review.openstack.org/20524719:19
SamYaplesdake: that should fix it. youll need to rekick since i updated the br-ex to match compose for consistency19:19
SamYaplephysnet119:20
*** apuimedo has joined #kolla19:27
apuimedoSamYaple: sdake: Hi!19:28
apuimedoThanks for reaching out!19:28
*** gfidente has quit IRC19:29
SamYaplehi! antoni?19:29
apuimedoYup, that's me19:30
SamYaplewelcome!19:30
harmwsomething networking, our way has come19:30
apuimedomay the source be with us19:31
harmwpeering established19:31
harmwnice :p19:31
SamYaplethats definetly better than 'may the fork be with us'19:31
harmwI always like spoons better19:31
apuimedoI prefer to chew at the food like an animal :-)19:32
SamYaplewell apuimedo you have caught us at a good time. the ansible bits have just landed in place so a complete and working openstack environment comes up using Ansible now19:32
apuimedospecially when the pig leg is starting to be quite finished19:32
apuimedos/pig/pork/19:33
bmacei like that one apuimedo.  i usually go with just "use the source"19:33
apuimedoSamYaple: that's great to hear19:33
apuimedocan you point me to it19:33
apuimedowe use ansible quite a bit19:33
SamYaplehttps://github.com/stackforge/kolla/tree/master/ansible19:34
apuimedoand we are very much looking forward to have a kolla based deployment19:34
SamYaplehttps://github.com/stackforge/kolla/blob/master/docs/ansible-deployment.md19:34
apuimedooh, so it's in master19:34
apuimedoI thought it would be a feature branch :P19:34
harmwaren't we all in master19:34
SamYaplehah as if!19:34
SamYaplethe docs will get you started, i hope you dont mind bleeding edge ;)19:35
apuimedothere is only one thing when I tried kolla that left me puzzled19:35
apuimedoa month ago19:35
SamYaplesure19:35
apuimedothat it automatically set up the compose for restart19:35
apuimedoso every reboot my laptop would start all of kolla :P19:35
SamYapleyoull have to talk to sdake about that. i also dont like that ;)19:35
harmwsystemctl disable docker :p19:36
SamYapleits configurable for ansible19:36
apuimedoI hope that by deleting all the yml of compose I finally got rid of it19:36
apuimedoharmw: +1 for using systemd19:36
harmwhah19:36
SamYapleas if we have a choice these days19:36
harmwhe SamYaple how exactly do you use a custom docker registry19:36
apuimedothere is only one init and poettering is its prophet19:37
harmwtalking usecase here19:37
harmwyep apuimedo19:37
SamYapleapuimedo: i actually do like systemd, I just wish it was more modular19:37
apuimedoharmw: what do you mean custom docker registry?19:37
harmwrunning my own registry19:37
SamYaplewe support private registries19:37
harmwto push the new images to, so they can easily be fetched from the other cluster nodes19:37
apuimedoI come from Red Hat, I was spreading the word to my older sys admins :P19:37
SamYapleharmw: https://github.com/stackforge/kolla/blob/master/etc/kolla/globals.yml#L43-4919:38
harmwbut thats for loading SamYaple , right?19:38
harmwpulling19:38
apuimedoSamYaple: kolla is all rdo based for now, right?19:38
SamYapleyou mean for pushing?19:38
SamYapleapuimedo: acutally we have many distros now19:38
SamYaplei beleive ubuntu is almost done19:38
SamYaplewe currently only gate rdo19:39
apuimedooh, it seems I missed quite a bit in the last month19:39
SamYaplewe have come a long way yes19:39
apuimedotoo busy setting up Kuryr and working on Juju19:39
harmwSamYaple: the workflow is probably building and pulling from dockerhub, then push to on premise registry19:39
harmwright?19:39
harmwand have other nodes pull from internal registry19:39
SamYapleI actually expect most people to build thier own images harmw19:39
apuimedoSamYaple: for networking plugins, what is your idea, to make separate image names19:39
apuimedoor just tag differentiation?19:40
harmwI do, but never pushed to internal registry19:40
SamYapleapuimedo: i think we can get by with simply installing the plugin in the existing container. Then configuration would be handled by ansible after the build19:40
apuimedomodify the container after the build?19:41
SamYapleapuimedo: oh im sorry, i meant for nova container. the nova bits can be dropped in the existing nova container19:41
SamYapleneutron will get its own neutron-midonet-agent container19:41
apuimedoyou mean the nova-compute container?19:42
SamYapleyes19:42
*** athomas has quit IRC19:43
apuimedoSamYaple: how I had thought about it was that neutron-server would have different builds for the different plugins19:43
apuimedothen19:43
apuimedomake a nova-compute-vendorname for each of the vendors19:44
SamYaplewe can certainly go that path if needed. we do break up the neutron plugin agents so far we havent had a need to split of nova-compute19:45
SamYaplehttps://github.com/stackforge/kolla/tree/master/docker/centos/binary/neutron19:45
apuimedoSamYaple: it's very good that you split the neutron agents19:45
apuimedosince some vendors do not use some of them ;-)19:46
SamYapleyes so we could easily add neutron-midonet-agent19:46
SamYaplei am worried a bit about spliting compute so as not to violate DRY19:46
SamYaplebut if we do it as a seperate layer, that may work well19:46
apuimedothe midonet agent has to run on the nova-compute19:46
apuimedothink of it as the same as ovs19:47
apuimedonova-compute, when talking to libvirt to start a VM19:47
apuimedotells libvirt to start the container with a specific virtual port uuid19:47
apuimedolibvirt then calls ovs-vsctl19:47
apuimedofor midonet it's the same, but libvirt calls mm-ctl19:48
apuimedoSamYaple: does nova-compute run on the --net=host?19:48
SamYapleapuimedo: all containers do19:48
SamYaplefor performance reasons19:48
apuimedooh, that's great19:48
apuimedowell, in that case19:48
apuimedomidonet-host-agent can run completely standalone19:48
*** stvnoyes has quit IRC19:49
SamYaplecurrently we install openvswitch innside nova-compute container itself, i can see the benefit to spliting that off19:49
SamYapleoh ok then thats great too19:49
apuimedowe could just have nova-compute have the mm-ctl binary and that's it19:49
SamYaplethats perfect19:49
SamYapleits exactly what we do with openvswitch19:49
SamYapleopevswitch is a seperate container19:49
apuimedomidonet-host-agent would receive all the data it needs from zookeeper19:49
apuimedo:-)19:49
SamYaplei love it when a plan comes together19:49
apuimedo:-)19:50
SamYaplewe can likely implement this in record time to19:50
apuimedoI think so19:50
apuimedoas soon as I can spare myself some time or of some of my team19:50
SamYaplei can wrok with you on the ansible bits. those are still in flux19:50
apuimedo:-)19:50
apuimedogreat19:50
SamYaplewould you care to start a blueprint for adding midonet?19:51
SamYapleperhaps some kolla folks can assist as well19:51
harmwhm?19:51
apuimedoI'll have to change our binary binding packaging19:51
apuimedosure thing19:51
apuimedoI'll do that!19:51
SamYaplehave we achieved synergy?19:51
SamYapleis this what that feels like?19:51
apuimedoSamYaple: should I create it in launchpad blueprints or send the spec to gerrit or both?19:51
SamYapleapuimedo: a lunchpad blueprint should be fine19:52
SamYaplethats all we have done for most containers19:52
apuimedogood19:52
SamYaplehonestly midonet doesnt sound much different from OVS from an implementation standpoint19:52
SamYapleso this should be easy-peasy19:53
apuimedoSamYaple: https://blueprints.launchpad.net/kolla19:53
apuimedoSamYaple: it's simpler, since it doesn't need the dhcp agent19:53
SamYapletahts the one19:53
apuimedoand soon it won't need the metadata agent19:53
SamYapleyou had my curiosity, but now you have my attention19:53
apuimedowe only will need to have a custom neutron-api that selects the right plugin, of course19:53
apuimedoSamYaple: well, I'm pushing for reducing moving parts19:54
apuimedoand having them closer to the VMs19:54
SamYapleso neutron-server-midonet?19:54
apuimedoI guess so19:54
SamYapleis this not a selectable plugin with neutron-server?19:54
apuimedoneutron.conf has to be different19:54
SamYaplethat can be handled with ansible19:55
SamYapleif its just the conf the container doesnt need to change19:55
apuimedoand have a midonet pypi package installed19:55
SamYaplethats fine19:55
apuimedonetworking-midonet19:55
apuimedoalright then19:55
apuimedothat makes me happy19:55
apuimedoI don't want separate containers19:55
apuimedoif possible19:55
SamYapleas long as the container can work normally with the package installed thats great19:55
SamYapleas in if we install midonet, we can still use OVS thats perfectly fine19:56
apuimedosure, of course it can ;-)19:56
SamYaplethen perfect we are good to go on our end19:56
apuimedosoon we'll even have an ML2 driver19:56
apuimedoto make it even easier19:56
SamYapleeven better19:56
apuimedohow does the ansible part work, for configuration?19:58
SamYapleid rather not say... :)19:58
apuimedoit puts ansible agents on the containers?19:58
SamYapleits still being flushed out19:58
SamYapleno19:58
*** dims has quit IRC19:58
apuimedoglad to read that :P19:58
SamYaplewe drop the configs in a location on the host19:58
apuimedoof course19:59
apuimedovolumes19:59
SamYaplewe bind mount them in the container and it copies them in to fix the permissions19:59
apuimedoI'm too hungry19:59
apuimedoand my brain lacks fodder19:59
apuimedoI know that what I'm about to say is a bit crazy19:59
apuimedobut, have we considered having nova-docker as well?19:59
SamYaplelol i like you apuimedo20:00
SamYaplei have indeed20:00
SamYaplei even have some code to support it20:00
SamYaplebut there is a bit of an issue with the nova-docker driver being... bad20:00
apuimedogood20:00
apuimedoSamYaple: heh, I have some experience with it20:00
apuimedoI was debugging it a bit for Juno for some customer20:00
apuimedo:P20:00
SamYaplehaving the driver running in the container and managing that same docker host is troublesome20:00
apuimedohad to backport a couple of things20:00
apuimedoit could20:01
apuimedothere's always the docker on docker :P20:01
SamYaplethats what im saying20:01
SamYaplewe share the docker socket into the container20:01
SamYaplethen bam20:01
apuimedono, I meant to use another docker inside20:02
SamYapleoh20:02
SamYapleyea... no20:02
apuimedoI've not tried it20:02
SamYaplelol20:02
SamYaplethat would have lots of namespace issues20:02
apuimedobut it sounds to me like it could be hacked out20:02
*** vinkman has joined #kolla20:02
apuimedoI've heard of people using docker on lxc20:02
*** stvnoyes has joined #kolla20:02
SamYapleplus then the data would be very not persistent, which might be ok i guess20:02
apuimedo(not seen it, so my belief on it is limited)20:03
SamYaplelet me put it this way, i am open to all working implementations20:03
SamYaplewhatever those may be20:03
apuimedoSamYaple: I did worn it would sound crazy20:03
apuimedos/worn/warn/20:03
SamYaplehaha yea i was talking about it a few days back in the channel20:03
SamYapleit is going to happen i promise you20:03
SamYaplejust maybe later rather than sooner20:04
apuimedoI have the suspicion that nova-docker (if it had more devs)20:04
SamYaplewait for things to stablize20:04
apuimedocould be hacked enough to share the docker server20:04
SamYaplethats the key, it would have to20:04
SamYapleif it could then Kolla wouldnt hurt the instances20:05
SamYaplekolla can coexist with teh containers20:05
apuimedo;-)20:06
apuimedogotta go for a while, talk to you later or tomorrow ;-)20:06
SamYaplelooking forward to it20:06
*** apuimedo is now known as apuimedo|away20:06
*** apuimedo|away is now known as apuimedo|dinner20:07
*** vinkman has left #kolla20:07
*** rhallisey has quit IRC20:28
*** stvnoyes has quit IRC20:34
*** bmace has quit IRC20:38
*** pradk has quit IRC20:41
*** bmace has joined #kolla20:50
*** shardy has quit IRC20:54
sdakeyo20:55
sdakewell that was a good power nap21:00
*** blahRus has joined #kolla21:01
*** jtriley has quit IRC21:02
openstackgerritHarm Weites proposed stackforge/kolla: [WIP] Vagrantfile and docs  https://review.openstack.org/20423821:03
openstackgerritSam Yaple proposed stackforge/kolla: Update init-runonce  https://review.openstack.org/20524721:05
SamYaplegood news sdake21:05
SamYapleblank brand new host with that patch works21:05
SamYapleyou are welcome21:05
sdakeit didn't work previously?21:05
SamYaplethe init patch i mean21:06
SamYaplei tested it for you21:06
SamYapleinit-runonce21:06
SamYapleanyway its late im going to bed21:06
SamYapletanksfor all the help21:06
SamYaplewe did accomplish alot today21:06
sdakewe solved a binary equation21:07
sdakenot working -> working21:07
*** jtriley_ has joined #kolla21:15
*** absubram has joined #kolla21:15
*** jtriley__ has joined #kolla21:45
*** jtriley_ has quit IRC21:49
*** achanda has joined #kolla21:49
sdakesamyaple dhcp no worky with master21:53
*** jtriley__ has quit IRC21:54
*** achanda has quit IRC22:23
*** absubram has quit IRC22:26
*** dims has joined #kolla22:39
*** dwalsh has quit IRC22:48
*** coolsvap is now known as coolsvap|away23:00
*** diogogmt has quit IRC23:04
*** weiyu has joined #kolla23:06
*** ashuk has joined #kolla23:10
*** weiyu has quit IRC23:23
*** dims_ has joined #kolla23:24
*** dims has quit IRC23:27
*** jruano has quit IRC23:34
*** blahRus has quit IRC23:45
*** dims_ has quit IRC23:46
*** weiyu has joined #kolla23:50

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