You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+19-10
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,5 @@
1
-
Copyright 2016 Distributed Management Task Force, Inc. All rights reserved.
1
+
Copyright 2016-2018 Distributed Management Task Force, Inc. All rights reserved.
2
+
2
3
# redfishtool
3
4
4
5
## About
@@ -29,14 +30,11 @@ While other generic http clients such as Linux curl can send and receive Redfish
29
30
30
31
## Why redfishtool?
31
32
32
-
33
33
1.***redfishtool*** was originally written during the development of the Redfish specification to help find ambiguities in the spec.
34
34
1.***redfishtool*** is now also being used to test inter-operability between redfish service implementations.
35
35
1. In addition, ***redfishtool*** provides an example implementation for how a client can execute common server management functions like inventory; power-on/off/reset; setting power limits, indicator LEDs, and AssetTags, and searching a multi-node redfish service to find a specific node (with specific UUID, redfish Id, etc). redfishtool follows strict rules of interoperability. To support this goal, liberal comments are added throughout code to explain why each step is being executed.
36
36
1. As described above, it makes it easy to use the Redfish API from a BASH script, or as an easy-to-use interactive CLI -- but WITHOUIT creating a 'new API'. All (rather most) of the responses from ***redfishtool*** are Redfish-defined responses. The properties and resources are defined in the redfish spec. ***redfishtool*** is just a tool to access the Redfish API-not a new interface itself.
37
37
* The execption is that a 'list' operation was added for all collections to display the key properties for each of the members--rather than just the URIs to the members.
38
-
39
-
40
38
41
39
## Usage
42
40
@@ -49,8 +47,8 @@ While other generic http clients such as Linux curl can send and receive Redfish
49
47
****Operations*** are specify an action or operation you want to perform like S`ystems setBootOverride` ..., or `Systems reset`.
50
48
****OtherArgs*** are any other arguments after the Operation that are sometimes required--like: `Systems <setBootOverride> <enableValue>` <targetValue>"
51
49
52
-
53
50
### Common OPTIONS:
51
+
54
52
-V, --version -- show redfishtool version, and exit
55
53
-h, --help -- show Usage, Options, and list of subCommands, and exit
56
54
-u <user>, --user=<usernm> -- username used for remote redfish authentication
@@ -72,18 +70,23 @@ While other generic http clients such as Linux curl can send and receive Redfish
72
70
-sss(+requestHdrs,data,authType, +respStatus_code, +elapsed exec time,
73
71
AuthToken/sessId/sessUri)
74
72
-ssss(+response headers for debug), -sssss(+response data for debug)
73
+
75
74
###### Options used by "raw" subcommand:
75
+
76
76
-d <data> --data=<data> -- the http request "data" to send on PATCH,POST,or PUT requests
77
77
78
78
###### Options to specify top-level collection members: eg: `Systems - I <sysId>`
79
+
79
80
-I <Id>, --Id=<Id> -- Use <Id> to specify the collection member
80
81
-M <prop>:<val> --Match=<prop>:<val> -- Use <prop>=<val> search to find the collection member
81
82
-F, --First -- Use the 1st link returned in the collection or 1st "matching" link if used with -M
82
83
-1, --One -- Use the single link returned in the collection. Return error if more than one member
83
84
-a, --all -- Returns all members if the operation is a Get on a top-level collection like Systems
84
85
-L <Link>, --Link=<Link> -- Use <Link> (eg /redfish/v1/Systems/1) to reference the collection member.
85
86
-- If <Link> is not one of the links in the collection, and error is returned.
0 commit comments