create clean segregation of storage networks

Registered by Gregory Elkinbard on 2014-03-02

Both swift and ceph now require two storage segments not one.
For Ceph you have a "public" network, this is the network by which librados will reach OSD (monitors use this network as well) and replication network which is used for OSDs to talk to each other.
Latest Swift has introduced this concept as well. with the Storage network proxy to object servers and a replication network used by all background anti-entropy processes.

We are currently mapping one of these network segments in ceph to management network, which is not necessarily the right thing to do as storage/public ceph networks are high bandwidth network segments. We need to be able to cleanly segregate these various storage networks away from the management network.

Blueprint information

Status:
Not started
Approver:
None
Priority:
Low
Drafter:
Gregory Elkinbard
Direction:
Needs approval
Assignee:
Andrew Woodward
Definition:
Drafting
Series goal:
Accepted for future
Implementation:
Not started
Milestone target:
milestone icon next

Related branches

Sprints

Whiteboard

Gerrit topic: https://review.openstack.org/#q,topic:bp/fuel-storage-networks,n,z

Addressed by: https://review.openstack.org/185651
    Blueprint: fuel-storage-networks

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.