Re: [opnfv-tech-discuss] TSC Schedule thought

[SULLIVAN, BRYAN L]

To address the quorum issues related to votes, we could:
- take votes out of the TSC calls altogether, and run them as doodle polls etc 
with notice at the TSC calls
- allow the present TSC members to vote on the call they attend, and summarize 
the results after both TSC calls in a week

These will slow things down a bit, but not a lot.

Personally, I am open to any secondary rotation (adding to the existing call). 
One TSC call that I can attend per week is good enough.

I assume  that we need to also rotate the release planning meetings if not 
already.

Thanks,
Bryan Sullivan | AT&T

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Dave Neary
Sent: Wednesday, July 20, 2016 3:05 PM
To: Raymond Paik; Dan Radez
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] TSC Schedule thought

Hi,

On 07/19/2016 08:54 PM, Raymond Paik wrote:
> On the GTM chat, Larry shared this
> link 
> http://www.timeanddate.com/worldclock/meetingtime.html?month=8&day=1&y
> ear=2016&p1=37&p2=33&p3=224&iv=0 that shows times in 
> UTC/Berlin/Beijing/San Francisco...
> 
> So the 2pm Pacific Time I suggested as an alternate slot is actually 
> 5am in China (not 6am as I thought).  Julien noted that he preferred 
> 6am over 10pm, but 5am may be another story (Julien plus others in 
> China, let us know your thoughts).
> 
> To make this exercise more interesting, not every country observes 
> Summer Time/Daylight Savings time, so come November, we'll be looking 
> at 
> http://www.timeanddate.com/worldclock/meetingtime.html?month=12&day=1&;
> year=2016&p1=37&p2=33&p3=224&iv=0
> 
> When we return to "Standard" times in Europe/N. America 2pm Pacific 
> Time is actually 6am in China & 7am in Japan + Korea which maybe more 
> reasonable for people in Asia.
> 
> If you have other ideas/suggestions, please chime in :-)

I fear that whatever we do will cause issues.

* It's clearly unfair to leave things as they are - we are forcing part of the 
TSC to attend at unsociable hours
* If we move to rotating meetings, we may struggle to attain quorum. For many, 
it is difficult to attend at certain times (family dinner time, night time, 
etc), we will lose some attendees, and they will not always be the same people
* Decisions made by the TSC if people are unable to attend may be called into 
question - do we have a mandate to decide something important (say, a scope 
expansion, a request for resources to the board, or a new project approval) if 
30-40% of TSC members are absent?
* Abandoning meetings (the radical alternative) will likely not be successful 
given the dynamic of the group - we are meeting-driven, agenda-driven, and I 
fear that "take it to the list" will not result in us getting very much done

Adding the other cities where TSC members live, we have:
http://www.timeanddate.com/worldclock/meetingtime.html?iso=20160801&p1=37&p2=33&p3=224&p4=43&p5=101&p6=248

The best time is what we have currently. The best alternative is 11pm Eastern 
US time/5am Berlin time or midnight Eastern/6am Berlin. So the least painful of 
the proposals would be to alternate meetings between 14h UTC and 04h UTC - but 
you would probably lose several East Coasters and Central Europeans at that 
time.

Thanks,
Dave.

--
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338 
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Who is using the Go To Meetings line? This ARMband time slot

[SULLIVAN, BRYAN L]

Hi Bob,

Dovetail is apparently conflicting with your timeslot now.

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Bob Monkman
Sent: Friday, July 22, 2016 7:10 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Who is using the Go To Meetings line? This 
ARMband time slot

Sorry for the broadcast message but someone keep killing our armband meeting. 
7am PDT is our time slot for the last year.


Robert (Bob) Monkman
Enterprise Segment Marketing Manager
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490

IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Do all OPNFV installers create an external net/subnet?

[SULLIVAN, BRYAN L]

Hi all,

This question came up as I was debugging why in my NUC lab environment.  I was 
not able to ping or SSH to VMs. Turns out there was an external network and 
subnet that had been created by JOID as part of the install process (see 
https://git.opnfv.org/cgit/joid/plain/ci/openstack.sh). Creating a second 
external net/subnet as I do in my tests e.g. the smoke test 
(https://git.opnfv.org/cgit/copper/plain/tests/adhoc/smoke01.sh), prevents ping 
and SSH from working for some reason. So I had to change that script to find an 
existing external net/subnet if any, first.

This brings up the question: like JOID, do all other OPNFV installers create an 
external network as part of the install process?

If not, is there a recommended way for tests to determine what the parameters 
(e.g. gateway, allocation pools) of an external net/subnet should be?

BTW, the smoke01 script I developed goes beyond vPing, with tests of external 
network connectivity as well. Is that something we should add to vPing (I 
didn't see it in vPing)?

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] Do all OPNFV installers create an external net/subnet?

[SULLIVAN, BRYAN L]

Jose,

Thanks for confirming. I think the bash function I'm using is good enough for 
now. I do plan to migrate my tests to python once I get the time to learn it.

The test script I called out below is just what I use to verify basic 
functionality of the deploy, similar to vPing as you mention. I don't expect it 
to be used in Functest. But it's a single self-contained script and easier for 
me to use than vPing. I developed it as an exercise to learn the OpenStack APIs 
and how to get the results using bash etc.

Thanks,
Bryan Sullivan | AT&T

From: Jose Lausuch [mailto:jose.laus...@ericsson.com]
Sent: Wednesday, July 27, 2016 12:48 AM
To: SULLIVAN, BRYAN L; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] Do all OPNFV installers create an external 
net/subnet?

Hi Bryan,

Yes, the 4 installers deploy an external network by default, we requested that 
already in Arno for Functest. We have a "utils" function that returns you the 
name of the external network, but it is written in Python and we can use it and 
pass the network name as a parameter when calling your Shell script. Is that ok?

Regarding our vPing tests, we do test the external connectivity as well making 
use of floating ips and ssh to the instances. Check this out for more info:
http://artifacts.opnfv.org/functest/docs/userguide/index.html#vping-ssh

Regards,
Jose


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Wednesday, July 27, 2016 5:25 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] Do all OPNFV installers create an external 
net/subnet?

Hi all,

This question came up as I was debugging why in my NUC lab environment.  I was 
not able to ping or SSH to VMs. Turns out there was an external network and 
subnet that had been created by JOID as part of the install process (see 
https://git.opnfv.org/cgit/joid/plain/ci/openstack.sh). Creating a second 
external net/subnet as I do in my tests e.g. the smoke test 
(https://git.opnfv.org/cgit/copper/plain/tests/adhoc/smoke01.sh), prevents ping 
and SSH from working for some reason. So I had to change that script to find an 
existing external net/subnet if any, first.

This brings up the question: like JOID, do all other OPNFV installers create an 
external network as part of the install process?

If not, is there a recommended way for tests to determine what the parameters 
(e.g. gateway, allocation pools) of an external net/subnet should be?

BTW, the smoke01 script I developed goes beyond vPing, with tests of external 
network connectivity as well. Is that something we should add to vPing (I 
didn't see it in vPing)?

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

[opnfv-tech-discuss] OPNFV platform API inventory and CI test coverage

[SULLIVAN, BRYAN L]

Hi all,

I was wondering if there is any activity or capability in OPNFV yet to:

-  Build a living catalog (i.e. automatically maintained) of APIs 
exposed by the OPNFV platform components

-  Target CI tests to those APIs (I assume for OpenStack, Tempest tests 
cover some of this)

-  Track the test coverage of APIs per the catalog

Any info/pointers are appreciated.

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

[opnfv-tech-discuss] [Models] Models Project Meeting #11

[SULLIVAN, BRYAN L]

Today in the Models meeting we agreed to merge the Models meeting with the MANO 
WG meeting going forward.  This will help reduce meeting overload that we are 
all experiencing.
The current Models meeting times and bridge can be used for the MANO WG meeting 
as well. Prakash is still finalizing that - stay tuned.
In the same discussion, I indicated that for the VES project this would be a 
similarly good approach to avoiding meeting overload. So both Models and VES 
updates and discussions will occur on the MANO WG calls.

Models project related meeting notes will still be posted to 
https://wiki.opnfv.org/display/models/Models+Meetings.

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] [Dovetail] Aug 5 Dovetail meeting notes

[SULLIVAN, BRYAN L]

Hi all,

I missed the last Dovetail meeting but from what I heard about some of the 
discussion, I'd like to seek clarification on some things that might have been 
expressed in the meeting, e.g. that implementations which will go thru C&C may 
not be expected to be compatible with existing OPNFV test suites, or at least 
that not all of the OPNFV test suites, e.g. FuncTest and Yardstick, would be 
expected to be tested on an certified implementations.

First I'd like to verify that such opinions were expressed (e.g. per Bin's 
comment that as a result "Dovetail testing and OPNFV tests are different"), and 
have them further explained if possible.

Second, given that the notes do capture the discussion and concerns correctly, 
here are some thoughts about that:

1)  The C&C committee is responsible for setting the "what is expected" out 
of a certification, within some flexibility within Doevtail as to what/how/when 
that can be delivered.

2)  Overall, it's expected that any implementation is compatible with the 
OPNFV test suites as test frameworks. The degree of compatibility with specific 
test may be limited e.g. if the target hardware/software function focused on by 
the tests is not supported by the implementation (e.g. an implementation that 
supports only a specific SDNC), but the significance of such N/As needs to be 
carefully considered by the C&C committee or Dovetail.

Overall we need to ensure that any aspect of certification can work equally 
(same end result) on an OPNFV-based implementation (meaning a collection of the 
core components as released in some OPNFV release, or even with slight 
variations e.g. different versions of the components), or another 
implementation. We should not leave tests out of the Dovetail scope just 
because they will "not work" on some implementations. There may be good reasons 
for them not to work (the N/As), but if those reasons are simply based upon the 
test design, the platform vendor should provide a compatible version of the 
tests based upon the OPNFV tests, so that we can still certify the platform 
functionally. Examples of this may be:

-  FuncTest

o   vIMS (Clearwater IMS) is based upon Orange's implementation of the Cloudify 
blueprint, using Cloudify as a VNFM. In the process, the Cloudify Manager is 
installed as a VM under OpenStack, and then executes the vIMS blueprint. I see 
no reason that this should not work essentially the same in any other 
environment. AFAIK, the only possible differences, which would need to be 
addressed by adding options to the existing FuncTest code for this, are that 
e.g. a different approach to kicking off the FuncTest framework is needed due 
to differences in Jumphost OS or configuration. But OPNFV should not be 
responsible for accommodating platform implementations that vary in this way; 
the vendor should step up and implement the support so their product can be 
validated.

o   The rest of FuncTest is pretty generic and I see no reason why it should 
not be supportable.

-  Yardstick

o   As with FuncTest, the framework under which Yardstick operates may need 
some tweaks for compatibility with the vendor implementation. These tweaks need 
to be contributed to OPNFV by the vendor.

o   The C&C program may not initially include performance benchmarking, but any 
implementation should have demonstrated compatibility with the Yardstick test 
suite.

-  Other tests that we develop for Dovetail may go beyond FuncTest and 
Yardstick, to focus on more complex use cases or specific technical 
capabilities. In principle I would expect that these would migrate into 
FuncTest and Yardstick however, over time, because if they are important they 
need to be part of the base test system. These might include tests for 
reference VNFs that we collect and run as blueprints under various VNFMs, e.g. 
thru the Models project. In those cases, if a vendor does not support one of 
the VNFMs for some reason (as with vIMS/Cloudily), then they need to contribute 
the support using their VNFM to OPNFV.

-  The rest of the Dovetail tests will be based upon existing upstream 
test suites including certification suites such as RefStack. We need to be 
proactively reaching out to these upstream teams, e.g. per 
https://etherpad.openstack.org/p/interop-challenge-meeting-2016-08-03.


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: Friday, August 05, 2016 8:08 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [Dovetail] Aug 5 Dovetail meeting notes

Here is today's OPNFV Dovetail meeting notes based on Gotomeeting and  
#opnfv-dovetail channels ...
Agenda:
1)start point(L3VPN, SFC and IPV6)
2)test cases structures
3) additional basic testcases( for SDN controller and NFVI...)
https://wiki.opnfv.org/pages/viewpage.action?pageId=6827269
4)other i

Re: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large TSC elections

[SULLIVAN, BRYAN L]

Here’s a nomination:
· Nominee: Bin Hu, bh5...@att.com
· Employer: AT&T
· Bin has demonstrated his dedication and leadership to the maturity 
and success of the community. He has been organizing and leading the weekly 
technical discussion of the community to review project proposals. Being the 
PTL of the IPv6 project, Bin has been leading the group to collaborate with 
sister groups and upstream communities and deliver the results. Bin is also 
instrumental in incubating NetReady/Gluon project and leading Gluon work in 
OpenStack as well. Bin’s leadership, collaboration effort within community and 
with upstreams, and his detailed and practical working knowledge of OPNFV will 
add great value to TSC.

Thanks,
Bryan Sullivan | AT&T

From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of Raymond Paik 
mailto:rp...@linuxfoundation.org>>
Date: Monday 8 August 2016 at 08:21
To: TSC OPNFV mailto:opnfv-...@lists.opnfv.org>>, 
TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] Opening nominations for the Committers-at-Large 
TSC elections

OPNFV Community:

Based on feedback last week, the list of committers have been updated and you 
can find the committers list at 
https://wiki.opnfv.org/display/DEV/OPNFV+Committers+List.

Now, I'd like to open the nomination period for the Committers-at-Large TSC 
elections.  As noted in the elections wiki page 
(https://wiki.opnfv.org/display/DEV/Community+Election+Procedure#CommunityElectionProcedure-CommunityTSCmemberelection(proposalpendingapproval),
 nominations can be either self-nominations or anyone can nominate other 
committers. If a committer is nominated by others, the nominee must accept the 
nomination for it to be valid.

For self-nominations, I created a wiki page with a suggested template at 
https://wiki.opnfv.org/display/DEV/2016+Commiters-at-Large+TSC+Election+Self-Nominations.
  If you are interested in nominating yourself, please add your nomination 
statements directly on the wiki page.

If you'd like to nominate others, please send your nominations to opnfv-tsc & 
opnfv-tech-discuss mailing lists so that your nominations can be accepted (or 
declined) by the nominees on the mailing lists.

I will close the nominations at 5pm Pacific Time on August 12th (Friday).  
Please let me know if you have any questions.

Thanks,

Ray

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

Re: [opnfv-tech-discuss] 答复: [dovetail]suggest to use the #opnfv-dovetail for the dovetail meeting

[SULLIVAN, BRYAN L]

I support fewer distinct channels also. If it turns out we have an adhoc 
meeting conflict, we can setup #opnfv-alt1/2/3 ala OpenStack, ping others and 
move conversations there as needed. Just like CB radio.

On Aug 10, 2016, at 8:54 AM, Dave Neary  wrote:

Hi,

I agree with Chris.

There is also a very well suited channel for general discussion, not
limited to Dovetail, #opnfv - I propose we use that if there are topics
that need real-time interaction. Also, please remember the old Apache
dictum: "If it didn't happen on the mailing list, it didn't happen".
Nowadays, we would probably extend that to "if it didn't happen on the
mailing list, on Jira, on Gerrit, or in the wiki, it didn't happen, but
you get the point - it's important that real-time discussions are
brought back to an asynchronous, archived forum.

Thanks,
Dave.
> On 08/10/2016 08:25 AM, Christopher Price wrote:
> Ok, interesting no-one mentioned that on the last meeting. 
> 
> 
> 
> Can we discuss it as a group on Friday before changing what was agreed 5
> days ago? 
> 
> (Note: releng did create it’s own channel but no longer uses it, rather
> they work on community channels as separate channels are at times not
> very useful for collaborative activities.)
> 
> 
> 
> / Chris
> 
> 
> 
> 
> 
> *From: *Tianhongbo 
> *Date: *Wednesday 10 August 2016 at 13:53
> *To: *Christopher Price , Christopher Price
> , Dave Neary ,
> TECH-DISCUSS OPNFV 
> *Subject: *答复: [opnfv-tech-discuss] [dovetail]suggest to use the
> #opnfv-dovetail for the dovetail meeting
> 
> 
> 
> Hi Chris:
> 
> 
> 
> Yes, we agreed to use the opnfv-meeting.
> 
> But now, there is a requirements that all people like to talk in the IRC
> all time for dovetail like done in the releng or yardstick.
> 
> If we use opnfv-meeting, we cannot do that.
> 
> That is the problem.
> 
> 
> 
> Best Regards
> 
> 
> 
> hongbo
> 
> 
> 
> *发件人**:*Christopher Price [mailto:chrispric...@gmail.com]
> *发送时间:* 2016年8月10日 18:34
> *收件人:* Tianhongbo; Christopher Price; Dave Neary; TECH-DISCUSS OPNFV
> *主题:* Re: [opnfv-tech-discuss] [dovetail]suggest to use the
> #opnfv-dovetail for the dovetail meeting
> 
> 
> 
> Hi Hongbo,
> 
> 
> 
> If I recall, there were comments on the last meeting that people
> preferred to use opnfv-meeting.  I had not heard anyone speak to the
> desire to create another IRC channel for this meeting series.
> 
> 
> 
> My only thought is that it seems unnecessary to create another channel,
> our committers indicated a desire to stay on opnfv-meeting and it is
> unclear why this has come up again.
> 
> 
> 
> / Chris
> 
> 
> 
> *From: * > on behalf of
> Tianhongbo  >
> *Date: *Wednesday 10 August 2016 at 03:02
> *To: *Christopher Price  >, Dave Neary  >, TECH-DISCUSS OPNFV
>  >
> *Subject: *[opnfv-tech-discuss] [dovetail]suggest to use the
> #opnfv-dovetail for the dovetail meeting
> 
> 
> 
> Hi all:
> 
> 
> 
> With the development of dovetail, there are more people involved in.
> 
> we used the opnfv-meeting before.
> 
> In order to help people to discuss whenever and wherever, I suggest to
> use the #opnfv-dovetail for dovetail discussion.
> 
> If we have dovetail own IRC, it can avoid the conflict.
> 
> We tested it, it works.
> 
> 
> 
> Any comments?
> 
> 
> 
> Best Regards
> 
> 
> 
> hongbo
> 
> ___ opnfv-tech-discuss
> mailing list opnfv-tech-discuss@lists.opnfv.org
> 
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

-- 
Dave Neary - NFV/SDN Community Strategy
Open Source and Standards, Red Hat - http://community.redhat.com
Ph: +1-978-399-2182 / Cell: +1-978-799-3338
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Dovetail] Aug 5 Dovetail meeting notes

[SULLIVAN, BRYAN L]

I would say rather that the Dovetail system needs to be aware of what system 
and components are under test, and select as fully as possible the compatible 
tests from the Functest and Yardstick suites. 

We should not narrow down the scope to just what will run across all 
implementations, even proprietary (e.g. those implementations not supporting 
the open source project VIMs with their published interfaces). There would be 
little in common, and we would be left trying to certify that something meets 
the "spirit" of an NFV/SDN system with any specific interoperability 
expectations. I don't think that is what the C&C program is about.

On Aug 8, 2016, at 12:16 PM, Dave Neary  wrote:

Hi Bryan,

> On 08/08/2016 10:45 AM, SULLIVAN, BRYAN L wrote:
> I missed the last Dovetail meeting but from what I heard about some of
> the discussion, I�d like to seek clarification on some things that might
> have been expressed in the meeting, e.g. that implementations which will
> go thru C&C may not be expected to be compatible with existing OPNFV
> test suites, or at least that not all of the OPNFV test suites, e.g.
> FuncTest and Yardstick, would be expected to be tested on an certified
> implementations.
> 
> First I�d like to verify that such opinions were expressed (e.g. per
> Bin�s comment that as a result �Dovetail testing and OPNFV tests are
> different�), and have them further explained if possible.

Yes, I expressed the view that Functest and Yardstick, as testing
projects, were designed to stretch the platform - that we will
periodically add failing functest tests to validate that the tests pass
after we make a change to the upstream projects under test. They will
also include tests which are targeting specific scenarios, and are known
to fail (and thus will not be run) on other scenarios.

In that sense, the Dovetail test suite should be a subset of FuncTest
and Yardstick which pass on multiple scenarios and installers, and can
be run unchanged on stacks with (for example) a proprietary SDN controller.

> Second , given that the notes do capture the discussion and concerns
> correctly, here are some thoughts about that:
> 
> 1)  The C&C committee is responsible for setting the �what is
> expected� out of a certification, within some flexibility within
> Doevtail as to what/how/when that can be delivered.
> 
> 2)  Overall, it�s expected that any implementation is compatible
> with the OPNFV test suites as test frameworks. The degree of
> compatibility with specific test may be limited e.g. if the target
> hardware/software function focused on by the tests is not supported by
> the implementation (e.g. an implementation that supports only a specific
> SDNC), but the significance of such N/As needs to be carefully
> considered by the C&C committee or Dovetail.

This is the context for the "subset of..." I mentioned above.

Chris started a page in the wiki a couple of weeks ago to describe the
criteria for a test case in the Dovetail test framework, I and others
added to it: https://wiki.opnfv.org/pages/viewpage.action?pageId=6827269

Thanks,
Dave.

> Overall we need to ensure that any aspect of certification can work
> equally (same end result) on an OPNFV-based implementation (meaning a
> collection of the core components as released in some OPNFV release, or
> even with slight variations e.g. different versions of the components),
> or another implementation. We should not leave tests out of the Dovetail
> scope just because they will �not work� on some implementations. There
> may be good reasons for them not to work (the N/As), but if those
> reasons are simply based upon the test design, the platform vendor
> should provide a compatible version of the tests based upon the OPNFV
> tests, so that we can still certify the platform functionally. Examples
> of this may be:
> 
> -  FuncTest
> 
> o   vIMS (Clearwater IMS) is based upon Orange�s implementation of the
> Cloudify blueprint, using Cloudify as a VNFM. In the process, the
> Cloudify Manager is installed as a VM under OpenStack, and then executes
> the vIMS blueprint. I see no reason that this should not work
> essentially the same in any other environment. AFAIK, the only possible
> differences, which would need to be addressed by adding options to the
> existing FuncTest code for this, are that e.g. a different approach to
> kicking off the FuncTest framework is needed due to differences in
> Jumphost OS or configuration. But OPNFV should not be responsible for
> accommodating platform implementations that vary in this way; the vendor
> should step up and implement the support so their product can be validated.
> 
> o   The rest of FuncTest is pretty generic and I see no reason why it
> should not be suppor

Re: [opnfv-tech-discuss] [Dovetail] Aug 5 Dovetail meeting notes

[SULLIVAN, BRYAN L]

Chris,

I either don't understand or don't agree to the statement that the Functest 
isn't designed to be generic, at least as a framework. Certainly where we 
leverage upstream test suites e.g. Tempest/rally they are contextual, but so 
far we have no other cloud VIM in OPNFV except for OpenStack. Some tests might 
be specific to some SDNCs, but again thats just because we are using the 
upstream tests. Functest as a framework though *is* IMO a generic framework, 
and we should leverage it thru Dovetail for testing against expectations for 
the system components under test.

We do not yet AFAICT a concept of a high-level intent framework through which 
we could drive any implementation/VIM, and I don't expect any such framework 
soon. Certainly it's one of the goals of the broader communities e.g. ONF and 
the Multi-SDO Information Modeling activity, but will take a while to 
materialize. So I don't see how we can expect to use a truly generic test suite 
for any comprehensive purpose, anytime soon.

On Aug 8, 2016, at 7:58 AM, Christopher Price 
mailto:chrispric...@gmail.com>> wrote:

Hi Bryan,

There was a fair amount of discussion around what Dovetail is testing.
One item I was trying to articulate is that the purpose of the Dovetail suite 
is to validate the compliance of a platform to the behaviors and interfaces 
targeted for compliance validation in OPNFV.  This differs from the purpose of 
Functest and Yardstick which is to validate as thoroughly as possible the 
design of the OPNFV platform.

I have one small concern with your comment: ”The rest of FuncTest is pretty 
generic“
Functest is anything but generic as far as a platform for generic platform 
feature validation is concerned, functest test cases derive mostly from the 
upstream community and do not, by design, provide neutral generic test cases 
for a platform.  This is not a bad thing, it simply does not lend itself to 
creating test cases that should be able to be run over any platform composition.

Our Dovetail suite needs to work even when someone swaps out OpenStack for 
another VIM, or a completely different SDN controller for instance.

/ Chris

From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of "SULLIVAN, BRYAN L" mailto:bs3...@att.com>>
Date: Monday 8 August 2016 at 16:45
To: Prakash Ramchandran 
mailto:prakash.ramchand...@huawei.com>>, 
TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [Dovetail] Aug 5 Dovetail meeting notes

Hi all,

I missed the last Dovetail meeting but from what I heard about some of the 
discussion, I’d like to seek clarification on some things that might have been 
expressed in the meeting, e.g. that implementations which will go thru C&C may 
not be expected to be compatible with existing OPNFV test suites, or at least 
that not all of the OPNFV test suites, e.g. FuncTest and Yardstick, would be 
expected to be tested on an certified implementations.

First I’d like to verify that such opinions were expressed (e.g. per Bin’s 
comment that as a result “Dovetail testing and OPNFV tests are different”), and 
have them further explained if possible.

Second, given that the notes do capture the discussion and concerns correctly, 
here are some thoughts about that:

1)   The C&C committee is responsible for setting the “what is expected” 
out of a certification, within some flexibility within Doevtail as to 
what/how/when that can be delivered.

2)   Overall, it’s expected that any implementation is compatible with the 
OPNFV test suites as test frameworks. The degree of compatibility with specific 
test may be limited e.g. if the target hardware/software function focused on by 
the tests is not supported by the implementation (e.g. an implementation that 
supports only a specific SDNC), but the significance of such N/As needs to be 
carefully considered by the C&C committee or Dovetail.

Overall we need to ensure that any aspect of certification can work equally 
(same end result) on an OPNFV-based implementation (meaning a collection of the 
core components as released in some OPNFV release, or even with slight 
variations e.g. different versions of the components), or another 
implementation. We should not leave tests out of the Dovetail scope just 
because they will “not work” on some implementations. There may be good reasons 
for them not to work (the N/As), but if those reasons are simply based upon the 
test design, the platform vendor should provide a compatible version of the 
tests based upon the OPNFV tests, so that we can still certify the platform 
functionally. Examples of this may be:

-  FuncTest

ovIMS (Clearwater IMS) is based upon Orange’s implementation of the 
Cloudify blueprint, using Cloudify as a VNFM. In the process, the Cloudify 
Manager is installed as a VM under OpenStack, and then executes the vIMS 
bluep

Re: [opnfv-tech-discuss] [Orchestra] new project proposal

[SULLIVAN, BRYAN L]

How about Bat-Mano?

On Aug 5, 2016, at 8:52 AM, Bob Monkman 
mailto:bob.monk...@arm.com>> wrote:

Guiseppe, Chris,
Good comments and I like fun names. I see both sides on this 
one. I thought it was worth a look, since Yuan brought it up and I could see 
how it could _possibly_ be misconstrued. As was said, if a critical mass were 
to think it an issue, the Open Baton team- else I do not feel strong enough to 
push on it. Good luck with the project Giuseppe and team.
Regards,
Bob

Robert (Bob) Monkman
Enterprise Segment Marketing Manager
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490

From: Carella, Giuseppe [mailto:giuseppe.care...@fokus.fraunhofer.de]
Sent: Friday, August 05, 2016 4:32 PM
To: Christopher Price
Cc: Bob Monkman; Liu Yuan; BIN; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Orchestra] new project proposal

Hi all,

indeed that was our intention, to have a funny name…considering our open 
“baton" we thought it would make sense to build an orchestra using the OPNFV 
instruments (projects) :-)

of course, I agree that if there are major concerns we’ll have to reconsider it.

Cheers,
Giuseppe

Join us at the IEEE 5G Week in November in Berlin (http://www.berlin5gweek.org/)

On 05 Aug 2016, at 17:26, Christopher Price 
mailto:chrispric...@gmail.com>> wrote:

Hi Bob,

I tend to agree with you, but personally don’t put that much stock into a name.
In the case of OPNFV-MANO the name was indicative of an area in OPNFV so we did 
ask that the team consider revising the name.  If a project was to propose the 
name OPNFV “orchestration” I would similarly ask them to reconsider.

Opera and Orchestra I thank are really fun names that refer to the MANO space 
and activities is service orchestration, I had thought it was an entertaining 
theme and to be honest was wondering if the OSM group might choose something 
similarly theatrical if/when they were to participate.

I guess I had not considered this name to be an issue, but if there are 
concerns with it let’s discuss it openly every opinion counts here.

/ Chris


From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of Bob Monkman mailto:bob.monk...@arm.com>>
Date: Friday 5 August 2016 at 16:59
To: Liu Yuan mailto:liuyuan_c...@hotmail.com>>, BIN 
mailto:bh5...@att.com>>, "Carella, Giuseppe" 
mailto:giuseppe.care...@fokus.fraunhofer.de>>
Cc: TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] [Orchestra] new project proposal

Yuan,
I can see your point. I think projects should avoid names that 
come to close to appearing to describe themselves as _the_ solution for some 
category of function, unless the project is an umbrella for multiple options. I 
am not judging that this was the intent with Orchestra, but one could argue 
such a name “grabs” the function for one option.

I think we made a mistake with Fast Data Stacks, but no one 
else seemed to question it. It comprises a single vendor solution for a broad 
function area that has innumerable options. I think teams should be sent back 
to the drawing board for a new name, as was asked of Open-O team.

One opinion,
Bob

Robert (Bob) Monkman
Enterprise Segment Marketing Manager
150 Rose Orchard Way
San Jose, Ca 95134
M: +1.510.676.5490

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Liu Yuan
Sent: Friday, August 05, 2016 10:25 AM
To: BIN; Carella, Giuseppe
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Orchestra] new project proposal

Hi,

I just recall the OPNFV OPEN-O project was named OPNFV-MANO at the beginning. 
And during the discussion, the team thought the scope were too broad, and 
needed focus or convergence. Then the project changed the name.

About the name of the Orchestra, I think have the similar situation. The 
meaning of Orchestra also includes broad scopes. So, I am wondering why there 
is a difference between these two projects.

Regards,
Yuan


Liu Yuan
liuyuan_c...@hotmail.com

From: liuyuan_c...@hotmail.com
Date: 2016-08-02 18:23
To: Carella, Giuseppe
CC: 
opnfv-tech-discuss@lists.opnfv.org; 
Michael Pauls
Subject: Re: Re: [opnfv-tech-discuss] [Orchestra] new project proposal
Hi Giuseppe,

I just think your project needs a unique name to represent the Open Baton, 
instead of a general name. Anyway, we can see others' suggestions on this. :)

Regards,
Yuan

Liu Yuan
liuyuan_c...@hotmail.com

From: Carella, Giuseppe

[opnfv-tech-discuss] Bin will stand in today at TSC

[SULLIVAN, BRYAN L]

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

[opnfv-tech-discuss] [copper] Docs ready for integration

[SULLIVAN, BRYAN L]

Sofia,

The copper sections for the common docs are ready for integration (userguide, 
configguide in https://git.opnfv.org/cgit/copper/tree/docs).

I didn't see that there was a test run of the common guide when I submitted the 
patches for review, so I haven't verified the formatting etc of the sections. 
If there's a way I can get a common doc test run integrated into copper thru 
Gerrit let me know, and I will check the docs. Otherwise the sections are there 
(merged) and ready for test.

The copper design docs are also ready to go, and verified re formatting using 
the existing Gerrit test runs.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Functest] reporting page doc

[SULLIVAN, BRYAN L]

Morgan,

This is very helpful. 
It would be great to add links to the last run to these pages, e.g. 
http://testresults.opnfv.org/reporting/functest/release/master/index-status-joid.html
Seeing a stormy/cloudy icon, I want to immediately click on it to see what's 
up. Is that in the plan? Let me know if I can help.

Thanks,
Bryan Sullivan | AT&T

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
morgan.richo...@orange.com
Sent: Wednesday, August 17, 2016 5:53 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [Functest] reporting page doc

Hi

I created a wiki page to detail the reporting page and explain how Functest 
scoring is calculated:
https://wiki.opnfv.org/pages/viewpage.action?pageId=6828617

/Morgan



_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites 
ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez 
le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les 
messages electroniques etant susceptibles d'alteration, Orange decline toute 
responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law; they should not be distributed, used 
or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
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 Weekly Meeting A

[SULLIVAN, BRYAN L]

Hi all,

I'm on vacation this week. I'm not sure if Prakash intends to hold the MANO WG 
today, but there will be no Models project meeting today.

Thanks,
Bryan Sullivan | AT&T


-Original Appointment-
From: SULLIVAN, BRYAN L
Sent: Monday, July 18, 2016 12:12 PM
To: SULLIVAN, BRYAN L; 'opnfv-tech-discuss@lists.opnfv.org'
Cc: MORTON JR., AL; 'Andrew Veitch'; 'David Suarez Fuentes'; GUPTA, ALOK; Henry 
Fourie; Ulas Kozat; Mario Torrecillas Rodriguez; Sen, Prodip; Dan Westerberg; 
Tal Barenboim; Kuppuswamy, Prabu; Gabor Halász; Lawrence Lamers; Ola Liljedahl; 
Vul, Alex
Subject: Models Weekly Meeting A
When: Monday, August 22, 2016 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://global.gotomeeting.com/join/865421325


Sending out a calendar reminder since this makes it easier to remember!

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] Q2'2016 OPNFV Quarterly Award Winners

[SULLIVAN, BRYAN L]

Many thanks to the community for this recognition. It’s been challenging, but a 
lot of fun at the same time, and collaboration is a two-way street so many of 
you deserve equal recognition in this.

Looking forward to getting on to the D release!

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Tuesday, August 23, 2016 2:02 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Q2'2016 OPNFV Quarterly Award Winners

All,

Here are winners of the Q2'2016 Awards as was announced at the Hackfest earlier 
today.

•   Code Development: Jose Lausuch (repeat winner) & Ulas Kozat
•   Collaboration: Bryan Sullivan
•   Documentation & User Support: Mark Beierl (repeat winner)
•   Integration: Dan Radez & Hongbo Tian
•   Testing: Maryam Tahhan (repeat winner)

Thanks and congratulations to all the winners!

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

[opnfv-tech-discuss] [Models] 2016-Aug-29 Models Project Meeting #12

[SULLIVAN, BRYAN L]

Agenda from the wiki https://wiki.opnfv.org/display/models/Models+Meetings
* Status of Colorado release work
* Goals thru 2016
* * Demo at OpenStack Barcelona
* * Dec plugfest at U-NH
* * Reference libraries
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] Models Weekly Meeting A

[SULLIVAN, BRYAN L]

No, there was no meeting as no one showed up :(...
I also don't know of any discussions around onboarding yet. That's a to-do for 
the MANO WG I think.

Thanks,
Bryan Sullivan | AT&T

From: Prakash Ramchandran [mailto:prakash.ramchand...@huawei.com]
Sent: Monday, August 29, 2016 12:03 PM
To: SULLIVAN, BRYAN L ; 'opnfv-tech-discuss@lists.opnfv.org' 

Subject: RE: Models Weekly Meeting A

Bryan,

If there was any discussions on VNF On-boarding in terms of the VNFD , 
TOSCA/YANG templates and workflow with respect to Cloudify please do point to 
summary.

I missed today's Models meeting at 9 AM. Will catch up as just returned from 
Hackfest and trying to get back to normal working.

Thanks
Prakash

Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@huawei.com>
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Monday, August 22, 2016 7:40 AM
To: 'opnfv-tech-discuss@lists.opnfv.org'
Subject: Re: [opnfv-tech-discuss] Models Weekly Meeting A

Hi all,

I'm on vacation this week. I'm not sure if Prakash intends to hold the MANO WG 
today, but there will be no Models project meeting today.

Thanks,
Bryan Sullivan | AT&T


-Original Appointment-----
From: SULLIVAN, BRYAN L
Sent: Monday, July 18, 2016 12:12 PM
To: SULLIVAN, BRYAN L; 'opnfv-tech-discuss@lists.opnfv.org'
Cc: MORTON JR., AL; 'Andrew Veitch'; 'David Suarez Fuentes'; GUPTA, ALOK; Henry 
Fourie; Ulas Kozat; Mario Torrecillas Rodriguez; Sen, Prodip; Dan Westerberg; 
Tal Barenboim; Kuppuswamy, Prabu; Gabor Halász; Lawrence Lamers; Ola Liljedahl; 
Vul, Alex
Subject: Models Weekly Meeting A
When: Monday, August 22, 2016 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://global.gotomeeting.com/join/865421325


Sending out a calendar reminder since this makes it easier to remember!

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

[opnfv-tech-discuss] [opnfvdocs] Including docs in other folders to a rendered document

[SULLIVAN, BRYAN L]

Hi all,

FYI in case this is useful to you. I was trying to figure out how to include 
the following document sections in the Copper project doc (the main 
project-specific doc):

-  configguide

-  userguide

I needed to do this because:

1)  The opnfvdocs project rendering of the OPNFV-wide 
configguide/userguide/releasenotes doc is not ready, and in the meantime I need 
a way to verify that Copper sections to that doc are rendering

a.   Note I found a workaround to this by putting an index.rst file in the 
folders ala 
index.rst, 
but that only allows you to see the artifact as generated by the Jenkins job, 
and when merged there is no artifact stored under artifacts.opnfv.,org (except 
for the Jenkins job artifact)

2)  I wanted to include these additional sections in the Copper 
documentation, since

a.   It makes sense to me to have all the doc sections in a single place

b.  I wanted to use the readthedocs style as with the main Copper doc (the 
Jenkins job artifact mentioned above uses another stylesheet)

Here are the steps if you want to do this:

1)  In your main docs folder (e.g. for Copper, 
design), create a file 
which includes the other document sections - one file for each distinct section 
document you want to include, e.g.

a.   
featureconfig_link.rst

b.  
featureusage_link.rst

c.   
postinstall_link.rst

2)  In those files, specify that you want to include another file and 
provide the path, e.g.
.. include::
   ../configguide/postinstall.rst

3)  Reference those files in your document 
index.rst, e.g. 
for Copper

OPNFV Copper Project


.. toctree::
   :numbered:
   :maxdepth: 4

   introduction.rst
   definitions.rst
   usecases.rst
   architecture.rst
   requirements.rst
   featureconfig_link.rst
   postinstall_link.rst
   featureusage_link.rst

That's all you need. Now with any change to the files, you will get a combined 
rendered document in the artifacts folder. You can see these sections now at 
the end of the Copper doc: 
http://artifacts.opnfv.org/copper/docs/design/index.html

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] Models Weekly Meeting A

[SULLIVAN, BRYAN L]

Yes, the work to create reference VNF blueprints and test them with various 
VNFMs, can be referenced as a piece of the MANO WG scope. I've started with 
Cloudify, and am working on expanding to Tacker and JuJu. Giuseppe was planning 
to do the same with OpenBaton. As we wrap up Colorado, and that I was more or 
less out for 3 weeks, time has been short but it's progressing again now. I've 
got open threads going with the Cloudify and Tacker team members to resolve 
issues with setting up those VNFMs.

Thanks,
Bryan Sullivan | AT&T

From: Prakash Ramchandran [mailto:prakash.ramchand...@huawei.com]
Sent: Tuesday, August 30, 2016 1:22 PM
To: SULLIVAN, BRYAN L ; 'opnfv-tech-discuss@lists.opnfv.org' 

Subject: RE: Models Weekly Meeting A

Bryan,

Was the VNF On boarding  with Cloudify  "hello world sample" was a Model 
project that can be linked or tagged as MANO participation task?

I thought we had another one from Giuseppe for MANO API testing with 
Yardstick/Functets that was part of "Orchestra".


Another one was VES for metadata standardization for VNF Event streaming for 
Collector, await Aloks return from Leave on that.

All I am is trying to gather that can bring value to MANO Working Groups 
efforts to share best practices across different projects including upstream to 
help minimize gaps between OPNFV reference architecture and its deployments.

I did miss Model as I was on road and will try attend with some inputs on  
Sept. 12th and if possible next week Sept. 5th too.

Thanks
Prakash



Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@huawei.com>
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Tuesday, August 30, 2016 1:07 PM
To: Prakash Ramchandran; 'opnfv-tech-discuss@lists.opnfv.org'
Subject: RE: Models Weekly Meeting A

No, there was no meeting as no one showed up :(...
I also don't know of any discussions around onboarding yet. That's a to-do for 
the MANO WG I think.

Thanks,
Bryan Sullivan | AT&T

From: Prakash Ramchandran [mailto:prakash.ramchand...@huawei.com]
Sent: Monday, August 29, 2016 12:03 PM
To: SULLIVAN, BRYAN L mailto:bs3...@att.com>>; 
'opnfv-tech-discuss@lists.opnfv.org' 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: RE: Models Weekly Meeting A

Bryan,

If there was any discussions on VNF On-boarding in terms of the VNFD , 
TOSCA/YANG templates and workflow with respect to Cloudify please do point to 
summary.

I missed today's Models meeting at 9 AM. Will catch up as just returned from 
Hackfest and trying to get back to normal working.

Thanks
Prakash

Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@huawei.com>
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Monday, August 22, 2016 7:40 AM
To: 'opnfv-tech-discuss@lists.opnfv.org'
Subject: Re: [opnfv-tech-discuss] Models Weekly Meeting A

Hi all,

I'm on vacation this week. I'm not sure if Prakash intends to hold the MANO WG 
today, but there will be no Models project meeting today.

Thanks,
Bryan Sullivan | AT&T


-Original Appointment-
From: SULLIVAN, BRYAN L
Sent: Monday, July 18, 2016 12:12 PM
To: SULLIVAN, BRYAN L; 'opnfv-tech-discuss@lists.opnfv.org'
Cc: MORTON JR., AL; 'Andrew Veitch'; 'David Suarez Fuentes'; GUPTA, ALOK; Henry 
Fourie; Ulas Kozat; Mario Torrecillas Rodriguez; Sen, Prodip; Dan Westerberg; 
Tal Barenboim; Kuppuswamy, Prabu; Gabor Halász; Lawrence Lamers; Ola Liljedahl; 
Vul, Alex
Subject: Models Weekly Meeting A
When: Monday, August 22, 2016 9:00 AM-10:00 AM (UTC-08:00) Pacific Time (US & 
Canada).
Where: https://global.gotomeeting.com/join/865421325


Sending out a calendar reminder since this makes it easier to remember!

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

[opnfv-tech-discuss] opnfv.org is not resolving

[SULLIVAN, BRYAN L]

Anyone else seeing this issue? Just started happening. Opnfv.org and all 
subdomains.

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] harmonized configuration set for OPNFV

[SULLIVAN, BRYAN L]

I’d suggest a Jira issue be created that we can add details to. I agree that 
this will be a very helpful effort. Right now there is substantial variation in 
the deployed platform e.g. even to such things as:

-  Number and names of networks, routers, etc created by default

-  Default images created in glance

-  Names of projects (e.g. “services” vs “service”)

-  …

These variations add complexity to install and test scripts for features. As we 
eliminate the variations, we do need a process to identify and address  impact 
to existing code and tests.

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Jack Morgan
Sent: Tuesday, September 06, 2016 8:41 AM
To: TSC OPNFV
Cc: TECH-DISCUSS OPNFV
Subject: Re: [opnfv-tech-discuss] harmonized configuration set for OPNFV


Yujun,

Thanks for raising this issue. This is a longer term issue to solve but for now 
I've added it as a topic for to the Infra WG weekly meeting. I'm hoping to 
solve this for the D release and been tasked by the TSC to help drive this 
effort. Please join the Infra WG meeting to provide your input.

On 09/05/2016 12:11 AM, Yujun Zhang wrote:
Dear TSC,

We have encountered some issues on the openstack environment configuration for 
some projects and it could not be resolved within the project scope. So I have 
to escalate it to TSC to look for a solution.

Some OPNFV project requires dedicated configuration on common services. But the 
environment deployed by the installers may not always come with a valid 
configuration.

For example, doctor project requires `notifier://?topic=alarm.all` in 
ceilometer event pipeline configuration. But the default deployed environment 
by fuel does not include this configuration. There has been a long debates 
between the two teams on where the modification should be made [1][2]. The 
contradiction is that if we enable this notifier topic, doctor will work, but 
nobody can guarantee that other projects are not affected.

OPNFV is targeting to deliver a "de facto standard open source NFV platform for 
the industry" [3]. The platform on software part includes not only the services 
installed but also a common configuration for all projects to run.

So the first step should be working out a harmonized configuration set which 
will allow all existing projects to run normally. Then it can be used to 
validate the deployed environment from each installer.

I'm sincerely hoping TSC can help to resolve this issue and lead OPNFV to a 
success.

[1] https://gerrit.opnfv.org/gerrit/#/c/18285/
[2] https://jira.opnfv.org/browse/FUEL-159
[3] https://wiki.opnfv.org/

--
Yujun Zhang




___

opnfv-tech-discuss mailing list

opnfv-tech-discuss@lists.opnfv.org

https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss



--

Jack Morgan

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

Re: [opnfv-tech-discuss] How are Documentation/Reference Projects Published in C release

[SULLIVAN, BRYAN L]

My take is that we have projects, and those projects create documents that are 
optionally (on request of the project) included in the release documentation. 
We need go no further than that. Labelling projects (something I thought we had 
moved away from) or types of documents/focuses (e.g. requirements) and applying 
different policies as to what/how they are included in the release 
documentation, is unnecessary and ultimately confusing to the community.

As an example, my Copper project 
documentation is one 
document (a “design” document but that’s only a repo folder naming convention) 
that addresses the subject completely – e.g. use cases, architecture, 
requirements, and implementation approaches. I see no reason to apply a 
different policy to the separate sections of this document based upon their 
focus, and I don’t intend to. The document itself addresses what is specific to 
Colorado, can what is possible future work. This will be what is published for 
Copper.

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Georg Kunz
Sent: Tuesday, September 06, 2016 8:56 AM
To: Adi Molkho; Sofia Wallin; Kunzmann, Gerald; Daniel Smith; David McBride; 
Christopher Price
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

Hi Adi,

We had a discussion on this in the docs meeting last week and to my 
understanding we came to the agreement that the requirement docs should be 
included. The exact location and the naming still needs to be decided upon. For 
instance, it should be clear for users of the release that the requirement docs 
do NOT describe features which are available in the release. One proposal is to 
add a section to the documentation library called “Requirement Analyses” (my 
favorite) or “Future Work” (indicating that the requirements identified by the 
requirement docs will hopefully be addressed in future releases.

I hope we can conclude on the details soon, either here on the list or in 
tomorrow’s docs meeting.

Georg

From: Adi Molkho [mailto:adi.mol...@huawei.com]
Sent: Tuesday, September 06, 2016 3:40 PM
To: Sofia Wallin; Kunzmann, Gerald; Georg Kunz; Daniel Smith; David McBride; 
Christopher Price
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

Hi
Is there any final conclusion to this mail thread ? Are the documents of the 
requirement project going to be part of the C release?

Thanks
Adi



From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]
 On Behalf Of Sofia Wallin
Sent: Wednesday, August 31, 2016 1:42 PM
To: Kunzmann, Gerald; Georg Kunz; Daniel Smith; David McBride; Christopher Price
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

Hi everyone,
I haven’t been involved in the discussion whether we want the requirement 
projects to be a part of our releases or not.
But when it comes to documentation it is obvious that people see a need to 
include this kind of work as well.
I agree with Chris, “to publish a “future work” section of our release library 
that describes more where our community is heading”.

I talked to Daniel yesterday and we think that it would be fine to handle this 
in the same way as the release documentation. We create an introduction 
document explaining what this is about and link to the projects documentation.


But let’s discuss this (and hopefully agree),
I will add this as topic for the docs meeting this afternoon, so people 
concerned are welcome to call in.

BR,
Sofia

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Kunzmann, 
Gerald
Sent: den 31 augusti 2016 09:51
To: Georg Kunz; Daniel Smith; David McBride
Cc: 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

Hi David, all,

My 2 cent on your question:

The question is: does it make sense for requirements projects to participate in 
releases until they're ready to deliver code?

Requirement projects are an essential part of OPNFV and some may even do all 
development in upstream, i.e. there might even be no code within OPNFV except 
test cases. Thus, I support having the requirement documents as part of the 
release documentation.

Best regards,
Gerald

From: 
opnfv-tech-discuss-boun...@lists.opnfv.

Re: [opnfv-tech-discuss] Following up on Project Health metrics discussion

[SULLIVAN, BRYAN L]

I’m unsure of the overall value of this exercise. Simply ask the PTLs what the 
“health” of the project is. An honest PTL will tell you, and that’s the only 
type we should elect.

Publish metrics if you want (we already do), but I would avoid trying to draw 
conclusions from them. We do not have the luxury (if you can even call it 
that!) of creating and maintaining a project-introspection framework ala what 
you might see in corporate development shops. Even considering what metrics are 
“useful” for specific purposes (e.g. what “useful”/reliable implications can 
you draw from them) takes too much time away from the real work.

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Frank 
Brockners (fbrockne)
Sent: Tuesday, September 06, 2016 7:39 AM
To: Raymond Paik; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Following up on Project Health metrics 
discussion

Hi Ray,

thanks for posting the initial cut. IMHO a "composite score", as proposed on 
the page, could be *very* misleading, especially for projects which do most of 
the work upstream. So unless we track all upstream repos and upstream Jiras (or 
similar), I would suggest to *not* compute a composite score but evaluate 
things qualitatively only.

Thanks, Frank

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Montag, 29. August 2016 19:33
To: 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Following up on Project Health metrics discussion

All,

I had an action item from last week to start a wiki page for the "project 
health metrics".  You can find a proposal page at 
https://wiki.opnfv.org/display/PROJ/Project+Health+Metrics.

Please add your comments/feedback via email or directly on the wiki page.  I 
listed four activity areas that was discussed on the TSC call, but feel free to 
add other activities that the community should consider.

Thanks,

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

Re: [opnfv-tech-discuss] How are Documentation/Reference Projects Published in C release

[SULLIVAN, BRYAN L]

David,

To a point I put into my comments, there is no such thing as a “requirements 
project” in OPNFV anymore. There are projects, and they have artifacts. If the 
artifacts are simply documents, there are quality gates that govern them (the 
gerrit commit review process), and project schedule gates as well.

I’m not sure what you mean as “quality metrics” for code contributed in a 
release, other than gerrit reviews, tests, and project milestones. So I would 
suggest not to push the analogy too far with documents, as the basis for 
holding code up as an example is questionable other than the very same things 
that apply for documents: reviews, tests (to the extent that we test documents 
as suggested on the opnfvdocs project wiki) and milestones.

Thanks,
Bryan Sullivan | AT&T

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Tuesday, September 06, 2016 1:00 PM
To: HU, BIN
Cc: SULLIVAN, BRYAN L; Georg Kunz; Adi Molkho; Sofia Wallin; Kunzmann, Gerald; 
Daniel Smith; Christopher Price; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

Bin,

You hit on a key point:  "meets milestones and other quality metrics".  One 
reason that I question whether requirements projects should join a release is 
that the requirements projects associated with Colorado responded with "N/A" 
for most or all of their milestone reporting.  That's understandable, since the 
milestones are oriented toward projects that are creating or modifying code.  
I'm not aware of any quality metrics that they have been subjected to.

So, that raises the question, should requirements projects be tracked in a 
release?  If so, what milestones or other metrics should be used to track them?

David

On Tue, Sep 6, 2016 at 12:07 PM, HU, BIN 
mailto:bh5...@att.com>> wrote:
+1 for Bryan’s point.

If a project requests its docs to be included in release documentation, and it 
meets milestones and other quality metrics and won’t pose any adversary effects 
on release schedule, it should be included.

Many documentation provides “knowledge”, as Heather indicated in a separate 
thread, and is very valuable to industry.

Thanks
Bin

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>]
 On Behalf Of SULLIVAN, BRYAN L
Sent: Tuesday, September 06, 2016 9:40 AM
To: Georg Kunz mailto:georg.k...@ericsson.com>>; Adi 
Molkho mailto:adi.mol...@huawei.com>>; Sofia Wallin 
mailto:sofia.wal...@ericsson.com>>; Kunzmann, Gerald 
mailto:kunzm...@docomolab-euro.com>>; Daniel Smith 
mailto:daniel.sm...@ericsson.com>>; David McBride 
mailto:dmcbr...@linuxfoundation.org>>; 
Christopher Price 
mailto:christopher.pr...@ericsson.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
My take is that we have projects, and those projects create documents that are 
optionally (on request of the project) included in the release documentation. 
We need go no further than that. Labelling projects (something I thought we had 
moved away from) or types of documents/focuses (e.g. requirements) and applying 
different policies as to what/how they are included in the release 
documentation, is unnecessary and ultimately confusing to the community.

As an example, my Copper project 
documentation<http://artifacts.opnfv.org/copper/docs/design/index.html> is one 
document (a “design” document but that’s only a repo folder naming convention) 
that addresses the subject completely – e.g. use cases, architecture, 
requirements, and implementation approaches. I see no reason to apply a 
different policy to the separate sections of this document based upon their 
focus, and I don’t intend to. The document itself addresses what is specific to 
Colorado, can what is possible future work. This will be what is published for 
Copper.

Thanks,
Bryan Sullivan | AT&T

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Georg Kunz
Sent: Tuesday, September 06, 2016 8:56 AM
To: Adi Molkho; Sofia Wallin; Kunzmann, Gerald; Daniel Smith; David McBride; 
Christopher Price
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] How are Documentation/Reference Projects 
Published in C release

