18:01:06 <anteaya> #startmeeting third-party
18:01:08 <openstack> Meeting started Mon Jun  9 18:01:06 2014 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:01:09 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:01:11 <openstack> The meeting name has been set to 'third_party'
18:01:24 <anteaya> who is here for the third-party meeting?
18:01:24 <SergeyLukjanov> o/
18:01:29 <ArxCruz> o/
18:01:43 <anteaya> that's a start
18:01:47 <anteaya> thanks for being here
18:01:58 <anteaya> #link https://wiki.openstack.org/wiki/Meetings/ThirdParty#Agenda_for_next_meeting
18:02:04 <anteaya> here is our agenda for today
18:02:19 <anteaya> #topic Welcome & Reminder of OpenStack Mission
18:02:25 <anteaya> so welcome
18:02:29 <anteaya> thanks for being here
18:02:42 <anteaya> #link 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:02:55 <anteaya> the openstack misison, in case you forgot or are new
18:03:09 <anteaya> #topic  Review of previous week's open action items
18:03:24 <anteaya> we had no open action items for last week
18:03:26 <anteaya> onward
18:03:39 <anteaya> #topic Announcements
18:04:08 <sweston> o/
18:04:21 <anteaya> third party documentation is here: Documentation:  #link http://ci.openstack.org/third_party.html
18:04:44 <anteaya> and we have a new section on getting non-voting systems voting
18:05:04 <mestery> o/
18:05:25 <anteaya> this will become a staple as new folks integrate with our communication system #info How To Ask Questions The Smart Way: http://www.catb.org/esr/faqs/smart-questions.html
18:06:01 <anteaya> and I am working though items on this etherpad: #link https://etherpad.openstack.org/p/juno-infra-improving-3rd-party-testing
18:06:12 <anteaya> and one of them is about name formating
18:06:40 <anteaya> I am working on standardizing name formatting for third party accounts: #link https://etherpad.openstack.org/p/automated-gerrit-account-naming-format
18:07:09 <anteaya> currently the format guidelines are as follows:
18:07:12 <anteaya> Ci if it votes or ever might in the future, Bot if it will never ever vote
18:07:13 <anteaya> Format:
18:07:15 <anteaya> username --> lowercase, hyphens between words, matches Full Name, -ci or -bot at the end
18:07:17 <anteaya> Full Name --> capitalize, upper(minimal) and lowercase, matches username, CI, -CI, -ci or Bot, -Bot, -bot at the end
18:07:19 <anteaya> {company name}-{thing it is testing}-{ci|bot}
18:07:21 <anteaya> remove test, testing, jenkins, openstack, tempest, user from the names
18:07:41 <anteaya> we have an infra meeting tomorrow and I will get more feedback on these guidelines and then they will be published
18:07:52 <anteaya> but that is where they are right now, in draft form
18:08:04 <anteaya> any other announcements?
18:08:24 <anteaya> moving on
18:08:29 <anteaya> #topic OpenStack Program items
18:08:43 <anteaya> anyone have any items from an openstack program?
18:08:55 <anteaya> mestery: anything from neutron this week?
18:09:24 <anteaya> I'll go with no
18:09:27 <anteaya> and move on
18:09:31 <anteaya> #topic  Deadlines & Deprecations
18:09:58 <anteaya> any deadlines or code heading for deprecation that we need to talk about this week?
18:10:24 <anteaya> okay
18:10:30 <anteaya> #topic Highlighting a Program or Gerrit Account
18:10:49 <anteaya> any third party accounts want or need to discuss anything about their account?
18:11:04 <sweston> yes
18:11:14 <anteaya> sweston, you have the floor
18:11:30 <sweston> what is the recommendation for multiple ci accounts in an organization?
18:11:43 <anteaya> that depends on what you are doing
18:12:04 <anteaya> vmware has one account, minesweeper that does both nova and neutron and it seems to work for them
18:12:08 <anteaya> salv-orlando: ping
18:12:24 <sweston> ok
18:12:37 <anteaya> it depends on how you want it to return results and how many projects you intend on testing
18:13:09 <sweston> maybe we can discuss more later
18:13:10 <anteaya> from a third-party account admin perspective, I would love it if all companies had one per company and then I knew who to ping for each company
18:13:31 <anteaya> but that doesn't tend to be how companies want to do it from their side
18:13:42 <anteaya> well we have 47 minutes left in the meeting
18:13:45 <sweston> that would be optimal
18:13:46 <ArxCruz> IBM have the PowerKVM account who test openstack in general running in power, as well as another who test only openstack in db2
18:13:58 <anteaya> and hopefully others will read the logs, so it would be good to discuss now
18:14:04 <sweston> ok, then we can discuss now, yay!!
18:14:10 <anteaya> yes
18:14:29 <anteaya> sweston: you are brocade, if I remember correctly
18:14:30 <anteaya> yes?
18:14:33 <sweston> so, we have multiple projects we would like to upstream
18:14:38 <sweston> yes
18:14:41 <anteaya> great
18:14:51 <anteaya> I remember talking to a brocade person at the summit
18:15:14 <anteaya> and told them that for my purposes, it would be optimal to have you, sweston, as point person for all the brocade accounts
18:15:19 <sweston> yup, I wasn't able to make it because of another project
18:15:40 <anteaya> and then you and I can talk and you can ensure internally brocade is doing "the right thing"
18:15:46 <anteaya> understood
18:15:48 <mestery> annegentle_: Nothing from Neutron (apologies for the delayed reply)
18:15:53 <anteaya> but that conversation happened
18:16:09 <anteaya> mestery: np, figured you had shown up and gotten pulled off on something else
18:16:42 <sweston> are there other companies contributing multiple projects with only one gerrit account?
18:16:56 <anteaya> sweston: so yeah, if you are able to be brocade third-party account manager, that would be way easier for me, even if you do keep all three brocade accounts
18:17:07 <anteaya> sweston: ahhhh
18:17:10 * anteaya looks at list
18:17:13 <sweston> hehe
18:17:21 <anteaya> smokestack
18:17:22 <sweston> Yes, I will be third-party account manager
18:17:26 <sweston> for Brocade
18:17:28 <ArxCruz> sweston: yes, PowerKVM is testing multiple projects
18:17:29 <anteaya> yay!!
18:17:32 <anteaya> thanks so much
18:17:45 <anteaya> smokestack tests many different projects
18:18:00 <sweston> :-)
18:18:20 <sweston> so what is the difference
18:18:31 <sweston> between running smokestack and setting up your own ci
18:18:46 <anteaya> smokestack is dprince's ci
18:18:57 <anteaya> he decides what smokestack tests
18:19:05 <anteaya> the code is up somewhere
18:19:08 * anteaya looks
18:19:18 <sweston> so for a reference implementation
18:19:25 <sweston> that might be a place to start?
18:19:33 <sweston> or even recommend
18:20:32 <anteaya> sweston: it is used on our pages as an example of how to set up a third party ci
18:20:59 <sweston> understood
18:21:03 <anteaya> but I would suggest a workflow more along the lines of what we are currently using in openstack-infra now
18:21:19 <anteaya> are you testing propriatry code or just hardware?
18:21:46 <anteaya> or should I say propriatry hardware or just code
18:22:06 <dprince> sweston: probably not recommended unless you like Ruby, it evolved into what was the first example of 3rd party testing in OpenStack and there are now many other examples of how to do that too
18:22:06 <sweston> ok, just want to verify that I am on the right track, am using the infra manifests
18:22:33 <anteaya> sweston: yes that is probably a good place to start
18:22:40 <anteaya> dprince: everywhere, all the time :D
18:22:42 <sweston> dprince: understood, I do like ruby
18:23:23 <sweston> so moving on to next question
18:23:23 <ArxCruz> sweston: Our CI is very based on openstack ci, even the puppet files we use are based on openstack ones
18:23:33 <ArxCruz> I can give you some tips
18:23:51 <sweston> ArxCruz: ok, thank you :-)
18:23:53 <ArxCruz> right now we have zuul, nodepool, jenkins, and even puppetboard running in our infra
18:24:06 <ArxCruz> just like upstream
18:24:26 <ArxCruz> our plans is to increase this to use logstash and other cool stuff
18:24:27 <sweston> there are two ways to configure the communication between Gerrit and Jenkins, correct?
18:25:17 <sweston> the jenkins gerrit trigger, and zuul
18:25:22 <ArxCruz> sweston: I use what upstream use, in this case zuul - gearman - jenkins
18:25:29 <sweston> are those two methods exclusive?
18:25:59 <sweston> ArxCruz: ok, gotcha.
18:26:24 <ArxCruz> jenkins have a gearman-job-plugin who connects to gearman
18:26:47 <ArxCruz> so the communication is jenkins <-> gearman-job-plugin <-> gearman <-> zuul
18:26:56 <ArxCruz> and zuul from and to gerrit
18:27:32 <bookwar> sweston: there are certain limitations when using jenkins with gerrit trigger plugin directly. No support for recheck for example
18:27:42 <bookwar> zuul is more powerfull
18:28:04 <sweston> bookwar: thank you :-) was just going to ask about the differences
18:29:02 <bookwar> sweston: our ci is rather small thus we use simplified setup, but we already plan to move to zuul in next month or so because of better scheduling and features
18:29:18 <sweston> anteaya: no proprietary hardware or code, AFAIK but I will need to check on a few things before making that official
18:29:47 <anteaya> sweston: if you have no proprietary hardware or code, why do you want to do third-party testing?
18:29:56 <anteaya> sweston: what would you be testing?
18:30:04 <sweston> well, we have the vyatta plugin
18:30:13 <anteaya> sweston: what is that?
18:30:29 <sweston> and we have adx
18:30:58 <sweston> vyatta is a virtual router, and adx virtual switch
18:31:12 <anteaya> and brocade owns those?
18:31:22 <sweston> excuse me, adx is a hardware switch
18:31:41 <sweston> yes, Brocade owns them
18:31:42 <anteaya> is adx an opensource switch?
18:32:07 <sweston> no
18:32:20 <anteaya> okay so you have propriatary hardware, adx
18:32:35 <anteaya> are you going to opensource the code for vyatta?
18:32:45 <sweston> ok
18:33:00 <anteaya> so you have propriatary code and hardware both
18:33:07 <sweston> anteaya: I need to check on Vyatta, there are licenses
18:33:17 <anteaya> so you are opensourcing the hooks to use the code
18:33:21 <sweston> yes
18:33:38 <anteaya> since it is the hooks that will be opensource and you intend to merge them into openstack
18:33:40 <anteaya> right?
18:33:46 <sweston> yes
18:33:49 <anteaya> great
18:34:05 <sweston> sorry ... I know that was a long walk for a short drink of water :-)
18:34:16 <anteaya> so you use our test suite to test your hooks with the propriatary stuff
18:34:41 <anteaya> this is the third-party space, every conversation is a long walk for a short drink of water
18:34:54 <sweston> hehe
18:34:58 <sweston> need a workflow
18:35:03 <anteaya> right
18:35:12 <anteaya> talk with ArxCruz and bookwar
18:35:35 <anteaya> get a jenkins listening to the gerrit stream with a gerrit plugin to start
18:35:35 <sweston> yes, own test suites
18:35:59 <anteaya> comment on the sandbox repo, test > make mistakes > ask questions
18:36:18 <sweston> already have done that ...
18:36:20 <anteaya> once your jenkins is working with the gerrit plugin, move to zuul and friends
18:36:24 <anteaya> great
18:36:33 <sweston> now doing ci "for realsies"
18:36:47 <anteaya> do you have zuul set up?
18:36:48 <sweston> but want to get the implementation right the first time
18:36:57 <anteaya> stable logs, recheck capability
18:37:04 <sweston> I have zuul bootstrapped with puppet
18:37:10 <anteaya> yes, that is what the sandbox is for
18:37:19 <sweston> haven't started on configuring it yet
18:37:23 <anteaya> let's see some comments on sandbox patches this week
18:37:33 <anteaya> okay, so do that and ask questions in infra
18:37:33 <ArxCruz> zuul is easy to configure to not report
18:37:54 <anteaya> make sure you are only commenting once per patchset
18:38:04 <anteaya> get rid of the comment "staring jobs"
18:38:08 <anteaya> don't post that
18:38:21 <sweston> ok
18:38:37 <anteaya> the post on the sandbox, ping me and we will go over it
18:38:45 <anteaya> ping ArxCruz and bookwar ask questions
18:38:51 <ArxCruz> =]
18:39:02 <anteaya> we will let you know if you are ready to comment on projects
18:39:03 <roeyc> sweston, our setup includes Zuul and Jenkins and using JJB, I can also assist you
18:39:09 <sweston> ok, need to set some realistic expectations, for us and others
18:39:12 <anteaya> you won't be to start, start on the sandbox
18:39:17 <anteaya> sweston: yes
18:39:24 <sweston> roeyc: ok
18:39:25 <anteaya> great, thanks roeyc
18:39:32 <anteaya> roeyc: which system is yours?
18:39:51 <sweston> how much time should I give as an eta for when we can vote?
18:39:57 <anteaya> none
18:40:10 <anteaya> you don't know yet, since you have nothing to show us on the sandbox repo
18:40:12 <roeyc> Mellanox
18:40:28 <anteaya> I haven't seen the state of your logs, links, comment message, nothing
18:40:39 <sweston> ok
18:40:57 <anteaya> get me that and we can start setting timelines, in collaboration with the ptls of the projects you want to test
18:41:05 <anteaya> sweston: tesing more than neutron?
18:41:09 <anteaya> roeyc: awesome
18:41:16 <sweston> not right now, no
18:41:42 <sweston> awesome, thank you, everyone for the information and helpful advice :-)
18:41:45 <bookwar> roeyc: hi, from Mirantis Fuel project, by the way :)
18:41:52 <anteaya> sweston: okay so once you have some testing to show me on sandbox, we will chat with mestery to see what he wants to see
18:42:07 <roeyc> bookwar: Hi :-)
18:42:13 <anteaya> sweston: thanks for using this space the way I had hoped it would be used
18:42:31 <anteaya> roeyc: I'm going to have to stick CI on the end of your name, Mellanox CI
18:42:43 <anteaya> roeyc: to fit with the new naming format
18:42:45 <sweston> anteaya: Yay!! You're welcome :-)
18:42:49 <anteaya> sweston: :D
18:43:06 <anteaya> so anymore gerrit account discussion?
18:43:19 <luqas> anteaya: fast status
18:43:22 <sweston> not from me, all questions answered
18:43:25 <luqas> sorry I was late
18:43:25 <roeyc> anteaya: Cool
18:43:32 <anteaya> luqas: np, let's hear from you
18:43:39 <anteaya> roeyc: thanks
18:43:43 <luqas> well we fix our CI
18:43:46 <anteaya> sweston: great
18:43:53 <luqas> it s still based on gerrit plugin
18:43:53 <anteaya> luqas: glad to hear those words
18:44:01 <anteaya> can you share what was wrong?
18:44:06 <luqas> but tests neutron master correctly
18:44:09 <anteaya> it might help someone else
18:44:27 <luqas> our plugin wasn't stacking correctly with the master branch of neutron
18:44:29 <luqas> on devstack
18:44:41 <anteaya> did you find out why?
18:45:05 <luqas> mmm my colleague tomoe was with that...
18:45:10 <anteaya> luqas is midokura
18:45:12 <luqas> guess several things
18:45:23 <anteaya> go ahead
18:45:47 <luqas> well basically we are reporting legitimate failures
18:46:08 <luqas> we still need to add some logs, and more tests of the suite
18:46:30 <luqas> and the recheck capability
18:46:40 <luqas> but I guess this is zuul
18:46:53 <luqas> which will be our next step
18:46:58 <anteaya> okay great
18:47:08 <anteaya> good work and thanks for the update on your status
18:47:22 <luqas> anteaya: you're welcome!
18:47:26 <anteaya> :D
18:47:30 <anteaya> anyone else?
18:47:53 <anteaya> I'm going to change the topic to open discussion for the rest of the meeting
18:48:06 <anteaya> #topic Open Discussion
18:48:22 <anteaya> so now we can discuss anything related to third-party
18:48:33 <anteaya> does anyone have anything that want to talk about?
18:48:44 <bookwar> anteaya: are there any updates about account wiki pages?
18:48:44 <sweston> yup
18:49:12 <anteaya> bookwar: this week I am going to create two seed pages, one for gerrit accounts and one for openstack programs
18:49:36 <sweston> when is the latest that our system can be up and still be able to submit code to be included in Juno
18:49:41 <anteaya> if they pass review at tomorrow's infra meeting, I do believe I will be given permission to start informing people
18:49:52 <bookwar> anteaya: cool, thanks
18:50:04 <anteaya> I think I would like to start populating a few in coordination with others until we have a few good examples
18:50:10 <anteaya> and then announce to others
18:50:34 <anteaya> bookwar: if you would like to be one of the examples that is great, I will ping you after tomorrow's meeting and we can talk
18:50:38 <anteaya> bookwar: is that fair?
18:50:42 <bookwar> anteaya: yes, i'd be glad to help, so ping me if needed
18:50:49 <anteaya> bookwar: great thanks
18:51:01 <anteaya> sweston: that is a question that is project specific
18:51:19 <anteaya> so if you are gearing this question for neutron, we need to hear from mestery
18:51:24 <anteaya> if he is still here
18:51:30 <sweston> anteaya: ok
18:51:42 <mestery> anteaya: Sorry, I am back now, juggling a few too many things, apologies :(
18:51:45 <anteaya> if not, the neutron meeting is in an hour or two, get on the agenda
18:51:55 <mestery> What can I help with?
18:51:59 <sweston> I don't need an answer right now, but will need to have the discussion soon
18:52:05 <anteaya> great, so what are sweston's deadlines fo third party if he wants code in juno?
18:52:35 <mestery> We just require the system to be voting correctly on the driver/plugin before it can be merged.
18:52:39 <mestery> That's what we've done so far.
18:52:55 <anteaya> mestery: what is a realistic timeframe for includsion in juno
18:53:14 <anteaya> you want them commenting for 2-3 weeks before they are voting, correct?
18:53:14 <mestery> Juno-2 would be the place to shoot for, after that FPF happens very fast.
18:53:18 <sweston> mestery: optimally how much time would you like for review
18:53:20 <anteaya> right
18:53:20 <mestery> Correct
18:53:24 <mestery> 2-3 weeks.
18:53:31 <mestery> So, Juno-2 would be the ideal deadline
18:53:49 <anteaya> so ensure your system is stable by mid j-2, to enable you to be voting by j-2
18:53:56 <anteaya> and j-1 is in 3 days
18:54:05 <mestery> :)
18:54:11 <anteaya> so you have about 3 weeks to get stable, sweston
18:54:23 <anteaya> so that is your system up and running, stable
18:54:30 <sweston> anteaya: ok
18:54:33 <anteaya> stable logs, comments, gerrit history
18:54:48 <anteaya> so you need zuul up and running by the end of this week
18:55:06 <anteaya> or a running zuul for every gerrit account
18:55:27 <sweston> anteaya: ok
18:55:36 <anteaya> that gives you two weeks to figure out how to keep it running while figuring out the rest
18:56:11 <sweston> anteaya:  gotcha, thank you so much for the wonderful guidance and advice
18:56:23 <anteaya> sweston: you ask good questions?
18:56:33 <anteaya> s/?/!
18:56:41 <anteaya> anything else for open discussion?
18:56:42 <sweston> :-D
18:56:44 <luqas> anteaya: so without zuul CI is not valid?
18:56:59 <anteaya> luqas: that is an incorrect statement
18:57:17 <anteaya> as long as the tests are running and we have logs the CI is valid
18:57:18 <luqas> anteaya: I mean, without recheck capability
18:57:32 <anteaya> having recheck is one of our requirements
18:57:45 <luqas> I know
18:57:49 <anteaya> so I would aim for having recheck ability
18:58:19 <luqas> anteaya: ok, just to be sure
18:58:26 <anteaya> we are in j-1
18:58:42 <anteaya> so the conversation in j-1 is to aim for it and ask questions if you are having problems
18:59:05 <anteaya> luqas: make sense?
18:59:17 <luqas> anteaya: completely
18:59:20 <anteaya> thanks
18:59:27 <anteaya> so it looks like we are done
18:59:32 <roeyc> anteaya: Can you please point me to where I can create a wiki page for our CI ?
18:59:48 <sweston> thanks again, everyone for your time
18:59:49 <anteaya> roeyc: can I table that until next week?
19:00:04 <anteaya> roeyc: I will have a really good answer next week for that question
19:00:09 <anteaya> and a poor answer today
19:00:11 <roeyc> ok
19:00:13 <anteaya> thanks
19:00:17 <anteaya> we are out of time
19:00:26 <anteaya> thanks everyone for a great meeting
19:00:30 <anteaya> #endmeeting