Wednesday, 2013-06-26

*** zhuadl has joined #openstack-meeting00:03
*** MarkAtwood has joined #openstack-meeting00:04
*** lastidiot has joined #openstack-meeting00:04
*** ryanpetrello has quit IRC00:10
*** virajh has quit IRC00:10
*** markwash has quit IRC00:12
*** epim has quit IRC00:16
*** NothingDone has quit IRC00:16
*** NothingDone has joined #openstack-meeting00:16
*** cliu has joined #openstack-meeting00:16
*** RajeshMohan has quit IRC00:24
*** cliu has quit IRC00:25
*** RajeshMohan has joined #openstack-meeting00:26
*** IlyaE has quit IRC00:35
*** bdpayne has quit IRC00:36
*** sleepsontheflo-1 has quit IRC00:37
*** cliu has joined #openstack-meeting00:39
*** noslzzp has quit IRC00:39
*** rwsu is now known as rwsu-away00:41
*** bdpayne has joined #openstack-meeting00:44
*** dstanek has joined #openstack-meeting00:44
*** vipul is now known as vipul|away00:45
*** yaguang has joined #openstack-meeting00:47
*** hanrahat_ has quit IRC00:50
*** Mandell has quit IRC00:52
*** cliu has quit IRC00:53
*** alexpilotti has quit IRC00:54
*** vipul|away is now known as vipul00:55
*** lloydde_ has quit IRC00:57
*** zhuadl has quit IRC00:59
*** dcramer_ has joined #openstack-meeting01:02
*** MarkAtwood has quit IRC01:04
*** SumitNaiksatam has joined #openstack-meeting01:07
*** gyee has quit IRC01:10
*** mikal has quit IRC01:13
*** dcramer_ has quit IRC01:14
*** tanisdl has quit IRC01:15
*** mikal has joined #openstack-meeting01:15
*** ryanpetrello has joined #openstack-meeting01:17
*** IlyaE has joined #openstack-meeting01:18
*** ryanpetrello has quit IRC01:19
*** MarkAtwood has joined #openstack-meeting01:21
*** MarkAtwood has quit IRC01:22
*** ryanpetrello has joined #openstack-meeting01:25
*** IlyaE has quit IRC01:26
*** yuanz has quit IRC01:34
*** terry7 has quit IRC01:37
*** IlyaE has joined #openstack-meeting01:38
*** kebray has joined #openstack-meeting01:39
*** ozstacker has joined #openstack-meeting01:41
*** bdpayne has quit IRC01:42
*** _ozstacker_ has quit IRC01:43
*** adalbas has quit IRC01:47
*** IlyaE has quit IRC01:48
*** kebray has quit IRC01:54
*** zehicle_at_dell has joined #openstack-meeting02:06
*** zigo has quit IRC02:09
*** zigo has joined #openstack-meeting02:10
*** shang has joined #openstack-meeting02:11
*** ctracey` has quit IRC02:11
*** noslzzp has joined #openstack-meeting02:12
*** ctracey|away has joined #openstack-meeting02:13
*** ctracey|away is now known as ctracey02:13
*** cody-somerville has quit IRC02:18
*** abhisri has joined #openstack-meeting02:19
*** fnaval has joined #openstack-meeting02:19
*** IlyaE has joined #openstack-meeting02:19
*** nati_ueno has quit IRC02:21
*** abhisri has quit IRC02:21
*** IlyaE has quit IRC02:22
*** shang has quit IRC02:23
*** sdake has quit IRC02:23
*** bdpayne has joined #openstack-meeting02:25
*** stevemar has joined #openstack-meeting02:26
*** matiu has quit IRC02:35
*** shang has joined #openstack-meeting02:36
*** dstanek has quit IRC02:38
*** novas0x2a|laptop has quit IRC02:49
*** shang has quit IRC02:50
*** woodspa has quit IRC02:52
*** sleepsonthefloor has joined #openstack-meeting02:53
*** dcramer_ has joined #openstack-meeting02:57
*** shang has joined #openstack-meeting03:03
*** leizhang has joined #openstack-meeting03:08
*** litong has quit IRC03:15
*** timello_ has joined #openstack-meeting03:16
*** fnaval has quit IRC03:17
*** timello has quit IRC03:18
*** fnaval has joined #openstack-meeting03:18
*** stevemar has quit IRC03:19
*** alexpilotti has joined #openstack-meeting03:19
*** alexpilotti has quit IRC03:25
*** neelashah has joined #openstack-meeting03:43
*** gongysh has joined #openstack-meeting03:51
*** zehicle_at_dell has quit IRC03:58
*** zehicle_at_dell has joined #openstack-meeting03:58
*** martine has joined #openstack-meeting03:58
*** IlyaE has joined #openstack-meeting04:02
*** nati_ueno has joined #openstack-meeting04:04
*** nati_ueno has quit IRC04:05
*** nati_ueno has joined #openstack-meeting04:05
*** bdpayne has quit IRC04:11
*** martine_ has joined #openstack-meeting04:14
*** cliu has joined #openstack-meeting04:14
*** martine has quit IRC04:18
*** rostam has quit IRC04:20
*** rostam has joined #openstack-meeting04:23
*** shang has quit IRC04:26
*** afazekas has joined #openstack-meeting04:29
*** lloydde has joined #openstack-meeting04:31
*** Mandell has joined #openstack-meeting04:31
*** haomaiwang has joined #openstack-meeting04:37
*** dcramer_ has quit IRC04:37
*** IlyaE has quit IRC04:37
*** martine_ has quit IRC04:44
*** martine has joined #openstack-meeting04:45
*** koolhead11|away has joined #openstack-meeting04:50
*** cody-somerville has joined #openstack-meeting04:51
*** shang has joined #openstack-meeting04:52
*** nati_uen_ has joined #openstack-meeting04:53
*** nati_uen_ has quit IRC04:53
*** nati_uen_ has joined #openstack-meeting04:54
*** nati_ueno has quit IRC04:56
*** koolhead11|away is now known as koolhead1704:57
*** noslzzp has quit IRC05:00
*** kebray has joined #openstack-meeting05:00
*** colinmcnamara has joined #openstack-meeting05:01
*** neelashah has quit IRC05:02
*** ryanpetrello has quit IRC05:09
*** SergeyLukjanov has joined #openstack-meeting05:11
*** gongysh has quit IRC05:13
*** martine has quit IRC05:18
*** lastidiot has quit IRC05:20
*** haomaiwang has quit IRC05:25
*** haomaiwang has joined #openstack-meeting05:26
*** colinmcnamara has quit IRC05:26
*** cdub_ has quit IRC05:28
*** kebray has quit IRC05:36
*** kebray has joined #openstack-meeting05:37
*** lloydde has quit IRC05:41
*** kebray has quit IRC05:41
*** nati_ueno has joined #openstack-meeting05:48
*** nati_ueno has quit IRC05:49
*** nati_ueno has joined #openstack-meeting05:51
*** nati_uen_ has quit IRC05:51
*** zhuadl has joined #openstack-meeting05:51
*** nati_ueno has quit IRC05:52
*** jcoufal has joined #openstack-meeting05:52
*** nati_ueno has joined #openstack-meeting05:53
*** jhenner has joined #openstack-meeting05:56
*** zhuadl has quit IRC05:56
*** lloydde has joined #openstack-meeting06:02
*** zhuadl has joined #openstack-meeting06:04
*** SergeyLukjanov has quit IRC06:04
*** tayyab has joined #openstack-meeting06:22
*** psedlak has joined #openstack-meeting06:28
*** egallen has joined #openstack-meeting06:31
*** ozstacker has quit IRC06:44
*** ozstacker has joined #openstack-meeting06:45
*** hanrahat has joined #openstack-meeting06:46
*** eglynn has joined #openstack-meeting06:46
*** hanrahat has quit IRC06:50
*** eglynn has quit IRC06:54
*** tkammer_ has joined #openstack-meeting07:02
*** dkehn has joined #openstack-meeting07:03
*** timello_ has quit IRC07:09
*** timello_ has joined #openstack-meeting07:10
*** jhenner has quit IRC07:10
*** gongysh has joined #openstack-meeting07:12
*** cliu has quit IRC07:13
*** jtomasek has joined #openstack-meeting07:13
*** pnavarro has joined #openstack-meeting07:15
*** egallen has quit IRC07:17
*** egallen has joined #openstack-meeting07:18
*** lloydde has quit IRC07:18
*** lukego has joined #openstack-meeting07:19
*** lloydde has joined #openstack-meeting07:19
*** koolhead17 has quit IRC07:23
*** sushils has joined #openstack-meeting07:23
*** lloydde has quit IRC07:24
*** zhuadl has quit IRC07:29
*** jhenner has joined #openstack-meeting07:37
*** zhuadl has joined #openstack-meeting07:37
*** lloydde has joined #openstack-meeting07:49
*** johnthetubaguy has joined #openstack-meeting07:54
*** lloydde has quit IRC07:58
*** tayyab_ has joined #openstack-meeting08:02
*** tayyab_ has quit IRC08:03
*** tayyab_ has joined #openstack-meeting08:03
*** tayyab has quit IRC08:04
*** huats has joined #openstack-meeting08:05
*** huats has quit IRC08:05
*** huats has joined #openstack-meeting08:05
*** tzn has quit IRC08:05
*** eglynn has joined #openstack-meeting08:08
*** Mandell has quit IRC08:09
*** huats has quit IRC08:12
*** huats has joined #openstack-meeting08:13
*** huats has quit IRC08:13
*** huats has joined #openstack-meeting08:13
*** derekh has joined #openstack-meeting08:17
*** nati_ueno has quit IRC08:17
*** afazekas_ has joined #openstack-meeting08:23
*** afazekas_ has quit IRC08:23
*** afazekas_ has joined #openstack-meeting08:24
*** nati_ueno has joined #openstack-meeting08:24
*** reed has joined #openstack-meeting08:25
*** tayyab_ has quit IRC08:26
*** tayyab has joined #openstack-meeting08:28
*** haomaiwang has quit IRC08:35
*** SergeyLukjanov has joined #openstack-meeting08:49
*** lloydde has joined #openstack-meeting08:49
*** salv-orlando_ has joined #openstack-meeting08:54
*** salv-orlando has quit IRC08:54
*** salv-orlando_ is now known as salv-orlando08:54
*** lloydde has quit IRC08:54
*** mikal has quit IRC08:57
*** mikal has joined #openstack-meeting08:58
*** mkollaro has joined #openstack-meeting09:02
*** agordeev has joined #openstack-meeting09:04
*** johnthetubaguy has quit IRC09:08
*** johnthetubaguy has joined #openstack-meeting09:08
*** nati_ueno has quit IRC09:17
*** ttrifonov is now known as ttrifonov_zZzz09:20
*** ozstacker has quit IRC09:21
*** ttrifonov_zZzz is now known as ttrifonov09:22
*** ozstacker has joined #openstack-meeting09:22
*** shang has quit IRC09:32
*** boris-42 has quit IRC09:39
*** lloydde has joined #openstack-meeting09:50
*** dabo has joined #openstack-meeting09:51
*** sivel has joined #openstack-meeting09:51
*** briancline has joined #openstack-meeting09:51
*** cyeoh has joined #openstack-meeting09:52
*** lloydde has quit IRC09:55
*** pcm___ has joined #openstack-meeting10:04
*** pcm___ has quit IRC10:04
*** psedlak has quit IRC10:04
*** pcm__ has joined #openstack-meeting10:05
*** dstanek has joined #openstack-meeting10:05
*** fifieldt has joined #openstack-meeting10:14
*** shang has joined #openstack-meeting10:18
*** yaguang has quit IRC10:21
*** NothingDone has quit IRC10:26
*** zul has quit IRC10:27
*** zul has joined #openstack-meeting10:29
*** NothingDone has joined #openstack-meeting10:30
*** lukego has quit IRC10:32
*** psedlak has joined #openstack-meeting10:33
*** tzn has joined #openstack-meeting10:41
*** leizhang has quit IRC10:42
*** tzn has quit IRC10:48
*** gongysh has quit IRC10:50
*** lloydde has joined #openstack-meeting10:50
*** lloydde has quit IRC10:55
*** timello_ has quit IRC10:58
*** timello_ has joined #openstack-meeting10:59
*** pnavarro has quit IRC10:59
*** sungju_ has joined #openstack-meeting11:02
*** sungju_ has quit IRC11:02
*** ndipanov has quit IRC11:03
*** tzn has joined #openstack-meeting11:07
*** lukego has joined #openstack-meeting11:14
*** zhuadl has quit IRC11:14
*** ndipanov has joined #openstack-meeting11:16
*** dkranz has quit IRC11:18
*** fifieldt has quit IRC11:19
*** HenryG has joined #openstack-meeting11:20
*** boris-42 has joined #openstack-meeting11:23
*** sdake has joined #openstack-meeting11:26
*** sdake has quit IRC11:26
*** sdake has joined #openstack-meeting11:26
*** tayyab has quit IRC11:27
*** rscottcoyle has joined #openstack-meeting11:30
*** garyk has joined #openstack-meeting11:30
*** eglynn has quit IRC11:40
*** vkmc has joined #openstack-meeting11:41
*** vkmc has joined #openstack-meeting11:41
*** vkmc has quit IRC11:44
*** vkmc has joined #openstack-meeting11:45
*** vkmc has joined #openstack-meeting11:45
*** dstanek has quit IRC11:47
*** dkranz has joined #openstack-meeting11:49
*** lloydde has joined #openstack-meeting11:51
*** rnirmal has joined #openstack-meeting11:51
*** tedross has joined #openstack-meeting11:51
*** tkammer_ has quit IRC11:55
*** jcoufal has quit IRC11:55
*** afazekas_ has quit IRC11:55
*** jhenner has quit IRC11:55
*** martine has joined #openstack-meeting11:56
*** noslzzp has joined #openstack-meeting11:59
*** eharney has joined #openstack-meeting11:59
*** eharney has joined #openstack-meeting11:59
*** flaper87 has joined #openstack-meeting11:59
*** psedlak_ has joined #openstack-meeting12:01
*** mkollaro has quit IRC12:02
*** jcoufal has joined #openstack-meeting12:02
*** mkollaro has joined #openstack-meeting12:02
*** psedlak has quit IRC12:02
*** dprince has joined #openstack-meeting12:05
*** tayyab_ has joined #openstack-meeting12:05
*** lloydde has quit IRC12:05
*** dstanek has joined #openstack-meeting12:06
*** SergeyLukjanov has quit IRC12:07
*** CaptTofu_ has quit IRC12:10
*** afazekas_ has joined #openstack-meeting12:13
*** ndipanov has quit IRC12:13
*** SergeyLukjanov has joined #openstack-meeting12:17
*** haomaiwang has joined #openstack-meeting12:21
*** tkammer_ has joined #openstack-meeting12:21
*** afazekas_ has quit IRC12:21
*** ndipanov has joined #openstack-meeting12:25
*** ryanpetrello has joined #openstack-meeting12:30
*** zhuadl has joined #openstack-meeting12:34
*** dstanek has quit IRC12:34
*** pnavarro has joined #openstack-meeting12:42
*** dhellmann-away is now known as dhellmann12:42
*** lbragstad has quit IRC12:43
*** sandywalsh has quit IRC12:45
*** SergeyLukjanov has quit IRC12:48
*** leizhang has joined #openstack-meeting12:49
*** noslzzp has quit IRC12:51
*** lloydde has joined #openstack-meeting12:51
*** noslzzp has joined #openstack-meeting12:56
*** lloydde has quit IRC12:56
*** sandywalsh has joined #openstack-meeting12:59
*** psedlak__ has joined #openstack-meeting13:02
*** litong has joined #openstack-meeting13:03
*** psedlak_ has quit IRC13:03
*** mkollaro has quit IRC13:03
*** martine_ has joined #openstack-meeting13:03
*** martine has quit IRC13:04
*** bdpayne has joined #openstack-meeting13:05
*** gongysh has joined #openstack-meeting13:06
*** jtomasek has quit IRC13:06
*** jtomasek has joined #openstack-meeting13:07
*** SergeyLukjanov has joined #openstack-meeting13:09
*** BrianB has joined #openstack-meeting13:10
*** ayoung has joined #openstack-meeting13:11
*** zehicle_at_dell has quit IRC13:11
*** lbragstad has joined #openstack-meeting13:11
*** krtaylor has quit IRC13:12
*** vijendar has joined #openstack-meeting13:14
*** dolphm has joined #openstack-meeting13:14
*** egallen has quit IRC13:16
*** cp16net is now known as cp16net|away13:16
*** egallen has joined #openstack-meeting13:16
*** egallen has quit IRC13:17
*** dkranz has quit IRC13:21
*** afazekas_ has joined #openstack-meeting13:25
*** tkammer_ has quit IRC13:26
*** neelashah has joined #openstack-meeting13:28
*** tkammer has joined #openstack-meeting13:29
*** dhellmann is now known as dhellmann-away13:31
*** yaguang has joined #openstack-meeting13:31
*** fmanco has joined #openstack-meeting13:31
*** yaguang has quit IRC13:34
*** afazekas_ has quit IRC13:34
*** mkollaro has joined #openstack-meeting13:35
*** tedross has quit IRC13:36
*** dkranz has joined #openstack-meeting13:36
*** tedross has joined #openstack-meeting13:37
*** dcramer_ has joined #openstack-meeting13:43
*** jecarey_ has joined #openstack-meeting13:44
*** markpeek has joined #openstack-meeting13:47
*** noslzzp has quit IRC13:48
*** stevemar has joined #openstack-meeting13:48
*** matrohon has joined #openstack-meeting13:48
*** fnaval has quit IRC13:49
*** kevinconway has left #openstack-meeting13:50
*** krtaylor has joined #openstack-meeting13:51
*** mtreinish has joined #openstack-meeting13:51
*** zehicle_at_dell has joined #openstack-meeting13:51
*** lloydde has joined #openstack-meeting13:52
*** noslzzp has joined #openstack-meeting13:52
*** kevinconway has joined #openstack-meeting13:56
*** vijendar has quit IRC13:56
*** lloydde has quit IRC13:57
*** apech has joined #openstack-meeting13:58
*** rkukura has joined #openstack-meeting13:59
mesteryHi folks, ready for the networking_ml2 meeting?14:00
*** rcurran has joined #openstack-meeting14:00
mestery#startmeeting networking_ml214:00
openstackMeeting started Wed Jun 26 14:00:26 2013 UTC.  The chair is mestery. Information about MeetBot at http://wiki.debian.org/MeetBot.14:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:00
*** openstack changes topic to " (Meeting topic: networking_ml2)"14:00
openstackThe meeting name has been set to 'networking_ml2'14:00
mestery#link https://wiki.openstack.org/wiki/Meetings/ML2 Agenda14:00
*** rwsu-away is now known as rwsu14:01
mestery#topic MechanismDriver14:01
*** openstack changes topic to "MechanismDriver (Meeting topic: networking_ml2)"14:01
mesteryapech: Here?14:01
apechyup14:01
*** doude_ has joined #openstack-meeting14:01
mestery#link https://review.openstack.org/33201 MechanismDriver review14:01
rkukuragood morning!14:01
mesteryapech: Great! Can you provide an update on MechanismDriver?14:01
*** garyk has quit IRC14:01
mesteryrkukura: Good morning to you too!14:02
apechSure. I posted a new review on Sunday. I hope that I've addressed everyone's comments. rcurran took a look through, am hoping to get a few more eyeballs on it14:02
apechIt does not yet have subnet support, and unit testing could be better14:02
rkukuraI'll do a detailed review today or tomorrow at the latest.14:02
apechbut hopefully it's converging to a more stable point14:02
mesteryapech: It's on my list, I'll do a review tomorrow as I'm on PTO rest of the day after this meeting.14:02
apechrkukura: that's be great, thanks!14:02
mesteryrcurran had sent an email with some issues which may be interesting to the MechanismDriver around things like DBs, etc.14:03
mesteryrcurran: Want to discuss that now quickly?14:03
rcurranin creating the ml2 version of cisco nexus14:04
*** shang has quit IRC14:04
rcurrani'm coming across code in the cisco version that may need to be added to ml2 common code14:04
rcurrandb, exceptions, xml snippets, etc14:04
rcurranwas curious if arista guys are coming across the same issues14:05
rkukuraare these common across different ml2 drivers, or more widely?14:05
*** vijendar has joined #openstack-meeting14:05
rcurranor more restrictive14:05
*** feleouet has joined #openstack-meeting14:06
rcurrani.e. may only apply to cisco14:06
rcurranbut can be made common14:06
rkukurado you mean common across a subset of ml2 drivers?14:06
rcurranright14:06
*** markmcclain has joined #openstack-meeting14:06
apechrcurran: Sukhdev isn't on, he'd be a better person to comment on the Arista drivers. My guess is that they'll be common14:06
rkukurahave we decided on whether sets of related drivers (such as cisco) should be in a subdir of ml2/drivers?14:06
apechsetting up the separate directories seems right14:06
rcurranor maybe, i should say ... i don't know anything about arista implementation of their plugins14:07
apechrkurkura: I thought we decided to put it all under drivers14:07
mesteryrkukura: I think the subdir makes sense for sets of common drivers.14:07
rkukuraI have no objection to a subdir for a closely-related set of drivers14:07
*** mrodden has joined #openstack-meeting14:07
apechyeah, subdir under drivers seems fine14:07
rkukuratype drivers should generally go at the top level since they are intended to apply across mechanisms14:07
rkukuraone goal would be to keep packaging easy - so the entire subdir can be packaged separately if needed14:08
*** ayurchen has quit IRC14:08
apechrcurran: to your original question, if you send us the files you had in mind, we can review and help provide feedback14:08
*** ayurchen has joined #openstack-meeting14:08
apechbut my guess is that we will end up with some common infrastructure for all mechanism drivers14:09
mesteryapech: Agreed, there is some common code there for sure.14:09
*** shang has joined #openstack-meeting14:09
rcurranok, i'm still porting over cisco_nexus, when i get closer to being done i'll send out more detailed info on what i think can possibly be made common14:09
rkukuraanything shared with other plugins or agents should probably be in quantum/common, right?14:09
mestery#action rcurran to send email or review notes for details on common code14:10
rkukuragreat14:10
*** cdub_ has joined #openstack-meeting14:10
mesteryOK, anything else to discuss on MechanismDriver?14:10
mestery#topic ml2-portbinding14:11
*** openstack changes topic to "ml2-portbinding (Meeting topic: networking_ml2)"14:11
mestery#link https://blueprints.launchpad.net/quantum/+spec/ml2-portbinding ml2-portbinding blueprint14:11
mesteryrkukura: portbinding update?14:11
rkukuranothing new on portbinding - should start coding today or tomorrow14:11
rkukuralooks like other plugins are starting to address this as well14:11
mesteryrkukura: OK, cool! I think that will be the next piece that MechanismDriver writers will be waiting for.14:12
apechrkukura: do you have a sense of when you'll have an initial version?14:12
*** michchap has quit IRC14:12
rkukuraI'll shoot for Monday14:12
apechrkukura: that'd be awesome, thanks!14:12
rkukuraCan we get the initial MechanismDrivers merged by then?14:12
mesteryrkukura: cool!14:12
mesteryrkukura: You mean the arista and cisco mech drivers, or the blueprint apech is working on?14:13
rkukurathe BP all these depend on14:13
apechI would love to - appreciate the review14:13
apechand I'll focus on beefing up the testing between now and then14:13
rkukuraso a question was raised about putting the nova instance name on the port14:13
apechyeah - that's something we'd be interested in on the Arista side14:13
mestery#action ML2 subteam to try to get MechanismDriver blueprint merged before Monday 7-1-2013.14:13
*** zhuadl has quit IRC14:13
*** lastidiot has joined #openstack-meeting14:13
rkukuraor at least having ml2 make it available to the driver14:14
*** Sukhdev_ has joined #openstack-meeting14:14
mesteryinstance name on the port would be interesting, can we make that happen?14:14
rkukuraI was thinking the device_id might be sufficient, since a driver can use it to find the nova instance and get its name14:14
apechwould this just be using the nova api calls?14:15
rkukuraI'm not sure there are any other cases where ml2 code would be making nova API calls14:15
*** timello_ has quit IRC14:15
apechThis is what I wasn't sure about - is this ok, or should we be passing that information in as part of the call nova makes to quantum14:15
*** timello_ has joined #openstack-meeting14:15
*** tkammer has quit IRC14:15
rkukuraSeems there are two ways to get the nova info - for nova to set it on port (like host_id), or neutron to use the nova API14:15
mesteryrkukura: If multiple MechanismDrivers would find this useful, it makes sense to do this in a generic spot in the code rather then per-driver.14:15
apechif making nova api calls is okay, that's an easier thing to add for now14:15
rkukuranot sure about nova api calls being ok14:16
*** fnaval has joined #openstack-meeting14:16
*** tkammer has joined #openstack-meeting14:16
rkukurado we do that anywhere else in neutron?14:16
mesteryrkukura: Having nova set it on the port seems to be the cleanest way for this to happen.14:16
rkukuraif we decide it is OK, then the context object could do it the first time a driver asks, and cache the result14:16
rkukuraits taking forever just to get nova to set the host_id14:17
apechthat was exactly my thinking - this seems like a very similar patch to getting the host_id14:17
rkukuracertainly having nova also set the instance_name on port would be trivial14:17
Sukhdev_Sorry - I joined late -14:17
mesteryrkukura: That seems like a process problem, not a technical one from what I can tell.14:18
rkukuraso what is the use case for a mech driver needing the instance name?14:18
apechvisibility - we'd like to be able to map how VMs map to physical ports14:18
mesteryapech: +114:18
doude_the instance name can be updated so we must be careful14:18
mesteryAnd it's nice to have that VM name for display purposes.14:18
apechyeah, device_id is a bit unruly :)14:19
mesterydoude_: Yes, any caching on the Neutron side would need to take that into account.14:19
rkukuraso wouldn't a display tool be able to use the device_id with the nova API to get the instance name, and any other info it also needed?14:19
Sukhdev_rkukura: if you display 100's ov VMs it is pain to see them by long IDs :-)14:19
*** tzn has quit IRC14:20
mesteryrkukura: That's possible, but that means the display tool needs to talk Nova API. Sometimes that's not desirable.14:20
apechmestery: +114:20
mesterySo, how do we proceed here?14:20
*** pschaef has joined #openstack-meeting14:20
rkukuraMy suggestion is to let the current host_id patch get merged, then add instance_name as a followup nova patch.14:21
apechrkukura: that sounds like a good plan14:21
mesteryrkukura: OK, I can file a bug for the instance_name as well.14:21
mesteryrkukura: I can work on that patch as well.14:21
rkukuraI guess that would also mean extending the portbinding extension, but that should be OK14:21
apechmestery: thanks!14:21
mestery#action mestery to file bug to get instance_name passed in from nova following the host_id patch14:21
rkukuraas a fallback plan, we could have the ml2 context object use the nova API if needed14:22
mesteryrkukura: Sounds like a plan.14:22
rkukuraok14:22
rkukurathat it for portbinding for now then14:22
mestery#action If nova patch to add instance_name is rejected, have ml2 context object use the nova API instead.14:22
mesteryrkukura: thanks!14:22
mestery#topic ml2-gre14:22
*** openstack changes topic to "ml2-gre (Meeting topic: networking_ml2)"14:22
mestery#link https://review.openstack.org/33297 ml2-gre review14:22
matrohonhi14:23
mesterymatrohon: hi!14:23
mesterymatrohon: Updates on ML2 GRE?14:23
matrohonI just proposed two new patch today14:23
mesteryI saw that, I will review that tomorrow.14:23
matrohonthe first one add unit test14:23
matrohonthe second one remove the endpoint ID usag14:23
matrohonas propose by garyk in a review14:24
mesterygreat progress!14:24
HenryGIs it a separate review?14:24
rkukuraI'll review them both this week14:24
matrohonno it's the same14:24
mesterymatrohon: I've started the vxlan type driver based on your patch since you implemented the RPC callbacks I'll need for that one as well.14:24
mesterythanks for that matrohon. :)14:25
matrohonbut we definitly think that endpoint id doesn't make sense14:25
rkukuracorrection, I'll review it this week;-)14:25
mesteryAny questions on ML2 GRE?14:25
mestery#topic ml2-vxlan14:26
*** openstack changes topic to "ml2-vxlan (Meeting topic: networking_ml2)"14:26
mestery#link https://blueprints.launchpad.net/quantum/+spec/ml2-vxlan ml2-vxlan blueprint14:26
mesterySo I've started on this now, utilizing matrohon's ml2-gre patch as a base.14:27
mesteryShooting for Friday for an initial review.14:27
matrohonmestery : great!14:27
mesterymatrohon: Thanks for all the RPC work in your patch, this made mine smaller than yours. :)14:27
*** dolphm has quit IRC14:28
matrohonyou will manage multicast14:28
matrohon?14:28
mesterymatrohon: That's the plan, I'm going to add in the option of configuring multicast as well.14:28
*** egallen has joined #openstack-meeting14:28
matrohonmestery : ok, great!14:28
*** adalbas has joined #openstack-meeting14:29
mesterymatrohon: Will appreciate your review once I push the review. :)14:29
matrohonmestery : np14:29
mesteryAny more queries on ML2 VXLAN?14:29
feleouetquestion regarding multicast:14:29
feleouetshouldn't the option be set in agents14:30
feleouetand plugin support implemented as provider extension14:30
*** lastidiot has quit IRC14:31
mesteryfeleouet: That may be the case, but if you're using multicast, you will end up mapping VNIs to multicast groups, so the type driver DB needs to store that info.14:31
mesteryThe agents will determine if multicast VXLAN is supported or not I guess.14:31
mesteryE.g. the current OVS VXLAN code doesn't support it, but likely will soon, while the LinuxBridge agent (with Tomas's patch) would support it.14:31
*** dolphm has joined #openstack-meeting14:32
feleouetok, makes sense14:32
mesteryfeleouet: Cool!14:32
mestery#topic Bugs and other blueprints14:33
*** openstack changes topic to "Bugs and other blueprints (Meeting topic: networking_ml2)"14:33
mesteryWanted to call attention to the "tunnel_types" OVS agent bug14:33
mestery#link https://review.openstack.org/#/c/33107/ tunnel_types review14:33
mesterymatrohon: I got your latest feedback, will see if I can implement that tonight/tomorrow.14:33
rkukuralooks about ready to merge to me, but wanted to test in devstack before giving my +214:33
mesteryrkukura: Thanks!14:33
matrohonmestery : ok it's quite tricky14:34
mesterymatrohon: One question I had was, we could file a separate bug to address your comment and fix that separately.14:34
mesterymatrohon: Exactly, which is why maybe a different bug makes sense since this one is ready to merge.14:34
matrohonmestery : it makes senses for me14:34
mesterymatrohon: Would you be ok with that?14:34
mesteryOK, great!14:34
mestery#action mestery to file new bug to address matrohon's concerns on the tunnel_type fix14:34
matrohonI can manage that bug if you want14:34
mesterymatrohon: Cool!14:35
rkukurahadn't seen matrohon's comment though14:35
mesteryI'll assign it to you.14:35
mesteryrkukura: Can you review what's there now, we'll do a different bug to address matrohon's comment.14:35
mesterymatrohon: Once I file the bug, can you remove your -1? :)14:35
rkukuramestery: I had one code nit if you plan to update, but not critical14:35
matrohonmestery : ok14:35
mesteryrkukura: File your nit, and I can update the patch late tonight or tomorrow morning, up to you.14:36
rkukuraok14:36
*** IlyaE has joined #openstack-meeting14:36
mesteryOK, wanted to bring everyone's attention to matrohon's L2 population blueprint as well.14:36
mestery#link https://blueprints.launchpad.net/quantum/+spec/l2-population L2 population blueprint14:36
mesterymatrohon: Is this something we should get in under the context of ML2?14:37
matrohonmestery : we target it for havana314:37
*** woodspa has joined #openstack-meeting14:37
mesterySorry, this is under feleouet's name, not matrohon's. :)14:37
rkukurais the idea to add the support to the agent, but only when used with ml2?14:38
mesterymatrohon: OK, fair enough.14:38
matrohonrkukura : exactly14:38
rkukuraand keep backward compatibility with openvswitch plugin?14:39
matrohonrkukura : this will be based on new RPC callbacks14:39
rkukuramakes sense to me14:39
mesteryYes, this looks great matrohon.14:39
mesteryOK, did I miss any other Ml2 related bugs or blueprints?14:40
mesteryBTW: If any new bugs or blueprints come up that you don't see on the agenda, please unicast me and I will add them. I'll do my best to keep on top of it so we can discuss urgent ones in the weekly meeting though.14:40
*** topol has joined #openstack-meeting14:41
mestery#topic Ported Mechanism Drivers14:41
*** openstack changes topic to "Ported Mechanism Drivers (Meeting topic: networking_ml2)"14:41
*** psedlak__ has quit IRC14:41
rkukurathere may be some recent reviews and/or merges to openvswitch that need to be duplicated in ml214:41
feleouetOne last bug concerning OVS agent14:41
feleouetsorry, may I continue?14:41
mesteryrkukura: OK, good point, lets track those and file ML2 bugs to ensure we get the work in as well.14:42
mesteryfeleouet: yes14:42
*** jtomasek has quit IRC14:42
mesteryplease14:42
feleouet#link https://bugs.launchpad.net/quantum/+bug/117797314:42
feleouetI'll try to propose a first WIP for this one today14:42
*** jtomasek has joined #openstack-meeting14:42
*** michchap has joined #openstack-meeting14:42
feleouetUsing event-based detection rather than pooling14:42
mesteryfeleouet: Great! I'll add this to track for Ml2 as well, thanks!14:42
rkukurapolling?14:43
feleouetReplacing the agent loop that pools for new devices14:43
rkukuraexcellent!14:43
feleouet(And is very ressource consuming)14:43
mesteryfeleouet: +114:43
*** beagles is now known as beagles_brb14:44
feleouetI'd be great if you could give me an inital feedback, then I'll work on UT14:44
feleouet(depending on feedback, of course)14:44
rkukuraOne other review we should look at14:44
mesteryfeleouet: Will keep an eye out for the patch.14:45
*** IlyaE has quit IRC14:45
feleouetmestery: thanks14:45
*** sc68cal has joined #openstack-meeting14:45
rkukurahttps://review.openstack.org/#/c/33736/ seems to be related to our eventual multi-segment network API14:45
*** spzala has joined #openstack-meeting14:46
mesteryrkukura: I agree, this seems relevant to the multi-segment network API.14:46
rkukurabut does not seem as usable as what I was envisioning14:46
*** _TheDodd_ has joined #openstack-meeting14:46
mesteryrkukura: I agree.14:46
rkukuraalso seems to expose nicira's transport zones, which wouldn't apply14:46
mesteryrkukura: Can you provide feedback of this nature on the review itself to alert them to our ML2 overlapping work and your concerns?14:47
*** vkmc has quit IRC14:47
rkukuraDoes it make sense to clarify that their extension is nicira-specific?14:48
mestery#action rkukura to provide ML2 related feedback on review https://review.openstack.org/#/c/33736/14:48
rkukuraok14:48
mesteryrkukura: Yes, it does, I think pointing that out is the way to go.14:48
*** euanh has joined #openstack-meeting14:48
mesteryI don't think we shoudl be exposing vendor specific extensions into the core extension APIs, they can implement it as a plugin specific extension API I think.14:48
*** hanrahat has joined #openstack-meeting14:50
mesteryOK, we have about 10 minutes left, how about if we quickly get an update for each of the 4 known MechanismDriver implementations out there?14:50
mestery#link https://blueprints.launchpad.net/quantum/+spec/sukhdev-8 Arista Mechanism Driver Blueprint14:50
mesterySukhdev_: Hi!14:50
Sukhdev_Hi14:50
Sukhdev_sorry was distracted14:50
mesterySukhdev_: No worries, any updates on Arista MD?14:51
Sukhdev_I am stuck on testing because of port binding issue - other than that I am good14:51
*** dkehn has quit IRC14:51
mesterySukhdev_: Thanks!14:51
mestery#link https://blueprints.launchpad.net/quantum/+spec/ml2-md-cisco-nexus Cisco Nexus Mechanism Driver14:52
mesteryrcurran: Cisco Nexus MD updates?14:52
rcurranworking on it. Have ported over most of the code. (Except common code already mentioned in this meeting)14:52
*** michchap has quit IRC14:52
mesteryrcurran: Cool, no road blocks so far?14:53
rcurranno, i have plenty to work on ... coding to andre's bp that should go in soon14:53
mesteryrcurran: Thanks!14:53
mestery#link https://blueprints.launchpad.net/quantum/+spec/ml2-opendaylight-mechanism-driver OpenDaylight Mechanism Driver14:53
Sukhdev_mestery: are you still planning on putting out the wiki for ML2?14:53
mesterySukhdev_: I had thought I did that, let me check for that after the meeting and send a note.14:54
mesteryIf I didn't, I'll make the wiki page and send out a note to openstack-dev14:54
*** mrodden has quit IRC14:54
*** lukego has quit IRC14:54
apechmestery: thanks14:54
mesterySo, the ODL MD update is that it's complicated. :)14:54
Sukhdev_mestery: thanks14:54
mesteryWe'll begin porting the code we had into a MD this coming week, but the broader question of how ODL integrates with Neutron is being worked on over in the ODL project.14:55
mesterySo the final result may look slightly different than what we have so far.14:55
*** sneezezhang has joined #openstack-meeting14:56
rkukuramestery: Is the plan from ODL to have both a monolithic plugin and ml2 MD support?14:56
mesteryrkukura: That's part of the complication. I would prefer only an ML2 MD one.14:56
mesteryI think after the ODL HackFest in July a more concrete plan will be know, though this will affect Havana integration for ODL I realize.14:57
rkukuramestery: Running into anything difficult to do with ml2 as currently defined?14:57
mesteryrkukura: No, the ML2 side looks fine, it's more ODL issues and deficiencies we're hitting.14:57
*** leizhang has quit IRC14:58
mesteryThe final MD for ML2 is the Tail-f NCS one14:58
mestery#link https://blueprints.launchpad.net/quantum/+spec/tailf-ncs Tail-f NCS Mechanism Driver14:58
*** dhellmann-away is now known as dhellmann14:58
mesteryI don't know Luke Gorrie's IRC nick though.14:58
mesteryrkukura; Do you?14:58
rkukuramestery: no14:58
mesteryOK, I don't see an update, just calling it out for consistency here then.14:59
mestery#topic Questions?14:59
*** openstack changes topic to "Questions? (Meeting topic: networking_ml2)"14:59
mesteryOK, that's all for the agenda.14:59
mesteryLets keep up on reviews for the next week as much as possible!14:59
apechsounds great, thank sall14:59
*** haomaiwang has quit IRC14:59
rcurranthanks14:59
mestery#endmeeting14:59
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"14:59
openstackMeeting ended Wed Jun 26 14:59:55 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-06-26-14.00.html14:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-06-26-14.00.txt14:59
openstackLog:            http://eavesdrop.openstack.org/meetings/networking_ml2/2013/networking_ml2.2013-06-26-14.00.log.html15:00
rkukurathanks mestery and all!15:00
mesteryThanks everyone!15:00
mesteryThanks to you too rkukura!15:00
johnthetubaguy#startmeeting XenAPI15:00
openstackMeeting started Wed Jun 26 15:00:23 2013 UTC.  The chair is johnthetubaguy. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: XenAPI)"15:00
openstackThe meeting name has been set to 'xenapi'15:00
Sukhdev_Thanks15:00
johnthetubaguyhello xenapi folks15:00
johnthetubaguyshow of hands for who is around for this one?15:00
*** apech has quit IRC15:01
johnthetubaguylooking a bit thin on the ground for the regulars I think15:01
*** haomaiwang has joined #openstack-meeting15:01
*** tanisdl has joined #openstack-meeting15:02
*** sleepsonthefloor has quit IRC15:03
*** tanisdl has quit IRC15:03
johnthetubaguy#help https://review.openstack.org/#/c/32760/ more reviews15:03
*** rcurran has quit IRC15:04
johnthetubaguyI guess the Citrix folks are busy today15:05
johnthetubaguy#endmeeting15:05
*** psedlak has joined #openstack-meeting15:05
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"15:05
openstackMeeting ended Wed Jun 26 15:05:24 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:05
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-06-26-15.00.html15:05
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-06-26-15.00.txt15:05
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-06-26-15.00.log.html15:05
*** lastidiot has joined #openstack-meeting15:05
*** haomaiwang has quit IRC15:08
*** mrodden has joined #openstack-meeting15:08
*** lloydde has joined #openstack-meeting15:10
*** tayyab_ has quit IRC15:11
*** jcoufal has quit IRC15:12
*** sc68cal has left #openstack-meeting15:12
*** nati_ueno has joined #openstack-meeting15:13
*** armax has joined #openstack-meeting15:13
*** rcrit has quit IRC15:13
*** zehicle_at_dell has quit IRC15:14
*** jtomasek has quit IRC15:14
*** fmanco has quit IRC15:15
*** otherwiseguy has joined #openstack-meeting15:16
*** tanisdl has joined #openstack-meeting15:17
*** tkammer has quit IRC15:18
*** tkammer has joined #openstack-meeting15:18
*** cliu has joined #openstack-meeting15:19
*** michchap has joined #openstack-meeting15:20
*** danwent has joined #openstack-meeting15:20
*** Sukhdev_ has quit IRC15:22
*** kmartin has joined #openstack-meeting15:25
*** hartsocks has joined #openstack-meeting15:25
*** rcrit has joined #openstack-meeting15:26
*** _TheDodd_ has quit IRC15:28
*** kebray has joined #openstack-meeting15:28
*** joel-coffman has joined #openstack-meeting15:29
*** Ritz-Laptop has quit IRC15:29
*** _TheDodd_ has joined #openstack-meeting15:30
*** rkukura has left #openstack-meeting15:30
*** michchap has quit IRC15:31
*** Ritz-Laptop has joined #openstack-meeting15:37
*** bgorski has joined #openstack-meeting15:39
*** otherwiseguy has quit IRC15:40
*** mirrorbox has joined #openstack-meeting15:43
*** beagles_brb is now known as beagles15:43
*** matiu has joined #openstack-meeting15:46
*** cliu has quit IRC15:48
*** thingee has joined #openstack-meeting15:48
*** michchap has joined #openstack-meeting15:50
*** michchap_ has joined #openstack-meeting15:51
*** Ritz-Laptop has quit IRC15:51
*** tanisdl has quit IRC15:51
*** dprince has quit IRC15:52
*** tanisdl has joined #openstack-meeting15:52
*** michcha__ has joined #openstack-meeting15:52
*** enikanorov has quit IRC15:52
*** tanisdl has quit IRC15:53
*** michch___ has joined #openstack-meeting15:53
*** tanisdl has joined #openstack-meeting15:54
*** michchap has quit IRC15:54
*** michchap has joined #openstack-meeting15:55
*** sleepsonthefloor has joined #openstack-meeting15:55
*** MarkAtwood has joined #openstack-meeting15:55
*** michchap_ has quit IRC15:55
*** michchap_ has joined #openstack-meeting15:55
*** lloydde has quit IRC15:55
*** jbrogan has joined #openstack-meeting15:56
*** joel-coffman has quit IRC15:56
*** michcha__ has quit IRC15:56
*** michcha__ has joined #openstack-meeting15:57
*** jgallard has joined #openstack-meeting15:58
*** michch___ has quit IRC15:58
*** joel-coffman has joined #openstack-meeting15:58
*** michchap has quit IRC15:59
seiflotfy_yo new meeting guys?15:59
seiflotfy_mkoderer: ping15:59
*** avishay has joined #openstack-meeting15:59
*** armax has left #openstack-meeting15:59
seiflotfy_i put some stuff on the agenda15:59
jgriffith#startmeeting cinder15:59
openstackMeeting started Wed Jun 26 15:59:48 2013 UTC.  The chair is jgriffith. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
*** openstack changes topic to " (Meeting topic: cinder)"15:59
openstackThe meeting name has been set to 'cinder'15:59
jgriffithheelllllllooooooooo16:00
mkodererHi!16:00
agordeevhello16:00
seiflotfy_hi guys16:00
*** zhiyan has joined #openstack-meeting16:00
DuncanThey16:00
*** michchap_ has quit IRC16:00
zhiyanhi16:00
*** jdurgin1 has joined #openstack-meeting16:00
avishayhi all16:00
thingeeo/16:00
seiflotfy_so lets start16:01
jgriffithseiflotfy_: oh16:01
*** michcha__ has quit IRC16:01
jgriffithok16:01
jgriffith:)16:01
* jgriffith was getting a cup o'joe16:01
seiflotfy_who put in the first item o nthe agenda16:01
thingeeme16:01
seiflotfy_jgriffith: oh go no hurry16:01
jgriffith#topic pecan16:01
*** openstack changes topic to "pecan (Meeting topic: cinder)"16:01
thingeewas waiting for topic switch16:01
*** michchap has joined #openstack-meeting16:01
thingeethere we go16:01
seiflotfy_thingee: any blue print for it?16:02
thingeeseiflotfy_: it's on the agenda16:02
thingeehttps://wiki.openstack.org/wiki/CinderMeetings16:02
seiflotfy_firefox nightly is broken16:02
seiflotfy_i cant see any links16:02
seiflotfy_brb16:02
jgriffiththingee: go for it16:02
thingeefolks it's a scary change. if you've read john and I's points on the ML it's going to be one big commit which would scary for reviewing16:03
avishaythingee: why the switch?  is it mainly for python 3?16:03
thingeeavishay: it works towards that goal sure16:03
thingeegets rid of paste16:03
*** michchap_ has joined #openstack-meeting16:03
seiflotfy_back16:03
thingeeso I propose instead of fixing v1 and v2 to use pecan, we wait for a v3 bump and have pecan and paste run with each other16:03
thingeethis is similar to what ceilometer did16:04
jgriffith+116:04
seiflotfy_thingie cant it be done in subtasks ?16:04
thingeethat way we have small commits for each v3 controller with test16:04
seiflotfy_thingee: sorry16:04
thingeeone at a time16:04
seiflotfy_ah ok16:04
*** ajforrest has joined #openstack-meeting16:04
seiflotfy_cool16:04
*** jasondotstar has joined #openstack-meeting16:04
*** pcm__ has quit IRC16:04
thingeeI also encourage people to not work on the patch. I don't really care if I'm the person that does, but just the sake of review resources16:05
*** mkerrin has joined #openstack-meeting16:05
thingeeI've had several people ping about wanting to collaborate and I don't think it's worth resources right now16:05
*** skolathu has joined #openstack-meeting16:05
thingeethe blueprint has a link to my github branch which moved v1 over. I can easily change that to be v3 so this should go smooth in I16:05
thingeeany questions?16:05
jgriffithso my 2 cents; changing out the entire web framework out from under the existing API needs some more justification than what we have so far16:05
boris-42hi all=)16:06
jgriffithDoing in in a V3 isolated seems more pragmatic16:06
jgriffiththingee: sorry... thought you were done :)16:06
thingeeno that's fine16:06
thingeehere's the thread that lists the points http://lists.openstack.org/pipermail/openstack-dev/2013-June/010857.html16:06
seiflotfy_thingee: which release are you targeting with this?16:06
*** michchap has quit IRC16:06
thingeeseiflotfy_: I mentioned about I16:07
*** lastidiot has quit IRC16:07
thingeeabout=above16:07
thingeeif we have a reason for a version bump, which I think we might16:07
*** tanisdl has quit IRC16:07
thingeeI don't want a version bump just for a framework switch16:07
jgriffith+116:07
thingeeand as john mentioned a version bump each release is kinda a bummer.16:07
*** michchap_ has quit IRC16:07
thingeewould rather make things sane for ops16:07
*** lastidiot has joined #openstack-meeting16:07
jgriffithIf there were more compelling gains or bug fixes to going to pecan that'd be one thing16:08
jgriffithbut as it stands I say cache it until we need a bump for other things16:08
hemnagot my coffee..phew16:08
thingeebut Icehouse we'll probably have a reason for a bump...and I already have most of the work done there for pecan. just gotta make the old framework run along side with pecan which is pretty easy imo16:08
DuncanTThere are a few bit of crazy in our API (inc V2), but as people start to write things that talk to cinder we need to think about long term support16:08
*** garyk has joined #openstack-meeting16:09
thingeeDuncanT: why do I not hear about these?16:09
thingee:)16:09
thingeehere I am going to meetups and bragging about how awesome cinder is :P16:09
thingeepresentations and all :D16:09
jgriffithDuncanT: you wanna share your insights?16:09
DuncanTjgriffith: Little things... resize during snapshot, no need to force for an attach clone16:10
*** BrianB has quit IRC16:10
jgriffithDuncanT: those aren't API issues16:10
DuncanTCouple of other bits I need to flick through my notebook for16:10
jgriffithDuncanT: Those are things that *you* don't like in the Cinder behaviors16:10
jgriffiththat's different16:10
thingeeDuncanT: make me bugs and have john target them...I now have a lot of bandwidth16:10
jgriffithand others.. not just you16:10
DuncanTThey're issues with the definition of the API, not the implementation, sure, but they're things that we might want to make sane in V316:11
*** SumitNaiksatam has quit IRC16:11
DuncanTThe behaviour /is/ the API...16:11
jgriffithI'm not prepared for the snapshot/volume argument yet again16:11
thingeehaha16:11
DuncanTI've given up on that one for now16:11
thingeeOk so any questions regarding the pecan switch?16:12
jgriffithOk... anyway, DuncanT makes a good point16:12
jgriffithDuncanT: Log some bugs if you would16:12
DuncanTSure16:12
DuncanTWill do16:12
thingeeDuncanT: thanks16:12
thingeeI think I'm done...anyone have any questions later, feel free to ping me16:12
jgriffithThat'll fit nicely in with thingee 's plan regarding pecan V3 in I (hopefully)16:12
thingeejgriffith: hopefully? :(16:12
jgriffiththingee: ok... s/hopefully/''16:13
jgriffith:)16:13
jgriffithV3 will be slated for I, I just hope there's other really cool things to go in it16:13
thingeelosing faith in me, sheesh16:13
jgriffithno no no.... not at all16:13
*** tzn has joined #openstack-meeting16:13
jgriffithsmart ass!16:13
thingeeit's a sane approach. it just took me 5k lines of code writing to realize it16:13
thingee:P16:13
hemnathat's better than 10k lines of code16:14
jgriffithSo I'm hoping that DuncanT will come up with all kinds of new things we need in V316:14
thingeehemna: I only did v1 at that point and some tests16:14
jgriffithSo we'll have a brand new shiny toy for I all the way around16:14
hemnaooh...shiny!16:14
jgriffithThe "season of the API"16:14
thingeehemna: imagine thd diff stat once I finished ;)16:14
thingeecould be 10k16:14
hemnalol16:14
seiflotfy_o_O16:15
jgriffithalright... everyboy cool with the Pecan decision?16:15
jgriffithavishay: ?16:15
seiflotfy_that would require another release to review it :P16:15
avishayjgriffith: sounds good to me16:15
jgriffithavishay: you're unusually quiet this evening16:15
avishayjgriffith: just no objections :)16:15
jgriffith;)16:15
jgriffithalright...16:15
jgriffith#topic ceph support in Cinder16:15
*** openstack changes topic to "ceph support in Cinder (Meeting topic: cinder)"16:15
jgriffithseiflotfy_: you're up16:15
seiflotfy_well i wanted to know if everybody is ok with the current map and if it will make it in "I"16:16
jgriffithI... you mean H?16:16
seiflotfy_i dont think it will make it in H16:16
seiflotfy_if it can that would be amazing16:16
dosaboycinder-backup-to-ceph is *hopefully* ready now ;)16:16
DuncanTErm, should make it in H... looks to be making good progress...16:16
jgriffithSorry... dont' know what you're talking about then16:16
seiflotfy_NICE16:16
jgriffithYou have 3 patches listed, 3 patches under review16:17
jgriffithYou have some other plan that we don't know about :)16:17
seiflotfy_jgriffith: just references to say that this is what is still to be done16:17
DuncanTI can't see any real benefit to the interface class, other than making java coders slightly more at home, but it is harmless enough16:17
seiflotfy_and they look good16:17
mkodererDuncanT: ;)16:17
dosaboyonly two patchsets here (if you meant me)16:18
dosaboyone was abandoned16:18
jgriffithalright... let's back up16:18
*** psedlak has quit IRC16:18
seiflotfy_DuncanT: good point, but I also see a benefit for other "new" backend services16:18
jgriffithOn the agenda:16:18
jgriffithItem #216:18
seiflotfy_yep back to number 216:18
jgriffithseiflotfy_: has "Discuss status of Ceph support in Cinder"16:18
jgriffithand there are 3 reviews listed16:18
seiflotfy_yeah, so is it possible for us to have it for havana?16:19
seiflotfy_also what tests do we have for it16:19
jgriffithseiflotfy_: so Havana is the current release we're working on16:19
seiflotfy_how do we intend to test this properly16:19
jgriffithseiflotfy_: Havan will be cut from master in the fall16:19
jgriffithseiflotfy_: that's your job :)16:19
DuncanTseiflotfy_: It is undergoing a perfectly normally trajectory to land on trunk in the next week or two...16:19
jgriffithseiflotfy_: submitting that patch means I've assumed you test it :)16:19
mkodererI think we need to spend time for performence testing16:20
*** rostam has quit IRC16:20
seiflotfy_jgriffith: i tested it with my old shitty patches16:20
seiflotfy_and it worked16:20
seiflotfy_but it was really slow16:20
thingeejdurgin1: can you test it? :)16:20
seiflotfy_managed to backup 1 gig16:20
seiflotfy_:P16:20
thingeelike actually whitebox testing16:20
dosaboycome someone clarify what patches we are discussing here16:21
dosaboyif it is item 216:21
seiflotfy_a question would be how can we make use of ceph 2 ceph backup without going through the generic route16:21
hemnamkoderer, we (my group at HP) just got legal approval to release the performance script I wrote a while back to test cinder16:21
seiflotfy_is that up for question16:21
dosaboytwo of those are duplicate16:21
jgriffithdosaboy: :)16:21
mkodererhemna: sounds great16:21
thingeehttps://review.openstack.org/#/q/status:open+project:openstack/cinder+branch:master+topic:bp/cinder-backup-to-ceph,n,z16:21
jgriffithdosaboy: indeed16:21
dosaboyand I have tested them quite extensively16:21
hemnamkoderer, https://github.com/terry7/openstack-stress16:21
dosaboybu more testing is never a bad thing16:21
*** markwash has joined #openstack-meeting16:21
seiflotfy_dosaboy: do you intend to allow use of rbd tools for ceph2ceph backups16:22
seiflotfy_?16:22
*** lloydde has joined #openstack-meeting16:22
thingeejgriffith, seiflotfy_: I'll see if jdurgin1 wants to test things out16:22
*** _TheDodd_ has quit IRC16:23
dosaboynot sure what you mean, but look at bp for what remains to be implemented16:23
*** nati_ueno has quit IRC16:23
jgriffithOk, so I'm not sure how well organized this topic is... shall we move on?16:23
thingeeis there anything else relevant to discuss in terms with this in cinder?16:23
seiflotfy_ok cool, so to sum it up "cinder ceph backup" ===> might make it in havana, neds more testing16:24
jgriffithItem #3 ?16:24
*** rostam has joined #openstack-meeting16:24
seiflotfy_jgriffith: yes16:24
mkodereryes pls16:24
jgriffith#topic parent calss for backup service?16:24
*** openstack changes topic to "parent calss for backup service? (Meeting topic: cinder)"16:24
jgriffithclass16:24
seiflotfy_mkoderer: go ahead16:24
mkodererok I just introduced this interface class16:25
*** otherwiseguy has joined #openstack-meeting16:25
mkodererI know DuncanT hate me for it ;)16:25
mkodererbut I think we could put some overall functionallity in it16:25
jgriffithmkoderer: I think there's just a question of "what's the plan"16:25
seiflotfy_the idea is we have now 2 backends swift and ceph and more will be coming i guess16:25
seiflotfy_just to have a standard class that one can orient ones self on16:26
thingeeseiflotfy_: so i think this is fine...it sets a guideline to devs adding additional services. However, I would like to see documentation that explains this a bit more for newcomers wanting to add their object store16:26
thingeeI don't really care who does that...but it'll be, well, great :)16:27
mkodererthingee: good point16:27
*** markwash_ has joined #openstack-meeting16:27
seiflotfy_thingee: i think mkoderer will take the lead on this16:27
seiflotfy_:d16:27
mkoderersure np16:27
*** garyk has quit IRC16:27
thingeeseiflotfy_, mkoderer: wonderful thanks guys!16:27
seiflotfy_so i assume you want us to plan it out more and introduce it again in a better blueprint?16:27
*** sabari_ has joined #openstack-meeting16:28
seiflotfy_ok cool16:28
dosaboythat would be a good idea16:28
jgriffithcool by me, follows our patterns we use everywhere else16:28
*** mkollaro has quit IRC16:28
seiflotfy_item 4?16:28
mkodererjepp16:28
*** boris-42 has quit IRC16:28
jgriffith#topic community recognition16:28
*** openstack changes topic to "community recognition (Meeting topic: cinder)"16:28
seiflotfy_so in my free time i do work for GNOME and Mozilla16:29
thingeeseiflotfy_: I don't think it needs to be planned more...the interface is already defined. I think  the documentation will speak for it :)16:29
*** sabarim has joined #openstack-meeting16:29
*** markwash has quit IRC16:29
*** markwash_ is now known as markwash16:29
seiflotfy_thingee: ok16:29
seiflotfy_so back to 416:29
*** sabari_ has quit IRC16:29
seiflotfy_the idea is i have a small script i can adapt that goes through git and bugzilla (will change it to launchpad)16:29
seiflotfy_we use it at mozilla with every release to detect new code contributors16:30
seiflotfy_and publish it via a link in the release notes16:30
guitarzandoesn't openstack already do this?16:30
jgriffithseiflotfy_: FYI we have one of those :)16:30
thingeeguitarzan: yup16:30
seiflotfy_they do?16:30
jgriffithseiflotfy_: https://github.com/j-griffith/openstack-stats16:30
seiflotfy_ok16:30
jgriffithguitarzan: yes16:30
seiflotfy_then no need for me to do it then16:30
thingeeit's in community newsletter thing16:30
seiflotfy_just wanted to help16:30
thingeeseiflotfy_:  :)16:30
seiflotfy_ok less work for me then :D16:31
*** kumar_ has joined #openstack-meeting16:31
thingeewow look at that, 9:3016:31
*** tkammer has quit IRC16:31
thingeepdt16:31
thingee16:30 whatever16:31
*** kumar_ has quit IRC16:31
eharneyis it currently done for things like: new reviewers, new people active on launchpad (but haven't committed code)?16:31
*** Guest32596 is now known as med_16:32
avishaythingee: no banking time for next meetings!16:32
*** med_ has quit IRC16:32
*** med_ has joined #openstack-meeting16:32
*** neouser has joined #openstack-meeting16:32
*** gyee has joined #openstack-meeting16:32
seiflotfy_eharney: we can look into this and try to work it out during the week16:32
jgriffith#topic H216:32
*** openstack changes topic to "H2 (Meeting topic: cinder)"16:32
eharneyi don't know of any real needs there, just thinking16:32
jgriffithreal quick16:32
*** shang_ has joined #openstack-meeting16:32
jgriffithhttps://launchpad.net/cinder/+milestone/havana-216:32
jgriffithwe're a bit stalled on BP's here16:33
jgriffithanyone from mirantis around this morning?16:33
*** neouser has quit IRC16:33
jgriffitheharney: also looking for an update from you on the ILO BP16:33
*** epim has joined #openstack-meeting16:33
*** doude_ has left #openstack-meeting16:33
*** jgallard has quit IRC16:34
jgriffithbueller... bueller16:34
eharneyyes, i need to update there16:34
* jgriffith is talking to his dog this morning16:34
jgriffith:)16:34
avishayhaha16:34
eharneyat the moment gluster snaps work has been higher priority for me16:34
jgriffitheharney: You still planning on H2, or you want it deferred?16:34
jgriffitheharney: I can defer it and if you get to it bring it back in16:34
eharneyrealistically it should probably be at H3 at this point16:35
jgriffitheharney: sounds good16:35
eharneyi did have a question there though16:35
*** Shengjie has joined #openstack-meeting16:35
jgriffitheharney: have at it16:35
*** Shengjie has quit IRC16:35
eharneywe have this idea of minimum driver requirements, right16:35
jgriffitheharney: indeed, we do16:35
eharneyi'm trying to understand how that works for a driver like this that supports multiple different backends16:36
*** shang has quit IRC16:36
*** jcoufal has joined #openstack-meeting16:36
*** michchap has joined #openstack-meeting16:36
jgriffitheharney: not sure I follow?16:36
jgriffitheharney: this is what I consider more a base layer than a driver per-say16:36
jgriffithwell... it's an iscsi driver16:36
*** SergeyLukjanov has quit IRC16:36
jgriffitheharney: or are youtalking your gluster work?16:37
eharneyhere, the driver supports libstoragemgmt, which enables support for targetd, and a couple of other storage platforms16:37
*** derekh has quit IRC16:37
*** leizhang has joined #openstack-meeting16:37
eharneyso, meeting minimum requirements for the driver may depend on what backend you configure it to use16:37
jgriffitheharney: well, I think it's a different category16:37
eharneyok, makes sense16:38
jgriffitheharney: min requirements for LIO would be >= tgtd16:38
jgriffithNo?16:38
eharneyright16:38
*** Mandell has joined #openstack-meeting16:38
*** dprince has joined #openstack-meeting16:38
jgriffitheharney: and if we're not switching the default (which it looks like we won't due to time) it's an option/beta so to speak anyway16:38
jgriffithwas that what you were wondering?16:39
eharneyi think that covers what i was wondering16:39
jgriffitheharney: k... ping me if there's more questions16:39
*** gongysh has quit IRC16:39
*** sneezezhang has quit IRC16:39
jgriffithor if I'm missing a point here16:39
*** SumitNaiksatam has joined #openstack-meeting16:39
eharneyok16:39
zhiyanfolks, for volume-host-attach, when you have time pls take a look on https://review.openstack.org/#/c/34125/ , i think it's closely ready to merge.16:40
jgriffithOk.. we have no winston, so we can't get into the QoS rate-limiting debate16:40
jgriffithphewww16:40
jgriffithI would like it if folks could help out with guitarzan 's type-quota patch16:40
guitarzanI would like that as well :)16:40
jgriffithwe need some input on how this should be presented16:41
jgriffithguitarzan: and I have talked a bit but I think I'm stuck... need some brain-storming16:41
jgriffithand need to make sure nobody pukes on it when they notice it later16:41
jgriffith:)16:41
jgriffithguitarzan: has a number of possibilities worked up he can share16:41
thingeejgriffith, guitarzan: can help after morning meeting...around 17:20 utc16:41
DuncanTI was starting to read through your discussions on channel, damn you two go on....16:42
DuncanT;-)16:42
guitarzanhaha16:42
* guitarzan hides in shame16:42
jgriffithDuncanT: we'll need your input as well as you've objected to the approach before16:42
jgriffith:)16:42
jgriffithalmost as bad as you and I16:42
jgriffithor me and thingee16:42
*** egallen has quit IRC16:42
DuncanTIndeed and indeed16:42
jgriffithor whoever is foolish enough to start a conversation with me :)16:43
*** colinmcnamara has joined #openstack-meeting16:43
jgriffithOk, I had more... but quite frankly it'd be nice to wrap a meeting early for a change :)16:43
DuncanTAt least it is harder for me to turn into a shouting match on IRC... apparently that can make bystanders nervious16:43
jgriffith#topic open discussion16:43
*** openstack changes topic to "open discussion (Meeting topic: cinder)"16:43
jgriffithDuncanT: whimps!16:43
jgriffithanybody have anything?16:44
eharneyone more point re: min driver requirements16:44
jgriffitheharney: yes?16:44
eharneythere are a couple of new driver reviews outstanding that probably aren't meeting those... we need to tell them something?16:44
thingeeI verified gpfs16:44
*** colinmcnamara has quit IRC16:45
*** garyk has joined #openstack-meeting16:45
jgriffitheharney: zvm and gpfs are the only two that come to mind16:45
thingeejgriffith, DuncanT: if you guys don't mind, I'm going to take my "that guy" role and start sending emails to driver owners?16:45
jgriffithOhh... xtreemfs as well16:45
jgriffiththingee: :)16:45
eharneyjgriffith: xtreemfs, "generic block" thing16:45
DuncanTthingee: Go for it16:46
hemnathat's been stale for a while16:46
avishayspeaking of GPFS, any idea why its blueprint isn't showing up in search (and therefore in the link in the commit message)?16:46
avishayhttps://blueprints.launchpad.net/cinder/+spec/gpfs-volume-driver16:46
jgriffithbecause he's got a bogus link16:46
thingeeavishay: I believe jgriffith gave 'em a -2 about it16:46
DuncanTMy plan is to put patches in to remove them the day after H3 closes, but it is probably far nicer to give people warning16:46
eharneyavishay: does it not show ones "Pending approval"?  dunno16:47
jgriffithI did, and even told him how to fix it16:47
thingeeDuncanT: we're splitting, remember?16:47
thingee:)16:47
DuncanTthingee: :-)16:47
avishayjgriffith: how can he fix?16:48
jgriffithavishay: FYI https://blueprints.launchpad.net/cinder?searchtext=gpfs16:48
avishayjgriffith: yes, his BP isn't there16:48
*** lpabon has joined #openstack-meeting16:48
*** michchap has quit IRC16:48
jgriffithavishay: yeah it is16:48
jgriffithhttps://blueprints.launchpad.net/cinder/+spec/ibm-gpfs-driver16:48
avishayjgriffith: no it's not...that one was made by someone else and is not relevant16:48
avishayjgriffith: this is his - https://blueprints.launchpad.net/cinder/+spec/gpfs-volume-driver16:48
*** cbananth has joined #openstack-meeting16:49
dosaboyjgriffith: I've updated the bp for ceph backup to aim for h2 since that is hopefully realistic now16:49
zhiyani created ibm-gpfs-driver16:49
*** scott_ has joined #openstack-meeting16:50
*** vijendar has quit IRC16:51
*** kirankv has joined #openstack-meeting16:51
jgriffithavishay: I'll look into it16:51
*** vijendar has joined #openstack-meeting16:51
avishayjgriffith: thanks!16:51
jgriffithavishay: the fact that he marked it complete may be an issue16:51
thingeezhiyan: hi, can you provide the blueprint in your next patch commit message?16:51
avishayjgriffith: aahhhh...16:51
thingee8 minute warning16:52
jgriffithzhiyan: can you kill the one you started, or mark it superseded or something16:52
zhiyanjgriffith: ok16:52
zhiyanthingee: which one?16:53
thingeezhiyan: the patch that's introducing the gpfs driver should have a blueprint about adding the gpfs driver16:53
jgriffiththingee: haha... see, you just fell into the same trap that I did :)16:53
avishaythingee: it does, but the link is broken16:53
jgriffiththingee: zhiyan isn't doing that work... dinesh is16:54
jgriffithzhiyan: had a bp16:54
jgriffithdinesh started a new one16:54
avishayzhiyan: please kill https://blueprints.launchpad.net/cinder/+spec/ibm-gpfs-driver16:54
jgriffithavishay: haha :)16:54
jgriffithalright folks16:54
jgriffithwe blew our early quit time16:54
*** Eustace has joined #openstack-meeting16:54
thingeeavishay: oh yeah that's what I meant :)16:54
avishaythingee: :)16:54
jgriffithI'm in #openstack-cinder as always16:54
*** joel-coffman has quit IRC16:55
avishaywe can still be 5 minutes early16:55
jgriffithThanks!!16:55
*** nati_ueno has joined #openstack-meeting16:55
avishayBye all!16:55
thingeeguitarzan, DuncanT, jgriffith: can we talk about quotas in 20 mins?16:55
guitarzansure16:55
zhiyandone16:55
thingeezhiyan: thanks16:55
thingeethanks everyone16:55
jgriffith#endmeeting cinder16:55
jgriffith#end meeting16:55
jgriffith#endmeeting16:55
jgriffithbooo..16:55
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"16:55
openstackMeeting ended Wed Jun 26 16:55:38 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-06-26-15.59.html16:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-06-26-15.59.txt16:55
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-06-26-15.59.log.html16:55
*** vijendar1 has joined #openstack-meeting16:55
*** avishay has left #openstack-meeting16:55
jgriffithfinally!16:55
*** vijendar has quit IRC16:56
*** ajforrest has quit IRC16:56
*** mkerrin has left #openstack-meeting16:57
hartsocksGreetings stackers! I'll be with you in a moment.16:59
sabarimHey Shawn!16:59
*** sabarim is now known as Sabari16:59
hartsocks#startmeeting VMwareAPI17:00
openstackMeeting started Wed Jun 26 17:00:15 2013 UTC.  The chair is hartsocks. Information about MeetBot at http://wiki.debian.org/MeetBot.17:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:00
*** openstack changes topic to " (Meeting topic: VMwareAPI)"17:00
openstackThe meeting name has been set to 'vmwareapi'17:00
hartsocks#topic greetings17:00
*** openstack changes topic to "greetings (Meeting topic: VMwareAPI)"17:00
hartsocksWho's here?17:00
kirankvhi!17:00
*** neouse has joined #openstack-meeting17:00
hartsocks@kirankv hey!17:01
SabariHi, this is sabari here17:01
cbananthhi17:01
danwenthello17:01
hartsocksanyone else?17:02
hartsocksLet's get rolling then.17:04
hartsocks#topic agenda17:04
*** openstack changes topic to "agenda (Meeting topic: VMwareAPI)"17:04
hartsocks#link https://wiki.openstack.org/wiki/Meetings/VMwareAPI#Agenda17:04
hartsocksWe kicked off with bugs last time so this time let's start with blueprints.17:04
hartsocksIs anyone around to discuss Fiber Chanel and iSCSI support for the VCDriver?17:05
kirankvyes17:05
kirankvthe bp is specifically for the fibre channel support17:05
hartsocksokay, let's move into that topic then...17:06
hartsocks#topic blueprints17:06
*** openstack changes topic to "blueprints (Meeting topic: VMwareAPI)"17:06
hartsocks@kirankv do you have a link to the BluePrint?17:06
kirankvhttps://blueprints.launchpad.net/nova/+spec/fc-support-for-vcenter-driver17:07
kirankv#link https://blueprints.launchpad.net/nova/+spec/fc-support-for-vcenter-driver17:07
kirankvthe implementation would be similar to iSCSI17:07
hartsocksHow is this coming?17:08
kirankvthe only challenge is that should the LUN be presented to all the hosts in the cluster or only the host on which the instance is hosted upon17:08
kirankvwe are modifying the iSCSI code to enable FC attach as well, otherwise ther will be lot of code repitition17:09
*** mikal has quit IRC17:09
kirankvam working on this right now17:09
kirankvwork in progree patch should be available by Monday17:09
kirankvprogress*17:10
*** mikal has joined #openstack-meeting17:11
kirankvdoes anyone object/like the idea of "LUN be presented to all the hosts in the cluster or only the host on which the instance is hosted upon"17:11
*** tzn has quit IRC17:11
hartsocksDo we have to decide?17:11
hartsocksCan it be a configuration?17:12
kirankvwell im going with the presentation to all hosts since cinder is working on facilitating multi attach of volumes17:12
kirankvit can be a config, by not presenting it would mean live move of the VM will not be possible17:13
hartsocksThat would seem to allow for the LUN as shared storage between the hosts.17:13
*** terriyu has joined #openstack-meeting17:13
*** thingee has left #openstack-meeting17:13
hartsocksThat second line… would be useful for a LUN being used by a single VM.17:14
hartsocksI'm not certain that this is an important use case… but this is all so young I don't want to exclude it.17:14
hartsocksIf we can only have one...17:15
*** michchap has joined #openstack-meeting17:15
hartsocksI would prefer the LUN be available to all hosts… but...17:15
hartsocksI like to keep options open for later.17:15
hartsocksDoes anyone else have an opinion?17:15
hartsocksI'll take that as a resounding *shrug*17:16
hartsocks@kirankv any other points on this blueprint?17:17
kirankvwe will be testing this using 3par driver, but should work for others as well17:18
kirankvno other points to add for this bp17:18
hartsocksOkay.17:19
hartsocksMoving on...17:19
hartsocks#link https://blueprints.launchpad.net/glance/+spec/hypervisor-templates-as-glance-images17:19
hartsocksIs anyone working on this?17:19
hartsocksI think this is you again @kirankv17:20
kirankvi was working but now moved to the FC driver17:20
hartsocksYou have H-2 listed as your target.17:20
*** pschaef has quit IRC17:20
hartsocksIf you get FC driver through … you won't hit H-2 on that blueprint.17:21
hartsocksCan you move the Milestone target to H-3? Do you think you could hit that?17:21
kirankvit might be difficult, i will change the target date by Monday17:21
*** sandywalsh has quit IRC17:21
hartsocksOn the plus side...17:22
*** sarob has joined #openstack-meeting17:22
hartsocks#link https://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-by-one-service17:22
hartsocksFeels like it is almost there.17:22
hartsocks… or at least moving… I see a new patch up here...17:22
hartsocks#link https://review.openstack.org/#/c/30282/17:23
kirankvhopefully should make it17:23
*** luis_fdez has joined #openstack-meeting17:23
*** sarob has quit IRC17:23
hartsocksI'll solicit folks who are in this IRC meeting to take a look at the latest patch.17:23
*** sarob has joined #openstack-meeting17:23
hartsocks… so … folks … (you know who you are)17:23
hartsocksOkay...17:24
hartsocksAny canonical folks in the meeting?17:24
*** sarob has quit IRC17:24
hartsocksWe have two related BP I'll just touch on...17:24
hartsocks#link https://blueprints.launchpad.net/nova/+spec/vmware-image-clone-strategy17:24
*** sarob has joined #openstack-meeting17:25
hartsocks#link https://blueprints.launchpad.net/nova/+spec/improve-vmware-disk-usage17:25
hartsocksI'll talk to Yaguang Tang off IRC and see if he can move his BP out to H-3 or if we can hand off work for the blocking BP.17:25
hartsocks#action followup with Yaguang Tang on BPs17:26
hartsocksAre there other BP that people need to discuss?17:26
*** ladquin has quit IRC17:26
*** michchap has quit IRC17:27
*** sarob_ has joined #openstack-meeting17:27
* hartsocks whistles a merry tune for a moment in case someone is typing17:28
hartsocksokay17:28
*** tzn has joined #openstack-meeting17:28
hartsocks#topic bugs17:28
*** openstack changes topic to "bugs (Meeting topic: VMwareAPI)"17:28
Sabari:)17:28
hartsocksHeh17:28
hartsocks@Sabari you have a pet bug you want to parade out?17:29
SabariI wanted to talk about the live migration bug17:29
Sabarihttps://bugs.launchpad.net/nova/+bug/119219217:29
*** luis_fdez has quit IRC17:29
hartsocksoh dear. I almost forgot about this one.17:30
*** sarob__ has joined #openstack-meeting17:30
*** ssurana has joined #openstack-meeting17:31
SabariWe can do vMotion between clusters (without shared storage) in VC > 5.117:31
*** sarob has quit IRC17:31
Sabariand with shared storage in VC  5.117:31
*** sarob_ has quit IRC17:31
Sabaridoes this mean we should support this feature ?17:31
hartsocksI think this interacts with that BP...17:31
*** skolathu has quit IRC17:32
* hartsocks looking up BP17:32
Sabaribut the clusters have to be within the same VC and a bunch of other prerequisites17:32
hartsockshttps://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-by-one-service17:32
hartsocks@kirankv does this bug affect your work?17:32
SabariBut that just makes all the clusters in VC visible under the same hypervisor17:33
hartsocks@Sabari my preference is when we see things like that we should have "sanity check" code that tells an operator why things will fail.17:33
kirankvim not sure where the changes are, but should not affect, if it does will rebase :)17:33
SabariI don't think it ll have any effect on this bug17:33
hartsocksOkay… so...17:33
hartsocksTo get vMotion to make sense when using clusters...17:34
SabariApart from the fact, it cannot pariticipate in live-migration (correct me, if am wrong ?17:34
hartsocksyou have to have...17:34
hartsocksmore than one cluster.17:34
hartsocksshared datastores between all these clusters...17:34
hartsocksand you have to have one vCenter controlling all the shots...17:35
SabariThis feature can only work in the following scenario, you have multiple nova service configured with different clusters in the same VC. Then we can support live migration between them17:35
hartsocks*and* OpenStack *must* talk to the one vCenter for both clusters?17:35
hartsocksOkay.17:35
hartsocksSo you can have multiple nova-compute nodes.17:35
SabariShared datastore is a reqiurement only prior to 5.117:35
Sabariyes, you can have multiple nova-compute nodes per cluster in same VC17:36
hartsocksI think we have to be prepared for people using this on 5.1 < … for the next few years.17:36
SabariPost 5.1 you need to have a vMotion Network that is stretched between the clusters.17:36
Sabarito support non-shared scenario17:37
hartsocksAt minimum we need to give a warning as to why things won't work when they don't.17:37
hartsocksThis seems like a big job.17:37
hartsocksIs this really a bug?17:37
*** GheRiver1 is now known as GheRivero17:38
SabariYes. A bunch of hardware related compatiibility is run by VC and we can re throw the results of the checks back to the user.17:38
*** sandywalsh has joined #openstack-meeting17:38
*** johnthetubaguy has quit IRC17:38
SabariNo not a bug - but more like a feature17:38
hartsocksBut… it was *supposed* to be there in Grizzly…17:38
*** jhenner has joined #openstack-meeting17:39
hartsocks(I wrote this bug based on a conversation I read on the mailing list)17:39
hartsocksWe then spotted that the live migrate code was orphaned.17:39
SabariHmm, if we see this from ESXDriver perspective, may be something might be working today17:40
Sabari*need to check17:40
hartsocksOkay. Let's follow up on this later.17:40
hartsocksI'm glad this won't hurt @kirankv's work.17:40
kirankv:)17:40
Sabariyes17:40
hartsocks#action Sabari will investigate bug 1192192 from ESXDriver side and report back17:41
Sabarisure17:42
hartsocksThis could be a feature for VC or a bug under ESX.17:42
hartsocksnext up ...17:42
hartsocks#link https://bugs.launchpad.net/nova/+bug/118480717:42
*** ladquin has joined #openstack-meeting17:43
*** ladquin has joined #openstack-meeting17:43
*** tzn has quit IRC17:43
hartsocksThis is the "snapshot bug"17:43
hartsocksanyone around to talk about this?17:43
hartsocks@danwent any comment here?17:44
*** rnirmal has quit IRC17:44
*** sandywalsh has quit IRC17:44
hartsocksI'll go follow up on this off line.17:45
danwentI just tested it and saw that it didn't work and filed a bug.  I haven't done any investigation around this.  i think tracy was looking at it.17:45
*** ndipanov is now known as ndipanov_gone17:45
hartsocks@danwent okay.17:45
hartsocks@danwent she seems to have asked you to clarify something in the bug. Could you look at that when you get a chance?17:46
danwentk17:46
*** otherwiseguy has quit IRC17:46
hartsocksI'm working 2 bugs at the same time...17:46
hartsocks#link https://bugs.launchpad.net/nova/+bug/117836917:46
kirankvlooks like the last comment in the bug is how the snapshot feature works as per the documentations17:46
hartsocks#undo17:46
openstackRemoving item from minutes: <ircmeeting.items.Link object at 0x3198ed0>17:46
hartsocks… the code base shifted under the bug ...17:47
kirankvim not sure of the history, but teh doc says17:47
kirankvSnapshots of running instances may be taken which create a new image based on the current disk state of a particular instance.17:47
kirankv#link http://docs.openstack.org/trunk/openstack-compute/admin/content/images-and-instances.html17:48
hartsocksthanks for posting the link.17:48
*** lukego has joined #openstack-meeting17:49
*** jlucci has joined #openstack-meeting17:49
kirankvim not sure if openstack snapshot feature is same as vCenter snapshot, needs further reading for me17:49
*** Tross has quit IRC17:50
hartsocksLet's follow up on that one outside IRC then.17:50
kirankvok17:50
hartsocksSo I'm tracking 4 total bugs that are open + high/critical … the last two are on my plate.17:50
*** jcoufal has quit IRC17:50
hartsocks#link https://bugs.launchpad.net/nova/+bug/118004417:51
hartsocks… the patch for this I personally would reject if someone else were presenting it to me… but it *kinda* works.17:51
hartsocks#link https://review.openstack.org/#/c/33576/17:52
hartsocksI'm putting it up for review here to solicit comments from other VMwareAPI people.17:52
hartsocksThe change involves using a traversal spec to sort out inventory details. I will cycle back to writing tests for this shortly.17:52
hartsocksIt does rely on this patch...17:53
hartsocks#link https://bugs.launchpad.net/nova/+bug/117836917:53
*** gholt has joined #openstack-meeting17:53
hartsocks#link https://review.openstack.org/#/c/30036/17:53
*** michchap has joined #openstack-meeting17:53
hartsocksWhich you will note has a *regal* history… approaching that of nobility...17:53
hartsocksI have been working on this patch since May 21st.17:54
hartsocksIt is now on revision 17.17:54
* hartsocks bows17:54
hartsocks(so if you think you have problems… )17:54
hartsocks:-)17:54
hartsocksOkay...17:55
hartsocksAre there any other bugs I should be actively tracking?17:55
*** mikal has quit IRC17:55
*** mrodden has quit IRC17:56
Sabarihttps://review.openstack.org/#/c/30822/ needs +1's it received earlier. I had to rebase as the code base shifted17:56
SabariI have resolved the merge conflicts and uploaded a new patch17:57
*** mikal has joined #openstack-meeting17:57
*** pcm___ has joined #openstack-meeting17:58
hartsocksI called out the try-catch block in your patch because it looks like the test might be non-deterministic17:58
*** sandywalsh has joined #openstack-meeting17:58
kirankv@Sabari, will check the patch17:58
*** pcm___ has quit IRC17:58
hartsocksI see you left comments on why this is okay.17:58
Sabari@hartsocks, I replied to it in-line. Please take a look17:58
Sabariyes17:58
*** timello_ has quit IRC17:58
*** pcm__ has joined #openstack-meeting17:58
hartsocksIf I tripped on this, other people might too. Please put some of that in a "#" comment near the try-catch block...17:59
*** timello_ has joined #openstack-meeting17:59
Sabariokay17:59
*** lbragstad has quit IRC17:59
*** mrodden has joined #openstack-meeting17:59
*** sdake has quit IRC17:59
hartsocksI will use that comment to raise an issue about the language support issues.17:59
hartsocksOkay.17:59
hartsocksWe're out of time.17:59
hartsocksSee the #openstack-vmware channel if folks want to have impromptu meetings!18:00
hartsocksOtherwise, see you next week.18:00
hartsocks#endmeeting18:00
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"18:00
openstackMeeting ended Wed Jun 26 18:00:32 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-06-26-17.00.html18:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-06-26-17.00.txt18:00
*** lbragstad has joined #openstack-meeting18:00
openstackLog:            http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-06-26-17.00.log.html18:00
kirankvthanks18:01
Sabarithanks!18:01
*** cbananth has quit IRC18:01
*** vijendar has joined #openstack-meeting18:02
*** Sabari has quit IRC18:02
*** vijendar1 has quit IRC18:03
*** clayg has joined #openstack-meeting18:04
*** vijendar has quit IRC18:04
*** IlyaE has joined #openstack-meeting18:05
*** michchap has quit IRC18:06
*** vijendar has joined #openstack-meeting18:06
*** Mandell has quit IRC18:07
*** _TheDodd_ has joined #openstack-meeting18:09
*** otherwiseguy has joined #openstack-meeting18:11
*** Eustace has quit IRC18:13
*** clayg has left #openstack-meeting18:13
*** anniec has joined #openstack-meeting18:14
*** ivasev has joined #openstack-meeting18:15
*** kirankv has left #openstack-meeting18:17
*** zaitcev has joined #openstack-meeting18:17
*** cp16net|away is now known as cp16net18:19
*** sarob has joined #openstack-meeting18:19
*** Mandell has joined #openstack-meeting18:20
*** cliu has joined #openstack-meeting18:22
*** otherwiseguy has quit IRC18:22
*** sarob__ has quit IRC18:22
*** hartsocks has left #openstack-meeting18:23
*** sushils has quit IRC18:23
*** dhellmann has quit IRC18:23
*** epim has quit IRC18:25
*** SumitNaiksatam has quit IRC18:29
*** IlyaE has quit IRC18:29
*** michchap has joined #openstack-meeting18:32
*** jculp_ has joined #openstack-meeting18:33
*** jculp_ has quit IRC18:33
*** jsloyer has joined #openstack-meeting18:33
*** novas0x2a|laptop has joined #openstack-meeting18:37
*** diogogmt has joined #openstack-meeting18:37
*** ayurchen has quit IRC18:39
*** epim has joined #openstack-meeting18:39
*** otherwiseguy has joined #openstack-meeting18:39
*** neouse has quit IRC18:41
*** lloydde has quit IRC18:42
*** Vernier has joined #openstack-meeting18:43
*** michchap has quit IRC18:44
*** hanrahat has quit IRC18:45
*** tanisdl has joined #openstack-meeting18:45
*** mrodden has quit IRC18:48
*** lloydde has joined #openstack-meeting18:49
*** portante has joined #openstack-meeting18:53
*** Tross has joined #openstack-meeting18:57
*** vvechkanov|2 has joined #openstack-meeting18:58
*** rnirmal has joined #openstack-meeting18:59
notmynameswift meeting time. anyone here?19:00
swifterdarrello/19:00
*** jking_swift has joined #openstack-meeting19:00
zaitcevo/19:00
portanteo/19:00
davidhadashi19:01
notmynameok, let's get started :-)19:01
litongo/19:01
notmyname#startmeeting swift19:01
openstackMeeting started Wed Jun 26 19:01:39 2013 UTC.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
vvechkanov|2o/19:01
*** openstack changes topic to " (Meeting topic: swift)"19:01
openstackThe meeting name has been set to 'swift'19:01
*** cp16net is now known as cp16net|away19:01
*** IlyaE has joined #openstack-meeting19:01
*** cp16net|away is now known as cp16net19:01
torgomatico/19:01
notmynameGood morning or afternoon to everyone!19:02
notmynamewe've got several things to discuss today19:02
notmynamehttps://wiki.openstack.org/wiki/Meetings/Swift19:02
notmynamefirst, general stuff19:02
notmyname#topic general stuff19:02
*** openstack changes topic to "general stuff (Meeting topic: swift)"19:02
notmyname1.9.0 RC has been cut and is on the milestone-proposed branch19:03
notmynametons of great stuff in it19:03
notmynameplease take time to review it and do any tests19:03
notmynameunless something comes up before next tuesday, this is what we'll release as 1.9.0 (final)19:03
davidhadaswhen was the cut time?19:03
*** dfg has joined #openstack-meeting19:03
notmynamedavidhadas: sometime between midnight-ish pacific last night and whenever ttx got my email in france :-)19:04
notmynameany questions about 1.9.0?19:04
davidhadas:) do we want to add account-acl to 1.9? I think its is mmmmmmerging19:04
notmynameno19:05
davidhadasinteresting :)19:05
creihtawww19:05
dfgis nested slo's and the bulk name change thing in 1.9?19:06
*** listening has joined #openstack-meeting19:06
notmynamedfg: https://review.openstack.org/#/c/30956/ is not19:06
notmynamedfg: I think the "name change thing" is19:06
dfgthis one: https://review.openstack.org/#/c/34107/19:06
notmynamedfg: yes, but checking19:07
davidhadasnotmyname: any reason after we did refactor swift with two patchs and got the work done to use it with accoung acls we are not adding it in?19:07
davidhadasThis was something we said we will do in Portland19:08
*** bgorski has quit IRC19:08
*** n0ano has quit IRC19:08
notmynamedfg: yes, that's included19:08
notmynamedavidhadas: there will still be at least one more release before the openstack havana cycle is done19:09
portantedo you mean one more release and then the final release of havana?19:09
davidhadasI am sure - but this is no reason not to include it :)19:09
portanteor one more release that constitutes havana?19:09
*** Tross has quit IRC19:09
notmynameportante: not sure yet19:10
portantek19:10
*** clayg has joined #openstack-meeting19:10
zaitcevmeans we need to act on https://blueprints.launchpad.net/swift/+spec/diskfile-databasebroker-as-apis Right Now in order to see it in Havana19:10
notmynamequick poll: who is going to be going to Hong Kong for the next summit?19:11
*** michchap has joined #openstack-meeting19:11
creihtwe don't know for sure yet on our side19:11
* torgomatic isn't sure yet19:11
portantenotmyname: I am not19:11
portantezaitcev: yes we are working on that19:11
creihtlikely just 1 of us though19:11
davidhadasNo decision yet19:11
* swifterdarrell isn't sure yt19:11
swifterdarrell*yet19:11
torgomaticcreiht: just one from the Cloud Files team?19:12
*** garyk has quit IRC19:12
creihttorgomatic: yes19:12
litongneed approval from management.19:12
*** IlyaE has quit IRC19:12
litongthat normally won't come until close to the summit date.19:12
notmynamegood to know. as the summit approaches, the topics discussed will be influenced by who can be there19:12
notmynameok, next up19:13
notmyname#topic PBR19:13
*** openstack changes topic to "PBR (Meeting topic: swift)"19:13
notmynamethere's a proposal to use it for swift. it's already used for python-swiftclient19:13
notmynamethere have been some complaints about it19:13
creihtPabst Blue Ribbon?19:14
zaitcevSuch as what?19:14
notmynameand I believe mordred is lurking to hear any concerns19:14
notmynametorgomatic: swifterdarrell: ?19:14
mordredheyhey19:14
swifterdarrellI like pbr okay, especially since I've already gone through the work to package it for python-swiftclient.19:14
notmynamemordred: could you give a 1 line summary of what PBD does?19:14
creihtI think mordred just likes tweaking that stuff once a round so that he gets to be an ATC for every project :)19:14
notmyname*PBR19:15
mordredcreiht: that's DEFINITELY my goal :)19:15
* mordred proposes a new super-atc label for people with commits in all projects...19:15
mordrednotmyname: so - the basic thing is19:15
creihtnotmyname: I just heard word that there is a good chance none of us may be there19:16
notmynamecreiht: hmmm (but what's new? *zing*!19:16
mordrednotmyname: pbr is a library that enapsulates all of the various build operations and standards that we were copying around all of the projects19:16
claygI think there used to be this idea that swift wanted to not include depends that weren't available on old distros because we want to be easy to package... but I'm not sure that's still true (e.g. xattr>=newest-version-evar)19:16
*** boris-42 has joined #openstack-meeting19:16
portantemy vote would be to try to use pbr for Havana19:16
mordredmost notable features relevant for swift are: declarative config, tag-based-versioning19:16
* portante not that I really understand what I am saying but hey19:17
notmynamemordred: what is "declarative config"?19:17
mordredit also does some other things - like authors and changelog generation, but the intent is to disable those for swift19:17
torgomaticone thing I find weird about pbr is that it's a run-time dependency; it seems like it only provides any utility at build-time19:17
mordrednotmyname: instead of putting code in setup.py, you put build info in setup.cfg19:17
notmynamemordred: I think a question is what benefit it brings beyond "well everyone else is using it"19:17
mordredtorgomatic: it doesn't have to be a run-time dep19:17
torgomaticmordred: oh? do tell...19:17
claygmordred: I thought the __version__ stuff imported from pbr?19:18
mordredtorgomatic: and there is a bug that's got a patch up to be fixed that will make that even more the case19:18
* clayg goes to get his head back on stright19:18
notmynamemordred: if it is a run-time dep, that needs to change19:18
mordredclayg: the version stuff does import from pbr - but the version stuff just draws from pkg_resources19:18
mordredso if you don't want it runtime- you can totally just make the pkg-resources call yourself19:18
*** vijendar has quit IRC19:18
claygnotmyname: rly?  dnspython is a "runtime dependency" because of setuptools and requires.txt - why should pbr be different?19:18
*** vijendar has joined #openstack-meeting19:19
notmynameclayg: now we get back to those fun dependency requirements questions :-)19:19
mordrednotmyname: the main benefit you'll get other than just doing what other people do is the tag-based-versions and releasing things by pushing tags19:19
notmynameclayg: I'm not sure it is19:19
torgomaticif I can build packages for swift[client] that need pbr at build-time only, that'd be nice19:19
*** otherwiseguy has quit IRC19:20
notmynamemordred: I like that feature, but not at the expense of making every packagers life harder because I didn't want to update a string in a file19:20
*** IlyaE has joined #openstack-meeting19:20
mordredtorgomatic: you can totally do that19:20
swifterdarrellDoes it even matter if pbr is a run-time dep?  Every distro for which a pbr-using package is built, will need to have pbr packaged...  not that I don't think it'd be better if it weren't, but as far as a reason to not use it...19:20
* notmyname withdraws previous "if ... then that needs to change" statement ;-)19:21
mordrednotmyname: and I don't think it should make packagers life harder - at least I certianly hope it wouldn't19:21
*** IlyaE has quit IRC19:21
*** woodspa has quit IRC19:21
torgomaticmordred: got any pointers on how?19:21
mordredtorgomatic: we just need to modify the swift pbr patch to use pkg_resources call for the version call19:22
notmynamecreiht: any RAX perspective? is it a pain point or an improvement that you can take advantage of?19:22
mordredtorgomatic: I can make that patch and show it to you19:22
torgomaticmordred: that would be very nice19:22
zaitcevI'm trying to see if get_manpath() in pbr is the right one. I remember I had to fix it somewhere, but I forgot what package19:22
notmyname#action mordred modify the swift pbr patch to use pkg_resources call for the version call19:22
*** atiwari has joined #openstack-meeting19:22
claygyeah I mean idk... if I "import swiftclient.version" it says I need pbr19:22
mordredyeah. we'll fix that19:22
claygi see pbr imported in swift/__init__ so I ...19:23
claygoh :D19:23
*** michchap has quit IRC19:23
*** vijendar has quit IRC19:23
notmynameso the patch as proposed to swift now still needs work? and pbr's use in python-swiftclient should be update to remove swift's transitive runtime dependency?19:23
*** vipul is now known as vipul|away19:24
notmynamemordred: ^ or is pbr itself going to change?19:24
notmyname...19:25
notmynamemaybe we should come back to that? :-)19:26
claygbut... i mean pkg_resources returns a string for version... not a VersionInfo instance19:26
claygwhy can't we just depend on and package pbr?19:27
clayglike... who cares?19:27
zaitcevokay, I verified pbr has okay get_manpath(). What the heck, let's do that Declarative Mumbo-Jumbo, it promises to save code a bit.19:27
torgomaticclayg: it just seems weird to me that there's a runtime dependency on a thing that looks at git metadata to make a version tag, because at runtime there isn't any git metadata floating around19:28
*** sdake has joined #openstack-meeting19:28
*** sdake has quit IRC19:28
*** sdake has joined #openstack-meeting19:28
torgomaticI mean, it's not the end of the world, but it does seem weird19:28
mordredsorry - got pulled away for a sec19:29
mordrednotmyname: I will change the swift patch19:29
notmynamebut since the runtime dependency is going to be resolved by mordred's new patch, that concern should go away19:29
mordrednotmyname: and Ill put in a patch to swiftclient19:29
notmynameok, sounds good :-)19:29
torgomaticnotmyname: works for me19:29
notmynamethanks19:29
creihtTo me, it still really to give us very little, for the cost of depending on another package19:29
notmynamenext topic then19:29
notmynameor not19:29
creihtlol19:29
creihtmove on19:29
notmynameheh19:30
claygwell i guess if there's a new patch coming we'll wait19:30
notmyname#topic openstack-hacking19:30
*** openstack changes topic to "openstack-hacking (Meeting topic: swift)"19:30
notmynamehttps://review.openstack.org/#/c/33861/ has been proposed19:30
notmynameI'm not a fan of starting to use yet another external test dependency, but I want to get other thoughts19:30
creihtyay more of "not adding much value" :)19:31
portantehow do other openstack projects use it?19:31
notmynameI was thinking about -2'ing that patch until I saw it on the agenda for today's meeting19:31
portantein addition to other tools?19:31
notmynamemordred: if you're still here, you may have some good info for us about openstack-hacking19:31
*** cliu has quit IRC19:31
portanteOr as the only way of enforcing coding standards19:31
mordredI know many things :)19:32
notmynameportante: I think it's the nova code standards19:32
portantedoes the nova coding standards apply to all the other groups?19:32
portanteor projects?19:32
notmynameportante: I'll let you guess ;-)19:32
portante:)19:32
mordredpretty much everyone else has decided to adopt some or all of them now19:32
claygI think it *started* as a nova standard19:32
mordredthey are done as a flake8 plugin, so it's possible to choose to only enforce some of them19:33
claygeither way it all seems fine to me19:33
portantethen it might be worth for us to do the same19:33
*** kiall has left #openstack-meeting19:33
mordredit did - and most of them (it turns out) actually derive from google's python style guidelines19:33
claygredbo whined when the new pep8 started enforcing indent rules but he survived19:33
notmynamemordred: so if that patch get's merged what's added for us to get code merged?19:33
clayg+1 dont' care19:33
davidhadaschmouel: suggested as a topic but could not attend today - maybe we should postpone to next meeting before deciding19:33
torgomaticI'll give the hacking patch a resounding "meh"19:34
mordrednotmyname: it the same process as before19:34
portantenot that we have to immediately change all our code, but let's start using it for what we do at first19:34
notmynamedavidhadas: I had the same concerns as him, I think19:34
torgomaticif others want it, that's fine; I'll neither help nor hinder19:34
notmynameportante: how so?19:34
davidhadasok19:34
notmynametorgomatic: well, we've said that before (eg pbr)19:34
swifterdarrellThe patch to add hacking stuff didn't seem to have to change much of the existing source-base, right?  Mostly stuff related to doc-string formatting?  That's what I remember, anyway19:35
creihtportante: I'm not looking forward to the, oh you are using hacking.txt now, why aren't you following x,y, and z?19:35
swifterdarrellIt seems fine to me19:35
notmynameswifterdarrell: yes, but it added something to tox.ini that changes what is run19:35
*** tealtealteal has joined #openstack-meeting19:35
claygcreiht: not everything is as slippery a slope as you make it out to be19:35
creihtlol19:35
zaitcevsometimes it's an abyss19:35
creihtI just said I'm not looking forward to it19:35
clayglol19:35
creihtnot that it is the end of the world19:35
zaitcevWarning: No matches found for: python-hacking19:35
zaitcevoh great, another thing to package19:36
swifterdarrellcreiht: well, at least there's still Christmas...19:36
notmynamehow do new contributors find the guidelines and test before they submit? does it add any packaging requirements?19:36
portantecreiht: yes, that is always possible19:36
creihtI just think we spend way too much time on this minutiae rather than real problems19:36
swifterdarrellzaitcev: mordred: wait, seriously?  It's another package to get the hacking plugin?19:36
swifterdarrellI *do* think that depending on something not in PyPi is bullshit19:37
torgomaticcreiht: +119:37
* clayg doesn't say anything about creiht's and clayg "fixing" the saio doc lately19:37
mordredit's in pypi19:37
torgomaticswifterdarrell: it's in pypi as "hacking"19:37
zaitcevNo, maybe it's in flake8, I'm looking right now19:37
swifterdarrelloh, okay...19:37
torgomaticnot "python-hacking"19:37
* swifterdarrell settles down and takes a deep breath ;)19:37
portante;)19:37
* portante always with them negatives waves, moriarty19:37
*** jhenner has quit IRC19:37
* portante its a mother beautiful bridge and its gonna be there19:37
notmynameok, so then the patch should be reviewed as normal and not blocked for any meta-reason19:38
notmynamelet's move on to all that important stuff then ( creiht, torgomatic ) ;-)19:38
*** IlyaE has joined #openstack-meeting19:38
notmyname#topic smallest swift config19:38
*** openstack changes topic to "smallest swift config (Meeting topic: swift)"19:38
davidhadasWe would like to start up with a swift/doc/… describing a current 3 replica small configuration (2 nodes) and describing how it can be extended to a full size swift cluster – any thoughts/suggestions?19:39
notmynamedavidhadas: not sure what's the issue here19:39
notmynamedavidhadas: ok, do it :-)19:39
creihthaha19:39
davidhadasNext topic than :)19:39
notmynameheh :-)19:39
creihtsee the important stuff is so easy19:39
notmyname#topic placement control middleware19:39
*** openstack changes topic to "placement control middleware (Meeting topic: swift)"19:39
portantewhat is this exactly?19:39
davidhadasSO here there is a new blueprint19:39
*** IlyaE has quit IRC19:39
davidhadashttps://blueprints.launchpad.net/swift/+spec/cluster-sync-policy19:40
notmyname#link https://blueprints.launchpad.net/swift/+spec/cluster-sync-policy19:40
davidhadasBasically it is a step in the direction of enabling an assembly of N clusters19:40
notmynamedavidhadas: seems that the tl;dr is hooks for some sort of placement policy, and these can be managed in middleware19:40
davidhadastl;dr?19:41
portantedoes the middleware need something from the core?19:41
notmyname"too long; didn't read" ie summary19:41
notmynamedavidhadas: and IMO if it can be handled in middleware, then it's perhaps something that can be deferred19:41
davidhadasTHe idea is to add to container sync a level of automation in teh way containers which have container sync are created19:41
*** koolhead17 has joined #openstack-meeting19:42
notmynamedavidhadas: is there a question you'd specifically like answered about the blueprint?19:43
notmynamedavidhadas: or about the topic in general?19:43
portantedavidhadas: so what does that mean for the core code?19:43
davidhadasI would like to hear first reaction and fiurst objctions to understand if we should ivest in making this part of swift19:43
*** hanrahat has joined #openstack-meeting19:44
davidhadasi.e. if others would be interested in such an approach19:44
portanteas middleware, it should be first developed and put in place and demonstrated before considered part of swift19:44
notmynamedavidhadas: do you anticipate any changes required in swift that would need to be done not in middleware?19:44
davidhadasso we can develop it with time to allow a multi-caluter env with placement control19:44
portanteunless it has some core component that needs to change to enable efficient operation19:44
davidhadasThis is too early to say19:45
torgomaticI think Swift is getting better at having geographically-distributed clusters, and IMHO that's way nicer than container-sync19:45
torgomaticbut that's just me19:45
claygtorgomatic: +1 not just you19:45
*** barefoot has joined #openstack-meeting19:45
*** tealtealteal has quit IRC19:45
davidhadasI would like as a first stagte to build it as a middleware without changing swift - but with time I see it part of swift19:45
portantesounds reasonable19:46
portantego for it19:46
davidhadastorgomatic: the region approach does not allow placement control which is critical for certain customers19:46
notmynamedavidhadas: like portante said, implementing it as middleware as a first step and demonstrating how it works is a great way to proceed19:47
notmynamedavidhadas: any other questions about it?19:47
davidhadasno - sounds good19:47
notmynamegreat :-)19:47
*** teal3 has joined #openstack-meeting19:47
zaitcevI can't imagine this monstrous container-sync in middleware. Surely it needs a background process of some kind. Currently IIRC container-sync parasites on replicator.19:47
claygdavidhadas: I think also any improvements to container-sync would be appreciated19:47
notmyname#topic directory storage19:47
*** openstack changes topic to "directory storage (Meeting topic: swift)"19:47
notmynameI have no idea what this is? who added it to the meeting and what is it?19:48
claygzaitcev: seperate daemon yeah?19:48
*** dprince has quit IRC19:48
portanteis this the storage_directory() code changes in DiskFile and db.py?19:48
davidhadasclayg: I agree but this is orthogonbal19:48
portantedavidhadas: ^^^19:49
notmynameportante: the meeting agenda page has "Directory storage  - can we move forward with this?"19:49
davidhadasStorage directory is me asking how are we going to continue with this pathc19:49
notmynamewhat path?19:49
davidhadas2 weeks ago we said that we want to have it combined with time to the diskFile and since we did not progress19:49
davidhadashttps://review.openstack.org/#/c/32563/19:49
*** michchap has joined #openstack-meeting19:50
portantecurrently the DiskFile work is in a refactoring phase ... I was unavailable due to the Red Hat summit (in Boston!) and am now back on the case19:50
notmynamedavidhadas: looks like a good idea. what did you need addressed here that shouldn't be addressed in gerrit on the patch?19:50
davidhadasA decission to cont with it19:50
notmynamewhy wouldn't you?19:51
davidhadasIts for the reviewers to review - not for me to do :)19:51
*** therve has joined #openstack-meeting19:51
davidhadasI did what I could19:51
davidhadas;/19:51
portantethe gist of the issue, IIRC, is that the patch proposed a function that behaved differently based on the arguments19:51
*** jlucci has quit IRC19:51
notmynameok, then let's address the code issues in the patch in gerrit as code reviews. no need to do code reviews in here19:52
portantethere is refactoring work in the DiskFile stuff coming that might make this cleaner19:52
portantenotmyname: k19:52
notmyname#topic other19:52
*** openstack changes topic to "other (Meeting topic: swift)"19:52
notmynameanything else?19:52
notmynameok. thanks for your time, everyone :-)19:53
notmyname#endmeeting19:53
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"19:53
openstackMeeting ended Wed Jun 26 19:53:11 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:53
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-06-26-19.01.html19:53
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-06-26-19.01.txt19:53
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-06-26-19.01.log.html19:53
*** jking_swift has left #openstack-meeting19:53
*** zaitcev has left #openstack-meeting19:53
*** tspatzier has joined #openstack-meeting19:55
*** jhenner has joined #openstack-meeting19:57
*** nicolascrowell has joined #openstack-meeting19:57
*** nicolascrowell is now known as tealteal19:58
*** shardy has joined #openstack-meeting19:58
davidhadasclayg: any conclusion from the discussion above with golt?19:59
davidhadas(on account acls)19:59
*** ayurchen has joined #openstack-meeting19:59
*** bgorski has joined #openstack-meeting19:59
*** ayurchen has joined #openstack-meeting20:00
shardy#startmeeting heat20:01
openstackMeeting started Wed Jun 26 20:01:10 2013 UTC.  The chair is shardy. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
*** openstack changes topic to " (Meeting topic: heat)"20:01
openstackThe meeting name has been set to 'heat'20:01
shardy#topic rollcall20:01
*** openstack changes topic to "rollcall (Meeting topic: heat)"20:01
*** rpothier_ has joined #openstack-meeting20:01
*** jlucci has joined #openstack-meeting20:01
asalkeldo/20:01
tspatzierhi20:01
SpamapSahoy!20:01
kebrayhello20:01
jpeeleryo20:01
bgorskio/20:01
stevebakerpong20:01
therveHoy20:01
radixoh hey20:02
*** randallburt has joined #openstack-meeting20:02
radixasalkeld: I now realize just how late this meeting is for you. you're dedicated :)20:02
radixwell, early I guess :)20:02
asalkeldit is 6am20:02
randallburto/20:02
*** lpabon_ has joined #openstack-meeting20:02
*** michchap has quit IRC20:02
*** tealnick has joined #openstack-meeting20:03
shardyOk, hi all, lets get started! :)20:03
shardy#topic Review last weeks actions20:03
*** openstack changes topic to "Review last weeks actions (Meeting topic: heat)"20:03
*** jhenner has quit IRC20:03
sdakeo/20:03
shardyhey sdake20:03
shardy#link http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-06-19-20.00.html20:03
shardytwo actions:20:04
*** lpabon has quit IRC20:04
shardy#info sdake to raise BP re gold images20:04
shardythat happened:20:04
*** tealteal is now known as ateam20:04
shardy#link https://blueprints.launchpad.net/heat/+spec/cloudinit-cfntools20:04
ateamquit20:05
*** ateam has quit IRC20:05
shardy#info asalked to write up AS/Ceilometer wiki20:05
shardythat also happened:20:05
asalkeld#link https://wiki.openstack.org/wiki/Heat/AutoScaling20:05
*** gholt has left #openstack-meeting20:05
radixyes, thanks asalkeld :)20:05
shardythanks asalkeld :)20:06
therveIndeed20:06
asalkeldso still need to chat to radix and therve about20:06
asalkeldit20:06
shardysdake: the cloud-init cfntools looks interesting20:06
shardysdake: aiming for h2 or h3?20:06
*** teal3 has quit IRC20:06
sdakemaybe h3 depends how native-nova-instance comes along20:06
*** zhiyan has quit IRC20:06
shardysdake: ok, cool20:06
sdakeI finally got my devstack working - so can make some progress20:07
sdakethat blueprint will only take a couple days20:07
sdakethe one you linked above20:07
shardyanyone else got anything to raise from last week?20:07
tspatziersdake, is that a generic approach for installing any kind of "agent" or just cfn-tools?20:07
stevebakersdake: SpamapS's os-collect-config may be doing the metadata fetch for cfntools, just something to keep in mind for that bp20:07
sdakeany agent tspatzier20:07
tspatziersdake, sounds interesting20:07
sdakemy thinking is you put a agent directory in a config file, and bam it gets loaded20:08
SpamapSRight I just submitted os-collect-config to stackforge20:08
thervesdake, There is some limit on how much you can put in user data no?20:08
sdaketherve yes, I added compression to userdata20:08
sdakebut there may be some upper limits20:08
sdakeunfortunately userdata compresses into base64 ;(20:08
randallburtthere will be cloud-provider-specific limits too, but we can sort that20:08
sdakecan't send binary20:08
therveYeah20:09
shardysdake: any idea what the compressed limit will be, roughly?20:09
shardythe uncompressed limit is really low iirc20:09
stevebakersdake: does this put the actual agent source in the userdata? cfntools tarball is already close to the limit20:09
*** lpabon_ has quit IRC20:09
sdakeshardy no idea20:09
SpamapShttps://github.com/SpamapS/os-collect-config.git until it is added in stackforge. :)20:09
sdakestevebaker yes20:09
*** lpabon has joined #openstack-meeting20:09
*** ffive has joined #openstack-meeting20:09
therveIt's fairly low in EC2, like 16k or something20:09
sdakeit puts the agent files in the userdata and compresses them, then base64 encodes them20:09
fsargento/20:09
sdakeec2 is 16k, nto sure what openstack is20:10
shardysdake: I'm just thinking we need to ensure we don't leave a tiny amount of space for template userdata stuff by filling up the payload with agents20:10
sdake16k is rediculous20:10
sdakeshardy it will take some testing to see what happens20:10
therveIt's pretty small20:10
stevebakerthe payload might have to be an install script rather than the actual agent20:10
sdakemy compression blueprint ends with a 4k userdata on a small template20:10
SpamapSSo, I'd almost rather see heat just serve the cfntools tarball to the instance rather than shove it into userdata.20:10
randallburtor from swift?20:10
shardystevebaker: that's what I was thinking, but cloud-config already allows you to specify scripts, which could e.g pip install stuff20:11
tspatzierrandallburt, nice idea20:11
sdakepip install has problems20:11
asalkeldso why not just add a pre-userdata script to install cfntools?20:11
sdakeif pip mirrors are down, instance wont start20:12
shardySpamapS: or just specify a url in a config file, which could be anything, webserver, pre-signed swift url, etc20:12
SpamapSrandallburt: yeah having it in swift or just having a configurable URL for them in the engine seems like it would work fine.20:12
sdakeif network is slow, pip install times out20:12
sdakereally we don't want to pip install anything at image start time20:12
sdakekey is to be local20:12
radixI'm sure the NSA has clouds that don't have Internet access at all, too :)20:12
therveNot if you don't have a mirror20:12
sdakespamaps I'll try that out20:12
*** SumitNaiksatam has joined #openstack-meeting20:12
SpamapSDoesn't have to be pip.. just needs to be something which can encapsulate tools.20:12
sdakeya config drive might work too20:13
sdakeanyway feel free to discuss on the blueprint :)20:13
shardyOk, sounds good20:13
shardy#topic h2 blueprint status20:13
*** openstack changes topic to "h2 blueprint status (Meeting topic: heat)"20:14
asalkeldsdake, agent tools always a popular discussion point20:14
stevebakerlol20:14
sdakeasalkeld groan :(20:14
shardy#link https://launchpad.net/heat/+milestone/havana-220:14
shardytwo weeks until h220:14
sdakestevebaker been busy - 17 bps ;)20:14
shardy#link https://wiki.openstack.org/wiki/Havana_Release_Schedule20:15
shardyI've bumped a couple of blocked/not started things to h3 already20:15
sdakeoh i guess those are bugs20:15
shardyanything else there which probably  won't make it?20:15
*** timductive has joined #openstack-meeting20:15
randallburtdepends on reviews, but I'm good20:15
*** jsloyer has quit IRC20:16
sdakehttps://bugs.launchpad.net/heat/+bug/115413920:16
SpamapSI'm starting to worry that I haven't started on rolling updates, so it may not make H3, but nothing in H2.20:16
sdakenot a real high priority and not sure I'll have time to fix it20:16
shardyOk, cool, well if in doubt please start bumping rather than suddenly deferring lots of things near the milestone20:16
stevebakerI'll be switching to quantum by default, so should start getting some traction on those quantum bugs20:17
shardystevebaker: sounds good20:17
*** jsloyer has joined #openstack-meeting20:17
sdakei'd like tot switch to quantum by default too, stevebaker if you sort out devstack + quantum can you share your localrc?20:18
sdakemine seems to not get dhcp addresses20:18
shardyso on a related-to-h2 note, I'm unfortunately going to be on holiday for the two weeks around the milestone (booked before I took the PTL role on..)20:18
*** vipul|away is now known as vipul20:18
stevebakersdake: I made some progress yesterday, will pm20:18
sdakethanks20:18
shardyso I need a volunteer to handle the release coordination, speaking to ttx about go/no-go and generally making sure what we end up with works20:18
shardyanyone keen?20:18
stevebakerI can20:18
shardystevebaker: OK, thanks - I'll follow up with you to discuss the details20:19
stevebakerSpamapS: we should do a heat-cfntools release too, and switch the element to install from pip?20:19
shardy#info stevebaker to do h2 release management while shardy on pto20:19
*** IlyaE has joined #openstack-meeting20:20
SpamapSstevebaker: +120:20
SpamapSstevebaker: IMO we should do the heat-cfntools release now20:20
SpamapSand way more often20:20
SpamapSit has had a ton of improvement20:20
stevebakeryeah20:20
shardyanyone like an action to do that?20:20
SpamapSeven if I am trying to kill it, as yet unsuccessful, its rather wiley, like its old man20:20
shardylol20:21
* SpamapS raises Dr. Evil eyebrow at heat-cfntools20:21
stevebakerits not being killed, just neutered ;)20:21
shardy#info heat-cfntools release to be made prior to h220:21
* SpamapS suggests we rename cfn-hup to SCOTTYDONT20:21
shardyOk, that's all I have for today20:22
*** mkollaro has joined #openstack-meeting20:22
shardy#info open discussion20:22
*** dfg has left #openstack-meeting20:22
stevebakerGenericResource for integration tests20:22
bgorski+120:23
radixasalkeld, therve: do you guys want to have a chat now/after the meeting?20:23
stevebakerI'd like to register GenericResource by default again, so it can be used in tempest templates20:23
therveWell after is a bit late for me20:23
shardystevebaker: could it just be loaded as a plugin?20:23
stevebakerand extend it so it can do mock delays during in-progress states20:23
radixtherve: ok20:23
SpamapSSo..20:24
SpamapSResourceFacade20:24
asalkeldradix might help to do an informal first20:24
shardystevebaker: or do you mean put it in engine/resources?20:24
asalkeldSpamapS, that is only usable to a nested stack20:24
stevebakershardy: it could, devstack would have to configure that though - I don't really see the harm in it being registered by default though.20:24
radixok20:24
asalkeldso small user base20:24
stevebakershardy: yes, back to engine/resources20:24
radixby the way: https://twitter.com/radix/status/34998639297102233620:25
stevebakerit could be useful to users, as a placeholder in their templates20:25
shardystevebaker: I guess it's not that big of a deal, but if it's only ever going to be used for testing, it'd be kind of nice for it to be in a test-appropriate location20:25
SpamapSasalkeld: The term still makese no sense to me.20:25
*** vijendar has joined #openstack-meeting20:25
*** Alex_Gaynor has joined #openstack-meeting20:25
*** tomprince has joined #openstack-meeting20:25
asalkeldSpamapS, open to others...20:26
radixasalkeld, therve: anyway I kind of want to let you guys talk about linear vs circular dependency20:26
shardyradix: is it you or the cat typing? ;)20:26
radixI'm in the middle20:26
radixshardy: we cooperate ;-)20:26
randallburtshardy, stevebaker: would it make sense just to leave it where it is and configure the tempest integration stuff to load plugins from tests/resources?20:26
SpamapSradix: that explains all the references to mice.. ;)20:26
radixhehe :)20:27
shardyrandallburt: that's basically what I was suggesting, but I'm not strongly opposed to moving it if needed20:27
*** vijendar has quit IRC20:27
therveasalkeld, Right, what do you think of "duplicating" the server creation in the AS service?20:27
randallburtfwiw, I'd rather it stay in a test-y place.20:27
*** vijendar has joined #openstack-meeting20:27
stevebakerrandallburt: I'll look into that, but I'm not against moving it20:27
SpamapSAnyway, please respond on openstack-dev if you have some insight for me to help me understand what Fn::ResourceFacade means.20:27
therveasalkeld, So that it's possibly standalone20:27
shardySpamapS: I agree the resource facade naming is awkward, but I've got no better alternatives to suggest20:27
asalkeldradix, well we need to dream up a usable solution20:27
*** sushils has joined #openstack-meeting20:28
asalkeldjust not sure on what feature that provides20:28
radixI think SpamapS's use cases may also be relevant to the way the AS-Service and Heat fit together20:28
asalkeldwhat use case was that?20:28
radixasalkeld: ok, I'll send an email to openstack-dev (or just add something to the wiki page) about the dreamt up solutions. I can write up two alternatives20:28
radixasalkeld: he's talked about being able to address the individual nodes in a scaling group20:28
*** michchap has joined #openstack-meeting20:29
asalkeldI have some ideas for that20:29
asalkeldradix, do you have time for a chat after this?20:29
shardyradix: I was working on the InstanceGroup resource today, and thought it's pretty dumb that we don't store the instances in the DB20:29
*** lbragstad has quit IRC20:29
radixasalkeld: yep, plenty20:29
asalkeldcool20:29
*** SergeyLukjanov has joined #openstack-meeting20:29
shardyI guess that will be fixed as part of bug 1189278 tho20:30
asalkeldshardy, i still think instancegroup should be a special type of nested stack20:30
radixshardy: yeah but I just want to understand the use cases better20:30
shardyasalkeld: Yeah, maybe that would work20:30
SpamapSFor the record, I am -1 on AS spinning up instances for itself. I'd much rather see auto scaling as a subset of ceilometer's functionality suitable for general u[D[D[D[D[D[D[D[D[D[D[D[D[D[D[D[D[Dser consumption.20:31
shardyasalkeld: that would actually make the stuff in there which converts from string into GroupedInstance resources much cleaner (or unnecessary)20:31
asalkeldSpamapS, agree20:31
*** sarob_ has joined #openstack-meeting20:31
asalkeldshardy, excactly20:31
therveSpamapS, I'm not sure those are contradictory?20:31
radixso, I think we have a pretty strong interest in *allowing* autoscale to be able to spin up instances without needing to use Heat templates20:31
therveSpamapS, I mean, ceilometer would need some kind of service to autoscaling?20:31
radixat least, without requiring the user to care about Heat templates20:31
*** adalbas has quit IRC20:32
shardySpamapS: You may be right, but we need to get the first stage of ceilometer integration done, then we'll have a clearer picture of what should do what20:32
SpamapStherve: ceilometer needs a place to send notifications to.20:32
randallburtso use webhooks and let orchestration set up autoscale how it sees fit while allowing others to spin up their own orchestration/scaling solutions.20:32
SpamapSshardy: agreed20:32
sdakeradix I get that, but what I don't get is how you plan to communicate to the service the metadata which describes the autoscaling20:32
shardySpamapS: my expectation was that CM would notify us when to spin up instances, or kill them20:32
shardynot that CM would do the orchestration part20:33
radixsdake: do you mean in the "user is using Heat templates" case?20:33
sdakeradix I mean the user needs some userdata, and some parameters around scaling20:33
asalkeldsdake, launchconf20:33
therveshardy, Well not really? It would notify us when a load is high, or something20:33
SpamapSshardy: precisely my thinking as well. If AS is allowed to do that independent of Heat, then it will make the instances inside AS unaddressable (or special cased) by Heat.20:33
sdakeyes launchconfig from aws speak20:33
sdakethat is like a template20:33
radixsdake: so yeah, that's the debate. I see two possibilities20:34
shardytherve: Yeah, which we then map to an AS action via the ScalingPolicy associated with the alarm/event20:34
*** Alex_Gaynor has left #openstack-meeting20:34
therveRight ok20:34
radixI think I'm going to write up these two possibilities and we can all have concrete options to discuss20:34
asalkeldI'd advocate a special nested stack that as can update20:34
sdakeradix sounds like a good openstack-dev topic ;)20:34
radixyes20:34
SpamapSso to me, an instance group should just be an array of resources. AS would use notifications to operate on that array. Said arrays are useful without AS too, so I believe the instance management should only be in Heat.20:34
*** sarob has quit IRC20:34
shardyasalkeld: I'm starting to agree with you.. :)20:34
asalkeldwith a parameter giving the number of instances20:35
shardythen an AS action is just handle_update, like the loadbalancer now is20:35
asalkeldso no worries about config20:35
*** andrew_plunk has joined #openstack-meeting20:35
asalkeldyea20:35
sdakegotta pick robyn up from airport bbl20:35
*** jasond has joined #openstack-meeting20:35
sdakeo/20:35
SpamapSasalkeld: you also need to be able to say "remove this instance that is performing inefficiently"20:35
shardyasalkeld: +120:35
radixI'll make sure to include use cases20:35
*** sarob_ has quit IRC20:36
SpamapSor "remove this instance that has been compromised ...20:36
asalkeldyea20:36
SpamapSBoth of those things are things Heat needs to support regardless of AS being smart enough to remove inefficient instances eventually.20:36
shardySpamapS: that's a differnt type of resource, a specialized InstanceGroup20:36
*** dkranz has quit IRC20:37
SpamapSshardy: what makes it special?20:37
asalkeldworks on an array?20:37
asalkeldnot just one resource20:37
shardySpamapS: the fact that you differentiate health of individual instances, rather than just adding or removing them in a dumb way, like we currently do20:37
shardySpamapS: I'm not saying it's a bad idea, but just that it should be e.g InstanceMonitorGroup or something20:38
SpamapSshardy: right, I'm saying that independent of AS.. as an operator.. one needs these capabilities.20:38
SpamapSgah20:38
SpamapSone group with all the capabilities please :)20:38
SpamapS(maybe not everything turned on, but don't make me delete all the servers just to turn on a nice feature)20:39
radixYeah, I kinda feel like there should be an "InstanceGroup" living in Heat that is manipulated by other things20:39
shardySpamapS: what you're suggesting implies a more detailed set of metrics than is necessary for simple scaling20:39
radixan administrator might remove an instance, an autoscale service might add an instance20:39
asalkeldshardy, that is ok20:39
asalkeldmore policy20:39
asalkeldmore complexity20:39
radixin other words, composition instead of inheritance :)20:39
shardyasalkeld: so would CM alarms allow aggregation of several metrics, to make the alarm decision?20:40
SpamapSshardy: Agreed! What I'm suggesting is that the fundamental thing that AS should operate on is a fully addressable array of servers, and that operators need that too.20:40
asalkeldyea you just tag the instances20:40
radix+120:40
radixto SpamapS20:40
shardySpamapS: yep, which moving to a nested stack would actually give you, as asalkeld pointed out20:40
SpamapSyeah thats basically already what I'm doing in tripleo because InstanceGroup doesn't allow addressing the servers. :-P20:41
*** michchap has quit IRC20:41
radixin the nested stack model, are the individual instances actually Resources?20:41
asalkeldyes20:41
shardySpamapS: OK, well I think we're all agreed that we need to fix that ;)20:41
radixso... doesn't this contradict the opinion that resources shouldn't be created/removed dynamically via API?20:41
asalkeldno20:41
SpamapShttps://github.com/stackforge/tripleo-heat-templates/blob/master/nova-compute-group.yaml20:41
SpamapSfor reference :)20:41
asalkeldyou are updating the stack20:42
radixasalkeld: are you suggesting that all manipulation of the substack be done with uploading a template?20:42
*** otherwiseguy has joined #openstack-meeting20:42
shardyradix: no, you are updating the resource, which just happens to be a nested stack underneath20:42
SpamapSNote "NovaCompute0" ... You can guess how we scale up/down :)20:42
*** mrodden has joined #openstack-meeting20:42
asalkeldradix, no20:42
radixshardy: right but there are resources you're creating and removing inside that substack20:42
asalkelduse the Stack() class20:42
asalkeldand have some smarts in heat20:42
asalkeldbut talk to it via update20:43
shardyradix: yes, which is fine, and a side-effect of that is that they are addressable via a fully-qualified name via the API20:43
asalkeldor some action20:43
radixI see20:43
shardybecause the nested resources are real resources20:43
shardyjust not defined at the top-level20:43
radixso the "adjust" API (to be created) on the InstanceGroup will add or remove Instance resources from its substack?20:43
radixinternal substack20:43
*** enikanorov has joined #openstack-meeting20:43
shardyit also means we can use the same update method for user-template updates and internal resource updates (like is now done for LoadBalancer, thanks andrew_plunk ;)20:44
andrew_plunk;)20:44
asalkeldradix,  or update20:44
*** jsloyer has quit IRC20:44
radixyeah, whatever it's called20:44
radixokay, that sounds sensible to me20:44
asalkeldand pass it some new metadata20:44
radixtherve: what do you think of this?20:45
radixI like the idea of AutoScale-Service hitting this API in Heat to add or remove instances20:45
therveradix, Trying to digest it :)20:45
andrew_plunkradix: that sounds like a good separation of concerns20:45
asalkeldif you want we can chat further about it20:45
shardyradix: there's no adjust API needed really, you just update the template, or trigger a scaling event20:46
radixshardy: what's "trigger a scaling event"?20:46
*** avishayb_ has joined #openstack-meeting20:46
shardyradix: webhook, either called from ceilometer, or somewhere else20:46
therveshardy, You need an API if you want to support SpamapS' use cases20:46
therveLike removing a specific instance20:46
radixshardy: once we have the AS-Service, ceilometer should only be talking to it, IMO, and the AS-Service should talk to Heat in response20:46
therveHum or maybe there is a property of nested stack I'm missing20:47
randallburt"removing a specific instance" should just be a template update as well, though wouldn't it?20:47
randallburtassuming the nested stack implementation20:47
radixrandallburt: the problem is that substack wasn't created by a template20:47
therverandallburt, You may be right20:47
therveYeah but it would be20:47
asalkeldradix,  heat will always talk to as20:47
shardytherve: I'm still not convinced we need a whole new API to allow that, but I guess we'll see :)20:48
asalkeldyou have to create/destory the as group/as policy resource20:48
radixasalkeld: right I agree... I don't think that's related to my point though20:48
*** lbragstad has joined #openstack-meeting20:48
radixI was just saying that long-term, ceilometer should not talk directly to Heat, but rather go through the AS-Service which is where scaling policies will live20:48
SpamapSradix: its not created by a template, but it has one, and that template can be manipulated by any entity, AS or not.20:48
shardytherve: I think a special type of resource update is all that is needed, ie a native scaling group resource with a very flexible properties schema20:49
therveshardy, Sounds about right20:49
radixSpamapS: agreed. I just think that if you as an administrator wants to remove a specific instance it's a crappy workflow to download a reflected template, delete a few lines from it, and then reupload it to that stack20:49
SpamapSI agree there's a need for an API for stack manipulation in an imperative fashion... that would need to be the only way users were allowed to mess with internally created stacks.20:49
radixbut that's not related to my problem :)20:49
asalkeldradix, that is not what we are suggesting20:49
*** avishayb has quit IRC20:49
randallburtradix: maybe so but one that's really easy to automate20:50
* stevebaker has to go20:50
radixasalkeld: my statement to to spamaps is not about autoscaling at all20:50
SpamapSBasically AS is just a smart, hyper vigilant robotic operator. :)20:50
radixit's unrelated. just an aside.20:50
shardyradix: I'm saying you allow control of it from the top-level template definition20:50
shardyor via a special type of webhook update20:50
radixshardy: even to talk about individual instances? I guess there could be an array of IDs in the properties?20:50
SpamapSI think we're going to need more concrete foundations to stand on if we're going to continue this discussion.20:51
radixyes, need a list of use cases.20:51
SpamapSPerhaps ideas can be put into templates and sent to the ML?20:51
randallburtor a map/json property20:51
shardyradix: something like that, yes, expose the array via a resource attribute, and allow explicit specification of a list of instance uuids via a property20:51
SpamapStemplates/api calls/etc I mean.20:51
radixshardy: yeah I can get behind that20:51
SpamapSanyway, my poor kids are about to melt, have to take them for lunch now.20:51
radixSpamapS: seeya :)20:51
radixthanks for the input20:52
SpamapSradix: and thank you. :)20:52
SpamapSreally thank you everyone for coming to this discussion with open minds... I think the end product is going to be really great.20:52
* SpamapS disappears20:52
shardyOk, well as mentioned earlier, I think we'll be better placed to plan the next steps of this after asalkeld is done with the watch-ceilometer work20:52
shardybut we can keep discussing it :)20:53
*** ffive has quit IRC20:53
shardyreal-world use cases are useful, lets keep adding those20:53
therve:)20:53
shardyOk, anyone have anything else before we wrap things up?20:53
*** woodspa has joined #openstack-meeting20:53
radixis anyone else particularly interested in starting an openstack-dev about this, or shall I still do that?20:53
therveJust one thing maybe20:53
radixI have been trying to think of how to write an email for like two days but still haven't been able to, but now with this conversation I think I have a good base20:53
asalkeldradix, you could alter the wiki20:54
therveThere was some concern that the ceilometer integration was backward incompatible20:54
asalkeldthink about use cases20:54
therveCould we create new resources to workaround that?20:54
shardyradix: I'd keep adding to and refining the wiki, and use openstack-dev for more contentious stuff where we need to argue a bit first ;)20:54
radixalright, sounds good20:54
radixtherve: don't know what you're talking about20:54
radixyou mean the stuff asalkeld is working on?20:55
therveradix, Keep the current resources using the cfn monitoring20:55
therveYeah20:55
asalkeldwell we want to get rid of our cw20:55
asalkeldit is not scalable20:55
*** spzala has quit IRC20:55
asalkeldand basically sucks20:55
therveOkay :)20:55
radixwhat's cw?20:55
asalkeldcloud watch20:55
radixah. ok20:56
*** IlyaE has quit IRC20:56
shardytherve: at one point we did say we were going to maintain the old stuff for one cycle, but tbh, I'm not sure if we want to do that20:56
asalkeldbut we do need to be careful20:56
*** stevemar has quit IRC20:56
asalkeldmigrating alarms would be _interesting_20:56
shardyif we do, then I guess we'll have to say there are limitations, like multiple engines can only work whem the cw stuff is disabled20:56
therveshardy, Fair enough. It's not like the current implementation is going to work for many people :)20:56
shardytherve: exactly, it was just a starting point, now we know there's a better way, so may as well just do that :)20:57
shardywhen we created the cw/watchrule stuff, CM was just starting, so we had no choice20:57
shardy3mins20:57
asalkeldshardy, any response about task work?20:58
asalkeld(qpid)20:58
shardyasalkeld: didn't see any, no...20:58
asalkeldcan celery grow qpid support20:58
radixas usual this has been a very helpful meeting20:58
asalkeldbummer20:58
*** martine_ has quit IRC20:58
shardyI'm sure it's possible (or oslo rpc)20:58
shardyjust a question of who does it20:59
asalkeldyip20:59
shardyit's a blocker for now for sure20:59
shardyright out of time, thanks all!20:59
randallburtcelery uses kombu, but doesn't work directly with qpid last I checked20:59
shardy#endmeeting20:59
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"20:59
openstackMeeting ended Wed Jun 26 20:59:25 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-06-26-20.01.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-06-26-20.01.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-06-26-20.01.log.html20:59
*** tzn has joined #openstack-meeting20:59
thervethanks!20:59
shardyrandallburt: yeah thats what I figured but was seeking confirmation20:59
*** andrew_plunk has left #openstack-meeting21:01
*** sandywalsh has quit IRC21:01
*** amor has joined #openstack-meeting21:01
*** randallburt has left #openstack-meeting21:01
*** jasondotstar has quit IRC21:01
*** rpothier_ has quit IRC21:02
amorv21:02
amor Martín Luther King21:02
*** jasond has left #openstack-meeting21:02
*** bdpayne has quit IRC21:02
*** therve has left #openstack-meeting21:04
*** zehicle_at_dell has joined #openstack-meeting21:05
*** vvechkanov|2 has quit IRC21:05
*** topol has quit IRC21:05
*** tspatzier has left #openstack-meeting21:05
*** enikanorov has quit IRC21:05
*** pcm__ has quit IRC21:06
*** michchap has joined #openstack-meeting21:07
*** lpabon has quit IRC21:08
*** Vernier has quit IRC21:10
*** seiflotfy_ has quit IRC21:13
*** portante has left #openstack-meeting21:14
*** enikanorov has joined #openstack-meeting21:15
*** mkoderer has quit IRC21:16
*** HenryG has quit IRC21:17
*** sandywalsh has joined #openstack-meeting21:17
*** cliu has joined #openstack-meeting21:18
*** sarob has joined #openstack-meeting21:19
*** sarob has quit IRC21:19
*** koolhead17 has quit IRC21:19
*** sarob has joined #openstack-meeting21:19
*** michchap has quit IRC21:20
*** pnavarro has quit IRC21:23
*** tzn_ has joined #openstack-meeting21:23
*** pnavarro has joined #openstack-meeting21:23
*** tzn has quit IRC21:23
*** tzn_ is now known as tzn21:23
*** zul has quit IRC21:24
amorDo you speak Spanish21:25
*** amor has left #openstack-meeting21:25
*** nati_uen_ has joined #openstack-meeting21:28
*** timductive has left #openstack-meeting21:30
*** rnirmal has quit IRC21:30
*** nati_ueno has quit IRC21:31
*** mrodden has quit IRC21:33
*** lbragstad has quit IRC21:33
*** cliu has quit IRC21:33
*** rscottcoyle has quit IRC21:35
*** ryanpetrello has quit IRC21:36
*** krtaylor has quit IRC21:36
*** IlyaE has joined #openstack-meeting21:37
*** cliu has joined #openstack-meeting21:42
*** zul has joined #openstack-meeting21:42
*** timello_ has quit IRC21:44
*** mrodden has joined #openstack-meeting21:44
*** timello_ has joined #openstack-meeting21:45
*** michchap has joined #openstack-meeting21:46
*** nachi_ has joined #openstack-meeting21:49
*** nachi__ has joined #openstack-meeting21:49
*** nachi__ has quit IRC21:49
*** mtreinish has quit IRC21:50
*** jlucci has quit IRC21:51
*** mkollaro has quit IRC21:52
*** ryanpetrello has joined #openstack-meeting21:56
*** michchap_ has joined #openstack-meeting21:57
*** IlyaE has quit IRC21:57
*** michchap has quit IRC21:58
*** michcha__ has joined #openstack-meeting21:58
*** michchap has joined #openstack-meeting21:59
*** cliu has quit IRC22:01
*** michchap_ has quit IRC22:01
*** michchap_ has joined #openstack-meeting22:02
*** michcha__ has quit IRC22:02
*** ryanpetrello has quit IRC22:03
*** michcha__ has joined #openstack-meeting22:03
*** michchap has quit IRC22:03
*** michchap has joined #openstack-meeting22:04
*** lukego has quit IRC22:04
*** cliu has joined #openstack-meeting22:04
*** nati_uen_ has quit IRC22:05
*** michch___ has joined #openstack-meeting22:05
*** michchap_ has quit IRC22:06
*** michchap_ has joined #openstack-meeting22:07
*** michcha__ has quit IRC22:07
*** dcramer_ has quit IRC22:07
*** michchap has quit IRC22:09
*** ivasev has quit IRC22:09
*** michch___ has quit IRC22:10
*** spzala has joined #openstack-meeting22:10
*** afazekas has quit IRC22:10
*** michchap_ has quit IRC22:11
*** tzn has quit IRC22:12
*** listening has quit IRC22:12
*** _TheDodd_ has quit IRC22:12
*** jbrogan has quit IRC22:12
*** tealnick has quit IRC22:13
*** diogogmt has quit IRC22:14
*** vijendar has quit IRC22:18
*** tzn has joined #openstack-meeting22:19
*** lastidiot has quit IRC22:22
*** jhenner has joined #openstack-meeting22:22
*** HenryG has joined #openstack-meeting22:23
*** vijendar has joined #openstack-meeting22:23
*** kebray has quit IRC22:24
*** spzala has quit IRC22:25
*** tzn has quit IRC22:26
*** tzn has joined #openstack-meeting22:27
*** lloydde has quit IRC22:27
*** jlucci has joined #openstack-meeting22:30
*** sarob_ has joined #openstack-meeting22:30
*** cliu has quit IRC22:31
*** sarob_ has quit IRC22:32
*** sarob_ has joined #openstack-meeting22:33
*** lloydde has joined #openstack-meeting22:33
*** sarob has quit IRC22:34
*** tedross has quit IRC22:34
*** zehicle_at_dell has quit IRC22:34
*** jlucci has quit IRC22:34
*** SergeyLukjanov has quit IRC22:35
*** atiwari has quit IRC22:35
*** nati_ueno has joined #openstack-meeting22:36
*** IlyaE has joined #openstack-meeting22:36
*** michchap has joined #openstack-meeting22:37
*** IlyaE has quit IRC22:38
*** krtaylor has joined #openstack-meeting22:40
*** barefoot has left #openstack-meeting22:42
*** neelashah has quit IRC22:44
*** jecarey_ has quit IRC22:44
*** jhenner has quit IRC22:45
*** gongysh has joined #openstack-meeting22:45
*** dolphm has quit IRC22:45
*** zhuadl has joined #openstack-meeting22:45
*** michchap has quit IRC22:50
*** michchap has joined #openstack-meeting22:52
*** tealnick has joined #openstack-meeting22:52
*** michchap has quit IRC22:52
*** mrodden has quit IRC22:53
*** michchap has joined #openstack-meeting22:53
*** fifieldt has joined #openstack-meeting22:56
*** cliu has joined #openstack-meeting22:57
fifieldtgood morning all22:58
lifelesso/22:59
fifieldthihi lifeless22:59
fifieldtWe're about to start the weekly community meeting in a minute or so https://wiki.openstack.org/wiki/Meetings/Community#Weekly_Community_Meeting22:59
fifieldtanyone around for that  ?22:59
* fifieldt waits for a few minutes to see if evgeny appears23:00
* fifieldt waves at the sleeping reed23:01
*** bgorski has quit IRC23:01
*** otherwiseguy has quit IRC23:02
*** tealnick has quit IRC23:03
*** tealnick has joined #openstack-meeting23:04
fifieldtok, looks like it's just me today ;)23:05
*** nati_ueno has quit IRC23:06
fifieldtmeeting cancelled.23:07
*** markpeek has quit IRC23:07
*** shang_ has quit IRC23:07
*** shang_ has joined #openstack-meeting23:08
sarob_im here23:09
sarob_i was on the community channel23:09
*** rcrit has quit IRC23:09
annegentleI'm here23:09
fifieldtoh, hi23:09
fifieldtok, let's have the meeting then :D23:10
fifieldt#startmeeting OpenStack Community23:10
openstackMeeting started Wed Jun 26 23:10:11 2013 UTC.  The chair is fifieldt. Information about MeetBot at http://wiki.debian.org/MeetBot.23:10
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.23:10
*** openstack changes topic to " (Meeting topic: OpenStack Community)"23:10
openstackThe meeting name has been set to 'openstack_community'23:10
* sarob_ waving yes23:10
sarob_no reed?23:10
fifieldthe's well asleep23:10
fifieldtcurrently in italy23:10
sarob_tough break23:10
fifieldtindeed :)23:10
annegentleyeah night time for him23:10
fifieldtJust to quickly run through the action items from the past meeting23:11
fifieldtACTION: evgeny_ to work on bug 1172076 (reed, 23:24:56)23:11
fifieldtOngoing - still shows:23:11
fifieldt$ openssl s_client -showcerts -connect ask.openstack.org:44323:11
fifieldt  Verify return code: 21 (unable to verify the first certificate)23:11
fifieldtACTION: reed to send a request to Chinese User Groups to help translate askbot GUI (reed, 23:35:01) <-- done23:11
fifieldtACTION: fifieldt to summarise conversation with Everett about helping developers consuming OpenStack (reed, 00:18:59) <-- ongoing, has branched out into many discussions23:11
fifieldtany queries about those annegentle, sarob_?23:12
*** hanrahat has quit IRC23:12
*** sarob_ has quit IRC23:12
annegentlenope23:12
*** lloydde has quit IRC23:12
fifieldtcool23:12
annegentledoh lost sarob looks like23:12
fifieldtdammnn23:13
*** sarob has joined #openstack-meeting23:13
annegentleAnd another californian!23:13
fifieldtah california :)23:13
sarobhmm23:13
fifieldtany queries about those action items sarob?23:13
sarobtx at heart23:13
sarobno questions23:14
fifieldt#topic evaluate pending issues from the bug tracker23:14
*** openstack changes topic to "evaluate pending issues from the bug tracker (Meeting topic: OpenStack Community)"23:14
fifieldt#info https://bugs.launchpad.net/openstack-community23:14
fifieldtnormally at this point we'd ask evgeny, our tame askbot developer, to give an update on the bugs assigned to that team23:14
fifieldtbut it doesn't look like any have been completed since last tgime23:15
*** lbragstad has joined #openstack-meeting23:15
fifieldtalso: annegentle, sarob - feel free to spam bugs to that tracker regarding the community tools23:15
fifieldtsans openstack.org website23:15
annegentlefifieldt: yeah looking/browsing now23:15
sarobyeah, like https://bugs.launchpad.net/openstack-community/+bug/109988723:16
annegentlefifieldt: I don't know if you've seen it, but https://bugs.launchpad.net/openstack-org has openstack.org website issues23:16
fifieldtyup, I'm an active contributor there now I have write access to the CMS :)23:16
fifieldtindeed, sarob23:16
fifieldtso the plan is to create a 'user portal'23:16
sarobits not really a bug, rather blueprint23:17
sarobright23:17
fifieldtwhich will have many features23:17
sarobrighto23:17
fifieldtand reed has been scoping the funding and methods to do that out with mark recently23:17
fifieldtbut it's slow going23:17
annegentleI lost my write access to silverstripe, reed was looking into it23:17
sarobbugs tracking as features, or just side effect23:17
*** fnaval has quit IRC23:18
fifieldtyeah, since this is just a small team at the moment it doesn't use blueprints23:18
fifieldtmaybe it should?23:18
*** nati_ueno has joined #openstack-meeting23:18
fifieldtwould you like more visibility of what's going on future roadmap wise?23:18
*** lastidiot has joined #openstack-meeting23:18
fifieldtblueprints work for that well, yes...23:18
sarobreed created one for the portal23:19
fifieldt#info https://blueprints.launchpad.net/openstack-community/+spec/community-portal23:19
sarobright23:19
*** Mandell has quit IRC23:19
fifieldtok, let me do this:23:19
sarobi created two new ones based on reed conversation last week23:19
saroblinking into the portal23:19
fifieldt#action fifieldt to talk to reed about use of blueprints, and making 'large' community plans roadmap more visible23:19
fifieldtcool23:19
sarobokay23:20
fifieldtanything else on the launchpad time, while we're at it?23:20
fifieldtok then23:20
*** IlyaE has joined #openstack-meeting23:20
fifieldt#topic  how to help developers consuming API23:20
*** openstack changes topic to "how to help developers consuming API (Meeting topic: OpenStack Community)"23:20
fifieldtso I had a chat with everett, dianne via email, reed, and annegentle about this23:21
fifieldtand also other people in the foundation23:21
fifieldtanalysed the current poor (say, nonexistent) treatment of SDKs on openstack.org23:21
*** noslzzp has quit IRC23:21
fifieldtand started writing up some stuff to replace the current "getting started" page23:21
fifieldtthe foundation team is meeting at OSCON for a workshop, and one idea we had was to look at the getting started page and smash out some content so that it's accessible for all types of people in the community23:22
fifieldtof course, annegentle, we'll also need to look at http://docs.openstack.org/ and make sure it's pristine as it can be for developers23:23
*** sdake has quit IRC23:23
* annegentle nods23:23
fifieldtI'm thinking we need pretty icons, thoughts? :)23:23
* annegentle just found bootstrap's icons yesterday23:23
*** rcrit has joined #openstack-meeting23:23
fifieldt:D23:23
sarobwould like be like clearer steps for learning openstack23:24
fifieldtindeed23:24
saroband/or provide more options23:24
annegentlecould you redesign api.openstack.org?23:24
fifieldtit's a nice domain name :) I think we have two types of developer23:25
fifieldtone type uses the API directly, - our own coders, people writing SDKs, other hardcore people23:25
fifieldtthe other type relies on libraries and SDKs23:25
fifieldtand that's actually a greater number of people23:25
fifieldtso we need to make sure we deal with both very well23:26
sarobme thinks as instruction gets23:26
annegentleagreed on all23:26
sarobdeeper then expose more details23:26
sarobbeyond just using api23:26
sarobn00bs get confused23:27
fifieldtso, providing actual examples, sarob?23:27
fifieldtwith a tangible use case to follow23:27
sarobdef23:27
fifieldtsounds good to me23:27
sarobwe need to make tiers of material23:28
annegentleI think Diane's user guides are going that direction with your guidance fifieldt23:28
annegentleDashboard > CLI > API > SDK23:28
sarobright23:28
fifieldtindeed, I need to get back to her  on those - sobusybusy23:28
sarobso how can the efforts around training23:28
*** cp16net is now known as cp16net|away23:28
sarobbe spun into23:29
*** cp16net|away is now known as cp16net23:29
sarobcause nobody wants stale, dub material23:29
fifieldthehe, indeed23:29
sarobdup that is23:29
annegentledubstep is awesome tho23:29
sarobso i created this bp https://blueprints.launchpad.net/openstack-manuals/+spec/training-manuals23:30
sarobits meant to create those tiers23:31
sarobtie into the docs23:31
saroband the getting started stuff23:31
*** lloydde has joined #openstack-meeting23:31
fifieldtI agree with creating training content, but my understanding is that this is a contentious board-level issue right now :|23:31
sarobsfbay user group is working on it23:31
* annegentle reads23:31
sarobwell, we are not talking about certs23:32
*** MarkAtwood has quit IRC23:32
sarobjust creating material23:32
annegentlesarob: what's the tie in to refstack exactly?23:32
sarobfoundation board will debate certs, def, etc23:32
sarobthe idea being that to provide examples and scenarios23:33
fifieldtOf course it's always fine to create, but I think it's naive to assume people wouldn't get up in arms, so I'm just going to take a light touch :)23:33
sarobwe need an archetype23:33
*** clayg has left #openstack-meeting23:33
sarobthats me light touch23:34
*** leizhang has quit IRC23:34
fifieldtcool23:34
fifieldtso what's our action item here?23:34
fifieldtshare more widely23:34
*** IlyaE has quit IRC23:34
fifieldtask for people?23:34
fifieldtread & feedback?23:34
sarobwell started with api23:34
*** lbragstad has quit IRC23:35
annegentlesarob: reading more to try to figure out refstack tie-in23:35
sarobroger that23:36
sarobrefstack would be reference stack, debate about whats in, what to call it, etc23:37
annegentlesarob: my understanding of refstack is a test suite23:37
annegentlemore or less23:37
*** gyee has quit IRC23:37
fifieldtin this case: a way to have a defined openstack install, without using vendor Product X?23:38
* sarob putting my user commuity hat on23:38
annegentlesarob: but I do like the idea of real trainees getting real cloud experiences, but they're going to want it for free?23:38
sarobthats def part of it23:38
annegentle#link https://etherpad.openstack.org/RefStackBlueprint23:38
sarobcrowdsourced training23:38
annegentlethat was the link23:38
sarobright23:38
* fifieldt supports the free part and thinks usergroups around the world can deliver training material should it be available23:38
sarobtesting based on refstack, the ins and outs23:39
annegentlesarob: so the training is for cloud users23:39
sarobcontinue to be debated23:39
annegentlesarob: the Dash > CLI > API > SDK range of users23:39
sarobvery similar23:40
annegentleI mean that as a question, is that the range of abilities?23:40
sarobstart easy23:40
sarobgoing to an architect/devops23:40
annegentlesarob: sure if that's what you're seeing as demand23:40
sarobdemand is all over the place23:40
sarobbut they need to start somewhere23:41
annegentlesarob: sure23:41
annegentlesarob: just have to prioritize somewhat :)23:41
sarobif it is selfpaced then np23:41
annegentlesarob: to me, refstack is more about API > SDK23:41
sarobtrue, i was just stating that the training is intended to teach the core of openstack23:42
sarobnot get into the weeds23:42
*** markwash has quit IRC23:42
*** lbragstad has joined #openstack-meeting23:42
sarobrefstack will evenually explain / def the core of openstack23:43
sarobthrough the tests23:43
annegentlesarob: ok got it23:43
annegentlesarob: that helped, thanks23:43
sarob;)23:43
fifieldtindeed23:44
sarobso api teach23:44
sarobcan we mold this topic into the broader training materials plus docs?23:44
sarobas part of community23:44
fifieldt#topic training material, documentation23:45
sarobor massive super overload23:45
*** openstack changes topic to "training material, documentation (Meeting topic: OpenStack Community)"23:45
sarob:)23:45
fifieldt;)23:45
fifieldtyou won't get argument from annegentle or I regarding words on paper, I think :)23:45
annegentleright!23:45
sarobwords are our friends23:45
annegentleOne idea I see coming out of these etherpads is an appendix on certain manuals that offers training materials - objectives, labs?23:46
*** tealnick has quit IRC23:46
sarobthats the idea23:46
sarobwas thinking that could keep the docs as23:47
annegentlesarob: what's unfortunate is that our restructure may gut the compute admin manual and the blueprint fifieldt wrote up for restructuring the doc gets rid of the admin manuals... we're still doing content analysis on it23:47
fifieldtindeed23:47
annegentle#link https://wiki.openstack.org/wiki/Blueprint-restructure-documentation23:47
sarobyeah23:47
annegentlewell, actually, the Compute Admin manual gets rolled into an OpenStack Admin manual -- so it would still work23:48
annegentlefifieldt: Diane and Nick Chase and I just talked about it this week and Nick's going to write an outline23:48
sarobyeah, i think its not the end of the world23:48
annegentlesarob: so it still works for training needs23:48
fifieldtsweet23:48
*** jlucci has joined #openstack-meeting23:48
fifieldtbut yeah, sarob, if there's some content you like in there23:48
annegentlesarob: have you seen the Couch to OpenStack webinar series? Can't help but think there's something to that organizational approach23:48
fifieldtearmark it soon and communicate it23:49
fifieldtbecause the scope is being reduced :)23:49
sarobwe could just thinking about how to break down the training structure to follow the docs structure23:49
annegentle#link http://openstack.prov12n.com/vbrownbag-podcast-couch-to-openstack/23:49
annegentlefifieldt: for which?23:49
fifieldtI'd say for the compute admin manual especially23:49
sarobhmm, nope. i chk it out23:49
*** crank_ is now known as crank23:49
annegentlefifieldt: the way I explained it to Nick this week is we're tacking towards a point like a sailboat :)23:49
sarobnot couch to 5k23:49
annegentlefifieldt: correcting direction as we discover23:50
fifieldtsure, annegentle :)23:50
fifieldtindeed23:50
fifieldtbut I think practically, this means some of the content from compute admin will disappear23:50
sarobhmm, interesting idea23:50
fifieldthence the note to earmark things that might be working in case we miss them off the side of the boat in a tack :)23:50
sarobso getting back to content23:51
annegentlefifieldt: yeah I think the scoping is for "what goes with a release as official docs"23:51
*** crank is now known as crank_23:51
annegentlesarob: and I don't think that training materials can be scoped in "released" docs (which is also a starting discussion with the programs discussion)23:51
annegentleah too many tie ins today sorry23:51
sarobsure i get that23:52
fifieldtperhaps, unless someone else writes them, and it brings billions of contributors annegentle ?  :)23:52
* sarob looking forward23:52
* sarob on the bow23:52
fifieldthehehe23:52
fifieldtmetaphor win!23:52
*** crank_ is now known as crank23:52
annegentlesarob: land ho!23:53
* sarob falls overboard and gets prowed23:53
annegentlefifieldt: just drawing imaginary lines23:53
*** crank is now known as crank_23:53
annegentleesp. since there's a mention of refstack in the room :)23:53
fifieldtaye!23:53
*** crank_ is now known as crank23:53
fifieldtor is that aye aye23:53
fifieldt:)23:53
annegentleor arrrr matey23:53
sarobwhat homework23:53
sarobsfbay hackathon is tomorrow night23:54
annegentlesarob: you have done a good job getting up to speed on doc processes/tools23:54
sarob:)23:54
fifieldt+123:54
annegentlesarob: so that's excellent. I would like to know if people generally have an idea of how training material is usually written with objectives and such23:54
sarobi gots to teach me peoples23:54
annegentleis that what they want?23:54
*** dkranz has joined #openstack-meeting23:55
sarobnow that we getting more of a crowd23:55
saroband yurs input23:55
sarobim going to get some of my university friends23:55
annegentleI guess I'd like more definition from your group too -- what's the audience, be specific. Do you need slide decks? questions? if there's stuff not covered in the manuals, will they add it as manuals or as a training add on23:55
saroband other user groups to chime in23:56
sarobroger that23:56
annegentlesarob: yes, I like that. Trainers are a really unique bunch.23:56
annegentlesarob: and how much lab equip would be assumed/acquired?23:56
annegentlesarob: audience, tasks, equipment.23:56
*** tanisdl has quit IRC23:56
sarobuniversities are already creating their own materials23:56
sarobdetails23:56
sarobright23:56
sarobi going tap in to that gusher23:57
annegentlefifieldt: do you have a sense of the audience yourself? students? new to cloud? IT warriors?23:57
fifieldtindeed23:58
fifieldtup until recently I was also creating an OpenStack course for a university23:58
sarobi will start surveys through meetup for the user groups23:58
fifieldtand I have many thoughts on training23:58
* fifieldt is a trainer23:58
*** salv-orlando has quit IRC23:59
sarobthose involved peoples are the ones to tap first,23:59
annegentle"target population"23:59
* sarob you think so?23:59
* sarob too23:59
annegentlethen "task analysis" and "course objectives"23:59

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