Hi Adi,

We had a discussion on this in the docs meeting last week and to my 
understanding we came to

Re: [opnfv-tech-discuss] [opnfv-mano-wg] Need Subscription list plus discussions for Sept 14 VNF onbaoarding & Mapping TOSCA service to NFV{VNFD+NSD}

[SULLIVAN, BRYAN L]

Prakash,

Some responses inline.

Thanks,
Bryan Sullivan | AT&T

From: Prakash Ramchandran [mailto:prakash.ramchand...@huawei.com]
Sent: Tuesday, September 06, 2016 6:53 PM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: Margaret Chiosi ; SULLIVAN, BRYAN L 
; denglin...@chinamobile.com; 
giuseppe.care...@fokus.fraunhofer.de; Ulas Kozat ; 
Yingjun Li ; artur.tyl...@canonical.com; 
dne...@redhat.com; sric...@gmail.com; bob.monk...@arm.com; 
christopher.pr...@ericsson.com; raghavendrachari.kams...@hpe.com; 
ljlam...@live.com
Subject: [opnfv-tech-discuss][opnfv-mano-wg] Need Subscription list plus 
discussions for Sept 14 VNF onbaoarding & Mapping TOSCA service to NFV{VNFD+NSD}

Hi all,
There  was a request from Margret that she cannot  get this as without joining 
opnfv-tech-list and that she and many in Polestar/S&P would prefer that we have 
a separate opnnfv-mano-wg subscription. My understanding is that this will be 
addressed by LF helpdesk. Until then I am copying the listed participants of 
MANO WG on wiki page and this is for September 14th meeting. We still have a 
week's time to get things moving.

If so can I request LF helpdesk to enable the opnfv-mano-wg subscription list.
 We do have #opnfv-mano channel that we use besides the scheduled


As part of MANO WG tasks would like to initiate debate on following items:

Like to verify with Models & Domino/parser if they would create a opnfv-mano-wg 
tags and create a Jira tickets for the  same?
[bryan] Not sure what you mean by tags or why we need to create Jira tickets. I 
recommend to avoid getting too deep into Jira for project management at the 
level that these groups work (analysis, experimentation, specification). My 
experience is that except for code dev/bug tracking, Jira brings a lot of 
overhead that I don't think we need. Outlining the work of the group at a 
high-level is fine with Jira, but let's watch out for the overhead.


1.   VNF On boarding as listed by Polestar / S&P team by Bryan

[bryan] I will add some of the aspects of this to the wiki, as I described on 
the call, including a high-level outline of a conceptual process for 
onboarding, highlighting aspects that I think are potentially in scope for 
OPNFV projects (including those underway, today). This is work that is in the 
scope of the MANO WG, since it helps draw a thread through many of the systems 
and processes that make up a MANO stack, and above (e.g. business processes 
that are outside OPNFV/OpenSource scope).
? VNF Packaging - Compare and contrast  in how JuJu and Tacker  use OpenStack 
Glance or SDN-C (ODL/ONOS/OC}  {how do they align with IFA011?}
[bryan] This analysis is underway (or at least in scope) in the Models project, 
as a test/documentation exercise. The current state of that project is setting 
up the test environment (Cloudify, Tacker, JuJu, OpenBaton, etc) to assess how 
MANO-stack projects require/support various VNF Package elements, starting with 
TOSCA-based blueprints for reference VNFs (which will become part of the OPNFV 
CI/CD inventory along with vIMS). I welcome the support of anyone that wants to 
focus on the specific question Prakash mentioned.

2. Mapping between TOSCA and NFV for using VNFD from oasis for VNFM to use 
(http://docs.oasis-open.org/tosca/tosca-nfv/v1.0/csd03/tosca-nfv-v1.0-csd03.pdf 
)
? Review how Service Descriptors from TOSCA match with NFV and if mapped 
correctly can  Template Distribution and Parsing manage this to deliver to 
orchestrators   like Heat or any controller that can support Pub/Sub via OPNFV 
project like Domino/Parser?
[bryan] VNF Package cataloging/distribution is one of the key aspects of an 
onboarding process. As mentioned AFAIK only the Domino project has been 
considering so far some of the technical approaches to blueprint/template 
distribution (along with other VNF assets). The mapping of elements (e.g. 
Service Descriptors) is part of the information model - data model analysis 
that needs to be done; work that so far is still in the SDO realm AFAICT.

3. Would like to see OPEN-O(Opera) / OpenBaton (Orchestra) to add any Jira 
tickets that will help them on IFA007, use case or API aspects that would like 
to bring to opnfv-mano-wg

Once we know JIRA tickets are established will let Bryan lead us on 1 and will 
try bring some proposal for 2 working with Domino/Parser projects and PTLS of 
Opera and Orchestra as what they will need guidance from MANO WG to support 
them.

Thanks
Prakash


Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@huawei.com>
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






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

[opnfv-tech-discuss] Canceled: Models Weekly Meeting B

[SULLIVAN, BRYAN L]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:Pacific Standard Time
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="SULLIVAN, BRYAN L":MAILTO:bs3...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='opnfv-tec
 h-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON JR.
 , AL":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Andrew Ve
 itch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='David Sua
 rez Fuentes':MAILTO:david.suarez.fuen...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Hesham El
 Bakoury':MAILTO:hesham.elbako...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Henry Fou
 rie':MAILTO:louis.fou...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Mario Tor
 recillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Sen, Prod
 ip'":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Dan Weste
 rberg':MAILTO:dan.westerb...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Kuppuswam
 y, Prabu'":MAILTO:prabu.kuppusw...@spirent.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Lawrence 
 Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ola Lilje
 dahl':MAILTO:ola.liljed...@arm.com
DESCRIPTION;LANGUAGE=en-US:Sending out a calendar reminder since this makes
  it easier to remember!\n\nhttps://wiki.opnfv.org/display/models/Models+Me
 etings\nIRC: #opnfv-models\, e.g.  https://www.irccloud.com/#!/ircs://irc.
 freenode.net:6697/%23opnfv-models\n\n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=MO;WKST=SU
EXDATE;TZID=Pacific Standard Time:20160620T17
SUMMARY;LANGUAGE=en-US:Canceled: Models Weekly Meeting B
DTSTART;TZID=Pacific Standard Time:20160307T17
DTEND;TZID=Pacific Standard Time:20160307T18
UID:04008200E00074C5B7101A82E008B03F73AB8778D101000
 01000B43E4A21E706944BB10E5A1290F31D94
CLASS:PUBLIC
PRIORITY:1
DTSTAMP:20160912T203517Z
TRANSP:OPAQUE
STATUS:CANCELLED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/865421325
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:1691514848
X-MICROSOFT-CDO-BUSYSTATUS:FREE
X-MICROSOFT-CDO-INTENDEDSTATUS:FREE
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:2
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [polestar] ODL Seattle Summit 9/29 12-3PM Polestar/EUG/MANO/Functest meetup Agenda

[SULLIVAN, BRYAN L]

· I added an item: (draft) MANO WG input on the end-to-end VNF/service 
lifecycle and the Onboarding phase in particular is at VNF 
Onboarding.
Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Margaret Chiosi
Sent: Wednesday, September 14, 2016 6:01 AM
To: opnfv-tech-discuss
Subject: [opnfv-tech-discuss] [polestar] ODL Seattle Summit 9/29 12-3PM 
Polestar/EUG/MANO/Functest meetup Agenda

Folks: I created in the polestar meeting wiki a section for this F2F meeting. 
Feel free to submit ideas on an agenda.
the overall goal is to discuss with the EUG, MANO, Functest reps VNF on 
boarding scenario.
We will just flush it out. But if there are other ideas you would like to 
discuss, add it to the agenda.
thanks.

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

[opnfv-tech-discuss] [Models] 2016-Sep-19 Models Project Meeting #12 agenda

[SULLIVAN, BRYAN L]

https://global.gotomeeting.com/join/865421325
#opnfv-models

Agenda:
* Status of current work
* * Hello World on Tacker
* * Hello World on Cloudify
* VNF Onboarding
* VES event model in YANG
* Goals thru 2016
* * Demo at OpenStack Barcelona
* * Dec plugfest at U-NH
* * Reference libraries
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

[opnfv-tech-discuss] [Models] 2016-Sep-19 Models Project Meeting #12 minutes

[SULLIVAN, BRYAN L]

 events). For the Models project, the issue will be how to include 
YANG data models in the VNF package, and what NFVO/VNFM functions will handle 
them.
  *   Goals thru 2016 (Bryan)
 *   Demo at OpenStack Barcelona
*   As a sponsor, AT&T will have a booth at OpenStack. We will demo a 
VNF running on OPNFV Colorado, and integrating with a PoC 
closed-loop-monitoring system using VES as the event stream framework. This 
demo will include a reference VNF installed via a TOSCA blueprint via Tacker or 
Cloudify (or both, if we have time).
 *   Dec plugfest at U-NH
*   As shown at Colorado Plugfest Test 
Cases<https://wiki.opnfv.org/display/EVNT/Colorado+Plugfest+Test+Cases>, the 
December plugfest will cover various reference blueprint tests with any 
VNFM/NFVO projects/vendors that want to demonstrate their compatibility with 
those reference blueprints. The blueprints will be provided in October so the 
VNFM/NFVO under test can determine whether they will be able to participate. As 
noted, the goal is not 100% compatibility verification, rather "to demonstrate 
the degree of portability, uncover issues for followup, build the library of 
tested blueprints (VNFM-specific, as needed), and overall come away with a much 
clearer assessment of VNFM product support for blueprint standards"
 *   Reference libraries
*   These will be developed as part of the Models repo through Q4 2016. 
The goal is to establish several reference VNFs and blueprints, for use in 
plugfests and Functest.


Thanks,
Bryan Sullivan | AT&T

From: SULLIVAN, BRYAN L
Sent: Monday, September 19, 2016 8:55 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [Models] 2016-Sep-19 Models Project Meeting #12 agenda

https://global.gotomeeting.com/join/865421325<https://global.gotomeeting.com/join/865421325/>
#opnfv-models

Agenda:
* Status of current work
* * Hello World on Tacker
* * Hello World on Cloudify
* VNF Onboarding
* VES event model in YANG
* Goals thru 2016
* * Demo at OpenStack Barcelona
* * Dec plugfest at U-NH
* * Reference libraries
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

[opnfv-tech-discuss] [Models] Progress on VNF test cases

[SULLIVAN, BRYAN L]

Hi all,

A quick update in case some of this is useful to others. I updated the Models 
testing wiki page https://wiki.opnfv.org/display/models/testing with info on 
VNF tests in development.


* Today I got the OpenStack Interop challenge lampstack blueprint 
(Ansible-based) running on JOID (nosdn scenario). This is a 4-VM deployment 
which will be a good target for a medium-complexity TOSCA blueprint, which I'll 
start working on. Prior to that I'll try it on an ODL based scenario as well. I 
think this would be a good test to integrate into Functest for Danube.

o   I'll probably use this blueprint as the basis for the VES demo I will do in 
OpenStack Barcelona, at the AT&T booth, unless I can get OpenWRT working (see 
below).

* The vHello ("Hello world") blueprint (TOSCA-based, using Tacker) is 
also working on JOID and Apex. I'm working on a similar one for Cloudify, 
currently working thru Cloudify install issues. The plan is to have these 
working in Functest for Danube also, as a smoke test for VNFMs.

* I started development on OpenWRT deployment, not yet modeled (using 
bash scripts). I'd really like to get the help of anyone with experience on 
OpenWRT. I think this can make a really compelling "network function" test, vs 
the others which are mostly cloud apps running on OPNFV.

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] Follow up on Upstreaming Questions

[SULLIVAN, BRYAN L]

AFAIK there is no such thing as a "requirement project" any more, just projects 
with various types of intent to produce one thing or another. Projects can have 
multiple types of intent to add value in OPNFV, e.g. gap analysis, testing, 
prototyping, platform feature development, upstream work motivating etc. All of 
that can be documented, and those documents can be published at release time or 
whenever a project wants.

But I think I know what you are asking anyway, which I would phrase as "for 
work in projects that does not result in OPNFV functional artifacts (tests, 
platform code), how do we know that this work is relevant to anyone outside 
OPNFV?". (note we could ask the same thing for even projects that *do* produce 
functional artifacts...)

IMO if we cared (not that I think we should, at least *too* strongly, if that 
takes our focus away from just getting stuff done), we could ask projects to 
post on their wiki home notes about the impact that they believe (and can 
evidence if possible) their work is having outside OPNFV. Anything more than 
that may begin to beg the question "who am I doing this for?" when projects 
consider the effort, e.g. if required (or strongly suggested) that JIRA tickets 
be created to track (and prove) upstream value.

For me, as PTL/lead in the Copper, Models, and VES projects I can sign up to 
doing that (post notes on the wiki home). Will that be enough?

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Daniel Smith
Sent: Tuesday, September 20, 2016 9:57 AM
To: David McBride ; Fatih Degirmenci 
; jack.mor...@intel.com; Christopher Price 
; Heather Kirksey 
(hkirk...@linuxfoundation.org) ; Ray Paik 

Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Follow up on Upstreaming Questions

Hello TSC Membrs

Several weeks ago as part of the inclusion of Requirements Projects,  I asked 
how we know that people are looking at what we are producing in Requirements 
projects and how we (OPNFV) ensure that deliverables from Requirements projects 
are being reviewed and taken into account upstream (from an OPNFV overall 
standpoint).

Would any of you be able to shed some light on this?  The current impression 
that I have is we have the docs that sit in a repo and that's it.

Thank you



[Ericsson]

Daniel Smith
Sr. System Designer
Ericsson Inc.
8400 Decarie Blvd.  Montreal, PQ
(514)-594-2799

[http://www.ericsson.com/current_campaign]

Legal entity: Ericsson AB, registered office in Stockholm. This Communication 
is Confidential. We only send and receive email on the basis of the terms set 
out at 
www.ericsson.com/email_disclaimer

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

Re: [opnfv-tech-discuss] Plugfest registration reminder plus the co-located Hackfest

[SULLIVAN, BRYAN L]

I added three topics to that page:

· Creating VNF blueprint tests: approaches to creating automated 
scripts that install VNFMs, blueprints, lifecycle-manage them, etc.

· Integrating VES agent code into your VNFs.

· Hacking policies thru Congress.

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Tuesday, September 06, 2016 11:17 PM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Plugfest registration reminder plus the 
co-located Hackfest

All,

A reminder that you can now register for the 2nd OPNFV Plugfest at 
https://www.regonline.com/OPNFVPlugfestDec2016.

Also, as was discussed on the TSC call last week, the Q4 Hackfest will be 
co-located with the Plugfest.  Under the Plugfest wiki, I created a Hackfest 
planning page at 
https://wiki.opnfv.org/display/EVNT/Co-located+Hackfest+Planning+Page

During our first plugfest, we had some great sessions led by project team 
members from testing and installer projects and those are good examples of 
hacking sessions that we could repeat at UNH-IOL.  Please add your 
topic/session ideas to the wiki page.

Thanks,

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

Re: [opnfv-tech-discuss] [OPNFV] [functest] [D release]

[SULLIVAN, BRYAN L]

Morgan,

That's a big page so I'm not sure where to put this input, but here are some 
things in scope for Danube:

* Models: several new VNFs and VNFM tests, some already listed at 
https://wiki.opnfv.org/display/models/testing. Some of these will be used in 
the Colorado Plugfest - see the "VNF Portability" section on the page 
https://wiki.opnfv.org/display/EVNT/Colorado+Plugfest+Test+Cases. VNFMs will 
include Tacker, Cloudify, OpenBaton, etc. The tests will focus on simple to 
medium-complexity VNFs, specific TOSCA-based resource requirements as supported 
by those VNFMs, and YANG-based application control via ODL.

* VES: Deployment of a VES Hello World VNF, and reference (real) VNFs 
integrated with VES

* Copper: additional policy test cases

Thanks,
Bryan Sullivan | AT&T

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of 
morgan.richo...@orange.com
Sent: Friday, September 23, 2016 8:09 AM
To: Jose Lausuch ; serena feng 
; OLLIVIER Cédric IMT/OLN 
; Jose Lausuch ; 
Tikkanen, Viktor (Nokia - FI/Espoo) ; Kosonen, Juha 
(Nokia - FI/Espoo) ; Gaynor, Colum (Nokia - FI/Espoo) 
; Haapavirta, Juha (Nokia - FI/Espoo) 
; Kamsali, Raghavendrachari 
; Meimei ; valentin 
boucher 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [OPNFV] [functest] [D release]

Hi

based on the discussion initiated during last Functest weekly meeting, I
created the Danube page for the project.

https://wiki.opnfv.org/display/functest/Functest+Danube

as mentioned in the beginning of the page, this page is a draft

The goal is to collect element to prepare the D release.

Functest evolutions are expected in

- the Functest framework (reflexion on the relations between the test
projects (API), dockerization, CI evolution, reporting, dashboard)

- new tools and libs

- the new tests (unit, functional, VNF onboarding,...)

If you want to participate to Functest D release feel free to modify the
page and/or create new pages referenced from this one

You can also obviously use the mailing list or meet us during the weekly
meeting (Every Tuesday 8 AM UTC #opnfv-functest)

/Morgan


_

Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou 
falsifie. Merci.

This message and its attachments may contain confidential or privileged 
information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete 
this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been 
modified, changed or falsified.
Thank you.

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

[opnfv-tech-discuss] Notice of intent to participate in OPNFV Danube release

[SULLIVAN, BRYAN L]

Hear ye, by these presents you are notified that the Copper project intends to 
participate in the Danube release.

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] Notice of intent to participate in OPNFV Danube release

[SULLIVAN, BRYAN L]

What he said, for the Models project (as PTL).

Thanks,
Bryan Sullivan | AT&T

From: SULLIVAN, BRYAN L
Sent: Tuesday, September 27, 2016 6:16 AM
To: opnfv-tech-discuss@lists.opnfv.org; opnfv-...@lists.opnfv.org
Subject: Notice of intent to participate in OPNFV Danube release

Hear ye, by these presents you are notified that the Copper project intends to 
participate in the Danube release.

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] Notice of intent to participate in OPNFV Danube release

[SULLIVAN, BRYAN L]

Oops, just saw David's note about holding off on these notices for now. So 
Models and Copper are holding off.
But you are warned.

Thanks,
Bryan Sullivan | AT&T

From: SULLIVAN, BRYAN L
Sent: Tuesday, September 27, 2016 6:19 AM
To: 'opnfv-tech-discuss@lists.opnfv.org' ; 
'opnfv-...@lists.opnfv.org' 
Subject: RE: Notice of intent to participate in OPNFV Danube release

What he said, for the Models project (as PTL).

Thanks,
Bryan Sullivan | AT&T

From: SULLIVAN, BRYAN L
Sent: Tuesday, September 27, 2016 6:16 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
opnfv-...@lists.opnfv.org<mailto:opnfv-...@lists.opnfv.org>
Subject: Notice of intent to participate in OPNFV Danube release

Hear ye, by these presents you are notified that the Copper project intends to 
participate in the Danube release.

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

[opnfv-tech-discuss] New process for Test Plans etc in Danube

[SULLIVAN, BRYAN L]

David,

As noted in the release call today, I'd like to help you find the right 
solution toward visibility of test planning by projects, which meets the need 
(which needs to be defined) in the lightest-weight way. I suggest that we start 
a wiki page which defines the goals for the process changes you've proposed, 
clarifying:

-  What are the issues that these process changes are intended to 
address

o   Specific examples from Colorado would be helpful. I don't think any project 
should be overly concerned about a retrospective discussion of perceived issues 
and future solutions to them.

o   We should also point to examples of perceived best practices from Colorado.

-  What is the "ask" in response to those issues.

o   I heard today, the development of a test plan that projects would publish.

-  What are the solution alternatives to that ask, e.g.

o   Sections in project documents (vs a separate document), e.g. as shown in 
10.1. Copper functional 
tests
 (admittedly, brief... but a start)

o   wiki pages (as Jose pointed to, for 
FuncTest - which 
needs to be updated as I notice now...), or as I created for 
Copper

o   creating a template for test planning clarity through JIRA

o   ...

-  What are the upstream best practices for this ask, that we might 
adopt

-  What are the thoughts of the community on the issues and proposals

Further I suggest we make very sure that all projects/PTLs are aware of the 
proposed changes and have a chance to weigh in ASAP in the process.

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] Updated Invitation: OPNFV SPC Polestar WG Call (8/25-9/29) @ Thu Sep 29, 2016 10am - 1pm (CDT) (m...@linuxfoundation.org)

[SULLIVAN, BRYAN L]

FYI, this meeting will be noon-3 as earlier noted by Margaret. It will be in 
the same room (407-408).

Thanks,
Bryan Sullivan | AT&T


-Original Appointment-
From: m...@linuxfoundation.org [mailto:m...@linuxfoundation.org]
Sent: Thursday, September 15, 2016 10:32 AM
To: m...@linuxfoundation.org; opnfv-tech-discuss@lists.opnfv.org; SULLIVAN, 
BRYAN L; dick.c...@ztetx.com; sandra.l.riv...@intel.com; Raymond Paik; 
zhangyujun+...@gmail.com; paul...@emc.com; dmcbr...@linuxfoundation.org; 
jonne.soini...@nokia.com; pyeg...@juniper.net; prodip@hpe.com; 
margaretchiosi.o...@gmail.com; dne...@redhat.com; bob.monk...@arm.com; 
cyo...@clearpathnet.com; hkirk...@linuxfoundation.org; 
anthony.so...@huawei.com; christopher.pr...@ericsson.com; 
john.v.he...@intel.com; FORD, TOBY; fbroc...@cisco.com; 
ulrich.kle...@huawei.com; WRIGHT, STEVEN A
Subject: Updated Invitation: OPNFV SPC Polestar WG Call (8/25-9/29) @ Thu Sep 
29, 2016 10am - 1pm (CDT) (m...@linuxfoundation.org)
When: Thursday, September 29, 2016 3:00 PM-6:00 PM .
Where: F2F at OpenDayLight Summit


This event has been changed.
more details 
»<https://www.google.com/calendar/event?action=VIEW&eid=OWJzNG1wcTMwbjM5amdkMHBtZzlobTkwdDBfMjAxNjA5MjlUMTMwMDAwWiBiczMxMzFAYXR0LmNvbQ&tok=MjMjbXl1QGxpbnV4Zm91bmRhdGlvbi5vcmc3MmM2YWFkNmZiMDgyODc0NzI2YTUxYWYyZDQ5ZmUzNmMwMTAwOThh&ctz=America/Chicago&hl=en>

OPNFV SPC Polestar WG Call (8/25-9/29)
Changed: 2016-Sep-29 Polestar WG Meeting (Joint with MANO/EUG WGs) #10 - ODL 
Bellevue F2F
Agenda:
--Modify the Openstack user story process to be OPNFV version.
--Flesh out VNF onboarding user story more indepth with MANO, EUG and Polestar 
WGs
(draft) MANO WG input on the end-to-end VNF/service lifecycle and the 
Onboarding phase in particular is at VNF Onboarding
--Work Operator/Producer terminology
--Review Grouping into 2 categories - methodology & platform

When
Changed: Thu Sep 29, 2016 10am – 1pm Central Time

Where
Changed: F2F at OpenDayLight Summit 
(map<https://maps.google.com/maps?q=F2F+at+OpenDayLight+Summit&hl=en>)

Calendar
m...@linuxfoundation.org

Who
•
m...@linuxfoundation.org - organizer

•
opnfv-tech-discuss@lists.opnfv.org

•
bs3...@att.com

•
dick.c...@ztetx.com

•
sandra.l.riv...@intel.com

•
Raymond Paik

•
zhangyujun+...@gmail.com

•
paul...@emc.com

•
dmcbr...@linuxfoundation.org

•
jonne.soini...@nokia.com

•
pyeg...@juniper.net

•
prodip@hpe.com

•
margaretchiosi.o...@gmail.com

•
dne...@redhat.com

•
bob.monk...@arm.com

•
cyo...@clearpathnet.com

•
hkirk...@linuxfoundation.org

•
anthony.so...@huawei.com

•
christopher.pr...@ericsson.com

•
john.v.he...@intel.com

•
tf4...@att.com

•
fbroc...@cisco.com

•
ulrich.kle...@huawei.com

•
sw3...@att.com



Going?   
Yes<https://www.google.com/calendar/event?action=RESPOND&eid=OWJzNG1wcTMwbjM5amdkMHBtZzlobTkwdDBfMjAxNjA5MjlUMTMwMDAwWiBiczMxMzFAYXR0LmNvbQ&rst=1&tok=MjMjbXl1QGxpbnV4Zm91bmRhdGlvbi5vcmc3MmM2YWFkNmZiMDgyODc0NzI2YTUxYWYyZDQ5ZmUzNmMwMTAwOThh&ctz=America/Chicago&hl=en>
 - 
Maybe<https://www.google.com/calendar/event?action=RESPOND&eid=OWJzNG1wcTMwbjM5amdkMHBtZzlobTkwdDBfMjAxNjA5MjlUMTMwMDAwWiBiczMxMzFAYXR0LmNvbQ&rst=3&tok=MjMjbXl1QGxpbnV4Zm91bmRhdGlvbi5vcmc3MmM2YWFkNmZiMDgyODc0NzI2YTUxYWYyZDQ5ZmUzNmMwMTAwOThh&ctz=America/Chicago&hl=en>
 - 
No<https://www.google.com/calendar/event?action=RESPOND&eid=OWJzNG1wcTMwbjM5amdkMHBtZzlobTkwdDBfMjAxNjA5MjlUMTMwMDAwWiBiczMxMzFAYXR0LmNvbQ&rst=2&tok=MjMjbXl1QGxpbnV4Zm91bmRhdGlvbi5vcmc3MmM2YWFkNmZiMDgyODc0NzI2YTUxYWYyZDQ5ZmUzNmMwMTAwOThh&ctz=America/Chicago&hl=en>
more options 
»<https://www.google.com/calendar/event?action=VIEW&eid=OWJzNG1wcTMwbjM5amdkMHBtZzlobTkwdDBfMjAxNjA5MjlUMTMwMDAwWiBiczMxMzFAYXR0LmNvbQ&tok=MjMjbXl1QGxpbnV4Zm91bmRhdGlvbi5vcmc3MmM2YWFkNmZiMDgyODc0NzI2YTUxYWYyZDQ5ZmUzNmMwMTAwOThh&ctz=America/Chicago&hl=en>
Invitation from Google Calendar<https://www.google.com/calendar/>

You are receiving this courtesy email at the account bs3...@att.com because you 
are an attendee of this event.
To stop receiving future updates for this event, decline this event. 
Alternatively you can sign up for a Google account at 
https://www.google.com/calendar/ and control your notification settings for 
your entire calendar.
Forwarding this invitation could allow any recipient to modify your RSVP 
response. Learn 
More<https://support.google.com/calendar/answer/37135#forwarding>.


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

[opnfv-tech-discuss] [VES] OpenStack Days Seattle presentation

[SULLIVAN, BRYAN L]

Hi all,

I've uploaded "OPNFV VES: A Modeled Approach to Monitoring VNF Event Streams" 
on the VES wiki: 
OPNFV_VES_OpenStack_Days_Seattle.pptx
I'll be presenting this today at the OpenStack Seattle 
Days event, as well as participating in a 
panel on "OpenStack & Telcos/NFV".  I'll be happy to meetup with any of you 
that are there, to discuss VES etc.

FYI also - the VES git repo and JIRA are now setup. I'll be uploading the work 
in progress (implementing the VES demo on OPNFV Colorado) to the git repo and 
establishing the work outline for Danube in JIRA over the next week.

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] [announce] Upgrade of Gerrit report. (ssh host key changed)

