| commit | dfe81ad5679268f235451e74a84a8a67817f7316 | [log] [tgz] |
|---|---|---|
| author | Marri Devender Rao <devenrao@in.ibm.com> | Mon Jul 01 05:38:09 2019 -0500 |
| committer | Marri Devender Rao <devenrao@in.ibm.com> | Wed Jul 31 09:00:43 2019 -0500 |
| tree | 0fdfcc42c41941b65340f3365867470a70e023ed | |
| parent | 77e7868f28e33d6a2dfc9082d1a4a82db693f546 [diff] |
Add Replace certificate command
Redfish does not support certificate delete rather supports
certificate replace added support for certificate replace.
Tested:
-------OP930-------
$ python openbmctool.py -H $BMC_IP -U root -P 0penBmc certificate replace
server https -f cert.pem
Attempting login...
Replace complete.
{
"data": null,
"message": "200 OK",
"status": "ok"
}
User root has been logged out
-------OP940-------
bash-4.2$ python openbmctool.py -H $BMC_IP -U xxxx -P xxxx certificate --help
usage: openbmctool.py certificate [-h] {update,replace} ...
optional arguments:
-h, --help show this help message and exit
subcommands:
valid certificate commands
{update,replace} sub-command help
update Update the certificate
replace Replace the certificate
bash-4.2$ python openbmctool.py -H abc -U xxxx -P xxxx certificate replace --help
usage: openbmctool.py certificate replace [-h] -f FILELOC
{server,client,authority}
positional arguments:
{server,client,authority}
certificate type to replace
optional arguments:
-h, --help show this help message and exit
-f FILELOC, --fileloc FILELOC
The absolute path to the certificate file
bash-4.2$ python openbmctool.py -H $BMC_IP -U xxxx -P xxxx certificate replace server -f cert.pem
Attempting login...
Replacing certificate url=/redfish/v1/Managers/bmc/NetworkProtocol/HTTPS/Certificates/1
Replace complete.
{
"@odata.context": "/redfish/v1/$metadata#Certificate.Certificate",
"@odata.id": "/redfish/v1/Managers/bmc/NetworkProtocol/HTTPS/Certificates/1",
"@odata.type": "#Certificate.v1_0_0.Certificate",
"CertificateString": "-----BEGIN CERTIFICATE-----\n-----END CERTIFICATE-----\n",
"Description": "HTTPS certificate",
"Id": "1",
"Issuer": {
"CommonName": "localhost",
"Organization": "openbmc-project.xyz"
},
"KeyUsage": [],
"Name": "HTTPS certificate",
"Subject": {
"CommonName": "localhost",
"Organization": "openbmc-project.xyz"
},
"ValidNotAfter": "2029-05-09T19:59:40+00:00",
"ValidNotBefore": "2019-05-12T19:59:40+00:00"
}
Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
Change-Id: I4d222a3db1590c2c4206798ac3cc0eea4899eb48
The goal of this repository is to collect the two-minute hacks you write to automate interactions with OpenBMC systems.
It's highly likely the scripts don't meet your needs - they could be undocumented, dysfunctional or utterly broken. Please help us improve!
Then this repository aims to be the default destination for your otherwise un-homed scripts. As such we are setting the bar for submission pretty low, and we aim to make the process as easy as possible.
openbmc-events: Query error events on the target serveropenbmc-sensors: Query sensors on the target serveropenbmc-sfw: Manage host and BMC firmware images on the target serveropenbmctool: A general purpose tool for user interactions with OpenBMCpretty-journal: Convert journalctl's 'pretty' output to regular outputupload_and_update: Upload a tarball to TFTP server and update BMC with itnetboot: Painless netboot of BMC kernelsobmc-gerrit: Automagically add reviewers to changes pushed to Gerritreboot: Endlessly reboot OpenPOWER hoststracing: Enable and clean up kernel tracepoints remotelywitherspoon-debug: Deploy the debug tools tarball to Witherspoon BMCscla-signers: Check if a contributor has signed the OpenBMC CLAopenbmc-autobump.py: Update commit IDs in bitbake recipes to bring in new changesPlease use gerrit for all patches to this repository:
Do note that you will need to be party to the OpenBMC CLA before your contributions can be accepted. See Gerrit Setup and CLA for more information.
So long as your patches look sane with a cursory glance you can expect them to be applied. We may push back in the event that similar tools already exist or there are egregious issues.
We don't ask for much, but you need to give us at least a Signed-off-by, and put your work under the Apache 2.0 license. Licensing everything under Apache 2.0 will just hurt our heads less. Lets keep the lawyers off our backs. ^
^Any exceptions must be accompanied by a LICENSE file in the relevant subdirectory, and be compatible with Apache 2.0. You thought you would get away without any fine print?
There's no standard way to install the scripts housed in the here, so adding parts of the repository to your PATH might be a bit of a dice-roll. We may also move or remove scripts from time to time as part of housekeeping. It's probably best to copy things out if you need stability.