Re: [onap-discuss] [so] SO API version

Hi Seshu, API we are trying is POST http://:8080/ecomp/mso/infra/serviceInstances/v6 with payload. We are getting 404 Not Found back. Same API works with v4. VID is also trying to invoke SO API with v6 and it is also getting error 404. Btw, when service is distributed from SDC, we are getting

[onap-discuss] [sdc] Error while onboarding vDNS CSAR in Azure SDC

Hi, We are trying to follow https://wiki.onap.org/display/DW/vDNS+on+Azure on Azure with ONAP Beijing release. Getting the below error in SDC while uploading simple_vdns.csar . Any pointer? [cid:image001.png@01D44905.32796E30] ==

[onap-discuss][Environment setup]

Hi, I have tried to install the ONAP on kubernetes with rancher on my host and followed below steps. 1. launched two VM's on my ubuntu host (one for Rancher master and one for Kubernetes node) 2. Followed, the below link to configure rancher and kubernetes. https://docs.onap.org/en/beijing/submo

[onap-discuss][SDC] : multiple VF linked to same VSP ?

Hello Is it possible to create several VF in SDC, linked to the same VSP ? René [Logo Orange] René Robert «Open and Smart solutions for autOmating Network Services» ORANGE/IMT/OLN/CNC/NARA/OSONS Fixe : +33 2 96 07 39 29

[onap-discuss][SDC][SDNC] : preload for Generic Neutron ?

Hello Using Beijing, I would like to instantiate a Generic Neutron network. What is the preload to use in SDNC for such network ? René [Logo Orange] René Robert «Open and Smart solutions for autOmating Network Services» ORANGE/IMT/OLN/CNC/NARA/OSONS Fixe : +33 2 96 07 3

Re: [onap-discuss] #vnfrqts PNP text

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 in last century. Do we have any plan to update that requirement by including "SHALL

Re: [onap-discuss] #vnfrqts PNP text > SHOULD vs SHALL

English is not my first language. But I believe Steven can help with this. In standardization English language, both “SHALL” and “MUST” means “REQUIRED”. For instance, 3GPP is using “SHALL” and IETF is using “MUST”. “SHOULD” means “RECOMMENDED”. “MAY” means “OPTIONAL”. For more details, please re

Re: [onap-discuss][Environment setup]

Prasad, Hi, docker, rancher master, helm and kubectl are installed on the master Docker and the rancher client container are installed on the minion/kubernetes/cluster-nodes – (no kubectl or helm required). A refused connection usually means tiller is not running – check that you are get

Re: [onap-discuss] [sdc] Error while onboarding vDNS CSAR in Azure SDC

Hi, The TOSCA which we have on the Confluence page is tested on Amsterdam release version of ONAP. In beijing release of ONAP, the TOSCA needs modifications as there is compatibility issues. We are working on the same to make this available to community. -=-=-=-=-=-=-=-=-=-=-=- Links: You rece

[onap-discuss] Controller Blueprints MS ( Architecture, Design & Code ) Live Discussion

BEGIN:VCALENDAR X-LOTUS-CHARSET:UTF-8 VERSION:2.0 PRODID:-//Lotus Development Corporation//NONSGML Notes 9.0.1//EN_S METHOD:REQUEST BEGIN:VTIMEZONE TZID:Eastern Standard Time BEGIN:STANDARD DTSTART:19501105T02 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 RRULE:FREQ=YEARLY;BYMINUTE=0;BYHOUR=2;BYDAY=1SU;B

Accepted: [onap-discuss] Controller Blueprints MS ( Architecture, Design & Code ) Live Discussion

BEGIN:VCALENDAR METHOD:REPLY PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:Eastern Standard Time BEGIN:STANDARD DTSTART:16010101T02 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 RRULE:FREQ=YEARLY;INTERVAL=1;BYDAY=1SU;BYMONTH=11 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T02

Re: [onap-discuss] Data Modeling IG call (Sep 10, 2018) is canceled #modeling

Wishing you and your family a very Happy New Year! Best Regards, Andy Andy Mayer, Ph.D. | PMTS, Network Cloud and Infrastructure | AT&T Labs | Phone: +1 (732) 420-9945 | am8...@att.com From: onap-discuss@lists.onap.org [mailto:onap-discuss@lists.onap.org] On Behalf Of Anatoly Katzman Sent: Sun

[onap-discuss] Controller Blueprints MS ( Architecture, Design & Code ) Live Discussion

Please send me the bridge info. Thanks Mehmet Title: Controller Blueprints MS ( Architecture, Design & Code ) Live Discussion Team, Please plan to attend this meeting, to know about Controller Blueprints MS (ccsdk/apps). Join Webex meeting Meeting number: 964 872 376 When: Mon Sep 10, 20

Re: [onap-discuss] Spike nodePortPrefix

Michael, Hi, an update: forgot to re-view the comments on the page after our update friday Mike updated the wiki on Friday after Mike, myself, James and Mandeep went through the list after the clamp, so fixes. You will see his update on the list https://lists.onap.org/g/onap-discuss/topi

Re: [onap-discuss] [doc] DOC Project PTL Election - Self-Nomination Phase Open

Hi Ritch, All, Sofia Wallin would like to self-nominate. She has PC problems hence she requested me to send this on her behalf. Best Regards, Steve -- Hi, I would like to nominate myself for the role as PTL for the ONAP documentation project. As PTL for the OPNFV docs project and drive

Re: [onap-discuss][Logging] Python Logging library

