The SGE service uses two disk templates, one for VMMaster and another for VMExecutor The SGE service consisers one internal network (sge_net) and one pubilc (admin_net) Network to connect service components (VMMaster and VMExecutors) Network to provide administrative access to VMMaster SGE only uses one KPI: the length of the jobs queue There are two elasticity rules, to scale up and down VMExecutor components ScaleUp ScaleDown The SGE service is composed by two types of VMs, VMMaster and VMExecutor VMMaster has to be booted before any VMExecutor Product customization for the installed master software SGE Master 1.0 Product customization for the installed executor software SGE Executor 1.0 Master VM description Virtual Hardware Requirements: 512Mb, 2 CPU, 1 disk, 1 nic Virtual Hardware Family 0 vmx-4 Number of virtual CPUs 2 virtual CPU 1 3 2 MegaBytes Memory Size 512 MB of memory 2 4 512 true sge_net Ethernet adapter on sge_net network 3 10 true admin_net Ethernet adapter on admin_net network 3 10 Harddisk 1 ovf://disk/master 5 4 17 Executor VM description Virtual Hardware Requirements: 256Mb, 1 CPU, 1 disk, 1 nic Virtual Hardware Family 0 vmx-4 Number of virtual CPUs 1 virtual CPU 1 3 1 MegaBytes Memory Size 256 MB of memory 2 4 256 true service_network Ethernet adapter on sge_net network 3 10 Harddisk 1 ovf://disk/execution 5 4 17