18:00:16 <anteaya> #startmeeting third-party
18:00:17 <openstack> Meeting started Mon Jun  2 18:00:16 2014 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.
18:00:18 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
18:00:20 <openstack> The meeting name has been set to 'third_party'
18:00:38 <anteaya> anyone here for the third-party meeting?
18:00:42 <mestery> o/
18:00:52 <anteaya> hmmm
18:00:58 <bruff> o/
18:01:00 <anteaya> going  to be a short meeting then
18:01:10 <david-lyle> o/
18:01:29 <anteaya> great, thanks for being here
18:01:30 <krtaylor> o/
18:01:35 <anteaya> #link https://wiki.openstack.org/wiki/Meetings/ThirdParty#Agenda_for_next_meeting
18:01:40 <anteaya> our agenda for today
18:01:56 <anteaya> #topic Welcome & Reminder of OpenStack Mission
18:02:19 <anteaya> welcome to everyone who is here
18:02:31 <anteaya> for anyone who is new here is the openstack mission
18:02:33 <linggao> o/
18:02:38 <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:54 <anteaya> #topic Review of previous week's open action items
18:03:12 <anteaya> #info Anita (anteaya) to polish the Purposes/Goals section from the etherpad
18:03:23 <anteaya> #link https://etherpad.openstack.org/p/polished-third-party-goals
18:03:31 <SergeyLukjanov> o/
18:03:36 * SergeyLukjanov lurking
18:03:38 <bookwar> hi, all
18:03:41 <anteaya> so I have taken a bit of time on our goals for the use of this space
18:03:55 <anteaya> please take a look at the etherpad and share your thoughts
18:04:20 <anteaya> do they goals listed adequately descrive your motivations for attending  these meetings?
18:04:53 <anteaya> don't forget to sign your name to the etherpad
18:05:07 <anteaya> Longgeek: are you here?
18:05:25 <Longgeek> anteaya: yes.
18:05:51 <anteaya> Longgeek: good please look at the linked etherpad with us
18:06:03 <anteaya> any comments?
18:06:10 <Longgeek> anteaya: ok
18:06:32 <anteaya> anyone with any thoughts?
18:07:04 <bookwar> anteaya: general idea is clear, i think
18:07:05 <anteaya> okay, I will acknowledge no complaints and list them on the meeting page as our goals
18:07:06 <krtaylor> LGTM, we can morph over time as everyone gets up to speed
18:07:10 <anteaya> bookwar: thanks
18:07:15 <anteaya> krtaylor: agreed
18:07:46 <anteaya> so I will add them to the meeting page and when someone feels they need to be reviewed please add an item to the agenda
18:08:01 <anteaya> #topic Announcements
18:08:15 <anteaya> bookwar: you added the first item
18:08:57 <bruff> there is probably some common questions implementors have for the different groups with differing answers by group, like sizing CI infrastructure which for some contributions would differ from say nova to cinder.
18:08:57 <trinaths> HI
18:09:18 <anteaya> bookwar: do you have anything you want to say on the item you added to the agenda
18:09:20 <bookwar> anteaya: actually i just read it on the mailing list and decided that it's worth mentioning here
18:09:31 <anteaya> bookwar: okay, what did you want to mention?
18:10:03 <bookwar> #info http://www.mail-archive.com/openstack-dev@lists.openstack.org/msg25513.html  there will be Meet Up for Infra with possible Third-Party participants
18:10:12 <anteaya> sorry no
18:10:15 <anteaya> that is incorrect
18:10:19 <bookwar> ok )
18:10:30 <bookwar> so then it's my question
18:10:37 <trinaths> anteaya: I have got a new hosting account for CI logs. Do I need to restore old CI logs, or start with new logs.
18:10:37 <anteaya> there will be a meetup of infra/qa folks in which various items will be discussed
18:10:46 <anteaya> including third party matters
18:10:52 <bookwar> can third-party members participate?
18:10:59 <anteaya> trinaths: we have an agenda: https://wiki.openstack.org/wiki/Meetings/ThirdParty#Agenda_for_next_meeting
18:11:04 <anteaya> please follow along
18:11:14 <anteaya> bookwar: I was expecting that question
18:11:38 <anteaya> this meeting is for people who have a commitment to becomeing core contributors to infra and/or qa
18:12:18 <anteaya> if anyone is willing to commit to learning and reliably performing at least 30 reviews/per month to start (that is not enough for core)
18:12:33 <anteaya> in any of the infra/qa repos that person can request to attend
18:12:58 <anteaya> if you are expecting this will be a place to ask questions to get your system running, the answer is no, this is not that place
18:13:12 <anteaya> actually this meeting is that place
18:13:26 <anteaya> once we get folks trusting the agenda format and using it
18:13:30 <anteaya> bookwar: make sense?
18:13:41 <bookwar> anteaya: yes, thanks for clarifying
18:13:44 <anteaya> great
18:13:59 <anteaya> #link Documentation: http://ci.openstack.org/third_party.html
18:14:09 <anteaya> please read that, there are some changes this week
18:14:18 <anteaya> be sure to share that around
18:14:31 <anteaya> also
18:14:35 <anteaya> #link How To Ask Questions The Smart Way: http://www.catb.org/esr/faqs/smart-questions.html
18:14:41 <anteaya> this is an invaluable resource
18:14:51 <anteaya> and one that i will be pointing to frequently
18:15:04 <anteaya> please read it if you haven't and share with others
18:15:10 <anteaya> any other announcements?
18:15:29 <anteaya> #topic OpenStack Program items
18:15:37 <anteaya> david-lyle: you're up
18:15:48 <david-lyle> thank anteaya
18:16:24 <david-lyle> So the main question I have is what are the requirements for third parties to provide infrastructure to test against outside of CI
18:17:10 <anteaya> david-lyle: are any of your concerns answered here? http://ci.openstack.org/third_party.html#requirements
18:17:11 <david-lyle> in Horizon we get numerous patches that want to target say a 3rd party device in neutron, but have no means to actually exercise the code other than through unit tests
18:17:29 <anteaya> can you give me a forinstance?
18:17:35 <anteaya> like a url for a patch?
18:18:36 <david-lyle> this outdated, but Horizon in the H cycle added support for managing a cisco router, unfortunately there is not test environment to verify the running code
18:18:46 <anteaya> hmmmm
18:18:49 <bookwar> "support recheck" is not an easy feature to implement
18:18:57 <david-lyle> so we have fair chunk of code that we can't validate
18:18:59 <anteaya> bookwar: this is david-lyle's time
18:19:11 <anteaya> david-lyle: yes I am beginning to see
18:19:36 <anteaya> I question that horizon should add support for a propietary service in the first place
18:19:45 <david-lyle> there are requests for more code along those lines, but without a requirement for an environment where we can validate, I am very uneasy to add support
18:19:49 <david-lyle> anteaya: that too
18:19:51 <krtaylor> david-lyle, is this for supporting that third party functionality? else it shouldn't be part of horizon
18:20:43 <krtaylor> david-lyle, that would be up to the third party implementors to test and report, horizon will have to come up with how it will require testing on this code
18:20:51 <anteaya> david-lyle: I'm feeling this question needs to find it's way onto the tc agenda
18:20:52 <david-lyle> so several services expose driver support and include code for it, correct?  then isn't it reasonable to support those same drivers in Horizon
18:21:01 <krtaylor> similar to what Nova has done for instance
18:21:15 <anteaya> david-lyle: that is a question I can't answer
18:21:19 <anteaya> since I have no authority
18:21:25 <anteaya> but it is a good question
18:21:29 <krtaylor> it is
18:21:33 <HenryG> davidlenwell: there is a cisco CI for neutron. Maybe a horizon CI can be run against the same lab config. I will ask them.
18:21:44 <anteaya> HenryG: ?
18:21:59 <krtaylor> but that is one specific example, not general case
18:22:28 <david-lyle> Ideally, I want to be able to try the code on a live environment before merging
18:22:33 <anteaya> david-lyle: I enourage the process for discussing it with the tc, to discuss the scope of horizon regarding third-party
18:23:19 <anteaya> david-lyle: if the tc feels horizon should be including support for third-party services then the testing conversation can come from that
18:23:35 <anteaya> and yes, I agree you should be able to test what you are including in master
18:23:39 <david-lyle> anteaya: I'm heading that way.  I just wanted to raise the issue that CI support isn't necessarily enough
18:24:09 <anteaya> david-lyle: yes we have to have the understanding of how it affects other projects
18:24:24 <anteaya> and I am glad I have a better understanding of how it affects horizon now
18:24:40 <david-lyle> my recommendation for Horizon at the summit was that there needed to be an environment we could exercise the Horizon code against before integrating it
18:24:51 <anteaya> I like that
18:25:06 <anteaya> after the tc chat put an item on the infra meeting agenda
18:25:09 <david-lyle> just wanted to make sure that wasn't completely against the other assorted edicts in openstack
18:25:15 <anteaya> so we can discuss how to create that support
18:25:17 <david-lyle> anteaya: will do
18:25:21 * anteaya nods
18:25:24 <anteaya> thanks david-lyle
18:25:27 <david-lyle> and thanks for the time
18:25:31 <anteaya> np
18:25:43 <anteaya> next topic
18:25:49 <anteaya> #topic Deadlines & Deprecations
18:26:02 <anteaya> anyone have any deadlines or deprecations they want to announce?
18:26:20 <anteaya> no?
18:26:22 <anteaya> okay
18:26:27 <anteaya> #topic Highlighting a Program or Gerrit Account
18:26:44 <anteaya> okay today we are going to look at two maintainers
18:26:52 <trinaths> Hi, i'm there with freescale-ci
18:26:57 <anteaya> Longgeek: who mantains thstack-ci
18:26:59 <anteaya> and trinaths
18:27:00 <Longgeek> yes
18:27:05 <anteaya> great
18:27:07 <trinaths> Longgeek: Hi
18:27:18 <Longgeek> trinaths: hi
18:27:25 <anteaya> so some of the things you are doing well is you are both on irc and you are talking in channels which is good
18:27:52 <Longgeek> anteaya: ok
18:27:59 <trinaths> anteaya: :-)
18:28:02 <anteaya> and I bring you to the attention of others so that as I address some of your concerns, and mine that others can read the logs and learn
18:28:07 <anteaya> so for starters
18:28:19 <Longgeek> About our account have any questions?
18:28:27 <anteaya> Longgeek: I'm speaking
18:28:36 <Longgeek> ok
18:28:52 <anteaya> everyone knows the logs are here: #link http://eavesdrop.openstack.org/
18:28:55 <anteaya> correct
18:29:02 <trinaths> yes
18:29:20 <anteaya> and everyone reads the meeting logs and -infra and -qa and the project you are testing on a daily basis, correct?
18:29:22 <Longgeek> yes
18:29:26 <anteaya> great
18:29:42 <anteaya> so one of the things I want to start with
18:30:00 <anteaya> when something goes wrong, don't start by assuming that our system is the problem
18:30:14 <anteaya> which is covered in how to ask smart questions, linked above
18:30:17 <anteaya> as an example
18:30:50 <Longgeek> This is, I need to learn.
18:30:51 <anteaya> anyone who wants to look at the infra logs for the weekend will see Longgeek spent a considerable about of time trying to get a patch in dealing with min.js
18:31:00 <anteaya> after many hours and much time
18:31:13 <anteaya> he found out his https proxy wasn't working properly
18:31:14 <Longgeek> anteaya, :)
18:31:39 <anteaya> he found that out by pasting the output of the error for jheseth to view
18:31:53 <anteaya> and jheseth gave him a suggestion
18:32:03 <Longgeek> yes, The https proxy problem
18:32:11 <anteaya> which helped him to conclude that his error lay within his own environment
18:32:13 <anteaya> so
18:32:17 <anteaya> let's help each other
18:32:37 <anteaya> if you have a problem, first evaluate your local environment
18:32:44 <anteaya> Longgeek you know trinaths now
18:32:44 <Longgeek> yes.
18:32:51 <anteaya> so you can help each other
18:32:59 <anteaya> paste, using paste.openstack.org
18:33:10 <anteaya> the command and output and share it with each other
18:33:16 <anteaya> bruff: you can help in this too
18:33:19 <Longgeek> ok, paste.openstack.org.
18:33:19 <trinaths> anteaya: yes..
18:33:47 <trinaths> anteaya: Longgeek, helped me with Zuul troubleshooting
18:33:47 <anteaya> if you all have the same output then it isn't a local issue, and then you can ask in -infra what someone can see when the view the paste
18:34:12 <anteaya> please don't go straight to filing bugs and offering patches, that wastes our time in -infra
18:34:16 <anteaya> make sense?
18:34:24 <anteaya> bruff: you can help here, yes?
18:34:40 <Longgeek> OK, I understand.
18:34:46 <anteaya> great
18:34:56 <anteaya> now Longgeek
18:35:08 <anteaya> there are some questions about your account
18:35:27 <anteaya> the people involved with the projects you are testing don't know what you are doing
18:35:47 <anteaya> so it is helpful if, before you test a project, you talk to the people involved with the project
18:35:57 <anteaya> and if you don't know who they are, ask
18:36:01 <Longgeek> I test my present work system stability.
18:36:27 <Longgeek> ok.
18:36:46 <anteaya> here is the list of openstack projects and their governing programs: http://git.openstack.org/cgit/openstack/governance/tree/reference/programs.yaml
18:36:52 <anteaya> please refer to that list
18:37:20 <Longgeek> I'll look at it
18:37:29 <anteaya> now, right now Longgeek's system is posting 2 comments per patchset and third-party ci is only allowed one comment per patchset
18:37:43 <anteaya> anyone able to help Longgeek fix his system?
18:38:03 <[1]trinaths> Just got diconnected..
18:38:22 <anteaya> is anyone able to help Longgeek?
18:38:53 <Longgeek> zuul event？
18:39:11 <anteaya> you can't have your systems post the comment "starting tests"
18:39:24 <anteaya> can anyone help Longgeek turn that comment off?
18:39:45 <Longgeek> Like this? Starting gate jobs. http://status.openstack.org/zuul/
18:39:58 <anteaya> right you can't have that comment
18:40:04 <anteaya> that is noise
18:40:20 <anteaya> third-party ci systems can't post that comment
18:40:32 <anteaya> okay let's move to trinaths, who has some issues
18:40:35 <Longgeek> Well, I'll try to locate it, and close
18:40:41 <anteaya> he is having difficulty will logs
18:41:07 <anteaya> his first server was hacked and he has now moved to a public server which gives a malware warning
18:41:30 <trinaths> anteaya: I may leave the chat at any time.. Since, we are experiencing a cyclone here and can be a power shutdown to the colony,..
18:41:30 <anteaya> anyone have any suggestions for trinaths and securely serving his logs?
18:41:40 <anteaya> trinaths: okay you can read the logs
18:41:45 <trinaths> anteaya: I went for godaddy hosting
18:41:49 <trinaths> now
18:42:03 <anteaya> does anyone have any suggestions for helping trinaths?
18:42:09 <trinaths> the logs are available at fslopenstackci.com
18:42:26 <mestery> I've verifed the new log location for trinaths doesn't trigger Cisco WSA alarms anymore.
18:42:28 <anteaya> I'll let you know now, these meetings are going to be painfully slow if folks are not willing to help each other
18:42:35 <anteaya> mestery: great thank you
18:42:50 <anteaya> trinaths: good work, we may have solved that issue
18:42:53 <mestery> anteaya: I think trinaths issue is solved now regarding logging from my perspective.
18:43:00 <anteaya> mestery: great thanks
18:43:05 <mestery> anteaya: thank you too!
18:43:13 <trinaths> mestery: thanks a lot..
18:43:17 <anteaya> those were the main issues I had
18:43:27 <anteaya> please read how to ask smart questions
18:43:35 <anteaya> there is a lot of good information in there
18:43:47 <anteaya> Longgeek trinaths anything else from you?
18:44:02 <trinaths> mestery: were there any other issues I need to address regarding CI?
18:44:12 <mestery> trinaths: Not from my perspective, no.
18:44:34 <trinaths> mestery: okay.. thank you
18:44:38 <anteaya> okay going to move topics
18:44:44 <anteaya> #topic Open Discussion
18:44:52 <anteaya> anyone have anything for open discussion?
18:44:55 <Longgeek> anteaya: There is nothing for the time being! :)
18:45:12 <anteaya> Longgeek: okay thanks, we still need to talk before you turn your system back on
18:45:22 <trinaths> anteaya: doubt
18:45:48 <anteaya> trinaths: if that means you have a question, do ask your question
18:46:08 <trinaths> anteaya: Since, I moved to a new Log repository, do I need to hold the old logs present in my old server ?
18:46:25 <anteaya> you need the old logs present on your new server
18:46:48 <trinaths> anteaya: okay. thanks
18:46:49 <anteaya> logs from yesterday need to be accessed reliable and without triggering malware warnings
18:46:58 <anteaya> bookwar: did you have anything?
18:47:49 <anteaya> bruff: was there something you wanted to say?
18:48:07 <trinaths> anteaya: okay..
18:48:09 <bruff> No I did add to the etherpad
18:48:22 <anteaya> bruff: what etherpad?
18:49:15 <bruff> linked earlier in the meeting
18:49:20 <bruff> ..
18:49:27 <anteaya> #link https://etherpad.openstack.org/p/polished-third-party-goals
18:49:34 <anteaya> what do you want to know?
18:49:42 <anteaya> can you expand on what you are looking for?
18:50:02 <anteaya> I think the level of detail you are asking for is a little specific for overall goals
18:50:10 <anteaya> and is better as an agenda item
18:50:11 <bruff> suggestion to have projects document common information around what their CI 3rd party requirements are
18:50:32 <bruff> in addition to getting started process
18:50:36 <anteaya> third-party requirements are here: http://ci.openstack.org/third_party.html#requirements
18:50:50 <anteaya> bruff: what are you looking for in addition to that?
18:51:35 <bruff> It seems like the scale of testing will vary by the project you are committing to right?
18:51:41 <anteaya> exactly right
18:52:17 <anteaya> nova will be the project with the greatest throughput
18:52:31 <bruff> So in the getting started section might be useful for each project to provide some info around these differences, by project
18:52:31 <anteaya> bruff: what project do you want to test?
18:52:49 <bruff> For my specific group it is a cinder driver
18:52:56 <anteaya> bruff: that would be difficult since there are so many projects
18:53:16 <anteaya> okay, well I think time is better spent ensuring you have good contact with the cinder folks
18:53:25 <anteaya> do you spend time in their channel?
18:53:52 <anteaya> and read the cinder channel and meeting logs?
18:54:01 <bruff> Oh, yes but as you try to get your head around the 3rd party CI testing you go to those webpages  as well
18:54:23 <anteaya> yes, that is what they are meant for
18:54:36 <anteaya> what stage are you at right now, with setting up your testing?
18:54:50 <bruff> so providing some of this common documentation (or a set of common questions that the project leads could answer is useful
18:55:15 <anteaya> we are working on that, but since we are standardizing across all systems taht will take some time
18:55:22 <anteaya> right now, what do you need to know?
18:55:49 <bruff> no question currently
18:55:52 <bookwar> maybe certain stat about commits per day, it allows you to plan your infrastructure loads
18:56:07 <anteaya> okay, if you do have a question bruff do you feel you know where to ask it?
18:56:39 <bruff> Yes this type of thing, I'm trying to get through our GIT process so we can get going
18:56:58 <anteaya> bookwar: do you look at the graphs at the bottom of: http://status.openstack.org/zuul/
18:57:14 <anteaya> bruff: what do you mean get through your git process?
18:57:46 <bruff> OK good to know, but if you don't have a handle on CI stuff yet it isn't clear where you can get this info to start with.
18:58:13 <anteaya> bruff: right, which is why we set up these meetings
18:58:19 <anteaya> with open discussion
18:58:51 <bruff> Right?  So as a general question/info knowing about scaling this will be a common question and you might be able to provide pointers for this as the wiki develops
18:58:51 <anteaya> bookwar: https://github.com/openstack/openstack/graphs/commit-activity
18:59:06 <asselin_> bruff, for cinder ci setup, you can also chat int he #openstack-cinder channel. many of use are getting 3rd party ci setup
18:59:16 <anteaya> thanks asselin_
18:59:32 <bruff> Yes, agreed
18:59:48 <anteaya> we are at time
18:59:54 <anteaya> thanks for a great meeting everyone
18:59:57 <anteaya> read the logs
19:00:01 <anteaya> see you next week
19:00:05 <anteaya> #endmeeting