[
https://issues.apache.org/jira/browse/ARIA-165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16000785#comment-16000785
]
Maxim Orlov commented on ARIA-165:
----------------------------------
We can uitilze the SQLAlcehmy events mechanism, which could automate the name
composition. However, this mechanism is a bit more complicated as it requires
better knowledge of sqlalcehmy (and SQL). Example:
http://stackoverflow.com/questions/32277403/how-can-i-create-a-sqlalchemy-column-whose-default-is-to-be-equal-to-the-primary
Another optional fix is the use of the length of the list of the current nodes
for the relevant node_template. This would enable easy suffices but once a node
is deleted, a new node could get the old node's name.
The latter is the current fix for this issue.
> Make node name suffix UUIDs become more readable
> ------------------------------------------------
>
> Key: ARIA-165
> URL: https://issues.apache.org/jira/browse/ARIA-165
> Project: AriaTosca
> Issue Type: Story
> Reporter: Ran Ziv
> Assignee: Maxim Orlov
> Priority: Minor
>
> Node names are currently constructed of the node template name with a UUID
> suffix. While this makes the node name unique across all services, it also
> makes the node names less readable, and since nodes are already unique via
> their ID, it might be better to use a different type of suffix.
> One option would be to generate a shorter, no capital letters string, which
> would be more readable, and (in very high probability) unique in a single
> service.
> Another option would be to go for a running number suffix for each node of a
> given node template, which could be simple, unique and readable.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
