08:00:01 <anteaya> #startmeeting third-party 08:00:02 <openstack> Meeting started Tue Jan 6 08:00:01 2015 UTC and is due to finish in 60 minutes. The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:00:03 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:00:05 <openstack> The meeting name has been set to 'third_party' 08:00:07 <trinaths> Hi 08:00:10 <anteaya> hello 08:00:31 <anteaya> anyone else here for the third party meeting? 08:00:53 <anteaya> how are you trinaths? 08:01:19 <trinaths> Doing good. thank you .. :) 08:01:23 <anteaya> good 08:01:29 <trinaths> my first meeting in 2015 08:01:36 <anteaya> great 08:01:38 <trinaths> Happy New Year all 08:02:05 <anteaya> what shall we talk about, trinaths? 08:02:28 <jyuso> hi anteaya,hi everyone.sorry I'm late:) 08:02:39 <anteaya> jyuso: hello, not to worry 08:02:50 <anteaya> we are just deciding what to talk about 08:02:56 <anteaya> jyuso: any thoughts? 08:03:17 <trinaths> I'm Currently working on the CI - an upgrade process. 08:03:48 <anteaya> trinaths: great 08:03:52 <anteaya> how is that going? 08:04:32 <trinaths> incorporating upgraded CRD (our service code) to the CI 08:05:10 <trinaths> we have less attendance today ?? I guess 08:05:25 <anteaya> we are just coming back from holidays for some 08:05:36 <anteaya> and russia is on holidays from the 1 to the 12 08:05:52 <anteaya> the first week back after a break is sometimes tough for people 08:06:33 <trinaths> :) 08:06:55 <anteaya> so what do you want to accomplish this week, regarding third party 08:09:09 <trinaths> my self, had a TODO here, [1] Upgrade CRD service to 2 nodes of CI and [2] Enabled two more nodes for neutron-fwaas with updated CRD service - requirement for my FWaaS Plugin. 08:09:09 <anteaya> I'm taking my cue from you, so do speak up 08:09:25 <anteaya> good 08:09:29 <trinaths> it takes some time for me to type 08:09:36 <anteaya> ah I see 08:09:43 <trinaths> :) 08:09:51 <anteaya> how is step 1 coming along? 08:10:13 <trinaths> one server just now completed, so need to test with sandbox, and then divert to neutron. 08:10:29 <anteaya> great 08:10:38 <trinaths> will clone the server-1 to server-2 so both share the task 08:10:48 <anteaya> I'm not sure you knew but we have a dedicated sandbox for ci 08:11:16 <jyuso> trinaths: May I ask a question about your step 1? 08:11:22 <trinaths> oh! I'm not aware of this. How is this different from normal sandbox 08:11:26 <trinaths> please go ahead. 08:11:27 <anteaya> #link http://git.openstack.org/cgit/openstack-dev/ci-sandbox/ 08:11:38 <trinaths> oh okay. Will use this. 08:12:10 <anteaya> thank you 08:12:53 <anteaya> it hopefully will be less shocking for new devs using sandbox to practice the contributor's workflow to have fewer ci systems report on all their patches 08:13:11 <anteaya> jyuso: do ask your question of trinaths 08:13:43 <jyuso> trinaths: If we create a 2 node CI task.How did you create project and collect logst?I'm confused about how to collect logs in multi node environment. 08:15:14 <trinaths> jyuso: in my setup jenkins + gearman + zuul gives jobs to the registered nodes. 08:16:05 <trinaths> regarding posting of logs, I have written a custom script to upload the logs to the freescale hosted server in a specific location. The same is configured in Zuul and is posted as comment in gerrit. 08:17:48 <anteaya> jyuso: any reply? 08:18:37 <trinaths> jyuso: Okay with the reply ? do u need more clarification 08:19:47 <jyuso> trinaths:Yes.Thanks for your reply.I think it is very helpful. 08:19:58 <trinaths> okay 08:20:07 <anteaya> great 08:21:01 <anteaya> what else shall we discuss? 08:24:50 <trinaths> no doubts from my end for now .. :) 08:24:57 <anteaya> great 08:25:06 <anteaya> anything else you want to accomplish 08:25:15 <anteaya> perhaps contributing back to infra? 08:31:07 <jyuso> anteaya:Yes.If I want to do some jobs of infra,what could I do then? 08:31:17 <anteaya> thanks jyuso 08:31:26 <anteaya> well to start you could review patches 08:31:39 <anteaya> have you ever reviewed any openstack patches before? 08:32:07 <jyuso> anteaya: I'm planning to wirte some Tempest case of Ceilometer after our CI is online:) 08:32:18 <anteaya> great 08:32:33 <anteaya> so reviewing some tempest patches would be a good place to start 08:32:53 <anteaya> so you can learn what the tempest team likes to see in new tempest code 08:32:58 <anteaya> does that make sense? 08:33:16 <jyuso> anteaya: OK,thanks for your advice:) 08:33:30 <anteaya> jyuso: have you reviewed any openstack patches before? 08:33:38 <jyuso> anteaya: not yet 08:33:48 <anteaya> okay good to know 08:33:50 <jyuso> anteaya: I just do deploy job 08:34:06 <jyuso> anteaya: and write some Tempest cases 08:34:16 <anteaya> okay 08:34:27 <anteaya> here is a good place to start learning how to review patches 08:34:54 <anteaya> #link http://anteaya.info/blog/2013/03/21/reviewing-an-openstack-patch/ 08:35:16 <anteaya> some people think they have to know everything about the code base before they review any patches 08:35:35 <anteaya> when in actual fact, learning how to give a good review helps you to learn the code 08:35:54 <anteaya> as well as how to spot well written code as opposed to poorly written code 08:37:18 <anteaya> these are all the open tempest patches 08:37:22 <anteaya> #link https://review.openstack.org/#/q/status:open+project:openstack/tempest,n,z 08:37:40 <anteaya> so start anywhere and start to look at them 08:37:45 <anteaya> look for patterns 08:37:56 <anteaya> read what other reviewers have said 08:38:26 <anteaya> these people are the tempest core reviewers 08:38:29 <anteaya> #link https://review.openstack.org/#/admin/groups/42,members 08:38:38 <anteaya> read what they say about patches 08:39:16 <anteaya> just reading core reviewer comments on patches for 2 weeks will be a great use of your time 08:39:23 <anteaya> though you will think it won't 08:39:48 <anteaya> once you feel you have something to offer, even if it is just a question, post it as a comment on a patch 08:40:02 <anteaya> you start to get feedback on your reviewing style 08:40:08 <anteaya> and everyone benefits 08:40:42 <anteaya> jyuso: does that make sense? 08:40:45 <jyuso> anteaya: thank you for your patience:) 08:40:48 <jyuso> anteaya: yes 08:40:52 <anteaya> great 08:40:55 <anteaya> my pleasure 08:41:08 <jyuso> anteaya: I'm reading your blog.so reply is a bit slow.sorry:) 08:41:09 <anteaya> happy to take the time to support someone contributing back 08:41:14 <anteaya> jyuso: ah 08:41:21 <anteaya> no problem, I understand 08:51:43 <trinaths> do we have our own pypi ? 08:52:10 <anteaya> we had a mirror of pypi but got rid of it 08:52:35 <anteaya> #link http://pypi.openstack.org/ 08:52:55 <anteaya> so the server is still up but no content 08:53:11 <trinaths> then, in the requirements of the projects, there some version, >=1.1.0 like that, which are not atleast in pypi.python.org. 08:53:30 <anteaya> do you have an example? 08:54:30 <trinaths> in keystone, its oslo.db>=1.1.0 but in pypi.python.org, its 1.0.3 https://pypi.python.org/pypi/oslo.db 08:54:53 <trinaths> where to get this >=1.1.0 version ? 08:55:10 <anteaya> first I have to confirm what you are seeing in keystone 08:55:34 <trinaths> requirements.txt 08:56:02 <anteaya> #link http://git.openstack.org/cgit/openstack/keystone/tree/requirements.txt#n24 08:56:08 <anteaya> I see it 08:56:19 <trinaths> yes 08:56:27 <anteaya> jhesketh: you about? 08:56:37 <trinaths> pypi.openstack.org is empty. 08:56:49 <anteaya> yes it is 08:56:59 <trinaths> pypi.python.org has an lesser version. any idea on how to proceed on the same 08:57:13 <trinaths> i mean where to find the applicable/required version 08:57:55 <anteaya> olso.db has a 1.3.0 version, a 1.2.0 version, a 1.1.0 version: http://git.openstack.org/cgit/openstack/oslo.db/ 08:58:46 <anteaya> and you are correct these versions are not on pypi.python.org 08:58:58 <anteaya> so in short I don't know yet, but I will find out 08:59:06 <anteaya> this is a good question, thanks trinaths 08:59:10 <trinaths> okay, so there is no need at all for querying pip for installaing these packages 08:59:17 <anteaya> I don't know 08:59:42 <anteaya> time to wrap up 08:59:45 <trinaths> every time, in my CI, I see that the packages in requirements.txt are instaled with pip 08:59:51 <anteaya> thanks for your attendance 08:59:57 <anteaya> trinaths: I will find out 09:00:03 <anteaya> see you next week 09:00:07 <anteaya> #endmeeting