CycleServer Grid Engine Support Install Guide. version

Transcription

1 CycleServer Grid Engine Support Install Guide version

2 Contents CycleServer Grid Engine Guide 1 Administration 1 Requirements 1 Installation 1 Monitoring Additional Grid Engine Clusters 3 Monitoring Additional Ganglia Clusters 4 Upgrading to a New Version 4 Appendix 4

3 CycleServer Grid Engine Guide Administration Requirements Before proceeding with the installation, please make sure the following prerequisites are met: A 32-bit or 64-bit Linux distribution. At least 8GB RAM. 2 or more cores. At least 50GB free disk space. Administrator (root) privileges. Open Grid Scheduler (OGS) or Sun Grid Engine (SGE) 6.2u6 or higher. Ganglia with a running gmetad daemon, monitoring all nodes in the cluster. Recommended: Chef client running on all nodes in the cluster. The scheduler host must be accessible via passwordless (key-based) SSH from the machine that is running CycleServer. Alternatively, CycleServer may be installed directly on the scheduler. Ganglia's gmetad daemon must be configured to serve up XML via its RESTful interface and the CycleServer host must be able to request this XML. By default this is enabled and accessible on port 8652 ( Installation Before beginning, make sure you are logged into your machine as the root user. This is required for the installation process to set CycleServer to start on boot. Download the CycleServer tarball, then extract the contents into a temporary directory. The temporary directory will now contain a cycle_server folder. From this directory you may execute the installation script. If you wish to install CycleServer in the default /opt/cycle_server directory:./install.sh or if you wish to specify an installation directory:./install.sh --installdir /path/to/install/dir 1

4 This installation script will place CycleServer in the desired directory and create a user called "cycle_server" that will be used to run the service. It will also add an init.d script so that CycleServer is started on boot. When the installation script finishes, you should see the following message: CycleServer is installed. Please browse to to complete the installation. Open the provided URL inside of your web browser. It may take a minute for the URL to become available as CycleServer initializes itself, after which you will see the installation wizard appear. Creating an admin user The wizard will prompt you to create a user. This user will have full administrative privileges to CycleServer. Simply enter a user id (such as "admin"), a full name ("CycleServer Administrator") and a password. After initial setup is complete, you may configure Active Directory/LDAP integration if desired. Initial Grid Engine Cluster Configuration This section of the wizard will guide you through configuring CycleServer to monitor a Grid Engine cluster. The following values are required: Cluster Name: The name of the cluster. A short but descriptive name is recommended. This cannot be changed later. Cell Name: The cell name of the cluster. This should almost always be set to "default". Hostname: The fully qualified host name of the scheduler node. SSH User: The user that will be used to run remote commands on the scheduler. SSH Key: The absolute path of an RSA key used to connect to the scheduler. The scheduler machine must be configured for passwordless SSH. You may test this by running the following command as the cycle_server user: ssh -i /path/to/rsa_key your_ssh_user@your.scheduler.host Note that the cycle_server user must own the key file, and it must be readable and writable by only the owner (chmod 600). Grid Engine Root: The full path to Grid Engine on the scheduler (for example: /opt/ogs/ogs ). Monitoring: If checked, Grid Engine monitoring will be enabled. This should checked for this install. 2

5 Interval: How often CycleServer will poll Grid Engine for new data. This should generally be set to "1m". Initial Ganglia Cluster Configuration This section of the wizard will help you configure CycleServer to monitor a Ganglia cluster through its gmetad daemon. The following values are required: Name: The name of the Ganglia cluster. A short but descriptive name is recommended. If the Ganglia and Grid Engine clusters contain the same hosts then the cluster names should match. This cannot be changed later. Interval: How often CycleServer will poll Ganglia for new data. This should generally be set to "1m". Daemon: The fully qualified host name of the host running Ganglia's gmetad. If the gmetad is serving XML on a port other than 8652 (the default), then this value should be in hostname:port format. Installing a License Completing the installation wizard will navigate to the "installed applications" page, where the product license can be entered. Under "install a license" you may enter a redemption code or a license key and click the "Install License" button. If you need a license, select the "License Key" tab, copy the license request code, paste it into an and send it to support@cyclecomputing.com. Once a valid licenses is entered, click the CycleServer icon in the upper right-hand corner of the screen to go to the home page. Configuring CycleServer Chef Monitoring CycleServer runs an Apache Qpid message queue which is used to receive Chef data from a custom Chef handler. For instructions on installing and configuring the handler, visit and see the install guide. Note that the handler should be configured to point to the CycleServer machine. Monitoring Additional Grid Engine Clusters To monitor another Grid Engine cluster, select "Systems" then "Grid Engine" from the menu, then click "Configure qmasters" in the upper right-hand corner of the page. This will bring you to a list of your currently configured clusters. Click the "Create" button. This will pop up the cluster configuration dialog. Follow the steps described under the "Initial Grid Engine Cluster Configuration" section above to set up your new cluster. 3

