[Bug 1026621] Re: nova-network gets release_fixed_ip events from someplace, but the database still keeps them associated with instances

[Shawn Duex]

Hey Jay,

Funny you posted this. I was about to post the same. after a bunch of
testing and comparing how CLoudStack deals with the Hardware Clock for
Windows with how Openstack is configured by default we also noticed that
the Nova VM template uses a hardware clock with a UTC offset. This is a
standard for Linux but not for Windows. The reg key you listed does
allow Windows to deal with a UTC offset hardware clock. In my looking
into this I do see that this change is not without issue, as some things
will not work correctly. But for the most part on server OS I think it
should be fine. CloudStack manages this issue by having a OS_Type for
each image and for images that are windows it  local time rather that
the UTC offset for the hardware clock. This then does not require an
image side change for Windows images. Currently we do not see an easy
way to implement the same kind of solution as the best we can do is set
advanced metadata properties on an image in glance, but then having Nova
key off this and use a Windows specific template would require some
additional work. I think another aspect of this is that the DHCP leases
are set for 120 seconds on OpenStack by default. I think this
exacerbates the issue because the lease time is shorter that the time
offset. Does anyone know why the DHCP lease times are so short for
OpenStack? CloudStack configures the leases to not expire which would
also make this issue not happen.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1026621

Title:
  nova-network gets release_fixed_ip events from someplace, but the
  database still keeps them associated with instances

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