yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #20652
[Bug 1366842] [NEW] No way to set config-drive property when launching instance
Public bug reported:
The dashboard does not provide an option to enable/disable config drive
when launching an instance. This is a problem for OpenStack deployments
that do not enable the metadata service. For such deployments,
launching an instance from the dashboard will result in the image not
activating properly because config drive was not enabled.
The dashboard does provide options to set "Customization Script" (i.e.
user data), key pair, etc. which only work if config drive is enabled or
the metadata service is enabled. Since a user cannot control whether or
not the metadata service is enabled, the user at least needs control of
config drive to ensure the options work.
** Affects: horizon
Importance: Undecided
Assignee: Justin Pomeroy (jpomero)
Status: New
** Changed in: horizon
Assignee: (unassigned) => Justin Pomeroy (jpomero)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1366842
Title:
No way to set config-drive property when launching instance
Status in OpenStack Dashboard (Horizon):
New
Bug description:
The dashboard does not provide an option to enable/disable config
drive when launching an instance. This is a problem for OpenStack
deployments that do not enable the metadata service. For such
deployments, launching an instance from the dashboard will result in
the image not activating properly because config drive was not
enabled.
The dashboard does provide options to set "Customization Script" (i.e.
user data), key pair, etc. which only work if config drive is enabled
or the metadata service is enabled. Since a user cannot control
whether or not the metadata service is enabled, the user at least
needs control of config drive to ensure the options work.
To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1366842/+subscriptions
Follow ups
References