Re: [Openstack-operators] user-info.py contribution to osops-tools-contrib

Looking better! Thanks all Edgar On 4/5/16, 5:34 AM, "Bajin, Joseph" wrote: >It’s already been merged.. >https://github.com/openstack/osops-tools-contrib/blob/master/multi/user-info.py > > >So.. Yes it can! :) > > > > > > > > >On 4/5/16, 7:53 AM, "Valery Tschopp"

Re: [Openstack-operators] [osops] Finding ways to get operator issues to projects - Starting with NOVA

I'll throw this out there but the Product Work Group[1] has a place for submitting "User Stories"[2] which are meant to be robust descriptions of problem statements and use cases. Speaking as a core PWG team member, I can say we'd love to have operators submit User Stories with whatever level of

Re: [Openstack-operators] [osops] Finding ways to get operator issues to projects - Starting with NOVA

Hi Christoph, This is a great idea and a tool I think others would be very interested in having. Now the question that I have to you and everyone else, is within the Operators community how would we capture this information so we could open up dialogue with both the Neutron and Nova teams?

Re: [Openstack-operators] [osops] Finding ways to get operator issues to projects - Starting with NOVA

Just sending this out to the Operator Community for more feedback. We'll be having a session at the summit about it, but I'd like to get this discussion going a little more here if we could. --Joe On Sat, Mar 26, 2016 at 4:47 PM, Joseph Bajin wrote: > Operators, > > At

Re: [Openstack-operators] user-info.py contribution to osops-tools-contrib

It’s already been merged.. https://github.com/openstack/osops-tools-contrib/blob/master/multi/user-info.py So.. Yes it can! :) On 4/5/16, 7:53 AM, "Valery Tschopp" wrote: >Hello Edgar, > >Happy to ear that you think it is a great tool. Can it be included in