[Openstack-operators] A Hypervisor supporting containers

David Kranz dkranz at redhat.com
Fri May 2 20:11:18 UTC 2014

On 05/02/2014 03:03 PM, Jonathan Proulx wrote:
> On Fri, May 2, 2014 at 1:30 PM, Brad Knowles <brad at shub-internet.org> wrote:
>> On May 2, 2014, at 11:27 AM, matt <matt at nycresistor.com> wrote:
>>> most operators do not attend summits.
> That is probably true in the strict sense (I wonder if "most" devs do,
> I doubt it), but many operators do.  My organization is doubling the
> number of ops people we're sending (to 2 :) ) while marketing and
> management is constant at zero.
> It would be interesting to try and capture real numbers on this, maybe
> through the user survey?  Or less formally attendance at the
> Ops-meetup summit (http://junodesignsummit.sched.org/type/ops+meetup)
> sessions, since those are on the "design" schedule we'll probably
> ditch most of the marketeers.
> The Operators Meet-up (or what ever it was called) in San Jose got a
> fair number of operators on fairly short notice with zero marketing
> people, so I think these sorts of sessions are valuable and attract
> enough experienced real world ops people to be useful.
> Of course no point in time event like a summit or meet up is a
> substitute for ongoing feed back processes, but the are important
> especially in building new processes.
> As an operator I've never really felt an us against them friction with
> dev's in OpenStack.  People have bad days on both sides but that's
> just people.  There is a divide are we tend to look at things in
> different ways and on different time scales but I also see a real
> desire and practical work being done to bridge those differences.  I
> don't get it when people try and go to war over issue the both sides
> (from where I sit) seem to genuinely be working to resolve in an open
> collaborative way.
As a former operator and current qa contributor I agree. Also, we should 
focus on the two issues that started this thread:

1. What standard of testing should be required for code to be accepted 
into OpenStack?
2. If existing code does not meet the current standard, should it be 
tossed out of the code base?

These are difficult issues but I really don't see how they necessarily 
break on the dev/operator line. There are reasonable arguments on both 
sides, and one person's "lupus" is another's good engineering practice. 
It is similar to the discussions about api compatibility in that there 
are a lot of different opinions and this community doesn't have a clear 
way to resolve them among the interested parties. It seems that 
ultimately PTLs decide these things.


> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

More information about the OpenStack-operators mailing list