Configure OpenStack in charm-deployment-guide

[Juergen Morgenstern]

This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:

- [x] This doc is inaccurate in this way: the resulting environment is with QEMU Hypervisors, which is not the standard - should be KVM. My understanding is that it is not supported to change the Hypervisor type of a nova instance. How can I deploy a KVM one ?
Is there a bug in the bundle deployment scenario or did I miss something?

- [ ] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output.

If you have a troubleshooting or support issue, use the following resources:

 - The mailing list: https://lists.openstack.org
 - IRC: 'openstack' channel on Freenode

-----------------------------------
Release: 0.0.1.dev329 on 2021-05-11 14:43:51
SHA: 2be8037f5998f92ee57504af18e0cdf3e6a896ef
Source: https://opendev.org/openstack/charm-deployment-guide/src/deploy-guide/source/configure-openstack.rst
URL: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/wallaby/configure-openstack.html

[Peter Matulis (petermatulis)]

Hi Juergen,

The hypervisor type is determined by the nova-compute charm configuration option 'virt-type', which has a default value of 'kvm'.

If your cloud is deployed, you can query the current value in this way:

$ juju config nova-compute virt-type

[Juergen Morgenstern (jmorgenstern)]

Many thanks for the fast RTT, Peter!!!

The CLI command shows „kvm“ as the virt-type; the GUI shows QEMU.
And if I try to launch an instance, the error message says there is no kvm being configured.

Sorry for the newbie question, but do you have any clue art a possible solution of this issue?

Thanks,
Juergen

> Am 10.06.2021 um 16:50 schrieb Peter Matulis <email address hidden>:
>
> Hi Juergen,
>
> The hypervisor type is determined by the nova-compute charm
> configuration option 'virt-type', which has a default value of 'kvm'.
>
> If your cloud is deployed, you can query the current value in this way:
>
> $ juju config nova-compute virt-type
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1931579
>
> Title:
> Configure OpenStack in charm-deployment-guide
>
> Status in OpenStack Charms Deployment Guide:
> New
>
> Bug description:
> This bug tracker is for errors with the documentation, use the
> following as a template and remove or add fields as you see fit.
> Convert [ ] into [x] to check boxes:
>
> - [x] This doc is inaccurate in this way: the resulting environment is with QEMU Hypervisors, which is not the standard - should be KVM. My understanding is that it is not supported to change the Hypervisor type of a nova instance. How can I deploy a KVM one ?
> Is there a bug in the bundle deployment scenario or did I miss something?
>
>
> - [ ] This is a doc addition request.
> - [ ] I have a fix to the document that I can paste below including example: input and output.
>
> If you have a troubleshooting or support issue, use the following
> resources:
>
> - The mailing list: https://lists.openstack.org
> - IRC: 'openstack' channel on Freenode
>
> -----------------------------------
> Release: 0.0.1.dev329 on 2021-05-11 14:43:51
> SHA: 2be8037f5998f92ee57504af18e0cdf3e6a896ef
> Source: https://opendev.org/openstack/charm-deployment-guide/src/deploy-guide/source/configure-openstack.rst
> URL: https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/wallaby/configure-openstack.html
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/charm-deployment-guide/+bug/1931579/+subscriptions

[Peter Matulis (petermatulis)]

Juergen,

You're welcome. Glad to help. But I propose that you join our user forum [1] to continue the discussion. There, you can provide more detailed information (e.g how you installed and maybe a screenshot of what you're seeing in the GUI). Let's get this resolved.

[1]: https://discourse.charmhub.io/tag/openstack

[Peter Matulis (petermatulis)]

To wrap this up:

It turns out that the cloud (MAAS) nodes being used were VMware ESXi guests, which demanded that nested virtualisation be enabled on the guests acting as OpenStack compute nodes. I'll add a note to the docs to this effect.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/charm-deployment-guide/+/797503

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/charm-deployment-guide/+/797503
Committed: https://opendev.org/openstack/charm-deployment-guide/commit/043cbbca00057e1bc8e8842152be808dc110342b
Submitter: "Zuul (22348)"
Branch: master

commit 043cbbca00057e1bc8e8842152be808dc110342b
Author: Peter Matulis <email address hidden>
Date: Tue Jun 22 11:55:12 2021 -0400

    Mention possible need for nested virtualisation

    Although the guide assumes physical MAAS nodes add a
    note reminding readers about a possible need for
    nested virtualisation.

    Closes-Bug: #1931579
    Change-Id: I3fa453c0ce52c463b5a6b6079deb08d8092927f0