A script like this exists for Apex today: https://github.com/opnfv/apex/blob/stable/danube/contrib/simple_deploy.sh
Thanks to Nikolas for contributing it. Tim Rozet Red Hat SDN Team ----- Original Message ----- From: "Luke Hinds" <[email protected]> To: "liangqi (D)" <[email protected]> Cc: "bryan sullivan" <[email protected]>, [email protected], "narinder gupta" <[email protected]> Sent: Thursday, June 29, 2017 6:32:21 AM Subject: Re: [opnfv-tech-discuss] [Infra][Pharos][Releng][Octopus] Proposal to implement installers' quickstart wrapper scripts Hi, Don't want to detract from the topic, but please do not use curl | bash, its dangerous and if opnfv.org is every compromised, scripts like this could be used to back door all the PODS and test sites deployed by end users. If deploying a system this way, then use a checksum (with sha256 or stronger) to first to insure the script has not been tampered with (I have examples if some are needed). Cheers, Luke On Thu, Jun 29, 2017 at 10:54 AM, liangqi (D) < [email protected] > wrote: Hi, In OPNFV we have 4 installers in Danube release, we will have more in the next release. Each of them supports multiple scenarios and has different install user steps. This is quite confusing and difficult to use, especially for the newbies. In releng we already have scripts to trigger all installers' deploy and test, but the scripts are CI oriented, not user oriented. So I proposal to implement wrapper scripts in releng to provide easy way for people to try opnfv. With minimum requirement(a server with Ubuntu 14.04/16.04 or CentOS7 installed and with internet connectivity), without checking detail installers' install guide, just run one command you will get your environment ready. The simplest way to install opnfv environment will be like: `curl https://get.opnfv.org/ephrates/quickstart.sh | bash`. For each installer we may have one command deploy like: `curl https://get.opnfv.org/ephrates/compass/quickstart.sh | bash` Basic virtual deploy workflows: 1. Run command (e.g. `curl https://get.opnfv.org/ephrates/quickstart.sh | bash`) 2. Check environment 3. Fetch supported installers and select one installer 4. Generate the deploy command and execute 5. Verify the deployed environment 6. Deploy success For BareMetal deployment the workflow are almost the same, the only different is you need prepare physical servers/switches, connect the cables, setup the switches, create a pod-descriptor file, and run the deploy command with the pod-descriptor file. The attached slide illustrate the initial idea, which was shared by Justin at the OPNFV Summit in Beijing. Here is the initial script patch: https://gerrit.opnfv.org/gerrit/#/c/36711/ @Uli, I saw you've sent the latest infra working group meeting agenda in the mailing list. Could you please include the topic to the infra working group meeting agenda. Welcome feedback, comments, discuss here or at the infra working group meeting. Best Regards, Qi Liang _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss -- Luke Hinds | NFV Partner Engineering | Office of Technology | Red Hat e: [email protected] | irc: lhinds @freenode | m: +44 77 45 63 98 84 | t: +44 12 52 36 2483 _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss _______________________________________________ opnfv-tech-discuss mailing list [email protected] https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
