Ran,
Thank you for the ONAP status initiative - we definitely need deployment
status as we stabilize 1.1. Ideally we would tag sanity tested builds.
I would like to collaborate with whatever artifacts/jobs you are running to
generate/consolidate the issues - as we have a very high vested interest in
having ONAP running.
Before 20170812 the AAI schema 11 issue caused is a bit of an issue - since
then we have started looking into running a daily deployment job - likely
running K8S that would launch all the containers and do some minimal rest calls
between them. It would be good if we could collaborate on this in the
Integration project. In the past we would raise jiras directly in the
components.
We have periodically reverted to 1.0 for because it was the only branch that
would function or go all the way to vFirewall closed-loop - except lately
docker image issues are also breaking 1.0 - currently AAI does not come up
properly. We definitely need to work in 1.1/master though.
So in summary - I think it would be good to coordinate reporting of issues
to your group/this-list as we bring up some infrastructure to verify ONAP daily.
/michael
From: [email protected]
[mailto:[email protected]] On Behalf Of Ran Pollak
Sent: Tuesday, August 22, 2017 05:48
To: [email protected]
Cc: [email protected]
Subject: [onap-discuss] FW: Stabilized the ONAP master branch
Thanks Gaurav!
We attend to have a different format for the daily mail that will include all
the Components with the relevant issues, so we will have DCAE as well.
Also if you can send me the relevant info regarding DCAE issues that will be
very helpful !
BR,
Ran Pollak
From:
[email protected]<mailto:[email protected]>
[mailto:[email protected]] On Behalf Of Gaurav Gupta (c)
Sent: Tuesday, August 22, 2017 06:35
To: Ran Pollak <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Subject: Re: [onap-discuss] Stabilized the ONAP master branch
Hi Ran Pollak
amazing intiative . May I request you to include DACE Init issues also in your
list of items to be resolved . Do let me know if you need any specifics of the
issues .
with best regards
Gaurav
________________________________
From:
[email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>>
on behalf of Ran Pollak <[email protected]<mailto:[email protected]>>
Sent: 21 August 2017 21:34
To: [email protected]<mailto:[email protected]>
Subject: [onap-discuss] Stabilized the ONAP master branch
Hello ONAP Community Members,
This is the first Daily status for the ONAP community regarding the status of
the Master branch, this format will change into all the ONAP components with
their issues/Status and we will add also info regarding "health-check"
scenarios.
Part of our efforts to stabilize the 1.1 ONAP and certify Open loop, we are
troubleshooting the issues and below is the issue we are now stuck at. We need
more help on this since this is reported as high and still in Open state.
Bug
Module
Issue
State
Defect Aging
Resolution
-
AAI
Unable to deploy model loader docker in AAI
Closed
NA
Update the port numbers and restart the dockers
-
SO
Unable to connect to AAI due to SSL
Closed
NA
1. Comment the certificate part in java.security file resides in
/etc/java-8-openjdk/security
2. Update mso.asdc.json located in /etc/mso/config.d path.
AAI-190<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_AAI-2D190&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=1OWfF7oUOY6tjenngZvE99gKYQYaGXwvFd0fd90XvxA&s=xj7XvnhCWnAzA1S8XZDhhZ5yA4XBFypyiptNHJNwkMk&e=>
AAI
AAI was not able to communicate with ASDC
Closed
NA
Stop and remove the old dockers, place new dockers and update the java.security
file like above.
VID-38<https://urldefense.proofpoint.com/v2/url?u=https-3A__jira.onap.org_browse_VID-2D38&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=1OWfF7oUOY6tjenngZvE99gKYQYaGXwvFd0fd90XvxA&s=zkpfZpxYEtyVOV3qcSUdyZjVLTaBiIMIXGU135karQc&e=>
VID
Deploy button is not working in VID to distribute Model
Open
10 days
We have this issue reported and been followed up for more than ten days yet no
update. Posted on community as well.
Please, if you have something to add or ask please contact me.
BR,
Ran Pollak
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<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.amdocs.com_about_email-2Ddisclaimer&d=DwMFAg&c=uilaK90D4TOVoH58JNXRgQ&r=ebJjFMpXijqZjbZCcbF7yJIq2ES6jM0Q-DEcP-qjjeI&m=1OWfF7oUOY6tjenngZvE99gKYQYaGXwvFd0fd90XvxA&s=9Ry6rgG1kK3uvv1a91PhMJNA7tZB3XqFLWFBzf7E7c8&e=>
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
<https://www.amdocs.com/about/email-disclaimer>
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
