Control another virtualbricks session on a remote host
Bug #691977 reported by
Daniele Lacamera
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Virtualbricks |
Fix Released
|
Medium
|
Daniele Lacamera |
Bug Description
Virtualbricks should accept TCP connections from another virtualbricks client that want to control all the bricks on it, and the two networks can be joined using a tunnel. This way the cloud can be distributed, extensible and will have centralized control.
Changed in virtualbrick: | |
status: | New → Opinion |
importance: | Undecided → Wishlist |
assignee: | nobody → Danielinux (o-root-danielinux-net) |
Changed in virtualbrick: | |
status: | Opinion → In Progress |
importance: | Wishlist → Low |
Changed in virtualbrick: | |
milestone: | none → 0.3 |
importance: | Low → Medium |
Changed in virtualbrick: | |
assignee: | Danielinux (o-root-danielinux-net) → nobody |
Changed in virtualbrick: | |
milestone: | 0.3 → 0.4 |
Changed in virtualbrick: | |
milestone: | 0.4 → 0.5 |
Changed in virtualbrick: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I think that we have to use libssl to create the tunnel between two remote virtualbricks.