| *** sabeen1 has joined #openstack-tailgate | 00:39 | |
| *** sabeen2 has joined #openstack-tailgate | 00:46 | |
| *** malini has joined #openstack-tailgate | 00:47 | |
| *** malini has left #openstack-tailgate | 00:48 | |
| *** sabeen1 has quit IRC | 00:48 | |
| *** jasonsb has quit IRC | 00:58 | |
| *** jasonsb has joined #openstack-tailgate | 00:59 | |
| *** zz_dimtruck is now known as dimtruck | 01:02 | |
| *** jasonsb has quit IRC | 01:03 | |
| *** sabeen2 has left #openstack-tailgate | 01:36 | |
| *** sabeen1 has joined #openstack-tailgate | 01:37 | |
| *** jasonsb has joined #openstack-tailgate | 03:23 | |
| *** sabeen1 has quit IRC | 05:35 | |
| *** sabeen1 has joined #openstack-tailgate | 05:36 | |
| *** ig0r_ has joined #openstack-tailgate | 05:51 | |
| *** ig0r__ has quit IRC | 05:55 | |
| *** sabeen1 has quit IRC | 06:02 | |
| *** dimtruck is now known as zz_dimtruck | 07:10 | |
| *** pserebryakov has joined #openstack-tailgate | 12:50 | |
| *** spyderdyne has joined #openstack-tailgate | 13:26 | |
| spyderdyne | is anyone here familiar with this project? https://wiki.openstack.org/wiki/UnifiedInstrumentationMetering | 13:32 |
|---|---|---|
| spyderdyne | good info but it seems like it makes a lot of assumptions on things that most orgs are not using | 13:39 |
| *** pserebryakov has quit IRC | 14:00 | |
| *** pglass has joined #openstack-tailgate | 14:05 | |
| *** malini has joined #openstack-tailgate | 14:47 | |
| *** zz_dimtruck is now known as dimtruck | 14:47 | |
| hockeynut | I won't be at our meeting today - noon on Thurs is a bad time for me in general. Will catch up on the notes...will this one be IRC only? | 15:04 |
| jasonsb | hockeynut: yes IRC only | 15:07 |
| hockeynut | cool | 15:07 |
| jasonsb | hockeynut: should i add meeting time to agenda? | 15:07 |
| jasonsb | hockeynut: we can move it | 15:07 |
| hockeynut | don't move just on my account... | 15:07 |
| malini | as long as we keep the same time, the day should be ok | 15:10 |
| malini | Now if we want to move the meetings to one of #openstack-meeting…. tht will be different | 15:10 |
| malini | I tried to find us a spot there, but its really hard to find a time unless its Friday :/ | 15:11 |
| jasonsb | all the spots are used up? | 15:11 |
| malini | just the time we want | 15:11 |
| jasonsb | oh | 15:11 |
| malini | since we are on diff time zones, this slot woks the best | 15:11 |
| malini | Pacific, Eastern, Central, Europe…. | 15:12 |
| malini | & even with this it's not nice for the Europe folks I guess :( | 15:12 |
| jasonsb | ic | 15:12 |
| jasonsb | thierry probably wont open new ones at our time i suspect | 15:13 |
| jasonsb | since he wants to spread the meetings out | 15:13 |
| malini | At some point we should switch to the official meeting channels | 15:13 |
| jasonsb | we could state our case to thierry and get on the wait list for 10am pst | 15:16 |
| malini | tht will be great ..Is there an official waitlist? | 15:19 |
| jasonsb | no idea but i suspect there is based on -dev ml threads | 15:20 |
| jasonsb | malini: are you fine to give a walkthrough today? | 15:21 |
| *** sabeen has joined #openstack-tailgate | 15:22 | |
| malini | jasonsb: not today. | 15:29 |
| malini | I was thinking of we should pick each openstack project like nova, glance each week | 15:29 |
| malini | & have folks from each of the companies talk abt how they test it | 15:30 |
| malini | Even within the same company we might not be testing exactly the same across different projects | 15:31 |
| malini | thoughts? | 15:31 |
| spyderdyne | sounds accurate :) | 15:34 |
| spyderdyne | it is entirely possible that halfway through the list all the companies that provided their input will have made modifications already | 15:36 |
| spyderdyne | would a spreadsheet or a matrix of some kind that we could all fill in and keep updated be a better use of time perhaps? | 15:36 |
| malini | I didnt quite get that | 15:37 |
| malini | what kind of info are you talking at being captured? | 15:38 |
| spyderdyne | a summary of how each member's org tests each component | 15:42 |
| spyderdyne | if it was all captured in one place we could see the similarities and examine the differences without taking 12 months to do so | 15:43 |
| malini | oops..what will do the rest of 12 months! :D | 15:44 |
| spyderdyne | maybe something akin to a questionaire or a surveymonkey quiz that we can aggregate, or even as simple as a matrix/etherpad that each member can update freely | 15:44 |
| malini | but tht sure sounds like a good idea | 15:44 |
| jasonsb | interesting | 15:44 |
| spyderdyne | the rest of the 12 months we will find meaningful ways to contribute | 15:45 |
| malini | the google survey stuff has good aggregation stuff | 15:45 |
| spyderdyne | lol | 15:45 |
| jasonsb | it might be nice for somebody to do an example | 15:45 |
| jasonsb | to help get the focus in the right place | 15:45 |
| spyderdyne | i will take that as an action item to provide for next week's meeting | 15:46 |
| spyderdyne | then everyone can cut it apart and make it shine | 15:46 |
| jasonsb | its a good idea | 15:46 |
| malini | spyderdyne: awesome..& we'll tell you what you cud have done better ;) | 15:46 |
| spyderdyne | its on my list | 15:46 |
| spyderdyne | lol | 15:46 |
| spyderdyne | exactly | 15:46 |
| jasonsb | and it will help show what areas everybody is testing because it is a weak spot | 15:46 |
| malini | I am sure, each of us will need to forward tht surver to atleast 10 diff ppl in their respective companies | 15:47 |
| spyderdyne | without making everyone write a book report :) | 15:47 |
| jasonsb | spyderdyne: you will take as action to come up with a format to capture the info? | 15:47 |
| spyderdyne | i will | 15:47 |
| jasonsb | awesome | 15:47 |
| spyderdyne | it runs in parallel with what I am working on already so I shoudl be able to provide example entries as well | 15:49 |
| spyderdyne | will try this: http://justingale.com/2013/09/url-tricks-for-google-forms-pre-populate-and-automatically-submitting-responses/ | 16:06 |
| jasonsb | i like it | 16:08 |
| jasonsb | or even just a shared goog spreadsheet might be a good start | 16:09 |
| jasonsb | worksheet per openstack project | 16:09 |
| jasonsb | spyderdyne: i see on actions from meetup-3 you might talk about HA testing | 16:24 |
| spyderdyne | yes | 16:24 |
| jasonsb | spyderdyne: that would be great if you swing it | 16:24 |
| spyderdyne | i have an issue/nothing useful to present | 16:24 |
| spyderdyne | we ran into some issues with the tests we have inherited. i am also the FNG | 16:25 |
| jasonsb | fng? | 16:25 |
| spyderdyne | all of this is new to me and i was unable to get to HA testing. I am however starting testing in another environment tomorrow and shoudl have time to include them now that we have most of the bugs ironed out | 16:25 |
| spyderdyne | * new guy | 16:26 |
| jasonsb | oh sure okedokey | 16:26 |
| spyderdyne | i still owe you that and will definitely provide our results once I can get them run | 16:26 |
| spyderdyne | apologies | 16:26 |
| jasonsb | np this is somethign everybody touches i think | 16:27 |
| jasonsb | we just need somebody to go first :) | 16:27 |
| spyderdyne | understood | 16:27 |
| spyderdyne | i hit a pretty decent learning curve having never seen any of this before, but it will get done soon | 16:28 |
| spyderdyne | i may have been a little overconfident in my assessments :) | 16:28 |
| jasonsb | i too | 16:29 |
| jasonsb | you tend to get pulled in lot of different directions | 16:30 |
| spyderdyne | i had another action item to contact the rally team with regards to creating some form of cleanup mechanism outside of the completion of a test run should one fail in the middle | 16:30 |
| jasonsb | because everything touches everything with this stuff | 16:30 |
| jasonsb | i see that | 16:31 |
| jasonsb | i'll list it to keep the record if thats ok | 16:31 |
| spyderdyne | i made contact with them but need to step back and provide some details on how to implement. in the interim we have actually implement just such a thing in python for the KloudBuster project | 16:31 |
| jasonsb | ah good stuff | 16:31 |
| jasonsb | i'll bring up in meeting | 16:31 |
| spyderdyne | in the rally implementation it would just perform a regex check for rally_* objects in each service and wipe them in case of a failure | 16:32 |
| spyderdyne | nothing very advanced, but definitely easy to write and very effective | 16:32 |
| spyderdyne | unless oyu work at rallydev building software to track user stories it shoudl work for now... | 16:33 |
| spyderdyne | i intend to yank it out and file it soon | 16:33 |
| spyderdyne | our project also has a feature that cleans up on termination via CTRL+C and it does pretty well, but its not quite right yet | 16:34 |
| spyderdyne | this is all written in python so i dont expect it to be too hard to get acceptance | 16:35 |
| jasonsb | nice | 16:36 |
| spyderdyne | rahter, i think i can present it accurately as something useful even with my fat fingered code hackery | 16:37 |
| jasonsb | i'm going to make it a point to get familiar with kloudbuster | 16:38 |
| jasonsb | i have some gremlins i need to chase | 16:38 |
| spyderdyne | git clone -b kloudbuster https://github.com/stackforge/vmtp.git | 16:39 |
| spyderdyne | cd vmtp/scale/ | 16:40 |
| spyderdyne | cfg.topo lets you configure physical topologies for things like same leaf, or leaf to spine to leaf testing | 16:40 |
| spyderdyne | cfg.scale contians the actual test params | 16:41 |
| spyderdyne | it is pretty well self documented, but if you have any issues i am in constant contact with the developers and they would love the feedback | 16:41 |
| spyderdyne | cfg.topo is also optional | 16:41 |
| jasonsb | neat | 16:42 |
| spyderdyne | we are working to add the ability to only use existing tenants and users now. it should be ready in a couple weeks | 16:42 |
| spyderdyne | i seem to be hijacking the meeting | 16:43 |
| spyderdyne | what other items do we have to discuss? | 16:43 |
| spyderdyne | are there any actions we can take on the toyko proposal since the deadline is looming? | 16:44 |
| jasonsb | not hijacking | 16:44 |
| jasonsb | i hope you don't mind describing again in meeting :) | 16:44 |
| jasonsb | its in 15 min | 16:44 |
| spyderdyne | i dont | 16:44 |
| spyderdyne | lol | 16:45 |
| spyderdyne | stupid timezones | 16:45 |
| jasonsb | ah | 16:45 |
| jasonsb | ima try kloudbuster after the meeting | 16:45 |
| spyderdyne | i have a new IRC client so I will probably just be on the channel every day when im online now | 16:46 |
| spyderdyne | its pretty cool | 16:46 |
| jasonsb | same here | 16:46 |
| *** localloop127 has joined #openstack-tailgate | 17:00 | |
| beisner | o/ hi all | 17:00 |
| jasonsb | g'day | 17:00 |
| spyderdyne | hello | 17:01 |
| malini | hello again ! | 17:01 |
| jasonsb | #startmeeting tailgate | 17:01 |
| openstack | Meeting started Thu Jul 9 17:01:50 2015 UTC and is due to finish in 60 minutes. The chair is jasonsb. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:01 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:01 |
| openstack | The meeting name has been set to 'tailgate' | 17:01 |
| beisner | ooo fancy bot action | 17:02 |
| jasonsb | its nice | 17:02 |
| jasonsb | yay gema | 17:02 |
| malini | & she is green too !!! | 17:02 |
| jasonsb | #topic update on last week's actions | 17:02 |
| beisner | she's also not here today, so we can assign her all of the to-dos | 17:02 |
| malini | +1 ;) | 17:02 |
| jasonsb | #link last meeting summary: http://eavesdrop.openstack.org/meetings/tailgate/2015/tailgate.2015-07-02-17.00.html | 17:02 |
| jasonsb | exactly | 17:03 |
| jasonsb | lets pick up a few actions from two meetings ago | 17:03 |
| jasonsb | spyderdyne to talk to boris about rally not cleaning up after itself and ways to mitigate, also talk to him about running again when things go wrong | 17:03 |
| jasonsb | spyderdyne: would you mind repeating your rally update? | 17:03 |
| spyderdyne | putting together a spec to present to them | 17:04 |
| spyderdyne | 50% complete | 17:04 |
| jasonsb | should i keep as action? | 17:04 |
| spyderdyne | please | 17:04 |
| jasonsb | #action spyderdyne composing a spec to present to rally on topic of rally cleanup | 17:05 |
| spyderdyne | have produced an external script in another repo that should work for this as well, | 17:05 |
| jasonsb | link? | 17:06 |
| spyderdyne | but it does not incorporate any of the intelligence in rally and rather just looks for the regex "rally_" in each service and removes entries | 17:06 |
| spyderdyne | git clone -b kloudbuster https://github.com/stackforge/vmtp.git | 17:06 |
| spyderdyne | its in there somewhere. will provide the actual code later if oyu want it | 17:07 |
| jasonsb | sounds good | 17:07 |
| jasonsb | next item | 17:07 |
| spyderdyne | i think I can just submit in launchpad and see if they accept it | 17:07 |
| jasonsb | doesnt hurt to just put it up on gerrit and mark it WIP | 17:08 |
| jasonsb | people can comment | 17:08 |
| jasonsb | we have HA discussion from 2 weeks back | 17:08 |
| jasonsb | currently accepting volunteers if anybody would like to present anything | 17:08 |
| jasonsb | spyderdyne i think is a volunteer, but for a future meeting | 17:08 |
| malini | Somebody had started on tht -rt? | 17:09 |
| jasonsb | spyderdyne: do i have that right? | 17:09 |
| spyderdyne | i was unable to run any of the HA scripts we are using internally for HA testing but shoudl have another opportunity tomororw | 17:09 |
| spyderdyne | correct | 17:09 |
| jasonsb | next item | 17:09 |
| spyderdyne | they are marked as part of my new battery of tests I will be running over the course of the next week in a new deployment | 17:09 |
| jasonsb | can i make an action to ask you again in couple of weeks? | 17:10 |
| jasonsb | :) | 17:10 |
| spyderdyne | yes | 17:10 |
| jasonsb | awesome | 17:10 |
| spyderdyne | am hpoing for the next meeting, but 2 weeks is comfortable | 17:10 |
| jasonsb | #action spyderdyne check back to see if any updates/info for HA testing discussion | 17:11 |
| jasonsb | there was a good discussion with hogepodge on defcore last week | 17:11 |
| jasonsb | #link http://eavesdrop.openstack.org/#DefCore_Committee_Meeting | 17:11 |
| jasonsb | since gema not here keeping her action | 17:11 |
| jasonsb | #action gema to submit a few test runs of refstack and get familiar with it | 17:11 |
| jasonsb | also keep her tempest action | 17:12 |
| jasonsb | #action gema to talk to matthew about stable tempest kilo and report back | 17:12 |
| jasonsb | there is a topic for malini on giving a walkthrough of rackspace testing | 17:12 |
| spyderdyne | cleanup script: https://github.com/stackforge/vmtp/commit/af1e5ca210b5eec2ceba0aa6caf27993d37f2a9d | 17:13 |
| jasonsb | i think this has morphed a bit | 17:13 |
| malini | not yet | 17:13 |
| spyderdyne | replace KB with rally_ | 17:13 |
| malini | But as we discussed earlier, it'll be good to tackle on a per project basis | 17:13 |
| jasonsb | into capturing testing strategies per project | 17:13 |
| malini | & Get into the integration part after we do the per project | 17:13 |
| spyderdyne | If this is current it may be useful for the rackspace discussion: https://wiki.openstack.org/wiki/UnifiedInstrumentationMetering | 17:14 |
| jasonsb | so chop it up into bite size pieces to discuss? | 17:14 |
| malini | yes | 17:14 |
| malini | We can pick the core projects & tackle them one by one | 17:15 |
| jasonsb | i think spyderdyne expressed interest in working on a way to capture the test strategies (per project) | 17:15 |
| malini | tht sounds like the most efficient way to get info | 17:15 |
| jasonsb | google form or similar | 17:15 |
| spyderdyne | i propose that it would be more time friendly to create a quiz/form for each member to fill out and submit rather than spending the next year covering each org's methods by project | 17:16 |
| jasonsb | who would be willing to contribute? | 17:16 |
| malini | We can have each person here hunt down the respective folks in their companies for info | 17:16 |
| spyderdyne | by the time we completed an iteration of the reveiw everyone would be doing something different anyway | 17:16 |
| malini | eg. I can find all the rax folks in different projects & have the update the surver link | 17:17 |
| beisner | i like gdocs for shared braindumps | 17:17 |
| spyderdyne | this ideally would also allow anyone to change their responses anytime something changes | 17:17 |
| jasonsb | i like it | 17:17 |
| spyderdyne | i suggested something like this: http://justingale.com/2013/09/url-tricks-for-google-forms-pre-populate-and-automatically-submitting-responses/ | 17:17 |
| beisner | easy to turn into a formatted & arranged collection of info | 17:17 |
| malini | if we can also have folks from Cisco, Hitachi, CAnonical etc. get their folks to contribute, we can have decent info | 17:18 |
| spyderdyne | yes | 17:18 |
| spyderdyne | the more the merrier without sucking up meeting and projec time | 17:18 |
| jasonsb | #action spyderdyne work on a goog doc/form to capture per project testing strategies so we can crowdsource good info | 17:18 |
| spyderdyne | im going to need an assistant | 17:18 |
| spyderdyne | lol | 17:18 |
| jasonsb | i was just thinking that | 17:19 |
| jasonsb | i would be happy to help with the goog piece | 17:19 |
| spyderdyne | ok | 17:19 |
| spyderdyne | call us a breakout team on this item? | 17:19 |
| jasonsb | i will circulate it within hitachi | 17:19 |
| malini | you might want to actionize all of us to circulate within the respective companies | 17:20 |
| spyderdyne | i can at cisco as well | 17:20 |
| jasonsb | good idea. i'll set it as action for next time | 17:20 |
| malini | gema for canonical | 17:21 |
| malini | he hee..all the actions we can give her | 17:21 |
| spyderdyne | i have friends in other large orgs that may have interest as well | 17:21 |
| jasonsb | #action malini open topic of actioning tailgate members to circulate test strategy goog doc within respective company | 17:21 |
| jasonsb | oh, should i have put gema? | 17:21 |
| malini | hmm..I just meant an action tag for each of us :D | 17:21 |
| malini | maybe update tht action tag to put all our names? | 17:22 |
| jasonsb | oh, you get to make that next week :) | 17:22 |
| jasonsb | when we have the goog doc (draft) | 17:22 |
| malini | sounds good | 17:22 |
| jasonsb | ok thast all i had for updates | 17:22 |
| jasonsb | #topic talk@tokyo "testing beyond the gate" | 17:22 |
| jasonsb | gema had sent an email about call for speakers for tokyo | 17:23 |
| beisner | #link https://etherpad.openstack.org/p/tailgaters-tokyo-summit | 17:23 |
| malini | lets vote on the tile/ start updating etherpad | 17:24 |
| jasonsb | the response was quite positive i think | 17:24 |
| malini | title* | 17:24 |
| jasonsb | shall we take a vote? | 17:24 |
| jasonsb | any +1's? | 17:24 |
| beisner | +1 Testing Beyond the Gate | 17:24 |
| malini | +1 | 17:24 |
| spyderdyne | +1 | 17:24 |
| jasonsb | +1 | 17:25 |
| malini | can we get rid of the rest from the etherpad? | 17:25 |
| malini | I just did (A) | 17:25 |
| jasonsb | malini: move it to goog doc? | 17:25 |
| malini | keep it at etherpad for now? | 17:26 |
| malini | Once we are all done scratching & scribbling, we can move to gdoc | 17:26 |
| malini | sounds ok? | 17:26 |
| beisner | i think epad is ok for our purposes on this | 17:26 |
| jasonsb | malini: you wanted to nail down title? | 17:26 |
| spyderdyne | i prefer EP | 17:26 |
| malini | we just nailed down the title rt? | 17:27 |
| jasonsb | everybody happy with the title? | 17:27 |
| spyderdyne | yes | 17:27 |
| beisner | yep | 17:27 |
| spyderdyne | very clever | 17:27 |
| spyderdyne | :) | 17:27 |
| malini | Lets start putting our thoughts into the etherpad, agree, disagree, new stuff etc. | 17:27 |
| malini | we can clean up later | 17:27 |
| jasonsb | awesome | 17:28 |
| beisner | i'd suggest we take Option2 and expand on that. whaddaya think? | 17:28 |
| malini | as long as we take out a lot of the fluff | 17:28 |
| malini | we need something crisp & to the point. | 17:29 |
| beisner | +1 defluff, distill it | 17:29 |
| spyderdyne | what we are testing, how we are testing it, what are the issues, how do we propose to solve | 17:29 |
| spyderdyne | ? | 17:29 |
| beisner | ok... so are we wanting to present on testing clouds; or are we wanting to present on who we are, what we want to do, why this is necessary, and how "you" can help? | 17:30 |
| malini | I like the outline better than our abstract | 17:30 |
| beisner | i could see two proposals actually | 17:30 |
| jasonsb | motivations might be worth discussing too | 17:30 |
| spyderdyne | +1 on motivations | 17:30 |
| jasonsb | the gate using devstack doesn't cover everything | 17:31 |
| malini | anybody has the link handy for call for speakers? | 17:31 |
| jasonsb | testing on a production cloud is different | 17:31 |
| beisner | #link https://www.openstack.org/summit/tokyo-2015/call-for-speakers/ | 17:31 |
| jasonsb | i think this means we need to focus on what we will accomplish this cycle and next | 17:31 |
| malini | "Real-world user stories and in-the-trenches experiences are favored over sales pitches." | 17:31 |
| spyderdyne | yes | 17:32 |
| malini | tht is us :) | 17:32 |
| spyderdyne | i think there is huge value for anyone using openstack to see what others are doing | 17:32 |
| spyderdyne | what works, and what the issues are | 17:32 |
| spyderdyne | then the community has something to look at addressing | 17:32 |
| malini | jasonsb: I think we'll have a better idea of what we will do, once we go thru the exercise of collecting info from all companies | 17:32 |
| spyderdyne | +1 | 17:32 |
| malini | Despite 2-3 months, we are still cloudy on what we want to do | 17:33 |
| spyderdyne | identify commonalities | 17:33 |
| malini | not a bad thing, since we are trying to tackle something huge | 17:33 |
| spyderdyne | i would like to suggest that we specifically will not be able to address every issue | 17:33 |
| jasonsb | i see it as somewhat of a problem of where-to-start | 17:34 |
| malini | spyderdyne: exactly | 17:34 |
| spyderdyne | and that our value may be greatest in providing a framework where these items can be identified and worked through collectively | 17:34 |
| jasonsb | +1 | 17:34 |
| malini | spyderdyne: agreed | 17:34 |
| spyderdyne | 1. identify methods, commonalities, and pain points | 17:34 |
| malini | If we identify the problems, interested parties can pool together to address them | 17:34 |
| spyderdyne | 2. address pain points | 17:34 |
| spyderdyne | imho that is the best way to approach this | 17:35 |
| beisner | what if: We propose 2 talks ... (a) who/what/why/motives/call to arms; and (b) a cross-section of our actual test approaches ? | 17:35 |
| jasonsb | hogepodge also made some interesting comments about defcore testing welcoming tailgate | 17:36 |
| malini | beisner: +1 | 17:36 |
| hogepodge | o/ | 17:36 |
| hogepodge | Hello! | 17:36 |
| spyderdyne | for a July 20th speaker call I think all we can expect to present as of this minute is to provide a framework for the dialogue and demonstrate some of the common solutions | 17:36 |
| hogepodge | Yes, please, come to our meetings. Next one is Wednesday. | 17:36 |
| jasonsb | hogepodge: oh yay your on | 17:36 |
| beisner | with (b) being us each taking 10 min or so to talk about our very specific things | 17:36 |
| jasonsb | hogepodge: could you give time and link to meeting? | 17:36 |
| malini | sure hogepodge..I tried last time, but wasnt sure how to start without hijacking | 17:37 |
| malini | maybe we should add us to the defcore agenda? | 17:37 |
| beisner | (b) being determined and collectively agreed upon based on this gdoc circulated info collection thing ;-) | 17:37 |
| hogepodge | Looking for the links | 17:38 |
| jasonsb | beisner: i like it | 17:39 |
| *** mohnatar has joined #openstack-tailgate | 17:39 | |
| spyderdyne | our subject is all encompassing like defcore, but we are exploring minutia that they probably want to be left out of | 17:39 |
| spyderdyne | :) | 17:39 |
| malini | I like the two talk idea | 17:39 |
| hogepodge | #link http://eavesdrop.openstack.org/#DefCore_Committee_Meeting | 17:39 |
| jasonsb | beisner: chop 40 minute time slot into 20 + lightning talks? | 17:39 |
| spyderdyne | we have a very narrow focus | 17:39 |
| hogepodge | (the link is wrong though, all meetings on Wednesday) | 17:39 |
| malini | Testing Beyond the Gate, Fixing beyond the gate :D | 17:40 |
| beisner | jasonsb, sure something like that would be a good format i think | 17:40 |
| spyderdyne | oiling the gate | 17:40 |
| hogepodge | next week is at 1500 | 17:40 |
| hogepodge | The agenda is published on the defcore-committee mailing list and can be modified in the etherpad | 17:40 |
| jasonsb | do we have to decide now about format? | 17:41 |
| jasonsb | gema i think said she wanted to submit monday | 17:41 |
| malini | July 15th is the deadline | 17:41 |
| malini | So Gema is right | 17:42 |
| malini | quoting beisner 'who/what/why/motives/call to arms; and (b) a cross-section of our actual test approaches ?' | 17:42 |
| jasonsb | i wonder how much time we can get | 17:43 |
| spyderdyne | we know we need to provide a purpose for the effort, a way to contribute, and maybe show some cool gadgets for getting results | 17:43 |
| jasonsb | b almost sounds like a fishbowl to me | 17:43 |
| malini | jasonsb: 'like a fishbowl to me' what does tht mean? | 17:44 |
| malini | good or bad? | 17:44 |
| beisner | So with the deadline being right around the corner, shall we get 2 or more heads on each of the 2 talks to nail down proposals out of band? then bring those back here on Fri/Mon for final review? | 17:44 |
| malini | beisner: +1 | 17:44 |
| jasonsb | sorry, sounds like a fishbowl session where you present to wide audience | 17:44 |
| beisner | i might suggest that those who have been more involved with other projects take (a); and those who do a ton of testing now, take (b) | 17:44 |
| jasonsb | on a technical topic | 17:44 |
| jasonsb | beisner: good idea | 17:46 |
| jasonsb | beisner: but maybe for submission we only have to do a? | 17:46 |
| malini | Sounds like (b) will lead to (a) | 17:46 |
| malini | a | 17:46 |
| jasonsb | and just list b as "lightning talks" | 17:47 |
| spyderdyne | +1 | 17:47 |
| malini | But there is advantage of b being one single talk | 17:48 |
| spyderdyne | there is | 17:48 |
| malini | It will highlight how all of us testing the same thing differently | 17:48 |
| malini | & why there is value in joining forces | 17:48 |
| jasonsb | +1 | 17:48 |
| jasonsb | yes you are right | 17:48 |
| beisner | i think 2 submissions: (a) proposed under "How to Contribute" or "Community"; and (b) proposed under "Enterprise IT Strategies" | 17:49 |
| malini | good idea | 17:49 |
| beisner | or (b) in "User Stories" ? | 17:49 |
| spyderdyne | Enterprise IT Strategies | 17:51 |
| malini | beisner: where are u seeing these sections? | 17:51 |
| malini | The 'Enterprise IT Strategies' might be like the walmart stories -rt? | 17:51 |
| beisner | you may have to be logged in | 17:51 |
| beisner | #link http://paste.ubuntu.com/11850138/ | 17:51 |
| malini | where we have the CTO of so & so come tell us how they make more money | 17:51 |
| malini | I think we are much lower in the food chain :/ | 17:52 |
| malini | I think we are almost out of time | 17:53 |
| jasonsb | community? | 17:53 |
| malini | Community —> for why we shud join forces talk | 17:53 |
| jasonsb | exactly | 17:53 |
| malini | User Stories —> How each of us are testing | 17:53 |
| beisner | i'd go (a) community & (b) user stories | 17:53 |
| malini | How each of us are testing will have more details once we do the spreadsheet exercixe | 17:54 |
| malini | But we can just create a small gist for the topic submission | 17:54 |
| jasonsb | who/what/why/motives/call to arms -> community | 17:54 |
| malini | Anybody has prior experience submitting accepted talks? | 17:55 |
| beisner | for the proposal, we just need an abstract that states what cool stuff we will be talking about. we don't have to have the whole thing figured out this week. | 17:55 |
| malini | beisner: exactly | 17:55 |
| malini | I can start working on the who/what/why/motives/call to arms -> community | 17:55 |
| malini | I will send out the etherpad link for folks to start adding ideas | 17:55 |
| spyderdyne | good | 17:56 |
| jasonsb | beisner: were you intending the single cross-section talk to go to user stories? | 17:56 |
| malini | Well we dont necessarily need tht maybe? | 17:56 |
| malini | We can split some of the sttuff in existing etherpad into two? | 17:56 |
| malini | We already have a good pool of ideas there | 17:56 |
| spyderdyne | sounds like a winner | 17:56 |
| beisner | jasonsb, i think the session (b) where we talk about our specific test approaches is either operations or user stories. retract my enterprise it suggestion ;-) | 17:57 |
| jasonsb | beisner: got it | 17:57 |
| jasonsb | i like the idea of submit to operations or user stories | 17:57 |
| jasonsb | it shows we have technical depth | 17:58 |
| spyderdyne | :) | 17:58 |
| malini | Operations as per definition sounds good too - though the name sounds like …well 'operations' | 17:58 |
| jasonsb | can always collapse into 1 talk | 17:58 |
| beisner | ok let's determine the 2 submitters | 17:58 |
| malini | gema can do one & somebody else can do the other. | 17:58 |
| malini | We can have multiple ppl listed as speakers | 17:59 |
| beisner | and the 2 people who submit those will need email addresses for "other speakers" in order to list them, and i believe those ppl must have already created a speaker bio etc | 17:59 |
| malini | sounds like work now :( | 17:59 |
| jasonsb | any volunteers? | 17:59 |
| beisner | i'd be happy to submit (b). i submitted a handful of things on different topics today. | 17:59 |
| jasonsb | awesome | 18:00 |
| malini | gema can possibly do a | 18:00 |
| malini | She already started tht -rt? | 18:00 |
| jasonsb | #action beisner to do talk submission for operations or user stories track | 18:01 |
| malini | we will keep the existing etherpad for a | 18:01 |
| malini | beisner: can u send the etherpad link when you have it? | 18:01 |
| jasonsb | maybe we should spread out submission between companies | 18:01 |
| jasonsb | to show the collaboration aspect | 18:02 |
| beisner | definitely | 18:02 |
| malini | good point | 18:02 |
| beisner | malini, you're doing a, right? if i do b, we have different companies. | 18:02 |
| malini | lets check with gema tht she is ok | 18:02 |
| malini | She did bulk of the writing up | 18:02 |
| jasonsb | when is she back? | 18:03 |
| malini | If she is, I can submit tht | 18:03 |
| malini | need to run to another meeting | 18:03 |
| jasonsb | yes, we are out of time | 18:03 |
| malini | But feel free to actionize me for anything | 18:03 |
| jasonsb | can i put action to check with gema? | 18:03 |
| jasonsb | #action malini check with gema to coordinate who should do talk submission for community track | 18:04 |
| jasonsb | ok, any other topics or close it out | 18:04 |
| jasonsb | ok, closing out. thanks all! | 18:04 |
| jasonsb | #endmeeting | 18:05 |
| openstack | Meeting ended Thu Jul 9 18:05:02 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 18:05 |
| beisner | thanks all, i'll be updating in that same epad, and will ping back here for further input. i'll also be able to sync up with gema. | 18:05 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/tailgate/2015/tailgate.2015-07-09-17.01.html | 18:05 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/tailgate/2015/tailgate.2015-07-09-17.01.txt | 18:05 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/tailgate/2015/tailgate.2015-07-09-17.01.log.html | 18:05 |
| *** jasonsb has quit IRC | 18:26 | |
| *** jasonsb has joined #openstack-tailgate | 18:26 | |
| *** jasonsb has quit IRC | 18:31 | |
| *** jasonsb has joined #openstack-tailgate | 19:19 | |
| *** malini has quit IRC | 19:40 | |
| *** spyderdyne has quit IRC | 20:52 | |
| *** localloop127 has quit IRC | 21:29 | |
| *** pglass has quit IRC | 22:10 | |
| *** jasonsb has quit IRC | 22:25 | |
| *** jasonsb has joined #openstack-tailgate | 22:26 | |
| *** jasonsb has quit IRC | 23:04 | |
| *** jasonsb has joined #openstack-tailgate | 23:05 | |
| *** openstack has joined #openstack-tailgate | 23:38 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!