Difference between revisions of "HOWTO06 How to publish the system architecture"
Line 4: | Line 4: | ||
{{TOC_right}} | {{TOC_right}} | ||
= How to | = How to publish the system architecture = | ||
== Policy == | == Policy == |
Revision as of 13:27, 22 June 2011
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Documentation menu: | Home • | Manuals • | Procedures • | Training • | Other • | Contact ► | For: | VO managers • | Administrators |
How to publish the system architecture
Policy
The GLUE attribute GlueHostArchitecturePlatformType in the SubCluster object will be used to define the system architecture. The value will be obtained from uname -m.
GlueHostArchitecturePlatformType: `uname -m`
This should be taken from the operating system installed on your batch workers. So regardless of if your machine is for instance 64bit capable you may have a 32 bit os installed and so uname -m might return i686. In this case i686 should be published. It is obviously the value that is returned on one of your batch workers and not on your CE node.
Valid Strings
If GlueHostArchitecturePlatformType is defined then it must be one of the following strings.
Example Processor | Bits for OS | GlueHostArchitecturePlatformType |
---|---|---|
Intel i386 | 32 | i386 |
Intel Pentium 4, Xeon, AMD Athlon, Opteron | 32 | i686 |
Intel Itanium | 64 | ia64 |
Intel Xeon, AMD Opteron | 64 | x86_64 |
Power PC | 32/64 | powerpc |
if you have an architecture not specified above you would like added to the acceptable list for gstat please add it here and contact roc-dev@lists.grid.sinica.edu.tw .
Up until now GlueHostArchitecturePlatformType is currently not generally advertised, it is assumed that if you are not publishing this value then your site is i3/686. However it is always advisable to explicitly publish this value. gstat will not throw an error currently if this value is not published. If your site is not i3/686 then it is a requirement that you publish your host architecture with or with out yaim as below.
Yaim Deployment
An update is required to yaim to deploy this tag: https://savannah.cern.ch/bugs/?24523. Once this is deployed we expect all sites to be publishing this tag.
Status
- 16th July 2007 this was deployed to the EGEE PPS service. Bug https://savannah.cern.ch/bugs/?28020 does not break the deployment of this tag but does make it likely that many sites may ignore that they should do it.
- 19th July 2007 a deficiency was found in lcg-info-templates on the PPS that stops it working https://savannah.cern.ch/bugs/?28166
Match Making Example
Matching Intel i[3456]86
This also matches to sites where this value is not defined. Until the yaim above is widely deployed this is all can be done. Any non-i686 sites not publishing must contacted and requested.
Requirements = other.GlueHostArchitecturePlatformType is UNDEFINED || RegExp("i[3456]86",other.GlueHostArchitecturePlatformType) ;
Matching 64 bit Xeon, Opeteron
Requirements = (other.GlueHostArchitecturePlatformType == "x86_64") ;
Matching 64bit Itanium
Requirements = (other.GlueHostArchitecturePlatformType == "ia64") ;
though today there are none so pretty useless :-)