Difference: Condor_annex (11 vs. 12)

Revision 122016/11/21 - Main.MartinKandes

Line: 1 to 1
 
META TOPICPARENT name="WebHome"
Line: 18 to 18
 

Definitions

Changed:
<
<
  • SUBMIT is the hostname of the HTCondor submit node, where users submit their jobs to your local pool.
  • CENTRAL_MANAGER is the hostname of the HTCondor central manager of your local pool, which collects and matches job and machine class ads.
>
>
  • SUBMIT is the hostname of an HTCondor submit node, where users submit their jobs to your local pool.
  • CENTRAL_MANAGER is the hostname of your HTCondor central manager, where job and machine class ads are matched.
 
  • EXECUTE is the hostname of an HTCondor execute node in your local pool.
  • ANNEX is the hostname of an EC2 instance configured as a condor_annex execute node.
Line: 48 to 48
 To create access keys, you must have permissions to perform the required IAM actions.

  1. Open the IAM console.
Changed:
<
<
  1. In the navigation pane, choose Users.
  2. If you do not already have an IAM username, then select Create New Users. Each new user is issued credentials.
>
>
  1. In the navigation pane, choose Users.
  2. If you do not already have an IAM username, then select Add User. Each new user is issued credentials.
 
  1. If you already have an IAM username, then choose your IAM username (not the check box).
Changed:
<
<
  1. Next, select the Security Credentials tab and then choose Create Access Key.
>
>
  1. Next, select the Security Credentials tab and then choose Create Access Key.
 
  1. To see your access key, choose Show User Security Credentials. Your credentials will look something like this:
    • Access Key ID: AKIAIOSFODNN7EXAMPLE?
    • Secret Access Key: wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY
  2. Choose Download Credentials, and store the keys in a secure location. Your secret key will no longer be available through the AWS Management Console; you will have the only copy. Keep it confidential in order to protect your account, and never email it. Do not share it outside your organization, even if an inquiry appears to come from AWS or Amazon.com. No one who legitimately represents Amazon will ever ask you for your secret key.
Changed:
<
<		If you need more information about AWS Security Credentials, please consult the AWS documentation at:
>
>		Save your Access Key ID and Secret Access Key. You will need to provide them later when configuring the AWS CLI. If you need more information about AWS Security Credentials, please consult the AWS documentation at:
 
Added:
>
>

Step 4: Select a Region for the Annex

 
Changed:
<
<

Step 4: Select an Amazon Region for the Annex

Amazon Elastic Compute Cloud (EC2) instances are hosted in multiple locations world-wide. These locations are composed of Regions and Availability Zones. Each Region is a separate geographic area. However, each Region also has multiple, isolated locations known as Availability Zones (AZs), which are simply high-availability data centers. However, not all AWS Regions are created equal. Each Region may offer only a subset of AWS services. You can find out what services are offered in each Region from the table provided here:

>
>		Amazon Elastic Compute Cloud (EC2) instances are hosted in multiple locations world-wide. These locations are composed of Regions and Availability Zones. Each Region is a separate geographic area. However, each Region also has multiple, isolated locations known as Availability Zones (AZs). However, not all AWS Regions are created equal. Each Region may offer only a subset of AWS services. You can find out what services are offered in each Region from the table provided here:
 
Changed:
<
<		When selecting a Region for your HTCondor annex, you must select a region that offers all of the AWS services required by condor_annex to function properly. These services are:
>
>		When selecting a Region for your annex, you must select a region that offers all of the AWS services required by condor_annex to function properly. These services are:
 
Line: 89 to 88
  Select your desired Region accordingly from the drop-down menu in the upper-right-hand side of the AWS Management Console.
Changed:
<
<

Step 5: Generate an Amazon EC2 Key Pair

>
>

Step 5: Generate an EC2 Key Pair

 
Changed:
<
<		After selecting a Region for your HTCondor annex, you will need to generate an SSH key pair that will allow you to login to your EC2 instances. You can create a key pair using the Amazon EC2 console or the command line. After you create a key pair, you will specify it when launching your instances from condor_annex.
>
>		After selecting a Region for your annex, you will need to generate an SSH key pair that will allow you to login to your EC2 instances in that Region. You can create a key pair using the EC2 console or the command line. You will specify this key pair when launching your instances with condor_annex.
  To create your key pair using the Amazon EC2 console
Changed:
<
<
  1. Open the Amazon EC2 console at https://console.aws.amazon.com/ec2/.
  2. In the navigation pane, under NETWORK & SECURITY, choose Key Pairs.
  3. Choose Create Key Pair.
  4. Enter a name for the new key pair in the Key pair name field of the Create Key Pair dialog box, and then choose Create.
>
>
  1. Open the EC2 console at https://console.aws.amazon.com/ec2/.
  2. In the navigation pane, under NETWORK & SECURITY, choose Key Pairs.
  3. Choose Create Key Pair.
  4. Enter a name for the new key pair in the Key pair name field of the Create Key Pair dialog box, and then choose Create.
 
  1. The private key file is automatically downloaded by your browser. The base file name is the name you specified as the name of your key pair, and the file name extension is .pem. Save the private key file in a safe place. This is the only chance for you to save the private key file. You'll need to provide the name of your key pair when you launch an instance and the corresponding private key each time you connect to the instance.
Changed:
<
<
  1. Use the following command to set the permissions of your private key file so that only you can read it. 
     [user@client ~]$ chmod 400 my-key-pair.pem
>
>
  1. Use the following command to set the permissions of your private key file so that only you can read it. 
     [user@SUBMIT ~]$ chmod 400 my-key-pair.pem
  If you would like to create your SSH key pair using the AWS CLI or import your own key pair, please consult the AWS documentation at:
Line: 108 to 107
 

Step 6: Configure Default VPC Security Group

Changed:
<
<		condor_annex will automatically create and configure an AWS Security Group (i.e., a virtual firewall) around each annex it builds. However, depending on your HTCondor pool configuration, it may also been useful to place some on-demand resources in AWS. For example, you may want to a separate HTCondor central manager instance in AWS in order to flock user jobs over to the annex instead of connecting the annex instances themselves all the way back to your local central manager.
>
>		condor_annex will automatically create and configure an AWS Security Group (i.e., a virtual firewall) around all of the instances within an annex. However, depending on your HTCondor pool configuration, it may also been useful to place some on-demand resources in AWS. For example, you may want to a separate HTCondor central manager instance located in AWS in order to flock user jobs over to the annex instead of connecting the annex instances back to your local central manager.
  These on-demand resources may be placed in your AWS Region's default Virtual Private Cloud (VPC) Security Group. To configure the default VPC Security Group:
Changed:
<
<
  1. Open the Amazon VPC console at https://console.aws.amazon.com/vpc/.
>
>
  1. Open the VPC console at https://console.aws.amazon.com/vpc/.
 
  1. In the navigation pane, under Security, choose Security Groups.
  2. Select the Security Group in the list that has Group Name default and Description default VPC security group.
  3. Next, select the Inbound Rules tab and then click on the Edit button.
View topic | History: r16 < r15 < r14 < r13 | More topic actions...
 
This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback