Open Stack

+2

It'd be nice to start putting historical data by default into HDFS (via
sahara?) and leave the databases as only what exists 'now'.

Then people can setup pig or other hadoop jobs and analyze there data as
they wish (slice and dice thousands of ways...)

-----Original Message-----
From: Robert Collins <robertc at robertcollins.net>
Reply-To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev at lists.openstack.org>
Date: Wednesday, April 9, 2014 at 7:45 AM
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev at lists.openstack.org>
Subject: Re: [openstack-dev] [nova] Server Groups are not an optional
element, bug or feature ?

>On 10 April 2014 02:32, Chris Friesen <chris.friesen at windriver.com> wrote:
>> On 04/09/2014 03:45 AM, Day, Phil wrote:
>>>>
>>>> -----Original Message----- From: Russell Bryant
>>
>>
>>>> We were thinking that there may be a use for being able to query a
>>>> full list of instances (including the deleted ones) for a group.
>>>> The API just hasn't made it that far yet.  Just hiding them for now
>>>> leaves room to iterate and doesn't prevent either option (exposing
>>>> the deleted instances, or changing to auto- delete them from the
>>>> group).
>>
>>
>>> Maybe it's just me, but I have a natural aversion to anything that
>>> grows forever in the database - over time and at scale this becomes a
>>> real problem.
>>
>>
>> Not just you.  I want my main database to reflect the current active
>>data.
>> Historical data should go somewhere else.
>
>+1. Fastest way to make an OLTP workload crawl is to mix it up with
>warehousing.
>
>-Rob
>
>-- 
>Robert Collins <rbtcollins at hp.com>
>Distinguished Technologist
>HP Converged Cloud
>
>_______________________________________________
>OpenStack-dev mailing list
>OpenStack-dev at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev