| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
@rhtyd this has some small conflicts with your PR #3797 |
Sorry, something went wrong.
|
@rhtyd Long size = _tmpltMgr.getTemplateSize(template.getId(), vm.getDataCenterId());
if (rootDisksize != null) {
rootDisksize = rootDisksize * 1024 * 1024 * 1024;
if (rootDisksize > size) {
s_logger.debug("Using root disk size of " + rootDisksize + " Bytes for volume " + name);
size = rootDisksize;
} else {
s_logger.debug("Using root disk size of " + size + " Bytes for volume " + name + "since specified root disk size of " + rootDisksize + " Bytes is smaller than template");
}
}
|
Sorry, something went wrong.
|
hm, I think you want milestone 4.14 for this one as well, right @weizhouapache ? |
Sorry, something went wrong.
@DaanHoogland I expect to add to 4.14. However, it require to build new systemvm template (and test it). |
Sorry, something went wrong.
|
Thanks per your comment assigned against 4.15 @weizhouapache |
Sorry, something went wrong.
|
@ustcweizhou do we want this for master/4.15+? Can you fix conflicts? |
Sorry, something went wrong.
|
bump @ustcweizhou - can you fix conflicts so we can progress into testing please. |
Sorry, something went wrong.
There was a problem hiding this comment.
code looks good, we need this integration tested on the new release (which will happen automatically 🤞 )
Sorry, something went wrong.
|
@rhtyd @DaanHoogland any chance to get this into 4.15 ? |
Sorry, something went wrong.
|
|
||
| Long rootDiskSize = rootDiskOfferingInfo.getSize(); | ||
| if (vm.getType().isUsedBySystem() && SystemVmRootDiskSize.value() != null) { | ||
| rootDiskSize = SystemVmRootDiskSize.value(); |
There was a problem hiding this comment.
@ustcweizhou should there be a check for > 0 ?
Sorry, something went wrong.
There was a problem hiding this comment.
@rhtyd added check.
Sorry, something went wrong.
| if which growpart > /dev/null; then | ||
| growpart /dev/vda 2 | ||
| growpart /dev/vda 6 | ||
| resize2fs /dev/vda6 |
There was a problem hiding this comment.
@ustcweizhou have you tested this for KVM, and non-KVM hypervisors? It's possible the partitions are not called (hard-coded) vda; instead of this can be find/use partitions by mount point names or other valid/static identifiers?
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
Sorry, something went wrong.
There was a problem hiding this comment.
@ustcweizhou have you tested this for KVM, and non-KVM hypervisors? It's possible the partitions are not called (hard-coded) vda; instead of this can be find/use partitions by mount point names or other valid/static identifiers?
@rhtyd good point. thanks for review
Sorry, something went wrong.
| echo "" > /root/.ssh/known_hosts | ||
|
|
||
| if which growpart > /dev/null; then | ||
| growpart /dev/vda 2 |
There was a problem hiding this comment.
I checked the 4.15 systemvmtemplate, growpart is not available but resize2fs is available. Can we use fdisk instead of growpart to resize partition instead, or some other alternative? This would save from creating a new systemvmtemplate as we get closer to the 4.15 release?
Sorry, something went wrong.
There was a problem hiding this comment.
@rhtyd root partition must be the last partition (it is linux swap for now), so this feature requires new systemvm template. let's move to 4.16.
I will work on other hypervisors except kvm.
Sorry, something went wrong.
|
@ustcweizhou I've left some review comments, please see. As we're getting closer to 4.15 release I would like to avoid anything that could add any regression, usually a systemvmtemplate change could potentially add regressions. A new Debian 10.6 was released over the weekend so if we build a systemvmtemplate now there may be several differences due to pkg/kernel changes against the one we've been testing for months - http://download.cloudstack.org/systemvm/4.15/ |
Sorry, something went wrong.
@rhtyd ok, then let's not merge this into 4.15 |
Sorry, something went wrong.
|
|
||
| Long rootDiskSize = rootDiskOfferingInfo.getSize(); | ||
| if (vm.getType().isUsedBySystem() && SystemVmRootDiskSize.value() != null) { | ||
| rootDiskSize = SystemVmRootDiskSize.value(); |
There was a problem hiding this comment.
@rhtyd added check.
Sorry, something went wrong.
|
ignore my approval ... |
Sorry, something went wrong.
|
@weizhouapache I think @Pearl1594 has already included these changes in her #4329 PR |
Sorry, something went wrong.
@rhtyd good. I closed this ticket then. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Description
The official systemvm template has very few free spaces, it would be better to make the disk size configuration.
Main changes in systemvm template
(1) remove /var and /tmp partitions
(2) move / partition to the last.
(3) install cloud-guest-utils to support "growpart"
(4) install haproxy 1.8 from stretch-backports instead of haproxy 1.7
other changes
(3) add global setting systemvm.root.disk.size
(4) when systemvm starts, allocate all free spaces on disk to the extend partition, root partition (/dev/vda6) and file system.
This applies on all systemvms (cpvm,ssvm,virtual routers, etc)
This fixes #3455
Types of changes
Screenshots (if appropriate):
How Has This Been Tested?
old VR
new VR