Skip to content

Commit e1fd15d

Browse files
tcpdumpfbacketcpdumpfbacke
authored
Merge pull request #7739 from ovh/ls_update_transition
Ls update transition to include new storage class STANDARD_IA
2 parents 98f724b + 70574c6 commit e1fd15d

File tree

15 files changed

+150
-105
lines changed

15 files changed

+150
-105
lines changed

‎pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.de-de.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -362,11 +362,11 @@ In a versioned bucket, the following configuration does the following actions:
362362
363363
The following are the currently supported transitions:
364364

365-
| from/to | High Performance | Standard | Cold Archive |
366-
| ---------------- | ---------------- | --------- | ------------ |
367-
| High Performance | - | yes | no |
368-
| Standard | forbidden | - | no |
369-
| Cold Archive | forbidden | forbidden | - |
365+
| from/to | High Performance | Standard | Standard Infrequent Access |Cold Archive |
366+
| ---------------- | ---------------- | --------- | -------------------------- |------------ |
367+
| High Performance | - | yes | yes | no |
368+
| Standard | forbidden | - | yes | no |
369+
| Cold Archive | forbidden | forbidden | forbidden | - |
370370

371371
### Minimum object size
372372

@@ -375,6 +375,9 @@ OVHcloud Object Storage will prevent any transition to any storage tier for obje
375375
### Minimum transition delay
376376

377377
The minimum duration for transition rules is **30 days** i.e your lifecycle configuration will not be valid and you will get an error if the number of days for your transition rule is less than 30 days. In practice, it means that the lifecycle feature will only consider objects older than **30 days**.
378+
For example, let's say you upload an object in the High Performance storage tier and you want to transition said object to Standard storage tier after a certain amount of time and then from Standard to Standard Infrequent Access storage tier after another amount of time. That means:
379+
- your object can only be transitioned from High Performance to Standard after 30 days
380+
- your object can only be transitioned from Standard to Standard Infrequent Access after 60 days (30 days after the previous transition)
378381

379382
### Expiration vs transitions
380383

@@ -471,7 +474,7 @@ In this scenario, suppose you upload an object with multiple versions:
471474
If the current date is 2024-10-23:
472475

473476
- v5 will be transitioned 30 days after 2024-10-23
474-
- v1 will be transitioned since it has been a noncurrent version for 5 days already
477+
- v1 will be transitioned 30 days after its creation date (2024-10-18)
475478

476479
```json
477480
{
@@ -488,7 +491,7 @@ If the current date is 2024-10-23:
488491
],
489492
"NoncurrentVersionTransitions": [
490493
{
491-
"NoncurrentDays": 5,
494+
"NoncurrentDays": 30,
492495
"StorageClass": "STANDARD"
493496
}
494497
]

‎pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-asia.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -362,11 +362,11 @@ In a versioned bucket, the following configuration does the following actions:
362362
363363
The following are the currently supported transitions:
364364

365-
| from/to | High Performance | Standard | Cold Archive |
366-
| ---------------- | ---------------- | --------- | ------------ |
367-
| High Performance | - | yes | no |
368-
| Standard | forbidden | - | no |
369-
| Cold Archive | forbidden | forbidden | - |
365+
| from/to | High Performance | Standard | Standard Infrequent Access |Cold Archive |
366+
| ---------------- | ---------------- | --------- | -------------------------- |------------ |
367+
| High Performance | - | yes | yes | no |
368+
| Standard | forbidden | - | yes | no |
369+
| Cold Archive | forbidden | forbidden | forbidden | - |
370370

371371
### Minimum object size
372372

@@ -375,6 +375,9 @@ OVHcloud Object Storage will prevent any transition to any storage tier for obje
375375
### Minimum transition delay
376376

377377
The minimum duration for transition rules is **30 days** i.e your lifecycle configuration will not be valid and you will get an error if the number of days for your transition rule is less than 30 days. In practice, it means that the lifecycle feature will only consider objects older than **30 days**.
378+
For example, let's say you upload an object in the High Performance storage tier and you want to transition said object to Standard storage tier after a certain amount of time and then from Standard to Standard Infrequent Access storage tier after another amount of time. That means:
379+
- your object can only be transitioned from High Performance to Standard after 30 days
380+
- your object can only be transitioned from Standard to Standard Infrequent Access after 60 days (30 days after the previous transition)
378381

379382
### Expiration vs transitions
380383

@@ -471,7 +474,7 @@ In this scenario, suppose you upload an object with multiple versions:
471474
If the current date is 2024-10-23:
472475

473476
- v5 will be transitioned 30 days after 2024-10-23
474-
- v1 will be transitioned since it has been a noncurrent version for 5 days already
477+
- v1 will be transitioned 30 days after its creation date (2024-10-18)
475478

476479
```json
477480
{
@@ -488,7 +491,7 @@ If the current date is 2024-10-23:
488491
],
489492
"NoncurrentVersionTransitions": [
490493
{
491-
"NoncurrentDays": 5,
494+
"NoncurrentDays": 30,
492495
"StorageClass": "STANDARD"
493496
}
494497
]

