-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 11/09/15 17:08, James O'Connor wrote:
On Sep 11, 2015, at 6:25 AM, Karanbir Singh kbsingh@centos.org wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
hi Ashish,
Fabian is putting together a VM ( or 2 if you need more ), for the BE bringup. This would be a fedora19 VM.
Fabian: Ashish has confirmed that he has all the mock configs required to bringup the CentOS 7.1406 os/ release content, then build the updates upto May 2015 content. So here is what I see happening,
- Fabian to setup a VM for ppc64 BE 2) Fabian to setup a VM for
ppc ( multilib, 32 bit ) 3) Ashish to file a bug report at bugs.centos.org to req direct access, include ssh key 4) Fabian to get Ashish setup, and get Ashish an account on the ipv4 jumphost. 5) One that is in place, Ashish to build mock itself on the machines for either 64bit or 32bit 6) Fabian to let Ashish know the mirror url for fedora19, which would be the base of the builds 7) Ashish should then be able to kick off the first bringup cycle, with mock configs he already has in place. 8) build to CentOS-7 1406 content being complete. 9) Checkpoint at this stage, to evaluate payload, build process, build delivery and workout path to automating builds from there on.
I’ve got the BE side of the house covered too or will delegate as appropriate so pass this all through s/Ashish/James/ as well.
So, I've been "off and on" on this today , and I had to fight a strange ppc64 bug with anaconda and kickstart for f19/f20. Current status is that I have kickstart working now for the f19/f20/f21 ppc64 and f21 ppc64le. So next question is how much VMs do we want/need for the initial bootstrap ? IIRC we said something like F19 ppc64/ 4Gb/40GB disk (in lvm) ? Correct me if I'm wrong . How much VMs for that ? Depending on the number of builders (threads) we'll have after that to think about common storage for repositories and so on .. but let's start "easy".
Cheers,
- -- Fabian Arrotin The CentOS Project | http://www.centos.org gpg key: 56BEC54E | twitter: @arrfab