[
https://issues.apache.org/jira/browse/DTACLOUD-577?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13697691#comment-13697691
]
Dies Koper commented on DTACLOUD-577:
-------------------------------------
I've started on a fix in this branch but need your help:
https://github.com/dkoper/deltacloud-core/commits/cimi-ui
(see CIMI: changed CEP key names and order to match spec)
This fixed the element names and order, but has a side-effect: their hrefs
changed too!
<machineConfigs href="http://localhost:3001/cimi/machine_configs"; />
To reduce the impact on existing clients (and DC tests, etc.), I'd like to only
change the element name and not the href. How?
> cimi: config element names in CEP (volumeConfigurations, etc.) are incorrect:
> should be volumeConfigs, etc.
> -----------------------------------------------------------------------------------------------------------
>
> Key: DTACLOUD-577
> URL: https://issues.apache.org/jira/browse/DTACLOUD-577
> Project: DeltaCloud
> Issue Type: Bug
> Components: CIMI/Frontend
> Reporter: Dies Koper
>
> I noticed the element names for *Configurations returned in the CEP don't
> match the names and order in the CIMI spec:
> $ curl -u mockuser:mockpassword http://localhost:3001/cimi/cloudEntryPoint
> -H "Accept: application/xml"
> <CloudEntryPoint xmlns="http://schemas.dmtf.org/cimi/1";
> resourceURI="http://schemas.dmtf.org/cimi/1/CloudEntryPoint";>
> ...
> <forwardingGroups href="http://localhost:3001/cimi/forwarding_groups";
> />
> <volumeConfigurations
> href="http://localhost:3001/cimi/volume_configurations"; />
> <machineConfigurations
> href="http://localhost:3001/cimi/machine_configurations"; />
> <networkConfigurations
> href="http://localhost:3001/cimi/network_configurations"; />
> <networkPortConfigurations
> href="http://localhost:3001/cimi/network_port_configurations"; />
> </CloudEntryPoint>
> The "*Configurations" elements are called "*Configs" in the spec, and each
> Configs entry comes directly after *Templates instead of all together at the
> end.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
