From d3489d1b4bea8971c7c90cdc829c0e3fbb1aea9f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?H=C3=A9ctor=20Hurtado?= Date: Wed, 27 Nov 2019 10:08:10 +0100 Subject: [PATCH] Fix some formatting bugs 'The Project' section --- docs/source/the_project/quickstart.rst | 38 +++++++++++--------------- 1 file changed, 16 insertions(+), 22 deletions(-) diff --git a/docs/source/the_project/quickstart.rst b/docs/source/the_project/quickstart.rst index a538b1d..a55cc44 100644 --- a/docs/source/the_project/quickstart.rst +++ b/docs/source/the_project/quickstart.rst @@ -1,52 +1,46 @@ Quick start =========== - We'll explain a simple example to help you understand what Kapow! really does - and why it is awesome. +We'll explain a simple example to help you understand what Kapow! really does and why it is awesome. Scenario -------- - Consider that we're in a corporate network like the following one: +Consider that we're in a corporate network like the following one: - .. _quickstart_image: - .. image:: /_static/network.png - :align: center - :width: 80% +.. _quickstart_image: +.. image:: /_static/network.png + :align: center + :width: 80% - Our organization has an external host that act as a bridget between our - intranet an the public Internet. +Our organization has an external host that act as a bridget between our intranet an the public Internet. - **Our goal: We need to check if the** :samp:`Internal Host` **is alive.** +**Our goal: We need to check if the** :samp:`Internal Host` **is alive.** Limitations and constraints -------------------------- - 1. We **don't want** to **grant access** to the :samp:`External Host` to - anybody. - 2. We **don't want** to manage VPNs or any similar solutions to access to :samp:`Internal Host` from the Internet. - 3. We **want to limit the actions** that an user can perform in our intranet while it is checking if :samp:`Internal Host` is alive. - 4. We **want** to use the most standard mechanism. Easy to use and that facilitates the automation. - 5. We **don't have a budget** to invest in a custom solution. +1. We **don't want** to **grant access** to the :samp:`External Host` to anybody. +2. We **don't want** to manage VPNs or any similar solutions to access to :samp:`Internal Host` from the Internet. +3. We **want to limit the actions** that an user can perform in our intranet while it is checking if :samp:`Internal Host` is alive. +4. We **want** to use the most standard mechanism. Easy to use and that facilitates the automation. +5. We **don't have a budget** to invest in a custom solution. What options we have? --------------------- - Alter analyzyng the problem and our goal we conclude that is enough - **to use a simple** :samp:`ping` **to** :samp:`Internal Host`. +Alter analyzyng the problem and our goal we conclude that is enough **to use a simple** :samp:`ping` **to** :samp:`Internal Host`. - So, the next step is to **analyze how to perform the ping.** +So, the next step is to **analyze how to perform the ping.** Accessing via SSH to :samp:`External Host` ++++++++++++++++++++++++++++++++++++++++++ - If we choose this option then we need to create a user and grant him access - via :samp:`SSH` to :samp:`External Host` for every person that needs to - check for :samp:`Internal host` status. + If we choose this option then we need to create a user and grant him access via :samp:`SSH` to :samp:`External Host` for every person that needs to check for :samp:`Internal host` status. Conclusion: **Not a good idea**