Tuesday, 2014-03-18

*** cjelli___ has quit IRC00:05
*** sarob has quit IRC00:06
*** eguz_ has quit IRC00:17
*** julim has joined #openstack-meeting-300:17
*** julim has quit IRC00:24
*** Sukhdev has joined #openstack-meeting-300:27
*** yamahata has joined #openstack-meeting-300:40
*** banix has joined #openstack-meeting-300:41
*** markmcclain has joined #openstack-meeting-300:49
*** alexpilotti has quit IRC00:55
*** yamahata has quit IRC01:03
*** yamahata has joined #openstack-meeting-301:03
*** markmcclain has quit IRC01:16
*** banix has quit IRC01:18
*** banix has joined #openstack-meeting-301:41
*** david-lyle has joined #openstack-meeting-301:42
*** HenryG has joined #openstack-meeting-301:43
*** sarob has joined #openstack-meeting-302:10
*** sarob has quit IRC02:14
*** banix has quit IRC02:15
*** RajeshMohan has quit IRC02:18
*** Sukhdev has quit IRC02:27
*** edhall_ is now known as edhall02:49
*** sarob has joined #openstack-meeting-303:02
*** sarob has quit IRC03:47
*** sarob has joined #openstack-meeting-303:48
*** sarob has quit IRC03:52
*** eghobo has joined #openstack-meeting-303:53
*** eghobo has quit IRC03:57
*** mwagner_lap is now known as mwagner_zzz04:25
*** sarob has joined #openstack-meeting-304:48
*** sarob has quit IRC04:53
*** eghobo has joined #openstack-meeting-304:56
*** sarob has joined #openstack-meeting-304:59
*** sarob has quit IRC05:03
*** sarob has joined #openstack-meeting-305:52
*** sarob has quit IRC05:56
*** tmazur has joined #openstack-meeting-306:05
*** mrunge has joined #openstack-meeting-306:29
*** tmazur has quit IRC06:30
*** tmazur has joined #openstack-meeting-306:43
*** saju_m has joined #openstack-meeting-306:44
*** saju_m has quit IRC06:45
*** saju_m has joined #openstack-meeting-306:46
*** ttrifonov_zZzz is now known as ttrifonov06:50
*** sarob has joined #openstack-meeting-306:53
*** MaxV has joined #openstack-meeting-306:57
*** sarob has quit IRC06:57
*** eghobo has quit IRC07:18
*** ttrifonov is now known as ttrifonov_zZzz07:25
*** lpetrut has joined #openstack-meeting-307:28
*** enikanorov__ has joined #openstack-meeting-307:28
*** MaxV has quit IRC07:29
*** enikanorov_ has quit IRC07:31
*** jcoufal has joined #openstack-meeting-307:42
*** jcoufal has quit IRC07:42
*** jcoufal has joined #openstack-meeting-307:42
*** MaxV has joined #openstack-meeting-307:46
*** sarob has joined #openstack-meeting-307:54
*** jcoufal has quit IRC07:57
*** sarob has quit IRC07:58
*** MaxV has quit IRC07:58
*** jcoufal has joined #openstack-meeting-308:00
*** ttrifonov_zZzz is now known as ttrifonov08:06
*** jtomasek has joined #openstack-meeting-308:13
*** jtomasek has quit IRC08:18
*** jrist has joined #openstack-meeting-308:19
*** jtomasek has joined #openstack-meeting-308:36
*** MaxV has joined #openstack-meeting-308:38
*** saju_m has quit IRC08:50
*** nacim has joined #openstack-meeting-308:51
*** sarob has joined #openstack-meeting-308:54
*** saju_m has joined #openstack-meeting-308:56
*** sarob has quit IRC09:00
*** johnthetubaguy has joined #openstack-meeting-309:17
*** johnthetubaguy has quit IRC09:20
*** johnthetubaguy has joined #openstack-meeting-309:22
*** jtomasek has quit IRC09:23
*** MaxV has quit IRC09:23
*** MaxV has joined #openstack-meeting-309:24
*** jcoufal has quit IRC09:37
*** jcoufal has joined #openstack-meeting-309:39
*** johnthetubaguy1 has joined #openstack-meeting-309:39
*** johnthetubaguy has quit IRC09:41
*** jcoufal has quit IRC09:41
*** jcoufal has joined #openstack-meeting-309:43
*** lpetrut has quit IRC09:49
*** lcheng has joined #openstack-meeting-309:54
*** sarob has joined #openstack-meeting-309:58
*** sarob has quit IRC10:02
*** lcheng has quit IRC10:06
*** lpetrut has joined #openstack-meeting-310:07
*** jcoufal has quit IRC10:16
*** jcoufal has joined #openstack-meeting-310:48
*** yamahata has quit IRC10:49
*** sarob has joined #openstack-meeting-310:59
*** sarob has quit IRC11:05
*** sarob has joined #openstack-meeting-311:08
*** jrist has quit IRC11:10
*** sarob has quit IRC11:12
*** jrist has joined #openstack-meeting-311:24
*** MaxV has quit IRC11:28
*** mwagner_zzz has quit IRC11:35
*** MaxV has joined #openstack-meeting-311:43
*** david-lyle has quit IRC11:46
*** yamahata has joined #openstack-meeting-311:56
*** sarob has joined #openstack-meeting-312:02
*** obondarev1 has joined #openstack-meeting-312:06
*** sarob has quit IRC12:06
*** yamahata_ has quit IRC12:08
*** yamahata_ has joined #openstack-meeting-312:08
*** obondarev has quit IRC12:09
*** mrunge has quit IRC12:09
*** tmazur has quit IRC12:18
*** mrunge has joined #openstack-meeting-312:21
*** tmazur has joined #openstack-meeting-312:39
*** xuhanp has joined #openstack-meeting-312:42
*** jcoufal has quit IRC12:47
*** amotoki has joined #openstack-meeting-312:47
*** markmcclain has joined #openstack-meeting-312:55
*** sarob has joined #openstack-meeting-313:02
*** lblanchard has joined #openstack-meeting-313:05
*** sarob has quit IRC13:08
*** julim has joined #openstack-meeting-313:14
*** jpomero has joined #openstack-meeting-313:17
*** obondarev1 is now known as obondarev13:18
*** lenrow_ has quit IRC13:22
*** peristeri has joined #openstack-meeting-313:29
*** mwagner_lap has joined #openstack-meeting-313:43
*** mfer has joined #openstack-meeting-313:45
*** jtomasek has joined #openstack-meeting-313:58
*** banix has joined #openstack-meeting-313:59
*** jthopkin has joined #openstack-meeting-314:00
*** jrist has quit IRC14:01
*** jtomasek has quit IRC14:04
*** sarob has joined #openstack-meeting-314:04
*** sarob has quit IRC14:09
*** jtomasek has joined #openstack-meeting-314:10
*** mrunge has quit IRC14:12
*** johnthetubaguy1 is now known as johnthetubaguy14:13
*** jrist has joined #openstack-meeting-314:15
*** wchrisj has joined #openstack-meeting-314:21
*** alexpilotti has joined #openstack-meeting-314:22
*** jnoller has joined #openstack-meeting-314:31
*** dguitarbite has quit IRC14:31
*** jnoller has quit IRC14:31
*** jnoller has joined #openstack-meeting-314:32
*** jnoller has quit IRC14:32
*** jnoller has joined #openstack-meeting-314:33
*** jnoller has quit IRC14:33
*** jnoller has joined #openstack-meeting-314:34
*** jnoller has quit IRC14:35
*** jnoller_ has joined #openstack-meeting-314:35
*** jnoller_ has quit IRC14:35
*** david-lyle has joined #openstack-meeting-314:36
*** dguitarbite has joined #openstack-meeting-314:36
*** jnoller has joined #openstack-meeting-314:36
*** jnoller has quit IRC14:36
*** jcoufal has joined #openstack-meeting-314:41
*** coolsvap has joined #openstack-meeting-314:51
*** jnoller has joined #openstack-meeting-315:00
*** mrunge has joined #openstack-meeting-315:04
*** cjellick has joined #openstack-meeting-315:04
*** sarob has joined #openstack-meeting-315:05
*** cjellick has joined #openstack-meeting-315:05
*** cgoncalves has quit IRC15:07
*** cgoncalves has joined #openstack-meeting-315:07
*** sarob has quit IRC15:10
*** saju_m has quit IRC15:23
*** jcoufal has quit IRC15:24
*** xuhanp has quit IRC15:25
*** absubram has joined #openstack-meeting-315:28
*** jcoufal has joined #openstack-meeting-315:29
*** cjellick_ has joined #openstack-meeting-315:36
*** jtomasek has quit IRC15:36
*** cjellick has quit IRC15:36
*** cjellick has joined #openstack-meeting-315:37
*** jrist has quit IRC15:37
*** devlaps has joined #openstack-meeting-315:37
*** yamahata has quit IRC15:39
*** yamahata has joined #openstack-meeting-315:39
*** saju_m has joined #openstack-meeting-315:40
*** jtomasek has joined #openstack-meeting-315:52
*** jrist has joined #openstack-meeting-315:53
*** aleParedes has joined #openstack-meeting-315:56
*** saju_m has quit IRC15:57
*** doug-fish has joined #openstack-meeting-315:59
*** cgoncalves has quit IRC16:00
david-lyle#startmeeting Horizon16:02
openstackMeeting started Tue Mar 18 16:02:03 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:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** openstack changes topic to " (Meeting topic: Horizon)"16:02
openstackThe meeting name has been set to 'horizon'16:02
david-lyleHello everyone16:02
mrungeo/16:02
doug-fishhello16:02
lblanchardhi all16:02
tmazurhello o/16:02
aleParedesHello!16:02
*** cgoncalves has joined #openstack-meeting-316:02
amotokihi, good night16:03
MaxVhi!16:03
absubramhi all16:03
*** cgoncalves has quit IRC16:03
david-lyleLet's dive in16:04
david-lyle#topic Icehouse RC116:04
*** openstack changes topic to "Icehouse RC1 (Meeting topic: Horizon)"16:04
david-lylehttps://launchpad.net/horizon/+milestone/icehouse-rc116:04
*** eghobo has joined #openstack-meeting-316:04
*** cgoncalves has joined #openstack-meeting-316:04
david-lyleso many of you may be getting emails that your bug was moved from rc1 to next16:04
david-lylethis does not mean that it can't go into RC1, it merely means that we can cut RC1 without it16:05
david-lyleThe distinction was pointed out to me this morning16:05
david-lyleso I will continue to prune the bugs down to items that are blockers to cutting the RC1 branch16:06
david-lylequestions on that part?16:06
amotokiWe have two unassinged bugs.16:06
*** sarob has joined #openstack-meeting-316:06
david-lyleyes those are also bad :)16:06
amotokiI can take the fist one. it is related to neutronclient.16:06
doug-fishdavid-lyle - I think the mox import bug that I've been bothing people about should be on that list too16:07
doug-fishother than mentioning it to you know how do we have that discussion?16:07
david-lylecan you post a link?16:07
doug-fishhttps://bugs.launchpad.net/horizon/+bug/128824516:08
amotokihttps://review.openstack.org/#/c/79378/16:08
david-lyleI think that should be in RC116:09
david-lyleI added it16:09
doug-fishthx16:09
david-lyleanything else not on the RC1 list that people feel is essential?16:09
amotokifor bug 1292937, can anyone familiar with ceilometer take a look at it?16:10
amotokiI am not sure it is visible or not.16:10
*** jnoller has quit IRC16:10
*** sarob has quit IRC16:10
*** wchrisj has quit IRC16:11
david-lyleI assigned someone to take a look16:11
*** johnma has joined #openstack-meeting-316:11
david-lyleHe's been working on ceilometer16:11
david-lylein Horizon16:11
*** SumitNaiksatam has quit IRC16:11
david-lyleI have on item in django-openstack-auth that I need to add.  So, I've been pushing to move our default keystone API version to v3.  We merge a patch in django_openstack_auth, turns out that although keystone v2 is deprecated, we can't use a v3 token to do anything other than identity management in Horizon16:13
*** wchrisj_ has joined #openstack-meeting-316:13
*** johnthetubaguy has quit IRC16:13
*** lcheng has joined #openstack-meeting-316:13
david-lyleso I'm going to move the default back to v2 for icehouse and we need to address broader support at the summit16:13
david-lyleI'm tempted to go so far as to disable v3 altogether in Horizon, but I think there may be some groups out there that have hacks in place to make v2 and v3 work16:14
*** johnthetubaguy has joined #openstack-meeting-316:14
david-lyleso I'm going to leave it in, and add documentation for the problem16:15
david-lyleother ideas around that?16:15
jthopkinWill this disable the ability for a user to change their own password?  V3 was required for that right?16:15
david-lyleI'd have to check that v3 is required, but if so then yes16:16
david-lylev3 tokens used to work through a bug in keystoneclient which has since been closed, hence the belief that all was well16:16
mrungeafaik, the own password thing works only on v216:17
mrunge because such a support was forgotten or left out of keystone, but I may be wrong here16:17
lchengagree on mrunge,  it was the other way around.16:18
david-lylechange own password?16:18
lchengthere is a patch on-going to add to add the change password on keystone v3 in keystoneclient16:18
david-lyleI don't think that's supported in either unless you are admin16:18
lchengchange own password16:18
*** jcoufal has quit IRC16:19
lchengdavid-lyle: yes16:19
lchengwhat you said :-)16:19
mrungedavid-lyle, it was supported, but led to the cool situation, that you didn't had to provide your old password. keystone didnd't check, if your old password matched16:19
mrungeso we (I) disabled that *feature* in horizon in that condition.16:20
mrungeneed to check, if it was v2 or v316:21
david-lylemrunge for v3 though, correct?16:21
mrungejust one.16:21
mrungelet me check16:21
david-lylelooking at code, v2 may support user updating password, was looking at wrong api call before16:21
mrungeyou can only set your password on v216:22
mrungehttps://github.com/openstack/horizon/blob/master/openstack_dashboard/dashboards/settings/password/panel.py16:22
mrungel.3116:22
david-lylejthopkin: there we go16:22
jthopkinawesome, thanks all16:22
david-lyleAny other issues regarding RC1?16:23
david-lyleWe did merge 4 of the 6 FFE we had, so that's great16:24
absubram:)16:24
mrungewhat are we doing about the mox thing?16:24
absubramthe IPv6 neutron side got merged late last night.. but it essentially added only the attributes.. but they don't do anything.. so good that we moved the Horizon BP to J16:25
david-lylemrunge: I agree that we should not depend on mox in a non-dev situation16:25
david-lyleI added it to RC116:25
*** Walls has joined #openstack-meeting-316:25
david-lyleamotoki: do you have anything you want to comment on regarding translation and string freeze?16:25
amotokidavid-lyle: I18N need to know the planned date of RC1 .16:26
amotokiI would like to propose the first import before RC1 but i am not sure when it is better to do.16:26
david-lyleamotoki: hmm, I don't know a date, I would imagine we have at least a week16:27
*** nacim has quit IRC16:27
david-lyleI'll work on coming up with a better date16:27
david-lyleor a date ;)16:27
amotokithanks. the first milestone in i18n team is set to Mar 24 but someone needs more time.16:28
david-lyleok, thanks16:29
david-lyle#topic Design Summit Session Topics16:29
*** openstack changes topic to "Design Summit Session Topics (Meeting topic: Horizon)"16:29
david-lylehttp://summit.openstack.org/16:29
david-lyleSo only two topics so far16:29
jthopkinOK, Jacki and I have some ideas.  I'll get those into there as well16:30
david-lyleI have a couple to add: "Node toolchain for development" and "Approach for localized API error messages/logging"16:31
mrungeI'd have some ideas in the queue16:31
david-lylerevisiting the project split might be worth rehashing a bit16:31
amotokiWe have many gaps in CLI and Horizon. IMO we need to list the gaps and prioritize them in Juno. It is not a session proposal but we need to do it as a project.16:31
david-lylesure16:32
mrungebetter error reporting, separate dashboard, and something like messaging support through marconi would be great16:32
tmazuramotoki, great idea!16:32
mrungeamotoki, yes, and that should be a session16:32
david-lyleMy other big topic is "A Launch Instance that makes sense/works"16:32
mrungepaper and pencil session16:32
lblanchardamotoki: +1 I've heard users say they don't use Horizon since they have to switch back and forth to CLI…they say "May as well just stick with CLI for now."16:33
david-lyleamotoki +116:33
lblancharddavid-lyle: :) We have a lot of feedback from the usability tests on that flow…it will probably be a big topic in the session I proposed too…maybe if you propose one it can be a deeper dive into the code discussion?16:33
mrungeah, and support many users? it seems keystone got support for limiting user lists16:34
*** gseverina has joined #openstack-meeting-316:34
mrungesomething like paging support16:34
jthopkinlblanchard: A big request I have heard and we've provided some feedback on is the ability to better do capacity management.  We've been providing feedback to some of the work lblanchard is doing16:34
MaxVdavid-lyle: We are currently working on an implementation of http://ask-openstackux.rhcloud.com/question/12/enhance-the-selection-of-a-flavor-and-an-image/16:34
*** jcoufal has joined #openstack-meeting-316:34
david-lylejthopkin: capacity as in number of controllers?16:35
*** tqtran has joined #openstack-meeting-316:35
david-lylequotas, ?16:35
lblanchardMaxV: It would be awesome if we could track down some users at summit and do some user testing of the work you've done so far16:35
jthopkindavid-lyle: partially but not controllers specifically16:35
jthopkini.e. - who is using all the resources in my cloud and how much hardware will I need in the future16:35
MaxVlblanchard: a patch will be released in a few weeks16:35
amotokiwhat does "capacity management" mean? It may be a part of tuskar-ui.16:36
mrungesounds like heat16:36
jthopkinthere's two pieces to it, but it is better understanding how your cloud is being used16:36
lblanchardMaxV: awesome16:36
david-lyleMaxV: I'll take a look, and thanks16:36
jthopkinthe ceilometer visualization gives some of that, but it needs to be better implemented16:36
lblanchardjthopkin: more on the monitoring side of things, right?16:36
jthopkinyes16:36
david-lyleproblem is OpenStack doesn't have a monitoring solution today16:37
lblanchardmrunge: really…a better way of visualizing how resources are used16:37
david-lyleceilometer is only part of the solution16:37
jthopkindavid-lyle: correct, this wouldn't just be about monitoring (that would be further down the road).  More about how my resources are being used and who is using them16:37
david-lylesure16:38
jthopkinhttp://ask-openstackux.rhcloud.com/question/132/improvements-to-horizon-admin-overview/16:38
*** jrist has quit IRC16:38
*** jtomasek has quit IRC16:38
jthopkinthat is the work lblanchard has been doing and jackibauer has also proposed some alternate concepts16:38
absubramwe are internally doing something similar too.. to monitor the usage of the hardware resources.. still working on development.. was going to being it up at the summit16:39
absubramas amotoki mentioned.. wasn't sure if it is already addressed in Tuskar?16:39
absubrambut would love to learn more about how you guys went about it jthopkin :)16:39
lblanchardjthopkin: are the other concepts somewhere to review?16:39
jthopkinlblanchard: yes, Jacki added them in the comments.  I'll post them here too.  One sec16:40
*** jcoufal has quit IRC16:40
jthopkinhttp://tvpnk4.axshare.com/#p=admin_overview16:40
lblanchardjthopkin: thanks16:40
jthopkinhttp://tvpnk4.axshare.com/#p=admin_overview_-_text16:40
jthopkinhttp://tvpnk4.axshare.com/#p=user_overview16:40
jthopkinhttp://tvpnk4.axshare.com/#p=user_overview_-_text16:40
jthopkinWe'll need to rework them a bit to conform to the Horizon design pattern though16:41
*** akrivoka has joined #openstack-meeting-316:41
david-lyleseems like we have much to talk about :)16:42
david-lyleanyway, submit your session ideas16:42
lblanchardjthopkin: very nice though! Thanks for sharing :)16:42
*** dguitarbite has quit IRC16:42
amotokiIt looks great. Doesn't ceilometer provide such information? If it provides them, all works should be in Horizon side.16:42
*** Walls has quit IRC16:42
jthopkinamotoki: I believe it does, but I'm working on identifying any gaps16:42
MaxVmrunge: what is the status of https://blueprints.launchpad.net/horizon/+spec/separate-horizon-from-dashboard?16:43
david-lyleI think we're here anyway.16:43
david-lyle#topic Open Discussion16:43
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"16:43
amotokiIn the dev list, we heard muranodashboard needs openstack_dashboard release to PyPI.16:44
amotokiCan we push the release to PyPI or should we wait for splitting horizon and dashboard?16:45
david-lyleI think the idea was to autorelease to pypi as a wheel, I'll look into where that is at, otherwise we could probably release it.16:46
david-lyleI think the stance before was not to release any of the openstack services to PyPi16:47
david-lylemostly because just giving someone a nova .tar.gz isn't enough16:47
amotokiI see. only client libs are released to PyPI.16:47
david-lyleHorizon may be a little different in that respect16:47
david-lyleSomething about wheels was supposed to change that policy16:48
david-lylelet me follow up16:48
amotokiI think tarball should work for the case murano team asked.16:48
david-lyleyes, Horizon is a simpler case for sure16:48
absubramamotoki: saw your email response to Radomir and me.. regarding the ip_version in the EditSubnet class.. thanks.. will respond to the thread.. we won't be able to do away with it because we need it for the IPv6 identification and corresponding v6 fields..16:52
amotokiabsubram: thanks for raising it. Such cleanup will be appreciated :)16:53
lblancharddavid-lyle: Should we add Horizon to this list? https://etherpad.openstack.org/p/ATL-ops-dedicated-design-summit-sessions16:53
* david-lyle reading16:54
absubramglad to help :)16:54
*** jcoufal has joined #openstack-meeting-316:55
david-lylelblanchard: absolutely16:55
lblancharddavid-lyle: cool, I will add16:56
david-lylethanks16:57
*** jcoufal has quit IRC16:57
absubramumm just a review request for https://review.openstack.org/#/c/76653/ https://review.openstack.org/#/c/78708/ and https://review.openstack.org/#/c/76787/ please :)16:57
*** gseverina has quit IRC16:58
amotokiregarding string freeze, it is just a soft freeze. Please keep on your eyes if a patch changes strings much or not. I believe small changes does not matter.16:59
absubrammrunge: and others (amotoki) thanks for the approval earlier this morning for the head of my dependency list!.. appreciate it17:00
absubramas you've mentioned.. the above reviews I have do have small string changes..17:00
david-lyleThanks everyone! Have a great week.17:00
david-lyle#endmeeting17:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:00
openstackMeeting ended Tue Mar 18 17:00:53 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-03-18-16.02.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-03-18-16.02.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-03-18-16.02.log.html17:00
absubramthanks!17:01
amotokithanks all!17:01
lblanchardthanks all!17:01
tmazur thanks all!17:01
absubramhave a good week all!..17:01
lchengthanks all!17:01
*** absubram has quit IRC17:02
*** johnma has quit IRC17:02
*** doug-fish has left #openstack-meeting-317:02
*** SumitNaiksatam has joined #openstack-meeting-317:03
*** tqtran has left #openstack-meeting-317:03
aleParedesbye!17:04
*** aleParedes has quit IRC17:04
*** mrunge has quit IRC17:07
*** amotoki has quit IRC17:17
*** devlaps1 has joined #openstack-meeting-317:23
*** devlaps has quit IRC17:24
*** jnoller has joined #openstack-meeting-317:25
*** johnthetubaguy has quit IRC17:27
*** johnthetubaguy has joined #openstack-meeting-317:27
*** jtomasek has joined #openstack-meeting-317:28
*** mrunge has joined #openstack-meeting-317:29
*** MaxV has quit IRC17:38
*** ttrifonov is now known as ttrifonov_zZzz17:39
*** Alex_Gaynor has joined #openstack-meeting-317:43
*** jpomero has quit IRC17:48
*** jnoller has quit IRC17:52
*** lcheng has quit IRC17:57
*** lcheng has joined #openstack-meeting-317:58
*** lcheng has quit IRC17:59
*** lcheng has joined #openstack-meeting-318:00
*** jpomero has joined #openstack-meeting-318:03
*** jnoller has joined #openstack-meeting-318:04
*** akrivoka has quit IRC18:07
*** jnoller has quit IRC18:10
*** lcheng has quit IRC18:13
*** jtomasek has quit IRC18:13
*** lcheng has joined #openstack-meeting-318:14
*** muralia has joined #openstack-meeting-318:20
*** mfer has quit IRC18:20
*** mrunge has quit IRC18:23
*** jtomasek has joined #openstack-meeting-318:24
*** mfer has joined #openstack-meeting-318:25
*** tmazur has quit IRC18:37
*** MaxV has joined #openstack-meeting-318:43
*** johnthetubaguy has quit IRC18:57
*** johnthetubaguy has joined #openstack-meeting-318:57
*** jamielennox has joined #openstack-meeting-318:57
*** dtroyer has joined #openstack-meeting-318:57
*** briancurtin has joined #openstack-meeting-318:58
briancurtin#startmeeting python-openstacksdk19:00
openstackMeeting started Tue Mar 18 19:00:39 2014 UTC and is due to finish in 60 minutes.  The chair is briancurtin. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: python-openstacksdk)"19:00
openstackThe meeting name has been set to 'python_openstacksdk'19:00
briancurtin#link https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK <- agenda19:01
*** bknudson has joined #openstack-meeting-319:01
briancurtinMay as well start with roll call and let everyone file in. Can everyone here for the python-openstacksdk meeting state their name and affiliation?19:01
edleafeEd Leafe, Rackspace19:02
wchrisj_Chris Johnson, HP19:02
dtroyerDean TRoyer, Nebula19:02
Alex_GaynorAlex Gaynor (affiliations: Rackspace, many many others, avialable upon request, lol)19:02
bknudsonBrant Knudson, IBM19:02
briancurtinBrian Curtin, Rackspace19:02
jamielennoxJamie Lennox, Red Hat19:02
briancurtinso i guess the first thing is Alex_Gaynor's review19:03
mferMatt Farina, HP19:03
briancurtin#topic https://review.openstack.org/#/c/79435/19:03
*** openstack changes topic to "https://review.openstack.org/#/c/79435/ (Meeting topic: python-openstacksdk)"19:03
Alex_GaynorWant me to talk about teh current status of it?19:04
briancurtinAlex_Gaynor: sure, go ahead19:04
briancurtini guess the ultimate goal here would be to figure out what the next steps are19:05
Alex_GaynorSo, I think the code is basically don-ish, which is to say I have no more TODOs, and I think I've responde to every review item. It's blocked on requirements integration with the CI stuff.19:05
Alex_GaynorI'm working on getting that unblocked today with the infra/config repos/folks.19:05
*** jpomero has quit IRC19:06
briancurtini agree that it seems to be done-ish. i got beat to a lot of my comments, so i haven't had any specific input on the reviews, but will give it another look19:06
bknudsonendpoints is going to have a function for every type of openstack request?19:06
bknudsonactually a class19:06
Alex_GaynorI think we may eventually find patterns to make that even simpler, but for now, yeah19:07
bknudsondoes this require a versioned endpoint? i.e., http://localhost:5000/v2.0 ?19:07
edleafeSo are we planning on having permutations for every combination of auth? Methods like 'CreateIdentityV2UsernamePasswordTokenRequest' seem like they would lead to copy/paste hell19:08
jamielennoxgiven the early stage we are currently at i'm fine with merging reviews like this until we get to the point we figure out what we need to improve on, there are no compatability issues to deal with yet19:09
wchrisj_Alex_Graynor: where does discovery fit into this approach (endpoints, versioning, etc.)?19:10
wchrisj_Alex_Gaynor: ^^19:10
Alex_GaynorYou're talking about integration with the srvice catalog, or discovery of the properties of teh auth endpiont?19:10
wchrisj_including api version, yes.19:10
wchrisj_that would cut down on those permutations dramatically19:11
Alex_GaynorI'm not sure what the best pattern for that is, I think it's by composing what's in that PR though.19:11
wchrisj_Have you looked at what jamielennox: has done around that?19:11
Alex_GaynorI looked through some of the keystoneclient stuff, yes.19:12
jamielennox(there is a review up now to make keystoneclient discovery a bit more sane and useful)19:12
briancurtinedleafe: can we just have IdentityV2 and have it accept user, pass, token, fancy handshake, whatever, and construct an appropriate request with what's given?19:13
edleafebriancurtin: I would certainly prefer that approach19:13
Alex_GaynorI think it makes sense to compose that on top of what's there, rather than putting it all into one class.19:13
jamielennoxbriancurtin: that can work for v2 because it's largely frozen but it won't extend to v319:13
wchrisj_I'm definitely arguing against putting it all on one class - especially across versions (Identity v2 vs v3), etc.19:14
briancurtinAlex_Gaynor: true19:14
briancurtinand jamielennox thanks for the insight19:14
wchrisj_... actually not arguing ;-)19:15
*** johnthetubaguy has quit IRC19:15
bknudsonwe'll need a CreateIdentityV2UsernamePasswordScopedTokenRequest, too19:16
bknudsonto get a token scoped to a project19:16
jamielennoxbknudson: that can't be a parameter?19:17
bknudsonjamielennox: it could be19:17
bknudsonactually, I'd expect this unscoped token request wouldn't include a catalog?19:18
mferif the design ends up with methods like that we might want to re-think the approach for developer experience19:18
mferi can't imagine using a method like that19:18
*** saju_m has joined #openstack-meeting-319:18
bknudsonmfer: what's the best method you can imagine?19:18
briancurtinmfer: well i think you'd use a higher-level approach to it, like the above mentioned IdentityV2 that takes a bunch of parameters (or something like that)19:19
edleafeOr a config setting19:19
*** lcheng has quit IRC19:19
edleafeA user isn't going to be switching between auth methods all that often19:20
mferi'd likely have an identityv2 object. then i'd auth ot using a username and password.19:20
mferthe goal is to create an sdk for application developers. not to reflect what the API does19:20
edleafemfer +119:20
briancurtinas long as calling IdentityV2(username="briancurtin", password="lol") gets me auth'ed properly, i'm good19:20
Alex_Gaynoryou probably need an auth_url19:21
Alex_Gaynorbut yeah, IdentityV2 is a trivial composition19:21
mferyou might want something like IdentityV2(endpoint)19:21
mferthen from that object you auth19:21
edleafeGenerally things like auth_url, identity version/type, etc., are best left for config settings19:21
mferauthenticate(username="briancurtin", password="lol")19:22
edleafeThe SDK should figure out how to auth based on how it's configured19:22
Alex_GaynorSorry, what config are you talking abotu ed?19:22
jamielennoxedleafe: mixing config files and libraries is tricky - you will still need to expose everything via regular optoins19:22
mferedleafe this isn't an app. config should be managed by the app and passed in19:22
briancurtinyep19:22
edleafeAlex_Gaynor: env vars, for one19:22
bknudsonmaybe you config the library -- openstack.config(auth_endpoint='http://localhost:35357', ...)19:23
*** muralia has quit IRC19:23
edleafejamielennox: everything should be passable, but default to config if not otherwise specified19:23
jamielennoxedleafe: no, you are definetly mixing the responsibilities of a library vs the application19:23
mferedleafe the SDK should not look for env variables. that makes too many assumptions about the app using it. this is a library not an application19:23
edleafethat's just one option19:24
bknudsonthen token, service_catalog = openstack.authenticate(username='user1', password='user1pwd')19:24
briancurtinmfer: quick jump-back, but yes on authenticate(...) as a high-level/end-user approach to be built on top of this IdentityV2BlahBlahBlah19:24
*** muralia has joined #openstack-meeting-319:24
edleafethere are many ways to set a consistent set of settings19:24
*** muralia has quit IRC19:24
*** muralia has joined #openstack-meeting-319:24
mferedleafe across every possible application using an SDK (most of which you can't imagine) on every platform python runs?19:25
*** terrylhowe has joined #openstack-meeting-319:25
mferedleafe this is seaparation of concerns. app config is not hte concern of the sdk19:25
jamielennoxedleafe: it's always possible to do context like objects that can be loaded in various ways - have to see what the api looks like to see how they would work19:25
*** jtomasek has quit IRC19:25
edleafejamielennox: yes. The point is that we should make it simple for the developer19:26
briancurtinsimple for the developer is "pass a URL in"19:27
wchrisj_agreed19:27
mferedleafe simple for a developer to do what? for example, one use case is to authenticate to two different openstack services and copy objects from one to another.19:27
briancurtinif we get into config files, config files not existing, confing files in the wrong place, wrong line endings, wrong encoding, wrong configuration, it's not going to be great19:27
wchrisj_use case: web app developer19:27
edleafemfer: heh, I do that all the time now  ;-)19:28
edleafebut yeah, there will be places where it won't work19:28
mferthis is an SDK/library and not an application. as it was said earlier... separation of concerns19:29
edleafeI'm thinking about the 80-90% of use cases where it will and we will be making the developer's life simpler19:29
mferstoring the config is not the concern of this19:29
jamielennoxthere is advantage to providing standard ways of loading things, ie read this oslo.config file and load up the appropriate auth plugin - however that's a helper function and a  later issue19:29
mferyour low level functionality shouldn't assume that19:30
mferthat's helper stuff19:30
jamielennoxmfer: right19:30
edleafeI'm not trying to settle how configs might be persisted and read in - just making the point that requiring devs to call methods like 'CreateIdentityV2UsernamePasswordTokenRequest()' is not ideal19:30
briancurtinthey're not going to have to19:30
jamielennoxedleafe: i understand that to be an endpoint.py thing and not exposed to the user19:30
mferit's a poor developer experience19:30
bknudsonseems like we don't need to write CreateIdentityV2UsernamePasswordTokenRequest first... let's write/mock the ideal interface.19:31
edleafejamielennox: then requiring devs to know to create an instance of 'IdentityV2UsernamePasswordAuth' is equally unfriendly19:31
briancurtinthey're not going to have to19:31
edleafebriancurtin: what will they be doing, then?19:32
jamielennoxedleafe: depends how you cut it up that equivalent in keystoenclient is keystoneclient.auth.identity.v2.Password - just as long a name but importable in a useful way19:32
briancurtinedleafe: openstack.authenticate(username="edleafe", password="lol")19:33
edleafebriancurtin: then I missed how that call maps to that class19:33
briancurtinsomething like that. a higher-level end-user abstraction that allows them to give the details that they have, which will construct the request that they need19:33
briancurtinedleafe: well if you call openstack.authenticate(smokesignal="lkajsldfkjasldkfj"), it'll create an auth object based on smoke signals19:34
jamielennoxbriancurtin: this will quickly become a problem if we are basing authentication upon which parameters are required19:34
bknudsonwe'll need a factory function based on the arguments... username="edleafe", password="lol" -> IdentityV2UsernamePassword, smokesignal="lkajsldfkjasldkfj" -> IdentityV2SmokeSignal19:35
*** lcheng has joined #openstack-meeting-319:35
wchrisj_as far as I know, there are only two ways to authenticate - username/password, with an optional tenant, and re-authing with a token19:36
wchrisj_yes/no?19:36
edleafebriancurtin: I was just commenting on the code that has been submitted. I didn't see anything about the sort of interface you're talking about19:37
briancurtinthat is what we have been talking about19:37
jamielennoxbknudson: relying on parameters is still a bad way to go -  if you are passing the params you know what you want anyway so i think the plugin approach is better19:37
jamielennoxwchrisj_: for v2 yes. for v3 that + oauth, kerberos soon and a bunch more to come19:37
wchrisj_So for v2, I'd suggest we do the simplest thing that works19:38
wchrisj_and lets learn from that when we build Identity v319:38
bknudsonv3 has username and password, too19:39
wchrisj_yep19:39
Alex_GaynorThere's also proprietary extension nonsense, which should be usable, even if they aren't included in openstacksdk19:39
wchrisj_does the proprietary extension nonsense have anything to do with auth?19:40
jamielennoxAlex_Gaynor: right i see at least the combination of username+password parameters could fit multiple plugins in future19:40
edleafewchrisj_: yes, since Rackspace still uses a proprietary auth19:41
jamielennoxand if you need to specify my_proprietary_username then you may as well call the plugin because you know what you want19:41
wchrisj_isn't that Rackspace auth specific to 1.0 endpoints?19:41
dolphmthe identity service is basically an abstraction layer over existing, proprietary auth systems -- but the way users expect to authenticate varies wildly from deployment to deployment19:42
*** lpetrut has quit IRC19:42
dolphmso the UX needs to be entirely tailorable to any given deployment ... i don't think openstacksdk should tackle much more than the base case (username + password) and pluggability19:42
wchrisj_dolphm: +119:43
dtroyerdolphm: +119:43
dolphmeven token-based auth strikes me as out of scope for openstacksdk19:43
*** jtomasek has joined #openstack-meeting-319:44
dtroyerdolphm: at the high-level api, agreed…at the low-level, there needs to be a way to inject it19:44
dolphmdtroyer: right, i'm more concerned about what is exposed to end users19:45
*** muralia has left #openstack-meeting-319:45
dolphmdtroyer: it'll have to handle token refreshing, rescoping, etc so it's got to be available somewhere19:45
dtroyerI'd love to focus on getting the low-level stuff fleshed out so we can start doing something…mixing discussions about high and low isn't being very productive so far19:46
*** david-lyle has quit IRC19:46
briancurtinnot to totally end this current auth topic, but with 14 minutes left, any thoughts on the next steps after this current review is approved?19:46
dolphmdtroyer: i don't want to commit to any high level stuff at this point :)19:47
bknudsonthere's a couple of approaches -- focus on the low level and work your way up, for focus on the high-level and work your way down19:47
bknudsonI'd prefer to focus on the high level, since those are our use cases.19:47
briancurtin#topic next steps and approaches19:47
*** openstack changes topic to "next steps and approaches (Meeting topic: python-openstacksdk)"19:47
Alex_Gaynorbriancurtin: I think the next step is expose an actual Client object19:47
dtroyerbknudson: yup…but it's hard to road-test the high-level  without the low-level19:48
edleafeAlex_Gaynor:  but we can'19:48
edleafecan19:48
bknudsondtroyer: it'll require implementing something ugly, but we can make direct requests and then flesh out the low level from there... keeping the high-level working thorough unit tests19:48
edleafetarrgggh19:48
edleafewe can't call it 'client' - see: https://etherpad.openstack.org/p/sdk-glossary19:49
Alex_GaynorConnection, whatever.19:49
dtroyerbknudson: then maybe we should just use keystoneclient as a stand-in low level rather than invent yet something else?19:49
bknudsondtroyer: as long as it doesn't tie us into any high-level decisions then I'm fine with that. But http clients are not difficult to write.19:50
wchrisj_This sounds a lot like what jamielennox: has suggested around the term Session19:51
bknudsonI'd like to see a definition of Session19:51
wchrisj_or context19:51
bknudsonwould a session be used by a single connection to a cloud? (i.e., one session - one cloud)19:52
briancurtinbknudson: to kick things off "(proposed) a wrapper around requests.Session that adds OpenStack-specific things like logging and auth-header injections and re-authentication on token expiration" (not my words, from the etherpad)19:52
dtroyerbknudson: yes, including specific user creds19:52
*** dguitarbite has joined #openstack-meeting-319:52
jamielennoxbknudson: yes, one session = one cloud using one auth19:53
edleafeI've used 'context' to be a specific authed user for a service. From there, you can access clients/whatever for each service19:53
wchrisj_See "context" definition in etherpad19:54
bknudsonbriancurtin: that definition sounds good to me.19:54
dtroyercontext is what you would have multiple instance of to talk to multiple clouds, or as multiple users, at the same time19:54
edleafedtroyer: yes19:55
briancurtin3 min left, anything else to squeeze in?19:57
*** sarob has joined #openstack-meeting-319:59
briancurtin#endmeeting19:59
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:59
openstackMeeting ended Tue Mar 18 19:59:04 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-18-19.00.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-18-19.00.txt19:59
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-18-19.00.log.html19:59
briancurtinthanks all!19:59
Alex_Gaynorthanks everyone19:59
wchrisj_thanks19:59
*** julim has quit IRC20:02
*** Alex_Gaynor has left #openstack-meeting-320:02
*** terrylhowe has left #openstack-meeting-320:02
*** lpetrut has joined #openstack-meeting-320:12
*** lcheng has quit IRC20:14
*** peristeri has quit IRC20:16
*** david-lyle has joined #openstack-meeting-320:18
*** bknudson has left #openstack-meeting-320:19
*** lcheng has joined #openstack-meeting-320:26
*** lcheng has quit IRC20:36
*** sarob has quit IRC20:38
*** sarob has joined #openstack-meeting-320:38
*** lcheng has joined #openstack-meeting-320:39
*** eguz has joined #openstack-meeting-320:46
*** lcheng has quit IRC20:47
*** eguz_ has joined #openstack-meeting-320:49
*** eghobo has quit IRC20:50
*** lblanchard has quit IRC20:51
*** eguz has quit IRC20:52
*** jtomasek has quit IRC20:57
*** jtomasek has joined #openstack-meeting-321:11
*** dtroyer has left #openstack-meeting-321:12
*** banix has quit IRC21:16
*** mfer has quit IRC21:28
*** jtomasek has quit IRC21:32
*** saju_m has quit IRC21:42
*** jthopkin has quit IRC21:58
*** lpetrut has quit IRC22:04
*** lcheng has joined #openstack-meeting-322:08
*** wchrisj_ has quit IRC22:14
*** wchrisj has joined #openstack-meeting-322:14
*** markmcclain1 has joined #openstack-meeting-322:17
*** markmcclain has quit IRC22:17
*** mwagner_lap has quit IRC22:21
*** markmcclain1 has quit IRC22:24
*** banix has joined #openstack-meeting-322:31
*** lcheng has quit IRC22:31
*** banix has quit IRC22:40
*** devlaps has joined #openstack-meeting-323:00
*** devlaps1 has quit IRC23:02
*** alexpilotti has quit IRC23:52
*** sarob has quit IRC23:57

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