Open Stack

Thanks Edgar and Anita.

I will keep monitoring the CI. Will attend the meeting as well.

Thanks,
Gary


On Mon, Sep 8, 2014 at 8:17 AM, Edgar Magana <edgar.magana at workday.com>
wrote:

> Completely understandable!
>
> I really appreciate the quick action.
>
> Gary,
>
> Please, recheck the testing commits for Neutron:
> https://review.openstack.org/#/c/114393/
>
> https://review.openstack.org/#/c/114629/
>
>
> Do attend as well the third-party meeting on Mondays.
>
> Thanks,
>
> Edgar
>
> On 9/8/14, 8:13 AM, "Anita Kuno" <anteaya at anteaya.info> wrote:
>
> >On 09/08/2014 10:54 AM, Edgar Magana wrote:
> >> Anita,
> >>
> >> Could you please enable back vArmour CI system?
> >> It seems that this time all tests have been completed properly.
> >>
> >> Thanks,
> >>
> >> Edgar
> >Thanks Edgar, the account has been re-enabled. Last week was just too
> >busy for anyone to have the time to re-enable it. I had asked twice last
> >week and noone was able to fulfill my request. Since load this week is
> >lighter, fungi was able to have a moment to re-enable.
> >
> >Thanks,
> >Anita.
> >>
> >> From: Gary Duan <gduan at varmour.com<mailto:gduan at varmour.com>>
> >> Date: Friday, September 5, 2014 at 1:57 PM
> >> To: Anita Kuno <anteaya at anteaya.info<mailto:anteaya at anteaya.info>>
> >> Cc: Edgar Magana
> >><edgar.magana at workday.com<mailto:edgar.magana at workday.com>>,
> >>"openstack-infra at lists.openstack.org<mailto:
> openstack-infra at lists.opensta
> >>ck.org>"
> >><openstack-infra at lists.openstack.org<mailto:
> openstack-infra at lists.opensta
> >>ck.org>>,
> >>"openstack-ci-test at varmour.com<mailto:openstack-ci-test at varmour.com>"
> >><openstack-ci-test at varmour.com<mailto:openstack-ci-test at varmour.com>>,
> >>Kyle Mestery <mestery at mestery.com<mailto:mestery at mestery.com>>
> >> Subject: Re: [OpenStack-Infra] vArmour CI is disabled
> >>
> >> Hi,
> >>
> >> Could you enable our CI system? I will limit the Gerrit Trigger to
> >>"openstack-dev/sandbox". I have manually verified that two testing
> >>patches are give expected votes.
> >>
> >> Thanks,
> >> Gary
> >>
> >>
> >> On Thu, Sep 4, 2014 at 2:18 PM, Gary Duan
> >><gduan at varmour.com<mailto:gduan at varmour.com>> wrote:
> >> Hi,
> >>
> >> Could you re-enable our vArmour CI system? I have manually verified
> >>that two testing patches are give expected vote and made sure the logs
> >>link is correct. I will limit the Gerrit Trigger to
> >>"openstack-dev/sandbox", and monitor it actively.
> >>
> >> Thanks,
> >> Gary
> >>
> >>
> >> On Tue, Sep 2, 2014 at 2:50 PM, Anita Kuno
> >><anteaya at anteaya.info<mailto:anteaya at anteaya.info>> wrote:
> >> On 09/02/2014 05:25 PM, Anita Kuno wrote:
> >>> On 09/02/2014 05:20 PM, Gary Duan wrote:
> >>>> Hi, Edgar,
> >>>>
> >>>> After our CI was enabled again this morning, I kept checking all the
> >>>> patches it run against, however, I can only see the vote, I'm not
> >>>>able to
> >>>> see the link it posts.
> >>>>
> >>>> I have modified the "URL to post" link, but I am not able to see if
> >>>>it is
> >>>> correct or not from the review
> >>>>review.openstack.org<http://review.openstack.org>.
> >>>>
> >>>> Thanks,
> >>>> Gary
> >>> Are you not able to consume the artifacts of your own system?
> >>>
> >>> Isolate yourself to sandbox and test there.
> >>>
> >>> Please do so or your system will be disabled.
> >>>
> >>> Thank you,
> >>> Anita.
> >> Your system was still posting comments:
> >> https://review.openstack.org/#/c/66347/
> >>
> >> It has been disabled.
> >>
> >> Please learn how to operate your system on the sandbox repo.
> >>
> >> Attending the third party meetings will allow you to ask questions of
> >> your fellow operators to help you get the information you need to
> >> successfully operate your system:
> >> https://wiki.openstack.org/wiki/Meetings/ThirdParty
> >>
> >> Thank you,
> >> Anita.
> >>>>
> >>>>
> >>>>
> >>>> On Tue, Sep 2, 2014 at 1:49 PM, Edgar Magana
> >>>><edgar.magana at workday.com<mailto:edgar.magana at workday.com>>
> >>>> wrote:
> >>>>
> >>>>> Gary,
> >>>>>
> >>>>> The varmour CI is NOT providing the right logs of their testing.
> >>>>> This is the published link for your CI:
> >>>>> http://173.228.89.201:8080/logs/$LOG_DIR
> >>>>>
> >>>>>
> >>>>> I found this from my validation commit:
> >>>>> https://review.openstack.org/#/c/114393/
> >>>>>
> >>>>>
> >>>>> Please, resolve this issue ASAP.
> >>>>>
> >>>>> Edgar
> >>>>>
> >>>>> On 9/2/14, 9:33 AM, "Anita Kuno"
> >>>>><anteaya at anteaya.info<mailto:anteaya at anteaya.info>> wrote:
> >>>>>
> >>>>>> On 09/02/2014 12:26 PM, Gary Duan wrote:
> >>>>>>> Hi, Edgar,
> >>>>>>>
> >>>>>>> Our Jenkins shows the connection to
> >>>>>>>review.openstack.org<http://review.openstack.org> is down.
> >>>>>>>
> >>>>>>> Connection error : com.jcraft.jsch.JSchException: Auth fail
> >>>>>>>
> >>>>>>> Can I run against a specific patch and post the review with account
> >>>>>>> disabled?
> >>>>>>>
> >>>>>>> Thanks,
> >>>>>>> Gary
> >>>>>> Your system is re-enabled.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Anita.
> >>>>>>>
> >>>>>>>
> >>>>>>> On Tue, Sep 2, 2014 at 8:42 AM, Edgar Magana
> >>>>>>><edgar.magana at workday.com<mailto:edgar.magana at workday.com>>
> >>>>>>> wrote:
> >>>>>>>
> >>>>>>>>  Did you run it yet against these two commits:
> >>>>>>>>
> >>>>>>>>  https://review.openstack.org/#/c/114393/
> >>>>>>>> https://review.openstack.org/#/c/114629/
> >>>>>>>>
> >>>>>>>>  Edgar
> >>>>>>>>
> >>>>>>>>   From: Gary Duan <gduan at varmour.com<mailto:gduan at varmour.com>>
> >>>>>>>> Date: Monday, September 1, 2014 at 10:40 AM
> >>>>>>>> To: Anita Kuno <anteaya at anteaya.info<mailto:anteaya at anteaya.info
> >>
> >>>>>>>> Cc:
> >>>>>>>>"openstack-infra at lists.openstack.org<mailto:
> openstack-infra at lists.o
> >>>>>>>>penstack.org>" <
> >>>>>>>>
> >>>>>>>>openstack-infra at lists.openstack.org<mailto:
> openstack-infra at lists.op
> >>>>>>>>enstack.org>>,
> >>>>>>>>"openstack-ci-test at varmour.com<mailto:
> openstack-ci-test at varmour.com
> >>>>>>>>>"
> >>>>> <
> >>>>>>>>
> >>>>>>>>openstack-ci-test at varmour.com<mailto:openstack-ci-test at varmour.com
> >
> >>>>>>>>>
> >>>>>>>> Subject: Re: [OpenStack-Infra] vArmour CI is disabled
> >>>>>>>>
> >>>>>>>>   Hi, Anita,
> >>>>>>>>
> >>>>>>>>  I have fixed our CI system. Can you enable it so we can test it
> >>>>>>>> against
> >>>>>>>> the sandbox? I want to make sure the URL for logs is correct.
> >>>>>>>>
> >>>>>>>>  Thanks,
> >>>>>>>> Gary
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On Tue, Aug 26, 2014 at 1:22 PM, Anita Kuno
> >>>>>>>><anteaya at anteaya.info<mailto:anteaya at anteaya.info>>
> >>>>>>>> wrote:
> >>>>>>>>
> >>>>>>>>> Your system is obviously not conducting tests at the moment. One
> >>>>>>>>> minute
> >>>>>>>>> to post a successful build message on a new patch is not
> >>>>>>>>>acceptable.
> >>>>>>>>> Also your url does not yield any logs.
> >>>>>>>>> https://review.openstack.org/#/c/113421/
> >>>>>>>>>
> >>>>>>>>> Your system is disabled.
> >>>>>>>>>
> >>>>>>>>> Please fix your system to test the patches it is triggered by.
> >>>>>>>>>Please
> >>>>>>>>> also ensure the url in your comment yields logs as outlined in
> >>>>>>>>>the
> >>>>>>>>> third
> >>>>>>>>> party ci requirements:
> >>>>>>>>> http://ci.openstack.org/third_party.html#requirements
> >>>>>>>>>
> >>>>>>>>> Once you have fixed your system, we can re-enable it so you may
> >>>>>>>>>test
> >>>>>>>>> it
> >>>>>>>>> on the sandbox repository:
> >>>>>>>>> http://git.openstack.org/cgit/openstack-dev/sandbox/ Then get
> >>>>>>>>>Kyle
> >>>>>>>>> Mestery's permission to comment again on Neutron patches.
> >>>>>>>>>
> >>>>>>>>> Thank you,
> >>>>>>>>> Anita.
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>> This message is for the designated and authorized recipient only
> >>>>>>>>and
> >>>>>>>> may
> >>>>>>>> contain privileged, proprietary, confidential or otherwise private
> >>>>>>>> information relating to vArmour Networks, Inc. and is the sole
> >>>>>>>> property of
> >>>>>>>> vArmour Networks, Inc.  Any views or opinions expressed are solely
> >>>>>>>> those of
> >>>>>>>> the author and do not necessarily represent those of vArmour
> >>>>>>>>Networks,
> >>>>>>>> Inc.
> >>>>>>>> If you have received this message in error, or if you are not
> >>>>>>>> authorized to
> >>>>>>>> receive it, please notify the sender immediately and delete the
> >>>>>>>> original
> >>>>>>>> message and any attachments from your system immediately. If you
> >>>>>>>>are
> >>>>>>>> not a
> >>>>>>>> designated or authorized recipient, any other use or retention of
> >>>>>>>>this
> >>>>>>>> message or its contents is prohibited.
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
> >>
> >>
> >>
> >>
> >> This message is for the designated and authorized recipient only and
> >>may contain privileged, proprietary, confidential or otherwise private
> >>information relating to vArmour Networks, Inc. and is the sole property
> >>of vArmour Networks, Inc.  Any views or opinions expressed are solely
> >>those of the author and do not necessarily represent those of vArmour
> >>Networks, Inc. If you have received this message in error, or if you are
> >>not authorized to receive it, please notify the sender immediately and
> >>delete the original message and any attachments from your system
> >>immediately. If you are not a designated or authorized recipient, any
> >>other use or retention of this message or its contents is prohibited.
> >>
> >
>
>

-- 
This message is for the designated and authorized recipient only and may 
contain privileged, proprietary, confidential or otherwise private 
information relating to vArmour Networks, Inc. and is the sole property of 
vArmour Networks, Inc.  Any views or opinions expressed are solely those of 
the author and do not necessarily represent those of vArmour Networks, Inc. 
If you have received this message in error, or if you are not authorized to 
receive it, please notify the sender immediately and delete the original 
message and any attachments from your system immediately. If you are not a 
designated or authorized recipient, any other use or retention of this 
message or its contents is prohibited.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-infra/attachments/20140908/34a51bd6/attachment-0001.html>