9:52 a.m.
Dear oVIrt,
Even though I would like to get some insight into what could be reason this is no working,
I did find a workaround:
Instead of trying to get Ubuntu disk specified with ovirt_disk size,
I used qemu-img resize to increase the disk size before importing it to oVIrt.
This works, but it still going to present the problem if User eventually wants to increase
for example disk from 40GBto 80GB.
Kindly awaiting your reply.
— — —
Met vriendelijke groet / Kind regards,
Marko Vrgotic
Sr. System Engineer @ System Administration
m.vrgotic@activevideo.com<mailto:m.vrgotic@activevideo.com>
From: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>
Date: Wednesday, 10 July 2019 at 16:19
To: "users(a)ovirt.org" <users(a)ovirt.org>
Subject: ovirt_disk and ubuntu issues
Dear oVirt,
I am downloading the ubuntu cloud image 16.04 and or 18.04:
- name: "Download base cloud image from server"
get_url:
url: "{{ image_url }}"
checksum: "sha256:{{ image_checksum }}"
validate_certs: yes
dest: "/tmp/{{ inventory_hostname_short }}.qcow2"
delegate_to: localhost
creating a 40GB HDD and attaching image to it:
- name: "Create oVirt disk with base image (with 40Gb allocated)"
ovirt_disk:
name: "{{ inventory_hostname_short }}"
interface: virtio
size: 40GiB
format: cow
upload_image_path: "/tmp/{{ inventory_hostname_short }}.qcow2"
storage_domain: ovirt_production
wait: true
delegate_to: localhost
creating VM afterwards:
- name: "Create new Ubuntu VMs from cloud image"
delegate_to: localhost
ovirt_vm:
auth: "{{ ovirt_auth }}"
name: "{{ inventory_hostname_short }}"
disks:
- name: "{{ inventory_hostname_short }}"
graphical_console:
protocol: vnc
serial_console: true
usb_support: true
soundcard_enabled: false
operating_system: "{{ operating_system_type }}"
type: server
nics:
- name: nic1
profile_name: tenant1
interface: virtio
nic_on_boot: true
cloud_init:
host_name: "{{ inventory_hostname }}"
user_name: ubuntu
authorized_ssh_keys: "{{ ssh_agent_pubkeys.stdout }}"
state: "running"
cluster: "{{ ovirt_cluster }}"
when: inventory_hostname in groups['ubuntu-baker']
When VM gets created, I can see in oVIrt VM details disk created is 40GB.
Executing df -h, gives me following:
root@av3-ubuntu-18-base:/home/ubuntu# df -h
Filesystem Size Used Avail Use% Mounted on
udev 447M 0 447M 0% /dev
tmpfs 92M 696K 92M 1% /run
/dev/vda1 2.0G 1.3G 706M 65% /
tmpfs 460M 0 460M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 460M 0 460M 0% /sys/fs/cgroup
/dev/vda15 105M 3.6M 101M 4% /boot/efi
tmpfs 92M 0 92M 0% /run/user/1000
Initially I thought growpart or resize2fs is not triggered, but then running dmesg or
fdisk /dev/vda, told me that physical disk size is still only size of the downloaded
ubuntu cloud image.
Disk /dev/vda: 2.2 GiB, 2361393152 bytes, 4612096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Is this related to ovirt_disk module, or ubuntu and ovirt_disk, since I do not have this
behavior with CentOS 7 images?
Can you advise how to proceed, in case I am missing some configuration parameter or
command to be run?
The following Ubuntu images are used:
ubuntu-16:
image_url=https://cloud-images.ubuntu.com/xenial/current/xenial-server-cl...
image_checksum=fda868058586b129c7fdb6472fe575e911f7c67551a6dc75966f2ec02201bdae
ubuntu-18:
image_url=https://cloud-images.ubuntu.com/bionic/current/bionic-server-cl...
image_checksum=7d2b90022a169119d7726c0fefa1713acbead7cc36d282c879896fd89c5a6663
Kindly awaiting your reply.
— — —
Met vriendelijke groet / Kind regards,
Marko Vrgotic
Sr. System Engineer @ System Administration
m.vrgotic@activevideo.com<mailto:m.vrgotic@activevideo.com>
tel. +31 (0)35 677 4131
3:20 a.m.
New subject: ovirt_disk and ubuntu issues
Good day Marko,
Can you please tell us whether you tried to create a pre-allocated or
thin-provision disk?
Ondra, can you please take a look that is not an Ansible issue?
Thank you in advance!
Pavel
On Mon, Jul 15, 2019 at 12:29 AM Vrgotic, Marko <M.Vrgotic(a)activevideo.com>
wrote:
Dear oVIrt,
Even though I would like to get some insight into what could be reason
this is no working, I did find a workaround:
Instead of trying to get Ubuntu disk specified with ovirt_disk size,
I used qemu-img resize to increase the disk size before importing it to
oVIrt.
This works, but it still going to present the problem if User eventually
wants to increase for example disk from 40GBto 80GB.
Kindly awaiting your reply.
— — —
Met vriendelijke groet / Kind regards,
*Marko Vrgotic*
Sr. System Engineer @ System Administration
m.vrgotic(a)activevideo.com
*From: *"Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>
*Date: *Wednesday, 10 July 2019 at 16:19
*To: *"users(a)ovirt.org" <users(a)ovirt.org>
*Subject: *ovirt_disk and ubuntu issues
Dear oVirt,
I am downloading the ubuntu cloud image 16.04 and or 18.04:
- name: "Download base cloud image from server"
get_url:
url: "{{ image_url }}"
checksum: "sha256:{{ image_checksum }}"
validate_certs: yes
dest: "/tmp/{{ inventory_hostname_short }}.qcow2"
delegate_to: localhost
creating a 40GB HDD and attaching image to it:
- name: "Create oVirt disk with base image (with 40Gb allocated)"
ovirt_disk:
name: "{{ inventory_hostname_short }}"
interface: virtio
size: 40GiB
format: cow
upload_image_path: "/tmp/{{ inventory_hostname_short }}.qcow2"
storage_domain: ovirt_production
wait: true
delegate_to: localhost
creating VM afterwards:
- name: "Create new Ubuntu VMs from cloud image"
delegate_to: localhost
ovirt_vm:
auth: "{{ ovirt_auth }}"
name: "{{ inventory_hostname_short }}"
disks:
- name: "{{ inventory_hostname_short }}"
graphical_console:
protocol: vnc
serial_console: true
usb_support: true
soundcard_enabled: false
operating_system: "{{ operating_system_type }}"
type: server
nics:
- name: nic1
profile_name: tenant1
interface: virtio
nic_on_boot: true
cloud_init:
host_name: "{{ inventory_hostname }}"
user_name: ubuntu
authorized_ssh_keys: "{{ ssh_agent_pubkeys.stdout }}"
state: "running"
cluster: "{{ ovirt_cluster }}"
when: inventory_hostname in groups['ubuntu-baker']
When VM gets created, I can see in oVIrt VM details disk created is 40GB.
Executing df -h, gives me following:
root@av3-ubuntu-18-base:/home/ubuntu# df -h
Filesystem Size Used Avail Use% Mounted on
udev 447M 0 447M 0% /dev
tmpfs 92M 696K 92M 1% /run
*/dev/vda1 2.0G 1.3G 706M 65% /*
tmpfs 460M 0 460M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 460M 0 460M 0% /sys/fs/cgroup
/dev/vda15 105M 3.6M 101M 4% /boot/efi
tmpfs 92M 0 92M 0% /run/user/1000
Initially I thought growpart or resize2fs is not triggered, but then
running dmesg or fdisk /dev/vda, told me that physical disk size is still
only size of the downloaded ubuntu cloud image.
Disk /dev/vda: 2.2 GiB, 2361393152 bytes, 4612096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Is this related to ovirt_disk module, or ubuntu and ovirt_disk, since I do
not have this behavior with CentOS 7 images?
*Can you advise how to proceed, in case I am missing some configuration
parameter or command to be run?*
The following Ubuntu images are used:
ubuntu-16: image_url=
https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd...
image_checksum=fda868058586b129c7fdb6472fe575e911f7c67551a6dc75966f2ec02201bdae
ubuntu-18: image_url=
https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd...
image_checksum=7d2b90022a169119d7726c0fefa1713acbead7cc36d282c879896fd89c5a6663
Kindly awaiting your reply.
— — —
Met vriendelijke groet / Kind regards,
*Marko Vrgotic*
Sr. System Engineer @ System Administration
m.vrgotic(a)activevideo.com
tel. +31 (0)35 677 4131
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VRLKCMREVCT...
4:04 a.m.
New subject: ovirt_disk and ubuntu issues
Hey Pavel,
As far as I remember, I went with Ansible ovirt_vm and ovrit_disk defaults. I will double
check.
“format: cow” which would mean thin-provisioned.
I have all prepared so I can make quick test with all scenarios:
1. format: cow
2. format: raw
3. format: cow and sparse: false(no)
4. ….
Let me know.
— — —
Met vriendelijke groet / Kind regards,
Marko Vrgotic
From: Pavel Bar <pbar(a)redhat.com>
Date: Monday, 15 July 2019 at 10:20
To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>, Ondra Machacek
<omachace(a)redhat.com>
Cc: "users(a)ovirt.org" <users(a)ovirt.org>
Subject: Re: [ovirt-users] Re: ovirt_disk and ubuntu issues
Good day Marko,
Can you please tell us whether you tried to create a pre-allocated or thin-provision
disk?
Ondra, can you please take a look that is not an Ansible issue?
Thank you in advance!
Pavel
On Mon, Jul 15, 2019 at 12:29 AM Vrgotic, Marko
<M.Vrgotic@activevideo.com<mailto:M.Vrgotic@activevideo.com>> wrote:
Dear oVIrt,
Even though I would like to get some insight into what could be reason this is no working,
I did find a workaround:
Instead of trying to get Ubuntu disk specified with ovirt_disk size,
I used qemu-img resize to increase the disk size before importing it to oVIrt.
This works, but it still going to present the problem if User eventually wants to increase
for example disk from 40GBto 80GB.
Kindly awaiting your reply.
— — —
Met vriendelijke groet / Kind regards,
Marko Vrgotic
Sr. System Engineer @ System Administration
m.vrgotic@activevideo.com<mailto:m.vrgotic@activevideo.com>
From: "Vrgotic, Marko"
<M.Vrgotic@activevideo.com<mailto:M.Vrgotic@activevideo.com>>
Date: Wednesday, 10 July 2019 at 16:19
To: "users@ovirt.org<mailto:users@ovirt.org>"
<users@ovirt.org<mailto:users@ovirt.org>>
Subject: ovirt_disk and ubuntu issues
Dear oVirt,
I am downloading the ubuntu cloud image 16.04 and or 18.04:
- name: "Download base cloud image from server"
get_url:
url: "{{ image_url }}"
checksum: "sha256:{{ image_checksum }}"
validate_certs: yes
dest: "/tmp/{{ inventory_hostname_short }}.qcow2"
delegate_to: localhost
creating a 40GB HDD and attaching image to it:
- name: "Create oVirt disk with base image (with 40Gb allocated)"
ovirt_disk:
name: "{{ inventory_hostname_short }}"
interface: virtio
size: 40GiB
format: cow
upload_image_path: "/tmp/{{ inventory_hostname_short }}.qcow2"
storage_domain: ovirt_production
wait: true
delegate_to: localhost
creating VM afterwards:
- name: "Create new Ubuntu VMs from cloud image"
delegate_to: localhost
ovirt_vm:
auth: "{{ ovirt_auth }}"
name: "{{ inventory_hostname_short }}"
disks:
- name: "{{ inventory_hostname_short }}"
graphical_console:
protocol: vnc
serial_console: true
usb_support: true
soundcard_enabled: false
operating_system: "{{ operating_system_type }}"
type: server
nics:
- name: nic1
profile_name: tenant1
interface: virtio
nic_on_boot: true
cloud_init:
host_name: "{{ inventory_hostname }}"
user_name: ubuntu
authorized_ssh_keys: "{{ ssh_agent_pubkeys.stdout }}"
state: "running"
cluster: "{{ ovirt_cluster }}"
when: inventory_hostname in groups['ubuntu-baker']
When VM gets created, I can see in oVIrt VM details disk created is 40GB.
Executing df -h, gives me following:
root@av3-ubuntu-18-base:/home/ubuntu# df -h
Filesystem Size Used Avail Use% Mounted on
udev 447M 0 447M 0% /dev
tmpfs 92M 696K 92M 1% /run
/dev/vda1 2.0G 1.3G 706M 65% /
tmpfs 460M 0 460M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 460M 0 460M 0% /sys/fs/cgroup
/dev/vda15 105M 3.6M 101M 4% /boot/efi
tmpfs 92M 0 92M 0% /run/user/1000
Initially I thought growpart or resize2fs is not triggered, but then running dmesg or
fdisk /dev/vda, told me that physical disk size is still only size of the downloaded
ubuntu cloud image.
Disk /dev/vda: 2.2 GiB, 2361393152 bytes, 4612096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Is this related to ovirt_disk module, or ubuntu and ovirt_disk, since I do not have this
behavior with CentOS 7 images?
Can you advise how to proceed, in case I am missing some configuration parameter or
command to be run?
The following Ubuntu images are used:
ubuntu-16:
image_url=https://cloud-images.ubuntu.com/xenial/current/xenial-server-cl...
image_checksum=fda868058586b129c7fdb6472fe575e911f7c67551a6dc75966f2ec02201bdae
ubuntu-18:
image_url=https://cloud-images.ubuntu.com/bionic/current/bionic-server-cl...
image_checksum=7d2b90022a169119d7726c0fefa1713acbead7cc36d282c879896fd89c5a6663
Kindly awaiting your reply.
— — —
Met vriendelijke groet / Kind regards,
Marko Vrgotic
Sr. System Engineer @ System Administration
m.vrgotic@activevideo.com<mailto:m.vrgotic@activevideo.com>
tel. +31 (0)35 677 4131
_______________________________________________
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to
users-leave@ovirt.org<mailto:users-leave@ovirt.org>
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VRLKCMREVCT...
4:01 a.m.
New subject: ovirt_disk and ubuntu issues
Hi,
What actually defines whether the disk is thin-provisioned or pre-allocated
is the "sparse" flag.
If you want the pre-allocated disk - the "sparse" flag should be set to
false.
If you want the thin-provisioned disk - the "sparse" flag should be set to
true.
Try to set the "sparse" flag to whatever scenario you are testing and send
the results.
Thank you in advance!
Pavel
On Mon, Jul 15, 2019 at 12:04 PM Vrgotic, Marko <M.Vrgotic(a)activevideo.com>
wrote:
Hey Pavel,
As far as I remember, I went with Ansible ovirt_vm and ovrit_disk
defaults. I will double check.
“format: cow” which would mean thin-provisioned.
I have all prepared so I can make quick test with all scenarios:
1. format: cow
2. format: raw
3. format: cow and sparse: false(no)
4. ….
Let me know.
— — —
Met vriendelijke groet / Kind regards,
*Marko Vrgotic*
*From: *Pavel Bar <pbar(a)redhat.com>
*Date: *Monday, 15 July 2019 at 10:20
*To: *"Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>, Ondra Machacek <
omachace(a)redhat.com>
*Cc: *"users(a)ovirt.org" <users(a)ovirt.org>
*Subject: *Re: [ovirt-users] Re: ovirt_disk and ubuntu issues
Good day Marko,
Can you please tell us whether you tried to create a pre-allocated or
thin-provision disk?
Ondra, can you please take a look that is not an Ansible issue?
Thank you in advance!
Pavel
On Mon, Jul 15, 2019 at 12:29 AM Vrgotic, Marko <M.Vrgotic(a)activevideo.com>
wrote:
Dear oVIrt,
Even though I would like to get some insight into what could be reason
this is no working, I did find a workaround:
Instead of trying to get Ubuntu disk specified with ovirt_disk size,
I used qemu-img resize to increase the disk size before importing it to
oVIrt.
This works, but it still going to present the problem if User eventually
wants to increase for example disk from 40GBto 80GB.
Kindly awaiting your reply.
— — —
Met vriendelijke groet / Kind regards,
*Marko Vrgotic*
Sr. System Engineer @ System Administration
m.vrgotic(a)activevideo.com
*From: *"Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>
*Date: *Wednesday, 10 July 2019 at 16:19
*To: *"users(a)ovirt.org" <users(a)ovirt.org>
*Subject: *ovirt_disk and ubuntu issues
Dear oVirt,
I am downloading the ubuntu cloud image 16.04 and or 18.04:
- name: "Download base cloud image from server"
get_url:
url: "{{ image_url }}"
checksum: "sha256:{{ image_checksum }}"
validate_certs: yes
dest: "/tmp/{{ inventory_hostname_short }}.qcow2"
delegate_to: localhost
creating a 40GB HDD and attaching image to it:
- name: "Create oVirt disk with base image (with 40Gb allocated)"
ovirt_disk:
name: "{{ inventory_hostname_short }}"
interface: virtio
size: 40GiB
format: cow
upload_image_path: "/tmp/{{ inventory_hostname_short }}.qcow2"
storage_domain: ovirt_production
wait: true
delegate_to: localhost
creating VM afterwards:
- name: "Create new Ubuntu VMs from cloud image"
delegate_to: localhost
ovirt_vm:
auth: "{{ ovirt_auth }}"
name: "{{ inventory_hostname_short }}"
disks:
- name: "{{ inventory_hostname_short }}"
graphical_console:
protocol: vnc
serial_console: true
usb_support: true
soundcard_enabled: false
operating_system: "{{ operating_system_type }}"
type: server
nics:
- name: nic1
profile_name: tenant1
interface: virtio
nic_on_boot: true
cloud_init:
host_name: "{{ inventory_hostname }}"
user_name: ubuntu
authorized_ssh_keys: "{{ ssh_agent_pubkeys.stdout }}"
state: "running"
cluster: "{{ ovirt_cluster }}"
when: inventory_hostname in groups['ubuntu-baker']
When VM gets created, I can see in oVIrt VM details disk created is 40GB.
Executing df -h, gives me following:
root@av3-ubuntu-18-base:/home/ubuntu# df -h
Filesystem Size Used Avail Use% Mounted on
udev 447M 0 447M 0% /dev
tmpfs 92M 696K 92M 1% /run
*/dev/vda1 2.0G 1.3G 706M 65% /*
tmpfs 460M 0 460M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 460M 0 460M 0% /sys/fs/cgroup
/dev/vda15 105M 3.6M 101M 4% /boot/efi
tmpfs 92M 0 92M 0% /run/user/1000
Initially I thought growpart or resize2fs is not triggered, but then
running dmesg or fdisk /dev/vda, told me that physical disk size is still
only size of the downloaded ubuntu cloud image.
Disk /dev/vda: 2.2 GiB, 2361393152 bytes, 4612096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Is this related to ovirt_disk module, or ubuntu and ovirt_disk, since I do
not have this behavior with CentOS 7 images?
*Can you advise how to proceed, in case I am missing some configuration
parameter or command to be run?*
The following Ubuntu images are used:
ubuntu-16: image_url=
https://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd...
image_checksum=fda868058586b129c7fdb6472fe575e911f7c67551a6dc75966f2ec02201bdae
ubuntu-18: image_url=
https://cloud-images.ubuntu.com/bionic/current/bionic-server-cloudimg-amd...
image_checksum=7d2b90022a169119d7726c0fefa1713acbead7cc36d282c879896fd89c5a6663
Kindly awaiting your reply.
— — —
Met vriendelijke groet / Kind regards,
*Marko Vrgotic*
Sr. System Engineer @ System Administration
m.vrgotic(a)activevideo.com
tel. +31 (0)35 677 4131
_______________________________________________
Users mailing list -- users(a)ovirt.org
To unsubscribe send an email to users-leave(a)ovirt.org
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct:
https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VRLKCMREVCT...
7:05 a.m.
New subject: ovirt_disk and ubuntu issues
Hey Pavel,
The reason why I mentioned it is that in the ansible ovirt_disk module it is explained if
cow format is used, sparse is true by default. This is scenario I used to create disk in
oVIrt with Centos and Ubuntu cloud images attached.
The main difference is that with CentOS images the disk size (in my case 40GB) is
recognized by OS and cloud-init grows partition to full size of the disk.
With Ubuntu, its not recognized by OS, disk is sized to 40GB, so cloud-init reports
“nothing to do”.
I will run the tests, so we can verify if it will make a difference if sparse is set to
True specifically or if it help pre-allocating the disk, if deploying Ubuntu cloud
image.
Considering that format for both CentOS and Ubuntu cloud images is qcow2 or 3, I would
expect it does not matter to the ovirt_disk module when resizing.
Or maybe better question is why does not Ubuntu OS recognize the new disk size?
Ultimately, in oVirt UI correct disk size is reported, but in Ubuntu OS is not.
My 5cents
As soon as tests are done, I will provide results.
Kindly awaiting your reply.
— — —
Met vriendelijke groet / Kind regards,
Marko Vrgotic
From: Pavel Bar <pbar(a)redhat.com>
Date: Tuesday, 16 July 2019 at 11:01
To: "Vrgotic, Marko" <M.Vrgotic(a)activevideo.com>
Cc: Ondra Machacek <omachace(a)redhat.com>, "users(a)ovirt.org"
<users(a)ovirt.org>
Subject: Re: [ovirt-users] Re: ovirt_disk and ubuntu issues
Hi,
What actually defines whether the disk is thin-provisioned or pre-allocated is the
"sparse" flag.
If you want the pre-allocated disk - the "sparse" flag should be set to
false.
If you want the thin-provisioned disk - the "sparse" flag should be set to
true.
Try to set the "sparse" flag to whatever scenario you are testing and send the
results.
Thank you in advance!
Pavel
On Mon, Jul 15, 2019 at 12:04 PM Vrgotic, Marko
<M.Vrgotic@activevideo.com<mailto:M.Vrgotic@activevideo.com>> wrote:
Hey Pavel,
As far as I remember, I went with Ansible ovirt_vm and ovrit_disk defaults. I will double
check.
“format: cow” which would mean thin-provisioned.
I have all prepared so I can make quick test with all scenarios:
1. format: cow
2. format: raw
3. format: cow and sparse: false(no)
4. ….
Let me know.
— — —
Met vriendelijke groet / Kind regards,
Marko Vrgotic
From: Pavel Bar <pbar@redhat.com<mailto:pbar@redhat.com>>
Date: Monday, 15 July 2019 at 10:20
To: "Vrgotic, Marko"
<M.Vrgotic@activevideo.com<mailto:M.Vrgotic@activevideo.com>>, Ondra Machacek
<omachace@redhat.com<mailto:omachace@redhat.com>>
Cc: "users@ovirt.org<mailto:users@ovirt.org>"
<users@ovirt.org<mailto:users@ovirt.org>>
Subject: Re: [ovirt-users] Re: ovirt_disk and ubuntu issues
Good day Marko,
Can you please tell us whether you tried to create a pre-allocated or thin-provision
disk?
Ondra, can you please take a look that is not an Ansible issue?
Thank you in advance!
Pavel
On Mon, Jul 15, 2019 at 12:29 AM Vrgotic, Marko
<M.Vrgotic@activevideo.com<mailto:M.Vrgotic@activevideo.com>> wrote:
Dear oVIrt,
Even though I would like to get some insight into what could be reason this is no working,
I did find a workaround:
Instead of trying to get Ubuntu disk specified with ovirt_disk size,
I used qemu-img resize to increase the disk size before importing it to oVIrt.
This works, but it still going to present the problem if User eventually wants to increase
for example disk from 40GBto 80GB.
Kindly awaiting your reply.
— — —
Met vriendelijke groet / Kind regards,
Marko Vrgotic
Sr. System Engineer @ System Administration
m.vrgotic@activevideo.com<mailto:m.vrgotic@activevideo.com>
From: "Vrgotic, Marko"
<M.Vrgotic@activevideo.com<mailto:M.Vrgotic@activevideo.com>>
Date: Wednesday, 10 July 2019 at 16:19
To: "users@ovirt.org<mailto:users@ovirt.org>"
<users@ovirt.org<mailto:users@ovirt.org>>
Subject: ovirt_disk and ubuntu issues
Dear oVirt,
I am downloading the ubuntu cloud image 16.04 and or 18.04:
- name: "Download base cloud image from server"
get_url:
url: "{{ image_url }}"
checksum: "sha256:{{ image_checksum }}"
validate_certs: yes
dest: "/tmp/{{ inventory_hostname_short }}.qcow2"
delegate_to: localhost
creating a 40GB HDD and attaching image to it:
- name: "Create oVirt disk with base image (with 40Gb allocated)"
ovirt_disk:
name: "{{ inventory_hostname_short }}"
interface: virtio
size: 40GiB
format: cow
upload_image_path: "/tmp/{{ inventory_hostname_short }}.qcow2"
storage_domain: ovirt_production
wait: true
delegate_to: localhost
creating VM afterwards:
- name: "Create new Ubuntu VMs from cloud image"
delegate_to: localhost
ovirt_vm:
auth: "{{ ovirt_auth }}"
name: "{{ inventory_hostname_short }}"
disks:
- name: "{{ inventory_hostname_short }}"
graphical_console:
protocol: vnc
serial_console: true
usb_support: true
soundcard_enabled: false
operating_system: "{{ operating_system_type }}"
type: server
nics:
- name: nic1
profile_name: tenant1
interface: virtio
nic_on_boot: true
cloud_init:
host_name: "{{ inventory_hostname }}"
user_name: ubuntu
authorized_ssh_keys: "{{ ssh_agent_pubkeys.stdout }}"
state: "running"
cluster: "{{ ovirt_cluster }}"
when: inventory_hostname in groups['ubuntu-baker']
When VM gets created, I can see in oVIrt VM details disk created is 40GB.
Executing df -h, gives me following:
root@av3-ubuntu-18-base:/home/ubuntu# df -h
Filesystem Size Used Avail Use% Mounted on
udev 447M 0 447M 0% /dev
tmpfs 92M 696K 92M 1% /run
/dev/vda1 2.0G 1.3G 706M 65% /
tmpfs 460M 0 460M 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 460M 0 460M 0% /sys/fs/cgroup
/dev/vda15 105M 3.6M 101M 4% /boot/efi
tmpfs 92M 0 92M 0% /run/user/1000
Initially I thought growpart or resize2fs is not triggered, but then running dmesg or
fdisk /dev/vda, told me that physical disk size is still only size of the downloaded
ubuntu cloud image.
Disk /dev/vda: 2.2 GiB, 2361393152 bytes, 4612096 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Is this related to ovirt_disk module, or ubuntu and ovirt_disk, since I do not have this
behavior with CentOS 7 images?
Can you advise how to proceed, in case I am missing some configuration parameter or
command to be run?
The following Ubuntu images are used:
ubuntu-16:
image_url=https://cloud-images.ubuntu.com/xenial/current/xenial-server-cl...
image_checksum=fda868058586b129c7fdb6472fe575e911f7c67551a6dc75966f2ec02201bdae
ubuntu-18:
image_url=https://cloud-images.ubuntu.com/bionic/current/bionic-server-cl...
image_checksum=7d2b90022a169119d7726c0fefa1713acbead7cc36d282c879896fd89c5a6663
Kindly awaiting your reply.
— — —
Met vriendelijke groet / Kind regards,
Marko Vrgotic
Sr. System Engineer @ System Administration
m.vrgotic@activevideo.com<mailto:m.vrgotic@activevideo.com>
tel. +31 (0)35 677 4131
_______________________________________________
Users mailing list -- users@ovirt.org<mailto:users@ovirt.org>
To unsubscribe send an email to
users-leave@ovirt.org<mailto:users-leave@ovirt.org>
Privacy Statement: https://www.ovirt.org/site/privacy-policy/
oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/
List Archives:
https://lists.ovirt.org/archives/list/users@ovirt.org/message/VRLKCMREVCT...
1951
days inactive
1953
days old
4 comments
2 participants
participants (2)
-
Pavel Bar -
Vrgotic, Marko