Tuesday, 2013-12-03

*** rongze has quit IRC00:00
*** fbo_away is now known as fbo00:02
*** NobodyCam_afk is now known as NobodyCam00:04
*** tanisdl has quit IRC00:04
*** tanisdl has joined #openstack-meeting00:05
*** jhenner has quit IRC00:07
*** gokrokve has joined #openstack-meeting00:09
*** mrodden has quit IRC00:09
*** jmontemayor has quit IRC00:12
*** markpeek has quit IRC00:12
*** fbo is now known as fbo_away00:13
*** ArthurBerezin has quit IRC00:14
*** yamahata_ has quit IRC00:15
*** weshay has joined #openstack-meeting00:16
*** dims has joined #openstack-meeting00:23
*** dcramer_ has quit IRC00:24
*** nermina has joined #openstack-meeting00:26
*** rnirmal has quit IRC00:27
*** matsuhashi has joined #openstack-meeting00:29
*** hemna is now known as hemnafk00:30
*** markwash has quit IRC00:30
*** nati_uen_ has joined #openstack-meeting00:33
*** nati_ueno has quit IRC00:35
*** s3wong_ has quit IRC00:37
*** otherwiseguy has quit IRC00:39
*** eharney has quit IRC00:41
*** zbitter has joined #openstack-meeting00:41
*** pablosan has quit IRC00:41
*** fnaval_ has quit IRC00:44
*** pablosan has joined #openstack-meeting00:44
*** zaneb has quit IRC00:44
*** nati_uen_ has quit IRC00:45
*** nati_ueno has joined #openstack-meeting00:46
*** kui has quit IRC00:47
*** sdake_ has quit IRC00:47
*** sdake has quit IRC00:47
*** bill_az has quit IRC00:47
*** matsuhashi has quit IRC00:50
*** matsuhashi has joined #openstack-meeting00:50
*** cdub has quit IRC00:52
*** michchap_ has quit IRC00:53
*** matsuhas_ has joined #openstack-meeting00:53
*** michchap has joined #openstack-meeting00:53
*** matsuhashi has quit IRC00:54
*** marun has joined #openstack-meeting00:55
*** markpeek has joined #openstack-meeting00:55
*** dolphm has quit IRC00:56
*** sacharya has joined #openstack-meeting00:57
*** SridarK has quit IRC00:58
*** dcramer_ has joined #openstack-meeting00:59
*** reaper has quit IRC01:00
*** marun has quit IRC01:02
*** sdake has joined #openstack-meeting01:03
*** ryanpetrello has joined #openstack-meeting01:03
*** cdub has joined #openstack-meeting01:03
*** SumitNaiksatam has quit IRC01:09
*** IlyaE has quit IRC01:10
*** colinmcn_ has quit IRC01:12
*** colinmcnamara has quit IRC01:12
*** herndon_ has joined #openstack-meeting01:13
*** bdpayne has joined #openstack-meeting01:14
*** sdake has quit IRC01:15
*** beagles has quit IRC01:19
*** yamahata_ has joined #openstack-meeting01:20
*** bill_az has joined #openstack-meeting01:22
*** mrodden has joined #openstack-meeting01:23
*** nosnos has joined #openstack-meeting01:26
*** rongze has joined #openstack-meeting01:27
*** rongze has quit IRC01:31
*** SumitNaiksatam has joined #openstack-meeting01:31
*** yamahata_ has quit IRC01:34
*** jcooley_ has joined #openstack-meeting01:37
*** bdpayne has quit IRC01:39
*** sjing has joined #openstack-meeting01:39
*** sarob_ has joined #openstack-meeting01:41
*** sarob has quit IRC01:43
*** kui has joined #openstack-meeting01:43
*** nermina has quit IRC01:44
*** jcooley_ has quit IRC01:45
*** ryanpetrello has quit IRC01:45
*** sarob_ has quit IRC01:45
*** slong has joined #openstack-meeting01:50
*** banix has joined #openstack-meeting01:50
*** slong is now known as summerlong01:50
*** mengxd has joined #openstack-meeting01:52
*** radix_ has quit IRC01:52
*** neelashah has joined #openstack-meeting01:55
*** colinmcnamara has joined #openstack-meeting01:56
*** colinmcn_ has joined #openstack-meeting01:56
*** reed has quit IRC02:00
*** jcooley_ has joined #openstack-meeting02:01
*** MarkAtwood has quit IRC02:01
*** jcooley_ has quit IRC02:02
*** Mandell has quit IRC02:06
*** rongze has joined #openstack-meeting02:06
*** yaguang has joined #openstack-meeting02:07
*** nati_ueno has quit IRC02:09
*** esker has joined #openstack-meeting02:13
*** colinmcnamara has quit IRC02:14
*** colinmcn_ has quit IRC02:14
*** gokrokve has quit IRC02:17
*** gokrokve has joined #openstack-meeting02:17
*** vkozhukalov has joined #openstack-meeting02:19
*** devlaps has quit IRC02:20
*** gokrokve has quit IRC02:22
*** bill_az has quit IRC02:23
*** ryanpetrello has joined #openstack-meeting02:27
*** gokrokve has joined #openstack-meeting02:29
*** pablosan has quit IRC02:29
*** Mandell has joined #openstack-meeting02:29
*** masayukig has joined #openstack-meeting02:30
*** matsuhas_ has quit IRC02:31
*** matsuhashi has joined #openstack-meeting02:31
*** sdake has joined #openstack-meeting02:32
*** masayukig has quit IRC02:39
*** masayuki_ has joined #openstack-meeting02:39
*** ryanpetrello has quit IRC02:43
*** hua has quit IRC02:43
*** nati_ueno has joined #openstack-meeting02:43
*** masayuki_ has quit IRC02:44
*** colinmcnamara has joined #openstack-meeting02:49
*** colinmcn_ has joined #openstack-meeting02:49
*** tanisdl has quit IRC02:51
*** gongysh has joined #openstack-meeting02:52
*** nati_ueno has quit IRC02:53
*** RobinWang has quit IRC02:53
*** dkranz has joined #openstack-meeting02:54
*** SvenDowideit has quit IRC02:54
*** saurabh_ has joined #openstack-meeting02:54
*** sdake_ has joined #openstack-meeting02:56
*** sdake_ has quit IRC02:56
*** sdake_ has joined #openstack-meeting02:56
*** hemanth has quit IRC02:56
*** dcramer_ has quit IRC02:57
*** nosnos has quit IRC02:58
summerlonghey fifieldt!02:58
*** nosnos has joined #openstack-meeting02:59
*** ndipanov has quit IRC02:59
*** danwent has quit IRC02:59
summerlongbrucer...02:59
brucerslong Hi02:59
summerlong#startmeeting DocTeamMeeting03:00
openstackMeeting started Tue Dec  3 03:00:05 2013 UTC and is due to finish in 60 minutes.  The chair is summerlong. Information about MeetBot at http://wiki.debian.org/MeetBot.03:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.03:00
*** openstack changes topic to " (Meeting topic: DocTeamMeeting)"03:00
openstackThe meeting name has been set to 'docteammeeting'03:00
summerlongSo, let's see, anyone besides Bruce out there for the OpenStack meeting?03:00
*** loq_mac has joined #openstack-meeting03:00
summerlongVERY small group, brucer, just the two of us:)03:00
brucerscuse my ignorance - is the the APAC-timing upstream docs meeting thingo?03:01
summerlongyep:)03:01
summerlongAnd loquacious isn't here today, and looks like fifeldt isn't either...03:01
brucerhmm, i totally forgot it was today,03:02
summerlong:)03:02
summerlongWell, let's wait a few minutes and see whether anyone else joins.03:02
loq_maci'm here!03:03
brucerOK. who all is meant to attend?03:03
summerlongYou're here!03:03
loq_macyay!03:03
summerlongSo, lana, tom, the RH crew, and who else, Lana?03:03
loq_macis fifieldt here?03:03
summerlongnot answering :(03:04
* annegentle lurks!03:04
*** dkranz has quit IRC03:04
summerlongannegentle!03:04
annegentlesummerlong! :)03:04
loq_macoh hai annegentle :)03:05
summerlongWas looking through the notes for the last meeting and 3 of the 4 of us were there.03:05
*** SvenDowideit has joined #openstack-meeting03:05
annegentleI'll be in and out, packing for San Antonio (and an early dawn-thirty start) :)03:05
*** twoputt__ has quit IRC03:05
*** twoputt_ has quit IRC03:05
loq_macouch ><03:05
summerlongOk, well, this will be a quick one. Mostly for brucer's benefit.03:05
*** chandankumar has joined #openstack-meeting03:06
brucerWill this meeting be held every alternate Tue?03:06
summerlong#topic last action items:03:06
*** openstack changes topic to "last action items: (Meeting topic: DocTeamMeeting)"03:06
summerlongItem: Loquacity to begin working on a proposal for config-reference and cloud admin guide IA.03:06
summerlongyes, brucer. See the https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting03:06
*** markpeek has quit IRC03:06
loq_maci haven't done that yet03:06
brucerta03:06
annegentlebrucer: summerlong: well technically four Tuesdays a month03:06
loq_machowever, i've made movements in that direction03:06
summerlongYes, was just referring to this time.03:06
*** cdub has quit IRC03:06
*** nati_ueno has joined #openstack-meeting03:07
loq_maci decided i needed to get to know the books better, so i'm doing some general edits on them now03:07
summerlongok, loq_mac, that makes sense. What I did to start with.03:07
loq_macyep03:07
loq_macso, hopefully i'll get started on that before too long03:07
loq_macalso, i think fifieldt and i need to talk in more depth before i can start, too03:07
summerlongItem: Bug Day. The Bug Day has been organised for Dec 20 2013. Do as many as you can on one day....03:07
loq_macannegentle: we might need to add that to our list of things to talk about while i'm here, too03:08
summerlongBug day?03:08
loq_macyep, it's just a day where we all sit down and grind through as many bugs as we can03:08
chandankumarHello03:08
loq_mactom sent mail to the list about it03:08
*** cdub has joined #openstack-meeting03:08
loq_macheya chandankumar03:08
summerlonghello chandankumar03:08
summerlongWill talk to the team here about it. I'm assuming we'll all be in.03:09
brucerhi chandankumar03:09
loq_maccool :)03:09
summerlongOf course, anyone who hasn't worked before will probably just be there looking around.03:09
chandankumar:)03:09
summerlongOk...03:09
summerlong#topic Google Hangout03:09
*** openstack changes topic to "Google Hangout (Meeting topic: DocTeamMeeting)"03:09
summerlong - fun had by all, any comments? Any ideas for future hangouts?03:09
loq_maci'd like to make that a regular thing, personally03:10
loq_macit's nice to see everyone :)03:10
summerlongHow regular, what topic?03:10
summerlongEvery month?03:10
summerlongEvery other month?03:10
loq_maci might leave that up to annegentle :)03:10
summerlongBut...what would be your preference?03:10
chandankumarsummerlong, can hangout will be made in that time when everybody able to attend irrespective of different time zone?03:11
loq_macmonthly would be excessive, i think, if we consider that we're meeting weekly03:11
summerlongPerhaps every other month, and yes, chandankumar, the timing is tricky.03:11
loq_macunless we do it monthly on an alternating time, so we catch the TZs03:11
loq_maclike the irc meeting03:11
summerlongWe in australia were over the moon that it was in daylight.03:11
loq_macwe could do a hangout in lieu of office hours03:11
chandankumarthat will work :)03:12
summerlongwe're not doing office hours....03:12
loq_maci was kicking myself that i was in the US ;)03:12
loq_macyeah, that's what i mean03:12
*** Mandell has quit IRC03:12
summerlongWhat would you want for a topic?03:12
summerlongCurrent issues?03:12
loq_maccan the office hours, do a monthly hangout instead, alternate timezomes03:12
loq_macit wouldn't be hard to have a rolling agenda03:12
loq_macwe could use the wiki for it, just like we do for IRC meetings03:13
summerlongYou mean, can the meeting every month?03:13
*** mengxd has quit IRC03:13
loq_maci'll add this to the list of things to chat to anne about, i think03:13
loq_macand come up with a reasonable proposal03:13
*** colinmcnamara has quit IRC03:13
*** colinmcn_ has quit IRC03:13
loq_macdo you have any strong preferences?03:13
summerlongCould you please do the chat on the list, so all of us can have input?03:13
loq_macok, i'll start the convo there03:14
summerlongSwitching out one meeting a month for a visual sounds good.03:14
loq_macthat'll give everyone a chance to have input03:14
loq_macyeah, that could work03:14
summerlongappreciate it.03:14
*** gyee has quit IRC03:14
loq_macnp03:14
summerlong#action loq_mac to start email discussion around continuing the hangout03:14
summerlong#topic Educating devs03:14
*** openstack changes topic to "Educating devs (Meeting topic: DocTeamMeeting)"03:14
summerlongNick Chase to help with onboarding doc contribs. If you have anyone contact you, can direct to him if you'd like.03:14
summerlongAnne to write blog post describing titles and priorities, and will also follow up with HP Cloud's Spector for a podcast/screencast03:14
summerlongThat was just from the last meeting.03:15
summerlongWas there anything else we needed to discuss?03:15
brucerwhere does anne blog?03:15
loq_maci'm progressing the docs team leads thing with my guys03:15
summerlongon the doc wiki03:15
* brucer needs link03:15
brucerok03:15
summerlongnice, loq_mac03:16
loq_macbrucer: http://www.openstack.org/blog/03:16
loq_macthey're coming around, slowly ;)03:16
brucerta Lana, just got it03:16
summerlongYes, devs are always just a tad, er, something.03:16
loq_maci'm getting them when they're nicely jet lagged, so their resistance is low ;)03:16
summerlongExactly, nice work :)03:16
summerlongOk, and on to the next.03:16
loq_mac*grin*03:17
summerlong#topic Office hours03:17
*** openstack changes topic to "Office hours (Meeting topic: DocTeamMeeting)"03:17
summerlongNow cancelled, per US meeting, now that there are weekly meetings.03:17
loq_mac+103:17
summerlongIt was decidedin the last meeting. Yes, me too, +1.03:17
*** nati_ueno has quit IRC03:17
summerlongbrucer, annegentle was holding office meetings with low attendance.03:17
summerlongWith the new weekly meetings,03:17
summerlongit was decided to forego them.03:17
summerlongNot much else to say, really.03:18
summerlongI never attended, wrong time.03:18
summerlong#topic Doc Boot Camp03:18
*** openstack changes topic to "Doc Boot Camp (Meeting topic: DocTeamMeeting)"03:18
summerlongAny preferences for times? Should it be twice-yearly? Once yearly?03:18
summerlongWould Feb be too soon after the summit? Could anyone on this side go at that time?03:18
summerlongAny wishes for session topics?03:18
summerlongOk, big discussion there.03:19
loq_macok, so, i'd really like to make it03:19
brucerWould it be in US again?03:19
summerlongProbably, most people are there.03:19
loq_macbecause i'd like to be able to do a docs camp in aus this year03:19
loq_macpossibly coordinated with pycon03:19
chandankumarsummerlong, can i attend the bootcamp?03:20
loq_macbut my boss wants me to have gone to one before i can run one03:20
annegentleloq_mac: when's pycon?03:20
loq_macaugust, IIRC03:20
annegentlechandankumar: sure03:20
loq_macin brisbane03:20
summerlongThat's your manager's decision, chandankumar, but everyone is invited!03:20
annegentlechandankumar: sometimes we get funding from the Foundation too03:20
summerlongYES03:20
loq_mac:)03:20
chandankumarsummerlong, :)03:20
summerlongOf course, I'd love it to be in AUS!03:21
annegentleloq_mac: makes sense to go to one before hosting :) but they will change over time with the team makeup and so on03:21
*** banix has quit IRC03:21
annegentleloq_mac: for example I think the last one had a mix of real beginners and doc pros03:21
loq_machttp://2014.pycon-au.org/03:21
annegentleloq_mac: and I could send out the feedback from the last one03:21
brucerloq_mac: you helped run linuxconf, isnt that good enough?03:21
loq_macbrucer: very different event ;)03:21
summerlongCan't have too many social events, hey loq_mac?!03:21
loq_macannegentle: yes, i think it needs a lot more thought yet03:21
brucerno -is all herding cats03:22
loq_macof course not!03:22
summerlongFor me, Feb would be too soon, regardless of location.03:22
summerlongWe'd just be starting to implement summit decisions.03:22
loq_macyeah03:23
annegentlebrucer: +103:23
loq_macmarch would probably be better for me too03:23
summerlongkk, on to the next.03:23
summerlong#topic Operations Guide workflow03:23
*** openstack changes topic to "Operations Guide workflow (Meeting topic: DocTeamMeeting)"03:23
summerlongAnne is still in discussion with the O'Reilly folk, to figure out timing and process.03:23
summerlongGraeme Gillies has since volunteered to do the RHEL architecture.03:23
summerlongMight or might not be a 2-day sprint; Gillies will probably work online.03:23
summerlongAnything to talk about here?03:23
loq_maci'm cool03:23
summerlong#topic Doc tools updates03:24
*** openstack changes topic to "Doc tools updates (Meeting topic: DocTeamMeeting)"03:24
summerlongInfo from the last meeting:03:24
summerlongThe Clouddocs-maven-plugin is now in Stackforge.03:24
summerlong#link http://git.openstack.org/cgit/stackforge/clouddocs-maven-plugin/03:24
summerlongEnables all openstack contributors to work on the maven plugin that builds our HTML and PDF and api-ref output03:24
summerlongAlso, Rackspace just got 4 interns through the GNOME Outreach Program. So at least one more person helping with OpenStack upstream. In particular, helping Miranda Zhang will be helping Diane with the API docs.03:24
summerlong#link https://wiki.gnome.org/OutreachProgramForWomen/2013/DecemberMarch#Accepted_Participants03:24
summerlongAnd, Anne is working through doc templates for incubating projects.03:24
summerlongAnything else on doc tools?03:24
loq_maci'm still hassling michael davies on that03:24
*** jecarey has joined #openstack-meeting03:24
annegentleloq_mac: hehehe03:25
summerlongOn the script you talked about in the hangout?03:25
annegentlesummerlong: we did fix two build bugs that showed up today03:25
loq_macah, no, this is the guy who thought someone else was doing it03:25
loq_macso he backed off03:25
chandankumarsummerlong, i have started working on my blueprint but delayed due to bad health.03:25
summerlongOh, right.03:25
chandankumarfor askbot integration03:25
summerlongchandankumar: looking forward to seeing the result03:26
summerlongoookkkkk, that was it for doc tools?03:26
loq_macthat's all i have03:27
*** paragan has joined #openstack-meeting03:27
* summerlong wishes she knew more about doc tools03:27
summerlong#topic Open discussion03:27
*** openstack changes topic to "Open discussion (Meeting topic: DocTeamMeeting)"03:27
summerlongWishes? Thoughts?03:27
loq_maclots, but probably none relevant ;)03:27
summerlongPersonally, I'm wishing for the RH release date to come quickly so I can play upstream again.03:28
loq_macwhen is it?03:28
summerlongDec.1903:28
summerlongso the bug day falls well.03:28
loq_macooh, not long now!03:28
summerlongEXACTLY!03:28
loq_macwe need to set a date for our brisbane catchup, too03:28
summerlongYes, right after the new year, I'd think?03:28
loq_macyou don't want to do it before christmas?03:29
*** jcooley_ has joined #openstack-meeting03:29
*** mrodden has quit IRC03:29
loq_maci've got LCA in the new year, so wouldn't be able to do anything in the first half of jan, basically03:29
summerlonglet me check03:30
annegentleloq_mac: what's LCA?03:30
loq_maclinux.conf.au03:30
annegentleloq_mac: ah got it03:30
loq_mac:)03:30
annegentletoo many tlas!03:30
loq_mactoo right!03:30
summerlongSo, 20 is friday03:30
*** gokrokve has quit IRC03:31
annegentleI'm gonna be in and out Tues/Wed/Thurs. this week gettin' built into a team :)03:31
summerlongbelieve we're not here 23-24, brucer, is that right?03:31
*** markwash has joined #openstack-meeting03:31
annegentletrust falls and all that I'm sure03:31
*** gokrokve has joined #openstack-meeting03:31
summerlongshould know this, have only been looking at the release schedule.03:31
annegentleloq_mac: whatcha doing for lunch tomorrow? Want to meet?03:31
loq_macah, i see the problem03:31
brucerwell, RH does not have leave 23, 24 Dec, but depends who is taking03:32
annegentlesorry don't need to take up meeting time with lunch plans :)03:32
loq_macannegentle: np03:32
summerlongYeah, just feels like people might not be here, loq_mac.03:32
summerlongWill do when you get back, I guess.03:32
summerlongOk, anything else before we sign off?03:32
annegentleThank you for running the meeting summerlong!03:33
summerlongannegentle, my pleasure!03:33
loq_macyes, thanks summerlong :)03:33
loq_maci really appreciate you stepping in03:33
summerlongAlways good to learn something new :)03:33
summerlongciao!03:33
summerlong#endmeeting DocTeamMeeting03:33
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"03:33
openstackMeeting ended Tue Dec  3 03:33:58 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)03:34
openstackMinutes:        http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-12-03-03.00.html03:34
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-12-03-03.00.txt03:34
openstackLog:            http://eavesdrop.openstack.org/meetings/docteammeeting/2013/docteammeeting.2013-12-03-03.00.log.html03:34
chandankumarThank summerlong :)03:34
brucerTa Summer03:34
*** gokrokve has quit IRC03:35
*** mrodden has joined #openstack-meeting03:36
*** IlyaE has joined #openstack-meeting03:36
*** matsuhashi has quit IRC03:42
*** dims has quit IRC03:43
*** cdub has quit IRC03:43
*** nati_ueno has joined #openstack-meeting03:45
*** summerlong has left #openstack-meeting03:45
*** fnaval has joined #openstack-meeting03:45
*** cdub has joined #openstack-meeting03:45
*** sdake has quit IRC03:46
*** sdake has joined #openstack-meeting03:46
*** sdake has quit IRC03:46
*** sdake has joined #openstack-meeting03:46
*** brucer has left #openstack-meeting03:47
*** cdub has quit IRC03:51
*** loq_mac has quit IRC03:52
*** novas0x2a|laptop has quit IRC03:52
*** cdub has joined #openstack-meeting03:52
*** summerlong has joined #openstack-meeting03:53
*** gongysh has quit IRC03:54
*** loq_mac has joined #openstack-meeting03:57
*** esker has quit IRC03:58
*** loq_mac has quit IRC03:58
*** esker has joined #openstack-meeting03:59
*** rakhmerov has joined #openstack-meeting04:00
*** gokrokve has joined #openstack-meeting04:02
*** resker has joined #openstack-meeting04:03
*** otherwiseguy has joined #openstack-meeting04:03
*** esker has quit IRC04:03
*** loq_mac has joined #openstack-meeting04:05
*** loq_mac has quit IRC04:05
*** gokrokve has quit IRC04:06
*** resker has quit IRC04:08
*** loq_mac has joined #openstack-meeting04:11
*** weshay has quit IRC04:17
*** sandeepr has left #openstack-meeting04:17
*** Sukhdev has quit IRC04:19
*** michchap has quit IRC04:21
*** radsy has quit IRC04:21
*** michchap has joined #openstack-meeting04:21
*** maxdml has quit IRC04:22
*** colinmcnamara has joined #openstack-meeting04:24
*** colinmcn_ has joined #openstack-meeting04:24
*** matsuhashi has joined #openstack-meeting04:25
*** bdpayne has joined #openstack-meeting04:26
*** colinmcn_ has quit IRC04:29
*** colinmcnamara has quit IRC04:29
*** gokrokve has joined #openstack-meeting04:31
*** rongze has quit IRC04:31
*** jecarey has quit IRC04:33
*** IlyaE has quit IRC04:35
*** gokrokve has quit IRC04:36
*** herndon_ has quit IRC04:43
*** DinaBelova has joined #openstack-meeting04:56
*** DennyZhang has joined #openstack-meeting04:57
*** sarob has joined #openstack-meeting04:57
*** DinaBelova has quit IRC04:57
*** matsuhashi has quit IRC05:00
*** radsy has joined #openstack-meeting05:03
*** jcoufal has joined #openstack-meeting05:07
*** matsuhashi has joined #openstack-meeting05:08
*** danwent has joined #openstack-meeting05:08
*** Abhishek has quit IRC05:09
*** markpeek has joined #openstack-meeting05:09
*** nono1_ has joined #openstack-meeting05:10
*** ryanpetrello has joined #openstack-meeting05:11
*** ryanpetrello has quit IRC05:12
*** ryanpetrello has joined #openstack-meeting05:13
*** markwash has quit IRC05:16
*** summerlong has left #openstack-meeting05:17
*** nono1_ has quit IRC05:17
*** sacharya has quit IRC05:17
*** ryanpetrello has quit IRC05:17
*** crank has quit IRC05:26
*** matsuhashi has quit IRC05:27
*** crank has joined #openstack-meeting05:31
*** DennyZhang has quit IRC05:31
*** gokrokve has joined #openstack-meeting05:32
*** jaypipes has quit IRC05:33
*** loq_mac has quit IRC05:34
*** gokrokve has quit IRC05:37
*** garyk has quit IRC05:45
*** SergeyLukjanov has joined #openstack-meeting05:48
*** markpeek has quit IRC05:50
*** sarob has quit IRC05:51
*** sarob has joined #openstack-meeting05:51
*** jaypipes has joined #openstack-meeting05:54
*** sarob has quit IRC05:56
*** matsuhashi has joined #openstack-meeting05:59
*** ArxCruz has quit IRC06:00
*** markwash has joined #openstack-meeting06:02
*** neelashah has quit IRC06:06
*** bdpayne has quit IRC06:07
*** coolsvap has joined #openstack-meeting06:08
*** DennyZhang has joined #openstack-meeting06:08
*** bdpayne has joined #openstack-meeting06:13
*** mmcgrath has quit IRC06:15
*** skraynev has quit IRC06:17
*** Abhishek has joined #openstack-meeting06:20
*** sarob has joined #openstack-meeting06:22
*** skraynev has joined #openstack-meeting06:22
*** noslzzp has quit IRC06:25
*** SergeyLukjanov has quit IRC06:27
*** yfujioka has joined #openstack-meeting06:31
*** gongysh has joined #openstack-meeting06:31
*** gokrokve has joined #openstack-meeting06:33
*** jpeeler has quit IRC06:34
*** fungi has quit IRC06:35
*** fungi has joined #openstack-meeting06:36
*** jpeeler has joined #openstack-meeting06:37
*** gokrokve has quit IRC06:37
*** sarob has quit IRC06:38
*** Mandell has joined #openstack-meeting06:40
*** yamahata_ has joined #openstack-meeting06:46
*** otherwiseguy has quit IRC06:47
*** vkozhukalov has quit IRC06:47
*** denis_makogon has joined #openstack-meeting06:48
*** radsy has quit IRC06:54
*** garyk has joined #openstack-meeting06:56
*** Abhishek has quit IRC07:06
*** Abhishek has joined #openstack-meeting07:07
*** coolsvap has quit IRC07:07
*** coolsvap has joined #openstack-meeting07:07
*** yamahata_ has quit IRC07:07
*** coolsvap is now known as coolsvap_awap07:09
*** coolsvap_awap is now known as coolsvap_away07:09
*** doron_afk has joined #openstack-meeting07:09
*** sdake_ has quit IRC07:09
*** ryanpetrello has joined #openstack-meeting07:13
*** bdpayne has quit IRC07:14
*** jlibosva has joined #openstack-meeting07:15
*** mrunge has joined #openstack-meeting07:16
*** lsmola has joined #openstack-meeting07:16
*** mrunge has quit IRC07:17
*** akuznetsov has quit IRC07:17
*** mrunge has joined #openstack-meeting07:17
*** radix_ has joined #openstack-meeting07:17
*** ryanpetrello has quit IRC07:19
*** sarob has joined #openstack-meeting07:22
*** belmoreira has joined #openstack-meeting07:24
*** DinaBelova has joined #openstack-meeting07:24
*** ArthurBerezin has joined #openstack-meeting07:26
*** ArthurBerezin has left #openstack-meeting07:27
*** vipul has quit IRC07:32
*** vipul has joined #openstack-meeting07:33
*** gokrokve has joined #openstack-meeting07:33
*** gokrokve_ has joined #openstack-meeting07:35
*** jcooley_ has quit IRC07:35
*** jcooley_ has joined #openstack-meeting07:36
*** Fdot has joined #openstack-meeting07:37
*** gokrokve has quit IRC07:38
*** gokrokve_ has quit IRC07:40
*** Abhishek has quit IRC07:41
*** jhenner has joined #openstack-meeting07:44
*** nprivalova has joined #openstack-meeting07:46
*** DennyZhang has quit IRC07:52
*** fbo_away is now known as fbo07:52
*** jtomasek has joined #openstack-meeting07:54
*** vuil has joined #openstack-meeting07:54
*** sarob has quit IRC07:55
*** garyk has quit IRC07:57
*** vuil has quit IRC08:00
*** flaper87|afk is now known as flaper8708:03
*** aloga has quit IRC08:05
*** jtomasek has quit IRC08:07
*** jtomasek has joined #openstack-meeting08:09
*** jhenner has quit IRC08:11
*** avishayb has joined #openstack-meeting08:12
*** danwent has quit IRC08:15
*** sarob has joined #openstack-meeting08:22
*** SergeyLukjanov has joined #openstack-meeting08:23
*** sushil_ has joined #openstack-meeting08:24
*** vkozhukalov has joined #openstack-meeting08:27
*** ihrachyska has quit IRC08:29
*** Mandell has quit IRC08:29
*** Mandell has joined #openstack-meeting08:31
*** Mandell has quit IRC08:31
*** gokrokve has joined #openstack-meeting08:36
*** jcooley_ has quit IRC08:36
*** jcooley_ has joined #openstack-meeting08:38
*** gokrokve has quit IRC08:40
*** denis_makogon has quit IRC08:42
*** sjing has quit IRC08:49
*** ArxCruz has joined #openstack-meeting08:50
*** jorisroovers has joined #openstack-meeting08:53
*** nati_ueno has quit IRC08:56
*** sarob has quit IRC08:56
*** derekh has joined #openstack-meeting08:57
*** ikhudoshyn has quit IRC09:00
*** coolsvap_away has quit IRC09:01
*** ikhudoshyn has joined #openstack-meeting09:02
*** rpodolyaka has quit IRC09:02
*** ygbo has joined #openstack-meeting09:03
*** boris-42 has joined #openstack-meeting09:03
*** rpodolyaka has joined #openstack-meeting09:04
*** jroovers has joined #openstack-meeting09:05
*** jorisroovers has quit IRC09:05
*** ndipanov has joined #openstack-meeting09:08
*** yassine has joined #openstack-meeting09:10
*** avishayb has quit IRC09:10
*** ttrifonov is now known as ttrifonov_zZzz09:11
*** ttrifonov_zZzz is now known as ttrifonov09:12
*** garyk has joined #openstack-meeting09:14
*** ryanpetrello has joined #openstack-meeting09:16
*** ryanpetrello has quit IRC09:20
*** sarob has joined #openstack-meeting09:22
*** sushil_ has quit IRC09:26
*** coolsvap_away has joined #openstack-meeting09:29
*** ilyashakhat_ has quit IRC09:31
*** ilyashakhat has quit IRC09:32
*** jroovers has quit IRC09:32
*** NikitaKonovalov has joined #openstack-meeting09:34
*** ihrachyska has joined #openstack-meeting09:34
*** jcooley_ has quit IRC09:34
*** lbragstad has quit IRC09:36
*** lbragstad has joined #openstack-meeting09:36
*** gokrokve has joined #openstack-meeting09:37
*** jhenner has joined #openstack-meeting09:37
*** rossella_s has joined #openstack-meeting09:40
*** gokrokve has quit IRC09:42
*** kushi_ has joined #openstack-meeting09:50
*** matsuhashi has quit IRC09:51
*** kui has quit IRC09:52
*** matsuhashi has joined #openstack-meeting09:54
*** kushi_ has quit IRC09:55
*** sarob has quit IRC09:55
*** jcooley_ has joined #openstack-meeting10:05
*** ilyashakhat has joined #openstack-meeting10:06
*** jcooley_ has quit IRC10:12
*** boris-42 has quit IRC10:13
*** sushil_ has joined #openstack-meeting10:13
*** gongysh has quit IRC10:14
*** yfujioka has quit IRC10:18
*** nprivalova has quit IRC10:20
*** marun has joined #openstack-meeting10:20
*** sarob has joined #openstack-meeting10:22
*** yamahata_ has joined #openstack-meeting10:26
*** coolsvap_away has quit IRC10:27
*** rongze has joined #openstack-meeting10:28
*** fbo is now known as fbo_away10:28
*** ccorrigan has quit IRC10:29
*** jcoufal has quit IRC10:34
*** paragan has quit IRC10:34
*** igormarnat_ has joined #openstack-meeting10:36
*** gokrokve has joined #openstack-meeting10:37
*** nprivalova has joined #openstack-meeting10:42
*** gokrokve has quit IRC10:43
*** ArthurBerezin has joined #openstack-meeting10:43
*** yamahata_ has quit IRC10:43
*** rongze has quit IRC10:46
*** ArthurBerezin has left #openstack-meeting10:48
*** avishayb has joined #openstack-meeting10:48
*** markmcclain has joined #openstack-meeting10:49
*** SvenDowideit has quit IRC10:55
*** sarob has quit IRC10:55
*** weshay has joined #openstack-meeting10:58
*** markmcclain has quit IRC11:00
*** markmcclain has joined #openstack-meeting11:00
*** rongze has joined #openstack-meeting11:03
*** jcooley_ has joined #openstack-meeting11:05
*** jcooley_ has quit IRC11:10
*** DinaBelova has quit IRC11:11
*** weshay has quit IRC11:11
*** jamespage_ has joined #openstack-meeting11:13
*** jamespage_ has quit IRC11:13
*** weshay has joined #openstack-meeting11:16
*** ryanpetrello has joined #openstack-meeting11:17
*** kui has joined #openstack-meeting11:17
*** weshay has quit IRC11:17
*** mrunge` has joined #openstack-meeting11:18
*** kmartin has quit IRC11:19
*** ryanpetrello has quit IRC11:22
*** ivar-lazzaro has quit IRC11:22
*** sarob has joined #openstack-meeting11:22
*** zhikunliu has joined #openstack-meeting11:25
*** boris-42 has joined #openstack-meeting11:27
*** jcoufal has joined #openstack-meeting11:31
*** gokrokve has joined #openstack-meeting11:38
*** rongze has quit IRC11:39
*** jtomasek has quit IRC11:39
*** jtomasek has joined #openstack-meeting11:39
*** fifieldt has quit IRC11:40
*** gokrokve has quit IRC11:43
*** jcooley_ has joined #openstack-meeting11:51
*** adalbas has joined #openstack-meeting11:53
*** rongze_ has joined #openstack-meeting11:56
*** sarob has quit IRC11:56
*** ttrifonov is now known as ttrifonov_zZzz11:57
*** dims has joined #openstack-meeting11:58
*** ttrifonov_zZzz is now known as ttrifonov11:59
*** DinaBelova has joined #openstack-meeting12:02
*** yaguang has quit IRC12:04
*** boris-42_ has joined #openstack-meeting12:05
*** rpodolyaka has quit IRC12:05
*** DinaBelova has quit IRC12:05
*** rpodolyaka has joined #openstack-meeting12:06
*** boris-42 has quit IRC12:08
*** cdub has quit IRC12:14
*** belmoreira has quit IRC12:14
*** cdub has joined #openstack-meeting12:16
*** sarob has joined #openstack-meeting12:22
*** crank has quit IRC12:24
*** belmoreira has joined #openstack-meeting12:25
*** jcooley_ has quit IRC12:25
*** igormarnat_ has quit IRC12:25
*** boris-42_ has quit IRC12:27
*** lsmola has quit IRC12:30
*** crank has joined #openstack-meeting12:30
*** markmcclain has quit IRC12:30
*** beagles has joined #openstack-meeting12:31
*** markmcclain has joined #openstack-meeting12:32
*** jamespage_ has joined #openstack-meeting12:33
*** boris-42 has joined #openstack-meeting12:33
*** crank has quit IRC12:35
*** crank has joined #openstack-meeting12:36
*** markmcclain has quit IRC12:36
*** tsufiev has quit IRC12:38
*** akuznetsov has joined #openstack-meeting12:38
*** jamespage_ has quit IRC12:39
*** gokrokve has joined #openstack-meeting12:39
*** tsufiev has joined #openstack-meeting12:39
*** markmcclain has joined #openstack-meeting12:40
*** crank has quit IRC12:41
*** comay has quit IRC12:42
*** gokrokve has quit IRC12:44
*** lsmola has joined #openstack-meeting12:47
*** crank has joined #openstack-meeting12:48
*** rdxc has joined #openstack-meeting12:51
*** adalbas has quit IRC12:52
*** doron_afk is now known as doron12:53
*** comay has joined #openstack-meeting12:54
*** markvoelker1 has joined #openstack-meeting12:55
*** pdmars has joined #openstack-meeting12:55
*** sarob has quit IRC12:55
*** fbo_away is now known as fbo12:56
*** mrunge is now known as mrunge_away12:57
*** mrunge_away has quit IRC12:57
*** dkranz has joined #openstack-meeting12:58
*** maxdml has joined #openstack-meeting12:58
*** yaguang has joined #openstack-meeting12:58
*** SpamapS has quit IRC12:59
*** jhenner has quit IRC13:01
*** noslzzp has joined #openstack-meeting13:01
*** jhenner has joined #openstack-meeting13:01
*** ryanpetrello has joined #openstack-meeting13:02
*** paragan has joined #openstack-meeting13:02
*** rossella_s has quit IRC13:04
*** jcooley_ has joined #openstack-meeting13:08
*** yamahata_ has joined #openstack-meeting13:08
*** adalbas has joined #openstack-meeting13:09
*** dolphm has joined #openstack-meeting13:11
*** jcooley_ has quit IRC13:13
*** dolphm has quit IRC13:16
*** weshay has joined #openstack-meeting13:18
*** dims has quit IRC13:21
*** ayoung has quit IRC13:22
*** sarob has joined #openstack-meeting13:22
*** jdob has joined #openstack-meeting13:23
*** jcooley_ has joined #openstack-meeting13:23
*** aguzikova has joined #openstack-meeting13:23
*** rossella_s has joined #openstack-meeting13:23
*** sandywalsh has quit IRC13:24
*** dims has joined #openstack-meeting13:25
*** rossella_s has quit IRC13:26
*** rossella-s has joined #openstack-meeting13:26
*** aguzikova has quit IRC13:27
*** dolphm has joined #openstack-meeting13:28
*** jcooley_ has quit IRC13:28
*** aguzikova has joined #openstack-meeting13:29
*** zul has quit IRC13:29
*** aguzikova has quit IRC13:30
*** aguzikova has joined #openstack-meeting13:30
*** zul has joined #openstack-meeting13:31
*** tedross has joined #openstack-meeting13:34
*** tedross has left #openstack-meeting13:34
*** jdob has quit IRC13:35
*** sandywalsh has joined #openstack-meeting13:36
*** jdob has joined #openstack-meeting13:37
*** kui has quit IRC13:37
*** gokrokve has joined #openstack-meeting13:40
*** matsuhashi has quit IRC13:40
*** thomasem has joined #openstack-meeting13:40
*** inkerra has joined #openstack-meeting13:41
*** rossella-s has quit IRC13:43
*** rossella_s has joined #openstack-meeting13:44
*** venkatesh has joined #openstack-meeting13:44
*** aguzikov1 has joined #openstack-meeting13:44
*** gokrokve has quit IRC13:44
*** aguzikova has quit IRC13:47
*** rakhmerov has quit IRC13:51
*** inkerra_ has joined #openstack-meeting13:51
*** inkerra_ has quit IRC13:51
*** jdob has quit IRC13:51
*** jtomasek has quit IRC13:52
*** jdob has joined #openstack-meeting13:52
*** rakhmerov has joined #openstack-meeting13:52
*** DinaBelova has joined #openstack-meeting13:55
*** sarob has quit IRC13:55
*** jtomasek has joined #openstack-meeting13:56
*** rakhmerov has quit IRC13:57
*** aguzikova has joined #openstack-meeting13:58
*** dprince has joined #openstack-meeting13:59
*** SergeyLukjanov has quit IRC14:00
*** aguzikova has quit IRC14:00
*** aguzikova has joined #openstack-meeting14:00
*** markvoelker1 has quit IRC14:00
*** jasondotstar has joined #openstack-meeting14:01
*** julim has joined #openstack-meeting14:01
*** doron is now known as doron_afk14:02
*** inkerra__ has joined #openstack-meeting14:02
*** avishayb has quit IRC14:03
*** doron_afk is now known as doron14:03
*** inkerra__ has quit IRC14:03
*** inkerra_ has joined #openstack-meeting14:03
*** DinaBelova has quit IRC14:03
*** inkerra_ has quit IRC14:04
*** aguzikova has quit IRC14:04
*** reaper has joined #openstack-meeting14:04
*** jeckersb_gone is now known as jeckersb14:04
*** aguzikov1 has quit IRC14:04
*** inkerra has quit IRC14:05
*** inkerra has joined #openstack-meeting14:05
*** dperaza has joined #openstack-meeting14:05
*** NikitaKonovalov has quit IRC14:06
*** neelashah has joined #openstack-meeting14:06
*** lblanchard has joined #openstack-meeting14:08
*** dvarga has joined #openstack-meeting14:08
*** inkerra has quit IRC14:08
*** inkerra has joined #openstack-meeting14:09
*** avishayb has joined #openstack-meeting14:10
*** markmcclain has quit IRC14:10
*** DrBacchus has joined #openstack-meeting14:11
*** fnaval has quit IRC14:11
*** fnaval has joined #openstack-meeting14:12
*** inkerra_ has joined #openstack-meeting14:14
*** inkerra_ has quit IRC14:15
*** krtaylor has quit IRC14:15
*** jcooley_ has joined #openstack-meeting14:17
*** dkranz has quit IRC14:18
*** ArthurBerezin has joined #openstack-meeting14:19
*** jhenner has quit IRC14:19
*** nosnos has quit IRC14:20
*** lbragstad has quit IRC14:20
*** jcooley_ has quit IRC14:21
*** sarob has joined #openstack-meeting14:22
*** sacharya has joined #openstack-meeting14:23
*** banix has joined #openstack-meeting14:24
*** safchain has joined #openstack-meeting14:26
*** DrBacchus has quit IRC14:27
*** rongze_ has quit IRC14:27
*** reaper has quit IRC14:28
*** jhenner has joined #openstack-meeting14:32
*** krtaylor has joined #openstack-meeting14:33
*** salv-orlando has quit IRC14:33
*** ihrachyska has quit IRC14:34
*** ihrachyska has joined #openstack-meeting14:35
*** rdxc has quit IRC14:36
*** stevemar has joined #openstack-meeting14:37
*** doron is now known as doron_afk14:37
*** radez_g0n3 is now known as radez14:37
*** rdxc has joined #openstack-meeting14:37
*** rongze has joined #openstack-meeting14:38
*** gokrokve has joined #openstack-meeting14:40
*** amotoki has quit IRC14:41
*** akuznetsov has quit IRC14:44
*** sarob has quit IRC14:45
*** johnthetubaguy has joined #openstack-meeting14:45
*** gokrokve has quit IRC14:45
*** markpeek has joined #openstack-meeting14:46
*** zhikunliu has quit IRC14:47
*** nprivalova has quit IRC14:47
*** dolphm has quit IRC14:48
*** ruhe has joined #openstack-meeting14:49
*** lbragstad has joined #openstack-meeting14:50
*** rakhmerov has joined #openstack-meeting14:53
*** sacharya has quit IRC14:53
*** toan-tran has joined #openstack-meeting14:53
*** vijendar has joined #openstack-meeting14:54
*** esker has joined #openstack-meeting14:55
*** sarob has joined #openstack-meeting14:55
*** dolphm has joined #openstack-meeting14:58
*** shane-wang has joined #openstack-meeting14:58
*** PaulMurray has joined #openstack-meeting14:58
*** dolphm has quit IRC14:58
*** krtaylor has quit IRC14:58
*** fkak has quit IRC14:59
*** dolphm has joined #openstack-meeting14:59
*** mspreitz has joined #openstack-meeting14:59
*** jgallard has joined #openstack-meeting14:59
*** jecarey has joined #openstack-meeting14:59
*** jeckersb is now known as jeckersb_gone14:59
*** RobinWang has joined #openstack-meeting15:00
*** sarob has quit IRC15:00
*** markvan has joined #openstack-meeting15:00
n0ano#startmeeting scheduler15:00
openstackMeeting started Tue Dec  3 15:00:26 2013 UTC and is due to finish in 60 minutes.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.15:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.15:00
*** openstack changes topic to " (Meeting topic: scheduler)"15:00
openstackThe meeting name has been set to 'scheduler'15:00
n0anohello all, anyone here for the scheduler meeting?15:00
garykhi15:00
PaulMurrayhello15:00
mspreitzhi15:00
bauzashi15:00
shane-wanghi15:01
*** afazekas has joined #openstack-meeting15:01
garykare alaski and boris-42 around?15:01
n0anoboris-42, alaski  - are you here?15:01
alaskihi15:02
PaulMurraygaryk I'd like to get a mention in for my blueprint later15:02
toan-tranhi15:02
toan-tranall15:02
garykjust wanted to be sure because a lot of the discuss on the ML about thte scheduler forklift is related to items that they are working on.15:02
garykPaulMurray: n0ano is leading :)15:03
PaulMurraysorry - n0ano15:03
garykPaulMurray: np, I am just heckling from the sidelines now15:03
PaulMurrayyou just seem to authoritative :)15:03
*** Loquacity has quit IRC15:04
*** tianst has joined #openstack-meeting15:04
garyknah.15:04
n0anosorry guys, you can't do much when the battery on your mouse dies :-(15:04
* n0ano remembers when a mouse was just a rodent15:04
*** jeckersb_gone is now known as jeckersb15:04
boris-42garyk hi15:04
*** Loquacity has joined #openstack-meeting15:04
n0anoboris-42, excellent15:04
n0ano#topic memcached based scheduler15:04
*** openstack changes topic to "memcached based scheduler (Meeting topic: scheduler)"15:04
jgallardhi15:04
garykboris-42: just in time :)15:05
boris-42yep15:05
n0anoboris-42, so, do you have any update on the status of your scheduler changes15:05
boris-42n0ano yep I have some15:06
boris-42n0ano so we are now working on bunch of patches15:06
boris-42n0ano let me find the links sorry15:06
*** gokrokve has joined #openstack-meeting15:07
boris-42n0ano here is it https://review.openstack.org/#/c/45867/15:07
boris-42n0ano so there were a lot of changes from start of work15:07
garykboris-42: are there any core guys signed up to review this?15:07
boris-42n0ano first of all we are trying to add garbage collector (because previously memcahced objects weren't deleted)15:08
garyki really think that if we are serious about the forkilft and this is one of the blocking items then we need russellb to try and ensure that there are cores involved here.15:08
johnthetubaguyits worth setting a milestone on that BP, and we can get people signed up and approved15:08
boris-42n0ano the second change is that we will soon finish work around sqlalchemy backend15:08
alaskigaryk: no, the bp isn't sponsored at this point15:08
garykwhat do you guys think?15:08
garykalaski: thaks for the clarification15:09
*** BillArnold has joined #openstack-meeting15:09
n0anoI think it's a great idea but I'm not core so how do we get someone like that on board?15:09
boris-42johnthetubaguy done15:09
johnthetubaguyas long as we keep the old and new present I am happy with the idea15:09
*** ayoung has joined #openstack-meeting15:09
johnthetubaguyboris-42: cool15:09
boris-42ndipanov is looking at this patch15:10
n0anojohnthetubaguy, since the basic idea is to remove references to the DB I'm not sure we can keep the old and new present15:10
boris-42johnthetubaguy yep there should be switch between 2 approaches15:10
boris-42johnthetubaguy in some moment new scheduler should use own DB15:11
johnthetubaguyn0ano: but we just need "scheduler" update driver framework, and swap between the two15:11
boris-42johnthetubaguy we just need to run new code of scheduler and it will collect all data15:11
johnthetubaguyboris-42: exactly, the pull out of the scheduler needs the same entry points (I think)15:11
johnthetubaguyah, OK, that works15:11
boris-42johnthetubaguy hmm not sure that I undertand=)15:11
ndipanovboris-42, which patch?15:12
boris-42ndipanov scheduler15:12
*** rfolco has quit IRC15:12
n0anoI wouldn't think any of the APIs change, just the internal implementation15:12
boris-42ndipanov with memcached15:12
johnthetubaguyboris-42: which blueprint is this, I don't see the no-db-scheduler one updated15:12
ndipanovboris-42, well... among others15:12
boris-42johnthetubaguy https://blueprints.launchpad.net/nova/+spec/no-db-scheduler15:12
ndipanovboris-42, but yeah - will follow up15:12
johnthetubaguyboris-42: need to set the milestone target to trigger to process15:13
boris-42ndipanov thanks, we will fix all issues I hope soon15:13
boris-42ndipanov there was a lot of refactoring since first solution15:13
boris-42ndipanov name_spaces, garbage collector, mysql backend..15:13
ndipanovboris-42, yeah I saw that there was good work being done15:13
ndipanovboris-42, but couldn't manage to catch up :15:13
ndipanov(15:13
*** debo_os has joined #openstack-meeting15:14
boris-42ndipanov we will call you when we address all stuff15:14
n0anoback to johnthetubaguy concerns, can we easily set this up to support both old & new schemes15:14
boris-42ndipanov so you will save a lot of review time =)15:14
boris-42n0ano actually yes15:15
ndipanovboris-42, I'll check it out to stay informed15:15
boris-42n0ano we could update nova.db and scheduler.db in the same time15:15
boris-42johnthetubaguy ^15:15
*** doron_afk is now known as doron15:15
boris-42n0ano so we could move step by step from one scheduler to another15:15
*** nprivalova has joined #openstack-meeting15:16
boris-42n0ano but I am not sure that it will be super easy to move from one Scheduler to another without this small steps (patch by patch)15:16
n0anoso you'd make it switchable/configurable to update the memcached or DB or both15:16
boris-42n0ano no I mean that first patch (where we are going to switch to new scheduler)15:16
boris-42will still have the nova.db tables that are updated15:17
*** jcooley_ has joined #openstack-meeting15:17
boris-42and after it we will remove at all tables and use data from scheduler15:17
johnthetubaguyyeah, I kinda would expect patches to add the entry points the new scheduler needs, then adding the alternatives for the new scheduler, and then extra tests in the gate for the new scheduler?15:17
*** jcoufal has quit IRC15:17
boris-42johnthetubaguy it will a bit hard to organize support of two schema but we could try15:18
*** dkranz has joined #openstack-meeting15:18
boris-42johnthetubaguy but at the end when we totally switch from one to another scheduler (in code)15:18
boris-42johnthetubaguy updating from example havana to icehouse will require some arch changes15:18
*** ArthurBerezin has quit IRC15:19
boris-42johnthetubaguy like switching from nova-network to neutron (but not so big hard and complex)15:19
*** avishayb has quit IRC15:19
n0anoso we have to be aware that the first version will actually be a little slower (it modifies both the DB & memcached) but will be better in the future15:19
johnthetubaguyhmm, I see, but why not create a brand new DB for the new stuff?15:19
shane-wangboris-42: will you merge the code after forklift?15:19
*** sacharya has joined #openstack-meeting15:19
boris-42shane-wang it will be easily for all us to make this change before15:20
boris-42shane-wang because then it will be much easily to grab code from nova15:20
boris-42johnthetubaguy I mean you have all data in nova.db and then data will be stored in another place15:20
boris-42johnthetubaguy if you turnoff scheduler and run new version15:21
PaulMurrayboris-42 can't it be configurable instead of doing both15:21
boris-42johnthetubaguy after 60 sec delay you will have all updated data in your new scheduler15:21
PaulMurray?15:21
boris-42PaulMurray what exactly?15:21
PaulMurrayI'm not sure if I follow exactly15:21
boris-42johnthetubaguy let me try to describe the order of patches15:21
*** jcooley_ has quit IRC15:21
boris-42PaulMurray &15:21
PaulMurraywhat I have in mind is that we follow trunk15:21
johnthetubaguyboris-42: Yeah, that seems fine, I am just wanting to have both schedulers as an option, the data can be in different places15:22
mspreitzPaulMurray: are you concerned about migrating a running system, or about retaining ability to run old code in case new code has a problem?15:22
PaulMurrayit would be good to keep up to date without haveing to switch15:22
PaulMurraywhile testing out new version15:22
johnthetubaguyPaulMurray: +115:22
garyk+115:22
boris-421 sec15:22
*** sarob has joined #openstack-meeting15:22
PaulMurraythen when we are happy, we switch15:22
PaulMurrayeventually support for old way can be removed15:22
debo_os+115:22
johnthetubaguywe need to have the scheduler pluggable, so people can test and switch as required15:22
johnthetubaguywe don't need data migration, assuming it self-heals15:23
boris-42Guys what I think is that there will be duplication of code15:23
toan-tranPaul: by swithching you mean in the configuration first?15:23
boris-42Let me explain step by step15:23
*** fnaval has quit IRC15:23
boris-42in code15:23
johnthetubaguythen rescructure the code, so it shares common libs15:23
boris-421 patch: add synchronizer15:23
boris-422 patch: call not only db.compute_node_update but also new scheduler rpc method host_update15:23
johnthetubaguyinstead of 2, add a driver for "send_update" with two implementations?15:24
n0anojohnthetubaguy, let him finish, I think there's more15:24
boris-423 patch: drop compute_nodes tables/ and db.compute_node_update call and get db.api data from scheduler15:24
boris-424 patch: remove db.api calls and call scheduler directly for host states15:25
PaulMurrayboris-42: I see, you're describing an update process, yes?15:25
johnthetubaguybut you could have a "get_stats" driver too, with one from memcache, the other from DB right?15:25
boris-42johnthetubaguy not sure15:26
n0anojohnthetubaguy, what would be the advantage of that15:26
boris-42johnthetubaguy what you mean by get_stats15:26
johnthetubaguyn0ano: we have the old and new behind a common interface, just flick a switch between them15:26
boris-42johnthetubaguy I mean we could just change step by step backend of scheduler without tracking anything15:26
*** rakhmerov has quit IRC15:27
n0anocurrent scheme is to have both at the same time, no need for a switch15:27
PaulMurrayjohnthetubaguy: are you thinking because stats is high overhead? but rest is same as usual?15:27
PaulMurrayor because new features?15:27
boris-42PaulMurray johnthetubaguy  there won't be anymore stats actually15:28
boris-42PaulMurray johnthetubaguy we will store json like objects15:28
PaulMurrayyes - but I think he is suggesting two paths15:28
PaulMurrayto scheduler15:28
PaulMurraywondering why15:28
boris-42PaulMurray johnthetubaguy first strcture will be the same as now services, compute_node, compute_node_stats15:28
toan-tranboris: if we create a synchronizer inside nova, then after switching we have to remove it?15:28
boris-42toan-tran it is not in nova15:29
boris-42toan-tran it is inside scheduler15:29
johnthetubaguymaybe its just I don't want two schedulers running at once, but maybe thats OK15:29
boris-42toan-tran and the goal is to grab all code15:29
boris-42johnthetubaguy I am not sure that there will be 2 scheduler in the same15:29
toan-tranboris: then who calls synchronizer? nova-conductor? and how?15:29
n0anojohnthetubaguy, I don't think there's 2 schedulers, one scheduler storing data in 2 places15:29
boris-42n0ano yep one scheduler that could store all data from all services15:30
toan-tranboris: do we have to create new interface for this synchonrizer?15:30
boris-42toan-tran synchronizer is internal part of scheduler15:30
*** venkatesh has quit IRC15:30
*** schwicht has joined #openstack-meeting15:30
boris-42toan-tran scheduler has special RPC method update_host_state that will call synchronizer15:30
boris-42toan-tran this RPC method could be called from anywhere compute node, cinders nodes15:31
*** paragan has quit IRC15:31
johnthetubaguywell they sound like two implementations of the same thing, we generally encapsulate those inside driver objects, we could run both, thats just a multi driver driver.15:31
n0anocorrect me if I'm wrong, but the synchronizer keeps multiple schedulers in sync (needed since there will no longer be a DB to do that)15:31
boris-42n0ano yep15:31
boris-42n0ano all data is stored locally on each scheduler15:31
boris-42n0ano plus mechanism that syncs states15:32
boris-42n0ano one scheduler is processing one host_update message15:32
boris-42n0ano and then all are synced using synchronizer15:32
*** radez is now known as radez_g0n315:32
n0anoavoids the fan-out problem with schduler update messages15:33
boris-42n0ano much more effective then just grab all data from DB on each request15:33
*** rfolco has joined #openstack-meeting15:33
boris-42n0ano yep exactly15:33
boris-42n0ano add more schedulers and process more messages =)15:33
johnthetubaguythis is all good, my only request is to have it optional in Icehouse15:33
*** zbitter is now known as zaneb15:33
boris-42johnthetubaguy I am not a PTL15:33
*** akuznetsov has joined #openstack-meeting15:33
toan-tranboris: ok so all schedulers will use this synchronizer to update its db15:34
boris-42johnthetubaguy so I can't guarantee =)15:34
boris-42toan-tran there is no DB15:34
n0anotoan-tran, update it's internal data, not a database15:34
johnthetubaguyboris-42 sure, but code wise, thats all I mean15:34
boris-42toan-tran there is just local object in each scheduler that contains state of workld15:34
boris-42johnthetubaguy we will try to implement it ASAP15:34
boris-42=)15:34
*** nelsnelson has joined #openstack-meeting15:35
boris-42johnthetubaguy and then let's community/cores/PTL make decission15:35
*** otherwiseguy has joined #openstack-meeting15:35
*** shane-wang has quit IRC15:35
*** krtaylor has joined #openstack-meeting15:35
boris-42toan-tran and then synchronizer is used to update these local objects15:35
*** venkatesh has joined #openstack-meeting15:35
johnthetubaguyboris-42: agreed, I just want to keep the options open15:35
*** rakhmerov has joined #openstack-meeting15:35
n0anojohnthetubaguy, how optional does this have to be - is `keep the current DB tables updated but don't use them' acceptable15:36
johnthetubaguyI don't think they need updating15:36
johnthetubaguyunless you have to read from them15:36
boris-42n0ano it is just to make baby step implementation of new scheduler15:36
*** jlibosva has quit IRC15:36
*** ruhe has quit IRC15:36
n0anonote that we're not talking about changing any APIs, this is all internal implementation inside the scheduler15:36
*** shanewang has joined #openstack-meeting15:37
*** dolphm has quit IRC15:37
boris-42n0ano actually we are adding new RPC methods in scheduler15:37
toan-tranboris: ok, that's why it is absolutely necessary that your blueprint is merged before forking15:37
boris-42toan-tran yep it will totally simplify work15:37
n0anoboris-42, but that's just scheduler to scheduler, not seen by any other entity15:37
boris-42toan-tran actually we already try to make oslo.scheduler15:37
boris-42toan-tran and we failed because all internal stuff is deeply connected with project logic15:38
johnthetubaguytoan-tran: or build it in the fork, maybe15:38
*** ruhe has joined #openstack-meeting15:38
boris-42johnthetubaguy it will be hard just believe me+)15:38
boris-42johnthetubaguy we already tried to make this stuff, and failed=(15:38
*** ArthurBerezin has joined #openstack-meeting15:38
boris-42n0ano actually no, there is the new RPC method that is called from compute_nodes15:38
*** dcramer__ has joined #openstack-meeting15:38
boris-42n0ano or cinder or any other place15:38
boris-42n0ano to update host_state15:39
*** sacharya has quit IRC15:39
n0anoboris-42, hmmm, that will require carefull consideration then, that's a significant change15:39
boris-42n0ano it is not API, it's internal stuff (like changes in conductor)15:39
*** shane-wang has joined #openstack-meeting15:39
boris-42n0ano I don't think that such changes are pretty big, we don't change public API of services (like nova boot)15:40
n0anobut there is already an RPC to do that, why do you need a new one15:40
toan-tranboris-42: ok for compute_node_update, then what does nova do for get compute's info?15:41
boris-42n0ano where https://github.com/openstack/nova/blob/master/nova/scheduler/rpcapi.py ?15:41
*** dolphm has joined #openstack-meeting15:41
PaulMurraySome of this stuff will go behind objects - compute manager wont call conductor directly15:41
boris-42toan-tran move will ask scheduler about info about all compute_nodes15:41
boris-42PaulMurray compute manager want call conductor at all15:41
PaulMurraythe objects are remotable15:41
boris-42PaulMurray conductor is nova stuff15:42
boris-42PaulMurray I just don't understand why we need conductor or object heres15:42
boris-42PaulMurray object are nova.db, conductor is nova stuff15:42
PaulMurrayWhat I mean is the db calls are behind objects15:42
toan-tranboris-42: that would be another challenge to consider if we want to maintain 2 versions of schedulers: nova and new one during transition15:42
boris-42PaulMurray there is no DB calls in our new approach15:42
PaulMurrayyou can switch implementation of objects pretty easy without changing main code15:42
toan-tranboris-42 currently nova does not need scheduler15:43
shane-wangboris-42: compute manager will call objects15:43
johnthetubaguyyeah, the conductor calls the scheduler for which host to pick, are we changing that call? that seems bad?15:43
boris-42toan-tran ?15:43
toan-tranboris-42 to search for data15:43
boris-42toan-tran yep but it need scheduler to schedule=)15:43
boris-42toan-tran so it should be just a bit of refactoring "where" to get data15:43
boris-42johnthetubaguy there will be no condcutor15:44
boris-42johnthetubaguy compute node calls scheduler dirrectly15:44
boris-42johnthetubaguy make RPC call15:44
PaulMurrayI think we're thinking at two levels here15:44
alaskiboris-42: which RPC call are you talking about on the compute node15:44
toan-tranboris-42 as the mater of fact, nova get direct access to its DB, so if we want it to call scheduler, we have to introduce a new method15:44
PaulMurraycompute node will deal with objects15:44
johnthetubaguyboris-42: right, I agree with that, I think, its two points here though15:44
boris-42lol)15:44
boris-424 questions / sec=)15:44
PaulMurrayhow data moves areound is implemnetation detail15:44
toan-tranfor instances, migration with destination does not need scheduler15:45
debo_oshonestly there are 2 issues …. foklifting the decision making (on where to place the resources) and forklifting the code to make that prpocess clean… During the last summit a bunch of us already demo-ed how the 1st problem has been already solved …15:45
*** vkozhukalov has quit IRC15:45
debo_osout here we should spend some time talking about both IMO15:45
toan-trannova verifies directly if the destination can host the VM15:45
toan-tranby consulting its DB15:45
boris-42toan-tran yep nova scheduler will response about all statuses of compute nodes15:46
boris-42toan-tran so it should have methods15:46
boris-42toan-tran RPC methods for that15:46
johnthetubaguytoan-tran: the newer code uses an RPC call in the conductor to the scheudler to pick which node to use, the scheduler reads it from the nova db currently15:46
toan-tranboris-42: agreed15:46
boris-42alaski We are going to add few RPC methods in scheduler15:46
boris-42alaski so to store and keep all data about compute nodes inside scheduler instead of nova.db15:46
*** fnaval has joined #openstack-meeting15:46
debo_osboris-42 … could we make the store generic and not pegged to memcached15:47
boris-42alaski this will allow us to make scheduler in depend of project data15:47
johnthetubaguywe might want a different set of queues for the updates and the other scheduler requests?15:47
alaskiboris-42: ok, just making sure.  johnthetubaguy is talking about a call to the schduler from conductor, but you're talking about two different things15:47
boris-42alaski I am talking actually about that conductur is unnessacery here15:48
johnthetubaguyalaski: yeah, updates vs host picking, I am getting confused15:48
*** hemanthravi has joined #openstack-meeting15:48
alaskiboris-42: right, I agree15:48
*** eharney has joined #openstack-meeting15:48
boris-42alaski we are able to call from compute.manager directly scheduler15:48
johnthetubaguy+115:48
boris-42okay nice15:48
*** whenry has joined #openstack-meeting15:48
boris-42debo_os we are not going to store all data inside memcached15:48
*** yaguang has quit IRC15:49
boris-42debo_os memcached is used just to effectively sync states in different schedulers, and avoid fanaouts15:49
shane-wangboris-42: how will you deal with live-upgrade?15:49
debo_osboris-42: thx … it would be nice to have a query-able  state layer that can be used by anyone …15:49
*** ociuhandu has joined #openstack-meeting15:49
shane-wangboris-42: in future15:49
*** coolsvap has joined #openstack-meeting15:49
shane-wangboris-42: you probably need ojects between computes and schedulers?15:50
*** mrodden has quit IRC15:50
n0anoshane-wang, that's why the stepwise progression is to keep data in both memcache & DB to begin with, eventually deprecate/remove the DB15:50
garykboris-42: does you design document have all of the stages that you plan to implement. it would be nice if it did then we could use it as a refernce. the bigger picture would be nice here15:51
debo_os+115:51
n0anogaryk +115:51
*** SpamapS has joined #openstack-meeting15:51
garykthings just seem very fluid at the moment and there seem to be a ton of edge cases that we are discussing15:51
boris-42garyk we are working on it guys15:51
garykgreat. please post a update when you have it.15:51
boris-42garyk will be done15:52
debo_osboris-42: got it … am guessing the doc will have the clean API to query the state engine (whatever is behind it) ….15:52
n0anoI haven't seen any gaping holes, closing the edge cases is always the hard part15:52
garyksorry to be a stick in the mud but with something complex like this a little extra detail helps15:52
boris-42garyk I think that it could make understanding of our approach much more simplier15:52
garykboris-42: agreed15:52
toan-tran+115:52
boris-42yep yep15:52
jgallard+115:52
boris-42I hope that we will publish this week some stuff15:52
debo_osrequest: could we please have a slightly higher level picture in the document too15:52
*** Leon_ has joined #openstack-meeting15:53
boris-42debo_os sure15:53
n0anoprobably more to discuss on this but it's getting late, let's move on15:53
garykyou still have a few more days for a hanuka miracle :)15:53
shane-wangthat will help a lot15:53
shane-wangdocument15:53
n0anoI wanted to talk about the forklifting proposal from the mailing list but I don't know if we have time15:53
*** jmontemayor has joined #openstack-meeting15:53
n0ano#topic forlifting code15:53
*** openstack changes topic to "forlifting code (Meeting topic: scheduler)"15:53
n0anoseems to be a lot of talk about this, has it been decided to move the scheduler code to a separate repo?15:54
garykn0ano: i think that is the general idea15:54
*** hemanthravi has quit IRC15:54
alaskiyep, pretty much15:54
*** ivasev has joined #openstack-meeting15:55
*** hemanthravi has joined #openstack-meeting15:55
n0anoso, seems like the question is timing, who's going to do the work and when15:55
shane-wangand how many efforts do you expect?15:55
garyki think that it is going to be non trivial without an api - but others seem to differ15:55
debo_osI think we have a list of volunteers on the google doc page15:55
*** hemanthravi has quit IRC15:55
*** sarob has quit IRC15:55
alaskiA lot of people have signed up for the work.  I believe it's just currently waiting on one of my blueprints to be finished, which I'm hoping will be by this week15:55
debo_osgaryk: I think its best to let people come to the conclusion on their own :) I agree 10000%15:56
alaskihttps://etherpad.openstack.org/p/icehouse-external-scheduler has a list of volunteers15:56
*** hemanthravi has joined #openstack-meeting15:56
n0anodo we want to get boris-42 changes in before or after (or does it matter)15:56
debo_osBefore we start the coding, I think we should have an approved doc15:56
debo_oswhere we all agree on the plan … else its going to be messy15:56
alaskin0ano: honestly, I don't think it matters.  It would be nive to get it in before, but it's probably not going to happen15:57
johnthetubaguyalaski: +115:57
*** reed has joined #openstack-meeting15:57
n0anoI just don't want all changes to the scheduler to stop for an indetermine time waiting for the restructure15:57
*** markvan has quit IRC15:57
debo_oscould we please have the doc as a gate before ethe coding fest begins15:57
n0anodebo_os, +115:57
garyk+115:57
alaskin0ano: definitely a concern, but the plan is for work to continue but it may have to happen in two places15:58
shane-wang+115:58
debo_osand reviewed/approived :)15:58
toan-trancan we add plan for works & some milestones on the doc ? we know that we must have boris' bluepritn merged first hand,15:58
toan-tranthus during that time we need to accomplish sth15:58
alaskidebo_os: the etherpad I linked above has the plan, and there's a bp up for it15:58
n0anoalaski, good answer, I can live with that (even if it does require  a little more work)15:58
debo_osalaski: as it been reviewed and approved?15:59
*** ArthurBerezin has quit IRC15:59
debo_osby this subgroup15:59
*** hartsocks has joined #openstack-meeting15:59
debo_osdoes everyone agree its going to be the right thing :)15:59
*** SumitNaiksatam has quit IRC16:00
debo_osif we avoid this formal get we will spend more time later16:00
n0anodebo_os, well, I haven't heard anyone complain so it must be corret :-)16:00
johnthetubaguya blueprint review seems like the right way to agree the approach16:00
alaskieveryone doesn't agree, but that's never going to happen anyways16:00
debo_osI think we should just review the ether pad one meeting16:00
n0anosorry guys but we're out of time, let's continue on the email list16:00
debo_osand say we are done16:00
jgallardtime :)16:01
debo_osif people don't disagree by a deadline16:01
debo_oswe can't complain later16:01
n0ano#endmeeting16:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"16:01
debo_osat least do the process16:01
openstackMeeting ended Tue Dec  3 16:01:21 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-12-03-15.00.html16:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-12-03-15.00.txt16:01
openstackLog:            http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-12-03-15.00.log.html16:01
*** reaper has joined #openstack-meeting16:01
*** shane-wang has quit IRC16:01
*** kmartin has joined #openstack-meeting16:01
n0anotnx everyone16:01
alaskithanks16:01
toan-trantnx everybody16:01
*** PaulMurray has quit IRC16:02
*** hemanthravi has quit IRC16:02
debo_osthx16:02
*** dkranz has quit IRC16:02
toan-tranthx boris-42, it's been real enlightment16:02
primemin1sterp#startmeeting hyper-v16:02
openstackMeeting started Tue Dec  3 16:02:30 2013 UTC and is due to finish in 60 minutes.  The chair is primemin1sterp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:02
*** dcramer__ has quit IRC16:02
*** openstack changes topic to " (Meeting topic: hyper-v)"16:02
openstackThe meeting name has been set to 'hyper_v'16:02
*** ayoung has quit IRC16:02
primemin1sterphey guys16:02
*** primemin1sterp is now known as primeministerp16:02
*** mspreitz has quit IRC16:03
*** BillArnold has quit IRC16:03
primeministerpNo realy agenda today16:03
primeministerpsome are travelling16:03
primeministerpwe're heads down bringing more servers online16:04
primeministerpadditionally looks like we've been able to get an additionaly 200 or so machines16:04
primeministerpfor the ci16:04
*** jcooley_ has joined #openstack-meeting16:04
*** RobinWang has quit IRC16:05
primeministerpso that's the quick update.16:05
primeministerpmordred: ping16:05
mordredwhat did I do?16:05
primeministerphey now16:05
primeministerpsorry i've been delayed w/ the ironic stuff16:06
mordredit's ok. I'll just whip you16:06
primeministerpdid anyway look at what i did16:06
*** PhilD has joined #openstack-meeting16:06
mordredooh. WAIT16:06
mordreddid you just say 200 machines?16:06
mordredjeblair: ^^16:06
primeministerpmordred: yes16:06
mordredlifeless: ^^16:06
*** garyk has quit IRC16:06
primeministerpmordred: it's early16:06
primeministerpmordred: but16:06
*** sdake_ has joined #openstack-meeting16:06
*** pnavarro has joined #openstack-meeting16:06
primeministerpthey are already racked16:06
primeministerpin our colo here in cambridge16:07
pnavarrohi all !16:07
primeministerphey pedro16:07
*** sdake_ has quit IRC16:07
mordredthat's awesome16:07
primeministerpI just need to get them to another part of the colo16:07
PhilDHi Folks16:07
*** sdake_ has joined #openstack-meeting16:07
*** sdake_ has quit IRC16:07
*** sdake_ has joined #openstack-meeting16:07
jeblairyay!16:07
*** tianst has left #openstack-meeting16:07
primeministerpfor a power budget perspective16:07
primeministerpthat's going to be where the real thing will live16:07
primeministerpfor now I have about 50+ machines we're finalizing16:07
primeministerpfor hyper-v16:08
*** cdub has quit IRC16:08
primeministerpand another 10 or so for the kvm workloads16:08
primeministerpmordred: i have proper zuul node up16:08
primeministerpmordred: and connected, I'll want to talk w/ you at some point if possible16:08
*** rnirmal has joined #openstack-meeting16:08
primeministerpmordred: the keys are already set16:09
primeministerpand inplace16:09
*** cdub has joined #openstack-meeting16:09
primeministerpi've verified upstream alerts coming in16:09
primeministerpas well16:09
primeministerpso back to the 200 machines16:09
*** hartsocks has left #openstack-meeting16:09
primeministerpmordred:I have the 50+ online now, the 200 will come sometime before the end of icehouse16:10
mordredthat's awesome16:10
*** sacharya has joined #openstack-meeting16:10
primeministerpmordred: i'm also getting through the security review for the network circuit16:10
primeministerpinterally16:10
primeministerpnot sure how much longer that will be16:11
primeministerpthe 200 machines complicated things a bit16:11
mordredyeah, I'll bet they did16:11
primeministerphowever I pleased to find out they are already racked16:11
mordredwe should set up a time for you and lifeless to talk - he's got progress on the test broker piece, which I think is one of the pieces we'll need for you too16:11
*** PhilD has quit IRC16:11
primeministerpi'm hoping to see them physically as soon as I can time from local it resource16:12
primeministerpmordred: would you mind helping coordinate that ?16:12
mordredprimeministerp: happy to16:12
primeministerpmordred: i've got 2 guys from redmond for the next two weeks16:12
primeministerpmordred: I need to keep them engaged16:13
primeministerpand moving on this16:13
primeministerpso they can take a look too16:13
mordredprimeministerp: I'll make sure we get something set up asap16:13
primeministerpmordred: thx16:13
*** doron is now known as doron_afk16:14
primeministerpmordred: just as a fyi16:14
mordredprimeministerp: you are a rockstar16:14
*** toan-tran has quit IRC16:14
primeministerpmordred: we've been trying to use chocolatey16:14
primeministerpmordred: from a windows perspective16:14
mordredI have no idea what that is16:14
primeministerpmordred: to enable us to get as close to linux16:14
primeministerpmordred: windows package management16:14
mordredoh, neat16:14
primeministerpmordred: open source style16:14
*** colinmcnamara has joined #openstack-meeting16:15
*** colinmcn_ has joined #openstack-meeting16:15
*** dvarga has quit IRC16:15
primeministerpmordred: puppetlabs hired the guy who created/maintains it16:15
mordredoh - that's smart of them honestly16:15
*** markvan has joined #openstack-meeting16:15
primeministerpmordred: thing is we can close to linux like16:15
mordredpuppet bootstrapping that on windows would make puppet manifests make much more sense16:15
primeministerpmordred: well that's that i've started moving too16:15
primeministerpmordred: because they now have a package provider16:16
primeministerpmordred: and it means unified manifests16:16
primeministerpmordred: if you see where i'm going16:16
*** ArthurBerezin has joined #openstack-meeting16:16
primeministerponly differences become simple case $osfamily16:16
*** ArthurBerezin has left #openstack-meeting16:16
primeministerpjust like differentiating between linux distros16:16
*** belmoreira has quit IRC16:16
primeministerpmordred: it also means an easy way to get to python/easyinstall/pip16:17
*** _ozstacker_ has quit IRC16:17
*** ayoung has joined #openstack-meeting16:17
mordredvery nice16:17
primeministerpmordred: currently working to integrate mingw16:17
primeministerpmordred: so in theory16:17
*** dkranz has joined #openstack-meeting16:17
primeministerpmordred: all the pip reqs will compile on the fly16:17
mordrednice!16:18
primeministerpmordred: on windows16:18
*** mrodden has joined #openstack-meeting16:18
primeministerpmordred: only problem is we have to use puppet 3+16:18
*** ozstacker has joined #openstack-meeting16:18
*** colinmcn_ is now known as colinmcnamara_16:19
*** colinmcnamara_ has quit IRC16:19
*** colinmcnamara has quit IRC16:19
primeministerpmordred: however we're using upstream modules like vcsrepo and such across platform w/ no issues thanks to the chocolate bits and some somewindows path modules16:19
*** jcooley_ has quit IRC16:19
*** colinmcnamara has joined #openstack-meeting16:19
*** colinmcn_ has joined #openstack-meeting16:19
*** jcooley_ has joined #openstack-meeting16:19
primeministerpmordred: so I'll look for an email for you regarding setting up that discussion16:20
*** jgallard has quit IRC16:20
primeministerppnavarro: do you have anything to discuss?16:20
*** jcooley_ has quit IRC16:20
pnavarronot really, thanks primeministerp16:20
primeministerpno luis todya16:20
primeministerpok16:20
primeministerpthat's all i have16:20
primeministerpfor now16:20
primeministerpmordred: thx16:20
primeministerp#endmeeting16:21
*** tanisdl has joined #openstack-meeting16:22
*** sarob has joined #openstack-meeting16:22
*** pnavarro has quit IRC16:23
*** dprince has quit IRC16:25
*** SumitNaiksatam has joined #openstack-meeting16:27
*** nprivalova has quit IRC16:28
*** stevemar has quit IRC16:30
*** stevemar has joined #openstack-meeting16:31
*** atiwari has joined #openstack-meeting16:31
*** mengxd has joined #openstack-meeting16:31
*** mengxd has quit IRC16:32
*** doron_afk has quit IRC16:33
*** sparkycollier has joined #openstack-meeting16:34
*** jcooley_ has joined #openstack-meeting16:35
*** sarob has quit IRC16:35
*** sarob has joined #openstack-meeting16:35
*** venkatesh has quit IRC16:37
*** marun has quit IRC16:37
*** radez_g0n3 is now known as radez16:38
*** ociuhandu has left #openstack-meeting16:40
*** tristanC has joined #openstack-meeting16:41
*** msdubov has joined #openstack-meeting16:43
*** samcdona has joined #openstack-meeting16:45
*** jcooley_ has quit IRC16:47
*** herndon has joined #openstack-meeting16:49
*** yassine has quit IRC16:49
*** mestery has quit IRC16:49
*** garyk has joined #openstack-meeting16:50
*** mestery has joined #openstack-meeting16:50
*** rakhmerov has quit IRC16:51
*** gyee has joined #openstack-meeting16:52
*** SpamapS has quit IRC16:52
*** DennyZhang has joined #openstack-meeting16:52
*** jraim has joined #openstack-meeting16:53
*** ruhe has quit IRC16:53
*** hemna has joined #openstack-meeting16:54
*** jtomasek has quit IRC16:55
*** marun has joined #openstack-meeting16:57
*** metral_ has joined #openstack-meeting16:59
*** metral_ has quit IRC16:59
*** danwent has joined #openstack-meeting16:59
*** jtomasek has joined #openstack-meeting16:59
boris-42#startmeeting Rally17:00
openstackboris-42: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.17:00
boris-42#endmeeting17:01
boris-42#startmeeting Rally17:01
openstackboris-42: Error: Can't start another meeting, one is in progress.  Use #endmeeting first.17:01
boris-42#endmeeting17:01
boris-42omg meeting bot is broken17:01
guitarzanthe person that started the meeting has to end it17:02
boris-42#info17:02
sarobping infra17:02
*** Alexei_987 has joined #openstack-meeting17:02
boris-42garyk ping17:02
notmynamelooks like it was primeministerp (but his #endmeeting didn't take)17:02
*** viktors has joined #openstack-meeting17:02
guitarzanyeah, he started it with a different nick17:03
*** jlibosva has joined #openstack-meeting17:03
*** redixin has joined #openstack-meeting17:03
*** guitarzan is now known as primemin1sterp17:03
primemin1sterp#endmeeting17:03
*** primemin1sterp is now known as guitarzan17:04
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:04
openstackMeeting ended Tue Dec  3 17:03:59 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:04
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-12-03-16.02.html17:04
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-12-03-16.02.txt17:04
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-12-03-16.02.log.html17:04
*** funzo has joined #openstack-meeting17:04
guitarzanhaha, worked?17:04
boris-42primeministerp thank you17:04
boris-42#startmeeting Rally17:04
openstackMeeting started Tue Dec  3 17:04:35 2013 UTC and is due to finish in 60 minutes.  The chair is boris-42. Information about MeetBot at http://wiki.debian.org/MeetBot.17:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.17:04
*** openstack changes topic to " (Meeting topic: Rally)"17:04
openstackThe meeting name has been set to 'rally'17:04
boris-42hi all17:04
*** sarob has quit IRC17:04
*** SpamapS has joined #openstack-meeting17:05
*** SpamapS has quit IRC17:05
*** SpamapS has joined #openstack-meeting17:05
*** sarob has joined #openstack-meeting17:05
boris-42am I alone ;)17:05
boris-42?)17:05
Alexei_987alone in the room17:05
akscramyep17:05
boris-42lol17:06
redixinwat17:06
boris-42#topic Splitting Rally benchmark & deploy workflows17:06
*** openstack changes topic to "Splitting Rally benchmark & deploy workflows (Meeting topic: Rally)"17:06
boris-42akscram could you share latest news ?17:06
*** vuil has joined #openstack-meeting17:07
*** galstrom_zzz is now known as galstrom17:07
*** Haneef has joined #openstack-meeting17:07
boris-42akscram ?17:08
akscramtoday we discussed benchmarking workloads as a complex tasks17:08
boris-42akscram see topic pls17:08
boris-42akscram splitting benchmark & deploy workflows17:09
akscramis it the #topic command, right?17:09
*** dolphm has quit IRC17:10
redixinafaik this work depends on resource-db-tracking, and patches are coming soon17:10
boris-42akscram yep17:10
boris-42Okay let's speed up this discussion17:10
akscram#topic splitting benchmark & deploy workflows17:11
boris-42I think that only I am able to run this command17:11
boris-42#topic splitting benchmark & deploy workflows17:11
*** openstack changes topic to "splitting benchmark & deploy workflows (Meeting topic: Rally)"17:11
akscramso, redixin is right17:11
boris-42akscram so pls say in few words what we are going to do and links do bp and pathces17:12
akscramthe splitting is blocked by the resource tracking17:12
*** syerrapragada has quit IRC17:12
*** jcooley_ has joined #openstack-meeting17:12
akscrama patch introducing Resource model is still in progress17:13
*** syerrapragada has joined #openstack-meeting17:13
*** marun has quit IRC17:13
boris-42akscram okay to make in more clear I will try to explain17:14
akscramafter that I want to create a patch with tracking resources in server providers17:14
boris-42akscram we should merge this patch https://review.openstack.org/#/c/57455/17:14
boris-42but it is impossible until deploy part of Rally will track all allocated resources like allocated VMs17:15
*** jcooley_ has quit IRC17:15
boris-42it is caused because before this patch, we made deploy-benchamrk-deploy_clenaup in one action and store all data in memory of process17:15
*** jcooley_ has joined #openstack-meeting17:16
boris-42and now deploy and deploy_cleanup are totally separated tasks17:16
boris-42so we should store all allocated resources in DB instead of process memory17:16
*** reed has quit IRC17:16
boris-42so I hope at this week we will finish all work around this stuff17:16
boris-42#topic benchmark engine improvements17:17
*** openstack changes topic to "benchmark engine improvements (Meeting topic: Rally)"17:17
boris-42msdubov ping17:17
msdubovboris-42 here17:17
boris-42msdubov could you share improvements around benchmark engine17:17
*** tanisdl has quit IRC17:17
msdubovboris-42 So, 1) we have merged the patch which enabled Rally to run benchmark scenarios for a given period of time, say, 10 minutes. This is a significant improvement since earlier we were only able to launch scenarios for a restricted number of times, say, 5 times, and this change allows us to create more realistic load17:19
msdubov2) We have also enabled admin openstack client support in benchmark scenarios which will allow us to write fully functional keystone benchmark scenarios17:19
msdubovAnd there are several changes pending for review:17:19
*** tanisdl has joined #openstack-meeting17:20
*** jcooley_ has quit IRC17:20
boris-42msdubov okay nice17:20
msdubov1) Periodic launch of benchmark scenarios (another significant change, since earlier we were able to run scenarios only continuously, but now we will be able to run periodic tasks17:20
msdubov2) I've repaired the init() mechanism17:20
msdubovbasically that's all for now17:21
boris-42msdubov okay thnaks17:21
boris-42#topic make Rally more community oriented17:21
*** openstack changes topic to "make Rally more community oriented (Meeting topic: Rally)"17:21
boris-42Ok, we have pretty good wiki page, roadmap and so on17:22
*** coolsvap has quit IRC17:22
boris-42But it is hard to understand what are our current goals, current roadmap, tasks in progress and free tasks17:22
boris-42so we made Rally page on etherpad that will contain all interesting infromation17:22
*** ildikov_ has joined #openstack-meeting17:23
*** jcooley_ has joined #openstack-meeting17:23
msdubovboris-42 Will we post weekly updates there?17:23
redixinlink?17:23
*** boden has joined #openstack-meeting17:23
boris-42so here is the page https://etherpad.openstack.org/p/Rally_Main17:23
boris-42msdubov no weekly updates we will publish on wiki page17:23
boris-42msdubov but there will be link from this page to rally updates17:24
msdubovboris-42 ok nice17:24
msdubovboris-42 btw I think next week I'll start pushing old updates to the archive since there are already 3 of them, and the wiki page is pretty long already17:24
boris-42msdubov I think that we could wait a bit17:25
boris-42msdubov 5-6 news per page17:25
msdubovboris-42 Ok17:25
boris-42boden do you have some news to share with us17:25
boris-42boden around cloud cleanup17:25
*** ndipanov has quit IRC17:26
bodenboris-42 -- almost done with the cloud cleanup... I just finished up the UTs... all I have to do now is merge with the latest and then retest before submitting code review17:26
*** bgorski has joined #openstack-meeting17:26
*** debo_os has quit IRC17:26
*** ndipanov has joined #openstack-meeting17:27
boris-42boden are you executing to finish it  today?17:27
boris-42expecting *17:27
*** ndipanov has quit IRC17:28
bodenboris-42 I would like to, but it depends if I run into issues from the resulting merge17:28
*** ndipanov has joined #openstack-meeting17:28
boris-42boden ok nice, thank you17:28
*** krtaylor has quit IRC17:28
boris-42Okay I think that we could end todays meeting17:28
bodenboris-42... I will probably not take on any more work in near future as I will be out for awhile this month for vacation17:29
boris-42boden eh sad..17:29
redixinwhy sad? some snowboarding is fun =)17:29
boris-42redixin yep=)17:30
boris-42boden okay have a nice vacation-=)17:30
msdubovboden have a nice time17:30
redixin#endmeeting17:30
bodenthank you17:30
boris-42boden I hope you won't forget us after vacation=)17:31
boris-42#endmeeting17:31
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"17:31
openstackMeeting ended Tue Dec  3 17:31:14 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)17:31
openstackMinutes:        http://eavesdrop.openstack.org/meetings/rally/2013/rally.2013-12-03-17.04.html17:31
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/rally/2013/rally.2013-12-03-17.04.txt17:31
openstackLog:            http://eavesdrop.openstack.org/meetings/rally/2013/rally.2013-12-03-17.04.log.html17:31
*** bauzas has quit IRC17:31
*** msdubov has quit IRC17:31
*** Alexei_987 has quit IRC17:31
*** redixin has left #openstack-meeting17:32
*** dcramer__ has joined #openstack-meeting17:32
*** viktors has left #openstack-meeting17:32
*** dcramer__ has quit IRC17:33
*** dcramer__ has joined #openstack-meeting17:33
*** sharp_ has joined #openstack-meeting17:37
*** boris-42 has quit IRC17:38
*** fbo is now known as fbo_away17:38
*** ayoung has quit IRC17:39
*** reed has joined #openstack-meeting17:41
*** sharp_ is now known as kmsWork17:41
*** derekh has quit IRC17:41
*** fabio has joined #openstack-meeting17:45
*** fabio is now known as fabiog17:45
*** bdpayne has joined #openstack-meeting17:47
*** ayoung has joined #openstack-meeting17:51
*** mrunge has joined #openstack-meeting17:52
*** galstrom is now known as galstrom_zzz17:54
*** coolsvap has joined #openstack-meeting17:54
*** dkranz has quit IRC17:55
*** vkozhukalov has joined #openstack-meeting17:55
*** bauzas has joined #openstack-meeting17:55
*** twoputt_ has joined #openstack-meeting17:56
*** twoputt__ has joined #openstack-meeting17:56
*** nachi has joined #openstack-meeting17:58
ayoung Keystone Pre meeting chat room infitration17:58
*** brich1 has joined #openstack-meeting17:58
*** rongze has quit IRC17:58
morganfainbergo/17:58
gyee\o/17:59
fabioghi17:59
ayoungBY THE POWER OF KEYSTONE!17:59
*** ivar-lazzaro has joined #openstack-meeting17:59
* morganfainberg has 80s movie flashbacks.17:59
*** bknudson has joined #openstack-meeting17:59
gyeeI NOW PRONOUNCE YOU MAN AND ...18:00
*** nkinder has joined #openstack-meeting18:00
ayoungCat18:00
morganfainbergdog?18:00
bknudsonKEYSTONE18:00
lbragstado/18:00
*** ArxCruz has quit IRC18:00
*** jamielennox has joined #openstack-meeting18:01
stevemaro/18:01
ayoungdolphm is MIA...18:01
*** ygbo has quit IRC18:01
shardyo/18:01
*** ArxCruz has joined #openstack-meeting18:01
ayoung#startmeeting Keystone18:02
openstackMeeting started Tue Dec  3 18:02:21 2013 UTC and is due to finish in 60 minutes.  The chair is ayoung. 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
ayoungOyez Oyez....18:02
morganfainberg#ayoung beat me to typing it.18:02
ayounghttps://wiki.openstack.org/wiki/Meetings/KeystoneMeeting#Weekly_Keystone_team_meeting18:02
*** danwent has quit IRC18:02
jamielennoxmorganfainberg really wanted to be king for the day18:03
morganfainbergjamielennox, i'd just delegate it.18:03
*** danwent has joined #openstack-meeting18:03
*** markmcclain has joined #openstack-meeting18:03
*** rossella_s has quit IRC18:03
ayoung#topic Tempest change for assignments-doesn't-check-identity18:03
*** openstack changes topic to "Tempest change for assignments-doesn't-check-identity (Meeting topic: Keystone)"18:03
jamielennoxmorganfainberg: that's the point of being king18:03
ayoungThe floor recognized bknudson18:03
bknudsonok, I put this one on there.18:03
ayoungrecognizes18:03
bknudsonso henrynash (not here) had commented in a previous commit18:03
bknudsonthat we shouldn't be checking against identity API from assignments18:04
bknudsone.g., grant role or whatever shouldn't check that the user exists.18:04
bknudsonwhich makes some sense especially if using LDAP...18:04
ayoungbknudson, agreed.  In the case of Federation, we will not be able to do active lookups18:04
bknudsonuser could go away right after you check it.18:04
bknudsonso I made that change in keystone18:04
bknudsonbut it fails tempest18:04
morganfainbergbknudson, so 3-way tempest change?18:05
bknudsonbecause they added a test that if user doesn't exist then should fail18:05
ayoungbknudson, are the tempest tests too restrictive?18:05
gyeebknudson, how are we going to cleanup the data18:05
bknudsonayoung: that's kind of my question18:05
ayoungOK,  lets put in a change request to drop that test from tempest18:05
bknudsonthe identity spec doesn't say that it fails specifically18:05
gyeeI would imagine roles assignment will need to be cleanup at some point18:05
gyeejust like expired tokens18:05
ayoungIt should not fail18:05
morganfainbergi would agree, it shouldn't fail18:05
ayoungits just a rule that will never be triggered18:05
bknudsonfor the tempest change, I'll need a blueprint, and not sure if we had one.18:06
bknudsonit's probably the federation one18:06
morganfainbergbknudson, use the split assignment/identity one?18:06
ayoungbknudson, can't we use the Keystone blueprint?  File it under Federation18:06
morganfainbergbknudson, or federation18:06
ayoungsplit id is better18:06
bknudsonok, I'll point to the split ID one.18:06
bknudsonI think that's all I needed.18:06
ayoung#topic REMOTE_USER auth v2 and v3 mismatch18:07
bknudsonMy change to the tempest test was to accept either NotFound or success.18:07
*** openstack changes topic to "REMOTE_USER auth v2 and v3 mismatch (Meeting topic: Keystone)"18:07
bknudsonthey didn't like that.18:07
morganfainbergbknudson, also, iirc tempest likes you to @skip the test, then change keystone, then unskip/fix test18:07
*** dkranz has joined #openstack-meeting18:07
morganfainbergbknudson, at least that was needed for the token 403 vs 404 one18:07
*** arunkant has joined #openstack-meeting18:07
ayoungmorganfainberg, in this case, just drop the test, or the check18:07
morganfainbergayoung, right, i meant if we were keeping the test.18:07
bknudsonIt seems "correct" to me to actually accept either 404 or 200 in this case...18:08
*** divyeshk has joined #openstack-meeting18:08
bknudsonsince identity api doesn't really say what it does18:08
bknudsonAlright, moving on to REMOTE USER18:08
bknudsonmaybe you had a chance to look at this18:08
bknudsonbut v2 doesn't use plugin so does remote auth its way18:08
bknudsonv3 uses plugins so does remote auth its way18:09
bknudsonso you can easily put yourself in a situation where v2 remote auth works and v3 doesn't18:09
morganfainbergthis is the user w/ @ in the name?18:09
bknudsonor vice-versa18:09
ayoungbknudson, so you want to make V2 honor the v3 plugins?18:09
morganfainbergand other... oddities18:09
bknudsonyes, the problem is typically handling @ in the name18:09
bknudsonsince that's what our supplied external auth plugins do differently18:09
bknudsonayoung: I think it makes sense for v2 to use whatever plugin is used for v3...18:10
ayoungbknudson, no reason the v2 token controller can't call the v3 plugins.18:10
bknudsonbut I haven't looked into if there's any reason it wouldn't work.18:10
ayoungproblem solved.18:10
ayoungNext topic?18:10
morganfainbergayoung, as long as you wedge in issue_v2_token.18:10
jamielennoxdoesn't that change how v2 auth works?18:10
morganfainbergayoung, but not a big deal18:10
ayoungmorganfainberg, nah,18:10
ayoungplugin just does authentication18:10
bknudsonjamielennox: it doesn't have to change how v2 auth works if you use the "correct" plugin?18:11
ayoungit doesn't get into the token creation code18:11
*** marekd has joined #openstack-meeting18:11
morganfainbergayoung, doesn't it also issue the token? erm call the token issuancE?18:11
*** colinmc__ has joined #openstack-meeting18:11
morganfainbergayoung, i might be thjinking something else18:11
*** colinm___ has joined #openstack-meeting18:11
bknudsonbut, I haven't looked into it18:11
ayoungjamielennox, it would be a backwards compatible change18:11
ayoungmorganfainberg, this is auth plugins, not token provider18:11
morganfainbergayoung, hm. ok.18:11
*** sandywalsh_ has joined #openstack-meeting18:11
jamielennoxbknudson: so you want to expose the plugins as configurable to v2 as well - default to the old form?18:11
bknudsonthere's already work in progress to clean up auth plugins, so I think we let that progress and then can consider using plugin for v218:11
ayoungV2 can call https://github.com/openstack/keystone/blob/master/keystone/auth/plugins/external.py  if it REMOTE_USER gets triggered18:12
*** colinmcn_ has quit IRC18:12
*** colinmcnamara has quit IRC18:12
bknudsonjamielennox: I would guess that for backwards compat they'll have to be separately configurable.18:12
ayoungfrom here...https://github.com/openstack/keystone/blob/master/keystone/token/controllers.py#L28118:12
*** krtaylor has joined #openstack-meeting18:12
morganfainbergbknudson, i think there is still a fix needed in the V3 plugin... inconsistent behavior (as we discussed before) but it's not as bad as v2 vs v3 at the moment18:13
jamielennoxbknudson: yea, because the default needs to be different between versions - that works for me18:13
ayoungmorganfainberg, we can always make more plugins18:13
morganfainbergayoung, right.18:13
ayoungwe good to move on?18:13
bknudsonyes, thanks.18:13
jamielennoxis there a reason we can't just use the v3 one?18:13
bknudsonoh, one more q18:13
bknudsonbackporting the fix... worth it?18:14
ayoungbknudson, lets see how invasive it is, but I suspect no18:14
jamielennoxbecause as it stands if using REMOTE_AUTH you would only be able to use v2 or v3 at the moment anyway18:14
bknudsonapparently we made backwards-incompat change in H18:14
bknudsonand V2 vs V3 is broken in H18:14
*** sandywalsh has quit IRC18:14
bknudsonmaybe we just say that you have to write your own external auth plugin.18:14
bknudson(for H)18:14
bknudsonsince we're not going to backport18:15
ayoungbknudson, we could provide one out of tree18:15
ayoungbut..if we do that, we should just put it in a bug fix18:15
*** nati_ueno has joined #openstack-meeting18:15
*** vipul is now known as vipul-away18:15
ayounggood to move on?18:16
bknudsonI think it would be hard to justify the backport18:16
bknudsonlet's move on.18:16
ayoung#topic reviews for icehouse blueprints18:16
*** openstack changes topic to "reviews for icehouse blueprints (Meeting topic: Keystone)"18:16
ayoung#topic reviews for icehouse blueprints: API Version Discover18:16
*** openstack changes topic to "reviews for icehouse blueprints: API Version Discover (Meeting topic: Keystone)"18:16
ayoung#link https://review.openstack.org/#/c/3841418:16
ayoungMerged18:16
ayoung#topic reviews for icehouse blueprints: Add federation API18:17
*** openstack changes topic to "reviews for icehouse blueprints: Add federation API (Meeting topic: Keystone)"18:17
ayoung#link https://review.openstack.org/#/c/5198018:17
*** DennyZhang has quit IRC18:17
atiwariadded some comments on patch #1218:17
ayoungThere is a lot in those three docs.18:17
jamielennoxwoohoo!18:17
stevemar *alot*18:18
stevemari will upload a new version of the spec soon18:18
ayoungMight I suggest that we only -1 something for structural changes, not verbage or editing, to get a firm contract?18:18
marekdayoung: i should upload some CRUD for IDPs on gerrit tomorrow (my timezone)18:18
ayoungstevemar, any thought on splitting that review?18:18
ayoungor do you want all three to live/die together?18:18
stevemarayoung, it doesn't bother me that it's all in one18:18
ayoungOK18:18
atiwari+1 ayoung18:18
*** sdake has quit IRC18:19
ayoungstevemar, you feel like you are making progress?  Ice2 will be here before you know it18:19
atiwariI think splitting wd work better18:19
marekd+1 atiwari18:19
*** sdake has joined #openstack-meeting18:19
*** sdake has quit IRC18:19
*** sdake has joined #openstack-meeting18:19
lbragstadatiwari: FWIW, i think so too18:19
*** devlaps has joined #openstack-meeting18:19
atiwariayoung, too much content in one review18:19
stevemarmarekd is submitting a patch to keystone for the idp changes, (based on the current spec state)18:19
lbragstadit could almost be broken up into commit for each blueprint...18:20
*** sdake has quit IRC18:20
ayounglets prioritze the mapping one.  That stands alone, and will be useful even if we don't get the whole Federation BP iplemented by I2.18:20
*** sdake has joined #openstack-meeting18:20
*** sdake has quit IRC18:20
*** sdake has joined #openstack-meeting18:20
stevemarayoung, yeah, i'm starting to actively work on the impl for that one now, i think the current api spec is close18:20
stevemarchadwicks folk like it, so thats a big plus18:21
ayoungFederation and IdP can go into I3.  They would be disabled by default, but that is probably OK for people that want Federation support to explicitly enable it.18:21
morganfainbergayoung, ++ i think that is fine18:21
stevemaryep, of course18:21
gyeeayoung, isn't there a long running Keystone policy that API changes need to be done by I2?18:21
morganfainbergayoung, for J we can enable it by default.  actually kindof like the new feature, disabled by default, next cycle enable if desired / fix and enable18:21
ayoung#action stevemar to split API reviews into Mapping and Federation reviews18:21
stevemarokay, i can break up the api spec into multiple reviews18:21
ayoungmorganfainberg, yep18:21
morganfainberggyee, yes, but the SPEC will be done and this shouldn't have any api incompatible changes (extension)18:22
morganfainberggyee (or just disabled even if not an extension)18:22
ayoung#topic reviews for icehouse blueprints: Revocation Events18:22
*** openstack changes topic to "reviews for icehouse blueprints: Revocation Events (Meeting topic: Keystone)"18:22
ayoung#link https://review.openstack.org/#/c/5954618:23
ayoungThis one is mine.  Please beat it up accordingly18:23
ayoungthis needs to go in by I2, and I suspect we will also want to add config options to disable some of the features in the current token infrastructure that are providing pain:18:23
morganfainbergayoung, that is looking good (based upon convos at the summit)18:24
ayoungnamely, the need to explicitly enumerate tokens18:24
ayoungmorganfainberg, that's what scares me18:24
morganfainbergayoung, yes, please lets make that die a horrible death.  enumerating tokens == bad18:24
ayoungmorganfainberg, so I want to make it optional, and make the new revocation architecture optional as well.  If someone doesn't want revocations, that should be OK.18:25
gyeeayoung, the revocation events are signed too right?18:25
ayounggyee, I wasn'18:25
*** gokrokve has quit IRC18:25
ayoungt doing that as a first approximation18:25
morganfainbergayoung, correct.  eventually events should be the way to go.18:25
ayoungbut we could add on a signature envelope.18:25
gyeeI mean we need to CMS envelope them, just like tokens18:25
*** gokrokve has joined #openstack-meeting18:25
morganfainbergayoung, we should sign the envelope, we do it already for TRL.18:25
*** ryanpetrello has quit IRC18:26
ayounggyee, in theory, we could make Keystone sign anything it publishes....it would be a content wrappper18:26
ayoungAccpest:JSON+CMS18:26
ayoungor summat18:26
ayoungAccpets18:26
ayoung#action ayoung to look into signing revocation events18:26
*** markmcclain has quit IRC18:26
*** Fdot has quit IRC18:26
atiwari#link any thoughts on https://blueprints.launchpad.net/keystone/+spec/service-scoped-role-definition18:26
morganfainbergayoung, and i'll (hopefully) have the last bugs worked out on key-value-store token stuff so you can base anything you need on that.18:27
jamielennoxayoung: i actually like the Accepts: idea - i'm not sure if anyone would use it though18:27
ayoungdata model will be scope-type = (user|project|domain)  and then scope Id18:27
*** nachi has quit IRC18:27
ayoungjamielennox, I'd like to see if there is a standard out there we could use for signing...but yeah, it seesm like it should be an "add on" for any API18:27
atiwarinow resource scoped as per Devid Chadwick18:27
ayoungatiwari, hold on18:28
*** gokrokve_ has joined #openstack-meeting18:28
ayoung#topic reviews for icehouse blueprints: KDS18:28
*** openstack changes topic to "reviews for icehouse blueprints: KDS (Meeting topic: Keystone)"18:28
ayoung#link https://review.openstack.org/#/c/5960018:28
ayoungthis is the first of a long chain of jamielennox 's pathces for KDS18:28
*** gokrokve_ has quit IRC18:28
ayoungthe Nova team especially is waiting for this18:29
jamielennoxthis is still fairly raw - but because I am introducing a whole new framework i'm assuming there will be some beating on the architecture18:29
*** DinaBelova has joined #openstack-meeting18:29
jamielennoxso the first couple of reviews can be done without understanding the crypto18:29
*** Abhishek has joined #openstack-meeting18:29
morganfainbergjamielennox, ayoung , i just did an oslo sync and ended up with a far different oslo result18:29
ayoungjamielennox, you bhave unit tests in the latter reviews that should server as examples18:29
morganfainbergare we missing things in the openstack-common.conf?18:29
bknudsonseems like we should get the KDS spec first18:29
*** gokrokve has quit IRC18:30
ayoungbknudson, in parallel18:30
morganfainbergand i'm not sure how much in oslo-incubator changed since that review was posted.18:30
ayoungwe can get the infrastructure for KDS in place while we finalize the spec18:30
jamielennoxmorganfainberg: oh - mine was a few days ago18:30
jamielennoxmaybe it's changed18:30
jamielennoxi'll update the patch18:30
ayoung#action do updated oslo sync18:30
morganfainbergand you're missing the py3kcompat stuff from the update.py run etc18:30
lbragstadnot sure if this will apply in time, but I think oslo/nova teams were working on a consistency document for syncs from oslo18:31
morganfainbergjamielennox, http://pastebin.com/ZYKEgi0y is what i got.18:31
jamielennoxmorganfainberg: has that changed in that time? i did a fairly standard oslo update18:31
lbragstadmorganfainberg: and some discussion about reworking update.py18:31
ayounglbragstad, we will have to sync again.  THis is just geting the deps in that KDS needs18:31
*** ildikov_ has quit IRC18:31
morganfainbergjamielennox i just ran with the openstack-common.conf as a config and it was missing files you had in yours, just an FYI18:31
*** vipul-away is now known as vipul18:32
lbragstadayoung: right, yeah that makes sense. Just a heads up in case any of that work has an impact on this18:32
*** SergeyLukjanov has joined #openstack-meeting18:32
morganfainberglbragstad, nod.18:32
lbragstadit was something that was discussed in the cross project meeting last week I htin k18:32
lbragstadthink*18:32
ayoung#topic Icehouse 118:32
*** openstack changes topic to "Icehouse 1 (Meeting topic: Keystone)"18:32
*** egallen has joined #openstack-meeting18:32
ayoung#link https://launchpad.net/keystone/+milestone/icehouse-118:32
morganfainbergi really should start attending the cross-project meetings18:32
nkinderOne more note on KDS.  I'm taking a pass through the spec today.18:33
ayoungAll BPs implemented18:33
morganfainbergw00t!18:33
ayoungnkinder, sounds good18:33
jamielennoxnkinder: thanks18:33
morganfainbergoooh, i need to put a series of idenitty proxy tests in still *doh*18:33
ayoungnkinder, as I said, we are going to try and get in infrastructure in place in parallel, so we don't need to wait for a finalized spec in order to get jamielennox moving18:33
* morganfainberg scribbles a todo18:33
bknudsonI posted several comments on the KDS spec on path set 15 ... not sure if those were rejected or what.18:34
ayoung#topic service or resource scoped role definition18:34
*** openstack changes topic to "service or resource scoped role definition (Meeting topic: Keystone)"18:34
ayoungatiwari, you;re up18:34
atiwarigreat18:34
atiwariso, are we cool with Davis's thoughts18:35
ayoung#link https://blueprints.launchpad.net/keystone/+spec/service-scoped-role-definition18:35
atiwariresource scoped role-def18:35
atiwari?18:35
ayoungatiwari, looking18:35
*** joesavak has joined #openstack-meeting18:35
nkinderbknudson: patch set 16 addresses many of those18:35
atiwari#link https://etherpad.openstack.org/p/service-scoped-role-definition18:35
bknudsonok, I'll go through and make the same comments again if it wasn't addressed.18:36
atiwarisomething like link: http://paste.openstack.org/show/54377/18:36
ayoungatiwari, where is the active portion of that document18:36
ayoungthe etherpad18:36
atiwariyes18:36
ayoungatiwari, where is the active portion of the etherpad that has David's comments?18:37
atiwarilink : https://etherpad.openstack.org/p/service-scoped-role-definition line 90 to 10718:37
*** ruhe has joined #openstack-meeting18:38
ayoungatiwari, there is a misconnect18:38
ayoungdisconnect18:38
atiwarilook at link: http://paste.openstack.org/show/54379/18:38
ayoungDomains and Services are resources that Keystone knows about.  Files are not18:38
*** dprince has joined #openstack-meeting18:39
atiwariI think it is for future extension18:39
*** jpich has joined #openstack-meeting18:39
atiwariayoung, +118:39
atiwaribut that approach is workable18:39
*** pabelanger has joined #openstack-meeting18:39
ayoungso lets ignore Files etc for the moment.  THe question you and I have been arguing is "do we scope a role definition to a service, or do we make only  of the existing scoping mechanisms"18:40
*** rakhmerov has joined #openstack-meeting18:40
ayoungdoes that sum it up?18:40
atiwariyes18:41
ayoungYou've been saying "scope a role definition to a project."  I'e pushed back on that.18:41
ayoungI've18:41
*** sarob has quit IRC18:41
ayoungso..here is my thinking, to lay it out for the rest of the team:18:41
atiwariand in my opinion scoping to service is need to address my use case18:41
atiwariand the service scoped token BP18:41
atiwarilink:https://blueprints.launchpad.net/keystone/+spec/service-scoped-tokens18:41
*** sarob has joined #openstack-meeting18:41
*** mrunge has quit IRC18:42
ayoungSo I see Service scoping as a shortsighted limitation.  THere are at least two things it fails to address:18:42
ayoung1.  Scope a role to multiple endpoints for a service (but not all)18:42
ayoung2.  Scoped a role to multiple services (but not all)18:42
ayoungRole defintions are, currently, a cross cutting concern18:42
atiwariayoung, that is why David'd proposal is good for both18:42
ayounga role is on a project or domain, and is equally applicable across all services18:43
ayoungatiwari, has a requirement to scope a role definition to a specific service18:43
atiwariayoung, I am not saying no but it role name which is cross cutting18:43
atiwarirole-def entity can be separate for all service18:43
*** herndon has quit IRC18:43
ayoungso David's scope and my Namespaceing are solving the same proble,18:43
ayoungm18:43
atiwariayoung, no18:44
ayoungatiwari, hold on18:44
ayoungI am truing to explain to the team...18:44
atiwariok18:44
ayoungIt is a question of Namespacing a role definitin, and then proving access rules for who can modify a role defintion.  To me, this is separate from what the role gets assigned to18:45
ayoungThe goal is to be able to distinguish betwee "admin" for "keystone" and "admin" for "glance"18:45
ayoungthat, in the existing approach, is not really covered by role assignments18:45
*** coolsvap_ has joined #openstack-meeting18:45
*** safchain has quit IRC18:45
ayoungit could be handled by using projects, however18:46
*** sarob has quit IRC18:46
ayoungfor example, we could make a project (under the default or admin domain) called Keystone, and another one called glance18:46
ayoungthen, to do administrative tasks on glance, you would need the admin role on the glance procet.18:46
ayoungThat is an implicit mapping of role to service18:46
ayoungatiwari, 's proposals so far have been around making it an explicit link18:47
bknudsonhave a role called glance-admin18:47
*** coolsvap has quit IRC18:47
ayoungso instead of a user having a role on project, they would have a role on a sevice18:47
ayoungbknudson, that is basically namespacing18:47
jamielennoxayoung: (when you're finished) are these exclusive? My immediate thought is that when have a role on a project you only get that role in the token if you scope it to the project - if as you say we have a role on a service wouldn't we need to scope the token to a service to make that work18:47
ayoungjamielennox, let me address bknudson first, and then I'll come back to that18:48
shardyayoung: +1, then the service can just define a policy rule to control access18:48
shardyayoung: That is essentially the interim solution I've been working on for Heat18:48
*** herndon_ has joined #openstack-meeting18:48
ayoungbknudson, so he wants the glance admin to be able to define multiple roles, and do so independantly of what other people are creating and managing18:48
bknudsonso somebody could do this already with roles and policy.json updates ?18:48
atiwariayoung, role assignment must be abstracted from service (or resource) for which assignment is done18:48
ayoungbasically, the ability to delegate to other users the ability to create role definitions18:48
ayoungbknudson, the assignment side can be done, but not the creation18:49
ayoungcreation of new role defs in a delegated manner is new18:49
ayoungand, I think, innovative18:49
*** rongze has joined #openstack-meeting18:49
ayoungthe question, then, is how to decide "who can create a new role"18:49
bknudsonwhat if we put roles in domains?18:50
ayoungbknudson, or projects18:50
ayoungbknudson, that was my thought18:50
gyeedomain-owned roles?18:50
ayoungthen, a user with the role "roleadmin" on the "glance" project can manage the set of roles for the "glance" proejct, which is mapped to the "glance" service18:50
*** pablosan has joined #openstack-meeting18:50
bknudsonare they namespaced to the project?18:50
ayoungbknudson, that is my proposal18:51
*** divyeshk has left #openstack-meeting18:51
*** nermina has joined #openstack-meeting18:51
*** coolsvap_ has quit IRC18:51
ayoungbknudson, so glance would get a top level role  "glance"18:51
jamielennoxbknudson: would they need to be or is it just something we need to specify in policy?18:51
ayoungthat would be created by superadmin, and assigned to the glance proejct18:51
*** hemna has quit IRC18:52
bknudsonjamielennox: I'm just wondering if someone creates "role1" in "glance" can someone else create "role1" in "cinder"18:52
ayoungthis would be immutable, but "roleadmin"s in the "glance" proejct" could create roles underneath it18:52
*** gokrokve has joined #openstack-meeting18:52
atiwarinamespace or role name should not be service name18:52
bknudsonand is "role1" in "glance" the same as "role1" in "cinder" or is it different?18:52
ayoungbknudson, they would get namespaced "glance":"admin"  adn "cinder":"admin"18:52
atiwarithat is tight coupling with resource name18:52
ayoungatiwari, I would replace "should not" with "does not have to be"18:53
jamielennoxbknudson: yea - i got that, but is it something we need to mangle the role name of can we just say in the policy file "role1" in "cinder" somehow18:53
*** coolsvap has joined #openstack-meeting18:53
ayoungatiwari, I would suggest it as documentation.18:53
*** dkranz has quit IRC18:53
ayoungone other thing:  role Ids would be immutable, but role names would not.18:53
atiwariayoung, at the same time nested role-def are confusing and hard to implement18:53
atiwarimy view18:54
gyeeayoung, only problem is policy acts on role names, not IDs18:54
*** comay has quit IRC18:54
ayoungatiwari, so, you could do something like this:18:54
*** rongze has quit IRC18:54
gyeedon't believe middleware set the role IDs either18:54
*** mrodden has quit IRC18:55
atiwariayoung, I am advocation name space should be made of something immutable18:55
ayoungall the standard Openstack services are put into one of three projects:18:55
atiwarilike system generated id18:55
jamielennoxayoung: agree with gyee - renaming roles will be a problem18:55
nkinderwe would need to be careful that a scoped role is not named the same as a normal (unscoped) role to avoid ambiguity in the policy files.18:55
ayoungos-id:  (keystone, KDS)18:55
ayoungos_core (Nova, glance, swift)18:55
ayoungos-apps (Marconi etc)18:55
*** hemna has joined #openstack-meeting18:55
ayoungand you could do admin on multiple services based on the role a user has in that project, as opposed to specific to the service18:56
ayoungnkinder, so..we discussed reserving a separator18:56
jamielennoxnkinder: with the way that policy is written now, but can we change it so that we can specify "cinder:role1" in policy which is role1 in cinder without having to namespace them18:56
ayoung:  or \ or -> or something18:56
ayoungto indicate nesting18:56
gyeenkinder, we'll need role filtering based on scope18:56
atiwariayoung, that is not a workble because we have 1 to 1 with service and admin18:56
nkinderif the policy file has to specify the namespace, that works fine18:56
gyeei.e. nova only interested in nova roles18:57
*** gokrokve has quit IRC18:57
ayoungatiwari, 1 to 1 is the degenerate case18:57
atiwarigyee +118:57
*** jerryz__ has joined #openstack-meeting18:57
gyeethat's basically what atiwari is trying to address18:57
atiwarino it is not18:57
jamielennoxayoung: so i'm comfotable with roles belonging to a project or a domain18:57
atiwariif nova manage his role and and swift manage his18:57
nkinderok, so nova would only care about "nova:<role>" scoped roles, but doesn't it care about non-scoped roles too?18:57
jamielennoxif we are going to let user's add roles it's out only choice18:57
bknudsonwe already use domains for namespacing, so that seemed like the more natural fit18:57
atiwariwhat is the problem18:57
morganfainbergnkinder, i think that depends on the policy.json18:58
ayoungis if a user has a role on the glance service/project, and sends a token with that role assignment in it to the nova service, nova will ignore it.18:58
atiwariand keystone admin can manage all18:58
atiwariif needed18:58
morganfainbergnkinder, so deployer action. not implementation action18:58
ayoungnkinder, "care about" only for admin operations18:58
ayoung2 minutes remaining18:58
ayoungSo my take  :services are not containers, and should not become containers.  Services will not own role definitions directly, but rather will be paired with a project to manage the role definitions.18:59
atiwariso all I am trying to get is Nova/ Swift role-def is managed by nova/swift admin of keystone admin18:59
nkinderwe should just be careful about avoiding ambiguity to prevent one from accidentally granting access when they don't intend to.19:00
*** nono1 has joined #openstack-meeting19:00
atiwariayoung, that is why we should look for David's proposal19:00
ayoungTimes up19:00
atiwariwhich is not tight linking19:00
ayoung#endmeeting19:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"19:00
openstackMeeting ended Tue Dec  3 19:00:48 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-12-03-18.02.html19:00
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-12-03-18.02.txt19:00
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-12-03-18.02.log.html19:00
*** comay has joined #openstack-meeting19:01
gyeenkinder, you know what's really scary today, the role 'admin' works everywhere today :)19:01
gyeethere's no way to distinguish nova admin from swift admin today19:01
*** brich1 has quit IRC19:01
tristanCHello folks, can I ask a couple question before you guys leave ?19:01
clarkbjeblair: fungi morganfainberg pleia2 zaro et al meeting time?19:01
pleia2o/19:01
clarkber mordred ^19:01
zaroo/19:01
fungiyah19:01
mordredo/19:02
morganfainbergclarkb, hey, i can join you guys too...i just wont have much to say atm :(19:02
jeblair#startmeeting infra19:02
openstackMeeting started Tue Dec  3 19:02:19 2013 UTC and is due to finish in 60 minutes.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:02
* mordred hands morganfainberg his voice19:02
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:02
morganfainbergmordred is more useful i'm sure in that regard19:02
*** openstack changes topic to " (Meeting topic: infra)"19:02
openstackThe meeting name has been set to 'infra'19:02
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:02
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-11-26-19.02.html19:02
tristanCaww, I thought there was going to be an open meeting (for keystone) at the end :(19:02
jeblair#topic agenda19:03
*** openstack changes topic to "agenda (Meeting topic: infra)"19:03
morganfainbergtristanC, come chat w/ us in #openstack-dev19:03
* morganfainberg quiets up so Infra can do awesome stuff.19:03
*** nkinder has left #openstack-meeting19:03
jeblairbecause last week we did not get through the whole agenda19:03
jeblairand also there was this holiday in the us...19:03
* coolsvap is away: Away!!!19:03
jeblairi think we should skip things covered last week and start with things we did not get to.19:04
*** ryanpetrello has joined #openstack-meeting19:04
jeblair#action jeblair file bug about cleaning up gerrit-trigger-plugin19:04
jeblair#action jeblair move tarballs.o.o and include 50gb space for heat/trove images19:04
jeblair#action fungi grow logs and docs-draft volumes so they're 50% full19:04
jeblair#action fungi update docs for static to recommend 1t cinder volumes19:04
jeblair#action mordred to harrass hub_cap until he's writen the tempest patches19:04
*** coolsvap has quit IRC19:04
*** fabiog has quit IRC19:04
jeblair#topic  Maven clouddoc plugin move (zaro, mordred)19:04
*** openstack changes topic to "Maven clouddoc plugin move (zaro, mordred) (Meeting topic: infra)"19:04
jeblairzaro, mordred: you're up first! :)19:04
*** slagle_ has joined #openstack-meeting19:05
mordredthe repo moved19:05
clarkb\o/19:05
zarook. patch is up for review.19:05
zaro#link https://review.openstack.org/#/c/4609919:05
*** slagle has quit IRC19:05
*** slagle_ is now known as slagle19:06
zaro#link https://review.openstack.org/#/c/4793719:06
jeblairi think that's a future topic19:06
mordredI find this work exciting, btw19:06
zaroopps previous one was wrong. it's https://review.openstack.org/#/c/58349/19:06
zaroohh and i think we'll need core to create maven nexus accounts for this to work.19:07
zaro#link https://review.openstack.org/#/c/58349/19:07
jeblairzaro: can you point us at how to create those accounts?19:07
zaroI believe you just go onto oss.sonotype.org and create an account.19:08
*** sushil_ has quit IRC19:08
clarkbits a bit more tricky than that19:08
jeblairzaro: is dwcramer up to speed?  he knows the repo has been moved?19:08
clarkbas their release process requires gpg signing of things19:08
jeblairzaro: i don't see any reviews from him...19:08
zarojeblair: yes, been working with him.19:08
*** danwent has quit IRC19:08
zarojeblair: what review were you expecting?19:08
*** danwent has joined #openstack-meeting19:09
clarkbbut yes, you go to the sonotype site, submit a jira ticket ! and eventually you get an account. I was hoping for more solid footing on the gpg stuff before doing that though19:09
anteayao/19:09
jeblairclarkb: so jenkins needs to gpg sign artifacts before uploading?19:09
clarkbyes19:09
jeblairok.  i think we have a gpg key for jenkins, btw.19:09
clarkbwell something needs to sign it with a key that upstream trusts19:09
clarkbcool I didn't know that19:10
zarojeblair: yes, i sign the package when i do a release.19:10
jeblairclarkb: i believe that would be jenkins, in our system, right?19:10
jeblairwe're talking about tag based versioning, right?  where jenkins creates an artifact and uploads it based on a tag in gerrit...19:10
clarkbjeblair: yes, unless fungi has sorted out a better way of doing it19:10
jeblairzaro: i don't think there's an opportunity there for you to sign something.19:11
*** dkranz has joined #openstack-meeting19:11
clarkbI know fungi had ideas, but having jenkins sign is most straightforward19:11
clarkbzaro: jeblair: right, individual signs the git tag, jenkins signs the package19:11
fungione proposed alternative is to add a manual step for committing a detached signature to a repo and then having automation key off that change merging to do the upload of the package and sig together19:11
zarojeblair: ohh.  i seem to remember having to enter my password or something upon creating a tag.19:11
*** marekd is now known as marekd|away19:11
jeblairzaro: yes, the _tag_ should be signed.19:12
jeblairby you19:12
jeblairfungi: of what would the signature be?19:12
* ttx lurks19:12
fungisignature of the generated release artifact19:12
jeblairfungi: roger19:12
SergeyLukjanovmvn repo requires signed artifacts19:12
fungidownload the tarball or whatever it is, create a detached sig of it, and then upload a change containing that sig (to a separate signatures repo or branch or something)19:13
fungithis was the suggested alternative (or addition) to having automated package signing19:13
zaroclarkb: so what's the tricky bit again?  same process as the jenkins deployments right?19:13
jeblairi think we should proceed with jenkins signing for the clouddocs repo, for expediency19:13
clarkbzaro: the tricky bit is the signing, we can go the easy route or we can do fancy things that fungi suggests19:14
*** gokrokve has joined #openstack-meeting19:14
clarkbbut I don't want to setup accounts until we have at least a solid idea of which route we are going19:14
clarkbjeblair: ++19:14
jeblairfungi: because what you are discussing sounds more like something we want to do long-term for openstack releases19:14
mordredI agree with jeblair19:14
fungiwell, i only suggest them as an alternative to people who have expressed concerns about the simpler way19:14
clarkbright the simpler way seems like signing to have a signature19:14
clarkbrather than signing to actually trust a thing19:15
fungii am cool with the automated solution19:15
*** arunkant has quit IRC19:15
jeblairclarkb: well, it means you can trust that this thing was created by our jenkins.19:15
*** chandankumar has quit IRC19:15
*** colinmc__ has quit IRC19:15
*** colinm___ has quit IRC19:15
jeblairclarkb: and put the appropriate level of trust in 'a thing created by our jenkins'.  which may not be high.  :)19:15
fungithe upload slave can certainly provide some assertion. i already have a proposed mechanism in that bug, elegantly simple, to have it confirm the tag on the git repo matches the contents of the tarball it retrieves19:16
fungithe slave can't assert that it is not compromised itself, but it can at least indicate whether the tarball and/or git repo have been tampered with19:16
mordredI don't think the jenkins sig is perfect19:16
mordredBUT19:16
mordredit's better than no sig19:16
mordredand it's sooner than a perfect human sig19:17
mordredso we should at least do it19:17
jeblairyup19:17
mordredwhile we figure out a way to do the other thing thta doesn't kill us19:17
clarkb++19:17
jeblairzaro: have you signed up a core person to get a nexus account?19:17
fungino question. and i think it's possible to tack on the human sig solution without significant retooling later19:17
mordred++19:17
*** fbo_away is now known as fbo19:17
zarojeblair: nope, looking for volunteers.19:18
clarkbjeblair: zaro: I had looked at it at one point, and can look at it again. Unless someone more familiar with gpg wants to do it19:18
fungisign me up19:18
fungizaro: get me the specifics after the meeting19:18
zarofungi: you got it19:18
jeblair#action fungi create maven nexus account19:18
zarofungi: cool19:18
jeblairclarkb: fungi seemed to want it more.  :)19:18
jeblair#topic  Private gerrit for security reviews (zaro, fungi)19:19
*** openstack changes topic to "Private gerrit for security reviews (zaro, fungi) (Meeting topic: infra)"19:19
clarkb:) np my brain melted a little the first time I looked at it (probably overthinking the signing problem)19:19
fungizaro: sorry on this one--i haven't caught up far enough in my review backlog to revisit the current patchset19:19
*** shardy is now known as shardy_afk19:20
zaroohh.  i'm trying to remember todo list for this one.  but i think this one needs accounts as well.19:20
zarothe bigger thing it needs is for us to figure out how the projects will work.19:20
fungiyou mean as far as git replication vs uploaded changes?19:21
zaroclarkb says we should set acls in all-projects and have per-project acls19:21
fungior the manage-projects pieces19:21
zarothat's a lot of work.19:21
clarkbzaro: we do it today19:21
zaroyea, seems like a lot of work.19:21
clarkbits not that much work once you have it in place, the acls themselves don't change, just group membershio19:21
fungiright, that part. so the trick was working out a mechanism to manage the all-projects acl outside of gerrit's interface, including bootstrapping it. and the current suggestion is to punt because that's how we do the prod one19:22
zarowell.  if that's the way we do it now.  then i guess we replicate for private gerrit?19:22
fungiyes19:22
fungii think so, anyway19:22
*** sarob has joined #openstack-meeting19:23
zarook.  then i'll need to work with fungi to figure out all-project &  per-project acl settings.19:23
fungisounds good19:23
jeblairi'm okay with punting for this19:23
zarothen somehow get that all into config?19:23
jeblairi'm hoping that some of the folks working on downstream "infras" will contribute all-projects bootstrapping19:23
*** sdake has quit IRC19:24
fungizaro: yeah, i think it can be documented (the central bits) and then the per-project special acls can be kept in the config repo i think, applied via manage-projects like we do on prod19:24
zaroohh yea, also i remember looking at this and it seems like a lot of work change pp files to templates.19:24
*** sdake has joined #openstack-meeting19:24
jeblairfungi, mordred: though after bootstrapping, can't we manage all-projects acls in the usual way?19:24
*** Mandell has joined #openstack-meeting19:24
*** jlibosva has quit IRC19:25
clarkbjeblair: yes19:25
fungijeblair: yes, except for the part where it might lock you out19:25
jeblairfungi: ssh?19:25
jeblairfungi: more words:  in such a situation, we could fix it by shelling into the server, surely?19:25
fungisince the all-projects acl also controls whether your automation account can push changes for acls19:25
*** reed has quit IRC19:25
jeblairfungi: oh, and in that case we can even fix it using the webui.19:25
fungiyes, we could ssh in and hand-edit the acl on disk and hope we get it correct (or revert it would make more sense)19:26
fungibut correct, we could move that into config19:26
jeblairzaro, fungi: maybe the security gerrit can guinea-pig managing all-projects in git?19:26
*** ivar-lazzaro_ has joined #openstack-meeting19:26
jeblairzaro, fungi: and then we can extend that to regular gerrit19:26
*** nono1_ has joined #openstack-meeting19:27
clarkb++ I like that idea19:27
fungisure. an easy first step would be simply documenting the minimal initial acl needed to get manage-projects able to apply the full one19:27
zarowhy don't we guinea-pig in review-dev?19:27
jeblairthat would help the full bootstrapping process.19:27
jeblairzaro: that's fine too.19:28
*** reed has joined #openstack-meeting19:28
*** dkranz has quit IRC19:28
guitarzanwin 2319:28
zaroi'de prefer to keep it seperate because to get all the acls right would be a large change.19:28
*** terriyu has joined #openstack-meeting19:28
*** nono1 has quit IRC19:28
*** ivar-lazzaro has quit IRC19:28
jeblairzaro: what do you mean?19:28
zaroi think the right way to do the per-project acls would be to template the current set of alc config files.19:29
fungithough it's worth noting that there will be far fewer per-project acls for security reviewing. we can have one per program (not per project) receiving security support through the vmt, which is no more than a dozen in total19:29
zaroi'm not even sure how to do that yet.19:29
zaroohh, that's a revelation.  then maybe it's not such a big change.19:30
fungii'd suggest a field in the jeepyb projects.yaml which indicates the name of the security acl, and then maybe a little tweak to manage-projects to determine which kind of acl to apply19:30
jeblairfungi: sounds good.19:30
fungithat's just off the top of my head. might be better alternatives19:30
jeblairmordred: ^ you've been in this code lately; thoughts?19:31
clarkbwhy not two different project lists?19:31
fungialso doable, though results in more duplication19:31
clarkbmaybe that is too much trouble, but I don't see us putting stackforge projects on that server19:31
jeblairclarkb: that's a good idea.... also, might we want to use the track-upstream feature?19:32
fungii think we can either ignore the extra repos, or we can simply specialize manage-projects and the one yaml file a little further19:32
jeblairto have security-gerrit track regular gerrit?19:32
fungibut tracking might be a good feature to leverage there instead of using one list, agreed19:32
clarkbjeblair: I think we want to go the other way nad have regular gerrit update security gerrit19:32
clarkbjeblair: but tracking may be more sane depending on workflow19:32
jeblairclarkb: i think we said the same thing? :)19:32
*** vipul is now known as vipul-away19:33
*** vipul-away is now known as vipul19:33
clarkbjeblair: replication vs tracking19:33
fungiyeah, tracking branches on the security gerrit would pull in updates from public gerrit19:33
jeblairclarkb: security gerrit is downstream of regular gerrit.19:33
clarkbI prefer replication over tracking, but am not involved in the workflow19:33
jeblairclarkb: can you elaborate on what you mean by replication vs tracking?19:34
fungireplication also ends up sending the refs/for/stuff though, right? i mean, it can probably be ignored--i don't think it would cause collissions--but...19:34
clarkbjeblair: I want review.o.o to replicate its repos to review-secure.o.o. So that review-secure.o.o is always up to date19:34
clarkbjeblair: we might need to pick a crazy change number offset and that might still bite us, so not perfect19:34
*** gyee has quit IRC19:35
jeblairclarkb: isn't this what jeepyb's upstream-tracking is designed for?  to keep a downstream repo up-to-date with an upstream one?19:35
fungichange numbers are only a concept inside the db (change-id headers are also unlikely to collide)19:35
clarkbjeblair: sort of19:35
clarkbjeblair: I am not a fan of tracking fwiw19:35
clarkbit keeps certain branches in sync19:35
clarkbbut not the branches you want to work against in most cases, that is a manual step19:36
fungiclarkb: which, for security support development, is probably fine19:36
clarkbright it depends on the workflow19:36
fungiwe essentially want to track master and one or two stable branches per project we're supporting for this19:36
*** jcooley_ has quit IRC19:37
*** jcooley_ has joined #openstack-meeting19:37
clarkbfungi: so in this case all changes could be proposed against upstream/stable/foo rather than stable/foo19:38
mordredjeblair: sorry - was afk for a sec19:38
clarkband since changes won't get submitted and merged it is probably fine19:38
mordredjeblair: I agree that the work we're doing with track-upstream is EXACTLY trying to solve this issue19:38
jeblairclarkb: ok, i could see how replicating might be preferable by being a bit more real-time (and not depending as much on manage-projects)19:38
clarkbthe problems arise when you need to take upstream/stable/foo and stable/foo and not hate each other19:38
fungiclarkb: right. just provides a convenient place to iterate through code review, and then they get discarded, downloaded, and pushed to proper public gerrit19:38
mordredthe problem is exactly the same as a company working on a private fork of openstack that tehy're trying to track upstream on19:39
*** denis_makogon has joined #openstack-meeting19:39
fungimordred: agreed19:39
clarkbmordred: except in this case we shouldn't have the merge problem so I am ok with it19:39
mordred:)19:39
mordredhow about we take an action to sync up on the tracking thoughts19:39
mordredI think it's slightly verbose of a topic to cover this instant19:39
clarkb++19:40
zaro++19:40
fungiyes, meeting topic sufficiently beaten to death for this week19:40
jeblairi'm glad we uncovered this.  :)19:40
jeblair#topic  Upgrade gerrit (zaro)19:40
*** openstack changes topic to "Upgrade gerrit (zaro) (Meeting topic: infra)"19:40
zarook. best news of the week.19:40
zaro#link https://gerrit-review.googlesource.com/#/c/4825419:40
zaroit's merged!19:40
* fungi cheers loudly19:40
pleia2\o/19:40
pleia2congrats, zaro :)19:40
jeblairyaaaay!19:41
zarowhat now?19:41
jeblairzaro: this is post 2.8, and should be in 2.9, right?19:41
jeblairzaro: eta on 2.9?19:41
zaroyes.19:41
mordredwoohoo!19:41
*** dkranz has joined #openstack-meeting19:41
*** jcooley_ has quit IRC19:41
fungidoes this achieve upstream feature parity with our current workflows?19:41
jeblairfungi: or what we hope will be equivalent19:42
fungior is there more outstanding19:42
clarkbI would be ok with running a forked 2.8 with that patch on top of it if we can iterate that quickly19:42
clarkbthen go to 2.9 when that happens19:42
jeblairclarkb: me too, but i'm trying to figure out if that's necessary...19:42
*** jcooley_ has joined #openstack-meeting19:42
mordred++19:42
clarkbgerrit doesn't have release cycles aiui so 2.9 could happen whenever19:42
clarkbthough they seem better at doing them regularly now19:42
fungicarrying patches we know are already merged upstream and will go away when we upgrade seems okay *if& we need to do that19:43
clarkb_david_ might know19:43
jeblairzaro: so, assuming 2.9 isn't expected in, say, 2 weeks....19:43
*** otherwiseguy has quit IRC19:43
jeblairzaro: we pull 2.8 into openstack-infra/gerrit, build it, and deploy on review-dev19:43
jeblairfigure out what needs to happen to do the upgrade (if it's not fully automatic)19:44
zarojeblair: sounds good to me19:44
jeblairmake config changes, etc...19:44
jeblairthere are some _serious_ problems with the gerrit ui that have developed since the last time i looked19:44
mordredoh yeah?19:44
zarojeblair: do we want to do WIP vote or WIP button (plugin)19:44
zaro?19:44
clarkbchange screen 2 is not fungi device happy19:44
jeblairmordred: look at the link zaro sent19:44
mordredWOAH19:45
mordredthat's crazy looking19:45
jeblaircomments are too wide, the tabs can get even wider, meaning it won't fit even on a 1280 pixel wide screen19:45
jeblairit uses g+ avatars (i assume/hope that can be disabled)19:45
*** novas0x2a|laptop has joined #openstack-meeting19:45
clarkbI like some of the changes, in particular in the diff screen19:46
mordredthat cherry-picks thing is interesting19:46
fungithat is sorta wideish. i still have to scroll sideways when fullscreening a browser on a 1080px-wide display19:46
jeblairso anyway, i expect we have some tuning we may need to do.19:46
fungii'm hoping 1440px will be wide enough19:46
mordredI like that the reply button popup is better19:47
*** jcooley_ has quit IRC19:47
*** jcooley_ has joined #openstack-meeting19:47
fungimaybe they could make the layout configurable/skinnable19:48
jeblairfungi: i honestly don't know what's tunable, which is why i think we should get it up on review-dev and start poking at it19:48
clarkb++19:48
mordredjeblair: ++19:48
fungiyup, absolutely19:48
jeblairhopefully there are things we can do in config and css19:48
jeblairbut there's a possibility that some things may need upstream patches (if just to expose a parameter in config)19:49
jeblairso we should be prepared for that.19:49
SergeyLukjanovbtw how it looks like on MBA (1440x900) - https://dl.dropboxusercontent.com/u/33687550/Screen%20Shot%202013-12-03%20at%2011.48.21%20PM.png19:49
jeblairat any rate, as much as i'd like to roll this out as quickly as possible... we have _a lot_ of developers, so we need to get the details right.19:49
fungiyes, i think the fewer number of times we change this up on them in production, the happier everyone will be19:50
fungiit's going to be disruptive no matter how smoothly it goes19:50
jeblair#topic  Proposed next bug day: Tuesday, December 17th at 1700 UTC (pleia2)19:51
*** openstack changes topic to "Proposed next bug day: Tuesday, December 17th at 1700 UTC (pleia2) (Meeting topic: infra)"19:51
clarkbwe should also maybe compile a list of the good new features so that people are aware of them eg better search19:51
pleia2so I was looking at the calendar19:51
*** rongze has joined #openstack-meeting19:51
pleia2our final two meetings of the month land on Christmas Eve and New Years Eve19:51
*** jcooley_ has quit IRC19:51
pleia2I'm going to be doing the family thing for the holidays, so I'll be family + airplane respectively on these days19:51
pleia2but it would be nice to have a bug day before the new year, so December 18th19:52
pleia2err 17th19:52
fungii can be around for both those meetings, but suspect i might be one of the only people in here19:52
clarkb17th isn't good for me, but 18th should work19:52
clarkbor next week is good19:52
*** jcooley_ has joined #openstack-meeting19:52
zaroi'll be around19:52
clarkbisn't icehouse-1 this week?19:53
pleia2yeah19:53
clarkbwe could try to stick to week after milestone which would mean bug day next week19:53
*** vipul is now known as vipul-away19:53
pleia2wfm19:53
pleia2so December 10th19:53
jeblairi think we may cancel the christmas and new years meetings.  :)19:53
zaro++19:53
pleia2jeblair: yeah, I'm thinking that too19:53
clarkbpleia2: I like that plan19:53
fungii'm good with the 10th for bugs19:54
anteayame too19:54
pleia2great, I'll add it to our wiki19:54
fungithanks pleia2!19:54
jeblairpleia2: thanks!19:55
jeblair#topic  Zuul release (2.0?) / packaging (pabelanger)19:55
*** openstack changes topic to "Zuul release (2.0?) / packaging (pabelanger) (Meeting topic: infra)"19:55
*** sparkycollier has quit IRC19:55
jeblairpabelanger: i take this to mean you think it's time.  :)19:55
jeblairit's probably a bit past time, really19:55
pabelangerjeblair: Ya, I think we are ready to get started on packaging19:55
*** rakhmerov has quit IRC19:55
pabelangerand since it is a big change after 1.3 for the triggers, I guess we should consider 2.0?19:56
clarkbthough it might be worth waiting a bit to see if the split gate bug can be tracked down19:56
jeblairi will try to take a look and make sure it's ready (docs caught up with features, etc)19:56
jeblairand yes, definitely 2.0 -- it's full of breaking changes (documented in the NEWS file i believee)19:56
fungi2.z0mg19:56
clarkbjeblair: ++19:56
pabelangerEvent if it is not a full release, maybe an alpha?19:56
*** rongze has quit IRC19:56
pabelangerEven*19:56
jeblairpabelanger: i think we can do a full release soon19:58
pabelangerPerfect19:58
*** colinmcnamara has joined #openstack-meeting19:58
fungiwe certainly have tested it (in production!)19:58
jeblairindeed!19:58
jeblair#topic Open discussion19:59
*** openstack changes topic to "Open discussion (Meeting topic: infra)"19:59
jeblairanything else in the next minute? :)19:59
ryanpetrelloo/ not much time left19:59
ryanpetrellothought I'd mention a pecan review I have open19:59
ryanpetrellohttps://review.openstack.org/#/c/58643/119:59
ryanpetrelloit's failing to run ceilometer tests, as it can't connect to mongodb for some reason19:59
ryanpetrelloI nagged Monty about it yesterday, but just thought I'd ask around again19:59
mordredI have looked at the above and find it very odd19:59
*** colinmcn_ has joined #openstack-meeting19:59
clarkbmongodb is only available on the centos slaves19:59
mordredbecause the log does show mongo launching successfully19:59
ryanpetrelloI can confirm that it works just fine when run via tox on my own precise images on DH's cloud19:59
clarkbwhere are those jobs running?19:59
fungii will be disappearing for a couple hours tomorrow afternoon20:00
fungilocal osug meetup20:00
clarkbmongodb on precise is too old for ceilometer20:00
clarkboh I am disappearing tomorrow mid day due to dentist20:00
mordredah. that might be the problem ryanpetrello is seeing then :)20:00
ryanpetrelloyep, that might be it20:00
*** mrodden has joined #openstack-meeting20:00
*** markvan has quit IRC20:00
jeblairthanks everyone20:00
jeblair#endmeeting20:00
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"20:00
openstackMeeting ended Tue Dec  3 20:00:58 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-12-03-19.02.html20:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-12-03-19.02.txt20:01
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-12-03-19.02.log.html20:01
ttxReminder: No TC meeting today. Next meeting is the project/release status meeting in one hour.20:01
*** kevinconway has quit IRC20:01
ruheryanpetrello, afaik, ceilometer doesn't work with devstack/mongo env, but you can manually upgrade mongo20:01
* jeblair has a real lunch for a change20:01
ryanpetrelloruhe: odd, I wonder what the ceilometer folks are doing to make their tests pass, then20:01
*** kevinconway has joined #openstack-meeting20:02
*** neelashah has quit IRC20:02
*** rockyg has joined #openstack-meeting20:03
clarkbryanpetrello: they only run on centos6 nodes20:03
*** markvan has joined #openstack-meeting20:03
*** epim has joined #openstack-meeting20:03
*** dhellmann has quit IRC20:04
mordredryanpetrello: you may want to tie your ceilo tests to centos620:04
*** pabelanger has left #openstack-meeting20:04
*** vipul-away is now known as vipul20:04
*** egallen has quit IRC20:06
*** MaxV has joined #openstack-meeting20:06
*** jcooley_ has quit IRC20:06
*** neelashah has joined #openstack-meeting20:06
*** pdmars_ has joined #openstack-meeting20:07
*** pdmars_ has quit IRC20:07
*** pdmars_ has joined #openstack-meeting20:08
*** kevinconway has quit IRC20:08
*** dhellmann has joined #openstack-meeting20:09
*** pdmars has quit IRC20:09
*** kevinconway has joined #openstack-meeting20:11
*** dolphm has joined #openstack-meeting20:11
*** vipul is now known as vipul-away20:11
*** vipul-away is now known as vipul20:12
*** steven-weston has quit IRC20:13
*** DinaBelova has quit IRC20:15
*** salv-orlando has joined #openstack-meeting20:17
*** ttrifonov is now known as ttrifonov_zZzz20:19
*** vkozhukalov has quit IRC20:19
*** pdmars has joined #openstack-meeting20:24
*** pdmars_ has quit IRC20:25
*** Abhishek has quit IRC20:25
*** IlyaE has joined #openstack-meeting20:26
*** vipul is now known as vipul-away20:27
*** Abhishek has joined #openstack-meeting20:27
*** salv-orlando_ has joined #openstack-meeting20:28
*** pdmars has quit IRC20:29
*** sushils has joined #openstack-meeting20:29
*** ttrifonov_zZzz is now known as ttrifonov20:30
*** salv-orlando has quit IRC20:30
*** salv-orlando has joined #openstack-meeting20:31
*** salv-orlando_ has quit IRC20:33
*** nermina has quit IRC20:36
*** xyang has joined #openstack-meeting20:36
*** xyang has quit IRC20:38
*** bknudson has left #openstack-meeting20:38
*** kui has joined #openstack-meeting20:39
*** rockyg has quit IRC20:42
*** jasondotstar has quit IRC20:45
*** vipul-away is now known as vipul20:45
*** johnthetubaguy has quit IRC20:50
*** salv-orlando has quit IRC20:51
*** jcooley_ has joined #openstack-meeting20:51
*** jcooley_ has quit IRC20:53
*** rongze has joined #openstack-meeting20:53
*** rakhmerov has joined #openstack-meeting20:56
*** dhellmann has quit IRC20:58
*** carl_baldwin has joined #openstack-meeting20:58
*** rongze has quit IRC20:58
*** kevinconway has quit IRC20:59
*** dhellmann has joined #openstack-meeting20:59
ttxo/21:00
*** pdmars has joined #openstack-meeting21:00
notmynamehi21:00
ttxdhellmann: you're with us ?21:00
ttxdolphm, jd__, markwash, jgriffith, russellb, stevebaker, david-lyle, markmcclain, hub_cap: around ?21:00
russellbo/21:00
hub_cappresent21:00
david-lyleo/21:00
markwasho/21:00
*** vipul is now known as vipul-away21:00
dimso/21:01
hub_capbut grr irssi didnt notify me.. i thik cuz of the colon in my name hub_cap_colon21:01
*** kevinconway has joined #openstack-meeting21:01
ttxdims: you're replacing dhellmann ?21:01
dimsttx, yep21:01
*** hartsocks has joined #openstack-meeting21:01
* ayoung here for Keystone21:01
ttxayoung: ok21:01
dolphmo/21:01
*** markmcclain has joined #openstack-meeting21:02
ttx#startmeeting project21:02
openstackMeeting started Tue Dec  3 21:02:12 2013 UTC and is due to finish in 60 minutes.  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
ttx#link http://wiki.openstack.org/Meetings/ProjectMeeting21:02
ttx#topic Icehouse-121:02
*** openstack changes topic to "Icehouse-1 (Meeting topic: project)"21:02
*** jerryz__ has quit IRC21:02
ttxWe looked into that during the 1:1s today21:02
ttxA few blueprints are still incomplete21:03
markmcclaino/21:03
ttxThe plan is to defer anything that doesn't make it before I cut the branches21:03
ttxwhich should be tomorrow morning Europe time, late night US time.21:03
* ttx checks for recent status changes21:03
* russellb will make a pass through deferring stuff before EOD21:03
russellbhaven't done it yet21:03
*** rockyg has joined #openstack-meeting21:03
jgriffitho/21:03
SergeyLukjanovo/21:04
*** neelashah has quit IRC21:04
*** nermina has joined #openstack-meeting21:05
ttxmarkmcclain: how is neutron-tempest-parallel doing ?21:05
ttxrussellb: recover-stuck-state is completed now ?21:05
ttxdims: standalone-rootwrapis not really affected by EOD but could still use a hand at: https://review.openstack.org/#/c/59745/21:06
stevebakero/21:06
dimsttx, will look21:06
ttx(that's the only oslo blueprint left)21:06
russellbttx: yes, and i just marked it implemented21:07
*** boris-42 has joined #openstack-meeting21:07
ttxrussellb: ok21:07
*** shardy_afk is now known as shardy21:07
ttxSo... any objection to the big deferral plan tomorrow ?21:07
ttxI guess that's a no21:08
hub_capheh guess thats a no :)21:08
hub_caplol ttx21:08
ttxI'll just wait if a few reviews get stuck in queue21:08
ttxbut everything missing the necessary approvals will get punted when I reach 3G/wifi21:09
* ttx on a train tomorrow morning21:09
markwashttx: yeah, oslo-messaging for glance is on its way, it might take a little while through the queue21:09
ttx#topic Swift 1.11.021:09
*** openstack changes topic to "Swift 1.11.0 (Meeting topic: project)"21:09
ttxSo Swift 1.11.0 will be released once the last two blockers (a blueprint and a critical bug) are cleared.21:09
notmynamelast two patches should merge Real Soon Now (tm)21:09
ttx#link https://launchpad.net/swift/+milestone/1.11.021:09
ttxRough ETA is end of week for the MP branch cut and hopefully mid-nextweek for release21:09
markmcclainIt will be deferred21:10
ttxnotmyname: anything you want to add ?21:10
notmynamenope21:10
ttxmarkmcclain: ok21:10
*** FallenPegasus has joined #openstack-meeting21:10
*** markvan has quit IRC21:10
ttx#topic Icehouse cycle roadmapping21:10
*** openstack changes topic to "Icehouse cycle roadmapping (Meeting topic: project)"21:10
ttx#link http://status.openstack.org/release/21:10
*** sandywalsh_ has quit IRC21:10
ttxWe have 208 tracked blueprints (completed or >=Medium prio) at this point21:11
ttxAt this point it should reflect what we expect to land during icehouse21:11
ttx...at least by our current knowledge21:11
ttxThe trick now is to try to keep it current as we learn more, so try to stay on top of proposed work21:11
*** vuil has quit IRC21:11
hub_capttx: the i1 for trove is Implemented now (just changed a few min ago)21:11
ttxwhich can be rather tricky as people continue to propose new work all the time21:11
ttxhub_cap: ack, trove all set21:12
ttxQuestions on that roadmapping part ?21:12
*** vuil has joined #openstack-meeting21:13
ttx#topic Red Flag District / Blocked blueprints21:13
*** dhellmann has quit IRC21:13
*** openstack changes topic to "Red Flag District / Blocked blueprints (Meeting topic: project)"21:13
*** weshay has quit IRC21:13
ttxThere are a number of blueprints marked "Blocked"...21:13
ttxThe idea is to keep that status for blueprints we need to discuss in-meeting, not for stuff that is "normally blocked" waiting for dependent blueprints to be merged21:13
ttx(at least not until the absence of progress on dependent blueprints is starting to seriously jeopardize the blocked blueprint)21:13
*** noslzzp has quit IRC21:13
ttxlet's see.. we have 5 of them21:14
ttxhttps://blueprints.launchpad.net/heat/+spec/instance-users21:14
*** dhellmann has joined #openstack-meeting21:14
ttxstevebaker: anything particular you wanted to discuss about that one ?21:14
stevebakerttx: refresh your browser ;)21:14
ttxdamn, relying on stale release statuys view21:15
ttxhttps://blueprints.launchpad.net/heat/+spec/x-auth-trust then21:15
hub_capi suspect his answer may be the same ;)21:15
*** nono1_ has quit IRC21:15
*** ivar-lazzaro_ has quit IRC21:15
ttxWell I reloaded that one.21:15
stevebakerttx: that should remain blocked, but possibly priority should be Low21:15
ttxand it's still blocked :)21:15
ttxstevebaker: what is in blocking on ?21:16
lifelesso/21:16
ttxkeystone/trusts-chained-delegation21:16
ttx?21:16
*** egallen has joined #openstack-meeting21:16
*** uri__ has joined #openstack-meeting21:16
stevebakerttx: chained-delegation in keystone, which shardy may end up working on anyway21:16
stevebakerhttps://blueprints.launchpad.net/keystone/+spec/trusts-chained-delegation21:17
stevebakeryet to be approved21:17
ttxstevebaker: ideally we would use another status than "Blocked" if there is nothing to discuss yet to unblock it. "Not started" looks fine by me21:17
stevebakerok21:17
dolphmthe x-auth-trust bp is new to me... reading that now21:18
ttxjust set it back to "Blocked" if for example it gets rejected by Keystone or theer is something cross-project to discuss to unblock it21:18
ttxdavid-lyle: you cleared the Blocked status for the Horizon one, cool21:18
ttxones*21:19
david-lyleyes21:19
ttxAny other blocked work that this meeting could help unblock ?21:19
*** vipul-away is now known as vipul21:19
*** dhellmann has quit IRC21:19
ttxbah, I expect we'll have more as we go deeper in the cycle21:20
ttx#topic Incubated projects21:20
*** openstack changes topic to "Incubated projects (Meeting topic: project)"21:20
devananda\o21:20
ttxdevananda: o/21:20
ttxhow is ironic going those days ?21:20
devanandagetting closer21:21
*** dhellmann has joined #openstack-meeting21:21
ttxanyone from savanna or Marconi ? SergeyLukjanov ?21:21
ttxdevananda: still targeting i-2 for your first clear milestone ?21:21
SergeyLukjanovttx, everything is ok in savanna - https://launchpad.net/savanna/+milestone/icehouse-121:21
SergeyLukjanovttx, I'll cut the m-p today21:22
*** vuil has quit IRC21:22
ttxSergeyLukjanov: I can do it as I do the others tomorrow, if you want21:22
devanandattx: yes. at the very least, I will want to go through all the milestone & release stuff with you at that point. and I think we are still on target to have soething that (mostly) works by then21:22
SergeyLukjanovttx, good, thanks21:22
ttxSergeyLukjanov: will let you know if I run into a problem21:22
devanandawe might not have some of the less used features of nova-bm, like console support21:23
devanandaromcheg's work on tempest / devstack integration got blocked for a bit on infra work. i think that's unblocked now.21:23
SergeyLukjanovttx, ok21:23
*** radez is now known as radez_g0n321:23
ttxdevananda: it's mostly a question of following most of https://wiki.openstack.org/wiki/PTLguide21:23
ttxany other question ?21:24
devanandattx: ack. i've read it a few times :)21:24
*** jcooley_ has joined #openstack-meeting21:24
devanandanope21:24
ttxSergeyLukjanov: I can run the branch cut just after meeting if you prefer, although I don't want to make you stay up even later21:25
ttx#topic Open discussion21:25
*** openstack changes topic to "Open discussion (Meeting topic: project)"21:25
ttxrussellb: was PowerVM removed already ?21:26
russellbyes21:26
ttxok21:26
ttxanything anyone ?21:26
SergeyLukjanovttx, doesn't matter for me, btw I'll be here for about hour21:26
ttxSergeyLukjanov: ok, let's try, looks like meeting will close soon21:27
*** sandywalsh_ has joined #openstack-meeting21:27
*** colinmcn_ has quit IRC21:27
*** colinmcnamara has quit IRC21:27
notmynameo/21:27
*** dhellmann has quit IRC21:27
SergeyLukjanovttx, ok21:27
ttxunless someone wants to discuss Critical vs. High for non-deterministic bugs affecting gate again21:27
russellbmarkmcclain: anything we need to sync up on re: neutron vs nova-network?21:27
ttxnotmyname: go for it21:27
*** gyee has joined #openstack-meeting21:28
ttxmarkwash: got enough clarity around your client release questions ?21:28
notmynameperhaps this should stay on the mailing list for now, but a cross-project issue on the horizon is the "keystone for quotas" issue that was brought up recntly21:28
markwashttx, yeah I can give a little update here I think21:28
notmynameI'm fine leaving it on the ML for now21:28
notmynameor we can discuss here21:28
ttxnotmyname: I'm fine with discussing it a bit here. Although I haven't read that thread yet :)21:29
ayoungnotmyname, that is something that can be done in pieces.  They need an initial implemenation and REST API21:29
*** rakhmerov has quit IRC21:29
* ttx goes to read thread21:29
* russellb isn't up to date on that thread either ...21:29
notmynamettx: tl;dr as I know it is keeping all quota info in keystone21:30
ayoungI'd like Quotas to be kind of like KDS:  something that gets incubated in Keystone, but with the potential to move elsewhere.  They are going to need to be able to do an initial population of quota data when the service comes up, or when the first usr hits it, so the REST API has to be first.21:30
ayoungNotifications can come later21:30
ttxat the very least it's fine to attract our collective attention to threads that should be interesting for us21:30
* russellb wonders what the benefit is?21:30
ayoungnotmyname, do it as a n extension, like how we implemented KDS, and if we need to push it it a separate service, we can do that over time21:30
notmynameayoung: actually what I'm concerned with is the idea of storing all the quota info in keystone. I don't think that's tennable21:30
dolphmi don't see quotas as being a distinct service, at least in keystone21:31
*** ruhe has quit IRC21:31
ayoungdolphm, right, just the potnetial to split it out as a performance optimization.21:31
russellbwhat's the tl;dr for why this is a good idea?21:31
dolphmnotmyname: i like the 'flavor' suggestion from the list21:31
russellbvs a quota lib21:32
notmynamerussellb: it's not (IMO) ;-)21:32
russellbnotmyname: right, got that much, asking from supporters :)21:32
ttxnotmyname: that's typically the sort of thing that would benefit from being visited in a cross-project session at a design summit21:32
russellbindeed21:32
ttxbecause it's so far-reaching21:32
markwashnotmyname: I share that view.. it seems like quotas tend to need to stored alongside the resource they affect for performance reasons. . I guess some quotas don't fall into that category though maybe21:32
notmynamettx: isn't this meeting the cross-project place to discuss stuff more than twice a year?21:32
ayoungttx, it happened...back in Portland.  We scoped it down to just "static quotas" in Keystone21:32
ttxnotmyname: it is, it is21:32
russellbmarkwash: yeah, same21:33
russellbwhat are static quotas?21:33
ttxnotmyname: just thinking out loud... something of this magnitude should have been brought up earlier21:33
russellband why does it make sense for keystone to own them?21:33
ttxif it's to appear in this cycle21:33
russellbi guess I need to read the thread21:33
russellbbut count me as a skeptic :)21:33
ttxrussellb: more than the thread we need to look at the spec21:34
russellbi assumed the thread would reference such a thing21:34
dolphmrussellb: i haven't heard a strong argument for keystone; i agree with ayoung... requirements will likely grow very complex and we'll end up with a quota service in stackforge21:34
ayoungstatic quotas are the limits, not the portion of them that are currrently in use21:34
dolphmayoung: ++21:34
ayoungwe would not make Keystone the clearing house for "has this user gone over their quote"21:34
*** markmcclain has quit IRC21:34
markwashI think there is a great usecase though for administration / management to have one overall view of quota settings21:34
russellbstill seems odd21:34
ttxISTR the idea was that some quotas might span multiple projects21:34
dolphmit's centralized quota storage, quota distribution via notifications, and decentralized reservations, etc21:34
russellbmarkwash: couldn't you make the same argument for *all* resources owned by a given user/tenant/project/whateverwecallittoday?21:35
notmynameany sort of centralized quota storage seems like a bad idea, if it's in keystone or separate21:35
markwashrussellb: heh, perhaps21:35
ttxnotmyname: maybe let everyone think about it, and add it for discussion at next week meeting21:36
ayoungso I still don't like the notifiation portion of that.  I would rather have the services query it for now.  Question is "at what granularity" and  I think notifications has to address the same question.21:36
russellbI think it's the job of some administrative thingy on top of all of these APIs to make that easier to consume and appear together as it makes sense21:36
dolphmttx: not sure i've heard the multi-project quota use case?21:36
notmynamettx: sure. just seemed like something important, especially early in the process21:36
dolphmayoung: why do you want them to query for it?21:37
notmynamedolphm: buy 10 VMs and get 10GB free in cinder/swift?21:37
ttxnotmyname: it is important, and I think it's great to mention the thread here21:37
ayoungdolphm, I want them to query for it first, since that API needs to be implemented regardless.21:37
dolphmnotmyname: lol fair enough21:37
notmynamedolphm: but that gets into lots of external integrations21:37
dolphmayoung: oh sure21:37
ttxnotmyname: just thinking that most of us haven't read the spec so have no good idea about it21:37
dolphmayoung: on startup, HTTP query for it21:37
dolphmayoung: or on first use21:37
notmynamettx: if you add it to the agenda, can you respond to the thread with that info?21:38
ttxyes, doing it right now21:38
dolphmis this for TC?21:38
dolphmor..?21:38
notmynameno for in here21:38
*** vipul is now known as vipul-away21:39
ttxno, here21:39
*** vipul-away is now known as vipul21:39
ayoungdolphm, Notifications have the possibility of being very chatty, as there will be multiple potential consumers, and lots of little notifications that would never really need to be processed.  I suspect taht a query API would serve better over time.21:39
*** FallenPegasus has quit IRC21:39
dolphmi think it was sandywalsh_ that pushed back on replacing nova's own storage of quotas -- he asked that keystone simply provide updates to nova's existing quota persistence21:39
notmynameayoung: as in a client request would result in a query to keyston/quota_service from the server to see if the quota is full?21:40
dolphmayoung: why would there be a lot of little notifications? i suspect quota changes are relatively rare21:40
ttxnotmyname: done21:40
dolphmespecially if you use the 'flavor' concept21:40
notmynamettx: thanks21:40
ayoungnotmyname, yeah, logic along the lines of the token revocation list:  it will be cached for some period of time, and refreshed.  Notifications could even just be "hey, there is a new one, refresh"21:41
ttxLet's read the thread, the spec and discuss more next week21:41
ttxmarkwash: you wanted to summarize the client release thing ?21:41
markwashtime for a quick mention of the current plan for major client releases?21:41
markwashsure21:41
markwashThere was some discussion a while back about how to stage changes that are part of a major version release of openstack clients. Glance needs this as we'd like to deprecate some crazy old cli stuff and make a few other minor, generally palatable changes.21:41
notmynameayoung: and to be very specific, therefore a client request to a swift cluster would result in the swift cluster asking keystone for the quota usage? that's billions of things to track21:41
*** jdob has quit IRC21:41
markwashso the plan that is shaping up now is21:41
markwash1) use a feature branch21:41
markwash2) cut 1.0 once the feature branch is complete21:41
*** markvan has joined #openstack-meeting21:41
markwashat no point would we be supporting both v0 and v1 simultaneously21:42
markwashthis is still sort of limited in its applicability, i.e. it wouldn't work for truly major changes21:42
ayoungnotmyname, something has to store it.  I think that Keystone versus some other service is not the real issue, but how to store, update, and query.21:42
markwashbut I think it gets the job done for us without requiring a lot of changes on the CI side21:42
mordredhi!21:42
*** mrodden1 has joined #openstack-meeting21:42
markwashplease feel free to tell me how that plan is crazy and I should crawl back into my hole21:42
ttxmordred: oh hi!21:42
mordredI was just about to send you an email with a plan that's pretty opposite to that :)21:42
dolphmmordred had concerns about how that works in testing infra ... i don't remember specifics, but were those resolved by deciding not to support both at once?21:42
markwashoh okay cool21:43
*** ndipanov has quit IRC21:43
mordredI have a couple of specific issues21:43
dolphmhow does tempest "switch" over, etc?21:43
ttxmaking progress here I see21:43
*** bauzas has quit IRC21:43
*** matiu has quit IRC21:43
mordredone of the main ones being how stable/X deals with teh API change21:43
markwashyes, that's a good thing to be concerned about21:43
mordredbut - srrsly, today has been kicking my ass - let me write up something longform with justifications and details and send it to markwash and the list21:43
*** mrodden has quit IRC21:43
anteayarussellb: I know markmcclain wanted to talk to you, too bad his connection collapsed. I am meeting with him tomorrow and will draw his attention to your question.21:43
mordredI think if I try to vomit it here you'll all just kill me21:44
markwashI'm fine with waiting a bit21:44
mordredbut- tl;dr I think you're going ot have to support v0 and v1 side by side for at least a year21:44
mordredbecause deprecation21:44
* mordred waits to be shot21:44
russellbanteaya: yeah we have a hard time connecting21:44
russellbbusy busy21:44
anteayarussellb: nod21:45
* russellb shoots mordred with kindness21:45
russellbor something21:45
mordredyay!21:45
* mordred gets to take a nap now21:45
markwashnot a problem for me21:45
mordredmarkwash: but if we can do that - then we can have a 'simple' plan21:45
mordredmarkwash: where we release a 1.0 that also has the 0.x api in it21:45
mordredmarkwash: then bump the min ver on all of our server requirements to >= 1.021:46
dolphm ^ this is what we're planning for keystone, basically21:46
mordredthen, once the server releases that require less than that are gone, we can release a thing with 0.0 removed, probably called 2.021:46
mordredthis is where the libtool version age thing is really nice21:46
mordredin that it allows you to specify that you have added na api, but that you support X number of previous apis21:47
markwashhmm, interesting21:47
mordredit's too bad our friends in semver have not adopted it21:47
*** fbo is now known as fbo_away21:47
mordredanywho - lemme write up more details - but I think we can do it without getting ourselves in pretzels21:47
ttxok21:47
ttx#action mordred to expose his evil plan on a ML thread21:48
mordredoh god. I have an action21:48
mordredhow did that happen21:48
ttxmordred: "lemme write up more details"21:48
ttxmagic words :)à21:48
ttx:) even21:48
* mordred shoots ttx with kindness21:48
anteayalooks like you have a cleft in your chin21:49
ttxok, anything else ?21:49
*** thingee has joined #openstack-meeting21:50
ttxI'll take that as a no again21:50
*** MarkAtwood has joined #openstack-meeting21:50
hub_capheh ttx21:50
hub_capjust hugs21:50
ttxthx everyone21:50
ttx#endmeeting21:50
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"21:50
openstackMeeting ended Tue Dec  3 21:50:57 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:50
openstackMinutes:        http://eavesdrop.openstack.org/meetings/project/2013/project.2013-12-03-21.02.html21:50
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/project/2013/project.2013-12-03-21.02.txt21:51
openstackLog:            http://eavesdrop.openstack.org/meetings/project/2013/project.2013-12-03-21.02.log.html21:51
*** rockyg has quit IRC21:51
*** nermina has quit IRC21:53
*** mrunge has joined #openstack-meeting21:53
*** rongze has joined #openstack-meeting21:55
*** lcheng has joined #openstack-meeting21:56
*** uri__ has quit IRC21:56
*** stevemar has quit IRC21:57
*** jeckersb is now known as jeckersb_gone21:57
*** casanch1 has joined #openstack-meeting21:58
*** safchain has joined #openstack-meeting21:59
*** kspear_ has joined #openstack-meeting21:59
*** bdehamer has joined #openstack-meeting22:00
*** rongze has quit IRC22:00
david-lyle#startmeeting Horizon22:01
openstackMeeting started Tue Dec  3 22:01:29 2013 UTC and is due to finish in 60 minutes.  The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot.22:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:01
*** openstack changes topic to " (Meeting topic: Horizon)"22:01
openstackThe meeting name has been set to 'horizon'22:01
*** hartsocks has left #openstack-meeting22:01
julimhi there22:01
lsmolahello22:02
casanch1hello22:02
mrungehey22:02
devlapso/22:02
jtomasekhi22:02
bdehamerhello22:02
lchenghello22:02
david-lyleHello everyone22:02
david-lyleSo the freeze for Icehouse-1 is today22:02
*** jcoufal has joined #openstack-meeting22:02
*** carl_baldwin has left #openstack-meeting22:02
david-lylethere are still a few items pending review22:02
*** pdmars has quit IRC22:02
jcoufalo/22:02
david-lylehttps://launchpad.net/horizon/+milestone/icehouse-122:03
david-lyleWhat doesn't merge in the next few hours will just get moved to i-222:03
david-lyleI do think a couple of the items are close though22:03
*** ivar-lazzaro has joined #openstack-meeting22:04
*** garyk1 has joined #openstack-meeting22:04
*** lblanchard has quit IRC22:04
orion66hello everyone22:04
jomarahowdy22:04
lsmoladavid-lyle, darn, the inline-edit patch got some selenium error, thought it passed like 3 hours ago :-)22:04
lsmoladavid-lyle, it is destined to fail :-)22:04
*** boden has quit IRC22:04
david-lyleAside, from that, I spent time this week trying to cobble together a plan for icehouse as a whole22:04
MaxVo/22:05
david-lyleif anyone feels there's a misalignment or something I overlooked, please change it or contact me to change it22:05
*** krtaylor has quit IRC22:05
david-lyleI may have also assigned a couple of owners that weren't, again I can correct if something is incorrect22:06
ekarlsoyo gang, is there any clue on when the notifications stuff that have been talked so much about will land ?22:06
david-lylelsmola, I saw that, no worries22:06
*** tanisdl has quit IRC22:06
*** garyk has quit IRC22:06
*** reed has quit IRC22:06
david-lyleekarlso, I added the real-time work shadower started back in for i-222:06
david-lylelanding, not sure, that was mostly a proof of concept22:07
ekarlsowill it land this time during the cycle ?22:07
ekarlsosigh22:07
*** matty_dubs has joined #openstack-meeting22:07
*** fifieldt has joined #openstack-meeting22:07
david-lyleekarlso: it needs eyes and time using22:07
*** reed has joined #openstack-meeting22:07
ekarlsois there any recent patchsets  ?22:08
lsmolaekarlso, yeah i guess shadower would appreciate some feedback22:08
david-lyleekarlso: not that I am aware of22:08
ekarlsoshadower: ? ;)22:08
lsmolaekarlso, there weren't many reviews22:08
casanch1what about the bug fixes that still didn't make it to master?22:08
ekarlsoit would be a great addition to have :(22:08
lsmolaekarlso, yeah, it's the guy assigned to that22:09
david-lylecasanch1: 66 bug fixes landed in i-122:09
mrungecasanch1, that can't happen22:09
ekarlsoshadower: any recent work on it ?22:09
*** Toshi has joined #openstack-meeting22:09
mrungecasanch1, or misunderstood you?22:09
lsmolaekarlso, or is there some newer patch?22:09
ekarlsolsmola: thats22:09
david-lylepatches are coming in at about 4.9 per day22:09
ekarlsowhat I am wondering about ;)22:09
mrungecasanch1, you mean a patch landed in havana. but not in icehouse?22:09
*** reed has quit IRC22:10
*** sdake_ has quit IRC22:10
casanch1yes, I mean the bugs that are still under review22:10
david-lyleby coming in, I mean up for review22:10
casanch1waiting for approval22:10
*** reed has joined #openstack-meeting22:10
casanch1but if it's ok to postpone them to i-2, there's no problem22:10
lsmolaekarlso, no recent work, as far as I know22:10
*** sdake_ has joined #openstack-meeting22:11
david-lylecasanch1: anything that didn't land in i-1 that was targeted to i-1 automatically gets targeted to i-222:11
*** radsy has joined #openstack-meeting22:11
*** mrodden1 has quit IRC22:12
casanch1oh ok22:12
david-lyleI understand review time lag can be frustrating, I feel that too22:12
david-lyleThe best thing to speed things up is provide reviews22:13
david-lyle:)22:13
jpichYes, please help review other patches, it really helps :)22:13
*** thingee has left #openstack-meeting22:14
david-lyle#topic Agenda22:14
*** openstack changes topic to "Agenda (Meeting topic: Horizon)"22:14
MaxVI'd like to review all futur patches about Angular22:14
david-lylehttps://wiki.openstack.org/wiki/Meetings/Horizon22:14
*** ayoung has quit IRC22:14
jomaraMaxV: +122:15
david-lyleMaxV: please do22:15
jomaraMaxV: you did an outstanding job with mine22:15
MaxVIf someone sees one, or make one ping me22:15
david-lyleyour input is greatly valued22:15
*** noslzzp has joined #openstack-meeting22:15
david-lyle#topic Review IA proposal22:15
*** openstack changes topic to "Review IA proposal (Meeting topic: Horizon)"22:15
david-lyleThis was a carry over from last week.  I posted a mind map diagram to http://ask-openstackux.rhcloud.com/question/1/openstack-ui-information-architecture/22:16
david-lyleI still need to write the prose22:16
david-lyleSo, this is just a reminder to provide feedback if there's anything you disagree with22:17
david-lyleA lot of what's in there in contingent on the RBAC work which is progressing slowly :)22:17
david-lylebut I think bdehamer may be coming to assist on that22:17
jcoufalthat's great news22:17
jcoufaljust quickly connected to that22:18
david-lyle#topic Jasmine (MaxV)22:18
*** openstack changes topic to "Jasmine (MaxV) (Meeting topic: Horizon)"22:18
jcoufalok, I'll leave it to open discussion :)22:18
david-lyleMaxV made a proposal on the mailing list22:18
jomara+1 to proposal22:18
jtomasek+122:19
MaxVyou also have a blueprint, if someone wants to check https://blueprints.launchpad.net/horizon/+spec/jasmine-integration22:19
jtomasekI still need to have a look, but MaxV, how does it integrate with selenium? Are there any issues?22:19
MaxVthere also are a few POC https://review.openstack.org/#/q/status:open+project:openstack/horizon+branch:master+topic:jasmine-jshint,n,z22:19
lsmolajasmine sounds very good, +1 to that22:20
MaxVI made it working through selenium22:20
MaxVthe error messages are retrieved server side22:20
MaxVand fire as a failure of the test22:20
MaxVI also wrapped jshint22:21
jomaraawesome! jshint is very necessary22:21
*** danwent has quit IRC22:21
jomaraas you can tell by my flagrant lack of semicolons22:21
MaxVIt logs the first 10 failures22:22
*** ryanpetrello has quit IRC22:22
*** dprince has quit IRC22:22
MaxVI also wants to make a runserver-test command22:22
MaxVwhich will brings up a testing server22:22
MaxVsome people are interested?22:22
MaxVselenium will be used for the packaging and checking regressions22:23
MaxVI'm a little on fire, you can say calm down :)22:23
david-lyleMaxV: the test server is for the Jasmine tests only?22:23
jpichWhat do you mean with testing server, how much does it do?22:24
*** galstrom_zzz is now known as galstrom22:24
MaxVno, It just run a server with debug = true and compress false22:24
*** tanisdl has joined #openstack-meeting22:24
jomaraoh, you mean just django, but with uncompressed assets and debugging22:24
jomarait is the entire horizon app22:24
mrungewhy compress = False?22:24
david-lyledebugging22:25
david-lylejavascript22:25
MaxVrunserver-dev must be a better name22:25
*** galstrom is now known as galstrom_zzz22:25
mrungewell, that wouldn't test, what will be deployed in production22:25
mrungewouldn't catch issues with compressing22:25
david-lyleno, but when developing the JavaScript it's useful22:25
*** colinmcnamara has joined #openstack-meeting22:26
*** colinmcn_ has joined #openstack-meeting22:26
MaxVno test, my bad, it is a dev server22:26
mrungeah, ok22:26
david-lylegates and checkin verification would still run the way they do now22:26
MaxVyes22:26
*** galstrom_zzz is now known as galstrom22:26
MaxVit is just an entry in run_test.sh22:26
*** rakhmerov has joined #openstack-meeting22:26
david-lyleor a flag to --runserver22:26
jomara+50000 to that22:27
*** thomasem has quit IRC22:27
david-lyleI would like to take some time to look into Jasmine and the patches you've put up for review22:27
MaxVthe main discussion was about Jasmine22:27
MaxVsure22:27
david-lylethat said Jasmine sounds reasonable, I would just like to do my homework and let others check it out too22:28
david-lyleI'll add it as a topic for the next meeting so we can revisit it22:28
lsmoladavid-lyle, +122:29
david-lyleAny other questions for MaxV or re: Jasmine in general?22:29
*** ArxCruz has quit IRC22:29
jomarajust as a comment, i think it'll be very nice to have a testing framework people who know angular are familiar with (since we now have angular)22:29
david-lyle#topic Client side validation22:30
*** ArxCruz has joined #openstack-meeting22:30
*** openstack changes topic to "Client side validation (Meeting topic: Horizon)"22:30
david-lylelast meeting the issue of client side validation was brought up22:30
casanch1yes, that was a quick fix I made22:31
*** rakhmerov has quit IRC22:31
david-lylea patch https://bugs.launchpad.net/horizon/+bug/1125232 was proposed that used html522:31
uvirtbotLaunchpad bug 1125232 in horizon "Object Upload is validated after object upload" [Medium,In progress]22:31
david-lylethere was input that angular might provide a better solution once in22:31
casanch1it's pending approval https://review.openstack.org/#/c/57499/22:32
david-lylenow that it's in, is that the case?22:32
jomaraangular has nice inline form validation options22:32
jomarathey are very very simple22:32
david-lyleor should we accept this approach until the angular method is better laid out22:32
david-lyleit's a question of time, I suppose22:32
jomaradavid-lyle: is there a thread about this? i can write up an example if we're interested22:33
casanch1the fix is really simple, it's just needed to add one line of code in each form22:33
mrungehow long will it take for angular?22:33
*** salv-orlando has joined #openstack-meeting22:33
jomaradepends on how many forms you want to set up and how complex the validations are22:33
MaxVit seems easy22:33
jtomasekdavid-lyle: this html5 method is very unintrusive, so there is no issue with it for now22:33
*** denis_makogon has quit IRC22:34
jtomasekMaxV: jomara: good read: http://django-angular.readthedocs.org/en/latest/angular-form-validation.html22:34
jomaraoh cool, will check that out22:34
david-lyleit felt clean to me, I just knew there were concerns expressed22:34
*** lsmola has quit IRC22:35
mrungecasanch1, does your "fix" work with older browsers? Internet explorer?22:35
*** danwent has joined #openstack-meeting22:35
jtomasekmrunge: not really, client side validations should be backed up by server side validations still22:35
david-lyleIE 8 is as far back as we support22:35
jtomaseknot sure about this instance though22:36
casanch1it doesn't work on old versions of IE, IE10 for sure, that IE9 or 8, not sure22:36
casanch1I can check22:36
mrungejtomasek, point taken. let's make it directly right, no quick fixes22:36
devlapsjtomasek: +122:36
MaxVangular support IE8 and form validation is easy22:36
*** galstrom is now known as galstrom_zzz22:37
MaxVbut as mentionned jtomasek we have to check on server side too22:37
casanch1it is being checked on server side22:37
mrungeyes of course!22:37
casanch1that is already in22:37
casanch1this is for the missing client-side validation22:37
jtomasekcasanch1: then I think it is good enough22:38
jtomasekcasanch1: as discussed last time22:38
casanch1and again, I completely agree that angular is the best final solution, but this fix will prevent wasting resources while uploading large objects22:38
*** neelashah has joined #openstack-meeting22:38
*** lsmola has joined #openstack-meeting22:38
casanch1while we wait for angular...22:38
MaxVit is merged22:38
*** maxdml has quit IRC22:39
*** vuil has joined #openstack-meeting22:39
mrungeMaxV you mean angular is merged22:39
david-lyleok, casanch1 and MaxV can you two use that bug to collaborate on an angular based solution22:39
MaxVyes22:39
casanch1oh, didn't know that Angular was already merged to master22:39
mrungenot the qickhack casanch1 made22:39
*** epim has quit IRC22:39
casanch1ok, I can rework the fix to use angular22:40
david-lyleok, casanch1, thank you22:40
*** jmontemayor has quit IRC22:40
casanch1no problem22:40
lsmolaMaxV, would be nice to find a way how to generate client side validation from Django validations22:40
MaxVgood idea22:41
bdehamerYeah, the tricky part is making sure your server-side validations stay in sync with your client-side logic.22:41
david-lylea linked solution would be ideal22:41
kspear_jtomasek's link above talks about that22:42
*** pablosan has quit IRC22:42
david-lyle#topic Follow up on: Updates from I18N team22:43
*** openstack changes topic to "Follow up on: Updates from I18N team (Meeting topic: Horizon)"22:43
jtomaseklsmola: this is the right solution: http://django-angular.readthedocs.org/en/latest/angular-form-validation.html22:43
david-lyleI think there are just two remaining reviews that need to be merged on stable, although if the deadline is today, that seems unlikely22:44
lsmolajtomasek, excellent22:44
david-lylethanks jtomasek22:44
david-lyle#topic Open Discussion22:45
*** openstack changes topic to "Open Discussion (Meeting topic: Horizon)"22:45
jpichWe may be able to backport a translation patch to the milestone-proposed branch if it's proposed within the next couple of days22:45
david-lylejpich ok, that would work22:46
jpichbut I'm not sure what's the status on Transifex, if the latest strings have been updated or if the i18n has had a chance to translate yet22:46
jpichI'll check with amotoki tomorrow, he may be more up to date than I am22:46
david-lyleok thanks jpich22:47
jpichsure22:47
* david-lyle jumps topics a little too quickly22:47
jpich:-)22:47
david-lylealright, open season22:47
jcoufalone quick update22:48
jcoufalthere is updated navigation proposal22:48
jcoufalhttp://ask-openstackux.rhcloud.com/question/2/openstack-dashboard-navigation-redesign/?answer=99#post-id-9922:48
jcoufalso whoever is interested, feel free to give any feedback, everything is welcome22:49
*** casanch1 has quit IRC22:50
lsmolawill do22:50
*** krtaylor has joined #openstack-meeting22:50
jcoufalit's mostly reflecting summit discussions22:50
devlapsjcoufal: thanks for the info. definitely interested.22:50
david-lylejcoufal: thanks for putting that together.  I think there is more than one bp in there22:51
david-lylethe main navigation and header updates is one22:51
jcoufalyeah, BP are already there AFAIK22:52
david-lylebreadcrumbs would be another22:52
*** epim has joined #openstack-meeting22:52
jcoufaldavid-lyle: +122:52
*** lbragstad has quit IRC22:52
jcoufali think there was already one about breadcrumbs22:52
jcoufalbut it might be obsolete by this time (not sure)22:52
*** fifieldt_ has joined #openstack-meeting22:52
jpichBy the way, 2 of the 4 interns who will participate in the next OPW round will be doing work related to Horizon: Sayali will be working with lsmola on sparklines, and Anna will be working with me on the instance actions22:53
david-lyleok, I thought I read through -all- of them in the last week, but I may have missed one22:53
*** dkranz has quit IRC22:53
jpichThe internship starts on December 10, say hello if you see them around :)22:53
lsmolayaaay22:53
david-lylefantastic22:53
lsmolajpich, sayali has already started22:53
mrungeone quick update for django-1.622:54
mrungeI have a fix for horizon for revuew22:54
jcoufaldavid-lyle: it was pretty old one, maybe that's my mistake22:54
mrungethe larger issue is django_openstack_auth22:54
jpichlsmola: Cool!! Let her know about these meetings so she can join in and say hello, if it's at a reasonable time where she lives :)22:54
lsmolajpich, ok, will do22:55
david-lylemrunge, what's the issue?22:55
david-lylejcoufal: could be a ux bp22:55
mrungedavid-lyle, the review is here: https://review.openstack.org/#/c/58947/22:55
*** michchap has quit IRC22:56
mrungedavid-lyle, and the issue is: somethings in authenticate changed22:56
mrungelet me check for the bug I filed22:56
mrungehttps://bugs.launchpad.net/django-openstack-auth/+bug/125680522:56
uvirtbotLaunchpad bug 1256805 in django-openstack-auth "django-1.6: TypeError at /auth/login/" [Undecided,New]22:56
*** rongze has joined #openstack-meeting22:57
david-lyleyeah, openstack_auth seems to break every django roll22:57
mrungeonce authenticated, one can use horizon with 1.6 (with the proposed fix for horizon)22:58
mrungeso, the larger issue is openstack_auth22:58
mrungewhen we fixed that, we could start gating at 1.6 as well ;-)22:58
lsmolamrunge, great22:59
david-lylemrunge: great22:59
david-lyletimes almost up, any last items23:00
*** jdurgin has quit IRC23:00
*** markvan_ has joined #openstack-meeting23:01
david-lyleok, thanks everyone23:01
david-lyle#endmeeting23:01
*** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings"23:01
openstackMeeting ended Tue Dec  3 23:01:30 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:01
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-12-03-22.01.html23:01
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-12-03-22.01.txt23:01
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-12-03-22.01.log.html23:01
jpichThanks23:01
mrungethanks david-lyle !23:01
*** jpich has quit IRC23:01
lsmolathanks everybody, have a great night23:01
jcoufal\o23:01
jcoufalthanks23:02
*** eharney has quit IRC23:02
*** michchap has joined #openstack-meeting23:02
mrungeyeah, good night23:02
jomaralater everyone23:02
*** mrunge has quit IRC23:02
*** rongze has quit IRC23:02
jtomasekthanks23:02
*** jcoufal has quit IRC23:02
*** nermina has joined #openstack-meeting23:02
*** matty_dubs has left #openstack-meeting23:04
*** devlaps has quit IRC23:05
*** fifieldt_ has quit IRC23:05
*** burt has quit IRC23:06
*** ivasev has quit IRC23:06
*** lsmola has quit IRC23:07
*** sarob has quit IRC23:07
*** fifieldt_ has joined #openstack-meeting23:07
*** jtomasek has quit IRC23:07
*** sarob has joined #openstack-meeting23:07
*** bdehamer has quit IRC23:08
*** joesavak has quit IRC23:10
*** mrodden has joined #openstack-meeting23:10
*** kspear_ has quit IRC23:10
*** noslzzp has quit IRC23:11
*** sarob has quit IRC23:11
*** jecarey has quit IRC23:13
*** sacharya has quit IRC23:13
*** jdurgin has joined #openstack-meeting23:13
*** markvan has quit IRC23:14
*** jcooley_ has quit IRC23:18
*** MaxV has quit IRC23:18
*** ttrifonov is now known as ttrifonov_zZzz23:20
*** esker has quit IRC23:24
*** dolphm has quit IRC23:25
*** SergeyLukjanov has quit IRC23:26
*** cdub has quit IRC23:26
*** markpeek has quit IRC23:26
*** markpeek has joined #openstack-meeting23:27
*** rakhmerov has joined #openstack-meeting23:27
*** nati_uen_ has joined #openstack-meeting23:28
*** nati_uen_ has quit IRC23:29
*** nati_uen_ has joined #openstack-meeting23:30
*** egallen has quit IRC23:30
*** nati_ueno has quit IRC23:30
*** vijendar has quit IRC23:32
*** dolphm has joined #openstack-meeting23:32
*** xuhaiwei has joined #openstack-meeting23:32
*** lcheng has quit IRC23:33
*** banix has quit IRC23:33
*** neelashah has quit IRC23:34
*** yamahata_ has quit IRC23:34
*** xuhaiwei has quit IRC23:36
*** mrodden has quit IRC23:38
*** sgordon has joined #openstack-meeting23:39
*** yfujioka has joined #openstack-meeting23:43
*** rnirmal has quit IRC23:45
*** jtomasek has joined #openstack-meeting23:45
*** sarob has joined #openstack-meeting23:46
*** dolphm has quit IRC23:47
*** atiwari has quit IRC23:49
*** hemna has quit IRC23:50
*** lbragstad has joined #openstack-meeting23:50
*** tanisdl_ has joined #openstack-meeting23:51
*** loq_mac has joined #openstack-meeting23:52
*** jtomasek has quit IRC23:52
*** tanisdl has quit IRC23:52
*** tanisdl_ is now known as tanisdl23:52
*** fnaval has quit IRC23:53
*** hemna has joined #openstack-meeting23:54
*** kui has quit IRC23:56
*** mrodden has joined #openstack-meeting23:57
*** cdub has joined #openstack-meeting23:58
*** rongze has joined #openstack-meeting23:59
*** rakhmerov has quit IRC23:59

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