hi guys,
RHEL 7.2 was released a few days back and we've been busy sorting through the code and working on the downstream CentOS Linux release ( its going to likely be released in November and will be called 7.1511 ).
I'd like to make that content available on ci.centos.org ahead of public release. And there are a couple of ways to do this :
1) either we update the provisioning service, so all requests for a centos linux 7 machine will give you a 7.1511 build ( its 7.1503 at the moment ), with all the updates etc posted in sync that way. This also means that mirror.centos.org inside the ci infra will look DIFFERENT from mirror.centos.org the real users see, since it will be setup to look like the next release.
2) we make the content available in a new set of repos, called CentOS.next or something; and the ci users are able to optionally tweak their build scripts etc to include or not include these new changes.
3) we dont make this content available before its publicly released.
of all those bits, I like (1) best; (2) only delays the content from hitting the ci infra by a week or 10 days. We dont usually take longer than that from when the builds are done to when the distro update is released. (3) just means that if there are changes, failures or breakages in the ci tested code, we only find out at the same time as the users - which isnt nice.
thoughts ?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 24/11/15 00:30, Karanbir Singh wrote:
hi guys,
RHEL 7.2 was released a few days back and we've been busy sorting through the code and working on the downstream CentOS Linux release ( its going to likely be released in November and will be called 7.1511 ).
I'd like to make that content available on ci.centos.org ahead of public release. And there are a couple of ways to do this :
- either we update the provisioning service, so all requests for
a centos linux 7 machine will give you a 7.1511 build ( its 7.1503 at the moment ), with all the updates etc posted in sync that way. This also means that mirror.centos.org inside the ci infra will look DIFFERENT from mirror.centos.org the real users see, since it will be setup to look like the next release.
Not the solution I was thinking of, as that would imply we'll have an installable tree with 7.1511 content, and that's not the case. So my idea was more something like : - - provision using the http://mirror.centos.org/centos/7/ url - - add the 7.1511 pre-released and unsigned/untested content as another repo in the kickstart.
That means that new nodes provisioned with 7 will have directly newer packages installed. and we also need to enforce that repo to be available for the CI tests (kickstart can drop an additional .repo pointing to that internal temporary repo)
The issue is that because it's untested, the provisioning itself can fail (due to conflicting packages, or other issues), leading to CI tests not being able to be launched (in worst case)
I'd also like to keep the internal mirror.centos.org exactly the same as what is released and available publicly, and keep the untested/unsigned packages in another repository, so that it would be clear to see the root cause if there is a packaging issue, etc (like gluster packages - part of - available now in the 7.1511 repo)
- we make the content available in a new set of repos, called
CentOS.next or something; and the ci users are able to optionally tweak their build scripts etc to include or not include these new changes.
Yes, at least $projects actually using the CI env would be able to opt-in
- we dont make this content available before its publicly
released.
of all those bits, I like (1) best; (2) only delays the content from hitting the ci infra by a week or 10 days. We dont usually take longer than that from when the builds are done to when the distro update is released. (3) just means that if there are changes, failures or breakages in the ci tested code, we only find out at the same time as the users - which isnt nice.
thoughts ?
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab
On 24/11/15 06:37, Fabian Arrotin wrote:
On 24/11/15 00:30, Karanbir Singh wrote:
hi guys,
RHEL 7.2 was released a few days back and we've been busy sorting through the code and working on the downstream CentOS Linux release ( its going to likely be released in November and will be called 7.1511 ).
I'd like to make that content available on ci.centos.org ahead of public release. And there are a couple of ways to do this :
- either we update the provisioning service, so all requests for
a centos linux 7 machine will give you a 7.1511 build ( its 7.1503 at the moment ), with all the updates etc posted in sync that way. This also means that mirror.centos.org inside the ci infra will look DIFFERENT from mirror.centos.org the real users see, since it will be setup to look like the next release.
Not the solution I was thinking of, as that would imply we'll have an installable tree with 7.1511 content, and that's not the case. So my idea was more something like :
- provision using the http://mirror.centos.org/centos/7/ url
- add the 7.1511 pre-released and unsigned/untested content as another
repo in the kickstart.
I dont think we should put any unsigned code in here, if its not good enough to be signed, its not good enough to test stacks on, either upstream or downstream.
That means that new nodes provisioned with 7 will have directly newer packages installed. and we also need to enforce that repo to be available for the CI tests (kickstart can drop an additional .repo pointing to that internal temporary repo)
The issue is that because it's untested, the provisioning itself can fail (due to conflicting packages, or other issues), leading to CI tests not being able to be launched (in worst case)
but... surely the point of CI is also to test the platform side for the code running on it, so these failures would be welcome ?
I'd also like to keep the internal mirror.centos.org exactly the same as what is released and available publicly, and keep the untested/unsigned packages in another repository, so that it would be clear to see the root cause if there is a packaging issue, etc (like gluster packages - part of - available now in the 7.1511 repo)
When testing things, I like to know that I'm testing content the way the user is going to see it, so I know I'm testing my code, and not the mirror infra or testing specific tweaks that are irrelevant to the user side : so having mirror inside the ci infra look like a released mirror is the way to go ( imho ), otherwise people are testing exceptions.
- we make the content available in a new set of repos, called
CentOS.next or something; and the ci users are able to optionally tweak their build scripts etc to include or not include these new changes.
Yes, at least $projects actually using the CI env would be able to opt-in
opt-in yes, but its only an opt-in if there is an opt-out, in this case there isnt one - we're just getting them the content a week or so ahead of the rest of the world, so ci-users can make sure ( or atleast know! of any major issue coming up ). eg. if a major app stops working, we should make sure its not a break at our end, and if not-possible to fix, we should put that info in the release notes atleast.
regards,
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Folks,
The CR repo[1][2] is queuing up for release to the mirrors sometime today. After that happens our plan is to enable this for all CentOS 7 hosts in CI from that point on. To do this, we'll need to flush the cache of 'Ready' machines as soon as we make the change, but we expect the whole process to happen within the day.
What this means for you: - - CentOS 7 hosts will install with the CR repo enabled and provisioned with @core packages representing the content included in the upcoming 7.1511 release - - Packages with 7.1511 builds that are not included in the @core install will be available in the CR repository (enabled by default) - - CentOS 7 hosts will still present as 7.1.1503 in /etc/centos-release
This should give you an opportunity to test your projects against the upcoming release before the Core team seeds it to mirror.centos.org
I'll send updates here as we progress. As always if you have questions or comments, feel free to respond here on-list.
Cheers!
- -- Brian Stinson CentOS CI Infrastructure Team
[1]: https://wiki.centos.org/AdditionalResources/Repositories/CR [2]: https://lists.centos.org/pipermail/centos-cr-announce/
On Dec 01 12:48, Brian Stinson wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi Folks,
The CR repo[1][2] is queuing up for release to the mirrors sometime today. After that happens our plan is to enable this for all CentOS 7 hosts in CI from that point on. To do this, we'll need to flush the cache of 'Ready' machines as soon as we make the change, but we expect the whole process to happen within the day.
What this means for you:
with @core packages representing the content included in the upcoming 7.1511 release
- CentOS 7 hosts will install with the CR repo enabled and provisioned
will be available in the CR repository (enabled by default)
- Packages with 7.1511 builds that are not included in the @core install
- CentOS 7 hosts will still present as 7.1.1503 in /etc/centos-release
This should give you an opportunity to test your projects against the upcoming release before the Core team seeds it to mirror.centos.org
I'll send updates here as we progress. As always if you have questions or comments, feel free to respond here on-list.
Cheers!
Brian Stinson CentOS CI Infrastructure Team
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJWXeuUAAoJEIMGvNKzCweM97kP/0bsBP4aWZYeXhi/FJV8t9OA CGynzcr+lEMKHbZL4SIWn8WWj9DlegWBeXVD4CLNJby4WVFf/oXN1oKIy0mwOAHQ IQK3oKYwKiPE4vT2auW+mgnnt/2dF59xi5su5XVbjHpkEYBBV0ezWWfXxq3c9Fyg u+gt5rDrheetvFfzE8csarQBVXznnfEjo9DDFxNtszzGTquOwCz/qnk4dAU+pbEY NlhZRgdxMwxTSr7u/Qtbxg+9to+lUFJWVQyNe3MCdOKe4Fo4k5WDNtRqOGKQvUqK Dtu41XLW53U7FXezLK1nEW9JpxFaqcg5essuchz3LtxSQYuyM2Z67rpMH8UJIKGh ONxaiZOo+L848Qq4pck5Y0V+d+FishknIYQwmQP6USKBLL1DAEaphdhFGq1d9SHv gyg6+KZyrIt+meWivt6ah9v0O1+gMa487HTYnXFbM6TKpFfrfjK/76FaJS2jKsV8 blN6WUYSF2+EHmXsZEGImXTaj0FBlgA0roPyYVyvKxa/MPdXOYP02gQQRiktUWPu wMTOCLy4Qnx2tAfE6ghVPGr9rS+M4kvRmvXyn+UcG0dCDs5tDdP0twQpDCw1RZCN TKAkSqiRomKL+FMFfNAXGGGYx4CKyiyLlWXoi7mmiGasWXNOl5hQ8Hjqq9zAu+JS COpFDTX+LMPW7y7N0kbm =km3H -----END PGP SIGNATURE----- _______________________________________________ Ci-users mailing list Ci-users@centos.org https://lists.centos.org/mailman/listinfo/ci-users
Hi All,
This is done, we have a fresh stock of CentOS 7 + CR machines ready for testing!
If you have any trouble please let us know.
--Brian
-
Brian Stinson -
Fabian Arrotin -
Karanbir Singh