Team: Event Registration or the YAML document provides machine readable document to DCAE providing them the exact content of events (both VES defined and vendor defined) along with their recommendatio

#vnfrqts #vnfsdk #controlloop

See separate email to the list from Kenny Paul. The Zoom bridges have apparently been disabled. Given the short notice, it is impractical to distribute an alternate bridge and so I ‘m cancelling the V

#vnfrqts

#vnfrqts Team (UTC) When: Wednesday, 20 March 2019 2:00pm to 3:00pm (GMT+00:00) UTC Repeats: Weekly on Wednesday Where: https://zoom.us/j/991786959 Organizer: sw3588@att.com Bridge:ONAP9 Description:

#vnfrqts #cal-invite

Cancelled: #vnfrqts Team This event has been cancelled. When: Wednesday, 23 January 2019 7:00am to 8:00am (GMT-07:00) America/Los Angeles Repeats: Weekly on Wednesday Where: https://zoom.us/j/99178695

#vnfrqts #cal-cancelled

Per the meeting time discussions last year, the VNFRQTS project team meeting is moving to WEDNESDAYs at 10AM EST – please check the community calendar for the zoom call coordinates best regards Steven

#vnfrqts

#vnfrqts Team When: Wednesday, 23 January 2019 7:00am to 8:00am (GMT-08:00) America/Los Angeles Repeats: Weekly on Wednesday Where: https://zoom.us/j/991786959 Organizer: sw3588@att.com ONAP9 Descript

#vnfrqts #cal-invite

The #VNFRQTS and #VVP calls cancelled this week due to the F-F Developer event in Paris this week. best regards Steven Wright, MBA, PhD, JD. AT&T Services Inc. 1057 Lenox Park Blvd NE, STE 4D28 Atlant

#vvp #vnfrqts

#vnfrqts Team When: Tuesday, 13 November 2018 5:00am to 6:00am (GMT-08:00) America/Los Angeles Repeats: Weekly on Tuesday Where: ONAP3 https://zoom.us/j/991786959 Organizer: sw3588@att.com Steven Wrig

#vnfrqts #cal-invite

Hi Eric, Glad to see that the VVP validation scripts are actively being leveraged. There are many HEAT requirements enumerated in the VNFRQTs project and the requirement you highlighted (R-20856) has

#doc #vnfrqts #vvp

Thanks Victor, Andrei, Andy, Could you respond? (preferably on the wiki?) Can we separate any controversial material so that we can proceed with the remaining stable items best regards Steven Wright,

#vnfrqts

Hello, Ben The following is the response from Steven Wright, which I totally agree with him. But if you would like to change the ONAP community decision, may be you should call in the VNGRQTS meeting

#vnfrqts

Hello, Steven According to the vnf requirement section 3, “Requirements are identified as either MUST, MUST NOT, SHOULD, SHOULD NOT, or MAY as defined in RFC 2119.” Unfortunately, RFC2119 is specified

#vnfrqts

Resending as I saw a lot fewer responses than we have folks claiming to be contributors. Based on the current responses it is difficult to justify any changes in the meeting time. I’ll leave the poll

#vnfrqts

Lets try this again – last time I messed up the settings and people could only respond with a single option. Please respond by the next vnfrqts meeting next Tuesday and we can discuss the poll results

#vnfrqts

Current meeting time for the regular weekly project call is 8AM EST. I understand this timezone is not ideal for everyone so I created a doodle poll to see if there is an alternate time that would wor

#vnfrqts

Hi Qiang, Sounds like a good place to me. Why not pick a place and put the proposed new text in context into the Jira ticket and see if anyone has any concerns? best regards Steven Wright, MBA, PhD, J

#vnfrqts

Hi Alex, I just wanted to follow up on the HPA impact into the VNF Requirements for Casablanca. We have JIRA ticket open as a placeholder for this. https://jira.onap.org/browse/VNFRQTS-159 I’d like to

#vnfrqts

Hello ONAP Community, The VNFRQTS project would like to delete seed documents out of the vnfrqts/documentation repository. We don’t need these documents moving forward and they result in some RST erro

#vnfrqts