cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chip Childers (JIRA)" <>
Subject [jira] [Resolved] (CLOUDSTACK-2215) ACS41 SSVM does not use allocated storage ip range
Date Fri, 26 Apr 2013 18:08:15 GMT


Chip Childers resolved CLOUDSTACK-2215.

       Resolution: Invalid
    Fix Version/s:     (was: 4.1.0)
         Assignee: Chip Childers

After discussing this with Ilya on IRC, this isn't a bug as much as it's a feature request.

The 3 IP's being assigned from the public network portion of the description is an outstanding
question, but Ilya will raise it on the MLs to undstand if it's a bug or not.
> 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