Manage a remote virtualbricks session via TCP socket
It will be possible to set up a listening TCP
port on each VB instance. A client connecting and authenticating to that
port will take over the management, and the window actions for the server
Virtualbricks will be set to non-sensitive, displaying a message to the
user to inform her on the fact that the network is being remotely managed.
On the client side, there will be almost no difference between local and
remote bricks being managed.
Connection should have:
* Authentication
* Encryption
Blueprint information
- Status:
- Started
- Approver:
- Daniele Lacamera
- Priority:
- High
- Drafter:
- Daniele Lacamera
- Direction:
- Approved
- Assignee:
- Francesco Apollonio
- Definition:
- Approved
- Series goal:
- Accepted for 1.x
- Implementation:
- Needs Code Review
- Milestone target:
- 1.1
- Started by
- Daniele Lacamera
- Completed by
Related branches
Related bugs
Sprints
Whiteboard
STEP 0: start without the gui. [Done in 0.3]
STEP 1: provide connection facilities (TCP sockets): done
STEP 2: copy bricks at runtime through TCP CLI : done
STEP 3: client GUI: done
STEP 4: connectivity for remote bricks: WIP
STEP 5: error handling, disconnections
STEP 6: verify/implement event bindings to remote bricks
after the code refactory of the latest versions this blueprint requires a complete code review to check if all the previously implemented features are still valid or not.
Work Items
Dependency tree
* Blueprints in grey have been implemented.