This learning track contains a sequence of tutorials that will introduce
SlapOS and teach the setup and use of a Network Management System (NMS)
based on SlapOS for ADMINS. After finishing this learning track,
you should have a ready-to-use network and be familiar with providing and
extending existing software to users as well as monitoring network status.
The course is split into lectures introducing a certain component and
showing how they are setup and fit into the overall architecture. All
documents that are part of this learning track are also included in PDF
and hmtl format.
If applicable, each lecture also provides links to additional generic
SlapOS documentation such as HowTos explaining certain aspects in more
detail or outlining how certain prerequisities of a component can be met.
Note, that the lectures are meant to be read in the order listed.
Reading material and actual tutorials to setup the will be pointed out.
This section is a global introduction to NMS and only contains reading materials.
It will introduce the NMS and underlying SlapOS sytems and provide
answers to key questions. The following documents should be read:
This lecture introduces SlapOS and its architecture and from this derives
the requirements for an NMS Network Management System. This lecture also
contains reading materials. The following documents are required to be read:
Once you understand the differences between Master and nodes, can distinguish
COMP-ROOT, 0 and 123 in a network, know where software releases are added and
what supplying a software on a node and instantiating it on a partition means,
you can start with the next lecture of setting up the NMS.
This lecture will covers installing and configuring the SlapOS Master (COMP-ROOT).
It is the main component of a NMS network but relatively straightforward to
setup. Please do the following tutorial to get a SlapOS Master up and running:
This lecture will cover setting up the COMP-0 machine required to provide
core services to the COMP-ROOT and other nodes in the network. They include
IPv6, a Frontend to streamline browser-based access and the SimcardDB
Setting up COMP-0 is the complicated part as it requires some improvisation
for simulating services to properly connect nodes before they are provided
by COMP-0. Please do the following tutorials to setup COMP-0:
In case of a missing wildcard SSL certificate you can follow
how to request a wildcard SSL certificate
(presentation). After you have finished this tutorial, you will know
how to add software to the network and how to deploy instances. The procedure
is the same for any software provided over SlapOS.
This lecture will cover installing and deploying a eNodeB/EPC server. It will
include setting up a new generic node (COMP-123), using the SlapOS Master to
install EPC/eNB on this node and providing instances using several
configurations available. Technically this lecture does the same as in the
previous steps, only in a different order and with a different software.
Please do the following to learn how to setup regular network nodes:
This lecture includes material to show demonstrating how to manage the
NMS system once it has been setup, including classifying network nodes,
monitoring network performance and handling tickets created from anomalies or
failures of deployed instances or computers. The following tutorials should
be done to complete this lecture:
The only thing necessary to be configured on a running NMS network are
instantiation parameters. This lecture will teach working with the software
profile underlying the software installed in the catalogue. It will introduce
Buildout in more detail and show how a software release can be modified using
a Webrunner. This lecture is more technical and covers the basics of creating
a software release like the one used to create the NMS.
Read the following documents to familiarize yourself with developing in SlapOS:
Then add the Webrunner to your network, deploy an instance and inside install the helloworld software release.
This will then be used as example showing how to modify a software release to add parameters, promises and components.