Release Notes (also available in RSS format)

oapi-cli is now documented on this website. oapi-cli is the successor of OSC CLI, providing expanded features and improved user experience. For example: better handling of error responses, Bash autocompletion, and a variable system.

This update includes:

The OUTSCALE API documentation now also includes tabs for the HCL language, which is used by the OUTSCALE Terraform provider. These tabs contain links to the pages of the corresponding Terraform resources or data sources.

This way, if you are a Terraform user, you can better identify the correlations between OUTSCALE API and OUTSCALE Terraform provider.

You can now subscribe to Microsoft Windows license offers. For more information, see Estimating the Cost of a Product and Subscribing To an OMI Product > Microsoft Windows License.

You can now get information about all the entities linked to a specific managed policy with the OUTSCALE API method ReadEntitiesLinkedToPolicy. For more information, see Getting Information About Entities Linked to a Managed Policy.

For security reasons, or because of the capacity of your software solutions, you might want to delegate the control of network traffic to an appliance.

To do this, you can send all external network traffic to a VM running an appliance.

You can follow this tutorial to set up an appliance: Setting Up an Appliance in a Net.

The PeerOwnerId parameter of the CreateVpcPeeringConnection FCU method is now added to its corresponding OUTSCALE API CreateNetPeering method under the name AccepterOwnerId.

This integration is done in two steps:

In the OUTSCALE API, the value of the IsSourceDestChecked parameter in the primary Network Interface Card (NIC), with 0 as device index, is now consistent with the IsSourceDestChecked parameter of the VM.

This improvement is also applied in the Flexible Compute Unit (FCU) API with the sourceDestCheck parameter of the Flexible Network Interface (FNI) that is consistent with the sourceDestCheck parameter of the instance.

The definition of recommended virtual machines (VMs) when creating an OUTSCALE machine image (OMI) product has been improved. For more information, see Creating and Publishing an OMI Product > Offer.

When creating an outsourced product, you must now read and accept the business provider contract in order to publish the product. For more information, see Creating and Publishing an Outsourced Product > Contractual terms.

When creating an OUTSCALE machine image (OMI) product and specifying the Versions form, you must now select the operating system from a list and provide details on it. For more information, see Creating and Publishing an OMI Product > Versions.

You can now estimate the cost of using an OMI product on several virtual machines (VMs). For more information, see Estimating the Cost of a Product.

When creating an OMI product whose pricing mode is bring your own license (BYOL) or free/open source, you must now specify a link to the product’s license agreement in the Legal section. For more information, see Creating and Publishing an OMI Product > Legal.

When subscribing to an OMI product whose pricing mode is bring your own license (BYOL) or free/open source, you can now view the license agreement of the product in the My subscriptions page. For more information, see Subscribing To an OMI Product.

CPU performance has been improved across all our Regions.

The placement of vCores of new virtual machines has been optimized, through better support for NUMA (non-uniform memory access) zones in Intel processors.

The network performance has been improved across all our Regions.

For the newly created Nets, the network can now handle a larger number of packets per second, and bandwidth capacity has been increased.