[opnfv-tech-discuss] [KVM] Weekly meeting for KVM enhancements for NFV - Agenda 11/10/2016

[Reddy, Raghuveer]

Meeting logistics - https://wiki.opnfv.org/nfv-kvm
Weekly on Thursday at 
2330 
UTC (4:30PM PDT)
Goto Meeting Link

Agenda:

1)  Project Status/Milestone check

2)  Jira Item Review

3)  Opens

Regards,
-Raghu
Ph: 408 765 4620
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

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

[morgan.richomme]

+2

short way: redirection docs.opnfv.org to
http://artifacts.opnfv.org/opnfvdocs/colorado/docs/documentation/index.html
to be done, I think we can send a ticket to helpdesk but then only
colorado will be referenced

mid way: we can also reuse the structure done for test reporting
http://testresults.opnfv.org/reporting/ (the code is on releng:
https://git.opnfv.org/cgit/releng/tree/utils/test/reporting, it is based
on a free HTML5 template) and adapt if for docs.opnfv.org (i.e. add
links to the colorado/brahmaputra docs)
it is easy to do

ideally we should have something like OpenStack

it is up to opnfvdocs to decide

/Morgan



Le 10/11/2016 à 02:58, Yujun Zhang a écrit :
> 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


-- 
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


_

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

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

[Wenjing Chu]

Yes, this thread was on the docs project mails and I believe it’s been 
considered/planned for D release. That was about a month ago.
Sophia Wallin can you say more?

Wenjing

From: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, 
BRYAN L
Sent: Wednesday, November 09, 2016 6:10 PM
To: Yujun Zhang ; TECH-DISCUSS OPNFV 

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

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 
mailto:opnfv-tech-discuss@lists.opnfv.org>>
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] [qtip] Attention required for project folder structure

[Yujun Zhang]

Dear qtip runners,

We planned a folder reorganization[1] in this sprint. And it is quite
important to complete it ASAP so other tasks won't get blocked.

So I propose to merge a patch set[2] to setup the base folder structure.

The existing features might get broken. But I believe it will be easier to
fix them with the target structure in place.

What do you think? Please reply before tomorrow. Thank you.

[1] https://jira.opnfv.org/browse/QTIP-131
[2] https://gerrit.opnfv.org/gerrit/#/c/24133/
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] 答复: Who can help run weekly technical discussion tomorrow?

[Tianhongbo]

Hi Bin:

If needed, I can try.

Best Regards

hongbo

-邮件原件-
发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 HU, BIN
发送时间: 2016年11月10日 1:14
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] Who can help run weekly technical discussion tomorrow?

Hello team,

I have been sick since yesterday afternoon, and can hardly sit because of 
dizziness. I need to go to doctor's office to check it out soon.

Can one of you help run weekly technical discussion tomorrow? The agenda is on 
wiki. Primarily Morgan will discuss opnfv vision and Danube priorities, and 
Dave N wants to discuss certification program topic.

If no one is available to run it, we can cancel it.

Thanks

Bin
___
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] [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

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

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

[Yujun Zhang]

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] 答复: [dovetail] JIRA issues management

[Lijun (Matthew)]

hi Leo

thanks, It looks clear for me now.


best regards

/MatthewLi


发件人: opnfv-tech-discuss-boun...@lists.opnfv.org 
[opnfv-tech-discuss-boun...@lists.opnfv.org] 代表 Leo Wang 
[grakiss...@hotmail.com]
发送时间: 2016年11月9日 17:06
收件人: opnfv-tech-discuss@lists.opnfv.org
主题: [opnfv-tech-discuss] [dovetail] JIRA issues management

Hi all

Dovetail project has so many issues on JIRA now, so it’s time to manage them in 
a more effective way

These issues should be organized into several epic issues for a clear view.

So guys contributing to dovetail may check your lira task that if your task is 
linked to  a propitiate epic issue.

Do not hesitate to tell us if some issues are missing or in a wrong place, we 
can correct the epic link then.

Also JIRA get this handful tool “board" to manage all issues in one page

here is the board “Dovetail Overview", please punch the link for details:

https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=149


BR

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

[opnfv-tech-discuss] [doctor] performance profile design spec

[Yujun Zhang]

Hi, doctors,

Would you spare sometime to review the spec for performance profile[1]?

The motivation for this feature is described in JIRA: DOCTOR-72 [2]

Please feel free to give comments.

