Xenopsd: Difference between revisions
From Xen
Jump to navigationJump to search
Dave.scott (talk | contribs) (Created page with "= The xenops daemon = This is an attempt to improve the architecture of the XCP toolstack by splitting *domain management* into a separate service, known as the *xenops daemon*.…") |
Dave.scott (talk | contribs) No edit summary |
||
Line 10: | Line 10: | ||
== Design overview == |
== Design overview == |
||
[[File:xenopsd-internals.svg]] |
|||
== Code status == |
== Code status == |
||
Revision as of 20:47, 30 December 2011
The xenops daemon
This is an attempt to improve the architecture of the XCP toolstack by splitting *domain management* into a separate service, known as the *xenops daemon*. This should have the following advantages:
- it helps untangle the domain management code from the rest of xapi (which will focus on multi-host resource pool management)
- it forces us to be explicit about the interface xapi needs, making the future libxl port more predictable and likely to succeed
- it forces us to be explicit about the interface xenopsd needs, preventing (for example) the accidental insertion of a expensive RPC to a remote host through an internal xapi interface in a hot codepath.