On Tue, Mar 05, 2013 at 01:31:12AM +0900, Go Chiba wrote: > Hi folks, > > I have a question for traffic type that discussed as CLOUDSTACK-382 on JIRA. > ref: > https://issues.apache.org/jira/browse/CLOUDSTACK-382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel > > By my understanding, "storage traffic" isolation on CS means separate disk > I/O for primary storage as that explained blog post by shapeblue team and I > believe their explanation is correct. > But could you clearly my understanding for architecture of CS networking. > Because, official document cause misunderstanding or confusion as me and it > caused business impact for design of production services of several > enterprise users... > > regards > -- > Go Chiba > E-mail:go.ch...@gmail.com
When the documentation says "storage traffic", it's actually talking about traffic to and from the secondary storage of the zone. The point of that bug, is that it's obviously quite confusing to simply call it "storage traffic". What we've done, in order to isolate traffic intended for *primary storage* (Xen environment at least) to a dedicated pair of NICs on the hosts, is to pre-create the storage volumes in the Xen clusters. Then, CS simply knows about the pre-existing primary storage, and you are able to have at least host to primary storage traffic running through it's own cables to the top of rack switches. -chip
