Hi Kristian,
I have lost track of where this issue is. Are you happy with solution
(1) or do you still need a solaris zone on an Apache machine? If you
still need a zone, can you give me some justification--I think that I
will be asked why (1) isn't sufficient. It's ok to say "I don't know,
I'm running some experiments, I'll get back to you." I just want to make
sure that I'm not letting this issue fall through the cracks.
Thanks,
-Rick
Rick Hillegas wrote:
There seem to be two proposals on the table:
1) Conscript existing ASF build infrastructure for some of our
automated builds (including the docs build): http://ci.apache.org/
2) Request additional build resources for the db PMC:
http://www.apache.org/dev/solaris-zones.html#establish
(1) seems to be very simple. Anyone can request an account and start
migrating our automated builds. Is there some reason that (1) is not
sufficient for our needs?
Thanks,
-Rick
Andrew McIntyre wrote:
On Mon, Jun 8, 2009 at 8:54 AM, Kristian
Waagan<[email protected]> wrote:
The first step would involve at least the following steps:
1) Obtain a Solaris zone.
2) Agree on who should have access to the zone (PMC chair will be the
initial owner).
I don't understand why the PMC chair needs to be so heavily
involved. I
can promise you that this PMC chair will pass the responsibility
onto more
knowledgeable people in a New York minute!
I think this is ASF policy, but I'll check if it has to be the PMC
chair or
just a PMC member.
If the chair has to do anything, I expect it will only be
formalities and
I'll help you out as much as I can.
The PMC chair needs to request a zone from infrastructure:
http://www.apache.org/dev/solaris-zones.html#establish
Once that is done, the PMC chair becomes the root user of the zone and
can then add other users.
FYI, for builds, besides a zone there are now several options for
continuous builds at Apache, see:
http://ci.apache.org/
I might have a little time to help with setup once the zone has been
created. Let me know.
Thanks,
andrew
