Yes, Anita. We are seeking the alternatives to fix it and hope the CIs can be 
recovered very soon.

Also please allow me to explain a little bit, we shut down the service without 
any email notification, but update the wiki 
(https://wiki.openstack.org/wiki/ThirdPartySystems/Intel-PCI-CI) only according 
to the suggestion from the Infra team.

[09:18:52] <anteaya> then if anyone wonders what is happening with your system 
they check the status page
[09:18:52] <anteaya> does that make sense?
[09:19:13] <anteaya> correct
[09:19:23] <anteaya> anytime you need to change the status of your ci
[09:19:37] <jyuso1> OK,thanks.I
[09:19:37] <anteaya> change it here
[09:19:45] <jyuso1> I'll change it soon
[09:19:49] <anteaya> and please don't send an email to the mailing list, people 
won't read it anyway

We're going to make the CIs more stable in the future, and in case that any 
issue happened unexpectedly, we will let the community know.

Sorry for inconvenience and thank you for your understanding. 

Best Regards.
--
Shane
-----Original Message-----
From: Anita Kuno [mailto:ante...@anteaya.info] 
Sent: Thursday, July 16, 2015 10:34 AM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Nova][infra][third-party] Intel actively seeking 
solution to CI issue and getting close to a solution

On 07/15/2015 10:19 PM, yongli he wrote:
> Hello OpenStackers!
> 
> The Intel PCI/SRIOV/NGFW/PTAS CI located in China, due to reasons 
> beyond our control, lost connectivity to the Jenkins servers.

The great firewall of China is making quite a few folks unhappy.


> Although the CI
> system is working fine we haven't been able to report results back for 
> about a month now.
> 
> We are actively looking for a solution to this problem.
> 
> Currently we are seeking a VM in AWS or similar public cloud to hold 
> our CI logs,

Have you taken a look at any of the fine offerings from companies who operate 
OpenStack public clouds?
http://www.openstack.org/marketplace/public-clouds/


> which will quickly give us a short term solution.  For a longer term 
> solution we are exploring moving to machines located in the US.
> 
> Sorry for the inconvenience and your patience.
> 
> Regards
> Yongli

Thanks Yongli,
Anita.

> 
> 
> 
> 
> ______________________________________________________________________
> ____ OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: 
> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> 


__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Reply via email to