Re: [vnfpool] FW: New Version Notification for draft-zong-vnfpool-problem-statement-02.txt

["Susan Hares" <[e-mail]>]

Ning: 

I'm glad I understand the VNF Set.   You may want to include that example in
your draft. 

The question is what information is included in the automatic state
synchronization.

The more information you send in the automatic state synchronization, the
less you need to send in "5. "Complication of VNF placement".  

If you are designing interoperable systems, you will need to agree on what
data gets sent where.  This agreement can be done in data models.  

For example, I am VNF set 1 uses Data model 1.  Due to its sub-second
fail-over requirements for load-balancing, it send more information in the
automatic state synchronization so that it can exchange minimal information
for placement.  

VNF Set 2 could use Data model 2 - where it send very little in the state
synchronization, but has a fast query set to place the VNFs. 

This example of data models provides a "whole tree" of data information
unique to VNFs.  You could also make it a composite model where VNF set 1
supports subtree 1-2, and VNF set 2 supports only subtree 1. 

Does this make sense at the architecture level, or would you prefer more
specific information?

Sue 

-----Original Message-----
From: Zongning [mailto:[e-mail]] 
Sent: Tuesday, January 14, 2014 10:23 PM
To: Susan Hares; [e-mail]
Subject: RE: [vnfpool] FW: New Version Notification for
draft-zong-vnfpool-problem-statement-02.txt

Hi, Sue,

Thanks for your reply.

A VNF set have multiple instances, with each instance doing a specific
function. So, you have listed three valid examples of VNF set. :)

As described in the draft, there are multiple pools for multiple VNFs (LB,
Spam Filter, etc.). Currently we don't necessarily restrict to one-to-one
mapping of pool and VNF. For example, a single pool can manage either the
instances of a single VNF, or those of multiple VNFs.

I am not sure I understand your question about "continuum between the
service state synchronization and information transfer". Do you actually
want to scope the work around state synchronization? or just want to unify
the terms?

Thanks.

-Ning

> -----Original Message-----
> From: Susan Hares [mailto:[e-mail]]
> Sent: Wednesday, January 15, 2014 5:22 AM
> To: Zongning; [e-mail]
> Subject: RE: [vnfpool] FW: New Version Notification for 
> draft-zong-vnfpool-problem-statement-02.txt
> 
> Ning, Linda, Melinda, and Diego:
> 
> 
> This draft is very readable and addresses the issues we raised. The 
> clarification of terminology builds a clear workable set of 
> definitions for the Pool with its manager, users, and elements; and a set
of VNFs.
> 
> However, I find the definition of VNF Set to be a little fuzzy.  Is 
> the VNF set a particular instance doing a specific set of functions (load
balancing,
> spam filtering, etc.)?   How does the pool work with several instances?
> 
> VNF set 1
> (load-balance, spam filter, admin 1)
> 
> VNF set 2
> (load balance-spam filter (admin 2))
> 
> VNF set 3
> (spam filter)
> 
> Are these three valid sets?
> 
> The  following 6 problems are a good set of initial problems to work on.
> 
> 1. Cases of VNF failures
> 2. backup advertisement across VNF set.
> 3. State notification across VNF set
> 4. Service state synchronization
> 5. Complication of VNF placement
> 6. How get Reliable transport.
> 
> Beyond the VNF Set definition, there is a continuum between the 
> service state synchronization and information transfer for VNF placement?
> 
> Does anyone have experience with this continuum and like to talk about it?
> 
> Sue Hares
> 
> 
> -----Original Message-----
> From: vnfpool [mailto:[e-mail]] On Behalf Of Zongning
> Sent: Monday, January 13, 2014 8:25 PM
> To: [e-mail]
> Subject: [vnfpool] FW: New Version Notification for 
> draft-zong-vnfpool-problem-statement-02.txt
> 
> Hi, folks,
> 
> Happy new year!
> 
> We made a new revision of VNF Pool Problem Statement. Please see the 
> below abstract and links:
> 
> Abstract:
>    There is a trend to implement network services by using a group of
>    Virtualized Network Functions (VNFs) called a VNF set.  A VNF set can
>    offer benefits like flexible service provisioning.  A VNF set also
>    introduces additional points of failure, and therefore poses
>    additional challenges on reliability.
> 
>    This document overviews the problems related to the reliability of a
>    VNF set.  A VNF pooling architecture is also briefly introduced as
>    candidate solution to address the problems.
> 
> URL:
>
http://www.ietf.org/internet-drafts/draft-zong-vnfpool-problem-statement-02.
> txt
> Htmlized:
> http://tools.ietf.org/html/draft-zong-vnfpool-problem-statement-02
> 
> 
> Other related drafts including VNF Pool Use Cases, VNF Pooling 
> Architecture are under development and will be available soon in this
month...
> 
> Thanks.
> 
> -Ning
> 
> > -----Original Message-----
> > From: [e-mail] [mailto:[e-mail]]
> > Sent: Tuesday, January 14, 2014 9:18 AM
> > To: Zongning; Linda Dunbar; Melinda Shore; Linda Dunbar; Melinda 
> > Shore; Diego Lopez; Diego R. Lopez; Zongning
> > Subject: New Version Notification for 
> > draft-zong-vnfpool-problem-statement-02.txt
> >
> >
> > A new version of I-D, draft-zong-vnfpool-problem-statement-02.txt
> > has been successfully submitted by Ning Zong and posted to the IETF 
> > repository.
> >
> > Name:		draft-zong-vnfpool-problem-statement
> > Revision:	02
> > Title:		Virtualized Network Function (VNF) Pool Problem
> Statement
> > Document date:	2014-01-14
> > Group:		Individual Submission
> > Pages:		10
> > URL:
> >
>
http://www.ietf.org/internet-drafts/draft-zong-vnfpool-problem-statement-02.
> > txt
> > Status:
> > https://datatracker.ietf.org/doc/draft-zong-vnfpool-problem-statemen
> > t/
> > Htmlized:
> > http://tools.ietf.org/html/draft-zong-vnfpool-problem-statement-02
> > Diff:
> > http://www.ietf.org/rfcdiff?url2=draft-zong-vnfpool-problem-statemen
> > t-
> > 02
> >
> > Abstract:
> >    There is a trend to implement network services by using a group of
> >    Virtualized Network Functions (VNFs) called a VNF set.  A VNF set can
> >    offer benefits like flexible service provisioning.  A VNF set also
> >    introduces additional points of failure, and therefore poses
> >    additional challenges on reliability.
> >
> >    This document overviews the problems related to the reliability of a
> >    VNF set.  A VNF pooling architecture is also briefly introduced as
> >    candidate solution to address the problems.
> >
> >
> >
> >
> > Please note that it may take a couple of minutes from the time of 
> > submission until the htmlized version and diff are available at
> tools.ietf.org.
> >
> > The IETF Secretariat
> 
> _______________________________________________
> vnfpool mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/vnfpool