sponsored activity that aims to address the matching and utilization of
of worker node resources within the EGEE grid.
The mandate, list of members and mailing list is available here.
A number of steps must be completed to reach a state where we support rich configuration of Glue Clusters and SubClusters. For all deployment dependencies
they are within a site or gLite release. We have no expectation that something must be deployed everywhere before we can proceed to the next step.
Key |
Item |
Development Status |
YAIM Status |
Certification Status |
Dependencies |
F |
YAIM supporting free style Clusters and SubClusters |
There is now a good attempt at this within YAIM not in the main development branch. This is documented well YAIM Cluster and I reviewed the installation recently here WNWorkingGroupInstallLog. Its a very good first attempt and all of the complexity needed is present. The items highlighted in the install log are all small fixes. Essentially another round of development process is required. |
This is all YAIM. |
Another development round needed. |
This could in principal be deployed tomorrow. But this unlikely to happen, much of the above can and should be deployed first. C should be done first though. |
E |
lcg-ManageTags and lcg-tags need to support a --cluster option |
Developers are expecting bugs from me with a request to support "--subcluster" option. We have to have publication details of the RTEPublisher finalised in B before they can have details of what to query. |
No YAIM work. |
Certification has to check not only --subcluster works but mainly that it is backwards compatible assuming that a lack of RTEpublisher for a SubCluster signifies that the SubCluster is the hostname. |
As mentioned the RTEPublisher publishing must be finalised as per B. Once done and developed can be deployed without delay. The deployment is irrelevant in the sense that sgm users will just carry on using --cehost and not --subcluster in the first instance of deployment |
D |
Infoprovider update to publish software tags per SubCluster |
Requires an update to lcg-info-dynamic-software BUG:45310 . This is the next thing I will do. |
No changes to YAIM |
Easy to certify if a little fictitious. Nothing will actually be putting tags in here at the time of deployment. |
No dependencies, can and should be deployed tomorrow. |
A |
Resolving WN to a GlueSubCluster |
Package glite-wn-info exists and can be configured to return this value. |
PATCH:2114 is submitted but is in configuration status, i.e YAIM needs to support a richer wn-list.conf file allowing per WN properties. |
Needs the updated YAIM before it can really begin. |
None, could be deployed tomorrow. |
B |
Resolving a GlueSubCluster to an RTEPublisher |
Steve Burke's has a provider for this resolution glite-info-provider-service-1.0.3-0.noarch.rpm . I reviewed it recently and gave some comments that were accepted. BUG:45313 . |
Trivial configuration, trivial addition to YAIM. New YAIM function attached on WNWorkingGroupInstallLog. |
Submitted after updates, easy to certify. |
Can be deployed now even on today's lcg-CE and would be worth while anyway before being moved with the eventual creation of the glite-CLUSTER node. Although can be deployed , effectivly not used till C is done |
C |
Creation of per SubCluster RTE Tags areas |
No development. |
Not submitted formally as a request to yaim but a trivial function that can be added to the current lcg-CE as well. Will do it. Essentially for each SubCluster create a /opt/glite/var/info/<SubCluster>/<VO> directories with sgm like permissions. |
Trivial to certify. |
As mentioned this can be done now on the lcg-CE where we know the name of the single SubCluster. However D should be deployed first so that any tags that end up in their are subsequently published as software tags in the SubCluster. |
A number of comments have already been addressed to the group that might be considered for inclusion within discussions
and outputs.
The software tags need to addressed with respect to running multiple SubClusters on the same physical host.
A test installation is being set up within the PPS.