Yes it's quite confusing. My best guess, just guess, is CloudStack used to have similar feature but somehow dropped it at some moment, however, the doc was not updated promptly. Anyway, the storage network in current code base means secondary storage. Could you file a bug on http://bugs.cloudstack.org/ for this issue? Thank you.
> -----Original Message----- > From: Geoff Higginbottom [mailto:geoff.higginbot...@shapeblue.com] > Sent: Friday, June 22, 2012 12:43 PM > To: cloudstack-dev@incubator.apache.org > Subject: RE: Storage Networks XenServer > > Hi Frank > > If the storage network is for Secondary Storage, why does the admin guide > contain the following > > "For the separate storage network to work correctly, it must be the only > interface that can ping the primary storage device's IP address. For example, > if eth0 is the management network NIC, ping -I eth0 <primary storage device > IP> must fail. In all deployments, secondary storage devices must be pingable > from the management network NIC or bond. If a secondary storage device > has been placed on the storage network, it must also be pingable via the > storage network NIC or bond on the hosts as well." > > And it also states > > "The secondary storage NFS export is mounted by the secondary storage VM. > Secondary storage traffic goes over the management traffic network, even if > there is a separate storage network. Primary storage traffic goes over the > storage network, if available. If you choose to place secondary storage NFS > servers on the storage network, you must make sure there is a route from > the management traffic network to the storage network." > > This seems to make it very clear that the "Storage Network" is for Primary > Storage, not Secondary. > > Geoff > > > -----Original Message----- > From: Frank Zhang [mailto:frank.zh...@citrix.com] > Sent: 22 June 2012 19:45 > To: cloudstack-dev@incubator.apache.org > Subject: RE: Storage Networks XenServer > > See my another reply. > The storage network(I admit it's a bad term for this feature) is indeed for > secondary storage now. > > > -----Original Message----- > > From: Weiran Xia [mailto:weiran.x...@gmail.com] > > Sent: Friday, June 22, 2012 4:57 AM > > To: cloudstack-dev@incubator.apache.org > > Subject: Re: Storage Networks XenServer > > > > here i got a similar question, there seems be some confusion in > terminology. > > > > From > > http://wiki.cloudstack.org/display/DesignDocs/Storage+network+in+Acton > > it says a storage network is for speeding up template/snapshot copying > > process, and indeed during the zone creation process there is a step > > of configuring this network(ip range,gateway..). when the SSVM is up > > and running it gets 4 NICs, one of them is dedicated for this purpose. > > > > But where is the storage network for primary storage? is this storage > > network only defined by label in step two (drag and drop) of zone creation? > > is there any relationship between two 'storage networks'? > > > > thanks very much if someone can clarify the storage nework in 3.0.x > > > > Regards > > Mice > > ShapeBlue provides a range of strategic and technical consulting and > implementation services to help IT Service Providers and Enterprises to build > a true IaaS compute cloud. ShapeBlue’s expertise, combined with CloudStack > technology, allows IT Service Providers and Enterprises to deliver true, > utility > based, IaaS to the customer or end-user. > > ________________________________ > > This email and any attachments to it may be confidential and are intended > solely for the use of the individual to whom it is addressed. Any views or > opinions expressed are solely those of the author and do not necessarily > represent those of Shape Blue Ltd. If you are not the intended recipient of > this email, you must neither take any action based upon its contents, nor > copy or show it to anyone. Please contact the sender if you believe you have > received this email in error. Shape Blue Ltd is a company incorporated in > England & Wales.
