Allow Post Server Extensions To Be Disabled
Some server extensions allow extra parameters to be posted along with the server entity. There is currently no way for these extensions to be disabled, which creates confusion about the core api spec. This blueprint encompasses adding a simple set of checks for enabled extensions before handling this post data.
Blueprint information
- Status:
- Complete
- Approver:
- Vish Ishaya
- Priority:
- High
- Drafter:
- Vish Ishaya
- Direction:
- Needs approval
- Assignee:
- Vish Ishaya
- Definition:
- Approved
- Series goal:
- Accepted for folsom
- Implementation:
-
Implemented
- Milestone target:
-
2012.2
- Started by
- Thierry Carrez
- Completed by
- Vish Ishaya
Related branches
Related bugs
Sprints
Whiteboard
Gerrit topic: https:/
Addressed by: https:/
Make extension aliases consistent
Addressed by: https:/
Allow loaded extensions to be checked from servers
Addressed by: https:/
Adds ability to inherit wsgi extensions
Addressed by: https:/
Moves security group functionality into extension
Addressed by: https:/
Key block_device_
Addressed by: https:/
Key user_data in create server off of extension
Addressed by: https:/
Only accept scheduler_hints if extension is enabled
Addressed by: https:/
Key availability_zone in create server off of ext.
Addressed by: https:/
Key min_count, max_count, ret_res_id off of ext.
Addressed by: https:/
Don't accept key_name if not enabled
Addressed by: https:/
Key requested_networks off of network extension
Addressed by: https:/
Key config_drive off of config-drive extension
Addressed by: https:/
Key auto_disk_config in create server off of ext.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
