Age | Commit message (Collapse) | Author | Files | Lines |
|
I am removing the following committers who are standing down..
Jose Lausuch
Morgan Richomme
Wenjing Chu
Change-Id: I1cc451cc9a4c4598262ce913a1b34a2a656b9d61
|
|
|
|
I would like to nominate Trevor Bramwell as a committer to the Pharos project.
Trevor has been an active contributor to the Pharos project over the last few months.
Please provide a +1/-1 vote before the end of next week, Dec. 31st
Change-Id: I8c7d09e67a86c814bb89beac878da74a03bdd1c4
|
|
I would like to nominate Aric Gardner as a committer to the Pharos project. Aric has been an active contributor to the Pharos project over the last few months.
Please provide a +1/-1 vote before the end of next week, Dec. 31st
Change-Id: Ia381c93bd46053891195f8740d43cd4b010bef42
|
|
|
|
|
|
|
|
|
|
VIP can not conflict with the address of any node.
Otherwise the deployment will fail. See [1].
[1]: https://build.opnfv.org/ci/job/daisy-deploy-baremetal-daily-master/359
Change-Id: I53a79c478d355d00b6eec16c462694eab68292d7
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
The admin external network mapping is used by post deploy script
in daisy to create network.
Change-Id: I4bdde9ca52d8932f77e91b8bf7d41b0c2e821a20
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
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>
|
|
I would like to nominate Alexandru Avadanii as a committer to the Pharos
project. Alexandru Avadanii has been an active contributor to the Pharos
project over the last few months.
Please provide a +1/-1 vote before the end of next week, Dec. 31st
Change-Id: I192c87b6a36b2981cdfb4c780bd1fff9152201a8
|
|
|
|
If keys do not exist, the skipping decryption python stuff doesn't
work, see:
https://build.opnfv.org/ci/job/validate-pdf-jinja2-templates-master/16/consoleFull
Still does not fallback to plain in the case of a 'bad decryption',
but the current code does not either, bad decryption is logged
in any case.
Change-Id: I8da2c7cf8568a6e77ca24cc9ce665410d93b7ba9
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>
|
|
I would like to nominate Parker Berberian as a committer to the Pharos project. Parker has been an active contributor to the Pharos project over the last few months. His foxus on the Pharos Dashboard will be key to reaching community goals.
Please provide a +1/-1 vote before the end of next week, Dec. 31st
Change-Id: Iee363751fd06a12a4e16b8a638e821ea274a7f96
|
|
I would like to nominate Guillermo Herrero as a committer to the Pharos project. Guillermo has been an active contributor to the Pharos project over the last few months.
Please provide a +1/-1 vote before the end of next week, Dec. 31st
Change-Id: I452c1eb1050932accdf312226d4808f41d574ee3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The example configuration file in the directory pharos/config/utils/
is config.example.yaml.
Change-Id: I493274e4ddb689eb729ed642b5f495b5be0b75b0
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
Change-Id: I86935bee9ff30d811f0e756f93716cb415fa3a01
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
|
|
|
|
|
|
On CentOS7 systems the gem command is contained in the 'rubygems'
package, not 'ruby-gems'.
After the keys have been moved, there is not reason to keep around the
'keys' directory.
Change-Id: I5cb9f474276de75b650ddf323a279e139fb62d37
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Change-Id: I0c4389059edb33fecdd472777d7266c4934f1d07
Signed-off-by: Trevor Bramwell <tbramwell@linuxfoundation.org>
|
|
Removing Qiao Fu who is no longer able to participate in project.
Change-Id: I4bfcb378f3a5da6af59292f8911fa8fc8200cbae
|
|
|
|
|
|
|
|
JIRA: FUEL-313
Change-Id: I046ea732e1047f793f1b3bc6f7fc31cfcee9ff40
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Our PDF installer adapter defines 3 unused reclass params that are
misleading, so drop them (infra_compute_node{01,02,03}_address).
Change-Id: Iedf68bbfa77f3a42572dde30275318c8d04f5eb4
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
If eyaml is not installed or misconfigured, we should output raw
encrypted data and throw a warn/error accordingly, instead of
bailing out completely.
Needed for Fuel deploys on PODs that do not use PDF encryption, e.g.
lf-pod2.
Change-Id: I2905df11a3cf2f2eb1ab9bfd8bd88619af2cab04
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
Change-Id: I3a82ed747d2671510a25e65388c7f73ec760afc3
Signed-off-by: Alexandru Avadanii <Alexandru.Avadanii@enea.com>
|
|
JIRA: FUEL-305
Change-Id: Ic5a2d499925aeec5b597394a059640ddae83fb2d
Signed-off-by: Guillermo Herrero <guillermo.herrero@enea.com>
|
|
|
|
|
|
|
|
JIRA: DAISY-74
Add jinja2 templates for daisy network configuration.
For DPDK, TENANT and EXTERNAL networks should share the
same interface now.
Change-Id: I6e9b7a68fb572e9ad844cfcc6ff383aaa25e3bc1
Signed-off-by: Alex Yang <yangyang1@zte.com.cn>
|
|
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>
|
|
Stupid jenkins
Change-Id: Ibfd83e7dadd674cfe7d7a9c2a712ef069fb8d5de
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>
|