Allow user to set disk size for workers easily in libvirt provider

[tareqalayan]

Currently workers comes with 16GB of disk and there is no way to set the size of worker.
However for master it can be set by adding size = 42949672960 in the file:

installer/data/data/libvirt/main.tf

Line 31 in b5dbb46

resource "libvirt_volume" "master" {

Version

$ openshift-install version
<your output here>

Platform:

What happened?

Enter text here.
See the troubleshooting documentation for ideas about what information to collect.
For example, if the installer fails to create resources, attach the relevant portions of your .openshift_install.log.

What you expected to happen?

Enter text here.

How to reproduce it (as minimally and precisely as possible)?

$ your-commands-here

Anything else we need to know?

Enter text here.

References

• enter text here.

[zeenix]

You can do it through manifests. See #2111 for the discrepancy between how it's handled for master and worker.

/close

[openshift-ci-robot]

@zeenix: Closing this issue.

In response to this:

You can do it through manifests. See #2111 for the discrepancy between how it's handled for master and worker.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[zeenix]

/label platform/libvirt

[cynepco3hahue]

@zeenix You can not set the volume size, only the memory, and VCPU, it the reason for openshift/cluster-api-provider-libvirt#175, but anyway this issues should be open for the https://github.com/openshift/cluster-api-provider-libvirt/ repo

[AsherShoshan]

@zeenix - Please reopen the issue

[zeenix]

Oh right, i missed that fact. :) A related issue: #2112

/reopen

[openshift-ci-robot]

@zeenix: Reopened this issue.

In response to this:

Oh right, i missed that fact. :) A related issue: #2112

/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jichenjc]

let me try whether I can fix it...

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci-robot]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.