X-Git-Url: https://osm.etsi.org/gitweb/?p=osm%2Fvim-emu.git;a=blobdiff_plain;f=README.md;h=ba22ec342ed5d60bf65770aa154adce8b0fcc141;hp=6309f7c181664cdd5a2c00f20c12c9e999c24d97;hb=ea1c56125cb8a37b7b1614ab0aa46f9dc8f576dc;hpb=726a45874fda781f19d1bc1c21b18ba8526e2c19 diff --git a/README.md b/README.md old mode 100644 new mode 100755 index 6309f7c..ba22ec3 --- a/README.md +++ b/README.md @@ -1,87 +1,145 @@ -# Distributed Cloud Emulator - -Contributors: - -* Manuel Peuster - - -### Requirements -* needs the latest Dockernet to be installed in the system - * the wrapper uses standard Python imports to use the Dockernet modules -* Uses ZeroMQ based RPC to open a cloud-like interface that can be used by a demo CLI client - * pip install import zerorpc - * This will be replaced / extended by a REST API later - -### Project structure -* **emuvim/** all emulator code - * **api/** Data center API endpoint implementations (zerorpc, OpenStack REST, ...) - * **cli/** CLI client to interact with a running emulator - * **dcemulator/** Dockernet wrapper that introduces the notion of data centers and API endpoints - * **test/** Unit tests - * **example_topology.py** An example topology script to show how topologies can be specified - -### Installation -Automatic installation is provide through an Ansible playbook. -* Requires: Ubuntu 14.04 LTS -* `sudo apt-get install ansible git` -* `sudo vim /etc/ansible/hosts` -* Add: `localhost ansible_connection=local` - -#### 1. Dockernet -* `git clone https://github.com/mpeuster/dockernet.git` -* `cd dockernet/ansible` -* `sudo ansible-playbook install.yml` -* Wait (and have a coffee) ... - -#### 2. Emulator -* Fork the repository. + + +# vim-emu: A NFV multi-PoP emulation platform + +This emulation platform was created to support network service developers to locally prototype and test their network services in realistic end-to-end multi-PoP scenarios. It allows the execution of real network functions, packaged as Docker containers, in emulated network topologies running locally on the developer's machine. The emulation platform also offers OpenStack-like APIs for each emulated PoP so that it can integrate with MANO solutions, like OSM. The core of the emulation platform is based on [Containernet](https://containernet.github.io). + +The emulation platform `vim-emu` is developed as part of OSM's DevOps MDG. + +### Acknowledgments + +This software was originally developed by the [SONATA project](http://www.sonata-nfv.eu), funded by the European Commission under grant number 671517 through the Horizon 2020 and 5G-PPP programs. + +### Cite this work + +If you use the emulation platform for your research and/or other publications, please cite the following paper to reference our work: + +* M. Peuster, H. Karl, and S. v. Rossem: [MeDICINE: Rapid Prototyping of Production-Ready Network Services in Multi-PoP Environments](http://ieeexplore.ieee.org/document/7919490/). IEEE Conference on Network Function Virtualization and Software Defined Networks (NFV-SDN), Palo Alto, CA, USA, pp. 148-153. doi: 10.1109/NFV-SDN.2016.7919490. (2016) + +## Installation + +There are three ways to install and use the emulation platform. The bare-metal installation requires a freshly installed Ubuntu 16.04 LTS and is done by an ansible playbook. The second option is to use a nested Docker environment to run the emulator inside a Docker container. The third option is to use Vagrant to create a VirtualBox-based VM on your machine that contains the pre-installed and configured emulator. + +### Option 1: Bare-metal installation + +* Requires: Ubuntu 16.04 LTS +* `sudo apt-get install ansible git aptitude` + +#### 1. Containernet + * `cd` -* `git clone https://github.com//son-emu.git` -* `cd emulator-strawman/ansible` -* `sudo ansible-playbook install.yml` +* `git clone https://github.com/containernet/containernet.git` +* `cd ~/containernet/ansible` +* `sudo ansible-playbook -i "localhost," -c local install.yml` +#### 2. vim-emu -### Run -* First terminal: - * `cd emulator-strawman/emuvim` - * `sudo python example_topology.py` -* Second terminal: - * `cd emulator-strawman/emuvim/cli` - * `./son-emu-cli compute start -d dc1 -n vnf1` - * `./son-emu-cli compute start -d dc1 -n vnf2` - * `./son-emu-cli compute list` +* `cd` +* `git clone https://osm.etsi.org/gerrit/osm/vim-emu.git` +* `cd ~/vim-emu/ansible` +* `sudo ansible-playbook -i "localhost," -c local install.yml` + +### Option 2: Nested Docker Deployment +This option requires a Docker installation on the host machine on which the emulator should be deployed. + +* `git clone https://osm.etsi.org/gerrit/osm/vim-emu.git` +* `cd ~/vim-emu` +* Build the container: `docker build -t vim-emu-img .` +* Run the (interactive) container: `docker run --name vim-emu -it --rm --privileged --pid='host' -v /var/run/docker.sock:/var/run/docker.sock vim-emu-img /bin/bash` + +### Option 3: Vagrant Installation +* Request VirtualBox and Vagrant to be installed on the system. +* `git clone https://osm.etsi.org/gerrit/osm/vim-emu.git` +* `cd ~/vim-emu` +* `vagrant up` +* `vagrant ssh` to enter the new VM in which the emulator is installed. + +## Usage + +### Example + +This simple example shows how to start the emulator with a simple topology (terminal 1) and how to start (terminal 2) some empty VNF containers in the emulated datacenters (PoPs) by using the vim-emu CLI. + +* First terminal (start the emulation platform): + * `sudo python examples/default_single_dc_topology.py` +* Second terminal (use `docker exec vim-emu ` for nested Docker deployment): + * `vim-emu compute start -d dc1 -n vnf1` + * `vim-emu compute start -d dc1 -n vnf2` + * `vim-emu compute list` * First terminal: - * `dockernet> vnf1 ping -c 2 vnf2` - - -### TODO -* DCemulator - * Advanced network model - * improve network management, multiple interfaces per container - * API to create multiple networks (per DC?) - - -* Add resource constraints to datacenters -* Check if we can use the Mininet GUI to visualize our DCs? -* (Unit tests for zerorpc API endpoint) - - -### Features / Done -* Define a topology (Python script) - * Add data centers - * Add switches and links between the, -* Define API endpoints in topology - * call startAPI from topology definition and start it in a own thread - * make it possible to start different API endpoints for different DCs -* DCemulator - * correctly start and connect new compute resources at runtime - * remove and disconnect compute resources at runtime - * do IP management for new containers - * list active compute resources -* Cloud-like reference API with CLI for demonstrations - * Write CLI client - * Start compute (name, DC, image, network) - * Stop compute -* Create an Ansible-based automatic installation routine -* Unit tests + * `containernet> vnf1 ifconfig` + * `containernet> vnf1 ping -c 2 vnf2` + +### Further documentation and useful links + +* [Full CLI command documentation](https://github.com/sonata-nfv/son-emu/wiki/CLI-Command-Overview) +* [Requirements for Docker containers executed by the emulator](https://github.com/sonata-nfv/son-emu/wiki/Container-Requirements) +* [REST API](https://github.com/sonata-nfv/son-emu/wiki/APIs) +* [Mininet](http://mininet.org) +* [Containernet](https://containernet.github.io) +* [Maxinet](https://maxinet.github.io) + +## Development + +### How to contribute? + +Please check [this OSM wiki page](https://osm.etsi.org/wikipub/index.php/Workflow_with_OSM_tools) to learn how to contribute to a OSM module. + +### Testing + +To run the unit tests do: + +* `cd ~/vim-emu` +* `sudo py.test -v src/emuvim/test/unittests` +(To force Python2: `python2 -m pytest -v src/emuvim/test/unittests`) + +## Seed code contributors: + +### Lead: + +* Manuel Peuster (https://github.com/mpeuster) +* Steven Van Rossem (https://github.com/stevenvanrossem) + +### Contributors + +* Hadi Razzaghi Kouchaksaraei (https://github.com/hadik3r) +* Wouter Tavernier (https://github.com/wtaverni) +* Geoffroy Chollon (https://github.com/cgeoffroy) +* Eduard Maas (https://github.com/edmaas) +* Malte Splietker (https://github.com/splietker) +* Johannes Kampmeyer (https://github.com/xschlef) + +## License + +The emulation platform is published under Apache 2.0 license. Please see the LICENSE file for more details. + +## Contact + +Manuel Peuster (Paderborn University)