oneview-sdk 5.12.0 → 5.17.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: '0238ef899ada881e00eb2306bbd4949f6e68f8e563c50439adb2176102a71129'
-  data.tar.gz: a0b3ab5b55a09e7668d6112d86c54bd1161a56271c33fb2c9b3b8096839d185b
+  metadata.gz: 57f4ba8b142a1cc2f82ed657b4ff2cf2ad6e780ba8d4752194da7f2f75adfc9a
+  data.tar.gz: bcfdcc2f203b888fcfeecf99ca4d27b9a1cba089ff197e71d448edf38b05c3f1
 SHA512:
-  metadata.gz: dcbe5953943d825aa5bd0ab3d4c09dabbf86a404495c6cb0e55bd520fa10c30b06198217acecd3d78ec9f3cd11ca4d1603db523714b00498b846d9d034e8d411
-  data.tar.gz: 4121dc7a3e7ea94658543bf7de10e99062ab9cb040015834886b5697a90695d47cac717faee8c59c4c5b45e2b5b45cad77a469dbc69d3691126396b8dc71145c
+  metadata.gz: ed91e250b12f06966b3203c52d0b1ae73c987949dc80c54666472683f67b1efc093d3faf74b818f0bf5d82ee1a76ee30597995bd9df1992240f88ae61cafe2ce
+  data.tar.gz: b6c85c9a553592709c0046a251d891e452afd9b7b40a4360c2dc4ca0a795ffc8d0068b8fa87911293b57401febb7b0c7c21f13151042297c8db62910da5be755

data/CHANGELOG.md

