Tuesday, 2013-01-15

*** bencherian has quit IRC00:00
*** gyee has quit IRC00:00
*** mrodden1 has quit IRC00:01
*** mlavalle has left #openstack-meeting00:03
*** koolhead17 has quit IRC00:03
*** alexpilotti has quit IRC00:08
*** dwcramer has quit IRC00:11
*** cloudchimp has quit IRC00:14
*** mrodden has joined #openstack-meeting00:19
*** mrodden1 has joined #openstack-meeting00:20
*** mrodden has quit IRC00:23
*** dwcramer has joined #openstack-meeting00:24
*** bencherian has joined #openstack-meeting00:27
*** vkmc has quit IRC00:28
*** hemna is now known as hemnafk00:28
*** vishy is now known as vishy_zz00:36
*** ewindisch has quit IRC00:46
*** dosaboy has quit IRC00:50
*** radez is now known as radez_g0n300:51
*** AlanClark has joined #openstack-meeting00:56
*** llu_linux has joined #openstack-meeting00:58
*** jog0_ has joined #openstack-meeting00:58
*** roaet-away is now known as roaet00:59
*** enikanorov_ has joined #openstack-meeting00:59
*** EmilienM has left #openstack-meeting01:01
*** b3nt_pin has joined #openstack-meeting01:01
*** enikanorov has quit IRC01:04
*** beagles has quit IRC01:04
*** jog0 has quit IRC01:04
*** rkukura has quit IRC01:04
*** skiarxon has quit IRC01:04
*** yuanz has quit IRC01:04
*** ogelbukh has quit IRC01:04
*** dansmith has quit IRC01:04
*** llu has quit IRC01:04
*** jog0_ is now known as jog001:04
*** rkukura has joined #openstack-meeting01:04
*** skiarxon has joined #openstack-meeting01:04
*** yuanz has joined #openstack-meeting01:04
*** ogelbukh has joined #openstack-meeting01:04
*** rkukura has quit IRC01:06
*** skiarxon has quit IRC01:06
*** yuanz has quit IRC01:06
*** ogelbukh has quit IRC01:06
*** otherwiseguy has quit IRC01:06
*** rkukura has joined #openstack-meeting01:07
*** skiarxon has joined #openstack-meeting01:07
*** yuanz has joined #openstack-meeting01:07
*** ogelbukh has joined #openstack-meeting01:07
*** SumitNaiksatam has quit IRC01:08
*** skiarxon has quit IRC01:10
*** patelna_ has quit IRC01:12
*** lloydde has quit IRC01:14
*** novas0x2a|laptop has quit IRC01:24
*** skiarxon has joined #openstack-meeting01:25
*** lbragstad has joined #openstack-meeting01:26
*** dwcramer has quit IRC01:33
*** novas0x2a|laptop has joined #openstack-meeting01:33
*** colinmcnamara has quit IRC01:37
*** juice has quit IRC01:37
*** dprince has joined #openstack-meeting01:38
*** yaguang has joined #openstack-meeting01:38
*** lloydde has joined #openstack-meeting01:39
*** kaganos has quit IRC01:39
*** ctracey` is now known as ctracey01:39
*** danwent has quit IRC01:40
*** Mandell has quit IRC01:45
*** dwcramer has joined #openstack-meeting01:46
*** dprince_ has joined #openstack-meeting01:49
*** nati_ueno has quit IRC01:49
*** dprince_ has quit IRC01:50
*** dprince_ has joined #openstack-meeting01:50
*** dprince has quit IRC01:51
*** lloydde has quit IRC02:03
*** AlanClark has quit IRC02:04
*** AlanClark has joined #openstack-meeting02:04
*** novas0x2a|laptop has quit IRC02:07
*** ryanpetrello has joined #openstack-meeting02:11
*** juice has joined #openstack-meeting02:12
*** shang_ has quit IRC02:17
*** shang has joined #openstack-meeting02:18
*** salv-orlando has quit IRC02:26
*** amotoki has left #openstack-meeting02:33
*** ewindisch has joined #openstack-meeting02:39
*** adjohn has quit IRC02:43
*** llu_linux is now known as llu02:45
*** dwcramer has quit IRC02:51
*** dwcramer has joined #openstack-meeting03:05
*** shang has quit IRC03:05
*** dprince_ has quit IRC03:06
*** galthaus has quit IRC03:07
*** bencherian has quit IRC03:09
*** colinmcnamara has joined #openstack-meeting03:10
*** colinmcnamara1 has joined #openstack-meeting03:11
*** colinmcnamara has quit IRC03:11
*** sarob has quit IRC03:14
*** zhuadl has joined #openstack-meeting03:15
*** Edward_Zhang has joined #openstack-meeting03:17
*** vishy_zz is now known as vishy03:22
*** shang has joined #openstack-meeting03:22
*** vishy is now known as vishy_zz03:31
*** vishy_zz is now known as vishy03:48
*** adjohn has joined #openstack-meeting03:50
*** galthaus has joined #openstack-meeting03:52
*** galthaus has quit IRC03:53
*** shang has quit IRC04:01
*** martine_ has quit IRC04:06
*** shang has joined #openstack-meeting04:13
*** AlanClark has quit IRC04:14
*** Edward_Zhang has quit IRC04:15
*** zhuadl has quit IRC04:15
*** vishy is now known as vishy_zz04:18
*** AlanClark has joined #openstack-meeting04:20
*** adjohn has quit IRC04:30
*** yuanz has quit IRC04:36
*** zhuadl has joined #openstack-meeting04:39
*** Edward_Zhang has joined #openstack-meeting04:39
*** danwent has joined #openstack-meeting04:53
*** yuanz has joined #openstack-meeting04:55
*** yuanz has quit IRC04:56
*** yuanz has joined #openstack-meeting04:56
*** adjohn has joined #openstack-meeting04:59
*** vishy_zz is now known as vishy05:02
*** adjohn has quit IRC05:02
*** adjohn has joined #openstack-meeting05:20
*** adjohn has quit IRC05:20
*** ewindisch has quit IRC05:23
*** TonyNIU has joined #openstack-meeting05:24
*** TonyNIU has left #openstack-meeting05:24
*** rohitk has joined #openstack-meeting05:24
*** AlanClark has quit IRC05:29
*** garyk has quit IRC05:41
*** adjohn has joined #openstack-meeting05:45
*** devananda has quit IRC05:53
*** devananda has joined #openstack-meeting05:55
*** ctracey has quit IRC06:08
*** koolhead17 has joined #openstack-meeting06:21
*** colinmcnamara1 has quit IRC06:22
*** jjm3lp has quit IRC06:25
*** vishy is now known as vishy_zz06:34
*** afazekas has joined #openstack-meeting06:57
*** garyk has joined #openstack-meeting07:00
*** mrunge has joined #openstack-meeting07:09
*** mrunge has quit IRC07:10
*** Mandell has joined #openstack-meeting07:14
*** danwent has quit IRC07:14
*** andreaf has quit IRC07:20
*** andreaf has joined #openstack-meeting07:21
*** mrunge has joined #openstack-meeting07:29
*** koolhead17 has quit IRC07:35
*** rturk` has quit IRC07:38
*** jhenner has joined #openstack-meeting07:46
*** adjohn has quit IRC07:50
*** EmilienM has joined #openstack-meeting07:52
*** rafaduran has joined #openstack-meeting07:54
*** egallen has joined #openstack-meeting08:00
*** alexpilotti has joined #openstack-meeting08:02
*** afazekas is now known as _afazekas08:14
*** egallen has quit IRC08:21
*** egallen has joined #openstack-meeting08:21
*** mrunge has quit IRC09:05
*** christophk has joined #openstack-meeting09:08
*** dosaboy has joined #openstack-meeting09:09
*** derekh has joined #openstack-meeting09:12
*** derekh has joined #openstack-meeting09:12
*** yaguang has quit IRC09:18
*** dosaboy has quit IRC09:19
*** dosaboy has joined #openstack-meeting09:21
*** mrunge has joined #openstack-meeting09:22
*** darraghb has joined #openstack-meeting09:30
*** zhuadl_ has joined #openstack-meeting09:33
*** zhuadl has quit IRC09:36
*** zhuadl_ is now known as zhuadl09:36
*** Mandell has quit IRC09:38
*** afazekas has joined #openstack-meeting09:44
*** gatuus has joined #openstack-meeting09:46
*** egallen has quit IRC10:07
*** salv-orlando has joined #openstack-meeting10:07
*** christophk has quit IRC10:13
*** egallen has joined #openstack-meeting10:15
*** maurosr has quit IRC10:16
*** gatuus has quit IRC10:17
*** reed has joined #openstack-meeting10:27
*** zhuadl has quit IRC10:29
*** Edward_Zhang has quit IRC10:30
*** christophk has joined #openstack-meeting10:47
*** maurosr has joined #openstack-meeting11:00
*** rkukura has quit IRC11:40
*** christophk has quit IRC11:41
*** vkmc has joined #openstack-meeting11:46
*** almaisan-away is now known as al-maisan11:48
*** christophk has joined #openstack-meeting12:09
*** cdub_ has quit IRC12:16
*** EmilienM has left #openstack-meeting12:23
*** sandywalsh has quit IRC12:23
*** egallen has quit IRC12:31
*** sandywalsh has joined #openstack-meeting12:36
*** gongysh has quit IRC12:40
*** christophk has quit IRC12:44
*** alexpilotti has quit IRC12:54
*** alexpilotti has joined #openstack-meeting12:55
*** yugsuo has joined #openstack-meeting13:00
yugsuoa test13:01
*** ayoung has quit IRC13:06
*** zhuadl_ has joined #openstack-meeting13:07
*** zhuadl__ has joined #openstack-meeting13:09
*** EmilienM has joined #openstack-meeting13:09
*** zhuadl has joined #openstack-meeting13:11
*** zhuadl_ has quit IRC13:12
*** martine_ has joined #openstack-meeting13:12
*** Edward_Zhang has joined #openstack-meeting13:13
*** zhuadl_ has joined #openstack-meeting13:13
*** zhuadl__ has quit IRC13:14
*** zhuadl has quit IRC13:16
*** martine_ has quit IRC13:17
*** martine has joined #openstack-meeting13:17
*** zhuadl_ has quit IRC13:18
*** zhuadl has joined #openstack-meeting13:21
*** jaypipes has joined #openstack-meeting13:22
*** zhuadl_ has joined #openstack-meeting13:25
*** egallen has joined #openstack-meeting13:25
*** egallen_ has joined #openstack-meeting13:25
*** eharney has joined #openstack-meeting13:25
*** eharney has joined #openstack-meeting13:25
*** zhuadl has quit IRC13:26
*** zhuadl__ has joined #openstack-meeting13:26
*** zhuadl__ is now known as zhuadl13:26
*** eglynn_ is now known as hungry-eglynn13:26
*** christophk has joined #openstack-meeting13:26
*** galthaus has joined #openstack-meeting13:27
*** zhuadl__ has joined #openstack-meeting13:27
*** spn_ has quit IRC13:28
*** spn has joined #openstack-meeting13:29
*** egallen has quit IRC13:29
*** egallen_ is now known as egallen13:29
*** zhuadl_ has quit IRC13:29
*** zhuadl has quit IRC13:30
*** yugsuo has quit IRC13:30
*** zhuadl__ has quit IRC13:32
*** tongli has joined #openstack-meeting13:36
*** zhuadl has joined #openstack-meeting13:40
*** Edward_Zhang has quit IRC13:42
*** zhuadl_ has joined #openstack-meeting13:44
*** dosaboy has quit IRC13:44
*** dosaboy has joined #openstack-meeting13:45
*** zhuadl has quit IRC13:48
*** zhuadl has joined #openstack-meeting13:50
*** zhuadl_ has quit IRC13:50
*** zhuadl_ has joined #openstack-meeting13:55
*** zhuadl has quit IRC13:57
*** EmilienM has quit IRC13:59
*** zhuadl has joined #openstack-meeting14:00
*** AlanClark has joined #openstack-meeting14:01
*** zhuadl_ has quit IRC14:01
*** dprince has joined #openstack-meeting14:02
*** Edward_Zhang has joined #openstack-meeting14:03
*** zhuadl_ has joined #openstack-meeting14:03
*** zhuadl has quit IRC14:05
*** zhuadl has joined #openstack-meeting14:07
*** al-maisan is now known as almaisan-away14:07
*** zhuadl_ has quit IRC14:08
*** zhuadl has quit IRC14:12
*** hungry-eglynn is now known as eglynn14:12
*** dosaboy has quit IRC14:12
*** dosaboy has joined #openstack-meeting14:13
*** zhuadl has joined #openstack-meeting14:14
*** sandywalsh has quit IRC14:14
*** sandywalsh has joined #openstack-meeting14:16
*** EmilienM has joined #openstack-meeting14:17
*** zhuadl has quit IRC14:20
*** zhuadl has joined #openstack-meeting14:22
*** primeministerp has joined #openstack-meeting14:24
*** woodspa has joined #openstack-meeting14:26
*** zhuadl has quit IRC14:27
*** zhuadl has joined #openstack-meeting14:27
*** woodspa has quit IRC14:28
*** woodspa has joined #openstack-meeting14:29
*** ayoung has joined #openstack-meeting14:32
*** zhuadl has quit IRC14:32
*** jhenner1 has joined #openstack-meeting14:32
*** galthaus has joined #openstack-meeting14:35
*** galthaus has joined #openstack-meeting14:35
*** primeministerp has quit IRC14:35
*** rkukura has joined #openstack-meeting14:35
*** jhenner has quit IRC14:36
*** zhuadl has joined #openstack-meeting14:40
*** bencherian has joined #openstack-meeting14:41
*** zhuadl has quit IRC14:44
*** AlanClark has quit IRC14:45
*** vkmc has quit IRC14:46
*** vkmc has joined #openstack-meeting14:46
*** dwcramer has quit IRC14:47
*** roaet is now known as roaet-away14:48
*** mtreinish has joined #openstack-meeting14:51
*** ewindisch has joined #openstack-meeting14:56
*** radez_g0n3 is now known as radez14:56
*** bencherian has quit IRC14:57
*** alexpilotti has joined #openstack-meeting14:59
*** markvan has joined #openstack-meeting15:00
*** zhuadl has joined #openstack-meeting15:01
*** cloudchimp has joined #openstack-meeting15:01
*** christophk has quit IRC15:03
*** Edward_Zhang has quit IRC15:04
*** dprince has quit IRC15:04
*** christophk has joined #openstack-meeting15:06
*** zhuadl has quit IRC15:06
*** rkukura has quit IRC15:10
*** EmilienM has quit IRC15:11
*** mattray has joined #openstack-meeting15:11
*** dprince has joined #openstack-meeting15:13
*** roaet-away is now known as roaet15:14
*** markmcclain has joined #openstack-meeting15:18
*** luis_fdez has joined #openstack-meeting15:25
*** ryanpetrello has quit IRC15:25
*** lbragstad has quit IRC15:25
*** markvan_ has joined #openstack-meeting15:26
*** cp16net|away is now known as cp16net15:26
*** ryanpetrello has joined #openstack-meeting15:26
*** bencherian has joined #openstack-meeting15:26
*** markvan_ has quit IRC15:27
*** markvan has quit IRC15:29
*** annegentle_itsme has joined #openstack-meeting15:31
*** egallen has quit IRC15:31
*** psedlak has joined #openstack-meeting15:32
*** mikal has quit IRC15:36
*** CrackerJackMack has quit IRC15:36
*** dwcramer has joined #openstack-meeting15:37
*** mikal has joined #openstack-meeting15:37
*** pnavarro has joined #openstack-meeting15:41
*** dwcramer has quit IRC15:48
*** jhenner1 has quit IRC15:48
*** lbragstad has joined #openstack-meeting15:49
*** otherwiseguy has joined #openstack-meeting15:57
*** primeministerp has joined #openstack-meeting15:59
primeministerp#startmeeting hyper-v15:59
openstackMeeting started Tue Jan 15 15:59:28 2013 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.15:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:59
*** openstack changes topic to " (Meeting topic: hyper-v)"15:59
openstackThe meeting name has been set to 'hyper_v'15:59
primeministerpflaky webchat today15:59
primeministerpalexpilotti: morning15:59
primeministerppnavarro: er afternoon16:00
primeministerplots to discuss today16:00
alexpilottimorning!16:00
pnavarrogood morning primeministerp !16:00
primeministerphow's everyone today16:00
alexpilottihangovered!16:00
primeministerpalexpilotti: good16:00
alexpilottikidding ;-)16:00
primeministerpalexpilotti: you deserve it16:00
primeministerp;)(16:00
primeministerpok16:00
alexpilottiI still have to properly party for the release16:01
primeministerpon that note16:01
primeministerp#topic Hyper-V/Quantum16:01
*** openstack changes topic to "Hyper-V/Quantum (Meeting topic: hyper-v)"16:01
*** dwcramer has joined #openstack-meeting16:01
*** srini_g_ has joined #openstack-meeting16:01
*** spn has quit IRC16:01
*** srini_g has quit IRC16:01
*** spn has joined #openstack-meeting16:01
alexpilottiI guess that I start this one :-)16:01
ociuhandumorning all16:01
primeministerpalessandro's hard work paid off and hyper-v quantum bits were accepted in both the quantum project as well as nova16:01
primeministerpociuhandu: tavi!16:02
*** jhenner has joined #openstack-meeting16:02
primeministerpalexpilotti: feel free to continue16:02
alexpilottiprimeministerp: ok, was just waiting ;-)16:02
alexpilottiso, fater one week of reviews16:03
alexpilotti99% of them just spaces, comments, syntax, etc16:03
alexpilottiactually nothing really drastic changed from the proposed stuff16:03
alexpilottis/fater/after/ lol16:04
pnavarrohehehe16:04
primeministerphehe16:04
alexpilottiit was a very hard work, but it really paid off16:04
primeministerpyes excellent16:04
pnavarroyeah, congrats alexpilotti !16:04
primeministerpmajor milestone achieved16:04
*** ryanpetr_ has joined #openstack-meeting16:04
alexpilottigongysh, a core reviewer from IBM china helped a lot16:04
primeministerpis he on16:05
alexpilottihe's actually the first core dev to really run our stuff on Hyper-V!16:05
primeministerpwas hoping to see if he got his msdn acct16:05
primeministerpthat's great news16:05
alexpilottino, he's offline, I looked for him16:05
alexpilottiit's 00.00 am in Beijing16:05
alexpilottiso16:05
primeministerpwell offically if anyone else wants to run on hyper-v and needs msdn access, please contact me  directly16:06
primeministerpand I'll do my best to get a subscription16:06
*** mnewby has quit IRC16:06
primeministerpsorry16:06
primeministerpalexpilotti: continue pls16:06
alexpilottihe worked with me and I helped him on getting his way around on HyperV16:06
*** spn has quit IRC16:07
alexpilottiit's very good that he did that, so we have somebody else that can test our code16:07
*** ryanpetrello has quit IRC16:07
*** spn has joined #openstack-meeting16:07
alexpilottianother great news is that he tested it also connected to OVS16:07
*** vkmc has quit IRC16:07
primeministerpsecond eyes are always key16:07
alexpilottiincluding L3 tests16:07
alexpilottiand everything works very well I have to say16:08
alexpilottithanks pnavarro for your help in the initial stage of the project! :-)16:08
alexpilottiIt was very helpful to finish this in time!16:08
*** patrocinio has joined #openstack-meeting16:08
primeministerphaha no hard push like last time16:08
primeministerpalexpilotti: ok to move on?16:09
primeministerpalexpilotti: or do you want to get into any more detail16:09
alexpilottilast line as usual: please tests and feedback! :-)16:09
pnavarroit's a pleasure to work with you !16:09
primeministerpok16:09
primeministerp#topic RDP status16:10
*** openstack changes topic to "RDP status (Meeting topic: hyper-v)"16:10
primeministerpso moving on16:10
alexpilottiyep16:10
primeministerpis there a general status of the rdp-console-proxy16:10
primeministerphow far off until testable bits16:10
alexpilottithe FreeRDP-WebConnect gateway is taking shape16:10
alexpilotti3 weeks16:10
primeministerpgreat16:10
alexpilottifrom a testable alfa16:11
alexpilottiso the bad part is that the WebConnect gateway is not mantained anymore16:11
alexpilottiso we updated it to support the latest FreeRDP code16:11
primeministerpalexpilotti: were you able to push it upstream?16:11
alexpilottiThe FreeRDP itslef was broken, so I worked with Marc, the FreeRDP lead to fix it16:12
alexpilottiWe agreed with Marc to push it in the official code base16:12
alexpilottiwhich is really cool, as we don't have to mantain a separate fork16:12
primeministerpgotcha16:12
alexpilottiwhich is what killed nova-novnc16:12
primeministerpthat works out well then16:12
alexpilottiyes16:13
*** sagar_nikam has joined #openstack-meeting16:13
alexpilottiso, now we are adding the support for Hyper-V console connections to the gateway16:13
primeministerpso moving on16:13
alexpilottionce that is done, we'll add the Keystone bits for auth16:13
alexpilottiwe have a dedicated developer on it, Marius, next time I'll ask him to join16:14
primeministerpalexpilotti: i need to resurrect the customssp provider discussion16:14
primeministerpalexpilotti: that would great to get him involved16:14
alexpilottiyeah, for that one we definitely need support from MS16:14
primeministerpyes16:14
primeministerpalexpilotti: i'm fire in additional requests today16:14
primeministerper i'll16:15
alexpilottiah, BTW Marc (FreeRDP) is implementing a porting of CredSSP on Linux16:15
alexpilottithat will also be used by ReactOS16:15
*** patrocinio has left #openstack-meeting16:15
alexpilottiwe agreed to contribute on that project (CredSSP), with it as a base we will be able to have a starting point for the SSH SSP16:15
primeministerpthat's good16:16
alexpilottithis is a mid term project anyway16:16
*** dprince has quit IRC16:16
alexpilottiAh, one small extra:16:16
alexpilotti2 of our guys are woring on a .Net interface on the OPenstack RESTful APIs16:16
alexpilottias we need it for on of our projects16:16
primeministerpalexpilotti: interesting16:16
alexpilottiwe'll release that as Apache code of course16:17
primeministerpperfecto16:17
alexpilottiwe should speak with ttx to see if they fit somewhere in inclubation16:17
alexpilottilol "incubation"16:17
primeministerphehe16:17
alexpilottimy fingers needs some debug :-)16:18
primeministerpalexpilotti: maybe address that in an email thread?16:18
primeministerpalexpilotti: start the discussion16:18
alexpilottigood point16:18
alexpilottiit's fresh news anyway, we started this week16:18
*** markwash has quit IRC16:18
primeministerpthat's good to hear16:18
primeministerpanything else on rdp?16:19
alexpilottiI'll ask Adi and Gerry to join this meeting next time as well16:19
primeministerpperfect16:19
alexpilottithat's it for now16:19
primeministerpok16:19
primeministerp#topic general updates16:19
*** openstack changes topic to "general updates (Meeting topic: hyper-v)"16:19
primeministerpCirrius16:19
primeministerper16:20
alexpilottiabout typos and autocorrection:16:20
primeministerpat least i have an excuse16:20
alexpilottigoogle suggested for "CirrOS" the term "Cirrosis"16:20
*** hemna has joined #openstack-meeting16:20
pnavarroyeah, cirrosis is not cool16:21
*** eharney has quit IRC16:21
primeministerpalexpilotti: thx16:21
*** hanrahat has joined #openstack-meeting16:21
primeministerplost my window16:21
primeministerpso Linux integration services were added to CirrOS16:21
alexpilottilet me paste the link16:21
primeministerpperfect16:21
alexpilottito cut it short, I worked with smoser to make Cirros working16:21
alexpilottion Hyper-V16:21
primeministerpgreat news16:22
alexpilottiwe added the LIS and it works perfectly16:22
primeministerpalexpilotti: what's the base os on cirros16:22
alexpilottinow we have to package it in a way that the LIS don't get loaded on other hypervisors16:22
alexpilottithe kernel is the one from 12.0416:22
primeministerpgotcha16:22
alexpilotti#link https://bugs.launchpad.net/cirros/+bug/109961116:22
smoser(cirros is the base os for cirros. built from buildroot, with ubuntu kernel).16:22
uvirtbotLaunchpad bug 1099611 in cirros "Missing Hyper-V modules" [Undecided,New]16:22
alexpilottihi smoser :-)16:23
primeministerpsmoser: thx16:23
primeministerpsmoser: thanks for the help btw16:23
primeministerpsmoser: both w/ this and cloudinit bits16:23
primeministerpsmoser: greatly appreciated16:23
alexpilottiprimeministerp: smoser was super fast in packaging it for testing16:23
*** hemna_ has quit IRC16:23
alexpilottismoser: I was updating the masses here with what we did :-)16:24
primeministerpalexpilotti: shall we discuss resize?16:24
alexpilottisure16:24
primeministerpalexpilotti: will be finished prior to G316:25
primeministerpalexpilotti: or is it going to pushed to h16:25
alexpilotti"resize" will probably use CirrOS as a working VM for managing the actual resizes of Linux partitions (extx)16:25
*** ryanpetr_ has quit IRC16:25
alexpilottiresize depends on the refactoring16:26
primeministerpok16:26
alexpilottiI'll do anything possible to finish refactoring in time16:26
*** ryanpetrello has joined #openstack-meeting16:26
alexpilottiis not IMO a mandatory feature for now, as not so many customers really asked for it16:26
*** danwent has joined #openstack-meeting16:26
primeministerpalexpilotti: and after the refactor how much additional is needed to rework the original cloud.com code to be in the v2 wmi namespace?16:26
alexpilottibut it's still an important feature in Nova16:26
primeministerpdanwent: btw thanks for your help as well16:27
*** dprince has joined #openstack-meeting16:27
primeministerpdanwent: greatly appreciated16:27
alexpilottiprimeministerp: not much, between 4 and 7 days16:27
primeministerpalexpilotti: ok16:27
primeministerpalexpilotti: still attainable for G?16:27
alexpilottiV2?16:27
alexpilottivery hard16:27
primeministerpok16:27
hanrahatalexpilotti: yes thanks on the v2 wmi  ... good news16:28
*** cdub_ has joined #openstack-meeting16:28
primeministerphanrahat: huh?16:28
alexpilottihanrahat: hi Tom!16:28
*** adjohn has joined #openstack-meeting16:28
primeministerphanrahat: we're discussing moving the original cloud.com code from v1 to v216:28
primeministerphanrahat: it's not complete yet16:28
primeministerphanrahat: that's work to be done16:28
hanrahatprimeministerp: understood.  i was referring to the time estimeate16:29
hanrahatestimate16:29
primeministerphanrahat: perfect16:29
alexpilottith eoriginal cloud.com code is not exactly a show of best coding principles, to be eufemistic16:29
*** dolphm has joined #openstack-meeting16:29
primeministerpalexpilotti: we should probabably talk about the renaming16:29
alexpilottiso the sooner we clean it up and refactor it the better it will be16:29
primeministerpas well16:29
*** dolphm has joined #openstack-meeting16:29
alexpilottirenaming?16:29
*** dolphm has quit IRC16:30
primeministerpalexpilotti: the suggestion16:30
primeministerpon renaming the hyper-v16:30
alexpilottiah yeah.16:30
primeministerpin the refactor16:30
alexpilottishould we change topic?16:30
primeministerpyes16:30
alexpilottiok16:30
primeministerpto what specifically16:30
primeministerp;)16:30
*** dolphm has joined #openstack-meeting16:30
alexpilottirussellb asked to move all the Hyper-V specific options16:31
primeministerp#topic Hyper-V Specific Options16:31
*** openstack changes topic to "Hyper-V Specific Options (Meeting topic: hyper-v)"16:31
alexpilottito a [HYPERV] group16:31
primeministerpso16:31
alexpilottiit will break compatibility with older versions of course16:31
primeministerpI'm all for it16:31
primeministerpwell16:31
primeministerpwe're going to break compat once we move to v216:31
alexpilottibut the more we wait the worse it will be16:31
primeministerpthat's correct16:31
primeministerpI'm in agreement16:31
alexpilottialso the installer will take care of it for most customers16:32
*** shengjie has quit IRC16:32
primeministerpwell16:32
alexpilottiand for manual deployments we will make sure to document it well16:32
primeministerpconsidering we already got a backport request for the yet to be completed RDP code16:32
primeministerpI would imagine we would also get a back port request16:32
primeministerpfor this16:32
primeministerpcern is moving to folsom, not grizzly16:33
alexpilottihmm16:33
primeministerpi believe16:33
primeministerpcould cause some issue for thier deployment16:33
primeministerpno16:33
primeministerper now16:33
alexpilottiour Folsom code contains 10% of the features we have16:33
russellbthanks guys :)16:33
*** otherwiseguy has quit IRC16:33
alexpilottiIf they are serious about it, we should backport the entire HyperV driver16:33
primeministerprussellb: np16:33
primeministerprussellb: thanks for your help16:34
alexpilottirussellb: we didn't say yes yet! :-D16:34
primeministerpso16:34
primeministerpI'm in agreement that it should be renamed16:34
alexpilottirussellb: kidding16:34
alexpilotti+116:34
ociuhandu+116:34
russellbhappy to help with ideas on backwards compatibility if needed16:34
russellbthat's up to you guys16:34
pnavarro+116:34
alexpilottipnavarro: ?16:34
russellbeasier code change if you just don't bother16:35
primeministerprussellb: that would be great16:35
primeministerprussellb: well that is true16:35
russellbthing is ... we already have code to easily support the old option name ... but I don't think it supports the case of moving options to a new group16:35
*** christophk has quit IRC16:35
russellbwouldn't be too hard to add support for it i'm guessing ... but it's just another step that needs to be done16:35
russellbwould be a patch to cfg in oslo16:35
alexpilottirussellb: I don't think it's worth for us now16:36
primeministerpalexpilotti: let's push it to H16:36
alexpilottithe rename?16:36
*** shengjie has joined #openstack-meeting16:36
primeministerpwell16:36
alexpilottiprimeministerp: ^16:36
* primeministerp thinks16:36
primeministerpis it worth doing it now?16:36
russellbwhy not now?16:36
primeministerpmaybe i didn't understand where you were going16:36
primeministerpw/ your comment16:36
alexpilottipushing it for H means having a lot of customers having backwards compatibility issues16:36
primeministerpalexpilotti: yes I agree16:37
primeministerpok16:37
*** hemna_ has joined #openstack-meeting16:37
primeministerpwe're on the same page16:37
primeministerptha'ts the only issue i have16:37
alexpilottiok, so option rename goes for G3, ok?16:37
russellbit would be all the same option names, just in [HYPERV] instead of [DEFAULT]16:37
russellbto tidy things up a bit :)16:37
primeministerpok16:38
russellbin general, we want to move more and more things into groups as it makes sense16:38
alexpilottirussellb: what do we do with the "cross hypervisor" ones?16:38
alexpilottilike "force_config_drive"?16:38
russellbif it's cross hypervisor ... leave in [DEFAULT] for now16:39
alexpilottiwhich is also available for KVM?16:39
alexpilottirussellb: ok16:39
russellbjust the stuff that you know is hyperv specific16:39
primeministerpthat makes more sense16:39
alexpilottirussellb: ok tx, I'll ping you if I have doubts about specific options!16:40
russellbsounds good16:40
primeministerprussellb: thanks again16:40
russellbsure, np16:40
primeministerp#topic CI progress16:40
*** openstack changes topic to "CI progress (Meeting topic: hyper-v)"16:40
primeministerpso tavi and i have been working on our puppet bits16:41
*** vishy_zz is now known as vishy16:41
primeministerphopefully we'll have our first control ring up in a couple weeks16:41
primeministerpmaybe sooner16:41
primeministerpmordred: ping16:41
primeministerpso16:42
primeministerpanyone have anything additional to add?16:42
pnavarroyes16:43
primeministerpociuhandu: I think i know what the problem is w/ the puppet registration16:43
primeministerppnavarro: shoot16:43
ociuhanduprimeministerp: cool16:43
pnavarrowhat are  next steps for quantum?16:43
ociuhanduprimeministerp: keystone is 99% done16:43
ociuhanduand all "clients" are working fine16:43
primeministerpociuhandu: good16:43
ociuhandui expect the other ones to go faster now16:44
primeministerpociuhandu: i need to get moving on the other windows pieces as well16:44
ociuhanduprimeministerp: also a first "draft" for the compute node is working16:44
primeministerpociuhandu: i've been testing that this week16:44
primeministerpociuhandu: i'm sure we're missing something16:44
primeministerpwe'll find out shortly16:45
primeministerppnavarro: that's a good question16:45
primeministerppnavarro: there are bunch of different discussions going on16:45
alexpilottipnavarro: I think we should discuss it in the general discussion after the CI!16:46
pnavarroCERN guys were interested in ceilometer project, do you know if they are coding something?16:46
primeministerpalexpilotti: yes16:46
primeministerppnavarro: they mentioned interest to me a while back16:46
*** psedlak has quit IRC16:46
primeministerppnavarro: however I don't know if they are16:46
pnavarrook, sorry, I thought primeministerp was going to close the meeting16:47
primeministerppnavarro: I've always looked at cielometer as a H project16:47
pnavarrogot it !16:47
primeministerppnavarro: we can move the discussion16:47
primeministerpok16:47
primeministerpI'll close16:47
primeministerpthe meeting16:47
primeministerpthanks for the time everyone16:47
*** afazekas has quit IRC16:47
primeministerpgreat work16:47
primeministerpas usual alexpilotti16:48
primeministerpociuhandu: i'll be in touch16:48
primeministerp#closemeeting16:48
alexpilottiprimeministerp: tx! and tx pnavarro as well!16:48
primeministerp#endmeeting16:48
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:48
openstackMeeting ended Tue Jan 15 16:48:31 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:48
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-01-15-15.59.html16:48
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-01-15-15.59.txt16:48
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-01-15-15.59.log.html16:48
*** koolhead17 has joined #openstack-meeting16:49
alexpilottiprimeministerp: we moved to -hyper-v16:49
primeministerpalexpilotti: coming16:50
primeministerp#openstack-hyper-v16:50
*** colinmcnamara has joined #openstack-meeting16:51
*** joesavak has joined #openstack-meeting16:51
*** srini_g has joined #openstack-meeting16:53
*** KernelDog has joined #openstack-meeting16:54
*** john5223 has joined #openstack-meeting16:55
*** Gordonz_ has joined #openstack-meeting16:55
*** vishy is now known as vishy_zz16:56
*** hanrahat has quit IRC16:58
*** gary has joined #openstack-meeting16:58
*** gary has quit IRC16:58
*** Gordonz has quit IRC16:59
*** sarob has joined #openstack-meeting17:00
*** Gordonz_ has quit IRC17:01
*** Gordonz has joined #openstack-meeting17:02
*** srini_g_ has quit IRC17:05
*** eharney has joined #openstack-meeting17:06
*** ijw has joined #openstack-meeting17:10
*** christophk has joined #openstack-meeting17:11
*** mdomsch has joined #openstack-meeting17:12
*** gyee has joined #openstack-meeting17:12
*** nijaba_ is now known as nijaba17:13
*** nijaba has joined #openstack-meeting17:13
*** sagar_nikam has quit IRC17:14
*** rohitk has quit IRC17:16
*** otherwiseguy has joined #openstack-meeting17:18
*** cp16net is now known as cp16net|away17:22
*** Mandell has joined #openstack-meeting17:25
*** rafaduran has quit IRC17:27
*** kaganos has joined #openstack-meeting17:28
*** sarob has quit IRC17:29
*** sarob has joined #openstack-meeting17:30
*** egallen has joined #openstack-meeting17:34
*** pnavarro has quit IRC17:39
*** sarob has quit IRC17:43
*** mrodden1 has quit IRC17:43
mordredprimeministerp: morning!17:44
*** dolphm has quit IRC17:47
*** alexpilotti has quit IRC17:49
*** nati_ueno has joined #openstack-meeting17:49
*** dolphm has joined #openstack-meeting17:49
*** nati_ueno has quit IRC17:53
*** jorgew has joined #openstack-meeting17:54
*** nati_ueno has joined #openstack-meeting17:54
*** topol has joined #openstack-meeting17:57
*** kwss has joined #openstack-meeting17:58
*** dwchadwick has joined #openstack-meeting17:58
dwchadwickhello everyone18:00
*** spzala has joined #openstack-meeting18:00
*** henrynash has joined #openstack-meeting18:00
kwsshello18:00
henrynashhi18:00
topolHi18:00
jorgewHello18:00
*** brich1 has joined #openstack-meeting18:00
ayoungKeystone!   \O\   /O/  \O/    /O/18:00
dolphmdo we have a heckj around?18:01
joesavakhiya18:01
ayoungdolphm, nope18:02
dolphmalright...18:02
gyeeo/18:02
dolphm#startmeeting keystone18:02
openstackMeeting started Tue Jan 15 18:02:18 2013 UTC.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
gyeefull house today :)18:02
*** openstack changes topic to " (Meeting topic: keystone)"18:02
openstackThe meeting name has been set to 'keystone'18:02
dolphm#topic Team Membership Updates18:02
*** openstack changes topic to "Team Membership Updates (Meeting topic: keystone)"18:02
dolphmofficial welcome to henrynash and gyee :)18:02
henrynashthank you, kindly18:02
gyeelook forward to do some serious damage18:03
ayoungGood job on code reviews this past week.  Much appreciated you two18:03
*** mrodden has joined #openstack-meeting18:03
dolphmkeep it up :)18:03
henrynash:)18:03
dolphm#topic Test Coverage18:03
*** openstack changes topic to "Test Coverage (Meeting topic: keystone)"18:03
dolphmayoung: any updates?18:03
ayoungtopol, want to join the weekly Keystone meeting?18:03
topolyes18:03
topolthis is it correct?18:03
ayoungdolphm,  no major changes in test coverage has happened this week18:04
ayoungdolphm, going back one step18:04
joesavakjorgew and myself are here too. : )18:04
ayoungtopol is going to be helping out on LDAP support18:04
dolphmyay!18:04
ayoungtopol, who is the other dev with you?18:04
*** colinmcnamara has quit IRC18:04
topolsahdev will be helping too18:04
topolsay hi sahdev18:04
spzalaayoung: hi Adam, I would like to join keystone weekly meeting as well.18:04
ayoungcool18:05
spzalaHi all!18:05
dolphmspzala: /salute18:05
gyeewelcome18:05
*** dwcramer has quit IRC18:05
ayoungThis is starting to feel like a real project.18:05
topolThanks18:05
spzala:-) thanks!18:05
ayoungso, back to test coverage.  Lets open a Jenkins bug to rerun the test coverage results18:06
dolphmayoung: a bug?18:06
dolphmayoung: i.e. we lost coverage on something?18:06
ayoungdolphm, wasn't it there before and got removed?18:06
ayoungI thought you said last week that we used to run coverage on each Jenkins run18:06
ayoungotherwise RFE18:06
*** lloydde has joined #openstack-meeting18:07
ayoungShould be as simple as adding the flag to run_tests.sh, but maybe jenkins doesn;t use that18:07
dolphmah that kind of coverage18:07
ayoungyeah, unit test coverage18:07
dolphmi don't see the charting anymore on jenkins, but we have the infrastructure for it as far as i can tell18:08
*** egallen_ has joined #openstack-meeting18:08
dolphmkeystoneclient too18:08
dolphmsee tox.ini18:08
ayoungdolphm, so, for example, http://logs.openstack.org/18519/5/check/gate-keystone-python27/2010/18:09
dolphmayoung: want to tackle that?18:09
ayoungdolphm, sure18:09
ayoung#action ayoung get jenkins to generate unit test coverage report18:09
dolphm#action ayoung to trace down jenkins coverage reporting18:09
dolphmand do it twice!18:10
joesavakha18:10
dolphm#topic critical issues18:10
*** openstack changes topic to "critical issues (Meeting topic: keystone)"18:10
*** egallen has quit IRC18:10
*** egallen_ is now known as egallen18:10
*** markwash has joined #openstack-meeting18:10
dolphmi know we have a security-related fix in the works, anything else on fire?18:10
ayounghttp://wiki.openstack.org/Meetings/KeystoneMeeting18:11
dolphmayoung: yeah, criticalness appears to have dissappeared from the agenda18:11
ayoungFor everyone new, Agenda is ^^18:11
dolphmi noticed yesterday that db_sync no longer supports specifying a migration number -- need to file a bug on taht18:12
*** nachi_ has joined #openstack-meeting18:12
*** nachi has joined #openstack-meeting18:12
dolphm#action dolphm to file a bug on lack of db_sync migration number option18:12
ayoungdolphm, I don't think it is critical, but the is an issue identified by tempest WRT roles that is coming up as a bug.  I'll take it for now18:12
*** ctracey|away has joined #openstack-meeting18:12
*** ctracey|away is now known as ctracey18:12
*** nachi has joined #openstack-meeting18:13
ayoung#link http://paste.openstack.org/show/29472/18:13
ayoungjaypipes is opening/assigning18:13
dolphmcool18:13
*** cp16net|away is now known as cp16net18:13
dolphmi'll assume that's it for now18:13
dolphm#topic "Default" domain migration18:13
*** openstack changes topic to ""Default" domain migration (Meeting topic: keystone)"18:13
dolphmso, this is a topic i've only scratched the surface on, but i wanted to give everyone a heads up on what i'm doing18:14
dolphmthis is probably bp worthy, so...18:14
dolphm#action dolphm to write default-domain blueprint18:14
ayoungdolphm, how does that tie in with henrynash 's domain blueprint...18:14
dolphmanyway, we'll be creating a data migration to create a Default domain (id=default, name=Default) that will contain user/tenant resources on the V2 API18:15
ayoung#link https://blueprints.launchpad.net/keystone/+spec/domain-name-spaces18:15
henrynashdolphm: I'm already monkeying around with domains, so feel free to assign it to me :-)18:15
dolphmi assume it'll use private namespaces once that bp is implemented18:15
ayoung+118:15
gyeehenrynash, I meant to response to your domain namespace proposal18:16
dolphmany operation on the v2 API will automatically work with default domain resources (creating a new tenant on v2 will create a project in v3 in the default domain)18:16
dolphmwe may also need to special case the domain so that users can't accidentally delete it from the v3 api18:16
*** nachi has quit IRC18:16
dolphmand i'd also like to make the default_domain_id a configuration option so that users can override the behavior and delete the domain we create if they'd prefer18:16
dolphmany objections?18:17
dolphmor questions18:17
ayoungdolphm, no.18:17
ayoungdolphm, a suggestion18:17
dolphmor suggestions18:17
gyee+1 on default_domain_id18:17
henrynashdolphm: we need to also define what happens when (in v3) a user creates entities without specify a domain (e.ff. users)18:17
ayoungwe should probably gues the default domain from the DNS domain name.18:17
ayoungBut that is an install issue18:17
henrynashdo they go in the default domain?18:18
dolphmhenrynash: my thoughts-- automatically create the user in the creating user's domain18:18
dolphmsame for projects18:18
joesavak+118:18
joesavak(autlo create the userin the creating user's domain)18:18
ayoungwhy users domain and not "default" domain?18:18
topolthe same domain you plan to use for v2 tenants or are they separate?18:19
ayoungOr,  if there is more than one domain, why not force them to specify?18:19
dolphmayoung: as a v3 user, that doesn't seem intuitive to me18:19
dolphmayoung: as a v2 user, i don't care about domains, but the implementation has to18:19
ayoungdolphm, so the question is how should the V2 API behave?18:19
dolphmayoung: in terms of..?18:20
ayoungif no domain is specified.18:20
dolphmayoung: v2 api isn't domain-aware18:20
ayoungV2 create user needs to guess the domain18:20
ayoungOK,  I can go with "same as user"18:20
ayoungfor V3, lets make it default if there is only one domain, and must be specified if there is more than one?18:20
dolphmayoung: that's an interesting thought...18:20
dolphmayoung: we can apply that behavior across both API's18:21
dolphmayoung: or, hrm18:21
dolphmayoung: can users not in the default domain authenticate on the v2 api? they absolutely can't with a privately namespaced domain18:21
ayoungdolphm, I'm ok with guessing for V2.  We don;t want to break existing tools, and matching the existing user seems to make the most sense18:22
dolphm..without using ID's18:22
joesavakFYI - jorgew and i have a hard stop at 12:30 and would like to discuss multi-project/token scope18:22
dolphmi'll write the BP and ping the list18:22
henrynashdolphm: +118:22
dolphm#topic multi-project tokens in V318:22
*** openstack changes topic to "multi-project tokens in V3 (Meeting topic: keystone)"18:22
joesavakdolphm - thank you18:23
ayoungjoesavak, any change in your thinking from last discussion?18:23
dolphm#link https://review.openstack.org/#/c/19014/18:23
joesavakWe've updated to include the roles under tokens per your suggestion ayoung18:23
ayoungjoesavak, +118:24
henrynashso I think the proposal hangs together fine….as long as we are convinced we need the capability…sorry for keeping on asking about that...18:24
joesavakhenrynash: the rax use case may be unique but it could happen again. We had a swift product runnning under 1 tenant. We acquired a company (mosso) that is the compute product running under a different tenant structure18:24
jorgewSo we have two major reasons for the feature18:24
ayounghenrynash, it should not be a general use thing, but only for specific use cases that span multiple tenants18:24
jorgewand joe just mentioned one of them :-)18:24
joesavakso to do a back up of a compute instance and to store in a swift instance, we need a token capable of seeing 2 projects18:25
jorgewayoung, +118:25
ayoungthe question is how to consume them18:25
jorgewThe other is to keep in mind that V2 supported the feature at least in the contract18:25
ayoungMy thinking is that we should make a multi-project token look like a single project token, but provide the data to the application from the middleware18:25
jorgewayoung,  I agree.18:26
ayoungauth_token will just say "yep, this is OK"18:26
ayoungthe unmarshalled token data should then be in the context18:26
jorgewin fact because a resource can belong in a single project, then and the validate call can check for that the change is minimal18:26
ayoungNow, RBAC will come into play18:26
*** vkmc has joined #openstack-meeting18:27
dolphmjoesavak: v2 supported this feature in the XML contract, but the feature was lost in the JSON interpretation of that contract18:27
jorgewdolphm,  I think our implementation went ahead and added the support in JSON :-)18:27
jorgew+1 on adding support for JSON schema :-)18:27
dwchadwickseems the obvious answer, fix JSON18:28
joesavak+1 ; )18:28
dolphmayoung: we don't have a way to provide multiple projects to services underlying auth_token today, i wrote a comment in the review about how to go about supporting that18:28
ayoungdolphm, right.18:28
joesavakany questions on the use cases presented?18:29
dolphmdwchadwick: which will immediately break all clients written against the current implementation; it's too late to go back and match the intent at this point on v218:29
dwchadwickWe have an alternative use case based on federated identities18:29
ayoungdolphm, my point is that it should be possible to use a multi-project token like a single project token, perhaps based on the ordering of the projects requested.  Some projects are more equal than others.18:29
dolphmdwchadwick: please share18:29
dwchadwickWhen you present a set of identity attributes from the federated infrastructure, then these are mapped into local tenants/domains/roles18:30
ayoungdwchadwick, that uses a different middleware, correct?18:30
henrynashjoesavak:…so once we different services based on different trees, I think I get the need18:30
dwchadwickyes18:30
*** sdake has joined #openstack-meeting18:30
dwchadwickso the client is presented with a set of tenants to choose from18:30
gyeeayoung, I am not sure about the ordering18:30
dwchadwickcurrently he picks just one, but can swap to another one later if he wants to18:31
gyeedepending on ordering is too easy for implementations to screw up18:31
dwchadwickso the client has a set of accounts he can use from his single authentication session. Thus it should be possible to support this with keystone tokens18:31
*** Nachi has joined #openstack-meeting18:31
dolphmsimply migrating a resource from ownership by project A to ownership by project B requires authz on both projects (which is a use case requested on the mailing list recently)18:31
dwchadwickthat is a different case to the one I am talking about18:32
dolphmgranted you could implement it with multiple tokens18:32
ayoungdolphm, I have to say, I really don't like the _build_user_headers  aspect of auth_token middleware.  It feels wrong18:32
ayoungBut, if we must...18:32
ayoungX_TENANT_IDS,  X_TENANT_NAMES ...18:32
ayoungcomma separated18:33
ayoungX_ROLES...ugh18:33
dolphmayoung: what if the name includes a comma?18:33
*** sivel has joined #openstack-meeting18:33
gyeeor in chinese? :)18:33
dolphmgyee: right18:33
*** jorgew1 has joined #openstack-meeting18:33
ayoung<lando>This deal is getting worse all the time! </lando>18:33
dolphmi think you need to JSON encode a list of strings (w/ unicode support)18:34
ayoungdolphm, and, since this is all consumed by the WSGI app after the auth_token middleware, it should all be in the context, and not in custom headers18:34
*** Ryan_Lane has joined #openstack-meeting18:34
*** nati_ueno has quit IRC18:34
gyeeI think various context are built from the headers right now18:35
*** jorgew has quit IRC18:35
dolphmayoung: i'm not aware of another way to communicate between middleware layers except through the environment18:35
gyeewe can stash the entire token access into the env18:36
ayounggyee, yeah18:36
* dolphm runs18:36
ayounggyee, change "we can" to "we should"18:36
gyeeamen18:36
joesavakwe are diving quite deep into the implementation for multi-projects/token. Is that needed to agree on https://review.openstack.org/#/c/19014/ ?18:37
dolphmthen you're expecting underlying services to understand identity api v2, v3, v4, etc18:37
dolphmwhich is not their responsibility18:37
*** alexpilotti has joined #openstack-meeting18:37
gyeewe version the tokens18:38
gyeemight as well :)18:38
dolphmjoesavak: the only snag i see is that we'll also need to support multi-domain tokens since we're also going down the domain-scoped route18:38
dwchadwickYou need to move to an extensible design for the API if you can, so that new features can be added without changing the api18:38
ayoungdolphm, multi project tokens are breaking the xcontract regadless of who we break it18:38
*** garyk has quit IRC18:38
jorgew1dolphm,  really it's the middle ware that needs to understand this.  Note that a resoruce still exists in a single project18:38
dwchadwickthe attribute type-value approach solves at least part of this18:38
dwchadwickso domains would have just become yet another attribute in the set, and the API would not have needed to change to cater for domains18:38
joesavak+1 dwchadwick18:39
gyeedwchadwick, what does the attribute for project_ids like?18:39
dolphmjorgew1: the implementation spans client + server + middleware though18:39
dwchadwickproject-ID=1132418:39
gyeeservices still need to be aware of the attributes right?18:39
dwchadwickproject-ID=45657818:40
gyeefor multi-project scoping?18:40
dwchadwickyes they do, but that then becomes a config issue of the service18:40
henrynashso I think we may be getting off in the weeds here….18:40
ayoungdwchadwick, the question is not whether we can solve this in the general case.  The question is can we solve this with the existing contract.  I'm all for attribute based, but that still means changing the other projects consumption of the tokens18:40
gyeehow does that different from X-Project-IDs?18:40
ayoungWe've left the weeds behind.  We are in the woods, crossing a stream18:41
dolphm;)18:41
ayoungand I think I spotted a deer tick18:41
joesavaklol18:41
dolphmalright...18:41
dolphm#topic SQL Testing18:41
*** openstack changes topic to "SQL Testing (Meeting topic: keystone)"18:41
dolphm#link https://review.openstack.org/#/c/18519/18:41
ayoungjoesavak, I'm OK with the concept of multi-proejct tokens, but I don;'t think the existing projects can consume them yet.  Any thing consuming them needs to be a one off.18:42
dolphmayoung: ^18:42
ayoungOK, so the review above again has a test fix18:42
dolphmayoung: don't think = can't :)18:42
gyeeayoung, a great topic for the next summit18:42
joesavakayoung -  ok. thanks for everyone's attention on it.18:42
ayounghttps://review.openstack.org/#/c/18519/5/keystone/common/sql/migrate_repo/versions/009_normalize_identity_migration.py18:42
ayoungThis downgrade was not tested18:42
dolphmmy only realy issue with https://review.openstack.org/#/c/18519/ is that it's effectively stepping on the toes of tempest, which is already built for this18:43
ayoungit probably should have its own unit test, but it gets run as part of the downgrade18:43
henrynashdolpm: fyi ,we missed the v3 token discussion topic on the agenda18:43
ayoungdolphm, disagree18:43
jaypipesayoung: done: https://bugs.launchpad.net/keystone/+bug/109996618:44
uvirtbotLaunchpad bug 1099966 in keystone "Race condition when rapidly deleting and creating tokens" [Undecided,New]18:44
*** Nachi has quit IRC18:44
ayoungtempest should be feeding us test that we should be working into the unit test framework,  but we should be able to  run against live DBs as part of development18:44
*** nati_ueno has joined #openstack-meeting18:44
dolphmhenrynash: ah, i'll hit that next/last18:44
ayoungA developer shouldn't need to know about Tempest to check that Keystone works18:44
jaypipesayoung: lemme know if the information in the bug isn't enough... happy to provide more.18:44
ayoungand while sqlite is a good first approximateion,   We should be able to test against a RDBMS18:44
ayoungjaypipes, would you say it is a critical?18:45
gyeeI have bad experiences where stuff appeared to work in sqlite but blow up in mysql18:45
ayounggyee, and I don;t trust MySQL.  I want PostgrSQL18:45
gyeeso be able to test against different DBs is definitely useful18:45
jaypipesayoung: meh.. I'm just ignoring the failures in my local tempest env. But it would be nice to fix.18:46
gyeeayoung, that's the point18:46
ayoungIt was essential for LDAP, too18:46
jaypipesayoung: I could give it a go myself.18:46
jaypipesayoung: also, has nothing to do with MySQL.18:46
dolphmayoung: i don't disagree, but the same issue applies to all of openstack... hence, it's a project-wide initiative... ergo, tempest18:46
ayoungjaypipes, nah, that is part of the ongoing discussion, not on that bug18:46
jaypipesayoung: and we do run tempest against an env with a PG backend.18:46
*** vishy_zz is now known as vishy18:46
jaypipesayoung: https://jenkins.openstack.org/view/Tempest/job/gate-tempest-devstack-vm-postgres/18:47
ayoungdolphm, so the remaining changes in that bug (other than the fix to 009) are just to use teardown instead of assuming a blank database.  We could make that conditional on the URL, and assume blank fro sqlite, use teardown otherwise18:47
gyeedolphm, somebody's going to do it18:48
ayoungjaypipes, we are discussing https://review.openstack.org/#/c/18519/18:48
*** eharney has quit IRC18:48
ayoungdolphm, I think that the same approach (check the URL) probably makes sense for the rest of the unit tests.  But that will be a separate commit.  It has other issues to work through.18:48
jaypipesayoung: oh, sorry man.18:48
* jaypipes goes back into his hole.18:49
ayoungdolphm, should I move  https://review.openstack.org/#/c/18519/5/keystone/common/sql/migrate_repo/versions/009_normalize_identity_migration.py into its own review like I did the other fix?18:49
*** jorgew1 has left #openstack-meeting18:49
*** mdomsch has quit IRC18:50
dolphmjaypipes: lol your input is appreciated18:50
dolphmayoung: i would say so18:51
dolphmayoung: not that it has backport potential, but it'll still merge faster as a discrete fix18:51
ayoungdolphm, OK,  will do so.  Then I can redo the above for both upgrade test and unit tests.18:51
dolphmayoung: cool18:52
dolphm#topic v3 tokens/authn/authz etc.18:52
*** openstack changes topic to "v3 tokens/authn/authz etc. (Meeting topic: keystone)"18:52
dolphmi didn't add this, but i assume this was the API discussion in gyee's thread?18:53
henrynashguang: I added this so you had a chance to discuss18:53
ayounggood idea18:53
gyeeexcellent18:53
ayoungOK,  so I still don't really want to build multiple auth support into Keystone if we get it from Apache for free, but...18:53
ayoungI do want to be able to use basic_auth and HTML18:54
henrynashgyee: vested interest…since I need to make changes to this for both domain-scoping and name-spaces18:54
dolphmayoung: not everyone runs behind apache18:54
ayoungAnd we need a V3 API for Authentication18:54
ayoungdolphm, not yet they don't...18:54
gyeeayoung, they said you can get java for free before oracle comes in :)18:54
* ayoung twirls mustache18:54
ayoungthe use case I can see as most important is18:55
ayoungkeep ID in Mysql but auth against LDAP18:56
ayoungI'd like that to be the first supported18:56
ayoungassume that syncing users from LDAP to MySQL is done externally somehow...18:56
dolphmayoung: how does that impact the API?18:56
ayoungdolphm, that makes LDAP the first supported Auth Mechanism18:56
*** juice has quit IRC18:56
ayounginstead of Google whateveritis18:56
gyeewith auth plugin, I don't care where you store LDAP users18:57
gyeeKeystone can just be a proxy for all I care18:57
dolphmgyee: +118:57
ayounggyee,  right.  just understand that this is the single most demanded feature right now18:57
gyeesince we are going to abstract auth, token issuance, and token validation18:57
dolphmgyee: have you worked on a python API for authentication plugins?18:57
*** sarob has joined #openstack-meeting18:57
gyeeyou can effectively have your own backends18:57
gyeedolphm, not formally18:58
gyeejust have a bunch of brain farts so far18:58
dolphmgyee: {'auth': {'password'}} x.authenticate(**contents_of_object_x)18:58
dolphmwhoops18:58
*** joesavak has quit IRC18:58
*** dwchadwick has quit IRC18:58
ayoungone question:  how are we going to decide which auth mechanism to use for a given request?18:59
gyeedolphm, I'll send out a proposal for the interfaces this week, assuming we all agree on the direction18:59
dolphmgyee: {'auth': {'password': {'username': 'a', 'password': 'b'}} -> password_plugin.authenticate(username='a', password='b')18:59
ayoungDomain is the most viable option18:59
dolphmsomething like, **explode the contents of hte request that map to the name of the plugin18:59
*** colinmcnamara has joined #openstack-meeting18:59
*** colinmcnamara has quit IRC18:59
gyeeyep19:00
dolphmayoung: according to gyee's proposal, it depends on the contents of the request19:00
*** olaph has joined #openstack-meeting19:00
ayoungdolphm, that is too wide open19:00
gyeemechanism maps to the plugin seem simple enough19:00
dolphmplugins[plugin_name].authenticate(**credentials) -> resulting in -> plugins['password'].authenticate(username='a', password='b')19:01
dolphmayoung: what is too wide open for what19:01
ayoungdolphm, "based on the request"19:01
ayoungthat implies a whole policy like rules engine19:01
ayoung I'd prefer it to be something more implementable\19:01
gyeeI am not seeing any problem19:01
gyeeif we don't support a given auth mechanism, we return a 40119:02
ayounglike list the auth mechanisms in the config file, and then the domain entry has an auth mechanism specified in it19:02
*** bearovercloud has joined #openstack-meeting19:02
dolphmah, we're over time19:02
dolphmswitch to #openstack-dev ;)19:02
*** colinmcnamara has joined #openstack-meeting19:02
dolphm#endmeeting19:02
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:02
openstackMeeting ended Tue Jan 15 19:02:34 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-15-18.02.html19:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-15-18.02.txt19:02
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-01-15-18.02.log.html19:02
fungici times?19:03
clarkb*ci fun times. FTFY19:03
jeblairyay!19:04
jeblair#startmeeting infra19:04
openstackMeeting started Tue Jan 15 19:04:40 2013 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:04
*** openstack changes topic to " (Meeting topic: infra)"19:04
openstackThe meeting name has been set to 'infra'19:04
jeblairin accordance with the first item from last meeting, i'm calling this meeting infra.19:05
clarkb++19:05
* fungi cheers19:05
*** Shree has joined #openstack-meeting19:05
jeblair#action jeblair make sure wiki/calendar are updated19:05
jeblair#topic CLA19:05
*** openstack changes topic to "CLA (Meeting topic: infra)"19:05
ttxo/19:05
jeblairttx: oh, hi! while you're here... we want to call this the infra meeting, can you update the calendar entry?19:06
fungiwe've got the new cla text wrapped up i think (just needs approval/merge):19:06
fungi#link https://review.openstack.org/1933519:06
jeblairfungi: that's safe to do now?19:06
ttxdoing it now19:07
jeblairttx: (i believe i can update the wiki page)19:07
clarkbdid we get a response to fungi's question in the change ocmments?19:07
* ttx is parralelizing with an audio meeting19:07
fungiyes, it doesn't get linked anywhere until we start using gerrit clas19:07
clarkbsomething about referring to text below a point in the CLA document?19:07
jeblairclarkb: yes, latest change reflects that19:07
fungiclarkb: yep, jonathan got back to us on that19:07
jeblairclarkb: it's an inline block now19:07
ttxI'm happy to share agenda-updating privileges. [caution: trap in previous sentence]19:07
ttxinfra team meeting it is19:08
*** primeministerp has quit IRC19:08
fungiwe also need reviews on the cla implementation change itself...19:09
fungi#link https://review.openstack.org/1409919:09
fungithis is basically shifting the review-dev only bits over to apply to review.o.o as well19:09
clarkbshould we remove the WIP tag from that change?19:10
fungiit's still set to wip, but i can un-wip it if that helps. still don't want it to merge until we schedule19:10
clarkbin that case maybe its best to leave it as WIP19:10
clarkbso that nothing happens unintentionally19:10
fungiyeah, that's why i opted to advertise it in the meeting instead19:10
clarkb++19:11
jeblairfungi: cool, what about doc updates and scheduling?19:11
jeblairfungi: you had an etherpad somethere with the whole plan, right?19:12
fungii need to finish up a few bits of the documentation updates and submit a change to turn off user sync (all three should go in at the same time)19:12
fungisorry, fell off the office wireless for a moment19:12
fungi#link https://etherpad.openstack.org/cla-maintenance-201219:13
fungi(slightly in need of a rename now)19:13
fungibut i think the outstanding pieces are trivial enough we can pick adate19:13
fungier, a date19:13
*** juice has joined #openstack-meeting19:14
jeblairfungi: the communication with todd can go ahead and happen, right?19:14
jeblairabout the appsec?19:14
fungijeblair: yes, i'll sync up with him. he'll want to change that around the same time we merge the cut-over changes19:14
jeblairfungi: oh, why not now?19:15
fungijeblair: well, the cla implementation on review-dev will start working when he invalidates its appsec key19:15
fungisorry, stop working19:16
fungimaybe we want to repoint that to a dummy cgi first?19:16
fungii can do that after lunch pretty easily19:16
fungibasically a one-line change to the gerrit config and a four-line (or so) cgi19:17
jeblairfungi: yeah, let's do that and then go aheand and coordinate with todd19:17
jeblairfungi: and then when todd&co have a staging server, we can point review-dev at that19:17
fungiyep, sounds good19:17
clarkb++19:17
*** mdomsch has joined #openstack-meeting19:18
ttxjeblair: I'll have to drop in a few. We should really move that meeting at some other time some other day :)19:18
ttxanything you needed from me ?19:18
jeblairfungi: the announcement looks generally good, though i feel like http://ci.openstack.org/gerrit.html#group-management should probably be a wiki page...19:18
fungijeblair: works for me. i can do that easily enough19:19
jeblairttx: i don't think so; i think the other big thing is the wiki migration19:19
ttxI haven't worked on the main page yet. I plan to do that tomorrow.19:19
fungii'd like to make sure whatever scheduling we do for the cla cut-over doesn't intersect with the wiki final migration19:19
fungisince there are wiki bits involved19:19
jeblairwhat about sunday feb 17th?19:20
jeblairfor the cla change19:20
* fungi looks at a calendar19:20
jeblairi think that's the first time i'm available after LCA19:20
fungisure, works for me19:20
ttxjeblair: that's the weekend just before g319:20
fungiooh, right19:21
ttxa.k.a. money time19:21
jeblairsun feb 24th?19:21
clarkbthat should work for m19:21
clarkb*me19:21
fungii can do the 24th19:21
ttxSure, i'll be on ski slopes at that point :)19:21
mordred++19:21
fungiha!19:21
mordredthat's the academy awards, just fyi19:21
jeblairyeah, i'll just have to ski on saturday.  :)19:21
clarkbttx: you should tell us when all of your ski days are so that we can plan to break things then19:22
annegentle_itsmeI keep meaning to send an email to the mailing list about the wiki migration, shall I do so with a new date?19:22
jeblairmordred: annegentle_itsme we had a few things we wanted to get sorted before scheduling the date...19:23
annegentle_itsmejeblair: ah ok19:23
*** nati_ueno has quit IRC19:23
ttxhow are we doing with the openstack theme ?19:23
annegentle_itsmejeblair: I think communicating that would be good19:23
clarkbolaph: ^19:23
jeblair#topic wiki19:23
*** openstack changes topic to "wiki (Meeting topic: infra)"19:23
annegentle_itsmejeblair: that is, what's still in the works and part of the plan19:23
jeblairhttp://eavesdrop.openstack.org/meetings/ci/2013/ci.2013-01-08-19.03.html19:23
olaphhttp://openstack-wiki-instance.pmtpa.wmflabs/wiki/Main_Page19:24
ttxWe had a number of blocking issues -- get the main page ok (should be ready by tomorrow) and a base theme19:24
jeblairannegentle_itsme: the three big things are under item 6 there19:24
olaphoh, no, wait19:24
ttxany other issue we needed to solve before cutoff?19:24
jeblairRyan_Lane: ping19:24
jeblairttx: the third was the redirects19:24
Ryan_Lanedidn't get to it just yet :(19:24
annegentle_itsmejeblair: got it19:24
ttxoh right, serving everything under /19:24
jeblairso it sounds like we should give ourselves another week and see if those three things are resolved, and try to schedule a date hten19:25
jeblairolaph: how is your skin coming?19:25
ttxsounds good. My part should be covered by then19:25
annegentle_itsmejeblair: sounds very reasonable19:25
jeblair#action ttx make nice front page19:25
jeblair#action Ryan_Lane handle redirects19:25
Ryan_Laneday job is currently killing me. I should hopefully get time soonish.19:25
ttxRyan_Lane: couldn't you edit the wiki page of your job and fix it ?19:26
jeblairRyan_Lane: much appreciated.19:26
jeblairttx: you should be able to do thta19:26
Ryan_Lane:D19:26
olaphI was just trying to show it - guess it's still behind mediawiki's bastion19:26
ttxI thought EVERYTHING was wikidriven at wikimedia :P19:26
olaphwill paste.o.o handle a screenshot?19:26
Ryan_Laneit is for the most part ;)19:26
jeblairolaph: no, but you could put it on imgur19:27
*** gyee has quit IRC19:27
clarkbolaph: no, but imgur will19:27
Ryan_Laneolaph: does that link I sent not work?19:27
Ryan_Lanehttp://openstack-wiki-instance.pmtpa.wmflabs/wiki/Main_Page19:27
Ryan_Laneoh19:27
Ryan_Lanecrap19:27
Ryan_Laneof course it won't19:27
ttxunless you registered some pretty neat toplevel lately19:27
Ryan_Lanelet me give it a public IP19:27
Ryan_Lanehm. actually. let me just fix its redirects19:28
Ryan_Lanehttp://openstack-wiki-instance.instance-proxy.wmflabs.org/wiki/Main_Page19:28
jeblairRyan_Lane: css is still at the wmflabs toplevel19:28
fungii like it! very minimalist19:29
jeblairRyan_Lane: (rather, load.php)19:29
ttxfungi: looks like your website :P19:29
fungiheh19:29
* fungi likes console-based web browsers19:29
Ryan_Laneok, hit it now19:30
Ryan_Laneforce-refresh, too19:30
Ryan_LaneI know it's working this time, I hit it from a browser that doesn't have a socks proxy configured :)19:31
*** dansmith has joined #openstack-meeting19:31
jeblaircool, so things i see real quick:19:31
jeblairwe might want to use the vertial version of the logo so it's not as crowded19:31
jeblairfooter needs styling19:32
ttxlinks are lighter than regular text, feels funny19:32
*** mikal has quit IRC19:32
jeblairand the links should either be red or blue; probably red.19:32
Ryan_LaneI mentioned to olaph that links shouldn't be red19:32
jeblairhehe19:32
jeblairso most of the openstack sites have red links19:32
Ryan_Lanered links mean something in mediawiki19:32
Ryan_Lanethey mean "this is a link to a page that doesn't yet exist"19:32
jeblairon some of the CI systems that are just pages full of links, it makes your eyes bleed, so we changed them to blue19:32
Ryan_Laneblue links are links that exist19:33
olaphhttp://imgur.com/0DaRW19:33
jeblairso i think we could use mediawiki standard blue/red, but just use the openstack blue and red links19:33
Ryan_Laneolaph: heh. I got it working without the screencaps :)19:33
*** mikal has joined #openstack-meeting19:33
ttxSounds like a better logo: http://upload.wikimedia.org/wikipedia/en/thumb/4/4c/OpenStack.png/170px-OpenStack.png19:33
ttxmore vertical, square19:34
jeblairttx: yeah, that's the one19:34
jeblairthere should be one with a transparent bg19:34
olaphwill we need all the navigation/toolbox links?19:34
jeblairttx: http://www.openstack.org/assets/openstack-logo/openstack-cloud-software-vertical-small.png19:34
jeblairolaph: ^ the official version of that (and it does have a transparent bg, i just didn't know how to read that in FF)19:35
ttxalso maybe ruse the same font for something as the one in openstack.org titles19:35
ttxreuse19:35
jeblairolaph: yeah, and i think they can probably be openstack-blue too.19:35
*** spzala has quit IRC19:35
jeblairttx: that's a google-hosted woff font, so it'll take a bit more work...19:36
olaphroger that19:36
ttxah ok, we can tweak that later19:36
jeblairolaph, Ryan_Lane: is it easy to add in a woff font?19:36
Ryan_Lanewoff?19:36
*** alexpilotti has quit IRC19:36
fungimaybe long-term the tab bar across the tops of articles could be redone like the menu bar on the other ostack sites too19:36
jeblairRyan_Lane: css font-face19:36
jeblairRyan_Lane: it's probably just some more css19:36
Ryan_Laneshould be. can also use web fonts if the font doesn't exist in the browser19:36
jeblairRyan_Lane: yeah, that's what this is19:37
jeblairttx: I've been thinking we should actually host that ourselves; it'll be faster.  but of course, we should get the website in our infra first.  then that change will be easier to make.  :)19:37
ttxI think if we fix the logo and the color of the links we are good to go... then we can make the top menu more openstack like and some fonts more openstack like in v219:37
jeblairttx: +119:37
fungisounds great19:38
clarkbworks for me19:38
ttx(v2 can happen before cut-off, but won't block migration if ot doesn't)19:38
jeblair#action olaph to finish openstack skin19:38
jeblairolaph: you good?19:38
ttx(v1 of openstack skin19:38
ttx)19:38
olaphjeblair: yup19:38
jeblairgroovy19:38
* ttx disappears19:38
jeblair#topic rechecks19:38
*** openstack changes topic to "rechecks (Meeting topic: infra)"19:38
ttxooh, sounds interesting19:38
* ttx stays19:39
jeblair#link http://status.openstack.org/rechecks/19:39
jeblairquick recap: that page updates when you leave a comment like "recheck bug ####"19:39
jeblairwe merged a change to zuul to allow configuration of the message left in gerrit, so that when changes fail, we can link right to the wiki page19:40
jeblair#link http://wiki.openstack.org/GerritJenkinsGithub#Test_Failures19:40
jeblair^ has updated documentation19:40
uvirtbotjeblair: Error: "has" is not a valid command.19:40
jeblairgrumble.19:40
jeblairso the last thing is for me to write an announcement about that syntax; send it to the -dev list, and in a week, change the regex to require the new syntax19:41
jeblairi haven't written that yet, but i hope to do that RSN.19:41
jeblairany questions?19:42
clarkbsounds good to me19:43
jeblair#topic status page19:43
*** b3nt_pin is now known as beagles19:43
*** openstack changes topic to "status page (Meeting topic: infra)"19:43
jeblairreviewday is now a project in gerrit19:44
jeblairbut other than that, i don't think we've made progress on running it on static.o.o.  shouldn't be too hard though.19:44
jeblairif anyone's eager for a smallish puppet project, that would be a good one.19:45
jeblairthat's bug 108278519:45
uvirtbotLaunchpad bug 1082785 in openstack-ci "Import reviewday into OpenStack infrastructure" [High,Triaged] https://launchpad.net/bugs/108278519:45
jeblair#link https://bugs.launchpad.net/openstack-ci/+bug/108278519:45
uvirtbotLaunchpad bug 1082785 in openstack-ci "Import reviewday into OpenStack infrastructure" [High,Triaged]19:45
*** novas0x2a|laptop has joined #openstack-meeting19:46
pleia2I'll take a look at it19:46
jeblairpleia2: awesome!  go ahead and grab that bug if you like then.19:47
ttxpleia2: heh, welcome :)19:47
pleia2thanks :)19:47
jeblaircool, any other topics?19:48
jeblair#topic open discussion19:48
*** openstack changes topic to "open discussion (Meeting topic: infra)"19:48
fungidprince might want to say something about rhel-based jenkins slaves?19:48
clarkband in a related conversation our cloud providers now have quantal images19:48
fungirighteous19:48
jeblairyeah, i need to verify that branch can spin up oneiric/precise slaves still19:48
jeblairi sat down to do that last week and rackspace stopped working.19:49
*** stevebaker has quit IRC19:49
*** sdake_z has joined #openstack-meeting19:49
jeblairi'll try to do that this afternoon19:49
dprincefungi: I'm anxious to have the RHEL jenkins stuff merged!19:49
jeblairthough the branch needs one update to get the ldap change19:49
jeblairsorry, this one:19:50
jeblair    Add libsasl2-dev package to jenkins slaves.19:50
*** darraghb has quit IRC19:50
dprincejeblair: you need me to add that?19:50
jeblairdprince: that would be great19:50
dprincejeblair: will do.19:50
ttxI'd suggest to change the meeting time but i can't find a good time. I'm out of california-compatible time slots19:50
fungidprince: on rhel it'll be cyrus-sasl-devel19:51
jeblairhttps://review.openstack.org/#/c/19716/ is also in the pipeline, but maybe we can procrastinate that until after the rhel changes land19:51
*** ayoung has quit IRC19:51
clarkbI think we can procrastinate since dprince got in the queue first iirc19:51
jeblairttx: :( you're around for the next meeting, right?19:51
jeblairttx: i guess this is dinner time?19:51
ttxyes, it's eating half my dinner19:51
ttxin winter time19:52
ttxin summer time it just createes a LOOOONG meetings tunnel19:52
ttx1700 UTC is when I usually care for the kids, so not so great either19:52
clarkbfor quantal we will need to make sure puppet doesn't break to badly on it when running the slave manifests19:53
fungiany earlier than 1700 and the usa west-coasters will hate you19:53
clarkband I some people have had trouble with quantal and devstack which may need sorting19:53
ttxfungi: yeah, if I had a good alternatives I would insist, but I haven't19:54
jeblairclarkb: yeah, i think that's going to be a moderate sized project we'll need to start soon.19:54
clarkbjeblair: yeah it won't be something that gets done in an afternoon19:55
jeblairclarkb: we can start by adding some quantal slaves, and manually testing unit test jobs on them19:55
jeblairclarkb: previously, we've moved one project at a time to the new slave19:55
jeblairclarkb: and then maybe when that's done, or in parallel, tackle devstack19:56
clarkbjeblair: sounds good19:56
jeblairanything else?19:57
funginothing from me19:57
jeblairthanks everyone!19:58
jeblair#endmeeting19:58
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:58
openstackMeeting ended Tue Jan 15 19:58:05 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-01-15-19.04.html19:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-01-15-19.04.txt19:58
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-01-15-19.04.log.html19:58
*** otherwiseguy has quit IRC20:00
*** dwcramer has joined #openstack-meeting20:01
*** edgarstp has joined #openstack-meeting20:02
*** stevebaker has joined #openstack-meeting20:03
*** olaph has left #openstack-meeting20:04
*** maurosr has quit IRC20:05
ttx(no TC meeting now)20:08
ttx(next meeting is the project/release status meeting in 52 min)20:08
notmynamettx: I meant to send that email to just you. but anyway. FYI20:09
*** vipul is now known as vipul|away20:10
*** vipul|away is now known as vipul20:10
*** christophk has quit IRC20:10
ttxnotmyname: got it, thx20:11
ttxnotmyname: any idea when the milestone-proposed branch would be cut for 1.7.6 ?20:11
ttx(i.e. when you freeze for qa)20:11
notmynamethere are a couple of important patches landing now (give or take 24 hours). later this week, I think. I just sent an email to the core devs about that. waiting on responses20:13
*** Shree has quit IRC20:15
*** donaldngo has joined #openstack-meeting20:16
*** gatuus has joined #openstack-meeting20:17
*** gatuus has quit IRC20:20
*** gatuus has joined #openstack-meeting20:21
*** christophk has joined #openstack-meeting20:21
*** vipul is now known as vipul|away20:25
*** dprince has quit IRC20:28
*** dwcramer has quit IRC20:32
*** luis_fdez has quit IRC20:32
*** bencherian has quit IRC20:38
*** Vek has joined #openstack-meeting20:50
*** ayoung has joined #openstack-meeting20:53
*** gabrielhurley has joined #openstack-meeting20:56
*** jhenner has quit IRC20:57
*** markmc has joined #openstack-meeting20:57
*** markwash_ has joined #openstack-meeting20:57
*** gatuus has quit IRC20:57
*** christophk has quit IRC21:00
ttxmarkmc, heckj, bcwaldon, jgriffith, vishy, gabrielhurley, danwent: around ?21:00
bcwaldonttx: yepper21:00
vishyo/21:00
gabrielhurley\o21:00
markmcreporting for duty21:00
danwento/21:00
* Vek yawns21:00
jgriffitho/21:00
notmynamettx: here, if I can go soon21:00
ttxnotmyname: ok you go first, let me start meeting21:01
ttx#startmeeting project21:01
openstackMeeting started Tue Jan 15 21:01:14 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
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:01
ttxWe'll spend most of our time looking at grizzly-3 plans and adjusting them so that they are reasonable21:01
ttxdiscussing swift first before notmyname disappears21:01
ttx#topic Swift status21:01
*** openstack changes topic to "Swift status (Meeting topic: project)"21:01
notmynamethanks21:01
ttx#link https://launchpad.net/swift/+milestone/1.7.621:01
notmynamewe're preparing for 1.7.621:02
ttxI saw you set a tentative date during your meeting last week, which I reflected on that milestone page21:02
notmynamethings are looking good, and I think we're on track for next week21:02
notmynameI think we can cut a milestone-proposed branch later this week21:02
ttxsure, just keep me posted on when I can cut a milestone-proposed branch (when you have things frozen for QA)21:02
notmynameI'v also added a 1.8 milestone to target things against21:02
notmynamettx: will do21:03
ttxsounds good21:03
notmynameswift meeting next week (not tomorrow)21:03
notmynameI think that's all I have21:03
notmynamequestions?21:03
ttxno, that's all I had21:03
*** e0ne has joined #openstack-meeting21:03
notmynamethanks for letting me go first21:03
ttxno pb21:03
ttx#topic General announcements21:03
*** openstack changes topic to "General announcements (Meeting topic: project)"21:04
*** egallen has quit IRC21:04
ttx#info OpenStack Summit registration is open21:04
jaypipeso/21:04
ttxIf you had a contribution merged in Folsom or Grizzly, you should have received a free registration code21:04
ttxWe'll issue new codes for late grizzly contributors around grizzly-3 milestone21:04
ttxso it's not too late, hint hint21:04
ttxmarkmc, mordred, annegentle, davidkranz: Anything from Stable/CI/QA/Docs teams ?21:05
markmc#info 2012.2.3 scheduled for January 31st, aiming for RC and slushy freeze on January 24th21:05
markmcwe're behind on stable/folsom reviews21:05
markmcand there's probably a bunch of backports queued up waiting to be done21:05
* markmc will poke people for help21:05
ttxmarkmc: I'll see if I can devote a few cycles to that21:05
markmcttx, thanks21:05
davidkranzttx: We've got a lot of new contributors but nothing specific to report.21:06
ttxmordred, jeblair: anything from infra team ?21:06
annegentle_itsmeo/21:07
ttxannegentle_itsme: go ahead21:07
annegentle_itsmeI'll send an email to the mailing list about progress on the wiki migration21:07
*** Mr_T has joined #openstack-meeting21:07
annegentle_itsmebasically hoping to synch up after a few more tasks are done and the CLA is solid21:07
ttxcool, cut off before the end of month I think ?21:07
annegentle_itsmettx: sounds right21:08
ttxannegentle_itsme: anything else ?21:08
annegentle_itsmethat's it21:08
ttxOK, let's move to project-specific topics then...21:08
ttx#topic Oslo status21:08
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:08
ttx#link https://launchpad.net/oslo/+milestone/grizzly-321:08
markmcpretty light on bps this time around21:08
ttxmarkmc: that plan looks very reasonable21:08
markmcwouldn't be surprised if more come in21:09
markmcI need to get on the oslo-config release asap21:09
ttxShould amqp-rpc-fast-reply-queue be added to the grizzly series goals ?21:09
ttx(it's only "proposed" at this point)21:09
markmcmostly about figuring out what the CI tasks are21:09
markmcttx, hmm, most likely I screwed up - please fix21:09
ttxwilldo21:09
markmcah, I see .. proposed21:10
markmccommon DB needs review help21:10
ttxYou have four grizzly series blueprints without a milestone set: oslo-build, wsgi-common and no-kombu-default21:10
ttxand rpc-api-review21:10
markmcah, good point21:10
ttxIf you leave them there, they look like targets of opportunity rather than stated objectives21:10
jeblairo/21:10
markmcI'll knock all them off grizzly21:10
ttxwhich is fine by me21:10
*** kwss has quit IRC21:10
ttxyes, if you already know some of them won't make it, or some of them are definitely targeting grizzly-3, you should adjust accordingly.21:10
markmcnone of them really look like they'll happen in grizzly21:11
markmcgood catch, thanks21:11
ttxLooking at your stuff marked essential... What's the ETA for oslo-config-package ?21:11
ttxnext few weeks ?21:11
markmcyes, I'd hope so21:11
ttxok then. Anything else on the oslo topic ?21:12
markmc#action markmc chase what needs doing by CI for oslo-config21:12
markmcnope, thanks21:12
markmcoh, wait21:12
* ttx waits21:12
*** brich1 has left #openstack-meeting21:12
markmcwanted to mention monty's requirements thread21:12
markmc#link http://lists.openstack.org/pipermail/openstack-dev/2013-January/thread.html#444521:12
markmcnot strictly oslo related21:12
markmcbut it's important, cross-project, needs help :)21:13
markmcthat's it21:13
ttx#info Please see http://lists.openstack.org/pipermail/openstack-dev/2013-January/thread.html#4445 about common requirements21:13
*** vipul|away is now known as vipul21:13
jeblairthe CI part of that should be very easy...21:13
markmcjeblair, awesome21:13
jeblairthe biggest thing is getting a good starting point in the repo21:13
ttxjeblair: CI part of oslo-config-package ?21:13
*** christophk has joined #openstack-meeting21:13
ttxOK, good, would like all Essential stuf cleared as early as possible21:14
jeblairttx: the requirements repo.  but that too, probably.  :)21:14
ttxha21:14
ttx#topic Keystone status21:14
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:14
*** belliott has joined #openstack-meeting21:14
ttxanyone from keystone ? Looks like we don't have heckj yet21:14
dolphmo/ sorta21:14
*** markmc has quit IRC21:15
* dolphm apologizes for not being heckj21:15
ttxHmm, let's wait a bit to give him more time, and you can sub for him if he doesn't show up in a few21:15
ttx#topic Glance status21:15
dolphmttx: cool21:15
*** openstack changes topic to "Glance status (Meeting topic: project)"21:15
ttxbcwaldon: around ?21:15
bcwaldonttx: yes21:15
ttx#link https://launchpad.net/glance/+milestone/grizzly-321:15
ttxbcwaldon: Any idea who is going to work on glance-notifications-deux ?21:16
bcwaldonttx: back-loaded several blueprints :(21:16
bcwaldonttx: just had a conversation about that21:16
bcwaldonttx: seems like we may have someone21:16
bcwaldonwill lock that down this week21:16
ttxbcwaldon: ok. My main concern actually are the 3 "essential" blueprints21:17
bcwaldonmine as well21:17
ttxI think most of those are highly-desirable, but we /could/ release grizzly without them -- in which case "High" reflects the priority better ?21:17
bcwaldontechnically, yes21:17
ttxcould we move some of them to High to reflect that ? I would sleep better at nights21:17
bcwaldonI would keep image-sharing as essential21:17
ttxagreed21:17
bcwaldonthe other two, I am still confident about, to be clear21:17
ttxsince it's finalizing the apiv221:17
bcwaldonyes21:17
ttxI think the other two wouldn't delay the release if not complete, to be clear21:18
bcwaldonagree21:18
*** mattray has quit IRC21:18
ttxso "High" is good, really top priority, but not blocking21:18
bcwaldonfine by me21:18
ttxwill adjust21:18
*** dwalleck has joined #openstack-meeting21:18
ttxMy second concern is the number of blueprints targeted compared to the weight that was pulled in previous grizzly milestones21:19
ttxbcwaldon: will you and markwash have more time to throw at Glance in the coming month ? Or should we further cut down the number of objectives ?21:19
bcwaldoncompletely understandable concerns21:19
bcwaldonwe will have much more time during this milestone, for sure21:19
ttxthe load is pretty spread between assignees.. I think it's more the review / pushing assignees part that's lacking21:20
ttxthan pure development time21:20
bcwaldonttx: so you're blaming me, I see how it is21:20
bcwaldonwhich is totally fair :)21:20
ttxno, my point is that  it's the part that requires regular attention that causes the most problems as to be expected21:21
bcwaldonttx: if you don't see commitment pick up over the next week, you can personally punch markwash21:21
gabrielhurleyway to man up, bcwaldon21:21
ttxOK, let's go with 6 blueprints and see how it goes21:21
bcwaldonokie dokie21:22
*** otherwiseguy has joined #openstack-meeting21:22
ttxbut we'll cut down the objectives at mid-milestone if we see it's going in the same direction as g2 ;)21:22
ttxLast remark, there is atmos-storage-adapter planned for grizzly but without a milestone set, do you know when that's supposed to land ?21:22
bcwaldonttx: doubt it will land - the code showed up too late for folsom so it couldn't land21:22
bcwaldongot pushed to grizzly, yet I haven't heard back from the original author21:22
bcwaldonI can reach out21:22
ttxok, of it lands by miracle we can always add it back21:23
bcwaldonsure21:23
ttxI'll just un-series-set it, might trigger a response from assignee :)21:23
ttxAnything more on Glance ?21:23
bcwaldonnot from me!21:23
ttxbcwaldon: thanks!21:23
ttx#topic Quantum status21:23
bcwaldonttx: no, thank you21:23
*** openstack changes topic to "Quantum status (Meeting topic: project)"21:23
ttxdanwent: hi!21:24
ttx#link https://launchpad.net/quantum/+milestone/grizzly-321:24
danwenthi21:24
danwentlots of BPs :)21:24
ttxYou have a large number of blueprints that are targeted to grizzly-3 but not confirmed in the grizzly series goal (11)21:24
danwentbut only a few are high, non are essential21:24
danwentttx: i cleaned several up this morning21:24
ttxunless you accepted them recently...21:24
danwenti thought your script was running clean.21:24
ttxarh.21:25
ttxyou got me21:25
ttxAnyway, some of them look like they could be merged in a single blueprint21:25
danwentsorry, yeah, did that late21:25
jeblairttx: [quantum devstack gating if you have a sec]21:25
ttxbut you did that as well21:25
danwentttx: i eliminated a couple, and asked to combine two into one21:25
ttxAnyway, yes, that's a pretty large set of blueprints21:25
ttxI think you can succeed if you get all the code under review merged ASAP and start to focus on the rest early ?21:26
*** maurosr has joined #openstack-meeting21:26
danwentthe way i see it is that we'll get our 4 'high' blueprints, as i'll focus the team on those.  of the medium priority blueprints, those already in code review stand a good chance of making it, those that are not started will only make it if someone is really driving them.21:26
danwentinterestingly, no one is super overloaded this milestone, its just a lot of new people signing up for BPs.21:27
danwentso its hard to tell which of the medium blueprints will make it ahead of time.21:27
ttxok, that works21:27
ttxWould also be good to review the set of grizzly blueprints that don't have a milestone set at https://blueprints.launchpad.net/quantum/grizzly21:27
ttx(same remark as the other projects)21:27
ttxThere are 15 of them, and I'm pretty sure you know some of them that won't make it and should be removed from the series goal21:27
danwentttx: good point, will do21:27
ttxOthers can be kept as "targets of opportunity", time permitting.21:27
*** sarob has quit IRC21:28
danwentagreed.21:28
ttxbut somehow I doubt there will be that many :)21:28
danwentyeah, seems to work our that way, huh? :)21:28
ttxjeblair: quantum devstack gating ?21:28
jeblairhttps://review.openstack.org/#/c/19724/21:28
*** bearovercloud_ has joined #openstack-meeting21:28
danwentjeblair: yup, i gave my +1 to that earlier21:28
jeblairNachi did some analysis of failures of quantum and non-quantum devstack-gate runs21:28
*** KernelDog has quit IRC21:29
*** radez is now known as radez_g0n321:29
*** koolhead17 has quit IRC21:29
jeblairthat review addresses the largent difference in failures between them21:29
jeblairi think after that's in, we should be able to enable quantum gating21:29
jeblairwhich will affect all the projects gated on devstack-gate, of course21:29
ttxyay, more tests21:29
danwentjeblair: that's great.  we've been wanting this for a LONG time :)21:29
jeblairyes, indeed!21:29
danwentjeblair: thanks for all you help on this21:29
danwentand thanks to nachi (who doesn't seem to be online right now)21:30
ttxAnything else on Quantum ?21:30
danwentnot today21:30
ttx#topic Cinder status21:30
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:30
ttxjgriffith: hi!21:30
jgriffithHey there21:30
ttx#link https://launchpad.net/cinder/+milestone/grizzly-321:30
*** vkmc has quit IRC21:30
ttxjgriffith: Who is going to work on quotas-limits-by-voltype ?21:31
jgriffithttx: will likely be me21:31
jgriffithupdated21:31
ttxthx21:31
*** alexpilotti has joined #openstack-meeting21:31
ttxYou have 4 blueprints that were targeted to g3 but not approved in the series goal (or prioritized) yet21:31
jgriffithttx: Yeah... you caught me21:31
jgriffithttx: I'm working through things as we speak21:32
ttxYou should review them and set series goal / priority for those you accept (remove target milestone for those you don't)21:32
ttxLast remark about https://blueprints.launchpad.net/cinder/+spec/del-vols-with-snaps21:32
ttxIt's accepted in grizzly series goal... is that still an objective ?21:32
*** bearovercloud has quit IRC21:32
*** bearovercloud_ is now known as bearovercloud21:32
jgriffithI would like to remove it TBH but I wanted to catch vishy before doing so21:33
ttxgood thing he is around :)21:33
jgriffithI'll update after talking through tha tlater21:33
vishylooking21:33
jgriffithI'll yield, I'm just pretty indifferent on the whole thing21:34
jgriffithvishy: the reason I mentioned checkign with you...21:35
jgriffithvishy: There's a bug of the same topic that you logged a while back21:35
*** colinmcnamara has quit IRC21:35
jgriffithhttps://bugs.launchpad.net/cinder/+bug/97040921:35
uvirtbotLaunchpad bug 970409 in nova "Deleting volumes with snapshots should be allowed for some backends" [Low,Triaged]21:35
vishyjgriffith: I think I was filing that on behalf of others21:36
vishyso it isn't really that important to me21:36
jgriffithvishy: K21:36
jgriffithvishy: I'll give it some more thought and decide later today21:36
jgriffiththanks21:36
ttxOK, anything more in Cinder ?21:36
jgriffithNot from me21:37
ttx#topic Nova status21:37
*** openstack changes topic to "Nova status (Meeting topic: project)"21:37
ttx#link https://launchpad.net/nova/+milestone/grizzly-321:37
vishyoh hai!21:37
ttxvishy: yay, 46 blueprints21:37
vishyshould be cake!21:37
ttxMy main concern here is that the review effort to merge all the targeted low-prio stuff distracts us from getting the important stuff done and merged21:37
*** pony has joined #openstack-meeting21:37
ttxso i wonder if we can afford looking in 46 directions at the same time21:38
ttxvishy: what do you think ? Worth a try ?21:38
comstud2 eyes per person.. only need 23 people21:38
vishyttx: well I think some of those need to be cleaned out21:38
russellbprogress is so bleak on a bunch of those21:38
vishybecause they stalled21:38
russellbyeah, i think some initial cleaning will remove a bunch21:38
vishyand just got moved through the milestones21:38
ttxok, could you clean up the objectives at the next Nova meeting ?21:39
ttxyou can keep the "maybe" stuff in the grizzly series without a milestone set, I guess21:39
ttxvishy: What's the ETA of backportable-db-migrations ? You know essential stuff in last milestones keep me awake at nights21:40
vishyttx: that is just something that goes in right at the end21:40
vishyttx: we discussed last summit making 10 blank db migrations21:41
russellbthe big range of extra migration numbers?21:41
vishyso that we can backport stuff if necessary21:41
*** dhellmann is now known as dhellmann-afk21:41
vishyso there isn't any real work to be done there21:41
ttxoh. ok21:41
ttxa few random remarks then...21:41
ttxhttps://blueprints.launchpad.net/nova/+spec/cpu-entitlement is targeted to g3 but not in grizzly series21:42
ttxSame for recently-added https://blueprints.launchpad.net/nova/+spec/multi-tenancy-aggregates21:42
ttxworth reviewing in the same grizzly-3 check meeting21:42
ttxIf you keep them, set series goal and a priority21:42
ttxYou also have 21 blueprints in https://blueprints.launchpad.net/nova/grizzly that have no milestone set21:42
ttxWould be good to look into them and remove grizzly goal (or set milestone) for those you know won't make it21:43
ttx(or will)21:43
ttxFor example xenapi-config-drive and nova-direct-image-upload look like they are being worked on21:43
vishyttx: ok will look through those21:43
ttxat some point in milestone we might uise priority to prioritize the review effort, so also check that priorities reflect that21:44
ttxAny question on Nova ?21:45
*** mikal has quit IRC21:45
ttxrussellb: you add that G3 objectives review topic to the Nova meeting agenda ?21:45
russellbyes i'll add it to the agenda21:45
ttxrussellb: awesome, thx21:46
ttx#topic Horizon status21:46
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:46
ttxgabrielhurley: hey21:46
gabrielhurleyyo21:46
russellbbut i may miss the meeting, have a flight that lands 15 minutes before the meeting ... will try to join from airport21:46
ttx#link https://launchpad.net/horizon/+milestone/grizzly-321:46
ttxvishy: you will be there, right ?21:46
vishyttx: yes21:46
ttxgabrielhurley: 12 blueprints, OI see you removed a few :)21:47
ttxvishy: thx21:47
*** mikal has joined #openstack-meeting21:47
gabrielhurleythe Horizon team meeting last week was really good. I got clarity on all the blueprints that were in G3, and everything that's still there has an assignee who has actively committed to it. It's more than the last milestone, but if a couple slip that'll be okay.21:47
*** jpich has joined #openstack-meeting21:47
gabrielhurleyand yeah, anything that was blocked or hesitant I just bumped out21:47
*** tong|2 has joined #openstack-meeting21:47
ttxquantum-floating-ip depends on query-service-capabilities, which is not targeted or assigned... does that mean it's unlikely to make it ?21:47
gabrielhurleydoes it now...21:48
gabrielhurleythat link should probably be severed21:48
ttxhttps://blueprints.launchpad.net/horizon/+spec/query-service-capabilities21:48
ttxthat would fix it21:48
gabrielhurleyI think that was more of a "it would be better to implement this way" more than an "it must be implemented this way"21:49
gabrielhurleyand the feature being in Grizzly to support Quantum is more important than the larger sense of right-ness21:49
ttxok, then remove link and just mention it in whiteboard21:49
*** tongli has quit IRC21:49
ttxquantum-vnic-ordering (Medium) depends on orderable-mutiple-choice-field (Low prio) -- should I raise prio for the latter ?21:49
gabrielhurleyyeah21:49
ttxwilldo21:49
gabrielhurleythanks21:50
ttxFinally... inline-table-editing is accepted for grizzly but with no milestone set. Should it be kept that way, as a target of opportunity ?21:50
gabrielhurleyI fixed the dependency on the other one21:50
gabrielhurleyah, no that's bumped out21:50
gabrielhurleyjust didn't get fully unset21:50
*** GheRivero has joined #openstack-meeting21:50
ttxok will unset series goal as well21:50
gabrielhurleyagain, thanks21:50
ttxso that it doesn't clog views21:50
gabrielhurleyyeah21:50
ttxAnything more on Horizon ?21:50
gabrielhurleynot this week21:50
*** martine has quit IRC21:51
ttxok then, no heckj still21:51
ttx#topic Keystone status21:51
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:51
ttxdolphm: around ?21:51
dolphmttx: o/21:51
ttxyou just got promoted21:51
ttx#link https://launchpad.net/keystone/+milestone/grizzly-321:51
ttxLooks reasonable too, although it assumes a faster velocity than what you achieved in the first two milestones...21:52
dolphmguang-yee has a pretty heavily load21:52
dolphmas his bp assignments encompass v3 authentication entirely21:52
dolphmso myself and henrynash will be providing him quite a bit of support21:53
ttxsounds good21:53
ttxdolphm: you have two blueprints in the grizzly series taht are not targeted to any milestone21:53
ttxdomain-role-assignment21:53
ttxdefault-domain21:53
ttxDo you know when that's supposed to land ?21:53
dolphmttx: i just created one today, default-domain... i think that's essential to v3 utility in grizzly21:53
dolphmttx: default-domain is my top priority at the moment21:53
ttxok, so it should get added to grizzly-3 milestone target ?21:54
dolphmit's been under discussion for quite a bit amongst core contribs21:54
dolphmttx: yes21:54
ttxok willdo21:54
dolphmttx: domain role assignment is also essentially done, it was mostly a spec change that has already landed21:54
ttxso both should be in g3 ?21:54
dolphmttx: yes21:54
ttxok, will push them, adjust status for them to match21:55
ttxAnything more about Keystone ?21:55
dolphmttx: that sounds like it to me21:55
ttxwhat status should domain-role-assignment have ?21:56
ttxbeta available, needs code review or implemented ?21:56
dolphmttx: i'm checking on that now, i'll let you know after the meeting21:56
ttxsure21:56
ttx#topic Incubated projects21:57
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:57
*** sandywalsh has quit IRC21:57
ttxAnyone from Ceilometer team ?21:57
*** eharney has joined #openstack-meeting21:57
*** eharney has joined #openstack-meeting21:57
ttx#action dolphm to update status for domain-role-assignment21:57
ttxAnyone from Heat team ?21:57
stevebakery21:57
sdake#link https://launchpad.net/heat/+milestone/grizzly-321:57
sdakeour main focus for g3 is fixing bugs21:57
ttxTwo issues reported by ttx.py:21:57
ttxaws-cloudformation-init has unknown status21:57
ttxresource-properties-schema has unknown status and no priority21:58
ttxotherwise looks pretty conservative21:58
sdakei'll correct those on our wednesday meeting21:58
ttxfixing bugs is good21:58
*** kspear has joined #openstack-meeting21:58
ttxSo that plan reflects all your grizzly-3 objectives ?21:58
*** cdub_ has quit IRC21:58
stevebakeris it common to maintain a grizzly branch to build packages from?21:58
sdakea few people have asked for more blueprints for specific items, but i've asked they wait until h to implement21:58
sdakewould like our g to work properly first, features second ;)21:59
sdakegoing to open gates on h-1 for blueprints21:59
ttxok22:00
sdakeso yes, all objectives unless new bugs open22:00
ttxno more time left, anyone from Ceilometer team ?22:00
*** mdomsch has quit IRC22:00
ttxFor the record,  https://launchpad.net/ceilometer/+milestone/grizzly-3 looks good22:00
ttxceilometer crew should probably review the 28 blueprints you have with series goal = grizzly22:00
ttxAnd remove the series goal for those which won't make it22:00
ttx#endmeeting22:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:00
openstackMeeting ended Tue Jan 15 22:00:56 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-01-15-21.01.html22:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-01-15-21.01.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-01-15-21.01.log.html22:01
ttxThansk everyone22:01
ttxThanks, even22:01
*** Vek has left #openstack-meeting22:01
*** e0ne has quit IRC22:01
gabrielhurleyokay, Horizon meeting...22:02
gabrielhurley#startmeeting horizon22:02
openstackMeeting started Tue Jan 15 22:02:20 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
gabrielhurleyquick one today as far as I know22:02
gabrielhurley#topic General STatus22:02
*** openstack changes topic to "General STatus (Meeting topic: horizon)"22:02
gabrielhurleyNothing new to report since last week, really. Reviews have been happening, the G3 milestone is well-planned after our meeting last week.22:03
gabrielhurley#topic Blueprints and Bugs22:03
*** openstack changes topic to "Blueprints and Bugs (Meeting topic: horizon)"22:03
gabrielhurleyI bumped out the two blocked blueprints (Enforce RBAC from Keystone, and PKI offline validation)22:04
gabrielhurleyerr22:04
*** vishy is now known as vishy_zz22:04
gabrielhurleythe other blocked one was actually the Evacuate Host22:04
gabrielhurleybut I bumped PKI offline validation 'cuz adam didn't seem confident on completing it22:04
gabrielhurleyso same net result22:04
gabrielhurleybugs have been getting fixed, overall bug count has continued to go down instead of up, so that's great22:05
kspearhi Gabriel. Is it too late to add blueprints for G3?22:05
gabrielhurleykspear: not if you want to do the work22:05
gabrielhurleywhat did you want to file?22:05
kspearthere's a couple i have22:06
kspearone was https://blueprints.launchpad.net/horizon/+spec/add-security-group-to-instance22:06
gabrielhurleyah yes, that'd be great22:06
mrungeyes, sounds nice22:06
kspearand one i've just got around to creating22:06
kspearhttps://blueprints.launchpad.net/horizon/+spec/organised-images-display22:06
*** MarkAtwood has joined #openstack-meeting22:07
gabrielhurleysounds good. I'd like to see a proposal on how the UX there would work, but generally agreed22:08
kspearyeah, sure22:08
gabrielhurleyI think most people's plates are pretty full for G3 so would you be willing to work on those two? If so I'll accept them both into G3 and assign them to you.22:08
kspearyeah i'm fairly confident i'll have them both done22:09
gabrielhurleygreat22:09
gabrielhurleywill do22:09
kspearit's quite important for us22:09
kspearthanks22:09
gabrielhurleyman, launchpad has sooooo many fields to fill in22:10
kspearhaha, sorry to ruin the flow of the meeting22:11
gabrielhurleyno worries22:11
gabrielhurleytotally worth it to get more stuff in :-)22:11
gabrielhurleythey're all assigned and approved now22:11
kspeargreat22:11
gabrielhurleycool. one last note on bugs22:11
*** galthaus_ has joined #openstack-meeting22:11
gabrielhurleyI just want to remind folks that they should file bugs in launchpad before submitting gerrit reviews for patches. It both allows us to track what was done/fixed in a release, and also makes sure nothing escapes being properly reviewed/triaged22:12
gabrielhurleyI get lazy about it sometimes too,  but it's the right thing to do22:12
*** Mr_T has left #openstack-meeting22:12
gabrielhurleythat's about all I've got though, so I'll open it up22:12
gabrielhurley#topic General Discussion22:12
*** openstack changes topic to "General Discussion (Meeting topic: horizon)"22:13
gabrielhurleyhave at it!22:13
mrungegabriel, there are quite a few backports for folsom22:13
*** galthaus has quit IRC22:13
mrungehow do we get them in?22:13
gabrielhurleyBackports need extra-thorough review22:14
mrungeyes, I'm aware of that22:14
gabrielhurleyit helps if people can try them out against a stable/folsom devstack and apply the patch to make sure it's exactly right22:14
mrungeand there's a separate group of reviewers22:14
gabrielhurleyonly myself or someone from the stable maintenance team can actually approve them though22:14
gabrielhurleyother people can +122:14
gabrielhurleywhich is helpful22:15
mrungeyes22:15
mrungeimho, many of the backports have at least one +122:15
gabrielhurleyI can go through them and try to clear them out22:15
mrungethat would be very nice!22:15
gabrielhurleythey're slower just 'cuz the burden of testing and the penalty of getting something wrong is much higher22:15
mrungeof course22:15
gabrielhurleyI'll do that before the next meeting, though22:16
*** galthaus_ has quit IRC22:16
mrungegreat, thank you!22:16
*** nati_ueno has joined #openstack-meeting22:17
jpichLots of those Folsom patches's launchpad bugs also don't have the "Also affects folsom series" field set, which would be nice for tracking and linking with gerrit. I'd be happy to set it and keep track of backports that way, if I had the rights to set that field (need to be part of the bug supervisor team?)22:17
gabrielhurleygood point22:18
gabrielhurleyI'll see about adding you to that team22:18
* gabrielhurley dislikes launchpad22:18
jpichThanks :)22:18
mrungenice!22:19
jpichWe may have to ask Devin - https://launchpad.net/~horizon-bugs/+members#active22:19
gabrielhurleyno, I don't think it's that one22:19
gabrielhurleyI forget which group actually controls it22:19
gabrielhurleyI'll look into it22:19
jpichAh, that would explain the short list :)22:19
jpichThanks!22:19
gabrielhurley#action gabriel to figure out which launchpad group allows bug edit permissions22:19
*** gyee has joined #openstack-meeting22:20
lifelessgabrielhurley: which project ?22:20
gabrielhurleyanything else?22:20
gabrielhurleyhorizon22:20
lifelessgabrielhurley: https://launchpad.net/~horizon-bugs22:20
gabrielhurleynope22:21
lifelesshuh22:21
gabrielhurley'cuz I and several other folks have that permission22:21
gabrielhurleyand we're not in that group22:21
gabrielhurleythat group is dead22:21
lifelessgabrielhurley: you may be in https://launchpad.net/~openstack-admins22:21
gabrielhurleyI'll figure it out22:21
lifelessgabrielhurley: which also has it, transitively22:21
lifelessgabrielhurley: ok22:21
gabrielhurleyI'll investigate today22:22
lifelesshttps://launchpad.net/~horizon-drivers is the other team that would get it22:22
lifeless(triage is inherited from two roles)22:23
gabrielhurleygotcha22:23
gabrielhurleyit's probably that one22:23
gabrielhurleythat sounds familiar22:23
gabrielhurleyokay, last call for topics22:24
gabrielhurleyalright folks. that'll be it for today. have a great week!22:25
jpichThanks. You too!22:25
mrungethanks, same to you!22:25
gabrielhurley#endmeeting22:25
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:25
openstackMeeting ended Tue Jan 15 22:25:42 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-01-15-22.02.html22:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-01-15-22.02.txt22:25
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-01-15-22.02.log.html22:25
*** vkmc has joined #openstack-meeting22:25
*** roaet is now known as roaet-away22:26
*** christophk has quit IRC22:29
*** lbragstad has quit IRC22:29
*** bencherian has joined #openstack-meeting22:30
*** sandywalsh has joined #openstack-meeting22:32
*** mrunge has quit IRC22:35
*** cdub_ has joined #openstack-meeting22:35
*** annegentle_itsme has quit IRC22:36
*** gabrielhurley has quit IRC22:37
*** jpich has quit IRC22:39
*** nati_ueno has quit IRC22:41
*** sarob has joined #openstack-meeting22:42
*** bearovercloud has quit IRC22:44
*** bearovercloud has joined #openstack-meeting22:44
*** mtreinish has quit IRC22:46
*** henrynash has quit IRC22:46
*** dwalleck has quit IRC22:46
*** nati_ueno has joined #openstack-meeting22:48
*** vishy_zz is now known as vishy22:49
*** vkmc has quit IRC22:51
*** topol has quit IRC22:52
*** roaet-away is now known as roaet22:54
*** sandywalsh has quit IRC22:58
*** john5223 has quit IRC22:58
*** lbragstad has joined #openstack-meeting22:58
*** kspear has left #openstack-meeting23:00
*** woodspa has quit IRC23:01
*** stevebaker has quit IRC23:02
*** stevebaker has joined #openstack-meeting23:03
*** vkmc has joined #openstack-meeting23:04
*** dosaboy has quit IRC23:06
*** lloydde has quit IRC23:09
*** nati_ueno has quit IRC23:10
*** reed has quit IRC23:17
*** jrodom has joined #openstack-meeting23:18
*** vkmc has quit IRC23:20
*** galthaus has joined #openstack-meeting23:22
*** galthaus has quit IRC23:27
*** alexpilotti has quit IRC23:32
*** guillaume_ has joined #openstack-meeting23:39
*** gpernot has quit IRC23:39
*** edgarstp has quit IRC23:40
*** cdub_ has quit IRC23:41
*** nati_ueno has joined #openstack-meeting23:42
*** juice has quit IRC23:44
*** gongysh has joined #openstack-meeting23:44
*** ewindisch has quit IRC23:47
*** nati_ueno has quit IRC23:48
*** topol has joined #openstack-meeting23:49
*** henrynash has joined #openstack-meeting23:52
*** mrodden has quit IRC23:57

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