From 1eb888169449fb6cceccd3a81279560b6bd94c8d Mon Sep 17 00:00:00 2001 From: Dmitry Tantsur Date: Sat, 27 Apr 2024 17:25:46 +0200 Subject: [PATCH] Remove the outdated virsh_dev_env and its documentation It's completely untested, I don't know anyone who uses it, and it relies on CentOS 7 which is known not to work with latest Bifrost. Change-Id: Ie960356cf9abd91b12266aa3a0d955c78e63372b --- doc/source/contributor/testenv.rst | 8 -- doc/source/contributor/virsh.rst | 67 -------------- doc/source/user/howto.rst | 5 ++ tools/virsh_dev_env/network/br_direct.xml | 6 -- tools/virsh_dev_env/network/default.xml | 15 ---- tools/virsh_dev_env/vm/baremetal.xml | 101 ---------------------- 6 files changed, 5 insertions(+), 197 deletions(-) delete mode 100644 doc/source/contributor/virsh.rst delete mode 100644 tools/virsh_dev_env/network/br_direct.xml delete mode 100644 tools/virsh_dev_env/network/default.xml delete mode 100644 tools/virsh_dev_env/vm/baremetal.xml diff --git a/doc/source/contributor/testenv.rst b/doc/source/contributor/testenv.rst index 39c6043f1..94741ffdb 100644 --- a/doc/source/contributor/testenv.rst +++ b/doc/source/contributor/testenv.rst @@ -106,13 +106,5 @@ sushy-tools_ is also installed. in the previous step. #. Run the deployment step, as documented in :ref:`deploy`. -Configuring libvirt -------------------- - -.. toctree:: - - virsh - - .. _VirtualBMC: https://docs.openstack.org/virtualbmc/ .. _sushy-tools: https://docs.openstack.org/sushy-tools/ diff --git a/doc/source/contributor/virsh.rst b/doc/source/contributor/virsh.rst deleted file mode 100644 index ae1ae6e2a..000000000 --- a/doc/source/contributor/virsh.rst +++ /dev/null @@ -1,67 +0,0 @@ -Deploying with libvirt -====================== - -In order to deploy bifrost with libvirt, in order to support managing -baremetal servers from with-in that libvirt VM, a special network -configuration is required. - -Two networks need to be created: - -- default network, that will be a standard virtual network, using NAT. -- provisioning network, that will be used for PXE boot. As we need to setup - a dhcp server on bifrost guest, creating a virtual network will give - conflicts between guest and host. So to avoid it, we can define a - network that uses macvtap interfaces, associated with the physical - interface. - Please note that you will need to have macvlan enabled on your kernel. - -When creating the guest, a minimum of 8GB of memory is needed in order to -build disk images along with run the services to support bifrost. - -When defining the interfaces for the guest, the two networks that have been -created need to be attached. - -These sample commands will spin up a bifrost vm based on centos:: - - virsh net-define --file tools/virsh_dev_env/network/default.xml - virsh net-start default - virsh net-define --file tools/virsh_dev_env/network/br_direct.xml - virsh net-start br_direct - virsh define --file tools/virsh_dev_env/vm/baremetal.xml - virsh start baremetal - virsh console baremetal - -When you login into baremetal, the interface for the provisioning -network will be down. You may need to add an IP manually:: - - ip addr add <>/<> dev <> - ip link set <> up - -Where to get guest images -------------------------- -In order to create the guest VMs, you will need a cloud image -for the distro you want to deploy. You will need to download the -guest image on a directory on the host, and then in the template -for the VM, you can specify it on the disk section, as shown -in the example template. - -Please see the `OpenStack Image Guide `_ -for options and locations for obtaining guest images. - -Add credentials to guest image ------------------------------- - -Normally guest images come without user and password, they rely on ssh to -allow access. In this case, it can be useful to enable ssh access to some -user from host to guest. A way to do that, is creating a config drive -and reference it on the template for the guest VM. - -A useful script to generate config drives can be found -`here `_. - -Relying on this script, a config drive can be created with:: - - create-config-drive -k ~/.ssh/id_rsa.pub config.iso - -And then this ISO can be referenced on the guest VM template. - diff --git a/doc/source/user/howto.rst b/doc/source/user/howto.rst index b495b2a9a..89bf6b87c 100644 --- a/doc/source/user/howto.rst +++ b/doc/source/user/howto.rst @@ -284,6 +284,11 @@ installation. You can also use a custom image: --image http://example.com/images/my-image.qcow2 \ --image-checksum 91ebfb80743bb98c59f787c9dc1f3cef \ +.. note:: + Please see the `OpenStack Image Guide + `_ for options + and locations for obtaining guest images. + You can also provide a custom configdrive URL (or its content) instead of the one Bifrost builds for you: diff --git a/tools/virsh_dev_env/network/br_direct.xml b/tools/virsh_dev_env/network/br_direct.xml deleted file mode 100644 index 206205859..000000000 --- a/tools/virsh_dev_env/network/br_direct.xml +++ /dev/null @@ -1,6 +0,0 @@ - - br_direct - - - - diff --git a/tools/virsh_dev_env/network/default.xml b/tools/virsh_dev_env/network/default.xml deleted file mode 100644 index 0d6fe9240..000000000 --- a/tools/virsh_dev_env/network/default.xml +++ /dev/null @@ -1,15 +0,0 @@ - - default - 76d95e35-3cf6-4a43-bf31-9d10717982e6 - - - - - - - - - - - - diff --git a/tools/virsh_dev_env/vm/baremetal.xml b/tools/virsh_dev_env/vm/baremetal.xml deleted file mode 100644 index e995ac78b..000000000 --- a/tools/virsh_dev_env/vm/baremetal.xml +++ /dev/null @@ -1,101 +0,0 @@ - - baremetal - 99714ffa-c947-4ff9-818d-ca11ee152494 - 8388608 - 8388608 - 2 - - /machine - - - - - - - Broadwell - - - - - - - destroy - restart - restart - - - - - - /usr/libexec/qemu-kvm - - - - - - -
- - - - - - - - -
- - - - -
- - - - -
- - - - -
- - - - - - -
- - - - - - - -
- - - - - - - - - - - - - - - - - -
- - - - - system_u:object_r:svirt_image_t:s0:c71,c869 - -