Tuesday, 2012-11-20

*** anniec has joined #openstack-meeting00:02
*** markwash has joined #openstack-meeting00:03
*** devanand1 has joined #openstack-meeting00:04
*** devananda has quit IRC00:05
*** pballand has quit IRC00:05
*** fnaval has joined #openstack-meeting00:06
*** fnaval has quit IRC00:06
*** fnaval has joined #openstack-meeting00:07
*** danwent has joined #openstack-meeting00:11
*** danwent has quit IRC00:16
*** adjohn has quit IRC00:24
*** markwash has quit IRC00:26
*** nati_ueno has quit IRC00:27
*** nati_ueno has joined #openstack-meeting00:28
*** nati_ueno has quit IRC00:42
*** adjohn has joined #openstack-meeting00:46
*** colinmcnamara has quit IRC00:48
*** colinmcnamara has joined #openstack-meeting00:48
*** andrewbogott is now known as andrewbogott_afk00:52
*** anniec has quit IRC00:58
*** EntropyWorks_ has joined #openstack-meeting00:59
*** EntropyW- has joined #openstack-meeting01:00
*** salv-orlando has quit IRC01:01
*** devanand1 is now known as devananda01:02
*** zhuadl has joined #openstack-meeting01:04
*** radez is now known as radez_g0n301:05
*** Mandell has quit IRC01:06
*** hemna has quit IRC01:06
*** martine has joined #openstack-meeting01:08
*** ryanpetrello has quit IRC01:10
*** ryanpetrello has joined #openstack-meeting01:12
*** EntropyW- is now known as jcooley_01:12
*** Mandell has joined #openstack-meeting01:14
*** EntropyWorks_ has quit IRC01:21
*** NobodyCam is now known as NobodyCam_afk01:22
*** eglynn_ has joined #openstack-meeting01:31
*** matiu has quit IRC01:33
*** eglynn has quit IRC01:34
*** zhuadl has quit IRC01:36
*** Mandell has quit IRC01:44
*** redthrux has quit IRC01:45
*** matiu has joined #openstack-meeting01:49
*** matiu has joined #openstack-meeting01:49
*** jcooley has quit IRC01:51
*** jcooley_ is now known as jcooley01:51
*** jcooley_ has joined #openstack-meeting01:52
*** markmcclain has quit IRC01:52
*** littleidea has quit IRC01:53
*** littleidea has joined #openstack-meeting01:56
*** jcooley_ has quit IRC01:56
*** novas0x2a|laptop has quit IRC02:01
*** martine has quit IRC02:05
*** martine_ has joined #openstack-meeting02:05
*** annegentle_ has joined #openstack-meeting02:10
*** martine_ has quit IRC02:10
*** martine_ has joined #openstack-meeting02:11
*** annegentle_ has quit IRC02:16
*** zhuadl has joined #openstack-meeting02:17
*** alexpilotti has quit IRC02:18
*** annegentle_ has joined #openstack-meeting02:19
*** zhuadl has quit IRC02:23
*** zhuadl has joined #openstack-meeting02:24
*** ywu_ has joined #openstack-meeting02:25
*** annegentle_ has quit IRC02:30
*** maoy has quit IRC02:33
*** ryanpetrello has quit IRC02:34
*** ryanpetrello has joined #openstack-meeting02:36
*** jog0_ has joined #openstack-meeting02:42
*** jog0_ has joined #openstack-meeting02:43
*** jog0__ has joined #openstack-meeting02:43
*** jog0__ has quit IRC02:43
*** jog0__ has joined #openstack-meeting02:44
*** jog0 has quit IRC02:46
*** jog0__ is now known as jog002:46
*** jog0_ has quit IRC02:48
*** zhuadl has quit IRC02:48
*** ryanpetrello has quit IRC02:57
*** zoumpis has joined #openstack-meeting03:08
*** markmcclain has joined #openstack-meeting03:09
*** llu has joined #openstack-meeting03:14
*** annegentle_ has joined #openstack-meeting03:18
*** jcooley_ has joined #openstack-meeting03:27
*** shang has quit IRC03:29
*** martine has joined #openstack-meeting03:32
*** shang has joined #openstack-meeting03:33
*** zoumpis has quit IRC03:35
*** martine_ has quit IRC03:35
*** juice has joined #openstack-meeting03:37
*** littleidea has quit IRC03:43
*** littleidea has joined #openstack-meeting03:44
*** jcooley_ has quit IRC03:51
*** Mandell has joined #openstack-meeting03:56
*** jcooley_ has joined #openstack-meeting03:59
*** ywu_ has quit IRC04:09
*** jcooley_ has quit IRC04:10
*** koolhead17 has joined #openstack-meeting04:21
*** annegentle_ has quit IRC04:21
*** littleidea has quit IRC04:26
*** juice has quit IRC04:27
*** littleidea has joined #openstack-meeting04:28
*** koolhead17 has quit IRC04:32
*** annegentle_ has joined #openstack-meeting04:34
*** esp has joined #openstack-meeting04:40
*** esp has left #openstack-meeting04:40
*** jdurgin1 has joined #openstack-meeting04:41
*** martine has quit IRC04:41
*** samkottler|afk is now known as samkottler04:47
*** samkottler is now known as samkottler|afk04:52
*** adjohn has quit IRC04:56
*** jog0 has quit IRC04:58
*** martine has joined #openstack-meeting05:01
*** jhenner has joined #openstack-meeting05:03
*** anniec has joined #openstack-meeting05:05
*** anniec has joined #openstack-meeting05:05
*** nati_ueno has joined #openstack-meeting05:10
*** nati_ueno_2 has joined #openstack-meeting05:19
*** nati_ueno has quit IRC05:22
*** markwash has joined #openstack-meeting05:29
*** annegentle_ has quit IRC05:34
*** Mandell has quit IRC05:36
*** Mandell has joined #openstack-meeting05:37
*** Mandell has quit IRC05:39
*** Mandell has joined #openstack-meeting05:43
*** garyk has quit IRC05:44
*** Mandell has quit IRC05:45
*** termie has quit IRC05:53
*** jhenner has quit IRC05:54
*** termie has joined #openstack-meeting05:55
*** termie has quit IRC05:55
*** termie has joined #openstack-meeting05:55
*** reed has quit IRC05:55
*** dendrobates has quit IRC06:02
*** dendrobates has joined #openstack-meeting06:02
*** jcooley_ has joined #openstack-meeting06:03
*** martine has quit IRC06:08
*** nati_ueno has joined #openstack-meeting06:09
*** nati_ueno_2 has quit IRC06:11
*** nati_ueno_2 has joined #openstack-meeting06:16
*** nati_ueno has quit IRC06:19
*** jcooley_ has quit IRC06:21
*** ben__duyujie has joined #openstack-meeting06:21
*** Mandell has joined #openstack-meeting06:34
*** nati_ueno_2 has quit IRC06:35
*** jcooley_ has joined #openstack-meeting06:36
*** garyk has joined #openstack-meeting06:38
*** jcooley_ has quit IRC06:38
*** nati_ueno has joined #openstack-meeting06:53
*** eglynn__ has joined #openstack-meeting07:07
*** henrynash has joined #openstack-meeting07:10
*** eglynn_ has quit IRC07:10
*** adjohn has joined #openstack-meeting07:11
*** markmcclain has quit IRC07:20
*** turul64 has joined #openstack-meeting07:32
*** henrynash has quit IRC07:45
*** nati_ueno has quit IRC07:49
*** turul64 is now known as afazekas07:50
*** rafaduran has joined #openstack-meeting07:56
*** eglynn__ has quit IRC07:58
*** adjohn has quit IRC08:13
*** Daviey has quit IRC08:15
*** EntropyWorks has quit IRC08:18
*** EntropyWorks has joined #openstack-meeting08:18
*** Daviey has joined #openstack-meeting08:18
*** eglynn__ has joined #openstack-meeting08:25
*** eglynn__ has quit IRC08:31
*** henrynash has joined #openstack-meeting08:33
*** ben__duyujie has quit IRC08:36
*** eglynn__ has joined #openstack-meeting08:45
*** littleidea has quit IRC09:00
*** derekh has joined #openstack-meeting09:05
*** darraghb has joined #openstack-meeting09:07
*** ijw1 has joined #openstack-meeting09:15
*** ijw1 has joined #openstack-meeting09:16
*** jhenner has joined #openstack-meeting09:25
*** salv-orlando has joined #openstack-meeting09:29
*** alexpilotti has joined #openstack-meeting09:36
*** mikal has quit IRC10:18
*** henrynash has quit IRC10:18
*** mikal has joined #openstack-meeting10:20
*** fnaval has quit IRC10:33
*** EmilienM_ has joined #openstack-meeting10:35
*** maurosr has joined #openstack-meeting10:51
*** mikal has quit IRC10:54
*** shang has quit IRC10:56
*** frankm has joined #openstack-meeting11:08
*** almaisan-away is now known as al-maisan11:10
*** jcooley_ has joined #openstack-meeting11:15
*** jcooley_ has quit IRC11:27
*** sandywalsh has joined #openstack-meeting11:28
*** nati_ueno has joined #openstack-meeting11:33
*** henrynash has joined #openstack-meeting11:33
*** nati_ueno has quit IRC11:34
*** dwcramer has quit IRC11:34
*** rkukura has left #openstack-meeting11:57
*** dwcramer has joined #openstack-meeting12:01
*** salv-orlando has quit IRC12:12
*** EmilienM_ has quit IRC12:13
*** ijw11 has joined #openstack-meeting12:14
*** ijw1 has quit IRC12:16
*** salv-orlando has joined #openstack-meeting12:19
*** eglynn__ is now known as eglynn12:25
*** eglynn_ has joined #openstack-meeting12:33
*** eglynn has quit IRC12:33
*** jaypipes has joined #openstack-meeting12:37
*** dhellmann-afk is now known as dhellmann12:41
*** salv-orlando_ has joined #openstack-meeting12:45
*** salv-orlando has quit IRC12:45
*** salv-orlando_ is now known as salv-orlando12:45
*** salv-orlando_ has joined #openstack-meeting12:46
*** salv-orlando has quit IRC12:46
*** salv-orlando_ is now known as salv-orlando12:46
*** dwcramer has quit IRC13:00
*** EmilienM_ has joined #openstack-meeting13:00
*** markvoelker has joined #openstack-meeting13:00
*** CaptTofu has quit IRC13:06
*** dhellmann is now known as dhellmann-afk13:06
*** radez_g0n3 is now known as radez13:12
*** littleidea has joined #openstack-meeting13:15
*** alexpilotti has quit IRC13:16
*** littleidea has quit IRC13:16
*** salv-orlando_ has joined #openstack-meeting13:21
*** salv-orlando has quit IRC13:22
*** salv-orlando_ is now known as salv-orlando13:22
*** littleidea has joined #openstack-meeting13:22
*** littleidea has quit IRC13:30
*** martine has joined #openstack-meeting13:30
*** alexpilotti has joined #openstack-meeting13:36
*** ryanpetrello has joined #openstack-meeting13:40
*** anniec_ has joined #openstack-meeting13:40
*** ryanpetrello has quit IRC13:40
*** radez is now known as radez_g0n313:42
*** anniec_ has quit IRC13:46
*** jjm3lp has quit IRC13:50
*** dprince has joined #openstack-meeting13:59
*** primeministerp has joined #openstack-meeting14:12
*** radez_g0n3 is now known as radez14:18
*** radez is now known as radez_g0n314:19
*** shengjie has joined #openstack-meeting14:36
*** dolphm has joined #openstack-meeting14:41
*** dwcramer has joined #openstack-meeting14:43
*** mtreinish has joined #openstack-meeting14:43
*** zoumpis has joined #openstack-meeting14:46
*** ryanpetrello has joined #openstack-meeting14:49
*** AlanClark has joined #openstack-meeting14:52
*** samkottler|afk is now known as samkottler14:57
*** samkottler is now known as samkottler|afk14:58
*** eglynn__ has joined #openstack-meeting15:01
*** eglynn_ has quit IRC15:01
*** dkehn has joined #openstack-meeting15:06
*** dhellmann has joined #openstack-meeting15:09
*** salv-orlando has quit IRC15:10
*** salv-orlando has joined #openstack-meeting15:10
*** asalkeld has quit IRC15:13
*** mattray has joined #openstack-meeting15:14
*** jcooley_ has joined #openstack-meeting15:15
*** asalkeld has joined #openstack-meeting15:19
*** Mandell has quit IRC15:20
*** colinmcnamara has joined #openstack-meeting15:31
*** andrewbogott_afk is now known as andrewbogott15:31
*** dendrobates has quit IRC15:33
*** annegentle_ has joined #openstack-meeting15:40
*** koolhead17 has joined #openstack-meeting15:41
*** oNeToWn has joined #openstack-meeting15:41
*** salv-orlando_ has joined #openstack-meeting15:45
*** salv-orlando has quit IRC15:45
*** salv-orlando_ is now known as salv-orlando15:45
*** dendrobates has joined #openstack-meeting15:46
*** dendrobates has joined #openstack-meeting15:46
*** NobodyCam_afk is now known as NobodyCam15:48
*** danwent has joined #openstack-meeting15:54
*** jcooley_ has quit IRC15:57
*** jcooley is now known as jcooley_afk15:57
*** luis_fdez has joined #openstack-meeting15:58
primeministerp#startmeeting hyper-v15:59
openstackMeeting started Tue Nov 20 15:59:10 2012 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
openstackThe meeting name has been set to 'hyper_v'15:59
primeministerpHI all15:59
primeministerpwe'll give a couple more minutes before we get started15:59
*** rushiagr has joined #openstack-meeting15:59
*** Hitesh has joined #openstack-meeting16:00
*** dwcramer has quit IRC16:01
Hiteshprimeministerp: Hi,16:01
Hiteshalexpilotti: Hello16:02
primeministerpHitesh: hello16:02
primeministerpHitesh: starting in a couple minutes16:02
Hiteshprimeministerp: Ok.16:03
*** pnavarro has joined #openstack-meeting16:04
pnavarrohi all16:04
primeministerppnavarro: perfect16:04
primeministerppnavarro: i was mainly waiting for you16:05
primeministerplet's begin everyone16:05
pnavarrosorry and thanks primeministerp16:05
primeministerppnavarro: no worries16:05
alexpilottihi guys!16:05
primeministerpzykes-: hey now16:05
HiteshHello guys16:06
primeministerpEmilienM_: how's it going16:06
primeministerpalexpilotti: you around?16:06
primeministerpociuhandu: ?16:06
alexpilottiprimeministerp: yep16:06
*** rushiagr has quit IRC16:06
primeministerp#topic blueprints16:06
*** openstack changes topic to "blueprints"16:06
alexpilottipnavarro: this is the repo with the cinder bits?16:06
EmilienM_primeministerp: fine thx16:06
primeministerpso first item to discuss is blueprints16:06
*** annegentle__ has joined #openstack-meeting16:07
primeministerpalessandro has been adding/adjust blueprints for work that is being done16:07
primeministerpvish had requested that we break the blueprints up by implemented veature16:07
primeministerper feature16:07
pnavarroalexpilotti: what do you mean by this?16:07
pnavarroalexpilotti: did you point to a link? I missed it16:07
alexpilottipnavarro: I forgot the link sorry :-D16:07
alexpilottipnavarro: https://github.com/pnavarro/nova/blob/master/nova/virt/hyperv/volumeops.py16:08
pnavarroyeah, alexpilotti16:08
primeministerp#link https://github.com/pnavarro/nova/blob/master/nova/virt/hyperv/volumeops.py16:08
primeministerppnavarro: alexpilotti added a bluepint for the wmi v2 cinder work as well16:08
primeministerppnavarro: i believe16:08
primeministerpalexpilotti: am i correct?16:08
alexpilottipnavarro: I see that you are using a CONF.hyperv_os_version to get the OS version16:08
alexpilottipnavarro: why don't you query the OS directly?16:09
pnavarrowell, in fact, volumeops have no changed that much, the true changes are in : https://github.com/pnavarro/nova/blob/master/nova/virt/hyperv/volumeutilsV2.py16:09
primeministerp#link https://github.com/pnavarro/nova/blob/master/nova/virt/hyperv/volumeutilsV2.py16:09
pnavarroalexpilotti: err... good point, I didn't know I could get this granurality through os16:10
primeministerppnavarro: how long before the cinder pieces are complete?16:10
alexpilottipnavarro:  def _get_hypervisor_version(self):16:10
alexpilotti        """Get hypervisor version.16:10
alexpilotti        :returns: hypervisor version (ex. 12003)16:10
alexpilotti        """16:10
alexpilotti        version = self._conn_cimv2.Win32_OperatingSystem()[0]\16:10
alexpilotti            .Version.replace('.', '')16:10
alexpilotti        LOG.info(_('Windows version: %s ') % version)16:10
alexpilotti        return version16:10
pnavarrook !16:10
*** annegentle_ has quit IRC16:11
pnavarroprimeministerp: well, it's 99% complete, just was missing some pieces like alexpilotti was pointing16:11
primeministerppnavarro: will it be in for g1?16:11
primeministerppnavarro: that's by week end I believe..16:11
primeministerpor is it next16:11
primeministerppnavarro: it's close16:12
alexpilottipnavarro: the storage WMI namespace is supported on Windows 8?16:12
pnavarroalexpilotti: yes, the doc says so16:12
alexpilottipnavarro: in that case we can just check for the OS version >= 6.2 :-)16:12
alexpilottipnavarro: what about adding a FLAG (aka CONF) for forcing the usage of the old one in case of issues?16:13
pnavarroprimeministerp: I'd need some help from alexpilotti to launch live migration tests16:13
*** dwcramer has joined #openstack-meeting16:13
alexpilottipnavarro: like: CONF.force_vmutils_v116:14
primeministerppnavarro: I'm still a week off from that16:14
primeministerppnavarro: any way we can get help from the ibm folks on that?16:14
primeministerpEmilienM_: can you help test the livemigration side of things?16:14
EmilienM_primeministerp: yep16:15
primeministerppnavarro: EmilienM_ can assist too16:15
*** hemna has joined #openstack-meeting16:15
*** al-maisan is now known as almaisan-away16:15
*** rushiagr has joined #openstack-meeting16:15
primeministerp#action EmilienM_ help w/ volume/live-migration testing16:15
pnavarroalexpilotti: in that case, I can transform the conf _hyperv_os_version for that16:15
alexpilottiprimeministerp: pnavarro needs only to generate the test stubs for passing Jenkins tests16:16
primeministerpalexpilotti: great16:16
alexpilottipnavarro: sure! :-)16:16
primeministerpand that can be done by just generating the moc?16:16
primeministerpor additional coding prior to the moc?16:16
alexpilottiprimeministerp: yep, by simply running the tests16:16
primeministerpwhich is why he needs the live migration bits16:17
primeministerpgot it16:17
alexpilottiprimeministerp: correct!16:17
primeministerppnavarro: are you capible of working w/ EmilienM_ to do that?16:17
EmilienM_pnavarro: I think that's ok :)16:17
pnavarroI don't know how EmilienM_ can help...16:17
primeministerppnavarro: you don't have a live migration setup16:18
primeministerppnavarro: if EmilienM_ does16:18
primeministerppnavarro: he can generate the moc bits by running the test16:18
EmilienM_pnavarro: I have I think16:18
primeministerpalexpilotti: correct in my understanding?16:18
alexpilottiprimeministerp: yep16:18
primeministerppnavarro: you understand?16:19
pnavarroprimeministerp: I started yesterday a VM Domain controller... but if EmilienM_ has this setup, yes definetely can be helpful16:19
primeministerpEmilienM_: you have a 2 hyper-v setup correct?16:19
EmilienM_primeministerp: right16:19
EmilienM_primeministerp: but never test live migration16:19
primeministerpEmilienM_: if you're in a domain, and have used the cloudbase installer16:19
primeministerpEmilienM_: it should work16:20
EmilienM_primeministerp: that's fine16:20
primeministerpEmilienM_: i can help debug today in a hour or so16:20
primeministerpif you need help16:20
EmilienM_primeministerp: which kind of test16:20
EmilienM_live migration or python tests ?16:20
primeministerpEmilienM_: live migration16:20
EmilienM_primeministerp: fine16:20
EmilienM_primeministerp: can't do it before 8pm CEST16:21
primeministerppnavarro: so you can help him get those running w/ your code?16:21
* EmilienM_ in classroom ATM :-)16:21
primeministerpEmilienM_: coordinate w/ pnavarro16:21
primeministerpEmilienM_: but that's ok16:21
pnavarroI'll call EmilienM_ later16:21
primeministerppnavarro: great, thanks for working together16:21
EmilienM_primeministerp: yep, we have scheduled a conf call tonight16:21
primeministerpEmilienM_: thanks for helping out16:21
EmilienM_primeministerp: I'll do my best16:22
primeministerpmoving on then16:22
primeministerp#status updates16:22
*** Gordonz has joined #openstack-meeting16:22
primeministerpalexpilotti: you want to give a quick rundown?16:22
* alexpilotti is cloning pnavarro's repo16:22
alexpilottiprimeministerp: sure16:22
primeministerpcloudinit work was completed and made it through jenkins last friday16:22
alexpilottiCloudInit / ConfigDriveV2 is in16:23
alexpilottiand the Grizzly installer has been updated16:23
EmilienM_I need to leave IRC guys16:23
primeministerpGood feature to have for G116:23
EmilienM_bye all16:23
primeministerpEmilienM_: thx again, include me on threads16:23
alexpilottiwe are using a couple extra tools: mkisofs and qemu-img16:23
EmilienM_pnavarro: see you later ;)16:23
pnavarrobye EmilienM_16:24
alexpilottito generate the ISO and VHD to attach16:24
*** EmilienM_ has left #openstack-meeting16:24
alexpilotticloud-init had a few bugs, we helped the mainteiners to fix them16:24
primeministerpalexpilotti: great work16:24
primeministerpany updates on RDP?16:25
alexpilottiwe have precompiled deb and rpm packaes with cloudinit if you need them16:25
primeministerpalexpilotti: o nice, do you have urls?16:25
primeministerpwe'll post them for the minutes16:25
alexpilottiand on our blog there's a full VHD w Ubuntu 12.04 ready for Glance16:26
*** redthrux has joined #openstack-meeting16:26
primeministerpalexpilotti: great let's post those url's too if you got them16:26
alexpilottia full blog post will follow up on cloud init / config drive16:26
*** redthrux has joined #openstack-meeting16:26
primeministerp#link http://www.cloudbase.it/downloads/UbuntuServer1204_cloudinit.zip16:27
alexpilottiI'm going to fetch the .deb and .rpm asap16:27
alexpilottiok, back to the updates16:27
primeministerpuse "#link" when posting16:27
alexpilotticloud-init for Windows. We have a bomb:16:27
primeministerpanything i can help w/?16:28
alexpilottipublik key authentication on RDP16:28
primeministerpwe discussed briefly16:28
*** dhellmann has quit IRC16:28
primeministerpdid you finish the work for ssh key auth?16:28
alexpilottibriefly, auth on Windows will use the same SSH keys16:28
alexpilottiprimeministerp: working on it16:28
luis_fdezalexpilotti: that sounds interesting...16:28
primeministerpalexpilotti: well from a end user perspective it's great news16:29
primeministerpgreat feature alexpilotti16:29
primeministerpalexpilotti: even if it's from a bomb16:29
alexpilottionce that is done we'll port cloud-init to Windows, using the same authorized_keys deployed for SSH16:29
alexpilottiand the sae keypairs udes by openstack16:29
alexpilottiin short this means that there will be no more issue for password distribution16:29
*** Gordonz has quit IRC16:30
alexpilottiI'd expect also Amazon & company to pick up such a feature16:30
primeministerpthat should make it interesting16:30
*** markwash has quit IRC16:30
*** Gordonz has joined #openstack-meeting16:30
alexpilottiok, that's it for cloud-init so far16:30
primeministerpalexpilotti: and i'm assuming quantum status is the same due to work on cloudinit?16:30
alexpilottinova: fixed a few bugs16:30
pnavarroQuantum: from my side wvs_quantum_plugin (Windows Virtual Switch) advances slowly, but it advances16:31
alexpilottiincluding today a very annoying one on VM status16:31
primeministerpalexpilotti: yes i saw that16:31
alexpilottiQuantum: we are also advancing slowly, due to teh time we had to spend w the reviews16:31
primeministerpyes I know16:32
alexpilottiQuantum target is definitely G216:32
primeministerphopefully we can find a way to speed up that process16:32
alexpilottiother stuff: RDP console, ociuhandu is working on it16:32
alexpilottiwe got aslo a great help from sagar, which is doing some great testing work16:33
primeministerpI don't think sagar's on today16:33
alexpilottiok, those were the updates for this week :-)16:33
primeministerpalexpilotti: thanks for info16:33
primeministerpluis_fdez: any thing to add from the CERN front?16:33
HiteshThanks for great info :)16:34
primeministerpluis_fdez: sorry i couldn't get more movement on the SCOM discussion16:34
Hiteshspecially alexpilotti :)16:34
alexpilottiHitesh: tx16:34
luis_fdeznothing new... I was out of the office since thursday...16:34
alexpilottiluis_fdez: tx for your get_stats patch!16:34
primeministerpluis_fdez: yes thank you16:34
primeministerpalexpilotti: thanks for reminding me16:35
luis_fdezno problem primeministerp, let's see if we can make some development on that...16:35
Hiteshalexpilotti: sorry I couldn't contribute more, however, I am doing setup..16:35
alexpilottiluis_fdez: I'd like to get your CPU patch in this week. Do you have some time to get it done?16:35
Hiteshalexpilotti: stucked with office work..16:35
primeministerpluis_fdez: well if you start let me know, and I'll try to get you at least the information sources when needed16:35
Hiteshalexpilotti: building quantum source from scratch on RedHat16:35
luis_fdezalexpilotti: ok, I think I'll be able16:35
*** cp16net is now known as cp16net|away16:35
luis_fdezbut... alexpilotti , I can't wait cloud-init for win and ssh key auth!!!!16:36
primeministerpluis_fdez: talk it up...16:36
primeministerpluis_fdez: make sure jan knows16:36
primeministerpluis_fdez: ;)16:36
alexpilottiluis_fdez: should be a quick thing. I'd like to validate the json stuff w the nova guys as there's no documentation on it and you did a great job in reverse engineer it from KVM etc16:36
pnavarroHitesh: why don't you use devstack?16:37
alexpilottiluis_fdez: ssh jey auth is very close. As a side effect, I have a tool that dumps clear text passwords on login :-D16:37
primeministerpalexpilotti: we all need one of those tools16:38
Hiteshpnavarro: you are right, but we are developing custom plugin16:38
Hiteshpnavarro: and supporting different DB16:38
pnavarroprimeministerp: so G1 it's for 22-11-2012.16:38
alexpilottiI have a question on the Nova side16:38
Hiteshpnavarro: so we will have to run only quantum :)16:38
primeministerppnavarro: so thinking G2?16:38
Hiteshpnavarro: so let's think to target our quantum stuff for G2 :)16:39
alexpilottido you guys have any feature you'd like in Nova-Grizzly, beside what we already have and Resize?16:39
primeministerppnavarro: or will you be able to get done what you need w/ EmileM before?16:39
Hiteshpnavarro: hope I will finish office stuff this weekend16:39
Hiteshpnavarro: I will get back to you on wvs_quantum_plugin16:39
primeministerpalexpilotti: you mean for G1?16:40
primeministerpalexpilotti: or in general?16:40
pnavarroprimeministerp: well we'll try16:40
alexpilottiprimeministerp: Grizzly in ge16:40
alexpilottiprimeministerp: just to check if there are more plugins to write16:40
alexpilottisorry, meant blueprints, lapsus :-)16:41
primeministerppnavarro: o yes16:41
primeministerppnavarro: make sure you have appropriate blueprints prior to submitting16:41
primeministerpHitesh: anything to add?16:41
pnavarrook primeministerp16:41
Hiteshprimeministerp: Nops from my side16:41
alexpilottipnavarro: we need to add a blueprint for your new Cinder bits16:42
Hiteshprimeministerp: I didn;t get a chance to work more on our stuff...so nothing to add this time...:(16:42
pnavarroI'll sync with you this night alexpilotti16:42
alexpilottipnavarro: ok!16:43
primeministerpguess general ci update from my end16:44
alexpilottiprimeministerp: cool!16:44
primeministerpworking like a mad man preping for the visit from alexpilotti and ociuhandu16:44
primeministerpimplemeneted the production puppet infra on friday and base pxe node16:44
primeministerpall puppetized16:44
alexpilottiprimeministerp: cool! Should we also set up a meeting with the OpenStack CI guys for inputs?16:44
primeministerpcore switch is puppetized16:45
primeministerpalexpilotti: i'll work on that for next week16:45
alexpilottiprimeministerp: great tx!16:45
primeministerp#action pp setup meeting w/ mtaylor and other for ci discussion16:45
pnavarroI have to go, missing my bus... see you later16:45
primeministerppnavarro: thanks again16:45
alexpilottipnavarro: bye!16:46
Hiteshsame here..I will to catch my bus16:46
*** dendrobates has quit IRC16:46
primeministerpI should be done w/ the switch automation and trunking of all available ports between switches16:46
Hiteshbye guys16:46
primeministerpbye Hitesh16:46
HiteshI will synch with alexpilotti and pnavarro16:46
*** Mandell has joined #openstack-meeting16:46
*** dendrobates has joined #openstack-meeting16:46
primeministerpalexpilotti: we'll deal w/ things like logging etc later, i'm trying to get the basics in place for when you come to to be able to roll the setups as quickly as possible16:47
primeministerpand have contol w/ jenkins16:47
alexpilottiprimeministerp: ok!16:47
primeministerpalexpilotti: the rest i fugure we integrate what is already there16:47
primeministerpalexpilotti: in terms of the jenkins jobs etc16:47
primeministerpalexpilotti: we'll discuss that w/ monty16:48
primeministerpok I'll talk w/ him and schedule something for next week16:48
primeministerpwe have a holiday on thurs16:49
primeministerpi'll be working on friday as well16:49
primeministerpjust out thur16:49
primeministerpon that note16:49
primeministerpI'll end it and send out the notes16:49
primeministerpwe can touch base later16:49
primeministerpif needed16:49
primeministerpalexpilotti: ^16:49
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:49
openstackMeeting ended Tue Nov 20 16:49:56 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:49
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2012/hyper_v.2012-11-20-15.59.html16:49
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2012/hyper_v.2012-11-20-15.59.txt16:49
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2012/hyper_v.2012-11-20-15.59.log.html16:50
alexpilottiprimeministerp: ok!16:50
*** pnavarro has quit IRC16:50
alexpilottiprimeministerp: I have a quick meeting here at the office as well, brb16:50
luis_fdezsee you16:50
*** luis_fdez has quit IRC16:50
*** adjohn has joined #openstack-meeting16:52
*** rushiagr has quit IRC16:57
*** dendrobates has quit IRC17:00
*** colinmcnamara has quit IRC17:00
*** colinmcnamara1 has joined #openstack-meeting17:00
*** garyk has quit IRC17:02
*** cp16net|away is now known as cp16net17:02
*** markwash has joined #openstack-meeting17:03
*** Mandell has quit IRC17:06
*** reed has joined #openstack-meeting17:07
*** oNeToWn has quit IRC17:08
*** oNeToWn has joined #openstack-meeting17:11
*** Mandell has joined #openstack-meeting17:11
*** jhenner has quit IRC17:16
*** garyk has joined #openstack-meeting17:16
*** cp16net is now known as cp16net|away17:17
*** rafaduran has quit IRC17:23
*** dendrobates has joined #openstack-meeting17:28
*** anniec has quit IRC17:28
*** eglynn__ has quit IRC17:29
*** eglynn has joined #openstack-meeting17:29
*** jcooley_afk is now known as jcooley17:32
*** jcooley_ has joined #openstack-meeting17:32
*** cp16net|away is now known as cp16net17:33
*** eglynn_ has joined #openstack-meeting17:33
*** eglynn has quit IRC17:33
*** jdurgin1 has quit IRC17:34
*** rnirmal has joined #openstack-meeting17:36
*** fnaval has joined #openstack-meeting17:36
*** EmilienM_ has joined #openstack-meeting17:42
*** heckj has joined #openstack-meeting17:45
*** EmilienM_ has quit IRC17:46
*** derekh has quit IRC17:46
*** lloydde has joined #openstack-meeting17:48
*** jcooley_ has quit IRC17:48
*** rushiagr has joined #openstack-meeting17:50
*** nati_ueno has joined #openstack-meeting17:53
*** ksiu has joined #openstack-meeting17:57
*** dwchadwick has joined #openstack-meeting17:57
*** marek_ has joined #openstack-meeting17:58
*** garyk has quit IRC17:59
*** etoews has joined #openstack-meeting17:59
*** eglynn_ has quit IRC18:00
dwchadwickKeystone OK18:01
heckj#startmeeting keystone18:01
openstackMeeting started Tue Nov 20 18:01:18 2012 UTC.  The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
openstackThe meeting name has been set to 'keystone'18:01
dwchadwickI have sent an email to the list suggestions some topics for discussion18:01
heckjdwchadwick: sounds reasonable - I'm behind on email by several hundred at the moment, so I haven't seen it though...18:01
heckjagenda: http://wiki.openstack.org/Meetings/KeystoneMeeting18:02
*** brich1 has joined #openstack-meeting18:02
heckj#topic burning issues18:02
*** openstack changes topic to "burning issues"18:02
dwchadwickI can repeat the list here if you like18:02
heckjWe have a security bug that we're working (not public)  - Dolph has posted patches, core needs to vet.18:03
ayoungheckj, I don;t think any outstanding bugs are burning issues right now.18:03
heckjayoung: I subscribed you: https://bugs.launchpad.net/keystone/+bug/107921618:03
*** brich1 has quit IRC18:03
heckj(note: everyone else will likely get a 404 on that link, since it's marked security)18:03
*** brich1 has joined #openstack-meeting18:04
heckjdwchadwick: your list would be welcome, thank you18:04
*** cp16net is now known as cp16net|away18:04
dwchadwickIn no particular order18:05
dwchadwick1. Groups vs. attribute mappings18:05
dwchadwick2. Adding IDPs to service catalog18:05
dwchadwick3. RBAC API, and why have tenants/projects? or groups for that matter?18:05
dwchadwick4. Delegation18:05
dwchadwick5. Status/Timeframe of Federation integration18:05
*** nati_ueno has quit IRC18:05
heckjdwchadwick: will add to agenda, as I suspect we won't get through that all18:05
heckj#topic V3 API18:06
*** openstack changes topic to "V3 API"18:06
dwchadwickso we should prioritse first18:06
dwchadwickI guess groups vs attribute mappings comes under this agenda item18:06
ayounggetting V3 in is, I think priority, as is the other changes that are causing us to "lock down" sections of the code for changes18:07
heckjReview's are up - catalog pending attention, ayoung and dolph working on Identity along with database refactoring and normalization18:07
heckjayoung: yep, agreed18:07
heckjWe won't have all the V3 in for this first milestone, so I'll retarget that to G2 prior to the release meeting today18:07
ayoungthat means auth_token changes from here on out only go into keystoneclient18:07
dwchadwickwe have posted a blueprint that shows how IDPs can be added to the catalog with no changes to the API18:08
*** frankm has quit IRC18:08
ayoungdwchadwick, link?18:08
dwchadwickKristy should have posted it to the list. Its in google docs18:09
ayoung#link http://wiki.openstack.org/Keystone/Federation/Blueprint18:09
dolphm#link https://blueprints.launchpad.net/keystone/+spec/adding-idps-to-service-catalog18:09
dwchadwickyep its here18:09
* heckj wave18:10
dwchadwickWe are proposing two changes to the client but none to keystone18:10
dwchadwick1. made the type a type.subtype18:11
dwchadwickthis should help with scalability as more services are added in the future, and different types of IDPs18:11
*** salv-orlando has quit IRC18:11
*** eglynn_ has joined #openstack-meeting18:11
dwchadwickbut to keystone is it still just a string, so no changes18:11
*** salv-orlando has joined #openstack-meeting18:11
ayoungdwchadwick, is it possible that the change will trip up on some previous data?18:12
ayoungsay someone has already named their types that way?18:12
dwchadwick2. I dont think so, since all types today are simply types and dont use subtypes18:12
dolphmdwchadwick: i'm confused on how you say you don't need to modify the API, but then turn around and specify that the client needs to be passing at least two new pieces of data to the keystone server, via the API?18:12
dwchadwickSo only future types of services (like IDPs) can make use of subtype18:13
ayoungdolphm, I think he means it is a format of the string18:13
dwchadwickIts a new optional parameter that clients add at their end18:13
*** jcooley is now known as jcooley_afk18:13
dolphmayoung: dwchadwick: i'm referring to certdata and protocol, not 'type', which is just an opaque string to keystone18:13
dwchadwickbut the keystone database does not change cos it is all bundled in the extras field18:13
ayoung--certdata – the identity provider certificate data for signing and verification.  +1 there18:14
ayoungprobably should be a file name.18:14
dwchadwickyes this is a new parameter that the client can optionally add18:14
ksiuHi, correct me if I'm wrong but the service data is stored as a jsonblob in the extra field of the database?18:14
ayoungdwchadwick, should tag that as optional, too.18:14
dwchadwickso it is backwards compatible with current implementations18:15
*** EmilienM has left #openstack-meeting18:15
ksiuSo certdata and protocol could be adding to that without changing anything?18:15
*** nachi has joined #openstack-meeting18:15
ayoungWe also will need a way to set and update it after the endpoint has been created for existing endpoints and cert expiration18:15
dwchadwickyes its optional18:15
heckjayoung, dwchadwick: what explicitly is the cert data? Is this an endpoint with where to get the identity information, or a certificate that can be used to verify requests to access the service?18:15
ayoungksiu, not a fan of 'extra'  I would love to focus on keeping stuff normalized.  serialization of JSON is an antipattern in my book18:16
ksiuheckj: it's the certificate use to validate the signed response from the Identity provider18:16
dolphmdwchadwick: what do you expect the client to do with --certdata, for example?18:16
ayoungheckj, say an endpoint is allowed to sign certs, it is the cert it would present for other services to verify them18:16
heckjayoung: +1 - was intended as a placeholder until it was clear what we wanted/needed to model and capture18:16
dwchadwickthe client will pass cert data back to the credential issuing component of federated keystone, so it does not need to touch it18:17
*** markmcclain has joined #openstack-meeting18:17
ksiuis the way of storing the service data changing in V3?18:18
ayoungdwchadwick, I kind of see this still as just the stub of the effort for cert management for endpoints.  The workflow will likely be slightly more complicated. But I would classify this as "necsssary first steps"18:18
*** darraghb has quit IRC18:18
dwchadwickfederated keystone is responsible for doing all the work. The client simply gets parameters from one part of keystone and passes them back to another part18:18
dolphmksiu: not really https://review.openstack.org/#/c/15610/7/keystone/catalog/backends/sql.py18:18
dolphmksiu: driver is a little more robust, and API-level service/endpoint crud is pretty much 1:1 with the driver18:19
*** eglynn_ has quit IRC18:19
*** eglynn_ has joined #openstack-meeting18:20
dwchadwickHave we stalled?18:20
dolphmdwchadwick: i absolutely don't see statement as being realistic- "As mentioned previously no changes to the Keystone service would be required to store and retrieve the extra data."18:20
*** rushiagr has quit IRC18:21
dwchadwickIt depends upon where the json blob is created. If the client creates it, then keystone does not see the change.18:21
ksiudolphm: perhaps I have misunderstood the way the endpoint and service data is stored but it looked to me as if it was stored in a jsonblob in the extra field18:21
*** jcooley_afk is now known as jcooley18:22
dwchadwickSo we have defined a parameter that the user passes to the client (the certdata) and the client software packages this into the json blob18:22
ayoungdwchadwick, "extra" is not part of the API, just a storage detail;18:22
ayoungmore correct to say you have added an additional field to the API. I think that is ok, but only if it is optional.  Which, I think, it is.18:23
dwchadwickBTW there is a mistake in the diagram as we dont need protocol. This was in an earlier design but has been removed from the text but the diagram was not updated to conform to the new text18:23
*** esp1 has joined #openstack-meeting18:23
dolphmdwchadwick: 'localurl' should also read 'internalurl'18:24
dwchadwickOk. Kristy will update the doc tomorrow18:24
*** eglynn_ has quit IRC18:25
heckjsounds like we all need to do a little more reading to have an intelligent response18:25
ayoungdwchadwick, ksiu might I suggest then that you post images as svg files, and other people can then modify them?18:25
dwchadwickSo can I understand the message that is passed from the client to keystone. Does it contain a json blob or not? And if it does, does it contains an extra field18:25
ksiuayoung: noted18:26
*** jcooley is now known as jcooley_afk18:26
dolphmdwchadwick: 'extra' is not exposed to the API per se18:26
dolphmdwchadwick: the driver stores non-indexed attributes of services & endpoints as a JSON blob in a column called 'extra'18:27
*** markmcclain has quit IRC18:27
dwchadwickwe assumed the client could pass extra to keystone for it to store. This would make a sensible extension point18:27
heckjdwchadwick: how it presents them is something we can extend into the API, which is what we want/need to define to enable this18:28
dwchadwickOf course it could not be indexed because keystone has no idea what is contained there, except some random string of random lenght18:28
dolphmdwchadwick: the service implementation is flexible in that it handles attributes it doesn't otherwise understand18:28
dwchadwickSo an alternative would be to define an attribute called certificate?18:29
dolphmdwchadwick: the client must still adhere to a tested contract, in this case, i imagine you're envision a v2.0 API extension, and perhaps an extension to the OS-KSADM extension18:29
dolphmdwchadwick: (unless you're only talking about v3 support)18:29
dwchadwickI think we can wait to v3 for this, since it is not needed until you have federated keystone, which I assume will be v3 (but that is another agenda item)18:30
dwchadwickthe thing that is most pressing for v2 seems to be groups vs attribute mapping18:30
dolphmdwchadwick: great that simplifies things quite a bit then!18:30
*** markmcclain has joined #openstack-meeting18:30
*** garyk has joined #openstack-meeting18:31
dolphmdwchadwick: user groups?18:31
dwchadwickshall we move to groups vs mappings18:31
henrynashdo we think groups vs attribute mapping is a v2 thing?  I could be, but I had imagined part of v318:31
*** mnewby has quit IRC18:31
dwchadwickdolphm: yes18:31
heckjdwchadwick: please get me agenda suggestions earlier next time18:31
*** radez_g0n3 is now known as radez18:32
dwchadwicksorry, but I was in meetings most of the day18:32
heckjdwchadwick: me too - is okay - just trying to keep things organized, and we've jumped all over18:32
dolphmi haven't been following user group discussions, but there's already a defined API for them that was implemented in diablo: https://github.com/openstack/identity-api/tree/master/openstack-identity-api/src/docbkx/extensions/RAX-KSGRP18:32
heckjhenrynash: I managed to get you some feedback this weekend, but haven't followed up since I sent off the initial sets18:33
dwchadwickI am pretty much against groups, since they are no different to roles18:33
ayoungdwchadwick, not correct18:33
heckjdwchadwick: I disagree entirely18:33
dwchadwickayoung: in what way18:33
ayoungdwchadwick, they are an essential organizational tool.18:33
ayoungroles must be assigned to something18:33
ayoungand usually, they are assigned to a user18:34
ayoungif you were to say that groups are roles18:34
dwchadwickwhat you are saying is that there are two different types of roles: organisational roles and cloud service roles18:34
dolphmi like the definition provided at the summit: "every operation you can apply to a user, you should be able to apply to a group of users"18:34
heckjgroups allow us to not have to submit 10's or 100's of links from user < -- role --> project, but manage that in explicit "groups"18:34
dolphmso, "grant this role on this project to this entire group of users"18:34
ayoungyou have no way to reuse things...it all falls on the back of the policy enforcement18:34
heckjdwchadwick: this isn't about different roles, but applying roles to sets of users18:34
dwchadwicka group is just another collection, same as a role (or better still get rid of roles and call them all attributes)18:34
*** anniec has joined #openstack-meeting18:35
dolphmdwchadwick: roles have explicit associations with domains or projects, however18:35
ayoungdwchadwick, they are all "attributes" but that doesn't mean that there are not semantic differences.18:35
heckjdwchadwick: roles == attribute is fine from an academic perspective, but will consfuse laymen trying to implement this and looking for what they're considering "roles"18:35
*** anniec_ has joined #openstack-meeting18:35
dwchadwickwhat you want is a mechanism to say people with this attribute (which you call group) also have this attribute (which you call role)18:36
*** nati_ueno has joined #openstack-meeting18:36
ayoungdwchadwick, right18:36
heckjdwchadwick: you're already talking in groups, but we don't have "woking with sets of people" built in to our API18:36
dwchadwickOf course different attributes have different semantics18:36
dolphmdwchadwick: the second half of your statement is meaningless unless you also specify the domain/project the "attribute" applies to18:37
dwchadwickBut ultimately what you are interested in is ABAC18:37
dwchadwickie. a user with this set of attributes gets access to this set of resources18:37
ayoungdwchadwick, well, I am, but most people think I am crazy18:37
heckjplease define ABAC18:37
ayoungheckj, attribute based access control18:38
henrynashI think the challenge is we have a set of definitions (e.g. what a role is) already for keystone, we need to decide if we are going to re-define all that, or work to extend these in the direction of organisational (roles) as well as mapping to external defintions18:38
*** saurabhs has joined #openstack-meeting18:38
ayoungheckj, so for instance, "you must be older than 18 to purchase cigarrettes."18:38
*** saurabhs has left #openstack-meeting18:38
dwchadwickayoung: correct18:38
ayoungthe attribute age is evaluated against a criteria to determine access18:38
ayoungit is the most generl form of auth,  with RBAC a simplified version, etc18:39
dwchadwickwhich is why I question why you need tenants either, since these are simply another type of attribute which grant you access to a set of resources18:39
heckjayoung: understood. I think henrynash's has it in a nutshell though18:39
dolphmdwchadwick: is there a precedence contextual attributes?18:39
*** anniec has quit IRC18:39
*** anniec_ is now known as anniec18:39
dolphmdwchadwick: e.g. i have a purple-shirt, but only under a blacklight18:40
ayoungdwchadwick, two sides to it, one of which is granting access, and the other is providing the pieces for people to manage that access.  We are trying to provide a reasonable subset of atttributes that map to how most tech-based organizations already perform auth control18:40
dwchadwickI would like us to define an ABAC interface for authorisation, where you pass a bunch of attributes and get a response. One of the attributes can be tenant=idx, another can be role=admin and another can be age=1918:40
dwchadwickThen we have a clean and simple interface that is fully flexible and extensible18:41
ayoungdwchadwick, the thing is, role is really the tuple "role-name, tenant-name"18:41
dwchadwickyes, and all of these concepts are confusing and end up creating spaghetti18:41
*** markmcclain has quit IRC18:41
*** metral has joined #openstack-meeting18:41
henrynashSo maybe the things is, we might indeed want to propose an ABAC interface, but in the meantime how to we have an RBAC interface that works well for enterprises?18:41
ayoungso "role:vm-administrator in tenant:live-servers" is different from "role:vm-administrator in tenant:staging-servers"18:41
*** markmcclain has joined #openstack-meeting18:42
dwchadwickwell ABAC is a superset of RBAC, so it can be introduced and be backwards compatible18:42
dwchadwickI would hope :-)18:42
*** MarkAtwood has joined #openstack-meeting18:42
heckjdwchadwick: I'm not at all opposed to that style of implementation, it fits pretty reasonably with the policy mechanisms that we're using to gate authorization today, but we need to continue to evolve, not trash and rebuild, the API and mechanisms we have today as well. We should not go for a "all in one rewrite" at this stage.18:42
dolphmheckj: i like the approach but know how to implement while maintaining backwards compatibility with roles18:43
dwchadwickneither should we complicate the interface by adding yet more concepts like groups18:43
henrynashdwchadwick: agree, but not sure we can go there in one hop18:43
henrynashdwchadwick: to previous comment don't agree that we should not add groups18:43
ayoungdwchadwick, OK, here is what we need:  a mechanism to apply the same set of attributes to more than one user at a time.18:44
dwchadwickthe first thing to do is design the new interface and then see how it can be made to migrate from the existing one to it18:44
*** cp16net|away is now known as cp16net18:44
heckjdwchadwick: For reasonable management, I don't see how we can avoid adding groups. The alternative is asking administrators of clouds to manage sets of individuals totally externally, or hack solutions in of their own.18:44
dwchadwickhenrynash: we are specifying the attribute mapping interface now which should give you what you want18:45
heckjayoung: +118:45
dolphmayoung: would need to also being able to specify an operation against a set of users with an arbitrary attribute18:45
dwchadwickayoung: attribute mapping18:45
ayoungdwchadwick, I think I might not have understood that concept that way when we discussed before18:46
dwchadwickayoung: anyone who is in group=my group has role=admin18:46
brich1ayoung: isn't role a name for an amalgam of permissions, the same way that group is a name for an amalgam of users? If so, solving one problem might solve two.18:46
henrynash…and all in a way that is simple for non-federated openstack implementations which will be the norm for some time to come18:46
dolphmdwchadwick: what's the benefit of an attribute mapping API without also changing the rest of the API to operate on attributes, and can you do that while maintaining backwards compatibility with the existing API in a single implementation?18:46
dwchadwickattribute mapping is completely independent of federation18:47
ayoungdwchadwick, right.  I think that is what we are trying to get at with groups.18:47
ayoungmapping is a more general purpose mechanism, but could be used to implement groups.18:47
dwchadwicki just gave an example above18:47
*** eglynn_ has joined #openstack-meeting18:48
ayoungdwchadwick, right...what I am thinking is that groups could be "pre-canned" attribute mappings18:48
dwchadwickthe interface we are proposing will allow organisations to define their own groups and say what roles they should have18:48
henrynashSo the risk is that if we do groups, we find, in the further, when we have ABAC, that we could implement the same ability….but in the meantime we have delivered the "normal way of doing this in RBAC environments" to build the acceptance of openstack18:49
ayoungdwchadwick, I'm kindof thinking that we might want to pull that out into its own blueprint, then, and specify how we would implement groups in terms of mapping18:49
dwchadwickayoung: not precanned, because you dont know what groups organisations will have. Henry gave examples of programmers, team leaders in one org, and teacher, pupil in another org18:50
henrynashdwchadwick +118:50
*** bklei has joined #openstack-meeting18:50
ksiuayoung: we're working on that18:50
dwchadwickOur blueprint will be out this week. We sketched it out today and Kristy is currently writing it up18:50
ayounghenrynash, I realize you want to get moving on this.  Can you work with Kristy on just that piece, and see if we can do it in such a way as to A)  get it in to grizzly and B) support what you need from groups?18:51
ayoungIt seems like it is at least worth evaluating the approach18:51
dwchadwickIt would be good if Henry could work with Kristy, since we are newbies to Openstack and Henry probably knows lots more than us about the internals18:52
ayoungit might be that we have to punt on the mapping approach if we can't get it in to Grizzly, in which case we accept groups approach as "stop gap" and we plan on reworking groups in terms of mappings in "H*" time?18:52
henrynashsure, happy to work with Kirtsy to investigate18:53
ayounghenrynash has PM'ed me "sure" which I think means he is willing to do it, and is accepting that my neck is not within throttling distance.18:53
*** CI_Guy has joined #openstack-meeting18:53
henrynashayoung :-)18:54
dwchadwickKristy is also able to work on the implementation to speed things up if the design is accepted18:54
henrynashI'd be keen to see the mapping design, anyhow18:54
dwchadwickWhat time frame are you looking at for grizzly release18:54
henrynashwe got to get it in for grizzly-2 ?18:55
heckjall code implemented by Feb 21st at the latest18:55
heckjJan 10th is much safer18:55
heckj(jan 10th is grizzly-2 milestone)18:55
dwchadwickGrizzly 2 should be Ok for the first release18:55
dwchadwickI can see a phased approach to implementation, with non-federated access initially then federated access afterwards18:56
*** brich1 has quit IRC18:56
dwchadwickWe want to get to the stage where the administrators dont have to have their un/pws configured into keystone, but use their own external IDP18:56
henrynashfor something like this, i say we must hit grizzly-218:57
dwchadwickWhat time is this call due to end?18:57
heckjgoing to have wrap this up in 2 minutes18:57
dwchadwickOk, so I will go now as I have an appointment. Bye18:58
*** dolphm has quit IRC18:58
*** pabelanger has joined #openstack-meeting18:58
*** primeministerp has quit IRC18:59
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:00
openstackMeeting ended Tue Nov 20 19:00:06 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-20-18.01.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-20-18.01.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2012/keystone.2012-11-20-18.01.log.html19:00
jeblairany ci people around?19:00
pabelangeron time this week too19:00
jeblairmordred: ping19:01
clarkbjeblair: I will ping him IRL. One sec19:01
*** ijw1 has joined #openstack-meeting19:01
fungihe said something about phone calls all day19:01
jeblairfungi: this meeting was scheduled well in advance.19:01
fungiindeed it was19:02
*** marek_ has quit IRC19:02
jeblair#startmeeting ci19:02
openstackMeeting started Tue Nov 20 19:02:42 2012 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
openstackThe meeting name has been set to 'ci'19:02
*** mnewby has joined #openstack-meeting19:02
jeblair#topic actions from last meeting19:02
*** openstack changes topic to "actions from last meeting"19:02
*** ijw11 has quit IRC19:03
*** dwchadwick has quit IRC19:03
jeblairfungi: it seems like progress with the foundation server, care to give an update?19:03
fungitoddmorey has set up a dummy interface on the foundation server and we've repointed review-dev at that now19:03
fungihe's requested saner error handling for gerrit's remote http calls, so i'm trying to dissect the code paths those take19:04
jeblairfungi: we can move forward with your "static string update" patch, right?19:04
fungithough i'm not really savvy with java, so i'm about to the point of bringing it up on #gerrit19:04
jeblairfungi: (I don't want the perfect solution to hold us up)19:05
fungithat'll be a temporary workaround19:05
jeblaircool, so assuming "making error handling nicer is an out-of-band project", what's next?19:05
fungihe's still working on integration on the foundation side of things19:05
fungii've got patches more or less ready for review.o.o once we're ready topull the trigger19:06
fungijust need a couple of trivial updates and a revbase19:06
fungier, rebase19:06
fungiwe've got a new official keypair generated and implemented for the contact info encryption19:06
fungithat's more or less it on that topic unless there are questions19:07
jeblairfungi: do you have a feeling for when this might be ready?19:07
fungiit's entirely dependent on when the remaining pieces come together on the foundation end19:08
jeblairand toddmorey isn't here.  :(19:08
fungihopefully no more than another week or so, but not under my control19:08
jeblairso before we roll this out in production, we need a few more things19:08
*** ksiu has quit IRC19:08
clarkbbut it sounds like things are rolling on the other end which is ++19:09
jeblairdoc updates to the wiki for new contributors (and old, who will be required to re-agree)19:09
jeblairif we want to stop running the sync script at the same time, we'll also need:19:09
*** mnewby_ has joined #openstack-meeting19:09
jeblairdoc updates to tell people how to manage the core and drivers groups in gerrit19:09
jeblairacl changes to allow self-management of those groups19:09
jeblairand changes to the bug/blueprint scripts to not assume lp/gerrit username equality19:10
jeblairand a nice announcement explaining all this and scheduling a time for the change19:10
*** mnewby has quit IRC19:10
jeblairnone of those things are very hard, i just wanted to put them out there.  :)19:10
jeblairpersonally, i'd like to stop running the sync script when we make this change19:11
fungiagreed. i think we really ought to be 100% positive review-dev is working the way we want before we announce/schedule however19:11
*** heckj has quit IRC19:11
jeblairany differing opinions on ending the sync script?19:11
jeblairthe main downside i see is that there are still a few groups that have overlap in LP and gerrit...19:12
clarkbjeblair: stopping the sync script is a big win. no opposition here19:12
jeblairthe release groups, and -drivers groups...19:12
fungidoesn't the sync script have some bearing on openid fixups though?19:12
jeblairbut i think the (distributed!) task of dual-maintenance of those groups is small, esp compared to the costs of running the sync script.19:12
jeblairfungi: with group self-management, we don't really care anymore.19:12
*** mnewby has joined #openstack-meeting19:13
*** jcooley_afk is now known as jcooley19:13
jeblairwe only care that the openids match users so that we can make sure the right gerrit users are in the -core groups, which at the moment, are managed in lp19:13
jeblairby making the group management happen in gerrit, that goes away...19:13
*** jcooley is now known as jcooley_afk19:13
jeblair-core members just have to add the correct gerrit user to their -core gerrit group19:14
*** mnewby_ has quit IRC19:14
jeblair(which is no more difficult than identifying the correct lp user, really, possibly less)19:14
jeblairfungi: answer your question?19:14
fungiokay, so the lp user/multiple openid situation isn't really at issue as long as groups aren't also managed via lp. got it19:15
*** jcooley_afk is now known as jcooley19:15
fungiand yes, my lack of timely responses is due only to the tin cans and string over which my internet connection is travelling at the moment19:15
fungii'm good with it19:15
jeblairyeah. it also affects the bug/blueprint scripts, but we can have them look up gerrit-username->openid->launchpad-person mapping when they go to do an update.19:16
*** mnewby_ has joined #openstack-meeting19:16
*** stevebake has quit IRC19:16
jeblair(they'll need gerrit database read access, but i don't think that's a problem)19:16
jeblair#action toddmorey continue to integrate gerrit contact store with foundation server19:17
*** mnewby has quit IRC19:17
*** mnewby_ is now known as mnewby19:17
jeblairanyone want to (a) write docs on the transition (b) update bug/blueprint scripts?19:18
*** littleidea has joined #openstack-meeting19:18
fungiput me down for those19:19
fungii haven't looked at the bug/bp scripts, but those can't be too complicated right? ;)19:19
jeblair#action fungi write docs on CLA/group changes19:19
clarkbfungi: the lp stuff is pretty straightforward19:19
clarkb(bugs, blueprints, etc)19:19
jeblair#action fungi update bug/blueprint scripts to use openids to look up lp usernames19:20
jeblairfungi: i can help out with that too19:20
*** patelna has joined #openstack-meeting19:20
fungijeblair: appreciated19:20
clarkbmaybe put the wiki changes in an etherpad19:20
fungiclarkb: yeah, i figure we'll want to stage those changes somewhere19:20
jeblairalso, we can actually make the bug/blueprint changes before everything else19:21
jeblair(ie, it should work if we put it in place right now)19:21
fungii'll put together a comprehensive etherpad to track the time-sensitive changes19:21
jeblair#action mordred bugify summit actions19:21
jeblair^ that's going to get reassigned real soon now19:21
uvirtbotjeblair: Error: "that's" is not a valid command.19:21
clarkbjeblair: he said earlier today that he started that process19:22
jeblairoh good!19:22
clarkbnot done, but he is working on it19:22
jeblair#action everyone collect action items from other summit session etherpads and register as bugs19:22
jeblairand i know i haven't done that one yet, so, oops.19:22
jeblair"clarkb look into subunit/testtools with coverage"19:23
jeblairclarkb: had time to look into that yet?19:23
clarkbjeblair: lifeless and I have chatted about it and I have a plan, but haven't implemented anything yet19:23
clarkbbesically we can run subunit under coverage when testr runs19:23
jeblairclarkb: does that involve post-run merging?19:24
clarkbinitially that will be done without parallel subunit execution to avoid the need for merging results19:24
clarkblong term lifeless' suggestion is to include coverage info in the subunit stream then testr can do the merging19:25
clarkbshort term will be equivalent to what we have today. long term will be a step up19:25
jeblair#action clarkb continue to look into subunit/testtools with coverage19:25
jeblair"clarkb document and test project creation change"19:25
jeblairclarkb: i think that has happend, yeah?19:26
clarkbit did. I think we/I may end up needing to write a little more documentation, but the puppet + python script is working19:26
jeblairclarkb: where is documentation lacking?19:26
clarkbstackforgers are a primary consumer of the new tool and the docs don't directly address stackforge19:26
clarkbneed a if you are adding a stackforge project do foo and bar section19:27
*** littleidea has quit IRC19:27
jeblairclarkb: yeah, i think a bit of a reorg may be in order...19:27
jeblairclarkb: i'm thinking a lot of the new stuff could go into a "howto: create a new project" section19:27
jeblairclarkb: (which isn't gerrit-specific, like the current one)19:28
clarkband that should cover things like gitreview, zuul and JJB, and launchpad (or maybe gerrit groups)19:28
jeblairclarkb: exactly.19:28
mordredjeblair, clarkb: ++19:28
mordred(lurking, but in an in-person meeting)19:28
*** stevebake has joined #openstack-meeting19:28
*** littleidea has joined #openstack-meeting19:29
jeblairmordred: this one's cooler.  and also has persons.  ;)19:29
*** AlanClark has quit IRC19:29
jeblairclarkb: want to volunteer for that?19:29
clarkbjeblair: sure19:29
* fungi is not a person19:29
clarkb#action clarkb write a howto: create a new project in openstack-ci docs19:29
jeblair"jeblair finish updates to sync script"19:30
jeblairso that's basically done...19:30
fungijust in time to deprecate it?19:30
jeblairbut then i got sick and haven't done final testing/polishing on it.19:30
jeblairand then it looks like we might actually be able to deprecate ti...19:30
jeblairso i'm thinking i'll just sit on that and see where we are next week.19:31
clarkbjeblair: to test it you should be able to drop it into review-dev19:31
fungiif nothing else, your investigation into the lp/openid api additions will help the bug/bp script updates19:31
clarkbreview-dev runs the sync script as well19:31
jeblairclarkb: yeah, i've been testing it locally with a db dump from review dev.19:32
jeblairanyway, like i said, if it looks like it may be useful next week, i'll finish it up.  otherwise, i'm happy to be rid of it.  :)19:33
clarkbsounds good to me19:33
jeblairfungi: and yeah, there's some code/experience there that should make the bug script updates easy19:33
jeblair"jeblair propose a system for linking reverifies to bugs"19:33
fungii will feast on whatever part of your brains contains that experience19:33
jeblairi have not done that.  but i have thought about it.  :)19:34
jeblair#action jeblair propose a system for linking revierifies to bugs19:34
clarkbjeblair: do we want it to be more robust than simply updating the regex in layout.yaml?19:34
jeblairclarkb: yeah, i think the main component is the reporting...19:34
clarkbjeblair: the comment contents already end up in the zuul logs19:34
fungithough i suppose the bug linking can come first and reporting second19:35
clarkbmaybe reporting is an offline grep through the logs?19:35
*** salv-orlando has quit IRC19:35
jeblairclarkb: which i think should be something that watches for reverifies and produces a web page with like the top 10 bugs19:35
*** salv-orlando has joined #openstack-meeting19:35
clarkb(more robust is definitely better though, could check the bug is valid in LP and matches and openstack project for example)19:35
clarkbjeblair: ++19:35
fungiyes, some way of actually forcing people to have a real lp bug open before being able to reverify would be good19:36
jeblairi think the reporting is what makes it less "annoying thing the ci people are making us do" and more "useful thing to direct testing and developer resources at known problems"  :)19:36
fungiso in that regard, i guess not annoying the devs until we can give them useful reports would be good after all19:37
fungior at least a promise of reports rsn19:37
jeblairyeah.  i don't think that'll be too hard though.  gerritlib script that watches the event stream, totals bug links, then spits out some html to a static web page.19:37
jeblair_or_ we could try to pretend that's in-scope for zuul.  :)  i'm not convinced.19:38
jeblair#topic grenade/quantum19:39
*** openstack changes topic to "grenade/quantum"19:39
fungii'd be interested to see gerritbot mention the reverifies in #-infra maybe19:39
clarkbfungi: ++19:39
jeblairI've restarting work with nachi on quantum.  it needs some more changes before it's ready, but progress is being made19:39
* fungi curses his flaky internets19:39
*** nachi has quit IRC19:39
*** annegentle__ has quit IRC19:39
jeblairfungi: +119:39
jeblairi'll probably not get to revisiting grenade until next week19:39
jeblairanyone have other topics?19:40
clarkbpypi uploads19:40
jeblair#topic pypi uploads19:40
*** openstack changes topic to "pypi uploads"19:40
clarkblast week it became apparent that stackforgers could make use of jenkins jobs to upload their packages to pypi19:41
*** mnewby has quit IRC19:41
clarkbwe can't let them run the existing jobs because arbitrary code on hosts with passwords, so to better accomodate them and stop trusting openstack projects I have added two new jenkins job templates to make this more secure19:41
clarkbbasically create an sdist on a normal jenkins slave, copy that to a slave with pypi credentials and use curl to upload the sdist to pypi19:42
* jeblair cheers19:42
clarkbnow no more arbitrary code is executed to upload changes to pypi19:42
clarkb#link https://review.openstack.org/#/c/16501/19:43
clarkbis the last change needed to make it work in the way that is expected (upload meta data being the current missing piece)19:43
jeblairclarkb: cool, so we should be able to update all the projects after that's merged19:43
jeblairbut maybe we'll make one more jjb release first.  :)19:44
clarkbjeblair: yes, that is probably a good thing19:44
clarkband we keep getting more JJB patches19:44
jeblairyay more jjb contributors!19:44
fungiclearly it fills a previously unaddressed niche19:44
jeblairanything else?19:45
fungijeblair: you were wanting to also do a g-r release via traditional methods too, yes? or wait for the pipy automation?19:46
jeblair#topic git-review19:46
*** openstack changes topic to "git-review"19:46
jeblairfungi, saper, and I have tested git-review HEAD19:46
jeblairwe haven't seen any major regressions, which is expected since currently it only contains one patch over 1.1919:46
jeblairwhich fixes the upgrade bug19:46
jeblairso I'll release that today,19:47
jeblairthen we'll merge documentation of the testing we've done19:47
*** sarob has joined #openstack-meeting19:47
jeblairand open git-review to more substantial changes19:47
clarkbjeblair: saper mentioned a bug, in -infra. Did yo usee that?19:47
*** annegentle_ has joined #openstack-meeting19:47
jeblairwe still expect it to work on every commit, but we'll be doing manual regression testing before we make another release19:48
clarkblooks like its a bug when downloading a change from a different project19:48
clarkbmaybe that is out of scope19:48
fungioh, that reminds me from this morning... hashar found the previoys commit for the -W option, so i'll see if i can port that to a 1.21 target if nobody beats me to it19:48
*** arbrandes has joined #openstack-meeting19:48
*** littleidea has quit IRC19:48
jeblairclarkb: yeah, if that's what it is, then i'd say it can wait for the next release19:48
fungiseems like that bug saper found has probably been hiding in there a while19:49
jeblair#topic stackforge19:50
*** openstack changes topic to "stackforge"19:50
jeblairconsidering the large number of new stackforge projects that have recently been or are expected to be added...19:50
*** annegentle__ has joined #openstack-meeting19:51
jeblairi thought it'd be a good time to remind people that the primary goal of the infrastructure and ci teams is to support the openstack project19:51
*** jpich has joined #openstack-meeting19:51
*** markmc has joined #openstack-meeting19:52
fungito that end, a semi-official statement on what stackforge is and isn't might be in order19:52
jeblairstackforge is an important area that the ppb has asked us to support as well, but not at the expense of attention and resources for the openstack projects19:52
*** jcooley is now known as jcooley_afk19:52
jeblairi expect new stackforge projects to be completely self-sufficient, and i also expect them not to divert time from the infrastructure team, at least, not without giving something back, preferably in the form of people with general interest in the openstack project infrastructure and ci19:54
clarkbspeaking of zykes- added a simple jenkins job to support readthedocs (FYI to other projects that want to use RTD)19:54
*** annegentle_ has quit IRC19:55
*** gabrielhurley has joined #openstack-meeting19:55
*** dolphm has joined #openstack-meeting19:55
fungijeblair: that sounds entirely reasonable to me19:56
*** heckj has joined #openstack-meeting19:56
ttxjeblair: +119:56
jeblairso i hope that helps people prioritize work and reviews appropriately.  i know some people may not have been around when stackforge started, and it may be helpful to know that concern and decision on prioritization was explicit.  :)19:56
jeblairttx was there.  :)19:56
jeblairand since he's here now, i think it's probably time to19:57
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:57
openstackMeeting ended Tue Nov 20 19:57:18 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/ci/2012/ci.2012-11-20-19.02.html19:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/ci/2012/ci.2012-11-20-19.02.txt19:57
openstackLog:            http://eavesdrop.openstack.org/meetings/ci/2012/ci.2012-11-20-19.02.log.html19:57
*** eglynn_ has quit IRC19:57
ttxyou still had 3 minutes :)19:57
clarkbdon't forget thanksgiving is thursday19:58
jeblairttx: we're efficient19:58
*** CI_Guy has quit IRC19:58
*** pabelanger has left #openstack-meeting19:58
* ttx just likes milestone weeks that double as thanksgiving weeks19:58
jeblairttx: we always finish early when mordred doesn't show up19:58
clarkbyes, I think at least on project is releasing a milestone on thursday19:59
ttxjeblair: yeah, i wonder why.19:59
annegentle__ttx you're clever that way19:59
* clarkb will most likely be away from Internets19:59
*** zaneb has joined #openstack-meeting19:59
ttxWho is around for the TC meeting ?20:00
bcwaldonttx: you know it20:00
bcwaldonlooks like all the important ones are here20:00
bcwaldonlets get started20:00
ttx6.. 7 if heckj does more than lurking20:00
*** eglynn_ has joined #openstack-meeting20:01
* heckj is a professional lurker20:01
ttxthat's 9! let's get started20:01
russellbbcwaldon: ಠ_ಠ20:01
notmynameheckj: I've seen you not in IRC before!20:01
* heckj hides20:01
ttx#startmeeting tc20:01
openstackMeeting started Tue Nov 20 20:01:33 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:01
openstackThe meeting name has been set to 'tc'20:01
ttxAgenda for today is:20:01
ttx#link http://wiki.openstack.org/Governance/TechnicalCommittee20:01
*** mnewby has joined #openstack-meeting20:01
ttx#topic Vote on direction for Incubator/Core process update20:02
*** openstack changes topic to "Vote on direction for Incubator/Core process update"20:02
ttxThis is about selecting a vision for how to handle incubation and core inclusion in a world where the TC coexists with the BoD20:02
ttxThis vision will be defended by 2 or 3 TC members in a joint committee with BoD representatives, starting next week20:02
ttxWe had a lengthy thread at:20:02
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2012-November/thread.html#238720:02
ttxThree visions emerged, which I would summarize like this:20:02
ttx* (markmc) Separate the trademark question from the "developed under OpenStack umbrella" question, have incubation be the process by which you become supported20:03
*** maurosr has quit IRC20:03
ttx(please add more to that description if you think it's unfair or incomplete)20:03
ttx* (annegentle) Same as markmc, but separate the "developed under OpenStack umbrella" projects into two categories with different associated resources attached to them20:03
*** vipul is now known as vipul|away20:03
*** vipul|away is now known as vipul20:03
ttx* (notmyname) Keep core co-defined by TC and BoD, restrict core to IaaS projects, incubation is the road to core, keep other projects out of OpenStack infrastructure and focus20:03
*** eglynn_ has quit IRC20:03
ttxAs far as the discussion with the BoD is concerned, it just looks like two options to me20:04
ttxOne of them with two variants on how the TC would internally organize the resources associated to projects20:04
ttxSo as a first step I propose we vote between:20:04
ttx* (annemark) Separate the trademark question from the "developed under OpenStack umbrella" question, have incubation be the process by which you become supported, potentially with multiple categories as far as associated resources are concerned20:04
ttx* (notmyname) Keep core co-defined by TC and BoD, restrict core to IaaS projects, incubation is the road to core, keep other projects out of OpenStack infrastructure and focus20:05
ttx* (abstain) None of the above, we need to discuss this for one more week20:05
*** novas0x2a|laptop has joined #openstack-meeting20:05
ttxAny question/discussion needed before we start voting ?20:05
gabrielhurleyare we voting numerically, by name, etc?20:05
russellbcan we give options a number so the vote results don't look like a popularity contest?  heh20:05
ttxrussellb: i can do that20:06
markmcthis annemark person sounds awesome20:06
annegentle__I won't get my feelings hurt, really20:06
ttxgabrielhurley: you'll see when I start the vote process20:06
*** alexpilotti has quit IRC20:06
* annegentle__ snorts20:06
ttxeveryone cool with voting on this now ?20:06
* ttx freezes20:07
notmynamewhat's the criteria? majority? plurality? supermajority? unanimous?20:07
ttxnotmyname: same as usual. We'll have optionA, optionB, abstain20:07
annegentle__is the vote for "this is what we tell the board we agree to?"20:08
ttxto win, optionA needs more votes than optionB20:08
ttxand at least 5 votes20:08
ttx(same as a yes/no motion)20:08
notmynameok, thanks20:08
ttxnotmyname: that would make it a majority with affirmative voting threshold.20:09
*** mikal has joined #openstack-meeting20:09
ttxOK, so option1 = annemark, option2 = notmyname, abstain = abstain20:09
*** bklei has quit IRC20:10
ttx#startvote Which vision for incubation process should we defend in the BoD/TC joint committee? option1, option2, abstain20:10
openstackBegin voting on: Which vision for incubation process should we defend in the BoD/TC joint committee? Valid vote options are option1, option2, abstain.20:10
openstackVote using '#vote OPTION'. Only your last vote counts.20:10
russellb#vote option120:10
markmc#vote option120:10
gabrielhurley#vote option120:10
annegentle__#vote option120:10
bcwaldon#vote option120:10
ttx#vote option120:10
notmyname#vote option220:10
danwent#vote abstain20:10
jgriffith#vote option120:10
heckj#vote option120:10
ttx30 more seconds20:11
*** spn has quit IRC20:11
mordred#vote option120:11
openstackVoted on "Which vision for incubation process should we defend in the BoD/TC joint committee?" Results are20:11
openstackabstain (1): danwent20:11
openstackoption2 (1): notmyname20:11
openstackoption1 (9): markmc, bcwaldon, ttx, heckj, russellb, jgriffith, mordred, gabrielhurley, annegentle__20:11
ttx#agreed option1 (annemark) vision will be defended on the BoD/TC joint committee on the future of incubation/core20:12
ttxdanwent: does your abstain mean you'd have love to have time to propose another option ?20:12
*** mnewby_ has joined #openstack-meeting20:12
heckjno love for danwent!20:12
vishy#vote option120:12
*** AlanClark has joined #openstack-meeting20:12
ttxDo we want to vote today on which of the two variants should be preferred ? Or leave that for a future discussion if our vision ends up prevailing in the joint committee ?20:12
vishybtw :)20:12
danwentttx: no, it means I am sorry to say I didn't have time to read the whole thread, and therefore am not properly informed20:12
ttxvishy: too late :P20:12
ttxdanwent: ok20:13
annegentle__at least you're honest danwent :)20:13
markmcttx, it might be useful info to help those on the sub-committee, maybe a "testing the water" vote ?20:13
*** mnewby has quit IRC20:14
markmcttx, it might be all need to be revisited after first sub-committee discussions20:14
markmcwho knows20:14
russellbis it a final declaration, or a "this is how i feel right now, but would abstain if this were a final decision"20:14
ttxmarkmc: I'm fine with a non-binding vote between the two variants, to serve as indicator... if everyone is fine with that20:14
russellbi could do that.  there hasn't been enough discussion on that topic specifically on the list to do a final vote IMO20:15
annegentle__I'd like the extra info as well20:15
markmcmaybe a vote would no abstain option would be the way to do that20:15
ttxmaybe we can informally state our preference rather than use the vote20:15
* ttx isn't convinced either way yet (abstain)20:15
annegentle__I like informal rather than a vote20:15
markmcannegentle__, good point20:16
markmcwhat's people's thinking?20:16
russellbok, so informally ... i really don't like the idea of categories because it seems like putting projects in tiers, and having "second class citizens"20:16
russellband we just need to figure out how to scale the whole project20:16
gabrielhurley+1 to russellb20:16
*** lloydde has quit IRC20:16
bcwaldon+1 to gabrielhurley20:16
russellbgrowing pains be damned, we're going to grow20:16
jgriffithpersonally I'm on the opposite end of that spectrum20:16
zanebfwiw I think it's great that annegentle__ is looking at what the barriers to scaling are and trying to find ways to grow the project without taking resources from existing projects20:16
* ttx thinks it might end up being necessary to have multiple tiers, though I'd prefer if we didn't have to...20:17
zanebI can't comment on the specifics because I'm not familiar enough with them20:17
annegentle__I thought of another scenario we're seeing, and that's projects that are open source like StachTach that have no (stated) desire to be subject to OpenStack processes -- is this the other direction we'll see depending on how we have incubation work?20:17
russellbif docs are a scaling pain point, then *all* projects need to step up and help fill that gap20:17
jgriffithrussellb: growing is good, growing to an unmanageable collage of projects is not so good IMO20:17
russellbsure, need to have standards.20:18
markmcannegentle__, if projects don't want to be in, they're just not in imho20:18
russellbjgriffith: but with categories, i'm afraid the second tier will become that unmanageable collage20:18
vishyI like the simplicity of no categories but I really think we should keep projects in incubation for longer in that case20:18
*** vipul is now known as vipul|away20:18
markmcI imagine for stuff like docs, we'll have "informal tiers" anyway20:18
jgriffithrussellb: fair point20:18
markmcbut they're just gaps where we need folks to step up20:19
vishyas in there should be some form of quality control for moving out of incubation20:19
markmcwe have "good at bug triaging and sucky at bug triaging" tiers now20:19
annegentle__yeah we do have informal tiers already for various reasons20:19
markmci.e. nova vs the rest20:19
gabrielhurley+1 to more rigorous incubation20:19
ttxmarkmc: yeah20:19
jgriffithI could see the more rigorous incubation as a good compromise20:19
russellbsure, +1 from me too20:19
ttxok, anyone else wanting to voice their opinion on this, before we talk about WHO we send to that joint committee ?20:20
ttx(we can come back to this, time permitting, at the end of the meeting20:20
jaypipesfor the record I vote option120:20
jaypipessorry I'm late20:20
* mordred punches jaypipes20:20
*** mnewby_ has quit IRC20:21
markmcsettle down kids20:21
*** eglynn_ has joined #openstack-meeting20:21
ttx#topic Choice of TC members to represent that direction on the BoD/TC joint committee20:21
*** openstack changes topic to "Choice of TC members to represent that direction on the BoD/TC joint committee"20:21
ttxSo... we need to pick two or three TC members to represent that chosen vision20:21
* jaypipes votes annegentle__ and markmc20:21
ttxThe obvious choice is markmc and annegentle, as the original proposers, but they may not volunteer20:21
markmcprobably obvious I'm happy to represent20:22
*** jcooley_afk is now known as jcooley20:22
markmcannegentle__ and ttx would be other obvious choices20:22
ttxAnyone else who wants to defend this to the joint committee ?20:22
gabrielhurleywhen/where is the meeting?20:22
* mordred can/will be around20:22
ttxgabrielhurley: I have NO idea20:22
vishyit seems like there is more to it than just what we present20:22
mordredbut also can represent from the other side :)20:22
ttxthey asjked us to come up with names by the end of the week20:22
annegentle__I think I can make the commitment but if I pick up an intern that may change20:22
*** oNeToWn has quit IRC20:22
annegentle__I won't know until next month20:22
ttxmordred: that's smarter to try to get into that committee from the other side20:22
vishyWe are saying that the TC is giving responsibility for "CORE" to the BoD20:22
ttxI can volunteer as a substitute, if one ends up being needed.20:23
mordredttx: k20:23
vishybut they still may want input from us20:23
markmcvishy, where "CORE" == "list of projects for trademark"20:23
vishymarkmc: correct20:23
markmc(just being clear :)20:23
ttxvishy: we have no idea how that discussion is going to go anyway, I expect the chosen ones to come back and report to the TC20:23
zanebmarkmc: what if the board is more interested in controlling the scope of OpenStack, rather than the trademark?20:24
markmczaneb, I don't think we need to get into hypotheticals20:24
ttxso... markmc+annegentle, with me as substitute if one is needed ? anyone else wanting to play ?20:24
gabrielhurleythat's why you take the baseball bats20:24
markmcthe TC representatives clearly don't have a mandate to agree to that20:24
zanebfair enough20:25
annegentle__russellb: are you interested?20:25
russellbi could substitute if needed as well, sounds like a fun time.20:25
* annegentle__ can read minds20:25
markmcannegentle__, ok smarty pants, what are the board people going to say? :)20:25
* markmc tests annegentle__ skillz20:25
annegentle__magic 8 ball says "Future cloudy"20:26
russellbi see what you did there.20:26
ttxdo we need a vote on that or is anyone fine with markmc+annegentle with russellb+ttx as substitutes if need be20:26
annegentle__sounds good20:26
*** mnewby has joined #openstack-meeting20:27
ttx#agreed TC members to represent in the BoD joint committee on incubation/core: markmc+annegentle (russellb+ttx to serve as substitutes if needed)20:27
* ttx is happy we came up with something in the limited time that was given to us to organize this20:28
ttx#topic Ongoing discussion: Distro & Python 2.6/3.x support policy20:28
*** openstack changes topic to "Ongoing discussion: Distro & Python 2.6/3.x support policy"20:28
ttxmordred: you were supposed to push a thread on the ML on that topic20:28
ttxAre we waiting on that ML thread to start, or should we use part of the remaining time in the meeting to continue the preliminary discussion on that ?20:28
*** sudorandom has joined #openstack-meeting20:28
mordredttx: yes. we are waiting on the ML thread to start - my bad20:29
markmcWhat's the pressing thing here?20:29
markmcwhat to do CI on?20:29
*** spligak has joined #openstack-meeting20:29
*** briancline_ has joined #openstack-meeting20:29
markmce.g. are there 3.x patches waiting for be merged but can't because it would kill 2.6 support?20:29
markmcfor be merged20:29
ttxmordred: ? ^20:30
mordredmarkmc: there's a thread that needs to be started20:30
mordredmarkmc: I could write it all here, but it would be better if I just write the email20:31
russellbI'd like to see a good documented list of all the 3.x blockers, as I suspect 2.6 support isn't the only one (dependencies)20:31
markmcmordred, ok20:31
* russellb retracts and waits for ML thread20:31
ttx#topic Open discussion20:31
*** openstack changes topic to "Open discussion"20:31
mordredmarkmc: the tl;dr is "what do we as a project care about" - but the definitions of that get intricate20:31
*** mnewby has quit IRC20:31
ttxThen we are back to the open discussion on incubation/core20:31
ttxI think we'll still have to build up guidelines for inclusion/exclusion, and those will define how inclusive we end up being20:32
markmcwhat did folks think of my starting point20:33
* markmc digs up the link20:33
ttxeven if markmc's vision included a tendancy to be inclusive20:33
markmcfootnote of20:33
markmc#link http://lists.openstack.org/pipermail/openstack-dev/2012-November/002470.html20:33
markmcprobably the scope part needs most debate20:34
ttxIn particular, I think we need to limit the rhythm of growth to something we can handle20:34
markmc"measured growth"20:34
ttxi.e. not doubling the number of projects every 6 months20:35
*** MarkAtwood has quit IRC20:35
* markmc cracks open a beer, passes one to ttx and puts his feet up in front of the fire20:36
ttxI'm fine with ending the meeting now, unless someone has something else to say20:36
* mordred enjoes beer20:36
markmcyeah, sounds like the topic has us all a bit drained20:36
* mordred wishes markmc had given him one20:36
* russellb is jealous he didn't get a beer :(20:36
heckjmarkmc: I generally liked it, with a heavy preference to anything in the bundle of "OpenStack projects' having a very high score on integration20:37
*** adjohn has quit IRC20:37
markmcheckj, cool20:37
heckjmarkmc: I personally think interop is the hardest linkage to maintain, and where we're still somewhat shakey - even with current core projects.20:37
heckjIt's where I'm spending all of my time20:37
ttxthere will be some floating period until we hear back from the joint committee anyway...20:38
heckjmarkmc: I took your first three footnotes as a prerequisite and given to be even thought of20:38
ttxno need to get too far if that vision is shot down early20:38
* jgriffith is saving his energy until then...20:38
mordredyeah. I'm also saving energy until committee feedback time20:39
*** maoy has joined #openstack-meeting20:39
markmcmordred, hey, I assume you'll be a board rep on this thing? :)20:39
russellbso mordred, what will the board say?  :)20:39
* markmc watches mordred juggle hats20:40
ttxok, I can do with one short TC meeting, let's end this20:42
ttxnext week we should have Monty's stuff to discuss, if he gets around to posting this20:42
ttxthanks everyone!20:42
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:42
openstackMeeting ended Tue Nov 20 20:42:36 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:42
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2012/tc.2012-11-20-20.01.html20:42
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2012/tc.2012-11-20-20.01.txt20:42
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2012/tc.2012-11-20-20.01.log.html20:42
jeblairttx: you had 17 minutes left.  ;)20:42
ttxjeblair: you started that trends20:43
fungittx was trying to one-up you i think20:44
fungior fourteen-up i guess20:44
AlanClarkping ttx20:47
ttxAlanClark: pong20:47
AlanClarkhey ttx, looks like I missed the TC meeting?20:48
AlanClarkguess I was an hour off20:48
ttxAlanClark: just ended20:48
*** lloydde has joined #openstack-meeting20:48
*** vipul|away is now known as vipul20:49
AlanClarkI'd like to sync up regarding the incubation/core work20:49
*** Vek has joined #openstack-meeting20:50
ttxAlanClark: sure, see private message ?20:50
ttxAlanClark: Anne Gentle and Mark McLoughlin will represent the TC in the joint committee20:51
AlanClarkI'd like to setup a "kickoff" meeting20:51
AlanClarkThere's lots of ideas for an agenda - which means it could be a looong first meeting.20:52
AlanClarkAm wondering if  they would be open to a F2F or if we need to break down the agenda and do it online20:52
AlanClarkover time20:52
*** devananda has quit IRC20:52
*** devananda has joined #openstack-meeting20:53
ttxAlanClark: I suggest you reach them by email, i'll send those to you20:54
*** adjohn has joined #openstack-meeting20:54
annegentle__I'd be willing to meet F2F but really depends on where/when -- anne dot gentle at rackspace dot com20:54
*** SlickNik has joined #openstack-meeting20:55
*** jog0 has joined #openstack-meeting20:56
*** jog0 has joined #openstack-meeting20:57
*** dwchadwick has joined #openstack-meeting20:59
*** dwchadwick has left #openstack-meeting21:00
*** dhellmann has joined #openstack-meeting21:00
ttxmarkmc, heckj, notmyname, bcwaldon, jgriffith, vishy, gabrielhurley, danwent: around ?21:01
bcwaldonttx: hey hey21:02
ttxmissing vishy and heckj, hopefully they will join21:02
ttx#startmeeting project21:03
openstackMeeting started Tue Nov 20 21:03:04 2012 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:03
openstackThe meeting name has been set to 'project'21:03
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:03
ttxNote that the agenda order was slightly reworked in order to have common topics first21:03
*** dprince has quit IRC21:03
ttxso when you're done you can more easily ignore the rest of the meeting :)21:03
ttx#topic General announcements21:03
*** openstack changes topic to "General announcements"21:03
stevebakeo/ for heat21:03
ttx#info At the end of today (i.e. tomorrow European morning), I'll cut the milestone-proposed branches for the projects that do grizzly-121:04
ttxIn this meeting we'll look into grizzly-1 status and defer bugs/blueprints where appropriate21:04
*** sarob has quit IRC21:04
ttxmordred, annegentle, davidkranz: Anything in CI, QA or Docs that you want to bring to the general attention ?21:04
markmcttx, if you want common stuff first, maybe put stable branch in there too21:04
*** maoy_ has joined #openstack-meeting21:04
markmcttx, this week is supposed to be 2012.2 release week21:05
ttxmarkmc: good point21:05
ttxmarkmc: go ahead21:05
annegentle__yes, we now have a new Basic Install guide at http://docs.openstack.org/folsom/basic-install/content/21:05
markmcok, so at the summit we agreed a tentative schedule21:05
davidkranzttx: Just that attempts to run the ful tempest gate are now failing quite often.21:05
markmc#link https://etherpad.openstack.org/process-stable-branch21:05
markmc2012.2 was put in for November 22nd21:05
markmcdidn't realize it was thanksgiving at the time21:06
markmcbut we're in pretty good shape for a release IMHO21:06
davidkranzThis bug: https://bugs.launchpad.net/nova/+bug/107968721:06
uvirtbotLaunchpad bug 1079687 in nova "Flaky failures of instances to reach BUILD and ACTIVE states" [Undecided,New]21:06
markmcbugs fixed:21:06
markmc 37 nova21:06
markmc 25 quantum21:06
markmc  9 glance21:06
markmc  6 keystone21:06
markmc  3 cinder21:06
markmc  1 horizon21:06
markmc 81 total21:06
markmcI'm thinking of going ahead and announcing RC tarballs21:06
*** maoy has quit IRC21:06
*** maoy_ is now known as maoy21:06
markmcand pushing the release as planned on Thursday21:06
markmcdon't want to do it the same week as grizzl-121:07
markmcdon't see the need to push it out 2 weeks21:07
ttxmarkmc: not worth waiting one more week ?21:07
davidkranzttx: Perhaps this group can figure out how to get that issue involved as it is not clear where the problem lies.21:07
ttxmarkmc: grizzly-1 is this week21:07
markmcttx, ah, perfect - I got mixed up21:07
markmcttx, ok, let's do it next week21:07
ttxmarkmc: sounds good21:07
markmcI'll send out a mail21:07
markmcif PTLs know of fixes that need backporting21:08
markmcnows a good time21:08
ttx#info 2012.2.1 scheduled for next week21:08
ttxdavidkranz: looks like Nova failures ?21:08
davidkranzttx: Yes.21:08
davidkranzttx: But it could be an infrastructure issue.21:08
ttxdavidkranz: ok, we can cover it in the Nova topic, hopefully we'll have vishy by then21:09
davidkranzttx: Great.21:09
ttxAnything else for the general crowd before we dive into project-specific topics ?21:09
*** jhenner has joined #openstack-meeting21:09
ttx#topic Oslo status21:10
*** openstack changes topic to "Oslo status"21:10
ttxmarkmc: welcome back21:10
markmcthanks, I've been a little AWOL21:10
* markmc done with travelling21:10
ttxIncomplete action item: markmc to file blueprint for oslo-config release21:10
markmc#link https://launchpad.net/oslo/+milestone/grizzly-121:10
markmcttx, ah, good point21:10
ttx#action markmc to file blueprint for oslo-config release21:11
markmcalso need to dig into the release version thing21:11
markmcboth are related21:11
ttxok, looking at g121:11
ttxcfg-argparse: should it be considered implemented ?21:11
ttxoh it was21:11
markmcyeah, want to get all the projects using it21:11
ttxin the last 5 minutes21:11
markmcbut that'll be grizzly-2 at this point21:11
ttxoslo-release-versioning: defer to g2 ?21:12
* markmc does that21:12
markmcbit behind on bug triage too, but don't see anything too scarey21:12
ttxmarkmc/others: Anything you wanted to raise on oslo, before we switch to next topic ?21:12
*** olaph has joined #openstack-meeting21:12
ttx#topic Keystone status21:13
*** openstack changes topic to "Keystone status"21:13
ttxheckj: hello!21:13
ttx#link https://launchpad.net/keystone/+milestone/grizzly-121:13
heckj(refresh if you haven't recently - was cleaning in past 30 minutes)21:13
* ttx refreshes21:13
ttximplement-v3-core-api: how far are we ?21:14
heckjtwo blueprints are pending code reviews, and look to be complete by Thursday21:14
heckjFor a tech preview, we're looking good - starting to log new bugs, etc. and deal with issues as they've been coming up21:14
ttxheckj: trick is, we are supposed to cut the branch at the end of today, not the end of Thursday21:14
heckjAh - thought the date was the 22nd21:14
*** rnirmal has quit IRC21:15
* gabrielhurley thought that too21:15
jgriffithheckj: That makes two of us21:15
ttxthe branch lives for two days before being released21:15
ttxwith only the theoretical bugfix backports21:15
heckjI think we'll want to update the Grizzly Release page with that detail - I certainly didn't expect that21:15
* gabrielhurley never saw that page21:16
* jgriffith says "well crap"21:16
ttxit's only g1, so I guess we could do the milestone cut slightly later21:17
heckjtwo pending reviews to complete the V3 API - that's all that remains21:17
ttxwould Thursday EU morning be OK with you ?21:17
ttxthen I can publish the milestone on Friday morning, while it's still Thursday somewhere21:17
ttxok, let's do that.21:18
ttxSorry I thought that was clear (that's how we did all the folsom milestones, no change in that area)21:18
ttxheckj: so implement-v3-core-api and rbac-keystone-api should be in by EOD tomorrow ?21:19
heckjYes. In other news, ton of bugs nailed down, including auth_token into a separate repo (keystoneclient)21:19
ttxAnything more about Keystone ?21:19
heckjthat's it from me21:19
ttx#topic Swift status21:20
*** openstack changes topic to "Swift status"21:20
ttxnotmyname: o/21:20
ttx1.7.5 was released last week...21:20
ttxnotmyname: Anything planned yt for 1.7.6 ?21:20
notmynamedates? no21:20
*** Hitesh has quit IRC21:20
ttxnotmyname: did you get to the bottom of your -announce issues ?21:21
notmynamettx: I sent several messages, all rejected (as expected)21:21
ttxfor what reason ?21:21
ttxit should say "message held for moderation", not "rejected"21:21
ttxthen I can whitelist you21:22
ttxbut at this point your emails don't even show up on the moderation panel21:22
notmynameYou are not allowed to post to this mailing list, and your message has21:22
notmynamebeen automatically rejected.21:22
ttxnotmyname: hmm, weird. Are you a list member ?21:22
ttxmaybe that would explain the difference with others that we could moderate in21:23
*** thingee has joined #openstack-meeting21:23
ttxnotmyname: your call, jhoin the list and repost, or forward me the email contents and i'll post it for you21:23
notmynameI'll try again21:23
ttxThat's all I had. Anything else about Swift before we move to Glance ?21:23
*** jhenner has quit IRC21:24
ttx#topic Glance status21:24
*** openstack changes topic to "Glance status"21:24
ttxbcwaldon: hi!21:24
bcwaldonttx: hello!21:24
ttx#link https://launchpad.net/glance/+milestone/grizzly-121:25
bcwaldondon't act like you're not impressed21:25
ttxso *you* are done21:25
*** SlickNik has left #openstack-meeting21:25
ttxbecause *you* knew that Tuesday is always the cut date.21:25
ttxjust saying21:25
ttxOn the general grizzly plan, did you sort out streaming-server priority?21:26
bcwaldonmaybe not21:26
ttxMaybe set it to Low and keep it as a target of opportunity ?21:26
bcwaldondoing it now21:26
bcwaldonttx: ah, I untargeted it already21:26
ttxso I can cut milestone-proposed for Glance tomorrow morning ? and let it live with the occasional backport for a few days ?21:26
bcwaldonyes you may21:26
ttxbcwaldon: so I should remove the series goal too, so that it doesn't pollute the view21:27
bcwaldonfine with me21:27
*** ryanpetr_ has joined #openstack-meeting21:27
ttxbcwaldon/others: Anything more on Glance before we switch to Quantum ?21:27
bcwaldonttx: Released python-glanceclient v0.6.0 last night21:27
bcwaldonwriting up a note for the list today21:28
ttxnice. Anything we should know about it ?21:28
bcwaldon#link http://docs.openstack.org/developer/python-glanceclient/#id121:28
ttxbcwaldon: anything else ?21:29
bcwaldonttx: that would be it21:29
ttx#topic Quantum status21:29
*** openstack changes topic to "Quantum status"21:29
ttxdanwent: o/21:29
ttx#link https://launchpad.net/quantum/+milestone/grizzly-121:29
danwentbtw, refresh if you didn't in last 30 mins :)21:29
ttxI like that21:29
danwentwe had a couple "just misses" in terms of features21:30
danwentbut i figured there was no need to try to cram for G-1, so we moved them to G-221:30
ttxthere are two ryu blueprints that are targeted to g2 but already completed...21:30
danwentthere's only one bug that really MUST be in G-1 that is not merged21:30
*** ryanpetrello has quit IRC21:30
ttxdansmith: shoulds I move them to g1 ?21:30
*** brich1 has joined #openstack-meeting21:30
ttxdanwent: ^21:30
danwentttx:  sure.. i think those where the one's I was pestering for an update on :)21:30
uvirtbotLaunchpad bug 1081259 in quantum "hasattr check for get_*_counts is invalid " [Critical,In progress]21:31
danwentthis one is a regression introduced in a previous fix, so we need to get this in.  just needs one more +2, so we should be in good shape21:31
ttxmoved both ryu things to g121:31
*** brich1 has left #openstack-meeting21:31
danwentyup, looks good21:31
ttxdanwent: for bugfixes you have until Thursday anyway21:31
*** ryanpetrello has joined #openstack-meeting21:32
danwentttx: yup, bug given the holidays, i'm trying to clear the deck21:32
ttxdanwent: so I can cut milestone-proposed tomorrow morning and we can backport that fix ?21:32
danwentyeah, if its not merged in by then, we can backport it21:32
danwentremember that you'll be contacting salv-orlando for the milestones, as I am connection-less :(21:32
*** andrewbogott is now known as andrewbogott_afk21:32
salv-orlandoyeah no thanksgiving for me...21:33
ttxfor the other two bugs, if they are not in at the end of today, they will be g2 ?21:33
danwentsalv-orlando: i've give up my thanksgiving for a wifi connection21:33
*** koolhead17 has quit IRC21:33
danwentttx: yes.  we're just targeting them for g1, as we'd like to backport them sooner rather than later21:33
danwent(backport to stable/folsom that is)21:33
danwentand people are targeting G-1 as a point for releasing 2012.1, I believe21:34
*** jcooley is now known as jcooley_afk21:34
danwent(though I just saw a flurry of emails on this, so perhaps that date was moved up?)21:34
ttxwell, if you want the fix in 2012.2.1 that wil help21:34
*** ryanpetr_ has quit IRC21:34
ttx2012.2.1 should be next week21:34
ttxAnything more on Quantum ?21:35
danwentttx: ok, great.  maybe markmc is just taking care of items that are already in in preparation for the official 2012.1 release next week21:35
ttxdanwent: yes21:35
ttx#topic Cinder status21:36
*** openstack changes topic to "Cinder status"21:36
ttxjgriffith: o/21:36
ttx#link https://launchpad.net/cinder/+milestone/grizzly-121:36
*** gabrielhurley has quit IRC21:36
*** markvoelker has quit IRC21:36
ttxso looks like you could use another day or two :)21:36
jgriffithI'm still hopeful for all of them by tomorrow21:36
jgriffithttx: :(21:36
*** gabrielhurley has joined #openstack-meeting21:36
ttxjgriffith: let's do it like for Keystone, one more day before I cut the g1 branch21:37
jgriffithttx: Thanks, that would be great21:37
ttxjgriffith: and we'll see how far we are tomorrow21:37
ttxdriver-cleanup: is there anything more to it than the two commits already merged ?21:37
jgriffithttx: yeah... some minor org changes (moving things under a drivers directory)21:38
jgriffithttx: If rnirmal can't get to it I'll finish it tonight or tomorrow morning21:38
ttxcinder-apiv2: this looks a bit far away... is there a point in trying to get it in g1 ? or defer to g2 ?21:38
jgriffithttx: I need to reword that BP and have it in phases21:38
ttxcouldn't really find code proposed for it21:38
jgriffithttx: The initial framework piece should be G1, the rest G2 and on21:38
ttxjgriffith: sounds good, just explode it in multiple blueprints21:39
jgriffithttx: Yep, there are 5 outstanding reviews for it already21:39
jgriffithttx: I'll clean up the BP this afternoon21:39
ttxsounds good. I'll talk to you tomorrow to check progress21:39
ttxeveryone ready to switch to Nova ?21:40
jgriffithttx: Looking forward to it :)21:40
jgriffithtomorrow that is...21:40
ttx#topic Nova status21:40
*** openstack changes topic to "Nova status"21:40
ttxvishy: hey21:40
ttx#link https://launchpad.net/nova/+milestone/grizzly-121:40
ttxso, let's see21:41
*** jcooley_afk is now known as jcooley21:41
ttxdo you want to play the "i forgot we cut on Tuesday" card to get another day ?21:41
ttxor it won't really help ?21:42
vishyi don't know that it will help21:42
vishyjust looking21:42
ttxlet's have a look at them21:42
ttxxenapi-volume-drivers: looks a bit far away ?21:42
ttxserver-count-for-nova-flavors: same ?21:42
ttxbetter-libvirt-network-volume-support: looks like it's almost there ?21:42
vishyi'm not sure if the volume driver patch is done21:43
vishylast current review got sent in21:43
ttxgeneral-bare-metal-provisioning-framework: looks like it's still at least one week away?21:43
ttxquota-instance-resource: same ?21:43
ttxhyper-v-config-drive-v2: unknown status, not in series goal... should I just un-milestone it ?21:43
*** mnewby has joined #openstack-meeting21:44
vishybaremetal is going to be another few days21:44
ttxnot sure any of those would get in given an extra day21:44
vishyquota-instance no code, don't know what happened so i delayed21:44
vishyi think the hyper-v config drive is in21:45
vishyt didn't get linked to the blueprint properly21:45
vishyooking for it21:45
*** ddemir has joined #openstack-meeting21:45
*** hub-cap has joined #openstack-meeting21:46
ttxvishy: I can clarify that off-meeting21:46
*** sarob has joined #openstack-meeting21:46
ttxvishy: should I cut tomorrow morning with what's in ? and defer the rest ? or wait until eod tomorrow ?21:47
vishytomorrow morning should be fine21:47
*** spiffxp has joined #openstack-meeting21:47
ttxvishy: ok, let me know if I should assume otherwise21:47
ttxOn the bug side, we have bug 107610921:47
uvirtbotLaunchpad bug 1076109 in nova "nova rest /v2/ call returns v1.1 documentation" [Medium,In progress] https://launchpad.net/bugs/107610921:47
ttxis that a milestone-blocking bug ? Or should I defer to g2 if not complete by eod ?21:48
vishyok it is in21:48
vishyno not a blocker imo21:48
ttxok thx21:48
ttxOn the grizzly general plan, I see that your quest for assignees wasn't very successful so far21:48
*** MarkAtwood has joined #openstack-meeting21:48
ttxStill planning to send a "take it or it will be H" email about those ?21:48
ttxAlternatively you could set them to Low priority to keep them as targets of opportunity21:48
vishyttx: i didn't get a chance to send out the email21:49
vishyi will do it today21:49
ttx#action vishy to send email about missing blueprint assignees21:49
vishyso the only unknown bp is the xenapi volume driver one21:49
*** olaph has left #openstack-meeting21:49
vishyi don't know if it is complete21:49
ttxdavidkranz raised a CI issue that seems to point to a Nova problem... any chance you could help him narrow it down ? Or someone else from Nova ?21:49
ttxwill try to contact mate_lakat on that bp status21:50
uvirtbotLaunchpad bug 1079687 in nova "Flaky failures of instances to reach BUILD and ACTIVE states" [Undecided,New]21:50
ttxbecause we don't have enough time to investigate it in-meeting21:50
*** cp16net is now known as cp16net|away21:51
davidkranzvishy: We also want to bring stress tests online which is made hard by https://bugs.launchpad.net/nova/+bug/107921021:51
uvirtbotLaunchpad bug 1079210 in nova "Successful full gate jobs show ERRORs and stacktraces" [Medium,Confirmed]21:51
ttxvishy: so in summary, I'll cut MP tomorrow morning from master, unless you tell me otherwise (IRC or email)21:51
davidkranzvishy: We can discuss this offline.21:51
*** andrewbogott_afk is now known as andrewbogott21:51
ttxvishy/others: anything more on Nova ?21:51
ttx#action davidkranz and vishy to look into bug 107921021:52
uvirtbotLaunchpad bug 1079210 in nova "Successful full gate jobs show ERRORs and stacktraces" [Medium,Confirmed] https://launchpad.net/bugs/107921021:52
ttx#topic Horizon status21:52
*** openstack changes topic to "Horizon status"21:52
ttxgabrielhurley: hi!21:52
ttx#link https://launchpad.net/horizon/+milestone/grizzly-121:52
gabrielhurleyBlueprints are in the process of merging... I kicked my other core reviewers to go get everything in progress reviewed and hopefully merged (there were 7 that needed a second +2). Most of them will be taken care of shortly. I have three bugs I need to code up today, but the only blocker is the one about the files missing from the tarball. I'll make sure things are ready to go within 24 hours.21:52
ttxok, so I'll wait until EOD tomorrow before cutting MP21:53
ttxnote that we can still backport bugfixes between then and "Thursday"21:54
gabrielhurleynoted, but hopefully not needed21:54
ttxwe'll talk tomorrow, but is there any bug in that g1 list that is a milestone blocker ?21:54
gabrielhurleyonly the tarball one21:55
gabrielhurleyand I'll deal with that right now21:55
ttxi.e. which I should not just defer to g2 if incomplete by tomorrow eod ?21:55
*** saurabhs has joined #openstack-meeting21:55
ttxAnything more on Horizon ?21:55
gabrielhurleyone thing21:55
gabrielhurleyI'll be starting a regular Horizon project IRC meeting like the rest of the projects. Announcement of time will be forthcoming on the ML.21:55
ttxcool! more meetings.21:56
ttxwe should soon need an #openstack-meetings2 room21:56
ttx#topic Incubated projects21:56
*** openstack changes topic to "Incubated projects"21:56
ttxAnyone to talk Ceilometer ?21:56
*** jdbarry has joined #openstack-meeting21:56
eglynn_nijaba: there?21:57
ttxstevebake: still around ?21:57
ttxlet's do Heat first21:57
*** SlickNik has joined #openstack-meeting21:57
ttxIncomplete action item: heat crew to align Launchpad teams with openstack model21:57
ttxLet me know if you need help with that, otherwise I'll just postpone that action to next week21:57
nijabattx o/21:58
stevebakeNothing has really changed since last week. We've changed our meeting time and haven't met at the new time yet21:58
stevebakettx: we'll figure out what is outstanding on that and get back to you21:58
ttx#action heat crew to align Launchpad teams with openstack model21:58
ttxThe next step after that would be to move your code repository under openstack/heat21:58
ttxyou'll have to sync with CI on that21:58
asalkeldk, who do we need to chat to?21:59
stevebakeyep, we can coordinate for the gerrit downtime21:59
ttxasalkeld: jeblair21:59
ttxok, one minute for ceilometer now :)21:59
ttxIncomplete action item: ceilometer crew to pimp up their grizzly roadmap21:59
eglynn_#link https://launchpad.net/ceilometer/+milestone/grizzly-221:59
*** kmansel_ has joined #openstack-meeting21:59
nijabaI just finished pimping that up22:00
eglynn_nijaba has done a good job of getting us with the blueprint program ;)22:00
ttxThe ceilometer-tarball job looks sane now. You said you would skip g1 milestone ?22:00
ttxOK, then I should bump your next milestone to g2 soon22:00
nijabawe will join at g222:00
ttx#action ttx to bump ceilometer next milestone to g222:00
ttxI'll review your grizzly roadmap and discuss it at next meeting22:01
ttxwe need to clear the room now22:01
*** jdorothy has joined #openstack-meeting22:01
ttxnijaba, stevebake: any question ?22:01
nijabathanks ttx, none here22:01
ttxjust hit me on IRC any time22:01
stevebakeno, all good22:01
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:01
asalkeldsay ttx we need <project>-core and <project>-drivers?22:01
openstackMeeting ended Tue Nov 20 22:01:38 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2012/project.2012-11-20-21.03.html22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2012/project.2012-11-20-21.03.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2012/project.2012-11-20-21.03.log.html22:01
ttxasalkeld: let's continue on #openstack-dev22:02
vipul#startmeeting Reddwarf22:03
openstackMeeting started Tue Nov 20 22:03:22 2012 UTC.  The chair is vipul. Information about MeetBot at http://wiki.debian.org/MeetBot.22:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:03
openstackThe meeting name has been set to 'reddwarf'22:03
*** yidclare has joined #openstack-meeting22:03
*** jcru has joined #openstack-meeting22:03
vipulDon't have an official agenda link as of yet22:03
vipullooks like there may be some stuff here22:04
vipul#link http://wiki.openstack.org/Meetings/RedDwarfMeeting22:04
*** cp16net|away is now known as cp16net22:04
*** datsun180b has joined #openstack-meeting22:04
vipul#topic Action Items22:05
*** openstack changes topic to "Action Items"22:05
vipulSo going off the agenda, let's review the action items from previous week22:05
hub-capvipul: i added that agenda22:05
SlickNiksounds good.22:05
hub-capwant to do action items by person or the list above?22:05
vipulhub-cap: suer22:06
vipulgrapex: any update on the launchpad site?22:06
hub-capive done all the necessaries for the 3 launchpad sites22:06
hub-capreddwarf, python-reddwarfclient and reddwarf-integration22:06
SlickNikSounds good, hub-cap.22:07
SlickNikI've already started using the reddwarf-integration one.22:07
spiffxphub-cap: any reason to use you specifically for driver instead of reddwarf-drivers?22:07
hub-caplink plz22:07
*** markmc is now known as mcaway22:07
hub-capthere is likely not  agood reason22:07
*** mcaway has left #openstack-meeting22:07
hub-capjust prolly forgot to change22:08
spiffxpI'll do it now then22:08
hub-capsry didnt see u were changing :P22:08
*** GrapeX2 has joined #openstack-meeting22:08
spiffxpalso, the futurestack designation for reddwarf, does that still make sense?  if so, does reddwarfclient need to be added?22:08
SlickNik#info reddwarf-integration launchpad site: https://launchpad.net/reddwarf-integration22:08
hub-capspiffxp: im not sure what the futurestack thing is... jaypipes added it back in the day22:09
*** heckj has quit IRC22:09
hub-capmaybe he can chime in :D22:09
*** jpich has left #openstack-meeting22:09
vipulspiffxp - i don't think it matters that much, supposedly as long as it's a subproject of openstack then everything is cool22:09
cp16nethub-cap: looks like the pre-incubating project area22:09
spiffxpseems like ceilometer and heat aren't using it?22:09
hub-capya its likely just old22:09
SlickNik#info Reddwarf client binding launchpad site: https://launchpad.net/python-reddwarfclient22:09
hub-capthat page was added a LONG time ago22:09
hub-capthx SlickNik for those infoz22:10
jaypipeshub-cap: long time ago...22:10
vipulthe next item was for grapex to own CI - assume this means getting the integration tests in?22:10
spiffxpok I'm going to remove that if no objections22:10
hub-capif yall see any issues w/ them hit me up22:10
jaypipesit's dead, AFAIK22:10
hub-capjaypipes: lol ya, do u know is tha tfuture....ok :)22:10
hub-caplets remove it then22:10
*** jaypipes has quit IRC22:10
vipulor should i refer to him as GrapeX222:11
SlickNik@hub-cap: np22:11
hub-capgrapex, GrapeX2, GrapeX3, GrapeX422:11
hub-capdepends on how many tiems hes logged in to irc22:12
cp16netyeah hes away right now i think22:12
hub-capvipul: lets chat about that in a bit22:12
hub-capits one of the agenda items22:12
hub-capits big enough to warrant further discussion than a action item22:12
vipulYep, that's next, if we're done talking about the launchpad site22:13
hub-capthats all the action items?22:13
vipuli'm going by person22:13
hub-capthat has the next item as CI22:13
hub-caplets skip it in the ActionItems portion and talk about it after all the action items have been done22:14
*** sudorandom has left #openstack-meeting22:14
*** hemna has quit IRC22:14
*** kmansel_ has quit IRC22:14
*** cdub has quit IRC22:14
*** zul has quit IRC22:14
*** swifterdarrell has quit IRC22:14
cp16netsounds good22:14
*** cdub has joined #openstack-meeting22:14
SlickNiksounds good, let's move on to the next item.22:14
*** zul has joined #openstack-meeting22:14
*** martine_ has joined #openstack-meeting22:15
*** Vek has left #openstack-meeting22:15
hub-capyar. lets wait for GrapeXY22:15
hub-capwhre Y is a number > 022:15
*** joe5081 has joined #openstack-meeting22:15
vipulk, so let's move on to the next action item22:15
*** hemna has joined #openstack-meeting22:15
vipulhubcap: devstack integration status22:15
hub-capthat got passed to jcooley22:15
hub-capsee item #222:15
*** juice__ has joined #openstack-meeting22:16
hub-cap3 is done22:16
*** swifterdarrell has joined #openstack-meeting22:16
*** rnirmal has joined #openstack-meeting22:16
hub-cap4 is done, and i havent been online to talk to lifeless or devananda about the image stuff, but its on my list22:16
hub-cap#action hub_cap talk to lifeless or devananda about the image creation22:16
lifelesshub-cap: o/22:16
spiffxpjcooley was offline a good chunk of last week as well22:16
hub-caplifeless: im on paternity leave still :)22:17
vipulugh i should use the list on top22:17
hub-capvipul: likely thats the best way22:17
SlickNikYeah, I think 2 is still on jcooley's plate.22:17
*** martine has quit IRC22:17
jcooleyremind me of #2 and I'll give an update.22:18
hub-capto discuss devstack integration22:18
devanandaoh, hai22:18
*** metral_ has joined #openstack-meeting22:18
hub-capas in configuration of reddwarf via devstack jcooley22:18
hub-caphai devananda22:18
jcooleyyes.  discussed with mordred, need to discuss with devstack folks.  still outstanding.22:18
SlickNikhey devananda.22:18
*** kmansel has joined #openstack-meeting22:18
hub-cap#action jcooley to discuss reddwarf devstack integration w/ devstack folks22:19
SlickNikSweet, thanks jcooley!22:19
vipulOk, we're on 5 I believe.. Reddwarf-core completed22:19
vipul6 is related.. so done22:19
hub-capwe did a great job w #722:20
vipul7 - Make sure reviews have blueprints or bugs22:20
*** grapen has joined #openstack-meeting22:20
hub-capgoodjob to everyone on that one22:20
vipulyep - we're getting better22:20
spiffxpyeah now that I've tripped over that twice I'm watching for it22:20
SlickNikNice. Thx.22:20
*** GrapeX2 has quit IRC22:20
vipul8 - grapex to own CI and make sure it gets accomplished22:20
cp16netoh yeah i mentioned that earlier :-P22:20
hub-capgrapex is having connection issues22:20
*** annegentle__ has quit IRC22:20
cp16neti didnt realize until today we had these meetings...22:20
vipulok we'll wait for his response offline22:20
hub-capso hes doing his best to connect up22:20
*** jgriffith has quit IRC22:21
grapenSorry guys22:21
hub-capis that grapex? grapen?22:21
SlickNikAh, welcome! Np.22:21
grapenWe're traveling back from San Antonio today. I've been using Nirmal's cell phone with a pretty decent connection, but we got weird issues trying to join freenode just now.22:21
hub-capOh ure on da bus22:22
hub-caprnirmal: thx for allowing grapeKERJ#H$#KXNK#J!@@#$%%%1223456 to use your cell22:22
grapenWhere "n" is the number of times I tried to connect.22:22
hub-capso youre up, CI status22:22
*** radez is now known as radez_g0n322:23
grapenBy the way, this is the real GrapeX and not a hacker. Now that I've assured you...22:23
grapenhub-cap: Well we've got a huge chunk of tests running in CI.22:23
*** jgriffith has joined #openstack-meeting22:23
grapenWe still need to run tests in real mode somehow.22:23
hub-capawesome. so they are running as part of the jenkins gate job now?22:23
grapenYes, because its tox it naturally plugs into the Jenkins gate stuff.22:24
*** stevebake has quit IRC22:24
*** metral has quit IRC22:24
*** jcru has quit IRC22:24
*** metral_ is now known as metral22:24
grapenAs part of this, the client is now in PyPi.22:24
vipulhub-cap grapen - they are running currently as unit tests would22:24
hub-capawesome. so some work accomplished, def some more to go22:24
grapenmordred and I co-own it. Apparently all the uploads to PyPi happen manually.22:24
esp1anyone have a link to the jenkins box handy?22:24
*** martine_ has quit IRC22:24
grapenHP has done a lot of work getting the public RDLI environment to run.22:24
vipul#link jenkins.openstack.org22:25
spiffxp#link https://jenkins.openstack.org/view/Stackforge/job/gate-python-reddwarfclient-python26/22:25
hub-capesp1: its in all the reviews in gerrit as well22:25
esp1thx :)22:25
hub-capok we are for sure falling behind :) grapen anythign more to add?22:25
esp1hmm. pretty.22:25
*** dolphm has quit IRC22:26
vipul9 - hub_cap make sure the client launchpad page is up to date w/ the series like the reddwarf one22:26
esp1well except the thunder clouds22:26
hub-capvipul: check22:26
grapenThe next thing we've got to do is find some way to get CI for the RDLI tests running in real mode on a Jenkins box that can plug into Gerrit.22:26
hub-capand we need to figure out the image creation for that too22:26
SlickNikYeah, a few of us here at HP were looking at running the tests in real mode. Will take that offline with grapex…22:26
spiffxphub-cap vipul fwiw I just went through and configured support and answers on that page to use launchpad too22:26
vipulgrapen: I think that's what the whole devstack integration work is going to turn into22:26
hub-capok i guess that bleeds us in to the next section, and we can just summarize it then eh?22:26
hub-capspiffxp: sweet thx22:26
vipulit will involve adding a redstack-gate job and run integration tests in real mode22:27
spiffxpk, done w/ action items?22:27
vipulok anything more to add?22:27
hub-capnot here22:28
vipul#topic CI / Image Updates22:28
*** openstack changes topic to "CI / Image Updates"22:28
vipulI can speak a bit to the image portion of this22:28
rnirmalhub-cap: Nope, sorry. Getting those tests to run in the main repo with Tox took forever.22:28
vipulWe're currently working on building out a precise image with percona bits...22:28
hub-capps we also have a script we might be able to adapt that sets up a bunch of the image stuff. i can find out internally22:29
grapenhub-cap: I agree with this rnirmal character.22:29
hub-capvipul: are u using the same process that devananda is?22:29
vipulwe're going to fix the image buildling code in redstack as the first step - and eventually make it so that you can build hp/rax images22:29
hub-capok great22:29
vipulhub-cap - not yet.. this is the interim step to getting things working on precise22:29
hub-capthat was a bit of a hack job :P22:29
hub-capvipul: what are u using then? i suggest debootstrap!22:30
vipulwe're also going to look at Devananda and tripleo's image builders and hook into those22:30
hub-capok cool22:30
juice__hub-cap we are in the process of creating something22:30
*** stevebake has joined #openstack-meeting22:30
grapenvipul: Quick question, do we want to stick with Ubuntu 12.4 or go to 12.10?22:30
hub-capjuice__: cool. when i get back from paternity leave id like to help out22:30
juice__we reviewed the image creation currently in the redstack scripts22:31
hub-capgrapen vipul we shoudl stick to what nova uses dont u think? it seems funky to have diff version requirements for things that _could_ be deployed in the same env22:31
vipulgrapen: We are targetting 12.04 for now, we might want to consider jumping ahead22:31
*** mtreinish has quit IRC22:31
spiffxp12.04 please22:31
hub-capwaht does devstack target?22:31
spiffxpwe'd like to stick with LTS unless there's a strong reason not to22:31
vipul12.04 hub-cap22:32
esp1I think you want a LTS which is 12.0422:32
hub-capcuz if we start usign diff versions / etc tis gonna be a nightmare22:32
hub-cap12.04 it is22:32
*** gabrielhurley has quit IRC22:32
SlickNikdevstack targets 12.04, iirc since it is LTS22:32
hub-capgood, lets target that too, i think we are mostly in agreement eh?22:32
vipul#link https://github.com/tripleo/baremetal-initrd-builder22:32
grapenSounds good.22:32
hub-capgrapen: did u have any reason for 12.10?22:32
vipulthis is the tripleo image builder that we want to target eventually22:32
*** ryanpetrello has quit IRC22:33
juice__hub-cap can I reach out to you with a couple questions on the current image building process?22:33
jcooleyalso, i understand that 12.10 has the correct openstack clients22:33
grapenhub-cap: No, I thought devstack targeted the latest one. My mistake.22:33
hub-capjuice__: plz do, but grapen can help as well if im not very useful (ill be back officially monday)22:34
hub-capbut i respond to emails for sure22:34
*** ryanpetrello has joined #openstack-meeting22:34
hub-capid say email us both22:34
yidclare#info using Ubuntu 12.04 because it is LTS22:34
*** dendrobates has quit IRC22:34
juice__thanks hub-cap22:34
vipulOk moving on..22:35
hub-cap#info need to work on image building / realmode tests22:35
vipulany CI updates?22:35
hub-capi dont think we info'd much for that :P22:35
hub-capoh i thought u meant the next topic totally22:35
vipulthe second part of this topic22:35
*** samkottler|afk is now known as samkottler22:36
hub-capanyone want to own this for the next wk? i think we need to make progress w/ ci22:36
hub-capgrapen wink wink22:36
*** ywu_ has joined #openstack-meeting22:36
vipulOne thing i'll point out here is we are trying to get the redstack-gate stuff sorted out - an additional gate on Jenkins that would do real-mode tests22:36
spiffxphub-cap: I will try to help w/ devstack integration but I don't think I can own22:36
grapenI'm setting up a VM for the rdli stuff, but getting the fake mode stuff to work in tox took forever.22:36
vipulour guys can work with grapen on this22:37
grapenHopefully I'll have some progress made tomorrow.22:37
*** dendrobates has joined #openstack-meeting22:37
spiffxp#link https://github.com/openstack-ci/devstack-gate/blob/master/README.md22:37
SlickNikI can work with grapen on this…22:37
spiffxpooo I one other thing in CI actually22:37
hub-capvipul: id like someone from each group to work together22:37
hub-capso SlickNik or spiffxp?22:37
spiffxpI would say SlickNik, I can pester as appropriate22:38
vipul#action SlickNik and grapen to work on redstack-gate22:38
SlickNikokay, sounds good spiffxp.22:38
spiffxpI knew enough to get reddwarf-integration into stackforge, but I don't think I have the bandwidth to own22:38
hub-cap:D cool22:38
spiffxphub-cap: mind adding a "this is deprecated" commit to https://github.com/hub-cap/reddwarf_lite-integration?22:38
spiffxpw/ pointer to https://github.com/stackforge/reddwarf-integration22:39
hub-capgonan do it22:39
hub-capif u check out the meeting notes22:39
hub-capMod rax/reddwarf && hub-cap/reddwarf_lite to point to stackforge22:39
hub-capis on it :)22:39
spiffxpahh k22:39
vipulok let's move on, got a lot to cover22:39
vipul#topic blueprinting22:39
*** openstack changes topic to "blueprinting"22:39
hub-capand very little time!22:39
grapenSo when we say redstack-gate, I think the first job should be to just get any of us running the tests in a VM. After we do that, then lets look at incorporating it into Openstack CI.22:39
hub-caplol we moved on grapen!!!!!! youre too late for input!!22:40
vipulgrapen: yep, that's the idea, it would be part of the core CI process22:40
vipulhub-cap what did you want to discuss aobut blueprinting22:40
hub-cap2 thinkgs22:40
SlickNikgrapen, let's discuss in #reddwarf after the meeting, when you have some time.22:40
grapenvipul: Agreed, just wanted to set everyone's expectations.22:40
grapenSlickNik: Ok22:40
hub-cap1) should we shoudl be using our own space or openstack's space? <-- gerrit reviews go to openstack, not reddwarf22:40
hub-capif u look @ grapens tox test commit, it cant find the blueprint22:41
cp16netyeah i noticed that for robert's commit earlier22:41
hub-capgotta take dog out brb22:41
cp16neti was wondering if there is some configuration we could do for gerrit that would make it point to reddwarf22:41
vipuli wonder if that's just an issue with gerrit config22:41
grapenI wonder if thats because its a StackForge process.22:41
vipulwe all wondered the same thing22:42
spiffxpmight be, I say we action item someone to followup w/ #openstack-infra22:42
cp16neti'll look into seeing if thats possible22:42
cp16neti'll compare with some of the other proejcts like glance or swift22:42
vipul#action cp16net to look into why blueprints in Reddwaf aren't closed with gerrit reviews22:42
vipulanything else to add to this?22:43
vipul#topic Stackforge22:43
*** openstack changes topic to "Stackforge"22:43
SlickNik#action hub-cap to Mod rax/reddwarf && hub-cap/reddwarf_lite to point to stackforge22:44
hub-cap#action hub_cap to modify all rax resources to point to stackforge22:44
SlickNikoops, thought you were still away...22:44
SlickNikwb. :)22:44
vipulrelated to Stackforge move, there are a couple of reviews in the pipe that resolve some of the naming issues with RDL and D22:44
spiffxpI've got two outstanding reviews to s/reddwarf_lite/reddwarf as well22:44
hub-capya lets remove the lite thing22:45
hub-capall over22:45
hub-capi like reddwarf and reddwarf-integration22:45
spiffxpk, just wanted to double-check that wouldn't mess anything up on your end22:45
vipulalong these lines, can the hub-cap repos be modified to be read-only?22:45
*** jcooley is now known as jcooley_afk22:45
hub-capvipul: yup and as per the action above im going to point them to stackforge22:45
hub-cap#action hub-cap also make them readonly22:45
*** redthrux has quit IRC22:46
vipulOther resources may already point to stackforge22:46
hub-capi tried to mod everything i saw, but there may be others in regard to launchpad22:46
hub-capfeel free to update anything i missed22:46
*** markmcclain has quit IRC22:47
vipul#action Look over all references (including launchpad) to reddwarf and ensure they point to stackforge22:47
hub-capwho owns that, u?22:47
vipul#action vipul owns updating references22:47
*** markmcclain has joined #openstack-meeting22:48
vipulk.. next topic22:48
*** markmcclain has quit IRC22:48
hub-cap#action hub_cap to talk to mordred about why gerrit wont search reddwarf blueprint space22:48
hub-capok we can move on22:48
cp16nethub-cap: i made comments to make the reddwarf-intergration PRs to gerrit instead22:48
hub-capwanted to get that in22:48
vipulcp16net had a similar action22:48
hub-capcp16net: cool from the public repo? <322:48
cp16nethub-cap: yeah i have something simiar22:48
vipul#topic os_admin vs root22:49
*** openstack changes topic to "os_admin vs root"22:49
hub-capvs is such a harsh word ;)22:49
hub-capso i had a question for yall22:49
vipul#info background: os_admin user does not exist in public version of RD instances22:49
hub-capdoes your agent need to access the database?22:49
SlickNik#link https://bugs.launchpad.net/reddwarf/+bug/107898122:49
uvirtbotLaunchpad bug 1078981 in reddwarf/grizzly "The mysql user that the guest agent uses needs to be different for HP and RAX" [Undecided,New]22:49
hub-capnice :) i like that22:50
vipulhub-cap: our implementation will not require login, n o22:50
*** littleidea has joined #openstack-meeting22:50
hub-capok so maybe we should widen the discussion to _do we need a default login user_ ?22:50
hub-capbut im not sure thats good for the meeting22:50
hub-capmaybe a ML thing22:51
vipulyes - sounds like a larger discussion is needed22:51
hub-caprax wants one for the users/dbs/root portions but hp doesnt need. i think we need to figure it out22:51
hub-capmailing list cp16net22:51
cp16netoh yeah22:51
hub-cap#action hub-cap start discussion about the need for the extra actions that require login in reddwarf22:51
vipul#info rax wants one for the users/dbs/root portions but hp doesnt need22:52
hub-capi miiiight not get on that for another wk22:52
hub-capbut id like to work it out22:52
hub-capid like a nicer way to turn on/off those things that we dont necessarily both need22:52
*** ryanpetrello has quit IRC22:52
cp16netyeah i agree it could be done multiple ways22:52
vipulhub-cap, yep, agreed, although for the public version, we may need to support both ways22:52
hub-capya so that brings us to22:52
vipuland when we deploy, we'd toggle a flag22:52
hub-capshoudl we default the public version to root?22:53
cp16netyeah its an option22:53
hub-capand let our stuff flag os_admin22:53
SlickNikOne idea that was floating around was sone sort of conf toggle.22:53
hub-capgrapen, rnirmal cp16net is there anything that would blow up if we default the user to root, and flag it to os_admin?22:53
hub-capi tihnk it might require a change in sneaky pete but i dont think thats a deal breaker or anything22:54
cp16netnot that i can think of off hand right now.22:54
hub-capspecially since yall dont use it :D22:54
cp16netyeah i am sure the same change will need to happen in sneaky22:54
grapenhub-cap: The only thing is when we reset root we need to make sure the agent can use the updated password, if its also logging in as root.22:54
grapenI think that's it, but I feel like I'm forgetting some important edge case.22:54
hub-capgrapen, we will still use os_admin, it woudl be a flag that we set in the guest conf22:55
cp16netgrapen: yeah good thing for tests :)22:55
hub-capso sneaky woudl always still use os_admin for our needs22:55
hub-capor whatever we want to use22:55
vipul#info os_admin can be a config so it works for rax/sneaky pete22:55
*** zoumpis has quit IRC22:55
hub-capit seems that we shooudl do this anyway, cuz a 3rd company might not want to use either of those22:55
vipul#action make user configurable in guest agent22:56
hub-capdoes anyone in particular want to own this?22:56
vipulI can drive it on our end...22:56
hub-cap#action grapen work w/ vipul to update sneaky once its been pushed22:57
hub-capkk, moving on then?22:57
juice__I can look at this as part of building the image yes?22:57
juice__must type faster :)22:57
juice__I will work with vipul on it22:57
vipuljuice__ the config would likely be derived at runtime22:57
vipul#topic bugchat22:58
*** openstack changes topic to "bugchat"22:58
juice__ok so an orthogonal issue22:58
juice__done moving on22:58
hub-cap#info ive added milestones and series to all the bugs22:58
hub-capif i missed anything plz notify me or update it :)22:58
vipulwho owns attaching milestones? reddwarf-core?22:58
hub-capive tried to put things that are smaller in g2 and that seem bigger in g322:58
hub-capvipul: not sure i mgith have set myself as the triage, since nova has a single person doing as well22:59
hub-capi _thnk_ ttx only does that, but posssibly a whole team does?22:59
vipuldo we need to change the way we've been doiing bugs so far?22:59
cp16nethub-cap: looks like nova bug team is the manager23:00
cp16netor supervisor of the bugs23:00
hub-caphmmm we need to have a bug team then it seems23:00
spiffxpI say we have reddwarf-core triage informally23:00
cp16netyeah maybe so23:00
hub-capmakes sense23:00
spiffxpand take a formal policy up offline or next meeting23:00
hub-capwe can mod to do the bug team in the future23:00
vipul#info reddwarf-core to triage bugs23:00
hub-capi dont mind triaging as well, so if u dont get around to it, ill try to spend a hr or 2 each wk doing23:00
cp16netright now it would be ok to just have the reddwarf-core do it23:01
vipul#topic open-discussion23:01
*** openstack changes topic to "open-discussion"23:01
*** ijw11 has joined #openstack-meeting23:01
hub-capim chiangin them to reddwarf-core now23:01
vipulrunning out of time... any remaining out of band items?23:01
yidclareis there a meeting after us?23:01
vipulnot sure..23:01
* cp16net shrugs23:01
hub-capi dont think there is a meeting after23:01
*** ijw1 has quit IRC23:01
hub-capbut i dont really have any open items to add....23:01
spiffxphub-cap, grapen: waht's the best way to ping openstack-core when we want a RAX person to look at a review?23:02
hub-capi just add that _in case_ we mised something23:02
hub-capopenstack-core? id say ping us in #reddwarf23:02
spiffxpI've started add redstack-core to open reviews, but I'm not sure if that's too noisy23:02
hub-capspiffxp: im fine w/ that23:02
grapenspiffxp: I'm not worried about the noise.23:02
vipulif there is no meeting.. i'll give a quick status update on some things that were not part of action items23:02
hub-capi did notice a review went in today? w/ vipul spiffxp review23:02
vipulWork being done to get redstack on precise23:03
vipul#link https://etherpad.openstack.org/reddstack-precise-12.0423:03
hub-capok cool vipul23:03
cp16netspiffxp: sounds good23:03
spiffxphub-cap: yah we missed that one I think, I think consensus in #openstack-infra is it's tough to customize that policy too much23:03
vipulhp cloud precise images are a bit different from what rax may have -- outline some of teh tweaks we've had to make23:03
hub-capbut lets still get some rax eyes on those since they affect our stuff too23:04
spiffxp#link https://review.openstack.org/#/c/16552/23:04
hub-capmabye i was wrong tho23:04
*** jcooley_afk is now known as jcooley23:04
vipulWe're also looking at unit testing holistically23:04
vipul#info HP going to be adding tests for python-reddwarfclient and guestagent23:05
hub-capgood we abandoned unit testing very quickly but id love to have them back in23:05
vipulpython-reddwarfclient doesn't seem to have any, so we're working on that23:05
vipuland the guestagent probably is not well tested either23:06
spiffxphub-cap: here's the review that made it in w/o RAX eyes fwiw, if you want someone to look at it https://review.openstack.org/#/c/16551/23:06
grapenvipul: I'm always for more tests, but we may want to check the code coverage for python-reddwarfclient from the current tox tests in reddwarf23:06
hub-caphttps://review.openstack.org/#/c/16573/ this one was reviewed by one of our guys but not one of our core23:06
grapenvipul: I omitted that directory in the tox.ini file, but you can take that omission out23:06
hub-capid prefer them to be core23:06
hub-capya spiffxp thats the one i saw today via email23:06
grapenvipul: I noticed a lot of stuff in the client wasn't being hit, which kind of shocked me. We may have cruft we should just cut out.23:06
hub-capthings like https://review.openstack.org/#/c/16573/ can change our api w/o notice23:06
vipulgrapen: i'd like some tests to live in its own repo, so we can gate the python-reddwarfclient patches as well23:07
cp16nethub-cap: i agree seemed to be merged before i looked over it all23:07
hub-capcp16net:  it was :)23:08
hub-caplooks like i was wrong23:08
spiffxphub-cap: roger23:08
hub-capive been informed it was by my team23:08
grapenhub-cap: 16573 was by one of ours. :)23:08
hub-capbut i havent met the new guy yet!23:08
cp16netyes it was23:08
*** littleidea has quit IRC23:08
grapenHe ran it in real mode first, so we should be good.23:08
cp16netyeah i walked him through submitting it to gerrit but it went through fast... :-P23:09
hub-capgrapen: i just saw api changes so i got freaked out23:09
cp16netto mgmt23:09
hub-capif it was something that we did then im not worried about it affecting our api, cuz we needed it done. and thats why i want the "other" team to look it over. like hp says its ok for them23:09
jcooleyre api changes -- hence the reason we need to get the api tests back online :)23:09
*** fnaval has quit IRC23:09
hub-capjcooley: +1billion23:10
spiffxpone other testing q: looks like a bunch of tests from reddwarf-integration are now (back?) in reddwarf, do we need to be updating them in both places, or is there some overlap that can be removed from reddwarf-integration?23:10
cp16netyeah !!!!23:10
hub-capwe also need to come up w/ some api docs :) (i know rnirmal has a old crufty bluerpint about them)23:10
hub-capspiffxp: ill let grapen speak to that23:10
*** littleidea has joined #openstack-meeting23:10
spiffxphub-cap: looks like reddwarf-integration has a maven project for docs?  or maybe it's out of date...23:11
grapenspiffxp: We're going to remove them from RDLI, while still running them in the VM.23:11
spiffxpk, still digesting the RD commit so I wasn't yet sure what it means for RDI as a devstack gate etc.23:11
vipulgrapen: I think it may be good to identify tests that are pure 'integration' tests and maybe leave then in RDI - these will be what get added to Tempest down the road23:12
cp16netspiffxp: yeah there is a maven pom in there for docs23:12
grapenvipul: Yes. There may be some duplication for awhile, but ultimately we'll separate them out.23:12
hub-capvipul: +123:12
spiffxpI get the sense that until we sort it out, if a test changes in one place, it needs to change in the other as well23:13
hub-capthat does not sound fun23:13
hub-capcan we attempt to sort it out sooner than later?23:13
grapenThat's my next commit. But I'd like to get the redstack VM set up first.23:14
vipuli think the key dependency is the Devstack integration, if that work is completed sooner, then we can start looking at tempest23:14
hub-capokey, ETA?23:14
grapenhub-cap: Sometime next week.23:15
SlickNikClarification: do we have a similar issue for tests between rd and python-rdclient?23:15
*** etoews has quit IRC23:15
vipuli think teh tests in python-rd client should only be unit tests, so i don't think those would be ever considered to move out to tempest, if that's what your asking23:16
grapenSo the RDI tests use python-rdclient, and as a result python-rdclient should work.23:16
hub-capvipul: +1 to unit tests for rdcli23:17
grapenrdclient lacks coverage on the CLI though. That's a big pain.23:17
SlickNikWhat's tempest?23:17
vipultempest is the openstack integration test suite - run against live destack23:17
SlickNikokay, gotcha.23:17
vipulok anything else to discuss?23:18
SlickNikI was asking if there are tests that test rd-client in Tempest that we want to move to the rd-client repo, because we might want to gate on them.23:18
spiffxptempest doesn't as yet do anything non-core-openstack to my knowledge?23:19
vipulSlickNik: I think the tests in RD only 'use' the client, so probably not sufficient for gating rdclient repo23:19
SlickNikokay, then that shouldn't be an issue; looks like we need to still write all the new rdclient tests.23:20
vipulannashen and steveleon are looking at adding some tests separately into that repo to act as gates23:20
hub-capvipul: im done w/ discussion good sir23:20
SlickNikcool, thanks23:20
*** thingee has quit IRC23:20
vipulcool, thanks everyone - ran _way_ over time23:20
spiffxpdone here too23:20
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"23:20
openstackMeeting ended Tue Nov 20 23:20:53 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:20
openstackMinutes:        http://eavesdrop.openstack.org/meetings/reddwarf/2012/reddwarf.2012-11-20-22.03.html23:20
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/reddwarf/2012/reddwarf.2012-11-20-22.03.txt23:20
openstackLog:            http://eavesdrop.openstack.org/meetings/reddwarf/2012/reddwarf.2012-11-20-22.03.log.html23:20
*** esp1 has left #openstack-meeting23:21
*** jdorothy has left #openstack-meeting23:21
*** SlickNik has left #openstack-meeting23:21
*** spiffxp has left #openstack-meeting23:21
*** yidclare has left #openstack-meeting23:21
*** ddemir has left #openstack-meeting23:21
*** annashen has left #openstack-meeting23:21
*** joe5081 has quit IRC23:30
*** arbrandes has quit IRC23:31
*** Gordonz has quit IRC23:35
*** kmansel has quit IRC23:37
*** grapen has left #openstack-meeting23:38
*** rnirmal has quit IRC23:38
*** AlanClark has quit IRC23:38
*** datsun180b has quit IRC23:39
*** samkottler is now known as samkottler|afk23:39
*** fnaval has joined #openstack-meeting23:39
*** fnaval has joined #openstack-meeting23:40
*** jcooley is now known as jcooley_afk23:44
*** jcooley_afk is now known as jcooley23:44
*** mattray has quit IRC23:45
*** henrynash has quit IRC23:46
*** andrewbogott is now known as andrewbogott_afk23:47
*** eglynn__ has joined #openstack-meeting23:48
*** Mandell has quit IRC23:48
*** stevebake has quit IRC23:49
*** andrewbogott_afk is now known as andrewbogott23:49
*** MarkAtwood has quit IRC23:49
*** annashen has joined #openstack-meeting23:50
*** annashen has left #openstack-meeting23:50
*** MarkAtwood has joined #openstack-meeting23:50
*** Mandell has joined #openstack-meeting23:50
*** eglynn_ has quit IRC23:50
*** annashen has joined #openstack-meeting23:50
*** hub-cap has quit IRC23:51
*** stevebake has joined #openstack-meeting23:51
*** tr3buchet2 has joined #openstack-meeting23:57

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