xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Matt Wilson <msw@linux.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>,
	Zhigang Wang <zhigang.x.wang@oracle.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Matt Wilson <msw@amazon.com>
Subject: Re: Suggestion for merging xl save/restore/migrate/migrate-receive
Date: Wed, 2 Oct 2013 19:19:48 -0700	[thread overview]
Message-ID: <20131003021948.GA29049@u109add4315675089e695.ant.amazon.com> (raw)
In-Reply-To: <CAFLBxZbeDik_PG14Wkd1jq0Xq+_3cVo2XyEph68TCeaCPo2G7w@mail.gmail.com>

On Wed, Sep 25, 2013 at 11:06:29AM +0100, George Dunlap wrote:
> On Tue, Sep 24, 2013 at 5:46 PM, Konrad Rzeszutek Wilk
> <konrad.wilk@oracle.com> wrote:
> >> >>>* In order to migrate a VM without user interactive, we have to configure ssh
> >> >>>   keys for all Servers in a pool. Key management brings complexity.
> >> >>
> >> >>Surely your automated server deployment system can manage this ?
> >> >
> >> >Yes, we can.
> >> >
> >> >keys are states; we need to make sure they are always sync. Also after this,
> >> >all Servers in a pool can login to each other. I don't know whether it's
> >> >a security issue for our product.
> >> >
> >> >This is something we try to avoid at this time.
> >>
> >> ...so instead of allowing anyone on one of the hosts log in, you're
> >> going to allow anyone with access to the network to create a VM
> >> without any kind of authentication?
> >>
> >> From a security perspective, that doesn't really sound like an
> >> improvement...
> >>
> >
> > How did this work with 'xend' and its migration using SSL? Was it as
> > simple as this ?
> 
> I have no idea -- Matt, do you know / would you care to take a look
> and find out (since you have expressed a willingness to maintain
> xend)?

It seems that you would just configure a ssl key file and cert file in
xend-config.sxp

http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=0f26d15c

Zhigang: you wrote this code, correct?

--msw

  reply	other threads:[~2013-10-03  2:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-13 16:04 Suggestion for merging xl save/restore/migrate/migrate-receive Zhigang Wang
2013-09-16 10:04 ` George Dunlap
2013-09-16 15:51   ` Zhigang Wang
2013-09-16 16:05     ` George Dunlap
2013-09-16 16:07       ` George Dunlap
2013-09-16 16:20     ` Ian Jackson
2013-09-16 16:40       ` George Dunlap
2013-09-16 17:06         ` Ian Jackson
2013-09-16 17:21         ` Zhigang Wang
2013-09-16 17:41       ` Zhigang Wang
2013-09-16 20:42         ` Ian Campbell
2013-09-16 20:51           ` Zhigang Wang
2013-09-17  8:25         ` George Dunlap
2013-09-17  9:26           ` Ian Jackson
2013-09-17 10:07             ` George Dunlap
2013-09-17 13:44             ` Zhigang Wang
2013-09-24 16:46           ` Konrad Rzeszutek Wilk
2013-09-25 10:06             ` George Dunlap
2013-10-03  2:19               ` Matt Wilson [this message]
2013-10-03 13:34                 ` Zhigang Wang
2013-09-17 10:28     ` George Dunlap
2013-09-17 10:45       ` Processed: " xen

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=20131003021948.GA29049@u109add4315675089e695.ant.amazon.com \
    --to=msw@linux.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=msw@amazon.com \
    --cc=xen-devel@lists.xen.org \
    --cc=zhigang.x.wang@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).