Monday, 2016-05-02

*** banix has joined #openstack-kolla00:01
*** betheynyx has joined #openstack-kolla00:08
*** salv-orlando has joined #openstack-kolla00:12
*** sdake has quit IRC00:15
*** ravig has joined #openstack-kolla00:16
*** salv-orlando has quit IRC00:17
*** rstarmer_ has quit IRC00:19
*** daneyon has joined #openstack-kolla00:21
*** rstarmer has joined #openstack-kolla00:29
*** thumpba has quit IRC00:30
*** sdake has joined #openstack-kolla00:32
*** daneyon_ has joined #openstack-kolla00:39
*** sdake_ has joined #openstack-kolla00:42
*** daneyon has quit IRC00:42
*** sdake has quit IRC00:44
*** daneyon_ has quit IRC00:44
*** jasonsb has joined #openstack-kolla00:49
*** jasonsb has quit IRC00:54
*** rstarmer has quit IRC01:03
*** rstarmer has joined #openstack-kolla01:03
*** salv-orlando has joined #openstack-kolla01:13
*** salv-orlando has quit IRC01:18
*** rstarmer has quit IRC01:18
*** rstarmer has joined #openstack-kolla01:19
*** inc0 has joined #openstack-kolla01:27
*** ravig has quit IRC01:30
*** ravig has joined #openstack-kolla01:31
*** rstarmer_ has joined #openstack-kolla01:33
*** rstarmer has quit IRC01:33
*** ravig has quit IRC01:40
*** banix has quit IRC01:45
*** mdnadeem has quit IRC01:46
*** mdnadeem_ has joined #openstack-kolla01:48
*** ravig has joined #openstack-kolla01:48
*** rstarmer has joined #openstack-kolla01:48
*** rstarmer_ has quit IRC01:50
*** banix has joined #openstack-kolla01:50
*** rstarmer has quit IRC01:59
sbezverksdake ping02:03
*** ravig has quit IRC02:10
*** salv-orlando has joined #openstack-kolla02:14
*** salv-orlando has quit IRC02:19
*** ravig has joined #openstack-kolla02:19
*** ravig has quit IRC02:29
*** ravig has joined #openstack-kolla02:30
*** inc0_ has joined #openstack-kolla02:45
*** inc0 has quit IRC02:49
*** jasonsb has joined #openstack-kolla02:51
*** jasonsb has quit IRC02:55
*** klint has joined #openstack-kolla02:56
*** coolsvap has joined #openstack-kolla02:59
*** rstarmer has joined #openstack-kolla03:01
*** rstarmer has quit IRC03:05
*** mdnadeem has joined #openstack-kolla03:07
*** mdnadeem_ has quit IRC03:10
*** inc0__ has joined #openstack-kolla03:11
*** betheynyx has quit IRC03:11
*** rstarmer has joined #openstack-kolla03:12
*** inc0_ has quit IRC03:14
*** salv-orlando has joined #openstack-kolla03:15
*** salv-orlando has quit IRC03:19
*** daneyon has joined #openstack-kolla03:22
*** daneyon has quit IRC03:27
*** inc0__ has quit IRC03:28
*** jpeeler has joined #openstack-kolla03:44
*** jpeeler has joined #openstack-kolla03:44
*** dave-mccowan has quit IRC04:01
sbezverksdake if you get this message, check this bug I hit, it applies to both master and stable/mitaka: https://bugs.launchpad.net/kolla/+bug/157727304:03
openstackLaunchpad bug 1577273 in kolla "Failure of creating haproxy mysql user" [Undecided,New] - Assigned to Serguei Bezverkhi (sbezverk)04:03
*** salv-orlando has joined #openstack-kolla04:16
*** salv-orlando has quit IRC04:20
*** rstarmer has quit IRC04:22
*** ravig has quit IRC04:32
sdake_evening04:45
sdake_sbezverk i think my fix for removing kazoo should fix  that sbezverk - could you try it?04:46
*** manjeets has quit IRC04:47
*** manjeets has joined #openstack-kolla04:48
*** unicell has joined #openstack-kolla04:50
*** banix has quit IRC05:02
*** rstarmer has joined #openstack-kolla05:12
*** salv-orlando has joined #openstack-kolla05:16
*** rstarmer has quit IRC05:19
*** salv-orlando has quit IRC05:21
*** ssurana has joined #openstack-kolla05:21
*** daneyon has joined #openstack-kolla05:22
*** betheynyx has joined #openstack-kolla05:32
*** reddydodda has joined #openstack-kolla05:33
*** sdake_ has quit IRC05:47
*** Mr_Broken has joined #openstack-kolla05:48
*** sdake has joined #openstack-kolla05:52
*** jasonsb has joined #openstack-kolla05:53
*** ccesario_ has quit IRC05:55
*** ccesario_ has joined #openstack-kolla05:55
*** jasonsb has quit IRC05:58
*** salv-orlando has joined #openstack-kolla05:58
*** coolsvap has quit IRC06:26
*** coolsvap has joined #openstack-kolla06:30
*** mdnadeem_ has joined #openstack-kolla06:33
*** mdnadeem has quit IRC06:37
*** mdnadeem has joined #openstack-kolla06:41
*** mdnadeem_ has quit IRC06:43
*** fragatina has joined #openstack-kolla07:08
*** ssurana has quit IRC07:15
*** daneyon_ has joined #openstack-kolla07:19
*** daneyon has quit IRC07:22
*** salv-orlando has quit IRC07:28
*** fragatina has quit IRC07:46
*** rstarmer has joined #openstack-kolla07:58
*** dmk0202 has joined #openstack-kolla08:06
*** rstarmer has quit IRC08:13
*** gfidente has joined #openstack-kolla09:01
*** reddydodda has quit IRC09:37
*** fragatina has joined #openstack-kolla09:46
*** pbourke has quit IRC09:51
*** pbourke has joined #openstack-kolla09:51
*** fragatina has quit IRC09:52
*** reddydodda has joined #openstack-kolla09:53
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Exclude the docker registry image from cleanup-images  https://review.openstack.org/31067709:59
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Exclude the docker registry image from cleanup-images  https://review.openstack.org/31067710:02
*** ccesario_ has quit IRC10:16
*** betheynyx has quit IRC10:23
*** betheynyx_ has joined #openstack-kolla10:25
*** Serlex has joined #openstack-kolla10:28
*** coolsvap has quit IRC10:29
*** coolsvap has joined #openstack-kolla10:30
*** daneyon has joined #openstack-kolla10:35
*** Guest68119 has quit IRC10:37
*** zeus- has joined #openstack-kolla10:38
*** daneyon has quit IRC10:40
*** reddydodda has quit IRC10:42
*** fragatina has joined #openstack-kolla10:49
*** allen_gao has quit IRC10:49
*** Mr_Broken has quit IRC10:52
*** Mr_Broken has joined #openstack-kolla10:53
*** fragatina has quit IRC10:53
*** Mr_Broke_ has joined #openstack-kolla10:53
*** allen_gao has joined #openstack-kolla10:54
*** ccesario___ has joined #openstack-kolla10:54
*** rhallisey has joined #openstack-kolla10:54
*** Mr_Broken has quit IRC10:57
*** jasonsb has joined #openstack-kolla10:57
*** zeus- is now known as zeus10:58
*** zeus is now known as Guest2591510:59
*** ccesario___ has quit IRC10:59
nihilifersdake: let me know when you'll awake10:59
*** ccesario___ has joined #openstack-kolla10:59
*** jasonsb has quit IRC11:02
*** ccesario has joined #openstack-kolla11:07
*** reddydodda has joined #openstack-kolla11:19
openstackgerritCarlos Cesario proposed openstack/kolla: Fix radosgw 'rgw frontends' param  https://review.openstack.org/31122211:32
*** thumpba has joined #openstack-kolla11:33
*** thumpba has quit IRC11:34
*** thumpba has joined #openstack-kolla11:43
openstackgerritMauricio Lima proposed openstack/kolla: Remove unecessary blank lines  https://review.openstack.org/31119911:44
*** coolsvap has quit IRC11:56
*** athomas_ has joined #openstack-kolla12:12
*** mlima has joined #openstack-kolla12:15
*** Mr_Broke_ has quit IRC12:16
*** Mr_Broken has joined #openstack-kolla12:17
*** Mr_Broken has quit IRC12:21
*** daneyon has joined #openstack-kolla12:24
*** Mr_Broken has joined #openstack-kolla12:26
*** daneyon has quit IRC12:28
*** mbound has joined #openstack-kolla12:30
openstackgerritMichal Rostecki proposed openstack/kolla: [WIP] Exclude the docker registry image from cleanup-images  https://review.openstack.org/31067712:37
*** reddydodda has quit IRC12:46
*** athomas_ has quit IRC12:49
*** diogogmt has quit IRC12:52
*** dave-mccowan has joined #openstack-kolla12:53
*** diogogmt has joined #openstack-kolla12:57
*** jasonsb has joined #openstack-kolla13:00
*** sdake has quit IRC13:00
*** reddydodda has joined #openstack-kolla13:00
*** sdake has joined #openstack-kolla13:01
*** jtriley has joined #openstack-kolla13:02
*** klint has quit IRC13:02
*** sdake_ has joined #openstack-kolla13:04
*** jasonsb has quit IRC13:05
*** sdake has quit IRC13:06
*** thumpba has quit IRC13:10
*** thumpba has joined #openstack-kolla13:10
openstackgerritSteven Dake proposed openstack/kolla: Remove dependencies on kazoo and friends  https://review.openstack.org/31163213:13
*** thumpba has quit IRC13:15
sdake_pbourke around?13:16
*** thumpba has joined #openstack-kolla13:19
openstackgerritRyan Hallisey proposed openstack/kolla: Spec: Deploy Kolla images using Kubernetes  https://review.openstack.org/30418213:21
*** banix has joined #openstack-kolla13:23
*** thumpba has quit IRC13:23
openstackgerritRyan Hallisey proposed openstack/kolla: Spec: Deploy Kolla images using Kubernetes  https://review.openstack.org/30418213:25
*** thumpba_ has joined #openstack-kolla13:26
nihilifersdake_: around?13:32
sdake_sup dude13:32
openstackgerritMerged openstack/kolla: Remove the eth1 up and down manually in the rax-ord node  https://review.openstack.org/31063613:36
*** rmart04 has joined #openstack-kolla13:38
openstackgerritMerged openstack/kolla: Use a random virtual_router_id in the keepalived  https://review.openstack.org/30408013:42
*** dmsimard|afk is now known as dmsimard13:49
*** JoseMello has joined #openstack-kolla13:50
*** Guest25915 is now known as zeus`13:54
*** dwalsh has joined #openstack-kolla13:54
*** inc0 has joined #openstack-kolla13:58
*** fragatina has joined #openstack-kolla13:59
*** ravig has joined #openstack-kolla13:59
*** diogogmt has quit IRC14:03
*** fragatina has quit IRC14:03
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Addining ability to specify capabilities and security  https://review.openstack.org/30844714:04
inc0o/14:06
*** sdake_ is now known as sdake14:11
*** rmart04 has quit IRC14:12
*** rmart04 has joined #openstack-kolla14:12
*** rmart04 has quit IRC14:13
sdakecan i get another core reviewer to ack https://review.openstack.org/#/c/290238/914:17
patchbotsdake: patch 290238 - kolla - Handle multi Ethernets case in the gate14:17
sdakehey inc014:17
sdakehey sbezverk14:17
sdakehey all :)14:17
sbezverkhey sdake14:18
sdakeif your a core reviewer please vote on the general "lets get rolling on k8s"14:19
sdakebtw, if we do have a split repo, it will have to be named kolla-k8s becuase kolla-kubernetes wont work in pypi for some reaon14:20
inc0kolla-k8s is good14:20
sdakeeither someone registered it already (my guess) or kubernetes is not allowed or its too long who knows ;)14:20
sdakei like andreas's approach though -  fit filter allows us to split anythign later down the road14:20
sdakeand maintain all history14:20
sdakebut anyway vote on the lets get the ball rollign on k8s, then we can sort out the repo14:20
sdakeso far it looks split pretty even14:21
inc0ehh, I'd rather have first split then merged, we can make history wirks14:21
sbezverksdake I could not test your patch yet as I have a presentation at noon my time.. I made deployment working by little hack.14:21
sdakeandreas is an expert in git14:21
sdakeget him to say thato n the mailign list :)14:21
inc0my point is, we can do both with history14:21
sdakesbezverk which patch14:21
sdakei disagree, a split then merge would lose history14:21
sbezverksdake you mentioned kazoo14:21
sdakesbezverk oh that - ya that works14:22
sdakei tested it ;)14:22
sdakeneed a rubber stamp on https://review.openstack.org/#/c/290238/9 plz14:22
patchbotsdake: patch 290238 - kolla - Handle multi Ethernets case in the gate14:22
sbezverksdake so you saw the same issue right?14:22
sdakethe gate is seriously busted - if this doesn't fix it we can fix it some othe rway14:22
sdakesbezverk which issue14:22
inc0sdake, http://stackoverflow.com/questions/13040958/merge-two-git-repositories-without-breaking-file-history14:23
sdakebrain fry - going to have to give me somethign to work with :)14:23
sdakeinc0 if you read that full thraed, the essence is "yes you can merge repos but lose history"14:24
sbezverksdake https://bugs.launchpad.net/kolla/+bug/157727314:24
openstackLaunchpad bug 1577273 in kolla "Failure of creating haproxy mysql user" [Critical,New] - Assigned to Serguei Bezverkhi (sbezverk)14:24
sdakelook at the footnotes14:24
sdakesbezverk oh - ya it is speculatory if my fix fixes that problem14:24
sdakewhich demo are you giving if you dont mind me asking, nfvi?14:25
inc0sdake, I'll try it locally14:25
sbezverksdake yes nfv vt14:25
sdakebot hdims and ajeager have said its irreversible in private conversations14:25
sdakeanyway up to the community to decide :)14:26
sdakeatm vote is equal but many folks are unrepresented14:26
inc0first I personally don't want bunch of cores in kolla (that I don't know)14:26
sdakeinc0 that wont be the case14:26
inc0second I don't want people to think k8s is ready14:26
sdakethe new folks will go in kolla-k8s-core14:26
rhalliseysdake, ya but they = kolla core14:26
inc0if they checkout kolla, everything there works14:27
sdakeand be promoted to kolla-core as they show interest in the general repo14:27
sdakerhallisey this is where  training and lecturing come in :)14:27
inc0I think we need more than interest14:27
rhalliseythere's no difference between kolla-k8-core and kolla-core14:27
sdakethey also do not have policy voting rights14:27
sdakethat is the difference14:27
inc0every core should have equal chances/requirements to join the eam14:27
rhalliseyhow they not have policy voting rights?14:27
rhalliseythey belong to the kolla repo14:28
sdakethey may not commit to any directory other then kubernetes14:28
sdake*ONLY* people in kolla-core have policy voting rights14:28
*** thumpba_ has quit IRC14:28
*** Mr_Broken has quit IRC14:28
sdakejust as it was with kolla-k8s-core14:28
sdakerather kolla-mesos-core14:28
inc0sdake, this will be trust-based and I'm 100% sure someone will break it, even if untintentionally14:28
rhalliseyexcept that was a differnt repo14:28
openstackgerritMerged openstack/kolla: Handle multi Ethernets case in the gate  https://review.openstack.org/29023814:28
sdakeif they do unintentionally their change will be reverted14:28
*** thumpba has joined #openstack-kolla14:29
*** Mr_Broken has joined #openstack-kolla14:29
inc0also major raise on core team will make people think that we're less stabke14:29
inc0I would...14:29
sdakeif they do so intentionallly and it becomes a pattern they will be kicked from the kolla-k8s-core reviewer team14:29
rhalliseyI'd rather let that community manage itself until it's ready14:29
inc0we did kolla-mesos, we should follow pattern in kolla0k8s14:29
sdakethey are added to a separate group14:29
sdakeyes but that pattern was flawed14:29
inc0also it will be hell to figure out who does reviews on main repo14:30
sdakewhat i'd like to see is people from kolla-mesos chime in on what they think went wrong/right14:30
inc0so we can actually promote them for core status14:30
sdakeno, there are two seprate acl groups in gerrit14:30
inc0sdake, kolla-mesos Angus and Michal did14:30
sdakepromotion is easy14:30
sdakeangus got promoted14:30
inc0yes, once he earned it14:30
sdakethere was another dude in kolla-mesos-core that was never promoted14:30
sdakeagree he earned it14:30
inc0granted, for Angus we give him a bit of a slack, but because both you and me and few others knows him14:31
sdakei am promoting same model here14:31
rhalliseyI don't think it's the same14:31
inc0let's wait for vote to finish, so far split of repos wins14:31
inc0but let's wait for other cores to chime in14:32
inc0also I honestly think that having k8s in main repo will make people deploy it and potentially hurt14:33
inc0and in case k8s fails, which it might (I hope not, but well), it would make it harder to remove14:33
sdakeso far its equal in my count :)14:33
rhalliseyI think it's catastrophic in the main repo.  All so we don't potentially lose some git histy14:33
*** Mr_Broken has quit IRC14:33
sdakeinc0 i raised that with  a warning in the tool14:33
sdakethat isn't the main reason14:33
sdakethe main reason is to have one integrated solution14:34
sdakewtb kolla-mesos reviewers to chime in14:34
rhalliseyok, so what about other projects?14:34
inc0now with nihilifer vote is 3v2 for separate repo14:34
sdakenihilifer can you weigh in plz14:34
inc0few minutes ago was 3v114:34
*** salv-orlando has joined #openstack-kolla14:34
rhalliseywe can't integrate every project into kolla14:34
sdakerhallisey agree, but we aren't talking about future proofing this14:35
rhalliseythis is the first class argument all over again14:35
sdakethis is for one case14:35
sdakeyes i want k8s to be first class14:35
inc0sdake, we all do..when it's ready14:35
sdakebritt, sdake, nihilifer = 314:35
rhalliseywhat about tripleo/chef/puppet14:35
inc0britt is not a core14:35
rhalliseythey all get denoted to 2nd class14:35
inc0also dims voted for separate repo if non-cores also vote14:36
sdakebritt was on the list of people invited to vote because he was interested in participated14:36
sdakeok 4/3 then ;)14:36
inc0so did dims14:36
rhalliseyplus this vote is not a merge now and vote to split later14:36
*** v1k0d3n has joined #openstack-kolla14:36
rhalliseyyour talking about merging the tools14:36
sdakeeveryone on that list has a say14:36
sdakewhat we do later is a separate and orthogonal discussion14:36
sdakevikram iirc was in favor of same repo14:37
sdake4/4 :)14:37
sdakeequal14:37
nihiliferbut what's the problem with having all the things (even tripleo/puppet/chef) in one repo? i see no real problem to solve. things like "it's better to keep ecosystems in separate repo" are no problems for me14:37
Lyncospython-memcache package is missing in Cinder and glance ubuntu containers.....14:37
*** mag009_ has joined #openstack-kolla14:37
Lyncosis this adressed somewhere ?14:37
nihiliferon the other hand, we indeed had technical problems when we separated kolla-mesos14:37
sdakeLyncos probably not, ubuntu binary needs some love - could you file a bug14:37
mag009_mornin all14:37
sdakehey mag :)14:37
sdakewelcome to the party14:37
Lyncossdake will file a bug14:37
rhalliseynihilifer, that's not the problem. The problem is that all the things won't be willing to join the main repo14:37
*** ravig has quit IRC14:38
sdakeLyncos thanks14:38
rhalliseyand since they arn't willing the get demoted14:38
sdakeand ify ou want ot fix it we will take tha t too ;)14:38
inc0nihilifer, idea is to merge repos when k8s becomes stable14:38
inc0one idea at least14:38
nihiliferrhallisey: how we can know whether all the things will will to join the main repo if they don't exist yet?14:38
inc0problem with one repo is that it will be hell to manage with first commits14:38
inc0these have to be fast paced14:38
sdakeinc0 little faith goes a long long way :)14:39
nihiliferinc0: yea, so in the first months we will begin development with copied files, copied code and with technical debt14:39
sdakeok its day 1 of th evote14:39
nihiliferand then "solve it"14:39
sdakelets not argue it into death14:39
sdakeuntil we have wide community weighin14:39
v1k0d3nhey guys. morning.14:39
sdakenihilifer right on dude i agree14:39
sdakehey v1k0d3n14:39
rhalliseynihilifer, tripleo has a stable repo and community.  Their case is to consume.  Chef was a similar scenario14:39
nihilifer"later solving" rarely happens, just saying14:40
sdaketbh i dont know if chef will consume or not14:40
inc0sdake, it might be my polish untrusting soul of an eastern european, but I want people to earn our trust before deciding about future of our project14:40
sdakeits unclear what tripleo's plan is :)14:40
sdakethey decide the future of k8s directory ONLY14:40
v1k0d3nwanted to get back into kolla, and check it out. seems like i keep running into issues. does anyone have a few minutes to direct message for a bit, so i can make sure i'm reading through docs correcty?14:40
sdakeand possibly tests directory14:40
sdakev1k0d3n i'm here for you bro if you throw me some vikoden :)14:40
* sdake needs some anestaphine from the medlock14:41
v1k0d3nrhallisey: maybe you would be best, since i'm joining the party since i'm going to get involved with the kolla-k8s portion.14:41
v1k0d3nlol sorry sdake i'm all out. :)14:41
rhalliseyv1k0d3n, oh hey!14:41
v1k0d3ngotta love those aggressive gamertag handles. :)14:41
sdakev1k0d3n its a-ok i was just jking :)14:41
rhalliseyv1k0d3n, sure14:42
inc0v1k0d3n, issue is - we want to start working on kolla-k8s14:42
Lyncossdake I submitted the bug  :-) now have to figure out how to submit a patch14:42
inc0but discussion is about whether we make dir in main kolla tree or separate kolla-k8s repo14:42
sdakeLyncos moment i have a link for you14:43
LyncosOk thanks14:43
sdakeLyncos http://docs.openstack.org/infra/manual/developers.html14:44
sdakeneed thorough review of https://review.openstack.org/#/c/311632/414:45
patchbotsdake: patch 311632 - kolla - Remove dependencies on kazoo and friends14:45
v1k0d3ninc0: agreed...me too, definitely.14:45
inc0please, put a mail into openstack-dev then14:45
inc0that's how we vote14:46
sdakev1k0d3n yo uhavce an action on the ml - all people that were interested were asked to vote whether they want split repo or unified repo14:46
sdakeplease read the entire thread before making your choice14:46
sdakeiirc your name was on the list of poeple interested14:47
sdakebtw, i got my office half assembled ;)14:48
sdakemy lab mahcines are still not hooked up14:48
sdakewhich iw ill do today14:48
sdakethen i'll have 10gig multinode rolling yay :)14:48
sdakerhallisey would you mind atleast voting +1 on the proposal to actually do kolla k8s support ;)14:49
rhalliseyI'm +1.  I wouldn't vote against my own spec14:50
*** MarMat has joined #openstack-kolla14:50
*** ayoung has joined #openstack-kolla14:50
*** salv-orlando has quit IRC14:53
sdakerhallisey cool can you put that on the ml ;)14:55
sdakebecause as it stands now you sort of look -1 ;)14:55
sdakejust put the caveat in that you prefer a split repo but your +1 for the idea of k8s dev14:56
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Addining ability to specify capabilities and security  https://review.openstack.org/30844714:56
*** thumpba has quit IRC14:59
sdakehey folks i just spoke with infra, we can have two groups, one with +2 ability but kolla-core would retain +w rights on the repo15:00
*** dwalsh has quit IRC15:01
inc0sdake, but according to your proposal k8s will be *in* our repo15:01
inc0so either there will be no k8s specific cores or kolla will have lot's of cores15:02
sdakeno, there will be a kolla-k8s-core group15:04
*** ravig has joined #openstack-kolla15:04
sdakethese people can +2 patches, but not workfow them is one option15:04
sdakeor +2 and +w patches15:04
sdakeremember git revert is an easy solution to bad actors :)15:05
*** mlima has quit IRC15:05
inc0not so easy if there would be lots of reverts15:05
sdakedont let paranoia rule :)15:05
sdakewe will have training session :)15:05
*** daneyon has joined #openstack-kolla15:06
sdakethe core team knows who the core team is15:06
sdakeanyone know which tz mlima is in15:06
*** |GonZo2000| has joined #openstack-kolla15:10
*** daneyon has quit IRC15:10
*** severion has joined #openstack-kolla15:12
*** thumpba has joined #openstack-kolla15:12
nihiliferidea of having only +2 sounds good for kolla-k8s-core15:13
*** dwalsh has joined #openstack-kolla15:14
*** diogogmt has joined #openstack-kolla15:15
*** cfarquhar has joined #openstack-kolla15:18
*** cfarquhar has joined #openstack-kolla15:18
*** harmw_ has joined #openstack-kolla15:18
ccesarioafternoon guys :)15:19
ccesariosdake, GMT -03:00  or -02:0015:20
*** mlima has joined #openstack-kolla15:20
*** betheynyx has joined #openstack-kolla15:21
*** betheynyx_ has quit IRC15:21
*** GonZo2000 has quit IRC15:21
*** harmw has quit IRC15:21
*** v1k0d3n has quit IRC15:21
*** harmw has joined #openstack-kolla15:21
*** cfarquhar_ has quit IRC15:21
*** jrist has quit IRC15:21
*** harmw has quit IRC15:21
*** ravig has quit IRC15:21
mlimasdake, ?15:23
openstackgerritTravis McPeak proposed openstack/kolla: Adding a few #nosec tags to prepare for Bandit usage  https://review.openstack.org/31086915:31
openstackgerritStephane Boisvert proposed openstack/kolla: Closes-Bug: 1577422  https://review.openstack.org/31176515:33
openstackbug 1577422 in kolla "python-memcache is missing from cinder and glance containers" [Undecided,New] https://launchpad.net/bugs/157742215:33
*** fragatina has joined #openstack-kolla15:34
*** ravig has joined #openstack-kolla15:36
*** salv-orlando has joined #openstack-kolla15:36
timssmaybe I misunderstood something, but regarding preserving git history, maybe this is of interest? http://stackoverflow.com/questions/1365541/how-to-move-files-from-one-git-repo-to-another-not-a-clone-preserving-history/11426261#1142626115:37
*** jrist has joined #openstack-kolla15:37
timssit can be pretty cool (unless there are lots of conflicts)15:38
*** thumpba_ has joined #openstack-kolla15:40
inc0timss, no conflicts ever as it will be separate directory15:40
timsssure, I was just talking in general for that approach15:41
rhalliseytimss, neat15:41
Lyncossdake: I did submit my patch... can you just please confirm that I did it the right way ?15:41
sdakeLyncos link?15:41
timsshttps://github.com/vimperator/vimperator.vim/commits/master15:41
timssexample where I used it15:41
Lyncos  https://review.openstack.org/31176515:41
*** fragatina has quit IRC15:41
*** thumpba has quit IRC15:41
inc0Lyncos, you need commit message;)15:42
Lyncos damn15:42
inc0a title and some short desc15:42
*** fragatina has joined #openstack-kolla15:42
inc0also tag is Closes-Bug: #xxx15:42
inc0you forgot #15:42
Lyncosok I'll try to figure out how to change my commit :-)15:42
inc0this will make your bug in launchpad turn into inprog automagically15:42
inc0Lyncos, git commit --amend15:42
inc0if we'd ask you to change something in files, git commit --amend as well15:43
inc0git add files_changed, git commit --amend15:43
sdakeLyncos your commit message is wrong but otherwise looks good :)15:43
LyncosOk fixing this15:44
sdakeLyncos serguei has a question int he bug tracker15:44
sdakei have same question15:44
sdakehttps://bugs.launchpad.net/kolla/+bug/157742215:44
openstackLaunchpad bug 1577422 in kolla "python-memcache is missing from cinder and glance containers" [Undecided,New]15:44
sdakeLyncos what is your launchpad id plz15:45
LyncosLaunchpad Id:15:45
Lyncosstephane-boisvert15:45
*** haplo37 has joined #openstack-kolla15:47
LyncosI think my comment is better now15:50
Lyncosalso answered your questions15:50
*** rstarmer has joined #openstack-kolla15:51
*** mbound has quit IRC15:52
*** rstarmer has quit IRC15:55
*** rstarmer has joined #openstack-kolla15:56
dimssdake : inc0 : rhallisey : multiple groups on same repo gets too complicated (esp so many new folks!). i assumed that eventually we'll have a base repo (may be even publish code to pypi) and ansible/ kubernetes/ would consume that deliverable and do things specific to their environments.15:56
*** ozialien10 has joined #openstack-kolla15:58
jpeelerso basically, you're saying a separate repo to maintain access permissions makes sense?15:58
*** dmk0202 has quit IRC15:59
dimsjpeeler : my opinion. yes15:59
*** JoseMello has quit IRC15:59
sdakeso acls are one thing15:59
sdakebut we can enforce acl's via a social contract15:59
sdakei am thinking back to kolla-mesos and some of the reasons that failed15:59
sdakeand it had alot to do with nihilfer's email15:59
dimsjpeeler : though i think that once we hit the deadline that sdake mentioned (july 15?) then we should have one single group16:00
sdakethere were basically two camps16:00
sdakedeadline pulled out of ass btw :)16:00
dims:)16:00
sdakejust a proposal to get poeple thinking16:00
sdakemesos folsk reviewed kolal repo16:00
sdakekolla core didn't review mesos code base16:01
*** rstarmer has quit IRC16:01
sdakewhich i found disturbing and not what i thought would make the projects successful16:01
sdakeLyncos your patch doesn't need to do that work for centos16:01
sdakeits an ubuntu binary only problem16:01
*** unicell has quit IRC16:01
Lyncosyeah I just figured it out16:01
LyncosI guess I'll amend again16:01
*** ssurana has joined #openstack-kolla16:03
dimssdake : true. we have that problem in say nova + nova-vmware/hyperv driver etc as well. one repo does not help16:03
sdakeif we fail a 3rd time on k8s + kolla i'm afraid people will lose confidence in our ability to execute16:03
sdakeya but nova is bigger scale16:03
dimsfair point sdake16:03
LyncosSorry for my noobness but do I have to 'push' when I ammend  ?16:03
sdakewe are talking two coe's here16:03
sdakeLyncos type git review16:04
sdakeand gerrit takes care of the git push stuff16:04
rhalliseysdake, disagree16:04
sdakeLyncos we are here to train :)16:04
dimssdake : am perfectly willing to go with majority opinion :)16:04
openstackgerritStephane Boisvert proposed openstack/kolla: Add python-memcache package on cinder / glance  Adding python-memcache package to cinder-base and glance ubuntu docker images  https://review.openstack.org/31176516:04
rhalliseysdake, what if kolla-ansible and kolla-mesos were sep repos16:04
rhalliseythat was the real problem16:04
Lyncossdake thanks for your comprehension we used to be a  SVN shop :-)16:05
dimsrhallisey : right, that was my long term view16:05
sdakerhallisey that is a different way of looing at the problem indeed16:05
Lyncossdake: I think I fixed my commit It looks better now16:05
rhalliseythe repos should've been split to allow for kolla-mesos to have a fair shot at it16:05
*** ssurana has quit IRC16:05
sdakeshould have but capacity problems limited our ability to execute that16:05
sdakewe have the same capacity problems on splitting the repo now16:05
sdakei tink that would have slowed down our ansible implementation tremendously as well16:06
openstackgerritStephane Boisvert proposed openstack/kolla: Add python-memcache package on cinder / glance  Adding python-memcache package to cinder-base and glance ubuntu docker images  https://review.openstack.org/31176516:06
rhalliseysdake, ^ you nailed it right there16:06
rhalliseyas to why mesos didn't work16:06
rhalliseybecause anisble was a first class citizen16:06
dimsand is still going to be first class whether we do one repo or two16:07
rhalliseydims, correct, but ansible is far more developed now16:07
dimsrhallisey : ah ok16:08
rhalliseydims, plus the k8s community is a lot larger16:08
*** salv-orlando has quit IRC16:08
*** ssurana has joined #openstack-kolla16:08
rhalliseylike 10x larger16:08
sdakenailed which16:08
sdakethat splitting the repos would have slowed down commits?16:08
sdakeinstead of committing to one repo we would have commit to two16:09
sdakeour gating is all based aroudn one repo and not two16:09
rhalliseysdake, it would've slowed down ansible commits because we wanted to develop ansible16:09
sdakeit takes 2 months to split the repos and get the ci going again16:09
sdakei dont want to wait16:09
sdakeit would have slowed down the docker  file dev as well16:09
sdakebackports of a fully split repo as mentioend before is a manual process and irrevisible16:10
dimssdake : so another option...we have a feature branch and provide ACL access to k8s group to the branch only16:10
dimssdake : and have sync every week from master to branch or when necessary16:11
openstackgerritStephane Boisvert proposed openstack/kolla: Add python-memcache package on cinder / glance  https://review.openstack.org/31176516:11
dimswe could even do two way sync's16:11
sdakedims how would we sync?16:11
sdake(I am a git noob :)16:11
dimssdake : there's a way to do it. we used it for pika driver and zmq driver in oslo.messaging16:12
dimslet me dig up details16:12
jpeelerdims: but then you'd have to audit the merges from k8s, right?16:12
rhalliseydims, at that point why not just make a new repo?16:12
dimsrhallisey : going from 2 repos to one is difficult. merging feature branch is easy16:12
dimsjpeeler : if we decide k8s is viable then we audit+merge16:13
dimssdake : http://docs.openstack.org/infra/manual/drivers.html16:14
rhalliseyhow about merging two communities into one? I'd say that's harder than merging two repos.16:14
sdakethat is why we have one community16:15
dimsrhallisey : right, we have a deadline say (newton-2) at which point we decide to pull feature branch into master and make it as one ACL16:15
sdakedims what type of rocket science is required to commit to a feature branch?16:15
dimsuntil then folks on branch can pull stuff from master on demand and we have one repo to review for all16:15
sdake(is it hard)16:15
dimssdake : nope. just an entry in .gitreview16:16
sdakeone repo one community - sounds good16:16
rhalliseyexcept there won't be one community..16:16
dimsexample https://github.com/openstack/oslo.messaging/blob/feature/pika/.gitreview#L516:16
rhalliseyeven in one repo..16:16
sdakedims i'd have tot trust you have read through everyone's concerns and understand them all and this meets the requirements people have set out16:16
sdakewe promote people that are active in kolla-k8s-core to kolla-core once htey have earned it16:17
sdakeeveryone else gets removed from +2/+W16:17
dimssdake : that won't change mental model of people who are currently ansible only to review k8s code16:17
dimssdake : right16:17
sdakedims, they might take a peek :)16:18
sdakeif its in one gerrit review queue16:18
dimssdake : u surely hope so :)16:18
dimss/u/i/16:18
sdakethat is what i am after16:18
dimsit's just like people looking at stable/ branches16:18
dimswe can setup jobs that run on feature branches too16:19
*** sacharya has joined #openstack-kolla16:21
*** haplo37 has quit IRC16:24
dimsone more. for the things nihilifer mentioned, the idea would be to first submit patches to master and then pull them into feature branch16:25
dimsso that will take care of making sure folks are working on master mostly and doing only minimal things in the branch16:26
*** ravig has joined #openstack-kolla16:29
*** banix has quit IRC16:30
inc0dims, but that's kina non-standard way in OS16:31
inc0possible, non standard16:31
*** haplo37 has joined #openstack-kolla16:31
inc0feature branches aren't something gerrit handles in openstack16:31
inc0we don't want to be infra's own snowflake16:31
dimsinc0 : we used for pika and zmq drivers without much problems. its up to you all :) the idea is that we are trying to bootstrap both people and code in a "safe" space and then have a good way to either merge code into master or split into a separate repo. i pointed it out as  feature branches are fully supported currently by infra folks AFAIK16:35
inc0ok, fair enough...who will have +2+w power on feature branch?16:36
*** severion has quit IRC16:36
inc0can we specify separate group for that?16:36
openstackgerritMerged openstack/kolla: Remove dependencies on kazoo and friends  https://review.openstack.org/31163216:36
dimsinc0 : yes, we can specify a group for feature branch16:36
inc0ok...so essentially it's lightweight separate repo16:37
dimsright16:37
inc0not horrible solution16:37
*** v1k0d3n has joined #openstack-kolla16:38
dimslet me confirm the ACL question with some folks16:38
sdakerhallisey this lightweight second repo - thoughts?16:43
dimsgot confirmation from infra that a separate group for feature branch is possible16:44
inc0cons of this is it will in fact lower exposure of k8s to people16:45
inc0if you don't know what to look for, it's unlikely you'll find it16:45
sdakeinc0 not if we weekly periodically merge16:46
sdakebut i'm all about simplicity nad one repo gives that :)16:46
inc0sdake, if we merge periodically we might as well skip feature branch as well16:47
inc0as code people will merge in branch will end up in kolla master as well16:47
sdakeinc0 that was dims idea :)16:47
inc0that would solve lack of trust I have tho;)16:48
sdaketrust until given reason not to ;)16:48
dimshaha16:48
dimsinc0 : so i wanted current core to bless sync from branch to master. but folks on k8s group could pull from master whenever they want to16:49
inc0dims that makes sense16:49
inc0but I still think this won't fix problems...I want people to feel in control of their code16:50
inc0I don't want to have core team and half core team16:50
inc0(I would be pissed if I'd be a half-core;))16:50
dimsinc0 : they have complete freedom in the branch :)16:50
inc0better give them their own repo and powers of +2 in it's full glory16:50
dimsit's all a tradeoff :)16:50
dimsall 3 options are valid in one way or another16:50
rhalliseyidk if I really like the branch.  It will cause merging of the CLI + ansible config16:51
rhalliseywhich means down the road is a 0% of a split if the cores want it16:52
rhalliseyI see that split gives is the most flexibility16:52
rhalliseyand if we merge we lose some git history, even though there will not have been a release yet16:52
rhalliseyhttp://stackoverflow.com/questions/1365541/how-to-move-files-from-one-git-repo-to-another-not-a-clone-preserving-history/11426261#1142626116:53
jpeeleri'm pretty sure the git history will work either way. two repos -> one, one -> two repos16:53
rhalliseyearlier from timss16:53
inc0rhallisey, I don't think we will16:53
inc0there are ways16:54
sdakeit took me two ways to get one history for stable/liberty16:54
sdakejust keep that metric in mind16:54
sdakeways/weeks16:54
inc0sdake, we revmaped whole branch16:55
inc0this is easier16:55
rhalliseyso then what's the argument against here? k8s is 10x the size of mesos & ansible is stable16:55
rhalliseythe mesos arguments from earlier don't apply here16:55
inc0and for git magic, liberty was easy too16:55
inc0it was politics that took week16:55
inc0s16:55
sdakethe k8s code base will be small16:56
sdakeprobably 3-4kloc16:56
*** ssurana has quit IRC16:58
inc0sdake, I don't think so16:59
inc0we are creating new models of HA16:59
inc0unlike whatever we have now16:59
sdakek8s in the past was just a bunch of yaml16:59
*** ssurana has joined #openstack-kolla17:00
inc0if we do PoC quality17:00
*** stvnoyes has joined #openstack-kolla17:00
inc0if you want to include fencing of mariadb, ceph stuff17:00
inc0it'll grow17:00
sdakewe dont have fencing now ;)17:00
inc0galera does17:01
inc0we're not running galera on k8s17:01
*** gfidente has quit IRC17:01
sdakeright17:01
*** banix has joined #openstack-kolla17:02
sdakerhallisey can you send out a link to your specification and get people reviewing and commenting on it plz17:02
sdakewe need to get that finished so people know what the implementation willl look like17:02
inc0so we need to solve problems, that'll take time, work and some clever scripts I bet17:02
rhalliseysdake, I'm adding a name to the list one moment17:03
inc0in fact, I think my first contribution to kolla-k8s will be a spec with HA model17:03
inc0we need to figure out this one before we start implementing hard stuff17:03
sdakecan we just have one spec17:03
sdakeplz17:03
rhalliseyinc0, I mentioned your comments about fencing in the spec17:03
*** unicell has joined #openstack-kolla17:04
rhalliseyinc0, I can co author you, but I don't know if you can vote on it17:04
rhalliseyif I do that17:04
*** rajathagasthya has joined #openstack-kolla17:04
sdakeinc0 can you ack https://review.openstack.org/#/c/311570/17:04
patchbotsdake: patch 311570 - kolla-mesos - Retire the kolla-mesos repository17:04
inc0rhallisey, let's just get started and have this discussion later17:04
rhalliseyroger17:05
inc0we have basics figured out, it's crazy netsplits that we need to do17:05
rhalliseyhttps://review.openstack.org/#/c/304182/417:05
patchbotrhallisey: patch 304182 - kolla - Spec: Deploy Kolla images using Kubernetes17:05
rhallisey^ spec17:06
rhalliseythat's good for another round of comments17:06
openstackgerritMerged openstack/kolla-mesos: Retire the kolla-mesos repository  https://review.openstack.org/31157017:06
*** fragatina has quit IRC17:08
sdakedims quick question https://github.com/openstack/kolla-mesos17:09
sdakei missed the dot files17:09
sdakei am going to submit a new review to remove them17:09
sdakeshould I change the readme to say git checkout HEAD^217:10
dimssdake : sure. that or the SHA either one should be ok17:11
openstackgerritSteven Dake proposed openstack/kolla-mesos: Final removal of files beginning with dot  https://review.openstack.org/31179117:13
sdakeinc0 jpeeler rhallisey can you guys rubber stamp that one plz :)17:13
sdakeone thing about seaprate repos, reitrement is easier ;)17:14
openstackgerritMerged openstack/kolla-mesos: Final removal of files beginning with dot  https://review.openstack.org/31179117:14
sdakethanks ;)17:14
dimslol17:15
dimsdang i missed a easy review to pad my stats17:15
openstackgerritSteven Dake proposed openstack/kolla-mesos: Fix typos in readme.rst  https://review.openstack.org/31179217:16
sdakeone more17:16
jpeelerthe readme says where the kubernetes dev will take place17:16
* sdake groans17:16
dimslol17:16
jpeelerwhich hasn't been decided. and there were several misspellings in the readme :(17:16
sdakejpeeler i am going to leave the acls in palce17:16
sdakeuntil that is decided17:16
sdakeand make whatever we decide17:16
sdakein the readme17:16
sdakethen remove the acls as is documented in the retirement document17:16
sdakefair enough?17:17
sdakesee https://review.openstack.org/#/c/311574/17:17
patchbotsdake: patch 311574 - openstack-infra/project-config - Part two of kolla-mesos retirement17:17
jpeelerwhat editor do you use sdake ?17:17
sdakenotice worklow -117:17
sdakejpeeler vi17:17
jpeeleri wonder if there's a way to add spell check to that17:18
sdakeit would be helpful for rst files only17:18
sdakeif you find a way let me know17:18
sdakethat way I dont keep having typos in my commit messages :)17:18
*** ccesario___ has quit IRC17:19
rhalliseydims, lol17:19
sdakei did that retirement on a plane :)17:19
*** ccesario___ has joined #openstack-kolla17:19
sdakewit hlots of liquor17:19
sdakedims i dont think your stats need paddding :)17:21
sdakelast cycle I was top 1% of all commits for openstack for the lifetime of the project17:21
dimssdake : lol17:21
sdakethis cycle top 1.5% :(17:21
sdakemy typos are actually to pad stats17:22
sdaketo get into the top 10 :)17:22
* dims starts a new email thread "Gaming stackalytics - How to do it right" :)17:22
sdakehey, atleast i am not changing "openstack" to "OpenStack" across all the projects17:22
jpeelerhaha17:22
* sdake shakes head at that dude17:23
jpeelerhonestly though if people want to do project wide spelling fixes, go for it. at least it wasn't a one project drive by commit to get an ATC17:24
*** ccesario___ has quit IRC17:30
sdakejpeeler agree - although even drive by atc commits typically improve the code or I -1 em :)17:32
sdakewhy is my heater swet to 80 in summertime17:32
dimsrelated to prev discussion but another data point... if we say ansible is advanced, how long would it take to split that into a separate repo?17:32
sdakei dont get this whole nest thing17:32
sdakeit just doesn't work17:32
sdakedims i think 4-6 weeks17:32
*** fragatina has joined #openstack-kolla17:32
sdaketo split both efforts from repo 6-8 weeks17:33
rhalliseyand that's a code freeze17:33
*** fragatina has joined #openstack-kolla17:33
sdakeya its a cvode freeze17:33
sdakeit locks up the repo for some time17:33
dimsrhallisey sdake : mainly CI?17:33
sdakedims ci integration project config etc17:34
timssI actually noticed a couple of typos in the doc when reading through it earler. Is a commit with only 1-2 character fixes ok?17:34
rhalliseytimss, ya17:34
sdaketimss if there is an error fix it17:34
sdakedoc fixes dont' need bug ids17:34
sdakewe dont backport docs because afaik they can't be versioned17:34
rhalliseysay we were merged and we want to split 6-8 weeks of a code freeze on an entire project O.o17:34
sdakethe reason we require bug ids is to deal with backports17:34
timssall right, I'll try to take a look at it later, no experience with gerrit or openstack development in general other than lurking17:35
sdaketimss √17:35
sdakehttps://wiki.openstack.org/wiki/How_To_Contribute17:35
dimsrhallisey : so no way to start a new repo, get CI to work on new repo while continuing work to proceed in the old repo in parallel until we cut over17:36
sdakedims interesting idea - hadn't thought of that17:36
sdakeit would require a repo rename17:36
sdakewhich fungi says infra doesn't do anymore17:36
sdakebut they might cut us some slack on that special case17:36
rhalliseyhm17:37
timssas for spell checking in vi; it's builtin, as well as dictionary functionality if you use vim. There are plugins which make it easier to use though, such as vim-lexical: https://github.com/reedes/vim-lexical17:37
dimsy, we can ask for exception17:37
sdakeright dims17:37
rhalliseydims, does that mean were always playing catchup though?17:37
timssexamples for only using with certian filetypes are included in its docuemntation17:37
rhalliseysay only 2 people work on the split17:37
timsssdake: thanks for the link17:37
dimsrhallisey : once the CI is up on the new repo, we cut over immediately and copy over stuff we need from the other repo17:38
dimsthat's all the options i can think of... head hurts now :)17:38
sdakeya my brain was melted by thursday of alst week17:38
sdakeface melted  by friday :)17:38
sdakenext time we only doing a half day contributor meetup ;)17:38
*** inc0 has quit IRC17:39
sdakemidcycle, ansible offices or wesford?17:39
*** ccesario___ has joined #openstack-kolla17:39
*** Serlex has quit IRC17:39
*** inc0 has joined #openstack-kolla17:39
sdakerdu woudl be good too at rht facilities17:39
rhallisey:)17:39
* sdake not a fan of westford17:39
rhalliseysdake, dude come to westford!17:40
* dims starts his car17:40
rhalliseyya dims is nearby!17:40
sdakethe red aht offices there are beutiful17:40
sdakereally modern ad great grass17:40
sdake(to walk on, not smoke :)17:40
inc0grass...I've heard that it is a thing...not in Texas tho17:40
sdakei have grass in my backyard17:41
sdakeand weeds17:41
dimsif it was winter we could go snow tubing next door...right rhallisey ?17:41
rhalliseydims, it'17:41
rhalliseyit's not as much fun as you think17:41
rhallisey:)17:41
rhalliseyit's decent17:41
dimsrhallisey : y, brought the kids ones there. long lines :)17:43
rhalliseyit's just hard to argue it's a mountain17:44
dims:)17:44
rhallisey:D17:44
openstackgerritTravis McPeak proposed openstack/kolla: Adding a few #nosec tags to prepare for Bandit usage  https://review.openstack.org/31086917:46
*** thumpba_ has quit IRC17:47
*** daneyon has joined #openstack-kolla17:48
*** thumpba has joined #openstack-kolla17:51
*** inc0_ has joined #openstack-kolla17:52
*** inc0 has quit IRC17:52
*** daneyon has quit IRC17:53
openstackgerritTravis McPeak proposed openstack/kolla: Adding a few #nosec tags to prepare for Bandit usage  https://review.openstack.org/31086917:53
*** ccesario___ has quit IRC17:54
openstackgerritTravis McPeak proposed openstack/kolla: Adding a few #nosec tags to prepare for Bandit usage  https://review.openstack.org/31086918:04
*** fragatina has quit IRC18:13
*** fragatina has joined #openstack-kolla18:14
*** fragatina has quit IRC18:19
*** Mr_Broken has joined #openstack-kolla18:22
*** Mr_Broken has quit IRC18:26
*** inc0_ has quit IRC18:29
*** mkoderer__ has quit IRC18:32
*** ravig has quit IRC18:39
*** fragatina has joined #openstack-kolla18:40
*** ravig has joined #openstack-kolla18:41
*** ravig has quit IRC18:43
ccesarioLyncos, I just try simulate the problem reported... and you are right.... !! the memcache is missing in ubuntu binary18:44
Lyncosccesario... I'm also testing neutron.. it seems that it also need it18:45
Lyncos(not part of initial bug report)18:45
ccesarioLyncos, cool!18:45
Lyncosnow I'm trying to figure out how to refresh my images .. as it seems to always pull the old one18:46
*** rajathagasthya has quit IRC18:49
*** banix has quit IRC18:51
*** banix has joined #openstack-kolla18:51
*** inc0 has joined #openstack-kolla18:52
inc0sdake,19:13
inc0we need to merge liberty patch19:13
inc0to stable/liberty19:13
inc0we don't have stable/liberty now19:13
*** ravig has joined #openstack-kolla19:18
sdakeinc0 justwoek up from nap19:18
sdakedid people test it?19:18
sdakei am ok with merging butnot ok with testing unless there is enough testing19:18
*** ravig has quit IRC19:18
inc0people, did you test it?19:20
inc0if you didn't, then do test it19:20
sdakeiu tested centos source works19:21
sdakei tested centos binary fails19:21
sdakei dont know why centos binary doesn'twork19:21
*** ravig has joined #openstack-kolla19:21
sdakei also tested thatsome services have 127.0.0.1 as their ip address which is wrong19:21
inc0sdake, there is nothing in liberty that would make this happen, not that I know of in any case19:22
inc0centos binary - no clue, I don't speak centos19:22
sdakeit has to do with how auth is done19:23
sdakeit was fixed in neutron 7.0.319:23
sdakecentos binary hsa 7.0.319:23
sdakeyet centos binary doesn't appear to have the correct change19:23
sdakeor alternately iwas testing the wrong stuff :)19:23
sdakei was akind of tired19:23
sdakei can get back to it today19:23
sdakethe 127.0.0.1 was around [vnc] in nova19:24
sdakewhich changed19:24
sdakein liberty to mitaka19:24
inc0if it's in nova, we can't really do much about it19:25
inc0guys please test it out19:25
inc0it's important19:25
mlimainc0, tell me how can i help19:25
mlimai can test ubuntu source here :)19:26
inc0mlima, https://review.openstack.org/#/c/308390/19:26
patchbotinc0: patch 308390 - kolla (stable/liberty) - WIP: Changes needed to deploy liberty with mitaka ...19:26
sdakeif someone could test someo f hte newer services too that would rock19:26
sdakebecausei only tested comptue kit19:26
sdakebut i am feeding myself atm because i barely ate last week19:27
sdakeexcept blowout dinners :)19:27
mlimamultinode? single node?19:27
sdakemultinode woudl be best19:28
inc0all needs working19:28
inc0needs to work*19:28
sdakei need to get my lab put tgoether today before i can begin testing19:29
sdakemy office reorgdisconnected dmy server i test on19:29
mlimawhat is the deadline?19:29
*** ravig has quit IRC19:29
*** ravig has joined #openstack-kolla19:29
mlimathe test is build, deploy and launch some instance?19:30
sdakeyup19:30
sdakee need the new services tested too19:30
mlimajust it?19:30
*** absubram has joined #openstack-kolla19:30
mlimanew services?19:30
sdakealso the versions used in the tarball references are out of date19:30
sdakethat needs fixing19:30
sdakei fixed it for nova and neutron19:31
sdakebut then had to get on a plane without snakes19:31
*** MarMat_ has joined #openstack-kolla19:31
mlimaok19:31
mlimawhat is the deadline? sdake19:32
inc0sdakes on the plane19:32
inc0mlima, it would be cool to make it work before summit19:32
*** huikang has joined #openstack-kolla19:32
inc0in Austin19:33
sdakeinc0 what i'm getting at is if you could fix some of the problems i just outlined that would be great - while I get my lab reassembled19:33
inc0will do19:33
mlimaI need to set up my multinode environment, but i can test single node19:34
mlima:/19:34
mlimaand tomorrow i test multinode19:34
*** MarMat has quit IRC19:34
ccesarioLyncos, ping ?19:38
Lyncosyep19:39
ccesarioLyncos, neutron needs memcache too19:39
ccesariohttp://paste.openstack.org/show/495908/19:39
Lyncoswant me to add it up to my original bug report ?19:39
ccesariocould you please update your ps?19:40
Lyncosps ?19:40
inc0patchset Lyncos19:40
ccesariopatch set19:40
ccesariohttps://review.openstack.org/#/c/311765/19:41
patchbotccesario: patch 311765 - kolla - Add python-memcache package on cinder / glance19:41
Lyncosyes sure19:41
Lyncosjust give me some time so I can test everything ... trying to setup a better test environmnet19:41
LyncosI'm also trying to figure out why memcache is not added to glance even if i modified my docker file19:42
ccesarioOk, i 'll  update the launchpad bug id19:42
ccesarioLyncos, did you rebuild it ? --no-cache option ?19:42
Lyncosyeah19:42
Lyncosbut I can't see apt getting memcache19:42
LyncosI probably did something wierd19:43
sdakeLyncos are you using a registry and forgot to --push?19:43
LyncosI'm always --push19:43
Lyncosand I also deleted images from my 'nodes'19:43
Lyncosand set   docker_image_pull:  always  in global.yml19:43
*** rajathagasthya has joined #openstack-kolla19:44
LyncosI'm re-building everything again just to make sure19:44
ccesarioright19:49
LyncosIs it normal that git review hangs ?19:51
Lyncosnvm19:53
Lyncosmy bad :-)19:53
openstackgerritStephane Boisvert proposed openstack/kolla: Add python-memcache package cinder,glance,neutron  https://review.openstack.org/31176519:54
*** absubram has quit IRC19:56
*** absubram has joined #openstack-kolla19:58
*** huikang has quit IRC19:58
openstackgerritStephane Boisvert proposed openstack/kolla: Add python-memcache package cinder,glance,neutron  https://review.openstack.org/31176520:02
*** mlima has left #openstack-kolla20:05
*** sdake_ has joined #openstack-kolla20:08
*** sdake has quit IRC20:08
ccesarioLyncos, make the package list sortable :) as other Dockerfiles20:09
openstackgerritStephane Boisvert proposed openstack/kolla: Add python-memcache package cinder,glance,neutron  https://review.openstack.org/31176520:12
Lyncosdone20:12
*** huikang has joined #openstack-kolla20:13
inc0thank you Lyncos20:14
Lyncosnp20:15
ccesarioLyncos, thank you ;)20:18
LyncosI still don't have it installed in my glance image :-(20:18
*** serverascode_ has joined #openstack-kolla20:23
*** ravig has quit IRC20:27
*** daneyon has joined #openstack-kolla20:28
*** ravig has joined #openstack-kolla20:28
*** elemoine- has joined #openstack-kolla20:28
*** ntpttr has quit IRC20:29
*** elemoine has quit IRC20:29
*** serverascode has quit IRC20:29
inc0Lyncos, did you rebuild it?20:29
inc0and re-pushed20:29
LyncosYes20:29
*** daneyon_ has quit IRC20:29
Lyncosit's like my server are not pulling out the new image20:29
Lyncoseven if I set   docker_image_pull to always20:29
*** daneyon_ has joined #openstack-kolla20:31
*** thumpba has quit IRC20:31
inc0strange20:31
inc0well, you can run cleanup-images on stuff20:31
LyncosI did20:31
inc0then something is not right20:32
Lyncosin fact I can't see memcache at build step20:32
inc0did you push them?;)20:32
inc0ahh20:32
inc0hmm20:32
Lyncoseven if I do --no-cache20:32
inc0Lyncos, you're running ubuntu?20:32
LyncosYes20:32
*** banix has quit IRC20:33
inc0ahhh20:33
Lyncos kolla-build --push --type binary --base ubuntu --registry our.repo.org:5000 --no-cache -T 500 --namespace kollaglue glance-api20:33
inc0hold on20:33
LyncosIt's like it's not reading the right dockerfile20:33
ccesarioLyncos, with me it is working20:34
inc0https://github.com/openstack/kolla/blob/master/docker/openstack-base/Dockerfile.j2#L10820:34
inc0something is wrong20:34
inc0in your case20:34
inc0you should have python-memcached installed20:34
*** serverascode_ is now known as serverascode20:34
Lyncosin every images right ?20:35
*** daneyon_ has quit IRC20:35
inc0every openstack image20:35
dimsinc0 : that one is "python-memcached", Lyncos is installing "python-memcache" without the 'd'20:35
Lyncosit's not working20:35
inc0well, python lib for talking to memchace is python-memcached afair20:36
dimsdunno what the diff is20:36
inc0ubuntu might have renamed it20:36
Lyncosbut none is working20:36
ccesarioinc0, https://github.com/openstack/kolla/blob/master/docker/openstack-base/Dockerfile.j2#L108  but this is reagarding Redhat based ....  right!?20:36
dimsglobal requirements has the python package "python-memcached>=1.56  # PSF"20:37
*** jtriley has quit IRC20:37
Lyncospython-memcached or python-memcache is not installed in both case20:37
LyncosI think I was wrong with python-memcache and it is really python-memcached which is not installed20:38
inc0ccesario, this one is not https://github.com/openstack/kolla/blob/master/docker/openstack-base/Dockerfile.j2#L30720:38
Lyncosin cinder_api I can see  python-pymemcache module20:38
*** ravig has quit IRC20:39
Lyncosnothing in  glance or neutron20:39
inc0hmf20:39
inc0thats bad20:39
ccesarioinc0, yes. But the problem only happen in binary mode ... in source mode it is ok :)20:40
Lyncosyou maybe better to double check on your side ... maybe my environment is wrong...20:40
inc0Lyncos, you're running ubuntu-source?20:40
inc0if not, do this20:40
LyncosBinary20:40
inc0I stopped running binary20:40
inc0and ubuntu binary was never really well tested20:41
sbezverkccesario have you repro the same issue as Lyncos reports?20:41
Lyncosin openstack-base   you don't have any memcache20:41
ccesarioinc0, the problem is related to ubuntu-binary20:41
ccesariosbezverk, yes20:41
inc0yes, well, I would recomend against running ubuntu binary20:41
sbezverkccesario cool, thanks for confirming,, as I could not find any logs..20:41
inc0Lyncos, is there anything specific about source that would prevent you from using it?20:42
ccesariosbezverk, I post the logs in launchpad20:42
Lyncosinc0 .. I was thinking binary would be faster to build ? no real reason20:42
LyncosThat make my bug request useless then20:43
Lyncosif you guys fix it in openstack-base20:43
*** macsz has quit IRC20:43
inc0Lyncos, use source, much more tested with ubuntu20:43
Lyncosok20:43
inc0keep the bug, it's valid20:43
Lyncoswill do20:43
*** macsz has joined #openstack-kolla20:43
LyncosI'm trying source right now20:44
inc0ubuntu-source should work, but frankly everyone runs source builds that I know of20:44
inc0centos doesn't show any apparent benefit of running binary20:44
inc0besides having to deal with repo issues20:44
*** ravig has joined #openstack-kolla20:45
*** rajathagasthya has quit IRC20:45
LyncosI'll fix the bug tomorrow  ... removing modifications from individual base files (cinder, glance neutron) and modify openstack-base instead20:46
inc0would be better20:46
inc0thank you, I'll make comment on patchset20:46
Lyncosthis will make it more 'clean'20:46
*** rajathagasthya has joined #openstack-kolla20:47
inc0definetly20:51
inc0that's what it's for20:51
*** ravig has quit IRC20:53
*** ravig has joined #openstack-kolla20:54
*** harlowja has joined #openstack-kolla20:56
*** inc0 has quit IRC20:58
*** dmk0202 has joined #openstack-kolla21:00
openstackgerritStephane Boisvert proposed openstack/kolla: Add python-memcache package openstack base  https://review.openstack.org/31176521:01
*** sdake_ has quit IRC21:03
*** sdake has joined #openstack-kolla21:03
*** ccesario___ has joined #openstack-kolla21:03
sdakehey cats21:04
sdakeinc0 not true at all, centos binary is faster then sourc ebuilds21:07
sdakebecause centos binary compiles the python bytecode21:07
*** intr1nsic has quit IRC21:09
*** intr1nsic has joined #openstack-kolla21:10
*** ByPasS has quit IRC21:10
*** ntpttr- has quit IRC21:10
*** ByPasS has joined #openstack-kolla21:12
*** dmk0202 has quit IRC21:12
jpeeleri thought the pyc files were generated after first execution anyway21:12
jpeeleris that not true sdake ?21:13
*** ntpttr has joined #openstack-kolla21:13
*** daneyon has quit IRC21:16
sdakeinc0 i got my lab setup21:17
sdakejpeeler in rpms they are created prior to first start21:18
sdakeon from source we drop root so the binaries never get executed21:18
sdakeso there is never any precompiled bytecode21:18
sdakeits probably 5-15% difference in performance21:18
jpeeleroh right, drop root21:18
sdakeconsidering openstack is bloated anyway21:18
sdakeit probably doesn't matter all that much21:18
*** haplo37 has quit IRC21:19
sdakeinc0 i have 3 of my workstations now setup21:21
sdakeguess inc0 is gone for the day21:21
*** mbound has joined #openstack-kolla21:25
*** ccesario___ has quit IRC21:28
*** huikang has quit IRC21:29
sbezverksdake if you have 5 minutes, could you check this PS please https://review.openstack.org/#/c/308447/21:35
patchbotsbezverk: patch 308447 - kolla - Addining ability to specify capabilities and security21:35
*** ravig has quit IRC21:42
*** ravig has joined #openstack-kolla21:43
*** ravig has quit IRC21:46
*** ravig has joined #openstack-kolla21:53
*** banix has joined #openstack-kolla21:56
*** daneyon has joined #openstack-kolla21:59
*** thumpba has joined #openstack-kolla22:01
*** ccesario___ has joined #openstack-kolla22:01
*** ntpttr- has joined #openstack-kolla22:05
*** ccesario___ has quit IRC22:06
*** thumpba has quit IRC22:08
*** mbound has quit IRC22:11
*** betheynyx has quit IRC22:13
*** absubram has quit IRC22:16
*** fragatin_ has joined #openstack-kolla22:19
*** ravig has quit IRC22:20
*** fragatina has quit IRC22:22
*** ravig has joined #openstack-kolla22:26
*** rajathagasthya has quit IRC22:27
*** ravig has quit IRC22:32
*** ravig has joined #openstack-kolla22:32
*** ravig has quit IRC22:34
*** ravig has joined #openstack-kolla22:34
openstackgerritRyan Hallisey proposed openstack/kolla: Doc rework for quickstart, multinode, and image-building  https://review.openstack.org/31188422:34
*** daneyon has quit IRC22:36
*** ravig has quit IRC22:38
*** ravig has joined #openstack-kolla22:38
*** fragatina has joined #openstack-kolla22:39
*** fragatina has quit IRC22:39
*** fragatina has joined #openstack-kolla22:40
*** banix has quit IRC22:42
*** ravig has quit IRC22:42
*** ravig has joined #openstack-kolla22:42
*** asalkeld has joined #openstack-kolla22:42
*** dwalsh has quit IRC22:43
sdakerhallisey 20 comments on spec - please address ;)22:47
*** betheynyx has joined #openstack-kolla22:57
openstackgerritSerguei Bezverkhi proposed openstack/kolla: Addining ability to specify capabilities and security  https://review.openstack.org/30844723:03
asalkeldsdake: fyi, I am keeping out of the discussion on kube. I pretty much disagree with both points (abi and and seperate repo) and don't want to get into an anti kolla-mesos thing. IMHO technically there was nothing wrong with our approach and it was purely business/management descision to drop it that caused us to step away.23:04
sdakeasalkeld fair enough23:05
sdakejust to be clear though, you mean you prefer one repo?23:05
sdakeor you want separate repo23:05
sdake(you were unclear above)23:06
asalkeldno, per deployment makes senes to me23:06
sdakeper COE repo yo umean23:06
asalkeldi don't know what a "coe" is23:06
sdakeasalkeld what i'd do is send a note to hte mailing liststating sincey ou are not really actively involvedi nthe projet you do not wish your vote to be counted23:06
sdakecontainer orchestration engine23:06
sdakebecause as is we have 12 cores23:06
sdakewhich means if its 6/6, we will hae a tiebreak problem23:07
asalkeldi'll do that if my vote is needed23:07
sdakewith 11 people eligble to vote, only 6 votes are needed rather then 723:08
sdakeso you see you could end up being a tiebreaker23:08
sdakewhich i am sure you dont want after what you just said above ;)23:08
sdakeI think it may come to a tie break :)23:08
asalkeldok, well let me know23:08
sdakewith the current voting23:08
sdakewill do23:08
sdakethanks for your honesty23:08
asalkeldalso if you remember correctly i did give you a detailed response about the abi question23:09
sdakei dont sorry23:09
sdakebut not saying you didn't23:09
sdakejust dont recall - brain mush23:09
asalkeldyou said i replied "meh"23:09
sdakemy mistatement23:10
sdakewould you like me to correct it ?23:10
sdakei'm sorry angus i can't remember every single detailed converstaion i have about every technical issue23:10
sdakebuti do know it wasn't resolved23:10
sdakeif you want me to take action to correct it i can do that23:10
asalkelddocker abi is like a library, define what can be done the format. not exact content. This is like saying every heat template must be written by the heat team23:10
sdakesince i'm obviously inthe wrong here23:11
asalkeldsdake: don't worry23:11
sdakeagain apologies if that got your bloodpressure up ;(23:11
sdakeas you can tell this morning was prety heated :)23:12
asalkeldi wrote up an etherpad, can't find it - I'll hunt out my irc history23:12
sdakeneed a thermometor23:12
sdakei definately dont remember an etherpad23:12
sdakewhat all that thread shows is that the kolla team really cares about kolla strongly23:13
sdakebut has different opinions23:13
*** daneyon has joined #openstack-kolla23:13
sdakesince we all have different logical thought patterns :)23:13
sdakeasalkeld anyway i wouldn't worry about it, nobody actually reads what I write :)23:14
*** daneyon has quit IRC23:18
*** ravig has quit IRC23:19
*** jrist has quit IRC23:19
asalkeldsdake: here is the etherpad https://etherpad.openstack.org/p/kolla-set_configs23:21
sdakewow didn't see that at all23:22
sdakeya i like the utopia model23:23
sdakeeven though its unused23:24
sdakeits one abi23:24
sdakevs two23:24
sdakethanks for sharing that document23:24
sdakei hope we have utopia model in k8s and ansible abi23:25
sdakerhallisey can you somehow work that utopia model into the spec23:25
asalkeldsdake: mistake23:26
asalkeldjust saying, i think you are nuts23:26
sdakei am nuts23:26
sdakeyour right23:26
*** daneyon has joined #openstack-kolla23:26
sdakewhy else would anyone be a ptl of a project in openstack? :)23:27
asalkeldcontent of those files != ABI,23:27
sdakewell there are no dependencies in the k8s model23:27
asalkeldABI is the format and they ENV23:27
sdakeso the utopia model is possible23:27
sdakeabi si the json file and env right23:27
asalkeldformat, not specific files - IMHO23:28
*** daneyon has quit IRC23:28
asalkeldanyway, i'll stop arguing...23:28
sdakethanks for findin the link asalkeld23:29
*** daneyon has joined #openstack-kolla23:29
sdakewoud you like me to post it to the thread to correct my "meH" statemet23:29
asalkeldno, don't give it fuel23:29
sdakeI thought the lack of action was a meh, but you did indeed to action of writing up an etherpad23:29
*** ccesario___ has joined #openstack-kolla23:30
sdaketo/do action23:30
sdakecool thanks for being mature about it :)23:30
sdakebut i want you to understand that i thought you pretty much ignored my request23:31
sdakewhich kind of pissed me off23:31
sdakeso it was a communication problem on my end23:31
sdakeso please accept my apology on the meh statement atleast on irc :)23:31
asalkeldk23:31
sdakewhat i should have done is harassed you again about it23:32
sdakeat which point you would have pointed out the etherpad23:32
sdakeand then i wouldn't have written that meh statement23:32
sdakebut i was neck deep in bugs and you were neck deep in othe rthings23:33
sdakeso that didn't happen23:33
sdakeboth human, my error :)23:33
sdakeif we could just read each other's minds :)23:33
*** jrist has joined #openstack-kolla23:33
asalkeldsdake: it says "if you are on the list" ... "please vote" - I am not on that list23:34
sdakeyou are - under kolla-core23:34
sdakemaybe that was befoer kolla-core was added to the list23:35
sdakea couple cores have approached me and said ony cores should vote on this since its a policy decision23:35
sdakewhich i tend to agree with23:35
sdakebreaking new ground here, not quite sure what to do23:35
sdakeits not like i imagined half our cores want it integrated from the start23:36
sdakethat seems obvious from the ml posts :)23:36
*** daneyon has quit IRC23:36
sdakeit affects the new contribtors as much as the current kolla core team23:37
*** ssurana has quit IRC23:37
sdakeand I want to be inclusive of our new contributors23:37
*** sdake_ has joined #openstack-kolla23:41
ccesario___Evening folks!!23:41
*** jtriley has joined #openstack-kolla23:41
*** sdake has quit IRC23:43
*** banix has joined #openstack-kolla23:46
sdake_hey ccesario___23:47
*** diogogmt has quit IRC23:51
ccesario___Hey sdake_ !23:52
*** diogogmt has joined #openstack-kolla23:54
*** sdake_ has quit IRC23:55
*** sdake has joined #openstack-kolla23:56
*** sdake has quit IRC23:56
*** sdake has joined #openstack-kolla23:57
*** sdake has quit IRC23:58
ccesario___sdake, how is going the kubernetes directions?23:59

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