From nobody Fri May 17 12:15:02 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) client-ip=170.10.133.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1671043162; cv=none; d=zohomail.com; s=zohoarc; b=b4LkbzgpQAJ23yCOM1C5laxmGw0jawaoDxjoLitxnXaBRYLwCkVvC0eIQL7WCNCEPFCm1U+GfQv8hf1/CL0y+huFiR63SqiNIpnWY5dIpW82PjpB/i+sFQmMTK8QEneDHTXT+VCmsqmnYS81+umOPxVYJlv8Janyfqs7ta8M6w0= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1671043162; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=emJEqH0GKbbBxMXuS6+KkWq/3oMsDn7yVS8TtNBDsCo=; b=UdCqUF8KQp8rm4jbHL8/u1sLcuPrHtmQFzN3D2XOdHJxPgvbp3BZKl2/Idp+RkmeCnFDcmLKeVTw+q2ZubObJ4km0WBRRsih/lqxnZbIsz4nFcawve+qszeDTTLwTyv7SrrJqxU9TvRiT7CKx4Y/gCR8oM2DRJ07HvDXtkPfiLY= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.133.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.133.124]) by mx.zohomail.com with SMTPS id 1671043162311749.5654814863717; Wed, 14 Dec 2022 10:39:22 -0800 (PST) Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-668-rpRRd6l7Pq6N90KxHVLQ9g-1; Wed, 14 Dec 2022 13:39:17 -0500 Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.rdu2.redhat.com [10.11.54.3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id A41CF802D36; Wed, 14 Dec 2022 18:39:15 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id D328F1121314; Wed, 14 Dec 2022 18:39:13 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 12BC81946A42; Wed, 14 Dec 2022 18:39:13 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id DD93919465B9 for ; Wed, 14 Dec 2022 18:39:10 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id B25CA40BC781; Wed, 14 Dec 2022 18:39:10 +0000 (UTC) Received: from harajuku.usersys.redhat.com (ovpn-195-21.brq.redhat.com [10.40.195.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 17131400D79E for ; Wed, 14 Dec 2022 18:39:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1671043161; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=emJEqH0GKbbBxMXuS6+KkWq/3oMsDn7yVS8TtNBDsCo=; b=QwJqh3KOb8FyTyrWJFOfcanD2dyPTkJv3KlNimfpSC1OqrHu2LBYHLpuVjN+jDRRyxlqwd VegfuW3u9E0JBCENjuIhJXraGdjtZglQgavb75tJndV/tLt0KqxJAvoqFSNS+xhVcgWUY3 YK+9PeevR7EoB6aToJjEz46XYAUBIfM= X-MC-Unique: rpRRd6l7Pq6N90KxHVLQ9g-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Andrea Bolognani To: libvir-list@redhat.com Subject: [libvirt PATCH 1/2] kbase: Reorder sections Date: Wed, 14 Dec 2022 19:39:06 +0100 Message-Id: <20221214183907.149555-2-abologna@redhat.com> In-Reply-To: <20221214183907.149555-1-abologna@redhat.com> References: <20221214183907.149555-1-abologna@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 3.1 on 10.11.54.3 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1671043162945100003 Content-Type: text/plain; charset="utf-8"; x-default="true" Users are likely more interested in the main deployment scenarios than in the detailed list of every existing RPM package. Reorder sections accordingly. Signed-off-by: Andrea Bolognani Reviewed-by: Jim Fehlig --- docs/kbase/rpm-deployment.rst | 134 +++++++++++++++++----------------- 1 file changed, 67 insertions(+), 67 deletions(-) diff --git a/docs/kbase/rpm-deployment.rst b/docs/kbase/rpm-deployment.rst index b5ee7fd827..d1180fb0c3 100644 --- a/docs/kbase/rpm-deployment.rst +++ b/docs/kbase/rpm-deployment.rst @@ -20,6 +20,73 @@ of the drivers will be disabled at build time, so not al= l of the packages listed on this page will exist. =20 =20 +Deployment choices +=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D + +Client only install +------------------- + +If an application is capable of using multiple different virtualization dr= ivers +it is undesirable to force the installation of a specific set of drivers. = In +this case the application will merely wish to request a client only install + +Alternatively if an application is intended to communicate with a hypervis= or on +a remote host there is no need to install drivers locally, only a client is +needed + +The only required package is the `libvirt-libs`, however, it is useful to +also install `libvirt-client`. + + +Every possible virt driver +-------------------------- + +There is rarely a need to install every virt driver at once on a given hos= t. +In the unlikely event that this is needed, however, the `libvirt` package +should be installed. + +Note that this doesn't actually pull in the hypervisors, only the libvirt +code to talk to the hypervisors. + + +Full features for one virt driver +--------------------------------- + +This is a common default installation profile when there is no need to min= imise +the on-disk footprint. + +This is achieved by installing the `libvirt-daemon-XXXX` package for the +virtualization driver that is desired. This will also pull in the default +set of hypervisor packages too. + +Since this installs every possible libvirt feature for the virtualization +driver in question, the on-disk footprint is quite large. The in-memory +footprint of the daemons is also relatively large since a lot of code is +loaded. + + +Minimal features for one virt driver +------------------------------------ + +This is the best installation profile when it is desired to minimize the +on-disk footprint. + +This is achieved by installing the individual `libvirt-daemon-driver-XXX` +packages needed for the features that will be used. This will not pull in= the +hypervisor packages, allowing a fine grained set of hypervisor features to= be +chosen separately. + +Since this allows fine grained installation of individual libvirt drivers, +this results in the lowest on-disk footprint. The in-memory footprint of +the daemons is also minimized by reducing the code loaded. + +As an example, the smallest possible installation for running KVM guests c= an +be achieved by installing `libvirt-daemon-driver-qemu` and `qemu-kvm-core`. +This will exclude all the secondary libvirt drivers for storage, networking +and host devices, leaving only the bare minimum functionality for managing +KVM guests. + + RPM packages =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 @@ -308,70 +375,3 @@ RPM packages between libvirt and its daemons. Since production deployments should all= be using a TLS encrypted, this only useful for development hosts with a lib= virt daemon configured without encryption. - - -Deployment choices -=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D - -Client only install -------------------- - -If an application is capable of using multiple different virtualization dr= ivers -it is undesirable to force the installation of a specific set of drivers. = In -this case the application will merely wish to request a client only install - -Alternatively if an application is intended to communicate with a hypervis= or on -a remote host there is no need to install drivers locally, only a client is -needed - -The only required package is the `libvirt-libs`, however, it is useful to -also install `libvirt-client`. - - -Every possible virt driver --------------------------- - -There is rarely a need to install every virt driver at once on a given hos= t. -In the unlikely event that this is needed, however, the `libvirt` package -should be installed. - -Note that this doesn't actually pull in the hypervisors, only the libvirt -code to talk to the hypervisors. - - -Full features for one virt driver ---------------------------------- - -This is a common default installation profile when there is no need to min= imise -the on-disk footprint. - -This is achieved by installing the `libvirt-daemon-XXXX` package for the -virtualization driver that is desired. This will also pull in the default -set of hypervisor packages too. - -Since this installs every possible libvirt feature for the virtualization -driver in question, the on-disk footprint is quite large. The in-memory -footprint of the daemons is also relatively large since a lot of code is -loaded. - - -Minimal features for one virt driver ------------------------------------- - -This is the best installation profile when it is desired to minimize the -on-disk footprint. - -This is achieved by installing the individual `libvirt-daemon-driver-XXX` -packages needed for the features that will be used. This will not pull in= the -hypervisor packages, allowing a fine grained set of hypervisor features to= be -chosen separately. - -Since this allows fine grained installation of individual libvirt drivers, -this results in the lowest on-disk footprint. The in-memory footprint of -the daemons is also minimized by reducing the code loaded. - -As an example, the smallest possible installation for running KVM guests c= an -be achieved by installing `libvirt-daemon-driver-qemu` and `qemu-kvm-core`. -This will exclude all the secondary libvirt drivers for storage, networking -and host devices, leaving only the bare minimum functionality for managing -KVM guests. --=20 2.38.1 From nobody Fri May 17 12:15:02 2024 Delivered-To: importer@patchew.org Received-SPF: pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) client-ip=170.10.129.124; envelope-from=libvir-list-bounces@redhat.com; helo=us-smtp-delivery-124.mimecast.com; Authentication-Results: mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass(p=none dis=none) header.from=redhat.com ARC-Seal: i=1; a=rsa-sha256; t=1671043162; cv=none; d=zohomail.com; s=zohoarc; b=O2i4k1LJCD2SlALuGj2Xeh8WtJZnYl64hbt2yKyBF79VrIH77oIuvM8u0s//Z1tVjNShNE/Cwl2LJL6rMWVmssUcd3kxpRIRToJxxvMT5UpoaIFEzMLqAbceDkPgUahch8jO5xTSQhooZ1VAx7sgpFnRf1VXDUrdWcT8N70Hc20= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1671043162; h=Content-Type:Content-Transfer-Encoding:Date:From:In-Reply-To:List-Subscribe:List-Post:List-Id:List-Archive:List-Help:List-Unsubscribe:MIME-Version:Message-ID:References:Sender:Subject:To; bh=7Cy+YoEJEEhX+jaCg3KorrTafpDb2NxBaHb+WEy1pNY=; b=l0n44N1ExU0q1Vr2ILs8Aee7tDka1ZFI7nJoc0ReGCXmjSXx9dJW9RIQChxijqTt7SziYEFkLa7qBe3x/sZW1eddu5uDh192Aq2GYmVUZ4mYsF1Iby5GIDwyDMif0eQiFd95lPrYwyJOjjhEZ/hqQvEuSAt/+5nsv0144m8oEek= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass; spf=pass (zohomail.com: domain of redhat.com designates 170.10.129.124 as permitted sender) smtp.mailfrom=libvir-list-bounces@redhat.com; dmarc=pass header.from= (p=none dis=none) Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.zohomail.com with SMTPS id 1671043162323624.7721065506715; Wed, 14 Dec 2022 10:39:22 -0800 (PST) Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-53-dZkgDNtvMzuPhnoxZYFztg-1; Wed, 14 Dec 2022 13:39:18 -0500 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.rdu2.redhat.com [10.11.54.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id A4CDB1C02CB8; Wed, 14 Dec 2022 18:39:15 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com [10.30.29.100]) by smtp.corp.redhat.com (Postfix) with ESMTP id 8D771140E949; Wed, 14 Dec 2022 18:39:14 +0000 (UTC) Received: from mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (localhost [IPv6:::1]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 4E6331946A66; Wed, 14 Dec 2022 18:39:13 +0000 (UTC) Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) by mm-prod-listman-01.mail-001.prod.us-east-1.aws.redhat.com (Postfix) with ESMTP id 8F00B1946A4E for ; Wed, 14 Dec 2022 18:39:11 +0000 (UTC) Received: by smtp.corp.redhat.com (Postfix) id 80EAC400D796; Wed, 14 Dec 2022 18:39:11 +0000 (UTC) Received: from harajuku.usersys.redhat.com (ovpn-195-21.brq.redhat.com [10.40.195.21]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 06E6040C945A for ; Wed, 14 Dec 2022 18:39:10 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1671043161; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=7Cy+YoEJEEhX+jaCg3KorrTafpDb2NxBaHb+WEy1pNY=; b=aQ/EVj2uOlHBPA2md39j/bJ/Ftoo7f8GXEktLJrB7c4ITjyBTpYov9e04zrufBF5xi9slC b3UqYjuPRox9xj7Y1GB/Hg8hTUlXFUOAFrUvBmIv91iWl1TTVOgjnEYKhVJ7Ety53yRhdd wa2+r6YU73IDEhHEwkopik1P9TwaZ4M= X-MC-Unique: dZkgDNtvMzuPhnoxZYFztg-1 X-Original-To: libvir-list@listman.corp.redhat.com From: Andrea Bolognani To: libvir-list@redhat.com Subject: [libvirt PATCH 2/2] kbase: Reorder deployments Date: Wed, 14 Dec 2022 19:39:07 +0100 Message-Id: <20221214183907.149555-3-abologna@redhat.com> In-Reply-To: <20221214183907.149555-1-abologna@redhat.com> References: <20221214183907.149555-1-abologna@redhat.com> MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.1 on 10.11.54.2 X-BeenThere: libvir-list@redhat.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development discussions about the libvirt library & tools List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: libvir-list-bounces@redhat.com Sender: "libvir-list" X-Scanned-By: MIMEDefang 3.1 on 10.11.54.7 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: quoted-printable X-ZohoMail-DKIM: pass (identity @redhat.com) X-ZM-MESSAGEID: 1671043162906100001 Content-Type: text/plain; charset="utf-8"; x-default="true" List the various options so that the most likely ones come first. Signed-off-by: Andrea Bolognani Reviewed-by: Jim Fehlig --- docs/kbase/rpm-deployment.rst | 52 +++++++++++++++++------------------ 1 file changed, 26 insertions(+), 26 deletions(-) diff --git a/docs/kbase/rpm-deployment.rst b/docs/kbase/rpm-deployment.rst index d1180fb0c3..31805c2280 100644 --- a/docs/kbase/rpm-deployment.rst +++ b/docs/kbase/rpm-deployment.rst @@ -23,32 +23,6 @@ listed on this page will exist. Deployment choices =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 -Client only install -------------------- - -If an application is capable of using multiple different virtualization dr= ivers -it is undesirable to force the installation of a specific set of drivers. = In -this case the application will merely wish to request a client only install - -Alternatively if an application is intended to communicate with a hypervis= or on -a remote host there is no need to install drivers locally, only a client is -needed - -The only required package is the `libvirt-libs`, however, it is useful to -also install `libvirt-client`. - - -Every possible virt driver --------------------------- - -There is rarely a need to install every virt driver at once on a given hos= t. -In the unlikely event that this is needed, however, the `libvirt` package -should be installed. - -Note that this doesn't actually pull in the hypervisors, only the libvirt -code to talk to the hypervisors. - - Full features for one virt driver --------------------------------- =20 @@ -65,6 +39,21 @@ footprint of the daemons is also relatively large since = a lot of code is loaded. =20 =20 +Client only install +------------------- + +If an application is capable of using multiple different virtualization dr= ivers +it is undesirable to force the installation of a specific set of drivers. = In +this case the application will merely wish to request a client only install + +Alternatively if an application is intended to communicate with a hypervis= or on +a remote host there is no need to install drivers locally, only a client is +needed + +The only required package is the `libvirt-libs`, however, it is useful to +also install `libvirt-client`. + + Minimal features for one virt driver ------------------------------------ =20 @@ -87,6 +76,17 @@ and host devices, leaving only the bare minimum function= ality for managing KVM guests. =20 =20 +Every possible virt driver +-------------------------- + +There is rarely a need to install every virt driver at once on a given hos= t. +In the unlikely event that this is needed, however, the `libvirt` package +should be installed. + +Note that this doesn't actually pull in the hypervisors, only the libvirt +code to talk to the hypervisors. + + RPM packages =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =20 --=20 2.38.1