Dark-Alex-17/kapow
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix some formatting bugs 'The Project' section

Browse Source
This commit is contained in:
Héctor Hurtado
2019-11-27 10:08:10 +01:00
parent 1e0ba8d7e8
commit d3489d1b4b
1 changed files with 16 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/source/the_project/quickstart.rst
+16 -22
View File
@@ -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**