Jump to: navigation, search


< XenServer
Revision as of 10:23, 7 February 2014 by Mate Lakat (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Last Status Update

As this page contains statuses, which will vary in time, so the latest update should follow this line:

--mate-lakat (talk) 10:23, 7 February 2014 (UTC)

Background 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 and poll status file - This phase will install XenServer on the server. 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
  • 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

Changes to DevStack-Gate


--mate-lakat (talk) 10:23, 7 February 2014 (UTC)

  • pull changes up to domU has been split into two work items

--mate-lakat (talk) 18:13, 6 February 2014 (UTC)

  • Status ox XenAPI package caching has changed to Merged

--mate-lakat (talk) 11:46, 30 January 2014 (UTC)

  • Removed leftovers from pre-snapshot and timeout script, updated installer's status.

--mate-lakat (talk) 08:18, 30 January 2014 (UTC)