Wednesday, 2013-01-23

*** nati_ueno has quit IRC00:00
*** diogogmt has quit IRC00:00
*** nati_ueno has joined #openstack-meeting00:00
*** danwent has joined #openstack-meeting00:00
*** vipul is now known as vipul|away00:01
*** dolphm has joined #openstack-meeting00:02
*** henrynash has quit IRC00:04
*** yaguang has quit IRC00:05
*** markvoelker has joined #openstack-meeting00:06
*** otherwiseguy has quit IRC00:08
*** dtalton has quit IRC00:09
*** dwcramer has joined #openstack-meeting00:09
*** markvoelker has quit IRC00:10
*** dolphm has quit IRC00:11
*** dolphm has joined #openstack-meeting00:14
*** vipul|away is now known as vipul00:15
*** cp16net is now known as cp16net|away00:17
*** crank has joined #openstack-meeting00:22
*** ryanpetrello has joined #openstack-meeting00:26
*** markmcclain has quit IRC00:27
*** salv-orlando has quit IRC00:27
*** dabo has quit IRC00:27
*** dabo has joined #openstack-meeting00:28
*** cdub_ has joined #openstack-meeting00:29
*** dolphm has quit IRC00:33
*** jgriffith has quit IRC00:33
*** eharney has quit IRC00:34
*** dwcramer has quit IRC00:35
*** lloydde has quit IRC00:36
*** kaganos has joined #openstack-meeting00:38
*** alexpilotti has quit IRC00:41
*** dolphm has joined #openstack-meeting00:41
*** rnirmal has quit IRC00:44
*** lcheng has quit IRC00:45
*** fnaval has joined #openstack-meeting00:47
*** dwcramer has joined #openstack-meeting00:48
*** Nachi has joined #openstack-meeting00:54
*** juice_ has quit IRC00:57
*** nati_ueno has quit IRC00:58
*** lloydde has joined #openstack-meeting00:58
*** jcmartin has quit IRC01:01
*** mrodden has quit IRC01:01
*** lbragstad has quit IRC01:02
*** Nachi has quit IRC01:03
*** nati_ueno has joined #openstack-meeting01:04
*** markvoelker has joined #openstack-meeting01:06
*** nati_ueno has quit IRC01:07
*** nati_ueno has joined #openstack-meeting01:08
*** lloydde has joined #openstack-meeting01:10
*** otherwiseguy has joined #openstack-meeting01:10
*** markvoelker has quit IRC01:11
*** gyee has quit IRC01:14
*** dolphm has quit IRC01:16
*** Edward_Zhang has joined #openstack-meeting01:16
*** mrodden has joined #openstack-meeting01:19
*** zhuadl has joined #openstack-meeting01:25
*** jcmartin has joined #openstack-meeting01:26
*** dolphm has joined #openstack-meeting01:27
*** cp16net|away is now known as cp16net01:27
*** lloydde has quit IRC01:32
*** bdpayne has quit IRC01:35
*** mrodden has quit IRC01:37
*** cdub_ has quit IRC01:40
*** AlanClark has joined #openstack-meeting01:41
*** cdub_ has joined #openstack-meeting01:44
*** jgriffith has joined #openstack-meeting01:46
*** galthaus has joined #openstack-meeting01:49
*** lbragstad has joined #openstack-meeting01:53
*** galthaus has quit IRC01:54
*** stevemar has joined #openstack-meeting01:55
*** gabrielhurley has quit IRC01:59
*** kaganos has quit IRC02:05
*** danwent has quit IRC02:05
*** markvoelker has joined #openstack-meeting02:07
*** galthaus has joined #openstack-meeting02:11
*** markvoelker has quit IRC02:11
*** galthaus has quit IRC02:15
*** maurosr has quit IRC02:21
*** ryanpetrello has quit IRC02:22
*** ryanpetrello has joined #openstack-meeting02:26
*** hemna has quit IRC02:27
*** novas0x2a|laptop has quit IRC02:28
*** stevemar has quit IRC02:32
*** yuanz has quit IRC02:34
*** AlanClark has quit IRC02:36
*** sdake_z has quit IRC02:44
*** alrs has quit IRC02:46
*** alrs has joined #openstack-meeting02:50
*** roaet-away is now known as roaet02:52
*** ryanpetrello has quit IRC02:54
*** ryanpetrello has joined #openstack-meeting02:55
*** danwent has joined #openstack-meeting03:00
*** ryanpetrello has joined #openstack-meeting03:01
*** nati_ueno has quit IRC03:01
*** cdub_ has quit IRC03:01
*** nati_ueno has joined #openstack-meeting03:01
*** AlanClark has joined #openstack-meeting03:02
*** ryanpetrello has quit IRC03:03
*** ryanpetrello has joined #openstack-meeting03:05
*** markvoelker has joined #openstack-meeting03:07
*** vishy is now known as vishy_zz03:07
*** dolphm has quit IRC03:08
*** jcmartin has quit IRC03:09
*** ryanpetrello has quit IRC03:09
*** nati_ueno has quit IRC03:10
*** markvoelker has quit IRC03:12
*** Mandell has quit IRC03:13
*** ryanpetrello has joined #openstack-meeting03:13
*** dolphm has joined #openstack-meeting03:13
*** cp16net is now known as cp16net|away03:13
*** cp16net|away is now known as cp16net03:14
*** ryanpetrello has quit IRC03:14
*** ryanpetrello has joined #openstack-meeting03:15
*** galthaus has joined #openstack-meeting03:18
*** jcmartin has joined #openstack-meeting03:42
*** vishy_zz is now known as vishy03:45
*** nati_ueno has joined #openstack-meeting03:54
*** adjohn has quit IRC04:04
*** markvoelker has joined #openstack-meeting04:07
*** lloydde has joined #openstack-meeting04:12
*** markvoelker has quit IRC04:12
*** Edward_Zhang has quit IRC04:13
*** zhuadl has quit IRC04:14
*** garyk has quit IRC04:19
*** nati_ueno has quit IRC04:20
*** nati_ueno has joined #openstack-meeting04:21
*** AlanClark has quit IRC04:29
*** martine_ has quit IRC04:31
*** juice has joined #openstack-meeting04:39
*** beagles has quit IRC04:40
*** Edward_Zhang has joined #openstack-meeting04:41
*** danwent has quit IRC04:42
*** danwent has joined #openstack-meeting04:47
*** garyk has joined #openstack-meeting04:47
*** zhuadl has joined #openstack-meeting04:58
*** jcmartin has quit IRC05:04
*** markvoelker has joined #openstack-meeting05:08
*** Mandell has joined #openstack-meeting05:09
*** Nachi has joined #openstack-meeting05:09
*** ewindisch has quit IRC05:10
*** nati_ueno has quit IRC05:12
*** markvoelker has quit IRC05:12
*** dolphm has quit IRC05:13
*** adjohn has joined #openstack-meeting05:15
*** lloydde has quit IRC05:24
*** ewindisch has joined #openstack-meeting05:26
*** acemid has joined #openstack-meeting05:41
*** acemid has quit IRC05:43
*** nati_ueno has joined #openstack-meeting05:46
*** acemid has joined #openstack-meeting05:46
*** topol has joined #openstack-meeting05:47
*** Nachi has quit IRC05:47
*** yuanz has joined #openstack-meeting05:52
*** stevebaker has quit IRC05:55
*** MarkA3 is now known as MarkAtwood05:55
*** Mandell has quit IRC06:01
*** Mandell has joined #openstack-meeting06:03
*** koolhead17 has joined #openstack-meeting06:08
*** markvoelker has joined #openstack-meeting06:08
*** nati_ueno has quit IRC06:08
*** topol has quit IRC06:11
*** markvoelker has quit IRC06:13
*** otherwiseguy has quit IRC06:19
*** Mandell has quit IRC06:26
*** shang has joined #openstack-meeting06:26
*** Mandell has joined #openstack-meeting06:27
*** Mandell has quit IRC06:31
*** galthaus has quit IRC06:32
*** lloydde has joined #openstack-meeting06:35
*** koolhead17 has quit IRC06:36
*** ewindisch has quit IRC06:38
*** lloydde has quit IRC06:39
*** jhenner has joined #openstack-meeting06:45
*** acemid has quit IRC06:46
*** acemid has joined #openstack-meeting06:46
*** MarkAtwood has quit IRC06:47
*** Mandell has joined #openstack-meeting06:49
*** morganfainberg has quit IRC06:50
*** psedlak has quit IRC06:51
*** koolhead17 has joined #openstack-meeting06:59
*** adjohn has quit IRC07:05
*** adjohn has joined #openstack-meeting07:05
*** markvoelker has joined #openstack-meeting07:09
*** zhuadl has quit IRC07:10
*** ewindisch has joined #openstack-meeting07:10
*** adjohn has quit IRC07:10
*** markvoelker has quit IRC07:13
*** zhuadl has joined #openstack-meeting07:14
*** mrunge has joined #openstack-meeting07:16
*** koolhead17 has quit IRC07:18
*** ryanpetrello has quit IRC07:19
*** nati_ueno has joined #openstack-meeting07:36
*** morganfainberg has joined #openstack-meeting07:39
*** sdake_z has joined #openstack-meeting07:43
*** bencherian has quit IRC07:50
*** psedlak has joined #openstack-meeting07:51
*** juice has quit IRC07:54
*** EmilienM has joined #openstack-meeting07:58
*** rafaduran has joined #openstack-meeting07:59
*** jhenner has quit IRC08:00
*** ewindisch has quit IRC08:00
*** bencherian has joined #openstack-meeting08:09
*** markvoelker has joined #openstack-meeting08:09
*** henrynash has joined #openstack-meeting08:12
*** markvoelker has quit IRC08:14
*** henrynash has quit IRC08:16
*** ijw has joined #openstack-meeting08:19
*** bencherian has quit IRC08:19
*** shang has quit IRC08:21
*** shang has joined #openstack-meeting08:22
*** ewindisch has joined #openstack-meeting08:32
*** ijw has quit IRC08:37
*** ijw has joined #openstack-meeting08:37
*** ijw has quit IRC08:43
*** ewindisch has quit IRC08:50
*** Mandell has quit IRC08:53
*** ttx has quit IRC08:53
*** ttx has joined #openstack-meeting08:54
*** ttx has joined #openstack-meeting08:54
*** danwent_ has joined #openstack-meeting08:54
*** danwent has quit IRC08:56
*** danwent_ is now known as danwent08:56
*** almaisan-away is now known as al-maisan08:57
*** danwent_ has joined #openstack-meeting09:00
*** danwent has quit IRC09:03
*** danwent_ is now known as danwent09:03
*** markvoelker has joined #openstack-meeting09:10
*** markvoelker has quit IRC09:14
*** shang has quit IRC09:15
*** ijw has joined #openstack-meeting09:16
*** danwent has quit IRC09:18
*** shang has joined #openstack-meeting09:20
*** cdub_ has joined #openstack-meeting09:27
*** cdub_ has quit IRC09:32
*** darraghb has joined #openstack-meeting09:32
*** yamahata_ has joined #openstack-meeting09:33
*** jhenner has joined #openstack-meeting09:38
*** derekh has joined #openstack-meeting09:54
*** morganfainberg has quit IRC10:01
*** morganfainberg has joined #openstack-meeting10:01
*** zhuadl has quit IRC10:02
*** zhuadl has joined #openstack-meeting10:03
*** vishy is now known as vishy_zz10:06
*** markvoelker has joined #openstack-meeting10:10
*** yamahata_ has quit IRC10:11
*** markvoelker has quit IRC10:14
*** yamahata_ has joined #openstack-meeting10:17
*** zhuadl has quit IRC10:33
*** Edward_Zhang has quit IRC10:37
*** vkmc has joined #openstack-meeting10:51
*** shang has quit IRC10:57
*** shang has joined #openstack-meeting10:58
*** maurosr has joined #openstack-meeting10:59
*** shengjie has quit IRC11:03
*** markvoelker has joined #openstack-meeting11:11
*** zhuadl has joined #openstack-meeting11:11
*** Edward_Zhang has joined #openstack-meeting11:15
*** kmartin has quit IRC11:15
*** markvoelker has quit IRC11:16
*** ijw has quit IRC11:32
*** spn has quit IRC11:41
*** alexpilotti has joined #openstack-meeting11:41
*** spn has joined #openstack-meeting11:45
*** BobBall is now known as BobBallAway11:49
*** Edward_Zhang has quit IRC11:56
*** zhuadl has quit IRC11:57
*** Edward_Zhang has joined #openstack-meeting12:10
*** martine has joined #openstack-meeting12:24
*** MarkAtwood has joined #openstack-meeting12:26
*** zhuadl has joined #openstack-meeting12:27
*** EmilienM has quit IRC12:28
*** MarkAtwood has quit IRC12:30
*** shang has quit IRC12:32
*** MarkAtwood has joined #openstack-meeting12:35
*** MarkAtwood has quit IRC12:35
*** Edward_Zhang has quit IRC12:39
*** zhuadl has quit IRC12:39
*** EmilienM has joined #openstack-meeting12:42
*** henrynash has joined #openstack-meeting12:53
*** henrynash has quit IRC12:57
*** shang has joined #openstack-meeting13:04
*** shang has quit IRC13:05
*** shang has joined #openstack-meeting13:05
*** shang has quit IRC13:06
*** shang has joined #openstack-meeting13:07
*** shang has quit IRC13:10
*** dwcramer has quit IRC13:15
*** dprince has joined #openstack-meeting13:24
*** brianr_ has left #openstack-meeting13:47
*** brianr_ has joined #openstack-meeting13:47
*** radez_g0n3 is now known as radez13:52
*** galthaus has joined #openstack-meeting13:53
*** galthaus has quit IRC13:59
*** sandywalsh has joined #openstack-meeting14:06
*** ayoung is now known as ayoung-meeting14:11
*** dwcramer has joined #openstack-meeting14:23
*** joesavak has joined #openstack-meeting14:30
*** al-maisan is now known as almaisan-away14:30
*** ryanpetrello has joined #openstack-meeting14:32
*** woodspa has joined #openstack-meeting14:32
*** fnaval has quit IRC14:35
*** annegentle has joined #openstack-meeting14:37
*** yaguang has joined #openstack-meeting14:38
*** dosaboy has joined #openstack-meeting14:38
*** markvoelker has joined #openstack-meeting14:38
*** frankm has joined #openstack-meeting14:39
*** EmilienM has quit IRC14:41
*** markvoelker has quit IRC14:43
*** mtreinish has joined #openstack-meeting14:44
*** reed has joined #openstack-meeting14:47
*** roaet is now known as roaet-away14:53
*** roaet-away is now known as roaet14:53
*** reed has quit IRC14:54
*** EmilienM has joined #openstack-meeting14:56
*** EmilienM has quit IRC14:57
*** EmilienM has joined #openstack-meeting14:58
*** galthaus has joined #openstack-meeting14:58
*** mrodden has joined #openstack-meeting14:59
*** markvan has joined #openstack-meeting14:59
*** fnaval has joined #openstack-meeting14:59
*** markvan has quit IRC15:00
*** markvan has joined #openstack-meeting15:00
*** dwcramer has quit IRC15:03
*** diogogmt has joined #openstack-meeting15:03
*** barruf has joined #openstack-meeting15:04
barrufhi15:04
barrufno one?15:05
*** radez is now known as radez_g0n315:08
*** ewindisch has joined #openstack-meeting15:08
*** radez_g0n3 is now known as radez15:12
*** EmilienM has left #openstack-meeting15:12
barrufhttp://ced85.wordpress.com15:12
barrufif someone is getting bored like me...15:12
*** EmilienM has joined #openstack-meeting15:13
barrufnice to see15:13
*** rnirmal has joined #openstack-meeting15:13
*** markmcclain has joined #openstack-meeting15:14
barrufhi15:15
*** esker has joined #openstack-meeting15:15
*** topol has joined #openstack-meeting15:16
barrufanyone is gettign bored?15:16
*** eharney has joined #openstack-meeting15:16
barrufand enjoys to see some paints?15:17
barrufhttp://ced85.wordpress.com15:17
*** barruf has quit IRC15:17
*** blamar has joined #openstack-meeting15:18
*** shang__ has joined #openstack-meeting15:20
*** rushiagr1 has joined #openstack-meeting15:21
*** lbragstad has quit IRC15:22
*** Mandell has joined #openstack-meeting15:24
*** ewindisch has quit IRC15:24
*** beagles has joined #openstack-meeting15:27
*** matelakat has joined #openstack-meeting15:31
*** diogogmt has quit IRC15:34
*** lloydde has joined #openstack-meeting15:35
*** vkmc_ has joined #openstack-meeting15:35
*** lbragstad has joined #openstack-meeting15:37
*** vkmc has quit IRC15:37
*** vkmc_ is now known as vkmc15:38
*** markvoelker has joined #openstack-meeting15:39
*** reed has joined #openstack-meeting15:43
*** markvoelker has quit IRC15:44
*** AlanClark has joined #openstack-meeting15:47
*** bvibhu has joined #openstack-meeting15:48
*** bdpayne has joined #openstack-meeting15:49
*** reed has quit IRC15:49
*** lloydde has quit IRC15:51
*** garyTh has joined #openstack-meeting15:52
*** pschaef has joined #openstack-meeting15:53
*** Mandell has quit IRC15:53
*** shang__ has quit IRC15:54
*** dwcramer has joined #openstack-meeting15:54
*** otherwiseguy has joined #openstack-meeting15:57
*** smulcahy has joined #openstack-meeting15:57
*** xyang_ has joined #openstack-meeting15:57
*** bswartz has joined #openstack-meeting15:58
*** jsavak has joined #openstack-meeting15:58
jgriffithI see most cinder folks lurking already :)15:59
* DuncanT tries not to look suspicious15:59
jgriffith#startmeeting cinder16:00
openstackMeeting started Wed Jan 23 16:00:01 2013 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
*** bencherian has joined #openstack-meeting16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
*** joesavak has quit IRC16:00
*** kmartin has joined #openstack-meeting16:00
jgriffithLooks like we're missing winston and thingee...16:00
*** blamar_ has joined #openstack-meeting16:00
*** blamar has quit IRC16:00
*** blamar_ is now known as blamar16:00
jgriffithDuncanT: Do you want to start or would you prefer to wait for Winston and Mike?16:00
jgriffithhmmm....16:01
DuncanTI can start... if you think they'll have opinions then I can postpone til they turn up16:01
jgriffithFair16:01
jgriffith#topic snapshots and backups etc etc16:01
*** openstack changes topic to "snapshots and backups etc etc (Meeting topic: cinder)"16:01
jgriffithDuncanT: How's that for a segway :)16:01
*** JM1 has joined #openstack-meeting16:01
JM1hi16:01
DuncanTSo my first question is snapshots and their lifecycle .v. the volume they came from (and go to)16:02
*** ayoung-meeting is now known as ayoung16:02
* jgriffith ducks... this always gets messy :)16:02
DuncanTAt the moment, if you create vol1, snap it to snap1, delete vol1 then try to clone snap1, badness happens16:02
jgriffithActually right now you can't do that16:02
DuncanTIt doesn't appear to stop me16:03
JM1the vol delete command complains that the vol is in use16:03
rushiagr1jgriffith: exactly, you arent alowd to delete vol if snap exist, i guess16:03
*** rushiagr1 is now known as rushiagr16:03
*** markvan has quit IRC16:03
jgriffithYou shouldn't be able to16:03
jgriffithIf you can that's a bug16:03
jgriffithLVM will have a fit16:03
*** jaypipes has quit IRC16:03
DuncanTOh, maybe I've too many hacks in there, I'll try again on devstack later16:03
*** jbrogan has joined #openstack-meeting16:03
jgriffithDuncanT: If it does, file a bug :)16:04
DuncanTI want to be able to, either way16:04
jgriffitherrr.... I knew you were going to say that16:04
jgriffithI just don't understand the big advantage of this16:04
*** ollie1 has joined #openstack-meeting16:04
guitarzanjgriffith: we want to be able to as well16:05
*** ollie1 has left #openstack-meeting16:05
guitarzan:)16:05
DuncanTCustomers who pay for disk space16:05
jgriffithEspecially once we get backup to swift or xxxx in16:05
bswartzI'm here16:05
* jgriffith is always in the minority!16:05
*** hub_cap has joined #openstack-meeting16:05
guitarzanhistory, snapshots aren't snapshots, they're backups16:05
*** winston-d_ has joined #openstack-meeting16:05
guitarzanbut that's another topic16:05
DuncanTIf you want to keep a golden image around for fast instance creation, you probably don't want to pay for the space twice16:05
*** ollie1 has joined #openstack-meeting16:05
xyang_I don't think you should delete vol when it has a snapshot16:05
jgriffithDuncanT: sure, so do a clone16:05
DuncanTYou /could/ use a backup, but they are slow16:06
jgriffith:)16:06
*** vishy_zz is now known as vishy16:06
jgriffithNot as slow as LVM snapshots :)16:06
DuncanTI'm not running LVM ;-)16:06
smulcahywe also allow the creation of volumes from volumes (is that what people mean by a clone?)16:06
jgriffithsmulcahy: yup16:06
DuncanTsmulcahy: That is the new clone interface, yes16:06
jgriffithOk, seems I'm finally going to have to give in on this one16:07
DuncanTClone is a possibility, but I don't see a strong reason for the limitations of snapshots, beyond LVM suckage16:07
bvibhuHow about -force option? As long as the user knows what he/she is doing.16:07
DuncanT(and it works on amazon)16:08
jgriffithbut I still say it has to be consistent behavior for ALL drivers16:08
jgriffithDuncanT: Well I agree to a point16:08
jgriffithbut really tht was the WHOLE reason I did clones16:08
DuncanTShould need to be a force option16:08
*** Navneet has joined #openstack-meeting16:08
DuncanTShouldn't. rather16:08
*** AlanClark has quit IRC16:09
guitarzanI think volume->snap dependency is completely driver dependent16:09
DuncanTclones loose the read-only-ness  though16:09
NavneetHello every one...I am Navneet from NetApp16:09
jgriffithguitarzan: yes, it is but I want that dependency abstracted out16:09
bswartzhi navneet16:09
guitarzanabstracted out?16:09
guitarzanhow so?16:09
guitarzanmorning Navneet16:09
JM1I agree with DuncanT that immutability of a snap is an important property16:09
bswartzjgriffith: how about making snapshot dependency on volumes a driver capability that can be reported back?16:10
Navneetbswartz: hi ben16:10
*** thingee has joined #openstack-meeting16:10
jgriffithIn terms of I don't want our api to be "if this back-end you can do this, if that back-end you can do that"16:10
JM1when then entity is immutable, you know precisely the stat of your golden image16:10
JM1state*16:10
Navneetgood morning huitarzan16:10
DuncanTbswartz: driver capability reporting is another subject I'd like to bring up ;-)16:10
guitarzanjgriffith: but it already is16:10
guitarzanour driver doesn't support clone16:10
guitarzansomeone elses does16:10
jgriffithRight but where this is going I tihnk somebody is going to suggest changing that :)16:10
DuncanTclone is not (yet) supported by most drivers16:11
guitarzanbut you can't force me to implement it16:11
jgriffithala "allow delete volumes with snaps on *some* back-ends"16:11
xyang_we support it16:11
guitarzanI guess I don't see the problem16:11
bswartzjgriffith: it sounds like you're arguing for homogeneity and against driver capabilities16:11
jgriffithbswartz: +116:11
JM1what if generic code supported some form of refcounting?16:12
jgriffithat least in the core api calls16:12
*** jaypipes has joined #openstack-meeting16:12
bswartzthe downside with homogeneity is that it impedes progress16:12
DuncanTWe were talking about what the minimum feature set for a driver to be accepted is last week16:12
guitarzanif uncle rackspace decides that it really wants independent snapshots (and our customers definitely do) I'd have to just fork/patch cinder api to allow it16:12
JM1I mean, one could mark a volume for deletion, and space could be reclaimed when possible, depending on the driver capabilities16:13
DuncanTSame. We already support it (viz a  bug found last week) on hpcloud16:13
jgriffithalright, I'm going to loose this debate so no use continuing16:13
JM1either immediately, or when the last snap is deleted16:13
jgriffithWe can go that route if folks would like16:13
jgriffithI still don't like it, and don't understand WTF we have clones for then16:13
guitarzanwell, I'm just saying that the product specifies the features16:13
jgriffithSorry for the language, I think when it acronyms it's ok though right? :)16:14
guitarzanyes :)16:14
DuncanTjgriffith: If we do read-only volumes in future, we can redo most of the snapshot capabilites with them16:14
bswartzjgriffith: clones can be faster/more efficient that snapshot+create_vol_from_snapshot16:14
jgriffithguitarzan: Sure, but how is that communicated to the end user?16:14
guitarzanin our product documentation16:14
JM1jgriffith: I thought clones were cheap writable copies of a volume, while snaps were cheap immutable copies16:14
guitarzanopenstack is just a means to an end16:14
jgriffithThe end user shoudln't know aything about what the back-end is16:14
jgriffithJM1: yes16:14
DuncanTI agree that, in order for this feature to be merged, it should be made to work on the the LVM backend (at a minimum) in some sensible manner16:15
winston-d_JM1: i like your definition16:15
jgriffithguitarzan: DuncanT or are you suggesting it's a global config and admin beware if they're back-end supports it or not?16:15
jgriffithDuncanT: Yeah, that can be done16:15
DuncanTjgriffith: I'd like the drivers to report it, ideally, rather than needing flags, but yeah16:16
jgriffithDuncanT: but that's what I don't like16:16
*** vkmc has quit IRC16:16
guitarzanI'm ok with either choice16:16
jgriffithDuncanT: So if some provider has multiple back-ends16:16
*** avishay has joined #openstack-meeting16:16
jgriffithone supports it and one doesnt16:16
avishayhi sorry im late16:16
jgriffithhow does the user know what to expect?16:16
jgriffithThe end user that is16:16
guitarzanthat's certainly a complication16:16
xyang_I prefer drivers to report it16:16
jgriffithJust run it and see if it fails16:16
DuncanTjgriffith: Ideally I'd make LVM able to do create-from-snap-of-deleted-volume by some manner16:16
DuncanTjgriffith: Possibly by doing some clone magic behind the scenes16:17
jgriffithDuncanT: Sure, but back up to my issue with different back-ends having different behavior16:17
DuncanTjgriffith: I can't do that for all backends though16:17
jgriffithDuncanT: right16:17
*** john5223 has joined #openstack-meeting16:17
DuncanTWe already have that with clone;16:17
jgriffithOk, we're on the same page16:17
*** diogogmt has joined #openstack-meeting16:17
jgriffithhaha!!!!16:18
DuncanTIf I use e.g. solidfire and bock, one supports clone, one doesn't16:18
jgriffithWell get clones added to bock already :)16:18
Navneetif every backend uses clone it can be done16:18
DuncanTIt's on the list16:18
jgriffithThere.. problem solved :)16:18
xyang_we shouldn't force all drivers to support delete vol with snapshot16:18
DuncanTBut going forward, some drivers will always lag others16:18
DuncanTIt is going to happen the minute you add a new feature to the driver16:19
DuncanTSome mechanism to manage that seems sensible16:19
JM1then you could have a slow fallback strategy for said new feature16:19
xyang_clone support is different.  If it is not supported by a driver, mark it not implemented.16:19
xyang_for the force flag to work, that's is very specific.16:19
DuncanTAnd since some drivers have different abilities (like snap/clone/delete not needing to be run on the volume node 'owning' the volume), a using the same mechanism to express capabilities would be ncie16:20
*** jcmartin has joined #openstack-meeting16:20
jgriffithDuncanT: sure but major things like "deleting" a volume should work the same always IMO16:20
*** cp16net is now known as cp16net|away16:20
jgriffithI just think it's bad user experience to sometimes be able to delete a volume and sometimes not and never knowing why16:21
DuncanTThe advantage of a driver expressing capabilities means you can test in API and give back a sensible error message, rather than silent failure like you get with raise NotImplementedException16:21
jgriffithJust give your customers free or cheap snaps, you're not using any real space anyway :)16:21
jgriffithDuncanT: Sure but the end user doesn't see that16:21
guitarzanbut the volume is expensive, and they don't want it anymore!16:22
avishaywhat's the use case for this feature anyway?16:22
jgriffithThe end user just knows this volume can delete, but this one can't16:22
JM1if you have cheap snaps, the cost of keeping the volume around should be low16:22
jgriffithguitarzan: I know.. I hear ya16:22
DuncanTjgriffith: If we add a get_capabilites call to the driver, the API can give some explaination why, rather than silent failure16:22
jgriffithLike I said, you guys are going to win on this, I'm just saying there's a major concern IMO16:22
JM1DuncanT: that can make higher-level automation tedious16:23
jgriffithDuncanT: I understand that16:23
DuncanTJM1: Silent failures make it worse!16:23
guitarzanJM1: how so?16:23
JM1DuncanT: I never pushed for silent failures :)16:23
guitarzanwe're not giving our customers much credit here... they're going to know what product they're buying16:23
xyang_are we talking about a force flag in clone volume or delete volume?  that is different16:23
jgriffithxyang_: that's diff16:24
jgriffithxyang_: We're talking about being able to delete a vol that has a snap on "some" back-ends that support it16:24
* jgriffith thinks it needs to be all or nothing16:24
DuncanTI'd like to push towards fixing up all drivers to support the facility where possible, just like clone, but having a mechanism to express to the user where that hasn't been done yet / is impossible is also good to have16:24
xyang_a force flag in delete volume makes sense16:24
DuncanTforce flag is meaningless though16:25
jgriffithxyang_: We have a force flag16:25
JM1guitarzan: well what if you mix different backends? I think it's planned16:25
jgriffithand it doesn't have anything to do with the problem here16:25
xyang_ok16:25
DuncanTIf your backend doesn't support it, what is --force supposed to do?16:25
guitarzanJM1: I personally think that's less likely than others seem to think16:25
guitarzanDuncanT: silently fail!16:25
DuncanTguitarzan: Silent failures bad. Worse than just about anything else IMO16:25
guitarzansorry, couldn't help it :)16:26
*** ewindisch has joined #openstack-meeting16:26
guitarzananyway, this horse is dead16:26
DuncanTI'll code up a concrete patch and get comments then, I think16:26
DuncanTIt sounds like at least some people agree with me16:26
guitarzanDuncanT: excellent, I'd like to see it16:26
jgriffithhaha16:26
jgriffithguitarzan: dead horses16:27
jgriffithDuncanT: Just for the record, I don't disagreee with you, I just don't like different behaviors16:27
DuncanTYou've heard about our burgers, right? We can make good use of dead horses16:27
jgriffithbut alas, I'll approve the patch16:27
jgriffithhey now... remember who you're talking to16:28
jgriffith:)16:28
jgriffithUs horsey people are funy about that sort of thing16:28
*** jog0 has joined #openstack-meeting16:28
DuncanTjgriffith: I'll try to fix up can't-do-clone error reporting in the same patch16:28
DuncanTTalk to Tesco about the horses, not me16:28
JM1ah, horse breeders vs. horse eaters, always funny to watch :)16:28
jgriffithhaha16:29
Navneet:)16:29
*** rushiagr1 has joined #openstack-meeting16:29
jgriffithOk... DuncanT I think you had another topic?16:29
*** mikal has quit IRC16:29
*** vkmc has joined #openstack-meeting16:29
DuncanTCapability reporting, but I think that will fall out in the same patch then get extended...16:30
DuncanTMulti AZ was my next one16:30
jgriffithDuncanT: I would prefer it's a seperate patch16:30
winston-d_jgriffith: +116:30
DuncanTjgriffith: Sure, ok, same patch series16:30
*** gyee has joined #openstack-meeting16:30
jgriffithsure16:30
jgriffithPlans to expose that as an admin extension?16:30
*** rushiagr has quit IRC16:31
jgriffithI'm assuming we don't want it customer visible16:31
DuncanTIndeed16:31
*** mikal has joined #openstack-meeting16:31
jgriffithrighty oh then16:31
jgriffithDuncanT: anything else?16:31
DuncanTMulti-AZ16:31
jgriffith#topic multi-az16:32
*** openstack changes topic to "multi-az (Meeting topic: cinder)"16:32
DuncanTIs anybody else doing it?16:32
jgriffithSo I have a blue print16:32
jgriffithI'm going to have to look at sooner rather than later16:32
jgriffithWe have to do it really else ec2 is going to be broken16:32
guitarzanlink?16:32
jgriffithNova put it in via aggregates16:32
DuncanTQuestion 1) Should cross-az volume mounting work?16:33
jgriffithDuncanT: I don't think EC2 allows it, no16:33
DuncanT(Nova's AZ support is broken in places - this is being looked at)16:33
jgriffithguitarzan: https://blueprints.launchpad.net/cinder/+spec/aggregates-in-cinder16:33
DuncanTGood, because as ideas go, allowing it sucks ;-)16:34
jgriffithNot much there yet16:34
jgriffithhehe16:34
guitarzancool, thanks16:34
jgriffithEverybody feel free to provide input on this one16:34
jgriffithI'm getting a handle on AZ and now aggregates but honestly I dislike all of the above :)16:34
*** reed has joined #openstack-meeting16:35
jgriffithNot in on a philosophical or implementation level or anything, I just find it a bit tedious :)16:35
DuncanTSyncronising the default AZ in nova with the default AZ in cinder, particularly if you want that to vary per tenant for load ballancing, is an issue, though probably not a major one (e.g. let keystone pick it)16:35
winston-d_jgriffith: could you elaborate a little bit on this BP?16:35
jgriffithDuncanT: That's actually the point of that BP16:35
jgriffithwinston-d_: sure16:35
*** AlanClark has joined #openstack-meeting16:35
jgriffithAs DuncanT just pointed out AZ's between Nova and Cinder need to be synched16:36
jgriffithIn other words instance and volume have to be in same AZ for attach to work16:36
winston-d_right16:36
jgriffithWe cheated before and just said, admin set the AZ16:36
jgriffithBut now it's not going ot be quite so simple16:36
jgriffithThe changes in Nova will allow aggreagates, which results in multiple AZ's for a single node16:37
jgriffithin essence16:37
jgriffithAlso, it's now a bit dynamic16:37
xyang_what about cells?  How does cells affect this?16:37
jgriffithwell, not a *bit*, it is16:37
jgriffithcells are different, and I have chosen to ignore them :)16:37
guitarzancells shouldn't make much difference I think16:37
*** vkmc has quit IRC16:37
winston-d_xyang_: i don't think so. cell is transparent to end-users16:37
JM1storage location isn't very dynamic by nature16:38
*** cdub_ has joined #openstack-meeting16:38
jgriffithJM1: well yes and no16:38
*** vishy is now known as vishy_zz16:38
jgriffithJM1: You may start with an AZ based on a data center, then break it down to racks16:38
jgriffiththen break it down to PDU's16:38
jgriffithetc etc16:38
JM1do people expect such small AZ ?16:39
jgriffithalthough folks like guitarzan and DuncanT would have better use case descriptions than I16:39
winston-d_jgriffith: so you want cinder to be able to support aggreagates?16:39
jgriffiththey actually deal with this stuff on a daily basis :)16:39
jgriffithwinston-d_: correct16:39
bswartzIn my experience, AZs for storage never get smaller than a rack -- usually a group of racks16:39
jgriffithwinston-d_: I think it's goint o have to16:39
jgriffithto16:39
*** markvoelker has joined #openstack-meeting16:39
*** koolhead17 has joined #openstack-meeting16:39
DuncanTSo we have 3 AZs in a datacenter, each in their open fire-cell and independant core switching etc16:40
jgriffithbswartz: Yeah, but doesn't the netapp cluster take up an entire rack :)16:40
DuncanTs/open/own/16:40
bswartzjgriffith: lol16:40
jgriffithbswartz: :)16:40
*** johngarbutt has joined #openstack-meeting16:40
jgriffithSo DuncanT does this line up with what you were wanting to talk about16:40
JM1so even with small AZ, data is either here or there, and has to move somehow16:41
JM1it's still not very dynamic I think16:41
jgriffithJM1: the dynamic piece is the ability to create/change names at any time16:41
DuncanTjgriffith: Yes, though I'm not yet massively familiar with agrigates .v. cells .v. azs - I can grab a nova person and get them to educate me though16:41
DuncanTjgriffith: It sounds like you're heading in the same general direction though, which is good16:42
JM1jgriffith: ah ok, that sounds more realistic16:42
winston-d_DuncanT: so what is your use cases for multiple-AZ?16:42
jgriffithBasicly just making sure we can sync with Nova and not break16:42
jgriffithsorry.. that was for DuncanT regarding my direction16:42
DuncanTwinston-d_: Multiple firecells within a datacentre... scalability beyond a few hundred compute nodes16:42
DuncanTjgriffith: Yeah, but we're also evolving nova at the same time ;-)16:43
guitarzanand as an aside, I don't think rackspace uses AZs16:43
jgriffithDuncanT: Yeah, that's the problem :)16:43
*** psedlak has quit IRC16:43
jgriffithguitarzan: oh... really?16:43
guitarzanwe just use cells to scale out, and regions for datacenters16:43
jgriffithYay!16:43
DuncanTCan you connect storage across cells?16:43
winston-d_DuncanT: yes, that i can understand.16:43
jgriffithwell... doesn't the region coorelate to an AZ?16:43
guitarzanDuncanT: yes16:43
guitarzanjgriffith: I don't know, maybe?16:43
jgriffithguitarzan: isn't cells really just a tag?16:43
jgriffithie metadata16:44
*** markvoelker has quit IRC16:44
DuncanTSo our idea with multiple AZs  in a region/datacentre is that if one goes down, the other is pretty much independant16:44
guitarzanit's passing messages through different queues16:44
guitarzanbut you'll have to talk to comstud to find out what all it entails :)16:44
winston-d_jgriffith: no, my understanding is cell is a small cloud with almost everything: API/DB/scheduler/ComputeNodes16:44
jgriffithwinston-d_: haha.. that's what I thought of as an AZ :)16:45
JM1DuncanT: isn't that a region within a region?16:45
guitarzanwinston-d_: api calls tend to go to the parent cell16:45
jgriffithalright, Ithink we're all going to get much smarter on cells and AZ's in the coming weeks16:45
*** jog0 has quit IRC16:45
winston-d_guitarzan: that's right, but as i said, cell is transparent to end users.16:45
guitarzanyep16:45
jgriffithAnything else on the topic of AZ's, cells etc?16:45
DuncanTJM1: Pretty much, currently each of our AZs has its own set of endpoints, which we don't really like16:45
xyang_and a child cell can have its own child cell16:45
jgriffith#topic G316:46
*** openstack changes topic to "G3 (Meeting topic: cinder)"16:46
DuncanTjgriffith: I'll probably have more in future, for now I need to get reading up on nova approaches a bit more16:46
jgriffithDuncanT: sounds like we all need to do that homework16:46
jgriffith:)16:46
jgriffithI've updated the G3 targets again16:47
jgriffithhttps://launchpad.net/cinder/+milestone/grizzly-316:47
jgriffithThere's an awful lot going on again :)16:47
jgriffithBig chunk of it is new drivers16:47
JM1sorry :)16:47
jgriffith:)16:48
rushiagr1jgriffith: need to add cinder protocol enhancements aka 'nas as service'16:48
avishayI'll probably have another small driver + driver update for new API and bug fixes16:48
jgriffithrushiagr1: the BP is there, we can target it if you think you'll have something in the next couple weeks16:48
bswartzrushiagr1: +116:48
jgriffithHow are things going on that BTW?16:49
jgriffithHaven't heard anything in a bit16:49
bswartzjgriffith: we're aiming to be COMPLETE on 2/14 with some WIP submitted before then16:49
jgriffith2/14 with some WIP?16:49
jgriffithCutting it kinda close for a large change isn't it?16:49
*** Mr_T has joined #openstack-meeting16:49
jgriffithbswartz: that sounds good if you guys can hit it16:50
*** markvan has joined #openstack-meeting16:50
bswartzjgriffith: you yourself said a week before the milestone would be okay as long as the overlap with existing code was minimized16:50
rushiagr1jgriffith: a WIP version before 2/1416:50
bswartzwe're doing the best we can to make it available before then16:50
jgriffithThat was when the milestone was G2 :)16:50
jgriffithbswartz: I hear ya16:50
jgriffithbswartz: I think that's fine16:50
jgriffithbswartz: I'm just saying be kind to us16:50
jgriffithI've got patches that are only in the teens in terms of lines16:51
jgriffithfolks haven't been able to review them in a wekk16:51
jgriffithweek16:51
kmartinjgriffith: Still waiting for some core nova reviewers(russellb and/or vishy) to look at the FC nova changes https://review.openstack.org/#/c/19992/  only one review since we put the review in on Jan 17th16:51
jgriffithYour patch is going to be significantly larger :)16:51
Navneetwe have also submitted NetApp direct drivers for review16:51
bswartzwe'll help out with reviews from our side16:51
*** jog0 has joined #openstack-meeting16:51
jgriffithNavneet: Yeah, I'm working on that one16:52
bswartzNavneet: are those done or going to be revised once more?16:52
jgriffithbswartz: how about helping with reviews that are non-netapp?16:52
bswartzjgriffith: absolutely16:52
jgriffithbswartz: awesome16:52
jgriffithok.. that all sounds good16:52
jgriffithI'm looking forward to what you guys came up with16:52
rushiagr1jgriffith: I would be there for reviews too.. Sorry, wasnt able to dedicate time in this first half of this week16:52
Navneetjgrifith: thats final from us...it contaons clone vol and filter scheduler related capabilities16:52
bswartzNavneet, rushiagr1: please review stuff from https://launchpad.net/cinder/+milestone/grizzly-316:52
jgriffithremember, if you can share the source before review even better16:52
eskerjgriffith: we're absolutely interested in doing so16:52
jgriffithie github or draft etc16:53
jgriffithbswartz: Navneet rushiagr1 actually if you could just poke around here: https://review.openstack.org/#/q/status:open+cinder,n,z16:53
*** ryanpetrello has quit IRC16:53
jgriffithesker: cool.. thanks16:53
jgriffithWe can use all the review help we can get16:54
*** ryanpetrello has joined #openstack-meeting16:54
winston-d_jgriffith: hasn't been doing reviews lately, will catch up16:54
Navneetok16:54
avishaykmartin: when do we get the cinder FC patches?  is it waiting on nova getting merged?16:54
jgriffithThat link I gave shows all open cinder patches16:54
jgriffithand dont' forget there are cinderclient patches too :)16:54
kmartinavishay: yes, that was the plan16:55
*** mikal has quit IRC16:55
avishaykmartin: ok thanks16:55
jgriffithOk folks, we've got 5 minutes til the other John kicks us out :)16:55
jgriffith#topic open discussion16:55
*** openstack changes topic to "open discussion (Meeting topic: cinder)"16:55
kmartinCan winston-d give an update on the volume stats changes that we talked about last week?16:55
rushiagr1jgriffith: sure. Would take some more time before I start cinderclient reviews16:55
jgriffithwinston-d_: ^^16:55
Navneetjgrifith: the latest submit from us is large in size...if we can get review comments soon to get it in...request16:56
*** mikal has joined #openstack-meeting16:56
winston-d_kmartin: i'm working on RetryFilter, should be able to submit this week. by then the scheduler is able to handle those 3 cases we talked about last week.16:57
*** dolphm has joined #openstack-meeting16:57
kmartinwinston-d_: thanks.16:57
jgriffithwinston-d_: speaking of which, any chance you can throw out some info on how to configure the fitlers, and how we might do custom filters in the future?16:57
jgriffithAlso how to set up back-end filter :)16:57
jgriffithmaybe a wiki?16:58
jgriffithdesign theory, control flow type thing?16:58
winston-d_jgriffith: sure. my document plan is pending, i have something already but not complete yet.16:58
jgriffithwinston-d_: Ok, great!16:58
jgriffithalright.. anybody else have anything?16:58
jgriffithwe've got two minutes :)16:59
jgriffithDOH one minute16:59
smulcahyWhen you send a request to cinder, it returns a unique request id - presumably for support/diagnostics16:59
smulcahythis is currently called X-Compute-Request-Id16:59
smulcahyshould it be called something else?16:59
winston-d_jgriffith: sure. if you like i can even do a  session for filter/weigh development in next summit. :)16:59
*** jcmartin has quit IRC16:59
jgriffithwinston-d_: +116:59
jgriffithwinston-d_: fantastic idea!16:59
avishayjgriffith: any thoughts on safely disconnecting iscsi connections w/ multiple LUNs/target?16:59
smulcahyand currently there is v little diff between /volumes and /volumes/detail - is that intentional or are there plans to strip down the output of /volumes ?16:59
rushiagr1winston-d_: +117:00
*** dtalton has joined #openstack-meeting17:00
kmartinwinston-d_: +1, but we would like to get in Grizzly :)17:00
jgriffithsmulcahy: probably, I'll have to llok17:00
*** ryanpetrello has quit IRC17:00
guitarzansmulcahy: is that the same header name as from compute?17:00
jgriffithavishay: I think your'e the only one with multiple luns per target17:00
*** thingee has left #openstack-meeting17:00
smulcahyjgriffith: I'm guessing something like X-Volume-Request-Id or maybe just X-Request-Id17:00
winston-d_kmartin: yup, all basic filter scheduler features to make cinder work will get in G. and more advanced filter/weigher can come later.17:01
avishayxyang_ has also :)17:01
xyang_We also have multiple luns per target17:01
smulcahyguitarzan: didn't check but I'm guessing we inherited it in move from nova17:01
jgriffithmight be easiset to just over-ride the disconnect, but I honestly never got back to it17:01
*** jog0 has quit IRC17:01
xyang_LVM supports it too17:01
kmartinwinston-d_: ok great, looking forward to it17:01
guitarzansmulcahy: sure, but since those request ids are the same across the service, it might not make sense to use different header names17:01
jgriffithavishay: That would be a band-aid at least17:01
jgriffithguitarzan: smulcahy IIRC there was a reason I left those headers17:02
*** cdub_ has quit IRC17:02
smulcahyguitarzan: right, so maybe then something service neutral like X-Request-Id ?17:02
guitarzansmulcahy: no argument about that from me :)17:02
avishayxyang_: can you explain about LVM to me and jgriffith?17:02
jgriffithand I believe it had something to dow ith attach/detach as well as avoiding some keystone work17:02
jgriffithbut not sure17:02
smulcahynot a big issue, just thought I'd mention it17:02
jgriffithavishay: sure, meet me in #openstak-cidner17:02
jgriffithOk wer'e out of time17:02
jgriffiththanks everyone17:02
jgriffith#openstack-cinder17:02
jgriffithand reviews, reviews, reviews!!!!!17:02
jgriffith#endmeeting17:03
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:03
openstackMeeting ended Wed Jan 23 17:03:03 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:03
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-01-23-16.00.html17:03
JM1thanks john for hosting the party17:03
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-01-23-16.00.txt17:03
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-01-23-16.00.log.html17:03
*** avishay has left #openstack-meeting17:03
*** rushiagr1 has left #openstack-meeting17:03
johngarbutt#startmeeting XenAPI17:03
openstackMeeting started Wed Jan 23 17:03:27 2013 UTC.  The chair is johngarbutt. Information about MeetBot at http://wiki.debian.org/MeetBot.17:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:03
*** openstack changes topic to " (Meeting topic: XenAPI)"17:03
openstackThe meeting name has been set to 'xenapi'17:03
*** rushiagr1 has joined #openstack-meeting17:03
johngarbutthello all17:03
nikhilhi17:03
matelakathi17:03
ameade_hey hey17:03
*** JM1 has left #openstack-meeting17:03
Mr_Thola17:04
*** bswartz has left #openstack-meeting17:04
*** winston-d_ has left #openstack-meeting17:04
johngarbutt#topic agenda17:04
*** openstack changes topic to "agenda (Meeting topic: XenAPI)"17:04
johngarbuttwhat do people want to cover?17:04
johngarbuttthere was the swift upload stuff17:04
johngarbuttanything else?17:04
*** BobBall has joined #openstack-meeting17:04
*** vishy_zz is now known as vishy17:04
johngarbuttideas: blueprints, docs, QA, Bugs17:05
matelakatI would like to have some xenapi lib code pulled to oslo.17:05
matelakatBut that's far away from being ready.17:05
*** jsavak has quit IRC17:05
johngarbuttright, Cinder now contacts XenAPi17:06
johngarbuttas does Nova17:06
johngarbuttlets not get into more cut and paste17:06
johngarbuttOK17:06
nikhil:)17:06
johngarbuttlets move on to swift17:06
*** SpamapS has joined #openstack-meeting17:07
johngarbutt#topic swift client in dom017:07
*** openstack changes topic to "swift client in dom0 (Meeting topic: XenAPI)"17:07
johngarbuttlet me find the link17:07
*** danwent has joined #openstack-meeting17:07
nikhilshould we ans any concerns?17:07
johngarbutt#link https://review.openstack.org/#/c/17803/17:08
johngarbuttso, what was the issue getting the swift CLI working in Dom0 again?17:08
BobBallI haven't been following this properly - what's the current proposal? a python 2.4 compatible client in dom0?17:08
johngarbuttnope17:08
johngarbuttinstall python 2.617:08
johngarbuttthen use a custom swift client17:08
johngarbuttwith some chunking code from glance17:08
johngarbuttas plugins17:08
BobBallgood for the first bit! I was a little worried :D17:08
johngarbuttI think that is right?17:08
ameade_that's what is in the patch atm17:09
* notmyname is lurking because you mentioned swift17:09
johngarbuttso I just wondered, why don't we install all of the swift client, unmodified17:09
ameade_so I thought maybe packaging swiftclient code into the rpm for dom0 would work17:10
ameade_but turns out that it also has a dependency of keystoneclient17:10
ameade_when using auth v217:10
*** smulcahy has quit IRC17:10
johngarbuttOK17:10
ameade_which has a few other dependencies17:10
johngarbuttis keystone a problem?17:10
johngarbutthmm, true17:10
*** rushiagr1 has left #openstack-meeting17:10
*** hemnafk is now known as hemna17:10
johngarbuttI understand we want to minimize the changes to dom017:11
nikhildo we run yum on dom0, is that something advised?17:11
johngarbuttbut it seems better to use the standard swift client,17:11
matelakatvirtualenv?17:11
johngarbuttgood idea17:12
nikhilplease just quantify here, why would consider it better john?17:12
johngarbuttthe only issue is on non python stuff like lxml17:12
johngarbuttsure17:12
johngarbuttbasically we have much less code to maintain17:12
nikhilmatelakat: how much memory do you think it will take additionally?17:12
matelakatnikhil: I don't think a virtualenv would cause memory overhead.17:13
johngarbuttso XCP/XenServer doesn't use python 2.617:13
johngarbuttso installing pure python 2.6 dependencies should be no issue right?17:14
johngarbuttits the extra bits I fear17:14
johngarbuttlet me check out the pip requires for keystone client...17:14
nikhiljohngarbutt: pure python 26 screws up a yum and stuff on dom017:14
johngarbuttouch, really?17:14
johngarbuttwhat happens?17:14
nikhilwe could not run yum after installing py2617:14
johngarbutthmm, that sucs, I see your yum question before17:15
johngarbuttwhat package did you use? the one from EPEL?17:15
nikhilright17:15
matelakatcan we compile stuff within dom0?17:15
johngarbuttI guess the key thing is not to change the default python to 2.6, leave that at 2.417:15
nikhilyes17:15
johngarbuttpresumably anyway17:16
matelakatSo can we compile a python26, and use it separately?17:16
johngarbuttI didn't spot they when I tried it17:16
johngarbuttI was thinking an extra rpm to switch the default back to python 2.417:16
matelakatwithout disturbing yum?17:16
BobBallThe epel packages just sit as new pythons - don't replace the 2.4 at all17:16
johngarbuttthat is what I remembered17:17
johngarbuttmaybe something deeper is breaking yum17:17
johngarbuttOK, well that is a problem for any of the approaches here17:17
johngarbuttdoh17:17
johngarbutt#action johngarbutt: ask about yum and python 2.6 packages17:17
nikhilthe minimal py26 works for the swiftclient17:18
ameade_yeah, we just need to see if getting keystone client and things is more trouble than it's worth17:18
nikhilspot on17:18
johngarbuttright, again, better than writing our own keystone client though?17:18
johngarbutt#link https://github.com/openstack/python-keystoneclient/blob/master/tools/pip-requires17:18
johngarbuttlooks quite small17:19
matelakatThe effort wouldn't be wasted, if anyone would try to run compute in dom0.17:19
nikhilall the more, we were advised against having to install a package on dom017:19
nikhilits a big No No from the Ops17:19
johngarbuttagreed, because of the risk of Citrix saying its not supported, and security risks I guess17:19
nikhilright17:20
johngarbuttvirtual env could be the answer, and adding permissions and users etc17:20
johngarbuttbut it seems overkill17:20
nikhilmatelakat: don't think dom0 could handle running entire compute on it (from the current experience)17:20
ameade_yeah seems like a possibility but really heavy handed17:21
matelakatThese keystoneclient deps does not seem to be too serious.17:21
nikhilanother dev had mentioned virtualenv17:21
johngarbuttI think the security risk of bad code due to copy and paste would be bigger than most of the others17:21
matelakatjohngarbutt +117:21
johngarbuttbut that is just my view, willing to be corrected!17:21
*** garyTh has quit IRC17:21
nikhilbut hw backed from that opinion as some of them were concerned about small memory on dom017:21
*** lloydde has joined #openstack-meeting17:21
*** garyTh has joined #openstack-meeting17:22
nikhiljohngarbutt: think keystone is quite fragile17:22
nikhilhaving keystone client would make it worse17:22
johngarbuttthe process is very short lived, so it should be OK, but testing is the only well to tell I guess17:22
nikhilnot sure if can expect security changes from swift anytime soon17:22
johngarbuttyou can increase dom0 memory, but obviously that reduces what is left for VMs17:22
nikhilright you are17:22
*** danwent has quit IRC17:22
nikhilyes17:23
*** danwent has joined #openstack-meeting17:23
johngarbuttits not just changes right, we have new code that might have its own issues17:23
nikhilguess as a Citrix person you would suggest against increasing dom0 memory?17:23
johngarbuttI know Citrix recommends it for XenDeskop customers, for certain density reasons. Newer versions actually have higher defaults17:24
johngarbuttbut not sure17:24
johngarbuttfor the general case17:24
BobBallWe're quite happy for dom0 memory to be increased now - in fact it's going to be the default in some scenarios.  The only downside is there is a reduction in some blk performances17:24
*** hub_cap has left #openstack-meeting17:24
*** gary_th has joined #openstack-meeting17:24
johngarbuttBobBall: was that only over 2GB of RAM though? or something?17:24
johngarbuttanyway17:25
johngarbuttwe got side tracked17:25
nikhilwell to have to increase the dom0 memory for 1000s of servers might just do some trick in the deployment, i would guess?17:25
nikhilyes yes17:25
nikhilswift client17:25
*** Navneet has quit IRC17:26
johngarbuttcan we try and see if that installs OK?17:26
johngarbuttusing pip is easiest17:26
johngarbuttpip-2.6 or something like that I gues17:26
johngarbuttif its really bad, then I guess we need to look at something else?17:27
ameade_yeah i think this is something to look into17:27
johngarbuttwe should be able to run it and see how much memory that process uses17:27
ameade_is there another option we aren't considering?17:27
ameade_currently the glance plugin just does communication through httplib17:27
johngarbuttso, there was some code from glance in there for chunking, could the swift client not do that for us now?17:27
*** mikal has quit IRC17:27
johngarbuttah, I guess that answers my question!17:27
*** garyTh has quit IRC17:28
johngarbuttI don't understand why glance does that? I guess someone will know17:28
*** garyk has quit IRC17:28
*** derekh has quit IRC17:28
*** mikal has joined #openstack-meeting17:28
nikhildom0 streams images to glance17:28
nikhilso there is an open connection for doing that17:28
johngarbuttyes, it just uses wget I think17:29
johngarbuttI would have to check17:29
*** vishy is now known as vishy_zz17:29
johngarbuttI think we could look at using the official glance client if this other stuff goes well17:29
*** kaganos has joined #openstack-meeting17:30
johngarbuttif Dom0 had python 2.6 by default, I am guessing we would not even worry about this17:30
johngarbuttsorry I see httplib17:30
johngarbuttfor the upload17:30
nikhilyes, however at the same time we would like to avoid installing anything on dom017:31
*** adjohn has joined #openstack-meeting17:31
*** thunquest has joined #openstack-meeting17:31
ameade_are we out of time?17:31
matelakatversioning would be another pain, I guess.17:31
johngarbuttif the swift code could be as simple, I guess I would be OK with it. its the chunking stuff that seems working sharing17:31
ameade_yeah it would have to be much simpler for me to feel comfortable too17:32
johngarbuttameade_: we have till 18:00 UTC as normal this week I think17:32
ameade_kk17:32
johngarbuttbut we should wrap this up17:32
nikhilyes, glance is flexible to handle that17:32
ameade_off the top of my head i'm not sure how much simpler we can make that code17:32
johngarbuttis there some vote function on here17:32
nikhilwhat are the next steps we have considered then?17:32
johngarbutt#vote17:32
nikhilunless a decision has been made, seem unlikely17:32
ameade_yeah i dont know how to do it17:33
ameade_vote i mean17:33
johngarbutt#startvote17:33
openstackUnable to parse vote topic and options.17:33
*** kaganos has quit IRC17:33
johngarbuttwhat we try to install swift client, and see how bad it is first17:34
johngarbuttplease +1 or -1 that17:34
nikhil+117:34
ameade_yeah i feel like we should look deeper into both options17:34
*** gary_th has quit IRC17:34
ameade_starting with installing17:34
matelakat+117:34
ameade_so +117:34
BobBall+117:34
ameade_+117:34
johngarbutt+117:34
johngarbuttOK17:35
nikhil:-)17:35
*** pschaef has quit IRC17:35
johngarbutt#agreed try install swiftclient (and keystone client) into dom017:35
johngarbuttI think that is best17:35
johngarbuttwe can then see how bad stuff is17:35
nikhilagree17:35
johngarbuttcool17:35
*** jcmartin has joined #openstack-meeting17:35
*** vishy_zz is now known as vishy17:36
johngarbuttany other concerns with this stuff? it looks good to me really17:36
nikhilwell another collegue just pointed out17:36
nikhilthe httplib connection seems insecure, although not in consideration just wanted to put it on the table17:37
nikhilinsecure for dom017:37
johngarbuttfor glance or swift or both?17:37
nikhilanyways, guessing we have our TODOs, do we meet again next Wed?17:37
johngarbuttyes, lets meet every wednesday17:38
nikhilin general17:38
johngarbuttyou would like https?17:38
nikhilhowever glance is supposed to be an internal deployment and hidden behind nova17:38
*** Gordonz has joined #openstack-meeting17:38
johngarbuttI assumed that was internal network17:38
johngarbuttat the moment17:38
nikhilhttps would be too slow if you want to upload 30G image17:38
johngarbuttglance can be external17:38
nikhilyou'r right17:38
nikhilbut that usecase for security hasn't come yet17:39
johngarbuttI guess its defence in depth17:39
nikhilright17:39
johngarbuttthe checksums are probably worth checking17:39
johngarbuttto make sure it didn't get tampered with17:39
nikhilI would just like to rewrite a lot of stuff17:39
johngarbuttI can understand that!17:39
ameade_story of my life17:39
nikhilthose are checked in glance and swift17:39
nikhilchecksums17:39
johngarbuttI like the boy scout rule17:39
johngarbuttmake sure stuff is better after every checkin17:40
johngarbutt:-)17:40
johngarbuttanyway17:40
ameade_me too but people dont like random improvments in merge props17:40
ameade_lol17:40
*** markvoelker has joined #openstack-meeting17:40
johngarbuttI guess we are finished17:40
ameade_thanks17:40
nikhilthanks!17:40
johngarbutt#topic aob17:40
*** openstack changes topic to "aob (Meeting topic: XenAPI)"17:40
johngarbuttanything else?17:40
notmynameameade_: feel free to submit "random improvements" into python-swiftclient :-)17:40
johngarbuttameade_: yes, but you can impove stuff in separate checkins17:40
johngarbutt+117:41
*** kaganos has joined #openstack-meeting17:41
ameade_definitely, just find me some time!17:41
johngarbuttOK, some extra love for the OVS reviews seems worth bringing up again, I guess17:41
johngarbuttbut looks like that is getting closer now17:41
johngarbuttsee you all next week17:41
johngarbuttthanks for your time17:42
johngarbuttI hope it helped!17:42
johngarbutt#endmeeting17:42
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"17:42
openstackMeeting ended Wed Jan 23 17:42:09 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-01-23-17.03.html17:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-01-23-17.03.txt17:42
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-01-23-17.03.log.html17:42
*** kaganos has left #openstack-meeting17:42
*** matelakat has quit IRC17:43
*** jdurgin1 has joined #openstack-meeting17:44
*** markvoelker has quit IRC17:45
*** bencherian has quit IRC17:45
*** asparks has joined #openstack-meeting17:46
*** johngarbutt has left #openstack-meeting17:46
*** BobBall has quit IRC17:46
*** xyang_ has quit IRC17:48
*** EmilienM has quit IRC17:50
*** garyk has joined #openstack-meeting17:52
*** Mandell has joined #openstack-meeting17:57
*** joesavak has joined #openstack-meeting17:58
*** danwent has quit IRC18:00
SpamapSo/18:01
SpamapSheaters?18:01
*** danwent has joined #openstack-meeting18:02
*** markvan_ has joined #openstack-meeting18:03
*** bencherian has joined #openstack-meeting18:03
*** markvan has quit IRC18:03
*** markvan_ is now known as markvan18:03
*** lloydde has quit IRC18:06
*** lloydde has joined #openstack-meeting18:07
*** bvibhu has quit IRC18:07
*** lloydde has joined #openstack-meeting18:07
*** mrodden has quit IRC18:08
*** Mr_T has left #openstack-meeting18:15
*** lloydde has quit IRC18:15
*** sdake_z has quit IRC18:18
*** morganfainberg has quit IRC18:19
*** juice has joined #openstack-meeting18:23
*** metral_ has joined #openstack-meeting18:28
*** jhenner has quit IRC18:29
*** metral__ has joined #openstack-meeting18:30
*** metral has quit IRC18:30
*** metral__ is now known as metral18:30
*** lloydde has joined #openstack-meeting18:31
*** diogogmt has quit IRC18:33
*** metral_ has quit IRC18:33
*** diogogmt has joined #openstack-meeting18:34
*** juice has quit IRC18:34
*** stevebaker has joined #openstack-meeting18:35
*** vishy is now known as vishy_zz18:35
*** vkmc has joined #openstack-meeting18:36
*** juice has joined #openstack-meeting18:36
*** kmartin has quit IRC18:36
*** anniec has joined #openstack-meeting18:37
*** darraghb has quit IRC18:37
*** ndipanov has quit IRC18:39
*** kmartin has joined #openstack-meeting18:39
*** markvoelker has joined #openstack-meeting18:40
*** GheRivero is now known as GheRivero_afk18:40
*** sdake has joined #openstack-meeting18:40
*** vishy_zz is now known as vishy18:41
*** tongli has joined #openstack-meeting18:41
*** malini has joined #openstack-meeting18:42
*** markvoelker has quit IRC18:45
*** ollie1 has left #openstack-meeting18:45
*** clayg has joined #openstack-meeting18:50
*** diogogmt has quit IRC18:52
*** yaguang has quit IRC18:53
*** caitlinbestler has joined #openstack-meeting18:55
*** cschwede has joined #openstack-meeting18:55
*** ryanpetrello has joined #openstack-meeting18:55
notmynameswift meeting time19:00
notmynameyour favorite part of the fortnight ;-)19:00
notmyname#startmeeting swift19:00
openstackMeeting started Wed Jan 23 19:00:43 2013 UTC.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: swift)"19:00
openstackThe meeting name has been set to 'swift'19:00
notmynameI sent out an agenda outline to the mailing list19:01
*** dfg has joined #openstack-meeting19:01
notmynamefirst up: slight change in versioning/tagging at common release time19:01
notmynamenothing major, but something I think you should be aware of19:01
*** mpdehaan has joined #openstack-meeting19:01
notmynameold way: we release when we're ready (hopefully close to the combined release time), and our last release during the cycle gets included19:02
notmynamein the case that we want to cut another release before the combined release comes out, we do it and versions get bumped19:02
notmynamenew way: we release when we're ready (hopefully close to the combined rleease time), and that does the normal milestone-proposed dance as normal19:03
*** sdake_z has joined #openstack-meeting19:03
*** ThiagoCMC has joined #openstack-meeting19:03
*** diogogmt has joined #openstack-meeting19:04
notmynameexcept now, at the combined release time, the final version on milestone-proposed will not get the final version flag until the actual release, and instead will get a -rcX tag19:04
*** markvan has quit IRC19:04
notmynameno real change to us, but the impact is that we cannot release a full new version between what we think will be in the combined release and when the combined release actually releases19:05
notmynameany questions?19:05
chmouelso on milestone-proposed we get -rc? and on release remove the -rc?19:05
*** mrodden has joined #openstack-meeting19:05
notmynamechmouel: technically, a new non-rc tag (rather than deleting a tag), but yes19:05
chmouelok19:05
swifterdarrellnotmyname: "combined release" is like Essex or Folsom?  or something inbetween?19:05
notmynameya, the essex, folsom, etc releases19:06
notmynamebut since the milestone-proposed will still be "active", we cannot use it for another release until the combined release comes out19:06
*** dosaboy has quit IRC19:06
*** stevebaker has quit IRC19:06
notmynameoh, I should use the meetbot flags19:07
swifterdarrellso the tradeoff is potentially backporting (to -rcX) instead of rushing a new release if we have late changes which are important (between the milestone-proposed release and combined release), correct?19:07
notmynamecorrect19:07
caitlinbestlerDoes this reduce the amount of project-wide testing on a non-openstack-integrated release?19:07
notmynamebut that's essentially what we do now anyway19:07
tongli@notmyname, is there a link to access the 'what's new in the release on Swift'?19:08
notmynamecaitlinbestler: I think this mostly comes from distros being able to plan for the combined release. I think it may help the openstack CI team have consistent version numbers, though19:09
notmynametongli: the CHANGELOG os the authoritative source, but I also normally send out an email about it too19:09
malininotmyname: -rcX is the X an integer, just bunp up X? or is it -rcGrisly .. I am wondering because we have milestones such as G1, G2 etc19:09
creihtnotmyname: in other words, avoids everyone from going crazy because we add a .1 to the release? :)19:09
notmynamemalini: integer19:09
notmynamecreiht: ya :-)19:09
creihtlol19:09
notmynameit doesn't really change anything we've been doing, but I'm told it makes other people's lives easier :-)19:10
creihtseems like a reasonable compromise though19:10
creihtjust funny19:10
notmynameya19:10
notmyname#info swift candidates for the openstack combined release will have an -rcX tag until the combined release actually happens to avoid a version number dance in the case of backports19:11
swifterdarrellimportant changes between milestone-proposed release and combined release are a PITA any way you slice it, so seems reasonable (not any worse, etc.)19:11
*** stevebaker has joined #openstack-meeting19:11
notmynameyup19:11
notmyname#topic swift next API wiki19:11
*** openstack changes topic to "swift next API wiki (Meeting topic: swift)"19:11
*** adrian_smith has joined #openstack-meeting19:11
notmynamecreiht and chmouel talked about and put together http://wiki.openstack.org/SwiftNextAPI. awesome. let's all add to it19:12
notmyname#link http://wiki.openstack.org/SwiftNextAPI19:12
claygcool hadn't seen that19:13
notmynamesome of the minor changes are things we should consider addressing sooner than later, but for the big stuff, I'd like you to think about "what does swift 2.0 mean?"19:13
notmynamecreiht: thanks for putting it up19:13
*** ladquin has joined #openstack-meeting19:14
*** jsavak has joined #openstack-meeting19:14
*** morganfainberg has joined #openstack-meeting19:14
notmynameI don't have much to add there. just wanted to say I liked it and make sure people knew about it19:14
notmyname#topic pycon sprint19:14
*** openstack changes topic to "pycon sprint (Meeting topic: swift)"19:15
*** vishy is now known as vishy_zz19:15
maliniFor me from an API standpoint, it means new user functionality.  Including server side encryption, it could include stuff like cold-storage, reduce number of copies19:15
notmynameswiftstack and redhat are working together to host a sprint at pycon this year. our goal is not to work on swift directly, but to encourage client apps written against the swift api19:15
creihtnotmyname: I'm planning on going through the apis before the conference19:15
notmynameIf you would like to be involved, please let me know19:15
notmynamecreiht: cool19:16
cschwedei'd like to be involved, might add some code to server side encryption19:16
notmynamewe have 2 ideas for the sprint, and I'd like your feedback: 1) add swift support to tools like boto and s3cmd 2) hackathon to build swift clients19:17
notmynamethoughts?19:17
notmynamewhat would be interesting to you to hack on?19:17
creihtnotmyname: That will likely depends on who shows up for the sprints right?19:17
notmynamecreiht: it does affect how we promote it though19:18
chmouelwill probably not be able to make it19:18
*** joesavak has quit IRC19:18
creihttrue19:18
creihtI'm still looking into weather I can stay for the sprints or not19:18
*** Dieterbe has joined #openstack-meeting19:18
notmynamealthough the sprints are 3 days after the conference, I think we'll just be doing stuff on monday the 18th19:19
notmynamea single day19:19
maliniI am new to all things Swift and would like to participate .. so I have some ramping to do till March before hackthon. Just went through John's swift workshop from the last summit.19:19
creihtk19:19
malini+1 for swift clients19:20
notmynamemalini: that's what I'm leaning towards too19:20
*** vishy_zz is now known as vishy19:20
swifterdarrellI like the adding-swift-support to existing tools idea... since this is PyCon, we'd be talking tools implemented in python or python client libraries, right?19:20
creihtnotmyname: that's cool with me, perhaps with a "or we will help you with whatever you would like to hack on"19:20
claygyeah I'd rather see a new tool that is built for swift than adding swift support to something I don't know the guts of and has an impedence mismatch19:21
claygheh19:21
notmynamecreiht: of course19:21
cschwededoes swift clients includes addons to the current swift.py?19:21
notmynameswifterdarrell: clayg: can I agree with both of you? ;-)19:21
creihtnotmyname: another intersting one would be improving swift319:22
* clayg is not that interested...19:22
clayg;)19:22
notmynamecschwede: perhaps, but also like "build a better cyberduck" or, in a hackathon sense, "build a small site that stores data in swift"19:22
notmynamecreiht: indeed19:22
creihtlol19:22
creihtnotmyname: I think a general cross-platform gui written in python would be very nice19:23
creihtand well received19:23
notmynameya19:23
claygcross-platform?  you mean the web right?19:23
cschwedecreiht: web or desktop?19:23
clayglol19:24
claygsrly who does desktop apps anymore19:24
creihtof course there is also improving swiftly, or the user space wrappers (like fuse, etc.)19:24
creihtcschwede: desktop19:24
tongliprobably swift-dropbox for mobile device is the best thing to do.19:24
creihtif you are looking at web based, actually it wouldn't be a bad idea to improve horizon support19:24
swifterdarrellcschwede: I hope so :)  having python-swiftclient be a well-regarded, easy to use  python client for Swift is a good goal; I'd like python devs who want to store and retrieve things to look at python-swiftclient and say, "Oh yeah, this is a breeze and does what I want" (not saying it's not already--I haven't looked at it from that perspective)19:24
chmouelor improve things like that https://github.com/reidrac/swift-nbd-server19:24
creihtI think there are plenty of opportunities19:25
creihtjust depends on the interest of those that show up19:25
notmynameya, tons of great ideas19:25
chmouelwe probably should start  a wiki page with the list of ideas19:25
swifterdarrellclayg: who does desktop apps?  Um, Cyberduck?  (which keeps coming up from real people as a client they're pointing at Swift)19:25
tongliI've noticed a lot of people have dropbox on their phone these days, including few 9 year-olders and I was bit surprised.19:25
claygI acctally had a question about the api thing (tahnks for bringing that up notmyname) - it kinda moved by quickly - should I wait?19:25
creihttongli: it is more difficult to do mobile dev with python19:26
notmynameclayg: let's move on. next topic is future plans for swift, so it fits there19:26
notmynamethanks for the great ideas for the sprint19:26
tonglideveloped a mobile app based on swift API will be useful and get product recongized by large number of people quickly.19:26
creihttongli: I totaly agree that mobile apps would also be useful :)19:26
tonglitrue!19:26
notmynametongli: provide a moble framework that app devs can use to store data in swift (ie what dropbox is doing)19:27
malinii like tongli mobile drop-box idea19:27
malinithat meets GUI, swift client ..19:27
creihtmalini: but this is a python conference, and the sprints are usually on python apps19:27
creihtwhich don't match well with mobile19:27
chmouelyeah not sure about the java part19:27
tonglisince we were talking about client. right true for that conf.19:27
notmynamecreiht: it did with the nokia OS ;-)19:27
tonglibut client app can be built regardless that that meeting/conf19:28
*** imcleod has joined #openstack-meeting19:28
creihtoh great, so the 1 person with a nokia os phone and a swift cluster to talk to could use it :)19:28
creihttongli: certainly19:28
tongliit will spread the Swift to bigger crowd.19:28
notmynamecreiht: symbian19:28
notmynamecreiht: http://en.wikipedia.org/wiki/Python_for_S6019:28
*** scotticus has joined #openstack-meeting19:29
notmynameok, moving on... :-)19:29
creihtlol19:29
notmyname#topic swift in 201319:29
*** diogogmt has quit IRC19:29
*** openstack changes topic to "swift in 2013 (Meeting topic: swift)"19:29
swifterdarrellwe gonna wikify the ideas somewhere?19:29
*** glange has joined #openstack-meeting19:29
notmynameswifterdarrell: ya, I'll scape the transcript for it19:29
*** ijw has joined #openstack-meeting19:29
creihtwe should start a wiki to keep track of all the stuff we want to wiki19:29
swifterdarrellcool19:29
notmynameclayg: what's your API question?19:29
claygwell so... we have some "optional" middleware right now "enahcnes" the api19:30
*** vishy is now known as vishy_zz19:31
claygdo those ever becomes part of the core api?  Like when you talk about what a POST means to the swift api - you have to talk about multipart forms and form-post (e.g.)19:31
creiht*crickets*19:33
creiht:)19:33
claygI just ask because we talk about client tools - they want to know what they can count on from a swift endpoint, and a major version bump might be a good time to "officialize" some of the api enhancements that already have momentum - or double check to see if they have any warts?19:33
notmynameclayg: so since there is no doc defining the swift api as a spec, the "swift API" has pretty much meant "what can an app reasonably expect a deployer to do"19:33
*** morganfainberg has quit IRC19:33
notmynameya, a mojor version bump (or any version bump) would require some more formal definition19:33
notmyname*probably19:33
swifterdarrelldiscoverability of what's supported in a particular deployment's implementation of the API could be handy; don't want to overcomplicate things, but being able to tell something about what middleware is around or how proxy-server's configured, etc could be useful19:34
notmynamebut I don't think that code organization affects what the API is (at least too much). IOW, it doesn't matter from an API perspective if it's in middleware or in the process19:34
*** ijw has quit IRC19:35
*** mrunge has quit IRC19:35
swifterdarrellI know the idea of exposing the configured swift limits was floated at one point19:35
clayg^ good example!19:35
uvirtbotclayg: Error: "good" is not a valid command.19:35
claygi hate you SO much uvirtbot19:35
yuanznotmyname: can I say that you will focus on the multi-region for swift 2013? seems there are lots of dependency on this in the blueprints page19:36
*** bdpayne has quit IRC19:36
notmynameclayg: example of discovering configured constraints as part of the API?19:36
swifterdarrellclayg: Error: "i hate you SO much uvirtbot" is not nice.19:36
torgomaticI like the middleware-queryability idea19:36
notmynameyuanz: ya, I'll get to that in just a bit19:36
creihthttps://developers.google.com/discovery/19:36
claygswifterdarrell: sorry19:37
swifterdarrelltorgomatic: I guess you can always "query" it by trying the API a middleware might be implementing and deduce its absence from the response19:37
alpha_oricreiht: interesting.19:37
swifterdarrelltorgomatic: doh, misread that as "I don't like"19:37
claygnotmyname: yeah something like discovery would "need to be there" so if it's done in middleware it couldn't really be "optional" in your pipeline?19:37
notmynameswifterdarrell: essentially the web client model for feature degredation19:38
creihtalpha_ori: yeah I haven't had a chance to dig real deep into it yet, but seems like they have done a lot in that domain19:38
*** markmcclain has quit IRC19:38
notmynameclayg: ya, but things like cache and check_errors aren't really optional either19:38
alpha_orinotmyname: That's what we do now with our web client to some degree.19:38
*** krtaylor has quit IRC19:39
alpha_orinotmyname: but that puts some burden on the client.19:39
notmynameya, it's not great. it's where we are today, and I do like the idea of discoverability19:39
creihtthe easiest (and could still be v1 compatible) would be to add some sort of capabilities resource19:40
caitlinbestlerAren't we talking about two different things here? 1) a presumably wsgi method to find out exactly what middleware modules are enabled, and 2) what the relevant configuration options are for the swift relevant modules?19:40
*** vishy_zz is now known as vishy19:40
creihta client could get that to know what apis are available19:40
maliniwould python decorators saying deprecated be adequate (java has deprecated tags)19:40
creihtcaitlinbestler: it could be depending on how it is implemented19:40
claygdiscoverability is great for *optional* elements, my originial question was really about getting things that clients want to count on in the api spec explicitly19:40
swifterdarrellSwift API 2.0 (or whatever) could define an API middlewares would implement, with, perhaps, proxy-server coughing up the proper "not present" response (for when an optional middleware isn't in the pipeline)19:40
*** markvoelker has joined #openstack-meeting19:41
notmynamecreiht: ya, I've got a (really, really dumb 30-minutes-spent-on-it) middleware in my github account that does that19:41
notmynameclayg: that would mean that we'd have to be explicit about the api19:41
claygI also don't like the idea of "discoveribility" being "what middleware is in the pipeline" - I should be able to conform to the api (including a well speced ehancement) even if I'm running a *different* middleware that the one that comes stock?19:41
notmynamewhich would be a change19:41
notmynameclayg: like the deb packaging "provides" directive (eg you get "mail" with both postfix and sendmail)19:42
alpha_oriclayg: interesting, but that would require defining standards for features themselves.19:42
alpha_oriclayg: not that we couldn't do that.19:42
torgomaticcould group things into conceptual "features"; then do something like OPTIONS /features/temporary-urls, and if it 404s, then tempurl's functionality isn't there19:42
alpha_oriclayg: What does it mean to provide S3 compatibility, for instance?19:43
*** yaguang has joined #openstack-meeting19:43
torgomaticthen you can reimplement tempurl's API to your heart's content, and just make sure your new fancy middleware says 200 to OPTIONS /features/temporary-urls19:43
swifterdarrellclayg: my idea was that middleware would say kind of what it can do; so like you said, the Swift API would define an optional form-post subset; any middleware purporting to support form-post functionality would implement that API including answing some kind of discovery req about it19:43
claygswifterdarrell: ok, that sounds reasonable19:44
swifterdarrellclayg: if an alternate implementation of Swift's optional subset API for form-post came along, it could conform to the discovery API response and be a drop-in replacement from a client perspective19:44
swifterdarrellclayg: (the point of APIs, right?)19:44
alpha_oriswifterdarrell: Do we yet have any examples of popular middleware that duplicate each other's efforts?19:44
claygalpha_ori: s3 is hard, but if someone wrote a "better than swift3" middleware for swift - clients checking for "does this endpoint support s3 api" shouldn't have to know if I've installed swift3 or the other?19:44
notmynamealpha_ori: auth19:44
*** vishy is now known as vishy_zz19:44
*** novas0x2a|laptop has joined #openstack-meeting19:45
alpha_orinotmyname: ok...anything else?19:45
*** markvoelker has quit IRC19:45
notmynameok, we only have a few more minutes. let's put dsicoverability off till later (would make a great summit topic)19:45
notmynameya19:45
*** shardy has joined #openstack-meeting19:45
*** vishy_zz is now known as vishy19:45
notmynamegeneral 2013 goals.19:45
claygswifterdarrell: I agree with 100%, i was worried for some reason that we'd  "return a list of middleware - discoverable - done"19:46
notmynamewhat use case are we looking to solve or enhance this year?19:46
creihtclayg: hehe19:46
creihtclayg: you always asume the worst :)19:46
notmynameglobal clusters is something that we (swiftstack) are working on now19:46
creihtnotmyname: any update as to where that is?19:47
swifterdarrellAs mentioned, global clusters has been a community desire since at least the Boston conference (and probably before)19:47
creihthow things are coming?19:47
*** shadower has joined #openstack-meeting19:47
swifterdarrellcreiht: well the first two patches are languishing in Gerrit pretty well19:47
torgomaticwell, ring enhancements are sitting in Gerrit (https://review.openstack.org/18263)19:47
*** reed has quit IRC19:47
creihtthere is a lot languishing in gerrit :)19:47
notmynamecreiht: isn't one of those waiting for a follow up from you? ;-)19:48
*** ccrouch has joined #openstack-meeting19:48
creihtnotmyname: like I said, my list keeps getting longer :)19:48
*** bdpayne has joined #openstack-meeting19:49
*** maoy has joined #openstack-meeting19:49
notmynameya, so global clusters has some patches in gerrit now, and the other functionality will be coming, I hope, over the next month19:49
creihtswifterdarrell: I was asking that rather than submit a couple of patches and wait, could you at least throw some stuff in WIP so people could see how things are taking shape overall?19:49
*** malini has quit IRC19:49
notmynamecreiht: our list is long too, we'll submit them when we can :-)19:50
swifterdarrellcreiht: because that'd speed up the reviews on the ready patches or because that'd be a good unrelated thing to have?19:50
creihtok, so then future patches aren't hinging on those approvals... good :)19:51
swifterdarrellcreiht: I think we'd like to submit a couple of patches and not have to wait (forever)19:51
creihtswifterdarrell: it would just be nice to see where things are going19:51
swifterdarrell;)19:51
notmynamebeyond global clusters, are there any other big things like that that your associated companies are working on? tiering? encryption ( caitlinbestler?) etc?19:51
creihtswifterdarrell: I think we can all agree that we all have a lot on our plates, and we are getting to things as we can19:51
swifterdarrellcreiht: yup!19:51
notmynamegenerally, what are you working on or planning that will go into the core of Swift?19:51
cschwedeMaybe not a big thing - but I'm working on a quota middleware19:52
creihtcschwede: have you seen the quota stuff that is currently in review?19:53
notmynamecschwede: ah, cool. have you seen mike barton's (redbo) patches19:53
swifterdarrellWe'll continue to improve Swift monitoring as we get to it (see: plates and the count of things on them), but nothing earth-shattering planned there19:53
cschwedecreiht: yes, my work is currently on an account level19:53
chmouelwe'll probaby work on some migration tools for swift (cluster to cluster) probably not something for Core19:54
cschwedenotmyname: no, will look into that. I talked to nijaba and chmouel (thanks for your comments!)19:54
*** caitlinbestler_ has joined #openstack-meeting19:54
notmynamechmouel: cool19:54
*** caitlinbestler has quit IRC19:55
claygwasn't rax looking at enhancements to object replication to leverage xfs internal data structures or do better prefix-hash-tree-rsync-faster-ninja-something?  or is object repliation still cycling "fast enough"?19:55
cschwedenotmyname: current working implementation supports tempauth, keystone and swauth: https://github.com/cschwede/swquota README is a little bit out of date - I'll update it tomorrow (added a tool for simpler quota set recently)19:55
creihtclayg: replication enhancements are still being looked into, but I think they have moved onto another idea19:55
caitlinbestler_Reconnecting -- on encryption - Nexenta is working on encryption but specifically on solutions that would *not* be part of swift core.19:55
yuanzswifterdarrell: by monitoring do you mean the statsd+graphit work, or a new tool?19:55
notmynamecaitlinbestler_: ok, good to know (I liek that approach, thanks for your ML comments)19:56
claygcreiht: awesome!19:56
chmouelcschwede: nice.. i am planning to test that sometime next week and we'll give you some feedback it could be nice to merge this with the redbo's container quota19:56
notmynameand we're pretty much out of time.. anything else for the last 3 minutes?19:56
swifterdarrellyuanz: I generally mean changes to core swift for emission of monitoring data (eg. statsd, but not graphite or any other consumer of StatsD output, which is outside the scope of core swift code)19:56
notmynamenext meeting is Feb 6 at 1900UTC19:57
yuanzok19:57
*** dosaboy has joined #openstack-meeting19:57
notmynameI'll put together a summary based on the transcript and send it out19:57
creihtnotmyname: redbo has some work on bit torrent support19:57
swifterdarrellyuanz: an example of "ongoing improvement" to that would be https://review.openstack.org/#/c/20089/19:57
notmynamecreiht: nice!19:57
creihthttps://github.com/rackspace/cloudfiles-sworrent19:58
creihtif anyone would like to provide some feedback19:58
*** jamespage_ has joined #openstack-meeting19:58
notmynamecreiht: 40419:58
creihtoh dangit19:58
creihtheh19:58
creihtI thought he made that public :)19:58
creihtwell once he is comfortable with others seeing it, I'll let you know :)19:58
notmynamecool19:58
cschwedechmouel: that would be nice - thanks!19:58
creihtnotmyname: I'm trying to play with better ways with handling metadata19:59
creihtbut that's very low priority19:59
creihtat the moment19:59
notmynamek19:59
notmynameand we're out of time19:59
notmynamethanks for attending. great feedback19:59
notmyname#endmeeting20:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:00
openstackMeeting ended Wed Jan 23 19:59:59 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-01-23-19.00.html20:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-01-23-19.00.txt20:00
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-01-23-19.00.log.html20:00
notmynamewow. perfect timing20:00
*** caitlinbestler_ has quit IRC20:00
sdake#startmeeting heat20:00
openstackMeeting started Wed Jan 23 20:00:19 2013 UTC.  The chair is sdake. 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: heat)"20:00
openstackThe meeting name has been set to 'heat'20:00
*** dfg has left #openstack-meeting20:00
*** zaneb has joined #openstack-meeting20:00
*** clayg has left #openstack-meeting20:00
sdake#topic rollcall20:00
*** openstack changes topic to "rollcall (Meeting topic: heat)"20:00
*** reed has joined #openstack-meeting20:00
zanebo/20:00
sdakesdake here20:00
cody-somervilleHi20:00
*** rafaduran has quit IRC20:00
sdakehowdy zaneb20:00
SpamapSo/20:00
stevebaker\O20:00
*** yuanz has left #openstack-meeting20:00
shardyshardy here20:00
*** adrian_smith has quit IRC20:00
sdakestevebaker has a big head ;)20:00
zanebDSL works this week :)20:01
sdakenice zaneb20:01
shadowerhey20:01
asalkeldhi20:01
jpeelerjpeeler here20:01
stevebakerfull house20:01
echoheadhi20:01
sdake#info sdake, cody-somrville, spamaps, stevebaker, shardy, zaneb, shadower, asalkeld, jpeeler, echohead present20:01
sdake#topic action review20:02
*** openstack changes topic to "action review (Meeting topic: heat)"20:02
sdake#info http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-01-16-20.00.html20:02
*** scotticus has left #openstack-meeting20:02
sdakenot sure what i was supposed to do with moving vpc resources to defn->approved - I think stevebaker was going to file separate blueprints for each vpc type20:03
*** cschwede has left #openstack-meeting20:03
stevebakerI've just done the blueprints20:03
sdakeok, i'll move that to next week then :)20:03
sdake#action sdake to follow up on stevebaker's vpc blueprints20:04
stevebaker#link https://blueprints.launchpad.net/heat/+spec/vpc-resources20:04
sdakestevebaker to take on ubuntu ppa20:04
stevebakerThey should all be hanging off that now20:04
sdakeany progress there?20:04
stevebakernothing this week, thats a long term project l)20:04
stevebaker020:04
sdakeok, will move off the weekly beating on that one ;)20:05
stevebakerbeat away20:05
sdake#action ubuntu PPA long term action20:05
sdake#topic blueprint review for g320:05
*** openstack changes topic to "blueprint review for g3 (Meeting topic: heat)"20:05
sdakehttps://launchpad.net/heat/+milestone/grizzly-320:05
sdakettx had asked us to sort out "Delivery" field20:05
sdakeif unknown, should go to started or not started20:06
sdakecan the assignees of the blueprint do that, since they are best suited to know the correct answer?20:06
asalkeldwhen i go to the bp there is no delivery20:07
zanebhow do you even do that?20:07
zanebyeah, what asalkeld said20:07
*** glange has left #openstack-meeting20:07
sdake"Implementation"20:07
SpamapSI think you mean Implementation20:07
stevebakerDoes the Definition need to be set to something other than New before that happens?20:07
*** krtaylor has joined #openstack-meeting20:07
zanebah yeah, Implementation did it20:08
*** cp16net|away is now known as cp16net20:08
*** dwcramer has quit IRC20:08
zanebthat seems like a bug in Launchpad20:08
sdakeclick through to the blueprint, then click "Implementation"20:08
Slowersorry here20:08
sdakeok, so asalkeld, shardy, stevebaker, jpeeler all have BPs, can you set the "Implementation" field then?20:09
*** maurosr has quit IRC20:09
* stevebaker does it now20:09
sdakethanks20:09
asalkeldyip20:09
shardysdake: done20:09
sdake#action asalkeld, shardy, stevebaker, jpeeler to set implementation field in BPs20:09
jpeeleris the implementation only changeable by the person who registered?20:10
sdakeyes20:10
SpamapSor assignee should also be able to do it20:10
sdakeor maybe only the asignee20:10
jpeeleri'm assigned, but have no way i see to change it. can sort it later20:10
sdakewe should go through these vpc priorities20:11
*** koolhead17 has quit IRC20:11
sdakei'd personally say they all should be hi20:11
SpamapSIts entirely possible that New has to be changed to a "defined" state for assignee to be allowed to mess with Implementation20:11
sdakegh20:11
SpamapSthe whole thing is rather opaque and designed to fit the ubuntu dev workflow20:11
sdakejpeeler use the force (ie: play with it ;)20:11
*** vipul is now known as vipul|away20:11
stevebakerThey should all be the same priority, whatever it is20:12
sdakeanyone have objections for high?20:12
SpamapSusually there's an approver (track lead) that sets Definition to Approved, and then the assignee is responsible from there20:12
stevebakernope20:12
sdakethanks spamaps, new to launchpad here ;)20:12
SpamapSso, if you want asignees to have full control, make them approvers too20:13
sdakethey are approvers I believe20:13
sdakewe can chat after meeting if you have a moment20:13
*** jog0 has joined #openstack-meeting20:13
sdake#action sdake to set all VPC blueprints to high20:13
SpamapShttps://blueprints.launchpad.net/heat/+spec/prebuilding-images <-- jpeeler is not approver, and definition is still Drafting20:14
sdake#topic preservation of resources20:14
*** openstack changes topic to "preservation of resources (Meeting topic: heat)"20:14
sdake#link https://blueprints.launchpad.net/heat/+spec/preserve-resources20:14
SpamapSoh thats me :)20:14
sdakemy initial thought is we have alot on our plate already for H - only 4 weeks left in the dev cycle20:15
SpamapSSo, I think this will take a good discussion at the summit to fully flesh out, but I need to put together some PoC implementations before then so I thought I'd bring it up now20:15
sdake15 blueprints, about 25 bugs to fix20:15
sdakeya, open to discussions at summit20:15
stevebakerThis looks like another umbrella blueprint, which could do with a sub blueprint that specifies what each resource should do20:16
asalkeldSpamapS, that behaviour is what we want20:16
sdakepoc sounds good so people have a chance to see whats there20:16
SpamapSI wanted to spitball a few ideas here and get people thinking about it now.20:16
asalkeldno need for poc20:16
asalkeldjust implement20:16
zanebis this proposal somehow different from what AWS has already?20:16
SpamapSas I say in the description, I'm not sure whether a new field, UpdatePolicy, or a whole new resource type would be best.20:16
SpamapSzaneb: yes20:17
zanebin what way?20:17
shardySpamapS: I believe that behavior will be provided by the UpdateStack blueprint I have for instance resources20:17
SpamapSzaneb: as far as I can tell, AWS will not let you update an instance's userdata without at least rebooting (EBS) or at worst terminate/create(instance store)20:17
asalkeldaaaa20:17
SpamapSIts also not well defined what happens if you just update Metadata20:18
asalkeldyes userdata is readonly20:18
shardySpamapS: we can just re-parse the template via UpdateStack and then update the instance metadata20:18
shardythat will then get picked up via cfn-hup20:18
shardywhich AFAICT is exactly what AWS does20:18
asalkeldbut can't you put your data into metadata20:18
asalkeldya20:18
asalkelduserdata is bootup only20:18
shardyNo, cfn hup reads the metadata via the CFN API now (or at least it can20:18
SpamapSSo perhaps I just didn't read the AWS docs well.. I couldn't find anywhere that Metadata's update behavior was defined.20:19
shardyif you provide credentials it will poll the CFN API for metadata updates20:19
zanebUpdate requires:20:19
zanebUpdate requires: some interruptions (EBS-backed AMIs)20:19
zanebUpdate requires: replacement (instance-store backed AMIs)20:19
zanebAWS docs ^20:19
SpamapSzaneb: for userdata, or metadata?20:19
zanebUserData20:19
*** esker has quit IRC20:19
SpamapSYeah so I need it to not reboot or replace.20:19
SpamapSAnd I do think Metadata should be changable without replacement. Right?20:20
asalkeldthe trick is to put as much as possible in the metadata20:20
asalkeldshould be20:20
asalkeldyes20:20
shardybut what we call metadata internally (for AWS::Cloudformation::Init) is not the same as EC2 metadata20:20
shardywe send that metadata via user data, and it can be updated via the CFN API route described above20:20
shardyie we can update the stuff done by cfn-init, but not cloud-init20:21
asalkeldyou need to poll it using cfn-hup20:21
SpamapSshardy: yes I nyes, thats yes, the heat metadata is what I call it20:21
SpamapSsorry, lag issues here causing keyboard fail20:21
sdakeok, sounds like some debate about what can/can't be done - perhaps can sort out if this is already possible in #heat over the coming week and bring up for discussion next week?20:21
shardyasalkeld: yep, but we already have that, so we just need to implement the capability to update the metadata parsed as part of the AWS::Cloudformation::Init section of the intance definition in the template20:22
SpamapSYes that sounds great20:22
SpamapSshardy: not just AWS::Cloudformation::Init though20:22
SpamapSshardy: the whole Metadata block20:22
shardysdake: FWIW, I was planning to implement (or at least try to implement) this next week20:22
sdake#action heat devs to sort out if updatestack can update rather then delete in coming week20:22
sdakecool sounds good :)20:22
SpamapSCool, I have cycles to help with this btw20:23
shardySpamapS: Ok, lets pick this up and work together to figure it out :)20:23
SpamapSindeed20:23
sdake#topic open discussion20:23
*** openstack changes topic to "open discussion (Meeting topic: heat)"20:23
sdakeok good work on the bugs - making good progress20:23
sdakeremember our deadline is t-4 weeks20:23
sdakeneed to fix the bugs and fix the blueprints by then20:23
*** dwcramer has joined #openstack-meeting20:23
sdakeif you have something assigned to you that isn't going to make it, earlier notification better then later20:24
*** cp16net is now known as cp16net|away20:24
SpamapSI poked at a few. Not many unassigned.. will continue to sift through them though.20:24
asalkeldSpamapS, shardy another option is to support configdrive20:24
SpamapSasalkeld: not an option for my use case.20:24
asalkeldok20:24
SpamapSnova baremetal may one day support configdrive..20:24
shardyasalkeld: Not looked into that myself, was thinking, lets just use cfn-hup since we already have it working20:24
SpamapSbut that would require some iscsi hackery that we haven't done yet20:24
SpamapS+1 cfn-hup is the way to go IMO20:25
asalkeldsure20:25
sdakeif you have alot of bugs assigned to you (I think this applies mostly to shardy) might think about releasing some of the easier ones for new community members to take on20:26
shardysdake: most of mine are pretty easy I think, should be OK but will check20:26
sdakeok - well up to you ;)20:26
sdakejust dont need to work a million hours a week - community effort here20:26
zanebSpamapS, shardy: http://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/using-cfn-updating-stacks.html implies that a standard UpdateStack is always able to update metadata20:27
*** cp16net|away is now known as cp16net20:27
shardysdake: k, will release any I'm not confident I'll finish20:27
sdakeok any other open discussion?20:27
asalkeldnope20:28
SpamapSzaneb: lets discuss further in #heat :)20:28
sdakeok thanks guys short meeting today ftw ;)20:28
sdake#endmeeting20:28
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:28
openstackMeeting ended Wed Jan 23 20:28:38 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:28
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-01-23-20.00.html20:28
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-01-23-20.00.txt20:28
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-01-23-20.00.log.html20:28
SpamapSsdake: thanks for chairing20:28
*** markmcclain has joined #openstack-meeting20:29
*** bencherian has quit IRC20:30
*** jsavak has quit IRC20:30
*** krtaylor has quit IRC20:32
*** dcramer_ has joined #openstack-meeting20:34
*** shadower has quit IRC20:35
*** vipul|away is now known as vipul20:37
*** dwcramer has quit IRC20:37
*** juice has quit IRC20:40
*** markvan has joined #openstack-meeting20:40
*** alexpilotti has quit IRC20:40
*** alexpilotti has joined #openstack-meeting20:41
*** markvoelker has joined #openstack-meeting20:41
*** juice_otg has joined #openstack-meeting20:44
*** markvoelker has quit IRC20:46
*** asparks has left #openstack-meeting20:47
*** joesavak has joined #openstack-meeting20:51
*** dosaboy has quit IRC20:54
*** krtaylor has joined #openstack-meeting20:54
*** dosaboy has joined #openstack-meeting20:54
*** cp16net is now known as cp16net|away20:58
*** bencherian has joined #openstack-meeting20:58
*** jamespage_ has quit IRC20:59
*** sdake has quit IRC20:59
*** iben1 has joined #openstack-meeting21:02
*** sandywalsh has quit IRC21:04
*** thouvenin has joined #openstack-meeting21:08
*** debo-os has joined #openstack-meeting21:08
*** thouvenin has quit IRC21:12
*** dcramer_ has quit IRC21:12
*** EmilienM has joined #openstack-meeting21:15
*** sarob has joined #openstack-meeting21:15
*** yaguang has quit IRC21:16
*** yaguang has joined #openstack-meeting21:17
*** dani4571 has joined #openstack-meeting21:17
*** debo-os has quit IRC21:18
*** dprince has quit IRC21:21
*** krtaylor has quit IRC21:22
*** dcramer_ has joined #openstack-meeting21:24
*** cp16net|away is now known as cp16net21:38
*** iben1 has quit IRC21:40
*** iben has joined #openstack-meeting21:41
*** markvoelker has joined #openstack-meeting21:42
*** krtaylor has joined #openstack-meeting21:42
*** juice has joined #openstack-meeting21:43
*** markvoelker has quit IRC21:46
*** sarob has quit IRC21:46
*** dcramer_ has quit IRC21:50
*** sdake_z has quit IRC22:00
*** radez is now known as radez_g0n322:03
*** sarob has joined #openstack-meeting22:04
*** sarob_ has joined #openstack-meeting22:08
*** juice_otg has quit IRC22:10
*** sarob has quit IRC22:10
*** iben has quit IRC22:21
*** dolphm has quit IRC22:25
*** danwent has quit IRC22:30
*** dani4571 has quit IRC22:31
*** reed has quit IRC22:34
*** stevebaker has quit IRC22:36
*** jog0 has quit IRC22:37
*** mtreinish has quit IRC22:41
*** annegentle has quit IRC22:43
*** sdake_z has joined #openstack-meeting22:45
*** joesavak has quit IRC22:45
*** juice has quit IRC22:48
*** markvan has quit IRC22:48
*** tongli has quit IRC22:50
*** juice has joined #openstack-meeting22:51
*** jkyle has quit IRC22:52
*** jcmartin has quit IRC22:56
*** john5223 has quit IRC22:56
*** stevebaker has joined #openstack-meeting22:57
*** shardy has quit IRC22:57
*** mpdehaan has quit IRC22:57
*** vkmc has quit IRC23:01
*** danwent has joined #openstack-meeting23:01
*** anniec has quit IRC23:01
*** anniec has joined #openstack-meeting23:05
*** blamar has quit IRC23:07
*** blamar has joined #openstack-meeting23:07
*** afazekas has quit IRC23:08
*** topol has quit IRC23:13
*** gyee has quit IRC23:15
*** lloydde has quit IRC23:21
*** markvan has joined #openstack-meeting23:24
*** EmilienM has quit IRC23:24
*** salv-orlando has joined #openstack-meeting23:24
*** maoy has quit IRC23:25
*** ladquin is now known as ladquin_brb23:27
*** henrynash has joined #openstack-meeting23:27
*** jcmartin has joined #openstack-meeting23:28
*** krtaylor has quit IRC23:31
*** fnaval has quit IRC23:31
*** ewindisch has quit IRC23:32
*** ewindisch has joined #openstack-meeting23:32
*** dtalton has quit IRC23:35
*** dolphm has joined #openstack-meeting23:36
*** galthaus has quit IRC23:40
*** dolphm_ has joined #openstack-meeting23:41
*** dolphm has quit IRC23:41
*** alexpilotti has quit IRC23:41
*** dolphm has joined #openstack-meeting23:42
*** dolphm_ has quit IRC23:42
*** markvoelker has joined #openstack-meeting23:43
*** diogogmt has joined #openstack-meeting23:44
*** markvoelker has quit IRC23:48
*** DuncanT has quit IRC23:48
*** AlanClark has quit IRC23:50
*** eharney has quit IRC23:50
*** DuncanT has joined #openstack-meeting23:53
*** markvan has quit IRC23:54
*** iben1 has joined #openstack-meeting23:55
*** dwcramer has joined #openstack-meeting23:55
*** blamar has quit IRC23:59
*** kebray has joined #openstack-meeting23:59

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