Victor, Yeap. I am using windows machine and what I did for that is using Cygwin dos2unix plugin to bypass that which has been mentioned in the confluence in a similar way.
Link 1 is really awesome. It does mentioned some details of the change, especially, why install_sdnc is not invoked. I’m going to follow it and do again. Really thanks for the information. Best, Kevin From: Morales, Victor [mailto:[email protected]] Sent: Thursday, October 26, 2017 1:59 PM To: Hao Kuang <[email protected]>; Gary Wu <[email protected]> Cc: [email protected] Subject: Re: [integration] RE: Question about wiki of ONAP-intergration Kevin, Are you using a windows machine? Idan has documented some changes that are needed for different encodings in the point 2.d [1], I suggest to change the settings of the IDE or editor to don’t change the encoding format. Regarding the docker-compose installation this is placed in */opt/docker/docker-compose* path thru the install_docker_compose function [2] Regards/Saludos Victor Morales [1] https://wiki.onap.org/pages/viewpage.action?pageId=15999821#UsingVagrant-OnapforlocaldeploymentofSDCproject-WIP!!!-InitialSetup [2] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib/functions#n193 From: Hao Kuang <[email protected]<mailto:[email protected]>> Date: Thursday, October 26, 2017 at 10:35 AM To: Victor Morales <[email protected]<mailto:[email protected]>>, Gary Wu <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>> Subject: RE: [integration] RE: Question about wiki of ONAP-intergration Hi Victor, Thanks for the reply. Basically I ran the $ ./tools/run.sh sdnc first, otherwise I cannot get vagrant vm running. One issue is that some of the scripts are ending with “\r” which might need to be updated in ONAP ☺ Link 2 is very helpful. It does use docker compose to up the docker images as what APPC has. But I didn’t find docker-compose in the running vm. It might be the reason that I didn’t do vagrant reload after changing the settings.yaml.development. Thanks for the help and confirm. I’m going to give a try again. Best, Kevin From: Morales, Victor [mailto:[email protected]] Sent: Thursday, October 26, 2017 12:01 PM To: Hao Kuang <[email protected]<mailto:[email protected]>>; Gary Wu <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]> Subject: Re: [integration] RE: Question about wiki of ONAP-intergration Hey Kevin, Maybe we should describe better the way of how to use it but here [1] is more information. The configuration values that you used are fine, basically you are compiling all the SDNC repos (which it’s optional for the creation of images) and build and start the SDNC images from source code instead of pulling them from *nexus3.onap.org* hub. And you have the right assumption that using the testing execution is not providing a development environment, this is used to validate the functions of the scripts, so in order to provide a SDNC development environment you have to run the following bash command: $ ./tools/run.sh sdnc or the powershell version: PS C:\> .\tools\Run.ps1 sdnc Those commands are going to create a virtual machine (in their respective OS) and will execute the corresponding provisioning script, in this case SDNC [2]. Regards/Saludos Victor Morales irc: electrocucaracha [1] http://onap.readthedocs.io/en/latest/submodules/integration.git/bootstrap/vagrant-onap/doc/source/features/configure_execution.html [2] https://git.onap.org/integration/tree/bootstrap/vagrant-onap/lib/sdnc From: Hao Kuang <[email protected]<mailto:[email protected]>> Date: Wednesday, October 25, 2017 at 4:44 PM To: Gary Wu <[email protected]<mailto:[email protected]>> Cc: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>, Victor Morales <[email protected]<mailto:[email protected]>> Subject: RE: [integration] RE: Question about wiki of ONAP-intergration Hi Gary, Thanks for your quick reply. I will check the link you mentioned. From: Gary Wu [mailto:[email protected]] Sent: Wednesday, October 25, 2017 7:33 PM To: Hao Kuang <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; MORALES RUVALCABA, VICTOR <[email protected]<mailto:[email protected]>> Subject: [integration] RE: Question about wiki of ONAP-intergration Hi Kevin, On #1, that URL in the README was incorrect; it should be https://wiki.onap.org/display/DW/Integration+Project. I’ve fixed it now. On #2 and #3 I assume you’re talking about onap-vagrant? Victor (cc:’ed) can probably better answer those questions for you. Thanks, Gary From: Hao Kuang [mailto:[email protected]] Sent: Wednesday, October 25, 2017 4:23 PM To: Gary Wu <[email protected]<mailto:[email protected]>> Subject: Question about wiki of ONAP-intergration Hi Gary, I am Kevin from Amdocs who just start working on SDNC project for ATT. I am not sure if it’s appropriate to contact with you directly or not. But I do have some dummy questions about ONAP-integration. (1) The link https://wiki.open-o.org/view/Integration mentioned in README of root folder does not exist. a. I am wondering where I can get the discussion board, wiki or any related link. (2) May be because of lack of information, I checked most of README files under the project and finally I can get a running sdnc system. a. The problem I have is that I would like to start all the sdnc docker images after finishing running the script. b. The setting file of development is like below, but finally those docker instances are not started, but those docker images are generated. build_images: "True" compile_repo: "True" skip_get_images: "False" skip_install: "False" c. I guess is that because I have to use testing mode? (3) Could we start multiple components instead of ALL-In-ONE. Best Regards, Hao (Kevin) Kuang Software Developer APP-C 613-595-5266 (office) 613-252-4781 (mobile) [docs-2017-brand-mark-rgb] Did you know…? Every day is a good day! Read the latest on Amdocs.com<http://www.amdocs.com/> and the Amdocs blog network<http://blogs.amdocs.com/> – and follow us on Facebook<http://www.facebook.com/Amdocs>, Twitter<http://twitter.com/Amdocs>, LinkedIn<http://www.linkedin.com/company/amdocs> and YouTube<http://www.youtube.com/amdocs>. 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 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
