[Openstack-operators] [openstack-dev][openstack-operators]flush expired tokens and moves deleted instance
matthew.fischer at twcable.com
Tue Jan 27 18:49:26 UTC 2015
On 1/27/15, 10:21 AM, "gustavo panizzo (gfa)" <gfa at zumbi.com.ar> wrote:
>On 01/28/2015 01:13 AM, Fischer, Matt wrote:
>> Our keystone database is clustered across regions, so we have this job
>> running on node1 in each site on alternating hours. I don¹t think you¹d
>> want a bunch of cron jobs firing off all at once to cleanup tokens on
>> multiple clustered nodes. That¹s one reason I know not to put this in
>> the code.
>i prefer a cronjob to something on the code that i have to test,
>configure and possible troubleshot
>besides, i think is well documented. i don't see a problem there.
>maybe distributions could ship the script into /etc/cron.daily by
>default? i would remove it on my case but is a good default for simple
>1AE0 322E B8F7 4717 BDEA BF1D 44BB 1BA7 9F6C 6333
Just to be clear we¹re also using cronjobs, we just configure and set them
up with puppet, so not really custom code. If the package starts
installing them, we¹ll just remove them with puppet and do our own again
What I¹d like to know is whether there are reasons that someone might want
to keep their tokens and not have this running by default.
This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
More information about the OpenStack-operators