-
Notifications
You must be signed in to change notification settings - Fork 19
WIP: PED10891-Ansible-basics #544
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
@dariavladykina please review thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Amrita,
so far these suggestions. Thanks!
| <merge> | ||
| <title>Ansible core</title> | ||
| <revhistory xml:id="rh-ansible"> | ||
| <revision><date>2025-06-19</date> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <revision><date>2025-06-19</date> | |
| <revision><date>2025-11-04</date> |
|
|
||
| <!-- Productname & Version --> | ||
| <meta name="productname" its:translate="no"> | ||
| <productname version="16">&sles;</productname> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <productname version="16">&sles;</productname> | |
| <productname version="16.0" os="sles;sles4sap">&productname;</productname> |
| <!-- S T R U C T U R E --> | ||
| <structure renderas="article" xml:id="ansible" xml:lang="en"> | ||
| <merge> | ||
| <title>Ansible core</title> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <title>Ansible core</title> | |
| <title>Introduction to Ansible</title> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Feel free to change, however, as a beginner I wouldn't know what Ansible core is, so I'd search for Introduction or Getting started.
| </meta> | ||
|
|
||
| <!-- Social Media --> | ||
| <meta name="title" its:translate="yes">Ansible automation platform</meta> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The title must be the same as the article title.
| <term>WHAT?</term> | ||
| <listitem> | ||
| <para> | ||
| This article gives an introduction to Ansible and guides you on how to automate repetitive IT tasks. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd leave the first sentence from here as it mentioned in the Why?
| This article gives an introduction to Ansible and guides you on how to automate repetitive IT tasks. |
| <listitem> | ||
| <para>Variables can be assigned to all hosts within a specific group. | ||
| These are defined under the group name using a <literal>:vars</literal> suffix. For example:</para> | ||
| <screen>[webservers:vars] |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like INI format to me.
| <varlistentry> | ||
| <term><emphasis>Group variables</emphasis> </term> | ||
| <listitem> | ||
| <para>Variables can be assigned to all hosts within a specific group. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The description is the same as for the INI file, but I don't think there is any :vars suffix in YAML.
| <para> | ||
| Ansible provides ad-hoc commands and several utilities to perform various operation and automation | ||
| tasks. Ad-hoc commands in Ansible are useful for performing quick and one-off tasks that do not need to be saved for future use. | ||
| They are single line commands executed directly from the command line. Ad-hoc commands use the <literal>ansible</literal> CLI tool. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
These 2 sentences should be better placed in the subsection ad-ho commands. Also consider creating a separate section for playbooks. Those 2 are basically alternatives, right? If so, they deserve the same attention - either 2 subsections, or everything written in the section intro.
| <title>Using roles</title> | ||
| <para>You can use the role in the following ways:</para> | ||
| <itemizedlist> | ||
| <listitem><para>At the play level with the <literal>roles</literal>: This is the default way of using roles in a play.</para> </listitem> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bear in mind that newbie has no idea what a play is.
| </section> | ||
| <section xml:id="about-variables"> | ||
| <title>About variables</title> | ||
| <para>With Ansible, you can run tasks and playbooks with a single command. You can define these variables using standard YAML syntax (including lists and dictionaries) in your playbooks, inventories, roles, or at the command line. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is a variable should be IMHO mentioned here. I don't know about which variables this is.
| <para>With Ansible, you can run tasks and playbooks with a single command. You can define these variables using standard YAML syntax (including lists and dictionaries) in your playbooks, inventories, roles, or at the command line. | |
| <para>You can define these variables using standard YAML syntax (including lists and dictionaries) in your playbooks, inventories, roles, or at the command line. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Amrita, please see some linguistic things for the content. Also, I couldn't review the DC-SAP-Ansible article as it built the SLES one for me. Thanks!
| <!-- S T R U C T U R E --> | ||
| <structure renderas="article" xml:id="ansible" xml:lang="en"> | ||
| <merge> | ||
| <title>Ansible core</title> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest an extended title, e.g. Ansible Core Installation Configuration and Automation Basics
| </meta> | ||
|
|
||
| <!-- Social Media --> | ||
| <meta name="title" its:translate="yes">Ansible automation platform</meta> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <meta name="title" its:translate="yes">Ansible automation platform</meta> | |
| <meta name="title" its:translate="yes">Ansible automation platform for IT task automation</meta> |
|
|
||
| <!-- Social Media --> | ||
| <meta name="title" its:translate="yes">Ansible automation platform</meta> | ||
| <meta name="social-descr" its:translate="yes">Learn how to automate IT tasks using Ansible</meta> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <meta name="social-descr" its:translate="yes">Learn how to automate IT tasks using Ansible</meta> | |
| <meta name="social-descr" its:translate="yes">Learn how to simplify IT tasks and system management using Ansible automation platform</meta> |
| <meta name="social-descr" its:translate="yes">Learn how to automate IT tasks using Ansible</meta> | ||
|
|
||
| <!-- Search --> | ||
| <meta name="description" its:translate="yes">Save time by using Ansible automation platform.</meta> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <meta name="description" its:translate="yes">Save time by using Ansible automation platform.</meta> | |
| <meta name="description" its:translate="yes">Use Ansible automation platform to efficiently automate IT tasks</meta> |
| Learn how to automate IT infrastructure with Ansible; how to install and configure, create | ||
| an inventory file and a playbook. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| Learn how to automate IT infrastructure with Ansible; how to install and configure, create | |
| an inventory file and a playbook. | |
| Learn how to automate IT infrastructure with Ansible, from installation and configuration | |
| to creating inventory files and playbooks. |
| <important> | ||
| <itemizedlist> | ||
| <listitem><para>Python and Ansible versions in the control and managed nodes must be compatible.</para></listitem> | ||
| <listitem><para>Third party software is not supported.</para></listitem> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <listitem><para>Third party software is not supported.</para></listitem> | |
| <listitem><para>Third-party software is not supported.</para></listitem> |
| <itemizedlist> | ||
| <listitem><para>Python and Ansible versions in the control and managed nodes must be compatible.</para></listitem> | ||
| <listitem><para>Third party software is not supported.</para></listitem> | ||
| <listitem><para>Only versions provided in packages which installs into System Python are supported. </para></listitem> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| <listitem><para>Only versions provided in packages which installs into System Python are supported. </para></listitem> | |
| <listitem><para>Only versions provided in packages that install into System Python are supported. </para></listitem> |
| <itemizedlist> | ||
| <listitem> | ||
| <para> | ||
| <link xlink:href="https://docs.ansible.com/ansible-core/devel/index.html">The official source for Ansible core. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please turn this into a regular sentence as there's only 1 item - too few for a list.
| xmlns:xlink="http://www.w3.org/1999/xlink" | ||
| xmlns:trans="http://docbook.org/ns/transclusion"> | ||
| <info> | ||
| <title>Installing and running a &sles4sap; 16 Ansible playbook</title> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure but I couldn't see this part in the output when I built DC-SAP-Ansible
| <!-- S T R U C T U R E --> | ||
| <structure renderas="article" xml:id="intro-sap-ansible" xml:lang="en"> | ||
| <merge> | ||
| <title>Introduction to Ansible automation for &sles4sap; 16</title> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wasn't able to build this DC file for SAP
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Amrita, please see some linguistic things for the content. Also, I couldn't review the DC-SAP-Ansible article as it built the SLES one for me. Thanks!
PR creator: Description
Describe the overall goals of this pull request.
PR creator: Are there any relevant issues/feature requests?
PR reviewer: Checklist for editorial review
Apart from the usual checks, please double-check also the following: