Open Stack

Just spit balling here....

But wouldn't the way you deploy/patch these patches be good for the
OSOps tools? I bet there is some overlap and having a discussion around
how to get those patches _out_ would be a good topic?

(Probably for the Tools WG, but worth mentioning here)

Best Regards, 
JJ Asghar 
c: 512.619.0722 t: @jjasghar irc: j^2 

On 9/29/15 6:33 PM, Kris G. Lindgren wrote:
> Hello All,
>
> We have some pretty good contributions of local patches on the
> etherpad.  We are going through right now and trying to group patches
> that multiple people are carrying and patches that people may not be
> carrying but solves a problem that they are running into.  If you can
> take some time and either add your own local patches that you have to
> the ether pad or add +1's next to the patches that are laid out, it
> would help us immensely.
>
> The etherpad can be found
> at: https://etherpad.openstack.org/p/operator-local-patches
>
> Thanks for your help!
>
> ___________________________________________________________________
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy
>
> From: "Kris G. Lindgren"
> Date: Tuesday, September 22, 2015 at 4:21 PM
> To: openstack-operators
> Subject: Re: Operator Local Patches
>
> Hello all,
>
> Friendly reminder: If you have local patches and haven't yet done so,
> please contribute to the etherpad
> at: https://etherpad.openstack.org/p/operator-local-patches
>
> ___________________________________________________________________
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy
>
> From: "Kris G. Lindgren"
> Date: Friday, September 18, 2015 at 4:35 PM
> To: openstack-operators
> Cc: Tom Fifield
> Subject: Operator Local Patches
>
> Hello Operators!
>
> During the ops meetup in Palo Alto were we talking about sessions for
> Tokyo. A session that I purposed, that got a bunch of +1's,  was about
> local patches that operators were carrying.  From my experience this
> is done to either implement business logic,  fix assumptions in
> projects that do not apply to your implementation, implement business
> requirements that are not yet implemented in openstack, or fix scale
> related bugs.  What I would like to do is get a working group together
> to do the following:
>
> 1.) Document local patches that operators have (even those that are in
> gerrit right now waiting to be committed upstream)
> 2.) Figure out commonality in those patches
> 3.) Either upstream the common fixes to the appropriate projects or
> figure out if a hook can be added to allow people to run their code at
> that specific point
> 4.) ????
> 5.) Profit
>
> To start this off, I have documented every patch, along with a
> description of what it does and why we did it (where needed), that
> GoDaddy is running [1].  What I am asking is that the operator
> community please update the etherpad with the patches that you are
> running, so that we have a good starting point for discussions in
> Tokyo and beyond.
>
> [1] - https://etherpad.openstack.org/p/operator-local-patches
> ___________________________________________________________________
> Kris Lindgren
> Senior Linux Systems Engineer
> GoDaddy
>
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20150929/61bb73ab/attachment.html>