Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
On 21/12/13 00:41 -0500, Jay Pipes wrote: On 12/20/2013 10:42 AM, Flavio Percoco wrote: Greetings, In the last Glance meeting, it was proposed to pull out glance's stores[0] code into its own package. There are a couple of other scenarios where using this code is necessary and it could also be useful for other consumers outside OpenStack itself. That being said, it's not clear where this new library should live in: 1) Oslo: it's the place for common code, incubation, although this code has been pretty stable in the last release. 2) glance.stores under Image program: As said in #1, the API has been pretty stable - and it falls perfectly into what Glance's program covers. What about: 3) Cinder Cinder is for block storage. Images are just a bunch of blocks, and all the store drivers do is take a chunked stream of input blocks and store them to disk/swift/s3/rbd/toaster and stream those blocks back out again. So, perhaps the most appropriate place for this is in Cinder-land. This is an interesting suggestion. I wouldn't mind putting it there, although I still prefer it to be under glance for historical reasons and because Glance team knows that code. How would it work if this lib falls under Block Storage program? Should the glance team be added as core contributors of this project? or Just some of them interested in contributing / reviewing those patches? Thanks for the suggestion. I'd like John and Mark to weigh in too. Cheers, FF -- @flaper87 Flavio Percoco pgpoUXdfJuR51.pgp Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
Flavio Percoco wrote: On 21/12/13 00:41 -0500, Jay Pipes wrote: Cinder is for block storage. Images are just a bunch of blocks, and all the store drivers do is take a chunked stream of input blocks and store them to disk/swift/s3/rbd/toaster and stream those blocks back out again. So, perhaps the most appropriate place for this is in Cinder-land. This is an interesting suggestion. I wouldn't mind putting it there, although I still prefer it to be under glance for historical reasons and because Glance team knows that code. How would it work if this lib falls under Block Storage program? Should the glance team be added as core contributors of this project? or Just some of them interested in contributing / reviewing those patches? Thanks for the suggestion. I'd like John and Mark to weigh in too. Programs are a team of people on a specific mission. If the stores code is maintained by a completely separate group (glance devs), then it doesn't belong in the Block Storage program... unless the Cinder devs intend to adopt it over the long run (and therefore the contributors of the Block Storage program form a happy family rather than two separate groups). Depending on the exact nature of the couple of other scenarios where using this code is necessary, I think it would either belong in Glance or in Oslo. -- Thierry Carrez (ttx) signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
On 12/23/2013 05:42 AM, Thierry Carrez wrote: Flavio Percoco wrote: On 21/12/13 00:41 -0500, Jay Pipes wrote: Cinder is for block storage. Images are just a bunch of blocks, and all the store drivers do is take a chunked stream of input blocks and store them to disk/swift/s3/rbd/toaster and stream those blocks back out again. So, perhaps the most appropriate place for this is in Cinder-land. This is an interesting suggestion. I wouldn't mind putting it there, although I still prefer it to be under glance for historical reasons and because Glance team knows that code. How would it work if this lib falls under Block Storage program? Should the glance team be added as core contributors of this project? or Just some of them interested in contributing / reviewing those patches? Thanks for the suggestion. I'd like John and Mark to weigh in too. Programs are a team of people on a specific mission. If the stores code is maintained by a completely separate group (glance devs), then it doesn't belong in the Block Storage program... unless the Cinder devs intend to adopt it over the long run (and therefore the contributors of the Block Storage program form a happy family rather than two separate groups). Understood. The reason I offered this up as a suggestion is that currently Cinder uses the Glance REST API to store and retrieve volume snapshots, and it would be more efficient to just give Cinder the ability to directly retrieve the blocks from one of the underlying store drivers (same goes for Nova's use of Glance). ...and, since the glance.store drivers are dealing with blocks, I thought it made more sense in Cinder. Depending on the exact nature of the couple of other scenarios where using this code is necessary, I think it would either belong in Glance or in Oslo. Perhaps something in olso then. oslo.blockstream? oslo.blockstore? Best, -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
On 23/12/13 07:57 -0500, Jay Pipes wrote: On 12/23/2013 05:42 AM, Thierry Carrez wrote: Flavio Percoco wrote: On 21/12/13 00:41 -0500, Jay Pipes wrote: Cinder is for block storage. Images are just a bunch of blocks, and all the store drivers do is take a chunked stream of input blocks and store them to disk/swift/s3/rbd/toaster and stream those blocks back out again. So, perhaps the most appropriate place for this is in Cinder-land. This is an interesting suggestion. I wouldn't mind putting it there, although I still prefer it to be under glance for historical reasons and because Glance team knows that code. How would it work if this lib falls under Block Storage program? Should the glance team be added as core contributors of this project? or Just some of them interested in contributing / reviewing those patches? Thanks for the suggestion. I'd like John and Mark to weigh in too. Programs are a team of people on a specific mission. If the stores code is maintained by a completely separate group (glance devs), then it doesn't belong in the Block Storage program... unless the Cinder devs intend to adopt it over the long run (and therefore the contributors of the Block Storage program form a happy family rather than two separate groups). Understood. The reason I offered this up as a suggestion is that currently Cinder uses the Glance REST API to store and retrieve volume snapshots, and it would be more efficient to just give Cinder the ability to directly retrieve the blocks from one of the underlying store drivers (same goes for Nova's use of Glance). ...and, since the glance.store drivers are dealing with blocks, I thought it made more sense in Cinder. Depending on the exact nature of the couple of other scenarios where using this code is necessary, I think it would either belong in Glance or in Oslo. Perhaps something in olso then. oslo.blockstream? oslo.blockstore? What about just oslo.store or oslo.objstore ? I'm leaning towards Oslo as well. I know Mark preferred Glance so I'd like him to chime in too. In order to do this, though, we'll need to add some Glance developers to the group of reviewers of this library at least during the Ith release cycle. This will help with providing enough reviews. It'll also help with sharing the knowledge / history about this package. Cheers, FF -- @flaper87 Flavio Percoco pgp5cjcfgpfkO.pgp Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
On Mon, Dec 23, 2013 at 12:11 AM, Flavio Percoco fla...@redhat.com wrote: On 21/12/13 00:41 -0500, Jay Pipes wrote: On 12/20/2013 10:42 AM, Flavio Percoco wrote: Greetings, In the last Glance meeting, it was proposed to pull out glance's stores[0] code into its own package. There are a couple of other scenarios where using this code is necessary and it could also be useful for other consumers outside OpenStack itself. That being said, it's not clear where this new library should live in: 1) Oslo: it's the place for common code, incubation, although this code has been pretty stable in the last release. 2) glance.stores under Image program: As said in #1, the API has been pretty stable - and it falls perfectly into what Glance's program covers. What about: 3) Cinder Cinder is for block storage. Images are just a bunch of blocks, and all the store drivers do is take a chunked stream of input blocks and store them to disk/swift/s3/rbd/toaster and stream those blocks back out again. So, perhaps the most appropriate place for this is in Cinder-land. This is an interesting suggestion. I wouldn't mind putting it there, although I still prefer it to be under glance for historical reasons and because Glance team knows that code. How would it work if this lib falls under Block Storage program? Should the glance team be added as core contributors of this project? or Just some of them interested in contributing / reviewing those patches? Thanks for the suggestion. I'd like John and Mark to weigh in too. I think Jay's suggestion makes a lot of sense. I don't know if the Cinder folks want to take it on, however. I think its going to be easier in a process sense to just keep it in the Glance/Images program. Oslo doesn't seem like the right fit to me, just because this already has a clear owner, and as you said, it doesn't really need an unstable api cleanup phase (I know you were not proposing it start out in copy-around mode.) Cheers, FF -- @flaper87 Flavio Percoco ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
On Mon, Dec 23, 2013 at 4:57 AM, Jay Pipes jaypi...@gmail.com wrote: On 12/23/2013 05:42 AM, Thierry Carrez wrote: Flavio Percoco wrote: On 21/12/13 00:41 -0500, Jay Pipes wrote: Cinder is for block storage. Images are just a bunch of blocks, and all the store drivers do is take a chunked stream of input blocks and store them to disk/swift/s3/rbd/toaster and stream those blocks back out again. So, perhaps the most appropriate place for this is in Cinder-land. This is an interesting suggestion. I wouldn't mind putting it there, although I still prefer it to be under glance for historical reasons and because Glance team knows that code. How would it work if this lib falls under Block Storage program? Should the glance team be added as core contributors of this project? or Just some of them interested in contributing / reviewing those patches? Thanks for the suggestion. I'd like John and Mark to weigh in too. Programs are a team of people on a specific mission. If the stores code is maintained by a completely separate group (glance devs), then it doesn't belong in the Block Storage program... unless the Cinder devs intend to adopt it over the long run (and therefore the contributors of the Block Storage program form a happy family rather than two separate groups). Understood. The reason I offered this up as a suggestion is that currently Cinder uses the Glance REST API to store and retrieve volume snapshots, and it would be more efficient to just give Cinder the ability to directly retrieve the blocks from one of the underlying store drivers (same goes for Nova's use of Glance). ...and, since the glance.store drivers are dealing with blocks, I thought it made more sense in Cinder. True, Cinder and Nova should be talking more directly to the underlying stores--however their direct interface should probably be through glanceclient. (Glanceclient could evolve to use the glance.store code I imagine.) Depending on the exact nature of the couple of other scenarios where using this code is necessary, I think it would either belong in Glance or in Oslo. Perhaps something in olso then. oslo.blockstream? oslo.blockstore? Best, -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
On 12/23/2013 08:48 AM, Mark Washenberger wrote: On Mon, Dec 23, 2013 at 4:57 AM, Jay Pipes jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: On 12/23/2013 05:42 AM, Thierry Carrez wrote: Flavio Percoco wrote: On 21/12/13 00:41 -0500, Jay Pipes wrote: Cinder is for block storage. Images are just a bunch of blocks, and all the store drivers do is take a chunked stream of input blocks and store them to disk/swift/s3/rbd/toaster and stream those blocks back out again. So, perhaps the most appropriate place for this is in Cinder-land. This is an interesting suggestion. I wouldn't mind putting it there, although I still prefer it to be under glance for historical reasons and because Glance team knows that code. How would it work if this lib falls under Block Storage program? Should the glance team be added as core contributors of this project? or Just some of them interested in contributing / reviewing those patches? Thanks for the suggestion. I'd like John and Mark to weigh in too. Programs are a team of people on a specific mission. If the stores code is maintained by a completely separate group (glance devs), then it doesn't belong in the Block Storage program... unless the Cinder devs intend to adopt it over the long run (and therefore the contributors of the Block Storage program form a happy family rather than two separate groups). Understood. The reason I offered this up as a suggestion is that currently Cinder uses the Glance REST API to store and retrieve volume snapshots, and it would be more efficient to just give Cinder the ability to directly retrieve the blocks from one of the underlying store drivers (same goes for Nova's use of Glance). ...and, since the glance.store drivers are dealing with blocks, I thought it made more sense in Cinder. True, Cinder and Nova should be talking more directly to the underlying stores--however their direct interface should probably be through glanceclient. (Glanceclient could evolve to use the glance.store code I imagine.) Hmm, that is a very interesting suggestion. glanceclient containing the store drivers. I like it. Will be a bit weird, though, having the glanceclient call the Glance API server to get the storage location details, which then calls the glanceclient code to store/retrieve the blocks :) -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
On 23/12/13 09:00 -0500, Jay Pipes wrote: On 12/23/2013 08:48 AM, Mark Washenberger wrote: On Mon, Dec 23, 2013 at 4:57 AM, Jay Pipes jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: On 12/23/2013 05:42 AM, Thierry Carrez wrote: Flavio Percoco wrote: On 21/12/13 00:41 -0500, Jay Pipes wrote: Cinder is for block storage. Images are just a bunch of blocks, and all the store drivers do is take a chunked stream of input blocks and store them to disk/swift/s3/rbd/toaster and stream those blocks back out again. So, perhaps the most appropriate place for this is in Cinder-land. This is an interesting suggestion. I wouldn't mind putting it there, although I still prefer it to be under glance for historical reasons and because Glance team knows that code. How would it work if this lib falls under Block Storage program? Should the glance team be added as core contributors of this project? or Just some of them interested in contributing / reviewing those patches? Thanks for the suggestion. I'd like John and Mark to weigh in too. Programs are a team of people on a specific mission. If the stores code is maintained by a completely separate group (glance devs), then it doesn't belong in the Block Storage program... unless the Cinder devs intend to adopt it over the long run (and therefore the contributors of the Block Storage program form a happy family rather than two separate groups). Understood. The reason I offered this up as a suggestion is that currently Cinder uses the Glance REST API to store and retrieve volume snapshots, and it would be more efficient to just give Cinder the ability to directly retrieve the blocks from one of the underlying store drivers (same goes for Nova's use of Glance). ...and, since the glance.store drivers are dealing with blocks, I thought it made more sense in Cinder. True, Cinder and Nova should be talking more directly to the underlying stores--however their direct interface should probably be through glanceclient. (Glanceclient could evolve to use the glance.store code I imagine.) Hmm, that is a very interesting suggestion. glanceclient containing the store drivers. I like it. Will be a bit weird, though, having the glanceclient call the Glance API server to get the storage location details, which then calls the glanceclient code to store/retrieve the blocks :) Exactly. This is part of the original idea. Allow Glance, nova, glanceclient and cinder to interact with the store code. -- @flaper87 Flavio Percoco pgpc0yiev4T5j.pgp Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
On Mon, Dec 23, 2013 at 10:26 PM, Flavio Percoco fla...@redhat.com wrote: On 23/12/13 09:00 -0500, Jay Pipes wrote: On 12/23/2013 08:48 AM, Mark Washenberger wrote: On Mon, Dec 23, 2013 at 4:57 AM, Jay Pipes jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: On 12/23/2013 05:42 AM, Thierry Carrez wrote: Flavio Percoco wrote: On 21/12/13 00:41 -0500, Jay Pipes wrote: Cinder is for block storage. Images are just a bunch of blocks, and all the store drivers do is take a chunked stream of input blocks and store them to disk/swift/s3/rbd/toaster and stream those blocks back out again. So, perhaps the most appropriate place for this is in Cinder-land. This is an interesting suggestion. I wouldn't mind putting it there, although I still prefer it to be under glance for historical reasons and because Glance team knows that code. How would it work if this lib falls under Block Storage program? Should the glance team be added as core contributors of this project? or Just some of them interested in contributing / reviewing those patches? Thanks for the suggestion. I'd like John and Mark to weigh in too. Programs are a team of people on a specific mission. If the stores code is maintained by a completely separate group (glance devs), then it doesn't belong in the Block Storage program... unless the Cinder devs intend to adopt it over the long run (and therefore the contributors of the Block Storage program form a happy family rather than two separate groups). Understood. The reason I offered this up as a suggestion is that currently Cinder uses the Glance REST API to store and retrieve volume snapshots, and it would be more efficient to just give Cinder the ability to directly retrieve the blocks from one of the underlying store drivers (same goes for Nova's use of Glance). ...and, since the glance.store drivers are dealing with blocks, I thought it made more sense in Cinder. True, Cinder and Nova should be talking more directly to the underlying stores--however their direct interface should probably be through glanceclient. (Glanceclient could evolve to use the glance.store code I imagine.) Hmm, that is a very interesting suggestion. glanceclient containing the store drivers. I like it. Will be a bit weird, though, having the glanceclient call the Glance API server to get the storage location details, which then calls the glanceclient code to store/retrieve the blocks :) Exactly. This is part of the original idea. Allow Glance, nova, glanceclient and cinder to interact with the store code. Actually I consider this Glance store stuff can be packaged to a dedicated common lib belongs to Glance, maybe we can put it into glanceclient if we don't like create a new sub-lib, IMO it worked just like current Cinder's brick lib IMO, in sort term. In long term we can move those stuff all to oslo when they stable enough (if we can see that day ;) ) and don't organize them by project's POV but storage type: oslo.blockstore (or other name) for block storage backend handling, and oslo.objectstore for object storage, and upper layer project just delegate all real storage device operation requests to those lib, like mount/attach, unmoun/detach, read/write.. zhiyan -- @flaper87 Flavio Percoco ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
On 23/12/13 22:46 +0800, Zhi Yan Liu wrote: On Mon, Dec 23, 2013 at 10:26 PM, Flavio Percoco fla...@redhat.com wrote: On 23/12/13 09:00 -0500, Jay Pipes wrote: On 12/23/2013 08:48 AM, Mark Washenberger wrote: On Mon, Dec 23, 2013 at 4:57 AM, Jay Pipes jaypi...@gmail.com mailto:jaypi...@gmail.com wrote: On 12/23/2013 05:42 AM, Thierry Carrez wrote: Flavio Percoco wrote: On 21/12/13 00:41 -0500, Jay Pipes wrote: Cinder is for block storage. Images are just a bunch of blocks, and all the store drivers do is take a chunked stream of input blocks and store them to disk/swift/s3/rbd/toaster and stream those blocks back out again. So, perhaps the most appropriate place for this is in Cinder-land. This is an interesting suggestion. I wouldn't mind putting it there, although I still prefer it to be under glance for historical reasons and because Glance team knows that code. How would it work if this lib falls under Block Storage program? Should the glance team be added as core contributors of this project? or Just some of them interested in contributing / reviewing those patches? Thanks for the suggestion. I'd like John and Mark to weigh in too. Programs are a team of people on a specific mission. If the stores code is maintained by a completely separate group (glance devs), then it doesn't belong in the Block Storage program... unless the Cinder devs intend to adopt it over the long run (and therefore the contributors of the Block Storage program form a happy family rather than two separate groups). Understood. The reason I offered this up as a suggestion is that currently Cinder uses the Glance REST API to store and retrieve volume snapshots, and it would be more efficient to just give Cinder the ability to directly retrieve the blocks from one of the underlying store drivers (same goes for Nova's use of Glance). ...and, since the glance.store drivers are dealing with blocks, I thought it made more sense in Cinder. True, Cinder and Nova should be talking more directly to the underlying stores--however their direct interface should probably be through glanceclient. (Glanceclient could evolve to use the glance.store code I imagine.) Hmm, that is a very interesting suggestion. glanceclient containing the store drivers. I like it. Will be a bit weird, though, having the glanceclient call the Glance API server to get the storage location details, which then calls the glanceclient code to store/retrieve the blocks :) Exactly. This is part of the original idea. Allow Glance, nova, glanceclient and cinder to interact with the store code. Actually I consider this Glance store stuff can be packaged to a dedicated common lib belongs to Glance, maybe we can put it into glanceclient if we don't like create a new sub-lib, IMO it worked just like current Cinder's brick lib IMO, in sort term. I don't like the idea of having it in the client. I'd prefer the client to just consume it. IMHO, glance.store sounds like the way to go here. In long term we can move those stuff all to oslo when they stable enough (if we can see that day ;) ) and don't organize them by project's POV but storage type: oslo.blockstore (or other name) for block storage backend handling, and oslo.objectstore for object storage, and upper layer project just delegate all real storage device operation requests to those lib, like mount/attach, unmoun/detach, read/write.. mhh, not sure. That sounds like way more of what the lib should do. IMHO, this lib shouldn't take care of any admin operation, it should be just about getting / putting data into those stores. -- @flaper87 Flavio Percoco pgpxQokq35Y0G.pgp Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
Greetings, In the last Glance meeting, it was proposed to pull out glance's stores[0] code into its own package. There are a couple of other scenarios where using this code is necessary and it could also be useful for other consumers outside OpenStack itself. That being said, it's not clear where this new library should live in: 1) Oslo: it's the place for common code, incubation, although this code has been pretty stable in the last release. 2) glance.stores under Image program: As said in #1, the API has been pretty stable - and it falls perfectly into what Glance's program covers. [0] https://github.com/openstack/glance/tree/master/glance/store/ Thoughts? Cheers, FF -- @flaper87 Flavio Percoco pgpSaOGX3Qu0u.pgp Description: PGP signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
On Fri, Dec 20, 2013 at 10:42 AM, Flavio Percoco fla...@redhat.com wrote: Greetings, In the last Glance meeting, it was proposed to pull out glance's stores[0] code into its own package. There are a couple of other scenarios where using this code is necessary and it could also be useful for other consumers outside OpenStack itself. That being said, it's not clear where this new library should live in: 1) Oslo: it's the place for common code, incubation, although this code has been pretty stable in the last release. 2) glance.stores under Image program: As said in #1, the API has been pretty stable - and it falls perfectly into what Glance's program covers. Either makes sense. If the glance team is going to continue maintaining the code, it may make more sense to create a repo managed by glance-core. One note, unless glance is using a namespace package, the name for the library can't be glance.store, unfortunately. It wouldn't be difficult to make that sort of structure work, though, so if you like the name it would just mean some changes to glance and its packaging. Doug [0] https://github.com/openstack/glance/tree/master/glance/store/ Thoughts? Cheers, FF -- @flaper87 Flavio Percoco ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance][Oslo] Pulling glance.store out of glance. Where should it live?
On 12/20/2013 10:42 AM, Flavio Percoco wrote: Greetings, In the last Glance meeting, it was proposed to pull out glance's stores[0] code into its own package. There are a couple of other scenarios where using this code is necessary and it could also be useful for other consumers outside OpenStack itself. That being said, it's not clear where this new library should live in: 1) Oslo: it's the place for common code, incubation, although this code has been pretty stable in the last release. 2) glance.stores under Image program: As said in #1, the API has been pretty stable - and it falls perfectly into what Glance's program covers. What about: 3) Cinder Cinder is for block storage. Images are just a bunch of blocks, and all the store drivers do is take a chunked stream of input blocks and store them to disk/swift/s3/rbd/toaster and stream those blocks back out again. So, perhaps the most appropriate place for this is in Cinder-land. Best, -jay ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
