Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 8/28/15, 10:07 AM, "gord chung" wrote: > > >On 28/08/15 12:18 PM, Roman Dobosz wrote: >> So imagine we have new versions of the schema for the events, alarms or >> samples in ceilometer introduced in Mitaka release while you have all >> your ceilo services on Liberty release. To upgrade ceil

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 8/28/15, 11:39 AM, "gord chung" wrote: >i should start by saying i re-read my subject line and it arguably comes >off aggressive -- i should probably have dropped 'explain' :) > >On 28/08/15 01:47 PM, Alec Hothan (ahothan) wrote: >> >&g

Re: [openstack-dev] [oslo][versionedobjects][ceilometer] explain the benefits of ceilometer+versionedobjects

On 9/1/15, 11:31 AM, "gord chung" wrote: > > >On 28/08/2015 5:18 PM, Alec Hothan (ahothan) wrote: >> >> >> >> >> On 8/28/15, 11:39 AM, "gord chung" wrote: >> >>> i should start by saying i re-read my subject line

Re: [openstack-dev] [app-catalog] PTL Candidacy

+1 Great job leading the app catalog and looking forward for all these new features! On 9/11/15, 12:23 PM, "Christopher Aedo" wrote: >It's time for the Community App Catalog to go through an official >election cycle, and I'm putting my name in for PTL. I've been filling >that role provisio

Re: [openstack-dev] Scheduler proposal

Still the point from Chris is valid. I guess the main reason openstack is going with multiple concurrent schedulers is to scale out by distributing the load between multiple instances of schedulers because 1 instance is too slow. This discussion is about coordinating the many instances of schedu

Re: [openstack-dev] Scheduler proposal

o the heavy lifting). > >Chris Friesen wrote: >> On 10/09/2015 12:25 PM, Alec Hothan (ahothan) wrote: >>> >>> Still the point from Chris is valid. I guess the main reason openstack is >>> going with multiple concurrent schedulers is to scale out by >>> di

Re: [openstack-dev] Scheduler proposal

On 10/9/15, 6:29 PM, "Clint Byrum" wrote: >Excerpts from Chris Friesen's message of 2015-10-09 17:33:38 -0700: >> On 10/09/2015 03:36 PM, Ian Wells wrote: >> > On 9 October 2015 at 12:50, Chris Friesen > > > wrote: >> > >> > Has anybody looked at why 1

Re: [openstack-dev] Scheduler proposal

On 10/10/15, 11:35 PM, "Clint Byrum" wrote: >Excerpts from Alec Hothan (ahothan)'s message of 2015-10-09 21:19:14 -0700: >> >> On 10/9/15, 6:29 PM, "Clint Byrum" wrote: >> >> >Excerpts from Chris Friesen's message of 2015-1

Re: [openstack-dev] Scheduler proposal

On 10/12/15, 11:45 AM, "Joshua Harlow" wrote: >Alec Hothan (ahothan) wrote: >> >> >> >> >> On 10/10/15, 11:35 PM, "Clint Byrum" wrote: >> >>> Excerpts from Alec Hothan (ahothan)'s message of 2015-10-09 21:19:14 -0700:

Re: [openstack-dev] Scheduler proposal

On 10/12/15, 12:05 PM, "Monty Taylor" wrote: >On 10/12/2015 02:45 PM, Joshua Harlow wrote: >> Alec Hothan (ahothan) wrote: >>> >>> >>> >>> > >I want to do 100k hypervisors. No, that's not hyperbole. > >Also, I do not

Re: [openstack-dev] Scheduler proposal

On 10/15/15, 11:11 PM, "Clint Byrum" wrote: >Excerpts from Ed Leafe's message of 2015-10-15 11:56:24 -0700: >> Wow, I seem to have unleashed a bunch of pent-up frustration in the >> community! It's great to see everyone coming forward with their ideas and >> insights for improving the way

Re: [openstack-dev] [kloudbuster] authorization failed problem

