Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On Tue, 22 Dec 2015 08:56:08 -0800 Clint Byrum wrote: > You could create a unique swift container, upload things to that, and > then update a pointer in a well-known location to point at that container > for the new plan only after you've verified it is available. This is a >

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

thats somewhat limiting though... We use ceph here because we can pool our storage between the swift protocol endpoint, and the block storage system. It doesn't make us partition up our storage. I can totally see a case where you'd maybe just scale out your undercloud ceph for use in the

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On Tue, 2015-12-22 at 15:36 +, Dougal Matthews wrote: > Hi all, > > This topic came up in the 2015-12-15 meeting[1], and again briefly > today. > After working with the code that came out of the deployment library > spec[2] I > had some concerns with how we are storing the templates. > >

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

I don't think the radosgw supports bulk yet. They haven't for a very long time. :/ Thanks, Kevin From: Dan Prince [dpri...@redhat.com] Sent: Thursday, January 07, 2016 9:03 AM To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 01/06/2016 11:48 AM, Dougal Matthews wrote: On 5 January 2016 at 17:09, Jiri Tomasek > wrote: On 12/23/2015 07:40 PM, Steven Hardy wrote: On Wed, Dec 23, 2015 at 11:05:05AM -0600, Ben Nemec wrote: On 12/23/2015

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 5 January 2016 at 17:09, Jiri Tomasek wrote: > On 12/23/2015 07:40 PM, Steven Hardy wrote: > >> On Wed, Dec 23, 2015 at 11:05:05AM -0600, Ben Nemec wrote: >> >>> On 12/23/2015 10:26 AM, Steven Hardy wrote: >>> On Wed, Dec 23, 2015 at 09:28:59AM -0600, Ben Nemec

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 6 January 2016 at 12:30, Ryan Brown wrote: > On 12/23/2015 04:19 AM, Dougal Matthews wrote: > >> >> >> On 22 December 2015 at 17:59, Ben Nemec > > wrote: >> >> Can we just do git like I've been suggesting all

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 12/23/2015 04:19 AM, Dougal Matthews wrote: On 22 December 2015 at 17:59, Ben Nemec > wrote: Can we just do git like I've been suggesting all along? ;-) More serious discussion inline. :-) On 12/22/2015 09:36 AM, Dougal

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

When you state Swift I assume you mean TripleO will use swift APIs to access objects in it (template, metadata, etc). There are many environment where there is no swift but Ceph or other object store that can be used for it using swift APIs. Are all these will be under single user/project that

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 12/23/2015 07:40 PM, Steven Hardy wrote: On Wed, Dec 23, 2015 at 11:05:05AM -0600, Ben Nemec wrote: On 12/23/2015 10:26 AM, Steven Hardy wrote: On Wed, Dec 23, 2015 at 09:28:59AM -0600, Ben Nemec wrote: On 12/23/2015 03:19 AM, Dougal Matthews wrote: On 22 December 2015 at 17:59, Ben

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 22/12/15 11:56, Clint Byrum wrote: Excerpts from Dougal Matthews's message of 2015-12-22 07:36:02 -0800: Hi all, This topic came up in the 2015-12-15 meeting[1], and again briefly today. After working with the code that came out of the deployment library spec[2] I had some concerns with how

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

