- reads in configs,
- initializes networking paths,
- checks licensing,
- maintains a Database with all this info (the XAPI database),
- manages Storage Repositories,
- manages VMs,
- tracks VM states,
- manages networking,
- High Availability
- other XenServer hosts in the pool and more……
Each XenServer request or action is done via Xapi – and only by asking the Master XenServer XAPI to do so.
A copy of the XAPI database (or you could consider this to be the state of XAPI) is synchronized among all the hosts in the pool – so they all have a copy of the current XAPI database – giving them the knowledge of what is going on – and in the case of the master going down – a new master can be appointed from the pool using the XAPI state information or shared database.
When you collect a status report from XenServer – the XAPI Database is stored in the status report. It is a relational database – and shows us the state of the environment at that point in time (when the status report was captured).
Reference
2. XAPI Developer Guide, http://wiki.xensource.com/xenwiki/XAPI_Developer_Guide
沒有留言:
張貼留言