Tuesday, 2014-02-04

*** david-lyle has quit IRC00:16
*** david-lyle has joined #openstack-meeting-300:20
*** mikal_ is now known as mikal00:29
*** david_lyle_ has joined #openstack-meeting-300:55
*** gyee has quit IRC00:59
*** david-lyle has quit IRC00:59
*** lblanchard has joined #openstack-meeting-301:12
*** david-lyle has joined #openstack-meeting-301:40
*** david_lyle_ has quit IRC01:44
*** MaxV has joined #openstack-meeting-301:49
*** MaxV has quit IRC01:54
*** david-lyle has quit IRC02:29
*** lblanchard has quit IRC02:42
*** MaxV has joined #openstack-meeting-302:50
*** MaxV has quit IRC02:54
*** jpomero has quit IRC03:49
*** MaxV has joined #openstack-meeting-303:51
*** MaxV has quit IRC03:55
*** david-lyle has joined #openstack-meeting-303:57
*** troytoman is now known as troytoman-away04:03
*** MaxV has joined #openstack-meeting-304:51
*** MaxV has quit IRC04:56
*** DinaBelova_ is now known as DinaBelova05:04
*** amotoki has joined #openstack-meeting-305:22
*** jcoufal has joined #openstack-meeting-306:04
*** d0ugal has quit IRC06:38
*** d0ugal has joined #openstack-meeting-306:45
*** d0ugal has quit IRC06:45
*** d0ugal has joined #openstack-meeting-306:45
*** saju_m has joined #openstack-meeting-307:12
*** lcheng_ has joined #openstack-meeting-307:16
*** mrunge has joined #openstack-meeting-307:31
*** MaxV has joined #openstack-meeting-307:41
*** lcheng_ has quit IRC07:47
*** MaxV has quit IRC07:50
*** jtomasek has joined #openstack-meeting-308:22
*** MaxV has joined #openstack-meeting-308:52
*** lsmola has joined #openstack-meeting-308:56
*** MaxV has quit IRC09:30
*** MaxV has joined #openstack-meeting-309:31
*** d0ugal has quit IRC10:29
*** d0ugal has joined #openstack-meeting-310:32
*** d0ugal has quit IRC10:32
*** d0ugal has joined #openstack-meeting-310:32
*** DinaBelova is now known as DinaBelova_11:01
*** DinaBelova_ is now known as DinaBelova11:02
*** DinaBelova is now known as DinaBelova_11:10
*** MaxV has quit IRC11:10
*** MaxV has joined #openstack-meeting-311:23
*** jcoufal has quit IRC11:26
*** david-lyle has quit IRC11:29
*** amotoki has quit IRC11:38
*** amotoki has joined #openstack-meeting-311:38
*** DinaBelova_ is now known as DinaBelova12:38
*** DinaBelova is now known as DinaBelova_12:52
*** tmazur has joined #openstack-meeting-312:54
*** DinaBelova_ is now known as DinaBelova12:55
*** DinaBelova is now known as DinaBelova_12:55
*** DinaBelova_ is now known as DinaBelova13:01
*** DinaBelova is now known as DinaBelova_13:10
*** jcoufal has joined #openstack-meeting-313:21
*** saju_m has quit IRC13:41
*** lsmola has quit IRC14:05
*** lblanchard has joined #openstack-meeting-314:20
*** lsmola has joined #openstack-meeting-314:22
*** amotoki has quit IRC14:35
*** lsmola has quit IRC14:41
*** lsmola has joined #openstack-meeting-314:53
*** DinaBelova_ is now known as DinaBelova14:54
*** bauzas has joined #openstack-meeting-314:59
bauzasHorizon folks, is your meeting ended ?15:00
DinaBelovathey really have meeting after15:01
DinaBelovaI may try to start meeting15:01
DinaBelovabauzas, let's try? :)15:01
bauzasok with it15:01
DinaBelova#startmeeting climate15:02
openstackMeeting started Tue Feb  4 15:02:01 2014 UTC and is due to finish in 60 minutes.  The chair is DinaBelova. Information about MeetBot at http://wiki.debian.org/MeetBot.15:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:02
*** openstack changes topic to " (Meeting topic: climate)"15:02
openstackThe meeting name has been set to 'climate'15:02
bauzaswoooow15:02
DinaBelovaok, it seems like everything is ok :)15:02
DinaBelovao/15:02
bauzasso15:02
bauzaso/15:02
DinaBelovaI think we may be lonely here today :)15:02
bauzasscroiset won't be able to attend, still somewhere in between Belgium and France :)15:02
DinaBelovaSwann and Nick cannot take part today15:03
DinaBelovayep15:03
bauzasNick as well15:03
*** MaxV has quit IRC15:03
bauzaswell, Sergey too15:03
bauzasthere is maybe a chance to get frossigneux15:03
bauzasdunno15:03
DinaBelovaSergey may join us, but in 10 mins15:03
DinaBelovabauzas, I suppose we may start with several beginning topics15:04
bauzaswell, ok15:05
DinaBelovanot to waste time15:05
bauzasput the agenda15:05
DinaBelovaok, today's agenda is15:05
DinaBelova#link https://wiki.openstack.org/wiki/Meetings/Climate15:05
*** lsmola has quit IRC15:05
DinaBelovaas usual, we start with action items from last meeting15:05
DinaBelova#topic Action items from the last meeting + reviews queries15:06
*** openstack changes topic to "Action items from the last meeting + reviews queries (Meeting topic: climate)"15:06
DinaBelova#link http://eavesdrop.openstack.org/meetings/climate/2014/climate.2014-01-24-15.01.html15:06
DinaBelovaNick sent mail to novaclient guys15:06
DinaBelovabut they seem not react15:06
bauzasyup15:06
bauzasanyway, the urgency of the issue decreased as we found a workaround15:07
DinaBelovaas for reviews15:07
DinaBelovawe actually have really nice picture15:07
DinaBelovafinally :)15:07
DinaBelova#link https://launchpad.net/climate/+milestone/0.1.015:07
bauzasyup !15:07
DinaBelovaall is fixed/implemented15:07
DinaBelovaso we may go to the next topic :)15:07
bauzassure :)15:07
DinaBelova#topic Climate 0.1.015:08
*** openstack changes topic to "Climate 0.1.0 (Meeting topic: climate)"15:08
DinaBelovaokay15:08
DinaBelovaAfter this meeting15:08
DinaBelovaI'm planning to tag our first release :)15:08
DinaBelovayay :)15:08
bauzasgreat !15:08
DinaBelovaSo we'll be the happiest ones :)15:09
SergeyLukjanovhey15:09
SergeyLukjanovI'm here15:09
SergeyLukjanovo/15:09
DinaBelovao/15:09
SergeyLukjanovpartially crazy, partially sleepy :)15:09
DinaBelovaSergeyLukjanov, nice to see you here :)15:09
bauzas:-)15:09
DinaBelovaAnd I'm proud we completed all things we wanted for 0.115:09
bauzaswell, that's what we call the 'beer effect' ;)15:09
bauzascool15:09
DinaBelovaSo let's move on :)15:10
bauzasso, what's the action for you ? :D15:10
SergeyLukjanovbauzas, I think that it's a flight effect - 3 flights from Brussels to Saratov ;)15:10
DinaBelova#action DinaBelova Release 0.1 :)15:10
bauzas:)15:10
bauzason Launchpad15:10
DinaBelovathat's included :)15:11
bauzasbtw, that's not the point here, but I would love knowing how to do it :)15:11
DinaBelovatags + tarball + implemented -> fix released on Launchpad15:11
bauzaslet's discuss it on the channel15:11
bauzasafter the meeting15:11
DinaBelovain proper way or how we need to do that?15:11
DinaBelovaok15:11
bauzascool15:11
DinaBelovaso next topic15:11
DinaBelova#topic Future plans/status for 0.1.1 & 0.2 (https://etherpad.openstack.org/p/climate-0.2)15:11
*** openstack changes topic to "Future plans/status for 0.1.1 & 0.2 (https://etherpad.openstack.org/p/climate-0.2) (Meeting topic: climate)"15:11
bauzasI just created a dependency on a 0.1.1 task15:12
DinaBelova#link https://launchpad.net/climate/+milestone/0.1.115:12
bauzashttps://blueprints.launchpad.net/climate/+spec/hosts-api-docs15:12
DinaBelovayep, good idea15:12
DinaBelovacause I can't finish Wiki15:12
DinaBelovawithout that pat, really15:12
DinaBelovaalso I may mention15:12
DinaBelovathat while we were fighting 0.115:13
bauzasthe idea is to leave WSME generating our docs15:13
bauzasyup ?15:13
DinaBelovalots of tasks for 0.1.1 have been started15:13
DinaBelovaI meant :)15:13
DinaBelovaas for this dependency15:13
DinaBelovaI dunno really how WSME is doing that15:14
DinaBelovabut if it's good why not15:14
bauzasthat's basically a decorator :)15:14
DinaBelovaI only love nice tables in docs like here https://wiki.openstack.org/wiki/Climate/REST_API15:14
DinaBelovabut anyway, for wiki that docs might be modified15:15
bauzashttp://pythonhosted.org//WSME/document.html15:15
DinaBelovaok, thanks15:15
DinaBelovawill take a look15:15
DinaBelovaalso I'm almost done with our docs ^^_^15:15
DinaBelovahttps://wiki.openstack.org/wiki/Climate15:15
*** MaxV has joined #openstack-meeting-315:16
DinaBelova^_^15:16
bauzasyup, saw it :)15:16
DinaBelovawith links to small installation guide and rest api docs :)15:16
DinaBelovaI'm haaaappyyyy :)15:16
DinaBelovaso now we can give link to it15:16
DinaBelovaAs for 0.215:17
DinaBelovahttps://etherpad.openstack.org/p/climate-0.215:17
DinaBelova#link https://etherpad.openstack.org/p/climate-0.215:17
DinaBelovaI think we've accumulated almost all cool ideas for that15:17
DinaBelovaso I'm planning to move some of them to BPs15:18
DinaBelovaat least check if we need some to be created15:18
*** lsmola has joined #openstack-meeting-315:18
DinaBelova#action DinaBelova create BPs for 0.2 (and check existing ones)15:18
DinaBelova#info main focus for 0.2 I believe will be preparing for incubation15:19
bauzassure :)15:19
DinaBelovaand in parallel we'll work on summit topics together15:20
DinaBelova:)15:20
DinaBelovanext topic? :)15:20
DinaBelova#topic Possibly new name for Climate ('climate' repos already exist on PyPi and rtfd) (https://etherpad.openstack.org/p/climate-new-name)15:20
*** openstack changes topic to "Possibly new name for Climate ('climate' repos already exist on PyPi and rtfd) (https://etherpad.openstack.org/p/climate-new-name) (Meeting topic: climate)"15:20
bauzasthat's something quite necessary but painful15:21
DinaBelovaa-a-a-and some ba-a-a-a-ad news one more time15:21
DinaBelovayes15:21
bauzasthat said, we are not enough today for voting15:21
DinaBelova#info we need to start working on new name for Climate15:21
DinaBelovayes15:21
DinaBelovaand also15:22
bauzasmaybe let's communicate it first thanks to the ML15:22
DinaBelovawe NEED that really15:22
bauzasand ask for ideas15:22
*** MaxV has quit IRC15:22
DinaBelovayep15:22
DinaBelovaI suggest to use that Etherpad15:22
bauzasso that we could vote afterwards15:22
DinaBelova#link https://etherpad.openstack.org/p/climate-new-name15:22
bauzaswell, OK15:22
DinaBelovato accumulate ideas15:22
DinaBelovaand then use voting mechanism15:22
DinaBelovato decide what to use15:22
bauzaswe could use the CIVS system15:23
bauzasthat would be fair enough15:23
DinaBelovaor use #_vote here15:23
*** MaxV has joined #openstack-meeting-315:23
SergeyLukjanovyou should start from etherpads with several weeks to make folks able to propose names15:23
SergeyLukjanovand then probably you will have <=1 options :)15:24
bauzas+115:24
DinaBelova#info new name might be synthetic one not to intersect with existing repos/trademarks15:24
DinaBelova+!15:24
DinaBelova+1 :)15:24
DinaBelovaSpeaking about synthetic names I remember new cars namings15:25
DinaBelovaalmost all of them are really strange :)15:25
DinaBelovabecause all normal words are already in use :)15:25
bauzaswell, some of them are actually funny15:26
DinaBelovaNext meeting is this week, so I think we should spend one more week to accumulate ideas for the new name15:26
bauzasI could give some explanations on a few later on :D15:26
DinaBelova:D15:26
DinaBelovaok15:26
DinaBelovaa-a-and the next topic15:26
DinaBelova#topic Open discussion15:27
*** openstack changes topic to "Open discussion (Meeting topic: climate)"15:27
bauzaswell, nothing to say specific15:27
DinaBelovaI think we have not much topics to discuss too15:27
DinaBelovaso we may say goodbye :)15:27
bauzasoh yep15:27
bauzasI got one15:27
DinaBelovaAnd I'll go and release Climate :)15:27
DinaBelova?15:27
DinaBelovasure15:27
bauzasPecan/WSME is currently having 'future' as scoped15:27
bauzasyou ok with moving to 0.1.1?15:28
DinaBelovaIf it's almost done, as I understand, yep - sure15:28
DinaBelova:)15:28
bauzasok cool15:28
DinaBelovaalso next meeting (that will be this week) we should discuss scope for 0.1.1 and 0.215:29
bauzasthe missing steps are bugfixing, docstrings and unittests15:29
DinaBelovaand focus on dates also15:29
DinaBelovayes15:29
bauzasyup agree15:29
DinaBelova#agreed discuss next meeting scope for 0.1.1 and 0.2 and their dates15:29
DinaBelovaI think that's it :)15:30
bauzasok bye15:30
DinaBelovabauzas, SergeyLukjanov any other quesitons?15:30
bauzasnope15:30
DinaBelovaoh, ok15:30
DinaBelova#endmeeting15:30
*** openstack changes topic to "Free for all (Meeting topic: Horizon)"15:30
openstackMeeting ended Tue Feb  4 15:30:33 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/climate/2014/climate.2014-02-04-15.02.html15:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/climate/2014/climate.2014-02-04-15.02.txt15:30
openstackLog:            http://eavesdrop.openstack.org/meetings/climate/2014/climate.2014-02-04-15.02.log.html15:30
*** david-lyle has joined #openstack-meeting-315:34
*** akrivoka has joined #openstack-meeting-315:39
*** troytoman-away is now known as troytoman15:41
*** troytoman is now known as troytoman-away15:41
*** troytoman-away is now known as troytoman15:42
*** troytoman is now known as troytoman-away15:43
*** jpich has joined #openstack-meeting-315:47
*** DinaBelova is now known as DinaBelova_15:51
*** amotoki has joined #openstack-meeting-315:53
*** DinaBelova_ is now known as DinaBelova15:53
*** bdehamer has joined #openstack-meeting-315:56
*** Gaston_Severina has joined #openstack-meeting-315:57
*** doug-fish2 has joined #openstack-meeting-315:57
*** jpomero has joined #openstack-meeting-315:58
*** lcheng has joined #openstack-meeting-315:59
david-lyle#startmeeting Horizon16:01
openstackMeeting started Tue Feb  4 16:01:06 2014 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.16:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:01
*** openstack changes topic to " (Meeting topic: Horizon)"16:01
openstackThe meeting name has been set to 'horizon'16:01
david-lyleHello everyone16:01
lblanchardhi all16:01
tmazurhello o/16:01
akrivokahi everyone16:01
*** xazel has joined #openstack-meeting-316:01
*** Gaston_Severina has quit IRC16:01
amotokihi16:01
doug-fish2greetings16:01
mrungehey16:01
xazelhey16:01
*** xazel is now known as enykeev16:02
lchenghello16:02
david-lyleThe only general item I have today is that the gate is in great shape right now, so let's merge some patches before anything changes :)16:03
jcoufalo/16:03
akrivokaawesome :)16:03
david-lyle#topic https://launchpad.net/horizon/+milestone/icehouse-316:03
*** openstack changes topic to "https://launchpad.net/horizon/+milestone/icehouse-3 (Meeting topic: Horizon)"16:04
jomarahello!16:04
jristo/16:04
*** tzumainn has joined #openstack-meeting-316:04
david-lylelots of bps up for review right now.16:04
*** GastonSeverina has joined #openstack-meeting-316:04
david-lyleI think we're looking all right heading into a soft-freeze on Feb 1816:05
david-lylethe RBAC support is still making progress16:05
jpichdavid-lyle: I started testing the navigation patch, very nice!16:06
doug-fish2david-lyle - can you share briefly what you mean by "soft-freeze"?  What things should we start excluding on the 18th?16:06
david-lylejpich: my css could use some help :)16:06
david-lyletaking another pass16:06
david-lyledoug-fish2: The service teams try to not consider anything that is not up for review by Feb 18 (this releases arbitrary deadline)16:07
doug-fish2ok that helps.  thanks!16:08
david-lyleI've stated before that I would be open to exceptions beyond that on a case by case basis16:08
doug-fish2david-lyle - would that include bugs?  or are you thinking of blueprints?16:08
david-lylejust bps16:08
doug-fish2k great.16:08
david-lylebug fixes are outside of that16:08
amotokii see. "soft-freeze" means Feature proposed deadline.16:08
david-lyleamotoki: yes, but with the code16:08
david-lylewe'll always fix bugs16:09
jpichuntil there aren't any left16:09
doug-fish2:-)16:09
jpich... :-)16:10
david-lyleonce we hit March 5, the cut off for icehouse-3, there is a more formal feature exception process that can be utilized if we have to, but it would be nice to get things in order without resorting to that16:10
david-lylebug fixes still happen then too during the release candidate phases16:10
doug-fish2do we have any concept of fixing only high priority bugs during RC phases?16:11
david-lyleI'm working on one bp that I haven't added to the i-3 list yet, a smaller pass at a bigger RBAC item, and that's pulling out the identity dashboard with RBAC on the data loading as well16:11
*** peristeri has joined #openstack-meeting-316:12
jpichdoug-fish2: Yes. There's a stabilisation period between feature freeze and the first RC though16:12
david-lyleso look for that today or tomorrow as well16:12
david-lyleamotoki: are you able to handle the translation patches again?16:13
david-lyleas we near the end16:13
amotokidavid-lyle: no. daisy is porposing jenkins job patch, but she is in chinese vacation.16:13
david-lyleok, so it will be automated this time around?16:13
jpichThe patch: https://review.openstack.org/#/c/68042/16:14
amotokii hope so.16:14
jpichHopefully16:14
david-lyle+116:14
david-lyleok, I'll keep an eye on that, thanks16:14
david-lyleI have a couple of patches pending in django_openstack_auth that I would like to roll into a release before i-316:15
david-lyleone fixes keystone v3 auth issues16:15
david-lylehttps://review.openstack.org/#/c/70479/16:15
david-lyleas well as moves the default API version to v3 as v2.0 is now deprecated16:16
david-lylethe seconds is around django 1.6 support finalization https://review.openstack.org/#/c/70798/16:16
david-lylebut that will require an openstack/requirements change16:17
david-lyleis there any reason not to allow Django 1.6 at this point in Horizon16:17
david-lyleI think this needs to be in for icehouse16:17
jpichWe'll probably want a tox django 1.5 job in Horizon too (or is there a patch up for this already?)16:18
david-lylejpich: I plan on posting one, but it will fail until the requirements patch lands (which I need to post too)16:18
jpichdavid-lyle: I think it shouldn't fail since we already have access to django 1.5, it would simply duplicate the main test job for now?16:19
david-lylejpich: I see, we could do that separately sure16:19
david-lyleand follow on with the requirements bump16:20
david-lylesure I'll do that16:20
david-lylethose were my main concerns around i-3, anyone else? before we jump to Open16:21
jpichNo strong preference from me either way as long as we Test All The Things eventually :-) Thanks david-lyle, let me know if I can help with something around this16:21
david-lylejpich: thanks, will do16:21
david-lyleAh, I do have one more i-3 item...16:22
david-lylethe bootstrap update bp https://blueprints.launchpad.net/horizon/+spec/bootstrap-update16:23
david-lyleThere is currently a patch pending on openstack/requirements to bump the lesscpy version to theoretically support this, I have not tested yet, but enykeev does not think it's anywhere close16:23
david-lyleso this bp may be completely blocked until Juno16:24
david-lyleenykeev: do you have more you would like to add16:24
david-lyleI think we're going to have at least a session around less/css path forward at the summit in Atlanta16:26
david-lyle#topic Open Discussion16:26
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"16:26
enykeevno, except that i tried to run less.js tests on lesscpy and results were unpleasant. Even if author would be able to make it build, there are probably a bunch of small bugs16:26
enykeevlink on results is in bp16:27
*** absubram has joined #openstack-meeting-316:27
david-lyleenykeev: thanks, seems like we're further away than we thought16:27
* tshirtman waves16:28
absubramhi.. sorry am a bit late.. are we in open discussion?16:29
david-lyleyeah, go ahead16:29
absubramah ko.. just going through the minutes from earlier on in today's meeting.. see the Feb-18th deadline for BPs16:29
absubramthis is not mine.. but just wanted to bring this up16:29
absubramhttps://blueprints.launchpad.net/horizon/+spec/neutron-subnet-mode-support16:29
absubramone of my teammates at work brought it up16:30
absubramI'm new to it myself..16:30
absubramthere aren't any details at all.. just looking at it16:30
absubrambut I can help scope out what's there and add stuff into the whiteboard for it16:30
david-lyleabsubram: that would be great.  At this point it seems unlikely for icehouse as no one has picked it up.16:31
absubramlooks like there's new IPV6 additions in neutron and they want to reflect those in HOrizon16:31
amotokiIf it is a small one, it can be handled as a bug. IPv6 support is one of the important topics in neutron.16:31
absubramright.. that's what I was afraid of and mentioned as much16:31
jpichIt doesn't look like it's implemented fully in Neutron yet either16:31
jristjtomasek: do you need help with the bootstrap conversion?16:31
absubrambut I'll try to add details to the BP at any rate..16:31
absubramno it's not..16:32
absubramthey're still working on it16:32
amotokiabsubram: can you break down the working items? adding subnet mode is just small but IPv6 support is not small.16:32
david-lylethat's late for us to support coming in at the end of i-316:32
absubramamotoki: will do.. will try to add that in within the next day or so16:33
david-lylesmall pieces could be handled in bugs as amotoki said16:33
absubramok.. at this point I'm not exactly sure what is involved16:33
david-lylebut larger scale changes for items landing in i-3 are difficult16:33
absubramI'll bring it back up when I find out more16:33
absubramdavid-lyle: got it16:33
amotokiI don't have much experince on IPv6, so I would like to kwow what we need to support IPv6.16:33
david-lyleabsubram: I appreciate you looking into it16:33
amotokiit helps horizon folks understand if it is big or small :-)16:34
absubramdavid-lyle: np.. we decided last minute we needed this done haha16:34
absubramamotoki: yep.. understand and agree16:34
jomaradavid-lyle: i wanted to modify priority on a couple of the heat BPs - i think topology should be bumped down, and the remaining ones should be bumped up16:35
david-lylejomara: looking16:35
david-lyleso the validation goes down?16:36
jomaradavid-lyle: the topology one is a lot "fluffier" than the others16:36
jomaravalidation?16:36
jomaraone sec16:36
jomaraill give you the exact names16:36
david-lylethat would help, there are several16:36
jomara+ heat-stack-detail-resources-column  , +  heat-fix-status-column , +  heat-stack-list-paging,  -  heat-topology-improvements16:37
absubramumm additionally.. if there's still time.. on a different issue,.. I'm having a little difficulty figuring out the horizon.membership.js file.. I'll send out an email to the mailer so it can be answered easier.. but was just hoping to figure out how some of the code works in generating the drop down for the member/roles16:37
jomaraabsubram: check out the patch in review for the angularization of that code16:38
jomaraits quite a bit simpler16:38
absubramI need to do something simlar but not exactly the same.. I'm trying to add a drop down with a list of profiles for each network at the time of launching an instance.. but my js just doesn't seem to work :(.. would appreciate a different pair of eyes16:38
jomarai woudl recommend you write an angular directive16:38
absubramjomara: thanks.. can you give me a pointer to the patch in review please?16:39
*** lsmola has quit IRC16:39
jomaraabsubram: yeah one sec16:39
jomarahttps://review.openstack.org/#/c/57456/16:39
absubramjomara: thanks a bunch!16:40
david-lyleon a general note regarding blueprints, when linking a commit to a blueprint, the blueprint name is the last part of the URL when on that blueprint's page, otherwise, the linking does not happen and is very hard to track.16:40
david-lyles/on/one16:40
david-lylejomara: all the bps you want bumped are on target for i-3?16:41
david-lyleor just raised in priority for any release?16:41
jomaradavid-lyle: yeah, but i would suggest topology is questionable16:41
jomaraits less specific and thus could fill up a lot more time16:41
jpichIt's usually ok to start small and have the rest as future bp / bugs for enhancements too (<- as a reply to review comments that try to expand the scope ;))16:42
david-lylejomara: the topology is not slated for icehouse, I think we're ok16:42
jomaradavid-lyle: oh, cool :)16:43
jomaradavid-lyle: the rest should be in based on my timeline, though16:43
david-lylejomara: that's great.  Thanks.  I think those will be great improvements/additions16:43
jomaranp!16:44
david-lylejpich: the integration tests are still WIP is that correct?16:45
lchenghi jomara, I'm planning to work on adding RBAC for heat. Can I bug you later for the devstack config? :-)16:45
jpichdavid-lyle: The test runner theoretically could stand on its own, there's just no useful tests at the moment still16:46
jomaralcheng: certainly! i have a working heat on devstack right now16:46
lchengjomara: cool, will ping you later.16:46
*** SergeyLukjanov is now known as SergeyLukjanov_a16:46
david-lylejpich: ok, just checking16:46
david-lylewe could do it in pieces as well16:47
david-lyleup to you16:47
jpichdavid-lyle: I think so - get the general test running infrastructure in place then add tests forever more16:47
david-lylemakes sense16:47
jpichdavid-lyle: I would have liked to showcase a few tests that use the pattern we want to use (Page Object pattern) first - but if there's no progress on that front I'll work on getting the infra pieces well sorted first16:48
david-lylejpich: sure, I agree some sanity tests would help, but let's not miss icehouse because of it :)16:49
jpichYup! Initial piece at https://review.openstack.org/#/c/66012/ if anyone wants to take a peek16:50
david-lylethanks!16:51
*** lsmola has joined #openstack-meeting-316:51
david-lyleany one have anything else?16:51
akrivokaone thing that's been coming up a lot lately is inclusion of exception error message in the user facing UI16:52
david-lylesure16:52
akrivokae.g. https://review.openstack.org/#/c/62026/ https://review.openstack.org/#/c/70158/16:52
akrivokabasically, people have tried to improve a vague error mesage by including exception details16:52
akrivokaespecially for new contributors, that approach seems intuitively like a valid solution (I've been guilty of that myself)16:53
akrivokaI wonder if we should make an faq entry in the docs about it, so that we can refer people to it when it comes up16:54
akrivokaor maybe add a paragraph about it here http://docs.openstack.org/developer/horizon/ref/exceptions.html16:54
akrivokato explain why it's a bad idea, etc16:54
david-lyleakrivoka: that's a great idea16:54
akrivokajust wanted to throw it out there and see if you guys have a better idea16:55
jpichI don't think this page is meant to be blank16:55
lblanchardakrivoka: +1 I think making this error messages clear to users is a huge improvement16:55
david-lylejpich: oops16:55
* jpich files a new bug16:55
amotokiregarding error message, personally it is okay to include an error messge from backend services to error message to horizon. it is done in several places already.16:56
david-lylewe may want to look into that a bit :)16:56
david-lyleamotoki: depends on your audience16:56
doug-fish2I can't sort out the concern/question around this yet:  are we talking about getting back translated/displayable error messages from the services when they fail (which would be great), or are we talking about dumping exception details (which is not so great)?16:56
akrivokaamotoki: it's been discussed extensively, and the consensus is it is not secure or user friendly to do that16:56
tshirtmani think one way to improve things could be to separate "human readable" and "technical" info in errors, and horizon could only show the human readable part by default16:57
akrivokahttp://lists.openstack.org/pipermail/openstack/2014-January/004651.html16:57
david-lylelanguages read, understanding of the technology stack.  Essentially we could be sending them "PC LOAD LETTER"16:57
tshirtmanbecause users don't read a message if it contains cryptic parts, even if the beggining is perfectly readable16:57
lblancharddavid-lyle: lol16:57
david-lyleThe proper approach is to capture the errors and display a translated and rational message related to the error encountered16:58
lblanchardCould we translate the messages to be user friendly? E.g: "This instance couldn't be created since it requires 2GB of RAM and your quota is 1GB"?16:58
doug-fish2david-lyle: are you saying that should happen in Horizon?16:58
amotokiI agree the general concern, but it is case by case.16:58
amotokiIMO translation related issue should be addressed separately.16:58
tshirtmanso horizon has to know about all the potential errors in all openstack projects?16:59
tshirtmanto translate them smartly16:59
doug-fish2tshirtman, yeah that's my concern16:59
doug-fish2especially with an extensible architecture, I think that's impossible.16:59
david-lyleSure, it's not scalable, which is why we have generic messages and logging at this point16:59
tshirtmanyep16:59
peristeridavid-lyle to capture and display human readable messages we should stop using Exception and use the Exceptions classes provided by the API.17:00
tshirtmani think the generic messages should be formed of an human, and a technical part17:00
lblanchardMaybe we could push on having a standardized error message format which includes a human readable piece?17:00
tshirtmanbut i guess convincing all the other projects may not be easy ^^17:00
tshirtmanlblanchard: +#17:00
tshirtmanlblanchard: +1*17:00
jpichBtw while working on Cinder v2 I noticed projects are starting to add "Accept-Locale" to the clients and APIs - so we are going toward becoming able to get error messages in the correct locale17:00
amotokiI think error message from backend projects should be human friendly because they are visible through CLI too.17:01
tshirtmanjpich: oh, that sounds good :)17:01
david-lyleCLI users aren't human :)17:01
lblanchardlol17:01
akrivokadavid-lyle: lol :)17:01
jpichhttps://github.com/openstack/cinder/commit/681a898101f81dbe2317a84e4496bd1e000cf527 (That's Accept-Language, sorry)17:02
tshirtmanif they weren't they wouldn't need error messages at all :P17:02
*** jcoufal_ has joined #openstack-meeting-317:02
*** jcoufal has quit IRC17:02
jpichWe're over time...17:02
david-lyleamotoki: but yes I agree, if we get usable strings back we'll have to make sure they are not harmful and we can display them.17:03
david-lyleThe solution may find us17:03
david-lylejpich: ack17:03
jpich:-)17:03
david-lyleThanks everyone!17:03
amotokiUsing Accept-Language in API calls raises another problem. we still want english log messages....17:03
lblanchardthanks all!!17:03
david-lyle#endmeeting17:03
*** openstack changes topic to "Free for all (Meeting topic: Horizon)"17:03
akrivokathanks!17:03
openstackMeeting ended Tue Feb  4 17:03:47 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-02-04-16.01.html17:03
amotokithanks all!17:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-02-04-16.01.txt17:03
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-02-04-16.01.log.html17:03
absubramthanks!17:03
jpichThanks!17:04
david-lylelblanchard: good point, potentially another summit topic17:04
jristthanks17:04
jomarathanks everyone17:04
tshirtmanthanks :)17:05
*** JLStaude has joined #openstack-meeting-317:08
*** JLStaude has left #openstack-meeting-317:08
*** GastonSeverina has quit IRC17:21
*** mrunge has quit IRC17:21
*** ftcjeff has joined #openstack-meeting-317:21
*** GastonSeverina has joined #openstack-meeting-317:21
*** bauzas has quit IRC17:24
*** bdehamer has quit IRC17:25
*** amotoki has quit IRC17:34
*** GastonSeverina has quit IRC17:34
*** jrist has quit IRC17:35
*** tshirtma1 has joined #openstack-meeting-317:45
*** tshirtman has quit IRC17:46
*** MaxV has quit IRC17:47
*** jrist has joined #openstack-meeting-317:48
*** jrist has quit IRC17:56
*** SergeyLukjanov_a is now known as SergeyLukjanov18:05
*** jrist has joined #openstack-meeting-318:09
*** jpich has quit IRC18:40
*** tmazur has quit IRC18:41
*** tzumainn has left #openstack-meeting-318:54
*** dguitarbite has joined #openstack-meeting-319:04
*** jcoufal_ is now known as jcoufal19:06
*** akrivoka has quit IRC19:14
*** dguitarbite has quit IRC19:41
*** jpomero has quit IRC19:57
*** bauzas has joined #openstack-meeting-319:58
*** jtomasek has quit IRC20:00
*** troytoman-away is now known as troytoman20:05
*** troytoman is now known as troytoman-away20:15
*** troytoman-away is now known as troytoman20:22
*** troytoman is now known as troytoman-away20:34
*** troytoman-away is now known as troytoman20:37
*** jrist has quit IRC20:58
*** MaxV has joined #openstack-meeting-321:06
*** absubram has quit IRC21:11
*** jrist has joined #openstack-meeting-321:11
*** DinaBelova is now known as DinaBelova_21:32
*** peristeri has quit IRC21:48
*** troytoman is now known as troytoman-away21:49
*** tshirtma1 is now known as tshirtman21:54
*** lblanchard has quit IRC22:01
*** MaxV has quit IRC22:03
*** MaxV has joined #openstack-meeting-322:03
*** david-lyle has quit IRC22:04
*** MaxV has quit IRC23:23
*** bauzas has quit IRC23:42
*** MaxV has joined #openstack-meeting-323:53

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