You can create a resource to contain solely static hosts, solely cloud burst hosts, or a combination of each. For more information about resources, the purpose of resources, and a description of static versus cloud burst hosts, see Working with Resources .
Field Descriptions
Field | Description |
---|---|
Name |
Unique name for your resource definition. The name can contain numbers and letters. This is also the name that you specify in the |
Description |
(Optional) Description of the specified resource. |
Applicable for static hosts: |
|
Hosts |
(If you are using static hosts) One or more static host names. See Host Name Globbing below. You must configure at least one host or one cloud burst provider (described below). |
Add Host Mask Pattern |
Host name masks follow the same standard globbing rules as Make. Globbing lets you use a pattern to match one or more files. Examples are below. |
Applicable for cloud burst hosts: |
|
Cloud Burst |
(If you are using cloud bursting) Type of cloud provider for the credential. You can select ec2 or kubernetes. You must configure at least one cloud burst provider or one static host (described above). |
Credentials |
Choose an existing credential set or choose to add a new set.
For AWS EC2 clusters, as supplied with your EC2 account:
For Kubernetes clusters, as supplied with your Kubernetes account:
|
If the connection is successful, provide additional details as required for the cloud burst model as follows.
Kubernetes
Field | Description |
---|---|
Image Name |
This is the image that is used by the resource that you specified via the |
Namespace |
The name of the Kubernetes namespace within which the deployed services should be discovered. Defaults to the default namespace. |
Labels |
(Optional) Define and use labels that identify semantic attributes of your application or deployment. |
Image Pull Policy |
(Optional) The image pull policy and the tag of the image affect when the kubelet attempts to pull the specified image. Always —the image is pulled every time the pod is started. If Not Present —the image is pulled only if it is not already present locally. Never —the image is assumed to exist locally. No attempt is made to pull the image. Default is By default, the kubelet tries to pull each image from the specified registry. However, if the Image Pull Policy of the container is set to If you want to rely on pre-pulled images as a substitute for registry authentication, you must ensure all nodes in the cluster have the same pre-pulled images. This can be used to pre-load certain images for speed or as an alternative to authenticating to a private registry. |
Agents Per Instance |
Number of agents installed on the image used to create the instance. Default is |
Instance Idle Timeout (minutes) |
Period of time before idle agents are terminated. After their corresponding cluster resource is done being used, agents become idle and available for a subsequent build. If a new build starts using that resource during idle timeout, idle instances are used and new instances are provisioned if needed. The default is 15 minutes. |
EC2
Field or menu | Description | ||||
---|---|---|---|---|---|
Instance Type |
Information provided from AWS EC2 specification that defines the memory, CPU, storage capacity, and usage cost for an instance. |
||||
Security Group |
Named set of allowed inbound network connections for an instance. Security groups in Amazon Virtual Private Cloud (VPC) also include support for outbound connections. |
||||
Key Pair |
Set of security credentials that you use to prove your identity electronically. A key pair consists of a private key and a public key. You use the private key to create a digital signature, and then AWS uses the corresponding public key to validate the signature. |
||||
Availability Zone |
Distinct location within a region that is insulated from failures in other Availability Zones. |
||||
Subnet ID |
Segment of the IP address range of a VPC that Amazon EC2 instances can be attached to. You can create subnets to group instances according to security and operational needs. |
||||
AMI |
The Amazon EC2 image name that is used to launch cloud burst agent instances. |
||||
Extra Tags |
Extra (custom) tags to add to the Amazon EC2 agent instance at launch. These tags are visible in the instance settings on AWS. These are in addition to To add extra tags, you set the variable to a comma-separated list of Name:MyAgent, ProvisionedBy:EA
|
||||
Agents Per Instance |
Number of agents installed on the image used to create the instance. Default is |
||||
Instance Idle Timeout (minutes) |
(Optional) Period of time before idle agents are terminated. After their corresponding cluster resource is done being used, agents become idle and available for a subsequent build. If a new build starts using that resource during idle timeout, idle instances are used and new instances are provisioned if needed. The default is 15 minutes. |
For more information about Amazon EC2 and the terms used above, see the Amazon Elastic Compute Cloud Documentation .
include:partial$stalled-cloud-agents-note.adoc[] |
Glob-Style Pattern Example 1
With the hosts specification below, the build runs with agents on hosts earth
, wind
, or `fire, ` only. If these hosts are not available, the build waits until they are. If other builds are running on these hosts, Accelerator may move those builds to other hosts to free up agents for this build.
Resource definition:
Name — Xcard
Hosts — earth;wind;fire
eMake execution:
--emake-resource=Xcard
If you use the --emake-resource option, it overrides the resource request defined in the --emake-class option if both options exist.
|
Glob-Style Pattern Example 2
With the hosts specification below, the build runs on host earth, ` only, or hosts whose names start with `asteroid
.
Resource Definition:
Name — Xsoft
Hosts — earth;asteroid*
Build Class definition:
Name — Xbuilds
Resource Request — Xsoft
eMake execution:
--emake-class=Xbuilds