Jump to: navigation, search


< XenServer
Revision as of 11:44, 29 January 2014 by Mate Lakat (talk | contribs)

Backround for Nodepool

The standard Nodepool population looks like:

  • Launch server
  • Bootstrap server
  • Snapshot server
  • Populate pool from snapshot
  • Node is ready when it's accessible through SSH

Whereas, we need some additional entry points:

  • Launch server
  • Install server - This phase will install XenServer on the server
  • Poll install status - As installing XenServer includes rebooting the server, the best way to figure out when the installation is finished, is to try to connect to the server through ssh, and check if a specific status file exists.
  • Bootstrap instance
  • Pre-snapshot script and timeout - Before taking a snapshot, we need to halt the server. Therefore we execute a halt in dom0, and ask nodepool to wait for a specified timeout. The timeout should be enough for the server to halt.
  • Snapshot server
  • Populate pool from snapshot
  • Poll status file on node launch - As starting the image invlolves an automatic reboot, we again need a proper way to make sure, that XenServer is up and running. This could be achieved with the same polling mechanism that we used for Poll install status.
  • Node is ready when it's accessible through SSH

Changes to Requirements

Changes to DevStack

Changes to Config

Changes to Nodepool

  • - WAITING - Install phase - execute a script, that converts the node to a XenServer, and use polling to find out when it's finished: https://review.openstack.org/61463
  • - MISSING - Pre-snapshot script and timeout - The script will halt the node, and the wait will make sure, that the machine has enough time to halt. It's safe to snapshot a halted server.
  • - WAITING - Support status file polling on node launch: https://review.openstack.org/65261

Changes to DevStack-Gate