Advanced Settings

Bug #1326128 reported by Jesse Pretorius
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Won't Fix
Fuel Python (Deprecated)

Bug Description

There are advanced settings which a user may wish to change in their environment, but there is no way to do it through Fuel.

OpenStack examples from nova.conf:
 - cpu_allocation_ratio
 - ram_allocation_ratio
 - disk_allocation_ratio
 - cpu_mode
 - dhcp_domain
 - allow_resize_to_same_host
 - default_availability_zone (per node, or per environment)
 - default_floating_pool
 - default quota settings

OpenStack examples for Horizon:
 - upload (or perhaps rather provide a URL to) a custom css/logo/favicon

Fuel examples:
 - additional package repositories per role
 - additional packages per role
 - node name prefix per role (instead of all nodes being node-<num>)

Ideally settings like these should be exposed in something like an 'Advanced Settings' interface, allowing the user to change them if they'd like to.

summary: - Advanced Openstack settings
+ Advanced Settings
description: updated
description: updated
description: updated
Dima Shulyak (dshulyak)
Changed in fuel:
milestone: none → 5.1
assignee: nobody → Fuel Python Team (fuel-python)
Revision history for this message
Dima Shulyak (dshulyak) wrote :

I think to cover all edge cases we need some kind of config passthrough for each service, but it requires additional spec for sure

Changed in fuel:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Dima Shulyak (dshulyak) wrote :

In my opinion this is ideal candidate for plugin, for fuelweb everything necessery is almost there, just need merge stuff.
Need to properly design this, and decide on priority.

Changed in fuel:
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.