Bug #5179
sunstone not allowing custom attributes in datastore definitions
| Status: | Closed | Start date: | 06/07/2017 | |
|---|---|---|---|---|
| Priority: | High | Due date: | ||
| Assignee: |  Abel Coronado | % Done: | 100% | |
| Category: | Sunstone | |||
| Target version: | Release 5.4 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 5.2 |
Description
The current implementation is closing the sunstone interface to alter only the known(to sunstone) attributes
How to reproduce:
It is easilly reproducible when creating a new datastore with custom TM_MAD and DS_MAD.
The when custom is selected the sunstone wizard suggest only known attributes: LVM, Gluster, CEPH and iSCSI which is OK as they are the upstream MADs
After the datastore is registered I am trying to add attributes that are relevant to the "custom" MADs like 'CUSTOM_ATTR' with value '2'
The interface forbid adding attributes that are not known with error message "Not valid attribute"
IMO the sunstone must allow any attribute if it is custom template. Or there should be attribute whitelist in the given DS_MAD/TM_MAD definition in oned.conf. Or oneadmin user should have the rights to add any attribute(as it is in 5.2.1 and below)
Currently all attributes for our addon should be patched in sunstone and recompiled. And if there is something I need to test/add - I need to patch again and recompile the javascripts, which is far from convinient workflow.
BR,
Anton
Associated revisions
Bug #5179 sunstone not allowing custom attributes in datastore definitions
History
#1
Updated by OpenNebula Systems Support Team about 4 years ago
- Status changed from Pending to New
- Assignee set to Abel Coronado
- Target version set to Release 5.4
#2
Updated by Abel Coronado about 4 years ago
- % Done changed from 0 to 100
- Affected Versions OpenNebula 5.2 added
#3
Updated by OpenNebula Systems Support Team about 4 years ago
- Status changed from New to Closed
- Resolution set to fixed