Tuesday, 2014-02-11

*** chandan_kumar has joined #openstack-climate02:48
*** chandan_kumar has quit IRC02:54
*** chandan_kumar has joined #openstack-climate02:56
*** chandan_kumar has quit IRC03:04
*** chandan_kumar has joined #openstack-climate03:29
*** chandan_kumar has quit IRC05:15
*** chandan_kumar has joined #openstack-climate05:16
*** DinaBelova_ is now known as DinaBelova06:31
*** saju_m has joined #openstack-climate06:38
*** saju_m has quit IRC06:43
*** saju_m has joined #openstack-climate06:50
*** saju_m has quit IRC06:51
*** DinaBelova is now known as DinaBelova_07:30
*** saju_m has joined #openstack-climate07:37
*** saju_m has quit IRC07:52
*** bauzas has joined #openstack-climate08:01
*** DinaBelova_ is now known as DinaBelova08:32
openstackgerritDina Belova proposed a change to stackforge/climate: Port to oslo.messaging  https://review.openstack.org/5788008:38
openstackgerritA change was merged to stackforge/climate: lease_create now raises InvalidDate exception  https://review.openstack.org/7163108:48
*** saju_m has joined #openstack-climate08:51
*** DinaBelova is now known as DinaBelova_09:13
*** DinaBelova_ is now known as DinaBelova09:24
bauzasDinaBelova: about SchedulerService, you there ?09:57
bauzasDinaBelova: I think it would be worth it keeping for this BP : https://blueprints.launchpad.net/climate/+spec/ha-manager10:00
bauzasbecause IMHO the scheduler should be a separate service10:00
bauzasthat's currently dead code, so there are 2 choices :10:01
bauzas1. either we keep it for future work on https://blueprints.launchpad.net/climate/+spec/ha-manager10:01
bauzas2. or we remove it and we recreate it later on ?10:01
bauzasDinaBelova: what is your preference ?10:01
*** DinaBelova is now known as DinaBelova_10:03
*** DinaBelova_ is now known as DinaBelova10:19
DinaBelovaI think we may keep it as is10:19
DinaBelovaI think we may keep it as is :?10:19
DinaBelovaif we'll use this code - great10:19
DinaBelovaif not - I'll remove it while working on ha mechanism10:19
bauzasDinaBelova: I'm just submitting a patch for removing it10:20
bauzasit would anyway require to move to oslo.messaging10:21
bauzasso, let's go with option #210:21
DinaBelovaok, I'm ok with that10:21
bauzasand recreate it within the HA bp10:21
openstackgerritSylvain Bauza proposed a change to stackforge/climate: Remove old Scheduler RPC Service  https://review.openstack.org/7261210:21
bauzasnice synchronization :)10:21
DinaBelova:)10:22
bauzasit was submitted 2 mins ago... :D10:22
*** saju_m has quit IRC10:25
*** saju_m has joined #openstack-climate10:26
DinaBelovabauzas, also I wanted to speak about summit talks10:51
bauzasDinaBelova: sure10:51
DinaBelovanow we're thinking about two of them10:51
bauzasyep, I thought about it10:52
DinaBelovaare you sure we should divide our Climate forces?10:52
bauzasone talk is risky10:52
bauzasunless you think we have a good chance to get it10:52
bauzasand I think there can be 2 different audiences10:52
DinaBelovaI mean maybe it'll be better to have one talk, but we'll have more voices for it? I mean having two of them - we may have not enough voices on both10:52
bauzasone technical or one more IT general10:53
SergeyLukjanovbauzas, DinaBelova, I see you speaking about Climate talks proposals for Juno sumit10:53
SergeyLukjanov:)10:53
bauzaswell, if voting is like for HK, that's a rolling proposal10:53
bauzasso, unless you got huge fans in Mirantis, 2 talks are better than one ;) :D10:54
DinaBelovaSergeyLukjanov, yep but I can't get your 'Juno' word10:54
bauzasAtlanta will be the Juno summit :)10:54
SergeyLukjanovJ release cycle name :)10:54
DinaBelovaah :)10:54
DinaBelovayep10:54
DinaBelovasure10:54
SergeyLukjanovIMO, having one joined talk is increasing the chance to be selected for summit10:54
bauzasJuno will be in May :)10:54
bauzas:p10:54
DinaBelova:D:D:D10:54
DinaBelovayep, that's confusing for me :)10:54
bauzasSergeyLukjanov: do you think so ?10:55
SergeyLukjanovbauzas, yup10:55
bauzasSergeyLukjanov: I have to admit I'm not an expert for this10:55
SergeyLukjanovlet me share my concerns about separation10:55
bauzasSergeyLukjanov: sure10:55
DinaBelovaSergeyLukjanov, please, yes10:55
SergeyLukjanovfirst of all, you have only several tracks to propose your talks10:55
bauzasSergeyLukjanov: I was basically thinking that proposing more talks would increase our chances to at least get one10:55
SergeyLukjanovand if two talks will be in one track - than 100% only one will be selected10:55
bauzasSergeyLukjanov: that's why we're proposing 2 talks on different tracks10:56
bauzassee the gdoc10:56
DinaBelovahttps://docs.google.com/a/mirantis.com/document/d/1EsacsG-AgaM67SH4J_zoPUI7N77-5_7cOnMFQFgLVgQ/edit10:56
SergeyLukjanovit's guaranteed that talks will not be reassigned ;)10:56
bauzasyay10:56
bauzasjust removed the Operations track for the first talk, in order to be clear10:57
SergeyLukjanovand IMO it's better to send proposal to several tracks10:57
bauzasSergeyLukjanov: see the gdoc10:57
SergeyLukjanovthe next concern is that it's better to have a talk with several folks from several companies with cool interesting proposal10:57
SergeyLukjanovand w/o technical details10:57
SergeyLukjanovto overview project, goals, status and roadmap10:57
SergeyLukjanovshow demo10:57
bauzasthat's exactly why we propose the first talk10:57
DinaBelovaexcept demo thing :?10:58
SergeyLukjanovand continue on designed summit / unconference10:58
DinaBelovawe're not sure here10:58
bauzaswell, the demo thing can be discussed10:58
bauzasI'm not con10:58
SergeyLukjanovI'll propose talk for savanna w/o demo10:58
SergeyLukjanovjust status, overview, etc.10:58
SergeyLukjanovwith two folks from RH and HWX10:58
SergeyLukjanovit adds great visibility for the talk10:58
bauzasyay10:58
SergeyLukjanovand IMO all developers will be on design summit10:59
SergeyLukjanovso, you should target mostly for non-devs10:59
DinaBelovathat's true....10:59
SergeyLukjanovand if you'd like to catch devs or share tech details - unconference is your choise10:59
DinaBelovalast summit all devs were on design summits10:59
DinaBelovaand on unconference thing11:00
SergeyLukjanovthis time we'll have onle one (!!) day w/o design summit11:00
bauzaswell, the ideal would be to get some timeslots on design summit11:00
SergeyLukjanovand it'll be full of keynotes11:00
SergeyLukjanovhttp://www.openstack.org/summit/openstack-summit-atlanta-2014/11:00
bauzasyay11:00
bauzasbut don't you think a talk for operators would make sense ?11:00
bauzasI was thinking of 2 audiences11:01
bauzas1. IT managers and people willing to know what's in the ecosystem11:01
bauzas2. Openstack operators wanting to know how to better manage their systems11:01
DinaBelovabauzas, I suppose SergeyLukjanov is trying to say that for 2nd audience it'll be better to catch them somewhere else11:01
bauzasoperators won't be at the design summit11:02
bauzasthat's a different audience from savannah11:02
DinaBelovabut I suppose they'll go to 1.11:02
bauzasClimate is also planned to be some tool for operations11:02
DinaBelovabauzas, don't name Savanna as Savannah :D11:02
bauzasDinaBelova: uh, shame on it11:02
DinaBelovaSergey does not love it :)11:02
bauzasanyway, Savanna will be renamed :p11:03
SergeyLukjanovdue to the renaming, I'm ok with any :)11:03
bauzasok, S-the-one-whose-name-shouldn't-be-pronounced11:03
bauzasthen11:03
DinaBelovaOk, I'm confused now about summit abstracts... For me one talk looks better, but I see you, Sylvain, don't really like it11:04
SergeyLukjanovbauzas, I think that it could be ok to propose two talks in following manner - main talk with you and Dina proposed to all relevant tracks excluding operators and one more talk with you and Dina about usecases for operators but only for operators track to avoid overlaps between talks11:04
bauzasso, if we do one talk, that means that in 40 mins, we have to go thru all the concepts, features, tools and provide a demo11:04
SergeyLukjanovbut IMO one talk is better11:04
bauzasthat would be though11:04
bauzasSergeyLukjanov: well, I do truly understand your thoughts11:05
SergeyLukjanovbtw ops track is overloaded AFAIK11:05
bauzasSergeyLukjanov: so, the question is : do we think 40 mins is enough for it ?11:05
SergeyLukjanovbauzas, IMO demo should be 5-10 mins, and then you have 20-25 mins for status update and goals11:06
bauzasand (again), do we have a good confidence on the fact we would get selected ?11:06
SergeyLukjanovthat's enough to talk about nova :)11:06
bauzasSergeyLukjanov: well, OK11:06
SergeyLukjanovbauzas, what does you mean? "do we have a good confidence on the fact we would get selected ?"11:06
bauzasSergeyLukjanov: I also know about Operations, this track is really overloaded11:06
DinaBelovabauzas, SergeyLukjanov, I suppose we may have one theoretical talk if it would be no time for demo + unconference demo11:06
bauzasif we put all our chances into one ticket, is it a winning ticket ?11:06
DinaBelovabauzas, nobody can be sure here...11:07
DinaBelovaeven with two ones11:07
DinaBelovacause here community votes...11:07
bauzasDinaBelova: that's the only reason why I think that 2 is better than 1, because you have 2 chances11:07
SergeyLukjanovbauzas, IMO it'll have more chances than several topics, but it just my thoughts ;)11:07
bauzaswell, I'm torn11:07
bauzasthat's like betting at poker11:08
DinaBelovathey can give more votes to one than two with more probability, than with two looking like each other topics11:08
DinaBelovacause when people see two looking like each other talks with same Climate name in it11:08
bauzasDinaBelova: SergeyLukjanov: well, OK, I'm really a bad poker player11:08
DinaBelovaI think they'll choose11:08
DinaBelova:D11:08
bauzasDinaBelova: SergeyLukjanov: OK for putting all our eggs into one basket :)11:09
DinaBelovaok, so we're thinking about one really nice talk11:09
DinaBelovaand we'll try to do everything11:09
DinaBelovafor choosing that11:09
DinaBelovaok11:09
bauzasSergeyLukjanov: I really understand your opinion11:10
bauzasDinaBelova: ok, so we need to amend a little bit the talk11:10
bauzasthe abstract sorry11:10
bauzasSergeyLukjanov: if you have chance to review the proposal, that would be great :)11:10
DinaBelovaok, I'll add some info about demo there11:10
SergeyLukjanovbauzas, DinaBelova, I'll take a look later today11:11
DinaBelovabut abstract one - to get rid of it, if there will be no time for it11:11
DinaBelovaok11:11
DinaBelova+ I'll give that link to our marketing group11:11
DinaBelovathey'll take a look on it11:11
SergeyLukjanovyou could always skip the demo if you have no time for it or show short video recording11:11
DinaBelova+111:11
bauzasSergeyLukjanov: yay11:12
bauzasSergeyLukjanov: I like the idea (again), I'm just stressed that's it ;)11:12
bauzasat the moment, we only need to provide an abstract11:12
DinaBelovabauzas, sure11:13
bauzasenough sexy to be elected11:13
DinaBelova:D11:13
bauzasthat's it11:13
bauzasbut yay, I think we need to split our talk into pieces so that we can have enough time and confidence for the talk11:13
bauzasand Q&A11:13
DinaBelovasure, as it should be done anyway :)11:15
*** DinaBelova has quit IRC11:39
*** DinaBelova has joined #openstack-climate11:39
*** SergeyLukjanov has quit IRC11:51
*** SergeyLukjanov has joined #openstack-climate11:55
*** casanch1 has joined #openstack-climate12:48
*** saju_m has quit IRC14:27
*** saju_m has joined #openstack-climate14:29
openstackgerritYuriy Taraday proposed a change to stackforge/climate: Remove direct assignments of context attributes  https://review.openstack.org/7267314:56
openstackgerritChristian Martinez proposed a change to stackforge/climate: Modifying coverage tox.ini configuration  https://review.openstack.org/7267415:11
*** pafuent has joined #openstack-climate15:19
casanch1hi, I have made some comments on the whiteboard of this bp: https://blueprints.launchpad.net/climate/+spec/notifications15:20
casanch1could you please take a look?15:20
bauzascasanch1: sure, will do15:25
bauzasDinaBelova: there is a thread about SolverScheduler I really think you should take a look on it15:26
DinaBelovacasanch1, bauzas - ok15:26
bauzasDinaBelova: because that's talking about reservations...15:26
*** pafuent has left #openstack-climate15:36
*** saju_m has quit IRC15:45
*** saju_m has joined #openstack-climate15:46
*** DinaBelova is now known as DinaBelova_15:51
*** DinaBelova_ is now known as DinaBelova16:43
*** pafuent has joined #openstack-climate16:52
*** bauzas has quit IRC16:58
*** YorikSar has joined #openstack-climate17:38
openstackgerritPablo Andres Fuente proposed a change to stackforge/climate: Initial devstack support implemented  https://review.openstack.org/6046517:40
*** ppetit has quit IRC17:42
*** bauzas has joined #openstack-climate17:46
openstackgerritPablo Andres Fuente proposed a change to stackforge/climate: Initial devstack support implemented  https://review.openstack.org/6046518:19
*** chandan_kumar has quit IRC18:34
*** bauzas has quit IRC18:38
*** pafuent has left #openstack-climate18:48
*** pafuent has joined #openstack-climate19:12
openstackgerritYuriy Taraday proposed a change to stackforge/climate: Remove explicit access to is_admin in context  https://review.openstack.org/7274219:22
openstackgerritYuriy Taraday proposed a change to stackforge/climate: Remove direct assignments of context attributes  https://review.openstack.org/7267319:22
*** bauzas has joined #openstack-climate19:41
*** saju_m has quit IRC19:49
*** saju_m has joined #openstack-climate19:51
*** saju_m has quit IRC20:04
*** saju_m has joined #openstack-climate20:05
openstackgerritYuriy Taraday proposed a change to stackforge/climate: Remove explicit access to is_admin in context  https://review.openstack.org/7274220:17
openstackgerritYuriy Taraday proposed a change to stackforge/climate: Remove direct assignments of context attributes  https://review.openstack.org/7267320:21
*** saju_m has quit IRC20:32
*** DinaBelova is now known as DinaBelova_20:47
*** casanch1 has quit IRC21:11
*** pafuent has left #openstack-climate21:15
*** bauzas has quit IRC23:47

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