The glance artefact service is glare. swift isn't atomic though. you can get inconsistent reads for a while between different files that can cause issues. big +1 for making a glare artefact type for a set of heat templates. My heat templates are usually a collection of nested templates,

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On Tue, Dec 22, 2015 at 03:36:02PM +, Dougal Matthews wrote: >Hi all, > >This topic came up in the 2015-12-15 meeting[1], and again briefly today. >After working with the code that came out of the deployment library >spec[2] I >had some concerns with how we are storing the

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On Wed, Dec 23, 2015 at 09:28:59AM -0600, Ben Nemec wrote: > On 12/23/2015 03:19 AM, Dougal Matthews wrote: > > > > > > On 22 December 2015 at 17:59, Ben Nemec > > wrote: > > > > Can we just do git like I've been suggesting all along?

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 23 December 2015 at 12:01, Steven Hardy wrote: > On Tue, Dec 22, 2015 at 03:36:02PM +, Dougal Matthews wrote: > >Hi all, > > > >This topic came up in the 2015-12-15 meeting[1], and again briefly > today. > >After working with the code that came out of the

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 12/23/2015 01:01 PM, Steven Hardy wrote: On Tue, Dec 22, 2015 at 03:36:02PM +, Dougal Matthews wrote: Hi all, This topic came up in the 2015-12-15 meeting[1], and again briefly today. After working with the code that came out of the deployment library spec[2] I had

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 23 December 2015 at 12:01, Steven Hardy wrote: > On Tue, Dec 22, 2015 at 03:36:02PM +, Dougal Matthews wrote: > >Hi all, > > > >This topic came up in the 2015-12-15 meeting[1], and again briefly > today. > >After working with the code that came out of the

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On Wed, Dec 23, 2015 at 11:05:05AM -0600, Ben Nemec wrote: > On 12/23/2015 10:26 AM, Steven Hardy wrote: > > On Wed, Dec 23, 2015 at 09:28:59AM -0600, Ben Nemec wrote: > >> On 12/23/2015 03:19 AM, Dougal Matthews wrote: > >>> > >>> > >>> On 22 December 2015 at 17:59, Ben Nemec

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 12/23/2015 10:26 AM, Steven Hardy wrote: > On Wed, Dec 23, 2015 at 09:28:59AM -0600, Ben Nemec wrote: >> On 12/23/2015 03:19 AM, Dougal Matthews wrote: >>> >>> >>> On 22 December 2015 at 17:59, Ben Nemec >> > wrote: >>> >>> Can we just

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 22 December 2015 at 16:56, Clint Byrum wrote: > Excerpts from Dougal Matthews's message of 2015-12-22 07:36:02 -0800: > > Hi all, > > > > This topic came up in the 2015-12-15 meeting[1], and again briefly today. > > After working with the code that came out of the deployment

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 22 December 2015 at 18:50, Julien Danjou wrote: > On Tue, Dec 22 2015, Dougal Matthews wrote: > > > - Store the files in a tarball (so we only deal with one file). I think > we > >could still hit issues with multiple operations unless we guarantee > that > >only

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 22 December 2015 at 17:59, Ben Nemec wrote: > Can we just do git like I've been suggesting all along? ;-) > > More serious discussion inline. :-) > > On 12/22/2015 09:36 AM, Dougal Matthews wrote: > > Hi all, > > > > This topic came up in the 2015-12-15 meeting[1], and

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On Wed, Dec 23 2015, Dougal Matthews wrote: > Good to know, thanks. I guess the remaining issue would be with the work > Tomas Sedovic mentioned. It sounds like Swift might not work well there. Right, reply below. On Tue, Dec 22 2015, Tomas Sedovic wrote: > At minimum, we'd have to store the

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 22 December 2015 at 19:29, Dan Prince wrote: > On Tue, 2015-12-22 at 15:36 +, Dougal Matthews wrote: > > Hi all, > > > > This topic came up in the 2015-12-15 meeting[1], and again briefly > > today. > > After working with the code that came out of the deployment

[openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

Hi all, This topic came up in the 2015-12-15 meeting[1], and again briefly today. After working with the code that came out of the deployment library spec[2] I had some concerns with how we are storing the templates. Simply put, when we are dealing with 100+ files from tripleo-heat-templates how

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On Tue, Dec 22 2015, Dougal Matthews wrote: > - Store the files in a tarball (so we only deal with one file). I think we >could still hit issues with multiple operations unless we guarantee that >only one instance of the API is ever running. That shouldn't be a problem since the

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On Tue, 2015-12-22 at 15:36 +, Dougal Matthews wrote: > Hi all, > > This topic came up in the 2015-12-15 meeting[1], and again briefly > today. > After working with the code that came out of the deployment library > spec[2] I > had some concerns with how we are storing the templates. > >

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

Can we just do git like I've been suggesting all along? ;-) More serious discussion inline. :-) On 12/22/2015 09:36 AM, Dougal Matthews wrote: > Hi all, > > This topic came up in the 2015-12-15 meeting[1], and again briefly today. > After working with the code that came out of the deployment

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 12/22/2015 11:17 AM, Tomas Sedovic wrote: > On 12/22/2015 04:36 PM, Dougal Matthews wrote: >> Hi all, >> >> This topic came up in the 2015-12-15 meeting[1], and again briefly today. >> After working with the code that came out of the deployment library >> spec[2] I >> had some concerns with how

Re: [openstack-dev] [TripleO] Is Swift a good choice of database for the TripleO API?

On 12/22/2015 04:36 PM, Dougal Matthews wrote: Hi all, This topic came up in the 2015-12-15 meeting[1], and again briefly today. After working with the code that came out of the deployment library spec[2] I had some concerns with how we are storing the templates. For alternatives, I see a