Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lpar integration - installation on LPAR as nodes #241

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

sandisamp
Copy link

Create integration of LPAR into playbook - 6_create_nodes

Accordingly tasks and roles have been created.

Note: This PR is a work in progress. Created for initial reviews and not to make the review process too long. Will update detailed description when PR is ready.

Copy link
Collaborator

@AmadeusPodvratnik AmadeusPodvratnik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @sandisamp , thx for the PR. Following additonal comments:

  • There is a description missing what support you are adding (lpar).
  • You need to document what your are supporting (Classic vs. DPM, fcp device, etc).
  • You have additional variables defined which needed to be explained and described.
  • In your boot_LPAR task I do not see a interface name and you are supporting ipv4 only ... is this correct?

playbooks/5_setup_bastion.yaml Outdated Show resolved Hide resolved
playbooks/5_setup_bastion.yaml Outdated Show resolved Hide resolved
playbooks/5_setup_bastion.yaml Outdated Show resolved Hide resolved
@sandisamp sandisamp changed the title [WIP] Lpar integration - installation on LPAR as nodes Lpar integration - installation on LPAR as nodes Mar 27, 2024
Copy link
Collaborator

@AmadeusPodvratnik AmadeusPodvratnik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @sandisamp Thx for the lpar. Pls add the description of the lpar to section 3 (Step 3: Set Variables (host_vars)) for the time being.
In addition pls add a section to the Readme.md (New features) and add your lpar support to it.

playbooks/5_setup_bastion.yaml Show resolved Hide resolved
playbooks/5_setup_bastion.yaml Outdated Show resolved Hide resolved
playbooks/5_setup_bastion.yaml Outdated Show resolved Hide resolved
playbooks/5_setup_bastion.yaml Outdated Show resolved Hide resolved
playbooks/5_setup_bastion.yaml Outdated Show resolved Hide resolved
roles/boot_LPAR/tasks/main.yaml Outdated Show resolved Hide resolved
roles/boot_LPAR/tasks/main.yaml Outdated Show resolved Hide resolved
Copy link
Collaborator

@AmadeusPodvratnik AmadeusPodvratnik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@sandisamp Thank you for the PR. Pls see my comments.

roles/boot_LPAR/tasks/main.yaml Outdated Show resolved Hide resolved
roles/boot_LPAR/tasks/main.yaml Outdated Show resolved Hide resolved
playbooks/6_create_nodes.yaml Show resolved Hide resolved
playbooks/5_setup_bastion.yaml Outdated Show resolved Hide resolved
@sandisamp sandisamp force-pushed the LPAR_integration branch 2 times, most recently from df749d5 to 7462195 Compare May 10, 2024 06:57
Signed-off-by: Sanidhya <sanidhya@Sanidhyas-MacBook-Pro.local>
@@ -55,6 +55,7 @@
## 5 - Bastion
**Variable Name** | **Description** | **Example**
:--- | :--- | :---
**env.bastion.installation_type** | Can be of type kvm or lpar. Some packages will be ignored for installation in case of lpar based installation. | kvm
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is the installation_type variable defined under "env.bastion.installation_type" and not under "env.installation_type" ?
If enabled, bootstrap, control nodes and compute node will be installed in LPAR mode.

include_role:
name: check_for_lpar_nodes
loop:
- bootstrap
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we use a KVM guest as bootstrap, not an LPAR ?

playbooks/5_setup_bastion.yaml Outdated Show resolved Hide resolved
ansible.builtin.service:
name: NetworkManager
state: restarted
block:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This patch is not required anymore.
We use RHEL 9 as default OS.

ansible.builtin.service:
name: NetworkManager
state: restarted
tags: dns, resolv
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This patch is not required anymore.
We use RHEL 9 as default OS.

@@ -39,7 +39,7 @@
tags: lpar_check
stat:
path: "{{ inventory_dir }}/host_vars/{{ env.z.lpar1.hostname }}.yaml"
when: env.z.lpar1.hostname is defined
when: env.z.lpar1.create == True
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is this changed ?

@@ -155,10 +163,10 @@
- client.crt
- client.key
- ta.key
when: env.setup_openvpn == True and env.z.high_availability == True
when: env.z.high_availability == True and env.bastion.installation_type|lower != "zvm" and env.bastion.installation_type|lower != "lpar"
roles:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is" env.setup_openvpn == True" removed from the "when" check ?

loop:
- bootstrap
- compute
- control
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not see an error check ?
What happen if bootstrap install fails ?
Will the creation of compute nodes and control nodes continue ?


- name: Undefine bootstrap. Expect ignored errors if bootstrap is already undefined.
tags: create_nodes, teardown_bootstrap
community.libvirt.virt:
name: "{{ env.cluster.nodes.bootstrap.vm_name }}"
command: undefine
ignore_errors: true
<<<<<<< HEAD
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bad patch !
Merge conflicts are not resolved !!!!!


>>>>>>> 077c676 (Revert "Deleting entries related to Bootstrap in Haproxy post its del… (#255))
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bad patch !!
Resolve merge conflicts correctly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants