18:00:57 <krtaylor> #startmeeting third-party
18:00:58 <openstack> Meeting started Mon Oct 20 18:00:57 2014 UTC and is due to finish in 60 minutes.  The chair is krtaylor. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:59 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:01:02 <openstack> The meeting name has been set to 'third_party'
18:01:19 <krtaylor> anyone here for third-party?
18:01:24 <asselin> hi
18:01:26 * ctlaugh_ is here
18:01:29 <patrickeast> hey
18:01:40 <luqas> hi
18:02:03 <krtaylor> hey everyone
18:02:20 <mmedvede> o/
18:02:32 <krtaylor> we have another light agenda today
18:02:43 <krtaylor> thanks goodness for down time between releases
18:03:05 <krtaylor> but it will leave us with plenty of open discussion time
18:03:22 <krtaylor> topic Welcome & Reminder of OpenStack Mission
18:03:49 <krtaylor> hm
18:03:50 <krtaylor> #topic Welcome & Reminder of OpenStack Mission
18:03:59 <krtaylor> that's better
18:04:10 <krtaylor> #info The OpenStack Open Source Cloud Mission: to produce the ubiquitous Open Source Cloud Computing platform that will meet the needs of public and private clouds regardless of size, by being simple to implement and massively scalable.
18:04:46 <krtaylor> and here's a link to the agenda, pretty light as I said before:
18:04:50 <krtaylor> #link https://wiki.openstack.org/wiki/Meetings/ThirdParty#10.2F20.2F14
18:05:16 <krtaylor> #topic Review of previous week's open action items
18:05:24 <krtaylor> so, I show no action items
18:05:37 <krtaylor> #topic Announcements
18:05:49 <krtaylor> any announcements?
18:06:29 <krtaylor> ok, next then
18:06:40 <krtaylor> #topic OpenStack Program items
18:07:16 <krtaylor> only thing here is I left the session link in case someone missed it last week
18:07:29 <krtaylor> #link http://kilodesignsummit.sched.org/event/9902dac01525691e60ac94bf236569c6#
18:07:49 <krtaylor> I'm really looking forward to meeting everyone
18:08:16 <krtaylor> #topic Deadlines & Deprecations
18:08:35 <krtaylor> I doubt we have any deadlines to communicate this week :)
18:08:50 <krtaylor> #topic Highlighting a Program or Gerrit Account
18:09:26 <krtaylor> nothing here, I need to get volunteers to talk about their CI environment, how it is working for them, etc
18:09:44 <krtaylor> pick a week and we'll get you on the agenda
18:09:59 <krtaylor> I suspect that we'll see this pick up again after summit
18:10:40 <krtaylor> well, the time everyone has been waiting for...
18:10:44 <krtaylor> #topic Open Discussion
18:10:55 <jesusaurus> krtaylor: what do you want out of a talk about a ci environment?
18:10:57 <krtaylor> open floor, what's on everyone's mind
18:11:37 <cpowell> krtaylor: I requested a CI account several weeks ago and was wondering if it was possible to get a status
18:11:56 <asselin> I'd like to converge on a common ci environment setup located in -infra repo. We discussed this a while back. Interested to know who else would like to work on this..
18:11:57 <krtaylor> jesusaurus, I am looking for shared experience, others can look back on and see how others have solved problems
18:13:08 <krtaylor> cpowell, I would expect some to be here, it may have just slipped
18:13:27 <krtaylor> cpowell, if no one pops up here, ask in -infra
18:13:32 <patrickeast> asselin: I would be interested in that, not sure how much time I will have to contribute to it, but I’d definitely like to help out if I can
18:13:45 <cpowell> krtaylor: I understand. I want to make sure that nothing is blocking. I have seen other accoutns requested after mine which have been filled.
18:13:46 <krtaylor> asselin, yes
18:13:48 <asselin> patrickeast, great thanks
18:14:02 <cpowell> and I have asked in the -infra channel
18:14:14 <ctlaugh_> asselin: can you provide more details on what you are interested in?
18:14:15 <krtaylor> cpowell, was that sent to the -requests maillist?
18:14:20 <cpowell> yes
18:15:08 <anteaya> cpowell: what account? are you poppy?
18:15:09 <asselin> ctlaugh_, I have my 3rd party ci setup in github. I'd like to migrate/refactor it so it can be located in -infra project. (or use a different starting point)
18:15:16 <cpowell> anteaya: Yes, I am poppy
18:15:32 <krtaylor> asselin, I would like to see that proposed again, we have tried to discuss it at -infra meetings, but it got scattered
18:15:37 <anteaya> asselin: we discussed this, the way forward is with the puppet module split spec and the public heira spec
18:15:48 <anteaya> cpowell: yes, well there seems to be a problem
18:16:03 <anteaya> since we are getting folks from stackforge projects
18:16:08 <anteaya> wanting to set up ci
18:16:18 <anteaya> and the point of stackforge is to use our ci
18:16:32 <anteaya> so why as a stackforge project, do you need your own ci?
18:16:53 <krtaylor> asselin, my team just went through an exercise where we generalized everything we could, I think we could help
18:17:13 <krtaylor> rfolco, mmedvede ^^
18:17:23 <anteaya> asselin krtaylor you are welcome to have another agenda item on the infra meeting, but don't be surprised if the response is the same
18:17:45 <anteaya> cpowell: why do you need your own ci for a stackforge project?
18:18:03 <krtaylor> anteaya, I think the problem was that we got too specific in our request
18:18:15 <anteaya> krtaylor: how's that?
18:18:20 <asselin> anteaya, no need to add another item in -infra. We as 3rd party need to come together and commit to work on this.
18:18:24 <cpowell> anteaya: we want to ensure that changes work within our production env, as we will be consuming the product ourselves
18:18:34 <krtaylor> asselin ++
18:18:38 <cpowell> external contributions
18:18:52 <anteaya> asselin: yes, working on spliting out the puppet modules would help infra greatly
18:19:18 <anteaya> cpowell: so why is it necessary to have your own ci?
18:19:34 <anteaya> cpowell: why not write tests and jobs that run in ours
18:19:39 <anteaya> that is the point of our infra
18:19:40 <asselin> so we have asselin patrickeast krtaylor rfolco mmedvede. anyone else?
18:19:47 <jesusaurus> asselin: splitting out the modules also helps me a ton as I'm a downstream consumer of infra. its something ive been trying to find time to help with
18:20:27 <asselin> asselin patrickeast krtaylor rfolco mmedvede jesusaurus
18:20:35 <krtaylor> I think it is a good step
18:21:48 <krtaylor> infra proposed a session in Atlanta on How to improve CI, maybe we'll see part II?
18:21:49 <cpowell> anteaya: we have a number of checks that utilize specific db's and frameworks which are not available within stackforge
18:22:10 <anteaya> cpowell: well you are going to have to convince mordred then
18:22:27 <anteaya> since the trend of having a stackforge having its own ci is disturbing for us
18:22:31 <asselin> that's a good small team. Perhaps we can setup a separate working meeting, or use this one?
18:22:46 <anteaya> asselin: don't split
18:23:01 <krtaylor> cpowell, what would you report back against?
18:23:02 <anteaya> have the minimum amount of structure to get work done
18:23:25 <anteaya> asselin: and honestly any of you are welcome to ask questions in infra to learn how to do the work
18:23:35 <asselin> ok then we'll use this meeting & -infra for online discussions
18:23:35 <anteaya> don't create overheaad for yourself, create patches
18:23:36 <cpowell> anteaya: I understand. What would be the preferred method of speaking with mordred
18:23:41 <anteaya> asselin: thank you
18:24:03 <anteaya> cpowell: in the -infra channel use his name and ask your question
18:24:25 <cpowell> anteaya: ok, thank yoi
18:24:34 <krtaylor> asselin, I can help in an etherpad, put together some ideas to bring here maybe?
18:24:52 <anteaya> cpowell: welcome, just so you know I am against creating a whole bunch of ci accounts for stackforge
18:25:00 <anteaya> this was never the intention
18:25:17 <asselin> krtaylor, thanks
18:26:57 <krtaylor> ok, we are winding down maybe?
18:27:17 <anteaya> one of the things you can always do if you have a light meeting
18:27:24 <anteaya> is spot check accounts
18:27:32 <anteaya> and review them against the requirements
18:27:36 <krtaylor> +1
18:27:46 <asselin> and we'll add nibalizer who'll help us get started with puppet module split
18:27:46 <anteaya> and if any account is not meeting requirements you tell them
18:28:04 <anteaya> since you telling them will not cause their account to be disabled
18:28:26 <anteaya> so consider it a public service
18:28:49 <krtaylor> anyone here from hyper-v?
18:28:55 <krtaylor> see: https://review.openstack.org/#/c/119013/
18:29:28 <krtaylor> its not a good idea to use an IP addr, if it changes it breaks the link
18:29:41 <krtaylor> see the last comment
18:30:01 <anteaya> you can find their email on their wikipage and email them
18:30:13 <anteaya> or you can post to the -announce mailing list
18:30:19 <krtaylor> not sure if that is a hard requirement, but a bad idea none the less
18:30:27 <anteaya> worth telling them
18:30:43 <anteaya> and their wikipage should have the irc nicks of their ops
18:30:59 <krtaylor> hyper-v_ci@microsoft.com
18:31:13 <anteaya> so email and cc announce
18:31:32 <krtaylor> anyone else caught anything - this would be a soft notice  :)
18:31:45 <krtaylor> anteaya, will do
18:32:10 <anteaya> it would be a big step towards self-regulation
18:32:42 <krtaylor> oh, ociuhandu
18:32:53 <krtaylor> usually around
18:32:59 <nibalizer> ohai
18:33:07 <krtaylor> or primeministerp
18:33:57 <asselin> I see ociuhandu is also interested in common 3rd party ci (last entry of https://etherpad.openstack.org/p/kilo-third-party-items)
18:33:59 <krtaylor> anteaya, I like that so much, I am going to add it as a meeting agenda heading
18:34:44 <anteaya> krtaylor: good idea
18:35:05 <ctlaugh_> krtaylor: Are there any prerequisites to requesting a service account?
18:35:15 <krtaylor> asselin, I believe ociuhandu is going to summit also
18:35:36 <krtaylor> ctlaugh_, not many...currently
18:35:38 <asselin> krtaylor, unfortunately I won't be present.
18:35:46 <krtaylor> asselin, darn
18:36:30 <krtaylor> ctlaugh_, I believe the only one currently is to have a wiki page entry in third-party systems, although, anyone that asks me
18:36:41 <krtaylor> ctlaugh_, I tell them to do that the very last step
18:37:51 <krtaylor> ctlaugh_, we got everything running first, then asked for an account and turned on reporting
18:37:51 <ctlaugh_> krtaylor: ok, thank you.  I'll try to request the account first without the wiki page.  I don't have all the details on what to fill in there yet.
18:38:28 <ctlaugh_> Did you get everything running using an individual account/ssh key?
18:38:36 <krtaylor> ctlaugh_, I can help you through that
18:38:59 <ctlaugh_> We are nowhere near ready to report results yet -- just wanting to get things setup
18:39:01 <krtaylor> ctlaugh_, yes, except reporting, then got "official"
18:40:22 <virmitio> krtaylor: I'm from hyper-v.  my understanding is that our IP is static and not subject to change, but I'll start asking about shifting to a name.
18:40:53 <krtaylor> virmitio, great, thanks, its just a good idea
18:41:17 <krtaylor> virmitio, would you like me to send email after this meeting as a reminder?
18:41:35 <virmitio> krtaylor: probably a good idea
18:41:44 <krtaylor> virmitio, will do
18:42:46 <krtaylor> anyone notice any other systems that need anything, you know, when you were doing your daily reviews?  :)
18:42:59 * krtaylor needs to step it back up
18:43:29 <anteaya> krtaylor asselin you did notice that nibalizer is here
18:43:32 <anteaya> in channel
18:43:47 <anteaya> and probably would welcome any questions pertaining to spliting up puppet modules
18:44:33 <krtaylor> nibalizer, that would be welcome, maybe a general overview of what needs to be done for everyone?
18:45:00 <asselin> as krtaylor said the other day in -infra. It would be good if we (asselin patrickeast krtaylor rfolco mmedvede jesusaurus ociuhandu) and anyone else interested meet with nibalizer.
18:45:35 <anteaya> what is wrong with now?
18:45:39 <anteaya> right now?
18:45:44 <nibalizer> heh
18:45:51 <asselin> now is fine...
18:45:52 <nibalizer> i actually am about to go on a burrito raid
18:45:53 <anteaya> why do we have to set up anothe rmeeting?
18:45:59 <nibalizer> but i can briefly get into it
18:46:09 <asselin> (b/c nibalizer wasn't chiming in....)
18:46:09 <anteaya> nibalizer: 15 minutes left in the meeting
18:46:36 <nibalizer> anteaya: help me out here for a sec, where is the specs?
18:46:53 * krtaylor was looking too
18:46:53 <asselin> http://git.openstack.org/cgit/openstack-infra/infra-specs/tree/specs/puppet-modules.rst
18:47:02 <nibalizer> https://github.com/openstack-infra/infra-specs/blob/master/specs/puppet-modules.rst
18:47:06 <nibalizer> ya that^
18:47:15 <nibalizer> there is a nice rendered one somewhere
18:47:21 <nibalizer> but we dont need that
18:47:36 <nibalizer> basically everything in openstack-infra/modules/* should become its own module
18:47:43 <jesusaurus> http://specs.openstack.org/openstack-infra/infra-specs/specs/config-repo-split.html
18:47:49 <nibalizer> those modules should live under openstack as openstack-infra/puppet-THING
18:47:57 <nibalizer> now there are a couple cases where we don't want to do that
18:48:02 <nibalizer> openstack_project should stay where it is
18:48:03 <asselin> hi nibalizer I read the spec, the the biggest unknown for me is how to test: http://git.openstack.org/cgit/openstack-infra/infra-specs/tree/specs/puppet-modules.rst#n239
18:48:59 <asselin> here's the nicely formatted one: http://specs.openstack.org/openstack-infra/infra-specs/specs/puppet-modules.html
18:49:00 <nibalizer> so thats actually not really the job of the splitter?
18:49:13 <nibalizer> so the person doing the splitting should NOT be writing those tests
18:49:16 <nibalizer> at least durring the split
18:49:24 <nibalizer> the split action comes down to these bullet points
18:49:32 <nibalizer> git clone system-config
18:49:35 <nibalizer> cd system-config
18:49:45 <nibalizer> git subtree split --prefix=modules/derp --branch derp
18:49:55 <nibalizer> git remote add <you> <yourgithub>/derp
18:50:13 <nibalizer> then you make a commit to project-config that adds the openstack-infra/puppet-derp project, with yourgithub/derp as the upstream
18:50:18 <nibalizer> once that's been pulled in
18:50:21 <nibalizer> two more things happen
18:50:42 <nibalizer> 1) we make a review against system-config to nuke out all of the old module, as well as adding the module to install_modules.sh
18:50:50 <nibalizer> 2) we start writing unit and acceptance tests for the module
18:51:06 <anteaya> just focus on getting the patch up to project-config
18:51:17 <anteaya> once you do that, I can beat anything you offer into shape
18:51:22 <nibalizer> exactly
18:51:31 <anteaya> and we will worry about the system-config and testing steps
18:51:44 <anteaya> just make a start
18:51:49 <anteaya> even a bad start is something
18:51:57 <krtaylor> cool, I'm in, I can do that!
18:52:04 <anteaya> great thank you
18:52:04 <krtaylor> hehheh
18:52:16 <anteaya> assign yourself any module on in the story on storyboard
18:52:19 <mmedvede> that sounds simple enough, thanks for clearing it up
18:52:23 <anteaya> nibalizer: have a link to the story?
18:52:32 <krtaylor> I do, one sec
18:53:24 <nibalizer> https://storyboard.openstack.org/#!/story/302
18:53:33 <nibalizer> so the thing about that is i tried to add all the modules as sub tasks
18:53:43 <anteaya> #link https://storyboard.openstack.org/#!/story/302
18:53:48 <nibalizer> and now only like 15-20 show up
18:53:55 <nibalizer> so not sure if thats a storybaord bug, or what
18:54:11 <mordred> anteaya, cpowell: I may also be overreacting to the original thing - so let's definitely snc up
18:54:17 <anteaya> well if we can address the 15 that show up, that is a start
18:54:41 <anteaya> so for third party, just pick something you can see and assign it to yourself
18:54:50 <asselin> so the first task "Split out Puppet Modules"....each task is one like that right?
18:54:57 <anteaya> once you have a focus we can answer your questions as you go through
18:55:05 <anteaya> but ask, and then do something
18:55:10 <anteaya> and then ask again
18:55:45 <asselin> ok I got one
18:56:12 <nibalizer> okay i g2g thanks everyone!
18:56:26 <nibalizer> feel free to hilight me and jesusaurus in -infra if you have questions
18:56:26 <krtaylor> thanks nibalizer
18:56:33 <asselin> thank you
18:57:20 <anteaya> nibalizer: thank you
18:57:31 <anteaya> asselin: thanks for taking a task
18:57:52 <asselin> I was just able to add a test task
18:57:58 <anteaya> asselin: so ask lots of questions
18:58:00 <anteaya> fine
18:58:10 <anteaya> since once everyone sees how to do one
18:58:18 <anteaya> hopefully everyone will learn
18:58:25 <asselin> so we should be able to add the other puppet modules as tasks...
18:58:27 <anteaya> and the steps will be the same
18:58:36 <anteaya> let's just worry about jenkins
18:58:42 <anteaya> until after jenkins is done
18:58:55 <anteaya> stay focused until it is finished
18:59:16 <krtaylor> go asselin, go asselin  :)
18:59:22 <asselin> lol thanks :)
18:59:32 <krtaylor> another great meeting out of a light agenda
18:59:40 <anteaya> asselin: I will make sure you get lots of help
18:59:40 <krtaylor> thanks everyone
18:59:46 <asselin> thanks
18:59:50 <anteaya> good meeting, krtaylor
19:00:00 <ctlaugh_> yes, thank you
19:00:08 <krtaylor> see you all next week!
19:00:15 <krtaylor> #endmeeting