This is an automated email from the ASF dual-hosted git repository.
weizhou pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/cloudstack-documentation.git
The following commit(s) were added to refs/heads/main by this push:
new 16581d2 Replace CentOS 7 references with EL8 (#441)
16581d2 is described below
commit 16581d2cc4a0c63fe5bacd309bb7d600e78a3022
Author: Vishesh <[email protected]>
AuthorDate: Wed Nov 27 20:47:51 2024 +0530
Replace CentOS 7 references with EL8 (#441)
* Update QIG with EL8 and remove centos 7
* remove remaning mentions of centos 7
* Update _requirements.rst
* Update qig.rst
* Update qig.rst
* Update qig.rst
* Update qig.rst
* nmcli commands and corrections
* Update qig.rst
* Update qig.rst
---------
Co-authored-by: Andrija Panic
<[email protected]>
---
source/adminguide/templates/_cloud_init.rst | 2 +-
source/installguide/building_from_source.rst | 4 +-
source/installguide/overview/_requirements.rst | 2 +-
source/plugins/cloudian-connector.rst | 3 +-
source/quickinstallationguide/qig.rst | 193 ++++++++-----------------
5 files changed, 62 insertions(+), 142 deletions(-)
diff --git a/source/adminguide/templates/_cloud_init.rst
b/source/adminguide/templates/_cloud_init.rst
index 91793c1..1494308 100644
--- a/source/adminguide/templates/_cloud_init.rst
+++ b/source/adminguide/templates/_cloud_init.rst
@@ -176,7 +176,7 @@ These features can be implemented in `“Linux Template
creation process” <_cr
~ CentOS
- Centos 7 root volume is /dev/centos/root if no changes are done during
installation. Change the value accordingly if setup is different.
+ CentOS root volume is /dev/centos/root if no changes are done during
installation. Change the value accordingly if setup is different.
.. code:: bash
diff --git a/source/installguide/building_from_source.rst
b/source/installguide/building_from_source.rst
index 0915b97..70315b3 100644
--- a/source/installguide/building_from_source.rst
+++ b/source/installguide/building_from_source.rst
@@ -483,9 +483,9 @@ Generating RPMs is done using the ``package.sh`` script:
.. parsed-literal::
- $ ./package.sh -d centos63
+ $ ./package.sh -d el8
-For other supported options(like centos7), run ``./package.sh --help``
+For other supported options, run ``./package.sh --help``
That will run for a bit and then place the finished packages in
``dist/rpmbuild/RPMS/x86_64/``.
diff --git a/source/installguide/overview/_requirements.rst
b/source/installguide/overview/_requirements.rst
index c46f90e..7d42d6f 100644
--- a/source/installguide/overview/_requirements.rst
+++ b/source/installguide/overview/_requirements.rst
@@ -29,7 +29,7 @@ Management Server may be placed on an Instance.
- Operating system:
- - Preferred: CentOS/RHEL 7.2+ or Ubuntu 16.04(.2) or higher
+ - Preferred: EL8+ or Ubuntu 22.04 or higher
- 64-bit x86 CPU (more cores results in better performance)
diff --git a/source/plugins/cloudian-connector.rst
b/source/plugins/cloudian-connector.rst
index addd869..83d25fb 100644
--- a/source/plugins/cloudian-connector.rst
+++ b/source/plugins/cloudian-connector.rst
@@ -229,8 +229,7 @@ settings. To enable the connector, ensure that the global
setting
"cloudian.connector.enabled" is set to true. Finally, restart each of the
management server(s) to reload and enable the connector.
-For example, here is how you can restart the CloudStack management server
-installed on CentOS7:
+For example, here is how you can restart the CloudStack management server:
::
diff --git a/source/quickinstallationguide/qig.rst
b/source/quickinstallationguide/qig.rst
index be0ba6e..0fe2041 100644
--- a/source/quickinstallationguide/qig.rst
+++ b/source/quickinstallationguide/qig.rst
@@ -40,7 +40,8 @@ get you up and running with CloudStack with a minimum amount
of trouble.
The requirement is that you enable "Enable Nested VT-x/AMD-V" as the
Extended Feature on the System page of the Settings of the Instance.
You will want to create an Instance of "Red Hat (64-bit)" type and 40+GB
disk space.
You will need to have 1 NIC in your Instance, bridged to the NIC of your
laptop/desktop
- (wifi or wired NIC, doesn't matter), and optimally to set Adapter
Type="Paravirtualized Network (virtio-net)"
+ (bridging to a wireless adapter does frequently cause connectivity
issues, so avoid it, and instead bridge to the wired adapted),
+ and optimally to set Adapter Type="Paravirtualized Network (virtio-net)"
for somewhat better network performance (Settings of Instance, Network
section, Adapter1,
expand "Advanced"). Make sure the NIC on your Instance is configured as
promiscuous (in VirtualBox,
choose "Allow All" or just "Allow Instances" as the Promiscuous Mode),
so that it can pass traffic from
@@ -48,13 +49,11 @@ get you up and running with CloudStack with a minimum
amount of trouble.
enough CPU cores (3+) for demo purposes.
-High level overview of the process
+High-level overview of the process
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-This guide will focus on building a CloudStack cloud using KVM on CentOS
-7.9 with NFS storage and layer-2 isolation using VLANs,
-(flat home network can be used for this as well) and on a single piece of
-hardware (server/VM)
+This guide will focus on building a CloudStack cloud using KVM on an EL8
distro with NFS storage and layer-2 isolation using VLANs,
+(flat home network can be used for this as well) and on a single piece of
hardware (server/VM)
KVM, or Kernel-based Virtual Machine is a virtualization technology for the
Linux kernel. KVM supports native virtualization atop processors with hardware
@@ -68,8 +67,11 @@ To complete this guide you'll need the following items:
#. At least one computer which supports and has enabled hardware
virtualization.
-#. An `CentOS 7.9 minimal x86_64 install ISO, on bootable media
- <http://isoredirect.centos.org/centos/7/isos/x86_64/>`_
+#. A minimal EL8 distro like
+
+ #. Oracle Linux 8 - https://yum.oracle.com/oracle-linux-isos.html
+ #. Rocky Linux 8 - https://rockylinux.org/download
+ #. AlmaLinux OS 8 - https://almalinux.org/get-almalinux/
#. A /24 network with the gateway being at (e.g.) xxx.xxx.xxx.1, no DHCP is
needed
on this network and none of the computers running CloudStack will have a
@@ -86,8 +88,7 @@ CloudStack. We will go over the steps to prepare now.
Operating System
~~~~~~~~~~~~~~~~
-Using the CentOS 7.9.2009 minimal x86_64 install ISO, you'll need to install
-CentOS 7 on your hardware. The defaults will generally be acceptable for this
+Install preferred EL8 distro on your hardware. The defaults will generally be
acceptable for this
installation - but make sure to configure IP address/parameters so that you
can later install needed
packages from the internet. Later, we will change the Network configuration as
needed.
@@ -97,7 +98,7 @@ server - through SSH.
It is always wise to update the system before starting:
.. parsed-literal::
- # yum -y upgrade
+ # dnf -y upgrade
.. _conf-network:
@@ -105,14 +106,13 @@ It is always wise to update the system before starting:
Configuring the Network
^^^^^^^^^^^^^^^^^^^^^^^
-Before going any further, make sure that "bridge-utils" and "net-tools" are
installed and available:
-
-.. parsed-literal::
- # yum install bridge-utils net-tools -y
+Starting with EL8, we must use the Network Manager to configure all network
interfaces
+(instead of using the network-scripts we have used for so many years).
-Connecting via the console or SSH, you should login as root. We will start by
creating
-the bridge that Cloudstack will use for networking. Create and open
-/etc/sysconfig/network-scripts/ifcfg-cloudbr0 and add the following settings:
+We will start by creating the bridge that Cloudstack will use for networking.
+To avoid remote (ssh) disconnections, you should be logging to the server
locally,
+via console/physical screen (or save the commands below as a script and then
run it
+via remote ssh session)
.. note::
IP Addressing - Throughout this document we are assuming that you will have
@@ -126,56 +126,24 @@ the bridge that Cloudstack will use for networking.
Create and open
::
- DEVICE=cloudbr0
- TYPE=Bridge
- ONBOOT=yes
- BOOTPROTO=static
- IPV6INIT=no
- IPV6_AUTOCONF=no
- DELAY=5
- IPADDR=172.16.10.2 #(or e.g. 192.168.1.2)
- GATEWAY=172.16.10.1 #(or e.g. 192.168.1.1 - this would be your
physical/home router)
- NETMASK=255.255.255.0
- DNS1=8.8.8.8
- DNS2=8.8.4.4
- STP=yes
- USERCTL=no
- NM_CONTROLLED=no
-
-Save the configuration and exit. We will then edit the NIC so that it
-makes use of this bridge.
-
-Open the configuration file of your NIC (e.g.
/etc/sysconfig/network-scripts/ifcfg-eth0)
-and edit it as follows:
+ #create an "empty” bridge, add eth0 to the bridge, set static IP and
reactivate the whole configuration
+ nmcli connection add type bridge con-name cloudbr0 ifname cloudbr0
+ nmcli connection modify eth0 master cloudbr0
+ nmcli connection up eth0
+ nmcli connection modify cloudbr0 ipv4.addresses '172.16.10.2/24'
ipv4.gateway '172.16.10.1' ipv4.dns '8.8.8.8' ipv4.method manual && nmcli
connection up cloudbr0
.. note::
Interface name (eth0) used as example only. Replace eth0 with your default
ethernet interface name.
-.. parsed-literal::
- TYPE=Ethernet
- BOOTPROTO=none
- DEFROUTE=yes
- NAME=eth0
- DEVICE=eth0
- ONBOOT=yes
- BRIDGE=cloudbr0
-
-.. note::
- If your physical nic (eth0 in the case of our example) has already been
- setup before following this guide, make sure that there is no duplication
- between IP configuration of /etc/config/network-scripts/ifcfg-cloudbr0 and
- /etc/sysconfig/network-scripts/ifcfg-eth0 which will cause a failure that
- would prevent the network from starting. Basically, IP configuration
- of eth0 should be moved to the bridge and eth0 will be added to the bridge.
+Optionally, we can install the net-tools:
+.. parsed-literal::
+ # dnf install net-tools -y
-Now that we have the configuration files properly set up, we need to run a few
-commands to start up the network:
+Now that we have the configuration files properly set up, let's reboot:
.. parsed-literal::
- # systemctl disable NetworkManager; systemctl stop NetworkManager
- # systemctl enable network
# reboot
.. _conf-hostname:
@@ -197,23 +165,19 @@ At this point it will likely return:
localhost
-To rectify this situation - we'll set the hostname by editing the /etc/hosts
-file so that it follows a similar format to this example (remember to replace
-the IP with your IP which might be e.g. 192.168.1.2):
+To rectify this situation - we'll set the hostname so that it follows a
similar format to this example:
.. parsed-literal::
- 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
- ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
- 172.16.10.2 srvr1.cloud.priv
+ hostnamectl set-hostname server.local --static
-After you've modified that file, go ahead and restart the network using:
+After you've modified that file, go ahead and reboot:
.. parsed-literal::
- # systemctl restart network
+ # reboot
-Now recheck with the
+Now recheck the hostname with the
.. parsed-literal::
@@ -258,8 +222,8 @@ To ensure that it remains in that state we need to
configure the file
.. _conf-ntp:
-NTP
-^^^
+NTP (Chrony)
+^^^^^^^^^^^^
NTP configuration is a necessity for keeping all of the clocks in your cloud
servers in sync. However, NTP is not installed by default. So we'll install
@@ -267,15 +231,15 @@ and and configure NTP at this stage. Installation is
accomplished as follows:
.. parsed-literal::
- # yum -y install ntp
+ # dnf -y install chrony
The actual default configuration is fine for our purposes, so we merely need
to enable it and set it to start on boot as follows:
.. parsed-literal::
- # systemctl enable ntpd
- # systemctl start ntpd
+ # systemctl enable chronyd
+ # systemctl start chronyd
.. _qigconf-pkg-repo:
@@ -314,7 +278,7 @@ start out by installing nfs-utils.
.. parsed-literal::
- # yum -y install nfs-utils
+ # dnf -y install nfs-utils
We now need to configure NFS to serve up two different shares. This is handled
in the /etc/exports file. You should ensure that it has the following content:
@@ -333,31 +297,17 @@ appropriately on them with the following commands:
# mkdir -p /export/primary
# mkdir /export/secondary
-CentOS 7.x releases use NFSv4 by default. NFSv4 requires that domain setting
-matches on all clients. In our case, the domain is cloud.priv, so ensure that
-the domain setting in /etc/idmapd.conf is uncommented and set as follows:
+NFSv4 requires that domain setting matches on all clients. In our case, the
+domain is "local", so ensure that the domain setting in /etc/idmapd.conf is
uncommented and set as follows:
.. parsed-literal::
- Domain = cloud.priv
-
-Now you'll need to add the configuration values at the bottom in the file
-/etc/sysconfig/nfs (or merely uncomment and set them)
-
-.. parsed-literal::
-
- LOCKD_TCPPORT=32803
- LOCKD_UDPPORT=32769
- MOUNTD_PORT=892
- RQUOTAD_PORT=875
- STATD_PORT=662
- STATD_OUTGOING_PORT=2020
+ Domain = local
For simplicity, we need to disable the firewall, so that it will not block
connections.
.. note::
- Configuration of the firewall on CentOS7 is beyond the purview of this
- guide.
+ Configuration of the firewall is beyond the purview of this guide.
To do so, simply use the following two commands:
@@ -372,9 +322,9 @@ it on the host by executing the following commands:
.. parsed-literal::
# systemctl enable rpcbind
- # systemctl enable nfs
+ # systemctl enable nfs-server
# systemctl start rpcbind
- # systemctl start nfs
+ # systemctl start nfs-server
Management Server Installation
@@ -389,23 +339,13 @@ Database Installation and Configuration
We'll start with installing MySQL and configuring some options to ensure it
runs well with CloudStack.
-First, as CentOS 7 no longer provides the MySQL binaries, we need to add a
MySQL community repository,
-that will provide MySQL Server (and the Python MySQL connector later) :
-
.. parsed-literal::
- # yum -y install wget
- # wget http://repo.mysql.com/mysql-community-release-el7-5.noarch.rpm
- # rpm -ivh mysql-community-release-el7-5.noarch.rpm
-Install by running the following command:
+ # dnf -y install mysql-server
-.. parsed-literal::
-
- # yum -y install mysql-server
-
-This should install MySQL 5.x, as of the time of writing this guide.
+This should install MySQL 8.x, as of the time of writing this guide.
With MySQL now installed we need to make a few configuration changes to
-/etc/my.cnf. Specifically we need to add the following options to the [mysqld]
+/etc/my.cnf.d/mysql-server.cnf. Specifically, we need to add the following
options to the [mysqld]
section:
.. parsed-literal::
@@ -416,18 +356,6 @@ section:
log-bin=mysql-bin
binlog-format = 'ROW'
-.. note::
-
- For Ubuntu 16.04 and later, make sure you specify a ``server-id`` in your
``.cnf`` file for binary logging. Set the ``server-id`` according to your
database setup.
-
-.. parsed-literal::
-
- server-id=source-01
- innodb_rollback_on_timeout=1
- innodb_lock_wait_timeout=600
- max_connections=350
- log-bin=mysql-bin
- binlog-format = 'ROW'
Now that MySQL is properly configured we can start it and configure it to
start on boot as follows:
@@ -437,19 +365,6 @@ start on boot as follows:
# systemctl enable mysqld
# systemctl start mysqld
-
-MySQL Connector Installation
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
-Install Python MySQL connector from the MySQL community repository (which
we've added previously):
-
-.. parsed-literal::
-
- # yum -y install mysql-connector-python
-
-Please note that the previously required ``mysql-connector-java`` library is
now bundled with CloudStack
-Management server and is no longer required to be installed separately.
-
Installation
~~~~~~~~~~~~
@@ -458,7 +373,7 @@ following command:
.. parsed-literal::
- # yum -y install cloudstack-management
+ # dnf -y install cloudstack-management
CloudStack |version| requires Java 17 JRE. Installing the management server
will automatically install Java 17, but it's good to explicitly confirm that
Java 17
@@ -542,12 +457,11 @@ Installation
~~~~~~~~~~~~
Installation of the KVM agent is trivial with just a single command, but
-afterwards we'll need to configure a few things. We need to install the EPEL
repository also.
+afterwards we'll need to configure a few things.
.. parsed-literal::
- # yum -y install epel-release
- # yum -y install cloudstack-agent
+ # dnf -y install cloudstack-agent
KVM Configuration
@@ -599,6 +513,12 @@ and should already be installed.
#LIBVIRTD_ARGS="--listen"
+# As of EL8, we'll have to do the socket masking:
+
+ .. parsed-literal::
+
+ # systemctl mask libvirtd.socket libvirtd-ro.socket
libvirtd-admin.socket libvirtd-tls.socket libvirtd-tcp.socket
+
#. Restart libvirt
.. parsed-literal::
@@ -814,6 +734,7 @@ That's it, you are done with installation of your Apache
CloudStack demo cloud.
To check the health of your CloudStack installation, go to Infrastructure -->
System VMs and refresh
the UI from time to time - you should see “S-1-VM” and “V-2-VM” system VMs
(SSVM and CPVM) in State=Running and Agent State=Up
+
After that you can go to Images --> Templates, click on the built-in Template
named "CentOS 5.5(64-bit) no GUI (KVM)",
then click on "Zones" tab - and observe how the Status is moving from a few
percents downloaded up to fully downloaded,
after which the Status will show as "Download Complete" and "Ready" column
will say "Yes".
