Re: [onap-discuss][SDC] : new connectivity model
Rene: Please take a look at the contribution from Nokia on pnfRegistration in the VES specs (Beijing) where PNF on a boot-up, send a VES pnfRegistration (provides IP address, correlation ID etc.) event to DCAE and a Micro-service in DCAE will pick the event and updates A You can review details information at: https://wiki.onap.org/display/DW/Meetings?preview=%2F13598723%2F34375934%2Fpnfregistration+questions_Nokia+respv2+%28Read-Only%29.pdf Regards, Alok Gupta 732-420-7007 MT B2 3D30 ag1...@att.com<mailto:ag1...@att.com> From: onap-discuss@lists.onap.org On Behalf Of Rene Robert Sent: Tuesday, September 18, 2018 12:31 PM To: onap-discuss@lists.onap.org Cc: LANDO, MICHAEL Subject: [onap-discuss][SDC] : new connectivity model Hello I would like to add a new kind of connectivity resource/service in ONAP : That connectivity will be realized by configuring a PNF (could be as well a VNF) : when instantiating that service, a set of request will have to be sent to a PNF (using a Rest API) to transfer a set of information (Route Target, VLANid..) How to describe in SDC that kind of service ? [Logo Orange]<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.orange.com_=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=iMEfHC7-BOQWThCp4DitXXietk8ZsD51gO12T53sTlo=fNZP4SKbAymkIgQQe8s96nTIZSHkBjvqeYyhrMbTBSY=> René Robert «Open and Smart solutions for autOmating Network Services» ORANGE/IMT/OLN/CNC/NARA/OSONS Fixe : +33 2 96 07 39 29 <https://urldefense.proofpoint.com/v2/url?u=https-3A__monsi.sso.francetelecom.fr_index.asp-3Ftarget-3Dhttp-253A-252F-252Fclicvoice.sso.francetelecom.fr-252FClicvoiceV2-252FToolBar.do-253Faction-253Ddefault-2526rootservice-253DSIGNATURE-2526to-253D-2B33-25202-252096-252007-252039-252029=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=iMEfHC7-BOQWThCp4DitXXietk8ZsD51gO12T53sTlo=14SLsVVQL51MyW1DkyCaVWxEQMOePN2OXCsmIsmmzsY=> Mobile : +33 6 74 78 68 43 <https://urldefense.proofpoint.com/v2/url?u=https-3A__monsi.sso.francetelecom.fr_index.asp-3Ftarget-3Dhttp-253A-252F-252Fclicvoice.sso.francetelecom.fr-252FClicvoiceV2-252FToolBar.do-253Faction-253Ddefault-2526rootservice-253DSIGNATURE-2526to-253D-2B33-25206-252074-252078-252068-252043=DwMFAw=LFYZ-o9_HUMeMTSQicvjIg=iccs1VIxoa5SRlt4QotAwA=iMEfHC7-BOQWThCp4DitXXietk8ZsD51gO12T53sTlo=YxZLbYYJgI7Y614s56OQFML4tQ9JnU8wg5KYHCaoLqM=> rene.rob...@orange.com<mailto:rene.rob...@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. -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12486): https://lists.onap.org/g/onap-discuss/message/12486 Mute This Topic: https://lists.onap.org/mt/25747513/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] Custom Events in DCAE
Sirisha: We do support SNMP collector, which digest SNMP traps but then are mapped by a Microservice to VES events. Mapper mService was being contributed by TechM. I have copied Lusheng Ji (previous DCAE PTL) and Vijay Venkateshkumar (current DCAE PTL, on vacation till end of Aguuset), who can provide you more details on the SNMP Collector and Mapper mService. Regards, Alok Gupta 732-420-7007 MT B2 3D30 ag1...@att.com<mailto:ag1...@att.com> From: sirisha.gopig...@verizon.com Sent: Thursday, August 16, 2018 5:46 AM To: onap-discuss@lists.onap.org; GUPTA, ALOK Cc: bharath.thiruveed...@verizon.com Subject: Re: [onap-discuss] Custom Events in DCAE Hi Alok, Thank you for the mail, the documentation was helpful. Will check and get back to you. I could see ONAP Beijing supports SNMP Collector, Can you please give me some pointers regarding this. Thank you Best Regards Sirisha Gopigiri From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> mailto:onap-discuss@lists.onap.org>> on behalf of Alok Gupta mailto:ag1...@att.com>> Sent: Tuesday, August 14, 2018 8:34 PM To: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org>; Gopigiri, Sirisha Cc: Thiruveedula, Bharath Subject: [E] Re: [onap-discuss] Custom Events in DCAE Sirisha: The only way VES collector can support custom events is via use of 'Other Domain'. It still requires to have a header in vEs format and the payload can be name/value pair embedded in the "other' Domain. I have attached VES summary presentation and the detailed requirement currently supported VES 5.4.1 is included on the last page as an embedded file. Please let me know if this meets your need. Regards, Alok Gupta 732-420-7007 MT B2 3D30 ag1...@att.com<mailto:ag1...@att.com> From: onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> mailto:onap-discuss@lists.onap.org>> On Behalf Of sirisha.gopigiri via Lists.Onap.Org Sent: Tuesday, August 14, 2018 5:47 AM To: onap-discuss mailto:onap-discuss@lists.onap.org>> Cc: bharath.thiruveed...@verizon.com<mailto:bharath.thiruveed...@verizon.com> Subject: [onap-discuss] Custom Events in DCAE Hi, I am working on configuring DCAE with custom events. I have some queries regarding DCAE components configuration and implementation, 1. Can we configure custom events with VES collector, If so could you please give me a reference on how to do so. 2. How can I configure other collectors, like SNMP or Restconf? Please give me some pointers, referring to the above. Thanks in advance! Regards Sirisha -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11900): https://lists.onap.org/g/onap-discuss/message/11900 Mute This Topic: https://lists.onap.org/mt/24525346/21656 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] #aai
Recently Nokia has contributed pnfRegistration domain in VES 7.0.1 that is created to update pnf inventory in the A We can explore to see if this event can be used to update A However, A needs to have a record for the device either through orchestration or some other onboarding/provisioning process. Regards, Alok Gupta 732-420-7007 MT B2 3D30 ag1...@att.com<mailto:ag1...@att.com> From: onap-discuss@lists.onap.org On Behalf Of Rahul Wadodkar Sent: Thursday, August 2, 2018 2:08 AM To: onap-discuss@lists.onap.org Subject: [onap-discuss] #aai Hi, we are looking to integrate EMS with DCAE for Fault and performance, however we are also getting Inventory and configuration from EMS. is there any standard collector that we can use to read the configuration data and put it in A? -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#11611): https://lists.onap.org/g/onap-discuss/message/11611 Mute This Topic: https://lists.onap.org/mt/24140934/21656 Mute #aai: https://lists.onap.org/mk?hashtag=aai=2740164 Group Owner: onap-discuss+ow...@lists.onap.org Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
Re: [onap-discuss] VES RanMetrics Recommendation
That would work or we can review it in the n next DCAE team meeting. Regards, Alok Gupta 732-420-7007 MT B2 3D30 ag1...@att.com<mailto:ag1...@att.com> From: Michela Bevilacqua Sent: Thursday, June 21, 2018 10:29 AM To: GUPTA, ALOK ; kp...@linuxfoundation.org; JI, LUSHENG ; onap-discuss@lists.onap.org Cc: Agron, Minerva (Nokia - US/Murray Hill) ; HYNES, GERARD W Subject: RE: VES RanMetrics Recommendation Hi Alok, I propose to review our proposal shared last week and in agenda for the last DCAE meeting but unluckily time run out. I can call for a dedicated meeting. BR Michela Original Message Subject: RE: VES RanMetrics Recommendation From: "GUPTA, ALOK" mailto:ag1...@att.com>> Date: 21 Jun 2018, 21:25 To: Michela Bevilacqua mailto:michela.bevilac...@ericsson.com>>,kp...@linuxfoundation.org,"JI, LUSHENG" mailto:l...@research.att.com>>,onap-discuss@lists.onap.org Michela: Please ignore Ran Metric Domain. It will be added to spec later. This domain would be the one which could be generated from data transferred via bulk data transfer or Ran devices can directly send events.. The defined metrics need Vendor specific payload and not xml file details. This domain definition needs more work. We will work with you as a team to finalize this domain. I P\plan to publish VES 6.0 without Ran Metric Domain. Regards, Alok Gupta 732-420-7007 MT B2 3D30 ag1...@att.com<mailto:ag1...@att.com> From: Michela Bevilacqua mailto:michela.bevilac...@ericsson.com>> Sent: Wednesday, June 20, 2018 11:32 AM To: GUPTA, ALOK mailto:ag1...@att.com>>; kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; JI, LUSHENG mailto:l...@research.att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Cc: Agron, Minerva (Nokia - US/Murray Hill) mailto:minerva.ag...@nokia.com>>; HYNES, GERARD W mailto:gh7...@att.com>> Subject: RE: VES RanMetrics Recommendation HI Alok, We need some more time to review the ranMetric Domain proposal shared Friday considering this week we are attending to the Casablanca F2F dev in Beijing Can you postpone the deadline to beginning of the next week ? BR Michela From: GUPTA, ALOK mailto:ag1...@att.com>> Sent: den 19 juni 2018 14:25 To: Michela Bevilacqua mailto:michela.bevilac...@ericsson.com>>; kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; JI, LUSHENG mailto:l...@research.att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Cc: Agron, Minerva (Nokia - US/Murray Hill) mailto:minerva.ag...@nokia.com>>; HYNES, GERARD W mailto:gh7...@att.com>> Subject: RE: VES RanMetrics Recommendation Michela: We are still in the process of updating the spec. here is the fault domain with comments on MO. 1.1.1'Fault' Domain Datatypes 1.1.1.1Datatype: faultFields The faultFields datatype consists of the following fields: Field Type Required? Description alarmAdditional Information hashMap No Additional alarm information (note: for SNMP mapping to VES, for hash key use OID of varbind, for value use incoming data for that varbind). alarmCondition string Yes Single word denoting the alarm condition/problem, such as a trap name. Should not have white space (e.g., tpLgCgiNotInConfig, BfdSessionDown, linkDown, etc...) alarmInterfaceA string No Card, port, channel or interface name of the device generating the alarm. This could reflect Managed object. This could be Managed Object. eventCategory string No Event category, for example: 'license', 'link', 'routing', 'security', 'signaling' eventSeverity string Yes Event severity enumeration: 'CRITICAL', 'MAJOR', 'MINOR', 'WARNING', 'NORMAL'. NORMAL is used to represent clear. eventSourceType string Yes Examples: 'card', 'host', 'other', 'port', 'portThreshold', 'router', 'slotThreshold', 'switch', 'virtualMachine', 'virtualNetworkFunction'. This could be Managed Object Class. faultFieldsVersion number Yes Version of the faultFields block specificProblem string Yes Description of the alarm or problem (e.g., 'eNodeB 155197 in PLMN 310-410 with eNodeB name KYL05197 is lost'). 3GPP probable cause would be included in this field. vfStatus string Yes Virtual function status enumeration: 'Active', 'Idle', 'Preparing to terminate', 'Ready to terminate', 'Requesting Termination' Note: Alarm ID for 3GPP should be included (if applicable) in alarmAdditonalInformation as alarmId:value. This information has been included in the excel sheet as well. Regards, Alok Gupta 732-420-7007 MT 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 mailto:l...@research.at
Re: [onap-discuss] VES RanMetrics Recommendation
Michela: Please ignore Ran Metric Domain. It will be added to spec later. This domain would be the one which could be generated from data transferred via bulk data transfer or Ran devices can directly send events.. The defined metrics need Vendor specific payload and not xml file details. This domain definition needs more work. We will work with you as a team to finalize this domain. I P\plan to publish VES 6.0 without Ran Metric Domain. Regards, Alok Gupta 732-420-7007 MT B2 3D30 ag1...@att.com<mailto:ag1...@att.com> From: Michela Bevilacqua Sent: Wednesday, June 20, 2018 11:32 AM To: GUPTA, ALOK ; kp...@linuxfoundation.org; JI, LUSHENG ; onap-discuss@lists.onap.org Cc: Agron, Minerva (Nokia - US/Murray Hill) ; HYNES, GERARD W Subject: RE: VES RanMetrics Recommendation HI Alok, We need some more time to review the ranMetric Domain proposal shared Friday considering this week we are attending to the Casablanca F2F dev in Beijing Can you postpone the deadline to beginning of the next week ? BR Michela From: GUPTA, ALOK mailto:ag1...@att.com>> Sent: den 19 juni 2018 14:25 To: Michela Bevilacqua mailto:michela.bevilac...@ericsson.com>>; kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; JI, LUSHENG mailto:l...@research.att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Cc: Agron, Minerva (Nokia - US/Murray Hill) mailto:minerva.ag...@nokia.com>>; HYNES, GERARD W mailto:gh7...@att.com>> Subject: RE: VES RanMetrics Recommendation Michela: We are still in the process of updating the spec. here is the fault domain with comments on MO. 1.1.1‘Fault’ Domain Datatypes 1.1.1.1Datatype: faultFields The faultFields datatype consists of the following fields: Field Type Required? Description alarmAdditional Information hashMap No Additional alarm information (note: for SNMP mapping to VES, for hash key use OID of varbind, for value use incoming data for that varbind). alarmCondition string Yes Single word denoting the alarm condition/problem, such as a trap name. Should not have white space (e.g., tpLgCgiNotInConfig, BfdSessionDown, linkDown, etc…) alarmInterfaceA string No Card, port, channel or interface name of the device generating the alarm. This could reflect Managed object. This could be Managed Object. eventCategory string No Event category, for example: ‘license’, ‘link’, ‘routing’, ‘security’, ‘signaling’ eventSeverity string Yes Event severity enumeration: ‘CRITICAL’, ‘MAJOR’, ‘MINOR’, ‘WARNING’, ‘NORMAL’. NORMAL is used to represent clear. eventSourceType string Yes Examples: ‘card’, ‘host’, ‘other’, ‘port’, ‘portThreshold’, ‘router’, ‘slotThreshold’, ‘switch’, ‘virtualMachine’, ‘virtualNetworkFunction’. This could be Managed Object Class. faultFieldsVersion number Yes Version of the faultFields block specificProblem string Yes Description of the alarm or problem (e.g., ‘eNodeB 155197 in PLMN 310-410 with eNodeB name KYL05197 is lost’). 3GPP probable cause would be included in this field. vfStatus string Yes Virtual function status enumeration: ‘Active’, ‘Idle’, ‘Preparing to terminate’, ‘Ready to terminate’, ‘Requesting Termination’ Note: Alarm ID for 3GPP should be included (if applicable) in alarmAdditonalInformation as alarmId:value. This information has been included in the excel sheet as well. Regards, Alok Gupta 732-420-7007 MT 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 mailto:l...@research.att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Cc: Agron, Minerva (Nokia - US/Murray Hill) mailto:minerva.ag...@nokia.com>>; HYNES, GERARD W mailto:gh7...@att.com>> Subject: RE: VES RanMetrics Recommendation 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<mailto:onap-discuss-boun...@lists.onap.org> mailto:onap-discuss-boun...@lists.onap.org>> On Behalf Of GUPTA, ALOK Sent: den 15 juni 2018 16:08 To: kp...@linuxfoundation.org<mailto:kp...@linuxfoundation.org>; JI, LUSHENG mailto:l...@research.att.com>>; onap-discuss@lists.onap.org<mailto:onap-discuss@lists.onap.org> Cc: Agron, Minerva (Nokia - US/Murray Hill) mailto:minerva.ag...@nokia.com>>; HYNES, GERARD W mailto:gh7...@att.com>> Subject: [onap-discuss] VES RanMetrics Recommendation Team: Please find enclosed an updated ranMetrics Domain for your review and comments. This will be included in VES 6.0
