Delete the presence of default flavors
There are not any default flavors after the commit "Remove flavor seeding from the base migration" which removes default flavors from the database, that means the new deploys will not have them(m1.tiny, m1.small, m1.medium, m1.large, m1.xlarge). Change-Id: Ifcdd6f1500a937de8dfd9d265bd5ee3406cb70e0 Closes-Bug: #1567009
This commit is contained in:
@@ -279,10 +279,9 @@ The displayed image attributes are:
|
||||
is the UUID of the instance the snapshot derives from. For uploaded
|
||||
images, this field is blank.
|
||||
|
||||
Virtual hardware templates are called ``flavors``. The default
|
||||
installation provides five flavors. By default, these are configurable
|
||||
by admin users, however that behavior can be changed by redefining the
|
||||
access controls for ``compute_extension:flavormanage`` in
|
||||
Virtual hardware templates are called ``flavors``. By default, these are
|
||||
configurable by admin users, however that behavior can be changed by
|
||||
redefining the access controls for ``compute_extension:flavormanage`` in
|
||||
``/etc/nova/policy.json`` on the ``compute-api`` server.
|
||||
|
||||
For a list of flavors that are available on your system:
|
||||
|
||||
@@ -364,8 +364,9 @@ The displayed image attributes are:
|
||||
is the UUID of the instance the snapshot derives from. For uploaded
|
||||
images, this field is blank.
|
||||
|
||||
Virtual hardware templates are called ``flavors``. The default
|
||||
installation provides five predefined flavors.
|
||||
Virtual hardware templates are called ``flavors``, and are defined by
|
||||
administrators. Prior to the Newton release, a default installation also
|
||||
includes five predefined flavors.
|
||||
|
||||
For a list of flavors that are available on your system, run:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user