I guess I'm confused by this. When we started talking about a POD configuration file, I thought we were basically creating a template by which we could easily and rapidly deploy new PODs. Why are we creating static files for what could be easily detected?
Sorry if this has already been hashed to death. I missed that conversation. Thanks, Ash On Fri, Nov 18, 2016 at 3:13 PM, Jack Morgan <jack.mor...@intel.com> wrote: > OPNFV... > > Thanks to all who provided feedback to the commits below. I've taken the > feedback we have received so far for the POD description file and > resubmitted the changes to gerrit. In addition, I've created a wiki page to > document additional information such as back ground, goals, etc that wasn't > able to make into the git commit. Feel free to update the wiki page as > well. > > https://wiki.opnfv.org/display/INF/POD+Descriptor > > On 10/27/2016 09:17 PM, Jack Morgan wrote: > > > > *Common configuration files *Each installer has its own strategy for > deploying OPNFV onto an OPNFV POD. There has been an effort to come up with > a common configuration file that all installers use for deployments for > more then 18 months. We came up with a proposal to define what should be > included in this file based on the current files that installers use. > Again, we need lots of feedback on our proposal (see gerrit commit below) > > https://gerrit.opnfv.org/gerrit/#/c/23727/ > > > Thanks, > > -- > Jack Morgan > OPNFV Pharos Intel Lab > > > _______________________________________________ > opnfv-tech-discuss mailing list > opnfv-tech-discuss@lists.opnfv.org > https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss > >
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
