[onap-discuss] [vnfrqts] The requirement of open source database needs discussion and I suggest we remove it in R1. 

Hi Steven, I saw this item, but it has not been discussed. I suggest we remove it from R1 requirements and discuss it later. I opened a jira ticket. R-88199 The VNF MUST utilize virtualized, scalable open source database software that can meet the performance/latency requirements of the

[onap-discuss] 答复: [vnfrqts] vnf requirement keeps align with vnf guideline

Hi Neal, Steven I think this issue must be corrected immediately. Please refer to the VNF Guidelines document. What is the bug number? Regards, Wenyao 发件人: Zhuning [mailto:zhun...@huawei.com] 发送时间: 2017年11月16日 13:28 收件人: sw3...@att.com 抄送: liying...@chinamobile.com; 'Lingli Deng'

Re: [onap-discuss] newbee question

AS Please identify which company or institute you are part of so we track contributors and inquirers. AT ECOMP and LF ONAP are aligned. Mazin On Nov 15, 2017, at 3:22 PM, Andrey Selivanov via onap-discuss > wrote: Hi! How

Re: [onap-discuss] Modeling Project doc missing

Hi Eric Since you contributed this part document, do you want to help Aria by including them? Thanks DENG Hui From: onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of DeWayne Filppi Sent: Thursday, November 16, 2017 12:52 AM To:

[onap-discuss] 答复: RE: RE: Re: [onap-tsc] Official ONAP ArchitectureSlide

Hi Jamil From the VFC project coming into ONAP, VFC focus on ETSI NFV implimention, which is well-known in the community. In R1 arch, VFC marked with ETSI NFV is no problem, which can make the reader more clear about the main-contribution project. Because VFC as one

[onap-discuss] 答复: [onap-tsc] Official ONAP Architecture Slide

Hi, Agree that Jamil's suggestion in adding a general description for standard alignment to the text description. To avoid confusion mentioned by Susana, it is recommended to keep ‘ETSI-aligned' description in VF-C in the diagram. Best Regards, Yan 发件人:

[onap-discuss] compile:aai

