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

Readd validate inventory and display plan, remove os_images and release_images and set default installer to agent based. #307

Merged

Conversation

nocturnalastro
Copy link
Collaborator

No description provided.

@nocturnalastro nocturnalastro changed the title Readd validate inventory Readd validate inventory and display plan, remove os_images and release_images and set default installer to agent based. Mar 18, 2024
@nocturnalastro nocturnalastro force-pushed the readd_validate_inventory branch from bec54ea to 8c5e110 Compare March 21, 2024 16:37
@nocturnalastro nocturnalastro mentioned this pull request Mar 25, 2024
@nocturnalastro nocturnalastro force-pushed the readd_validate_inventory branch 3 times, most recently from 5af284e to 54966a9 Compare March 26, 2024 13:05
@nocturnalastro nocturnalastro force-pushed the readd_validate_inventory branch from 54966a9 to c02ef69 Compare March 26, 2024 15:23
arjuhe
arjuhe previously approved these changes Mar 26, 2024
Copy link
Collaborator

@arjuhe arjuhe left a comment

Choose a reason for hiding this comment

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

LGTM

@nocturnalastro nocturnalastro marked this pull request as ready for review March 26, 2024 15:26
@nocturnalastro nocturnalastro requested a review from a team as a code owner March 26, 2024 15:26
@arjuhe arjuhe dismissed their stale review March 26, 2024 15:28

testing review inside single commit

Copy link
Collaborator

@arjuhe arjuhe left a comment

Choose a reason for hiding this comment

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

LGTM.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Just add these direct to the requirements.txt. It would make the install process a little easier.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I have removed the requirements file and instead I've just put the instructions in the README

Copy link
Collaborator

@arjuhe arjuhe left a comment

Choose a reason for hiding this comment

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

LGTM

@nocturnalastro nocturnalastro force-pushed the readd_validate_inventory branch from c02ef69 to 97e9139 Compare March 27, 2024 18:31
@@ -595,17 +627,6 @@ The basic network configuration of the inventory for the fully bare metal deploy
bmc_address: 172.30.10.7
# ...
```
## Additional Partition Deployment

For OCP 4.8+ deployments you can set partitions if required on the nodes. You do this by adding the snippet below to the node definition. Please ensure you provide the correct label and size(MiB) for the additional partitions you want to create. The device can either be the drive in which RHCOS image needs to be installed or it can be any additional drive on the node that requires partitioning. In the case that the device is equal to the host's `installation_disk_path` then a partition will be added defined by `disks_rhcos_root`. All additional partitions must be added under `extra_partitions` key as per the example below.
Copy link
Collaborator

Choose a reason for hiding this comment

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

One sentance per line here.

@@ -651,7 +672,7 @@ You must have these services when using PXE deployment
vendor: pxe
bmc_address: "nfvpe-21.oot.lab.eng.bos.redhat.com"
bmc_port: 8082

```
> **Note**: that the BMCs of the nodes in the cluster must be routable from the bastion host and the HTTP Store must be routable from the BMCs
Copy link
Collaborator

Choose a reason for hiding this comment

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

period missing


## Day 2 nodes

Day 2 nodes are added to an existing cluster. The reason why the installation of day 2 nodes is built into the main path of our automation, is that for assisted installer day 2 nodes can be on a different L2 network which the main flow does not allow.
Copy link
Collaborator

Choose a reason for hiding this comment

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

sentence per line

[edited to correct spelling]


## Additional Partition Deployment

For OCP 4.8+ deployments you can set partitions if required on the nodes. You do this by adding the snippet below to the node definition. Please ensure you provide the correct label and size(MiB) for the additional partitions you want to create. The device can either be the drive in which RHCOS image needs to be installed or it can be any additional drive on the node that requires partitioning. In the case that the device is equal to the host's `installation_disk_path` then a partition will be added defined by `disks_rhcos_root`. All additional partitions must be added under `extra_partitions` key as per the example below.
Copy link
Collaborator

Choose a reason for hiding this comment

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

sentence per line

[edited to correct spelling]

hack/README.md Outdated
pip install semver beautifulsoup4
```

## Useage
Copy link
Collaborator

Choose a reason for hiding this comment

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

spelling

@nocturnalastro nocturnalastro force-pushed the readd_validate_inventory branch from af5753d to 4a5b8b2 Compare March 28, 2024 13:26
Copy link
Collaborator

@arjuhe arjuhe left a comment

Choose a reason for hiding this comment

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

Thanks LGTM

@arjuhe arjuhe merged commit 874b98a into redhat-partner-solutions:main Mar 28, 2024
2 of 3 checks passed
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.

2 participants