Good day, definitely missing the Portal-apps VM! Please choose a Heat template that deploys the just-released Amsterdam release of Portal, which is version 1.3.0, instead of the (much older) 1.1.0. Hope this helps.
> On Nov 22, 2017, at 8:52 AM, Muhammad Ali <a...@strategicalli.com> wrote: > > Hi, > > I’ve started deploying ONAP using the following Heat template. > > https://nexus.onap.org/content/sites/raw/org.openecomp.demo/heat/OpenECOMP/1.1.0-SNAPSHOT/onap_openstack.yaml > > Stack creation was successful in Openstack. VMs and networks are up running. > > However, Portal VM was not configured correctly, below is the output of > “docker ps -a” from portal VM. > > root@vm1-portal:/opt# docker ps -a > CONTAINER ID IMAGE COMMAND CREATED > STATUS PORTS NAMES > a07f1099790d mariadb "docker-entrypoint..." 2 hours ago > Created data_vol_portal > > Is this the correct output? I’m wondering if there should be more active > containers of ecomp portal and its components. > > Below are my findings, when manually executed the portal_install.sh file. > > <…> > docker stop/waiting > docker start/running, process 20839 > Cloning into 'portal'... > remote: Finding sources: 100% (6754/6754) > remote: Total 6754 (delta 2747), reused 6754 (delta 2747) > Receiving objects: 100% (6754/6754), 16.28 MiB | 3.46 MiB/s, done. > Resolving deltas: 100% (2747/2747), done. > Checking connectivity... done. > Already up-to-date. > chmod: cannot access ‘portal/deliveries/new_start.sh’: No such file or > directory > chmod: cannot access ‘portal/deliveries/new_stop.sh’: No such file or > directory > chmod: cannot access ‘portal/deliveries/dbstart.sh’: No such file or directory > unzip: cannot find or open portal/deliveries/etc.zip, > portal/deliveries/etc.zip. > Login Succeeded > 1.1-STAGING-latest: Pulling from openecomp/portaldb > 4a441ce0e165: Pull complete > a1ddcbe73394: Pull complete > <…snipped…> > Status: Downloaded newer image for mariadb:latest > a07f1099790d8b19db7906b7bd337459d4b0676c08b9515fe6d0d3ba7872ff19 > Error response from daemon: No such container: ecompdb_portal > Error response from daemon: No such container: 1610-1 > Error response from daemon: No such container: widget-ms:latest > ./portal_vm_init.sh: line 35: ./dbstart.sh: No such file or directory > ./portal_vm_init.sh: line 36: ./new_start.sh: No such file or directory > ./portal_vm_init.sh: line 37: ./widget_ms_start.sh: No such file or directory > > And script hangs there. > > Below is my heat env file. > > nexus_repo: https://nexus.onap.org/content/sites/raw > nexus_docker_repo: nexus3.onap.org:10001 > nexus_username: docker > nexus_password: docker > dmaap_topic: AUTO > artifacts_version: 1.1.0-SNAPSHOT > docker_version: 1.1-STAGING-latest > gerrit_branch: master > openstack_tenant_id: admin > openstack_username: admin > cloud_env: openstack > > Seems like, it is missing some *start.sh scripts from the repo. > > Can you please point me to the correct upstream repo? Also, kindly review the > my env config, if there is something that I need to modify/update. > > Any help will be appreciated in this regard. > > Thanks > Muhammad Ali > _______________________________________________ > onap-discuss mailing list > onap-discuss@lists.onap.org > https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.onap.org_mailman_listinfo_onap-2Ddiscuss&d=DwICAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=IZdJcfOS7YWo6UY200A3VVFzja_rCk3u0gLN62mqPOk&m=sacvlwYW47YjlXiDSJKZwC2JE28RYdBYgpQMwGXFjmQ&s=Qf6h0Fsjsf2VseXfAJ28K64pYlu6m3WATmhKeZcPOgU&e= _______________________________________________ onap-discuss mailing list onap-discuss@lists.onap.org https://lists.onap.org/mailman/listinfo/onap-discuss
