Outscale

An Outscale resource handler connects to a single Outscale region and manages its servers, images, networks, and VPCs

Adding the handler creates a Cloud Management Platform (CMP) environment and imports the Outscale parameters. A handler covers one region, and each region has its own access key pair. Add a separate handler for each region you use.

Before you begin

Collect the following from Outscale:

  • The Region to connect to. Outscale region names follow the AWS pattern, such as us-east-2. See Outscale’s regions and endpoints reference for the full list.
  • The Access Key and Access Key Secret for that region.

Add an Outscale resource handler

  1. Go to Admin > Resource Handlers, select Add, then select Outscale under Public Cloud.
  2. Enter the Region, Access Key, and Access Key Secret, then select Continue.
  3. Enter a name and an optional description, then select Done.

CMP opens the new handler. Before ordering, work through its tabs to complete configuration.

Import images

Use the Images tab to import images for the handler’s region. An environment needs at least one image to build a server.

Import networks

Use the Networks tab and select Import Networks to import networks for the handler’s region. Select a network’s name to see its details.

Outscale networks are tied to their region, so which environments a network serves is not something you edit: the network’s Environments tab offers no Edit control, unlike other technologies.

Import VPCs

Use the Vpcs tab to import your Outscale VPCs. Select Import VPCs, choose VPCs, and submit the dialog. CMP creates an environment for each selected VPC, which is how you add environments beyond the one the handler starts with.

CMP records each VPC’s name and ID against the environment it creates. The tab lists each VPC’s name, ID, and environments.

Sync servers

Use the Servers tab to sync VMs from Outscale. Select a server’s name to see its details.

Set compute limits

Use the Compute Limits tab to see and change the limits on what this handler can consume.

Tag Outscale resources

CMP tags the resources it creates during provisioning. Map a tag to a CMP server attribute. The tag’s value follows that attribute.

  1. On the handler, open the Tags tab and select Add.
  2. In Add a Tag, choose the Parameter that supplies the value, give the tag a name, and select Add.

A tag marked as bidirectional updates in both places: change it in Outscale or in CMP, and the other follows.

Configure the environment

Configure the CMP environment before ordering a server. Open the handler’s Overview tab, select the environment name, and then set the following on the environment:

Tab What to set
Groups Select Edit, choose the groups that can order into this environment, then select Save.
OS Builds Select Edit, choose the OS builds, then select Save.
Parameters Set values for the Outscale parameters below, or add any other CMP parameter. Use the edit icon in the Actions column to change a parameter’s value or options.

Outscale parameters

Adding the handler imports these parameters. Instance Type, Availability Zone, Outscale Keypair Name, and Outscale Security Group come with options discovered from your Outscale account. Outscale External IP and Outscale User Data have no discovered options: add them to the environment and set a value.

Parameter Description
Instance Type Required. The instance type to provision, which sets the server’s size.
Outscale Keypair Name The name of a key pair in your Outscale account. For CMP to connect with it, add the private key on the handler’s SSH Keys tab. See SSH keys. It is placed on the instance at launch for key-based access, in place of a username and password.
Outscale Security Group A security group in the environment’s VPC. More than one can be selected.
Availability Zone Required. The availability zone to deploy into.
Outscale External IP Assigns an external IP to an instance or NIC. If the list is empty, an Outscale administrator must allocate additional addresses.
Outscale User Data User data passed to the instance, which can run scripts after it starts. See Customize VMs during provisioning.