Thursday, 2013-06-13

*** amytron has joined #openstack-meeting-alt00:10
*** lastidiot has joined #openstack-meeting-alt00:19
*** dhellmann is now known as dhellmann-away00:43
*** bdpayne has quit IRC00:49
*** yidclare has quit IRC00:58
*** cp16net|away is now known as cp16net01:21
*** esp has joined #openstack-meeting-alt01:42
*** yamahata has quit IRC01:49
*** pcm____ has joined #openstack-meeting-alt01:51
*** pcm____ has joined #openstack-meeting-alt01:52
*** pcm__ has quit IRC01:55
*** markwash has joined #openstack-meeting-alt01:59
*** esp has left #openstack-meeting-alt02:03
*** yamahata has joined #openstack-meeting-alt02:06
*** amytron has quit IRC02:08
*** seanrob has joined #openstack-meeting-alt02:09
*** pcm____ has quit IRC02:15
*** mestery has joined #openstack-meeting-alt02:20
*** jergerber has quit IRC02:49
*** openfly has left #openstack-meeting-alt02:53
*** cp16net is now known as cp16net|away03:00
*** cp16net|away is now known as cp16net03:00
*** bdpayne has joined #openstack-meeting-alt03:18
*** bdpayne has quit IRC03:19
*** seanrob has quit IRC03:27
*** seanrob has joined #openstack-meeting-alt03:28
*** pcm__ has joined #openstack-meeting-alt03:32
*** seanrob has quit IRC03:32
*** Riddhi has quit IRC03:37
*** Riddhi has joined #openstack-meeting-alt03:39
*** SergeyLukjanov has joined #openstack-meeting-alt03:45
*** esp has joined #openstack-meeting-alt03:52
*** esp has left #openstack-meeting-alt03:52
*** amytron has joined #openstack-meeting-alt03:56
*** esp has joined #openstack-meeting-alt04:11
*** akuznetsov has joined #openstack-meeting-alt04:36
*** SergeyLukjanov has quit IRC04:37
*** akuznetsov has quit IRC04:38
*** seanrob has joined #openstack-meeting-alt04:38
*** Riddhi has quit IRC04:42
*** amytron has quit IRC04:42
*** cp16net is now known as cp16net|away04:42
*** amytron has joined #openstack-meeting-alt04:42
*** akuznetsov has joined #openstack-meeting-alt04:43
*** seanrob has quit IRC04:44
*** amytron has quit IRC04:49
*** amytron has joined #openstack-meeting-alt04:51
*** kagan has joined #openstack-meeting-alt04:56
*** amytron has quit IRC04:56
*** amytron has joined #openstack-meeting-alt04:57
*** lastidiot has quit IRC05:16
*** amytron has quit IRC05:26
*** redthrux has quit IRC05:28
*** redthrux has joined #openstack-meeting-alt05:32
*** esp has left #openstack-meeting-alt05:37
*** HenryG_ has joined #openstack-meeting-alt06:02
*** markmcclain has quit IRC06:05
*** markmcclain has joined #openstack-meeting-alt06:05
*** HenryG has quit IRC06:06
*** briancline has quit IRC06:06
*** briancline has joined #openstack-meeting-alt06:07
*** kagan has left #openstack-meeting-alt06:08
*** sdake_ has quit IRC06:42
*** akuznetsov has quit IRC07:13
*** SergeyLukjanov has joined #openstack-meeting-alt07:14
*** briancline has quit IRC07:33
*** briancline has joined #openstack-meeting-alt07:34
*** SergeyLukjanov has quit IRC07:45
*** nmakhotkin has joined #openstack-meeting-alt07:47
*** pcm__ has quit IRC08:02
*** SergeyLukjanov has joined #openstack-meeting-alt08:27
*** SergeyLukjanov has joined #openstack-meeting-alt08:28
*** akuznetsov has joined #openstack-meeting-alt08:30
*** nmakhotkin has quit IRC09:14
*** markwash has quit IRC09:14
*** nmakhotkin has joined #openstack-meeting-alt09:14
*** pcm___ has joined #openstack-meeting-alt10:02
*** pcm___ has quit IRC10:05
*** pcm__ has joined #openstack-meeting-alt10:05
*** pcm__ has quit IRC10:09
*** qwerty_nor has joined #openstack-meeting-alt10:35
*** pcm__ has joined #openstack-meeting-alt11:25
*** pcm__ has quit IRC11:49
*** pcm__ has joined #openstack-meeting-alt11:58
*** dhellmann-away has quit IRC12:00
*** pcm____ has joined #openstack-meeting-alt12:03
*** pcm__ has quit IRC12:05
*** pcm____ has quit IRC12:22
*** pcm___ has joined #openstack-meeting-alt12:25
*** jergerber has joined #openstack-meeting-alt12:30
*** HenryG_ has quit IRC12:53
*** HenryG has joined #openstack-meeting-alt13:09
*** pcm___ has quit IRC13:13
*** pcm___ has joined #openstack-meeting-alt13:18
*** rnirmal has joined #openstack-meeting-alt13:18
*** imsplitbit has joined #openstack-meeting-alt13:29
*** imsplitbit has left #openstack-meeting-alt13:30
*** mtreinish has joined #openstack-meeting-alt13:46
*** markmcclain has quit IRC14:02
*** susanne-balle has joined #openstack-meeting-alt14:03
*** cp16net|away is now known as cp16net14:05
*** jcru has joined #openstack-meeting-alt14:08
*** djohnstone has joined #openstack-meeting-alt14:11
*** lastidiot has joined #openstack-meeting-alt14:14
*** lastidiot has quit IRC14:29
*** Riddhi has joined #openstack-meeting-alt14:35
*** markmcclain has joined #openstack-meeting-alt14:38
*** dhellmann has joined #openstack-meeting-alt14:45
*** amytron has joined #openstack-meeting-alt14:46
*** tanisdl has joined #openstack-meeting-alt15:01
*** tanisdl has quit IRC15:02
*** yidclare has joined #openstack-meeting-alt15:04
*** tanisdl has joined #openstack-meeting-alt15:04
*** lastidiot has joined #openstack-meeting-alt15:04
*** dmitryme has joined #openstack-meeting-alt15:05
*** pcm___ has quit IRC15:18
*** dmitryme has quit IRC15:19
*** pleia2 has joined #openstack-meeting-alt15:20
*** dmitryme has joined #openstack-meeting-alt15:20
*** pcm___ has joined #openstack-meeting-alt15:22
*** bdpayne has joined #openstack-meeting-alt15:41
*** SergeyLukjanov has quit IRC15:50
*** cp16net is now known as cp16net|away16:01
*** cp16net|away is now known as cp16net16:01
*** pcm___ has quit IRC16:01
*** markmcclain has quit IRC16:03
*** akuznetsov has quit IRC16:04
*** seanrob has joined #openstack-meeting-alt16:21
*** yidclare has quit IRC16:22
*** seanrob has quit IRC16:23
*** seanrob has joined #openstack-meeting-alt16:24
*** seanrob has quit IRC16:25
*** seanrob has joined #openstack-meeting-alt16:25
*** dmitryme has quit IRC16:26
*** kevinconway has quit IRC16:28
*** seanrob has quit IRC16:28
*** seanrob has joined #openstack-meeting-alt16:28
*** seanrob_ has joined #openstack-meeting-alt16:33
*** seanrob has quit IRC16:33
*** seanrob has joined #openstack-meeting-alt16:36
*** seanrob_ has quit IRC16:36
*** seanrob_ has joined #openstack-meeting-alt16:44
*** seanrob__ has joined #openstack-meeting-alt16:47
*** seanrob has quit IRC16:47
*** seanrob_ has quit IRC16:49
*** seanrob__ has quit IRC16:50
*** seanrob has joined #openstack-meeting-alt16:50
*** seanrob has quit IRC16:52
*** kevinconway has joined #openstack-meeting-alt16:52
*** markmcclain has joined #openstack-meeting-alt16:53
*** SergeyLukjanov has joined #openstack-meeting-alt16:56
*** seanrob has joined #openstack-meeting-alt16:56
*** esp1 has joined #openstack-meeting-alt16:57
*** dhellmann has quit IRC16:57
*** dhellmann has joined #openstack-meeting-alt16:57
*** seanrob_ has joined #openstack-meeting-alt16:58
*** esp1 has quit IRC16:59
*** seanrob has quit IRC16:59
*** esp1 has joined #openstack-meeting-alt17:03
*** markmcclain1 has joined #openstack-meeting-alt17:04
*** seanrob_ has quit IRC17:04
*** markmcclain has quit IRC17:04
*** harlowja has quit IRC17:06
*** seanrob has joined #openstack-meeting-alt17:06
*** seanrob_ has joined #openstack-meeting-alt17:07
*** seanrob__ has joined #openstack-meeting-alt17:08
*** seanrob_ has quit IRC17:08
*** harlowja has joined #openstack-meeting-alt17:09
*** yidclare has joined #openstack-meeting-alt17:10
*** seanrob has quit IRC17:10
*** seanrob__ has quit IRC17:22
*** dmitryme has joined #openstack-meeting-alt17:28
*** seanrob has joined #openstack-meeting-alt17:32
*** pcm___ has joined #openstack-meeting-alt17:37
*** hub_cap has left #openstack-meeting-alt17:40
*** seanrob_ has joined #openstack-meeting-alt17:41
*** seanrob has quit IRC17:42
*** seanrob has joined #openstack-meeting-alt17:45
*** seanrob_ has quit IRC17:47
*** seanrob has quit IRC17:47
*** seanrob has joined #openstack-meeting-alt17:48
*** seanrob has quit IRC17:50
*** nkonovalov has joined #openstack-meeting-alt17:50
*** seanrob_ has joined #openstack-meeting-alt17:50
*** seanrob_ has quit IRC17:53
*** seanrob has joined #openstack-meeting-alt17:54
*** seanrob_ has joined #openstack-meeting-alt17:55
*** Nadya has joined #openstack-meeting-alt17:56
*** esp1 has left #openstack-meeting-alt17:58
*** seanrob has quit IRC17:58
*** akuznetsov has joined #openstack-meeting-alt17:58
*** aignatov3 has joined #openstack-meeting-alt18:00
*** jmaron has joined #openstack-meeting-alt18:03
*** jspeidel has joined #openstack-meeting-alt18:03
SergeyLukjanovhi everyone, who's around for the Savanna meeting today?18:03
aignatov3hi18:03
jmaronJohn and Jon are here.  Erik will log in shortly18:04
aignatov3good, today I'm aignatov3 :)18:04
SergeyLukjanovjmaron, great18:04
dmitrymethanks jmaron18:04
dmitrymelets start18:04
SergeyLukjanovaignatov3, waiting for aignatov4218:04
dmitryme#startmeeting Savanna18:04
aignatov3xD18:04
openstackMeeting started Thu Jun 13 18:04:51 2013 UTC.  The chair is dmitryme. Information about MeetBot at http://wiki.debian.org/MeetBot.18:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:04
*** openstack changes topic to " (Meeting topic: Savanna)"18:04
openstackThe meeting name has been set to 'savanna'18:05
SergeyLukjanovopenstack, thank you!18:05
dmitrymeHere is today's agenda:18:05
dmitryme#topic Meeting Agenda18:05
dmitryme#info 1. UI updates18:05
*** openstack changes topic to "Meeting Agenda (Meeting topic: Savanna)"18:05
dmitryme#info 2. Savanna core updates18:05
dmitryme#info 3. Vanilla Plugin updates18:05
dmitryme#info 4. Swift Integration updates18:05
dmitryme#info 5. Other Updates18:05
dmitrymeLets go through the items one by one18:06
dmitryme#topic UI updates18:06
*** openstack changes topic to "UI updates (Meeting topic: Savanna)"18:06
SergeyLukjanovdmitryme, bulk messaging guy :)18:06
dmitrymeNikita, update if you please18:06
aignatov3I recommend to do updates in a few words, no fancy18:06
nkonovalovwe have finished our rest client to access rest api for ui18:07
nkonovalovnow tables and wizards are populated using it18:07
nkonovalovnow, cluster creation wizard implementation is in progress18:07
nkonovalovthat's our ui update18:08
SergeyLukjanovbtw here is our dashboard repo18:08
SergeyLukjanov#link http://github.com/stackforge/savanna-dashboard18:08
dmitrymethank you18:08
dmitryme#topic Savanna core updates18:08
*** openstack changes topic to "Savanna core updates (Meeting topic: Savanna)"18:08
dmitrymeSergey please18:08
SergeyLukjanovdmitryme, thank you18:08
SergeyLukjanovwe are working hard on the core code implementation :)18:09
SergeyLukjanovi think that the most part of the behaviors has been implemented18:09
SergeyLukjanovnow we are improving object model18:09
SergeyLukjanovand code around the "convert" method18:09
SergeyLukjanovof pluggable provisioning mechanism18:10
SergeyLukjanovmm, dmitryme, let's go on18:10
dmitrymesure18:10
dmitryme#topic Vanilla Plugin updates18:10
*** openstack changes topic to "Vanilla Plugin updates (Meeting topic: Savanna)"18:10
dmitrymeAlexander, please update18:10
aignatov3ok, last week I'm working on reference implemntation of Vanilla plugin18:11
aignatov3it's almost completed18:11
aignatov3just polishing it18:11
aignatov3btw, link18:11
aignatov3#link https://review.openstack.org/#/c/31532/18:11
aignatov3special thanks to Alex K for valuable comments)18:12
aignatov3you can try use it, it works as expectd I think18:12
aignatov3be sure, It works on our Lab. I've checked it xD18:13
SergeyLukjanovit works on my laptop too :)18:13
aignatov3Dima, please move on18:13
dmitrymethank you Alexander18:14
dmitryme#topic Swift Integration updates18:14
*** openstack changes topic to "Swift Integration updates (Meeting topic: Savanna)"18:14
dmitrymeNadya, please tell us18:14
Nadyahi all :)18:14
Nadyaswift integration to savanna is done. The first version is on review: https://review.openstack.org/3243218:15
Nadya Tomorrow I'm planning to submit the final version18:15
*** ErikB has joined #openstack-meeting-alt18:15
NadyaTo make swift work with Hadoop on OpenStack it would be necessary not only to integrate savanna+swift but add several lines of code to each plugin.18:15
NadyaTomorrow the change-request for vanilla-plugin would be available and it may be used as an example18:16
NadyaI've tested swift-integration with vanilla-plugin and it works on our lab18:16
NadyaThat's all18:17
dmitrymeok, thank you and finally18:17
dmitryme#topic Other updates18:17
*** openstack changes topic to "Other updates (Meeting topic: Savanna)"18:17
dmitrymefolks, anything you want to share?18:17
SergeyLukjanovyep, I want to update on Cinder integration18:18
SergeyLukjanovwe are start working on basic integration with Cinder to provide an ability to auto create/attach volumes to instances of Hadoop cluster18:18
SergeyLukjanovI think it'll be done to the end of the next wek18:18
SergeyLukjanovweek*18:18
SergeyLukjanovthat's all from my side18:18
SergeyLukjanovare there any other updates?18:19
jmaronwe are moving along with our plugin.  shooting for some internal testing today and tomorrow with an initial merge into savanna repo tomorrow18:19
dmitrymejmaron, great news!18:19
SergeyLukjanovjmaron, great!18:19
aignatov3I have a few words about diskimage-builder instructions of Vanilla images creation for Savanna are in progress18:19
dmitrymethank you!18:20
dmitrymeanything else?18:20
aignatov3q&a?18:20
SergeyLukjanovyep, I think it's time for q&a18:21
jmaronone question:  can we get a listing of information/attributes available from the context/current?18:21
dmitrymeyep, I think it is about time18:21
dmitryme#topic General Discussion18:21
*** openstack changes topic to "General Discussion (Meeting topic: Savanna)"18:21
jmarondoesn't have to be now, but if we can get an email to the list or the like that would be helpful18:22
SergeyLukjanovjmaron, it contains user id, tenant id, auth token, request headers, database session18:22
SergeyLukjanov#link https://github.com/stackforge/savanna/blob/master/savanna/context.py#L3118:22
jmaronok.  thx18:23
jmaronanother question:  why is there a need for a username and password for the images?  aren't we using key pairs?18:23
SergeyLukjanovadditionally, there are some helpers like nova client and etc. that are available any ware but backed by the current context18:24
SergeyLukjanovjmaron, we don't need password now18:24
jmaronok18:24
jmaronso I'll leave it blank in savanna.conf18:24
SergeyLukjanovjmaron, only username to determine which user should be used for provisioning and etc.18:24
SergeyLukjanovjmaron, what option do you mean?18:25
dmitrymejmaron, Savanna still need admin password in Savanna.conf18:25
SergeyLukjanovpassword in cluster_node group?18:25
jmaron# User's password (string value)18:25
jmaron#password=swordfish18:25
SergeyLukjanovlook like I forgot to remove it :(18:25
SergeyLukjanov#action SergeyLukjanov to cleanup config samples18:26
dmitrymehm, as far as I recall we used OS admin credentials to verify user's token18:26
dmitrymeok, I got it18:27
SergeyLukjanovdmitryme, we are speaking about different configs :)18:27
dmitrymethat is not admin password, that's image password18:27
jmaronyes18:28
jmaronit looks like the 'extra' field in Instance object was removed?18:28
SergeyLukjanovjmaron, no, it's mixed to the Instance object https://github.com/stackforge/savanna/blob/master/savanna/db/models.py#L14518:29
jmaronah…ok18:29
SergeyLukjanovjmaron, Cluster, NodeGroup and Instance objects have an extra field18:30
jmarongood.  thanks18:30
Nadyajmaron, are you interested in swift integration?18:30
Nadyajmaron, in your plugin18:31
jmaronyes18:32
SergeyLukjanovare there any other questions?18:33
jmaronnot from me :)18:33
*** markwash has joined #openstack-meeting-alt18:34
SergeyLukjanovI think that all for today :)18:36
SergeyLukjanovthat's *18:36
dmitrymethanks everyone for taking part in the meeting!18:36
jmaronok.  thank you18:36
SergeyLukjanovopenstack, please, end the meeting!18:36
dmitryme#endmeeting18:36
*** openstack changes topic to "OpenStack meetings (alternate)"18:36
aignatov3great! our first half-hour meeting :)18:36
openstackMeeting ended Thu Jun 13 18:36:30 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:36
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-06-13-18.04.html18:36
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-06-13-18.04.txt18:36
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-06-13-18.04.log.html18:36
*** nkonovalov has quit IRC18:37
*** ruhe has joined #openstack-meeting-alt18:37
*** Nadya has quit IRC18:39
*** qwerty_nor has quit IRC18:42
*** seanrob_ has quit IRC18:51
*** markmcclain1 has quit IRC18:57
*** bryansd has joined #openstack-meeting-alt19:00
*** ametts has joined #openstack-meeting-alt19:01
*** flaper87 has joined #openstack-meeting-alt19:01
*** aignatov3 has quit IRC19:02
*** kgriffs has joined #openstack-meeting-alt19:03
*** malini has joined #openstack-meeting-alt19:04
flaper87soooooooooooooooooo19:05
kgriffsok folks, ready to get this party started?19:06
flaper87\o/19:06
* ametts queues the music19:06
flaper87dumbs dumbs dumbs dumbs19:06
kgriffs#startmeeting marconi19:06
openstackMeeting started Thu Jun 13 19:06:56 2013 UTC.  The chair is kgriffs. Information about MeetBot at http://wiki.debian.org/MeetBot.19:06
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:06
*** openstack changes topic to " (Meeting topic: marconi)"19:07
openstackThe meeting name has been set to 'marconi'19:07
kgriffs#topic town hall19:07
*** openstack changes topic to "town hall (Meeting topic: marconi)"19:07
flaper87\o/19:07
kgriffsok, any folks in the room with general questions about Marconi?19:07
*** oz_akan has joined #openstack-meeting-alt19:08
flaper87tic, toc, tic, toc, tic, toc19:08
oz_akan:)19:08
kgriffsgreat, so sounds like everyone understands what's going on with the project 100% or simply doesn't care. :p19:08
*** markmcclain has joined #openstack-meeting-alt19:08
kgriffsso, general questions regarding the project before we talk about incubation?19:09
* kgriffs watches a tumbleweed roll by19:10
kgriffsok, so we got a couple of feedback items from the dev list post19:10
kgriffsVish recommended we move project ID out of the url, and just get it from a header19:11
flaper87sounds like something we could do for H-219:11
flaper87thoughts?19:11
kgriffssounds good to me. Since this changes pretty much every URI path, we should do it sooner rather than later.19:12
flaper87right19:13
kgriffshttps://trello.com/c/oxPdEQpJ19:13
amettsDefinitely before there are clients out there in the wild that are coded to the old scheme.19:13
flaper87we could schedule sqlalchemy's for H-3 if you agree19:13
kgriffsNot sure if it's worth creating a bp19:13
flaper87kgriffs: I'd say so, just to keep track in lp as well19:14
kgriffsflaper87: k, I'll ad that. Can you set the milestone for sqlalchemy to H3?19:14
flaper87sure19:14
kgriffs#action kgriffs to add blueprint for moving project id to headers19:15
kgriffs#action flaper87 to schedule sqlalchemy driver for H319:15
*** torgomatic has joined #openstack-meeting-alt19:15
flaper87kgriffs: re sqlalchemy, I think that back-end is a replacement for sqlite19:16
flaper87I mean, once it is done we'll just remove sqlites19:16
kgriffs(for the folks following along at home, the sqlalchemy bp came from some other feedback we got that we should support MySQL or some other mainstream RDBMS)19:17
*** oz_akan has quit IRC19:17
flaper87re blueprints, we should start setting some of those bp as Implemented and start tracking upcoming changes as bugs or new blueprints19:18
*** oz_akan has joined #openstack-meeting-alt19:18
oz_akanHA part of mysql is very difficult compared to mongodb19:18
kgriffsflaper87: that's fine re sqlite, since sqlalchemy supports that as a dialect19:18
kgriffs(so we can still use for unit tests)19:18
flaper87kgriffs: we kind of talked about that a few months ago (sqlalchemy) I'm glad Jay helped us on making up our minds about it19:18
flaper87kgriffs: right19:18
flaper87oz_akan: I don't think we need to do load / HA / security tests on every transport / storage we support19:19
kgriffsflaper87: I spent some time yesterday cleaning up the bp's - i'll take another pass today19:19
flaper87that's kind of a deployment decistion19:19
kgriffs#action kgriffs to update bp's19:19
kgriffswell, it seems like we will need to have a reasonable idea of performance/load that a given supported driver can handle19:20
kgriffs(in it's vanilla configuration)19:20
kgriffsand there's no reason we can't run security tests on all drivers19:20
flaper87we can do it but should we? (I'm speaking of storages here)19:21
kgriffsthen we can sort of recommend different backends depending on people's needs19:21
kgriffswell, we should do security testing. I don't want to be blamed for someone's cluster getting cracked.19:22
flaper87agreed about security19:22
kgriffsas for load testing, eventually I say yes, but initially we don't need to.19:22
kgriffs(useful for comparison; maybe one of these other solutions will actually be faster or something than mongo, who knows?)19:23
oz_akanI wonder how a RDBMS would make the queueing service better...19:23
flaper87oz_akan: We'll need to test that19:24
kgriffswell, the one advantage is you get auto-inc keys19:24
kgriffsbut you trade that for other things19:24
*** yidclare has quit IRC19:24
*** pcm___ has quit IRC19:25
kgriffsflaper87: agreed. we have some experimenting to do, and we don't know yet what the usage patterns are going to be with real users.19:25
oz_akankgriffs: yes, since this is a service, I want to think it will be easy to manage19:25
kgriffsheh, too bad we didn't just do sqlalchemy from the beginning, since we needed sqlite for prototyping and unit testing anyway.19:26
kgriffsAnyway, let's move on.19:27
kgriffsSo, I'm trying to see if Meghan is here from Rackspace19:27
kgriffsactually, I think she is on vacation or something today19:27
flaper87Meghaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaan, you there?19:27
flaper87awwwwww :(19:27
kgriffsso, hopefully she'll join us next time, but she will be helping us get the incubation wiki page filled out and keep track of the stuff we need to do otherwise.19:28
kgriffs(to get incubated)19:28
flaper87awesome, that sounds really great, we need that19:28
amettskgriffs:  Wanna tag that as an action for purposes of the minutes?19:29
kgriffs#action Megan to get our incubation request page filled out19:29
kgriffs#link https://wiki.openstack.org/wiki/Marconi/Incubation19:30
kgriffsso, I was trying to remember how soon we needed to apply...19:31
flaper87we said mid H-219:31
flaper87but I guess end H-2 is find as well19:31
*** ruhe has left #openstack-meeting-alt19:31
kgriffsok, so that puts us at the end of this month, July 18 at the latest19:32
flaper87right19:33
flaper87#link https://wiki.openstack.org/wiki/Havana_Release_Schedule19:34
kgriffsIf we can get the wiki page updated in the next several days, then we can send to the appropriate lists and git-r-done19:35
kgriffs#link https://wiki.openstack.org/wiki/Governance/NewProjects19:35
amettsgit has that command?  Why haven't we used it yet?19:35
kgriffsjust came out in the last release. ;)19:36
kgriffsgit r done19:36
kgriffs#action kgriffs to follow up with Megan on preparing and submitting incubation request.19:36
kgriffsok, open discussion - anything folks want to discuss on the topic of the direction of the project, incubation, whatever?19:37
flaper87o/19:38
flaper87Don't want to push but, do we have a due date for the load tests ?19:38
kgriffs#topic load testing19:38
*** openstack changes topic to "load testing (Meeting topic: marconi)"19:38
flaper87I just want to have an idea of when we'll be able to test that and get some realworld results19:39
kgriffs+1, the sooner the better19:39
kgriffsmalini, oz_akan: ^^19:39
maliniwe have the tests ready..once we have the env, we can break it :)19:39
oz_akanhmm19:40
oz_akanworking on CD a few days19:40
oz_akanwe already have the test env with the latest code19:40
oz_akanwe can benchmark it, right Malini?19:40
maliniyes19:40
kgriffsso, you have the load generators provisioned already as well?19:41
maliniprovisioned?19:41
maliniWe have load generators created manually..not yet salt-ed19:41
kgriffsi.e., there's salt for that19:41
oz_akanas soon as done with CICD, I am working on that19:41
kgriffskk19:41
flaper87are / will be the results of those tests public? I mean, we page or something similar19:41
kgriffsmanual is fine for now19:41
flaper87webpage*19:42
oz_akanflaper87: yes, sure we can19:42
maliniwe'll have tht19:42
kgriffsit would be kind of cool to track those over time19:42
flaper87awesome19:42
kgriffsgraphtastic19:42
* flaper87 very happy about that19:42
*** vipul is now known as vipul|away19:42
*** vipul|away is now known as vipul19:42
maliniyes.we will store those results & use them as baseline for future releases as well19:42
kgriffscan we dump those to graphite, maybe the nightly run?19:42
kgriffs(from the mainline)19:43
oz_akanafter a change on master branch,we will run these tests19:43
kgriffsor whatever, anyway, malini can u register a bp?19:43
malinihavent tried tht yet..But we sure can19:43
oz_akanto automate them, I need to work with Malini19:43
malinibp for graphite ?19:43
flaper87wasn't there one?19:43
oz_akanI think I can finish CICD by Tuesday, so next week test environment can be ready19:43
maliniwe already have bp for load test https://blueprints.launchpad.net/marconi/+spec/load-test19:44
kgriffsmalini: for graphing performance and load watermark over time19:44
kgriffsa separate one, we can do it later19:44
maliniok19:44
kgriffsfor now, just dump them somewhere and people can make their own pretty graphs if they want. :p19:44
kgriffs(by "them" I mean the tsung output)19:45
*** yidclare has joined #openstack-meeting-alt19:45
maliniok :)19:45
kgriffsok, so we have a home for the salt and load/security tests?19:45
maliniwe have a home..It'll soon have inhabitants19:46
kgriffsexcellent19:46
maliniTo start with I'll add the tsung xmls19:46
kgriffsre security tests, it would be nice to have at least some very basic ones done by H319:46
kgriffsmaybe we need to split up the bp?19:47
maliniI havent done much on security testing yet19:47
maliniIt'll be good to define some specific stuff we need by H319:47
kgriffskk, let me rename this one to "basic-security-tests", and you can register another blueprint for doing more comprehensive ones.19:48
kgriffshttps://blueprints.launchpad.net/marconi/+spec/security-testing19:48
maliniCan I just keep this as is & register a new one for basic-security-tests ?19:49
kgriffshttps://blueprints.launchpad.net/marconi/+spec/security-testing-basic19:50
kgriffsoops19:50
kgriffssorry19:50
malininp19:50
maliniI'll just add a new one for comprehensive test19:50
kgriffskk, and feel free to add work items to those19:51
kgriffsok, anything else on the topic of quality?19:51
malinino19:51
*** seanrob has joined #openstack-meeting-alt19:51
kgriffs#action malini to add bp for comprehensive security testing19:51
kgriffs#action malini to add work items to those bp's19:51
*** zhiyan has joined #openstack-meeting-alt19:51
kgriffs#topic rename "exceptions" modules to "errors"19:52
*** openstack changes topic to "rename "exceptions" modules to "errors" (Meeting topic: marconi)"19:52
kgriffsso, any objections to doing this?19:53
flaper87nope19:53
kgriffsseems more idomatic to call them errors, IMHO19:53
kgriffsand may earn us brownie points with the TC19:53
* kgriffs can hope19:54
flaper87dude, out of my mind, I was just writing the "Why?" question19:54
flaper87cool19:54
*** akuznetsov has quit IRC19:54
kgriffskk, it's super quick change19:54
kgriffsI wasn't going to rename the exceptions to append "Error" at this time, but maybe later where it makes sense19:55
kgriffs#action kgriffs to rename exceptions to errors19:55
flaper87wwkk19:55
flaper87I'll migrate the transport / storage load to stevedore19:55
kgriffs#action flaper87 to migrate the transport / storage load to stevedore19:56
kgriffslast item, real quick19:56
kgriffsso, right now we aren't doing any authorization:19:56
*** dmitryme has quit IRC19:56
kgriffshttps://blueprints.launchpad.net/marconi/+spec/project-id-authorization19:56
kgriffsand we *need* to be doing it19:57
flaper87wait, you mean the keystone thing?19:57
kgriffsso, keystone does authentication, meaning the token is good, and passes through project id19:58
flaper87right19:58
kgriffsbut we aren't actually enforcing anything about which account can access which project19:58
flaper87but that's done by keystone19:59
flaper87during the login process19:59
kgriffsbut this is from the old model of having the project id in the url19:59
* kgriffs just has an ah-ha moment19:59
kgriffsso, check me on this, but user passes auth token to api20:00
*** ErikB has quit IRC20:00
kgriffsmiddleware checks auth token, injects project id header20:00
kgriffsthe marconi just uses that project id20:00
flaper87right20:00
flaper87:)20:00
* markwash is *not* in a rush to start the glance meeting, so please take your time20:00
kgriffsas long as the user can't specify the project id directly, we are cool20:00
*** esheffield has joined #openstack-meeting-alt20:00
kgriffsmarkwash: no worries, we are wrapping up now20:01
flaper87kgriffs: that's already enforced by keystone's log-in process20:01
*** bdpayne has quit IRC20:01
flaper87so, we're good there20:01
flaper87it already checks user1 has permissions in project120:01
flaper87and so on20:01
kgriffssweet. OK. I haven't looked yet, but does the middleware still do X-Tenant-ID or is it using the new "project" name?20:01
kgriffsoic, so a user can specify project header if they like?20:02
* kgriffs should know this20:02
*** bdpayne has joined #openstack-meeting-alt20:02
flaper87well, it has to specify the project it wants to log-in to20:02
*** seanrob_ has joined #openstack-meeting-alt20:02
kgriffsmakes sense20:03
kgriffskk, let's wrap up20:03
flaper87:D20:03
kgriffsany parting thoughts20:03
kgriffs?20:03
flaper87nope20:03
kgriffs#endmeeting20:04
*** openstack changes topic to "OpenStack meetings (alternate)"20:04
openstackMeeting ended Thu Jun 13 20:04:02 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-13-19.06.html20:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-13-19.06.txt20:04
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-06-13-19.06.log.html20:04
* flaper87 puts his Glance's hat on20:04
markwash#startmeeting glance20:04
openstackMeeting started Thu Jun 13 20:04:34 2013 UTC.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.20:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:04
*** openstack changes topic to " (Meeting topic: glance)"20:04
openstackThe meeting name has been set to 'glance'20:04
markwashhowdy glance folks20:04
flaper87\o/20:04
zhiyano/20:04
flaper87\o/20:05
markwashhaha20:05
flaper87just to make some more noise20:05
flaper87:D20:05
*** jmaron has quit IRC20:05
markwashso, maybe a lighter meeting today20:05
zhiyan\o/20:05
*** malini is now known as malini_away20:05
markwash#topic open discussion20:05
*** openstack changes topic to "open discussion (Meeting topic: glance)"20:05
*** ametts has left #openstack-meeting-alt20:05
markwashesheffield: did you have notes for us about v1 vs v2 documentation?20:05
zhiyanmarkwash: hi do you checked https://review.openstack.org/#/c/31591/5 ? see my comments?20:06
*** seanrob has quit IRC20:06
esheffieldmarkwash: not so much new on the documentation front, more just v1 / v2 work in general20:06
*** markmcclain has quit IRC20:07
markwashesheffield: ah, okay sorry I misunderstood20:07
esheffieldmarkwash: you saw the email between waldon and me?20:07
markwashyes20:07
*** lindj has joined #openstack-meeting-alt20:07
esheffieldwas basically going to just touch on that if anyone else had interest / was working on it20:07
markwashesheffield: so you're asking about interest in this blueprint https://blueprints.launchpad.net/python-glanceclient/+spec/glance-client-v2and20:08
markwashhttps://blueprints.launchpad.net/python-glanceclient/+spec/glance-client-v220:08
markwashmaybe just that second one20:08
*** markmcclain has joined #openstack-meeting-alt20:09
esheffieldright - waldon had been working on it, but hasn't for a while so we're going to pick it up20:09
markwashsounds great to me20:09
esheffieldbut wanted to see if anyone else in the group here might be doing related work already as well20:09
markwashI know waldon has been distracted from that work for some time20:09
markwashflaper87: I know you've been following the v2 glanceclient work20:10
markwashesheffield: but I'm sure you all are welcome to finish off that blueprint20:10
*** jmaron has joined #openstack-meeting-alt20:10
markwashI think you guys might be best positioned to give it the attention it deserves, esheffield20:10
*** seanrob_ has quit IRC20:10
esheffieldmarkwash: sounds good - I know we're going to need that functionality pretty soon20:11
flaper87yeah, I've followed it but I'm more than happy to see folks signing up for it20:11
markwashzhiyan: so I took a look at that review. . I'm not totally sure how I feel20:11
markwashzhiyan: there are two issues I think20:11
zhiyanmarkwash: I just means maybe there should have a checking for location adding20:11
markwash1) when you add locations to the image, and then delete the image, should glance delete the underlying location20:12
markwash2) when you add a location to the image, (how) should glance verify the validity of that location and its underlying data20:12
zhiyan2# agree, that is my comments mean also.20:13
markwashsince the initial target for adding locations is as a protected ( or admin-only) action, we might want to be more permissive than otherwise20:13
flaper87I'm not sure I agree with #220:13
zhiyanfor 1#, IMO we should just delete location records only but not delete image data from those locations..20:13
flaper87How would glance verify that? Wouldn't that take us back to the discussion about whether glance should verify tenants ids or not?20:14
zhiyanflaper87: use store drivers check it IMHO20:14
zhiyanflaper87: such as: check scheme is well-know and valid20:15
markwashflaper87: I am tending towards the idea that we should not treat directly added locations as different from the typical location case20:15
flaper87well, but that doesn't verify the underlying data20:15
flaper87zhiyan: ^20:15
markwashflaper87: but it would be easy to load the location into the store and at least run "get_size" to see if it theoretically works20:15
flaper87markwash: I think we should verify the image location is supported and that's it20:16
zhiyanmarkwash: probable it's a good method20:16
markwashI'd like to think a bit more about it, and then take my feedback to the review20:16
markwashI owe jbresnah some serious review time in any case20:16
flaper87me too20:17
zhiyanflaper87: yes, just like my comments :)20:17
zhiyanthank you20:17
markwashzhiyan: is there a specific reason why you don't want glance to delete the image location in the cinder volume case?20:17
flaper87zhiyan: sorry, haven't read them, will do tomorrow :(20:17
zhiyanmarkwash: sorry, do you means https://review.openstack.org/#/c/32864/ ? I just want to paste it here...20:18
markwashzhiyan, thanks20:19
markwashflaper87: async stuff?20:20
flaper87markwash: yup20:20
markwashI've got a full-time upstream week coming up20:20
markwashand i'd like to take care of as much of that as possible (unless I'm stepping on toes!)20:20
flaper87awesome, sounds really great20:20
markwashso I think the real weakness in the poc I have up now20:21
markwashhttps://review.openstack.org/#/c/31874/20:21
flaper87so, I think I'll give up on the idea of using Oslo's messaging code for the async work bp20:21
markwashis that it doesn't really show anything about how to implement the actual asynchronous work20:21
markwashflaper87: oh?20:22
zhiyanmarkwash: ok, because I have check 'buyer-beware' with jbresnahan before, under this principle, user should manually handle image data... and also under current implementation, cinder-store not create volume when user register an image (make sense, right? he just register a external volume as an image), so when user delete the image recode, store should not delete it also....20:22
flaper87right but, I saw that Heat has something similar that we could use in glance as well20:22
flaper87which seemed pretty solid20:22
flaper87we could also take some ideas from Oslo's messaging but not using it directly (unless we want to have distributed async workers)20:23
zhiyanflaper87: does Task and TaskRunner is ready?20:23
markwashflaper87: I really want to support distributed async workers, but not have the distributed nature of it reflected in the interface20:23
markwashflaper87: like, all implementations of that interface are async20:24
markwashflaper87: but some of them, based only on their internal implementation with no interface changes, are also distributed across other hosts20:24
flaper87markwash: If we want to support async workers then I would say we should use Oslo's messaging and work along those lines20:24
markwashzhiyan: I wanna circle back around to the buyer-beware part, sorry for a brief delay20:24
flaper87markwash: sorry, I meant distributed async workers20:25
flaper87:D20:25
markwashflaper87: I actually can't tell if we're agreeing or disagreeing :-)20:25
flaper87hehehe, sorry, let start again20:25
zhiyanflaper87: seems like a glance-worker service?20:25
flaper87markwash: I agree we should support distributed async workers20:26
flaper87and IMHO, the easiest way to do that is relying on Oslo's messaging library20:26
flaper87because it's ready20:26
markwashcool20:26
*** esp2 has joined #openstack-meeting-alt20:26
flaper87markwash: I mean, the rpc one, we're still working on the new one20:27
markwashso then I just need to  look more closely at what using oslo messaging would mean in the code20:27
flaper87right20:27
flaper87it's not so different and I think it integrates better20:27
flaper87zhiyan: mmh, could be, yup!20:27
markwashit still seems like what we might disagreeing on is where rpc.cast gets called20:27
flaper87markwash: right20:27
markwashi.e., is it called in a driver for the async processing, or is it called in something more like "core" glance20:28
flaper87in your POC it's called here: https://review.openstack.org/#/c/31874/2/glance/api/v2/images.py20:28
zhiyanzhiyan: flaper87: i just think, for glance-cinder-store, when user use volume as an image and the volume stored in backend by FC, then maybe only some host have FC HBA card (hardward), so glance-worker could running on that node...20:29
markwashso if I were using rpc.cast, it would go in those functions ?20:29
markwashzhiyan: that's a great use case for distributed!20:30
markwashty20:30
flaper87yeah, I think so20:30
flaper87because if we use rpc.cast we wouldn't need to create an Async domain20:30
zhiyanmarkwash: yes, in cinder, that's a service plan for that: cinder-io-worker...not start yet20:30
flaper87we could easily integrate it in the existing doamins20:31
markwashI'm guessing there must be something a bit awkward about representing asynchronous tasks within the domain model that I'm not noticing20:32
zhiyanzhiyan: first step, i think we can put async message handler in glance-api, and when we need, we can pick it out to a new distributed service...20:32
flaper87markwash: mmh, where would you put it instead?20:33
flaper87Do you think a separate domain makes more sense?20:34
markwashflaper87: no no, I think I mis spoke20:34
zhiyandomain.py ? right, flaper8720:34
markwashI guess I'm just a bit prejudiced against putting rpc.cast directly in api calls20:34
markwashrpc feels kind of "external" and I like to hide that away form the core of the project as much as possible20:35
markwashbut I confess I haven't dug deep enough to know the actual tradeoffs well20:35
flaper87well, I guess we could take some time to think about where to put it a bit further20:35
markwashlike, when I'm unit testing api calls, I don't want to have to stub out rpc20:35
*** ashwini_ has joined #openstack-meeting-alt20:35
flaper87markwash: mmh, i see what you mean20:36
markwashflaper87: that will probably be the first thing I do, I'll keep it out in the open so people can see where I'm headed and offer more of this good critique20:36
flaper87markwash: would it make sense to enable / disable async support ?20:36
markwashzhiyan: I'm sure we can support both local and distributed in either case, and that's definitely on the roadmap. . so I'm glad you and I are on the same page20:37
*** SergeyLukjanov has quit IRC20:37
markwashflaper87: hmm, I dunno.. . I hadn't thought you would be able to *disable* asynchronous processing20:37
zhiyan:), cool!20:37
markwashzhiyan, re buyer beware. . I think you're right about the user being surprised if glance deletes their volume for example20:38
markwashzhiyan: but maybe this isn't a "user" oriented use case yet20:38
zhiyanmarkwash: yes, i agree20:38
zhiyanmarkwash, flaper87: shall we talk about glance-cinder-store now?20:39
zhiyani have post a draft patch for you review, https://review.openstack.org/#/c/32864/20:39
markwashzhiyan: sure, I saw your review, I still need to dig into it20:39
zhiyanmarkwash: thanks.20:39
* flaper87 hasn't reviewed that one yet20:39
flaper87zhiyan: in my To review list20:40
flaper87oh you posted that today20:40
flaper87cool20:40
zhiyanflaper87: :), yes20:40
zhiyanthank you all :)20:40
flaper87zhiyan: you'll have to give some pop-tarts away20:40
flaper87:D20:40
* flaper87 is always hungry20:40
zhiyanbtw, for nova side multiple-location image preparing support, I have created a bp https://blueprints.launchpad.net/nova/+spec/image-multiple-location20:41
markwashzhiyan: cool20:41
*** esp2 has left #openstack-meeting-alt20:42
zhiyanwhen glance side ready, i will propose it again, and i will take high level design for it today20:42
flaper87cool, thanks for that20:42
markwashzhiyan: great. .thanks for getting on top of that. . it will be good to see if we get any feedback from nova folks20:42
markwashcan we talk a little bit about testing now, and then maybe we're done for the day. . .20:42
flaper87sure20:43
markwash#link https://etherpad.openstack.org/glance-improving-test-cycle-times20:43
markwash#link https://review.openstack.org/#/c/30512/20:43
zhiyanwe have talked that draft plan in glance irc channel...when we finish the last weekly meeting20:43
zhiyani will keep that way.20:44
zhiyanok. next.20:44
markwashso I put together a review (that needs a lot of fixup, thanks for the notes flaper87 ) that tries to speed up glance testing20:44
markwashzhiyan, sorry didn't mean to rush you!20:44
markwashand when I was talking about it with some folks earlier, it seemed like we needed a high level strategy for what testing in glance should look like20:44
markwashI had some spare coffee-fueled moments on the train and put together the etherpad I linked above20:45
zhiyanmarkwash: no, just for image-multiple-location...not testing20:45
flaper87markwash: the ehterpad looks good, great work.20:45
markwashI'm going to start working through the specific proposals at the bottom20:45
markwashand its least invasive first, so I think folks should have a lot of time to respond and redirect the work as we go20:46
flaper87markwash: about #120:46
markwashwe have *something* like that now, but it might only be in ./run_tests.sh20:47
flaper87markwash: we were just discussing about how to separate / organize tests in Marconi earlier today. There's a pattern I've seen / used in the past that might work for glance as well. (by pattern I mean modules structure)20:47
markwashoh cool20:47
markwashI think it would be fantastic if most os projects could adopt similar (but good) conventions for where tests live20:47
flaper87Inside glance.test we should have the base clases that will be imported / used by the actual tests and the tests should live outside the glance/ package20:48
flaper87lemme at that to your pad20:48
markwashcool20:49
markwashI think that about covers testing for now20:49
markwashother open topics? iccha?20:49
icchathanks markwash will look at etherpad20:49
icchaya markwash , so i noticed https://blueprints.launchpad.net/glance/+spec/remove-sensitive-data-from-locations20:50
icchashould be looking more closely at this is we are inching towards public glance?20:50
flaper87iccha: ++ for resurecting that20:50
markwashiccha: funny you should mention that. . I saw that recently and realized I had completely forgot about it20:50
markwashiccha: +1 yes20:50
icchahehe yeah sorry i jumped in in last min on meeting, turns out my flight was cancelled and i could join meeting afterall :p20:51
zhiyanshould we use metadata_encryption ?20:51
icchamarkwash: so do we target that for havana20:51
markwashiccha yeah, if somebody wants to work on it20:51
icchadid anyone do any ground work on it or have any ideas? if yes the whiteboard is a great place20:51
flaper87I'd like to see that happen in Havanna20:51
flaper87Havana20:51
markwashiccha: I'm a bit hesitant to myself, only because I don't have a big ready deployment at my fingertips to help me figure out all the possible gotchas20:51
icchamarkwash: i think we would be interested20:52
markwashas far as I can tell, the thought was "just remove it", but do something like moving the related per store/container/etc authn creds to config20:52
markwashso you might have a glance.store.swift.user_id config setting20:53
markwashor maybe even a mapping of container -> user_id / password (again still thinking of swift)20:53
icchafor each user?20:53
zhiyancan we extract those sensitive data from location string, and encrypt them by metadata_encryption and save them to location's metadata (https://blueprints.launchpad.net/glance/+spec/direct-url-meta-data) ?20:53
markwashnot quite, I think the users would share the same ones20:54
markwashzhiyan: I think the hope is to get rid of the need for metadata encryption20:54
markwashzhiyan: basically, we would remove sensitive stuff completely from glance's database20:54
flaper87iccha: what about writing ideas on ehterpad? I'm interested in that as well20:54
markwashyeah, we should etherpad that out20:54
iccha+1 flaper8720:54
markwashinstead of me yammering unintelligibly :-)20:54
zhiyanok, +120:55
* flaper87 is with technology as his sister is with shoes. He's always interested20:55
icchahttps://etherpad.openstack.org/remove-sensitive-location-info-glance20:55
flaper87iccha: +120:55
icchaits blank for now cause i removed all the sensitive info from etherpad :p20:55
markwashokay cool, anything else for the last 5 minutes? or extra free time for all?20:55
markwashwe don't even have to tell our bosses20:56
flaper87cool, I can help with that blueprint!20:56
flaper87not from me20:56
zhiyannot from me now :)20:56
icchanothing else here :)20:56
markwash#endmeeting20:56
*** openstack changes topic to "OpenStack meetings (alternate)"20:56
openstackMeeting ended Thu Jun 13 20:56:49 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-06-13-20.04.html20:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-06-13-20.04.txt20:56
markwashthanks everybody20:56
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-06-13-20.04.log.html20:56
zhiyanoh, btw, can we confirm next meeting time ?20:57
nikhilprolly should ask that in openstack-glance20:57
*** flaper87 has left #openstack-meeting-alt20:58
*** pcm___ has joined #openstack-meeting-alt20:58
*** bdpayne has quit IRC20:59
*** pcm__ has joined #openstack-meeting-alt20:59
*** bdpayne has joined #openstack-meeting-alt21:00
*** jcru is now known as jcru|away21:02
*** hartsocks has joined #openstack-meeting-alt21:02
*** kgriffs has left #openstack-meeting-alt21:02
*** jcru|away is now known as jcru21:05
*** markmcclain has quit IRC21:11
*** dhellmann has quit IRC21:12
*** djohnstone has left #openstack-meeting-alt21:13
*** zhiyan has quit IRC21:14
*** markmcclain has joined #openstack-meeting-alt21:18
*** esheffield has quit IRC21:24
*** hartsocks has quit IRC21:24
*** jspeidel has quit IRC21:29
*** markwash has quit IRC21:29
*** djohnstone has joined #openstack-meeting-alt21:33
*** jspeidel has joined #openstack-meeting-alt21:36
*** jspeidel has quit IRC21:37
*** markmcclain has quit IRC21:38
*** mtreinish has quit IRC21:45
*** dhellmann has joined #openstack-meeting-alt21:53
*** rnirmal has quit IRC22:03
*** pcm__ has quit IRC22:04
*** djohnstone has quit IRC22:05
*** dhellmann has quit IRC22:08
*** oz_akan has quit IRC22:09
*** jmaron has quit IRC22:09
*** jmaron has joined #openstack-meeting-alt22:10
*** lastidiot has quit IRC22:13
*** amytron has quit IRC22:17
*** dhellmann has joined #openstack-meeting-alt22:18
*** dhellmann has quit IRC22:19
*** jmaron has quit IRC22:22
*** jcru is now known as jcru|away22:22
*** markwash has joined #openstack-meeting-alt22:23
*** jcru|away is now known as jcru22:24
*** jcru has quit IRC22:25
*** jmaron has joined #openstack-meeting-alt22:25
*** yidclare has quit IRC22:28
*** imsplitbit has joined #openstack-meeting-alt22:29
*** Riddhi has quit IRC22:34
*** jspeidel has joined #openstack-meeting-alt22:45
*** jergerber has quit IRC23:10
*** jergerber has joined #openstack-meeting-alt23:13
*** kevinconway has left #openstack-meeting-alt23:14
*** bdpayne has quit IRC23:23
*** jmaron has quit IRC23:24
*** hartsocks has joined #openstack-meeting-alt23:31

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