Tuesday, 2012-12-11

*** vipul is now known as vipul|away00:30
*** vipul|away is now known as vipul00:49
*** vipul is now known as vipul|away01:29
*** vipul|away is now known as vipul01:29
*** juice_ has quit IRC01:51
*** juice_ has joined #openstack-meeting-alt05:22
*** juice_ has quit IRC09:07
*** cp16net is now known as cp16net|away15:22
*** cp16net|away is now known as cp16net15:24
*** rnirmal has joined #openstack-meeting-alt15:36
*** juice_ has joined #openstack-meeting-alt16:04
*** esp1 has joined #openstack-meeting-alt18:15
*** esp1 has left #openstack-meeting-alt18:16
*** esp1 has joined #openstack-meeting-alt18:33
*** esp1 has left #openstack-meeting-alt18:40
*** cp16net is now known as cp16net|away19:39
*** cp16net|away is now known as cp16net20:16
*** juice_ has quit IRC20:37
*** juice_ has joined #openstack-meeting-alt21:00
*** vipul is now known as vipul|away21:09
*** vipul|away is now known as vipul21:09
*** vipul is now known as vipul|away21:24
*** vipul|away is now known as vipul21:29
*** hub_cap has joined #openstack-meeting-alt21:58
*** SlickNik has joined #openstack-meeting-alt21:59
hub_cap#start-meeting reddwarf22:00
hub_caplol did we lose our bot?22:00
SlickNikwhat's his name?22:00
hub_capor did i muck it up22:00
hub_cap#startmeeting reddwarf22:00
openstackMeeting started Tue Dec 11 22:00:35 2012 UTC.  The chair is hub_cap. Information about MeetBot at http://wiki.debian.org/MeetBot.22:00
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.22:00
*** openstack changes topic to " (Meeting topic: reddwarf)"22:00
openstackThe meeting name has been set to 'reddwarf'22:00
hub_capi mucked it up :D22:00
*** esp1 has joined #openstack-meeting-alt22:00
vipulyo22:01
SlickNikyo yo yo22:01
grapexGreetings.22:01
hub_capok so lets start w/ last wks action items22:01
hub_caphttp://eavesdrop.openstack.org/meetings/reddwarf/2012//reddwarf.2012-12-04-22.00.html22:01
*** datsun180b has joined #openstack-meeting-alt22:01
hub_cap#topic update to action items22:01
cp16nethola22:01
*** openstack changes topic to "update to action items (Meeting topic: reddwarf)"22:01
hub_caplet me start by sayign i didnt update the meeting page for reddwarf, but i think we have some stuff that got moved to chat about22:01
hub_capso22:02
hub_capis dkehn around?22:02
SlickNikdkehn is in the air, so I can give an update.22:02
datsun180bhello there22:02
hub_caphah nice SlickNik tell us about keystone22:02
SlickNik(he's on an airplane :)_22:02
hub_capdid yall figure out all u need about the daffy users (no pun intended)22:02
*** saurabhs has joined #openstack-meeting-alt22:02
SlickNikthere's some random picking of users in some tests that might need it.22:03
SlickNikSo we decided that we'd create them tentatively and once we have the tests running, we would clean the list up if needed.22:03
hub_capsounds good22:03
hub_capnext22:03
cp16netgravy22:03
hub_capvipul: did u file a bug in regard to tripelo image builder?22:03
SlickNikcool beans22:03
vipulhub_cap: I filed a blue print22:04
vipul# link https://blueprints.launchpad.net/reddwarf/+spec/migrate-to-diskimage-builder22:04
vipulugh22:04
vipul#link https://blueprints.launchpad.net/reddwarf/+spec/migrate-to-diskimage-builder22:04
hub_caphehe gotta love it22:04
hub_capvipul: even better good sir22:04
vipuljuice_ and kaganos are working on it22:05
SlickNikyes, everyone here is filing BPs these days.22:05
hub_capive approved it. id love to see it done22:05
hub_capyup thats great news22:05
SlickNikMake hay while the lawyers let us… or something… :P22:05
vipulwe did have some issues to bring up22:05
vipulmaybe reserve that for later?22:05
hub_capya go head and edit the meeting adn put a space for it on the wiki22:05
hub_capwiki.openstack.org/Meetings/RedDwarfMeeting22:05
hub_caperr on the page not wiki, lol22:06
hub_capso vipul and i talked about the image stuff in regard to percona22:06
hub_capsince the images wont be in reddwarf, we can build any image on earth and not really worry about whats inside it22:06
vipulhub_cap, and that's something we'll need further discussion on22:06
hub_capso there are no problems w/ having specialized images for companies needs22:06
hub_capvipul: hmm ok sounds good, was there a change?22:07
hub_capor will it still exist as it stands currently?22:07
vipuljuice_, SlickNik?22:07
juice_so the idea is that...22:07
SlickNikYeah, we just had a discussion with the tripleo folks and there's a change from that end...22:07
hub_capmy stance is as long as its not _in_ reddwarf have at it22:07
SlickNikBasically, they want the individual teams to own the elements (flavours) that they need built.22:07
hub_capSlickNik: do tell22:07
hub_caphonestly i figured it woudl be that22:08
hub_capit didnt really make sense that they would own the images22:08
SlickNikSo they want the scripts/code for the image building to reside in red-dwarf.22:08
hub_capso yall can have a repo/image you use and reddwarf can use stock mysql22:08
hub_capand we can have one we use as well22:08
*** ddemir has joined #openstack-meeting-alt22:08
vipulonly issue I have with that is we'll never be testing our imags in Openstack CI22:08
juice_there is a real subtle difference between the two flavors22:09
juice_most of it will be shared22:09
juice_so having a repo for one file is a bit over kill imho22:09
hub_capvipul: ya i know, we have our own test infra to test out our stuff as well22:09
grapexSlickNik: Has image-building been generalized in Nova to the point where scripts and code to build images in Reddwarf would work with all virt drivers in Nova?22:09
hub_capjuice_: its not about the "overkill"22:09
hub_capits about whethere we, as reddwarfers shoudl be supporting multiple flavors22:09
hub_capi understand HP wants to support it22:09
hub_capbut reddwarf shouldnt be thought of as HP and/or rax22:09
hub_capif a 3rd company comes in and says22:10
SlickNikGrapex: it's a work in progress, but they're getting there from what I understand.22:10
hub_capi want my own flavor of mysql, johhny's mysql as a image22:10
cp16netand they want their own type of flavor they should be able to do that22:10
hub_capdo we suppor that as well?22:10
grapexSlickNik: Wow. Cool.22:10
cp16netyeah agree hub_cap22:10
grapexThat'll be nice.22:10
hub_capwe shoudl support stock mysql22:10
hub_capas deployed by ubuntu22:10
cp16netyeah something as a standard22:10
hub_capotherwise we eventually end up w/ pain22:10
vipulyep, completely agree, but at the same time, we need to enable that 3rd companay a way to come in and leverage existing image building tools we have in reddwarf to create their own22:10
hub_capvipul: absolutely22:11
vipulso we need to think of a way to possibly generalize how we create these22:11
hub_capand yall will build that path cuz u will be using percona image22:11
*** imsplitbit has joined #openstack-meeting-alt22:11
hub_cap+1 vipul22:11
hub_capid love to have a way to generalize them, but again, when we run ci against it on jenkins, itll be on stock mysql22:11
hub_capand a team can devote their own resources to running thier own custom images...22:11
cp16netwe need to have some sort of script/how-to/etc.. to make those images22:11
cp16netright22:12
vipuli'd like to be able to provide a flag to Devstack or whatever, and have it run 'my' flavor or any other custom flavor22:12
vipulmaybe what runs in CI is the image without that flag22:12
hub_capthats not a bad idea ata ll devstack22:12
hub_cap*at all*22:12
grapexhub_cap: We could make a test config to choose the image run by the tests. If someone wanted to use a different image they could then run their own CI job.22:12
hub_capgrapex: ya that works too22:13
hub_capwe can work w/ monty and devstack team on that22:13
hub_capjust like when we run on debian, instead of ubuntu, we have to do that internally... nova def cares not about integrating w/ multiple os'22:13
vipulk, i think we need an offline discussion to further clarify things22:14
hub_capand we have our own jenkins and such to run those jobs... im sure monty can work something otu for u ;)22:14
hub_capvipul: def22:14
hub_caplets move on22:14
vipulk22:14
SlickNik+1 on offline discussion, but let's move on.22:14
hub_capSlickNik: default user?22:14
hub_capany update to that... do yall _need_ it to be config'd?22:14
SlickNikYeah, Steve and I looked at this. The reason I needed to use root was because the my_cnf was failing on my older redstack box for some reason.22:15
SlickNikI verified that it does run correctly now, and creates the os_admin user.22:15
hub_capperfect22:16
hub_capso we can squash that one?22:16
SlickNikWe need to talk about whether those users will work for us @HP or whether we will need some other my_cnf.22:16
*** durnas has joined #openstack-meeting-alt22:16
hub_capwas a bug/BP ever filed for that?22:16
hub_capok SlickNik lets leave it open then22:16
SlickNikyes, there was, I'll update it.22:16
*** durnas has quit IRC22:16
steveleonyou can use "root" with no problem22:16
hub_cap#action SlickNik to discuss w/ HP about os_admin22:16
steveleonas long as you enable it via the reddwarf-cli22:17
*** durnas has joined #openstack-meeting-alt22:17
vipulhub_cap, SlickNik, steveleon: we may wnat to stick to the default user for now22:17
hub_capvipul: config'ing a default user is very little work tho22:17
hub_capso if u want ot do it, say the word22:17
hub_capnext, esp1 and grapex22:17
hub_caplets talk test22:18
vipulok22:18
steveleonthat default user cannot be "root"... root is already a user automatically22:18
steveleonso we can just leave it as "os_admin22:18
*** jcooley_ has joined #openstack-meeting-alt22:18
steveleon for now22:18
esp1yep I got some good feedback from you and grapex regarding tests22:18
vipulyep, should wait til we get some tests for guest agent22:18
vipuland are ready to implmeent some features before changing users22:18
grapexRe: tests. I've had fairly bad luck getting an active instance.22:19
esp1grapex: yeah I can only use flavor 1 to work currently.22:19
vipulesp1, grapex: i think there was an effort by esp1 to start a new set of integration tests, since the existing ones have a ton of dependencies and assumptions22:19
grapexNew set? I think it was just a new group22:20
esp1it's just a new group22:20
grapexBut anyway, you might not want to do that. I recently pushed a commit that took the MGMT API out of the "blackbox" group of tests.22:20
esp1was going to name it simple-blackbox-group or something less exciting22:20
cp16netgrapex, esp1: a new group being a subset of all the tests that are all ready there?22:20
grapexSo now, if we run "./redstack int-tests --group=blackbox --stop" it should only run tests we expect to work.22:21
vipulso do those work at this piont?22:21
vipulor are there other things we need to debug through22:21
grapexThe MGMT API being used in the tests was one of the biggest problems, but it turns out they were already well seperated from the other tests.22:21
esp1cp16net sort of.  I currently have about 60 tests running in a consistent way for reddwarf-int22:21
cp16netesp1: ok22:21
grapexvipul: I can't get an active instance so right now only a handful work for me. :(22:21
grapexBut in theory all of them should run22:22
grapexkeep in mind ATM the instance created by a test doesn't have a volume either22:22
vipulok good info22:22
hub_caphow come weve dropped support for volume grapex? especially if vipul fixed it :D22:22
grapexSo all it does it create a volume-less instance, and then run some actions against it such as resize. It seems like a goal we should be able to hit. Then we can turn on the creation of the volume in the test config.22:22
hub_capdo the tests still fail w/ volume?22:22
esp1grapex: if it helps I have my configs with volume support set to False.22:22
esp1hub_cap: I think so but I need to run those tests again to make sure.22:23
grapexhub_cap: We turned it off awhile ago. I noticed a failure in the taskmanager logs, but my VM isn't on par at the moment.22:23
grapexMaybe we can turn it back on.22:23
vipulhub_cap, grapex: I did verify that we can boot wiht volume support on22:23
vipulafter that fix22:23
hub_capsweet lets first get them runnin22:23
hub_capand then readd volume tests22:23
hub_capsound good?22:23
vipulso not sure if there are subtle differences in the tests usage of volumes22:24
esp1yep22:24
hub_capid like to get them gating22:24
vipulhub_cap: yea good plan22:24
hub_capwell we will support default iscsi volumes vipul22:24
hub_capsupported by ubuntu's openiscsi version (Whateve that is :D )22:24
vipulesp1, grapex: are you guys sync'd up?22:25
hub_capokey, thats great work grapex esp122:25
hub_capya we dont want duplication22:25
hub_cap#reddwarf is still a barren chat wasteland, lets try to use it more22:25
esp1I believe so22:25
hub_capgood deal, moving on!22:25
hub_capso ill knock out both of mine22:26
hub_capmgmt api-no progress, still on my list22:26
hub_capworking on oslo updates still22:26
esp1grapex: feel free to yell at me later if you want to compare configs22:26
hub_capand ovz, we will have a resource devoted begin of yr so says the mgr folk here22:26
grapexesp1: Will do.22:26
vipulnice22:26
hub_capya itll be super awesome22:26
SlickNikcool..22:27
hub_capi really want to get it in the public22:27
hub_capive been pushing here22:27
hub_captrying to get it bumped higher22:27
vipulyep, looks like the critical things are in place now22:27
vipulsuch as a keernel that support ovz22:27
vipulso let us know when you guys are ready - we can possibly get someone here to help22:28
hub_capyup vipul that is super awesome thats _the_ critical thing for sure22:28
hub_capvipul: cool! i know we have the driver 90% done so im not sure what we will need to do22:28
hub_capbut i _do_ know once we push it that there will need to be work done to it22:28
hub_capso its less rax specific... we could have a goofy default or formula here or there that works well for us but maybe not everyone22:28
vipulk sounds good22:29
hub_capso quotas.... has anyone talked to the openstack gurus on high about quota support?22:29
hub_capi have _not_22:29
vipulnope22:29
SlickNiknope22:29
SlickNikstill pending22:29
vipul#action check with openstack folks on commonized quotas22:29
hub_capcool. i will say its not super high prio for us right now22:29
hub_capwe will likely be using repose22:29
vipulrepose does quotas too?22:30
vipulor just rate limits22:30
hub_caphmm i thought it did do quotas22:30
vipulnot sure..22:30
hub_caphmm ive been told it does, maybe its internal22:31
hub_capif so thats weak22:31
hub_capand we need support for it publicly22:31
vipulyea everything i see seems to be a high-level authz filter and rate limits22:31
hub_cap#action hub_cap to find out whats up w/ repose in regard to quotas22:32
hub_capill figure it out22:32
hub_capso vipul did u ever set up a roadmapping session w/ your team?22:33
SlickNikYeah, that's what the wiki at openrepose.org seems to think... no info on quotas...22:33
hub_capshould we wait till the new yr?22:33
vipulno, i think this may need to wait22:33
vipulyep, we've only got 1 more week and a shutdown22:33
hub_capok lets wait then till new yr22:34
hub_capits prolly easiest anyway to wait till we are all avail, we shut down too here :P22:34
hub_capok then we are DONE w/ action items, woot!22:34
hub_caplooking@ the meeting it seems there is not much more that we dont have ironed out alrady, sans what vipul talked about earlier22:35
hub_capbut we talked about that _kinda_ right vipul?22:35
hub_capim ok w/ discussing it more here if there is nothing else to talk about22:36
SlickNikI just wanted to give an update on the devstack integration piece...22:36
vipulyes22:36
vipullet's update on things that weren't brought up22:36
SlickNik#link https://github.com/dkehn/devstack22:36
hub_capok cool22:36
hub_cap#topic devstack integration22:36
*** openstack changes topic to "devstack integration (Meeting topic: reddwarf)"22:36
SlickNikDon and I got reddwarf API and taskmgr up and running under devstack.22:37
hub_capvery nice!22:37
hub_capare we lib/reddwarf?22:37
SlickNikYes! :)22:37
hub_cap:D very nice22:37
vipulSlickNik, i think we're close to pushing upstream.. any ETA22:37
SlickNikWe're still working out how we're going to build the guest-image, but that's the discussion we're going to have.22:38
hub_capya we will prolly need to do the guest-image stuffs before we push upstream right?22:38
cp16netgj SlickNik22:38
SlickNikyup.22:38
hub_capthatll be a fun one! any progress on the guestimage stuff to date?22:38
SlickNikWe still need to figure out where to pull the right "elements" from, but we've got the tripleo disk-imagebuilder integrated…22:39
hub_capdefine elements plz sir22:39
hub_capfor those of us (like me) who arent familair w/ tripelo imagebuilder22:39
SlickNikBasically flavors for disk-imagebuilder.22:39
durnascomponents that are composed together to make up a single image.22:39
vipulthink of them as toppings ?22:40
hub_capmmmmm toppings22:40
*** yidclare has joined #openstack-meeting-alt22:40
durnasthe example the d-i-b folks use is some bizarro driver & centos.22:40
SlickNiklol, I've heard them called at least 4 different things today :P22:40
durnascombine the two together & you get centos for your crazy setup.22:40
hub_capok cool. so one thing that we shoudl try to solve is do we put the reddwarf-guest _in_ the image22:40
hub_capor do we inject somehow on boot22:40
durnasit's pretty fluid, but think 'elelment' will be around for at least another week :)22:41
hub_capright now redstack scp's it over in a very ghetto way22:41
hub_capthat worked great for development when i was drinking 64oz of coffee at 4am coding it22:41
vipulI think we need the guest in there, to be able to really call it s 'reddwarf' element22:41
durnasyup. we might stay ghetto-ish in the vein of getting it in.22:41
hub_capok given that does it need to be packaged somehow?22:41
vipuland it is also nice for development in that you can make a change without baking another image22:42
durnaswe can keep it rsync for now22:42
hub_capvipul: yes sir it is22:42
hub_capdurnas: cool, im ok w/ that22:42
hub_capas long as we dont ahve to bake a new image for small guest updates when we dev22:42
vipuli think for a production deploy though, we'll both need some other packaged agent22:42
hub_capdef vipul we do that22:42
SlickNikYeah, I'm good with rsync for now. Maybe PyPi later?22:42
hub_capwell pypi would assume latest is always there22:43
juice_we can create another flavor (err element) that has it baked in22:43
juice_it'll be like cheese stuffed crust22:43
hub_capjuice_: is that chicken b4 the egg? :D22:43
durnasvipul: at some point, it might make sense for guest-agent to be a separate build/package22:43
juice_hub_cap: more like a turducken22:43
hub_capmmmmmmmmmm turducken22:43
vipulwe should talk about that.. durnas22:43
hub_capdurnas: ours is a separate pkg, it works nicely22:44
vipulhub_cap: any thoughts on moving guest agent out of reddwarf repo?22:44
durnasyep.22:44
hub_capput it in the image and start deploying22:44
hub_capvipul: not opposed in any way :)22:44
vipul#action vipul to move guest agent bits out of Reddwarf into reddwarf-guestagent22:44
grapexvipul: Any reason to move it out?22:44
hub_capbut i would be opposed to putting pkg scripts in to it fo the sake of imaging :D22:44
grapexvipul: I'd rather not22:45
vipulI think for testing, packaging it makes sense for it to be self-contained22:45
hub_caphaah grapex no like distributed projects22:45
hub_capi dont blame him we have a lot of "instrumenting" to do here22:45
hub_capw/ the 900 projects we have goin22:45
vipulwe can make changes to guest_agent without affecting reddwarf and vice-versa22:45
grapexIf we can keep the reference agent where the reddwarf code is, when we add new features we can keep the reference agent close to the other changes22:45
vipulright, but the theory is that we'll have redstack-vm-gate anyway22:45
vipulso you'll always be testing tip of everything22:45
durnasits true. but you can also control that with build rules22:45
SlickNikgrapex: Are there any dependencies on shared components between guest-agent and rest of reddwarf/common?22:46
SlickNikor hub_cap...22:46
grapexSlickNik: Totally.22:46
vipulSlickNik, grapex: that's a good point22:46
hub_capya we might have to have a reddwarf-common ;)22:46
vipulthere's a ton of Oslo suff that's shared22:46
grapexWe'd have to duplicate a lot of code to move the reference agent out22:46
hub_capvipul: there is much less now thats in our repo, but the wsgi one is a big one (which the guest doent need)22:47
grapexIs HP planning on using the reference agent?22:47
vipulgrapex: yes, that is the plan22:47
hub_capsweet22:47
hub_capwell im not sure we need to solve this now22:47
vipulwe'd like to put some of our maxwell bits in down the road, but first get geust agent a bit more solidified22:47
vipulso we're adding unit tests, etc to it now22:48
hub_capwe _know_ that the guest shoudl be 1) easily avail for development and 2) distributable in a way for deployments22:48
grapexOk. I'm sure we're all smart enough to make it work even if it was 57 repos.  OpenStack is a large enough project that the manpower is out there. I do think though that when new features are introduced it would be nice to show the reference guest code in the same commit as the reddwarf code.22:48
hub_capwe can meet those req's in a bunch of diff ways i bet22:48
vipulgrapex, hub_cap: Yep, let's hold off on the move, i think we need to think of the implications a bit more22:48
steveleonwe can make guest-agent into its own repo with all the oslo stuff in it. We can refine it later22:49
vipul#action do not do move guest-agent out yet22:49
hub_capsteveleon: the oslo stuff is not 100% of what we have in reddwarf.common sadly22:49
vipulsteveleon: yes, but then we'd need to keep them in sync also22:49
SlickNikshouldn't it be more like #no-action do not move guest-agent out yet.. heh...22:49
hub_capthere is def more too it, but im trying to get most of it merged into oslo22:49
vipulso upgrades need to be coordinated between reddwarf and agent22:49
cp16netagree22:49
hub_caplol SlickNik22:49
steveleonthats true.. with keeping in sync22:50
hub_capok so seems like we should discuss that more off line22:50
hub_capand we also need to discuss the image builder offline22:50
vipulyes.22:50
hub_capid like to bring mordred in on it22:50
vipulwhen is a good time to talk about those?22:50
hub_capim always in #reddwarf22:50
SlickNikyes.22:50
hub_capbut im really watching between 9~4 cst22:51
vipulk let me coordinate on our end here, and we'll meet with those guys in #reddwarf22:51
hub_capvipul: yup22:51
hub_capthatd be great22:51
hub_capand we can talk about turducken and sprinkle toppings22:51
hub_cap:D22:51
SlickNikwith elements it would be "image-create turkey duck chicken" to get your turducken image, I think… :)22:52
cp16netlolz22:52
vipulnice :)22:52
hub_cap#action hub_cap SlickNik vipul to discuss w/ mordred the implications of multiple images housed in reddwarf and how we woudl do it22:52
hub_capSlickNik: haha22:52
hub_capso i guess that brings us to the freeform jazz portion of the meeting22:53
hub_cap#topic open discussion22:53
*** openstack changes topic to "open discussion (Meeting topic: reddwarf)"22:53
vipulsteveleon: how are the guestagent unit tests coming?22:53
hub_capanyone have anything to add here?22:53
steveleonwe have been tackling down class by class22:54
hub_capguestagent? as well as reddwarfclient?22:54
hub_capsweet!22:54
steveleonwe are starting with MySqlAdmin first22:54
steveleonThen annashen and I will divide and conquer22:55
steveleonhub_cap, just guestagent22:55
hub_capsteveleon: do yall have a BP in regard to this?22:55
steveleonddemir is working on the reddwarf-client22:55
steveleonBP, meaning blueprints? no22:55
hub_capsure im just elated that yall are doing the unit test stuff!!!!22:55
annashenhub_cap: not yet, will work on BP22:55
hub_capannashen: <322:55
hub_caplets try to make the commits small, we all knows what happens when u push a huge commit ...cough cough... oslo updates22:56
cp16netGROSS22:56
hub_caponce u get MySqlAdmin up, lets gerrit review it22:56
hub_capcp16net: lol22:56
cp16netyeah there is no nice way to see the diffs between patch sets...22:56
annashensteveleon: yeah, BP == blueprint,  proposal basically22:56
steveleonyes. We will be committing each unittest class as they are ready22:56
cp16netjust checking it all out locally...22:56
hub_capawww ya steveleon awesome22:57
steveleonbecome ready*22:57
hub_capcp16net: ya so that is annoying, diffing patchsets is not supported in gerrit22:57
cp16netshould open a bug22:57
cp16net:-P22:57
hub_capso if u have > 1 patchset try to put whats in the newest or what u fixed in a comment22:57
hub_capi did that for _only_ the last patchset of mine...sry22:57
cp16netyes that would be a good practice22:57
steveleonno sure if i was looking in the right place, but it seems that we dont have much unit tests22:58
hub_cap#info diffing patchsets in gerrit is not implemented. try to put a comment w/ what you did on each patchset after the first one22:58
hub_capsteveleon: we dont have much at all22:58
steveleonall the tests under reddwarf.tests seem to be integration tests22:58
hub_capi started writing them a while ago but we lost track of them and focused on integration22:59
vipulsteveleon: yep, i think we'll need to spend some more time on getting some more unit test coverage all around22:59
grapexLet's focus on the coverage missing right now.22:59
hub_capyup and we can make new features gate on unit tests as well, and bugfixes once we get to > 8% coverage :D22:59
steveleonok.. cool.. just wanted to make sure if there were any unit tests already there22:59
hub_capsteveleon: sadly no /sadface23:00
cp16netis that all we have right now? 8%?23:00
grapex78%23:00
cp16netok23:00
hub_cap34.85% of statistics are made up cp16net23:00
steveleoncool.. we will start by attacking the guest agent first... since it seems to be the most isolated component23:00
cp16netREALLY?23:00
hub_cap:P23:00
cp16neti'll believe that23:00
vipul78 seemss kinda high :)23:00
SlickNiklol...23:01
hub_cap78 is our integration tests says grapex23:01
hub_capunit is non existing :D23:01
vipulah ok23:01
hub_caphence the 8% :P23:01
vipulanything else anyone?23:02
hub_capya23:02
hub_capid like to discuss oslo23:02
grapexSo is the idea to gate just on "unit" tests?23:02
esp1I think so...23:02
SlickNikNope, unit + integration I think...23:02
vipulgrapex: no no, gate on unit + live integration tests23:02
grapexOk, I concur.23:03
vipullive integration = devstack iwth redstack flag23:03
steveleonwe should gate on all tests23:03
hub_capyes that makes sense23:03
cp16neti think it should be on both if we have both of them23:03
SlickNikThat's better :)23:03
grapexDon't get me wrong, I don't mind duplicate coverage. I just want to focus on whats missing.23:03
hub_capvery much so23:03
steveleonwe should have a small set of smoke tests as well.. for faster gating, if needed23:03
SlickNikYeah, we should gate on the kitchen sink — if it makes sense and doesn't take forever.23:03
vipulalthough for local developement, having unit tests to run prior to commit is super nice23:03
hub_capSlickNik: if it contains a turducken yes23:03
* SlickNik thinks hub_cap skipped his lunch today :P23:04
hub_caphaha yup23:04
esp1vipul's a vegetarian23:04
vipulall this talk about meat..23:04
hub_capok vegan turducken23:04
cp16netdamn makes me hungry23:04
grapexvipul: So right now the integration tests should be runnable via tox in ten seconds or less. But I agree, more focused unit tests would be nice.23:04
hub_capspinach, kale, and wheatgrass23:04
vipulgrapex: Yep, the fake mode tests to run fast, but as we add code, we'll need to get in a habit of unit testing things we develop23:05
esp1yeah we have a test case that waits for the guest agent to return 'ACTIVE' takes like 5 mins.23:05
hub_capyes we will want to have ot be able to rely on those when deving locally23:05
hub_capand then wait forever for them to run in stackforge jenkins via real integration tests ;)23:06
esp1ok23:06
vipulyep i think nova gate takes upwards of 25 mins23:06
vipulso not a huge deal, it's mordred's problem23:06
cp16netyeah whats the rush when its running on jenkins... as long as its not taking >6 hours or something23:06
hub_capHA23:06
SlickNikI agree…cloud compute is cheap, dev cycles are expensive…:)23:06
* cp16net agrees23:07
vipulhub_cap: oslo?23:07
hub_capYS!23:07
cp16netwhen someone breaks something fundamental to the system it should yel... :)23:07
hub_capso ive got the mgso in regard to oslo, ive got all the binscripts running and im wading thru getting an instance to come online23:07
hub_capthe service stuff was painful but its done now23:08
hub_capive had a few reviews in oslo done/pending23:08
hub_caphttps://review.openstack.org/#/c/17615/23:08
hub_caphttps://review.openstack.org/#/c/17559/23:08
hub_caphttps://review.openstack.org/#/c/17386/23:08
hub_capso things are running smoothly but its going to be a few more days b4 its completely ready, and likely a patchset or 2 more23:09
vipulsweet, are we waiting on those patches to land into Oslo before merge ours?23:09
hub_capvipul: all but one are merged23:09
hub_capbut no we arent23:10
jcooley_ok, i'm way behind... but what is Olso?23:10
vipulopenstack-common23:10
vipulit's new incarnation23:10
hub_capive basically coded our own version of those in reddwarf.common but id like to remove them in favor of them being _in_ oslo23:10
jcooley_ah. nice.23:10
hub_capso itll be code removal once that last one in particular gets merged23:10
jcooley_so RD common gets smaller :)23:10
hub_capand one more is inflight but its got work to do23:10
hub_capjcooley_: precisely23:10
hub_capas small as possible23:11
*** jdbarry has joined #openstack-meeting-alt23:11
cp16netyay23:11
jcooley_excellent!23:11
hub_capive deleted config.py completly23:11
SlickNiksweetness.23:11
cp16netalright we done?23:11
hub_capyup, we are going ot try to rely on openstack common and wrap it when needed, but rather apply fixes to oslo instead of putting htem in our codebase23:11
vipulgood stuff hub_cap, looking forward to getting that merged23:11
hub_capvipul: i know!!!! :P23:12
hub_capme223:12
jcooley_hub_cap: great stuff!23:12
hub_cap#action hub_cap to get oslo update merged!!!!23:12
hub_capso im out of stuff to talk about23:12
cp16netw00t <3 hub_cap23:12
vipullet's end on a positive note :)23:12
SlickNikhells yea!23:12
hub_capvipul: easy23:13
hub_capturducken23:13
hub_cap#stopmeeting23:13
hub_capAWWWWWW FAIL23:13
hub_cap#endmeeting23:13
*** openstack changes topic to "OpenStack meetings (alternate) || Development in #openstack-dev || Help in #openstack"23:13
openstackMeeting ended Tue Dec 11 23:13:31 2012 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)23:13
openstackMinutes:        http://eavesdrop.openstack.org/meetings/reddwarf/2012/reddwarf.2012-12-11-22.00.html23:13
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/reddwarf/2012/reddwarf.2012-12-11-22.00.txt23:13
openstackLog:            http://eavesdrop.openstack.org/meetings/reddwarf/2012/reddwarf.2012-12-11-22.00.log.html23:13
SlickNikvegan even..23:13
hub_caphehe23:13
hub_capok time to brave the Austin cold. cu guys later23:13
SlickNiklaters23:14
hub_captomorrow migth _not_ be good for a chat w/ mordred23:14
hub_capwe are in planning23:14
hub_capso maybe thr?23:14
vipulk, i was shooting for tomororw23:14
vipulbut i'll check with him23:14
jcooley_hub_cap: vipul: tomorrow's ok for mordred.23:14
hub_capok, will that hamper work on anyone on your team if we dont do it tomorrow?23:14
vipuljcooley_ can he do thursday?23:14
hub_capjcooley_: my day is real tight tomorrow23:14
jcooley_yes, thursday works23:15
hub_capgiven the beginning of our iteration23:15
vipuljcooley_ and mordred share an office, so if yo uneed to reach him ;)23:15
hub_capcool ill be round all day on thr, just hit me up in #reddwarf23:15
hub_capjcooley_: gooooood to know23:15
hub_cap:D23:15
hub_captell him <3 from me :P23:15
jcooley_it's handy sometimes :)23:16
hub_capl8r all23:16
jcooley_cheers23:16
vipulsee ya23:16
SlickNiklater23:16
*** vipul has left #openstack-meeting-alt23:16
grapexAdios23:16
*** ddemir has left #openstack-meeting-alt23:16
esp1thx23:16
*** esp1 has left #openstack-meeting-alt23:16
*** datsun180b has quit IRC23:22
*** esp1 has joined #openstack-meeting-alt23:34
*** imsplitbit has quit IRC23:36
*** cp16net is now known as cp16net|away23:43
*** cp16net|away is now known as cp16net23:43
*** esp1 has left #openstack-meeting-alt23:47
*** yidclare has left #openstack-meeting-alt23:49

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