Open Stack

On 7/1/16, 8:48 PM, "Ian Cordasco" <sigmavirus24 at gmail.com> wrote:



>-----Original Message-----
>From: Jesse Pretorius <jesse.pretorius at rackspace.co.uk>
>
>> In a recent conversation on the Operators list [1] there was a discussion about purging
>> archived data in the database. It would seem to me an important step in maintaining an
>> environment which should be done from time to time and perhaps at the very least prior
>> to a major upgrade.
>>
>> What’re the thoughts on how often this should be done? Should we include it as an opt-in
>> step, or an opt-out step?
>>
>> [1] http://lists.openstack.org/pipermail/openstack-operators/2016-June/010813.html
>
>Is OpenStack-Ansible now going to get into the minutae of operating
>the entire cloud? I was under the impression that it left the easy
>things to the operators (e.g., deciding when and how to purge the
>database) while taking care of the things that are less obvious
>(setting up OpenStack, and interacting with the database directly to
>only set up things for the services).

That’s a good question which betrays the fact that I phrased my question poorly. :)

The question is whether we should do something like this:

1) As part of the normal execution of the service playbooks;
2) As part of the automated major upgrade (i.e. The step is not optional);
3) As part of the manual major upgrade (i.e. The step is optional);
4) Never.

If never, it might be useful for our community to curate a few bits of operations tooling to automated this sort of thing on demand. The tooling can be placed into the Ops repository [1] if this is done.

[1] https://github.com/openstack/openstack-ansible-ops

________________________________
Rackspace Limited is a company registered in England & Wales (company registered number 03897010) whose registered office is at 5 Millington Road, Hyde Park Hayes, Middlesex UB3 4AZ. Rackspace Limited privacy policy can be viewed at www.rackspace.co.uk/legal/privacy-policy - This e-mail message may contain confidential or privileged information intended for the recipient. Any dissemination, distribution or copying of the enclosed material is prohibited. If you receive this transmission in error, please notify us immediately by e-mail at abuse at rackspace.com and delete the original message. Your cooperation is appreciated.