[
https://issues.apache.org/jira/browse/CLOUDSTACK-9019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14986890#comment-14986890
]
ASF GitHub Bot commented on CLOUDSTACK-9019:
--------------------------------------------
GitHub user bhaisaab opened a pull request:
https://github.com/apache/cloudstack/pull/1025
[4.5] 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
(Manually tested)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/shapeblue/cloudstack CLOUDSTACK-9019-4.5
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1025.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1025
----
commit 619f0eb276499a7b8f31d31f6479d27f215c7b3f
Author: Rohit Yadav <[email protected]>
Date: 2015-11-03T08:17:23Z
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 <[email protected]>
----
> 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)
