How about extending all features into io-socket in KVM/XEN and VM
Annotation details with VmWare?
Similar to what we do with system VMs when they come up - except there
are no router vms to manage and depend on.
On 3/26/15 11:37 PM, Rohit Yadav wrote:
Hi everyone,
I want to re-start the dis
Hi Rohit,
At the moment I’m looking into doing something with a much lighter and quite
flexible alternative for the VR. I was actually thinking of using Tiny Core OS
as a base, it has a great packaging system with loop mounts and is very simple
and tiny compared to the VR we have now (tens of M
Hi everyone,
I want to re-start the discussion on improving VR services and making a
framework to build/improve old/new features such as reset password, dhcp, dns,
vpn etc. that are both running on VR or on user VMs (reset password for
example). For this, I’ve updated the wiki for high level go
Do you know of any plans/possibilities to completely get rid of the VR and move
functionality - especially routing traffic - in host agents?
On another note, something more pluggable would be nice. One thing I'd really
love to see is OpenVPN support (because anything else is just a world of pain
Rohit,
Completely agree with the scalability and maintenance issues with systems Vms.
Using an agent inside VR will probably work well for KVM, since the KVM agent
(Resource layer) is remote. Communication using link-local network also won't
be a problem is such case.
For other hypervisors, it w
