Hello Todd. This is a long standing discussion and was something that GENESIS has an action to solve within OPNFV _ not really from PHAROS>
The have been well established specifications for what we call a lab, how the networks and network cards are named. Where and when we want to draw the line. As well, all lab configurations can be stored securely in securedlab repo – since certain lab owners don’t want to have their GW and Infrastructure information out in the open public. Further to that end, there are many examples of common files to be ready (DHA/DEA) is one of them. Its really unclear to me what we are trying to “validate’ in the case of the validator. Are we trying to check that a lab “meets” a specification? If this is the case, then I would say we need to take a step back, since as of Colarado, I have seen now 6 different HW topologies being used depending on the feature and the installer being used. So if we are going to “validate”, I would suggest that you get some consensus from the installers about how to approach this prior to trying to come up with a Validation solution (since validation implies that we have a rule to follow – and as we have seen, this “specification” that provided commonality in A and B release has been dropped (along with the whole of GENESIS not participating in C-release). My thoughts.. hope that helps, but I really would think that some establishment and agreement on the common foundations of how to approach a validation of a lab task is needed otherwise I do think we have a solid base for comparison. Cheers, D From: opnfv-tech-discuss-boun...@lists.opnfv.org [mailto:opnfv-tech-discuss-boun...@lists.opnfv.org] On Behalf Of Todd Gaunt Sent: Tuesday, August 23, 2016 9:41 AM To: opnfv-tech-discuss@lists.opnfv.org; Jack Morgan <jack.mor...@intel.com>; Lincoln Lavoie <lylav...@iol.unh.edu> Subject: [opnfv-tech-discuss] Common configuration files Hello, I want to open up a discussion on the pod configuration files regarding the inventory and network configuration files as described here https://wiki.opnfv.org/display/genesis/Configuration-files-discussion. As I'm working on the Pharos validation tool, getting a common configuration file, at least a baseline common format that can be made alongside installer configuration files, would help pod owners to support every installer and allow tools like the Pharos validation tool I'm working on to work in every deployment scenario without having custom configuration to support every possible configuration and installer. This would be preferable to me making yet another configuration file for my tool. I'd like to know from the developers of the installers what it might take to use these common configuration formats. Along with this what is needed to finalize the network configuration file here: https://wiki.opnfv.org/display/genesis/Common+Network+Settings. This configuration file is almost perfect aside from how it specifies NICs with the names the OS gives them (eth0, eth1) rather something more deterministic is such as the MAC addresses. Thanks, Todd Gaunt
_______________________________________________ opnfv-tech-discuss mailing list opnfv-tech-discuss@lists.opnfv.org https://lists.opnfv.org/mailman/listinfo/opnfv-tech-discuss
