Comments

• 

  over 3 years ago by jfehlig | Reply

  The provo cluster has been updated to SLES15 SP3 snapshot12 + latest k3s. The latest git master of harvester is also installed on the cluster admin node and I've used it to successfully install a Tumbleweed VM from ISO.

  The installation took a very long time. I'll need to compare with a traditional virtualzation host. If there are differences the block IO path is highly suspect.

×
Edit Comment 5390
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
The provo cluster has been updated to SLES15 SP3 snapshot12 + latest k3s. The latest git master of harvester is also installed on the cluster admin node and I've used it to successfully install a Tumbleweed VM from ISO. The installation took a very long time. I'll need to compare with a traditional virtualzation host. If there are differences the block IO path is highly suspect.
 
×
Reply to jfehlig
The provo cluster has been updated to SLES15 SP3 snapshot12 + latest k3s. The latest git master of harvester is also installed on the cluster admin node and I've used it to successfully install a Tumbleweed VM from ISO.
The installation took a very long time. I'll need to compare with a traditional virtualzation host. If there are differences the block IO path is highly suspect.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  over 3 years ago by jfehlig | Reply

  To be specific about installation time, it took ~75 minutes to install Tumbleweed in the harvester created VM. By comparison, it took ~15 minutes to install Tumbleweed in a similarly configured VM created on a traditional KVM host with virt-install.

  To support my hypothesis that block IO might account for the long installation time, I ran some initial fio tests in the Tumbleweed VM created with harvester and the Tumbleweed VM created with virt-install

  Traditional VM sequential read: ~150MB/s Harvester VM sequential read: ~45MB/s

  Traditional VM random read: ~732KB/s Harvester VM random read: ~564KB/s

  Traditional VM sequential write: ~289MB/s Harvester VM sequential write: ~340MB/s

  Traditional VM random write: ~35MB/s Harvester VM random write: ~195KB/s

  The long install time of Tumbleweed in the harvester VM might be explained by the difference between random write performance. More investigation of the storage stack used by the harvester VM is needed...

×
Edit Comment 5402
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
To be specific about installation time, it took ~75 minutes to install Tumbleweed in the harvester created VM. By comparison, it took ~15 minutes to install Tumbleweed in a similarly configured VM created on a traditional KVM host with virt-install. To support my hypothesis that block IO might account for the long installation time, I ran some initial fio tests in the Tumbleweed VM created with harvester and the Tumbleweed VM created with virt-install Traditional VM sequential read: ~150MB/s Harvester VM sequential read: ~45MB/s Traditional VM random read: ~732KB/s Harvester VM random read: ~564KB/s Traditional VM sequential write: ~289MB/s Harvester VM sequential write: ~340MB/s Traditional VM random write: ~35MB/s Harvester VM random write: ~195KB/s The long install time of Tumbleweed in the harvester VM might be explained by the difference between random write performance. More investigation of the storage stack used by the harvester VM is needed...
 
