Re: How to configure if there are tow network cards in Client

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

You would look to standard Linux routing to take care of this. If NIC1
is on the same subnet as the Ceph cluster, then it will automatically
work. If the NIC is not on the Ceph subnet, then you would use a
static route to route traffic for the Ceph network through NIC1. You
may need a corresponding route on the router to send traffic to that
NIC, but I assume that is already working. There is no Ceph
configuration that you need to do.

I'm moving this to the ceph-users list where it is more appropriate.
- ----------------
Robert LeBlanc
PGP Fingerprint 79A2 9CA4 6CC4 45DD A904  C70E E654 3BB2 FA62 B9F1


On Fri, Dec 25, 2015 at 7:04 AM, 蔡毅  wrote:
> Hi all,
>     When we read the code, we haven’t find the function that the client can bind a specific IP. In Ceph’s configuration, we could only find the parameter “public network”, but it seems acts on the OSD but not the client.
>     There is a scenario that the client has two network cards named NIC1 and NIC2. The NIC1 is responsible for communicating with cluster (monitor and RADOS) and the NIC2 has other services except Ceph’s client. So   we need the client can bind specific IP in order to differentiate the IP communicating with cluster from another IP serving other applications. We want to know is there any configuration in Ceph to achieve this function? If there is, how could we configure the IP? if not, could we add this function in Ceph? Thank you so much.
> Best regards,
> Cai Yi

-----BEGIN PGP SIGNATURE-----
Version: Mailvelope v1.3.2
Comment: https://www.mailvelope.com

wsFcBAEBCAAQBQJWfiZ6CRDmVDuy+mK58QAAAHAQAK3Yjxbhy8UETI6z9FtD
4F/tIw+7t6w9Il3Yp3a79swDcpV5+jiRqvkx7qDmK8ZpshbSxhOyfKrtp24R
qbCFTJceTNWJbgHzqc2D6RdpG4lmphviXJqMc7UUxWbXxG00yY03cVYg9X1y
+i3ZMZ5goSOVY43TVF5/VMb1/IWaUUICTfiIm1R0X2fLBwP3EPRK4l81GlwF
bsnuhRcF1eT0YGKaP4cASQTHDw1Osr2yRIJkVjhml+XbJTJ4ZzM5J9k+BHj3
mNXaWl/7I8mBMjShQu2hTx2xjLv/In+q93ZwOvv32W2JX8FNV3Q9a3TEcixR
FAZ++bE31O0/vt5m4CscDCBZmEA09uQ4WIScrvXMgGjTs0YhK9MbZfpJd3d2
X98BKODUgptDVt9HCi+X5gyq0j03dzJM4sF30bmwPBme07J9/D9Yrs3LtqoA
eJFyWR52fbcI7ESZAzo9yw3BbPwFH/6+E0K1J0x/zCE/bJMNGJs/Q+qcZTGm
X9Q0vUN5gT6bMbKshAoR7XSAuxLpdrtX+x/eHQ1tZiRk+I38MczicCHHEZ+Z
b3zRvWMjSqbhufOK4cM0NSVEAhN40+J2+VfxRQ81/WfG3JOAwLTNPaLDpkJF
sQxEyYiKJRZO7f24g0KdNlXm62shzDjeE0pWJh7h29onWQkvYMzgQGklbWQV
zYU9
=fpri
-----END PGP SIGNATURE-----
_______________________________________________
ceph-users mailing list
ceph-users@xxxxxxxxxxxxxx
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




[Index of Archives]     [Information on CEPH]     [Linux Filesystem Development]     [Ceph Development]     [Ceph Large]     [Ceph Dev]     [Linux USB Development]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [xfs]


  Powered by Linux