yahoo-eng-team team mailing list archive

[OpenStack Hudson <1161190@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/25721
Committed: http://github.com/openstack/openstack-manuals/commit/392da359d77c227cf91132fae31114a1bf521dd4
Submitter: Jenkins
Branch:    master

commit 392da359d77c227cf91132fae31114a1bf521dd4
Author: Tom Fifield <fifieldt@xxxxxxxxxxxxxx>
Date:   Fri Mar 29 23:49:45 2013 +0800

    Add quota_fixed_ips to nova conf ref
    
    Grizzly brings a new feature quota_fixed_ips, which this
    patch documents - including its default value of unlimited
    
    fixes bug 1161190
    
    Change-Id: I013bccaeff5372b3360e6b16b7b9b20b8ff52aad


** Changed in: openstack-manuals
       Status: In Progress => Fix Released

-- 
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/1161190

Title:
  Fixed IPs quota can break upgrades

Status in OpenStack Compute (Nova):
  Fix Released
Status in OpenStack Compute (nova) essex series:
  In Progress
Status in OpenStack Compute (nova) folsom series:
  Fix Committed
Status in OpenStack Manuals:
  Fix Released

Bug description:
  When upgrading our folsom cloud to latest stable/folsom it added
  support for fixed ip quota.

  The default is 10 which means all of a sudden my instances weren't
  getting IP's.

  I think the default should be -1 so it doesn't break existing clouds.

  Also need something in the release notes/ upgrade notes

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