‎pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-au.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -362,11 +362,11 @@ In a versioned bucket, the following configuration does the following actions:
362362
363363
The following are the currently supported transitions:
364364

365-
| from/to | High Performance | Standard | Cold Archive |
366-
| ---------------- | ---------------- | --------- | ------------ |
367-
| High Performance | - | yes | no |
368-
| Standard | forbidden | - | no |
369-
| Cold Archive | forbidden | forbidden | - |
365+
| from/to | High Performance | Standard | Standard Infrequent Access |Cold Archive |
366+
| ---------------- | ---------------- | --------- | -------------------------- |------------ |
367+
| High Performance | - | yes | yes | no |
368+
| Standard | forbidden | - | yes | no |
369+
| Cold Archive | forbidden | forbidden | forbidden | - |
370370

371371
### Minimum object size
372372

@@ -375,6 +375,9 @@ OVHcloud Object Storage will prevent any transition to any storage tier for obje
375375
### Minimum transition delay
376376

377377
The minimum duration for transition rules is **30 days** i.e your lifecycle configuration will not be valid and you will get an error if the number of days for your transition rule is less than 30 days. In practice, it means that the lifecycle feature will only consider objects older than **30 days**.
378+
For example, let's say you upload an object in the High Performance storage tier and you want to transition said object to Standard storage tier after a certain amount of time and then from Standard to Standard Infrequent Access storage tier after another amount of time. That means:
379+
- your object can only be transitioned from High Performance to Standard after 30 days
380+
- your object can only be transitioned from Standard to Standard Infrequent Access after 60 days (30 days after the previous transition)
378381

379382
### Expiration vs transitions
380383

@@ -471,7 +474,7 @@ In this scenario, suppose you upload an object with multiple versions:
471474
If the current date is 2024-10-23:
472475

473476
- v5 will be transitioned 30 days after 2024-10-23
474-
- v1 will be transitioned since it has been a noncurrent version for 5 days already
477+
- v1 will be transitioned 30 days after its creation date (2024-10-18)
475478

476479
```json
477480
{
@@ -488,7 +491,7 @@ If the current date is 2024-10-23:
488491
],
489492
"NoncurrentVersionTransitions": [
490493
{
491-
"NoncurrentDays": 5,
494+
"NoncurrentDays": 30,
492495
"StorageClass": "STANDARD"
493496
}
494497
]

‎pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-ca.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -362,11 +362,11 @@ In a versioned bucket, the following configuration does the following actions:
362362
363363
The following are the currently supported transitions:
364364

365-
| from/to | High Performance | Standard | Cold Archive |
366-
| ---------------- | ---------------- | --------- | ------------ |
367-
| High Performance | - | yes | no |
368-
| Standard | forbidden | - | no |
369-
| Cold Archive | forbidden | forbidden | - |
365+
| from/to | High Performance | Standard | Standard Infrequent Access |Cold Archive |
366+
| ---------------- | ---------------- | --------- | -------------------------- |------------ |
367+
| High Performance | - | yes | yes | no |
368+
| Standard | forbidden | - | yes | no |
369+
| Cold Archive | forbidden | forbidden | forbidden | - |
370370

371371
### Minimum object size
372372

@@ -375,6 +375,9 @@ OVHcloud Object Storage will prevent any transition to any storage tier for obje
375375
### Minimum transition delay
376376

377377
The minimum duration for transition rules is **30 days** i.e your lifecycle configuration will not be valid and you will get an error if the number of days for your transition rule is less than 30 days. In practice, it means that the lifecycle feature will only consider objects older than **30 days**.
378+
For example, let's say you upload an object in the High Performance storage tier and you want to transition said object to Standard storage tier after a certain amount of time and then from Standard to Standard Infrequent Access storage tier after another amount of time. That means:
379+
- your object can only be transitioned from High Performance to Standard after 30 days
380+
- your object can only be transitioned from Standard to Standard Infrequent Access after 60 days (30 days after the previous transition)
378381

379382
### Expiration vs transitions
380383

@@ -471,7 +474,7 @@ In this scenario, suppose you upload an object with multiple versions:
471474
If the current date is 2024-10-23:
472475

473476
- v5 will be transitioned 30 days after 2024-10-23
474-
- v1 will be transitioned since it has been a noncurrent version for 5 days already
477+
- v1 will be transitioned 30 days after its creation date (2024-10-18)
475478

476479
```json
477480
{
@@ -488,7 +491,7 @@ If the current date is 2024-10-23:
488491
],
489492
"NoncurrentVersionTransitions": [
490493
{
491-
"NoncurrentDays": 5,
494+
"NoncurrentDays": 30,
492495
"StorageClass": "STANDARD"
493496
}
494497
]

