openinfra/refstack
Code Issues Proposed changes

Update to the organization and product tables.

Browse Source 
Add 'properties' column to the organization table.
Add 'product_type' column to the product table.

Change-Id: Ibdbff019bc627e3c65e7c37b334fb674f8c85529
This commit is contained in:
cdiep 2016-02-09 10:39:38 -08:00
parent efe42b6589
commit d98e0d1b97
1 changed files with 17 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
specs/mitaka/approved/vendor-registration-data-model.rst
View File

@ -42,9 +42,9 @@ The following tables will be added to the RefStack database:
* A table named "product" * A table named "product"
This table will contain the product information. Each product must be owned This table will contain the product information. Each product must be owned
by a vendor. A "type" column will be used to identify the different types by a vendor. A "product_type" column will be used to identify the different
of products. The types of products are pre-defined constants (enum) with types of products. The types of products are pre-defined constants (enum)
descriptive names as defined in the OpenStack Marketplace with descriptive names as defined in the OpenStack Marketplace
( http://www.openstack.org/marketplace/). For example: 1 = distro, ( http://www.openstack.org/marketplace/). For example: 1 = distro,
2 = public_cloud, 3 = hosted_private_cloud, etc. 2 = public_cloud, 3 = hosted_private_cloud, etc.
@ -95,6 +95,8 @@ The following tables will be added to the RefStack database.
+------------------------+-------------+----------+ +------------------------+-------------+----------+
| group_id | varchar(36) | FK | | group_id | varchar(36) | FK |
+------------------------+-------------+----------+ +------------------------+-------------+----------+
| properties | text | |
+------------------------+-------------+----------+
* "product" table * "product" table
@ -122,6 +124,8 @@ The following tables will be added to the RefStack database.
+------------------------+-------------+----------+ +------------------------+-------------+----------+
| type | int(11) | | | type | int(11) | |
+------------------------+-------------+----------+ +------------------------+-------------+----------+
| product_type | int(11) | |
+------------------------+-------------+----------+
| public | tinyint(1) | | | public | tinyint(1) | |
+------------------------+-------------+----------+ +------------------------+-------------+----------+
| organization_id | varchar(36) | FK | | organization_id | varchar(36) | FK |
@ -129,6 +133,7 @@ The following tables will be added to the RefStack database.
| properties | text | | | properties | text | |
+------------------------+-------------+----------+ +------------------------+-------------+----------+
**Notes:** **Notes:**
The value of the product_id field is used for storing a secondary ID to The value of the product_id field is used for storing a secondary ID to
@ -141,6 +146,15 @@ The following tables will be added to the RefStack database.
Ideally, the "deleted" column should be of type tinyint(1) (which is a Ideally, the "deleted" column should be of type tinyint(1) (which is a
boolean in SQLAlchemy). Int(11) is used here for being consistent with Oslo. boolean in SQLAlchemy). Int(11) is used here for being consistent with Oslo.
The product_type column will store the pre-defined constants (enum) with
descriptive names as defined in the OpenStack Marketplace
( http://www.openstack.org/marketplace/). For example: 1 = distro,
2 = public_cloud, 3 = hosted_private_cloud, etc.
The values in the "type" column are used by RefStack to identity the type of
the vendor object.
REST API impact REST API impact
--------------- ---------------