Bug 1299743
Summary: | [RFE] Set default value for "Instance Boot Source" in Horizon dashboard | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Anand Nande <anande> |
Component: | python-django-horizon | Assignee: | Beth White <beth.white> |
Status: | CLOSED DUPLICATE | QA Contact: | Ido Ovadia <iovadia> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 7.0 (Kilo) | CC: | achernet, aortega, apannu, athomas, beth.white, chris.brown, ealcaniz, jrist, markmc, mburns, mrunge, rdopiera, rhos-maint, srevivo, tvignaud |
Target Milestone: | Upstream M2 | Keywords: | FutureFeature, Triaged, ZStream |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Enhancement | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-06-29 11:37:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Comment 2
Edu Alcaniz
2016-09-16 06:40:16 UTC
Could you update the target of the RFE please Moved to OSP 12 It would be good to see some attention on this. The side effect of defaulting to boot from volume means we get lots of volumes and space used. For people reading/subscribed to this bz, it might be possible that some of the following settings help: https://docs.openstack.org/developer/horizon/topics/settings.html LAUNCH_INSTANCE_LEGACY_ENABLED=True or LAUNCH_INSTANCE_NG_ENABLED=False which could help to restore old functionality as a potential workaround. There is also: LAUNCH_INSTANCE_DEFAULTS but this only appears to disable booting from volume entirely. Finally this bug: https://bugs.launchpad.net/horizon/+bug/1640493 indicates a fix may be landing to allow a user to set a default. Thanks so much for your information This is a duplicate bug of https://bugzilla.redhat.com/show_bug.cgi?id=1432963 A fix has been released upstream and backported to OSP10 to address this. The solution is that a user can now configure the default "create volume" value when launching an instance. *** This bug has been marked as a duplicate of bug 1432963 *** |