Tuesday, 2013-06-11

*** danwent has quit IRC00:01
*** matiu has joined #openstack-meeting00:01
*** matiu has joined #openstack-meeting00:01
*** noslzzp has quit IRC00:01
*** gyee has quit IRC00:03
*** noslzzp has joined #openstack-meeting00:03
*** ryanpetrello has quit IRC00:05
*** stevemar has quit IRC00:11
*** diogogmt has quit IRC00:18
*** reed has quit IRC00:22
*** virajh has quit IRC00:23
*** epim has quit IRC00:24
*** epim_ has joined #openstack-meeting00:24
*** roampune has quit IRC00:25
*** tanisdl has quit IRC00:25
*** colinmcnamara has quit IRC00:25
*** danwent has joined #openstack-meeting00:29
*** fnaval has joined #openstack-meeting00:30
*** changbl has joined #openstack-meeting00:38
*** jecarey has quit IRC00:45
*** jecarey has joined #openstack-meeting00:46
*** stevemar has joined #openstack-meeting00:47
*** seanrob has quit IRC00:52
*** jecarey has quit IRC00:58
*** ryanpetrello has joined #openstack-meeting01:05
*** jlucci has joined #openstack-meeting01:09
*** terryg__ has quit IRC01:10
*** jlucci has quit IRC01:14
*** novas0x2a|laptop has quit IRC01:19
*** danwent has quit IRC01:20
*** epim_ has quit IRC01:27
*** mrodden has joined #openstack-meeting01:29
*** Mandell has quit IRC01:29
*** jecarey has joined #openstack-meeting01:30
*** kebray has joined #openstack-meeting01:33
*** ryanpetrello has quit IRC01:34
*** krtaylor has joined #openstack-meeting01:35
*** otherwiseguy has joined #openstack-meeting01:35
*** rongze has joined #openstack-meeting01:36
*** ivasev has joined #openstack-meeting01:37
*** nati_ueno has quit IRC01:40
*** maoy has joined #openstack-meeting01:42
*** kebray has quit IRC01:46
*** ogelbukh1 has quit IRC01:54
*** maoy has quit IRC01:54
*** novas0x2a|laptop has joined #openstack-meeting01:56
*** haomaiwang has joined #openstack-meeting02:00
*** HenryG has quit IRC02:04
*** seanrob has joined #openstack-meeting02:09
*** seanrob has quit IRC02:09
*** seanrob has joined #openstack-meeting02:09
*** jecarey has quit IRC02:11
*** seanrob has quit IRC02:12
*** seanrob has joined #openstack-meeting02:12
*** nati_ueno has joined #openstack-meeting02:16
*** nati_ueno has quit IRC02:18
*** emagana has quit IRC02:18
*** armax has joined #openstack-meeting02:20
*** ayoung has quit IRC02:26
*** seanrob has quit IRC02:35
*** seanrob has joined #openstack-meeting02:35
*** cp16net is now known as cp16net|away02:40
*** cp16net|away is now known as cp16net02:40
*** MarkAtwood has quit IRC02:45
*** otherwiseguy has quit IRC02:48
*** noslzzp has quit IRC02:48
*** markvoelker has quit IRC02:48
*** otherwiseguy has joined #openstack-meeting02:50
*** markvoelker has joined #openstack-meeting02:55
*** Banix has quit IRC02:57
*** dcramer_ has quit IRC03:01
*** ayoung has joined #openstack-meeting03:02
*** seanrob has quit IRC03:05
*** Mandell has joined #openstack-meeting03:11
*** armax has quit IRC03:14
*** boris-42 has joined #openstack-meeting03:21
*** dcramer_ has joined #openstack-meeting03:23
*** russellb has quit IRC03:26
*** russellb has joined #openstack-meeting03:31
*** marun has joined #openstack-meeting03:40
*** dcramer_ has quit IRC03:44
*** SergeyLukjanov has joined #openstack-meeting03:47
*** neelashah has joined #openstack-meeting03:51
*** koolhead17 has joined #openstack-meeting03:51
*** koolhead17 has joined #openstack-meeting03:51
*** ogelbukh1 has joined #openstack-meeting03:52
*** dcramer_ has joined #openstack-meeting03:57
*** sdake_ has joined #openstack-meeting03:57
*** otherwiseguy has quit IRC04:06
*** dripton_ has joined #openstack-meeting04:06
*** danwent has joined #openstack-meeting04:10
*** dripton has quit IRC04:10
*** dcramer_ has quit IRC04:12
*** carl_baldwin has joined #openstack-meeting04:13
*** zehicle has joined #openstack-meeting04:17
*** nati_ueno has joined #openstack-meeting04:17
*** rostam has quit IRC04:20
*** lloydde has joined #openstack-meeting04:21
*** rostam has joined #openstack-meeting04:23
*** adalbas has quit IRC04:27
*** lpabon has quit IRC04:30
*** nati_ueno has quit IRC04:31
*** vipul is now known as vipul|away04:32
*** jhenner has quit IRC04:33
*** SergeyLukjanov has quit IRC04:43
*** danwent has quit IRC04:56
*** stevemar has quit IRC04:58
*** carl_baldwin has quit IRC05:03
*** martine_ has quit IRC05:03
*** ayurchen has joined #openstack-meeting05:12
*** koolhead17 has quit IRC05:17
*** mdomsch has joined #openstack-meeting05:18
*** matiu has quit IRC05:19
*** JimJiang has joined #openstack-meeting05:21
*** neelashah has quit IRC05:30
*** thomas has joined #openstack-meeting05:31
*** thomas is now known as Guest1006705:31
*** Guest10067 has left #openstack-meeting05:32
*** armax has joined #openstack-meeting05:40
*** mrunge has joined #openstack-meeting05:41
*** alican has joined #openstack-meeting05:53
*** lloydde has quit IRC05:59
*** lloydde has joined #openstack-meeting05:59
*** ryanpetrello has joined #openstack-meeting06:04
*** lloydde has quit IRC06:04
*** lukego has joined #openstack-meeting06:05
*** Mandell has quit IRC06:06
*** lukego_ has joined #openstack-meeting06:15
*** lukego has quit IRC06:16
*** lukego_ is now known as lukego06:16
*** alican has quit IRC06:17
*** adalbas has joined #openstack-meeting06:22
*** jcoufal has joined #openstack-meeting06:22
*** SergeyLukjanov has joined #openstack-meeting06:24
*** lloydde has joined #openstack-meeting06:29
*** lloydde has quit IRC06:34
*** belmoreira has joined #openstack-meeting06:40
*** hartsocks has joined #openstack-meeting06:40
*** ryanpetrello has quit IRC06:41
*** thomas has joined #openstack-meeting06:42
*** thomas is now known as Guest6703306:42
*** hemna has quit IRC06:44
*** mrunge has quit IRC06:45
*** Mandell has joined #openstack-meeting06:46
*** Guest67033 has left #openstack-meeting06:47
*** mrunge has joined #openstack-meeting06:49
*** xBsd has joined #openstack-meeting06:54
*** hemna has joined #openstack-meeting06:56
*** tayyab has joined #openstack-meeting06:58
*** harlowja has quit IRC07:06
*** jtomasek has joined #openstack-meeting07:06
*** lukego has quit IRC07:06
*** lukego has joined #openstack-meeting07:12
*** whenry has quit IRC07:12
*** shang has joined #openstack-meeting07:14
*** koolhead17 has joined #openstack-meeting07:18
*** flaper87 has joined #openstack-meeting07:19
*** ndipanov has quit IRC07:23
*** ndipanov has joined #openstack-meeting07:24
*** armax has quit IRC07:25
*** MarkAtwood has joined #openstack-meeting07:26
*** lloydde has joined #openstack-meeting07:30
*** afazekas_ has joined #openstack-meeting07:30
*** Mandell has quit IRC07:31
*** ivasev has quit IRC07:34
*** lloydde has quit IRC07:34
*** jhenner has joined #openstack-meeting07:38
*** sushils has joined #openstack-meeting07:40
*** sushils has quit IRC07:41
*** boris-42 has quit IRC07:42
*** sushils has joined #openstack-meeting07:43
*** michchap has quit IRC07:44
*** michchap has joined #openstack-meeting07:45
*** xBsd has quit IRC07:45
*** salv-orlando has joined #openstack-meeting07:49
*** briancline has quit IRC08:00
*** briancline has joined #openstack-meeting08:00
*** Mandell has joined #openstack-meeting08:01
*** lukego has quit IRC08:01
*** lukego has joined #openstack-meeting08:02
*** salv-orlando has quit IRC08:05
*** tayyab has quit IRC08:06
*** tayyab_ has joined #openstack-meeting08:07
*** MarkAtwood has quit IRC08:16
*** afazekas has quit IRC08:16
*** Mandell has quit IRC08:17
*** derekh has joined #openstack-meeting08:17
*** Mandell has joined #openstack-meeting08:18
*** johnthetubaguy has joined #openstack-meeting08:27
*** matiu has joined #openstack-meeting08:29
*** matiu has quit IRC08:29
*** matiu has joined #openstack-meeting08:29
*** mkollaro has joined #openstack-meeting08:30
*** afazekas has joined #openstack-meeting08:30
*** lloydde has joined #openstack-meeting08:30
*** alexpilotti has joined #openstack-meeting08:32
*** lloydde has quit IRC08:35
*** boris-42 has joined #openstack-meeting08:46
*** garyk has joined #openstack-meeting08:46
*** boris-42 has joined #openstack-meeting08:46
*** psedlak has joined #openstack-meeting08:52
*** tayyab_ has quit IRC09:01
*** jlucci has joined #openstack-meeting09:11
*** jlucci has quit IRC09:14
*** tayyab has joined #openstack-meeting09:19
*** timello has quit IRC09:23
*** timello has joined #openstack-meeting09:24
*** ogelbukh1 is now known as ogelbukh09:26
*** lloydde has joined #openstack-meeting09:31
*** lloydde has quit IRC09:36
*** Mandell has quit IRC09:42
*** ilyashakhat_ has joined #openstack-meeting09:51
*** ilyashakhat has quit IRC09:52
*** salv-orlando has joined #openstack-meeting09:59
*** rods has joined #openstack-meeting10:09
*** mdenny has quit IRC10:21
*** lloydde has joined #openstack-meeting10:32
*** lloydde has quit IRC10:36
*** Vivek has joined #openstack-meeting10:56
*** derekh has quit IRC11:03
*** belmoreira has quit IRC11:07
*** derekh has joined #openstack-meeting11:08
*** marun has quit IRC11:20
*** tedross has joined #openstack-meeting11:26
*** lbragstad has quit IRC11:26
*** krtaylor has quit IRC11:28
*** lbragstad has joined #openstack-meeting11:28
*** pcm__ has joined #openstack-meeting11:31
*** lloydde has joined #openstack-meeting11:32
*** johnthetubaguy has quit IRC11:34
*** dhellmann-away has quit IRC11:34
*** krtaylor has joined #openstack-meeting11:34
*** HenryG has joined #openstack-meeting11:35
*** marun has joined #openstack-meeting11:36
*** lloydde has quit IRC11:37
*** johnthetubaguy has joined #openstack-meeting11:38
*** belmoreira has joined #openstack-meeting11:38
*** dhellmann has joined #openstack-meeting11:39
*** lbragstad has quit IRC11:39
*** fifieldt has joined #openstack-meeting11:42
*** belmoreira has quit IRC11:47
*** derekh has quit IRC11:53
*** derekh has joined #openstack-meeting11:54
*** SergeyLukjanov has quit IRC11:56
*** SergeyLukjanov has joined #openstack-meeting11:59
*** SergeyLukjanov has quit IRC11:59
*** dprince has joined #openstack-meeting11:59
*** beagles has joined #openstack-meeting12:00
*** sandywalsh has quit IRC12:01
*** mrunge has quit IRC12:03
*** belmoreira has joined #openstack-meeting12:05
*** novas0x2a|laptop has quit IRC12:05
*** sgordon has joined #openstack-meeting12:10
*** egallen has joined #openstack-meeting12:13
*** martine_ has joined #openstack-meeting12:14
*** sandywalsh has joined #openstack-meeting12:14
*** zyluo has joined #openstack-meeting12:15
*** [1]NickChase has joined #openstack-meeting12:21
*** lbragstad has joined #openstack-meeting12:29
*** SergeyLukjanov has joined #openstack-meeting12:32
*** lloydde has joined #openstack-meeting12:33
*** marun has quit IRC12:36
*** lloydde has quit IRC12:37
*** shengjie has joined #openstack-meeting12:41
*** rickerc has joined #openstack-meeting12:49
*** matiu has quit IRC12:49
*** marcosmamorim has joined #openstack-meeting12:53
*** michchap has quit IRC12:53
*** michchap_ has joined #openstack-meeting12:53
*** jasondotstar has joined #openstack-meeting12:54
annegentlealmost time for Doc team meeting12:57
*** writerDi_ has joined #openstack-meeting12:57
*** marun has joined #openstack-meeting12:58
fifieldtyay!12:58
*** writerDi_ is now known as writerDiane_12:59
*** fifieldt_ has joined #openstack-meeting12:59
*** sld has joined #openstack-meeting12:59
[1]NickChaseGood morning, all.13:00
writerDiane_Hello!13:00
fifieldt_Good morning [1]NickChase13:00
*** [1]NickChase is now known as NickChase13:00
NickChaseNot sure what THAT was about. :)13:00
*** t4nk778 has joined #openstack-meeting13:01
annegentlemorning!13:01
annegentleall set?13:01
*** jpich has joined #openstack-meeting13:01
annegentle#startmeeting Doc/Web team13:01
ladquingood morning / evening / afternoon, folks13:01
openstackMeeting started Tue Jun 11 13:01:37 2013 UTC.  The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot.13:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:01
*** openstack changes topic to " (Meeting topic: Doc/Web team)"13:01
openstackThe meeting name has been set to 'doc_web_team'13:01
annegentleAgenda can be found at https://wiki.openstack.org/wiki/Meetings/DocTeamMeeting#Agenda_for_next_meeting13:02
*** lukego has quit IRC13:02
annegentle#topic Action items from the last meeting13:02
*** openstack changes topic to "Action items from the last meeting (Meeting topic: Doc/Web team)"13:02
annegentleer maybe I should ask who all is here?13:02
annegentlethen again maybe I see all I need to :)13:02
sgordon>.>13:02
annegentle:)13:02
t4nk778:>13:02
annegentle1. annegentle ask about DocImpact automation. Done, sld started a patch to automate13:03
annegentle#link https://review.openstack.org/#/c/30718/ original patch13:03
fifieldt_NickChase, writerDiane_, annegentle, koolhead17, sld, EmilienM (no lorinh or razique)13:03
annegentlealso fifieldt_ picked up the work while sld was on vaction13:03
koolhead17hi all13:03
*** dkehn has quit IRC13:03
annegentleat least that's what I got from reading through the links13:03
annegentle#link https://review.openstack.org/#/c/32348/ new patch while sld went on vacay13:03
t4nk778can someone help me with the nova live migration feature ?13:04
annegentlelooks like there are more TODOs to try to make it expandable for other impact flags, but we need to stop drowning in DocImpact emails.13:04
* ladquin here13:04
fifieldt_not in this channel t4nk778, we're having a meeting :) try #openstack13:04
t4nk778ah ok ^^13:04
annegentlefifieldt_: do you have any more details about DocImpact automation?13:04
annegentlet4nk778: yeah we can try to help elsewhere though!13:04
*** changbl has quit IRC13:04
fifieldt_well, Steven did all the hard work13:05
*** t4nk778 has left #openstack-meeting13:05
fifieldt_effectively making code that creates bugs in launchpad similar to what I'm doing now13:05
annegentlefifieldt_: sweet13:05
sldI do, sortof... by 'borrowing' some other code and then changing that, and generalizing it... ;)13:05
fifieldt_then extended that so that it only makes one bug per DocImpact13:05
annegentlesld: hehe isn't that the way it goes13:05
fifieldt_the bugs will still need some triaging after being created13:05
fifieldt_but it removes a silly manual process13:05
annegentlefifieldt_: that sounds really more reasonable though13:06
*** dkehn has joined #openstack-meeting13:06
fifieldt_then there are extensions we can add13:06
fifieldt_eg13:06
fifieldt_1) alter the text on bug update13:06
fifieldt_2) close bugs associated with abandoned patch sets13:06
fifieldt_3) mark patch-merged bugs as 'confirmed'13:06
fifieldt_in the future13:06
annegentleFreakin' nifty13:06
annegentleesp. the close doc bugs when a patch gets abandoned13:06
annegentleok there was one more action item13:06
annegentle2. annegentle and sld meet to talk about install docs13:07
annegentleMet, talked about install docs, docimpact, config automation. Probably about rain too since we are in Texas. :)13:07
annegentleThat was sld's action item too. Done and done.13:07
*** belmoreira1 has joined #openstack-meeting13:08
annegentleOh and I forgot to mention, fifieldt_ is going to take over the meeting later when I have to leave early... we sorted the agenda13:08
annegentleok next topic13:08
annegentle#topic Shaun McCance starting June 20, contractor for Cisco13:08
*** openstack changes topic to "Shaun McCance starting June 20, contractor for Cisco (Meeting topic: Doc/Web team)"13:08
annegentleIt took a pile of paperwork but Shaun's hired. Woo.13:08
fifieldt_congratulations13:08
NickChaseCongrats13:08
annegentleHe's running the Open Help Conference June 15-19.13:08
annegentle#link http://openhelpconference.com/13:08
annegentleHe'll be working on sorting through install guides to create explanatins for multiple architectures.13:09
* annegentle can't spell13:09
sldisn't that a requirement for someone working with docs? :)13:09
annegentleThe contract is 3 months if I recall correctly.13:09
annegentlesld: pretty much!13:09
annegentleI think we can all help Shaun get onboard13:10
*** belmoreira has quit IRC13:10
fifieldt_indeed13:10
fifieldt_have to make the most of the time13:10
NickChaseDefinitely13:10
annegentleOh and I made a blueprint for that install sorting.13:10
annegentle#topic Install guides blueprint - https://wiki.openstack.org/wiki/Install-with-multiple-architectures13:10
*** openstack changes topic to "Install guides blueprint - https://wiki.openstack.org/wiki/Install-with-multiple-architectures (Meeting topic: Doc/Web team)"13:10
annegentle#link https://wiki.openstack.org/wiki/Install-with-multiple-architectures13:10
*** belmoreira1 has quit IRC13:11
*** belmoreira has joined #openstack-meeting13:11
annegentleHoenstly part of the work is to figure out if that's the right approach (example architecture) but that sounded like what we decided at the Summit. Any discussion, questions?13:11
writerDiane_I still think we could consolidate into one install guide13:11
annegentleMy only hesitation for a single install guide is that "everyone" wants a "simple test" one.13:11
sgordonyeah13:12
annegentleoh and my other hesitation is, the distros that have their own install guides, how do we differentiate ours as the "official" one?13:12
sgordonproblem is they also want expandable :)13:12
annegentlesgordon: yeah13:12
writerDiane_okay - that sounds reasonable - but they could share some common files and be made more consistent13:12
annegentleSo some of Shaun's work will be that analysis.13:12
writerDiane_in organization and style13:12
*** haomaiwang has quit IRC13:12
annegentlewriterDiane_: for sure13:12
fifieldt_cool13:12
NickChaseAs the "official" one we're talking about the bare bones, no external tools version.13:13
annegentlewriterDiane_: that would greatly improve the install experience from docs.o.o13:13
writerDiane_okay!13:13
*** Tross has quit IRC13:13
annegentleNickChase: right, can be core and integrated, but no more13:13
*** spzala has joined #openstack-meeting13:13
annegentleNickChase: or we decide core only to lessen scope13:13
sgordoni would +1 core only13:13
annegentlesgordon: yeah might be the best to stick to core only, good input13:14
sgordonfrom my pov as an employee of a vendor we are happy to maintain a doc for our specific deployment method13:14
annegentlethen we just coach the integrated on how to document their install processes13:14
fifieldt_I would instead go "best practice"/"usual practice" :)13:14
sgordonbut would like to collaborate on 'manual' deployment13:14
sgordonof the core13:14
annegentleinstall/config13:14
writerDiane_i think the horizon info can definitely move into the new user guide13:14
writerDiane_or at least be shared13:15
NickChaseI think it'd be good to start with core only, but ultimately there should be "official" doc on how to install all "official" software.13:15
annegentlesgordon: cool, Shaun is used to working in open source collaborations so I think he'll be very open to help13:15
NickChaseDiane:  I agree.13:15
sgordonyes, will be meeting him for the first time on the weekend :)13:15
annegentlewriterDiane_: Horizon install/conig?13:15
annegentleconfig13:15
annegentlesgordon: aw cool! I so wish I could go but my son's camp dates prevented it...13:15
annegentleI nearly bought a ticket last week in fact :)13:15
annegentlefifieldt_: do you think we'll have some data for "usual" in the next few weeks from the user committee?13:16
annegentlefifieldt_: it would be great to apply some of that knowledge (what lots of deployers are doing)13:16
annegentlefifieldt_: or, are you familiar enough to tell Shaun what's best practice/usual?13:17
fifieldt_that data will be months, rather than weeks13:17
annegentlefifieldt_: ah ok13:17
annegentleok any more on install guide?13:17
fifieldt_I'm just thinking of the approach from the ops guide13:17
annegentlefifieldt_: yeah good one13:17
fifieldt_which was opinionated13:17
annegentlearen't they all :)13:17
annegentle#topic User Guide - https://wiki.openstack.org/wiki/Blueprint-os-user-docs13:17
*** openstack changes topic to "User Guide - https://wiki.openstack.org/wiki/Blueprint-os-user-docs (Meeting topic: Doc/Web team)"13:17
fifieldt_mm.13:18
annegentlewriterDiane_ has been going great gangbusters on the user guide13:18
annegentlewriterDiane_: you want to talk about it? your findings re: sharing and user v admin user?13:18
writerDiane_yes13:18
writerDiane_i think it's possible to share, but the user guide I'm creating is going to be larger than the SUSE one - but I think that parts of it can use conditional tags13:19
writerDiane_and be shared13:19
writerDiane_but we can figure that out later -13:19
annegentleOy! And I have to go now, fifieldt_ you have the ocn.13:19
annegentleer, con13:19
fifieldt_ok13:19
fifieldt_ta13:19
NickChaseBye, Anne13:19
writerDiane_bye anne13:19
annegentlebye, thanks writerDiane_!13:19
fifieldt_sounds impressive writerDiane_13:19
writerDiane_tom, i also think we'll need an admin users guide13:20
fifieldt_ok, two separate guides? cool13:20
NickChaseI was about to say that I was looking into splitting them out13:20
writerDiane_that's what I'm thinking13:20
fifieldt_cool, nice13:20
writerDiane_both would have same format, but the admin guide would focus on admin-only tasks13:20
NickChaseand I am thinking that maybe you and I can get together to make sure nothing slips through the cracks?13:20
*** johnthetubaguy has quit IRC13:20
writerDiane_sure nick13:21
NickChasegreat, we'll schedule offline?13:21
writerDiane_yes - i've written a similar guide for cloud servers at rackspace -13:21
writerDiane_yes, schedule offline13:21
fifieldt_brilliant work guys13:21
fifieldt_shall we move on then? or is anything else bothering you about the user guide?13:21
*** garyk has quit IRC13:21
*** markmcclain has joined #openstack-meeting13:22
writerDiane_move on13:22
fifieldt_ok!13:22
fifieldt_#topic  Auto-generated configuration reference tables for milestone13:22
fifieldt_so, you've probably seen the patches floating about13:22
fifieldt_generated by Steven & I's code13:22
*** markmcclain has quit IRC13:22
sld...not sure when we'll have that done, but you know the progress. :)13:22
fifieldt_that runs through every python file in an openstack product and extracts options and their help text13:22
fifieldt_recent patches to go in include13:22
*** markmcclain has joined #openstack-meeting13:22
fifieldt_https://review.openstack.org/#/c/28904/13:23
*** johnthetubaguy has joined #openstack-meeting13:23
fifieldt_which went through and added config reference tables in the compute admin guide13:23
*** garyk has joined #openstack-meeting13:23
fifieldt_if you're looking for something that might be an example of this fabled 'config reference'13:23
*** davidkranz has joined #openstack-meeting13:23
fifieldt_check out the RPC section in that13:23
fifieldt_and how it includes rabbit, qpid etc13:23
fifieldt_we also have quantum (https://review.openstack.org/#/c/28905/) and glance(https://review.openstack.org/#/c/28903/)13:23
fifieldt_the key problem right now13:24
fifieldt_is that the config tables don't track which file to configure the options in13:24
*** michchap has joined #openstack-meeting13:24
fifieldt_as raised in the quantum review and glancve13:24
fifieldt_so that'll be the next step, capturing that13:24
fifieldt_Steven was also working on some code today which might be more robust than what we're currently doing13:24
fifieldt_ok, end of rant13:24
fifieldt_any queries?13:24
sldnope. :)13:25
fifieldt_writerDiane_, NickChase is this whole automated config table thing making sense?13:25
writerDiane_yes!13:25
NickChaseYes.  I'm thinking...13:25
*** ttrifonov is now known as ttrifonov_zZzz13:25
fifieldt_a dangerous activity13:25
NickChase:)13:25
NickChase... that it shouldn't be too much to include an ID in the docs and the code to match them up13:26
fifieldt_perhaps we should discuss offline - thought through many things on making this work :)13:26
NickChasesounds good13:26
fifieldt_cool, I'll hit you on skype13:26
NickChasegreat13:26
*** gakott has joined #openstack-meeting13:26
fifieldt_ok, if there's nothing else .... ?13:27
NickChasenot on this13:27
fifieldt_#topic  Bug report, DocImpact state13:27
*** neelashah has joined #openstack-meeting13:27
fifieldt_so, I think we covered this just before in the action items13:27
fifieldt_sld, any comments?13:27
*** markmcclain has quit IRC13:27
sldnope13:28
sldi think?13:28
sldyou know all i know. heh..13:28
fifieldt_cool, is everyone else comfortable with what's going on with the DocImpact-becomes-bug process>?13:28
*** krtaylor has quit IRC13:29
NickChaseI am13:29
writerDiane_yes13:29
fifieldt_brilliant, ta13:29
*** skort has joined #openstack-meeting13:29
fifieldt_in that case, we're on to ...13:29
fifieldt_#topic  Open discussion13:29
fifieldt_anything you want to talk about?13:29
NickChaseOK, well, briefly, I got with Emilien and we're going to expand the HA guide.13:30
fifieldt_oh, great!13:30
*** garyk has quit IRC13:30
NickChasewe decided to keep what is there and add the new content to it13:30
fifieldt_did you sort out the active-active vs active-passtive thing?13:30
EmilienMo/13:30
fifieldt_it's alive13:30
NickChaseyes, we're going to do an intro that starts with the general concepts13:30
NickChaseHey there. :)13:30
EmilienMhttps://etherpad.openstack.org/HA-Active-Active13:30
fifieldt_#link https://etherpad.openstack.org/HA-Active-Active13:31
fifieldt_#info https://etherpad.openstack.org/HA-Active-Active13:31
fifieldt_hmm, I was sure one of those fed the meet bot :)13:31
NickChaseAnd we have an Etherpad. :)13:31
fifieldt_looks good13:31
NickChaseAnyway, the idea (as I understood it) was to start with concepts, then discuss them as potential ways to do it.13:32
fifieldt_a sound plan13:32
EmilienMand share use cases13:32
NickChaseWhat we want is to provide a way to do it "out of the box" without stifling innovation on the topic.13:32
NickChaseright13:32
fifieldt_(minor administrative note: do you want to create a blueprint on launchpad as well - it can link to the etherpad - just to give others visibility on the work that's going on?)13:32
EmilienMit seems Mirantis & eNovance are doing HA on the same way for almost all OpenStack components13:33
*** gakott has quit IRC13:33
fifieldt_how convenient :)13:33
EmilienMfifieldt: sounds good ! let's for a blueprint13:33
EmilienMlet's go*13:33
NickChaseYes, good idea.  Emilien, you or me?13:33
EmilienMI can write it13:33
fifieldt_#action EmilienM create a blueprint on openstack-manuals to link to https://etherpad.openstack.org/HA-Active-Active13:33
*** lloydde has joined #openstack-meeting13:33
*** michchap has quit IRC13:33
NickChasegreat, thanks13:34
fifieldt_cool13:34
fifieldt_on random thing I should note is - has everyone seen the bootcamp the infrastructure team is having?13:34
NickChaseno13:34
*** litong has joined #openstack-meeting13:34
writerDiane_i heard about it13:35
fifieldt_there's some posts on the openstack-infra mailing list explaining it recently13:35
fifieldt_essentially they are looking for long term sustained contributors (please don't abandon us for infra :D)13:35
fifieldt_and having a meeting to bring people up to speed to be useful in this way13:35
fifieldt_I think sld was considering joining13:35
fifieldt_after his recent work into that side of things13:35
fifieldt_but anyway, check out the infra mailing list archives if it interests you13:36
fifieldt_we could also consider doing such a boot camp for docs13:36
*** timello_ has joined #openstack-meeting13:36
sldhehe13:36
fifieldt_thoughts on that?13:36
NickChaseI'd be all for a docs boot camp13:36
writerDiane_yes, a boot camp for docs would be good13:36
fifieldt_what would the scope be?13:36
fifieldt_& purpose13:36
writerDiane_doc tools, common practices for contributing13:37
NickChasethe actual process of contributing is a bit confusing13:37
writerDiane_best practices - writing style, spellcheck,13:37
writerDiane_i agree -13:37
writerDiane_people are intimidated13:37
NickChaseactually13:37
NickChaseunofficially, we are in the process of writing up a document on it13:37
writerDiane_we?13:37
*** afazekas_ has quit IRC13:37
*** lloydde has quit IRC13:38
NickChaseI've got a guy here, Tyler.13:38
NickChaseI put him on it.13:38
NickChaseThe doc he produced isn't ready for prime time yet13:38
fifieldt_on contributing, that is?13:38
NickChasebut ultimately it could serve as a good foundation for a boot camp13:38
NickChaseyes13:38
fifieldt_sounds cool13:38
NickChasebut it does need work13:38
fifieldt_no dramas13:39
*** skort has quit IRC13:39
*** timello has quit IRC13:39
fifieldt_my feeling is that we need to "get our house in order" before we can ramp up contributors in a big way13:39
NickChasethank you.13:39
fifieldt_and by that I mean the restructure13:39
*** skort has joined #openstack-meeting13:39
writerDiane_rackspace recently created a course for docbook - we could borrow from that13:39
NickChasenice13:39
fifieldt_ok, everyone has awesome ideas13:39
*** adalbas has quit IRC13:39
fifieldt_let's start an etherpad on planning this13:39
fifieldt_and eventually turn it into a proposal13:40
*** ryanpetrello has joined #openstack-meeting13:40
fifieldt_we might be able to get fundingz13:40
EmilienM#link https://blueprints.launchpad.net/openstack-manuals/+spec/improve-high-availability-support13:40
fifieldt_love your work EmilienM13:40
EmilienM;)13:40
NickChasethanks, Emilien :)13:40
fifieldt_#link fifieldt to create an etherpad for potential doc boot camp and communicate link13:40
*** ttrifonov_zZzz is now known as ttrifonov13:40
fifieldt_#link https://etherpad.openstack.org/DocsBootCamp201313:41
*** vijendar has joined #openstack-meeting13:41
fifieldt_ok - any other general doc discussion?13:41
fifieldt_we have 19 minutes of meeting time left that we could give back to our lives :)13:41
NickChase+1 on that. :)13:42
writerDiane_+113:42
*** jecarey has joined #openstack-meeting13:42
fifieldt_oh damn, why didn't you use +2 s :)13:42
EmilienMI have one question13:42
*** rnirmal has joined #openstack-meeting13:42
fifieldt_yes EmilienM13:42
EmilienMfor the HA doc, is it a good idea to work with Google Doc first, to collaborate with the community ?13:43
EmilienMfirst with NickChase13:43
EmilienMbut maybe other people would like to see our work13:43
EmilienMbefore patching the doc13:43
NickChaseI'm for that.13:43
sgordonthat would be great in my opinion13:43
fifieldt_for the rapid development stage, whatever works13:43
* sgordon is having a lot of difficulty working out where to fit in with a lot of things happening offline13:44
fifieldt_oh, how can we fix that sgordon13:44
EmilienMok, NickChase : I start a google doc13:44
sgordonfifieldt, EmilenM's suggestion seems reasonable13:44
sgordonstill have rapid development just have it in the open13:44
fifieldt_ya13:44
fifieldt_'course13:45
NickChaseEmilien:  thx13:45
sgordontooling doesnt really phase me13:45
sgordongoogle docs seems fine :)13:45
fifieldt_some would argue that vehemently :)13:45
*** johnthetubaguy has quit IRC13:45
fifieldt_tehehe13:45
sgordonhey if the NSA want to contribute...13:45
sgordon;p13:45
*** johnthetubaguy has joined #openstack-meeting13:45
fifieldt_:D13:45
fifieldt_but yeah, all of the other work like the new docs is already in the gerrit system13:45
writerDiane_I have no problem with google-docs, but then there is the conversion from the google-docs to docbook, which I've done for quantum and it's a pain in the neck13:46
writerDiane_not easy13:46
NickChaseWell, it will be when it's ready for review13:46
writerDiane_especially with tables13:46
NickChaseIt is a pain, true13:46
fifieldt_indeed13:46
NickChasebut I volunteer13:46
fifieldt_yay!13:46
NickChasedone it before, I can do it again. :)13:46
writerDiane_alternatively, you can generate PDF for a doc patch and have people review that13:46
fifieldt_#action NickChase to convert google docs to docbook, when the time comes13:46
writerDiane_wow, glutton for punishment? :)13:46
EmilienM\o/13:46
fifieldt_cool, so it seems that is progressing13:47
fifieldt_perhaps you can update your etherpad with the new gdoc link EmilienM :)13:47
fifieldt_so, we have 13 minutes of meeting time left13:47
fifieldt_life or docs? :)13:47
NickChasewriterDiane:  I'm here, aren't I?13:47
NickChase:)13:47
ekarlso-ello folks13:47
fifieldt_hi ekarlso-13:47
fifieldt_we're just in open discussion on docs now13:48
writerDiane_yes!!!! ha ha ha13:48
fifieldt_any thoughts?13:48
EmilienMfifieldt: of course I can13:48
fifieldt_cheers EmilienM13:48
fifieldt_ok, unless ekarlso- has comments in the next half minute, I'm tempted to call the meeting to a close :)13:49
sldlol13:49
sldi had an addendum.13:49
fifieldt_yes?13:49
sldi was thinking of emaililng the guy that did the config-option-grabbing stuff for nova/c...was it cinder or ceilometer i don't remember.. to see if had anything more genericised. (sp?).13:50
sld...since apparenlty that stuff is from last year - if not older.13:50
fifieldt_yes, sounds good13:50
fifieldt_#action sld get in touch with conf file code people to collaborate13:51
fifieldt_anyone else?13:51
*** kchenweijie has joined #openstack-meeting13:51
*** mtreinish has joined #openstack-meeting13:51
*** kchenweijie has left #openstack-meeting13:51
fifieldt_I have to run to another meeting now myself13:51
writerDiane_bye13:51
*** writerDiane_ has left #openstack-meeting13:51
fifieldt_thanks all!13:51
NickChasethanks fifieldt_13:51
fifieldt_#endmeeting13:51
fifieldt_have fun!13:51
NickChasebye!13:51
*** ladquin has left #openstack-meeting13:52
*** eharney has joined #openstack-meeting13:52
*** NickChase has quit IRC13:53
*** gakott has joined #openstack-meeting13:54
EmilienMo/13:55
*** garyk has joined #openstack-meeting13:56
*** stevemar has joined #openstack-meeting13:57
*** garyTh has joined #openstack-meeting13:57
*** fifieldt_ has quit IRC13:58
*** skort has quit IRC13:58
*** gakott has quit IRC13:59
*** michchap has joined #openstack-meeting14:00
*** JimJiang has left #openstack-meeting14:00
*** michchap_ has joined #openstack-meeting14:02
*** changbl has joined #openstack-meeting14:03
*** michcha__ has joined #openstack-meeting14:03
*** michchap has quit IRC14:04
*** michchap has joined #openstack-meeting14:05
*** seiflotfy_ has joined #openstack-meeting14:05
*** michch___ has joined #openstack-meeting14:06
*** michchap_ has quit IRC14:07
*** michchap_ has joined #openstack-meeting14:07
*** timello_ has quit IRC14:07
*** michcha__ has quit IRC14:08
*** michcha__ has joined #openstack-meeting14:09
*** michchap has quit IRC14:09
*** chuckieb has joined #openstack-meeting14:10
*** timello_ has joined #openstack-meeting14:10
*** michch___ has quit IRC14:10
*** cp16net is now known as cp16net|away14:11
*** michchap_ has quit IRC14:11
*** adalbas has joined #openstack-meeting14:11
*** tayyab has quit IRC14:12
*** sld is now known as sld-away14:13
annegentle#endmeeting14:13
*** openstack changes topic to "R/O volumes (Meeting topic: cinder)"14:13
openstackMeeting ended Tue Jun 11 14:13:58 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:14
openstackMinutes:        http://eavesdrop.openstack.org/meetings/doc_web_team/2013/doc_web_team.2013-06-11-13.01.html14:14
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/doc_web_team/2013/doc_web_team.2013-06-11-13.01.txt14:14
openstackLog:            http://eavesdrop.openstack.org/meetings/doc_web_team/2013/doc_web_team.2013-06-11-13.01.log.html14:14
*** michcha__ has quit IRC14:14
*** tayyab has joined #openstack-meeting14:14
*** cp16net|away is now known as cp16net14:16
*** cp16net is now known as cp16net|away14:16
*** cp16net|away is now known as cp16net14:18
*** zehicle_at_dell has joined #openstack-meeting14:18
*** marun has quit IRC14:18
*** sgordon has left #openstack-meeting14:18
*** noslzzp has joined #openstack-meeting14:22
*** mrutkows has joined #openstack-meeting14:25
*** krtaylor has joined #openstack-meeting14:26
*** enikanorov_ has quit IRC14:28
*** ivasev has joined #openstack-meeting14:29
*** pmurray has joined #openstack-meeting14:29
*** pmurray has left #openstack-meeting14:30
*** dkehn has quit IRC14:33
*** dcramer_ has joined #openstack-meeting14:36
*** Banix has joined #openstack-meeting14:36
*** marun has joined #openstack-meeting14:37
*** otherwiseguy has joined #openstack-meeting14:40
*** topol has joined #openstack-meeting14:40
*** michchap has joined #openstack-meeting14:40
*** vijendar has quit IRC14:42
*** jcoufal has quit IRC14:44
*** mdenny has joined #openstack-meeting14:44
*** Mr_T has joined #openstack-meeting14:46
*** lloydde has joined #openstack-meeting14:47
*** jtomasek has quit IRC14:48
*** alexpilotti has quit IRC14:49
*** vijendar has joined #openstack-meeting14:49
*** murkk has joined #openstack-meeting14:51
*** koolhead17 has quit IRC14:52
*** michchap has quit IRC14:52
*** michchap has joined #openstack-meeting14:54
*** n0ano has joined #openstack-meeting14:54
*** armax has joined #openstack-meeting14:55
*** michchap_ has joined #openstack-meeting14:57
*** sushils has quit IRC14:58
*** michcha__ has joined #openstack-meeting14:58
*** michchap has quit IRC14:58
*** michchap has joined #openstack-meeting14:59
n0ano#startmeeting scheduler14:59
openstackMeeting started Tue Jun 11 14:59:45 2013 UTC.  The chair is n0ano. Information about MeetBot at http://wiki.debian.org/MeetBot.14:59
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:59
*** openstack changes topic to " (Meeting topic: scheduler)"14:59
openstackThe meeting name has been set to 'scheduler'14:59
n0anoshow of hands, anyone here for the scheduler meeting?15:00
*** michch___ has joined #openstack-meeting15:00
*** senhuang has joined #openstack-meeting15:01
senhuanghi guys15:01
*** danwent has joined #openstack-meeting15:01
*** sushils has joined #openstack-meeting15:01
*** armax has left #openstack-meeting15:01
*** michchap_ has quit IRC15:01
*** pmurray has joined #openstack-meeting15:01
*** michchap_ has joined #openstack-meeting15:02
*** PhilDay has joined #openstack-meeting15:02
*** michcha__ has quit IRC15:02
n0anohmm, slow start today, I'm getting a lack of enthusiasm from the crowd :-)15:02
PhilDayI'm here - what do you want to talk aboui ?15:03
*** tayyab has quit IRC15:03
*** michcha__ has joined #openstack-meeting15:03
n0anoI was hoping to talk about the scaling issues that jog0 brought up last week.15:03
pmurrayHi I'm new to this group but I'll be joining in15:04
*** michchap has quit IRC15:04
n0anopmurray, NP welcome15:04
PhilDayDid jog0 have specific issues that he'd seen - or was it a general question ?15:04
n0ano#topic scheduler scaling15:04
*** openstack changes topic to "scheduler scaling (Meeting topic: scheduler)"15:04
n0anounfortunately, he brought it up in the last 5 min. so we don't have a lot of detail...15:05
*** michch___ has quit IRC15:05
PhilDayAre you here jog0 ?15:05
n0anothe basic issues was BlueHost created a 16K node cluster, discovered the scheduler was not working and removed it in favor of a totally random scheduler15:05
*** michchap_ has quit IRC15:06
PhilDayBluehost have a very specific use case though - they are in effect a trad. hosting company, and so they can in effect hand place thier VMs15:06
n0anoI don't believe they did a thorough analysis of what was wrong but the guess would be the scheduler dealing with all the compute node updates.15:06
senhuangthis is interesting. it will be great if we can get more details on the bottleneck15:06
*** tanisdl has joined #openstack-meeting15:07
n0anosenhuang, that was my thought, I'd like to know what is wrong to see if there's an implementation issue or something needs to be re-archtected15:07
*** michcha__ has quit IRC15:07
PhilDaySo they didn't need a rich scheduler.   I didn't get the imporession that they spent long tying to work out the issues15:07
senhuangn0nao: yes. agreed15:07
PhilDayMost of thier effort went into DB access15:08
n0anoPhilDay, I'm not that concerned with BH's specific use case, if there is a scaling issue I'd like to analyze it and see what can be done.15:08
*** hub_cap has joined #openstack-meeting15:08
PhilDaySo I think it would be wrong to conclude from Bluesacle that there is a specific scale issue15:08
*** marun has quit IRC15:08
n0anoPhilDay, possibly, but it is a data point, do we know of any more traditional cloud use cases that have scaled beyond what the scheduler can handle?15:09
senhuangPhilDay: what is special about a trad. hosting company in terms of scheduling?15:09
PhilDayI did find one issue this week that I'm working on a fix for - which is that some filters really don't need to run for each instance in request - e.g. no need to evaluate the AZ filter 100 times for 100 instances - esp as it currently makes a db query for each host15:10
PhilDaySo I'm looking at making filters able to declare if they need to be run for each instance or just once15:10
*** garyk has quit IRC15:11
PhilDaycompute_filter is another that it doesn't make sense to run multiple times15:11
n0anoPhilDay, good idea but I'd be more concerned about compute node updates, seems like that would be an on-going overhead that could cause scaling issues.15:11
*** garyk has joined #openstack-meeting15:11
n0anoalso, I thought there was an effort to create a DB free compute node, is that still a goal or have we dropped that idea?15:12
PhilDayAs I understand it there are two update paths (not sure why).    The hosts send updates on capabitlies via mesages to the scheduler, but the resource counts are still updated via the DB.15:12
n0anowe should really consolidate one or the other, two paths seem silly15:13
PhilDayNot clear to me that there is value in the capability update messages as they stand, as they are pretty much fixed data.  You can filter the rate at which they send the updates.15:13
garykhi, sorry for joing late15:13
n0anoalso, not sure why capabilities are periodically sent since they are static15:13
*** egallen has quit IRC15:13
senhuangPhiDay: maybe the update is another way of heartbeat?15:13
PhilDayIts two different sets of data; capabilites and capacity15:13
n0anoI'd prefer to remove the DB update and put everything in the message to the scheduler15:14
PhilDayMaybe, but its not used as such as far as I can see15:14
senhuangagreed. basically qualitative and quantitative capabilities15:14
PhilDayIf you do it all in messages then you need some way for a scheduler to know at start up when it has all of the data15:15
n0anobut it does create an obvious scale issue, have all compute nodes send a message with static data to the scheduler seems a little silly15:15
n0anoPhilDay, how would that be different from getting the same data (possibly incomplete) from the DB15:16
*** davidkranz has quit IRC15:16
PhilDayI could be wrong - but that was my reading of the code.  For sure the host manager view of capacity is read from the DB at the start of each request15:16
*** sandywalsh has quit IRC15:16
n0anowouldn't be that hard to have the scheduler ignore nodes that haven't reported capacity yet15:17
PhilDayBut when your trying to stack to teh most loaded host you coudl get soem very wrong results durign that start up stage15:17
*** carl_baldwin has joined #openstack-meeting15:18
PhilDayAt least with teh DB you get the full scope of hosts, even if the data is stale.  And stale data is handled by the retry15:18
n0anoPhilDay, but is a non-optimal scheduling decision, only during startup, that big a problem.15:18
*** davidkranz has joined #openstack-meeting15:18
PhilDayDepends on your use case I guess ;-)   I'm sure there wil be someone its a problem for15:19
*** egallen has joined #openstack-meeting15:19
PhilDayI think we have to be wary of trying to design out scale issues that we don't know for sure exist15:19
*** koolhead17 has joined #openstack-meeting15:20
*** koolhead17 has joined #openstack-meeting15:20
n0anoI don't know, stale (e.g. incorrect data) in some sense is even worse to me than no data at all.15:20
*** derekh has quit IRC15:20
n0anobottom line, 2 mechanisms (message & DB) seem wrong, we should pick one and use that15:21
*** derekh has joined #openstack-meeting15:21
PhilDay Probably need to start with a post in openstack.dev to see if someone can explain why capabilities are sent by messages15:22
n0anoPhilDay, good idea15:23
*** carl_baldwin has left #openstack-meeting15:23
n0ano#action n0ano to start thread on openstack-dev about messages to scheduler15:23
*** lloydde_ has joined #openstack-meeting15:23
*** hartsocks1 has joined #openstack-meeting15:24
PhilDayPerhaps the generic host state BP is the right place to mop up any changes around this ?15:24
*** hartsocks1 has joined #openstack-meeting15:24
n0anopotentially, I'm interested in the area so I can look at that BP and see what's appropriate, do you have a specific link to it?15:25
*** shengjie has quit IRC15:25
PhilDayhttps://blueprints.launchpad.net/nova/+spec/generic-host-state-for-scheduler15:25
n0anotnx, I'll check it out15:25
n0anowe've talked about compute node capacity updates, are there any other obvious scaling issues in the scheduler we can think of?15:26
*** hartsocks has quit IRC15:26
*** lastidiot has joined #openstack-meeting15:26
*** lloydde has quit IRC15:26
*** davidkranz has quit IRC15:27
*** boris-42 has quit IRC15:28
n0anothen, without any empirical data (like what BH was seeing), we'll have to accept what the scheduler is doing so far.15:28
*** davidkranz has joined #openstack-meeting15:28
n0ano#topic DB free compute node15:29
*** openstack changes topic to "DB free compute node (Meeting topic: scheduler)"15:29
*** hartsocks1 has quit IRC15:29
* n0ano this is fun, being the chair means I can set the topics :-)15:29
n0anoI thought there was a goal for this at one point in time, is that still true?15:29
*** lloydde_ has quit IRC15:30
*** vijendar has quit IRC15:30
*** hartsocks has joined #openstack-meeting15:31
n0anohmm, hearing silence, I guess I'll have to bring this up on the mailing list15:31
n0ano#topic opens15:31
*** openstack changes topic to "opens (Meeting topic: scheduler)"15:31
n0anoAnyone have anything new they want to bring up today?15:32
*** haomaiwang has joined #openstack-meeting15:32
haomaiwangjoin #openstack-cinder15:32
*** changbl has quit IRC15:32
n0anohaomaiwang, forgot the `/' on that join :-)15:32
garykn0ano: the instance groups is coming along nicely and would be nice if we can get some help with the reviews15:32
*** sandywalsh has joined #openstack-meeting15:32
n0anogaryk, sure, you got a pointer I can add to ping people15:33
garykn0ano: that would be great - https://blueprints.launchpad.net/openstack/?searchtext=instance-group-api-extension . hopefully by the end of the week we'll have the cli support too15:33
*** mdomsch has quit IRC15:34
n0anoall - if you got the time, try and give a review on this15:34
garykn0ano: thanks15:34
*** michchap has joined #openstack-meeting15:35
*** sandywalsh has quit IRC15:35
*** PhilDay has quit IRC15:35
*** senhuang has quit IRC15:35
n0anoI'm hearing silence so I think we'll close a little early this week (more time for reviews :-)15:36
*** PhilDay has joined #openstack-meeting15:36
garyki need to run to swap the babysitter. sorry15:36
n0anoOK, tnx everyone and we'll type at each other next week15:37
n0ano#endmeeting15:37
*** openstack changes topic to "R/O volumes (Meeting topic: cinder)"15:37
openstackMeeting ended Tue Jun 11 15:37:12 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:37
openstackMinutes:        http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-06-11-14.59.html15:37
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-06-11-14.59.txt15:37
openstackLog:            http://eavesdrop.openstack.org/meetings/scheduler/2013/scheduler.2013-06-11-14.59.log.html15:37
*** senhuang has joined #openstack-meeting15:37
*** pmurray has quit IRC15:37
*** PhilDay has quit IRC15:37
*** dripton_ is now known as dripton15:38
*** MarkAtwood has joined #openstack-meeting15:40
*** garyk has quit IRC15:40
*** Mr_T has left #openstack-meeting15:40
*** hemna has quit IRC15:40
*** hemna has joined #openstack-meeting15:41
*** ociuhandu has joined #openstack-meeting15:45
*** schwicht has joined #openstack-meeting15:45
*** michchap has quit IRC15:46
*** belmoreira has quit IRC15:47
*** belmoreira has joined #openstack-meeting15:48
*** vijendar has joined #openstack-meeting15:50
*** sandywalsh has joined #openstack-meeting15:50
*** pnavarro has joined #openstack-meeting15:55
*** jcoufal has joined #openstack-meeting15:55
*** jcoufal has quit IRC15:56
*** jcoufal has joined #openstack-meeting15:56
*** kirankv has joined #openstack-meeting15:57
*** MarkAtwood has quit IRC15:58
*** belmoreira has quit IRC15:58
*** senhuang has quit IRC15:59
*** mordred has quit IRC15:59
*** mordred has joined #openstack-meeting15:59
*** lloydde has joined #openstack-meeting15:59
*** reed has joined #openstack-meeting16:00
primeministerp#startmeeting hyper-v16:00
openstackMeeting started Tue Jun 11 16:00:15 2013 UTC.  The chair is primeministerp. Information about MeetBot at http://wiki.debian.org/MeetBot.16:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.16:00
*** openstack changes topic to " (Meeting topic: hyper-v)"16:00
openstackThe meeting name has been set to 'hyper_v'16:00
primeministerphi everyone16:00
schwichthi ...16:00
*** mrodden has quit IRC16:00
ociuhanduhi everyone16:00
primeministerphi tavi16:00
primeministerppnavarro: hi pedro16:00
*** kchenweijie1 has joined #openstack-meeting16:01
*** koolhead17 has quit IRC16:01
*** mrodden1 has joined #openstack-meeting16:01
primeministerphmm was hoping lluis would show up16:01
primeministerplet's wait a couple minutes before we get started16:01
*** kchenweijie1 has left #openstack-meeting16:01
*** alexpilotti has joined #openstack-meeting16:02
primeministerpalexpilotti: i'm waiting a couple in hopes that lluis will join16:02
alexpilottimorning!16:02
primeministerphehe16:02
primeministerpmorning!16:02
pnavarrohello !16:03
alexpilottipnavarro: hola!16:03
primeministerppedro!16:03
primeministerpok16:03
primeministerpthat was a couple16:03
primeministerp#topic status update wmiv216:03
*** openstack changes topic to "status update wmiv2 (Meeting topic: hyper-v)"16:03
*** seanrob has joined #openstack-meeting16:04
primeministerpalexpilotti: how is the wmiv2 code migration progressing16:04
alexpilottiwe are almost done16:04
alexpilottithe idea is simple:16:04
alexpilottiV2 utils classes inherit from V116:04
*** colinmcnamara has joined #openstack-meeting16:04
alexpilottiprovide the new namespace and different implementations whenever needed16:04
*** sushil_ has joined #openstack-meeting16:05
alexpilottia fatory method (like the one we have for volume utils) takes care of instantiating the right one based on the OS16:05
*** spzala_ has joined #openstack-meeting16:05
alexpilotti*factory16:05
primeministerpalexpilotti: so this will allow the backward compatitbility for 2008r2 to remain intact16:05
alexpilottiyes16:05
primeministerpalexpilotti: perfect16:05
alexpilottieverythinhg that used to work on 2008 R2 will still work16:05
alexpilottionly new features will be applied to V2 only16:06
schwichtnice16:06
*** shang_ has joined #openstack-meeting16:06
primeministerpalexpilotti: although obviously this there for "legacy" purposes"16:06
*** ekarlso has joined #openstack-meeting16:06
primeministerponly16:06
alexpilottiyeah, the idea is to eventually remove the V1 classes16:06
*** shang has quit IRC16:06
*** shang_ has quit IRC16:06
alexpilottiin a few years, which are geological ages in this domain :-)16:07
*** shang has joined #openstack-meeting16:07
primeministerpour goal to reiterate is to use 2012 and on as the default platform for development16:07
primeministerpok16:07
alexpilottimost meaningful features, including  OpenVSwitch and Ceph16:08
alexpilottiwill be on 2012+16:08
primeministerpwhen will the bits be ready for testing16:08
primeministerpre: wmiv216:08
alexpilottimaybe we'll manage to have them up for review this week already16:08
primeministerpgreat16:08
alexpilottiClaudiu, one of our guys is working on it16:09
*** MIDENN_ has joined #openstack-meeting16:09
primeministerpoki shall we move on then16:09
alexpilottisure16:09
*** pnavarro has quit IRC16:09
primeministerpalexpilotti: shared mem?16:09
*** krtaylor_ has joined #openstack-meeting16:09
*** pnavarro has joined #openstack-meeting16:10
*** lastidiot1 has joined #openstack-meeting16:10
alexpilottioki16:10
primeministerp#topic hyper-v shared memory support16:10
*** openstack changes topic to "hyper-v shared memory support (Meeting topic: hyper-v)"16:10
alexpilottishared mamory is a fairly easy thing16:10
alexpilottibut we'll need 2 options16:10
*** RajeshMohan has quit IRC16:11
*** lastidiot has quit IRC16:11
*** ekarlso- has quit IRC16:11
*** ndipanov has quit IRC16:11
*** sushils has quit IRC16:11
*** spzala has quit IRC16:11
*** mrodden1 has quit IRC16:11
*** n0ano has quit IRC16:11
*** mdenny has quit IRC16:11
*** krtaylor has quit IRC16:11
*** sushil_ is now known as sushils16:11
alexpilottiactually it's "dynamic memory"16:11
primeministerpsorry16:11
*** spzala_ is now known as spzala16:11
alexpilottinp, I was also going on with it :-)16:11
primeministerpbalooning16:11
alexpilottiyep16:11
primeministerpre ballooning16:11
alexpilottiso we need one optio: "enable_dynamic_memory", defaulting to false16:12
*** RajeshMohan has joined #openstack-meeting16:12
primeministerpI knew what i was talking about too ;)16:12
*** sushils has quit IRC16:12
schwichtprimeministerp: is that supported with regular LIS or just on windows VMs ?16:12
alexpilottiand "dynamic_memory_initial_perc"16:12
*** neelashah1 has joined #openstack-meeting16:12
primeministerpschwicht: yes16:12
primeministerpschwicht: in newer releases i believe16:12
alexpilottischwicht: yep, including Linux now16:12
*** neelashah has quit IRC16:12
schwichtok, good .. we had that discussion the other days, and I was not sure about the RHEL 6.4 situation ...16:13
*** michchap has joined #openstack-meeting16:13
alexpilottithe latter option is needed to tell Hyper-V how much memory to allocate initially in percentage16:13
alexpilottilet's say that a flavor states 10GB ram, if the above option's value is 60, the initial memory will be 6GB16:14
alexpilottias easy as that16:14
alexpilottithere's of course the risk of overcommitting and what applies for any balooning consideration applies to openstack as well16:15
primeministerpobviously16:15
alexpilottiin particular the scheduler can get confused by the amount of free memory16:15
alexpilotticonsidering that the host reports to Nova the current free memory, w/o considering VM requirements16:16
*** mrodden has joined #openstack-meeting16:16
alexpilottiany comment on this?16:16
primeministerphmm16:16
*** stevemar has quit IRC16:16
primeministerpi'm thinking16:16
*** ndipanov has joined #openstack-meeting16:16
primeministerpthe scheduler issues can be dangerous leading to cascading failure16:17
alexpilottiit's a very useful feature, but misusage can create huge issues16:17
*** stevemar has joined #openstack-meeting16:17
primeministerpalexpilotti: exactly16:17
alexpilottithat's why I bvote for disabling it by default16:17
primeministerp+116:17
alexpilotti> so we need one optio: "enable_dynamic_memory", defaulting to false16:17
alexpilottipnavarro: ehat's your opinion?16:17
alexpilotti*what16:18
pnavarroin vmare exists the same functionality... I was thinking how they are doing that...16:18
* primeministerp pokes pnavarro 16:18
pnavarroin the esxi plugin16:18
alexpilottipnavarro: VMWare uses shared paging16:18
*** sushils has joined #openstack-meeting16:19
alexpilottipnavarro: the implementation differs from the Hyper-V way16:19
*** kebray has joined #openstack-meeting16:19
alexpilottisince we are using SLAT on Hyper-V shared pages make little sense16:19
pnavarrook, but from an  API point of view, you set % and intervals too..16:20
*** rostam has quit IRC16:20
alexpilottipnavarro: sure16:20
alexpilottipnavarro: I'm not familiar with their settings, let me take a look16:20
*** writerDiane has joined #openstack-meeting16:20
*** writerDiane has quit IRC16:20
pnavarroabout overcommitment there are some flags to make the scheduler aware16:21
*** writerDiane has joined #openstack-meeting16:21
*** otherwiseguy has quit IRC16:22
primeministerppnavarro: could we theoritically reuse those?16:22
alexpilottipnavarro: I'm looking at the VMWare driver, but I don't see anything16:22
alexpilottipnavarro: do you have a link to teh code line by any chance?16:22
*** bdpayne has joined #openstack-meeting16:23
*** michchap has quit IRC16:23
*** terry7 has joined #openstack-meeting16:23
pnavarrono, I've used the vmware API in the past, I didn't know how the esxi was using that16:23
pnavarroI was just wondering...16:24
*** rostam has joined #openstack-meeting16:24
*** jlucci has joined #openstack-meeting16:24
alexpilottipnavarro: are you sure is not the scheduler's overcommit?16:24
pnavarrowell, I'm not sure...16:25
pnavarrosorry16:25
primeministerpok16:25
primeministerpno worries16:25
*** krtaylor_ has quit IRC16:25
alexpilottipnavarro: ram_allocation_ratio16:25
alexpilottithat's the option name16:25
alexpilottiok, if any additional idea should come up, let's add comments to the BP whiteboard in case, please16:26
primeministerpperfect16:27
primeministerpI was hoping luis would be here16:27
*** jaybuff1 has joined #openstack-meeting16:27
primeministerpi'll skip the puppet discussion as I need his input16:27
alexpilottiprimeministerp: can you please add Ceph to the topics?16:27
primeministerpo16:27
primeministerpyes16:27
primeministerp#topic ceph16:27
*** openstack changes topic to "ceph (Meeting topic: hyper-v)"16:27
primeministerpalexpilotti: you want to begin or do you want me to start?16:28
alexpilottiSo, we're prelimiarily discussing the porting of BRD to Hyper-V with Inktank16:28
primeministerpalexpilotti: RBD16:28
alexpilottimy initial idea was to "simply" port the linux kernel driver to Windows16:28
alexpilottiprimeministerp: yep sorry, mixing up acronysm is a passion of mine :-)16:29
primeministerpalexpilotti: i'm here to keep you honest16:29
primeministerp;)16:29
alexpilottilol16:29
alexpilottiback to RBD,16:29
primeministerpalexpilotti: although that could totally be taken out of context16:29
primeministerp;)16:30
alexpilottithe problem is that the kernel driver is way behind librbd16:30
*** fifieldt has quit IRC16:30
alexpilottiwhich is the userspace library used by qemu, for example16:30
alexpilottifor example cloning is not implemented in the kernel module, only in the userspace lib16:30
alexpilottiin Hyper-V we have no choice, we need a kernel driver16:31
primeministerpalexpilotti: meaning that's it consumed more via vms through qemu than by native kernel drivers?16:31
alexpilottiprimeministerp: yep, the main business case is KVM16:31
alexpilottimy initial idea is to write a userspace filesystem driver using librbd16:32
primeministerpthe kernel drivers were more for the clustered storage replacement16:32
*** ayoung has quit IRC16:32
alexpilottimoving to a full kernel one once Inktank (or the community) will bring the kernel module on parity16:32
alexpilottiadvantages of this approach:16:32
alexpilottisecurity: we are in userspace, no blue screen16:33
primeministerpalexpilotti: i'm assuming it's quciker development too16:33
alexpilottifast development: we avoid all the kernel debugging nightmares16:33
primeministerphehe16:33
alexpilottiyep :)16:33
primeministerpso are we talking h timeframe?16:34
alexpilottiwe can use threads, work in C++, no IRQ dispatch issues, etc etc16:34
*** pnavarro has quit IRC16:34
*** pnavarro has joined #openstack-meeting16:34
alexpilottidisadvantages:16:34
alexpilotticontext switches might affect quite a bit the performance side16:34
zehicle_at_dellsorry, I was late16:35
zehicle_at_dellhad to prep for HostingCon panel next week16:35
primeministerpzehicle_at_dell: ok16:35
primeministerpzehicle_at_dell: and you are?16:35
alexpilottialthough all the traffic will go on TCP/IP16:35
primeministerpzehicle_at_dell: care to introduce yourself?16:35
alexpilottizehicle_at_dell: nice to see you here :-)16:35
primeministerphaha16:36
*** schwicht has quit IRC16:36
primeministerprob16:36
primeministerpzehicle_at_dell: hi rob16:36
zehicle_at_dellL)16:36
primeministerpzehicle_at_dell: nice name16:36
ociuhanduzehicle_at_dell: hi Rob16:36
zehicle_at_dellThis is Rob Hirschfeld, I'm on the Dell OpenStack team16:36
primeministerpzehicle_at_dell: we're talking ceph on hyperv16:36
zehicle_at_dellCool!16:37
primeministerpzehicle_at_dell: alexpilotti is talking about the userspace being ported to hyper-v16:37
alexpilottizehicle_at_dell: can you see the previous msgs in the chat?16:37
zehicle_at_dellyy16:37
alexpilottizehicle_at_dell: I'd like to hear your opinion on this16:37
*** krtaylor has joined #openstack-meeting16:38
alexpilottizehicle_at_dell: but we can talk about it later if you need time16:38
zehicle_at_dellintersting, so are you saying that the HyperV Cinder integration cannot use block store?16:38
alexpilottizehicle_at_dell: only the iSCSI wrapper for now16:39
zehicle_at_dellok, that should be OK16:39
alexpilottizehicle_at_dell: fairly ok, not as good as native Ceph of course16:39
*** neelashah has joined #openstack-meeting16:39
alexpilotti*native RBD16:39
zehicle_at_dellthe goal would be to have the RBD driver I'm assuming16:39
zehicle_at_dellclient16:40
alexpilottiyep16:40
primeministerpthat's what we're talking about16:40
*** neelashah has quit IRC16:40
*** neelashah1 has quit IRC16:40
primeministerpalexpilotti: move on to ovs?16:40
alexpilottisure16:41
primeministerp#topic OpenVSwitch16:41
alexpilottiI just wanted to introduce the topic16:41
*** openstack changes topic to "OpenVSwitch (Meeting topic: hyper-v)"16:41
*** neelashah has joined #openstack-meeting16:41
alexpilotti(i mean RBD)16:41
primeministerpalexpilotti: yep16:41
primeministerpalexpilotti: we should do the same now for ovs, considering your recent announcement?16:41
zehicle_at_dell(closing on RBD, I think it's interesting for us.  Will have to reflect on it some more, it's not our first use case)16:42
alexpilottizehicle_at_dell: I don't know if the news reached you, we're porting OVS to Hyper-V16:42
zehicle_at_dellI think that's awesome16:42
alexpilottido you have any specific requirements for OVS?16:43
alexpilottilike specific tunnelling protocols, etc16:43
*** pnavarro has quit IRC16:44
*** jtomasek has joined #openstack-meeting16:44
alexpilottizehicle_at_dell: ^^16:44
*** pnavarro has joined #openstack-meeting16:44
primeministerpalexpilotti: ideall the same ones as the core project16:44
zehicle_at_dellWe're looking at GRE tunnels as the integration approach16:44
alexpilottiok, tx16:45
alexpilottitalking in general about OVS, it's a fairly big effort16:45
alexpilottilot's of kernel code to be ported (including GRE and VXLAN)16:45
alexpilottilots of userspace posix -> Windows migration work16:46
alexpilottiwe're ramping up a "swat" team for it16:46
zehicle_at_dellwhat features of OVS are being planned?16:46
zehicle_at_dellfor example, is VLAN support higher than GRE16:47
alexpilottizehicle_at_dell: well, VLAN altready works with OVS on Hyper-v now16:47
alexpilottizehicle_at_dell: for the rest: OpenFlow, ovsdb, all userspace tools, tiunnelling (GRE, VXLAN)16:48
alexpilottithose are roughly the main features involved16:48
*** fnaval has quit IRC16:49
primeministerpalexpilotti: all the usual suspects16:49
primeministerp;)16:49
alexpilottiamong the goals, we want to use the Quantum OVS agent on Hyper-V16:49
alexpilottiwhich means thet the CLI tools must be completely ported as well16:49
zehicle_at_delldo you have a feel for the relatative priorities?16:50
*** michchap has joined #openstack-meeting16:50
zehicle_at_dellbeause GRE would be high on our list since we've built infrastructure to work with that16:50
*** salv-orlando has quit IRC16:50
primeministerpzehicle_at_dell: is the switch integration stronger now?16:50
alexpilottizehicle_at_dell: we're collecting customer based priorities now16:51
zehicle_at_dellgood question -> the choice for GRE allowed use to bypass that for now16:51
alexpilottizehicle_at_dell: good to know16:51
zehicle_at_dellso, it was a good first pass because it was easier to get adoption started16:51
zehicle_at_dellVLAN would have required more switch config work16:51
primeministerpzehicle_at_dell: understood16:52
*** BobBall has quit IRC16:52
alexpilottizehicle_at_dell: GRE is anyway already before VXLAN oin our GANTT16:52
zehicle_at_delldownside is that GRE will have performance impacts16:52
zehicle_at_dellperfect16:52
alexpilottiVXLAN introduction in OVS is very recent16:52
alexpilottiand I expect some big changes in the tunnelling world soon16:52
*** harlowja has joined #openstack-meeting16:53
alexpilottiso it's hard to predict now how much VXLAN will get traction in QUantum16:53
*** vipul|away is now known as vipul16:53
primeministerpzehicle_at_dell: do you have specific topics to add?16:53
alexpilotti(I keep on calling it Quantum if you don't mind for now) ;-)16:53
primeministerppfkaq16:54
alexpilottilol16:54
pnavarrolol !16:54
*** jlucci has quit IRC16:54
primeministerpalexpilotti: any final words on ovs?16:54
*** vijendar has quit IRC16:54
zehicle_at_dellfor the current working set, you said VLAN was enabled?16:55
zehicle_at_dellagainst Grizzly?16:55
alexpilottiyep16:55
alexpilottiyep16:55
primeministerpzehicle_at_dell: yes16:55
alexpilottithat was our goal16:55
*** ryanpetrello has quit IRC16:55
zehicle_at_dellok, I'll need to see where we stand on VLAN.  I think we've got it in place but not our primary test path16:55
*** ryanpetrello has joined #openstack-meeting16:56
*** seanrob has quit IRC16:56
alexpilottiusing the Hyper-V Quantum agent with 100% OVS compatibility was the main use case16:56
*** seanrob has joined #openstack-meeting16:56
alexpilottion VLAN, I mean16:56
alexpilottiprimeministerp: should we move to the next topic?16:56
primeministerpalexpilotti: yes16:56
primeministerpalexpilotti: is there one?16:57
*** seanrob_ has joined #openstack-meeting16:57
primeministerpalexpilotti: puppet bits are on hold until luis and i sync16:57
*** vipul is now known as vipul|away16:57
alexpilottiif nexttopic == NULL -> endmeeting() ;-)16:57
primeministerpok16:57
primeministerpzehicle_at_dell: anything you want to add?16:57
primeministerplooks like frank left16:58
primeministerpok16:58
primeministerp#endmeeting16:58
*** openstack changes topic to "R/O volumes (Meeting topic: cinder)"16:58
openstackMeeting ended Tue Jun 11 16:58:24 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)16:58
openstackMinutes:        http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-06-11-16.00.html16:58
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-06-11-16.00.txt16:58
primeministerpthanks everyone16:58
openstackLog:            http://eavesdrop.openstack.org/meetings/hyper_v/2013/hyper_v.2013-06-11-16.00.log.html16:58
alexpilottitx bye!16:58
pnavarrociao !16:58
ociuhandubye all16:58
*** johnthetubaguy1 has joined #openstack-meeting16:59
*** marun has joined #openstack-meeting16:59
*** derekh has quit IRC16:59
zehicle_at_dellthanks everyone!16:59
*** vijendar has joined #openstack-meeting16:59
*** abhisri has joined #openstack-meeting17:00
*** nati_ueno has joined #openstack-meeting17:00
*** johnthetubaguy has quit IRC17:01
*** seanrob has quit IRC17:01
*** michchap has quit IRC17:01
*** johnthetubaguy1 has quit IRC17:02
*** shang has quit IRC17:06
*** kirankv has quit IRC17:07
*** changbl has joined #openstack-meeting17:07
*** SergeyLukjanov has quit IRC17:10
*** otherwiseguy has joined #openstack-meeting17:11
*** gyee has joined #openstack-meeting17:12
*** mrunge has joined #openstack-meeting17:13
*** dolphm has joined #openstack-meeting17:13
*** Tross has joined #openstack-meeting17:19
*** sandywalsh has quit IRC17:19
*** jcoufal has quit IRC17:20
*** spzala has quit IRC17:22
*** jtomasek has quit IRC17:23
*** spzala has joined #openstack-meeting17:26
*** michchap has joined #openstack-meeting17:27
*** HenryG has quit IRC17:28
*** kchenweijie has joined #openstack-meeting17:28
*** cp16net is now known as cp16net|away17:29
*** kchenweijie has left #openstack-meeting17:31
*** timello_ has quit IRC17:31
*** sandywalsh has joined #openstack-meeting17:32
*** Mandell has joined #openstack-meeting17:36
*** enikanorov has joined #openstack-meeting17:36
*** enikanorov has quit IRC17:38
*** enikanorov has joined #openstack-meeting17:38
*** michchap has quit IRC17:39
*** timello has joined #openstack-meeting17:39
*** seanrob_ has quit IRC17:42
*** sandywalsh has quit IRC17:45
*** schwicht has joined #openstack-meeting17:49
*** kchenweijie has joined #openstack-meeting17:50
*** mkollaro has quit IRC17:51
*** lpabon has joined #openstack-meeting17:53
*** kchenweijie has left #openstack-meeting17:54
*** cp16net|away is now known as cp16net17:54
*** maoy has joined #openstack-meeting17:55
*** nati_uen_ has joined #openstack-meeting17:57
*** nati_ueno has quit IRC17:57
*** sandywalsh has joined #openstack-meeting17:58
*** abhisri has quit IRC17:58
*** fabio has joined #openstack-meeting17:58
*** brich1 has joined #openstack-meeting17:58
*** bknudson has joined #openstack-meeting17:59
*** egallen has quit IRC17:59
stevemarkeystoners assemble!17:59
*** henrynash has joined #openstack-meeting17:59
gyeehenrynash!17:59
*** nachi__ has joined #openstack-meeting17:59
*** abhisri has joined #openstack-meeting17:59
gyeeyah17:59
henrynashgyee: hi!18:00
spzalaHi!18:00
fabioHi!18:00
lbragstadhey! stevemar nice18:00
nachi__hi18:00
*** kiall has joined #openstack-meeting18:00
dolphmo/18:00
stevemarlbragstad, credit goes to ayoung18:00
dolphmno ayoung?18:00
gyeehey everybody, say hi to fabio, new guy from HP18:00
dolphmfabio: o/18:01
topolhello18:01
stevemarhi fabio18:01
bknudsonhi fabio18:01
spzalafabio: Hello18:01
*** tiamar has joined #openstack-meeting18:01
gyeefyi, he don't have long hairs and big muscle18:01
lbragstadHey fabio18:01
*** benonsoftware has quit IRC18:01
dolphmunnacceptable18:01
gyeehaha18:01
henrynashgyee: and you still hired him?18:01
bknudsonI can dream, can't I.18:01
dolphm#startmeeting keystone18:01
openstackMeeting started Tue Jun 11 18:01:50 2013 UTC.  The chair is dolphm. Information about MeetBot at http://wiki.debian.org/MeetBot.18:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.18:01
*** openstack changes topic to " (Meeting topic: keystone)"18:01
openstackThe meeting name has been set to 'keystone'18:01
*** Mandell has quit IRC18:01
dolphm#topic Havana milestone 2 cut & API-level feature freeze July 16th18:02
*** openstack changes topic to "Havana milestone 2 cut & API-level feature freeze July 16th (Meeting topic: keystone)"18:02
topolwho remembers those I cant believe its not butter commercials with Fabio?18:02
*** ryanpetrello has quit IRC18:02
dolphm#link https://wiki.openstack.org/wiki/Havana_Release_Schedule18:02
dolphmjust a reminder that api-impacting things need to land this milestone18:02
*** SergeyLukjanov has joined #openstack-meeting18:02
*** tkammer has joined #openstack-meeting18:02
dolphmso, get on identity-api reviews asap :D18:02
dolphm#topic High priority bugs or immediate issues?18:03
*** openstack changes topic to "High priority bugs or immediate issues? (Meeting topic: keystone)"18:03
topoldolphm, you have a link?18:03
*** the_akshat has joined #openstack-meeting18:03
dolphmtopol: https://review.openstack.org/#/q/project:openstack/identity-api+status:open,n,z18:03
topolfor identity-api reviews18:03
*** marun has quit IRC18:03
topolthanks18:03
dolphmbug 1179955 is still outstanding18:04
uvirtbotLaunchpad bug 1179955 in keystone "Disabling a tenant would not disable a user token" [Critical,In progress] https://launchpad.net/bugs/117995518:04
gyeewas hoping to get a resolution on the inherited role stuff18:04
dolphmit's marked in progress and assigned to me, but i'll i've done is put up tests WIP18:04
henrynashgyee: on the agenda later18:04
*** whenry has joined #openstack-meeting18:04
henrynashdolphm: what needs doing …the actual fix?18:05
dolphmhenrynash: yeah18:05
dolphmhenrynash: we should probably do a simple fix asap, but i'd like to take a long hard look at the overall problem and do a lot of refactoring18:05
dolphmif anyone wants to put up a fix, feel free, otherwise i'm sure i'll get to it in a couple days18:06
dolphmi'm not aware of any other big issues that need attention, so...18:06
*** michchap has joined #openstack-meeting18:06
dolphm#topic Changing the default token backend from KVS to SQL or Memcache18:06
*** openstack changes topic to "Changing the default token backend from KVS to SQL or Memcache (Meeting topic: keystone)"18:06
dolphm#link https://bugs.launchpad.net/keystone/+bug/118837018:06
uvirtbotLaunchpad bug 1188370 in keystone "kvs driver for tokens is not a production quality default" [Low,In progress]18:06
dolphm#link https://review.openstack.org/#/c/32296/18:06
*** krtaylor has quit IRC18:06
topoldolphm, I htought Memcache was the only one that really scales18:06
dolphmhenrynash commented in the above review that we should also consider memcache as a viable default option18:06
topol+118:07
morganfainbergtopol: memcache does scale better, thought, it has some issues.18:07
henrynashI think we all agree kvs is not the right one18:07
bknudsonwe should have at least one token backend that's production quality18:07
dolphmtopol: both are better than kvs :)18:07
topolSQL makes us look bad when under stress :-)18:07
bknudsonmaybe we need a note regarding each backend the quality, production or not18:07
henrynashis PKI the default on the client now?18:07
dolphmhenrynash: ?18:07
topolPKI??18:07
dolphmbknudson: kvs backends are raelly intended to be undocumented / for dev18:08
henrynashfor tokens18:08
dolphmhenrynash: what does the client care?18:08
bknudsonPKI is a server setting18:08
henrynash(instead of UUID)18:08
bknudsonclient knows how to handle PKI or UUID18:08
topolPKI is default on server side18:08
bknudson(correct me if I'm wrong)18:08
morganfainbergbknudson: that is my understanding18:08
bknudsondoes memcache require any extra packages / server started?18:09
henrynash…in which case this (I think) would make the performance of memcache vs SQL somewhat mute…(since the token can be validate in the auth_token middleware18:09
bknudsonnice thing about kvs is it doesn't require any config18:09
morganfainbergbknudson: it requires the python-memcache client, and the memcache server18:09
*** kchenweijie1 has joined #openstack-meeting18:09
morganfainbergrunning.18:09
dolphmmorganfainberg: ++18:09
*** Mandell has joined #openstack-meeting18:09
morganfainbergSQL is probably the best default since the identity drive defaults to SQL.18:10
topolarent those typically there?18:10
henrynashand the only issue is the built up of records due to us not having any auto-cleanup of expired tokens by default18:10
morganfainbergtopol: the python-memcache package, yes.18:10
bknudsonI assume someone would have db setup for another backend (identity), so they'd already have it setup.18:10
morganfainbergbknudson: yep.18:10
bknudsonso I'd lean towards sql.18:11
*** BobBall has joined #openstack-meeting18:11
henrynashbknudson: my issue is that if we do that, by default, the DB will fill for ever18:11
topolSo SQL does not do well under stress.  So you will get a lot of bug reports where you end up recommending memcache to handle the load18:11
dolphmhenrynash: we have keystone-manage token_flush now18:11
henrynashdolphm: true…I assume that is a manual operation (by default)18:12
bknudsondevstack must set the token backend to sql.18:12
morganfainbergI am also working on some retro-fitting of the revocation lists, which will include (if I can make it happy) cleanup options18:12
bknudsonmorganfainberg: for sql or memcache?18:12
morganfainbergbknudson: the revocation list cacheing BP will encompass all revocation lists18:12
morganfainbergi'm planning on making it have semantics to cleanup SQL if enabled.18:13
*** zehicle_at_dell has quit IRC18:13
morganfainbergagain, provided I can do it cleanly18:13
bknudsonhad we discussed before not providing so many tokens?18:13
topolI would recommend that we convince ourselves that SQL wont fill up anymore before it becomes the default18:13
bknudsonthis is kind of the root of the problem18:13
*** atiwari has joined #openstack-meeting18:13
dolphmi think the best first step is to switch to sql as a default, and then have the "should we switch to memcache" as a default after that18:13
*** MarkAtwood has joined #openstack-meeting18:13
gyee+118:14
morganfainbergthat is the end-all solution, but we need to be tolerant of people issuing a ton of tokens.18:14
*** zehicle_at_dell has joined #openstack-meeting18:14
dolphm... have that *conversation* later18:14
morganfainberg+1 to what dolphm said18:14
dolphmtopol: it will fill up just as kvs does18:14
dolphmtopol: so, it's not a worse solution than kvs in that respect18:14
bknudsonI have no problem with sql as the default.18:15
topoldolphm, agreed.18:15
henrynashdolphm: Ok, agreed…let's do that18:15
dolphmcool18:15
dolphm#topic Push to complete role-assignment/inheritance api changes18:15
*** openstack changes topic to "Push to complete role-assignment/inheritance api changes (Meeting topic: keystone)"18:15
henrynashso this is just a call to get any final comments into these bps…links coming up...18:15
dolphm#link https://review.openstack.org/#/c/29781/18:15
dolphm#link https://blueprints.launchpad.net/keystone/+spec/inherited-domain-roles18:16
henrynashthx :-)18:16
gyee"scope" is more extensible18:16
bknudsonso now roles have attributes18:16
bknudsonand aren't just names18:16
dolphmi haven't caught up to this conversation since thursday/friday..18:16
topolI knew I would something important while on vacation...18:17
henrynashSo roles give guidance as to how inheritance should work WHEN they get assigned18:17
*** michchap has quit IRC18:17
henrynashFor everyone's info:18:17
*** Tross has quit IRC18:17
henrynashthe current proposal only covers inheriting from a domain to its projects18:18
gyeetoday role definition is just a name, nothing more18:18
*** akshat_at_cern has joined #openstack-meeting18:18
dolphmgyee: for consumers, that won't change18:18
dolphmcorrect?18:18
*** tkammer has quit IRC18:18
henrynashgyee and others would also like more global roles across all domains…What I have proposed (read the various comments) can be extended for that18:18
henrynashI am suggesting we put that extension into a separate proposal18:19
gyeedolphm, right, unless we change the policies18:19
dolphmdon't want to impact anyone on this18:19
henrynashgyee: the point about "scope" vs booleans…..18:19
gyeerole assignment is really about the scope in which the role is "applicable"18:19
gyeeboolean is not extensible18:20
*** leandrorosa has joined #openstack-meeting18:20
bknudsonI generally agree that booleans are a bad idea where an enum would be more descriptive.18:20
henrynashgyee: we need to have distinctions between how to apply role assignments to both domains and and projects….As per my comments, we would add a second boolean for "inherted_to_domains"…since you need all 4 states18:20
dolphmgyee: is there an extensibility scenario you have in mind that you didn't suggest in the code review? henrynash seems to address your concerns pretty well18:21
gyeehenrynash, we don't want to keep adding booleans18:21
gyeeso tomorrow we want to support othe scopes, we are going to keep adding boolean?18:21
henrynashgyee: we either have two booleans or all 4 states in the enum18:22
*** psedlak has quit IRC18:22
bknudsonhttp://codeclimber.net.nz/archive/2012/11/19/Why-you-should-never-use-a-boolean-field-use-an.aspx18:22
gyeethat would be very confusing would it18:22
*** akshat_at_cern_ has joined #openstack-meeting18:22
gyeehaving to aggregate the two or more18:22
gyeebknudson, agreed 110%, booleans are bad for multistate18:22
dolphmgyee: the meaning of your enumerations was obviously a source of confusion in the last keystone meeting18:22
*** akshat_at_cern has quit IRC18:23
fabio+1 bknudson18:23
dolphmgyee: perhaps there are more intuitive terms we can use, but that's my *only* opposition to your proposal18:23
henrynashgyee: my concern is if they are independant concepts, then is an 8 role enum better than 3 booleans?18:23
gyeedolphm, I am fine with different naming18:23
gyeebut I am not fine with boolean18:23
henrynashgyee, dolphm: Ok, I'll document both alreatnatives in a email tonight…and I'll look to response by tomorrow…then we'll make the call18:24
bknudsonif it turns out that the names aren't adequate maybe we go to a structure (object), or maybe we add another field.18:24
bknudsonEither way, I18:24
bknudsonI'd prefer names over true/false.18:24
gyeeI am fine with either a structure, enum, or string18:24
gyeebut not boolean18:24
*** fnaval has joined #openstack-meeting18:25
dolphmgyee: what's the fundamental opposition to booleans?18:25
gyeedolphm, role scope is multi-state18:25
gyeeyou don't want to use multiple booleans to describe multiple states18:25
*** lauria has joined #openstack-meeting18:26
dolphmi really don't want to see things like 'inherits-to-projects-but-not-if-assigned-to-a-group-on-tuesdays' in the enumeration to handle dumb edge cases18:26
gyeeenum or string gives us a lot of flexibility18:26
*** MarkAtwood has quit IRC18:26
henrynashright now we'd have (something like)18:27
dolphmgyee: is there some scenario you have in mind that you're designing for beyond the 4 states we're currently discussing?18:27
atiwariI also see an issue with defining global behavior in roleDef18:27
henrynashinherited_to_projects, inherited_to_domains, Inhertited_to_projects_and_domains18:27
gyeedolphm, and you want to represent 4 states in a boolean?18:27
dolphmatiwari: +1 that's a weird one, because the assignment of a 'global' role to a specific project or domain doesn't make any sense18:27
atiwariwe have to define multiple roleDefs and which will make complexity in policy18:27
gyeeatiwari, policies act on role names18:28
*** salv-orlando has joined #openstack-meeting18:28
*** vijendar has quit IRC18:28
gyeeit doesn't care about the mechanism in which the role is obtain18:28
dolphmgyee: he's saying he'd have to radically expand the number of role names he's using in policy18:28
*** krtaylor has joined #openstack-meeting18:28
atiwarithat is true but think of one Nova role e.g. sys-admin18:28
gyeewe are talking about the mechanism to assign roles18:28
dolphm'admin' will have to become 'global-admin' 'domain-admin' and 'project-admin'18:28
atiwarihow do we fit that for global and domain-global use case18:29
gyeeatiwari, its more scarier than that :)18:29
henrynashatiwari: we are not defining any kind of global behaviour in the role itself….only how that role is inherited (or not) form the point of assignment18:29
gyeerole definitions are not tied to services18:29
gyeeyou have to name your role different to avoid conflicts18:29
topoldo we have the notion of a global-admin (ie super-admin) yet?18:29
dolphmhenrynash: changing the semantics of how a role can be applied (defining it to be 'global' in scope) has direct impact on the way that role can be intuitively assigned18:29
gyeesay you have an "admin" role, how can you tell its really a nova admin or swift admin?18:30
bknudsonhenrynash: the inherited_by_projects property only has an effect at the time of assignment, so that if I change the value, no existing assignments are affected?18:30
bknudson(which is different than a previous revision of the design)18:30
dolphmhenrynash: PUT /projects/{project_id}/users/{user_id}/roles/{some_global_role} suddenly doesn't make sense18:30
henrynashdolphm: which is why we don't use the term "global" anywhere18:30
*** noslzzp has quit IRC18:30
dolphmyet18:30
atiwarigyee that is another issue which need some attention the serviceId18:30
henrynashdolphm: and I'm not suggesting we ever dp18:30
henrynashdo18:30
gyeeatiwari, absolutely18:31
dolphmhenrynash: i know :)18:31
henrynashwhat we *might* do is add a iinherited_to_domains flag in the role...18:31
atiwariroleDef without a serviceId is complex to handle18:31
gyeeinherited by projects is essentially "global" within a domain, no?18:31
henrynashand then if you applied (using an api that doesn't exist today) PUT /dmains/*/roles/roleId/users/userId18:32
atiwariand we ahev to make the role name unique all over the services18:32
dolphmgyee: that's not global at all, according to your definition of global18:32
atiwarihave18:32
gyeedolphm, global and domain-global18:32
henrynashgyee: there are just too confusing18:32
dolphmgyee: do you get 'global' roles along with an unscoped token?18:32
gyeeglobal - applicable to all projects and all domains, regardless of token scope18:32
*** hub_cap has left #openstack-meeting18:32
gyeedolphm, global yes, domain-global no18:33
henrynashgyee, dolphm: give me the floor here for 3 mins18:33
topoldidnt we have a similar conversation last week???18:33
*** haomaiwang has quit IRC18:34
atiwarihenrynash: I think we need to think through a use case to support global as well as domain-global roleDef for the similar capability18:34
henrynashthe things we add to roledef should just indicate HOW we inherit (or not) roles when they are assugned18:34
henrynashso18:34
atiwariand I can see that we will endup with complex policy18:34
*** ladquin has joined #openstack-meeting18:34
henrynashinherit_to_projects means….IF you assign this role to a domain, it will be interpreted as being inherited to any projects within it18:35
atiwariI think inheritence should be enforced in the role assignment18:35
henrynashimagine we add inherit_to_domains as another options (via enum or whatever) to roeldef18:35
henrynashthen18:35
*** sushils has quit IRC18:35
*** kchenweijie1 has left #openstack-meeting18:35
henrynashIF you can assign just a role to a "root" domain, then all child domains would inherit that role18:36
*** derekh has joined #openstack-meeting18:36
henrynashif we ever supported nested domains, only the one below the assignment point would inherit the roles18:36
atiwarithink you need same capabilty for a global and domain-global roleDef18:36
atiwariyou can not get that with single roleDef18:37
henrynashthe missing piece(for inherit_to_domains) would be to amend the assignment API to someone specify "the root" domain18:37
henrynash</henry>18:37
atiwariyou have to define multiple roleDefs and hence policy18:37
dolphmhenrynash: aaand, you've sold me on booleans18:37
topolhenrynash  why would all levels of nested domains inherit the role???18:37
dolphmtopol: because inherit_to_domains=true18:37
topolerr why wouldnt?18:37
henrynashtopol: (hyperthetcially) …onlythose domains in the tree below the assignment point18:37
topolbut multiple levels deep, correct?18:38
henrynashtopol: yes18:38
topolk, im good then18:38
dolphmi like how subdomains are suddenly on the table again lol18:38
henrynashtopol: not that we have sub domains yet18:38
topolunderstood. just for my own understanding18:38
henrynashdolphm: I'm not pushing for them, just wanted a solution that would work with them18:38
dolphmhenrynash: i appreciate that18:39
gyeehenrynash, so you are proposing one boolean "inherited_to_domains" as oppose to "inherited_by_projects"?18:39
gyeenot sure if I understand you18:39
dolphmgyee: both18:39
henrynashgyee: no, tow booleans18:39
henrynashinherited_to_domains, and18:39
dolphmgyee: inherited_by_projects today, the other tomorrow18:39
henrynashinherited_to_projects18:39
*** vijendar has joined #openstack-meeting18:39
topolI actually find the booleans easy to understand.18:39
gyeeand they are both mutually exclusive?18:39
dolphmtopol: +118:39
bknudsonhow about { "inherited": { "domains": true, "projects": true } }18:39
henrynashgyee: no18:40
dolphmtopol: i share you confusion with the enumerations18:40
atiwarigyee +118:40
henrynashbknudson: I'm ok with taht18:40
topolcause if we have a hard time undersat5nding the semantics our stakeholders will forever send us bug reports18:40
*** brich1 has left #openstack-meeting18:40
henrynashI actually wanted to call them "apply_to_child_projects"18:40
dolphmtopol: +118:40
henrynash"apply_to_child_domains"18:40
henrynashbut thought that child wasn't real a term we use18:41
fabiobknudson: you don't even need the boolean, you can just have a list18:41
topolwhat was wrong with inherited _to_domains and inherited_to_projects???18:41
bknudson{ "inherited": ["domains", "projects"] }18:41
gyeewhat happen if "domains": true, "projects": false?18:41
fabioyes18:41
gyeeor the other way around?18:42
fabioin this way is extensible18:42
dolphmi think i prefer to individual booleans over the structure18:42
fabioyou can add new concepts18:42
henrynashgyee; roles sit on the domain, don't get to the projects18:42
dolphmfabio: did you just miss the last 20 minutes of conversation?18:42
fabiono I did not18:42
*** kchenweijie has joined #openstack-meeting18:42
fabiowhy do you have to say project = true18:42
fabioif project is in the list it means it inherits from it18:43
*** kchenweijie has joined #openstack-meeting18:43
*** kchenweijie has left #openstack-meeting18:43
henrynashfabio: means it gets inherited to18:43
atiwariare we still thinking of having inheritable in roleDef?18:43
*** mkollaro has joined #openstack-meeting18:43
henrynashwhich is kind of why I like the more descriptive booleans…."inherited_to_projects" or "apply_to_child_projects"...18:44
henrynashatiware: this is all about the roelDef18:44
*** michchap has joined #openstack-meeting18:44
*** novas0x2a|laptop has joined #openstack-meeting18:44
dolphmhenrynash: +118:44
henrynashbut { "inherited to": ["domains", "projects"] } would be your view bknudson?18:45
gyeehenrynash, that's would be the enum approach we talked about earlier18:45
bknudsonhenrynash: yes, this would remove duplication18:45
atiwarihenrynash: I think we are not seeing the problem with this approach18:45
gyeeI am down with the enum approach18:46
gyeeless confusion18:46
gyeeand extensible18:46
dolphmgyee: more* confusion18:46
fabioI agree with bknudson18:46
dolphmgyee: just as extensible*18:46
gyeedolphm, keep adding boolean as extension?18:47
topol+1 on the booleans18:47
dolphmgyee: sure, or add an enumeration on top of that if you find a use case that booleans don't work for18:47
bknudsoneven with booleans it's not like we can't change it to a string/enum later.18:47
bknudsonthat's the power of JSON18:47
dolphmgyee: booleans solve the current use cases18:47
atiwarionce we set a roleDef with any inheritance behavior that roleDef is used only for that.18:48
atiwariand we have to define multiple roleDefs for the same purpose18:48
gyeedolphm, he's use case is cloud provider version admin18:49
gyeethat's applicable to all the domains18:49
gyeeversus admin18:49
*** Otavio_ has joined #openstack-meeting18:49
henrynashso let's finish the booleans discussion18:49
henrynashI think  the general agreement is two booelans or { "inherited to": ["domains", "projects"] }18:49
topol+2 on the booleans..  (I will keeep upping the ante)18:50
gyeehenrynash, that looks like an enum18:50
gyee{ "inherited to": ["domains", "projects"] }18:50
*** michchap has quit IRC18:50
*** derekh has quit IRC18:50
*** jhenner has quit IRC18:50
atiwari-2 with this approach18:50
*** colinmcnamara1 has joined #openstack-meeting18:50
*** abhisri has quit IRC18:51
henrynashatiwari which? { "inherited to": ["domains", "projects"] }18:51
topolatiwari, which approach?18:51
atiwarihaving this info in roleDef18:51
*** ryanpetrello has joined #openstack-meeting18:51
*** colinmcnamara has quit IRC18:52
henrynashdolphm: suggest we rule for two booleans for now18:52
dolphm+118:52
henrynashatwari: happy to take it off line and discuss your conerns18:52
atiwariThis would cause role explosion and policy complexity.18:52
topolagreed, until we have use cases that show two booleans wont work18:52
topol(if ever)18:53
bknudsonI thought rbac already had a problem with role explosion?18:53
dolphmatiwari: i don't see how the other model is any different in that respect18:53
gyeeI need some clarification18:53
gyeeare we going with this? { "inherited to": ["domains", "projects"] }18:53
henrynashatiwari: so that was my INITIAL concern over using try roleDef, but the general consensus was that was better than changing the apis to include inheritance as parameters18:53
topolwhy isnt this scenario fairly contained for what henerynash is trying to accomplish? For more complex stuff we may add somethig else, vcorrect?18:53
atiwaribut this approach wd cause even more explosion18:54
dolphmtopol: +1, i just want to make sure we're not screwing ourselves over on future use cases18:54
atiwarisorry I did not see the issue that time18:54
atiwariand now it seems totally wrong to me18:55
dolphm(5 min)18:55
dolphmatiwari: since we don't have much time left, can you put together an example illustrating your concern and reply to one of henry's email on openstack-dev with it?18:55
atiwarisure18:56
*** murkk has quit IRC18:56
atiwariI will do18:56
gyeedolphm, henrynash, are we going with this? { "inherited to": ["domains", "projects"] }18:56
dolphminherits_to_projects = boolean18:56
gyeek, I am getting conflict answer then18:57
*** chuckieb has quit IRC18:57
dolphmdid i miss something?18:57
gyeethought we are going with this { "inherited to": ["domains", "projects"] }18:57
gyeeI am cool with that18:57
topoldolphm, please declare which way we are going. im getting confused18:58
dolphmgyee: that's completely identical in functionality and extensibility to inherits_to_domains + inherits_to_projects18:58
topol(boolean or enumeration)18:58
gyee+1 on enum, -1 on multiple booleans18:58
henrynashdolphm, gyee: yes, I see them as the same……18:58
dolphmboth of these are boolean-based approaches, it's just a matter of style... what we've decided is to *not* do full enumeration ('global', 'domain-global', 'project-local', etc)18:58
dolphmi can't even remember the full enumeration18:58
topolI can live either way18:59
*** derekh has joined #openstack-meeting18:59
henrynashdolphm: exactly18:59
dolphmyay18:59
*** mkollaro has quit IRC18:59
dolphm#endmeeting18:59
*** openstack changes topic to "R/O volumes (Meeting topic: cinder)"18:59
openstackMeeting ended Tue Jun 11 18:59:24 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)18:59
openstackMinutes:        http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-06-11-18.01.html18:59
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-06-11-18.01.txt18:59
openstackLog:            http://eavesdrop.openstack.org/meetings/keystone/2013/keystone.2013-06-11-18.01.log.html18:59
jeblairany ci/infra people around?18:59
*** atiwari has quit IRC18:59
*** bknudson has left #openstack-meeting18:59
pleia2o/19:00
clarkbo/19:00
fungiheya19:00
*** fabio has quit IRC19:00
* BobBall sneaks in before anyone notices19:00
*** ChanServ sets mode: +o jeblair19:00
* ttx is around but afflicted by hte lag-of-death19:00
*** jeblair changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"19:01
mordredo/19:01
jeblair#startmeeting infra19:01
openstackMeeting started Tue Jun 11 19:01:14 2013 UTC.  The chair is jeblair. Information about MeetBot at http://wiki.debian.org/MeetBot.19:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.19:01
*** openstack changes topic to " (Meeting topic: infra)"19:01
openstackThe meeting name has been set to 'infra'19:01
zulhelo19:01
jeblaircan we comment when we use #link ?19:01
*** olaph has joined #openstack-meeting19:01
fungizul: ehlo will provide a lot more options19:01
jeblairlike #link agenda http:// ...?19:01
fungii thought that didn't work19:02
olapho/19:02
jeblair#help19:02
zulfungi:  if sendmail wasnt broken then it might19:02
*** vipul|away is now known as vipul19:02
zaroo/19:02
jeblair#link https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting19:02
jeblair#topic actions from last meeting19:03
*** openstack changes topic to "actions from last meeting (Meeting topic: infra)"19:03
jeblair#link http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-06-04-19.01.html19:03
jeblairmordred made a signup thingy for bootcamp!19:03
*** tiamar has left #openstack-meeting19:03
mordredIndeed!19:03
jeblairmordred: but i think it's still missing some people, right?19:03
BobBallQuick Q - do you prefer us to raise items for AOB now, or wait until the open discussion to raise them?19:03
mordredI'm assuming that to be the case19:03
jeblairmordred: aren't there supposed to be some people from mirantis?19:03
mordredjeblair: yes. and also possibly dell and ibm (not sean) and piston19:04
pleia2BobBall: typically at the end (unless you have time constraints)19:04
BobBallno, that's fine :) Just some people prefer the other way - was just asking :)19:04
jeblairBobBall: there's an open discussion time at the end (sometimes), but the agenda is open, so you can add items to https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting before the meeting too19:04
mordredjeblair: so, I tihnk it's going to be a crowd!19:04
jeblairexcellent19:04
*** jeblair sets mode: -o jeblair19:04
BobBalloh drat - wish I had edited the agenda to put what I want to talk about at the start :D19:05
* BobBall will wait patiently :)19:05
clarkbjeblair: you don't like wearing hats to meetings?19:05
jeblairreed did summarize the trystack thing, but i haven't seen any responses19:05
reedyeah, no response19:05
lloyddesignup thingy for bootcamp?19:05
mordredhttps://docs.google.com/forms/d/1ZV1Ct6GlaTioWajEVoBcahRNBHRDfBRxiLRYgmQj_lg/viewform19:06
anteayameetings need hats19:06
mordred#link https://docs.google.com/forms/d/1ZV1Ct6GlaTioWajEVoBcahRNBHRDfBRxiLRYgmQj_lg/viewform19:06
ttxhats need signup thingies19:06
jeblairlloydde: a bootcamp for people who would like to become serious regular contributors to openstack-infra19:06
lloyddergr19:06
*** Otavio_ has left #openstack-meeting19:07
fungidefined as people who fix at least as much stuff as they break ;)19:07
fungi(hopefully)19:07
jeblairzul is working on a py3k ppa; though i think at the moment we're looking at f18 for testing py3k...19:07
jeblairfungi: careful, we don't want to recklessly change the criteria and lose mordred.  :)19:08
fungii think zul posted the link for that in #-infra on friday?19:08
fungiha19:08
fungisometimes you eat the bug, and sometimes the bug eats you19:08
zulfungi:  yeah its ready to be tetsed19:08
fungizul: that was quantal-sane but not for precise, right?19:08
*** salv-orlando has quit IRC19:08
clarkbzul: can you #link it here?19:08
jeblairreed: ping19:09
zulfungi:  precise sane19:09
zulclarkb:  just a sec19:09
zul#link https://launchpad.net/~zulcss/+archive/py3k19:09
fungiaha. so that gives us the opportunity to do tox -epy33 as long as we stop pip-installing things system-wide19:09
reedsorry folks, being dragged in multiple conversations19:09
zulits suacy python3 rebuilt for precise19:09
zul(because im running saucy)19:10
zullike a good boy19:10
*** abhisri has joined #openstack-meeting19:10
jeblair#topic Mailing list19:10
*** openstack changes topic to "Mailing list (Meeting topic: infra)"19:10
jeblairreed: anything going on with the general mailing list move?19:10
reedno relevant progress to report yet :(19:11
jeblairbummer19:11
jeblair#topic gearman (for zuul)19:11
*** openstack changes topic to "gearman (for zuul) (Meeting topic: infra)"19:11
jeblairhey i have to qualify that now.  that's cool.  :)19:12
jeblairanyway, i think zuul-gearman and gearman-plugin are ready for use in production...19:12
clarkbjeblair: ready today or ready after a couple more changes?19:12
clarkb(it wasn't clear to me after you saw the null pointer exception and if the fix was sufficient)19:12
clarkbalso, I am super excited about getting gearman zuul going. So many shiny things can happen after that19:13
mordred++19:14
jeblairi'd like to make the change during a slightly less busy time... perhaps some time friday19:14
fungithat sounds great19:14
jeblairand be prepared to roll the change back if it doesn't work out19:14
mordreddo it right now after I just pushed changes to every single core project!19:14
ttxclarkb: you should blog about that gearman zuul thing19:15
jeblairclarkb: i believe my fix for the npe is sufficient -- at least it should keep things going if something weird happens19:15
clarkbjeblair: ok19:15
clarkbttx: no I think that honor goes to jeblair and zaro19:15
fungijeblair: do we want to conflate the zuul change window with the pending project renames/cleanup, or am i jumping ahead in the meeting agenda?19:15
ttxclarkb: as long as they are as excited as you are, that works19:15
jeblairclarkb: (even if it doesn't address the actual cause)19:15
jeblairttx: i am very excited.19:16
jeblairthis is my excited face.19:16
ttxI want to feel the excitement too19:16
* mordred is weirded out by jeblair's excited face19:17
zarojeblair: where will the other master be?:19:17
ttx^W oops too late19:17
jeblairfungi: i was thinking it would be a good idea to combine them19:17
uvirtbotttx: Error: "W" is not a valid command.19:17
*** michchap has joined #openstack-meeting19:17
jeblairzaro: what other master?19:17
zarojeblair: won't you setup with 2 masters or are you starting with just 1 ?19:17
fungiokay, cool. i was going to draft up an etherpad with cut-n-pasty steps for the renames, so we can integrate the zuul upgrade/rollback steps19:17
jeblairzaro: oh, just one.  :)19:17
*** ladquin is now known as ladquin_brb19:17
jeblairfungi: yeah, let's see if we can schedule all those at the same time. if we can't, oh well.19:18
*** david-lyle has joined #openstack-meeting19:19
jeblairshould we aim for friday morning, or friday afternoon? (vaguely us-time)?19:19
*** benonsoftware has joined #openstack-meeting19:19
fungii'm good with either... afternoons tend to be pretty light on gate activity19:20
zaro++ morning19:20
fungimornings less so, but if we announce in advance then it seems fine with me19:20
fungipoll?19:20
jeblairclarkb, mordred: thoughts?19:20
clarkbyeah I can do either, but afternoons are quieter and I don't mind spending time friday afternoon assisting19:20
mordredjeblair: I could go either19:21
mordredit might not be terrible to do morning though19:21
*** ivasev has quit IRC19:21
mordredso that we can see it in action for a while while we're all still around19:21
mordredsince this is, well, a fairly fundamental change to the world order19:21
kiallHah - Yea, Friday afternoon deploys *always* result in a whole weekend off ;)19:21
kiallEsp the major ones :)19:21
jeblairi'm leaning toward afternoon....19:22
mordredkk19:22
jeblairbecause if we find that we have to do an immediate rollback, there's less mess to clean up.19:22
fungii'll be around well into the night (my time) if things break horribly and rollback isn't smooth19:22
jeblair#topic project renames19:23
*** openstack changes topic to "project renames (Meeting topic: infra)"19:23
jeblairhub_cap isn't around...19:23
jeblairbut kiall is.19:23
jeblairkiall: did you decide you wanted to do the moniker->designate rename now?19:23
*** atiwari has joined #openstack-meeting19:23
kiallSo - If Gerrit is going down anyway, lets rename.. That way if the incubation proposal is rejected, no need to schedule another downtime.19:24
*** mrunge has quit IRC19:24
mordredkiall: if it is accepted, we can always rename you to the openstack org whenever we rename quantum to mutnauq19:24
jeblairkiall, ttx: if designate is incubated, when would it be accepted?19:24
mordredjeblair: it would be at least 2 weeks out19:24
kiall25th or so would be the TC meet19:25
*** marun has joined #openstack-meeting19:25
ttxyeah minimum in +2weeks19:25
fungii just pinged hub_cap in #-trove19:25
jeblairokay, if we do the rename now, there is the potential to have two renames in fairly rapid succession... :/19:25
mordredandit might take us more than one meeting to decide19:25
*** SlickNik has joined #openstack-meeting19:25
jeblairkiall: but that mostly affects you...19:25
jeblairkiall: so i'm okay with it if you are.  :)19:25
kiallAh, we'll survive 2 renames.. The less we have to take gerrit down, the better IMO.19:26
kiallSo - whatever causes the least disruption to overall set of projects.19:26
*** mrunge has joined #openstack-meeting19:26
jeblairkiall: is friday afternoon us-time okay with you?  that'll be a hard cutover for developers where they'll have to update remotes, etc, afterwords.19:27
kiallYea, that's fine.19:27
fungithe trove crowd says they think hub_cap is afk all day19:27
*** pnavarro has quit IRC19:28
fungii asked him to hit us up in #-infra whenever he can to talk about the possibility of getting renamed friday afternoon19:28
jeblairfungi: cool, thx19:28
*** markmcclain has joined #openstack-meeting19:28
mordredttx: any chance mutnuaq will be accepted by friday?19:28
*** nachi__ has quit IRC19:28
zulmutnuaq?19:28
mordredzul: it's what jeblair and I decided quantum should be renamed to19:28
kiall<aside>I hope not ;) That's an awful name IMHO!</aside>19:28
ttxmordred: the new name might be in by Friday19:28
zulmordred: ah19:29
ttxmordred: I thought we would get it today tbh19:29
* markmcclain is still waiting on legal feedback from the latest list19:29
mordredcool19:29
ttxjeblair: did Mark say anything at the staff call ?19:29
*** michchap has quit IRC19:29
*** boris-42 has joined #openstack-meeting19:29
jeblairttx: mark and jbryce were not on it; no one else had heard anything.  :(19:29
fungiit was a quick call19:29
fungiso anyway, mutnuaq soon come19:30
ttxheh19:30
jeblair#topic Hosting gitweb on another machine19:30
*** openstack changes topic to "Hosting gitweb on another machine (Meeting topic: infra)"19:30
jeblairso gerrit's been being affected by web spiders a lot recently...19:30
*** ayoung has joined #openstack-meeting19:30
jeblairwell, one spider (bing)19:30
mordredthanks microsoft!19:31
*** whenry has quit IRC19:31
jeblairso perhaps we should run gitweb (or gitblit or something) on another machine19:31
clarkbhow important is gitweb? do we need to run it at all? (I only use it to look at acl files)19:31
pleia2does anyone use that gitweb?19:31
* ttx 's train running, may disappear unexpectantly19:31
clarkbpleia2: o/19:31
mordredI have used it before19:31
ttxclarkb: +119:31
mordredbut I usually use github19:31
jeblairpleia2: it gets lots of hits.  :)19:31
mordredjeblair: from not bing?19:32
kiallpleia2: yea, more often than I would have thought I would..19:32
fungii think it dovetails nicely into wanting to have somewhere to point people to get copies of our git repos which aren't a commercial closed-source proprietary service19:32
pleia2fair enough19:32
jeblairso a lot of projects you know, maintain a git.project.org where they run git and gitweb or cgit or gitblit...19:32
fungisticking a web interface on top of that becomes gravy19:32
clarkbyeah ok. I am not against it just wondering what the use case was. sounds like there is a good one19:32
jeblairit's also good for automated testing...19:33
fungiand since gerrit has gitweb links baked in (and a way to massage the urls for them?) gitweb is probably an easy sell to keep that integration intact19:33
kiallIs a better solution to rate limit and/or block spiders from hitting the UI?19:33
*** danwent has quit IRC19:33
pleia2kiall: the first robot.txts file was installed yesterday :)19:33
fungikiall: already done, belt and braces19:33
jeblairi'd rather have peoples test rigs hammering at git.openstack.org than gerrit, even with our local caching mirror19:34
mordred++19:34
*** seanrob has joined #openstack-meeting19:34
jeblairfungi: yeah, the gitweb links are pretty flexible; mediawiki links them to their gitblit server19:34
fungiin addition to the robots.txt which tells bing to cool its heels, we're still actively dropping connections from their bots with iptables19:34
jeblairfungi: maybe about time to remove that...19:35
kiallfungi: lol, how are they going to read the robots.txt then? ;)19:35
*** mrutkows has quit IRC19:35
fungithe robots.txt is for when the iptables rules get undone19:35
fungiand yeah, i can carefully undo those after the meeting19:36
mordredjeblair: so, external seems good- pending long bikeshed conversation about which git server thign to run19:36
jeblairmordred: yes.  any quick thoughts on that?19:36
*** Tross has joined #openstack-meeting19:37
jeblairi guess we should look at gitweb, and probably gitblit because wikimedia use it; though that means running another java app.  however, it's fast and pretty.19:37
mordredjeblair: not really. gitlab is pretty, but also heavy weight. gitweb is what we're using now. people like cgit. gitblit is java19:37
*** vipul is now known as vipul|away19:37
*** sarob has joined #openstack-meeting19:37
*** Tross has quit IRC19:37
jeblairkernel.org uses cgit19:38
jeblairokay, so i'll file a bug and suggest that whoever takes it look at those 4 options.19:38
mordredkk19:39
mordredI'd be fine with any of them I think19:39
mordredI do like that git.wikimedia.org and git.kernel.org give indexes19:39
mordredthe git.kernel.org index looks friendly to our org structure19:39
jeblairthe wikimedia folks apparently chose gitblit at least partially because it efficiently produces tarballs19:39
*** sarob has quit IRC19:40
mordredah. well, I do not care about that feature19:40
jeblairi don't think that's really a requirement for us, since we currently produce branch-tip archives19:40
mordredin fact, I want to avoid people thinking that's a feature19:40
pleia2I can probably look at those 4 and draft up some pros/cons for our next meeting19:40
jeblairthat's good to know.  that could be an anti-requirement.19:40
*** danwent has joined #openstack-meeting19:40
fungiyeah, people already want to download tarballs of our stuff from github, and that's a recipe for disaster19:40
clarkbyeah19:41
jeblair(either don't support that or be able to turn it off)19:41
mordred++19:41
*** jang1 has joined #openstack-meeting19:41
jeblairpleia2: cool, you want to go ahead and file the bug and assign it to yourself, at least for the first part of this?19:41
*** timello has quit IRC19:41
pleia2jeblair: will do19:41
jeblairpleia2: any toci things to discuss?19:42
pleia2just quick progress update19:42
jeblair#action pleia2 file bug and look into gitweb-style options19:42
jeblair#topic  TripleO Testing (TOCI) (pleia2)19:42
*** openstack changes topic to "TripleO Testing (TOCI) (pleia2) (Meeting topic: infra)"19:42
*** timello has joined #openstack-meeting19:42
pleia2not a ton of news, but I can now boot the dib-created image in LXC19:42
mordredwhee!19:42
clarkbpleia2: does that perform much better?19:42
pleia2working out some networking issues now for proper testing to make sure all the pieces actually work19:42
* anteaya applauds19:42
pleia2(I have dnsmasq chaos happening on my desktop right now)19:43
mordredmmm. desktop dnsmasq makes everything better19:43
pleia2clarkb: yeah, lxc is zippy on hpcloud :)19:43
pleia2that's it for now19:44
jeblair#topic open discussion19:44
*** openstack changes topic to "open discussion (Meeting topic: infra)"19:44
jeblairBobBall: ?19:44
* BobBall peers round the corner19:44
BobBallhi :)19:44
BobBallSo - I sent an email to the list a few days ago about XenServer gating trunk19:44
BobBallI just wanted to pop in to have a chat with a few of you to see what you thought the best way forward was19:44
BobBalland what I can do to make some progress :)19:45
fungiwhat platform requirements would the tests have?19:45
fungias compared with the current qemu-based testing i mean19:45
BobBallWe can run on the RS cloud - but I've not tested on the HP cloud (XenServer on top of KVM would be ... interesting!)19:45
*** mkollaro has joined #openstack-meeting19:46
pleia2BobBall: actually, it would be interesting if that worked (kvm on kvm doesn't work), I can test if you have some instructions for how I'd go about it19:46
pleia2^^ in hpcloud19:46
BobBallperhaps I don't understand enough about the current system - what do you mean by qemu based?19:46
uvirtbotpleia2: Error: "^" is not a valid command.19:46
mordredso, dprince has automation around doing this we can look at, right?19:46
BobBalldprince's automation is running on physical19:47
mordredalso, we need a xenserver instance to exist outside of the context of the openstack install, correct?19:47
jeblairBobBall: we're currently only running the devstack-gate tests on hpcloud because rs got very slow a while back... i think we saw something like 150% of hpcloud's runtime...19:47
clarkbjeblair: > 200% in many cases19:47
*** alexpilotti has quit IRC19:47
mordredI wonder what xenserver on top of xenserver performance in rax cloud would look like?19:48
BobBallpleia2: Sure thing - got an email addr I can send some details to?  It's basically "install and set tgt=off" for XS but I don't know what'd work for KVM.  It's running under Qemu in both cases, with no PV, so it _should_ work...19:48
pleia2BobBall: lyz@princessleia.com - thanks!19:48
BobBallPerformance wouldn't be great - disk access and network would be emulated rather than PV but we might be able to mitigate with a small ram disk for the SR19:49
mordredBobBall: I have no idea what PV or SR mean19:49
clarkbdoes xenserver require licensing?19:49
BobBalland yes, mordred, nova runs in a VM for a XenServer install - might make it easy(?) to re-use VMs rather than install XS each time19:49
BobBallno clarkb - no licensing - Free edition does everything that's needed and as of the next version of XenServer there will be no paid-for licenses (within the month)19:50
pleia2cool19:50
mordredBobBall: I think we're going to need to learn more about XenServer19:50
fungigot it. so this wouldn't necessarily be an all-in-one devstack vm with xenserver installed in the same base vm i guess19:50
mordredBobBall: part of the problem I'm having right now is that I'm asking questoins based on words I've heard people say in passing19:50
BobBallNo problem at all :)19:50
BobBallThere are other options too that we might consider19:51
mordredthat's an excellent question from fungi - is this something accomplishable via devstack?19:51
mordredin an all-in-one? or is this something that our other work on multi-machine deployments might be needed for?19:51
BobBallI'm mainly interested in XenAPI - XenServer is the ideal, but we can also install XenAPI-like packages on many other bases (e.g. CentOS, Ubuntu etc)19:51
BobBallYes, devstack installs on XS - but it takes a while because it sets up a Ubuntu VM19:51
fungii was more wondering whether xenserver can be integrated within devstack itself19:52
fungiin other words, can xenserver run within a devstack machine19:52
mordredwell, I know lifeless has a todo list item to talk to rackspace about getting their xenserver install done via tripleo19:52
BobBallI don't see a reason why not fungi19:52
BobBallnot tested that though19:52
mordredso, it's entirely possible that we might have a decent story for how this works once we have a story for how testing anything via tripleo works19:52
BobBallbut after all it's just a VM running in qemu!19:52
fungiin which case we already have a way to roll devstack onto a vm and run things and gate on that19:53
pleia2mordred: yeah, I'm thinking this is all closely related19:53
mordredpleia2: yes. I think I'd like to avoid solving this as a special case19:53
mordredpleia2: and instead deal with it as part of the general case19:53
* pleia2 nods19:53
BobBallYeah - I read the comments about tripleo but I didn't really understand the bigger picture of how it fitted together :)19:53
lifelesspleia2: cool news19:53
mordredlifeless: any thoughts on the above re: xenserver?19:54
lifelessmordred: quick synopsis?19:54
mordredlifeless: BobBall wants to test xenserver in the gate19:54
mordredlifeless: there are logistical issues (we need to install xenserver somewhere)19:54
mordredlifeless: and it seems like somethign that we might want to solve as an iteration of pleia2's work on tripleo testing19:55
BobBallinstall either as VM or physical19:55
lifelesscool; both devstack and bootstack will require a VM with a XenServer image in it to do that.19:55
lifelessor a physical machine with ditto19:55
*** michchap has joined #openstack-meeting19:55
mordredyah19:55
lifelesstripleo is probably a better harness for doing it on physical19:55
mordredwell, let's leave physical machien out of the loop for now19:55
lifelessas we're targeting that end2end19:55
jeblairmordred: so devstack-gate supports multiple image types...19:55
*** topol has quit IRC19:55
jeblairmordred: perhaps it's a matter of doing this: https://wiki.openstack.org/wiki/XenServer/InstallDebianUbuntu#Installing_XCP_on_Ubuntu_12.0419:55
lifelessdevstack knows how to setup such a VM already I think? If so thats the lowest cost path to get going.19:56
BobBallhmmm - just thinking out loud... it should be quite easy to generate an image that has an installed XS with a prepared devstack VM (minus the repos of course) already installed... Then that can just be restored, started, and it's all ready19:56
mordredBobBall: well, we have machinery to do image saving and all of that19:57
jeblairBobBall: the devstack-gate tests run devstack on prepapred images...19:57
mordredthe thing we need to sort is what content are we putting in to the images we're going to boot in the cloud and whatnot19:57
*** marun has quit IRC19:57
BobBallI see19:57
jeblairBobBall: the test itself runs devstack because we want that to be part of the test19:57
lifelessmordred: so my thoughts are that it doesn't seem all that coupled to tripleo||devstack, other than like tripleo it wants a different content on the root image19:57
*** ayoung has quit IRC19:57
lifelessmordred: and tripleo thanks to lxc doesn't need that anymore.19:57
mordredagree19:58
mordredI thought it was more complex originally19:58
jeblairBobBall: but we prepare images for it by caching things devstack needs onto it19:58
*** colinmcnamara1 has quit IRC19:58
BobBallunderstood19:58
jeblairBobBall: I believe we could also prepare a variant with xen already installed19:58
jeblairBobBall: so then the test would be "spin up vm from previously prepared image with xen installed.  run devstack.  run tempest"19:59
*** Tross has joined #openstack-meeting19:59
jeblairBobBall: would that general approach work?19:59
mordredyup. the main question will be around performance19:59
mordredof running that image that has xen installed on a vm in the cloud19:59
* olaph pretends to be a timer. ding!19:59
jeblairBobBall: https://github.com/openstack-infra/devstack-gate/blob/master/README.rst20:00
mordredbut I think it's a worthwhile path forward to investigate20:00
BobBallyes - with one minor comment - as I said, with devstack running in a VM under Xen we'd need to set that VM up too and include it in the base image20:00
*** Tross has quit IRC20:00
*** marun has joined #openstack-meeting20:00
jeblairBobBall: you may want to read that to familiarize yourself with devstack-gate's process20:00
*** pcm__ has quit IRC20:00
fungii think we can go over if we want, since i believe ttx cancelled the tc meeting (that's what would be following this, right?)20:00
jeblairBobBall: okay, i think i'm missing something because it sounds like you're talking about an extra level of virtualization than i'm considering20:00
BobBallok - so what actions do I need to take?  1) email pleia2 with how to test XS on HP's cloud, 2) read up on devstack-gate's process, 3) test performance of tempest in RS cloud20:01
*** zaneb has joined #openstack-meeting20:01
*** colinmcnamara has joined #openstack-meeting20:01
clarkbBobBall: well we already know the performance and we won't be able to gate on it. I think we need to see what we can do with hp cloud20:01
*** marun has quit IRC20:01
BobBalljeblair: XenAPI is installed on the base OS (which could be virtual), but nova and the rest of devstack run in a VM on that host20:01
clarkbunless xen makes everything magically faster20:01
pleia2clarkb: yeah20:02
mordredBobBall: why do they run in a vm?20:02
BobBallclarkb: I meant the relative degredation of having xen virtualised for the tempest tests20:02
mordredcan xenapi and nova and the rest of devstack not both run on the same host?20:02
jeblairBobBall: why do they run in a vm on that host?  the current system just runs devstack+nova on the cloud host.20:02
lifelessmordred: its' not the xen way20:03
BobBallThere are a number of reasons we run in a VM - in theory we could run in dom0, yes, but that'd need quite a few changes.  Things like mounting the VMs disks is easier in a VM rather than dom0 - although doable20:03
lifelessmordred: you have a privileged vm instead AIUI20:03
BobBallthe biggest reason is historical I'm afraid20:03
mordredok. so that sounds lke it's more work20:03
BobBall*nod*20:03
mordredbecause all of a sudden we're back to running devstack in a vm on the host that we're running on20:04
mordredwhich our automation does not do right now20:04
BobBallahhh - understood20:04
*** Tross has joined #openstack-meeting20:04
jeblairmordred: that's what lead you to think tripleo was a fit?20:04
mordredyes20:04
mordredbecause it's a similar problem space of layers20:04
mordrednot that we need tripleo for xen20:04
BobBallSo - in summary of that - it would be significantly easier if devstack+nova were running in dom020:05
jeblairmordred: yeah, in that case, i think pleia2's work would help, but if it could run in dom0, then it would be a pretty trivial devstack-gate change20:05
*** michchap has quit IRC20:05
mordredyes to both of you20:05
BobBallWe would definitely need xen-api changes to handle that, but it's eminently doable20:06
jeblairmordred: (in fact, i think devananda added the hook for that already)20:06
mordredso, let's have the takeaways be that BobBall and pleia2 talk about xenserver some more20:06
pleia2great20:06
mordredthat BobBall learn a little bit about devstack-gate20:06
BobBall*nod*20:06
mordredand that all of us brainstorm a little bit20:06
clarkbsounds good20:06
jeblair++20:06
fungiagreed20:06
BobBallWorks for me20:06
mordredwhee!20:06
anteayais BobBall attending the infra bootcamp?20:06
BobBallSounds like I've got a fun week!20:06
mordredBobBall: are you attending the infra bootcamp?20:07
BobBallI get the feeling that I should have been paying more attention when you were talking about the bootcamp earlier20:07
*** adalbas has quit IRC20:07
BobBallI'd like to say yes - this is an important thing for us20:07
BobBallso I'll look into it with a very probable yes20:08
*** tayyab has joined #openstack-meeting20:08
mordredcool. tl;dr - June 27/28 NYC - the aim is to get people bootstrapped with the knowledge they need to start being core contributors to openstack infra20:09
BobBallWow - I'd get a trip to NYC out of it too! Now I'll definitely push for it.20:09
clarkbha20:09
*** adalbas has joined #openstack-meeting20:10
jeblairthanks everyone!20:10
jeblair#endmeeting20:10
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"20:10
openstackMeeting ended Tue Jun 11 20:10:18 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:10
openstackMinutes:        http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-06-11-19.01.html20:10
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-06-11-19.01.txt20:10
openstackLog:            http://eavesdrop.openstack.org/meetings/infra/2013/infra.2013-06-11-19.01.log.html20:10
BobBallThanks for all your help guys - and for overrunning!20:10
*** ayoung has joined #openstack-meeting20:11
*** writerDiane has quit IRC20:11
*** boris-42 has quit IRC20:15
*** atiwari has quit IRC20:15
*** dolphm has quit IRC20:17
*** vipul|away is now known as vipul20:18
*** dprince has quit IRC20:19
*** gyee has quit IRC20:20
*** timductive has joined #openstack-meeting20:23
*** marun has joined #openstack-meeting20:25
*** colinmcnamara has quit IRC20:26
*** timello has quit IRC20:28
*** seanrob has quit IRC20:28
*** seanrob has joined #openstack-meeting20:28
*** dolphm has joined #openstack-meeting20:31
*** michchap has joined #openstack-meeting20:32
*** jcru has joined #openstack-meeting20:33
*** seanrob has quit IRC20:33
*** egallen has joined #openstack-meeting20:34
*** timello has joined #openstack-meeting20:34
*** danwent has quit IRC20:36
*** marun has quit IRC20:36
*** marun has joined #openstack-meeting20:37
*** leandrorosa has quit IRC20:38
*** seanrob has joined #openstack-meeting20:39
*** noslzzp has joined #openstack-meeting20:40
*** seanrob_ has joined #openstack-meeting20:42
*** seanrob has quit IRC20:42
*** seanrob_ has quit IRC20:42
*** seanrob has joined #openstack-meeting20:42
*** mkollaro has quit IRC20:43
*** lpabon has quit IRC20:44
*** kchenweijie1 has joined #openstack-meeting20:44
*** michchap has quit IRC20:45
*** kchenweijie1 has quit IRC20:45
*** kchenweijie1 has joined #openstack-meeting20:46
*** danwent has joined #openstack-meeting20:46
*** kchenweijie1 has quit IRC20:48
*** kchenweijie has joined #openstack-meeting20:48
*** mtreinish has quit IRC20:48
*** seanrob has quit IRC20:53
*** seanrob has joined #openstack-meeting20:54
*** spzala has quit IRC20:55
*** kevinconway has joined #openstack-meeting20:56
*** kevinconway has left #openstack-meeting20:56
*** neelashah has quit IRC20:57
*** seanrob has quit IRC20:58
*** kchenweijie has left #openstack-meeting20:58
*** stevebaker is now known as stevebaker_20:59
ttxReminder: no release/status meeting this week.20:59
*** zyluo has quit IRC21:01
*** seanrob has joined #openstack-meeting21:02
*** dolphm has quit IRC21:03
*** sdake has quit IRC21:05
*** Banix has quit IRC21:05
*** rnirmal has quit IRC21:06
*** sdake has joined #openstack-meeting21:08
*** sdake has quit IRC21:08
*** sdake has joined #openstack-meeting21:08
*** michchap has joined #openstack-meeting21:11
*** timello has quit IRC21:11
*** neelashah1 has joined #openstack-meeting21:12
*** tayyab has quit IRC21:12
*** abhisri has quit IRC21:14
*** anniec has joined #openstack-meeting21:15
*** dhellmann is now known as dhellmann-away21:17
*** flaper87 has quit IRC21:18
*** marun has quit IRC21:18
*** marun has joined #openstack-meeting21:19
*** mrunge has quit IRC21:19
*** stevemar has quit IRC21:21
*** olaph has left #openstack-meeting21:21
*** markmcclain has quit IRC21:21
*** michchap has quit IRC21:22
*** tedross has quit IRC21:23
*** whenry has joined #openstack-meeting21:23
*** litong has quit IRC21:24
*** BobBall has quit IRC21:24
*** rwsu has joined #openstack-meeting21:24
*** markmcclain has joined #openstack-meeting21:26
*** timello has joined #openstack-meeting21:29
*** jang1 has left #openstack-meeting21:31
*** atiwari has joined #openstack-meeting21:32
*** jasondotstar has quit IRC21:36
*** atiwari has quit IRC21:43
*** eharney has quit IRC21:44
*** gyee has joined #openstack-meeting21:44
*** HenryG has joined #openstack-meeting21:45
*** ilyashakhat_ has quit IRC21:46
*** maoy has quit IRC21:47
*** ilyashakhat has joined #openstack-meeting21:48
*** afazekas has quit IRC21:49
*** whenry has quit IRC21:49
*** michchap has joined #openstack-meeting21:49
*** lbragstad has quit IRC21:53
*** davidkranz has quit IRC21:56
*** kspear has joined #openstack-meeting21:58
*** rickerc_ has joined #openstack-meeting22:00
*** michchap has quit IRC22:01
*** dcramer_ has quit IRC22:03
*** markvoelker has quit IRC22:04
*** rickerc has quit IRC22:04
*** kashyap has quit IRC22:04
*** markvoelker has joined #openstack-meeting22:05
*** adalbas has quit IRC22:05
*** rickerc has joined #openstack-meeting22:05
*** marun_ has joined #openstack-meeting22:06
jpichNo sign of the chair. Is anyone else around for the Horizon meeting?22:06
lchengo/22:07
kspearjpich: Hi, around, but don't have anything in particular to talk about22:07
*** kashyap has joined #openstack-meeting22:07
*** jecarey has quit IRC22:07
*** rickerc_ has quit IRC22:07
*** anniec has quit IRC22:07
jpichHey there! I think I have one tiny thing to bring up, let's have a quick one then, maybe someone else will jump in too22:07
*** marun_ has quit IRC22:07
*** alexpilotti has joined #openstack-meeting22:07
*** marun has quit IRC22:07
kspeargo for it22:07
david-lyleo/22:07
jpich#startmeeting horizon22:08
openstackMeeting started Tue Jun 11 22:08:01 2013 UTC.  The chair is jpich. Information about MeetBot at http://wiki.debian.org/MeetBot.22:08
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:08
*** openstack changes topic to " (Meeting topic: horizon)"22:08
openstackThe meeting name has been set to 'horizon'22:08
jpichHi everyone, thanks for being here with us today22:08
jpich#topic Blueprints and bugs22:08
*** Tross has quit IRC22:08
*** openstack changes topic to "Blueprints and bugs (Meeting topic: horizon)"22:08
*** ladquin_brb is now known as ladquin22:08
*** marun has joined #openstack-meeting22:08
jpichOk, the main thing I wanted to bring up is on behalf of mrunge, who doesn't seem to be online anymore22:08
jpichthere are a couple of very big cleanup patches that have been submitted, mostly about cleaning up the imports22:09
jpichIt probably would be nice for the authors if we could make an effort at reviewing them quickly enough, so they don't have to be rebased which would probably be a misery22:10
jpich...Anything else relating to bugs and blueprints?22:11
* jpich unfortunately not on top of reviews at the moment so no other comments22:11
*** SergeyLukjanov has quit IRC22:12
lchengI am still working on the v3 auth support for keystone-client.  This is blocking the https://blueprints.launchpad.net/horizon/+spec/login-domain-support22:12
lchengIt is currently in review, but probably will still be awhile before it gets merged.  Quite a number of files to review.22:13
*** alexpilotti has quit IRC22:13
lchengThat's all from my side.22:13
jpichSounds good! We're just starting havana-2 so I'd assume it'll still be good for this milestone, hopefully22:14
david-lyleand I have the domain context support bp done except for a few more unit tests22:15
david-lylenext day or so22:15
jpichyay unit tests :-)22:15
david-lylethen hopefully I can catch up on reviews22:15
jpichCool22:16
david-lyleis the ceilometer integration to trunk in progress?22:16
jpichdavid-lyle: It's available at https://github.com/yuanotes/horizon/tree/ceilometer22:16
david-lylethanks!22:17
jpichI had a look last week, it looks like it should be submittable through gerrit soon (added a few review comments on the blueprint)22:17
david-lyleeven better :)22:17
jpichI'm not sure what's the best way to review something that's not in gerrit yet22:17
jpichhttps://blueprints.launchpad.net/horizon/+spec/ceilometer22:17
david-lyleseems a work in progress submission to gerrit would be easier22:18
jpichdavid-lyle: Feel free to have a look too, my devstack ceilometer self-destructed along the way so I couldn't really look at how it works, only what I assume the code does :-)22:18
jpichI find multiple commits in a series like that can be awkward to review as well though22:19
jpichThe git history can definitely be improved with a bit of squashing in this case. We'll see how it goes, I agree we should get it in gerrit soon22:19
*** matiu has joined #openstack-meeting22:19
jpich#topic Open discussion22:20
*** openstack changes topic to "Open discussion (Meeting topic: horizon)"22:20
*** Swami has joined #openstack-meeting22:20
jpichIf anyone has anything somewhat Horizon related they'd like to bring up, go for it22:20
david-lyleany strong opinions re: HACKING.rst?22:22
*** markvoelker has quit IRC22:22
david-lyleI know there are some patches moving in that direction22:22
jpichNot particularly. It looks like it should help make things more consistent?22:23
jpichThat's the way the consensus seemed to go on the mailing list, yeah. Do you have concerns?22:23
*** anniec has joined #openstack-meeting22:23
*** rostam has quit IRC22:23
david-lylenot really, just didn't really get a feel for a Horizon consensus22:23
*** neelashah1 has quit IRC22:24
*** mkollaro has joined #openstack-meeting22:25
*** fnaval has quit IRC22:25
*** rostam has joined #openstack-meeting22:25
jpichTrue. The general feeling seems to be that this increases the consistency with the other projects, and should help with rebases and style consistency22:26
david-lyleanything to helps reduce rebases is certainly a plus22:26
kspeari'm not too fond of "import only modules" when it comes to classes22:27
kspearand i think we should talk about new-style relative imports at some point22:28
*** vijendar has quit IRC22:28
*** michchap has joined #openstack-meeting22:28
kspeari don't see the danger of the new-style22:28
david-lylenor do I22:29
jpichIf that's something that can/should be done as part of the patches for hacking.rst, it sounds like it would be worthwhile bringing up now22:29
kspearbecause of the nesting in openstack_dashboard our import lines can get huge22:29
jpichas a bug or a ML dicussion?22:29
kspeari'll add a reply to the ML discussion22:29
kspearit is important we stay reasonably consistent with the rest of openstack22:30
kspearso would be good to get consensus on it22:30
jpichthanks kspear22:30
clarkbis anyone interested in implementing/fixing https://bugs.launchpad.net/horizon/+bug/1177924 ? we (the CI team) are trying to testr all of the projects where it makes sense (and currently we think that is true for just about all of them). gabrielhurley did some preliminary investigation I think and I would be happy to help someone fix that22:30
uvirtbotLaunchpad bug 1177924 in cinder "Use testr instead of nose as the unittest runner." [Medium,In progress]22:30
*** timductive has left #openstack-meeting22:30
kspearclarkb: I looked into that briefly22:30
kspearseems we need a django test runner that runs testr?22:31
clarkbkspear: are you using a django test runner or just nose?22:31
clarkbI thought you guys were just running nose22:31
kspearwe use django_nose22:31
kspearwhich does the same thing for nose22:31
kspearit's a test runner that runs nose22:31
*** cp16net is now known as cp16net|away22:32
clarkbI see22:32
*** cp16net|away is now known as cp16net22:32
kspearthe test runner is important because there's special django setup that needs to be done22:32
lifelesswhich is a massive django bug :)22:32
lifelessanyhow, what you need is a custom runner that will glue a subunit result object in, which is about 10 lines.22:33
*** topol has joined #openstack-meeting22:33
kspearlifeless: can you help with that?22:33
*** changbl has quit IRC22:33
kspeari don't have any experience with testr/subunit22:33
lifelesskspear: I can certainly advise22:34
lifelessits been a while since I actively poked at django22:35
kspearlifeless: thanks. well i'll see how far I get, couldn't see see any examples on the web of where this has been done before22:36
lifelesskspear: if you look at the source for subunit.run it should be pretty obvious:22:36
lifelesswhere you do suite.run(result), result should be a testtools.ExtendedToStreamResult(subunit.v2.StreamResultToBytes(sys.stdout))22:37
kspearlifeless: okay, will do.22:37
*** gyee has quit IRC22:37
*** markvoelker has joined #openstack-meeting22:37
lifelesskspear: + you need to implement the list-tests and load-list features, to let testr enumerate and select tests to run.22:37
*** gyee has joined #openstack-meeting22:38
lifelesskspear: http://testrepository.readthedocs.org/en/latest/MANUAL.html#listing-tests and http://testrepository.readthedocs.org/en/latest/MANUAL.html#running-tests22:38
kspearlifeless: cool, thanks for the pointers22:39
lifelesskspear: so you should be able to keep your current django suite stuff (per https://docs.djangoproject.com/en/1.2/topics/testing/#defining-a-test-runner) and just override the result, plus add teh load-and-list facilities.22:39
lifelesskspear: please reach out on any issues22:40
*** mdomsch has joined #openstack-meeting22:40
kspearlifeless: will do, thanks22:40
*** michchap has quit IRC22:40
*** mkollaro has quit IRC22:41
jpichCool, thanks22:42
jpichAnything else from anyone?22:42
*** vipul has quit IRC22:42
*** vipul has joined #openstack-meeting22:43
*** derekh has quit IRC22:44
jpichThank you everyone, have a nice day/afternoon/evening/night :)22:45
jpich#endmeeting22:45
*** lastidiot1 has quit IRC22:45
*** openstack changes topic to "OpenStack meetings || https://wiki.openstack.org/wiki/Meetings"22:45
openstackMeeting ended Tue Jun 11 22:45:09 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)22:45
openstackMinutes:        http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-06-11-22.08.html22:45
*** whenry has joined #openstack-meeting22:45
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-06-11-22.08.txt22:45
openstackLog:            http://eavesdrop.openstack.org/meetings/horizon/2013/horizon.2013-06-11-22.08.log.html22:45
*** SlickNik has left #openstack-meeting22:45
kspearthanks jpich, have a good week everyone22:45
david-lylethanks jpich22:45
*** cody-somerville has joined #openstack-meeting22:46
*** cody-somerville has joined #openstack-meeting22:46
*** kspear has quit IRC22:47
*** morganfainberg has left #openstack-meeting22:47
*** sushils has joined #openstack-meeting22:47
*** jpich has quit IRC22:47
*** atiwari has joined #openstack-meeting22:48
*** jcru is now known as jcru|away22:50
*** jcru|away is now known as jcru22:50
*** markmcclain has quit IRC22:51
*** sushils has quit IRC22:51
*** egallen has quit IRC22:52
*** HenryG_ has joined #openstack-meeting22:52
*** henrynash has quit IRC22:53
*** sushils has joined #openstack-meeting22:53
*** HenryG has quit IRC22:56
*** zehicle_at_dell has quit IRC22:56
*** mkollaro has joined #openstack-meeting23:00
*** marcosmamorim has quit IRC23:03
*** michchap has joined #openstack-meeting23:06
*** danwent has quit IRC23:08
*** whenry has quit IRC23:13
*** huats_ has joined #openstack-meeting23:13
*** huats_ has quit IRC23:13
*** huats_ has joined #openstack-meeting23:13
*** huats has quit IRC23:14
*** michchap has quit IRC23:18
*** lloydde has quit IRC23:21
*** david-lyle has left #openstack-meeting23:23
*** jcru is now known as jcru|away23:23
*** kebray has quit IRC23:26
*** dcramer_ has joined #openstack-meeting23:27
*** danwent has joined #openstack-meeting23:28
*** mdomsch has quit IRC23:29
*** krtaylor has quit IRC23:29
*** jcru|away is now known as jcru23:34
*** mrodden has quit IRC23:36
*** asalkeld is now known as gloomy23:39
*** otherwiseguy has quit IRC23:39
*** gloomy is now known as angus23:39
*** MarkAtwood has joined #openstack-meeting23:40
*** MarkAtwood has quit IRC23:42
*** lloydde has joined #openstack-meeting23:44
*** MarkAtwood has joined #openstack-meeting23:44
*** michchap has joined #openstack-meeting23:44
*** michchap has quit IRC23:45
*** michchap has joined #openstack-meeting23:46
*** ivasev has joined #openstack-meeting23:53
*** Swami has quit IRC23:55
*** atiwari has quit IRC23:56
*** hub_cap has joined #openstack-meeting23:57
*** mkollaro has quit IRC23:59

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