date:20180111

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

2018-01-11 Thread jamil.chawki

Hello Randa
+1 for your proposal
Regards
Jamil

Le 12 janv. 2018 à 00:58, MAHER, RANDA > 
a écrit :

Dear TSC,

Please consider request below for Committer Promotion for APPC project.

https://wiki.onap.org/pages/viewpage.action?pageId=22251669

One of our existing committers has indicated that he will  step down from 
Committer to Contributor role.
Existing Committers have all voted +1 on Taka Cho promotion to Committer.

Thanks, Randa
APPC PTL
___
ONAP-TSC mailing list
onap-...@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-tsc

_

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.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [E] RE: [sdc] Error in SDC on dependency validation in ONAP R1

2018-01-11 Thread Avi Gaffa

Thanks Viswa.
We're on it

-- Sent from my Android Device



From: Kumar Skand Priya, Viswanath V
Sent: Thursday, January 11, 2018 3:37:25 PM
To: Avi Gaffa
Cc: Thiruveedula, Bharath
Subject: Re: [E] RE: [onap-discuss] [sdc] Error in SDC on dependency validation 
in ONAP R1

Hi Avi,

PFA requested info. Bharath ( CCed ) would provide any other additional info if 
you might need them.

BR,
Viswa


[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]

Viswanath Kumar Skand Priya
Architect
Verizon Network Ops & Eng


On Wed, Jan 10, 2018 at 6:20 PM, Avi Gaffa 
> wrote:
We also need the csar that was created after onboarding


From: Kumar Skand Priya, Viswanath V 
[mailto:viswanath.kumarskandpr...@verizon.com]
Sent: Wednesday, January 10, 2018 1:55 PM
To: Avi Gaffa >
Subject: Re: [E] RE: [onap-discuss] [sdc] Error in SDC on dependency validation 
in ONAP R1

Hi Avi,

Thanks for chiming in. PFA .

BR,
Viswa


[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]

Viswanath Kumar Skand Priya
Architect
Verizon Network Ops & Eng


On Wed, Jan 10, 2018 at 5:22 PM, Avi Gaffa 
> wrote:
Hi,
Can you provide the images as attachment with a better resolution?
It is very hard to see the errors.

Thanks,
Avi

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org]
 On Behalf Of Kumar Skand Priya, Viswanath V via onap-discuss
Sent: Wednesday, January 10, 2018 12:01 PM
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] [sdc] Error in SDC on dependency validation in ONAP R1

Dear SDC Team,

We found an error while using dependency attribute in SDC of ONAP R1

While creating a VSP, we added a dependency between 2 components as below:

[cid:image001.jpg@01D38A22.4FDC86D0]
Things look good until VSP level. Now when we tried to promote a VSP to VF 
using "Import VSP" option in SDC, we are hit with following error:

[cid:image002.jpg@01D38A22.4FDC86D0]
If we remove the dependency in VSP and re-promote to VF, then it pass through 
successfully.
Is this is a gap in SDC or are we doing a mistake in configuration? Kindly 
clarify...

BR,
Viswa


[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]

Viswanath Kumar Skand Priya
Architect
Verizon Network Ops & Eng

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,
you may review at 
https://www.amdocs.com/about/email-disclaimer

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [E] [oom] OOM Installation Problem | Unable to bring up Portal Pod

2018-01-11 Thread Karthik

Hi Michael and Team, Good day !

@Michael - Thanks for your inputs.

Yes, no problem with the Installation right now. Onap is up and running.I
highly appreciate for pro actively helping others to solve the problems. Thanks
a lot for your help.

Best Regards,
Karthik.

On 12 Jan 2018 00:22, "Michael O'Brien"  wrote:

> Viswa, Karthik,
>
>Hi, we are here to help you through this – I may have replied to an
> earlier mail.
>
>Just verifying you are OK now – it looks like you have increased your
> ram after talking to Mandeep and myself  – yes portal is at the top of the
> hierarchy and will not start unless all the pods in its yaml dependency
> section are up first –
>
>
>
> https://lists.onap.org/pipermail/onap-discuss/2018-January/007328.html
>
> https://lists.onap.org/pipermail/onap-discuss/2018-January/007299.html
>
>
>
> thank you
>
> /michael
>
>
>
> *Karthik* sdkarthikk at gmail.com
> 
> *Thu Jan 11 12:13:17 UTC 2018*
>
>- Previous message: [onap-discuss] OOM Installation Problem | Unable
>to bring up Portal Pod
>
>- Next message: [onap-discuss] How to test the vFW configuration and
>deployment
>
>- *Messages sorted by:* [ date ]
>
> [ thread ]
>
> 
> [ subject ]
>
> 
> [ author ]
>
> 
>
> --
>
> Hi Mandeep, Alexis, Michael, Viswa ,
>
>
>
> Thanks a lot for your quick responses and suggestions.
>
>
>
> As Michael suggested that RAM should be more than 55 G, so I increased it
>
> to 128G.
>
> After increasing RAM size , I am able to install ONAP using OOM. Thanks!
>
>
>
> Regards,
>
> Karthik.
>
>
>
> On 11 Jan 2018 03:42, "Mandeep Khinda"  > wrote:
>
>
>
> >* Hi Karthik,*
>
> >
>
> >* Can you share some more output from your k8s cluster (in a text format
> if*
>
> >* possible)*
>
> >
>
> >
>
> >
>
> >* kubectl -n onap-portal get events|grep portalapps*
>
> >
>
> >
>
> >
>
> >* This will show the events that took place and hopefully the reason why
> it*
>
> >* is stuck at initializing.  In my experience it is usually image
> pulling*
>
> >* issues and/or k8s cluster resource limits are maxed out.*
>
> >
>
> >
>
> >
>
> >
>
> >
>
> >* *Mandeep Khinda**
>
> >
>
> >* Software Development*
>
> >
>
> >* *Open Network Division**
>
>
>
>
>
> *From:* onap-discuss-boun...@lists.onap.org [mailto:onap-discuss-bounces@
> lists.onap.org ] *On Behalf Of *
> Karthik
> *Sent:* Tuesday, January 9, 2018 10:19
> *To:* onap-discuss@lists.onap.org
> *Subject:* [onap-discuss] OOM Installation Problem | Unable to bring up
> Portal Pod
>
>
>
>
>
> *From:* Michael O'Brien
> *Sent:* Wednesday, January 10, 2018 07:15
> *To:* 'Karthik' ; onap-discuss@lists.onap.org
> *Subject:* RE: [onap-discuss] OOM Installation Problem | Unable to bring
> up Portal Pod
>
>
>
> Karthik,
>
>Hi, it’s Mike, welcome to ONAP.  Failure of vnc-portal initialization
> by itself usually means you are running a currently unsupported version of
> helm on the server side of Kubernetes.
>
>Do a “helm version” – you should see 2.3.x on both the client and
> server – if you see 2.6 then you installed :latest for rancher and not
> v1.6.10
>
>Verify you are running the following detailed on the wiki.
>
>Rancher 1.6.10
>
>Kubernetes 1.8.x – to 1.8.6
>
>Helm 2.3.x
>
>Likely you are running docker 1.12.x
>
>
>
>Also to bring up all of ONAP you will need at least 55G.
>
>
>
>
>
>See
>
> https://jira.onap.org/browse/OOM-441
>
> https://jira.onap.org/browse/OOM-486
>
>
>
>Thank you
>
>/michael
>
>
>
>
>
>
>
> *From:* Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
> *Sent:* Tuesday, January 9, 2018 14:40
> *To:* Kumar Skand Priya, Viswanath V  verizon.com>
> *Cc:* Michael O'Brien ; David Sauvageau <
> david.sauvag...@bell.ca>; onap-discuss@lists.onap.org; Karthik <
> sdkarth...@gmail.com>
> *Subject:* Re: [onap-discuss] [E] [oom] OOM Installation Problem | Unable
> to bring up Portal Pod
>
>
>
> Hi,
>
>
>
> Can you send the logs?
>
>
>
> Thanks,
>
> Alexis
>
>
>
> On Jan 9, 2018, at 2:37 PM, Kumar Skand Priya, Viswanath V via
> onap-discuss

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

2018-01-11 Thread MAHER, RANDA

Thank you, Mazin.

I have updated the Committer Promotion form on wiki with details and also 
including information here:
APPC has always had a very small number of committers: 4 before recent step 
down of one committer (3 from AT, 1 from Intel)

