All of lore.kernel.org
 help / color / mirror / Atom feed
From: Willem Jan Withagen <wjw@digiware.nl>
To: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Multiple IPnr for OSDs in a multi-tenant environment
Date: Wed, 3 Feb 2016 13:21:07 +0100	[thread overview]
Message-ID: <56B1F0B3.5050907@digiware.nl> (raw)

Hi,

I was discussing multi-tenant sollutions with our engineers.
And one of the requirements we have there is:
	- tenants should not see one-another in the network
	- Seperate VLAN to customer/tenant

Now perhaps the first one would be possible by stringently applying
firewalls. But that is not really the most performant way since
everything has to go thru a firewall at 10Gb.

The second one would be relatively easy dependant on the chosen
construction of the infra.

I've seen some discussion on having multiple addresses on OSDs, but as
far as I can see/remember, and this is limitted to max 2 ipnrs.

For performance reasons perhaps everything can go over the same network,
but for separation and security, it might be that more is needed.

Who have others solved this in a multi-tenant environment?

Thanx,
--WjW

                 reply	other threads:[~2016-02-03 12:21 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=56B1F0B3.5050907@digiware.nl \
    --to=wjw@digiware.nl \
    --cc=ceph-devel@vger.kernel.org \
    /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.