[Nfvrg] Using container based hypervisor in NFV
nikhil ap <niks3089@gmail.com> Thu, 16 March 2017 20:39 UTC
Return-Path: <niks3089@gmail.com>
X-Original-To: nfvrg@ietfa.amsl.com
Delivered-To: nfvrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 3B0DE129A7F
for <nfvrg@ietfa.amsl.com>; Thu, 16 Mar 2017 13:39:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25,
FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7,
SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id yyOuKwlnJHyT for <nfvrg@ietfa.amsl.com>;
Thu, 16 Mar 2017 13:39:30 -0700 (PDT)
Received: from mail-qk0-x235.google.com (mail-qk0-x235.google.com
[IPv6:2607:f8b0:400d:c09::235])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 318AE129A5B
for <nfvrg@irtf.org>; Thu, 16 Mar 2017 13:39:27 -0700 (PDT)
Received: by mail-qk0-x235.google.com with SMTP id p64so49893922qke.1
for <nfvrg@irtf.org>; Thu, 16 Mar 2017 13:39:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
h=mime-version:from:date:message-id:subject:to;
bh=n/kG9IdoalbNpbfanDB54BOeZostqhVMUL3wIQwPq0o=;
b=u4Hz3t051XAc0r2a9t3sKbGx+YQct2bmvGtzk2MR0rE4zCMpdYyrSNqGf6RHtRU+5o
I2ZQOERxYpv6zv8J8DmU8uISx8hxhImIn00PpKfSIQciFuGcXeB0myL7JL0fBJSea+43
vSs4mTGrm+Rv/2SacST7o1Jb4Ox16IW5sxpzlYAjmKpX6cuX/qfNF4PBDiDh835vCS/Q
YD+mZv1B3b3lDFq5n6jJlvBlMl9PRk38m7Oo6OSClCS4x8q71AJUd75ueYcQTBqHllm/
zjYPeIXivJQUAwCzn9jMVD8NfgcKMeVJprPx6gL1juD0v3O4o8IbzTwu/472yv4NsNgv
Pcfg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=n/kG9IdoalbNpbfanDB54BOeZostqhVMUL3wIQwPq0o=;
b=Tkc67TdrULIFBnozQoIGuU8KpoxDk3nTHjEv9LU7iv5687jBxA014CZ4XYXhkyea7z
7KRW4KhE4DwyfTy7+xKxE7W5LMCTr1kMPpzsLdBX2kWWDsu7uRsA85BeHFkVgaczqlbY
NCdlG+303rZgrmLWSbcWcgTH9k7BQ6vWmVqXqU2J6by7w28JhforK3wNhPqC02Wr5fQi
chrvHYSKAdj9R1mXSonMzlr6kCtaaYt5ouQv6H54GMEL1AxLU0AZjW75/axzOtljL+JC
a5pr5KRhkWDR5qjTA09gXo+Y3ICY/kQuYV8Tn8xwYMRWXOOy0uPTJ+iodmXgT+D5/zW5
zjlQ==
X-Gm-Message-State: AFeK/H2WQjuhbrgTEZbdJFKPdyKuObTVW7jmBKNLwxWB/FoQTEfoRmIPYxfh/8IetWQ6JhXq4yeiIEHaOeoNCg==
X-Received: by 10.55.157.146 with SMTP id g140mr9701826qke.30.1489696766184;
Thu, 16 Mar 2017 13:39:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.28.133 with HTTP; Thu, 16 Mar 2017 13:39:25 -0700 (PDT)
From: nikhil ap <niks3089@gmail.com>
Date: Fri, 17 Mar 2017 02:09:25 +0530
Message-ID: <CACPJs-CP0Q0tyEy4CO4jB339LwHfFhhJZhivrOiz0tVpR9kc+Q@mail.gmail.com>
To: nfvrg@irtf.org
Content-Type: multipart/alternative; boundary=001a114d56849255db054adf0e10
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfvrg/5usCO-lVlbsUAViz_FmQgAtmjHA>
Subject: [Nfvrg] Using container based hypervisor in NFV
X-BeenThere: nfvrg@irtf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Network Function Virtualization Research Group \(NFVRG\) discussion
list" <nfvrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nfvrg>,
<mailto:nfvrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfvrg/>
List-Post: <mailto:nfvrg@irtf.org>
List-Help: <mailto:nfvrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nfvrg>,
<mailto:nfvrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Mar 2017 20:39:32 -0000
Currently, the NFV architecture dictates that virtual functions run on top of full fledged hypervisor. However, recent advancements in container based hypervisor such as LXD looks promising. I think there will be a significant performance benefit in using Lxd over KVM although security is the obvious concern. Going forward, do we see container based hypervisor replacing KVM like hypervisors in deploying network virtual function? -- Regards, Nikhil
- [Nfvrg] Using container based hypervisor in NFV nikhil ap
- Re: [Nfvrg] Using container based hypervisor in N… GENG Liang
- Re: [Nfvrg] Using container based hypervisor in N… Roberto Riggio