Merge "Correct spelling mistakes"
This commit is contained in:
commit
74c2c6f366
@ -377,7 +377,7 @@ class VirtualInstancePlugin(base.BasePlugin, nova.NovaClientWrapper):
|
||||
following conditions.
|
||||
- If an instance reservation has not started yet
|
||||
- vcpus, memory_mb disk_gb and amount can be updateable unless
|
||||
Blazar can accomodate the new request.
|
||||
Blazar can accommodate the new request.
|
||||
- If an instance reservation has already started
|
||||
- only amount is increasable.
|
||||
"""
|
||||
|
@ -50,7 +50,7 @@ specs focuses only on supporting resource_properties matches to
|
||||
ComputeHostExtraCapability.
|
||||
|
||||
When an user reserves instances with resource_properties, Blazar picks up
|
||||
hypervisors which can accomodate the requested flavor and the resource_properties.
|
||||
hypervisors which can accommodate the requested flavor and the resource_properties.
|
||||
|
||||
When admins update ComputeHostExtraCapability, Blazar re-allocates reservations
|
||||
related to the updated ExtraCapability. The re-allocation strategy is the same
|
||||
|
@ -61,7 +61,7 @@ before they call the create host API.
|
||||
ComputeExtraCapability approach
|
||||
```````````````````````````````
|
||||
|
||||
Operators define az infomation as ComputeExtraCapability to enable users can
|
||||
Operators define az information as ComputeExtraCapability to enable users can
|
||||
specify az when they create a reservation.
|
||||
|
||||
The good point of this approach is there is no need to change Blazar's APIs
|
||||
|
@ -9,5 +9,5 @@ features:
|
||||
upgrade:
|
||||
- |
|
||||
The availability zone information is stored only when cloud operators add
|
||||
a new host to Blazar's freepool. If the operators needs the infomation,
|
||||
a new host to Blazar's freepool. If the operators needs the information,
|
||||
please re-add hosts already registered in Blazar.
|
Loading…
Reference in New Issue
Block a user