cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9019) Storage VM gets two mgmt nics when no storage net defined
Date Tue, 03 Nov 2015 20:31:27 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14988057#comment-14988057
] 

ASF subversion and git services commented on CLOUDSTACK-9019:
-------------------------------------------------------------

Commit 8922707076632d478d7ed088a08bf24261e07c82 in cloudstack's branch refs/heads/master from
[~rohit.yadav@shapeblue.com]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=8922707 ]

CLOUDSTACK-9019: Add storage network offering in ssvm only if storage network is defined

During creation of SSVM, checks and adds NetworkOffering.SystemStorageNetwork to
offerings only if storage network exists for the target datacenter

Signed-off-by: Rohit Yadav <rohit.yadav@shapeblue.com>


> Storage VM gets two mgmt nics when no storage net defined
> ---------------------------------------------------------
>
>                 Key: CLOUDSTACK-9019
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9019
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Rohit Yadav
>            Assignee: Rohit Yadav
>             Fix For: 4.5.3, 4.6.0
>
>
> If a dedicated storage network is not provided in a zone, secondary storage VMs get two
management nics. This eats up an additional IP, the fix would be to allocate a storage nic
only when storage network is defined.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message