Tuesday, 2013-02-12

*** maurosr has quit IRC00:01
*** otherwiseguy has joined #openstack-meeting00:02
*** markmcclain has quit IRC00:02
*** maurosr has joined #openstack-meeting00:02
*** metral has joined #openstack-meeting00:03
*** danwent has joined #openstack-meeting00:03
*** lbragstad has quit IRC00:04
*** markmcclain has joined #openstack-meeting00:04
*** alexpilotti has quit IRC00:06
*** adjohn_ has joined #openstack-meeting00:09
*** adjohn has quit IRC00:09
*** eharney has quit IRC00:10
*** sarob has quit IRC00:10
*** sacharya has joined #openstack-meeting00:20
*** rnirmal has quit IRC00:21
*** markwash has quit IRC00:25
*** mattray has quit IRC00:27
*** jog0 has joined #openstack-meeting00:28
*** alexpilotti has joined #openstack-meeting00:28
*** lukeh has quit IRC00:30
*** mrodden has quit IRC00:31
*** Nachi has joined #openstack-meeting00:33
*** nati_ueno has quit IRC00:34
*** ewindisch has joined #openstack-meeting00:40
*** novas0x2a|laptop has quit IRC00:41
*** markmcclain has quit IRC00:43
*** jog0_ has joined #openstack-meeting00:45
*** MarkAtwood has quit IRC00:47
*** metral has quit IRC00:47
*** jog0 has quit IRC00:47
*** jog0_ is now known as jog000:47
*** jhenner has joined #openstack-meeting00:48
*** alexpilotti has quit IRC00:50
*** sdake has quit IRC00:51
*** ryanpetrello has quit IRC00:53
*** ryanpetrello has joined #openstack-meeting00:59
*** stevebaker has quit IRC01:00
*** stevebaker has joined #openstack-meeting01:01
*** kmartin is now known as kmartin_zz01:01
*** Mandell has quit IRC01:06
*** Shree-HP has quit IRC01:06
*** rkukura has left #openstack-meeting01:07
*** mrodden has joined #openstack-meeting01:09
*** novas0x2a|laptop has joined #openstack-meeting01:09
*** Mandell has joined #openstack-meeting01:11
*** ewindisch has quit IRC01:12
*** Nachi has quit IRC01:12
*** sleepsonthefloor has quit IRC01:13
*** nati_ueno has joined #openstack-meeting01:13
*** vkmc has quit IRC01:14
*** ryanpetrello has quit IRC01:15
*** vkmc has joined #openstack-meeting01:20
*** gyee has quit IRC01:26
*** ryanpetrello has joined #openstack-meeting01:27
*** bencherian has quit IRC01:28
*** bencherian has joined #openstack-meeting01:28
*** bencherian has quit IRC01:34
*** salv-orlando has quit IRC01:35
*** eharney has joined #openstack-meeting01:37
*** eharney has joined #openstack-meeting01:37
*** danwent has quit IRC01:37
*** lifeless has quit IRC01:43
*** sarob has joined #openstack-meeting01:50
*** sthakkar has quit IRC01:51
*** nati_ueno has quit IRC01:51
*** dprince has joined #openstack-meeting01:54
*** eharney has quit IRC01:56
*** noslzzp has joined #openstack-meeting01:56
*** bencherian has joined #openstack-meeting01:59
*** novas0x2a|lapto1 has joined #openstack-meeting02:04
*** novas0x2a|laptop has quit IRC02:05
*** jhenner has quit IRC02:06
*** cp16net is now known as cp16net|away02:09
*** cp16net|away is now known as cp16net02:09
*** danwent has joined #openstack-meeting02:10
*** dwcramer has joined #openstack-meeting02:11
*** jog0 has quit IRC02:12
*** bdpayne has quit IRC02:13
*** stevebaker has quit IRC02:13
*** metral has joined #openstack-meeting02:15
*** adjohn_ has quit IRC02:15
*** ryanpetrello has quit IRC02:18
*** ewindisch has joined #openstack-meeting02:20
*** ewindisch_ has joined #openstack-meeting02:27
*** ewindisch has quit IRC02:27
*** ewindisch_ is now known as ewindisch02:27
*** metral has quit IRC02:28
*** nati_ueno has joined #openstack-meeting02:28
*** sarob has quit IRC02:32
*** metral has joined #openstack-meeting02:34
*** MarkAtwood has joined #openstack-meeting02:35
*** jog0 has joined #openstack-meeting02:36
*** jog0 has quit IRC02:36
*** ryanpetrello has joined #openstack-meeting02:38
*** emagana has quit IRC03:08
*** anniec has quit IRC03:15
*** dprince has quit IRC03:18
*** vkmc has quit IRC03:21
*** markwash has joined #openstack-meeting03:21
*** vkmc has joined #openstack-meeting03:23
*** ryanpetrello has joined #openstack-meeting03:24
*** adjohn has joined #openstack-meeting03:26
*** alrs has quit IRC03:29
*** bencherian_ has joined #openstack-meeting03:31
*** adjohn has quit IRC03:31
*** markvoelker has joined #openstack-meeting03:32
*** fnaval_ has joined #openstack-meeting03:32
*** fnaval_ has quit IRC03:33
*** DuncanT1 has joined #openstack-meeting03:36
*** Mandell has quit IRC03:37
*** novas0x2a|lapto1 has quit IRC03:39
*** bencherian has quit IRC03:39
*** fnaval has quit IRC03:39
*** CyclicFlux has quit IRC03:39
*** markvoelker1 has quit IRC03:39
*** DuncanT has quit IRC03:39
*** bencherian_ is now known as bencherian03:39
*** metral has quit IRC03:40
*** markwash has quit IRC03:41
*** CyclicFlux has joined #openstack-meeting03:46
*** markvoelker has quit IRC03:46
*** CyclicFlux is now known as Guest3698303:47
*** sandywalsh has quit IRC03:47
*** lifeless has joined #openstack-meeting03:48
*** markwash has joined #openstack-meeting04:08
*** sandywalsh has joined #openstack-meeting04:17
*** dwcramer has quit IRC04:17
*** radez is now known as radez_g0n304:19
*** markwash has quit IRC04:22
*** sandywalsh has quit IRC04:26
*** anniec has joined #openstack-meeting04:30
*** anniec has quit IRC04:31
*** anniec has joined #openstack-meeting04:31
*** dwcramer has joined #openstack-meeting04:31
*** bdpayne has joined #openstack-meeting04:33
*** afazekas has joined #openstack-meeting04:34
*** ryanpetrello has quit IRC04:38
*** sandywalsh has joined #openstack-meeting04:39
*** boris-42 has joined #openstack-meeting04:40
*** ladquin has quit IRC04:40
*** martine has quit IRC04:41
*** ryanpetrello has joined #openstack-meeting04:43
*** MarkAtwood has quit IRC04:44
*** koolhead17 has joined #openstack-meeting04:45
*** anniec has quit IRC04:57
*** sleepsonthefloor has joined #openstack-meeting05:00
*** ryanpetrello has quit IRC05:03
*** alrs has joined #openstack-meeting05:03
*** markmcclain has joined #openstack-meeting05:07
*** adjohn has joined #openstack-meeting05:09
*** henrynash has joined #openstack-meeting05:09
*** Mandell has joined #openstack-meeting05:10
*** dwcramer has quit IRC05:20
*** markwash has joined #openstack-meeting05:29
*** novas0x2a|laptop has joined #openstack-meeting05:32
*** markwash has quit IRC05:33
*** bdpayne has quit IRC05:33
*** garyk has quit IRC05:36
*** markmcclain has quit IRC05:38
*** metral has joined #openstack-meeting05:41
*** davidlenwell has quit IRC05:44
*** maurosr has quit IRC05:50
*** sacharya has quit IRC05:57
*** HenryG has quit IRC06:04
*** danwent has quit IRC06:06
*** koolhead11|away has joined #openstack-meeting06:16
*** mrunge has joined #openstack-meeting06:19
*** novas0x2a|laptop has quit IRC06:22
*** koolhead17 has quit IRC06:22
*** garyk has joined #openstack-meeting06:23
*** mnewby has quit IRC06:51
*** adjohn has quit IRC07:00
*** novas0x2a|laptop has joined #openstack-meeting07:01
*** afrittoli has quit IRC07:02
*** afrittoli has joined #openstack-meeting07:03
*** adjohn has joined #openstack-meeting07:04
*** davidha has quit IRC07:07
*** afazekas has quit IRC07:14
*** PopeAdolfTheFirs has quit IRC07:20
*** sandywalsh has quit IRC07:28
*** boris-42 has quit IRC07:30
*** Mandell has quit IRC07:43
*** sandywalsh has joined #openstack-meeting07:48
*** matiu_ has joined #openstack-meeting07:50
*** matiu_ has quit IRC07:53
*** rafaduran has joined #openstack-meeting08:02
*** davidha has joined #openstack-meeting08:10
*** EmilienM has joined #openstack-meeting08:13
*** flaper87 has joined #openstack-meeting08:30
*** koolhead11|away has quit IRC08:35
*** boris-42 has joined #openstack-meeting08:42
*** afazekas has joined #openstack-meeting08:43
*** koolhead11|away has joined #openstack-meeting08:48
*** koolhead11|away has quit IRC08:55
*** Yada has joined #openstack-meeting08:57
*** sandywalsh has quit IRC09:08
*** sandywalsh has joined #openstack-meeting09:09
*** darraghb has joined #openstack-meeting09:12
*** jhenner has joined #openstack-meeting09:19
*** pnavarro has joined #openstack-meeting09:33
*** salv-orlando has joined #openstack-meeting09:33
*** metral has quit IRC09:34
*** adjohn has quit IRC09:42
*** emagana has joined #openstack-meeting09:52
*** dkehn_away has left #openstack-meeting09:57
*** flaper87 has quit IRC10:21
*** Guest36983 has quit IRC10:32
*** salv-orlando has quit IRC10:32
*** derekh has joined #openstack-meeting10:36
*** novas0x2a|laptop has quit IRC10:37
*** anniec has joined #openstack-meeting10:44
*** anniec has joined #openstack-meeting10:44
*** henrynash has quit IRC10:48
*** novas0x2a|laptop has joined #openstack-meeting11:05
*** asalkeld has quit IRC11:14
*** asalkeld has joined #openstack-meeting11:17
*** maurosr has joined #openstack-meeting11:28
*** emagana_ has joined #openstack-meeting11:32
*** emagana has quit IRC11:36
*** almaisan-away is now known as al-maisan11:43
*** martine has joined #openstack-meeting11:44
*** ladquin has joined #openstack-meeting11:44
*** jaypipes has quit IRC11:44
*** ladquin1 has joined #openstack-meeting11:44
*** SpamapS_ has joined #openstack-meeting11:49
*** SpamapS has quit IRC11:49
*** nijaba has quit IRC11:49
*** nijaba has joined #openstack-meeting11:51
*** nijaba has quit IRC11:51
*** nijaba has joined #openstack-meeting11:51
*** salv-orlando has joined #openstack-meeting11:59
*** jaypipes has joined #openstack-meeting12:01
*** EmilienM has left #openstack-meeting12:04
*** nati_ueno has quit IRC12:13
*** nati_ueno has joined #openstack-meeting12:14
*** nati_ueno has quit IRC12:18
*** flaper87 has joined #openstack-meeting12:27
*** ttrifonov is now known as ttrifonov_zZzz12:34
*** ttrifonov_zZzz is now known as ttrifonov12:46
*** noslzzp has quit IRC12:48
*** writerDiane has joined #openstack-meeting12:52
*** writerDiane has left #openstack-meeting13:03
*** Daisy has joined #openstack-meeting13:03
*** writerDiane has joined #openstack-meeting13:03
DaisyIs Anne or Tom there?13:07
DaisyHi, Diane13:07
DaisyI think it's time for doc meeting. Am I right?13:08
writerDianeThat's what I thought! Don't know where they are.13:08
*** dolphm has joined #openstack-meeting13:09
*** markvoelker has joined #openstack-meeting13:15
*** emagana_ has quit IRC13:17
*** noslzzp has joined #openstack-meeting13:21
*** EmilienM has joined #openstack-meeting13:22
*** fifieldt has joined #openstack-meeting13:23
fifieldtDaisy, did I miss the meeting?13:25
DaisyHi, Tom13:25
DaisyNo, the meeting is not started.13:25
EmilienMwhen does it start ? :)13:25
fifieldtMy impression was that it was starting at 1300 UTC13:26
fifieldtwhich is ~26 mins ago13:26
fifieldtok, so my guess is we have no Anne?13:26
DaisyI think maybe we schedule another time for next meeting.13:26
*** dwcramer has joined #openstack-meeting13:27
DaisyI think 1300 UTC is too early for Anne.13:27
fifieldtyeah, probably13:27
DaisyMaybe 30 minutes late, i.e. 1330 UTC13:27
fifieldtthat's fine for me13:27
fifieldtis it OK for you?13:27
DaisyIt should be 12:30 am for you?13:28
fifieldtin my old job I had one day with meetings at : 1800, 0000, 0300, 0600, 1000 ... it was fun :)13:28
DaisyYou can have a short sleep before the meeting. :)13:29
writerDianeOr just sleep during the meeting! :)13:29
DaisyLet's discuss it with Anne when she comes.13:29
fifieldtin the mean time we could discuss the action items from the previous meeting13:30
fifieldtsince I believe they are all having clear outcomes13:30
Daisyok. Let's start the meting.13:30
fifieldt#startmeeting docwebteam13:30
openstackMeeting started Tue Feb 12 13:30:44 2013 UTC.  The chair is fifieldt. Information about MeetBot at http://wiki.debian.org/MeetBot.13:30
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:30
*** openstack changes topic to " (Meeting topic: docwebteam)"13:30
openstackThe meeting name has been set to 'docwebteam'13:30
fifieldtso the previous meeting was on 2013-01-0813:31
fifieldtwe had 4 action items13:31
fifieldt#1: annegentle-web to share the proposal for the book sprint13:31
fifieldtI believe Anne did this and asked for feedback on the outline on etherpad13:31
fifieldtcan someone confirm?13:31
fifieldt#info http://wiki.openstack.org/Meetings/DocTeamMeeting13:32
fifieldt#topic action items13:32
*** openstack changes topic to "action items (Meeting topic: docwebteam)"13:32
*** asalkeld has quit IRC13:33
DaisyIn my mind, I didn't see it. I'm checking my mail.13:33
fifieldtthanks Daisy13:33
*** asalkeld has joined #openstack-meeting13:33
fifieldthi EmilienM13:33
DaisyI don't find such mail in my mail box.13:34
fifieldtOK, so maybe she hasn't done it yet13:34
fifieldtthat's fine13:34
DaisyYeah. Maybe she is too busy.13:34
fifieldtso I would propose that she, or some delegate explain the principle of the doc sprint and ask for feedback onto the etherpad ?13:34
fifieldt#link http://etherpad.openstack.org/EssexOperationsGuide13:34
fifieldtdoes that sound reasonable?>13:35
DaisyI'm fine with it.13:35
fifieldt#action AnneGentle or delegate to explain the principle of the doc sprint and ask for feedback onto the etherpad prior to the doc sprint (i.e. this week ASAP)13:35
fifieldtOK, the next action item13:36
fifieldt#2: annegentle-web to investigate wiki migration status13:36
fifieldtI believe that I saw an email about this from Anne13:36
fifieldt[Openstack] Progress on wiki migration to Mediawiki on 19/113:36
fifieldtso I believe this action item is done13:36
fifieldtthe next action item13:37
fifieldt#3: Daisy write up what the role of a lead translator would be? And what permissions they'd need where?13:37
fifieldtDaisy, I saw the email from you today13:37
fifieldtso I'd consider that you did this quite well and are just waiting on feedback ?13:37
DaisyOh. My mail doesn't cover this topic.13:37
DaisyI can write another mail this week to include this information.13:37
fifieldtthat would be excellent, I think13:38
fifieldtperhaps tied in with your existing proposal somehow? :) you're the expert ....13:38
fifieldt#action Daisy write up what the role of a lead translator would be? And what permissions they'd need where?13:38
fifieldt#action all to provide feedback on Daisy's proposal for translation access control13:39
DaisyI'm on vacation this week, Tom, for Chinese New years holiday.13:39
fifieldtThe final action point we have listed is:13:39
fifieldtof course!13:39
fifieldtplease, enjoy your holiday!13:39
DaisySo I will do it next week week.13:39
fifieldtthis seems entirely reasonable :)13:40
fifieldt#4 EmilienM to reply to comments & fix bugs if they exist.13:40
fifieldtEmilienM, are you happy with the bug progress compared to last meeting?13:40
EmilienMfifieldt: yes :)13:41
fifieldtis anything bothering you (apart from our overwhelming lack of people) ? :)13:41
*** dwcramer has quit IRC13:41
fifieldtok, cool - let's consider this one ongoing work, rather than a specific action item13:42
*** ryanpetrello has joined #openstack-meeting13:42
fifieldtladquin, just pinging you in case you're around for the doc meeting and need anything :)13:42
ladquinI am.  Hey there, folks13:42
fifieldtHi ladquin!13:43
ladquinbut no needs so far, thanks!13:43
*** emagana has joined #openstack-meeting13:43
fifieldtAll, after our action items the next on the agenda is : Wiki migration, Grizzly priorities, Do we need an #openstack-doc IRC channel?, Doc tools update, Open discussion13:43
fifieldtdoes anyone have anything to add to that agenda?13:43
Daisyno, I don't have.13:44
fifieldtthanks Daisy -- EmilienM, writerDiane ?13:45
fifieldtok, assuming not13:47
fifieldtI don't want to touch wiki migration without AnneGentle13:47
fifieldtbut perhaps we can do an easy one like "Do we need an #openstack-doc IRC channel?"13:48
fifieldtdo people want to attempt to answer that?13:48
fifieldt#topic Do we need an #openstack-doc IRC channel?13:48
*** openstack changes topic to "Do we need an #openstack-doc IRC channel? (Meeting topic: docwebteam)"13:48
EmilienMyes !13:49
DaisyI'm glad to have one, although I cannot answer why.13:50
fifieldtI'm interested in justifications too13:50
fifieldthere's a potential one: for coordination between the documentation team, to promote interactive discussions, rather than having them via email13:50
DaisyI guess, some doc team members should be there any time, in order to answer questions from developers and users.13:50
fifieldtthat's also good13:51
ladquinI think it'd be worth it.  Lurking in -dev I see many of the questions are about docs, so even if we're few people at first, it would get crowded soon, I guess13:51
fifieldtindeed, so many questions about docs ladquin13:51
Daisygreat explaination, ladquin !13:51
*** jjm3lp has quit IRC13:52
EmilienMfifieldt: +113:52
writerDianeI agree - separate openstack-docs would be good13:52
fifieldtok, it seems we're in agreeance13:52
Daisygreat !13:52
fifieldt#action all to start using #openstack-docs13:52
fifieldt#action AnneGentle to formalise #openstack-docs, including justification for separate channel and any other necessary work to register the channel13:53
Daisywe shall broadcast it to the community.13:53
fifieldt#action AnneGentle to email the community once the channel is setup13:53
fifieldtAssigning action items to people who aren't here is evil .. but fun13:53
*** anteaya has joined #openstack-meeting13:53
*** emagana has quit IRC13:54
*** writerDiane has left #openstack-meeting13:54
Daisygood work, Tom.13:54
fifieldtSo left on the agenda we have: Wiki migration, Grizzly priorities, Doc tools update, Open discussion13:54
*** lorin1 has joined #openstack-meeting13:54
fifieldtSo left on the agenda we have: Wiki migration, Grizzly priorities, Doc tools update, Open discussion13:55
fifieldtI'm not sure on the wiki migration status, but perhaps we could look at Grizzly priorities13:55
fifieldt#topic Grizzly Priorities13:55
*** openstack changes topic to "Grizzly Priorities (Meeting topic: docwebteam)"13:55
DaisyI agree.13:55
fifieldt#link https://launchpad.net/openstack-manuals/+milestone/grizzly13:55
fifieldt#link https://launchpad.net/openstack-api-site/+milestone/grizzly13:55
fifieldtfirst, ladquin, do you have a feeling on how things are going for grizzly API-wise?13:56
fifieldtit seems like you're doing quite well13:56
*** sandywalsh_ has joined #openstack-meeting13:57
ladquinfifieldt, I think we might be ok for grizzly, but it seems tome that there are some unreported work thats not there too13:58
fifieldtah, right13:58
ladquinannegentle may give us a better idea13:58
fifieldtare you going to be looking for missing things, or do you need us to remind people to use DocImpact again for API changes?13:58
fifieldtWhile Laura is looking, here are the stats for the manuals project right now:      19 New, 47 Confirmed, 1 Triaged, 2 In Progress, 15 Fix Released14:00
fifieldtit's a lot of work14:00
fifieldtwith pretty much everything marked as "Medium"14:00
ladquinfifieldt, oh no they use it a lot! :P  but perhaps I'm going through too much detail14:00
fifieldtno worries :)14:00
fifieldtOK - so just let just know if you need anything14:00
fifieldtlooking at the grizzly milesone bug lists for both projects, is there anything that jumps out as more important or less important for people?14:01
ladquinfifieldt, what I'm really missing right now is samples, I've filed some bugs, but I can try to generate them myself (under supervision)14:01
fifieldtah, right14:01
fifieldtdo you need a test environment ladquin?14:01
fifieldtpersonally, I think Quantum and Cinder docs right now are lacking. I also really want to see Cells as a first-class citizen of the documents14:03
*** matiu has quit IRC14:03
fifieldtany other ideas?14:03
ladquinI do have one, I just couldn't dedicate a lot of time to testing the apis, as it was not a priority (maybe now)14:04
fifieldtno dramas :)14:04
fifieldtmy personal aim: get the grizzly version of everything out to the release as close as possible14:05
fifieldtok, since noone has any ideas right now, I propose we take this discussion back to the mailing list14:05
fifieldt#action all to discuss grizzly priorities on the mailing list (and work on them!)14:05
fifieldtSince we don't have the people here to talk about wiki migration or doc tools, this only leaves open discussion14:06
fifieldt#topic open discussion14:06
*** openstack changes topic to "open discussion (Meeting topic: docwebteam)"14:06
fifieldtover to you, EmilienM, lorin1, ladquin, Daisy for your thoughts on anything and everything :)14:06
*** dprince has joined #openstack-meeting14:07
*** matiu has joined #openstack-meeting14:08
lorin1Don't really have anything to add here...14:08
lorin1Oh, I should mention the Cells docs14:09
lorin1I have a WIP branch, I'm waiting for Chris Behrens to give me the OK that's accurate.14:09
lorin1I pinged him a couple of days ago on this, he said all of the pending code landed, he needs to look over the docs again.14:09
fifieldtSometimes Chris is slow14:09
fifieldtif you need help, we're running Cells in production14:10
lorin1Is there someone else we could ping re cells?14:10
fifieldtso I might be able to look over it with colleagues14:10
lorin1fifeldt: Can you look over the WIP branch?14:10
lorin1OK, I'm going to set it to a regular merge proposal.14:10
fifieldt#action fifieldt to look over Cells WIP branch or ask his colleagues to fix it14:10
lorin1Also, I'd like to eventually morph that into a chapter on "Partitioning your OpenStack cloud" and provide an overview of regions, zones, cells, availability zones, and host aggregates.14:10
fifieldtsounds sorely needed14:11
fifieldtOK, if noone else has anything to say ... we can close the meeting?14:12
*** egallen has quit IRC14:12
lorin1good for me.14:12
fifieldtEmilienM ?14:12
*** jaypipes has quit IRC14:12
*** lbragstad has joined #openstack-meeting14:13
fifieldtExcellent. Thanks all for attending the meeting. I'll try to followup with Anne about the meeting time and hope to see all of you on the mailing list until next meeting :)14:13
fifieldt#action fifieldt to followup with AnneGentle about the meeting time14:13
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"14:13
openstackMeeting ended Tue Feb 12 14:13:51 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-02-12-13.30.html14:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-02-12-13.30.txt14:13
openstackLog:            http://eavesdrop.openstack.org/meetings/docwebteam/2013/docwebteam.2013-02-12-13.30.log.html14:13
DaisyThanks, Tom.14:14
fifieldtThanks all :)14:14
ladquinthank you!14:14
DaisyHave a good night !14:14
fifieldtcheers, sleep well - whenever that is in your timezones :)14:14
*** Daisy has quit IRC14:15
*** fifieldt has quit IRC14:15
*** lorin1 has left #openstack-meeting14:15
*** joesavak has joined #openstack-meeting14:16
*** jaypipes has joined #openstack-meeting14:17
*** emagana has joined #openstack-meeting14:19
*** beagles is now known as beagles|brb14:23
*** jsavak has joined #openstack-meeting14:23
*** joesavak has quit IRC14:27
*** emagana has quit IRC14:31
*** mtreinish has joined #openstack-meeting14:34
*** dwcramer has joined #openstack-meeting14:37
*** primeministerp has joined #openstack-meeting14:40
*** davidh_ has joined #openstack-meeting14:40
*** davidha has quit IRC14:42
*** markmcclain has joined #openstack-meeting14:46
*** radez_g0n3 is now known as radez14:48
*** markmcclain has quit IRC14:48
*** mattray has joined #openstack-meeting14:54
*** eharney has joined #openstack-meeting14:56
*** eharney has quit IRC14:56
*** eharney has joined #openstack-meeting14:56
*** emagana has joined #openstack-meeting14:56
*** mnewby has joined #openstack-meeting14:59
*** flaper87 has quit IRC15:00
*** fnaval has joined #openstack-meeting15:02
*** al-maisan is now known as almaisan-away15:03
*** markvan has joined #openstack-meeting15:06
*** john5223 has joined #openstack-meeting15:06
*** emagana has quit IRC15:07
*** markvan has quit IRC15:09
*** markvan has joined #openstack-meeting15:09
*** garyTh has joined #openstack-meeting15:10
*** john5223 has quit IRC15:11
*** john5223 has joined #openstack-meeting15:11
*** sdake has joined #openstack-meeting15:15
*** markvan has quit IRC15:15
*** egallen has joined #openstack-meeting15:16
*** patrocinio has joined #openstack-meeting15:16
*** alexpilotti has joined #openstack-meeting15:17
*** alexpilotti has quit IRC15:17
*** alexpilotti has joined #openstack-meeting15:18
*** markvan has joined #openstack-meeting15:19
*** rnirmal has joined #openstack-meeting15:24
*** markvan has quit IRC15:28
*** HenryG has joined #openstack-meeting15:32
*** diogogmt has joined #openstack-meeting15:32
*** primeministerp has quit IRC15:33
*** ryant_ has quit IRC15:33
*** boris-42 has quit IRC15:33
*** emagana has joined #openstack-meeting15:34
*** primeministerp has joined #openstack-meeting15:38
*** Gordonz has joined #openstack-meeting15:41
*** Gordonz has quit IRC15:41
*** maoy has joined #openstack-meeting15:42
*** Gordonz has joined #openstack-meeting15:42
*** luis_fdez has joined #openstack-meeting15:44
*** emagana has quit IRC15:46
*** iben has joined #openstack-meeting15:46
*** sacharya has joined #openstack-meeting15:53
*** topol has joined #openstack-meeting15:54
*** patrocinio has quit IRC15:55
*** iben-mobile has joined #openstack-meeting15:56
*** ayoung has quit IRC15:56
primeministerp#startmeeting hyper-v15:56
openstackMeeting started Tue Feb 12 15:56:59 2013 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.15:57
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:57
*** openstack changes topic to " (Meeting topic: hyper-v)"15:57
openstackThe meeting name has been set to 'hyper_v'15:57
primeministerphi everyone15:57
primeministerpcouple of things to discuss today15:57
*** sacharya has quit IRC15:57
primeministerpiben-mobile: how are things going on your end15:57
pnavarrohello people15:58
primeministerpalexpilotti: are you with us15:58
*** ociuhandu has joined #openstack-meeting15:58
alexpilottihi there!15:58
primeministerppnavarro: hi pedro15:58
primeministerpalexpilotti: is tavi coming today?15:59
primeministerpshall we begin15:59
primeministerpalexpilotti has been working quite hard at getting the resize feature done15:59
primeministerpalexpilotti: i know the first part got a +216:00
*** iben-mobile has quit IRC16:00
primeministerphas there been any additional activity?16:00
alexpilottiyes, everything is looking well16:00
alexpilottifeatures are done16:00
*** ociuhandu has quit IRC16:01
alexpilottiThere are a lot of conductor related issues16:01
primeministerpalexpilotti: continue...16:01
*** ociuhandu has joined #openstack-meeting16:01
alexpilottiso we have to test them as well to help in fixing them16:01
*** fnaval_ has joined #openstack-meeting16:01
ociuhanduhi all, sorry for being late :)16:01
alexpilottiresize is not tested by tempest16:01
primeministerpociuhandu: no worries16:01
alexpilottiso a lot of issues simply got through16:02
primeministerpalexpilotti: we'll have to write that16:02
primeministerpi'm assuming16:02
primeministerpthe tempest bits16:02
alexpilottiand they discovered them now that we started testing them :-)16:02
primeministerpthat's a good thing16:02
ibenthings are going good - slow but steady - getting customer resources lined up to expand project internally16:02
alexpilottiwhen I say missing resize on Tempest, I mean on KVM etc as well16:02
primeministerpalexpilotti: do you have specific bugs16:02
*** bdperkin has joined #openstack-meeting16:02
primeministerpalexpilotti: ahh16:03
alexpilottiplenty :-)16:03
primeministerpalexpilotti: so it really wasn't be testing16:03
*** fnaval_ has quit IRC16:03
primeministerper tested16:03
primeministerpiben: great16:03
*** kmartin_zz is now known as kmartin16:03
uvirtbotLaunchpad bug 1120402 in nova "ConfigDrive uses metadata service which hits the database from within nova-compute" [High,In progress]16:03
uvirtbotLaunchpad bug 1119873 in nova "nova-compute crashes if restarted with an instance in VERIFY_RESIZE state" [High,Triaged]16:03
*** fnaval_ has joined #openstack-meeting16:03
uvirtbotLaunchpad bug 1119817 in nova "Missing exception data for exceptions raised in resize methods" [Undecided,Fix committed]16:04
primeministerpalexpilotti: thx16:04
uvirtbotLaunchpad bug 1117882 in nova "Resize doesn't apply the hypervisor_type filter in choosing the migration target" [High,Triaged]16:04
*** bdperkin has quit IRC16:04
*** bdperkin has joined #openstack-meeting16:04
*** annegentle has joined #openstack-meeting16:04
alexpilottithe last one is a big issue16:04
*** woodspa has joined #openstack-meeting16:04
primeministerplooking now16:04
*** patrocinio has joined #openstack-meeting16:04
*** fnaval has quit IRC16:05
*** bvibhu has joined #openstack-meeting16:05
alexpilottiit tries to migrate from Hyper-V to KVM :-)16:05
primeministerpo yes16:05
primeministerpwe discussed16:05
primeministerpwas taking a second to load16:05
alexpilottieven if the image has a hypervisor property set16:05
primeministerpyeah that's to good16:06
*** rushiagr1 has joined #openstack-meeting16:06
alexpilottidansmith is working hard to fix them16:06
*** bvibhu has quit IRC16:06
*** fnaval_ has quit IRC16:06
alexpilottiI did quite a lot of extensive testing on resize, so hopefully we won't have big surprises :-)16:07
primeministerpI think we'll be in a good position to start adding some value to the testing once we're back from redmond16:07
primeministerpalexpilotti: great16:07
primeministerpmoving on16:07
primeministerpto the other issues that need to be addressed16:08
alexpilottiBut before the Grizzly release after G3, It'd be great to have some community help in testing all the feature16:08
*** iben-mobile has joined #openstack-meeting16:08
primeministerpas always16:08
*** lbragstad has quit IRC16:08
pnavarrobeers for bugs16:08
primeministerpI'm not putting that in writing16:08
alexpilottipnavarro: sure, plenty! :-)16:08
primeministerp... but see me at the summit16:09
alexpilotti(of beers, not of bugs, hopefully)16:09
primeministerpluis_fdez: ping16:09
*** fnaval has joined #openstack-meeting16:09
primeministerpluis_fdez: any chance you'll be able to check out the resize bits?16:09
*** gyee has joined #openstack-meeting16:10
luis_fdezas I'm excited after reciving the mail of alexpilotti, I think I'll try it!! hehe16:10
primeministerp#topic missing features16:10
*** openstack changes topic to "missing features (Meeting topic: hyper-v)"16:10
*** adjohn has joined #openstack-meeting16:10
primeministerpso moving on16:10
primeministerpwe have some area's that need to be addressed16:11
primeministerpspecifically in terms of resize on boot16:11
alexpilottiluis_fdez: is it important for you guys th eresize on boot?16:11
primeministerpand •ephemeral storage16:11
primeministerpalexpilotti: resize on boot is important for everyone i would imagine16:12
alexpilottiI mean currently Hyper-V deploys the glance image w/o resizing it16:12
*** emagana has joined #openstack-meeting16:12
primeministerpalexpilotti: storing windows images can become quite horrible16:12
luis_fdezalexpilotti: I think it would be useful as our environment could mix really different flavors16:12
alexpilottiprimeministerp: up to a point, private clouds might simply not care as they have tailored images16:12
primeministerpalexpilotti: nod16:12
alexpilottiluis_fdez: cool16:12
primeministerpalexpilotti: but generally being able expand to a specific size at boot is useful16:13
alexpilottiBTW the current version of resize expands the VHDs, but not the guest partitions16:13
alexpilottiI'm thinking about adding a simple feature to Cloudbase-init16:14
primeministerpalexpilotti: I was going to say16:14
primeministerpthat would have to be handled by the booting os16:14
alexpilottito simply expand the last partition ;-)16:14
luis_fdezas a starting point is ok, from an unattend file is easy to expand the partition to the new size when the vm is deployed16:14
primeministerpalexpilotti: that might be a great workaround16:14
alexpilottiyep, IMO is a guest os thing16:14
primeministerpluis_fdez: that would work too16:14
alexpilottiI frankly don't like too much the fact that the Hypervirso fiddles with guest OS partitions16:14
primeministerpalexpilotti: seperation of church and state is key16:15
alexpilottiIt will be necessary for AKI/AMI/ARI16:15
alexpilottiIn Italy we try to repeat it since a few centuries, but it doesn'r really work ;-)16:16
pnavarroalexpilotti: +116:16
*** john5223 has quit IRC16:16
alexpilottiso about resize on boot16:16
alexpilottia big advantage of VHDX over VHD is that it handles resize of differential disks16:17
*** davidh__ has joined #openstack-meeting16:17
alexpilottiwe could add resize on bot now, before closing Grizzly on VHD but:16:17
alexpilottiif a CoW image comes in, we need to convert it to non CoW before resizing it OR, and here comes the trick:16:18
*** danwent has joined #openstack-meeting16:18
alexpilottiwe copy the base disk for each requested flavor and we resize that one.16:18
alexpilottibefore creating the diff disk16:18
alexpilottiso the format will be e.g.:16:18
alexpilottiand we can go on w CoW as usual16:19
alexpilottithe only drawback is that it's not possible to change a flavor's size after the first deployment16:19
luis_fdezand what's the main drawback in that case?16:19
alexpilottiluis_fdez: ^16:19
luis_fdezhehe, you read my mind!16:20
*** davidh_ has quit IRC16:20
alexpilottiso if you need to change a flavor, you simply change ID as well :-)16:20
primeministerpalexpilotti: well strictly from a security perspective it's not a good thing16:20
alexpilottiprimeministerp: why?16:20
primeministerpalexpilotti: sorry16:21
primeministerpalexpilotti: was talking about the hypervisor controlling guest bits16:21
alexpilottiprimeministerp: ok :-)16:22
primeministerpalexpilotti: i was sidetracked for a moment16:22
alexpilottiprimeministerp: "a moment" ? :-D16:22
primeministerpalexpilotti: people talking to me16:22
primeministerpdistracting my attention16:22
primeministerpback to the missing features16:22
primeministerpI think they are on the list for H16:23
*** emagana has quit IRC16:23
alexpilottiprimeministerp: here's a quick list, Nova related:16:24
alexpilotti- Nova dynamic memory16:24
alexpilotti- Nova ephemeral storage16:24
alexpilotti- Nova progress update16:24
alexpilotti- Nova resize on spawn (currently images are not resized)16:24
alexpilotti- Nova support for AMI / ARI / AKI16:24
alexpilotti- Nova guest FS resize (at least: NTFS, EXT2-4)16:24
alexpilotti-Nova rescue16:24
primeministerpI don't think i had rescue on my list16:24
primeministerpperfect thx16:25
alexpilottiprimeministerp: yes sorry, it's a new entry :-)16:25
primeministerpadd it yours ;)16:25
primeministerpyours it more important at this time16:25
alexpilottiit got added today, was going to send it w the rest later16:25
primeministerpso moving on16:26
alexpilottianyway, the good news is that no big features are missing16:26
primeministerpalexpilotti: that's what we were shooting for16:26
primeministerpalexpilotti: great work16:26
alexpilottimerci :-)16:26
*** lbragstad has joined #openstack-meeting16:26
alexpilottiresize was the last big thing16:26
primeministerpociuhandu: ping16:27
ociuhanduprimeministerp: pong16:27
primeministerp#topic general updates16:27
*** openstack changes topic to "general updates (Meeting topic: hyper-v)"16:27
primeministerpociuhandu: got my scripts running out unattend.xml16:27
primeministerpociuhandu: debugging puppet install16:27
primeministerpociuhandu: i'll be back in the office tomorrow16:27
primeministerpociuhandu: we can start testing the whole compute node deployment then16:28
*** bdpayne has joined #openstack-meeting16:28
ociuhanduprimeministerp: great16:28
primeministerpociuhandu: I made good progress this am16:28
alexpilottivishy: hi, any chance you could take a look at: https://review.openstack.org/#/c/21695/ :-)16:28
ociuhanduprimeministerp: excellent16:29
*** sacharya has joined #openstack-meeting16:29
primeministerpanyone have anything else they would like to add16:29
primeministerpif not I'm closing it16:30
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"16:30
openstackMeeting ended Tue Feb 12 16:30:51 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:30
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-02-12-15.56.html16:30
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-02-12-15.56.txt16:30
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-02-12-15.56.log.html16:30
*** pony has joined #openstack-meeting16:30
primeministerpthanks everyone16:31
ociuhanduprimeministerp: going to ping you later16:31
*** markmcclain has joined #openstack-meeting16:33
primeministerpociuhandu: ok16:33
tsygrlSorry i missed meeting !16:35
tsygrlIs there anyone here i can talk to about the website - i found a bit of an error in one of the pages at openstack.org.16:35
alexpilottitsygrl: sure, which one?16:36
tsygrlThe description of the ubuntu install does not tell to install the swift packages.16:38
tsygrl(just the redhat family description)16:38
alexpilottitsygrl: we just finished a OpenStack Hyper-V meeting :-)16:38
alexpilottitsygrl: so I cannot help you too much w Swift related documentation16:39
*** iben-mobile has quit IRC16:39
*** iben-mobile has joined #openstack-meeting16:39
tsygrlalexpilotti, who could help - i want the docs to be the best possible ....16:39
alexpilottitsygrl: I suggest you to ask in #OpenStack-Swift16:39
*** garyk has quit IRC16:40
tsygrlalexpilotti, heading over there.16:40
alexpilottitx vishy!16:44
*** iben-mobile has quit IRC16:48
*** iben-mobile has joined #openstack-meeting16:48
*** mattray has quit IRC16:49
*** emagana has joined #openstack-meeting16:49
*** markwash has joined #openstack-meeting16:52
*** SpamapS_ is now known as SpamapS16:52
*** SpamapS has joined #openstack-meeting16:53
*** mattray has joined #openstack-meeting16:53
*** topol_ has joined #openstack-meeting16:53
*** fnaval_ has joined #openstack-meeting16:54
*** topol has quit IRC16:56
*** topol_ is now known as topol16:56
*** fnaval has quit IRC16:57
*** emagana has quit IRC17:01
*** rushiagr1 has quit IRC17:06
*** boris-42 has joined #openstack-meeting17:11
*** beagles|brb is now known as beagles17:15
*** adjohn has quit IRC17:16
*** hemna has joined #openstack-meeting17:18
*** jaypipes has quit IRC17:24
*** davidh__ has quit IRC17:26
*** davidh_ has joined #openstack-meeting17:27
*** anniec has quit IRC17:29
*** lglenden has joined #openstack-meeting17:31
*** emagana has joined #openstack-meeting17:33
*** iben-mobile has quit IRC17:34
*** jog0 has joined #openstack-meeting17:37
*** lloydde has joined #openstack-meeting17:38
*** stevemar has joined #openstack-meeting17:39
*** rafaduran has left #openstack-meeting17:39
*** markmcclain has quit IRC17:43
*** metral has joined #openstack-meeting17:43
*** kwss has joined #openstack-meeting17:48
*** lcheng has joined #openstack-meeting17:50
*** donaldngo_hp has joined #openstack-meeting17:53
*** dwcramer has quit IRC17:56
*** garyk has joined #openstack-meeting17:57
*** nati_ueno has joined #openstack-meeting17:57
topolkeystone time?17:58
*** brich1 has joined #openstack-meeting17:58
*** spzala has joined #openstack-meeting17:59
stevemartopol: soon17:59
*** henrynash has joined #openstack-meeting17:59
stevemarhenrynash: hello18:01
*** Haneef has joined #openstack-meeting18:01
*** anniec has joined #openstack-meeting18:01
*** heckj has joined #openstack-meeting18:02
heckj#startmeeting keystone18:02
openstackMeeting started Tue Feb 12 18:02:18 2013 UTC.  The chair is heckj. Information about MeetBot at http://wiki.debian.org/MeetBot.18:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:02
*** openstack changes topic to " (Meeting topic: keystone)"18:02
openstackThe meeting name has been set to 'keystone'18:02
heckjwho's around?18:02
topoltopol is here18:02
henrynashheckj: hi18:02
stevemarheckj: hello18:02
*** nachi has joined #openstack-meeting18:03
heckjexcellent! Welcome all18:03
*** nachi_ has joined #openstack-meeting18:03
heckjgrabbing up the agenda18:03
heckjpretty stock - agenda at #link http://wiki.openstack.org/Meetings/KeystoneMeeting18:03
heckjayoung? dolphm? either of you around?18:03
topolheckj, I had a quick question that I wanted to add to the agenda. Sent it to dolphm but forgot to send to you18:03
heckjtopol no problem - whatcha got?18:04
*** derekh has quit IRC18:04
dolphmi'm here18:04
heckj#topic burning issues18:04
*** openstack changes topic to "burning issues (Meeting topic: keystone)"18:04
dolphmtopol: you should be able to edit the agenda with a wiki account18:04
*** iben has quit IRC18:04
heckjtopol: in the future, please do edit the agenda - common place to keep us organized18:05
topoldolphm, another newbie error by me. will do that next time.18:05
heckjAnything top on the list?18:05
dolphmheckj: just review! review! review!18:05
heckjgyee: last time, this was almost entirely focused on auth API - you good?18:05
topolmy question was regarding my devstack keystone ldap identity driver work18:05
topolSo in keystone.conf I set user_attribute_ignore = tenant_id,tenants,enabled and this allowed me to now successfully add a user using the ldap backend. My question is for getting keystone ldap to work from devstack should we just do this or am I hiding stuff under the rug and we really need to store the enabled attribute and thus we should add an extra objectClass to address this?18:05
*** mrunge has quit IRC18:05
gyeeheckj, yeah18:05
gyeemaking good progress, https://review.openstack.org/#/c/21487/18:06
heckjtopol: cool, we'll come back to that18:06
gyeemissing tests and doc18:06
*** jaypipes has joined #openstack-meeting18:06
gyeeI am working on the tests at the moment18:06
dolphmtopol: i think we'd definitely prefer a place to store it, especially in tests18:06
heckj#topic blueprint statii18:06
*** openstack changes topic to "blueprint statii (Meeting topic: keystone)"18:06
heckjWe have grizzly-3 milestone coming up in just over a week - that's the feature freeze time18:07
heckj#link http://wiki.openstack.org/GrizzlyReleaseSchedule18:07
dolphmi believe the last piece of bp default-domain is gating right now18:07
heckjdolphm: excellent18:07
gyee9 more days!18:08
topolI have free cycles to review stuff so let me know what is most critical18:08
*** sarob has joined #openstack-meeting18:08
heckjgyee: pluggable authn also coming in with the API implementation?18:08
henrynashheckj: …and that same change includes all the domain-scoping prep work…so ready to plug into v3 auth18:08
gyeeheckj, yes, there are 3 bps in there18:08
dolphmtopol: anything that's not specifically a bug18:08
topoldolphm: Will do!18:09
dolphmgyee's review is definitely most critical of all18:09
heckjfor all - the thing that will make this next week go the most smoothly with be consistent and clear reviews. If you can, please look over the list daily and update any that you see.18:09
dolphmheckj: +1018:09
henrynashheckj: on domain name spaces, we agreed the spec change…and the good news is that the work on top of the domain-scoping is really just to ensure name uniques constraints are set right18:09
topolwill do Gyees today18:09
heckjAnyone know status from ayoung on token trusts and the replacement of tenant-membership with role?18:10
heckjlink for reviews: #link https://review.openstack.org/#/q/status:open+keystone,n,z18:11
henrynashheckj: review is up, not quite there…I did suggest an alternative approach to what he is doing that *may* be simpler (its a comment on his review)18:11
henrynashsee my comment to patch 4: https://review.openstack.org/#/c/21327/18:12
dolphmheckj: would love to get tenant-membership refactor in ASAP, and ayoung said he was going to tackle the identity-api for trusts related changes as well18:13
heckjOkay - I've got what I need to update for the release meeting anyway.18:14
heckj#topic Topol's LDAP question18:14
*** openstack changes topic to "Topol's LDAP question (Meeting topic: keystone)"18:14
dolphmayoung is also blocking bp additional-endpoint-metadata which is just a giant nice-to-have for grizzly -- not sure how to resolve his concern18:14
henrynashdolphm: take a look at my suggestion on tenant-membership….I may be missing something18:14
heckjtopol said: So in keystone.conf I set user_attribute_ignore = tenant_id,tenants,enabled and this allowed me to now successfully add a user using the ldap backend. My question is for getting keystone ldap to work from devstack should we just do this or am I hiding stuff under the rug and we really need to store the enabled attribute and thus we should add an extra objectClass to address this?18:14
*** davidh_ has quit IRC18:14
dolphmbp additional-endpoint-metadata  https://review.openstack.org/#/c/20075/18:14
dolphmheckj: will do18:14
dolphmheckj: topol: i imagine we want to A) have a conventional way to store the enabled attribute, B) demonstrate that convention in devstack18:15
topolso enabled is giving me trouble for both add user and add tenant18:15
dolphmtopol: how so?18:16
*** dwchadwick has joined #openstack-meeting18:16
topolBoth do not currently include an objectclass that has a good place to map the enabled value to that i know of18:17
topolfor AddUser what attribute of InetOrgPerson should I use for enabled?18:17
*** stevebaker has joined #openstack-meeting18:18
dolphmtopol: do you have a suggestion for what to use?18:18
dwchadwickYou can invent your own boolean attribute and object class, call it a Keystone related name18:18
topolSame question for addTenant18:18
topolWas hoping folks knew of an existing one. Otherwise I will invent my own. But wanted to check with you all first18:19
dwchadwickEg. Enabled attribute syntax boolean. Keystone Object class must contain Enabled attribute18:19
dolphmtopol: i'd say invent your own and work it out in code review, if anyone has a better solution18:19
*** Mandell has joined #openstack-meeting18:20
topolK. I will do it as dwchadwick recommends.  I'll open it as a bug on devstack cause thats where my changes will go.  THANKS!18:20
dolphm(i'm stepping away from my desk for now -- will hopefully be back before the official meeting end time)18:20
heckjtopol: sounds like a plan.18:21
heckj#topic keystoneclient or openstackclient support18:21
*** openstack changes topic to "keystoneclient or openstackclient support (Meeting topic: keystone)"18:21
henrynashheckj: I put this on18:22
heckjNot sure who/what this topic is specifically about - anyone have th detail?18:22
*** reed has joined #openstack-meeting18:22
heckjAll yours18:22
henrynashjust wanted to get some clarity…we have Steve on I think who is working on adding v3 cli support18:22
stevemaryes, currently adding v3 support to openstackclient18:23
henrynashthe intention had been to do this in the openstackclient , rather than update the keystone specific cleint18:23
henrynash…put impression from Dean is that the openstackclient is on a different schedule, maybe not be shipped with the main Girzzly release etc.18:23
henrynashdid we get the correct impression, or did we misread that?18:24
heckjyou got the correct impression.18:24
henrynashhence…do we need a cli v3 client for keystone at Grizzly release?18:24
heckjThe clients in general are all on their own cycle, with the intention (unfortunately, more than the reality) that they always maintain backwards compatibility18:24
heckjWe *don't* need it - but it would be nice. At a minimum, I we need keystoneclient to support the same V3 auth, but that's more about our integration testing across both sides than an otherwise specific need.18:25
henrynashheckj: would it be beneficial if we gave the keystone client some v3 cli capability?18:25
gyeephew! I was think we have to hookup the auth apis for keystoneclient by 21st :)18:25
heckjThat said, we won't get uptake without clients supporting the API18:25
heckjhenrynash: absolutely18:25
heckjgyee: you may find you have to anyway to do the full cycle testing18:26
henrynashheckj: so Steve and others are ready to pitch in and try and add this to keystone client if this would help18:26
heckjwe won't be able to get V3 enabled in devstack until the client fully supports it, and that will be the next large critical step to getting it accepted as the new API18:26
gyeeI can definitely use some help on the keystoneclient side18:26
gyeeright now I am just adding tests for keystone only18:27
heckjhenrynash: stevemar: that help would be very, very welcome!18:27
*** martine has quit IRC18:27
stevemargyee: i'm able and willing18:27
topolgyee, we will have Gordon Chung connect with you to help18:27
henrynashheckj: ok, sign us up18:27
heckj#topic open conversation18:27
*** openstack changes topic to "open conversation (Meeting topic: keystone)"18:27
topol(and Steve) :-)18:28
heckjer, unless you've more there Henry?18:28
henrynashheckj: nope, that's it18:28
henrynashso one, thing for open discussion: we need to pull in the oslo policy engine18:28
henrynash…and then really take a close look at what a v3 policy.json file will likely look at and makes sure er think a customer could control the api in a sensible fashion18:29
henrynashI'll take that if nobody else wants to :-)18:30
heckjhenrynash: yeah, makes sense18:30
dwchadwickthere is a standard json api for a policy engine recently been released by the XACML group18:31
dwchadwickwe should consider using this18:31
dwchadwickIf this is going to become the standard api for policy engines then we would be silly to reinvent our own18:32
henrynashdwchadwick: sounds like the route to that would be for the oslo team to consider it and then we would pick it up if it gets endoresed18:32
dwchadwickwe already use the XACML XML api for our policy engine18:32
dwchadwickWe are going to migrate our policy engine to this api anyway18:33
*** gordc has joined #openstack-meeting18:33
dwchadwickI guess I should get in touch with the oslo team. How do I contact them18:33
henrynashheckj: ?18:33
heckjdwchadwick: how different are the implementations and semantics of the policy engines? If there's a huge mismatch, we're looking at a lot of work to make it fit on top of the effort of changing across all of openstack18:34
heckjoslo team lead is effectively markmc (Mark McLoughlin - probably just mangled his name) - would ask on #openstack-dev for him (he's in dchadwick's timezones) or scan through the mailing list18:35
*** dolphm has quit IRC18:35
*** cp16net is now known as cp16net|away18:35
*** adjohn has joined #openstack-meeting18:35
*** anniec has quit IRC18:36
*** anniec has joined #openstack-meeting18:37
*** emagana has quit IRC18:37
*** emagana_ has joined #openstack-meeting18:37
dwchadwickI will do this, thanks18:37
*** adjohn has quit IRC18:37
heckjhenrynash: how familiar are you with devstack?18:37
henrynashheckj: fyi, we have a discussion going on regarding whether we can feed filter attributes into the policy engine18:37
*** adjohn has joined #openstack-meeting18:37
heckjdwchadwick: sounds good - looking forward to hearing the latest18:37
topolheckj: I know a little devstack18:38
henrynashheckj: oops, sorry crossed questions18:38
*** emagana_ has quit IRC18:38
heckjno worries18:38
henrynashheckj: tool probably knows more than me :-)18:38
topolhenrynash, in US english calling someone a tool is an insult :-)18:39
*** alexpilotti has quit IRC18:39
dwchadwickhe took the p out of you ;-)18:40
topolHe must know me :-)18:40
*** dolphm has joined #openstack-meeting18:40
henrynashheckj: idea is that if someone does, e.g. GET /users?{domain_id="my domain"}  can we ensure the policy engine will let us protect this call by whether I have a domain scoped token to "my domain"18:40
henrynashtopol: oops, sorry, good thing I do know you :-)18:40
henrynashthe sound of silence…..18:42
heckjsorry - in two meetings at once - back in a sec18:42
dwchadwickthe whole issue of access control to the policy engine is an interesting one, because you could easily introduce recursions (policy controling access to policy engine ;-)18:42
dwchadwickOut of interest, who is allowed to call the policy engine18:44
heckjjumping back up the stack in my head - I think it's clear we want to be able to feed in additionla additbutes into the policy engine to let it work against that additional set of data18:45
henrynashdwchadwick: so each service calls the policy engine with a) the details of the request and b) details extracted from the token provided by the caller18:45
heckjdwchadwick: the policy engine is called by each of the services - they "own" their  authroization, and use the common library to enable it18:46
dwchadwickbut what is to stop me using a client to call the same API?18:46
henrynashdwchawick: it is not exposed18:46
dwchadwickbut it exists at some URL.18:47
henrynasherrr, don;t think so18:47
dwchadwickso its not a RESTful API18:47
dwchadwickThe XACML json api is restful I believe18:47
henrynash(correct me anyone if I have this wrong_ but its a private call internal to each serbice18:47
heckjit's not a restful API, it's a python API internal to the services18:48
henrynashdwchadwick:….and not everyone has the same version of the policy engine….yet18:48
*** hemna has quit IRC18:48
dwchadwickOk understood. Then perhaps the oslo team wont be so keen on the XACML approach18:49
henrynashdwchadwick: I would not assume that18:49
*** christophk has quit IRC18:49
heckjpretty much everything the oslo team is doing it python libraries in use by multiple services, but I don't think anything's really off the table18:49
henrynashpolicy engine as  a new OS service?18:49
*** markmcclain has joined #openstack-meeting18:49
dwchadwickwhat we have done is SSL enabled the link to the policy API so that only trusted clients can call it18:50
*** egallen has quit IRC18:50
henrynash(hmmm…but it needs to be fast as it is called inline as part of every call)18:50
*** dosaboy has quit IRC18:50
dwchadwickI know. Ours is not fast, not when you do SOAP and XML and SSL18:51
*** markmcclain1 has joined #openstack-meeting18:51
*** markmcclain has quit IRC18:51
dwchadwickWe have a programmable API as well that is fast18:51
dwchadwickthis is more equivalent to the python call18:51
henrynashdwchadwick: probably...18:51
*** dosaboy has joined #openstack-meeting18:51
henrynashany other issues…don't want to hog the floor18:52
henrynash(probably a UK expression, that)18:52
dwchadwickJust to let you know that Kristy has almost finished implementing the federated keystone blueprint of Adam18:52
*** christophk has joined #openstack-meeting18:53
dwchadwickBut using our federation infrastructure instead of his kerberos like mechanism18:53
gyeehenrynash, have you give some thought into how to migrate the swift ACLs with <tenant name>:<username>?18:53
gyeeor *:<username>?18:53
henrynashgyee: so an initial review is that we might get away with it for now…..but still trying to get this confirmed..gyee/heckj: who would be the best person in swift to chat to?18:54
gyeeI implemented the cross-tenant ACLs :)18:55
heckjhenrynash: really good question18:55
gyeethe latest ones anyway18:55
*** davidh_ has joined #openstack-meeting18:55
heckjhenrynash: I'd suggest starting with chmouel - he has excellent cross knowledge there, but also worth just hopping to the top (jon dickinson)18:56
*** cp16net|away is now known as cp16net18:56
notmynames/jon/john/  ;-)18:56
heckjsorry notmyname18:56
henrynashheckj: thx18:56
dwchadwickJust located markmc@redhat.com  is this the Mark of oslo18:57
heckjthat's him18:57
gyeehenrynash, I am think to have authtoken middleware set the X-Domain-* headers if the domain is not the default domain18:57
notmynameat the last swift meeting, chmouel said he would be able to look in to the swift+keystone v3 and migration issues.18:57
henrynashnotmyname: great….either gyee or I can provide guidance18:58
gyeeand have Swift authorized on project@domain:username@domain if X-Domain-* is present18:58
henrynashgyee: not sure if we set X-Domain if it is a project token….18:58
gyeeotherwise, do it the old fashion way18:58
gyeewe should18:58
*** markmcclain1 has quit IRC18:59
heckjtime to wrap this up19:00
*** olaph has joined #openstack-meeting19:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"19:00
henrynashgyee: agree we could do it both ways: we just need to give clear guidance that if there is a project defined in the token then it is NOt domain scoped19:00
openstackMeeting ended Tue Feb 12 19:00:11 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)19:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-12-18.02.html19:00
heckjthanks all19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-12-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-02-12-18.02.log.html19:00
*** hemna has joined #openstack-meeting19:00
*** nachi has quit IRC19:00
*** nachi_ has quit IRC19:00
*** stevemar has left #openstack-meeting19:00
*** gordc has left #openstack-meeting19:00
*** brich1 has left #openstack-meeting19:01
*** dolphm has quit IRC19:01
*** kwss has quit IRC19:01
fungican haz infra meeting?19:02
*** heckj has quit IRC19:02
*** mawagon1 has joined #openstack-meeting19:02
fungihey pleia2! clarkb? jeblair? zaro?19:02
clarkbzuul distracted me19:03
fungihe does that19:03
* clarkb votes fungi runs the meeting today since he is paying attention to things19:03
* zaro thinks good idea19:04
fungiahh, okay19:04
fungijust about proved you wrong there ;)19:04
fungi#startmeeting infra19:04
openstackMeeting started Tue Feb 12 19:04:34 2013 UTC.  The chair is fungi. Information about MeetBot at http://wiki.debian.org/MeetBot.19:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:04
*** openstack changes topic to " (Meeting topic: infra)"19:04
openstackThe meeting name has been set to 'infra'19:04
*** rnirmal_ has joined #openstack-meeting19:04
fungiWiki: Meetings/InfraTeamMeeting (last edited 2013-01-29 05:30:39 by JamesBlair)19:05
*** spzala has quit IRC19:05
*** olamalaf has joined #openstack-meeting19:05
fungii feel like i've seen this episode before19:05
*** olaph has quit IRC19:05
* fungi pulls up the action items list19:05
*** olamalaf is now known as olaph19:05
fungiclarkb start discussion on long term log archival options when jeblair gets back19:06
fungii guess that can happen now19:06
*** markmcclain has joined #openstack-meeting19:06
clarkbyes, sort of started it yesterday but not in much detail19:06
*** rnirmal has quit IRC19:06
*** rnirmal_ is now known as rnirmal19:06
fungiit's a jeblair!19:06
clarkbshould we have that discussion here and now?19:06
*** dwchadwick has quit IRC19:07
fungiup to you guys. the itenerary is short and mostly checkboxish19:07
clarkbmay as well then19:07
clarkbour test log growth is not linear19:07
fungito say the least19:07
*** mawagon1 has quit IRC19:07
jeblairso i was wondering how much logstash could be a complete replacement for statically storing logs19:08
clarkbhttp://cacti.openstack.org/cacti/graph.php?action=view&local_graph_id=309&rra_id=all you can see the curve at the bottom of that page19:08
jeblairand clarkb said it may not be a good one19:08
jeblairclarkb: can you elaborate on why?19:08
clarkbjeblair: logstash's purpose is to index and give quick access to your logs19:08
clarkbthis makes it a bad way to archive your logs19:08
jeblairclarkb: but doesn't it have a complete copy of them and present them to you through a web ui?19:09
fungiso it's only useful for recent/small log quantities i guess?19:09
clarkbyes, however if were to keep 100GB of logs in logstash I get the feeling we would need a much larger elasticsearch cluster to handle the increased workload19:09
*** Haneef has quit IRC19:10
clarkbI don't think we want to sacrifice index speed and usability for archival functionality19:10
jeblairclarkb: ok, so you're suggesting we maintain a smaller logstash system for searching the last x days of logs19:10
fungioh, guess i forgot to /topic19:10
fungi#topic log archival19:10
*** openstack changes topic to "log archival (Meeting topic: infra)"19:10
jeblairclarkb: and keep 6 mos of logs in a static setup?19:11
jeblairclarkb: (it's easy to delete >x days of logs from logstash?)19:11
clarkbthe way logstash is configured to index by default suggests that this is the normal operating behavior (each day gets its own index and you want to keep the number of indexes down)19:11
clarkbjeblair: yes and yes. To make deleting logs from logstash easy you set it to use a timebased index of some sort19:11
*** markmcclain1 has joined #openstack-meeting19:11
clarkbjeblair: then you have a cron or similar look for old indexes and delete them19:12
*** Yada has quit IRC19:12
jeblairclarkb: so for the zuul reports in gerrit, we'd probably need to link to the static archiving solution19:12
jeblairclarkb: since the logstash one will disappear19:12
clarkbjeblair: I think so. But probably with a note that you can search recent job runs in logstash and link to logstash19:13
jeblairbut maybe we can link to logstash from the static reports19:13
fungiand so we'll still need some separate interface to anonymously browse older archived logs. does cloudfiles have that built in?19:13
*** novas0x2a|laptop has quit IRC19:13
jeblairyeah, we're relying on the apache mod_index for that now19:13
*** markmcclain has quit IRC19:14
jeblairi don't think there's such a thing for cloud files19:14
mordredmaybe notmyname has something ...19:14
jeblairnotmyname, mordred?19:14
notmynamejust saw my name19:14
mordrednotmyname: last 8 lines of scrollback - discussing putting build logs in swift - wondering about indexes19:14
jeblairnotmyname: http://logs.openstack.org/21691/1/check/gate-tempest-devstack-vm-full/2081/19:15
*** salv-orlando_ has joined #openstack-meeting19:15
notmynameif you use the pseudo directory naming structure I suggested yesterday (to clarkb?), then you have listing support19:15
*** adjohn_ has joined #openstack-meeting19:15
notmynamecombined with staticweb (which cloud files supports), you can even get "pretty" web pages19:15
jeblairnotmyname: oh, so if you GET a .../job-id/ url, you get an index page?19:16
notmynamejeblair: ya, it can be configured to do so19:16
jeblairnotmyname: cool, that sounds like exactly what we need then19:16
ttxyay cloud19:17
jeblairso we should be able to use jclouds to put these things in cloud files...19:17
fungihave we exhausted that topic for the moment? action items coming from it?19:17
clarkbthe second thing we need to sort out is having jenkins use swift the logs. in theory we can rely on jclouds for that. in practice clarkb had a bad experience last week19:17
*** mawagon1 has joined #openstack-meeting19:17
fungiahh, right19:17
jeblairthen clarkb can watch the zeromq stream to fetch those things and shove them in logstash19:17
fungiyou said there was a patch forthcoming from jclouds19:17
*** lbragstad1 has joined #openstack-meeting19:17
jeblairclarkb: oh :(, what's the skinny on that?19:18
clarkbthe current release of the jclouds plugin is broken for blob storing. this has been fixed in master.19:18
clarkbsecond that fixed commit dumps your cloud key/password to the console log when it gets a 401 from the cloud provider19:18
*** dosaboy1 has joined #openstack-meeting19:18
*** dprince_ has joined #openstack-meeting19:18
clarkbthere is a potential fix for that at the tip of master but i have yet to find time to test it19:18
jeblairmy experience suggests that errors from cloud providers are frequent.19:18
fungioh, right. lots of notfun in that19:18
clarkbso we will just need to be careful and defensive about how we test the jclouds blobstore19:19
clarkbabayer in #jclouds has been super helpful though19:19
jeblairclarkb: yeah, we don't need to rush this.  :)19:20
fungiwe now have more space at least19:20
*** martine has joined #openstack-meeting19:20
*** bencherian has quit IRC19:21
fungiokay, so next action items, or was there more on that one?19:21
*** enikanorov has quit IRC19:22
jeblairfungi: i'm good19:22
clarkbI think that is it19:22
*** enikanorov has joined #openstack-meeting19:22
fungi#topic wiki stuffs19:22
*** openstack changes topic to "wiki stuffs (Meeting topic: infra)"19:22
mordredmoin sucks19:22
* annegentle waves19:22
* annegentle agrees with mordred 19:22
funginext action items were the date change to saturday and annegentle sending an updated announcement?19:22
annegentlefungi: I wasn't sure if the date really changed so I didn't send anything :)19:23
jeblairto answer annegentle's question in email, no, i'm not critical.  :)19:23
mordredjeblair is so critical19:23
fungiso then it's sticking with sunday after all?19:24
*** markmcclain1 has quit IRC19:24
*** olaph has quit IRC19:24
*** dosaboy has quit IRC19:24
*** adjohn has quit IRC19:24
*** lbragstad has quit IRC19:24
*** dprince has quit IRC19:24
*** salv-orlando has quit IRC19:24
*** salv-orlando_ is now known as salv-orlando19:24
pleia2ryan confirmed saturday was ok19:24
*** mawagon1 is now known as olaph19:25
jeblair(i'm so sorry!)19:25
clarkbyeah we are saturdaying19:25
clarkbannegentle: oh, you didn't get the email from ryan? I completely missed that this didn't go out19:26
clarkbmy bad19:26
fungiso if it's saturday, then we need a last-minute update announcement i guess19:26
annegentleclarkb: ohh ok19:26
annegentleyeah that's how I missed it19:26
annegentlesure, I'll send now19:26
fungiannegentle: thanks!19:26
fungiso who all is planning to be around for the cut-over on saturday then?19:27
* jeblair plans to be around19:27
mordredyeah. me too19:27
olaphshould be19:27
pleia2not me (I'll be out of town for the holiday weekend)19:27
* ttx will probably be jetlagged but ~present19:27
fungi#action jeblair, clarkb, olaph, Ryan_Lane, mordred, annegentle, ttx, fungi work on wiki upgrade 2013-02-1619:28
fungiany other wiki-related notes while we're on the topic? we're missing a Ryan_Lane in here i guess19:28
* mordred just saw Ryan_Lane an hour ago - he was leaving on his way to work ...19:29
fungiwe can catch up with him later in the week if there are last-minute issues i suppose19:29
* zaro is out of town.19:29
fungi#topic python-swiftclient upload19:30
*** openstack changes topic to "python-swiftclient upload (Meeting topic: infra)"19:30
fungimordred to upload python-swiftclient 1.3.019:30
fungithat happened, right?19:30
fungiokay. that's it for old business19:30
mordredI used the jenkins jobs too - so they have been tested19:30
funginew business...19:30
fungi# cla19:30
fungi#topic cla19:31
*** openstack changes topic to "cla (Meeting topic: infra)"19:31
*** gyee has quit IRC19:31
mordredfunny - we're just now talking about CLAs at the board meeting19:31
fungino real news on the cla stuff. basically ready, pending last minute reviews (i'll hit people up in the next week for reviewing after a rebase)19:31
jeblairat LCA we chatted with notmyname about it, and realized he was unaware of the change...19:31
fungistill on track for 2013-02-24 cut-over19:31
jeblairmordred: are we getting rid of CLA? ;)19:32
*** dolphm has joined #openstack-meeting19:32
*** mawagon1 has joined #openstack-meeting19:32
mordredjeblair: nope19:32
clarkbjeblair: fungi should we send another announcement to the mailing list?19:32
jeblairso we discussed that we sholud do some extra communication...19:32
jeblairprobably in a different form19:32
fungiyes, agreed19:32
mordredyeah. more specific19:32
mordredless explanatory19:32
mordred"you will need to resign the CLA on X"19:32
jeblairttx: can you make sure the PTLs are all aware of this at the project meeting?19:32
ttxjeblair: sure19:32
fungi#action fungi draft and send more explicit/cautionary announcement about cla cut-over19:32
fungi#action ttx discuss cla at next project meeting19:33
jeblairwe can ask lauren/stef to use blog/community newsletter/etc to disseminate it as well19:33
ttxfungi: any chnace you cna send that before the meeting, so that I can reference your post ?19:33
fungi#action fungi hit up infra core team for reviews19:33
fungittx: sure19:33
fungiremind me when the project meeting happens?19:33
fungii can look it up if necessary19:33
fungii can join in when that topic comes up too19:34
*** mattray has quit IRC19:34
jeblairfungi: then maybe pass that announcement to lauren and stef for them to process19:34
*** olamalaf has joined #openstack-meeting19:34
*** davidh_ has quit IRC19:34
*** olaph has quit IRC19:34
fungijeblair: awesome. sounds like a great idea19:34
jeblairfinally, there's one other option we should consider: we _could_ email everyone in gerrit.19:34
fungii'm a little edgy about that19:35
jeblairi _think_ the other things we've discussed should be enough...19:35
mordredthey'll notice whenthey go to upload something19:35
jeblairso i'd propose that we do those, and only if we still think no one knows about it a week before the cutover, should we spam.19:35
jeblair(regardless, we should send at least one more announcement closer to the cutover)19:36
jeblair(ml, i mean, not spam)19:36
*** darraghb has quit IRC19:36
*** davidh_ has joined #openstack-meeting19:36
fungiwiki tells me the project/release meeting is Tuesdays at 2100 UTC so i'll see about getting that announcement to the -dev ml in the next hour after this meeting19:36
*** mawagon1 has quit IRC19:36
fungiif that's what ttx was suggesting19:36
jeblairmordred: indeed, i think that's a reasonably mitigating factor.  the error has its own instructions for rectification.19:37
ttxotherwise I'll just point to the date19:37
fungiyes. the error messages are quite explicit19:37
fungiurls and all19:37
*** AndroUser2 has joined #openstack-meeting19:37
fungiokay, anything else on cla stuff?19:38
*** mattray has joined #openstack-meeting19:38
*** dolphm has quit IRC19:38
fungi#topic jenkins slave operating systems19:38
*** openstack changes topic to "jenkins slave operating systems (Meeting topic: infra)"19:38
*** markmcclain has joined #openstack-meeting19:38
*** sdake_z has joined #openstack-meeting19:38
fungii think we covered a couple items under this topic umbrella previously... jclouds and quantal19:38
fungiquantal is working for static slaves but i'm having trouble with jclouds'ing it. asked on #jclouds but nothing too helpful yet19:39
fungishort story is i can launch slaves from jclouds with the ubuntu version specified as 11.10 or 12.04, but if i change that to 12.10 i get an immediate java exception about not matching any images19:40
fungiso i think it's an image metadata issue in rackspace at this point19:40
*** olaph has joined #openstack-meeting19:40
fungialso jclouds-related, clarkb: you had some issues with slaves not deleting right?19:41
fungifungi@ci-puppetmaster:~$ nova list|grep -c jclouds19:41
clarkbso yeah19:41
fungii don't see anywhere near that many in jenkins (like maybe only 1)19:41
ttxfungi: 1h20min from now19:41
fungittx: yep. thanks! i checked the wiki pretty much immediately anyway19:42
* ttx is answering asynchronously19:42
jeblairprobably the same thing we work around in devstack-gate...19:42
*** AndroUser2 has quit IRC19:42
jeblairnova returns a 200 for the delete api call and then does not delete the server19:42
fungithat's pretty neat19:43
jeblairsome how this is apparently not a bug19:43
fungis/bug/money making opportunity for providers/19:43
jeblairexcept in our case.  :/19:43
*** olamalaf has quit IRC19:43
fungianyway, if there's nothing much else on that, we should probably jump into devstack/tempest/gating changes et cetera19:44
fungi#topic devstack, tempest and gating changes19:45
*** openstack changes topic to "devstack, tempest and gating changes (Meeting topic: infra)"19:45
ttxnotabug: "Empowering the ecosystem"19:45
fungittx: heh19:45
*** dolphm has joined #openstack-meeting19:45
jeblairenriching the ecosystem19:45
*** otherwiseguy has quit IRC19:45
*** novas0x2a|laptop has joined #openstack-meeting19:45
fungiokay, so there's been some more improvements to test scope, runtimes and also proposed efficiency improvements for the gating pipeline?19:45
fungianyone want to discuss high points on that?19:46
jeblairfungi: is 'efficiency improvements' https://review.openstack.org/#/c/20948/  ?19:46
fungijeblair: that looks like one of them19:47
*** eglynn has joined #openstack-meeting19:47
jeblairfungi: another?19:47
fungiclarkb: also has a wip one i think19:47
fungiand we just put something through to make expensive tests dependent on cheap ones19:47
*** markvan has joined #openstack-meeting19:47
fungithough only for the check pipeline, not gate19:48
jeblairfungi, clarkb, link?19:48
jeblairto clarkb's change19:48
* fungi is looking19:48
jeblairi saw mordred's pep8 change19:48
fungi#link https://review.openstack.org/2172319:48
*** almaisan-away is now known as al-maisan19:49
jeblairmordred: for https://review.openstack.org/#/c/21267/19:49
jeblairmordred: what problem does that solve?19:49
clarkbjeblair: https://bugs.launchpad.net/zuul/+bug/112332919:50
uvirtbotLaunchpad bug 1123329 in zuul "Zuul should remove unmergable changes from queue as soon as possible." [Undecided,New]19:50
jeblairclarkb: i like the sound of that19:51
clarkbjeblair: with the increased gate time per change unmergable changes end up serializing zuul more than is necessary19:51
fungii believe the idea behind 21267 was to avoid burning slave time on tempest tests (which are upwards of an hour or two at this point) if the tests which take <5 minutes don't pass anyway19:51
jeblairfungi: yeah, but we're not running low on devstack/tempest slaves, yeah?  and with jclouds, it seems like we shouldn't be running low on regular slaves either, in general...19:52
jeblairfungi: so what that change does is optimize for the case where pep8 fails19:53
jeblairit means that if your change fails pep8, the devs are notified very early19:53
clarkba lot of changes fail pep819:53
jeblairbut if your change passes pep8, it now takes runtime(tempest)+runtime(pep8) to be notified19:53
fungior pyflakes in some cases, but yes. more generally it was to avoid long-running tests if the patch isn't syntactically correct python (style checks are just a bonus there)19:54
jeblairyeah, i'm just wondering why that's desirable -- it is because we want to notify people that changes fail pep8 fast (at the cost of making successful changes take _longer_ to notify)19:54
jeblairor is it to solve a slave resource contention problem19:54
fungiand we're still running short on static slaves for the moment, until jclouds is in better shape19:55
mordredthe devs who were chatting with us (sdague was an active one) didn't seem to mind the extra 5ish minutes compared to getting the reject quicker19:55
clarkbI see it as reducing unnecessary load on the slaves and to encourage devs to run tox -epep8 before pushing19:55
clarkbjenkins is becoming everyones personal test box19:55
mordredalternately ... it might be interesting to add a feature to zuul to cancel and dequeu remaining jobs if one of them fails19:56
jeblairyeah, though looking at the zuul queue, the static slave tests are running ahead of the devstack tests, which is the main thing19:56
mordredwhich could get us to a place where we get the canary benefit without the serialization concern from jeblair19:56
jeblairmordred: yeah, that's kind of where i was heading19:57
fungiwe wind up starving the gate pipeline of available static slaves under heavy activity periods right now, and at least a significant percentage are spinning on failed unit tests for the check pipeline19:57
*** mawagon1 has joined #openstack-meeting19:57
*** bencherian has joined #openstack-meeting19:57
fungiso yes, anything to help that situation would be an improvement19:57
*** stevebaker has quit IRC19:57
jeblairmordred: we wanted to return as much info to devs as quickly as possible19:58
jeblairmordred: i think that's still desirable19:58
*** olamalaf has joined #openstack-meeting19:58
mordredI agree19:58
jeblairmordred: but clarkb has a good point that people are just throwing shit at jenkins and seeing what sticks19:58
jeblairadmittedly, he didn't quite put it like that.  but i will. :)19:58
fungiand we're about out of time19:59
*** markmc has joined #openstack-meeting19:59
mordredright. which is why I think early fail in check queue is helpful19:59
jeblairso anyway, yeah, let's think about short-circuiting the whole test run if some tests fail19:59
pleia2real quick, I made a wiki page: http://wiki.openstack.org/InfraTeam19:59
jeblairbut still start them all in parallel19:59
ttxjeblair: +120:00
ttxat leas tfor gate20:00
fungi#topic general20:00
*** openstack changes topic to "general (Meeting topic: infra)"20:00
fungi#link http://wiki.openstack.org/InfraTeam20:00
mordredjeblair: agree20:00
pleia2thanks fungi20:00
*** heckj has joined #openstack-meeting20:00
fungithank you pleia2!20:00
*** olaph has quit IRC20:00
*** stevebaker has joined #openstack-meeting20:00
fungiokay, i'll go ahead and shut this down so ttx can have the channel for tc20:01
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"20:01
openstackMeeting ended Tue Feb 12 20:01:05 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-02-12-19.04.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-02-12-19.04.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-02-12-19.04.log.html20:01
ttxI realize now that these two meetings are actually ruining lunch time20:01
*** mawagon1 has quit IRC20:01
ttxWho is around for the TC meeting ?20:01
mordredttx: o/20:01
sdake_zsdake here20:01
jeblairttx: yes, it takes special planning.20:01
ttxmarkmc, heckj, annegentle, russellb, bcwaldon, jgriffith, vishy, gabrielhurley, danwent: around ?20:01
*** jpeeler has quit IRC20:02
*** jpeeler has joined #openstack-meeting20:02
ttxso we are still missing... annegentle, danwent, gabrielhurley20:02
ttxok, let's get started, Gabriel should join us soon20:03
*** maurosr has quit IRC20:03
ttx#startmeeting tc20:03
openstackMeeting started Tue Feb 12 20:03:34 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:03
*** openstack changes topic to " (Meeting topic: tc)"20:03
openstackThe meeting name has been set to 'tc'20:03
ttxAgenda for today:20:03
ttx#link http://wiki.openstack.org/Governance/TechnicalCommittee20:03
ttx#topic Special motion on Incubation process evolution20:04
*** openstack changes topic to "Special motion on Incubation process evolution (Meeting topic: tc)"20:04
ttxAs discussed last week, we followed a bit of formality to make sure we were in line with the joint committee20:04
ttxSo we worked on with a set of changes to the incubation process and charter wording based on the work on the joint committee20:04
ttxThe joint committee approved that set and recommends that the TC now approves it20:04
*** joesavak has joined #openstack-meeting20:04
*** gabrielhurley has joined #openstack-meeting20:04
ttxIt's the same text that was posted to openstack-tc and openstack-dev and didn't trigger any comment on any list afaict20:04
*** Mr_T has joined #openstack-meeting20:04
gabrielhurleysorry I'm late20:05
ttxjust warming up20:05
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-February/005421.html20:05
markmcand it closely matches what the TC agreed back in november20:05
ttxOne important thing to note is that this motion doesn't prevent future changes as the joint committee makes further progress in defining "core" and the process around it20:05
markmci.e. the mandate for the TC reps on in the committee20:05
ttxIt just updates our process and texts to the current thinking so that we know how to proceed in the immediate future for projects currently in incubation20:05
ttxThis is a special motion since it requires wording changes to our Charter to introduce the concept of "Integrated" project20:05
ttxSo we need 9+ "Yes" for this to be approved20:06
ttxComments before we vote ?20:06
*** jsavak has quit IRC20:06
gabrielhurleyis that a vote or a comment? ;-)20:06
notmynamecomment on item 6 in the email20:06
ttxremoval of the "TC recommends core" sentence20:07
*** vipul is now known as vipul|away20:07
notmynamethis removes the TC from involvement in what is considered "openstack", at least to the external world. currently the BoD takes input from the TC on this. this clause seems to remove that20:07
ttxnotmyname: So this point was raised because that would be the only place where "core" is mentioned in our charter20:08
ttxonce we replace other mentions by "integrated"20:08
markmcwe know the TC's involvement isn't going to be "the project is graduating, we recommend it for core"20:08
markmcthere will likely be some other involvement20:08
ttxIt doesn't make any assumption on how the core process will evolve20:08
markmcmaybe the BoD asking for our opinion on specific technical matters20:08
markmcbut we can add that to the charter later when we know what it should be20:08
ttxyeah, we just don't know how much we'll be involved20:09
mordredor - the BoD might come back with a core process that specifically empowers the tc in additional ways20:09
ttxI'm fine with leaving that in... it's just inaccurate because we have no idea20:09
*** troytoman-away is now known as troytoman20:09
ttxso I figured we should remove it to reflect the fac tthat we don't have any process defined for "core" yet20:09
ttxrather thah leaving it in and imply we still have one20:09
annegentlettx: I wonder if you could just remove the word "Core" but still show the TC involvement in status changes20:10
ttxWhat's the others opinions on that ?20:10
jaypipesttx: I'm fine with the removal of that sentence.20:10
jaypipesttx: per my change of heart wrt the whole pointlessness of the "core" label.20:10
markmcI'd prefer it to be removed, but it's the least important part of the motion20:11
jgriffithttx: I'm fine with removing it as well for the same reasons noted by jaypipes20:11
ttxannegentle: you mean "recommends projects for status changes" ? That would also be a bit presomptuous, but why not20:11
annegentlettx: aim high20:11
vishyI'm fine with it being removed.20:11
russellbfine with me too20:12
*** olaph has joined #openstack-meeting20:12
annegentleremove "Core" or the entire sentence?20:12
ttxI think it makes more sense to remove it and update that again when we know what the joint committee and the BoD want to do with "core"20:12
ttxso I prefer to leave point 6 in, personally20:12
ttxannegentle: the entire setence20:13
jaypipesttx: ++20:13
annegentlettx: I'm amenable to removing the whole sentence and update later20:13
ttxOK, let's have a try at this, then20:13
ttxany other comment before we vote ?20:13
jaypipespugs are awesome.20:14
ttx#startvote Approve special motion on incubation process evolution? yes, no, abstain20:14
openstackBegin voting on: Approve special motion on incubation process evolution? Valid vote options are yes, no, abstain.20:14
openstackVote using '#vote OPTION'. Only your last vote counts.20:14
markmc#vote yes20:14
*** shardy has joined #openstack-meeting20:14
ttx#vote yes20:14
russellb#vote yes20:14
gabrielhurley#vote yes20:14
jaypipes#vote yes20:14
heckj#vote yes20:14
jgriffith#vote yes20:14
annegentle#vote yes20:14
vishy#vote yes20:14
mordred#vote yes20:14
*** olamalaf has quit IRC20:15
notmyname#vote yes20:15
danwent#vote yes20:15
bcwaldon#vote yes20:15
ttx30 more seconds20:15
openstackVoted on "Approve special motion on incubation process evolution?" Results are20:16
openstackyes (13): markmc, bcwaldon, ttx, notmyname, vishy, annegentle, heckj, jaypipes, russellb, jgriffith, mordred, gabrielhurley, danwent20:16
ttxawesome, so now the next agenda item doesn't look s oweird20:16
ttx#topic End-of-cycle graduation review20:16
*** openstack changes topic to "End-of-cycle graduation review (Meeting topic: tc)"20:16
*** joshuamckenty has joined #openstack-meeting20:17
ttxwe can start with the end-of-cycle graduation review now. This needs to be completed before the end of the month.20:17
ttxIt was proposed that we could start with "Why we think we're ready" statements from Ceilometer and Heat20:17
ttxThen a report on release cycle alignment progress20:17
ttxThen assessments of technical stability and architecture maturity (probably next week)20:18
ttxAnd finally a check of scope to ensure the complementarity we judged at incubation time is still present20:18
ttxAnything more you'd like to see considered/discussed in that review process ?20:18
ttxNote that the process might get influenced by future progress on the joint committee. Like if the BoD defines the outer limits of openstack and what we should be focusing resources on20:19
ttxIs that process looking good for everyone ?20:20
*** mawagon1 has joined #openstack-meeting20:20
heckjgood by me20:20
*** cp16net is now known as cp16net|away20:20
*** AndroUser2 has joined #openstack-meeting20:20
russellbquestion on outer limits of openstack ... that putting bounds on what we can include in coordinated release?20:20
markmcrussellb, I don't think the BoD can do that20:21
markmcrussellb, it can recommend, but ..20:21
russellbi didn't think so either20:21
ttxrussellb: That could happen, I think. They could say that "openstack" is not doing GMail clones20:21
russellbjust trying to interpret ttx's comment20:21
ttxso a project that proposes that could be refused on that ground, maybe20:21
mordredttx: how about let's not spend a lot of time thinking about what might could be decided in the future20:22
jgriffithmordred: +120:22
russellbk, i'm not actually worried, so we can move on20:22
ttxyeah, that's a bit of astroturfing20:22
*** olaph has quit IRC20:22
ttxhandling the present is hard enough20:22
ttx#topic "Why we think we're ready", Ceilometer20:22
*** openstack changes topic to ""Why we think we're ready", Ceilometer (Meeting topic: tc)"20:22
ttxnijaba: floor is yours20:22
nijabafor ceilometer it is at: http://wiki.openstack.org/Ceilometer/Graduation20:22
ttxcould you summarize for those who can't read ?20:23
nijabado you want me to copy paste?20:23
nijabayes, we think we are ready20:23
sandywalsh_ugh, sorry20:23
*** gyee has joined #openstack-meeting20:23
nijaba    Robust multi purpose architecture recently extended to support multiple publishing channels, thus allowing ceilometer to become a metrics source for other tools apart from metering20:24
nijaba    Successfully passed the challlenge of being adopted by 3 related projects which have agreed to join or use ceilometer:20:24
nijaba        Synaps20:24
nijaba        Healthnmon20:24
nijaba        StackTach20:24
nijaba    Delivered Folsom within 2 weeks of release, prior to incubation20:24
nijaba    Successfully delivered the G2 milestone aligned with the overall project release cycle20:24
nijaba    Good integration with all core projects now, including Swift20:24
nijaba    Built up a diverse and sustainable core developer community, affiliated to multiple organizations20:24
nijaba    Followed openstack community best practices from the outset20:24
nijaba    Deployed at many sites20:24
*** olaph has joined #openstack-meeting20:25
notmynamenijaba: is the goal of ceilometer to provide monitoring info or usage info (eg for billing)?20:25
nijabanotmyname: used to be focused on metering, now expanded to metrics in general20:26
nijabathat was a conclusion of the last summit20:26
nijababased on request from other project to not have to duplicate our efforts20:26
bcwaldonnijaba: instantaneous metrics, or eventual?20:27
*** mawagon1 has quit IRC20:27
notmynamenijaba: I ask because my understanding (could be incorrect) is that you seem to be doing metering, but promising usage. those have very different requirements20:27
nijababcwaldon: eventual, each subscriber can set a frequency independentl of others20:27
*** Zehicle_at_Dell has joined #openstack-meeting20:28
gabrielhurleyYou've got the statement "There are still some aspects of the architecture that are still emerging (such as database schemas for metadata/rich data and aggregation)" in that wiki page... could you talk a little about your schema and what you're facing since that's a significant challenge you've described?20:29
eglynn"eventual" could equal a 60s measurement cadence for example20:29
sandywalsh_bcwaldon: and instantaneous is possible with UDP notifiers that dragondm is working on (for statsd-like integration)20:29
gabrielhurleysandywalsh_: nice. I was gonna ask about that too.20:30
nijabagabrielhurley: the question that is being discussed is regarding how we do indexing and what to index.  the content will not chnage20:30
*** otherwiseguy has joined #openstack-meeting20:30
ttxsandywalsh: are you happy with ceilometer architecture now ? i.e. you won't make them rewrite everything over the H cycle ?20:30
*** MarkAtwood has joined #openstack-meeting20:31
ttxI see StackTach is mentioned above20:31
sandywalsh_ttx: I think we've identified the main areas of contention (metadata on metrics and how roll-ups will be done) ... we still need to pin down a solution, but CM is pretty flexible currently20:31
sandywalsh_I can't imagine a radical fork-lift change20:31
ttxsandywalsh: thx, good t oknow20:31
dragondmBTW, bp for the udp notifications: https://blueprints.launchpad.net/oslo/+spec/lightweight-notifications-driver   I will be fleshing out the spec momentarily.20:32
*** mawagon1 has joined #openstack-meeting20:32
ttxOK, any more question on that "why we think we are ready" statement ?20:33
russellbare there any "competing" projects at this point?  or is everyone happily working together?20:33
nijabaI think we are all joined in a happy family ;)20:33
* jaypipes would like to see better packaging and coordination with QA/Tempest20:33
russellbnijaba: excellent20:33
mordredI'd like to point out how happy I am at all of the cross-project collaboration via ceilometer20:33
notmynameI'd like to hear more about the goals re monitoring vs billing20:34
ttxjaypipes: we can cover that in the technical assessment later20:34
heckjhas there been any additions into tempest to do full integration testing at this point (or is that expected post graduation)?20:34
nijabajaypipes: point taken. we'll discuss the details offline?20:34
eglynnjaypipes: distro-level packaging do you mean?20:34
jaypipeseglynn: ya20:34
*** maurosr has joined #openstack-meeting20:34
jaypipesnijaba: yup, no worries.20:34
*** cp16net|away is now known as cp16net20:34
nijabajaypipes: distro packaging should be our concern?20:34
jaypipesnijaba: working with the packagers...20:34
nijabaI thought otherwise.  We just need to enable it20:34
*** olaph has quit IRC20:35
nijabajaypipes: that we do quite a bit already20:35
mordredI do not think that distro packaging is our concern20:35
vishynotmyname: I don't thing "monitoring" has ever been a stated concern of ceilometer20:35
ttxheckj: it's a bit of chicken-and-egg problem, like horizon integration20:35
eglynnjaypipes: I'm working on Fedora packaging, zul has done work for deb/ubuntu20:35
notmynamevishy: except that's what it's doing, from what I can tell20:35
jaypipeseglynn: things like the mongodb dep, etc, and lack of folsom packaging are a concern.20:35
nijabaand zigo is working on the debian pkg20:35
sandywalsh_notmyname: and monitoring is a big bucket (is it just "watch" or "watch and react") ... I think the synaps guys are working on that front.20:35
heckjis there a solid API that can be used to provide horizon (or other dashboard) support to the data store?20:36
ttxvishy: I think they want to cover collecting monitoring data at this point20:36
eglynnvishy: a goal though is avoid monitoring tools having to duplicate measurements already taken by ceilo20:36
nijabathere are pkg for folsom on debian and ubuntu20:36
nijabaheckj: yes, and their is an horizon plugin beeing developped by brooklyn shen20:36
heckjnijaba: thanks20:36
nijabavishy: we don't want to do monitoring bu we want to allow collecting data for a monitoring tool as one of our publisher20:37
jaypipesnijaba: don't mind me.... just being nit-picky, really...20:38
*** vipul|away is now known as vipul20:38
Davieyjaypipes: It does seem all distro's are keen on it :)20:38
al-maisansandywalsh_: IMHO monitoring is typically watch, define thresholds and raise alarms, the react part is somewhere else..20:38
nijabavishy: thus avoiding duplication of collection, and avoiding to have to support everything through our metering db api20:39
jgriffithnijaba: So is it accurate to say the intent is "data collection" and leave it at that?20:39
sandywalsh_al-maisan: that's a reasonable perspective :)20:39
jgriffithnijaba: The monitoring/billing etc debate is what's had me a bit confused20:39
jaypipesal-maisan: ++20:39
nijabajgriffith: yes, with a possible extension to alerting20:39
jgriffithnijaba: k, thanks20:39
sandywalsh_jgriffith: RAX needs CM for SEC-compliant billing, it's our primary driver.20:40
*** AndroUser2 has quit IRC20:40
ttxOK, can we switch to Heat statement now, or are there more questions ? or questions unanswered ?20:40
*** dprince_ has quit IRC20:40
eglynnmain focus of the ceilo core IMO is on data (measurement) acquisition ... many potential down-pipeline uses of that data of course20:41
nijabaeglynn: right20:41
ttxWe can discuss scope and complementarity when we reach that point in the review20:41
heckjttx: I'm good20:41
ttxthough it's good for the ceilometer crew to know that's one of the hot zones20:41
sandywalsh_eglynn: +120:41
*** afazekas has quit IRC20:41
*** john5223 has joined #openstack-meeting20:42
ttxOK, let's examine Heat statement now...20:42
ttx#topic "Why we think we're ready", Heat20:42
*** openstack changes topic to ""Why we think we're ready", Heat (Meeting topic: tc)"20:42
sdake_zhi guys20:42
sdake_zfor those that dont like to click links :)20:42
sdake_zWe have followed the full OpenStack process for the entire G cycle20:42
sdake_zHeat has been in development for about 11 months. Our developers have learned to follow the openstack workflow while implementing a pure OpenStack style implementation of orchestration during the G cycle.20:42
sdake_zThere are many people evaluating Heat for field deployments20:42
sdake_zSeveral enterprises are waiting for a stable G release of Heat to begin deploying. Some of those folks such as HP are contributing blueprints and code to improve Heat's functionality.20:43
sdake_zWe have a growing user community20:43
sdake_zThe Heat IRC channel is growing rapidly and adding new developers. The mailing list traffic related to heat is increasing as well.20:43
sdake_zDeployments want heat functionality20:43
sdake_zLots of folks want an easy way to wrap all of the great OpenStack APIs into one template format. We provide value for these deployments and speed up deployment and development times20:43
sdake_zDevelopers are interested in Heat20:43
sdake_zWe have many blueprints scheduled for H submitted by community developers.20:43
sdake_zWe work with other core and non-core projects20:43
sdake_zWe currently work with all core projects including Nova, Cinder, Glance, Quantum, Keystone, Swift, and Horizon. We were an early adopter of Oslo, before it entered Nova or other projects. We also have interest in working well with Ceilometer and have contributed ideas and patches to implement some of our dependent functionality. Finally we are always looking for new projects to integrate with. An example of a new integration point20:43
sdake_zis Moniker which had a blueprint for G cycle but was deferred to H because of maturity problems with Moniker client libraries.20:43
sdake_zok thats it ;)20:43
ttxquestions ?20:44
*** apmelton has joined #openstack-meeting20:45
*** olaph has joined #openstack-meeting20:45
*** olaph has left #openstack-meeting20:45
ttxsdake: roughly, how much of the API features are actually exposed in the templates ? 20% ? 50% ? 80%20:46
ttx99% ?20:46
*** mawagon1 has quit IRC20:46
mordredI didn't say it for ceilometere - but  it does apply to both projects ...20:46
sdake_zwell if you mean resources, I'd say we are at 90% - missing some quantum integration20:46
gabrielhurleythat summary makes things sound pretty rosy. what's still missing? what's challenging? I know y'all aren't done.20:46
ttxgabrielhurley is the atheist non-believer20:47
mordredheat and ceilometer both have been very responsive and self-sufficeient in CI/infra concerns20:47
nijabamordred: and the reverse has been true to... and we did stress you a bit lately20:47
sdake_zgabrielhurley we currently implement cloudwatch, which is going I believe into ceilometer so that is a chunk of work that needs sorting out20:47
sdake_zgabrielhurley the other point is our quantum integration which stevebaker is working on for g20:47
*** john5223 has quit IRC20:48
sdake_zgabrielhurley some folks want a non cloudformation CDL (the template language) which we plan to take up in G if there is interest20:48
sdake_zthats all I can think of at the moment20:48
*** john5223 has joined #openstack-meeting20:48
gabrielhurleylooks like there are a large number of untriaged blueprints...20:48
sdake_zheat usable today though with nearly all the infrastructure20:48
sdake_zthose aren't untriaged, they are g cycle20:49
jaypipessdake_z: plan to take up a non-CF CDL in G or H?20:49
sdake_zsorry they are h cycle20:49
sdake_znon-cf cdl for H20:49
sdake_zsorry not g guys, h :)20:49
*** john5223 has joined #openstack-meeting20:49
gabrielhurleyfigured that's what you meant20:49
sdake_zcdl, untriaged blueprints -> h20:49
*** sleepsonthefloor has quit IRC20:49
*** glenc has quit IRC20:50
sdake_zthis is the normal model for projects, accept blueprints at beginning of cycle,then accept new set at beginning of next cycle20:50
gabrielhurleyso from your perspective Heat is basically solid where it is, and the future is just about adding additional functionalities people would like to see (e.g. all those blueprints)?20:50
sdake_zyes, and sorting out cloudwatch20:51
gabrielhurleygot it20:51
*** AndroUser2 has joined #openstack-meeting20:51
*** AndroUser2 has quit IRC20:51
sdake_zcloudwatch not a major problem tho, it will end up somewhere just a matter of where20:51
*** AndroUser2 has joined #openstack-meeting20:51
sdake_zcommunity has decided ceil is place for that and I agree - just matter of  timing now20:51
gabrielhurleyand graduation ;-)20:52
ttxsdake: so having both considered at the same time is actually a good thing20:52
sdake_zagree ;)20:52
jaypipesand documentation :)20:52
russellband there seems to be very good collaboration between ceilometer and heat, so that helps20:52
annegentlejaypipes: +120:52
gabrielhurleyjaypipes: docs? I've heard of those...20:52
nijabarussellb: +120:52
* annegentle sobs20:52
ttxOK ,if we don't have further question, I'll do the release management repotr today as well20:52
* gabrielhurley feels bad for making annegentle cry20:52
* annegentle recovers quickly20:52
* jaypipes hands annegentle a tissue20:52
ttxgabrielhurley: she never actually cries20:52
sdake_zwe will improve docs - could use a bit of coaching there tho20:53
annegentleit seems like the API docs all point to AWS pages20:53
nijabasdake_z: force doc contrib along with any new feature/change20:53
annegentleboth projects will have to be on their toes with the wiki migration coming this weekend since quite a few docs are in there20:53
sdake_zmakes sense nijaba20:53
*** rnirmal has quit IRC20:53
ttxanything else before we do the release alignment report ?20:54
sdake_zone last point which I should mention is we feel the security model of heat is rock solid as well20:54
sdake_zsomething we have really spent alot of time on20:54
*** rnirmal has joined #openstack-meeting20:54
annegentleand use DocImpact in commit messages20:54
annegentlettx: sure go ahead20:54
gabrielhurleysdake_z speaking of... how do you get around issues of trust/delegation?20:54
*** markmcclain has quit IRC20:54
* ttx holds until that question is answered20:54
*** vipul is now known as vipul|away20:55
sdake_zyou mean where keystone requires admin to do something and the user only has some other privs like "demo"?20:55
sdake_zya we haven't fixed that yet, that is a blueprint for h - what we would like is a "sudo" for keystone but that may be untenable20:55
sdake_zdefinately a solveable problem though20:55
ttxok, moving on20:56
ttx#topic Report on release cycle alignment progress20:56
*** openstack changes topic to "Report on release cycle alignment progress (Meeting topic: tc)"20:56
ttxBoth projects were aligned to the common release process by grizzly-2.20:56
ttxCeilometer had last-minute issues that made it 4 days late, critical bugs that should probably have been spotted earlier... I don't think that would happen again20:56
ttxgrizzly-3 should be a good test, one week from now20:56
ttxAll in all, they are better integrated than Cinder or Keystone were at this point in their incubation cycle20:56
*** AndroUser2 has quit IRC20:57
ttxbut we have higher expectations now, that's how you make progress :)20:57
* jgriffith feels the sting20:57
bcwaldonttx: I'm not sure that's a fair argument ;)20:57
ttxI don't foresee any issue on the release management side.20:57
ttxBoth PTLs and teams were reactive and accessible20:57
ttxread: not in california20:57
bcwaldonread: ttx is being a jerk20:58
ttxquestions on that front ?20:58
ttxbcwaldon: hehe20:58
*** markmcclain1 has joined #openstack-meeting20:58
mordrednope. I'm happy with both projects in that regard20:58
markmcme too, both are doing a great job20:59
ttxmordred: is infra happy with both as well ?20:59
*** otherwiseguy has quit IRC20:59
heckjbcwaldon: nothing unusual, really20:59
mordredttx: yup20:59
* ttx cries now, to see if Jay will give him a tissue21:00
ttxOK time is off21:00
ttxWe'll continue with technical review next week21:00
ttxThanks everyone !21:00
* jaypipes hands ttx a hankie21:00
*** dims has joined #openstack-meeting21:00
* annegentle hands ttx a tissue21:00
sdake_zthanks guys21:00
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"21:00
openstackMeeting ended Tue Feb 12 21:00:54 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:00
openstackMinutes:        http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-02-12-20.03.html21:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-02-12-20.03.txt21:00
openstackLog:            http://eavesdrop.openstack.org/meetings/tc/2013/tc.2013-02-12-20.03.log.html21:00
ttxjaypipes, annegentle: thanks!21:01
*** al-maisan is now known as almaisan-away21:01
ttxmarkmc, heckj, notmyname, bcwaldon, jgriffith, vishy, gabrielhurley, danwent: still around ?21:01
rainyayou guys are silly21:02
bcwaldonquiet down, rainya!21:02
rainyamake me, waldon! ;P21:02
ttx#startmeeting project21:02
openstackMeeting started Tue Feb 12 21:02:32 2013 UTC.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.21:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:02
*** openstack changes topic to " (Meeting topic: project)"21:02
openstackThe meeting name has been set to 'project'21:02
ttxAgenda @ http://wiki.openstack.org/Meetings/ProjectMeeting21:02
*** nati_ueno has quit IRC21:02
*** nati_ueno has joined #openstack-meeting21:03
*** jsavak has joined #openstack-meeting21:03
ttx#topic General announcements21:03
*** openstack changes topic to "General announcements (Meeting topic: project)"21:03
ttxOne week left for feature merging before grizzly-3... Remember we cut the branch at the end of the day next Tuesday.21:03
ttxReview often and merge early... the gate *will* be slow, so the more you get in early, the better21:03
ttxthere will be stuff left over because the gate is busy and false negatives i ntests plaguing it21:04
ttx#info The session submission site for the Havana Design Summit in Portland is open21:04
ttx#link http://summit.openstack.org21:04
ttxI'll announce it in email... soon21:04
ttxBut if you already have ideas for topics that would make nice sessions at the Design Summit, feel free to suggest them21:04
ttx#info We'll all need to sign the CLA again after Feb 2421:05
ttx#link http://lists.openstack.org/pipermail/openstack-dev/2013-February/005662.html21:05
ttxSo it's simplifying stuff a lot for new contributors, but existing ones need to go through one more hoop21:05
ttxquestions about that ?21:05
mordred^^^ that last thing is important for everyone to note21:06
uvirtbotmordred: Error: "^^" is not a valid command.21:06
*** joesavak has quit IRC21:06
notmynamettx: does that affect voting at all?21:06
* mordred punches uvirtbot21:06
ttxthe CLA stuff ?21:07
*** vipul|away is now known as vipul21:07
notmynameyes. and whatever associated changes are involved21:07
*** radez is now known as radez_g0n321:07
fungiit will not affect voting at all21:07
ttxnotmyname: hmm... you will have to be a foundation member to sign the CLA21:07
ttxso you might see an increase in those members21:07
fungiit may increase the number of eligible voters over time21:07
fungiwhat ttx said21:08
mordredttx: do ongoing testing refactors count for feature freeze?21:08
ttxand since only people that are fondation memebrs and contributors could vote in PTL elections...21:08
* gabrielhurley despises the hoops it takes to contribute to openstack21:08
* fungi does too21:08
heckjgabrielhurley: +121:08
ttxthat may result in affecting the vote somehow21:08
*** topol has quit IRC21:08
mordredgabrielhurley: then you will like the new changes21:08
fungiwe made the hoops easier to jump through, and added chrome polish21:08
ttxmordred: adding more tests (or fixing them) is not a feature.21:09
mordredand lube21:09
ttxnotmyname: does that make sense ?21:09
mordredttx: just checking - I'm behind on that blueprint21:09
*** markmcclain1 has quit IRC21:09
heckjttx: when will we need to go jumping through these new flaiming hopes? Doesn't look like we can quite yet21:09
notmynamettx: ya. I wouldn't expect anything to change. but since it's close to the election time and in some part is dependent on foundation membership, I wanted to make sure21:09
ttxnotmyname: previously, you could have contributors that were not foundation members. That won't be possible anymore21:09
ttxnotmyname: oh, I see what you mean21:09
fungiheckj: february 24th or when you have time thereafter, but before you push any new commits to gerrit21:10
ttxthat's a question for mordred actually, how he will compile the voters list exactly21:10
heckjat least it's after grizzly-3 close21:10
notmynamettx: ah. so it may be possible that some previous contributors will need to do something they haven't done before21:10
ttxnotmyname: but if anything, I expect it will increase the number of voters rahter than reduce it21:10
*** pnavarro has quit IRC21:10
fungiheckj: we scheduled it that way intentionally21:10
ttxsince it wil catch contributors that failed to be foundation members21:10
mordredATC is decided from people who have contributed - current eligibility to contribute does not factor21:10
ttxok, we need to move on21:11
ttxmore discussion on the thread linked above21:11
ttx#topic Oslo status21:11
*** openstack changes topic to "Oslo status (Meeting topic: project)"21:11
*** annegentle has quit IRC21:11
ttx#link https://launchpad.net/oslo/+milestone/grizzly-321:11
ttxmarkmc: o/21:11
ttxAll Essential/High stuff is completed21:11
*** markmcclain has joined #openstack-meeting21:11
*** mrunge has joined #openstack-meeting21:12
markmcgrizzly-3 came fast21:12
markmckeyring won't make it21:12
markmcoslo-config cli probably not either21:12
ttxshould you be removing those from the roadmap now ?21:12
markmcyeah, will do21:12
markmcthe two rpc ones could miss too, I need to catch up on them21:12
ttxI gather that none of the remaining stuff is worth a feature freeze exception, right ?21:12
markmcother thing is I pushed a 2013.1b tag for oslo-config21:13
markmctarball didn't get pushed, but we're fixing that21:13
markmcI've got patches ready to push to make all projects use it21:13
markmcbasically s/from $project.openstack.common import cfg/from oslo.config import cfg/21:14
ttxmarkmc: tarballs not getting pushed happens. Would like it to happen less.21:14
markmcso they're fairly invasive21:14
markmchoping to get them merged before grizzly-321:14
*** gabrielhurley has quit IRC21:14
markmcso we're all using oslo-config21:14
ttxmarkmc: that would be preferable21:14
mordredttx: this was missing jobs - not broken jobs at least21:14
markmcttx, it was my fault21:14
ttxmarkmc: cool, I like that.21:14
markmcok, that's me21:15
*** alexpilotti has joined #openstack-meeting21:15
ttxmarkmc: if that oslo-config import doesn't make grizzly-3... are you fine with the code copy living there for grizzly release ?21:15
*** boris-42 has quit IRC21:15
markmcttx, yeah, that's fine21:15
markmcttx, I can remove it from oslo-incubator21:15
markmcttx, without affecting the projects21:15
ttxok, thx21:15
ttxAnything else on the oslo topic ?21:15
markmcnot from me21:16
ttx#topic Keystone status21:16
*** openstack changes topic to "Keystone status (Meeting topic: project)"21:16
ttxheckj: o/21:16
*** markmc has left #openstack-meeting21:16
ttx#link https://launchpad.net/keystone/+milestone/grizzly-321:16
ttxLimited progress since last week...21:16
ttxShould we be removing stuff from scope to allow focusing efforts ? Or does it not make any sense here due to the interrelation ?21:17
heckjlots of it held up in reviews, but code's coming in21:17
*** sandywalsh_ has quit IRC21:17
heckjttx: it's trimmed down pretty tight, all pretty interrelated right now21:17
heckjAll teh status could legit read "Needs Code Review" for the current status21:18
heckjwe have some code that's still being written, but down to the last pieces21:18
ttxHow is "trusts" going on ?21:18
*** garyTh has quit IRC21:19
heckjwe brought it up in the keystone meeting earlier today, but I'll reiterate - please actively review code - try and look and review at least once a day this week to help21:19
heckjttx: under active review, looking pretty good.21:19
ttxheckj: I can spend some time looking into that later today21:19
*** gabrielhurley has joined #openstack-meeting21:19
ttxbenefit of having me in that timezone21:19
ttxAnything more about Keystone ?21:19
heckjjust a need for a lot of reviews, that's it21:20
ttxheckj: should I update all those statuses to "Needs code review" ?21:20
heckjttx: sure, thanks21:20
ttxincluding replace-tenant-user-membership, ok21:20
ttx#topic Swift status21:21
*** openstack changes topic to "Swift status (Meeting topic: project)"21:21
ttxnotmyname: o/21:21
ttx#link https://launchpad.net/swift/+milestone/1.8.021:21
ttxStill shooting for roughly first half of March ?21:21
notmynameyes, but there is no date set21:21
notmynamethere are a couple of outstanding reviews that are important for 1.8 IMO, and a few that need to be written/submitted21:22
ttxI don't have anything else21:22
ttxAnything more on Swift ?21:22
notmynameI have one other thing21:22
ttxgo for it21:22
notmynamean FYI, since it's been discussed in many places recently21:22
notmynameone thing we talked about in the swift meeting last week was encryption in swift21:23
ttxa not in b or not a in b ?21:23
notmynamealthough this isn't really a new position, we all agreed that encryption doesn't belong in the scope of swift21:24
*** joesavak has joined #openstack-meeting21:24
ttxsounds good to me21:24
ttxthe bucket needs to stop somewhere21:24
notmynameagain, nothing new. just a little more formal21:24
ttxnoslzzp: anything else ?21:24
ttxnotmyname: anything else ?21:25
notmynamenope :-)21:25
ttx(bucket. heh)21:25
ttx#topic Glance status21:25
*** openstack changes topic to "Glance status (Meeting topic: project)"21:25
noslzzplol - nope. :)21:25
ttxbcwaldon: o/21:25
ttx#link https://launchpad.net/glance/+milestone/grizzly-321:25
ttxMostly concerned with the (essential) glance-api-v2-image-sharing21:25
bcwaldonthis is my week to catch up on reviews and land several bug fixes and features21:26
bcwaldonone of them being image sharing21:26
bcwaldonso I'm not actually concerned about it21:26
ttxSince the reviews there are a bit stalled, and it will take time to get them processed through the gate queue21:26
ttxthe sooner the better, for essential stuff21:26
ttxAre the rest of them still likely to make it ?21:26
*** jsavak has quit IRC21:26
bcwaldonyep, the first half of the reviews for that BP are already approved :)21:26
ttxShould we remove (not started) api-v2-property-protection from the mix ?21:27
bcwaldonmarkwash: ?21:27
bcwaldonttx: there's your answer21:27
bcwaldonnot sure21:27
bcwaldonwill confirm what to do offline21:28
ttxAlso I'd remove importing-rootwarp / iscsi-backend-store and move that to Havana, sounds like somethig that would benefit frmo further discussion21:28
bcwaldonttx: I've thought about that quite a bit, actually21:28
ttxbcwaldon: what's your take ?21:28
bcwaldonttx: I'm not against landing it in grizzly at all - I think there is an alternative approach we will end up taking as a community (cinder backend vs iscsi backend), but this is still a valid use case21:29
bcwaldonthe rootwrap piece has been proved in nova already, so I'm not worried about that21:29
ttxbcwaldon: it impacts packaging a bit, but if it lands by g3 it's probably ok21:29
bcwaldonyes, I would not give it a FFE21:29
*** jpich has joined #openstack-meeting21:29
ttxit's just that adding it for that release if the plan is to remove it next release, meh21:29
ttxbut that's your call, as long as you respect the deadlines :)21:30
ttxAnything more on Glance ?21:30
bcwaldonwhat deadlines!?21:30
bcwaldonnothing more on Glance other than an apology for not keeping up with reviews ;)21:30
rainyathere are deadlines!?21:30
bcwaldonrainya: quiet!21:30
bcwaldonttx: that is all21:31
ttx#topic Quantum status21:31
*** openstack changes topic to "Quantum status (Meeting topic: project)"21:31
rainyabcwaldon: yes, sir!21:31
ttxdanwent: hi!21:31
ttx#link https://launchpad.net/quantum/+milestone/grizzly-321:31
*** patrocinio has left #openstack-meeting21:31
ttxLoking busy but good21:31
danwentyes, overall, more green21:31
ttxHow is review prioritization going ? Do you think reviewers give priority to high-prio stuff ?21:31
danwenteverything must be in review by today, or its automatically out21:31
ttxi.e. we don't need to remove anything ?21:31
danwentgood.  really there are only two high priority features, though one of them (lbaas) is split into three BPs21:32
ttxOK, looking at the remaining ones in that category:21:32
danwentyong's multi l3/dhcp stuff is in good shape21:32
ttxHow close is quantum-scheduler ?21:32
danwenthe is on holiday, but i'm not very worried about that going in.21:32
danwentthat is yong's BP… sorry, we shoudl have renamed it.21:32
ttxoh, ok21:32
danwentthe good news on lbaas is that we got intiial code posted early enoug21:33
ttxdanwent: when are you going to remove those without code proposed ? EOD ?21:33
danwentthat when the feeback was that we need to drastically simplify the code, we still have some time to do it.21:33
danwentyes, EOD today21:33
danwentonly really two21:33
ttxsounds good21:33
danwentinclude one plugin that was dropped way last minute21:33
danwentdropped -> proposed21:33
ttxI use the word "thrown"21:34
danwentjust a heads up, with the lbaas reworking, i wouldn't be shocked to be talking FFE next week21:34
danwentbut we've paired down what we're targeting21:34
ttxprepare the beer bribes21:34
danwentso I think its managable.21:34
ttxAnything else on Quantum ?21:34
danwenti think the mirantis folks would rather pay in vodka :P21:34
ttxI'll have to check the beer/vodka change rate21:34
ttx#topic Cinder status21:35
*** openstack changes topic to "Cinder status (Meeting topic: project)"21:35
ttxjgriffith: hi!21:35
ttx#link https://launchpad.net/cinder/+milestone/grizzly-321:35
jgriffithI'm pretty confident in most of these21:35
ttxHow is volume-backups doing ?21:35
*** mdomsch has joined #openstack-meeting21:35
jgriffithThe drivers from coraid and Huawei etc are debateable21:35
jgriffithGood, going through review with the batch of changes from last round21:36
jgriffithI think it's looking good so far though21:36
jgriffithAnd the change eharney has for Gluster and LIO I'm not worried about at all21:36
*** kspear has joined #openstack-meeting21:36
ttxThe week will be very short21:36
ttxIs there anything in the rest of the list that we should remove right now ?21:36
reedjgriffith, did you have time to look at the encryption patch?21:36
jgriffithreed: Yeah, there's some concerns there21:36
jgriffithreed: snapshots, clones etc?21:37
jgriffithttx: I think I've cleaned out as fair as I can right now21:37
ttxjgriffith: https://blueprints.launchpad.net/cinder/+spec/quotas-limits-by-voltype in particular is "not started". Still want to keep it in scope ?21:37
jgriffithttx: I'm giving some of the drivers til Friday to make some progress21:37
jgriffithttx: I tricked ya21:37
ttxhhm, ok21:37
jgriffithttx: I already pulled that one out :)21:38
jgriffithttx: just a couple minutes ago21:38
reedjgriffith, cool, thanks21:38
jgriffithreed: we should sync up after meeting21:38
icchawin 1921:38
ttxjgriffith: still looks not statred to me21:38
jgriffithOh crud, I didn't save the change21:38
jgriffithI'll do that21:39
jgriffithIt will disappear21:39
jgriffithsorry bout that21:39
ttxIs xenapinfs-glance-integration complete ?21:39
jgriffithreview IIRC21:39
ttxI saw two review linked both merged21:40
ttxanyway, you can check it out, we need to move on21:40
*** otherwiseguy has joined #openstack-meeting21:40
jgriffithyeah, it merged21:40
ttxAnything more on Cinder ?21:40
jgriffithNetApp's share service:21:40
* ttx marks xenapinfs-glance-integration implemented21:40
jgriffithdidn't get much feed-back from the ML on the whole topic21:41
ttxmaybe raise it again21:41
jgriffithYeah, just wanted to point it out to folks here21:41
ttxor hunt down key people on IRC for feedback21:41
*** markmcclain1 has joined #openstack-meeting21:41
ttx#topic Nova status21:41
jgriffiththats' it for me I htink21:41
*** openstack changes topic to "Nova status (Meeting topic: project)"21:41
ttxjgriffith: thx!21:41
ttxvishy: o/21:42
ttx#link https://launchpad.net/nova/+milestone/grizzly-321:42
ttxvishy: About backportable-db-migrations: how about we push that between g3 and rc1 ? I don't see that as really disruptive anyway, and that's the right moment to push it (after all features merged) ?21:42
ttxOK, then I'll move it to rc1 when I'll have that created21:42
ttxLooking at the remaining High stuff:21:42
*** markmcclain has quit IRC21:42
ttxHow is nova-quantum-security-group-proxy going ?21:43
vishycode is up21:43
vishyunder review21:43
*** sleepsonthefloor has joined #openstack-meeting21:43
ttxvishy: should make it ?21:43
vishyi think so21:43
ttxSame question for instance-actions21:43
vishysame answer :)21:43
ttxshow-availability-zone and rebuild-for-ha still shouldn't be considered completed ?21:43
vishyshow-availability-zone is complete21:44
ttxok, updating21:44
vishyrebuild is complete too21:44
ttxok, updating21:45
*** luis_fdez has quit IRC21:45
ttxShould you be removing all stuff that doesn't have any code proposed yet ?21:45
ttxlike quantum does ?21:45
vishyttx: yeah21:45
ttxno point is spending time on reviews that won't make it anyway21:46
vishyttx: although i don't know if there are any of those21:46
ttxPlanning on reviewing that at the next Nova meeting ?21:46
ttxquite a few of those are marked 'started' with no code attached AFAICT21:46
*** primeministerp has quit IRC21:46
ttxAlso 3 blueprints are targeted to g3 but not in series goal: migrate-volume-block-migration configuration-strategies encrypt-cinder-volumes21:46
ttxyou might want to remove them as well21:47
ttxAny question on Nova ?21:47
russellbvishy: i can take that on (going through and removing stuff without code) if you'd like21:47
ttxI feel like we are in good shape, it's just that there isn't so much time left21:47
ttxso prioritization might be in order21:47
vishyrussellb: cool thanks21:47
ttxif only to have the gate process the right stuff21:48
russellbvishy: np, will get through it tonight/tomorrow AM21:48
ttxwhen it will be on the critical path (and it will)21:48
ttxhttps://blueprints.launchpad.net/nova/+spec/libvirt-aoe has code in review but is marked implemnted, I should probably reverse that21:49
ttxno, just merged21:49
vishyttx: it merged21:49
*** cp16net is now known as cp16net|away21:50
ttxok, that's all I got. Anything more about Nova ?21:50
ttx#topic Horizon status21:50
*** openstack changes topic to "Horizon status (Meeting topic: project)"21:50
ttxgabrielhurley: hey21:50
ttx#link https://launchpad.net/horizon/+milestone/grizzly-321:50
*** bencherian has quit IRC21:50
gabrielhurleya couple of those BPs will likely merge today21:51
ttxI see you updated your statuses recently21:51
gabrielhurleyseveral more are one patch away from being mergeable21:51
ttxHow is the upload stuff going ?21:51
gabrielhurleywell... mixed bag21:51
gabrielhurleydirect image uploading has a review which is gonna be functional for grizzly21:51
gabrielhurleybut the overall file upload UI stuff has about a day to get something up before I call that dead in Grizzly21:52
ttxYou mentioned you potentially consider an exception to get that merged... but it only makes sense if it's just a few days away21:52
gabrielhurleysoooo... it looks like that one may be a function over style decision for Grizzly21:52
gabrielhurleyrevisit in conjunction with the glance team and rework the UI in Havana21:53
*** cp16net|away is now known as cp16net21:53
ttxalmost everything else has code proposed now, iiuc21:53
gabrielhurleythe Quantum Security Groups BP needs code as well, but amotoki is very on top of things and I trust him to get it done if he says it'll happen.21:53
gabrielhurleyotherwise everything else has code up, yep21:53
ttxLooks good21:53
ttxAnything more on Horizon ?21:53
gabrielhurleystarted winnowing the bugs list too21:54
ttxThis is going to be review week21:54
gabrielhurleyjust trying to get ready for the RC21:54
gabrielhurleynothing more beyond that21:54
ttx#topic Incubated projects21:54
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:54
ttxAnyone from Heat/Ceilometer around ?21:54
sdake_zheat here21:54
ttx#link https://launchpad.net/heat/+milestone/grizzly-321:55
sdake_zso good progress in last week21:55
sdake_zalthough getting tight on time with lots of bugs to fix21:55
ttxLooks like you should remove stuff that won't make it by the deadline21:55
ttxI suspect some of the 'not started' stuff will miss21:55
sdake_zour meeting is wednesday where we will pull stuff that isn't going to make it21:55
sdake_zttx agree21:55
ttxalthough you're not in the common gate so you might not suffer that much21:56
sdake_zsounds like more schedule time to me ;)21:56
ttxnext week we'll basically review what's left and drop stuff that is not merged yet21:56
sdake_zsounds good21:57
ttxthat's when people realize it's too late and statr crying :)21:57
sdake_zquesito ntho, that does not include bugs right?21:57
sdake_zonly blueprints?21:57
sdake_zwe still have few moreweeks for bugs?21:57
ttxAfter g3... you build a RC bug list21:57
sdake_zgot it21:57
ttxwhen you complete that we build a RC121:57
ttxand then shit happens, a new RC bug is discovered21:58
ttxso you build a new list and do RC2, etc.21:58
ttxExplaines at http://wiki.openstack.org/ReleaseCycle21:58
ttxanyone from ceilometer ?21:58
ttxfor logging purpose, same remark as for heat21:59
*** troytoman is now known as troytoman-away21:59
ttxLooks like it's time to reduce the list to match what will be in by next week21:59
ttxanything else anyone ?22:00
rainyattx, i've read that wiki on release cycle several times times and it helped a lot having you type it out just now :)22:00
ttxrainya: I'm usually always confusing. Wiki AND Irc.22:00
rainyabetween the two, perfectly sensible!22:00
ttxGod thing today I'm clearer on Irc.22:00
ttxok, next meeting awaits22:01
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:01
openstackMeeting ended Tue Feb 12 22:01:04 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-02-12-21.02.html22:01
ttxThanks everyone!22:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-02-12-21.02.txt22:01
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-02-12-21.02.log.html22:01
rainyawooohooo ttx!22:01
rainyamade in time again!22:01
*** annegentle has joined #openstack-meeting22:02
*** Gordonz has quit IRC22:02
gabrielhurley#startmeeting horizon22:03
openstackMeeting started Tue Feb 12 22:03:00 2013 UTC.  The chair is gabrielhurley. Information about MeetBot at http://wiki.debian.org/MeetBot.22:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:03
*** openstack changes topic to " (Meeting topic: horizon)"22:03
openstackThe meeting name has been set to 'horizon'22:03
gabrielhurley#topic Status and Overview22:03
*** openstack changes topic to "Status and Overview (Meeting topic: horizon)"22:03
gabrielhurleyComing into the final week of real activity22:03
gabrielhurleylots of reviews up22:03
gabrielhurleylots of blueprints with reviews up particularly22:03
gabrielhurleyI've commented on almost all of 'em22:03
gabrielhurleygot my own BP review up22:04
gabrielhurley(I wrote code, yay!)22:04
*** sdake_z has quit IRC22:04
gabrielhurleyIn general everything's looking good and going the right direction22:04
gabrielhurleyjust need everyone to be really active and diligent for this week22:04
*** heckj has quit IRC22:04
*** woodspa has quit IRC22:04
gabrielhurleyI will do reviews every day22:04
gabrielhurleyI don't see anything that's got a review up there that can't make it though.22:05
gabrielhurley#topic Blueprints22:05
*** openstack changes topic to "Blueprints (Meeting topic: horizon)"22:05
gabrielhurleydavidlenwell seems to have escaped me22:05
gabrielhurleywas ginna grill him on the file upload UI blueprint22:05
*** noslzzp has quit IRC22:05
cody-somervilleI'll ping him.22:06
gabrielhurleycody-somerville got up a review for the Glance image upload which may have to suffice for Grizzly. It gets the job done, but I was hoping to have things be cool/fancy. Thanks to Cody for getting that far though,22:06
*** shardy has left #openstack-meeting22:06
gabrielhurleyIn Havana we can work with the Glance team to think about direct upload mechanisms with pretty progress indicators and such22:06
gabrielhurleyamotoki doesn't seem to be around currently either, but I'll follow up with him on the Quantum Security Groups blueprint.22:07
gabrielhurleyI'm not worried there, though.22:07
gabrielhurleycody-somerville: if you could tell davidlenwell that my inclination is to drop that blueprint from Grizzly unless there's a review in the next two days I'd appreciate it.22:08
cody-somervilleWill do.22:08
*** markmcclain1 has quit IRC22:08
gabrielhurleyanybody else got blueprints they want to discuss?22:08
kspeargabrielhurley: other than pleading for a review? :)22:08
gabrielhurleyI'm gonna go through 'em all again today22:09
*** jhenner has quit IRC22:09
gabrielhurley#topic Bugs22:09
*** openstack changes topic to "Bugs (Meeting topic: horizon)"22:09
gabrielhurleyI narrowed down the bug list to close out G3.22:09
*** davidlenwell has joined #openstack-meeting22:09
*** markmcclain has joined #openstack-meeting22:10
gabrielhurleyThere's also one new one for enabling the XFrameOptionsMiddleware byu default22:10
gabrielhurleyit's a termendously simple change but it's a good security practice22:10
gabrielhurleyI wanna make sure that's merged for Grizzly22:10
gabrielhurley#topic General Discussion22:10
*** openstack changes topic to "General Discussion (Meeting topic: horizon)"22:10
gabrielhurleyI've got one topic for general discussion today22:11
mrungeI have met one bug22:11
gabrielhurleygo ahead22:11
mrungehow do we handle backwards compatibilty?22:11
davidlenwellgabrielhurley: have you looked at / played with Thermal? the heat plugin someone wrote?  or did you already talk about that and I missed it.22:11
*** rnirmal has quit IRC22:11
mrungeI had one bug, where grizzly horizon don't works with folsom keystone22:12
*** bencherian has joined #openstack-meeting22:12
gabrielhurleymrunge: in general Grizzly Horizon should work with Folsom. If that's not the case why should figure out what introduced the incompatibility and either address it in code or address it via a setting as a last resort.22:12
gabrielhurleyis there a bug filed for it?22:12
mrungegabrielhurley, https://bugs.launchpad.net/horizon/+bug/112197522:12
uvirtbotLaunchpad bug 1121975 in horizon "original_ip keystone parameter not compatible with folsom keystone" [Undecided,New]22:12
gabrielhurleylet's fix that22:13
gabrielhurleyshould be easy to fix in code22:13
mrungethat change in keystone was introduced in mid october22:13
gabrielhurleytriaged into the list with High priority22:13
dolphmkeystoneclient then? not keystone folsom22:13
mrungedolphm, exactly22:14
*** Mr_T has left #openstack-meeting22:14
gabrielhurleydavidlenwell: I haven't looked at Thermal in quite some time, why do you ask?22:14
davidlenwellgabrielhurley: I was reviewing it last week because a few members of our team are putting a lot of effort into using heat22:15
davidlenwellwondered if you had seen the interface and if you had any opinions about it.22:16
gabrielhurleyI'm not gonna offer an opinoin 'cuz my opinion would be out of date22:16
mordredgabrielhurley: I've heard that, pending heat's acceptance, just merging the work into horizon might be an option?22:17
gabrielhurleyif Heat graduates then we'll get all the details sorted22:17
gabrielhurleyand yes, it'll absolutely be the starting point22:17
gabrielhurleynot trying to sound negative22:17
davidlenwellI think it will need a lot of work before its ready to merge into horizon.. some of the ui is very out of place22:18
gabrielhurleyI think that's likely22:18
davidlenwellfor one its got its own tab in the left nav .. with project and admin ..22:18
gabrielhurleybut the UI is easier to sort out than the API stuff, so the work they've done to get it functional will be valuable22:18
gabrielhurleyit won't be a wholesale merge by any means22:18
gabrielhurleyI've been taking a "cross that bridge when we get there" approach22:19
gabrielhurleysame with ceilometer22:19
gabrielhurleythey've been developing things in the wings22:19
gabrielhurleyThe one topic I'd like to discuss real quick: In the spirit of continuing to expand horizon core, I'd like to propose amotoki (who's not present) for Horizon Core. He's done a ton of work over the last two release cycles and has really stepped up his reviewing in the last few months. Anyone object before I send something to the ML?22:20
*** agentle_ has joined #openstack-meeting22:20
*** ladquin has quit IRC22:21
*** diogogmt has quit IRC22:21
gabrielhurleyAlso, a quick reminder for the current core folks: if something already has a +2 and you feel it's ready as well, feel free to +2 *and* approve the review. You have to do both. I've seen a few reviews that had a +2 from me and either a +1 or a +2 but no "approve" from other core folks.22:22
gabrielhurleyanyo other questions or topics?22:22
*** sandywalsh has quit IRC22:23
jpichwhen should code be up at the latest for bug fixes?22:23
gabrielhurleybug fixes can go straight to the release being cut, but make sure you file bugs in launchpad so they can be tracked by release management22:24
*** dosaboy1 has quit IRC22:24
*** annegentle has quit IRC22:24
*** agentle_ is now known as annegentle22:24
jpichOk! cheers22:24
gabrielhurleygreat. thanks everyone, and do all you can on reviews! have a great week!22:24
*** ladquin has joined #openstack-meeting22:25
*** openstack changes topic to "OpenStack meetings || Development in #openstack-dev || Help in #openstack"22:25
openstackMeeting ended Tue Feb 12 22:25:07 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:25
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-02-12-22.03.html22:25
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-02-12-22.03.txt22:25
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-02-12-22.03.log.html22:25
jpichReviews, reviews. Thanks everyone22:25
*** mrunge has quit IRC22:26
*** mtreinish has quit IRC22:26
*** gabrielhurley has quit IRC22:27
*** kspear has quit IRC22:29
*** mrunge has joined #openstack-meeting22:30
*** mrunge has quit IRC22:31
*** markmcclain has quit IRC22:31
*** jpich has left #openstack-meeting22:32
*** danwent has quit IRC22:35
*** sandywalsh has joined #openstack-meeting22:36
*** nati_ueno has quit IRC22:37
*** danwent has joined #openstack-meeting22:38
*** jhenner has joined #openstack-meeting22:40
*** joesavak has quit IRC22:40
*** alexpilotti has quit IRC22:41
*** koolhead11|away has joined #openstack-meeting22:41
*** danwent has quit IRC22:41
*** sdake has quit IRC22:42
*** danwent has joined #openstack-meeting22:46
*** markvan has quit IRC22:47
*** joshuamckenty has quit IRC22:53
*** EmilienM has left #openstack-meeting23:00
*** danwent has quit IRC23:01
*** annegentle has quit IRC23:02
*** lbragstad1 has quit IRC23:06
*** anniec has quit IRC23:08
*** joshuamckenty has joined #openstack-meeting23:11
*** mdomsch has quit IRC23:11
*** anteaya has quit IRC23:21
*** nati_ueno has joined #openstack-meeting23:22
*** bdperkin has quit IRC23:24
*** bdperkin has joined #openstack-meeting23:24
*** blamar has quit IRC23:25
*** mikal has quit IRC23:25
*** ctracey has quit IRC23:26
*** mikal has joined #openstack-meeting23:27
*** ctracey has joined #openstack-meeting23:27
*** ravikumar_hp has joined #openstack-meeting23:28
*** eharney has quit IRC23:32
*** fnaval_ has quit IRC23:34
*** maurosr has quit IRC23:36
*** lglenden has quit IRC23:40
*** mattray has quit IRC23:42
*** dims has quit IRC23:46
*** john5223 has quit IRC23:47
*** fifieldt has joined #openstack-meeting23:47
*** fnaval has joined #openstack-meeting23:51
*** fnaval has quit IRC23:51
*** fnaval has joined #openstack-meeting23:52
*** dolphm has quit IRC23:52
*** fifieldt has quit IRC23:53
*** stack_teaser has quit IRC23:55
*** ryanpetrello has quit IRC23:57

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