+ ci-users, not sure TripleO CI folks are subscribed to centos-devel.
David Moreau Simard
Senior Software Engineer | Openstack RDO
dmsimard = [irc, github, twitter]
On Sep 7, 2016 11:56 AM, "Karanbir Singh" <mail-lists(a)karan.org> wrote:
> hi guys,
>
> I am trying to track down exactly how the tripleo jobs - specially the
> large image builds are being run. Were trying to track down network
> bottlenecks and the tripleo jobs are consistently coming up as the
> biggest pain points.
>
> Is there an overview available to look at for the work flow and data
> flow within the ci infra itself ?
>
> regards
>
> --
> Karanbir Singh
> +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
> GnuPG Key : http://www.karan.org/publickey.asc
> _______________________________________________
> CentOS-devel mailing list
> CentOS-devel(a)centos.org
> https://lists.centos.org/mailman/listinfo/centos-devel
>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Folks,
We will be rebooting some of the CI infrastructure on Wednesday
September 7th starting at 06h00 UTC to apply updates. We will have the
usual quiet period starting 1 hour beforehand to let other job finish.
Below are the machines/services affected:
- - ci.centos.org Jenkins Interface
- - slave01.ci.centos.org (your Jenkins slaves will be reconnected for
you)
- - Duffy node provisioner
- - artifacts.ci.centos.org
- - Network services through the CI gateway (short outage)
We will keep the list up to date as we progress through this window. If
there are any questions or concerns please let us know.
Cheers!
- --
Brian Stinson
CentOS CI Infrastructure Team
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJXyaB6AAoJEIMGvNKzCweMZC0P/0wWQkU5ZWhmPyzSUKUzRAGw
uSau9ZV0BRAc9dM4djKraz9eNp+LoNjCiscEdrd5us8hVgNWtPMfhUqsg3AwJ3ym
6OXH7ja3ABideiP0X3Ycg2KmzBi14ti9NuNgY+WqPlYyly0r9nT0hv0qSomHDTU/
e7ot3Z56WYXk4ZQXb6/aOqgT5PajLJlnhT1N6LC8G+WU7Gx0qlzWRtIoxDGiOnAM
vjJv7i9tyJ8YLJWMUhoEL35b/UZGfMK5gGR/DFKdAxdzmE4CZD60oTFcQ1xn9qqD
JHSoiKy+5kY7dKETZspKltTaOgc+zFjxMeNVGcw8zP/uiZ4FVIVkgDuRlMzibMFm
7c3FqiPhAkg/QfTxIcFI27PQ6xxD7HpYtu0dvUxpqElRaXSYxHxP7deU6ENCiFkE
XQr764FW0K8+47b20cgJ4J0wBFeMLBXJnHBHzaEWmuJtHh26fYq0ncFOlA3rD/KO
0eJakH8uSHEUaco67EVc2b+SuL/mUEaA7T0Msh7LQllPPdV+Yx6otUkJmZCcK35/
WFvnANcrXzRoT7gkVr/jSiVlYELgPzFl71bKLDInpbmUCskbZlEIH5riqOVqsH9X
+cx1x/eR4YLug6XGATCjCs3Q80Aqae8LExmjSfaN3zazXXWx4esDV2CXv6aBc281
ZcrFRmeyKr0mxT+S3YvY
=l2+a
-----END PGP SIGNATURE-----
hi
We are going to change the way the backend inventory works to
accommodate different architectures, different type of deployments and
different ways to return/teardown CI hosts.
As a result, users will no longer be able to call the /Inventory API
call for a complete state, you will need to supply your apikey for it to
return anything worthwhile.
For existing calls that already supply the apikey ( I believe the cico
client does ), there should be no change. But for anyone doing a generic
blanket call to get entire stock report, they will get an empty result set.
Is this going to impact anything anyone has in production right now ?
Regards,
--
Karanbir Singh
+44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh
GnuPG Key : http://www.karan.org/publickey.asc