[opnfv-tech-discuss] Canceled: [netready] NetReady weekly project meeting

BEGIN:VCALENDAR METHOD:CANCEL PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Customized Time Zone BEGIN:STANDARD DTSTART:16010101T03 TZOFFSETFROM:+0200 TZOFFSETTO:+0100 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=-1SU;BYMONTH=10 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

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 wrote: > On the Barometer project (FKA SFQM) call today, I made the following > suggestion that was welcomed by the tea

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

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)

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

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

[opnfv-tech-discuss] [netready] agenda for today's meeting

Hi all, This is the agenda for today's meeting: * Use case: Provider type network administration * Service binding model for Gluon * Gluon OPNFV integration * New use case: ICN * Gluon and OpenStack summit updates * AOB Best regards Georg ___ opnfv-tec

[opnfv-tech-discuss] Weekly Technical Discussion #68

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:16010101T02000

[opnfv-tech-discuss] [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)

Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Planning of D release documentation

The epic name is quite long. Since it is all under OPNFV namespace, we may omit the prefix and use some abbreviation. e.g. Danube docs -- Yujun On Tue, Nov 1, 2016 at 8:18 PM Sofia Wallin wrote: > Hi Maryam, > > Depending on which documents you plan contributing to, create one or more > new sto

Re: [opnfv-tech-discuss] [opnfv-project-leads] Security Vulnerability Classification in OPNFV JIRA

Thanks for Luke to provide such solution for OPNFV projects. A short word in my understanding, security issues should not be exposed to public before it gets fixed. The JIRA security scheme provide us a convenient way to protect such secrets. I would encourage every project to try it out. Step 1

Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Planning of D release documentation

Hi Maryam, Depending on which documents you plan contributing to, create one or more new stories within your project and then add an Epic Link to targeted document, OPNFV Danube Installation and configuration guide, OPNFV Danube User Guide

[opnfv-tech-discuss] Security Vulnerability Classification in OPNFV JIRA

Hi, We now have a JIRA private security scheme that can be requested for assignment to projects. This will allow OPNFV projects to tag security issues raised in JIRA as private. I really would advise projects to make use of this JIRA feature. Being able to work on security fixes under a private

Re: [opnfv-tech-discuss] [opnfv-project-leads] [release][danube] MS1 - Planning - October 25 (tomorrow)

Hi David and Doctor team, I’ve just created doctor entry for D release planning according to our release planning discussion which already completed before the MS1 deadline. https://wiki.opnfv.org/display/SWREL/Doctor+Release+Plan+for+OPNFV+Danube BR, Ryota From: opnfv-project-leads-boun...@

Re: [opnfv-tech-discuss] [opnfv-project-leads] [opnfvdocs] Planning of D release documentation

Hi Sofia How do I cross reference JIRA issues to "OPNFV documentation"? through a label or something else? Thanks Maryam From: opnfv-project-leads-boun...@lists.opnfv.org [mailto:opnfv-project-leads-boun...@lists.opnfv.org] On Behalf Of Sofia Wallin Sent: Monday, October 31, 2016 3:19 PM To: op

Re: [opnfv-tech-discuss] [multisite] Secgroup syncing Approach

Just one more comment for this action: "All the resources(based on resource-type) from region 1 will be copied to region 2 and 3 leaving the overlapped ones where resource name being the identifier. " I think we can add one option to allow the force replacement for the overlapping items. If th