yahoo-eng-team team mailing list archive

[Alex Syafeyev <astafeye@xxxxxxxxxx>]

Public bug reported:

Kilo

nova absolute-limits 
+--------------------+------+-------+
| Name               | Used | Max   |
+--------------------+------+-------+
| Cores              | 2    | 20    |
| FloatingIps        | 0    | 10    |
| ImageMeta          | -    | 128   |
| Instances          | 1    | 10    |
| Keypairs           | -    | 100   |
| Personality        | -    | 5     |
| Personality Size   | -    | 10240 |
| RAM                | 4096 | 51200 |
| SecurityGroupRules | -    | 20    |
| SecurityGroups     | 1    | 10    |
| Server Meta        | -    | 128   |
| ServerGroupMembers | -    | 10    |
| ServerGroups       | 0    | 10    |
+--------------------+------+-------+
 we see floating IPs value as 0 even though we have floating IP configured, attached to v VM, and working properly. 

create a tenant with VM, with floating IP. 
Check for nova absolute-limits 

openstack-nova-compute-2015.1.0-3.el7ost.noarch
openstack-nova-console-2015.1.0-3.el7ost.noarch
openstack-nova-common-2015.1.0-3.el7ost.noarch
openstack-nova-scheduler-2015.1.0-3.el7ost.noarch
python-nova-2015.1.0-3.el7ost.noarch
openstack-nova-cert-2015.1.0-3.el7ost.noarch
openstack-nova-novncproxy-2015.1.0-3.el7ost.noarch
openstack-nova-conductor-2015.1.0-3.el7ost.noarch
python-novaclient-2.23.0-1.el7ost.noarch
openstack-nova-api-2015.1.0-3.el7ost.noarch

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  nova absolute-limits Floating ip

Status in OpenStack Compute (Nova):
  New

Bug description:
  Kilo

  nova absolute-limits 
  +--------------------+------+-------+
  | Name               | Used | Max   |
  +--------------------+------+-------+
  | Cores              | 2    | 20    |
  | FloatingIps        | 0    | 10    |
  | ImageMeta          | -    | 128   |
  | Instances          | 1    | 10    |
  | Keypairs           | -    | 100   |
  | Personality        | -    | 5     |
  | Personality Size   | -    | 10240 |
  | RAM                | 4096 | 51200 |
  | SecurityGroupRules | -    | 20    |
  | SecurityGroups     | 1    | 10    |
  | Server Meta        | -    | 128   |
  | ServerGroupMembers | -    | 10    |
  | ServerGroups       | 0    | 10    |
  +--------------------+------+-------+
   we see floating IPs value as 0 even though we have floating IP configured, attached to v VM, and working properly. 

  create a tenant with VM, with floating IP. 
  Check for nova absolute-limits 

  openstack-nova-compute-2015.1.0-3.el7ost.noarch
  openstack-nova-console-2015.1.0-3.el7ost.noarch
  openstack-nova-common-2015.1.0-3.el7ost.noarch
  openstack-nova-scheduler-2015.1.0-3.el7ost.noarch
  python-nova-2015.1.0-3.el7ost.noarch
  openstack-nova-cert-2015.1.0-3.el7ost.noarch
  openstack-nova-novncproxy-2015.1.0-3.el7ost.noarch
  openstack-nova-conductor-2015.1.0-3.el7ost.noarch
  python-novaclient-2.23.0-1.el7ost.noarch
  openstack-nova-api-2015.1.0-3.el7ost.noarch

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