I do totally agree. Some of the cases could be sorted within the openstack architecture network. But e do need a confederation inside openstack those kind of advanced problems for sure.
You might find a hot fix from the link below. Kind Regards Emrah ASLAN Cisco/Citrix System Engineer [cid:[email protected]] ü www.logicom.com.tr<http://www.logicom.com.tr/> Noramin İş Merkezi | No: 237 /114 | 34398 Maslak ,İstanbul ,TR T: +90 212 2762720 | D: +90 850 2215821 | M: +90 533 2853803 | F: +90 212 2762750 [Description: logidist]<http://www.logicomdistribution.net/> [Description: fb]<https://www.facebook.com/LogicomDistribution>[Description: tw]<https://twitter.com/LogicomDisti>[Description: in]<http://www.linkedin.com/company/164758?trk=tyah&trkInfo=tas%3Alogicom%20distribu%2Cidx%3A1-1-1> Değerli İş Ortaklarımız, Logicom kampanyaları , fırsat, duyuru ve stok bilgilerinin sizlere düzenli ulaşması için aşağıdaki linki tıklayarak e-mail adresinizi güncellemenizi rica ediyoruz. http://visitor.r20.constantcontact.com/manage/optin?v=001t9egDEMH10MEulnTu-Lzln0RXbiYIgR2HnLd_hpHmPb0K44ZxJOya0FvCOF3TI8c2qeErt1Xrn3PlZqntTSqiSTW40PTK2XQ8OlOUe4qYOE%3D From: Craig Tracey [mailto:[email protected]] Sent: Friday, November 07, 2014 8:38 AM To: Abel Lopez Cc: [email protected] Subject: Re: [Openstack-operators] database hoarding Hey Abel, We would be in favor of this as well. So much so that we would definitely be willing to put some resources on it. I'll reach out once we're back from Paris. Great suggestion, Craig On Oct 31, 2014 2:52 PM, "Abel Lopez" <[email protected]<mailto:[email protected]>> wrote: 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) <[email protected]<mailto:[email protected]>> wrote: 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, "Maish Saidel-Keesing" <[email protected]<mailto:[email protected]>> wrote: > >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 of their old data >>> (if any) they'd be OK losing. >> I would certainly use this feature, but please, please, please: make >> it work across all OpenStack databases, not just for Nova, but also >> for Cinder, Neutron, etc. >A Huge +1 for across all projects!! >Maish >> Let's try to get something integrated project-wide instead of having a >> number of poorly documented, slightly inconsistent commands. >> >> >> >> _______________________________________________ >> OpenStack-operators mailing list >> [email protected]<mailto:[email protected]> >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > >-- >Maish Saidel-Keesing > > >_______________________________________________ >OpenStack-operators mailing list >[email protected]<mailto:[email protected]> >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list [email protected]<mailto:[email protected]> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators _______________________________________________ OpenStack-operators mailing list [email protected]<mailto:[email protected]> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________ OpenStack-operators mailing list [email protected] http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
