Hi,
deploy_vm2.sh uses plain docker pull. So modify deploy_vm1.sh, remove
:${DOCKER_IMAGE_VERSION} from pull and tag command. Hopefully it works for you.
Regards,
Ajay
From: Ajay Priyadarshi
Sent: 26 June 2017 11:33
To: 'Subhash Kumar Singh'; [email protected]
Subject: RE: aai-instances installation
Hello Subhash,
I think aai is still under migration. You can pull manually by removing tag.
Hopefully this error is temporary.
root@vm1-aai-inst1:/opt# docker login -u docker -p docker nexus3.onap.org:10001
Login Succeeded
root@vm1-aai-inst1:/opt#
root@vm1-aai-inst1:/opt#
root@vm1-aai-inst1:/opt# docker pull
nexus3.onap.org:10001/openecomp/aai-resources:1.0-STAGING-latest
Pulling repository nexus3.onap.org:10001/openecomp/aai-resources
Error: image openecomp/aai-resources:1.0-STAGING-latest not found
root@vm1-aai-inst1:/opt# docker pull
nexus3.onap.org:10001/openecomp/aai-resources:1.0-STAGING-latest
Pulling repository nexus3.onap.org:10001/openecomp/aai-resources
Error: image openecomp/aai-resources:1.0-STAGING-latest not found
root@vm1-aai-inst1:/opt# docker pull
nexus3.onap.org:10001/openecomp/aai-resources
Using default tag: latest
latest: Pulling from openecomp/aai-resources
3f992ab3df53: Already exists
0aa0bd28396f: Already exists
db7bb15088de: Already exists
1b6d2bb5ddaa: Already exists
a2bc8c956e6b: Already exists
6f6d9d811535: Pulling fs layer
3f70b3791b34: Waiting
db82441d2f6a: Waiting
93ed6b3de520: Waiting
a9acf7284af3: Waiting
0bdb05fbee76: Waiting
d52f80f2aa03: Waiting
1c912a3373bf: Waiting
I have in my system
root@vm1-aai-inst1:/opt# docker image list
REPOSITORY TAG
IMAGE ID CREATED SIZE
nexus3.onap.org:10001/openecomp/aai-traversal latest
4e96228772af 3 days ago 1.25GB
dockerfiles_kafka latest
50be9273ac2e 3 days ago 260MB
nexus3.onap.org:10001/openecomp/model-loader 1.0-STAGING-latest
a0a7a2118095 4 days ago 755MB
nexus3.onap.org:10001/openecomp/model-loader latest
a0a7a2118095 4 days ago 755MB
nexus3.onap.org:10001/openecomp/aai-resources latest
9396b157c6bb 4 days ago 1.25GB
attos/dmaap latest
b0ae220fcf1f 5 days ago 747MB
anapsix/alpine-java latest
87267d67585e 6 days ago 124MB
nexus3.onap.org:10001/openecomp/data-router latest
741a7e538959 2 weeks ago 726MB
nexus3.onap.org:10001/openecomp/search-data-service latest
c6654101d2b8 2 weeks ago 735MB
aaionap/haproxy latest
68fbcebd5251 3 weeks ago 139MB
wurstmeister/zookeeper latest
351aa00d2fe9 7 months ago 478MB
Regards,
Ajay Priyadarshi
From: Subhash Kumar Singh [mailto:[email protected]]
Sent: 23 June 2017 18:59
To: Ajay Priyadarshi;
[email protected]<mailto:[email protected]>
Subject: RE: aai-instances installation
Hello Ajay,
We are also facing the same issue. For a quick fix, we used master branch and
we got the `test-config` repository to execute the `aai2_vm_init.sh` script.
Now, we are seeing that docker tag `1.0-STAGING-latest` is not available.
Please find the following log:
root@onap-aai-inst1:/opt# ./aai2_vm_init.sh
Already up-to-date.
Login Succeeded
Pulling repository nexus3.onap.org:10001/openecomp/aai-resources
Error: image openecomp/aai-resources:1.0-STAGING-latest not found
Error response from daemon: No such image:
nexus3.onap.org:10001/openecomp/aai-resources:1.0-STAGING-latest
Pulling repository nexus3.onap.org:10001/openecomp/aai-traversal
Error: image openecomp/aai-traversal:1.0-STAGING-latest not found
Error response from daemon: No such image:
nexus3.onap.org:10001/openecomp/aai-traversal:1.0-STAGING-latest
Pulling repository nexus3.onap.org:10001/openecomp/search-data-service
Error: image openecomp/search-data-service:1.0-STAGING-latest not found
Error response from daemon: No such image:
nexus3.onap.org:10001/openecomp/search-data-service:1.0-STAGING-latest
Pulling repository nexus3.onap.org:10001/openecomp/datarouter-service
Error: image openecomp/datarouter-service:1.0-STAGING-latest not found
Error response from daemon: No such image:
nexus3.onap.org:10001/openecomp/datarouter-service:1.0-STAGING-latest
1.0-STAGING-latest: Pulling from openecomp/model-loader
Digest: sha256:52b05fa7af784a1537f80ad2e4a92f49ba94b109a3251fcf2e4476beb0fa4e75
Status: Image is up to date for
nexus3.onap.org:10001/openecomp/model-loader:1.0-STAGING-latest
Pulling repository nexus3.onap.org:10001/openecomp/sparky
Error: image openecomp/sparky:1.0-STAGING-latest not found
Error response from daemon: No such image:
nexus3.onap.org:10001/openecomp/sparky:1.0-STAGING-latest
--
Regards,
Subhash Kumar Singh
________________________________
From:
[email protected]<mailto:[email protected]>
[[email protected]] on behalf of
[email protected]<mailto:[email protected]>
[[email protected]]
Sent: Friday, June 23, 2017 10:58
To: [email protected]<mailto:[email protected]>
Subject: [onap-discuss] aai-instances installation
Hi,
Both aai-instances uses the install script which try to access the
"release-1.0.0 --single-branch http://gerrit.onap.org/r/aai/test-config";. While
this project "aai/test-config" is not added to branch release-1.0.0, Same can
be verified in attached snapshot. Kindly add same to release-1.0.0 branch. I
manually did it by master branch.
root@vm1-aai-inst1:/opt# git clone -b release-1.0.0 --single-branch
http://gerrit.onap.org/r/aai/test-config
Cloning into 'test-config'...
warning: Could not find remote branch release-1.0.0 to clone.
fatal: Remote branch release-1.0.0 not found in upstream origin
root@vm1-aai-inst1:/opt# Unexpected end of command stream
root@vm1-aai-inst1:/opt# git clone -b master --single-branch
http://gerrit.onap.org/r/aai/test-config
Cloning into 'test-config'...
remote: Total 127 (delta 0), reused 127 (delta 0)
Receiving objects: 100% (127/127), 94.82 KiB | 0 bytes/s, done.
Resolving deltas: 100% (45/45), done.
Checking connectivity... done.
[cid:[email protected]]
Regards,
Ajay Priyadarshi
"Confidentiality Warning: This message and any attachments are intended only
for the use of the intended recipient(s).
are confidential and may be privileged. If you are not the intended recipient.
you are hereby notified that any
review. re-transmission. conversion to hard copy. copying. circulation or other
use of this message and any attachments is
strictly prohibited. If you are not the intended recipient. please notify the
sender immediately by return email.
and delete this message and any attachments from your system.
Virus Warning: Although the company has taken reasonable precautions to ensure
no viruses are present in this email.
The company cannot accept responsibility for any loss or damage arising from
the use of this email or attachment."
_______________________________________________
onap-discuss mailing list
[email protected]
https://lists.onap.org/mailman/listinfo/onap-discuss
