key_pairs name column should be not null in DB

[David Ripton]

mreidem mentioned this in IRC.

key_pairs.name is not forced to be non-null. But the API enforces that name is not allowed to be null. We should go ahead and add the constraint to the column.

[Boris Pavlovic (boris-42)]

I think that we should wait with this change. Until we implement this BP:
https://blueprints.launchpad.net/nova/+spec/db-sync-models-with-migrations

[Sean Dague (sdague)]

Honestly, this seems like an actual integrity concern, I think it should be more than wishlist.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/163230

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/163230
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=dd52617232c0915c85ca227e975c759c20e41b75
Submitter: Jenkins
Branch: master

commit dd52617232c0915c85ca227e975c759c20e41b75
Author: Kent Wang <email address hidden>
Date: Tue Mar 10 08:44:32 2015 -0700

    Adds Not Null constraint to KeyPair name

    Since the API enforces that name is not null, the database schema and
    model are now updated to enforce this.

    Change-Id: I1088cc79f4998d3b6609891adbb0479381297ec4
    Related-Bug: #1403544
    Closes-Bug: #1189981