The Committer that stepped down was from AT the committer promotion 
candidate (Takamune Cho)  is from AT

Current list of Committers:
• Randa Maher (AT - PTL)
• Patrick Brady (AT)
• Marcus Williams (Intel)

Thanks,
Randa

From: GILBERT, MAZIN E
Sent: Thursday, January 11, 2018 10:16 PM
To: MAHER, RANDA 
Cc: onap-...@lists.onap.org; onap-discuss@lists.onap.org
Subject: Re: [onap-tsc] Committer Promotion Request for [appc]

+1

Please add the candidate’s company plus existing committers.



On Jan 11, 2018, at 6:57 PM, MAHER, RANDA 
> wrote:

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Dear TSC,

Please consider request below for Committer Promotion for APPC project.

https://wiki.onap.org/pages/viewpage.action?pageId=22251669

One of our existing committers has indicated that he will  step down from 
Committer to Contributor role.
Existing Committers have all voted +1 on Taka Cho promotion to Committer.

Thanks, Randa
APPC PTL
___
ONAP-TSC mailing list
onap-...@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y=NXGqSa5NxTHo7zyxUrPP49eLYsmXzI4yh64s3B4oM5A=Evsqbp4rRCVLOh5p5fjHYs14lo95L06AtvAB_oZldfM=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] VNF SDK 01-12-2018 Meeting - Developer Wiki - Confluence

2018-01-11 Thread Tina Tsou

Dear all,

Here is agenda for this Friday 6am VNFSDK meeting. Talk to you soon.

https://wiki.onap.org/display/DW/VNF+SDK+01-12-2018+Meeting


Thank you,
Tina
IMPORTANT NOTICE: The contents of this email and any attachments are 
confidential and may also be privileged. If you are not the intended recipient, 
please notify the sender immediately and do not disclose the contents to any 
other person, use it for any purpose, or store or copy the information in any 
medium. Thank you.
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

2018-01-11 Thread Gary Wu

Ok, as long as we know what the issue was, I’ll think of a workaround.  I’ll 
probably end up customizing the wind river heat template to exclude 
dcae-bootstrap VM from using the local docker cache, as you described.

Thanks for your help!

-Gary


From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Thursday, January 11, 2018 5:46 PM
To: Gary Wu ; onap-discuss 
Subject: Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Gary,

Unfortunately, that is not an easy fix.

Is it possible to add https to this registry?

If not, This is what I did to fix SB-05: getting into dcae-bootstrap vm and run 
this:
sudo sed -ie 's/10.12.5.80:5000/nexus3.onap.org:10001/g' 
/opt/app/config/invinputs.yaml /opt/config/nexus_docker_repo.txt
then rerun /opt/dcae2_vm_init.sh.

Lusheng


From: Gary Wu >
Date: Thursday, January 11, 2018 at 4:22 PM
To: "JI, LUSHENG (LUSHENG)" 
>, onap-discuss 
>
Subject: RE: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Hi Lusheng,

10.12.5.80 is a docker cache local within the Wind River lab that allows us to 
dramatically speed up ONAP spin-up.   Unfortunately it only supports http.  The 
workaround for this is to configure the VM to allow insecure registries 
(https://docs.docker.com/registry/insecure/#deploy-a-plain-http-registry)
 by adding a /etc/docker/daemon.json file with the following content:

{
  "insecure-registries" : ["10.12.5.80:5000"]
}

Is this something that can be added/configured in the DCAE VMs relatively 
easily?  For all the other VMs I was able to add such a file by modifying the 
heat template, but it’s not clear how we can do so for the DCAE VMs.

Thanks,
Gary

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Thursday, January 11, 2018 1:01 PM
To: Gary Wu >; onap-discuss 
>
Subject: Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Gary,

The log of dcae bootstrap docker container shows that there was a transient 
problem last night.  One of the artifacts hosted by LF Nexus server failed to 
download (getting “502 bad gateway” response).   I dumped the docker log to 
file /opt/log-docker-15afe9c18611-20180110 on the dcae bootstrap VM and line 
and line 1515 shows the problem.

So after cleaning up I re-ran the vm_init bash script again.  The deployment 
has passed the failure point last night.

Now there is another problem.   One of DCAE subcomponent failed due to now able 
to contact docker registry.  I found that the configuration for nexus docker 
repo is set to “10.12.5.80:5000”.  The error message says expects https but 
getting http response:  “dockerplugin.create_and_start_container_for_platforms' 
-> 500 Server Error: Internal Server Error ("{"message":"Get 
https://10.12.5.80:5000/v1/_ping:
 http: server gave HTTP response to HTTPS client"}")”  Is this a new Nexus 
docker registry that only supports http?

Lusheng

From: 
>
 on behalf of Gary Wu >
Date: Thursday, January 11, 2018 at 11:41 AM
To: onap-discuss 
>
Subject: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Hi DCAE team,

Since last night the Amsterdam MR has been failing to spin up DCAE components.  
Can you take a look?

You can use the SB-05 environment to debug the issue.

Thanks,
Gary


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

2018-01-11 Thread GILBERT, MAZIN E (MAZIN E)

+1

Please add the candidate’s company plus existing committers.


On Jan 11, 2018, at 6:57 PM, MAHER, RANDA 
> wrote:

***Security Advisory: This Message Originated Outside of AT ***
Reference http://cso.att.com/EmailSecurity/IDSP.html for more information.

Dear TSC,

Please consider request below for Committer Promotion for APPC project.

https://wiki.onap.org/pages/viewpage.action?pageId=22251669

One of our existing committers has indicated that he will  step down from 
Committer to Contributor role.
Existing Committers have all voted +1 on Taka Cho promotion to Committer.

Thanks, Randa
APPC PTL
___
ONAP-TSC mailing list
onap-...@lists.onap.org
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Dtsc=DwICAg=LFYZ-o9_HUMeMTSQicvjIg=2dwD7a5k4V9cZl09O7uTpejnZMF8aa01W3yMqrrZC5Y=NXGqSa5NxTHo7zyxUrPP49eLYsmXzI4yh64s3B4oM5A=Evsqbp4rRCVLOh5p5fjHYs14lo95L06AtvAB_oZldfM=

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

2018-01-11 Thread Dhananjay Pavgi

+1


Thanks & regards,

Dhananjay Pavgi

Tech Mahindra Ltd

+91 98220 22264


-- Original message--

From: MAHER, RANDA

Date: Fri, 12 Jan 2018 05:29

To: onap-...@lists.onap.org;

Cc: onap-discuss@lists.onap.org;

Subject:[onap-tsc] Committer Promotion Request for [appc]

Dear TSC,

Please consider request below for Committer Promotion for APPC project.

https://wiki.onap.org/pages/viewpage.action?pageId=22251669

One of our existing committers has indicated that he will  step down from 
Committer to Contributor role.
Existing Committers have all voted +1 on Taka Cho promotion to Committer.

Thanks, Randa
APPC PTL


Disclaimer:  This message and the information contained herein is proprietary 
and confidential and subject to the Tech Mahindra policy statement, you may 
review the policy at http://www.techmahindra.com/Disclaimer.html 
 externally 
http://tim.techmahindra.com/tim/disclaimer.html 
 internally within 
TechMahindra.


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

2018-01-11 Thread JI, LUSHENG (LUSHENG)

Gary,

Unfortunately, that is not an easy fix.

Is it possible to add https to this registry?

If not, This is what I did to fix SB-05: getting into dcae-bootstrap vm and run 
this:
sudo sed -ie 's/10.12.5.80:5000/nexus3.onap.org:10001/g' 
/opt/app/config/invinputs.yaml /opt/config/nexus_docker_repo.txt
then rerun /opt/dcae2_vm_init.sh.

Lusheng


From: Gary Wu 
Date: Thursday, January 11, 2018 at 4:22 PM
To: "JI, LUSHENG (LUSHENG)" , onap-discuss 

Subject: RE: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Hi Lusheng,

10.12.5.80 is a docker cache local within the Wind River lab that allows us to 
dramatically speed up ONAP spin-up.   Unfortunately it only supports http.  The 
workaround for this is to configure the VM to allow insecure registries 
(https://docs.docker.com/registry/insecure/#deploy-a-plain-http-registry)
 by adding a /etc/docker/daemon.json file with the following content:

{
  "insecure-registries" : ["10.12.5.80:5000"]
}

Is this something that can be added/configured in the DCAE VMs relatively 
easily?  For all the other VMs I was able to add such a file by modifying the 
heat template, but it’s not clear how we can do so for the DCAE VMs.

Thanks,
Gary

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Thursday, January 11, 2018 1:01 PM
To: Gary Wu ; onap-discuss 
Subject: Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Gary,

The log of dcae bootstrap docker container shows that there was a transient 
problem last night.  One of the artifacts hosted by LF Nexus server failed to 
download (getting “502 bad gateway” response).   I dumped the docker log to 
file /opt/log-docker-15afe9c18611-20180110 on the dcae bootstrap VM and line 
and line 1515 shows the problem.

So after cleaning up I re-ran the vm_init bash script again.  The deployment 
has passed the failure point last night.

Now there is another problem.   One of DCAE subcomponent failed due to now able 
to contact docker registry.  I found that the configuration for nexus docker 
repo is set to “10.12.5.80:5000”.  The error message says expects https but 
getting http response:  “dockerplugin.create_and_start_container_for_platforms' 
-> 500 Server Error: Internal Server Error ("{"message":"Get 
https://10.12.5.80:5000/v1/_ping:
 http: server gave HTTP response to HTTPS client"}")”  Is this a new Nexus 
docker registry that only supports http?

Lusheng

From: 
>
 on behalf of Gary Wu >
Date: Thursday, January 11, 2018 at 11:41 AM
To: onap-discuss 
>
Subject: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Hi DCAE team,

Since last night the Amsterdam MR has been failing to spin up DCAE components.  
Can you take a look?

You can use the SB-05 environment to debug the issue.

Thanks,
Gary


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] MUSIC Proposal for Beijing

2018-01-11 Thread GILBERT, MAZIN E (MAZIN E)

TSC Members,

I met this afternoon with members of the OOM project and MUSIC team.
I confirmed the following

Although on the key common area among both projects is resiliency,
OOM’s scope is life cycle management of the ONAP platform itself.
Scope is the following
https://wiki.onap.org/display/DW/ONAP+Operations+Manager+Project

MUSIC, on the other hand, is focusing on database resiliency/scalability across 
sites.
MUSIC and OOM are complimentary, and MUSIC is optional and is relevant to only
few projects. Per authors, the scope is the following

MUSIC is a shared service with recipes that individual ONAP components and 
micro-service
can use for state replication, consistency management and state ownership 
across geo-distributed sites.
MUSIC will make sure that the right service data is available at the right 
place, and at the right time
to enable federated active-active operation of ONAP.

The OOM team recommended that MUSIC should be an independent project.
My criteria are for architecture input which has been vetted already. OOM
to provide recommendation which they have, and finally, the TSC to vote.

Kenny will shortly send out a vote for MUSIC. Please go ahead and vote
as +1, 0, -1. If you have not been part of the discussions and have questions,
then please follow up directly with the OOM and MUSIC teams.

Thanks, and appreciate everyone for doing their due diligence.

Mazin




___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] Committer Promotion Request for [appc]

2018-01-11 Thread MAHER, RANDA

Dear TSC,

Please consider request below for Committer Promotion for APPC project.

https://wiki.onap.org/pages/viewpage.action?pageId=22251669

One of our existing committers has indicated that he will  step down from 
Committer to Contributor role.
Existing Committers have all voted +1 on Taka Cho promotion to Committer.

Thanks, Randa
APPC PTL
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] OOM Option to preserve VNC Jump server ?

2018-01-11 Thread Mike Elliott

Hi Brian,

I have opened https://jira.onap.org/browse/OOM-576 to track this and it is 
currently being investigated.

Thanks for the suggested improvement,
Mike.

On Jan 11, 2018, at 11:59 AM, FREEMAN, BRIAN D 
> wrote:

I have been re-installing ONAP via OOM’s cd.sh script a couple times to test 
patches.

Turns out the jump server (VNC ) on a re-install loses all the data as 
expected. Its a bit of a pain.

Would it be feasible to preserve that container as an option on a re-install 
via cd.sh or put its file system into the dockerdata-nfs (preserving things 
like apt-get install vim, apt-get install wget , wget postman (and the 
collections for ONAP REST API calls), apt-get install libgconf-2-4,, etc)  ?

Either method would work for me but seems like not  deleteing vnc as an option 
might be the easiest ?

Brian

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] OOM Robot Distribute

2018-01-11 Thread Alexis de Talhouët

That’s a good solution Brian, not that we haven’t thought about it. 

We’re looking into un-forking every config bit we forked to integrate the fork 
we’ve done correctly in each project.

ONAP has 80+ containers, hence we forked config at first, but there is a long 
journey in front of us to un-fork things, and it’s not always as strait-forward 
as in this case.
Moreover, it implies ppl are willing to accept update to their config to 
satisfy OOM needs. In R1 we were told OOM isn’t the default deploy solution, so 
our updates were discarded.

Now Amsterdam is out, ppl are getting more aware of the mechanic of OOM. 
because it’s getting better. So Maybe now is a good time to fix things.

But the issue is slightly bigger than this. Basically, we should centralized 
configuration and derived properties of properties files from there. This way, 
we update only one place, and everybody is happy. But that’s another battle for 
another time.

Long story short, fork was easier for us to get where we are, but we always 
knew this was not a permanent solution: see OOM-10 


Alexis

> On Jan 11, 2018, at 4:39 PM, FREEMAN, BRIAN D  wrote:
> 
> So why not submit a change to testsuite so they split it into two IP’s and 
> modify the robot_vm_install.sh to ocpy the input into the two variable so 
> that we can use the same asdc_interface.robot for either HEAT or OOM ?
>  
> Testsuite will be adding to the asdc_interface.robot over time (as in this 
> case) .
>  
> I’m sure you dont want to maintain these files in OOM long term.
>  
> Brian
>  
>  
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com 
> ] 
> Sent: Thursday, January 11, 2018 4:29 PM
> To: FREEMAN, BRIAN D >
> Cc: onap-discuss@lists.onap.org 
> Subject: Re: [onap-discuss] OOM Robot Distribute
>  
> It’s the same IP address in the HEAT deployment. In OOM it’s not the same.
>  
> sdc-fe.onap-sdc for frontend —> GLOBAL_INJECTED_SDC_FE_IP_ADDR
> sdc-be.onap-sdc for backend —> GLOBAL_INJECTED_SDC_BE_IP_ADDR
>  
> Alexis
> 
> 
> On Jan 11, 2018, at 4:07 PM, FREEMAN, BRIAN D  > wrote:
>  
> The front end and back of SDC are the same IP address so its not clear to me 
> why you had to change anything in the asdc_interface.robot ?
>  
> Brian
>  
>  
> root@onapoom3:/dockerdata-nfs/onap/robot/robot/resources# diff 
> asdc_interface.robot asdc_interface.robot.old
> 47,48c47,48
> < ${ASDC_FE_ENDPOINT} 
> ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_IP_ADDR}:${GLOBAL_ASDC_FE_PORT}
> < ${ASDC_BE_ENDPOINT} 
> ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_IP_ADDR}:${GLOBAL_ASDC_BE_PORT}
> ---
> > ${ASDC_FE_ENDPOINT} 
> > ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_FE_IP_ADDR}:${GLOBAL_ASDC_FE_PORT}
> > ${ASDC_BE_ENDPOINT} 
> > ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_BE_IP_ADDR}:${GLOBAL_ASDC_BE_PORT}
> 56d55
> < ${catalog_resources}=   Create Dictionary
> 62d60
> < \Set To Dictionary${catalog_resources}   
> ${loop_catalog_resource_id}=${loop_catalog_resource_resp}
> 74,75c72,73
> < [Return]${catalog_service_resp['name']}
> ${loop_catalog_resource_resp['name']}${vf_module}   
> ${catalog_resource_ids}${catalog_service_id}   ${catalog_resources}
> < 
> ---
> > [Return]${catalog_service_resp['name']}
> > ${loop_catalog_resource_resp['name']}${vf_module}   
> > ${catalog_resource_ids}${catalog_service_id}
> > 
> 297,298c295,296
> <  [Documentation]Creates an asdc Software Product and returns its id
> <  [Arguments]${software_product_id}${file_path}  
> ${version_id}=0.1
> ---
> > [Documentation]Creates an asdc Software Product and returns its id
> > [Arguments]${software_product_id}${file_path}   
> > ${version_id}=0.1
> 301,302c299,300
> <  ${resp}=Run ASDC Post Files Request   
> ${ASDC_VENDOR_SOFTWARE_PRODUCT_PATH}/${software_product_id}/versions/${version_id}${ASDC_VENDOR_SOFTWARE_UPLOAD_PATH}
>   ${files}${ASDC_DESIGNER_USER_ID}
> <  Should Be Equal As Strings  ${resp.status_code}   200
> ---
> > ${resp}=Run ASDC Post Files Request
> > ${ASDC_VENDOR_SOFTWARE_PRODUCT_PATH}/${software_product_id}/versions/${version_id}${ASDC_VENDOR_SOFTWARE_UPLOAD_PATH}
> >  ${files}${ASDC_DESIGNER_USER_ID}
> >   Should Be Equal As Strings  ${resp.status_code} 200
>  
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com 
> ] 
> Sent: Thursday, January 11, 2018 4:01 PM
> To: FREEMAN, BRIAN D >
> Cc: onap-discuss@lists.onap.org 
> Subject: Re: [onap-discuss] OOM Robot Distribute
>  
>  
> 
> 
> 
> On Jan 11, 2018, at 4:00 PM, Alexis de Talhouët

