Remote OMNeT++ v2.0
Introduction
What is Remote OMNeT++?
• Remote environment for OMNeT++
• Remote simulation execution
• Remote data storage
Remote OMNeT++ v2.0
Introduction
Motivation
• Multiple users, highly scalable
• Little or no client installation required
• Use of remote, high performance simulation execution servers
• Use of remote data storage
• Manageability
Remote OMNeT++ v2.0
Architecture
Components of the system
• Processing Hosts for simulation execution
• High processing power
• Data Warehouses
• Large storage capacity
• Clients
• Runs on inexpensive workstations
Remote OMNeT++ v2.0
Architecture
Technologies
• Java for platform-independent operation
• RMI communications
• Socket communications
• DBMS for the Data Warehouses
Remote OMNeT++ v2.0
Data Warehouses Processing
Hosts
Architecture
Basic communications between the components
Client Processing
Host
Data Warehouse Processing
Hosts
Data Warehouses
Remote OMNeT++ v2.0
Architecture
Client
• Java application with graphical interface (Remote OMNeT++ Client)
• Possible local storage of simulation models and results
• Runs on any platform with suitable JVM installed
• UNIX
• Linux
• Any 32-bit Microsoft Windows platform
Remote OMNeT++ v2.0
Architecture
Processing Host
• Java application (Remote OMNeT++ Manager)
• OMNeT++ simulation engine
• Usually runs on UNIX or Linux
• Can be ported to most other platforms
Remote OMNeT++ v2.0
Architecture
Data Warehouse
• Java application (Remote OMNeT++ Dataware)
• Data storage (local files or DBMS)
• Runs on any platform with suitable JVM installed
• UNIX
• Linux
• Any 32-bit Microsoft Windows platform
Remote OMNeT++ v2.0
Architecture
Typical usage scenarios - Local computer
Remote OMNeT++
Manager
Remote OMNeT++
Dataware
Remote OMNeT++
Client Local computer
OMNeT++
Engine
Remote OMNeT++ v2.0
Architecture
Typical usage scenarios - Remote server
Remote OMNeT++
Manager
Remote OMNeT++
Dataware
Remote OMNeT++
Client Remote server
OMNeT++
Engine
Local computer
Internet or LAN (TCP/IP)
Remote OMNeT++ v2.0
Architecture
Typical usage scenarios - Separate remote servers
Remote OMNeT++
Manager
Remote OMNeT++
Dataware
Remote OMNeT++
Client Processing Host
OMNeT++
Engine
Local computer
Internet or LAN (TCP/IP)
Data Warehouse
Remote OMNeT++ v2.0
Architecture
Communication technologies
Remote OMNeT++
Manager
Remote OMNeT++
Dataware
Remote OMNeT++
Client OMNeT++
Engine
Internet or LAN (TCP/IP)
Java RMI Java RMI
TCP/IP Socket
Remote OMNeT++ v2.0 Client
The graphical user interface
Remote OMNeT++ v2.0
Client
Usage
• Login to the remote servers (Processing Host and Data Warehouse)
• Transfer the local files you wish to store to the Data Warehouse
• Transfer the necessary files to the Processing Host
• Compile the simulation on the Processing Host
• Execute the simulation
• The results are transferred to the Data Warehouse
• View the results or download them to the local computer
Remote OMNeT++ v2.0
Client
Usage
• You can disconnect after starting the simulation
• You can always connect to the servers later to monitor the progress
• You can watch monitored parameters as the simulation is running
• Your files are kept on the Data Warehouse where you can access them
• You are identified by a username and a password to protect data
Remote OMNeT++ v2.0
Possibilities
Kinds of simulation supported
• Ability to execute multiple simulations concurrently
• Run a simulation with different parameters concurrently
• Run a simulation in parallel using PVM and cluster technology
Remote OMNeT++ v2.0
Possibilities
Data analysis
• Results and models are stored in a Data Warehouse
• Data can be analyzed on the local computer
• Client application can be expanded to add new analysis tools
Remote OMNeT++ v2.0
Future
New possibilities
• The user should be able to develop new models in a graphical editor
• Models can be constructed from pre-created primitives
• Support for developing parallel models
Remote OMNeT++ v2.0 Related resources
• WebTeam homepage (whale.hit.bme.hu/~webteam)
• OMNeT++ homepage (www.hit.bme.hu/phd/vargaa/omnetpp.htm)
