Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • VILLASnode VILLASnode
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 25
    • Issues 25
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 6
    • Merge requests 6
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • ACS
  • Public
  • VILLASframework
  • VILLASnodeVILLASnode
  • Issues
  • #24

Closed
Open
Created Nov 06, 2015 by Ghost User@ghost

Reconsider the name of s2ss and organization of the overall platform

Created by: mstevic

s2ss is more than simulator-to-simulator server. maybe s2ss name can be kept as a component of a more general term: lab-to-lab server? For example, s2ss is "hard real-time" interface between the lab but we have different options (soft real-time, simply best-effort...) But it is even more than that, we have interface to OCB, websockets for example. Maybe, InetDistSim gateway? Refer to architecture in VILLAS and PES GM paper. Keep in mind software distribution and usage in a large-scale and diverse InetDistSim platform.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking