Hello,
I looked into the problem a little further and it seems to me that this is a
genuine bug.
If I switch from sqlite (that works) to MySQL and restart all the services, I
get the errors I illustrated in my previous post.
The only way I found for surpassing the problem is to manually define
into MySQL all the tables I find in sqlite and restart all the services.
At this point glance-registry does not complain any longer.
The following is the MySQL DDL I obtained by reverse-engineering sqlite
schema:
CREATE TABLE images (
id VARCHAR(36) NOT NULL,
name VARCHAR(255),
size BIGINT,
status VARCHAR(30) NOT NULL,
is_public BOOL NOT NULL,
location TEXT,
created_at DATETIME NOT NULL,
updated_at DATETIME,
deleted_at DATETIME,
deleted BOOL NOT NULL,
disk_format VARCHAR(20),
container_format VARCHAR(20),
checksum VARCHAR(32),
owner VARCHAR(255),
min_disk INTEGER,
min_ram INTEGER,
protected BOOL,
PRIMARY KEY (id),
CHECK (is_public IN (0, 1)),
CHECK (deleted IN (0, 1))
);
CREATE TABLE image_members (
id INTEGER NOT NULL AUTO_INCREMENT
,image_id VARCHAR(36) NOT NULL
,member VARCHAR(255) NOT NULL
,can_share BOOL NOT NULL
,created_at DATETIME NOT NULL
,updated_at DATETIME
,deleted_at DATETIME
,deleted BOOL NOT NULL
,UNIQUE (image_id, member)
,CHECK (can_share IN (0, 1))
,CHECK (deleted IN (0, 1))
,PRIMARY KEY (id)
,FOREIGN KEY(image_id) REFERENCES images (id)
);
CREATE TABLE image_properties (
id INTEGER NOT NULL AUTO_INCREMENT,
image_id VARCHAR(36) NOT NULL,
name VARCHAR(255) NOT NULL,
value TEXT,
created_at DATETIME NOT NULL,
updated_at DATETIME,
deleted_at DATETIME,
deleted BOOL NOT NULL,
PRIMARY KEY (id),
CHECK (deleted IN (0, 1)),
UNIQUE (image_id, name),
FOREIGN KEY(image_id) REFERENCES images (id)
);
CREATE INDEX ix_image_properties_name ON image_properties (name)
CREATE INDEX ix_image_members_deleted ON image_members (deleted);
CREATE INDEX ix_image_members_image_id ON image_members (image_id);
CREATE INDEX ix_image_members_image_id_member ON image_members (image_id,
member);
CREATE INDEX ix_images_deleted ON images (deleted);
CREATE INDEX ix_images_is_public ON images (is_public);
Note that I submitted these instructions into mysql by connecting with
command "mysql -u <myGlanceUser> -p <MyGlanceDB>"
** Changed in: glance (Ubuntu)
Status: Invalid => Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982787
Title:
glance-registry start report error
To manage notifications about this bug go to:
https://bugs.launchpad.net/glance/+bug/982787/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