[SULLIVAN, BRYAN L]

The fix was pretty painless. For me it was (on a JOID jumphost)
ssh-keygen -f "/home/ubuntu/.ssh/known_hosts" -R [gerrit.opnfv.org]:29418
and accept the new key on a reclone.

Thanks,
Bryan Sullivan | AT&T

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aric Gardner
Sent: Sunday, October 02, 2016 4:20 PM
To: infra-steer...@lists.opnfv.org; OPNFV Tech 
; Fatih Degirmenci 

Subject: [opnfv-tech-discuss] [announce] Upgrade of Gerrit report. (ssh host 
key changed)

Hello,

The upgrade of gerrit to 2.13.1 is complete.
And jenkins has been restarted to give it more memory.

There is an unfortunate caveat. I did not consider the rsa keys on the
old gerrit server would not be compatible with java on the new server

the old gerrit server has only one key.

ssh_host_key

the new gerrit server has

ssh_host_dsa_key
ssh_host_dsa_key.pub
ssh_host_rsa_key
ssh_host_rsa_key.pub

I tried to copy over the old ssh_host_key and use it as the rsa key on
the new server, but it is in MINA SSHD custom format. Both the public
and private halves are stored in the "ssh_host_key" file using a Java
serialization format. I searched online, and did not find any
utilities to convert this.

Gerrit failed to start like so:
[2016-10-02 22:32:38,226] [main] WARN
org.apache.sshd.common.util.SecurityUtils$BouncyCastleFileKeyPairProvider
: Failed (IOException) to load key
resource=/opt/gerrit/etc/ssh_host_rsa_key: Failed to read
/opt/gerrit/etc/ssh_host_rsa_key - unknown result object: null

18:56 < AlexAvadanii> aricg-: given the time, we could fix this, but
it's probably not
  that easy as converting one file to another
using a cli tool ...
  or if there is such a tool, I can't find it

I agree with Alex, but we can't stop using gerrit while we try to fix
this unforeseen problem.

So going forward, everything works excepting the host key change. Any
machine or developer that clones over ssh will see this warning.

git clone ssh://jenkins...@gerrit.opnfv.org:29418/releng
Initialized empty Git repository in /tmp/releng/.git/
@@@
@WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
46:3a:c5:80:58:7e:24:9e:88:d3:83:29:6c:9a:80:17.
Please contact your system administrator.
Add correct host key in /home/agardner/.ssh/known_hosts to get rid of
this message.
Offending key in /home/agardner/.ssh/known_hosts:1
RSA host key for [gerrit.opnfv.org]:29418 has changed and you have
requested strict checking.
Host key verification failed.

you will need to remove the specified line in /home/"Your
user"/.ssh/known_hosts:"The line number to delete"
and then re-accept the new key.

Apologies in advance and best regards,
-Aric
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [Fuel] Danube release. Components and dependencies

[SULLIVAN, BRYAN L]

I added

[bryan] Not sure where this goes, but... for Copper
- the intent is to support Congress installation on Fuel scenarios (all). This 
will involve (as I understand it) installation via a Fuel plugin for Congress. 
Any help developing that is appreciated (unsure what Fuel plugin expertise 
exists in Copper - for sure I am not a SME)
- Copper will provide all needed testing to be sure it works, and Functest 
integration for current and new tests

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Fedor Zhadaev
Sent: Friday, September 30, 2016 2:01 AM
To: MichalSkalski , yunhong.ji...@linux.intel.com 
, opnfv-tech-discuss@lists.opnfv.org 

Subject: [opnfv-tech-discuss] [Fuel] Danube release. Components and dependencies

Hello,
As was discussed on last Fuel@OPNFV meeting, each team which participate in 
Fuel release for D should specify list of components which they will provide 
and their dependencies here 
https://etherpad.opnfv.org/p/fuel-danube-components-and-deps.
This link also could be found on wiki 
(https://wiki.opnfv.org/display/fuel/Fuel+Opnfv) under Danube header.
--
Kind Regards,
Fedor Zhadaev

email: fzhad...@mirantis.com
skype: zhadaevfm
IRC: fzhadaev
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] OPNFV on Github

[SULLIVAN, BRYAN L]

Aric,

When you say " mirroring to github is done " you don't mean currently, right? 
("will be done")

Also - any chance we could get Iben to donate opnfv to us as the org name? He 
got out ahead of this game a while back:
https://github.com/opnfv 
It would be great if we could hang our repos off that link and org...

Thanks,
Bryan Sullivan | AT&T

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Aric Gardner
Sent: Tuesday, October 04, 2016 12:32 PM
To: MORTON JR., AL 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] OPNFV on Github

The mirroring to github is done with a Gerrit plugin and updates live.

Regards,
Aric

On Tue, Oct 4, 2016 at 12:06 PM, MORTON, ALFRED C (AL)  wrote:
> Sounds good to me, +1.
>
>
>
> Additional question:
>
> How often will we execute the mirroring operation to GitHub?
>
> Nightly (UTC)?
>
>
>
> Al
>
>
>
> From: opnfv-tech-discuss-boun...@lists.opnfv.org
> [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ash
> Sent: Tuesday, October 04, 2016 11:47 AM
> To: Leif Madsen
> Cc: opnfv-tech-discuss@lists.opnfv.org
> Subject: Re: [opnfv-tech-discuss] OPNFV on Github
>
>
>
> It sounds like we're all in violent agreement on this. And I'm okay for the
> meeting being delayed to the 13th.
>
>
>
> So, to summarize:
>
>
>
> 1) The github repo should be a read-only mirror of Gerrit.
>
> 2) Gerrit should be the workflow for and point for all check-ins
>
> 3) Still, to protect ourselves on github, all admins/owners will utilize
> 2-factor authentication for security purposes.
>
> 4) We will postpone the community discussion until Bin's 10/13 call.
>
> 5) Since the github repo will be a mirror of what's on Gerrit, it will
> continue to reinforce/reflect OPNFV governance, license practices, and any
> other legalities that might have an impact upon our community.
>
>
>
> Sound good?
>
>
>
> Best,
>
>
>
> Ash
>
>
>
> On Tue, Oct 4, 2016 at 8:15 AM, Leif Madsen  wrote:
>
> On Mon, Sep 26, 2016 at 08:17:20AM +0800, Zhipeng Huang wrote:
>> As far as I understand for OpenStack they just mirror it to github, any
>> code review and patch acceptance is still done in OpenStack gerrit.
>>
>> OPNFV should have the mirror so that a broader ecosystem of software
>> developers could be built for NFV even if they could only browse the code
>> on github
>
> Exactly. As soon as you get into trying to merge PRs from GitHub you're
> going to cause all sorts of issues.
>
> Gerrit should be the defacto source for changes, and GitHub simply as a
> nice location to clone / view from. There should be no need to make
> inbound changes from GitHub a thing.
>
> --
> Leif Madsen | Partner Engineer - NFV & CI
> NFV Partner Engineering
> Red Hat
> GPG: (D670F846) BEE0 336E 5406 42BA 6194 6831 B38A 291E D670 F846
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
>
>
>
> ___
> opnfv-tech-discuss mailing list
> opnfv-tech-discuss@lists.opnfv.org
> https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] congress support in compass4nfv

[SULLIVAN, BRYAN L]

Hi Herry,

Glad to be working with Compass on in this!

Congress should be installed as a basic service that is available in all 
Compass scenarios. This is what we did for Apex and JOID. There's no need for a 
specific scenario.

You can see they types of policy use cases that are in development for Congress 
at https://wiki.opnfv.org/display/copper/testing. The test cases shown there 
are integrated into Functest.

The Doctor project also depends upon Congress for some of its features.

I have an existing Ansible 
module<https://git.opnfv.org/cgit/copper/tree/components/congress/install/ansible>
 in the copper repo, that needs to be updated since I moved to a simple 
bash-script 
approach<https://git.opnfv.org/cgit/copper/tree/components/congress/install/bash>
 back in Brahmaputra, and then worked with the JOID and Apex teams on their 
installer tools (JuJu and Puppet). We can talk about updating that script at 
some meeting if you want to set it up. We don't have regular meetings in Copper 
at this time.

Thanks,
Bryan Sullivan | AT&T

From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: Friday, October 07, 2016 9:26 PM
To: SULLIVAN, BRYAN L ; carlos.goncal...@neclab.eu
Cc: Xueyifei (Yifei Xue) ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] congress support in compass4nfv

1.Hi, I am from compass4nfv team and see your Jira 
COMPASS-367<https://jira.opnfv.org/browse/COMPASS-367>. We can integrate 
congress into compass4nfv using ansible and want to check few things with you :

1.   How would you like to use congress? You just use its function or you 
have things based on it.

2.   Do you need a single congress scenario or a scenario with congress and 
what roles this scenario should have.

Best regards
Herry Huang

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

[opnfv-tech-discuss] [Models] Agenda for 2016-Oct-10 Models Project Meeting #14

[SULLIVAN, BRYAN L]

* Status of current work
* * VNFMs in testing
* * VNFM support planned
* Planning for Danube
* Upcoming events
* * OpenStack Barcelona demos / hackfest sessions
* * Plugfest use cases (reference VNFs)
* Next week
* * Cloudify/ARIA discussion
See https://wiki.opnfv.org/display/models/Models+Meetings for details.
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] OPNFV SPC Polestar WG Call 10/6/2016

[SULLIVAN, BRYAN L]

Sounds ok to me, but we need to ensure that project proposal discussions can 
take priority, and that we move them efficiently thru the process.

On Oct 10, 2016, at 3:19 AM, Margaret Chiosi 
mailto:margaretchiosi.o...@gmail.com>> wrote:

Folks we will switch to every other week when there are technical topics to 
discuss. Bin doesn't think there are enough topics to run every other week. 
Basically polestar will take the week sessions which Bin's sessions doesn't use.

On Monday, October 10, 2016, Christopher Price 
mailto:chrispric...@gmail.com>> wrote:
Hi Folks,

I think we may want to think a little loner on this.
I tend to agree that we have overlap in interested parties between the 
tech-discuss calls and Polestar which is good and healthy, but I don’t see that 
they serve such a common purpose that we would cancel tech-discuss to schedule 
a polestar meeting.  What happens if someone wants to review a project or 
technical contribution that week?  I don’t think we should offset the only 
general purpose community call we have established.

A longer term solution to this may be to find an alternative time for Polestar 
or accept that it may run in parallel to the community meetings.

/ Chris


From: 
>
 on behalf of Margaret Chiosi 
>
Date: Sunday, 9 October 2016 at 20:36
To: "HU, BIN" >
Cc: TECH-DISCUSS OPNFV 
>
Subject: Re: [opnfv-tech-discuss] OPNFV SPC Polestar WG Call 10/6/2016

Bin ok.
Min let's cancel next Thursday.

On Saturday, October 8, 2016, HU, BIN 
> wrote:
Sure. I am very happy to have you have the following week (Oct 20).

Because there is not many new project proposals or community issues to discuss 
now, essentially you may have most of weeks down the road. If there are new 
proposals or other community issues for discussion, I will let you and Min know 
and we may have alternate weeks.

What do you think?

Thanks
Bin

From: Margaret Chiosi [mailto:margaretchiosi.o...@gmail.com]
Sent: Saturday, October 08, 2016 12:48 PM
To: HU, BIN 
Cc: Ulrich Kleber ; Raymond Paik 
; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] OPNFV SPC Polestar WG Call 10/6/2016

So when is your next call? also if you have one next week then can you let me 
have my polestar the following week? thanks
On Oct 7, 2016, at 1:13 PM, HU, BIN  wrote:

Thank you Margaret.

Let’s coordinate in the future if many people intend to participate in both.

Thanks
Bin

From: Margaret Chiosi [mailto:margaretchiosi.o...@gmail.com]
Sent: Friday, October 07, 2016 2:58 AM
To: Ulrich Kleber 
Cc: HU, BIN ; Raymond Paik ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] OPNFV SPC Polestar WG Call 10/6/2016

Sure we can cancel our call if there is the true hbical community call. Bin 
just needs to coordinate with me and min.

On Friday, October 7, 2016, Ulrich Kleber  wrote:
I think we should consider the overlap with the technical community call.
It is not only about GTM accounts, but about people. There are several people 
who want to participate in both.
Can we still solve this?
(sorry, I forgot to raise it during the call due to the lively discussion on 
terminology and scope of “onboarding”)
Cheers,
Uli

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org]On
 Behalf Of HU, BIN
Sent: Thursday, 06 October, 2016 23:51
To: Raymond Paik
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] OPNFV SPC Polestar WG Call 10/6/2016

Sounds good, and thank you Ray

Bin
From: Raymond Paik [mailto:rp...@linuxfoundation.org]
Sent: Thursday, October 06, 2016 2:49 PM
To: HU, BIN 
Cc: Wenjing Chu ; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] OPNFV SPC Polestar WG Call 10/6/2016

Bin,

It's a separate one (username: commit...@opnfv.org) from the project calls so 
there shouldn't be conflicts with the technical discussion meeting on Thursday.

Thanks,

Ray

On Thu, Oct 6, 2016 at 2:43 PM, HU, BIN  wrote:
Ray,

What is the GTM account Polestar WG regularly uses?

I see the time overlap with technical discussion on Oct 13. We use the initial 
GTM account in weekly technical discussion on Oct 13.

Thanks
Bin

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Raymond Paik
Sent: Thursday, October 06, 2016 12:19 PM
To: Wenjing Chu 

Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] OPNFV SPC Polestar WG Call 10/6/2016

All,

Apologies for the inconvenience.  We realized late last night that Polestar was 
using the same GTM account as the Board meeting and there's an overlap between 
Polestar & Board meeting.

This won't be the case going forward...

Thanks,

Ray

On Thu, Oct 6, 2016 at 10:25 AM, Wenjing Chu  wrote:
Same disappointment for me.

The wiki also incorrectly listed the meeting on Oct 5. I was left wondering 
whether I missed the meeting because of wrong date. I didn't think it could be 
because of wrong bridge.

Wenjing

-

[opnfv-tech-discuss] [MANO] Discussion of how to include MANO stack components into scenarios

[SULLIVAN, BRYAN L]

Hi all,

Cross-posting as not all may be on the MANO-WG list yet. Subscribe here: 
https://lists.opnfv.org/mailman/listinfo/mano-wg

As noted today on the IRC for the Infra call:
bryan_att> Bryan Sullivan 
#info We 
should have a discussion on the MANO WG re the need for scenarios for MANO 
testing. IMO as noted we should have no direct dependency upon any scenario. 
MANO components can be installed and uninstalled, replaced, etc dynamically as 
part of test scripts or post-install scripts.
 Bryan Sullivan 
#info As 
noted in the Models project we will be doing this for a variety of MANO stack 
components, both to install them (a reusable capability) and then to test them 
for specific features e.g. TOSCA blueprint compatibility, from onboarding, 
deployment, lifecycle management, etc.
8:49 AM 
#info So 
far we have developed support for Tacker and Cloudify, and OpenBaton, 
ARIA+JuJu, OSM, etc all can be addressed if we have time resources. These 
should all run on any scenario.
 
#info How 
to handle MANO can be discussed within MANO WG and MANO WG can come up with a 
common way of handling these
8:50 AM
 Bryan Sullivan 
#info and 
of course, very soon (I hope) OpenECOMP!

* I started a MANO WG wiki page for the discussion at Integrating MANO 
Components in 
OPNFV.
 Some initial thoughts are shown there in a table that we can co-edit:
Goal

Assumption/Rationale/Exceptions

Comments

MANO stack component integration does not require new scenarios

VIM NBI provide a clean interface allowing MANO stack components to be added 
post-deploy, e.g. as we do today with vIMS, or as the Models project is doing 
for various VNFM/NFVO components. Exceptions might include MANO projects that 
depend (for some unclear/poor reason!) on a specific version/fork of a VIM.



Multiple MANO stack components can coexist in a single OPNFV deploy

MANO components, even those that offer the same/overlapping functions, can 
coexist as NBI consumers on OPNFV. Good use cases for this include interim 
phases toward a truly converged future, in which a SP may need to use various 
VNFMs that work with a particular VNF/service modeling toolset. In that case 
multiple MANO component deployment will be expected to work.



*
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] congress support in compass4nfv

[SULLIVAN, BRYAN L]

Email is OK, but you can also edit the Copper wiki at 
https://wiki.opnfv.org/display/copper/Installer+Support or provide a link to 
where you are describing the work on your wiki or JIRA. I'll also try to 
capture the status there as it gets developed.

Thanks,
Bryan Sullivan | AT&T

From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: Tuesday, October 11, 2016 6:45 PM
To: Carlos Goncalves ; huangxiangyu 

Cc: Xueyifei (Yifei Xue) ; 
opnfv-tech-discuss@lists.opnfv.org; SULLIVAN, BRYAN L 
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

OK, I got all your needs now. I also understand congress is an important 
component and agree that it should be appear in all scenarios. We are making 
some adjustment about our ansible now and I will suggest to add congress into 
the common part. Compass4nfv support offline installation so now I am working 
on adding congress debs. I will update you our progress on this thread.

Best regards
Herry Huang

From: Carlos Goncalves [mailto:carlos.goncal...@neclab.eu]
Sent: Sunday, October 09, 2016 5:50 PM
To: huangxiangyu
Cc: Xueyifei (Yifei Xue); 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
SULLIVAN, BRYAN L
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

Hi Henry,

Thanks for working on adding Congress support to Compass!

>From the Doctor side, we also just need Congress installed as a base service 
>available in all Compass scenarios.
There are no patches needing to be backported if Compass in Danube releases 
with OpenStack Newton or later.

Thanks,
Carlos

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: 09 October 2016 05:24
To: 'huangxiangyu'; Carlos Goncalves
Cc: Xueyifei (Yifei Xue); 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

Hi Herry,

Glad to be working with Compass on in this!

Congress should be installed as a basic service that is available in all 
Compass scenarios. This is what we did for Apex and JOID. There's no need for a 
specific scenario.

You can see they types of policy use cases that are in development for Congress 
at https://wiki.opnfv.org/display/copper/testing. The test cases shown there 
are integrated into Functest.

The Doctor project also depends upon Congress for some of its features.

I have an existing Ansible 
module<https://git.opnfv.org/cgit/copper/tree/components/congress/install/ansible>
 in the copper repo, that needs to be updated since I moved to a simple 
bash-script 
approach<https://git.opnfv.org/cgit/copper/tree/components/congress/install/bash>
 back in Brahmaputra, and then worked with the JOID and Apex teams on their 
installer tools (JuJu and Puppet). We can talk about updating that script at 
some meeting if you want to set it up. We don't have regular meetings in Copper 
at this time.

Thanks,
Bryan Sullivan | AT&T

From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: Friday, October 07, 2016 9:26 PM
To: SULLIVAN, BRYAN L mailto:bs3...@att.com>>; 
carlos.goncal...@neclab.eu<mailto:carlos.goncal...@neclab.eu>
Cc: Xueyifei (Yifei Xue) mailto:xueyi...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] congress support in compass4nfv

1.Hi, I am from compass4nfv team and see your Jira 
COMPASS-367<https://jira.opnfv.org/browse/COMPASS-367>. We can integrate 
congress into compass4nfv using ansible and want to check few things with you :

1.   How would you like to use congress? You just use its function or you 
have things based on it.

2.   Do you need a single congress scenario or a scenario with congress and 
what roles this scenario should have.

Best regards
Herry Huang

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

[opnfv-tech-discuss] Any graphic for an overview of Colorado senarios?

[SULLIVAN, BRYAN L]

It would be useful in promoting how OPNFV is benefitting the ecosystem if there 
was a graphic that provides an overview of the scenarios supported in Colorado. 
Does anyone have that, or something we could use as a basis?

The table at https://wiki.opnfv.org/display/SWREL/Colorado+Scenario+Status is 
very informative to those that already understand the scenario concept, but we 
probably need some more visual/abstracted expression to get the message out 
further.

I appreciate any help on this.

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

[opnfv-tech-discuss] [Copper] Danube Release Plan and Call for Participation

[SULLIVAN, BRYAN L]

Hi all,

This is going out to anyone that wants to contribute to, follow, or will be 
interacting with the Copper project in Danube. The wiki page 
https://wiki.opnfv.org/display/copper/Release+Plan and JIRA Kanban board 
https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=137&projectKey=COPPER 
have been updated and will be finalized for this release by the end of next 
week. Here's a summary of the plans:

* Deployment support via Fuel, for all scenarios, with Functest 
integration.

* Upstreaming current installer support via JuJu and Puppet.

* Deployment support via Compass, for all scenarios, with Functest 
integration.

* Deployment of the Congress Horizon plugin.

* HA support for the Congress service.

* Additional policy test use cases.

* Dovetail integration for Congress test cases.

* Further development of the Congress test webapp, e.g. library of 
policies with application via the Congress REST API.

* Further integration of Congress as a service supporting other OPNFV 
projects, as desired by those projects, e.g.

oVES: integration of Congress with the VES Collector, through a VES 
database driver.
I encourage your review and expression of intent to participate (especially my 
co-committers!), where possible. I'll even be happy to pass the PTL role off to 
whoever has the hankering to take it on... not much overhead really, and you 
can be sure that I'll still be driving specific work forward on the project as 
a committer. If you want to get some experience as PTL and collaborate actively 
on this project, let me know. Otherwise I will continue in that role.

Also - Aimee Ukasick (who has joined my team at AT&T) will be getting involved 
with mostly upstream focus on some of the Congress items. Please join me in 
welcoming Aimee to the project! She will be at the OpenStack Barcelona event 
with a slot speaking at the Women of OpenStack meetup, and getting to know the 
OPNFV team who is there.

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] Any graphic for an overview of Colorado senarios?

[SULLIVAN, BRYAN L]

As a quick way to have an overview of the scenarios, I added the page 
Colorado-Compact Table of 
Scenarios<https://wiki.opnfv.org/display/SWREL/Colorado-Compact+Table+of+Scenarios>
I suggest creating a similar page for Danube.

I would also like to find a useful graphic way to show this.

Thanks,
Bryan Sullivan | AT&T

From: morgan.richo...@orange.com [mailto:morgan.richo...@orange.com]
Sent: Friday, October 14, 2016 2:11 AM
To: Yingjun Li ; SULLIVAN, BRYAN L ; 
opnfv-tech-discuss@lists.opnfv.org; opnfv-marketing-commit...@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Any graphic for an overview of Colorado 
senarios?

Hi Yingjun

regarding scenarios
- a wiki page describing the naming: 
https://wiki.opnfv.org/display/INF/CI+Scenario+Naming
- see also section "Automated testing" in 
http://artifacts.opnfv.org/functest/colorado/docs/userguide/index.html

each version lists the candidate scenarios
- colorado: https://wiki.opnfv.org/display/SWREL/Colorado+Scenario+Status
- danube: https://wiki.opnfv.org/display/SWREL/Danube+Scenario+Status

installation description is under the responsibilty of the scenario owner
you may find info in the installer documentation (apex, compass, fuel, joid) => 
see for colorado https://wiki.opnfv.org/display/DOC/Colorado+documentation

regaring the criteria to add a new one, my view is
- first check if you cannot use an existing one, there are lots of generic 
scenarios that feature projects may join
- if it is not possible to join a "generic" scenario you can become the owner 
of a new "specific" scenario, then you have to complete the wiki page and will 
in charge of this scenario, it means you will have to ask for ressources to 
Infra group (need CI time with installer X), contact testing group to define 
the tests you want to run towards the scenario (in addition of your own tests)

you can have a view of the scenarios from testing perspective throught he 
automatic reporting pages we created (you can have a view per version/installer
functest colorado: 
http://testresults.opnfv.org/reporting/functest/release/colorado/index-status-apex.html
functest master: 
http://testresults.opnfv.org/reporting/functest/release/master/index-status-compass.html
yardstick colorado: 
http://testresults.opnfv.org/reporting/yardstick/release/colorado/index-status-joid.html
yardstick master: 
http://testresults.opnfv.org/reporting/yardstick/release/master/index-status-fuel.html

/Morgan

13/10/2016 à 19:51, Yingjun Li a écrit :
Hi Bryan

That is a pretty good suggestion. I myself is relatively new to OPNFV scenario 
and trying to understand it more deeply. If we have a dedicated wiki page 
talking about scenario (naming, config, document, criteria for adding new 
one...), that will be beneficial to anyone, especially for MANO projects.

Thanks
Yingjun


From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Thursday, October 13, 2016 8:33 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
opnfv-marketing-commit...@lists.opnfv.org<mailto:opnfv-marketing-commit...@lists.opnfv.org>
Subject: [opnfv-tech-discuss] Any graphic for an overview of Colorado senarios?

It would be useful in promoting how OPNFV is benefitting the ecosystem if there 
was a graphic that provides an overview of the scenarios supported in Colorado. 
Does anyone have that, or something we could use as a basis?

The table at https://wiki.opnfv.org/display/SWREL/Colorado+Scenario+Status is 
very informative to those that already understand the scenario concept, but we 
probably need some more visual/abstracted expression to get the message out 
further.

I appreciate any help on this.

Thanks,
Bryan Sullivan | AT&T





___

opnfv-tech-discuss mailing list

opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>

https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss




--

Morgan Richomme

Orange/ IMT/ OLN/ CNC/ NCA/ SINA



Network architect for innovative services

Future of the Network community member

Open source Orange community manager





tel. +33 (0) 296 072 106

mob. +33 (0) 637 753 326

morgan.richo...@orange.com<mailto:morgan.richo...@orange.com>

_



Ce message et ses pieces jointes peuvent contenir des informations 
confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce 
message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages 
electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a e

[opnfv-tech-discuss] [Models] Agenda for 2016-Oct-17 Models Project Meeting #15

[SULLIVAN, BRYAN L]

* Agenda:
*
* Status of current work
* Planning for Danube
* Cloudify/ARIA discussion
* Upcoming events
* Next week
See https://wiki.opnfv.org/display/models/Models+Meetings for details.
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] Updated Invitation: OPNFV SPC Polestar WG Call @ Thu Oct 20, 2016 10am - 11am (CDT) (m...@linuxfoundation.org)

