Is there anyone on the FUEL team monitoring this list? Really, we cannot make progress in Danube on Fuel support unless we get some basic support on the issues we have with standing up a Fuel-based deploy for testing.
Thanks, Bryan Sullivan | AT&T From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of SULLIVAN, BRYAN L Sent: Thursday, January 19, 2017 2:44 PM To: Michael Polenchuk <mpolenc...@mirantis.com> Cc: opnfv-tech-discuss@lists.opnfv.org Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs? Resending, as I have not yet see a clarification of the fields in the dea-pod-override.yaml and dha.yaml files. I need this in order to setup our PODs to test under Fuel for the Copper, Models, and VES project. Thanks, Bryan Sullivan | AT&T From: SULLIVAN, BRYAN L Sent: Thursday, January 12, 2017 6:13 AM To: 'Michael Polenchuk' <mpolenc...@mirantis.com<mailto:mpolenc...@mirantis.com>> Cc: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: RE: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs? Hi Michael, We figured out that much after actually looking at the README file, but the details of the dea-pod-override.yaml and dha.yaml files are unclear, i.e. how they should be setup for a specific POD, what are the options and values, what’s mandatory/optional, etc. In the repo, it looks like they refer to virtual envs, but after looking at the “secret” lab config versions it’s not much clearer. There are dozens of fields, subnet specs, etc and it’s unclear what they all related to. Where is the spec for all that? Thanks, Bryan Sullivan | AT&T From: Michael Polenchuk [mailto:mpolenc...@mirantis.com] Sent: Wednesday, January 11, 2017 11:35 PM To: SULLIVAN, BRYAN L <bs3...@att.com<mailto:bs3...@att.com>> Cc: opnfv-tech-discuss@lists.opnfv.org<mailto:opnfv-tech-discuss@lists.opnfv.org> Subject: Re: [opnfv-tech-discuss] [Fuel] Danube Status - ready to test in labs? On Wed, Jan 11, 2017 at 9:23 PM, SULLIVAN, BRYAN L <bs3...@att.com<mailto:bs3...@att.com>> wrote: Thanks for the help here and on IRC – much appreciated. One other question as asked on IRC: The deploy.sh script requires a "-b base-uri" parameter which is the "stack-configuration" location. But there is no spec of what needs to be at that location/resource (I’m assuming this is an input, not output) - at least I can't find it. Any guidance? Hi Bryan, "-b base-uri" parameter usually pointed to the config which resides in the repo, e.g.: # git clone https://gerrit.opnfv.org/gerrit/fuel /tmp/opnfv-fuel In this case -b should be set to file:///tmp/opnfv-fuel/deploy/config -s option is for a scenario name which is available in the repo as well (.../opnfv-fuel/deploy/scenario). -- Michael Polenchuk Private Cloud / Mirantis Inc.
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