Re: [onap-discuss] OOM Robot Distribute

2018-01-11 Thread FREEMAN, BRIAN D

So why not submit a change to testsuite so they split it into two IP’s and 
modify the robot_vm_install.sh to ocpy the input into the two variable so that 
we can use the same asdc_interface.robot for either HEAT or OOM ?

Testsuite will be adding to the asdc_interface.robot over time (as in this 
case) .

I’m sure you dont want to maintain these files in OOM long term.

Brian


From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Thursday, January 11, 2018 4:29 PM
To: FREEMAN, BRIAN D 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] OOM Robot Distribute

It’s the same IP address in the HEAT deployment. In OOM it’s not the same.

sdc-fe.onap-sdc for frontend —> GLOBAL_INJECTED_SDC_FE_IP_ADDR
sdc-be.onap-sdc for backend —> GLOBAL_INJECTED_SDC_BE_IP_ADDR

Alexis


On Jan 11, 2018, at 4:07 PM, FREEMAN, BRIAN D 
> wrote:

The front end and back of SDC are the same IP address so its not clear to me 
why you had to change anything in the asdc_interface.robot ?

Brian


root@onapoom3:/dockerdata-nfs/onap/robot/robot/resources# diff 
asdc_interface.robot asdc_interface.robot.old
47,48c47,48
< ${ASDC_FE_ENDPOINT} 
${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_IP_ADDR}:${GLOBAL_ASDC_FE_PORT}
< ${ASDC_BE_ENDPOINT} 
${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_IP_ADDR}:${GLOBAL_ASDC_BE_PORT}
---
> ${ASDC_FE_ENDPOINT} 
> ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_FE_IP_ADDR}:${GLOBAL_ASDC_FE_PORT}
> ${ASDC_BE_ENDPOINT} 
> ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_BE_IP_ADDR}:${GLOBAL_ASDC_BE_PORT}
56d55
< ${catalog_resources}=   Create Dictionary
62d60
< \Set To Dictionary${catalog_resources}   
${loop_catalog_resource_id}=${loop_catalog_resource_resp}
74,75c72,73
< [Return]${catalog_service_resp['name']}
${loop_catalog_resource_resp['name']}${vf_module}   ${catalog_resource_ids} 
   ${catalog_service_id}   ${catalog_resources}
<
---
> [Return]${catalog_service_resp['name']}
> ${loop_catalog_resource_resp['name']}${vf_module}   
> ${catalog_resource_ids}${catalog_service_id}
>
297,298c295,296
<  [Documentation]Creates an asdc Software Product and returns its id
<  [Arguments]${software_product_id}${file_path}  ${version_id}=0.1
---
> [Documentation]Creates an asdc Software Product and returns its id
> [Arguments]${software_product_id}${file_path}   ${version_id}=0.1
301,302c299,300
<  ${resp}=Run ASDC Post Files Request   
${ASDC_VENDOR_SOFTWARE_PRODUCT_PATH}/${software_product_id}/versions/${version_id}${ASDC_VENDOR_SOFTWARE_UPLOAD_PATH}
  ${files}${ASDC_DESIGNER_USER_ID}
<  Should Be Equal As Strings  ${resp.status_code}   200
---
> ${resp}=Run ASDC Post Files Request
> ${ASDC_VENDOR_SOFTWARE_PRODUCT_PATH}/${software_product_id}/versions/${version_id}${ASDC_VENDOR_SOFTWARE_UPLOAD_PATH}
>  ${files}${ASDC_DESIGNER_USER_ID}
>   Should Be Equal As Strings  ${resp.status_code} 200

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Thursday, January 11, 2018 4:01 PM
To: FREEMAN, BRIAN D >
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] OOM Robot Distribute





On Jan 11, 2018, at 4:00 PM, Alexis de Talhouët 
> wrote:

Robot can point to HEAT’s VM IP, whereas robot point to the service directly..

Not clear. In the HEAT setup, robot points to the SDC VM IP for that resources, 
whereas for the OOM setup, we point directly to the frontend or backend service.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] OOM Robot Distribute

2018-01-11 Thread Alexis de Talhouët

It’s the same IP address in the HEAT deployment. In OOM it’s not the same.

sdc-fe.onap-sdc for frontend —> GLOBAL_INJECTED_SDC_FE_IP_ADDR
sdc-be.onap-sdc for backend —> GLOBAL_INJECTED_SDC_BE_IP_ADDR

Alexis

> On Jan 11, 2018, at 4:07 PM, FREEMAN, BRIAN D  wrote:
> 
> The front end and back of SDC are the same IP address so its not clear to me 
> why you had to change anything in the asdc_interface.robot ?
>  
> Brian
>  
>  
> root@onapoom3:/dockerdata-nfs/onap/robot/robot/resources# diff 
> asdc_interface.robot asdc_interface.robot.old
> 47,48c47,48
> < ${ASDC_FE_ENDPOINT} 
> ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_IP_ADDR}:${GLOBAL_ASDC_FE_PORT}
> < ${ASDC_BE_ENDPOINT} 
> ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_IP_ADDR}:${GLOBAL_ASDC_BE_PORT}
> ---
> > ${ASDC_FE_ENDPOINT} 
> > ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_FE_IP_ADDR}:${GLOBAL_ASDC_FE_PORT}
> > ${ASDC_BE_ENDPOINT} 
> > ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_BE_IP_ADDR}:${GLOBAL_ASDC_BE_PORT}
> 56d55
> < ${catalog_resources}=   Create Dictionary
> 62d60
> < \Set To Dictionary${catalog_resources}   
> ${loop_catalog_resource_id}=${loop_catalog_resource_resp}
> 74,75c72,73
> < [Return]${catalog_service_resp['name']}
> ${loop_catalog_resource_resp['name']}${vf_module}   
> ${catalog_resource_ids}${catalog_service_id}   ${catalog_resources}
> < 
> ---
> > [Return]${catalog_service_resp['name']}
> > ${loop_catalog_resource_resp['name']}${vf_module}   
> > ${catalog_resource_ids}${catalog_service_id}
> > 
> 297,298c295,296
> <  [Documentation]Creates an asdc Software Product and returns its id
> <  [Arguments]${software_product_id}${file_path}  
> ${version_id}=0.1
> ---
> > [Documentation]Creates an asdc Software Product and returns its id
> > [Arguments]${software_product_id}${file_path}   
> > ${version_id}=0.1
> 301,302c299,300
> <  ${resp}=Run ASDC Post Files Request   
> ${ASDC_VENDOR_SOFTWARE_PRODUCT_PATH}/${software_product_id}/versions/${version_id}${ASDC_VENDOR_SOFTWARE_UPLOAD_PATH}
>   ${files}${ASDC_DESIGNER_USER_ID}
> <  Should Be Equal As Strings  ${resp.status_code}   200
> ---
> > ${resp}=Run ASDC Post Files Request
> > ${ASDC_VENDOR_SOFTWARE_PRODUCT_PATH}/${software_product_id}/versions/${version_id}${ASDC_VENDOR_SOFTWARE_UPLOAD_PATH}
> >  ${files}${ASDC_DESIGNER_USER_ID}
> >   Should Be Equal As Strings  ${resp.status_code} 200
>  
> From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com] 
> Sent: Thursday, January 11, 2018 4:01 PM
> To: FREEMAN, BRIAN D 
> Cc: onap-discuss@lists.onap.org
> Subject: Re: [onap-discuss] OOM Robot Distribute
>  
>  
> 
> 
> On Jan 11, 2018, at 4:00 PM, Alexis de Talhouët  > wrote:
>  
> Robot can point to HEAT’s VM IP, whereas robot point to the service directly..
>  
> Not clear. In the HEAT setup, robot points to the SDC VM IP for that 
> resources, whereas for the OOM setup, we point directly to the frontend or 
> backend service.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

