Opened this blueprint,
I've started doing part of it, with the simple way of doing it (add a new
config list that specifies the stores and import them at startup...)
Something like:
--- a/etc/glance-api.conf
+++ b/etc/glance-api.conf
@@ -5,10 +5,17 @@ verbose = True
# Show debugging output in
Andrew is doing some work on a plugin architecture. This sounds like
another good application of that.
On Wed, May 2, 2012 at 7:01 PM, Joshua Harlow harlo...@yahoo-inc.comwrote:
Right, if there isn’t that existing, then I think I might just make a
blueprint out of that. I just wanted to check
He definitely is, but its scope is limited to Nova (for now?). The idea
discussed below is something we could use without having to worry about a
Glance plugin implementation. We can talk about plugins for Glance later.
Brian
On May 3, 2012, at 10:58 AM, Doug Hellmann wrote:
Andrew is doing
Ok, although I wonder if a plug-in framework could benefit from just being
generic enough to be used in either place?
I think he's focusing on the notification system right now (being more
pluggable) there, so that be his scope for now. I'm willing to work together to
make that more generic so
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
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.wal...@rackspace.com wrote:
Jay might have a
6 matches
Mail list logo
