Wednesday, 2013-05-29

*** tomoe__ has quit IRC00:00
*** tomoe_ has joined #openstack-meeting00:01
*** lastidiot has joined #openstack-meeting00:01
*** mkollaro has quit IRC00:05
*** tomoe_ has quit IRC00:05
*** salv-orlando has quit IRC00:08
*** adjohn has joined #openstack-meeting00:10
*** stevemar has quit IRC00:11
*** seanrob has quit IRC00:12
*** lloydde has quit IRC00:12
*** beagles_lessons_ is now known as beagles00:12
*** seanrob has joined #openstack-meeting00:13
*** adjohn_ has quit IRC00:14
*** adjohn has quit IRC00:22
*** ryanpetrello has quit IRC00:23
*** carl_baldwin has quit IRC00:31
*** IlyaE has quit IRC00:32
*** bdpayne has quit IRC00:35
*** dstanek has quit IRC00:37
*** kebray has joined #openstack-meeting00:40
*** kebray has quit IRC00:41
*** ttrifonov is now known as ttrifonov_zZzz00:46
*** jdurgin has quit IRC00:50
*** seanrob has quit IRC00:50
*** adjohn has joined #openstack-meeting00:53
*** kwss has quit IRC01:03
*** lbragstad has joined #openstack-meeting01:04
*** schwicht has quit IRC01:06
*** schwicht has joined #openstack-meeting01:06
*** seanrob has joined #openstack-meeting01:08
*** seanrob has quit IRC01:10
*** seanrob has joined #openstack-meeting01:11
*** seanrob_ has joined #openstack-meeting01:11
*** seanrob has quit IRC01:11
*** eharney has joined #openstack-meeting01:12
*** tomoe_ has joined #openstack-meeting01:15
*** danwent has quit IRC01:16
*** stevemar has joined #openstack-meeting01:19
*** ryanpetrello has joined #openstack-meeting01:23
*** gyee has quit IRC01:26
*** yaguang has joined #openstack-meeting01:27
*** dstanek has joined #openstack-meeting01:28
*** Mandell has quit IRC01:29
*** armax has quit IRC01:41
*** crc32 has joined #openstack-meeting01:42
*** cp16net|away is now known as cp16net01:42
*** stevemar has quit IRC01:48
*** radez_g0n3 is now known as radez01:55
*** dstanek has quit IRC01:55
*** Tross has quit IRC01:57
*** sdake_ has joined #openstack-meeting02:01
*** sdake_ has joined #openstack-meeting02:01
*** Tross has joined #openstack-meeting02:03
*** ryanpetrello has quit IRC02:05
*** stevemar has joined #openstack-meeting02:14
*** markpeek has quit IRC02:16
*** cody-somerville has joined #openstack-meeting02:17
*** cody-somerville has joined #openstack-meeting02:17
*** yaguang has quit IRC02:18
*** sdake_ has quit IRC02:19
*** sdake has quit IRC02:20
*** ewindisch has quit IRC02:25
*** adjohn has quit IRC02:27
*** adalbas has quit IRC02:27
*** eharney has quit IRC02:28
*** cp16net is now known as cp16net|away02:31
*** sdake has joined #openstack-meeting02:32
*** yaguang has joined #openstack-meeting02:32
*** seanrob_ has quit IRC02:32
*** seanrob has joined #openstack-meeting02:33
*** sdake_ has joined #openstack-meeting02:33
*** sdake_ has joined #openstack-meeting02:33
*** seanrob has quit IRC02:37
*** crc32 has quit IRC02:47
*** markpeek has joined #openstack-meeting02:49
*** cp16net|away is now known as cp16net02:50
*** NobodyCam_ has joined #openstack-meeting02:50
*** NobodyCam has quit IRC02:50
*** sdake_ has quit IRC02:52
*** sdake_ has joined #openstack-meeting02:53
*** sdake_ has joined #openstack-meeting02:53
*** yaguang has quit IRC02:56
*** ewindisch has joined #openstack-meeting02:56
*** dstanek has joined #openstack-meeting02:57
*** lloydde has joined #openstack-meeting03:08
*** martine_ has joined #openstack-meeting03:08
*** ewindisch has quit IRC03:10
*** sdake_ has quit IRC03:11
*** lloydde has quit IRC03:13
*** yaguang has joined #openstack-meeting03:16
*** seanrob has joined #openstack-meeting03:22
*** sdake has quit IRC03:23
*** seanrob has quit IRC03:27
*** NobodyCam_ is now known as NobodyCam03:27
*** SergeyLukjanov has joined #openstack-meeting03:27
*** dstanek has quit IRC03:29
*** bdpayne has joined #openstack-meeting03:29
*** jmh_ has joined #openstack-meeting03:39
*** litong has quit IRC03:39
*** adrian_otto has joined #openstack-meeting03:41
*** Tross has quit IRC03:43
*** martine_ has quit IRC03:46
*** adrian_otto has quit IRC03:46
*** sdake_ has joined #openstack-meeting03:52
*** sdake_ has joined #openstack-meeting03:52
*** ewindisch has joined #openstack-meeting03:53
*** radez is now known as radez_g0n303:57
*** lastidiot has quit IRC04:01
*** koolhead17 has joined #openstack-meeting04:08
*** rostam has quit IRC04:20
*** spzala has quit IRC04:22
*** glikson has joined #openstack-meeting04:22
*** seanrob has joined #openstack-meeting04:22
*** rostam has joined #openstack-meeting04:22
*** fnaval_ has joined #openstack-meeting04:22
*** fnaval has quit IRC04:24
*** boris-42 has joined #openstack-meeting04:25
*** danwent has joined #openstack-meeting04:25
*** seanrob has quit IRC04:27
*** gongysh has quit IRC04:28
*** Tross has joined #openstack-meeting04:31
*** garyk has quit IRC04:38
*** haomaiwang has joined #openstack-meeting04:47
*** ewindisch has quit IRC04:49
*** sdake_ has quit IRC04:59
*** IlyaE has joined #openstack-meeting05:00
*** bdpayne has quit IRC05:01
*** mdomsch has quit IRC05:05
*** bdpayne has joined #openstack-meeting05:10
*** glikson has quit IRC05:11
*** glikson has joined #openstack-meeting05:11
*** sdake_ has joined #openstack-meeting05:21
*** sdake_ has joined #openstack-meeting05:21
*** stevemar has quit IRC05:22
*** haomaiwang has quit IRC05:22
*** SergeyLukjanov has quit IRC05:23
*** seanrob has joined #openstack-meeting05:23
*** Mandell has joined #openstack-meeting05:26
*** boris-42 has quit IRC05:28
*** seanrob has quit IRC05:28
*** mrunge has joined #openstack-meeting05:32
*** garyk has joined #openstack-meeting05:35
*** bdpayne has quit IRC05:36
*** mkollaro has joined #openstack-meeting05:37
*** adrian_otto has joined #openstack-meeting05:42
*** sdake has joined #openstack-meeting05:43
*** sdake_ has quit IRC05:45
*** matiu has quit IRC05:46
*** ndipanov has joined #openstack-meeting05:47
*** reed has quit IRC05:47
*** markpeek has quit IRC06:09
*** ndipanov has quit IRC06:16
*** adrian_otto has quit IRC06:17
*** Yada has quit IRC06:19
*** xBsd has joined #openstack-meeting06:19
*** seanrob has joined #openstack-meeting06:23
*** seanrob has quit IRC06:28
*** mikal has quit IRC06:31
*** mikal has joined #openstack-meeting06:32
*** psedlak has joined #openstack-meeting06:35
*** jcoufal has joined #openstack-meeting06:36
*** glikson has quit IRC06:51
*** seanrob has joined #openstack-meeting07:00
*** seanrob has quit IRC07:02
*** seanrob has joined #openstack-meeting07:02
*** seanrob has quit IRC07:07
*** graflu0 has joined #openstack-meeting07:10
*** graflu0 has quit IRC07:12
*** egallen has joined #openstack-meeting07:12
*** glikson has joined #openstack-meeting07:13
*** pnavarro has joined #openstack-meeting07:20
*** SergeyLukjanov has joined #openstack-meeting07:25
*** bogdando has quit IRC07:28
*** matiu has joined #openstack-meeting07:30
*** matiu has joined #openstack-meeting07:30
*** bogdando has joined #openstack-meeting07:31
*** seanrob has joined #openstack-meeting07:33
*** jtomasek has joined #openstack-meeting07:35
*** seanrob has quit IRC07:38
*** salv-orlando has joined #openstack-meeting07:38
*** flaper87 has joined #openstack-meeting07:46
*** markmcclain has joined #openstack-meeting07:49
*** sushils has joined #openstack-meeting07:50
*** markmcclain has quit IRC07:50
*** markmcclain has joined #openstack-meeting07:52
*** markmcclain has quit IRC07:54
*** markmcclain has joined #openstack-meeting07:54
*** yaguang has quit IRC07:56
*** boris-42 has joined #openstack-meeting07:58
*** jhenner has joined #openstack-meeting07:59
*** jang has quit IRC08:03
*** jcoufal has quit IRC08:05
*** yaguang has joined #openstack-meeting08:06
*** adjohn has joined #openstack-meeting08:06
*** jcoufal has joined #openstack-meeting08:06
*** Razique has joined #openstack-meeting08:07
*** johnthetubaguy has joined #openstack-meeting08:08
*** jang has joined #openstack-meeting08:09
*** egallen_ has joined #openstack-meeting08:10
*** stevebaker has joined #openstack-meeting08:12
*** hanney has joined #openstack-meeting08:12
*** egallen has quit IRC08:13
*** egallen_ is now known as egallen08:13
*** egallen has quit IRC08:15
*** egallen has joined #openstack-meeting08:20
*** markmcclain has quit IRC08:20
*** markmcclain has joined #openstack-meeting08:21
*** ttrifonov_zZzz is now known as ttrifonov08:23
*** derekh has joined #openstack-meeting08:24
*** IlyaE has quit IRC08:28
*** adjohn has quit IRC08:32
*** alexpilotti has joined #openstack-meeting08:32
*** seanrob has joined #openstack-meeting08:33
*** haomaiwang has joined #openstack-meeting08:34
*** seanrob has quit IRC08:37
*** xBsd has quit IRC08:57
*** egallen has quit IRC08:57
*** tomoe_ has quit IRC08:57
*** jcoufal has quit IRC08:58
*** xBsd has joined #openstack-meeting08:58
*** Razique has quit IRC09:06
*** xBsd has quit IRC09:07
*** xBsd has joined #openstack-meeting09:10
*** Mandell has quit IRC09:20
*** pnavarro has quit IRC09:23
*** xBsd has quit IRC09:25
*** hanney has quit IRC09:26
*** xBsd has joined #openstack-meeting09:27
*** shang has quit IRC09:32
*** shang has joined #openstack-meeting09:32
*** seanrob has joined #openstack-meeting09:34
*** sdake_ has joined #openstack-meeting09:35
*** sdake_ has joined #openstack-meeting09:35
*** jogo_ has joined #openstack-meeting09:35
*** jogo_ is now known as jog009:35
*** hanney has joined #openstack-meeting09:35
*** seanrob has quit IRC09:38
*** bradjones|away has quit IRC09:40
*** pnavarro has joined #openstack-meeting09:41
*** glikson has quit IRC09:46
*** bradjones|away has joined #openstack-meeting09:48
*** jcoufal has joined #openstack-meeting09:49
*** xBsd has quit IRC09:50
*** glikson has joined #openstack-meeting09:53
*** matiu has quit IRC10:00
*** lbragstad has quit IRC10:08
*** egallen has joined #openstack-meeting10:09
*** egallen has quit IRC10:18
*** lbragstad has joined #openstack-meeting10:19
*** pcm_ has joined #openstack-meeting10:26
*** matiu has joined #openstack-meeting10:28
*** matiu has joined #openstack-meeting10:28
*** matiu has quit IRC10:29
*** matiu has joined #openstack-meeting10:29
*** matiu has joined #openstack-meeting10:29
*** seanrob has joined #openstack-meeting10:34
*** jog0 has quit IRC10:36
*** seanrob has quit IRC10:39
*** egallen has joined #openstack-meeting10:40
*** xBsd has joined #openstack-meeting10:41
*** Kiall has left #openstack-meeting10:45
*** litong has joined #openstack-meeting10:45
*** yaguang has quit IRC10:58
*** pnavarro has quit IRC10:59
*** adalbas has joined #openstack-meeting11:03
*** acfleury has joined #openstack-meeting11:09
*** henrynash has quit IRC11:14
*** sungju has joined #openstack-meeting11:21
*** haomaiwang has quit IRC11:21
*** markmcclain has quit IRC11:22
*** seanrob has joined #openstack-meeting11:35
*** seanrob has quit IRC11:39
*** pcm___ has joined #openstack-meeting11:45
*** SergeyLukjanov has quit IRC11:47
*** egallen has quit IRC11:48
*** pcm_ has quit IRC11:49
*** egallen has joined #openstack-meeting11:51
*** SergeyLukjanov has joined #openstack-meeting11:53
*** netapp has quit IRC11:56
*** ayoung has quit IRC11:57
*** netapp has joined #openstack-meeting11:57
*** dprince has joined #openstack-meeting11:59
*** Tross has quit IRC11:59
*** henrynash has joined #openstack-meeting12:00
*** tomoe_ has joined #openstack-meeting12:01
*** markmcclain has joined #openstack-meeting12:04
*** egallen has quit IRC12:09
*** mrunge has quit IRC12:10
*** SergeyLukjanov has quit IRC12:10
*** pnavarro has joined #openstack-meeting12:11
*** jog0 has joined #openstack-meeting12:11
*** egallen has joined #openstack-meeting12:11
*** acfleury has quit IRC12:15
*** adalbas has quit IRC12:15
*** adalbas has joined #openstack-meeting12:15
*** jhenner has quit IRC12:20
*** jhenner has joined #openstack-meeting12:21
*** egallen has quit IRC12:22
*** lbragstad has quit IRC12:22
*** henrynash has quit IRC12:23
*** alexpilotti has quit IRC12:26
*** dosaboy_ has quit IRC12:28
*** dosaboy has joined #openstack-meeting12:30
*** seanrob has joined #openstack-meeting12:35
*** dosaboy_ has joined #openstack-meeting12:37
*** obondarev has quit IRC12:39
*** dosaboy has quit IRC12:40
*** seanrob has quit IRC12:40
*** enikanorov-w has quit IRC12:41
*** enikanorov-w has joined #openstack-meeting12:41
*** ilyashakhat_ has joined #openstack-meeting12:41
*** ilyashakhat has quit IRC12:41
*** obondarev has joined #openstack-meeting12:41
*** dosaboy has joined #openstack-meeting12:44
*** sungju has quit IRC12:44
*** dosaboy_ has quit IRC12:44
*** sandywalsh has quit IRC12:45
*** dosaboy has quit IRC12:45
*** dosaboy has joined #openstack-meeting12:46
*** eharney has joined #openstack-meeting12:48
*** eharney has quit IRC12:48
*** eharney has joined #openstack-meeting12:48
*** pnavarro has quit IRC12:48
*** egallen has joined #openstack-meeting12:48
*** kashyap has quit IRC12:49
*** martine has joined #openstack-meeting12:50
*** kashyap has joined #openstack-meeting12:53
*** ryanpetrello has joined #openstack-meeting12:56
*** sandywalsh has joined #openstack-meeting12:58
*** radez_g0n3 is now known as radez13:02
*** sdake has quit IRC13:04
*** lbragstad has joined #openstack-meeting13:08
*** yaguang has joined #openstack-meeting13:09
*** jasondotstar has joined #openstack-meeting13:11
*** mdomsch has joined #openstack-meeting13:11
*** stevemar has joined #openstack-meeting13:12
*** bogdando has quit IRC13:15
*** bogdando has joined #openstack-meeting13:15
*** mikal has quit IRC13:18
*** ctracey has quit IRC13:19
*** ctracey has joined #openstack-meeting13:19
*** mikal has joined #openstack-meeting13:20
*** henrynash has joined #openstack-meeting13:24
*** henrynash_ has joined #openstack-meeting13:27
*** henrynash has quit IRC13:28
*** henrynash_ is now known as henrynash13:28
*** jog0 has quit IRC13:29
*** koolhead17 has quit IRC13:29
*** henrynash has quit IRC13:33
*** adrian_otto has joined #openstack-meeting13:34
*** dstanek has joined #openstack-meeting13:34
*** adrian_otto has quit IRC13:35
*** jpipes has joined #openstack-meeting13:35
*** seanrob has joined #openstack-meeting13:36
*** FallenPegasus has joined #openstack-meeting13:38
*** koolhead17 has joined #openstack-meeting13:39
*** koolhead17 has joined #openstack-meeting13:39
*** seanrob has quit IRC13:40
*** woodspa has joined #openstack-meeting13:41
*** flaper87 has quit IRC13:41
*** otherwiseguy has quit IRC13:42
*** markmcclain has quit IRC13:43
*** xBsd has quit IRC13:44
*** SergeyLukjanov has joined #openstack-meeting13:44
*** cp16net is now known as cp16net|away13:45
*** ivasev has joined #openstack-meeting13:46
*** haomaiwang has joined #openstack-meeting13:48
*** xBsd has joined #openstack-meeting13:49
*** matiu has quit IRC13:49
*** xBsd has quit IRC13:51
*** xBsd has joined #openstack-meeting13:55
*** markpeek has joined #openstack-meeting13:56
*** jlucci has joined #openstack-meeting13:58
*** jlucci has joined #openstack-meeting13:58
*** FallenPegasus has left #openstack-meeting14:02
*** mrodden has joined #openstack-meeting14:03
*** pschaef has joined #openstack-meeting14:03
*** pschaef_t has joined #openstack-meeting14:04
*** mrodden1 has joined #openstack-meeting14:05
*** mrodden has quit IRC14:07
*** otherwiseguy has joined #openstack-meeting14:09
*** dosaboy_ has joined #openstack-meeting14:10
*** dstanek has quit IRC14:11
*** dosaboy has quit IRC14:13
*** jpipes has quit IRC14:16
*** danwent has quit IRC14:16
*** jog0 has joined #openstack-meeting14:17
*** lastidiot has joined #openstack-meeting14:18
*** lastidiot has quit IRC14:26
*** cp16net|away is now known as cp16net14:27
*** cp16net is now known as cp16net|away14:28
*** cp16net|away is now known as cp16net14:28
*** tanisdl has joined #openstack-meeting14:29
*** ryanpetrello has quit IRC14:30
*** ryanpetrello has joined #openstack-meeting14:31
*** ayoung has joined #openstack-meeting14:34
*** seanrob has joined #openstack-meeting14:36
*** KurtMartin has joined #openstack-meeting14:37
*** jmh_ has quit IRC14:40
*** seanrob has quit IRC14:41
*** cp16net is now known as cp16net|away14:43
*** jog0 has quit IRC14:49
*** BobBall has joined #openstack-meeting14:52
*** woodspa has quit IRC14:53
*** woodspa has joined #openstack-meeting14:54
*** bpb has joined #openstack-meeting14:57
*** dstanek has joined #openstack-meeting14:57
*** rushiagr has joined #openstack-meeting14:58
*** dolphm has joined #openstack-meeting14:58
johnthetubaguy#startmeeting XenAPI15:00
openstackMeeting started Wed May 29 15:00:13 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
johnthetubaguyhi15:00
johnthetubaguyhands up for the XenAPI meeting?15:00
BobBallo/15:01
*** kebray has joined #openstack-meeting15:01
*** matelakat has joined #openstack-meeting15:01
BobBalland matelakat too :)15:01
matelakathi15:01
johnthetubaguycool, hello15:02
*** spzala has joined #openstack-meeting15:02
johnthetubaguy#topic actions from last meeting15:02
*** openstack changes topic to "actions from last meeting (Meeting topic: XenAPI)"15:02
johnthetubaguymatelakat: how did that documenting go?15:02
*** xBsd has quit IRC15:02
matelakatAs I said, it is a low priority, haven't even touched it.15:03
BobBall*grin*15:03
*** lastidiot has joined #openstack-meeting15:03
johnthetubaguyOK, lets leave that off the actions for next week, its got boring15:03
matelakatfocusing on quantum, and saying hello to smokestack15:03
johnthetubaguy#topic blueprints15:03
*** openstack changes topic to "blueprints (Meeting topic: XenAPI)"15:03
johnthetubaguyso I have made progress with xenapi-server-log15:03
johnthetubaguyassuming someone configures the logging correctly15:04
*** tomoe_ has quit IRC15:04
johnthetubaguyI can now read the logs15:04
BobBallyou mean with the xenstore key?15:04
johnthetubaguy#link https://blueprints.launchpad.net/nova/+spec/xenapi-server-log15:04
johnthetubaguywell, its needs more than the xenstore key, but yes15:04
johnthetubaguy#link https://review.openstack.org/#/c/30301/15:05
BobBallAh - this was WIP15:05
johnthetubaguygot a few other bits till its finished, but the core proof of concept seems OK15:05
BobBallis it still WIP?15:05
BobBallor are you raedy for someone to look at it?15:05
johnthetubaguynope, its up for review15:05
BobBallokay cool15:05
BobBallI'll have a butchers :)15:05
johnthetubaguycool15:05
johnthetubaguyits not that sophisticated, but its a step forward15:06
johnthetubaguyI think we need to worry about deleting old logs too15:06
*** danwent has joined #openstack-meeting15:06
johnthetubaguythat probably shouldn't be the job of logrotate, but I can't quite decide15:06
johnthetubaguyanyhow, its baby steps forward15:06
BobBallsounds good to me15:07
johnthetubaguyso, next one I wanted to touch on was devstack refactor15:07
johnthetubaguy#link https://blueprints.launchpad.net/devstack/+spec/xenapi-devstack-cleanup15:07
johnthetubaguymatelakat: how is that going?15:07
matelakatAt the moment a quantum patch is waiting, after that, I would like to push the network cleanup.15:08
matelakatWe could discuss what we want in that.15:08
matelakatremove internal xapi interface15:08
matelakatsensible defaults15:08
johnthetubaguyyes, I had some people talking about that inside rax15:08
*** egallen has quit IRC15:08
*** kchenweijie has joined #openstack-meeting15:08
matelakatOh, is someone using that if?15:09
johnthetubaguyso, remove that guest install network thing, yes please15:09
matelakatguest install network?15:09
johnthetubaguythat internal xapi interface15:09
*** mrodden1 has quit IRC15:09
matelakatI am not sure if we are speaking about the same stuff.15:09
johnthetubaguyit has many names15:09
johnthetubaguycurrent eth0 on bridge xapi15:09
*** mjmulloc has joined #openstack-meeting15:09
matelakatAnother job would be to modify how the vm is built.15:09
johnthetubaguylets just get the network decided I think15:10
johnthetubaguyfirst15:10
matelakaty15:10
johnthetubaguyso default config, what you thinking?15:10
matelakatBut that will be another change.15:10
*** mjmulloc has left #openstack-meeting15:10
*** ryanpetr_ has joined #openstack-meeting15:10
matelakatDefault config - let's talk about that15:10
johnthetubaguyI recon something like eth0 = management, eth1 = data, eth2 = public15:10
johnthetubaguythat is the domU15:10
matelakatLet's look at the doc.15:11
johnthetubaguydoc?15:11
matelakatmy goal is to align devstack with the official docs15:11
matelakatyou know, the diagram.15:11
johnthetubaguywe probably need to change that now though15:11
BobBallIOW make devstack as close to what we'd recommend people deploying15:11
johnthetubaguyanyways, let me find a link15:11
matelakat#link http://docs.openstack.org/grizzly/openstack-compute/install/apt/content/introduction-to-xen.html#xenapi-deployment-architecture15:11
*** dstanek has quit IRC15:12
johnthetubaguyBobBall: yes, but it needs to be simple no change for devs15:12
matelakatwhat is IOW Bob?15:12
johnthetubaguymatelakat: cool that looks good15:12
johnthetubaguyI think managment network should be dhcp (i.e. home router)15:12
matelakatyes.15:12
*** jmh_ has joined #openstack-meeting15:12
johnthetubaguythen the tenant and public can default to host local private networks?15:12
BobBallIOW = in other words15:13
johnthetubaguyobviously you could create VLANS, etc, if you wish to do multi box setup15:13
*** ryanpetrello has quit IRC15:13
johnthetubaguydoes that sound like what you were thinking?15:13
matelakatI would leave it as an exercise for the user.15:13
matelakatI meant the VLAN and the physical game.15:14
johnthetubaguyerm, would be good to create the default host local networks auto-magically though?15:14
BobBallI agree - don't add complexity to devstack... we can get it to install on whateverthehostisrunning15:14
BobBallhost-local sure, yes15:14
johnthetubaguyah right, absolutaly, no VLAN creation15:14
*** cp16net|away is now known as cp16net15:14
matelakatThe change that has been accepted is already doing this host local stuff.15:14
johnthetubaguythe other Ubuntu installer stuff, that should probably default to eth0 dhcp to match the above15:15
*** henrynash has joined #openstack-meeting15:15
matelakaty15:15
johnthetubaguythen autodetect the management ip address on eth015:15
matelakaty15:15
johnthetubaguyI would just assume a default install of XS I guess (plus XD optimisations / EXT SR)15:15
matelakatAs documented.15:15
BobBallidd15:15
johnthetubaguysounds like we agree on the network defaults?15:15
*** kchenweijie has left #openstack-meeting15:15
*** ladquin has joined #openstack-meeting15:16
matelakatStatic IP could be another job.15:16
johnthetubaguywhat you mean? make it work with a static IP?15:16
matelakatfor now, let's assume dhcp on MGT network.15:16
johnthetubaguy+1 for dhcp for now15:16
matelakatyes, make it work without DHCP15:16
matelakatOkay, so that's an agreement.15:17
johnthetubaguyyeah, lets ignore that for now, we need to worry about proxies too in the complex case15:17
matelakatAlthough the quantum case would need another diagram.15:17
johnthetubaguyyes, that is worth doing15:17
johnthetubaguy#action: need new doc diagram for quantum setup15:17
johnthetubaguymatelakat: you mentioned ubuntu install changes?15:17
matelakatI would like to see the snapshotted VM not connected to any networks.15:18
matelakatOther than that: always update boot parameters15:18
johnthetubaguyin what sense? for the install?15:18
matelakatI meant kernel parameters.15:18
matelakatAt the moment, we are creating a VM with 4 interfaces, and preseed that VM15:19
*** KurtMartin has quit IRC15:19
matelakatAnd than snap it.15:19
johnthetubaguyOFFLINE=true gets close to that in localrc in the domU I think, for refresh15:19
*** fnaval_ has quit IRC15:19
matelakatOFFLINE=true????15:19
johnthetubaguyah, hang on, not sure I get what you mean15:19
johnthetubaguyOFFLINE=true stops the git pulls and apt-get updates, etc15:19
*** fnaval has joined #openstack-meeting15:19
BobBallI've not seen that one before :P15:19
BobBallahhh15:19
matelakatcreate a VM with one interface, preseed it -> remove the interface from the VM -> snap it15:20
*** KurtMartin has joined #openstack-meeting15:20
*** mrodden has joined #openstack-meeting15:20
matelakatGoal: You can change the network configuration without cleaning up the templates.15:20
*** henrynash has quit IRC15:21
matelakatMakes sense?15:21
johnthetubaguyah, yes, good point15:21
BobBallvery much to me too15:21
matelakatOkay.15:21
johnthetubaguythat would really help the retry loop15:21
matelakatI am not sure, if it is all one change.15:21
matelakatWe'll see how big it is.15:21
johnthetubaguyI lost intrested half way through adding those snapshots after getting the test times down to something I could bare15:21
johnthetubaguycool, so that sounds like pleanty15:22
johnthetubaguyand that should leave us in a good place for Havana I guess?15:22
matelakatNow, file some actions please, I like to see the bot doing its job.15:22
johnthetubaguylol, probably best to update the blueprint though?15:22
matelakatsure.15:23
matelakatLet me check my trello board.15:23
matelakatOh, separate volume for cinder in devstack15:23
johnthetubaguyI just updated the BP15:23
johnthetubaguy#link √15:24
matelakatOkay.15:24
johnthetubaguyoops15:24
johnthetubaguy#link https://blueprints.launchpad.net/devstack/+spec/xenapi-devstack-cleanup15:24
*** fnaval has quit IRC15:24
matelakatSo, one more thing that I have is: separate vhd for cinder volumes15:24
johnthetubaguyWork items:15:24
johnthetubaguyGet rid of VLAN configuration: DONE15:24
johnthetubaguyAdd proxy settings for Ubuntu install: DONE15:24
johnthetubaguyBetter network defaults: TODO15:24
johnthetubaguyReconfigure networking without Ubuntu VM re-install: TODO15:24
johnthetubaguySeparate Hypervisor setup: TODO15:24
johnthetubaguymatelakat: sure, but is that critical?15:24
matelakatI would like to see that, because with the loopback device, you get kernel lockups.15:25
johnthetubaguyah, yes, that old fella15:25
matelakatWhich is not really a good experiment.15:25
matelakats/experiment/experience/g15:25
johnthetubaguycool15:26
johnthetubaguyso lets move on to Quantum15:26
matelakatOkay, move.15:26
johnthetubaguyI saw L2 got into master15:26
johnthetubaguyhows DHCP?15:26
matelakatThat's really good thing.15:26
johnthetubaguy:)15:26
matelakatWe have issues with Quantum with oslo.config15:27
*** IlyaE has joined #openstack-meeting15:27
matelakatThat was a separate issue changing [OVS] -> [ovs]15:27
johnthetubaguyoh, thats not specific to XenAPI, but yes15:27
matelakatSo that was sort of blocking me15:27
*** lascii is now known as alaski15:27
matelakatApart from that, a ci job is here:15:28
matelakat#link https://github.com/citrix-openstack/qa/blob/master/xenserver-quantum-devstack.sh15:28
BobBallAlso blocked by a stupid commit I made :)15:28
*** liuxpei has joined #openstack-meeting15:28
matelakatI didn't say that.15:28
*** KurtMartin has quit IRC15:28
BobBalloh15:29
BobBallbut you thought it! :D15:29
matelakatBob's change just highlighted some other issues, but he likes to be punished by himself.15:29
johnthetubaguylol15:29
BobBallJust to fill John in on the details...15:29
johnthetubaguyOK, so you got DHCP working?15:29
matelakatdefine "working"15:29
johnthetubaguyinstances get IP addresses from DHCP?15:30
*** rushiagr has quit IRC15:30
matelakaty15:30
johnthetubaguycool, whats broken?15:30
BobBalldevstack had some libvirt specific variables which were used in common code - I removed the libvirt specific variables and apparently committed it without testing it (although I know I tested something!) - so the upshot is that devstack is currently broken for XenServer and all non-libvirt hypervisors15:30
johnthetubaguyoops15:30
*** jtomasek has quit IRC15:30
matelakat#link https://review.openstack.org/3070315:30
johnthetubaguyI will not update my repo today then...15:30
matelakatUpdate it.15:31
*** sandywalsh has quit IRC15:31
*** rushiagr has joined #openstack-meeting15:31
johnthetubaguyso, I hear OVS plugin is getting deprecated15:32
johnthetubaguydo we know what the plan is getting XCP working with the new one?15:32
matelakatWhich is the new one?15:32
matelakatI need some details.15:32
matelakatWas it on the ML ?15:33
johnthetubaguyit was hinted to on the ML15:33
johnthetubaguylet me check15:33
matelakatI wouldn't care about the future plans.15:33
johnthetubaguyits called ML215:33
matelakatAt the moment.15:33
matelakatML2 is my second revision - It's not even born.15:34
johnthetubaguy"However - do you have any idea about how this kind of feature will play with ML2 and deprecation of OVS plugin?"15:34
*** danwent has quit IRC15:34
johnthetubaguywas in a thread on VXLAN15:34
matelakatAh, how good is that. So that's why quantum folks accepted the L2 patch.15:34
matelakat:-)15:35
johnthetubaguyhttps://blueprints.launchpad.net/quantum/+spec/modular-l215:35
BobBallhaha15:35
*** sdake has joined #openstack-meeting15:35
matelakatLet's keep an eye on it.15:36
matelakatThanks John.15:36
*** garyk has quit IRC15:36
matelakatI need some time to parse that change.15:36
johnthetubaguywell seems like its the new thing, I would ask salvatore15:36
*** bdpayne has joined #openstack-meeting15:36
*** seanrob has joined #openstack-meeting15:37
johnthetubaguyit may require almost zero changes15:37
johnthetubaguyanyways15:37
johnthetubaguy#topic Docs15:37
*** openstack changes topic to "Docs (Meeting topic: XenAPI)"15:37
johnthetubaguyany updated for Xen Doc Day yesterday?15:37
johnthetubaguynothing from me15:37
BobBallnot from me either15:38
matelakat#link https://review.openstack.org/#/c/20105/9/quantum/plugins/ml2/README: It currently works with the existing openvswitch, linuxbridge, and hyperv L215:38
BobBallbut what would you hope we could do for the xen doc day?15:38
matelakat.. agents15:38
matelakatSo this ML2 seems to be higher up in the hierarchy.15:38
BobBallso ML2 is on top of OVS?15:38
johnthetubaguyah, I keep meaning to join in that effort and work on XS OS docs15:38
*** psedlak has quit IRC15:39
johnthetubaguyI think ML2 is the new things to configure OVS rather than the current OVS plugin15:39
*** vkmc has joined #openstack-meeting15:39
*** vkmc has joined #openstack-meeting15:39
matelakatOkay, so as long as Agent stays, we don't care.15:39
*** psedlak has joined #openstack-meeting15:39
*** colinmcnamara has joined #openstack-meeting15:39
johnthetubaguyhopefully15:40
*** psedlak has quit IRC15:41
johnthetubaguy#topic Bugs and QA15:41
*** openstack changes topic to "Bugs and QA (Meeting topic: XenAPI)"15:41
*** rushiagr has quit IRC15:41
matelakatpass15:41
*** seanrob has quit IRC15:41
BobBallSo the biggest one is the devstack bug15:41
matelakatAh QA15:42
matelakatI am trying to reproduce the Smoke things15:42
matelakatAnd I am at around 80%15:42
matelakatnamely here: #link https://github.com/dprince/firestack/blob/master/example_xen.bash#L7115:43
matelakatWho's gonna pick up the devstack one?15:43
BobBallwhich devstack one?15:44
BobBallthe one that I introduced?15:44
matelakatI would like to get quantum and smoke done this week.15:44
matelakatYes, let's call it Bob-Bug-2013/0000000115:44
BobBallWow - that's kind.  suggesting that it's the first bug.15:44
matelakatSo that we have enough digits for the year.15:44
BobBallMy issue with me looking at it is the next few days are likely to be busy15:45
*** anniec has joined #openstack-meeting15:45
BobBallbut I can say I'll take it15:45
BobBallI'll see what I can do tomorrow15:45
matelakatWe can try to do some pair programming15:45
*** pschaef has quit IRC15:45
BobBallSure - although I might fix it tomorrow morning before you get in the office ;)15:46
*** fnaval has joined #openstack-meeting15:46
*** jhenner has quit IRC15:46
johnthetubaguywell, that sounds good15:46
matelakatsuggests Bob-Bug-2013/0000000215:46
johnthetubaguyhow is smokestack then?15:46
*** sandywalsh has joined #openstack-meeting15:47
matelakatLet's say environment setup phase.15:47
matelakatlearning - from my side.15:48
matelakatAll we need is to be able to fix any issues in puppet manifests at the moment.15:48
matelakatAnd I would say we are not really far from being able to do that (hack -> test) cycle.15:49
matelakatAs I said, I would like to get it done this week.15:49
matelakatAny other Q?15:49
BobBallnope15:50
BobBallare we done with the meeting now?15:51
*** zhiyan has joined #openstack-meeting15:51
matelakatJohn has disappeared.15:51
matelakatWhat a chairman!15:51
BobBalland now we can't stop the meeting15:51
matelakatOh Bob15:52
BobBallthat means we have to keep going until John is back15:52
matelakatIt seems, that we have to stay here till the end of the time.15:52
johnthetubaguyhe is here15:52
johnthetubaguysorry15:52
matelakatOh.15:52
johnthetubaguyone more thing15:52
johnthetubaguy#topic open discussion15:52
matelakatGood old SJ.15:52
*** openstack changes topic to "open discussion (Meeting topic: XenAPI)"15:52
johnthetubaguyanything around diskimage-builder?15:53
johnthetubaguyanyone looking at that15:53
matelakatNot really.15:53
BobBallfraid not15:53
johnthetubaguyI noticed it was going for incubation / oslo inclusion15:53
johnthetubaguyOK15:53
*** mkerrin has joined #openstack-meeting15:53
johnthetubaguyI guess it doesn't do our style VHD15:53
*** jbrogan has joined #openstack-meeting15:53
matelakatWhat is the exact use-case for that?15:53
zhiyanhi, folks, how about https://etherpad.openstack.org/linked-template-image , any thoughts?15:54
BobBallI've gotta run - sorry guys - was expecting us to be done by now! Mate, will be back on later if you want to email me.15:54
*** BobBall is now known as BobBallAway15:54
johnthetubaguymatelakat: not sure15:54
*** xyang_ has joined #openstack-meeting15:54
zhiyanDuncanT: around?15:54
matelakatzhiyan, is it about XenAPI?15:55
*** jdurgin has joined #openstack-meeting15:55
*** danwent has joined #openstack-meeting15:55
johnthetubaguyok, so we are done with XenAPI I guess15:55
zhiyanmatelakat: no, just about cinder requirement/dependency: Attaching a volume to a host15:55
matelakatjohnthetubaguy: Is it some debootstrap thingie?15:56
johnthetubaguysorry got distracted at the end15:56
*** jgallard has joined #openstack-meeting15:56
johnthetubaguymatelakat: yep15:56
johnthetubaguyI think its about bootstrapping OpenStack15:56
DuncanTzhiyan: Give it 5 minutes, we aren't due to start yet!15:56
johnthetubaguyso building images, and everything15:56
matelakatzhiyan: I guess cinder meeting is the next, within few minutes.15:56
*** thingee has joined #openstack-meeting15:56
johnthetubaguyyup, we almost done here15:56
johnthetubaguymatelatat: any thing else?15:56
zhiyanDuncanT: oh, sorry, :)15:56
matelakatOkay, let's give the room to the cinder folks.15:56
*** dnoll has joined #openstack-meeting15:56
johnthetubaguy#endmeeting15:56
*** openstack changes topic to "OpenStack meetings"15:56
openstackMeeting ended Wed May 29 15:56:55 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:56
openstackMinutes:        http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-05-29-15.00.html15:56
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-05-29-15.00.txt15:56
openstackLog:            http://eavesdrop.openstack.org/meetings/xenapi/2013/xenapi.2013-05-29-15.00.log.html15:57
zhiyanmatelakat: haha, ok15:57
*** vincent_hou has joined #openstack-meeting15:59
*** haomaiwang has quit IRC15:59
*** cian_ has joined #openstack-meeting15:59
*** winston-d has joined #openstack-meeting16:00
DuncanTCinder people about?16:00
*** garyk has joined #openstack-meeting16:00
winston-dhi16:00
*** jsbryant has joined #openstack-meeting16:00
eharneyhello16:00
zhiyanDuncanT: zhiyan here16:00
cian_hi16:00
thingeeheey16:00
jgallardhello16:00
DuncanT#startmeeting cinder16:00
openstackMeeting started Wed May 29 16:00:41 2013 UTC.  The chair is DuncanT. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: cinder)"16:00
openstackThe meeting name has been set to 'cinder'16:00
xyang_hi16:00
vincent_houhi16:00
jsbryantHi all.  Happy Wednesday!16:01
DuncanTSo no jgriffith this week. 3 items on the agenda so far16:01
*** jsbryant is now known as jungleboyj16:01
*** avishay has joined #openstack-meeting16:01
DuncanTUpdate the wiki or PM or shout up for other items16:01
DuncanT#topic BUGSQUASH16:01
*** openstack changes topic to "BUGSQUASH (Meeting topic: cinder)"16:01
*** ollie1 has joined #openstack-meeting16:01
*** bswartz has joined #openstack-meeting16:02
avishayhi all16:02
DuncanTSo we've a bug squash day scheduled tomorrow... just after the H1 branch was cut, but never mind16:02
bswartzhi16:02
DuncanTAnybody got any questions on that?16:02
avishayYea we should have done it earlier, but we'll get a good start on H2 :)16:03
*** matelakat has quit IRC16:03
thingeeavishay: got some last minute stuff through thanks to winston-d16:03
avishaythingee: cool cool16:04
thingeenothing like last minute being a motivator16:04
avishay:)16:04
DuncanTI'll assume there are no questions then and look forward to the pretty graph plunging tomorrow16:04
med_:)16:04
avishay:)16:04
winston-d:)16:04
jungleboyj:-)16:04
thingee( ͡ಠ ͜ʖ ͡ಠ)16:05
DuncanT#topic Blueprint dependencies and generic local attach16:05
*** openstack changes topic to "Blueprint dependencies and generic local attach (Meeting topic: cinder)"16:05
avishaythingee: lol16:05
eharneyi'm not sure what emotion that is...16:05
med_now that's ascii art or utf-8 art16:05
DuncanTSo zhiyan highlighted the fact that we have a bunch of blueprints that need some flavour of local attach, but that work hasn't been started yet16:05
zhiyanhi please take a look on https://etherpad.openstack.org/linked-template-image , the changes need cinder give some support, glance and nova need attach the volume to glance-api host or nova-compute host..16:06
jdurginare you really after 'locally attaching', or is that just a means to do I/O to the volume?16:07
*** ryanpetr_ has quit IRC16:07
avishayjdurgin: i think the latter16:07
winston-davishay: +116:07
*** lloydde has joined #openstack-meeting16:07
*** ryanpetrello has joined #openstack-meeting16:07
zhiyaneharney: just improve vm provisioning performance, for now we use 'linked' volume to prepare template image, in future, we can use that prepare vm's vdisk directly, such as clone to make cow...16:07
avishayconnectivity issues worry me - cinder nodes may not have HBAs16:07
avishaysame for glance nodes16:08
*** skolathu has joined #openstack-meeting16:08
avishaywhich is why i suggested VMs to do the copies but nobody liked that idea :)16:08
kmartinzhiyan: avishay the etherpad says for iscsi only16:08
DuncanTavishay: In this case the attach is happening on the compute node, just to the host OS rather than direct to a VM, if I understand the plan16:08
zhiyankmartin: not just for iscsi, IMO, for all backend..16:09
zhiyanDuncanT: yes, that is16:09
avishayDuncanT: so this isn't that attach "service" refactor thing?16:10
*** SpamapS has quit IRC16:10
kmartinzhiyan: ok then it would need fibre channel as well, I was reading line #84 of the etherpad16:10
zhiyanso i list somethings we need to have: 1-5 at blow part in https://etherpad.openstack.org/linked-template-image16:10
DuncanTThe same attach would be done for a new 'cinder-ioworker' service in the case of backup, migration etc, which can be run on nodes with appropriate connectivity (including on compute nodes if desired)16:10
*** SpamapS has joined #openstack-meeting16:11
zhiyankmartin: yes, John tell me iscsi, AOE will be extracted, but not others...16:11
winston-dzhiyan: glance can already use block storage as back-end, Ceph is an good example.16:12
DuncanTI think brick on its own is not enough for this.... it will provide some useful parts but we need something more if we are going to do generic attach properly16:12
avishayDuncanT: agreed16:12
zhiyanwiston-d: yes, glance have Ceph store driver, but my plan is give a Cinder store driver to glance, then glance can use any type volume as an image from Cinder backend...16:13
*** jogo_ has joined #openstack-meeting16:13
*** jogo_ is now known as jog016:13
zhiyanDuncanT: yes +116:13
avishayDuncanT: if a deployer doesn't need to worry about connectivity from non-compute nodes, that's a win in my book16:13
zhiyanavishay: yes :)16:14
DuncanTavishay: In my model, the deployer has to run cinder-ioworker on some node(s) with connectivity. This need not be the same nodes that cinder-volume runs on, and can be a compute node if that works outt well with performance and connectivity constraints, or could be a dedicated node16:15
winston-dzhiyan: what you suggesting in this bp: https://blueprints.launchpad.net/glance/+spec/glance-cinder-driver is to use volumes created by Cinder as Glance back-end?16:15
jdurginI think the abstraction just needs to change slightly to focus on I/O rather than attach/detach - those are implementation details16:15
avishayDuncanT: yup, sounds good16:15
DuncanTjdurgin: Looks like they plan on mounting the volume then throwing a cow layer over the mounted volume...16:16
zhiyanDuncanT: what's the different about 'cinder-ioworker' and 'cinder-agent'?16:16
jdurginthen backends like sheepdog and rbd can be supported (and as DuncanT mentioned, having a general I/O mechanism is useful for several other things as well)16:16
*** markwash has joined #openstack-meeting16:17
avishayWho's signing up to do this?  Does it replace this: https://blueprints.launchpad.net/cinder/+spec/cinder-refactor-attach  ?16:17
winston-dzhiyan: cinder-ioworker is a dedicated machine has enough connectivity to various cinder back-ends.16:17
zhiyanwinston-d:for now, i just try to get agreement with cinder team....IMO, as i said in the etherpad, "extract attach/detach code from nova directly but NOT waiting cinder project do that, I will extract attach/detach code independently just for cinder-store-driver for glance project, an later (after i landing down the driver for glance) if cinder like it, I'd like also contribute it to cinder."  what's your thoughts?16:17
DuncanTzhiyan: ioworker is a cinder service that offloads long io jobs from the volume service16:17
* markwash showed up16:18
bswartzavishay: vish and jgriffith gave that talk jointly at the summit16:18
DuncanTzhiyan: cinder agent is moving attach/dettach code out of nova into some new cinder service or libbrary16:18
zhiyanDuncanT: jdurgin: for now, i just plan that cover base/template image preparing, future to cover cow...16:18
winston-dmarkwash: does zhiyan's bp target havana?16:18
*** jhenner has joined #openstack-meeting16:19
DuncanTzhiyan: If it only works for some cinder backends, I'm like to come along downvoting it... that sort of feature split is very harmful16:19
markwashwinston-d: glance-cinder-driver? yes16:19
winston-dzhiyan: how about your bp for nova?16:19
DuncanTzhiyan: Unless you have some fallback mechanism so that it goes back to the old way transparently I guess...16:19
*** rushiagr has joined #openstack-meeting16:20
*** danwent has quit IRC16:20
*** rostam has quit IRC16:20
avishaybswartz: this is going beyond 'brick', right?16:20
markwashsorry I am late :-( has there been discussion of cinder supporting attaching volumes to glance api nodes?16:20
*** hemnafk is now known as hemna16:20
rushiagrHi all sorry i m late16:20
DuncanTmarkwash: That's what we're discussing now16:20
hemnamorning16:20
bswartzavishay: yes I think so -- vish wanted to ultimately eliminate all the storage code from nova16:21
zhiyanmarkwash: yes, we are discussing...16:21
avishaybswartz: yes, i agree that this is working towards that goal16:21
markwashDuncanT: I admit I don't understand all the implications of attaching volumes to glance nodes, but I'm a bit scared of that approach. Do other folks here have alternative proposals?16:21
DuncanTavishay: cinder agent is going way beyond brick, yes, though it will use lots of brick code I expect16:21
markwashor am I just being chicken little?16:22
DuncanTmarkwash: The volume only gets attached to the compute node I think, not the glance node16:22
winston-dhemna: morning16:22
DuncanTmarkwash: Unless I'm failing to understand the design16:22
hemnaavishay, I was going to do the refactor stuff into brick16:22
markwashDuncanT: there is some provision for reading the volume data directly from the glance http api, for backwards compatibility16:22
avishayhemna: OK so you move stuff to brick which gets used by cinder-agent?16:23
winston-dmarkwash: so glance does have to attach the volume to write data?16:23
DuncanTmarkwash: Ah, that causes some issue for e.g. fibrechannel installations...16:23
hemnaI'm not familiar with the term cinder-agent, but the idea was to eventually remove the attach/detach code from nova16:23
zhiyanwinston-d: yes16:23
hemnaand only use the code that I'll put into brick16:23
markwashwinston-d: under the given plan, yes. . but as I said I'm hesitant16:24
*** rostam has joined #openstack-meeting16:24
DuncanThemna: cinder-agent was the name put on an early suggestion for doing code removal16:24
hemnabut for starters, just write the code in brick, get it working in cinder16:24
hemnathen remove the code from nova16:24
hemnaDuncanT, ok.16:24
*** egallen has joined #openstack-meeting16:25
hemnaI have a 3par driver feature to get in, then I'll start working on the attach/detach code16:25
*** pschaef has joined #openstack-meeting16:26
avishayhemna: Who cares about 3par? ;)16:26
hemna:P16:26
winston-dlol16:26
zhiyanhamna: yes. but folks, for this 'common' attching/detaching part, seems the options are all under discussing right?16:26
*** SergeyLukjanov has quit IRC16:26
avishayIs there some concrete plan for this transistion?  brick, agent, etc.?16:26
hemnaavishay, my discussions with john were basically16:27
hemnaput the first pass into brick16:27
hemnaget that working in cinder16:27
hemnathen get brick into oslo16:27
zhiyanhemna: just iscsi +AOE?16:27
hemnaand then use brick in nova16:27
zhiyaninclude others?16:27
DuncanTzhiyan: One option being discussed for things like backup, migration etc is to add a driver API that does reads & writes via the driver, rather than requiring an attach16:27
hemnazhiyan, this originated from the idea of getting FC attach/detach working, so the plan was to do iSCSI and FC at least16:27
zhiyanok....if that can I just port attach/detach code to glance from nova?16:28
markwashDuncanT: I really like that idea, then glance can just proxy calls out to that reader16:28
hemnaDuncanT, another option discussed was to create a utility VM and make the VM do the work...but that feels heavy16:28
zhiyandirectly?16:28
avishayDuncanT: what do you mean by "read & write via the driver"?16:28
thingeeI'm not sure I understand why somethings are in brick and somethings are in cinder agent. seems like it'll confuse new comers. If cinder agent is to take stuff away with volume manager, it should just have implementation in brick16:28
guitarzanhave the backend do the operation itself when applicable16:28
avishayDuncanT: for LVM/ceph/etc?16:29
hemnazhiyan, once brick is in oslo, you should just be able to use the brick attach/detach code16:29
zhiyanhemna: H-2?16:29
jdurginavishay: have some kind of open/read/write/close api, where open/close means attach/detach for lvm, but use other methods for e.g. ceph and sheepdog16:29
DuncanTavishay: Yeah. Many/most drivers will probably just do an attach and read/write, but if they want to do it over http or soem other voodoo then they are welcome to16:29
zhiyanhemna: I just want to implement somthing for H-2, such as glance-cinder-driver...16:29
hemnayah, I'll be shooting for H2, but most likely longer :(16:29
zhiyan:(16:29
winston-dzhiyan: but to make FC work, having common code is not enough, you have to have hardware (HBAs) installed on glance node16:29
DuncanTjdurgin is the mastermind for such designs16:30
avishayjdurgin: sounds good16:30
avishayDuncanT: OK16:30
hemnawinston-d, correct, you have to have FC HBAs on the node16:30
*** jmh_ has quit IRC16:30
markwashwinston-d: it sounds like adding that kind of hardware requirement for glance nodes will not work out well16:30
zhiyanwinston-d: yes, i c16:30
*** sandywalsh has quit IRC16:31
DuncanTOr else have a driver that checks if there is an HBA and if not does an http stream or something to a node that does...16:31
hemnav216:31
hemna:P16:31
*** ssshi has joined #openstack-meeting16:31
winston-dmarkwash: exactly, that's why i fail to see the value of zhiyan's BP16:31
hemnawinston-d, well cinder itself has the same problem right now16:31
hemnait requires a homogeneous deployment16:32
winston-dhemna: that's why we come up with ioworker node idea, right?16:32
hemnabut I'm not sure why someone would deploy half their OS deployment with FC and half w/o16:32
avishayI suggest that someone (hemna?) do a first pass of some high level design of this whole deal on some wiki/etherpad and everyone can bring up objections/refinements?16:32
DuncanTI'm all for volunteering Hemna ;-)16:33
hemnaavishay, didn't we do that in the design session?16:33
vincent_houjdurgin: Does this resemble what is in your mind? https://review.openstack.org/#/c/28931/16:33
avishayhemna: I don't know, I had to miss that one :P16:33
avishayhemna: the etherpad for that is pretty bare16:33
*** jog0 has quit IRC16:34
hemnayah I guess no one took notes16:34
DuncanTThe ioworker stuff got discussed, I think the glace wrinkle is new16:34
jdurginvincent_hou: almost, I'll leave some comments16:34
hemnaDuncanT, yah16:34
bswartzavishay: this one? https://etherpad.openstack.org/havana-cinder-local-storage-library16:34
hemnado we have an ioworker BP ?16:34
winston-dhemna: i can't find that one16:35
avishaybswartz: i thought this one?  https://etherpad.openstack.org/Cinder-Havana-Refactor-Attach-Code16:35
bswartzavishay: that's the one for brick16:35
hemnabswartz, I think that was vishy's etherpad for the long term plans of moving all storage related work to cinder16:35
zhiyanhemna: for now, i'm just now sure, i should waiting your changes or extract attach/detach code from nova to glance directly 16:35
zhiyansince you said that need H-2...16:36
hemnaI have H2 as the target.   We'll see if I get there.16:36
hemnaI also have the state mgmt stuff on my plate as well16:36
hemnaI need a clone of myself.16:37
avishayAnyway, again, I think it would be good to have a concrete design in hand that works for all protocols/back-ends/use-cases before someone runs off and writes code?16:37
zhiyanso, i don't think i should just waiting 'cinder/brick' and cinder-agent..16:37
winston-dhemna: make it 2 or even more. :)16:37
zhiyan:)16:37
DuncanTzhiyan: Extracting the current code is not enough. You'll need a fallback path for backends that don't expose a device or else you won't be backend agnostic and I'll be along to complain....16:37
*** seanrob has joined #openstack-meeting16:37
DuncanTzhiyan: I'm not sure how you can do fallback16:38
hemnaDuncanT, fwiw, we don't really have a fallback mechanism in place now.16:38
winston-dDuncanT: i agree.16:38
DuncanThemna: Yeah, need to fix that too ;-)16:38
hemnathe assumption is a homogeneous deployment on nova nodes now.16:38
hemnayes, we do...but not for H216:38
zhiyanDuncanT: yes, so i talked that with you, maybe i need a new api to drive the state machine properly for volume and snapshot.16:38
*** liuxpei has quit IRC16:39
DuncanTzhiyan: Yeah, that bit should be easy enough to do... just copy the attach API and change instance to host and add a reason field16:39
zhiyanDuncanT: yes, maybe need a new api...16:40
zhiyanbut not change 'attach' api directly...16:40
DuncanTzhiyan: Yes, a new API16:40
hemnastate mgmt is another topic...and it's being worked on now16:40
zhiyanand that new api can be used in future requirement....it's general.16:41
zhiyanhemna: on going?? who do that16:41
DuncanTzhiyan: Want to try to code up that API for review and then we can talk about the actual IO again next week when people have had time to think on it?16:41
DuncanTLooks like we're spinning our wheels a bit now16:41
*** seanrob has quit IRC16:42
zhiyanDuncanT, ok, i like it, but folks, i don't think is the key....16:43
zhiyanthe key is all about actual IO16:43
winston-dzhiyan: the key is even if you can extract attach code from nova to glance, it's not good enough and i think you better wait.16:43
*** sandywalsh has joined #openstack-meeting16:43
DuncanTzhiyan: Yes, but people need time to think about that, so we can bring it up again next week after people have had time to discuss it among themselves for a few days16:43
zhiyanfor now, it seems the concrete design just is what hemna did16:44
zhiyanextract code to 'cinder/brick'16:44
*** rushiagr has quit IRC16:44
zhiyanothers are all on going...16:44
hemnawe extracted the nova attach/detach code from nova for grizzly, but I'm sure it's already behind in bug fixes16:44
DuncanTbrick is not generic attach16:44
*** rushiagr has joined #openstack-meeting16:44
DuncanTbrick is a bunch of useful code for doing some driver stuff16:44
hemnawell hopefully the attach/detach code in brick will be used by nova16:45
*** John__ has joined #openstack-meeting16:45
thingeeDuncanT: maybe we should work on that then with brick :)16:45
hemnaso we don't have dupe code between the 2 projects and need to bugfix twice16:45
zhiyanDuncanT: thanks. so i'm readly not sure, what's the concrete design about generic attach ? :)16:45
DuncanTzhiyan: There is no concrete design. People will thing about it and discuss it again next week16:46
*** jog0 has joined #openstack-meeting16:46
zhiyanhemna: do you have plan to add attach/detach code to brick?16:46
DuncanTzhiyan: Lots of people have thoughts / concerns, we aren't going to get a conclusion now16:46
hemnazhiyan, I thought I touched on that already?16:46
zhiyanDuncant: yes, i totally understand. thanks.16:47
hemnaok lets move on16:47
*** vkmc has quit IRC16:47
zhiyanbut i just want to do some thing to get my bp move forward...16:47
DuncanT#topic Rate limiting, types and the database16:47
*** openstack changes topic to "Rate limiting, types and the database (Meeting topic: cinder)"16:47
avishayIf everyone goes off and thinks about a design we will either have 20 designs, or more likely be in the same place we are now16:47
*** kirankv has joined #openstack-meeting16:48
DuncanTavishay: We can take it to #cinder later16:48
hemnaDuncanT, +116:48
DuncanTSo we've a review open for rate limiting16:48
*** rushiagr has quit IRC16:48
avishayLet one person make a design, email to the list, everyone can raise objections, and we can discuss next week productively?16:48
vincent_houavishay: +116:49
hemnaavishay, I'll try and throw something together at a high level.   I don't think it has to be complicated IMO16:49
avishayhemna: thanks16:49
zhiyanavishay: +1, i'd like to take 'new api' part, to drive the state machine properly.16:49
*** ayurchen has joined #openstack-meeting16:50
DuncanT#action hemna to rough draft a design for host direct I/O / direct attach for discussion16:50
avishayOK, somebody do it, email it, and we'll discuss.16:50
avishayMoving on16:50
DuncanTSo there were some concerns about adding rate limiting stuff directly to the volume-types table in the database16:50
DuncanTThis grew into a few discussions about what our API goals are now that volume types are getting somewhat overloaded16:51
DuncanTI threw my thoughts onto an etherpad at https://etherpad.openstack.org/cinder-volume-types-evolution but haven't had much feedback16:52
DuncanTI believe winston-d has a plan to rework the patch vaguely along these lines to see how it looks?16:52
guitarzanDuncanT: those other entities better by identified by uuids instead of names :)16:52
*** cbananth has joined #openstack-meeting16:52
DuncanTguitarzan: I hate UUIDs but you're probably right16:52
guitarzanwell, no I'm just as wrong about it as we are volume types :)16:53
winston-dyes, i'll rework the patch and submit soon.16:53
DuncanTguitarzan: Unique names work fine in my opinion and have the huge advantage of being readable, but if somebody really wants UUIDs I'm not going to push hard against it16:53
*** SergeyLukjanov has joined #openstack-meeting16:53
DuncanTAnybody see any serious holes in the design?16:54
guitarzanDuncanT: I think the same about vtype names :)16:54
guitarzanit seems a little odd to have those specific classes16:54
guitarzanit will work obviously16:54
DuncanTqos and encyption you mean?16:54
guitarzanyes16:54
guitarzanis there a line to be drawn somewhere?16:54
guitarzanor does every distinguishing feature become an entity?16:54
winston-danything else besides qos and encryption?16:55
hemnaso the plan is to dump more core features into volume types?16:55
DuncanTI think we might end up with more classes over time... pushing them all under one abstraction is just going to lead to weird multiplexing. Only the admin sees the features, the external user still jsut sees volume types16:55
*** terry7 has joined #openstack-meeting16:55
*** sdake_ has quit IRC16:56
*** sdake_ has joined #openstack-meeting16:56
*** sdake_ has quit IRC16:56
*** sdake_ has joined #openstack-meeting16:56
DuncanThemna: I think volume types are our principle abstraction for differentiating volumes... they make a nice abstraction from an external view in my opinion16:56
guitarzanso now the capabilities are tied directly to these new classes?16:56
avishayI guess this helps with the whole "standardizing" effort16:56
*** sdake has quit IRC16:56
hemnahumm16:56
hemnakinda feels like a dumping ground16:56
guitarzanwe killed 40 minutes with one topic16:57
*** jmh_ has joined #openstack-meeting16:57
DuncanThemna I'd rather not see lots of complexity exposed to the 'customer' if possible16:57
avishayguitarzan: "killed" is right :)16:57
hemnaDuncanT, agreed16:57
hemnalol16:57
*** glikson has quit IRC16:58
guitarzanI think the last example, type-create feels weird16:58
winston-danyway, if you are interested in rate-limit, qos, you may want to take a look at this as well: https://etherpad.openstack.org/cinder-extend-volume-types16:58
guitarzanmaybe extra-specs suck, but maybe that's just an interface problem16:58
DuncanTI'd like to maybe see the capability stuff moved to a new class or classes, and volume types just become a bunch of those classes tied together16:58
hartsockshey guys… I have a meeting in this room in a few minutes.16:58
guitarzanhartsocks: we're aware of that16:58
DuncanThartsocks: Ok16:58
hemnawe can move this to #openstack-cinder16:59
avishayDirection seems right but I will have to look at that last etherpad16:59
DuncanTHmmm, since we're just about out of time, can I ask people to look at https://review.openstack.org/#/c/30291/ for testr migration please?16:59
*** ollie1 has left #openstack-meeting16:59
*** skolathu has quit IRC16:59
*** pschaef_t has quit IRC16:59
winston-dsure16:59
*** bswartz has left #openstack-meeting17:00
DuncanTavishay: The details were made up off the top of my head :-)17:00
DuncanTRight, I'm afraid we need to move everything else over to #openstack-cinder17:00
DuncanTThanks folks17:00
*** dosaboy_ is now known as dosaboy17:00
DuncanT#endmeetign17:00
hemnayah we're out of time17:00
winston-dthx DuncanT17:00
avishayDuncanT: some of the best and worst ideas come from that sort of thinking ;)17:00
zhiyanthanks17:00
avishaythanks17:00
DuncanT#endmeeting17:00
*** openstack changes topic to "OpenStack meetings"17:00
openstackMeeting ended Wed May 29 17:00:38 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-05-29-16.00.html17:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-05-29-16.00.txt17:00
openstackLog:            http://eavesdrop.openstack.org/meetings/cinder/2013/cinder.2013-05-29-16.00.log.html17:00
*** avishay has left #openstack-meeting17:00
*** jungleboyj has left #openstack-meeting17:01
hartsocks#startmeeting17:01
openstackhartsocks: Error: A meeting name is required, e.g., '#startmeeting Marketing Committee'17:01
*** pschaef has left #openstack-meeting17:01
hartsocks#startmeeting VMwareAPI17:01
openstackMeeting started Wed May 29 17:01:19 2013 UTC.  The chair is hartsocks. Information about MeetBot at http://wiki.debian.org/MeetBot.17:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:01
*** openstack changes topic to " (Meeting topic: VMwareAPI)"17:01
openstackThe meeting name has been set to 'vmwareapi'17:01
hartsocks#topic salutations17:01
*** openstack changes topic to "salutations (Meeting topic: VMwareAPI)"17:01
hartsocksGreetings! Who is around to talk about VMwareAPI?17:01
*** winston-d has left #openstack-meeting17:01
*** mkerrin has left #openstack-meeting17:01
*** dnoll has left #openstack-meeting17:02
ssshihi17:02
hartsocksheh.17:02
hartsockshi17:02
hartsocksI know Dan W. is traveling. Do we have anyone from HP here?17:02
kirankvHi17:02
*** Yatin has joined #openstack-meeting17:03
*** IlyaE has quit IRC17:03
*** colinmcnamara has quit IRC17:04
*** thingee has left #openstack-meeting17:04
hartsocksthat everyone?17:04
hartsocks(this will be a short meeting then… kinda feel bad for kicking #cinder out now)17:05
ssshiI'm just here to see you guys talking about the progress...17:05
*** reed has joined #openstack-meeting17:06
*** Eustace has joined #openstack-meeting17:06
hartsocksokay...17:06
hartsocks#topic Blueprint followups17:06
*** openstack changes topic to "Blueprint followups (Meeting topic: VMwareAPI)"17:06
hartsocks#link https://blueprints.launchpad.net/nova/+spec/multiple-clusters-managed-by-one-service17:06
hartsocksand17:06
hartsocks#link https://blueprints.launchpad.net/nova/+spec/accurate-capacity-of-clusters-for-scheduler17:06
*** Sabari_ has joined #openstack-meeting17:07
hartsockskirankv: how is the copyright issue coming?17:07
*** lcheng has joined #openstack-meeting17:07
EustaceCopyright issue is still with Legal17:07
kirankvwell the concerned team is looking into it17:07
hartsocksAny idea how long it might be? Will this cause problems hitting H-2 with these?17:08
*** John__ has quit IRC17:08
kirankvwe will be posting the patches and hopefully we should have it sorted by that time frame17:08
*** vincent_hou has quit IRC17:08
hartsocksplease be sure to allow enough time for back-and-forth on the reviews. Lots of people will be looking at these.17:09
kirankvyes, this week we should be able to post a patch set with most of the review comments addressed17:10
kirankvThe other reviews that have got multiple +1s are still not getting approved as well17:10
*** colinmcnamara has joined #openstack-meeting17:10
kirankvhow do we take them forward17:10
hartsocksFor the record, can you post links for the chat log?17:11
*** psedlak has joined #openstack-meeting17:11
hartsocksWe need to get russellb to give his +2 to some of these.17:11
hartsocksI noticed a comment from russellb related to:17:12
kirankvhttps://review.openstack.org/#/c/29396/17:12
hartsocks#link https://blueprints.launchpad.net/nova?searchtext=vmware17:12
kirankvhttps://review.openstack.org/#/c/29552/17:12
kirankv#link https://review.openstack.org/#/c/29552/17:12
*** Yatin has quit IRC17:12
hartsockswhere he mentioned that 4 of our blueprints are assigned to the same person...17:12
hartsocksI presume that in fact the whole team is working on these?17:13
*** ilyashakhat_ has quit IRC17:13
russellbhartsocks: none are proposed for havana right now ... i kicked them back for whatever reason, once they're ready for me to review again, re-propose17:13
russellbthey need to be assigned to whoever is doing the work, have a milestone target set, and then proposed for the havana series17:13
kirankvthe cluster and resource pool related blueprints are part of the patchset that is now marked work in progress17:13
hartsocksHmm… locks like I can't fiddle with these very much.17:14
hartsocksso… let's list what we need to do to these...17:15
*** SergeyLukjanov has quit IRC17:15
kirankvwell they all are stuck due to the copyright concern17:15
hartsocks1) assign to the person doing the work...17:15
hartsocks2) yep… address that copyright concern...17:16
*** BobBallAway has quit IRC17:16
hartsocks3) assign a milestone target of H-217:16
hartsocksI can't do these steps since I'm not on the blueprint. Who can?17:16
hartsocksAre we really completely stuck until that copyright comes off?17:17
*** enikanorov-w has quit IRC17:18
russellbthe assignee can update them17:18
russellbor you can ping me17:18
*** enikanorov-w has joined #openstack-meeting17:18
*** ayurchen has quit IRC17:18
russellband yes, the copyright statement is completely useless AFAIK, and with no indication from the submitters of what purpose it was supposed to serve, i'm not accepting it ...17:18
russellbnobody else does it17:18
*** Divakar has joined #openstack-meeting17:19
russellbour LegalFAQ now says don't do it17:19
kirankvFor esx-resource-pools-as-compute-nodes and Multiple VMware vCenter Clusters managed using single compute service, we are positive to make it to H2 since the patch set has been reviewed and we are in the process of addressing all review inputs17:19
*** ogelbukh1 has quit IRC17:19
russellbhartsocks: you could submit your own blueprint, worded your own way, and then get the patch(es) updated to reference that blueprint17:20
russellband then we just close the problematic ones as superseded17:20
hartsockskirankv: how would you feel about this? Do you think that will cause any problems?17:21
russellbit's kind of a silly thing to have the code have to block on17:21
russellbso i'd recommend that so we can move on17:21
EustaceThe copyright is meant to indicate that the bp is submitted by an HP employee17:22
*** beagles has quit IRC17:22
kirankvhartsocks: I can get back to you on this by tomorrow17:22
EustaceIs the Legal Wiki indicative of the legal stand of Openstack Foundation17:22
*** beagles has joined #openstack-meeting17:22
hartsockskirankv: okay. If I don't hear from you by this time tomorrow, I'll just do as russellb indicates and we can move forward that way.17:23
*** murkk has joined #openstack-meeting17:23
russellbthe LegalIssuesFAQ addresses that last question ... https://wiki.openstack.org/wiki/LegalIssuesFAQ17:23
russellb(is it an official opinion)17:23
russellbno, it is not17:23
hartsockskirankv: it is just paperwork… but I understand some companies might track these things on some people's performance reviews.17:23
hartsocksOkay, so we have an action plan there and we can finally unblock these two Havana-2 milestone blueprints.17:24
EustaceThen what is the Legal stand17:24
russellbhartsocks: hopefully based on the code, not blueprint paperwork17:24
*** boris-42 has quit IRC17:24
kirankvwell it not performance reviews in our case17:24
russellbwho files blueprint paperwork isn't terribly meaningful17:24
hartsocksrussellb: I try not to presume. You never know.17:24
russellbi'm not presuming anything, i'm just stating my opinion on the usefulness of such a thing :-)17:25
hartsocks*lol*17:25
hartsocksOkay, then we're agreed, this whole copyright business can get cleared up quickly and isn't of any consequence?17:25
*** shri1 has joined #openstack-meeting17:25
*** jgallard has quit IRC17:25
*** shri1 has left #openstack-meeting17:26
russellbit *can* be, will it be?  not in my hands17:26
*** Mandell has joined #openstack-meeting17:26
russellbhopefully i've at least made my stance clear17:26
EustaceIf the copyright is not the Legal stahd of the openstack foundation then there is no reason to block checkins17:26
ssshihttps://blueprints.launchpad.net/glance/+spec/hypervisor-templates-as-glance-images , this bp was also targeted at havana-2, should we add something in nova to support its validation?17:27
*** derekh has quit IRC17:27
*** seanrob has joined #openstack-meeting17:27
russellbwe don't need official legal opinion on every little thing, this was consensus on the legal discussion mailing list17:27
*** MarkAtwood has joined #openstack-meeting17:28
russellband as the PTL, it's my domain to set the rules on what can and can not go in17:28
kirankvssshi: yes some changes are required in the nova driver17:28
hartsocks#link https://blueprints.launchpad.net/glance/+spec/hypervisor-templates-as-glance-images17:28
russellbanyway, *moves on*17:28
EustaceI'm sure I can update this Wiki and get this point removed... So then there is no validity of the copyright issue17:28
EustaceThe checkins should be thne allowed against the original BP17:28
ssshikirankv: and any bp on the nova side for this glance bp?17:29
*** seanrob has quit IRC17:29
hartsocksEustace: can we also distribute the blueprint's assignee's between your team members actually doing the work?17:29
*** otherwiseguy has quit IRC17:29
EustaceKiran is doing all the work...17:29
*** seanrob has joined #openstack-meeting17:29
hartsocksYou have one developer?17:30
EustaceHe is very productive :)17:30
kirankvssshi: https://blueprints.launchpad.net/nova/+spec/deploy-vcenter-templates-from-vmware-nova-driver17:30
kirankvhartsocks: its assigned to the person working on it :)17:30
Eustaceyes17:30
Eustaceand we can get all the patches in for H217:30
kirankvthe other patches are smaller and they all depend on the patch for multi cluster support using single service17:31
kirankvthats the reasonw e are holding them up17:31
hartsocksWell, we've targeted 2 of the blueprints for H2. Based on how well that went, you have 2 more… and a glance patch...17:31
*** Tross has joined #openstack-meeting17:32
hartsocks… and it sounds like ssshi has identified a 3rd nova bp that needs to be written...17:32
kirankvwe've worked around the glance part, so changes would not be needed on the glance driver, doc updates only17:33
russellbEustace: the fact that you can vandalize the wiki to remove a point that was the result of a discussion on a mailing list is the worst argument i've heard.  you're killing me.17:33
hartsocks?17:33
hartsocks… reads through backlog ...17:34
*** tanisdl has quit IRC17:34
*** sdake_ has quit IRC17:34
*** seanrob has quit IRC17:34
*** gyee has joined #openstack-meeting17:35
*** sdake has joined #openstack-meeting17:35
kirankvhartsocks: the nova changes required and asked by ssshi are addressed by #link https://blueprints.launchpad.net/nova/+spec/deploy-vcenter-templates-from-vmware-nova-driver17:35
russellbhartsocks: sorry, was looking elsewhere for a bit, didn't mean to interrupt, *shuts up now*17:35
EustaceThe only point that I'm trying to make here is that this is not a Legal stand. Blocking a BP just because of a copyright is not right. I never meant to actually modify the Wiki :)17:35
russellbEustace: but it's *my* stance17:36
russellband I get to decide the rules for nova :-)17:36
russellband my stance is based on consensus17:36
hartsockskirankv: what's the target on this?17:36
kirankvWhat we have seen is that we need to do quite soe refactoring to our UTs similar to how it is done for KVM libvirt driver, to write UTs quickly, right now it takes quite some effort to get the UTs done17:37
hartsockscan we get an in-progress patch for review so the community can participate?17:37
kirankvA week after the the multi cluster checin goes through we will have the patches updated for the other bps17:37
hartsocks So...17:38
hartsocksH-3 target?17:38
*** johnthetubaguy has quit IRC17:38
hartsocksCan you put that in the BP?17:38
*** sushils has quit IRC17:38
kirankvwell i can post them as work in progress once ive finished update the new patch set for the existing two bps this week17:39
ssshikirankv: what does UT stand for?17:39
hartsocksDo you know what "Milestone target" is for?17:39
kirankvok, will mark them for H317:39
hartsocksThank you.17:39
kirankvUnit Tests17:39
DivakarUT = Unit Test17:39
hartsocksPlease remove those Copyright lines.17:39
ssshigot that. thanks.17:40
hartsocksIf they are not gone this week I will simply create new blueprints that russellb will approve… we can work from there. This will allow me to perform the project management and milestone target setting as well.17:41
russellbhartsocks: sounds good, thanks17:41
hartsocksAny more on blueprints before we move on?17:41
*** sdake has quit IRC17:41
*** zhiyan has left #openstack-meeting17:41
hartsocksOkay.17:42
yaguangI have create a blueprint https://blueprints.launchpad.net/nova/+spec/improve-vmware-disk-usage17:42
*** sdake has joined #openstack-meeting17:42
*** sdake has quit IRC17:42
*** sdake has joined #openstack-meeting17:42
hartsockshmm… I'm not sure I understand this blueprint...17:43
yaguangthis to support  ephemeral   disk for instance17:44
kirankvyaguang: do you want to make it par with libvirt behaviour?17:44
*** Tross has quit IRC17:44
yaguangyes17:44
yaguangdoes it make sense ?17:44
kirankvso you plan to add the difference between the image size and the flavor as as second disk?17:45
yaguangyes17:45
yaguangvm root size should be based on flavor17:46
yaguangand has nothing with  the image size17:46
DivakarYou can extend the size of the existing disk as well17:46
hartsocksHmm… let's take this into #openstack-vmware for design discussion. This could go a number of different ways.17:47
ssshiI'm wondering how to specify the root/ephemeral size if we were to deploy from vcenter templates.17:47
*** jamespage has quit IRC17:47
*** Divakar has quit IRC17:48
hartsocksWhatever you discuss, put it in the blueprint so the discussion doesn't end up locked in IRC but makes it back to the rest of the community.17:48
yaguangok17:48
hartsocksI'll put a note to follow up on this next week.17:49
hartsocks#action follow up on https://blueprints.launchpad.net/nova/+spec/improve-vmware-disk-usage17:49
kirankvyaguang: which milestone are you targeting this bp for?17:49
hartsockshey… over on #openstack-vmware with you! :-) target would be based on size-of-work which is based on design...17:50
*** egallen has quit IRC17:50
yaguangH217:50
yaguangyes, so it's early to set the milestone right now17:50
yaguangwe may need more discussion  for this17:51
hartsocksyep. H2 might be realistic, but it probably isn't.17:51
hartsocksI'm really glad the blueprint discussion has gotten lively (and messy) that's a good sign.17:52
hartsocksLet's keep up the good work here and try and conform to what the Nova community needs from us. They have rules we need to follow. Let's try and follow them unless we have a solid reason to argue for different.17:53
hartsocksWe're running short on time.17:53
hartsocksI'll ask that you use the #openstack-vmware channel to discuss issues in IRC when you need to, but remember to document changes in the BP. If anyone needs help writing things up my English is pretty good. I can help out if you need it.17:54
hartsocksI do want to switch to a quick bug discussion.17:55
hartsocks#topic high priority bugs17:55
*** openstack changes topic to "high priority bugs (Meeting topic: VMwareAPI)"17:55
hartsocksIs there anything *not* assigned that is blocking users, customers, etc? that is not being addressed?17:55
*** eharney has quit IRC17:56
*** Tross has joined #openstack-meeting17:56
*** eharney has joined #openstack-meeting17:57
*** eharney has quit IRC17:57
*** eharney has joined #openstack-meeting17:57
hartsocks#link https://bugs.launchpad.net/nova/+bug/118004417:57
uvirtbotLaunchpad bug 1180044 in nova "nova boot fails when any VMware vCenter managed datacenter or container object is empty" [High,Confirmed]17:57
hartsocksI am working on this next. Has anyone else observed this issue? It turns out this may be peculiar to a sub-set of users.17:58
hartsocks#link https://bugs.launchpad.net/nova/+bug/118319217:58
uvirtbotLaunchpad bug 1183192 in nova "VMware VC Driver does not honor hw_vif_model from glance" [Critical,In progress]17:58
yaguangI am working on this17:59
hartsocksLooks like you need some reviews.17:59
hartsocksOkay. I guess we're out of time.18:00
hartsocks#openstack-vmware is open for people who still need to talk.18:00
hartsocks… feel free to use that or set up meeting times in there. We can report them back to the official meeting later.18:00
hartsocksSee you next week. Same time, same channel.18:00
hartsocks#endmeeting18:01
*** openstack changes topic to "OpenStack meetings"18:01
openstackMeeting ended Wed May 29 18:01:00 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-05-29-17.01.html18:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-05-29-17.01.txt18:01
openstackLog:            http://eavesdrop.openstack.org/meetings/vmwareapi/2013/vmwareapi.2013-05-29-17.01.log.html18:01
*** jcoufal has quit IRC18:01
*** psedlak has quit IRC18:02
*** tanisdl has joined #openstack-meeting18:03
*** eharney has quit IRC18:03
*** Sabari_ has quit IRC18:05
*** jdurgin1 has joined #openstack-meeting18:11
*** ssshi has quit IRC18:12
*** otherwiseguy has joined #openstack-meeting18:14
*** yaguang has quit IRC18:14
*** kirankv has left #openstack-meeting18:16
*** eharney has joined #openstack-meeting18:16
*** eharney has quit IRC18:16
*** eharney has joined #openstack-meeting18:16
*** SergeyLukjanov has joined #openstack-meeting18:18
*** shri1 has joined #openstack-meeting18:18
*** stevemar has quit IRC18:22
*** stevemar2 has joined #openstack-meeting18:22
*** cp16net is now known as cp16net|away18:22
*** rushiagr has joined #openstack-meeting18:23
*** cbananth has quit IRC18:25
*** sandywalsh has quit IRC18:26
*** glikson has joined #openstack-meeting18:27
*** Mandell has quit IRC18:29
*** markwash has quit IRC18:36
*** Mandell has joined #openstack-meeting18:36
*** markwash_ has joined #openstack-meeting18:36
*** cp16net|away is now known as cp16net18:36
*** danwent has joined #openstack-meeting18:40
*** sandywalsh has joined #openstack-meeting18:42
*** lloydde has quit IRC18:42
*** alexpecoraro has joined #openstack-meeting18:45
*** lloydde has joined #openstack-meeting18:47
*** colinmcnamara has quit IRC18:48
*** xBsd has joined #openstack-meeting18:50
*** novas0x2a|laptop has joined #openstack-meeting18:50
*** rushiagr has quit IRC18:51
*** lloydde has quit IRC18:51
*** grey_ak has joined #openstack-meeting18:53
*** portante has joined #openstack-meeting18:54
*** jamespage has joined #openstack-meeting18:55
*** clayg has joined #openstack-meeting18:56
*** tanisdl has quit IRC18:58
*** cp16net is now known as cp16net|away18:59
*** lpabon has joined #openstack-meeting18:59
notmynameswift meeting time19:00
*** dstanek has joined #openstack-meeting19:00
notmyname1900utc by my clock, let's get started19:00
notmyname#startmeeting swift19:00
openstackMeeting started Wed May 29 19:00:36 2013 UTC.  The chair is notmyname. Information about MeetBot at http://wiki.debian.org/MeetBot.19:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:00
*** openstack changes topic to " (Meeting topic: swift)"19:00
openstackThe meeting name has been set to 'swift'19:00
litong@notmyname, good afternoon19:01
notmynamehellow everyone19:01
notmynamethings to cover today: next swift release, API, summit, and a few other things19:01
lpabonhello19:01
torgomaticahoy19:01
alexpecorarohi19:01
notmynamefirst, a few simple things19:01
shri1hey19:01
portantehelo19:01
portantehello19:01
notmyname#topic housekeeping/misc19:01
*** openstack changes topic to "housekeeping/misc (Meeting topic: swift)"19:01
*** dfg has joined #openstack-meeting19:02
notmynameThe naming for the next OpenStack release (the "I" release) is open for a vote.19:02
notmyname'the poll is at https://launchpad.net/~openstack/+poll/i-release-naming19:02
notmynameon the topic of openstack releases, the next summit is in hing kong19:02
notmynamehong kong19:03
notmynamedates are nov 5-819:03
notmynamehttp://www.openstack.org/summit/openstack-summit-hong-kong-2013/19:03
notmynameand if you are a US citizen, here's your visa info: http://hongkong.usconsulate.gov/acs_hkvisa.html19:03
*** stevebaker is now known as stevebaker_19:03
notmynameif you are planning on attending, make sure your passport is up to date. it can take up to 2 months to get one, so do it now19:04
notmynamea little more specific to swift now, let's talk about the next release of swift19:04
notmyname#topic next swift release19:05
*** openstack changes topic to "next swift release (Meeting topic: swift)"19:05
notmynameI'd like to cut the next release when the final global clusters features land19:05
litong@notmyname, for US citizen , you do not need visa if you stay there less than 90 days.19:05
notmynamelitong: correct19:05
litongbut you do need a valid passport.19:05
notmynamethe proxy affinity is the major one, but I've also got my eye on the cross-region replication19:06
notmynameany comments or questions on when we should do the next release? is that a good plan or should we do something else?19:06
*** cp16net|away is now known as cp16net19:07
notmynameI'll assume either everyone agrees or I've dropped out of IRC again... ;-)19:07
torgomaticI'd like to see https://review.openstack.org/30797 merged before the next release19:07
portanteI'd like to see thread pools make the next release19:08
litong@notmyname, cross-region replication is a good one.19:08
torgomaticor at least, I'd like to see that bug fixed; doesn't have to be my patchset19:08
shri1notmyname: whats the tentative release date for these features to be completed?19:08
*** hartsocks has left #openstack-meeting19:08
notmynametorgomatic: portante: agreed on both19:08
notmynameshri1: there is no date as of yet. it's done when it's done19:08
shri1*if these features have to be completed19:08
shri1I see19:08
notmynameshri1: sooner is better than later19:08
*** stevebaker has joined #openstack-meeting19:09
*** stevebaker is now known as stevebaker__19:09
*** stevebaker__ is now known as stevebaker19:09
litongif anyone can review this one (just need one more +1 to merge), that will be really nice. https://review.openstack.org/#/c/22569/19:09
notmynamebut aside from the 6 month openstack cycle, we aren't doing any sort of time-based releases19:09
portantenotmyname: do you want to keep the DiskFile and DatabaseBroker out of the next release to not delay it?19:09
*** anniec has quit IRC19:10
notmynameso basically, all this comes down to doing reviews19:10
notmyname(what's new?)19:10
portante;)19:10
litong@notmyname, yes, yes, yes. review, please19:10
notmyname#topic reviews19:10
*** openstack changes topic to "reviews (Meeting topic: swift)"19:10
notmynamespeaking of reviews...19:10
notmynamejust a quick note, especially for core reviewers: if someone has already given a +2 and there is a minor issue (eg typo in docs or commit message), it probably shouldn't be given a -1 by another reviewer. that resets the previous +2 and slows everything down19:12
notmynamequick follow-up commits could be a good way to address small issues like that, as long as master remains deployable19:12
notmynamejust something to keep in mind and try to see if we can speed up the review time19:13
notmyname#topic bot in channel19:13
*** openstack changes topic to "bot in channel (Meeting topic: swift)"19:13
* portante ack19:13
*** grey_ak has quit IRC19:14
notmynamelast quick thing: I added the openstackgerrit bot to #openstack-swift. anyone think it should be removed?19:14
*** ryanpetr_ has joined #openstack-meeting19:14
notmynameit reports on new patches and merges19:14
notmynamebut if it gets too annoying, we can easily remove it19:14
* torgomatic likes having the bot there19:14
* portante agrees19:14
*** ogelbukh1 has joined #openstack-meeting19:14
litongI think it is a good thing.19:15
notmynamecool. I like it too. let's keep it until it gets to be a problem19:15
notmynameogelbukh1: glad to see you. I'm interested in the mirantis patches wrt global clusters, but they are all marker WIP19:16
notmynameogelbukh1: basically, I want the functionality to be in the next release19:16
notmynameand I doubt many people have looked at them since they are marked WIP19:16
*** ryanpetrello has quit IRC19:16
dosaboyis there a bp/wiki entry for the global clusters work?19:17
notmynamedosaboy: https://blueprints.launchpad.net/swift/+spec/multi-region19:18
dosaboynotmyname: cool thanks19:18
notmynameportante: ready to talk about DiskFile?19:18
portantesure19:18
notmyname#topic DiskFile refactor19:18
*** openstack changes topic to "DiskFile refactor (Meeting topic: swift)"19:18
notmynameportante: go for it19:18
*** anniec has joined #openstack-meeting19:18
portanteso how many folks have heard about this effort?19:19
notmynameo/19:19
portanteI not that notmyname and torgomatic have looked at?19:19
torgomatico/19:19
notmyname(quiet crowd today)19:19
portanteFrom April's summit, we are working to refactor the DiskFile and DatabaseBroker to define them as "public" classes so that we can have various implementations of those classes19:20
alexpecoraroi've heard of it19:20
portantethe existing implementation would be the first19:20
portanteto date, we've proposed https://review.openstack.org/#/c/30051/19:20
portantewhich is a stab at refactoring just DiskFile to define the APIs19:21
portanteIt still has 18 unit test failures, so it is a work-in-progress for sure19:21
portantebut I am seeing folks to take a look at the changes to see if they make sense and if they are in a direction we want to go in19:21
notmynameaside from the minor comments I left, I like the direction of it19:22
*** lloydde has joined #openstack-meeting19:22
torgomaticI like the way it's going19:22
portantenotmyname has suggested that I pull out the "reader" work, which is sister work to the "writer" work performed in https://review.openstack.org/#/c/27149/19:22
portantethat might make it easier to review19:23
alexpecoraroi haven't yet, but i'm interested in taking a look and will provide any feedback that i can think of19:23
portantealexpecoraro: thanks19:23
*** IlyaE has joined #openstack-meeting19:23
portanteI personally think pulling the "reader" work out would be a good thing, but want to balance too many things to review against too large a change to review19:23
portanteThe next question is how to take this in pieces so that it does not straddle a release and possibly cause problems19:25
portanteI would like each piece to be fully functional, but still, not a fan of half-way for a release19:25
notmynameportante: well, anything that lands should be distinct enough to work itself19:25
torgomaticis it really a problem if it straddles a release? I mean, at each step, Swift is still working19:25
notmynameeg extracting the reader doesn't break anything19:25
*** ayoung has quit IRC19:26
portantetrue enough19:26
portanteif folks are fine with that, then let's work to target the "reader" work pulled out of the next release, and then the full API definition to follow19:26
notmynameI'm ok with that19:26
notmynameanyone else have comments?19:26
*** dprince has quit IRC19:26
portantecertainly I am available for questions afterwards19:27
litongwhen it is in, how one can replace with a different implementation?19:27
*** grey_ak has joined #openstack-meeting19:27
portanteah, em, ah, well, er, so, still working on those mechanics. :)19:28
notmynameheh19:28
notmynameworst-case (ie now), monkey-patching, right?19:28
portanteright19:28
*** wirehead_ has joined #openstack-meeting19:28
litong@portante, I am thinking about LTFS.19:29
portantebest case, defined backends associated with a know string19:29
portanteLFS patch?19:29
portantelitong?19:29
litongright.19:29
litongLinear Tape File System19:29
portanteThe DiskFile and DatabaseBroker refactoring work is going to be a subclass of that19:29
litongvery low cost storage.19:29
portanteah, yes19:29
portanteI see now19:29
litongin thoery, we should be able to do that.19:30
portanteyes19:30
litongswift cluster can be a mixed disk , tape, very fast storage and some what slow storage.19:30
notmynameI've got a couple of uses too (the most obvious is optimizing some XFS-specific things, if possible)19:30
torgomaticI'd like to use it to let me audit for missing objects on non-XFS filesystems19:30
notmynamewell, more quickly audit ;-)19:31
portanteto that end, it would be helpful to get the thread pools work in before this work19:31
torgomaticnotmyname: true; right now, though, it takes until another update invalidates hashes.pkl before anyone notices a missing file19:31
litongso the question is, when this patch is in, will it be every node with same driver or object node can have mixed drivers.19:31
portanteI would like to make sure this refactoring is considered on top of that19:31
torgomaticso let's say "update in bounded time" :)19:31
portanteAlso, regarding the DatabaseBroker side, the work that David Haddas did for the "db_file" exists code, would be useful19:32
notmynamelitong: that will be determined by the yet-to-be-defined inclusion mechanism, I'm usre19:32
notmynameportante: so what you're saying is "do more reviews" ;-)19:33
portanteAlso, zaitcev proposed a patch there as well19:33
portante;)19:33
*** grey_ak has quit IRC19:33
* portante smiles quietly to himself19:33
*** bradjones|away has quit IRC19:33
notmyname#agreed do more reviews19:33
notmyname(now it's official)19:34
portante;)19:34
notmynameok, shall we move on?19:34
portanteI'm good19:34
notmyname#topic swift API19:34
*** openstack changes topic to "swift API (Meeting topic: swift)"19:34
notmynamelast thing to discuss today19:34
notmynamehttps://wiki.openstack.org/wiki/Swift/API19:34
*** adalbas has quit IRC19:34
notmynamethis is a description of what I believe is the subset of functionality that can be defined as "swift" and that we can therefore call swift API v119:35
notmynamebut there are a couple of outstanding questions, and I'm not sure who has actually looked at the page (there certainly haven't been many edits)19:35
litong@notmyname, totally agree with the first 2 items. ACL and Auth.19:36
*** bradjones|away has joined #openstack-meeting19:36
*** psedlak has joined #openstack-meeting19:36
*** IlyaE has quit IRC19:36
litongmulti-range is not supported on large objects19:36
notmynamethe goal is not to restrict functionality but to find the subset of functionality that currently-deployed swift clusters (ie from the swift source code) support19:36
litongwe could have that, if the patch got reviewed. I worked on that for 4 months,19:37
*** Eustace has quit IRC19:37
notmynamelitong: right, I think that distinction was lost in my last edit19:37
portanteSo ACLs is interesting, because the code chose key names stored in the metadata on disk already, right?19:37
litongcan we have that back? I mean the multi-range on large objects.19:37
portanteMost auth filters rely on that format, don't they?19:37
notmynameportante: yes, probably19:38
*** danwent has quit IRC19:38
portantewould it cause a problem to define ACLs as part of the v1 API?19:39
*** jdurgin1 has quit IRC19:39
portanteit is kinda asymetrical, since an auth filter would not be part of the v1 API19:39
litong@portante, once it is in API, it alomst feel like required. some company may want to ACL completely different way.19:40
portantebut this is what it is today, these ACLs are stored on disk that way19:40
litongI mean "do ACL differently."19:40
litong@portante, you do not have to use it.19:41
notmynameI want to have a v2 API that has pretty much all of the functionality in the codebase, but I don't think we should ever deprecate v1. This is to give a baseline of what can be called an implementation of the swift api19:41
litongyou can add your own ACL at the proxy server any way you want.19:41
notmynameportante: since ACL definitions are only meaningful to a particular auth system, it doesn't make sense to me to define an ACL format as part of the swift api (especially a v1 api)19:42
litong@notmyname, not in v1, v2, or any other version.19:42
notmynameperhaps v1 and v2 are bad names. perhaps "basic functionality" and "complete functionality" are better19:42
notmynamelitong: perhaps. I'm not sure I'm willing to go that far yet19:43
litongit conflicts with separation of concerns (design principals)19:43
litongno matter how you define it , someone won't like it19:43
*** hanney has quit IRC19:43
portantewhat are the metadata key names used by the tempauth and other auth system?19:44
*** tanisdl has joined #openstack-meeting19:44
notmynameI'd like to agree that the wiki page is an accurate reflection of what we as a group can call the v1 API19:44
portantedo we have to define a names apced for the v1 API then?19:44
notmynameportante: I'd just leave X-Container-Read and X-Container-Write out of it19:44
*** jdurgin1 has joined #openstack-meeting19:45
notmynamethe other questions I had were around tempurl and large object support19:45
portanteokay19:45
notmynameI like them both. I want to have a definition that says both "here is something that defines swift" but also not so restrictive that existing clusters aren't swift any more19:46
*** danwent has joined #openstack-meeting19:46
notmynameso at this very moment, I'm leaning towards not including them. but I go back and forth19:46
portanteis tempurl purely a filter?19:47
portanteOr does it rely on some code in the app server side?19:47
*** jlucci1 has joined #openstack-meeting19:47
notmynameit is implemented as such, but that is immaterial to its inclusion19:47
portantehmm, messy19:48
notmynameI think it's important to separate the implementation decisions (ie middleware or not) from the functionality19:49
notmynameeg dynamic large objects vs static large objects. one is middleware and the other isn't19:49
torgomaticnotmyname: agreed 100%19:49
*** lloydde_ has joined #openstack-meeting19:49
*** grey_ak has joined #openstack-meeting19:49
portantewell, if I have an implementation that can use the existing tempurl filter, then my implementation could say it supports it19:50
notmynameto me the question is "when someone claims they have a swift cluster, what functionality should my client assume exists as a baseline?"19:50
portanteif I don't, then I have to implement it (like Ceph folks can use filters)19:50
*** markwash has joined #openstack-meeting19:50
*** sandywalsh_ has joined #openstack-meeting19:51
notmynameportante: correct. and in your case, when Red Hat says that gluster supports the Swift API, what does that mean for clients?19:51
*** salv-orlando_ has joined #openstack-meeting19:51
portantetoday, we support all the filters because we reuse most of the code19:51
notmynameas you should!19:51
notmyname;-)19:51
portante;)19:52
*** dcramer_ has joined #openstack-meeting19:52
*** harlowja_ has joined #openstack-meeting19:52
*** clayg_ has joined #openstack-meeting19:52
torgomaticthe way I see it, if a cluster lets me set X-Account-Meta-Temp-Url-Key on my account, and then do some HMAC magic to make a URL like /v1/AUTH_me/con/obj?temp_url_sig=X&temp_url_expires=Y and that url *works*, then that cluster supports Swift signed URLs19:52
torgomaticit's all from the client's perspective19:52
notmynameyes19:52
portanteokay, I'm easily convinced19:52
*** deagle has joined #openstack-meeting19:52
*** vipuls has joined #openstack-meeting19:53
notmynamebut should that be in the swift v1 api? :-)19:53
torgomaticI don't care if the implementation is using swift.common.middleware.tempurl verbatim, hacked up, or if it's got a hand-rolled proxy server written in node.js and befunge in front that handles it ;)19:53
litong@notmyname, if that is really useful to customers, yes it should be in.19:53
litongwe are defining an API after all.19:53
*** IlyaE has joined #openstack-meeting19:53
* torgomatic thinks signed requests *should* be in the Swift v1 API19:53
*** terryg_ has joined #openstack-meeting19:53
notmynameIOW, should any clusters out there that don't support it today no longer be able to be called a swift cluster?19:53
notmynamelitong: usefulness isn't the criteria IMO, since we are only formalizing an API post-facto19:54
*** psedlak_ has joined #openstack-meeting19:54
*** harlowja has quit IRC19:54
*** vipul has quit IRC19:54
*** markwash_ has quit IRC19:54
*** sandywalsh has quit IRC19:54
*** clayg has quit IRC19:54
*** psedlak has quit IRC19:54
*** jlucci has quit IRC19:54
*** bogdando has quit IRC19:54
*** lloydde has quit IRC19:54
*** salv-orlando has quit IRC19:54
*** salv-orlando_ is now known as salv-orlando19:54
*** danwent has quit IRC19:54
notmynameand we're running out of time, so it seems that there isn't a broad consensus19:55
*** terry7 has quit IRC19:55
portantehmmm, its the post-facto thingy that has me wondering here, not the core principle (which I like)19:55
*** cp16net is now known as cp16net|away19:55
*** psedlak_ has quit IRC19:56
notmynameportante: basically, I don't want so write a tester against the v1 spec and have mercado libre, wikimedia, vimeo, rackspace cloud files, or HP fail it :-)19:56
notmynameand all the others19:56
portanteyes19:56
*** shardy has joined #openstack-meeting19:56
portantethat is why I am thinking it should be based on the app server code vs filter code19:56
portantefor post-facto definition19:56
portantenot for the principle or the future19:56
portantedefine v1 based on that, immediately define v2 based on the principle19:57
*** xyang_ has quit IRC19:57
*** jamespage has quit IRC19:57
litongare we starting the API on the wrong foot?19:57
*** zaneb has joined #openstack-meeting19:57
*** jamespage has joined #openstack-meeting19:57
*** jamespage has quit IRC19:57
*** jamespage has joined #openstack-meeting19:57
litongI think stick with the principal is important. we can not change an api in v2 which was just defined in v1.19:57
portantelitong: it is the foot we are on already, I think.19:57
notmynamewe should continue this in the -swift channel19:58
portantewe won't be, if I understandthings, we'll only be adding to the API19:58
portantek19:58
notmynamewe're out of time19:58
*** therve has joined #openstack-meeting19:58
notmyname#agreed to nothing yet19:58
notmynamethanks for your time everyone19:58
notmyname#endmeeting19:58
*** openstack changes topic to "OpenStack meetings"19:58
openstackMeeting ended Wed May 29 19:58:42 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-05-29-19.00.html19:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-05-29-19.00.txt19:58
openstackLog:            http://eavesdrop.openstack.org/meetings/swift/2013/swift.2013-05-29-19.00.log.html19:58
*** portante has left #openstack-meeting19:58
*** alexpecoraro has left #openstack-meeting19:58
*** jasond has joined #openstack-meeting19:59
*** m4dcoder has joined #openstack-meeting20:00
*** TravT has joined #openstack-meeting20:00
*** timductive has joined #openstack-meeting20:00
*** hanney has joined #openstack-meeting20:00
shardy#startmeeting heat20:00
openstackMeeting started Wed May 29 20:00:53 2013 UTC.  The chair is shardy. Information about MeetBot at http://wiki.debian.org/MeetBot.20:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:00
*** openstack changes topic to " (Meeting topic: heat)"20:00
openstackThe meeting name has been set to 'heat'20:00
*** cp16net|away is now known as cp16net20:00
hanneyo/20:01
*** adrian_otto has joined #openstack-meeting20:01
zanebhowdy y'all20:01
adrian_ottohi20:01
jpeelerhere20:01
stevebakermeep20:01
SpamapSo/20:01
therveHi!20:01
*** sdake_ has joined #openstack-meeting20:01
*** sdake_ has quit IRC20:01
*** sdake_ has joined #openstack-meeting20:01
shardyasalkeld around?20:01
sdake_o/20:02
asalkeldhi20:02
radixhello :)20:02
*** shri1 has left #openstack-meeting20:02
m4dcoderO/20:02
*** dcramer_ has quit IRC20:02
shardyhi all :)20:02
shardy#topic Review last week's actions20:02
*** openstack changes topic to "Review last week's actions (Meeting topic: heat)"20:02
wirehead_Heya20:03
kebrayhello20:03
TravThello!20:03
shardy#info shardy PoC HOT patch20:03
shardyso I did this, but I'm now preferring zaneb's followup patch20:03
sdake_i prefer zanes as well20:03
shardy#link https://review.openstack.org/#/c/30405/20:03
shardy#link https://review.openstack.org/#/c/30439/20:04
zanebI added an item to the agenda to discuss this20:04
*** jlucci1 has quit IRC20:04
kebrayfyi, randallburt is out of office today, not feeling well.20:04
shardyOk, does anyone *not* think zaneb's approach is the way to go?20:04
therveThere seems to be a consensus on the new template class20:04
zanebI'd like to see some more input on my mailing list post20:04
shardyI like it but it does mean we're committing to keeping the template translation in the engine20:04
*** dfg has left #openstack-meeting20:05
asalkeldshardy eventually we need to move cfn out20:05
fsargenthiya20:05
stevebakerzaneb: the one on file inclusion?20:05
asalkeldso it is a start20:05
zanebstevebaker: yes20:05
zanebasalkeld: not sure I agree with your post20:06
shardyasalkeld: yeah, or move the CFNisms into a CFNTemplate class20:06
stevebakerzaneb: I prefer some kind of client-side file aggregation to zipping up template files20:06
zanebasalkeld: wouldn't it be better to have the engine mechanics independent of the template format?20:06
stevebakerzaneb: tl:dr +120:06
zanebasalkeld: rather than just tying it to HOT instead of CFN20:06
asalkeldno20:06
zaneblol20:06
asalkeldI think there is still heaps of time to sort it out20:07
asalkeldget this patch in already20:07
shardyzaneb: I really like the idea of decoupling the engine from template details, and just accessing Template class properties20:07
SpamapSi thi k the template format is pretty closely tied to the engi e so this seems fi e20:07
zanebSpamapS: lost your 'n' key?20:08
*** jhenner has quit IRC20:08
sdake_time for new keyboard imo ;)20:08
shardyOk, shall we continue discussions on the ML, and I'll abandon the template-mangle patch?20:08
asalkeldI seriously doubt it is possible for details not leak out20:08
stevebakerSpamapS: broken right thumb?20:08
asalkeld(of the Template class)20:08
asalkeldbut we will see20:08
therveRight that doesn't mean we shouldn't try though20:09
shardyif people have specific issues, pls update https://review.openstack.org/#/c/30439/20:09
*** grey_ak has quit IRC20:09
zanebasalkeld: you may be right. therve: I agree20:09
asalkeldtherve, totally think we need both format's in now20:09
asalkeldjust whether or not we kick cfn out20:10
asalkeld(of the engine)20:10
therveasalkeld, Agreed. We can improve things as they move on20:10
asalkeldat some later point20:10
*** xBsd has quit IRC20:10
zanebasalkeld: vote it off the island :)20:10
therveRight now it's a bit too abstract to figure out all the problems we'll encounter20:10
asalkeldyea20:10
shardyasalkeld: I guess we can decide that later :)20:10
asalkeldfor sure20:10
zanebfwiw...20:11
zanebI think moving from 2 Template classes in engine to cfn translation layer in API is easier than moving from HOT translation layer in API to cfn translation layer in API20:11
shardyzaneb: agree20:12
*** colinmcnamara has joined #openstack-meeting20:12
shardyLets get the "superset model" in the engine, then work out where the template transformations live later20:12
therve+120:12
zaneb+120:12
kebray+120:12
shardy#info action asalkeld wiki/bp re infra heat usage20:13
asalkeld(I +2'd it)20:13
shardyIIRC this happened, asalkeld got a link?20:13
asalkeldmmm20:13
asalkeldI can't even remember this20:13
asalkeldwow getting old20:13
asalkeldO, ok - hold on20:14
shardyIIRC you did it immediately after the meeting20:14
asalkeld(it is 6am)20:14
sdake_use the wiki related links20:14
shardyOk, lets forget the link and move on :)20:14
SpamapSthis was clarkb wanting to use heat for logstash for infra stuff20:14
kebrayhttps://wiki.openstack.org/wiki/Heat/on-public-clouds20:14
kebrayThat one?20:14
zanebI think it was another one20:15
asalkeldthat's it20:15
shardy#topic h1 release status20:15
*** openstack changes topic to "h1 release status (Meeting topic: heat)"20:15
shardyso h1 branched today, nice work everyone :)20:15
shardyfew things bumped to h2 but most of the stuff planned landed20:16
zanebI think we sort-of got parallel-launch in :)20:16
zanebexcept for nested templates20:16
shardyzaneb: yeah, sorry we didn't manage to get the reviews in for the final few20:17
shardynice job anyways :)20:17
zanebnp, was a pretty good effort20:17
zanebso many patches...20:17
*** eharney has quit IRC20:17
therveshardy, Any highlights on other things that got pushed?20:17
* zaneb has fingers crossed for no more rebases20:17
shardytherve: mainly a few quantum related bugfixes which are in-progress20:17
sdake_zaneb rebases more fun then java fedora package reviews :)20:17
zanebsdake_: I'll drink to that20:18
shardygoing to be a busy h2 tho by the looks of it :)20:18
*** mrutkows has joined #openstack-meeting20:18
zanebshardy: 'milestone-proposed' is the branch, I assume?20:18
mrutkowso/  sorry late20:18
shardy#link https://launchpad.net/heat/+milestone/havana-220:18
shardyzaneb: yep, then we have couple of days (until tomorrow IIRC) where backported critical fixes can be proposed20:19
shardybefore the release is made final20:19
*** boris-42 has joined #openstack-meeting20:19
zanebweird system, but ok :)20:19
shardywhich takes us nicely on to:20:19
shardy#topic 2013.1.2 stable release20:20
*** openstack changes topic to "2013.1.2 stable release (Meeting topic: heat)"20:20
shardySo I'm thinking we skip this as we don't have any backported fixes to grizzly/stable20:20
shardyDoes anyone have anything they want to flag as backport-potential?20:20
zaneb+1 for skipping20:20
shardythe main one is the latest-boto v4 signatures thing, but we need keystoneclient release before we can backport that20:21
*** stevebaker is now known as stevebaker__20:21
shardy(as SpamapS pointed out earlier)20:21
*** jog0 has quit IRC20:21
*** stevebaker__ is now known as stevebaker20:22
shardySo if anyone wants to propose stable backports at any point, see this wiki:20:22
shardy#link https://wiki.openstack.org/wiki/StableBranch20:22
shardy#topic heat-core proposed changes20:22
*** openstack changes topic to "heat-core proposed changes (Meeting topic: heat)"20:22
shardySo two things20:22
*** eharney has joined #openstack-meeting20:23
*** eharney has joined #openstack-meeting20:23
shardyfirstly, I'm proposing to remove shadower and Slower from heat-core as they're no longer actively contributing/reviewing20:23
shardyhere are the stats for the last 90 and 30 days:20:23
*** jog0 has joined #openstack-meeting20:23
shardyhttp://fpaste.org/15176/69819561/20:23
shardyany objections?20:23
shardyobviously we can add them again if they start working on Heat in the future20:23
stevebaker+120:24
sdake_so just to clarify20:24
sdake_and I agree they should be removed20:24
zanebinteresting, SpamapS is the harshest reviewer :D20:24
sdake_but what are your criteria for core20:24
SpamapSi didnt even know who they were20:24
sdake_zaneb: I'd thought you have been :)20:24
zanebclose second ;)20:24
shardysdake_: so criteria is (IMHO):20:24
m4dcoderWhat's the requirements to join core?20:25
sdake_SpamapS they did some early work on heat20:25
stevebakercore membership is for reviews more than anything else20:25
shardyActive reviewer, with consistent and well thought out downvotes (not just +1 on everything)20:25
asalkeld(but helps to code to know the code)20:25
shardySend some patches which prove you have some familiarity with the codebase and we can assess code-style/ability20:25
shardyBe active in #heat, get to know us/discuss stuff20:26
shardyattend these meetings from time to time and contribute to the discussions20:26
shardyalso ideally chime in on openstack-dev Heat related threads20:26
asalkeldlooks like therve is getting close20:26
shardyasalkeld: that was going to be my second point! :)20:27
shardySo I'd like to propose therve for heat-core20:27
asalkeldoops, sorry to spoil20:27
asalkeld+120:27
stevebakerI think we're keeping up with review load at the moment (HOT template reviews are pulling down our averages ;) )20:27
sdake_I think typically projects propose on ml20:27
sdake_and ppl vote there so there is a record20:27
shardyhe's done quite a lot of high-quality reviews lately, sent some nice patches, and has been actively involved day-to-day20:27
therve\o/20:27
zaneb+1, but I believe this is supposed to happen on the mailing list20:28
shardysdake_: Yes, we'll do the formal thing on the ML too20:28
shardyjust wanted to check there was consensus since we're discussing heat-core anyway20:28
sdake_need more reviewers definately20:28
stevebakersounds good to me20:28
jpeeleryep, agreed20:28
shardyOk, I'll send a propose email to openstack-dev later, please add your response there20:29
radixyay therve :)20:29
lifelessradix: oh hello :)20:29
therveThanks, I'll try to prove worthy! :)20:29
radixhello :)20:29
shardyYep, nice work therve, thanks :)20:29
shardy#topic Proposal: add public cloud resource types in-tree20:30
*** openstack changes topic to "Proposal: add public cloud resource types in-tree (Meeting topic: heat)"20:30
shardysdake, was this yours?20:30
zanebI think it was stevebaker20:30
asalkeldthere is a link20:30
wirehead_There was an IRC discussion on the subject that happened mostly in PST-friendly hours20:30
zanebso, by in-tree do we mean /contrib?20:30
zanebif so then +120:30
asalkeldzaneb, no in-tree20:30
sdake_asalkeld's shardy20:31
asalkeldlike first class20:31
asalkelddang, finding link...20:31
*** vkmc has joined #openstack-meeting20:31
*** m4dcoder has quit IRC20:31
sdake_its the same link posted above for the action items20:31
asalkeldhttps://wiki.openstack.org/wiki/Heat/on-public-clouds#Proposal_to_keep_Public_OpenStack_cloud_resources_in-tree20:31
shardystevebaker: care to give us a summary of the proposal?20:32
stevebaker<stevebaker> I think we should do what the kernel does, encourage plugins to be in-tree by:20:32
asalkeldso to me important point is: So not every public cloud on the planet, but rather where there are developers that are actively participating in the Heat commutity.20:32
stevebaker 1. not guaranteeing a stable internal api20:32
stevebaker 2. committing to updating in-tree plugins whenever internal api does change20:32
asalkeldI like that stevebaker +120:33
zaneb+1 on that20:33
stevebakerit works for the kernel20:33
*** jbrogan has quit IRC20:33
asalkeldto me better in tree, than out20:33
SpamapSWhat exact example of this are we thinking of?20:33
sdake_kernel has a million maintainers20:33
stevebakerSpamapS: hpcloud and rackspace20:33
davidhadasswift20:34
sdake_i believe asalkeld's proposal was essentially to put a hpcloud and rackspace at top of resources directory20:34
kebrayso, if internal API breaks, there's no guarantee that in-tree resources get updated and will work?  Isn't that the argument for them to be out-of-tree?20:34
zanebotoh we shouldn't be encouraging vendors to have non-compatible OpenStack APIs in the first place20:34
shardyI've got no real objection provided they're actively maintained20:34
sdake_and let them go wild with a "MAINTAINERS" contact20:34
shardydon't want to ship stuff which is broken ;)20:34
SpamapSstevebaker: but what special sauce would they have that isn't just "openstack" ?20:34
*** ayoung_ has joined #openstack-meeting20:34
zanebkebray: 2. committing to updating in-tree plugins whenever internal api does change20:34
wirehead_Yeah, if the internal API breaks, we would commit to updating the in-tree resources20:34
kebrayzaneb: we all know APIs never change :-)20:35
*** ayoung_ is now known as ayoung\20:35
stevebakerSpamapS: I would assume that as these public clouds are updated then legacy workarounds could be taken out of our tree20:35
davidhadasswift20:35
sdake_my only major heartburn with the proposal is we have no way to validate or test it20:35
davidhadas(sorry)20:35
*** ayoung\ has quit IRC20:35
asalkeldsdake_ they can add special mocks20:35
stevebakersdake, I'd like the tempest tests to be run against different clouds20:35
*** ayoung_ has joined #openstack-meeting20:35
shardyideally, those contributing these would provide provider-agnostic resources in the main resources area20:36
shardycan anyone explain some of the reasons for provider-specific resources?20:36
wirehead_Hacks.20:36
asalkeldweird auth20:36
sdake_no cloudinit20:36
*** ayoung_ has quit IRC20:36
zaneb+1 for hacks. +2 for putting them in /contrib20:36
SpamapSstevebaker: I guess I'm missing where they need any special "not openstack" things right now. :-P20:36
asalkeldand limited implementations?20:36
*** dcramer_ has joined #openstack-meeting20:36
*** ayoung_ has joined #openstack-meeting20:36
kebrayrackspace images don't have cloudinit on them today.20:36
SpamapSNo cloud-init has its genesis in rackspace, but it could very well be something that other private cloud operators do...20:37
asalkeldso shardy my hope is these are short lived20:37
sdake_rackspace also has no way to upload images - so  there is no real workaround without rs specific hacks to resources20:37
asalkeldsdake_ yea, you have to modify an existing one and "save" it20:38
SpamapSsdake_: HP is the same.20:38
shardyOk, not having cloud-init sounds pretty limiting to me, but if that's the status-quo then I guess we go with the hacks dir :)20:38
wirehead_I think that the hacks related to simple things like getting images up will hopefully go away, but there's always going to be some potential for vendor-specific magic stuff20:38
sdake_just see a future where there are 20 server plugins, 20 storage plugins, 20 different type of quantum plugins etc20:38
sdake_becomes especially intrusive if we change around the dsl20:38
kebrayThe workaround is snapshot an image, since you can't upload.20:38
*** lpabon has quit IRC20:38
*** m4dcoder has joined #openstack-meeting20:38
SpamapSI don't see this as hacks, but just drivers.20:38
asalkeldsdake to me worse if they are out of tree20:39
asalkeld(we then need much stronger api versioning)20:39
shardyOk, do we need to start a ML discussion on this?20:39
SpamapSYes agreed, in-tree drivers will stay more useful to more people.20:39
wirehead_Do we need to specify more carefully how it would look, so that people can be comfortable with exactly how it's split up?20:39
asalkeldme thinking it would make infra's life easier20:40
stevebakerlets decide when the first patch lands20:40
wirehead_We're mostly nodding in agreement about the base principles.20:40
shardyOk, well lets move on for now, and if necessary follow up on the ML20:40
shardy#topic Proposal (sdake): For [rs-dsl] or [open-api-dsl] require +2 from asalkeld, jpeeler, sdake, stevebaker, zaneb with +A from shardy20:40
*** openstack changes topic to "Proposal (sdake): For [rs-dsl] or [open-api-dsl] require +2 from asalkeld, jpeeler, sdake, stevebaker, zaneb with +A from shardy (Meeting topic: heat)"20:40
sdake_(and therve possibly:)20:41
asalkeld?20:41
sdake_so basic idea here is since dsl is huge change to everything in heat20:41
sdake_and we have to live with it20:41
sdake_we should all express our agreement in the patch20:41
sdake_vs just couple core devs20:41
SpamapSPerhaps we just call it a "majority" of devs need to weigh in with +2's?20:42
zanebagree with the rationale20:42
shardySo I think this may be a bit hard to manage, I agree everything should be well reviewed but will this make the review cycle unmanageble?20:42
sdake_personally I think the new dsl is pretty sweet20:42
asalkeldmm, so how do you figure out if a patch is dsl affecting20:42
SpamapSI don't want to set a precedent that we all have to agree or even review big decisions.20:42
sdake_only for the "first" patch that lands shardy20:42
zanebhowever, I don't think we should be committing the "end-state" DSL example at all20:42
zanebwe should have an example template that evolves with the code20:43
SpamapSBut I do like the idea that we would step back and not "approve" until at least half of the core team has said +2.20:43
shardyzaneb: I completely agree, incremental evolution20:43
*** jasond has quit IRC20:43
*** dstanek has quit IRC20:43
asalkeldis this for the heat-template patch or code in heat?20:43
zanebasalkeld: I think we're talking about the patch20:43
sdake_asalkeld: read the agenda - there are links there20:43
*** jasond has joined #openstack-meeting20:43
zanebI personally don't see the patch as something that will ever be committed20:44
therveAs long as we do incremental changes, I don't think there is much to fear about the end result being disliked.20:44
shardyOk, well shall we say that people posting HOT/DSL related patches should add all heat-core to the reviewers list, and that we (heat-core) will make sure things are reviewed by several (more than 2) reviewers before approving?20:44
zanebit's just using Gerrit as a discussion tool20:44
shardyI don't need to be the only one to approve IMO20:44
zanebI can -2 now to save time? ;)20:44
therveWe should probably all pay slightly more attention to those I presume20:44
kebrayAs long as the templates are properly versioned, can't we manage having a rapidly changing (lightweight review) template format in the short run?   that is, we only need to be backwards compatible with the version that yes stamped every 6 months, right?20:45
zanebshardy: +120:45
zanebkebray: correct20:45
shardytherve: Yep, we can just agree to give extra attention (and time) for everyone to get a look at stuff before it's merged20:45
therveshardy, In practice how does gerrit support it?20:45
stevebakershardy: +120:45
sdake_kebray as long as they are forward compatible...20:45
zanebI think everyone acknowledges there's a higher bar for consensus when implementing major features20:45
stevebakeran example template is just an expression of intent though20:46
asalkeldnot a spec20:46
*** sushils has joined #openstack-meeting20:46
sdake_so to zaneb's point about not approving the changes, shardy should we banhammer the patch so folks dont inadvertantly merge it ?20:47
asalkeldsdake why not merge it and work on it?20:47
* stevebaker has to go20:47
shardysdake_: I guess, but has anyone ever accidentally approved something?20:47
sdake_zaneb's idea ;)20:47
asalkeldinstead of letting it hang20:47
zanebshardy: I accidentally approved something the other day ;)20:48
shardyasalkeld: Idea is just to get eyes on the patch before we merge something half the team hate ;)20:48
* sdake_ admits to +2 +A without another +2 recently... groan20:48
shardyzaneb: lol20:48
asalkeldshardy, sure20:48
asalkeldbut, we can iterate as well20:48
clarkbif you catch yourself before jenkins finishes testing you can remove your +A to prevent merging20:48
sdake_clarkb ya i did catch it quickly20:49
sdake_and fixed it fortunately :)20:49
shardyOk, well shall we just handle this informally, if there's a patch anyone reviews which they thing is suitably contentious, -2 it and make sure we get consensus before merge20:49
zanebclarkb: I didn't want to be that obvious ;)20:49
sdake_zaneb never makes mistakess ;)20:49
shardyFpr obviously OK and simple/small stuff, we use the normal process of 2x+220:49
sdake_shardy : i think for most things that makes sense, the dsl is a special case tho20:50
asalkeldshardy, you mean for everything else?20:50
shardyI think we can all be trusted with this stuff, but I do agree we should all be extra active reviewing it20:50
therveLet's not be afraid of reverts too if that needs to happen.20:50
shardyasalkeld: I think we're just saying for big DSL changes20:51
asalkeldgood20:51
SpamapS9 minutes20:51
*** cp16net is now known as cp16net|away20:51
shardyI've got no desire to extend the review cycle unnecessarily20:51
sdake_in fact first one would be good enough to satisfy me :)20:51
sdake_after that iterate + normal process20:51
*** sushils has quit IRC20:51
shardy#topic How/where to handle HOT in the code20:51
*** openstack changes topic to "How/where to handle HOT in the code (Meeting topic: heat)"20:51
shardySo shall we skip this and go to open discussion?20:52
shardysince we really covered it earlier?20:52
zanebshardy: yep, we've done that to death20:52
shardy#topic Open discussion20:52
sdake_i do have one quesiton20:52
*** openstack changes topic to "Open discussion (Meeting topic: heat)"20:52
asalkeldinitial Environment patch: https://review.openstack.org/#/c/30866/20:52
zanebsdake_: too late ;)20:52
sdake_the open-dsl vs hot - are they competing proposals?20:52
fsargentDo y'all have Rackspace accounts yet? How is it going?20:52
fsargentIf not: http://iopenedthecloud.com/20:53
zanebsdake_: no, they're different names for the same general effort20:53
asalkeldthanks fsargent20:53
shardysdake_: No, we're trying to converge on a native syntax which pleases all those who want a non-cfn template model20:53
sdake_fsargent I applied but no email yet20:53
*** sushils has joined #openstack-meeting20:53
fsargentokay, I'll knock some heads together.20:53
zanebfsargent: I have the t-shirt, but not the account yet20:53
asalkeldha20:53
wirehead_Have the t-shirt, not the account.  That's a metaphor for something20:53
sdake_zaneb afraid to go over his 500 mo limit ;)20:54
asalkeldfsargent, can we get a racks server resource?20:54
shardyasalkeld: nice, will review in the morning :)20:54
wirehead_racks server resource?20:54
asalkelda resource that starts a rackspace server20:54
kebrayracks server, LBaaS, and DBaaS resources for Heat are in the works.20:54
kebrayasalkeld:  my team is working it right now.20:54
asalkeldI just need the server20:55
asalkeld(alpha?)20:55
kebrayYep.. well, I need all 3 :-)20:55
sdake_in h2 the nova resources are changing20:55
sdake_so keep that in mind - may hav eto do a bit of rework on your end20:55
*** SergeyLukjanov has quit IRC20:55
shardykebray: feel free to post WIP/draft patches or a fork somewhere, so we can see what you're doing :)20:55
asalkeld+120:55
kebraysdake_ don't care about Nova changes, as long as the resource implementation doesn't change.  it'll be one of the vendor specific resources for now.20:56
SpamapSsmall patches that work ho-hum are better than giant patches that "work fine in my rack"20:56
shardy4 minutes, anything else?20:56
zanebrandom interesting thing I discovered today20:56
zaneb#link http://www.pulpproject.org/20:56
kebrayYeah, been wondering where the team should dump code.. sort of waiting for the in-tree vs. just stack forge discussion to settle.20:56
zanebin the context of https://wiki.openstack.org/wiki/Heat/htr20:56
zanebapparently puppet are using it for their manifests repo20:57
zanebthat is all.20:57
SpamapSmeh20:57
* SpamapS hugs his image based update dreams tightly.20:57
asalkeldhar20:57
sdake_shardy the "only run non-aws templates" wasn't in the h2 milestone20:58
* kebray hands SpamapS a copy of Good to Great.20:58
sdake_the blueprint spamaps wrote up20:58
shardysdake_: the open-api-dsl is the umbrella BP, targetted at h320:58
sdake_we may need that for nova-server blueprint20:58
shardyas we have a load of dependent BPs targeted at h2, most of which have not even been started20:58
shardywhich is a bit worrying20:59
shardybut anyway, out of time20:59
wirehead_kebray: I haven't heard any major partisan fans of the stack forge approach.  We can negative-vote to say that the rackspace resource ought to live in-tree20:59
shardy#endmeeting20:59
*** openstack changes topic to "OpenStack meetings"20:59
openstackMeeting ended Wed May 29 20:59:15 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-05-29-20.00.html20:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-05-29-20.00.txt20:59
openstackLog:            http://eavesdrop.openstack.org/meetings/heat/2013/heat.2013-05-29-20.00.log.html20:59
*** m4dcoder has quit IRC20:59
SpamapSty everyone20:59
*** atiwari has joined #openstack-meeting20:59
wirehead_Thx20:59
shardythanks all!20:59
*** timductive has left #openstack-meeting20:59
therveThanks!20:59
*** timello has quit IRC21:00
*** therve has left #openstack-meeting21:00
*** jasond has left #openstack-meeting21:01
*** egallen has joined #openstack-meeting21:01
*** IlyaE has quit IRC21:03
*** sdake_ has quit IRC21:04
*** timello has joined #openstack-meeting21:08
*** stevebaker has left #openstack-meeting21:08
*** martine has quit IRC21:09
*** IlyaE has joined #openstack-meeting21:11
*** koolhead17 has quit IRC21:14
*** dcramer_ has quit IRC21:16
*** adrian_otto has quit IRC21:19
*** jhenner has joined #openstack-meeting21:25
*** Okatz has joined #openstack-meeting21:28
*** jhenner1 has joined #openstack-meeting21:31
*** IlyaE has quit IRC21:33
*** jhenner has quit IRC21:33
*** jasondotstar has quit IRC21:34
*** lcheng has quit IRC21:34
*** Okatz has quit IRC21:34
*** Okatz has joined #openstack-meeting21:35
*** glikson has quit IRC21:37
*** boris-42 has quit IRC21:40
*** Okatz has quit IRC21:40
*** xBsd has joined #openstack-meeting21:43
*** xBsd has quit IRC21:45
*** clayg_ has left #openstack-meeting21:45
*** colinmcnamara has quit IRC21:46
*** lbragstad has quit IRC21:49
*** lastidiot has quit IRC21:50
*** stevemar2 has quit IRC21:52
*** Tross has quit IRC21:56
*** kchenweijie has joined #openstack-meeting21:57
*** kchenweijie has left #openstack-meeting21:57
*** kebray has quit IRC21:58
*** egallen has quit IRC22:03
*** elo has joined #openstack-meeting22:04
*** mdomsch has quit IRC22:08
*** ewindisch has joined #openstack-meeting22:11
*** spzala has quit IRC22:11
*** jog0 has quit IRC22:12
*** ewindisch has quit IRC22:12
*** ewindisch has joined #openstack-meeting22:13
*** ryanpetr_ has quit IRC22:17
*** ivasev has quit IRC22:17
*** woodspa has quit IRC22:17
*** egallen has joined #openstack-meeting22:17
*** pcm___ has quit IRC22:18
*** hanney has quit IRC22:28
*** egallen has quit IRC22:31
*** radez is now known as radez_g0n322:31
*** egallen has joined #openstack-meeting22:33
*** egallen has quit IRC22:35
*** mrodden has quit IRC22:35
*** markpeek has quit IRC22:37
*** anniec has quit IRC22:39
*** elo has quit IRC22:42
*** anniec has joined #openstack-meeting22:42
*** spzala has joined #openstack-meeting22:47
*** dcramer__ has joined #openstack-meeting22:49
*** matiu has joined #openstack-meeting22:52
*** wirehead_ has left #openstack-meeting22:52
*** ewindisch has quit IRC22:53
*** shengjie_ has joined #openstack-meeting22:53
*** dcramer__ has quit IRC22:54
*** shengjie has joined #openstack-meeting22:54
*** seanrob has joined #openstack-meeting22:55
*** bpb has quit IRC22:55
*** seanrob_ has joined #openstack-meeting22:55
*** seanrob has quit IRC22:59
*** dhellmann is now known as dhellmann-away23:02
*** ayurchen has joined #openstack-meeting23:03
*** eharney has quit IRC23:06
*** harlowja_ has quit IRC23:06
*** harlowja has joined #openstack-meeting23:07
*** shengjie has quit IRC23:08
*** hemna is now known as hemnafk23:09
*** jhenner1 has quit IRC23:10
*** anniec has joined #openstack-meeting23:15
*** zb has joined #openstack-meeting23:16
*** lloydde_ has quit IRC23:18
*** zaneb has quit IRC23:18
*** sdake_ has joined #openstack-meeting23:19
*** sdake_ has quit IRC23:19
*** sdake_ has joined #openstack-meeting23:19
*** sdake has quit IRC23:20
*** sdake_ is now known as sdake23:25
*** salv-orlando has quit IRC23:25
*** mkollaro has quit IRC23:26
*** anniec has quit IRC23:28
*** MarkAtwood has quit IRC23:28
*** lastidiot has joined #openstack-meeting23:29
*** otherwiseguy has quit IRC23:30
*** markwash has quit IRC23:32
*** ewindisch has joined #openstack-meeting23:36
*** anniec has joined #openstack-meeting23:42
*** dcramer__ has joined #openstack-meeting23:45
*** sdake has quit IRC23:46
*** zbitter has joined #openstack-meeting23:47
*** zb has quit IRC23:47
*** sushils has quit IRC23:48
*** openrk has joined #openstack-meeting23:51
*** zbitter has quit IRC23:53
*** sushils has joined #openstack-meeting23:54
*** colinmcnamara has joined #openstack-meeting23:55
*** sdake has joined #openstack-meeting23:59
*** sdake has quit IRC23:59
*** sdake has joined #openstack-meeting23:59

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