yahoo-eng-team team mailing list archive

Thread
Date

[Bug 995124] Re: strict constrain for the creation of db tables and columns

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Matt Riedemann <mriedem@xxxxxxxxxx>
Date: Mon, 15 Sep 2014 15:59:29 -0000
Reply-to: Bug 995124 <995124@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

This is being worked by blueprint enforce-unique-instance-uuid-in-db:

https://blueprints.launchpad.net/nova/+spec/enforce-unique-instance-
uuid-in-db

https://review.openstack.org/#/c/97946/

I'm going to track this bug against that blueprint and invalidate this.

** Changed in: nova
       Status: Incomplete => Invalid

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

Title:
  strict constrain for the creation of db tables and columns

Status in OpenStack Compute (Nova):
  Invalid

Bug description:
  Some columns should be defined nullable=False，since they are unique in the table.  For example, address in virtual_interfaces, host in aggregate_hosts, name in aggregates, etc. MySQL is ok, but databases with more strict column creation can yield errors, if it is not strictly defined.
  Due to the same reason, method register_models in nova/db/sqlalchemy/models.py does not work for MYSQL. uuid in instance must be define unique and not null.

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