Friday, 2015-07-10

*** sdake_ has joined #kolla00:07
*** sdake has quit IRC00:11
*** jruano has joined #kolla00:14
*** sdake has joined #kolla00:18
*** sdake_ has quit IRC00:21
openstackgerritSteven Dake proposed stackforge/kolla: WIP: Start tgtd in cinder-volume container  https://review.openstack.org/20013900:22
*** mfalatic has quit IRC00:26
*** diga has quit IRC00:37
*** dims has quit IRC00:40
*** jasonsb has quit IRC00:48
*** dolpher has joined #kolla01:04
*** dolpher1 has joined #kolla01:18
*** dolpher has quit IRC01:21
*** erkules_ has joined #kolla01:22
*** dims has joined #kolla01:24
*** erkules has quit IRC01:25
*** dims has quit IRC01:25
*** dims has joined #kolla01:26
*** diogogmt has joined #kolla01:26
*** sdake_ has joined #kolla01:29
*** sdake has quit IRC01:32
*** dims has quit IRC01:36
*** dims has joined #kolla01:37
*** sdake has joined #kolla01:38
*** tobe has joined #kolla01:39
*** sdake_ has quit IRC01:41
*** dims has quit IRC01:42
sdakeanyone around that has launched a vm with nova lately?02:03
sdakegetting 2015-07-10 01:43:46.234 1 ERROR nova.compute.manager [instance: ce6bfd6c-a160-4302-bb99-70c9b8e2e317] libvirtError: Failed to create controller cpu for group: No such file or directory02:03
*** vinkman has joined #kolla02:09
*** jasonsb has joined #kolla02:20
*** achanda has joined #kolla02:23
sdakewould appreciate if someone could confirm by either reproducing from a build of master or indicate whether their version works...  Make sure to do a clean build.02:26
sdakehttps://bugs.launchpad.net/kolla/+bug/147327002:26
openstackLaunchpad bug 1473270 in kolla "compute container prints exception libvirtError: Failed to create controller cpu for group: No such file or directory" [Critical,Triaged] - Assigned to Steven Dake (sdake)02:26
*** dims has joined #kolla02:38
*** jruano has quit IRC02:39
*** achanda has quit IRC02:42
*** dims has quit IRC02:43
sdakesamyaple ping me when you arrive pls ;)02:55
*** diogogmt has quit IRC03:08
*** jruano has joined #kolla03:30
*** gfidente has quit IRC04:01
*** jruano has quit IRC04:07
*** achanda has joined #kolla04:20
*** tobe has quit IRC04:44
*** sdake_ has joined #kolla04:58
*** sdake has quit IRC05:00
*** sdake has joined #kolla05:00
*** dims has joined #kolla05:03
*** sdake_ has quit IRC05:03
*** dims_ has joined #kolla05:04
*** dims has quit IRC05:08
*** dims_ has quit IRC05:08
*** vinkman has quit IRC05:19
*** Slower has joined #kolla05:38
harmwit sucks $office is requiring a proxy05:48
harmwmakes building containers impossible05:48
*** dims has joined #kolla06:01
*** dims has quit IRC06:09
*** achanda has quit IRC06:11
*** dims has joined #kolla06:13
*** dims_ has joined #kolla06:14
*** erkules_ is now known as erkules06:15
*** erkules has joined #kolla06:15
harmwpbourke: gen-source-tar.sh is missing +x06:16
*** dims has quit IRC06:17
*** dims_ has quit IRC06:21
*** dims has joined #kolla06:22
*** dims has quit IRC06:27
*** inc0 has joined #kolla06:29
inc0good morning06:30
harmwhttps://github.com/docker/docker/pull/9176#issuecomment-118222682 there, building now behind a proxy :)06:32
inc0yes please06:34
harmwbuilding all containers now, looks fine so far :)06:34
*** tobe has joined #kolla06:45
*** shardy has joined #kolla07:09
harmwdone07:14
harmwfailed: magnum-conductor, barbican, swift07:16
harmwThe command '/bin/sh -c cd /tmp && curl -L https://github.com/GoogleCloudPlatform/kubernetes/releases/download/v0.15.0/kubernetes.tar.gz -o /tmp/kubernetes.tar.gz && /usr/bin/tar -xzvf /tmp/kubernetes.tar.gz && cp -a /tmp/kubernetes/platforms/linux/amd64/kubectl /usr/bin/kubectl && rm -rf /tmp/kubernetes' returned a non-zero code: 3507:20
harmwwhy is there even a -o there :/07:20
vincent_vdkmorning07:22
*** jmccarthy has joined #kolla07:23
*** SamYaple has quit IRC07:29
harmwbuilding magnum now, https_proxy wasn't set properly07:29
harmwmorning vincent_vdk07:29
*** shardy_ has joined #kolla07:33
harmwand it's done, great07:34
*** shardy has quit IRC07:35
harmwuhm, why is tools/kolla requiring root again?07:37
*** shardy_ has quit IRC07:38
*** shardy has joined #kolla07:39
vincent_vdkso i added python-oslo-reports to the cinder-base yum install line and rebuild07:41
vincent_vdkbut still geting ImportError: No module named oslo_reports07:42
harmwisn't that in the base-base?07:46
harmwand perhaps --no-cache is needed07:46
vincent_vdki'll add it to base-base and see what happens07:51
harmwit's not litteraly base-base07:51
harmwsry07:51
harmwit's centos-base or something similar07:52
vincent_vdki have docker/centos/rdo/base07:52
harmwjust check whatever cinder-base has for FROM07:52
harmwyep, ok07:52
vincent_vdki added it to cinder-base07:52
vincent_vdki'll add it to base-base now07:52
vincent_vdkhmm, oslo.service comes from pip07:53
vincent_vdkall the others from rpm07:53
harmwit got rebranded to oslo_service recently07:53
harmw*everything oslo07:53
vincent_vdkso base should have everything then07:53
vincent_vdkah, No package python-oslo-reports available07:56
openstackgerritSam Yaple proposed stackforge/kolla: Fixes an issue with AIO and galera clusters  https://review.openstack.org/19940608:02
harmwheat looks broken: ERROR: openstack 'NoneType' object does not support item assignment08:02
harmwnot sure why yet08:02
openstackgerritMerged stackforge/kolla: Add source keystone image for oraclelinux  https://review.openstack.org/19183308:05
*** jmccarthy1 has joined #kolla08:08
*** jmccarthy has quit IRC08:08
*** jmccarthy1 has quit IRC08:08
*** jmccarthy has joined #kolla08:08
harmwsdake: nova is stuck in SPAWNING08:25
*** shadower has joined #kolla08:25
*** coolsvap|afk is now known as coolsvap|away08:26
*** coolsvap|away is now known as coolsvap08:28
harmw"Build of instance 26fdc82a-5ca1-4b51-a781-b69af030d54f aborted: Failed to allocate the network(s), not rescheduling."08:28
*** gfidente has joined #kolla08:37
*** SamYaple has joined #kolla08:39
SamYaplehola08:40
*** dims has joined #kolla08:40
jmccarthyo/08:41
*** dims has quit IRC08:45
inc0SamYaple, hello, tell me plz, where do you register endpoint in glance08:49
inc0still in container?08:49
inc0or it'll be in register.yml?08:49
SamYapleGARRAGAGARAR08:50
SamYaplei dont yet.08:50
SamYapleworking on it08:50
SamYaplehttps://review.openstack.org/#/c/199463/08:50
inc0no worries, I'm just looking for a place for VIPs08:51
inc0ahh, you're making an module!08:51
SamYapleunfortunately :(*08:52
inc0yeah, I know, I'll look for haproxy module then08:52
inc0maybe there is something like that already08:52
inc0http://docs.ansible.com/haproxy_module.html there is and it's in main tree!08:53
SamYaplewait. why should we need an haproxy moule08:53
inc0I was thinking on changing our haproxy vips dynamically08:53
SamYapleyou cant do that with haproxy08:54
SamYaplerequires a config reload08:54
SamYaplethe socket is super limited08:54
inc0yes, I know08:54
SamYaplethe haproxy module only talks to the socket though08:54
inc0but we don't want to make haproxy "fire and forget"08:54
SamYapledidnt we have this conversation yesterday?08:55
inc0ah so you can't add backend dynamically?08:55
SamYapleright08:55
inc0forget about that then, gonna play with config08:55
SamYaplehere is my plan08:55
inc0go on08:55
SamYapledrop confs in conf.d per service. docker exec haproxy  to trigger a "config update" script which will pull in the new configs. HUP the process to reread the configs (without killing existing connections)08:56
SamYaplenot sure we can HUP the pid 1 in docker without crashing the contaienr, so we may need supervisord or something08:56
inc0I'll figure it out08:57
vincent_vdkyou can use consul and registrator to dynamically change the HA config09:04
SamYapleno to consul09:04
vincent_vdkwhy not?09:05
SamYapleit wont do exactly what we want, but more importantly, no external dependacies or additional services like that09:05
vincent_vdkwhat are no external dependacies or additional services09:06
SamYaplelet me change the question vincent_vdk, where would consul run?09:07
vincent_vdkin a docker container09:07
vincent_vdki used it for a project09:08
SamYaplethat is an additional service unrelated to deploying openstack09:08
vincent_vdkHAproxy is one too then. or not?09:08
SamYapleno, because that is _required_ to get it work HA09:09
SamYapleconsul is not09:09
SamYaplewe have gone over this in the community before, and the community shot down consul. You can propose it again if you would like09:09
*** jmccarthy has quit IRC09:10
*** jmccarthy has joined #kolla09:10
*** athomas has joined #kolla09:12
vincent_vdkit would solve your issue with static HA config though09:15
vincent_vdkbut nevermind09:16
harmwhe, lets deploy on top of mesos while at it! :>09:16
SamYaplevincent_vdk: what issue?09:16
vincent_vdkSamYaple: nevermind09:17
vincent_vdki'm just strugeling with an HA idea for our own use here09:17
*** dolpher1 has quit IRC09:25
vincent_vdkbut to give you an idea http://blog.xebia.com/2015/03/24/a-high-available-docker-container-platform-using-coreos-and-consul/09:33
harmwthat stuff is more microservice-oriented, not neccesarily something like Openstack09:34
SamYaplevincent_vdk: oh i know how consul works. I happen to not like it09:34
harmwwould be fun to make up something using consul and the likes though09:35
SamYaplei mean, the containers can be used standalone/with a different deploy method09:36
SamYaplethats kinda the point of this whole project09:36
vincent_vdkwell, one could take kolla and build consul around it for its own usage09:39
vincent_vdkso the current idea is to deploy a set with ansible and add these to the HAproxy config09:41
SamYaplevincent_vdk: its not one large haproxy config file, its a config file per service, but yes09:41
vincent_vdkok, that matches the current TripleO deployment more09:43
openstackgerritPaul Bourke proposed stackforge/kolla: Fixes an issue with AIO and galera clusters  https://review.openstack.org/19940609:53
harmwis there a bug targetting magnum not having +x on those config- scripts?09:59
SamYapleharmw: only start.sh and config-internal.sh need +x10:07
harmwfine, but they currently lack that :)10:07
harmwjust like Horizon, but there's a merge pending on that10:08
SamYapleno idea then10:08
harmwERROR (InstanceInErrorState): Build of instance f343e2a6-e3c0-445b-949b-6f52b5f5a254 aborted: Failed to allocate the network(s), not rescheduling.10:08
harmwthat sucks however10:08
harmwbooting a new instance on a fresh kolla cloud10:08
*** jmccarthy has quit IRC10:11
*** jmccarthy has joined #kolla10:11
openstackgerritSam Yaple proposed stackforge/kolla: Add temporary Ansible keystone modules  https://review.openstack.org/19946310:16
SamYapleharmw: would you mind https://review.openstack.org/#/c/199406/10:18
SamYaplehad to rebase10:18
SamYaplewait pbourke why did you commit to my patchset10:19
SamYaplepbourke: please dont do commit to other peoples patchsets unless you have discussed it with them10:21
pbourkeSamYaple: I just used the rebase button10:21
pbourkeSamYaple: didn't push any code10:21
SamYapleyea but i had already rebased10:21
SamYapleand it screws with stats10:22
pbourkesorry10:22
SamYapleits cool, just dont mess with patchsets that arent yours without tlaking to the owner10:23
*** dims has joined #kolla10:28
openstackgerritSam Yaple proposed stackforge/kolla: Fixes an issue with AIO and galera clusters  https://review.openstack.org/19940610:29
*** dims_ has joined #kolla10:29
SamYaplepbourke: that ended up being helpful. made me catch a mistake10:30
pbourkeSamYaple: that was my intention all along ;)10:30
SamYaplemwahaha10:31
*** dims has quit IRC10:33
*** dims_ has quit IRC10:34
*** coolsvap is now known as coolsvap|away10:43
harmwinteresting, docker-compose -f compose/horizon.yml logs11:08
harmwis showing me all services11:08
harmwinstead of only horizon11:08
*** jmccarthy has quit IRC11:08
*** jmccarthy has joined #kolla11:08
*** rhallisey has joined #kolla11:14
*** tobe has quit IRC11:15
*** tobe has joined #kolla11:16
harmwpbourke: you remember what was up with this error? NovaException: Unexpected vif_type=binding_failed11:16
pbourkeharmw: yeah that one is a pain11:16
pbourkeharmw: I cant really remember the specifics though :( I think there's a number of reasons that can cause it, anything to do with neutron not been able to succesfully create the virtual interfaces11:18
harmwall I remember is you caught it once and i hinted at a solution :p just can't remember the solution anymore11:19
pbourkeI have something in my notes around nova-server not registering mech drivers11:20
harmwah11:20
harmwEUTRON_FLAT_NETWORK_INTERFACE=eth111:20
harmwthat's a problem11:20
pbourkeyeah if that doesn't work make sure nova is loading the l2 mechanism drivers correctly11:21
*** gfidente has quit IRC11:25
*** tobe has quit IRC11:45
*** slagle has joined #kolla11:45
SamYaplei know that error harmw! i have done lots of answers for that11:46
harmwthe solution is up there11:47
harmw:)11:47
harmw(eth1 doesn't exist)11:47
harmwgenenv asumed it did, or I didn't bother to change it :p11:47
SamYapleyea eth1 not existing is the solution to fix the environment11:48
SamYaplebut that error is alot more complicated than that11:48
harmwoh yes11:48
harmwI've seen it numerous times11:48
harmwwith different causes11:48
SamYapleanyway its the source of lots of networking problems because neutron uses subprocess to wrap commands rather than useful python libraries11:48
*** prad has joined #kolla11:55
SamYapleso crux only supports keystone v2.0 which explains why i wasn't able to use it in the container12:04
harmwwicked, instance is running again sdake12:06
harmwIll file a bug+fix tonight12:07
SamYapleVICTORY12:08
*** absubram has joined #kolla12:08
SamYapledatabase rabbit keystone glance cominug up and registering themselves12:08
SamYapleidempotently as well12:09
harmwcool stuff Sam12:09
*** absubram has quit IRC12:10
*** absubram has joined #kolla12:10
*** dims has joined #kolla12:15
*** dims has quit IRC12:20
*** dwalsh has joined #kolla12:27
*** jruano has joined #kolla12:29
*** ccrouch has joined #kolla12:37
*** diogogmt has joined #kolla12:39
*** dims has joined #kolla12:41
openstackgerritSam Yaple proposed stackforge/kolla: Add temporary Ansible keystone modules  https://review.openstack.org/19946312:42
*** absubram has quit IRC12:43
*** coolsvap|away has quit IRC12:47
*** shadower has quit IRC12:48
*** sdake_ has joined #kolla12:50
*** coolsvap|away has joined #kolla12:51
*** coolsvap|away is now known as coolsvap12:53
*** sdake has quit IRC12:54
*** diogogmt has quit IRC13:01
*** diogogmt has joined #kolla13:04
*** gfidente has joined #kolla13:05
*** gfidente has joined #kolla13:05
*** inc0 has quit IRC13:07
*** thumpba has joined #kolla13:09
*** jmccarthy has quit IRC13:10
*** jmccarthy has joined #kolla13:11
*** athomas has quit IRC13:13
*** athomas has joined #kolla13:20
*** rhallisey has quit IRC13:20
*** rhallisey has joined #kolla13:23
*** shardy_ has joined #kolla13:37
*** shardy has quit IRC13:39
*** dolpher has joined #kolla13:39
*** shardy_ has quit IRC13:42
*** shardy has joined #kolla13:43
*** sdake_ has quit IRC13:51
*** dolpher1 has joined #kolla14:04
*** dolpher has quit IRC14:06
*** dolpher has joined #kolla14:09
*** jmccarthy has quit IRC14:10
*** jmccarthy has joined #kolla14:10
*** dolpher1 has quit IRC14:10
*** pbourke has quit IRC14:20
*** pbourke has joined #kolla14:21
*** thumpba has quit IRC14:39
*** dims has quit IRC14:40
*** jtriley has joined #kolla14:43
*** jtriley has quit IRC14:43
*** jtriley has joined #kolla14:43
*** jtriley has quit IRC14:43
*** jtriley has joined #kolla14:43
*** coolsvap is now known as coolsvap|away14:50
*** britthouser has quit IRC14:53
*** inc0 has joined #kolla15:06
*** dims has joined #kolla15:07
*** dims_ has joined #kolla15:07
*** dims has quit IRC15:11
inc0guys, especially SamYaple, you think keystone should put its haproxy to haproxy15:14
inc0haproxy's conf.d? or haproxy should do that?15:14
inc0if former, how do we make decision if to put it there alltogether, and if latter, how to provide full list of services to be configured?15:15
inc0I'm talking about ansible.15:15
inc0thoughts?15:16
*** sdake has joined #kolla15:20
sdakeharmw which bug did you find15:21
SamYapleinc0: what are you asking again?15:22
SamYapleshould keystone have a seperate conf.d file, or should it existi nthe haproxy conf?15:22
inc0no, there will be haproxy conf.d15:22
sdakerhallisey ping15:23
rhalliseysdake, hey15:23
inc0and if we run ha-setup, keystone on deployment will add its set of endpoints to this folder (/opt/kolla/haproxy/conf.d)15:23
sdakeis anyone able to get instanscas into the running state15:23
inc0and call hup on haproxy container15:23
sdakerhallisey why does cinder-api require python-eystone15:23
SamYaplesdake: for authentication?15:24
rhalliseylet me find the bug..15:24
inc0that's my idea15:24
*** shardy_ has joined #kolla15:24
SamYapleoh keystone, not keystoneclient15:24
sdakesamyaple in the same container...15:24
SamYapleinc0: yea thats what i was proposing to you, except it is going to have to work a bit different than that15:24
inc0other idea would be to haproxy somehow know which services it's supposed to configure, and add these configs by itself15:24
rhalliseyhttps://bugs.launchpad.net/kolla/+bug/146918215:25
openstackLaunchpad bug 1469182 in kolla "Cinder API requires python-keystone package" [High,Fix committed] - Assigned to Ryan Hallisey (rthall14)15:25
SamYapleinc0: that model works poorly, i used that for yaodu15:25
inc0I'm in favor of first one as well15:25
SamYapleinc0: so basically the keystone role _itself_ cannot add the conf to haproxy15:25
SamYaplewell have to do it a bit different15:25
inc0why?15:25
sdakerhallisey we odnt need all of eystone for that, we only need the eystonemiddleware package15:25
*** shardy has quit IRC15:25
SamYaplebecause haproxy is not gauranteed to run on the same nodes as keystone15:25
inc0hmm...good point15:26
SamYapleinc0: i know the model that will work, just get the container functional15:26
SamYapleill work with you on how the model should look15:26
inc0care to share it with me?15:26
SamYapletest the HUP thing esspecially, because that determines if we need supervisord15:27
SamYapleinc0: yea but i have to run out15:27
inc0ok, I'll ping you on monday15:27
SamYaplecool, im always around15:27
SamYapleyea you get the contaienr solid and ill help you with the ansible bits15:27
inc0I'm ok with ansible bits, I want to learn it anyway15:28
inc0just let me know what you have in mind;)15:28
rhalliseysdake, ya fine with me, I wasn't sure where to get it by itself15:28
*** absubram has joined #kolla15:28
sdakerhallisey no big deal just saw it in the ode and was like "wtf" :)15:29
inc0SamYaple, a callback plugin maybe15:29
sdakemy vms never enter a running state15:29
inc0?15:29
sdakeso i am  totallly jammed up15:29
*** shardy_ has quit IRC15:29
SamYapleinc0: the issue is the role itself cannot address hosts in a seperate group than the ones specified initially15:30
*** shardy has joined #kolla15:30
inc0but can it call some sort of callback on ansible itself, and ansible in turn will do stuff?15:30
rhalliseysdake, :)15:31
SamYapleyea but thats far from best practice :)15:31
SamYapleinc0: in fact, if you want to just on #ansible i should really ping them about the best way to handle this15:31
inc0I'll do that15:31
inc0and we'll see if this matches your idea15:31
inc0we'll get more problems like this one as we go on I guess15:32
SamYapleinc0: i do need to go, so ive asked the question, feel free to move the discussion along15:33
inc0kk15:33
inc0cya later15:33
SamYaplewell i see where you came up with callbacks15:34
inc0not exactly this one, but yeah, that would work I guess15:35
SamYaplerhallisey: hey. crux. it only supports v2.0 keystone15:37
rhalliseyoh really15:38
rhalliseyI think we can remove it at some point15:38
inc0hmm...ha playbook that will be called on register might work15:38
rhalliseyjust do the keystone calls15:38
sdakeharmw did you fix some problem?15:40
sdakecan ppl tell me if they have got nova booting in kolla lately?15:40
sdakeas in the last 2 weeks15:40
SamYapleas a whole we should talk about v3 keystone15:41
inc0SamYaple, how about this set_facts?15:44
SamYaplenope15:44
inc0why? if we'd set them in ks and configure haproxy afterwards15:44
inc0based on them15:44
SamYapleone, thats horribly ugly, two it still wouldnt do what we need because that means the haproxy role lays down ALL the configs15:45
inc0not too bad tho15:45
inc0one template per config15:45
inc0I mean one template, and facts determine how its filled15:46
SamYapleinc0: its pretty bad actually15:46
inc0this will keep all haproxy login in haproxy15:46
inc0which is good.15:46
SamYaplewell that would happen anyway15:46
inc0and DRY-happy15:46
inc0we add new service to playbook, rerun playbook and at the end of haproxy play do a hup15:47
SamYaplewhat im trying to avoid is including the haproxy hosts in each role and using a when conditional for all tasks15:47
inc0but you wont15:48
inc0you'll just fill facts15:48
inc0in each role15:48
inc0which isn't that bad anyway considering things like keystone port15:48
SamYaplefacts dont cross roles15:49
inc0ah...15:49
SamYaplealso this means the haproxy role is either run after EACH service, or it is run at the end of everything15:49
inc0is there anything that does?15:49
SamYapleboth bad15:49
SamYapleacross roles? i dont think so15:49
inc0end of everything isn't that bad tho15:49
SamYapleinc0: it is because all the services have to hit haproxy to talk to keystone and eachother :)15:50
SamYapleand the database15:50
inc0hmf15:50
inc0ok, I won't keep you Sam, thanks15:50
inc0I'll read a bit more about features we could potentially use15:51
SamYaplei think the best way might be to call the haproxy role initially and have it lay down all the configs that will be used15:51
SamYaplewell have all the facts to do so and it will just online serice as they check in15:51
inc0but we dont know which ones will15:51
SamYapleyes we do15:51
inc0where and how?15:52
SamYaplewe have access to all the same variables "use_cinder: True" then for the config file "when: use_cinder"15:52
inc0I wanted to avoid having list of services hardcoded in config...15:52
SamYapleinc0: well we have to do that....15:53
inc0we'd need to dig into vars from roles anyway15:53
SamYaplehow so15:53
inc0because keystone_port might be something else than 500015:53
SamYaplethat stuff exists in global for a few reasons15:53
SamYapleports and groups are all we need and we have it15:53
*** achanda has joined #kolla15:54
*** mfalatic has joined #kolla15:55
SamYaplek gotta go for realzz15:55
inc0ok SamYaple, go to sleep, cya in Monday15:55
SamYaplebai15:55
*** mfalatic_ has joined #kolla15:56
*** dolpher1 has joined #kolla15:56
*** dolpher has quit IRC15:57
*** mfalatic has quit IRC16:00
sdakelater inc016:07
inc0hehe I was only now writting that I'm going off16:07
inc0you're fast sdake!16:07
inc0sooo...cya all next week:)16:08
*** inc0 has quit IRC16:08
*** jmccarthy has quit IRC16:10
*** jmccarthy has joined #kolla16:10
*** vinkman has joined #kolla16:12
sdakesamyaple did we decide to use our own module or the osad module16:13
sdakesamyaple and by we I mean you :)16:14
*** sdake_ has joined #kolla16:19
openstackgerritBorneMace proposed stackforge/kolla: Fixed all remaining pep8 failures in the codebase  https://review.openstack.org/20061216:21
*** sdake has quit IRC16:22
harmwsdake_: yes, gimme a sec16:34
*** jtriley has quit IRC16:35
harmwsdake_: https://bugs.launchpad.net/kolla/+bug/147350016:35
openstackLaunchpad bug 1473500 in kolla "neutron-linuxbridge fails because of missing ebtables binary" [Undecided,New]16:35
*** jtriley has joined #kolla16:40
*** sdake_ has quit IRC16:43
*** jmccarthy has quit IRC16:43
*** dolpher1 has quit IRC16:44
*** sdake has joined #kolla16:45
*** dims_ has quit IRC16:46
harmwany tried to build a base image lately?16:46
harmwlike, last couple of hours?16:46
*** dims has joined #kolla16:46
*** dims has quit IRC16:47
*** dims has joined #kolla16:47
SamYaplesdake: once the OSAD one merges ill look at it16:48
SamYaplesdake: its probably a week from merge or so. by then we may just keep using mine if it works like we want16:48
harmwlooks like there is an issue with delorean: curl http://trunk.rdoproject.org/centos70/current/delorean.repo16:49
SamYaplesdake: i rewrote deguerri modules as well and put an explicit asl2.0 license so there is no confusion16:49
*** mfalatic_ is now known as mfalatic16:51
harmwsdake: who should I bug regarding a 404 on above url16:51
harmwjust rdo ML?16:51
sdakeharmw hang tight a moment16:54
sdakeharmw join #rdo16:55
*** bitblt has joined #kolla17:01
sdakeharmw try http://trunk.rdoproject.org/centos7/current/delorean.repo17:10
sdakehey lets change things for no good reason!17:10
harmwand not include a redirect17:11
harmwI want a redirect17:11
harmwlamers17:11
sdakei'll file a bug17:11
sdakegetting redirects on fedora infra is alot of work17:11
*** britthouser has joined #kolla17:13
harmwright, and changing some folder is not17:13
harmwbaseurl=http://209.132.178.14/centos7/1a/4c/1a4c958c1c98dc27bd8f8ecd2779e8adad4303d4_9c7271d917:14
harmwwtf17:14
harmwwhy is there an IP in there17:14
sdakehttps://bugs.launchpad.net/kolla/+bug/147351317:16
openstackLaunchpad bug 1473513 in kolla "delorean repo location changed" [Critical,Confirmed] - Assigned to Harm Weites (harmw)17:16
sdakeharmw can you apply a fix17:17
harmwnoes!17:17
harmwI'm building a new base17:17
sdakenah anyon ecan control folder destination17:17
harmwso gimme a sec17:17
sdakeits just a mv operation17:17
harmwthats insane17:17
*** gfidente has quit IRC17:17
sdakea redirect requires admin privs17:17
harmwppl should *think* before mv17:18
harmwlike mv -i17:18
*** sdake_ has joined #kolla17:19
sdake_harmw do you have an ebltables patch?17:21
sdake_or know what to do to fix?17:21
harmwyep17:21
harmwjust add the package17:22
sdake_wich package to which docker file17:22
harmwI wanted to test the fix, fully17:22
sdake_i just want to see if  that is why nova wouldn't boot17:22
harmwebtables, to neutron-linuxbridge17:22
harmwI got the fix right here17:22
*** sdake has quit IRC17:23
openstackgerritHarm Weites proposed stackforge/kolla: Fix the delorean repo url  https://review.openstack.org/20063717:24
bmaceany other core around able to take a quick look at https://review.openstack.org/#/c/200612 ?  i would love to get the pep8 test actually working correctly today :)17:29
sdake_harmw if you c an plz look above17:31
harmwbmace: https://review.openstack.org/#/c/200612/1/docker/centos/binary/neutron/neutron-base/ip_wrapper.py L4117:33
harmwdoes that work?17:33
sdake_syntax looks ok to me17:33
harmwI simply don't know, could be some kind of appender is needed17:34
harmwSamYaple: can you ack that repo fix?17:35
bmaceL41? the comment line?17:35
harmwcomment? no that print()17:35
harmwprint(17:35
harmw"bla"17:35
harmw"blabla"17:35
harmw)17:35
bmaceah, i looked it up.  i had tossed a \ in there to split lines but flake8 told me to yank it17:35
harmwthat just works? or should there be a + after the first "bla"?17:36
harmwok, sounds like it's ok17:36
harmwsdake_: you confirmed the ebtables fix?17:36
bmaceand i ran it through the python interpreter like that and it works :)17:36
harmwcool bmace :)17:36
sdake_have not17:37
harmwwill do?17:37
sdake_still building17:37
harmwor should I?17:37
harmwok17:37
sdake_did you think that owuld fix the nova instances not starting?17:37
sdake_i am using neutron in my startup (demos/heat/launch)17:37
harmwit did earlier today17:37
harmwI got an error regarding neutron, and in logs it bailed because of not finding ebtables17:37
openstackgerritMerged stackforge/kolla: Fixed all remaining pep8 failures in the codebase  https://review.openstack.org/20061217:38
sdake_harmw is there an ebtables bug filed and a patch up?17:41
harmwbug yes, patch not yet17:42
harmwI'm almost ready to test17:42
harmwand submit17:42
sdake_link to bug plz17:42
sdake_so i can set it appropriately17:42
harmwhttps://bugs.launchpad.net/kolla/+bug/147350017:42
openstackLaunchpad bug 1473500 in kolla "neutron-linuxbridge fails because of missing ebtables binary" [Critical,Confirmed] - Assigned to Harm Weites (harmw)17:42
sdake_or you can17:42
sdake_looks like its set17:42
sdake_all goo then17:42
*** prad has quit IRC17:53
*** sdake has joined #kolla17:55
openstackgerritHarm Weites proposed stackforge/kolla: Install ebtables in neutron-linuxbridge  https://review.openstack.org/20064217:56
sdakejpeeler or rhallisey can you ack those last two changes17:57
*** shardy has quit IRC17:58
*** sdake_ has quit IRC17:59
bmaceinteresting, apparently the "hacking" version of flake8 used via most other ostack projects is more strict than normal flake8, so there are still some issues to fix :/18:01
sdakethe rules are determined by the pep8 file18:03
sdakerather by the tox.ini file18:03
openstackgerritHarm Weites proposed stackforge/kolla: Add +x to Magnum's config-internal.sh scripts  https://review.openstack.org/20064518:03
bmacethat isn't the only thing.  if you use just vanilla flake8 that you grab via pip you will get different output than if you use the flake8 you get from the hacking package ostack projects usually use.18:04
sdakerux tox -e pep8 and it will apply the hacking rules18:04
bmaceit adds stuff like complains about missing apache 2 headers, etc.18:04
sdakebut wasn't aware of that - although differnett rules aer applied18:04
bmacebased on what we had before, it wouldn't.  we didn't even have "hacking" as a test requirement18:04
openstackgerritMerged stackforge/kolla: Install ebtables in neutron-linuxbridge  https://review.openstack.org/20064218:10
*** sdake_ has joined #kolla18:13
*** coolsvap|away is now known as coolsvap18:13
*** sdake has quit IRC18:16
sdake_harmw nice work - confirmed those two changes get me active instances18:19
openstackgerritMerged stackforge/kolla: Fix the delorean repo url  https://review.openstack.org/20063718:20
sdake_rhallisey how do you attach a cinder volume to a nova instance18:21
rhalliseynova volume-attach <instance_name> <cinder_id>18:21
rhalliseythen check nova-compute for volume attach successful18:21
rhalliseyor something like that18:21
sdake_seems to attach18:22
sdake_i can't actually login to the vm to verify unfortunately18:25
* sdake_ groans18:25
*** sdake_ is now known as sdake18:25
sdakeone of these days my network will work consistently18:25
sdakeharmw can you test out cinder18:27
sdakeharmw sincey our can get int oyour vms apparentl.y with one nic magically :)18:28
harmwI should verify that once18:28
sdakeoh you havenever sshed in?18:28
harmwnova console-log is just cheating18:28
harmwI have, just not recently18:28
sdakeoh let me try console log18:28
harmwconsole-log is just showing the console.log from your instance18:29
*** dims has quit IRC18:29
harmwso you can atleast check if it finished booting18:29
harmwwithout issues18:29
sdakeit doesn't appear to show the drive attached18:29
harmwI've got one more bugfix thats annoying the shit out of me for ages :p18:30
harmwhttps://bugs.launchpad.net/kolla/+bug/147133118:30
openstackLaunchpad bug 1471331 in kolla "tools/kolla concluding to soon deployment has succeeded" [Undecided,New] - Assigned to Harm Weites (harmw)18:30
rhalliseysdake, if you're not seeing any complaints on nova compute it should be working18:30
sdakerhallisey i get this after a cinder attach http://ur1.ca/n35dm -> http://paste.fedoraproject.org/242773/1436553018:31
sdakehttp://ur1.ca/n35e2 -> http://paste.fedoraproject.org/242774/6553142118:32
sdakeis this the error you got rhallisey?18:32
sdakecinder volume missing config options18:34
sdakehttp://ur1.ca/n35ee -> http://paste.fedoraproject.org/242776/5324214318:34
rhalliseyoh18:34
rhalliseygetting closer nice18:35
rhalliseywhere's my lock_path patch..18:35
*** diogogmt has quit IRC18:37
rhalliseysdake, just set lock_path via crudini18:37
rhalliseyI think I have a missing branch for my cinder work I need to find..18:38
harmwrhallisey: you had that, once18:38
sdakeset to what?18:38
harmwI remember we uncovered that18:38
sdakeshould it be shared between nova as well?18:38
sdakenova has a lack path for instances18:38
rhalliseyharmw, ya I remember18:38
rhallisey/tmp/cinder_lock18:39
rhalliseyor something18:39
sdaketaht should be persistent - so /var/run/cinder18:40
sdake /var/lib/cinder/lock that is18:40
*** diogogmt has joined #kolla18:40
sdakebut my question is is the same lock path used in nova18:40
rhalliseyok that works18:40
sdakeor do you know/not know?18:40
rhalliseyI don't know18:40
rhalliseylock_path showed up about a few days before liberty18:40
sdakewhat other gems are hiding in your lost repo :)18:43
rhalliseynot sure, a lot of this stuff showed up right before the release18:44
rhalliseyit's odd cause I remember talking with harmw about lock_path18:44
harmwyep, we did18:47
openstackgerritHarm Weites proposed stackforge/kolla: Properly wait for Openstack services to be ready  https://review.openstack.org/20065518:47
harmw^^ woohoo to that18:48
sdakedoes it go in the default section?18:49
sdakeI am going to set disable_process_locking to true instead18:49
sdakebut not sure which section it goe in18:49
*** athomas has quit IRC18:51
rhalliseysdake, ya default18:52
sdakedefault is deprecated18:54
sdakeits sactually oslo_concurrency18:54
*** athomas has joined #kolla18:56
bmacehrm.. am i still connected?  put up a review but no message in the channel from gerrit19:08
*** bmace has quit IRC19:09
*** bmace has joined #kolla19:09
*** dims has joined #kolla19:12
harmwsdake: rhallisey if you got the time, could you take a look at that review up above?19:14
harmwsdake: I can't bridge my wifi, so I'll give singlenic another go within my virtualboxed CoreOS19:15
harmwsee what happens19:15
*** achanda has quit IRC19:16
*** vinkman has left #kolla19:16
*** dims has quit IRC19:17
*** dims has joined #kolla19:17
harmwbah, building containers is probably going to take a while19:31
openstackgerritBorneMace proposed stackforge/kolla: Fixes the last of the hacking based pep8 errors  https://review.openstack.org/20069019:39
bmaceand, after these two reviews are done we can get pep8 actually turned on! :)19:40
sdakerhallisey looks like there are errors here:19:47
sdakehttps://bugs.launchpad.net/kolla/+bug/146932319:47
openstackLaunchpad bug 1469323 in kolla "cinder nova volume attach not working" [Critical,Triaged] - Assigned to Ryan Hallisey (rthall14)19:47
sdakeI added to the bug log19:47
sdakerhallisey please make it a priority to get this resolved ;)19:47
sdakewe are half way thorugh liberty 2 and this bug remains open19:48
rhalliseyya blew up my env today will get to fixing that..19:48
harmwsdake: https://blueprints.launchpad.net/kolla/+spec/standard-start19:49
openstackgerritSteven Dake proposed stackforge/kolla: Add oslo.reports as a global dependency  https://review.openstack.org/20029819:49
openstackgerritSteven Dake proposed stackforge/kolla: Change permissions on cinder config-internal/external  https://review.openstack.org/20005519:49
openstackgerritSteven Dake proposed stackforge/kolla: WIP: Start tgtd in cinder-volume container  https://review.openstack.org/20013919:49
openstackgerritSteven Dake proposed stackforge/kolla: Turn off oslo_conccurrency locking in volume driver  https://review.openstack.org/20069319:49
bmaceharmw: about your comment.  that comment needs to either have a summary added to it, or be squashed enough to be a single line comment.  right now it is a broken multi-line comment :/19:49
bmaceharmw: and a decent summary didn't immediately come to mind.19:50
harmwbmace: uhm, we can't have multi-line comments?19:50
sdakeyou can just put end in " and put in "19:50
bmaceharmw: not of that structure, no, multi-line comments require a summary on the """ start line19:50
sdakethe next line19:50
sdakehae to wrap at 79 characters19:50
sdakeoh thattype of comment19:50
harmwi know sdake , but bmace why not do just that?19:51
sdakeya bmace is correct19:51
harmwchange the commenttype?19:51
harmwsummary: organize bla19:51
harmwand BAM, you're done :)19:51
harmw(and can insert the multiline)19:52
bmaceyeah, i'll put in a very brief summary.19:52
*** sdake_ has joined #kolla19:52
*** sdake has quit IRC19:56
openstackgerritBorneMace proposed stackforge/kolla: Fixes the last of the hacking based pep8 errors  https://review.openstack.org/20069019:57
harmwsdake_: you agree on closing the standard-start spec which I just did?19:57
sdake_if its done19:57
sdake_it looks done to me19:57
harmwI've updated the spec's whiteboard19:58
harmwto reflect the missing bits19:58
sdake_what is missing19:58
harmweg. mariadb, mongodb, hautoproxy19:58
sdake_ok19:58
harmwand how they will be dealt with19:58
sdake_we should probably open a new blueprint for those 319:58
sdake_especially mongodb - should be done in this blueprint if possible19:59
harmwit needs additional work, since it's using entrypoint crap19:59
harmwmay be combined, but still, plus I don't know if the damn thing even works :p20:00
harmwwhich is why I put it aside20:00
harmwsince it's a dependecny for ceilometer, there could very well be just some get-ceilometer-to-operate spec20:01
sdake_there already is20:01
harmwcool20:01
sdake_but it doesnt include dependencies20:01
* sdake_ would like to see cinder working asap ;-)20:01
harmwhehe20:01
harmwI'm building all containers atm20:01
harmwwaiting for that to finish20:02
openstackgerritMerged stackforge/kolla: Fixes the last of the hacking based pep8 errors  https://review.openstack.org/20069020:02
harmwsdake_: you keep an eye on tagging all those for L2?20:02
harmwor can I do that as well?20:03
*** britthou_ has joined #kolla20:04
*** britthouser has quit IRC20:08
*** jruano has quit IRC20:13
*** bitblt has quit IRC20:14
bmaceone more review is up now and when it is merged i'll post the tox / test-requirement changes and we will be 100% pep8 compliant! :)20:16
*** prad has joined #kolla20:17
openstackgerritSwapnil Kulkarni proposed stackforge/kolla: Remove requirement for root user in scripts  https://review.openstack.org/20070220:17
*** prad has quit IRC20:19
coolsvapbmace, do we need requirement change for docker-py>=1.2.0 <=1.3.0?20:20
coolsvapi am not able to run kolla start unless i do this change20:21
coolsvapanyone else facing the similar issue20:21
harmwcoolsvap: I had something similar earlier today in my venv20:21
harmwafter fixing that I had to upgrade websockets (?) as well20:21
coolsvapharmw, yes20:22
bmacecoolsvap not sure.  my requirement change is just adding the hacking package to test-requirements.20:22
bmaceand it is test-requirements only20:22
coolsvapi think it will be a change20:23
coolsvapin requirements.txt20:23
bmacefor docker.py it would be, yes20:23
coolsvaphmm20:24
coolsvapharmw, do you have the log handy for the failure?20:27
harmwno, was at $work20:28
harmwpython errors20:28
coolsvaphmm, i wanted to create bug, will do that later sometime20:29
harmwI'm not sure if it is, realy20:29
harmwupgrading websockets doesn't feel like something we should fix20:29
openstackgerritSwapnil Kulkarni proposed stackforge/kolla: WIP: Update docker-py in requirement.txt  https://review.openstack.org/20070520:30
coolsvapharmw, but i think we will need to update docker-py20:30
*** britthou_ has quit IRC20:30
coolsvapcorrect?20:30
harmwdon't know, realy, since I didn't check what the actual issue was (apart from having to apply an update all of a sudden) since I didn't trust my python env either :)20:32
bmaceif it does need to be updated wouldn't it be >1.2.0,<=1.3.0  if your assumption is that 1.2.0 won't work20:33
sdake_coolsvap don't hard cap requirements pls20:34
openstackgerritSwapnil Kulkarni proposed stackforge/kolla: Remove requirement for root user in scripts  https://review.openstack.org/20070220:34
coolsvapsdake_, no i am not20:35
harmwcoolsvap: I think you missed my first comment on that bug :)20:35
sdake_[13:20:38]  <coolsvap>bmace, do we need requirement change for docker-py>=1.2.0 <=1.3.0?20:35
sdake_1.3.0 is a hard cap in this instanc20:35
sdake_hard caps are evil for a bunch of reasons20:35
coolsvapharmw, no, i did check the scripts with same user20:35
sdake_i am fine with exclusionis20:36
sdake_(when we know an upstream version is busted)20:36
sdake_did that cleanup-containers wor as nonroot20:36
coolsvapsdake_, yes20:36
sdake_i was curious about the release of the netns stuff20:36
sdake_release/clenaup20:36
harmwcoolsvap: then you misunderstood my comment, my question was to add in some logic to do (in a clever way) what the current check achieves20:37
harmw"since root can use docker, lets check if YOU are root!"20:37
harmw(and bail if you aren't)20:37
coolsvapharmw, sure i will add, i will put it wip20:37
harmwput workflow to -1 and when you're done put a new review up :)20:38
harmw(atleast thats what I would do)20:38
sdake_i think it is fine as is20:38
sdake_see comments in review20:38
sdake_we justneed to document how to add user to docerrott group20:38
sdake_or point at upstream docs on that20:38
sdake_having to run sudo for some commands and not others is annoying20:39
sdake_and the checking is different per distro and packaging20:39
*** coolsvap is now known as coolsvap|away20:39
sdake_some distros use dockerroot, some distro use the docker group20:39
harmwright, so mayhem will occur if $USER didn't read the docs...20:39
sdake_mayhem already occurs if user doesn't read the docs ;)20:40
sdake_trust me I always start out with "did you read the quickstart guide" :)20:40
harmwI didn't ask to check if $USER was in a specific group, just to check if docker was usable :)20:40
sdake_harmw that actually sounds good20:40
sdake_i'm not sure how you would do that docker ps perhaps20:40
harmwor docker info20:41
harmwI don't care, realy20:41
sdake_but lets do that as a seperate change if possible20:41
sdake_that way we can move on past the requireing orot20:41
harmwisn't that perfect for this changeset?20:41
sdake_harmw request a techdebt bug be filed in the bug20:41
sdake_and dont approve until it is :)20:41
harmwI'll file it this instant, way easier20:41
sdake_coolsvap has other higher priority things to work on I think20:41
sdake_like ansibllizing code base20:42
sdake_I asked him to fix this small probelm up in the meantime as I sort out our next work streams20:42
sdake_if coolsvap is good with doing the job now i'm ok with either approach ;)20:42
harmwfair enough20:42
harmwoh, he's away20:42
sdake_ya unfortunately he is afk20:42
sdake_so leave a comment in the bug as to how to proceed pls :)20:43
sdake_rather in the review20:43
harmwyea20:43
harmwyup20:43
sdake_thanks fine sir20:43
*** achanda has joined #kolla20:43
sdake_and i'll sort out oour next couple of weeks of work20:43
harmwack the init-runonce review pls :)20:43
harmwrhallisey: you to20:43
sdake_link harmw20:43
sdake_i usually do reviews in the morning unless they are blocking the code from working20:44
rhalliseyharmw, kk20:44
sdake_then ask for out of band acks20:44
harmwhttps://review.openstack.org/#/c/200655/20:44
harmwok sdake_ :)20:44
sdake_nice job harmw !20:45
sdake_I wanted to do that for like oh 3 months :)20:45
sdake_and never got around to it20:45
harmwsame here :)20:46
harmwuntil now20:46
*** sdake_ is now known as sdake20:46
sdakewish my client auto nick changed20:46
sdakei'll hav eto see if textual can do that20:46
rhalliseyso many things, so little tine O.o20:46
rhalliseynice harmw20:46
openstackgerritMerged stackforge/kolla: Properly wait for Openstack services to be ready  https://review.openstack.org/20065520:47
harmwcool!20:47
harmwthanks guys20:47
sdakei got some reviews which need attention too - the stream on cinder20:47
sdakeif folks could ack those or neg them20:47
sdakeso I can fix them20:47
sdakewould appreciate it20:47
bmacei have one more pep8 review, then i can do the commit for the actual pep8 enablement, if you want it today, if not i can finish it up monday.  https://review.openstack.org/#/c/200679/20:47
sdakedont ack the wip: tgt one yet20:47
harmwI never touch WIP's :)20:48
harmwunless explicitly asked20:48
sdakebmace will look - this is an example of a blocking reviwew harmw :)20:48
harmwI'm still building containers, damn20:48
harmweither my wifi sucks, or virtualbox does20:49
bmacei thought i saw something yesterday about the build time being super short now?20:49
sdakeare you using build.py -t rdo -T 1000?20:49
sdakeit taes me about 5 minutes to build there20:49
sdakebmace not yet20:49
harmwcrap, I should've done that sdake20:49
sdakebut there is a much faster builder tool20:49
bmaceyou sure you want the T 1000?  isn't that the liquid Terminator? :)20:49
sdakeand it seems reliable20:49
sdakebmace termination ftw ;)20:49
sdakesamyaple did a really nice job with the patch20:50
sdakeor the code rather20:50
sdakesince it wasn't really a patch :)20:50
harmwyea, I just totally forgot that script20:50
sdakethe plan is to remove the existing build once we get the new one into good woring order and can trust its results20:50
sdakeatm it seems like the command line around caching doesn't work for example20:50
sdakeharmw can you review the link in the scrollback from bmace20:53
sdakewe need this because the pep8 gate is soon to break ;)20:53
harmwI was saving that for sunday20:53
harmwactually :p20:53
bmaceputting in more pep8 breaking code harmw? ;)20:55
sdakeif someone could review this stream:20:56
sdakehttps://review.openstack.org/#/c/200693/120:56
sdakejpeeler or rhallisey - harmw has already reviewed20:56
harmwlol@https://review.openstack.org/#/c/200679/1/docker/centos/binary/neutron/neutron-base/ip_wrapper.py20:58
harmwgreat stuff :P20:58
bmaceyeah.  the hacking stuff added to pep8 gets pretty picky20:59
harmwI apparently like picky :>20:59
bmaceyeah, i really don't mind needing them to be alphabetized.20:59
bmaceespecially with larger import lists21:00
harmwit looks clean21:00
harmwless mess21:00
openstackgerritMerged stackforge/kolla: Fixed additional OpenStack pep8 issues  https://review.openstack.org/20067921:01
harmwthere you go21:01
-openstackstatus- NOTICE: Gerrit will be unavailable from 22:00 to 22:30 UTC for project renames21:01
bmaceawesome, now i'll put up the review to make it all official :)21:02
bmacesdake, still want the pep8 to run all those validate-contents tests until infra finished that other review?21:04
*** jtriley has quit IRC21:06
sdakebmace might as well21:09
sdakewhatever gets it done fastest without blociking the gate21:09
sdakeI dont want to do any emergency reverts because it annoys the infra tream :)21:09
bmaceyup, the only downside of checking in the final version of what we want to do would be that we wouldn't actually haver the validate-contents coverage until infra was done with their review21:10
sdakewell we do that in our repo right?21:10
bmaceif i commit both tests covering everything at some point we just need to yank the extra tests from our pep8 test21:10
bmaceyup21:10
sdakeif so, lets just do all the tests21:10
bmacekk21:11
sdakechanges in our repo are fast21:11
sdakeI can harass ppl to review and get em done in like 5-10 minutes during the work week typically21:11
sdakeI am more concerned about having long review cycles on the infra side21:11
sdakebmace btw the reason infra has not reviewed your patch is because this is rename week21:11
sdakewhen projects go from stackforge to openstack21:11
bmaceah, extra chaos21:12
sdakeits a super super busy time for them21:12
*** dwalsh has quit IRC21:12
bmaceok, review up shortly21:12
sdakeit requires all their attention to not fuck up the system ;)21:12
bmacebtw, found out that PyYAML wasn't needed as a dependency for those validate tests21:12
sdakeok so we need to revert a change then?21:12
sdakeor new patch?21:13
bmacenope.. again, just in our tree, it is part of my review going up soon21:13
sdakesounds good21:13
*** achanda has quit IRC21:14
openstackgerritBorneMace proposed stackforge/kolla: Enable pep8 tests  https://review.openstack.org/20072921:15
sdakeare ou sure about that line 38 change21:16
sdakecould you explain why you did that?21:16
bmacethe yank of test-requirements from images?21:16
sdakeyes21:16
bmaceit was added in base testenv21:16
sdakeok21:16
bmaceso it is available for all the tests21:16
sdakegot it21:16
bmaceso once that infra stuff is done we just yank the blah/tools/*.sh from testenv:pep8 and we are done.21:18
bmacebut those tests are fast anyway.  isn't super painful to have them in both places21:18
sdakewhat is the deal with this?21:19
sdakehttp://logs.openstack.org/98/200298/3/check/check-kolla-functional-f21/812e876/console.html21:19
sdakebmace ya just makes tracking down the problem harder21:19
sdakeeach of those should really be a separate gatei mo :)21:20
*** Slower has quit IRC21:21
bmacesdake hrm.. not sure.  i didn't get that in my environment21:21
* sdake really wants check-kolla-functioanl-f21 to start being more reliable not less reliable ;(21:22
bmacelet me see if i can find out what is going on21:22
*** sdake_ has joined #kolla21:24
bmacelooks like something mock is using, but i don't think i did anything that should have effected that.  i only added the hacking to test-requirement and if it was some sort of issue at that level i would have expected to see it on my system too :/21:24
openstackgerritMerged stackforge/kolla: Change permissions on cinder config-internal/external  https://review.openstack.org/20005521:24
openstackgerritMerged stackforge/kolla: Add oslo.reports as a global dependency  https://review.openstack.org/20029821:24
sdake_bmace yes it wasn'tdirected at you21:24
sdake_just a general question for people to help sort out :)21:24
sdake_bmace i'm pretty ssure something broke in the gate around that code21:25
sdake_jpeeler you should take a look too if you can21:25
bmacesdake_ i gotcha.  i know that the requirements can be really touchy about ordering21:25
sdake_there shouldn't be touchiness around ordering21:25
sdake_i personally haven't experienced that21:25
bmacea lot of other projects specifically mention in their requirements / test-requirements that the order should be left as is since issues can happen if it isn't :/21:26
sdake_what good is an installation system (pip) if its not deterministic21:26
*** achanda has joined #kolla21:26
sdake_bmace i still haven't experienced that21:26
bmacei don't disagree :)21:26
sdake_I know it says it across many projects, but i ordered them asci-betically and it had no impact21:27
sdake_other then being properly sorted ;)21:27
*** sdake has quit IRC21:27
harmwoh my, /me just created a linked profile :/21:29
sdake_your famous now ! :)21:34
sdake_btw harmw how old areoyu if i can ask :)21:34
harmw29 :)21:34
sdake_nice i remembe r2921:34
harmwhehe21:34
sdake_i felt so much better back then21:34
sdake_41 here21:34
rhalliseywoo still the youngest21:34
harmw29 and kid #3 on his way :p21:34
sdake_you now they make operations and pills to prevent that harmw :)21:35
harmwyep21:35
sdake_both of our chidren came on birth control21:35
sdake_yay for birth control21:35
harmwinteresting21:35
sdake_not that my kids dont rock21:35
sdake_i'm glad we had em when we did21:36
sdake_or we may never have21:36
bmacethey would not be stopped! :)21:36
harmw:)21:36
*** rhallisey has quit IRC21:37
bmacelast review request of the day if someone other than sdake could look at https://review.openstack.org/#/c/200729/   otherwise if someone sneaks in pep8 breaking changes before it goes in the gate might start failing :/21:37
jpeelersdake_: adding funcsigs to test-requirements.txt should fix it, i don't understand why pip isn't doing the job21:39
jpeelerhttps://github.com/testing-cabal/mock/blob/master/requirements.txt21:40
jpeelerit's listed there21:40
jpeelerthis comment does not inspire confidence: https://github.com/testing-cabal/mock/blob/master/mock/mock.py#L8521:41
harmwright, so, after filling in countless crappy forms I can finally invite $world to my linkedin profile21:50
harmwjeez21:50
harmwthe hassle21:50
*** achanda has quit IRC21:50
sdake_jpeeler loll21:52
sdake_thats a good one ;)21:52
sdake_"import funcsigs" ?Has this been fixed?21:53
*** achanda has joined #kolla21:54
-openstackstatus- NOTICE: Gerrit is unavailable from approximately 22:00 to 22:30 UTC for project renames21:56
*** ChanServ changes topic to "Gerrit is unavailable from approximately 22:00 to 22:30 UTC for project renames"21:56
jpeelerbmace: is it not the python way to keep separate dependency lists?21:57
*** vinkman has joined #kolla21:58
jpeeleri guess it's easier to maintain, but installing a bunch of clients in the pep8 virtual env seems weird to me21:58
bmacemost of the other projects i had looked at for sort of "standards" guidance had the requirements / test-requirements right in testenv like that21:59
jpeeleryeah, both nova and glance do it your way (but neutron does it my way)22:03
jpeelerwon't make a big deal out of it though22:03
jpeelerwell gerrit just went down, so i can't approve it22:03
jpeelershould have translated 22:00 UTC before i started looking around22:04
bmacejpeeler btw, i added your name into a couple of TODOs when doing my pep8 fixes earlier, based on the git blame line saying you were the last one to touch it, hopefully that was true :)22:07
jpeelergit is lying!22:07
bmacelol22:08
*** Slower has joined #kolla22:10
*** sdake has joined #kolla22:11
*** sdake_ has quit IRC22:14
*** britthouser has joined #kolla22:19
bmaceseems like it is alive again?22:29
*** ChanServ changes topic to "Please register for the the Kolla-Palooza midcycle July 28th, July 29th @ https://www.eventbrite.com/e/kolla-palooza-midcycle-event-tickets-17628669826 - Channel is Logged @ http://eavesdrop.openstack.org/irclogs/%23kolla/"22:29
bmaceand ChanServ agrees ;)22:31
*** diogogmt has quit IRC23:00
*** diogogmt has joined #kolla23:01
*** diogogmt has quit IRC23:02
*** jruano has joined #kolla23:04
*** britthouser has quit IRC23:08
vinkmanSo, for the config-external bits, I think we are missing a hook in there for people to setup pieces that would be required by their specific config, for example if someone wants to have  oslo lock dir somewhere sane, they would need to be able to do the mkdir -p and chown etc.23:11
*** dims has quit IRC23:13
*** dims has joined #kolla23:17
*** openstackgerrit has quit IRC23:39
*** openstackgerrit has joined #kolla23:39
*** jruano has quit IRC23:42
bmacegotta run guys, try to get that pep8 review in or else we might end up with gate issues if other breaking changes get in first :/23:52
bmacethanks much jpeeler :)23:55
openstackgerritMerged stackforge/kolla: Enable pep8 tests  https://review.openstack.org/20072923:55
jpeelernp23:55
bmacewell, now that is done, weekend time! have a great one all23:55

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