Re: ASF hosted machines - proposal
It appears that the discussion has died down on this topic. Here is the latest update with some minor changes based upon Donald's questions. I plan to send this on to the PMC in the next hour or so ... so please speak up if you think of anything additional. Thank you, Joe Rationale: The Apache Geronimo community has a need to support the execution and sharing of results from Sun certification tests (cts) which are necessary gain JavaEE5 certification compliance. This information is only available to those Geronimo committers that have signed the Sun NDA and other Apache committers that have signed an NDA and gained approval of the Apache Geronimo PMC. As such, this is becoming a resource for not only the Apache Geronimo but also other ASF projects. In the past these resource intensive tests have been run on private machines by individuals. As more people become involved with Apache Geronimo and related projects, it is becoming obvious that we need a central system to run and share the results of these tests. Request: To fulfill this requirement, the Apache Geronimo PMC is requesting the ASF infrastructure team to provide and host machines that can be used for this purpose. Initially, we would like to request two (2) machines that meet (as closely as possible) the specification below. However, we can see the need for 2 additional machines in the not too distant future. Machine specs: - 8 core (two 3.0 GHz quad-core) - 16 GB memory - two 750GB 7200 - rpm SATA 3GB/s disks - DVD R/W (20x?) - rack mountable specification to work with ASF infra requirements - LOM or other features as necessary for ASF infra support - to be developer managed and maintained by the Apache Geronimo Team - Apache Geronimo would assume all responsibility for: - configuration - backup/recovery - secure access - Strictly limited to those Apache Geronimo committers with NDAs on file or additional Apache committers with NDAs and approved by Geronimo PMC. - full, admin access would be granted to ASF infra with reboot directions - At least 2 active Apache Geronimo committers (with NDA authorization) would identified to manage the machines. - Running Linux with something like Xen for 4 VM images per machine - We would require both ssh and VNC access to the VMs. - It is not yet decided if we would use NAT to access the VMs or public IP addresses. Is there are recommendation from ASF Infra? - Automation will most likely be added to run builds, execute tests, and produce reports. - Capability to manually run tests on demand would also be supported.
Re: ASF hosted machines - proposal
Has anybody talked to Infra about virtualization environments, restrictions, guidance? Only 4 VM images? With an 8 core, I thought we'd try to allocate a VM per core... --kevan On May 19, 2008, at 1:04 PM, Joe Bohn wrote: It appears that the discussion has died down on this topic. Here is the latest update with some minor changes based upon Donald's questions. I plan to send this on to the PMC in the next hour or so ... so please speak up if you think of anything additional. Thank you, Joe Rationale: The Apache Geronimo community has a need to support the execution and sharing of results from Sun certification tests (cts) which are necessary gain JavaEE5 certification compliance. This information is only available to those Geronimo committers that have signed the Sun NDA and other Apache committers that have signed an NDA and gained approval of the Apache Geronimo PMC. As such, this is becoming a resource for not only the Apache Geronimo but also other ASF projects. In the past these resource intensive tests have been run on private machines by individuals. As more people become involved with Apache Geronimo and related projects, it is becoming obvious that we need a central system to run and share the results of these tests. Request: To fulfill this requirement, the Apache Geronimo PMC is requesting the ASF infrastructure team to provide and host machines that can be used for this purpose. Initially, we would like to request two (2) machines that meet (as closely as possible) the specification below. However, we can see the need for 2 additional machines in the not too distant future. Machine specs: - 8 core (two 3.0 GHz quad-core) - 16 GB memory - two 750GB 7200 - rpm SATA 3GB/s disks - DVD R/W (20x?) - rack mountable specification to work with ASF infra requirements - LOM or other features as necessary for ASF infra support - to be developer managed and maintained by the Apache Geronimo Team - Apache Geronimo would assume all responsibility for: - configuration - backup/recovery - secure access - Strictly limited to those Apache Geronimo committers with NDAs on file or additional Apache committers with NDAs and approved by Geronimo PMC. - full, admin access would be granted to ASF infra with reboot directions - At least 2 active Apache Geronimo committers (with NDA authorization) would identified to manage the machines. - Running Linux with something like Xen for 4 VM images per machine - We would require both ssh and VNC access to the VMs. - It is not yet decided if we would use NAT to access the VMs or public IP addresses. Is there are recommendation from ASF Infra? - Automation will most likely be added to run builds, execute tests, and produce reports. - Capability to manually run tests on demand would also be supported.
Re: ASF hosted machines - proposal
Kevan Miller wrote: Has anybody talked to Infra about virtualization environments, restrictions, guidance? I exchanged some emails with Justin Erenkrantz and asked about the VM issue. He mentioned that they had VMWare Workstation on one machine. In general, I have the impression that they aren't as concerned about the VM images/environment if we are controlling the machines. However, I suspect we'll get a better feel for that once we submit a request and see their response. Only 4 VM images? With an 8 core, I thought we'd try to allocate a VM per core... I thought about one per core but ended up with 2 just in case we need it for other related activities. This was also in line with what Matt was recommending. If we increase the # of VMs we would also need to up the memory and possibly diskspace and that really started to look excessive to me. I was just trying to give a high level description of our plans for the machines. I don't think this limits us to just 4 VMs. Perhaps instead of requesting additional machines later on we could add any additional resources to get more VMs active on the first 2 machines. --kevan On May 19, 2008, at 1:04 PM, Joe Bohn wrote: It appears that the discussion has died down on this topic. Here is the latest update with some minor changes based upon Donald's questions. I plan to send this on to the PMC in the next hour or so ... so please speak up if you think of anything additional. Thank you, Joe Rationale: The Apache Geronimo community has a need to support the execution and sharing of results from Sun certification tests (cts) which are necessary gain JavaEE5 certification compliance. This information is only available to those Geronimo committers that have signed the Sun NDA and other Apache committers that have signed an NDA and gained approval of the Apache Geronimo PMC. As such, this is becoming a resource for not only the Apache Geronimo but also other ASF projects. In the past these resource intensive tests have been run on private machines by individuals. As more people become involved with Apache Geronimo and related projects, it is becoming obvious that we need a central system to run and share the results of these tests. Request: To fulfill this requirement, the Apache Geronimo PMC is requesting the ASF infrastructure team to provide and host machines that can be used for this purpose. Initially, we would like to request two (2) machines that meet (as closely as possible) the specification below. However, we can see the need for 2 additional machines in the not too distant future. Machine specs: - 8 core (two 3.0 GHz quad-core) - 16 GB memory - two 750GB 7200 - rpm SATA 3GB/s disks - DVD R/W (20x?) - rack mountable specification to work with ASF infra requirements - LOM or other features as necessary for ASF infra support - to be developer managed and maintained by the Apache Geronimo Team - Apache Geronimo would assume all responsibility for: - configuration - backup/recovery - secure access - Strictly limited to those Apache Geronimo committers with NDAs on file or additional Apache committers with NDAs and approved by Geronimo PMC. - full, admin access would be granted to ASF infra with reboot directions - At least 2 active Apache Geronimo committers (with NDA authorization) would identified to manage the machines. - Running Linux with something like Xen for 4 VM images per machine - We would require both ssh and VNC access to the VMs. - It is not yet decided if we would use NAT to access the VMs or public IP addresses. Is there are recommendation from ASF Infra? - Automation will most likely be added to run builds, execute tests, and produce reports. - Capability to manually run tests on demand would also be supported.
Re: ASF hosted machines - proposal
By the way, I volunteer to help admin these beasts. On May 19, 2008, at 2:36 PM, Joe Bohn wrote: Kevan Miller wrote: Has anybody talked to Infra about virtualization environments, restrictions, guidance? I exchanged some emails with Justin Erenkrantz and asked about the VM issue. He mentioned that they had VMWare Workstation on one machine. In general, I have the impression that they aren't as concerned about the VM images/environment if we are controlling the machines. However, I suspect we'll get a better feel for that once we submit a request and see their response. K. Only 4 VM images? With an 8 core, I thought we'd try to allocate a VM per core... I thought about one per core but ended up with 2 just in case we need it for other related activities. This was also in line with what Matt was recommending. If we increase the # of VMs we would also need to up the memory and possibly diskspace and that really started to look excessive to me. I was just trying to give a high level description of our plans for the machines. I don't think this limits us to just 4 VMs. Perhaps instead of requesting additional machines later on we could add any additional resources to get more VMs active on the first 2 machines. OK. So, this number isn't laid in stone. We'll be tweaking to maximize our throughput and usage. --kevan On May 19, 2008, at 1:04 PM, Joe Bohn wrote: It appears that the discussion has died down on this topic. Here is the latest update with some minor changes based upon Donald's questions. I plan to send this on to the PMC in the next hour or so ... so please speak up if you think of anything additional. Thank you, Joe Rationale: The Apache Geronimo community has a need to support the execution and sharing of results from Sun certification tests (cts) which are necessary to gain JavaEE5 certification compliance. This information is only available to those Geronimo committers that have signed the Sun NDA and other Apache committers that have signed the NDA and gained approval of the Apache Geronimo PMC. As such, this is becoming a resource for not only the Apache Geronimo but also other ASF projects. Not sure what is meant by the last sentence. In the past these resource intensive tests have been run on private machines by individuals. As more people become involved with Apache Geronimo and related projects, it is becoming obvious that we need a central system to run and share the results of these tests. A centralized testing environment allows the Geronimo community to more fully participate in the TCK process. Some committers don't have access to the hardware resources needed to run the Java EE TCK tests in a timely manner. Although some ad-hoc sharing of private machines has occurred, this is not ideal from a community perspective. Community controlled systems allow us to equitably share these resources. --kevan Request: To fulfill this requirement, the Apache Geronimo PMC is requesting the ASF infrastructure team to provide and host machines that can be used for this purpose. Initially, we would like to request two (2) machines that meet (as closely as possible) the specification below. However, we can see the need for 2 additional machines in the not too distant future. Machine specs: - 8 core (two 3.0 GHz quad-core) - 16 GB memory - two 750GB 7200 - rpm SATA 3GB/s disks - DVD R/W (20x?) - rack mountable specification to work with ASF infra requirements - LOM or other features as necessary for ASF infra support - to be developer managed and maintained by the Apache Geronimo Team - Apache Geronimo would assume all responsibility for: - configuration - backup/recovery - secure access - Strictly limited to those Apache Geronimo committers with NDAs on file or additional Apache committers with NDAs and approved by Geronimo PMC. - full, admin access would be granted to ASF infra with reboot directions - At least 2 active Apache Geronimo committers (with NDA authorization) would identified to manage the machines. - Running Linux with something like Xen for 4 VM images per machine - We would require both ssh and VNC access to the VMs. - It is not yet decided if we would use NAT to access the VMs or public IP addresses. Is there are recommendation from ASF Infra? - Automation will most likely be added to run builds, execute tests, and produce reports. - Capability to manually run tests on demand would also be supported.
Re: ASF hosted machines - proposal
Kevan Miller wrote: By the way, I volunteer to help admin these beasts. On May 19, 2008, at 2:36 PM, Joe Bohn wrote: Kevan Miller wrote: Has anybody talked to Infra about virtualization environments, restrictions, guidance? I exchanged some emails with Justin Erenkrantz and asked about the VM issue. He mentioned that they had VMWare Workstation on one machine. In general, I have the impression that they aren't as concerned about the VM images/environment if we are controlling the machines. However, I suspect we'll get a better feel for that once we submit a request and see their response. K. Only 4 VM images? With an 8 core, I thought we'd try to allocate a VM per core... I thought about one per core but ended up with 2 just in case we need it for other related activities. This was also in line with what Matt was recommending. If we increase the # of VMs we would also need to up the memory and possibly diskspace and that really started to look excessive to me. I was just trying to give a high level description of our plans for the machines. I don't think this limits us to just 4 VMs. Perhaps instead of requesting additional machines later on we could add any additional resources to get more VMs active on the first 2 machines. OK. So, this number isn't laid in stone. We'll be tweaking to maximize our throughput and usage. right --kevan On May 19, 2008, at 1:04 PM, Joe Bohn wrote: It appears that the discussion has died down on this topic. Here is the latest update with some minor changes based upon Donald's questions. I plan to send this on to the PMC in the next hour or so ... so please speak up if you think of anything additional. Thank you, Joe Rationale: The Apache Geronimo community has a need to support the execution and sharing of results from Sun certification tests (cts) which are necessary to gain JavaEE5 certification compliance. This information is only available to those Geronimo committers that have signed the Sun NDA and other Apache committers that have signed the NDA and gained approval of the Apache Geronimo PMC. As such, this is becoming a resource for not only the Apache Geronimo but also other ASF projects. Not sure what is meant by the last sentence. The meaning is that running, managing, and sharing the test harness, systems, and test results is beneficial to several Apache projects. Certainly Geronimo is still the primary beneficiary but since we have opened our test harness and results to other apache projects Geronimo is not the sole beneficiary. I thought that highlighting this collaborative effort would improve our chances of getting the machines. In the past these resource intensive tests have been run on private machines by individuals. As more people become involved with Apache Geronimo and related projects, it is becoming obvious that we need a central system to run and share the results of these tests. A centralized testing environment allows the Geronimo community to more fully participate in the TCK process. Some committers don't have access to the hardware resources needed to run the Java EE TCK tests in a timely manner. Although some ad-hoc sharing of private machines has occurred, this is not ideal from a community perspective. Community controlled systems allow us to equitably share these resources. Good words ... I'll add this. --kevan Request: To fulfill this requirement, the Apache Geronimo PMC is requesting the ASF infrastructure team to provide and host machines that can be used for this purpose. Initially, we would like to request two (2) machines that meet (as closely as possible) the specification below. However, we can see the need for 2 additional machines in the not too distant future. Machine specs: - 8 core (two 3.0 GHz quad-core) - 16 GB memory - two 750GB 7200 - rpm SATA 3GB/s disks - DVD R/W (20x?) - rack mountable specification to work with ASF infra requirements - LOM or other features as necessary for ASF infra support - to be developer managed and maintained by the Apache Geronimo Team - Apache Geronimo would assume all responsibility for: - configuration - backup/recovery - secure access - Strictly limited to those Apache Geronimo committers with NDAs on file or additional Apache committers with NDAs and approved by Geronimo PMC. - full, admin access would be granted to ASF infra with reboot directions - At least 2 active Apache Geronimo committers (with NDA authorization) would identified to manage the machines. - Running Linux with something like Xen for 4 VM images per machine - We would require both ssh and VNC access to the VMs. - It is not yet decided if we would use NAT to access the VMs or public IP addresses. Is there are recommendation from ASF Infra? - Automation will most likely be added to run builds, execute tests, and produce reports. - Capability to manually run tests on demand would also be
Re: ASF hosted machines - proposal
I had posted this proposal on the PMC list when Kevan pointed out that we should really seek PMC approval on the dev list for this item. Below is an updated version of the proposal. It incorporates Kevan's most recent comments. What is the best way to gain PMC approval on the dev list? A vote is the only thing I can think of ... any other suggestions? Rationale: The Apache Geronimo community has a need to support the execution and sharing of results from Sun certification tests (cts) which are necessary gain JavaEE5 certification compliance. This information is only available to those Geronimo committers that have signed the Sun NDA and other Apache committers that have signed an NDA and gained approval of the Apache Geronimo PMC. In the past these resource intensive tests have been run on private machines by individuals. As more people become involved with Apache Geronimo and related projects, it is becoming obvious that we need a central system to run and share the results of these tests. A centralized testing environment allows the Geronimo community to more fully participate in the TCK process. Some committers don't have access to the hardware resources needed to run the Java EE TCK tests in a timely manner. Although some ad-hoc sharing of private machines has occurred, this is not ideal from a community perspective. Community controlled systems allow us to equitably share these resources. Request: To fulfill this requirement, the Apache Geronimo PMC is requesting the ASF infrastructure team to provide and host machines that can be used for this purpose. Initially, we would like to request two (2) machines that meet (as closely as possible) the specification below. However, we can see the need for 2 additional machines in the not too distant future. Machine specs: - 8 core (two 3.0 GHz quad-core) - 16 GB memory - two 750GB 7200 - rpm SATA 3GB/s disks - DVD R/W (20x?) - rack mountable specification to work with ASF infra requirements - LOM or other features as necessary for ASF infra support - to be developer managed and maintained by the Apache Geronimo Team - Apache Geronimo would assume all responsibility for: - configuration - backup/recovery - secure access - Strictly limited to those Apache Geronimo committers with NDAs on file or additional Apache committers with NDAs and approved by Geronimo PMC. - full, admin access would be granted to ASF infra with reboot directions - At least 2 active Apache Geronimo committers (with NDA authorization) would identified to manage the machines. - Running Linux with something like Xen for 4 VM images per machine. We may increase the number of VM images if it is feasible. - We would require both ssh and VNC access to the VMs. - It is not yet decided if we would use NAT to access the VMs or public IP addresses. Is there are recommendation from ASF Infra? - Automation will most likely be added to run builds, execute tests, and produce reports. - Capability to manually run tests on demand would also be supported.
Re: ASF hosted machines - proposal
On May 19, 2008, at 10:32 PM, Joe Bohn wrote: I had posted this proposal on the PMC list when Kevan pointed out that we should really seek PMC approval on the dev list for this item. Below is an updated version of the proposal. It incorporates Kevan's most recent comments. What is the best way to gain PMC approval on the dev list? A vote is the only thing I can think of ... any other suggestions? Call a vote on it. A few final suggestions... Rationale: The Apache Geronimo community has a need to support the execution and sharing of results from Sun certification tests (cts) which are necessary gain JavaEE5 certification compliance. This information is only available to those Geronimo committers that have signed the Sun NDA and other Apache committers that have signed an NDA and gained approval of the Apache Geronimo PMC. This has allowed other projects to test new products/releases by running JavaEE 5 TCK tests using the Geronimo test infrastructure. In the past these resource intensive tests have been run on private machines by individuals. As more people become involved with Apache Geronimo and related projects, it is becoming obvious that we need a central system to run and share the results of these tests. A centralized testing environment allows the Geronimo community to more fully participate in the TCK process. Some committers don't have access to the hardware resources needed to run the Java EE TCK tests in a timely manner. Although some ad-hoc sharing of private machines has occurred, this is not ideal from a community perspective. Community controlled systems allow us to equitably share these resources. Request: To fulfill this requirement, the Apache Geronimo PMC is requesting the ASF infrastructure team to provide and host machines that can be used for this purpose. Initially, we would like to request two (2) machines that meet (as closely as possible) the specification below. However, we can see the need for 2 additional machines in the not too distant future. Machine specs: - 8 core (two 3.0 GHz quad-core) - 16 GB memory - two 750GB 7200 - rpm SATA 3GB/s disks - DVD R/W (20x?) - rack mountable specification to work with ASF infra requirements - LOM or other features as necessary for ASF infra support - to be developer managed and maintained by the Apache Geronimo Team - Apache Geronimo would assume all responsibility for: - configuration - backup/recovery - secure access - Strictly limited to those Apache Geronimo committers with NDAs on file or additional Apache committers with NDAs and approved by Geronimo PMC. - full, admin access would be granted to ASF infra with reboot directions - At least 2 active Apache Geronimo committers (with NDA authorization) would identified to manage the machines. - Running Linux with something like Xen for 4 VM images per machine. We may increase the number of VM images if it is feasible. - We would require both ssh and VNC access to the VMs. - It is not yet decided if we would use NAT to access the VMs or public IP addresses. Is there are recommendation from ASF Infra? - Automation will most likely be added to run builds, execute tests, and produce reports. - Capability to manually run tests on demand would also be supported. Admin Volunteers: - Joe Bohn (PMC) - Jay McHugh (PMC) - Jason Warner - Matt Hogstrom (PMC) - Kevan Miller (PMC) --kevan
ASF hosted machines - proposal
Here is a proposal for the ASF hosted machines to run TCK. Please let me know if you think changes necessary. Once we get it to a state that we agree upon, I will forward it to the Geronimo PMC for further approval and for the PMC to make the request to ASF infra. It would be great if we could get this to the PMC by Monday, 5/19. Rational: The Apache Geronimo community has a need to support the execution and sharing of results from Sun certification tests (cts) which are necessary gain JavaEE5 certification compliance. This information is only available to those Geronimo committers that have signed the Sun NDA and other Apache committers that have signed an NDA and gained approval of the Apache Geronimo PMC. As such, this is becoming a resource for not only the Apache Geronimo but also other ASF projects. In the past these resource intensive tests have been run on private machines by individuals. As more people become involved with Apache Geronimo and related projects, it is becoming obvious that we need a central system to run and share the results of these tests. Request: To fulfill this requirement, the Apache Geronimo PMC is requesting the ASF infrastructure team to provide and host machines that can be used for this purpose. Initially, we would like to request two (2) machines that meet (as closely as possible) the specification below. However, we can see the need for 2 additional machines in the not too distant future. Machine specs: - 8 core (two 3.0 GHz quad-core) - 16 GB memory - two 750GB 7200 - rpm SATA 3GB/s disks - DVD R/W (20x?) - rack mountable specification to work with ASF infra requirements - LOM or other features as necessary for ASF infra support - to be developer managed and maintained by the Apache Geronimo Team - Apache Geronimo would assume all responsibility for: - configuration - backup/recovery - secure access - Strictly limited to those Apache Geronimo committers with NDAs on file or additional Apache committers with NDAs and approved by Geronimo PMC. - full, admin access would be granted to ASF infra with reboot directions - At least 2 active Apache Geronimo committers (with NDA authorization) would identified to manage the machines. - Running Linux with something like Xen for 4 VM images per machine - Automation will most likely be added to run builds, execute tests, and produce reports. - Capability to manually run tests on demand would also be supported. Joe
Re: ASF hosted machines - proposal
Joe, thanks for pulling this together. Just a couple more questions - For the vm images, do we want them behind a NAT or using public IP addresses, with the later being important in the request due to an additional infrastructure requirement... Do we need to mention any network bandwidth requirements or projected download/upload amounts? Also, do we want VNC access to the host and guest systems, or only access them via ssh? -Donald Joe Bohn wrote: Here is a proposal for the ASF hosted machines to run TCK. Please let me know if you think changes necessary. Once we get it to a state that we agree upon, I will forward it to the Geronimo PMC for further approval and for the PMC to make the request to ASF infra. It would be great if we could get this to the PMC by Monday, 5/19. Rational: The Apache Geronimo community has a need to support the execution and sharing of results from Sun certification tests (cts) which are necessary gain JavaEE5 certification compliance. This information is only available to those Geronimo committers that have signed the Sun NDA and other Apache committers that have signed an NDA and gained approval of the Apache Geronimo PMC. As such, this is becoming a resource for not only the Apache Geronimo but also other ASF projects. In the past these resource intensive tests have been run on private machines by individuals. As more people become involved with Apache Geronimo and related projects, it is becoming obvious that we need a central system to run and share the results of these tests. Request: To fulfill this requirement, the Apache Geronimo PMC is requesting the ASF infrastructure team to provide and host machines that can be used for this purpose. Initially, we would like to request two (2) machines that meet (as closely as possible) the specification below. However, we can see the need for 2 additional machines in the not too distant future. Machine specs: - 8 core (two 3.0 GHz quad-core) - 16 GB memory - two 750GB 7200 - rpm SATA 3GB/s disks - DVD R/W (20x?) - rack mountable specification to work with ASF infra requirements - LOM or other features as necessary for ASF infra support - to be developer managed and maintained by the Apache Geronimo Team - Apache Geronimo would assume all responsibility for: - configuration - backup/recovery - secure access - Strictly limited to those Apache Geronimo committers with NDAs on file or additional Apache committers with NDAs and approved by Geronimo PMC. - full, admin access would be granted to ASF infra with reboot directions - At least 2 active Apache Geronimo committers (with NDA authorization) would identified to manage the machines. - Running Linux with something like Xen for 4 VM images per machine - Automation will most likely be added to run builds, execute tests, and produce reports. - Capability to manually run tests on demand would also be supported. Joe smime.p7s Description: S/MIME Cryptographic Signature
Re: ASF hosted machines - proposal
Good points Donald ... comments inline Donald Woods wrote: Joe, thanks for pulling this together. Just a couple more questions - For the vm images, do we want them behind a NAT or using public IP addresses, with the later being important in the request due to an additional infrastructure requirement... I'm not well versed the advantages/disadvantages for these .. but I suspect NAT is better. comments? Do we need to mention any network bandwidth requirements or projected download/upload amounts? I'm sure that would be beneficial but I have no idea how to go about quantifying this. ideas? Perhaps we should just see if they inquire more about this. Also, do we want VNC access to the host and guest systems, or only access them via ssh? I think VNC would be beneficial. There are some tests that we've been running via the UI so if we want to run those tests on these machines it would be essential. I've added it below. -Donald Joe Bohn wrote: Here is a proposal for the ASF hosted machines to run TCK. Please let me know if you think changes necessary. Once we get it to a state that we agree upon, I will forward it to the Geronimo PMC for further approval and for the PMC to make the request to ASF infra. It would be great if we could get this to the PMC by Monday, 5/19. Rational: The Apache Geronimo community has a need to support the execution and sharing of results from Sun certification tests (cts) which are necessary gain JavaEE5 certification compliance. This information is only available to those Geronimo committers that have signed the Sun NDA and other Apache committers that have signed an NDA and gained approval of the Apache Geronimo PMC. As such, this is becoming a resource for not only the Apache Geronimo but also other ASF projects. In the past these resource intensive tests have been run on private machines by individuals. As more people become involved with Apache Geronimo and related projects, it is becoming obvious that we need a central system to run and share the results of these tests. Request: To fulfill this requirement, the Apache Geronimo PMC is requesting the ASF infrastructure team to provide and host machines that can be used for this purpose. Initially, we would like to request two (2) machines that meet (as closely as possible) the specification below. However, we can see the need for 2 additional machines in the not too distant future. Machine specs: - 8 core (two 3.0 GHz quad-core) - 16 GB memory - two 750GB 7200 - rpm SATA 3GB/s disks - DVD R/W (20x?) - rack mountable specification to work with ASF infra requirements - LOM or other features as necessary for ASF infra support - to be developer managed and maintained by the Apache Geronimo Team - Apache Geronimo would assume all responsibility for: - configuration - backup/recovery - secure access - Strictly limited to those Apache Geronimo committers with NDAs on file or additional Apache committers with NDAs and approved by Geronimo PMC. - full, admin access would be granted to ASF infra with reboot directions - At least 2 active Apache Geronimo committers (with NDA authorization) would identified to manage the machines. - Running Linux with something like Xen for 4 VM images per machine - We would require both ssh and VNC access to the VMs. - Automation will most likely be added to run builds, execute tests, and produce reports. - Capability to manually run tests on demand would also be supported. Joe
