Re: [Openstack-operators] [openstack-dev] Open letter/request to TC candidates (and existing elected officials)

.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Openstack] Certifying SDKs

> Post to : openst...@lists.openstack.org >> Unsubscribe : >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >> >> >> -- >> Volodymyr Litovka >> "Vision without Execution is Hallucination." -- Tho

Re: [Openstack-operators] [openstack-dev] Upstream LTS Releases

saying that they're maintaining >> the branch. >> >> Doug >> >> ______ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.o

Re: [Openstack-operators] [openstack-dev] LTS pragmatic example

s that is a first step towards LTS eventually. Thanks, Dims On Wed, Nov 15, 2017 at 2:46 AM, Flavio Percoco <fla...@redhat.com> wrote: > On 14/11/17 22:33 +1100, Davanum Srinivas wrote: >> >> Saverio, >> >> This is still under the stable team reviews... NOT LTS. >&

Re: [Openstack-operators] [openstack-dev] LTS pragmatic example

Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-operators m

Re: [Openstack-operators] [openstack-dev] Upstream LTS Releases

releases is insufficient. We are all trying to listen to > users' needs. Continuing to just say "we should do LTS releases" > however doesn't acknowledge the other long standing fact, which is > that over all of the time we have talked about it we have had *no > contributors willing to actually support an LTS release model > upstream.* > > We act like people have been saying "no, you are not allowed to > maintain branches for longer than the stable team says is OK," or > "no, we'll never provide an LTS release," but that's not how our > community works. The policies are set by the contributors. If there > are no contributors for an LTS release, there will be no LTS release. > If there *are* contributors, then we'll find a way to make some > sort of LTS model work within the other constraints we have. > > It seems now that we have people saying they would do some amount > of maintenance work (probably less than we try to do for stable > branches under our current model), if they could. The first change, > what has been proposed, is to give them a place to do the work. > Then we'll see if anyone actually does it, and if so we can plan > further improvements. > >> Then we can ask the operators if they would prefer that we stop EOL'ing >> things out from under them. We can make it a community goal to have a >> "feature" that is "you can upgrade from the last one" and have "the last >> one" be something older than 6 months, maybe even older than 1 year. >> >> [1] https://www.openstack.org/assets/survey/April2017SurveyReport.pdf >> > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] Dealing with ITAR in OpenStack private clouds

use case) Thanks, Dims On Tue, Mar 21, 2017 at 8:59 PM, Davanum Srinivas <dava...@gmail.com> wrote: > Jonathan, > > The folks from Boston University have done some work around this idea: > > https://github.com/openstack/mixmatch/blob/master/doc/source/architecture.rst > >

Re: [Openstack-operators] Dealing with ITAR in OpenStack private clouds

> ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- Davanum Srinivas :: https://twitter.com/dims __

Re: [Openstack-operators] [oslo] RabbitMQ queue TTL issues moving to Liberty

and our ops guys have to deal with something that >>>> isn’t really an issue. They basically delete the queue. >>>> >>>> A bad scenario is when you make a change to your cloud that means all >>>> your 1000 neutron agents are restarted, this cause

Re: [Openstack-operators] [nova docker]need help for nova-docker

under container" Can anybody help me ? > > > > > ___ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > -- Davanum Srinivas :: https://twi

Re: [Openstack-operators] [magnum] Trying to use Magnum with Kilo

-bin/mailman/listinfo/openstack-operators -- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] FYI: Rabbit Heartbeat Patch Landed

Kris Lindgren Senior Linux Systems Engineer GoDaddy, LLC. On 5/1/15, 9:41 AM, Davanum Srinivas dava...@gmail.com wrote: may i request folks post the versions of rabbitmq and pip versions of kombu and amqp libraries? thanks, dims On Fri, May 1, 2015 at 11:29 AM, Mike Dorman mdor

Re: [Openstack-operators] FYI: Rabbit Heartbeat Patch Landed

of people that would be keen to get a latest version of oslo.messaging working against a juno environment. What is the best way to make that happen though? Cheers, Sam [1] https://github.com/NeCTAR-RC/oslo.messaging/commits/nectar/1.8.0 On 20 Mar 2015, at 8:59 am, Davanum Srinivas dava

[Openstack-operators] Fwd: [openstack-dev] [release] oslo.messaging 1.8.1

?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman

Re: [Openstack-operators] FYI: Rabbit Heartbeat Patch Landed

-operators -- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] FYI: Rabbit Heartbeat Patch Landed

Apologies. i was waiting for one more changeset to merge. Please try oslo.messaging master branch https://github.com/openstack/oslo.messaging/commits/master/ https://github.com/openstack/oslo.messaging/commits/master/ (you need at least till Change-Id: I4b729ed1a6ddad2a0e48102852b2ce7d66423eaa

Re: [Openstack-operators] [openstack-dev][all][qa][gabbi][rally][tempest] Extend rally verfiy to unify work with Gabbi, Tempest and all in-tree functional tests

mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http

Re: [Openstack-operators] Operators Summit: RabbitMQ

-- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] EXT4 as ephemeral disk

___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators -- Davanum Srinivas :: https://twitter.com/dims ___ OpenStack-operators mailing list OpenStack-operators