hi,
On the 31st Jan, we hosted a CentOS Cloud Instance hackathon at the CentOS Dojo @ IBM Forum, brussels.
We had contributions from the redhat openstack team, the cloudstack people, hpcloud, opennebula and the xen crew. Apart from getting the base images done for these, we also had a few docker images built, xen-pv and xen=hvm images for xen4centos and as a final bonus towards the end of the day, I was able to update tooling to build all of the above against the rhel7beta tree ( the actual instance building work was all being done against centos-6/x86_64 only ).
All in all, I closed the day with 84 attempts ( of which 57 were successful ).
During the hack session, everyone was targetting, as had been planned really - a common cloud-init package. Before I start pushing the content up publicly and upload the images done in the session, it would be good to have the conversation around cloud-init. Are we going to keep consuming it from EPEL ? which is hard and tricky, or are we going to pull it into a centos.org repo ( Extras/ seems like a good target, for base common stuff ). And if we do pull it in, how are we going to keep in sync with EPEL ( and maybe other repos ) so we dont end up ver-rel thrashing at updates time.
For the sake of completeness, the AWS images for 6.5 I've pushed yesterday ( Wed 5th ) are as the 6.4 ones ( i.e. no cloud-init ).
Finally, to everyone there at the hackathon, I apologise for the rater poor network conditions. Its something I will try and fix for the next time.
- KB
On 02/06/2014 05:12 PM, Karanbir Singh wrote:
During the hack session, everyone was targetting, as had been planned really - a common cloud-init package. Before I start pushing the content up publicly and upload the images done in the session, it would be good to have the conversation around cloud-init. Are we going to keep consuming it from EPEL ? which is hard and tricky, or are we going to pull it into a centos.org repo ( Extras/ seems like a good target, for base common stuff ). And if we do pull it in, how are we going to keep in sync with EPEL ( and maybe other repos ) so we dont end up ver-rel thrashing at updates time.
in some regards, this conversation becomes easier, when working under the constraint that we need to have it hosted out of a centos.org repo in order to use it for CentOS images.
On Thu, Feb 6, 2014 at 7:40 PM, Karanbir Singh mail-lists@karan.org wrote:
On 02/06/2014 05:12 PM, Karanbir Singh wrote:
During the hack session, everyone was targetting, as had been planned really - a common cloud-init package. Before I start pushing the content up publicly and upload the images done in the session, it would be good to have the conversation around cloud-init. Are we going to keep consuming it from EPEL ? which is hard and tricky, or are we going to pull it into a centos.org repo ( Extras/ seems like a good target, for base common stuff ). And if we do pull it in, how are we going to keep in sync with EPEL ( and maybe other repos ) so we dont end up ver-rel thrashing at updates time.
in some regards, this conversation becomes easier, when working under the constraint that we need to have it hosted out of a centos.org repo in order to use it for CentOS images.
Why can't we consume directly from EPEL? There are a few additional EPEL packages that would have to be pulled in to support growing of the root partition. If I'm not mistaken, those would only be required for CentOS 5+6 and shouldn't be necessary for CentOS 7.
...Juerg
-- 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 http://lists.centos.org/mailman/listinfo/centos-devel
On 02/10/2014 08:46 AM, Juerg Haefliger wrote:
Why can't we consume directly from EPEL? There are a few additional EPEL packages that would have to be pulled in to support growing of the root partition. If I'm not mistaken, those would only be required for CentOS 5+6 and shouldn't be necessary for CentOS 7.
the buildsystem does not have internet access, so cant pull from external places, but beyond that its mostly a case of co-ordinating the versions with what we are doing here, if we can get to a point where we know for sure that EPEL wont update / change stuff till tests in centos images pass, then we could just do a binary mirror for the content; otherwise we're going to need to have the cloud-init code locally hosted in git.centos.org
- KB
-
Juerg Haefliger -
Karanbir Singh