-
Notifications
You must be signed in to change notification settings - Fork 51
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
To attach additional data volumes to nodes #212
To attach additional data volumes to nodes #212
Conversation
Makes sense. The requirement to add multiple volumes comes due to OCS and needs to be handled for both on-prem and off-prem |
Leet me know when you think this is functional. I will test it for you with ocs. |
I tested this change and it works. |
1059ccd
to
916c3d0
Compare
044f64c
to
25ad805
Compare
Updated the files to attach multiple volumes to the nodes. |
3a971eb
to
a8245be
Compare
@yussufsh Thank you for the suggestions. I have updated the changes. |
Expecting four mount points per worker node. [root@rdr-lbr48-c244-bastion-0 ~]# ssh core@worker-0 lsblk -a | grep 768 |
/approve Tip: we also mention in docs that the data_volume_size is in unit GB. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
cc - @bpradipt
@aishwaryabk the patch looks good. Just minor formatting comments and we should be good to go. |
Looks good. Tested latest changes. |
variables.tf
Outdated
@@ -96,6 +96,9 @@ variable "master" { | |||
# availability_zone = "" | |||
# optional fixed IPs | |||
# fixed_ips = [] | |||
# optional data volumes to master nodes | |||
# data_volume_size = 100 #Default volume size to be attached to the master nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Default volume size => Default volume size (in GB)
variables.tf
Outdated
@@ -109,6 +112,9 @@ variable "worker" { | |||
# availability_zone = "" | |||
# optional fixed IPs | |||
# fixed_ips = [] | |||
# optional data volumes to worker nodes | |||
# data_volume_size = 100 #Default volume size to be attached to the worker nodes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Default volume size => Default volume size (in GB)
docs/var.tfvars-doc.md
Outdated
@@ -76,6 +76,11 @@ bootstrap = {instance_type = "<bootstrap-compute-template>" | |||
master = {instance_type = "<master-compute-template>", image_id = "<image-uuid-rhcos>", "count" = 3, fixed_ips = ["<IPv4 address>", "<IPv4 address>", "<IPv4 address>"]} | |||
worker = {instance_type = "<worker-compute-template>", image_id = "<image-uuid-rhcos>", "count" = 2, fixed_ips = ["<IPv4 address>", "<IPv4 address>"]} | |||
``` | |||
To attach additional volumes to the master and worker nodes, use the optional `data_volume_count` and `data_volume_size` in master and worker variables. You can set the `data_volume_count` to any number depending on the number of volumes to be attached to each node. You can also change the `data_volume_size` as per your requirement (the `data_volume_size` is in unit GB). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about this?
To attach additional volumes to master or worker nodes, set the optional data_volume_count
key to the number of volumes that is to be attached and the data_volume_size
to the size (in GB) for each volume.
Signed-off-by: Aishwarya Kamat <aishwarya.kamat@ibm.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: aishwaryabk, bpradipt, yussufsh The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Please backport to release branches 4.6 and 4.7. |
It'll be backported. |
Signed-off-by: Aishwarya Kamat aishwarya.kamat@ibm.com