Skip to content

IBM/ansible-power-vios

Repository files navigation

IBM Power Systems VIOS Collection

Scope

The IBM Power Systems VIOS collection provides modules that can be used to manage configurations and deployments of Power VIOS systems. The collection content helps to include workloads on Power platforms as part of an enterprise automation strategy through the Ansible ecosystem.

The IBM Power Systems VIOS collection is included as an upstream collection under the Ansible Content for IBM Power Systems umbrella of community content.

Usage

This repository contains some example best practices for open source repositories:

Requirements

Platforms

  • VIOS 2.2.5+
  • VIOS 3.1.0+

Ansible

  • Requires Ansible 2.14 or newer
  • For help installing Ansible, refer to the Installing Ansible section of the Ansible Documentation
  • For help installing the ibm.power_vios collection, refer to the install page of this project

ansible user for VIOS

  • Modules included in this collection require administrator rights to run.
  • It is recommended to create an ansible user with the proper level of privilege on the VIOS like this:
  • command(1): oem_setup_env
  • command(2): mkuser roles=PAdmin,CacheAdm,FSAdmin,pkgadm default_roles=PAdmin,CacheAdm,FSAdmin,pkgadm ansible
  • sudoers-rule for the Ansible user: ansible ALL=(ALL), NOPASSWD: ALL
  • To connect to the VIOS using this ansible user, specify user: ansible in the playbook or ansible_user=ansible in the inventory.

Authentication:

  • echo "ssh_ssh_pub_key" >> /home/ansible/.ssh/authorized_keys

Python

  • Requires Python 3.9 or newer
  • To install (or upgrade) Python on VIOS, you must first configure DNF. As part of DNF installation, Python3 will be installed by default
  • After setting up and installing DNF, you may update all the packages to the latest level using the dnf update command

Resources

Documentation of modules is generated on GitHub Pages.

Question, Issue or Contribute

If you have any questions or issues you can create a new issue here.

Pull requests are very welcome! Make sure your patches are well tested. Ideally create a topic branch for every separate change you make. For example:

  1. Fork the repo
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request

License & Authors

If you would like to see the detailed LICENSE click here.

Copyright:: 2020- IBM, Inc

This program is free software: you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation, either version 3 of the License, or
(at your option) any later version.

This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
GNU General Public License for more details.

You should have received a copy of the GNU General Public License
along with this program.  If not, see <https://www.gnu.org/licenses/>.

Authors: