openstack team mailing list archive

[Joshua Harlow <harlowja@xxxxxxxxxxxxx>]

Right, if there isn't that existing, then I think I might just make a blueprint out of that. I just wanted to check beforehand that I am doing this right, or if it already exists and I did it wrong...

Thx :-)

On 5/2/12 3:57 PM, "Brian Waldon" <brian.waldon@xxxxxxxxxxxxx> wrote:

Jay might have a better answer, but as far as I know, yes. You could probably make the images stores truly pluggable (i.e. not needing to explicitly list them out) without much work.

Brian


On May 2, 2012, at 12:23 PM, Joshua Harlow wrote:

Glance store question??
Hi all,

I am making a y! specific backing store for glance and I was wondering if its really necessary to modify the following file to ensure that the code for that new store gets pulled in (or maybe I'm just doing it wrong).

diff --git a/glance/api/v1/images.py b/glance/api/v1/images.py
index 9839d2e..7c4f565 100644
--- a/glance/api/v1/images.py
+++ b/glance/api/v1/images.py
@@ -47,6 +47,7 @@ import glance.store.http
 import glance.store.rbd
 import glance.store.s3
 import glance.store.swift
+import glance.store.SUPERAWESOMEYSTORE
 from glance.store import (get_from_backend,
                           get_size_from_backend,
                           schedule_delete_from_backend,

Is there another way to make that happen so that it gets registered with glance besides either modifying that file or having a patch which will modify it upon installation (ie an RPM patch)?

Thx!

-Josh
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp