Hello, That makes sense to me. Still, I want to point that we're going to implement advanced networking and with this feature you'll be able to assign every single network role to any network.
That means, you'll be able to assign ceph network role to storage, management or whatever-you-want network. Sounds cool, ha? :) Feel free to read a design spec [1]. Thanks, Igor [1]: https://review.openstack.org/#/c/115340/ On Tue, Jun 23, 2015 at 1:13 PM, Zhou Zheng Sheng / 周征晟 <[email protected]> wrote: > Hi! > > I notice that in OpenStack deployed by Fuel, Ceph public network is on > management network. In some environments, not all NICs of a physical > server are 10Gb. Sometimes 1 or 2 among the NICs on a machine may be > 1Gb. Usually on this type of machine we assign management network to 1Gb > NIC, and storage network to 10Gb NIC. If Ceph public network is with > management network, the QEMU accesses Ceph using management network, and > the performance is not optimal. > > In a small deployment, cloud controller and Ceph OSD may be assigned to > the same machine, so it would be more effective to keep Ceph client > traffic separated from MySQL, RabbitMQ, Pacemaker traffic. Maybe it's > better to place Ceph public network on the storage network. Agree? > > -- > Best wishes! > Zhou Zheng Sheng, Software Developer > Beijing AWcloud Software Co., Ltd. > > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: [email protected]?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: [email protected]?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