‎pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-gb.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -362,11 +362,11 @@ In a versioned bucket, the following configuration does the following actions:
362362
363363
The following are the currently supported transitions:
364364

365-
| from/to | High Performance | Standard | Cold Archive |
366-
| ---------------- | ---------------- | --------- | ------------ |
367-
| High Performance | - | yes | no |
368-
| Standard | forbidden | - | no |
369-
| Cold Archive | forbidden | forbidden | - |
365+
| from/to | High Performance | Standard | Standard Infrequent Access |Cold Archive |
366+
| ---------------- | ---------------- | --------- | -------------------------- |------------ |
367+
| High Performance | - | yes | yes | no |
368+
| Standard | forbidden | - | yes | no |
369+
| Cold Archive | forbidden | forbidden | forbidden | - |
370370

371371
### Minimum object size
372372

@@ -375,6 +375,9 @@ OVHcloud Object Storage will prevent any transition to any storage tier for obje
375375
### Minimum transition delay
376376

377377
The minimum duration for transition rules is **30 days** i.e your lifecycle configuration will not be valid and you will get an error if the number of days for your transition rule is less than 30 days. In practice, it means that the lifecycle feature will only consider objects older than **30 days**.
378+
For example, let's say you upload an object in the High Performance storage tier and you want to transition said object to Standard storage tier after a certain amount of time and then from Standard to Standard Infrequent Access storage tier after another amount of time. That means:
379+
- your object can only be transitioned from High Performance to Standard after 30 days
380+
- your object can only be transitioned from Standard to Standard Infrequent Access after 60 days (30 days after the previous transition)
378381

379382
### Expiration vs transitions
380383

@@ -471,7 +474,7 @@ In this scenario, suppose you upload an object with multiple versions:
471474
If the current date is 2024-10-23:
472475

473476
- v5 will be transitioned 30 days after 2024-10-23
474-
- v1 will be transitioned since it has been a noncurrent version for 5 days already
477+
- v1 will be transitioned 30 days after its creation date (2024-10-18)
475478

