mirror of
https://github.com/minio/docs.git
synced 2025-07-30 07:03:26 +03:00
DOCS-399: Resolve ILM related issues
This commit is contained in:
ravindk89
Ravind Kumar
@ -1,96 +1,57 @@
|
||||
.. start-create-transition-rule-desc
|
||||
|
||||
Use the :mc-cmd:`mc ilm add` command to create a new transition rule
|
||||
for the bucket. The following tabs contain examples for transitioning
|
||||
objects on a calendar date *or* after a number of calendar days.
|
||||
for the bucket. The following example configures transition after the
|
||||
specified number of calendar days:
|
||||
|
||||
.. tab-set::
|
||||
.. code-block:: shell
|
||||
:class: copyable
|
||||
|
||||
.. tab-item:: Transition after Calendar Date
|
||||
mc ilm add ALIAS/BUCKET \
|
||||
--storage-class TIERNAME \
|
||||
--transition-days DAYS \
|
||||
--noncurrentversion-transition-days NONCURRENT_DAYS
|
||||
--noncurrentversion-transition-storage-class TIERNAME
|
||||
|
||||
.. code-block:: shell
|
||||
:class: copyable
|
||||
The example above specifies the following arguments:
|
||||
|
||||
mc ilm add ALIAS/BUCKET \
|
||||
--storage-class TIERNAME \
|
||||
--transition-date DATE \
|
||||
--noncurrentversion-transition-date NONCURRENT_DAYS
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 30 70
|
||||
:width: 100%
|
||||
|
||||
The example above specifies the following arguments:
|
||||
* - Argument
|
||||
- Description
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 40 60
|
||||
:width: 100%
|
||||
* - :mc-cmd:`ALIAS <mc ilm add TARGET>`
|
||||
- Specify the :mc:`alias <mc alias>` of the MinIO deployment for which
|
||||
you are creating the lifecycle management rule.
|
||||
|
||||
* - Argument
|
||||
- Description
|
||||
* - :mc-cmd:`BUCKET <mc ilm add TARGET>`
|
||||
- Specify the full path to the bucket for which you are
|
||||
creating the lifecycle management rule.
|
||||
|
||||
* - :mc-cmd:`ALIAS <mc ilm add TARGET>`
|
||||
- Specify the :mc:`alias <mc alias>` of the MinIO deployment for which
|
||||
you are creating the lifecycle management rule.
|
||||
* - :mc-cmd:`TIERNAME <mc ilm add storage-class>`
|
||||
- The remote storage tier to which MinIO transitions objects.
|
||||
Specify the remote storage tier name created in the previous step.
|
||||
|
||||
* - :mc-cmd:`BUCKET <mc ilm add TARGET>`
|
||||
- Specify the full path to the bucket for which you are
|
||||
creating the lifecycle management rule.
|
||||
If you want to transition noncurrent object versions to a distinct
|
||||
remote tier, specify a different tier name for
|
||||
:mc-cmd-option:`~mc ilm add noncurrentversion-transition-storage-class`.
|
||||
|
||||
* - :mc-cmd:`TIERNAME <mc ilm add storage-class>`
|
||||
- The remote storage tier to which MinIO transitions objects.
|
||||
Specify the remote storage tier name created in the previous step.
|
||||
* - :mc-cmd:`DAYS <mc ilm add transition-days>`
|
||||
- The number of calendar days after which MinIO marks an object as
|
||||
eligible for transition.
|
||||
|
||||
* - :mc-cmd:`DATE <mc ilm add transition-date>`
|
||||
- The ISO-8601-formatted calendar date after which MinIO marks an object
|
||||
as eligible for transition.
|
||||
* - :mc-cmd:`NONCURRENT_DAYS <mc ilm add noncurrentversion-transition-days>`
|
||||
- The number of calendar days after which MinIO marks a noncurrent
|
||||
object version as eligible for transition. MinIO specifically measures
|
||||
the time since an object *became* non-current instead of the object
|
||||
creation time.
|
||||
|
||||
Omit this value to ignore noncurrent object versions.
|
||||
|
||||
* - :mc-cmd:`NONCURRENT_DAYS <mc ilm add noncurrentversion-transition-days>`
|
||||
- The number of calendar days after which MinIO marks a noncurrent
|
||||
object version as eligible for transition. Omit this value to
|
||||
ignore noncurrent object versions.
|
||||
|
||||
This option has no effect on non-versioned buckets.
|
||||
|
||||
.. tab-item:: Transition after Calendar Days
|
||||
|
||||
.. code-block:: shell
|
||||
:class: copyable
|
||||
|
||||
mc ilm add ALIAS/BUCKET \
|
||||
--storage-class TIERNAME \
|
||||
--transition-days DAYS \
|
||||
--noncurrentversion-transition-days NONCURRENT_DAYS
|
||||
|
||||
The example above specifies the following arguments:
|
||||
|
||||
.. list-table::
|
||||
:header-rows: 1
|
||||
:widths: 40 60
|
||||
:width: 100%
|
||||
|
||||
* - Argument
|
||||
- Description
|
||||
|
||||
* - :mc-cmd:`ALIAS <mc ilm add TARGET>`
|
||||
- Specify the :mc:`alias <mc alias>` of the MinIO deployment for which
|
||||
you are creating the lifecycle management rule.
|
||||
|
||||
* - :mc-cmd:`BUCKET <mc ilm add TARGET>`
|
||||
- Specify the full path to the bucket for which you are
|
||||
creating the lifecycle management rule.
|
||||
|
||||
* - :mc-cmd:`TIERNAME <mc ilm add storage-class>`
|
||||
- The remote storage tier to which MinIO transitions objects.
|
||||
Specify the remote storage tier name created in the previous step.
|
||||
|
||||
* - :mc-cmd:`DAYS <mc ilm add transition-days>`
|
||||
- The number of calendar days after which MinIO marks an object as
|
||||
eligible for transition.
|
||||
|
||||
* - :mc-cmd:`NONCURRENT_DAYS <mc ilm add noncurrentversion-transition-days>`
|
||||
- The number of calendar days after which MinIO marks a noncurrent
|
||||
object version as eligible for transition. Omit this value to
|
||||
ignore noncurrent object versions.
|
||||
|
||||
This option has no effect on non-versioned buckets.
|
||||
This option has no effect on non-versioned buckets.
|
||||
|
||||
|
||||
.. end-create-transition-rule-desc
|
||||
|
||||
Reference in New Issue
Block a user