B2 3D30
ag1...@att.com<mailto:ag1...@att.com>
From: Michela Bevilacqua
mailto:michela.bevilac...@ericsson.com>>
Sent: Tuesday, June 19, 2018 12:16 AM
To: GUPTA, ALOK mailto:ag1...@att.com>>;
kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; JI, LUSHENG
mail
HI Alok,
I´ve noticed fault sheet is not updated according to the agreement reached
last week during the DCAE meeting.
(i.e. MO and MO instance, 3GPP alarm id).
Are you going to send for review a final update version with VES 6.0 specs ?
BR
Michela
From: onap-discuss-boun...@lists.onap.org
On
HI,
Where can I find the Minutes of the meeting and possible the recording about R3
content discussions ?
Thanks
Michela
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss
Hi,
I share some questions about Resource TOSCA data model as follow up of the
today´s ONAP modeling subcommittee meeting
1. Assuming the discussion we had today during the ONAP modeling
subcommittee about OASIS TOSCA NFV or SOL001 is limited to the VNF onboarding
model. What is the TOSCA
21 februari 2018 08:50
To: Michela Bevilacqua ; denghui (L)
; onap-discuss@lists.onap.org
Subject: RE: [onap-tsc] [modeling] Beijing Release new functional requirements
Hi Michela,
Regarding HPA in particular This is a functional requirement at cuts across
multiple use cases in support
Hi,
In the context of Beijing release, it could be good to have some more inputs
about possible ONAP IM and ONAP TOSCA DM impacts/expectations in relation to
the new functional requirements:
1. HPA: discussions progressed, analysis is ongoing
2. Change Management: no input
3. Scaling: n
+1, favorable to a Git for ONAP IM in Papyrus.
ONAP modeling subcommittee can be responsible for this with committers based on
commit operation in papyrus.
Use GenDoc to document the model.
Approach it in Beijing release, learn from the experience and be more
effective in Casablanca release.
