Tuesday, 2014-03-11

*** lblanchard has joined #openstack-meeting-300:15
*** yamahata__ has joined #openstack-meeting-300:24
*** wchrisj has quit IRC00:39
*** wchrisj has joined #openstack-meeting-300:41
*** yamahata has joined #openstack-meeting-300:42
*** wchrisj has quit IRC00:43
*** wchrisj has joined #openstack-meeting-300:55
*** devlaps has quit IRC00:55
*** SumitNaiksatam has joined #openstack-meeting-301:02
*** lblanchard has quit IRC01:20
*** wchrisj has quit IRC01:22
*** alexpilotti has quit IRC01:40
*** wchrisj has joined #openstack-meeting-301:53
*** yamahata has quit IRC02:11
*** yamahata__ has quit IRC02:12
*** jpomero has quit IRC02:43
*** Sukhdev has joined #openstack-meeting-302:57
*** markmcclain has quit IRC04:00
*** david-lyle has joined #openstack-meeting-304:08
*** yamahata__ has joined #openstack-meeting-304:11
*** yamahata has joined #openstack-meeting-304:12
*** markmcclain has joined #openstack-meeting-304:14
*** wchrisj has quit IRC04:24
*** wchrisj has joined #openstack-meeting-304:54
*** eghobo has joined #openstack-meeting-304:57
*** Sukhdev has quit IRC04:57
*** wchrisj has quit IRC05:04
*** edhall has quit IRC05:44
*** edhall has joined #openstack-meeting-305:55
*** lpetrut has joined #openstack-meeting-306:00
*** eghobo has quit IRC06:07
*** eghobo has joined #openstack-meeting-306:08
*** eguz has joined #openstack-meeting-306:09
*** eghobo has quit IRC06:09
*** eguz has quit IRC06:11
*** tmazur has joined #openstack-meeting-306:17
*** eghobo has joined #openstack-meeting-306:41
*** mrunge has joined #openstack-meeting-307:18
*** mrunge has joined #openstack-meeting-307:18
*** MaxV has joined #openstack-meeting-307:29
*** MaxV has quit IRC07:30
*** markmcclain has quit IRC07:53
*** yamahata has quit IRC08:14
*** yamahata__ has quit IRC08:15
*** eghobo has quit IRC08:18
*** jcoufal has joined #openstack-meeting-308:24
*** tmazur has quit IRC08:27
*** yamahata__ has joined #openstack-meeting-308:30
*** yamahata has joined #openstack-meeting-308:30
*** nacim has joined #openstack-meeting-308:32
*** lpetrut has quit IRC08:59
*** jcoufal has quit IRC09:00
*** jcoufal_ has joined #openstack-meeting-309:00
*** jcoufal_ has quit IRC09:02
*** yamahata has quit IRC09:04
*** yamahata__ has quit IRC09:04
*** jrist has quit IRC09:07
*** MaxV has joined #openstack-meeting-309:14
*** jcoufal has joined #openstack-meeting-309:15
*** johnthetubaguy has joined #openstack-meeting-309:19
*** jrist has joined #openstack-meeting-309:21
*** lpetrut has joined #openstack-meeting-309:31
*** johnthetubaguy has quit IRC09:44
*** johnthetubaguy has joined #openstack-meeting-309:44
*** johnthetubaguy1 has joined #openstack-meeting-309:57
*** johnthetubaguy has quit IRC10:01
*** saju_m has joined #openstack-meeting-310:05
*** yamahata__ has joined #openstack-meeting-310:08
*** yamahata has joined #openstack-meeting-310:09
*** saju_m has quit IRC10:18
*** tshirtman has quit IRC10:22
*** tshirtman has joined #openstack-meeting-310:22
*** saju_m has joined #openstack-meeting-310:31
*** akrivoka has joined #openstack-meeting-310:34
*** saju_m has quit IRC10:54
*** johnthetubaguy1 has quit IRC11:09
*** MaxV has quit IRC11:36
*** jtomasek has quit IRC11:46
*** jrist has quit IRC11:58
*** jtomasek has joined #openstack-meeting-312:00
*** yamahata__ has quit IRC12:04
*** yamahata has quit IRC12:09
*** MaxV has joined #openstack-meeting-312:14
*** MaxV has quit IRC12:18
*** david-lyle has quit IRC12:21
*** wchrisj has joined #openstack-meeting-312:29
*** wchrisj has quit IRC12:29
*** MaxV has joined #openstack-meeting-312:35
*** xuhanp has joined #openstack-meeting-312:37
*** mwagner_lap has quit IRC13:00
*** alexpilotti has joined #openstack-meeting-313:05
*** lblanchard has joined #openstack-meeting-313:08
*** yamahata__ has joined #openstack-meeting-313:11
*** jpomero has joined #openstack-meeting-313:11
*** yamahata__ has quit IRC13:15
*** yamahata__ has joined #openstack-meeting-313:16
*** julim has joined #openstack-meeting-313:18
*** yamahata__ has quit IRC13:21
*** yamahata__ has joined #openstack-meeting-313:22
*** jrist has joined #openstack-meeting-313:26
*** yamahata has joined #openstack-meeting-313:26
*** yamahata__ has quit IRC13:27
*** yamahata__ has joined #openstack-meeting-313:28
*** johnthetubaguy has joined #openstack-meeting-313:28
*** wchrisj has joined #openstack-meeting-313:28
*** yamahata__ has quit IRC13:30
*** yamahata__ has joined #openstack-meeting-313:31
*** yamahata__ has quit IRC13:34
*** jpich has joined #openstack-meeting-313:34
*** yamahata__ has joined #openstack-meeting-313:35
*** mfer has joined #openstack-meeting-313:37
*** yamahata has quit IRC13:41
*** yamahata has joined #openstack-meeting-313:41
*** yamahata__ has quit IRC13:43
*** yamahata__ has joined #openstack-meeting-313:47
*** ftcjeff has joined #openstack-meeting-313:48
*** jcoufal has quit IRC13:50
*** yamahata__ has quit IRC13:50
*** absubram___ has joined #openstack-meeting-313:51
*** yamahata__ has joined #openstack-meeting-313:51
*** peristeri has joined #openstack-meeting-313:57
*** yamahata__ has quit IRC13:59
*** yamahata__ has joined #openstack-meeting-314:05
*** yamahata__ has quit IRC14:09
*** alexpilotti has quit IRC14:10
*** peristeri has quit IRC14:12
*** peristeri has joined #openstack-meeting-314:16
*** alexpilotti has joined #openstack-meeting-314:19
*** xuhanp has quit IRC14:23
*** david-lyle has joined #openstack-meeting-314:26
*** xuhanp has joined #openstack-meeting-314:27
*** mrunge has quit IRC14:31
*** markmcclain has joined #openstack-meeting-314:33
*** wchrisj has quit IRC14:38
*** jcoufal has joined #openstack-meeting-314:40
*** lcheng has joined #openstack-meeting-314:42
*** jrist has quit IRC14:43
*** devlaps has joined #openstack-meeting-314:46
*** dtroyer has joined #openstack-meeting-314:47
*** peristeri has quit IRC14:49
*** jthopkin has joined #openstack-meeting-314:53
*** lcostantino has joined #openstack-meeting-314:57
*** peristeri has joined #openstack-meeting-315:00
*** lcostantino has left #openstack-meeting-315:02
*** wchrisj has joined #openstack-meeting-315:02
*** nacim has quit IRC15:03
*** jcoufal has quit IRC15:06
*** jcoufal has joined #openstack-meeting-315:07
*** johnthetubaguy1 has joined #openstack-meeting-315:07
*** fungi has quit IRC15:07
*** johnthetubaguy has quit IRC15:10
*** jcoufal has quit IRC15:12
*** jcoufal has joined #openstack-meeting-315:13
*** cjellick has joined #openstack-meeting-315:19
*** nacim has joined #openstack-meeting-315:21
*** cjellick_ has joined #openstack-meeting-315:22
*** cjellick_ has quit IRC15:22
*** cjellick_ has joined #openstack-meeting-315:23
*** cjellick has quit IRC15:24
*** jcoufal has quit IRC15:25
*** johnthetubaguy1 has quit IRC15:40
*** johnthetubaguy has joined #openstack-meeting-315:42
*** thinrichs has joined #openstack-meeting-315:44
*** jcoufal-mobile has joined #openstack-meeting-315:45
*** fungi has joined #openstack-meeting-315:46
*** eghobo has joined #openstack-meeting-315:53
*** tmazur has joined #openstack-meeting-315:53
*** pballand has joined #openstack-meeting-315:57
*** tzumainn has joined #openstack-meeting-315:57
*** mrunge has joined #openstack-meeting-315:59
*** jcoufal has joined #openstack-meeting-316:00
david-lyle#startmeeting Horizon16:01
openstackMeeting started Tue Mar 11 16:01:05 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 everyone!16:01
akrivokahi everyone16:01
jcoufalo/16:01
absubram___hey16:01
mrungeo/16:01
jpichHey16:01
lblanchardhi all16:01
lchengo/16:02
tmazurhello o/16:02
*** rajdeep has joined #openstack-meeting-316:02
david-lylehttps://wiki.openstack.org/wiki/Meetings/Horizon16:02
david-lyle#topic Welcome Radomir to Horizon Core16:03
*** openstack changes topic to "Welcome Radomir to Horizon Core (Meeting topic: Horizon)"16:03
*** SumitNaiksatam has quit IRC16:03
david-lyleAs of yesterday, Radomir was officially added to Horizon core.16:03
jcoufalRadomir is not here, but I am happy for him! :)16:04
mrungethank you david-lyle ! and well deserved Radomir!16:04
david-lyleRadomir has made many contributions, reviews and is highly involved in the tuskar-ui effort.16:04
*** johnthetubaguy1 has joined #openstack-meeting-316:04
lblanchardyes, congrats to Radomir!!16:04
david-lyleA welcome addition16:04
jpichAgreed16:04
akrivokadefinitely well deserved16:04
david-lyleSo congratulations to Radomir and thanks.16:04
lchengcongrats to Radomir!16:05
david-lyle#topic Icehouse RC116:05
*** openstack changes topic to "Icehouse RC1 (Meeting topic: Horizon)"16:05
david-lylehttps://launchpad.net/horizon/+milestone/icehouse-rc116:05
*** johnthetubaguy has quit IRC16:05
david-lylewe're looking good on the FFEs16:05
jpichdavid-lyle: Isn't the Django 1.6 one pretty much implemented now that the requirement change has gone through?16:06
jomaracongrats radomir!16:06
david-lylethe django 1.6 patch just merged into Horizon and I'm going to post a patch to run the new tox env py27dj15 to maintain 1.5 testing16:06
*** pballand has quit IRC16:06
*** rajdeep has quit IRC16:06
david-lylewe can probably call it implemented16:06
*** xuhanp has quit IRC16:07
david-lyleI also will release openstack_auth with a tox env to test 1.5 still16:07
mrungegreat, david-lyle! good that it landed16:07
david-lylemrunge: was worried for a while :)16:07
jpichGreat16:08
david-lylehttps://blueprints.launchpad.net/horizon/+spec/per-user-quotas is the last FFE open16:08
jpichdavid-lyle: https://review.openstack.org/#/c/32884/ (the django 1.4 job) may provide a few hints for the infra job, fwiw16:08
david-lyleooh, nice, I just tracked down the yaml file thanks to infra, but looks like I needed another piece16:09
*** gokul_ has joined #openstack-meeting-316:09
david-lylethanks jpich16:09
absubram___david-lyle: For my FFE - https://blueprints.launchpad.net/horizon/+spec/neutron-subnet-mode-support.. I had to update my review today16:09
absubram___the neutron side is still in review.. but some changes had been made16:10
david-lyleabsubram___, I think this will slip until Juno16:10
david-lyleFFEs should be merged by today16:10
absubram___ok.. that's fine16:10
david-lylesince neutron is not there, we can't really do much16:11
absubram___sure16:11
absubram___I think they are still targeting I :)16:11
david-lylesure16:11
mrungeeverybody is targeting Icehouse...16:11
david-lylethey _may_ land it today, or get more time, but that puts us out pretty far16:12
absubram___but they made some changes to the update side.. and so I had to also.. but I have some Q's about the Horizon side for the update - sent out an email about it16:12
absubram___and that change is breaking UT :(.. so need to fix it..16:12
absubram___but yeah.. pushing this out to J makes sense16:12
absubram___mrunge: lol16:13
david-lyleabsubram___, thanks for your effort here, unfortunately things didn't line up right16:13
david-lyleabsubram___, I'll wait til the program status meeting today to push to Juno based on neutron team feedback16:14
absubram___david-lyle: np.. thank you.. will continue working on getting it ready.. and it get's in J when the neutron side is also hopefully stable16:14
absubram___sounds good.. thanks david16:15
david-lylethe per-user-quota FFE needs to either merge today by the program team meeting 21:00 UTC or it too will push to Juno16:15
david-lyleI have not had a chance to review it yet16:16
david-lyleseems to be a common theme on that bp16:16
*** wchrisj has quit IRC16:17
*** wchrisj has joined #openstack-meeting-316:17
david-lyleand last for rc1, are there any bugs that aren't assigned to the milestone that should be?16:18
david-lyleI must admit, I'm behind on the bug triage, so please target any that are high priority16:18
mrungeor feel free to ping anyone else than david-lyle16:19
mrungee.g me16:19
absubram___yes please :).. I have a few reviews out.. all are specific to the 'router' dashboard side16:19
jpichOr leave a comment so that people with triaging powerz can set it accordingly16:19
*** jrist has joined #openstack-meeting-316:19
akrivokacan we target this one please? https://bugs.launchpad.net/horizon/+bug/128869816:20
mrungeoh yes absubram___ you should use that plugin style for the router dashboard16:20
akrivoka(fix is already implemented, just needs one more core review)16:20
mrungeakrivoka, done16:20
akrivokamrunge: thanks!16:20
absubram___yes I am.. and I like the new accordion style display too.. looks good :)16:20
absubram___but these are bugs in code that went in during Havana.. minor nits16:21
absubram___well… not very minor :)16:21
jcoufalregarding the accordion style, should we those minor things and smaller styling consider as bugs for Havana?16:21
jcoufalsorry16:21
jcoufalIcehouse :)16:21
jcoufalI am obviously one milestone behind :)16:22
mrungejcoufal, a release behind?16:22
david-lylejcoufal, can you be more specific?16:22
jcoufaloh dear16:22
jcoufaldavid-lyle: sure16:22
jcoufalwell16:22
david-lyleif there are errors we should certainly fix them16:23
jcoufalthere were no errors more smaller corrections which you also mentioned previously16:23
jcoufaland we also discussed the styling enhancements in time16:24
absubram___https://bugs.launchpad.net/horizon/+bug/1229811 https://bugs.launchpad.net/horizon/+bug/1285298 https://bugs.launchpad.net/horizon/+bug/1260438 https://bugs.launchpad.net/horizon/+bug/1260435 https://bugs.launchpad.net/horizon/+bug/126043616:24
absubram___all are in review.. and would love to get them into rc1 if possible :)16:24
jcoufalso I was just wondering if those are considered as bugs or features for Juno16:24
*** pballand has joined #openstack-meeting-316:25
jcoufallike project picker16:25
mrungejcoufal, could you please be *more* specific?16:25
david-lylelikely features for Juno, as we are really in the hardening phase of the release cycle, but it's likely a case by case basis16:25
mrungejcoufal, or do you have a patch ready?16:25
david-lylejcoufal, I would like the picker improved, to match the design, but at this point, it's not a small change16:26
jcoufalmrunge: nope, I was just wondering how it is considered, so case by case is valid answer16:26
jcoufaldavid-lyle: sure thing16:26
mrungeabsubram___, https://review.openstack.org/#/c/48255/7 is waiting on your input....16:26
absubram___yes.. Working on responsding16:27
david-lylejcoufal: let's concentrate on getting it right in Juno, if there are some minor fixes to improve/aid usability let's consider them16:27
david-lylenow16:27
david-lyleany other items for RC1?16:28
david-lyle#topic Design Summit Session Topics16:29
*** openstack changes topic to "Design Summit Session Topics (Meeting topic: Horizon)"16:29
*** zigo has joined #openstack-meeting-316:29
david-lyleSummit topic suggestion is open for the Juno summit. http://summit.openstack.org16:29
jcoufalhow many slots do we have for horizon?16:30
david-lyleanyone is free to propose session topics16:30
david-lylejcoufal: unclear, I would imagine the 6-816:30
david-lyleI think maybe one less than last summit to allow for the cross-project sessions16:30
david-lylebut the total has not been communicated yet16:30
jcoufalalright it makes sense16:31
david-lyleCross-project topics are also acceptable for the first time in a while16:31
*** doug-fish has joined #openstack-meeting-316:31
*** SumitNaiksatam has joined #openstack-meeting-316:31
*** kudva has joined #openstack-meeting-316:31
david-lyleSo please propose any topic ideas, I have a few, but would like to let others post theirs16:32
lblanchardjcoufal: I entered a "Other Project" session for a UX designers/developers gathering16:32
lblanchardjcoufal: happy to update this is you think it needs additions!16:32
jcoufallblanchard: seen that, I wanted to do the same, but I am happy it's covered16:33
lblanchardjcoufal: cool16:33
jcoufalwill definitely post some ideas what we can cover16:33
lblanchardjcoufal: perfect16:33
jcoufalthanks for thinking of this ;)16:33
lblanchardthen one other session I proposed is around the usability test results that we've gotten from the testing over the last 2 weeks16:34
david-lyleI think UX overflow may need to use the unconference schedule, but not a bad idea to get the topics proposed16:34
lblanchardit went very well and we hope to have a bunch of design proposals and blueprints to share in a Horizon session if it's accepted!16:34
lblancharddavid-lyle: yeah, we can definitely use unconference for topics too16:34
jcoufaldavid-lyle: I think at least one general topic is needed16:34
jcoufalthe one liz proposed16:34
david-lylejcoufal, I'm not disagreeing16:35
david-lylebut UX has a lot to talk about :) will take more than 40 minutes16:35
lblancharddavid-lyle: we hope to do some lightening talks too if they are available just to get people to have awareness of UX, usabillity testing, personas, etc16:35
david-lylegreat idea16:35
jcoufaldavid-lyle: yeah, we do :)16:36
*** jcoufal-mobile has quit IRC16:36
*** jcoufal-mobile has joined #openstack-meeting-316:36
*** jcoufal-mobile has quit IRC16:37
david-lyle#topic Open Discussion16:37
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"16:37
absubram___maybe we can have a short session for this - https://blueprints.launchpad.net/horizon/+spec/api-capability-detection16:37
absubram___at the summit16:37
david-lyleabsubram___, yes, we need to handle that for the keystone api in Juno as well as other services16:38
absubram___and I also had some questions about UT that I wanted to bring up16:38
david-lylegeneral questions or specific?16:39
david-lylespecific would be better to go through in the regular room16:39
david-lyleAnyone have anything else?16:43
*** markmcclain has quit IRC16:43
lblanchardQuick update on the Sparklines design…sayali, lsmola, and I have been discussing and this is one of the latest designs I put together. The hope is that we might be able to stack sparklines in the table and save some horizontal space…we are just targeting these two sparkline metrics for now: http://people.redhat.com/~lsurette/OpenStack/Sparkline%20Ideas16:44
lblanchardthis image is missing the actions column…sorry about that :) But the general idea is consolidation of the sparklines16:44
david-lylelblanchard: power state column is still present, and charted?16:47
lblancharddavid-lyle: great question…might not need to have a column16:47
lblancharddavid-lyle: I also asked about all of the possible states here…we might need more than just UP/DOWN16:48
mrungeisn't sparklines a new feature and not a bug?16:48
david-lylemrunge, yes would merge in Juno16:48
lblanchardmrunge: yes, sorry this is design work happening for a feature that will be pushed16:48
david-lylelblanchard, yes some states are more than binary16:50
david-lyleI do like the idea16:50
lblancharddavid-lyle: right16:50
lblancharddavid-lyle: thanks…still a work in progress, just wanted to update everyone16:50
jpichthanks lblanchard16:51
david-lyleyes thank you16:51
david-lyleLet's end a little early today.  Thank you everyone.16:54
david-lyle#endmeeting16:54
*** openstack changes topic to "Free for all (Meeting topic: Horizon)"16:54
openstackMeeting ended Tue Mar 11 16:54:09 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:54
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-03-11-16.01.html16:54
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-03-11-16.01.txt16:54
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-03-11-16.01.log.html16:54
jpichThanks16:54
david-lyleHave a great week!16:54
*** doug-fish has left #openstack-meeting-316:55
tmazurThank you!16:55
akrivokathanks everyone16:55
lblanchardthanks all16:55
absubram___thank you16:55
jcoufalthanks o/16:57
*** absubram___ is now known as absubram__lunch16:58
*** tzumainn has left #openstack-meeting-316:58
*** MaxV has quit IRC16:59
pballandhi17:00
thinrichsHi all.  We're getting the Congress meeting started.17:00
thinrichs#startmeeting CongressTeamMeeting17:00
openstackMeeting started Tue Mar 11 17:00:36 2014 UTC and is due to finish in 60 minutes.  The chair is thinrichs. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)"17:00
openstackThe meeting name has been set to 'congressteammeeting'17:00
*** akrivoka has left #openstack-meeting-317:01
thinrichsAgenda for the day:17:01
*** david-lyle has quit IRC17:01
*** sarob_ has joined #openstack-meeting-317:01
thinrichs1) progress toward an alpha release17:01
thinrichs2) pointer to other policy projects.17:01
thinrichsLet's start with 2 since it's quick.17:02
*** tmazur has quit IRC17:02
* sarob_ lurking17:02
thinrichsLast week gokul and others on the ML were asking about all the policy projects in OS.17:02
thinrichsThey put together a list of them with comparisons.  Probably incomplete.  But I took some time to go through them and put links to them on the Congress wiki.17:02
pballandsarob_: you're in good company :)17:03
sarob_;)17:03
*** jpich has left #openstack-meeting-317:03
thinrichsHere's a link to the wiki.  Let's make an effort to keep it up to date when we hear of new projects, etc.17:03
thinrichshttps://wiki.openstack.org/wiki/Congress17:03
pballandthe links are helpful, thank you17:03
thinrichsInfo is at the end of the page.17:04
*** jcoufal has quit IRC17:04
*** terrylhowe has joined #openstack-meeting-317:04
*** lcheng has quit IRC17:04
thinrichsAny comments/questions on that?17:04
pballandit seems like these projects may play well, in the future17:05
pballandcurrent strategy appears complimentary (which is great)17:06
thinrichsYeah--I'm hoping that down the line we'll be able to carve off pieces of the Congress policy and send them down to these other efforts for enforcement.17:06
*** rajdeep has joined #openstack-meeting-317:06
thinrichsMoving to next agenda item now.17:07
thinrichs#topic Progress toward alpha release17:07
rajdeephi17:07
*** openstack changes topic to "Progress toward alpha release (Meeting topic: CongressTeamMeeting)"17:07
thinrichsrajdeep: hi!17:07
pballandhi rajdeep - just in time :)17:07
rajdeepyes,17:07
thinrichsWe had just quickly gone over the list of other policy efforts within OS that we've listed on the Congress wiki page.17:07
thinrichsWe'll be trying to keep that up to date.17:08
rajdeepok17:08
thinrichsNow we've moved on to the main part of the agenda: progress toward an alpha release.17:08
thinrichsWe'll just go down a list of todos and discuss progress.17:08
rajdeepgreat - what are the time lines17:08
thinrichsNot sure what the right timeline is.  I was hoping to have something ready at the end of the month, but it's not clear if that's plausible.17:09
thinrichsLet's revisit once we talk through the todos.17:09
thinrichsFirst item is Data Integration, which you are working on rajdeep.17:10
rajdeepwhere is the agenda posted?17:10
rajdeepcurrently i am working on finishing the neutron integration17:10
rajdeepshould we have some kind of data model for each type of service we are integrating17:10
pballandI failed to post it - Tim has a list of todos to talk about17:11
rajdeepand populate those structures from the native objects17:11
rajdeepi saw your comments on neutron17:11
pballandthe data model is just tuples17:11
pballandtuples are lowest-common format for all data sources17:11
pballandthat allows the policy language to be common across all sources17:12
rajdeepok, so i need to convert networks, ports, subnets etc into tuples17:12
pballandwith that said, we should have a well defined (and commented) set of tuples for each data source17:12
thinrichsrajdeep: yes17:12
gokul_hi all:  this is gokul17:12
thinrichsI put an example in the comments.  Did that make sense?17:12
thinrichsgokul: hi!17:13
*** kudva_ has joined #openstack-meeting-317:13
rajdeepso i just convert dictionary into tuple and return17:13
rajdeepyes go it17:13
*** d0ugal has quit IRC17:13
gokul_just beginning with congress...  hope to contribute :)17:13
pballandgokul_: great - there is a lot to do :)17:13
thinrichsrajdeep: not just a Python dict to Python tuple.  The tuples must only have strings/numbers as elements.  No embedded data structures.17:13
rajdeepok, got it17:14
kudva_Hi, I am prabhakar, work with Gokul, joining as well17:14
thinrichskudva: welcome!17:14
pballandkudva_: welcome17:14
rajdeepso my plan is to cover neutron, nova, keystone and cinder17:14
thinrichsWe're in the midst of going thru the list of todos to get an alpha release ready.17:15
thinrichskudva, gokul: Why don't we keep going and then if anything sounds interesting to work on, let us know.17:15
*** lcheng has joined #openstack-meeting-317:15
rajdeepany other component for openstack i missed?17:16
gokul_yup -- sounds good.  just reading the conversation for now and "understanding".17:16
kudva_okay, I have some questions as well, will save for another discussion. Let's go through the list17:16
thinrichsrajdeep: I'd say that neutron and nova are musts and keystone and cinder are nice-to-haves17:16
rajdeepgood,17:16
rajdeepshould not be difficult17:16
rajdeepi found some problems getting groups out of keystone17:17
rajdeepapparently not many people use it as of now17:17
*** sarob_ has quit IRC17:17
rajdeepand all our examples tie users to groups17:17
rajdeepwhich is more of AD/LDAP use case17:17
thinrichsrajdeep: We probably want to at least understand how the tables/tuples that you're using to represent Neutron breaks/does-not-break the Neutron action descriptions that we have.17:17
*** sarob_ has joined #openstack-meeting-317:18
rajdeepok-- so how do we plan the integration one data is in place17:18
thinrichsrajdeep: I'd be happy to use AD/LDAP for groups -- to illustrate that Congress works with non-OS components.17:18
pballandrajdeep: can you elaborate?17:18
rajdeepdo we need another component which ties the parser/runtime with the data_driver17:19
rajdeepor will this be an example script outside the core code17:20
thinrichsrajdeep: not sure if it's another component but yes we need a framework that glues the policy-engine together with the data drivers you are writing.17:20
thinrichsrajdeep: I think we want it integrated.17:20
rajdeepexactly17:20
*** lpetrut has quit IRC17:20
thinrichsCongress will need to be responsible for integrating the data necessary to make policy decisions.17:21
rajdeepand we would need a place to do integration testing -- openstack + AD + congress17:21
*** SumitNaiksatam has quit IRC17:21
thinrichsrajdeep: that's another important issue and it's on the list of alpha todos17:21
rajdeepok17:22
*** jthopkin has left #openstack-meeting-317:22
rajdeeplet us move to the next item on the agenda17:22
thinrichsCan someone look into the data integration "glue"?17:22
pballandI would be happy to take that17:22
thinrichsGreat.17:22
thinrichs#action pballand will look into the data integration framework.17:23
thinrichsThe next todo is the API infrastructure that connects the policy engine to the outside world.17:23
thinrichspballand: you worked on this--could you give us a status update?17:24
pballandyeah, the code that is posted was pretty rushed17:24
pballandbasic idea was to use a simple API co-routine loop like other projects17:24
pballandI'm not worried about a fancy framework right now, but getting the API abstractions right is important17:24
*** nacim has quit IRC17:25
thinrichspballand: agreed17:25
*** SumitNaiksatam has joined #openstack-meeting-317:25
pballandstill need to expose _basically everything_17:25
thinrichsCould you estimate amount of time/work to hook everything up?17:25
pballandI imagine a pretty good interface could be constructed with a few solid weeks of work17:26
*** lcheng has quit IRC17:26
thinrichspballand: do you have cycles to devote to that?17:26
pballandI can definitely take a second pass at making the code more product-ready17:26
rajdeepwe would also need to tie the REST endpoints to the runtime engine17:27
rajdeepor we want to keep them separate17:27
rajdeep?17:27
pballandI think its best to keep a loose coupling between to two17:27
pballand... but in the same binary17:27
pballanddo you have thoughts?17:28
rajdeepwell it was hard for me to understand it initially17:28
*** lcheng has joined #openstack-meeting-317:28
rajdeephow the two are linked -- currently only through tables17:28
rajdeepperhaps we could put it in a readme17:29
pballand(in my experience, APIs that evolve along with the underlying implementation become cumbersome over time)17:29
pballandI'll try to make it clear as I develop the next iteration17:29
*** mrunge has quit IRC17:29
rajdeepok, great17:29
rajdeepany plans to add persistence layer to tables17:29
rajdeep?17:29
thinrichsrajdeep: persistence for policies is important.17:30
pballand(to be fair, the current implementation is "barely-coupled", so it isn't surprising that it is hard to follow)17:30
thinrichspersistence for tables is not.17:30
thinrichsbecause once we turn off Congress, it'll need to resync with all the data sources anyway.17:31
rajdeepok..i meant policies17:31
pballandrajdeep: congress is the source of truth for the policy, but is just a cache of other data (in the tables)17:31
thinrichspballand: agreed17:31
thinrichsrajdeep: yes--we should do that.17:31
thinrichsI was thinking that we'd do it via logging at first.17:32
thinrichsSo every time some inserts/deletes a policy statement, we'd log it in a way that we can replay the logs later to reconstruct the state of Congress.17:32
thinrichsWe'll need logging of some form for debugging/auditing anyway;.17:32
thinrichsAnyone want to look into this?17:32
rajdeepi can take it up after my data integration is over17:33
thinrichsI don't think this is a show-stopper for an alpha release.17:33
thinrichsrajdeep: great.17:33
rajdeepwe will use regular python logging?17:33
thinrichs#action rajdeep will look into persisting policy after his data integration work.17:33
thinrichsrajdeep: haven't thought that far ahead.17:33
thinrichsUnless there are objection, we'll move onto a couple of quick alpha todos.17:34
rajdeepsure go ahead17:34
pballandplease fire away :)17:34
thinrichsThere were some basic issues with the policy engine not doing really ANY syntax checking.17:35
thinrichsI pushed those last week sometime.  So that todo is finished well enough for now.17:35
thinrichsAnother small todo was to startup some user docs so that people have a guide when using Congress for the first time.17:35
thinrichsI just pushed for review the first cut at that.17:35
thinrichs        https://review.openstack.org/#/c/79383/17:36
*** sarob_ has quit IRC17:36
*** sarob_ has joined #openstack-meeting-317:36
thinrichsI'll give you a minute to peruse.  Let me know when you're ready to move on.17:36
pballandI'll try to review by tomorrow17:37
thinrichsIt's probably hard to look at in raw RST, but it gets compiled into HTML, PDF, etc.17:37
thinrichsIt's the standard thing to use in OS (I believe).17:37
rajdeepwow thats lot of docs17:37
thinrichsLots of files, perhaps, but only a few pages of content.17:37
rajdeepperhaps we could look at docbook format as well17:37
thinrichsrajdeep: I have no idea what the list of supported formats are.17:38
sarob_docs stores docbook in xml17:38
pballandfrom the opestack wiki: "We use DocBook to create OpenStack's web documentation for deployers, admins, and CLI and API users. We use ReStructured Text (RST) files stored in source code for developer docs."17:38
sarob_projects typically use RST17:38
*** markmcclain has joined #openstack-meeting-317:38
sarob_pballand: you got it17:38
thinrichssarob: that's what we're using.  Phew!17:39
rajdeepso we are building developer docs "only"?17:39
pballand:)17:39
pballandit's a great place to start :)17:39
rajdeepyes let us focus on getting alpha out17:39
sarob_ive been dabbling with setting standards for RST17:39
pballandI think there is confusion on whether these are dev or user docs, but our first users are developers :)17:39
sarob_so we can pull the content into XML on build17:39
sarob_pballand: right17:40
sarob_pballand: status quo, better than new ground on docs17:40
sarob_pballand: code perhaps first17:40
pballandas we get closer to alpha, we can leverage the RST to create more formal user docs17:40
pballandsarob_: agreed17:40
sarob_pballand: as long as you are consistent in formal, no problems17:40
sarob_pballand: arrg, format17:41
thinrichsMoving on: we wanted to do some basic scaling tests.17:42
thinrichsThat was on my plate and I haven't gotten around to it.17:42
pballandI was hoping to get an example dataset from a user with a big deployment, but they ran in to so hurdles17:42
pballandhopefully more to come on this...17:42
pballands/so/some/17:43
thinrichsLast item on my list for the alpha release.  (Probably others I'm missing.)17:43
rajdeepthinrichs : what would be typical number of policy insertions in a real life use case?17:43
pballandrajdeep: it seems to very *greatly* based on the deployment17:44
*** absubram__lunch has quit IRC17:44
pballandinsertions are relatively infrequent17:44
rajdeepok and total policy elements17:45
pballanddata changes (group membership, for instance) are common, however, so incremental computation is imporatnt17:45
pballandrajdeep: it's hard to say17:45
rajdeepanother question is how will congress scale17:45
rajdeepwill it be a multi node deployment?17:45
pballandscale is important, but we need the operational model first17:47
thinrichsWith that, we need to move on to the last todo.17:47
pballandI'd rather not scale a shitty model :)17:47
thinrichsBefore running out of time.17:47
thinrichsThe last issue is one of what *kinds* of policies we are having the user write.17:47
thinrichsThere are (at least) 3.17:47
thinrichs1. Classification + Action (what we're currently promoting).  The idea is to describe which *states* of the cloud are permitted by policy.17:48
thinrichs2. Access-Control (e.g. XACML, AD).  The idea is to describe what *actions* are *permitted* for whom.17:48
thinrichs3. Condition action: The idea is to describe what *actions* Congress should *execute* under what conditions.17:49
thinrichsDo those 3 types of policies make sense?17:49
kudva_In 1. do you mean *states* of a cloud as in compliance or reliability (failure), or a more generic state?17:49
*** mfer has quit IRC17:50
*** johnthetubaguy1 has quit IRC17:50
thinrichskudva: by *state* I mean the collection of all the data Congress knows about (i.e. the collection of all the cloud services that we've hooked up to Congress)17:50
thinrichsSo, generic, I think.17:50
thinrichsThe reason I bring this up is that I believe there are reasons that people might want/need all 3 kinds of policy simultaneously.17:51
thinrichsAnd perhaps we want to think of Congress as a policy engine that enables people to choose what they want and to mix and match.17:52
pballandI think it's important that congress doesn't interpret things like failure - it simply computes the policy provided17:52
rajdeephow are these related to each other17:52
*** johnthetubaguy has joined #openstack-meeting-317:52
rajdeep1 will lead to 317:52
rajdeep2 will feed into 1?17:52
thinrichsrajdeep: From 1 we can compute a bunch of possible 3s.17:53
*** eghobo has quit IRC17:53
thinrichsE.g. if we want all networks connected to a specific kind of VM, and that policy is violated, then there may be many ways to correct the violations.17:53
thinrichsWe could disconnect an offending network, delete the VM, etc.17:53
kudva_So condition would represent any python function (which uses os clients and monitored data, alarms etc)?17:53
thinrichsEach of those choices could lead to a different policy 3.17:54
pballandkudva: not python function; rather policy-directed combination of primitives from openstack components17:54
*** eghobo has joined #openstack-meeting-317:55
thinrichsPolicy type 2 is different than 1 b/c we might want to allow certain users to perform actions that cause certain types of violations.17:55
thinrichswhere by 'violations' I mean 'violations' according to policy type 1.17:55
*** Alex_Gaynor has joined #openstack-meeting-317:55
pballand(there is a function providing the data to congress, but the logic is in the way the policy language combines the tuples)17:55
thinrichsSo types 2 and 1 are different as well.17:56
pballandkudva: does that make sense?17:56
gokul_however (I brought up a similar qn on the ML), would it be correct to understand that at this point, based on how conditions evaluate to (pretty much Boolean), actions will be taken.    in some sense, something like an 'optimization policy' would not fit into this framework...   would that be a reasonable statement?17:56
thinrichsI just noticed we're running short on time.17:56
*** david-lyle has joined #openstack-meeting-317:56
thinrichsgokul: yes--I think that's a reasonable characterization of the class of policies that Congress can *enforce* itself.17:57
*** glyph has joined #openstack-meeting-317:57
thinrichsI'm not sure at this point whether we could express a policy requiring optimization for enforcement within Congress.17:57
thinrichsIf we could express such a policy, we could potentially carve it out and send it to another component for enforcement.17:57
gokul_  thinrichs:   thanks for the clarification.  thats fine.  i just wanted to understand the scope.17:57
thinrichsHand-waving furiously.17:58
thinrichsLet's wrap up since we're out of time.17:58
thinrichsThis has been a great discussion.  Let's continue on the ML.17:58
kudva_Yes, I would like  to understand the relationship between policy primitives and python functions17:59
*** jpomero has quit IRC17:59
pballandthanks everyone17:59
gokul_great.  thanks!17:59
kudva_thanks17:59
rajdeepthanks!17:59
thinrichsThanks all!17:59
thinrichs#endmeeting17:59
*** openstack changes topic to "Free for all (Meeting topic: Horizon)"17:59
openstackMeeting ended Tue Mar 11 17:59:39 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-03-11-17.00.html17:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-03-11-17.00.txt17:59
openstackLog:            http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-03-11-17.00.log.html17:59
*** gokul_ has quit IRC17:59
*** kudva_ has quit IRC17:59
*** jnoller has joined #openstack-meeting-318:00
*** mrunge has joined #openstack-meeting-318:00
*** pballand has quit IRC18:01
Alex_Gaynorjnoller: time to kick this party off?18:02
*** jpomero has joined #openstack-meeting-318:02
jnollerpython-openstacksdk meeting starting; need to find the meeting bot commands18:02
*** thinrichs has quit IRC18:02
jnoller#startmeeting Python-OpenstackSDK weekly meeting18:03
openstackMeeting started Tue Mar 11 18:03:21 2014 UTC and is due to finish in 60 minutes.  The chair is jnoller. Information about MeetBot at http://wiki.debian.org/MeetBot.18:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:03
*** openstack changes topic to " (Meeting topic: Python-OpenstackSDK weekly meeting)"18:03
openstackThe meeting name has been set to 'python_openstacksdk_weekly_meeting'18:03
jnoller#link Agenda: https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK#Agenda_for_2014-03-11_1900_UTC18:03
jnoller#link https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK#Agenda_for_2014-03-11_1900_UTC18:03
jnollerFirst item: if you are here #link https://wiki.openstack.org/wiki/SDK-Development/PythonOpenStackSDK18:04
jnoller*sigh*18:04
jnoller#link https://wiki.openstack.org/wiki/SDK-Development/PythonOpenStackSDK18:04
*** pballand has joined #openstack-meeting-318:04
*** johnthetubaguy has quit IRC18:04
jnollerFirst item: Roll call if you are here for the python sdk meeting!18:04
edleafeo/18:04
*** kudva has quit IRC18:04
jnollerJesse Noller, Rackspace18:04
*** johnthetubaguy has joined #openstack-meeting-318:04
edleafeEd Leafe, Rackspce18:04
wchrisjChris Johnson, HP18:05
Alex_GaynorAlex Gaynor18:05
dolphmthis meeting is an hour early in UTC18:05
jnollerit should be 1pm CST18:05
edleafeIt's 1pm CDT now18:05
jnollerI think daylight savings time just bit me ;)18:05
jnollerdolphm is right, technically it's now 2pm CDT18:06
*** mfer has joined #openstack-meeting-318:06
wchrisjIt's 2pm EDT18:06
jnollerAnyone mind us waiting the hour thanks to Daylight savings?18:07
glyphGlyph, Rackspace18:07
Alex_GaynorIf we wait an hour, I'll be at lunch18:07
edleafeyeah, let's start at the correct UTC time18:07
mferso, it'll start in an hour?18:07
* mfer thinks this is confusing18:08
jnollerYeah, daylight savings time messed it all up18:08
jnollermfer: 1900 UTC18:08
jnoller#endmeeting18:08
*** openstack changes topic to "Free for all (Meeting topic: Horizon)"18:08
openstackMeeting ended Tue Mar 11 18:08:49 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:08
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk_weekly_meeting/2014/python_openstacksdk_weekly_meeting.2014-03-11-18.03.html18:08
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk_weekly_meeting/2014/python_openstacksdk_weekly_meeting.2014-03-11-18.03.txt18:08
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk_weekly_meeting/2014/python_openstacksdk_weekly_meeting.2014-03-11-18.03.log.html18:08
jnollerlet's move back to -sdks18:09
*** jamielennox has joined #openstack-meeting-318:09
*** glyph has left #openstack-meeting-318:15
*** SumitNaiksatam_ has joined #openstack-meeting-318:27
*** SumitNaiksatam has quit IRC18:27
*** lpetrut has joined #openstack-meeting-318:29
*** SumitNaiksatam_ is now known as SumitNaiksatam18:29
*** mrunge has quit IRC18:32
*** pballand has quit IRC18:33
*** pballand has joined #openstack-meeting-318:38
*** pballand has quit IRC18:38
*** rajdeep has quit IRC18:38
*** johnthetubaguy has quit IRC18:39
*** devlaps1 has joined #openstack-meeting-318:48
*** devlaps has quit IRC18:48
*** SumitNaiksatam has quit IRC18:52
*** bknudson has joined #openstack-meeting-318:55
*** briancurtin has joined #openstack-meeting-318:59
*** lblanchard has quit IRC19:00
briancurtin#startmeeting python-openstacksdk19:00
openstackMeeting started Tue Mar 11 19:00:28 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
*** terrylhowe has left #openstack-meeting-319: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:00
briancurtin#link https://wiki.openstack.org/wiki/SDK-Development/PythonOpenStackSDK <- General Project Info19:01
briancurtinCould everyone here for the python-openstacksdk meeting state their name and affiliation?19:01
edleafeEd Leafe, Rackspace19:01
dtroyerDean Troyer,  Nebula19:01
briancurtinBrian Curtin, Rackspace19:01
jamielennoxJamie Lennox, Red Hat19:02
wchrisjChris Johnson, HP19:02
jnollerJesse Noller, Rackspace19:02
dolphmdolph mathews, rackspace19:02
*** jpomero has quit IRC19:02
briancurtinAlex_Gaynor: ping19:02
bknudsonBrant Knudson, IBM19:03
briancurtinSo the meeting agenda is pretty light, as there hasn't been a ton of movement, but the first item is discussion the identity example. Direction, etc19:03
briancurtin#topic https://review.openstack.org/#/c/79435/19:04
*** openstack changes topic to "https://review.openstack.org/#/c/79435/ (Meeting topic: python-openstacksdk)"19:04
briancurtinhopefully Alex_Gaynor comes in here, he was around earlier19:04
wchrisjdid he have lunch plans at this time?19:05
wchrisjsomeone did...19:05
jnollerhe did19:05
wchrisjIt was him19:05
wchrisjugh19:05
briancurtinoh, well moving on19:05
jnolleranyway; the primary contention here seems to httppretty19:05
jnollerwhich; has that been ported to python 3 yet?19:05
*** cjellick_ has quit IRC19:06
jnollerand the dependency on URLObject19:06
jamielennoxyes it has been ported to python 319:06
jnollerI do agree with alex re: the global monkey patching / magic stuff behind it19:07
jnollerI'm not a huge fan of those kinds of mocks/stubs19:07
bknudsonwe're using it in keystoneclient which passes python3319:07
jnollerbknudson: thanks, all I could recall were -dev discussions from a month or 3 ago19:08
jamielennoxjnoller: the advantage i've seen is that you are actually testing the code all the way through19:08
dolphmwhat does URLObject buy you here?19:08
jamielennoxyou actually test the request layer19:08
jamielennoxi completely agree with the global stuff in projects, but i think its fine for testing19:09
briancurtinif it does the trick and is working well elsewhere, i tend to agree19:09
jnollerjamielennox: part of this is that users want a lib (included with the sdk) of verified mocks/stubs/fakes that don't manipulate or monkeypatch19:09
jnollerso they can use those for testing as well19:10
jamielennoxjnoller: ok - that's new19:10
*** cjellick has joined #openstack-meeting-319:10
jnollerjamielennox: it's on the wiki19:10
bknudsonfor keystone, a verified mock would be essentially running it with kvs backends19:10
jnollerjamielennox: might need to call it out more19:10
dolphmauthorization scope is also completely ignored in that patch -- which is fine at rackspace, but doesn't fly in openstack19:10
bknudsonor sqlite.19:10
edleafejamielennox: It's important for an SDK, since it will be used as part of other projects19:10
*** cjellick has quit IRC19:10
briancurtinare there alternatives that do the same or similar stuff without global stuff?19:10
briancurtin(im not really familiar with this particular lib)19:11
jamielennoxbriancurtin: i don't think you can, it's patching at the socket level so it installs it globally19:11
jnollerbriancurtin: for http/requests you can use regular mocks or even betamax (which is an add on)19:11
*** cjellick has joined #openstack-meeting-319:11
jamielennoxmocking the requests interface is a PITA, you end up carrying these dictionaries of default arguments around19:11
jnollerI'm generally -1 on anything that patches sockets :( - but I'm also happy to reach out to Ian / Kenneth about better mocking for requests19:12
wchrisjif betamax is anything like it's cousin vcr (ruby), that would be worth considering imo19:12
jnollerBut I'm also just one voice :)19:12
briancurtinalso happy with that as well19:13
jnollerwchrisj: it was based on VCR19:13
wchrisjthat was my  thought19:13
jamielennoxif requests will provide support then that would be good19:13
wchrisjjnoller: ^^19:13
jamielennoxdoesn't VCR mock the socket as well?19:13
jnollerbetamax: https://pypi.python.org/pypi/betamax/0.1.619:13
briancurtinjnoller: does httpretty entirely fail the mock/stub thing, or is it just subpar? (not that i want to start this off with subpar stuff, just trying to understand where it fits)19:13
jnollerbriancurtin: I want to confirm with Alex_Gaynor19:13
briancurtinso i guess we have a couple of action points to work out19:14
jnollerbriancurtin: Anything that's monkeying with too much global state or monkey patching builtins is not a plus in my mind - especially if we want swappable tcp / http transports like Alex_Gaynor is proposing19:14
briancurtinagreed/makes sense19:15
jnollerbriancurtin: Ideally our test mocks / stubs can be used by end users building applications19:15
briancurtin#topic look into better mocking with requests (check with Kenneth et. al)19:15
*** openstack changes topic to "look into better mocking with requests (check with Kenneth et. al) (Meeting topic: python-openstacksdk)"19:15
briancurtinah crap, sorry, meant action19:15
briancurtin#action look into better mocking with requests (check with Kenneth et. al)19:15
jnollerThe other point on that change is the dependency on https://urlobject.readthedocs.org/en/latest/quickstart.html19:16
jamielennoxjnoller: i disagree, httpretty was adopted initially because it does deal with multiple HTTP transports. Because you mock at the socket layer it doesn't matter who makes the HTTP call19:16
jamielennoxif you use httplib or requests or whatever you will get the same response19:16
briancurtin#action confirm state of HTTPretty usability with regard to verifying mocks/stubs19:16
briancurtin#topic using URLObject19:17
*** openstack changes topic to "using URLObject (Meeting topic: python-openstacksdk)"19:17
jamielennox(if it clashes with a goal i understand not using it, just pointing out)19:17
bknudsondoes mocks/stubs here mean a fake keystone server?19:17
jnollerjamielennox: global patching socket objects side-effects end users in surprising/unexpected ways though - I see both sides honestly19:17
jnollerbknudson: in memory fake; not a running /forked daemon19:17
jamielennoxjnoller: it's testing code, users shouldn't care19:17
jnoller?19:17
bknudsonseems like it would be easier to make it so that keystone can run in-memory rather than develop a fake keystone.19:18
jamielennoxdepends on the goal, if you mean internal testing then i don't know why users care what you use, if you want to export that testing to others then sure we don't want to export global state19:18
jnollerWhat we use for testing should be what we recommend users use for testing - eating our own dogfood19:19
jnollerbknudson: that means an in memory version of a LOT of things (you're going to need a full in memory openstack system)19:20
jamielennoxthere's recommend and then there's here use all this stuff we've developed to help you19:20
jnollerIf we ship fakes/mocks/stubs we should be using the same ones - so the latter19:20
bknudsonjnoller: yes, keystone is probably simpler than some of the other things that will need to be faked19:20
jnollerPersonally: I would not make a recommendation for testing like this without the test suite for the sdk itself relying on it and shipping the verified mocks/stubs19:21
briancurtinbut we have a few levels of users to care about. end-users building products on this, vendors building extensions on this, etc. some end-users may not care, but i can see vendor users/devs caring19:22
*** briancurtin has left #openstack-meeting-319:22
jnollerBut, we need to clarify this for sure19:22
*** briancurtin has joined #openstack-meeting-319:22
jamielennoxjnoller: ok, when i wrote the httpretty comment i wasn't aware we were considering exporting mocks, in that case i wouldn't want to export something that globally patched objects19:23
jnollerbriancurtin: I added that to the wiki as it was like #2 or #3 on the most-requested-for-a-real-sdk things when I asked at large (verified testing stuff)19:23
jnollerjamielennox: Yeah, we should definitely dig into it19:23
briancurtinyes19:23
jnollerNext on Alex's patch is urlobject19:23
*** sarob_ has quit IRC19:24
*** sarob_ has joined #openstack-meeting-319:25
jnollerLooking at it; he doesn't make extensive use of it, but reading the docs I can see why he's using it19:25
briancurtinwhat does urlobject buy us?19:25
briancurtin(havent read those docs yet)19:25
jnollerit *seems* like a much better way of managing urls -> https://urlobject.readthedocs.org/en/latest/quickstart.html19:25
jnollerFor example19:25
jnoller>>> print(url.with_auth('alice', '1234'))19:25
jnollerhttps://alice:1234@github.com/zacharyvoase/urlobject?spam=eggs#foo19:25
bknudsonurlobjects looks safer than dealing with urls as strings.19:26
jnollerYou get out of the URL parsing / building / string concatenation game19:26
wchrisj+119:26
jnollerbknudson: exactly (I've been bitten a LOT by treating them like strings)19:26
jnollerurl = blah + var + '/whee:' : port :(19:27
briancurtinseems reasonable to me at first glance, and jamie's comment wasn't strong one way or another. Ed did bring up the point to minimize dependencies, but this seems valuable19:27
dolphmurlobject has no other deps19:27
jamielennoxsure, happy to not have to do URL building - i don't care either way on this one, if we get it past requirements then we should use it - else no great loss19:28
edleafeJust quoting from the original design criteria for the SDK19:28
jnollerI want to minimize dependencies, but I also don't want to fail boat on url management19:28
jnollerthis basically means: requests + urlobject19:28
jnollerwhich doesn't seem *terrible* as it still avoids the N+K dependencies creep19:29
dtroyerno but it's a bit ironic that the first code patch adda a new dependency...19:29
dolphmit's not in global requirements though, which just means no one else is using it yet19:29
*** sarob_ has quit IRC19:29
briancurtin(sorry, bad conference wifi)19:29
jnollerdtroyer: yeah :(19:30
dolphmjnoller: i'd simply like to have a reasonable explanation for needing every dependency; this seems to be one we'd use extensively, and it's light so ++19:30
briancurtinagree19:31
wchrisjagree19:31
jamielennox++19:31
jnollerdolphm: Ok, Alex_Gaynor needs to document (in a blueprint) why using this (and adding it to global-requirements) is a positive19:31
briancurtin#action Alex_Gaynor outline a justification of why to use URLObject and add it as a dependency19:31
jnollerIts not like installing its own wsgi server ;)19:32
dolphmjnoller: not that there's anything wrong with that, right?19:32
jnollerhaha19:32
dtroyerbut it's also not packaged in Ubuntu yet…so yet one more step to completion19:33
jnollerdolphm brought up some good rackspace-isms in Alex_Gaynor's patch that have to be excised19:33
jnollerdtroyer: good catch19:33
*** markmcclain has quit IRC19:34
briancurtinyeah that'll be a good thing to cover in the BP19:34
*** markmcclain has joined #openstack-meeting-319:34
jnollerSo, Alex has some refinement to do19:35
dolphmblueprints effectively get lost after they're implemented though... they "why" might be better preserved in a commit message19:35
dolphmthe*19:35
jnollerdolphm: commit message and the wiki19:35
briancurtindolphm: is this better to be laid out in a wiki, and then condensed into a commit19:36
briancurtinmind reader19:36
briancurtinso, ok, have some research to do on HTTPretty, requests mocking, URLObject. what else do we have with the example so far?19:37
jnollerbriancurtin: remove the rackspace-isms19:37
jnollerdolphm did a great job pointing those out19:38
briancurtin#action Alex_Gaynor remove Rackspace-isms in example code, as pointed out by dolphm19:38
bknudsonwhat's the "validated stub/mock" in this patch? https://review.openstack.org/#/c/79435/5/openstack/tests/test_auth.py ?19:38
*** sarob_ has joined #openstack-meeting-319:40
*** sarob_ has quit IRC19:41
jnoller@bknudson: good question for Alex_Gaynor19:41
jnollerbriancurtin: anything else for us to review? It seems everyone got busy with conferences and icehouse so our goal should be to focus on more BP / commits like the one Alex_Gaynor did so we can discuss those going into next week19:42
briancurtini think that's it on review for right now. should we take the last 20 or so min and talk about what, if anything we want to have at the design summit?19:42
dolphmdtroyer: i saw you added another line break to the requirements files, what happened there?19:43
dolphm(there's two line breaks at the end of the file now)19:43
dolphmwhich is definitely better than zero and a broken jenkins19:43
Alex_Gaynor(I'm present now)19:43
jnollerpfft food19:44
dtroyerit was part of trying to figure out what it took to get any of those changes through...19:44
dtroyerint he end we needed to just disable the test due to the way it was written19:44
dtroyercan be cleaned up now19:44
dolphmdtroyer: ack19:44
briancurtin#topic Design Summit topic(s)19:44
*** openstack changes topic to "Design Summit topic(s) (Meeting topic: python-openstacksdk)"19:44
briancurtinwith 15 minutes left, anything input as to what, if anything, should be submitted for the design summit?19:45
jnollerbriancurtin: I submitted a design summit session today on this and developer experience/cloud consumer stuff19:45
briancurtini'm not familiar with how this goes, so i would appreciate some insight into what we can do, how we should do it, etc.19:45
briancurtinjnoller: can you link to it?19:46
wchrisjNew for me too19:46
jnollery19:46
jnollerone second19:46
dolphmjnoller: i don't see one...19:46
dolphmah http://summit.openstack.org/cfp/details/3419:46
jnollerhttp://summit.openstack.org/cfp/details/3419:46
briancurtinnot knowing how broad or narrow these things go, should this project be on its own, or should it be a part of the greater experience stuff?19:47
jnollerbriancurtin: I'm open to suggestions on that too19:48
jnollerbriancurtin: too narrow worries me, I'd like to avoid a monoculture when looking at the personas/users19:49
briancurtini just don't really know. i think there's certainly value in getting together on the greater topic, and getting with teh PHP, Ruby, Go, etc folks19:49
edleafebriancurtin: The design summit sessions are where everyone concerned makes decisions on how to proceed over the next 6 months. The sessions should be very specific19:49
briancurtinyep19:49
dolphmrelated: User Experience Designers Gathering http://summit.openstack.org/cfp/details/3319:49
jnollerdolphm: yes, that one is very focused on horizon19:49
briancurtinedleafe: so should there be a python session, php session, ruby sess, etc?19:49
edleafeideally, yes19:49
Alex_Gaynordolphm: Will get a patch up to address your concerns after the meeting.19:49
edleafeA lot of what we will discuss has nothing to do with ruby or php19:50
dolphmjnoller: ++ it's on the "Other projects" track though - any idea why? (or what that track is for?)19:50
briancurtindo we then push for *both* avenues? individual to suss out a lot of our specific things, but also unified to gather common direction?19:50
jnollerdolphm: No idea, I saw it this morning19:50
jnollerbriancurtin: good idea19:50
jnollerbetter than mine!19:50
wchrisjbriancurtin: +119:50
dtroyerbriancurtin: ideally, yes19:50
edleafebriancurtin: it depends on what aspects of the design you need to work on19:50
dtroyergiven a choice and the stage we're in, python-specific if we can only do one19:51
jnollerI will say mfer and others here have been making progress on the other SDKs too (php, go, etc)19:52
edleafedtroyer: yeah, given that we don't have anything to go on, generic is probably all we can do19:52
jnollerthe goals are pretty aligned19:52
edleafejnoller: aren't they working from an established code base?19:53
jnolleredleafe: they're all shifting into 2.0 clean room modes19:53
dolphmjnoller: where are the non-python sdk's on github?19:53
jnolleredleafe: much like this one19:53
jnollerdolphm: hold on, need to find all the links19:54
dolphmjnoller: and is there any desire to get them into stackforge? (has that been discussed?)19:54
mferis this something we should continue in the #openstack-sdks room?19:54
dtroyerGo: http://git.openstack.org/cgit/stackforge/golang-client/19:54
jnollermfer: true19:54
mferdolphm a number of them are going into stackforge already19:54
jnollersorry, lack of focus19:54
jnolleredleafe: think you can work with alex to flesh out more of the identity stuff?19:55
edleafeI'19:56
edleafeoops19:56
edleafeI'd have to discuss with him what his goal is with the code - not entirely clear to me yet19:56
briancurtinif people aren't hounding us at this conference, i'm around to help out with it19:58
jamielennoxlet me know any issues you have with identity, though i realize i'm not in most peoples TZ19:58
jnollerok, let's see if we can do that and keep more going into the repo for discussion19:58
briancurtinfeed the machine with code19:58
*** d0ugal has joined #openstack-meeting-319:58
*** d0ugal has quit IRC19:58
*** d0ugal has joined #openstack-meeting-319:58
jnollerjamielennox: I don't even know what TZ I'm in right now so it's cool19:58
briancurtinwhat even is time19:58
briancurtinso i think that's probably it, anything as the clock winds down?19:59
jnollerNope!19:59
wchrisjI'll get with Alex_Gaynor: and help as well19:59
dolphmglad to see everyone here :)19:59
briancurtin#endmeeting19:59
*** openstack changes topic to "Free for all (Meeting topic: Horizon)"19:59
openstackMeeting ended Tue Mar 11 19:59:55 2014 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:59
*** bknudson has left #openstack-meeting-319:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-11-19.00.html19:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-11-19.00.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-11-19.00.log.html20:00
*** jnoller has quit IRC20:02
*** mwagner_lap has joined #openstack-meeting-320:03
*** dtroyer has left #openstack-meeting-320:18
*** Alex_Gaynor has left #openstack-meeting-320:20
*** freerider has joined #openstack-meeting-320:30
*** freerider is now known as Guest660720:31
*** pballand has joined #openstack-meeting-320:35
*** d0ugal_ has joined #openstack-meeting-320:38
*** d0ugal has quit IRC20:39
*** julim has quit IRC20:40
*** Guest6607 has quit IRC20:42
*** d0ugal_ has quit IRC20:43
*** lesotorg has joined #openstack-meeting-320:44
*** d0ugal_ has joined #openstack-meeting-320:45
*** mwagner_lap has quit IRC20:47
*** lesotorg has quit IRC20:47
*** SumitNaiksatam has joined #openstack-meeting-320:51
*** sarob_ has joined #openstack-meeting-320:51
*** SumitNaiksatam has quit IRC21:00
*** jthopkin has joined #openstack-meeting-321:03
*** izmocherovy has joined #openstack-meeting-321:21
*** izmocherovy has quit IRC21:24
*** HenryG has quit IRC21:28
*** peristeri has quit IRC21:28
*** alexpilotti has quit IRC21:28
*** ftcjeff has quit IRC21:28
*** sarob_ has quit IRC21:28
*** d0ugal_ has quit IRC21:28
*** devlaps1 has quit IRC21:28
*** lcheng has quit IRC21:28
*** edhall has quit IRC21:28
*** briancurtin has quit IRC21:28
*** amrith has quit IRC21:28
*** annegentle has quit IRC21:28
*** cjellick has quit IRC21:28
*** lpetrut has quit IRC21:28
*** wchrisj has quit IRC21:28
*** mfer has quit IRC21:28
*** david-lyle has quit IRC21:28
*** eghobo has quit IRC21:28
*** yamahata has quit IRC21:28
*** jtomasek has quit IRC21:28
*** dhellmann has quit IRC21:28
*** lsmola has quit IRC21:28
*** cgoncalves has quit IRC21:28
*** yamahata_ has quit IRC21:28
*** jamielennox has quit IRC21:28
*** ttrifonov has quit IRC21:28
*** jthopkin has quit IRC21:28
*** pballand has quit IRC21:28
*** jeblair has quit IRC21:28
*** enykeev has quit IRC21:28
*** SergeyLukjanov has quit IRC21:28
*** DinaBelova has quit IRC21:28
*** haleyb has quit IRC21:28
*** notmyname has quit IRC21:28
*** lifeless has quit IRC21:28
*** markmcclain has quit IRC21:28
*** dolphm has quit IRC21:28
*** Adri2000 has quit IRC21:28
*** troytoman-away has quit IRC21:28
*** timello has quit IRC21:29
*** wendar has quit IRC21:29
*** ttx has quit IRC21:29
*** mikal has quit IRC21:29
*** anteaya has quit IRC21:29
*** jomara has quit IRC21:29
*** Adri2000 has joined #openstack-meeting-321:30
*** pballand has joined #openstack-meeting-321:30
*** pballand has quit IRC21:32
*** lcheng has joined #openstack-meeting-321:38
*** edhall has joined #openstack-meeting-321:41
*** wendar has joined #openstack-meeting-321:41
*** timello has joined #openstack-meeting-321:41
*** sarob has joined #openstack-meeting-321:41
*** amrith has joined #openstack-meeting-321:41
*** devlaps has joined #openstack-meeting-321:41
*** briancurtin has joined #openstack-meeting-321:41
*** annegentle has joined #openstack-meeting-321:41
*** troytoman-away has joined #openstack-meeting-321:41
*** ttx has joined #openstack-meeting-321:41
*** pballand has joined #openstack-meeting-321:41
*** HenryG_ has joined #openstack-meeting-321:41
*** dolphm has joined #openstack-meeting-321:41
*** mikal has joined #openstack-meeting-321:41
*** markmcclain1 has joined #openstack-meeting-321:41
*** jthopkin has joined #openstack-meeting-321:41
*** cjellick has joined #openstack-meeting-321:41
*** jamielennox has joined #openstack-meeting-321:41
*** david-lyle has joined #openstack-meeting-321:41
*** eghobo has joined #openstack-meeting-321:41
*** wchrisj has joined #openstack-meeting-321:41
*** yamahata has joined #openstack-meeting-321:41
*** jtomasek has joined #openstack-meeting-321:41
*** jeblair has joined #openstack-meeting-321:41
*** cgoncalves has joined #openstack-meeting-321:41
*** yamahata_ has joined #openstack-meeting-321:41
*** dhellmann has joined #openstack-meeting-321:41
*** enykeev has joined #openstack-meeting-321:41
*** lsmola has joined #openstack-meeting-321:41
*** ttrifonov has joined #openstack-meeting-321:41
*** SergeyLukjanov has joined #openstack-meeting-321:41
*** DinaBelova has joined #openstack-meeting-321:41
*** haleyb has joined #openstack-meeting-321:41
*** notmyname has joined #openstack-meeting-321:41
*** jomara has joined #openstack-meeting-321:41
*** anteaya has joined #openstack-meeting-321:41
*** lifeless has joined #openstack-meeting-321:41
*** pballand has quit IRC21:42
*** Adri2000 is now known as Guest6828321:42
*** markmcclain1 has quit IRC21:51
*** jpomero has joined #openstack-meeting-321:55
*** edhall has quit IRC22:03
*** sarob has quit IRC22:03
*** sarob has joined #openstack-meeting-322:04
*** jthopkin has quit IRC22:05
*** edhall has joined #openstack-meeting-322:05
*** sarob has quit IRC22:09
*** jpomero has quit IRC22:13
*** skath has joined #openstack-meeting-322:13
*** pballand has joined #openstack-meeting-322:15
*** pballand has quit IRC22:22
*** pballand has joined #openstack-meeting-322:28
*** Sukhdev has joined #openstack-meeting-322:36
*** edhall has quit IRC22:40
*** yamahata has quit IRC22:43
*** openstackstatus has joined #openstack-meeting-322:44
*** edhall has joined #openstack-meeting-322:44
*** wchrisj has quit IRC22:48
*** OSM has joined #openstack-meeting-323:00
*** OSM is now known as songole23:07
*** pballand has quit IRC23:07
*** david-lyle has quit IRC23:08
*** songole has quit IRC23:09
*** lcheng has quit IRC23:31
*** mwagner_lap has joined #openstack-meeting-323:45

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