Skip to content

Commit 884382f

Browse files
jagadeeshnvjagadeeshnv
authored
Release 5.5.0 (#423)
* Release 5.5.0 * Update CI/CD Pipelines with latest Python and Ansible version coverage
1 parent 3bcb1b5 commit 884382f

27 files changed

+2001
-36
lines changed

‎.github/workflows/ansible-test.yml

+6-8
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ jobs:
1515
strategy:
1616
fail-fast: false
1717
matrix:
18-
ansible-version: [stable-2.11, stable-2.12]
18+
ansible-version: [stable-2.10, stable-2.11, stable-2.12, stable-2.13]
1919
steps:
2020
- name: Check out code
2121
uses: actions/checkout@v2
@@ -49,13 +49,11 @@ jobs:
4949
strategy:
5050
fail-fast: false
5151
matrix:
52-
python-version: [2.7, 3.8, 3.9]
53-
ansible-version: [stable-2.11, stable-2.12, devel]
52+
python-version: [3.8, 3.9, '3.10']
53+
ansible-version: [stable-2.11, stable-2.12, stable-2.13, devel]
5454
exclude:
55-
- ansible-version: devel
56-
python-version: 2.7
57-
- ansible-version: stable-2.12
58-
python-version: 2.7
55+
- ansible-version: stable-2.11
56+
python-version: '3.10'
5957

6058
steps:
6159
- name: Set up Python ${{ matrix.python-version }}
@@ -102,7 +100,7 @@ jobs:
102100
strategy:
103101
fail-fast: false
104102
matrix:
105-
ansible-version: [stable-2.11, stable-2.12, devel]
103+
ansible-version: [stable-2.11, stable-2.12, stable-2.13, devel]
106104

107105
steps:
108106
- name: Set up Python 3.8

‎CHANGELOG.rst

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

77

8+
v5.5.0
9+
======
10+
11+
Release Summary
12+
---------------
13+
14+
Support to generate certificate signing request, import, and export certificates on iDRAC.
15+
16+
Minor Changes
17+
-------------
18+
19+
- idrac_redfish_storage_controller - This module is updated to use the Job Service URL instead of Task Service URL for job tracking.
20+
- idrac_server_config_profile - This module is updated to use the Job Service URL instead of Task Service URL for job tracking.
21+
- redfish_firmware - This module is updated to use the Job Service URL instead of Task Service URL for job tracking.
22+
23+
Bugfixes
24+
--------
25+
26+
- idrac_server_config_profile - Issue(234817) – When an XML format is exported using the SCP, the module breaks while waiting for the job completion.
27+
- ome_application_console_preferences - Issue(224690) - The module does not display a proper error message when an unsupported value is provided for the parameters report_row_limit, email_sender_settings, and metric_collection_settings, and the value is applied on OpenManage Enterprise
28+
29+
Known Issues
30+
------------
31+
32+
- 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.
33+
- ome_application_alerts_smtp - Issue(212310) - The module does not provide a proper error message if the destination_address is more than 255 characters.
34+
- ome_application_alerts_syslog - Issue(215374) - The module does not provide a proper error message if the destination_address is more than 255 characters.
35+
- 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.
36+
- 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.
37+
- 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.
38+
- ome_device_power_settings - Issue(212679) - The module displays 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.``
39+
- ome_device_quick_deploy - Issue(216352) - The module does not display a proper error message if an unsupported value is provided for the ipv6_prefix_length and vlan_id parameters.
40+
- 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.
41+
42+
New Modules
43+
-----------
44+
45+
- dellemc.openmanage.idrac_certificates - Configure certificates for iDRAC.
46+
847
v5.4.0
948
======
1049

‎changelogs/changelog.yaml

+54-1
Original file line numberDiff line numberDiff line change
@@ -786,4 +786,57 @@ releases:
786786
because PowerCap does not exist or is not applicable for the resource URI.``
787787
release_summary: Support for export, import, and preview the Server Configuration
788788
Profile (SCP) configuration using Redfish and added support for check mode.
789-
release_date: '2022-05-26'
789+
release_date: '2022-05-26'
790+
5.5.0:
791+
changes:
792+
minor_changes:
793+
- redfish_firmware - This module is updated to use the Job Service URL instead of
794+
Task Service URL for job tracking.
795+
- idrac_redfish_storage_controller - This module is updated to use the Job Service URL
796+
instead of Task Service URL for job tracking.
797+
- idrac_server_config_profile - This module is updated to use the Job Service URL
798+
instead of Task Service URL for job tracking.
799+
bugfixes:
800+
- ome_application_console_preferences - Issue(224690) - The module does
801+
not display a proper error message when an unsupported value is provided
802+
for the parameters report_row_limit, email_sender_settings, and
803+
metric_collection_settings, and the value is applied on OpenManage Enterprise
804+
- idrac_server_config_profile - Issue(234817) – When an XML format is exported
805+
using the SCP, the module breaks while waiting for the job completion.
806+
known_issues:
807+
- ome_device_quick_deploy - Issue(216352) - The module does not display a
808+
proper error message if an unsupported value is provided for the
809+
ipv6_prefix_length and vlan_id parameters.
810+
- ome_device_local_access_configuration - Issue(217865) - The module does not
811+
display a proper error message if an unsupported value is provided for the
812+
user_defined and lcd_language parameters.
813+
- ome_device_local_access_configuration - Issue(215035) - The module reports
814+
``Successfully updated the local access setting`` if an unsupported value is
815+
provided for the parameter timeout_limit. However, this value is not
816+
actually applied on OpenManage Enterprise Modular.
817+
- ome_device_network_services - Issue(212681) - The module does not provide a
818+
proper error message if unsupported values are provided for the parameters-
819+
port_number, community_name, max_sessions, max_auth_retries, and idle_timeout.
820+
- ome_application_alerts_syslog - Issue(215374) - The module does not provide a
821+
proper error message if the destination_address is more than 255 characters.
822+
- ome_application_alerts_smtp - Issue(212310) - The module does not provide a
823+
proper error message if the destination_address is more than 255 characters.
824+
- idrac_user - Issue(192043) The module may error out with the message ``unable
825+
to perform the import or export operation because there are pending attribute
826+
changes or a configuration job is in progress``. Wait for the job to complete
827+
and run the task again.
828+
- ome_smart_fabric_uplink - Issue(186024) - The module does not allow the creation
829+
of multiple uplinks of the same name even though it is supported by OpenManage
830+
Enterprise Modular. If an uplink is created using the same name as an existing
831+
uplink, the existing uplink is modified.
832+
- ome_device_power_settings - Issue(212679) - The module displays the following
833+
message if the value provided for the parameter ``power_cap`` is not within
834+
the supported range of 0 to 32767, ``Unable to complete the request
835+
because PowerCap does not exist or is not applicable for the resource URI.``
836+
release_summary: Support to generate certificate signing request, import, and export
837+
certificates on iDRAC.
838+
modules:
839+
- description: Configure certificates for iDRAC.
840+
name: idrac_certificates
841+
namespace: ''
842+
release_date: '2022-06-29'

‎docs/CODE_OF_CONDUCT.md

+133
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,133 @@
1+
2+
# Contributor Covenant Code of Conduct
3+
4+
## Our Pledge
5+
6+
We as members, contributors, and leaders pledge to make participation in our
7+
community a harassment-free experience for everyone, regardless of age, body
8+
size, visible or invisible disability, ethnicity, sex characteristics, gender
9+
identity and expression, level of experience, education, socio-economic status,
10+
nationality, personal appearance, race, caste, color, religion, or sexual
11+
identity and orientation.
12+
13+
We pledge to act and interact in ways that contribute to an open, welcoming,
14+
diverse, inclusive, and healthy community.
15+
16+
## Our Standards
17+
18+
Examples of behavior that contributes to a positive environment for our
19+
community include:
20+
21+
* Demonstrating empathy and kindness toward other people
22+
* Being respectful of differing opinions, viewpoints, and experiences
23+
* Giving and gracefully accepting constructive feedback
24+
* Accepting responsibility and apologizing to those affected by our mistakes,
25+
and learning from the experience
26+
* Focusing on what is best not just for us as individuals, but for the overall
27+
community
28+
29+
Examples of unacceptable behavior include:
30+
31+
* The use of sexualized language or imagery, and sexual attention or advances of
32+
any kind
33+
* Trolling, insulting or derogatory comments, and personal or political attacks
34+
* Public or private harassment
35+
* Publishing others' private information, such as a physical or email address,
36+
without their explicit permission
37+
* Other conduct which could reasonably be considered inappropriate in a
38+
professional setting
39+
40+
## Enforcement Responsibilities
41+
42+
Community leaders are responsible for clarifying and enforcing our standards of
43+
acceptable behavior and will take appropriate and fair corrective action in
44+
response to any behavior that they deem inappropriate, threatening, offensive,
45+
or harmful.
46+
47+
Community leaders have the right and responsibility to remove, edit, or reject
48+
comments, commits, code, wiki edits, issues, and other contributions that are
49+
not aligned to this Code of Conduct, and will communicate reasons for moderation
50+
decisions when appropriate.
51+
52+
## Scope
53+
54+
This Code of Conduct applies within all community spaces, and also applies when
55+
an individual is officially representing the community in public spaces.
56+
Examples of representing our community include using an official e-mail address,
57+
posting via an official social media account, or acting as an appointed
58+
representative at an online or offline event.
59+
60+
## Enforcement
61+
62+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
63+
reported to the community leaders responsible for enforcement at
64+
[INSERT CONTACT METHOD].
65+
All complaints will be reviewed and investigated promptly and fairly.
66+
67+
All community leaders are obligated to respect the privacy and security of the
68+
reporter of any incident.
69+
70+
## Enforcement Guidelines
71+
72+
Community leaders will follow these Community Impact Guidelines in determining
73+
the consequences for any action they deem in violation of this Code of Conduct:
74+
75+
### 1. Correction
76+
77+
**Community Impact**: Use of inappropriate language or other behavior deemed
78+
unprofessional or unwelcome in the community.
79+
80+
**Consequence**: A private, written warning from community leaders, providing
81+
clarity around the nature of the violation and an explanation of why the
82+
behavior was inappropriate. A public apology may be requested.
83+
84+
### 2. Warning
85+
86+
**Community Impact**: A violation through a single incident or series of
87+
actions.
88+
89+
**Consequence**: A warning with consequences for continued behavior. No
90+
interaction with the people involved, including unsolicited interaction with
91+
those enforcing the Code of Conduct, for a specified period of time. This
92+
includes avoiding interactions in community spaces as well as external channels
93+
like social media. Violating these terms may lead to a temporary or permanent
94+
ban.
95+
96+
### 3. Temporary Ban
97+
98+
**Community Impact**: A serious violation of community standards, including
99+
sustained inappropriate behavior.
100+
101+
**Consequence**: A temporary ban from any sort of interaction or public
102+
communication with the community for a specified period of time. No public or
103+
private interaction with the people involved, including unsolicited interaction
104+
with those enforcing the Code of Conduct, is allowed during this period.
105+
Violating these terms may lead to a permanent ban.
106+
107+
### 4. Permanent Ban
108+
109+
**Community Impact**: Demonstrating a pattern of violation of community
110+
standards, including sustained inappropriate behavior, harassment of an
111+
individual, or aggression toward or disparagement of classes of individuals.
112+
113+
**Consequence**: A permanent ban from any sort of public interaction within the
114+
community.
115+
116+
## Attribution
117+
118+
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
119+
version 2.1, available at
120+
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
121+
122+
Community Impact Guidelines were inspired by
123+
[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
124+
125+
For answers to common questions about this code of conduct, see the FAQ at
126+
[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
127+
[https://www.contributor-covenant.org/translations][translations].
128+
129+
[homepage]: https://www.contributor-covenant.org
130+
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
131+
[Mozilla CoC]: https://github.com/mozilla/diversity
132+
[FAQ]: https://www.contributor-covenant.org/faq
133+
[translations]: https://www.contributor-covenant.org/translations

‎docs/COMMITTER_GUIDE.md

+41
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,41 @@
1+
<!--
2+
Copyright (c) 2022 Dell Inc., or its subsidiaries. All Rights Reserved.
3+
4+
Licensed under the GPL, Version 3.0 (the "License");
5+
you may not use this file except in compliance with the License.
6+
You may obtain a copy of the License at
7+
8+
https://www.gnu.org/licenses/gpl-3.0.txt
9+
-->
10+
11+
# Committer Guidelines
12+
13+
These are the guidelines for people with commit privileges on the GitHub repository. Committers act as members of the Core Team and not necessarily employees of Dell.
14+
15+
These guidelines apply to everyone and as Committers you have been given access to commit changes because you exhibit good judgment and have demonstrated your commitment to the vision of the project. We trust that you will use these privileges wisely and not abuse it.
16+
17+
If these privileges are abused in any way and the quality of the project is compromised, our trust will be diminished and you may be asked to not commit or lose these privileges all together.
18+
19+
## General Rules
20+
21+
### Don't
22+
23+
* Break the build.
24+
* Commit directly.
25+
* Compromise backward compatibility.
26+
* Disrespect your Community Team members. Help them grow.
27+
* Think it is someone elses job to test your code. Write tests for all the code you produce.
28+
* Forget to keep thing simple.
29+
* Create technical debt. Fix-in-place and make it the highest priority above everything else.
30+
31+
### Do
32+
33+
* Always follow the defined coding guideline
34+
* Keep the design of your software clean and maintainable.
35+
* Squash your commits, avoid merges.
36+
* Write tests for all your deliverables.
37+
* Automate everything.
38+
* Maintain a high code coverage, equal to or greater than 90%.
39+
* Keep an open communication with other Committers.
40+
* Ask questions.
41+
* Document your contributions and remember to keep it simple.

0 commit comments

Comments
 (0)