tripleo-operator-ansible/roles/tripleo_overcloud_node_conf...
Harald Jensås 570c886faa Bump molecule[test] to 3.5.x
CI is failing with conflictiong dependencies:

The conflict is caused by:
    molecule[test] 3.2.4 depends on pluggy<1.0 and >=0.7.1
    molecule[test] 3.2.3 depends on pluggy<1.0 and >=0.7.1
    molecule[test] 3.2.2 depends on pluggy<1.0 and >=0.7.1
    molecule[test] 3.2.1 depends on pluggy<1.0 and >=0.7.1
    molecule[test] 3.2.0 depends on pluggy<1.0 and >=0.7.1
    molecule[test] 3.2.0a2 depends on pluggy<1.0 and >=0.7.1
    molecule[test] 3.2.0a1 depends on pluggy<1.0 and >=0.7.1
    The user requested (constraint) pluggy===1.0.0

Let's try to use molecule[test] 3.5.x

Also set 'role_name' and 'namespace' in meta/main.yaml for
all roles. Namespace cannot container uppercase characters,
so computing fully qualified role name using author 'OpenStack'
does not work.

Also - fix tests in tripleo_overcloud_node_discover

Closes-Bug: #1943269
Change-Id: I1ab9764dd4d24c17c5ee2cb1f26fbc3c4b27d3d7
2021-09-23 15:33:06 +02:00
..
defaults Add ability to write scripts 2020-04-15 16:25:27 -06:00
meta Bump molecule[test] to 3.5.x 2021-09-23 15:33:06 +02:00
molecule/default Add ability to write scripts 2020-04-15 16:25:27 -06:00
tasks Ensure we export result only if we have an stdout 2020-05-15 15:43:20 +02:00
tests Add tripleo_overcloud_node_configure role 2020-01-28 12:58:57 -07:00
README.md Add tripleo_overcloud_node_configure role 2020-01-28 12:58:57 -07:00

README.md

tripleo_overcloud_node_configure

A role to run a node configuration.

Requirements

None.

Role Variables

  • tripleo_overcloud_node_configure_node_uuids: Baremetal Node UUIDs for the node(s) to be configured
  • tripleo_overcloud_node_configure_all_manageable: Configure all nodes currently in 'manageable' state
  • tripleo_overcloud_node_configure_deploy_kernel: Image with deploy kernel.
  • tripleo_overcloud_node_configure_deploy_ramdisk: Image with deploy ramdisk.
  • tripleo_overcloud_node_configure_instance_boot_option: Whether to set instances for booting from local hard drive (local) or network (netboot).
  • tripleo_overcloud_node_configure_root_device: Define the root device for nodes. Can be either a list of device names (without /dev) to choose from or one of two strategies: largest or smallest. For it to work this command should be run after the introspection.
  • tripleo_overcloud_node_configure_root_device_minimum_size: Minimum size (in GiB) of the detected root device. Used with --root-device.
  • tripleo_overcloud_node_configure_overwrite_root_device_hints: Whether to overwrite existing root device hints when --root-device is used.
  • tripleo_overcloud_node_configure_os_cloud: (String) (String) OS_CLOUD value to use when running the command. If tripleo_os_cloud is defined, it will be the default. Otherwise the default is ''. This variable takes precedence over tripleo_overcloud_node_configure_rc_file.
  • tripleo_overcloud_node_configure_rc_file: (String) (String) Path to the credential file to use. If tripleo_rc_file is defined, it will be the default. Default: "{{ ansible_env.HOME }}/stackrc"

NOTE: Please note that this command should be run against the undercloud so the OS_CLOUD or rc file variables should be set to use the 'undercloud' when calling this role. If you are not defining tripleo_os_cloud or tripleo_rc_file, stackrc will be used by default.

Output Variables

  • tripleo_overcloud_node_configure_output: (String) The command standard output.
  • tripleo_overcloud_node_configure_result: Ansible shell execution results

Dependencies

None.

Example Playbook

Example overcloud node configuration playbook

- hosts: undercloud
  gather_facts: true
  tasks:
    - name: Configure node
      import_role:
        name: tripleo_overcloud_node_configure

License

Apache-2.0