2018-01-11 Thread Gary Wu

Hi Lusheng,

10.12.5.80 is a docker cache local within the Wind River lab that allows us to 
dramatically speed up ONAP spin-up.   Unfortunately it only supports http.  The 
workaround for this is to configure the VM to allow insecure registries 
(https://docs.docker.com/registry/insecure/#deploy-a-plain-http-registry) by 
adding a /etc/docker/daemon.json file with the following content:

{
  "insecure-registries" : ["10.12.5.80:5000"]
}

Is this something that can be added/configured in the DCAE VMs relatively 
easily?  For all the other VMs I was able to add such a file by modifying the 
heat template, but it’s not clear how we can do so for the DCAE VMs.

Thanks,
Gary

From: JI, LUSHENG (LUSHENG) [mailto:l...@research.att.com]
Sent: Thursday, January 11, 2018 1:01 PM
To: Gary Wu ; onap-discuss 
Subject: Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Gary,

The log of dcae bootstrap docker container shows that there was a transient 
problem last night.  One of the artifacts hosted by LF Nexus server failed to 
download (getting “502 bad gateway” response).   I dumped the docker log to 
file /opt/log-docker-15afe9c18611-20180110 on the dcae bootstrap VM and line 
and line 1515 shows the problem.

So after cleaning up I re-ran the vm_init bash script again.  The deployment 
has passed the failure point last night.

Now there is another problem.   One of DCAE subcomponent failed due to now able 
to contact docker registry.  I found that the configuration for nexus docker 
repo is set to “10.12.5.80:5000”.  The error message says expects https but 
getting http response:  “dockerplugin.create_and_start_container_for_platforms' 
-> 500 Server Error: Internal Server Error ("{"message":"Get 
https://10.12.5.80:5000/v1/_ping: http: server gave HTTP response to HTTPS 
client"}")”  Is this a new Nexus docker registry that only supports http?

Lusheng

From: 
>
 on behalf of Gary Wu >
Date: Thursday, January 11, 2018 at 11:41 AM
To: onap-discuss 
>
Subject: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Hi DCAE team,

Since last night the Amsterdam MR has been failing to spin up DCAE components.  
Can you take a look?

You can use the SB-05 environment to debug the issue.

Thanks,
Gary


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] OOM Robot Distribute

2018-01-11 Thread FREEMAN, BRIAN D

The front end and back of SDC are the same IP address so its not clear to me 
why you had to change anything in the asdc_interface.robot ?

Brian


root@onapoom3:/dockerdata-nfs/onap/robot/robot/resources# diff 
asdc_interface.robot asdc_interface.robot.old
47,48c47,48
< ${ASDC_FE_ENDPOINT} 
${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_IP_ADDR}:${GLOBAL_ASDC_FE_PORT}
< ${ASDC_BE_ENDPOINT} 
${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_IP_ADDR}:${GLOBAL_ASDC_BE_PORT}
---
> ${ASDC_FE_ENDPOINT} 
> ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_FE_IP_ADDR}:${GLOBAL_ASDC_FE_PORT}
> ${ASDC_BE_ENDPOINT} 
> ${GLOBAL_ASDC_SERVER_PROTOCOL}://${GLOBAL_INJECTED_SDC_BE_IP_ADDR}:${GLOBAL_ASDC_BE_PORT}
56d55
< ${catalog_resources}=   Create Dictionary
62d60
< \Set To Dictionary${catalog_resources}   
${loop_catalog_resource_id}=${loop_catalog_resource_resp}
74,75c72,73
< [Return]${catalog_service_resp['name']}
${loop_catalog_resource_resp['name']}${vf_module}   ${catalog_resource_ids} 
   ${catalog_service_id}   ${catalog_resources}
<
---
> [Return]${catalog_service_resp['name']}
> ${loop_catalog_resource_resp['name']}${vf_module}   
> ${catalog_resource_ids}${catalog_service_id}
>
297,298c295,296
<  [Documentation]Creates an asdc Software Product and returns its id
<  [Arguments]${software_product_id}${file_path}  ${version_id}=0.1
---
> [Documentation]Creates an asdc Software Product and returns its id
> [Arguments]${software_product_id}${file_path}   ${version_id}=0.1
301,302c299,300
<  ${resp}=Run ASDC Post Files Request   
${ASDC_VENDOR_SOFTWARE_PRODUCT_PATH}/${software_product_id}/versions/${version_id}${ASDC_VENDOR_SOFTWARE_UPLOAD_PATH}
  ${files}${ASDC_DESIGNER_USER_ID}
<  Should Be Equal As Strings  ${resp.status_code}   200
---
> ${resp}=Run ASDC Post Files Request
> ${ASDC_VENDOR_SOFTWARE_PRODUCT_PATH}/${software_product_id}/versions/${version_id}${ASDC_VENDOR_SOFTWARE_UPLOAD_PATH}
>  ${files}${ASDC_DESIGNER_USER_ID}
>   Should Be Equal As Strings  ${resp.status_code} 200

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Thursday, January 11, 2018 4:01 PM
To: FREEMAN, BRIAN D 
Cc: onap-discuss@lists.onap.org
Subject: Re: [onap-discuss] OOM Robot Distribute




On Jan 11, 2018, at 4:00 PM, Alexis de Talhouët 
> wrote:

Robot can point to HEAT’s VM IP, whereas robot point to the service directly..

Not clear. In the HEAT setup, robot points to the SDC VM IP for that resources, 
whereas for the OOM setup, we point directly to the frontend or backend service.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

2018-01-11 Thread JI, LUSHENG (LUSHENG)

Gary,

The log of dcae bootstrap docker container shows that there was a transient 
problem last night.  One of the artifacts hosted by LF Nexus server failed to 
download (getting “502 bad gateway” response).   I dumped the docker log to 
file /opt/log-docker-15afe9c18611-20180110 on the dcae bootstrap VM and line 
and line 1515 shows the problem.

So after cleaning up I re-ran the vm_init bash script again.  The deployment 
has passed the failure point last night.

Now there is another problem.   One of DCAE subcomponent failed due to now able 
to contact docker registry.  I found that the configuration for nexus docker 
repo is set to “10.12.5.80:5000”.  The error message says expects https but 
getting http response:  “dockerplugin.create_and_start_container_for_platforms' 
-> 500 Server Error: Internal Server Error ("{"message":"Get 
https://10.12.5.80:5000/v1/_ping: http: server gave HTTP response to HTTPS 
client"}")”  Is this a new Nexus docker registry that only supports http?

Lusheng

From:  on behalf of Gary Wu 

Date: Thursday, January 11, 2018 at 11:41 AM
To: onap-discuss 
Subject: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Hi DCAE team,

Since last night the Amsterdam MR has been failing to spin up DCAE components.  
Can you take a look?

You can use the SB-05 environment to debug the issue.

Thanks,
Gary


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] OOM Robot Distribute

2018-01-11 Thread Alexis de Talhouët

> On Jan 11, 2018, at 4:00 PM, Alexis de Talhouët  
> wrote:
> 
> Robot can point to HEAT’s VM IP, whereas robot point to the service directly..

Not clear. In the HEAT setup, robot points to the SDC VM IP for that resources, 
whereas for the OOM setup, we point directly to the frontend or backend service.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] OOM Robot Distribute

2018-01-11 Thread Alexis de Talhouët

Brian,

For some reason, we had to fork asdc_interface.robot script, that’s why it’s 
not up-to-date, please create a ticket for this and assign it to me.
The reasons are hostname resolution are different from HEAT and OOM. Robot can 
point to HEAT’s VM IP, whereas robot point to the service directly..

Thanks,
Alexis

