php 8 install ansible
🐧 Как установить Ansible на CentOS / RHEL 8
Ansible – это бесплатный инструмент автоматизации с открытым исходным кодом, который позволяет системным администраторам настраивать и контролировать сотни узлов с центрального сервера без необходимости установки каких-либо агентов на узлах.
Для связи с удаленными узлами используется протокол SSH.
По сравнению с другими инструментами управления, такими как Puppet и Chef, Ansible является фаворитом благодаря простоте использования и установки.
В этом руководстве вы узнаете, как установить и настроить инструмент автоматизации Ansible в дистрибутиве RHEL / CentOS 8 Linux.
Шаг 1: Установка Python3
Обычно RHEL 8 и CentOS 8 поставляются с Python3, уже установленным по умолчанию.
Однако, если по какой-либо причине Python3 не установлен, установите его с помощью следующих команд dnf.
Убедитесь, что вы должны войти в систему как обычный пользователь с правами Sudo.
Чтобы убедиться, что у вас действительно установлен python3, выполните команду.
Шаг 2: Установка PIP – установщик пакетов Python
Pip – это менеджер пакетов Python, который также предустановлен, но, опять же, если Pip отсутствует в вашей системе, установите его с помощью команды.
Шаг 3: Установка Ansible
После выполнения всех необходимых условий установите ansible, выполнив команду.
Php 8 install ansible
Installs PHP on RedHat/CentOS and Debian/Ubuntu servers.
If you’re using an older LTS release of Ubuntu or RHEL, with an old/outdated version of PHP, you need to use a repo or PPA with a maintained PHP version, as this role only works with PHP versions that are currently supported by the PHP community.
Available variables are listed below, along with default values (see defaults/main.yml ):
Note: If you’re using Debian/Ubuntu, you also need to install libapache2-mod-fastcgi (for cgi/PHP-FPM) or libapache2-mod-php7.0 (or a similar package depending on PHP version) if you want to use mod_php with Apache.
A list of extra PHP packages to install without overriding the default list.
If your usage of PHP is tied to a web server (e.g. Apache or Nginx), leave this default value. If you are using PHP server-side or to run some small application, set this value to false so this role doesn’t attempt to interact with a web server.
The default values for the HTTP server deamon are httpd (used by Apache) for RedHat/CentOS, or apache2 (also used by Apache) for Debian/Ubuntu. If you are running another webserver (for example, nginx ), change this value to the name of the daemon under which the webserver runs.
(RedHat/CentOS only) If you have enabled any additional repositories (might I suggest geerlingguy.repo-epel or geerlingguy.repo-remi), those repositories can be listed under this variable (e.g. remi-php70,epel ). This can be handy, as an example, if you want to install the latest version of PHP 7.0, which is in the Remi repository.
If you’d like to be able to switch PHP versions easily, or use a version that’s not available in system packages: You can use the geerlingguy.php-versions role to more easily switch between major PHP versions (e.g. 5.6, 7.1, 7.2).
The executable to run when calling PHP from the command line. You should only change this if running php on your server doesn’t target the correct executable, or if you’re using software collections on RHEL/CentOS and need to target a different version of PHP.
PHP-FPM is a simple and robust FastCGI Process Manager for PHP. It can dramatically ease scaling of PHP apps and is the normal way of running PHP-based sites and apps when using a webserver like Nginx (though it can be used with other webservers just as easily).
When using this role with PHP running as php-fpm instead of as a process inside a webserver (e.g. Apache’s mod_php ), you need to set the following variable to true :
If you’re using Apache, you can easily get it configured to work with PHP-FPM using the geerlingguy.apache-php-fpm role.
Control over the fpm daemon’s state; set these to stopped and false if you want FPM to be installed and configured, but not running (e.g. when installing in a container).
The handler restarts PHP-FPM by default. Setting the value to reloaded will reload the service, intead of restarting it.
List of PHP-FPM pool to create. By default, www pool is created. To setup a new pool, add an item to php_fpm_pools list.
By default, all the extra defaults below are applied through the php.ini included with this role. You can self-manage your php.ini file (if you need more flexility in its configuration) by setting this to false (in which case all the below variables will be ignored).
The OpCache is included in PHP starting in version 5.5, and the following variables will only take effect if the version of PHP you have installed is 5.5 or greater.
The platform-specific opcache configuration filename. Generally the default should work, but in some cases, you may need to override the filename.
Whether to enable APCu. Other APCu variables will be ineffective if this is set to false.
APCu ini directives that are often customized on a system. Set the php_apc_shm_size so it will hold all cache entries in memory with a little overhead (fragmentation or APC running out of memory will slow down PHP dramatically).
The platform-specific APC configuration filename. Generally the default should work, but in some cases, you may need to override the filename.
Ensuring APC is installed
If you use APC, you will need to make sure APC is installed (it is installed by default, but if you customize the php_packages list, you need to include APC in the list):
Installing from Source
If you need a specific version of PHP, or would like to test the latest (e.g. master) version of PHP, there’s a good chance there’s no suitable package already available in your platform’s package manager. In these cases, you may choose to install PHP from source by compiling it directly.
Note that source compilation takes much longer than installing from packages (PHP HEAD takes 5+ minutes to compile on a modern quad-core computer, just as a point of reference).
Set this to true to install PHP from source instead of installing from packages.
The version of PHP to install from source (a git branch, tag, or commit hash).
Location where source will be cloned and installed, and the location of the GMP header file (which can be platform/distribution specific), and mysql_config binary (this may be mariadb_config in newer operating system versions).
A few other notes/caveats for specific configurations:
Ansible: миграция RTFM 2.11 — хост Services — установка PHP, PHP-FPM
Продолжаем миграцию.
Теперь можно приступить к настройке первого из «внутренних» серверов — начну с Services, т.к. он будет основным из всех трёх по количеству служб, которые на нём будут работать.
Сегодня планируется выполнить:
В целом схема сейчас вырисовывается такая:
(забегая наперёд: нет — пришлось прикручивать AWS EFS)
Получившаяся в результате роль есть в Гитхабе, пока в отдельном бранче, тут>>>, как и другие изменения, которые были сделаны в процессе написания этого поста.
data-disk
Сейчас EBS подключен (во время создания CloudFormation стека), но раздела на нём ещё нет:
Создаём файловую систему:
С диском на этом пока всё — остальное выполнит Ansbile.
Services inventory
Домен services.dev.rtfm.co.ua уже добавлен, и направлен на IP в приватной сети:
Пока — вручную, у регистратора, Freehost.com.ua, потом rtfm.co.ua мигрирует на AWS Route53, и IP будет задаваться через CloudFormation.
Теперь добавим Services хост в inventory файл — hosts :
В data_volume_id — указываем разел data-диска, см. тут>>>, а в set_hostname — имя хоста, см. тут>>>.
ОК, подключение есть — можно создавать плейбук.
Services playbook
Убираем лишнее, оставляем роли:
Ansible: условия выполнения — register и when
Следующей задачей тут добавим немного вывода на консоль:
Собственно — вот условие выполнения:
when: nginx_conf_d.stat.islnk is defined
Если каталог найден — то задача выполняется.
Аналогично применяем условие в Copy stub_status.conf:
Что бы не указывать сейчас host_key каждый раз — закинем его в переменную (в Jenkins будет в параметрах):
И ключ для Amplify-агента:
Данные в NGINX Amplify:
Ansible PHP и PHP-FPM
Одним из основных сервисов на Services будет PHP-FPM.
Конфиги будут храниться на подключаемом data-диске, поэтому в роль Ansible надо добавить только его установку и копирование дефолтного файла настроек.
Создадим свою роль для установки и настройки PHP и PHP-FPM:
Актуальная на сегодня версия PHP — 7, все пакеты установятся для неё.
Добавляем роль в rtfm-blog-ansible-services-provision.yml :
Запускаем для проверки, потом добавим остальное:
ОК, проверяем на хосте:
Сейчас PHP-FPM слушает только локальные сокеты, но т.к. NGINX и PHP у нас на разных хостах — надо включить TCP порты.
В нём добавляем конфиг /data/data-php-fpm.d/dev.rtfm.co.ua.conf :
Тут сразу видно — чего не хватает в роли php-fpm :
И тут загвоздка… Добавить создание пользователей можно через роль Ansible, но она у меня в Github-е, а светить всех пользователей — идея так себе.
Добавляем в roles/php-fpm/tasks/main.yml :
Проверяем на хосте:
Аналогично можно будет сделать для всех секретных переменных, но не сейчас. Ссылка на документацию тут>>>.
Последним — перезапускаем php-fpm на хосте:
Тут, кстати, сразу возможная бага в будущем: когда unattended-upgrades обновит PHP-FPM на хосте — имя сервиса поменяется, и при запуске Ansible на этой задаче упадёт провижен. Но будем решать проблемы по мере возникновения, пока хочется закончить с общей настройкой.
Install PHP 8.0 on Centos 7 using Ansible – How to do
Wondering how to install PHP 8.0 on Centos 7 using Ansible? We can help you!
Here at Bobcares, we often handle requests from our customers to Install PHP 8.0 as a part of our Server Management Services.
Today we will see how our Support Engineers do this using Ansible for our customers.
How to install PHP 8.0 on Centos 7 using Ansible
Generally, the base repository of Centos 7 does not have PHP 8.0 package on it. So to install PHP 8.0 we will use Remi-repository.
Following are the steps for installation:
1. Firstly, we need to set up Remi-repository on the target machine.
2. Then we can list the available PHP module streams with the following command:
3. After this we need to enable this module before installing PHP 8.0. To enable it we can use the following:
4. Finally, we can install PHP 8.0 depending upon the webserver as given below:
PHP 8.0 for Apache
PHP 8.0 for Nginx
Though the above steps can be done easily on a single CentOS machine quickly, it becomes tedious when we wish to deploy it on hundreds of servers at the same time.
However, using ansible, the process can be automated and done hassle-free.
Steps for PHP 8.0 Installation using Ansible:
When we have Ansible set up and ready we can do the following steps for installing PHP 8.0 on Centos 7
1. First we need to create a playbook named ‘php_8_centos.yml’ using the following command:
2. Then add the following lines into the playbook:
Expected Output :
[Need assistance? We can help you]
Conclusion
To conclude, we saw the steps that our Support Techs follow to Install PHP 8.0 on Centos 7 using Ansible for our customers.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
Installing Ansible¶
Ansible is an agentless automation tool that you install on a control node. From the control node, Ansible manages machines and other devices remotely (by default, over the SSH protocol).
To install Ansible for use at the command line, simply install the Ansible package on one machine (which could easily be a laptop). You do not need to install a database or run any daemons. Ansible can manage an entire fleet of remote machines from that one control node.
Prerequisites¶
Before you install Ansible, review the requirements for a control node. Before you use Ansible, review the requirements for managed nodes (those end devices you want to automate). Control nodes and managed nodes have different minimum requirements.
Control node requirements¶
For your control node (the machine that runs Ansible), you can use any machine with Python 2 (version 2.7) or Python 3 (versions 3.5 and higher) installed. ansible-core 2.11 and Ansible 4.0.0 will make Python 3.8 a soft dependency for the control node, but will function with the aforementioned requirements. ansible-core 2.12 and Ansible 5.0.0 will require Python 3.8 or newer to function on the control node. Starting with ansible-core 2.11, the project will only be packaged for Python 3.8 and newer. This includes Red Hat, Debian, CentOS, macOS, any of the BSDs, and so on. Windows is not supported for the control node, read more about this in Matt Davis’s blog post.
Please note that some plugins that run on the control node have additional requirements. These requirements should be listed in the plugin documentation.
When choosing a control node, remember that any management system benefits from being run near the machines being managed. If you are using Ansible to manage machines in a cloud, consider using a machine inside that cloud as your control node. In most cases Ansible will perform better from a machine on the cloud than from a machine on the open Internet.
Ansible 2.11 will make Python 3.8 a soft dependency for the control node, but will function with the aforementioned requirements. Ansible 2.12 will require Python 3.8 or newer to function on the control node. Starting with Ansible 2.11, the project will only be packaged for Python 3.8 and newer.
Managed node requirements¶
Please note that some modules have additional requirements that need to be satisfied on the ‘target’ machine (the managed node). These requirements should be listed in the module documentation.
If you have SELinux enabled on remote nodes, you will also want to install libselinux-python on them before using any copy/file/template related functions in Ansible. You can use the yum module or dnf module in Ansible to install this package on remote systems that do not have it.
By default, before the first Python module in a playbook runs on a host, Ansible attempts to discover a suitable Python interpreter on that host. You can override the discovery behavior by setting the ansible_python_interpreter inventory variable to a specific interpreter, and in other ways. See Interpreter Discovery for details.
Selecting an Ansible artifact and version to install¶
Starting with version 2.10, Ansible distributes two artifacts: a community package called ansible and a minimalist language and runtime called ansible-core (called ansible-base in version 2.10). Choose the Ansible artifact and version that matches your particular needs.
Installing the Ansible community package¶
The ansible package includes the Ansible language and runtime plus a range of community curated Collections. It recreates and expands on the functionality that was included in Ansible 2.9.
You can choose any of the following ways to install the Ansible community package:
Install the latest release with your OS package manager (for Red Hat Enterprise Linux (TM), CentOS, Fedora, Debian, or Ubuntu).
Install with pip (the Python package manager).
Installing ansible-core ¶
Ansible also distributes a minimalist object called ansible-core (or ansible-base in version 2.10). It contains the Ansible language, runtime, and a short list of core modules and other plugins. You can build functionality on top of ansible-core by installing collections from Galaxy, Automation Hub, or any other source.
You can choose any of the following ways to install ansible-core :
Install ansible-core from source from the ansible/ansible GitHub repository to access the development ( devel ) version to develop or test the latest features.
Ansible generally creates new releases twice a year. See Releases and maintenance for information on release timing and maintenance of older releases.
Installing and upgrading Ansible with pip ¶
Prerequisites: Installing pip ¶
If pip is not already available on your system, run the following commands to install it:
You may need to perform some additional configuration before you are able to run Ansible. See the Python documentation on installing to the user site for more information.
Installing Ansible with pip ¶
Once pip is installed, you can install Ansible 1:
If you wish to install Ansible globally, run the following commands:
Installing Ansible in a virtual environment with pip ¶
Ansible can also be installed inside a new or existing virtualenv :
Upgrading Ansible with pip ¶
Upgrading from 2.9 or earlier to 2.10¶
Starting in version 2.10, Ansible is made of two packages. When you upgrade from version 2.9 and older to version 2.10 or later, you need to uninstall the old Ansible version (2.9 or earlier) before upgrading. If you do not uninstall the older version of Ansible, you will see the following message, and no change will be performed:
As explained by the message, to upgrade you must first remove the version of Ansible installed and then install it to the latest version.
Upgrading from Ansible 3 or ansible-core 2.10¶
To upgrade to ansible-core :
To upgrade to Ansible 4:
Installing Ansible on specific operating systems¶
Follow these instructions to install the Ansible community package on a variety of operating systems.