08:02:16 #startmeeting third-party 08:02:18 Meeting started Tue Sep 1 08:02:16 2015 UTC and is due to finish in 60 minutes. The chair is anteaya. Information about MeetBot at http://wiki.debian.org/MeetBot. 08:02:19 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 08:02:21 The meeting name has been set to 'third_party' 08:02:50 hello 08:04:03 anteaya: hi 08:04:27 hi jyuso 08:04:51 anteaya: I've send mail,have you seen it?:) 08:05:56 I am looking at it now to approve it 08:06:46 jyuso: I'm going to reject it 08:06:51 and paste a copy to you 08:07:03 and I need you to post it as a reply to http://lists.openstack.org/pipermail/third-party-announce/2015-August/000263.html 08:07:25 when I start a thread I need replies to be to the inital post to the thread 08:07:32 to keep the conversation organized 08:07:43 rather than having new threads 08:07:49 can you understand that? 08:08:04 anteaya: ok 08:08:23 thank you 08:08:36 here is the paste: http://paste.openstack.org/show/437118/ 08:12:06 anteaya, sorry for this bug troubles so many people 08:13:29 yonglihe: hi how are you 08:13:38 well that is the nature of third party ci 08:13:46 the output affects a lot of people 08:13:48 good till to hear our CI problem this morning 08:13:58 yes you have been doing well 08:14:23 in future look at the third-party-announce mailing list first if there is an issue 08:14:54 and keep the conversation there, posts to that list are moderated so will need my approval to be posted, so after you send an email 08:14:55 anteaya: sorry,I'm not in third-party-announce mailing list.so i didn't receive your mail. 08:15:00 please be patience 08:15:06 jyuso: ah 08:15:22 jyuso: are you subscribed now? 08:16:01 go to lists.openstack.org 08:16:15 select the third-party-announce link 08:16:22 it should tell you how to subscribe 08:17:14 jyuso, use this link http://lists.openstack.org/cgi-bin/mailman/listinfo/third-party-announce 08:19:11 anteaya: I've subscribed. 08:19:15 anteaya, we all subscribed now, thanks a lot 08:19:15 thank you 08:19:28 yonglihe: great 08:19:40 so now copy the subject line from http://lists.openstack.org/pipermail/third-party-announce/2015-August/000263.html 08:19:53 Intel PCI CI is disabled 08:20:03 and use that as your subject for your email 08:20:07 not the tag part 08:20:17 not [Third-party-announce] 08:20:28 that gets added automatically when you post to that list 08:20:51 then your reply should be considered a reply to the parent post 08:20:55 does that make sense? 08:21:10 got it 08:22:31 great, thank you 08:22:49 anteaya: ok,thanks,the mail will be sent soon. 08:22:53 thank you 08:27:57 anteaya, mail sent, waiting approved now, i don't know if i do all right, update me if i'm still wrong. 08:29:17 yonglihe: you did fine, thank you http://lists.openstack.org/pipermail/third-party-announce/2015-September/000264.html 08:30:04 the month changed, so it it isnt showing up below the parent, but they both have the same subject so we can find them now, thank you 08:30:49 okay great 08:30:58 thanks for the report 08:31:16 you have some additional work to do to figure out your system, correct? 08:31:29 anteaya, is there anything bother you, i can tell a longer detail here 08:31:51 it is best if the details are on the mailing list 08:32:09 then others can help me decide when your system is ready to be active 08:32:33 also other operators can learn from your experience and hopefully make different choices for their systems 08:32:39 anteaya, we changed that testing scripts yesterday, and rolling back already. 08:33:52 okay but you still have an issue you want to fix, correct? 08:34:15 what are you going to do to ensure that your new solution doesn't create the same problem? 08:35:43 anteaya, firstly, we rolling back to original scripts, that's running for long time, second, we will closely monitoring the states to make sure it will running as it did before. 08:35:55 great 08:36:27 can you post that to the mailing list please? in reply to your post to third-party-announce? 08:36:34 third it , we will standard our testing system to ensure any new change be tested fully for days. 08:36:42 sure, anteaya 08:36:45 wonderful, thank you 08:42:53 mail sent, anteaya , additionally, to eliminate the human error , I'm wring ansible scripts for the CI, that should enable eliminate human accident, i think. 08:43:43 thank you 08:43:52 having scripts is a useful thing 08:44:04 if you want to write your own that is fine 08:44:23 we have a number of puppet scripts already for installing portions of the ci 08:44:44 and are working on creating a puppet single installer for a third party ci 08:44:47 yeah, ansible relatively simple, and, because we are not identical to upstream CI, so use upstream scripts also need many work, 08:45:10 #link http://git.openstack.org/cgit/openstack-infra/puppet-openstackci/tree/ 08:45:18 sure as you like 08:45:45 where did you send the email, I don't see it yet in my administrative interface for the third-party-announce mailing list 08:46:11 this is great, i will evaluate this one, if it suite for some part of our system, i definitely choose this one. 08:46:19 thank you 08:46:29 I look forward to your feedback 08:47:03 yonglihe: I don't see you email yet 08:47:08 your email 08:47:35 anteaya, sorry, check it now. 08:47:40 there it is 08:47:42 thank you 08:48:28 where was it? 08:49:05 in my Thunderbird, not sent, sorry 08:49:47 ah 08:49:59 good thing we found it then before I went back to bed 08:50:01 :) 08:51:04 we are going to deploy a mail alert to all machine to help identify problem ASAP. 08:51:18 a mail alert 08:51:27 an internal mail alert? 08:51:31 yes 08:51:35 oh good 08:51:38 good idea 08:51:48 inform operator when anything seems wrong 08:51:55 I have requested your system be re-enabled 08:51:59 wonderful thank you 08:52:15 it will be a few more hours before anyone who can re-enable it is awake 08:52:29 so hopefully be tomorrow it is in action again 08:52:37 thanks for being so attentive to this 08:52:41 I really appreciate it 08:52:44 anteaya, thanks for helping 08:52:49 of course :) 08:53:01 you have updated your wikipage status for your system? 08:53:19 anteaya: yes,i've change status of offline. 08:53:37 anteaya: to 08:53:43 #link https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-PCI-CI 08:53:48 did you? 08:53:55 yes you did 08:53:59 thank you 08:54:13 also on this page 08:54:16 #link https://wiki.openstack.org/wiki/ThirdPartySystems 08:54:34 can you do this? If your system is going down or having problems, change the entry to {{ThirdPartySystemTableEntryDown|}} 08:54:42 does that make sense? 08:54:54 anteaya: sure 08:54:55 thanks anteaya , got it 08:54:57 thank you 08:55:01 wonderful 08:55:07 anteaya: thanks,i'll change it soon 08:55:17 then when your system is back up you can change it back 08:55:29 copy, anteaya 08:55:34 I think that was all I wanted to talk about here 08:56:52 anteaya, thanks. 08:57:00 anteaya: yes,i'll remember these steps.thank you;) 08:57:45 wonderful 08:57:49 thank you both 08:57:57 it was nice to work with you again 08:58:08 I am thinking about closing the meeting 08:58:18 ok, good night 08:58:19 can you think of any reason why I should keep it open? 08:58:22 thanks 08:58:24 good night 08:58:30 #endmeeting