Home

Cloudbursting Manual - Support

1. 0 0 0 0 0000 ee eee 48 5 4 1 Resolution And globalnet 0 0 0000 eee ee ee 48 5 4 2 Resolution In And Out Of The Cloud 0 0 00 0 00002 bee 49 6 Virtual Private Clouds 51 6 1 EC2 Classic And EC2 VPC 2 ee 51 6 1 1 EC2 Classic Vs EC2 VPC Overview 2 0 0 a 51 6 1 2 EC2 Classic Vs EC2 VPC And AWS Account Creation Date 52 6 1 3 The Classic Cloud And The DefaultVPC Instances 0 000048 52 6 1 4 The Private Cloud And Custom VPC Instances 2 0 000008 52 6 1 5 Cloud Cluster Terminology Summary 2 2 e 53 6 2 Comparison Of EC2 Classic And EC2 VPC Platforms 00 0000 53 6 3 Setting Up And Creating A Custom VPC 1 2 aaa 53 6 3 1 SubnetsIn A Custom VPC aoaaa aaa ee 54 6 3 2 Creating The Custom VPC 1 2 es 54 6 3 3 Elastic IP Addresses And Their Use In Configuring Static IP Addresses 56 6 3 4 Subnets With Static IP Addresses In A Custom VPC Recommendation 57 6 3 5 Assignment Of Nodes To Subnets And Cloud Platforms 57 6 3 6 Creating A Cloud Director In A Custom VPC aaa 0000 0 ee eee 58 6 3 7 Creating Cloud Compute nodes In A Custom VPC 0 00000 58 6 3 8 Moving Existing Nodes To A Custom VPC 2 0 0 0 0 00000008 58 Preface Welcome to the Cloudbursting Manual for Bright Cluster Manager 7 1 0 1 About This Manual This manual is aimed at helping cluster administrators install understand configur
2. Bright Cluster Manager 7 1 Cloudbursting Manual Revision 6823 Date Thu 10 Dec 2015 Bright Computing 2015 Bright Computing Inc All Rights Reserved This manual or parts thereof may not be reproduced in any form unless permitted by contract or by written permission of Bright Computing Inc Trademarks Linux is a registered trademark of Linus Torvalds PathScale is a registered trademark of Cray Inc Red Hat and all Red Hat based trademarks are trademarks or registered trademarks of Red Hat Inc SUSE is a registered trademark of Novell Inc PGI is a registered trademark of NVIDIA Corporation FLEXIm is a registered trademark of Flexera Software Inc ScaleMP is a registered trademark of ScaleMP Inc All other trademarks are the property of their respective owners Rights and Restrictions All statements specifications recommendations and technical information contained herein are current or planned as of the date of publication of this document They are reliable as of the time of this writing and are presented without warranty of any kind expressed or implied Bright Computing Inc shall not be liable for technical or editorial errors or omissions which may occur in this document Bright Computing Inc shall not be liable for any damages resulting from the use of this document Limitation of Liability and Damages Pertaining to Bright Computing Inc The Bright Cluster Manager product principally consists of free so
3. Iceweasel 9o06 File Edit View History Bookmarks Tools Help I EC2 Management Console db S https console aws 2 v2 home region eu west 1 LaunchinstanceWizard RY Google Q Services v Edit Irelandy Help v 1 Choose AMI 2 Choose Instance Type 3 Configure Instance 4 Add Storage 5 Tag Instance 6 Configure Security Group 7 Review Step 1 Choose an Amazon Machine Image AMI Cancel and Exit An AMI is a template that contains the software configuration operating system application server and applications required to launch your instance You can select an AMI provided by AWS our user community or the AWS Marketplace or you can select one of your own AMIs Quick Start is Amazon Linux AMI 2013 09 1 ami c7ec0eb0 64 bit ami efecOe98 select My AMIs 32 bit Amazon Linux 64 bit O 32 bit ACEEA The Amazon Linux AMI is an EBS backed PV GRUB image It includes Linux 3 4 AWS Marketplace Is y S S AWS tools and repository access to multiple versions of MySQL PostgreSQL Python Ruby and Tomcat Community AMIs Root device type ebs Virtualization type paravirtual OFree tier only G Q Red Hat Enterprise Linux 6 4 ami 75342c01 64 bit ami 8b332bff 32 bit Red Hat e Red Hat Enterprise Linux version 6 4 EBS boot 64 bit O32 bit Rant davina tuna ahe__ Mirtualizatinn tune naranirt ial 2008 2013 Amazon Web Services Inc or its affiliates All rights reserved Privacy Policy Terms of Use Feedback O7 X Figu
4. The Bright Cluster Manager software itself also follows this convention In this chapter of the manual 6 however using the term private cloud for this is avoided and the terms are adhered to precisely as defined in order to avoid confusion Attempting to change a defaultVPC instance to a custom VPC instance by editing default VPC prop erties directly with Bright Cluster Manager is not possible because these properties are hidden behind the EC2 Classic facade This kind of change can be done via the Amazaon Webconsole instead If Bright Cluster Manager requires that the custom VPC functionality of a general VPC instance is needed in Amazon VPC then a custom VPC has to be created within Bright Cluster Manager How to do this is described in section 6 3 6 1 5 Cloud Cluster Terminology Summary The cluster terminology used so far can be summarized as follows cluster term platform type and connectivity classic cloud EC2 Classic classic cloud cluster that has direct connectivity to the outside a VPC that looks like it has direct connectivity to the outside because defaultVPC Eee it emulates a classic cloud cluster isolated VPC with no connectivity to the outside by default and Suton VE eG NAT gateway connectivity to the outside when made to connect private cloud EC2 VPC both defaultVPC and custom VPC 6 2 Comparison Of EC2 Classic And EC2 VPC Platforms There are several differences between EC2 Classic and EC2
5. cloud director node for that particular custome VPC is assigned An alternative solution to creating cloud compute nodes in a custom VPC is to instruct the cluster manager to automatically move the existing ones while also moving the cloud director to the custom VPC as explained in the following section 6 3 8 Moving Existing Nodes To A Custom VPC After a custom VPC has been configured it is possible to automatically reconfigure the existing cloud nodes to make them start inside that custom VPC This is an alternative to creating new nodes inside the custom VPC from scratch An existing cloud director can be moved to a custom VPC cloud using the Move Cloud Director button in cmgui This button can be clicked in the Overview tab of a cloud provider account and it opens up a dialog box After completion of the dialog the cloud director is moved to a custom VPC in the same region It can also move any other cloud compute nodes managed by the selected cloud director Moving a node to a custom VPC effectively terminates the current EC2 instance and creates a new one inside the target custom VPC Bright Computing Inc
6. 172 21 255 251 Figure 3 7 Setting The Tunnel Network Interface For The Cloud Director s With cmgui On clicking the Next button the configuration is processed The next screen figure 3 8 displays the proposed assignment of IP addresses in the NetMap net work These can be changed from the suggested defaults but should be consistent with the addressing schemes already defined Bright Computing Inc 28 Cluster Extension Cloudbursting It is recommended that all local devices are assigned IP address in the NetMap network The table below contains a list of all local devices with their proposed NetMap IP The values in the NetMap column may be modified at this stage if desired Removing a device from the list below will cause it not to be assigned an IP address in the NetMap range Hostname NetMap IP bright 60 172 31 255 2454 node001 L72 31 0 1 node002 L324 31 0 2 Cancel Next Figure 3 8 Setting The Tunnel Network Interface IP Addresses With cmgui On clicking the Next button the configuration is processed It should be noted that the default suggested NetMap cloud network and cloud region addresses configured by the wizard are all compliant with RFC1918 private network addressing and are thus not public IP addresses If all is well the configuration is successfully processed A message is then displayed indicating that the cloud provider service has been added to the existing cluster and configured
7. 3 3 Cluster On Demand Access With A Local cmgui It is possible to run an X forwarded cmgui session from within an ssh X connection that is already running to the head node However it suffers from significant X protocol lag due to the various network encapsulation layers involved The procedure described earlier for cluster on demand access with the remote standalone cmgui from outside the cloud is therefore recommended instead for a more pleasant experience 2 4 Cluster On Demand Cloud Node Start up Cloud nodes must be explicitly started up This is done by powering them up assuming the associated cloud node objects exist The cloud node objects are typically specified in the bright setup script in the preceding example the cloud node objects are cnode001 and cnode002 However more cloud node objects can be created if needed after the bright setup script has run The maximum number that may be created is set by the license purchased Large numbers of cloud node objects can be created with Bright Cluster Manager as follows e In cmgui they are conveniently created with the Node Creation Wizard as described in section 3 3 Several of the steps described in that section are specific to Cluster Extension clusters These steps are not needed for Cluster On Demand clusters and therefore do not come up when the wizard is used in this case e In cmsh a large number of cloud node objects can conveniently be created with the foreach clo
8. 8 Do you want to use the head node for compute jobs NO yes no The following information will be used to configure this head node Amazon information AWS username exampleuser brightcomputing com AWS Account ID 313234312222 Access Key ID OUPOUASOUDSSSAOU Secret Access Key Aighei8EooLilDae8Niod5oh14iexiAin5eeRoaiV Bright Product Key 423112 231432 134234 132423 134221 License information Country US State CA Locality San Francisco Organization name Bright Computing Organizational Unit Development Cluster Name demo cluster Hostname bright71 Second drive size no Instance Type tl micro Node Count 2 Base name cnode Storage type EBS Size of storage 15 GB Workload management system slurm Number of slots 8 Head node for compute jobs no The information to configure this head node has been collected and shown above The next phase will be to process this information A new Bright license will be installed the Bright Cluster Manager software will be initialized and the workload management software will be initialized Do you want to continue YES no yes Starting to configure this head node Successfully retrieved the licens Installed license Bright Computing Inc 2 3 Cluster On Demand Connecting To The headnode Via cmsh or cmgui 17 Initializing Bright Cluster Manager Installing admin certificates Configuring default scheduler slurm Set up finished It is recommende
9. Access Identifiers section of the subscription at http aws portal amazon com gp aws developer account index html action access key provides the required information If that URL does not work then the Amazon documentation at http docs amazonwebservices com fws latest GettingStartedGuide index html AWSCredentials html can be followed instead For Amazon the fields to enter in the wizard are e The Name A convenient arbitrary value e The Username The e mail address associated with the AWS account e The AWS account ID The AWS Account ID e The AWS account key ID The AWS Access Key ID e The AWS secret access key ID The AWS Secret Access Key The show password checkbox toggles the visibility of the sensitive input Clicking the Next button submits the details and inputs for the next screen are retrieved from Amazon The next screen figure 3 2 displays options for the Amazon cloud service Bright Computing Inc 24 Cluster Extension Cloudbursting x Add Cloud Provider Wizard 0o00 Please select default values Default region us east 1 X Default AMI latest brightinstaller 089 x Default type tl micro x Default director type m1 large v Figure 3 2 Selecting Options At The Cloud Provider With cmgui In figure 3 2 the following options are shown e Default region These are regions from which the service can be provided Amazon for exam ple offers
10. Coud instance ll Cat wi Persistent s ebs 40 Gi cloud di Spare us ast mL Interface Network IP offset etho cloud x o ie o 0 fo JoJo o_ Capacity us east 1 direc b 0 GPU Units Ypen Adc Create Cloud Nodes Revert Figure 3 10 Cloud Node Wizard Network And IP Offset Configuration Screen The last screen of the wizard figure 3 11 shows a summary screen of the proposed IP address allo cations If the cloud IP addresses are to be assigned using DHCP then their values are 0 0 0 0 Bright Computing Inc 3 3 Cluster Extension Cloud Node Start up 35 File Monitoring View Help Bright 6 0b Cluster Vee My Clusters Bright 6 0b Cluster Overview Modified Poviderw Hostnamew Type w Cloud instance IDW Categoy W Persistent s b i Switches lt Ss ER E ul i F d di b 40 Gi gt fig Networks pare us ast m1 clou ve e s cloud X Node Creation Wizard oo externalnet globalnet Values below can be changed as desired Please take care not to change the internalnet formatting or table headers netmap hostname eth0 cloud tun0 us east 1 a us east 1 Si a a a rn a a ce a Kaew ners wher ls b C Power Distribution Units cnode001 0 0 0 0 172 21 0 1 cnode002 0 0 0 0 172 221 0 2 gt E Sofware Images cnode003 0 0 0 0 172 21 0 3 gt i Node Categories cnode004 0 0 0 0 172 21 0 4 Head Nod
11. Instance If the system and network are working as expected then an SSH connection can be made to the head node to carry out the next step which is the configuration of the head node and cluster 2 2 Cluster On Demand Head Node Login And Cluster Configuration After the Amazon console manager has started up a head node instance the head node instance and cluster must be configured Logging into the head node via ssh allows this On logging in for the first time the system suggests that the bright setup script be run Example pj office S ssh i pjkeypair pem root ec2 176 34 160 197 eu west 1 com pute amazonaws com The authenticity of host ec2 176 34 160 197 eu west 1 compute amazonaw s com 176 34 160 197 can t be established RSA key fingerprint is 66 le 3 77 83 8 3f 42 cl1 b7 d2 d5 56 d8 c3 58 Are you sure you want to continue connecting yes no yes Warning Permanently added ec2 176 34 160 197 eu west 1 compute amazon aws com 176 34 160 197 RSA to the list of known hosts Welcome to Bright Cluster Manager Based on Scientific Linux 5 Cluster Manager ID 999915 To set up your cluster type bright setup and follow the instructions Creating DSA key for ssh root headnode Running the bright setup script goes through several screens some of which prompt for input At some prompts it is hinted that typing I gives further explanation about the input The screens go through the f
12. With Static IP Addresses In A Custom VPC Recommendation Subnets can be set up in many ways inside a custom VPC The following is recommended e There must be exactly one network containing all the instances which have static IP addresses This network should contain the cloud director The network with the cloud director is arbitrarily referred to as the public network e There must be zero or more networks containing instances with no static IP addresses assigned to them Such networks are arbitrarily referred to as the private subnets Instances in the private subnets have no static IP addresses assigned to them so by default they do not communicate with outside networks To allow them to connect to the outside the cloud director instance is automatically configured by CMDaemon as a NAT gateway for outside bound traffic for the instances existing inside the private subnets 6 3 5 Assignment Of Nodes To Subnets And Cloud Platforms A cloud node instance is connected to a network by its eth0 interface The network is one of those covered in following table that is classic physical classic emulated or subnet of a custom VPC what cloud is the eth0 cloud instance type and network interface connected to that the node joins classic cloud classic cloud cluster instance in classic physical network 10 0 0 0 8 default VPC defaultVPC instance in classic emulated network 172 31 0 0 8 custom VPC inside VPC instance in
13. a hybrid cloud cluster chapter 3 In this scenario the head node is kept outside the cloud Zero or more regular nodes are also run outside the cloud When additional capacity is required the cluster is extended via cloudbursting to make additional nodes available from within the cloud Chapters 2 and 3 deal with GUI configuration of the two cloudbursting scenarios Chapter 4 looks at cloudbursting configuration using command line tools Chapter 5 discusses some miscellaneous aspects of cloudbursting Chapter 6 describes the concepts including networking behind setting up a private cloud cluster on a virtual private network using the Amazon VPC infrastructure Bright Computing Inc Cluster On Demand Cloudbursting Requirements If the cloud provider is Amazon then Cluster On Demand cloudbursting the case of starting up a pure cloud cluster requires e an Amazon account e registration on the Bright Computing Customer Portal website at http www brightcomputing com Customer Login php e a Bright Cluster Manager product key The key is obtained at the Customer Portal website specif ically for a Cluster On Demand setup from the Burst menu This key is later activated when the license is installed section 2 2 on the head node The head node and regular nodes in this case are in the cloud Steps The following steps are then carried out to start up the head node and regular nodes of the cloud cluster
14. a choice out of capacity on the East Coast of the USA Western Europe the Asia Pacific region and others e Defaul lt AMI This is the Amazon Machine Instance image that Bright Computing provides The node installer from this image installs the cloud director and cloud nodes e Defaul lt type A choice out of a selection of possible virtual machine types http aws amazon com ec2 instance types made available by Amazon for the cloud node The choices others presented are from node specifications consisting of memory storage cores GPUs and In cmsh running cmsh c cloud types also shows the types available e Default director type A choice for the cloud director node made from a selection of pos sible virtual machine types made available by Amazon This virtual machine type usually needs to be m ore powerful than a regular cloud node and is by default set to m1 large The default settings are normally a good choice On clicking the Next button the choices are pro cessed The next screen figure 3 3 displays the NetMap network name and addressing scheme This is a network mapping that assigns extra IP addresses to local nodes to make them accessible from the cloud The addressing scheme can be changed if needed to another unused subnet By default it uses 172 31 0 0 16 Bright Computing Inc 3 1 Cluster Extension Cloud Provider Login And Cloud Director Configuration 25 The NetMap netwo
15. be created by specifying e the name e the default region e base address e number of netmask bits The network of the custom VPC must obviously be a superset of its subnets Any subnets of the custom VPC must also be specified Subnets can be added to or removed from an already created custom VPC but only if any cloud node instances within them are terminated first There are several ways to set up and create the subnets and custom VPC instance in Bright Cluster Manager 1 by using the command line cm cloud setup private cloud utility 2 by using the cmgui private cloud creation dialog box 3 by manually creating and configuring the private cloud object using cmsh These are described next 1 Subnet Setup And Custom VPC Instance Creation Using cloud setup private cloud Once the cloud provider account has been configured using the cm cloud setup utility section 4 1 or by using the cmgui wizard section 3 1 the cn cloud setup private cloud utility can then be run to set up a custom VPC The utility prompts the user to choose a cloud provider account a region to create the VPC in and the base address of the VPC It goes on to create the custom VPC and finishes by prompting whether to move any eligible cloud nodes to the custom VPC Bright Computing Inc 6 3 Setting Up And Creating A Custom VPC 55 2 Subnet Setup And Custom VPC Creation Using cmgui For the cloud provider resource item inside the Private Cl
16. center pane displays a pop up text that guides the user through the connection options for a running instance These connection options are via e astandalone SSH client There is further documentation on this at http docs aws amazon com AWSEC2 latest UserGuide AccessingInstancesLinux html for Linux clients http docs aws amazon com AWSEC2 latest UserGuide putty html for PuTTY users e a browser based Java SSH client MindTerm There is further documentation on this at http docs aws amazon com AWSEC2 latest UserGuide mindterm html Bright Computing Inc 12 Cluster On Demand Cloudbursting Most administrators should find the pop up text enough and the further documentation unnecessary The standalone SSH client help text displays instructions figure 2 9 on how to run ssh from the command line to access the marked instance If the launched head node is fully up then a login using those instructions succeeds Connect To Your Instance would like to connect with A standalone SSH client OA Java SSH Client directly from my browser Java required To access your instance 1 Open an SSH client find out how to connect using PuTTY Locate your private key file pjeukeypair pem The wizard automatically detects the key you used to launch the instance Your key must not be publicly viewable for SSH to work Use this command if needed chmod 400 pjeukeypair pem Co
17. cmsh with the node range option Example bright71 gt device foreach n cnode002 cnode010 power on 4 4 Submitting Jobs With cmsub And Cloud Storage Nodes The cmsub command is a user command wrapper that submit job scripts to a workload manager in a Cluster Extension cluster so that jobs are considered for running in the cloud Its usage for an end user is covered in section 4 7 of the User Manual The cmsub command is available from the Bright Cluster Manager repository as part of the cmdaemon cmsub package The cmsub command needs the cmsub environment module section 2 2 of the Administrator Manual to be loaded by the user before use If the cmsub command is run by the user to submit a job then the job is submitted to the workload manager and the data aware scheduling mechanism is initiated Bright Computing Inc 4 4 Submitting Jobs With cmsub And Cloud Storage Nodes 41 A cluster with data aware scheduling is a cluster that ensures that it has the data needed for the cloud computing job already accessible on cloud storage nodes Cloud storage nodes are nodes that are set up by the cluster manager before the job is executed in the cloud Because data stored can be written and read from many cloud storage nodes for each job that is placed in the cloud the data throughput in the cloud becomes more efficient than if only one storage space were used 4 4 1 Installation And Configuration of cmsub For Data aware Schedul
18. comes up and will have the same node name as before Bright Computing Inc Cluster Extension Cloudbursting Cluster Extension cloudbursting hybrid cloudbursting in Bright Cluster Manager is the case when a cloud service provider is used to provide nodes that are in the cloud as an extension to the number of regular nodes in a cluster The head node in a Cluster Extension configuration is always outside the cloud and there may be some regular nodes that are outside the cloud too Requirements Cluster Extension cloudbursting requires e An activated cluster license Some administrators skip on ahead to try out cloudbursting right away in a Cluster Extension configuration without having made the license active earlier on That will not work A check on the state of the license can be carried out with Example root bright71 cmsh c main licenseinfo License Information Licensee C US ST NY L WS O Bright Bitcoins OU Unit CN Bright 7 1 Cluster Serial Number 19305 Start Time Mon Dec 20 00 00 00 2015 End Time Wed Jun 20 00 00 00 2018 Version Pai Edition Advanced Pre paid Nodes 100 ax Pay per use Nodes N A ax Hadoop Nodes 80 ax OpenStack 70 ode Count 4 If activation is indeed needed then it is most likely a case of simply running the request license command with the product key Further details on activating the license are in section 4 of the Administrator Manual e Registration of
19. e ahead node instance is launched from a browser using the Amazon management console sec tion 2 1 e the head node instance is logged into via ssh and the cluster is configured section 2 2 e the regular nodes are started up from the head node using cmsh or cmgui to power them up section 2 4 These steps are now covered in more detail 2 1 Cluster On Demand Launching The Head Node From The Cloud Provider Launching a head node from within Amazon is covered in this section 2 1 1 Getting To The Launch Instance Button The Amazon management console can be logged into from https console aws amazon com console by using the e mail address and password of the Amazon account figure 2 1 Bright Computing Inc Cluster On Demand Cloudbursting a Amazon Web Services Sign In Iceweasel File Edit View History Bookmarks Tools Help a Amazon Web Services Sign In oP is amazon Es webservices Sign In or Create an AWS Account You may sign in using your existing Amazon com account or you can create a new account by selecting I am a new user My e mail address is orightguy example com O I am a new user I am a returning user and my password is eseese gt 4 Find Previous Next Highlight all Match case Figure 2 1 Logging Into The Amazon Management Console By default on login the management console displays a list of accessible Amazon web services
20. en i A hee i Oly About This Manual 42 22 mem eee eg aha 8 oe ee ede ee eae ENA SE Are a iii 0 2 About The Manuals In General 2 0 ee iii 0 3 Getting Administrator Level Support 2 0 0 00 0 eee ee ees iii Introduction 1 Cluster On Demand Cloudbursting 3 2 1 Cluster On Demand Launching The Head Node From The Cloud Provider 3 2 1 1 Getting To The Launch Instance Button 00 0000 000 3 2 1 2 Launching The Head Node Instance 2 2 ee ee ees 5 2 1 3 Managing A Head Node Instance With The AWS EC2 Management Console 9 2 2 Cluster On Demand Head Node Login And Cluster Configuration 13 2 3 Cluster On Demand Connecting To The headnode Via cmsh or cmgui 17 2 3 1 Cluster On Demand Access With A Remote Standalone cmgui 17 2 3 2 Cluster On Demand Access With ALocalcmsh 0 00000008 18 2 3 3 Cluster On Demand Access With A Local cmgui 0044 18 2 4 Cluster On Demand Cloud Node Start up 2 2 ee 18 2 4 1 IP Addresses In The Cluster On Demand Cloud 00048 20 Cluster Extension Cloudbursting 21 3 1 Cluster Extension Cloud Provider Login And Cloud Director Configuration 22 3 2 Cluster Extension Cloud Director Start up aooaa 28 3 2 1 Setting The Cloud Director Disk Storage Device Type 0 54 29 3 2 2 Setting The Cloud Director Disk Size 2 eee 30 3 2 3 Tracking Cloud Director Start up 6 ee eee 3
21. is created in such a network can be called a classic cloud cluster or simply a cloud cluster Amazon is gradually phasing out the EC2 Classic platform e EC2 VPC This platform is replacing EC2 Classic It provides an environment corresponding to an isolated virtual network A cloud cluster instance implemented on this virtual network is thus a virtual private cloud or VPC as described at the start of this section section 6 The EC2 VPC platform offers some extra features that are not available or not as easy to configure on the EC2 Classic platform Bright Computing Inc 52 Virtual Private Clouds Multiple VPCs can be configured per region The inherent isolation of Amazon VPCs makes them more secure by default their network properties can be customized The isolated network design of a VPC means that instances started within a VPC cannot by default communicate with instances outside Elastic IP addresses page 56 are used to explicitly allow commu nication with the outside 6 1 2 EC2 Classic Vs EC2 VPC And AWS Account Creation Date The type of platform that can be accessed by an AWS account varies as indicated by the following table Account Creation Date Typical Platform Offered Before start of 2013 EC2 Classic only In first half of 2013 EC2 Classic or EC2 VPC After first half of 2013 EC2 VPC only in most or all regions Typically depends on the region accessed Most new AWS accounts do
22. node can be set By default 16 regular cloud nodes are suggested The names of the nodes have a prefix of cnode by default and end in three digit numbers for example cnode001 cnode002 and so on e The category can be set for these nodes By default it is set to the default category e The region for the regular cloud nodes can be set By default it matches the cloud director region e The regular cloud node instance type can be set By default t1 micro is chosen e A spot price section 5 3 1 can be set in this screen to take advantage of cheaper pricing to launch regular cloud nodes By default no spot price is set e The storage type and size used can be set By default it is EBS and 42GB If the t1 micro instance type has been chosen then there is no ephemeral device storage available in accordance with Amazon policies The next screen of the wizard figure 3 10 applies to the region chosen in the previous screen in figure 3 9 the region is us east 1 Within the region IP offsets footnote on page 30 of the Installation Manual can be set Bright Computing Inc 3 3 Cluster Extension Cloud Node Start up 33 File Monitoring View Help we Spare Cap acit Bright 6 0b Cluster ves My Clusters v H Bright 6 0b C H Brig luster Providerw Hostnamew TypeW Chud instance IDW Categoy W Persisten gt Dj Switches v Networks Spare us east m1 cloud di ebs 40 clo
23. price quote in US dollars per hour for instances Instances that run while under the threshold are called spot instances Spot instances are described further at http aws amazon com ec2 spot instances With the pricing threshold set e If the set spot price threshold is above the instantaneous spot price then the spot instances run e If the set spot price threshold is below the instantaneous spot price then the spot instances are killed e If the set spot price threshold is N A then no conditions apply and the instances will run on demand regardless of the instantaneous spot price An on demand instance is one that runs regardless of the price according to the pricing at http aws amazon com ec2 pricing A persistent request is one that will retry running a spot instance if the conditions allow it 5 3 2 Storage Space Reduction Reducing the amount of EBS disk storage used per cloud node or per cloud director is often feasible 15 GB is usually enough for a cloud director and 5 GB is usually enough for a cloud node with common requirements In cmsh these values can be set with Example bright71 device cloudsettings eu west 1 director bright 71 gt device eu west 1 director gt cloudsettings storage bright71 gt gt cloudsettings gt storage set ebs size 15GB commit bright71 gt gt cloudsettings gt storage device cloudsettings cnode001 bright 71 gt device cno
24. protocol with the default CMDaemon back end on the head node The default security group setting should also be modified by the administrator at this point if a standalone cmgui is to be used to control the cluster section 2 3 For regular use in a cluster on demand setup lag is reduced if a standalone cmgui is used rather than running a cmgui originating from the head node via an ssh X connection e Step 7 Review Instance Launch The configuration so far can be reviewed On click ing the Launch button a pop up dialog for Select an existing key pair or create a new key pair is displayed figure 2 6 Bright Computing Inc 2 1 Cluster On Demand Launching The Head Node From The Cloud Provider 9 Select an existing key pair or create a new key pair x A key pair consists of a public key that AWS stores and a private key file that you store Together they allow you to connect to your instance securely For Windows AMls the private key file is required to obtain the password used to log into your instance For Linux AMls the private key file allows you to securely SSH into your instance Create a new key pair ly Key pair name Jakeypair Download Key Pair You have to download the private key file pem file before you can continue Store it in a secure and accessible location You will not be able to download the file again after it s created Cancel Launch Instances Figure 2 6 EC2 Choosing An AMI Step 7
25. successfully and that the wizard is finished with its job No nodes are activated yet within the cloud provider service To start them up the components of the cloud provider service must be started up by e powering up the cloud directors section 3 2 e powering on the cloud nodes after the cloud directors are up Often this involves creating new cloud nodes by using the Create Cloud Nodes wizard section 3 3 3 2 Cluster Extension Cloud Director Start up The cloud director can take some time to start up the first time The bottleneck is usually due to several provisioning stages where the bandwidth between the head node and the cloud director means that the provisioning runs typically take tens of minutes to complete The progress of the cloud director can be followed in the event viewer section 9 6 of the Administrator Manual This bottleneck is one of the reasons why the cloud director is put in the cloud in the first place The next time the cloud director powers up and assuming persistent storage is used as is the default the cloud director runs through the provisioning stages much faster and completes within a few minutes The cloud director acts as a helper instance in the cloud providing some of the functions of the head node within the cloud in order to speed up communications and ensure greater resource efficiency Amongst the functions it provides are e Cloud nodes provisioning e Exporting a copy of the share
26. 0 3 3 Cluster Extension Cloud Node Start up 6 a 32 Cloudbursting Using The Command Line And cmsh 37 4 1 Therem Cloud setup Script sats chante 8 ely eae eee ee A ee aS 37 4 2 Launching The Cloud Director 2 ee ee 39 4 3 Launching The Cloud Nodes 0 2 ee es 39 4 3 1 Creating And Powering Up An Individual Node 0 00 0 39 4 3 2 Creating And Powering Up Many Nodes 2 0 0 2 0 00000004 40 4 4 Submitting Jobs With cmsub And Cloud Storage Nodes 0 2005 40 4 4 1 Installation And Configuration of cmsub For Data aware Scheduling To The Cloud 41 4 5 Miscellaneous Cloud Commands 0 000 eee ee 44 4 5 1 Thecm cloud copy Tool 2 seso e eewo a nike ee ee 44 45 2 The em loud check Utility 224 2 ie 23 Oe we Soe tea ee Ba Pick 44 4 5 3 The cm scale cluster Utility 2 0 0 0 0 0 0 0 0 00 0000 44 4 5 4 The cm cloud remove all Utility 0 0 0 0 0 0 0 000 44 ii Table of Contents 5 Cloud Considerations And Issues With Bright Cluster Manager 47 5 1 Differences Between Cluster On Demand And Cluster Extension 47 5 2 Hardware And Software Availability 2 0 ee en 47 5 3 Redticing Running Costs asigi Gs weal ee ange a GPAs Glos ae E ana bate 47 DOL SPOEDIGE ies sd ts Be ces pee AMS NE Ad can beth ae ale aes Ute BEN OS a face ets aE 48 5 3 2 Storage Space Reduction 2 ee 48 5 4 Address Resolution In Cluster Extension Networks
27. 5 brightnode Volumes Source fr92 0 43 10 32 ia i i e g 192 168 2 0124 sg 47ad482e or Port Service Source Action napshots 1234567890 default 1o5535 g 71989218 Delete d Add Rule brightnode NETWORK amp SECURI 22 SSH 0 0 0 0 0 Delete Security Groups UDP Elastic IPs Apply Rule Changes Port Service Source Action Placement Groups p sg 71989e18 1 65535 brightnode Delete Load Balancers Key Pairs j 2008 2013 Amazon Web Services Inc or its affiliates All rights reserved Privacy Policy Terms of Use Feedback Isl Figure 2 11 Security Group Network And Port Access Restriction e To allow only a specific network block to access the instance the network from which remote connections are allowed can be specified in CIDR format e Explicitly allowing inbound connections to port 8081 on the head node allows the standalone cmgui section 2 4 of the Administrator Manual to connect to the head node This is because the Bright Computing Inc 18 Cluster On Demand Cloudbursting cmgui back end which is CMDaemon communicates via port 8081 2 3 2 Cluster On Demand Access With A Local cmsh The security group created by Amazon by default already allows inbound SSH connections from outside the cloud to the instance running in the cloud even if the incoming port 8081 is blocked Launching a cmsh session within an SSH connection running to the head node is therefore possible and works well 2
28. Computing Inc 3 1 Cluster Extension Cloud Provider Login And Cloud Director Configuration 27 The head node s needs a tunnel network interface on each tunnel network Please assign an IP address for the head node s on each tunnel network Region Head node interface IP us east 1 tun O O 172 21 255 254 Cancel Figure 3 6 Setting The Tunnel Network Interface For The Head Node s With cmgui On clicking the Next button the configuration is processed The next screen figure 3 7 displays a proposed Bright Cluster Manager hostname and tunnel IP address for the cloud director node s By default the suggested hostname is the region name with director as the suffix For example us east1 director for the region us east1 By default an address ending in 255 251 is suggested for appending to the first two parts of the dotted quad for example the prefix 172 21 for us east 1 so that the suggested default IP address in this case becomes 172 21 255 251 The addresses ending in 252 and 253 may be required by head nodes that implement failover Chapter 12 of the Administrator Manual These can be changed if needed from the suggested defaults but should be consistent with the net work address x Add Cloud Provider Wizard e089 Acloud director needs to be present in each region Please assign an IP address on the tunnel network for the cloud director in each region Region Hostname IP us east 1 us east 1 director
29. Keypair generation creation dialog This dialog allows the creation and storage of a cryptographic key pair It can alternatively allow an existing pair to be used from the Select a key pair selection The private key of the key pair is used in order to allow SSH access to the head node instance when it is up and running After the instance is launched the web session displays a window informing that the instance is being started up 2 1 3 Managing A Head Node Instance With The AWS EC2 Management Console A newly launched head node instance after it is fully up is a fully booted and running Linux instance but it is not yet a fully configured head node That is it is capable of running Bright Cluster Manager but it is not yet running it nor is it working with compute nodes at this point The steps to make it a fully configured head node are covered in section 2 2 For now the newly launched head node instance can be watched and managed without Bright Clus ter Manager in the following ways Status checking via instance selection from instances list Clicking the Instances menu resource item from the navigation pane opens up the Instances pane This lists instances belonging to the account owner An instance can be marked by ticking its checkbox Information for the selected instance is then displayed in the lower main pane figure 2 7 Bright Computing Inc 10 Cluster On Demand Cloudbursting https console aws amazo
30. Launch e Step 3 Configure Instance Details Among other instance options this optional step allows the following to be set Purchasing option for spot instances section 5 3 1 Network This is a choice of EC2 Classic or EC2 VPC instances section 6 1 1 Availability Zone for if there is a preference for the location of the instance Nodes within the same availability zone can connect with low latency and high bandwidth to each other They are also isolated from other availability zones in the same region which reduces the risk of network outages from another zone affecting them By default no preference is specified for the head node nor for the cloud nodes later This is because spot pricing can increase as nodes from an availability zone become scarce which may conflict with the intention of the administrator The default availability setting for a cloud account can be set in cmsh from within cloud mode Example Bright Computing Inc Cluster On Demand Cloudbursting o bright71 gt cloud Spare Capacity set defaultavailabilityzone Shutdown behavior to decide if the instance should be stopped kept around or termi nated removed e Step 4 Add Storage Among other storage options this optional step allows the following options to be set Size GB The size of storage to be added to the instance Type Whether the storage is EBS or ephemeral Device A device name chosen from dev sdb onw
31. Start up 31 Tracking cloud director start up from cmgui the boot progress of the cloud director can also be followed by e watching the icon changes as in section 5 5 1 of the Administrator Manual e watching the State in the Overview tabbed window e watching the Console log from the Tasks tabbed window Tracking cloud director start up from the bash shell of the head node there are some further possibilities to view the progress of the cloud director after it has reached at least the initrd stage These possibilities include e an SSH connection to the cloud director can be made during the pre init initrd stage after the cloud director system has been set up via an rsync This allows a login to the node installer shell e an SSH connection to the cloud director can be also be made after the initrd stage has ended after the init process runs making an SSH daemon available again This allows a login on the cloud director when it is fully up During the initrd stage the cloud director is provisioned first The cloud node image s and shared directory are then provisioned on the cloud director still within the initrd stage To see what rsync is supplying to the cloud director the command ps uww C rsync can be run on the head node Its output can then be parsed to make obvious the source and target directories currently being transferred Example root bright71 ps uww C rsync cut f11 d 11th part onwards cm shar
32. VPC platforms The most important ones are e Cloud nodes created inside the EC2 VPC platform do not have an external public IP address assigned to them by default An exception to this is the case of nodes running in a defaultVPC instance which emulates EC2 Classic network behaviour Having no public IP address by default allows for a greater degree of out of the box security e Custom VPCs are self contained and securely isolated from the instance of other users e Custom VPCs are partitioned into multiple network segments called subnets section 6 3 1 e It is possible to specify a custom base network address for the custom VPC This is in contrast to the EC2 Classic platform where a base network address always has the value of 10 0 0 0 8 For a defaultVPC instance the base network address takes the value of 172 31 0 0 8 6 3 Setting Up And Creating A Custom VPC By default when Bright Cluster Manager creates a new cloud provider account the cloud nodes created are EC2 Classic instances or defaultVPC instances inside the EC2 VPC platform That is they are not nodes in a custom VPC instance This default behavior is expect to change in a later version of Bright Cluster Manager as Amazon and Bright Cluster Manager both evolve Bright Cluster Manager can be set to create custom VPC instances inside the EC2 VPC platform The EC2 VPC platform is recommended for all new cloudbursting setups Bright Computing Inc 54 Virtual Private C
33. ards since dev sda is already taken Delete on Termination Whether the device is deleted when the instance terminates By default the instance has a Type called Root which is a special EBS volume It has a default Size GB of 80 which can be edited For most instances other than micro a certain amount of ephemeral storage is provided by Ama zon for free and can then be set for the root device in the Storage Device Configuration options of this screen The EBS and ephemeral storage types are described in section 3 2 1 e Step 5 Tag instance This optional step allows the addition of metadata to an instance via assignment of key value pairs A default key of Name is presented and the administrator should put in a name for the instance as the associated value The associated value can be arbitrary e Step 6 Configure Security Group This optional step allows a security group to be de fined A security group is a configuration that defines how network access to the instance is al lowed By default all access to the instance is blocked apart from SSH access Default SSH inbound allowed This means that cmsh can be used to control the Cluster On Demand cluster via SSH just like a regular cluster Inbound connections can be defined based on protocol packet type port and source in CIDR specification For example allowing inbound connections via TCP port 8081 from anywhere 0 0 0 0 0 allows cmgui to communicate via its custom
34. be used a tunnel network needs to be defined Atunnel network is used to make cloud nodes accessible within the cluster Please select the regions that will be used and choose an unused IP subnet for the tunnel network in each range Region Tunnel network IP range ee ap northeast 1 ap northeast 1 172 16 0 o 16 ap southeast 1 ap southeast 1 172 17 o lo I 16 ap southeast 2 ap southeast 2 172 18 0 0 I 16 eu west 1 eu west 1 172 19 0 0 16 sa east 1 sa east 1 172 20 0 0 16 v us east 1 us east 1 172 21 0 0 I 16 us west 1 us west 1 172 22 o 0 I 16 us west 2 us west 2 172 23 o 0 16 Cancel Figure 3 5 Setting The Tunnel Network For Regions With cmgui On clicking the Next button the configuration is processed The next screen figure 3 6 displays a proposed Bright Cluster Manager tunnel interface name and IP address for the head node s A tunnel interface is defined for the head node for each tunnel network By default the address ending in 255 254 is used and appended to the first two parts of the dotted quad for example 172 21 for us east 1 so that the suggested default IP address in this case becomes 172 21 255 254 The default suggested device name is tun0 These can be changed if needed from the suggested defaults Bright
35. bright71 gt network bright71 gt networks v bright71 gt networks v clone vpc 0 sn 0O vpc O0 sn 1 set baseaddress 10 0 1 0 commit pc O sn 1 pc O sn 1 e Custom VPC creation The following example session in the privateclouds submode of the cloud mode creates a private cloud called vpc 0 The private cloud is actually a custom VPC according to the strict definition of a private cloud instance in the section on page 52 It is of type ec2 and within a network that contains the two subnets specified earlier Example bright71 gt cloud Amazon EC2 gt privateclouds bright71 gt gt privateclouds add ec2privatecloud vpc 0 bright71 gt gt privateclouds vpc 0 set region eu west 1 bright71 gt vpc 0 set baseaddress 10 10 0 0 bright71 gt vpc 0 set netmaskbits 16 bright71 gt vpc 0 set subnets vpc 0 sn 0 vpc 0 sn 1 bright71 gt vpc 0 J J commit Bright Computing Inc 56 Virtual Private Clouds 6 3 3 Elastic IP Addresses And Their Use In Configuring Static IP Addresses Unlike default VPC and EC2 Classic instances a custom VPC instance does not have an externally visible public IP address assigned to it by Amazon by default Without an externally visible IP address the custom VPC cannot communicate with the internet and it cannot even be an endpoint to an outside connection To solve this issue Amazon elastic IP addresses EIPs can be used
36. cated by 2 a in the preceding External Network us east 1 network s 172 21 0 0 em Nead node A cloud director je 172 21 255 254 oth 172 21 255 251 BAAN 172 31 255 254 Ny Amazon IP 10 0 0 0 8 10 141 255 254 external IP o o 172 21 0 1 Internal Network gt O 9 10 141 0 0 16 as 3 Amazon IP 10 0 0 0 8 m a S aia 5 17221 02 wawi 172 31 0 1 on Amazon IP 10 0 0 0 8 A route via netmap Figure 5 1 NetMap In Relation To The General Network Scheme 172 31 0 2 ode002 As pointed out in the introduction to this section 5 4 the main reason for the IP addressing network scheme used is to avoid IP address conflicts between nodes within the cloud and nodes outside the cloud The difference in resolution of the IP address for the nodes as listed in points 1 and 2 in the preceding text is primarily to get the lowest overhead route between the source and destination of the packet being routed Thus for example a packet gets from the regular cloud node to the cloud director with less overhead if using the Amazon cloud IP addressing scheme 10 0 0 0 8 than if using the Bright OpenVPN addressing scheme 172 21 0 0 16 A secondary reason is convenience and reduction of networking complexity For example a node in the cloud may shut down and start up and get an arbitrary Amazon IP address but using an OpenVPN network such as us east 1 allows it to retain its OpenVPN address and thus stay identified instead of hav
37. cloud account which opens up the Add Cloud Provider Wizard window figure 3 1 Bright Computing Inc 3 1 Cluster Extension Cloud Provider Login And Cloud Director Configuration 23 Eile Monitoring View Help Cloud Nodes E Bright 6 06 Cluster Sverview Tasks Cloud Accounts vis My Clusters H Bright 6 0b Cluster b J Switches gt Lj Networks Add a new cloud account b Q Power Distribution Units gt C Software Images gt lt Add Cloud Provider Wizard b 9 Node Categories b Q Head Nodes Please enter cloud account information b Racks b Gj Chassis b 9 Virtual SMP Nodes b I Nodes Name Spare Capacity E Cloud Nodes b GPU Units Username martijn devries brightcomputing com b _ dj Other Devices b Node Groups A Users amp Groups AWS account key ID ssssssessssssssssse gt Workload Management EN Monitoring Configurat a AWS secretaccess key sesssssssessssssossssesesseseessesessese AWS account ID 137677338923 Authorization _ Show password B Authentication Figure 3 1 Logging Into A Cloud Provider With cmgui In the first screen the cloud account subscription information is added The subscription information could be from Amazon or from another supported provider In the case of Amazon the information is obtainable after signing up for Amazon Web Services AWS at http aws amazon com After sign up the
38. cm cloud storage setup configure Specify workload manager default slurm options slurm pbspro torque Ilsf openlava sge gt slurm Specify software image used for cloud nodes default default image options default im age gt Do you want to create job queues for cloud nodes default y options y n gt Specify a comma separated list of job queue names gt cloudq extracloudg Create symlink cm images default image cm local apps slurm var prologs 10 prolog cmsub to cm local apps cmd scripts cloudjob cmsub prolog Create symlink cm images default image cm local apps slurm var epilogs 10 epilog cmsub to cm local apps cmd scripts cloudjob cmsub epilog Please note that the changes in the software image s have not been propagated to the running nodes This will happen when the node s is are rebooted Creation Of Templates For Storage Nodes And Creation Of Storage Policy For cmsub A session with cm cloud storage setup that creates storage node templates and that creates stor age node policies is Example root bright71 cm cloud storage setup creat Specify a name for the storage node template you want to create use gt atemplate Is this a new template default yes options yes no gt Specify a name for the storage node policy you want to create use gt apolicy Is this a new policy default yes options yes no gt Specify category for storage nod
39. d CPU performance Popular uses for micro instances include low traffic websites or blogs small administrative applications bastion hosts and free trials to explore EC2 functionality Micro instances General purpose Memory optimized ee Ecus 1 vcPUs 1 Memory Instance Storage EBS Optimized s Network GiB GiB i Available i Performance Storage optimized tl micro up to 2 0 613 EBS only Very Low Compute optimized Micro instances are eligible for the AWS free usage tier For the first 12 months following your AWS sign up date you get up to 750 hours of micro instances each month When your free usage tier expires or if your usage exceeds the free tier restrictions you pay standard pay as you go service rates Learn more about free usage tier eligibility and restrictions Cancel Previous Review and Launch Next Configure Instance Details s Inc or its affiliates All rights reserved Privacy Policy Terms of Use Feedback Figure 2 5 EC2 Choosing An AMI Step 2 The t1 micro is the smallest and least powerful type of instance that a head node can run as but is only useful for quite minor testing It is likely to be overwhelmed when doing any significant work A more reasonable node type to use for testing is therefore the m1 small type which is available under the General purpose navigation option of this window Steps 3 to 6 that follow are optional and can be skipped by going ahead to Step 7 Review Instance
40. d directory cm shared to the cloud nodes so that they can mount it Bright Computing Inc 3 2 Cluster Extension Cloud Director Start up 29 e Providing routing services using an OpenVPN server While cloud nodes within a region commu nicate directly with each other cloud nodes in one region use the OpenVPN server of their cloud director to communicate with the other cloud regions and to communicate with the head node of the cluster Cloud directors are not regular nodes so they have their own category cloud director into which they are placed by default The cloud related properties of the cloud director are displayed in the Cloud Settings tab of the Cloud Nodes director item The cloud director can be started up in cmgui by right clicking on the cloud director item from the Cloud Nodes resource and selecting Power on from the menu Any cloud settings options that have been set are frozen as the instance starts up until the instance terminates 3 2 1 Setting The Cloud Director Disk Storage Device Type Amazon provides two kinds of storage types as part of EC2 1 Instance storage using ephemeral devices Instance storage is not provided for the following instance types e tl micro e m3 xlarge e m3 2xlarge e crl 8xlarge However Amazon by default currently provides 150GB or more of instance storage for all other instance types Details on instance storage can be found at http docs aws amazon com AWSEC2 lates
41. d shows the values of the storage devices associated with the cloud director The values can be modified as required with the usual object commands The set com mand can be used to modify the values Bright Computing Inc 30 Cluster Extension Cloudbursting Example bright71 device use us east l director bright71 gt device us east 1 director cloudsettings bright71 gt device us east 1 director gt cloudsettings storage bright71 gt gt cloudsettings gt storage list Type Name key Drive Size Volume ID ebs ebs sdb 42GB phemeral phemeral0 sdc OB ephemeral0 bright71 gt gt cloudsettings gt storage remove ebs bright71 gt gt cloudsettings gt storage set ephemeralO drive sdb bright71 gt gt cloudsettings gt storage list Type Name key Drive Size Volume ID phemeral phemeral0 sdb OB ephemeral0 bright71 gt gt cloudsettings gt storagex commit 3 2 2 Setting The Cloud Director Disk Size The disk size for the cloud director can be set with cmgui in the Cloud Settings tab By default an EBS volume size of 42GB is suggested This is as for a standard node layout sec tion D 3 of the Administrator Manual and no use is then made of the ephemeral device 42GB on its own is unlikely to be enough for most purposes other than running basic hello world tests In actual use the most important considerations are likely to be that the cloud
42. d that the system administrator log out and login again after the script has been run in order to enable the new environment for the shell that the administrator is in If the hostname was changed in the bright setup script for example the name change shows up in the shell prompt only after the re login Once there is a head in the cloud the other cloud nodes can be started up 2 3 Cluster On Demand Connecting To The headnode Via cmsh or cmgui Amazon provides a security group to each instance By default this configures network access so that only inbound SSH connections are allowed from outside the cloud A new security group can be config ured or an existing one modified using the Edit details button in figure 2 11 Security groups can also be accessed from the navigation menu on the left side of the EC2 Management Console 2 3 1 Cluster On Demand Access With A Remote Standalone cmgui The security group defined by Amazon for the head node can be modified by the administrator to allow remote connections to CMDaemon running on the head node figure 2 11 File Edit View History Bookmarks Tools Help EC2 Management Console T z Services v Reserved Instanced _ Security Group quicklaunch 11 ee A 4 es IMAGES Details Inbound AMIs Create anew Custom TCP rule iv ICMP Bundle Tasks rule Port Service Source Action Port range 8081 ALL sg 71989e18 Delete ELASTIC BLOCK STOF e g 80 or 49152 6553
43. dding cloud provider Amazon EC2 ok Waiting for cloud provider data Got 7 regions 29 images 12 types Default region default eu west 1 options ap northeast l us west 2 gt eu west 1 Default AMI default latest options brightinstaller 074 brightinstaller 075 gt Default type default tl micro options cl xlarge tl micro gt Default cloud director type default ml large options cl xlarge tl micro gt Update cloud provider Amazon EC2 ok Got 6 networks Found tunnel network for eu west 1 172 16 0 0 16 Using NetMap network 172 31 0 0 16 Using cloud network 10 0 0 0 8 Use regions default eu west 1 space separated all options ap northeast l us west 2 gt Updating head node bright71 ok Updating tunnel network eu west 1 ok Cloud director ip on eu west 1 default 172 16 255 251 gt Adding cloud director eu west l1 director ok Provisioning update started root bright71 After cm cloud setup has run the cloud nodes the cloud director and regular cloud nodes can be launched Bright Computing Inc 4 2 Launching The Cloud Director 39 4 2 Launching The Cloud Director Launching the cloud requires that the cloud director and cloud nodes be powered up This can be done using cmgui as described in sections 3 2 and 3 3 It can also be carried out in cmsh for example the cloud director eu west 1 director can be powered up from d
44. de001 gt cloudsettings storage bright71 gt gt cloudsettings gt storage set ebs size 5GB commit The value for the cloud node EBS storage can also be set in the cloud node wizard fig 3 9 for a Cluster Extension configuration 5 4 Address Resolution In Cluster Extension Networks 5 4 1 Resolution And globalnet The globalnet network is introduced in section 3 2 3 of the Administrator Manual It allows an extra level of redirection during node resolution The reason for the redirection is that it allows the resolution of node names across the entire cluster in a hybrid cluster regardless of whether the node is a cloud node cloud director node or regular cloud node or a non cloud node head node regular node or networked device A special way of resolving nodes is needed because the Amazon IP addresses are in the 10 0 0 0 8 network space which conflicts with some of the address spaces used by Bright Cluster Manager There are no IP addresses defined by globalnet itself Instead a node with its domain defined by the globalnet network parameters has its name resolved by another network to an IP address The resolution is done by the nameserver on the head node for all nodes lirregular turns out to be random within a tight range bound to a reserve price Or rather that was the case during the period 20th January 13th July 2010 that was analyzed by Ben Yehuda et al http www cs technion ac il users wwwb egi bin tr
45. director should have enough space for e the user home directories under home e the cluster manager shared directory contents under cm shared e the software image directories under cm images The cluster administrator should therefore properly consider the allocation of space and decide if the disk layout should be modified An example of how to access the disk setup XML file to modify the disk layout is given in section 3 9 3 of the Administrator Manual For the cloud director an additional sensible option may be to place t mp and the swap space on an ephemeral device by appropriately modifying the XML layout for the cloud director 3 2 3 Tracking Cloud Director Start up Tracking cloud director start up from the EC2 management console the boot progress of the cloud director can be followed by watching the status of the instance in the Ama zon EC2 management console as illustrated in figure 2 8 The Instance ID that is used to identify the instance can be found e with cmgui within the Cloud Settings tab for the cloud director node e with cmsh by running something like Example bright71 device use us east 1l director bright71 gt device us east l1 director get cloudid i 98e7441 bright71 gt device us east 1 director cloudsettings i bright71 gt device us east 1 director cloudsettings get instanceid 98e7441 Bright Computing Inc 3 2 Cluster Extension Cloud Director
46. e and manage the cloud capabilities of Bright Cluster Manager The administrator is expected to be reasonably familiar with the Administrator Manual 0 2 About The Manuals In General Regularly updated versions of the Bright Cluster Manager 7 1 manuals are available on updated clus ters by default at cm shared docs cm The latest updates are always online at http support brightcomputing com manuals e The Installation Manual describes installation procedures for the basic cluster e The Administrator Manual describes the general management of the cluster e The User Manual describes the user environment and how to submit jobs for the end user The Developer Manual has useful information for developers who would like to program with Bright Cluster Manager e The OpenStack Deployment Manual describes how to deploy OpenStack with Bright Cluster Man ager e The Hadoop Deployment Manual describes how to deploy Hadoop with Bright Cluster Manager e The UCS Deployment Manual describes how to deploy the Cisco UCS server with Bright Cluster Manager If the manuals are downloaded and kept in one local directory then in most pdf viewers clicking on a cross reference in one manual that refers to a section in another manual opens and displays that section in the second manual Navigating back and forth between documents is usually possible with keystrokes or mouse clicks For example lt Alt gt lt Backarrow gt in Acrobat Reader or clic
47. ed syncer 172 22 255 251 target cm shared Tracking cloud director start up from cmsh the provisioningstatus command in cmsh can be used to view the provisioning status some out put elided Example root bright71 cmsh c softwareimage provisioningstatus us east l1 director Up to date images none Out of date images default image In the preceding output the absence of an entry for Up to date images shows that the cloud director does not yet have an image that it can provision to the cloud nodes After some time the last few lines of output should change to something like Example us east l1 director Up to date images default image This indicates the image for the cloud nodes is now ready With the a option the provisioningstatus a command gives details that may be helpful For example while the cloud director is having the default software image placed on it for provisioning purposes the source and destination paths are cm images default image Bright Computing Inc 32 Cluster Extension Cloudbursting Example root bright71 cmsh c softwareimage provisioningstatus a Request ID s 4 Source node bright71 Source path cm images default imag Destination node us east 1 director Destination path cm images default imag After some time when the shared filesystem is being provisioned the source and destination paths should change to the cm shared direc
48. es default default options default cloud director us east l gt Tunnel interface was found on director node us east l director So storage nodes will a lso have a tunnel interface Is this correct default yes options yes no gt Bright Computing Inc 4 4 Submitting Jobs With cmsub And Cloud Storage Nodes 43 Define a starting point for the IPs assigned to storage nodes on the tunnel network Th is IP value must contain zeros as the network part If there is no tunnel network speci fy value 0 0 0 0 default 0 0 100 0 gt Specify the time a storage node can be idle before it gets automatically powered off d efault 15m Input format is lt value gt s S m M h H d D gt Specify the name of the S3 bucket to use for transferring input data and results of jo bs gt abucket Adding cloud storage node templat The storage node policy settings can be modified via CMDaemon using cmsh root bright71 cmsh bright71 cloud bright71 gt cloud use amzazonec2 bright71 gt cloud Amazon EC2 storagenodepolicies bright71 gt cloud Amazon EC2 gt storagenodepolicy list Name key Template for cloud nodes apolicy atemplate bpolicy atemplate bright71 gt cloud Amazon EC2 gt storagenodepolicy use apolicy o bright71 gt cloud Amazon EC2 gt storagenodepolicy apolicy show Parameter Value Bucket Name abucket Default job output size 1GB Disab
49. es cnode005 0 0 0 0 172 21 0 5 Gorana enode007 0 0 0 0 172 21 0 7 b 0 Racks poses aah v b i Chassis 4 a gt b i Virtual SMP Nodes b Nodes v Cloud Nodes he pare Capacity us east l direc z z E gt E GPU Units Open Add remove Create Cloud Nodes Figure 3 11 Cloud Node Wizard Network And IP Layout Screen When the wizard is finished the regular cloud nodes must be saved This adds them to the default category by default If the cloud director is up then the cloud nodes can be booted up by powering them up section 4 2 of the Administrator Manual by category or individually Bright Computing Inc Cloudbursting Using The Command Line And cmsh The command line and cmsh can be used to set up Cluster On Demand and Cluster Extension clusters For Cluster On Demand setups a GUI web browser is needed initially to launch the head node AMI from Amazon However once an ssh connection is made by the administrator to the head node cloudbursting can be continued from command line Thus the bright setup script is run from the command line as in section 2 2 and the cloud nodes can be powered up from the command line as in section 2 4 For Cluster Extension setups cloudbursting can be carried out entirely from the command line The cm cloud setup script section 4 1 sets up the cloud provider login and cloud director configura tion GUI steps of section 3 1 in a guided manner on a command line dialog after which cmsh power c
50. es them With cmgui this can be done with the help of a wizard to assign the IP addresses section 3 3 With cmsh assignment can be done for an individual cloud node or for many cloud nodes as follows 4 3 1 Creating And Powering Up An Individual Node In the example that follows a single cloud node is assigned a management network a tunnel IP address and a tunnel network so that it can communicate with the cloud director Example root bright71 cmsh bright71 device bright71 gt device add cloudnode cnode001 This CloudNode will not start set managementnetwork Warning tunnel ip of cnode001 not set bright71 gt devicesx cnode001 bright71 gt devices cnode001 Parameter u west 1 show Value Management network eu west 1 Network eu west 1 bright 71 gt devicex cnode001 interfaces Bright Computing Inc 40 Cloudbursting Using The Command Line And cmsh bright 71 gt devicex cnode001 gt interfaces list Type Network device name IP Network physical eth0O prov dhcp O0 a00 cloud ec2classic tunnel tuno 0 0 0 0 bright 71 gt devicex cnode001 gt interfaces set tun0O ip 172 16 0 1 bright 71 gt devicex cnode001 gt interfaces set tun0 network eu west 1 s bright 71 gt devicex cnode001 gt interfaces list Type Network device name IP Network physical eth0O prov dhcp Oss 0i0 9 0 cloud ec2classic tunnel tu
51. evice mode with Example cmsh c device power on n eu west 1 director If the administrator is unsure of the exact cloud director name one way it can easily be found is via tab completion within the device mode of cmsh As explained in section 3 2 the cloud director takes some time to power up Its status can be followed in the notice messages sent to the cmsh session or in the cmgui event viewer The status can also be queried via the status command in device node For example a wat ch instruction such as root bright71 watch cmsh c device status n eu west 1l director will show a series of outputs similar to u west l director PENDING Waiting for instance to start u west l director PENDING Waiting for instance to start u west l director PENDING IP assigned 54 220 240 166 u west l director PENDING setting up tunnel u west l director INSTALLER_REBOOTING u west l director INSTALLING recreating partitions u west l director INSTALLING FULL provisioning to u west l director INSTALLING provisioning started 4 3 Launching The Cloud Nodes Once the cloud director is up the cloud nodes can be powered up This first requires that the cloud node objects exist and each have an IP address assigned to them that is consistent with that of the cloud director that manag
52. external interface cluster has publicly accessible IP address cloud directors have publicly accessible IP addresses A note about the last entry The access to the cloud director addresses can be restricted to an administrator defined set of IP addresses using the Externally visible IP entry in figure 3 1 of the Administrator Manual 5 2 Hardware And Software Availability Bright Computing head node AMIs are available for the following distributions RHEL5 RHEL6 SL5 SL6 CentOS5 CentOS6 and SLES 11 SP1 SP2 AMIs with GPU computing instances are available with Amazon cloud computing services only in the US East Virginia region the last time this was checked April 2012 These can be used with Bright Computing AMIs with hvm in the name not xen in the name To power the system off a shutdown h now can be used or the power commands for cmgui or cmsh can be executed These commands stop the instance without terminating it Any associated extra drives that were created need to be removed manually via the Volumes screen in the Elastic Block Store resource item in the navigation menu of the AWS Management Console 5 3 Reducing Running Costs Bright Computing Inc 48 Cloud Considerations And Issues With Bright Cluster Manager 5 3 1 Spot Pricing The spot price field is a mechanism to take advantage of cheaper pricing made available at irregular times The mechanism allows the user to decide a threshold spot price a
53. f cloud compute nodes and their base name the cnode part of the name if the nodes have the names cnode001 to cnode lt N gt Setting up the amount of storage for the cloud compute node instance The default disk partitioning layout for nodes can be modified as described in Appendix D of the Administrator Manual Using diskless nodes is also possible if the cloud compute node instance has enough RAM about 2GB at the time of writing Setting these values causes the cloud node objects to be created in the CMDaemon database Cloud nodes are not however actually started up at this stage Starting up must be done explicitly and is covered in section 2 4 e Setting up the workload manager along with the number of slots and if the head node is to be used for compute jobs too After accepting the input the bright setup script runs through the configuration of the head node and the cloud nodes Its progress is indicated by output similar to the following Example root headnode bright setup Retrieving Amazon instance information License agreements Th nd user license agreement will be shown in a new screen To exit this screen type q Press any key to continue Do you agree with the license terms and conditions yes no show yes Bright Computing Inc 2 2 Cluster On Demand Head Node Login And Cluster Configuration 15 Amazon account information AWS username I for information exa
54. figure 2 2 OO G File Edit View History Bookmarks Tools Help E AWS Management Console Qo 2 https conso Services v Amazon Web Services Database Compute amp Networking Direct Connect e DynamoDB Dedicated Network Connection to Predictable and Scalable NoSQL AWS Data Store EC2 ElastiCache Virtual Servers in the Cloud In Memory Cache Route 53 RDS Scalable Domain Name System Managed Relational Database Service ii VPC https console aws amazon com ec2 v2 home ishift Gry X Analytics Data Pipeline Orchestration for Data Driven Workflows Elastic MapReduce Managed Hadoop Framework App Services CloudSearch Managed Search Service v E Google Martijn de Vries v Global v Additional Resources Getting Started See our documentation to get started and learn more about how to use our services Trusted Advisor Best practice recommendations to save money improve fault Figure 2 2 Amazon Management Console Accessible Services Help v To set up the Cluster On Demand cluster the EC2 service within the Compute amp Networking grouping should be clicked This brings up the EC2 Dashboard which is also the top link of a resource tree that is displayed in a Navigation pane figure 2 3 Bright Computing Inc 2 1 Cluster On Demand Launching The Head Node From The Cloud Provider 5 a EC2 Management Console Iceweasel ooo File Edit View Hi
55. ftware that is licensed by the Linux authors free of charge Bright Computing Inc shall have no liability nor will Bright Computing Inc provide any warranty for the Bright Cluster Manager to the extent that is permitted by law Unless confirmed in writing the Linux authors and or third parties provide the program as is without any warranty either expressed or implied including but not limited to marketability or suitability for a specific purpose The user of the Bright Cluster Manager product shall accept the full risk for the qual ity or performance of the product Should the product malfunction the costs for repair service or correction will be borne by the user of the Bright Cluster Manager product No copyright owner or third party who has modified or distributed the program as permitted in this license shall be held liable for damages including general or specific damages damages caused by side effects or consequential damages resulting from the use of the program or the un usability of the program including but not limited to loss of data incorrect processing of data losses that must be borne by you or others or the inability of the program to work together with any other program even if a copyright owner or third party had been advised about the possibility of such damages unless such copyright owner or third party has signed a writing to the contrary Table of Contents Tabl sof Contents a eyes ar ee ee ea ee a ae I eee
56. hots ec2 50 16 44 106 compute 1 amazonaws com Description Status Checks Monitoring Tags Security Groups Status checks detect problems that may impair this instance from running your applications Create Status Check Alarm P Elasuc lrs System Status Checks Instance Status Checks Placement Groups Load Balancers These checks monitor the AWS systems required to use These checks monitor your software and network configuration this instance and ensure they are functioning properly for this instance Key Pairs System reachability check passed Instance reachability check failed at 2013 04 03 17 58 more info GMT 0200 15 minutes 52 seconds ago x 2008 2013 Amazon Web Services Inc or its affiliates All rights reserved Privacy Policy Terms of Use Feedback https console aws amazon com ec2 home region us east 1 BZ Figure 2 8 Reachability Status For An EC2 Instance Acting on an instance from the AWS EC2 Management Console An instance can be marked by clicking on it Clicking the Actions button near the top of the main center pane or equivalently from a right mouse button click in the pane brings up a menu of possible actions These actions can be executed on the marked instance and include the options to Start Stop or Terminate the instance Connecting to an instance from the AWS EC2 Management Console A marked and running instance can have an SSH connection made to it Clicking on the Connect button near the top of the main
57. info cgi 2011 CS CS 2011 09 Bright Computing Inc 5 4 Address Resolution In Cluster Extension Networks 49 5 4 2 Resolution In And Out Of The Cloud The networks their addresses their types and their domains can be listed from the network mode in cmsh bright71 gt network list Name key Type Netmask bits Base address Domain name bmcnet Internal 16 10 148 0 0 bmc cluster cloud Cloud 8 10 0 0 0 cloud cluster xternalnet External 16 10 2 0 0 brightcomputing com globalnet Global 0 0 0 0 0 cm cluster ibnet Internal 16 10 149 0 0 ib cluster internalnet Internal 16 10 141 0 0 eth cluster netmap NetMap 16 172 31 0 0 us east 1 Tunnel 16 i eller Ore In a Type 1 network section 3 3 6 of the Installation Manual the head node is connected to internalnet When a cloud service is configured the head node is also connected to the CMDaemon managed NetMap network It is useful to think of NetMap as a special network al though it is actually a network mapping from the cloud to internalnet That is it connects maps from the nodes in one or more cloud networks such as the us east 1 network provided by Amazon to IP addresses provided by netmap The mapping is set up when a cloud extension is set up With this mapping packets using NetMap go from the cloud via an OpenVPN connection to the NetMap IP address Once the packets reach the OpenVPN interface for that address which is actually on the head node they a
58. ing To The Cloud The configuration of data aware scheduling means configuring the cluster so that the tools that allow data aware scheduling to work correctly are configured The configuration that is carried out depends on the workload manager that is to be used If cmsub has not yet been set up or if it needs reconfiguration then the following steps should be carried out 1 The cmdaemon cmsub package is installed It must be installed on the head node and in the software image that is to be used for compute cloud nodes and storage cloud nodes Example root bright71 yum install cmdaemon cmsub ic eed root bright71 yum installroot cm images default image cmdaemon cmsub eee 2 The cmsub cloud storage setup utility is run Example runs are provided later starting on page 42 but an explanatory background is given here first The utility is part of the cluster tools package which is installed by default The utility e configures cmsub properties page 42 e creates page 42 templates for cloud storage nodes storage polices for cmsub Templates For Cloud Storage Nodes And Storage Policy Templates for cloud storage nodes area cloud node definition associated with a cloud provider Tem plates for cloud storage nodes more conveniently called template nodes provide a template that is used by the cloud storage nodes Template nodes being templates are never powered on and are therefore always in a Dow
59. ing the properties that have been assigned to it under Bright Cluster Manager become useless Bright Computing Inc Virtual Private Clouds A virtual private cloud is an implementation of a cluster on a virtual network in a cloud service provider The Amazon Virtual Private Cloud Amazon VPC is an implementation of such a virtual private cloud The Amazon VPC is documented more fully at http docs aws amazon com AWSEC2 latest UserGuide using vpc html Managing VPCs would normally require significant networking expertise Bright Cluster Manager makes it easier to do this so that the administrator can focus on using them productively instead of on working out VPC configurations The following VPC related terms are explained and compared in this chapter e EC2 Classic page 51 e EC2 VPC page 51 e classic cloud page 52 default VPC page 52 private cloud page 52 custom VPC page 52 elastic IP addresses page 56 6 1 EC2 Classic And EC2 VPC 6 1 1 EC2 Classic Vs EC2 VPC Overview So far this manual has discussed configuring clusters within Amazon EC2 The EC2 designation actu ally covers two kinds of platforms e EC2 Classic This platform provides an environment that corresponds to a physical network In stances in the same region exist on the same physical network and rely on explicitly configured security groups to restrict unauthorized access from other instances on the same network A cloud instance that
60. ing to cluster Removing all normal cloud nodes Removing all cloud director nodes removed eu west 1 director Removing all netmap and tunnel interfaces remove interface tun0 of bright71 remove interface mapO of bright71 remove interface map0 0 of bright71 updated bright71 remove interface mapO of node001 updated node001 remove interface mapO of node002 updated node002 Removing all tunnel networks removed eu west 1 Removing all cloud categories removed cloud director Removing all cloud networks removed cloud ec2classic Removing all netmap networks removed netmap Bright Computing Inc 4 5 Miscellaneous Cloud Commands 45 Removing all cloud providers removed Amazon EC2 Done root bright71 If the d dryrun option is used then it shows what the utility intends to remove during a run but without actually removing it Bright Computing Inc Cloud Considerations And Issues With Bright Cluster Manager 5 1 Differences Between Cluster On Demand And Cluster Extension Some explicit differences between Cluster On Demand and Cluster Extension clusters are Cluster On Demand Cluster Extension cloud nodes only in 1 region cloud nodes can use many regions no cloud director uses one or more cloud directors per region no failover head node failover head node possible no VPN or NetMap VPN and NetMap no externalnet interface on head can have an
61. king on the bottom leftmost naviga tion button of xpdf both navigate back to the previous document The manuals constantly evolve to keep up with the development of the Bright Cluster Manager envi ronment and the addition of new hardware and or applications The manuals also regularly incorporate customer feedback Administrator and user input is greatly valued at Bright Computing So any com ments suggestions or corrections will be very gratefully accepted at manuals brightcomputing com 0 3 Getting Administrator Level Support Unless the Bright Cluster Manager reseller offers support support is provided by Bright Computing over e mail via support brightcomputing com Section 10 2 of the Administrator Manual has more details on working with support Introduction In weather a cloudburst is used to convey the idea that a sudden flood of cloud contents takes place In cluster computing the term cloudbursting conveys the idea that a flood of extra cluster capacity is made available when needed from a cloud computing services provider such as Amazon Bright Cluster Manager implements cloudbursting for two scenarios 1 A Cluster On Demand or a pure cloud cluster chapter 2 In this scenario the entire cluster can be started up on demand from a state of non existence All nodes including the head node are instances running in a coordinated manner entirely inside the cloud computing service 2 A Cluster Extension or
62. le cmsub no Maximum number of storage nodes 5 Minumum EBS volume size 1GB Revision Storage node name prefix cstorage Template for cloud nodes atemplate Tunnel IP start address 0 0 100 0 cloudOperationTimeout 0 xportedDirectories home maxDownloadTime 7200 maxUploadTime 7200 name apolicy storageNodelIdleTimeLimit 900 Only one policy can be active at a time for a cloud object The cm cloud storage setup create session will prompt the administrator to set the policy to active during its session A pol icy can also be set to active within cloud mode of cmsh within the object by setting the value of activestoragenodepolicy to an existing policy Example bright71 gt cloud Amazon EC2 get activestoragenodepolicy apolicy bright71 gt cloud Amazon EC2 set activestoragenodepolicy bpolicy bright71 gt clouds Amazon EC2 commit get activestoragenodepolicy bpolicy Bright Computing Inc 44 Cloudbursting Using The Command Line And cmsh 4 5 Miscellaneous Cloud Commands 4 5 1 The cm cloud copy Tool The cm cloud copy tool is automatically installed with the cmdaemon cmsub package section 4 4 1 Its purpose is to transfer data to and from AWS storage It is used automatically as a backend to cmsub to create and remove AWS storage containers in AWS S3 and to upload and download files and directories to those containers The cm cloud copy tool can also be used as a standalone tool by the cluster administrat
63. louds 6 3 1 Subnets In A Custom VPC The components of a custom VPC include subnets the nodes that run in them and static IP addresses The subnets are logical network segments within the network range of that custom VPC Subnets can be thought of as interconnected with a central magic router with Bright Cluster Manager managing the routing tables on that router The routing ensures correct subnet communication Inside Bright Cluster Manager subnets are represented as a type of network section 3 2 of the Administrator Manual with a value for type set to CLOUD Subnets for a custom VPC must have non overlapping ranges If there are multiple custom VPCs being managed by Bright Cluster Manager then a particular subnet may be assigned to one custom VPC at the most Two series of valid network ranges could be Example 1 10 0 0 0 10 0 31 255 10 0 0 0 19 10 0 32 0 10 0 63 255 10 0 32 0 19 10 0 64 0 10 0 95 255 10 0 64 0 19 2 192 168 0 0 192 168 0 255 192 168 0 0 24 192 168 1 0 192 168 1 255 192 168 1 0 24 The sipcalc command page 58 of the Administrator Manual is a useful tool for calculating appro priate subnet ranges At least one subnet must be assigned to a custom VPC before an instance can be created in that cloud Typically two or more subnets are assigned as shown in the custom VPC creation example in the following section 6 3 2 Creating The Custom VPC After subnets have been configured a custom VPC can
64. mazon cloud network service assigns the addresses in this network to the cloud director and regular cloud nodes An explanation of the networks mentioned in the preceding list follows e The nodes within all available cloud networks all networks such as for example us east 1 us west 1 and so on are given CMDaemon assigned addresses in the cloud node space range 172 16 0 0 172 30 255 255 In CIDR notation that is 172 16 0 0 12 172 16 0 0 172 31 255 255 ex cept for 172 31 0 0 16 172 31 0 0 172 31 255 255 Bright Computing Inc 50 Cloud Considerations And Issues With Bright Cluster Manager e The network address space 172 31 0 0 16 172 31 0 0 172 31 255 255 is taken by the CMDaemon assigned NetMap network explained shortly The addressing scheme for each cloud network is assigned as suggested in figure 3 5 e Each node in a cloud network is also assigned an address in the network addressing space pro vided by Amazon The assignment of IP addresses to nodes within the 10 0 0 0 8 range is decided by Amazon via DHCP e The netmap network figure 5 1 is a helper mapping reserved for use in routing from the cloud that is from a cloud director or a cloud node to a regular node The mapping uses the 172 31 0 0 16 addressing scheme Its routing is asymmetrical that is a NetMap mapping from a regular node to the cloud does not exist Packets from a regular node to the cloud do however resolve to the cloud network as indi
65. mpleuser brightcomputing com AWS Account ID I for information 313234312222 Access Key ID I for information OUPOUASOUDSSSAOU Secret Access Key I for information Aighei8EooLilDae8Nio5ohl4ieXiAiaiV Verifying Amazon credentials Bright License Bright Product Key I for information 423112 231432 134234 132423 134221 Country US State CA Locality San Francisco Organization name Bright Computing Organizational Unit Development Cluster Name demo cluster Head Node Hostname bright71 Administrative Password Verify password Do you want to create a second drive for more storage capacity I for information YES no no Extra storage for home I for information NO yes n Extra storage for monitoring data I for information NO yes n Compute Nodes Instance Type I for information ml small ml medium cl medium ml large tl micro m2 xlarge m2 2xlarge m2 4xlarge cl xlarge tl micro gt tl micro Node Count 2 2 Base name I for information cnode cnode Instances of type tl micro need to use EBS storage Bright Computing Inc 16 Cluster On Demand Cloudbursting Size of EBS GB 40 15 Do you want to configure more node types NO yes no Workload Management system Which workload management system do you want to use I for information slurm sge torque slurm gt slurm Number of slots per node 8
66. n com ec2 home region us east 1 s Instances EC2 Management Console Ga Services v v N Virginiay Help v EC2 Dashboard Launch Instance Actions v C Viewing All Instances 7 Allinstance Types 7 J 1torro0farinstances gt gt Instances O Name instance AMI ID Root Device Type State Status Alarm St Monitoring Security Gi Spot Requests Events INSTANCES Reserved instanced examplecluster i g0718213 ami Oc2f8a65 ebs tl micro running amp init none H basic quicklau IMAGE AMIs Bundle Tasks us east 1 direct i et7p p91 ami 543baa3c ebs mi large stopped none basic brightclo us east 1 direct i testcssa ami e04cde8 ebs tl micro stopped none basic brightclo C piotr cluster on f i a4d5b5d4 ami 0c2f8a65 ebs ml smal stopped none basic quicklaui Oo o 1 EC2 Instance selected ELASTIC BLOCK EC2 Instance examplecluster i 907182f3 e A Volumes Snapshots ec2 50 16 44 106 compute 1 amazonaws com NETWORK amp SECURI Description Status Checks Monitoring Tags s G eeun oraups brightheadnode 6 0 centos6 xen ami 0c2f8a65 Elastic IPs Placement Groups Load Balancers Type tL micro State running Alarm Status none Zone us east ld Security Groups quicklaunch 2 view rules Key Pairs Scheduled Events No scheduled events Owner 137677339600 VPC ID Subnet ID SourceMest Check Virtualization paravirtual 2008 2013 Amazon Web Services Inc o
67. n state in cmsh and cmgui Actual cloud storage nodes on the other hand can be powered on by the cluster manager so that they can be used to store cloud job data In addition any network interfaces associated with a template node can generally be regarded are non functioning as far as the administrator is concerned One feature of template nodes however is that the tunnel IP address set in the template is an offset to the network address that will be used to assign IP addresses to actual storage nodes A storage policy defines other parameters for how storage for cloud jobs is handled Its parameters include e Name the name set for the policy e Bucket Name the S3 bucket used for cloud jobs to transfer input and output job data e Default job output size specifies the default free storage space that will be provisioned for the result that a job produces Bright Computing Inc 42 Cloudbursting Using The Command Line And cmsh e Storage node name prefix specifies a prefix for how storage nodes are to be named The prefix is cst orage by default The number suffix scheme is as for regular nodes Thus by default the storage nodes are cstorage001 cstorage002 and so on e Template for cloud nodes the template to use as the prototype for storage nodes Example Configuration Of cmsub Properties A session with cm cloud storage setup that configures cmsub properties on a cloud deployment is Example root bright71
68. ne command instead as described in section 4 3 After creation individual cloud nodes can be powered up from within cmgui by a right click on the cloud node resource item figure 2 12 Bright Computing Inc 2 4 Cluster On Demand Cloud Node Start up 19 X Bright Cluster Manager ooa Hle Monitoring View Bookmarks Help RESOURCES cnode001 E Bright 5 2 Cluster vd Switches Overview Tasks Settings cloud Settings System Information Services Pr v Networks ca globalnet internalnet Hostname cnode001 Running Jobs Mj Power Distribution Units Wama v Software Images State Down Internal ip detected 10 235 51 56 2 default image Gi Node Categories Power cloud amp default v Head Nodes Load O 1 min O 5 min O 15 min E headnode v Racks Uptime O days O hours O minutes vH 52 Memory v Chassis Ea Gl Gi Virtual SMP Nodes Swap Memory vig Nodes OB out of OB v Cloud Nodes CPU Usage VW Amazon EC2 O u O sS O O0 OKI en cnode00l Power E cnode002 Power off 5 bs To o Power reset EVEN VIEWER mt q Terminate o All Events Shutdown vi Time a Reboot Message vB Q 23 Apr 2012 17 10 i Drain Power on cnode001 i 23 Apr 2012 17 0 Undrain Check DevicelsUp is in state PASS on headnode 23 Apr 2012 17 0 Service slurm was restarted on headnode 23 Apr 2012 17 0 Open Service munge was started on headnode oO 23 Apr 2012 17 0 Close Service slurm was star
69. nnect to your instance using its Public DNS ec2 54 220 69 16 eu west 1 compute amazonaws com Example ssh i pjeukeypair pem rootGec2 54 220 69 16 eu west 1 compute amazonaws com Please note that in most cases the username above will be correct however please ensure that you read your AMI usage instructions to ensure that the AMI owner has not changed the default AMI username If you need any assistance connecting to your instance please see our connection documentation Close Figure 2 9 SSH Instructions To Connect To The Marked Instance Viewing the head node console The head node takes about 2 minutes to start up If on following the instructions an SSH connection cannot be made then it can be worth checking the head node system log to check if the head node has started up correctly The log is displayed on right clicking on the Actions button and selecting the Get System Log menu item figure 2 10 A successful start of the system generates a log with a tail similar to that of figure 2 10 Bright Computing Inc 2 2 Cluster On Demand Head Node Login And Cluster Configuration 13 Services v Edit v zi Cancel X Launch Instance Actions ee a Viewing All Instances CO Name Instance exampleciuster gj i 609999 1EC2 Instance selected EC2 Instance examplecl C2 23 20 123 252 computes Description Status Checks Close Figure 2 10 System Log Of The Checkboxed
70. no 172 16 0 1 eu west 1 o bright 71 gt devicex cnode001 gt interfaces commit The preceding session completes the cloud node object configuration The cloud node itself can now be launched with an explicit power command such as bright71 gt device cnode001 gt interfaces device power on n cnode001 4 3 2 Creating And Powering Up Many Nodes For a large number of cloud nodes the creation and assignment of IP addresses can be done with the clone option of the foreach command section 2 5 5 of the Administrator Manual together with a node range specification This is the same syntax as used to create non cloud regular nodes with cmsh Continuing on with the preceding session where a node cnode001 was configured bright71 gt device foreach clone cnode001 n cnode002 cnode010 The IP of network interface ethO was not updated Warning The Ethernet switch settings were not cloned and have to be set manually bright71 gt devicex commit Mon Apr 23 04 19 41 2012 alert cnode002 Check DeviceIsUp is in state FAIL on cnode002 bright71 gt device Mon Apr 23 04 19 41 2012 alert cnode003 Check DeviceIsUp is in state FAIL on cnode003 Successfully committed 9 Devices bright71 gt device The IP addresses are assigned via heuristics based on the value of cnode001 and its cloud director As before an alert warns each cloud node is down The list of cloud nodes can be powered up using
71. not provide an EC2 Classic platform However to maintain backward compatibility for users who are migrating to EC2 VPC and who have applications that run on the EC2 Classic platform Amazon provides the defaultVPC instance on the EC2 VPC platform 6 1 3 The Classic Cloud And The DefaultVPC Instances The classic cloud is a cloud instance that EC2 Classic supports The defaultVPC instance is a special VPC instance that emulates EC2 Classic behavior on the EC2 VPC platform This allows legacy applications that do not support EC2 VPC to run on it A legacy application that runs in a defaultVPC instance may be thought of as having its EC2 Classic API calls translated into EC2 VPC API calls The defaultVPC instance is available in all regions that do not offer the EC2 Classic platform There is one major difference between the network environments of EC2 Classic and the default VPC instance For EC2 Classic instances the base address of network inside Amazon is 10 0 0 0 8 In contrast for defaultVPC instances the base address is 172 31 0 0 16 When creating a new cloud provider account Bright Cluster Manager automatically detects which regions offer the EC2 Classic platform and which do not The suggested base address of the cloud network that is to be created is then automatically matched according to the regions The platform supported EC2 Classic or EC2 VPC is also displayed in cmgui when the cloud director is being created A few Amazon AWS acc
72. object A new static IP address is then made available and can be assigned to instances running within custom VPCs After allocation the static IP address can be assigned and reassigned to any instance inside any custom VPC created within the region in which the IP address was allocated Example bright71 cloud use amazonec2 bright71 gt cloud Amazon EC2 staticip allocate us west 1 Allocating Static IP Please wait Successfully allocated the following static IP 54 215 158 42 bright71 gt cloud Amazon EC2 staticip list Cloud Provider Cloud Region Static IP Assigned to Amazon EC2 us west 1 54 215 158 42 lt not assigned gt bright71 gt cloud Amazon EC2 An allocated static IP can be released with the staticip release command in cmsh Example bright71 gt cloud Amazon EC2 staticip release 54 215 158 42 Releasing static IP 54 215 158 42 Please wait Successfully released the static ip bright71 gt cloud Amazon EC2 Once the IP address has been released it may no longer be used for instances defined in the custom VPC The staticips command lists all allocated static IPs for all configured cloud providers The staticip list command lists static IP addresses for the currently active cloud provider ob ject In cmgui the static IPs can be managed via the Static IPs tab of a cloud provider object Bright Computing Inc 6 3 Setting Up And Creating A Custom VPC 57 6 3 4 Subnets
73. ollowing issues Bright Computing Inc 14 Cluster On Demand Cloudbursting e The license agreement e Amazon Web Services account information This asks for the AWS Username AWS Account ID Access Key ID and Secret Access Key These are needed by Bright Cluster Manager to manage the cloud node instances e The installation of the Bright Computing product key formatted like 868868 797099 979199 091301 134414 This is the cloud version of the request license command in section 4 3 of the Installation Manual and asks for The organization information for the license This requires input for the fields country state locality organizational unit unit and cluster name The values to be used for the head node machine name and its administrative password used for the root and MySQL passwords e Optionally setting up the secondary drives using Amazon s EBS service e Optionally setting up extra storage for home using Amazon s EBS service e Optionally setting up extra storage for monitoring data recommended for more than 500 nodes e Setting up cloud node instance types Amazon instance types http aws amazon com ec2 instance types are choices presented from node specifications consisting of memory stor age cores GPUs and others The setting up of the instance type step is looped through if necessary to allow more than one instance type to be configured Setting up the number lt N gt o
74. ommands can launch the required cloud nodes sections 4 2 and 4 3 4 1 The cm cloud setup Script The cm cloud setup script is run on the head node and allows the administrator to specify settings to launch a cloud using the command line The help text for this utility shows USAGE cm local apps cluster tools bin cm cloud setup lt OPTIONS gt OPTIONS p provider lt name gt Provider name default amazon n name lt name gt Account name default Amazon EC2 u username lt username gt Username used in Amazon AWS console Ww password lt password gt Password used in Amazon AWS console if omitted you will be prompted unless account keys are provided accountId Amazon account ID k awskey lt key gt AWS access key ID secretkey lt key gt AWS secret access ID q delete Delete Amazon account if it exists y yes Use all h help Print this help NOTES password option does not work yet Bright Computing Inc 38 Cloudbursting Using The Command Line And cmsh It can be used as follows from the prompt Example root bright71 cm cloud setup u rotwang example com a 123923792991 k OIQQOWU9SLJJEI1232PIP s ra9xaG7oUiyluqu0ahW4aixuTheeS5ahmUGoh9cha The administrator is then guided through the steps needed to launch the cloud The session output may show up as something like some text elided Example Connecting to cluster Waiting for data from cluster A
75. or directly However because its behavior may change due to development it should only be used if the admin istrator has explicitly been instructed to do so by Bright Computing engineers At the time of writing October 2015 its use requires that the cm cloud copy module is loaded A short help can then be seen on running cm cloud copy without options while more information and examples can be found in the cm cloud copy 1 man page 4 5 2 The cm cloud check Utility The cm cloud check utility checks the current cloud bursting configuration for possible problems and misconfigurations It reports any potential issues The tool also tests communications with Amazon using some simple Amazon API calls Only a handful of tests are performed at present More tests will be added over time 4 5 3 The cm scale cluster Utility The cm scale cluster utility is a Bright Cluster Manager utility that allows workload managers to scale a cluster up or down in size depending on job requirements and administrator preferences This can improve cluster efficiency by cutting down on needless energy consumption The development of the utility was originally aimed at cloud use but it is now a general cluster management utility Its use is covered in section 7 9 2 of the Administrator Manual 4 5 4 The cm cloud remove all1 Utility This utility simply removes all clouds and associated objects Example root bright71 cm cloud remove all Connect
76. or the appropriate XEN or HVM head node AMI then brings up the next step in the launch wizard e Step 2 Choose an Instance Type This displays a micro instance by default figure 2 5 Bright Computing Inc 2 1 Cluster On Demand Launching The Head Node From The Cloud Provider 7 va E 0O06 File Edit View History Bookmarks Tools Help i EC2 Management Console Oa 2 https console aws amazon com ec2 v2 home region eu west 1 LaunchinstanceWizard Services v Martijn de Vries v Irelandy Help v 1 Choose AMI 2 Choose Instance Type 3 Configure Instance 4 Add Storage 5 Tag Instance 6 Configure Security Group 7 Review Step 2 Choose an Instance Type Amazon EC2 provides a wide selection of instance types optimized to fit different use cases Instances are virtual servers that can run applications They have varying combinations of CPU memory storage and networking capacity and give you the flexibility to choose the appropriate mix of resources for your applications Learn more about instance types and how they can meet your computing needs Currently selected t1 micro up to 2 ECUs 1 vCPUs 0 613 GiB memory EBS only All instance types Micro instances Micro instances are a low cost instance option providing a small amount of CPU resources They are suited for lower throughput applications and websites that require additional compute cycles periodically but are not appropriate for applications that require sustaine
77. ouds tab clicking the Add button launches a dialog box to create a custom VPC 3 Subnet Setup And Custom VPC Creation Using cmsh Similarly with cmsh the subnets to be used for the custom VPC are created first before creating the private cloud as shown in the following examples e Subnet creation and cloning In the following example session an arbitrary naming scheme is used for subnets with a pattern of lt name of custom VPC gt sn lt number gt Here sn is an arbitrary abbreviation for subnet Example bright71 gt network add vpc 0 sn 0 set type cloud set baseaddress 10 0 0 0 set netmaskbits 24 set ec2availabilityzone eu west la bright71 gt networks vpc O0 sn 0x bright71 gt networks vpc 0 sn 0x bright71 gt network vpc 0 sn 0x bright71 gt network vpc 0 sn 0 JP A oP bright71 gt networks vpc 0 sn 0 commit Setting the ec2availabilityzone property is optional It causes the subnet to be created in a specific availability zone Leaving its value empty creates the subnet inside a randomly chosen availability zone Having all subnets of the custom VPC inside the same availability zone is ad vised for better network performance The availability zone set for the network must be one of the availability zones available for the region inside which the private cloud will be created Once the first subnet has been created it can be cloned Example
78. ounts provide the EC2 Classic platform for only a certain subset of all avail able regions and provide EC2 VPC in other regions In such a case when a new cloud provider account is created in Bright Cluster Manager with a cloud director in both types of platforms then two cloud networks can be created If only a single cloud director is run then only one network is created and the network base address in that case depends on the platform EC2 Classic or EC2 VPC that it is run on However if two cloud directors are started up with each cloud director on a different platform then one cloud director runs on one platform and associated network and the other cloud director on the other platform and associated network 6 1 4 The Private Cloud And Custom VPC Instances A private cloud without the virtual in front is the term used in the Bright Cluster Manager manuals as well as by Amazon and in general for a general VPC instance A custom VPC is the term used in the manual to mean a general VPC instance but one that is not a default VPC instance Thus in terms of math sets Bright Computing Inc 6 2 Comparison Of EC2 Classic And EC2 VPC Platforms 53 private clouds custom VPCs defaultVPCs In the context of Amazon VPCs the term private cloud is often used by administrators by con vention and for convenience to mean the more precise term of custom VPC as defined here implic itly ignoring possible defaultVPC instances
79. p of a cloud provider account the following steps can be followed to launch Cluster Extension cloud nodes 1 The cloud provider is logged into from cmgui and a cloud director is configured section 3 1 2 The cloud director is started up section 3 2 3 The cloud nodes are provisioned from the cloud director section 3 3 The cloud nodes then become available for general use by the cluster Cluster Extension Cloudbursting With A Hardware VPN Bright Cluster Manager recommends and provides OpenVPN by default for Cluster Extension cloud bursting VPN connectivity If there is a wish to use a hardware VPN for example if there is an existing hardware VPN network already in use at the deployment site then Bright Cluster Manager can option ally be configured to work with the hardware VPN The configuration details can be found in the Bright Computing knowledgebase at http kb brightcomputing com by carrying out a search on the site using the keywords cloudbursting without openvpn 3 1 Cluster Extension Cloud Provider Login And Cloud Director Configuration To access the Amazon cloud service from cmgui the Cloud Nodes resource is selected and the Cloud Accounts tabbed pane opened This allows a cloud provider account to be edited or deleted from the available ones already there It also allows a new cloud account provider to be added and configured This is done by clicking on the H button beside the text Add a new
80. r its affiliates All rights reserved Privacy Policy Terms of Use Feedback Figure 2 7 The EC2 Instances List System Amazon machine infrastructure and instance instance running under the infrastructure reachabilities are similarly shown under the neighboring Status Checks tab figure 2 8 Bright Computing Inc 2 1 Cluster On Demand Launching The Head Node From The Cloud Provider 11 EC2 Management Console Iceweasel ooa File Edit View History Bookmarks Tools Help e gt v i x M n EE https console aws amazon com ec2 home region us east 1 s Instances v EC2 Management Console oF Z Services v Edit v v N Virginiay Helpv EC2 Dashboard Launch Instance Actions v C Events 4 Viewing All Instances All Instance Types bd 1to 11 of 11 Instances Instances O Name Instance AMI ID Root Device Type State Status Alarm St Monitoring Security Gi Spot Requests a BA i i i i Te i i Reasivad Instanead E examplecluster i 907182f3 ami 0c2f8a65 ebs tL micro running 4 1 2 none basic quicklaury piotr cluster on E i a4d5b5d4 ami 0c2f8a65 ebs mi smal stopped none basic quicklaun es O us east l direct i e17b6b91 ami 543baa3c ebs mi large stopped none basic AM Mls 1 sus east 1 direct i testc46d ami eO4cde8 ebs tl micro stopped none basic brightclou Bundle Tasks w 1EC2 Instance selected Volumes EC2 Instance examplecluster i 907182f3 e A Snaps
81. re 2 4 EC2 Choosing An AMI Step 1 The default AMIs can be ignored Clicking on the Community AMIs link in the left navigation pane brings up a new display of community AMIs Entering a search text of brightheadnode then shows only the AMIs appropriate for a Bright Cluster Manager head node instance in a Cluster On Demand cluster These are 1 An AMI that uses standard XEN paravirtualization technology This is available for all re gions If this image is used hardware virtualization extensions acceleration is not imple mented even if available in the underlying cloud node hardware 2 An AMI with hvm in the name This is available for some regions It is intended for use in regions that support HVM Hardware Virtual Machines HVM requires that the CPU used has the Intel VT or AMD V virtualization extensions to implement hardware acceleration for virtualized machines At the time of checking April 2013 Regions supporting HVM are eu west 1 us east 1 and us west 2 Instance types supporting HVM are the m3 xlarge instance type and higher Instance types http aws amazon com ec2 instance types are a way of characteriz ing machine specifications such as whether it has more RAM more cores or HVM Updated details on the regions and instance types that Amazon EC2 supports can be found via the Amazon website http docs aws amazon com AWSEC2 latest UserGuide instance types html Clicking on the Select button f
82. re forwarded via Shorewall s IPtables rules to their destination nodes on internalnet With default settings nodes on the network internalnet and nodes in a cloud network such as us east 1 are both resolved with the help of the cm cluster domain defined in globalnet Fora cluster with default settings and using the cloud network us east 1 the resolution of the IP address of 1 a regular node and 2 a regular cloud node takes place as follows 1 node001 a regular node in the internalnet network is resolved for node001 cm cluster to a 10 141 0 1 when at the head node The cluster manager assigns this address which is on internalnet It could also be an ibnet address instead such as 10 149 0 1 if Infini Band has been configured for the nodes instead of Ethernet b 172 31 0 1 when at the cloud director or regular cloud node The cluster manager assigns this address which is a NetMap address It helps route from the cloud to a regular node It is not actually an IP address on the interface of the regular node but it is convenient to think of it as being the IP address of the regular node 2 cnode001 a regular cloud node in the us east 1 network is resolved for cnode001 cm cluster to a 172 21 0 1 when at the head node The cluster manager assigns this address which is an OpenVPN tunnel address on us east 1 b an IP address within 10 0 0 0 8 10 0 0 1 10 255 255 254 when at a regular cloud node or at a cloud director The A
83. rk device name IP Network Bright Computing Inc 58 Virtual Private Clouds physical eth0 dhcp 0 0 0 0 cloud tunnel tun0 prov LIZ LEs 255291 us west 1 Once a cloud node instance has been instantiated inside a specified subnet it cannot be reassigned to a different subnet nor can it be reassigned to a different custom VPC The cloud instance must first be terminated and reconfigured Only then can it be powered on inside a different subnet 6 3 6 Creating A Cloud Director In A Custom VPC To create a cloud director in a custom VPC using cmgui the cloud director must first be created inside the EC2 Classic platform region in which the custom VPC is created This can be done via the Add Cloud Director button inside the Overview tab of a cloud provider account After this has been done the cloud director must be moved from the EC2 Classic platform to the custom VPC as explained in section 6 3 8 6 3 7 Creating Cloud Compute nodes In A Custom VPC Creating cloud compute nodes inside a custom VPC can be done in a similar way to creating cloud compute nodes for the EC2 Classic platform That is by clicking the Create Cloud Nodes button in the overview tab of the cloud provider in cmgui However to create a cloud node inside the custom VPC a subnet of the custom VPC must be specified when selecting the network of the eth0 interface of the node To avoid confusion it is sensible to make this a different subnet from the one in which the
84. rk is used to make local cluster nodes accessible from the cloud All nodes in the local cluster will be assigned an IP address in the NetMap network Please choose an unused IP subnet for the NetMap network NetMap network netmap J 172 31 0 0 I 16 Figure 3 3 Setting The NetMap Network With cmgui The default values are normally a good choice On clicking the Next button the values are pro cessed The next screen figure 3 4 displays the cloud network name and addressing scheme This can be changed if needed but for Amazon the 10 0 0 0 8 range is expected The cloud network is a network that represents the internal network of the cloud provider Under normal circumstances the 10 0 0 0 8 range should be used for Amazon EC2 Use existing cloud network x e Create new cloud network cloud a 10 0 0 0 I 8 Figure 3 4 Setting The Cloud Network At The Cloud Provider With cmgui On clicking the Next button the configuration is processed The next screen figure 3 5 displays a proposed Bright Cluster Manager tunnel network naming and addressing scheme for each checkboxed cloud region These can be changed if needed from the sug gested defaults For Amazon the us east 1 region shown in the figure has a default tunnel network value of 172 21 0 0 16 Bright Computing Inc 26 Cluster Extension Cloudbursting x Add Cloud Provider Wizard e089 For each of the cloud regions that will
85. stance ID not set No power control UNKNOWN headl headl gt device power on n cnode002 Bright Computing Inc 20 Cluster On Demand Cloudbursting CLOU aaia e Wo eae ee ees ON cnode002 headl gt device power status CLOW oa dbo s tn ee head ON cnode001 running ELOU e 6k ee OES OFF cnode002 pending No power control UNKNOWN headl headl gt device ping c1 cnode001 ping unknown host cnode001 headl gt device status MEAG yanlara iaia aS UP MOCSOU0L wca whee w ed ea Ke bees UP sakele 0O LE OEE S E Ee ERS DOWN head1 gt device ping c1 cnode001 PING cnode001 cm cluster 10 234 226 155 56 84 bytes of data 64 bytes from cnode001 cm cluster 10 234 226 155 icmp_seq 1 ttl 63 t ime 3 94 ms Multiple cloud nodes can be powered up at a time in cmsh with the power on command using ranges and other options section 4 2 2 of the Administrator Manual 2 4 1 IP Addresses In The Cluster On Demand Cloud e The IP addresses assigned to cloud nodes on powering them up are arbitrarily scattered over the 10 0 0 0 8 network and its subnets No pattern should therefore be relied upon in the addressing scheme of cloud nodes e Shutting down and starting up head and regular cloud nodes can cause their IP address to change However Bright Cluster Manager managing the nodes means that a regular cloud node re establishes its connection to the cluster when it
86. story Bookmarks Tools Help e K x ae amazon com https console aws amazon com ec2 v2 home region us east 1 i EC2 Management Console Services v E v N Virginia y EC2Dashboard E ee Feedback B Event aia Create Instance Feedback Report an Issue To start using Amazon EC2 you will want to launch a virtual server known as an Amazon EC2 instance Instances Spot Requests Launch Instance Reserved Instances Note Your instances will launch in the US East N Virginia region E Onninn lanlth A ean dilad Funnin 13 Amazon Web Services l rights reserved Privacy Policy Terms of Use Feedback pe e e TZ Figure 2 3 The EC2 Dashboard With The Launch Instance Button In the main pane of the dashboard is the Launch Instance button Clicking it starts up Amazon s Launch Instance Wizard Amazon documentation for the wizard is at http docs aws amazon com AWSEC2 latest UserGuide launching instance html Using the wizard to launch a head node instance is described next 2 1 2 Launching The Head Node Instance To start a Cluster On Demand cluster a head node instance must first be launched This can be done as follows e Step 1 Choose an Amazon Machine Image AMI The first step in the wizard offers a choice of Select buttons to launch an instance from an AMI image figure 2 4 Bright Computing Inc 6 Cluster On Demand Cloudbursting v EC2 Management Console
87. t UserGuide InstanceStorage html StorageOnInstanceTypes Ephemeral means that the device is temporary which means that whatever is placed on it is lost on reboot 2 Elastic Block Storage EBS volumes Normally EBS is suggested for cloud director and cloud node use The reasons for this include e it can be provided to all nodes in the same availability zone e unlike instance storage EBS remains available for use when an instance using it reboots e instance storage is not available for some instances types such as t1 micro Using the ephemeral device as the drive for the cloud director Since the cloud provider instance type is essential and contains so much data it is rarely wise to use ephemeral devices as the drive for the cloud provider However if for some reason the administrator would like to avoid using EBS and use the instance storage then this can be done by removing the default EBS volume suggestion for the cloud director provided by Bright Cluster Manager When doing this the ephemeral device that is used as the re placement must be renamed It must take over the name that the EBS volume device had before it was removed e In cmgui this can be done in the Cloud Settings tab of the Cloud Nodes director item e In cmsh this can be done in device mode by going into the cloudsett ings submode for the cloud director and then going a level deeper into the storage submode Within the storage submode the 1ist comman
88. ted on headnode Oo 23 Apr 2012 17 0 Service slurmdbd was started on headnode 23 Apr 2012 17 0 TOPE SREI Service postfix was restarted on headnode A_ Aneu s Remote Console ervice named was restarted an headnade lindata Figure 2 12 Powering on a cloud node with cmgui As with regular non cloud nodes multiple cloud nodes can be powered up in cmgui by selecting them from the Overview tabbed pane Switching to the Tasks tabbed pane and clicking on the power on button then powers them up As with regular non cloud nodes cloud nodes can also be powered up from within the device mode of cmsh The initial power status section 4 1 of the Administrator Manual of cloud nodes is FAILED because they cannot be communicated with As they start up their power status changes to OFF and then to ON Some time after that they are connected to the cluster and ready for use The device status as opposed to the power status remains DOWN until it is ready for use at which point it switches to UP Example headl gt device power status COU ute ee ROE FAILED cnode001 Cloud instance ID not set ELOU cH ee ek wo tan eee ns FAILED cnode002 Cloud instance ID not set No power control UNKNOWN headl headl gt device power on n cnode001 GLOW aaa e erase aie aE E E ON cnode001 headl gt device power status CLOUG sie Rd wk dees be aes OFF cnode001 pending COU peee dae E eee FAILED cnode002 Cloud in
89. the connected subnet if any of that network Therefore when the cloud node is being created inside EC2 the CMDaemon must tell the EC2 envi ronment which of these networks is going to be attached to the eth0 interface of the newly created cloud node This information is deduced by CMDaemon by looking at the interface configuration of the cloud node Bright Cluster Manager More specifically it is deduced from the value set for network in the cloud node s eth0 interface settings If that network is part of a custom VPC that is if it is a subnet then the node starts inside the custom VPC instance Otherwise it starts inside the EC2 Classic or defaultVPC instance in that region For example the cloud director node is started inside the vpc 0 sn 0 network in the following session It is considered a custom VPC node and starts up inside the EC2 VPC platform Example bright 71 gt device us west l1 director gt interfaces list Type Network device name IP Network physical eth0 dhcp 0 0 0 0 vpc 0 sn 0 tunnel tun0 prov L72 18 255 251 us west 1 In contrast if the cloud network assigned to the eth0 interface is the cloud network representing the network environment of an EC2 Classic or defaultVPC cloud then the node is considered to be an EC2 Classic node It then starts up inside the EC2 Classic platform by default Example bright71 gt device us west 1 director gt interfaces list Type Netwo
90. the product key The product key must also be registered on the Bright Computing Customer Portal website at http www brightcomputing com Customer Login php A Customer Portal account is needed to do this Bright Computing Inc 22 Cluster Extension Cloudbursting The product key is submitted at the Customer Portal website specifically for a Cluster Extension setup from the Burst menu The customer portal account is then automatically associated with the license installed section 2 2 on the head node The key is also needed to activate the cluster license if that has not been done before e An Amazon account if the cloud provider is Amazon e An open UDP port By default this is port 1194 It is used for the OpenVPN connection from the head node to the cloud and back To use TCP and or ports other than 1194 the Bright Computing knowledgebase at http kb brightcomput ing com can be consulted using the keywords openvpn port Outbound ssh access from the head node is also useful but not strictly required By default Shorewall as provided by Bright Cluster Manager on the head node is configured to allow all outbound connections but other firewalls may need to be considered too Steps Cluster Extension cloudbursting uses a cloud director A cloud director is a specially connected cloud node used to manage regular cloud nodes and is described more thoroughly in section 3 2 Assuming the administrator has ownershi
91. to assign a public IP address to a custom VPC cloud EIP addresses are the public IP addresses that Amazon provides for the AWS account These ad dresses are associated with defaultVPC and EC2 Classic cloud instances by Amazon by default These addresses can also be associated with custom VPC instances The public addresses in the set of addresses can then be used to expose the custom VPC instance In this manual and in Bright Cluster Manager EIPs are referred to as static IPs in the cloud context When allocating a static IP addres the exact IP ad dress that is allocated is a random IP address from the set of all public IP addresses made available in the specified region by the configured cloud provider Automatic allocation of static IP addresses When a cloud director instance is started inside a custom VPC CMDaemon automatically allocates and assigns a static IP address to it By default the static IP address is automatically released when the cloud director instance is terminated This behavior can be changed in the CMDaemon cloud settings for the cloud director Manual allocation of static IP addresses It is also possible to manually allocate a static IP address to a cloud director using cmgui or cmsh Allocating a static IP address in cmsh is done using the staticip allocate command followed by the string indicating the region in which the static IP address is to be allocated In cmsh the command is issued inside a cloud provider
92. tory root bright71 cmsh c softwareimage provisioningstatus a Request ID s 5 Source node bright71 Source path cm shared Destination node us east 1 director Destination path cm shared After the shared directory and the cloud node software images are provisioned the cloud director is fully up Cloud node instances can then be powered up and provisioned from the cloud director 3 3 Cluster Extension Cloud Node Start up The Create Cloud Nodes wizard button in cmgui conveniently creates cloud node objects The wizard is accessed from within the Cloud Nodes resource by selecting the provider item and then choosing the Overview tab Cloud node objects can also be created in cmsh as described in section 4 3 A working cloud director is not needed to configure the regular cloud nodes However the cloud director must be up and the associated networks to the regular cloud nodes and to the head node must be configured correctly in order for the regular cloud nodes to boot up properly If needed additional cloud provisioning nodes section 5 2 of the Administrator Manual can be configured by assigning the provisioning role to cloud nodes along with appropriate nodegroups page 153 of the Administrator Manual values in order to create a provisioning hierarchy By default the first screen of the wizard figure 3 9 allows the administrator to do the following e The first regular cloud node and last regular cloud
93. ud externalnet faa oe Penden nternalne netmap Last node cnode016 us east 1 b 9 Power Distribution Units sy gt E Software Images Region us east 1 Spare Capacity gt Gj Node Categories via Hand Nodak Type tl micro Spare Capacity E bright60 Spot price N A V Persistent request gt Racks gt chassis Storage 40 GiB gt Virtual SMP Nodes gt Nodes via Cloud Nodes he Spare Capacity G us east 1 director gt Sj GPU Units gt other Devices gt O Node Groups A Users amp Groups op Workload Management A Monitoring Configuration Cancel Previous Next amp Authorization Authentication Open Adc Remove Create Cloud N Aia Figure 3 9 Main Cloud Node Creation Wizard Configuration Screen e for nodes in the associated cloud network e for nodes in the associated tunnel network By default both these IP offsets are 0 0 0 0 Bright Computing Inc 34 Cluster Extension Cloudbursting File Monitoring View Help Bright 6 0b Cluster Vee My Clusters Bright 6 0b Cluster b switches vi Networks cloud externalnet globalnet internalnet netmap us east 1 gt C Power Distribution Units gt E Software Images b Node Categories v Head Nodes Ef bright60 b 0 Racks gt chassis gt i virtual SMP Nodes b Nodes dj Cloud Nodes Cancel Previous Next Spar Providerw Hostname Type v

Cloudbursting Manual - Support

Contents

Download Pdf Manuals

Related Search

Related Contents