| *** banix has joined #openstack-meeting-4 | 00:03 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 00:07 | |
| *** markvoelker has quit IRC | 00:07 | |
| *** VW has joined #openstack-meeting-4 | 00:11 | |
| *** VW has quit IRC | 00:11 | |
| *** VW has joined #openstack-meeting-4 | 00:12 | |
| *** banix has quit IRC | 00:18 | |
| *** s3wong has quit IRC | 00:18 | |
| *** s3wong has joined #openstack-meeting-4 | 00:18 | |
| *** s3wong has quit IRC | 00:20 | |
| *** carl_baldwin has quit IRC | 00:33 | |
| *** banix has joined #openstack-meeting-4 | 00:49 | |
| *** markvoelker has joined #openstack-meeting-4 | 00:52 | |
| *** david-lyle is now known as david-lyle_afk | 00:57 | |
| *** wojdev has quit IRC | 00:59 | |
| *** markvoelker has quit IRC | 01:00 | |
| *** VW has quit IRC | 01:09 | |
| *** VW has joined #openstack-meeting-4 | 01:09 | |
| *** markvoelker has joined #openstack-meeting-4 | 01:19 | |
| *** VW has quit IRC | 01:42 | |
| *** VW has joined #openstack-meeting-4 | 01:43 | |
| *** VW has quit IRC | 01:44 | |
| *** banix has quit IRC | 01:46 | |
| *** kobis has joined #openstack-meeting-4 | 01:57 | |
| *** fnaval has joined #openstack-meeting-4 | 02:02 | |
| *** VW has joined #openstack-meeting-4 | 02:18 | |
| *** sigmavirus24_awa is now known as sigmavirus24 | 02:26 | |
| *** jckasper has joined #openstack-meeting-4 | 02:26 | |
| *** sigmavirus24 is now known as sigmavirus24_awa | 02:27 | |
| *** banix has joined #openstack-meeting-4 | 02:29 | |
| *** salv-orlando has quit IRC | 02:29 | |
| *** galstrom_zzz is now known as galstrom | 02:33 | |
| *** ajmiller has joined #openstack-meeting-4 | 02:40 | |
| *** VW has quit IRC | 02:42 | |
| *** VW has joined #openstack-meeting-4 | 02:43 | |
| *** SridharRamaswamy has quit IRC | 03:20 | |
| *** ajmiller has quit IRC | 03:42 | |
| *** banix has quit IRC | 03:56 | |
| *** ajmiller has joined #openstack-meeting-4 | 04:07 | |
| *** sarob has joined #openstack-meeting-4 | 04:19 | |
| *** galstrom is now known as galstrom_zzz | 04:25 | |
| *** fnaval has quit IRC | 04:38 | |
| *** kobis has quit IRC | 04:53 | |
| *** david-lyle_afk has quit IRC | 05:11 | |
| *** david-lyle_afk has joined #openstack-meeting-4 | 05:11 | |
| *** ivar-laz_ has joined #openstack-meeting-4 | 05:24 | |
| *** qwebirc78548 has joined #openstack-meeting-4 | 05:25 | |
| *** qwebirc28104 has joined #openstack-meeting-4 | 05:27 | |
| *** ivar-lazzaro has quit IRC | 05:27 | |
| *** qwebirc28104 has left #openstack-meeting-4 | 05:28 | |
| *** ivar-laz_ has quit IRC | 05:28 | |
| *** qwebirc78548 has quit IRC | 05:34 | |
| *** sarob has quit IRC | 05:40 | |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 05:49 | |
| *** markvoelker has quit IRC | 06:08 | |
| *** wojdev has joined #openstack-meeting-4 | 06:13 | |
| *** ivar-laz_ has joined #openstack-meeting-4 | 06:21 | |
| *** numan has joined #openstack-meeting-4 | 06:22 | |
| *** ivar-lazzaro has quit IRC | 06:24 | |
| *** wojdev has quit IRC | 06:26 | |
| *** markvoelker has joined #openstack-meeting-4 | 06:39 | |
| *** markvoelker has quit IRC | 06:43 | |
| *** wojdev has joined #openstack-meeting-4 | 06:59 | |
| *** VW has quit IRC | 07:00 | |
| *** VW has joined #openstack-meeting-4 | 07:01 | |
| *** ivar-laz_ has quit IRC | 07:03 | |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 07:04 | |
| *** wojdev has quit IRC | 07:09 | |
| *** [1]evgenyf has quit IRC | 07:11 | |
| *** VW has quit IRC | 07:15 | |
| *** VW has joined #openstack-meeting-4 | 07:16 | |
| *** ivar-laz_ has joined #openstack-meeting-4 | 07:16 | |
| *** ivar-lazzaro has quit IRC | 07:19 | |
| *** ivar-laz_ has quit IRC | 07:19 | |
| *** VW has quit IRC | 07:23 | |
| *** [1]evgenyf has joined #openstack-meeting-4 | 07:23 | |
| *** VW has joined #openstack-meeting-4 | 07:23 | |
| *** VW has quit IRC | 07:29 | |
| *** VW has joined #openstack-meeting-4 | 07:29 | |
| *** ajmiller has quit IRC | 07:33 | |
| *** ajmiller has joined #openstack-meeting-4 | 07:33 | |
| *** belmoreira has joined #openstack-meeting-4 | 07:36 | |
| *** VW has quit IRC | 07:37 | |
| *** VW has joined #openstack-meeting-4 | 07:38 | |
| *** markvoelker has joined #openstack-meeting-4 | 07:39 | |
| *** markvoelker has quit IRC | 07:44 | |
| *** VW has quit IRC | 07:46 | |
| *** VW has joined #openstack-meeting-4 | 07:47 | |
| *** VW has quit IRC | 07:49 | |
| *** VW has joined #openstack-meeting-4 | 07:50 | |
| *** VW has quit IRC | 07:52 | |
| *** VW has joined #openstack-meeting-4 | 07:53 | |
| *** VW has quit IRC | 07:58 | |
| *** VW has joined #openstack-meeting-4 | 07:59 | |
| *** VW has quit IRC | 07:59 | |
| *** VW has joined #openstack-meeting-4 | 08:00 | |
| *** VW has quit IRC | 08:11 | |
| *** VW has joined #openstack-meeting-4 | 08:12 | |
| *** VW has quit IRC | 08:18 | |
| *** VW has joined #openstack-meeting-4 | 08:19 | |
| *** VW has quit IRC | 08:27 | |
| *** VW has joined #openstack-meeting-4 | 08:27 | |
| *** VW has quit IRC | 08:32 | |
| *** markvoelker has joined #openstack-meeting-4 | 08:40 | |
| *** markvoelker has quit IRC | 08:45 | |
| *** dhruvdhody has joined #openstack-meeting-4 | 08:49 | |
| *** matrohon has joined #openstack-meeting-4 | 08:54 | |
| *** dhruvdhody has quit IRC | 09:11 | |
| *** mfedosin has quit IRC | 09:20 | |
| *** belmoreira has quit IRC | 09:21 | |
| *** belmoreira has joined #openstack-meeting-4 | 09:22 | |
| *** dhruvdhody has joined #openstack-meeting-4 | 09:25 | |
| *** dhruvdhody has quit IRC | 09:30 | |
| *** jckasper has quit IRC | 09:30 | |
| *** salv-orlando has joined #openstack-meeting-4 | 09:37 | |
| *** markvoelker has joined #openstack-meeting-4 | 09:41 | |
| *** lakshmiS has joined #openstack-meeting-4 | 09:42 | |
| *** lakshmiS has quit IRC | 09:47 | |
| *** markvoelker has quit IRC | 09:47 | |
| *** lakshmiS has joined #openstack-meeting-4 | 09:47 | |
| *** igordcard has joined #openstack-meeting-4 | 09:49 | |
| *** igordcard has quit IRC | 09:54 | |
| *** ajmiller has quit IRC | 10:21 | |
| *** ajmiller has joined #openstack-meeting-4 | 10:22 | |
| *** markvoelker has joined #openstack-meeting-4 | 10:43 | |
| *** markvoelker has quit IRC | 10:48 | |
| *** belmoreira has quit IRC | 10:48 | |
| *** VW has joined #openstack-meeting-4 | 10:58 | |
| *** VW has quit IRC | 11:03 | |
| *** lakshmiS has quit IRC | 11:03 | |
| *** lakshmiS has joined #openstack-meeting-4 | 11:30 | |
| *** lakshmiS_ has joined #openstack-meeting-4 | 11:43 | |
| *** markvoelker has joined #openstack-meeting-4 | 11:44 | |
| *** lakshmiS has quit IRC | 11:46 | |
| *** markvoelker has quit IRC | 11:49 | |
| *** david-lyle_afk is now known as david-lyle | 12:01 | |
| *** mwang2_ has joined #openstack-meeting-4 | 12:10 | |
| *** hemanth has joined #openstack-meeting-4 | 12:14 | |
| *** mwang2 has quit IRC | 12:20 | |
| *** hemanth_ has quit IRC | 12:20 | |
| *** david-lyle is now known as david-lyle_afk | 12:36 | |
| *** david-lyle_afk is now known as david-lyle | 12:36 | |
| *** david-lyle is now known as david-lyle_afk | 12:44 | |
| *** david-lyle_afk is now known as david-lyle | 12:45 | |
| *** markvoelker has joined #openstack-meeting-4 | 12:45 | |
| *** markvoelker has quit IRC | 12:49 | |
| *** markvoelker has joined #openstack-meeting-4 | 13:20 | |
| *** galstrom_zzz is now known as galstrom | 13:23 | |
| *** lakshmiS_ has quit IRC | 13:49 | |
| *** lakshmiS_ has joined #openstack-meeting-4 | 13:49 | |
| *** klamath has joined #openstack-meeting-4 | 13:54 | |
| *** klamath has quit IRC | 13:54 | |
| *** wojdev has joined #openstack-meeting-4 | 13:55 | |
| *** klamath has joined #openstack-meeting-4 | 13:55 | |
| *** jckasper has joined #openstack-meeting-4 | 14:01 | |
| *** ajmiller has quit IRC | 14:03 | |
| *** galstrom is now known as galstrom_zzz | 14:09 | |
| *** kobis has joined #openstack-meeting-4 | 14:10 | |
| *** belmoreira has joined #openstack-meeting-4 | 14:11 | |
| *** jckasper has quit IRC | 14:18 | |
| *** jckasper has joined #openstack-meeting-4 | 14:19 | |
| *** kobis has quit IRC | 14:21 | |
| *** VW_ has joined #openstack-meeting-4 | 14:24 | |
| *** lennyb has joined #openstack-meeting-4 | 14:59 | |
| *** omrim has joined #openstack-meeting-4 | 14:59 | |
| *** sigmavirus24_awa is now known as sigmavirus24 | 15:00 | |
| krtaylor | #startmeeting third-party | 15:00 |
|---|---|---|
| openstack | Meeting started Wed Feb 4 15:00:48 2015 UTC and is due to finish in 60 minutes. The chair is krtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| *** openstack changes topic to " (Meeting topic: third-party)" | 15:00 | |
| openstack | The meeting name has been set to 'third_party' | 15:00 |
| omrim | Hello | 15:00 |
| mmedvede | o/ | 15:01 |
| rfolco | Hi | 15:01 |
| krtaylor | who is here for the Third Party CI Working Group meeting? | 15:01 |
| omrim | omrim | 15:01 |
| lennyb | Hello, My name is Lenny, I work for Mellanox and will be working on our CI. | 15:01 |
| krtaylor | hi lennyb | 15:01 |
| krtaylor | hi omrim | 15:01 |
| omrim | krtaylor: Hello :) | 15:02 |
| *** ja has joined #openstack-meeting-4 | 15:02 | |
| ja | moin moin | 15:02 |
| krtaylor | ok, well let's get started, we have a full agenda today | 15:02 |
| krtaylor | hi ja | 15:02 |
| krtaylor | #topic Third-party CI documentation | 15:02 |
| *** openstack changes topic to "Third-party CI documentation (Meeting topic: third-party)" | 15:02 | |
| *** rhe00_ has joined #openstack-meeting-4 | 15:02 | |
| ja | howdy krtaylor | 15:03 |
| krtaylor | so, the documentation sprint went well, but we still have a lot of work to do | 15:03 |
| krtaylor | omrim, you are going to help us get a FAQ going right? | 15:03 |
| omrim | krtaylor: Yes, I will be glad to get some great refernces | 15:04 |
| krtaylor | you can use the etherpad to gather ideas if you wish, or start a new one | 15:04 |
| krtaylor | #link https://etherpad.openstack.org/p/third-party-ci-documentation | 15:04 |
| krtaylor | there is the link, for everyone else | 15:05 |
| rfolco | will revisit there and see what is missing | 15:05 |
| krtaylor | ja, I think you have some interesting points in the Meta-comments | 15:05 |
| krtaylor | those could be turned into patches | 15:05 |
| krtaylor | rfolco, yes please, that woul dbe great | 15:06 |
| krtaylor | and would be great too | 15:06 |
| krtaylor | we have done a pretty good job on third-party.rst | 15:06 |
| krtaylor | but running-your-own.rst is untouched | 15:07 |
| krtaylor | it needs the most work | 15:07 |
| ja | are there any upcoming milestones that make it harder/easier to do patches at a given time? I'm unsure how/if the overall release dates affect documentation patches. | 15:07 |
| krtaylor | we can divide that up to make progress | 15:07 |
| krtaylor | ja, good question, but we are still in the middle of kilo | 15:08 |
| krtaylor | we should be good for several more weeks | 15:08 |
| *** kobis has joined #openstack-meeting-4 | 15:08 | |
| krtaylor | and since docs don't hurt anything else, it should be fairly independent of release schedules | 15:09 |
| krtaylor | so, any volunteers for running-your-own? | 15:09 |
| ja | krtaylor, that's the point of the question... interaction between doc and release dates. e.g. in w3c there is a "quiet period" at certain points where nothing new gets published. | 15:09 |
| ja | ... little/no interaction was the hoped-for state | 15:10 |
| krtaylor | ja, oh, yeah I remember that, no nothing like that here | 15:10 |
| krtaylor | especially for what we are doing to help external testing | 15:10 |
| ja | krtaylor, is the same true of the puppet splits or will those "have" to quiesce "during" the release? | 15:11 |
| *** numan has quit IRC | 15:11 | |
| krtaylor | lennyb, getting your perspective on the documentation would be really good, and we can help you get started in patch writing | 15:11 |
| krtaylor | ja, not sure I understand, do you mean for adopting the module split-out? | 15:12 |
| ja | ... if the CI work is closer to ... well, CI process... that's ideal for me at least. | 15:12 |
| lennyb | ok, | 15:12 |
| ja | krtaylor, since puppet is "code" not "doc" it might have to play by different rules - that was the point of that question | 15:12 |
| *** wojdev_ has joined #openstack-meeting-4 | 15:13 | |
| krtaylor | ja, good stuff, but lets focus on docs for the moment, can we discuss that at the end in open discussion? | 15:13 |
| ja | sure | 15:13 |
| *** wojdev has quit IRC | 15:13 | |
| *** wojdev_ is now known as wojdev | 15:13 | |
| krtaylor | ok, so how do we get the running-your-own to move forward? | 15:14 |
| krtaylor | do we need to assign chunks? any volunteers? | 15:14 |
| krtaylor | I'll be in, obviously | 15:14 |
| *** rm_work|away is now known as rm_work | 15:14 | |
| rfolco | seems to be huge | 15:15 |
| krtaylor | yes, and needs the most work | 15:15 |
| krtaylor | So, I'll take the requirements section | 15:15 |
| krtaylor | everyone, grab a section in the etherpad | 15:16 |
| ja | do we have consensus on what purposes it is intended to serve? e.g. purely reference, closer to tutorial | 15:16 |
| ja | ...I wouldn't really know what to put into a patch until I understand where the wg wants it to land. | 15:16 |
| *** pmesserli has joined #openstack-meeting-4 | 15:17 | |
| krtaylor | ja, I think refreshing what is there is the first goal, but including links to other parts of the existing documentation is a really good thing | 15:17 |
| krtaylor | so, reuse the infra manual as much as possible | 15:18 |
| rfolco | I guess for running-your-own it's just an update. You need a balance between detailed/superficial | 15:18 |
| krtaylor | we, as a work group, own keeping this document up to date, so minimizing revisions by referencing other infra docs is a priority | 15:18 |
| krtaylor | rfolco, yes | 15:18 |
| krtaylor | ok, well, I encourage everyone to read that doc and think about a section to re-write, its a great way to get started in the community | 15:20 |
| krtaylor | #link http://ci.openstack.org/running-your-own.html | 15:20 |
| krtaylor | just for completeness | 15:20 |
| krtaylor | also remember to please set topic to 'third-party-ci-documentation' | 15:21 |
| krtaylor | on any patches, makes it easier to track as a group | 15:21 |
| krtaylor | ok, any questions on documentation, else we'll move on | 15:21 |
| ja | If I see its current form as a reference, and I think a tutorial is what newbies really need, is the net that I should just write it all up as a patch first and then see if reviewers like it? | 15:21 |
| krtaylor | ja, smaller is better, just start with a section | 15:22 |
| *** fnaval has joined #openstack-meeting-4 | 15:22 | |
| krtaylor | easier to review and merge | 15:22 |
| omrim | krtaylor: Great doc thanks | 15:22 |
| krtaylor | omrim, thank you for your FAQ patch! | 15:23 |
| krtaylor | ok, lets move on, we have a full agenda today | 15:23 |
| krtaylor | #topic Splitting out puppet modules | 15:23 |
| *** openstack changes topic to "Splitting out puppet modules (Meeting topic: third-party)" | 15:23 | |
| krtaylor | I left this on the agenda, but just to summarize | 15:24 |
| krtaylor | not sure if we have asselin yet, its early for him | 15:24 |
| krtaylor | it was a tremendous success | 15:24 |
| krtaylor | and a lot of fun | 15:24 |
| mmedvede | +1 | 15:25 |
| krtaylor | thanks mmedvede for a big part, how many patches? | 15:25 |
| mmedvede | I think I did 14 during the sprint | 15:25 |
| mmedvede | modules | 15:25 |
| mmedvede | ~3 patches per module | 15:25 |
| krtaylor | wow, nice | 15:25 |
| krtaylor | yeah, I did a search to see and stopped counting after a page | 15:26 |
| krtaylor | any thoughts about what went well in the sprint, what didnt? | 15:26 |
| mmedvede | The result is that now puppet modules are in their own projects. And we are encouraged to make those modules more consumable by 3rd parties | 15:27 |
| mmedvede | krtaylor: the ordering was an issue | 15:27 |
| krtaylor | I think pleia2 is going to summarize the virtual sprints in general via email, more teams should consider them | 15:28 |
| krtaylor | mmedvede, agreed | 15:28 |
| mmedvede | a lot of merge conflicts. We should have figured out a way to avoid this. Other than that, it was efficient | 15:28 |
| krtaylor | rebase, rebase, rebase | 15:28 |
| *** yamahata has joined #openstack-meeting-4 | 15:28 | |
| krtaylor | it was amazing, good infra core participation was critical | 15:29 |
| mmedvede | Infra team helped a lot | 15:29 |
| krtaylor | ok, lets move on | 15:29 |
| krtaylor | #topic Spec for in-tree 3rd party ci solution | 15:29 |
| *** openstack changes topic to "Spec for in-tree 3rd party ci solution (Meeting topic: third-party)" | 15:29 | |
| krtaylor | please review this spec, it is a really good direction and a place where we can get involved | 15:30 |
| krtaylor | #link https://review.openstack.org/#/c/139745/ | 15:30 |
| krtaylor | I know asselin would appreciate any feedback or ideas | 15:31 |
| krtaylor | and finally | 15:32 |
| krtaylor | #topic Highlighting Third-Party CI Service | 15:32 |
| *** openstack changes topic to "Highlighting Third-Party CI Service (Meeting topic: third-party)" | 15:32 | |
| krtaylor | this was an idea we had last year, that I wanted to start doing again | 15:32 |
| krtaylor | one of the goals of this work group is to help each other out, and share how we solved the hard problems | 15:33 |
| krtaylor | so, to kick this off again | 15:33 |
| krtaylor | I figured that I would volunteer my team | 15:33 |
| krtaylor | and specifically rfolco | 15:33 |
| *** VW_ has quit IRC | 15:33 | |
| krtaylor | to come and share what we are doing | 15:33 |
| krtaylor | and how we solved some problems in our environment | 15:33 |
| *** wojdev has quit IRC | 15:34 | |
| krtaylor | so, rfolco it is all yours | 15:34 |
| rfolco | sure I'll just summarize few topics due to the limitation of this format and time | 15:35 |
| rfolco | and make breaks for questions | 15:35 |
| *** fnaval has quit IRC | 15:35 | |
| rfolco | We'll base the discussions on the article https://www.ibm.com/developerworks/community/blogs/fe313521-2e95-46f2-817d-44a4f27eba32/entry/building_your_openstack_3rd_party_ci_system1?lang=en. | 15:35 |
| rfolco | For this meeting we're going to focus on the problems we solved and also on the improvements we've made so far. | 15:35 |
| *** fnaval has joined #openstack-meeting-4 | 15:35 | |
| krtaylor | #link https://www.ibm.com/developerworks/community/blogs/fe313521-2e95-46f2-817d-44a4f27eba32/entry/building_your_openstack_3rd_party_ci_system1?lang=en | 15:36 |
| rfolco | so how did we avoid our CI to break every time Openstack Infra changed their code? | 15:36 |
| rfolco | Successful rate of builds in Jenkins increased from ~60% to ~97% after implementing two separate envioments: production and development. Before that the CI system was so sensitive and broke more often. | 15:37 |
| rfolco | A typical CI system needs custom code and configuration overrides on top of OpenStack Infra code (system-config and project-config). Pinning these projects to a code level on production environment increased stability of our CI jobs significantly. | 15:37 |
| rfolco | --pause for questions-- | 15:37 |
| ja | rfolco, how much of that breakage do you think would be addressed by the puppet work? | 15:37 |
| rfolco | I don't have a good estimate number, but I think about 30% more or less | 15:38 |
| krtaylor | so, I guess we could also say that we are using the upstream infra ci ported to our environment, our goal was to follow them as closely as possible, but if we followed too close, we were not stable | 15:38 |
| ja | ...and thinking out loud, does it suggest that *infra* needs a CI process to avoid breaking 3rd parties | 15:38 |
| ja | 30% is pretty substantial | 15:39 |
| krtaylor | ja, no, not their concern, it is up to us to address | 15:39 |
| rfolco | the problem ja, is that we had in the beginning some code overrides, not only configuration | 15:39 |
| rfolco | our fault on designing a stable CI that does not have workarounds or hacks in the code | 15:40 |
| rfolco | he right way to do it is to override config | 15:40 |
| rfolco | so now we pin the code to a stable code level that we know that works | 15:40 |
| *** ChuckC has joined #openstack-meeting-4 | 15:40 | |
| ja | +1 on overriding config as the right way | 15:40 |
| rfolco | and do experiements / test on a separate environment (dev) | 15:40 |
| mmedvede | ja, puppet split work should reduce the amount of custom puppet code we have, this is a big advantage | 15:40 |
| krtaylor | ++ | 15:41 |
| *** ChuckC_ has quit IRC | 15:41 | |
| rfolco | ok so moving on | 15:41 |
| wznoinsk | hi rfolco | 15:41 |
| rfolco | Production services Jenkins, Nodepool and Zuul run on VMs in an x86 cloud. Each of these services has a "clone" for the development environment. This enables a better control of code levels in each service. Another advantage is the ability of creating snapshots for the services. | 15:41 |
| rfolco | feel free to ask any questions wznoinsk, this is more fun being interactive :) | 15:42 |
| wznoinsk | in what situations config from upstream has to be updated in 3rd party ci? I'm not using Zuul/Puppet at this very moment would there be something I'd need from upstream infra projects in this case? | 15:42 |
| *** ajmiller has joined #openstack-meeting-4 | 15:43 | |
| rfolco | Well all depends on your needs | 15:43 |
| rfolco | if you wanna report back to community, yes, you need to override zuul yaml config with your config | 15:43 |
| * krtaylor notes a good documentation topic | 15:44 | |
| rfolco | this is just an example, the article details better the most common overrides you have to make, and what are their purposes | 15:44 |
| rfolco | in our case, we started testing NOva project | 15:45 |
| wznoinsk | so if I'm only using Jenkins + lxc containers in my case via docker (a basic 3rd party CI setup) and I'm always fetching master of each of openstack projects + the change proposed I can leave without getting infra configs for now? | 15:45 |
| rfolco | so we went to zuul yaml, and override upstream yaml with our custom yaml just to test Nova | 15:45 |
| wznoinsk | s/leave/live | 15:46 |
| rfolco | the key point is: do you need to trigger your test for every patch? Another important thing: if you are stable running upstream code, thats awsome | 15:46 |
| rfolco | but in our case we decided to not work with latest upstream code from Infra | 15:47 |
| rfolco | It's ok just to use Jenkins | 15:47 |
| rfolco | in case you don't need to report back and you define when your tests will run | 15:48 |
| rfolco | You can automated your builds this way, nothing wrong... | 15:48 |
| wznoinsk | with efficency of lxc container that's the plan to run on every patchset, also 'stable running upstream code' is a negation of itself ;-) | 15:48 |
| rfolco | :) | 15:48 |
| krtaylor | wznoinsk, it also depends on what and how many tests you have to run, and how big your system needs to scale | 15:49 |
| wznoinsk | I'm still able to comment back on the build, potentially listing tempest/other tests and their success separately in a single comment (without using Zuul), I'm trying to understand whether I should go the Zuul-way already ... | 15:49 |
| rfolco | zuul listens on gerrit the patches and queues jobs for you | 15:49 |
| rfolco | and reports back | 15:50 |
| *** matrohon has quit IRC | 15:50 | |
| rfolco | so you define in layout.yaml what to listen, what jobs to trigger and how to report back | 15:50 |
| rfolco | wznoinsk, I'll be happy to answer in more detail about this topic... | 15:51 |
| wznoinsk | I know it's beneficial to have Zuul when you have multiple proposed code changes that may depend on each other (two independent jenkins jobs wouldn't catch the reliance) but I don't think using Zuul is a must for 3rd party CI to have, is it? | 15:51 |
| wznoinsk | sure rfolco, I'll catch you after this meeting | 15:52 |
| krtaylor | wznoinsk, I would really like to hear about your environment, can I schedule you for an upcoming week to tell us about it? | 15:52 |
| ja | My impression is that the choice of implementation components on your side of the firewall is yours. In that sense, the ssh mechanism Zuul uses and so on is "interface" not "implementation" | 15:53 |
| wznoinsk | krtaylor: yes, with pleasure, thanks | 15:53 |
| rfolco | as I said you can run your CI without it, but its easier with zuul I think | 15:53 |
| ja | ...of course, as with any community, using what others use makes it easier to find help and give it | 15:53 |
| wznoinsk | ja I'd agree, but without Zuul 3rd party CI tests could be missing some of the code breakages that may happen when two/more code changes can break each other | 15:54 |
| krtaylor | rfolco, we had several areas that we made modifications right? | 15:54 |
| rfolco | yes, | 15:54 |
| rfolco | The customizations required to run a 3rd-party CI include changes in: layout.yaml (Zuul); nodepool.yaml; (Nodepool); projects.yaml & devstack-gate.yaml (Jnkins Job Builder). | 15:54 |
| rfolco | To override code and configurations two internal Git repositories have been created: (1) puppet-config, which overrides code and configuration; and (2) ibm-devstack-gate, which contains additional customizations for devstack-gate jobs such as regex file (skip list for Tempest), pre_test_hook.sh and Swift upload log script. | 15:54 |
| rfolco | Both internal repositories (puppet-config and ibm-devstack-gate) work in different branches: dev (development) and master (production). To turn reporting off on production one needs to checkout puppet-config master branch and comment out the lines "success" and "failure" in layout.yaml. Changing base image or memory requirements for slaves in Development Nodepool, one would change nodepool.ya | 15:55 |
| rfolco | ml in the repository but push changes to dev branch instead. The same idea applies to JJB configuration files. It's also possible to checkout ibm-devstack-gate and modify regex file and include a new test to the skip list for Tempest runs. | 15:55 |
| rfolco | some of the customizations and where we spent more time on out CI: | 15:56 |
| rfolco | (1) Build the cloud infrastructure for the services and compute nodes (2) Install and configure services using Puppet (3) Build CirrOS for Power with mainline kernel (4) Skip Tempest failures (5) Resolve devstack-gate problems on Power platform by overriding config (6) Build custom MySQL to resolve issues on Power (7) Map and debug Tempest failures (8) Investigate concurrency problems for Tem | 15:56 |
| rfolco | pest (9) Cleanup database for expired keystone entries and deleted instances (our current problem this week) (10) Upload script to Softlayer Swift. | 15:56 |
| rfolco | I'm open for anybody to ping me after the meeting nd detail better any of these | 15:57 |
| rfolco | back to you Kurt since time is over :) | 15:57 |
| rhe00_ | rfolco: thanks for writing up the article. Very informative. | 15:57 |
| krtaylor | the blog illustrates this pretty well | 15:58 |
| wznoinsk | rfolco: thanks for getting it all together, it's a compact version of what you should know about 3rd party ci, learned a few new things from it as well | 15:58 |
| rfolco | thats great to hear | 15:58 |
| krtaylor | well, we are still learning how to do this, but rfolco, this was a really good kickoff | 15:58 |
| rfolco | thanks guys.. wznoinsk if you wanna discuss zuul role better let me know | 15:59 |
| krtaylor | I hope to get every CI team to come and share how they fixed problems for their environment | 15:59 |
| krtaylor | we are out of time, thanks everyone | 15:59 |
| rfolco | thx | 15:59 |
| krtaylor | really good meeting, see you next time | 15:59 |
| krtaylor | #endmeeting | 16:00 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:00 | |
| openstack | Meeting ended Wed Feb 4 16:00:34 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:00 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-02-04-15.00.html | 16:00 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-02-04-15.00.txt | 16:00 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/third_party/2015/third_party.2015-02-04-15.00.log.html | 16:00 |
| *** VW_ has joined #openstack-meeting-4 | 16:00 | |
| *** sarob has joined #openstack-meeting-4 | 16:00 | |
| *** lennyb has quit IRC | 16:05 | |
| *** galstrom_zzz is now known as galstrom | 16:06 | |
| *** wojdev has joined #openstack-meeting-4 | 16:09 | |
| *** ja has quit IRC | 16:11 | |
| *** wojdev has quit IRC | 16:12 | |
| *** pmesserli has left #openstack-meeting-4 | 16:12 | |
| *** ChuckC_ has joined #openstack-meeting-4 | 16:14 | |
| *** carl_baldwin has joined #openstack-meeting-4 | 16:16 | |
| *** ChuckC has quit IRC | 16:17 | |
| *** SridharRamaswamy has joined #openstack-meeting-4 | 16:30 | |
| *** SridharRamaswam1 has joined #openstack-meeting-4 | 16:33 | |
| *** SridharRamaswamy has quit IRC | 16:34 | |
| *** banix_ has joined #openstack-meeting-4 | 16:43 | |
| *** belmoreira has quit IRC | 16:52 | |
| *** galstrom is now known as galstrom_zzz | 16:55 | |
| *** galstrom_zzz is now known as galstrom | 16:56 | |
| *** banix_ has quit IRC | 17:01 | |
| yamahata | hello | 17:01 |
| *** s3wong has joined #openstack-meeting-4 | 17:04 | |
| yamahata | hi | 17:04 |
| s3wong | hello | 17:04 |
| SridharRamaswam1 | hi | 17:05 |
| yamahata | #startmeeting servicevm-device-manager | 17:05 |
| openstack | Meeting started Wed Feb 4 17:05:28 2015 UTC and is due to finish in 60 minutes. The chair is yamahata. Information about MeetBot at http://wiki.debian.org/MeetBot. | 17:05 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 17:05 |
| *** openstack changes topic to " (Meeting topic: servicevm-device-manager)" | 17:05 | |
| openstack | The meeting name has been set to 'servicevm_device_manager' | 17:05 |
| yamahata | #chair s3wong SridharRamaswam1 | 17:05 |
| openstack | Current chairs: SridharRamaswam1 s3wong yamahata | 17:05 |
| s3wong | seems like just the three of us | 17:06 |
| *** [1]evgenyf has quit IRC | 17:06 | |
| yamahata | giving few minutes others... | 17:07 |
| s3wong | well, bobmel and hareeshpc aren't on channels | 17:09 |
| yamahata | unfortunately. | 17:09 |
| yamahata | okay let's start. | 17:10 |
| yamahata | #topic Announcement | 17:10 |
| *** openstack changes topic to "Announcement (Meeting topic: servicevm-device-manager)" | 17:10 | |
| yamahata | thank you for attending the f2f last week. | 17:10 |
| SridharRamaswam1 | sure | 17:10 |
| yamahata | the conclusion is, | 17:11 |
| yamahata | the important thing is to articulate the need and use cases for the value | 17:11 |
| yamahata | The very shot version. | 17:11 |
| yamahata | SridharRamaswam1: s3wong do you want to add more? | 17:12 |
| s3wong | yamahata: I sent out a meeting minute --- so it was captured there | 17:13 |
| SridharRamaswam1 | yes, s3wong has nicely summarized the outcome in the email | 17:13 |
| yamahata | Ah yes. | 17:13 |
| yamahata | s3wong: do you mind that is's public on wiki? | 17:13 |
| yamahata | Sorry. Let's move on. | 17:14 |
| s3wong | yamahata: np. sure | 17:14 |
| *** vishwanathj has joined #openstack-meeting-4 | 17:15 | |
| yamahata | #topic discussion on L3 service insertion and its scope | 17:16 |
| *** openstack changes topic to "discussion on L3 service insertion and its scope (Meeting topic: servicevm-device-manager)" | 17:16 | |
| yamahata | is there vks? | 17:16 |
| yamahata | After the irc meeting last week, vks wanted to discuss it and added this topic to the wiki. | 17:17 |
| yamahata | we don't have vks. | 17:18 |
| s3wong | yamahata: what is l3 service insertion? | 17:18 |
| yamahata | I guess how/where service is instantiated. But I'm not sure what he wanted to discuss. | 17:19 |
| yamahata | Personally I think FWaaS is pioneering on this front. | 17:19 |
| yamahata | For Kilo cycle, FWaaS just tries simple one. | 17:20 |
| yamahata | #link https://blueprints.launchpad.net/neutron/+spec/fwaas-router-insertion | 17:20 |
| yamahata | #link https://review.openstack.org/#/c/138672/ | 17:20 |
| *** matrohon has joined #openstack-meeting-4 | 17:20 | |
| yamahata | #topic Open Discussion | 17:22 |
| *** openstack changes topic to "Open Discussion (Meeting topic: servicevm-device-manager)" | 17:22 | |
| yamahata | move on | 17:22 |
| s3wong | yamahata: FWaaS insertion, by SridarK, is to insert FW into per router rather than on all routers, AFAIU | 17:22 |
| yamahata | #undo | 17:22 |
| openstack | Removing item from minutes: <ircmeeting.items.Topic object at 0x3635ed0> | 17:22 |
| s3wong | L3 service insertion can mean a variety of things | 17:23 |
| s3wong | for FW, most likely it means traffic ingress from a particular subnet (router interface(s)) should be subjected to the FW service | 17:24 |
| s3wong | or traffic egress to a particular subnet should be subjected to FW service | 17:24 |
| s3wong | this currently cannot be represented by Neutron | 17:24 |
| s3wong | during the meeting, SridarK put up a use case that is even simpler | 17:25 |
| s3wong | a Neutron port to another Neutron port on the same Neutron network, can we selectively direct traffic to a service | 17:25 |
| s3wong | "bump in the wire" | 17:25 |
| s3wong | so overall, one suggestion during last Friday's meeting is to find ways to provide these kinds of abstraction (on API layer) and the appropriate driver / plugin to implement the behavior as part of Tacker framework | 17:26 |
| s3wong | and if it means the Tacker "service insertion" driver needs to be of the same type (for example, OVS) as Neutron, that is OK | 17:27 |
| s3wong | furthermore, SridharRamaswam1 suggested we should extend this to a flow level forwarding abstraction, which excludes a very big chunk of current Neutron plugins/drivers; and we are fine with that | 17:28 |
| yamahata | thanks for good summary. | 17:31 |
| yamahata | #topic Open Discussion | 17:32 |
| *** openstack changes topic to "Open Discussion (Meeting topic: servicevm-device-manager)" | 17:32 | |
| yamahata | anything else to discuss? | 17:32 |
| s3wong | "Call for Speaker" proposal deadline for the L-Summit is next Monday | 17:32 |
| yamahata | good point | 17:33 |
| yamahata | #info "Call for Speaker" proposal deadline for the L-Summit is next Monday | 17:33 |
| s3wong | I do realize we are somewhat in a limbo on Tacker (seems like we don't really have a fixed direction yet); but perhaps we can put our vague new direction as a way to introduce Tacker to the wider community? | 17:33 |
| yamahata | Sure, I'll try to come up with some abstract for "Call for Speaker" | 17:34 |
| s3wong | yamahata: I can work on a rough draft too, and send it to you also | 17:35 |
| s3wong | SridharRamaswam1: are you interested? | 17:35 |
| yamahata | #action yamahata, s3wong sent a draft of CfS | 17:35 |
| s3wong | well, that's all I have anyway | 17:37 |
| yamahata | thank you everyone | 17:37 |
| yamahata | #endmeeting | 17:37 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 17:37 | |
| openstack | Meeting ended Wed Feb 4 17:37:51 2015 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 17:37 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2015/servicevm_device_manager.2015-02-04-17.05.html | 17:37 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2015/servicevm_device_manager.2015-02-04-17.05.txt | 17:37 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/servicevm_device_manager/2015/servicevm_device_manager.2015-02-04-17.05.log.html | 17:37 |
| *** SridharRamaswam1 has quit IRC | 17:38 | |
| *** SridharRamaswamy has joined #openstack-meeting-4 | 17:38 | |
| SridharRamaswamy | folks, sorry, fighting connectivity issue | 17:38 |
| s3wong | SridharRamaswamy: I also notice your nic changed | 17:38 |
| *** banix has joined #openstack-meeting-4 | 17:39 | |
| SridharRamaswamy | +1 for a speaker abstract for Tacker | 17:39 |
| s3wong | SridharRamaswamy: OK, we will include you also :-) | 17:39 |
| s3wong | (as a speaker) | 17:39 |
| SridharRamaswamy | thanks! | 17:39 |
| s3wong | OK, time to go to work. Have a good day, guys | 17:40 |
| SridharRamaswamy | s3wong: have a nice one | 17:40 |
| *** s3wong has quit IRC | 17:40 | |
| *** rhe00_ has left #openstack-meeting-4 | 17:57 | |
| *** VW_ has quit IRC | 17:59 | |
| *** SumitNaiksatam has joined #openstack-meeting-4 | 18:01 | |
| *** Salman has joined #openstack-meeting-4 | 18:11 | |
| *** yamahata has quit IRC | 18:14 | |
| *** SridharRamaswam1 has joined #openstack-meeting-4 | 18:19 | |
| *** SridharRamaswamy has quit IRC | 18:19 | |
| *** IRTermite has quit IRC | 18:30 | |
| *** yamahata has joined #openstack-meeting-4 | 18:37 | |
| *** lakshmiS_ has quit IRC | 18:38 | |
| *** Salman has quit IRC | 18:41 | |
| *** sarob has quit IRC | 18:43 | |
| *** IRTermite has joined #openstack-meeting-4 | 18:45 | |
| *** jckasper has quit IRC | 18:54 | |
| *** sarob has joined #openstack-meeting-4 | 19:06 | |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 19:09 | |
| *** VW_ has joined #openstack-meeting-4 | 19:10 | |
| *** ivar-lazzaro has quit IRC | 19:11 | |
| *** ivar-lazzaro has joined #openstack-meeting-4 | 19:12 | |
| *** kobis has quit IRC | 19:25 | |
| *** kobis has joined #openstack-meeting-4 | 19:27 | |
| *** kobis has quit IRC | 19:29 | |
| *** kobis has joined #openstack-meeting-4 | 19:32 | |
| *** rfolco has quit IRC | 19:34 | |
| *** vishwanathj has quit IRC | 19:37 | |
| *** jckasper has joined #openstack-meeting-4 | 19:42 | |
| *** pmesserli has joined #openstack-meeting-4 | 19:44 | |
| *** pmesserli has quit IRC | 19:48 | |
| *** carl_baldwin has quit IRC | 19:49 | |
| *** carl_baldwin has joined #openstack-meeting-4 | 19:52 | |
| *** VW_ has quit IRC | 19:59 | |
| *** rfolco has joined #openstack-meeting-4 | 20:00 | |
| *** VW_ has joined #openstack-meeting-4 | 20:02 | |
| *** pmesserli has joined #openstack-meeting-4 | 20:03 | |
| *** sarob has quit IRC | 20:13 | |
| *** sarob has joined #openstack-meeting-4 | 20:16 | |
| *** vishwanathj has joined #openstack-meeting-4 | 20:24 | |
| *** carl_baldwin has quit IRC | 20:25 | |
| *** sarob has quit IRC | 20:31 | |
| *** fnaval_ has joined #openstack-meeting-4 | 20:41 | |
| *** fnaval has quit IRC | 20:45 | |
| *** matrohon has quit IRC | 20:48 | |
| *** galstrom has left #openstack-meeting-4 | 20:51 | |
| *** fnaval_ has quit IRC | 20:57 | |
| *** fnaval has joined #openstack-meeting-4 | 20:57 | |
| *** ChuckC_ is now known as ChuckC | 21:16 | |
| *** rfolco has quit IRC | 21:28 | |
| *** rfolco has joined #openstack-meeting-4 | 21:32 | |
| *** sarob has joined #openstack-meeting-4 | 21:32 | |
| *** d34dh0r53 is now known as blarnath | 21:48 | |
| *** pmesserli has quit IRC | 21:48 | |
| *** belmoreira has joined #openstack-meeting-4 | 21:48 | |
| *** pmesserli has joined #openstack-meeting-4 | 21:49 | |
| *** pmesserli has quit IRC | 21:52 | |
| *** pmesserli has joined #openstack-meeting-4 | 21:52 | |
| *** carl_baldwin has joined #openstack-meeting-4 | 21:52 | |
| *** sarob has quit IRC | 21:54 | |
| *** carl_baldwin has quit IRC | 21:59 | |
| *** s3wong has joined #openstack-meeting-4 | 22:04 | |
| *** blarnath is now known as d34dh0r53 | 22:05 | |
| *** s3wong has quit IRC | 22:36 | |
| *** klamath has quit IRC | 23:15 | |
| *** belmoreira has quit IRC | 23:20 | |
| *** banix has quit IRC | 23:20 | |
| *** fnaval has quit IRC | 23:29 | |
| *** ajmiller has quit IRC | 23:39 | |
| *** kobis has quit IRC | 23:50 | |
| *** markvoelker has quit IRC | 23:56 | |
| *** rm_work is now known as rm_work|away | 23:56 | |
| *** pmesserli has quit IRC | 23:58 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!