[SULLIVAN, BRYAN L]

Per Chris Price’s request I added some “how do I get involved” info to the 
Models project wiki: https://wiki.opnfv.org/display/models/Models+Home
Chris, let me know if that will help anyone who has ideas for the Models 
project and wants to get involved.

For anyone who will be at OpenStack, I can spend some time to demo the current 
work and show you in detail what’s been done and what is planned. AT&T will 
have a booth in the Marketplace, and I will send out a note today or tomorrow 
on the schedule for demos at that booth and in the Marketplace Theater. We can 
also do this at any OPNFV meetups that give us a place to do demos.

Thanks,
Bryan Sullivan | AT&T


-Original Appointment-
From: m...@linuxfoundation.org [mailto:m...@linuxfoundation.org]
Sent: Wednesday, October 19, 2016 11:33 AM
To: m...@linuxfoundation.org; prodip@hpe.com; dmcbr...@linuxfoundation.org; 
zhangyujun+...@gmail.com; anthony.so...@huawei.com; pyeg...@juniper.net; 
SULLIVAN, BRYAN L; paul...@emc.com; ulrich.kle...@huawei.com; Raymond Paik; 
hkirk...@linuxfoundation.org; john.v.he...@intel.com; 
christopher.pr...@ericsson.com; sandra.l.riv...@intel.com; 
opnfv-tech-discuss@lists.opnfv.org; FORD, TOBY; WRIGHT, STEVEN A; 
margaretchiosi.o...@gmail.com; dick.c...@ztetx.com; fbroc...@cisco.com; 
dne...@redhat.com; bob.monk...@arm.com; jonne.soini...@nokia.com; 
cyo...@clearpathnet.com
Subject: Updated Invitation: OPNFV SPC Polestar WG Call @ Thu Oct 20, 2016 10am 
- 11am (CDT) (m...@linuxfoundation.org)
When: Thursday, October 20, 2016 10:00 AM-11:00 AM America/Chicago.
Where: https://global.gotomeeting.com/join/158053245


This event has been changed.
more details 
»<https://www.google.com/calendar/event?action=VIEW&eid=ZTcxcmxiaDRyMm1yMzk1bzVtMnBxdWY0c29fMjAxNjEwMjBUMTMwMDAwWiBiczMxMzFAYXR0LmNvbQ&tok=MjMjbXl1QGxpbnV4Zm91bmRhdGlvbi5vcmc0ZjZkMzdhYzFlNTM0MTg1ODVmNTQ0MDA5MTA3YWJhYzg5MTgwMmJl&ctz=America/Chicago&hl=en>

OPNFV SPC Polestar WG Call
OPNFV SPC Polestar WG Call

Please join my meeting from your computer, tablet or smartphone.
https://global.gotomeeting.com/join/158053245<https://www.google.com/url?q=https%3A%2F%2Fglobal.gotomeeting.com%2Fjoin%2F158053245&sa=D&usd=2&usg=AFQjCNFIlaJBPZNXlROtHjuKSxeb6XuW1w>
You can also dial in using your phone.
United States +1 (571) 317-3116
United States (Toll-free) 1 877 309 2070
Access Code: 158-053-245
More phone numbers
Australia +61 2 8355 1034
Austria +43 7 2088 0716
Belgium +32 (0) 28 93 7002
Canada +1 (647) 497-9372
Denmark +45 69 91 84 58
Finland +358 (0) 923 17 0556
France +33 (0) 170 950 590
Germany +49 (0) 692 5736 7206
Ireland +353 (0) 19 030 053
Italy +39 0 699 26 68 65
Netherlands +31 (0) 208 080 759
New Zealand +64 9 974 9579
Spain +34 931 76 1534
Sweden +46 (0) 852 500 691
Switzerland +41 (0) 435 0026 89
United Kingdom +44 (0) 20 3713 5011
First GoToMeeting? Try a test session: 
http://help.citrix.com/getready<https://www.google.com/url?q=http%3A%2F%2Fhelp.citrix.com%2Fgetready&sa=D&usd=2&usg=AFQjCNFfzseVEuxj21268l9npyfmpQPnbQ>





When
Changed: Thu Oct 20, 2016 10am – 11am Central Time

Where
https://global.gotomeeting.com/join/158053245 
(map<https://www.google.com/url?q=https%3A%2F%2Fglobal.gotomeeting.com%2Fjoin%2F158053245&sa=D&usd=2&usg=AFQjCNFIlaJBPZNXlROtHjuKSxeb6XuW1w>)

Calendar
m...@linuxfoundation.org

Who
•
m...@linuxfoundation.org - organizer

•
prodip@hpe.com

•
dmcbr...@linuxfoundation.org

•
zhangyujun+...@gmail.com

•
anthony.so...@huawei.com

•
pyeg...@juniper.net

•
bs3...@att.com

•
paul...@emc.com

•
ulrich.kle...@huawei.com

•
Raymond Paik

•
hkirk...@linuxfoundation.org

•
john.v.he...@intel.com

•
christopher.pr...@ericsson.com

•
sandra.l.riv...@intel.com

•
opnfv-tech-discuss@lists.opnfv.org

•
tf4...@att.com

•
sw3...@att.com

•
margaretchiosi.o...@gmail.com

•
dick.c...@ztetx.com

•
fbroc...@cisco.com

•
dne...@redhat.com

•
bob.monk...@arm.com

•
jonne.soini...@nokia.com

•
cyo...@clearpathnet.com



Going?   
Yes<https://www.google.com/calendar/event?action=RESPOND&eid=ZTcxcmxiaDRyMm1yMzk1bzVtMnBxdWY0c29fMjAxNjEwMjBUMTMwMDAwWiBiczMxMzFAYXR0LmNvbQ&rst=1&tok=MjMjbXl1QGxpbnV4Zm91bmRhdGlvbi5vcmc0ZjZkMzdhYzFlNTM0MTg1ODVmNTQ0MDA5MTA3YWJhYzg5MTgwMmJl&ctz=America/Chicago&hl=en>
 - 
Maybe<https://www.google.com/calendar/event?action=RESPOND&eid=ZTcxcmxiaDRyMm1yMzk1bzVtMnBxdWY0c29fMjAxNjEwMjBUMTMwMDAwWiBiczMxMzFAYXR0LmNvbQ&rst=3&tok=MjMjbXl1QGxpbnV4Zm91bmRhdGlvbi5vcmc0ZjZkMzdhYzFlNTM0MTg1ODVmNTQ0MDA5MTA3YWJhYzg5MTgwMmJl&ctz=America/Chicago&hl=en>
 - 
No<https://www.google.com/calendar/event?action=RESPOND&eid=ZTcxcmxiaDRyMm1yMzk1bzVtMnBxdWY0c29fMjAxNjEwMjBUMTMwMDAwWiBi

[opnfv-tech-discuss] [VES] Demo at OpenStack Barcelona

[SULLIVAN, BRYAN L]

Hi all,
I will be giving demos of the VES project code as it stands, on the following 
schedule at the AT&T sponsor booth in the marketplace:

TIME

TUESDAY

WEDNESDAY

THURSDAY

10:00-11:00

Bryan

11:00-12:00

Bryan (10:45-11:45)

12:00-1:00

1:00-2:00

Bryan

2:00-3:00

Bryan

Bryan

3:00-4:00

4:00-5:00

Bryan

5:00-6:00

Bryan, Bin (Gluon at Theater)

6:00-6:30


It would be great if you can drop by the booth,  or tell others to. Here are 
some other details:

-  The Hello VES Demo 
page has been updated for 
the latest demo design and features

-  I created a flyer to handout at the booth:  
VES_Demo_Flyer.pdf
 - handy as a one page overview of the VES project

-  I created a video of the demo (just in case...): 
https://www.youtube.com/watch?v=0ZQPU947E2Q

Many thanks to Maryam and Intel for their development effort on the collectd 
plugin, which is the 
strongest part of the demo honestly.

Also there are some great collaboration opportunities presented by what we've 
learned so far with VES (e.g. integrating with dashboards and closed-loop 
monitoring frameworks which can use the VES-collected data, and integrating the 
VES data with OpenStack services or other OPNFV projects) so I look forward to 
discussing them with you and the attendees.

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] Support for multi-site development and testing

[SULLIVAN, BRYAN L]

In particular as discussed today on the Domino call:

-  What Pharos lab environments do you use for any multi-site testing

-  What multi-site-distributed VNF use cases have you worked on, and 
related aspects such as how you create the inter-VNF networking per VNF 
connection points

-  What if any "site agents" you are working on that aggregate 
site-related state etc and sync that with some multi-site "master" function 
(e.g. a global orchestrator or monitoring system)

These are all topics that are in scope for Domino to some degree.

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ulas Kozat
Sent: Monday, October 31, 2016 7:19 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Support for multi-site development and testing

Hi everyone,

Is anyone in the community working towards a real multi-site development and 
testing environment?

I created a link under MANO WG 
https://wiki.opnfv.org/display/mano/Multi-Site+Support so that we can aggregate 
use cases from different projects in one place. Please pitch in.

It would be also interesting to learn how any of the existing OPNFV projects 
(e.g., multisite, IPv6, etc.) had circumvented their multi-site needs for 
testing and development.

Regards,

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

Re: [opnfv-tech-discuss] congress support in compass4nfv

[SULLIVAN, BRYAN L]

Hi Harry,

Can you drop a console log or other details on the process you are using to IRC 
(#opnfv-copper) or on an etherpad somethere etc? I need to understand where you 
are getting the Congress code (e.g. "congress debs") and what 
environment/process you are using to install it. I'm not familiar with antlr 
and don't know what role it might have in the install. But I can probably 
figure it out with more info.

Thanks,
Bryan Sullivan | AT&T

From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: Wednesday, October 26, 2016 8:28 PM
To: SULLIVAN, BRYAN L ; Carlos Goncalves 

Cc: Xueyifei (Yifei Xue) ; 
opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

Hi, I encounter some problem when I start congress-server after I installed 
congress using congress debs: when I used antlr V3.0.1 runtime returns 
"ParserRuleReturnScope  is not defined" error while  other antlr  runtime has 
ANTLR version mismatch problem saying 'The recognizer has been generated by 
V3.0.1. Please use the V3.0.1 runtime '. So which antlr runtime should I use?

Thanks
Harry huang


From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: Thursday, October 13, 2016 1:19 AM
To: huangxiangyu; Carlos Goncalves
Cc: Xueyifei (Yifei Xue); 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

Email is OK, but you can also edit the Copper wiki at 
https://wiki.opnfv.org/display/copper/Installer+Support or provide a link to 
where you are describing the work on your wiki or JIRA. I'll also try to 
capture the status there as it gets developed.

Thanks,
Bryan Sullivan | AT&T

From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: Tuesday, October 11, 2016 6:45 PM
To: Carlos Goncalves 
mailto:carlos.goncal...@neclab.eu>>; huangxiangyu 
mailto:huangxiang...@huawei.com>>
Cc: Xueyifei (Yifei Xue) mailto:xueyi...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
SULLIVAN, BRYAN L mailto:bs3...@att.com>>
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

OK, I got all your needs now. I also understand congress is an important 
component and agree that it should be appear in all scenarios. We are making 
some adjustment about our ansible now and I will suggest to add congress into 
the common part. Compass4nfv support offline installation so now I am working 
on adding congress debs. I will update you our progress on this thread.

Best regards
Herry Huang

From: Carlos Goncalves [mailto:carlos.goncal...@neclab.eu]
Sent: Sunday, October 09, 2016 5:50 PM
To: huangxiangyu
Cc: Xueyifei (Yifei Xue); 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
SULLIVAN, BRYAN L
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

Hi Henry,

Thanks for working on adding Congress support to Compass!

>From the Doctor side, we also just need Congress installed as a base service 
>available in all Compass scenarios.
There are no patches needing to be backported if Compass in Danube releases 
with OpenStack Newton or later.

Thanks,
Carlos

From: SULLIVAN, BRYAN L [mailto:bs3...@att.com]
Sent: 09 October 2016 05:24
To: 'huangxiangyu'; Carlos Goncalves
Cc: Xueyifei (Yifei Xue); 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: RE: [opnfv-tech-discuss] congress support in compass4nfv

Hi Herry,

Glad to be working with Compass on in this!

Congress should be installed as a basic service that is available in all 
Compass scenarios. This is what we did for Apex and JOID. There's no need for a 
specific scenario.

You can see they types of policy use cases that are in development for Congress 
at https://wiki.opnfv.org/display/copper/testing. The test cases shown there 
are integrated into Functest.

The Doctor project also depends upon Congress for some of its features.

I have an existing Ansible 
module<https://git.opnfv.org/cgit/copper/tree/components/congress/install/ansible>
 in the copper repo, that needs to be updated since I moved to a simple 
bash-script 
approach<https://git.opnfv.org/cgit/copper/tree/components/congress/install/bash>
 back in Brahmaputra, and then worked with the JOID and Apex teams on their 
installer tools (JuJu and Puppet). We can talk about updating that script at 
some meeting if you want to set it up. We don't have regular meetings in Copper 
at this time.

Thanks,
Bryan Sullivan | AT&T

From: huangxiangyu [mailto:huangxiang...@huawei.com]
Sent: Friday, October 07, 2016 9:26 PM
To: SULLIVAN, BRYAN L mailto:bs3...@att.com>>; 
carlos.goncal...@neclab.eu<mailto:carlos.goncal...@neclab.eu>
Cc: Xueyifei (Yifei Xue) mailto:xueyi...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-te

Re: [opnfv-tech-discuss] Support for multi-site development and testing

[SULLIVAN, BRYAN L]

Yes, that’s specifically what I intend – i.e. not to duplicate rather leverage 
any existing work there. I recommend that at least one member of these projects 
attend the MANO WG meeting as a common place for us to discuss cross-project 
needs such as this. The biggest issue in OPNFV re this is that we have so many 
discrete meetings with little cross-project discussion. We are trying to 
address that in the MANO WG.

Thanks,
Bryan Sullivan | AT&T

From: Christopher Price [mailto:chrispric...@gmail.com]
Sent: Monday, October 31, 2016 8:44 AM
To: SULLIVAN, BRYAN L ; Ulas Kozat ; 
opnfv-tech-discuss@lists.opnfv.org; Dimitri Mazmanov 

Subject: Re: [opnfv-tech-discuss] Support for multi-site development and testing

Hi Folks,

Why would this not be done in the multisite project?  
https://wiki.opnfv.org/display/multisite/

They have already done a lot of work on multisite services and began testing in 
Colorado, they are limited in progress only by the number of resources engaged 
at the moment I think.  Rather than spin up a new initiative or wiki page in 
parallel to spread us even thinner I would suggest coordinating and driving our 
solutions in that project.

/ Chris

From: 
mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>>
 on behalf of "SULLIVAN, BRYAN L" mailto:bs3...@att.com>>
Date: Monday, 31 October 2016 at 16:27
To: Ulas Kozat mailto:ulas.ko...@huawei.com>>, 
TECH-DISCUSS OPNFV 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: Re: [opnfv-tech-discuss] Support for multi-site development and testing

In particular as discussed today on the Domino call:

-  What Pharos lab environments do you use for any multi-site testing

-  What multi-site-distributed VNF use cases have you worked on, and 
related aspects such as how you create the inter-VNF networking per VNF 
connection points

-  What if any “site agents” you are working on that aggregate 
site-related state etc and sync that with some multi-site “master” function 
(e.g. a global orchestrator or monitoring system)

These are all topics that are in scope for Domino to some degree.

Thanks,
Bryan Sullivan | AT&T

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ulas Kozat
Sent: Monday, October 31, 2016 7:19 AM
To: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [opnfv-tech-discuss] Support for multi-site development and testing

Hi everyone,

Is anyone in the community working towards a real multi-site development and 
testing environment?

I created a link under MANO WG 
https://wiki.opnfv.org/display/mano/Multi-Site+Support so that we can aggregate 
use cases from different projects in one place. Please pitch in.

It would be also interesting to learn how any of the existing OPNFV projects 
(e.g., multisite, IPv6, etc.) had circumvented their multi-site needs for 
testing and development.

Regards,

Ulas Kozat
Domino PTL
___ opnfv-tech-discuss mailing list 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> 
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Models] 2016-Oct-31 Models Project Meeting #16 Minutes

[SULLIVAN, BRYAN L]

2016-Oct-31 Models Project Meeting #16
Attendees:

  *   Bryan Sullivan, AT&T
  *   Prakash Ramchandran, Huawei
  *   Larry Lamers, VMWare
  *   Dan Druta, AT&T
Agenda/Minutes:

  *   Dec Plugfest planning
 *   Finalize this week:
*   Who can bring VNFs/VNFMs
   *   vIMS in Open-O and OSM via JuJu
*   Who is ready to test against Models "Hello World" blueprint
*   Get confirmations of attendance (in person, virtual) this week
  *   Planning for Danube
 *   Complete JIRA: 
https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=139&projectKey=MODELS
 *   Will be closed this week if no more comments
 *   Functest strategy needs further discussion
 *   Role of YANG vs TOSCA, e.g. in OSM
*   YANG appears to be used as a modeling tool, but the artifacts (NDS, 
VNFD) are in YAML format - how this relates to YANG or TOSCA is TBD
*   https://osm.etsi.org/wikipub/index.php/Release_0_Data_Model_Details
*   
https://osm.etsi.org/wikipub/index.php/Release_ONE_Data_Model_details
  *   Recent events
 *   OpenStack Barcelona demos / hackfest sessions
*   Collecting best links from demos etc on the Models wiki
*   Doctor/Vitrage/Models
*   Domino
*   VES
 *   TSC/BoD takeaways
*   "Architecture of OPNFV" re CVP program and goals for what we can 
claim in 1st release of CVP
   *   Where how this will be addressed is TBD
   *   MANO WG should be a good venue for it
   *   Prakash has a draft diagram; some open issues e.g. underlay 
arrangement, service assurance
   *   Dan: 2 levels i.e. VNF and service; testing discussions should 
clarify the VNF and service design handoff, and that VNFs are reusable; both 
VNFs and services can be onboarded. Tacker as an example has this distinction 
and two separate catalogs for them.
*   MANO WG intro
   *   Few comments overall
   *   Clarified that the role of Models project is to "assess and 
advise"
   *   Send out a notice for the PM PST timeslot for Models; Prakash 
will send for MANO WG as well.
 *   Charmers meetup
*   Since JuJu is a common MANO stack element across projects, being 
familiar with its DSL is important
  *   Cross-project
 *   Movie project status
*   ONOS J release will have YANG model support
*   use cases include Virtual Private Cloud, L3VPN, vEPC, Bandwidth on 
Demand
*   ODL has NEMO project, being ported to ONOS by Movie project
  *   Upcoming
 *   Cloudify/ARIA discussion


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

[opnfv-tech-discuss] Dec Plugfest Planning

[SULLIVAN, BRYAN L]

Hi all,

Going out to OPNFV in general and specifically to those involved in the 
VNFM/NFVO projects OpenBaton, Tacker, Cloudify, ARIA, JuJu.

I'd like to get your confirmation this week as to whether your 
organization/projects will be able to support the OPNFV Colorado plugfest at 
UNH-IOL, Dec 5-9: 
https://wiki.opnfv.org/display/EVNT/Plugfest+-+Colorado+Release and 
specifically the VNF Portability tests as described on the wiki at 
https://wiki.opnfv.org/display/EVNT/Colorado+Plugfest+Test+Cases.  Since time 
is short for the event (1 month away) we need to quickly assess readiness for 
the event.

I updated the wiki to more completely explain the concept and option for the 
test scope:

VNF Portability Scope
Overall the focus of this test scope will be to demonstrate VNFM product degree 
of compatibility with standards-based, reference VNF blueprints, as installed 
on one or more OPNFV deployment scenarios. It's expected that with the current 
generation of VNFMs, variations in blueprint schema support (e.g. 
product-specific extensions/limitations) will require customization of the 
blueprints, VNF images, or related support scripts. The reference VNF 
blueprints will be provided in advance, so that VNFM projects can prepare any 
needed customizations. Specific goals for the testing are to demonstrate the 
degree of portability, uncover issues for followup, build the library of tested 
blueprints (VNFM-specific, as needed), and overall come away with a much 
clearer assessment of VNFM product support for blueprint standards. This 
initial plugfest will focus on:

  *   the onboading, deployment, and termination phases of the VNF lifecycle, 
as described on the MANO WG wiki at VNF 
Onboarding
  *   relatively basic blueprint attributes, e.g. basic resource topology and 
requirements
  *   potentially extending to further lifecycle stages (e.g. handing of 
in-service lifecycle events).
Future plugfests will address other lifecycle stages, more advanced blueprint 
attributes (e.g. policy), and service blueprints (e.g. composed of multiple 
VNFs with service chaining).
Other notes in advance:

  *   If you can't support it in person, we can likely do some remote testing 
as well.
  *   The test POD resources on the "Hello World" blueprint are pretty mild, 
doable in a virtual deploy.
  *   The more advanced blueprints may require a multi-node POD or a full POD. 
We will need PODs that we can use for them, for that week at least (and the 
prior week for any pre-testing).
  *   The tests we have prepared in the Models and VES projects depend upon 
JOID or Apex installs. You may have blueprints that work under other installs 
and that's fine. As noted below we can work to adapt the blueprints for testing 
also under the JOID and Apex deploys.
  *   Further VNFM support (ARIA/JuJu, OpenBaton) in the tests will be 
developed over the next few weeks - collaboration on that is welcome!

Hello World
Purpose:

  *   Assess portability of a very basic blueprint for a single/multi-node, 
multi-NIC web server.
Procedure:
See the examples for Tacker at 
vHello_Tacker.sh,
 and vHello_VES Demo which 
have the basic outline

  1.  VNFM is installed on the OPNFV system
  2.  Blueprint repo is cloned
  3.  Blueprint is imported into the onboarding system
  4.  Blueprint is started
  5.  Blueprint is functionally verified
  6.  Blueprint is terminated
  7.  Steps 4-6 are repeated several times without error or extra manual 
actions needed
Note that the blueprints above will be updated as needed to run in generic 
TOSCA VNFMs or for DSL-specific node types as needed). Let us know your 
specific VNFM's compatibility ahead of time and we can work to close any gaps 
in how it's supported.
Metrics / Expected Results:

  1.  Blueprint is successfully imported into the onboarding system (as 
applicable).
  2.  Blueprint is successfully deployed, including functional verification 
(web server responds as expected).
  3.  Blueprint is terminated and uninstalled successfully, leaving a clean 
system.
  4.  A minimal amount of blueprint functions require supplemental support, 
e.g. through scripts or image customization.

More Advanced VNFs
Purpose:

  *   Assess portability of more advanced VNF blueprints, as can be developed 
in advance of the plugfest, e.g.
 *   vIMS: Various versions of a vIMS blueprint have been indicated as 
