yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

** Changed in: nova
    Milestone: None => havana-3

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1192724

Title:
  libvirt Spice console requests should be able to fall back to novnc

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  Using master or Grizzly, there is currently no method for a Spice
  console request to automatically fallback to novnc.  This is important
  because otherwise there is no migration path if deployments decide to
  switch from novnc to Spice as their default.

  The reason is that the enabling of Spice cannot occur until the
  instance in question is destroyed, XML redefined enabling Spice, then
  restarted.  Thus, upon deployment, existing instances will only have
  VNC consoles enabled, where new instances will have VNC + Spice.  If
  the deployment preference is Spice, users and/or Horizon should simply
  be able to ask Nova for a Spice console and get back a novnc URL if
  Spice isn't ultimately available.

  We can make this fallback from VNC to Spice a configuration option,
  since the behavior may not be desired in some cases.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1192724/+subscriptions