Hi,team: I want to produce the dockers of aai/data-router. I download the code of aai/data-router project,then using the shell script: #!/bin/bash -x #build ajsc-aai echo "building docker for aai-data-router" source /etc/profile mvn package -Dmaven.test.skip=true docker:build -e [INFO]

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Sylvia, I believe Marco submitted a fix to the Heat template for this – I see that the current version is using the master branch. Dan -- Dan Timoney SDN-CP / OpenECOMP SDN-C SSO Please go to D2 ECOMP Release Planning

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Dan, the tag release-1.1.0 is the default value in current HEAT template (as said in https://jira.onap.org/browse/SDNC-196). That means that as soon as the release is released it should point to the stable branch of SDN-C. If it’s 1.1.0, fine (even if I would louve to have the branch merged

[onap-discuss] newbee question

Hi! How  ONAP official release (e.g. Amsterdam) corresponds to ECOMP software code base currently in production at AT (about 2 years I've heard)? Is it 2 completely different software projects from AT point of view? Do they collide in future? Sorry for stupidity). wbr, AS .

Re: [onap-discuss] Clarifying the TSC selected branching model for Amsterdam

Hi Michael, just a quick note to let you know I saw your tweet. The community is heads-down for tomorrow’s go/no-go decision right now. I’d hazard a guess that you are not the only person looking for clarification on these points, and expect that your email weill be the jumping off pointy for

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Yes, it worked fine after modifying /opt/config/gerrit_branch.txt to master release-1.1.0 is getting into /opt/config/gerrit_branch.txt from onap_openstack.env : aai_branch: master appc_branch: master so_branch: master mr_branch: master policy_branch: master portal_branch:

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Yes, this is what I suggested in a separate email. Marco From: "TIMONEY, DAN" Date: Wednesday, November 15, 2017 at 4:32 PM To: "BARSKY, GEORA" , "PLATANIA, MARCO (MARCO)" , Arun Arora ,

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Geora, The release-1.1.0 branch is pre-Amsterdam seed code. You want to be using the master branch, which should be working fine. The sdnc_install.sh script sets GERRIT_BRANCH (which is where it does the pull) to the contents of /opt/config/gerrit_branch.txt. I’m not sure how that’s set

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Geora, Please change /opt/config/gerrit_branch.txt from release-1.1.0 to master and retry. Thanks, Marco From: Geora Barsky Date: Wednesday, November 15, 2017 at 4:16 PM To: "PLATANIA, MARCO (MARCO)" , Arun Arora ,

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Hi Marco, In addition to below , I also noticed that there is an issue with /opt/sdnc/installation/src/main/yaml/docker-compose.yml . It points to openecomp/images instead of onap sdnc: image: openecomp/sdnc-image:latest During the installation it seems like this code is pulled from

Re: [onap-discuss] [HEAT Deployment] Many failures on components

Hi Michael and thanksgiving for the very interesting email. Where I fail is really related to ONAP deployment through Heat (bad default version for docker images, pull on git from a old branch for a docker compose...) and then that’s why you don’t see them on OOM. By the way, I love to see CD of

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Arun, Sylvain, Michael, I ran docker pull for SDNC WindRiver and it worked. I noticed the same issue with MSB though, because the docker version in Heat is wrong. It is v1.0.0, while it should be 1.0.0 (without v). I’m going to submit a change soon, please update your local Heat env. Arun,

Re: [onap-discuss] [HEAT Deployment] Many failures on components

Sylvain, Good question and thank you for syncing your deployment state with the rest of us. Some of the openecomp to onap namespace refactor is still going on – one went it 2 days ago to another component – it was fully OK. There is a small chance that runtime classloading – during

Re: [onap-discuss] [SDNC] sdnc_vm_init.sh fails

Following JIRA Ticket: https://jira.onap.org/browse/SDNC-102 was created for this issue and marked as Resolved and Closed. However, the issue still seems to be present. In comments it was mentioned to change the port from 10003 to 10001 in docker-compose.yml. But I didn't find any such port

Re: [onap-discuss] [HEAT Deployment] Many failures on components

Hi Christopher, I agree with you. 5 minutes should be sufficient (I was actually the guy who proposed to move from 180s to 300s, I guess it’s not sufficient for me ;-) ). It may be because all the VMs start at the same time and write to disks, which may put the servers under pressure (it’s a

[onap-discuss] Modeling Project doc missing

The ARIA REST API is contributed code to the ONAP project; ARIA includes a Python library and CLI. Runtime ARIA in ONAP lives in a container ( https://gerrit.onap.org/r/gitweb?p=so.git;a=blob;f=packages/docker/src/main/docker/docker-files/Dockerfile.aria). Also contributed to ONAP is a Java

Re: [onap-discuss] Updated Invitation: [appc] Weekly Meeting @ Weekly from 8am to 9am on Wednesday (PDT) (onap-discuss@lists.onap.org)

Team, Please be aware that APPC Project call is canceled for today. Notification has been sent to Gildas that APPC has completed all the necessary steps for the release. Congratulations to the team, excellent job by all! Randa -Original Appointment- From: ONAP Meetings and Events

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

Hi Maopeng I understand that it is not easy to map ETSI to ONAP architecture. But I don’t think by putting VFC aligned with ETSI NFV make any sense. As we are in one project my preference is to mention that ONAP is a way to implement ETSI NFV functionalities. Regards jamil De :

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

+1 De : Kanagaraj Manickam [mailto:kanagaraj.manic...@huawei.com] Envoyé : mercredi 15 novembre 2017 06:00 À : TALASILA, MANOOP (MANOOP); Kenny Paul; Lisa Caywood Cc : Sabater, Susana, Vodafone Spain; CHAWKI Jamil IMT/OLN; onap-discuss; onap-tsc Objet : RE: [onap-tsc] Official ONAP Architecture

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

+1 in addition Portal should not be part of the Design Time. OOM need to be positioned on the right to avoid to be considered as on the top of External API Regards Jamil De : TALASILA, MANOOP (MANOOP) [mailto:talas...@research.att.com] Envoyé : mercredi 15 novembre 2017 03:43 À : Kenny Paul;

Re: [onap-discuss] [vvp] - documentation

Thanks for your reply. As you suggested, I started working according to the 'devkit' summary: - I setup a linux development environment with vagrant and ansible. - from ../vvp/devkit I ran: . setenv vagrant up watch -n5 "kubectl get po -n kube-system" However, kubectl fails

[onap-discuss] Service distribution WorkFlow across various sdc/mso/aai/sdnc/v Containers via SDC Gui by Ops user

All , Michael While chasing the issue of Service distribution via SDC Gui and using VID to Deploy Service failing . There are certain dots that are missing while trying to establish due to which ONAP Container that issues is coming . For example in Distribution Flow Following are the

Re: [onap-discuss] [E] Centralized Image Management proposal discussion

Dear All, I have a question as to whether this proposal ( Centralized Image management ) conflicts with SDC Image management proposal, that was proposed earlier ? BR, Viswa Viswanath Kumar Skand Priya Architect Verizon Network Ops & Eng On Wed, Nov 15, 2017 at 2:10

Re: [onap-discuss] [onap-tsc] Official ONAP Architecture Slide

Thanks Maopeng! I was guessing that was the case when referencing IFA and not SOL specs. In any case, it will be good to update the links and make clear that VF-C does comply with NFV APIs and functionality, to avoid confusion as in this long thread. Cheers! /Susana From:

Re: [onap-discuss] [onap-tsc] 答复: Official ONAP Architecture Slide

+1 I don't believe 9 commercial vNFs from three different vendors could successfully deployed by VFC in voLTE service without compliance with ETSI specification. Yuan Yue 袁越 yuanyue 资深战略规划师 Senior Strategy Planner 技术规划部/技术规划部/系统产品 Technology Planning

[onap-discuss] [integration][uui]VoLTE use case UUI peroformance and alarm function test

BEGIN:VCALENDAR METHOD:REQUEST PRODID:Microsoft Exchange Server 2010 VERSION:2.0 BEGIN:VTIMEZONE TZID:China Standard Time BEGIN:STANDARD DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:STANDARD BEGIN:DAYLIGHT DTSTART:16010101T00 TZOFFSETFROM:+0800 TZOFFSETTO:+0800 END:DAYLIGHT

[onap-discuss] 答复: [onap-tsc] Official ONAP Architecture Slide

Hi I’d afraid that I can’t agree on it. The goal of VFC in ONAP is to provide ETSI NFV align capability, so make ONAP integrated with ETSI NFV complaint commercial solution in a more smooth way. I think the original version is most suitable way to describe the difference between VFC and

Re: [onap-discuss] 答复: RE: question about sdc_vm_init

It is a part but it is not needed for any of the use cases and currently has no integration with SDC. What Marco is pointing is that it is not needed in Amsterdam as a functional component. BR, Michael Lando Opensource TL , SDC AT Network Application Development · NetCom Tel Aviv | Tampa |

Re: [onap-discuss] [vvp] - documentation

Hello Moshe, VVP is built from multiple containers which rely on each other except from validation scripts. You need to set up the all system in order to use it as platform not just a single docker. VVP is based on kubernetes and use rockets. For example, the rocket you sent a picture of is just