supported by
*   Cloudify (Orange github 
version), as 
used in Functest. Note this depends upon an earlier version of Cloudify Manager 
and preferably would be updated to the current version before the plugfest
*   JuJu (Charm Store 
version, Metaswitch github 
version

[opnfv-tech-discuss] [VES] Team Meeting Schedule

[SULLIVAN, BRYAN L]

To all who want to participate in the VES project for Danube, here's an update.

* I've had some difficulty finding an open slot for any regular 
meetings. I would like to propose that we plan to get on the agenda for the 
MANO WG calls as shown below, to have quick verbal updates as needed on the 
project. That time should work for all timezones. We can consider some other 
slot if we need more time to talk, but that's challenging with the number of 
meetings we have in OPNFV.

* The project planning for Danube is at 
https://wiki.opnfv.org/display/ves/Project+Plan. Any comments to this plan 
should be received in JIRA (e.g. as edited or new items) or on the wiki (e.g. 
as new row entries in the plan table) by the end of this week.

* Activity in the git repo over the last few weeks have established a 
base of code for the demos e.g. as I did at OpenStack Barcelona, and other 
things

o   vHello_VES.sh: the 
base of the demo I gave (references 
tosca-vnfd-hello-ves
 in the blueprints folder and uses the 
tacker-setup.sh
 script from the Models repo). The demo video etc is shown on the page 
vHello_VES Demo

o   setenv.sh: in 
the utils folder, sets up the OpenStack environment etc for the tests

o   Other work in the repo

?  
vLamp_Ansible_VES.sh:
 work on getting the OpenStack Lampstack blueprint working. Was planned as the 
basis of the VES demo but a late change in the Lampstack blueprint cause this 
to stop working on OPNFV... so this will be revisited.

?  
VES_Reference.sh: 
initial work on getting the "VES Reference VNF" working - which I may abandon 
as I have now a real working demo as compared to this exploratory type 
"reference VNF" demo.

* I encourage the committers (cc'd) to watch the Gerrit 
project for patches that are 
being made to the code above. So far I've been pretty much merging patches as 
they are developed and tested without additional reviews. But your input on 
them is welcome, so if you want to start watching and commenting as needed I 
can slow down the merge process to enable that. But first please confirm by 
email that you will be participating actively as a committer, so I don't 
unnecessarily slow down development in the repo.

* I received a direct request a couple of weeks back from Liyuanzhen to 
be removed as committer and Dong wenjuan to be added in place. I have yet to 
see a specific request on that via the tech-discuss list, but just FYI that 
request is outstanding and when it comes thru I will start a vote of the 
committers on that.

* Finally: I have been pretty much acting as the PTL for this project. 
Though Alok was intended to take on that role, he's managing the team that is 
developing the internal implementation of VES for our service assurance team, 
so his time to lead this as PTL is limited. If anyone out there wants to get 
actively involved in the project and take on the PTL role, I'm sure we would 
appreciate that and support you!

FYI: OPNFV MANO WG Meeting Details
Meeting Times: Weekly 7 AM PDT (15:00 UTC) this week and 7 AM PST (14:00 UTC) 
after daylight changes next week
IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING: https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

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

[opnfv-tech-discuss] [Barometer][VES] Mapping monitored source data to backend interface/model items

[SULLIVAN, BRYAN L]

On the Barometer project (FKA SFQM) call today, I made the following suggestion 
that was welcomed by the team. Basically the Barometer project will be 
developing the "frontend" (i.e. agent) data source aspects of analytics 
collection (i.e. interfacing with hosts and VMs etc to collect analytics), and 
delivering it to "backends" (i.e. collectors such as VIMs/monitoring systems) 
via protocols such as REST/HTTP, Kafka, SNMP etc. I think this is a good 
development, as most of the frontend heavy lifting will be done in the collectd 
upstream, and specific projects in OPNFV such as Barometer and VES just need to 
take care of the mapping to the backend interfaces and data models.

To minimize development/maintenance of the mapping between the collectd plugin 
data sources and the specific backend protocol/data model, I suggested that we 
consider a mapping table as a static or manageable attribute of the 
configuration for the agent. For example, as you can see in Maryam's team 
implementation of the 
ves_plugin.py,
 values for the data source items are mapped to fields in the JSON-based VES 
message structure in individual code statements. Even in this early demo 
version, there are many monitored data items, and this can be expected to 
expand greatly. It would be nice if we can automate as much of this as possible 
through a table with rows such as:

{ plugin_name, plugin_instance, type_name, type_instance }, { 
domain.property.property.property... }

Theoretically, it should be possible in many cases to simply run thru such a 
table and copy the source data to the proper place in the target event 
structure. If calculations are needed on the source, they might still require a 
discrete statement, but many of the fields could be just copied. For target 
properties which are lists, that would need to be considered as well, but I 
think we could indicate that through some variable reference or "property[x]".

Any input on this idea, experience implementing such mapping systems etc, is 
appreciated.

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 #10 this Wendnesday Nov 2, 15.00 UTC (7.00 PDT)

[SULLIVAN, BRYAN L]

Hi all,

Cross-posting as this is a call to project teams beyond the MANO WG.

I encourage all PTLs in projects related to functions applicable above the VIM 
(see https://wiki.opnfv.org/display/mano/MANO+Project+Guidance for a draft 
list) to regularly attend the MANO WG calls, which will now be weekly and 
provide both a coordination venue and a place where specific projects can 
provide deep-dives on their plans/status and perceived role in the MANO stack, 
so we can all stay closer to the same page.

We can also add a second time more friendly to Asia if needed (e.g. the 00:00 
UTC Tuesday slot we have setup for Models, which so far has not been attended 
by anyone other than me :().

Also a note to anyone wanting an update on Copper, Models, and VES, I will 
provide a quick update as part of the ongoing MANO WG calls, focused on the 
cross-project important aspects.

Prakash, I want to add the above goal to the standing agenda, and also that the 
MANO WG members will fan-out to cover the various projects we have referenced 
above, to promote cross-project coordination. To do that we need to assess:

-  Which projects are active (visibly in some way)

-  Which projects have regular calls we can attend (evidenced by recent 
minutes etc on the wiki)

-  Who from the MANO WG should act as the advocate for that project (if 
not the project's PTL - people are busy...)

-  Who from the MANO WG can start actively supporting the work in the 
project (since that's the best way IMO to gain real attention...)

Also I want to add to the agenda a quick note on the Dec Plugfest planning for 
VNF testing and Portability.

Thanks,
Bryan Sullivan | AT&T

From: Prakash Ramchandran [mailto:prakash.ramchand...@huawei.com]
Sent: Tuesday, November 01, 2016 7:48 AM
To: opnfv-m...@lists.opnfv.org; Prakash Ramchandran 
; SULLIVAN, BRYAN L ; 
denglin...@chinamobile.com; giuseppe.care...@fokus.fraunhofer.de; Ulas Kozat 
; Yingjun Li ; 
artur.tyl...@canonical.com; dne...@redhat.com; sric...@gmail.com; 
bob.monk...@arm.com; christopher.pr...@ericsson.com; 
raghavendrachari.kams...@hpe.com; ljlam...@live.com; 
michael.k.bugenha...@centurylink.com; serge.mann...@sprint.com
Subject: FW: [mano-wg] [MANO] Meeting #10 this Wendnesday Nov 2, 15.00 UTC 
(7.00 PDT)

Forwarding as reminder for tomorrow's Wednesday MANO WG meeting 15 TC or 7 AM 
PDT...Thanks Prakash





From: Prakash Ramchandran
Sent: Tuesday, November 01, 2016 7:40 AM
To: 'opnfv-m...@lists.opnfv.org'
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: [mano-wg] [MANO] Meeting #10 this Wendnesday Nov 2, 15.00 UTC (7.00 
PDT)

FYI: OPNFV MANO WG Meeting Details

Meeting Times: Weekly 7 AM PDT (15:00 UTC) this week and 7 AM PST (14:00 UTC) 
after daylight changes next week

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045

Agenda of meeting November 2, 2016  14.00 UTC /7.00 PDT Meeting #10

1, Briefing on "State of MANO architecture" and feedback listed below.

MANO TSC-Board report and feedback
State of MANO in 
OPNFV-tsc-borad-october-28-2016.pdf<https://wiki.opnfv.org/download/attachments/6827111/State%20of%20MANO%20in%20OPNFV-tsc-borad-october-28-2016.pdf?version=1&modificationDate=1478009353911&api=v2>

2. Cross-Project Co-ordination for Danube and Assess the participation of MANO  
activities for UNHV Plugfest Dec 5-8

3. Functest through common test plans for MANO VNFM and NFVO  (Opera, 
Orchestra, and participating Projects)

4. Any topics of interests to upstream and Projects in OPNFV.
Thanks
Prakash


Prakash Ramchandran
[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@huawei.com<mailto:s.c...@huawei.com>
Work:  +1 (408) 330-5489
Mobile: +1 (408) 406-5810
2330 Central Expy, Santa Clara, CA 95050, USA






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

Re: [opnfv-tech-discuss] [availability] HA project weekly meeting

[SULLIVAN, BRYAN L]

Looks like we had connectivity issues, but I just wanted to drop a note that 
I'll do my best to participate going forward as this project is addressing a 
gap I believe, and as noted there will be some tangential at least relation to 
the other projects I'm involved in (Copper, Models, VES) as part of the overall 
management of control plane features that support e.g. application HA.

Ian, when you get the code https://github.com/Wind-River/titanium-server in the 
OPNFV git I'll add reviews if I have any expertise in what you're committing...

Thanks,
Bryan Sullivan | AT&T


-Original Appointment-
From: Fu Qiao [mailto:fuq...@chinamobile.com]
Sent: Sunday, October 30, 2016 8:50 PM
To: Fu Qiao; Ian; yuan@zte.com.cn; 'Waines, Greg'; 'Peng Liu'; 'Stefan 
Arntzen'; 'mathi.naickan'; 'jonas.arndt'; 'stpierre. edgar'; 
'opnfv-tech-discuss'
Subject: [opnfv-tech-discuss] [availability] HA project weekly meeting
When: Wednesday, November 02, 2016 9:00 PM-10:00 PM (UTC+08:00) Beijing, 
Chongqing, Hong Kong, Urumqi.
Where:


Minutes and Agenda:

https://wiki.opnfv.org/high_availability_project_meetings

Next Meeting on 13:00-14:00 UTC, Wednesday, Nov. 2nd

HA project meeting
Please join my meeting from your computer, tablet or 
smartphone.https://global.gotomeeting.com/join/772448949
You can also dial in using your phone.
United States (Long distance):
+1 (646) 749-3117
Access Code: 772-448-949
More phone numbers: https://global.gotomeeting.com/772448949/numbersdisplay.html
Agenda
1 Progress in Openstack summit - Ian
2 D release planning discussion
https://wiki.opnfv.org/display/availability/D+Release+Plan


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

[opnfv-tech-discuss] GTM Conflict at 14:00 UTC Wednesday?

[SULLIVAN, BRYAN L]

Hi all,

We were having the MANO WG meeting today at 7AM PST (14:00 UTC) using the 
https://global.gotomeeting.com/join/843517045 bridge, and got kicked out at 
about 15 past the hour. Just checking to see if there was some other project 
that started a meeting on the same bridge, e.g. due to a confusion over DST 
change.

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

[opnfv-tech-discuss] Models Weekly Meeting A

[SULLIVAN, BRYAN L]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:America/Los_Angeles
BEGIN:STANDARD
DTSTART:16010101T02
TZOFFSETFROM:-0700
TZOFFSETTO:-0800
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T02
TZOFFSETFROM:-0800
TZOFFSETTO:-0700
RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=2SU;BYMONTH=3
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="SULLIVAN, BRYAN L":MAILTO:bs3...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='opnfv-tec
 h-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Andrew Ve
 itch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Dan Weste
 rberg':MAILTO:dan.westerb...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='David Sua
 rez Fuentes':MAILTO:david.suarez.fuen...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Gabor Hal
 ász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Henry Fou
 rie':MAILTO:louis.fou...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Kuppuswam
 y, Prabu'":MAILTO:prabu.kuppusw...@spirent.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Lawrence 
 Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Mario Tor
 recillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ola Lilje
 dahl':MAILTO:ola.liljed...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Sen, Prod
 ip'":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tal Baren
 boim':MAILTO:t...@amdocs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ulas Koza
 t':MAILTO:ulas.ko...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON JR.
 , AL":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Ramia, Kan
 nan Babu":MAILTO:kannan.babu.ra...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="S, Deepak":
 MAILTO:deepa...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Seiler, Gl
 enn":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=amir@gigas
 paces.com:MAILTO:a...@gigaspaces.com
DESCRIPTION;LANGUAGE=en-US:Sending out a calendar reminder since this makes
  it easier to remember!\n\n\n\nhttps://wiki.opnfv.org/display/models/Model
 s+Meetings\n\nIRC: #opnfv-models\, e.g.  https://www.irccloud.com/#!/ircs:
 //irc.freenode.net:6697/%23opnfv-models\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=MO;WKST=SU
SUMMARY;LANGUAGE=en-US:Models Weekly Meeting A
DTSTART;TZID=America/Los_Angeles:20160718T09
DTEND;TZID=America/Los_Angeles:20160718T10
UID:04008200E00074C5B7101A82E008503F79DEDCE0D101000
 01000C52040BCAE1C654982CB8F8E3A58BA45
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20160718T171328Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:0
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/865421325
X-MICROSOFT-CDO-APPT-SEQUENCE:0
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Summary of Weekly Technical Community Discussion Thursday Nov 3

[SULLIVAN, BRYAN L]

As noted in the call, I will put the following item on the agenda for the next 
Models team meeting: discuss how/where to build a library of reference VNFs for 
functional and performance testing on OPNFV.

I encourage anyone interested in that to join the next Models meeting on 
Monday: https://wiki.opnfv.org/display/models/Models+Meetings

I have been pursuing that for the Models project, at the work-in-progress page 
https://wiki.opnfv.org/display/models/References (see the Open Source VNFs 
table which is pretty short right now).

The related goals in the Models project are to:

-  Increase the diversity of reference VNFs (meaning mostly 
functionally complete open source implementations of typical "network 
functions" and services built from them)

-  Create tests for their deployment/lifecycle management on various 
OPNFV scenarios using various upper-MANO stack components (NFVO/VNFM), and 
include those tests under Functest and Dovetail

-  In the process, collect additional models for VNFs/services that are 
not yet available as part of reference VNFs, and promote their further 
development as functional reference VNFs (see the "Model References" table)

-  Not host the code, but focus on tests and model/blueprint variations 
that support the tests and the goals of the models project to assess and 
promote model/blueprint convergence

It would be good for OPNFV to consider hosting reference VNF implementations 
where there is no current upstream home, e.g. if members donate open source 
VNFs OPNFV could create repos specific to those VNFs for their development.

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of HU, BIN
Sent: Thursday, November 03, 2016 10:28 AM
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] Summary of Weekly Technical Community Discussion 
Thursday Nov 3

***Security Advisory: This Message Originated Outside of AT&T ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.
Hello community,

We had a very good discussion today. Thank you all for participation and 
contribution.

We started with discussing a new project proposal 
"Rescuer". 
Through discussion, it was suggested that Leon work with HA PTL and Multisite 
PTL to identify overlaps and gaps, and find the best way to move forward that 
benefits all projects.

At the end, Dave suggested to put common topics of community as standing agenda 
items. As a result, we put current community discussion topics as standing 
agenda items. We will start to discuss Certification Program related topic next 
Thursday November 10.

The meeting minutes page is 
https://wiki.opnfv.org/display/PROJ/tc+minutes+20161103, which contains the IRC 
log 
http://meetbot.opnfv.org/meetings/opnfv-meeting/2016/opnfv-meeting.2016-11-03-13.01.html.

Thanks
Bin

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

Re: [opnfv-tech-discuss] GTM Conflict at 14:00 UTC Wednesday?

[SULLIVAN, BRYAN L]

Prakash changed the meeting time to be more APAC friendly but we did not change 
the meeting page. Sorry!
Now updated.

Thanks,
Bryan Sullivan | AT&T

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Wednesday, November 02, 2016 1:38 PM
To: SULLIVAN, BRYAN L 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] GTM Conflict at 14:00 UTC Wednesday?

Did the meeting time change?  I thought it was at 1:30 PST, according to the 
meetings page<https://wiki.opnfv.org/display/meetings#Meetings-MANOWGMeeting>.

David

On Wed, Nov 2, 2016 at 7:22 AM, SULLIVAN, BRYAN L 
mailto:bs3...@att.com>> wrote:
Hi all,

We were having the MANO WG meeting today at 7AM PST (14:00 UTC) using the 
https://global.gotomeeting.com/join/843517045 bridge, and got kicked out at 
about 15 past the hour. Just checking to see if there was some other project 
that started a meeting on the same bridge, e.g. due to a confusion over DST 
change.

Thanks,
Bryan Sullivan | AT&T


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



--
David McBride
Release Manager, OPNFV
Mobile: +1.805.276.8018
Email/Google Talk: 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>
Skype: davidjmcbride1
IRC: dmcbride
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Models Weekly Meeting A

[SULLIVAN, BRYAN L]

BEGIN:VCALENDAR
METHOD:REQUEST
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="SULLIVAN, BRYAN L":MAILTO:bs3...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='opnfv-tec
 h-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Dan Weste
 rberg':MAILTO:dan.westerb...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tal Baren
 boim':MAILTO:t...@amdocs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Henry Fou
 rie':MAILTO:louis.fou...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Andrew Ve
 itch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='amir@giga
 spaces.com':MAILTO:a...@gigaspaces.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ola Lilje
 dahl':MAILTO:ola.liljed...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON JR.
 , AL":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ulas Koza
 t':MAILTO:ulas.ko...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='David Sua
 rez Fuentes':MAILTO:david.suarez.fuen...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Mario Tor
 recillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Ramia, Ka
 nnan Babu'":MAILTO:kannan.babu.ra...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Sen, Prod
 ip'":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Kuppuswam
 y, Prabu'":MAILTO:prabu.kuppusw...@spirent.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Gabor Hal
 ász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Seiler, G
 lenn'":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'S, Deepak
 '":MAILTO:deepa...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Lawrence 
 Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ramki_Kri
 sh...@dell.com':MAILTO:ramki_krish...@dell.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Vandris, S
 teve":MAILTO:steve.vand...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=yaohelan:M
 AILTO:yaohe...@huawei.com
DESCRIPTION;LANGUAGE=en-US:Updating this invite to be UTC-based as intended
  on the wiki\, so we limit confusion during the seasonal change.\n\nhttps:
 //wiki.opnfv.org/display/models/Models+Meetings\nIRC: #opnfv-models\, e.g.
   https://www.irccloud.com/#!/ircs://irc.freenode.net:6697/%23opnfv-models
 \n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=MO;WKST=SU
SUMMARY;LANGUAGE=en-US:Models Weekly Meeting A
DTSTART;TZID=UTC:20160718T16
DTEND;TZID=UTC:20160718T17
UID:04008200E00074C5B7101A82E008503F79DEDCE0D101000
 01000C52040BCAE1C654982CB8F8E3A58BA45
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161104T131616Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:1
LOCATION;LANGUAGE=en-US:https://global.gotomeeting.com/join/865421325
X-MICROSOFT-CDO-APPT-SEQUENCE:1
X-MICROSOFT-CDO-OWNERAPPTID:1689417696
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:1
X-MICROSOFT-DISALLOW-COUNTER:FALSE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] Dec Plugfest Planning

[SULLIVAN, BRYAN L]

Hi all,

An update on this request. So far I've heard from the Tacker team that they can 
support the VNF Portability testing remotely. I want to be sure though that we 
have critical mass and the ability to spend time discussing the details of how 
the various projects define their service/VNF packages/blueprints, i.e. get 
some concrete takeaway-value from the event. Further at this point my 
investigations into the documentation for the various projects indicates that 
there's little commonality so far in the data models used in blueprints, e.g. 
some reference YANG and TOSCA, but the models as processed by the VNFM/NFVO 
don't seem to derive from those standards, i.e. they are often in a 
project-specific YAML format. So perhaps we are too early in the development 
process to obtain useful takeaways from the VNF Portability scope of the 
Plugfest.

But I would like to give you a second chance to weigh in on this, and 
strengthen the rationale for this event with input on these questions. If we 
focused just on the VNFM and VNF blueprints for management of OpenStack VIM 
resources (e.g. compute, storage, network resources and topology):

-  What model representation does your project support, e.g.

o   tosca_simple_profile_for_nfv_1_0_0

?  e.g. see the blueprint 
https://git.opnfv.org/cgit/models/tree/tests/blueprints/tosca-vnfd-3node-tacker/blueprint.yaml

o   YANG

?  E.g. see OSM: 
https://osm.etsi.org/gitweb/?p=osm/SO.git;a=blob;f=models/plugins/yang/vnfd.yang

o   Some other format in YAML or JSON

?  E.g. JuJu Charm or project-specific schema

If it turns out that both of the following are true, we should postpone this 
part of the Plugfest:

1)  We have no more than a couple of participating projects

2)  We have low expectations of there being a significant common data model 
support across those projects

If we did have more than two participating projects, at least we could use the 
event as more of a hackfest to see if we can get the "vnfd-3node" blueprint 
working in your projects' specific format.

Thanks,
Bryan Sullivan | AT&T

From: SULLIVAN, BRYAN L
Sent: Tuesday, November 01, 2016 3:42 AM
To: 'Carella, Giuseppe' ; 'FRANCISCO 
JAVIER RAMON SALGUERO' ; 
artur.tyl...@canonical.com; Sridhar Ramaswamy ; 'Sripriya 
Seetharam' ; Arthur Berezin 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Dec Plugfest Planning

Hi all,

Going out to OPNFV in general and specifically to those involved in the 
VNFM/NFVO projects OpenBaton, Tacker, Cloudify, ARIA, JuJu.

I'd like to get your confirmation this week as to whether your 
organization/projects will be able to support the OPNFV Colorado plugfest at 
UNH-IOL, Dec 5-9: 
https://wiki.opnfv.org/display/EVNT/Plugfest+-+Colorado+Release and 
specifically the VNF Portability tests as described on the wiki at 
https://wiki.opnfv.org/display/EVNT/Colorado+Plugfest+Test+Cases.  Since time 
is short for the event (1 month away) we need to quickly assess readiness for 
the event.

I updated the wiki to more completely explain the concept and option for the 
test scope:

VNF Portability Scope
Overall the focus of this test scope will be to demonstrate VNFM product degree 
of compatibility with standards-based, reference VNF blueprints, as installed 
on one or more OPNFV deployment scenarios. It's expected that with the current 
generation of VNFMs, variations in blueprint schema support (e.g. 
product-specific extensions/limitations) will require customization of the 
blueprints, VNF images, or related support scripts. The reference VNF 
blueprints will be provided in advance, so that VNFM projects can prepare any 
needed customizations. Specific goals for the testing are to demonstrate the 
degree of portability, uncover issues for followup, build the library of tested 
blueprints (VNFM-specific, as needed), and overall come away with a much 
clearer assessment of VNFM product support for blueprint standards. This 
initial plugfest will focus on:

  *   the onboading, deployment, and termination phases of the VNF lifecycle, 
as described on the MANO WG wiki at VNF 
Onboarding<https://wiki.opnfv.org/display/mano/VNF+Onboarding>
  *   relatively basic blueprint attributes, e.g. basic resource topology and 
requirements
  *   potentially extending to further lifecycle stages (e.g. handing of 
in-service lifecycle events).
Future plugfests will address other lifecycle stages, more advanced blueprint 
attributes (e.g. policy), and service blueprints (e.g. composed of multiple 
VNFs with service chaining).
Other notes in advance:

  *   If you can't support it in person, we can likely do some remote testing 
as well.
  *   The test POD resources on the "Hello World" blueprint are pretty mild, 
doable in a virtual deploy.
  *   The more advanced blueprints may require a multi-node POD or a full POD. 
We will need PODs that we can use for them, for that w

Re: [opnfv-tech-discuss] [VES] Team Meeting Schedule

[SULLIVAN, BRYAN L]

Per Prakash’s email:
FYI: OPNFV MANO WG Meeting Details

Meeting Times: Weekly Wednesday 7 AM PST (14:00 UTC)

 IRC#opnfv-mano (meetbot is set for meeting minutes)

GOTOMEETING:

1.  Please join my meeting.(refer to 
schedules)<https://wiki.opnfv.org/display/meetings>
https://global.gotomeeting.com/join/843517045

2.  Use your microphone and speakers (VoIP) - a headset is recommended.  Or, 
call in using your telephone.

United States: +1 (312) 757-3119
United States (toll-free): 1 877 309 2070

Access Code: 843-517-045
Audio PIN: Shown after joining the meeting

Meeting ID: 843-517-045
Thanks,
Bryan Sullivan | AT&T

From: Yujun Zhang [mailto:zhangyujun+...@gmail.com]
Sent: Tuesday, November 08, 2016 1:49 AM
To: SULLIVAN, BRYAN L ; opnfv-tech-discuss@lists.opnfv.org
Cc: dong.wenj...@zte.com.cn
Subject: Re: [opnfv-tech-discuss] [VES] Team Meeting Schedule

Which week day is the meeting? Not mentioned in the original message.

On Wed, Nov 2, 2016 at 12:17 AM SULLIVAN, BRYAN L 
mailto:bs3...@att.com>> wrote:
FYI: OPNFV MANO WG Meeting Details
Meeting Times: Weekly 7 AM PDT (15:00 UTC) this week and 7 AM PST (14:00 UTC) 
after daylight changes next week
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Colorado Colocated Plugfest/Hackfest - VNF Portability Scope

[SULLIVAN, BRYAN L]

Hi all,

During the TSC discussion today it became clear to me that we needed to move 
the "VNF Portability Scope" tests from the Plugfest to the collocated hackfest. 
The reason is that the intent of the VNF Portability tests is to help drive 
progress on the Models project goals for Danube, and the prohibition against 
publication of any results for 60 days (per the Rules of Engagement for the 
Plugfest) will not support those goals. As well, I believe any VNF Portability 
scope participants would:

-  have the same goals (to help drive progress on the Models project 
goals for Danube)

-  would be unconcerned about the Models project publishing results (or 
takeaways, at least) of the testing, as they represent open source projects or 
products based upon open source projects

Any exceptions to the above will certainly be considered in how we document the 
hackfest testing results. We'll work that out with the participants as desired.

But the general intent for this test activity, especially at this early stage 
in progress toward Models project goals, places it more appropriately in the 
scope of the hackfest vs the plugfest.

Updated pages on the wiki include:
https://wiki.opnfv.org/display/EVNT/Plugfest+-+Colorado+Release (removed the 
VNF Portability Scope section)
https://wiki.opnfv.org/display/EVNT/Colorado+Hackfest+Test+Cases (added this 
page with the VNF Portability Scope section - we can expand with more detail on 
the tests described on Co-located+Plugfest-Hackfest+Planning+Page)
https://wiki.opnfv.org/display/EVNT/Co-located+Plugfest-Hackfest+Planning+Page 
(linked to the new page)

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] [barometer] Weekly Call

[SULLIVAN, BRYAN L]

Sorry about that. Hopefully coming out of this seasonal scheduling trainwreck 
we will get more aligned for the next one – we need someone to clarify what our 
aligned scheduling policy is (or was agreed to be some time ago), or create an 
alignment. I don’t care how it’s homed (though I recommend UTC) but we do need 
to align across projects (or enforce the existing alignment) to prevent this 
from continuing to happen.

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Tahhan, Maryam
Sent: Tuesday, November 08, 2016 2:39 PM
To: opnfv-tech-discuss@lists.opnfv.org
Cc: Power, Damien ; Mcmahon, Tony B 

Subject: [opnfv-tech-discuss] [barometer] Weekly Call

Hi folks
We are clashing with the OPNFV Release Call with the time change ☹. So I will 
move the barometer meeting to one hour later from next week on to accommodate 
this change. I didn’t realize the clash till just now, so for this week I will 
cancel the meeting because of this short notice.

Agenda for next week:
· Collectd 101.
· Metrics list update and kick off metrics definition activity (will 
send out a mail on this shortly).
· A.O.B

Sorry for the inconvenience

BR
Maryam
-Original Appointment-
From: Tahhan, Maryam
Sent: Tuesday, October 25, 2016 10:33 AM
To: Tahhan, Maryam; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
Power, Damien; Mcmahon, Tony B
Cc: Mario Torrecillas Rodriguez; Chornyi, TarasX; GUPTA, ALOK; MORTON, ALFRED C 
(AL); Lawrence Lamers; Shobhan AyyadevaraSesha (sayyadev); Seiler, Glenn; Scott 
Mansfield; Bernier, Daniel (520165); Canio Cillis; Tomasini, Lorenzo; Srinivasa 
Chaganti; Laporte, Laurent [CTO]; Ola Liljedahl; Jaggi, Manish; Gabor Halász; 
'杨艳'; SULLIVAN, BRYAN L
Subject: [barometer] Weekly Call
When: Tuesday 8 November 2016 16:00-17:00 (UTC+00:00) Dublin, Edinburgh, 
Lisbon, London.
Where: https://global.gotomeeting.com/join/157141149


Hi Folks

Let’s kick off a weekly call on Tuesdays to cover project updates.

BR
Maryam

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

[opnfv-tech-discuss] Colorado Scenario Diagram

[SULLIVAN, BRYAN L]

Hi all,

As noted in the takeaways from the BOD/TSC joint session in Barcelona, I am 
working on creating a diagram that illustrates the Colorado scenario diversity. 
This should be a useful marketing tool for OPNFV. As a start, I updated the 
Colorado-Compact Table of 
Scenarios
 page I created to show the distribution of scenarios across installers more 
succinctly (vs HA/NoHA which is less significant from a marketing perspective). 
I also updated the Brahmaputra slide on scenarios for Colorado and posted the 
slide on that page: Colorado Scenario 
Diagram.pptx.

I'm going to think about how we could add punch to this diagram through other 
ways to show the scenario distribution graphically. Any ideas are welcome!

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

[SULLIVAN, BRYAN L]

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 reviewed next week.
[bryan] We need first to define these components more clearly in terms of role, 
but also to agree that those roles will be served through a variety of 
implementation approaches, so those components are conceptual only. Please 
forward the lifecycle hook proposal asap. I will also pull out the lifecycle 
hook specs and examples as I find them for comparison.

 *   API versioning - which API?
The API versioning is of abstractions or wrappers that is being proposed by 
OpenBaton and will be reviewed by other MANO participants to agree on a common 
wrapper approach for IFA 5, 6,7 and OPNFV VIM and VNFM drivers from NFVO.
[bryan] This point is unclear. Are you referring to the need to version APIs in 
general?

  1.  At what point should upstream integration project  consider OPNFV Models 
topology design and templates to choose  and use. - This will be discussed at 
next Models call with Bryan Sullivan.
[bryan] The question is unclear.

  1.  Wha

