summaryrefslogtreecommitdiffstats
path: root/labs/zte/idf-pod1.yaml
AgeCommit message (Collapse)AuthorFilesLines
2018-08-17Add mask to the oob networksManuel Buil1-0/+1
It is not needed but it helps a lot to the xci parser Change-Id: I6943b21cd2aca2036783430cde03fb8d3b567f3b Signed-off-by: Manuel Buil <mbuil@suse.com>
2018-05-31[idf.fuel] Add NTP serversAlexandru Avadanii1-0/+2
Change-Id: Ib840995b085ec9d8a585d5cf2e2a84e5801875b6 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-04-24update idf file for zte-pod1zhihui wu1-1/+1
Change-Id: Iffed25c5e01aa9bf2a7b4a7103b07fb1c097d811 Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
2018-04-18[fuel] Parameterize tenant VLAN rangesAlexandru Avadanii1-1/+1
- IDF: convert all tenant VLANs to ranges; - IA: convert 'M-N' to 'M:N' for `opnfv_net_tenant_vlan`; Change-Id: Ic9211235281c81ba082d10806651c35116ba4c35 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-04-12JOID PDF-IDF support for intel-pod18agardner1-0/+1
More info in gerrit comments. Remove joid from all other idfs other than intel/pod18 add installer: ['apex', 'compass4nfv', 'daisy', 'fuel'] where missing Change-Id: I2afc415599070e210736c5fc304f7cb150f05029 Signed-off-by: agardner <agardner@linuxfoundation.org>
2018-03-03[IDF] zte-pod1: Remove br-mgmtAlexandru Avadanii1-1/+1
All recent Fuel deploy attempts on zte-pod1 failed due to br-mgmt not being present (or up), although it is defined in IDF. Since this bridge is optional in the Fuel deployment process and mostly useful for manual debugging, let's remove it from idf.fuel. Change-Id: I130ec61427237f979f6a6212ca8c291ba203ef39 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-01-26[IDF] zte-pod1: Fix admin bridgeAlexandru Avadanii1-1/+1
Align PXE/admin bridge name on jumpserver with value in releng slave param BRIDGE for zte-pod1. Change-Id: I57e1079bc047046cb85afe6d7f7abcc340217235 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-01-14[PDF] zte-pod*: Move net_config to IDFAlexandru Avadanii1-1/+34
Drop 'fixed_ips', which is a leftover from early net_config implementation. To maintain compatibility with the only 'fixed_ips' consumer (Daisy), add 'address' on the first jumpserver interface to leverage Daisy's fallback path for determining the gateway. While at it, add/update copyright headers. Change-Id: I7c4cb5997e368503ab0b30903e5c0c58e13fe408 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2018-01-14[PDF] Fix yamllint issues in installer adaptersAlexandru Avadanii1-1/+1
Although current YAML files in Pharos are all valid according to yamllint, the resulting YAMLs after PDF/IDF + IA interpolations still have a lot of violations, which need to be addressed. PDF changes: - bii/pod1: + fix typo in disks_A reference; IDF changes: - replace empty strings with `~` keyword (will be expanded to 'None'); IA (installer adapter) changes: - apex: + add missing document start; - compass4nfv: + too few spaces before comment; + missing starting space in comment; + replace '\t' with spaces; - daisy: + None; - fuel: + check conf.idf is defined first (fix parse for PODs without IDF); + move document start outside conf.idf condition - joid: + None; This is not an exhaustive change, some yamllint issues are still there but require either refactoring IAs or changing the PDF/IDF files in a way that needs the respective maintainer's input. Change-Id: I26743e265217e892b6a94de96a016c295ea24fb5 Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
2017-12-01Moving all pdfs to pharos repoagardner1-0/+44
Note: Also fixed yamllint issues with these files Inline encrytion of yaml files allows us to make away with securedlab's restrictions. Going forward, anyone will be able to see Lab PDFs See: https://github.com/opnfv/pharos/blob/master/config/utils/README.eyaml.rst If you are the reviewer on this changeset it is becasue git blamed showed you to be the author of the pdf in this review. Encrypting ipmi password etc is optional. I have scrubbed the password from this change. If you do not need the password to be hidden, please let me know in the comment, and I will put it back. If you do need the password hidden, please follow the readme above and ammend this patch to include the encrypted value that you create on your pods jumphost. Passwords and Usernames removed: $ egrep -r '(pass|user)' zte/pod2/daisy/config/deploy.yml: ipmi_user: zte/pod2/daisy/config/deploy.yml: ipmi_pass: zte/pod2/daisy/config/deploy.yml: ipmi_user: zte/pod2/daisy/config/deploy.yml: ipmi_pass: zte/pod2/daisy/config/deploy.yml: ipmi_user: zte/pod2/daisy/config/deploy.yml: ipmi_pass: zte/pod2/daisy/config/deploy.yml: ipmi_user: zte/pod2/daisy/config/deploy.yml: ipmi_pass: zte/pod2/daisy/config/deploy.yml: ipmi_user: zte/pod2/daisy/config/deploy.yml: ipmi_pass: zte/pod2/daisy/config/deploy.yml:daisy_passwd: '' zte/virtual1/daisy/config/deploy.yml:daisy_passwd: '' zte/pod3.yaml: user: zte/pod3.yaml: pass: zte/pod3/daisy/config/deploy.yml: ipmi_user: zte/pod3/daisy/config/deploy.yml: ipmi_pass: zte/pod3/daisy/config/deploy.yml: ipmi_user: zte/pod3/daisy/config/deploy.yml: ipmi_pass: zte/pod3/daisy/config/deploy.yml: ipmi_user: zte/pod3/daisy/config/deploy.yml: ipmi_pass: zte/pod3/daisy/config/deploy.yml: ipmi_user: zte/pod3/daisy/config/deploy.yml: ipmi_pass: zte/pod3/daisy/config/deploy.yml: ipmi_user: zte/pod3/daisy/config/deploy.yml: ipmi_pass: zte/pod3/daisy/config/deploy.yml:daisy_passwd: '' zte/pod1.yaml: user: zte/pod1.yaml: pass: zte/virtual2/daisy/config/deploy.yml:daisy_passwd: '' zte/pod2.yaml: user: zte/pod2.yaml: pass: lf/pod2.yaml: user: > Change-Id: I876f4b553c51dd4592701539cfce66bcf8c114ab Signed-off-by: agardner <agardner@linuxfoundation.org>