×
Reply to jfehlig
To be specific about installation time, it took ~75 minutes to install Tumbleweed in the harvester created VM. By comparison, it took ~15 minutes to install Tumbleweed in a similarly configured VM created on a traditional KVM host with virt-install.
To support my hypothesis that block IO might account for the long installation time, I ran some initial fio tests in the Tumbleweed VM created with harvester and the Tumbleweed VM created with virt-install
Traditional VM sequential read: ~150MB/s Harvester VM sequential read: ~45MB/s
Traditional VM random read: ~732KB/s Harvester VM random read: ~564KB/s
Traditional VM sequential write: ~289MB/s Harvester VM sequential write: ~340MB/s
Traditional VM random write: ~35MB/s Harvester VM random write: ~195KB/s
The long install time of Tumbleweed in the harvester VM might be explained by the difference between random write performance. More investigation of the storage stack used by the harvester VM is needed...
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  over 3 years ago by jfehlig | Reply

  I've created ContainerDisks based on openSUSE Tumbleweed and SLES15 SP2 JeOS OpenStack Cloud images. For lack of a better place, I've pushed them to quay.io

  https://quay.io/repository/jfehlig/tumbleweed https://quay.io/repository/jfehlig/sles15-sp2

  So far I have not been able to start a VM using a ContainerDisk in the test cluster. The ContainerDisk image is never imported or cloned into a PVC for use by the VM. I'll need to gain a better understanding of CDI to get it working. I've found no helpful hints in any pod, service, system, etc. logs.

  • 

    over 3 years ago by jfehlig | Reply

    It looks like the installation of k3s followed by Harvester has resulted in two default StorageClass being defined

    kubectl get sc -A
    NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
    local-path (default) rancher.io/local-path Delete WaitForFirstConsumer false 3d19h
    longhorn (default) driver.longhorn.io Delete Immediate true 2d11h

  ×
  Edit Comment 5506
  # A First Level Header
  ## A Second Level Header
  
  Use one asterisk to *emphasize*
  
  Use two asterisks for **strong emphasis**
  
  - Use hyphens
  - for unordereed
  - lists
  
  This is an [link to example.com](http://example.com/)
  
  This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)
  
  This is a user link @hans
  
  This is a project link hw#some-cool-title
  
  More Complex Markdown Help
  Formatting Help
  • Edit
  • Preview
  It looks like the installation of k3s followed by Harvester has resulted in two default StorageClass being defined kubectl get sc -A NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE local-path (default) rancher.io/local-path Delete WaitForFirstConsumer false 3d19h longhorn (default) driver.longhorn.io Delete Immediate true 2d11h
   
  ×
  Reply to jfehlig
  It looks like the installation of k3s followed by Harvester has resulted in two default StorageClass being defined
  kubectl get sc -A
  NAME PROVISIONER RECLAIMPOLICY VOLUMEBINDINGMODE ALLOWVOLUMEEXPANSION AGE
  local-path (default) rancher.io/local-path Delete WaitForFirstConsumer false 3d19h
  longhorn (default) driver.longhorn.io Delete Immediate true 2d11h
  ---
  # A First Level Header
  ## A Second Level Header
  
  Use one asterisk to *emphasize*
  
  Use two asterisks for **strong emphasis**
  
  - Use hyphens
  - for unordereed
  - lists
  
  This is an [link to example.com](http://example.com/)
  
  This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)
  
  This is a user link @hans
  
  This is a project link hw#some-cool-title
  
  More Complex Markdown Help
  Formatting Help
  • Edit
  • Preview
   
×
Edit Comment 5498
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
I've created ContainerDisks based on openSUSE Tumbleweed and SLES15 SP2 JeOS OpenStack Cloud images. For lack of a better place, I've pushed them to quay.io https://quay.io/repository/jfehlig/tumbleweed https://quay.io/repository/jfehlig/sles15-sp2 So far I have not been able to start a VM using a ContainerDisk in the test cluster. The ContainerDisk image is never imported or cloned into a PVC for use by the VM. I'll need to gain a better understanding of CDI to get it working. I've found no helpful hints in any pod, service, system, etc. logs.
 
×
Reply to jfehlig
I've created ContainerDisks based on openSUSE Tumbleweed and SLES15 SP2 JeOS OpenStack Cloud images. For lack of a better place, I've pushed them to quay.io
https://quay.io/repository/jfehlig/tumbleweed https://quay.io/repository/jfehlig/sles15-sp2
So far I have not been able to start a VM using a ContainerDisk in the test cluster. The ContainerDisk image is never imported or cloned into a PVC for use by the VM. I'll need to gain a better understanding of CDI to get it working. I've found no helpful hints in any pod, service, system, etc. logs.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
 
• 

  over 3 years ago by jfehlig | Reply

  After changing the local-path StorageClass to non-default I'm able to import a ContainerDisk to a PVC, but still having problems starting a VM that uses it.

×
Edit Comment 5510
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview
After changing the local-path StorageClass to non-default I'm able to import a ContainerDisk to a PVC, but still having problems starting a VM that uses it.
 
×
Reply to jfehlig
After changing the local-path StorageClass to non-default I'm able to import a ContainerDisk to a PVC, but still having problems starting a VM that uses it.
---
# A First Level Header
## A Second Level Header

Use one asterisk to *emphasize*

Use two asterisks for **strong emphasis**

- Use hyphens
- for unordereed
- lists

This is an [link to example.com](http://example.com/)

This is an image ![an openSUSE geeko icon](https://en.opensuse.org/images/d/d0/Icon-distribution.png)

This is a user link @hans

This is a project link hw#some-cool-title
More Complex Markdown Help
Formatting Help
• Edit
• Preview