[Openstack-operators] /var/lib/nova/instances fs filled up corrupting my Linux instances

Lorin Hochstein lorin at nimbisservices.com
Wed Apr 10 02:27:54 UTC 2013


On Wed, Apr 3, 2013 at 5:52 PM, Andrew Glen-Young <
andrew.glen-young at canonical.com> wrote:

> Hello All,
>
> Apologies, I'm a little late to reply to this thread.
>
> On Sat 16-03-2013 22:38 ›, Lorin Hochstein wrote:
> > On Thu, Mar 14, 2013 at 9:13 PM, Michael Still <mikal at stillhq.com>
> wrote:
> >
> > > On Thu, Mar 14, 2013 at 8:50 PM, Blair Bethwaite
> > > <blair.bethwaite at gmail.com> wrote:
> > >
> > I think my overall learning from this thread is that there's no point
> > > disabling features for a few releases so that operators can test in a
> > > staged manner -- the reality is that testing doesn't occur.
> > >
> >
> >
> > Here's a broader question: what are the other implicit assumptions that
> > devs are making about how ops...er...operate? How can the OpenStack
> project
> > take the experiences of operators and feed that back to the developers so
> > they know what people are really doing in practice?
>
> I have added a note about the new behaviour of the image-cache-manager
> to the 'Upgrade Notes' section of Grizzly's release notes.
>
> This is one way developers can communicate these changes to operators.
>
>
Thanks, Andrew. I changed the wording a little bit in the release notes,
since the functionality was actually enabled by default in Folsom, not
Grizzly. Grizzly has the fix, it just hasn't been extensively tested in
production.


> >
> > For example: do the devs know the circumstances for which operators have
> to
> > poke directly at the database to perform tasks because they can't do what
> > they want with the existing tools?
> >
>
> IMHO these circumstances are bugs that should be filed. In my experience
> the developers are very responsive to address these issues.
>
> This is one way operators can communicate their needs to developers.
>
>
Yes, I've submitted "ops" bugs in the past, and gotten good responses, I'm
not sure how to encourage people to do this more. Perhaps in one of the ops
sessions at the summit, we can encourage folks to submit ops bugs somehow?
Maybe I'll try to sneak in a lightning talk or something...

-- 
Lorin Hochstein
Lead Architect - Cloud Services
Nimbis Services, Inc.
www.nimbisservices.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20130409/7183e230/attachment.html>


More information about the OpenStack-operators mailing list