08:00:12 <anteaya> #startmeeting third-party
08:00:13 <openstack> Meeting started Tue Dec 23 08:00:12 2014 UTC and is due to finish in 60 minutes.  The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot.
08:00:14 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:16 <openstack> The meeting name has been set to 'third_party'
08:00:31 <anteaya> anyone here for the third-party meeting?
08:00:42 <nuritv> yes
08:00:48 <anteaya> nuritv: hello
08:00:50 <omrim_> Yes Hello
08:00:56 <nuritv> Hi Anteaya
08:01:03 <anteaya> hello omrim_
08:01:24 <anteaya> what shall we discuss today?
08:01:24 <omrim_> anteaya: Hi
08:02:01 <omrim_> What about the FAQ page? we should increase the information there
08:02:20 <anteaya> omrim_: lets have the url for that patch`
08:02:29 <anteaya> we can see how that is coming along
08:03:03 <omrim_> https://review.openstack.org/#/c/141817/
08:03:15 <anteaya> #link https://review.openstack.org/#/c/141817/
08:03:45 <anteaya> if you put the link command before it it will show up in the meeting minutes
08:03:59 <anteaya> omrim_: there are some -1's on it
08:04:14 <omrim_> anteaya: I know I will fix it
08:04:21 <anteaya> great
08:04:28 <anteaya> can you do so now?
08:04:51 <omrim_> anteaya: Sure
08:04:59 <anteaya> Jenkins is also failing, the docs are failing to build
08:05:09 <anteaya> have you looked at the logs to see why?
08:05:52 <omrim_> anteaya: Yes
08:06:01 <anteaya> great, what have you found?
08:06:45 <omrim_> anteaya: I got: "Definition list ends without a blank line; unexpected unindent"
08:07:00 <anteaya> do you know what that means?
08:08:13 <anteaya> here is the entire line
08:08:18 <anteaya> #info sphinx.errors.SphinxWarning: /home/jenkins/workspace/gate-ci-docs/doc/source/third_party.rst:338: WARNING: Definition list ends without a blank line; unexpected unindent.
08:08:36 <anteaya> so the third_party.rst:338 is important here
08:08:48 <anteaya> the third_party.rst is the file
08:08:50 <omrim_> anteaya: I assume that I did not put space in the end of the marked block
08:08:56 <anteaya> and the 338 is the line number
08:10:38 <anteaya> do you see both pleia2 and asselin have added comments to help you there
08:11:13 <omrim_> anteaya: Thanks
08:13:07 <anteaya> nuritv: were there other things to discuss while omrim_ offers a new patchset?
08:13:48 <nuritv> anteaya: not from me. we are keeping an eye on the changes in Neutron and start working no them
08:13:57 <anteaya> wonderful
08:13:59 <nuritv> *on
08:14:15 <anteaya> there are many changes in neutron, which ones are you tracking?
08:14:29 <nuritv> splitting the plugins and drivers
08:14:36 <anteaya> ah yes
08:14:47 <nuritv> we have quite a work to do there
08:14:59 <anteaya> splitting out code is work that is true
08:15:09 <nuritv> :)
08:15:25 <anteaya> have you worked through armax's instructions yet at least once to practice splitting out your code?
08:15:34 <nuritv> however, there is still a lot of "noise" in CI systems these days - so we also keep an eye on that
08:15:50 <anteaya> yes that is true
08:16:12 <nuritv> we've started doing so. we are looking at the ODL MD as an example
08:16:15 <anteaya> figuring out what to listen to and what to reduce takes work
08:16:23 <anteaya> MD?
08:16:29 <nuritv> mechanism Driver
08:16:32 <anteaya> ah
08:17:09 <nuritv> so since, most of blue prints were declined, we have time to the some infra work :)
08:17:21 <anteaya> okay well it costs nothing to run the commands to split out your code, and then you can test the result to see if you have all you need
08:17:34 <anteaya> well that is good then
08:17:39 <nuritv> yes. that's the plan
08:17:44 <anteaya> since the infra work is the basis for all else
08:17:54 <anteaya> hard for folks to see that sometimes
08:17:55 <nuritv> i agree.
08:18:12 <anteaya> but it is really important to being able to keep up with growth when it happens
08:18:59 <nuritv> BTW, i wanted to give a +1 for the do it yourself gerrit acoount
08:19:06 <anteaya> great
08:19:15 <anteaya> glad to have that feedback thank you
08:19:18 <nuritv> Murad from my team had done it and it was very easy
08:19:24 <anteaya> oh wonderful
08:19:47 <anteaya> thanks, that maybe the first feedback I have had on that, so that is helpful thank you
08:20:07 <anteaya> I'm glad it was straightforward
08:20:15 <nuritv> thank you :)
08:20:19 <anteaya> :D
08:20:42 <anteaya> many times we do things and never get any positive feedback
08:20:52 <anteaya> but we haven't had any complaints
08:21:03 <anteaya> and now some positive feedback so that it nice
08:21:27 <anteaya> thank you
08:21:50 <nuritv> np
08:22:00 <anteaya> nuritv: so most of north america is coming up to holidays
08:22:21 <nuritv> yes - i guess this is why it is so quiet
08:22:25 <anteaya> yes
08:22:36 <omrim_> anteaya: I have another issue
08:22:45 <anteaya> omrim_: go ahead
08:23:02 <jhesketh> o/ (sorry I'm late)
08:23:04 <omrim_> anteaya: But I am not complaining..:)
08:23:08 <anteaya> hi jhesketh
08:23:17 <anteaya> omrim_: I'm listening
08:23:42 <omrim_> anteaya: When I use try to install a new jenkins master I got the following error:
08:23:46 <omrim_> anteaya: When I use try to install a new jenkins master I got the following error:
08:23:52 <anteaya> jhesketh: not to worry we were just working on omrim_'s patch
08:24:01 <omrim_> anteaya: http://paste.openstack.org/show/154104/
08:25:03 <omrim_> anteaya: I think that This issue came after the changes in install_pupprt script
08:25:15 <anteaya> omrim_: ah I think this is an extension of the conversation we were having in -infra today
08:25:20 <omrim_> *puppet
08:25:41 <anteaya> jhesketh: omrim_ followed jay's blogpost and then was having this difficulty
08:26:28 <anteaya> well the error is saying that it is looking for a puppet.conf.erb file that it can't find
08:26:39 <anteaya> where is your puppet.conf.erb file located?
08:28:25 <anteaya> because it appears that your module/os_ext_testing/manifests/base.pp is telling it to look somewhere and it isn't there
08:28:52 <omrim_> It should be at: /root/config/modules/openstack_project/templates/puppet.conf.erb
08:28:53 <jhesketh> is this because the project_config is split out now?
08:29:07 <anteaya> and as fungi pointed out in the -infra channel today the os_ext_testing module is not one we support
08:29:13 <omrim_> And the install_puppet should create this file
08:29:30 <anteaya> jhesketh: not sure, that might be part of it, since jay created this module before the split
08:29:47 <jhesketh> yeah, I'm not familiar with Jay's setup
08:29:58 <anteaya> neither is fungi
08:30:13 <anteaya> so the suggestion was to move to using modules we do support
08:30:40 <anteaya> and I don't think jay is supporting his stuff right now either
08:31:10 <anteaya> he had said that he had placed warnings at the top of the blog posts saying this material is out of date and no longer supported
08:31:29 <anteaya> omrim_: do you see a statement at the top of the blog post saying the content is out of date?
08:31:31 <omrim_> anteaya: That's true
08:31:42 <omrim_> anteaya: Yes
08:31:57 <anteaya> well it is possible that what you are seeing is a consequence of the fact the material is out of date
08:31:58 <omrim_> anteaya: The point that I can find my own solution
08:32:17 <anteaya> well have you tried using any code from infra?
08:32:27 <omrim_> anteaya: But I think that we should define a convention to prevent such an independent solutions
08:32:31 <anteaya> you can find it on git.openstack.org/openstack-infra
08:32:48 <anteaya> omrim_: well while that is a good idea
08:33:06 <anteaya> the difficulty lies in finding people willing to follow such a convention
08:33:50 <anteaya> whereas the current approach lies in improving communication and making the software more modular
08:34:03 <anteaya> and you and nuritv are welcome to help with both
08:34:30 <anteaya> you are learning the workflow for improving communication by offering your patch to the .rst file and working through the comments
08:34:40 <anteaya> as well as participating at the meetings, thank you
08:34:55 <anteaya> and you are welcome to participate in making the software more modular
08:35:15 <omrim_> anteaya: I will be glad to be the owner of such a generic solution
08:35:26 <omrim_> anteaya: For that, we should do a design
08:35:34 <anteaya> ah, well while I appreciate your enthusiasm
08:36:13 <anteaya> what I am trying to say is that we have tried it in the past and getting this group to come to consensous is difficult
08:36:29 <anteaya> #link http://specs.openstack.org/openstack-infra/infra-specs/specs/puppet-modules.html
08:36:42 <anteaya> that is the spec we are working on to make the software more modular
08:37:03 <anteaya> and actually putting your energy behind this effort which is already underway
08:37:30 <anteaya> is a great step toward increasing the energy that you are identifying
08:39:09 <omrim_> anteaya: :)
08:39:13 <anteaya> :D
08:44:44 <anteaya> omrim_: do you think we will see a new patchset for 141817 from you before the end of the meeting?
08:47:30 <omrim_> anteaya: I try to run the tox testing on my own enviroment before I add the patchset in order to avoud such a tox fauilre
08:47:39 <anteaya> good workflow
08:47:42 <anteaya> well done
08:47:49 <anteaya> are you able to run tox?
08:49:51 <omrim_> anteaya: Not really because in my server it passed
08:50:03 <anteaya> I don't understand what you just said
08:50:20 <omrim_> anteaya: While I except tox to failed like at the gerrit
08:50:20 <anteaya> when you execute the `tox` command, does tox run?
08:50:33 <anteaya> well then tox ran successfully
08:50:36 <anteaya> well done
08:50:44 <anteaya> and you had output
08:50:54 <anteaya> which tells you the patch still needs work
08:51:29 <anteaya> do you understand what needs to be changed in your patch?
08:51:53 <anteaya> have you a blank line after your code block as pleia2 suggested?
08:52:23 <omrim_> anteaya: Yes I understand what should I have to change
08:52:33 <anteaya> okay
08:52:36 * anteaya waits
08:53:05 <heyongli> anteaya,  hi, could i ask a question?
08:53:14 <anteaya> heyongli: hello, of course
08:53:23 <heyongli> refer to this page: http://logs.openstack.org/48/142648/3/check/check-tempest-dsvm-full/285f251/
08:53:32 <omrim_> anteaya: But when I run tox in the version that exist now at the gerrit I do not get the failure so I want to see the failure in my enviroment and then I will be able to change and rerun
08:54:14 <anteaya> omrim_: the version of what, do you mean patchset 4?
08:54:19 <heyongli> there is some text, "Guide to Tempest Results Runs.....", how  add it to apache?  our ci should put testcases link there.
08:54:22 <omrim_> Yes
08:55:01 <anteaya> heyongli: don't worry about creating a page of text there
08:55:27 <anteaya> heyongli: if you want to put some information about your system and your test runs, that is fine, you don't have to
08:55:38 <anteaya> heyongli: you don't have to match the text on this page
08:56:11 <heyongli> anteaya, that' s a good thing. and jogo want to see some link to testcases, i think there is the best palce to do such thing.
08:56:17 <anteaya> omrim_: interesting that running tox locally does not replicate the error that jenkins shows
08:56:41 <anteaya> heyongli: I think that would be a good direction
08:57:12 <heyongli> i don't know how to do that -:)..
08:57:53 <anteaya> heyongli: well there is a template with text somewhere in the source code, I would grep for "Guide to Tempest Results Runs" to find it
08:58:23 <anteaya> they I would come up with my own version
08:58:57 <anteaya> are you running a fork of tempest or are you downloading a fresh tempest on a regular basis?
08:59:30 <anteaya> omrim_: the only thing I could suggest is that versions of tox or sphinix on your local env don't match gerrits
08:59:53 <anteaya> omrim_: so you can either try to fix that or submit to gerrit
08:59:56 <anteaya> or both
09:00:03 <anteaya> and we are at time for this week
09:00:15 <anteaya> no meeting next week
09:00:21 <anteaya> next meeting Jan 6th
09:00:23 <omrim_> anteaya: Thanks, I think that the problem is with tthe tox.ini content
09:00:29 <anteaya> thank you all for attending
09:00:32 <anteaya> omrim_: okay
09:00:41 <anteaya> time for me to end the meeting
09:00:42 <heyongli> anteaya, thanks,
09:00:47 <anteaya> see you Jan. 6th
09:00:52 <anteaya> #endmeeting