This project is no longer being developed and has limited support. In the near future this repository will be fully deprecated. Please consider using other OneView projects, such as Terraform and Ansible Collection
Home Page: https://forge.puppet.com/hewlettpackard/oneview
License: Apache License 2.0
Use Oneview_logical_switch with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_logical_switch resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_datacenter with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_datacenter resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use the SDK like method instead of custom find_bys for ensuring idempotency on resources
Puppet module for HPE OneView Version: 2.0.0
OneView SDK Version: 3.1.0
OneView Appliance Version: 3.0
OneView Client API Version: 300
Puppet Version: 4.8
Ruby Version: 2.2.6
Platform: Windows
Run any exists?
Use a standard like method instead of custom find_bys
Currently there are several different find_bys being used, some use unique_id, some use the whole @data, others are completely ignored.
Use Oneview_logical_interconnect_group with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_logical_interconnect_group resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use the Golden Image resource from this module
-Puppet module for HPE OneView Version: 2.2.0
-OneView SDK Version: 3.1.0
-OneView Appliance Version: 3.0
-OneView Client API Version: 300
-Puppet Version: 4.8
-Ruby Version: 2.2.6
-Platform: Windows/Linux
Try to call the resource Image_streamer_golden_image
To be able to use the resource Golden Image on Image Streamer
Resource not implemented / Could not find the Image_streamer_golden_image
Use Oneview_logical_switch_group with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_logical_switch_group resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
On some usage scenarios, when running with the 'present' ensurable, the server profile does not behave idempotently as expected and makes calls when it shouldn't.
Puppet module for HPE OneView Version: 2.0.0
OneView SDK Version: 3.1.0
OneView Appliance Version: 3.0
OneView Client API Version: 300
Puppet Version: 4.8
Ruby Version: 2.2.6
Platform: Windows
Run complete scenarios with server profile, specifying as many options as possible.
If there are no changes between manifest runs, or if the change is something which should not matter, like order on a hash, then no create/update/patch calls should be made to OneView since it should be able to notice nothing has changed.
On some scenarios it actually does not act as expected and runs update calls.
Use Oneview_enclosure_group with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_enclosure_group resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Should improve documentation metadata to include supported OS and integrate repository with Travis CI.
Reduce code duplication and complexity, while maintaining functionality.
-Puppet module for HPE OneView Version: 2.0.0
-OneView SDK Version: 3.1.0
-OneView Appliance Version: 3.0
-OneView Client API Version: 300
-Puppet Version: 4.8
-Ruby Version: 2.2.6
-Platform: Windows
Check the code, mainly on the resources which currently do not use a parent class.
Should have the least amount of code duplication, as it is possible.
Some classes currently are not yet inheriting from Oneview_resource and thus have a lot of code duplication inside them.
Also, others were implemented while the Oneview_resource class was being improved, and could also have many improvements.
Use Oneview_storage_system with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_storage_system resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_logical_interconnect with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_logical_interconnect resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_interconnect with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_interconnect resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use the SAS Logical Interconnect Group resource from this module
-Puppet module for HPE OneView Version: 2.0.0
-OneView SDK Version: 3.1.0
-OneView Appliance Version: 3.0
-OneView Client API Version: 300
-Puppet Version: 4.8
-Ruby Version: 2.2.6
-Platform: Windows
Try to call the resource Oneview_sas_logical_interconnect_group
To be able to use the resource to create, update and delete SAS Logical Interconnect Groups on OneView
Resource not implemented / Could not find the Oneview_sas_logical_interconnect_group type
Use Oneview_firmware_bundle with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_firmware_bundle resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_rack with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_rack resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_power_device with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_power_device resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_server_hardware_type with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_server_hardware_type resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use the SAS Interconnect resource from this module
-Puppet module for HPE OneView Version: 2.0.0
-OneView SDK Version: 3.1.0
-OneView Appliance Version: 3.0
-OneView Client API Version: 300
-Puppet Version: 4.8
-Ruby Version: 2.2.6
-Platform: Windows
Try to call the resource Oneview_sas_interconnect
To be able to use the resource to create, update and delete SAS Interconnects on OneView
Resource not implemented / Could not find the Oneview_sas_interconnect type
Insert a name for Scope Uris and it automatically get the correct resource for it
Puppet module for HPE OneView Version: 2.0.0
OneView SDK Version: 3.1.0
OneView Appliance Version: 3.0
OneView Client API Version: 300
Puppet Version: 4.8
Ruby Version: 2.2.6
Platform: Windows
Insert a name instead of a '/rest/etc' uri on a scope uri field
Should "automagically" get the resource uri
Currently does not work / this is not yet implemented on the ruby sdk
Use Oneview_uplink_set with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_uplink_set resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_managed_san with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_managed_san resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_enclosure with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_enclosure resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_volume_template with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_volume_template resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use the information from a get endpoint as an input or variable for a resource declaration
Feature not implemented - no steps to reproduce
Expected meaningful facts with output that can be used as variables on resource declarations
Currently no facts are available for this module
Use Oneview_server_hardware with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_server_hardware resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_logical_enclosure with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_logical_enclosure resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_server_profile_template with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_server_profile_template resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use the SAS Logical Interconnect resource from this module
-Puppet module for HPE OneView Version: 2.0.0
-OneView SDK Version: 3.1.0
-OneView Appliance Version: 3.0
-OneView Client API Version: 300
-Puppet Version: 4.8
-Ruby Version: 2.2.6
-Platform: Windows
Try to call the resource Oneview_sas_logical_interconnect
To be able to use the resource to create, update and delete SAS Logical Interconnects on OneView
Resource not implemented / Could not find the Oneview_sas_logical_interconnect type
Run unit tests on a file with API 200 and Synergy hardware variant.
Run unit tests on a file with API 200 and Synergy hardware variant.
I get only the c7000 unit tests for 200, as synergy was not supported in 200.
It tries to run Synergy with 200 and fails due to uninitialized constant.
Use the Plan Script resource from this module
-Puppet module for HPE OneView Version: 2.2.0
-OneView SDK Version: 3.1.0
-OneView Appliance Version: 3.0
-OneView Client API Version: 300
-Puppet Version: 4.8
-Ruby Version: 2.2.6
-Platform: Windows/Linux
Try to call the resource Image_streamer_plan_script
To be able to use the resource Plan Script on Image Streamer
Resource not implemented / Could not find the Image_streamer_plan_script type
Use Oneview_firmware_driver with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_firmware_driver resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use the OS Volume resource from this module
-Puppet module for HPE OneView Version: 2.2.0
-OneView SDK Version: 3.1.0
-OneView Appliance Version: 3.0
-OneView Client API Version: 300
-Puppet Version: 4.8
-Ruby Version: 2.2.6
-Platform: Windows/Linux
Try to call the resource Image_streamer_os_volume
To be able to use the resource OS Volume on Image Streamer
Resource not implemented / Could not find the Image_streamer_os_volume type
Use Oneview_logical_downlink with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_logical_downlink resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Inch CI is showing some undocumented methods. Should look into those and make sure everything is either documented or look into disabling Inch CI for what is not relevant/should not be documented.
Check the Inch CI in the readme or https://inch-ci.org/github/HewlettPackard/oneview-puppet
See no undocumented methods
There's something like 1/3 methods that are undocumented. Those should be documented or if the CI is expecting documentation where it would not make sense, a way to clearly show that would also be good.
Read updated documentation on the new resource types added and new ensure methods
-Puppet module for HPE OneView Version: 2.0.0
-OneView SDK Version: 3.1.0
-OneView Appliance Version: 3.0
-OneView Client API Version: 300
-Puppet Version: 4.8
-Ruby Version: 2.2.6
-Platform: Windows
Check the docs
Should have the documentation for all ensure methods and resource types
Currently it does not.
Use Oneview_volume with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_volume resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_unmanaged_device with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_unmanaged_device resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_switch with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_switch resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Currently the module only has support for the C7000 variant of the enclosures supported by OneView. Since the oneview-sdk gem that this module uses has extended support for the Synergy variant, this should be added as well.
Use Oneview_storage_pool with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_storage_pool resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use the Drive Enclosure resource with this module
-Puppet module for HPE OneView Version: 2.0.0
-OneView SDK Version: 3.1.0
-OneView Appliance Version: 3.0
-OneView Client API Version: 300
-Puppet Version: 4.8
-Ruby Version: 2.2.6
-Platform: Windows
Try to call the resource Oneview_drive_enclosure
To be able to use the resource Drive Enclosures on OneView
Resource not implemented / Could not find the Oneview_drive_enclosure type
'rake test' should fail if a file has not achieved a minimal coverage%, but with its current configs it doesn't
1- Delete one of the unit tests under spec/unit/provider
2- Run 'rake test'
It should fail because the provider for which the test was deleted does meet the minimal code coverage
Does not fail
Use Oneview_volume_attachment with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_volume_attachment resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use the Deployment Plan resource from this module
-Puppet module for HPE OneView Version: 2.2.0
-OneView SDK Version: 3.1.0
-OneView Appliance Version: 3.0
-OneView Client API Version: 300
-Puppet Version: 4.8
-Ruby Version: 2.2.6
-Platform: Windows/Linux
Try to call the resource Image_streamer_deployment_plan
To be able to use the resource Deployment Plan on Image Streamer
Resource not implemented / Could not find the Image_streamer_deployment_plan type
Use Oneview_server_profile with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_server_profile resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use connection template with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the connection template resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Use Oneview_san_manager with API 300 on the Synergy and C7000 hardware variants
1- Create a login file with api_version = 300 and hardware_variant = "C7000" or "Synergy"
2- Create a manifest in which I call the Oneview_san_manager resource
Should use the API 300 of the chosen hardware variant to perform any actions
Uses the API 200 of the C7000 hardware variant to perform all actions.
Currently the API 300 of OneView is not supported by this module. Since the oneview-sdk gem has released support for API 300, it should also be added here.
Use the Build Plan resource from this module
-Puppet module for HPE OneView Version: 2.2.0
-OneView SDK Version: 3.1.0
-OneView Appliance Version: 3.0
-OneView Client API Version: 300
-Puppet Version: 4.8
-Ruby Version: 2.2.6
-Platform: Windows/Linux
Try to call the resource Image_streamer_build_plan
To be able to use the resource Build Plan on Image Streamer
Resource not implemented / Could not find the Image_streamer_build_plan type
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.
