Age | Commit message (Collapse) | Author | Files | Lines |
|
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.
Fixes: c01d68e
Change-Id: I8dc386535a20d64593eccc9abd8ee8d1ef27decf
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: Ide79f18bae20e599eeefe13f4ad2dba1f4a0207d
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Drop 'fixed_ips', which is a leftover from early net_config
implementation.
Rework the contents of 'fixed_ips' using the standard PDF spec
'address' parameter.
Change-Id: Ife2c1c4b0c97479e962a32fa7825864c94e9a80c
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
While at it, drop 'fixed_ips', which is a leftover from early
net_config implementation and is not currently used by the Fuel
installer (only Daisy seems to use 'fixed_ips', but falls back
to using 'address' of the first interface when 'fixed_ips' is not
present).
Keep 'address: 192.168.11' on jumpserver first interface for Daisy
compatibility.
Change-Id: I83455a45a2a19fde6b9fb8b7f0fa8872b1291ab0
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
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>
|
|
|
|
LF PODs IPMI user/pass was previously encrypted with the wrong key,
switch them back to cleartext.
Change-Id: Iccd106b60d2051acf7d928205bd2f6ae3f256884
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: PHAROS-298
Change-Id: Ied56d4e1fdf09d3361de5aae64088e65cb5125ad
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I8e0d88da016801e7997b4cdf870e2d11b4fca80a
Signed-off-by: 00184532 <lu.yao135@zte.com.cn>
|
|
|
|
|
|
Change-Id: Ibdf3ea886fcfca8246cd8cb24d52d12b689a733b
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Fix typo before it gets propagated even more:
$ grep hasewell -Rl . | \
xargs sed -i 's/hasewell/haswell/g'
Change-Id: Id6a17ae8f429946f7febba6f319a25759fc8339f
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Moved net_config from PDF to IDF for discussion on what the idf should look like
The PDF spec is static and should not change.
All changes needed for installers should be put in other descriptor files.
(senario and installer descriptor files)
Change-Id: I79f6c751cabc69bded255ce0471e8512c656c259
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
The previous network segment conflicts with INSTALLER_IP.
Change-Id: I160c2ee368f716d13510bfea69e2dc453d164276
Signed-off-by: zhihui wu <wu.zhihui1@zte.com.cn>
|
|
|
|
|
|
|
|
Change-Id: I86935bee9ff30d811f0e756f93716cb415fa3a01
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
|
|
|
|
Change-Id: I0c4389059edb33fecdd472777d7266c4934f1d07
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
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>
|
|
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.
Change-Id: Idc70540477d8569f15335e75e7725c1e4e56a60b
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
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>
|
|
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: I52a5c117da599fd46aa246de20077d5bdbe8a3b6
Signed-off-by: agardner <agardner@linuxfoundation.org>
|
|
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>
|
|
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>
|