Monday, 2012-06-11

*** blamar has quit IRC00:05
*** ryanpetr_ has joined #openstack-meeting00:12
*** ryanpetrello has quit IRC00:15
*** danwent has quit IRC00:15
*** danwent has joined #openstack-meeting00:24
*** littleidea has joined #openstack-meeting00:43
*** danwent has quit IRC00:51
*** sdake has quit IRC00:59
*** sdake has joined #openstack-meeting01:00
*** danwent has joined #openstack-meeting01:07
*** ryanpetr_ has quit IRC01:36
*** cdub has quit IRC01:53
*** cdub has joined #openstack-meeting01:54
*** cdub has quit IRC01:59
*** Mandell has joined #openstack-meeting01:59
*** rnirmal has joined #openstack-meeting02:01
*** littleidea has quit IRC02:03
*** littleidea has joined #openstack-meeting02:08
*** danwent has quit IRC02:13
*** ryanpetrello has joined #openstack-meeting02:19
*** edygarcia has joined #openstack-meeting02:20
*** cdub has joined #openstack-meeting02:35
*** cdub has quit IRC02:40
*** danwent has joined #openstack-meeting02:44
*** edygarcia has quit IRC02:47
*** nati_ueno has joined #openstack-meeting03:24
*** cdub has joined #openstack-meeting03:29
*** cdub has quit IRC03:33
*** cdub has joined #openstack-meeting03:34
*** cdub has quit IRC03:41
*** nati_ueno has quit IRC03:44
*** cdub has joined #openstack-meeting03:46
*** nati_ueno has joined #openstack-meeting04:03
*** rnirmal has quit IRC04:30
*** jakedahn_zz is now known as jakedahn04:37
*** ryanpetrello has quit IRC04:42
*** nati_ueno has quit IRC04:46
*** nati_ueno has joined #openstack-meeting04:47
*** joearnold has joined #openstack-meeting04:50
*** garyk has joined #openstack-meeting04:58
*** joearnold has quit IRC05:18
*** joearnold has joined #openstack-meeting05:21
*** jakedahn is now known as jakedahn_zz05:37
*** dachary has joined #openstack-meeting05:47
*** joearnold has quit IRC05:59
*** danwent has quit IRC06:14
*** dachary has quit IRC06:19
*** littleidea has quit IRC06:54
*** bencherian has quit IRC07:13
*** Razique has joined #openstack-meeting07:26
*** dachary has joined #openstack-meeting07:37
*** bencherian has joined #openstack-meeting07:45
*** bencherian has quit IRC07:45
*** bencherian_ has joined #openstack-meeting07:46
*** Guest95641 is now known as Adri200008:15
*** Adri2000 has joined #openstack-meeting08:15
*** Adri2000 has quit IRC08:21
*** Mandell has quit IRC08:22
*** Adri2000 has joined #openstack-meeting08:23
*** Adri2000 has joined #openstack-meeting08:23
*** no`x has quit IRC08:23
*** bencherian_ has quit IRC08:34
*** no`x has joined #openstack-meeting08:39
*** darraghb has joined #openstack-meeting08:42
*** ttrifonov_zZzz is now known as ttrifonov08:48
*** no`x has quit IRC09:12
*** dachary has quit IRC09:53
*** no`x has joined #openstack-meeting10:34
*** milner has joined #openstack-meeting11:26
*** dprince has joined #openstack-meeting11:51
*** dwcramer has quit IRC11:53
*** dragondm has quit IRC11:57
*** dprince has quit IRC12:00
*** markvoelker has joined #openstack-meeting12:02
*** markvoelker has quit IRC12:02
*** markvoelker has joined #openstack-meeting12:02
*** dragondm_ has joined #openstack-meeting12:02
*** dragondm_ is now known as dragondm12:02
*** dprince has joined #openstack-meeting12:07
*** arosen has quit IRC12:27
*** dwcramer has joined #openstack-meeting12:39
*** littleidea has joined #openstack-meeting12:44
*** arosen has joined #openstack-meeting12:45
*** jaypipes has joined #openstack-meeting12:47
*** joesavak has joined #openstack-meeting12:47
*** sandywalsh has joined #openstack-meeting12:50
*** GheRivero has quit IRC12:50
*** edygarcia has joined #openstack-meeting12:50
*** edygarcia has quit IRC12:55
*** littleidea has quit IRC12:58
*** hggdh has quit IRC13:00
*** hggdh has joined #openstack-meeting13:12
*** littleidea has joined #openstack-meeting13:19
*** littleidea has quit IRC13:21
*** littleidea has joined #openstack-meeting13:26
*** littleidea has quit IRC13:28
*** hggdh has quit IRC13:32
*** littleidea has joined #openstack-meeting13:32
*** hggdh has joined #openstack-meeting13:33
*** oubiwann has joined #openstack-meeting13:35
*** dwcramer has quit IRC13:35
*** jsavak has joined #openstack-meeting13:39
*** ryanpetrello has joined #openstack-meeting13:42
*** joesavak has quit IRC13:42
*** littleidea has quit IRC13:43
*** edygarcia has joined #openstack-meeting13:47
*** Mandell has joined #openstack-meeting13:53
*** dabo has joined #openstack-meeting14:01
*** edygarcia has quit IRC14:02
*** dabo has left #openstack-meeting14:04
*** dabo has joined #openstack-meeting14:04
*** dwcramer has joined #openstack-meeting14:09
*** mattray has joined #openstack-meeting14:10
*** troytoman is now known as troytoman-away14:11
*** ayoung has joined #openstack-meeting14:12
*** littleidea has joined #openstack-meeting14:14
*** nikhil has joined #openstack-meeting14:18
*** littleidea has quit IRC14:19
*** GheRivero has joined #openstack-meeting14:20
*** littleidea has joined #openstack-meeting14:21
*** blamar has joined #openstack-meeting14:22
*** troytoman-away is now known as troytoman14:24
*** ryanpetrello has quit IRC14:25
*** ryanpetrello has joined #openstack-meeting14:25
*** edygarcia has joined #openstack-meeting14:39
*** danwent has joined #openstack-meeting14:48
*** Gordonz has joined #openstack-meeting14:49
*** matwood has joined #openstack-meeting14:49
*** rnirmal has joined #openstack-meeting15:11
*** bencherian has joined #openstack-meeting15:14
*** nati_ueno has joined #openstack-meeting15:36
*** nati_ueno has quit IRC15:36
*** joearnold has joined #openstack-meeting15:46
*** bencherian has quit IRC15:46
*** Razique has quit IRC15:47
*** darraghb has quit IRC15:53
*** lloydde has joined #openstack-meeting16:02
*** nati_ueno has joined #openstack-meeting16:07
*** darraghb has joined #openstack-meeting16:24
*** Mandell has quit IRC16:30
*** anderstj has joined #openstack-meeting16:31
*** anderstj has quit IRC16:32
*** anderstj_ has joined #openstack-meeting16:32
*** sleepsonzzz is now known as sleepsonthefloor16:35
*** dtroyer_zzz is now known as dtroyer16:38
*** Gordonz has quit IRC16:38
*** Gordonz has joined #openstack-meeting16:39
*** chrisfer has joined #openstack-meeting16:44
*** adjohn has joined #openstack-meeting16:44
*** darraghb has quit IRC16:54
*** ghe has joined #openstack-meeting16:55
*** darraghb has joined #openstack-meeting16:55
*** ghe is now known as Guest3595216:55
*** Guest35952 is now known as GheRivero_16:56
*** darraghb has quit IRC16:56
*** darraghb has joined #openstack-meeting17:01
*** jdurgin has joined #openstack-meeting17:05
*** littleidea has quit IRC17:05
*** darraghb has quit IRC17:05
*** garyk has quit IRC17:06
*** darraghb has joined #openstack-meeting17:06
*** jakedahn_zz is now known as jakedahn17:09
*** littleidea has joined #openstack-meeting17:13
*** PotHix has joined #openstack-meeting17:17
*** ncode has joined #openstack-meeting17:26
*** mattray has quit IRC17:33
*** GheRivero_ has quit IRC17:36
*** dendrobates is now known as dendro-afk17:38
*** darraghb has quit IRC17:39
*** garyk has joined #openstack-meeting17:39
*** GheRivero has quit IRC17:40
*** bencherian has joined #openstack-meeting17:40
*** littleidea_ has joined #openstack-meeting17:41
*** littleidea has quit IRC17:44
*** littleidea_ is now known as littleidea17:44
*** dolphm has joined #openstack-meeting17:49
*** DuncanT has joined #openstack-meeting17:58
*** dtroyer is now known as dtroyer_zzz17:59
*** dtroyer_zzz is now known as dtroyer17:59
*** matwood has quit IRC18:04
*** rnirmal has quit IRC18:10
*** Mandell has joined #openstack-meeting18:12
*** jakedahn is now known as jakedahn_zz18:14
*** rnirmal has joined #openstack-meeting18:17
*** troytoman is now known as troytoman-away18:21
*** mattray has joined #openstack-meeting18:22
*** johnpostlethwait has joined #openstack-meeting18:22
*** novas0x2a|laptop has joined #openstack-meeting18:29
*** jaypipes is now known as jaypipes-afk18:31
*** davidkranz has quit IRC18:39
*** davidkranz has joined #openstack-meeting18:41
*** matwood has joined #openstack-meeting18:43
*** troytoman-away is now known as troytoman18:44
*** davidkranz_ has joined #openstack-meeting18:44
*** davidkranz_ has quit IRC18:45
*** davidkranz_ has joined #openstack-meeting18:45
*** davidkranz has quit IRC18:46
*** anderstj_ has quit IRC18:47
*** romain_lenglet has joined #openstack-meeting18:49
*** rnirmal has quit IRC18:52
*** romain_lenglet has quit IRC18:52
*** rnirmal has joined #openstack-meeting18:52
*** rnirmal_ has joined #openstack-meeting18:55
*** littleidea_ has joined #openstack-meeting18:58
*** rnirmal has quit IRC18:58
*** rnirmal_ is now known as rnirmal18:58
*** jakedahn_zz is now known as jakedahn18:59
*** littleidea has quit IRC19:01
*** littleidea_ is now known as littleidea19:01
*** rnirmal has quit IRC19:14
*** mnewby has joined #openstack-meeting19:29
*** mnewby has quit IRC19:38
*** mnewby_ has joined #openstack-meeting19:41
*** mnewby_ has quit IRC19:42
*** mnewby has joined #openstack-meeting19:45
*** wabat has joined #openstack-meeting19:51
*** KarinLevenstein has joined #openstack-meeting19:52
*** rnirmal has joined #openstack-meeting19:53
*** troytoman is now known as troytoman-away19:56
*** ijw has joined #openstack-meeting20:00
annegentleokay, who's here for the doc team meeting?20:00
annegentleBeth sent her regrets20:01
annegentlejoesavak is busy today20:01
annegentledwcramer: around?20:01
KarinLevensteinI'm here.20:01
annegentlewoo~20:01
annegentlewabat: around?20:02
annegentleah, Mondays.20:02
annegentle:)20:02
wabatyes I am20:02
* ijw is sticking his nose in20:03
* dwcramer I'm here20:03
*** Ravikumar_hp has joined #openstack-meeting20:03
annegentlecool, let's get started! I'm going to skip Skype today if no one protests - okay?20:03
*** writerDiane has joined #openstack-meeting20:03
annegentlewelcome writerDiane!20:03
annegentle#startmeeting20:03
openstackMeeting started Mon Jun 11 20:03:58 2012 UTC.  The chair is annegentle. Information about MeetBot at http://wiki.debian.org/MeetBot.20:03
writerDianeHello!20:03
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.20:04
annegentleAgenda at http://wiki.openstack.org/Meetings/DocTeamMeeting20:04
annegentle#topic Action items from last meeting20:04
*** openstack changes topic to "Action items from last meeting"20:04
annegentleFirst one was Anne to send Beth draft "Learning OpenStack" document20:04
*** bcwaldon has joined #openstack-meeting20:04
annegentleDone - sent to Beth and wabat (Walter) for their review, they'll look at it this week for uses20:04
annegentleSecond was joe to review bps and cdt product roadmap and update bps accordingly20:04
annegentleI'm meeting with Joe Savak tomorrow and I'll follow up.20:05
annegentle: put a list of pertinent metadata into the blueprint20:05
annegentlenot sure who was the colon :)20:05
annegentlebut I added some20:05
annegentleDone - added three items to the blueprint:20:05
annegentlegit SHA, version of the plugin used to build the particular page, Name or ID of last contributor to the page20:05
annegentleI think those would be a great start.20:06
annegentle#link https://blueprints.launchpad.net/openstack-manuals/+spec/doc-metadata20:06
annegentlelast action - Anne to add individual blog posts to Google CSE20:06
annegentleDone - added the ones from http://wiki.openstack.org/BloggersTips. For example, if you search for virtualbox on docs.openstack.org, the fourth hit now is a blog post.20:06
annegentleI think I'm now two posts behind the list at BloggersTips but I think it's easily maintained.20:06
annegentleI can share the CSE credentials with anyone who wants to add more.20:07
annegentleand that's all for action items.20:07
annegentle#topic Nova config flags reviews20:07
*** openstack changes topic to "Nova config flags reviews"20:07
*** ClemSF has joined #openstack-meeting20:08
annegentleThis one went through on trunk: https://review.openstack.org/#/c/8182/ but is still "Review in Progress"20:08
annegentleand I'm not sure why. CI team thinks we never did +2 and +120:08
annegentleSame with https://review.openstack.org/#/c/8383/.20:08
annegentleNoting it here because there used to be redundant flag listings and those should've cleared them out.20:09
annegentleI guess I'll just Review to get those through.20:09
annegentle#topic Landing page changes20:10
*** openstack changes topic to "Landing page changes"20:10
annegentleSwitched from /trunk to /essex yesterday and sent a Mailing List post out. Seems well-received and I had gotten plenty of requests for it. :)20:10
annegentleSo, while last meeting we said we'd wait for divergence between essex and folsom, there was enough uprising requests that I did it at the month mark.20:10
annegentleHope that's okay with everyone.20:10
annegentleAh, benevolent dictatorship.20:10
annegentleI'd like to discuss whether to continue to post the Starter Guide on the landing page - it seems redundant now. I really appreciate the work that goes into it. But it's not an "official" doc.20:11
*** edygarcia has quit IRC20:11
annegentleThe Starter Guide is the Ubuntu 12.04 document from CSS OSS.20:11
annegentleI can ask them to rebrand it as "built for OpenStack" with the CSS OSS logo so that perceptions of it's "officialness" are clear.20:12
*** Guest42130 has quit IRC20:13
*** nikhil has quit IRC20:13
annegentle#action annegentle to investigate Starter Guide repurposing20:13
jsavak\o20:14
*** edygarcia has joined #openstack-meeting20:14
annegentlehey jsavak20:14
jsavakhiya!20:14
annegentlejsavak: thought your Monday was a wash for you, thanks for joining!20:14
*** nikhil has joined #openstack-meeting20:14
jsavakmeeting ended early.Don't tell anyone20:14
annegentleone last thought on the landing page switch - I can't figure out why the /essex guides PDF links point to -trunk.pdf file names.20:15
annegentleI need to log a bug about it cuz I'm stumped… the pom.xml should be substituting release.name20:15
annegentledwcramer: I'll probably ask you about it after this meeting20:15
annegentleany questions on the landing page?20:16
annegentle#topic New high availability guide draft20:16
*** openstack changes topic to "New high availability guide draft"20:16
annegentle#link https://review.openstack.org/#/c/8139/20:16
*** edygarcia_ has joined #openstack-meeting20:16
annegentleRight now it's just an introduction, he has added Pacemaker info into additional reviews set to "Work in Progress"20:17
annegentlePlease review and comment - I think it'll be a good addition.20:17
wabatI agree20:17
annegentlewabat: you'd be a good reviewer for that guide20:17
wabatI'll probably end up using the guide as well20:17
annegentleI'm also hoping it'll help readers understand the "production" guides and the "starter" guides differences.20:18
* annegentle may be asking too much20:18
annegentleany questions on HA guide?20:18
annegentle#topic Blueprints status20:18
*** openstack changes topic to "Blueprints status"20:18
*** edygarcia_ has quit IRC20:19
annegentleso… operations manual20:19
annegentleNotes are at http://etherpad.openstack.org/EssexOperationsGuide20:19
annegentle#link http://etherpad.openstack.org/EssexOperationsGuide20:19
*** edygarcia has quit IRC20:19
*** edygarcia_ has joined #openstack-meeting20:19
annegentleThere are troubleshooting links we can pull from20:20
annegentle#link http://bit.ly/ostsg20:20
annegentle#link http://networkstatic.net/2012/05/12/troubleshooting-common-openstack-errors/20:20
annegentlebut yes these are just bits and pieces.20:20
annegentleStill hoping to get at least an Operators Quick Start and Operations Management Practices and Day-to-Day Operations20:21
annegentlein time for Folsom20:21
annegentleI have shopped the outline around and folks like it20:21
annegentleso really it's "just" filling in between :)20:21
*** beraldo_ has joined #openstack-meeting20:21
annegentlethe HA guide should help with some of it20:21
annegentleany questions? comments? anyone progressing on it?20:22
wabatI'm trying to get the day to day stuff going.  I was hoping to get involved in the Trystack admin group but no movement on that yet.20:22
annegentlewabat: great - TryStack had a "pregnant" pause when Nati became a dad last week I think :)20:23
annegentlewabat: so definitely keep asking how you can get involved and I'll poke at them too20:24
annegentlewabat: also jaypipes started a new job20:24
annegentleTrystack leads me to another blueprint, a "Deployment template"20:24
annegentleI have talked to a wide variety of people on "what is the purpose of this document" and come up with different answers :)20:25
*** ClemSF_ has joined #openstack-meeting20:25
annegentleone answer is "document what TryStack does so others can understand a public deployment" the other is "configuration is still too wide and broad what do I do?"20:25
annegentleSo, a good discussion here is - which do you think the "deployment template" should do?20:25
jsavakcommon out of the box general settings & env variable guide?20:26
annegentlejsavak: yeah, that's the original thought, document a couple of deployments20:27
annegentlejsavak: no one "wants" out of the box :)20:27
annegentle#link http://wiki.openstack.org/RealDeployments20:27
jsavakyup20:27
annegentleI'm trying to scope this narrowly enough to get done but broadly enough to be useful20:28
*** ClemSF has quit IRC20:28
*** ClemSF_ is now known as ClemSF20:28
annegentle"get done" - get something done20:28
*** clarkb has quit IRC20:29
annegentlerather, "real config info" beyond nova flags20:29
annegentleI also hear, "Why" is more generally wanted than "What"20:29
annegentleSo, I'll keep working on this blueprint, but am still trying to define what doc could be useful. My sense right now is that TryStack needs to get updated to Essex, then we'll have better "why" to document.20:31
annegentlethird blueprint, API "try-it-out"20:31
annegentleI did not end up hiring an intern here at Rackspace for the summer. Sadness.20:31
annegentleFour candidates ended up taking other positions not-in-Austin.20:31
annegentleBut, I do have basic psuedocode and I think here also I want to wait on TryStack to upgrade to Essex.20:32
annegentlelast blueprint, "metadata in docs" - jsavak let's talk tomorrow about how to work that into a schedule20:32
jsavaksure20:33
annegentlecool20:33
*** Ravikumar_hp has quit IRC20:33
annegentleok, last topic20:33
annegentle#topic Doc tools updates20:33
*** openstack changes topic to "Doc tools updates"20:33
*** beraldo_ has quit IRC20:33
annegentle#info Testing begins on Chinese language documents working with cloud doc tools maven plugin20:33
annegentleSetting language to zh should work in PDF builds now.20:34
annegentle#link https://bugs.launchpad.net/openstack-manuals/+bug/98058020:34
*** edygarcia_ has quit IRC20:34
uvirtbotannegentle: Error: Could not parse data returned by Launchpad: HTTP Error 503: Service Unavailable20:34
annegentlesend us your chinese docbook source so we can test20:34
chrisferoh, cool20:34
annegentlethe person who logged the bug can hopefully test against her source20:34
annegentlechrisfer: yeah!20:35
chrisferI'll let Daisy know20:35
annegentlechrisfer: hopefully Daisy got notification on that bug update20:35
annegentlechrisfer: better yet, thanks!20:35
*** edygarcia has joined #openstack-meeting20:35
annegentleanother good trick - use <?sbr?> processing instruction for a break in a table cell20:35
annegentlethat was helpful for all the nova.conf options listings20:36
*** markvoelker has quit IRC20:36
annegentleand then I also learned that Jenkins can't access the plugin builds with -SNAPSHOT for some reason, so I back ported fixes to the stable/diablo branch so Jenkins can build again20:36
annegentlenot that diablo is getting updated all that often, but it's a good best practice going forward.20:37
annegentlethe latest clouddoctools plugin version is 1.3.1, and you can test against 1.4.0-SNAPSHOT20:37
annegentleany questions on the doc tools?20:37
chrisferannegentle: I sent her a note - she is in class until Weds I think, but maybe someone on the team can test20:37
annegentlechrisfer: great, thanks20:37
annegentle#topic Open discussion20:38
*** openstack changes topic to "Open discussion"20:38
annegentleAnything else on your minds?20:38
annegentle(well, that's doc-related)20:38
ijwI had a question on api.openstack.org20:38
annegentleijw: sure, go ahead20:38
ijwIt's a bit of an open question, so bear with me20:39
annegentleno worries20:39
ijwIs it going to turn into a definitive description of the API, or is it just supposed to be some helpful ideas without being comprehensive?20:39
annegentleijw: I'd like it to document trystack.org, an actual implementation.20:40
annegentleijw: it's hard to define comprehensive… what would that look like to you?20:40
ijwThe reason I ask is that at the moment it's a bit sketchy when it comes to the posted information.  It lists a set of parameters, and then a chunk of JSON/XML that you can post.  Firstly, I'm not quite sure how the two relate. And secondly, it's not clear if the JSON lists *all* of the possible options that can be used, or whether it just lists one valid set of options.20:41
annegentleijw: for certain the JSON is just one valid set of options… hm, how could the examples be expanded to show more examples?20:42
annegentleijw: ideally the JSON/XML are all working samples - they should be as far as I know. Log bugs if they're not.20:42
annegentleijw: I think a "try it out" implementation might help with getting more possible options - let the user pull more switches, you know?20:43
*** edygarcia has quit IRC20:43
ijwWell, it'd be nice if there was a go-to definitive reference for what the API is, you see - I wasn't sure if the api.openstack.org site was going to be that.  And to be a full document in that sense it has to list all of the available knobs and switches that are there and what they can be set to.20:43
*** joearnold has quit IRC20:44
annegentleijw: I'd like it to be the go-to. then we move the "dev guides" into more developer guide mode, instead of "specs"20:44
annegentleijw: want reality :)20:44
ijwYeah, do you want all of reality? ;)20:44
annegentleijw: heh, not really if I only want to limit the scope to TryStack :)20:45
ijwCos I think we need all of reality, somewhere, eventually.20:45
annegentleijw: there's still talk of an extensions registry too, which would be more of reality20:45
annegentleijw: but yes, we NEED reality :)20:45
annegentleijw: thanks for asking20:46
chrisferI think I can see ijw's point20:46
chrisfershouldn't the various fields be fully documented?20:46
ijwIndeed, but even docs on the base API would be really helpful.  I'm speaking from a hacking the source perspective here, but the API is where developers and app designers meet and so it would be a good idea to have something that documents it extensively.20:46
ijwchrisfer: absolutely, that's the sort of thing I'm talking20:46
chrisfereg. v1.1/{tenant_id}/servers/detail status(optional)20:47
*** ClemSF has quit IRC20:47
*** edygarcia has joined #openstack-meeting20:47
*** ClemSF has joined #openstack-meeting20:47
chrisfershouldn't it provide the valid range of values that may be set?20:47
ijwAnd perhaps explain what those values mean...20:47
chrisferthat makes sense then20:47
chrisferexactly20:47
ijwWith apologies, cos that's obviously a lot of work ;)20:48
annegentleagree - how do we track what's still missing?20:48
chrisferand if there are constraints (e.g. for date format) then be explicit20:48
ijwWell, perhaps the best way to start would be to take a simple GET and a simple-ish POST and document them extensively to see how the whole thing would look.20:48
ijw(Emphasis on simple, because e.g. creating a server has a lot of knobs you can twiddle)20:49
annegentle#link http://heckj.github.com/api-site-mock/20:49
annegentlewe started with the above site mockup20:49
annegentleI wonder if we can mock up further?20:49
annegentlewriterDiane may have more details as well20:50
writerDianeyes, i'm working on a content model for api refs20:50
writerDianeapi ref pages20:50
*** rkukura has joined #openstack-meeting20:50
annegentleijw: could writerDiane send you a mockup of the details for "create server" to see if it covers what you're seeking?20:50
annegentleijw: your input is super valuable20:51
*** edygarcia has quit IRC20:51
ijwYeah, fine with me20:51
writerDianelet me know where to send - i can send it to you with mockup for create server20:51
annegentleok, great20:51
annegentle#action writerDiane to send mockup to ijw20:51
chrisferwriterDiane: this mock-up looks about right20:51
annegentlechrisfer: it's pretty low-detail though :) and no content reall20:52
annegentlereally20:52
chrisferI would again suggest that where applicable, that valid value ranges (or enums) be made explicit in the api doc20:52
annegentlechrisfer: ok, that would be a good addition20:52
chrisferwell, some include the narrative, which is goodness20:52
annegentleok, any other discussion?20:53
chrisferthink each should be accompanied by a narrative that 'splains what it is for, etc20:53
ijwParameters need describing by where they go, too - some are querystring, some in JSON, some in the URL path...20:53
annegentlechrisfer: so I think that the narrative belongs in a "Dev Guide" - not on a reference listing page, right?20:53
annegentleshort content verses long content20:54
ijwBut yeah, all detail, and all for later.20:54
writerDianeyes, i'd say the narrative belongs in dev guide20:54
writerDianemy api template covers all that - query parameters, header parms, etc -20:54
ijwannegentle, writerDiane: would be nice if the actual bits of information lived in one place and the different guides were generated from it, perhaps; I've no idea if we can do that...20:55
annegentleijw: that's the plan - WADL generates api.openstack.org, then we put the WADL in the dev guide too so it's all one source of truth. So glad you agree. :)20:56
ijwI've done this sort of stuff before.  There's nothing quite so horrifying as keeping umpteen Word documents in sync. ;)20:56
annegentleijw: bleeerrrrg.20:56
annegentle:)20:56
*** Salv-orlando has joined #openstack-meeting20:57
annegentleok, I'll wrap it up now - thanks all for coming20:57
annegentle#endmeeting20:57
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"20:57
openstackMeeting ended Mon Jun 11 20:57:38 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)20:57
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-11-20.03.html20:57
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-11-20.03.txt20:57
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-11-20.03.log.html20:57
*** bcwaldon has left #openstack-meeting20:57
*** writerDiane has left #openstack-meeting20:57
*** s0mik has joined #openstack-meeting20:58
*** KarinLevenstein has left #openstack-meeting20:58
*** jjm3lp has joined #openstack-meeting20:58
annegentleall yours, danwent20:58
danwentannegentle: thanks :)20:58
annegentle:)20:58
*** markvoelker has joined #openstack-meeting21:00
danwenthi folks21:00
PotHixo/21:00
Salv-orlandoHi!21:00
*** morellon has joined #openstack-meeting21:00
markvoelker0/21:00
morellon\o/21:00
rkukurao/21:00
*** SumitNaiksatam has joined #openstack-meeting21:01
s0miko/21:01
danwentok, let's get this started21:01
SumitNaiksatamhi21:01
danwent#startmeeting21:01
openstackMeeting started Mon Jun 11 21:01:10 2012 UTC.  The chair is danwent. Information about MeetBot at http://wiki.debian.org/MeetBot.21:01
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.21:01
*** gongys has joined #openstack-meeting21:01
gongyshello21:01
arosenhi21:01
garykhi21:01
danwent#info http://wiki.openstack.org/Network/Meetings21:01
ncodeo/21:01
danwentwow, big crowd today.  seems like the new time is working out :)21:01
danwent#topic folsom-2 deliverable21:01
*** openstack changes topic to "folsom-2 deliverable"21:01
*** romain_lenglet has joined #openstack-meeting21:02
danwent#info folsom-2 branch date is now 3 weeks out… coming up quickly if you consider the review lags we've been dealing with lately21:02
danwent#info welcome garyk and gongys as core devs by the way… that should help with review lags :)21:02
* markvoelker applauds21:03
*** mcohen has joined #openstack-meeting21:03
danwent#info Our main focus for F-2 work is still getting API v2 fully merged in.21:03
danwent#link https://review.openstack.org/#/c/8039/21:03
danwentour current plan is to get jkoelker_'s branch merged in, depsite some gaps21:03
danwentthis will let more people work on top of filling those gaps.21:04
gongysYes21:04
*** clarkb1 has joined #openstack-meeting21:04
danwentI have a branch already stacked on there for API validation and related improvements: https://review.openstack.org/#/c/8366/21:04
danwentand gongys has been bravely developing client + CLI code against a not entirely solid spec: https://review.openstack.org/#/c/7596/21:05
danwentwe're stil keeping the basic wiki page up to date: http://wiki.openstack.org/QuantumV2APIIntro21:05
danwentPlan is that all remaining API work should be filed as bugs against F-2:  https://launchpad.net/quantum/+milestone/folsom-221:06
danwentgaryk has already volunteered to pick up several of the items, thanks!21:06
danwentany questions concerns there?21:06
*** dwcramer has quit IRC21:07
*** zul has quit IRC21:07
danwentkevin mitchell from rackspace is working on Authz: https://blueprints.launchpad.net/quantum/+spec/authorization-support-for-quantum21:07
danwenthe seems to have good cycles to work on that, so I'm comfortable with progress there.21:07
danwentIs arvind here?21:07
danwentmarkvoelker: ?21:08
danwent#info arvind from cisco is working on https://blueprints.launchpad.net/quantum/+spec/quantum-horizon21:08
*** clarkb1 is now known as clarkb21:08
danwentwe had a call late last week to scope the first deliverable for F-2.21:08
*** jkoelker_ is now known as jkoelker21:09
danwent#info horizin on F-2 will focus on basic network creation/deletion, and being able to spin up VMs on a particular network.21:09
danwenterrr… horizon21:09
markvoelkerHe was around today, but I'm currently at home so can't yell over the cubical wall at him =)21:09
danwentmarkvoelker: that's ok, just yell louder21:09
danwentrkukura: any updates on https://blueprints.launchpad.net/quantum/+spec/provider-networks ?21:09
danwentrkukura: from emails to the list it seems like you're progressing?21:10
* markvoelker just frightened his 7 month old whilst yelling for Arvin's21:10
rkukurayes, specifying vlans works with linuxbridge21:10
rkukuraCan I get away with ignoring XML until we have proper support for extensibility?21:11
danwentrkukura: hrmmm… have we gotten anyone to confirm that there's no good way to do this with XML?21:11
danwentI personally have a bias against XML in general...21:11
*** Salv-orlando has quit IRC21:12
danwentbut if we're going to say we support it, it seems odd that we can't do request extensions with it.21:12
rkukuraI was chatting with Mark McLoughlin about it today21:12
danwentwas that Salv-orlando running away from an API question? :P21:12
*** Salv2 has joined #openstack-meeting21:12
s0mikrkukura: Jorge from Rax should be the authority on that21:12
danwents0mik: I agree.  I've tried to loop him into the threads.  We should bug him more.21:13
rkukuraSeems we need either the template stuff from nova.21:13
danwentrkukura: ok, so there's extra code in nova that isn't in quantum that let's them support it in nova?21:13
rkukuranova has diverged from the extension framework in quantum/openstack-common/melange21:13
danwentah, how i wish all of this API code was just a openstack-common lib :)21:14
rkukuraI can write a BP21:14
s0mikrkukura: I think the quantum framework was based on nova framework, so hope this becomes common soon21:14
garykopenstack-common - the answer to all our problems21:14
danwentrkukura: BP for what exactly?21:14
danwentgaryk:  well, in some cases, yes21:15
*** littleidea_ has joined #openstack-meeting21:15
rkukuraAccording to markmc, nova has gone in a different direction than whats in common21:15
rkukuraBP for making XML extensible in quantum21:15
danwentduring the v2 api stuff, I was really saddened by how much code was written that had nothing to do with quantum specifically.21:15
danwentrkukura: does common already have API extension framework?21:16
danwentlast I heard they were just talking about it.21:16
rkukurayes, and it looks like quantum's is based on it21:16
rkukurabut nova has abandoned it21:16
danwentrkukura: ok, and there's no way to do request extensions in the openstack-common extension framework either, i assume?21:17
rkukuramarkmc says: "but IMHO, the openstack-common version should just be deleted"21:17
rkukurarequest extensions for json work. xml is the issue21:17
danwentrkukura: yes, understood.21:17
rkukurathe openstack-common version does have some xml support thats missing in quantum21:18
danwentOk, so you think the right think it so do JSON only for now, and port the XML stuff over from nova?  Kind of hurts, as it seems like any porting effort should be done toward getting the stuff working on a common lib.21:18
*** littleidea has quit IRC21:18
*** littleidea_ is now known as littleidea21:18
danwentah, misunderstood you, sorry21:18
danwentso if we port over to openstack-common, request extensions can work with XML?21:19
rkukuralong term we should have a common extension framework21:19
danwentrkukura: definitely agree.21:19
ijwrkukura: any idea how far nova have diverged?21:19
rkukuraijw: significantly21:19
danwentOk, this sounds like a longer conversation.21:19
rkukuraThe nova approach now uses decorators, plus templates for xml21:20
*** Salv2 has quit IRC21:20
danwentso short-term call is whether to (a) use request extension and support JSON only until extension framework changes or (b) implement as resource extension?21:20
danwentrkukura: ?21:21
rkukuradanwent: yes, but still not sure xml would work right with resource extension - optional data seems to be a problem21:21
rkukurathe nova template approach leaves out the element for missing data21:22
danwentOk, let's take this to the list.21:22
danwentrkukura: is this already summarized in an email to the list, or should you write one?21:22
rkukuraI've been posting as I learn21:23
danwentlet's be sure to include the main openstack list, as many of the openstack API experts probably aren't on netstack.21:23
rkukuraI'll summarize the issues/questions21:23
danwentrkukura: thanks21:23
danwent#todo rkukura send email summarizing decision points around provider networks bp and request extensions with XML21:24
danwentok, now onto the two BPs that concern me the most for F-2 :)21:24
danwent#info DHCP BP: https://blueprints.launchpad.net/quantum/+spec/quantum-dhcp21:24
danwentcarlp: here?21:24
jkoelkersorry just catching up, but i agree with mark the openstack-common wsgi stuff should be tossed21:25
danwentjkoelker: ok, good to know.  too bad though, as each project seems to be inventing their own wheels :)21:25
jkoelkerits the way of our people ;)21:25
danwentbut if its not done right, no point in porting over to it.21:25
danwent:)21:25
danwentI got an email from mark mcclain at dreamhost saying that they have some internal designs for the dhcp work, but it makes me nervous not to have seen anything yet.21:26
*** jog0 has joined #openstack-meeting21:27
PotHixwe want to help, but I don't know how yet21:27
danwentthey say DHCP work in on target for F-2 though, so hopefully that's good news.   I still think we'll probably need people to help out toward the end.21:27
*** salv-orlando has joined #openstack-meeting21:27
oubiwanndanwent: he's getting ready to work on this in the next few weeks21:27
*** ClemSF_ has joined #openstack-meeting21:27
danwentPotHix: a while back I posted some thoughts on a potential design.  I'd like to see some discussion around designs, that way more people can potentially pitch in and bite off certain pieces.21:28
oubiwanndanwent: I thought he was waiting on the IPAM stuff to land?21:28
oubiwann(mark, that is)21:28
gongysI wan to know how the dhcp server will run in quantum? on quantum sever side or agent?21:28
danwentoubiwann: thanks.  Just that there's 3 weeks left.21:28
PotHixdanwent: where can I find your thoughts about it?21:28
*** ClemSF_ has quit IRC21:28
danwentoubiwann: we have a spec and code that's been in review for a while, so it should definitely be sufficient to make a design.21:28
PotHixI just have that e-mails21:29
danwentoubiwann: if there's missing info that he's waiting on, please have him raise that immediately.21:29
PotHixe-mail*21:29
danwentgongys: that's part of why we need some discussion of the design.  I was guessing that there would be agent code that could basicaly query quantum API for IP mac bindings, and "plug" dnsmasq interfaces into virtual switches, similar to what nova-network does today.21:30
danwentthat at least would be the design that allows us to leverage the most existing code from nova-network.21:31
danwentPotHix: yeah, just that email.  I can resend with a wider audience.  Just trying to get the conversation started on this.21:31
garykdanwent: can you please send to the list21:31
danwent#todo: danwent resent email about simple DHCP design to ML21:31
*** jsavak has quit IRC21:32
*** ClemSF has quit IRC21:32
danwentok, hopefully we can get some more attention focused on DHCP this in the next week.21:32
PotHixCool. I'll send some thoughts.21:32
danwentIn another bit of bad news, I heard tr3buchet is not going to be able to work on Nova + Quantum integration in F-2: https://blueprints.launchpad.net/quantum/+spec/improved-nova-quantum-integration21:33
danwenthe has a branch that has a lot of the changes already, though it uses the quantum v1.1 and melange APIs, rather than the quantum v2 API.21:33
*** jjm3lp has quit IRC21:33
danwentso we'll need to find someone who can work on this for F-221:34
gongysThis bp will rely on IPAM merged in21:34
danwentgongys: the new Quantum v2 API merges IPAM into Quantum.21:34
*** ncode has quit IRC21:34
danwentgongys: or am I misunderstanding you?21:34
gongysdan: no. you are right.21:35
PotHixA lot of changes depending on the v221:35
PotHixBut itś21:35
*** dolphm has quit IRC21:35
PotHixBut it is almost finished, right?21:35
*** salv-orlando has quit IRC21:36
*** davidkranz_ has quit IRC21:36
danwentPotHix: agreed, that's why our primary focus needs to be on getting that merged.  Main Api-v2 code should go in today, assuming we get a people to sign off on jkoelker recent tweaks to the branch21:36
*** davidkranz_ has joined #openstack-meeting21:36
*** ayoung has quit IRC21:36
danwentOk, so I have a lot of familiarity with the nova + quantum integration, and can help anyone able to work on that.21:36
*** SumitNaiksatam has quit IRC21:37
danwentlet me know.  this work is very fundemental to being able to see the benefits from the v2 API, so it definitely needs to be done in F-2.21:37
danwentOk, any other F-2 topics?21:37
garykdanwent: common config would be nice if it could be reviewed21:38
danwentoverall, we're getting a lot of great work done, we just have very ambitious goals :)21:38
danwentgaryk: good point.21:38
PotHixdanwent: ncode is working on iptables_manager and agents21:38
danwent#info: need review love for common-cfg bp: https://review.openstack.org/#/c/8101/21:38
PotHixwe don't have to include dependencies to it21:38
*** ncode has joined #openstack-meeting21:38
danwentPotHix: is this still the primary review: https://review.openstack.org/#/c/7762/ ?21:39
danwentwe need to get that in… its been under review for a while.21:39
gongysgaryk: I think we need put the api v2.0 in first, and then the common config.21:39
danwentlooks like we're close21:39
PotHixdanwent: yes21:39
garykok21:39
danwentgongys:  API v2 stuff should really be top priority for everyone, as there are so many dependencies.21:40
danwentwe all need to pitch in :)21:40
danwent#topic community topics21:40
*** openstack changes topic to "community topics"21:40
danwentoh no, did salvatore drop off?21:41
danwent#info wiki page for core devs to sign up for review days: http://wiki.openstack.org/Quantum/ReviewDays21:41
PotHixdanwent: we're waiting the iptables_manager merge to work on the generic_firewall21:42
danwentall core devs should be signed up for a day per week.  double-booking is ok, we'll just expect extra reviewing horsepower those days.21:42
*** nikhil has quit IRC21:42
danwentPotHix: yes, makes sense.21:42
*** salv-orlando has joined #openstack-meeting21:42
danwentfeel free to ping the "active" core devs about reviews on their days.21:43
danwentrecall that we're expecting 2-3 hours MINIMUM of reviews from a core dev per week.  If you're sticking to the minimum, those hours should be focused on your review day.  You should focus your review energies on the reviews that are most critical to the community (e.g., those blocking a lot of work, or ranked highly on launchpad)21:44
danwentas part of my review day, I'll review the reviews to make sure review days are working.21:45
*** milner has quit IRC21:45
danwent:)21:45
danwentany questions/comments/concerns?21:45
danwentalso, feel free to CC on emails you send to the reviewers requesting reviews on their review days.21:45
danwentsalv-orlando: there you are!21:45
salv-orlandohere I am!21:46
danwentwe were just talking about review days21:46
salv-orlandoI got disconnected21:46
danwent"conveniently" :P21:46
danwentsalv-orlando: anything you'd like to say on review days?21:46
salv-orlandoI am looking at the wiki page. Slots look pretty full which is great21:47
salv-orlandoAnd I see GaryK has volunteered for doing reviews on Sundays :)21:47
danwentsalv-orlando: yes, though we have a good number of people not signed up yet.  I mentioned that double-booking is ok, we'll have expect even more reviews :)21:47
garyksalv-orlando - sunday is a work day and friday is weekend :)21:48
danwentsalv-orlando: his monday21:48
danwent#topic open discussion21:48
*** openstack changes topic to "open discussion"21:48
salv-orlandogaryk: I didn't know you were in Israel, sorry :)21:48
danwentok, any other items we need to discuss21:48
ncodedanwent: I'd like to know about the agents21:48
danwentncode: what about them?21:48
garykncode: i am working on scalable agents21:49
ncodethey will use the common from quantum or will get a new one?21:49
*** SumitNaiksatam has joined #openstack-meeting21:49
garykncode: the rpc code is taken from openstack comon (if this is your question)21:49
ncodeis that21:49
danwentncode: current model is that quantum-server and quantum-agents both have access to the same quantum python libraries.21:50
*** jjm3lp has joined #openstack-meeting21:50
danwentthat is, there's not a separate common for agents vs. server plugin code.21:50
ncodeI will move some code to there as gongys said21:50
*** dwcramer has joined #openstack-meeting21:50
*** milner has joined #openstack-meeting21:50
danwentncode: yes, anything that might be shared across agents should go in quantum/agent/*21:50
danwentlike the ovs_lib.py example, and the iptables manager code.21:51
PotHixdanwent: Will we have the same dependencies on agents and server?21:51
ncodePotHix: is that my point :D21:51
ncodes/is that/that is/21:51
danwentPotHix: by dependencies, do you mean package dependencies, like apt-get?21:52
ncodemore like library danwent, can be package21:52
danwentdistros can and probably will have different depenedencies for the two, though I agree that our current model does not make it easy for them to determine which is which.21:52
danwentncode:  so you mean like a non-standard python library?21:53
ncodedanwent: package as you said, but is hard to have some things from quantum server inside XS21:54
danwentncode: we can keep talking about this, but let's wrap up the official meeting.21:54
ncodeoks21:54
danwentanything else urgent that we need to discuss before wrapping up?21:54
danwentok, thanks folks.  stay on the channel if you want to keep talking about agent dependencies21:55
danwent#endmeeting21:55
*** openstack changes topic to "OpenStack meeting channel. See http://wiki.openstack.org/Meetings for schedule and http://eavesdrop.openstack.org/meetings/openstack-meeting/ for meeting logs"21:55
openstackMeeting ended Mon Jun 11 21:55:10 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)21:55
openstackMinutes:        http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-11-21.01.html21:55
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-11-21.01.txt21:55
openstackLog:            http://eavesdrop.openstack.org/meetings/openstack-meeting/2012/openstack-meeting.2012-06-11-21.01.log.html21:55
salv-orlandobye, have a good one!21:55
danwenthave a good rest of the week.  please help get the api v2 stuff over the hump and in :)21:55
*** milner has quit IRC21:55
garykthanks! good night21:56
danwentncode: i think this is a good discussion.  currently, plugin specify their dependencies as part of their documentation, which is what a packager would look at.21:56
danwentI think it would commonly make sense for a plugin to specify differences in their dependencies between agent code and plugin code that runs as part of the main quantum server.21:56
danwentis there a specific example that you're dealing with?21:57
*** romain_lenglet has quit IRC21:57
gongysncode: I think your are talking about to use the execute() from openstack common, right?21:57
ncodenot from core21:57
ncodegongys: the execute and also run_cmd now21:57
ncodebut some deps from server21:57
ncodewill be hard to port to a old linux or XS21:58
ncodebut if you split the agent and server common21:58
ncodewill make it easy21:58
salv-orlandoIf I might chime in this discussion I'd say that I see ncode's concern21:58
ncodeagent will use way less code and libs than server21:59
danwentncode: i agree that we should structure common code in a way that makes it easy for agent code to pull in just what it needs, without pulling in a lot more dependencies21:59
salv-orlandodanwent: I agree with you, the agent should bring only what it actually needs.22:00
danwentso if there's something that an agent is likely to need, we shouldn't have it in the same module of something that imports a bunch of libs that an agent doesn't need.22:00
*** mcohen has quit IRC22:00
rkukuraIsn't quantum/openstack/common just a stopgap until the code is out of incubation?22:00
danwenthey guys, I need to run to a meeting.22:00
*** edygarcia has joined #openstack-meeting22:00
salv-orlandorkukura: what do you mean by stopgap?22:01
danwentrkukura: yes, eventually it will be its own lib…22:01
salv-orlandodanwent: see you tomorrow!22:01
*** mcohen has joined #openstack-meeting22:01
rkukuraEventually this code will be packages in a proper openstack-common package22:01
danwenti see your point.  do we need to be able to import only a subset of openstack-common?22:01
*** mattray has quit IRC22:01
PotHixSomething like that22:01
danwenti think each different chunk of openstack common would be package separately though, if they do it right.22:01
rkukuraor do we only depend on what we actually use?22:01
rkukuraI meant do we only pull in the dependencies of the chunks we actually use?22:02
ncodedanwent: if the common stay clean it will not be a problem22:03
salv-orlandoas danwent is noticing whether quantum-agent can use or not a subset of openstack-common probably depends on how it's packaged22:03
danwentncode: sorry, got to run.22:03
ncodedanwent: oks22:03
danwentfeel free to raise this on the list.22:03
*** danwent has quit IRC22:03
*** ttrifonov is now known as ttrifonov_zZzz22:03
rkukuraThis also might be a good one for the openstack list to get wider input.22:03
PotHixsalv-orlando: you're right, but could we manage it?22:04
salv-orlandoanyway, I'd say we should probably have two separate discussion on os-common packaging for quantum-agent and communication with hypervisors such as xs22:04
*** markvoelker has quit IRC22:04
salv-orlandoPotHix: if we finda dev with spare cycles, I guess we can :)22:04
*** Gordonz has quit IRC22:05
PotHixsalv-orlando: But each distro will may package it differently, right?22:05
salv-orlandoI am not a great fan of the idea of forking openstack-common or having our own libs, but I guess we can think of having an openstack-common-lite pkg22:05
PotHixsalv-orlando: insteresting :)22:06
salv-orlandoPotHix: it will. But we already have Fedora, Ubuntu, and Debian packagers among our devs22:06
ncodesalv-orlando: this would be really good :D22:06
rkukuraSo what defines lite? Python 2.4 compatability?22:07
salv-orlandoThat's the though bit22:07
PotHixrkukura: Less dependencies as possible, I think.22:07
*** littleidea_ has joined #openstack-meeting22:07
rkukuraSeems each component should have its own dependencies, and we should only use the components we need.22:08
salv-orlandoFrom what I see, if we want to keep python 2.4 compatibility indefinetely, then we will probably unable to use large chunks of openstack-common22:08
rkukuragaryk has been wrestling with this for the common-cfg work22:08
rkukurawhich is used by the common-rpc22:08
rkukuraI really think we'd be best off having the agent run in a modern environment and remotely execute things in dom0 when needed22:09
salv-orlandowhat's the feedback? Can we keep this compatibility? Or do you reckon it's going to be unmanageable in the long run?22:09
PotHixrkukura: common-cfg should be on the "openstack-common-lite" IMHO22:09
salv-orlandorkukura: +infinity22:09
salv-orlandobut this will imply that the agent is not anymore hypervisor agnostic, so it will be a bit more complex. Personally, I don't mind.22:10
ncoderkukura: This could be awesome, but is not the real world now :(.22:10
ncoderkukura: This will be hard to set up with the dhcp22:10
rkukuraI've suggested before that we see if the root_wrapper hooks could be used for this22:11
*** adjohn has quit IRC22:11
*** littleidea has quit IRC22:11
*** littleidea_ is now known as littleidea22:11
salv-orlandoAs an example I can cite the security groups driver. Both libvirt and xenapi backend use the same code, but when it comes to execute commands, libvirt does it locally, whether the xenapi driver invokes a dom0 extension22:11
*** adjohn has joined #openstack-meeting22:11
salv-orlandoI think that if we adopt the same mechanism in Quantum we should be allright. And I reckon we can do that through the rootwrap22:12
salv-orlandoAnd installing a dom0 extension is as easy as copying a python module to /etc/xapi.d/plugins22:12
*** dendro-afk is now known as dendrobates22:12
*** SumitNaiksatam has quit IRC22:16
salv-orlandobye, have a good one!22:17
*** salv-orlando has quit IRC22:17
*** rkukura has quit IRC22:17
*** rkukura has joined #openstack-meeting22:18
rkukuranode, salv-orlando: lost my connection for a bit. Any conclusion?22:19
rkukuras/node/ncode/22:19
ncoderkukura: not now, I'll start this talk on ML22:20
PotHix+122:20
PotHix:)22:20
rkukura+1, but its been attempted before22:20
*** LinuxJedi_ has joined #openstack-meeting22:21
*** jdurgin1 has joined #openstack-meeting22:21
*** novas0x2a|lapto1 has joined #openstack-meeting22:21
*** danwent has joined #openstack-meeting22:22
*** adam_g has joined #openstack-meeting22:22
*** _0x44_ has joined #openstack-meeting22:23
*** yamahata_ has joined #openstack-meeting22:23
*** comstud_ has joined #openstack-meeting22:24
*** _0x44 has quit IRC22:24
*** mikal_ has joined #openstack-meeting22:24
*** devcamcar has joined #openstack-meeting22:24
*** _0x44_ is now known as _0x4422:24
*** pknouff has joined #openstack-meeting22:25
*** LinuxJedi has quit IRC22:26
*** LinuxJedi_ is now known as LinuxJedi22:26
*** jjm3lp has quit IRC22:29
*** novas0x2a|laptop has quit IRC22:29
*** jdurgin has quit IRC22:29
*** devcamca- has quit IRC22:29
*** comstud has quit IRC22:29
*** mikal has quit IRC22:29
*** jaypipes-afk has quit IRC22:29
*** yamahata has quit IRC22:29
*** pknouff_ has quit IRC22:29
*** edygarcia has quit IRC22:29
*** primeministerp has quit IRC22:30
*** jaypipes-afk has joined #openstack-meeting22:30
*** rkukura has quit IRC22:30
*** danwent_ has joined #openstack-meeting22:30
*** yamahata_ has quit IRC22:31
*** dendrobates has quit IRC22:31
*** primeministerp has joined #openstack-meeting22:32
*** danwent has quit IRC22:32
*** oubiwann has quit IRC22:32
*** danwent_ is now known as danwent22:32
*** joearnold has joined #openstack-meeting22:33
*** rkukura has joined #openstack-meeting22:34
*** dwcramer has quit IRC22:34
*** oubiwann has joined #openstack-meeting22:35
*** dendro-afk has joined #openstack-meeting22:36
*** dwcramer has joined #openstack-meeting22:37
*** zul has joined #openstack-meeting22:37
*** yamahata_ has joined #openstack-meeting22:44
*** danwent has quit IRC22:47
*** mcohen has quit IRC22:49
*** rkukura has quit IRC22:50
*** mcohen has joined #openstack-meeting22:54
*** zul has quit IRC23:00
*** chuck_ has joined #openstack-meeting23:00
*** chuck_ has quit IRC23:01
*** zul has joined #openstack-meeting23:01
*** danwent has joined #openstack-meeting23:10
*** lloydde has quit IRC23:12
*** dtroyer is now known as dtroyer_zzz23:13
*** edygarcia has joined #openstack-meeting23:15
*** joearnold has quit IRC23:16
*** Mandell has quit IRC23:23
*** Mandell has joined #openstack-meeting23:26
*** sleepsonthefloor is now known as sleepsonzzz23:27
*** dtroyer_zzz is now known as dtroyer23:29
*** littleidea has quit IRC23:30
*** jdurgin1 has quit IRC23:31
*** jdurgin has joined #openstack-meeting23:31
*** gyee has joined #openstack-meeting23:33
*** lloydde has joined #openstack-meeting23:35
*** littleidea has joined #openstack-meeting23:38
*** donaldngo_hp has joined #openstack-meeting23:48
*** donaldngo_hp has joined #openstack-meeting23:50
*** donaldngo_hp has joined #openstack-meeting23:51
*** sdake has quit IRC23:52
*** lloydde has quit IRC23:59

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