Tuesday, 2013-07-09

*** salv-orlando has quit IRC00:00
*** ryanpetrello has quit IRC00:01
*** michchap has joined #openstack-meeting00:02
*** michchap has quit IRC00:02
*** michchap has joined #openstack-meeting00:03
*** thunquest has quit IRC00:03
*** anteaya has quit IRC00:05
*** mikal has quit IRC00:06
*** beagles has quit IRC00:06
*** mikal has joined #openstack-meeting00:07
*** jrodom has quit IRC00:09
*** lloydde has quit IRC00:11
*** beagles has joined #openstack-meeting00:12
*** colinmcnamara has quit IRC00:14
*** brucer has joined #openstack-meeting00:16
*** dkliban_afk has joined #openstack-meeting00:18
*** sarob has joined #openstack-meeting00:19
*** fnaval has joined #openstack-meeting00:20
*** safchain has quit IRC00:20
*** zehicle_at_dell has quit IRC00:21
*** galstrom is now known as galstrom_zzz00:23
*** bgorski has joined #openstack-meeting00:23
*** romcheg has joined #openstack-meeting00:25
*** romcheg has quit IRC00:26
*** marun has joined #openstack-meeting00:27
*** brucer has quit IRC00:27
*** armax has quit IRC00:28
*** sarob has quit IRC00:28
*** zehicle_at_dell has joined #openstack-meeting00:29
*** yamahata has quit IRC00:32
*** Adri2000 has quit IRC00:33
*** sarob has joined #openstack-meeting00:33
*** Mandell has quit IRC00:33
*** kebray has quit IRC00:34
*** shang has quit IRC00:35
*** Mandell has joined #openstack-meeting00:36
*** marun has quit IRC00:38
*** Adri2000 has joined #openstack-meeting00:40
*** sleepsonthefloor has quit IRC00:41
*** Swami has quit IRC00:42
*** sarob has quit IRC00:43
*** sarob has joined #openstack-meeting00:43
*** brucer has joined #openstack-meeting00:46
*** ryanpetrello has joined #openstack-meeting00:48
*** cp16net|away is now known as cp16net00:48
*** sarob has quit IRC00:48
*** fnaval has quit IRC00:48
*** cp16net is now known as cp16net|away00:48
*** cp16net|away is now known as cp16net00:48
*** bdpayne has quit IRC00:49
*** anniec has joined #openstack-meeting00:50
*** adjohn has quit IRC00:55
*** fifieldt has quit IRC00:55
*** adjohn has joined #openstack-meeting00:55
*** fifieldt has joined #openstack-meeting00:56
*** brucer has quit IRC00:57
*** brucer has joined #openstack-meeting00:58
*** adjohn has quit IRC01:00
*** tanisdl has quit IRC01:03
*** brucer has joined #openstack-meeting01:04
*** brucer has quit IRC01:05
*** JimJiang has joined #openstack-meeting01:07
*** anniec has quit IRC01:10
*** Mandell has quit IRC01:15
*** adjohn has joined #openstack-meeting01:20
*** dosaboy_ has joined #openstack-meeting01:22
*** nati_ueno has quit IRC01:22
*** sjing has joined #openstack-meeting01:24
*** scott_ has quit IRC01:24
*** haomaiwang has joined #openstack-meeting01:24
*** dosaboy has quit IRC01:26
*** virajh has quit IRC01:26
*** yaguang has joined #openstack-meeting01:27
*** brucer has joined #openstack-meeting01:28
*** jlucci has quit IRC01:33
*** ryanpetrello has quit IRC01:36
*** brucer has quit IRC01:39
*** scott_ has joined #openstack-meeting01:39
*** asalkeld has quit IRC01:41
*** gyee has quit IRC01:42
*** gongysh has joined #openstack-meeting01:44
*** leizhang has joined #openstack-meeting01:47
*** MarkAtwood has quit IRC01:48
*** asalkeld has joined #openstack-meeting01:54
*** markwash has joined #openstack-meeting01:55
*** dkliban_afk has quit IRC01:56
*** yamahata has joined #openstack-meeting01:58
*** emagana has quit IRC02:01
*** zehicle_at_dell has quit IRC02:03
*** MarkAtwood has joined #openstack-meeting02:11
*** bgorski has quit IRC02:19
*** novas0x2a|laptop has quit IRC02:20
*** mdomsch has quit IRC02:21
*** zul has joined #openstack-meeting02:22
*** stevemar has joined #openstack-meeting02:30
*** dkliban_afk has joined #openstack-meeting02:32
*** cp16net is now known as cp16net|away02:35
*** jrodom has joined #openstack-meeting02:39
*** lbragstad has joined #openstack-meeting02:40
*** litong has quit IRC02:42
*** zhuadl has joined #openstack-meeting02:42
*** jlucci has joined #openstack-meeting02:49
*** stevemar has quit IRC02:52
*** Mandell has joined #openstack-meeting02:52
*** colinmcnamara has joined #openstack-meeting02:53
*** neelashah has joined #openstack-meeting02:54
*** IlyaE has joined #openstack-meeting02:55
*** otherwiseguy has joined #openstack-meeting02:56
*** SergeyLukjanov has joined #openstack-meeting02:56
*** neelashah1 has joined #openstack-meeting03:01
*** neelashah has quit IRC03:01
*** jdurgin1 has quit IRC03:05
*** bdpayne has joined #openstack-meeting03:06
*** emagana has joined #openstack-meeting03:12
*** lloydde has joined #openstack-meeting03:13
*** mdomsch has joined #openstack-meeting03:15
*** emagana has quit IRC03:17
*** lloydde has quit IRC03:17
*** dguitarbite has joined #openstack-meeting03:18
*** sleepsonthefloor has joined #openstack-meeting03:19
*** bdpayne has quit IRC03:21
*** zhuadl has quit IRC03:25
*** adjohn has quit IRC03:26
*** adjohn has joined #openstack-meeting03:26
*** cp16net|away is now known as cp16net03:27
*** litong has joined #openstack-meeting03:29
*** martine_ has joined #openstack-meeting03:34
*** martine_ has quit IRC03:39
*** IlyaE has quit IRC03:42
*** lpabon has quit IRC03:48
*** zhuadl has joined #openstack-meeting03:52
*** jrodom has quit IRC03:52
*** colinmcnamara has quit IRC03:58
*** martine has joined #openstack-meeting03:58
*** martine is now known as Guest3805803:59
*** sushils has quit IRC04:03
*** IlyaE has joined #openstack-meeting04:03
*** emagana has joined #openstack-meeting04:07
*** zehicle_at_dell has joined #openstack-meeting04:07
*** sushils has joined #openstack-meeting04:08
*** MarkAtwood has quit IRC04:09
*** litong has quit IRC04:10
*** bdpayne has joined #openstack-meeting04:14
*** dcramer_ has quit IRC04:19
*** MarkAtwood has joined #openstack-meeting04:20
*** IlyaE has quit IRC04:22
*** neelashah1 has quit IRC04:24
*** mrunge has joined #openstack-meeting04:25
*** dcramer_ has joined #openstack-meeting04:32
*** jhenner has quit IRC04:34
*** brucer has joined #openstack-meeting04:34
*** terriyu has quit IRC04:35
*** boris-42 has joined #openstack-meeting04:45
*** emagana has quit IRC04:51
*** vipul is now known as vipul-away04:58
*** afazekas has joined #openstack-meeting05:03
*** sarob has joined #openstack-meeting05:05
*** IlyaE has joined #openstack-meeting05:09
*** jlucci has quit IRC05:10
*** dkliban_afk has quit IRC05:12
*** IlyaE has quit IRC05:20
*** bdpayne has quit IRC05:23
*** rwsu-away has quit IRC05:31
*** bdpayne has joined #openstack-meeting05:35
*** otherwiseguy has quit IRC05:37
*** MarkAtwood has quit IRC05:38
*** markpeek has quit IRC05:38
*** asalkeld has quit IRC05:42
*** IlyaE has joined #openstack-meeting05:42
*** SergeyLukjanov has quit IRC05:42
*** Guest38058 has quit IRC05:46
*** rwsu has joined #openstack-meeting05:48
*** dosaboy has joined #openstack-meeting05:48
*** sarob has quit IRC05:49
*** dosaboy_ has quit IRC05:51
*** otherwiseguy has joined #openstack-meeting05:54
*** zhuadl has quit IRC05:56
*** mrunge has quit IRC06:04
*** zhuadl has joined #openstack-meeting06:04
*** ryanpetrello has joined #openstack-meeting06:16
*** mrunge has joined #openstack-meeting06:17
*** IlyaE has quit IRC06:18
*** SergeyLukjanov has joined #openstack-meeting06:25
*** bdpayne has quit IRC06:26
*** jcoufal has joined #openstack-meeting06:30
*** ryanpetrello has quit IRC06:33
*** psedlak has joined #openstack-meeting06:42
*** afazekas_ has joined #openstack-meeting06:49
*** Yada has joined #openstack-meeting06:53
*** afazekas_ has quit IRC06:55
*** sarob has joined #openstack-meeting07:00
*** psedlak has quit IRC07:00
*** sarob has quit IRC07:05
*** zhuadl has quit IRC07:07
*** nicolae_ has joined #openstack-meeting07:10
*** sushils has quit IRC07:11
*** afazekas_ has joined #openstack-meeting07:13
*** zhuadl has joined #openstack-meeting07:13
*** psedlak has joined #openstack-meeting07:16
*** ujuc has joined #openstack-meeting07:18
*** ujuc has quit IRC07:22
*** ujuc has joined #openstack-meeting07:22
*** tkammer has joined #openstack-meeting07:30
*** salv-orlando has joined #openstack-meeting07:34
*** Mandell has quit IRC07:43
*** jtomasek has joined #openstack-meeting07:44
*** boris-42 has quit IRC07:52
*** Yada has quit IRC07:52
*** adam_g has quit IRC07:53
*** derekh has joined #openstack-meeting08:01
*** Guest35910 has quit IRC08:09
*** sivel has joined #openstack-meeting08:09
*** dguitarbite has quit IRC08:13
*** Yada has joined #openstack-meeting08:20
*** johnthetubaguy has joined #openstack-meeting08:20
*** dguitarbite has joined #openstack-meeting08:25
*** koolhead17 has quit IRC08:30
*** johnthetubaguy has quit IRC08:34
*** jhenner has joined #openstack-meeting08:40
*** sushils has joined #openstack-meeting08:47
*** romcheg has joined #openstack-meeting08:48
*** romcheg has left #openstack-meeting08:49
*** mikal has quit IRC08:53
*** mikal has joined #openstack-meeting08:54
*** boris-42 has joined #openstack-meeting08:55
*** fifieldt-mobile has joined #openstack-meeting08:57
*** dklyle has joined #openstack-meeting09:04
*** fifieldt-mobile has quit IRC09:05
*** egallen has joined #openstack-meeting09:06
*** rods1 has joined #openstack-meeting09:10
*** michchap has quit IRC09:10
*** david-lyle has quit IRC09:12
*** asadoughi has quit IRC09:12
*** mordred has quit IRC09:12
*** dragondm has quit IRC09:12
*** e-vad has quit IRC09:12
*** _ozstacker_ has quit IRC09:12
*** ivoks has quit IRC09:12
*** lcheng has quit IRC09:12
*** bdperkin has quit IRC09:12
*** netapp has quit IRC09:12
*** jd__ has quit IRC09:12
*** rmk has quit IRC09:12
*** _cerberus_ has quit IRC09:12
*** Yada has quit IRC09:12
*** derekh has quit IRC09:12
*** dcramer_ has quit IRC09:12
*** yamahata has quit IRC09:12
*** jog0 has quit IRC09:12
*** jculp has quit IRC09:12
*** ayoung has quit IRC09:12
*** matiu has quit IRC09:12
*** yuanz has quit IRC09:12
*** rongze has quit IRC09:12
*** jhenner has quit IRC09:12
*** mdomsch has quit IRC09:12
*** cliu has quit IRC09:12
*** amotoki has quit IRC09:12
*** erwan_taf has quit IRC09:12
*** swifterdarrell has quit IRC09:12
*** akscram has quit IRC09:12
*** guitarzan has quit IRC09:12
*** nachi__ has quit IRC09:12
*** HenryG has quit IRC09:12
*** akshayms_ has quit IRC09:12
*** zaro has quit IRC09:12
*** maurosr has quit IRC09:12
*** jeblair has quit IRC09:12
*** Adri2000 has quit IRC09:12
*** hyakuhei has quit IRC09:12
*** juice has quit IRC09:12
*** rosmaita_ has quit IRC09:12
*** cp16net has quit IRC09:12
*** sileht has quit IRC09:12
*** briancline has quit IRC09:12
*** jdurgin has quit IRC09:12
*** ttx has quit IRC09:12
*** galstrom_zzz has quit IRC09:12
*** cyeoh has quit IRC09:12
*** redthrux_ has quit IRC09:12
*** samalba has quit IRC09:12
*** benonsoftware has quit IRC09:12
*** mirrorbox has quit IRC09:12
*** jecarey has quit IRC09:12
*** dachary has quit IRC09:12
*** Guest76948 has quit IRC09:12
*** edleafe has quit IRC09:12
*** EntropyWorks has quit IRC09:12
*** jcooley has quit IRC09:12
*** arosen1 has quit IRC09:12
*** ndipanov has quit IRC09:12
*** ItSANgo has quit IRC09:12
*** al-maisan has quit IRC09:12
*** rpodolyaka has quit IRC09:12
*** esmute has quit IRC09:12
*** haleyb has quit IRC09:12
*** dtroyer has quit IRC09:12
*** mdenny has quit IRC09:12
*** jamespage has quit IRC09:12
*** jaypipes has quit IRC09:12
*** uvirtbot has quit IRC09:12
*** ohadlevy has quit IRC09:12
*** Adri2000 has joined #openstack-meeting09:13
*** hyakuhei has joined #openstack-meeting09:13
*** juice has joined #openstack-meeting09:13
*** rosmaita_ has joined #openstack-meeting09:13
*** cp16net has joined #openstack-meeting09:13
*** sileht has joined #openstack-meeting09:13
*** briancline has joined #openstack-meeting09:13
*** jdurgin has joined #openstack-meeting09:13
*** ttx has joined #openstack-meeting09:13
*** galstrom_zzz has joined #openstack-meeting09:13
*** cyeoh has joined #openstack-meeting09:13
*** redthrux_ has joined #openstack-meeting09:13
*** samalba has joined #openstack-meeting09:13
*** benonsoftware has joined #openstack-meeting09:13
*** mirrorbox has joined #openstack-meeting09:13
*** jecarey has joined #openstack-meeting09:13
*** dachary has joined #openstack-meeting09:13
*** Guest76948 has joined #openstack-meeting09:13
*** edleafe has joined #openstack-meeting09:13
*** EntropyWorks has joined #openstack-meeting09:13
*** jcooley has joined #openstack-meeting09:13
*** michchap_ has joined #openstack-meeting09:15
*** bdperkin has joined #openstack-meeting09:15
*** ozstacker has joined #openstack-meeting09:15
*** jhenner has joined #openstack-meeting09:15
*** Yada has joined #openstack-meeting09:15
*** derekh has joined #openstack-meeting09:15
*** dcramer_ has joined #openstack-meeting09:15
*** mdomsch has joined #openstack-meeting09:15
*** yamahata has joined #openstack-meeting09:15
*** cliu has joined #openstack-meeting09:15
*** jog0 has joined #openstack-meeting09:15
*** amotoki has joined #openstack-meeting09:15
*** jculp has joined #openstack-meeting09:15
*** arosen1 has joined #openstack-meeting09:15
*** ayoung has joined #openstack-meeting09:15
*** matiu has joined #openstack-meeting09:15
*** rongze has joined #openstack-meeting09:15
*** ndipanov has joined #openstack-meeting09:15
*** yuanz has joined #openstack-meeting09:15
*** ItSANgo has joined #openstack-meeting09:15
*** al-maisan has joined #openstack-meeting09:15
*** rpodolyaka has joined #openstack-meeting09:15
*** esmute has joined #openstack-meeting09:15
*** haleyb has joined #openstack-meeting09:15
*** dtroyer has joined #openstack-meeting09:15
*** mdenny has joined #openstack-meeting09:15
*** jamespage has joined #openstack-meeting09:15
*** erwan_taf has joined #openstack-meeting09:15
*** jaypipes has joined #openstack-meeting09:15
*** uvirtbot has joined #openstack-meeting09:15
*** ohadlevy has joined #openstack-meeting09:15
*** swifterdarrell has joined #openstack-meeting09:15
*** akscram has joined #openstack-meeting09:15
*** guitarzan has joined #openstack-meeting09:15
*** nachi__ has joined #openstack-meeting09:15
*** HenryG has joined #openstack-meeting09:15
*** akshayms_ has joined #openstack-meeting09:15
*** mordred has joined #openstack-meeting09:15
*** dragondm has joined #openstack-meeting09:15
*** e-vad has joined #openstack-meeting09:15
*** ivoks has joined #openstack-meeting09:15
*** zaro has joined #openstack-meeting09:15
*** maurosr has joined #openstack-meeting09:15
*** lcheng has joined #openstack-meeting09:15
*** jeblair has joined #openstack-meeting09:15
*** jd__ has joined #openstack-meeting09:15
*** rmk has joined #openstack-meeting09:15
*** _cerberus_ has joined #openstack-meeting09:15
*** netapp has joined #openstack-meeting09:19
*** lcheng has quit IRC09:26
*** lcheng has joined #openstack-meeting09:27
*** ivoks has quit IRC09:28
*** ivoks has joined #openstack-meeting09:28
*** rpodolyaka has quit IRC09:28
*** rpodolyaka has joined #openstack-meeting09:28
*** netapp has quit IRC09:29
*** asalkeld has joined #openstack-meeting09:44
*** egallen has quit IRC09:45
*** tomoe_ has joined #openstack-meeting09:46
*** ujuc has quit IRC09:49
*** zhuadl has quit IRC09:51
*** JimJiang has left #openstack-meeting09:57
*** tomoe_ has quit IRC10:00
*** tomoe_ has joined #openstack-meeting10:00
*** rods1 has quit IRC10:02
*** tomoe_ has quit IRC10:04
*** dguitarbite has quit IRC10:20
*** sungju has joined #openstack-meeting10:36
*** sungju has quit IRC10:37
*** egallen has joined #openstack-meeting10:39
*** mikal has quit IRC10:39
*** mikal has joined #openstack-meeting10:41
*** netapp has joined #openstack-meeting10:46
*** sarob has joined #openstack-meeting10:46
*** egallen has quit IRC10:49
*** egallen has joined #openstack-meeting10:50
*** sarob has quit IRC10:51
*** egallen has quit IRC10:51
*** mikal has quit IRC11:00
*** mikal has joined #openstack-meeting11:01
*** gongysh has quit IRC11:02
*** radez_g0n3 is now known as radez11:03
*** zhuadl has joined #openstack-meeting11:06
*** asadoughi has joined #openstack-meeting11:08
*** topol has joined #openstack-meeting11:09
*** sarob has joined #openstack-meeting11:17
*** AndroUser has joined #openstack-meeting11:17
*** mrunge has quit IRC11:17
*** mrunge has joined #openstack-meeting11:18
*** AndroUser is now known as slong_11:18
*** adjohn has quit IRC11:20
*** dkliban_afk has joined #openstack-meeting11:29
*** slong_ has left #openstack-meeting11:33
*** jmh_ has joined #openstack-meeting11:40
*** koolhead17 has joined #openstack-meeting11:44
*** mrunge has quit IRC11:46
*** AJaeger has joined #openstack-meeting11:50
*** gpocentek has joined #openstack-meeting11:53
*** johnthetubaguy has joined #openstack-meeting11:54
*** dkehn has joined #openstack-meeting11:56
*** bfirsh has quit IRC11:58
*** AJaeger has quit IRC12:01
*** sarob has quit IRC12:03
*** AJaeger has joined #openstack-meeting12:04
*** amytron has joined #openstack-meeting12:04
*** amytron has joined #openstack-meeting12:05
*** bfirsh has joined #openstack-meeting12:07
*** jackmccann has quit IRC12:08
*** egallen has joined #openstack-meeting12:10
*** egallen has quit IRC12:15
*** marun has joined #openstack-meeting12:17
*** tedross has joined #openstack-meeting12:21
*** ryanpetrello has joined #openstack-meeting12:25
*** marun has quit IRC12:28
*** sandywalsh has quit IRC12:29
*** adjohn has joined #openstack-meeting12:31
*** dprince has joined #openstack-meeting12:32
*** lbragstad has quit IRC12:36
*** adjohn has quit IRC12:37
*** Guest38058 has joined #openstack-meeting12:42
*** sandywalsh has joined #openstack-meeting12:42
*** Daisy has joined #openstack-meeting12:44
*** dkliban_afk has quit IRC12:45
*** mkollaro has joined #openstack-meeting12:51
*** rkukura has left #openstack-meeting12:51
*** nermina has joined #openstack-meeting12:56
*** amytron has quit IRC12:56
*** slong_ has joined #openstack-meeting12:57
*** sgordon has joined #openstack-meeting12:58
*** amytron has joined #openstack-meeting12:59
*** sarob has joined #openstack-meeting12:59
*** lorin1 has joined #openstack-meeting13:00
*** neelashah has joined #openstack-meeting13:00
*** leizhang has quit IRC13:00
*** tomoe_ has joined #openstack-meeting13:01
* annegentle waves13:01
annegentleanyone here for the doc / web team meeting?13:01
cyeohhi!13:01
fifieldthiya :D13:01
*** shaunm has joined #openstack-meeting13:01
annegentlehey!13:01
lorin1*raises hand*13:01
sgordon\o/13:01
slong_Hallo13:01
shaunmmorning13:01
annegentleawesome let's get started13:01
* sarob sarob waves back13:01
annegentle#startmeeting Doc Team Meeting13:01
openstackMeeting started Tue Jul  9 13:01:53 2013 UTC.  The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
openstackThe meeting name has been set to 'doc_team_meeting'13:01
Daisyhello13:02
fifieldtbig team :D13:02
annegentleyeah, great!13:02
annegentle#topic Action items from the last meeting13:02
*** roadnick has joined #openstack-meeting13:02
annegentlethe action was for EmilienM create a blueprint on openstack-manuals to link to https://etherpad.openstack.org/HA-Active-Active13:02
annegentlethat's done13:02
annegentle#link https://blueprints.launchpad.net/openstack-manuals/+spec/improve-high-availability-support13:02
annegentleand this one was just for posterity13:03
annegentleNickChase to convert google docs to docbook, when the time comes13:03
roadnickright, turns out that it's in Asciidoc13:03
EmilienMo/13:03
roadnickso it's less of a hassle than we expected.13:03
annegentlesure13:03
annegentlecool roadnick13:03
*** Guest38058 is now known as martine_13:03
annegentleEmilienM: how goes it?13:03
koolhead17hi13:03
EmilienMannegentle: Nick and I continue the work13:04
roadnickAnd Emilien's been converting his own stuff as well13:04
annegentleEmilienM: sounds good13:04
annegentlelast Action item, sld get in touch with conf file code people to collaborate13:04
EmilienMmy next step is Network node in HA13:04
annegentlesld did so via email13:04
*** mdomsch has quit IRC13:04
*** litong has joined #openstack-meeting13:04
annegentleI did add some agenda items this morning, so next up is13:05
annegentle#topic Completion of Security Guide book sprint13:05
annegentleCongratulations to the team! It's 227 pages in PDf in Crown Quarto format.13:05
annegentlePlus dcramer_ already converted it and we're patching to get PDF and HTML13:05
slong_Impressive stuff!13:05
EmilienMwow13:05
EmilienMgreat job guys13:06
fifieldt+113:06
annegentle#link http://docs.openstack.org/sec/13:06
annegentleAlready getting requests for it and attention on the epub, really great stuff.13:06
roadnicknice!13:06
annegentleI've encouraged them to present as a panel at the Summit13:06
sarobcool13:06
koolhead17good idea13:06
annegentleand invited bdpayne to be on doc-core13:06
annegentleso all around great event, great outcome13:07
annegentleanyone from the sprint here and want to say anything?13:07
* annegentle doesn't see anyone right away13:07
lorin1I just did some reviewing on one of the days, but I thought they did a really great job.13:07
koolhead17annegentle: so we have someone who will lead the whole security doc related fix/upgrade13:07
koolhead17*identified13:07
lorin1It was a good group of people assembled for that.13:08
annegentlekoolhead17: the team is very keen to keep updates and be part of the process13:08
annegentlekoolhead17: bdpayne has esp. stepped up13:08
koolhead17annegentle: great than.13:08
lorin1I think book sprints may be a useful mechanism for drawing people into the doc effort.13:08
annegentlelorin1: did it feel like a larger group than the Ops one? From pics I couldn't tell13:08
fifieldtlooked it to me13:08
annegentlelorin1: agreed13:09
lorin1It was a slightly bigger group13:09
sgordonon the list i saw it was supposed to be around 1513:09
fifieldt13  listed on the cover page13:09
annegentlesgordon: yeah I don't know if they got all 15, 2 were MIA13:09
*** lbragstad has joined #openstack-meeting13:09
sarobsomething we should copy for the training manuals?13:09
annegentlefifieldt: yeah that sounds right13:09
annegentlesarob: a sprint is a powerful mechanism, costs about $10k-15k13:09
sarobwhy costs?13:10
annegentlesarob: with a specific goal and team assembled it might make sense, could certainly talk through it13:10
annegentlesarob: flying everyone in, paying for facilitation, possibly renting space13:10
sarobah, right13:10
roadnickMirantis would be interested in doing a sprint13:11
annegentlesarob: contact me for more details if you want to know all the gory guts of it :)13:11
sarobmaybe13:11
annegentleroadnick: what topic?13:11
sarobwill do13:11
roadnickI'm not sure yet; HA perhaps.13:11
annegentleroadnick: or just funding one?13:11
fifieldt(annegentle, minor note to clean up for the sec guide - there's two near-identical reviews open for infra/config https://review.openstack.org/#/c/35592/ & https://review.openstack.org/#/c/36102/ )13:12
annegentleroadnick: ok we could certainly talk more about details13:12
roadnickI was handed goals for Q3, which included "host an upstream sprint".13:12
annegentlefifieldt: aw man13:12
roadnickBoris is sick this week, so I haven't gotten details yet.13:12
koolhead17roadnick: sounds good!!13:12
koolhead17roadnick: the HA sprint idea13:12
annegentlefifieldt: he hadn't assigned himself so i picked it up. Drat13:12
roadnickI think he would have jumped on the boot camp if Rackspace wasn't hosting that. :)13:13
annegentleroadnick: oh that's cool. We can certainly talk.13:13
roadnickin fact, I know he would13:13
roadnickk13:13
annegentleroadnick: and we're just offering space so we could certainly adjust13:13
roadnickok, let's talk.13:13
annegentleok, great13:13
annegentle#topic v3 Compute API doc plan13:13
annegentlejust to give the background, there was a thread started by Chris Yeoh about which extensions would be deprecated for v313:14
annegentleI suggested they need to get the word out beyond just the -dev mailing list and really what they need is a document13:14
*** dcramer_ has quit IRC13:15
annegentleI still don't have a clear plan from the nova team about what they want to do to document v313:15
sgordonthere is clearly a wider issue here about API upgrades in general though IMO13:15
cyeohwell what I'd like is at least something similar to what we have for V213:15
annegentlecyeoh: sure, makes sense13:15
cyeoheg. something that can be used a reference/spec for anyone wanting to develop against v3.13:16
annegentlecyeoh: and you know all the pieces and parts for that now13:16
cyeohand my thought was that if we can make the process easier for the doc team by what we do on the Nova side, then we'll do that13:16
annegentlecyeoh: you know about the openstack/compute-api repo right? That's where the spec is housed13:16
annegentlecyeoh: the doc team doesn't write specs, the original v2 spec for Compute was written by Jorge Williams.13:16
*** eharney has joined #openstack-meeting13:17
*** eharney has quit IRC13:17
*** eharney has joined #openstack-meeting13:17
annegentlecyeoh: for sure, we definitely like what nova does for response/requests already, it's great13:17
cyeohannegentle: i haven't actually looked at it - I don't know much about the whole process except for what Tom was helped me understand :-)13:17
annegentlecyeoh: okay, yup, and I was on vacation last week13:17
*** writerDi_ has joined #openstack-meeting13:17
cyeohah I didn't realise that about the original V2 spec13:18
annegentlecyeoh: so the openstack/compute-api repo is specifically set up for governance by the nova core team with doc-core also having +2 privileges13:18
*** writerDi_ is now known as dianefleming13:18
annegentlecyeoh: but the openstack-api-site repo is where all the extensions are documentd13:18
annegentlecyeoh: and since compute is so extension heavy it seems out of balance13:18
annegentlecyeoh: but there is a pattern there :)13:18
annegentlecyeoh: just making sure you know the history13:18
annegentlecyeoh: the original v2 spec has WADL and XSDs that validate13:19
annegentlecyeoh: I don't get the sense that anyone's stepping up to do that for v313:19
annegentlecyeoh: and v2.0 Identity is the only other spec that had full WADL and XSD13:20
cyeohannegentle: ah yea I was kind of hoping that all we'd need to do is produce the api samples (plus a bit more if we can), but looks like it might be more required?13:20
cyeoh(we from the Nova side that is)13:20
*** bitcoinnn has joined #openstack-meeting13:20
bitcoinnntutorial - how to get free bitcoins daily - http://imagetwist.com/hen1q41kb9bu/bitcoin.jpg.html13:20
*** bitcoinnn has left #openstack-meeting13:20
cyeohand um, to be honest I'm really unfamiliar with WADL/XSD13:20
annegentlecyeoh: well I think nova should provide an app dev reference, also known as a spec13:20
annegentlecyeoh: yeah fair enough.13:20
annegentlecyeoh: other PTLs just write it all down in markdown in their project-api repo13:21
roadnickcyeoh:  If you are willing to do the coding, I can help you with WADL/XSD13:21
*** rods1 has joined #openstack-meeting13:21
annegentlecyeoh: the main thing you need to provide is enough info for an SDK dev to know how to update their code to fit v313:21
*** alexpilotti has joined #openstack-meeting13:21
annegentlecyeoh: WADL is a good step that way since we have tooling around it13:21
cyeohroadnick: thanks!13:22
annegentleroadnick: cool13:22
annegentleok can't really spend all the meeting on v3 but that should give you a good next step or two or three13:22
cyeohannegentle: ok. it sounds like I need to have a good look at  the openstack/compute-api repo13:22
cyeohto better scope out what we need to do13:22
sarobcyeoh: theres a guy on my team that wants to help on the API docs13:22
annegentlecyeoh: sounds good.13:22
* fifieldt senses an action item :)13:22
dianeflemingwhat was the topic? I came in late - regarding v3?13:23
annegentlesarob: that would be awesome you can tell we need it13:23
annegentledianefleming: yeah v3 compute13:23
dianeflemingthx13:23
cyeohsarob: that would be really helpful as we're very under resourced for this13:23
*** ayoung has quit IRC13:23
sarobcyeoh: no prob, ill put him in touch with you13:23
annegentle#action cyeoh to study openstack/compute-api for the v2 docs13:23
cyeohsarob: thx!13:24
annegentle#action roadnick to help with WADL for Compute v313:24
annegentle#action sarob to get cyeoh in touch with API docs volunteer13:24
*** topol has quit IRC13:24
*** ryanpetrello has quit IRC13:24
annegentleany more?13:24
annegentle#topic Install guide plan13:24
roadnickOn that, or in general?13:24
annegentleroadnick: open discussion will come13:24
*** ryanpetrello has joined #openstack-meeting13:24
annegentleshaunm needs hardware, requesting from Cisco13:24
annegentledoes anyone else have access to hardware that shaunm could use to test install instructions?13:25
annegentlevbox all the way down only goes so far :)13:25
koolhead17annegentle: i need HW too :)13:25
sarobannegentle: im working on getting public access hardware setup13:26
koolhead17especially for nova/quantum. Vbox covers rest13:26
annegentlesarob: ohhh cool13:26
sgordonyeah quantum is troublesome13:26
annegentlekoolhead17: yeah it's neutron that's the most difficult13:26
*** anteaya has joined #openstack-meeting13:26
sgordoneven with hardware it clashes with corporate network setups a bit13:26
annegentleshaunm has been using old laptops13:26
sarobannegentle: prim for rhok, but we could use too13:26
*** jecarey_ has joined #openstack-meeting13:26
koolhead17sgordon: true. corporate firewall :)13:26
annegentleI had always wished trystack could give access13:26
*** amytron has quit IRC13:27
sarobit may take a few months though13:27
annegentleanyway, it's a known difficulty with writing install docs13:27
annegentlewe'll keep trying13:27
koolhead17soren: we can use 2 test new release :)13:27
*** cp16net is now known as cp16net|away13:27
annegentledianefleming: I had another "User Guide status" topic on the agenda, but it was just holdover13:27
annegentledianefleming: do you want to give an update?13:27
*** egallen has joined #openstack-meeting13:28
dianeflemingok -13:28
annegentle#topic User Guide status13:28
annegentleok13:28
dianeflemingthe update is, I'm still working on the User Guide but got sidetracked on Identity v2.0 and v3 stuff -13:28
dianeflemingI hope to have a first draft of User guide ready for review by next Monday -13:28
dianeflemingI'll let everyone know by way of the docs d-list13:28
dianeflemingI'll point people to the review13:29
dianeflemingdoes that sound okay?13:29
*** mtreinish has joined #openstack-meeting13:29
annegentledianefleming: sounds good13:29
sgordonyup, excellent13:29
annegentleyeah v3 Identity also came out of the woodwork13:29
dianeflemingfollow-on to that is the admin user guide13:29
annegentledianefleming: ah yes13:29
koolhead17dianefleming: great13:29
annegentledianefleming: still think that's the way to go, "admin user guide" or do we just go with "admin guide?"13:29
annegentle(not that the title is crucial but...)13:30
roadnickgood question13:30
roadnickwell, its one book or two13:30
annegentletrying to determine whether we have an overarching like roadnick suggests13:30
dianeflemingi like the "end user guide" and "admin user guide" that we are using as a model13:30
roadnickand I do have updates on that...13:30
annegentleroadnick: sure13:30
roadnickI agree with diane on that; I think it's good to have those two13:30
dianeflemingoverarching?13:30
annegentleactually let me hijack the user guide topic to let you discuss admin user guide :)13:30
roadnickOK, but you hijacked it, not me. :)13:30
dianeflemingi haven't had time to look at your blueprint yet, nick13:30
annegentle#link https://blueprints.launchpad.net/openstack-manuals/+spec/modularize-admin-guide13:30
annegentle#link https://blueprints.launchpad.net/openstack-manuals/+spec/os-admin-docs13:31
roadnickRight.13:31
annegentle#topic Admin docs13:31
annegentleand hijacked! Thanks dianefleming13:31
*** dkliban_afk has joined #openstack-meeting13:31
roadnickSo Nermina Miller (who should be here) and I went through the current docs and reorganized them by concept.13:31
annegentleroadnick: you have the floor13:31
roadnickthank you, ma'am!13:32
dianefleminghere's the blueprint for admin user guide: https://wiki.openstack.org/wiki/Blueprint-os-user-docs#Blueprint_-_OpenStack_Admin_User_Guide13:32
roadnickThe idea was to break out of the usual way of thinking aobut it13:32
*** jmh_ has quit IRC13:32
roadnickand to think about it more like a book about it than a collection of instructions.13:32
nerminahello everyone13:33
dianefleminghi!13:33
* roadnick waves to Nermina13:33
slong_Hi13:33
*** egallen has quit IRC13:33
dianeflemingroadnick i looked at your blueprint - it looks like your idea is to single-source one to multiple books from one set of source files13:33
dianeflemingis that right?13:33
roadnickcorrect.13:33
roadnickwell, sort of13:33
dianeflemingauth 2.0 tried to do that and it had problems, but i can tell you what they were13:34
koolhead17does this also cover distro specific install instructions13:34
sgordondoes clouddoc-maven support docbook "sets" ?13:34
roadnickthe idea is to make it possible to keep the multiple books, but make it possible to bring them together13:34
roadnickdianefleming: that would be useful, thanks13:34
dianeflemingyou could have multiple book files - each one pulls in different common files13:34
roadnicksgordon: I don't know13:34
dianeflemingto create different books?13:34
sgordonright13:34
lorin1I do like the idea of presenting the books as a coherent set of manuals.13:34
sgordontypically that is how you pull multiple "books" together13:34
sgordonwe use it with publican but somewhat infrequently13:35
roadnickwell, I did a test doc that pulled together multiple books as a single book13:35
sarobthat would be cool for training too13:35
annegentlesgordon: I dont' know if the plugin supports sets but I'll take an action item to find out13:35
dianefleminghowever, i think there's a first step, which is to outline what would go into each "book" before deciding how to implement this13:35
roadnickwe will need a bit more work to get more granular in pulling -- say, XPointer rather than just a file13:35
annegentle#action anne to find out if our maven plugin supports sets13:35
dianeflemingwhat is a "set"?13:35
sgordondianefleming, yes - these only work well if the information architecture of each stands on its own13:35
roadnickdianefleming:  that's why I broke them out into two blueprints13:35
sgordonhttp://www.docbook.org/tdg/en/html/set.html13:35
roadnicksgordon: thanks, I'll have a look at that13:36
sgordonA Set is a collection of Books.13:36
sgordonSet is the very top of the DocBook structural hierarchy. There's nothing that contains a Set.13:36
sgordonis the main two things13:36
dianeflemingthanks13:36
sgordonother items are left up to the implementation13:36
dianeflemingso a set is a parent to a book?13:36
sgordonpublican for instance will pull books into a set even if they are from completely different source control repos13:36
sgordonyes13:36
roadnickso we have the blueprint that includes the TOC; if we can agree on that, then we can start figuring out what content exists and can be used "as-is" and what needs to be wrtten13:36
*** vijendar has joined #openstack-meeting13:36
annegentlekoolhead17: no an admin guide will not also cover distro specific install13:36
* fifieldt likes the idea, but notes that if we're doing anything 'comprehensive', it's probably going to land post-havana ...13:36
sgordonyou can use it to combine multiple books into a "megabook" for want of a better term13:36
roadnickwhat we do NOT plan to do is just assume that every book is pulled in wholesale.13:37
sgordonright13:37
koolhead17annegentle: cool13:37
roadnickEach project is an entity in and of itself; some books, as has been pointed out, are well maintained, some are not.13:37
annegentleI'm with fifieldt on scope13:37
roadnickSome will fit with this structure, some will not.13:37
*** michchap_ has quit IRC13:37
annegentleroadnick: your criteria for inclusion?13:37
roadnickI missed fifieldt's scope comment13:38
fifieldt* fifieldt likes the idea, but notes that if we're doing anything 'comprehensive', it's probably going to land post-havana ...13:38
annegentleroadnick: the timing of post-havana13:38
*** michchap has joined #openstack-meeting13:38
sgordonfor what it's worth summer is really wanting to get involved in this full time but we're looking to make sure there is a clear direction to follow here13:38
annegentleroadnick: we do have time (I think) for dianefleming (or I should ask dianefleming if that's accurate)13:38
fifieldtthis is refering to producing the actual guide -- I think we've already started on the modularity work with the various other restructure blueprints13:38
sgordon("this" being admin materials)13:38
roadnickI think that's fine13:38
annegentlesgordon: yes agreed13:38
koolhead17fifieldt: that also means we will need to add many new studd13:38
koolhead17*stuff13:38
fifieldtyes, that's the issue koolhead1713:38
dianeflemingstudds13:38
roadnickbut I don't think it would hurt to start now13:39
slong_Hadn't seen that you'd posted the blueprints riadnick, will view asap13:39
roadnickand try to land it as close to havana as possible13:39
sgordonspeak of the devil :)13:39
fifieldtto be honest, I think we already have too much work roadnick :)13:39
roadnickI will post the blueprints to the list; they were just finished13:39
koolhead17fifieldt: will that require us doc sprint every release for all these guides?13:39
annegentlewelcome slong_13:39
slong_O/13:40
annegentlekoolhead17: I'd like to talk about that in the Program discussion because yes, only a very few guides will be released at release time13:40
fifieldtkoolhead17, I'm just noting that we have a ton of restructure work to do before we can do mass content adds again :)13:40
roadnickfifieldt:  that's fine with me13:40
annegentlefifieldt: right13:40
fifieldtroadnick, I would be very happy to be wrong :)13:40
roadnick:)13:40
annegentlelet's keep talking becaue I think this is shaping us towards 2 more topics, the auto-gen and the Program...13:40
roadnickNermina has been working on bugs -- though we have some issues getting her connected that we need help wtih13:40
* koolhead17 is not intersted in re-writing same every release13:40
annegentle#topic Auto-generated configuration reference tables for milestone13:40
fifieldtmaybe we will just finish the restructure this month - we can try :)13:40
roadnickbut when she's done maybe she can help on that, and then when that's done we can start13:41
annegentleorignally we wanted to generate the config tables each milestone, if my memory serves13:41
fifieldtsounds correct :)13:41
annegentlewe do have the patch in review now13:41
annegentle#link https://review.openstack.org/#/c/35726/13:41
fifieldt#link https://wiki.openstack.org/wiki/Havana_Release_Schedule13:41
annegentlefifieldt: I haven't tried it again this morning to see if I can generate cinder13:41
fifieldtcode's not much different annegentle, need to look into it with sld :(13:41
lorin1There's a patch into keystone to actually add their doc strings.13:42
annegentlelorin1: ok13:42
fifieldtan important feature missing from the code right now (as noted by lorinh) is the ability to update the mapping files13:42
annegentlefifieldt: ok fair enough13:42
fifieldti.e. detect new options added13:42
fifieldtso you can add the categories just for that13:42
annegentlefifieldt: I think a good test will be to spin up a Jenkins slave and run it there13:42
fifieldtbut that's not too hard to do13:42
fifieldtsounds good to me13:42
annegentlefifieldt: they have a script that'll create a Jenkins slave13:42
annegentlefifieldt: ok cool, that's probably how I should've been testing already13:42
annegentlefifieldt: so are you still good with the shape of the config guide?13:43
fifieldtit should have worked - apologies it has been soo much trouble annegentle13:43
annegentlefifieldt: nah no worries13:43
annegentlefifieldt: testing is good for me!13:43
annegentlefifieldt: I like how the config guide is going13:43
fifieldtslowly crafting things13:43
fifieldtmodularising13:43
annegentleit's the admin guides that we're going to struggle with13:43
annegentleseems like anyway13:43
fifieldtI should show you some of the patches roadnick13:43
roadnicksure13:43
fifieldtsince they're examples of modularising13:44
fifieldtI'd hope you'd approve of13:44
fifieldt:)13:44
roadnick:)13:44
roadnickI'll learn something if nothing else13:44
*** michchap has quit IRC13:44
*** burt has joined #openstack-meeting13:44
annegentlefifieldt: so how will it work to update the tables?13:44
fifieldtif you can follow https://review.openstack.org/#/c/35027/, it's a few moves along those lines13:44
fifieldtannegentle, what needs to happen is13:44
fifieldt1. update mapping tables based on milestone code13:44
fifieldt2. run the tool over the code to generate new xml tables13:45
fifieldt3. submit a gerrit patch with the new xml tables13:45
fifieldtsteps 2/3 are the easy ones13:45
fifieldt1 is not too hard, if the code to make it easy is in place13:45
*** jmh_ has joined #openstack-meeting13:45
annegentlefifieldt: okay sounds good... wish I could run step 1 myself but oh well :)13:46
fifieldtapologies again13:46
fifieldtyou can assign it to me/sld and we'll get it done, if you like :)13:46
annegentlelorin1: were you able to get it to work?13:46
fifieldtI will also try and get the code working on some other environments13:46
lorin1I tried it with nova, and it generated the DocBook for me.13:46
annegentlefifieldt: yes, please run the tables -- we need to start editing the descripitions as some are quite crap. :)13:46
annegentlelorin1: ok I'll try that. Maybe it's cinder.13:46
fifieldtindeed - recall all - option strings are now edited in code, rather than in docs :)13:47
annegentlefifieldt: right... my thinking exactly, we need tons of time to get those patches reviewed and in13:47
annegentleok any questions on the config guide and autogen tables?13:47
annegentleslong_: the config guide might also be a good place to get started?13:48
annegentleslong_: if you study what fifieldt has been doing and it makes sense to do more patching, feel free to hop in13:48
slong_Sure!13:48
annegentleslong_: ok cool13:48
*** tomoe_ has quit IRC13:48
koolhead17dianefleming: good work with the docs. :)13:48
annegentle#topic Documentation is now a Program, needs leader and mission statement13:48
slong_Will have a chat with fifieldt13:48
fifieldtcheers slong_13:48
*** tomoe_ has joined #openstack-meeting13:48
dianeflemingthanks!13:48
annegentleso this is the good news out of last week's technical committee meeting13:49
annegentleDocumentation is now a Program13:49
koolhead17annegentle: o/13:49
annegentlekoolhead17: yeah13:49
fifieldtcongratulations :)13:49
roadnickyay!13:49
sarob:)13:49
koolhead17so finally i will become official OS contributor13:49
*** markpeek has joined #openstack-meeting13:49
annegentlekoolhead17: you were already but this move cements it13:49
annegentleWe need a name, acting PTL, and a Mission Statement.13:50
annegentleHere's what Monty has for Infrastructure.13:50
koolhead17sounds cool13:50
annegentle#link http://lists.openstack.org/pipermail/openstack-dev/2013-July/011471.html13:50
annegentleit's simple, and to the point13:50
lorin1annegentle: What are the implications of being a "Program"? Is there a page somewhere that describes this?13:50
annegentlelorin1: yes, it involes changes to the governance on the wiki, just a min.13:51
sgordonthey updated https://wiki.openstack.org/wiki/Governance/Foundation/TechnicalCommittee13:51
annegentle#link https://wiki.openstack.org/w/index.php?title=Governance%2FFoundation%2FTechnicalCommittee&diff=25309&oldid=2442913:51
annegentleyep, and that one shows the changes.13:51
annegentlelorin1: the essence is13:51
annegentleOpenStack "Programs" are efforts which are essential to the completion of the OpenStack project mission, which is ''to produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable''. Programs can create any code repository and produce any deliverable they deem necessary to achieve thei13:51
annegentler goals.13:51
sgordonthe bigger difference is for some other projects13:52
annegentlesorry for the big paste13:52
sgordonwhich didnt get ATC status13:52
sgordonautomatically13:52
annegentlesgordon: right13:52
annegentleand I like that we can create any repo we need to get the job done. Which we were doing already. but I like it spelled out13:52
slong_Thx for that clarification13:52
annegentleit does mean that documentation is part of the integrated release13:53
annegentleso we need to state which deliverables are part of that integrated release quite firmly.13:53
dianeflemingyes -13:53
fifieldtfun!13:53
annegentleand we'll need to redesign the docs.o.o page to reflect that integrated release13:53
koolhead17annegentle: cool13:53
*** dkranz has joined #openstack-meeting13:54
annegentleso it requires more focus I believe... not sure how that'll exactly happen though with book sprints and etc.13:54
annegentlemy idea is that we'll have at least install docs for the integrated release13:54
annegentleother ideas for scope on integrated release docs?13:54
*** amytron has joined #openstack-meeting13:54
koolhead17annegentle: but install doc will still take time from the day new release comes13:54
sarobannegentle: milestone deliverables now?13:54
sgordonannegentle, i think ideally install and user at least13:55
*** eharney has quit IRC13:55
*** amytron has quit IRC13:55
annegentlesarob: we don't do milesteon deliverables now13:55
annegentlesgordon: ah yes, user guides13:55
sgordonkoolhead17, i disagree - it shouldnt really13:55
fifieldt+113:55
sgordonwe have access to the milestone builds of the code to work against13:55
annegentlekoolhead17: I don't htink we have much choice in the matter13:55
sgordonfor *manual* install instructions anyway13:55
annegentlesgordon: but not packages13:55
sgordonsure13:55
annegentlesgordon: right :)13:55
*** amytron has joined #openstack-meeting13:55
sgordonbut as per my email yesterday i dont think that should be the focus13:56
annegentlesgordon: we've not documented a manual install13:56
* koolhead17 had his share in previous releases 2 achieve same13:56
*** eharney has joined #openstack-meeting13:56
*** eharney has quit IRC13:56
*** eharney has joined #openstack-meeting13:56
annegentleI'm hoping shaunm can document a manual install13:56
*** egallen has joined #openstack-meeting13:56
annegentlekoolhead17: true true13:56
* fifieldt feels that package managers have won the install debate long ago for many purposes13:56
sgordonyeah13:56
sgordonwhat is the state of debian packaging13:56
annegentlefifieldt: yep, too true13:56
*** schwicht has joined #openstack-meeting13:57
sgordoni know for RDO we are started to attempt havana nightlies *now*13:57
sgordon*starting13:57
koolhead17sgordon::P13:57
fifieldtniice13:57
annegentlesgordon: nice13:57
koolhead17for ubuntu can anyway get from testing repo13:57
annegentlenext steps, I'll draft up a mission statement and send to the docs mailing list13:57
sgordonhttp://repos.fedorapeople.org/repos/openstack/openstack-trunk/13:57
annegentledo we want me to be acting PTL for now? Guess I should ask that!13:57
fifieldtsounds good annegentle13:57
*** dkliban_afk is now known as dkliban13:58
fifieldtall hail annegentle13:58
sgordon+113:58
sarob+113:58
Daisyagree13:58
annegentleheh13:58
lorin1+113:58
koolhead17annegentle: +113:58
koolhead17:)13:58
slong_+q13:58
roadnick+1 of course!13:58
annegentleaw you do like me :)13:58
* roadnick though Anne was already the PTL13:58
dianeflemingannegentle: +113:58
slong_:) +113:58
annegentle#action anne to draft a Mission Statement for Documentation and send to docs mailing list13:58
annegentleroadnick: heh13:58
annegentleroadnick: for all intents and purposes!13:58
roadnick:)13:59
annegentleok any more questions on our new Program status?13:59
annegentleI do have to do a small happy dance on that, seems like a long time coming!13:59
annegentleVery excited about it.13:59
* fifieldt also dances13:59
annegentle#topic Bug report, DocImpact state13:59
*** thunquest has joined #openstack-meeting14:00
annegentlefifieldt has been doing awesome work keeping up14:00
annegentlefifieldt: and the bad times of manual bug movements are over!14:00
fifieldtit's much easier now :)14:00
* koolhead17 214:00
*** afazekas_ has quit IRC14:00
fifieldtalso, you would have noticed the spam reduction14:00
annegentlefifieldt: well you always made it look easy, sheesh14:00
annegentlefifieldt: yes, real discussions, woo!14:00
koolhead17fifieldt: :)14:00
fifieldt#link https://launchpad.net/openstack-manuals/+milestone/havana14:00
*** fnaval has joined #openstack-meeting14:01
fifieldtso if anyone feels like working on the ;confirmed bugs for havana, feel free14:01
annegentlefifieldt: I did move about half the blueprints off that page to reflect what I think is really going to happen14:01
fifieldtcheers14:01
annegentleslong_: that is another idea for you and other newcomers, pick up bugs14:01
koolhead17yes please especially pre essex14:01
koolhead17i would say14:01
annegentleslong_: I know some are intimidating but you definitely know how the life of a writer works I think :)14:01
slong_Yeah, was talking to sgordon about that.14:02
annegentleso my thinking on onboarding would be something like this:14:02
annegentle1. Go through Conventions and spell check a document.14:02
annegentle2. Pick up low-hanging-fruit bugs14:02
koolhead17ooh BTW B1 for havana has landed in ubuntu repo as well https://wiki.ubuntu.com/ServerTeam/CloudArchive#Havana14:02
annegentle3. Pick up harder bugs14:02
annegentle4. Start really writing on the restructure stuff.14:02
annegentledoes that make sense? any other ideas?14:03
annegentleI feel it's too tough to ask newcomers to skip to 4.14:03
fifieldtI'd also suggest: keep in touch with others during the process14:03
sgordoni think from my pov my concern is investing effort in content that may be obliterated as a result of the restructure14:03
fifieldtwe're here to help :)14:03
sgordonit is pretty clear at some point there is going to need to be some culling of content to make the whole thing manageable14:04
annegentlesgordon: absolutely a valid concern... but with merging and stuff, content doesn't just get obliterated...14:04
koolhead17annegentle: also add get a core from every project involved with us14:04
koolhead17:)14:04
annegentlesgordon: at least I don't think so14:04
fifieldtso far I've been 'splitting' content, rather than obliterating14:04
annegentlesarob: koolhead17 reminds me that the timing is probably right now that programs are established to ask for a doc rep14:04
roadnicksgordon:  I think that until the bugs are all squashed, we can't really do much of the restructuring anyway14:04
sgordonroadnick, i dont think that is realistic14:04
annegentleroadnick: oh you don't mean that :)14:04
sgordonotherwise we will never restructure14:04
sgordonit's a vicious cycle to get stuck in14:05
annegentlesgordon: yeah I'm never deleting content so far14:05
annegentlesgordon: right agreed14:05
sarobannegentle:doc rep?14:05
*** lpabon has joined #openstack-meeting14:05
roadnicksgordon/annegentle:  well, not completely!14:05
annegentlesarob: weren't you saying we need to make each project have a doc representative14:05
*** afazekas_ has joined #openstack-meeting14:05
slong_I am so just listening at this point.14:05
roadnickI just mean that we need to make sure that the bugs DO get squashed for release.14:05
annegentleslong_: :)14:05
annegentleslong_: this is quite active for a doc team meeting14:05
annegentleoh crum and we've gone over time14:06
slong_Exciting..14:06
annegentle#topic open discussion14:06
sarobannegentle: the pdl idea, right14:06
annegentleat least want to open it up!14:06
annegentleI have 2 bits to share14:06
annegentleOne is, this week there's going to be an annoucement about  a travel support program for the Icehouse summit14:06
*** mrodden has joined #openstack-meeting14:06
sgordonannegentle, maybe i am misunderstanding roadnick's proposal for admin materials but it sounds like an implicit part of it is that not all content from existing admin guides would necessarily be in the restructured ones14:06
* fifieldt is going to brush his teeth, hoping the water is back on, back in 2min14:06
annegentlesgordon: ah right14:06
sgordonand i am onboard with that if it would result in a more manageable and *correct* guide14:06
roadnicktrue14:06
sarobannegentle: yes, I think we should have an formal doc position in each project14:06
roadnickbut I think that maybe the first step...14:07
annegentlesgordon: So far I've seen a need to for example, delete install info from the Networking Admin Guide.14:07
roadnickis to go through and mark parts that may not make it into the restructure document.14:07
annegentleso yeah, there are examples where deletion is needed14:07
sarobannegentle: PDL is what we came up with14:07
*** cliu has quit IRC14:07
*** egallen has quit IRC14:07
annegentlesarob: yeah Projet Doc Lead14:07
roadnickbecause if the restructure doesn't happen until post-havana, those parts still have to be right when Havana is released14:07
* annegentle can't spell14:07
roadnickbut at least you know where to NOT sweat blood14:07
annegentleroadnick: I think realistically, some guides won't be updated for havanah14:07
roadnickright14:08
annegentleroadnick: but we need to ensure they're not marked as havana either :)14:08
annegentleroadnick: that's the tricky bit, making a "release" doc site14:08
annegentlesomething we havent' done before14:08
annegentlewe just released everything14:08
roadnickHow about this:14:08
roadnickHow about if we concentrate on an outline that shows what pieces WILL get carried over, so that we know that we need to focus there.  But...14:09
* fifieldt back14:09
roadnickwe won't worry about writing the rest until everything else is done.14:09
annegentlefifieldt: water out? Eek.14:09
koolhead17roadnick: i read modular somewhere14:09
fifieldtyeah, they're trying to fix the exploding pipes14:09
roadnickthis way the "fluff" will be a known quantity, addressing sgordon's concerns.14:09
annegentle#action anne to float the Project Doc Lead idea to mailing list14:09
koolhead17that will take care of it i guess or was it for the BOOKS14:09
annegentlefifieldt: yikes14:09
annegentleroadnick: so dianefleming's outline isn't wha tyou're thinking of, and you have another?14:10
DaisyHi, I'd like to discuss the publish of operation guide in Japnese and Chinese to the doc website.14:10
*** afazekas_ has quit IRC14:10
roadnickkoolhead17:  Yes.  that's correct.  the overall book will be made from modular pieces of other books.14:10
annegentleDaisy: yes, go ahead14:10
fifieldtannegentle, my life: http://www.goodreads.com/book/show/70256.High_Rise14:10
roadnickDianefleming has the admin user guide, which I think we should keep in addition to this.14:10
annegentleroadnick: let's take the other discussion about admin guides to #openstack-docs so we can finish out the meeting14:10
roadnickMaybe this is more of an Admin Reference Guide.,14:10
annegentleroadnick: ooo14:10
annegentleok14:10
sgordonat this stage i like diane's plan14:11
roadnickannegentle:  agreed.14:11
sgordonbut perhaps that is because i can see it clearly14:11
dianeflemingroadnick - what is more of an admin reference guide?14:11
sgordon:)14:11
DaisySo the translation of Japanese are completed finished in Transifex. The Chinese in Transifex is not, but I'm sure the translation are finished but not in po format.14:11
annegentleDaisy: sorry to make you wait so long14:11
Daisywe are a big team and with a big mission.14:11
Daisyit's all right.14:11
annegentleDaisy: wow that's fantastic14:11
roadnickdianefleming:  the "comprehensive" Administration Guide14:11
roadnickDaisy:  great!14:11
dianeflemingok!14:11
*** egallen has joined #openstack-meeting14:11
Daisyso I want to try to publish operation guide in Japanese as the first case.14:11
annegentleDaisy: so you need a way to publish14:12
Daisyas the first test case.14:12
fifieldtDaisy, what do we need to do to get the Japanese guide on docs.openstack.org ?14:12
annegentleDaisy: the docs landing page needs even more work14:12
Daisyyes. I need to understand the structure of the website, and where to put the Japnese version.14:12
fifieldtdo you want me to help run through the various components14:12
fifieldtsuch as the maven build system?14:12
annegentleDaisy: a couple of thoughts... the index.html lives in openstack-manuals in the www directory14:12
DaisyI think we can brainstorming.14:12
*** psedlak has quit IRC14:12
annegentleDaisy: we have a drop down now for each release14:13
*** otherwiseguy has quit IRC14:13
annegentleDaisy: when you click More Releases... you can see the drop down14:13
DaisyI know the drop down.14:13
annegentleDaisy: but is that too hidden?14:13
*** otherwiseguy has joined #openstack-meeting14:13
annegentleis auto-detect yucky? as in, know what language their browser is and present a different landing page?14:14
Daisyit's ok. I can see the drop down.14:14
annegentlewe could add a row for language choices at the top?14:14
Daisyso maybe we want such a link: http://docs.openstack.org/jp/ ?14:14
Daisyor http://docs.openstack.org/folsom/jp?14:14
annegentlehonestly I might want to get Todd Morey or a designer at the Foundation involved to redesign the landing page?14:14
fifieldt(just on auto-detect: I know some people take issue with it, annegentle, but I'm not sure what the general consensus 'round the net is)14:15
annegentleDaisy: maybe... that would work too, and just maintain them by hand in www/jp/ www/zh?14:15
annegentlefifieldt: yeah I hear mixed feedback on auto-detect14:15
*** michchap has joined #openstack-meeting14:15
Daisywe can add the drop down when the link is ready.14:15
annegentleHow about this -- fifieldt can you ask Mark/Todd/others if we can get a designer to help with the landing page for 1. translation 2. releases14:16
*** egallen has quit IRC14:16
annegentlethen in the meantime we do something like what Daisy suggests, with docs.openstack.org/jp14:16
fifieldtSure, I'll do that14:16
*** jcoufal has quit IRC14:16
fifieldtmaybe even some of the horizon UX folks might be interested?14:16
Daisyannegentle: do you want index page in different languages too?14:16
annegentle#action fifieldt to see design resources for the docs.openstack.org landing page for 1. translation 2. releases14:17
annegentleDaisy: if possible, yes!14:17
Daisyannegentle: I mean, for example, if users open http://docs.openstack.org/jp, he will see all jp characters and he will see the availabe jp documents.14:17
annegentleDaisy: yes, that's what I'm thinking...14:17
annegentleDaisy: and a link to transifex too possibly14:17
*** egallen has joined #openstack-meeting14:17
annegentleOk good thing no one needs this meeting room...14:17
annegentleI'm going to end the logging14:17
annegentlethanks everyone!14:17
annegentle#endmeeting14:18
fifieldtI might have to head off all - got another meeting in 7.25 hours and need to get some sleep before then :)14:18
openstackMeeting ended Tue Jul  9 14:18:00 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:18
openstackMinutes:        http://eavesdrop.openstack.org/meetings/doc_team_meeting/2013/doc_team_meeting.2013-07-09-13.01.html14:18
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/doc_team_meeting/2013/doc_team_meeting.2013-07-09-13.01.txt14:18
sarob:)14:18
openstackLog:            http://eavesdrop.openstack.org/meetings/doc_team_meeting/2013/doc_team_meeting.2013-07-09-13.01.log.html14:18
annegentlefifieldt: for sure!14:18
fifieldtjust assign all the action items to me14:18
fifieldtI'll read the log :)14:18
*** AJaeger has left #openstack-meeting14:18
slong_Thx!14:18
annegentleDaisy: do you like the all JP landing apge idea?14:18
annegentleDaisy: seems doable14:18
Daisyannegentle: so I need to understand how to create the index page in http://docs.openstack.org/jp and how to publish http://docs.openstack.org/jp.14:18
annegentleDaisy: ok, so you would submit a patch to openstack-manuals14:19
annegentleDaisy: updating https://github.com/openstack/openstack-manuals/tree/master/www14:19
annegentleput a jp folder in there with an index.html in it in Japanese14:19
Daisyis http://docs.openstack.org/folsom/ a folder in www?14:19
annegentleDaisy: then I think the build job already gets every folder under www14:19
annegentleDaisy: yes14:19
*** slong_ has quit IRC14:19
annegentlehttps://github.com/openstack/openstack-manuals/tree/master/www/folsom14:20
annegentleDaisy: but only the index.html lives there14:20
Daisyright.14:20
*** ivasev has joined #openstack-meeting14:20
Daisyannegentle: I know how to add index page now.14:20
Daisyannegentle: can you tell me how to publish documents?14:20
annegentleDaisy: so the build job copies all files from www I believe... let me find it14:21
Daisyannegentle: I think the same.14:21
annegentleDaisy: line 332 of https://github.com/openstack-infra/config/blob/master/modules/openstack_project/files/jenkins_job_builder/config/manuals.yaml14:21
annegentleDaisy: so you don't have to change the build job even14:21
annegentleDaisy: it'll just pick them up14:22
*** dkliban is now known as dkliban_brb14:22
*** bdperkin has quit IRC14:22
*** stevemar has joined #openstack-meeting14:22
Daisyannegentle: ok. I will take a look at the links.14:22
annegentleLooking forward to the patch!14:22
DaisyThanks, annegentle .14:22
*** ayoung has joined #openstack-meeting14:22
annegentleDaisy: thank you!14:22
*** fifieldt has quit IRC14:22
*** dkliban_brb is now known as dkliban\14:22
*** dkliban\ is now known as dkliban14:22
Daisyannegentle: congratulations for the new program of documentation !14:22
*** tedross has quit IRC14:23
*** bdperkin has joined #openstack-meeting14:23
*** terriyu has joined #openstack-meeting14:23
roadnickthanks, all!14:23
*** nermina has quit IRC14:24
*** koolhead17 has left #openstack-meeting14:24
*** koolhead17 has quit IRC14:24
*** Daisy has quit IRC14:25
*** tedross has joined #openstack-meeting14:25
*** woodspa has joined #openstack-meeting14:25
*** michchap has quit IRC14:26
*** lorin1 has left #openstack-meeting14:29
*** fnaval has quit IRC14:32
*** fmanco has joined #openstack-meeting14:32
*** fmanco has left #openstack-meeting14:32
*** fmanco has joined #openstack-meeting14:32
*** tomoe_ has quit IRC14:33
*** tomoe_ has joined #openstack-meeting14:33
*** dcramer_ has joined #openstack-meeting14:34
*** tkammer has quit IRC14:38
*** tkammer has joined #openstack-meeting14:38
*** terriyu has quit IRC14:38
*** terriyu has joined #openstack-meeting14:41
*** haomaiwang has quit IRC14:44
*** tomoe_ has quit IRC14:45
*** cp16net|away is now known as cp16net14:45
*** dianefleming has quit IRC14:46
*** jmh_ has quit IRC14:47
*** topol has joined #openstack-meeting14:52
*** marun has joined #openstack-meeting14:53
*** michchap has joined #openstack-meeting14:53
*** fnaval has joined #openstack-meeting14:55
*** dripton__ is now known as dripton14:56
*** david-lyle has joined #openstack-meeting14:56
*** Mandell has joined #openstack-meeting14:56
*** llu-laptop has joined #openstack-meeting14:57
*** jtomasek has quit IRC14:59
*** jgallard has joined #openstack-meeting14:59
n0ano#startmeeting scheduler15:00
openstackMeeting started Tue Jul  9 15:00:19 2013 UTC.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
openstackThe meeting name has been set to 'scheduler'15:00
llu-laptopo/15:00
*** zehicle_at_dell has quit IRC15:00
n0anoshow of hands, anyone want to talk about the scheduler?15:00
*** sgordon has left #openstack-meeting15:00
jgallard\o15:00
alaskio/15:01
n0ano#topic code re-factoring15:02
n0anoI15:02
n0anoI've seen some emails on this subject but I'm not up on it, does anyone know what the real issue here is?15:03
*** SergeyLukjanov has quit IRC15:03
*** jhenner has quit IRC15:03
*** amytron has quit IRC15:03
*** mkollaro has quit IRC15:03
*** amytron_ has joined #openstack-meeting15:03
*** tanisdl has joined #openstack-meeting15:03
alaskiMaybe there's more than one effort, but I know about https://blueprints.launchpad.net/nova/+spec/query-scheduler15:04
jgallardthis is related to move some common part of scheduler for nova and cinder code into oslo?15:04
*** jhenner has joined #openstack-meeting15:04
*** mkollaro has joined #openstack-meeting15:04
*** jhenner is now known as jhenner|mtg15:04
*** michchap has quit IRC15:04
*** dkranz has quit IRC15:05
n0anoAah, common code between nova & cinder, that makes more sense (I had problems with duplicated code inside the scheduler itself)15:05
n0anogiven that there is some filtering/weighting going on in Cinder this sounds like a good idea, I guess it's just down to the implementation details15:06
*** jgallard has quit IRC15:07
*** jgallard has joined #openstack-meeting15:07
n0anogiven I don't see any architectural issues here I say we just review the code changes as they come by15:07
jgallardfrom my understanding yes: it's mainly related to implementation issue15:07
llu-laptopwhat are the common things in detail between cinder&nova scheduler? filter/weight framework?15:07
*** shaunm has left #openstack-meeting15:08
n0anollu-laptop, yes, I believe that's where the overlap occurs15:08
jgallardhttps://blueprints.launchpad.net/oslo/+spec/oslo-scheduler15:08
jgallardthis is the BP related to what we are discussing15:09
*** belmoreira has joined #openstack-meeting15:09
*** jcoufal has joined #openstack-meeting15:10
n0anolooks like mainly specific classes that have some overlap, not a complete framework issue.15:10
*** zehicle_at_dell has joined #openstack-meeting15:10
*** mrodden has quit IRC15:10
belmoreirasorry, late for the meeting.15:11
n0anogiven the specificity (I think that's a word) of the classes I wonder how much overlap there exists in the rest of nova/cinder/swift/glance15:11
n0anoprobably an issue for someone who gets motivated to do a complete review of the system.15:12
*** sleepsonthefloor has quit IRC15:12
*** PhilDay has joined #openstack-meeting15:12
*** dhellmann_ is now known as dhellmann15:12
n0anoanyway, I think this problem is well in hand, let's move on15:13
n0ano#topic volume affinity filter15:13
n0anojgallard, I think you've been involved in the thread, can you expand on this?15:13
jgallardyes of course15:14
jgallardhttps://review.openstack.org/#/c/29343/15:14
*** Fdot has joined #openstack-meeting15:14
*** haomaiwang has joined #openstack-meeting15:14
n0anoseems to me the biggest issue is are they talking about a filter or a weigh (I've seen that confusion in other contexts)15:14
jgallardthe goal of the patch is to allow (thanks to a hint) to place an instance on the same host of a volume15:15
jgallardand yes15:15
jgallardas you just said, the main issue is about filter and/or weigh function15:15
jgallardcurrently the patch implements a filter15:15
n0anothat seems rather restrictive, what's the view on changing to a weight?15:16
*** sarob has quit IRC15:16
jgallardyes the filter is restricitve15:16
jgallardbut it would have some interesting use cases15:17
*** sarob has joined #openstack-meeting15:17
jgallardregarding the weigh15:17
jgallardI didn't look at the code, however15:17
*** kebray has joined #openstack-meeting15:17
*** Mandell has quit IRC15:17
jgallardthe use of a weigh function is more complicated, because, the scheduler has to find himself from wich volume the instance has to be placed15:17
jgallard(no possibility to use an hint)15:18
n0anoI don't see the use cases for the filter, that wouldn't be a hint either (it would be a requirement)15:18
jgallardbut it seems that from a technical point of view the dic containing the host of the volume is not directly accessible from the scheduler15:18
jgallardfor the filter, maybe you can imagine a case where, the placement for high performance is mandatory15:19
jgallardif you don't want besteffort15:19
jgallardwhy not15:19
*** dkranz has joined #openstack-meeting15:20
jgallardhttp://lists.openstack.org/pipermail/openstack-dev/2013-July/011329.html15:20
jgallardfor those who are interesting to participate on the discussion15:20
*** sarob has quit IRC15:21
n0anohmm, a point, I wonder if that means we need both a filter and a weight or would that be overkill15:21
*** lcheng2 has joined #openstack-meeting15:22
jgallardif both of them are providing, I think the administrator will have more flexibility to configure its cloud15:22
*** mrodden has joined #openstack-meeting15:23
jgallardthe admin can use the filter (very restrictive case) or the weigh function (no restriction, best-effort mode)15:23
*** stevemar has quit IRC15:23
n0anoyeah but would it be overly complex and provide a framework that isn't actually used in practice15:23
jgallardthe main issue with the filter is that it "break" the cloud philosophy : the placement is not hidden to the user15:23
*** Guest39539 is now known as med_15:24
*** SergeyLukjanov has joined #openstack-meeting15:24
*** haomaiwang has quit IRC15:24
jgallardn0ano, sorry, you are talking about the filter or the weigh ?15:24
n0anojgallard, I'm talking about providing both15:24
jgallardah ok15:24
n0anoit would be simpler to provide just a weight and, if that satisfies 99% of the actual uses, that would be sufficient15:25
PhilDayNot sure I agree about breaking cloud philosophy - we already have affinity filters15:25
n0anoPhilDay, +1 (you typed faster than me :-)15:25
*** spzala has joined #openstack-meeting15:25
*** cliu has joined #openstack-meeting15:25
jgallardthe issue is that, in cloud philosophy, you ask for a resource and you have it "in all cases"15:26
jgallardbut with this kind of filter, you may not have any resources at all15:26
PhilDayThe general case though should be to be able to express some form or proximity - there are configurtaions where volume is never on the same host, but it could be closer on the network15:26
jgallardbut again, I think this is more related to the use case the admin wants to do15:26
jgallardPhilDay, +115:27
jgallardbut this is not possible to achieve with the filter15:27
jgallardit's more related to the weigh function15:27
n0anohence my preference would be to provide a weight15:27
PhilDayNothing stopping someone having a purely private filter or weighteing function that they configure in -  but to be accepted into the core set it should be a bit more general15:28
*** kebray has quit IRC15:29
jgallardok, so may be we can intervene on the mailing list?15:30
n0anoI think a volume weight would be general enough to be part of the core, while the volume filter might be more appropriate as a private function.15:30
*** yaguang has quit IRC15:30
*** IlyaE has joined #openstack-meeting15:30
*** michchap has joined #openstack-meeting15:30
jgallardn0ano, PhilDay, yes probably15:31
*** vijendar has quit IRC15:32
n0anojgallard, responding to the email thread is a good idea, nothing wrong with getting opinions out there15:32
jgallardyes of course15:32
n0anoOK, moving on15:33
n0ano#topic follow ups on the scheduler BPs15:33
n0anoAnything on the outstanding BPs anyone wants to raise?15:33
*** jcoufal has quit IRC15:33
n0anoHearing silence15:34
n0ano#topic opens15:35
n0anoAny opens for today?15:35
*** marun has quit IRC15:35
PhilDayScheduler hints APi is looking for reviewers:  https://review.openstack.org/#/c/34291/15:35
belmoreiraI started the implementation of multiple default av_zones15:35
n0anobelmoreira, cool, any major difficulties yet?15:36
belmoreiraas discussed some weeks ago. Hope to have the first implementation soon.15:36
PhilDayHoping to get started on the whole host allocation real soon now ;-)15:36
jgallardPhilDay, great!15:36
belmoreiran0ano: not yet.15:36
*** egallen has quit IRC15:37
n0anoOK, sounds like we've got some coding to accomplish - yea!15:37
n0anoTnx everyone, I think we've run down so I'll close the meeting for today15:39
*** PhilDay has quit IRC15:39
n0ano#endmeeting15:39
jgallardok thanks to all!15:39
openstackMeeting ended Tue Jul  9 15:39:21 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:39
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-07-09-15.00.html15:39
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-07-09-15.00.txt15:39
openstackLog:            http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-07-09-15.00.log.html15:39
*** llu-laptop|2 has joined #openstack-meeting15:39
*** llu-laptop has quit IRC15:41
*** amytron_ has quit IRC15:41
*** amytron has joined #openstack-meeting15:42
*** michchap has quit IRC15:42
*** yaguang has joined #openstack-meeting15:43
*** kebray has joined #openstack-meeting15:44
*** rongze1 has joined #openstack-meeting15:45
*** egallen has joined #openstack-meeting15:45
*** rongze has quit IRC15:46
*** martine_ has quit IRC15:46
*** kebray has quit IRC15:46
*** cody-somerville has joined #openstack-meeting15:46
*** cody-somerville has joined #openstack-meeting15:46
*** Fdot has quit IRC15:47
*** jgallard has quit IRC15:47
*** epim has joined #openstack-meeting15:47
*** yaguang has quit IRC15:48
*** vijendar has joined #openstack-meeting15:49
*** tanisdl has quit IRC15:50
*** llu-laptop|2 has quit IRC15:50
*** amytron has quit IRC15:51
*** amytron has joined #openstack-meeting15:51
*** eharney has quit IRC15:53
*** belmoreira has quit IRC15:53
*** luis_fdez has joined #openstack-meeting15:54
*** hanrahat has joined #openstack-meeting15:54
*** shmcfarl has joined #openstack-meeting15:56
*** tanisdl has joined #openstack-meeting15:57
*** hemna_ has joined #openstack-meeting15:59
*** boris-42 has quit IRC16:00
primeministerp#startmeeting hyper-v16:00
openstackMeeting started Tue Jul  9 16:00:30 2013 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
openstackThe meeting name has been set to 'hyper_v'16:00
primeministerphi everyone16:00
luis_fdezhi16:00
primeministerpit's been a while16:00
primeministerphey luis16:00
*** dkranz has quit IRC16:00
primeministerplet's wait for the others16:01
primeministerpI don't see alex here yet16:01
luis_fdezok16:01
primeministerpluis_fdez: so let's start w/ the puppet modules while waiting16:02
luis_fdezok16:02
primeministerp#topic hyper-v puppet modules16:02
schwichtprimeministerp: hi everyone16:02
*** ociuhandu has joined #openstack-meeting16:02
luis_fdezhave you looked at the last pull requrest?16:02
primeministerpi renamed the module and merged your pull requests last night16:02
*** jrodom has joined #openstack-meeting16:02
primeministerpluis_fdez: I haven't looked since last night16:02
primeministerpluis_fdez: you had 216:02
*** sleepsonthefloor has joined #openstack-meeting16:03
primeministerpluis_fdez: i merged them both16:03
primeministerpthe changes to the vswitch and the rename16:03
luis_fdezyes16:03
primeministerpfor module conformance16:03
*** tkammer has quit IRC16:03
primeministerpI also renamed the project16:03
primeministerpto match16:03
luis_fdezperfect16:03
primeministerpluis_fdez: so go ahead and add your other changes16:03
primeministerpschwicht: Hi frank16:03
primeministerpociuhandu: hi tavi16:04
luis_fdezok, one of the pull request is just a refactoring creating a new hyper-v.pp class16:04
alexpilottihi guys16:04
primeministerpluis_fdez: perfect16:04
luis_fdezto extract the installation of Hyper-V and configuration .... it can be the future init.pp of the hyper-v module16:04
primeministerpluis_fdez: i was thinking we need to move some into general windows16:04
primeministerpclass as well16:04
alexpilottisorry me and Tavi were in a meeting16:04
primeministerpalexpilotti: no problem16:04
luis_fdezthe other one is a proofofconcetp? hehe of how the nova_config type looks as in nova puppetlabs... but it adds one dependency16:04
zehicleHello!16:04
ociuhanduhi all16:05
*** markwash has quit IRC16:05
primeministerpluis_fdez: I need to add a puppetfile for dependencies16:05
luis_fdez((last time we talked about it I was wrong saying that it wont add new dependency))16:05
primeministerpluis_fdez: I don't mind adding dependencies16:05
luis_fdezalso.. I extracted windows_feature as a separate define16:05
primeministerpthen we can reuse16:05
luis_fdezto make the code cleaner and also follow the style rules16:06
primeministerpluis_fdez: that works too, because if using hyper-v server the role is already there16:06
*** yaguang has joined #openstack-meeting16:06
*** marun has joined #openstack-meeting16:06
primeministerpluis_fdez: perfect16:06
primeministerpluis_fdez: is there anything else we need to discuss?16:06
luis_fdeznow... I'm looking to the download question and.... opened to new proposals... can i give you a hand on something related with python?16:07
*** eharney has joined #openstack-meeting16:07
*** eharney has quit IRC16:07
*** eharney has joined #openstack-meeting16:07
alexpilottiluis_fdez: any BP you'd like to work on? :-)16:07
primeministerpluis_fdez: it needs to be there16:08
luis_fdezI'll take a look... now... im a puppet man... i have to revisit my compute driver profile :)16:08
primeministerpat least for the start16:08
primeministerpor16:08
primeministerpwe have it as a seed16:08
primeministerpalso16:08
primeministerponce we move to all source16:08
primeministerpwe won't necessarily need it16:08
primeministerpbc we can move to a git pull16:08
primeministerpfor all that16:08
primeministerphowever16:08
primeministerpif we're going to use the public bins16:08
*** michchap has joined #openstack-meeting16:09
primeministerpwe need to have a way to pull them16:09
primeministerpthat's my 2c16:10
luis_fdezyeps, I think for the start the public bins is the best option16:10
primeministerpok16:10
*** colinmcnamara has joined #openstack-meeting16:10
primeministerplet's move on topic wise16:10
luis_fdezdo you have changes to be committed or can I changes thinks on the python part?16:10
primeministerpalexpilotti: ready16:10
luis_fdezpasdfadf16:11
primeministerpluis_fdez: no I've been working on the provisioning side16:11
*** bdpayne has joined #openstack-meeting16:11
primeministerphad some stuff to clean up16:11
alexpilottisure16:11
primeministerpalexpilotti: where do we want to start?16:11
primeministerpwmiv2?16:11
alexpilottiyep16:11
primeministerp#topic wmiv216:11
alexpilottiso 2012R2 Preview is publicly avlaible16:11
primeministerphaha16:11
primeministerpwhy yes it is16:12
alexpilottiand the V1 namespace is gone :-)16:12
*** mkollaro has quit IRC16:12
primeministerpwhy yes it is16:12
primeministerp;)16:12
*** jhenner|mtg has quit IRC16:12
alexpilottiso it's time to do some testing of Havana on 2012R216:12
*** jhenner has joined #openstack-meeting16:12
alexpilottito get there, the first BP that we are releasing this week is teh WMIV2 one16:12
primeministerpis the wmiv2 code upstream16:13
primeministerpperfect16:13
alexpilottiprimeministerp: ?16:13
alexpilottiok16:13
primeministerpyou answered my question16:13
alexpilottithanks to the Grizzly refactoring it was a fairly contained work16:13
*** martine has joined #openstack-meeting16:13
alexpilottia factory is instantiating the relevant utils classes based on the OS: < 2012: V1, >= 2012 V216:14
*** martine is now known as Guest5445516:14
alexpilottia separate pachset will be released for the Neutron agent16:14
primeministerpawesome16:14
schwichtnice work16:14
primeministerpin the same timeframe?16:14
alexpilottione that's in place, we'll need also to update the installer16:14
*** dkranz has joined #openstack-meeting16:15
*** Guest54455 is now known as martine_16:15
alexpilottiI'd love to get both (Nova, Quantum) in for H216:15
*** stevemar has joined #openstack-meeting16:15
primeministerpok16:15
primeministerpthat would be great16:15
alexpilottiwe'll need a lot of help in testing16:15
primeministerpschwicht: .....16:15
primeministerpschwicht: will your folks be able to take a look16:16
schwichtprimeministerp: we'll need to chat off line16:16
primeministerpschwicht: np16:16
alexpilottione of the reasons I want to have those bits out early is that they replace the layer that interacts with the OS16:16
alexpilottiwhich cannot be tested with unit testing, only system / integration testing16:16
primeministerpalexpilotti: i'll be able to try them tomorrow16:17
alexpilottiand sicne we need a CI for that, the only alternative is having some hands doing it ;-)16:17
schwichtis the testing the WMIv2 testing?16:17
primeministerpalexpilotti: yes I know16:17
alexpilottischwicht: yes16:17
alexpilottischwicht: basically doing a lot of regression testing16:17
schwichtwe will have both funtional (IBM speak IVT) and SVT testing for the base stuff16:17
alexpilottischwicht: great tx!16:18
schwichthowever we are investigating the scope of the testing atm16:18
primeministerpgotcha16:18
*** gyee has joined #openstack-meeting16:19
*** koolhead17 has joined #openstack-meeting16:19
primeministerpso next topic?16:19
alexpilottiDynamic memory16:19
primeministerpsure16:19
primeministerp#topic dynamic memory16:19
*** haomaiwang has joined #openstack-meeting16:20
*** nicolae_ has quit IRC16:20
alexpilottiWe have this patch ready as well, I'm reviewing it internally, but is basically ready for public review16:20
primeministerpalexpilotti: i'm assuming you've completed it as well?16:20
*** michchap has quit IRC16:20
alexpilottiwe have 2 new options:16:20
alexpilottione to enable / disable the feature16:20
alexpilottiand one for the overcomit ratio16:21
alexpilottifor teh second one, we just reused the option coming from teh scheduler filter16:21
schwichtis the ratio part of the flavor ?16:21
alexpilottino, it's a configuration in the nova scheduler16:22
schwichtoh16:22
alexpilottidefault's to 1.516:22
alexpilottiso if the host that 100GB memory16:22
schwichtunderstood16:22
alexpilottiit overcommits to 150GB16:22
schwichtI was hoping we can do that for each instance16:22
alexpilottion HyperV this was not possible before16:22
schwichtand that I thought we would drive with a flavor attribute16:22
*** jcoufal has joined #openstack-meeting16:22
alexpilottias w/o dynamic memory there's no balooning and the mem is allocated 1:116:23
schwichtQoS (and overcommit are instance attributes)16:23
*** Fdot has joined #openstack-meeting16:23
schwichtalexpilotti: understood16:23
schwichtwe do that on other hypervisors ...16:23
primeministerpalexpilotti: anything else on the topic?16:24
alexpilottithe reason for reusing the same option is that they have anyway to match16:24
alexpilottinot really16:24
alexpilottionly one question16:24
schwichtsame page sharing is not a feature supported, right?16:24
alexpilottishould we default to true or false on enabling this feature?16:24
*** haomaiwang has quit IRC16:25
alexpilottischwicht: not on Hyper-V16:25
schwichtk16:25
alexpilottischwicht: it's not efficient with SLAT16:25
*** mkollaro has joined #openstack-meeting16:25
alexpilottischwicht: unlike e.g. ESXi16:25
schwichtyep16:25
schwichtI was thinking at KSM ..16:25
schwichtbut that is ok16:25
schwichtopenstack can not offer more than the base hypervisor16:26
alexpilottican you guys please vote on the above question? :-)16:26
alexpilotti> should we default to true or false on enabling this feature?16:26
primeministerpI would say false16:26
alexpilottischwicht: ?16:26
alexpilottipnavarro is not joining us today?16:27
schwichtVMware uses false ...16:27
alexpilottischwicht: cool, consistency is important16:27
alexpilottiI vote for false as well16:27
alexpilottiIt's a risky feature16:27
primeministerpagreed16:28
schwichtwhat happens on overcommit isues?16:28
alexpilottiI prefer the deoployer to know what he / she is doing16:28
schwichthalt the VM ?16:28
*** mkollaro has quit IRC16:28
alexpilottischwicht: yes16:28
alexpilottischwicht: which usually means that a lot of VMs get stopped16:28
*** mkollaro has joined #openstack-meeting16:28
schwichtoh ok16:28
*** lcheng2 has quit IRC16:28
alexpilottithere's also a "safety buffer" option16:28
schwichtI thought the iggest gets supsended16:28
*** eharney has quit IRC16:28
schwichtbiggest16:28
alexpilottithe one requesting for the memory gets suspended16:29
alexpilottithe safety buffer makes sure that an extra memory percentage is available (e.g. 20%)16:29
alexpilottiso a new VM cannot be started if there's less than the expected memory16:30
alexpilottiok, that's it on the topic on my side16:30
primeministerpok16:31
primeministerpanything on the RDP side of things?16:31
*** virajh has joined #openstack-meeting16:31
alexpilottinot yet, we put the WMIV2 into priority16:31
alexpilottiI'll probably send in a patch for RDP as well for H216:31
*** eharney has joined #openstack-meeting16:31
*** eharney has quit IRC16:31
*** eharney has joined #openstack-meeting16:31
primeministerpok16:32
alexpilottiknowing that the review will take some time16:32
alexpilottiI'd like to discuss if we should support or not the serial console16:32
primeministerpo yes16:33
*** zehicle_at_dell has quit IRC16:33
primeministerp#topic serial console16:33
schwichtalexpilotti: I like the serial console a lot16:34
alexpilottiOpenStack at the moment has only the option of getting the output16:34
primeministerpalexpilotti: you want to describe16:34
schwichtr/o ?16:34
alexpilottischwicht: yep16:34
alexpilottiwe us it r/w a lot for troubleshooting16:34
schwichtyep16:34
alexpilottiboth on Linux and on Windows16:34
alexpilottion Windows we created a service that provides a command prompt16:34
schwichtlogging boot issues is cool, messing with network etc16:34
schwichtprimeministerp: the OVS issue we usually debug with a serial console16:35
alexpilottischwicht: yep16:35
primeministerpschwicht: ;)16:35
alexpilottion Windows we use it to set the user name, reboot, setting network details16:35
alexpilottidiskpart for resizing the partitions, etc16:36
alexpilottienabling RDP if it was not enabled16:36
schwichtso as long openstack does not support r/w it is merly a debugging, logging tool16:36
schwichtand for that not as important for my use cases16:37
alexpilottiIt'd be great to have in in OpenStack with an HTML5 websocked based VT100 emulator :-)16:37
schwichtsince I can attach a console on the hyperV host16:37
alexpilottischwicht: yes, we a simple powershell script that attaches it and starts putty16:37
*** Swami has joined #openstack-meeting16:38
alexpilottischwicht: but the logging part is already cool to detect issues with cloud-init, to detect why e.g. the instance does not get SSH connections16:38
schwichtyes it is16:38
schwicht(we SOL enable all physical hosts for the same reason)16:38
*** Fdot has quit IRC16:38
alexpilottiok, I wanted to introduce the topic, I have a working proto, just need to file up a BP and polish up the patch16:39
primeministerpnice16:39
primeministerpwell good work16:39
alexpilotticool, tx16:40
alexpilottiI'm running a bit late, we organized the second Python event in Timisoara16:41
primeministerpok16:41
primeministerplet's finish up16:41
primeministerpis there anything else we're missing?16:41
*** SergeyLukjanov has quit IRC16:42
alexpilottiWe have issues with OVS on RDO16:42
alexpilottibut let's discuss about this next time once we have a solution :-)16:42
primeministerpschwicht: this is what we were discussing earlier16:42
primeministerpalexpilotti: can you discribe it16:42
alexpilottivery simple:16:42
schwichtalexpilotti: do you have a pointer with more details?16:42
alexpilottinot yet, it came out this sunday16:42
alexpilottiin brief:16:43
*** IlyaE has quit IRC16:43
alexpilottimultinode setup:16:43
alexpilotticontroller, network, kvm compute and hyperv compute16:43
*** elo has quit IRC16:43
alexpilottibased on CentOS 6.416:43
alexpilottieverything works except networking16:44
schwicht802.1Q ?16:44
alexpilottianything, VLAN or flat16:44
schwichtwhat physical ethernet adapter? what switch?16:44
alexpilottilooks like either the datapaths or the flows are not working16:45
alexpilottiOVS16:45
*** elo has joined #openstack-meeting16:45
alexpilottino phisycal switches16:45
schwichtthe physical switch between the KVM and and the hyperV node16:45
alexpilotticloud be virtual switches on ESXi / Fusion / workstation (testing)16:45
schwichtah ok16:46
alexpilottior any L2 switch when testing a flat network config16:46
schwichtstacked ...16:46
alexpilottiyep16:46
schwichtdo you use portgroup 4095 on ESXi ?16:46
alexpilottiat the beginning I was thinking about an issue due to the stacking16:46
alexpilottinope16:47
*** jcoufal is now known as jcoufal_afk16:47
alexpilottias I was saying the issue can be reproduced even with flat networking16:47
schwichtwe probably should move that off the meeting discussion16:47
*** michchap has joined #openstack-meeting16:47
alexpilottiI can tcpdump the traffic16:47
alexpilottiat  the ethx level16:47
alexpilottiit's simply not getting forwarded to the proper bridge / tap device16:48
alexpilotti(in OpenVSwitch)16:48
alexpilottiI'm gonna get in touch today with the RDO guys and see16:48
alexpilottioki guys, I really have to run unfortunately16:49
schwichtare your br-eth and br-int bridges up?16:49
primeministerpok16:49
alexpilottiAh, one more thing16:49
alexpilottischwicht: yep16:49
alexpilottiThis week we start committing the Crowbar upport for Hyper-V :-)16:49
*** zehicle_at_dell has joined #openstack-meeting16:50
primeministerpawesome!16:50
primeministerpso16:50
*** markwash has joined #openstack-meeting16:51
primeministerpanyone have anything else16:51
primeministerpto add?16:51
primeministerpif not, I'm going to end it.16:52
*** shmcfarl has quit IRC16:52
*** shmcfarl has joined #openstack-meeting16:52
primeministerpthanks alexpilotti for the updates16:52
primeministerp#endmeeting16:52
openstackMeeting ended Tue Jul  9 16:52:37 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:52
alexpilottithanks guys!16:52
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-07-09-16.00.html16:52
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-07-09-16.00.txt16:52
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-07-09-16.00.log.html16:52
alexpilottibye!16:52
*** stevemar has quit IRC16:54
*** kebray has joined #openstack-meeting16:56
*** kebray has quit IRC16:56
*** nati_ueno has joined #openstack-meeting16:56
*** luis_fdez has quit IRC16:57
*** colinmcnamara has quit IRC16:57
*** alexpilotti has quit IRC16:57
*** garyk has joined #openstack-meeting16:57
*** michchap has quit IRC16:59
*** derekh has quit IRC17:02
*** colinmcnamara has joined #openstack-meeting17:03
*** hk_peter has joined #openstack-meeting17:04
hk_peterhi all, pandora is open for test http://peter.kingofcoders.com/?p=677   , we need more team member, if you like it, join the team.17:05
garykdabo ping17:06
hk_peter?17:07
*** Adri2000 has quit IRC17:07
*** vipul-away is now known as vipul17:07
*** lloydde has joined #openstack-meeting17:08
*** nati_ueno has quit IRC17:08
*** Nachi has joined #openstack-meeting17:09
*** vipul is now known as vipul-away17:10
*** yaguang has quit IRC17:10
*** Adri2000 has joined #openstack-meeting17:13
*** morganfainberg has left #openstack-meeting17:14
*** morganfainberg has joined #openstack-meeting17:15
*** otherwiseguy has quit IRC17:15
*** otherwiseguy has joined #openstack-meeting17:15
*** SergeyLukjanov has joined #openstack-meeting17:18
*** boris-42 has joined #openstack-meeting17:19
*** haomaiwang has joined #openstack-meeting17:21
*** _TheDodd_ has joined #openstack-meeting17:22
*** haomaiwang has quit IRC17:25
*** michchap has joined #openstack-meeting17:25
*** hk_peter has quit IRC17:28
*** sarob has joined #openstack-meeting17:29
*** markmcclain has joined #openstack-meeting17:33
*** martines has joined #openstack-meeting17:33
*** Haneef has joined #openstack-meeting17:34
*** MarkAtwood has joined #openstack-meeting17:34
*** michchap has quit IRC17:38
*** vijendar has quit IRC17:43
*** cp16net is now known as cp16net|away17:46
*** Mandell has joined #openstack-meeting17:48
*** vijendar has joined #openstack-meeting17:49
*** cp16net|away is now known as cp16net17:50
*** otherwiseguy has quit IRC17:50
*** fmanco has quit IRC17:51
*** dkranz has quit IRC17:52
*** bknudson has joined #openstack-meeting17:53
*** otherwiseguy has joined #openstack-meeting17:54
*** fmanco has joined #openstack-meeting17:54
*** garyk has quit IRC17:56
*** fabio has joined #openstack-meeting17:58
*** dolphm has joined #openstack-meeting17:58
dolphmo/17:58
bknudsonhi17:58
fabiohi17:58
dolphmayoung: gyee: o/17:58
dolphmno henrynash?17:58
spzalaHi17:58
*** sarob has quit IRC17:58
dolphmtopol: o/17:58
dolphmtermie: o/ (in case you're around)17:59
gyee\o17:59
*** sarob has joined #openstack-meeting17:59
topoldolphm: Hi17:59
dolphm#start-meeting keystone17:59
*** henrynash has joined #openstack-meeting17:59
dolphm#topic Havana milestone 217:59
dolphmis a next week17:59
henrynashhi17:59
dolphmso i want to spend most of the meeting checking on status of >low blueprints18:00
*** jog0 is now known as jog0-away18:00
dolphmso, in order of priority...18:00
dolphm#topic Allow project roles to be inherited from owning domain18:00
dolphm#link https://blueprints.launchpad.net/keystone/+spec/inherited-domain-roles18:00
henrynashso nearly ready18:00
dolphm#link https://review.openstack.org/#/c/35986/18:00
henrynashWIP is up already18:01
henrynash2 days to go18:01
*** brich has joined #openstack-meeting18:01
henrynashneed to rebase on set of dependant changes and then will publish for full review18:01
dolphmit's also dependent on another review, but i think that's ready to go18:01
henrynashyes18:01
henrynashI need to rebase that on Adam's split change which is gating rig now18:01
*** sarob has quit IRC18:01
dolphm(if anyone wants to review in the mean time- https://review.openstack.org/#/c/35897/ )18:02
*** sarob_ has joined #openstack-meeting18:02
*** garyk has joined #openstack-meeting18:02
topoldolphm, will do18:02
dolphmhenrynash: rebase which patch?18:02
*** cliu has quit IRC18:02
henrynashI need to rebase this one: #link https://review.openstack.org/#/c/35897/18:02
gyeewe need a bp to rationalize authentication, making the v2 to use v3 in the backend18:03
henrynashwhich is also a bp went want in for H2…it is complete, just needs a rebase18:03
dolphmis jamie lennox on? i can't remember your alias18:03
*** sarob_ has quit IRC18:03
dolphmhenrynash: damn, alright18:03
dolphmhenrynash: hopefully that won't be a complicated one18:03
fabiocatalog opt-out should be ready to go18:03
fabiohttps://review.openstack.org/#/c/34478/18:03
dolphmfabio: i'll get there18:04
dolphm#topic Make Eventlet Optional18:04
*** ndipanov has quit IRC18:04
henrynashdolphm: I'll get https://review.openstack.org/#/c/35897/ done today18:04
dolphmerr, i guess this depends on jamie / ayoung being on18:04
*** michchap has joined #openstack-meeting18:04
dolphm#link https://blueprints.launchpad.net/keystone/+spec/extract-eventlet18:04
dolphmbut this bp looks completed to me, although i know one change had to be backed out18:04
dolphmit looks like most of the work is done and merged18:04
dolphmso, perhaps just follow up with a bug?18:05
dolphmmoving on ... maybe they'll be on later, but i'll mark as implemented if i don't hear back18:05
dolphm#topic Allow clients to opt-out of service catalog inclusion18:05
dolphm#link https://blueprints.launchpad.net/keystone/+spec/catalog-optional18:05
dolphm#link https://review.openstack.org/#/c/34478/18:06
dolphmthis is still in review at the identity-api, but an impl is WIP18:06
dolphm#link https://review.openstack.org/#/c/34478/18:06
topolwill review 34478 today18:06
dolphmerr, that's the same review18:07
henrynashso I guess we need to agree the identity pay change today18:07
dolphmfabio: is there an impl available?18:07
dolphmfabio: i thought i saw something in review, but don't have a link18:07
fabioyes18:07
dolphmfabio: can you link us?18:07
dolphmhenrynash: +118:07
fabiohttps://review.openstack.org/#/c/33188/18:07
fabioI stopped updating it pending design decisions18:07
ayoungI'm here18:07
ayoungwas just doing code reviews....18:08
dolphmi'd *love* to take this opportunity to create a new catalog response given people's unhappiness with our current format, but i'd like to save that discussion for after the meeting in -dev18:08
dolphmif anyone is interested :)18:08
dolphmayoung: awesome18:08
*** dkranz has joined #openstack-meeting18:08
gyeedolphm, but that two different issues right?18:08
topolwhats the design decision fabio is waiting on?18:08
dolphmayoung: see above about extract-eventlet18:08
gyeeone for opt-out, the other for different format?18:08
bknudsondon't we want the catalog from /catalog to be the same as a catalog in the token18:08
dolphmgyee: yes, technically...18:09
gyeebknudson, yes18:09
dolphmbknudson: *i* don't want it to be the same18:09
*** marun has quit IRC18:09
ayoungI think extract eventlet is completed.  Let me confirm18:09
dolphmayoung: thanks18:09
ayoungwhich one had to be backed out?18:09
dolphmgyee: if you cut the entire catalog response example from the identity-api proposal, then the rest of the review is good to go :P18:09
fabiotopol: catalog format and opt flag in the payload18:09
dolphmayoung: there was a bug filed against some import in some module being used by swift or something?18:10
*** tiamar has joined #openstack-meeting18:10
dolphmayoung: there was a small revert to one patch18:10
gyeedolphm, sounds good, we can settle on the format later18:10
ayoungdolphm, OK.  I'll hunt that down. Expect this to be a moving target, as people seem to love their eventlet code.18:10
dolphmgyee: has to be designed and implemented this week though18:11
gyeek18:11
dolphm#topic Rationalize how user roles are obtained at authentication time18:11
dolphm#link https://blueprints.launchpad.net/keystone/+spec/authenticate-role-rationalization18:11
dolphmthis is the one that needs a rebase18:11
dolphm#link https://review.openstack.org/#/c/35897/18:11
dolphmotherwise, looks like it'll land really soon18:11
dolphm#topic Delegated Auth a la Oauth18:12
dolphm#link https://blueprints.launchpad.net/keystone/+spec/delegated-auth-via-oauth18:12
dolphmis steve on?18:12
ayoungdolphm, Oauth should be an extension, and it is no close to being ready18:12
topolso steve martinelli has 3 inches of rain in his living room (toronto floods)18:12
*** koolhead17 has quit IRC18:12
dolphmayoung: i thought it was an extension, but yes18:12
dolphmayoung: i haven't looked at the impl :(18:12
ayoungIt could conceivably go in async18:12
dolphmtopol: oh that's right18:12
topolso he's not here today18:12
ayoungIE...after H218:13
gyeedolphm, is extension allowed after H2?18:13
topolOauth is an extension correct?18:13
gyeeI wasn't clear on that18:13
dolphmi'll go ahead and bump to h3 then18:13
ayoungI thought it was only API changes were frozen after H2, right?18:13
dolphmayoung: i haven't checked the code review, but is that the basis for your -2's, or was there anything else?18:13
ayoungdolphm, the big thing was all of the token revocation rules18:13
ayoungit took us a long time to get those right for trusts, and the same logic applied here18:14
dolphmgyee: i mentioned this on list while i was afk last week... but i'll touch on that at the end of the meeting w/ link18:14
henrynashdolphm: we also need a formal identity api extension spec - steve is writing this18:14
*** jcoufal_afk is now known as jcoufal18:14
topolhenrynash +118:14
dolphmhenrynash: is there anything to do beyond say the oauth 1.1a spec is available at /OS-OAUTH11a/ or whatever?18:15
henrynashdolphm:….and that's where all the clarifications on how what type of token revocation is supports should be specified and debated18:15
dolphmhenrynash: ah, that's true18:15
topolI think the API spec will help folks understand what been done18:15
topolsemantics etc18:15
henrynashdolplm:18:15
dolphmsounds good, definitely m3 then18:15
henrynashagreed18:15
gyeem3 = h3?18:16
ayoungI am far more concerned with https://blueprints.launchpad.net/keystone/+spec/authentication-tied-to-token18:16
gyeeayoung, that needs to be in its own pluggable provider18:16
ayounghttps://review.openstack.org/#/c/36166/  needs more review18:16
*** michchap has quit IRC18:16
dolphmgyee: havana milestone 318:17
ayounggyee, needs an API review, too.18:17
*** otherwiseguy has quit IRC18:17
gyeeayoung, sure, will take a look18:17
dolphm#link Bind the Tokens to a secure authentication mechanism18:17
ayoungdolphm, is there any reason that pluggable can't go in after H2 if it is completely config/wsie backwards compatable?18:17
dolphm#link https://blueprints.launchpad.net/keystone/+spec/authentication-tied-to-token18:17
ayoungI'd rather take the time to get that right18:18
ayoungthen to rush it in, or have to punt on it18:18
dolphmas ayoung said, this currently has undocumented api impact and smells like it should be dependent on gyee's work18:18
dolphmso, i'm already thinking it should land in icehouse18:18
ayoungdolphm, token binding?18:18
topolthought he said no API impact?18:18
topol(ayoung)18:19
dolphmit adds additional attributes to the token18:19
ayoungyeah,  nothing needs to use them to start, but they will be there18:19
henrynashtopol: binding does have api impact, huggable token provider does not (i believe)18:19
gyeeayoung, suppose you can park it in contrib till icehouse?18:19
dolphmayoung: and yet, if they're there you're suddenly held to support the implementation18:19
ayoungBut I think we can get it in this week, and then rebase it on top of gyee's18:20
henrynashHa - huggable token providers…much better name, gyee18:20
ayoungdolphm, Oh, I agree that we need the API to be reviewed18:20
gyeehuggable?!18:20
dolphmayoung: still blocked by identity-api documentation18:20
henrynashgyee: yep, we love you, really18:20
gyeeyah18:20
*** roadnick has quit IRC18:20
ayoungif I said "no API impact" in the past I was being overly optimistic18:20
dolphmayoung: either way, i'd like to untarget from milestone 2 for now18:20
dolphm#topic Migrate data from ec2_credential to credential table18:21
dolphm#link https://blueprints.launchpad.net/keystone/+spec/migrate-ec2-credentials18:21
*** stevemar has joined #openstack-meeting18:21
gyeedolphm, that one needs clarification18:21
dolphmi haven't seen anything in review for this?18:21
dolphmgyee: how so?18:21
gyeethe blob18:21
dolphmgyee: ah, that's right18:22
ayoungdolphm, tell you what, why don't you make a first pass review of the API changes, and if it seems like it isn't going to work, untarget it.  I'll elave it to you.18:22
*** haomaiwang has joined #openstack-meeting18:22
gyeemy understanding is that it is a string, a serialized JSON object18:22
dolphmgyee: didn't realize that was the same review18:22
dolphmgyee: +118:22
dolphmgyee: the proposed implementation treats it as a dict18:22
gyeedolphm, it does a json.loads()18:22
gyeeso it is treating it as a string18:23
dolphmgyee: only if it's ec2?18:23
gyeeyes, for now18:23
dolphmthat sounds like something that should be done in middleware, not core code18:23
dolphmand we already have an ec2 extension for it to live in :)18:23
gyeethought we are eliminated ec2_credential table18:24
gyeeeliminating18:24
ayoungI'd really rather not drop the token binding, as I think it is one of those things that is going to take time to get traction.  If we don't get it in until Icehouse, people won't use it until Joliet.18:24
dolphmgyee: the extension can start using the credential driver18:24
dolphmayoung: yep18:25
gyeedolphm, correct, but we need to decided how we migrate the ec2_credentials first18:25
dolphmayoung: but i'd really rather not rush a highly impactful feature that has immediate security implications18:25
dolphmgyee: did that review also address that?18:25
dolphmmaybe that's why i was confused that it was the same thing..18:25
dolphm#link https://review.openstack.org/#/c/31290/18:26
gyeedolphm, I am fine with treating it as a serialized JSON string18:26
gyeeso ec2 extension can deserialize it accordingly18:26
dolphmno migration there, and it cites a bug, not the bp18:26
dolphmi'll bump this one to m3+18:26
dolphmgyee: +118:26
gyeesounds good18:27
*** haomaiwang has quit IRC18:27
*** roadnick has joined #openstack-meeting18:27
topolwhy the bump?18:27
dolphmtopol: there's nothing in review, deadline is next week, the assignee isn't here to speak up, and it could probably be low priority for now18:27
topolOK cool18:28
gyeedolphm, I'll ask nachi to work overtime on this :)18:28
dolphmnachi__: Nachi: <-- assignee18:28
dolphmi'm assuming18:28
Nachidolphm: ?18:28
dolphmNachi: we're discussing one of your bp's, didn't realize you were on18:28
Nachidolphm: hehe I'm here :)18:28
Nachidolphm: which bp?18:29
dolphmNachi: thoughts on bumping bp migrate-ec2-credentials this from havana-m2 to m3+?18:29
dolphmif there's something in review, i just haven't seen it18:29
dolphmthis is obviously related, but doesn't directly address the goal of the bp https://review.openstack.org/#/c/31290/18:29
Nachidolphm: is this keystone related topic? Why I'm involved?18:29
gyeedolphm, actually, the review is good as is since it is already treating blob as serialized JSON string18:29
dolphmNachi: the bp is currently assigned to you18:30
NachiReally!?18:30
dolphmNachi: should it be assigned to someone else / no one?18:30
Nachiahhh18:30
dolphmNachi: https://blueprints.launchpad.net/keystone/+spec/migrate-ec2-credentials18:30
nachi__dolphm: it is assigned to me18:30
Nachisorry I'm different Nachi18:30
NachiI'm nati.ueno.18:30
dolphmhaha18:30
dolphmNachi: my mistake!18:31
gyeeahhh18:31
topolwow. Im playing the lottery today18:31
Nachisorry I'll switch back my account18:31
*** Nachi is now known as nati_ueno18:31
nati_uenohere we go18:31
dolphmnati_ueno: i had assumed you were just logged into two or more locations18:31
dolphmnati_ueno: and that you were someone else18:31
nati_uenodolphm: could be18:31
dolphmso anyway18:31
dolphmnachi__: can you read back?18:32
dolphmi'll move on in the mean time18:32
dolphm#topic Pluggable token formats18:32
*** sarob has joined #openstack-meeting18:32
gyeeyah18:32
dolphm#link https://blueprints.launchpad.net/keystone/+spec/pluggable-token-format18:32
dolphmi blocked the impl on this one this morning18:32
gyeedolphm, both need to be active, per ayoung18:32
gyeePKI token and UUID tokens are interchangable18:32
dolphmand then saw on the meeting agenda there was a question about the same reason that i had -2'd (pki and uuid are not separate providers)18:32
dolphmis that a leftover from a previous meeting, or was that meant to be addressed today?18:33
*** johnthetubaguy has quit IRC18:33
ayoungdolphm, right.  at least not for validation18:33
gyeedolphm, I originally implemented them as separate providers18:33
ayoungdolphm, and gyee I can see two providers for the format produced, though18:33
dolphmayoung: today, keystone can only be configured to issue one of the two types of tokens, so there's no need to maintain complicated code paths simultaneously supporting both18:33
ayoungso long as the pki provider will validate the hashes as per the existing code, I am OK with two providers, and it will work18:34
*** vipul-away is now known as vipul18:34
gyeeayoung, it should18:34
gyeek, I'll separate them out again18:34
bknudsondo we have a testcase that verifies it?18:34
ayoungbknudson, there was one in the past18:35
gyeebknudson, the existing test cases cover them18:35
dolphmgyee: my second issue is that i thought this would be a simplification of our current architecture, but it seems to complicate it quite a bit; i'm hoping that will be resolved by either splitting the "keystone" provider or in the subsequent "v2" review18:35
*** ryanpetrello has quit IRC18:35
henrynashI must admit, I had expected to actually find different providers for v2 and v3 tokens18:35
gyeeI can do the split18:35
gyeehenrynash, we have to support both token formats at the same time18:36
gyeev2 and v318:36
dolphmwe'll soon have the auth controller, token controller, token driver, and token provider, and there's almost zero separation between them18:36
henrynash…but understand now that the approach is to only have one provider active18:36
gyeeso it make sense to have them provided by a single provider18:36
topolI thought the UUID provider would be simple enough to serve as the annotated sample18:36
dolphmhenrynash: i expect v2 and v3 tokens to be provided and persisted by the same backends, but presented to the client by the controller in slightly different formats18:36
dolphmas we do in all the other web-layer controllers18:36
dolphmbecause that's what the controllers are for18:37
dolphmpresentation.18:37
dolphmthat's also why a lot of people call them "views"18:37
gyeedolphm, can't, providers has to provider the complete token18:37
topolis the design brittle if we have the constraint of only one provider being active?18:37
gyeewith PKI, the hash has to be done first18:37
gyeeI did tried the translation middleware and that didn't work too well18:38
henrynashdolphm: sure….just thought it would be nice that we had them separated out at the back…but that would be a different model….tight now, I guess we are saying we will have a "keystone_UUID" provider and a "keystone_PKI" provdier18:38
gyeeso UUID and PKI provider then?18:38
gyeewe good on that?18:38
ayounggyee, yep18:38
henrynashdolphm: where "keystone" means…support whatever v2/3/4 versions we have18:38
*** alexpilotti has joined #openstack-meeting18:39
dolphmgyee: definitely18:39
*** sushils has quit IRC18:39
dolphmlast but not least...18:40
dolphm#topic Split the Identity Backend18:40
gyeehenrynash, not sure if I understand the last question18:40
dolphm#link https://blueprints.launchpad.net/keystone/+spec/split-identity18:40
ayoungWe are tracking there18:40
ayounghad to rebase, but the rebase is going through gat18:40
ayounggate18:40
henrynashgyee: (Im agreeing with you :-) )18:40
*** mkollaro has quit IRC18:40
ayoungand after that is a cleanup change18:40
ayounghttps://review.openstack.org/#/c/34967/18:41
dolphmayoung: beyond what's in review, is there anything left to do to satisfy the bp?18:41
ayoungI'm willing to further refine the BP to say that this one is done here18:41
dolphmayoung: thanks18:41
ayoungand put things like "multipel LDAP support" into a future blueprint18:41
dolphmayoung: it was definitely very broad when first defined ;)18:41
dolphmayoung: cool18:41
fabiodolphm: can we briefly talk about https://blueprints.launchpad.net/keystone/+spec/endpoint-filtering ?18:42
fabioplease18:42
dolphmsure18:42
dolphm#topic filter endpoints based on scope18:42
dolphm#link https://blueprints.launchpad.net/keystone/+spec/endpoint-filtering18:42
fabiodolphm: you suggested to be an extension18:43
fabioI guess if it is in the core need to go to H218:43
*** michchap has joined #openstack-meeting18:43
dolphmit's a prime example of a feature that should be an extension, yes18:43
ayoungfabio, I can work with you on the review.  Some of the code you have needs to be re-arranged18:43
topolgyee, I am hoping there is a way for me to kick the tires on pluggable token.   Maybe by creating a trivial example to include and document18:43
fabiohttps://review.openstack.org/#/c/34489/18:43
topolmaybe its just annotating what you do for UUID. not sure yet18:44
ayoungfabio, endpoint is in the catalog backend, and projects are about to land in the assignment backend, so you are going to need to do some rebasing.18:44
fabiodolphm: so I will go ahead and re-factor it as an extension, agreed?18:44
dolphmfabio: yes18:44
dolphmfabio: api and implementation, both18:44
fabiodolphm: thanks!18:44
fabiodolphm: sure. Do I have time until H3 or it needs to go in H2?18:45
gyeefabio, extension can be in m3 and beyound18:45
dolphm#topic API feature freeze and extensions!18:45
morganfainbergdolphm / ayoung: I wont be able to finish https://blueprints.launchpad.net/keystone/+spec/cache-token-revocations by m2.  With the splits and changes, it'll also be easier to implement after the dust settles a little.18:45
morganfainbergjust as a heads up since we're rapidly approaching m2 deadline18:46
dolphmso, henrynash ping me a couple weeks ago and asked this question18:46
dolphmi've been mulling it ever since, and it came up on list last week18:46
dolphmthe goal of the api feature freeze is to provide stability on the core api during the last milestone so that we can fix bugs instead of creating them18:46
*** beagles has quit IRC18:47
gyeewe don't create bugs, only undocumented features :)18:47
dolphmso, as long as an API feature is not included in the default pipeline (and is therefore non-core) and doesn't impact that UX out of the box, i think it's fair to pursue development during m318:47
*** beagles has joined #openstack-meeting18:47
*** jcoufal has quit IRC18:47
ayoungmorganfainberg, that is fine.  I don't want to rush that one18:47
morganfainbergayoung: exactly.18:48
topoldolphm, so will you decide this on a case by case basis?18:48
dolphmanyway, i think default-disabled extensions can land in m3 without negatively impacting the havana release18:48
ayoungdolphm, +118:48
dolphmtopol: i'm making a general statement-- is there a specific case you have in mind?18:48
ayoungdolphm, might I explicitly add "changes must be configuration compatable"18:48
gyeedolphm, does that mean extensions are disabled by default?18:48
dolphmgyee: yes18:49
gyeeI am good with that18:49
topolNo. just good to understand the process. inevitably folks always trying and shove stuff in18:49
bknudsonin the v3 api, there's no /extensions...how does a client know what extensions are available?18:49
ayoungbknudson, I think fixing that can be a H3 feature18:49
dolphmbknudson: the v3 api doc only documents what's available on /v3/18:49
ayoungit is there, just broken18:50
dolphmbknudson: technically there's an xsd and wadl for what's available at / ... including the multiple choice response and /extensions18:50
*** joshuamckenty has joined #openstack-meeting18:50
dolphmbknudson: that's all buried in the identity-api repo somewhere18:50
gyeebknudson, you mean discover extensions programmatically?18:50
bknudsondolphm: ok, it's in /, not v3.18:50
gyeeyeah GET /18:50
*** jaypipes has quit IRC18:50
ayoung#link https://bugs.launchpad.net/keystone/+bug/117753118:50
uvirtbotLaunchpad bug 1177531 in keystone "Active Extensions not enumerated " [High,Confirmed]18:50
ayoungcan we make that a critical, and I am willing to take it?18:51
dolphmbknudson: yes, although i think it'd more sense for it to be on /v3/extensions18:51
dolphmayoung: looking18:51
*** egallen has quit IRC18:51
dolphmayoung: i don't really think it's critical without broken consumers18:51
gyeedolphm, as long as it is consistent with the rest of the stack18:51
dolphmgyee: gabrielhurley is doing some work around improving that openstack-wide18:52
ayoungdolphm, that logic is circular.  We have no consumers *because* it is broken18:52
*** mdomsch has joined #openstack-meeting18:52
ayounganyway, I will take the bug and fix.18:52
dolphmgyee: until then, i don't want to evolve what we have, other than make it work as promised ;)18:52
dolphmayoung: +1, so it's not critical :P18:52
ayounghigh is fine18:52
dolphmayoung: please do! that'd be awesome18:53
gyeealrighty then18:53
dolphmhigh priority bug != critical priority work18:53
*** stevemar has quit IRC18:53
dolphmor whatever18:53
dolphmbug priority != work priority18:53
gyeetru18:53
henrynashdolphm: one bug fix still outstanding for H2: #link https://bugs.launchpad.net/keystone/+bug/119179418:53
uvirtbotLaunchpad bug 1191794 in keystone "Some of the collections in the API document are missing the top level collections name " [Medium,Confirmed]18:53
dolphm#topic open discussion18:54
henrynashdolphm: this is just an api clean up…..no code change, will get it down in newt few days18:54
dolphmhenrynash: i *swear* there was a fix in review for that... but do you have a link?18:54
dolphmand i swear bknudson did it18:54
dolphmor maybe i did it and didn't put it up for review18:54
topolWho is going to Hong Kong?18:54
henrynash#link https://bugs.launchpad.net/keystone/+bug/119179418:55
uvirtbotLaunchpad bug 1191794 in keystone "Some of the collections in the API document are missing the top level collections name " [Medium,Confirmed]18:55
henrynashtopol: I am18:55
*** olaph has joined #openstack-meeting18:55
gyeetopol, you want an example of token provider in the doc?18:55
dolphmtopol: i'm waiting to be told if i'm being sent, or if i have to find another employer to send me18:55
gyeedolphm, heh, same here18:55
henrynashdolphm: :-)18:55
nachi__dolphm: i joined late in meeting. I read back the comments. I am done with blueprint implementation for migrate ec2 credentials. I have in draft review.18:55
nachi__It has a dependency on the bug fix https://review.openstack.org/#/c/33525/ if sqlite database is used.18:55
nachi__I got your comments for the review and i will rebase the changes with your comments. I am also waiting for ayoung comment on the18:55
nachi__review.18:55
*** michchap has quit IRC18:55
dolphmnachi__: that's what i figured, do you have the next step implemented / planned out / etc?18:56
bknudsonquick question -- should the identity endpoints in catalog have /v2? I was trying to use openstack CLI and v3 commands didn't work.18:56
*** jcoufal has joined #openstack-meeting18:56
dolphmnachi__: thanks for the follow up18:56
henrynashayoung: assignment split just merged!!!!18:56
dolphmbknudson: ideally, no... that's also something gabrielhurley is working on fixing throughout openstack18:56
topolgyee, I like some form of example. either in doc or sample code. Otherwise some clown like me adds a new provider by shoving it in the existing package instead of creating a new one...18:57
dolphmbknudson: in the mean time, keep shoving /v2.0/ onto the identity endpoint, etc, until we have smarter clients18:57
*** jmh_ has joined #openstack-meeting18:57
dolphmhenrynash: ayoung: yay18:57
* ayoung does happy dance18:57
ayoungnachi__, I'll review after the meeting18:57
*** colinmcnamara has quit IRC18:57
henrynashayoung: does "time_to_rebase" dance18:57
bknudsonwith v2.0, openstack commands don't work because the client tries to GET v2.0/projects or whatever.18:57
nachi__dolphm: thanks. i will submit the changes with your review comments https://review.openstack.org/#/c/33525/ in an hour18:57
nachi__thanks ayoung18:57
bknudsonwhen it should use v3.18:57
dolphmgyee: topol: on token providers, maybe hold off on new docs until there's a uuid provider in core? i'm thinking that would be simple enough to base a new impl on18:58
topoldolphm +118:58
gyeedolphm, +118:58
dolphmtopol: or, re-evaluate after the "keystone" provider is split into pki & uuid18:58
dolphmo/18:58
*** colinmcnamara has joined #openstack-meeting18:58
dolphm#endmeeting18:58
*** fabio has left #openstack-meeting18:58
topolagreed. I suspect with that may a line or two in the rst giving the right breadcrumbs and we are good to go18:59
gyeetopol, I am avaiable for consult, for a nominal fee :)18:59
*** brich has left #openstack-meeting18:59
gyeeconsultant18:59
*** dcramer_ has quit IRC19:00
topolnominal fee.  I shove my provider in the wrong place before I give you a buck :-)19:00
jeblairdolphm: was meetbot not working?19:02
*** koolhead17 has joined #openstack-meeting19:03
*** koolhead17 has joined #openstack-meeting19:03
* fungi was wondering the same19:03
dolphmoh, damn19:03
dolphmi didn't even notice19:03
fungitime for us to test it, i guess19:03
jeblairlets give it a go!19:03
jeblair#startmeeting infra19:03
openstackMeeting started Tue Jul  9 19:03:24 2013 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:03
openstackThe meeting name has been set to 'infra'19:03
*** vkmc has joined #openstack-meeting19:03
fungiseems sane as ever (maybe moreso)19:03
dolphm#facepalm19:03
dhellmanno/19:03
olapho/19:03
clarkbo/19:03
*** garyTh has joined #openstack-meeting19:03
zaroo/19:03
*** sarob has quit IRC19:03
fungidolphm: i have a copy of your sekrit meeting logs in my irc client anyway19:03
jeblairdolphm: yeah, looks like you had a stray '-' in the startmeeting cmd19:03
mordredo/19:04
*** sarob has joined #openstack-meeting19:04
anteayao/19:04
* zul lurks19:04
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:04
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-07-02-19.03.html19:04
jeblair#topic actions from last meeting19:04
pleia2o/19:05
jeblairso all the actions were about the quantum/neutron rename...19:05
jeblair#topic Rename of the project formerly known as mutnuaq (mordred)19:05
fungiwell, i know action item #3 happened19:05
jeblairso let's just jump to that19:06
*** bknudson has left #openstack-meeting19:06
jeblair(oh, it does look like meetbot doesn't have ops)19:06
mordredwth?19:06
jeblairmordred: probably netsplit fallout19:06
*** thunquest has quit IRC19:06
mordred++19:06
*** ChanServ sets mode: +o fungi19:07
*** vipul is now known as vipul-away19:07
*** fungi sets mode: +o openstack19:07
*** fungi sets mode: -o fungi19:07
fungihe's op'd now19:07
jeblairhttps://launchpad.net/~quantum-core19:07
jeblairthat doesn't exist anymore19:07
jeblairso i assume ttx did that19:07
jeblair#link https://wiki.openstack.org/wiki/Network/neutron-renaming19:08
mordredhttps://launchpad.net/~neutron-core doens't exist either19:08
ttxjeblair: indeed19:08
*** novas0x2a|laptop has joined #openstack-meeting19:08
ttxmordred: -core is maintained in gerrit now, removed the convenience almost-shadow group19:08
mordredttx: excellent. thank you19:09
jeblairi think the only specifically infra related thing left is to manually publish a quantumclient19:09
fungiif we need one going forward, it would be a ~neutron-security group or something instead19:09
jeblairwhich happens after all the code rename stuff happens19:09
*** jaypipes has joined #openstack-meeting19:09
*** vkmc has quit IRC19:09
*** vkmc has joined #openstack-meeting19:09
ttxfungi: +119:09
jeblairttx, markmcclain, mordred: know how the in-project renames are progressing?19:09
mordredjeblair: I do not know19:10
* ttx missed most of the saturday party due to some kind of family emergency, I hope it went well19:10
fungittx: it went fine. we were marvellously overstaffed19:10
jeblairttx: i think it went very well; nothing unexpected happened, and the gating jobs worked the first time through afterwords19:10
ttxjeblair: I've seen a few renames passing by. Will ask markmcclain during release meeting tonight19:11
jeblairttx: cool, thanks19:11
*** Haneef has quit IRC19:11
jeblairany final thoughts on this topic?19:12
markmcclainjeblair: horizon, heat, and nova left to finish19:12
*** gary_th has joined #openstack-meeting19:12
jeblairmarkmcclain: neato19:13
markmcclainI do want to say thanks to everyone for their work on renaming.. you guys made it super smooth and easy19:13
jeblair'quantum' shows up a lot less in devstack now19:13
jeblairmarkmcclain: thanks for iterating with us on the procedure; our earlier ones would not have gone as well.  :)19:13
* fungi raises a toast to thorough planning19:14
* jeblair cheers19:14
clarkbit did go very smoothly. I ended up reviewing code >_>19:15
*** garyTh has quit IRC19:15
jeblairso i think asterisk and mongodb are stale agenda items this week, or does anyone have something to say about those?19:15
fungii took mongo off just a moment ago19:16
fungimeant to do it after last week's meeting19:16
jeblair#topic open discussion19:16
*** openstack changes topic to "open discussion (Meeting topic: infra)"19:16
fungilooks like meetbot's oper status is good now19:16
jeblairmordred has proposed a scope for the infra program19:17
*** otherwiseguy has joined #openstack-meeting19:17
jeblairit's on the -dev list19:17
mordredso far no one has disagreed19:17
mordredwhich I take to be a good sign19:17
clarkblast week was a short week was a short week as was the one before it. I don't have a whole lot to talk about. Elasticsearch is unhappy and will be for the near future but two new nodes should help make it happy again19:17
* jeblair agrees19:17
fungii don't disagree with any of it, but didn't want to add silly +1 noise on the list19:17
* mordred tried to land a pbr change for over 10 hours yesterday and failed19:17
pleia2yeah, infra description looks good19:18
mordredwhich was fun19:18
pleia2no real updates from me, chugging along with cgit and bare metal stuff19:18
mordredand pointed out just how much benefit I think the projected work around kicking stuff out of queue will be19:18
jeblairmordred: what were the problems you observed?19:18
mordredpleia2: I welcome our upcoming cgit masters19:18
jeblairmordred: were you behind merge conflicts?19:19
mordredjeblair: long amounts of time waiting when changes in front were unmergable19:19
mordredjeblair: yes. most of the time I checked on the changes, they were in queue and zuul knew that their current state was pointless19:19
*** dcramer_ has joined #openstack-meeting19:19
mordredso I think our current ideas for improvement there would have been helpful19:19
jeblairk.  i'm getting closer to that.19:19
ttxmordred: is there a landing page for infra on the wiki already ?19:19
mordredttx: not sure19:20
mordredttx: I have not gotten to moving that info there19:20
fungittx: does the InfraTeam page count?19:20
pleia2we have an InfraTeam page I made, but that's more for us, not about Infrastructure19:20
fungii guess a separate page for the program itself is still warranted19:20
ttxpleia2: I'd rather create an "Infrastructure" page  as a classic program landing page and point to InfraTeam from there19:20
pleia2ttx: +119:21
fungiwfm19:21
jeblair"live reload" is merged, i just wrote "deeper log directories"; next up is gearman priorities; then i think merge conflicts.19:21
*** thunquest has joined #openstack-meeting19:21
jeblairthere's lots of docs about the program and team at ci.openstack.org19:21
jeblairwe should have the wiki page be short and point there19:21
mordredyuo19:21
jeblairto reduce redundancy, i think19:21
mordredyup19:21
mordredI think it should have mission statement, a link to ci.openstack.org and a link to InfraTeam19:21
mordredand that's it19:21
clarkb++19:21
mordredttx: are you going to have a Programs page?19:22
jeblairsounds good19:22
*** michchap has joined #openstack-meeting19:22
mordredttx: and/or should I  make the page Program/Infrastructure instead of just Infrastructure?19:22
ttxmordred: there is one already19:22
fungimordred: agreed19:22
mordredor https://wiki.openstack.org/wiki/Programs/Infrastructure19:22
ttxmordred: just "Infrastructure". There is "Oslo" already" and a page for each existing project at the top-level19:22
pleia2I'll clean up InfraTeam a bit this week, now that ci.openstack.org has been rewritten some of it is redundant19:22
*** haomaiwang has joined #openstack-meeting19:23
*** gary_th has quit IRC19:23
*** gyee has quit IRC19:23
ttxmordred: that will avoid having to move all the existing ones. We'll just link it from the Programs page19:23
*** galstrom_zzz is now known as galstrom19:23
*** jbjohnso has quit IRC19:23
fungiespecially since there's also, e.g., https://wiki.openstack.org/wiki/Nova19:24
ttxand https://wiki.openstack.org/wiki/Oslo19:24
*** alexpilotti has quit IRC19:25
fungithe final iteration was that each of the server projects is also a program, right?19:25
fungi(more or less)19:25
ttxfungi: yes19:25
mordredhttps://wiki.openstack.org/wiki/Infrastructure19:25
ttxmordred: ok, will add link19:26
pleia2\o/19:26
*** mdomsch has quit IRC19:26
ttxmordred: until we add some magic tagging to projects.yaml, would be great to list the repos that are under "Infra"19:27
*** haomaiwang has quit IRC19:27
ttxcan be as simple as openstack-infra/* + foo19:27
* fungi just had a vision of a cron job or puppet exec to update some wiki stubs from a project/program registry in projects.yaml19:29
ttxjeblair: can everyone see the -core group contents in gerrit ?19:29
* dhellmann thinks if we have a bot updating a wiki we might be using the wrong tool :-)19:29
jeblairttx: that is the intent19:30
mordreddavidlenwell: you were working on a diagram from the bootcamp - any status on that?19:30
ttxBecause http://dowdberry.blogspot.fr/2013/07/openstack-programs-core-developers.html is wrong19:30
pleia2oh, I did end up writing that launchpadlib script for our bug days, so it'll be much easier for me next time around19:30
fungidhellmann: yeah, that suggests something notwiki at that point, agreed19:30
pleia2(it just lives on my desktop for now, if there is a useful place to put it I'm open to suggestions)19:30
ttxjeblair: so everyone can access https://review.openstack.org/#/admin/groups/83,members for example ?19:30
davidlenwellits still kinda messy.. I was waiting for olaph to send me his drawings.. but he seems to have been pretty busy.. I'll make it priotity to finish early this week.19:30
* ttx can't tell what he is privileged for and what he isn't :)19:31
pleia2davidlenwell: great! looking forward to seeing that :)19:31
olaphdavidlenwell: coming right up...19:31
jeblairttx: yep.  i think you are unpriviliged in this context (unless you are a member of a group)19:31
davidlenwellthanks olaph19:31
jeblairttx: if any of them are not visible, it's a bug we can easily fix19:31
mordredit would be neat if that link had a name like "https://review.openstack.org/#/admin/groups/nova-core,members"19:31
ttxmordred: indeed19:32
clarkbpleia2: I want to say jeepyb would be a good place for that maybe19:32
pleia2clarkb: it's just a basic script that pours a bunch of stuff into stdout for me to copy into an etherpd19:32
*** haleyb has left #openstack-meeting19:33
jeblairi think a link to github or git.o.o (when it exists) for an automatic index of the infra repos makes sense19:33
clarkbhmm, not quite sure then. maybe just in your personal github is sufficient for now?19:33
pleia2clarkb: yeah, that's what I'm thinking19:33
pleia2I'll get it up later19:33
*** michchap has quit IRC19:34
*** joshuamckenty has quit IRC19:34
*** hanrahat has quit IRC19:35
jeblairanything else, or shall we wrap up early?19:36
mordredwrapping up sounds good to me19:36
clarkbyup. we have had a couple short weeks so not surprising :)19:36
fungittx: for the record, if you click on the "general" link for the group there's a checkbox for "Make group visible to all registered users."19:37
ttxfungi: cool19:37
fungittx: and also a column for it in the groups list19:37
*** henrynash has quit IRC19:37
*** dcramer_ has quit IRC19:37
fungiwith little checkmarks19:37
ttxjeblair, mordred: we are getting closer to h2 so please hold on non-urgent disruptive changes starting like..; thursday19:38
*** lcheng2 has joined #openstack-meeting19:38
fungiwith a deadline like that, i will bump zuul changes to the top of my review queue19:38
* mordred rushes to force-push all broken pbr changes...19:39
fungiha19:39
jeblairso i'm trying to roll out a potentially disruptive change to zuul19:39
jeblairwhich i wanted to do over the weekend, but was unable to19:39
jeblairmy next opportunity is wednesday afternoon19:39
ttxjeblair: should be good, but expect heavy review activity this week19:40
*** annegentle has quit IRC19:40
mordredjeblair: I'm going to release 0.5.18 of pbr now19:40
*** annegentle_ has joined #openstack-meeting19:40
mordredanybody have any concerns about that?19:40
clarkbmordred: none from me19:40
mordreddone19:41
jeblairwell, if i break anything, i'll do the reverifies myself.  though if there are problems, it's likely to mean long gate queues19:41
fungiif it works as intended, however, it could mean much shorter gate queues19:42
jeblairbut i think it's worth it because the next several changes to zuul are all about performance improvements19:42
mordred+10019:43
clarkb++19:43
*** cliu has joined #openstack-meeting19:43
jeblairat any rate, the change should be easy to revert, so if there's a problem that can't be immediately fixed, we'll just roll back to what we're running now19:43
mordredsounds good to me19:44
fungii'm in favor19:44
*** stevebaker has joined #openstack-meeting19:45
*** hanrahat has joined #openstack-meeting19:46
davidlenwellthanks for the scans olaph.. I'll kick this diagram out before eod tomorrow.19:46
jeblairlast call19:46
*** koolhead11|away has joined #openstack-meeting19:48
jeblairthanks everyone!19:48
jeblair#endmeeting19:48
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"19:48
openstackMeeting ended Tue Jul  9 19:48:11 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-07-09-19.03.html19:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-07-09-19.03.txt19:48
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-07-09-19.03.log.html19:48
*** olaph has left #openstack-meeting19:49
*** Yada has quit IRC19:51
*** dcramer_ has joined #openstack-meeting19:52
*** ryanpetrello has joined #openstack-meeting19:53
ttx(no TC meeting today, next meeting is release meeting in 66 minutes)19:55
*** koolhead17 has quit IRC19:55
*** koolhead11|away has quit IRC19:55
*** Nachi has joined #openstack-meeting19:55
*** ilyashakhat_ has joined #openstack-meeting19:55
*** koolhead17 has joined #openstack-meeting19:55
*** koolhead17 has joined #openstack-meeting19:55
*** terryw has joined #openstack-meeting19:55
stevebakerttx really? whew19:58
*** med_ has quit IRC19:58
*** s1rp has joined #openstack-meeting19:58
*** vipul-away is now known as vipul19:58
*** annegentle_ has quit IRC19:59
*** lychinus has joined #openstack-meeting20:00
*** otherwiseguy has quit IRC20:00
*** egallen has joined #openstack-meeting20:00
*** michchap has joined #openstack-meeting20:01
*** dkliban has quit IRC20:01
*** thunquest has quit IRC20:01
*** lychinus has quit IRC20:01
*** Adri2000 has quit IRC20:01
*** nati_ueno has quit IRC20:01
*** ociuhandu has quit IRC20:01
*** Akendo has quit IRC20:01
*** RajeshMohan has quit IRC20:01
*** lifeless has quit IRC20:01
*** Avatar[01] has quit IRC20:01
*** ilyashakhat has quit IRC20:01
*** s1rp_ has quit IRC20:01
*** harlowja has quit IRC20:01
*** troytoman-away has quit IRC20:01
*** torgomatic has quit IRC20:01
*** fmanco has quit IRC20:01
*** fmanco has joined #openstack-meeting20:02
*** hanrahat has quit IRC20:02
*** lychinus has joined #openstack-meeting20:02
*** hanrahat has joined #openstack-meeting20:02
*** lychinus_ has joined #openstack-meeting20:03
*** IlyaE has joined #openstack-meeting20:03
*** lifeless has joined #openstack-meeting20:03
*** lychinus is now known as Guest6997620:04
*** lychinus_ is now known as lychinus20:05
*** spzala has quit IRC20:05
*** sandywalsh has quit IRC20:05
*** Avatar[01] has joined #openstack-meeting20:06
*** thunquest has joined #openstack-meeting20:06
*** Adri2000 has joined #openstack-meeting20:06
*** ociuhandu has joined #openstack-meeting20:06
*** Akendo has joined #openstack-meeting20:06
*** RajeshMohan has joined #openstack-meeting20:06
*** troytoman-away has joined #openstack-meeting20:06
*** torgomatic has joined #openstack-meeting20:06
*** Guest69976 has quit IRC20:06
*** med_ has joined #openstack-meeting20:07
*** radez is now known as radez_g0n320:08
*** henrynash has joined #openstack-meeting20:08
*** tedross has quit IRC20:10
*** kebray has joined #openstack-meeting20:10
*** michchap has quit IRC20:13
*** sandywalsh has joined #openstack-meeting20:17
*** dprince has quit IRC20:19
*** Avatar[01] has quit IRC20:23
*** thunquest has quit IRC20:23
*** Adri2000 has quit IRC20:23
*** ociuhandu has quit IRC20:23
*** Akendo has quit IRC20:23
*** RajeshMohan has quit IRC20:23
*** troytoman-away has quit IRC20:23
*** torgomatic has quit IRC20:23
*** vijendar1 has joined #openstack-meeting20:24
*** Avatar[01] has joined #openstack-meeting20:24
*** thunquest has joined #openstack-meeting20:24
*** Adri2000 has joined #openstack-meeting20:24
*** ociuhandu has joined #openstack-meeting20:24
*** Akendo has joined #openstack-meeting20:24
*** RajeshMohan has joined #openstack-meeting20:24
*** troytoman-away has joined #openstack-meeting20:24
*** torgomatic has joined #openstack-meeting20:24
*** vijendar has quit IRC20:25
*** diogogmt has joined #openstack-meeting20:27
*** Yada has joined #openstack-meeting20:29
*** markwash_ has joined #openstack-meeting20:30
*** fmanco has quit IRC20:30
*** markwash has quit IRC20:31
*** markwash_ is now known as markwash20:31
*** michchap has joined #openstack-meeting20:32
*** gyee has joined #openstack-meeting20:32
*** gyee has quit IRC20:35
*** gyee has joined #openstack-meeting20:38
*** markmc has joined #openstack-meeting20:38
*** ilyashakhat_ has quit IRC20:38
*** ilyashakhat has joined #openstack-meeting20:38
*** Avatar[01] has quit IRC20:38
*** thunquest has quit IRC20:38
*** Adri2000 has quit IRC20:38
*** ociuhandu has quit IRC20:38
*** Akendo has quit IRC20:38
*** RajeshMohan has quit IRC20:38
*** troytoman-away has quit IRC20:38
*** torgomatic has quit IRC20:38
*** joshuamckenty has joined #openstack-meeting20:38
*** harlowja has joined #openstack-meeting20:38
*** dolphm has quit IRC20:39
*** jhenner has quit IRC20:39
*** joshuamckenty has left #openstack-meeting20:39
*** ociuhandu has joined #openstack-meeting20:40
*** dkliban has joined #openstack-meeting20:40
*** Yada has quit IRC20:40
*** shmcfarl has quit IRC20:41
*** Avatar[01] has joined #openstack-meeting20:41
*** thunquest has joined #openstack-meeting20:41
*** Adri2000 has joined #openstack-meeting20:41
*** Akendo has joined #openstack-meeting20:41
*** RajeshMohan has joined #openstack-meeting20:41
*** troytoman-away has joined #openstack-meeting20:41
*** torgomatic has joined #openstack-meeting20:41
*** Avatar[01] has quit IRC20:42
*** Avatar[01] has joined #openstack-meeting20:42
*** koolhead17 is now known as koolhead17|zzZZ20:44
*** vijendar1 has quit IRC20:45
*** IlyaE has quit IRC20:47
*** IlyaE has joined #openstack-meeting20:49
*** vijendar has joined #openstack-meeting20:50
*** luis_fdez has joined #openstack-meeting20:52
*** lcheng2 has quit IRC20:52
*** ni291187 has joined #openstack-meeting20:53
*** dolphm has joined #openstack-meeting20:53
*** luis_fdez has quit IRC20:53
*** lcheng2 has joined #openstack-meeting20:53
*** ni291187 has quit IRC20:53
*** gabrielhurley has joined #openstack-meeting20:55
*** hub_cap has joined #openstack-meeting20:58
*** annegentle has joined #openstack-meeting20:59
ttxo/20:59
russellbo/20:59
annegentleo/20:59
dhellmanno/20:59
stevebaker\o20:59
*** terryw is now known as otherwiseguy21:00
annegentleare we righties or lefties?21:00
russellbstevebaker waves like that because he's in the southern hemisphere21:00
* dhellmann is filling in for jd__ tonight21:00
* annegentle laughs21:00
dolphmo/21:00
ttxmarkmc, notmyname, markwash, jgriffith, gabrielhurley, markmcclain: around ?21:00
ttxdhellmann: noted21:00
gabrielhurley\o21:00
markwasho/21:00
markmcclaino/21:00
* stevebaker is holding a cup of tea21:00
notmynamehere21:00
devananda\o21:00
ttxmissing markmc and jgriffith, let's start21:01
ttx#startmeeting project21:01
openstackMeeting started Tue Jul  9 21:01:19 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** openstack changes topic to " (Meeting topic: project)"21:01
openstackThe meeting name has been set to 'project'21:01
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:01
markmchere21:01
ttxOne week left to H2 ! We'll look into progress and defer appropriately.21:01
*** beagles has quit IRC21:01
ttx#topic General stuff21:01
*** openstack changes topic to "General stuff (Meeting topic: project)"21:01
*** novas0x2a|laptop has quit IRC21:01
ttxI created the "future" series and sent you all an email about the BP tracking changes.21:02
*** beagles has joined #openstack-meeting21:02
ttxMost of you switched already, will discuss the few that didn't yet in their respective subtopics.21:02
ttxsdague, annegentle, jeblair/mordred: news from QA/Docs/Infra programs ?21:02
annegentle\o21:02
ttxannegentle: go for it21:02
jeblairttx: nak21:02
*** novas0x2a|laptop has joined #openstack-meeting21:02
annegentleDocs held our monthly meeting today and weekly office hours yesterday21:03
annegentlemeeting minutes:21:03
annegentle#link http://eavesdrop.openstack.org/meetings/doc_team_meeting/2013/doc_team_meeting.2013-07-09-13.01.html21:03
annegentlelots of discussion about Compute v3 api doc plan21:03
annegentleand Admin docs -- big or small?21:03
annegentleAlso we have Japanese and Chinese versions of the Operations Guide soon to be posted to docs.openstack.org21:03
annegentlethat's all I got21:04
ttxok, then let's move on21:04
ttx#topic Oslo status21:04
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:04
markmchey21:04
ttxmarkmc: hi!21:04
ttx#link https://launchpad.net/oslo/+milestone/havana-221:04
*** mtreinish has quit IRC21:04
markmcjust cleaning up bps a bit here, so refresh21:04
*** adjohn has joined #openstack-meeting21:04
markmcactually, had moved on to cleaning up h321:04
ttxLooking at tracked blueprints you're 71% implemented, 29% under review21:05
ttxLooks very good to me21:05
markmcyeah, and those reviews all are plausible for next week21:05
ttxOK so the last 2 "medium" on track to make it ?21:05
*** egallen has quit IRC21:05
markmcand then I need to hook up oslo.config docs21:05
markmcyeah, they look ok21:05
*** carl_baldwin has joined #openstack-meeting21:05
*** sleepsonthefloor has quit IRC21:05
ttxOK, no particular worry from me21:06
markmch3 plan is definitely a bit more up in the air21:06
ttxmarkmc: anything you wanted to raise ?21:06
*** cp16net is now known as cp16net|away21:06
ttxmarkmc: yes, it's a bit more crowded, but if everything in h2 makes it you might be ok21:06
markmcstuff like oslo.messaging and secure messaging definitely in question21:06
*** sleepsonthefloor has joined #openstack-meeting21:06
markmcthat's it from me21:06
* ttx doesn't really expect secure messaging to make it. We'll discuss in the next weeks but21:06
*** egallen has joined #openstack-meeting21:07
ttxwithout the prereq in it sounds very unlikely21:07
* markmc needs to check on kds progress21:07
ttxQuestions about Oslo ?21:07
*** marun has joined #openstack-meeting21:08
ttx#topic Keystone status21:08
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:08
dolphmo/21:08
ttxdolphm: hello!21:08
*** thingee has joined #openstack-meeting21:08
ttx#link https://launchpad.net/keystone/+milestone/havana-221:08
ttxI see you did some updates today21:08
dolphmlots!21:08
dolphmwe went through every bp targetted at h2 today during the keystone meeting21:08
ttxLooks a bit better than when i last looked into it :)21:08
ttx33% implemented, 33% under review, 33% todo21:09
ttxer21:09
*** jbresnah has joined #openstack-meeting21:09
dolphmi believe all those ones showing good progress actually have reviews up, in one state or another21:09
ttxactually makre that 28% 43% and 28%21:10
*** ayoung has quit IRC21:10
dolphmpercentages seem like overkill when there's only 9 blueprints lol21:10
*** dkranz has quit IRC21:10
ttxheh21:10
ttxAre all those still likely to make it ? Or should you just defer hte ones that are still in progress ?21:11
*** IlyaE has quit IRC21:11
ttx(since you have /some/ room left in H3)21:11
dolphmconsidering they're actually in review, i have a lot of confidence they'll make it21:11
ttxdolphm: should they be switched to "needs code review" then ? Are they fully proposed ?21:12
*** colinmcnamara has quit IRC21:12
*** jhenner has joined #openstack-meeting21:12
ttx(pluggable-token-format and catalog-optional)21:12
dolphmboth are in a bit too much flux to say they're ready for review21:13
ttxok21:13
ttxdolphm: Anything more about Keystone ?21:13
dolphmthey're technically complete, but have remaining todo's21:13
dolphmdon't believe so!21:13
ttxQuestions about Keystone anyone ?21:13
ttx#topic Ceilometer status21:14
*** openstack changes topic to "Ceilometer status (Meeting topic: project)"21:14
ttxdhellmann: hey21:14
dhellmanno/21:14
ttx#link https://launchpad.net/ceilometer/+milestone/havana-221:14
dhellmannwe have a lot of code up for review right now21:14
dhellmannand a couple of low priority items that haven't been started21:14
*** boris-42 has quit IRC21:14
dhellmannI expect us to review that list on Thursday during this week's meeting21:14
dhellmannoh, and jd__ said he has people working on the open bugs, so we expect to land those, too21:15
ttxLooking good with 50% done, 42% under review21:15
ttx(for the tracked stuff (> Low)21:15
ttx)21:15
*** martine_ has quit IRC21:15
ttxWas wondering if "one-meter-per-plugin" wasn't completed already ?21:15
ttxyou have more to propose ?21:16
dhellmannthere's a long stack of changes waiting for approval for that21:16
ttxok, somehow my script missed that long stack21:16
dhellmannsome of the early ones were approved, but I think folks are trying to get their own patches up for review :-)21:16
ttxWhat's the status of alarm-service-partitioner ? Still likely to make it ?21:16
dhellmannhttps://review.openstack.org/#/q/status:open+project:openstack/ceilometer+branch:master+topic:bp/one-meter-per-plugin,n,z21:17
dhellmannI haven't spoken with eglynn, but I haven't heard anything to indicate a problem21:17
ttxdhellmann: anything else you wanted to mention ?21:18
dhellmannthat's it, unless there are questions21:18
ttxQuestions on Ceilometer ?21:18
ttx#topic Swift status21:19
*** openstack changes topic to "Swift status (Meeting topic: project)"21:19
ttxnotmyname: o/21:19
notmynamehi21:19
ttxnotmyname: Should I enable the adjust_series_goal script for you right now ?21:19
ttxAt this point it would remove the series goal from object-replicator2 because it has no target milestone set.21:19
ttxYou should consider set that to 1.9.1 or future/next if you want to keep it on your radar21:19
notmynameya, I'll need to move it to next21:19
notmynamesure. go ahead and enable it21:20
ttxnotmyname: ok, will do after the meeting21:20
ttxnotmyname: anything you wanted to raise ? I guess it's a bit early to talk about your next release :)21:20
*** kebray has quit IRC21:20
notmynamewe released python-swiftclient 1.5.0 todya https://pypi.python.org/pypi/python-swiftclient/1.5.021:20
*** alexpilotti has joined #openstack-meeting21:21
notmynamethat's all I have for now21:21
ttxQuestions about Swift ?21:21
ttx#topic Glance status21:22
*** openstack changes topic to "Glance status (Meeting topic: project)"21:22
ttxmarkwash: o/21:22
ttx#link https://launchpad.net/glance/+milestone/havana-221:22
markwashgreetings21:22
*** colinmcnamara has joined #openstack-meeting21:22
markwasha few notes about the listing there21:23
markwashthe low bps are just part of Multiple Image Locations21:23
ttx40% done, 60% under review, looks good -- a bit of review effort needed now21:23
markwashthe in-progress bug is about to be merged, just waiting on jenkins to merge it ( it is already approved)21:23
markwashthe other bps are very close, I think we'll land all of them21:23
markwashI feel especially good about Multiple Image Locations and Registry Database Driver21:24
*** haomaiwang has joined #openstack-meeting21:24
ttxif the low ones are part of multiple image location... should we link them in and set them to Medium ?21:24
markwashthat or delete them21:24
ttxI'll do the linking21:24
*** michchap has quit IRC21:24
markwashthey were added very recently and aren't strictly necessary imo21:25
markwash*necessary to track independently21:25
markwashthat's all from me, we have very active reviewers this week, and I'll  keep turning the thumbscrews21:25
ttx#action ttx to link the two Low to multiple-image-locations and set them to med21:25
ttxall looks good to me21:26
ttxmarkwash: anything you wanted to mention ?21:26
markwashnope, thanks!21:26
markwashI'll clean up h3 after next week21:26
markwashdon't look now!21:27
* ttx closes his eyes21:27
ttxQuestions on Glance ?21:27
ttx#topic Neutron status21:27
*** openstack changes topic to "Neutron status (Meeting topic: project)"21:27
ttxmarkmcclain: hi!21:27
markmcclainhi21:27
ttx#link https://launchpad.net/neutron/+milestone/havana-221:27
*** haomaiwang has quit IRC21:28
ttx30% done, 64% proposed21:29
ttxlooks mostly good, lots and lots to review though21:29
markmcclainyeah.. renaming has slowed things up as folks had to rebase21:29
ttxbeen through that myself21:30
ttxHow is configurable-ip-allocation doing ?21:30
markmcclainit's revive an old patch.. either I'll fix it up tomorrow or kick it to H321:30
ttxshould it be pushed to h3 ? might make more sense to focus on reviews right now21:30
ttxok21:31
ttxhttps://blueprints.launchpad.net/neutron/+spec/hostid-vif-override is implemented but with "undefined" priority, could you set one ?21:31
ttxdoesn't really matter which at this point :)21:31
markmcclainyeah.. I'll clean it up for posterity21:32
ttxnec-plugin-test-coverage is marked implemented but has https://review.openstack.org/#/c/35807/ in progress ?21:32
markmcclainyes.. did see it in the h2 milestone21:33
markmcclains/did/did't/g21:33
ttxshould I make it "under review" ?21:33
markmcclainplease :)21:33
ttxok21:33
ttxhttps://blueprints.launchpad.net/neutron/+spec/ivs-interface-driver is marked implemented but targeted to h3... should I move it to h2 ?21:33
markmcclainyes.. I'll fix it21:34
ttxsdague raised bug 1194026 on the ML - i'd like to set it to critical and target it to H2...21:34
uvirtbotLaunchpad bug 1194026 in neutron "check_public_network_connectivity fails with timeout" [High,Confirmed] https://launchpad.net/bugs/119402621:34
ttxsomeone set it to High already21:34
ttxwould be nice to clean it up soon so that it doesn't impact the review rush to h221:35
*** woodspa_ has joined #openstack-meeting21:35
markmcclainright.. we talked about it yesterday in our meeting21:35
markmcclainhave one of our cores looking into it21:35
ttxmarkmcclain: can I bump it to criotical and target it to h2 ?21:35
markmcclainsure21:35
ttxsdague: you had another one ?21:35
sdaguemarkmcclain: cool, any chance you could set assigned on it? just to make it easy to know it's being worked21:36
markmcclainsdague: done21:36
sdaguettx: yes, there is also the issue with neutron on full gate, which is largely an issue that when you call network apis in nova...21:36
sdagueyou get different return codes on fails if nova-network or neutron is behind it21:36
sdaguethere has been some ML threads on this, another one kicked off21:37
*** woodspa has quit IRC21:37
ttxsdague: bug# ?21:37
sdagueit would be good to get this nailed soon if we think we want neutron running through full tests by H321:37
sdaguettx: there are a series of them, I don't have them all right nwo21:37
ttxsdague: ok, keep us posted on the ml21:38
sdagueyes, will do21:38
ttxmarkmcclain: About the neutron rename, is there anything left to do ?21:38
ttx(on the code side ?)21:38
markmcclainyes.. have a few integrated projects to finish updating21:38
*** comstud is now known as icanstill21:38
*** icanstill is now known as dothis21:38
*** dothis is now known as comstud21:38
ttxmarkmcclain: last time I looked there were still a few quantum-only files in bin/21:39
ttxnot sure what the plan is for those21:39
markmcclainttx: right those are for compatibility.. we're mostly using entrypoints for neutron-*21:39
ttxmarkmcclain: ok21:40
ttxmarkmcclain: I'd like to talk to you about enabling the adjust_series_goal automation, would you have some time after this meeting ?21:40
markmcclainyes21:40
ttxmarkmcclain: anything else you wanted to raise ?21:40
markmcclainnothing other than the other integrate reviews which I'll post for Nova, Horizon, and Heat21:40
ttxQuestions on Neutron ?21:40
stevebakershould those integrate reviews make it into h2?21:41
*** woodspa_ has quit IRC21:41
ttx#topic Cinder status21:41
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:41
ttxoops21:41
ttx#undo21:41
openstackRemoving item from minutes: <ircmeeting.items.Topic object at 0x3156850>21:41
jgriffithdoh21:41
*** neelashah has quit IRC21:41
stevebakerdoes the rename need to be coordinated in this release across projects?21:42
hub_capdid sometrhing goofy just happen or am i crazy?21:42
ttxmarkmcclain: I suspect it would be good if they did ?21:42
markmcclainstevebaker: my preference is yes21:42
*** markmc has quit IRC21:42
jgriffithhub_cap: you're not crazy21:42
ttxhub_cap: you crazy :P21:42
jgriffithwell... not because of the weird thing that happened21:42
hub_capheh ya21:42
hub_capsry for distracting21:42
*** cp16net|away is now known as cp16net21:42
ttx#topic Cinder status21:42
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:42
markmcclainstevebaker: the rename was planned to be phased since both neutron and quantum clients can be installed side-by-side for now21:42
ttxjgriffith: hola!21:42
jgriffithttx: howdy21:43
ttx#link https://launchpad.net/cinder/+milestone/havana-221:43
jgriffithslowwwwww21:43
jgriffithbut I still think that most of them are going to make it by Monday21:43
ttx53% done, 13% in review21:43
ttxso a bit late, but not too bad21:44
jgriffithThe DB changes and the state machine are my only concerns21:44
*** eharney has quit IRC21:44
ttxAre all those "medium" still likely to make it ?21:44
*** jbresnah has quit IRC21:44
ttxso maybe not the The DB changes and the state machine21:44
jgriffithttx: w/ the exception of those I just called out yes21:44
ttxLooking at critical bug https://bugs.launchpad.net/bugs/1197571 ...21:44
uvirtbotLaunchpad bug 1197571 in cinder "Upper bound on keystone-client in requires causes conflict" [Critical,In progress]21:44
ttxThe review about it was abandoned ?21:45
jgriffithttx: yeah, I need to file a bug against everybody else for that one21:45
jgriffithttx: common-reqs is out of sync with everybody else21:45
jgriffithor vice versa21:45
jgriffithso cinder matches21:45
jgriffithbut others don't have the upper bound21:45
jgriffithso I can't change cinder to match without updating common21:46
ttxjgriffith: you can probably reuse the same bug, just add project tasks to it21:46
jgriffithttx: will do21:46
gabrielhurleyFWIW, Horizon is shortly going to be requiring 0.3.0 or later21:46
ttxdo it soon, looks like something we'd like fixed by h2 too21:46
gabrielhurleydue to support for the v3 auth stuff21:46
jgriffithgabrielhurley: and there's the dilema21:46
jgriffithgabrielhurley: ttx there's some issues with 3.0 it seems though21:46
jgriffithanyway... I'll look at it21:47
jgriffithregardless it's a bug21:47
gabrielhurleyyep21:47
ttxjgriffith: anything else on your mind ?21:47
jgriffithis anybody requiring 3.0 now/today?21:47
jgriffithI'd like to just sync all the projects and get it over with if possible21:47
jgriffiththen we can move together in the future21:48
gabrielhurleyunlikely since 0.3.0 was cut *for* Horizon to make v3 auth work21:48
ttxjgriffith: no idea, no time to check. Maybe start an ML thread about that21:48
jgriffithttx: k21:48
gabrielhurleywe were the guinea pigs on it21:48
ttxQuestions on Cinder ?21:48
jgriffithgabrielhurley: :)21:48
ttx#topic Nova status21:48
*** openstack changes topic to "Nova status (Meeting topic: project)"21:48
russellbo/21:48
ttxrussellb: hey21:48
ttx#link https://launchpad.net/nova/+milestone/havana-221:48
russellbdid a lot of cleanup on there today.21:48
russellbstill a ton up for review ...21:49
* ttx refreshes21:49
russellbsent a note to nova-core earlier asking for a big push on reviews this coming week21:49
ttx47% done, 37% in review21:49
*** lbragstad has quit IRC21:50
ttxgood news is you have room in H3 to defer though.21:50
russellbheh, have room?  80 blueprints in h3 already i think :-)21:50
*** roadnick has quit IRC21:50
ttxI stopped looking at "Low" ones now :P21:50
russellbah!21:50
*** roadnick has joined #openstack-meeting21:50
russellbwell then, yes, perhaps better looking then21:50
ttxLooking at the whole release plan, I'm a bit worried about two things:21:51
ttxdeprecate-baremetal-driver and deprecate-nova-network21:51
russellbso one thing that came up in the last week was that it's becoming clear that we need to include reviewer bandwidth in the planning process21:51
russellbyeah, deprecate-baremetal-driver is dependent on ironic, and sounds like it won't be ready in time21:51
ttxdevananda reported recently that ironic just might not be ready by Havana release21:51
*** jaypipes has quit IRC21:51
ttxand we don't seem to have a magic way forward to solve deprecate-nova-network in the time remaining21:51
russellbdeprecate-nova-network ... no movement there still AFAIK21:51
*** vijendar has quit IRC21:51
russellbyeah :(21:51
ttxunless vishy has a magic wand21:51
russellbi've started asking around to recruit some more help on it21:52
*** jrodom has quit IRC21:52
russellbbut even if some other start ramping up, it seems unlikely to be completed in time21:52
ttx"include reviewer bandwidth in the planning process" what do you mean by that ?21:52
russellbi mean, try to get the review team (nova-core) to help ack how much big stuff we think we can review in a cycle21:52
ttxhmm, ok21:52
*** ivasev has quit IRC21:53
ttxI think review prioritization could help though21:53
russellbmaybe i just need to communicate better about prioritizing reviews on Low vs. higher priority stuff21:53
russellbyeah :)21:53
ttxOn the bugs side, Wanted to raise bug 1198040...21:53
uvirtbotLaunchpad bug 1198040 in nova "Nova-manage no longer operating due to neutron rename" [Critical,In progress] https://launchpad.net/bugs/119804021:53
russellbso, something i need to think about more / communicate better about ...21:53
russellborly!21:53
russellbguess we should fix that21:53
ttxDo you agree we should target it to h2 ?21:53
*** jmh_ has quit IRC21:53
*** ryanpetrello has quit IRC21:53
russellbyeah21:53
russellbjust updated it21:53
russellband will review21:53
ttxrussellb: anything else you wanted to mention ?21:54
russellbdon't think so, thanks again for the blueprint process update work you did21:54
ttxAny question on Nova ?21:54
* ttx is running a bit late21:55
ttx#topic Heat status21:55
*** openstack changes topic to "Heat status (Meeting topic: project)"21:55
ttxspeeding up21:55
ttxstevebaker: o/21:55
*** michchap has joined #openstack-meeting21:55
ttx#link https://launchpad.net/heat/+milestone/havana-221:55
stevebaker\o21:55
stevebakermy gut says those 4 bps will be deferred21:55
ttx73% done, almost there21:56
stevebakerthere are a handful of reviews for bugs.21:56
ttxstevebaker: not so much room in h3 to defer though :)21:56
*** jpich has joined #openstack-meeting21:56
ttxstevebaker: we'll talk adjust_series_goal automation just after the meeting21:56
stevebakerproject meeting is in 24 hours, so I'll get some commitments then.21:56
*** jaypipes has joined #openstack-meeting21:56
stevebakerwhat is the h2 branch date?21:57
ttxEOD next tuesday21:57
ttxone week and a 10 hours from now21:57
ttxstevebaker: anything else you want to raise ?21:57
stevebakerI don't think so21:57
ttxQuestions about Heat ?21:57
ttx#topic Horizon status21:58
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:58
ttxgabrielhurley: o/21:58
*** cp16net is now known as cp16net|away21:58
ttx#link https://launchpad.net/horizon/+milestone/havana-221:58
gabrielhurley\o21:58
gabrielhurleyI'm a little uncertain about the Quantum/Neutron Security Groups bp... akihiro motoki said it was close a week ago but I haven't seen code.21:58
ttxNot too bad, 40% done, 40% under review21:59
gabrielhurleythe other ones I'm feeling good about21:59
gabrielhurleypared down the bug list too21:59
stevebakerheat-ui is in !1!21:59
gabrielhurleyyay!21:59
ttxnot a lot of room in h3 for deferrals either21:59
*** dkliban has quit IRC21:59
gabrielhurleyno, I really don't want to see these slip21:59
gabrielhurleyI'll look at kicking stuff out of H3 soon as it is21:59
jeblairgabrielhurley: can you join us in #openstack-infra after the meeting to discuss a horizon problem that is affecting the entire project?22:00
gabrielhurleysure22:00
ttxgabrielhurley: sounds good. anything else you wanted to mention ?22:00
ttxgabrielhurley: remember you have a meeting after this one22:00
ttxQuestions on Horizon ?22:00
sdagueyeh, https://pypi.python.org/pypi/django_openstack_auth has broken the gate for everyone :)22:00
gabrielhurleyjust to reiterate the bit about keystoneclient that came up in the cinder topic22:00
*** _TheDodd_ has quit IRC22:00
gabrielhurleyyeah, we'll sort it out after this meeting22:01
ttxgabrielhurley: would be great to have a thread about it on the ml, looks like it will require a bit of coordination22:01
ttx#topic Incubated projects22:01
*** openstack changes topic to "Incubated projects (Meeting topic: project)"22:01
ttxany quick question / status update ?22:01
*** joshuamckenty has joined #openstack-meeting22:01
hub_capi <3 everyone22:01
hub_capthat is all22:01
ttxsounds good :)22:01
*** Toshi has joined #openstack-meeting22:01
*** joshuamckenty has quit IRC22:02
ttxmore time next week hopefully22:02
ttx#endmeeting22:02
hub_capno worries22:02
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"22:02
openstackMeeting ended Tue Jul  9 22:02:05 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-07-09-21.01.html22:02
*** burt has quit IRC22:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-07-09-21.01.txt22:02
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-07-09-21.01.log.html22:02
ttxgabrielhurley: sorry for the lateness22:02
gabrielhurleyno worries22:02
gabrielhurley#startmeeting horizon22:02
openstackMeeting started Tue Jul  9 22:02:40 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.22:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:02
*** openstack changes topic to " (Meeting topic: horizon)"22:02
openstackThe meeting name has been set to 'horizon'22:02
gabrielhurley#topic overview22:02
*** openstack changes topic to "overview (Meeting topic: horizon)"22:02
gabrielhurleyForgive me if I'm a little distracted, I'm also talking to the infra guys about fixing the gate now that we broke it by requiring keystoneclient 0.3.022:03
jgriffith:)22:03
jcoufalhey, np :)22:03
*** mrodden has quit IRC22:06
*** michchap has quit IRC22:06
gabrielhurleybah22:06
gabrielhurleythis isn't working...22:06
gabrielhurleyquick version:22:06
gabrielhurleyH2 gets cut next week22:06
gabrielhurleywe need to review review review22:06
gabrielhurleyHeat landed today, that's awesome22:06
*** SergeyLukjanov has quit IRC22:07
*** jlucci has joined #openstack-meeting22:07
gabrielhurleywould really like to see Ceilometer get merged ASAP too22:07
gabrielhurley#topic blueprints22:07
*** openstack changes topic to "blueprints (Meeting topic: horizon)"22:07
gabrielhurleyI'm gonna let y'all give updates, so feel free to just blurt out where things are at22:08
*** IlyaE has joined #openstack-meeting22:08
*** cp16net|away is now known as cp16net22:09
jcoufalInline table editing: https://blueprints.launchpad.net/horizon/+spec/inline-table-editing22:09
jcoufal- I've designed multiple variants and there is ongoing discussions on G+ about visualization22:09
jcoufal- discussion: https://plus.google.com/u/0/115177641540718537778/posts/HxgHdpmiUcG22:09
jcoufal- last version of designs: http://people.redhat.com/~jcoufal/openstack/2013-07-08_os-inline_editation.pdf22:09
jcoufal- feel free to discuss on G+ if you have some feedback for it22:09
*** topol has quit IRC22:09
*** jhenner has quit IRC22:10
david-lylestill waiting on a review for https://blueprints.launchpad.net/horizon/+spec/domain-context22:11
david-lylepoint of protocol, is there a point where bp's can just get bumped with one +2 after being left unreviewed?22:12
jcoufalNavigation UX Enhancements: https://blueprints.launchpad.net/horizon/+spec/navigation-enhancement22:12
jcoufal- newly opened one22:12
jcoufal- on mailing list, I started 1st phase - gathering issues from all developers22:12
jcoufal- mailing list thread: http://lists.openstack.org/pipermail/openstack-dev/2013-July/011509.html22:12
jcoufal- if you have any issue with Horizon's navigation, now is good time to speak up, we will be very happy to get each of your issues reflected in proposed enhancements22:12
david-lylejcoufal: thanks for starting that btw22:13
*** timductive has joined #openstack-meeting22:13
jcoufaldavid-lyle: np22:13
jcoufaldavid-lyle: I am happy we move forward and there is interest in that issue22:14
timductiveo/22:14
lcheng2https://blueprints.launchpad.net/horizon/+spec/login-domain-support has been implemented.  Gabriel released openstack_auth 1.1.0, and it requires keystoneclient 0.3.0 for the Keystone V3 Auth support.22:14
lcheng2The requirement for keystoneclient 0.3.0 broke the horizon gating job and keeping gabrielhurley busy in the infra room. :-)22:15
*** med_ has quit IRC22:15
jcoufalI have something to discuss about openstack_auth, but will leave that under general discussion22:16
*** litong has quit IRC22:16
*** jecarey_ has quit IRC22:17
jcoufalStylesheets breakdown: https://blueprints.launchpad.net/horizon/+spec/css-breakdown22:18
jcoufal- new blueprint opened&approved for future ("next") milestone which is helping to increase maintainability of stylesheets and improve cooperation in development by splitting one big file into logical parts22:18
*** fnaval has quit IRC22:18
*** medberry_ has joined #openstack-meeting22:18
*** medberry_ is now known as med_22:18
*** med_ has joined #openstack-meeting22:18
gabrielhurleydavid-lyle: generally not recommended. sometimes I abuse my PTL power when I know something's had significant review and there's a deadline looming.22:20
gabrielhurleyjcoufal: good call on that BP22:20
gabrielhurley#topic open discussion22:20
*** openstack changes topic to "open discussion (Meeting topic: horizon)"22:20
gabrielhurleytalk freely. lol22:20
*** eharney has joined #openstack-meeting22:20
*** schwicht has quit IRC22:20
jcoufalgabrielhurley: thanks22:20
*** cliu has quit IRC22:21
david-lylethat's what I figured.  my worry is there aren't a lot of public cloud scale providers looking to Horizon, so topics specific to that aren't popular for review22:21
david-lyleof course in general reviews are lagging22:21
*** adjohn has quit IRC22:22
*** adjohn has joined #openstack-meeting22:22
*** Rafael_Gomes has joined #openstack-meeting22:22
*** jrodom has joined #openstack-meeting22:23
jcoufalgabrielhurley: one question regarding openstack_auth library - I am wondering why this is not part of Horizon. We addressed this with bug #1185713 (Focus on the first visible input at Login screen) and if we want to implement clean solution it needs to change the form attributes (HTML5 autofocus works the best). However the form is defined in openstack_auth instead of Horizon itself. Shouldn't it be part of it?22:23
uvirtbotLaunchpad bug 1185713 in horizon "When login screen is loaded, put focus on first input field (User Name)" [Low,In progress] https://launchpad.net/bugs/118571322:23
david-lyleit certainly would simplify the change process to have it integrated22:24
jpichI was chatting with Daisy and amotoki about translations last week. Daisy (the translation coordinator) was asking why we don't update Transifex automatically, it seems they would prefer it that way. I either am not familiar with the reason, or forgot it22:25
*** haomaiwang has joined #openstack-meeting22:25
jpichAlso there was an interesting question about whether to update from stable or master, and if for stable for how long (e.g. we did a translation update with the first grizzly point release)22:25
jcoufaluvirtbot: will comment on that bug tomorrow, however there is issue with the "first visible input focus" function, doesn't work well in general use22:25
gabrielhurleyjcoufal: because it's generically useful22:25
uvirtbotjcoufal: Error: "will" is not a valid command.22:25
*** fmanco has joined #openstack-meeting22:25
gabrielhurleythe goal is to eventually split out the generic django parts of Horizon from the openstack-specific parts22:25
gabrielhurleysame reason that the clients are no longer part of their project repos22:25
gabrielhurleyyou shouldn't have to install all of nova to use novaclient22:26
gabrielhurleythese things are building blocks22:26
jcoufalok. And the source is in your github? so that if I want to address the bug, I need to do PR to your repo?22:26
david-lyleproblem is Horizon has to change it to adjust to keystone changes22:27
*** adjohn has quit IRC22:27
david-lyleopenstack_auth that is22:27
david-lylethe coupling is a little tight at this point22:27
dolphmdavid-lyle: has to or wants to? if has to, then that sounds like a bug in keystone/keystoneclient22:27
*** jlucci has quit IRC22:28
david-lyledolphm: perhaps wants bordering on needs22:28
jcoufaldavid-lyle: understood22:28
*** marun has quit IRC22:29
jcoufaldavid-lyle: if I need to do change there (openstack_auth), is Gabriel's github the right place?22:29
david-lylebut as it stands, it authenticates against a keystone (API compatible) backend22:29
*** jlucci has joined #openstack-meeting22:29
david-lyleso seems like being part of openstack makes sense22:30
*** haomaiwang has quit IRC22:30
david-lylejcoufal: yes22:31
david-lyleissue a pull request22:31
*** dcramer_ has quit IRC22:33
*** michchap has joined #openstack-meeting22:33
jcoufalUX discussing tool: I am sorry for the later answers in mail thread about this topic. Anyway, when conversations about UX are getting bigger, the limitations of G+ starts to flash out. I hope we will not get stuck in discussions about discussions for long and we move forward. Mostly because I feel that UX conversations are suffering by G+ limitations. So... I put together my thoughts about expectations, tried few tools,22:33
jcoufal and if I can help with moving forward anyhow else, just let me know guys (mordred, or others).22:33
jcoufaldavid-lyle: thanks22:33
gabrielhurleyjcoufal: david-lyle: yes, historically I owned it 'cuz I wrote it and I was the only one that knew anything about it. It allowed me to iterate rapidly. that's no longer the case nor necessary22:34
gabrielhurleyit's about to be absorbed by openstack22:34
*** ayoung has joined #openstack-meeting22:34
gabrielhurleythe infra team is working on it currently22:34
jcoufalgabrielhurley: perfect22:35
david-lylewho will own it?22:35
*** dkranz has joined #openstack-meeting22:35
*** med_ has quit IRC22:35
gabrielhurleyit'll be the purview of the Horizon core team22:35
*** jrodom has quit IRC22:35
gabrielhurleyI have the keys to PyPI still, along with openstack-ci22:36
david-lyleok, great22:36
gabrielhurleyit'll just be subject to the gerrit process22:36
*** HenryG has quit IRC22:37
*** galstrom is now known as galstrom_zzz22:37
*** thingee has left #openstack-meeting22:37
david-lyleso when that happens, are we still blocked on keystone v 0.3+, my understanding from the infra room is yes22:39
*** jrodom has joined #openstack-meeting22:39
gabrielhurleyyes22:39
gabrielhurleyit's gonna take another couple days of yelling at the other projects to get this through22:39
gabrielhurleyit sounds like keystone is the main holdup, but 0.3.1 may fix things for them22:39
*** Nachi has quit IRC22:39
david-lyleok22:40
gabrielhurleyno one is entirely sure if there are other projects unable to use a 0.3.x keystoneclient22:40
*** n0ano has quit IRC22:40
dolphmgabrielhurley: no one else has pursued 0.3.x yet, to my knowledge22:40
gabrielhurley(3:39:40 PM) clarkb: I don't think keystone is the only one22:42
gabrielhurley(3:41:01 PM) clarkb: gabrielhurley: horizon also explicitly depends on keystoneclient <0.322:42
gabrielhurley(3:41:25 PM) gabrielhurley: clarkb: d'oh!22:42
gabrielhurleydavid-lyle, lcheng: we'll need to fix that22:42
gabrielhurley(3:42:17 PM) sdague: python-heatclient/requirements.txt:python-keystoneclient>=0.2,<0.322:43
gabrielhurley(3:42:23 PM) sdague: python-ceilometerclient/requirements.txt:python-keystoneclient>=0.2,<0.322:43
gabrielhurley(3:42:34 PM) sdague: ceilometer/requirements.txt:python-keystoneclient>=0.2,<0.322:43
gabrielhurley(3:42:34 PM) sdague: cinder/requirements.txt:python-keystoneclient>=0.2,<0.322:43
gabrielhurley(3:42:48 PM) sdague: horizon/requirements.txt:python-keystoneclient>=0.2,<0.322:43
*** Toshi has quit IRC22:43
david-lylehttps://review.openstack.org/#/c/36343/22:43
david-lylein review22:43
gabrielhurleyokay, so basically we need patches to all these projects in order to get to 0.3.x for our purposes22:44
david-lylewe generally wait until the openstack-auth changes go through before trying to pull it in into Horizon22:44
*** michchap has quit IRC22:44
dolphmcinder- https://review.openstack.org/#/c/35844/122:45
dolphmceilometer- https://review.openstack.org/#/c/35842/22:45
*** henrynash has quit IRC22:45
david-lylebecause the flow is a little nutty right now...  openstack-auth -> openstack-requirements -> horizon22:45
david-lyle:)22:45
jpichIt's the same than with any client update, though22:47
david-lyletrue, just convoluted22:47
*** stevemar has joined #openstack-meeting22:49
*** nati_ueno has joined #openstack-meeting22:50
*** jlucci has quit IRC22:50
*** lloydde has quit IRC22:54
gabrielhurleyokay. I think we've mostly got a plan of action now22:55
*** lloydde has joined #openstack-meeting22:55
gabrielhurleyjust to reca:, django-openstack-auth will become part of gerrit and be gated with everything else. for today we're gonna pin to a version of openstack_auth prior to the new client dependency. in the coming days we need to get patches into all the other projects to upgrade to the new keystoneclient. barring any major problems we can still land v3 auth in H2.22:56
gabrielhurleyOn the plus side, breaking everyone actually made this a much faster process.22:57
gabrielhurleyanyhow.22:57
gabrielhurleythis week22:57
gabrielhurleyreview review review!22:57
david-lylelesson learned break things22:57
gabrielhurleywe're looking good for H2 as long as we stay on it22:57
stevebakerfyi, I've just raised this so it has visiblity for h2 https://bugs.launchpad.net/horizon/+bug/119954922:57
uvirtbotLaunchpad bug 1199549 in horizon "Heat stack create fails due to extra password validation" [Undecided,New]22:58
gabrielhurleystevebaker: thanks22:58
david-lylethanks Gabriel!22:58
gabrielhurleyset the priorities and such on that bug. If we can fix that this week that'd be great.22:59
gabrielhurleyanyhow, I think that's it for this meeting22:59
gabrielhurleythanks everyone!22:59
gabrielhurley#endmeeting22:59
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"22:59
openstackMeeting ended Tue Jul  9 22:59:17 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-07-09-22.02.html22:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-07-09-22.02.txt22:59
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-07-09-22.02.log.html22:59
*** jpich has quit IRC22:59
*** dolphm has quit IRC23:00
*** egallen has quit IRC23:01
*** timductive has left #openstack-meeting23:01
*** Toshi has joined #openstack-meeting23:04
*** david-lyle has quit IRC23:05
*** jcoufal has quit IRC23:05
*** lcheng2 has quit IRC23:06
*** jrodom has quit IRC23:08
*** Toshi has quit IRC23:08
*** jrodom has joined #openstack-meeting23:09
*** zynzel has quit IRC23:10
*** zynzel has joined #openstack-meeting23:10
*** colinmcnamara has quit IRC23:10
*** fmanco has quit IRC23:11
*** fmanco has joined #openstack-meeting23:11
*** colinmcnamara has joined #openstack-meeting23:11
*** michchap has joined #openstack-meeting23:11
*** carl_baldwin has quit IRC23:12
*** markpeek has quit IRC23:13
*** adjohn has joined #openstack-meeting23:14
*** dkliban has joined #openstack-meeting23:16
*** nachi__ has quit IRC23:16
*** nachi_ has joined #openstack-meeting23:16
*** nachi has joined #openstack-meeting23:16
*** jrodom has quit IRC23:16
*** nachi has quit IRC23:16
*** nachi has joined #openstack-meeting23:16
*** nachi_ has quit IRC23:16
*** nachi_ has joined #openstack-meeting23:16
*** nachi has quit IRC23:16
*** gyee has quit IRC23:17
*** Nachi has joined #openstack-meeting23:19
*** IlyaE has quit IRC23:19
*** gyee has joined #openstack-meeting23:19
*** stevemar has quit IRC23:20
*** IlyaE has joined #openstack-meeting23:20
*** nati_ueno has quit IRC23:22
*** otherwiseguy has quit IRC23:23
*** michchap has quit IRC23:23
*** sleepsonthefloor has quit IRC23:23
*** haomaiwang has joined #openstack-meeting23:25
*** vipul is now known as vipul-away23:27
*** adjohn has quit IRC23:29
*** haomaiwang has quit IRC23:30
*** IlyaE has quit IRC23:31
*** tanisdl has quit IRC23:31
*** lpabon has quit IRC23:35
*** zhuadl has quit IRC23:36
*** vipul-away is now known as vipul23:37
*** adjohn has joined #openstack-meeting23:39
*** adalbas has quit IRC23:44
*** amytron has quit IRC23:47
*** jrodom has joined #openstack-meeting23:50
*** fmanco has quit IRC23:50
*** michchap has joined #openstack-meeting23:50
*** gongysh has joined #openstack-meeting23:50
*** ryanpetrello has joined #openstack-meeting23:54
*** colinmcnamara has quit IRC23:55
*** jrodom has quit IRC23:58
*** ryanpetrello has quit IRC23:58
*** rwsu is now known as rwsu-away23:59
*** nachi_ has quit IRC23:59

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