6 Monitoring Additional Ganglia Clusters To monitor another Ganglia cluster, select "Systems" then "Ganglia" from the menu, then click "Configure masters" in the upper right-hand corner of the page. This will bring you to a list of your currently configured clusters. Click the "Create" button. This will pop up the cluster configuration dialog. Follow the steps described under the "Initial Ganglia Cluster Configuration" section above to set up your new cluster. Upgrading to a New Version To upgrade CycleServer, download the new tarball into a temporary directory and run the following commands as root (replacing /opt/cycle_server with your CycleServer installation directory if necessary): cd /opt/cycle_server./util/upgrade.sh /full/path/to/cycle_server.tar.gz This script will perform the upgrade and restart CycleServer automatically. To verify that the upgrade was successful, open the CycleServer web interface and look at the version number displayed in the lower left-hand corner of the screen. Appendix Job (OGS.Job) Name GridEngine Name Description Account JB_account Queue information Ar JB_ar Advance reservation number Arch arch CheckpointAttr JB_checkpoint_attr Checkpoint attributes CheckpointInterval JB_checkpoint_interval CheckpointObject JB_checkpoint_object ClusterName Defined name of the cluster ClusterQueue Count CpuTime cpu_usage CPU time accumulated 4

7 Cwd JB_cwd The current working directory of the job Deadline JB_deadline 1 if there a deadline for this job, 0 otherwise Department EndTime JB_department Time of the job completion, as unix time EnvList JB_env_list The environment variables for the job ExecFile JB_exec_file The executable script within sgeroot ExecutionTime JB_execution_time The number of seconds this job has been running ftickets ftickets Gid JB_gid The GID of the running job Group JB_group The group that owns the job HardQueueList JB_hard_queue_list HardWallclockGmt JB_hard_wallclock_gmt Hard wallclock limit Host HostName JB_host The hostname where the job completed Io io_usage IO accumulated with this job IoWait The I/O wait time in seconds JaStructure JB_ja_structure The job structure JAT_ntix JAT_share JaTasks JB_nppri JidRequestList JidSucessorList JAT_ntix JAT_share JB_ja_tasks JB_nppri JB_jid_request_list JB_jid_sucessor_list 5

8 JobName JB_job_name The name of the job (user-defined) JobNumber JB_job_number Job number Jobshare JB_jobshare 1 if jobsharing turned on for this job, 0 otherwise JobState jobstate One of 'queued', 'pending', 'running', 'suspended', 'completed', or 'deleted' load_avg load_avg MailList JB_mail_list addresses to be mailed for job events MailOptions JB_mail_options 1 if mail options are enabled, 0 otherwise MaxEndTime Mem mem_usage Memory consumed MergeStderr JB_merge_stderr True if stderr should be merged with stdout, false otherwise MinStartTime MinSubmissionTime Name JB_name Notify JB_notify True if job notification on, false otherwise Nrunning otickets JB_nrunning otickets OverrideTickets JB_override_tickets Number of override tickets Owner JB_owner The operating system username that owns the job Prio JAT_prio Priority JB_priority Job priority (higher values make jobs run earlier) 6

9 Project QueueInfo QueueInstance JB_project queue_info QueueName name The name of the queue this job is in QueueType QueueWaitTime qtype Reserve JB_reserve True if job reservation is enabled, false otherwise ReservedSlots slots_resv Restart JB_restart 1 if the job can be restarted, 0 otherwise RunTime ruwallclock Wallclock time spent on the job ScriptFile JB_script_file The actual name of the script submitted ScriptSize JB_script_size The size of the script submitted, in bytes Session JB_session ShellList JB_shell_list The shell of the running job Slots slots Number of slots for this job SoftWallclockGmt JB_soft_wallclock_gmt Soft wallclock limit StartTime JAT_start_time Time the job started running, as unix time State stickets state stickets SubmissionTime JB_submission_time Time of the job submission, as unix time Taskid tasks The task number within the array 7

10 tickets TotalSlots tickets slots_total Type JB_type The type of job Uid JB_uid The UID of the running job UsedSlots slots_used Verify JB_verify 1 if the job should be verified, 0 otherwise VerifySuitableQueues Version JB_verify_suitable_queues JB_version 8