Skip to content
This repository has been archived by the owner on Apr 22, 2024. It is now read-only.

Commit

Permalink
Merge pull request #526 from macartur/fix_tests
Browse files Browse the repository at this point in the history
Fix sphinx title markers on documentation
  • Loading branch information
diraol committed Jul 12, 2017
2 parents 7cd99f3 + 2f0079f commit 04bba53
Show file tree
Hide file tree
Showing 8 changed files with 25 additions and 17 deletions.
12 changes: 7 additions & 5 deletions docs/administrator/architecture.rst
@@ -1,12 +1,12 @@
Architecture Overview
---------------------
*********************

*Kytos* is a modular SDN controller, composed by the *Kytos Core*
and by applications called *Networks Applications* (or *napp*), which means
it has several parts that working together will compose a Kytos Controller.

Kytos Core
++++++++++
==========

The *Kytos Core* is responsible for the main core operations of the
controller like keeping track of the connected switches, enabling,
Expand All @@ -19,11 +19,13 @@ A web interface is being developed to manage the controller. This web
interface aims to be intuitive and very easy to use.

Network Applications
++++++++++++++++++++
====================

The *napps* can be divided into two categories, *kytos napps* and *user napps*.

kytos napps
~~~~~~~~~~~
-----------

The *kytos napps* are those needed for the controller to deal with main
operations with a switch using a certain protocol. ex:
- *of_core napp* is responsible for providing interaction
Expand All @@ -42,7 +44,7 @@ Several core applications were developed. Kytos's developer team is
constantly developing new core application to improve Kytos's features.

user napps
~~~~~~~~~~
----------
The applications stack are general applications, created by Kytos’s users.
These applications can be installed, loaded and unloaded on the fly by the
user. Also, these applications make use of the OpenFlow library and information
Expand Down
4 changes: 2 additions & 2 deletions docs/administrator/configuration.rst
@@ -1,5 +1,5 @@
Configuration
-------------
*************

*Kyco* has several configuration parameters that allows the user to setup the
controller according to his needs. To configure the *Kyco* you can edit the
Expand Down Expand Up @@ -31,7 +31,7 @@ The following parameters are available at ``/etc/kyco/kyco.conf``:
+-------------+---------------+--------------------------+

Parameters Description
^^^^^^^^^^^^^^^^^^^^^^
======================

This section describes all available parameters that can be used during the
*Kyco* startup. Please note that some parameters are available only at command
Expand Down
2 changes: 1 addition & 1 deletion docs/administrator/index.rst
Expand Up @@ -3,7 +3,7 @@ Administrator Guide
###################

Welcome to the **Administrator Guide**, here you will find all information and
references about *Kythos*.
references about *Kytos*.

.. include:: intro.rst

Expand Down
2 changes: 2 additions & 0 deletions docs/administrator/logging_and_troubleshooting.rst
@@ -1,3 +1,5 @@
:orphan:

Logging and troubleshooting
---------------------------

Expand Down
8 changes: 4 additions & 4 deletions docs/administrator/napps_management.rst
@@ -1,5 +1,5 @@
NApps management
----------------
****************

As mentioned earlier, *Kyco* is composed of several modules. One of these
modules is the Network Application (Napp), which can be a core Napp,
Expand All @@ -10,7 +10,7 @@ installing, removing and enable or disable).
.. note:: The procedure described here is temporary. It will be updated accordingly.

Installing NApps
^^^^^^^^^^^^^^^^
================

To load an application *Kyco* will lookup inside the directory indicated in
``napps`` parameter inside the configuration file. By default, this parameter
Expand All @@ -31,7 +31,7 @@ all Napp application directory should have the prefix ``of_`` before the Napp's
name.

Removing NApps
^^^^^^^^^^^^^^
==============

To remove a Napp from *Kytos* all the administrator has to do is to delete the
Napp from ``/var/lib/kytos/napps/kyco/``. Before removing the directory it is
Expand All @@ -46,7 +46,7 @@ After removing the directory the administrator can start the *Kyco* again and
the Napp will not be loaded.

Enable/Disable NApps
^^^^^^^^^^^^^^^^^^^^
====================

*Kyco* allows the administrator to prevent that a Napp to be loaded during the
startup process. As mentioned earlier, *Kyco* will look for Napps inside the
Expand Down
2 changes: 2 additions & 0 deletions docs/administrator/notifications.rst
@@ -1,3 +1,5 @@
:orphan:

Enabling notifications
----------------------

Expand Down
10 changes: 5 additions & 5 deletions docs/administrator/quickstart.rst
@@ -1,8 +1,8 @@
Quickstart
----------
**********

Docker
++++++
======

You do not need to install Kytos to try it.

Expand All @@ -22,7 +22,7 @@ and you will have your instance of a basic openflow controller built with
Kytos SDN Platform.

Install
+++++++
=======

In order to install and run kytos you need:

Expand All @@ -37,7 +37,7 @@ In order to install and run kytos you need:
$ python3.6 -m pip install kytos
Run
+++
===

once kytos is installed, you can:

Expand Down Expand Up @@ -66,7 +66,7 @@ NB:
- kytos/of_topology
- kytos/of_flow_manager
- kytos/of_ipv6drop
- kytos/web_topology_layout
- kytos/web_topology_layout

to do it, run:

Expand Down
2 changes: 2 additions & 0 deletions docs/administrator/requirements.rst
@@ -1,3 +1,5 @@
:orphan:

Requirements
------------

Expand Down

0 comments on commit 04bba53

Please sign in to comment.