476479
```json
477480
{
@@ -488,7 +491,7 @@ If the current date is 2024-10-23:
488491
],
489492
"NoncurrentVersionTransitions": [
490493
{
491-
"NoncurrentDays": 5,
494+
"NoncurrentDays": 30,
492495
"StorageClass": "STANDARD"
493496
}
494497
]

‎pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-ie.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -362,11 +362,11 @@ In a versioned bucket, the following configuration does the following actions:
362362
363363
The following are the currently supported transitions:
364364

365-
| from/to | High Performance | Standard | Cold Archive |
366-
| ---------------- | ---------------- | --------- | ------------ |
367-
| High Performance | - | yes | no |
368-
| Standard | forbidden | - | no |
369-
| Cold Archive | forbidden | forbidden | - |
365+
| from/to | High Performance | Standard | Standard Infrequent Access |Cold Archive |
366+
| ---------------- | ---------------- | --------- | -------------------------- |------------ |
367+
| High Performance | - | yes | yes | no |
368+
| Standard | forbidden | - | yes | no |
369+
| Cold Archive | forbidden | forbidden | forbidden | - |
370370

371371
### Minimum object size
372372

@@ -375,6 +375,9 @@ OVHcloud Object Storage will prevent any transition to any storage tier for obje
375375
### Minimum transition delay
376376

377377
The minimum duration for transition rules is **30 days** i.e your lifecycle configuration will not be valid and you will get an error if the number of days for your transition rule is less than 30 days. In practice, it means that the lifecycle feature will only consider objects older than **30 days**.
378+
For example, let's say you upload an object in the High Performance storage tier and you want to transition said object to Standard storage tier after a certain amount of time and then from Standard to Standard Infrequent Access storage tier after another amount of time. That means:
379+
- your object can only be transitioned from High Performance to Standard after 30 days
380+
- your object can only be transitioned from Standard to Standard Infrequent Access after 60 days (30 days after the previous transition)
378381

379382
### Expiration vs transitions
380383

@@ -471,7 +474,7 @@ In this scenario, suppose you upload an object with multiple versions:
471474
If the current date is 2024-10-23:
472475

473476
- v5 will be transitioned 30 days after 2024-10-23
474-
- v1 will be transitioned since it has been a noncurrent version for 5 days already
477+
- v1 will be transitioned 30 days after its creation date (2024-10-18)
475478

476479
```json
477480
{
@@ -488,7 +491,7 @@ If the current date is 2024-10-23:
488491
],
489492
"NoncurrentVersionTransitions": [
490493
{
491-
"NoncurrentDays": 5,
494+
"NoncurrentDays": 30,
492495
"StorageClass": "STANDARD"
493496
}
494497
]

‎pages/storage_and_backup/object_storage/s3_bucket_lifecycle/guide.en-sg.md

Lines changed: 10 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -362,11 +362,11 @@ In a versioned bucket, the following configuration does the following actions:
362362
363363
The following are the currently supported transitions:
364364

365-
| from/to | High Performance | Standard | Cold Archive |
366-
| ---------------- | ---------------- | --------- | ------------ |
367-
| High Performance | - | yes | no |
368-
| Standard | forbidden | - | no |
369-
| Cold Archive | forbidden | forbidden | - |
365+
| from/to | High Performance | Standard | Standard Infrequent Access |Cold Archive |
366+
| ---------------- | ---------------- | --------- | -------------------------- |------------ |
367+
| High Performance | - | yes | yes | no |
368+
| Standard | forbidden | - | yes | no |
369+
| Cold Archive | forbidden | forbidden | forbidden | - |
370370

371371
### Minimum object size
372372

@@ -375,6 +375,9 @@ OVHcloud Object Storage will prevent any transition to any storage tier for obje
375375
### Minimum transition delay
376376

377377
The minimum duration for transition rules is **30 days** i.e your lifecycle configuration will not be valid and you will get an error if the number of days for your transition rule is less than 30 days. In practice, it means that the lifecycle feature will only consider objects older than **30 days**.
378+
For example, let's say you upload an object in the High Performance storage tier and you want to transition said object to Standard storage tier after a certain amount of time and then from Standard to Standard Infrequent Access storage tier after another amount of time. That means:
379+
- your object can only be transitioned from High Performance to Standard after 30 days
380+
- your object can only be transitioned from Standard to Standard Infrequent Access after 60 days (30 days after the previous transition)
378381

379382
### Expiration vs transitions
380383

@@ -471,7 +474,7 @@ In this scenario, suppose you upload an object with multiple versions:
471474
If the current date is 2024-10-23:
472475

473476
- v5 will be transitioned 30 days after 2024-10-23
474-
- v1 will be transitioned since it has been a noncurrent version for 5 days already
477+
- v1 will be transitioned 30 days after its creation date (2024-10-18)
475478

476479
```json
477480
{
@@ -488,7 +491,7 @@ If the current date is 2024-10-23:
488491
],
489492
"NoncurrentVersionTransitions": [
490493
{
491-
"NoncurrentDays": 5,
494+
"NoncurrentDays": 30,
492495
"StorageClass": "STANDARD"
493496
}
494497
]

0 commit comments

Comments
 (0)