Re: [opnfv-tech-discuss] [opnfvdocs] documentation landing page

[SULLIVAN, BRYAN L]

This actually has been a thread of discussion and I think there is some effort 
to create a domain name for this as you describe. I can’t find the thread 
however right now. Anyone with a better memory or mail search tool?

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Yujun Zhang
Sent: Thursday, November 10, 2016 1:58 AM
To: TECH-DISCUSS OPNFV 
Subject: [opnfv-tech-discuss] [opnfvdocs] documentation landing page

Folks,

@Morgan mentioned a landing page for test results during yesterdays weekly 
meeting. I wonder if there is any similar plan for documentation.

Currently the published documents are available on artifacts site. But it seems 
there is no landing page giving an table of all available contents and we lack 
a friendly navigation page.

I think it would be nice to have one like http://docs.openstack.org/

What do you think?
--
Yujun
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[SULLIVAN, BRYAN L]

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] [Models] 2016-Nov-14 Models Project Meeting #18

[SULLIVAN, BRYAN L]

The meeting was at 16:00 UTC (always is) which as of today is 8AM PST.
Sorry for any confusion - hopefully we will standardize on a meeting time base 
(UTC) that is not subject to seasonal changes.

Thanks,
Bryan Sullivan | AT&T

From: Vul, Alex [mailto:alex@intel.com]
Sent: Monday, November 14, 2016 4:05 PM
To: SULLIVAN, BRYAN L ; opnfv-tech-discuss@lists.opnfv.org
Subject: RE: [Models] 2016-Nov-14 Models Project Meeting #18

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>
 [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<mailto: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] [Barometer][VES] Mapping monitored source data to backend interface/model items

[SULLIVAN, BRYAN L]

Peter, that would be great. Can you give some overview of how this can be done? 
I started a section of the wiki page 
https://wiki.opnfv.org/display/ves/Operational+Framework on “Field Mapping” 
where you can put your input in the table or as a paragraph. Or just reply here 
and I will capture the concept in the table.

Thanks,
Bryan Sullivan | AT&T

From: Peter Lee [mailto:pe...@corenova.com]
Sent: Tuesday, November 01, 2016 11:40 AM
To: SULLIVAN, BRYAN L ; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Barometer][VES] Mapping monitored source 
data to backend interface/model items

Sounds like a good use case for modeling using YANG.

Please feel free to ping me if interested in exploring how.

Best,

Peter
On Tue, Nov 1, 2016 at 10:07 AM SULLIVAN, BRYAN L 
mailto:bs3...@att.com>> wrote:
On the Barometer project (FKA SFQM) call today, I made the following suggestion 
that was welcomed by the team. Basically the Barometer project will be 
developing the “frontend” (i.e. agent) data source aspects of analytics 
collection (i.e. interfacing with hosts and VMs etc to collect analytics), and 
delivering it to “backends” (i.e. collectors such as VIMs/monitoring systems) 
via protocols such as REST/HTTP, Kafka, SNMP etc. I think this is a good 
development, as most of the frontend heavy lifting will be done in the collectd 
upstream, and specific projects in OPNFV such as Barometer and VES just need to 
take care of the mapping to the backend interfaces and data models.

To minimize development/maintenance of the mapping between the collectd plugin 
data sources and the specific backend protocol/data model, I suggested that we 
consider a mapping table as a static or manageable attribute of the 
configuration for the agent. For example, as you can see in Maryam’s team 
implementation of the 
ves_plugin.py<https://github.com/maryamtahhan/OpenStackBarcelonaDemo/blob/master/ves_plugin/ves_plugin.py>,
 values for the data source items are mapped to fields in the JSON-based VES 
message structure in individual code statements. Even in this early demo 
version, there are many monitored data items, and this can be expected to 
expand greatly. It would be nice if we can automate as much of this as possible 
through a table with rows such as:

{ plugin_name, plugin_instance, type_name, type_instance }, { 
domain.property.property.property… }

Theoretically, it should be possible in many cases to simply run thru such a 
table and copy the source data to the proper place in the target event 
structure. If calculations are needed on the source, they might still require a 
discrete statement, but many of the fields could be just copied. For target 
properties which are lists, that would need to be considered as well, but I 
think we could indicate that through some variable reference or “property[x]”.

Any input on this idea, experience implementing such mapping systems etc, is 
appreciated.

Thanks,
Bryan Sullivan | AT&T
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
--
Peter Lee
Corenova Technologies
+1 310 400 6450
pe...@corenova.com<mailto:pe...@corenova.com>
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Real-World CI/CD Topic for Hackfest

[SULLIVAN, BRYAN L]

Here's a topic I brought up at the Infra meeting today, that I've added to the 
Hackfest Planning page 
https://wiki.opnfv.org/display/EVNT/Co-located+Plugfest-Hackfest+Planning+Page
This was inspired by the OpenStack summit CI/CD Fishbowl session 
https://etherpad.openstack.org/p/BCN-ops-ci-cd-workflows (that etherpad doesn't 
capture all the perspectives offered in the meeting - but the key ones for us 
are reflected below).

Also see AT&T's Agile Journey: OpenStack Platform 
Delivery
 which was presented by our CI/CD team leads.

"Real-World CI/CD" (tm ;-) refers to CI/CD processes that support the 
real-world needs of service providers in deploying NFV service environments and 
virtual functions. In comparison to OPNFV's current processes which are largely 
based upon a "real-time" build process vs a "staged" build process (my terms). 
Real-world processes will probably have the characteristics below, especially 
for network service providers who have significant constraints (e.g. 
regulatory) on how they build and operate service environments.


  *   Real-world CI/CD pipelines: a real-world CI/CD environment will use 
pre-built components and local repos because
 *   Time to deploy/upgrade VIMs must be shorter and more reliable (thus 
less dependent upon uncontrolled elements e.g. public package servers and git 
repos), especially for large sites.
 *   Code scans have to be done in advance, e.g. for security, license 
management, etc
 *   Components e.g. containers or VM images for VIM services and VNFs have 
to be pre-built so they can be a "known quantity" and include all the necessary 
tools and customized configuration required by the operator, e.g. security 
tools, service assurance tools, etc

I brought this to the EUAG on the last call and there was some support for 
these goals:

  *   OPNFV should consider (value, process/resource impact) of NFVI/VNF 
deployment methods supporting "real-world CI/CD" needs
 *   CI/CD support for pre-built VIM/NFVI components and applications, and 
local repos.
 *   A continual need to optimize the CI/CD pipeline, while accommodating 
(i)

*   The need to support (1) brings its own challenges, which have to 
nonetheless be overcome to create a CI/CD pipeline that is as short and as 
agile as possible. The tools and techniques enabling pipeline optimization 
should be collaboratively developed in OPNFV.

As Chris P mentioned on the Infra call, we have various efforts underway that 
may help here, e.g. CI evolution. I suggest that we meet at the hackfest to 
talk about:

* The needs and goals expressed above

* how the current efforts e.g. CI evolution may support some of those 
goals

* where gaps in OPNFV processes remain

* if we were to try to close those gaps

 i.what would be the impact on 
OPNFV e.g. for Releng and Infra, e.g. assuming we want to maintain the current 
"real-time" process while adding some support for a "staged" process

   ii.assuming there would be resource 
impacts, how would we resource this effort

Any thoughts on this are appreciated.

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] 答复: [functest] [yardstick] Client version can't support Newton - solution proposal

[SULLIVAN, BRYAN L]

I would say that:

1)  We should strive to directly leverage upstream clients directly, and 
specifically the python-openstackclient in all cases where it serves our need 
for the specific OPNFV system version.

a.   Exceptions do exist, but we will not help promote removal of those 
exceptions by creating a shim client that shields us from the pain of the gaps, 
and the OpenStack python-openstackclient project from the need to address those 
gaps.

b.   After all, we are here to identity and address-upstream issues with 
the upstream projects.

2)  We should not own code intended as a long-term shim of an upstream 
project, even one that ostensibly simplifies how test code interacts with the 
openstack clients (the python-openstackclient or any of the others).

a.   An experimental shim might help the upstream teams to understand and 
address gaps/issues we have, but would have little real, long-term value to 
OPNFV beyond that.

b.   One key reason is any simplification/abstraction is likely to mask 
things that some project needs, and then we are right back to an 
exception/kludge situation, with the exception that to address the issue we now 
have to issue patches against another (and not even upstream) project.

3)  We should document all issues with the plan-of-record of the OpenStack 
community to converge on the python-openstackclient, and put any efforts to 
address them directly upstream, not in OPNFV.

a.   For now we have plenty of workaround approaches to those issues, e.g. 
use a different client/version.

b.   The implications/limitations of those workarounds should also be 
documented so we can decide which really are sufferable until the upstream 
client issues are addressed.

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of yaohelan
Sent: Monday, November 14, 2016 7:32 PM
To: Jose Lausuch ; Beierl, Mark 

Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] 答复: [functest] [yardstick] Client version can't 
support Newton - solution proposal

Hi all,

Here is the drafted proposal for the Newton support. Your feedback is 
appreciated.
If you have other solution, feel free to come up with.
Once we know every detail of each solution, we may vote for which one to use.

A common OpenStack utility library/module is needed to handle all operations 
against OpenStack,
and it will be used by projects including Yardstick, Functest, Storperf, 
Bottleneck
and other projects that have the requirements to interact with OpenStack.
Benefit:
Only OpenStack utility library/module is required to be updated when there is 
any request for upgrading/change.
Effort will be saved for projects and they can focus on the main business.
In real world, all projects are maintaining their own repository for OpenStack 
operation.
The effort to upgrade the process will not be shared among projects.
Area to Investigate
Look at the existing codes and come up with a solution to put them together.

Two possible solutions to deal with client version change for different 
OpenStack
Idea 1: Leverage OpenStackClient[1] to take care of different OpenStack version
Reason: OpenStack should be able to handle the version switching and support 
the backward compatibility.
It is quite challengeable for downstream projects to take care of the version 
with limited knowledge.
Areas to investigate

1.Identify the all scenarios that we are leveraging clients

2.Test with OpenStackClient to make sure all scenarios can be fulfilled
Risks/Challenges
1. Functest and Yardstick are mainly using components including Nova, Keystone, 
Neutron, Heat, etc. OpenStackClient provides a shell.py to wrapping the call 
into CLI and it seems that this way provides almost every possible alternatives 
to our currently implementation. However, if we wants to import openstackclient 
as module in the code, heat might be lost and we have to implement the logic to 
support calling different version of heatclient.
2. The learning curve might be long as it requires developers to map all of 
current implementation to openstackclient.

Idea 2: Design the logic to handle different clients
Areas to investigate

1.Come up with the client list for different OpenStack version

2.Put the client requirements into separate configuration per OpenStack 
version

3.Dynamically decide which configuration to use
Risks/Challenges
1. A wise and general architecture is required as more OpenStack upgrades are 
expected

[1] https://github.com/openstack/python-openstackclient



发件人: Jose Lausuch [mailto:jose.laus...@ericsson.com]
发送时间: 2016年11月11日 23:43
收件人: Beierl, Mark mailto:mark.bei...@dell.com>>; yaohelan 
mailto:yaohe...@huawei.com>>
抄送: liyuenan mailto:liyue...@huawei.com>>; 
opnfv-tech-discuss@lists.opnfv.org
主题: RE: [opnfv-tech-discuss] [functest] [yardstick] Client ver

[opnfv-tech-discuss] MANO-Related Project Huddle at Hackfest

[SULLIVAN, BRYAN L]

Hi all,

I created a page where we can organize around the agenda and attendance at a 
3-hour session on Thurs 8th (8:00-11:00) on MANO-related projects and 
cross-project topics.
https://wiki.opnfv.org/display/EVNT/Colorado+Hackfest-MANO+project+huddle

Depending upon the number of project members at the hackfest and conflicts with 
other sessions, we can use the time however best fits those that can attend. 
And we can also break it up, move it around, etc if needed for more attendance 
on specific topics. I recommend we finalize the plan at the session on Monday 
11AM.

Feel free to add your input and attendance to the page above or on the etherpad 
https://etherpad.opnfv.org/p/colorado-hackfest-mano

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 #13 todays Summary and next Meeting #14 - Nov 30th Wednesday 15 UTC

[SULLIVAN, BRYAN L]

Hi all,

As noted in the call today I added some info to the wiki to help us organize 
around the key themes we discussed today. We will defer discussion on Functest 
aspects until we have addressed these basic topics, or let the MANO-related 
projects consider the Functest aspects in the meantime.

For this I created a table on the MANO WG main page, and pages where we can 
capture the discussion details on 
Architecture and  
Lifecycle, in addition to the 
existing VNF Onboarding and 
Integrating MANO Components in 
OPNFV 
pages. Here are the main topics we agreed to consider today (please add/edit as 
needed here or on the wiki):

* Assess the various architectural approaches to MANO functions, e.g. 
across Open-O, OpenBaton, OSM, ...

o   On the Architecture page, 
provide links to documentation and assessment the various approaches.

* Assess the service/VNF lifecycle (e.g. sequence of operations) as 
supported by the various MANO projects, through links to documentation and 
assessments of the various approaches in wiki pages, e.g.

 *   the VNF Onboarding 
page, which addresses the broad outline of the VNF lifecycle with focus on the 
"onboarding" aspects
 *   the Lifecycle page 
which addresses the sequence of operations for deployment, and lifecycle events 
(hooks) supported by the MANO project e.g. through generic or specific VNFMs.

* Assess goals and options for MANO function integration into OPNFV.

o   On the Integrating MANO Components in 
OPNFV 
page, consider the options, e.g.:

*   inherent (pre-installed for all scenarios)
*   installable on-demand (install-time option or post-install)
*   installed for test purposes (e.g. as current for 
vIMS, and the 
Models project tests
Thanks,
Bryan Sullivan | AT&T

From: mano-wg-boun...@lists.opnfv.org [mailto:mano-wg-boun...@lists.opnfv.org] 
On Behalf Of Prakash Ramchandran
Sent: Wednesday, November 23, 2016 12:26 PM
To: mano...@lists.opnfv.org
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: [mano-wg] [MANO] Meeting #13 todays Summary and next Meeting #14 - Nov 
30th Wednesday 15 UTC


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

Agenda of meeting November 30, 2016  15.00 UTC /7.00 PST Meeting #14

  1.  Review of last week work and Agenda bashing

  2. The  FUNCTEST-353 is more 
comprehensive than  focus on API testing through common wrappers. Therefore  4 
mores tasks are created under Functest to address that and they are

FUNCTEST-614, 
FUNCTEST-615, 
FUNCTEST-616, 
FUNCTEST-617 (needs updates on test 
plans  and on  community PODs Huawei/ZTE)

   Yingjun/Giuseppe to ask their teams to  compare with 
https://git.opnfv.org/functest/tree/testcases/vnf/vIMS?h=stable/colorado this 
code with Java codes presented last week and give feedback.

 3. Action Artur to plan for getting Rebaca 
Automation team to present on how 
they use Juju with NFVOs

 4. How would the results of collaboration through MANO WG reflect in 
D-release of OPNFV. - A document template  to be proposed and  reviewed to see 
what should the best practices to include in the D-release based on MANO WG 
participation by Opera, Orchestra and associated VNFM.

 5. Discussions on what would be inputs from MANO_WG to OPNFV D & E 
Release. Wiki Page to update after discussions in WG. - Bryan to update this 
for Release D with minimum and Prakash to review all the participating projects 
and provide a report this 
meeting on 30th Nov.

 6. Any  Updates on UNH 
Plug-fest

Summary of meeting (today)  November 23, 2016  15.00 UTC /7.00 PST Meeting #13

  1.  Review of last week work and Agenda bashing

Need FUNCTEST-237 replaced by one 
that Opera/Orchestra will commonly use - YingjunLi/Giuseppe)

Giuseppe went over the codes listed for wrapper calls for or-vi and 
or-vnfm and explained how it 
uses Java Public cal

[opnfv-tech-discuss] [MANO] New time for MANO WG Calls?

[SULLIVAN, BRYAN L]

Hi all,

Intel (Alex Vul) would like to get engaged in the MANO WG calls as we consider 
the architectural aspects as he's directly engaged in Open-O strategy including 
service/VNF modeling (which is a topic of the Models project but also touches 
on the roles/design of the MANO stack components).

Unfortunately the MANO WG calls conflict with the Open-O TSC calls, so it would 
be great to change the time if possible. I can do 14:00 UTC (6 AM PST) if that 
works for others.

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

[opnfv-tech-discuss] [OPNFVDOCS] Add a bug report button to OPNFV docs

[SULLIVAN, BRYAN L]

I'd like to suggest that we figure out how to add something similar to the 
"report a bug" feature that OpenStack docs have.  e.g. see 
http://docs.openstack.org/user-guide/cli-nova-configure-access-security-for-instances.html.
 I found that they referred to "--pub-key" in creating keypairs, vs the correct 
"--public-key". Reporting the bug was easy (I hope they actually look at the 
bugs though...).

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

[opnfv-tech-discuss] Feedback requested on test documentation example from Models

[SULLIVAN, BRYAN L]

Hi all,

In the test wg meetings I've mentioned the goals I have for optimizing the 
effort required to develop test documentation and coverage. In summary,

* Tests should be self-documenting - no "test plan" should be needed 
beyond the entries in the test database and the comments in the tests

* Tests should include specific (identified by an ID) test assertions, 
which provide all the information necessary to understand the steps of the 
test, beyond a general description. For example, for the test 
vHello_Tacker.sh see 
the header below.

* The test assertions can be managed by some database if that's 
necessary and as effective as a simple flat file. For now, a flat file will do 
and they can be further described as needed on a wiki. See 
test-assertions on the 
Models wiki as an example. With the flat file approach can use simple bash 
scripts to change (by sed etc) the IDs as needed (e.g. as they get renamed, 
split, merged, etc... as typically will happen as tests are developed).

* Test coverage can be assessed by processing the set of test scripts 
to pull out the referenced assertions, and comparing them to the test assertion 
database. Or we can develop the test coverage map by adding assertion pass/fail 
reports (for the discrete assertions in addition to the overall test) to the 
test results database (recommended).

I'd like to get your feedback on this approach. The bottom line goal is that we 
have test documentation and coverage info with the least development and 
maintenance effort.

# What this is: Deployment test for the Tacker Hello World blueprint.
#
# Status: work in progress, planned for OPNFV Danube release.
#
# Use Case Description: A single-node simple python web server, connected to
# two internal networks (private and admin), and accessible via a floating IP.
# Based upon the OpenStack Tacker project's "tosca-vnfd-hello-world" blueprint,
# as extended for testing of more Tacker-supported features as of OpenStack
# Mitaka.
#
# Pre-State:
# models-joid-001 | models-apex-001 (installation of OPNFV system)
#
# Test Steps and Assertions:
# 1) bash vHello_Tacker.sh tacker-cli setup|start|run|stop|clean]
#   models-tacker-001 (Tacker installation in a docker container on the 
jumphost)
#   models-nova-001 (Keypair creation)
# 2) bash vHello_Tacker.sh tacker-cli start
#   models-tacker-002 (VNFD creation)
#   models-tacker-003 (VNF creation)
#   models-tacker-vnfd-001 (config_drive creation)
#   models-tacker-vnfd-002 (artifacts creation)
#   models-tacker-vnfd-003 (user_data creation)
#   models-vhello-001 (vHello VNF creation)
# 3) bash vHello_Tacker.sh tacker-cli stop
#   models-tacker-004 (VNF deletion)
#   models-tacker-005 (VNFD deletion)
#   models-tacker-vnfd-004 (artifacts deletion)
# 4) bash vHello_Tacker.sh tacker-cli clean
#   TODO: add assertions
#
# Post-State:
# After step 1, Tacker is installed and active in a docker container, and the
# test blueprint etc are prepared in a shared virtual folder /tmp/tacker.
# After step 2, the VNF is running and verified.
# After step 3, the VNF is deleted and the system returned to step 1 post-state.
# After step 4, the system returned to test pre-state.
#
# Cleanup: bash vHello_Tacker.sh tacker-cli clean


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] Feedback requested on test documentation example from Models

[SULLIVAN, BRYAN L]

This is still a work in progress so assertions for now every assertable thing 
may be fully developed yet. And there’s an important cost/benefit calculation 
in how deep we go with that (for example, I do not include assertions for the 
workarounds for Mitaka Tacker limitations). But I expect to beef it up further.

The quickest way to determine how things are done is to find the related 
assertion in the script and there will be a specific log entry that says what’s 
happening in that step. If there’s time, we can beef up descriptions but the 
general principle is to make it easy for someone who cares to see what’s 
happening, and to avoid duplicating the description of what’s happening in the 
test header. If we want to develop support tools that can pull these lines from 
tests to create some “test plan doc”, we can use these log entries as part of 
that step-by-step description.

For example:

  echo "$0: $(date) verify vHello server is running"
  apt-get install -y curl
  if [[ $(curl $SERVER_URL | grep -c "Hello World") == 0 ]]; then fail; fi
  assert "models-vhello-001 (vHello VNF creation)" true
  assert "models-tacker-003 (VNF creation)" true
  assert "models-tacker-vnfd-002 (artifacts creation)" true
  assert "models-tacker-vnfd-003 (user_data creation)" true

The step above shows that the method of determining that the VNF is really 
“active” is to curl the web server URL and get the expected response. The other 
assertions are implied to be true by the success of this operation (the 
artifact is the image created upon which the server is running, and the 
user_data contained the code that installed the web server, thus the successful 
curl confirms both were setup as expected).

Or the next step, which does the same thing but looks for the UUID which would 
be present in the returned page if the user_data code that pulled the ID from 
the config drive was successful in doing so (and thus the config drive was 
setup as expected).


  echo "$0: $(date) verify contents of config drive are included in web page"

  id=$(curl $SERVER_URL | awk "/uuid/ { print \$2 }")

  if [[ -z "$id" ]]; then fail; fi

  assert "models-tacker-vnfd-001 (config_drive creation)" true

(and actually now looking at this I see I need to change the “fail” lines to be 
“assert” lines also…)

Thanks,
Bryan Sullivan | AT&T

From: David McBride [mailto:dmcbr...@linuxfoundation.org]
Sent: Friday, December 02, 2016 10:12 AM
To: SULLIVAN, BRYAN L 
Cc: test...@lists.opnfv.org; opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] Feedback requested on test documentation 
example from Models

Bryan,

In general, I like this approach.

My only comment is that I think that the "Post-State" criteria should be more 
specific and detailed.  For example, "Tacker is installed and active in a 
docker container".  Specifically, how is this determined? OS commands? Docker 
commands? Something else?

Similarly, "the VNF is running and verified".  What does "verified" mean?  How, 
specifically, is this determined?

David

On Thu, Dec 1, 2016 at 6:56 PM, SULLIVAN, BRYAN L 
mailto:bs3...@att.com>> wrote:
Hi all,

In the test wg meetings I’ve mentioned the goals I have for optimizing the 
effort required to develop test documentation and coverage. In summary,

• Tests should be self-documenting – no “test plan” should be needed 
beyond the entries in the test database and the comments in the tests

• Tests should include specific (identified by an ID) test assertions, 
which provide all the information necessary to understand the steps of the 
test, beyond a general description. For example, for the test 
vHello_Tacker.sh<https://git.opnfv.org/models/tree/tests/vHello_Tacker.sh> see 
the header below.

• The test assertions can be managed by some database if that’s 
necessary and as effective as a simple flat file. For now, a flat file will do 
and they can be further described as needed on a wiki. See 
test-assertions<https://wiki.opnfv.org/display/models/test-assertions> on the 
Models wiki as an example. With the flat file approach can use simple bash 
scripts to change (by sed etc) the IDs as needed (e.g. as they get renamed, 
split, merged, etc… as typically will happen as tests are developed).

• Test coverage can be assessed by processing the set of test scripts 
to pull out the referenced assertions, and comparing them to the test assertion 
database. Or we can develop the test coverage map by adding assertion pass/fail 
reports (for the discrete assertions in addition to the overall test) to the 
test results database (recommended).

I’d like to get your feedback on this approach. The bottom line goal is that we 
have test documentation and coverage info with the least development and 
maintenance effort.

# What this is: Deploymen

Re: [opnfv-tech-discuss] [doctor] doctor CI now available

[SULLIVAN, BRYAN L]

Ryota, what was the quick hack for congress?

On Dec 4, 2016, at 2:36 AM, Carlos Goncalves  wrote:

Hi Ryota,

Really great job setting up the CI infrastructure and Doctor verify jobs! Thank 
you very much!

I found a false positive. Jenkins verifies (+1) but the job have actually 
failed. The Doctor functest exists with an error exit code (!=0), though.

https://gerrit.opnfv.org/gerrit/#/c/24399/

We can take care of this in person tomorrow at the Hackfest :-)

Carlos

-Original Message-
From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Ryota Mibu
Sent: 04 December 2016 08:54
To: opnfv-tech-discuss@lists.opnfv.org
Subject: [opnfv-tech-discuss] [doctor] doctor CI now available

Hi,


Doctor CI jobs are now available and I confirmed those returns green lights 
with current codes on the master branch.

Reviewers, please check the CI results before merging a patch set. If the CI 
jobs were run before Dec 2nd, just trigger CI jobs again by leaving comment 
"recheck".

  doctor-verify-apex-sample-master
  doctor-verify-apex-congress-master

Note: congress works fine, with some quick hack on the POD after I installed 
OPNFV with latest apex. I'll work with apex team to fix issues I found.

Let me know if you find any problems in those CI jobs.


Best regards,
Ryota

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

Re: [opnfv-tech-discuss] Discussion for OpenRetriever

[SULLIVAN, BRYAN L]

Xuan Jia,

What we meant re current scenarios, are what we build and test in CI/CD, with 
various combinations of components and feature-specific code that adds to the 
basic scenario components. We would need to see what components you intend to 
add beyond Kuryr, to know if a new scenario was needed. But the goal is not to 
add new scenarios due to the resource/process overhead.

And just FYI, it would be good for us to align on terms here. Note that re " 
let the VNF run in the container", a VNF won't run "in a container", unless the 
VNF has a single VNF Component (VNFC) and this needs only one VDU (Virtual 
Deployment Unit). Containers as with VMs are one of the options for VDU 
deployment. This is related to my comment on the call that the VIM should 
support VNF deployment in a mix of VDU types, for VNFs that have multiple 
VNFCs. Multi-VNFC VNFs will likely the the most common case, so we need to 
think and refer to VNFs running in "a set of containers and/or VMs" or more 
generically "a set of virtualization hosts".

On Dec 2, 2016, at 4:17 AM, jiaxuan  wrote:

Hi All
Thanks for the discussion for the new project proposal OpenRetriever. I
answer these questions we have discussed in the last meeting.  If I have
something misunderstood, please let me know.  

