*** heckj has quit IRC | 00:39 | |
*** cp16net|away is now known as cp16net | 01:44 | |
*** cp16net is now known as cp16net|away | 01:45 | |
*** cp16net|away is now known as cp16net | 01:45 | |
*** robertmyers has joined #openstack-meeting-alt | 02:02 | |
*** cp16net is now known as cp16net|away | 02:09 | |
*** chad has joined #openstack-meeting-alt | 02:15 | |
*** chad is now known as Guest52495 | 02:16 | |
*** Guest52495 is now known as carimura | 02:16 | |
*** carimura has quit IRC | 02:23 | |
*** kaganos has quit IRC | 02:24 | |
*** amyt has joined #openstack-meeting-alt | 02:28 | |
*** cp16net|away is now known as cp16net | 02:52 | |
*** grapex has quit IRC | 03:11 | |
*** grapex has joined #openstack-meeting-alt | 03:12 | |
*** bdpayne has quit IRC | 03:27 | |
*** grapex has joined #openstack-meeting-alt | 03:30 | |
*** grapex has quit IRC | 04:05 | |
*** grapex has joined #openstack-meeting-alt | 04:06 | |
*** grapex has quit IRC | 04:15 | |
*** bdpayne has joined #openstack-meeting-alt | 04:32 | |
*** chad has joined #openstack-meeting-alt | 05:16 | |
*** chad is now known as carimura | 05:16 | |
*** amyt has quit IRC | 05:28 | |
*** amyt has joined #openstack-meeting-alt | 05:28 | |
*** cp16net is now known as cp16net|away | 05:52 | |
*** cp16net|away is now known as cp16net | 05:53 | |
*** Alagar has quit IRC | 06:25 | |
*** bdpayne has quit IRC | 06:47 | |
*** carimura has quit IRC | 07:38 | |
*** bdpayne has joined #openstack-meeting-alt | 07:40 | |
*** bdpayne has quit IRC | 08:55 | |
*** amyt has quit IRC | 09:29 | |
*** robertmyers has quit IRC | 13:24 | |
*** robertmyers has joined #openstack-meeting-alt | 14:31 | |
*** cloudchimp2 has joined #openstack-meeting-alt | 14:55 | |
*** bdpayne has joined #openstack-meeting-alt | 15:27 | |
*** rnirmal has joined #openstack-meeting-alt | 15:44 | |
*** grapex has joined #openstack-meeting-alt | 15:59 | |
*** grapex has quit IRC | 15:59 | |
*** grapex has joined #openstack-meeting-alt | 16:00 | |
*** amyt has joined #openstack-meeting-alt | 16:00 | |
*** cp16net is now known as cp16net|away | 16:02 | |
*** amyt_ has joined #openstack-meeting-alt | 16:07 | |
*** amyt has quit IRC | 16:07 | |
*** amyt_ is now known as amyt | 16:07 | |
*** jcru has joined #openstack-meeting-alt | 16:12 | |
*** amyt has quit IRC | 16:13 | |
*** amyt has joined #openstack-meeting-alt | 16:13 | |
*** cloudchimp2 has quit IRC | 16:34 | |
*** cloudchimp has joined #openstack-meeting-alt | 16:34 | |
*** amyt_ has joined #openstack-meeting-alt | 16:36 | |
*** amyt has quit IRC | 16:36 | |
*** amyt_ is now known as amyt | 16:36 | |
*** grapex has quit IRC | 16:39 | |
*** carimura has joined #openstack-meeting-alt | 16:45 | |
*** amyt has quit IRC | 16:47 | |
*** amyt has joined #openstack-meeting-alt | 16:47 | |
*** jcru is now known as jcru|away | 17:05 | |
*** jcru|away is now known as jcru | 17:05 | |
*** jcru is now known as jcru|away | 17:21 | |
*** jcru|away is now known as jcru | 17:23 | |
*** esp has joined #openstack-meeting-alt | 17:39 | |
*** esp has left #openstack-meeting-alt | 17:39 | |
*** heckj has joined #openstack-meeting-alt | 17:39 | |
*** grapex has joined #openstack-meeting-alt | 17:43 | |
*** grapex has quit IRC | 17:43 | |
*** grapex has joined #openstack-meeting-alt | 17:43 | |
*** kaganos has joined #openstack-meeting-alt | 17:50 | |
*** carimura has quit IRC | 17:54 | |
*** carimura has joined #openstack-meeting-alt | 17:55 | |
*** carimura has quit IRC | 18:22 | |
*** carimura has joined #openstack-meeting-alt | 18:23 | |
*** carimura has quit IRC | 18:24 | |
*** carimura has joined #openstack-meeting-alt | 18:25 | |
*** vipul is now known as vipul|away | 18:31 | |
*** kaganos has quit IRC | 18:43 | |
*** kaganos has joined #openstack-meeting-alt | 18:45 | |
*** vipul|away is now known as vipul | 19:11 | |
*** cp16net|away is now known as cp16net | 19:28 | |
*** vipul is now known as vipul|away | 20:04 | |
*** vipul|away is now known as vipul | 20:51 | |
*** hub_cap has joined #openstack-meeting-alt | 21:45 | |
*** dkehn has joined #openstack-meeting-alt | 21:52 | |
*** datsun180b has joined #openstack-meeting-alt | 21:56 | |
*** SlickNik has joined #openstack-meeting-alt | 21:57 | |
hub_cap | #startmeeting reddwarf | 21:59 |
---|---|---|
openstack | Meeting started Tue Jan 29 21:59:26 2013 UTC. The chair is hub_cap. Information about MeetBot at http://wiki.debian.org/MeetBot. | 21:59 |
openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 21:59 |
*** openstack changes topic to " (Meeting topic: reddwarf)" | 21:59 | |
openstack | The meeting name has been set to 'reddwarf' | 21:59 |
SlickNik | hello there | 21:59 |
datsun180b | hiya | 21:59 |
hub_cap | howdy SlickNik | 21:59 |
vipul | here | 21:59 |
hub_cap | and everyone else :) | 21:59 |
hub_cap | #link http://wiki.openstack.org/Meetings/RedDwarfMeeting | 21:59 |
juice | here | 21:59 |
juice | present | 22:00 |
hub_cap | lets give a minute for the tricklers | 22:00 |
dkehn | ding | 22:00 |
jcooley | afternoon | 22:00 |
SlickNik | sounds good. | 22:00 |
*** esp has joined #openstack-meeting-alt | 22:00 | |
*** imsplitbit has joined #openstack-meeting-alt | 22:00 | |
imsplitbit | bam | 22:00 |
hub_cap | lol hi imsplitbit | 22:00 |
imsplitbit | howdy | 22:00 |
imsplitbit | sorry I'm late | 22:01 |
hub_cap | ok lets rock this, we have enough | 22:01 |
datsun180b | he started a minute early | 22:01 |
grapex | Greets | 22:01 |
*** jdbarry has joined #openstack-meeting-alt | 22:01 | |
hub_cap | grapex says he will be late | 22:01 |
datsun180b | won't hold it against him though | 22:01 |
hub_cap | WOAH nice grapex! | 22:01 |
imsplitbit | grapex, you live! | 22:01 |
hub_cap | #topic action items | 22:01 |
*** openstack changes topic to "action items (Meeting topic: reddwarf)" | 22:01 | |
*** yidclare has joined #openstack-meeting-alt | 22:01 | |
hub_cap | vipul: link us your bp plz sir | 22:02 |
hub_cap | for quotas | 22:02 |
vipul | #link https://blueprints.launchpad.net/reddwarf/+spec/quotas | 22:02 |
SlickNik | cool, thanks... | 22:02 |
vipul | annashen, juice added a bunch to this one | 22:02 |
vipul | i think this needs a good review, and some discussion | 22:02 |
vipul | which i've put as part of the agenda later | 22:02 |
hub_cap | hokey. and we have a topic right? | 22:02 |
SlickNik | they've also got a bunch of info up on the openstack wiki... | 22:03 |
*** djohnstone has joined #openstack-meeting-alt | 22:03 | |
hub_cap | so the testr BP | 22:03 |
dkehn | link to the wiki again | 22:03 |
vipul | #link http://wiki.openstack.org/reddwarf-quotas | 22:04 |
SlickNik | #link http://wiki.openstack.org/reddwarf-quotas | 22:04 |
dkehn | gotit | 22:04 |
juice | grr yes the wiki is more complete let me link to that | 22:04 |
juice | thanks vipul and nik | 22:04 |
hub_cap | nice | 22:04 |
hub_cap | so lets defer too much convo to the actual topic in the meeting | 22:04 |
SlickNik | Yes, we have a topic for discussion on this, | 22:04 |
*** DandyPandy has joined #openstack-meeting-alt | 22:04 | |
SlickNik | sounds good. | 22:04 |
hub_cap | and breeze thru these action items | 22:04 |
hub_cap | as for testr BP, i reviewed last wk. the only suggestion i have is that i dont think we need to put the files that are changing in the BPs | 22:04 |
vipul | testr Blueprint... I think we had some discussions here in the office, agreed to put everything testr related in /reddwarf/tests/unittest | 22:04 |
hub_cap | otherwise the content is good... cna someone link it? | 22:04 |
hub_cap | ok that makes sense | 22:05 |
vipul | #link https://blueprints.launchpad.net/reddwarf/+spec/testr-unit-tests | 22:05 |
*** CaptTofu has joined #openstack-meeting-alt | 22:05 | |
SlickNik | thanks vipul | 22:05 |
* CaptTofu is lurking | 22:05 | |
hub_cap | HAI! | 22:05 |
vipul | i think the idea was to show where tests would live, right esp? | 22:05 |
hub_cap | ya ive seen a few of the BPs have full file listings | 22:05 |
SlickNik | welcome aboard, capt! | 22:05 |
esp | yeah I think so | 22:05 |
vipul | welcome CaptTofu | 22:05 |
CaptTofu | hi! | 22:06 |
vipul | but yea, generally probalby don't need to have every file being changed listed in the bp | 22:06 |
hub_cap | there was another recent one that had the 3 files (the guest conf grant chante one) | 22:06 |
CaptTofu | one needs a break from chef | 22:06 |
hub_cap | :) | 22:06 |
esp | we decided to kill off the 'functional' package and shove everything under unittest I think. | 22:06 |
hub_cap | ok that works for me esp | 22:06 |
esp | #link https://blueprints.launchpad.net/reddwarf/+spec/create-restricted-root-account | 22:06 |
esp | ^^ we are still working out the details of this one | 22:07 |
hub_cap | ya i love the content of that BP im just not sure we need the files at the top of it | 22:07 |
vipul | any opposition to having a seaprate dbaas.conf file? | 22:07 |
esp | but yeah it involves adding a new config for the grant | 22:07 |
hub_cap | id prefer a separate guest conf file personally | 22:07 |
hub_cap | so we know where the split is if we create a different guest :) | 22:07 |
esp | k, I will fix the content of the BP | 22:08 |
hub_cap | but we got a bit OT on that one :) | 22:08 |
hub_cap | we are on housing multiple images action item | 22:08 |
cp16net | #agrees with hub_cap on separate guest conf | 22:08 |
hub_cap | i think weve beat that one to the ground right? | 22:08 |
SlickNik | lol, yea…I think so... | 22:08 |
hub_cap | :) | 22:08 |
vipul | esp: seems like we need a separate one then | 22:08 |
esp | vipul: yeah I'm good with that | 22:09 |
hub_cap | ya /me wants separate config.. it makes more sense | 22:09 |
vipul | just to be clear, there's gonna be a guestagent.conf.. and another conf for things like grants | 22:09 |
hub_cap | ok now im confused | 22:09 |
vipul | thigns that are hard-cdoed in dbaas.py could live there | 22:09 |
vipul | lol | 22:09 |
hub_cap | lets table this | 22:09 |
vipul | though so | 22:09 |
esp | also note that we are note going to put the actual GRANT stmt in the config but we'll build it in code as per steveleon | 22:09 |
vipul | come back to it | 22:09 |
hub_cap | and put it on the agenda so we can get thru action items | 22:09 |
esp | k | 22:10 |
hub_cap | vipul: can u amend the agenda? | 22:10 |
hub_cap | Slicknik working on making integration tests run post devstack install + local.sh run for CI <-- you are up SlickNik | 22:10 |
vipul | yep | 22:10 |
hub_cap | should we table this to the CI section? | 22:10 |
SlickNik | Okay, so I'm fixing up the two problematic tests... | 22:10 |
hub_cap | there are 2 action items SlickNik owns, go head and chat em up | 22:11 |
SlickNik | issues were being caused by apparmor and upstart trying to continuously start up mysql. | 22:11 |
hub_cap | problematic tests? speed wise? or mucking up content? | 22:11 |
hub_cap | AHH | 22:11 |
hub_cap | im pretty sure upstart _is_ the devil | 22:11 |
SlickNik | because of this the log files were never actually getting _fixed_ | 22:11 |
hub_cap | ya, grapex told me about that one recently | 22:12 |
vipul | it's the restart tests - problem only seems to be evident on cloud servers.. since it's much slower | 22:12 |
SlickNik | anyhow, after these fixes are in all the blackbox tests should run clean. | 22:12 |
hub_cap | coolness | 22:12 |
SlickNik | Also, we had to take some smaller fixes to make the build/tests run under devstack-vm-gate. | 22:12 |
hub_cap | thats great news. then its hook into gerrit time :) | 22:12 |
grapex | Did it seem like there was anything we could change to make the tests catch that bug every time? | 22:13 |
hub_cap | cool SlickNik i figured there would be a bit of work there... | 22:13 |
cp16net | thats awesome news! | 22:13 |
grapex | Instead of just on the slower environment? | 22:13 |
SlickNik | and there's a couple more I need to code up that have to do with us always using 10.0.0.1 for the host ip.. | 22:13 |
SlickNik | vm-gate uses 10.1.0.1 | 22:13 |
vipul | grapex: I think an explicit 'stop' call may work | 22:13 |
dkehn | and timeout issues with test_instance_created | 22:13 |
hub_cap | SlickNik: Ahhhh i was wondering why u mentioned removing that 10.0.0.1 hardcode... thx for the info | 22:14 |
SlickNik | Should be able to get to that by tomorrow, so ever inching closer. | 22:14 |
hub_cap | so that takes care of 4, 5, and 6 | 22:14 |
hub_cap | SlickNik: AWESOME | 22:14 |
vipul | hub_cap: http://eavesdrop.openstack.org/meetings/reddwarf/2013/reddwarf.2013-01-22-22.01.html | 22:14 |
hub_cap | vipul: #7 is you, once u and grapex figured out the apparmore thing u were good to og right? | 22:14 |
vipul | are you on the right one? | 22:14 |
hub_cap | WEAK vipul no im not | 22:15 |
hub_cap | stale link | 22:15 |
vipul | lol | 22:15 |
vipul | was cornfused | 22:15 |
SlickNik | heh, I was wondering too.. | 22:15 |
hub_cap | so that takes care of 2, 3 and 4 :) | 22:15 |
juice | just one other note - on images, test and performance…I am digging into the over performance issues with the disk image builder images | 22:15 |
vipul | #info juice looking into why diskimage builder images are slower | 22:16 |
hub_cap | if its over performing lets not look at it too hard /rimshot | 22:16 |
juice | I wish | 22:16 |
cp16net | lol | 22:16 |
juice | hub_cap: its a dog | 22:16 |
* hub_cap sheds a tear | 22:16 | |
hub_cap | so i spoke w/ heckj wrt the api | 22:17 |
SlickNik | I think it's an overperforming underperformer :P | 22:17 |
hub_cap | :) | 22:17 |
vipul | heh | 22:17 |
heckj | ?? | 22:17 |
hub_cap | hi lurker | 22:17 |
* heckj waves | 22:17 | |
heckj | I thought I'd been summoned | 22:17 |
hub_cap | nope just talked _about_ | 22:17 |
hub_cap | we exchanged emailses about the spec and what some good lessons learned are, ill foward them to u vipul | 22:17 |
vipul | soudns good | 22:18 |
hub_cap | #action hub_cap to forward joe hecks (so i dont mention his irc name heckj) email to vipul | 22:18 |
heckj | heh | 22:18 |
hub_cap | see how i did that there :P | 22:18 |
hub_cap | so our internal team does _not_ like the 1.0 2.0 spec change | 22:18 |
hub_cap | so we might just roll w/ a 1.1 spec | 22:18 |
heckj | vipul, hub-cap: I don't think anything was terribly private in there, do with it as you please | 22:19 |
hub_cap | <3 heckj | 22:19 |
hub_cap | and we are currently reviewing the internal 1.0 spec as per our doc writer, it should be up soon | 22:19 |
vipul | hub_cap... what's the issue with 1.1 vs 2.0? | 22:19 |
heckj | mostly my with-a-bourbon reflections on what went ok and what fucked up doing spec writing and pimping | 22:19 |
hub_cap | mmmm bourbon | 22:19 |
hub_cap | well since we havent changd the api significantly from the 1.0 api, why not roll w/ 1.1 since its just mroe features | 22:20 |
hub_cap | was their question.. and it makes sense | 22:20 |
vipul | right, agreed, not a compatilibity change | 22:20 |
hub_cap | no reason to go 2.0 until we break the 1x contract | 22:20 |
hub_cap | yup | 22:20 |
SlickNik | gotcha | 22:20 |
vipul | hub_cap: you have a 1.1 API flushed out? | 22:21 |
hub_cap | vipul: nope we have a full day meeting planned next wk | 22:21 |
hub_cap | so any features u have already fleshed out, send our way | 22:21 |
hub_cap | or btter yet, blueprint :) | 22:21 |
vipul | hub_cap: please forward our way | 22:21 |
vipul | hub_cap: we have a snapshots blueprint just filed | 22:21 |
vipul | I need to come up with an API around it | 22:21 |
hub_cap | DEF. itll be up on the database-api (but ill send u a working copy first) | 22:21 |
vipul | that's not quite int he BP yet | 22:21 |
hub_cap | cool | 22:21 |
hub_cap | ya id like ot not reinvent the wheel for that since uve done it already | 22:22 |
hub_cap | and we have done work for the my.cnf edits api as well | 22:22 |
hub_cap | so we can turn it into a nice little doc and go bakc and forth a bit on it | 22:22 |
hub_cap | #link http://wiki.openstack.org/Reddwarf | 22:22 |
hub_cap | ^ ^ needs love | 22:22 |
vipul | cool... hopefuly next couple of weeks we can get a few of thos big items flushed out | 22:22 |
hub_cap | vipul: i think next week ill have something for u | 22:22 |
hub_cap | i do like that yall put the quotas BP up on that, and i like even more the under construction sign is still there :) | 22:23 |
hub_cap | (sorry ive moved on to the next action item) | 22:23 |
vipul | #action everyone add more content to wiki | 22:23 |
hub_cap | #agreed | 22:23 |
hub_cap | juice: percona bits to integration, hows that comin? | 22:24 |
juice | I can document the disk image builder stuff there | 22:24 |
hub_cap | nice plz do juice | 22:24 |
juice | hub_cap: that was handed off to two folks here | 22:24 |
juice | I think they are just working on getting the flags/switches in there | 22:24 |
vipul | SlickNik or I can document how to get RD intalled with devstack | 22:24 |
hub_cap | great. who is the new handler? | 22:24 |
juice | Though I don't know if they have yet gotten guest agent to set status to ACTIVE | 22:24 |
SlickNik | #action SlickNik to document info about the new devstack - redstack build to the wiki | 22:24 |
vipul | thanks | 22:25 |
SlickNik | no worries, I'll run it by you vipul... | 22:25 |
vipul | kaganos, kmansel | 22:25 |
hub_cap | ok perfect | 22:25 |
kaganos | hey | 22:25 |
vipul | updates on Percona image? | 22:25 |
kaganos | sorry, we're head down into something here ... | 22:25 |
kaganos | what was the question? | 22:25 |
hub_cap | #action kaganos and kmansel own percona bits for integration | 22:25 |
hub_cap | kaganos: just wondering update on status, no worries | 22:25 |
kaganos | k | 22:26 |
hub_cap | do what u gotta do we can talk in #reddwarf later | 22:26 |
kaganos | status="working on it... | 22:26 |
kaganos | " | 22:26 |
hub_cap | :) | 22:26 |
hub_cap | ha i got my smiley in your quotes | 22:26 |
hub_cap | so grapex and steveleon, how did the test reviews go? | 22:26 |
vipul | I know the final review got merged... | 22:27 |
vipul | guest agent 100% | 22:27 |
grapex | There's one open from Deniz Demir I haven't looked at yet. Sorry, I've been ill. | 22:27 |
hub_cap | nice!! | 22:27 |
steveleon | yup | 22:27 |
steveleon | had some help from grapex.... | 22:27 |
hub_cap | grapex: caught the black lung | 22:27 |
SlickNik | grapex is here! | 22:28 |
SlickNik | hope you're feeling better... | 22:28 |
hub_cap | and consequently is also a merman | 22:28 |
annashen | what's black lung | 22:28 |
grapex | Thanks | 22:28 |
juice | grapex: flu or cold? | 22:28 |
vipul | too many cigarettes | 22:28 |
grapex | hub_cap: water is the essence of liquid | 22:28 |
CaptTofu | cigarattitis | 22:28 |
steveleon | vipul, you were saying that there was some intermittent failures with some tests | 22:28 |
hub_cap | grapex: :) | 22:28 |
vipul | steveleon: yes, saw that last night on the 'coverage' patch... sqllite tests fail from time to time | 22:28 |
*** carimura has quit IRC | 22:28 | |
vipul | since they are run parallel | 22:29 |
steveleon | ugh... i wonder if it is the fake id we are passing | 22:29 |
hub_cap | did yall do the randomizing thing to it? | 22:29 |
grapex | vipul: lifeless mentioned that if we ran those tests with sqlite in memory only, we'd get rid of those parallel problems | 22:29 |
hub_cap | isint that what the nova/cinder/etal tests do? | 22:30 |
vipul | we probably should just do that... no point in having a separate file, since i think we teardown/recreate db | 22:30 |
vipul | on each test | 22:30 |
grapex | vipul: Yeah, we never actually make use of persiting the sqlite db. | 22:30 |
grapex | I'll make a blueprint to change that. | 22:30 |
vipul | #action grapex to file BP on in-memory sqlite | 22:30 |
steveleon | wouldnt a bug be sufficient? | 22:31 |
juice | I think it's just a param for connecting to sqllite | 22:31 |
vipul | steveleon, bug works too, shoudl be small | 22:31 |
grapex | steveleon: Is it breaking anything yet? | 22:31 |
*** carimura has joined #openstack-meeting-alt | 22:31 | |
juice | db:men or something like that | 22:31 |
SlickNik | rackers just want to flaunt the fact that they can create new bps :P | 22:31 |
steveleon | i havent seen | 22:31 |
steveleon | but it has been passing most of the time | 22:31 |
grapex | I say bp because we'll need to update redstack too. :( | 22:31 |
steveleon | i havent seen it fail running it locally | 22:32 |
SlickNik | Ah, I see grapex… | 22:32 |
steveleon | ok bp sounds good | 22:32 |
vipul | last action item... | 22:32 |
hub_cap | ok so the last action item is qutoas | 22:32 |
steveleon | i think it might just be a name change | 22:32 |
steveleon | so instead of specifying the filename, you specify ":memory:"... or something like that | 22:33 |
vipul | hub_cap you mentioned there was no consensus? | 22:33 |
datsun180b | that sounds about right | 22:33 |
hub_cap | wellllll..... vipul | 22:33 |
datsun180b | wrt :memory: and sqlite | 22:33 |
hub_cap | the consensus is that everyone has their own till someone ponys up and works on the kyestone one | 22:33 |
hub_cap | so that seems to me that we could do that as well | 22:34 |
hub_cap | we will be using repose so i dont think we will be contributing cycles to it, but we welcome reviews to makeing it a better system... | 22:34 |
hub_cap | i know currently we only have max volumes and max geebees | 22:34 |
vipul | i'd like to get a solution in there, that doesn't involve fixing up CI to support Java | 22:35 |
vipul | so that's why i lean towards an embedded solution | 22:35 |
hub_cap | sure, we might just keep the java bits internal | 22:35 |
vipul | a stop-gap until its added to keystone, or some place better | 22:35 |
hub_cap | apt-get install apache-tomcat ;) | 22:35 |
hub_cap | cool.. well that maeks the quotas conversation easy | 22:36 |
hub_cap | lets go on to CI tho as per th emeeting | 22:36 |
vipul | might be that simple.. but it'll be a much bigger deal in openstack-ci me thinks | 22:36 |
hub_cap | yup | 22:36 |
juice | hub_cap: why do you like the repose solution? | 22:36 |
vipul | yep, have an item to dicuss futher later anyway | 22:36 |
hub_cap | #topic testing-ci | 22:36 |
*** openstack changes topic to "testing-ci (Meeting topic: reddwarf)" | 22:36 | |
hub_cap | so i tihnk we got updated w/ whats going on w/ CI right? lets summarize | 22:36 |
hub_cap | #info SlickNik working on getting CI tests working w/ devstack vm gate, fixing small issues, support to come soon | 22:37 |
SlickNik | yes.. | 22:37 |
hub_cap | is that good? | 22:37 |
hub_cap | anything more to add SlickNik? | 22:37 |
*** djohnstone has quit IRC | 22:38 | |
SlickNik | #info dkehn also working on devstack-vm-gate | 22:38 |
SlickNik | nope that's it. | 22:38 |
vipul | should have it pushed up to openstack CI this week (hopefully) | 22:38 |
SlickNik | The black box tests should be good to go soon. | 22:38 |
grapex | SlickNik: Nice! | 22:38 |
dkehn | thats if no more issues | 22:38 |
vipul | yup | 22:39 |
SlickNik | Just some more closing up on the devstack-vm-gate issues that keep cropping up. :) | 22:39 |
*** djohnstone has joined #openstack-meeting-alt | 22:39 | |
hub_cap | thatll be so cool | 22:39 |
hub_cap | ok do we have any unit test stuffs to talk about? | 22:39 |
hub_cap | if so ill mod the title otehrwise ill skip it | 22:39 |
vipul | nope | 22:39 |
hub_cap | hokey | 22:40 |
hub_cap | #topic quota consensus | 22:40 |
*** openstack changes topic to "quota consensus (Meeting topic: reddwarf)" | 22:40 | |
hub_cap | so i feel like we have consensus, let me sumarize | 22:40 |
hub_cap | #info quota support that mirrors cinder/nova will be added to reddwarf for the short to medium term | 22:41 |
hub_cap | #info eventually we will use what the other openstack projects use but that has yet to materialize | 22:41 |
juice | but rackspace is using repose | 22:41 |
hub_cap | #info rax to use repose internally | 22:41 |
vipul | hub_cap.. quick question about repose.. won't you need to add repose APIs ? | 22:41 |
juice | can I ask why you guys like that solution | 22:41 |
hub_cap | juice: rax wrote repose, and uses it :) | 22:42 |
juice | hub_cap: that's a good answer | 22:42 |
hub_cap | vipul: ya if we _have_ to add apis we can | 22:42 |
vipul | hub_cap: ok.. | 22:42 |
juice | as a matter of design/architecture what do you like about it | 22:42 |
vipul | hub_cap: rate limits, we ok with similar approach to nova? | 22:42 |
hub_cap | rate limits will be another one too... | 22:42 |
hub_cap | vipul: ya i think so vipul, we should call them limits, not quotas | 22:43 |
hub_cap | to support rate and absolute | 22:43 |
vipul | yup.. limits.py, possibly a request filter | 22:43 |
hub_cap | juice: we are evaluating it now, so lets give u that answer next wk | 22:43 |
hub_cap | :D | 22:43 |
juice | okie | 22:43 |
hub_cap | djohnstone: is your man for that | 22:43 |
djohnstone | back looking at that tomorrow | 22:43 |
vipul | hub_cap: there may be two use cases, one a filter (rate limits) and quotas really are checked upon time of creation) | 22:43 |
hub_cap | he just started on it but he can give a summary next meeting | 22:43 |
vipul | so may make sense to have them different | 22:44 |
hub_cap | vipul: likely there will be 2 different things | 22:44 |
hub_cap | i just meant we need to support limits of all types | 22:44 |
hub_cap | not that the code shoudl be the same :D | 22:44 |
vipul | ya | 22:44 |
vipul | ok | 22:44 |
hub_cap | i mean, if yall get limits done and they are AWESOME then we might use them :P | 22:44 |
vipul | #action djohnstone to give us an update on Repose? | 22:44 |
hub_cap | lol question mark at the end of that hah | 22:45 |
djohnstone | thanks vipul | 22:45 |
cp16net | lol | 22:45 |
vipul | makes it optional :D | 22:45 |
hub_cap | hahah nice | 22:45 |
hub_cap | ok we feel good about limits? | 22:45 |
vipul | ok we good, juice? | 22:45 |
SlickNik | Sounds like a plan to me. | 22:46 |
juice | yup | 22:46 |
hub_cap | coolness | 22:46 |
hub_cap | #topic User Management | 22:46 |
*** openstack changes topic to "User Management (Meeting topic: reddwarf)" | 22:46 | |
vipul | this is regarding the BP linked earlier... | 22:46 |
vipul | we wnat to be able to control grants given to root user on 'enableRoot' | 22:47 |
SlickNik | esp was briefly mentioning it earlier as well... | 22:47 |
hub_cap | ah okey. shall we discuss the multi config file together? | 22:47 |
hub_cap | vipul: i dont blame u for that. i think we talked about that too a while ago | 22:47 |
vipul | yes... any opposition to having those grants live in a separate config (different from guestagent.conf) | 22:47 |
vipul | since dbaas.py -- has a ton of grants/sql statement hard coded | 22:47 |
steveleon | so is it established that there will be a new conf file used only for root-privileges purposes? | 22:48 |
vipul | possibly this would be a config file that is gearted towards configuring dbaas.py | 22:48 |
hub_cap | so _why_ do we need yet another conf file? | 22:48 |
hub_cap | why cant we just put anotehr option in the conf file | 22:48 |
hub_cap | i thought, when i read that last night, that we were putting it all in the standard reddwarf.conf and got confused | 22:48 |
datsun180b | dbaas.py is going to get even more grants and statements shortly :3 | 22:48 |
vipul | we _could_... although the thinking is that we're configuring a subset of the geust agent | 22:48 |
hub_cap | not the guest.conf | 22:48 |
vipul | no, not guest.conf that's diff | 22:49 |
hub_cap | vipul: but there is no notion of having > 1 config file anywehre in openstack... it just seems like its going against the current so to speak | 22:49 |
hub_cap | ok so these are run by the guest, right? | 22:49 |
hub_cap | the grants | 22:49 |
datsun180b | they are | 22:49 |
steveleon | correct | 22:49 |
hub_cap | why would the grants not be in the conf file that is given to the guest | 22:49 |
vipul | right... where do we move hard-coded sql statements | 22:49 |
steveleon | i was under the impression that you didnt want the option in the guestagent.conf | 22:50 |
hub_cap | steveleon: i was confused last night when i said that | 22:50 |
hub_cap | i saw reddwarf.conf i thought in that blueprint | 22:50 |
datsun180b | i vote pull them not into a static config file but as a module to be imported by dbaas.py | 22:50 |
esp | initially we were putting the full GRANT stmt in the config file which was pretty gross | 22:50 |
grapex | Is the idea that the image could be build with a conf file that lives in it with the grants, and the dynamic conf file would just point to it? | 22:50 |
steveleon | my opinion is to put them in the guestagent.conf | 22:50 |
esp | datsun180b: that's the approach sorta | 22:50 |
esp | so the ?.conf file will have a property: root_grant= create delete update alter …. | 22:51 |
vipul | datsun180b.. there are certain things may need to enumerated.. like a list of privs that guest agnet could construct a grant statement from | 22:51 |
hub_cap | they are config values.... everyone will have different config values for their setups | 22:51 |
steveleon | put a list of all the privileges that root will have in a config file.. preferably guestagent.conf | 22:51 |
esp | and we will use the properties to build the GRANT stmt in code. | 22:51 |
hub_cap | steveleon: it _only_ seems right to put them there steveleon... im sorry for confusion | 22:51 |
steveleon | and dbaas.py will read from it and generate a grant sql query | 22:51 |
hub_cap | i feel like the email i sent out last night has caused all this | 22:51 |
esp | nah, we've been going back and forth on this | 22:52 |
hub_cap | general rule of thumb. if its a config that only the guest will use, put it in the guest.conf | 22:52 |
esp | it's already changed like 5 | 22:52 |
esp | x | 22:52 |
hub_cap | if it sgonna differ from install to install put it in _a_ conf (not code) | 22:52 |
vipul | so... i see two tracks.. put them in a module imported by dbaas.py... another to add to reddwarf-guestagent.conf | 22:52 |
hub_cap | so given that both of those are true, it seems it should be ina config right? | 22:52 |
datsun180b | we have our own homegrown Query class to facilitate guest agent queries, we can build a Grant to go with it | 22:52 |
esp | yep, I see no big deal putting it into reddwarf-guestagent.conf | 22:53 |
hub_cap | esp: #agreed | 22:53 |
grapex | I like the config idea too. | 22:53 |
vipul | right, let's go with reddwaf-guestagent.conf | 22:53 |
esp | datsun180b: let's chat after, seems like that direction I'm going | 22:53 |
vipul | #info static grants to be configurable through reddwarf-guestagent.conf | 22:53 |
hub_cap | #agreed | 22:53 |
steveleon | another thing that surge from this discussion is the ability to have a disable-root feature | 22:53 |
SlickNik | I prefer having it in a conf, rather than a module since it really is configuration. | 22:53 |
cp16net | #agreed | 22:53 |
vipul | ok.. next item around this | 22:54 |
vipul | adding a new API to disable root user | 22:54 |
steveleon | this will make it easier for support to see if and how long the user have used root privileges | 22:54 |
vipul | #link https://blueprints.launchpad.net/reddwarf/+spec/revoke-root-user-api | 22:54 |
vipul | steveleon just filed | 22:54 |
*** DandyPandy has left #openstack-meeting-alt | 22:54 | |
vipul | any reason to not add this API? | 22:54 |
hub_cap | hmm... this is going to be a contention point :) | 22:54 |
datsun180b | esp: please do | 22:54 |
hub_cap | well... we dont add it cuz once u enable root your support model changes | 22:55 |
hub_cap | but thats a rackspace specific thing | 22:55 |
vipul | right, but you have a history of if it was ever enabled | 22:55 |
datsun180b | breaking the seal voids your warranty, in short | 22:55 |
vipul | so it's something that you could still use to determine that | 22:55 |
hub_cap | datsun180b: exactly | 22:55 |
hub_cap | vipul: there is, ther is a root history table | 22:55 |
grapex | I guess I don't see the point of disabling root once you have it, since by then the support model already changes. | 22:55 |
hub_cap | well the support model should not govern the code | 22:56 |
grapex | True | 22:56 |
hub_cap | and thats why i said "its a rax specific thing" | 22:56 |
vipul | grapex: there may be scenarios when the user needs it for a period of time to diagnose an issue.. but possible needs to turn it off when done | 22:56 |
hub_cap | so im kinda at odds w/ my brain here | 22:56 |
grapex | but I'm trying to figure out why someone would want that | 22:56 |
hub_cap | i see from a permissions standpoint | 22:56 |
hub_cap | dont want root being enabled remotely forever | 22:56 |
hub_cap | but want to get in, touch something, and get out | 22:56 |
hub_cap | right? | 22:56 |
grapex | vipul: I think then that may be a different concept. It seems like you're giving someone temporary root permissions, like say someone in support. Like it could be a mgmt api. | 22:56 |
esp | does the calling root create api to enable root multiple times have the same effect as resetting the root password? | 22:56 |
vipul | right, and another tangent.. problay wnat a role-based access to the 'enableRoot' API | 22:57 |
steveleon | hub_cap: correect | 22:57 |
grapex | esp: Yes | 22:57 |
vipul | hub_cap: exactly | 22:57 |
vipul | grapex: i don't see managemnt api something end user would have access to | 22:57 |
vipul | i see a 'dba' at some company that needs temporary elevated access | 22:57 |
hub_cap | ok i think that we need to talk internally about this | 22:58 |
vipul | hub_cap.. ok, we just filed this today.. please review, add comment to BP | 22:58 |
esp | yeah I'm not sold yet :) | 22:58 |
hub_cap | #action hub_cap to get back to vipul on root rmemove | 22:58 |
hub_cap | wow rmemove?!?! | 22:58 |
cp16net | yeah well we have history of when root was enabled | 22:58 |
hub_cap | #action hub_cap to learn how to type | 22:59 |
vipul | cp16net: right, that's what would be the determining thing for your suppor tmodel i'd imagine | 22:59 |
esp | cp16net: yeah the history thing is cool. we were pondering how disable would fit in | 22:59 |
vipul | esp: temporary elevated privileges | 22:59 |
datsun180b | how can we determine which users can and can't use which api functions? would that eventually just grow into ACLs on api calls? | 22:59 |
cp16net | yeah we need to talk about this internally to figure that out | 22:59 |
vipul | datsun180b: we need to add additonal roles i think to API | 23:00 |
vipul | enableRoot shoudl only be accessible with a higher privileged user i thnk | 23:00 |
hub_cap | we need a policy like nova possibly... | 23:00 |
vipul | that's a different discussion | 23:00 |
datsun180b | user, superuser, and mgmt? | 23:00 |
vipul | yep | 23:00 |
cp16net | that could be handled with keystone right? | 23:00 |
hub_cap | but it can be whatever u want it to be... its configurable (nova policy) | 23:01 |
hub_cap | exactly cp16net | 23:01 |
esp | maybe would could enable root with a timeout…but perhaps that just complicates things... | 23:01 |
hub_cap | esp: naw, some people want root 200% of the tiem :) | 23:01 |
cp16net | thats x2 | 23:01 |
datsun180b | just an authentication that doesn't allow renewals | 23:01 |
SlickNik | esp: I thought about that, but I don't like it... | 23:01 |
datsun180b | there's your timeout | 23:01 |
esp | yeah makes sense | 23:01 |
hub_cap | ok so we never changed topic to the dbaas.py/conf file, but we have consensus ya? | 23:02 |
hub_cap | ill topic change and jot it down | 23:02 |
vipul | oh yea, forgot that was a separate item | 23:02 |
vipul | we're good on that one now | 23:02 |
SlickNik | esp: I don't think that there would be a one size fits all timeout, so then we'd have to get into the business of configuring that, which could potentially get messy | 23:02 |
hub_cap | ok lets just #info it then | 23:02 |
datsun180b | throwing my hat in for that one | 23:02 |
esp | SlickNik: yep. I hear ya. | 23:02 |
cp16net | SlickNik: yeah that would be messy quickly | 23:02 |
vipul | #info grants will go into reddwarf-guestagent.conf, not a separate file | 23:02 |
hub_cap | #info guest conf for configurable sql queries until we have a better solution | 23:02 |
hub_cap | doh u beat me to it | 23:02 |
hub_cap | #topic open discussion | 23:03 |
*** openstack changes topic to "open discussion (Meeting topic: reddwarf)" | 23:03 | |
hub_cap | i dont have long, i have to run and clean my house (closing is thursday) | 23:03 |
cp16net | JOY | 23:03 |
hub_cap | thats my open discussion :) | 23:03 |
SlickNik | fun | 23:03 |
esp | hub_cap: congrats! | 23:03 |
steveleon | are you living in the bay-area now? | 23:03 |
vipul | #action vipul to file BP on additional roles in reddwarf (user, superuser, admin) | 23:03 |
SlickNik | FYI, it's worth a mention that the tests are successfully running on RAX cloud :) | 23:04 |
vipul | woah nice | 23:04 |
hub_cap | WOOO | 23:04 |
grapex | Cool | 23:04 |
esp | vipul: is that to address the revoke api call? or something else? | 23:04 |
hub_cap | steveleon: i will be flying out soon to look for a place, im in an apartment here | 23:04 |
cp16net | awesome | 23:04 |
hub_cap | in austin | 23:04 |
vipul | esp: it will be related to that... as well as limiting who can call 'enableRoot | 23:04 |
hub_cap | vipul: i tink that we should not be specific on that | 23:04 |
hub_cap | if we do a policy like nova does, it wont matter what _roles_ u want | 23:05 |
hub_cap | if u can say a user of role X can execute things in module Y | 23:05 |
hub_cap | which is what the nova policy file does | 23:05 |
vipul | hub_cap: ok, will mention that in BP.. have a policy that dictates RBAC | 23:05 |
cp16net | #define RBAC? | 23:05 |
vipul | role based access control :D | 23:06 |
SlickNik | Role Based Access Control, I believe. | 23:06 |
cp16net | ok :) | 23:06 |
hub_cap | vipul: yar | 23:06 |
hub_cap | it _kinda_ does that currently | 23:06 |
vipul | right, but it's limited to user/admin only? | 23:06 |
hub_cap | its limited to whatever u want really | 23:07 |
SlickNik | Currently just admin/non-admin, right? | 23:07 |
hub_cap | as long as u configure it | 23:07 |
hub_cap | https://github.com/openstack/nova/blob/master/etc/nova/policy.json | 23:07 |
hub_cap | u can make yoru own groups | 23:07 |
vipul | #info https://github.com/openstack/nova/blob/master/etc/nova/policy.json | 23:07 |
vipul | just what i needed | 23:07 |
hub_cap | its just a Yes/No system really, so u can make the groups yourself based on the expressions | 23:07 |
cp16net | nice | 23:07 |
cp16net | what applies this policy though? | 23:08 |
vipul | where do you implement the rule | 23:08 |
vipul | admin_or_owner example | 23:08 |
hub_cap | "admin_or_owner": "is_admin:True or project_id:%(project_id)s", | 23:08 |
hub_cap | "context_is_admin": "role:admin", | 23:08 |
hub_cap | those are at the top | 23:08 |
vipul | oh duh | 23:08 |
hub_cap | so u can say what the roles are :) | 23:08 |
hub_cap | and then put them accordingly in teh stuf down below | 23:08 |
hub_cap | :D | 23:09 |
SlickNik | I see. | 23:09 |
vipul | and it's just a filter that get's added to wsgi? | 23:09 |
hub_cap | now that im not 101% sure about but that _seems_ like itd be the only place for it | 23:09 |
hub_cap | i havent looked into how it works | 23:09 |
vipul | ok, cool that's a good start thanks for the info | 23:09 |
hub_cap | np!! | 23:10 |
hub_cap | i think itll hold us over till keystone has decent rbac | 23:10 |
hub_cap | god i wish thsi was all in nova-common | 23:10 |
hub_cap | err, oslo-incubator | 23:10 |
cp16net | yeah that _could_ work temp | 23:10 |
*** esp has quit IRC | 23:10 | |
hub_cap | ok im out of things to discuss | 23:11 |
hub_cap | anyone else? | 23:11 |
vipul | yea temp is fine | 23:11 |
vipul | nope.. i'm good | 23:11 |
*** esp has joined #openstack-meeting-alt | 23:11 | |
hub_cap | vipul: sweet | 23:11 |
hub_cap | welcome back esp | 23:11 |
hub_cap | :P | 23:11 |
vipul | excess flood? | 23:11 |
cp16net | esp's water was rising... | 23:11 |
cp16net | :-P | 23:11 |
esp | sorry.. | 23:11 |
vipul | heh | 23:11 |
hub_cap | his float bobber got too high and pulled the blug | 23:11 |
hub_cap | *plug | 23:11 |
hub_cap | #action hub_cap still cant type | 23:12 |
esp | man tough crowd today. | 23:12 |
hub_cap | wait thats mroe info | 23:12 |
hub_cap | LOL | 23:12 |
hub_cap | ok im gonna call this | 23:12 |
cp16net | keep trying and surely one day.... | 23:12 |
hub_cap | cp16net: LAWL | 23:12 |
hub_cap | #endmeeting | 23:12 |
*** openstack changes topic to "OpenStack meetings (alternate) || Development in #openstack-dev || Help in #openstack" | 23:12 | |
openstack | Meeting ended Tue Jan 29 23:12:26 2013 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 23:12 |
openstack | Minutes: http://eavesdrop.openstack.org/meetings/reddwarf/2013/reddwarf.2013-01-29-21.59.html | 23:12 |
openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/reddwarf/2013/reddwarf.2013-01-29-21.59.txt | 23:12 |
openstack | Log: http://eavesdrop.openstack.org/meetings/reddwarf/2013/reddwarf.2013-01-29-21.59.log.html | 23:12 |
hub_cap | u know we might not be the most productive but we are the most fun meeting :) | 23:12 |
vipul | good times | 23:12 |
*** robertmyers has left #openstack-meeting-alt | 23:12 | |
cp16net | peace | 23:12 |
*** hub_cap has left #openstack-meeting-alt | 23:12 | |
SlickNik | thanks all | 23:12 |
grapex | See you later! | 23:13 |
SlickNik | later... | 23:13 |
*** SlickNik has left #openstack-meeting-alt | 23:13 | |
esp | thx | 23:13 |
*** djohnstone_ has joined #openstack-meeting-alt | 23:14 | |
*** dkehn has left #openstack-meeting-alt | 23:14 | |
juice | late | 23:15 |
*** SpamapS has quit IRC | 23:15 | |
*** djohnstone has quit IRC | 23:16 | |
*** bdpayne has quit IRC | 23:16 | |
*** jcru has quit IRC | 23:17 | |
*** djohnstone_ has quit IRC | 23:18 | |
*** jdbarry has left #openstack-meeting-alt | 23:20 | |
*** grapex has quit IRC | 23:20 | |
*** bdpayne has joined #openstack-meeting-alt | 23:23 | |
*** cloudchimp has quit IRC | 23:27 | |
*** carimura has quit IRC | 23:34 | |
*** carimura has joined #openstack-meeting-alt | 23:34 | |
*** esp has left #openstack-meeting-alt | 23:37 | |
*** yidclare has left #openstack-meeting-alt | 23:40 | |
*** rnirmal has quit IRC | 23:50 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!