Skip to content

Commit d8e7173

Browse files
felixs88felixs88
authored
Release 5.1.0 (#366)
* Release 5.1.0
1 parent 14064b2 commit d8e7173

34 files changed

+2563
-179
lines changed

‎CHANGELOG.rst

+43
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,49 @@ Dell EMC OpenManage Ansible Modules Release Notes
55
.. contents:: Topics
66

77

8+
v5.1.0
9+
======
10+
11+
Release Summary
12+
---------------
13+
14+
Support for OpenManage Enterprise Modular server interface management.
15+
16+
Minor Changes
17+
-------------
18+
19+
- ome_application_network_address - The module is enhanced to support check mode and idempotency.
20+
- ome_device_info - The module is enhanced to return a blank list when devices or baselines are not present in the system.
21+
- ome_firmware_baseline_compliance_info - The module is enhanced to return a blank list when devices or baselines are not present in the system.
22+
- ome_firmware_baseline_info - The module is enhanced to return a blank list when devices or baselines are not present in the system.
23+
- ome_identity_pool - The iSCSI Initiator and Initiator IP Pool attributes are not mandatory to create an identity pool. (https://github.com/dell/dellemc-openmanage-ansible-modules/issues/329)
24+
- ome_identity_pool - The module is enhanced to support check mode and idempotency. (https://github.com/dell/dellemc-openmanage-ansible-modules/issues/328)
25+
- ome_template_identity_pool - The module is enhanced to support check mode and idempotency.
26+
- redfish_event_subscription - The module is enhanced to support check mode and idempotency.
27+
28+
Bugfixes
29+
--------
30+
31+
- idrac_firmware - Issue (220130) The socket.timout issue that occurs during the wait_for_job_completion() job is fixed.
32+
33+
Known Issues
34+
------------
35+
36+
- idrac_user - Issue(192043) The module may error out with the message ``unable to perform the import or export operation because there are pending attribute changes or a configuration job is in progress``. Wait for the job to complete and run the task again.
37+
- ome_application_alerts_smtp - Issue(212310) - The module does not provide a proper error message if the destination_address is more than 255 characters.
38+
- ome_application_alerts_syslog - Issue(215374) - The module does not provide a proper error message if the destination_address is more than 255 characters.
39+
- ome_device_local_access_configuration - Issue(215035) - The module reports ``Successfully updated the local access setting`` if an unsupported value is provided for the parameter timeout_limit. However, this value is not actually applied on OpenManage Enterprise Modular.
40+
- ome_device_local_access_configuration - Issue(217865) - The module does not display a proper error message if an unsupported value is provided for the user_defined and lcd_language parameters.
41+
- ome_device_network_services - Issue(212681) - The module does not provide a proper error message if unsupported values are provided for the parameters- port_number, community_name, max_sessions, max_auth_retries, and idle_timeout.
42+
- ome_device_power_settings - Issue(212679) - The module errors out with the following message if the value provided for the parameter ``power_cap`` is not within the supported range of 0 to 32767, ``Unable to complete the request because PowerCap does not exist or is not applicable for the resource URI.``
43+
- ome_smart_fabric_uplink - Issue(186024) - The module does not allow the creation of multiple uplinks of the same name even though it is supported by OpenManage Enterprise Modular. If an uplink is created using the same name as an existing uplink, the existing uplink is modified.
44+
45+
New Modules
46+
-----------
47+
48+
- dellemc.openmanage.ome_server_interface_profile_info - Retrieves the information of server interface profile on OpenManage Enterprise Modular.
49+
- dellemc.openmanage.ome_server_interface_profiles - Configures server interface profiles on OpenManage Enterprise Modular.
50+
851
v5.0.1
952
======
1053

‎README.md

+12-13
Original file line numberDiff line numberDiff line change
@@ -38,19 +38,18 @@ Install the collection from the github repository using the latest commit on the
3838
**By default, SSL certificate validation is enabled in all modules to enforce secure communication.**
3939

4040
### Enable SSL certificate validation
41-
To enable SSL certificate validation, perform the following steps:
42-
* Generate and upload the custom or organizational CA signed certificates on the iDRACs, OpenManage Enterprise, and OpenManage Enterprise-Modular, as required.
43-
* For iDRAC, see the section `SSL server certificates` in the `Integrated Dell Remote Access Controller Users Guide`.
44-
* For OpenManage Enterprise, see the section `Security Certificates` in the `OpenManage Enterprise Users Guide`.
45-
* For OpenManage Enterprise Modular, see the section `Managing certificates` in the `OpenManage Enterprise Modular for PowerEdge MX7000 Chassis Users Guide`.
46-
* After you have uploaded the custom or organizational CA signed certificate to iDRAC or OME or OME-M, you must have the CA file or bundle available on your Ansible controller. For example, copy the CA file or bundle in the following path: /usr/share/ssl-certs/
47-
> **_NOTE_**: Ensure that the user running the Ansible modules has permission to access the certificate file or bundle.
48-
* You can then use either of the following methods to specify the custom or organization CA certificate file or bundle path to the module:
49-
* In your playbook tasks, set the `ca_path` argument to the file path of your custom or organization CA certificate file or bundle.
50-
```ca_path: /usr/share/ssl-certs/ca-cert.pem```
51-
* Use any of the following environment variables to specify the custom or organization CA certificate file or bundle path. The modules reads the environment variable in the following order of preference: ```REQUESTS_CA_BUNDLE```, ```CURL_CA_BUNDLE```, ```OMAM_CA_BUNDLE```.
52-
> **_NOTE_**: Use the following command to set the environment variable with the custom or organization CA certificate file or bundle:
53-
<br>```export REQUESTS_CA_BUNDLE=/usr/share/ssl-certs/ca-cert.pem```
41+
- Generate and upload the custom or organizational CA signed certificates on the iDRACs, OpenManage Enterprise, and OpenManage Enterprise-Modular, as required.
42+
- For iDRAC, see the section `SSL server certificates` in the `Integrated Dell Remote Access Controller Users Guide`.
43+
- For OpenManage Enterprise, see the section `Security Certificates` in the `OpenManage Enterprise Users Guide`.
44+
- For OpenManage Enterprise Modular, see the section `Managing certificates` in the `OpenManage Enterprise Modular for PowerEdge MX7000 Chassis Users Guide`.
45+
- After you have uploaded the custom or organizational CA signed certificate to iDRAC or OME or OME-M, you must have the CA file or bundle available on your Ansible controller. For example, copy the CA file or bundle in the following path: /usr/share/ssl-certs/
46+
> **_NOTE_**: Ensure that the user running the Ansible modules has permission to access the certificate file or bundle.
47+
- You can then use either of the following methods to specify the custom or organization CA certificate file or bundle path to the module:
48+
- In your playbook tasks, set the `ca_path` argument to the file path of your custom or organization CA certificate file or bundle.
49+
```ca_path: /usr/share/ssl-certs/ca-cert.pem```
50+
- Use any of the following environment variables to specify the custom or organization CA certificate file or bundle path. The modules reads the environment variable in the following order of preference: ```REQUESTS_CA_BUNDLE```, ```CURL_CA_BUNDLE```, ```OMAM_CA_BUNDLE```.
51+
> **_NOTE_**: Use the following command to set the environment variable with the custom or organization CA certificate file or bundle:
52+
```export REQUESTS_CA_BUNDLE=/usr/share/ssl-certs/ca-cert.pem```
5453

5554
### Ignore SSL certificate validation
5655
It is common to run a test environment without a proper SSL certificate configuration. To disable the certificate validation for a module, set the validate_certs module argument to ```False``` in the playbook.

‎changelogs/changelog.yaml

+61-1
Original file line numberDiff line numberDiff line change
@@ -569,4 +569,64 @@ releases:
569569
not within the supported range of 0 to 32767, ``Unable to complete the request
570570
because PowerCap does not exist or is not applicable for the resource URI.``
571571
release_summary: Support to provide custom or organizational CA signed certificate for SSL validation from the environment variable.
572-
release_date: '2022-02-11'
572+
release_date: '2022-02-11'
573+
5.1.0:
574+
changes:
575+
bugfixes:
576+
- idrac_firmware - Issue (220130) The socket.timout issue that occurs
577+
during the wait_for_job_completion() job is fixed.
578+
minor_changes:
579+
- ome_identity_pool - The module is enhanced to support check mode and
580+
idempotency.
581+
(https://github.com/dell/dellemc-openmanage-ansible-modules/issues/328)
582+
- ome_template_identity_pool - The module is enhanced to support check
583+
mode and idempotency.
584+
- ome_application_network_address - The module is enhanced to support
585+
check mode and idempotency.
586+
- redfish_event_subscription - The module is enhanced to support check
587+
mode and idempotency.
588+
- ome_identity_pool - The iSCSI Initiator and Initiator IP Pool
589+
attributes are not mandatory to create an identity pool.
590+
(https://github.com/dell/dellemc-openmanage-ansible-modules/issues/329)
591+
- ome_device_info - The module is enhanced to return a blank list when
592+
devices or baselines are not present in the system.
593+
- ome_firmware_baseline_compliance_info - The module is enhanced to
594+
return a blank list when devices or baselines are not present in the system.
595+
- ome_firmware_baseline_info - The module is enhanced to return a blank
596+
list when devices or baselines are not present in the system.
597+
known_issues:
598+
- ome_device_local_access_configuration - Issue(217865) - The module does not
599+
display a proper error message if an unsupported value is provided for the
600+
user_defined and lcd_language parameters.
601+
- ome_device_local_access_configuration - Issue(215035) - The module reports
602+
``Successfully updated the local access setting`` if an unsupported value is
603+
provided for the parameter timeout_limit. However, this value is not
604+
actually applied on OpenManage Enterprise Modular.
605+
- ome_device_network_services - Issue(212681) - The module does not provide a
606+
proper error message if unsupported values are provided for the parameters-
607+
port_number, community_name, max_sessions, max_auth_retries, and idle_timeout.
608+
- ome_application_alerts_syslog - Issue(215374) - The module does not provide a
609+
proper error message if the destination_address is more than 255 characters.
610+
- ome_application_alerts_smtp - Issue(212310) - The module does not provide a
611+
proper error message if the destination_address is more than 255 characters.
612+
- idrac_user - Issue(192043) The module may error out with the message ``unable
613+
to perform the import or export operation because there are pending attribute
614+
changes or a configuration job is in progress``. Wait for the job to complete
615+
and run the task again.
616+
- ome_smart_fabric_uplink - Issue(186024) - The module does not allow the creation
617+
of multiple uplinks of the same name even though it is supported by OpenManage
618+
Enterprise Modular. If an uplink is created using the same name as an existing
619+
uplink, the existing uplink is modified.
620+
- ome_device_power_settings - Issue(212679) - The module errors out with the
621+
following message if the value provided for the parameter ``power_cap`` is
622+
not within the supported range of 0 to 32767, ``Unable to complete the request
623+
because PowerCap does not exist or is not applicable for the resource URI.``
624+
release_summary: Support for OpenManage Enterprise Modular server interface management.
625+
modules:
626+
- description: Configures server interface profiles on OpenManage Enterprise Modular.
627+
name: ome_server_interface_profiles
628+
namespace: ''
629+
- description: Retrieves the information of server interface profile on OpenManage Enterprise Modular.
630+
name: ome_server_interface_profile_info
631+
namespace: ''
632+
release_date: '2022-02-24'

‎docs/README.md

+2
Original file line numberDiff line numberDiff line change
@@ -71,6 +71,8 @@ OpenManage Ansible Modules simplifies and automates provisioning, deployment, an
7171
- [ome_network_vlan_info](modules/ome_network_vlan_info.rst)
7272
- [ome_powerstate](modules/ome_powerstate.rst)
7373
- [ome_profile](modules/ome_profile.rst)
74+
- [ome_server_interface_profile_info](modules/ome_server_interface_profile_info.rst)
75+
- [ome_server_interface_profiles](modules/ome_server_interface_profiles.rst)
7476
- [ome_smart_fabric](modules/ome_smart_fabric.rst)
7577
- [ome_smart_fabric_uplink](modules/ome_smart_fabric_uplink.rst)
7678
- [ome_template](modules/ome_template.rst)

‎docs/modules/ome_server_interface_profile_info.rst

+145
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,145 @@
1+
.. _ome_server_interface_profile_info_module:
2+
3+
4+
ome_server_interface_profile_info -- Retrieves the information of server interface profile on OpenManage Enterprise Modular.
5+
============================================================================================================================
6+
7+
.. contents::
8+
:local:
9+
:depth: 1
10+
11+
12+
Synopsis
13+
--------
14+
15+
This module allows to retrieves the information of server interface profile on OpenManage Enterprise Modular.
16+
17+
18+
19+
Requirements
20+
------------
21+
The below requirements are needed on the host that executes this module.
22+
23+
- python >= 3.8.6
24+
25+
26+
27+
Parameters
28+
----------
29+
30+
device_id (optional, list, None)
31+
The ID of the device.
32+
33+
*device_id* is mutually exclusive with *device_service_tag*.
34+
35+
36+
device_service_tag (optional, list, None)
37+
The service tag of the device.
38+
39+
*device_service_tag* is mutually exclusive with *device_id*.
40+
41+
42+
hostname (True, str, None)
43+
OpenManage Enterprise Modular IP address or hostname.
44+
45+
46+
username (True, str, None)
47+
OpenManage Enterprise Modular username.
48+
49+
50+
password (True, str, None)
51+
OpenManage Enterprise Modular password.
52+
53+
54+
port (optional, int, 443)
55+
OpenManage Enterprise Modular HTTPS port.
56+
57+
58+
validate_certs (optional, bool, True)
59+
If ``False``, the SSL certificates will not be validated.
60+
61+
Configure ``False`` only on personally controlled sites where self-signed certificates are used.
62+
63+
Prior to collection version ``5.0.0``, the *validate_certs* is ``False`` by default.
64+
65+
66+
ca_path (optional, path, None)
67+
The Privacy Enhanced Mail (PEM) file that contains a CA certificate to be used for the validation.
68+
69+
70+
timeout (optional, int, 30)
71+
The socket level timeout in seconds.
72+
73+
74+
75+
76+
77+
Notes
78+
-----
79+
80+
.. note::
81+
- Run this module from a system that has direct access to OpenManage Enterprise Modular.
82+
- This module supports ``check_mode``.
83+
84+
85+
86+
87+
Examples
88+
--------
89+
90+
.. code-block:: yaml+jinja
91+
92+
93+
---
94+
- name: Retrieves the server interface profiles of all the device using device ID.
95+
dellemc.openmanage.ome_server_interface_profile_info:
96+
hostname: "192.168.0.1"
97+
username: "username"
98+
password: "password"
99+
ca_path: "/path/to/ca_cert.pem"
100+
device_id:
101+
- 10001
102+
- 10002
103+
104+
- name: Retrieves the server interface profiles of all the device using device service tag.
105+
dellemc.openmanage.ome_server_interface_profile_info:
106+
hostname: "192.168.0.1"
107+
username: "username"
108+
password: "password"
109+
ca_path: "/path/to/ca_cert.pem"
110+
device_service_tag:
111+
- 6GHH6H2
112+
- 6KHH6H3
113+
114+
115+
116+
Return Values
117+
-------------
118+
119+
msg (on success, str, Successfully retrieved the server interface profile information.)
120+
Overall status of the server interface profile information.
121+
122+
123+
server_profiles (success, list, [AnsibleMapping([('BondingTechnology', 'LACP'), ('Id', '6KZK6K2'), ('ServerInterfaceProfile', [AnsibleMapping([('FabricId', '1ea6bf64-3cf0-4e06-a136-5046d874d1e7'), ('Id', 'NIC.Mezzanine.1A-1-1'), ('NativeVLAN', 0), ('Networks', [AnsibleMapping([('CreatedBy', 'system'), ('CreationTime', '2018-11-27 10:22:14.140'), ('Description', 'VLAN 1'), ('Id', 10001), ('InternalRefNWUUId', 'add035b9-a971-400d-a3fa-bb365df1d476'), ('Name"', 'VLAN 1'), ('Type', 2), ('UpdatedBy', None), ('UpdatedTime', '2018-11-27 10:22:14.140'), ('VlanMaximum', 1), ('VlanMinimum', 1)])]), ('NicBonded', True), ('OnboardedPort', '59HW8X2:ethernet1/1/1')]), AnsibleMapping([('FabricId', '3ea6be04-5cf0-4e05-a136-5046d874d1e6'), ('Id', 'NIC.Mezzanine.1A-2-1'), ('NativeVLAN', 0), ('Networks', [AnsibleMapping([('CreatedBy', 'system'), ('CreationTime', '2018-09-25 14:46:12.374'), ('Description', None), ('Id', 10155), ('InternalRefNWUUId', 'f15a36b6-e3d3-46b2-9e7d-bf9cd66e180d'), ('Name', 'jagvlan'), ('Type', 1), ('UpdatedBy', None), ('UpdatedTime', '2018-09-25 14:46:12.374'), ('VlanMaximum', 143), ('VlanMinimum', 143)])]), ('NicBonded', False), ('OnboardedPort', '6H7J6Z2:ethernet1/1/1')])])])])
124+
Returns the information of collected server interface profile information.
125+
126+
127+
error_info (on HTTP error, dict, AnsibleMapping([('error', AnsibleMapping([('code', 'Base.1.0.GeneralError'), ('message', 'A general error has occurred. See ExtendedInfo for more information.'), ('@Message.ExtendedInfo', [AnsibleMapping([('MessageId', 'GEN1234'), ('RelatedProperties', []), ('Message', 'Unable to process the request because an error occurred.'), ('MessageArgs', []), ('Severity', 'Critical'), ('Resolution', 'Retry the operation. If the issue persists, contact your system administrator.')])])]))]))
128+
Details of the HTTP Error.
129+
130+
131+
132+
133+
134+
Status
135+
------
136+
137+
138+
139+
140+
141+
Authors
142+
~~~~~~~
143+
144+
- Felix Stephen (@felixs88)
145+

0 commit comments

Comments
 (0)