Hi, guys,
I encountered a problems when I ran ONAP demo and wanted to access the ONAP
portal
Specifically, I can start up the ONAP instances and login the ONAP portal with
release-1.0.0(in .env file, gerrit_branch: release-1.0.0) on Titanium cloud
platform,
But when I started up ONAP instances
Borislav
Thanks for the quick response, let me try this one and let you know the
results.
Regards
Vivek
On Sun, Mar 4, 2018 at 9:42 PM, Borislav Glozman <
borislav.gloz...@amdocs.com> wrote:
> Hi Vivek,
>
>
>
> This is a known problem with SDC initialization in amsterdam.
>
> In order to
Hi all,
Welcome to join us for reviving the service modeling discussion thread this
week.
Here is the proposed meeting logistics:
Start Time: 8 am US eastern (9 pm Beijing) Tue, March 6
Length: 1 hour
Meeting room: https://zoom.us/j/9117271979
Based on the latest contributions
Hi All,
Has any faced this issue. Please let us know if there is any workaround for
the below issue.
Regards
Vivek
On Sun, Mar 4, 2018 at 7:06 PM, Vivekanandan Muthukrishnan <
vmuthukrish...@aarnanetworks.com> wrote:
> Hi All,
>
> It looks like we are not able to create the asset after VSP is
Michael,
Thanks for the quick response!
Answers inline.
> On Mar 4, 2018, at 8:19 PM, Michael O'Brien wrote:
>
> Joe,
> Hi, Mike here, I am curious as to the hardware you use - I would like to
> also test on some arm chips - the only arm chips I have access to in
Joe,
Hi, Mike here, I am curious as to the hardware you use - I would like to
also test on some arm chips - the only arm chips I have access to in the one in
my iphone and the cortex based on in the PI3
https://wiki.onap.org/display/DW/ONAP+on+ARM+Cortex-A53 - docker installs
there but I
Hello ONAP Enthusiasts,
I am currently working on the Auto project in OPNFV, and one of our goals is
to run ONAP on arm64 servers.
At this point, I’m following the installation process described by Michael
O’Brien in [1].
I currently have a 4-server k8s cluster (1 master and 3 nodes)
Hi Vivek,
This is a known problem with SDC initialization in amsterdam.
In order to overcome it, you should recreate SDC pods in the following order:
cs -> be -> fe.
Example, if my namespace is onap, I would:
# kubectl delete pod -n onap-sdc sdc-cs-fd787c9b6-nt6f2
Wait for another instance of
Hi All,
It looks like we are not able to create the asset after VSP is imported
into the catalog. Is this something to do with the *onap-vnfsdk
refrepo-1924147637-6qn48*
oom release branch = amsterdam
Can some one help us to resolve the below issue would be really great.
Regards
Vivek
*SDC