inspur sm Collection

This repo contains the inspur.sm Ansible Collection. Inspur server supports ansible management device,Basic management of the server based on restful interface. Collections functionality will migrate to the inspur.ispim collection, head over to the new collection.

Tested with Ansible

Tested with the current Ansible 2.10 releases and the current development version of Ansible. Ansible versions before 2.10.0 are not supported.

External requirements

Circumstance instruction: Ansible module is suitable for ansible version 2.10

Main steps:

Install Ansible 2.10 Install inspursmsdk

Thes modules require the following to be installed on the control node:

• Python 3.7 or later
• Ansible 2.10 or later
• [Inspur support] inspursmsdk 1.5.0 or later

Included content

Please check the included content on the Ansible Galaxy page for this collection

Using this collection

Before using the General community collection, you need to install the collection with the ansible-galaxy CLI:

ansible-galaxy collection install inspur.sm

You can also include it in a requirements.yml file and install it via ansible-galaxy collection install -r requirements.yml using the format:

collections:
- name: inspur.sm

See Ansible Using collections for more details.

Contributing to this collection

If you want to develop new content for this collection or improve what is already here, the easiest way to work on the collection is to clone it into one of the configured COLLECTIONS_PATH, and work on it there.

You can find more information in the developer guide for collections, and in the Ansible inspur.sm Guide.

Running tests

See here.

Communication

wangbaoshan@inspur.com

Publishing New Version

Basic instructions without release branches:

1. Create changelogs/fragments/<version>.yml with release_summary: section (which must be a string, not a list).
2. Run antsibull-changelog release --collection-flatmap yes
3. Make sure CHANGELOG.rst and changelogs/changelog.yaml are added to git, and the deleted fragments have been removed.
4. Tag the commit with <version>. Push changes and tag to the main repository.

Release notes

See the changelog.

Roadmap

See this issue for information on releasing, versioning and deprecation.

In general, we plan to release a major version every year, and minor versions every three months. Major versions can contain breaking changes, while minor versions only contain new features and bugfixes.

More information

• Ansible Collection overview
• Ansible User guide
• Ansible Developer guide
• Ansible Community code of conduct

Licensing

GNU General Public License v3.0 or later.

See COPYING to see the full text.