From 01686867da5d35dc5fb555d4936a1448aa19a52e Mon Sep 17 00:00:00 2001 From: Jonas Bjurel Date: Sun, 6 Dec 2015 20:47:08 +0100 Subject: Proposal for common OPNFV CI/CD Configuration structure This patch provides a common configuration structure, providing separation of concern between: 1) Base installer configuration 2) Per Lab/POD specific configuration 3) Per installer feature/plugin configuration 4) Deployment scenario configuration. It is not yet aligned across installers - but provides a structure for future alignment. It relates to the implementation provided here: https://gerrit.opnfv.org/gerrit/#/c/3995/ Also see the README file VERIFIED READY TO MERGE JIRA: Change-Id: I852376ba4b500cc50cba6cb3c2634533fc6426a6 Signed-off-by: Jonas Bjurel --- README | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) create mode 100644 README (limited to 'README') diff --git a/README b/README new file mode 100644 index 0000000..ad806b3 --- /dev/null +++ b/README @@ -0,0 +1,46 @@ +############################################################################## +# Copyright (c) 2015 Ericsson AB and others. +# jonas.bjurel@ericsson.com +# All rights reserved. This program and the accompanying materials +# are made available under the terms of the Apache License, Version 2.0 +# which accompanies this distribution, and is available at +# http://www.apache.org/licenses/LICENSE-2.0 +############################################################################## + +Configuration repository structure +---------------------------------- +The OPNFV CI deployment engine relies on the configuration directory/file +structure as described below. +This sructure is provided by a secure official OPNFV secured one to which only +jenkins and andmins have access to. +The reason that this configuration structure needs to be secure/hidden +is that there are security sensitive information in the various configuration +files. +The structure provides separation of concerns between configuration provided +by the installer projects, the collaboration/feature/plugin providers/projects. +the CI/CD owners (Releng/Functest) and the lab owners (Pharos). + +Following configuration directory and file structure should be adheared to: + +TOP +! ++--- labs + ! + +---- lab-name-1 + ! ! + ! +---- pod-name-1 + ! ! ! + ! ! +---- fuel + ! ! ! + ! ! +---- config + ! ! ! ! + ! ! +---- dea-pod-override.yaml + ! ! ! + ! ! +---- dha.yaml + ! ! + ! +---- pod-name-2 + ! ! + ! + +---- lab-name-2 + ! ! + -- cgit