| |
|
 |
|
 |
|
|
|
| |
|
|
xen-devel
Re: [Xen-devel] [PATCH] xenctld - a control channel multiplexing daemon
Anthony Liguori wrote:
Jacob Gorm Hansen wrote:
My current implementation is less than 100 lines of network-facing
code (using ICMP payloads, but the same could be achieved with UDP),
though that increases to about 300 if you count in the SHA-1
implementation that I am using for verifying customer credentials. So
300 lines is for a complete solution including crypto and
accounting/payment.
That's certainly interesting. Are you using ICMP simply for high-level
management or are you passing event channel messages via ICMP? Are you
just punting issues of reliability?
I agree with you, TCP is not the only network solution. However, it
seems logically that a large number of people will want a TCP solution :-)
I am using TCP, but I am doing both bootstrap+shutdown of new domains,
migration, and accounting mostly within domUs. I send an ICMP payload
with an initial ticket/capability describing the max memory, disk
extents, external IP etc., and the ICMP server in dom0 decodes/verifies
that, an fires up a domU with a minimal TPC/IP stack and server inside.
The domain builder is then uploaded on that connection, takes over, and
handles the bootstrap from there. Same is true for migration.
Jacob
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
|
|
| |
|
Home