10. [EOS/EOSM of processor gens] I ordered 3 Reserved Instances of type tinav2.c2r4p2 from January 1, 2022 to December 31, 2023 (2-year commitment). Am I impacted and what will happen?

Yes, I am impacted since the date of EOSM of the v2 generation is August 31, 2023 and the ending date of the commitment is later (December 31, 2023).

In order to continue to ensure the service commitment on the virtual machines that use these reservations, we offer the possibility to upgrade these reservations, at no extra cost, to the v5 generation in the period between EOS and EOSM (2 months).

A stop/start with modification of the virtual machine will be required on your part, to be done at the time of your choice. To do so, see the documentation, Modifying an Instance Attribute (VmType attribute in the OUTSCALE API, or instance-type in the AWS compatibility layerof the FCU API).

This operation is at no extra cost and, in the period between EOS and EOSM, the equivalent virtual machines in the v5 generation will be credited for all active orders in the following way:

1. Before the date of EOS, your reservations are: 3x tinav2.c2r4p2.
2. Between the date of EOS and that of EOSM, your reservations are: 3x tinav2.c2r4p2 + 3x tinav5.c2r4p2.
3. After the date of EOSM, your reservations are: 3x tinav5.c2r4p2, and any remaining consumption on the v2 generations will be billed on the basis of the applicable public pricing.