[
https://issues.apache.org/jira/browse/CLOUDSTACK-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13663688#comment-13663688
]
Mice Xia commented on CLOUDSTACK-2215:
--------------------------------------
Ilya,
I built a test environment but cannot reproduce it, can you describe
how-to-reproduce in details?
Here is my configuration FYI:
CS 4.1, Xenserver with two NICs
* NIC 1 (public/management/guest)
public: untagged 1.1.1.130 - 1.1.1.139
private: untagged 1.1.1.141 - 1.1.1.149
* NIC 2 (storage)
storage: untagged: 192.168.10.151 - 192.168.10.160
* Secondary storage:
192.168.10.8
* ip route result on SSVM:
8.8.8.8 via 1.1.1.10 dev eth1
1.1.1.0/24 dev eth1 proto kernel scope link src 1.1.1.141
1.1.1.0/24 dev eth2 proto kernel scope link src 1.1.1.130
192.168.10.0/24 dev eth3 proto kernel scope link src 192.168.10.152
169.254.0.0/16 dev eth0 proto kernel scope link src 169.254.2.109
default via 1.1.1.10 dev eth2
the result of route table is correct and eth3, which is for storage network, is
allocated with correct IP address
VM deploy: succeed
ISO upload: succeed
> ACS41 SSVM does not use allocated storage ip range
> --------------------------------------------------
>
> Key: CLOUDSTACK-2215
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2215
> 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.0.1, 4.0.2, 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
> 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: http://www.atlassian.com/software/jira
