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

O. > > Completely agree, I think we might just disagree on where to strike > the balance of purely technical priorities for the TC (as I > personally think the TC is somewhat incorrectly named). > -- > Jeremy Stanley >

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

ck-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 mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

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

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

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

> > --John John, So... Any concrete ideas on how to achieve that? Thanks, Dims > > > /me puts on asbestos pants > >> >> -- >> Mathieu >> >> ___ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >>

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

maintaining >> the branch. >> >> Doug >> >> ______ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe &g

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

ss that is a first step towards LTS eventually. Thanks, Dims On Wed, Nov 15, 2017 at 2:46 AM, Flavio Percoco 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

ist (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 mai

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

n the room disputed the assertion that what we're doing for > stable 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

[Openstack-operators] Fwd: [tc][all] Etcd as a base service for ALL OpenStack installations

Dear Ops, fyi. please chime in. Thanks, Dims -- Forwarded message -- From: Davanum Srinivas Date: Wed, May 24, 2017 at 6:11 AM Subject: [tc][all] Etcd as a base service for ALL OpenStack installations To: "OpenStack Development Mailing List (not for usage questions)&quo

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 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 > > > On Tue, Mar 21, 2

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 ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

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

’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 causes a couple of dead queues >>>> per agent to hang around. (port updates and security group updates) We get >>>> around 25 messages / second on these queues and so you can see after 10 >>>> minutes we have a ton of messages in these queues. >>>> >>>> 1000 x 2 x 25 x 600 = 30,000,000 messages in 10 minutes to be precise. >>>> >>>> Has anyone else been suffering with this before a raise a bug? >>>> >>>> Cheers, >>>> Sam >>>> >>>> >>>> ___ >>>> OpenStack-operators mailing list >>>> OpenStack-operators@lists.openstack.org >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>> >>> >> > > > ___ > 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] [nova docker]need help for nova-docker

nder 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://twitter.com/dims _

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

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

Re: [Openstack-operators] Nova VMware driver don't know to deal with VMWare vSphere 5.5 API bugs

>> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > > > -- > Rackspace Australia > &g

Re: [Openstack-operators] [Fuel][Oslo][RabbitMQ][Shovel] Deprecate mirrored queues from HA AMQP cluster scenario

ps://bugs.launchpad.net/fuel/+bug/1460762 > [3] https://groups.google.com/forum/#!topic/rabbitmq-users/iZWokxvhlaU > > -- > Best regards, > Bogdan Dobrelya, > Skype #bogdando_at_yahoo.com > Irc #bogdando > > _______ > OpenS

[Openstack-operators] [nova-docker] Request for Volunteers

Dear Ops folks, I just sent this on openstack-dev list, in case anyone is interested in helping with nova-docker. http://markmail.org/message/geijiljch4yxfcvq thanks, dims ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org htt

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

Lindgren wrote: >>> >>> We are running: >>> kombu 3.0.24 >>> amqp 1.4.6 >>> rabbitmq 3.4.0 >>> erlang R16B-03.10 >>> >>> >>> Kris Lindgren >>> Senior Linux Systems Engineer >>> GoDaddy, LLC. >>&

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

gt;> Juno here [1] and I’m hoping that it will be easy to integrate the heartbeat >>> code. >>> I’m sure there is lots 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

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

rg/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] FYI: Rabbit Heartbeat Patch Landed

gt; Sam > > [1] https://github.com/NeCTAR-RC/oslo.messaging/commits/nectar/1.8.0 > > > >> On 20 Mar 2015, at 8:59 am, Davanum Srinivas wrote: >> >> So, talking about experiments, here's one: >> https://review.openstack.org/#/c/165981/ >> >>

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

>> 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

t; >> -- Kevin >> >> > On Mar 19, 2015, at 1:13 PM, Jesse Keating wrote: >> > >> > On 3/19/15 10:15 AM, Davanum Srinivas wrote: >> >> Apologies. i was waiting for one more changeset to merge. >> >> >> >> Plea

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/ (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

every > project. > It is better to implement it in one place with plugin support. Adding new > project means implementing new plugin (in most case it will be just > functional test conf generation) > > 4) Reusing already existing code > > Most

Re: [Openstack-operators] Operators Summit: RabbitMQ

.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] EXT4 as ephemeral disk

_ >> OpenStack-operators mailing list >> OpenStack-operators@lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > > > _______ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org

[Openstack-operators] EXT4 as ephemeral disk

gress will work in your environment(s) and let us know thanks, dims -- 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