Thursday, 2013-05-23

*** amyt has joined #openstack-meeting-alt00:05
*** yidclare has quit IRC01:02
*** esp1 has joined #openstack-meeting-alt01:34
*** zzs has quit IRC01:38
*** grapex has joined #openstack-meeting-alt02:01
*** amyt has quit IRC02:04
*** saurabhs has quit IRC02:19
*** markwash has joined #openstack-meeting-alt02:20
*** grapex has quit IRC02:52
*** esp1 has left #openstack-meeting-alt03:08
*** bdpayne has joined #openstack-meeting-alt03:27
*** bdpayne_ has joined #openstack-meeting-alt03:29
*** bdpayne has quit IRC03:31
*** jrodom has quit IRC03:49
*** grapex has joined #openstack-meeting-alt03:52
*** wolfdreamer has joined #openstack-meeting-alt03:58
*** wolfdreamer has quit IRC04:00
*** wolfdreamer has joined #openstack-meeting-alt04:01
*** grapex has quit IRC04:02
*** SergeyLukjanov has joined #openstack-meeting-alt04:12
*** wolfdrea_ has joined #openstack-meeting-alt04:16
*** wolfdreamer has quit IRC04:20
*** wolfdrea_ has quit IRC04:20
*** grapex has joined #openstack-meeting-alt05:16
*** bdpayne_ has quit IRC05:17
*** grapex has quit IRC05:20
*** bdpayne has joined #openstack-meeting-alt05:31
*** bdpayne_ has joined #openstack-meeting-alt05:34
*** bdpayne has quit IRC05:36
*** grapex has joined #openstack-meeting-alt06:16
*** bdpayne_ has quit IRC06:20
*** grapex has quit IRC06:21
*** kagan has joined #openstack-meeting-alt06:34
*** SergeyLukjanov has quit IRC06:56
*** SergeyLukjanov has joined #openstack-meeting-alt07:00
*** SergeyLukjanov has quit IRC07:02
*** johnthetubaguy has joined #openstack-meeting-alt08:06
*** SergeyLukjanov has joined #openstack-meeting-alt08:07
*** dmitryme has joined #openstack-meeting-alt08:21
*** dmitryme has quit IRC08:22
*** dmitryme has joined #openstack-meeting-alt08:23
*** kagan has quit IRC08:48
*** qwerty_nor has joined #openstack-meeting-alt08:54
*** grapex has joined #openstack-meeting-alt09:17
*** dmitryme has quit IRC09:20
*** grapex has quit IRC09:22
*** qwerty_nor has quit IRC09:27
*** SergeyLukjanov has quit IRC09:50
*** dmitryme has joined #openstack-meeting-alt09:51
*** nimi has left #openstack-meeting-alt10:05
*** SergeyLukjanov has joined #openstack-meeting-alt10:08
*** SergeyLukjanov has quit IRC10:25
*** SergeyLukjanov has joined #openstack-meeting-alt10:25
*** SergeyLukjanov has quit IRC10:25
*** qwerty_nor has joined #openstack-meeting-alt10:51
*** grapex has joined #openstack-meeting-alt11:17
*** grapex has quit IRC11:22
*** dmitryme has quit IRC12:14
*** dhellmann-away is now known as dhellmann12:21
*** dmitryme has joined #openstack-meeting-alt12:38
*** dhellmann is now known as dhellmann-away13:04
*** grapex has joined #openstack-meeting-alt13:18
*** grapex has quit IRC13:22
*** qwerty_nor has quit IRC13:32
*** dmitryme has quit IRC13:40
*** hartsocks has joined #openstack-meeting-alt13:41
*** hartsocks has left #openstack-meeting-alt13:42
*** dhellmann-away is now known as dhellmann13:50
*** djohnstone has joined #openstack-meeting-alt14:10
*** qwerty_nor has joined #openstack-meeting-alt14:10
*** amyt has joined #openstack-meeting-alt14:22
*** amyt has quit IRC14:22
*** amyt has joined #openstack-meeting-alt14:23
*** dmitryme has joined #openstack-meeting-alt14:26
*** djohnstone has quit IRC14:28
*** tanisdl has joined #openstack-meeting-alt14:28
*** djohnstone has joined #openstack-meeting-alt14:30
*** djohnstone1 has joined #openstack-meeting-alt14:41
*** djohnstone has quit IRC14:44
*** yidclare has joined #openstack-meeting-alt14:57
*** cp16net|away is now known as cp16net15:00
*** grapex has joined #openstack-meeting-alt15:06
*** grapex has quit IRC15:10
*** grapex has joined #openstack-meeting-alt15:11
*** esp has joined #openstack-meeting-alt15:31
*** seanrob has joined #openstack-meeting-alt16:02
*** dmitryme has quit IRC16:03
*** cp16net is now known as cp16net|away16:12
*** yidclare has quit IRC16:15
*** esp has left #openstack-meeting-alt16:16
*** bdpayne has joined #openstack-meeting-alt16:18
*** cp16net|away is now known as cp16net16:22
*** seanrob has quit IRC16:25
*** wolfdreamer has joined #openstack-meeting-alt16:25
*** seanrob has joined #openstack-meeting-alt16:25
*** SergeyLukjanov has joined #openstack-meeting-alt16:26
*** seanrob has quit IRC16:46
*** dmitryme has joined #openstack-meeting-alt16:55
*** esp1 has joined #openstack-meeting-alt16:58
*** esp1 has left #openstack-meeting-alt16:58
*** SergeyLukjanov has quit IRC17:03
*** yidclare has joined #openstack-meeting-alt17:03
*** kagan has joined #openstack-meeting-alt17:09
*** tanisdl has quit IRC17:12
*** nikhil__ is now known as nikhil17:18
*** djohnstone1 is now known as djohnstone17:24
*** tanisdl has joined #openstack-meeting-alt17:36
*** johnthetubaguy has quit IRC17:40
*** grapex has quit IRC17:42
*** jmaron has joined #openstack-meeting-alt17:46
*** grapex has joined #openstack-meeting-alt17:46
*** SergeyLukjanov has joined #openstack-meeting-alt17:46
*** SergeyLukjanov has quit IRC17:51
*** SergeyLukjanov_ has joined #openstack-meeting-alt17:52
*** SergeyLukjanov_ has quit IRC17:52
*** jspeidel has joined #openstack-meeting-alt17:53
*** SergeyLukjanov_ has joined #openstack-meeting-alt17:55
*** SergeyLukjanov has joined #openstack-meeting-alt17:56
*** ruhe has joined #openstack-meeting-alt17:57
*** Nadya has joined #openstack-meeting-alt17:58
*** akuznetsov has joined #openstack-meeting-alt17:58
*** mattf has joined #openstack-meeting-alt18:01
*** IlyaE has joined #openstack-meeting-alt18:01
*** aignatov2 has joined #openstack-meeting-alt18:01
aignatov2Hi all!18:01
aignatov2Savanna meeting will start in a few minutes18:01
*** highlycaffeinate has joined #openstack-meeting-alt18:02
*** highlycaffeinate is now known as highlycaffeinatd18:02
*** dripton has joined #openstack-meeting-alt18:03
aignatov2#startmeeting18:03
openstackaignatov2: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'18:03
*** ErikB has joined #openstack-meeting-alt18:03
aignatov2#startmeeting Savanna18:04
openstackMeeting started Thu May 23 18:04:13 2013 UTC.  The chair is aignatov2. 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:04
*** dripton has left #openstack-meeting-alt18:04
SergeyLukjanovWe are working on extension and templates blueprints last week18:05
aignatov2This week we updated bluprints related for Pluggable Provisioning Mechanism18:05
aignatov2Now they have more details18:06
aignatov2Nadya can you post links to this documents?18:06
Nadyayes, sure https://wiki.openstack.org/wiki/Savanna/PluggableProvisioning18:07
Nadya#link https://wiki.openstack.org/wiki/Savanna/PluggableProvisioning18:08
Nadyaand the second updated wiki page is about Templates #link https://wiki.openstack.org/wiki/Savanna/Templates18:10
aignatov2#link https://wiki.openstack.org/wiki/Savanna/Templates18:10
jmaronI just posted some thoughts about templates to the savanna-all list18:10
jmaronI'd welcome comments/thoughts18:12
aignatov2we are looking through it18:12
jmaronthanks!18:13
aignatov2besides your mail Jon, I'd like to notice another items.18:17
akuznetsovsuch parameters can be place at cluster config, not at a node group config18:18
aignatov2We are mostly finished with instructions for diskimage-builder to construct images with Apache Hadoop inside18:18
aignatov2It will support both Ubuntu and CentOS distros18:18
akuznetsovpossibly we should add for cluster config a nested layout18:18
akuznetsovfor example HDFS18:18
akuznetsovit should contain parameters applicable for all nodes in clusters18:19
akuznetsove.g. replication factor18:19
ErikBIn Jon's example on checkpoint.period, are you saying that this should be in the cluster config?18:20
jmaronI'm not sure what you mean.  service configuration properties can be defined at both the cluster level as well as the node group level18:21
jmaronso any 'GENERAL" or service specific property can be specified at both cluster and node level18:21
akuznetsovfor examples mapred child heap size is only applicable to the node group18:22
mattfaignatov2, when you have something even mostly working re diskimage-builder, fire it my way. i'll take it for a test drive through RDO. fyi, i still think you should check the recipe into the savanna.git repo.18:22
jmaronit can be specified globally at the cluster, but overridden at the node level if desired18:22
jmaronif specified at the cluster, it's essentailly a global default18:22
aignatov2mattf, we just have some troubles with DIB and not well tested it18:24
aignatov2sometimes clusters are not working with it :)18:24
aignatov2mostly it is the same DIB elements which I sent you last week)18:25
ruhemattf, we're going to create a new repo in stackforge for all the tools we build for Savanna18:25
mattfif they aren't working in that the instance doesn't get a vm priv ip, i found a fix for that. i needed it to get ubuntu instances running on rdo.18:25
mattfruhe, what's the hesitation for including the image creation in the savanna repo?18:26
jmaronin our view the user would have a cluster configuration panel and a node group configuration panel.  In both instances the same properties can be specified.  they'll end up in a cluster or node group template.  In both cases, they'd be associated to a "GENERAL" groping or a service grouping18:27
ruhemattf, we would like keep current repo only for savanna core. savanna-python-client, savanna-horizon-plugin will be separate projects. that's how all the OS projects manage additional components18:27
aignatov2mattf, I think these scripts are the separate project like savanna-pythonclient, savanna-horizon etc18:27
SergeyLukjanovruhe +118:28
mattfcurrently there's a tight coupling between what the image and savanna-api. until there's a cleaner separation, it seems wise to keep the two together. the hope is they'll more easily be kept in sync.18:29
akuznetsovbut node group can override parameters like replication factor18:29
akuznetsovin you case18:30
mattftake for instance the default root password. if it's changed in the image builder it must also be changed in savanna-api. best to do it as a unit in one repo.18:30
aignatov2in the future we may have more scripts and instructions, elements and so forth, and savanna repo is an independent project with it's integration tests, for instance18:30
dmitrymeJon, in your model user can redefine a property like HDFS replication factor in Node Group18:30
ruhemattf, we're definitely going to decouple these things in ongoing implementation of plugins18:30
aignatov2mattf, root password is a temporary solution, we plan to reset it after deployment for security reasons18:31
jmaronakuznetsov:  yes.  do you object to that capability?18:31
aignatov2in the duture releases18:31
dmitrymethis looks like a way to shoot in ones foot18:31
aignatov2*future18:31
jmaronOt18:31
akuznetsovyes because the replication factor is cluster parameter18:31
jmaronok.  I suppose we could add the scope parameter for such properties18:32
mattfroot pw is just a specific example. w/o defined expectations between savanna-api <-> instance, we risk the two getting out of sync if they live apart.18:32
ruhemattf, there is already set of integration tests we run on each commit. we'll know that something is wrong instantly :)18:33
mattfso i propose keeping them together, until the time there's a well defined interface, or they're entirely stable.18:33
ErikBakuznetsov - do you see the issue that was brought up by Jon on the property collision that is possible in the current proposal?18:33
mattfruhe, do those integration tests build a new image for testing w/ or use a stock image?18:34
dmitrymeErik, sure we see it18:34
jmaronthat was just one example.  there are others as well.  we believe the correct grouping is at a service level18:34
akuznetsovyes we see it18:34
dmitrymeactually we were thinking to avoid it in the following way:18:34
dmitrymewhen plugin specifies config applicable_target="service:hdfs", we demonstrate it in the UI once in Node Group18:35
jmaronto be clear: properties are defined as associated to services or general, scoped to node or cluster18:35
jmaronit would also have to be presented only once at the cluster level, if applicable18:36
dmitrymei.e. the do not going to provide user a way to specify it twice in a single Node Group18:36
dmitrymeJon, yep, for cluster as well18:37
ruhemattf, currently we don't build images for each commit. but i think that in a couple of weeks we'll have image-builder decoupled from any hard-code18:38
jmaronthat would fix that issue, but I'm wondering about the templates:  would properties still be grouped by component?18:38
Nadyacomponent = process?18:40
dmitrymeJon, component is "task tracker", "datanode", right?18:40
jmaronyes18:40
dmitrymeaha, I see18:40
mattfruhe, how would you do an integration test that involves image creation if the integration test is for savanna-api (lives w/ savanna-api repo) and the image creation lives in a separate repo?18:40
dmitrymeJon, we want some properties to be grouped by process (like processes heap sizes) and some - by service (like fs.checkpoint.dir)18:43
jmaronthe problem is that we actually don't even have that information in most instances.  Hadoop configuration is essentially service based, so there is actually no documentation about the component/process association.  we've spoken to internal developers, and the indication is that that would be a fairly significant documentation effort that isn't planned currently18:45
jmaronso there are two fundamental problems:  1.  grouping by component isn't generally done by hadoop and 2.  the information isn't even available18:46
jmaronbut as UI developers, given the information associated with the config object, you can make some design decisions (pagination, filtering, etc) to make a usable interface.  Trying to make the hadoop model align with the UI requirements is not the way to do that, IMHO18:47
ruhemattf, that's a good question. i think we should have a pool of images. i understand your point, but we really want to keep savanna similar to other OS projects. for instance, every project has python client which is kept separate from the main code. and at the same time python client can be used internally to handle requests from Horizon UI18:50
mattfruhe, python client makes sense. it forces you to have a stable API for each project/repo. i think it's premature to say the image & savanna-api is stable enough to live apart. it's also not entirely clear to me that there's major motivation to stabilize that interface right now.18:51
mattfconsider keeping them together for now. in any event, i'm keen to try it out asap. i've the email instructions to work from atm, would love a repo to work with too -- i'm guessing there will be rdo specific changes i'll have to make.18:53
ruhemattf, sure. we'll try to get that repo asap18:54
NadyaJon, an example.  we have 2 mashines: big and small. We run a service mapred. So it appears 2 process tt on 1st and on 2nd. It have different amount of tasks to which may be processed18:56
Nadyaso we need to configure that on 1st machine we may run 10 tasks and on second - 5. But it is the one service18:57
Nadya*map tasks18:58
jmaronI'm not sure you can even do that based on the selection of one flavor per node group.  How do you propose to have different machine sizes as part of the same node group?18:58
jmaronso in this case, you'd define a big machine group of one, a small machine group of one, and configure the service parameters for each accordingly18:59
Nadyaservice may be ran on 2 machines which belong to different node groups18:59
*** kgriffs has joined #openstack-meeting-alt19:00
*** malini has joined #openstack-meeting-alt19:00
kgriffshey folks19:01
aignatov2guys, we are out of time19:01
jmaronin that case you can specify cluster level parameters for the service as default values, and then node group overrides per node19:01
jmaronnode group19:01
aignatov2#endmeeting savanna19:01
*** openstack changes topic to "OpenStack meetings (alternate)"19:01
openstackMeeting ended Thu May 23 19:01:21 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:01
*** oz_akan has joined #openstack-meeting-alt19:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-05-23-18.04.html19:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-05-23-18.04.txt19:01
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-05-23-18.04.log.html19:01
*** jspeidel has left #openstack-meeting-alt19:01
dmitrymeguys lets move our conversation into #savanna channel19:01
*** Nadya has quit IRC19:02
*** aignatov2 has left #openstack-meeting-alt19:03
*** bryansd has joined #openstack-meeting-alt19:03
kgriffsso, just waiting a minute to see if flaper87 is going to make it19:04
maliniok19:04
*** jmaron has left #openstack-meeting-alt19:05
*** Nadya has joined #openstack-meeting-alt19:05
*** Nadya has left #openstack-meeting-alt19:08
oz_akanhi19:09
kgriffsyo19:09
oz_akan:)19:09
kgriffsjust waiting for a couple folks19:09
kgriffsgive it one more minute19:09
*** wirehead_ has joined #openstack-meeting-alt19:10
kgriffshttps://wiki.openstack.org/wiki/Meetings/Marconi#Agenda19:10
kgriffs#startmeeting marconi19:10
openstackMeeting started Thu May 23 19:10:44 2013 UTC.  The chair is kgriffs. Information about MeetBot at http://wiki.debian.org/MeetBot.19:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:10
*** openstack changes topic to " (Meeting topic: marconi)"19:10
openstackThe meeting name has been set to 'marconi'19:10
kgriffs#topic bugs19:10
*** openstack changes topic to "bugs (Meeting topic: marconi)"19:10
kgriffs#link https://bugs.launchpad.net/marconi19:11
kgriffsso, Flavio and I have started chipping away at some of these19:11
kgriffsmalini: anything in this list you would like to highlight?19:11
kgriffsI was thinking we could just prioritize the undecided real quick19:12
kgriffsso, sorting by number ,descending19:13
kgriffsrandom 404's - would you say that's high or critical?19:13
malinihigh as in - when will it be fixed?19:14
kgriffsI'd say, how important it is to get this done for a "beta" release19:14
maliniIt is important to get this one fixed19:14
kgriffsseems like this one is a blocker for load testing19:15
maliniThe 404s spike up when the number of users is large19:15
maliniyes19:15
maliniI have been able to repro thos only with tsung19:15
kgriffsok, but it isn't like a hole in our feature implementation, like some of the others19:15
kgriffshow about "high" for priority?19:16
maliniworks for me19:16
kgriffsnext19:16
kgriffshttps://bugs.launchpad.net/marconi/+bug/117797919:16
kgriffs#link https://bugs.launchpad.net/marconi/+bug/117797919:16
kgriffsI think medium is OK here19:17
maliniyeap19:17
*** seanrob has joined #openstack-meeting-alt19:17
* kgriffs does that19:17
kgriffs#link https://bugs.launchpad.net/marconi/+bug/117797619:17
kgriffssame here, methinks19:17
kgriffsditto for the next19:18
malinitht got me thinking- so max msg size per request will be 4kb 8 50 ?19:18
kgriffs#link https://bugs.launchpad.net/marconi/+bug/117797119:18
malini** 4kb * 50 ?19:18
*** mattf has left #openstack-meeting-alt19:18
kgriffsmax request body, you mean?19:18
maliniyes..19:18
maliniguess it'll have to be19:18
kgriffsthat's right, plus a little overhead19:18
maliniok19:18
kgriffsfor 2000 simultaneous requests, that comes out to be around 400 MB19:19
maliniok19:19
*** ruhe has left #openstack-meeting-alt19:20
kgriffsif we up that limit, to 64K then we definitely need to support streaming deserialization of the JSON (right now everything is buffered since we just use json.read)19:20
*** qwerty_nor has quit IRC19:20
kgriffs(BTW)19:20
kgriffs#link https://bugs.launchpad.net/marconi/+bug/117795219:21
kgriffsmedium on that as well19:21
maliniyeap19:21
kgriffsalthough some of these things have security consequences.19:21
kgriffsI'm not saying we don't need to get them done for the gold release, just trying to see where to focus for a beta19:21
kgriffsOK, so I'll set input validation bugs to medium19:22
malininone of these are show stoppers19:22
kgriffsOh, here's one19:22
kgriffshttps://bugs.launchpad.net/marconi/+bug/116510219:22
malinitht one could be a high19:23
kgriffswe better get that done for beta since it's spec'd in the API19:23
maliniagreed19:23
kgriffsis there a blueprint for modifying the syntax to using query param instead?19:23
* kgriffs looking19:23
kgriffsI guess that just falls under v1-api19:24
kgriffsso, anyone have an objection to changing this:19:24
malininot me19:25
kgriffscool19:25
kgriffsso it would look something like:19:25
kgriffsmyqueue/messages?ids=[95109,142358,1243098]19:26
kgriffsis OK?19:26
maliniare we also going to change how the location is returned when we post multiple messages?19:27
kgriffsyes19:27
malinicool19:27
kgriffsit would have to follow suit19:27
*** highlycaffeinatd has left #openstack-meeting-alt19:27
kgriffs#agreed change get list of specific messages URL to put IDs in a query string param, vs. as the resource name in the path19:28
kgriffsOK, all set with bugs?19:28
kgriffs#link https://bugs.launchpad.net/marconi19:28
maliniyes19:28
kgriffs#topic QA cluster19:29
*** openstack changes topic to "QA cluster (Meeting topic: marconi)"19:29
kgriffsoz_akan: I can haz updatez?19:29
oz_akansure19:29
*** SergeyLukjanov has quit IRC19:30
oz_akannew test environment is almost ready, except marconi configuration which we will do after the meeting with Malini19:30
kgriffsOK19:30
kgriffsexcellent19:30
kgriffsone thought19:30
oz_akanso we have web and mongodb configuration under Salt and I will soon create a git repo for that19:30
kgriffsOK19:30
kgriffswhere will that repo live?19:30
oz_akanI am working on documenting it19:30
oz_akanthat is a question, I would ask to you19:30
kgriffsmordred: ping19:31
kgriffsmordred: ^^^19:31
kgriffsI'm not sure. I think of it as a reference for deploying, but other people might want to do it in chef or puppet19:32
*** vkmc_ has joined #openstack-meeting-alt19:32
kgriffshey vkmc_19:33
oz_akansure, salt is in python so I think it will be adapted by openstack sooner or later19:33
kgriffsoz_akan - maybe ask in #openstack-infra ?19:33
vkmc_hey kgriffs!19:33
oz_akanI think infrastructure people are even open to port all puppet to salt19:33
oz_akanyes I asked yesterrday19:33
malinithere is a ci-salt repo in stackforge..But hasnt been updated in a while19:33
kgriffsoic19:33
kgriffsi mean, you can ask whether this repo should live under stackforge or just under rackspace org or something19:34
kgriffswow, I didn't realize salt was taking over the world. :D19:35
kgriffshey, if that happens, you can contribute to updating etherpad.openstack.org19:35
kgriffs(nudge nudge, wink wink)19:35
*** seanrob has quit IRC19:35
kgriffsok, so that's great you've made so much progress19:35
kgriffsI can't wait to have a real cluster to hammer. :D19:36
*** seanrob has joined #openstack-meeting-alt19:36
kgriffsat that point, we should also give out the info to the community so they can try it out, write non-python client libs, etc.19:36
*** ErikB has quit IRC19:37
oz_akanyes19:37
kgriffs#oz_akan to send out a not to dev list inviting people to pummel our QA/reference deployment19:37
kgriffslet me try that again19:37
*** ErikB has joined #openstack-meeting-alt19:37
kgriffs to send out a not to dev list inviting people to pummel our QA/reference deployment19:37
oz_akanI am working on a document about it19:37
kgriffscrap19:37
kgriffs#action oz_akan to send out a not to dev list inviting people to pummel our QA/reference deployment19:37
kgriffsoz_akan: perfect.19:37
kgriffsok19:38
kgriffsone more thing I thought of earlier today19:38
kgriffsit would be great to have hardening in there already if not done already19:38
oz_akannot done yet19:39
kgriffscould be a subsequent release of the salt states19:39
oz_akanit is more like having the service up19:39
oz_akansure19:39
oz_akanthat is the point19:39
kgriffssounds like a plan19:39
kgriffscan you also add HAVAGE to that19:40
kgriffs?19:40
oz_akanwhat is HAVAGE?19:40
kgriffshttp://www.issihosts.com/haveged/19:40
*** wirehead_ has left #openstack-meeting-alt19:40
*** seanrob has quit IRC19:40
kgriffsvirtualized guests generally have poor entropy19:41
kgriffsso they need a little help19:41
oz_akanok you need this package to be installed?19:41
* kgriffs trying to get used to using the meetbot commands19:41
kgriffs#link http://www.issihosts.com/haveged/19:41
kgriffscorrect19:41
*** IlyaE has quit IRC19:41
kgriffsI think it can contribute entropy to /dev/urandom - not sure if that happens by default19:42
mordredkgriffs: pong19:44
kgriffsmordred: hey, oz_akan was wondering where his salt scripts for Marconi should live. I'll let him explain. :)19:44
mordredah - gotcha19:44
mordredI think at the moment they would make sense to put into a stackforge project19:45
oz_akan"marconi-salt" would be a good repo name19:45
oz_akanor we could have it as a folder under marconi19:46
oz_akanbut that might slow down things19:46
*** IlyaE has joined #openstack-meeting-alt19:47
kgriffsif it goes in stackforge does it get wired up to gerrit & friends?19:48
*** seanrob has joined #openstack-meeting-alt19:48
*** tanisdl has quit IRC19:50
kgriffsoz_akan: can you follow up with mordred?19:50
kgriffs(we need to move on)19:50
kgriffs#action oz_akan to find a home for marconi-salt19:50
oz_akankgriffs: ok19:50
kgriffsone more thing on the topic of security. Do you have some hardening guides handy?19:51
kgriffsI've referenced NSA before, but didn't see RHEL 6 yet.19:51
kgriffs#link http://www.issihosts.com/haveged/19:51
oz_akanguess, pasted wrong link19:52
kgriffssorry19:52
kgriffswrong link19:52
kgriffs#link http://serverfault.com/questions/368055/anything-close-to-an-nsa-guide-for-securing-rhel-619:52
*** IlyaE has quit IRC19:52
*** tanisdl has joined #openstack-meeting-alt19:53
kgriffsanyway, something to keep on your radar19:53
kgriffsmoving right along...19:53
oz_akankgriffs: this is kind of at the very end of my todo list, next I want to create Malini's benchmarking environment19:53
oz_akanok got that19:53
kgriffsmakes sense19:53
kgriffslooking at the agenda, we'll skip down to polling modes, since the others I'd like to get flaper87's thoughts on and he couldn't make it19:55
kgriffs#topic •BP: https://blueprints.launchpad.net/python-marconiclient/+spec/polling-modes in the client19:55
*** openstack changes topic to "•BP: https://blueprints.launchpad.net/python-marconiclient/+spec/polling-modes in the client (Meeting topic: marconi)"19:55
kgriffs#link https://blueprints.launchpad.net/python-marconiclient/+spec/polling-modes19:55
kgriffsvkmc_: thoughts?19:55
kgriffsI guess this is assuming there is a blocking/greenlet-aware polling loop19:56
* kgriffs watches a tumbleweed roll by19:57
vkmc_kgriffs, not much I can suggest now, I'm from my phone just to keep up with the meeting :)19:59
*** esheffield has joined #openstack-meeting-alt19:59
kgriffsno worries19:59
kgriffsjust mostly wanted to raise awareness of that, since it is something we want to promote19:59
kgriffsOK, we are out of time folks20:00
kgriffsparting thoughts?20:00
malini bye bye :)20:00
kgriffsok, thanks everyone20:00
*** ashwini has joined #openstack-meeting-alt20:00
kgriffsnext week, same bat-time, same bat-channel.20:00
kgriffs#endmeeting20:00
*** openstack changes topic to "OpenStack meetings (alternate)"20:01
openstackMeeting ended Thu May 23 20:00:59 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-05-23-19.10.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-05-23-19.10.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/marconi/2013/marconi.2013-05-23-19.10.log.html20:01
vkmc_kgriffs, I'll make some progress on that this afternoon20:01
kgriffscool, thx20:01
kgriffsvkmc_: what timezone are you in?20:01
vkmc_Cheers20:01
*** jbresnah has joined #openstack-meeting-alt20:02
markwashglance folks around?20:02
* jbresnah is20:02
rosmaitayo!20:02
esheffield'sup20:02
icchahola20:02
ashwinihi20:02
markwash#startmeeting glance20:02
openstackMeeting started Thu May 23 20:02:43 2013 UTC.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.20:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:02
*** openstack changes topic to " (Meeting topic: glance)"20:02
openstackThe meeting name has been set to 'glance'20:02
*** tanisdl has quit IRC20:02
markwashAgenda for today20:03
markwash#link https://wiki.openstack.org/wiki/Meetings/Glance20:03
markwash#topic new blueprints20:03
*** openstack changes topic to "new blueprints (Meeting topic: glance)"20:03
*** tanisdl has joined #openstack-meeting-alt20:04
markwashfirst thing I wanted to mention is a sheepdog store20:04
markwashI don't know if folks are familiar, but sheepdog is a block/object store, some folks want to use for storing images20:04
markwashI was looking around for a blueprint we could approve, but couldn't find one20:04
markwashhere is the code so far https://review.openstack.org/#/c/29961/20:05
*** cp16net is now known as cp16net|away20:05
ameadei'm here now20:05
markwashworth a look20:05
markwashmaybe we should ask Liu to make a bp, or maybe its not a big deal20:05
icchaits good to have ppl interested in contributing and writing code for new stores, but +1 on bp required20:05
markwashanybody see any reason not to add a sheepdog store? the code in the review looks like it is progressing nicely20:05
ameadei'm cool with it, don't even care if there is a bp20:06
markwashone thing I keep thinking about is20:06
markwashin the long run, should we offer better support for drivers living outside of the code base?20:06
westmaasyes20:07
jbresnahit seems good to me20:07
ameademarkwash: ideally20:07
esheffieldI was about to say something along those lines20:07
jbresnahone thing tho...20:07
markwashthese backends we're getting are great, but glance core doesn't necessarily have the resources to test them20:07
jbresnahthere is always the debate about having plugins part of the distro or not20:07
jbresnahlike, it gets contributed and then the expertise goes away20:07
jbresnahand maintaining it is hard20:07
jbresnahprobably good to have an easy path to include your backend store without it being part of glance proper.20:08
esheffieldmaybe openstack needs a "user contrib" area for collecting things like this for people to find, but aren't part of the official distro20:08
jbresnahyeah something like that would be good20:08
markwashI think we maybe could have Glance provide a testing framework for what-have-you backends20:08
ameadewhat are the exact benefits and is it worth our time?20:09
*** malini is now known as malini_away20:09
markwashso this might be a concern folks should start to chatter about20:09
jbresnahthat would be good.  to vet a driver20:09
markwashI don't see it in our really near-term future20:09
jbresnahnod20:09
markwashcool, I've already asked for a blueprint for sheepdog, and I'll mark it approved when I see one (as long as its not somehow crazy)20:10
markwashnext item. . .20:10
markwashhttps://blueprints.launchpad.net/glance/+spec/image-error-state-management20:11
markwasherror state management20:11
markwashthis one was recently added by our good friend ameade20:11
*** grapex has left #openstack-meeting-alt20:11
markwashand triggered some interest from folks who are tired of being confused when their snapshot fails20:11
markwashnot trying to dig into the details, here, yet20:12
markwashbut I think it might make sense for more folks to take a look offline20:12
markwashI'm inclined to accept things we can to improve the experience with failed uploads, while maintaining backwards compatibility20:12
markwashone more pair of items for new blueprints20:13
nikhilmarkwash: a comment on your reply to the bp ..20:13
markwashnikhil: go for it20:13
nikhilcan we just check the checksum?20:13
nikhilno?20:13
markwashmaybe in some cases, however, I think sometimes the image gets deleted immediately on a failure20:14
markwashso there wouldn't be anything to check20:14
nikhilmigth be easier in case of copy_from (raw data) might get complicate20:14
nikhild in case of import on that (just completing thought)20:14
nikhilmarkwash: ah k20:14
markwashsure. . I think there's some possible synergy with the import export blueprints, which are next20:15
markwash#link https://blueprints.launchpad.net/glance/+spec/new-download-workflow20:15
markwash#link https://blueprints.launchpad.net/glance/+spec/new-upload-workflow20:15
ameademarkwash: really in this bp I care about the use cases and not the proposed solution20:15
ameadedoes it make sense to change the bp to not propose a solution?20:16
ameadeor does that make it a really fancy bug?20:16
nikhiltricky20:16
markwashameade, might be a good idea, but I'm not worried20:16
*** IlyaE has joined #openstack-meeting-alt20:17
markwashrosmaita sent out an email about the upload and download workflows (some might say import and export)20:17
ameadei'm assuming we will touch on when we want to solve this in the upload/download discussion?20:17
*** vkmc_ has quit IRC20:17
markwash#link http://lists.openstack.org/pipermail/openstack-dev/2013-May/009385.html20:17
markwashameade: its possible we can help out with the solution separately from upload/download changes20:18
markwashI guess its kind of up to whoever writes the code and reviewers :-)20:18
ameademarkwash: that's true lol20:18
markwashI just want to make sure we preserve backwards compat :-)20:18
nikhilmarkwash: well, i was under the impression both were diff (where import was upload+convert)20:18
markwashnikhil: I was under the same impression, but I think if you read into the specs its clear that import/export are whats being discussed20:19
markwashnikhil: but I wouldn't be terribly surprised if I was wrong about that and missed something :-D20:19
nikhil:)20:19
rosmaitawhich specs are you talking about?20:19
rosmaitaup/down?20:19
markwashyup20:19
nikhilanything works, as long as we've some concensus on how we'r handling the image standards20:20
nikhili mean vhd qcow2 etc20:20
rosmaitathey don't require conversion, but they leave open an easy way to include that20:20
rosmaitafor import, as part of the "verification" step20:20
rosmaitafor export, whatever we want to call the "scrubbing"20:20
markwashoh, yes20:21
markwashsorry20:21
markwashokay, maybe I'm on the same page as rosmaita, and not nikhil20:21
*** cp16net|away is now known as cp16net20:21
markwashand was just confused a moment ago20:21
rosmaitanp, not sure how clear that was in the spec20:21
markwashimport -> bits & metadata can change20:21
*** IlyaE has quit IRC20:21
icchaso our plan is to let the idea soak in and see what else ppl have to say in mailing list?20:21
markwashfor whatever purpose (verification, conversion, something else)20:21
markwashwell, for me, I love these spec20:22
markwashspecs20:22
markwashand I think it makes sense to start breaking ground20:22
markwashI am interested to take a poll here in this meeting to see if folks have concerns about the specs, or if they want more time to consider things20:22
*** akuznetsov has quit IRC20:23
rosmaitai have one more ... the image cloning one20:23
rosmaitanot complete though, but i use the "image-action" resource20:23
jbresnahI am good with those specs, but so much of it depends on async workers (in my mind) and that does not yet seem worked out20:24
markwashrosmaita: I was wondering, do we get cloning for free with image import?20:24
nikhil(has anyone got a chance to look at the etherpad for asycn workers?)20:24
nikhilpls ignore if this is not the topic of discussion20:24
rosmaitanot for free, i don't think20:24
markwashrosmaita: if we define glance in another region as the source of the import20:24
markwashperhaps I was wrong20:25
rosmaitamarkwash: i hav eto think, i think it requires more glance-to-glance coordination20:25
markwashnikhil: you and jbresnah bring up a good point. it seems like the first step here is still async workers20:25
nikhilmarkwash: we'r just worried about the grusome implementation details for cloning being incorporated as copy_from20:25
markwashnikhil: that's a good concern to have20:26
nikhil:)20:26
markwashnikhil: I think we're free to redefine how copy_from looks in the api for v2 (since it does not exist there yet TMK)20:26
nikhilsounds good20:26
nikhilso do you wanna start with that or from workers for that specifically?20:27
*** IlyaE has joined #openstack-meeting-alt20:27
markwashwell, it sounds like we don't have any surpises here about upload/download, so I think we can move on20:27
nikhildarn the stmnt looks complicated20:27
markwashI'd appreciate it if any folks here want to chime in on the ML20:27
markwashjust to keep the late-game surprises to a minimum20:27
markwashlets talk about bugs for a minute20:28
markwash#topic bugs!20:28
*** openstack changes topic to "bugs! (Meeting topic: glance)"20:28
markwashfolks, I have not been paying enough attention to bugs20:28
markwashI think we might be out of the post-summit bp triage glut20:29
markwashso maybe we can start taking on bugs as a group?20:29
* jbresnah has been slacking on bugs lately20:29
jbresnah+120:29
iccha+120:29
ameadeyou mean triaging as a group?20:29
markwashameade: just bringing up the difficult ones20:30
markwashI think we can make our way through most as a matter of just personal attention20:30
markwashwith that in mind, does anyone have any bugs they're worried about right now?20:30
markwashI have https://bugs.launchpad.net/glance/+bug/115538920:31
ameadehttps://bugs.launchpad.net/glance/+bug/106997920:31
ameadeis the one I posted still true?20:31
markwashameade: I'm worried about that one too20:31
markwashameade: I think we need to double check to verify20:31
markwashameade: I assume that I originally marked it "invalid" for a good reason20:32
markwashbut that assumption may be wrong. .20:32
* markwash marksmash20:32
ameadehehe20:32
markwashwe need a bugbot in this channel20:33
markwashameade: can you look into that bug some more?20:33
ameadesure you can action it to me20:33
markwash#action ameade try to reproduce https://bugs.launchpad.net/glance/+bug/106997920:34
markwashameade: thanks!20:34
ameadei'll confirm it if it's true20:34
markwashlooks nasty if it is20:34
markwashand we could theoretically get in quick fix before havana 1 is released20:34
icchahmm i think esheffield tried it recently tried it and it worked , but would be definitely worth checking through20:34
markwash#action markwash try to do some bug triage for a change20:35
esheffieldI've been doing a lot of experimenting the last couple of days with image creates / uploads and they were working20:35
ameadei think taking a look at what the root issue described is would be good20:35
esheffieldonce I got the headers etc. right20:35
esheffieldbut didn't see that specific error20:35
markwashesheffield: we might need to ask him about what transport hes' using for notifications, too20:35
ameadeto make sure it doesnt sneak back in somehow20:35
*** dmitryme has quit IRC20:35
*** kgriffs has left #openstack-meeting-alt20:35
esheffieldyeah, that was just a plain vanilla devstack setup I was using20:35
markwashany other bugs people want to draw our collective attention to?20:36
markwashcool, lets move on to tracking some existing work20:37
*** IlyaE has quit IRC20:37
markwash#topic blueprints in progress20:37
*** openstack changes topic to "blueprints in progress (Meeting topic: glance)"20:37
markwashthere has been a lot of discussion of https://blueprints.launchpad.net/glance/+spec/api-v2-property-protection20:37
markwashcontinuing in the etherpad20:37
* markwash searches for link20:37
icchahttps://etherpad.openstack.org/public-glance-protected-props20:37
icchamarkwash: ^^20:38
markwashnot sure if we're getting closer to breaking ground, but if not any delays are probably due to me being a jerk20:38
markwashthe main issues right now are how to deal with collisions between protected properties and existing free-form properties20:39
markwashI think we'll probably have an update again next week20:39
*** ErikB has quit IRC20:39
icchathe challenges being v2 api advocates flat hierarchy for properties20:40
markwashwhich means, lots of collisions!20:40
markwash:-(20:40
markwashnikhil: do you want to talk about async workers?20:40
markwashnikhil: and can you remind me of any links20:41
markwashameade: ^^ I think I randomly assigned you to the async workers bp20:41
jbresnahthere are some requirements on etherpad: https://etherpad.openstack.org/havana-glance-requirements20:41
nikhilsure20:42
nikhiljbresnah: thanks20:42
jbresnahnp20:42
nikhilmarkwash: was wondering if you got a change to browse through a get a picture20:42
*** yippi has joined #openstack-meeting-alt20:42
nikhiltho i might have been a bit late in getting everything there20:42
markwashnikhil: I don't think I quite follow what you are asking me20:43
nikhilalso, haven't added the granular opinions on the requirements20:43
ameademan this async worker has a lot of responsibilities20:43
nikhili was talking about https://etherpad.openstack.org/havana-glance-requirements20:43
nikhilmarkwash: ^^20:43
nikhilameade: yeah20:43
icchado we have a list of must haves vs nice to haves?20:43
markwashnikhil: oh, okay20:43
nikhili thought flavio was doing some kinda poc20:44
markwashnikhil what I'm seeing looks good to me20:44
nikhilmarkwash: ah k , though I feel like adding more details20:44
jbresnahiccha: must haves would be good20:44
* ameade wishes we had an implemented workflow service20:44
nikhiljust dont want o step on peoples toes on what ideas are already out there20:44
markwashI think some simple POCs would be great things for making the next step20:44
icchajbresnah: i agree that may help us focus20:44
* markwash vaguely recalls promising some sort of POC of his own. . .20:45
icchadid we reach any agreement about threads vs separate process..20:45
esheffieldthere seems to be a lot of chatter related to workers in other projects as well20:45
esheffieldwondering if openstack needs a general worker service of some sort20:45
* ameade switches to openstack-meeting to ask if they are done with it yet20:45
jbresnahiccha: i think we didnt get that far into impl20:45
esheffieldfeels like there may be a lot of "wheel reinventing" about to happen20:45
ameadecan threads handle some of these heavyweight usecases?20:46
markwashiccha: I still feel great about making it a deployment config option (greenthreads vs other processes)20:46
nikhilmarkwash: +120:46
markwashesheffield: this wheel might not be as old or universal20:46
markwashbut maybe it is and I just don't get it yet20:46
nikhilmarkwash: may be even services (besides threads and processes)20:47
markwashesheffield: though I guess it does all feel kind of like celery20:47
* nikhil waits for a hurray from jbresnah 20:47
jbresnahnod celery20:47
esheffieldmarkwash: yeah, I've been looking more at celery20:47
jbresnahbut i would like to be able to have a simple impl too20:47
markwashdo we have any takers on a POC / straw man code?20:47
*** jdurgin has joined #openstack-meeting-alt20:47
markwashor should I just follow up with flaper87?20:47
jbresnahit is not worth forcing everything through amqp messaging20:48
jbresnahnd nikhil20:48
nikhilmarkwash: i would like to try that, if we'r not focusing on getting it before h120:48
markwashjbresnah: agree, especially when it can save deployers the trouble of making a change if they don't particularly care about the new async features20:48
esheffieldcelery does seem to support a "webhooks" approach as well, so maybe not everything thru amqp20:48
jbresnahI would still like to see the first thing be an interface definition for a worker20:48
markwashnikhil: cool, go for it. . it won't hurt to have more than one if flaper87 is already working on one too20:49
jbresnahesheffield: but i would like to even support thtreads, fork, multiprocessing potentially20:49
nikhilcool, i'll follow up with him too20:49
markwash#action nikhil work on a proof of concept for processing20:49
markwashI may look into that POC as well20:49
nikhil#action nikhil what mark said20:49
markwashno promises20:49
jbresnahnikhil: can the first step be an interface deifnition for a service?20:49
nikhil:)20:50
markwashjbresnah: +120:50
*** IlyaE has joined #openstack-meeting-alt20:50
* markwash <3s interfaces20:50
iccha10 minutes20:50
markwashiccha makes a good point20:50
nikhiloh yeah20:50
icchai want to bring up something thats why :p20:50
markwashiccha for open discussion?20:50
icchayeah20:51
markwashcool20:51
markwash#topic open discussion20:51
*** openstack changes topic to "open discussion (Meeting topic: glance)"20:51
markwashiccha you go first20:51
jbresnahI have something too, but I yield to the representative from rackspace20:51
icchawe have oft and on talked about soft deletes, where we want to keep them if it would be great to take a look at alternative approaches than existing one20:51
iccha*whther20:51
jbresnah+120:52
markwash+120:52
jbresnahit seems that glance developers are on the same page there20:52
jbresnahbut not so much the users20:52
markwashfrom where I'm sitting, I'd love to see us fix the admin uuid reuse issue first20:52
markwashand then draw up a deprecation plan for getting rid of soft deletes20:52
jbresnah+1 uuid20:52
ameadesomeone please describe the use cases that caused soft deletes to happen20:52
ameadein the first place20:53
jbresnahameade: agreed20:53
jbresnahameade: we tried to tease it out on the mailing lists but pretty much failed20:53
markwashameade: the use case is "as a glance developer, I want to copy and paste nova's (oslos) db models, to save work"20:53
iccharosmaita: had good use cases for why we need soft deletes20:53
* markwash turns his sarcasm back off :-)20:53
icchaso we can look at alternative approaches if he manages to convince us :)20:53
jbresnahheh20:53
ameademarkwash: i figured that was why20:54
ameade:P20:54
rosmaitawell, suppose i make an image and put a lot of package info into the metadata20:54
jbresnahmarkwash: but if that is the reason it exists it is very helpful to know20:54
rosmaitaand i want to find out what that was, even though the image was deleted in the mean tim20:54
rosmaita*time20:54
*** IlyaE has quit IRC20:54
jbresnahrosmaitia: i think that is a misuse tho20:54
rosmaitawhy?20:54
jbresnahrosmaitia: because glance only knows what the metadata is now20:55
jbresnahrosmaitia: it can change throughout the lifetime20:55
jbresnahlooking up meta for a running instance give no gaurentee of consistancy20:55
markwashrosmaita: seems like a reasonable use case to me20:55
*** IlyaE has joined #openstack-meeting-alt20:55
jbresnahmarkwash: all that will give you is the metadata at the time of delete20:55
markwashrosmaita: we probably just need to figure out the right way to do that in the api, or through notifications or more structured logging20:55
jbresnahmarkwash: and that is only if updates are not allowed after delete20:55
markwashjbresnah: good points as well20:56
rosmaitaok, another use case would be if glance does a "changes-since" list like nova has20:56
jbresnahthat is sort of the same usecase that was talked aobut on the mailing list20:56
jbresnahand i think it is trying to use glance as a hammer when it was designed to be a wrench20:56
* jbresnah is not familiar with changes since20:57
markwash(3 minutes)20:57
rosmaitalets you see your servers from a particular time, even deleted ones20:57
ameadechanges-since is still auditing right?20:57
icchahere is another way to look at it, than getting rid of info; say if we err on side of keeping it and have a better way to soft delete. what do we lose?20:57
jbresnahrosmaita: so it takes all the changes and lets you get a view from any particular time?20:57
rosmaitaright20:57
markwashcan we take this discussion offline and hit a few more quick items?20:58
jbresnahrosmaita: sort of like version control (like git or whatever) would do?20:58
icchago for it markwash20:58
jbresnahnod20:58
markwashnext weeks meeting time20:58
rosmaitajbresnah: not as fine grained20:58
*** bryansd has left #openstack-meeting-alt20:58
markwashcrap I forgot my suggested time options20:58
iccha7 pm EST20:59
nikhiltime buddy?20:59
rosmaitawhile mark is thinking, also, check out spec for clonning BP: https://wiki.openstack.org/wiki/Glance-image-cloning20:59
iccha4 am EST :p20:59
markwashoh yeah, that one20:59
nikhillooks funky rosmaita20:59
markwashI think 7 pm EST would be good for folks other than in europe21:00
markwashbut flaper tends to stay up late anyway21:00
iccha*EDT21:00
markwashwell, I'll send out an email21:00
*** IlyaE has quit IRC21:00
markwashsince we're runnig out of time21:00
nikhilhaha, prolly we'd talk in UTC21:00
markwashany quick thoughts on another bug / review squash day?21:00
markwash+1 ?21:00
jbresnahfridays work well for me for such things21:00
jbresnah+121:00
iccha+121:00
rosmaita+1, hope to help this time21:00
ameade+121:01
esheffield+121:01
markwashlet's try for friday, unless its conflicts with the havana-1 release in a silly way21:01
markwashthanks everybody, in order not to anger the gods of timeliness, I'm going to close it out21:01
icchais anything due for h1?21:01
markwash. . . nothing critical21:01
markwashwe should probably start pushing harder on h2 deadlines though21:02
markwashas possible by the constraints of open source21:02
markwashThanks everybody!21:02
markwash#endmeeting21:02
*** openstack changes topic to "OpenStack meetings (alternate)"21:02
openstackMeeting ended Thu May 23 21:02:31 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-05-23-20.02.html21:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-05-23-20.02.txt21:02
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-05-23-20.02.log.html21:02
*** jbresnah has left #openstack-meeting-alt21:02
*** IlyaE has joined #openstack-meeting-alt21:05
*** yippi has quit IRC21:08
*** IlyaE has quit IRC21:10
*** johnthetubaguy has joined #openstack-meeting-alt21:10
*** amyt has quit IRC21:19
*** amyt has joined #openstack-meeting-alt21:19
*** dmitryme has joined #openstack-meeting-alt21:21
*** IlyaE has joined #openstack-meeting-alt21:23
*** oz_akan has quit IRC21:30
*** IlyaE has quit IRC21:30
*** dmitryme has quit IRC21:34
*** IlyaE has joined #openstack-meeting-alt21:40
*** IlyaE has quit IRC21:45
*** IlyaE_ has joined #openstack-meeting-alt21:50
*** djohnstone has quit IRC21:55
*** IlyaE_ has quit IRC21:59
*** johnthetubaguy has quit IRC22:03
*** IlyaE has joined #openstack-meeting-alt22:05
*** IlyaE_ has joined #openstack-meeting-alt22:12
*** IlyaE has quit IRC22:16
*** IlyaE_ has quit IRC22:17
*** IlyaE has joined #openstack-meeting-alt22:22
*** IlyaE has quit IRC22:32
*** tanisdl has quit IRC22:42
*** tanisdl has joined #openstack-meeting-alt22:47
*** IlyaE has joined #openstack-meeting-alt22:56
*** bdpayne has quit IRC23:00
*** IlyaE has quit IRC23:01
*** wolfdreamer has quit IRC23:18
*** IlyaE has joined #openstack-meeting-alt23:18
*** tanisdl has quit IRC23:21
*** IlyaE has quit IRC23:22
*** IlyaE has joined #openstack-meeting-alt23:48
*** IlyaE has quit IRC23:52
*** yidclare has quit IRC23:55
*** seanrob_ has joined #openstack-meeting-alt23:55
*** seanrob has quit IRC23:59

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