1. If there is a baremetal deployment, in case of COE, regarding networking
part, do you intend to use kubernetes or native COE APIs.
To Prem:  If we discuss it without openstack, I intend to use Kubernetes as
I am familiar with it.  But Openstack has been deployed widely in CT, I have
to think about how container integrated with openstack . So we can choose
mode ii or mode iii .  The reason why I want to choose mode iii is that for
mode ii, the upper layer has to use COE api to manage container, it has to
develop new plugin to suit COE api. If using Zun to translate COE api to
Openstack API, the upper layer will not change much.  'legacy', we need to
keep the previous software can work , but in mode iii, it still keeps the
Native COE APIs. 

2. Do I meet the performance issue?
To Prem: Currently, we don't meet the performance issue. We only tested vIMS
.  Well,  for other VNFs, it may need DPDK technology or others to
accelerate the network speed. This proposal we have considered to integrate
DPDK , SR-IOV and others . As far as I know Intel is working on it. 

3.  If to use kubernetes on top of OpenStack i.e. kubernetes as VNFM and OS
as VIM (Model 2) , why to prefer Model 3 than Model 2
To Dave:  I think kubernetes is a kind of COE and controls the resources
like CPU. Kubernetes could be a VIM.  But if  to make Kubernetes as VNFM, it
will be mode 1.  If I misunderstand, please correct me .

4. if there is an explicit goal of interoperability of VNFs instantiated by
VMs and Containers
To Steve: Well, I don't think so. Kuryr project (
https://github.com/openstack/kuryr ) can provide network for container.
Containers can connect to VMs and VMs can connect to containers. 

5. why does it mean to change COE API to native API?
To Bryan: I am sorry I didn't understand the question yesterday.  I meant
change COE api to Openstack API. Then the container can be managed by
Openstack.  For the upper layer, we will not change many things. If the
total platform is containerized, the upper layer has a lot of things to
modify. We can make it step by step.  Collaborate with community to add new
feature in TOSCA and standardized VIM Api. If COE API can be the stand API
of VIM, this proposal will be simple.   

6.suggested to create software within existing scenarios instead of creating
additional OPNFV scenarios, those container components can be added to
existing scenarios.
To Chris ,Bryan, Uli: 
I am sorry, what do you mean 'the existing scenarios' ?  Could you give me
some examples? Thanks. 
OpenRetriever focus on the container integrated with openstack and how
containerized VNF runs in the platform.  It not only needs to install
additional components, but also integrated DPDK and other container
technology to let the VNF run in the container.  

Good talk with you

BR

Xuan Jia
Project Manager
Big Data & IT Technology Research Center China Mobile Research Institute
32 Xuanwumen West Street, Xicheng Distirct, Beijing 100032, China
Mobile: (+86) 3811000575
E-mail: jiax...@chinamobile.com




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

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

[SULLIVAN, BRYAN L]

BEGIN:VCALENDAR
METHOD:CANCEL
PRODID:Microsoft Exchange Server 2010
VERSION:2.0
BEGIN:VTIMEZONE
TZID:UTC
BEGIN:STANDARD
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T00
TZOFFSETFROM:+
TZOFFSETTO:+
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
ORGANIZER;CN="SULLIVAN, BRYAN L":MAILTO:bs3...@att.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='opnfv-tec
 h-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Dan Weste
 rberg':MAILTO:dan.westerb...@enea.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Tal Baren
 boim':MAILTO:t...@amdocs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vul, Alex
 '":MAILTO:alex@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Henry Fou
 rie':MAILTO:louis.fou...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Andrew Ve
 itch':MAILTO:andrew.vei...@netcracker.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='amir@giga
 spaces.com':MAILTO:a...@gigaspaces.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="GUPTA, ALO
 K":MAILTO:ag1...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ola Lilje
 dahl':MAILTO:ola.liljed...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="MORTON JR.
 , AL":MAILTO:acmor...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ulas Koza
 t':MAILTO:ulas.ko...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='David Sua
 rez Fuentes':MAILTO:david.suarez.fuen...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Mario Tor
 recillas Rodriguez':MAILTO:mario.rodrig...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Ramia, Ka
 nnan Babu'":MAILTO:kannan.babu.ra...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Sen, Prod
 ip'":MAILTO:prodip@hpe.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Kuppuswam
 y, Prabu'":MAILTO:prabu.kuppusw...@spirent.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="DRUTA, DAN"
 :MAILTO:dd5...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Gabor Hal
 ász':MAILTO:gabor.hal...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Seiler, G
 lenn'":MAILTO:glenn.sei...@windriver.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'S, Deepak
 '":MAILTO:deepa...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Lawrence 
 Lamers':MAILTO:ljlam...@vmware.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ramki_Kri
 sh...@dell.com':MAILTO:ramki_krish...@dell.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Vandris, 
 Steve'":MAILTO:steve.vand...@intel.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='yaohelan'
 :MAILTO:yaohe...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Canio Cil
 lis':MAILTO:canio.cil...@de.ibm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Shobhan A
 yyadevaraSesha (sayyadev)':MAILTO:sayya...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Trinath S
 omanchi':MAILTO:trinath.soman...@nxp.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="'Zhangyi (
 ZHANG YI, SCC)'":MAILTO:enid.zh...@huawei.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Ahmed Elb
 ornou (amaged)':MAILTO:ama...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN='Randy Lev
 ensalor':MAILTO:r.levensa...@cablelabs.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Alan McNam
 ee:MAILTO:alan...@openet.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Tomasini, 
 Lorenzo":MAILTO:lorenzo.tomas...@fokus.fraunhofer.de
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Daniel Smi
 th:MAILTO:daniel.sm...@ericsson.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Edna Ganon
 :MAILTO:ega...@mrv.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN=Reid Cheng
  (xincheng):MAILTO:xinch...@cisco.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE;CN="Pauls, Mic
 hael":MAILTO:michael.pa...@tu-berlin.de
DESCRIPTION;LANGUAGE=en-US:On vacation\, tr

[opnfv-tech-discuss] [FuncTest] Test Database Swagger URI changed?

[SULLIVAN, BRYAN L]

Hi all,

I tried to verify the API URL 
http://testresults.opnfv.org/test/swagger/spec.html#!/spec/update which had 
been used earlier to update the database, but it appears not to be working now, 
using the credentials as shown on the page "Where can I find the documentation 
on the test API?". 
Did the swagger API URL change?

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] [polestar]Meeting thursday at 11AM US EST

[SULLIVAN, BRYAN L]

I didn’t see a response to this an it seems the meeting did not start  
(“waiting for organizer”) – just checking.

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Margaret Chiosi
Sent: Wednesday, January 04, 2017 7:57 PM
To: opnfv-tech-discuss 
Subject: [opnfv-tech-discuss] [polestar]Meeting thursday at 11AM US EST

Happy New Year and welcome back. Hope folks are ready for a productive 2017.
I will be hosting the call tomorrow - but may have issues sharing my PC 
depending on my comcast internet - comcast is coming 9-11 tomorrow for the 3rd 
time
Min: is it possible for you to initiate the call since I am concerned I may not 
be able to do it.
Then all i have to do is dial in if i have no internet and can talk through 
what we want to do.


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

[opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Hi all Fuel team members,

I'm looking for some guidance on how to track Fuel status for Danube and how to 
contact the Fuel team other than email, which we all have too much of. I see 
some info at https://wiki.opnfv.org/display/fuel/Fuel+Opnfv but it seems that 
the irc channel referenced (opnfv-bgs) has been idle for a while, so that's 
clearly not where the OPNFV Fuel team hangs out.

But the basic question is whether Fuel is ready for Danube testing, e.g. has 
been updated to OpenStack Newton. The Copper project would like to help in the 
testing of Congress, and for Models and VES I want to start 
developing/verifying support under Fuel-based installs.

Please let me know where you guys hang out on IRC, Slack, Trello, or whatever, 
if we can start testing Fuel for Danube yet, and how to track the status of 
Fuel for Danube overall.

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] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Thanks for the link. I do look at the Jenkins status for high-level info, but 
it’s hard to find out the things I need from that, which are, to start related 
to how a developer deploys a simple fuel-based scenario (e.g. os-nosdn-nonha) 
in the lab

-  What has changed since 
http://artifacts.opnfv.org/fuel/colorado/3.0/docs/installationprocedure/index.html
 (in general are there any draft Danube docs yet)

-  Is booting the fuel ISO the only option, or as with other installers 
can we build/deploy on the fly with a simple bash script (deploy.sh) after 
cloning the repo

-  If booting the fuel ISO is the only option, what are the 
requirements for the jumphost, e.g. can this be done in a virt-manager VM (and 
how) or does it need to be bare metal, what are the host requirements (minimum) 
for the jumphost, etc

-  How is virtual deployment of the fuel master achieved (the install 
doc above does not specify the details) – it’s not clear if this is different 
from booting the fuel ISO in a VM

-  If supported, what are the minimum requirements for virtual deploy

-  What are the minimum requirements for bare metal lab servers, e.g. 
as I have been using will this work

o   Three Intel NUC i7 machines with two NICs, wake-on-lan + PXE boot (no 
IPMI), 16GB memory

Thanks,
Bryan Sullivan | AT&T

From: Serg Melikyan [mailto:smelik...@mirantis.com]
Sent: Tuesday, January 10, 2017 7:59 AM
To: SULLIVAN, BRYAN L 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Hi Bryan,

indeed IRC channel mentioned on our wiki page was wrong, I have updated wiki 
page - our actively used IRC channel is #opnfv-fuel.

You can track our CI by the following link: 
http://build.opnfv.org/ci/view/fuel/ which has corresponding jobs for master 
which is Denube right now.

On Tue, Jan 10, 2017 at 7:20 AM, SULLIVAN, BRYAN L 
mailto:bs3...@att.com>> wrote:
Hi all Fuel team members,

I’m looking for some guidance on how to track Fuel status for Danube and how to 
contact the Fuel team other than email, which we all have too much of. I see 
some info at https://wiki.opnfv.org/display/fuel/Fuel+Opnfv but it seems that 
the irc channel referenced (opnfv-bgs) has been idle for a while, so that’s 
clearly not where the OPNFV Fuel team hangs out.

But the basic question is whether Fuel is ready for Danube testing, e.g. has 
been updated to OpenStack Newton. The Copper project would like to help in the 
testing of Congress, and for Models and VES I want to start 
developing/verifying support under Fuel-based installs.

Please let me know where you guys hang out on IRC, Slack, Trello, or whatever, 
if we can start testing Fuel for Danube yet, and how to track the status of 
Fuel for Danube overall.

Thanks,
Bryan Sullivan | AT&T


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



--
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com<http://mirantis.com/> | 
smelik...@mirantis.com<mailto:smelik...@mirantis.com> | +1 (650) 440-8979
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [Community] Inputs to 2nd Multi-SDO-OpenSource Info Modeling Workshop uploaded

[SULLIVAN, BRYAN L]

Hi all,

The inputs to the 2nd Multi-SDO - Open Source Info Modeling Workshop have been 
uploaded to the OPNFV wiki at 
https://wiki.opnfv.org/display/COM/Multi-SDO-Open+Source+Information+Modeling+Collaboration.
 In OPNFV we will be using that page and the linked pages for the action items 
to track further discussions/progress.

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] [polestar] Reminder of call this thursday 11AM US EST - also send me suggestions on when to do a F2F

[SULLIVAN, BRYAN L]

OPNFV Hackfest in April (France).
Thru May that’s about it, then there’s the OPNFV Summit in June (Beijing).

Thanks,
Bryan Sullivan | AT&T

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Margaret Chiosi
Sent: Tuesday, January 10, 2017 8:27 PM
To: opnfv-tech-discuss 
Subject: [opnfv-tech-discuss] [polestar] Reminder of call this thursday 11AM US 
EST - also send me suggestions on when to do a F2F

Folks:
Sounds like ONS may be the best time for us to do F2F vs Openstack in Atlanta 
next month.
Let me know which conferences you will be attending to see if we can get a 
quorum at one of these:
1. Openstack Atlanta, Feb
2. Openstack Boston, May?
3. ONS Santa Clara, April
4. Layer 123 Santa Clara, April
4. Others?

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

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Hi Fuel team,

Sorry to pester, but I didn’t get a response to this set of questions yet here 
or on IRC (#opnfv-fuel), so I’m pinging you again for help. With the short time 
until Danube freeze, we really need your help with Fuel install questions as 
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 SULLIVAN, 
BRYAN L
Sent: Tuesday, January 10, 2017 9:58 AM
To: Serg Melikyan 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Thanks for the link. I do look at the Jenkins status for high-level info, but 
it’s hard to find out the things I need from that, which are, to start related 
to how a developer deploys a simple fuel-based scenario (e.g. os-nosdn-nonha) 
in the lab

-  What has changed since 
http://artifacts.opnfv.org/fuel/colorado/3.0/docs/installationprocedure/index.html
 (in general are there any draft Danube docs yet)

-  Is booting the fuel ISO the only option, or as with other installers 
can we build/deploy on the fly with a simple bash script (deploy.sh) after 
cloning the repo

-  If booting the fuel ISO is the only option, what are the 
requirements for the jumphost, e.g. can this be done in a virt-manager VM (and 
how) or does it need to be bare metal, what are the host requirements (minimum) 
for the jumphost, etc

-  How is virtual deployment of the fuel master achieved (the install 
doc above does not specify the details) – it’s not clear if this is different 
from booting the fuel ISO in a VM

-  If supported, what are the minimum requirements for virtual deploy

-  What are the minimum requirements for bare metal lab servers, e.g. 
as I have been using will this work

o   Three Intel NUC i7 machines with two NICs, wake-on-lan + PXE boot (no 
IPMI), 16GB memory

Thanks,
Bryan Sullivan | AT&T

From: Serg Melikyan [mailto:smelik...@mirantis.com]
Sent: Tuesday, January 10, 2017 7:59 AM
To: SULLIVAN, BRYAN L mailto:bs3...@att.com>>
Cc: 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Hi Bryan,

indeed IRC channel mentioned on our wiki page was wrong, I have updated wiki 
page - our actively used IRC channel is #opnfv-fuel.

You can track our CI by the following link: 
http://build.opnfv.org/ci/view/fuel/ which has corresponding jobs for master 
which is Denube right now.

On Tue, Jan 10, 2017 at 7:20 AM, SULLIVAN, BRYAN L 
mailto:bs3...@att.com>> wrote:
Hi all Fuel team members,

I’m looking for some guidance on how to track Fuel status for Danube and how to 
contact the Fuel team other than email, which we all have too much of. I see 
some info at https://wiki.opnfv.org/display/fuel/Fuel+Opnfv but it seems that 
the irc channel referenced (opnfv-bgs) has been idle for a while, so that’s 
clearly not where the OPNFV Fuel team hangs out.

But the basic question is whether Fuel is ready for Danube testing, e.g. has 
been updated to OpenStack Newton. The Copper project would like to help in the 
testing of Congress, and for Models and VES I want to start 
developing/verifying support under Fuel-based installs.

Please let me know where you guys hang out on IRC, Slack, Trello, or whatever, 
if we can start testing Fuel for Danube yet, and how to track the status of 
Fuel for Danube overall.

Thanks,
Bryan Sullivan | AT&T


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



--
Serg Melikyan, Development Manager at Mirantis, Inc.
http://mirantis.com<http://mirantis.com/> | 
smelik...@mirantis.com<mailto:smelik...@mirantis.com> | +1 (650) 440-8979
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

Re: [opnfv-tech-discuss] [polestar] Reminder of call this thursday 11AM US EST - also send me suggestions on when to do a F2F

[SULLIVAN, BRYAN L]

The OPNFV Hackfest is still in discussion, but at Orange labs in Paris or north 
of Paris (can’t recall the city). Morgan will know.

Thanks,
Bryan Sullivan | AT&T

From: Pierre Lynch [mailto:ply...@ixiacom.com]
Sent: Wednesday, January 11, 2017 6:48 AM
To: Ash Young 
Cc: SULLIVAN, BRYAN L ; opnfv-tech-discuss 

Subject: Re: [opnfv-tech-discuss] [polestar] Reminder of call this thursday 
11AM US EST - also send me suggestions on when to do a F2F

When and where (more precisely) is that April Hackfest? I don’t see it on the 
Events page of the wiki.

Thanks,

Pierre




On Jan 11, 2017, at 9:42 AM, Ash Young 
mailto:a...@yunify.org>> wrote:

I'm so far planning on 3 events: April (ONS), May (OpenStack), and June (OPNFV).

On Wed, Jan 11, 2017 at 6:06 AM, SULLIVAN, BRYAN L 
mailto:bs3...@att.com>> wrote:
OPNFV Hackfest in April (France).
Thru May that’s about it, then there’s the OPNFV Summit in June (Beijing).

Thanks,
Bryan Sullivan | AT&T

From: 
opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>
 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org<mailto:opnfv-tech-discuss-boun...@lists.opnfv.org>]
 On Behalf Of Margaret Chiosi
Sent: Tuesday, January 10, 2017 8:27 PM
To: opnfv-tech-discuss 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
Subject: [opnfv-tech-discuss] [polestar] Reminder of call this thursday 11AM US 
EST - also send me suggestions on when to do a F2F

Folks:
Sounds like ONS may be the best time for us to do F2F vs Openstack in Atlanta 
next month.
Let me know which conferences you will be attending to see if we can get a 
quorum at one of these:
1. Openstack Atlanta, Feb
2. Openstack Boston, May?
3. ONS Santa Clara, April
4. Layer 123 Santa Clara, April
4. Others?

--
Margaret Chiosi

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.opnfv.org%2Fmailman%2Flistinfo%2Fopnfv-tech-discuss&data=01%7C01%7Cplynch%40ixiacom.com%7Cc8f2209f13dd4f385ce108d43a3011d4%7C069fd614e3f843728e18cd06724a9b23%7C0&sdata=4AyliSTuAGYsaic5R3BgsI2O4fGOo8LARybPE%2BR4WSw%3D&reserved=0>

___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.opnfv.org%2Fmailman%2Flistinfo%2Fopnfv-tech-discuss&data=01%7C01%7Cplynch%40ixiacom.com%7Cc8f2209f13dd4f385ce108d43a3011d4%7C069fd614e3f843728e18cd06724a9b23%7C0&sdata=4AyliSTuAGYsaic5R3BgsI2O4fGOo8LARybPE%2BR4WSw%3D&reserved=0

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

Re: [opnfv-tech-discuss] [OPNFV] VNF on boarding: Q&A Functest versus orchestrator projects

[SULLIVAN, BRYAN L]

Same. Here.
Is this meeting happening? Can't we use an OPNFV GTM bridge?

Thanks,
Bryan Sullivan | AT&T

From: Yunxia Chen [mailto:helen.c...@huawei.com]
Sent: Wednesday, January 11, 2017 8:17 AM
To: Yang Xu (Yang, Fixed Network) ; RICHOMME Morgan 
IMT/OLN ; zhao.huab...@zte.com.cn; 
meng.zhaoxi...@zte.com.cn; by...@etri.re.kr; navid.nika...@eurecom.fr; 
wlu...@bupt.edu.cn; cs15mtech01...@iith.ac.in; cs15mtech01...@iith.ac.in; 
opnfv-tech-discuss@lists.opnfv.org; Prakash Ramchandran 
; giuseppe.care...@fokus.fraunhofer.de; 
narinder.gu...@canonical.com; bouch...@live.fr; Olga Havel 
; dmcbr...@linuxfoundation.org; SULLIVAN, BRYAN L 
; jose.laus...@ericsson.com; michael.pa...@tu-berlin.de; 
lorenzo.tomas...@fokus.fraunhofer.de; huang.leib...@zte.com.cn; Thajudheen 
Rajak 
Subject: RE: [OPNFV] VNF on boarding: Q&A Functest versus orchestrator projects

I experienced the same thing: cannot dial in.

Regards,

Helen Chen


_
From: Yang Xu (Yang, Fixed Network)
Sent: Wednesday, January 11, 2017 8:11 AM
To: RICHOMME Morgan IMT/OLN; 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>; 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>; 
by...@etri.re.kr<mailto:by...@etri.re.kr>; 
navid.nika...@eurecom.fr<mailto:navid.nika...@eurecom.fr>; 
wlu...@bupt.edu.cn<mailto:wlu...@bupt.edu.cn>; 
cs15mtech01...@iith.ac.in<mailto:cs15mtech01...@iith.ac.in>; 
cs15mtech01...@iith.ac.in<mailto:cs15mtech01...@iith.ac.in>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
Prakash Ramchandran; 
giuseppe.care...@fokus.fraunhofer.de<mailto:giuseppe.care...@fokus.fraunhofer.de>;
 narinder.gu...@canonical.com<mailto:narinder.gu...@canonical.com>; 
bouch...@live.fr<mailto:bouch...@live.fr>; Olga Havel; 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>; 
bs3...@att.com<mailto:bs3...@att.com>; 
jose.laus...@ericsson.com<mailto:jose.laus...@ericsson.com>; 
michael.pa...@tu-berlin.de<mailto:michael.pa...@tu-berlin.de>; 
lorenzo.tomas...@fokus.fraunhofer.de<mailto:lorenzo.tomas...@fokus.fraunhofer.de>;
 Yunxia Chen; huang.leib...@zte.com.cn<mailto:huang.leib...@zte.com.cn>; 
Thajudheen Rajak
Subject: RE: [OPNFV] VNF on boarding: Q&A Functest versus orchestrator projects


Hi Morgan,

I dialed US number United States   +1 929-322-2258 with 437219548#, but was 
kicked out every time. What's the reason?

Thanks,

-Yang Xu
Huawei

-Original Appointment-
From: RICHOMME Morgan IMT/OLN
Sent: Wednesday, January 11, 2017 11:08 AM
To: RICHOMME Morgan IMT/OLN; 
zhao.huab...@zte.com.cn<mailto:zhao.huab...@zte.com.cn>; 
meng.zhaoxi...@zte.com.cn<mailto:meng.zhaoxi...@zte.com.cn>; 
by...@etri.re.kr<mailto:by...@etri.re.kr>; 
navid.nika...@eurecom.fr<mailto:navid.nika...@eurecom.fr>; 
wlu...@bupt.edu.cn<mailto:wlu...@bupt.edu.cn>; 
cs15mtech01...@iith.ac.in<mailto:cs15mtech01...@iith.ac.in>; 
cs15mtech01...@iith.ac.in<mailto:cs15mtech01...@iith.ac.in>; 
opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org>; 
Prakash Ramchandran; 
giuseppe.care...@fokus.fraunhofer.de<mailto:giuseppe.care...@fokus.fraunhofer.de>;
 narinder.gu...@canonical.com<mailto:narinder.gu...@canonical.com>; 
bouch...@live.fr<mailto:bouch...@live.fr>; Olga Havel; 
dmcbr...@linuxfoundation.org<mailto:dmcbr...@linuxfoundation.org>; 
bs3...@att.com<mailto:bs3...@att.com>; 
jose.laus...@ericsson.com<mailto:jose.laus...@ericsson.com>; 
michael.pa...@tu-berlin.de<mailto:michael.pa...@tu-berlin.de>; 
lorenzo.tomas...@fokus.fraunhofer.de<mailto:lorenzo.tomas...@fokus.fraunhofer.de>;
 Yunxia Chen; huang.leib...@zte.com.cn<mailto:huang.leib...@zte.com.cn>; 
Thajudheen Rajak; Yang Xu (Yang, Fixed Network)
Subject: [OPNFV] VNF on boarding: Q&A Functest versus orchestrator projects
When: Wednesday, January 11, 2017 10:00 AM-11:00 AM (UTC-05:00) Eastern Time 
(US & Canada).
Where: Conf Bridge (see details in the mails)


Sorry bad bridge (booked for yesterday)
I created a new one...


Hello,

We hereby confirm the scheduling of your conference.

NamePasswordBridge no.  Date (-MM-DD)   Start time  
Time zone
OPNFV   123456789   +33 4 37 21 95 48   2017-01-10  17:00   
(UTC+01:00) Brussels, Copenhagen, Madrid, Paris

You can provide those invited to participate with the following links, allowing 
them to join the conference easily in just a few clicks:

from INTRANET : click here
from INTERNET : click here

In providing these links, you do not need to give a reminder of the conference 
name, its password or the bridge number, where applicable, in your invitation.
These links remain valid even if you should modify your conference at a later 
stage (name, password, date, start time, bridge

Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

[SULLIVAN, BRYAN L]

Thanks for the help here and on IRC – much appreciated.
One other question as asked on IRC: The deploy.sh script requires a "-b 
base-uri" parameter which is the "stack-configuration" location. But there is 
no spec of what needs to be at that location/resource (I’m assuming this is an 
input, not output) - at least I can't find it. Any guidance?

Thanks,
Bryan Sullivan | AT&T

From: Michael Polenchuk [mailto:mpolenc...@mirantis.com]
Sent: Wednesday, January 11, 2017 8:03 AM
To: SULLIVAN, BRYAN L 
Cc: opnfv-tech-discuss@lists.opnfv.org
Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs?

Hi Bryan,
Please see answers inline ...


Thanks for the link. I do look at the Jenkins status for high-level info, but 
it’s hard to find out the things I need from that, which are, to start related 
to how a developer deploys a simple fuel-based scenario (e.g. os-nosdn-nonha) 
in the lab

-  What has changed since 
http://artifacts.opnfv.org/fuel/colorado/3.0/docs/installationprocedure/index.html
 (in general are there any draft Danube docs yet)
As I know nothing significant has changed in terms of installation procedure.

-  Is booting the fuel ISO the only option, or as with other installers 
can we build/deploy on the fly with a simple bash script (deploy.sh) after 
cloning the repo
Please refer at 
http://lists.openstack.org/pipermail/openstack-dev/2016-September/103969.html

-  If booting the fuel ISO is the only option, what are the 
requirements for the jumphost, e.g. can this be done in a virt-manager VM (and 
how) or does it need to be bare metal, what are the host requirements (minimum) 
for the jumphost, etc
This could be either virtual or baremetal (min RAM is ~2Gb, recommended 3Gb+ 
for fuel master node)

-  How is virtual deployment of the fuel master achieved (the install 
doc above does not specify the details) – it’s not clear if this is different 
from booting the fuel ISO in a VM
deploy.sh script will do a trick (only thing is needed to install missing 
packages), it'll create all of vms, boot them ... and finally deploy a cluster 
as well:
opnfv-fuel/ci# ./deploy.sh -b file:///tmp/opnfv-fuel/deploy/config -l 
devel-pipeline -p default -s no-ha_nfv-ovs_heat_ceilometer_scenario.yaml -i 
file:///tmp/opnfv.iso

ready-to-use ISO you could get at 
http://artifacts.opnfv.org/fuel/latest.properties (OPNFV_ARTIFACT_URL=)

-  If supported, what are the minimum requirements for virtual deploy
RAM 10-11Gb for controllers, ram of computes depends on required workloads 
(1Gb+)

-  What are the minimum requirements for bare metal lab servers, e.g. 
as I have been using will this work
The same as above.


--
  Michael Polenchuk
  Private Cloud / Mirantis Inc.
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss