cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ilya musayev (JIRA)" <>
Subject [jira] [Reopened] (CLOUDSTACK-2215) ACS41 SSVM does not use allocated storage ip range
Date Thu, 16 May 2013 16:15:16 GMT


ilya musayev reopened CLOUDSTACK-2215:


As per IRC communication with several users, we believe this is a valid issue and it was reported
by 2 people on IRC in 2 days.

Below is excerpt from the doc:
Storage. Traffic such as VM templates and snapshots, which is sent between the secondary storage
VM and secondary storage servers. CloudStack uses a separate Network Interface Controller
(NIC) named storage NIC for storage network traffic. Use of a storage NIC that always operates
on a high bandwidth network allows fast template and snapshot copying. You must configure
the IP range to use for the storage network.

My understanding of this - SSVM should get an IP and network configs from the network range
defined by on storage network. Where as now, it does not.

I've asked another user on IRC, NDK to update this issue as he has the same problem on KVM

> ACS41 SSVM does not use allocated storage ip range
> --------------------------------------------------
>                 Key: CLOUDSTACK-2215
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller, Storage Controller
>    Affects Versions: 4.1.0
>         Environment: ACS4.1 as of 04/15/13 - i know its 10 days old, but i've not seen
fixes for this yet.
> VMWare vSphere 5.0 with Advanced Network
>            Reporter: ilya musayev
>            Assignee: Chip Childers
>            Priority: Blocker
>              Labels: Network, SSVM
> Create Advanced Network Zone, assign a range of IPs to storage network, also predefine
public range. 
> The Secondary Storage VM gets the IPs of Public Networks and not whats its been given.
In my example, i've defined two public networks - with very small ip range (4 on each). I
noticed that SSVM took 2 IPs from Public Network A, and 1 IP from Public Network B. 
> If you have stringent setup and you need to allocate IPs as designed and setup firewall
rules, one would expect to setup firewall rules on storage ip range, thinking that SSVM is
going to use the IP from that range, however, instead - it uses public ip range.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message