Skip to content

Commit 1c3811c

Browse files
committed
Add note for editing lease for compute offering and lowest possible value for scheduler interval
1 parent 5a2ef2d commit 1c3811c

File tree

2 files changed

+5
-1
lines changed

2 files changed

+5
-1
lines changed

source/adminguide/service_offerings.rst

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -411,8 +411,10 @@ To create a new compute offering:
411411
These lease settings are defined in the Compute Offering and are automatically applied to any Instance created using it.
412412

413413
.. note:: The global configuration ``instance.lease.enabled`` should be configured as true to create compute offering with lease.
414+
415+
.. note:: Lease duration or expiryaction can't be updated for compute offering.
414416

415-
``instance.lease.enabled``: Indicates whether Instance Lease feature is enabled or not. Default is **false**
417+
``instance.lease.enabled``: Indicates whether Instance Lease feature is enabled or not. Default is **false**
416418
For more information, see `“Setting Global Configuration Parameters”
417419
<../installguide/configuration.html#setting-global-configuration-parameters>`_.
418420

source/adminguide/virtual_machines.rst

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -999,6 +999,8 @@ instance.lease.eventscheduler.interval Background task interval in seconds tha
999999
instance.lease.expiryevent.daysbefore Denotes number of days (N) in advance expiry events are generated for instance about to expire. Default: 7 days
10001000
======================================= ========================
10011001

1002+
.. note:: it is recommended to configure the lowest possible value (in secs) for **instance.lease.scheduler.interval**, so that lease expiry action is taken as soon as lease is expired.
1003+
10021004

10031005
**Lease Parameters**
10041006

0 commit comments

Comments
 (0)