This page lists OUTSCALE tags that you can use to manage the behavior of your Cloud resources according to your hardware or network needs.

You can apply these tags in the metadata of your instances, or using the classic method. For more information, see Configuring an Instance with User Data and OUTSCALE Tags or Adding or Removing Tags.

Tags are available for the following needs:

Instances Placement


Tag NameDescriptionTag ValueApplication

osc.fcu.repulse_server

Places instances with the same tag value on different serversFree
  • At instance launch
  • After a stop/start of the instance

osc.fcu.attract_server

Places instances with the same tag value on the same server

osc.fcu.repulse_cluster

Places instances with the same tag value on different Cisco UCS clusters

osc.fcu.attract_cluster

Places instances with the same tag value on the same Cisco UCS cluster

These tags can be used in strict mode, which means that if the requested placement options are not possible, an InsufficientCapacity error is returned. If you do not use strict mode, the requested placement options are bypassed if they are not possible.

To define strict mode, add _strict to the tag name (for example, osc.fcu.repulse_server_strict).



 

Association of IP Addresses to Instances 


Tag NameDescriptionTag ValueApplication

osc.fcu.eip.auto-attach

Automatically associates an External IP address (EIP) with an instance, and keeps them associated through the stop and start process

The EIP you want to associate.

For more information, see About EIPs > EIP Association.

  • At instance launch
  • After a stop/start of the instance
private_onlyBlocks attribution of a public IP to an instance in the public Cloudtrue or false




Firewall Bypass

Firewall bypass consists in disabling security groups in order to reduce overall latency between instances. For more information, see About VPCs > Subnet Routing and Security.

Use CaseTag Name to Put on the VPCTag Name to Put on the InstancesEffect
Instances in a VPCosc.fcu.disable_lan_security_groupsn/a

Security groups are disabled between instances of the same subnets.

This is the default behavior if no tag is applied.

osc.fcu.enable_lan_security_groupsn/a

Security groups are enabled between instances of the same subnets.

Instances in the Public Cloud
osc.fcu.enable_lan_security_groups

Security groups are enabled between the instances.

This is the default behavior if no tag is applied.

osc.fcu.disable_lan_security_groupsSecurity groups are disabled between the instances if they have the same tag and tag value.
  • Tags on a VPC must be applied after creating the VPC, but before creating any subnet in it. Once you have created a subnet in the VPC, the tags cannot modify the behavior any longer.
  • Tags on instances must be applied at instance launch, or must be followed by a stop/start on the instances.
  • The tag values can be any value, except for osc.fcu.disable_lan_security_groups in the public Cloud, where it must be at least one character long.




Use of Both OUTSCALE Tags and Free Section


Tag NameDescriptionTag ValueApplication

filter_private_section

Filters the OUTSCALE tags of the instance so that you can use both a section of OUTSCALE tags and a free section of user data in the same instance.

If true, all your OUTSCALE tags take effect, but they are not visible when reading the user data of the instance. 

If false or not defined, you cannot use both a section of OUTSCALE tags and a free section of user data.

true or false

  • At instance launch
  • After a stop/start of the instance

This tag is available for the OUTSCALE API only. It is not compatible with the FCU API.