+ 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@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@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On Wed, Sep 7, 2016 at 12:15 PM, David Moreau Simard dms@redhat.com wrote:
- 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@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
Just following up.. KB Matt Young will be changing the image building workflow at ci.centos to directly publish from the duffy nodes to the artifact server. The code is already written as we directly publish in other environments, we just need to flip a switch. We were under the impression that the duffy nodes did not have direct access to publish.
Sorry for the inconvenience.
--
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@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/09/16 23:44, Wesley Hayutin wrote:
Just following up.. KB Matt Young will be changing the image building workflow at ci.centos to directly publish from the duffy nodes to the artifact server. The code is already written as we directly publish in other environments, we just need to flip a switch. We were under the impression that the duffy nodes did not have direct access to publish.
sounds good, can you let us know once this is done ?
Sorry for the inconvenience.
no worries.
A key issue here is that we are essentially here to partner with and support the tenant's in the infra - and as we have consistently done in the past, willing to make changes even at the infra and service levels to facilitate roles and patterns.
But it would be good to have the opportunity to work with you guys on this, rather than having go in to impose limitations and restrictions as a way to rescue the service.
Regards
- -- Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc
On Thu, Sep 8, 2016 at 8:55 AM, Karanbir Singh kbsingh@centos.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 07/09/16 23:44, Wesley Hayutin wrote:
Just following up.. KB Matt Young will be changing the image building workflow at ci.centos to directly publish from the duffy nodes to the artifact server. The code is already written as we directly publish in other environments, we just need to flip a switch. We were under the impression that the duffy nodes did not have direct access to publish.
sounds good, can you let us know once this is done ?
Sorry for the inconvenience.
no worries.
A key issue here is that we are essentially here to partner with and support the tenant's in the infra - and as we have consistently done in the past, willing to make changes even at the infra and service levels to facilitate roles and patterns.
But it would be good to have the opportunity to work with you guys on this, rather than having go in to impose limitations and restrictions as a way to rescue the service.
Regards
Thanks as always KB! I think for the most part the tripleo tests in RDO can work w/o infra changes to ci.centos, I think we were caught flat footed because we were not aware of some of load issues the tripleo tests were causing. I'll make sure we have more folks on the centos mailing lists, irc and meetings to help improve the cross team communication.
Karanbir Singh, Project Lead, The CentOS Project +44-207-0999389 | http://www.centos.org/ | twitter.com/CentOS GnuPG Key : http://www.karan.org/publickey.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iQEcBAEBAgAGBQJX0V+yAAoJEI3Oi2Mx7xbtoQkH/Am6kK5nnkwG5s9qr9pao8+9 SW3jaM0VaMw4nS5uXSyMuSrF0YRLJaEFKPQuejLk5z49tmEY9tO3lO8Oy8LuzsQr ePVA+/gODjrz23ar6hWWy4AmJnu5u0K8Nwx5FGKrILAsFrP7X0vcjb8Nwt6Xi6DV te1BrEDmj0Imnk1QRpQyGQXtLWIou4kGGkZl9eZb7yZj//DdT2DcP++4PKu0Ih2N 4PlAxmoD1jVIzX+dPdA2L+o9YPGbyz1iFzQr3vyCaWkZaa2mwONhOF5CzRXChRVs JKy7TiJY2nEx8UKHX60QP8P0rz4nWJBNLDVLAqhD46bUx/mn235cU6XczaUNH6w= =S13B -----END PGP SIGNATURE-----