> On Jan 11, 2018, at 3:47 PM, FREEMAN, BRIAN D  wrote:
> 
> Alexis, Michael,
>  
> I was using robot ete-k8s.sh from amsterdam release and the version of 
> asdc_interface.robot in dockerdata-nfs was out of date.
> I cant seem to find where it got loaded from since the asdc_interface.robot 
> wasn’t compatible with the robot testsuite (the return parameter list from 
> Model Distribution in the testsuite didnt match the number returns by the 
> asdc-interface so an error of “16:03:12.828 FAIL   Cannot set 
> variables: Expected 6 return values, got 5.
> “ was being returned for each model that was distributed. The models did 
> successful distrubte but robot was failing on the check. When I did a git 
> clone and copy the asdc_interface.robot to the dockerdata-nfs directory for 
> robot ete-k8.sh distribute succeeded.
>  
> Is this just something I did in using cd.sh -b amsterdam or something else ?
>  
> Brian
>  
> ___
> onap-discuss mailing list
> onap-discuss@lists.onap.org
> https://lists.onap.org/mailman/listinfo/onap-discuss

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] OOM Robot Distribute

2018-01-11 Thread FREEMAN, BRIAN D

Alexis, Michael,

I was using robot ete-k8s.sh from amsterdam release and the version of 
asdc_interface.robot in dockerdata-nfs was out of date.
I cant seem to find where it got loaded from since the asdc_interface.robot 
wasn't compatible with the robot testsuite (the return parameter list from 
Model Distribution in the testsuite didnt match the number returns by the 
asdc-interface so an error of "16:03:12.828 FAIL   Cannot set 
variables: Expected 6 return values, got 5.
" was being returned for each model that was distributed. The models did 
successful distrubte but robot was failing on the check. When I did a git clone 
and copy the asdc_interface.robot to the dockerdata-nfs directory for robot 
ete-k8.sh distribute succeeded.

Is this just something I did in using cd.sh -b amsterdam or something else ?

Brian

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] clarification question on ONPA R2 resilience requirement

2018-01-11 Thread Jason Hunt

Hi Lusheng,

Thanks for the questions & attention to detail:

For #1, go with what is on the detailed requirements page... just 
"reroute" is necessary.  However, if you combine it with the scalability 
requirement, then there will be a need to add a new instance within the 
site... whether that is considered "recovery" or not is questionable.  In 
the cloud native world, you should be able to kill any process and a new 
process will take its place.

For #2, the idea was to run a test where you fail one of the stateful 
instances while running a load on the system.  You then measure how much 
data is "lost" while the recovery is happening... typically, some data 
doesn't get replicated if an instance gets killed.  Does that make sense?

Let me know if this explanation helped.


Regards,
Jason Hunt 
Executive Software Architect, IBM 

Phone: 314-749-7422
Email: djh...@us.ibm.com
Twitter: @DJHunt
 



From:   "JI, LUSHENG  (LUSHENG)" 
To: Jason Hunt 
Cc: Gildas Lanilis , "LEFEVRE, CATHERINE" 
, "FREEMAN, BRIAN D" , "Kumar Skand 
Priya,  Viswanath V via onap-discuss" 
Date:   01/10/2018 04:30 PM
Subject:clarification question on ONPA R2 resilience requirement



Hello Jason,
 
I have couple of questions regarding the resilience requirement for ONAP 
R2 that I hope to get your clarification. 
 
