User Tools

Site Tools


admin:introduction

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
admin:introduction [2015/08/31 12:37]
ivilata Mention user and root command prefixes.
admin:introduction [2015/09/03 09:10] (current)
ivilata Less style options for note.
Line 2: Line 2:
 <WRAP box 25% right> <WRAP box 25% right>
 //​**__[[start]]__**//​ //​**__[[start]]__**//​
-{{indexmenu>​.|msort tsort skipfile+/​(page_to_skip)/​}}+{{indexmenu>​.|msort tsort skipfile+/(hotfix_controller_certificates|page_to_skip)/​}}
 </​WRAP>​ </​WRAP>​
  
 ===== Introduction ===== ===== Introduction =====
  
-This guide describes the tasks needed to deploy and operate a testbed based on the software released by the [[https://​confine-project.eu/​|CONFINE Project]], a European FP7 project intended to develop the tools that allow researchers to deploy, run, monitor and experiment with services, protocols and applications on real-world community networks. ​ These instructions also apply to [[https://​community-lab.net/​|Community-Lab]],​ CONFINE'​s reference testbed based on several community networks.+This guide describes the tasks needed to **deploy and operate a testbed** based on the software released by the [[https://​confine-project.eu/​|CONFINE Project]], a European FP7 project intended to develop the tools that allow researchers to deploy, run, monitor and experiment with services, protocols and applications on real-world community networks. ​ These instructions also apply to [[https://​community-lab.net/​|Community-Lab]],​ CONFINE'​s reference testbed based on several community networks.
  
-The current implementation of CONFINE testbeds relies on a central ​**controller** which provides a web interface for human interaction with several toolsand a set of APIs for programs. ​ It also provides other important services to testbed nodes. ​ For more technical information on the Controller software, see [[soft:​server]].+The current implementation of CONFINE testbeds relies on a **central ​controller** which provides a web interface for human interaction with several tools and a set of APIs for programs. ​ It also provides other important services to testbed nodes. ​ For more technical information on the Controller software, see [[soft:​server]].
  
 In terms of the CONFINE architecture (see [[arch:]]), the Controller software implements a //testbed server// which provides an entry point to the //Registry REST API// (see [[arch:​rest-api]]) and which acts as a //​management network gateway server// (see [[arch:​management-network]]). In terms of the CONFINE architecture (see [[arch:]]), the Controller software implements a //testbed server// which provides an entry point to the //Registry REST API// (see [[arch:​rest-api]]) and which acts as a //​management network gateway server// (see [[arch:​management-network]]).
  
-Thus, this guide is centered on the configuration and maintenance of a server running the Controller software, and other servers run by testbed operators like gateway servers. ​ For the administration of testbed nodes, please refer to [[usage:]].+Thus, this guide is centered on the **configuration and maintenance** of a server running the **Controller software**, and other servers run by testbed operators like gateway servers. ​ For the administration of testbed nodes, please refer to [[usage:]].
  
-Please note that, throughout the guide and unless explicitly stated otherwise, whenever the reader is instructed to log into the Controller web interface, it is assumed that the used account possesses **superuser privileges**.  Command line operations are prefixed with ''​$''​ or ''#''​ depending on whether the command must be run as a plain system user (which holds a Controller deployment) or ''​root'',​ respectively.+<WRAP round info> 
 +Please note that, throughout the guide and unless explicitly stated otherwise, whenever the reader is instructed to log into the Controller web interface, it is assumed that the used account possesses **superuser privileges**.
  
 +Also note that command line operations are prefixed with ''​$''​ or ''#''​ depending on whether the command must be run as a plain system user (which holds a Controller deployment) or as ''​root'',​ respectively.
 +</​WRAP>​
admin/introduction.1441017443.txt.gz · Last modified: 2015/08/31 12:37 by ivilata