<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">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.<div><br></div><div>Brian<br><div><br></div><div><br><div><div>On May 2, 2012, at 12:23 PM, Joshua Harlow wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">
<title>Glance store question??</title>
<div>
<font face="Calibri, Verdana, Helvetica, Arial"><span style="font-size:11pt">Hi all,<br>
<br>
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).<br>
<br>
diff --git a/glance/api/v1/images.py b/glance/api/v1/images.py<br>
index 9839d2e..7c4f565 100644<br>
--- a/glance/api/v1/images.py<br>
+++ b/glance/api/v1/images.py<br>
@@ -47,6 +47,7 @@ import glance.store.http<br>
import glance.store.rbd<br>
import glance.store.s3<br>
import glance.store.swift<br>
+import glance.store.SUPERAWESOMEYSTORE<br>
from glance.store import (get_from_backend,<br>
get_size_from_backend,<br>
schedule_delete_from_backend,<br>
<br>
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)?<br>
<br>
Thx!<br>
<br>
-Josh</span></font>
</div>
_______________________________________________<br>Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br></blockquote></div><br></div></div></body></html>