In particular, for the level 2 requirement, 
The table in your recommendation ppt shows level 2 resilience as 
“automated detection and recovery (single site)”, but the detailed 
requirement wiki page (
https://wiki.onap.org/pages/viewpage.action?pageId=15998867) shows no 
“recovery”, only “reroute”.  Is failed component recovery part of level 2?
On the detailed requirement page (
https://wiki.onap.org/pages/viewpage.action?pageId=15998867), the third 
bullet under level 2 resilience states:  “stateful components: establish 
baseline of data loss for a component failure within a site”.  What 
exactly does this mean? 
 
Thanks,
 
Lusheng Ji
ONPA DCAE



___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [integration] RE: Jenkins CSIT requiring attention

2018-01-11 Thread Gary Wu

It looks like the latest versions of the selenium robot libraries were 
incompatible with ExtendedSelenium2Library.  I’ve changed to script to use a 
known-good older version here:  https://gerrit.onap.org/r/#/c/27973/

The latest run of 
https://jenkins.onap.org/view/portal/job/portal-master-csit-testsuite/165/console
 is no longer having this issue.

Thanks,
Gary

From: KOYA, KISHORE [mailto:kk7...@att.com]
Sent: Thursday, January 11, 2018 8:30 AM
To: TALASILA, MANOOP ; SHI, LEIMENG 
; Gary Wu 
Cc: HOTZE, BECKY L 
Subject: RE: Jenkins CSIT requiring attention

I do see below error in logs

[cid:image002.png@01D38AC6.86C91880]


Long back Gary fixed this issue. Please find the attached mail for same

Gary, could you please have a look into this issue

Thanks ,
Kishore Koya
ECOMP Open Source
Call Me @ 469-831-7289
Email : kk7...@att.com | Q me @ 
[cid:image002.jpg@01D38AD3.4B7B7130] 

From: KOYA, KISHORE
Sent: Thursday, January 11, 2018 10:16 AM
To: TALASILA, MANOOP 
>; SHI, LEIMENG 
>
Cc: HOTZE, BECKY L >
Subject: RE: Jenkins CSIT requiring attention

Let me have a look into this

Thanks ,
Kishore Koya
ECOMP Open Source
Call Me @ 469-831-7289
Email : kk7...@att.com | Q me @ 
[cid:image005.jpg@01D38AC6.86C91880] 

From: TALASILA, MANOOP
Sent: Thursday, January 11, 2018 10:14 AM
To: KOYA, KISHORE >; SHI, LEIMENG 
>
Subject: FW: Jenkins CSIT requiring attention

Hi Kishore,

Liemeng mentioned that you are not assigned to ONAP, we are trying to come up 
with a plan for the testing efforts. However, if you get chance, can you please 
guide us on the below csit tests failure which were setup by you? Thanks.

PORTAL
[ailed]

[%]

portal-master-csit-testsuite

1 mo 8 days - 
#125

12 hr - 
#163

9 min 8 sec

1 / 33 passed



[ailed]

[%]

portal-sdk-master-csit-testsuite

1 mo 7 days - 
#73

23 hr - 
#110

8 min 41 sec

0 / 8 passed

























Manoop


From: "MCCRAY, CHRISTOPHER" >
Date: Thursday, January 11, 2018 at 8:27 AM
To: "LEFEVRE, CATHERINE" >, 
"LANDO, MICHAEL" >, "FREEMAN, 
BRIAN D" >, "BENNETT, RICH" 
>, "SPATSCHECK, OLIVER (OLIVER)" 
>, "FORSYTH, JAMES" 
>, "TIMONEY, DAN" 
>, "JI, LUSHENG (LUSHENG)" 
>, "TALASILA, MANOOP 
(MANOOP)" >, 
"SONSINO, OFIR" >, "HU, JUN 
NICOLAS" >, "DRAGOSH, PAMELA L (PAM)" 
>, "KOYA, 
RAMPRASAD" >, "GUDISENA, VARUNESHWAR" 
>, "DAUGHERTY, ROBERT E" 
>, "NGUEKO, GERVAIS-MARTIAL" 
>, "FAZAL, ABBAS M (ABBAS)" 
>, "HERNANDEZ-HERRERO, 
JORGE" >, "MAHER, RANDA" 
>, "GUDISENA, VARUNESHWAR" 
>, "NGUEKO, GERVAIS-MARTIAL" 
>, "CLOSSET, CHRISTOPHE" 
>
Cc: "UNO, LAWRENCE H (LARRY)" 
>, "O'KEEFE, TIMOTHY J" 
>
Subject: Jenkins CSIT requiring attention

Good morning team,

Please take a moment to review Jenkins jobs that are in a failed or N/A status.

APPC
Fix or remove Jenkins jobs where Last Success is “N/A”
[ailed]

[onap-discuss] Did You Know?

2018-01-11 Thread Alexis de Talhouët


Did You Know?
OOM makes services available on any Node in a K8S cluster using a NodePort.
 
This allows a service to be reachable on any node in the cluster, using a 
statically assigned NodePort (default range: 3-32767). NodePorts are 
automatically mapped to the internal port of a service.

Some examples of services available today using NodePorts:
30023 --> 8080 (m)so

All services are mapped here: in OOM wiki 
.



https://kubernetes.io/docs/concepts/services-networking/service/#type-nodeport 


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [E] [oom] OOM Installation Problem | Unable to bring up Portal Pod

2018-01-11 Thread Michael O'Brien

Viswa, Karthik,
   Hi, we are here to help you through this - I may have replied to an earlier 
mail.
   Just verifying you are OK now - it looks like you have increased your ram 
after talking to Mandeep and myself  - yes portal is at the top of the 
hierarchy and will not start unless all the pods in its yaml dependency section 
are up first -

https://lists.onap.org/pipermail/onap-discuss/2018-January/007328.html
https://lists.onap.org/pipermail/onap-discuss/2018-January/007299.html

thank you
/michael

Karthik sdkarthikk at gmail.com 

Thu Jan 11 12:13:17 UTC 2018

  *   Previous message: [onap-discuss] OOM Installation Problem | Unable to 
bring up Portal 
Pod
  *   Next message: [onap-discuss] How to test the vFW configuration and 
deployment
  *   Messages sorted by: [ date 
] [ 
thread 
] 
[ subject 
] 
[ author 
]

Hi Mandeep, Alexis, Michael, Viswa ,

Thanks a lot for your quick responses and suggestions.

As Michael suggested that RAM should be more than 55 G, so I increased it
to 128G.
After increasing RAM size , I am able to install ONAP using OOM. Thanks!

Regards,
Karthik.

On 11 Jan 2018 03:42, "Mandeep Khinda" https://lists.onap.org/mailman/listinfo/onap-discuss>> wrote:

> Hi Karthik,
>
> Can you share some more output from your k8s cluster (in a text format if
> possible)
>
>
>
> kubectl -n onap-portal get events|grep portalapps
>
>
>
> This will show the events that took place and hopefully the reason why it
> is stuck at initializing.  In my experience it is usually image pulling
> issues and/or k8s cluster resource limits are maxed out.
>
>
>
>
>
> *Mandeep Khinda*
>
> Software Development
>
> *Open Network Division*

From: 
onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Karthik
Sent: Tuesday, January 9, 2018 10:19
To: onap-discuss@lists.onap.org
Subject: [onap-discuss] OOM Installation Problem | Unable to bring up Portal Pod

From: Michael O'Brien
Sent: Wednesday, January 10, 2018 07:15
To: 'Karthik' ; onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] OOM Installation Problem | Unable to bring up 
Portal Pod

Karthik,
   Hi, it's Mike, welcome to ONAP.  Failure of vnc-portal initialization by 
itself usually means you are running a currently unsupported version of helm on 
the server side of Kubernetes.
   Do a "helm version" - you should see 2.3.x on both the client and server - 
if you see 2.6 then you installed :latest for rancher and not v1.6.10
   Verify you are running the following detailed on the wiki.
   Rancher 1.6.10
   Kubernetes 1.8.x - to 1.8.6
   Helm 2.3.x
   Likely you are running docker 1.12.x

   Also to bring up all of ONAP you will need at least 55G.

   See
https://jira.onap.org/browse/OOM-441
https://jira.onap.org/browse/OOM-486

   Thank you
   /michael

From: Alexis de Talhouët [mailto:adetalhoue...@gmail.com]
Sent: Tuesday, January 9, 2018 14:40
To: Kumar Skand Priya, Viswanath V 
Cc: Michael O'Brien ; David Sauvageau 
; onap-discuss@lists.onap.org; Karthik 

Subject: Re: [onap-discuss] [E] [oom] OOM Installation Problem | Unable to 
bring up Portal Pod

Hi,

Can you send the logs?

Thanks,
Alexis

On Jan 9, 2018, at 2:37 PM, Kumar Skand Priya, Viswanath V via onap-discuss 
> wrote:

+ David +Michael

Dear OOM Team,

Could you please help us here?

BR,
Viswa

[http://ss7.vzw.com/is/image/VerizonWireless/vz-sig-verizon?$defaultscale$]

Viswanath Kumar Skand Priya
Architect
Verizon Network Ops & Eng

On Tue, Jan 9, 2018 at 8:48 PM, Karthik 
> wrote:

Hi Team , Good day !

I followed the Quick

[onap-discuss] FW: HF2 Network Downtime Jan 12 2018

2018-01-11 Thread Gooch, Stephen

Appologies for the late notice, the lab where the ONAP developers POD is 
located will be off line tomorrow morning from 07:00 to 09:00 PST, see below 
message from Intel IT.
I was added to the IT mailing list today, thus, in the future notices to the 
ONAP community will go out in advance.
Br,
- Stephen

 Forwarded Message 


REMINDER


Summary:

HF2 Lab Network is being switched to a new Router
Downtime will be from 7-9am
Testing of Network to occur from 8-9am
Application testing is to be performed by System Owner

Downtime to upgrade to core.  1-2-hour downtime for local area network changes.

No impact from the firewall perspective.  Same rules for now.  There will be a 
second phase to characterize traffic at a later date.

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] for sdc vnfd model , could a user-defined property be added in the node property for vdu, cpd, storage

2018-01-11 Thread x...@certusnet.com.cn

hi,
for sdc vnfd model ,  could  a user-defined property be added in the node 
property for vdu, cpd, storage ..

for example:
-type define-
UserDefine:
derived_from: tosca.datatypes.Root
properties:
name:
type: string
description: restful uri supported
required: true
value:
type: string
parameters:
type: list
required: false
entry_schema:
type: UserDefine  
---

 --use the type   
parameters:
type: list
required: false
entry_schema:
type: UserDefine  

--

when i import a nfpackage and create a vf in sdc, a problem is raised during 
creating vf , the alarm is "requested seq_id property was not found", as showed 
in the following illustration 1. 

I add a "seq_id" proterty in a vducpd node , then i meet the problem.


illustration 1

thanks.


CertusNet
赛特斯信息科技股份有限公司
徐剑波 | 技术经理
上海市杨浦区淞沪路433号创智天地企业中心6号楼10-11层
 
手机：13816780815
公司网址：www.certusnet.com.cn
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] OOM Option to preserve VNC Jump server ?

2018-01-11 Thread FREEMAN, BRIAN D

I have been re-installing ONAP via OOM’s cd.sh script a couple times to test 
patches.

Turns out the jump server (VNC ) on a re-install loses all the data as 
expected. Its a bit of a pain.

Would it be feasible to preserve that container as an option on a re-install 
via cd.sh or put its file system into the dockerdata-nfs (preserving things 
like apt-get install vim, apt-get install wget , wget postman (and the 
collections for ONAP REST API calls), apt-get install libgconf-2-4,, etc)  ?

Either method would work for me but seems like not  deleteing vnc as an option 
might be the easiest ?

Brian

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [sdc] Error in SDC on dependency validation in ONAP R1

2018-01-11 Thread Vitaliy Emporopulo

Hello,

We couldn’t reproduce the problem in our environments. Would it be possible for 
you to send us the HEAT files + CSAR after you’ve added the dependency?

Also, just to make sure if you’re running with the latest build of R1.

Regards,
Vitaliy Emporopulo
Software Architect @ Amdocs

From: onap-discuss-boun...@lists.onap.org 
[mailto:onap-discuss-boun...@lists.onap.org] On Behalf Of Kumar Skand Priya, 
Viswanath V via onap-discuss
Sent: Wednesday, January 10, 2018 12:01
To:
Subject: [onap-discuss] [sdc] Error in SDC on dependency validation in ONAP R1

Dear SDC Team,

We found an error while using dependency attribute in SDC of ONAP R1

While creating a VSP, we added a dependency between 2 components as below:

[cid:image002.jpg@01D38B0D.84246610]
Things look good until VSP level. Now when we tried to promote a VSP to VF 
using "Import VSP" option in SDC, we are hit with following error:

[cid:image004.jpg@01D38B0D.84246610]
If we remove the dependency in VSP and re-promote to VF, then it pass through 
successfully.
Is this is a gap in SDC or are we doing a mistake in configuration? Kindly 
clarify...

BR,
Viswa


[Image removed by sender.]

Viswanath Kumar Skand Priya
Architect
Verizon Network Ops & Eng

This message and the information contained herein is proprietary and 
confidential and subject to the Amdocs policy statement,

you may review at https://www.amdocs.com/about/email-disclaimer 

___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [uui] UUI intermittently failing in Amsterdam MR

2018-01-11 Thread Gary Wu

Hi UUI team,

