08:00:02 <anteaya> #startmeeting third-party
08:00:03 <openstack> Meeting started Tue Mar 31 08:00:02 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:04 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote.
08:00:06 <openstack> The meeting name has been set to 'third_party'
08:00:21 <anteaya> raise your hand if you are here for the third party meeting
08:00:50 <lennyb> Hi
08:00:55 <anteaya> hello lennyb
08:01:02 <anteaya> nice to see you
08:01:21 <anteaya> how are you today?
08:01:37 <lennyb> you too. It looks like only you and me again :)
08:01:44 <anteaya> it happens
08:01:56 <anteaya> how are you doing at responding to the email thread?
08:02:06 <anteaya> I don't think i have seen your response yet
08:02:43 <lennyb> I found a great feature in outlook - 'time zones' for setting recursive meetings with no effect of local summer/winter time.
08:02:55 <anteaya> well that is great
08:03:08 <anteaya> I'm glad you found something that works for you
08:03:50 <lennyb> Regarding email, I did not respond yet, since we had some issues with showing html reports (it was shown as plain text ) and recent Nova failures that I am fixing.
08:05:23 <anteaya> okay
08:05:35 <anteaya> what is wrong with plain text reports for now?
08:06:51 <lennyb> now it works as html according to community policy and jogo's comment
08:07:47 <anteaya> where is the community policy that it has to be in html?
08:08:01 <anteaya> and where is jogo's comment to that effect
08:08:16 <anteaya> if people are saying that your logs have to be in html that is news to me
08:08:27 <anteaya> and would like to see where you have seen that stated
08:08:36 <anteaya> you have to have logs, yes
08:09:01 <anteaya> the closer they are to what jenkins provides, the better it is for everyone concerned, yes
08:09:17 <anteaya> they have to be in html? I haven't seen that anywhere
08:09:38 <lennyb> "I couldn't find the equivalent of: http://logs.openstack.org/68/135768/9/check/check-tempest-dsvm-full/f6c95de/logs/testr_results.html.gz"
08:10:01 <anteaya> testr_results
08:10:22 <anteaya> had you provided the output of testr_results in any format?
08:10:42 <lennyb> This is his quote and my understanding of it. The link he opens as html, our ones were shown as plain text
08:10:49 <anteaya> that wasn't a request for html that was a request for testr_results output
08:11:09 <anteaya> had you shown testr_results prior to his comment?
08:12:22 <lennyb> yes, but was also not in root folder. so it's fixed now
08:12:37 <anteaya> can I see a link to one of your runs
08:12:44 <anteaya> and we can look at your logs
08:15:14 <lennyb> 1sec
08:16:23 <lennyb> I done have runs after the fix, yet. This is before the fix.  http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20150318_1650/
08:16:57 <anteaya> okay
08:17:13 <anteaya> can we agree that http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20150318_1650/console.html.gz is useless in its current format?
08:18:37 <anteaya> #link http://imgur.com/6MXyRQ4
08:18:39 <lennyb> yes. will be fixed as well
08:18:43 <anteaya> is what I see
08:19:58 <anteaya> testr_results is the only log that does seem readable: http://144.76.193.39/ci-artifacts/Check-MLNX-Nova-ML2-Sriov-driver_20150318_1650/logs/testr_results.html.gz
08:20:16 <anteaya> it doesn't provide much information but the format is readable
08:20:53 <lennyb> It was smoke run with 2 tests
08:20:57 <anteaya> yes
08:20:59 <anteaya> I see that
08:21:12 <anteaya> so you have a ways to go, yes?
08:21:49 <anteaya> so personally right now, I wouldn't be supportive of you leaving comments anywhere but on a sandbox repo
08:22:03 <lennyb> I believe so.
08:22:10 <anteaya> because the artifacts you are providing are not useful for anyone
08:22:12 <anteaya> okay good
08:22:21 <anteaya> so going forward, use your judgement
08:22:37 <anteaya> if you can't read what you provide, chances are noone else can either
08:23:01 <anteaya> does that make sense?
08:23:45 <anteaya> so here is my question
08:23:56 <anteaya> mellanox is leaving comments on other repos, right?
08:24:15 <anteaya> their logs must be in some kind of readable shape, I am assuming
08:24:27 <anteaya> why are you on your own with this?
08:24:27 <lennyb> yes, neutron and cinder
08:24:42 <anteaya> why isn't anyone at mellanox helping you get your logs in shape
08:24:58 <anteaya> certainly someone at mellanox must have figured out log formatting by now
08:25:06 <anteaya> why aren't they supporting you?
08:25:17 <lennyb> I am not on my own, I am just the one who represents Mellanox CI
08:26:33 <anteaya> http://144.76.193.39/ci-artifacts/143297/30/Check-MLNX-Neutron-ML2-driver/
08:26:49 <anteaya> and this is from a neutron patch
08:26:57 <anteaya> and the logs are in terrible shape
08:27:16 <lennyb> I see, It will be fixed a.s.a.p as well
08:27:16 <anteaya> Mellanox CI is commenting and leaving this on Neutron patches
08:27:21 <anteaya> how?
08:27:38 <anteaya> is there anyone at Mellanox that has figured out log formatting?
08:28:01 <anteaya> this was Kyle's and my concern we outlined on the third-party-announce mailing list thread
08:28:16 <anteaya> Mellanox CI is the account that comments on Neutron patches
08:28:24 <anteaya> you are just learning, which is fine
08:28:29 <anteaya> everyone has to learn
08:29:02 <anteaya> but this CI has voting privledges in Neutron
08:29:08 <anteaya> do you understand what that means?
08:29:41 <anteaya> can you understand our concerns here?
08:29:41 <lennyb> as I said it will be fixed.
08:29:56 <anteaya> can you understand our concerns?
08:31:01 <lennyb> yes, I do understand your concern, We are very responsive on every issue of Mellanox CI failure
08:31:50 <anteaya> do you understand that you are new
08:32:31 <anteaya> and that the reason we don't start off with systems voting right away anymore is that we have seen the mistakes that new people make when they are learning how to operate a ci system?
08:32:49 <anteaya> this is for your protection as much as for neutron's
08:32:54 <lennyb> yes, I understand and I do have full support of Mellanox team.
08:33:16 <anteaya> how can they leave a new person solely responsible for a voting ci system?
08:33:43 <anteaya> at the very least you should request yourself that for neutron voting permissions be removed until you learn what you are doing
08:34:21 <anteaya> if anythign this will be seen as a very responsible move on your part
08:35:23 <anteaya> this isn't your fault
08:35:41 <anteaya> ci operators are routinely expected to accomplish tasks that they have no idea how to do
08:35:50 <anteaya> but this approach has a cost
08:35:53 <anteaya> and you pay it
08:35:58 <anteaya> and so does the community
08:36:12 <anteaya> whereas management just thinks it is your fault
08:36:32 <anteaya> it is far better to be honest with yourself, and with us
08:36:58 <anteaya> and have the permissions on the account set in such a way that the operator is cognizant of the ramifications of their actions
08:37:05 <anteaya> and new people just aren't
08:37:44 <anteaya> hence we learned to restrict accounts run by new ci operators
08:37:51 <anteaya> which usually is new ci accounts
08:38:12 <anteaya> I don't know if I have other examples of a running ci account that is just handed off to a new person
08:41:26 <lennyb> As I said, I have enough experience in the field and enough support of the team and of the community ( as I see ) to continue running our CIs. logs will be fixed. Nova CI will be updated and appropriate email will be sent to the list
08:41:53 <anteaya> I don't know as you heard anything I said
08:41:55 <anteaya> sigh
08:42:05 <anteaya> I guess we just have to do this the hard way
08:43:29 <anteaya> as you see fit
08:43:46 <anteaya> anything else I can help you with today?
08:51:26 <lennyb> anteaya, we are currently disabling all our CIs untill this formatting issue is solved.
08:51:39 <anteaya> lennyb: good call
08:51:44 <anteaya> thanks for listening
08:52:03 <anteaya> can you update your system on this page: https://wiki.openstack.org/wiki/ThirdPartySystems
08:52:08 <anteaya> #link https://wiki.openstack.org/wiki/ThirdPartySystems
08:52:12 <anteaya> and this
08:52:20 <anteaya> #link https://wiki.openstack.org/wiki/ThirdPartySystems/Mellanox_CI
08:52:28 <anteaya> with your current status please?
08:52:34 <anteaya> thank you so much
08:52:37 <anteaya> I'm grateful
08:53:35 <anteaya> if you are around in a few hours I suggest pinging asselin, he is active in the cinder channel and in the infra channel
08:53:54 <anteaya> asselin he may have some suggestions about how you can get a readable format in your logs
08:54:26 <anteaya> he is on pacific time so should be around in 7 hours
08:54:35 <lennyb> this issue was caused yesterday, when I added html support to the server that stores our logs.
08:54:58 <anteaya> ah
08:55:08 <anteaya> okay that is making more sense now, thank you
08:55:25 <anteaya> I personally have never seen this issue before
08:55:41 <anteaya> but check with asselin or perhaps patrickeast
08:55:49 <anteaya> one of them might have seen it previously
08:55:55 <anteaya> thanks for being proactive
08:55:58 <anteaya> I appreciate it
08:55:58 <lennyb> the logs are ok, just trying to show plain txt as html. it has nothing to do with CI itself.
08:56:05 <anteaya> right I know
08:56:21 <anteaya> but artifacts that are useful is important
08:57:02 <anteaya> and being proactive in ensuring what you provide is consumable goes a long way to folks recognizing that you take responsiblity for your actions
08:57:12 <anteaya> which translates to how they view your entire system
08:57:14 <anteaya> so thank you
08:57:59 <lennyb> I know. Thanks for the meeting, tips and guidance
08:58:20 <anteaya> thanks for showing up
08:58:30 <anteaya> showing up is really _my_ only requirement
08:58:38 <anteaya> anything else can be learned
08:58:46 <anteaya> but you can't learn it if you don't show up
08:58:48 <anteaya> so thanks
08:58:56 <anteaya> and yeah looks like we are at the end
08:59:06 <anteaya> see you next week, I hope, lennyb
08:59:22 <anteaya> #endmeeting