Re: [vnfpool] New revision of VNFPool Problem Statement posted
Zu Qiang <zu.qiang@ericsson.com> Mon, 21 April 2014 13:10 UTC
Return-Path: <zu.qiang@ericsson.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 0A43B1A0212 for <vnfpool@ietfa.amsl.com>; Mon, 21 Apr 2014 06:10:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.55
X-Spam-Level:
X-Spam-Status: No, score=0.55 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_CHARSET_FARAWAY=2.45, SPF_PASS=-0.001] 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 hU4oaggwG59F for <vnfpool@ietfa.amsl.com>; Mon, 21 Apr 2014 06:09:58 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id BAD281A0210 for <vnfpool@ietf.org>; Mon, 21 Apr 2014 06:09:57 -0700 (PDT)
X-AuditID: c618062d-f79f66d000001393-a3-5354ca2dbfe6
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id 44.FF.05011.D2AC4535; Mon, 21 Apr 2014 09:35:09 +0200 (CEST)
Received: from EUSAAMB107.ericsson.se ([147.117.188.124]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.03.0174.001; Mon, 21 Apr 2014 09:09:50 -0400
From: Zu Qiang <zu.qiang@ericsson.com>
To: Zongning <zongning@huawei.com>, "vnfpool@ietf.org" <vnfpool@ietf.org>
Thread-Topic: New revision of VNFPool Problem Statement posted
Thread-Index: Ac9UbATHM7NhTJ8NTjunJ2NkO54O2gFMTj5AABQFCQAA3Vi7sA==
Date: Mon, 21 Apr 2014 13:09:50 +0000
Message-ID: <A4288FE24C337B47BB634F1E76CBF2EC28B11551@eusaamb107.ericsson.se>
References: <B0D29E0424F2DE47A0B36779EC6667796610DCEE@nkgeml501-mbs.china.huawei.com> <A4288FE24C337B47BB634F1E76CBF2EC28B0E942@eusaamb107.ericsson.se> <B0D29E0424F2DE47A0B36779EC66677966113AEA@nkgeml501-mbs.china.huawei.com>
In-Reply-To: <B0D29E0424F2DE47A0B36779EC66677966113AEA@nkgeml501-mbs.china.huawei.com>
Accept-Language: en-CA, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.10]
Content-Type: multipart/alternative; boundary="_000_A4288FE24C337B47BB634F1E76CBF2EC28B11551eusaamb107erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrLLMWRmVeSWpSXmKPExsUyuXRPgq7uqZBggzlPdSxmXPrPYtF0+RSj A5NHy5G3rB5LlvxkCmCK4rJJSc3JLEst0rdL4Mpo+LeXtWDvf8aK5VMfsDcwfnnJ2MXIySEh YCJxftlbNghbTOLCvfVANheHkMBRRon765vAEkICyxklXvxJ6GLk4GATUJO4eJgRxBQR8JT4 uUQSpEJYwFbi1pplzCC2iICdxMP5T5ggbCeJX2uugNksAqoSWyf8ApvIK+Ar8ezvZBaIVU8Z JR71NLODJDgFwiSeTboOVsQoICux++x1sGZmAXGJW0/mM0HcKSCxZM95ZghbVOLl43+sELaS xKSl51gh6vMlNu1+xQSxTFDi5MwnLBMYRWYhGTULSdksJGUQcS2JeQ2/oWoUJaZ0P2SHsDUl rkw+BGVrSyxb+Jp5ASP7KkaO0uLUstx0I4NNjMD4OSbBpruDcc9Ly0OMAhyMSjy8U677Bgux JpYVV+YeYpTmYFES5/3y1jlISCA9sSQ1OzW1ILUovqg0J7X4ECMTB6dUA+PGFbYnJgrddzpT cV2u9+6q56mcSbduLlhw5Iu6ZA6nULvLLp7ks1f+fDx9dEfIa5GIjXZTJPnuLzco7Pd3MVlp +lqk+0I2R+2V1tm9Ih3cBkz92vr9y5WcuWu2fC5l4khdnee/N4515RSnlf4cCqu8Bc0PmcxY YpqetM6HjbXjpbX/XRXpi0osxRmJhlrMRcWJAAOlAOqAAgAA
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/ySsZc644M0Gm48v3kYWT02vGul8
Subject: Re: [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: Mon, 21 Apr 2014 13:10:01 -0000
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 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
- [vnfpool] New revision of VNFPool Problem Stateme… Zongning
- Re: [vnfpool] New revision of VNFPool Problem Sta… PEDRO ANDRES ARANDA GUTIERREZ
- [vnfpool] 答复: New revision of VNFPool Problem Sta… Zongning
- Re: [vnfpool] New revision of VNFPool Problem Sta… Zu Qiang
- [vnfpool] 答复: New revision of VNFPool Problem Sta… Zongning
- Re: [vnfpool] New revision of VNFPool Problem Sta… Zu Qiang
- [vnfpool] 答复: New revision of VNFPool Problem Sta… Zongning