On 10/30/14 23:30, Abel Lopez wrote:
As an operator, I'd prefer to have time based criteria over number of rows, too.
I envision something like `nova-manage db purge [days]` where we can leave it
up to the administrator to decide how much of their old data (if any) they'd be
OK losing.
I would
I was wrong, sorry. Floatings assigned as /32 on external interface
inside network namespace. The signle idea I have now - is try to remove
all iptables with NAT (it's destructive up to moment of network node
reboot or router delete/create), and check out if address will reply to
ping.
If 'ye
On 31/10/2014 11:01, Daniele Venzano wrote:
> On 10/30/14 23:30, Abel Lopez wrote:
>> As an operator, I'd prefer to have time based criteria over number of
>> rows, too.
>> I envision something like `nova-manage db purge [days]` where we can
>> leave it up to the administrator to decide how much o
That would imply some extensible plugin type architecture, b/c "all
projects" changes over time and from setup to setup. So each project
would define its own cleanup routines, but those routines could be called
using a common set of parameters from a single tool.
Thx,
britt
On 10/31/14, 8:19 AM,
I've added the same blueprint to cinder/glance/etc. yes, the plan was for
this to be ${service}-manage feature.
On Friday, October 31, 2014, Britt Houser (bhouser)
wrote:
> That would imply some extensible plugin type architecture, b/c "all
> projects" changes over time and from setup to setup.
Hi all,
I wanted to highlight that as mentioned in the OpenStack NFV subteam meeting
yesterday [1] there is a Ops Summit session aiming to bring together those
interested in the use of OpenStack to provide the infrastructure for
communication services. This includes, but is not limited to:
- C