[1]: https://gerrit.opnfv.org/gerrit/#/c/23963/
[2]: https://jira.opnfv.org/browse/DOCTOR-72
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [it-infrastructure-alerts] [announce] OPNFV JIRA Maintainance: 2016-11-20

[Aric Gardner]

Hello,

The index of our JIRA system is currently broken.

On sunday Nov 20th I plan to apply the fix detailed here:
https://confluence.atlassian.com/jirakb/how-to-fix-a-jira-application-that-is-unable-to-perform-a-background-re-index-at-this-time-error-316637947.html

I will be stopping the Jira service and preforming a full backup
before modifying the database.
Afterwards I will be giving the machine a reboot and kernel upgrade.

Please email helpdesk if you have any further questions.

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] [mano-wg] [MANO] Meeting #11 agenda plus summary updates

[Prakash Ramchandran]

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.
 *   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. 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.

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 )

 *   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 
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.
 *   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.
  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.
  2.  What should be test strategy (refer  item 3 Nov 2 meeting) - Await 
FUNCTEST-237 response from Morgan and Action for MANO teams to create new 
FUNCTEST JIRA ticket based on vIMS use case.
  3.  Where is the test plan and how will the projects share the testing codes? 
- Proposal to be discussed next week with inputs for Giuseppe of Orchestra 
(OpenBaton team).
  4.  How would the results of collaboration through MANO WG reflect in 
