[vnfpool] 答复: New revision of VNFPool Problem Statement posted

Zongning <zongning@huawei.com> Tue, 22 April 2014 01:38 UTC

Return-Path: <zongning@huawei.com>
X-Original-To: vnfpool@ietfa.amsl.com
Delivered-To: vnfpool@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8925D1A033C for <vnfpool@ietfa.amsl.com>; Mon, 21 Apr 2014 18:38:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.522
X-Spam-Level:
X-Spam-Status: No, score=-98.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.272, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
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 BVV-XWWOvKLW for <vnfpool@ietfa.amsl.com>; Mon, 21 Apr 2014 18:38:33 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 8202B1A00EC for <vnfpool@ietf.org>; Mon, 21 Apr 2014 18:38:32 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BDI62593; Tue, 22 Apr 2014 01:38:26 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 22 Apr 2014 02:37:49 +0100
Received: from nkgeml405-hub.china.huawei.com (10.98.56.36) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Tue, 22 Apr 2014 02:38:24 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.85]) by nkgeml405-hub.china.huawei.com ([10.98.56.36]) with mapi id 14.03.0158.001; Tue, 22 Apr 2014 09:38:20 +0800
From: Zongning <zongning@huawei.com>
To: Zu Qiang <zu.qiang@ericsson.com>, "vnfpool@ietf.org" <vnfpool@ietf.org>
Thread-Topic: New revision of VNFPool Problem Statement posted
Thread-Index: Ac9UbATHM7NhTJ8NTjunJ2NkO54O2gFMTj5AABQFCQAA3Vi7sAAZ0IJA
Date: Tue, 22 Apr 2014 01:38:19 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC66677966114597@nkgeml501-mbs.china.huawei.com>
References: <B0D29E0424F2DE47A0B36779EC6667796610DCEE@nkgeml501-mbs.china.huawei.com> <A4288FE24C337B47BB634F1E76CBF2EC28B0E942@eusaamb107.ericsson.se> <B0D29E0424F2DE47A0B36779EC66677966113AEA@nkgeml501-mbs.china.huawei.com> <A4288FE24C337B47BB634F1E76CBF2EC28B11551@eusaamb107.ericsson.se>
In-Reply-To: <A4288FE24C337B47BB634F1E76CBF2EC28B11551@eusaamb107.ericsson.se>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.22]
Content-Type: multipart/alternative; boundary="_000_B0D29E0424F2DE47A0B36779EC66677966114597nkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/lBWz9i4M5GWU_R7v_yjd7MxIVM0
Subject: [vnfpool] 答复: New revision of VNFPool Problem Statement posted
X-BeenThere: vnfpool@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for virtual network function resource pooling." <vnfpool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vnfpool>, <mailto:vnfpool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vnfpool/>
List-Post: <mailto:vnfpool@ietf.org>
List-Help: <mailto:vnfpool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vnfpool>, <mailto:vnfpool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Apr 2014 01:38:37 -0000

Hi, Qiang,

I¡¯d prefer to leave these questions to the co-authors of Use Case I-Ds. :)
I remember that we have a case of multi-tier service where data connections are directly between pool elements of different pools. Also in RSerPool, a pool element can announce its backup elements to the pool users via business card. The interaction between pool managers can be used for pooling information / status enquiry, and so on. Anyway, I think the details can be in the Use Case I-Ds.

Thanks.

-Ning

·¢¼þÈË: Zu Qiang [mailto:zu.qiang@ericsson.com]
·¢ËÍʱ¼ä: 2014Äê4ÔÂ21ÈÕ 21:10
ÊÕ¼þÈË: Zongning; vnfpool@ietf.org
Ö÷Ìâ: RE: New revision of VNFPool Problem Statement posted

Hello, Zongning
                Thanks for your response. Can you give a use case of ¡°the interactions between the Pool Managers of different pools and between the Pool Functions of different¡±? and a use case of ¡°VNF set¡±?

Have a nice day
Zu Qiang

From: Zongning [mailto:zongning@huawei.com]
Sent: Wednesday, April 16, 2014 11:45 PM
To: Zu Qiang; vnfpool@ietf.org<mailto:vnfpool@ietf.org>
Subject: ´ð¸´: New revision of VNFPool Problem Statement posted

Hi, Qiang,

Please see inline.


·¢¼þÈË: Zu Qiang [mailto:zu.qiang@ericsson.com]
·¢ËÍʱ¼ä: 2014Äê4ÔÂ17ÈÕ 2:13
ÊÕ¼þÈË: Zongning; vnfpool@ietf.org<mailto:vnfpool@ietf.org>
Ö÷Ìâ: RE: New revision of VNFPool Problem Statement posted

Hello, Zongning
                Thanks for updating the draft. I do see this version is much better than the previous version. I have a few clarification questions below:

-          First, there are some existing HA solutions. Can you tell me what is the extra functionalities provided by the VNF Pool? Or the VNF Pool is only another alternative solution? Or are we going to use the existing HA solutions as inputs only?

[Ning] For sure there are existing HA solutions. For example, the SAF is about Service Availability mechanisms. I agree that there are definitely many pieces of existing work can be investigated as the basis of VNF Pool, e.g. redundancy model, state sharing. I think the extra work needed in VNF Pool is to address specific requirements on VNF failover procedure, VNF state sharing, etc. This will depend on further use case and gap analysis.


-          Second, in the early version, you have the interactions between the Pool Managers of different pools and between the Pool Functions of different pools specified, which is removed in this version. Do you see that type of interactions are still needed? And why it is needed?

[Ning] Yes, I do think those interactions are still needed. But I prefer an VNF Pool architecture document to describe them, rather than Problem Statement draft.


-          3rd, the VNF set is a new concept. What is the linkage with the proposed VNF Pool architecture?

[Ning] VNF set is just a general set of all the VNF instances. In VNF Pool architecture, these VNF instances are actually grouped into multiple pools, based on the functions they provided. For example, a VNF set {vFW#1, vFW#2, vLB#1, vLB#2, vLB#3} can be organized as two VNF pools ¨C one pool is {vFW#1, vFW#2}, another is {vLB#1, vLB#2, vLB#3}. I will try to enhance this in the draft later on.


-          4th, RSerPool is referred by your draft. I assume that VNF Pool will not reused the RSerPool  unchanged. So which part of RSerPool can be reused by VNF Pool?

[Ning] Yes, we believe some mechanisms introduced by RSerPool can be extended and reused, such as PE registration, pool handle resolution and response. We have a RSerPool applicability and gap analysis draft dedicated on this perspective.


Thanks.
Have a nice day
Zu Qiang

From: vnfpool [mailto:vnfpool-bounces@ietf.org] On Behalf Of Zongning
Sent: Wednesday, April 09, 2014 11:22 PM
To: vnfpool@ietf.org<mailto:vnfpool@ietf.org>
Subject: [vnfpool] New revision of VNFPool Problem Statement posted

Hi, folks,

The new revision (-04) of VNFPool Problem Statement I-D is available on the below page.
https://datatracker.ietf.org/doc/draft-zong-vnfpool-problem-statement/

Here are the major changes:

1)       Clarify VNFPool architecture and intended scope.

1.         Add new section of VNF Pools before the section of Problem. This new section is mainly to outline our scope based on high level description of VNF Pools architecture.

2.         Add text to clarify that we are specifically concerned with reliability (e.g. redundancy model, state sharing) that is managed inside the VNF. We are only concerned with the whole VNF set (or forwarding graph) to the extent that it involves reliability impact on adjacent instances of different VNFs.

3.         We focus on reliability mechanisms based on VNF pool. Other VNF management aspects such as scaling, load balancing are out of scope.

2)       Update terminologies to define Service Control Entity, and delete Pool User as the pool will be internal to VNF only.

3)       Re-arrange the text in section of Problems.

4)       Update text of VNF instance performance degradation in section of Problems.

5)       Update text of Reliable Transport in section of Problems.

6)       Add text to explain why service availability is not in scope in section of Problems.

7)       Re-write the section describing the relationship of VNFPool and SFC.

8)       Add text of transfer of security states in section of Security Consideration.

We hope that the changes have addressed most of the comments, and reflected most of the suggestions during London BoF.

Please review this new revision. Your further comments and suggestions are highly appreciated!

Thanks.

-Ning