[
https://issues.apache.org/jira/browse/CLOUDSTACK-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13827071#comment-13827071
]
Nitin Mehta commented on CLOUDSTACK-5206:
-----------------------------------------
Admin should have the ability to control the external facing id of their
resources (first class objects). This is important say in case of emergencies
when he/she wants to recover their resources.
For this I propose that all the resource creation/updation API's need to be
altered to take in the custom resource id in case the admin wants a custom id.
Please note following for the custom ids :-
This is an optional field and if not set, CS will use its custom logic to
assign the resource id.
They have to be unique for the particular type of resource.
They will have to follow the UUID format.
This is external Id change only and MS refers to all the objects through the DB
ids
> Admin should have the ability to control the external facing id of their
> resources
> ----------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5206
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5206
> Project: CloudStack
> Issue Type: New Feature
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Nitin Mehta
> Assignee: Nitin Mehta
> Fix For: Future
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
