Thursday, 2013-09-19

*** cmcnamara has joined #openstack-meeting-alt00:04
*** SergeyLukjanov has quit IRC00:07
*** sarob_ has joined #openstack-meeting-alt00:14
*** sarob has quit IRC00:17
*** sarob_ has quit IRC00:18
*** zzs has joined #openstack-meeting-alt00:20
*** zzs has left #openstack-meeting-alt00:24
*** vipul is now known as vipul-away00:25
*** vipul-away is now known as vipul00:25
*** bdpayne has quit IRC00:27
*** sacharya has joined #openstack-meeting-alt00:31
*** tanisdl has joined #openstack-meeting-alt00:34
*** tanisdl has quit IRC00:38
*** vipul is now known as vipul-away00:40
*** nosnos has joined #openstack-meeting-alt00:40
*** jmaron has joined #openstack-meeting-alt00:51
*** vipul-away is now known as vipul00:51
*** cmcnamara has quit IRC00:53
*** cmcnamara has joined #openstack-meeting-alt00:54
*** jcoufal has quit IRC00:56
*** amytron has quit IRC00:56
*** jmaron has quit IRC00:56
*** cmcnamara has quit IRC00:58
*** thatsdone has joined #openstack-meeting-alt01:06
*** cmcnamara has joined #openstack-meeting-alt01:09
*** thatsdone has quit IRC01:27
*** thatsdone has joined #openstack-meeting-alt01:29
*** thatsdone has quit IRC01:30
*** HenryG has quit IRC01:32
*** thatsdone has joined #openstack-meeting-alt01:32
*** thatsdone has quit IRC01:33
*** thatsdone has joined #openstack-meeting-alt01:33
*** thatsdone has quit IRC01:34
*** thatsdone has joined #openstack-meeting-alt01:36
*** lblanchard has joined #openstack-meeting-alt01:38
*** yidclare has quit IRC01:38
*** esker has joined #openstack-meeting-alt01:47
*** eankutse has joined #openstack-meeting-alt01:50
*** kebray has joined #openstack-meeting-alt01:51
*** jmaron has joined #openstack-meeting-alt01:52
*** jmaron has quit IRC01:58
*** thatsdone has quit IRC02:06
*** kebray has quit IRC02:09
*** esker has quit IRC02:16
*** kebray has joined #openstack-meeting-alt02:23
*** kebray has quit IRC02:28
*** eankutse has quit IRC02:33
*** eankutse has joined #openstack-meeting-alt02:34
*** sarob has joined #openstack-meeting-alt02:45
*** jmaron has joined #openstack-meeting-alt02:54
*** lblanchard has quit IRC02:56
*** sarob has quit IRC03:29
*** sarob_ has joined #openstack-meeting-alt03:30
*** boris-42 has joined #openstack-meeting-alt03:30
*** jmaron has quit IRC03:32
*** boris-42 has quit IRC03:35
*** sarob_ has quit IRC03:37
*** sarob has joined #openstack-meeting-alt03:37
*** sarob has quit IRC03:41
*** cmcnamara has quit IRC03:47
*** sarob has joined #openstack-meeting-alt03:48
*** jmaron has joined #openstack-meeting-alt03:59
*** thatsdone has joined #openstack-meeting-alt04:03
*** sacharya has quit IRC04:04
*** sarob has quit IRC04:06
*** sarob has joined #openstack-meeting-alt04:10
*** SergeyLukjanov has joined #openstack-meeting-alt04:12
*** jmaron has quit IRC04:41
*** akuznetsov has joined #openstack-meeting-alt04:42
*** thatsdone has quit IRC04:43
*** vipul is now known as vipul-away04:46
*** jmaron has joined #openstack-meeting-alt05:07
*** dmakogon_ has joined #openstack-meeting-alt05:17
*** vipul-away is now known as vipul05:20
*** SergeyLukjanov has quit IRC05:22
*** boris-42 has joined #openstack-meeting-alt05:23
*** jmaron has quit IRC05:25
*** thatsdone has joined #openstack-meeting-alt05:47
*** thatsdone has quit IRC05:49
*** eankutse has quit IRC05:53
*** akuznetsov has quit IRC05:57
*** akuznetsov has joined #openstack-meeting-alt06:17
*** jmaron has joined #openstack-meeting-alt06:21
*** jmaron has quit IRC06:26
*** akuznetsov has quit IRC06:33
*** akuznetsov has joined #openstack-meeting-alt06:41
*** SergeyLukjanov has joined #openstack-meeting-alt06:52
*** jtomasek has joined #openstack-meeting-alt06:53
*** jmaron has joined #openstack-meeting-alt07:21
*** dmakogon_ has quit IRC07:24
*** jmaron has quit IRC07:26
*** noslzzp has joined #openstack-meeting-alt07:45
*** akuznetsov has quit IRC08:17
*** flaper87|afk is now known as flaper8708:17
*** jmaron has joined #openstack-meeting-alt08:22
*** jmaron has quit IRC08:27
*** sarob has quit IRC08:33
*** sarob has joined #openstack-meeting-alt08:33
*** sarob has quit IRC08:38
*** nadya has joined #openstack-meeting-alt08:42
*** flaper87 is now known as flaper87|afk08:50
*** akuznetsov has joined #openstack-meeting-alt08:54
*** sarob has joined #openstack-meeting-alt09:04
*** SergeyLukjanov has quit IRC09:09
*** sarob has quit IRC09:12
*** jmaron has joined #openstack-meeting-alt09:23
*** jmaron has quit IRC09:27
*** sarob has joined #openstack-meeting-alt09:39
*** sarob has quit IRC09:43
*** noslzzp has quit IRC09:58
*** sungju has joined #openstack-meeting-alt10:03
*** jmaron has joined #openstack-meeting-alt10:23
*** jmaron has quit IRC10:28
*** sarob has joined #openstack-meeting-alt10:39
*** sarob has quit IRC10:44
*** sungju has quit IRC10:51
*** ruhe has joined #openstack-meeting-alt11:07
*** yamahata has quit IRC11:13
*** jmaron has joined #openstack-meeting-alt11:24
*** ruhe has quit IRC11:26
*** jmaron has quit IRC11:29
*** nosnos has quit IRC11:38
*** jcoufal has joined #openstack-meeting-alt11:39
*** nosnos has joined #openstack-meeting-alt11:39
*** sarob has joined #openstack-meeting-alt11:40
*** boris-42_ has joined #openstack-meeting-alt11:40
*** boris-42 has quit IRC11:41
*** nosnos has quit IRC11:43
*** HenryG has joined #openstack-meeting-alt11:44
*** sarob has quit IRC11:44
*** pcm_ has joined #openstack-meeting-alt11:46
*** thatsdone has joined #openstack-meeting-alt11:48
*** yamahata has joined #openstack-meeting-alt11:49
*** pcm_ has quit IRC12:06
*** pcm_ has joined #openstack-meeting-alt12:07
*** pdmars has joined #openstack-meeting-alt12:09
*** pdmars has quit IRC12:09
*** pdmars has joined #openstack-meeting-alt12:10
*** thatsdone has quit IRC12:13
*** jmaron has joined #openstack-meeting-alt12:24
*** jmaron has quit IRC12:29
*** ruhe has joined #openstack-meeting-alt12:31
*** nmakhotkin has joined #openstack-meeting-alt12:37
*** nmakhotkin has quit IRC12:39
*** nmakhotkin has joined #openstack-meeting-alt12:39
*** lblanchard has joined #openstack-meeting-alt12:48
*** nmakhotkin has quit IRC12:52
*** nmakhotkin has joined #openstack-meeting-alt12:53
*** amytron has joined #openstack-meeting-alt12:55
*** demorris has joined #openstack-meeting-alt12:57
*** ekarlso has quit IRC13:06
*** nmakhotkin has quit IRC13:06
*** sarob has joined #openstack-meeting-alt13:10
*** julim has joined #openstack-meeting-alt13:12
*** nmakhotkin has joined #openstack-meeting-alt13:12
*** eankutse has joined #openstack-meeting-alt13:14
*** sarob has quit IRC13:15
*** ozstacker has quit IRC13:18
*** ozstacker has joined #openstack-meeting-alt13:18
*** yamahata has quit IRC13:19
*** eankutse has quit IRC13:20
*** eankutse has joined #openstack-meeting-alt13:21
*** jmaron has joined #openstack-meeting-alt13:25
*** ozstacker has quit IRC13:27
*** ozstacker has joined #openstack-meeting-alt13:28
*** yamahata has joined #openstack-meeting-alt13:28
*** esker has joined #openstack-meeting-alt13:29
*** esker has quit IRC13:29
*** esker has joined #openstack-meeting-alt13:29
*** jmaron has quit IRC13:30
*** jmaron has joined #openstack-meeting-alt13:31
*** julim has quit IRC13:33
*** amytron has quit IRC13:35
*** AndroUser2 has joined #openstack-meeting-alt13:36
*** nmakhotkin has quit IRC13:37
*** yamahata has quit IRC13:37
*** jergerber has joined #openstack-meeting-alt13:39
*** zhiyan has joined #openstack-meeting-alt13:42
*** yamahata has joined #openstack-meeting-alt13:44
*** nmakhotkin has joined #openstack-meeting-alt13:44
*** AndroUser2 has quit IRC13:48
*** NehaV has joined #openstack-meeting-alt13:51
*** eankutse has quit IRC13:52
*** NehaV has quit IRC13:55
*** NehaV has joined #openstack-meeting-alt13:55
*** NehaV1 has joined #openstack-meeting-alt13:58
*** NehaV has quit IRC13:59
*** yamahata has quit IRC14:01
*** bugsduggan has joined #openstack-meeting-alt14:01
*** amytron has joined #openstack-meeting-alt14:04
*** yamahata has joined #openstack-meeting-alt14:04
*** dkoryavov has joined #openstack-meeting-alt14:05
*** dkoryavov has quit IRC14:05
*** nmakhotkin has quit IRC14:06
*** bugsduggan has left #openstack-meeting-alt14:10
*** eankutse has joined #openstack-meeting-alt14:11
*** megan_w has quit IRC14:17
*** ekarlso has joined #openstack-meeting-alt14:20
*** sacharya has joined #openstack-meeting-alt14:20
*** jmaron has quit IRC14:26
*** megan_w has joined #openstack-meeting-alt14:29
*** jmontemayor has joined #openstack-meeting-alt14:31
*** sarob has joined #openstack-meeting-alt14:31
*** sacharya has quit IRC14:32
*** ruhe has quit IRC14:32
*** yamahata has quit IRC14:34
*** sarob has quit IRC14:36
*** yamahata has joined #openstack-meeting-alt14:36
*** yportnova_ has joined #openstack-meeting-alt14:42
*** ruhe has joined #openstack-meeting-alt14:43
*** vponomaryov has joined #openstack-meeting-alt14:45
*** vbellur has joined #openstack-meeting-alt14:51
*** betsy has joined #openstack-meeting-alt14:52
*** shadower is now known as shadowarrr14:52
*** rnirmal has joined #openstack-meeting-alt14:54
*** bswartz has joined #openstack-meeting-alt14:54
*** rraja has joined #openstack-meeting-alt14:56
*** jmaron has joined #openstack-meeting-alt14:57
*** zaitcev has joined #openstack-meeting-alt14:58
*** amytron has quit IRC14:58
*** yamahata has quit IRC14:59
*** shamail has joined #openstack-meeting-alt14:59
*** vbelokon has joined #openstack-meeting-alt14:59
*** jmaron1 has joined #openstack-meeting-alt15:00
*** demorris has quit IRC15:00
*** jmaron has quit IRC15:00
bswartz#startmeeting manila15:00
openstackMeeting started Thu Sep 19 15:00:53 2013 UTC and is due to finish in 60 minutes.  The chair is bswartz. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: manila)"15:00
openstackThe meeting name has been set to 'manila'15:00
bswartzhello everyone15:01
vbellurbswartz: hello15:01
*** yidclare has joined #openstack-meeting-alt15:01
vbelokonhi15:01
yportnova_hi15:01
shamailHi15:01
vponomaryovhi15:01
bswartzokay so last week we said our goal was to get the code into stackforge by today15:02
bswartz#topic status15:02
*** openstack changes topic to "status (Meeting topic: manila)"15:02
*** yamahata has joined #openstack-meeting-alt15:02
bswartzWe've submitted the code at least15:02
bswartzvbelokon: can you tell us where that sits now?15:02
*** caitlin-nexenta has joined #openstack-meeting-alt15:02
*** flwang has joined #openstack-meeting-alt15:03
vbelokonbswartz: yes, we submitted to code, but we need approval from core-developers of Infra project15:03
vbelokonhttps://review.openstack.org/#/c/46919/15:03
vbelokonone +2 we have, another +2 we need15:03
*** sacharya has joined #openstack-meeting-alt15:03
vbelokonJeremy Stanley (core-developer) promised us to set +2 today during the day.15:03
vbelokonso, I hope Manila project will in StackForge today or tomorrow15:03
bswartzokay15:04
vbelokonalso we created blueprints to add changes in DevStack and Tempest to support Manila15:04
*** demorris has joined #openstack-meeting-alt15:04
vbelokonhttps://blueprints.launchpad.net/devstack/+spec/manila-project-support15:04
vbelokonhttps://blueprints.launchpad.net/tempest/+spec/manila-project-tempest-tests15:04
*** tkatarki has joined #openstack-meeting-alt15:04
*** bvandehey has joined #openstack-meeting-alt15:04
vbelokonthese blueprints we need to push our changes (supporting of Manila) to DevStack and Tempest15:04
bswartzvbelokon: ty15:04
vbellurvbelokon: sounds good15:05
vbelokonso, currently we are working on current bugs https://bugs.launchpad.net/manila/+bugs15:05
bswartzokay so we need to wait another day or so on stackforge15:05
vbelokonbswartz: yes15:05
*** navneet has joined #openstack-meeting-alt15:05
bswartzonce we're accepted there I plan to make another announcement on the ML15:05
bswartzand hopefully we'll see some more participation in these meetings15:06
*** davenoveck has joined #openstack-meeting-alt15:06
tkatarkihello all. in way of quick intro, I am from Red Hat and work with vbellur15:06
bswartzI imagine most people are holding back because they couldn't contribute code if they wanted to right now15:06
bswartztkatarki: welcome!15:06
vbelokontkatarki: hi15:07
caitlin-nexentabswartz: my suggestion is to focus on documentation for NAS vendors first, users later.15:07
*** bill_az has joined #openstack-meeting-alt15:07
*** yamahata has quit IRC15:07
*** zane has joined #openstack-meeting-alt15:07
vbellurwe have rraja and zaitcev joining from Red Hat too.15:07
bill_azHi, this is Bill Owen from IBM joining15:07
vbellurbill_az: hello15:07
bswartzcaitlin-nexenta: I agree -- I've been thinking about some of the "last mile" issues and how they will be tacked by various backends and it's a complicated problem15:08
* caitlin-nexenta is from Nexenta15:08
vbellurcaitlin-nexenta: hello15:08
bswartzI need to capture my thoughts in a document and get it up online15:08
bswartzbill_az: hello and welcome15:08
bill_azHi, thanks, glad to be here15:08
caitlin-nexentabswartz feel free to use me as a beta proofreader.15:08
*** caitlin-nexenta has quit IRC15:08
*** caitlin-nexenta has joined #openstack-meeting-alt15:09
*** kebray has joined #openstack-meeting-alt15:09
zaitcevI am just looking if I can be useful in the future, but currently I am up to my neck in Swift until end of September.15:09
bswartzokay15:09
bswartzthis is a good time to be joining because we're still designing things and and it's not too late to influence the eventual direction we take15:10
bswartzwe're at an odd phase now relative to the rest of openstack, because everytone else is worried about getting their release done and we don't have to worry about that15:10
bill_azbswartz:  I have been working on icnder driver for gpfs backend, and am looking forward to contributing to manila as well15:11
eskerbswartz: wrt to "holding back" your first announcement never actually made it to the wider list15:11
bswartzI expect a lot of stuff to get solidified during the icehouse timeframe however such that 6 months from now it will feel like a normal openstack project15:11
bill_az(cinder driver)15:11
bswartzbill_az: are you the actual developer? if so I'd like to talk to you and get you opinions on our design for the manila "driver" interface15:12
zaitcevIndeed, as esker says I did not even knew Manila existed until Ayal mentioned it.15:12
*** alexpecoraro has joined #openstack-meeting-alt15:12
*** yamahata has joined #openstack-meeting-alt15:13
bill_azbswartz:  yes, I'm doing most of the work on cinder driver for gpfs, and I'd be happy to discuss driver interface for manila15:13
bswartzesker, zaitcev: Yes I apologize but the initial announcement was evidently eaten by the ML. By the time I discovered what happened I'd changed my mind about making the announcement to wait until we were part of stackforge15:13
bswartzso the announcement which you can expect next week will actually be the "first" announcement that most people will see15:14
*** yportnova_ has quit IRC15:14
eskerbswartz: better this way... when the announcement goes out to the wider community there will be something substantive to look at15:14
caitlin-nexentaYou're better off announcing sooner than later. I was thinking of making a proposal myself when googling found the older Netapp Cinder proposal, and I asked about it.15:14
vbelluryeah, the timing is quite right now.15:14
caitlin-nexentaOthers might just start the same work in Cinder or Swift, better to be visible.15:14
bswartzcaitlin-nexenta: I know -- it's just a few days away now15:14
eskergreat... the stackforge stuff is almost done so all is aligning15:15
bswartzcaitlin-nexenta: regarding doing the work in cinder or swift -- we tried that and got nowhere, so I'm not worried about someone else trying that and succeeding15:15
eskerbswartz:  it might be time to start blueprinting the various options for solving the last mile problem15:15
tkatarki+1 on that15:15
bswartzbut the point is still valid that we want the community to know we're here15:15
shamail+115:16
eskerFWIW, we've operated under the presumption that on 1 option will suffice15:16
eskerrather... no 1 option will suffice15:16
caitlin-nexentabswartz : the worry is them trying and failing.15:16
bswartzokay anything more on status? we sort of took a side track here15:17
bswartzvbelokon: anything you wanted to discuss?15:17
vbelokonyes15:17
*** ruhe has quit IRC15:17
vbelokonI'd like to discuss nearest roadmap15:17
vbelokonand ask you to approve existing blueprints15:18
vbelokonor create new most important for current step15:18
*** zhiyan has quit IRC15:18
bswartzokay it sounds like we need the next topic15:19
bswartz#topic planning15:19
*** openstack changes topic to "planning (Meeting topic: manila)"15:19
*** zhiyan has joined #openstack-meeting-alt15:19
vbelokonhttps://blueprints.launchpad.net/manila15:19
*** amytron has joined #openstack-meeting-alt15:19
bswartz#link https://blueprints.launchpad.net/manila15:20
*** yportnova__ has joined #openstack-meeting-alt15:20
bswartzokay since we've already discussed quotas a great deal, I'd like to get that design finalized so we can finish it15:21
bswartzwe can talk a bit more about that in a minute15:21
bswartzthese other BPs are also important15:22
*** HenryG has quit IRC15:22
bswartzI think we need more however15:22
*** HenryG has joined #openstack-meeting-alt15:22
bswartzthe issue of connecting shares to guests is a complex one which we need to approach carefully15:23
bswartzby next  week I'll get a wiki page up that capture the issues15:23
vbelokonbswartz: good15:23
caitlin-nexentaEspecially if we want to embrace as many NAS vendors as possible.15:23
bswartz#action bswartz create wiki page for "last mile problem"15:24
bswartzHopefully people can read it and maybe next week we can create some BPs to address the isssues that exist15:24
yportnova__bswartz: will we make changes in current ACL implementation?15:24
bswartzFor those who are new, I'll summarize my thinking15:24
bswartzyportnova__: yes we will need to15:25
bswartzyportnova__: that's just one part of what's needed however15:25
tkatarkibswartz: it would definitely help. I am new. I hget the 100K view of what we want to do but could use a 10K view.15:25
bswartzSo our current thinking is that theres not a single way to deal with the network plumbing issue that will work for every user15:26
vbellurbswartz: agree with that15:26
bswartzWe need to implement a few ways to do it, and give administrators a choice (an option they can set in manila.conf)15:26
bswartzThis will probably result in a "frontend" plugin interface of some kind, because there will be parts of the connect-share-to-guest code that can be shared by all backends15:27
*** mestery has joined #openstack-meeting-alt15:27
caitlin-nexentabswartz: having a few options is great, but selling participation to my management requires that it not be an open-ended set of extra options.15:27
bswartzthat being said, I think it will be unavoidable that backends will need to explicitly support various connection methods15:27
bswartzThe connection methods we're considering are:15:28
bswartz0) Assume flat network and require the storage controller to enforce security15:28
bswartz1) Support segmented tenant networks and integrate w/ neutron to connect the storage controller to the tenant network15:29
bswartz2) Rely on hypervisor to tunnel NAS protocol from backend network to tenant network15:30
*** zhiyan has quit IRC15:30
eskeradditionally, there's the question of how instances (or other consumers) dynamically absorb and mount shares15:30
bswartz3) Exotic stuff like VirtFS to wrap the filesystem access15:30
caitlin-nexentaWhy is 2) different than 1)? Neutron supports different forms of tunneling.15:30
bswartzcaitlin-nexenta: it comes down to how smart the backend is required to be in the 2 cases15:31
caitlin-nexentaOr to put it another way, if a new tunelling method is needed - why not do it in the Neutron project?15:31
bswartzcaitlin-nexenta: I suspect the differences will be more clear when I write down all the details15:32
*** ruhe has joined #openstack-meeting-alt15:32
bswartzcaitlin-nexenta: if there's a trick we can use to force all the ugliness into neutron I'd be thrilled15:33
navneetcaitlin-nexenta: +115:33
caitlin-nexentaYou mean allow neutron to provide more features. ;-)15:33
bill_azbswartz:  can we hide the details of the connection type from the drivers?  can those details be encapsulated in connection class?15:33
bswartzAt the end of the day, the backends will have to understand the differences between tenants though15:33
navneethow abt having a connection manager to deal with different networks15:34
bswartzbill_az: I want to minimize how much the drivers have to deal w/ because we want to make drivier writing easy15:34
caitlin-nexentabill_az: I don't see how you hide the difference between 0 and 1. It is the context thaqtyou do authentiation in.15:34
navneetalso interface with neutron15:34
*** SergeyLukjanov has joined #openstack-meeting-alt15:34
bswartzhowever I think you'll see that when you consider all the issues there's no way to encapsulate a solution in something simple and clean15:35
bswartznevertheless we will strive toward something simple and clean!15:35
ekarlsocan I ask, what's Manila ?15:35
shamailbswartz: Let's get the wiki out there.  I think this topic will have great discussions.15:35
vbellurI think it would be good to await out bswartz's proposal.15:35
bswartzthese are longer term issues though, lets get back to the next week or 215:35
bswartzekarlso: a file-share management service for OpenStack15:36
bswartz#link https://wiki.openstack.org/wiki/Shares_Service15:36
ekarlsowasn't that a part of cinder ?15:36
bswartzekarlso: yes!15:36
bswartzekarlso: it was never accepted and we've move the code to this new project called manila15:36
bswartzmoved*15:36
*** caitlin-nexenta has quit IRC15:37
bswartz#topic quotas15:37
*** openstack changes topic to "quotas (Meeting topic: manila)"15:37
*** caitlin-nexenta has joined #openstack-meeting-alt15:37
bswartzokay so last week we spent a few minutes discussion the question of how quotas interact w/ snapshots15:38
bswartzdiscussing*15:38
bswartzif you allocate a 10GB NFS share, that counts as 10GB towards your quota15:38
caitlin-nexentaWhere would quotas be enforced? (stepping directly into the first tar-pit)15:38
*** sarob has joined #openstack-meeting-alt15:39
bswartzhowever if you only fill up 1GB of that share and then take a snapshot, it feels like charging another 10GB to your quota is not the right thing to do15:39
*** SergeyLukjanov has quit IRC15:39
bswartzintuitively, we should charge 1GB to the quota in that case15:39
caitlin-nexentaAnd if your NAS target does compression and/or dedup, do you get credit?15:39
*** HenryG has quit IRC15:39
shamailbswartz: Array-level snapshots?15:39
bswartzThe problem comes in when you're trying to figure out how much space was actually consumed out of the 10GB15:40
*** HenryG has joined #openstack-meeting-alt15:40
bswartzI believe that drivers are going to need to provide that information because manila will not be able to determine it in a generic way15:40
caitlin-nexentaThe big question is: are the quotas for guaranteed resources or actually consumed resources?15:40
caitlin-nexentaActual consumption is more useful, but only the targets can provide that data.15:41
bswartzcaitlin-nexenta: regarding space savings from vendor-specific technologies, I think we have to hide those savings from end-users and make the admin the beneficiary of them15:41
*** bdpayne has joined #openstack-meeting-alt15:42
bswartzthe reason for this is because we don't want inconsistent behaviour in multivendor environments15:42
caitlin-nexentaAt least for cross-tenant savings, otherwise you are leaking info between tenants.15:42
tkatarkii would think quota is "not to exceed" limit15:42
yportnova__bswartz: in this case how we can reserve resources?15:43
bswartztkatarki: yes the idea is that manila will enforce your quota by preventing you from taking a snapshot or creating a new share when you've reached your quota15:43
caitlin-nexentaBut are those limits enforced in a client with *no* concept of what actual resources are used, or in the target with deliberately limited single-tenant knowledge?15:44
caitlin-nexentaParticularly with snapshots, the client view will radically overstate the usage of storage with a Netapp or ZFS style snapshot.15:44
bswartzif we can agree that the drivers are required to report the "size" of a snapshot after its created, then the only issue is what kind of guidance do we provide to driver authors15:44
tkatarkiquota is not same as usage. So I would think that it is an enforcement at the client15:45
shamailbswartz: wouldn't Manila only be aware of allocation vs consumption of resources?15:45
bswartzshamail: yes15:45
shamailbswartz: I like the idea of the drivers handling this15:45
caitlin-nexentaThe client does not want to limit the total "size" of a single snapshot. They want to know how much disk space their snapshots are actually consuming.15:45
bswartzif you allocate a 10GB share, you lose 10GB from your quota immediately, even if you've written no data15:45
tkatarkithat seems ok to me15:46
bswartzthis is my proposal:15:46
*** bvandehey has quit IRC15:46
caitlin-nexentaIf you snapshot a 10 GB share 10 times are you using 100 GB of quota?15:47
bswartzthe "default" implementation of the snapshot size driver method should return the size of the share it was created from (which is the maximum value we could ever return)15:47
*** boris-42_ has quit IRC15:47
bswartzwe will suggest that driver authors provide a way to report how much space data the user has acutally filled up, not counting any space savings15:47
caitlin-nexentabswartz: at the minimum a driver module should be able to report aggregate actual usage (with the no-cross-tenant leakage caveat).15:48
tkatarkiguys let me ask a more basic question: is quota what u request to reserve when a file share is requested and created? That is, will I as a user be requesting 10GB and that is my "quota"15:48
bill_azif the driver returns both allocated and actually consumed space then the cloud operator has freedom to decide how to bill / account for this15:48
vbellurso would those be two separate methods?15:48
bswartzcaitlin-nexenta: yes15:49
caitlin-nexentaProviding both figures allows an operator to intelligently decide how many snapshots to retain.15:49
bswartzthe whole point of quotas in manila is to allow the manila admin to give a certain amount of space to a tenant that he can mange himself, either by creating new shares or taking snapshots of existing shares15:50
bswartzthe question of how the backend enforces that you don't write 11GB in to a 10GB share is a different issue15:50
bswartzsome controllers will use internal quotas to enforce such limits, and that's not what we're talking about15:51
shamailbswartz: There are also differences in how snapshot storage is allocated (reserved vs dynamic) and in either case snapshot capacity will change based on change rate.  If we track utilization then thus information may need to be updated periodically15:51
bswartzshamail: I think that's exactly what we want to avoid15:51
shamailthis*15:51
shamailbswartz: Agreed15:52
bswartzwe don't want the size of a snapshot to change because someone changed something else in the system somewehre15:52
bswartzthe size of the snapshot, for quota purposes, should be determined at the time it's taken15:52
caitlin-nexentaBut how much disk resources are required for a specific snapshot *does* change over time, even when viewed from a single tentant perspective.15:53
bswartzthen if the actual spaec consumed by the snapshot increases or decreases on the controller due to  compression or dedupe or other files getting deleted, we don't care15:53
caitlin-nexentaI'm talking about how much overlap there is with the current file system.15:53
caitlin-nexentaWith ZFS at the moment a snapshot is taken it is effectively consuming nearly zero disk space.15:54
bswartzcaitlin-nexenta: that's why I want to return a number large enough that it represents a number that will never be exceeded under any circumstance (a worst-case space number)15:54
*** sarob has quit IRC15:54
bswartzcaitlin-nexenta: that's right -- and the driver should not report the 0 number it should report how much data is in the snapshot15:54
shamailThere needs to be a defined "cost" for snapshots (each vendor can specify via driver)... The actual capacity would be great but difficult to track.15:54
caitlin-nexentaA quota for *all* snapshots on those terms might be reasonable.15:54
*** sarob has joined #openstack-meeting-alt15:54
vbellurshamail: +115:55
caitlin-nexentaBut stating a quota for *each* snapshot will grossly overallocate.15:55
davenoveckOk, but the issue of ovelap with current use is different than that of overlap among snapshots.15:55
bswartzokay I'm sensing this issue might be a sensitive one and require refinement over time15:55
*** mestery has quit IRC15:55
bswartzI'm going to propose that we do something VERY conservative for now, and we plan to propose better solutions in the future15:55
caitlin-nexentadavenoveck: +115:56
vbellurbswartz: +115:56
bswartzso in the short term, we will massively overcharge users for snapshots w.r.t. quotas on most backends (except very stupid ones)15:56
bswartzif we can agree on a better system then we will implement that later -- but I feel that we need to get some kind of quota support in from the beginning15:56
bswartzwe're almost out of time today15:57
bswartz#topic open discussion15:57
*** openstack changes topic to "open discussion (Meeting topic: manila)"15:57
bswartzanyone have anything else to bring up?15:58
vbellurnothing from me15:58
caitlin-nexentaHave you given any thought to the issue of NFSv4 vs NFSv3?15:58
shamailIs there any intersection between quota management and ceilometer in the future?15:58
bswartzcaitlin-nexenta: yes15:58
bswartzshamail: ceilometer is something I haven't spent time on but we will need to15:59
vbellurshould we move discussions over to #openstack-manila?15:59
*** sarob has quit IRC15:59
caitlin-nexentaI'm assuming from a charter point of view that we will have to support both, do you agree?15:59
bswartzyes everyone is welcome to join #openstack-manila and continue talking after we lose this room15:59
bswartzexpect an annoncement on the ML from me when we get into stackforge finally!16:00
*** davenoveck has quit IRC16:00
bswartz#endmeeting16:00
*** openstack changes topic to "OpenStack meetings (alternate)"16:00
vbellurbswartz: look forward to that!16:00
openstackMeeting ended Thu Sep 19 16:00:41 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-09-19-15.00.html16:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-09-19-15.00.txt16:00
openstackLog:            http://eavesdrop.openstack.org/meetings/manila/2013/manila.2013-09-19-15.00.log.html16:00
*** yportnova__ has quit IRC16:00
shamailI have to run but great discussions!! Take care everyone.16:00
vbellurlater everyone.16:00
*** vbellur has left #openstack-meeting-alt16:01
*** shamail has quit IRC16:01
*** vbelokon has left #openstack-meeting-alt16:01
*** bill_az has left #openstack-meeting-alt16:01
*** navneet has quit IRC16:02
*** ruhe has quit IRC16:03
*** markwash has joined #openstack-meeting-alt16:04
*** zaitcev has left #openstack-meeting-alt16:05
*** rraja has left #openstack-meeting-alt16:05
*** mestery has joined #openstack-meeting-alt16:05
*** mestery has joined #openstack-meeting-alt16:06
*** vponomaryov has quit IRC16:07
*** bswartz has left #openstack-meeting-alt16:07
*** tanisdl has joined #openstack-meeting-alt16:12
*** ruhe has joined #openstack-meeting-alt16:13
*** yaroslav has joined #openstack-meeting-alt16:20
*** yaroslav has left #openstack-meeting-alt16:20
*** ruhe has quit IRC16:22
*** jmaron1 has quit IRC16:25
*** sarob has joined #openstack-meeting-alt16:25
*** yidclare has quit IRC16:29
*** caitlin-nexenta has quit IRC16:35
*** caitlin-nexenta has joined #openstack-meeting-alt16:35
*** sarob has quit IRC16:36
*** caitlin-nexenta has quit IRC16:42
*** betsy_ has joined #openstack-meeting-alt16:43
*** betsy has quit IRC16:43
*** betsy_ is now known as betsy16:43
*** nadya has quit IRC16:50
*** dkoryavov has joined #openstack-meeting-alt16:51
*** eankutse has quit IRC16:54
*** jmaron has joined #openstack-meeting-alt16:57
*** akuznetsov has quit IRC16:58
*** anteaya has joined #openstack-meeting-alt16:59
*** sarob has joined #openstack-meeting-alt16:59
*** cp16net has left #openstack-meeting-alt17:01
*** jmaron has quit IRC17:02
*** alexpecoraro has quit IRC17:04
*** sarob has quit IRC17:14
*** sarob has joined #openstack-meeting-alt17:14
*** jmaron has joined #openstack-meeting-alt17:17
*** eankutse has joined #openstack-meeting-alt17:17
*** eankutse has quit IRC17:17
*** eankutse has joined #openstack-meeting-alt17:18
*** eankutse has quit IRC17:18
*** eankutse has joined #openstack-meeting-alt17:18
*** sarob has quit IRC17:19
*** eankutse has quit IRC17:21
*** eankutse has joined #openstack-meeting-alt17:21
*** lblanchard has quit IRC17:21
*** noslzzp has joined #openstack-meeting-alt17:21
*** yidclare has joined #openstack-meeting-alt17:23
*** mestery has quit IRC17:23
*** rnirmal has quit IRC17:25
*** rnirmal has joined #openstack-meeting-alt17:25
*** amytron has quit IRC17:28
*** eankutse1 has joined #openstack-meeting-alt17:30
*** eankutse has quit IRC17:31
*** NikitaKonovalov has joined #openstack-meeting-alt17:32
*** nadya has joined #openstack-meeting-alt17:32
*** ruhe has joined #openstack-meeting-alt17:35
*** HenryG has quit IRC17:35
*** aignatov_ has joined #openstack-meeting-alt17:38
*** mattf has joined #openstack-meeting-alt17:43
*** zane has quit IRC17:50
*** dukhlov has quit IRC17:51
*** alazarev has joined #openstack-meeting-alt17:56
*** akuznetsov has joined #openstack-meeting-alt17:58
*** sballe has joined #openstack-meeting-alt17:58
*** IlyaE has joined #openstack-meeting-alt17:58
*** NehaV1 has quit IRC17:58
*** NikitaKonovalov has quit IRC17:59
*** NikitaKonovalov has joined #openstack-meeting-alt17:59
*** amytron has joined #openstack-meeting-alt17:59
*** eankutse1 has quit IRC18:00
aignatov_hi all, are the Savanna folks around?18:02
ruhehi18:03
*** tanisdl has quit IRC18:03
NikitaKonovalovhi18:03
alazarevhi18:03
nadyao/18:03
rnirmalhi18:03
*** sreshetnyak has joined #openstack-meeting-alt18:04
jmaronhi18:04
akuznetsovhi18:04
*** julim has joined #openstack-meeting-alt18:04
aignatov_what's about RedHat guys and Hortonworks?18:04
*** ylobankov has joined #openstack-meeting-alt18:04
aignatov_ok, let's start18:05
*** eankutse has joined #openstack-meeting-alt18:05
aignatov_#startmeeting savanna18:05
openstackMeeting started Thu Sep 19 18:05:32 2013 UTC and is due to finish in 60 minutes.  The chair is aignatov_. Information about MeetBot at http://wiki.debian.org/MeetBot.18:05
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:05
*** openstack changes topic to " (Meeting topic: savanna)"18:05
openstackThe meeting name has been set to 'savanna'18:05
aignatov_#topic Agenda18:05
*** openstack changes topic to "Agenda (Meeting topic: savanna)"18:05
*** betsy_ has joined #openstack-meeting-alt18:05
aignatov_#info News / updates18:05
aignatov_#info Roadmap cleanup / update18:06
aignatov_#info Action items from the last meeting18:06
aignatov_#info General discussion18:06
aignatov_#topic News / updates18:06
*** openstack changes topic to "News / updates (Meeting topic: savanna)"18:06
aignatov_what about EDP?18:06
*** betsy has quit IRC18:07
*** betsy_ is now known as betsy18:07
nadyayesterday I successfully run pig job usin UI18:07
aignatov_smll note, Sergey is away today, I'm proxing him now18:07
aignatov_that's great, Nadya!18:08
aignatov_do you know knews from RedHat guys, Trevor and Chad working on edp?18:08
aignatov_knews-> news18:08
nadyayes18:09
aignatov_update from me, I've sent all patches related to moving vanilla to 1.2.1 Hadoop version18:10
akuznetsovwe find work around with problem getting information about host18:10
*** tkatarki has quit IRC18:10
akuznetsovnova return hostId which is hash of tenant id and host name18:10
*** crobertsrh has joined #openstack-meeting-alt18:10
aignatov_so, don't froget to update images in your environments and labs:)18:11
nadyaTrevor is working on job_manager refactoring and several bugs. Chad uploaded patch for UI that I've tested18:11
akuznetsovso knowing the rack configuration and using this information we can restore information about machine host18:11
akuznetsovcode is available on following patch set18:12
akuznetsov#link https://review.openstack.org/#/c/45434/18:12
aignatov_#info we find work around with problem getting information about host18:12
aignatov_#info work in progress on UI part and refactorin job_manager for EDP18:13
jmaronwhat image updates do we have to make in association with host issue?18:14
aignatov_hi, jmaron, what is that issue about? Can you give us more details?18:15
rnirmalakuznetsov: thanks for getting that in with the hostid... might be good to work with the scheduler team to get rack information as well.. but that's down the road18:15
aignatov_#topic Roadmap cleanup / update18:16
*** openstack changes topic to "Roadmap cleanup / update (Meeting topic: savanna)"18:16
rnirmaljmaron: if you are referencing the rack/host information.. no changes should be needed for the image. the topology.sh script should be injected on start18:16
jmaronok.  I was worried about "so, don't froget to update images in your environments and labs"18:17
aignatov_I think we should add Heat integration to  for the next cycle after the Savanna 0.3 released18:17
ruheaignatov_, isn't it already in the roadmap?18:18
*** markmcclain has joined #openstack-meeting-alt18:18
aignatov_I knnow that we palnned to add Heat to Savanna 1.0 release, it was the far future in our minds before TC meetings18:19
aignatov_ok18:19
aignatov_#action aignatov Update roadmap with Heat integration18:20
rnirmalI think we need to have a separate heat discussion. someone can correct me... but heat is based on file templates ... which may lead to a hacky solution trying to map the cluster templates to heat templates. i.e I think they don't have a programmable option. Or we covert cluster template to a heat template.18:21
*** tmckay has joined #openstack-meeting-alt18:21
rnirmalI've been trying to read up on heat.. hopefully will get to it this week18:22
ruhernirmal, i agree we don't need to pass hadoop cluster templates to Heat. But we can use Heat to provision and configure VMs with bare operating system18:22
aignatov_that's good point rnirmal,18:22
aignatov_ruhe, also +118:23
ruheHeat might also take care of anty-affinity, cinder volumes, etc18:23
aignatov_I've moving the next topic18:23
aignatov_#topic Action items from the last meeting18:23
*** openstack changes topic to "Action items from the last meeting (Meeting topic: savanna)"18:23
aignatov_there are no AIs on the last meeting, so next topic :)18:24
aignatov_#topic General discussion18:24
*** openstack changes topic to "General discussion (Meeting topic: savanna)"18:24
aignatov_rnirmal, you can create doc on wiki and etherpad to rite pur proc and cons and defficulty with Heat interation in details18:25
rnirmalaignatov_: yes I'll create a doc for it18:26
aignatov_I mean not only wiki pages with info why we can or cant use Heat in high level18:26
nadyayes, it's a good point. I think we should start thinking about integration with Heat18:26
rnirmalI'll start an etherpad which we can use to discussions first18:27
rnirmal#link https://etherpad.openstack.org/savanna_heat18:27
nadyabesides, Heat guys started to discuss autoscaling feature18:27
jmaronspecifically interested in some of the ssh and /etc/hosts setup required for savanna18:27
jmaron(can heat allow for such VM post processing)18:28
rnirmaljmaron: yeah I don't think that feature has been completed yet18:28
rnirmalthat will def be a blocker18:28
jmaronthat's a problem18:28
ruhejmaron, we'll need to implement it :)18:28
ruhein Heat18:28
jmaron:)18:28
ruheto be good citizens in OpenStack community18:29
nadyaif we want something special for Savanna from AS-feature we should let them know I guess18:29
aignatov_yes, we have to contribute to Heat in this case18:29
aignatov_otherwise it'll be a long way to get Savanna integrated w/o Heat :)18:29
rnirmalyeah it's going to end up that way18:29
*** yogesh has joined #openstack-meeting-alt18:30
*** sballe_ has joined #openstack-meeting-alt18:30
jmaronI guess it would be clearer to TC what the savanna value proposition is post Heat integration18:31
*** sballe_ has quit IRC18:31
aignatov_guys another request from Sergey and me: we have a tons of patches on the review18:32
mattfi'll take another shot at some this evening18:33
*** mestery has joined #openstack-meeting-alt18:33
*** sballe has quit IRC18:33
aignatov_please work with the code reviews more frequently18:33
aignatov_that;s request for all18:34
aignatov_thanks mattf18:35
*** NehaV has joined #openstack-meeting-alt18:36
aignatov_I'll try to merge patches with high raiting18:36
aignatov_hihg rating I mean more than two +1/+218:37
ruheImportant reminder: Next TC meeting will be on Tuesday at 20:00 UTC at #openstack-meeting ; TC will vote for Savanna incubation18:37
mattfruhe, thanks for the reminder18:37
aignatov_thanks ruhe18:37
aignatov_are there any other items to discuss?18:38
*** lblanchard has joined #openstack-meeting-alt18:40
aignatov_10 9 8 7 6 5 4 three18:41
aignatov_2 118:42
aignatov_#endmeeting savanna18:42
*** openstack changes topic to "OpenStack meetings (alternate)"18:42
openstackMeeting ended Thu Sep 19 18:42:26 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-09-19-18.05.html18:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-09-19-18.05.txt18:42
openstackLog:            http://eavesdrop.openstack.org/meetings/savanna/2013/savanna.2013-09-19-18.05.log.html18:42
aignatov_thank you all18:42
*** markmcclain has quit IRC18:44
*** NehaV has quit IRC18:44
*** akuznetsov has quit IRC18:44
*** ErikB has joined #openstack-meeting-alt18:45
*** sacharya has quit IRC18:45
*** ylobankov has left #openstack-meeting-alt18:45
*** jmontemayor has quit IRC18:45
*** ErikB has left #openstack-meeting-alt18:46
*** mattf has left #openstack-meeting-alt18:46
*** akuznetsov has joined #openstack-meeting-alt18:47
*** ruhe has quit IRC18:47
*** NehaV has joined #openstack-meeting-alt18:48
*** nadya has quit IRC18:51
*** eankutse has quit IRC18:54
*** eankutse1 has joined #openstack-meeting-alt18:54
*** eankutse1 has quit IRC18:55
*** eankutse has joined #openstack-meeting-alt18:55
*** eankutse has quit IRC18:56
*** eankutse has joined #openstack-meeting-alt18:56
*** sreshetnyak has quit IRC18:57
*** crobertsrh has left #openstack-meeting-alt18:58
*** tanisdl has joined #openstack-meeting-alt18:58
*** tanisdl has quit IRC18:59
*** bryansd has joined #openstack-meeting-alt19:00
*** jmontemayor has joined #openstack-meeting-alt19:01
*** tanisdl has joined #openstack-meeting-alt19:04
*** lpabon has joined #openstack-meeting-alt19:09
*** sarob has joined #openstack-meeting-alt19:13
*** julim has quit IRC19:14
*** sarob has quit IRC19:15
*** markmcclain has joined #openstack-meeting-alt19:17
*** jmaron has quit IRC19:26
*** vipul is now known as vipul-away19:29
*** jmaron has joined #openstack-meeting-alt19:29
*** bryansd has left #openstack-meeting-alt19:30
*** betsy_ has joined #openstack-meeting-alt19:30
*** betsy has quit IRC19:32
*** betsy_ is now known as betsy19:32
*** julim has joined #openstack-meeting-alt19:33
*** sarob has joined #openstack-meeting-alt19:34
*** eankutse has quit IRC19:39
*** vipul-away is now known as vipul19:40
*** jmaron has quit IRC19:42
*** jmaron has joined #openstack-meeting-alt19:44
*** zhiyan has joined #openstack-meeting-alt19:50
*** nadya has joined #openstack-meeting-alt19:51
*** julim has quit IRC19:52
*** sarob has quit IRC19:54
*** sarob has joined #openstack-meeting-alt19:55
*** sarob_ has joined #openstack-meeting-alt19:59
*** sarob has quit IRC19:59
*** NehaV has quit IRC19:59
markwashglance folks: o/20:00
*** jbresnah_ has joined #openstack-meeting-alt20:00
zhiyan\o20:00
*** pcm_ has quit IRC20:00
jbresnah_wave20:00
markwash#startmeeting glance20:00
zhiyanhey jbresnah_!20:00
openstackMeeting started Thu Sep 19 20:00:52 2013 UTC and is due to finish in 60 minutes.  The chair is markwash. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: glance)"20:00
openstackThe meeting name has been set to 'glance'20:00
markwashI'll go try a little highlighting in #openstack-glance20:01
markwash3 is a quorum, I'm pretty sure :-)20:01
rosmaitafour20:02
markwashrosmaita: hi!20:02
*** IlyaE has quit IRC20:02
rosmaitahowdy!20:02
esheffieldo/20:02
markwashI've been out for most of the past week, so I'm feeling a bit out of touch20:02
zhiyanmarkwash: any topic in today's agenda?20:03
markwashbut i've been looking through the rc1 bugs and it looks like we made some decent progress20:03
markwashzhiyan: yes, I would like to do the following20:03
*** nadya_ has joined #openstack-meeting-alt20:03
markwash1) action items for resolving all current RC1 bugs20:03
markwash2) action items for reviewing tasks20:03
markwashas we slowly approach unfreezing glance20:04
markwash3) and action items for glanceclient20:04
markwashother topics?20:04
jbresnah_i have some20:04
*** jbresnah_ is now known as jbresnah20:05
*** nadya has quit IRC20:05
zhiyanmarkwash: yes, talk about design summit topic?20:05
jbresnahflavio couldnt make it but he emailed me a couple of bugs he wanted to talk about20:05
jbresnahthey might be covered in the above20:05
jbresnahand also i want to tell everyone that i am leaving red hat20:05
zhiyanjbresnah: :)20:05
jbresnahand what that will be like for me on glance etc20:05
markwashjbresnah: OK, let's make sure to work that in20:06
markwashzhiyan: sounds good, lets talk design summit topics as well20:06
markwashjbresnah: are you still going to be working on openstack stuff?20:06
jbresnahyes, but less so20:07
zhiyanmarkwash: cool. http://summit.openstack.org20:07
jbresnah:-(20:07
jbresnahi will still be a good glance citizen in terms of reviews20:07
jbresnahbut probably less development20:07
*** eankutse has joined #openstack-meeting-alt20:08
markwashI see. . well we'll be sad to see your coding contributions decrease :-(20:08
jbresnahnod20:08
markwashwith all the great fixes and features you've added in havana, for example20:08
jbresnahwas a tough call, but i will still be around20:08
jbresnahthanks!20:08
*** eankutse has quit IRC20:08
*** _ozstacker_ has joined #openstack-meeting-alt20:08
*** eankutse has joined #openstack-meeting-alt20:09
zhiyanjbresnah: have a good career to you!20:09
*** sarob_ has quit IRC20:09
jbresnahzhiyan: this is not goodbye!20:09
*** ozstacker has quit IRC20:09
*** sarob has joined #openstack-meeting-alt20:09
zhiyanjbresnah: :) of cause. (you know we talked this)20:10
*** jmontemayor has quit IRC20:10
markwashall right. . well. . I guess we should take a quick look at rc 1 bugs20:10
markwash#topic rc1 bugs20:10
*** openstack changes topic to "rc1 bugs (Meeting topic: glance)"20:10
jbresnahdo you have a link to the list of them?20:10
zhiyanhttps://launchpad.net/glance/+milestone/havana-rc120:10
markwash#link https://launchpad.net/glance/+milestone/havana-rc120:10
markwashhaha20:10
markwashtwice20:10
*** hemanth has joined #openstack-meeting-alt20:10
nikhilo/20:10
markwash7 In progress, 1 new, 5 committed20:11
jbresnahoh, this one is not real: https://bugs.launchpad.net/glance/+bug/122091920:11
markwashand I think the highest priority In Progress bugs have at least a single +220:11
jbresnahi jsut set it to invalid20:12
markwashah, okay, thanks. . I was going to ask20:12
markwashI removed the milestone then too20:12
jbresnah1213241 should be all set20:13
jbresnahjust needs review20:13
markwashof note, it appears that the blocking jenkins issue was fixed in https://bugs.launchpad.net/glance/+bug/121324120:13
jbresnahflwang and zhiyan helped me through the last issue20:13
jbresnahyeah20:13
markwash#action more core reviews of https://bugs.launchpad.net/glance/+bug/121324120:13
*** nadya_ has quit IRC20:13
markwashflwang: zhiyan: thanks so much for that! I had been looking but was completely lost20:13
*** sarob has quit IRC20:14
*** sarob_ has joined #openstack-meeting-alt20:14
zhiyanmarkwash: welcome :)20:14
markwashhttps://bugs.launchpad.net/bugs/1223516 needs another core look as well20:14
markwash#action more core reviews of https://bugs.launchpad.net/bugs/122351620:14
markwashwe have the same story with https://bugs.launchpad.net/bugs/121871220:15
markwashthat last one is metadata encryption for multiple locations20:15
markwashzhiyan: I gave my +2 this morning as I was trying to catch up on reviews20:15
zhiyanmarkwash: saw, thanks.20:15
jbresnahi'll get through some reviews this afternoon20:16
zhiyanmarkwash: for #1213241, i think jbresnah's patch is good enough to get merge IMO.20:16
zhiyanjbresnah: thank you.20:16
markwashI guess "more reviews" is the main message for those rc1 bugs20:16
jbresnahnod20:17
markwashwith one standout: https://bugs.launchpad.net/bugs/122444920:17
*** jmontemayor has joined #openstack-meeting-alt20:17
*** NehaV has joined #openstack-meeting-alt20:17
zhiyanmarkwash: humm, this one seems ttx has some different sounds, iirc,,20:17
markwashthat one depends on a change to requirements20:18
markwashwhich has been blocked somewhat20:18
zhiyanmarkwash: nod20:18
markwashokay, it looks like ttx is okay with that requirements change at this point20:18
zhiyanmarkwash: ok, seems you like copy OrderedDict from package directly ...20:19
markwashI think we really need to fix that bug20:19
markwashI'd much prefer that we get the change in to requirements20:19
markwashbut i we cant, I think copying in OrderedDict would work as a Havana fix20:19
markwashs/i we/if we/20:19
*** vipul is now known as vipul-away20:19
*** vipul-away is now known as vipul20:19
zhiyanmarkwash: and it obviously is a obviously solution..20:20
markwashanyone here have strongish objections to just copying the implementation of OrderedDict into Glance if that's what it takes to fix this bug?20:21
markwashon the assumption that we would remove it asap for the Icehouse and future releases20:21
jbresnahsorry i am not familar with the bug yet20:21
jbresnahcopy from oslo?20:21
zhiyanjbresnah: from https://pypi.python.org/pypi/ordereddict/1.1 20:21
markwashit would involve copying from a project on pypi20:21
markwashI don't think the licensing is an issue at all, we can just preserve the original license20:22
markwashbut its kinda nasty20:22
jbresnah| License :: OSI Approved :: MIT License20:22
jbresnahthose are ok for a copy?20:22
markwashjbresnah: hmm, I guess maybe I should double check20:22
zhiyanmarkwash: is there have not any chance to allow us change requirement.txt at this stage??20:23
jbresnahi am ok with the copy20:23
markwashzhiyan: its looking more and more likely we can still change requirements at this stage, but I just want to make sure people are okay with "holding their noses" while we copy and paste, if that is what is required20:24
zhiyanmarkwash: i'm ok with the copy too. thanks for explaining markwash.20:25
markwashokay great20:25
markwashI hope we don't have to take that option, but I don't think we can ship with that bug20:26
markwashsince it will make property protection ordering non deterministic20:26
jbresnahyeah20:26
zhiyanmarkwash: nod20:26
markwashwhich would mean that you might match things in the wrong order. . breaks things the same as if your iptables rules were evaluated in a random order20:26
*** NikitaKonovalov has quit IRC20:26
markwashjbresnah: did flavio have any other bug notes for us?20:27
zhiyanmarkwash: it's a critical bug obviously20:27
jbresnahyeah but first  a quick question on this one: https://review.openstack.org/#/c/45942/20:27
jbresnahi am wondering if we lose context20:27
jbresnahwe trap exceptions, create messages and then raise20:27
*** sarob_ has quit IRC20:27
markwashhmm, I wonder about that too now20:27
jbresnahwith things like ValueError, will we lose the context for that exception?20:27
jbresnahStorageFull etc are probably not a problem20:28
*** sarob has joined #openstack-meeting-alt20:28
jbresnahi hate to stall it out on that20:28
*** boris-42 has joined #openstack-meeting-alt20:29
markwashbased on a simple on the spot test, I don't think we lose context when we use a "raise" statement with no argument20:29
jbresnahoh, i mean something else20:29
markwashhttp://paste.openstack.org/show/47282/20:29
jbresnahlike, at this point in the code we know what a ValueError is caused by20:29
jbresnahbut do we up the stack?20:29
jbresnahsure, we may have the wholestack trace20:30
jbresnahand can introspect that20:30
jbresnahbut can we create sane error messages20:30
jbresnahthat go to a user20:30
jbresnahdoes that make sense?20:30
markwashI think we do still "know" further up the stack20:30
jbresnaheven for Exception and ValueError?20:30
markwashb/c we're not really changing the behavior here at all20:30
markwashif it raises before you layer in notifications, it still raises20:31
markwashI think the argument could be made that those exceptions are too general for this interface, but it seems like the semantics (too general though they may be) are intact after layering in notification20:31
jbresnahhmmm20:31
jbresnahlook at the msg = for ValueError20:32
markwashhow about we take it up in the review though. . I'm okay with a -1 :-)20:32
jbresnahsure sounds good20:32
jbresnahi will just 0 it tho20:32
*** akuznetsov has quit IRC20:32
*** sarob has quit IRC20:32
jbresnahok, so flavio was concerned with these 220:32
markwashI mean, I'm okay with a -2 as well :-) I'd just be a little sad20:32
jbresnahheh20:32
jbresnahno, this is -1 worthy nitpick at best20:33
jbresnahhttps://bugzilla.redhat.com/show_bug.cgi?id=100439820:33
jbresnahi added comments to that after flavio brought it to my attention but it would be good for others to weigh in too20:33
*** jmaron has quit IRC20:33
jbresnahhttps://bugs.launchpad.net/glance/+bug/122607820:33
jbresnahthat one seems like something we should deal with20:34
*** mestery has quit IRC20:34
jbresnahi do not fully understand the problem yet20:34
*** vipul is now known as vipul-away20:34
jbresnahbut it is a potentially big security problem20:35
markwashokay interesting. . yeah both of those look signficant20:35
markwashfor the first one, I'm wondering if its a glanceclient bug only? or is it both glanceclient and glance?20:35
jbresnahi think it is a glance bug20:35
jbresnahglance allows a client to set a bogus size value20:36
jbresnahbut really all those values are just advisory20:36
jbresnahnothing is really vetted20:36
*** sarob has joined #openstack-meeting-alt20:36
zhiyanjbresnah: for glance server side, you meaning v1 or v2 api ?20:36
jbresnahi dont see it getting fixed for H20:36
jbresnahzhiyan: i think either?20:36
jbresnahzhiyan: but i am not certain20:36
esheffieldI agree it seems more like a glance bug than glanceclient20:37
zhiyanjbresnah: iirc, v1 has checking code for that..compare http content-length with store driver returned size ..20:37
zhiyanesheffield: i think so markwash.20:37
esheffieldesp with v2 where the client is more ignorant of the options, relying on the schema more20:37
markwashhmm okay20:38
markwashokay, I marked that first bug as triaged/confirmed20:39
jbresnahzhiyan: even when --location is used?20:39
jbresnahwe should have a discussion on that bug20:39
jbresnahi posted some of my thoughts20:39
zhiyanjbresnah: yes, seems defect related with that situation, need check code deeply20:40
markwashre the second, security-related bug20:40
markwashI'm confused20:40
markwashit seems like that bug is just documenting the thing we don't like about v1 memberships20:40
jbresnahalso with add location20:40
jbresnahhow do verify size?20:40
jbresnahchecksum?20:40
jbresnahthat it is actually  a replica20:40
jbresnahthe second bug?20:40
jbresnahwell i do not really understand the problem yet20:41
jbresnahmaybe we should talk it over with flavio when he is around20:41
markwashokay, sounds good20:41
markwash#action jbresnah, flaper87, markwash discuss https://bugs.launchpad.net/glance/+bug/122607820:41
markwashokay20:41
jbresnahbut i wold like to hear your understanding of too mark20:41
jbresnahat some point anyway20:42
markwashany other bugs of note for rc1?20:42
jbresnahnot from me20:42
markwash#topic glanceclient20:42
*** openstack changes topic to "glanceclient (Meeting topic: glance)"20:42
*** lblanchard has quit IRC20:42
markwashesheffield: I saw your recent message to the list and have the review open in my browser20:43
esheffieldyes - there were a couple of minor comments that I took care of this morning20:44
*** anteaya has quit IRC20:44
markwashthat looks like the main outstanding item for v2 support20:44
esheffieldI think so20:44
markwashand it has some options for managing caching of schemas, so it seems20:45
*** lpabon has quit IRC20:45
jbresnahesheffield: i am excited about that one landing btw20:45
markwashokay, well I just wanted to check in there. I expect to do another full pass on python-glanceclient reviews soon20:45
esheffieldgreat, thanks!20:46
zhiyanjbresnah: esheffield: I believe other folks from other team will be also20:46
markwashdoes anyone have other notes for glanceclient work in the next week or so?20:46
jbresnahi dont20:46
zhiyanzhiyan: i have not20:46
zhiyanoh, markwash ^20:46
jbresnahi do have a general question as a reviewer when there is a minute20:46
markwash#topic asynchronous tasks20:47
*** openstack changes topic to "asynchronous tasks (Meeting topic: glance)"20:47
markwashwhoops20:47
markwashjbresnah: go ahead with your question20:47
jbresnahwhat can i approve/not approve?20:47
markwashI don't think there are really any restrictions at this time20:48
*** sacharya has joined #openstack-meeting-alt20:48
jbresnahok cool20:48
markwashwe should avoid breaking backwards compatibility unless we're planning a major point release20:48
*** vipul-away is now known as vipul20:48
markwashwhich we are getting close to20:48
jbresnahi am worried i will approve something in a freeze20:48
markwashno freeze for the client20:48
jbresnahoh i mean in general20:48
jbresnahglance too20:48
markwashoh20:48
markwashyeah, glance is still frozen, so only approve bugs targeted to rc120:49
markwashbut feel free if you see something important to draw some attention to it so we can approve it if needed20:49
markwashthat gives some good context for async tasks20:49
markwashwe decided to try to land async tasks very early in Icehouse, which should open in about a week20:49
markwashso there is still good reason to be doing reviews there20:50
jbresnahyeah, ok20:50
markwashas I mentioned, I was out last week, and I'd like to do a deep dive on async tasks as I catch back up20:50
jbresnahso only things referencing these bugs: https://launchpad.net/glance/+milestone/havana-rc120:50
markwashjbresnah: right20:50
markwashnikhil: can you update me on the status of async tasks?20:50
nikhilmarkwash: here20:50
nikhil:)20:51
nikhilso, we created another wip/temp repo which has all the changes asyn workers need20:51
nikhilto make reviewers' and20:51
nikhileveryone who is working on it - their job easier to maintin the patch20:52
*** RajeshMohan has quit IRC20:52
markwashsounds good. . I think you emailed me the link, can you share it here though too?20:52
nikhilit has impl for a generic class which acts like interface20:52
nikhilsure20:52
nikhiland it has filesys-filesys importer almost complete20:53
*** RajeshMohan has joined #openstack-meeting-alt20:53
nikhilmeaning there is some error on the domain proxy for a functional test which I'm resolving this week!20:53
nikhilhttps://review.openstack.org/#/c/46117/20:53
nikhilmarkwash: the plan was to make it robust and acceptable20:54
nikhiland then we can break it down and send it in?20:54
markwash#action markwash (and others!) perform early reviews with an eye towards landing https://review.openstack.org/#/c/46117/ early in Icehouse20:54
nikhilI meant to ask if that is okay20:54
nikhilthanks markwash !!20:54
*** sarob has quit IRC20:54
markwashnikhil: I think that's fine, we can talk about how to break it up best in the review notes as well20:54
markwashbut anything that makes it easier to work on for you guys is good20:54
zhiyannikhil: seems it mixed all related changes in #46177, right?20:55
*** sarob has joined #openstack-meeting-alt20:55
markwashwe have only 5 minutes left20:55
markwashand wanted to touch on design summit talks as well20:55
nikhilmarkwash: thanks20:55
nikhilzhiyan: yes20:55
nikhilthat patch has all the changes which importer and tasks api would need20:56
jbresnahi have design summit topics, but it will have to be by proxy20:56
zhiyannikhil: is it just for testing ? i mean do you still maintain other separated patchs?20:56
nikhilzhiyan: the current patches are not up to date20:56
nikhilas they were causing issues20:56
nikhilmaintaining the earlier / depency patched by fei20:57
nikhilpatches**20:57
zhiyannikhil: so #46177 is latest code right?20:57
nikhilyes20:57
zhiyannikhil: ok, got it.20:57
*** RajeshMohan has quit IRC20:57
zhiyannikhil: thanks20:57
*** RajeshMohan has joined #openstack-meeting-alt20:57
markwash#topic design summit topics20:57
*** openstack changes topic to "design summit topics (Meeting topic: glance)"20:57
nikhilzhiyan: the MP to be reviewed is https://review.openstack.org/#/c/46117/20:57
nikhiloops20:58
zhiyanmarkwash: jbresnah yes do you think we'd better talk about design seesion topic?20:58
markwashyeah, with the little time we have left20:58
zhiyanmarkwash: seems we have not one proposal in the list20:58
jbresnahzhiyan: should we throw them out here or is the web site for submission available yet?20:58
nikhilI've one but would not be able to make it to the summit20:58
* markwash has forgotten where we are on that front, since we didn't have a project meeting this week20:59
zhiyanmarkwash: when you cut them up? i mean from summit.openstack.org?20:59
*** sarob has quit IRC20:59
markwashI've got one or two ideas I've been kicking around that I'd like to discuss at the summit as well20:59
zhiyanmarkwash: do you think we can just put something we want, and review together later?20:59
markwashoh yeah, looks like its opened up21:00
markwashyou guys can submit whatever you feel like there21:00
jbresnahzhiyan: i like that idea21:00
jbresnahcool21:00
zhiyanoh, seems time up..21:00
markwashyeah, I think we're out of time21:00
zhiyanmarkwash: will ping you later21:00
zhiyanoff line21:00
markwashthanks everybody21:00
jbresnahthanks!21:01
zhiyanthanks !21:01
markwash#action submit your summit topics at http://summit.openstack.org !21:01
markwash#endmeeting21:01
*** openstack changes topic to "OpenStack meetings (alternate)"21:01
openstackMeeting ended Thu Sep 19 21:01:21 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-09-19-20.00.html21:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-09-19-20.00.txt21:01
openstackLog:            http://eavesdrop.openstack.org/meetings/glance/2013/glance.2013-09-19-20.00.log.html21:01
*** pdmars has quit IRC21:01
*** RajeshMohan has quit IRC21:01
*** RajeshMohan has joined #openstack-meeting-alt21:02
*** jmaron has joined #openstack-meeting-alt21:03
*** jmaron has quit IRC21:08
*** boris-42 has quit IRC21:09
*** boris-42 has joined #openstack-meeting-alt21:10
*** sarob has joined #openstack-meeting-alt21:15
*** sarob has quit IRC21:16
*** sarob has joined #openstack-meeting-alt21:17
*** sarob has quit IRC21:22
*** markwash has left #openstack-meeting-alt21:24
*** NikitaKonovalov has joined #openstack-meeting-alt21:27
*** alazarev has quit IRC21:28
*** NikitaKonovalov has quit IRC21:31
*** NehaV has quit IRC21:34
*** mestery has joined #openstack-meeting-alt21:37
*** mestery has joined #openstack-meeting-alt21:38
*** jmaron has joined #openstack-meeting-alt21:39
*** pcm_ has joined #openstack-meeting-alt21:40
*** pcm_ has quit IRC21:41
*** pcm_ has joined #openstack-meeting-alt21:41
*** jtomasek has quit IRC21:41
*** jbresnah has left #openstack-meeting-alt21:42
*** NehaV has joined #openstack-meeting-alt21:43
*** betsy has quit IRC21:44
*** jcoufal has quit IRC21:45
*** HenryG has joined #openstack-meeting-alt21:50
*** vipul is now known as vipul-away21:56
*** markmcclain has quit IRC21:59
*** enikanorov-w has quit IRC22:00
*** enikanorov-w has joined #openstack-meeting-alt22:01
*** sungju has joined #openstack-meeting-alt22:02
*** zhiyan has quit IRC22:07
*** vipul-away is now known as vipul22:12
*** sarob has joined #openstack-meeting-alt22:16
*** sarob has quit IRC22:20
*** eankutse has quit IRC22:22
*** sacharya has quit IRC22:28
*** NehaV has quit IRC22:33
*** markmcclain has joined #openstack-meeting-alt22:34
*** esker has quit IRC22:34
*** esker has joined #openstack-meeting-alt22:35
*** esker has quit IRC22:39
*** markmcclain has quit IRC22:40
*** bdpayne has quit IRC22:41
*** demorris has quit IRC22:44
*** sarob has joined #openstack-meeting-alt22:46
*** IlyaE has joined #openstack-meeting-alt22:46
*** jergerber has quit IRC22:48
*** sarob has quit IRC22:51
*** sarob has joined #openstack-meeting-alt22:53
*** mestery has quit IRC23:00
*** markmcclain has joined #openstack-meeting-alt23:01
*** bdpayne has joined #openstack-meeting-alt23:04
*** bdpayne has quit IRC23:04
*** noslzzp has quit IRC23:04
*** jmontemayor has quit IRC23:07
*** amytron has quit IRC23:14
*** redthrux has left #openstack-meeting-alt23:14
*** markmcclain has quit IRC23:23
*** boris-42 has quit IRC23:23
*** pcm_ has quit IRC23:26
*** anteaya has joined #openstack-meeting-alt23:29
*** anteaya has quit IRC23:36
*** sacharya has joined #openstack-meeting-alt23:37
*** rnirmal has quit IRC23:43
*** tanisdl has quit IRC23:43
*** kebray has quit IRC23:46
*** sungju has quit IRC23:49
*** jmaron has quit IRC23:49

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