Re: [opnfv-tech-discuss] Models Weekly Meeting A

2016-12-19 Thread Vul, Alex
Hi,

Is the meeting happening today?

Thanks,

Alex


-Original Appointment-
From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Friday, November 4, 2016 6:16 AM
To: SULLIVAN, BRYAN L; 'opnfv-tech-discuss@lists.opnfv.org'
Cc: 'Dan Westerberg'; 'Tal Barenboim'; Vul, Alex; 'Henry Fourie'; 'Andrew 
Veitch'; 'a...@gigaspaces.com'; GUPTA, ALOK; 'Ola Liljedahl'; MORTON JR., AL; 
'Ulas Kozat'; 'David Suarez Fuentes'; 'Mario Torrecillas Rodriguez'; Ramia, 
Kannan Babu; 'Sen, Prodip'; 'Kuppuswamy, Prabu'; DRUTA, DAN; 'Gabor Halász'; 
Seiler, Glenn (Wind River); S, Deepak; 'Lawrence Lamers'; 
'ramki_krish...@dell.com'; Vandris, Steve; yaohelan
Subject: Models Weekly Meeting A
When: Monday, December 19, 2016 4:00 PM-5:00 PM (UTC) Coordinated Universal 
Time.
Where: https://global.gotomeeting.com/join/865421325


Updating this invite to be UTC-based as intended on the wiki, so we limit 
confusion during the seasonal change.

https://wiki.opnfv.org/display/models/Models+Meetings
IRC: #opnfv-models, e.g.  
https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23opnfv-models



___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] [Models] 2016-Nov-14 Models Project Meeting #18

2016-11-14 Thread Vul, Alex
All,

Are we meeting at 8 or 9 Pacific?

Thanks,

Alex


From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Monday, November 14, 2016 7:07 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [Models] 2016-Nov-14 Models Project Meeting #18

See https://wiki.opnfv.org/display/models/Models+Meetings

Agenda:

  *   Status of current work
  *   YANG Models discussion with Peter Lee
  *   Modeling approaches - collecting perspectives on
 *   What ETSI is recommending in their current drafts and why
 *   The role of YANG in service/application control
 *   How service and VNF modeling works in OpenCORD today
 *   If YANG was used at the service and VNF layers, how we can derive 
TOSCA NSDs/VNFDs etc as needed for processing by the cloud controller 
components e.g. Tacker?
  *   Planning for Danube
  *   Upcoming events
 *   Plugfest use cases (reference VNFs)
  *   Upcoming/Planned
 *   Cloudify/ARIA discussion

I will probably be hanging out at the auto shop so will do my best to run the 
meeting.

Thanks,
Bryan Sullivan | AT&T

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss


Re: [opnfv-tech-discuss] [mano-wg] [MANO] Meeting #11 agenda plus summary updates

2016-11-10 Thread Vul, Alex
Folks,

Can I assume that the VNF on-boarding proposal, outlined below, is a short-term 
one? For Open-0 R2 (Mercury) we are looking to do something a bit different in 
terms of VNF modeling and on-boarding. Ideally, we would want to think about 
some level of continuity between what exists today vs. what will exist tomorrow.

Prakash - I would have loved to participate in this discussion, but the MANO 
meeting time overlaps with the OPEN-O TSC call...

Cheers,

Alex Vul
Intel Corporation

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Wednesday, November 9, 2016 9:04 PM
To: Prakash Ramchandran ; 
mano...@lists.opnfv.org
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [mano-wg] [MANO] Meeting #11 agenda plus 
summary updates

Apologies for missing the call. Late night... late rise.
Good set of notes/questions. Some comments below.

Thanks,
Bryan Sullivan | AT&T

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Prakash 
Ramchandran
Sent: Wednesday, November 09, 2016 7:00 PM
To: mano...@lists.opnfv.org
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [mano-wg] [MANO] Meeting #11 agenda plus summary 
updates

Here is the summary of MANO meeting today Nov 9 and some common approach 
between Opera and Orchestra for on boarding, service invocation and  API 
versions / testing  - as summarized below.

I will be updating links etc provided by Giuseppe and Yingjun Li for same.
Any suggestions for next week call besides the ones agreed today, please feel 
free reply back for me or Bryan to include in next mano-wg or Models calls.

Subscribe for mano-wg if you want to keep upto date on mano-wg summary : 
https://lists.opnfv.org/mailman/listinfo/

Agenda of meeting November 9, 2016  14.00 UTC /7.00 PDT Meeting #11 and summary 
updates

  1.  What should we document for MANO best practice for OPEN-O and OpenBaton 
integration through Opera and Orchestra.
 *   What use case to start with - - Should vIMS be the first use case?
vIMS is agreed use case to document as first one for MANO integration
Besides Clearwater vIMS Blueprint in OPNFV,  Arthur from Canonical suggested 
using OpenIMS and JuJu can handle both.
[bryan] Fine with me, if you want to go for a complex VNF such as this. I am 
starting at the simpler end but your focus on this complex use case will drive 
the analysis faster, for sure. My issue with doing that is I simply don't 
understand all the detail in the Orange/Cloudify blueprint and have not done a 
mapping between it and the standard ETSI/OASIS TOSCA simple profile. My sense 
is that there are a substantial number of Cloudify extensions in there, 
probably also for JuJu. Identifying them and what's left as the standard "core" 
would be a great step forward.

 *   VNF On-Boarding - TOSCA Node Template  NFV (VNFD, VLD, 
VNNFGD, PNFD) - Onboarding
OpenBaton / Orchestra indicated that they like to see VNF Package to include 
VNFD along with image name and script to instantiate the VNF.
[bryan] how is the script invoked, e.g. a lifecycle hook for "started"?
So did Yingjun Li PTL Opera chimed and thus there is agreement on this from 
both projects. The issue of formats to use include CSAR & JSON and run times 
both Python and Java are being considered. Thus there will be attempt by both 
teams to define them along with VNFM's they plan to use like JujU and Tacker.
[bryan] What is meant by "run times" - the script runtime environment which the 
lifecycle event hook scripts execute in?

The VNF package, and data model / representations for NSD and VNFD, and how/why 
those vary across MANO projects

b1.   OpenBaton: JSON for 
VNFD, 
NSD; TOSCA for 
NSD
b2.   Open-O: ...Needs input from Opera team
 (OPNE-O : 
https://wiki.open-o.org/view/OPEN-O_Sun_Release_Notes#Release_Overview )
[bryan] I want to capture these differences/rationales on the Models wiki. I'll 
create a page for that.

 *   Service Invocation and Deletion - TOSCA Service  template = NFV NSD, 
How do we handle SO & RO for this?
This will follow NFVO flow to VNFM asking to allocate resource and if it does 
have not that capability then NFVO will reroute the request to VIM. On success 
of Resource reservation (Quota) etc. the NFVO will ask VNFM to instantiate the 
service for the deployment completion as first target. Life cycle management 
will follow that based on agreed hooks to be defined as common between the 
Opera , Orchestra, Juju and Tacker teams. A proposal will be