*** lblanchard has joined #openstack-meeting-3 | 00:15 | |
*** yamahata__ has joined #openstack-meeting-3 | 00:24 | |
*** wchrisj has quit IRC | 00:39 | |
*** wchrisj has joined #openstack-meeting-3 | 00:41 | |
*** yamahata has joined #openstack-meeting-3 | 00:42 | |
*** wchrisj has quit IRC | 00:43 | |
*** wchrisj has joined #openstack-meeting-3 | 00:55 | |
*** devlaps has quit IRC | 00:55 | |
*** SumitNaiksatam has joined #openstack-meeting-3 | 01:02 | |
*** lblanchard has quit IRC | 01:20 | |
*** wchrisj has quit IRC | 01:22 | |
*** alexpilotti has quit IRC | 01:40 | |
*** wchrisj has joined #openstack-meeting-3 | 01:53 | |
*** yamahata has quit IRC | 02:11 | |
*** yamahata__ has quit IRC | 02:12 | |
*** jpomero has quit IRC | 02:43 | |
*** Sukhdev has joined #openstack-meeting-3 | 02:57 | |
*** markmcclain has quit IRC | 04:00 | |
*** david-lyle has joined #openstack-meeting-3 | 04:08 | |
*** yamahata__ has joined #openstack-meeting-3 | 04:11 | |
*** yamahata has joined #openstack-meeting-3 | 04:12 | |
*** markmcclain has joined #openstack-meeting-3 | 04:14 | |
*** wchrisj has quit IRC | 04:24 | |
*** wchrisj has joined #openstack-meeting-3 | 04:54 | |
*** eghobo has joined #openstack-meeting-3 | 04:57 | |
*** Sukhdev has quit IRC | 04:57 | |
*** wchrisj has quit IRC | 05:04 | |
*** edhall has quit IRC | 05:44 | |
*** edhall has joined #openstack-meeting-3 | 05:55 | |
*** lpetrut has joined #openstack-meeting-3 | 06:00 | |
*** eghobo has quit IRC | 06:07 | |
*** eghobo has joined #openstack-meeting-3 | 06:08 | |
*** eguz has joined #openstack-meeting-3 | 06:09 | |
*** eghobo has quit IRC | 06:09 | |
*** eguz has quit IRC | 06:11 | |
*** tmazur has joined #openstack-meeting-3 | 06:17 | |
*** eghobo has joined #openstack-meeting-3 | 06:41 | |
*** mrunge has joined #openstack-meeting-3 | 07:18 | |
*** mrunge has joined #openstack-meeting-3 | 07:18 | |
*** MaxV has joined #openstack-meeting-3 | 07:29 | |
*** MaxV has quit IRC | 07:30 | |
*** markmcclain has quit IRC | 07:53 | |
*** yamahata has quit IRC | 08:14 | |
*** yamahata__ has quit IRC | 08:15 | |
*** eghobo has quit IRC | 08:18 | |
*** jcoufal has joined #openstack-meeting-3 | 08:24 | |
*** tmazur has quit IRC | 08:27 | |
*** yamahata__ has joined #openstack-meeting-3 | 08:30 | |
*** yamahata has joined #openstack-meeting-3 | 08:30 | |
*** nacim has joined #openstack-meeting-3 | 08:32 | |
*** lpetrut has quit IRC | 08:59 | |
*** jcoufal has quit IRC | 09:00 | |
*** jcoufal_ has joined #openstack-meeting-3 | 09:00 | |
*** jcoufal_ has quit IRC | 09:02 | |
*** yamahata has quit IRC | 09:04 | |
*** yamahata__ has quit IRC | 09:04 | |
*** jrist has quit IRC | 09:07 | |
*** MaxV has joined #openstack-meeting-3 | 09:14 | |
*** jcoufal has joined #openstack-meeting-3 | 09:15 | |
*** johnthetubaguy has joined #openstack-meeting-3 | 09:19 | |
*** jrist has joined #openstack-meeting-3 | 09:21 | |
*** lpetrut has joined #openstack-meeting-3 | 09:31 | |
*** johnthetubaguy has quit IRC | 09:44 | |
*** johnthetubaguy has joined #openstack-meeting-3 | 09:44 | |
*** johnthetubaguy1 has joined #openstack-meeting-3 | 09:57 | |
*** johnthetubaguy has quit IRC | 10:01 | |
*** saju_m has joined #openstack-meeting-3 | 10:05 | |
*** yamahata__ has joined #openstack-meeting-3 | 10:08 | |
*** yamahata has joined #openstack-meeting-3 | 10:09 | |
*** saju_m has quit IRC | 10:18 | |
*** tshirtman has quit IRC | 10:22 | |
*** tshirtman has joined #openstack-meeting-3 | 10:22 | |
*** saju_m has joined #openstack-meeting-3 | 10:31 | |
*** akrivoka has joined #openstack-meeting-3 | 10:34 | |
*** saju_m has quit IRC | 10:54 | |
*** johnthetubaguy1 has quit IRC | 11:09 | |
*** MaxV has quit IRC | 11:36 | |
*** jtomasek has quit IRC | 11:46 | |
*** jrist has quit IRC | 11:58 | |
*** jtomasek has joined #openstack-meeting-3 | 12:00 | |
*** yamahata__ has quit IRC | 12:04 | |
*** yamahata has quit IRC | 12:09 | |
*** MaxV has joined #openstack-meeting-3 | 12:14 | |
*** MaxV has quit IRC | 12:18 | |
*** david-lyle has quit IRC | 12:21 | |
*** wchrisj has joined #openstack-meeting-3 | 12:29 | |
*** wchrisj has quit IRC | 12:29 | |
*** MaxV has joined #openstack-meeting-3 | 12:35 | |
*** xuhanp has joined #openstack-meeting-3 | 12:37 | |
*** mwagner_lap has quit IRC | 13:00 | |
*** alexpilotti has joined #openstack-meeting-3 | 13:05 | |
*** lblanchard has joined #openstack-meeting-3 | 13:08 | |
*** yamahata__ has joined #openstack-meeting-3 | 13:11 | |
*** jpomero has joined #openstack-meeting-3 | 13:11 | |
*** yamahata__ has quit IRC | 13:15 | |
*** yamahata__ has joined #openstack-meeting-3 | 13:16 | |
*** julim has joined #openstack-meeting-3 | 13:18 | |
*** yamahata__ has quit IRC | 13:21 | |
*** yamahata__ has joined #openstack-meeting-3 | 13:22 | |
*** jrist has joined #openstack-meeting-3 | 13:26 | |
*** yamahata has joined #openstack-meeting-3 | 13:26 | |
*** yamahata__ has quit IRC | 13:27 | |
*** yamahata__ has joined #openstack-meeting-3 | 13:28 | |
*** johnthetubaguy has joined #openstack-meeting-3 | 13:28 | |
*** wchrisj has joined #openstack-meeting-3 | 13:28 | |
*** yamahata__ has quit IRC | 13:30 | |
*** yamahata__ has joined #openstack-meeting-3 | 13:31 | |
*** yamahata__ has quit IRC | 13:34 | |
*** jpich has joined #openstack-meeting-3 | 13:34 | |
*** yamahata__ has joined #openstack-meeting-3 | 13:35 | |
*** mfer has joined #openstack-meeting-3 | 13:37 | |
*** yamahata has quit IRC | 13:41 | |
*** yamahata has joined #openstack-meeting-3 | 13:41 | |
*** yamahata__ has quit IRC | 13:43 | |
*** yamahata__ has joined #openstack-meeting-3 | 13:47 | |
*** ftcjeff has joined #openstack-meeting-3 | 13:48 | |
*** jcoufal has quit IRC | 13:50 | |
*** yamahata__ has quit IRC | 13:50 | |
*** absubram___ has joined #openstack-meeting-3 | 13:51 | |
*** yamahata__ has joined #openstack-meeting-3 | 13:51 | |
*** peristeri has joined #openstack-meeting-3 | 13:57 | |
*** yamahata__ has quit IRC | 13:59 | |
*** yamahata__ has joined #openstack-meeting-3 | 14:05 | |
*** yamahata__ has quit IRC | 14:09 | |
*** alexpilotti has quit IRC | 14:10 | |
*** peristeri has quit IRC | 14:12 | |
*** peristeri has joined #openstack-meeting-3 | 14:16 | |
*** alexpilotti has joined #openstack-meeting-3 | 14:19 | |
*** xuhanp has quit IRC | 14:23 | |
*** david-lyle has joined #openstack-meeting-3 | 14:26 | |
*** xuhanp has joined #openstack-meeting-3 | 14:27 | |
*** mrunge has quit IRC | 14:31 | |
*** markmcclain has joined #openstack-meeting-3 | 14:33 | |
*** wchrisj has quit IRC | 14:38 | |
*** jcoufal has joined #openstack-meeting-3 | 14:40 | |
*** lcheng has joined #openstack-meeting-3 | 14:42 | |
*** jrist has quit IRC | 14:43 | |
*** devlaps has joined #openstack-meeting-3 | 14:46 | |
*** dtroyer has joined #openstack-meeting-3 | 14:47 | |
*** peristeri has quit IRC | 14:49 | |
*** jthopkin has joined #openstack-meeting-3 | 14:53 | |
*** lcostantino has joined #openstack-meeting-3 | 14:57 | |
*** peristeri has joined #openstack-meeting-3 | 15:00 | |
*** lcostantino has left #openstack-meeting-3 | 15:02 | |
*** wchrisj has joined #openstack-meeting-3 | 15:02 | |
*** nacim has quit IRC | 15:03 | |
*** jcoufal has quit IRC | 15:06 | |
*** jcoufal has joined #openstack-meeting-3 | 15:07 | |
*** johnthetubaguy1 has joined #openstack-meeting-3 | 15:07 | |
*** fungi has quit IRC | 15:07 | |
*** johnthetubaguy has quit IRC | 15:10 | |
*** jcoufal has quit IRC | 15:12 | |
*** jcoufal has joined #openstack-meeting-3 | 15:13 | |
*** cjellick has joined #openstack-meeting-3 | 15:19 | |
*** nacim has joined #openstack-meeting-3 | 15:21 | |
*** cjellick_ has joined #openstack-meeting-3 | 15:22 | |
*** cjellick_ has quit IRC | 15:22 | |
*** cjellick_ has joined #openstack-meeting-3 | 15:23 | |
*** cjellick has quit IRC | 15:24 | |
*** jcoufal has quit IRC | 15:25 | |
*** johnthetubaguy1 has quit IRC | 15:40 | |
*** johnthetubaguy has joined #openstack-meeting-3 | 15:42 | |
*** thinrichs has joined #openstack-meeting-3 | 15:44 | |
*** jcoufal-mobile has joined #openstack-meeting-3 | 15:45 | |
*** fungi has joined #openstack-meeting-3 | 15:46 | |
*** eghobo has joined #openstack-meeting-3 | 15:53 | |
*** tmazur has joined #openstack-meeting-3 | 15:53 | |
*** pballand has joined #openstack-meeting-3 | 15:57 | |
*** tzumainn has joined #openstack-meeting-3 | 15:57 | |
*** mrunge has joined #openstack-meeting-3 | 15:59 | |
*** jcoufal has joined #openstack-meeting-3 | 16:00 | |
david-lyle | #startmeeting Horizon | 16:01 |
---|---|---|
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 16:01 |
*** openstack changes topic to " (Meeting topic: Horizon)" | 16:01 | |
openstack | The meeting name has been set to 'horizon' | 16:01 |
david-lyle | Hello everyone! | 16:01 |
akrivoka | hi everyone | 16:01 |
jcoufal | o/ | 16:01 |
absubram___ | hey | 16:01 |
mrunge | o/ | 16:01 |
jpich | Hey | 16:01 |
lblanchard | hi all | 16:01 |
lcheng | o/ | 16:02 |
tmazur | hello o/ | 16:02 |
*** rajdeep has joined #openstack-meeting-3 | 16:02 | |
david-lyle | https://wiki.openstack.org/wiki/Meetings/Horizon | 16:02 |
david-lyle | #topic Welcome Radomir to Horizon Core | 16:03 |
*** openstack changes topic to "Welcome Radomir to Horizon Core (Meeting topic: Horizon)" | 16:03 | |
*** SumitNaiksatam has quit IRC | 16:03 | |
david-lyle | As of yesterday, Radomir was officially added to Horizon core. | 16:03 |
jcoufal | Radomir is not here, but I am happy for him! :) | 16:04 |
mrunge | thank you david-lyle ! and well deserved Radomir! | 16:04 |
david-lyle | Radomir has made many contributions, reviews and is highly involved in the tuskar-ui effort. | 16:04 |
*** johnthetubaguy1 has joined #openstack-meeting-3 | 16:04 | |
lblanchard | yes, congrats to Radomir!! | 16:04 |
david-lyle | A welcome addition | 16:04 |
jpich | Agreed | 16:04 |
akrivoka | definitely well deserved | 16:04 |
david-lyle | So congratulations to Radomir and thanks. | 16:04 |
lcheng | congrats to Radomir! | 16:05 |
david-lyle | #topic Icehouse RC1 | 16:05 |
*** openstack changes topic to "Icehouse RC1 (Meeting topic: Horizon)" | 16:05 | |
david-lyle | https://launchpad.net/horizon/+milestone/icehouse-rc1 | 16:05 |
*** johnthetubaguy has quit IRC | 16:05 | |
david-lyle | we're looking good on the FFEs | 16:05 |
jpich | david-lyle: Isn't the Django 1.6 one pretty much implemented now that the requirement change has gone through? | 16:06 |
jomara | congrats radomir! | 16:06 |
david-lyle | the 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 testing | 16:06 |
*** pballand has quit IRC | 16:06 | |
*** rajdeep has quit IRC | 16:06 | |
david-lyle | we can probably call it implemented | 16:06 |
*** xuhanp has quit IRC | 16:07 | |
david-lyle | I also will release openstack_auth with a tox env to test 1.5 still | 16:07 |
mrunge | great, david-lyle! good that it landed | 16:07 |
david-lyle | mrunge: was worried for a while :) | 16:07 |
jpich | Great | 16:08 |
david-lyle | https://blueprints.launchpad.net/horizon/+spec/per-user-quotas is the last FFE open | 16:08 |
jpich | david-lyle: https://review.openstack.org/#/c/32884/ (the django 1.4 job) may provide a few hints for the infra job, fwiw | 16:08 |
david-lyle | ooh, nice, I just tracked down the yaml file thanks to infra, but looks like I needed another piece | 16:09 |
*** gokul_ has joined #openstack-meeting-3 | 16:09 | |
david-lyle | thanks jpich | 16:09 |
absubram___ | david-lyle: For my FFE - https://blueprints.launchpad.net/horizon/+spec/neutron-subnet-mode-support.. I had to update my review today | 16:09 |
absubram___ | the neutron side is still in review.. but some changes had been made | 16:10 |
david-lyle | absubram___, I think this will slip until Juno | 16:10 |
david-lyle | FFEs should be merged by today | 16:10 |
absubram___ | ok.. that's fine | 16:10 |
david-lyle | since neutron is not there, we can't really do much | 16:11 |
absubram___ | sure | 16:11 |
absubram___ | I think they are still targeting I :) | 16:11 |
david-lyle | sure | 16:11 |
mrunge | everybody is targeting Icehouse... | 16:11 |
david-lyle | they _may_ land it today, or get more time, but that puts us out pretty far | 16: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 it | 16:12 |
absubram___ | and that change is breaking UT :(.. so need to fix it.. | 16:12 |
absubram___ | but yeah.. pushing this out to J makes sense | 16:12 |
absubram___ | mrunge: lol | 16:13 |
david-lyle | absubram___, thanks for your effort here, unfortunately things didn't line up right | 16:13 |
david-lyle | absubram___, I'll wait til the program status meeting today to push to Juno based on neutron team feedback | 16: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 stable | 16:14 |
absubram___ | sounds good.. thanks david | 16:15 |
david-lyle | the per-user-quota FFE needs to either merge today by the program team meeting 21:00 UTC or it too will push to Juno | 16:15 |
david-lyle | I have not had a chance to review it yet | 16:16 |
david-lyle | seems to be a common theme on that bp | 16:16 |
*** wchrisj has quit IRC | 16:17 | |
*** wchrisj has joined #openstack-meeting-3 | 16:17 | |
david-lyle | and last for rc1, are there any bugs that aren't assigned to the milestone that should be? | 16:18 |
david-lyle | I must admit, I'm behind on the bug triage, so please target any that are high priority | 16:18 |
mrunge | or feel free to ping anyone else than david-lyle | 16:19 |
mrunge | e.g me | 16:19 |
absubram___ | yes please :).. I have a few reviews out.. all are specific to the 'router' dashboard side | 16:19 |
jpich | Or leave a comment so that people with triaging powerz can set it accordingly | 16:19 |
*** jrist has joined #openstack-meeting-3 | 16:19 | |
akrivoka | can we target this one please? https://bugs.launchpad.net/horizon/+bug/1288698 | 16:20 |
mrunge | oh yes absubram___ you should use that plugin style for the router dashboard | 16:20 |
akrivoka | (fix is already implemented, just needs one more core review) | 16:20 |
mrunge | akrivoka, done | 16:20 |
akrivoka | mrunge: 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 nits | 16:21 |
absubram___ | well… not very minor :) | 16:21 |
jcoufal | regarding the accordion style, should we those minor things and smaller styling consider as bugs for Havana? | 16:21 |
jcoufal | sorry | 16:21 |
jcoufal | Icehouse :) | 16:21 |
jcoufal | I am obviously one milestone behind :) | 16:22 |
mrunge | jcoufal, a release behind? | 16:22 |
david-lyle | jcoufal, can you be more specific? | 16:22 |
jcoufal | oh dear | 16:22 |
jcoufal | david-lyle: sure | 16:22 |
jcoufal | well | 16:22 |
david-lyle | if there are errors we should certainly fix them | 16:23 |
jcoufal | there were no errors more smaller corrections which you also mentioned previously | 16:23 |
jcoufal | and we also discussed the styling enhancements in time | 16: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/1260436 | 16:24 |
absubram___ | all are in review.. and would love to get them into rc1 if possible :) | 16:24 |
jcoufal | so I was just wondering if those are considered as bugs or features for Juno | 16:24 |
*** pballand has joined #openstack-meeting-3 | 16:25 | |
jcoufal | like project picker | 16:25 |
mrunge | jcoufal, could you please be *more* specific? | 16:25 |
david-lyle | likely features for Juno, as we are really in the hardening phase of the release cycle, but it's likely a case by case basis | 16:25 |
mrunge | jcoufal, or do you have a patch ready? | 16:25 |
david-lyle | jcoufal, I would like the picker improved, to match the design, but at this point, it's not a small change | 16:26 |
jcoufal | mrunge: nope, I was just wondering how it is considered, so case by case is valid answer | 16:26 |
jcoufal | david-lyle: sure thing | 16:26 |
mrunge | absubram___, https://review.openstack.org/#/c/48255/7 is waiting on your input.... | 16:26 |
absubram___ | yes.. Working on responsding | 16:27 |
david-lyle | jcoufal: let's concentrate on getting it right in Juno, if there are some minor fixes to improve/aid usability let's consider them | 16:27 |
david-lyle | now | 16:27 |
david-lyle | any other items for RC1? | 16:28 |
david-lyle | #topic Design Summit Session Topics | 16:29 |
*** openstack changes topic to "Design Summit Session Topics (Meeting topic: Horizon)" | 16:29 | |
*** zigo has joined #openstack-meeting-3 | 16:29 | |
david-lyle | Summit topic suggestion is open for the Juno summit. http://summit.openstack.org | 16:29 |
jcoufal | how many slots do we have for horizon? | 16:30 |
david-lyle | anyone is free to propose session topics | 16:30 |
david-lyle | jcoufal: unclear, I would imagine the 6-8 | 16:30 |
david-lyle | I think maybe one less than last summit to allow for the cross-project sessions | 16:30 |
david-lyle | but the total has not been communicated yet | 16:30 |
jcoufal | alright it makes sense | 16:31 |
david-lyle | Cross-project topics are also acceptable for the first time in a while | 16:31 |
*** doug-fish has joined #openstack-meeting-3 | 16:31 | |
*** SumitNaiksatam has joined #openstack-meeting-3 | 16:31 | |
*** kudva has joined #openstack-meeting-3 | 16:31 | |
david-lyle | So please propose any topic ideas, I have a few, but would like to let others post theirs | 16:32 |
lblanchard | jcoufal: I entered a "Other Project" session for a UX designers/developers gathering | 16:32 |
lblanchard | jcoufal: happy to update this is you think it needs additions! | 16:32 |
jcoufal | lblanchard: seen that, I wanted to do the same, but I am happy it's covered | 16:33 |
lblanchard | jcoufal: cool | 16:33 |
jcoufal | will definitely post some ideas what we can cover | 16:33 |
lblanchard | jcoufal: perfect | 16:33 |
jcoufal | thanks for thinking of this ;) | 16:33 |
lblanchard | then one other session I proposed is around the usability test results that we've gotten from the testing over the last 2 weeks | 16:34 |
david-lyle | I think UX overflow may need to use the unconference schedule, but not a bad idea to get the topics proposed | 16:34 |
lblanchard | it 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 |
lblanchard | david-lyle: yeah, we can definitely use unconference for topics too | 16:34 |
jcoufal | david-lyle: I think at least one general topic is needed | 16:34 |
jcoufal | the one liz proposed | 16:34 |
david-lyle | jcoufal, I'm not disagreeing | 16:35 |
david-lyle | but UX has a lot to talk about :) will take more than 40 minutes | 16:35 |
lblanchard | david-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, etc | 16:35 |
david-lyle | great idea | 16:35 |
jcoufal | david-lyle: yeah, we do :) | 16:36 |
*** jcoufal-mobile has quit IRC | 16:36 | |
*** jcoufal-mobile has joined #openstack-meeting-3 | 16:36 | |
*** jcoufal-mobile has quit IRC | 16:37 | |
david-lyle | #topic Open Discussion | 16: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-detection | 16:37 |
absubram___ | at the summit | 16:37 |
david-lyle | absubram___, yes, we need to handle that for the keystone api in Juno as well as other services | 16:38 |
absubram___ | and I also had some questions about UT that I wanted to bring up | 16:38 |
david-lyle | general questions or specific? | 16:39 |
david-lyle | specific would be better to go through in the regular room | 16:39 |
david-lyle | Anyone have anything else? | 16:43 |
*** markmcclain has quit IRC | 16:43 | |
lblanchard | Quick 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%20Ideas | 16:44 |
lblanchard | this image is missing the actions column…sorry about that :) But the general idea is consolidation of the sparklines | 16:44 |
david-lyle | lblanchard: power state column is still present, and charted? | 16:47 |
lblanchard | david-lyle: great question…might not need to have a column | 16:47 |
lblanchard | david-lyle: I also asked about all of the possible states here…we might need more than just UP/DOWN | 16:48 |
mrunge | isn't sparklines a new feature and not a bug? | 16:48 |
david-lyle | mrunge, yes would merge in Juno | 16:48 |
lblanchard | mrunge: yes, sorry this is design work happening for a feature that will be pushed | 16:48 |
david-lyle | lblanchard, yes some states are more than binary | 16:50 |
david-lyle | I do like the idea | 16:50 |
lblanchard | david-lyle: right | 16:50 |
lblanchard | david-lyle: thanks…still a work in progress, just wanted to update everyone | 16:50 |
jpich | thanks lblanchard | 16:51 |
david-lyle | yes thank you | 16:51 |
david-lyle | Let's end a little early today. Thank you everyone. | 16:54 |
david-lyle | #endmeeting | 16:54 |
*** openstack changes topic to "Free for all (Meeting topic: Horizon)" | 16:54 | |
openstack | Meeting ended Tue Mar 11 16:54:09 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:54 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-03-11-16.01.html | 16:54 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-03-11-16.01.txt | 16:54 |
openstack | Log: http://eavesdrop.openstack.org/meetings/horizon/2014/horizon.2014-03-11-16.01.log.html | 16:54 |
jpich | Thanks | 16:54 |
david-lyle | Have a great week! | 16:54 |
*** doug-fish has left #openstack-meeting-3 | 16:55 | |
tmazur | Thank you! | 16:55 |
akrivoka | thanks everyone | 16:55 |
lblanchard | thanks all | 16:55 |
absubram___ | thank you | 16:55 |
jcoufal | thanks o/ | 16:57 |
*** absubram___ is now known as absubram__lunch | 16:58 | |
*** tzumainn has left #openstack-meeting-3 | 16:58 | |
*** MaxV has quit IRC | 16:59 | |
pballand | hi | 17:00 |
thinrichs | Hi all. We're getting the Congress meeting started. | 17:00 |
thinrichs | #startmeeting CongressTeamMeeting | 17:00 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:00 |
*** openstack changes topic to " (Meeting topic: CongressTeamMeeting)" | 17:00 | |
openstack | The meeting name has been set to 'congressteammeeting' | 17:00 |
*** akrivoka has left #openstack-meeting-3 | 17:01 | |
thinrichs | Agenda for the day: | 17:01 |
*** david-lyle has quit IRC | 17:01 | |
*** sarob_ has joined #openstack-meeting-3 | 17:01 | |
thinrichs | 1) progress toward an alpha release | 17:01 |
thinrichs | 2) pointer to other policy projects. | 17:01 |
thinrichs | Let's start with 2 since it's quick. | 17:02 |
*** tmazur has quit IRC | 17:02 | |
* sarob_ lurking | 17:02 | |
thinrichs | Last week gokul and others on the ML were asking about all the policy projects in OS. | 17:02 |
thinrichs | They 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 |
pballand | sarob_: you're in good company :) | 17:03 |
sarob_ | ;) | 17:03 |
*** jpich has left #openstack-meeting-3 | 17:03 | |
thinrichs | Here'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 |
thinrichs | https://wiki.openstack.org/wiki/Congress | 17:03 |
pballand | the links are helpful, thank you | 17:03 |
thinrichs | Info is at the end of the page. | 17:04 |
*** jcoufal has quit IRC | 17:04 | |
*** terrylhowe has joined #openstack-meeting-3 | 17:04 | |
*** lcheng has quit IRC | 17:04 | |
thinrichs | Any comments/questions on that? | 17:04 |
pballand | it seems like these projects may play well, in the future | 17:05 |
pballand | current strategy appears complimentary (which is great) | 17:06 |
thinrichs | Yeah--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-3 | 17:06 | |
thinrichs | Moving to next agenda item now. | 17:07 |
thinrichs | #topic Progress toward alpha release | 17:07 |
rajdeep | hi | 17:07 |
*** openstack changes topic to "Progress toward alpha release (Meeting topic: CongressTeamMeeting)" | 17:07 | |
thinrichs | rajdeep: hi! | 17:07 |
pballand | hi rajdeep - just in time :) | 17:07 |
rajdeep | yes, | 17:07 |
thinrichs | We had just quickly gone over the list of other policy efforts within OS that we've listed on the Congress wiki page. | 17:07 |
thinrichs | We'll be trying to keep that up to date. | 17:08 |
rajdeep | ok | 17:08 |
thinrichs | Now we've moved on to the main part of the agenda: progress toward an alpha release. | 17:08 |
thinrichs | We'll just go down a list of todos and discuss progress. | 17:08 |
rajdeep | great - what are the time lines | 17:08 |
thinrichs | Not 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 |
thinrichs | Let's revisit once we talk through the todos. | 17:09 |
thinrichs | First item is Data Integration, which you are working on rajdeep. | 17:10 |
rajdeep | where is the agenda posted? | 17:10 |
rajdeep | currently i am working on finishing the neutron integration | 17:10 |
rajdeep | should we have some kind of data model for each type of service we are integrating | 17:10 |
pballand | I failed to post it - Tim has a list of todos to talk about | 17:11 |
rajdeep | and populate those structures from the native objects | 17:11 |
rajdeep | i saw your comments on neutron | 17:11 |
pballand | the data model is just tuples | 17:11 |
pballand | tuples are lowest-common format for all data sources | 17:11 |
pballand | that allows the policy language to be common across all sources | 17:12 |
rajdeep | ok, so i need to convert networks, ports, subnets etc into tuples | 17:12 |
pballand | with that said, we should have a well defined (and commented) set of tuples for each data source | 17:12 |
thinrichs | rajdeep: yes | 17:12 |
gokul_ | hi all: this is gokul | 17:12 |
thinrichs | I put an example in the comments. Did that make sense? | 17:12 |
thinrichs | gokul: hi! | 17:13 |
*** kudva_ has joined #openstack-meeting-3 | 17:13 | |
rajdeep | so i just convert dictionary into tuple and return | 17:13 |
rajdeep | yes go it | 17:13 |
*** d0ugal has quit IRC | 17:13 | |
gokul_ | just beginning with congress... hope to contribute :) | 17:13 |
pballand | gokul_: great - there is a lot to do :) | 17:13 |
thinrichs | rajdeep: not just a Python dict to Python tuple. The tuples must only have strings/numbers as elements. No embedded data structures. | 17:13 |
rajdeep | ok, got it | 17:14 |
kudva_ | Hi, I am prabhakar, work with Gokul, joining as well | 17:14 |
thinrichs | kudva: welcome! | 17:14 |
pballand | kudva_: welcome | 17:14 |
rajdeep | so my plan is to cover neutron, nova, keystone and cinder | 17:14 |
thinrichs | We're in the midst of going thru the list of todos to get an alpha release ready. | 17:15 |
thinrichs | kudva, 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-3 | 17:15 | |
rajdeep | any 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 list | 17:16 |
thinrichs | rajdeep: I'd say that neutron and nova are musts and keystone and cinder are nice-to-haves | 17:16 |
rajdeep | good, | 17:16 |
rajdeep | should not be difficult | 17:16 |
rajdeep | i found some problems getting groups out of keystone | 17:17 |
rajdeep | apparently not many people use it as of now | 17:17 |
*** sarob_ has quit IRC | 17:17 | |
rajdeep | and all our examples tie users to groups | 17:17 |
rajdeep | which is more of AD/LDAP use case | 17:17 |
thinrichs | rajdeep: 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-3 | 17:18 | |
rajdeep | ok-- so how do we plan the integration one data is in place | 17:18 |
thinrichs | rajdeep: I'd be happy to use AD/LDAP for groups -- to illustrate that Congress works with non-OS components. | 17:18 |
pballand | rajdeep: can you elaborate? | 17:18 |
rajdeep | do we need another component which ties the parser/runtime with the data_driver | 17:19 |
rajdeep | or will this be an example script outside the core code | 17:20 |
thinrichs | rajdeep: 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 |
thinrichs | rajdeep: I think we want it integrated. | 17:20 |
rajdeep | exactly | 17:20 |
*** lpetrut has quit IRC | 17:20 | |
thinrichs | Congress will need to be responsible for integrating the data necessary to make policy decisions. | 17:21 |
rajdeep | and we would need a place to do integration testing -- openstack + AD + congress | 17:21 |
*** SumitNaiksatam has quit IRC | 17:21 | |
thinrichs | rajdeep: that's another important issue and it's on the list of alpha todos | 17:21 |
rajdeep | ok | 17:22 |
*** jthopkin has left #openstack-meeting-3 | 17:22 | |
rajdeep | let us move to the next item on the agenda | 17:22 |
thinrichs | Can someone look into the data integration "glue"? | 17:22 |
pballand | I would be happy to take that | 17:22 |
thinrichs | Great. | 17:22 |
thinrichs | #action pballand will look into the data integration framework. | 17:23 |
thinrichs | The next todo is the API infrastructure that connects the policy engine to the outside world. | 17:23 |
thinrichs | pballand: you worked on this--could you give us a status update? | 17:24 |
pballand | yeah, the code that is posted was pretty rushed | 17:24 |
pballand | basic idea was to use a simple API co-routine loop like other projects | 17:24 |
pballand | I'm not worried about a fancy framework right now, but getting the API abstractions right is important | 17:24 |
*** nacim has quit IRC | 17:25 | |
thinrichs | pballand: agreed | 17:25 |
*** SumitNaiksatam has joined #openstack-meeting-3 | 17:25 | |
pballand | still need to expose _basically everything_ | 17:25 |
thinrichs | Could you estimate amount of time/work to hook everything up? | 17:25 |
pballand | I imagine a pretty good interface could be constructed with a few solid weeks of work | 17:26 |
*** lcheng has quit IRC | 17:26 | |
thinrichs | pballand: do you have cycles to devote to that? | 17:26 |
pballand | I can definitely take a second pass at making the code more product-ready | 17:26 |
rajdeep | we would also need to tie the REST endpoints to the runtime engine | 17:27 |
rajdeep | or we want to keep them separate | 17:27 |
rajdeep | ? | 17:27 |
pballand | I think its best to keep a loose coupling between to two | 17:27 |
pballand | ... but in the same binary | 17:27 |
pballand | do you have thoughts? | 17:28 |
rajdeep | well it was hard for me to understand it initially | 17:28 |
*** lcheng has joined #openstack-meeting-3 | 17:28 | |
rajdeep | how the two are linked -- currently only through tables | 17:28 |
rajdeep | perhaps we could put it in a readme | 17:29 |
pballand | (in my experience, APIs that evolve along with the underlying implementation become cumbersome over time) | 17:29 |
pballand | I'll try to make it clear as I develop the next iteration | 17:29 |
*** mrunge has quit IRC | 17:29 | |
rajdeep | ok, great | 17:29 |
rajdeep | any plans to add persistence layer to tables | 17:29 |
rajdeep | ? | 17:29 |
thinrichs | rajdeep: 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 |
thinrichs | persistence for tables is not. | 17:30 |
thinrichs | because once we turn off Congress, it'll need to resync with all the data sources anyway. | 17:31 |
rajdeep | ok..i meant policies | 17:31 |
pballand | rajdeep: congress is the source of truth for the policy, but is just a cache of other data (in the tables) | 17:31 |
thinrichs | pballand: agreed | 17:31 |
thinrichs | rajdeep: yes--we should do that. | 17:31 |
thinrichs | I was thinking that we'd do it via logging at first. | 17:32 |
thinrichs | So 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 |
thinrichs | We'll need logging of some form for debugging/auditing anyway;. | 17:32 |
thinrichs | Anyone want to look into this? | 17:32 |
rajdeep | i can take it up after my data integration is over | 17:33 |
thinrichs | I don't think this is a show-stopper for an alpha release. | 17:33 |
thinrichs | rajdeep: great. | 17:33 |
rajdeep | we will use regular python logging? | 17:33 |
thinrichs | #action rajdeep will look into persisting policy after his data integration work. | 17:33 |
thinrichs | rajdeep: haven't thought that far ahead. | 17:33 |
thinrichs | Unless there are objection, we'll move onto a couple of quick alpha todos. | 17:34 |
rajdeep | sure go ahead | 17:34 |
pballand | please fire away :) | 17:34 |
thinrichs | There were some basic issues with the policy engine not doing really ANY syntax checking. | 17:35 |
thinrichs | I pushed those last week sometime. So that todo is finished well enough for now. | 17:35 |
thinrichs | Another small todo was to startup some user docs so that people have a guide when using Congress for the first time. | 17:35 |
thinrichs | I just pushed for review the first cut at that. | 17:35 |
thinrichs | https://review.openstack.org/#/c/79383/ | 17:36 |
*** sarob_ has quit IRC | 17:36 | |
*** sarob_ has joined #openstack-meeting-3 | 17:36 | |
thinrichs | I'll give you a minute to peruse. Let me know when you're ready to move on. | 17:36 |
pballand | I'll try to review by tomorrow | 17:37 |
thinrichs | It's probably hard to look at in raw RST, but it gets compiled into HTML, PDF, etc. | 17:37 |
thinrichs | It's the standard thing to use in OS (I believe). | 17:37 |
rajdeep | wow thats lot of docs | 17:37 |
thinrichs | Lots of files, perhaps, but only a few pages of content. | 17:37 |
rajdeep | perhaps we could look at docbook format as well | 17:37 |
thinrichs | rajdeep: I have no idea what the list of supported formats are. | 17:38 |
sarob_ | docs stores docbook in xml | 17:38 |
pballand | from 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 RST | 17:38 |
*** markmcclain has joined #openstack-meeting-3 | 17:38 | |
sarob_ | pballand: you got it | 17:38 |
thinrichs | sarob: that's what we're using. Phew! | 17:39 |
rajdeep | so we are building developer docs "only"? | 17:39 |
pballand | :) | 17:39 |
pballand | it's a great place to start :) | 17:39 |
rajdeep | yes let us focus on getting alpha out | 17:39 |
sarob_ | ive been dabbling with setting standards for RST | 17:39 |
pballand | I 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 build | 17:39 |
sarob_ | pballand: right | 17:40 |
sarob_ | pballand: status quo, better than new ground on docs | 17:40 |
sarob_ | pballand: code perhaps first | 17:40 |
pballand | as we get closer to alpha, we can leverage the RST to create more formal user docs | 17:40 |
pballand | sarob_: agreed | 17:40 |
sarob_ | pballand: as long as you are consistent in formal, no problems | 17:40 |
sarob_ | pballand: arrg, format | 17:41 |
thinrichs | Moving on: we wanted to do some basic scaling tests. | 17:42 |
thinrichs | That was on my plate and I haven't gotten around to it. | 17:42 |
pballand | I was hoping to get an example dataset from a user with a big deployment, but they ran in to so hurdles | 17:42 |
pballand | hopefully more to come on this... | 17:42 |
pballand | s/so/some/ | 17:43 |
thinrichs | Last item on my list for the alpha release. (Probably others I'm missing.) | 17:43 |
rajdeep | thinrichs : what would be typical number of policy insertions in a real life use case? | 17:43 |
pballand | rajdeep: it seems to very *greatly* based on the deployment | 17:44 |
*** absubram__lunch has quit IRC | 17:44 | |
pballand | insertions are relatively infrequent | 17:44 |
rajdeep | ok and total policy elements | 17:45 |
pballand | data changes (group membership, for instance) are common, however, so incremental computation is imporatnt | 17:45 |
pballand | rajdeep: it's hard to say | 17:45 |
rajdeep | another question is how will congress scale | 17:45 |
rajdeep | will it be a multi node deployment? | 17:45 |
pballand | scale is important, but we need the operational model first | 17:47 |
thinrichs | With that, we need to move on to the last todo. | 17:47 |
pballand | I'd rather not scale a shitty model :) | 17:47 |
thinrichs | Before running out of time. | 17:47 |
thinrichs | The last issue is one of what *kinds* of policies we are having the user write. | 17:47 |
thinrichs | There are (at least) 3. | 17:47 |
thinrichs | 1. Classification + Action (what we're currently promoting). The idea is to describe which *states* of the cloud are permitted by policy. | 17:48 |
thinrichs | 2. Access-Control (e.g. XACML, AD). The idea is to describe what *actions* are *permitted* for whom. | 17:48 |
thinrichs | 3. Condition action: The idea is to describe what *actions* Congress should *execute* under what conditions. | 17:49 |
thinrichs | Do 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 IRC | 17:50 | |
*** johnthetubaguy1 has quit IRC | 17:50 | |
thinrichs | kudva: 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 |
thinrichs | So, generic, I think. | 17:50 |
thinrichs | The 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 |
thinrichs | And 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 |
pballand | I think it's important that congress doesn't interpret things like failure - it simply computes the policy provided | 17:52 |
rajdeep | how are these related to each other | 17:52 |
*** johnthetubaguy has joined #openstack-meeting-3 | 17:52 | |
rajdeep | 1 will lead to 3 | 17:52 |
rajdeep | 2 will feed into 1? | 17:52 |
thinrichs | rajdeep: From 1 we can compute a bunch of possible 3s. | 17:53 |
*** eghobo has quit IRC | 17:53 | |
thinrichs | E.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 |
thinrichs | We 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 |
thinrichs | Each of those choices could lead to a different policy 3. | 17:54 |
pballand | kudva: not python function; rather policy-directed combination of primitives from openstack components | 17:54 |
*** eghobo has joined #openstack-meeting-3 | 17:55 | |
thinrichs | Policy 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 |
thinrichs | where by 'violations' I mean 'violations' according to policy type 1. | 17:55 |
*** Alex_Gaynor has joined #openstack-meeting-3 | 17: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 |
thinrichs | So types 2 and 1 are different as well. | 17:56 |
pballand | kudva: 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 |
thinrichs | I just noticed we're running short on time. | 17:56 |
*** david-lyle has joined #openstack-meeting-3 | 17:56 | |
thinrichs | gokul: 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-3 | 17:57 | |
thinrichs | I'm not sure at this point whether we could express a policy requiring optimization for enforcement within Congress. | 17:57 |
thinrichs | If 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 |
thinrichs | Hand-waving furiously. | 17:58 |
thinrichs | Let's wrap up since we're out of time. | 17:58 |
thinrichs | This 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 functions | 17:59 |
*** jpomero has quit IRC | 17:59 | |
pballand | thanks everyone | 17:59 |
gokul_ | great. thanks! | 17:59 |
kudva_ | thanks | 17:59 |
rajdeep | thanks! | 17:59 |
thinrichs | Thanks all! | 17:59 |
thinrichs | #endmeeting | 17:59 |
*** openstack changes topic to "Free for all (Meeting topic: Horizon)" | 17:59 | |
openstack | Meeting ended Tue Mar 11 17:59:39 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:59 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-03-11-17.00.html | 17:59 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-03-11-17.00.txt | 17:59 |
openstack | Log: http://eavesdrop.openstack.org/meetings/congressteammeeting/2014/congressteammeeting.2014-03-11-17.00.log.html | 17:59 |
*** gokul_ has quit IRC | 17:59 | |
*** kudva_ has quit IRC | 17:59 | |
*** jnoller has joined #openstack-meeting-3 | 18:00 | |
*** mrunge has joined #openstack-meeting-3 | 18:00 | |
*** pballand has quit IRC | 18:01 | |
Alex_Gaynor | jnoller: time to kick this party off? | 18:02 |
*** jpomero has joined #openstack-meeting-3 | 18:02 | |
jnoller | python-openstacksdk meeting starting; need to find the meeting bot commands | 18:02 |
*** thinrichs has quit IRC | 18:02 | |
jnoller | #startmeeting Python-OpenstackSDK weekly meeting | 18:03 |
openstack | Meeting 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 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 18:03 |
*** openstack changes topic to " (Meeting topic: Python-OpenstackSDK weekly meeting)" | 18:03 | |
openstack | The 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_UTC | 18:03 |
jnoller | #link https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK#Agenda_for_2014-03-11_1900_UTC | 18:03 |
jnoller | First item: if you are here #link https://wiki.openstack.org/wiki/SDK-Development/PythonOpenStackSDK | 18:04 |
jnoller | *sigh* | 18:04 |
jnoller | #link https://wiki.openstack.org/wiki/SDK-Development/PythonOpenStackSDK | 18:04 |
*** pballand has joined #openstack-meeting-3 | 18:04 | |
*** johnthetubaguy has quit IRC | 18:04 | |
jnoller | First item: Roll call if you are here for the python sdk meeting! | 18:04 |
edleafe | o/ | 18:04 |
*** kudva has quit IRC | 18:04 | |
jnoller | Jesse Noller, Rackspace | 18:04 |
*** johnthetubaguy has joined #openstack-meeting-3 | 18:04 | |
edleafe | Ed Leafe, Rackspce | 18:04 |
wchrisj | Chris Johnson, HP | 18:05 |
Alex_Gaynor | Alex Gaynor | 18:05 |
dolphm | this meeting is an hour early in UTC | 18:05 |
jnoller | it should be 1pm CST | 18:05 |
edleafe | It's 1pm CDT now | 18:05 |
jnoller | I think daylight savings time just bit me ;) | 18:05 |
jnoller | dolphm is right, technically it's now 2pm CDT | 18:06 |
*** mfer has joined #openstack-meeting-3 | 18:06 | |
wchrisj | It's 2pm EDT | 18:06 |
jnoller | Anyone mind us waiting the hour thanks to Daylight savings? | 18:07 |
glyph | Glyph, Rackspace | 18:07 |
Alex_Gaynor | If we wait an hour, I'll be at lunch | 18:07 |
edleafe | yeah, let's start at the correct UTC time | 18:07 |
mfer | so, it'll start in an hour? | 18:07 |
* mfer thinks this is confusing | 18:08 | |
jnoller | Yeah, daylight savings time messed it all up | 18:08 |
jnoller | mfer: 1900 UTC | 18:08 |
jnoller | #endmeeting | 18:08 |
*** openstack changes topic to "Free for all (Meeting topic: Horizon)" | 18:08 | |
openstack | Meeting ended Tue Mar 11 18:08:49 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:08 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/python_openstacksdk_weekly_meeting/2014/python_openstacksdk_weekly_meeting.2014-03-11-18.03.html | 18:08 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk_weekly_meeting/2014/python_openstacksdk_weekly_meeting.2014-03-11-18.03.txt | 18:08 |
openstack | Log: http://eavesdrop.openstack.org/meetings/python_openstacksdk_weekly_meeting/2014/python_openstacksdk_weekly_meeting.2014-03-11-18.03.log.html | 18:08 |
jnoller | let's move back to -sdks | 18:09 |
*** jamielennox has joined #openstack-meeting-3 | 18:09 | |
*** glyph has left #openstack-meeting-3 | 18:15 | |
*** SumitNaiksatam_ has joined #openstack-meeting-3 | 18:27 | |
*** SumitNaiksatam has quit IRC | 18:27 | |
*** lpetrut has joined #openstack-meeting-3 | 18:29 | |
*** SumitNaiksatam_ is now known as SumitNaiksatam | 18:29 | |
*** mrunge has quit IRC | 18:32 | |
*** pballand has quit IRC | 18:33 | |
*** pballand has joined #openstack-meeting-3 | 18:38 | |
*** pballand has quit IRC | 18:38 | |
*** rajdeep has quit IRC | 18:38 | |
*** johnthetubaguy has quit IRC | 18:39 | |
*** devlaps1 has joined #openstack-meeting-3 | 18:48 | |
*** devlaps has quit IRC | 18:48 | |
*** SumitNaiksatam has quit IRC | 18:52 | |
*** bknudson has joined #openstack-meeting-3 | 18:55 | |
*** briancurtin has joined #openstack-meeting-3 | 18:59 | |
*** lblanchard has quit IRC | 19:00 | |
briancurtin | #startmeeting python-openstacksdk | 19:00 |
openstack | Meeting 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-3 | 19:00 | |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 19:00 |
*** openstack changes topic to " (Meeting topic: python-openstacksdk)" | 19:00 | |
openstack | The meeting name has been set to 'python_openstacksdk' | 19:00 |
briancurtin | #link https://wiki.openstack.org/wiki/Meetings/PythonOpenStackSDK <- Agenda | 19:00 |
briancurtin | #link https://wiki.openstack.org/wiki/SDK-Development/PythonOpenStackSDK <- General Project Info | 19:01 |
briancurtin | Could everyone here for the python-openstacksdk meeting state their name and affiliation? | 19:01 |
edleafe | Ed Leafe, Rackspace | 19:01 |
dtroyer | Dean Troyer, Nebula | 19:01 |
briancurtin | Brian Curtin, Rackspace | 19:01 |
jamielennox | Jamie Lennox, Red Hat | 19:02 |
wchrisj | Chris Johnson, HP | 19:02 |
jnoller | Jesse Noller, Rackspace | 19:02 |
dolphm | dolph mathews, rackspace | 19:02 |
*** jpomero has quit IRC | 19:02 | |
briancurtin | Alex_Gaynor: ping | 19:02 |
bknudson | Brant Knudson, IBM | 19:03 |
briancurtin | So 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, etc | 19: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 | |
briancurtin | hopefully Alex_Gaynor comes in here, he was around earlier | 19:04 |
wchrisj | did he have lunch plans at this time? | 19:05 |
wchrisj | someone did... | 19:05 |
jnoller | he did | 19:05 |
wchrisj | It was him | 19:05 |
wchrisj | ugh | 19:05 |
briancurtin | oh, well moving on | 19:05 |
jnoller | anyway; the primary contention here seems to httppretty | 19:05 |
jnoller | which; has that been ported to python 3 yet? | 19:05 |
*** cjellick_ has quit IRC | 19:06 | |
jnoller | and the dependency on URLObject | 19:06 |
jamielennox | yes it has been ported to python 3 | 19:06 |
jnoller | I do agree with alex re: the global monkey patching / magic stuff behind it | 19:07 |
jnoller | I'm not a huge fan of those kinds of mocks/stubs | 19:07 |
bknudson | we're using it in keystoneclient which passes python33 | 19:07 |
jnoller | bknudson: thanks, all I could recall were -dev discussions from a month or 3 ago | 19:08 |
jamielennox | jnoller: the advantage i've seen is that you are actually testing the code all the way through | 19:08 |
dolphm | what does URLObject buy you here? | 19:08 |
jamielennox | you actually test the request layer | 19:08 |
jamielennox | i completely agree with the global stuff in projects, but i think its fine for testing | 19:09 |
briancurtin | if it does the trick and is working well elsewhere, i tend to agree | 19:09 |
jnoller | jamielennox: part of this is that users want a lib (included with the sdk) of verified mocks/stubs/fakes that don't manipulate or monkeypatch | 19:09 |
jnoller | so they can use those for testing as well | 19:10 |
jamielennox | jnoller: ok - that's new | 19:10 |
*** cjellick has joined #openstack-meeting-3 | 19:10 | |
jnoller | jamielennox: it's on the wiki | 19:10 |
bknudson | for keystone, a verified mock would be essentially running it with kvs backends | 19:10 |
jnoller | jamielennox: might need to call it out more | 19:10 |
dolphm | authorization scope is also completely ignored in that patch -- which is fine at rackspace, but doesn't fly in openstack | 19:10 |
bknudson | or sqlite. | 19:10 |
edleafe | jamielennox: It's important for an SDK, since it will be used as part of other projects | 19:10 |
*** cjellick has quit IRC | 19:10 | |
briancurtin | are 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 |
jamielennox | briancurtin: i don't think you can, it's patching at the socket level so it installs it globally | 19:11 |
jnoller | briancurtin: for http/requests you can use regular mocks or even betamax (which is an add on) | 19:11 |
*** cjellick has joined #openstack-meeting-3 | 19:11 | |
jamielennox | mocking the requests interface is a PITA, you end up carrying these dictionaries of default arguments around | 19:11 |
jnoller | I'm generally -1 on anything that patches sockets :( - but I'm also happy to reach out to Ian / Kenneth about better mocking for requests | 19:12 |
wchrisj | if betamax is anything like it's cousin vcr (ruby), that would be worth considering imo | 19:12 |
jnoller | But I'm also just one voice :) | 19:12 |
briancurtin | also happy with that as well | 19:13 |
jnoller | wchrisj: it was based on VCR | 19:13 |
wchrisj | that was my thought | 19:13 |
jamielennox | if requests will provide support then that would be good | 19:13 |
wchrisj | jnoller: ^^ | 19:13 |
jamielennox | doesn't VCR mock the socket as well? | 19:13 |
jnoller | betamax: https://pypi.python.org/pypi/betamax/0.1.6 | 19:13 |
briancurtin | jnoller: 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 |
jnoller | briancurtin: I want to confirm with Alex_Gaynor | 19:13 |
briancurtin | so i guess we have a couple of action points to work out | 19:14 |
jnoller | briancurtin: 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 proposing | 19:14 |
briancurtin | agreed/makes sense | 19:15 |
jnoller | briancurtin: Ideally our test mocks / stubs can be used by end users building applications | 19: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 | |
briancurtin | ah crap, sorry, meant action | 19:15 |
briancurtin | #action look into better mocking with requests (check with Kenneth et. al) | 19:15 |
jnoller | The other point on that change is the dependency on https://urlobject.readthedocs.org/en/latest/quickstart.html | 19:16 |
jamielennox | jnoller: 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 call | 19:16 |
jamielennox | if you use httplib or requests or whatever you will get the same response | 19:16 |
briancurtin | #action confirm state of HTTPretty usability with regard to verifying mocks/stubs | 19:16 |
briancurtin | #topic using URLObject | 19: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 |
bknudson | does mocks/stubs here mean a fake keystone server? | 19:17 |
jnoller | jamielennox: global patching socket objects side-effects end users in surprising/unexpected ways though - I see both sides honestly | 19:17 |
jnoller | bknudson: in memory fake; not a running /forked daemon | 19:17 |
jamielennox | jnoller: it's testing code, users shouldn't care | 19:17 |
jnoller | ? | 19:17 |
bknudson | seems like it would be easier to make it so that keystone can run in-memory rather than develop a fake keystone. | 19:18 |
jamielennox | depends 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 state | 19:18 |
jnoller | What we use for testing should be what we recommend users use for testing - eating our own dogfood | 19:19 |
jnoller | bknudson: that means an in memory version of a LOT of things (you're going to need a full in memory openstack system) | 19:20 |
jamielennox | there's recommend and then there's here use all this stuff we've developed to help you | 19:20 |
jnoller | If we ship fakes/mocks/stubs we should be using the same ones - so the latter | 19:20 |
bknudson | jnoller: yes, keystone is probably simpler than some of the other things that will need to be faked | 19:20 |
jnoller | Personally: 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/stubs | 19:21 |
briancurtin | but 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 caring | 19:22 |
*** briancurtin has left #openstack-meeting-3 | 19:22 | |
jnoller | But, we need to clarify this for sure | 19:22 |
*** briancurtin has joined #openstack-meeting-3 | 19:22 | |
jamielennox | jnoller: 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 objects | 19:23 |
jnoller | briancurtin: 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 |
jnoller | jamielennox: Yeah, we should definitely dig into it | 19:23 |
briancurtin | yes | 19:23 |
jnoller | Next on Alex's patch is urlobject | 19:23 |
*** sarob_ has quit IRC | 19:24 | |
*** sarob_ has joined #openstack-meeting-3 | 19:25 | |
jnoller | Looking at it; he doesn't make extensive use of it, but reading the docs I can see why he's using it | 19:25 |
briancurtin | what does urlobject buy us? | 19:25 |
briancurtin | (havent read those docs yet) | 19:25 |
jnoller | it *seems* like a much better way of managing urls -> https://urlobject.readthedocs.org/en/latest/quickstart.html | 19:25 |
jnoller | For example | 19:25 |
jnoller | >>> print(url.with_auth('alice', '1234')) | 19:25 |
jnoller | https://alice:1234@github.com/zacharyvoase/urlobject?spam=eggs#foo | 19:25 |
bknudson | urlobjects looks safer than dealing with urls as strings. | 19:26 |
jnoller | You get out of the URL parsing / building / string concatenation game | 19:26 |
wchrisj | +1 | 19:26 |
jnoller | bknudson: exactly (I've been bitten a LOT by treating them like strings) | 19:26 |
jnoller | url = blah + var + '/whee:' : port :( | 19:27 |
briancurtin | seems 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 valuable | 19:27 |
dolphm | urlobject has no other deps | 19:27 |
jamielennox | sure, 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 loss | 19:28 |
edleafe | Just quoting from the original design criteria for the SDK | 19:28 |
jnoller | I want to minimize dependencies, but I also don't want to fail boat on url management | 19:28 |
jnoller | this basically means: requests + urlobject | 19:28 |
jnoller | which doesn't seem *terrible* as it still avoids the N+K dependencies creep | 19:29 |
dtroyer | no but it's a bit ironic that the first code patch adda a new dependency... | 19:29 |
dolphm | it's not in global requirements though, which just means no one else is using it yet | 19:29 |
*** sarob_ has quit IRC | 19:29 | |
briancurtin | (sorry, bad conference wifi) | 19:29 |
jnoller | dtroyer: yeah :( | 19:30 |
dolphm | jnoller: 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 |
briancurtin | agree | 19:31 |
wchrisj | agree | 19:31 |
jamielennox | ++ | 19:31 |
jnoller | dolphm: Ok, Alex_Gaynor needs to document (in a blueprint) why using this (and adding it to global-requirements) is a positive | 19:31 |
briancurtin | #action Alex_Gaynor outline a justification of why to use URLObject and add it as a dependency | 19:31 |
jnoller | Its not like installing its own wsgi server ;) | 19:32 |
dolphm | jnoller: not that there's anything wrong with that, right? | 19:32 |
jnoller | haha | 19:32 |
dtroyer | but it's also not packaged in Ubuntu yet…so yet one more step to completion | 19:33 |
jnoller | dolphm brought up some good rackspace-isms in Alex_Gaynor's patch that have to be excised | 19:33 |
jnoller | dtroyer: good catch | 19:33 |
*** markmcclain has quit IRC | 19:34 | |
briancurtin | yeah that'll be a good thing to cover in the BP | 19:34 |
*** markmcclain has joined #openstack-meeting-3 | 19:34 | |
jnoller | So, Alex has some refinement to do | 19:35 |
dolphm | blueprints effectively get lost after they're implemented though... they "why" might be better preserved in a commit message | 19:35 |
dolphm | the* | 19:35 |
jnoller | dolphm: commit message and the wiki | 19:35 |
briancurtin | dolphm: is this better to be laid out in a wiki, and then condensed into a commit | 19:36 |
briancurtin | mind reader | 19:36 |
briancurtin | so, ok, have some research to do on HTTPretty, requests mocking, URLObject. what else do we have with the example so far? | 19:37 |
jnoller | briancurtin: remove the rackspace-isms | 19:37 |
jnoller | dolphm did a great job pointing those out | 19:38 |
briancurtin | #action Alex_Gaynor remove Rackspace-isms in example code, as pointed out by dolphm | 19:38 |
bknudson | what'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-3 | 19:40 | |
*** sarob_ has quit IRC | 19:41 | |
jnoller | @bknudson: good question for Alex_Gaynor | 19:41 |
jnoller | briancurtin: 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 week | 19:42 |
briancurtin | i 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 |
dolphm | dtroyer: 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 |
dolphm | which is definitely better than zero and a broken jenkins | 19:43 |
Alex_Gaynor | (I'm present now) | 19:43 |
jnoller | pfft food | 19:44 |
dtroyer | it was part of trying to figure out what it took to get any of those changes through... | 19:44 |
dtroyer | int he end we needed to just disable the test due to the way it was written | 19:44 |
dtroyer | can be cleaned up now | 19:44 |
dolphm | dtroyer: ack | 19:44 |
briancurtin | #topic Design Summit topic(s) | 19:44 |
*** openstack changes topic to "Design Summit topic(s) (Meeting topic: python-openstacksdk)" | 19:44 | |
briancurtin | with 15 minutes left, anything input as to what, if anything, should be submitted for the design summit? | 19:45 |
jnoller | briancurtin: I submitted a design summit session today on this and developer experience/cloud consumer stuff | 19:45 |
briancurtin | i'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 |
briancurtin | jnoller: can you link to it? | 19:46 |
wchrisj | New for me too | 19:46 |
jnoller | y | 19:46 |
jnoller | one second | 19:46 |
dolphm | jnoller: i don't see one... | 19:46 |
dolphm | ah http://summit.openstack.org/cfp/details/34 | 19:46 |
jnoller | http://summit.openstack.org/cfp/details/34 | 19:46 |
briancurtin | not 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 |
jnoller | briancurtin: I'm open to suggestions on that too | 19:48 |
jnoller | briancurtin: too narrow worries me, I'd like to avoid a monoculture when looking at the personas/users | 19:49 |
briancurtin | i 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 folks | 19:49 |
edleafe | briancurtin: The design summit sessions are where everyone concerned makes decisions on how to proceed over the next 6 months. The sessions should be very specific | 19:49 |
briancurtin | yep | 19:49 |
dolphm | related: User Experience Designers Gathering http://summit.openstack.org/cfp/details/33 | 19:49 |
jnoller | dolphm: yes, that one is very focused on horizon | 19:49 |
briancurtin | edleafe: so should there be a python session, php session, ruby sess, etc? | 19:49 |
edleafe | ideally, yes | 19:49 |
Alex_Gaynor | dolphm: Will get a patch up to address your concerns after the meeting. | 19:49 |
edleafe | A lot of what we will discuss has nothing to do with ruby or php | 19:50 |
dolphm | jnoller: ++ it's on the "Other projects" track though - any idea why? (or what that track is for?) | 19:50 |
briancurtin | do 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 |
jnoller | dolphm: No idea, I saw it this morning | 19:50 |
jnoller | briancurtin: good idea | 19:50 |
jnoller | better than mine! | 19:50 |
wchrisj | briancurtin: +1 | 19:50 |
dtroyer | briancurtin: ideally, yes | 19:50 |
edleafe | briancurtin: it depends on what aspects of the design you need to work on | 19:50 |
dtroyer | given a choice and the stage we're in, python-specific if we can only do one | 19:51 |
jnoller | I will say mfer and others here have been making progress on the other SDKs too (php, go, etc) | 19:52 |
edleafe | dtroyer: yeah, given that we don't have anything to go on, generic is probably all we can do | 19:52 |
jnoller | the goals are pretty aligned | 19:52 |
edleafe | jnoller: aren't they working from an established code base? | 19:53 |
jnoller | edleafe: they're all shifting into 2.0 clean room modes | 19:53 |
dolphm | jnoller: where are the non-python sdk's on github? | 19:53 |
jnoller | edleafe: much like this one | 19:53 |
jnoller | dolphm: hold on, need to find all the links | 19:54 |
dolphm | jnoller: and is there any desire to get them into stackforge? (has that been discussed?) | 19:54 |
mfer | is this something we should continue in the #openstack-sdks room? | 19:54 |
dtroyer | Go: http://git.openstack.org/cgit/stackforge/golang-client/ | 19:54 |
jnoller | mfer: true | 19:54 |
mfer | dolphm a number of them are going into stackforge already | 19:54 |
jnoller | sorry, lack of focus | 19:54 |
jnoller | edleafe: think you can work with alex to flesh out more of the identity stuff? | 19:55 |
edleafe | I' | 19:56 |
edleafe | oops | 19:56 |
edleafe | I'd have to discuss with him what his goal is with the code - not entirely clear to me yet | 19:56 |
briancurtin | if people aren't hounding us at this conference, i'm around to help out with it | 19:58 |
jamielennox | let me know any issues you have with identity, though i realize i'm not in most peoples TZ | 19:58 |
jnoller | ok, let's see if we can do that and keep more going into the repo for discussion | 19:58 |
briancurtin | feed the machine with code | 19:58 |
*** d0ugal has joined #openstack-meeting-3 | 19:58 | |
*** d0ugal has quit IRC | 19:58 | |
*** d0ugal has joined #openstack-meeting-3 | 19:58 | |
jnoller | jamielennox: I don't even know what TZ I'm in right now so it's cool | 19:58 |
briancurtin | what even is time | 19:58 |
briancurtin | so i think that's probably it, anything as the clock winds down? | 19:59 |
jnoller | Nope! | 19:59 |
wchrisj | I'll get with Alex_Gaynor: and help as well | 19:59 |
dolphm | glad to see everyone here :) | 19:59 |
briancurtin | #endmeeting | 19:59 |
*** openstack changes topic to "Free for all (Meeting topic: Horizon)" | 19:59 | |
openstack | Meeting 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-3 | 19:59 | |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-11-19.00.html | 19:59 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-11-19.00.txt | 20:00 |
openstack | Log: http://eavesdrop.openstack.org/meetings/python_openstacksdk/2014/python_openstacksdk.2014-03-11-19.00.log.html | 20:00 |
*** jnoller has quit IRC | 20:02 | |
*** mwagner_lap has joined #openstack-meeting-3 | 20:03 | |
*** dtroyer has left #openstack-meeting-3 | 20:18 | |
*** Alex_Gaynor has left #openstack-meeting-3 | 20:20 | |
*** freerider has joined #openstack-meeting-3 | 20:30 | |
*** freerider is now known as Guest6607 | 20:31 | |
*** pballand has joined #openstack-meeting-3 | 20:35 | |
*** d0ugal_ has joined #openstack-meeting-3 | 20:38 | |
*** d0ugal has quit IRC | 20:39 | |
*** julim has quit IRC | 20:40 | |
*** Guest6607 has quit IRC | 20:42 | |
*** d0ugal_ has quit IRC | 20:43 | |
*** lesotorg has joined #openstack-meeting-3 | 20:44 | |
*** d0ugal_ has joined #openstack-meeting-3 | 20:45 | |
*** mwagner_lap has quit IRC | 20:47 | |
*** lesotorg has quit IRC | 20:47 | |
*** SumitNaiksatam has joined #openstack-meeting-3 | 20:51 | |
*** sarob_ has joined #openstack-meeting-3 | 20:51 | |
*** SumitNaiksatam has quit IRC | 21:00 | |
*** jthopkin has joined #openstack-meeting-3 | 21:03 | |
*** izmocherovy has joined #openstack-meeting-3 | 21:21 | |
*** izmocherovy has quit IRC | 21:24 | |
*** HenryG has quit IRC | 21:28 | |
*** peristeri has quit IRC | 21:28 | |
*** alexpilotti has quit IRC | 21:28 | |
*** ftcjeff has quit IRC | 21:28 | |
*** sarob_ has quit IRC | 21:28 | |
*** d0ugal_ has quit IRC | 21:28 | |
*** devlaps1 has quit IRC | 21:28 | |
*** lcheng has quit IRC | 21:28 | |
*** edhall has quit IRC | 21:28 | |
*** briancurtin has quit IRC | 21:28 | |
*** amrith has quit IRC | 21:28 | |
*** annegentle has quit IRC | 21:28 | |
*** cjellick has quit IRC | 21:28 | |
*** lpetrut has quit IRC | 21:28 | |
*** wchrisj has quit IRC | 21:28 | |
*** mfer has quit IRC | 21:28 | |
*** david-lyle has quit IRC | 21:28 | |
*** eghobo has quit IRC | 21:28 | |
*** yamahata has quit IRC | 21:28 | |
*** jtomasek has quit IRC | 21:28 | |
*** dhellmann has quit IRC | 21:28 | |
*** lsmola has quit IRC | 21:28 | |
*** cgoncalves has quit IRC | 21:28 | |
*** yamahata_ has quit IRC | 21:28 | |
*** jamielennox has quit IRC | 21:28 | |
*** ttrifonov has quit IRC | 21:28 | |
*** jthopkin has quit IRC | 21:28 | |
*** pballand has quit IRC | 21:28 | |
*** jeblair has quit IRC | 21:28 | |
*** enykeev has quit IRC | 21:28 | |
*** SergeyLukjanov has quit IRC | 21:28 | |
*** DinaBelova has quit IRC | 21:28 | |
*** haleyb has quit IRC | 21:28 | |
*** notmyname has quit IRC | 21:28 | |
*** lifeless has quit IRC | 21:28 | |
*** markmcclain has quit IRC | 21:28 | |
*** dolphm has quit IRC | 21:28 | |
*** Adri2000 has quit IRC | 21:28 | |
*** troytoman-away has quit IRC | 21:28 | |
*** timello has quit IRC | 21:29 | |
*** wendar has quit IRC | 21:29 | |
*** ttx has quit IRC | 21:29 | |
*** mikal has quit IRC | 21:29 | |
*** anteaya has quit IRC | 21:29 | |
*** jomara has quit IRC | 21:29 | |
*** Adri2000 has joined #openstack-meeting-3 | 21:30 | |
*** pballand has joined #openstack-meeting-3 | 21:30 | |
*** pballand has quit IRC | 21:32 | |
*** lcheng has joined #openstack-meeting-3 | 21:38 | |
*** edhall has joined #openstack-meeting-3 | 21:41 | |
*** wendar has joined #openstack-meeting-3 | 21:41 | |
*** timello has joined #openstack-meeting-3 | 21:41 | |
*** sarob has joined #openstack-meeting-3 | 21:41 | |
*** amrith has joined #openstack-meeting-3 | 21:41 | |
*** devlaps has joined #openstack-meeting-3 | 21:41 | |
*** briancurtin has joined #openstack-meeting-3 | 21:41 | |
*** annegentle has joined #openstack-meeting-3 | 21:41 | |
*** troytoman-away has joined #openstack-meeting-3 | 21:41 | |
*** ttx has joined #openstack-meeting-3 | 21:41 | |
*** pballand has joined #openstack-meeting-3 | 21:41 | |
*** HenryG_ has joined #openstack-meeting-3 | 21:41 | |
*** dolphm has joined #openstack-meeting-3 | 21:41 | |
*** mikal has joined #openstack-meeting-3 | 21:41 | |
*** markmcclain1 has joined #openstack-meeting-3 | 21:41 | |
*** jthopkin has joined #openstack-meeting-3 | 21:41 | |
*** cjellick has joined #openstack-meeting-3 | 21:41 | |
*** jamielennox has joined #openstack-meeting-3 | 21:41 | |
*** david-lyle has joined #openstack-meeting-3 | 21:41 | |
*** eghobo has joined #openstack-meeting-3 | 21:41 | |
*** wchrisj has joined #openstack-meeting-3 | 21:41 | |
*** yamahata has joined #openstack-meeting-3 | 21:41 | |
*** jtomasek has joined #openstack-meeting-3 | 21:41 | |
*** jeblair has joined #openstack-meeting-3 | 21:41 | |
*** cgoncalves has joined #openstack-meeting-3 | 21:41 | |
*** yamahata_ has joined #openstack-meeting-3 | 21:41 | |
*** dhellmann has joined #openstack-meeting-3 | 21:41 | |
*** enykeev has joined #openstack-meeting-3 | 21:41 | |
*** lsmola has joined #openstack-meeting-3 | 21:41 | |
*** ttrifonov has joined #openstack-meeting-3 | 21:41 | |
*** SergeyLukjanov has joined #openstack-meeting-3 | 21:41 | |
*** DinaBelova has joined #openstack-meeting-3 | 21:41 | |
*** haleyb has joined #openstack-meeting-3 | 21:41 | |
*** notmyname has joined #openstack-meeting-3 | 21:41 | |
*** jomara has joined #openstack-meeting-3 | 21:41 | |
*** anteaya has joined #openstack-meeting-3 | 21:41 | |
*** lifeless has joined #openstack-meeting-3 | 21:41 | |
*** pballand has quit IRC | 21:42 | |
*** Adri2000 is now known as Guest68283 | 21:42 | |
*** markmcclain1 has quit IRC | 21:51 | |
*** jpomero has joined #openstack-meeting-3 | 21:55 | |
*** edhall has quit IRC | 22:03 | |
*** sarob has quit IRC | 22:03 | |
*** sarob has joined #openstack-meeting-3 | 22:04 | |
*** jthopkin has quit IRC | 22:05 | |
*** edhall has joined #openstack-meeting-3 | 22:05 | |
*** sarob has quit IRC | 22:09 | |
*** jpomero has quit IRC | 22:13 | |
*** skath has joined #openstack-meeting-3 | 22:13 | |
*** pballand has joined #openstack-meeting-3 | 22:15 | |
*** pballand has quit IRC | 22:22 | |
*** pballand has joined #openstack-meeting-3 | 22:28 | |
*** Sukhdev has joined #openstack-meeting-3 | 22:36 | |
*** edhall has quit IRC | 22:40 | |
*** yamahata has quit IRC | 22:43 | |
*** openstackstatus has joined #openstack-meeting-3 | 22:44 | |
*** edhall has joined #openstack-meeting-3 | 22:44 | |
*** wchrisj has quit IRC | 22:48 | |
*** OSM has joined #openstack-meeting-3 | 23:00 | |
*** OSM is now known as songole | 23:07 | |
*** pballand has quit IRC | 23:07 | |
*** david-lyle has quit IRC | 23:08 | |
*** songole has quit IRC | 23:09 | |
*** lcheng has quit IRC | 23:31 | |
*** mwagner_lap has joined #openstack-meeting-3 | 23:45 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!