Postman collections for Redfish requests against HPE servers
This repository contains exported Postman collections in .json files as well as a typical environment with suitable variables holding everything needed to run Redfish requests against HPE iLOs in a smoothly manner.
The overall goal is to provide raw Redfish examples to understand the basic Redfish mechanic. Once this mechanic is digested you will be able to translate the examples into your favorite programing or scripting language (Python, PowerShell...). Note that the Generate Code Snippet Postman facility can help you to perform this kind of translation.
The Redfish requests of this repository can help as well understand the examples posted in the python-ilorest-library.
NOTE: Using such raw Redfish requests or code snippets in a production environment is a very bad idea because Redfish objects may change their location overtime or be different from one server to another. Read the Getting Started with iLO RESTful API article to understand how important it is to never assume a Redfish property location.
Install or upgrade to the latest version of Postman and make sure it is connected to the Internet.
You need first to import the typical Redfish environment and customize it with your own values.
Download the Redfish_generic.postman_environment.json to your local computer. Start Postman and open the Manage Environments window (gear wheel icon in the upper right corner). Click on the import button, browse and select the just downloaded environment.
Once this generic environment is imported, select it and customize the three variables according to your environment: iloURI, iloUser and iloPasswd. The Token and SessionLocation variables will be automatically populated during the iLO session creation. Hence you can leave them empty.
Click on the Update button to save your changes.
You can now kill the Manage Environments popup window and select this new environment in the environment pull down list (upper right corner).
To use the various collections of this repository, you must import first the 1_Sessions collection. This collection contains iLO session management requests.
Copy in the clipboard the .json collection URL. Start Postman and click on File --> Import.... Select the Import From Link tabulation. Paste the URL in the dialog box and click import. You should see this new imported collection in the collection pane on the left side of Postman.
Use the same methodology to import other collections.
Expand the 1_Sessions collection and click on the Create iLO Session request. Click on the Send button. If everything goes smoothly, you get a 201 Created status code. You can verify that the Token and SessionLocation variables have been populated by the test javascript. The Token variable will be to authenticate future requests. The SessionLocation will be used to delete the iLO session.
Generic Redfish Postman environment containing the remote iLO IP address as well as the remote iLO credentials required to open a session. It contains as well Token and SessionLocation variables required, respectively, to authenticate HTTP requests and delete the iLO session.
Create, Delete and View iLO sessions. Use of the Postman test facility to capture the session Token and Session Location during the session creation.
Read the Managing iLO sessions with Redfish article to better understand iLO session management.
Management of HPE Smart Storage: view, create, delete disks and logical drives.
This collection can only be used against HPE Gen10 servers only.
This collection has been used to write the Storage management with Redfish article.
This collection proposes mount and unmount Virtual drive requests using the Redfish standard and the legacy HPE Oem implementation.
The first versions of the Redfish VirtualMedia were very limited in terms of actions and properties. However, in order to propose a decent user experience, HPE implemented its own Virtual Media subsystem under the Oem sub-tree, as permitted by the Redfish standard.
Today, and for backward compatibility, HPE implements both the Redfish VirtualMedia standard and its legacy Oem implementation.