From: Matt Benjamin <mbenjamin@redhat.com>
To: kernel neophyte <neophyte.hacker001@gmail.com>
Cc: vu@mellanox.com, raju kurunkad <raju.kurunkad@sandisk.com>,
ceph-devel@vger.kernel.org, Marcus Watts <mwatts@redhat.com>
Subject: Re: Cluster Network & Public Network w.r.t XIO ?
Date: Fri, 31 Jul 2015 13:04:12 -0400 (EDT) [thread overview]
Message-ID: <1211289190.918749.1438362252889.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <CAFkUHxcyxHO-0OyB9-v+6TeHAXRPQVS+LFeP7K7ywvEw0g=b_A@mail.gmail.com>
Hi Neo,
I'm not sure of the state of current WIP, but Marcus (CC'd) is coordinating atm
from our end. I'm sure we'd love help, so we'll check back in with updated branch
info--maybe next week?
Matt
----- Original Message -----
From: "kernel neophyte" <neophyte.hacker001@gmail.com>
To: "Matt Benjamin" <mbenjamin@redhat.com>
Cc: vu@mellanox.com, "raju kurunkad" <raju.kurunkad@sandisk.com>, ceph-devel@vger.kernel.org, "Marcus Watts" <mwatts@redhat.com>
Sent: Friday, July 31, 2015 12:20:33 PM
Subject: Re: Cluster Network & Public Network w.r.t XIO ?
On Fri, Jul 31, 2015 at 7:49 AM, Matt Benjamin <mbenjamin@redhat.com> wrote:
> Hi Neo,
>
> On our formerly-internal firefly-based branch, what we did was create additional Messenger
> instances ad infinitum, which at least let you do this, but it's not what anybody wanted for
> upstream or long-term. What's upstream now doesn't let you IIRC describe that. The rdma_local
> parameter like you say is insufficient (and actually a hack).
>
> What we plan to do (and have in progress) is extending work Sage started on wip-address, which
> will enable multi-homing and identify instances by their transport type(s). We might put more
> information there to help with future topologies. Improved configuration language to let you
> describe your desired network setup would be packaged with that.
This is awesome! could you please point me to your WIP branch ? Also
please let know if I could help speed up the dev/test process ?
-Neo
>
> The plan is that an improved situation might arrive as early as J. If we need an interim method,
> now would be a good time to start discussion.
>
> Matt
>
> ----- Original Message -----
> From: "kernel neophyte" <neophyte.hacker001@gmail.com>
> To: vu@mellanox.com, "raju kurunkad" <raju.kurunkad@sandisk.com>, ceph-devel@vger.kernel.org
> Sent: Thursday, July 30, 2015 11:21:06 PM
> Subject: Cluster Network & Public Network w.r.t XIO ?
>
> Hi Vu, Raju,
>
> I am trying to bring up ceph cluster on a powerful dell server with
> two 40Gbe ROCEv2 NIC.
>
> I have assigned one as my cluster network (would prefer all osd
> communications happen on that) and have assigned one as my public n/w.
> this works fine for simple messenger case. (ofcourse no rdma)
>
> but when I try to bring this up on XIO, this gets very complicated, as
> in how do I specify two RDMA_LOCAL ? one for cluster n/w and other
> for public ? can choose XIO for client to osd communication and simple
> for cluster n/w ?
>
> any thoughts ?
>
> Thanks,
> Neo
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-07-31 17:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 3:21 Cluster Network & Public Network w.r.t XIO ? kernel neophyte
2015-07-31 14:49 ` Matt Benjamin
2015-07-31 16:20 ` kernel neophyte
2015-07-31 17:04 ` Matt Benjamin [this message]
2015-07-31 20:28 ` Marcus Watts
-- strict thread matches above, loose matches on Subject: below --
2015-08-01 0:12 Marcus Watts
2015-08-01 1:07 ` Sage Weil
2015-08-03 16:43 ` kernel neophyte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1211289190.918749.1438362252889.JavaMail.zimbra@redhat.com \
--to=mbenjamin@redhat.com \
--cc=ceph-devel@vger.kernel.org \
--cc=mwatts@redhat.com \
--cc=neophyte.hacker001@gmail.com \
--cc=raju.kurunkad@sandisk.com \
--cc=vu@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.