Post-upgrade to 10.2409.2

After updating the service image to 10.2409.2, complete the migration steps to fully utilize certain enhancements.

Procedure

Alter the Inventory ledger and aggregate tables with gc_grace period
1. Log in to Cassandra instance.
2. Run the following command to select the keyspace.
```
USE <iv_keyspace>;
```
  This is the name of the keyspace that is defined in SIPEnvironment. For more information, see keyspace in cassandra parameter.
3. Run the following queries to alter ledger and aggregate tables with gc_grace period.
```
alter table inv_reserv_ledger WITH gc_grace_seconds = 3600;
alter table inv_reserv_aggregate WITH gc_grace_seconds = 3600;
```
Migrations steps for reservation feature enhancement
The 10.2409.0 release introduces performance enhancements to the reservation feature. To fully utilize this feature, migrate the existing reservation records from the inv_reserv_summary_v2 table to the inv_reserv_aggregate and inv_reserv_ledger tables. If no prior records exist, migration is not needed.
1. Note down the time when the deployment is complete.
2. If you wait for the expiration of existing reservation records that are created before the upgrade, then do not call the migration API. For example, if the expiration timestamp of the existing records is within the next 24 hours, then waiting for 24 hours ensures that all these records expire automatically and no data needs to be migrated into the new table. After waiting for the existing records to expire, skip step 3.
3. If the existing records that are created before the upgrade have a longer expiration duration, waiting for them to expire may not be feasible. In such cases, call the migration API to migrate records to the new table. You can still wait for 24 hours to let most of the records to expire so that fewer records need migration.
  1. Call the migration API after 24 hours of the deployment to migrate records that are created before the upgrade, based on the database write timestamp.
```
POST https://{{hostname}}/inventory/v1/migration/reserve_ledger
{
"tenantId": "default",
"pageSize": 100
}
```
  2. To check the status of the migration, call the following API. When the job status is complete, go to step 4.
```
GET https://{{hostname}}/inventory/v1/migration/reserve_ledger
```
    For more information, see the API documentation.
4. Update the base rule to ONLY_WRITE_NEW to disable writing to the inv_reserv_summary_v2 table by calling the PATCH operations API. To validate the updated value you can then call the GET operations API.
```
PATCH https://{{hostname}}/inventory/operations/v1/configuration/settings/default
 {
 "migration" :{
        "reserveAggregateMigrationMode": "ONLY_WRITE_NEW"
    }
 }
```
Enable events with publisher
Effective 10.0.2409.2 February 2025 release, in a container environment, a publisher is needed to publish the events that you are interested in. To enable events with a publisher, see Event publishing in container environments.
Initiate audit index rollover
Call the following API request to roll over the audit index and ensure that the newly created index reflects the component template changes that are applied during the upgrade process.
```
POST https://{{hostname}}/audits/_rollover
```