Project

General

Profile

« Previous | Next » 

Revision 2a39e0f3

Added by Alexis Mousset over 7 years ago

Fixes #9887: Prepare manual for 4.1

View differences:

10_installation/10_install_server/11_install_root_server_debian.txt
----
echo "deb http://www.rudder-project.org/apt-4.0/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/rudder.list
echo "deb http://www.rudder-project.org/apt-4.1/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/rudder.list
apt-get update
----
10_installation/10_install_server/12_install_root_server_sles.txt
----
zypper ar -n "Rudder SLES repository" http://www.rudder-project.org/rpm-4.0/SLES_11/ Rudder
zypper ar -n "Rudder SLES repository" http://www.rudder-project.org/rpm-4.1/SLES_11/ Rudder
zypper refresh
----
10_installation/10_install_server/13_install_root_server_centos_rhel.txt
----
echo '[Rudder_4.0]
name=Rudder 4.0 EL repository
baseurl=http://www.rudder-project.org/rpm-4.0/RHEL_$releasever/
echo '[Rudder_4.1]
name=Rudder 4.1 EL repository
baseurl=http://www.rudder-project.org/rpm-4.1/RHEL_$releasever/
gpgcheck=1
gpgkey=http://www.rudder-project.org/rpm-4.0/RHEL_$releasever/repodata/repomd.xml.key' > /etc/yum.repos.d/rudder.repo
gpgkey=http://www.rudder-project.org/rpm-4.1/RHEL_$releasever/repodata/repomd.xml.key' > /etc/yum.repos.d/rudder.repo
----
10_installation/11_install_agent/10_install_agent_debian.txt
----
echo "deb http://www.rudder-project.org/apt-4.0/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/rudder.list
echo "deb http://www.rudder-project.org/apt-4.1/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/rudder.list
----
10_installation/11_install_agent/20_install_agent_centos_rhel.txt
----
echo '[Rudder_4.0]
name=Rudder 4.0 EL repository
baseurl=http://www.rudder-project.org/rpm-4.0/RHEL_$releasever/
echo '[Rudder_4.1]
name=Rudder 4.1 EL repository
baseurl=http://www.rudder-project.org/rpm-4.1/RHEL_$releasever/
gpgcheck=1
gpgkey=http://www.rudder-project.org/rpm-4.0/RHEL_$releasever/repodata/repomd.xml.key' > /etc/yum.repos.d/rudder.repo
gpgkey=http://www.rudder-project.org/rpm-4.1/RHEL_$releasever/repodata/repomd.xml.key' > /etc/yum.repos.d/rudder.repo
----
......
====
The RPM can be directly downloaded for a standalone installation,
from the following URL: http://www.rudder-project.org/rpm-4.0/RHEL_7/
from the following URL: http://www.rudder-project.org/rpm-4.1/RHEL_7/
(or RHEL_6, RHEL_5, etc, depending on your host's OS version)
====
......
----
yum install rudder-agent-4.0.0-1.EL.7.x86_64.rpm
yum install rudder-agent-4.1.0-1.EL.7.x86_64.rpm
----
10_installation/11_install_agent/30_install_agent_suse.txt
----
zypper ar -n 'Rudder SLES 12 repository' http://www.rudder-project.org/rpm-4.0/SLES_12/ Rudder
zypper ar -n 'Rudder SLES 12 repository' http://www.rudder-project.org/rpm-4.1/SLES_12/ Rudder
----
......
----
zypper ar -n 'Rudder SLES repository' http://www.rudder-project.org/rpm-4.0/SLES_11_SP1/ Rudder
zypper ar -n 'Rudder SLES repository' http://www.rudder-project.org/rpm-4.1/SLES_11_SP1/ Rudder
----
......
----
zypper sa 'http://www.rudder-project.org/rpm-4.0/SLES_10_SP3/' Rudder
zypper sa 'http://www.rudder-project.org/rpm-4.1/SLES_10_SP3/' Rudder
----
12_upgrade/00_upgrade.txt
== Upgrade
This short chapter covers the upgrade of the Rudder Server Root and Rudder Agent
from older versions to the latest version, 4.0.
from older versions to the latest version, 4.1.
The upgrade is quite similar to the installation.
......
upgrade procedures manually, but you will note that several data migrations
occur during the upgrade process.
==== Upgrade from Rudder 3.1 or 3.2
==== Upgrade from Rudder 3.1, 3.2 or 4.0
Migration from 3.1 or 3.2 are supported, so you can upgrade directly to 4.0.
Migration from 3.1, 3.2 or 4.0 are supported, so you can upgrade directly to 4.1.
[WARNING]
......
In Rudder 4.0, we changed the default communication protocol between agent and server,
but still stay compatible with the old protocol. Hence, you can perfectly keep using
pre-4.0 agents with a 4.0 server.
pre-4.0 agents with a 4.0 or 4.1 server.
However, some networking issues may appear when using 4.0 agents with older servers with the
However, some networking issues may appear when using 4.0 or 4.1 agents with older servers with the
reverse DNS lookup option disabled in the settings (*Security* ->
*Use reverse DNS lookups on nodes to reinforce authentication to policy server*).
Therefore, you need to upgrade your server to 4.0 *before* upgrading the nodes so that the
Therefore, you need to upgrade your server to 4.1 *before* upgrading the nodes so that the
configuration distributed to the nodes include the use of the new protocol.
====
==== Upgrade from Rudder 3.0 or older
Direct upgrades from 3.0.x and older are no longer supported on 4.0.
Direct upgrades from 3.0.x and older are no longer supported on 4.1.
If you are still running one of those, either on servers or nodes,
please first upgrade to one of the supported versions above, and then upgrade to 4.0.
please first upgrade to one of the supported versions above, and then upgrade to 4.1.
12_upgrade/05_caution.txt
=== Caution cases
==== Compatibility between Rudder agent 4.0 and older server versions
==== Compatibility between Rudder agent 4.1 and older server versions
===== 4.0.x servers
Rudder agents 4.1.x are compatible with 4.0 Rudder servers.
===== 3.1.x and 3.2.x servers
Rudder agents 4.0.x are not compatible with Rudder servers older than 4.0.0.
You need to upgrade your server to 4.0 before the agents.
Rudder agents 4.1.x are not compatible with Rudder servers older than 4.0.0.
You need to upgrade your server to 4.1 before the agents.
==== Compatibility between Rudder server 4.0 and older agent versions
==== Compatibility between Rudder server 4.1 and older agent versions
===== 3.1.x and 3.2.x agents
===== 3.1.x, 3.2.x and 4.0.x agents
As they use a compatible CFEngine version, Rudder agent 3.1.x and 3.2.x are fully compatible with Rudder server 4.0.x. It is therefore not strictly necessary to update your agents to 4.0.x.
As they use a compatible CFEngine version, Rudder agent 3.1.x, 3.2.x and 4.0.x are fully compatible with Rudder server 4.1.x. It is therefore not strictly necessary to update your agents to 4.1.x.
===== 3.0.x or older
These agents are not compatible with Rudder 4.0, and you have to upgrade them.
These agents are not compatible with Rudder 4.1, and you have to upgrade them.
Be careful to follow the upgrade path explained <<_upgrade_from_rudder_3_0_or_older, above>>.
==== Protocol for reporting
12_upgrade/10_upgrade_debian.txt
----
echo "deb http://www.rudder-project.org/apt-4.0/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/rudder.list
echo "deb http://www.rudder-project.org/apt-4.1/ $(lsb_release -cs) main" > /etc/apt/sources.list.d/rudder.list
----
12_upgrade/20_upgrade_rhel.txt
----
echo '[Rudder_4.0]
name=Rudder 4.0 Repository
baseurl=http://www.rudder-project.org/rpm-4.0/RHEL_$releasever/
echo '[Rudder_4.1]
name=Rudder 4.1 Repository
baseurl=http://www.rudder-project.org/rpm-4.1/RHEL_$releasever/
gpgcheck=1
gpgkey=http://www.rudder-project.org/rpm-4.0/RHEL_$releasever/repodata/repomd.xml.key' > /etc/yum.repos.d/rudder.repo
gpgkey=http://www.rudder-project.org/rpm-4.1/RHEL_$releasever/repodata/repomd.xml.key' > /etc/yum.repos.d/rudder.repo
----
12_upgrade/30_upgrade_suse.txt
----
zypper ar -n "Rudder SLES repository" http://www.rudder-project.org/rpm-4.0/SLES_11_SP1/ Rudder
zypper ar -n "Rudder SLES repository" http://www.rudder-project.org/rpm-4.1/SLES_11_SP1/ Rudder
----
......
----
zypper sa "http://www.rudder-project.org/rpm-4.0/SLES_10_SP3/" Rudder
zypper sa "http://www.rudder-project.org/rpm-4.1/SLES_10_SP3/" Rudder
----

Also available in: Unified diff