Hi Akshay The URL you are using is a private address (http://192.168.138.51:5000/v2.0) and is likely the reason it does not work. If you run the kloudbuster App in the cloud, this app needs to have access to the cloud under test. So even if you can access 192.168.138.51 from your local browser (

Re: [openstack-dev] [kloudbuster] authorization failed problem

un kloudbuster, I am getting this error: "EndpointNotFound: publicURL endpoint for volumev2 service not found" Is it possible to run the scale test (creation of VMs, router, network) without having a cinder service? Any option that can be used so that kloudbuster can run without cinder.

Re: [openstack-dev] [kloudbuster] authorization failed problem

be up running. Thanks very much! Regards, Yichen From: Akshay Kumar Sanghai [mailto:akshaykumarsang...@gmail.com<mailto:akshaykumarsang...@gmail.com>] Sent: Wednesday, March 30, 2016 7:31 AM To: Alec Hothan (ahothan) mailto:ahot...@cisco.com>> Cc: OpenStack List mailto:openstack

Re: [openstack-dev] [kloudbuster] authorization failed problem

kshay On Wed, Apr 6, 2016 at 1:44 PM, Yichen Wang (yicwang) mailto:yicw...@cisco.com>> wrote: Hi, Akshay, Just curious, how do you find KloudBuster so far? Does it do its job and fit your needs? ☺ Thanks very much! Regards, Yichen From: Alec Hothan (ahothan) Sent: Tuesday, April 5, 2016 9:54

[openstack-dev] [diskimage-builder] disk-image-create from virtualenv not working

I wonder if anybody else ran into the same issue as it looks like PyYAML is required on the native python in order for disk-image-crate to succeed. Installing PyYAML in a virtual environment and running disk-iage-create from that venv won't work as one of the script fails to import yaml: dib-run

Re: [openstack-dev] [diskimage-builder] disk-image-create from virtualenv not working

02 19:58 GMT+02:00 Alec Hothan (ahothan) : >> >> I wonder if anybody else ran into the same issue as it looks like PyYAML >> is required on the native python in order for disk-image-crate to >>succeed. >> Installing PyYAML in a virtual environment and running disk-iage-cre

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

inline... On 7/8/15, 8:23 AM, "Bogdan Dobrelya" wrote: >>> On 6/12/15, 3:55 PM, "Clint Byrum" wrote: >>> >>> > >>> >> >>> > >>> >I think you missed "it is not tested in the gate" as a root cause for >>> >some of the ambiguity. Anecdotes and bug reports are super important >>>for >>> >knowing

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

On 7/20/15, 5:24 AM, "Bogdan Dobrelya" wrote: >inline > >On 14.07.2015 18:59, Alec Hothan (ahothan) wrote: >> inline... >> >> >> On 7/8/15, 8:23 AM, "Bogdan Dobrelya" wrote: >> >> >> I believe Oleksii is already worki

[openstack-dev] [oslo.messaging][zeromq] Next step

Looking at what is the next step following the design summit meeting on 0MQ as the etherpad does not provide too much information. Few questions: - would it be possible to have the slides presented (showing the proposed changes in the 0MQ driver design) to be available somewhere? - is there a parti

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

better option than rabbitMQ at production scale using measurable evidence. Thanks Alec Thanks, Oleksii 1 - http://zeromq.org/area:faq#toc7 5/26/15 18:57, Davanum Srinivas пишет: Alec, Here are the slides: http://www.slideshare.net/davanum/oslomessaging-new-0mq-driver-proposal All

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

On 6/1/15, 5:03 PM, "Davanum Srinivas" wrote: >fyi, the spec for zeromq driver in oslo.messaging is here: >https://review.openstack.org/#/c/187338/1/specs/liberty/zmq-patterns-usage >.rst,unified > >-- dims I was about to provide some email comments on the above review off gerrit, but figured

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

On 6/12/15, 3:55 PM, "Clint Byrum" wrote: > >> > >I think you missed "it is not tested in the gate" as a root cause for >some of the ambiguity. Anecdotes and bug reports are super important for >knowing where to invest next, but a test suite would at least establish a >base line and prevent t

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

;On 06/12/2015 09:41 PM, Alec Hothan (ahothan) wrote: >> One long standing issue I can see is the fact that the oslo messaging >>API >> documentation is sorely lacking details on critical areas such as API >> behavior during fault conditions, load conditions and scale condit

Re: [openstack-dev] [oslo.messaging][zeromq] pub/sub support for the revised zeromq driver

On 6/1/15, 5:03 PM, "Davanum Srinivas" mailto:dava...@gmail.com>> wrote: fyi, the spec for zeromq driver in oslo.messaging is here: https://review.openstack.org/#/c/187338/1/specs/liberty/zmq-patterns-usage .rst,unified The above spec suggests using the zmq pub/sub/xpub/xsub proxy pattern for

Re: [openstack-dev] [oslo.messaging][zeromq] Next step

Do we have a good understanding of what is expected of zmq wrt rabbitMQ? Like in what part of the bell curve or use cases would you see it? Or indirectly, where do we see RabbitMQ lacking today that maybe ZMQ could handle better? I have tried to find any information on very large scale deployment

Re: [openstack-dev] [devstack]Specific Juno version

You can specify specific tags for each component in your local.conf file, e.g.: NOVA_BRANCH=2014.2 CINDER_BRANCH=2014.2 GLANCE_BRANCH=2014.2 HORIZON_BRANCH=2014.2 KEYSTONE_BRANCH=2014.2 KEYSTONECLIENT_BRANCH=2014.2 NOVACLIENT_BRANCH=2014.2 SWIFT_BRANCH=2014.2 HEAT_BRANCH=2014.2 HTH Alec Fro

Re: [openstack-dev] [kloudbuster] test LBAAS at scale

Hi Akshay, I suppose you're talking about LBAAS v2? Adding support for lbaas in kloudbuster will require some amount of work which can be kept to a minimum if done properly, this addition would be a pretty good way to test lbaas at scale. The tricky part is to modify the staging code without br

Re: [openstack-dev] [all][massively distributed][architecture]Coordination between actions/WGs

This topic of oslo messaging issues has been going on for a long time and the main issue is not the transport itself (each transport has its own limitations) but the code using oslo messaging (e.g. pieces of almost every openstack service). It is relatively easy to write code using oslo messagi

Re: [openstack-dev] [release][requirements] disable constraint bot updates for our own libraries

From: Jeremy Stanley Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, January 17, 2017 at 10:15 AM To: "OpenStack Development Mailing List (not for usage questions)" Subject: Re: [openstack-dev] [release][requirements] disable constraint bot updates fo