@@ -1,3 +1,148 @@
+## v5.17.0
+#### Notes
+Extends support of the SDK to OneView REST API version 2200 (OneView v5.50) and ImageStreamer REST API version 2000 (I3S v5.40).
+
+#### Bug fixes & Enhancements
+- [#473](https://github.com/HewlettPackard/oneview-sdk-ruby/issues/473)Failing to install oneview-sdk gem as runtime environment
+
+#### Features supported
+- Artifact Bundle
+- Build Plan
+- Connection Template
+- Deployment Group
+- Deployment Plan
+- Enclosure
+- Enclosure Group
+- Ethernet Network
+- FC Network
+- FCOE Network
+- Firmware Driver
+- Golden Image
+- Hypervisor Cluster Profile
+- Hypervisor Manager
+- Interconnects
+- Interconnect Type
+- LIG Uplink Set
+- Logical Enclosure
+- Logical Interconnect
+- Logical Interconnect Group
+- Network Set
+- OS Deployment Plan
+- OS Volume
+- Plan Script
+- Scope
+- Server Certificate
+- Server Hardware
+- Server Hardware Type
+- Storage Pool
+- Server Profile
+- Server Profile Template
+- Storage System
+- Uplink Set
+- Volume
+- Volume Attachment
+- Volume Template
+
+## v5.16.0
+
+#### Notes
+This release extends support to OneView Rest API version 2000 (OneView v5.40) for the hardware variants C7000 and Synergy to the following features:
+
+#### Features supported
+- Connection Template
+- Enclosure
+- Enclosure Group
+- Ethernet Network
+- FC Network
+- FCOE Network
+- Firmware Driver
+- Hypervisor Cluster Profile
+- Hypervisor Manager
+- Interconnect
+- Interconnect Type
+- LIG Uplink Set
+- Logical Enclosure
+- Logical Interconnect
+- Logical Interconnect Group
+- Network Set
+- OS Deployment Plan
+- Scope
+- Server Certificate
+- Server Hardware
+- Server Hardware Type
+- Server Profile
+- Server Profile Template
+- Storage Pool
+- Storage System
+- Uplink Set
+- Volume
+- Volume Attachment
+- Volume Template
+
+#### Bug fixes & Enhancements:
+- Enhanced the method to set the default API version to appliance's max API version instead of hardcoded 200.
+- Added an automation to upload  package to Gems followed with uploading a new image to DockerHub when there is a new release in GitHub
+
+## v5.15.0
+
+#### Notes
+This release extends support to OneView Rest API version 1800 (OneView v5.30) for the Synergy hardware variant to the following features:
+
+#### Features supported
+- OS Deployment Plan
+
+#### Bug fixes & Enhancements
+- [#454](https://github.com/HewlettPackard/oneview-sdk-ruby/issues/454)OSDP resource is missing in API1800
+- [#455](https://github.com/HewlettPackard/oneview-sdk-ruby/issues/455)sasjbod helper function is missing in API1800 server profile resource
+
+## v5.14.0
+
+#### Notes
+This release extends support to OneView Rest API version 1800 (OneView v5.30) for the hardware variants C7000 and Synergy to the following features:
+
+#### Features supported
+- Connection Template
+- Enclosure
+- Enclosure Group
+- Ethernet Network
+- FC Network
+- FCOE Network
+- Firmware Driver
+- Hypervisor Cluster Profile
+- Hypervisor Manager
+- Interconnects
+- Interconnect Types
+- LIG Uplink Set
+- Logical Enclosure
+- Logical Interconnect
+- Logical Interconnect Group
+- Network Set
+- Scope
+- Server Certificate
+- Server Hardware
+- Server Hardware Type
+- Server Profile
+- Server Profile Template
+- Storage Pool
+- Storage System
+- Uplink Set
+- Volume
+- Volume Attachment
+- Volume Template
+
+## v5.13.0
+
+#### Notes
+This release extends support to OneView Rest API version 1600 (OneView v5.20) for the hardware variants C7000 and Synergy to the following features:
+
+#### Features supported
+- Connection Template
+- Firmware Driver
+- LIG UplinkSet
+
+#### Bug fixes & Enhancements
+- [#432](https://github.com/HewlettPackard/oneview-sdk-ruby/issues/432)Snapshot deletion will fail with mis match etags error
+
 ## v5.12.0
 
 #### Notes

data/README.md

@@ -1,18 +1,49 @@
-# oneview-sdk for Ruby
-[![Gem Version](https://badge.fury.io/rb/oneview-sdk.svg)](https://badge.fury.io/rb/oneview-sdk)
-[![Yard Docs](https://img.shields.io/badge/yard-docs-yellow.svg)](http://www.rubydoc.info/gems/oneview-sdk)
+# HPE OneView SDK for Ruby
 
-[![Build Status](https://travis-ci.org/HewlettPackard/oneview-sdk-ruby.svg?branch=master)](https://travis-ci.org/HewlettPackard/oneview-sdk-ruby)
-[![Coverage Status](https://coveralls.io/repos/github/HewlettPackard/oneview-sdk-ruby/badge.svg)](https://coveralls.io/github/HewlettPackard/oneview-sdk-ruby)
-[![Code Climate](https://codeclimate.com/github/HewlettPackard/oneview-sdk-ruby/badges/gpa.svg)](https://codeclimate.com/github/HewlettPackard/oneview-sdk-ruby)
+## Build Status 
 
-The OneView SDK provides a Ruby library to easily interact with HPE OneView and Image Streamer APIs. The Ruby SDK enables developers to easily build integrations and scalable solutions with HPE OneView and Image Streamer.
+| 5.50 Branch   | 5.40 Branch   | 5.30 Branch   | 5.20 Branch   |
+| ------------- |:-------------:| -------------:| -------------:|
+| ![Build status](https://ci.appveyor.com/api/projects/status/u84505l6syp70013?svg=true)| ![Build status](https://ci.appveyor.com/api/projects/status/u84505l6syp70013?svg=true)| ![Build status](https://ci.appveyor.com/api/projects/status/u84505l6syp70013?svg=true)| ![Build status](https://ci.appveyor.com/api/projects/status/u84505l6syp70013?svg=true)
+
+
+## Introduction
+
+HPE OneView makes it simple to deploy and manage today’s complex hybrid cloud infrastructure. HPE OneView can help you transform your data center to software-defined, and it supports HPE’s broad portfolio of servers, storage, and networking solutions, ensuring the simple and automated management of your hybrid infrastructure. Software-defined intelligence enables a template-driven approach for deploying, provisioning, updating, and integrating compute, storage, and networking infrastructure.
+
+The HPE OneView Ruby SDK provides library to easily interact with HPE OneView and HPE Image Streamer REST APIs. The HPE OneView Ruby SDK enables developers to easily build integrations and scalable solutions with HPE OneView and HPE Image Streamer.
+
+You can find the latest supported HPE OneView Ruby SDK [here](https://github.com/HewlettPackard/oneview-sdk-ruby/releases/latest)
+
+## What's New
+
+HPE OneView Ruby library extends support of the SDK to OneView REST API version 2200 (OneView v5.50)
+
+Please refer to [notes](https://github.com/HewlettPackard/oneview-sdk-ruby/blob/master/CHANGELOG.md) for more information on the changes , features supported and issues fixed in this version
+
+## Getting Started 
+
+## Installation and Configuration
 
 ## Installation
-- Require the gem in your Gemfile:
+HPE OneView SDK for Ruby can be installed from Source and Docker container installation methods.You can either use a docker container which will have the HPE OneView SDK for Ruby installed or perform local installation.
+
+###  Docker Setup
+The light weight containerized version of the HPE OneView SDK for Ruby is available in the [Docker Store](https://store.docker.com/community/images/hewlettpackardenterprise/hpe-oneview-sdk-for-ruby). The Docker Store image tag consist of two sections: <sdk_version-OV_version>
+
+```bash
+# Download and store a local copy of oneview-sdk-ruby and use it as a Docker Image.
+$ docker pull hewlettpackardenterprise/hpe-oneview-sdk-for-ruby:v5.17.0-OV5.5
+# Run docker commands below given, which  will in turn create a sh session 
+# where you can create files, issue commands and execute the examples.
+$ docker run -it hewlettpackardenterprise/hpe-oneview-sdk-for-ruby:v5.17.0-OV5.5 /bin/sh
+```
+
+### Local Setup
+- Local installation requires the gem in your Gemfile:
 
   ```ruby
-  gem 'oneview-sdk', '~> 5.2'
+  gem 'oneview-sdk', '~> 5.5'
   ```
 
   Then run `$ bundle install`
@@ -24,7 +55,9 @@ The OneView SDK provides a Ruby library to easily interact with HPE OneView and
 
 
 ## Configuration
-The OneView client has a few configuration options, which you can pass in during creation:
+
+### OneView Client Configuration
+The OneView Client configuration options that can be passed during OneView Client object creation:
 
 ```ruby
 # Create a OneView client object:
@@ -33,18 +66,19 @@ client = OneviewSDK::Client.new(
   url: 'https://oneview.example.com',
   user: 'Administrator',              # This is the default
   password: 'secret123',
-  token: 'xxxx...',                   # Set EITHER this or the user & password
+  token: 'xxxx...',                   # Set EITHER token or the username & password
   ssl_enabled: true,                  # This is the default and strongly encouraged
   logger: Logger.new(STDOUT),         # This is the default
   log_level: :info,                   # This is the default
   domain: 'LOCAL',                    # This is the default
-  api_version: 200                    # Defaults to minimum of 200 and appliance's max API version
+  api_version: 2200                   # Defaults to appliance's max API version which is API version of OneView 5.50
 )
 ```
 
 :lock: Tip: Check the file permissions because the password is stored in clear-text.
 
-The Image Streamer (I3S) client is very similar to the OneView client, but has one key difference:
+### Image Streamer Client Configuration
+The Image Streamer (I3S) client is very much similar to the OneView client, but has one key difference:
 it cannot generate it's own token. However, it uses the same token given to or generated by the OneView client,
 so if you need to generate a token, create a OneView client using a user & password, then pass the generated token
 into the Image Streamer client.
@@ -58,11 +92,12 @@ i3s_client = OneviewSDK::ImageStreamer::Client.new(
   ssl_enabled: true,                  # This is the default and strongly encouraged
   logger: Logger.new(STDOUT),         # This is the default
   log_level: :info,                   # This is the default
-  api_version: 300                    # Defaults to minimum of 300 and appliance's max API version
+  api_version: 2000                   # Defaults to appliance's max API version
 )
 ```
 
-You can also create the i3s client through the Oneview client instance.
+You can also create the Image Streamer(I3S) client through the Oneview client instance.
+
 ```ruby
 # Create an Image Streamer client object through the Oneview client object:
 require 'oneview-sdk'
@@ -71,13 +106,13 @@ i3s_client = client.new_i3s_client(
   ssl_enabled: true,                  # This is the default and strongly encouraged
   logger: Logger.new(STDOUT),         # This is the default
   log_level: :info,                   # This is the default
-  api_version: 300                    # Defaults to minimum of 300 and appliance's max API version
+  api_version: 2000                    # Defaults to appliance's max API version
 )
 ```
 
-##### Environment Variables
+### Environment Variables
 
-You can also set many of the client attributes using environment variables. To set these variables in bash:
+Configuration can also be defined through environment variables.To set these variables in bash:
 
 ```bash
 # OneView client options:
@@ -120,7 +155,7 @@ i3s_client = OneviewSDK::ImageStreamer::Client.new
 
 NOTE: Run `$ oneview-sdk-ruby env` to see a list of available environment variables and their current values.
 
-##### Configuration Files
+### Configuration Files
 
 Configuration files can also be used to define client configuration (json or yaml formats). Here's an example json file:
 
@@ -129,7 +164,7 @@ Configuration files can also be used to define client configuration (json or yam
   "url": "https://oneview.example.com",
   "user": "Administrator",
   "password": "secret123",
-  "api_version": 200
+  "api_version": 2200
 }
 ```
 
@@ -158,87 +193,56 @@ level=(Symbol, etc.) # The parameter here will be the log_level attribute
 
 ## API Implementation
 
-A status of the HPE OneView REST interfaces that have been implemented in this SDK can be found in the [endpoints-support.md](https://github.com/HewlettPackard/oneview-sdk-ruby/blob/master/endpoints-support.md) file.
+A detailed list of the HPE OneView REST interfaces that have been implemented in this SDK can be found in the [endpoints-support.md](https://github.com/HewlettPackard/oneview-sdk-ruby/blob/master/endpoints-support.md) file.
 
-### OneView API versions and appliance types
-You may notice resource classes being accessed in a few different ways; for example, `OneviewSDK::EthernetNetwork`, `OneviewSDK::API300::EthernetNetwork`, and `OneviewSDK::API300::C7000::EthernetNetwork`. However, each of these accessors may actually be referring to the same class. This is because in order to keep backwards compatibility and make examples a little more simple, there are module methods in place to redirect/resolve the shorthand accessors to their full namespace identifier. In order to automatically complete the full namespace identifier, there are some defaults in place. Here's some example code that should help clear things up (return values are commented behind the code):
+### HPE OneView API Versions and Appliance types
+You may notice resource classes being accessed in a few different ways; for example, `OneviewSDK::EthernetNetwork`, `OneviewSDK::API1000::EthernetNetwork`, and `OneviewSDK::API1000::C7000::EthernetNetwork`. However, each of these accessors may actually be referring to the same class. This is because in order to keep backwards compatibility and make examples a little more simple, there are module methods in place to redirect/resolve the shorthand accessors to their full namespace identifier. In order to automatically complete the full namespace identifier, there are some defaults in place. Here's some example code that should help clear things up (return values are commented behind the code):
 
 ```ruby
 require 'oneview-sdk'
 
 # Show defaults:
-OneviewSDK::SUPPORTED_API_VERSIONS      # [200, 300, 500, 600, 800, 1000,1200, 1600]
-OneviewSDK::DEFAULT_API_VERSION         # 200
-OneviewSDK.api_version                  # 200
+OneviewSDK::SUPPORTED_API_VERSIONS      # [1000, 1200, 1600, 1800, 2000, 2200]
+OneviewSDK::DEFAULT_API_VERSION         # 2200
+OneviewSDK.api_version                  # 2200
 OneviewSDK.api_version_updated?         # false
 
 # Notice the automatic redirection/resolution when we use the shorthand accessor:
-OneviewSDK::EthernetNetwork             # OneviewSDK::API200::EthernetNetwork
+OneviewSDK::EthernetNetwork             # OneviewSDK::API2200::EthernetNetwork
 
 # Even this comparison is true:
-OneviewSDK::EthernetNetwork == OneviewSDK::API200::EthernetNetwork  # true
+OneviewSDK::EthernetNetwork == OneviewSDK::API2200::EthernetNetwork  # true
 
 # Now let's set a new API version default:
-OneviewSDK.api_version = 300
-OneviewSDK.api_version                  # 300
+OneviewSDK.api_version = 2200
+OneviewSDK.api_version                  # 2200
 OneviewSDK.api_version_updated?         # true
 
-# The API200 module has no variants, but API300 and above has 2 (C7000 & Synergy):
-OneviewSDK::API300::SUPPORTED_VARIANTS  # ['C7000', 'Synergy']
-OneviewSDK::API300::DEFAULT_VARIANT     # 'C7000'
-OneviewSDK::API300.variant              # 'C7000'
-OneviewSDK::API300.variant_updated?     # false
-
-OneviewSDK::API500::SUPPORTED_VARIANTS  # ['C7000', 'Synergy']
-OneviewSDK::API500::DEFAULT_VARIANT     # 'C7000'
-OneviewSDK::API500.variant              # 'C7000'
-OneviewSDK::API500.variant_updated?     # false
-
-OneviewSDK::API600::SUPPORTED_VARIANTS  # ['C7000', 'Synergy']
-OneviewSDK::API600::DEFAULT_VARIANT     # 'C7000'
-OneviewSDK::API600.variant              # 'C7000'
-OneviewSDK::API600.variant_updated?     # false
-
-OneviewSDK::API800::SUPPORTED_VARIANTS  # ['C7000', 'Synergy']
-OneviewSDK::API800::DEFAULT_VARIANT     # 'C7000'
-OneviewSDK::API800.variant              # 'C7000'
-OneviewSDK::API800.variant_updated?     # false
-
-OneviewSDK::API1000::SUPPORTED_VARIANTS  # ['C7000', 'Synergy']
-OneviewSDK::API1000::DEFAULT_VARIANT     # 'C7000'
-OneviewSDK::API1000.variant              # 'C7000'
-OneviewSDK::API1000.variant_updated?     # false
-
-OneviewSDK::API1200::SUPPORTED_VARIANTS  # ['C7000', 'Synergy']
-OneviewSDK::API1200::DEFAULT_VARIANT     # 'C7000'
-OneviewSDK::API1200.variant              # 'C7000'
-OneviewSDK::API1200.variant_updated?     # false
-# Therefore, there is 1 more namespace level to the real resource class name
-OneviewSDK::EthernetNetwork             # OneviewSDK::API300::C7000::EthernetNetwork
-OneviewSDK::API300::EthernetNetwork     # OneviewSDK::API300::C7000::EthernetNetwork
-
-# Likewise, we can set a new default variant for the API300 module:
-OneviewSDK::API300.variant = 'Synergy'
-OneviewSDK::API300.variant              # 'Synergy'
-OneviewSDK::API300.variant_updated?     # true
-OneviewSDK::EthernetNetwork             # OneviewSDK::API300::Synergy::EthernetNetwork
-OneviewSDK::API300::EthernetNetwork     # OneviewSDK::API300::Synergy::EthernetNetwork
-
-OneviewSDK::API1600::SUPPORTED_VARIANTS  # ['C7000', 'Synergy']
-OneviewSDK::API1600::DEFAULT_VARIANT     # 'C7000'
-OneviewSDK::API1600.variant              # 'C7000'
-OneviewSDK::API1600.variant_updated?     # false
-
-# Likewise, we can set a new default variant for the API1600 module:
-OneviewSDK::API1600.variant = 'Synergy'
-OneviewSDK::API1600.variant              # 'Synergy'
-OneviewSDK::API1600.variant_updated?     # true
-# Therefore, there is 1 more namespace level to the real resource class name
-OneviewSDK::EthernetNetwork             # OneviewSDK::API300::C7000::EthernetNetwork
-OneviewSDK::API1600::EthernetNetwork     # OneviewSDK::API1600::C7000::EthernetNetwork
+# The API300 and above has 2 variants (C7000 & Synergy): For eg
+
+OneviewSDK::API1800::SUPPORTED_VARIANTS  # ['C7000', 'Synergy']
+OneviewSDK::API1800::DEFAULT_VARIANT     # 'C7000'
+OneviewSDK::API1800.variant              # 'C7000'
+OneviewSDK::API1800.variant_updated?     # false
+
+OneviewSDK::API2000::SUPPORTED_VARIANTS  # ['C7000', 'Synergy']
+OneviewSDK::API2000::DEFAULT_VARIANT     # 'C7000'
+OneviewSDK::API2000.variant              # 'C7000'
+OneviewSDK::API2000.variant_updated?     # false
+
+OneviewSDK::API2200::SUPPORTED_VARIANTS  # ['C7000', 'Synergy']
+OneviewSDK::API2200::DEFAULT_VARIANT     # 'C7000'
+OneviewSDK::API2200.variant              # 'C7000'
+OneviewSDK::API2200.variant_updated?     # false
+
+# Likewise, we can set a new default variant for the API2200 module:
+OneviewSDK::2200.variant = 'Synergy'
+OneviewSDK::API2200.variant              # 'Synergy'
+OneviewSDK::API2200.variant_updated?     # true
+
 ```
 
-We understand that this can be confusing, so to avoid any confusion or unexpected behavior, we recommend specifying the full namespace identifier in your code. At the very least, set defaults explicitly using `OneviewSDK.api_version = <ver>` and `OneviewSDK::API300.variant = <variant>`, as the defaults may change.
+:lock: Tip: We understand that this can be confusing, so to avoid any confusion or unexpected behavior, we recommend specifying the full namespace identifier in your code. At the very least, set defaults explicitly using `OneviewSDK.api_version = <ver>` and `OneviewSDK::API2200.variant = <variant>`, as the defaults may change.
 
 ## Resources
 Each OneView and Image Streamer resource is exposed via a Ruby class, enabling CRUD-like functionality (with some exceptions).
@@ -359,7 +363,6 @@ This example is about as basic as it gets, but you can make any type of OneView
 If a resource does not do what you need, this will allow you to do it.
 Please refer to the documentation and [code](lib/oneview-sdk/rest.rb) for complete list of methods and information about how to use them.
 
-
 ## CLI
 This gem also comes with a command-line interface to make interacting with OneView possible without the need to create a Ruby program or script.
 
@@ -458,19 +461,6 @@ $ oneview-sdk-ruby cert import https://oneview.example.com
 $ oneview-sdk-ruby scmb
 $ oneview-sdk-ruby scmb -r 'scmb.ethernet-networks.#'
 ```
-
-## License
-This project is licensed under the Apache 2.0 license. Please see [LICENSE](LICENSE) for more info.
-
-## Contributing and feature requests
-**Contributing:** You know the drill. Fork it, branch it, change it, commit it, and pull-request it.
-We are passionate about improving this project, and glad to accept help to make it better.
-
-NOTE: We reserve the right to reject changes that we feel do not fit the scope of this project, so for feature additions, please open an issue to discuss your ideas before doing the work.
-
-**Feature Requests:** If you have a need that is not met by the current implementation, please let us know (via a new issue).
-This feedback is crucial for us to deliver a useful product. Do not assume we have already thought of everything, because we assure you that is not the case.
-
 ### Building the Gem
 First run `$ bundle` (requires the bundler gem), then...
  - To build only, run `$ rake build`.
@@ -486,5 +476,49 @@ First run `$ bundle` (requires the bundler gem), then...
 
 For the full testing reference please look into [TESTING.md](TESTING.md) file.
 
-## Authors
-See the [contributors graph](https://github.com/HewlettPackard/oneview-sdk-ruby/graphs/contributors)
+## Getting Help 
+
+Are you running into a road block? Have an issue with unexpected behavior? Feel free to open a new issue on the [issue tracker](https://github.com/HewlettPackard/oneview-ansible/issues)
+
+## License
+This project is licensed under the Apache 2.0 license. Please see [LICENSE](LICENSE) for more info.
+
+## Contributing and feature requests
+
+We welcome your contributions to the HPE OneView for Ruby SDK library. 
+
+**Contributing:** You know the drill. Fork it, branch it, change it, commit it, and pull-request it.
+We are passionate about improving this project, and glad to accept help to make it better.
+
+NOTE: We reserve the right to reject changes that we feel do not fit the scope of this project, so for feature additions, please open an issue to discuss your ideas before doing the work.
+
+**Feature Requests:** If you have a need that is not met by the current implementation, please let us know opening an new enhancement request/issue.
+This feedback is important for us to deliver a useful product. 
+
+
+## Additional Resources 
+
+**HPE OneView Documentation**
+
+[HPE OneView Release Notes](http://hpe.com/info/OneView/docs)
+
+[HPE OneView Support Matrix](http://hpe.com/info/OneView/docs)
+
+[HPE OneView Installation Guide](http://hpe.com/info/OneView/docs)
+
+[HPE OneView User Guide](http://hpe.com/info/OneView/docs)
+
+[HPE OneView Online Help](http://hpe.com/info/OneView/docs)
+
+[HPE OneView REST API Reference](http://hpe.com/info/OneView/docs)
+
+[HPE OneView Firmware Management White Paper](http://hpe.com/info/OneView/docs)
+
+[HPE OneView Deployment and Management White Paper](http://hpe.com/info/OneView/docs)
+
+
+**HPE OneView Community**
+
+[HPE OneView Community Forums](http://hpe.com/info/oneviewcommunity)
+
+Learn more about HPE OneView at [hpe.com/info/oneview](https://hpe.com/info/oneview)