summaryrefslogtreecommitdiffstats
path: root/labs
AgeCommit message (Collapse)AuthorFilesLines
2017-12-15Encrypt ipmi info of zte baremetal podsAlex Yang3-6/+60
Change-Id: I86935bee9ff30d811f0e756f93716cb415fa3a01 Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
2017-12-14Merge "Moving all pdfs to pharos repo"Jack Morgan4-0/+573
2017-12-14Merge "Moving all pdfs to pharos repo"Jack Morgan14-0/+1293
2017-12-01Moving all pdfs to pharos repoagardner14-0/+1293
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>
2017-12-01Moving all pdfs to pharos repoagardner1-0/+294
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 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. Change-Id: Ie3e935e7e9250a387858c29eb77c3c06b4fe3f57 Signed-off-by: agardner <agardner@linuxfoundation.org>
2017-12-01Moving all pdfs to pharos repoagardner4-0/+573
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 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. Change-Id: Ic2db523e7f82a0fb48e462a1fbe1402267f22618 Signed-off-by: agardner <agardner@linuxfoundation.org>
2017-11-23Moving check-jinja2 to pharos.agardner1-0/+244
Securedlab will be going away now that we can encrypt strings (eyaml) we need to check jinja2 PDF templates that will be moving into pharos This adds one pod yaml files and fixes paths in check-jinja2.sh After this is merged I can create a jenkins job for pharos. Then I can start moving pdf files into the pharos repo Change-Id: I2f2f2925275de49035d7d0160249d75b25ca0d20 Signed-off-by: agardner <agardner@linuxfoundation.org>