Re: [onap-discuss] [aai] Standalone AAI UI

2018-11-05 Thread Chandra
Hi Arul, Thanks for information. I am currently using the following and using Beijing installation. Its heat based installation. nexus3.onap.org:10001/onap/sparky-be 1.2.1 Where exactly I can locate this file ? Inside any specific docker ? I tried to search but could not get the

Re: [E][onap-discuss][AAI] AAI authentication without AAF

2018-11-05 Thread Gopigiri, Sirisha via Lists.Onap.Org
Thank you Pavel, that was very helpful. Best Regards Sirisha Gopigiri On Mon, Nov 5, 2018 at 12:21 PM Pavel Paroulek wrote: > Hi Sirisha, > > yes there is. In values.yaml in the AAI chart replace the word aaf-auth > with one-way-ssl as shown in this commit >

[onap-discuss] [SDC][Integration] Error during "Certify" operation

2018-11-05 Thread Krzysztof Kuźmicki
Hi Today we were able to install locally whole Casablanca staging version including Brian's work around regarding failing message router :). However during PNF creation in SDC as Carlos Santana user during certify operation following error has appear: Error Error code: SVC4661 Status code:

Re: [onap-discuss] [aai] Standalone AAI UI

2018-11-05 Thread Arul Nambi
Hey Chandra, Sorry unfortunately we were in the middle of configuration changes in Beijing and there is no way to disable portal in Beijing. Can you move to master/Casablanca? It is stable at this point in time. Regards Arul From: Chandrashekhar Thakare [mailto:ct00548...@techmahindra.com]

Re: [onap-discuss] [dmaap] DMaaP is Not Reachable in Integration-OOM-Staging-Daily

2018-11-05 Thread UNNAVA, SUNIL
Hi, The issue is fixed now and the new image is released. Thanks, Sunil From: onap-discuss@lists.onap.org On Behalf Of FREEMAN, BRIAN D Sent: Saturday, November 03, 2018 9:47 AM To: 'onap-discuss@lists.onap.org' ; 'fu.guangr...@zte.com.cn' Subject: Re: [onap-discuss] [dmaap] DMaaP is Not

[onap-discuss] Who is using SB-01?

2018-11-05 Thread Gary Wu
Hi all, Who is using the ONAP instance in Wind River Integration-SB-01? Please remember to check with the Integration team before using any of the Integration tenants listed here: https://wiki.onap.org/display/DW/Integration+Test+Labs, and to add yourself as a contact for a tenant once you've

[onap-discuss] No LOG meeting Tue - prep for RC2, sick and Corp meet #log

2018-11-05 Thread Michael O'Brien
Team, No logging meet this week on Tue, I doing work for RC2, I can't talk too much (first time sick in 2 years) and there is a Corp meet at the same time. Thank you /michael “Amdocs’ email platform is based on a third-party, worldwide, cloud-based system. Any emails sent to Amdocs will

[onap-discuss] Request to review patch for INT-551: Optimizing OOF-HAS container image

2018-11-05 Thread Adolfo Perez-Duran
Dear OOF team, As part of the CIA Project work we talked about before, I have submitted a patch to optimize the HAS container image: https://gerrit.onap.org/r/#/c/71841/ The new image is 70% smaller and it is cpu architecture-agnostic. Will you please review and approve the patch? Thanks,

[onap-discuss] Please delete unused VMs in Wind River

2018-11-05 Thread Gary Wu
Hi all, We are running out of resources in Wind River lab. If you have any VMs or ONAP instances in Wind River that you're not currently using, can you please terminate them? Thanks, Gary -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online

[onap-discuss] Event: #aai Dev Meeting #cal-invite

2018-11-05 Thread onap-discuss@lists.onap.org Calendar
BEGIN:VCALENDAR VERSION:2.0 PRODID:-//Groups.io Inc//ONAP Calendar//EN METHOD:PUBLISH CALSCALE:GREGORIAN BEGIN:VEVENT UID:calendar.11...@lists.onap.org DTSTAMP:20181105T223322Z ORGANIZER;CN=onap-discuss@lists.onap.org Group:mailto:onap-discuss@lists.onap.org DTSTART:20181108T13Z

[onap-discuss] Invitation: added [coe] Weekly (updated nov 5, 2018) @ Weekly from 1pm to 2pm on Tuesday (PST) (onap-discuss@lists.onap.org)

2018-11-05 Thread Kenny Paul
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02

[onap-discuss] Invitation: [usecasesub] Change Management Weekly Meeting @ Weekly from 6am to 7am on Wednesday (PST) (onap-discuss@lists.onap.org)

2018-11-05 Thread Kenny Paul
BEGIN:VCALENDAR PRODID:-//Google Inc//Google Calendar 70.9054//EN VERSION:2.0 CALSCALE:GREGORIAN METHOD:REQUEST BEGIN:VTIMEZONE TZID:America/Los_Angeles X-LIC-LOCATION:America/Los_Angeles BEGIN:DAYLIGHT TZOFFSETFROM:-0800 TZOFFSETTO:-0700 TZNAME:PDT DTSTART:19700308T02

Re: [onap-discuss] [SDC][Integration] Error during "Certify" operation

2018-11-05 Thread Michael Lando
Hi, I believe the error you are getting is because the job that needs to update our db did not run as it has already run once (Cassandra init) You can delete the k8s job and restart sdc and it should be fine. >From the portal perspective portal moved to use https and as sdc did not the

[onap-discuss] Running ONAP with dummy openstack

2018-11-05 Thread Syed Atif Husain
Can we run the robot script demo-k8s.sh, to create demo customer, with a dummy openstack? Or is working openstack mandatory? I have installed onap but openstack is not setup as we intend to use a third party VNFM. When I run the script ./demo-k8s.sh init - it fails due to connection timeout

Re: [E][onap-discuss][integration][AAF] Error while Integration with AAF in OOM deployment

2018-11-05 Thread Gopigiri, Sirisha via Lists.Onap.Org
Hi Jonathan, Thank you for the reply! Earlier it was 2.1.6-SNAPSHOT, but with the latest OOM changes I am able to deploy AAF 2.1.7-SNAPSHOT. But still the cassandra pod logs shows the same error. Is there any other configuration required? Best Regards Sirisha Gopigiri On Mon, Nov 5, 2018 at

[onap-discuss] [integration] Poll Results for Integration Weekly Meeting Time

2018-11-05 Thread Helen Chen
Thank you for participating the poll. Here’re the results: We have 6 votes in favor of Wednesday 6:00AM – 8:00AM PDT, and 3 votes in favor of Wednesday 7:00AM-9:00AM. So, we will move Integration Weekly meeting to 6:00AM – 8:00AM PDT. (No change for people located no daylight saving area).