All of lore.kernel.org
 help / color / mirror / Atom feed
From: Whit Blauvelt <whit-M6G8SDWvnhfby3iVrkZq2A@public.gmane.org>
To: "Eric W. Biederman" <ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: How do containers tie to multiple IP's on a NIC?
Date: Wed, 7 Jul 2010 09:22:06 -0400	[thread overview]
Message-ID: <20100707132206.GA16692@transpect.com> (raw)
In-Reply-To: <m1sk3vjvt1.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>

On Wed, Jul 07, 2010 at 05:55:22AM -0700, Eric W. Biederman wrote:

> paired veth devices are interesting because you can put one end of a
> logical tunnel in each network namespace.
> 
> macvlan devices are interesting because you can create assign multiple
> mac addresses to a nic and have a different network device for each
> mac address.

These two statements could be section headers in a valuable article - or
book chapter.

The problem with the standard VM concep: it takes the metaphor of separate
computers too literally. The potential for lessening the materials expense
and environmental cost of producing so much hardware and the electricity to
power it - is huge. Conversion to containers instead of VMs can be a major
economic win.

But only if the knowledge of how to do it becomes widespread. 

Whit

      parent reply	other threads:[~2010-07-07 13:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-04  3:40 How do containers tie to multiple IP's on a NIC? Whit Blauvelt
     [not found] ` <20100704034023.GA29753-M6G8SDWvnhfby3iVrkZq2A@public.gmane.org>
2010-07-04 16:51   ` Daniel Lezcano
     [not found]     ` <4C30BC16.9090802-GANU6spQydw@public.gmane.org>
2010-07-04 19:18       ` Whit Blauvelt
     [not found]         ` <20100704191841.GA31425-M6G8SDWvnhfby3iVrkZq2A@public.gmane.org>
2010-07-04 19:49           ` Daniel Lezcano
     [not found]             ` <4C30E5CB.1080902-GANU6spQydw@public.gmane.org>
2010-07-04 23:08               ` Whit Blauvelt
     [not found]                 ` <20100704230827.GA1066-M6G8SDWvnhfby3iVrkZq2A@public.gmane.org>
2010-07-05  9:50                   ` Pavel Labushev
     [not found]                     ` <4C31AAEE.5010201-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-07-05 14:07                       ` Whit Blauvelt
     [not found]                         ` <20100705140750.GA3113-M6G8SDWvnhfby3iVrkZq2A@public.gmane.org>
2010-07-05 21:13                           ` Daniel Lezcano
     [not found]                             ` <4C324AFE.8000801-GANU6spQydw@public.gmane.org>
2010-07-05 22:04                               ` Whit Blauvelt
2010-07-06 15:00                           ` Pavel Labushev
     [not found]                             ` <4C334523.2080503-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2010-07-06 15:04                               ` Pavel Labushev
2010-07-07 12:55                           ` Eric W. Biederman
     [not found]                             ` <m1sk3vjvt1.fsf-+imSwln9KH6u2/kzUuoCbdi2O/JbrIOy@public.gmane.org>
2010-07-07 13:22                               ` Whit Blauvelt [this message]

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=20100707132206.GA16692@transpect.com \
    --to=whit-m6g8sdwvnhfby3ivrkzq2a@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.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.