| *** zz_dimtruck is now known as dimtruck | 01:03 | |
| *** jasonsb has quit IRC | 01:06 | |
| *** jasonsb has joined #openstack-tailgate | 01:06 | |
| *** jasonsb has quit IRC | 01:11 | |
| *** jasonsb has joined #openstack-tailgate | 01:56 | |
| *** ig0r_ has joined #openstack-tailgate | 05:51 | |
| *** ig0r__ has quit IRC | 05:55 | |
| *** dimtruck is now known as zz_dimtruck | 06:34 | |
| *** malini has joined #openstack-tailgate | 11:43 | |
| *** malini has quit IRC | 11:51 | |
| *** malini has joined #openstack-tailgate | 12:04 | |
| *** malini has quit IRC | 12:05 | |
| *** malini has joined #openstack-tailgate | 12:05 | |
| *** malini has quit IRC | 12:18 | |
| *** malini1 has joined #openstack-tailgate | 12:24 | |
| *** malini1 has quit IRC | 12:24 | |
| *** malini1 has joined #openstack-tailgate | 12:24 | |
| *** malini1 has quit IRC | 12:36 | |
| *** malini has joined #openstack-tailgate | 12:48 | |
| *** xwwt_ has joined #openstack-tailgate | 13:04 | |
| *** localloop127 has joined #openstack-tailgate | 13:30 | |
| *** malini has quit IRC | 13:37 | |
| *** malini has joined #openstack-tailgate | 13:39 | |
| *** malini has quit IRC | 13:44 | |
| *** malini has joined #openstack-tailgate | 13:51 | |
| *** malini has quit IRC | 13:58 | |
| *** zz_dimtruck is now known as dimtruck | 13:59 | |
| gema | jasonsb: ping | 14:04 |
|---|---|---|
| *** dimtruck is now known as zz_dimtruck | 14:06 | |
| *** pglass has joined #openstack-tailgate | 14:08 | |
| *** malini has joined #openstack-tailgate | 14:12 | |
| *** malini has quit IRC | 14:12 | |
| *** malini has joined #openstack-tailgate | 14:55 | |
| *** zz_dimtruck is now known as dimtruck | 15:06 | |
| *** malini has quit IRC | 15:16 | |
| *** malini has joined #openstack-tailgate | 15:25 | |
| *** sabeen1 has joined #openstack-tailgate | 15:26 | |
| *** sabeen3 has joined #openstack-tailgate | 15:34 | |
| *** sabeen1 has quit IRC | 15:35 | |
| jasonsb | gema: late pong | 15:55 |
| gema | jasonsb: ok | 16:04 |
| gema | jasonsb: when you say you wanted to contribute to the talk , do you mean go up there and talk | 16:04 |
| gema | as in, do you and your company want to be on the list? | 16:04 |
| gema | or do you want to contribute in some other way? | 16:05 |
| *** malini has quit IRC | 16:18 | |
| *** hogepodge has quit IRC | 16:21 | |
| jasonsb | gema: would love to go up there and talk | 16:27 |
| jasonsb | gema: but also happy to contribute in other way | 16:28 |
| *** malini has joined #openstack-tailgate | 16:29 | |
| *** jasonsb has quit IRC | 16:29 | |
| *** pglass has quit IRC | 17:02 | |
| *** pglass has joined #openstack-tailgate | 17:06 | |
| *** jasonsb has joined #openstack-tailgate | 17:15 | |
| *** pglass has quit IRC | 17:29 | |
| *** jasonsb has quit IRC | 17:31 | |
| *** jasonsb has joined #openstack-tailgate | 17:32 | |
| *** dwalleck has joined #openstack-tailgate | 17:36 | |
| *** dwalleck has quit IRC | 17:39 | |
| gema | jasonsb: ok | 17:43 |
| *** malini has quit IRC | 17:46 | |
| *** pglass has joined #openstack-tailgate | 18:03 | |
| *** malini has joined #openstack-tailgate | 18:08 | |
| *** hogepodge has joined #openstack-tailgate | 18:11 | |
| *** hogepodge has quit IRC | 18:20 | |
| *** hogepodge has joined #openstack-tailgate | 19:00 | |
| murphyslawbbs | i got a question: when you develop multiple things on top of openstack, what is your stretegy about testing those multiple changes with each other? | 19:06 |
| murphyslawbbs | in theory you could do a full mesh testing: each change in git is checked against each other change in gi | 19:06 |
| murphyslawbbs | but that soon becomes a permutation from hell | 19:06 |
| murphyslawbbs | so when is a change tested, and againstn what is it tested? | 19:07 |
| malini | hmm…when it comes to cloud operators, does anybody do a CD from upstream? | 19:07 |
| murphyslawbbs | CD? | 19:07 |
| malini | continuous deployment | 19:08 |
| murphyslawbbs | we don't | 19:08 |
| murphyslawbbs | but then we're on juno so not a lot of changes upstream ;) | 19:08 |
| malini | doesn't test each git commit make more sense if you are deploying it? | 19:08 |
| murphyslawbbs | well unit test each commit, yes | 19:09 |
| murphyslawbbs | but merge test? put up a full openstack environment and tear it down on every commit? | 19:09 |
| malini | tht is the intent of running tests against devstack | 19:10 |
| malini | But does it represent a real cloud is another question | 19:10 |
| murphyslawbbs | i think we'd settle for having our tests automated for now | 19:10 |
| malini | tht wouldn't be so bad :) | 19:11 |
| murphyslawbbs | so you would take an existing devstack, save it as a template image, and then install all our packages on top and test if the apis work | 19:12 |
| murphyslawbbs | for every commit? | 19:12 |
| malini | we dont run tests against devstack | 19:14 |
| malini | I was just referring to openstack gate - sorry abt the confusion | 19:14 |
| malini | But most teams do only stable releases, or if pulling from upstream have internal testing | 19:15 |
| malini | I don't think we deploy often enuf to run into testing each commit with another commit with..... | 19:15 |
| murphyslawbbs | grr docs.openstack.org still down :( | 19:16 |
| murphyslawbbs | well yes this is for internal testing | 19:16 |
| murphyslawbbs | we want to be able to test if changing a type in A affects API B | 19:16 |
| murphyslawbbs | *a typo* ;) | 19:17 |
| malini | if it's just for tht purpose, devstack shud be good enough -rt? | 19:18 |
| malini | is there any reason why you want to try tht on a full blown cloud? | 19:18 |
| murphyslawbbs | no devstack is fine | 19:19 |
| murphyslawbbs | my problem is what set of changes do i test against, we have 3 or 4 branches for each project | 19:20 |
| murphyslawbbs | what is the "last known good" for each project | 19:20 |
| malini | hmm…3 or 4 branches for each project ? I thought it shud be just master & the last two stable | 19:21 |
| murphyslawbbs | we have customers on private clouds on special branches of each project | 19:22 |
| murphyslawbbs | then we have the current masters | 19:22 |
| malini | oh..wow.. | 19:22 |
| murphyslawbbs | and we have several developers working on their own branches committing back every 2 weeks | 19:23 |
| murphyslawbbs | into new branches which then go through QA | 19:23 |
| murphyslawbbs | and get merged back into the deployment branches | 19:23 |
| malini | does tht get merged back to upstream? | 19:23 |
| murphyslawbbs | no these are downstream | 19:24 |
| murphyslawbbs | doesnt touch upstream | 19:24 |
| murphyslawbbs | we just extend the look and feel etc | 19:24 |
| malini | aah..ok | 19:25 |
| malini | I assume the 'specialized' branches are also internal? | 19:25 |
| murphyslawbbs | yh | 19:26 |
| malini | now I understand the mesh :D | 19:26 |
| murphyslawbbs | hehe | 19:27 |
| murphyslawbbs | it's hard to explain, perhaps cause it's all a bit convoluted | 19:27 |
| murphyslawbbs | and i'm new to the team | 19:27 |
| malini | ideally you should be able to specify a commit hash for each project & try to run it all together in devstack | 19:28 |
| malini | but I have no idea if it is possible | 19:29 |
| malini | looking at README here https://github.com/openstack-dev/devstack , you can specify a repo | 19:29 |
| murphyslawbbs | looking | 19:29 |
| murphyslawbbs | interesting | 19:30 |
| *** malini has quit IRC | 19:34 | |
| *** murphyslawbbs has quit IRC | 19:35 | |
| *** malini has joined #openstack-tailgate | 19:35 | |
| *** murphyslawbbs has joined #openstack-tailgate | 19:35 | |
| *** malini has quit IRC | 20:17 | |
| hockeynut | I've added a TITLE and ABSTRACT to our etherpad at https://etherpad.openstack.org/p/tailgaters-tokyo-summit - please take a look and feel free to update/correct/trash them! | 20:59 |
| *** localloop127 has quit IRC | 21:54 | |
| *** dimtruck is now known as zz_dimtruck | 22:09 | |
| *** pglass has quit IRC | 22:10 | |
| *** sabeen3 has quit IRC | 22:47 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!