D-release of OPNFV. - A template to be 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.  What is reasonable deliverable expected from UNH Plug-fest for 
cross-project co-ordination? - The Open-O team from China Mobile plans to demo 
OPEN-O and OpenBaton team indicated that they may not be bale to make it to UNH 
Plug-fest but plan to Demo their efforts in ETSI Plugtest in February.
Attendees: irc+GTM
aimeeu,B_Smith,bryan_att,ChrisPriceAB,collabot`,dmcbride,ljlamers, rprakash, 
yingjun Li, Arthur Tyloc, Narinder Gupta
Thanks
Prakash

[logo_huawei] R&D USA
FutureWei Technologies, Inc
Email: prakash.ramchand...@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] Who can help run weekly technical discussion tomorrow?

[HU, BIN]

Hello team,

I have been sick since yesterday afternoon, and can hardly sit because of 
dizziness. I need to go to doctor's office to check it out soon.

Can one of you help run weekly technical discussion tomorrow? The agenda is on 
wiki. Primarily Morgan will discuss opnfv vision and Danube priorities, and 
Dave N wants to discuss certification program topic.

If no one is available to run it, we can cancel it.

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] [Apex] deployment error

[Tim Rozet]

Hi Patrick,
For the Undercloud VM to bridge to your host, it needs to be able to get the IP 
information off of the host interfaces.  It does this by checking your ifcfg 
files under /etc/sysconfig/network-scripts for the interface you specify for 
each network.  Can you check that enp1s0f1 ifcfg file is not set to dhcp and 
has IP and NETMASK/PREFIX settings in the file?

Thanks,

Tim Rozet
Red Hat SDN Team

- Original Message -
From: "Francois Guay (A214312)" 
To: "Jamo Luhrsen" , "Patrick Lemay" 
, opnfv-tech-discuss@lists.opnfv.org
Cc: "Jocelyn Poulin (6007251)" 
Sent: Friday, November 4, 2016 2:59:14 PM
Subject: Re: [opnfv-tech-discuss] [Apex] deployment error

Patrick, Jamo,

I did the libvirt-python install and it solve the problem. (see attached)

Now, we need to add the two missing nodes to get the five required nodes. I 
will give it a try and let you know.

Thanks Jamo.

Patrick, I'll let you share with Jamo what you did with the admin_network and 
public_network stuff.



François

-Original Message-
From: Jamo Luhrsen [mailto:jluhr...@redhat.com] 
Sent: 4 novembre 2016 12:04
To: Lemay, Patrick; opnfv-tech-discuss@lists.opnfv.org
Cc: Poulin, Jocelyn (6007251); Guay, Francois (A214312)
Subject: Re: [opnfv-tech-discuss] [Apex] deployment error

Patrick,

I've had similar problems trying to get apex baremetal to work on the jumphost 
I'm working with.  I hit the libvirt issue the other day.  I think I just did a 
"yum install libvirt-python"  try that.

I'm still stuck on what I need to do with the admin_network, public_network 
stuff that I think you have overcome recently.  Can you recap the steps you 
took?

JamO

On 11/04/2016 08:47 AM, Lemay, Patrick wrote:
> Hi I finally create the br-public by hand instead of script. It work 
> but now I’m stock to another. «ImportError: No module named libvirt». 
> I’m using your deployment cd. All the dependencies should be install. I start 
> to tshoot the problem but I’m sure that you’ve already see that bug.
> 
>  
> 
> All python version installed:
> 
> [root@jumphost opnfv-apex]# python
> 
> python  python2 python2.7   python3 python3.4   python3.4m 
> 
>  
> 
> Output from the opnfv-deploy script:
> 
> INFO: virsh networks set:
> 
>  Name State  Autostart Persistent
> 
> --
> 
> admin_networkactive yes   yes
> 
> default  active yes   yes
> 
> public_network   active yes   yes
> 
>  
> 
> All dependencies installed and running
> 
> 4 Nov 10:58:33 ntpdate[27293]: adjust time server 206.108.0.133 offset 
> -0.002592 sec
> 
> Volume undercloud exists. Deleting Existing Volume 
> /var/lib/libvirt/images/undercloud.qcow2
> 
> Vol undercloud.qcow2 deleted
> 
>  
> 
> Vol undercloud.qcow2 created
> 
>  
> 
> Traceback (most recent call last):
> 
>   File "/usr/libexec/openstack-tripleo/configure-vm", line 8, in 
> 
> 
>import libvirt
> 
> ImportError: No module named libvirt
> 
>  
> 
>  
> 
> Thanks,
> 
>  
> 
>  
> 
>  
> 
>  
> 
> *From:*Lemay, Patrick
> *Sent:* November-01-16 11:42 AM
> *To:* 'opnfv-tech-discuss@lists.opnfv.org'
> *Cc:* Bernier, Daniel (520165); Guay, Francois (A214312); Poulin, 
> Jocelyn (6007251)
> *Subject:* Bell deployment config
> 
>  
> 
> Hi guys, I have some issues regarding opnfv baremetal deployment. I 
> install a jumphost from opnfv cd. I configure the inventory with IPMI ip mac 
> and users.
> 
>  
> 
> I’m not sure that I configure the network_settings correctly for 
> public_network.
> 
>  
> 
>  
> 
> For the deployment I use pod 2 and pod 3 from the drawing. The server 
> Catherine is use for the jumphost. Interface enp1s0f0 is for pxe and 
> enp1s0f1 is for public_network . The other 5 servers are for 
> deployment IPMI ready. All interfaces in vlan
> 1020 are pxe ready and disk are configured raid 1. I have a problem deploying 
> undercloud.
> 
>  
> 
>  
> 
> I have this error related to the undercloud deployment:
> 
> INFO: Creating Virsh Network: admin_network & OVS Bridge: br-admin
> 
> INFO: Creating Virsh Network: public_network & OVS Bridge: br-public
> 
> INFO: Bridges set:
> 
> br-admin
> 
> br-public
> 
> enp1s0f0
> 
> INFO: Interface enp1s0f0 bridged to bridge br-admin for enabled 
> network: admin_network
> 
> /var/opt/opnfv/lib/common-functions.sh: line 18: 5 - ( / 8) : syntax 
> error: operand expected (error token is "/ 8) ")
> 
> ERROR: IPADDR or NETMASK/PREFIX missing for enp1s0f1
> 
> ERROR: Unable to bridge interface enp1s0f1 to bridge br-public for 
> enabled network: public_network
> 
>  
> 
>  
> 
> Could you help please? There is no vmware at all in the setup only baremetal..
> 
>  
> 
> Regards,
> 
>  
> 
>  
> 
>  
> 
> Patrick Lemay
> 
> Consultant Managed Services Engineering Bell Canada
> 
> 671 de la Gauchetière O. Bur. 610, Montreal, Quebec  H3B 2M8
> 
> Tel:  (514) 870-1540
> 
>  
> 
> 
> 
> _

[opnfv-tech-discuss] [SFC] Fwd: sfc fd.io/vpp scenarios

[Brady Allen Johnson]

Thanks to Ferenc for looking up the actual scenario names.

Brady

 Forwarded Message 
Subject:sfc fd.io/vpp scenarios
Date:   Wed, 9 Nov 2016 16:59:32 +0100
From:   Ferenc Cserepkei 
To: Brady Allen Johnson 



Hello Brady,

here they are: https://wiki.opnfv.org/display/SWREL/Danube+Scenario+Status

os-odl_l2-sfc-fdio-ha 	Apex 	Brady Johnson 
 			


os-odl_l2-sfc-fdio-ha 	Fuel 	Brady Johnson 
 			


Regards:

Ferenc

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

[opnfv-tech-discuss] [SFC] weekly meeting, minutes of meeting, Nov 9, 2016

[Brady Allen Johnson]

Here are the Minutes of meeting from today's meeting:

http://ircbot.wl.linuxfoundation.org/meetings/opnfv-sfc/2016/opnfv-sfc.2016-11-09-15.05.html

Regards,

Brady


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

[opnfv-tech-discuss] Infra Working Group Weekly Meeting

[Morgan, Jack]

BEGIN:VCALENDAR
METHOD:REQUEST
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="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='opnfv-te
 ch-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Bob Monkm
 an:MAILTO:bob.monk...@arm.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=Alexandru
  Avadanii:MAILTO:alexandru.avada...@enea.com
DESCRIPTION;LANGUAGE=en-US:The "Infra Working Group" plans and tracks infra
 structure cross project initiatives and reports these up to the TSC to ens
 ure we are able to provide sufficient resources and support for developmen
 t and release infrastructure.\n\nWiki Page for topics and meeting agendas 
 at https://wiki.opnfv.org/display/INF/Infra+Working+Group\n\nWeekly on Wed
 nesday at 15:00 UTC (8am PST)\nGTM Link https://global.gotomeeting.com/joi
 n/773318405\nMinutes at Meetings#InfraWorkingGroupMeeting\nIRC #opnfv-meeting - freenode.net\nChaired by Jack Morgan\, Fatih Degirmenci\, Ulrich Klebe
 r\nYou can also dial in using your phone with Access Code: 773-318-405\n  
 United States +1 (224) 501-3312\n  Australia (Long distance): +61 2 8355 1
 039\n  Austria (Long distance): +43 7 2088 1033\n  Belgium (Long distance)
 : +32 (0) 28 93 7001\n  Canada (Long distance): +1 (647) 497-9379\n  Denma
 rk (Long distance): +45 69 91 89 33\n  Finland (Long distance): +358 (0) 9
 42 41 5770\n  France (Long distance): +33 (0) 170 950 585\n  Germany (Long
  distance): +49 (0) 692 5736 7205\n  Ireland (Long distance): +353 (0) 19 
 030 050\n  Italy (Long distance): +39 0 693 38 75 50\n  Netherlands (Long 
 distance): +31 (0) 208 080 208\n  New Zealand (Long distance): +64 9 925 0
 481\n  Norway (Long distance): +47 21 54 82 21\n  Spain (Long distance): +
 34 911 82 9890\n  Sweden (Long distance): +46 (0) 853 527 817\n  Switzerla
 nd (Long distance): +41 (0) 435 0167 65\n  United Kingdom (Long distance):
  +44 (0) 330 221 0099\n\n\n
SUMMARY;LANGUAGE=en-US:Infra Working Group Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20161109T08
DTEND;TZID=Pacific Standard Time:20161109T09
UID:04008200E00074C5B7101A82E00860D8B113D5C2D101000
 01000887EAAC68FE7944E82284BCE0D07B8ED
RECURRENCE-ID;TZID=Pacific Standard Time:20161109T08
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T10Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:10
LOCATION;LANGUAGE=en-US:#opnfv-meeting and GTM
X-MICROSOFT-CDO-APPT-SEQUENCE:10
X-MICROSOFT-CDO-OWNERAPPTID:-2041944096
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:TRUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Infra Working Group Weekly Meeting

[Morgan, Jack]

BEGIN:VCALENDAR
METHOD:REQUEST
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="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN='opnfv-te
 ch-disc...@lists.opnfv.org':MAILTO:opnfv-tech-discuss@lists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:The "Infra Working Group" plans and tracks infra
 structure cross project initiatives and reports these up to the TSC to ens
 ure we are able to provide sufficient resources and support for developmen
 t and release infrastructure.\n\nWiki Page for topics and meeting agendas 
 at https://wiki.opnfv.org/display/INF/Infra+Working+Group\n\nWeekly on Wed
 nesday at 15:00 UTC (8am PST)\nGTM Link https://global.gotomeeting.com/joi
 n/773318405\nMinutes at Meetings#InfraWorkingGroupMeeting\nIRC #opnfv-meeting - freenode.net\nChaired by Jack Morgan\, Fatih Degirmenci\, Ulrich Klebe
 r\nYou can also dial in using your phone with Access Code: 773-318-405\n  
 United States +1 (224) 501-3312\n  Australia (Long distance): +61 2 8355 1
 039\n  Austria (Long distance): +43 7 2088 1033\n  Belgium (Long distance)
 : +32 (0) 28 93 7001\n  Canada (Long distance): +1 (647) 497-9379\n  Denma
 rk (Long distance): +45 69 91 89 33\n  Finland (Long distance): +358 (0) 9
 42 41 5770\n  France (Long distance): +33 (0) 170 950 585\n  Germany (Long
  distance): +49 (0) 692 5736 7205\n  Ireland (Long distance): +353 (0) 19 
 030 050\n  Italy (Long distance): +39 0 693 38 75 50\n  Netherlands (Long 
 distance): +31 (0) 208 080 208\n  New Zealand (Long distance): +64 9 925 0
 481\n  Norway (Long distance): +47 21 54 82 21\n  Spain (Long distance): +
 34 911 82 9890\n  Sweden (Long distance): +46 (0) 853 527 817\n  Switzerla
 nd (Long distance): +41 (0) 435 0167 65\n  United Kingdom (Long distance):
  +44 (0) 330 221 0099\n\n\n
RRULE:FREQ=WEEKLY;INTERVAL=1;BYDAY=WE;WKST=SU
EXDATE;TZID=Pacific Standard Time:20160622T08
SUMMARY;LANGUAGE=en-US:Infra Working Group Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160615T08
DTEND;TZID=Pacific Standard Time:20160615T09
UID:04008200E00074C5B7101A82E00860D8B113D5C2D101000
 01000887EAAC68FE7944E82284BCE0D07B8ED
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T144438Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:9
LOCATION;LANGUAGE=en-US:#opnfv-meeting and GTM
X-MICROSOFT-CDO-APPT-SEQUENCE:9
X-MICROSOFT-CDO-OWNERAPPTID:-2041944096
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:TRUE
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:REMINDER
TRIGGER;RELATED=START:-PT15M
END:VALARM
END:VEVENT
BEGIN:VEVENT
SUMMARY:Infra Working Group Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160629T08
DTEND;TZID=Pacific Standard Time:20160629T09
UID:04008200E00074C5B7101A82E00860D8B113D5C2D101000
 01000887EAAC68FE7944E82284BCE0D07B8ED
RECURRENCE-ID;TZID=Pacific Standard Time:20160629T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T144438Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:9
LOCATION:#opnfv-meeting and GTM
X-MICROSOFT-CDO-APPT-SEQUENCE:9
X-MICROSOFT-CDO-OWNERAPPTID:-2041944096
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:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Infra Working Group Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160817T08
DTEND;TZID=Pacific Standard Time:20160817T09
UID:04008200E00074C5B7101A82E00860D8B113D5C2D101000
 01000887EAAC68FE7944E82284BCE0D07B8ED
RECURRENCE-ID;TZID=Pacific Standard Time:20160817T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T144438Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:9
LOCATION:#opnfv-meeting and GTM
X-MICROSOFT-CDO-APPT-SEQUENCE:9
X-MICROSOFT-CDO-OWNERAPPTID:-2041944096
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:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Infra Working Group Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160824T08
DTEND;TZID=Pacific Standard Time:20160824T09
UID:04008200E00074C5B7101A82E00860D8B113D5C2D101000
 01000887EAAC68FE7944E82284BCE0D07B8ED
RECURRENCE-ID;TZID=Pacific Standard Time:20160824T00
CLASS:PUBL

[opnfv-tech-discuss] Pharos Bi-Weekly Meeting

[Morgan, Jack]

BEGIN:VCALENDAR
METHOD:REQUEST
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="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@l
 ists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'SULLIVAN
 , BRYAN L'":MAILTO:bs3...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="'DRUTA, D
 AN'":MAILTO:dd5...@att.com
DESCRIPTION;LANGUAGE=en-US:Pharos Team..\n\nI’m scheduling a bi-weekly me
 eting to cover Pharos specific topics. Agenda and meeting topics on wiki.\n\nGoToMeeting (Wed
 nesday at 6:00 am PST / 13:00 UTC)\nPlease join my meeting from your compu
 ter\, tablet or smartphone.\nhttps://global.gotomeeting.com/join/349781141
 \n\nYou can also dial in using your phone.\nUnited States (Toll-free): 1 8
 66 899 4679\nUnited States : +1 (312) 757-3117\n\nAccess Code: 349-781-141
 \nMore phone numbers\nAustralia : +61 2 8355 1039\nAustria : +43 7 2088 10
 33\nBelgium : +32 (0) 28 93 7001\nCanada : +1 (647) 497-9379\nDenmark : +4
 5 69 91 89 21\nFinland : +358 (0) 923 17 0555\nFrance : +33 (0) 170 950 58
 5\nGermany : +49 (0) 692 5736 7301\nIreland : +353 (0) 19 030 050\nItaly :
  +39 0 693 38 75 50\nNetherlands : +31 (0) 208 080 208\nNew Zealand : +64 
 9 925 0481\nNorway : +47 21 54 82 21\nSpain : +34 911 82 9890\nSweden : +4
 6 (0) 853 527 817\nSwitzerland : +41 (0) 435 0167 65\nUnited Kingdom : +44
  (0) 330 221 0099\n\n
SUMMARY;LANGUAGE=en-US:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20161109T06
DTEND;TZID=Pacific Standard Time:20161109T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20161109T06
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T144319Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:10
LOCATION;LANGUAGE=en-US:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:10
X-MICROSOFT-CDO-OWNERAPPTID:529696736
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] Pharos Bi-Weekly Meeting

[Morgan, Jack]

BEGIN:VCALENDAR
METHOD:REQUEST
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="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@l
 ists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Pharos Team..\n\nI’m scheduling a bi-weekly me
 eting to cover Pharos specific topics. Agenda and meeting topics on wiki.\n\nGoToMeeting (Wed
 nesday at 6:00 am PST / 13:00 UTC)\nPlease join my meeting from your compu
 ter\, tablet or smartphone.\nhttps://global.gotomeeting.com/join/349781141
 \n\nYou can also dial in using your phone.\nUnited States (Toll-free): 1 8
 66 899 4679\nUnited States : +1 (312) 757-3117\n\nAccess Code: 349-781-141
 \nMore phone numbers\nAustralia : +61 2 8355 1039\nAustria : +43 7 2088 10
 33\nBelgium : +32 (0) 28 93 7001\nCanada : +1 (647) 497-9379\nDenmark : +4
 5 69 91 89 21\nFinland : +358 (0) 923 17 0555\nFrance : +33 (0) 170 950 58
 5\nGermany : +49 (0) 692 5736 7301\nIreland : +353 (0) 19 030 050\nItaly :
  +39 0 693 38 75 50\nNetherlands : +31 (0) 208 080 208\nNew Zealand : +64 
 9 925 0481\nNorway : +47 21 54 82 21\nSpain : +34 911 82 9890\nSweden : +4
 6 (0) 853 527 817\nSwitzerland : +41 (0) 435 0167 65\nUnited Kingdom : +44
  (0) 330 221 0099\n\n
RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=WE;WKST=SU
EXDATE;TZID=Pacific Standard Time:20161026T06
SUMMARY;LANGUAGE=en-US:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160831T06
DTEND;TZID=Pacific Standard Time:20160831T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T144317Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:9
LOCATION;LANGUAGE=en-US:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:9
X-MICROSOFT-CDO-OWNERAPPTID:529696736
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:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160831T06
DTEND;TZID=Pacific Standard Time:20160831T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20160831T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T144317Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:9
LOCATION:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:9
X-MICROSOFT-CDO-OWNERAPPTID:529696736
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:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160914T06
DTEND;TZID=Pacific Standard Time:20160914T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20160914T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T144317Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:9
LOCATION:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:9
X-MICROSOFT-CDO-OWNERAPPTID:529696736
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:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20161012T06
DTEND;TZID=Pacific Standard Time:20161012T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20161012T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T144317Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:9
LOCATION:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:9
X-MICROSOFT-CDO-OWNERAPPTID:529696736
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:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20161109T06
DTEND;TZID=Pacific Standard Time:20161109T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20161109T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T144317Z
TRANS

[opnfv-tech-discuss] Pharos Bi-Weekly Meeting

[Morgan, Jack]

BEGIN:VCALENDAR
METHOD:REQUEST
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="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@l
 ists.opnfv.org
DESCRIPTION;LANGUAGE=en-US:Pharos Team..\n\nI’m scheduling a bi-weekly me
 eting to cover Pharos specific topics. Agenda and meeting topics on wiki.\n\nGoToMeeting (Wed
 nesday at 6:00 am PST / 14:00 UTC)\nPlease join my meeting from your compu
 ter\, tablet or smartphone.\nhttps://global.gotomeeting.com/join/349781141
 \n\nYou can also dial in using your phone.\nUnited States (Toll-free): 1 8
 66 899 4679\nUnited States : +1 (312) 757-3117\n\nAccess Code: 349-781-141
 \nMore phone numbers\nAustralia : +61 2 8355 1039\nAustria : +43 7 2088 10
 33\nBelgium : +32 (0) 28 93 7001\nCanada : +1 (647) 497-9379\nDenmark : +4
 5 69 91 89 21\nFinland : +358 (0) 923 17 0555\nFrance : +33 (0) 170 950 58
 5\nGermany : +49 (0) 692 5736 7301\nIreland : +353 (0) 19 030 050\nItaly :
  +39 0 693 38 75 50\nNetherlands : +31 (0) 208 080 208\nNew Zealand : +64 
 9 925 0481\nNorway : +47 21 54 82 21\nSpain : +34 911 82 9890\nSweden : +4
 6 (0) 853 527 817\nSwitzerland : +41 (0) 435 0167 65\nUnited Kingdom : +44
  (0) 330 221 0099\n\n
RRULE:FREQ=WEEKLY;INTERVAL=2;BYDAY=WE;WKST=SU
EXDATE;TZID=Pacific Standard Time:20161026T06
SUMMARY;LANGUAGE=en-US:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160831T06
DTEND;TZID=Pacific Standard Time:20160831T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T143834Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:5
LOCATION;LANGUAGE=en-US:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:5
X-MICROSOFT-CDO-OWNERAPPTID:529696736
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:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160831T06
DTEND;TZID=Pacific Standard Time:20160831T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20160831T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T143834Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:5
LOCATION:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:5
X-MICROSOFT-CDO-OWNERAPPTID:529696736
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:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20160914T06
DTEND;TZID=Pacific Standard Time:20160914T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20160914T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T143834Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:5
LOCATION:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:5
X-MICROSOFT-CDO-OWNERAPPTID:529696736
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:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20161012T06
DTEND;TZID=Pacific Standard Time:20161012T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20161012T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T143834Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:5
LOCATION:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:5
X-MICROSOFT-CDO-OWNERAPPTID:529696736
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:TRUE
END:VEVENT
BEGIN:VEVENT
SUMMARY:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20161109T06
DTEND;TZID=Pacific Standard Time:20161109T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20161109T00
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T143834Z
TRANS

[opnfv-tech-discuss] Pharos Bi-Weekly Meeting

[Morgan, Jack]

BEGIN:VCALENDAR
METHOD:REQUEST
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="Morgan, Jack":MAILTO:jack.mor...@intel.com
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN=opnfv-tec
 h-discuss (opnfv-tech-discuss@lists.opnfv.org):MAILTO:opnfv-tech-discuss@l
 ists.opnfv.org
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="SULLIVAN,
  BRYAN L":MAILTO:bs3...@att.com
ATTENDEE;ROLE=OPT-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=FALSE;CN="DRUTA, DA
 N":MAILTO:dd5...@att.com
DESCRIPTION;LANGUAGE=en-US:Pharos Team..\n\nI’m scheduling a bi-weekly me
 eting to cover Pharos specific topics. Agenda and meeting topics on wiki.\n\nGoToMeeting (Wed
 nesday at 6:00 am PST / 14:00 UTC)\nPlease join my meeting from your compu
 ter\, tablet or smartphone.\nhttps://global.gotomeeting.com/join/349781141
 \n\nYou can also dial in using your phone.\nUnited States (Toll-free): 1 8
 66 899 4679\nUnited States : +1 (312) 757-3117\n\nAccess Code: 349-781-141
 \nMore phone numbers\nAustralia : +61 2 8355 1039\nAustria : +43 7 2088 10
 33\nBelgium : +32 (0) 28 93 7001\nCanada : +1 (647) 497-9379\nDenmark : +4
 5 69 91 89 21\nFinland : +358 (0) 923 17 0555\nFrance : +33 (0) 170 950 58
 5\nGermany : +49 (0) 692 5736 7301\nIreland : +353 (0) 19 030 050\nItaly :
  +39 0 693 38 75 50\nNetherlands : +31 (0) 208 080 208\nNew Zealand : +64 
 9 925 0481\nNorway : +47 21 54 82 21\nSpain : +34 911 82 9890\nSweden : +4
 6 (0) 853 527 817\nSwitzerland : +41 (0) 435 0167 65\nUnited Kingdom : +44
  (0) 330 221 0099\n\n
SUMMARY;LANGUAGE=en-US:Pharos Bi-Weekly Meeting
DTSTART;TZID=Pacific Standard Time:20161109T06
DTEND;TZID=Pacific Standard Time:20161109T07
UID:04008200E00074C5B7101A82E008F0EC14D714F9D101000
 01000E0F204B45F660247842A338E5586EE5B
RECURRENCE-ID;TZID=Pacific Standard Time:20161109T06
CLASS:PUBLIC
PRIORITY:5
DTSTAMP:20161109T143835Z
TRANSP:OPAQUE
STATUS:CONFIRMED
SEQUENCE:6
LOCATION;LANGUAGE=en-US:GTM and #opnfv-pharos
X-MICROSOFT-CDO-APPT-SEQUENCE:6
X-MICROSOFT-CDO-OWNERAPPTID:529696736
X-MICROSOFT-CDO-BUSYSTATUS:TENTATIVE
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
X-MICROSOFT-CDO-IMPORTANCE:1
X-MICROSOFT-CDO-INSTTYPE:3
X-MICROSOFT-DISALLOW-COUNTER:TRUE
END:VEVENT
END:VCALENDAR
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [SFC] Weekly meeting agenda

[Brady Allen Johnson]

Today, I would like to discuss the following

 * Changes to functest that affected SFC
 * Moving functest SFC code into the OPNFV SFC git repo
 * Boron SR1 and Colorado 3.0

Now that USA has also done the daylight savings time change, the meeting 
time will be back to normal.


Regards,

Brady


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

Re: [opnfv-tech-discuss] [doctor][VES][barometer] OVS link status notifications for OpenStack from collectd - Open Questions

[Christopher Price]

Hi Maryam,

Just going to chime in here as I am want to do on occasion, more or less 
reiterating Alok’s answers but including long and tedious reasoning.

For events I tend to think the events should be reported at a relative level of 
importance from the reporting function.  If my role in the system is to 
maintain a link and that link goes down this is a pretty big thing for me in my 
role.
Aggregation/normalization of the severity of the event should then be handled 
by an aggregative function that understands the context of the notification in 
a broader context.

I guess in my opinion if a link is down I would expect a switching function 
would be issuing a warning or error level event.  The “collector” or host 
application of that function may adjust that level in the context of functional 
redundancy or aggregation.  If the application is aware of the role of the 
switch in the overall system it may inform the switch of how to report these 
events, so configurability would seem a useful function to reduce event 
processing overhead.

/ Chris

On 2016-11-08, 07:51, "opnfv-tech-discuss-boun...@lists.opnfv.org on behalf of 
Tahhan, Maryam"  wrote:

 Hi Folks
 
 For the OVS events collectd plugin we wrote as part of barometer, we are 
currently sending a notification message from collectd with a level that is set 
to WARNING for when the link status is detected to be down. So this means that 
when the status changes from "Unknown" to "down" when a new interface is added 
a warning message will be generated. 


So from a Doctor/VES perspective:
 1. When do you expect to see a warning message vs an informational 
message? When the link status only changes from Up to down 

 2. Do you want to know when the status changes from unknown to down?

 3. Should we allow the notification severity to be configurable for link 
status? Or should we from a collectd point of view provide you with 
informational messages only and let you decide a severity?
 
 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 mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss

[opnfv-tech-discuss] [dovetail] JIRA issues management

[Leo Wang]

Hi all

Dovetail project has so many issues on JIRA now, so it’s time to manage them in 
a more effective way

These issues should be organized into several epic issues for a clear view.

So guys contributing to dovetail may check your lira task that if your task is 
linked to  a propitiate epic issue.

Do not hesitate to tell us if some issues are missing or in a wrong place, we 
can correct the epic link then.

Also JIRA get this handful tool “board" to manage all issues in one page

here is the board “Dovetail Overview", please punch the link for details:

https://jira.opnfv.org/secure/RapidBoard.jspa?rapidView=149


BR

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

[opnfv-tech-discuss] [multisite]Weekly meeting of Nov.10

[joehuang]

Hello, team,

Agenda of Nov.10 2016

* CI Job unstable, https://build.opnfv.org/ci/view/multisite/builds
* Automated multi-site deployment via Jenkins
* tempest job in openstack gate/check
* KB feature implementation

IRC: http://webchat.freenode.net/?channels=opnfv-meeting 8:00-9:00 UTC (During 
winter time, means CET 9:00 AM). Other topics are also welcome in the weekly 
meeting, please reply in this mail.

Best Regards
Chaoyi Huang (joehuang)
___
opnfv-tech-discuss mailing list
opnfv-tech-discuss@lists.opnfv.org
https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss