There was a discussion in the core meeting about that, please see the comments on the relevant patch for that.
Thanks, Thomas On Wed, May 15, 2013 at 4:06 PM, Guido Trotter <[email protected]> wrote: > > > > On Wed, May 15, 2013 at 3:04 PM, Thomas Thrainer <[email protected]>wrote: > >> Ganeti did not record the status of instance disks (active/inactive) >> explicitly until now. Instead, the status was inferred from the >> instance status (running/ADMIN_down/etc.). >> This led to problems when the disks of an instance were active >> (through a gnt-instance activate-disks) and then one of the nodes >> rebooted. In this case, disks were not re-activated automatically, >> which is especially bad in the case of DRBD, where the non-rebooting >> node ended up in WFConnection state. >> >> This patch series introduces a new instance attribute called disks_active. >> This flag records if the disks of an instance should be active or not. >> cfgupgrade is updated to being able to upgrade to the new format (2.9) >> too. >> > > Do we need cfgupgrade here? Should we just use the config self-upgrade > mechanism? > (for the downgrade we do, definitely) > > Thanks, > > Guido > > -- Thomas Thrainer | Software Engineer | [email protected] | Google Germany GmbH Dienerstr. 12 80331 München Registergericht und -nummer: Hamburg, HRB 86891 Sitz der Gesellschaft: Hamburg Geschäftsführer: Graham Law, Katherine Stephens
