[
https://issues.apache.org/jira/browse/CLOUDSTACK-8190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14301140#comment-14301140
]
ASF subversion and git services commented on CLOUDSTACK-8190:
-------------------------------------------------------------
Commit 48ec9ac11b0772ffb9b7be4947f26aba0ad9b89d in cloudstack's branch
refs/heads/4.5 from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=48ec9ac ]
CLOUDSTACK-8190: Fix xenserver traffic label for backward compatiblity
Signed-off-by: Rohit Yadav <[email protected]>
> XenServer traffic label has changed in 4.5, backward incompatibility is lost
> ----------------------------------------------------------------------------
>
> Key: CLOUDSTACK-8190
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8190
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Xen, XenServer
> Affects Versions: 4.5.0, 4.6.0
> Reporter: Rohit Yadav
> Assignee: Rohit Yadav
> Fix For: 4.5.0, 4.6.0
>
>
> Until 4.4, XenServer traffic label was xennetworklabel but in 4.5/master it's
> xenservernetworklabel. To keep backward compatibility I'm reverting such
> changes introduced in a8212d9ef458dd7ac64b021e6fa33fcf64b3cce0 (xenserver
> plugin refactoring). When in future we'll have a separate xen project plugin
> (based on libvirt or what have you) we should add a new label like
> xenprojectnetworklabel but let's keep the old one for backward
> compatibility's sake.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