The UUI component seems to intermittently fail to pass health check in the 
Amsterdam maintenance release.  Can you take a look?

You can use the SB-04 environment to debug the issue.

Thanks,
Gary


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

[onap-discuss] [dcae] DCAE failing in Amsterdam MR

2018-01-11 Thread Gary Wu

Hi DCAE team,

Since last night the Amsterdam MR has been failing to spin up DCAE components.  
Can you take a look?

You can use the SB-05 environment to debug the issue.

Thanks,
Gary


___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] 答复: RE: [clamp] Questions about https://jira.onap.org/browse/CLAMP-80

2018-01-11 Thread Ngueko, Gervais-Martial

Hi,

The tosca parser is not yet available in R2 code.

Br,
Martial

From: yuan@zte.com.cn [mailto:yuan@zte.com.cn]
Sent: jeudi 11 janvier 2018 02:40
To: Ngueko, Gervais-Martial 
Cc: onap-discuss@lists.onap.org
Subject: 答复: RE: [onap-discuss] 答复: RE: [clamp] Questions about 
https://jira.onap.org/browse/CLAMP-80

Hi Martial,

Is the tosca parser available in the R2 release?

Best Regards,

Yuan Hu

原始邮件
发件人： >;
收件人：袁虎10090474;
抄送人： >;
日 期 ：2018年01月10日 17:37
主 题 ：RE: [onap-discuss] 答复: RE: [clamp] Questions about 
https://jira.onap.org/browse/CLAMP-80
The tosca parser is a future development target, so all the details (inputs are 
not yet defined). The tosca parser has not been developed yet .

From: yuan@zte.com.cn 
[mailto:yuan@zte.com.cn]
Sent: mercredi 10 janvier 2018 03:37
To: Ngueko, Gervais-Martial >
Cc: Ngueko, Gervais-Martial >; 
onap-discuss@lists.onap.org
Subject: RE: [onap-discuss] 答复: RE: [clamp] Questions about 
https://jira.onap.org/browse/CLAMP-80

Addtion question, what's the inputs of the Tosca Parser in Clamp, is it a Tosca 
CSAR package?

原始邮件
发件人：袁虎10090474
收件人： >;
抄送人： >;
日 期 ：2018年01月10日 10:25
主 题 ：[onap-discuss] 答复: RE: [clamp] Questions about 
https://jira.onap.org/browse/CLAMP-80
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Hi Martial,

What's the data format of a mS transmitted  between SDC and CLAMP?

What's the sequence flow between the  SDC/DCAE-DS, Parser and CLAMP? Did the 
CLAMP download the TOSCA CSAR package of the mS from SDC/DCAE-DS to local 
first, and then decode the package to obtain  the properties/parameters of the 
mS?

Best Regards,

Yuan Hu

发件人： >;
收件人：袁虎10090474; >;
抄送人： >; 
>;
日 期 ：2018年01月09日 23:59
主 题 ：RE: [clamp] Questions about 
https://jira.onap.org/browse/CLAMP-80
Hello Yuan,

The goal of the Tosca parser in CLAMP would be to decode the transmitted 
properties of a micro-service  between SDC and CLAMP.
The Tosca model would contain the description of properties/parameters of a mS 
designed in SDC/DCAE-DS  ( and would be sent by DCAE-DS/SDC to CLAMP), but this 
 is still to be confirmed, normally this week, with the DCAE-DS/SDC team.

Br,
Martial

From: yuan@zte.com.cn 
[mailto:yuan@zte.com.cn]
Sent: mardi 9 janvier 2018 02:44
To: Lefevre, Catherine >; 
Ngueko, Gervais-Martial >
Cc: onap-discuss@lists.onap.org
Subject: [clamp] Questions about 
https://jira.onap.org/browse/CLAMP-80

Hi Martial and Catherine,

I see there has a issue for TOSCA Model Parser in Clamp, see

Re: [onap-discuss] OOM Installation Problem | Unable to bring up Portal Pod

2018-01-11 Thread Karthik

Hi Mandeep, Alexis, Michael, Viswa ,

Thanks a lot for your quick responses and suggestions.

As Michael suggested that RAM should be more than 55 G, so I increased it
to 128G.
After increasing RAM size , I am able to install ONAP using OOM. Thanks!

Regards,
Karthik.

On 11 Jan 2018 03:42, "Mandeep Khinda"  wrote:

> Hi Karthik,
>
> Can you share some more output from your k8s cluster (in a text format if
> possible)
>
>
>
> kubectl -n onap-portal get events|grep portalapps
>
>
>
> This will show the events that took place and hopefully the reason why it
> is stuck at initializing.  In my experience it is usually image pulling
> issues and/or k8s cluster resource limits are maxed out.
>
>
>
>
>
> *Mandeep Khinda*
>
> Software Development
>
> *Open Network Division*
>
>
>
> +1.613.595.5132 (office)
>
>
>
> [image: ocs-a]
>
>
>
> Read the latest on Amdocs.com  and the Amdocs
> blog network  – and follow us on Facebook
> , Twitter ,
> LinkedIn  and YouTube
> .
>
>
>
>
>
> *From: * on behalf of Karthik <
> sdkarth...@gmail.com>
> *Date: *Tuesday, January 9, 2018 at 10:18 AM
> *To: *"onap-discuss@lists.onap.org" 
> *Subject: *[onap-discuss] OOM Installation Problem | Unable to bring up
> Portal Pod
>
>
>
>
>
> Hi Team , Good day !
>
>
>
> I followed the Quick Installation
> 
>  steps
> to install ONAP.  All pods are up and running except "*Portal*".I tried
> multiple times to bring up  "Portal" pod , but  could not able to solve the
> problem . "portalapps", "vnc-portal" are keep on hangs with
> *Waiting:PodInitializing* status. I have attached the log and status
> images . Please refer it and reply to me if you could help me in this
> problem.
>
> Environment Details:
>
> Ubuntu 16, RAM 50 GB.
>
>
>
> Thanks in Advance.
>
>
>
> Regards,
>
> Karthik.
>
>
> This message and the information contained herein is proprietary and
> confidential and subject to the Amdocs policy statement,
> you may review at https://www.amdocs.com/about/email-disclaimer
>
___
onap-discuss mailing list
onap-discuss@lists.onap.org
https://lists.onap.org/mailman/listinfo/onap-discuss

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

Re: [onap-discuss] [E] RE: [sdc] Error in SDC on dependency validation in ONAP R1

Re: [onap-discuss] [E] [oom] OOM Installation Problem | Unable to bring up Portal Pod

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

[onap-discuss] VNF SDK 01-12-2018 Meeting - Developer Wiki - Confluence

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

Re: [onap-discuss] [onap-tsc] Committer Promotion Request for [appc]

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

[onap-discuss] MUSIC Proposal for Beijing

[onap-discuss] Committer Promotion Request for [appc]

Re: [onap-discuss] OOM Option to preserve VNC Jump server ?

Re: [onap-discuss] OOM Robot Distribute

Re: [onap-discuss] OOM Robot Distribute

Re: [onap-discuss] OOM Robot Distribute

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Re: [onap-discuss] OOM Robot Distribute

Re: [onap-discuss] [dcae] DCAE failing in Amsterdam MR

Re: [onap-discuss] OOM Robot Distribute

Re: [onap-discuss] OOM Robot Distribute

[onap-discuss] OOM Robot Distribute

Re: [onap-discuss] clarification question on ONPA R2 resilience requirement

[onap-discuss] [integration] RE: Jenkins CSIT requiring attention

[onap-discuss] Did You Know?

Re: [onap-discuss] [E] [oom] OOM Installation Problem | Unable to bring up Portal Pod

[onap-discuss] FW: HF2 Network Downtime Jan 12 2018

[onap-discuss] for sdc vnfd model , could a user-defined property be added in the node property for vdu, cpd, storage

[onap-discuss] OOM Option to preserve VNC Jump server ?

Re: [onap-discuss] [sdc] Error in SDC on dependency validation in ONAP R1

[onap-discuss] [uui] UUI intermittently failing in Amsterdam MR

[onap-discuss] [dcae] DCAE failing in Amsterdam MR

Re: [onap-discuss] 答复: RE: [clamp] Questions about https://jira.onap.org/browse/CLAMP-80

Re: [onap-discuss] OOM Installation Problem | Unable to bring up Portal Pod

33 matches

Site Navigation

Mail list logo

Footer information