100 likes | 259 Views
GPGPUs: GLUE schema support. Stephen Burke egi.eu EGI CF April 10 th 2013. Overview. GLUE 1 GLUE 2 Configuration/info providers. GLUE 1. Rather limited possibilities Main object is GlueSubCluster RunTimeEnvironment tag ArchitecturePlatformType , ProcessorModel
E N D
GPGPUs: GLUE schema support Stephen Burke egi.eu EGI CF April 10th 2013
Overview • GLUE 1 • GLUE 2 • Configuration/info providers GPGPUs in GLUE - EGI CF
GLUE 1 • Rather limited possibilities • Main object is GlueSubCluster • RunTimeEnvironment tag • ArchitecturePlatformType, ProcessorModel • Usually CPU, could append GPU • Risk of breaking existing use • ProcessorOtherDescription • String, already overloaded • CECapability • If a batch queue has special properties GPGPUs in GLUE - EGI CF
SubCluster attributes • ProcessorModel: Processor model as defined by the vendor • ProcessorVersion: Processor version • ProcessorVendor: Name of the processor vendor • ProcessorClockSpeed: MHz The clock speed • ProcessorInstructionSet: The processor instruction set; use comma-separated values (e.g.: mmx,cisc) • ProcessorOtherDescription: Other description for the processor • ArchitecturePlatformType: Platform type of the host • ArchitectureSMPSize: number of physical CPUs in the host • BenchmarkSI00: SpecInt2000 • BenchmarkSF00: SpecFloat2000 GPGPUs in GLUE - EGI CF
GLUE 2 • Equivalent to SubCluster is ExecutionEnvironment • Nothing specific to GPUs, but can add arbitrary OtherInfo attributes • Add GPU info to the standard EE object? • Or define a new GPU-specific one? • Would need to take care that it doesn’t break WMS matching, but GLUE 2 matching is new anyway GPGPUs in GLUE - EGI CF
ExecutionEnvironment attributes • Platform: The platform architecture of this Execution Environment. • CPUVendor: The name of the physicalCPU vendor. Free format, but it SHOULD correspond to the name by which the vendor is generally known. • CPUModel: The name of the physicalCPU model, as defined by the vendor. • CPUVersion: The specific version of the PhysicalCPU model, as defined by the vendor. • CPUClockSpeed: The nominal clock speed of the physical CPU. • MainMemorySize: The total amount of physical RAM in one Execution Environment instance; if many jobs run in the same instance they compete for the total RAM. • VirtualMemorySize: MB The total amount of virtual memory (RAM plus swap space) in one ExecutionEnvironment instance. GPGPUs in GLUE - EGI CF
GLUE 2 extension • Possible to define new attributes or objects, but: • Would need to get agreement in GLUE WG • Deployment could take a long time • But not so bad if it’s only a small number of sites? • Top BDIIs would need the upgraded schema first GPGPUs in GLUE - EGI CF
Configuration • All attributes are currently static • Configured by a yaim function • Difficult to publish dynamic information • Publication from a CE or Cluster node, not a WN • Could have a cron job to collect info on a typical WN, copy to Cluster node GPGPUs in GLUE - EGI CF
Summary • GLUE schema not defined with GPUs in mind • GLUE 1 has limited scope and is no longer developed • GLUE 2 has somewhat more flexibility and can potentially be extended • Dynamic information is somewhat difficult • How soon can we decide what’s needed? GPGPUs in GLUE - EGI CF
References • GLUE 1: • https://forge.cnaf.infn.it/plugins/scmsvn/viewcvs.php/*checkout*/v_1_3/spec/draft-2/pdf/GLUESchema.pdf?rev=24&root=glueschema • GLUE 2: • http://glue20.web.cern.ch/glue20/ • http://forge.ogf.org/sf/go/doc15519?nav=1 • WMS matching for GLUE 2 • https://wiki.italiangrid.it/twiki/bin/view/WMS/WMS34ExtendedReleaseNotes GPGPUs in GLUE - EGI CF