Re: [Openstack-operators] Fwd: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

All the different projects have different ways of reporting bugs and looking for features. You can see a few of the different ways that the Operators discussed back at the Summit here - https://etherpad.openstack.org/p/AUS-ops-Requests-for-Enhancement-Process That should give you some more

Re: [Openstack-operators] Fwd: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

Ya, I'd like to make sure that whoever starts applying these messages to bugs automagically takes into account that people may (or may not have) spent a lot of (personal or other) time reporting a bug and take that into account when producing a polite and thankful message to those that have

Re: [Openstack-operators] About Live Migration and Bests practises.

In general with L-M on a libvirt/kvm based env, I would cc: daniel barrange (barra...@redhat.com) and I've done that since I didn't seem him specifically. We have taken to GENERALLY SPEAKING doing a single VM at a time. If we have high confidence, we'll go 5 at a time (but never more than that)

[Openstack-operators] Keystone issues when upgrading from Kilo to Liberty

I am working on our Kilo->Liberty upgrade path at present, and when upgrading existing test Kilo controller nodes to Liberty, Keystone gets extremely weird. When evaluating token timestamps for revocation, it looks like sometimes the timestamps are processed as datetime.datetime objects and

Re: [Openstack-operators] Fwd: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

Seems like a great approach. You might want to also include: This bug was probably not triaged due to lack of information to reproduce the issue. Please include as much information about the problem including steps to allow a developer to reproduce the issue in order for your time in reporting

[Openstack-operators] About Live Migration and Bests practises.

Greetings, First thanks a lot for all the information provided regarding OpenStack and thanks for your hudge work on this topic. (Live Migration) We are operating an OpenStack setup running Kilo + Ceph + (ceph_patch_for_snapshot). We are still playing with live migration on Kilo and we had

Re: [Openstack-operators] [craton] Versions of Python to support for Craton

On Wed, May 25, 2016 at 12:47 PM, Tim Bell wrote: > Slight concern on how to deploy on a RHEL system base as software > collections are non-trivial. > But also worth keeping in mind, Craton and its dependencies (most significantly, MySQL or PostgreSQL, + Taskflow dependencies,

Re: [Openstack-operators] Nova 2.1 and user permissions in the policy file

On 05/27/2016 04:23 AM, Dario Vianello wrote: > >> On 25 May 2016, at 17:31, Tim Bell > > wrote: >> >> >> On 25/05/16 17:36, "Sean Dague" > > wrote: >> >>> On 05/23/2016 10:24 AM, Tim Bell wrote:

Re: [Openstack-operators] Fwd: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

Minor, but "This bug report has been closed [...]" sounds much better than "This bug report got closed [...]" - Aubrey Wells Manager, Network Operations Digium Cloud Services Main: 888.305.3850 Support: 877.344.4861 or http://www.digium.com/en/support

Re: [Openstack-operators] Fwd: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

On 27.05.2016 15:47, Vincent Legoll wrote: > Hello, > > Le 27/05/2016 15:25, Markus Zoeller a écrit : >> I don't see a benefit in leaving very old bug reports open when nobody >> is working on it (again, a resource problem). Closing it (with "Won't >> Fix") is explicit and easy to query. The

Re: [Openstack-operators] Fwd: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

Hello, Le 27/05/2016 15:25, Markus Zoeller a écrit : I don't see a benefit in leaving very old bug reports open when nobody is working on it (again, a resource problem). Closing it (with "Won't Fix") is explicit and easy to query. The information is not lost. This does*not* mean we don't care

Re: [Openstack-operators] Fwd: [openstack-dev] [nova] I'm going to expire open bug reports older than 18 months.

Maybe a few more words on this ML *why* I'm doing this. It all comes down to a simple resource problem. Far more bug reports get filed than solved. For the last 3 releases the numbers [1][2][3] are: Kilo Liberty Mitaka Filed Bugs: 1144 926 968

Re: [Openstack-operators] Nova 2.1 and user permissions in the policy file

> On 25 May 2016, at 17:31, Tim Bell wrote: > > > On 25/05/16 17:36, "Sean Dague" > > wrote: > >> On 05/23/2016 10:24 AM, Tim Bell wrote: >>> >>> >>> Quick warning for those who are dependent on the "user_id:%(user_id)s" >>> syntax