Shankar, Hi, good question. The Multivim/multicloud team (Liang Ke) developed and pushed the python version of the library with MDC. The python3 and MARKER(label) support was pushed this week. I would recommend using their library that they deploy to their 4 multicloud python containers

Re: [onap-discuss] Change in oom[master]: helm chart for so containers

Ramesh, Thanks for the update and the work guys– we now have 15 ports free in 302. AA&I can grab one of these https://lists.onap.org/g/onap-discuss/topic/spike_nodeportprefix/25502174?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,25502174 /michael From: PARTHASARATHY, RAMESH Sent: Mon

Re: [onap-discuss] #vnfrqts PNP text > SHOULD vs SHALL

Hello, Ben Thank you for your excellent explanation of the English words. Normative text is an ISO terminology and supported by each standardization origination, which you cannot find in any dictionary. For instance, IETF is using MUST/SHOULD/MAY as specified in RF

Re: [onap-discuss] #vnfrqts PNP text > SHOULD vs SHALL

Zu Qiang, Ben, The rest of the VNFRQTS are defined using the RC2119 keywords, and I'd rather not change that at this point. If you are adapting some text from elsewhere ( 3GPP?) then translating a SHALL"-> "MUST" would normally work based on the definition in RFC2119. regards Steven Wright -=-

Re: [onap-discuss] Change in oom[master]: helm chart for so containers

Hello Ramesh Why do you need a nodePort for so-mariadb ? I think that we want to optimize the nodePort for Casablanca and I am not sure that we need a nodePort for mariadb. Best Regards Eric -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#12344

Re: [onap-discuss] #vnfrqts PNP text > SHOULD vs SHALL

Hello, Ben With over 30 years standardization working experience, I do understand your confusions. First of all, “SHOULD” is defined in the RFC with the meaning “RECOMMENDED”, not past tense of “shall”. Second, using MUST or SHALL or both as “REQUIRED” is an ONAP community decis

Re: [onap-discuss] #vnfrqts PNP text > SHOULD vs SHALL

+1 Have a nice day Zu Qiang From: onap-discuss@lists.onap.org On Behalf Of WRIGHT, STEVEN A Sent: Monday, September 10, 2018 12:41 PM To: onap-discuss@lists.onap.org Subject: Re: [onap-discuss] #vnfrqts PNP text > SHOULD vs SHALL Zu Qiang, Ben, The rest of the VNFRQTS are defined using the RC

Re: [onap-discuss] OOM changes for PNDA waiting for docker images

Hi Donald, I'm not sure we can merge the charts into the OOM repo if we are unable to verify, to some degree, that they work. We verify and accept the merge of new charts or chart changes, based on the fact the all pods come up. I know this is a minimalistic approach but it is what we've been d

Re: [onap-discuss] [doc] DOC Project PTL Election - Self-Nomination Phase Open

I just want to chime in to provide some background and express my support here as this is out of the norm. Given the fact that there have been multiple unanswered calls for a Documentation PTL I believe that there is sufficient justification for a process exception to be granted by the ONAP

Re: [onap-discuss] [doc] DOC Project PTL Election - Self-Nomination Phase Open

+1 From: onap-discuss@lists.onap.org On Behalf Of Kenny Paul Sent: Monday, September 10, 2018 2:25 PM To: onap-discuss@lists.onap.org; stephen.terr...@ericsson.com; BENNETT, RICH Cc: Sofia Wallin Subject: Re: [onap-discuss] [doc] DOC Project PTL Election - Self-Nomination Phase Open I just

Re: [onap-discuss] #vnfrqts PNP text > SHOULD vs SHALL

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 tomorrow at 8am (New York time zone). “Zu Qiang, Ben, The rest of the VNFRQTS a

Re: [onap-discuss] [ONAP Helpdesk #60692] Jira strikethrough issue

Hi Jess, Yes, it is a very strange behavior. Not sure why Jira doesn't use the Status field to determine strikethrough instead of Resolution. Maybe we can remove the "unresolved" option from the Resolution field and allow Jira to default it to Unresolved on the Create screen. However, not sure ho

Re: [onap-discuss] ONAP Logging Project

David, Hi, it is good to meet you, we like working with the DCAE team. The Clamp, MultiVim, SO, Portal and Policy team are also involved. For EELF - yes most of the AT&T originated pods have EELF compliance (appc and aai directl use EELFLogger), there are several logging libraries in use

[onap-discuss] [modeling]Cancel the modeling subcommitee/Service IM/Data Model call this week

Hello all Due to New Year in Israel, modeling subcommittee would like to cancel below calls this week: 1) modeling subcommittee call , 9am eastern time Tuesday. 2) Service IM call, 12pm eastern time, Wednesday 3) Data modeling call, 10am eastern time, Monday Thanks a lot DENG

Re: [onap-discuss] [doc] DOC Project PTL Election - Self-Nomination Phase Open

Hi Kenny, Regarding the exception, it’s a corner case not considered in the charter – agree.I would propose the following: * Written support from the acting PTL (or any other committer) for allowing a PTL not derived from a committer to be included in the nominations * TSC approval

Re: [onap-tsc] [onap-discuss] [doc] DOC Project PTL Election - Self-Nomination Phase Open

Could we just do a quick vote amongst the DOC committers to promote Sofia to committer, then the election could proceed apace with no further exceptions needed from the TSC? She'll need to be a committer, anyways, to serve as PTL. While I'm not a DOC committer, I support Sofia's candidacy based