Re: [openstack-dev] [neutron] HA of dhcp agents?

Thanks for the pointer! I like how the first google hit for this is: Add details on dhcp_agents_per_network option for DHCP agent HA https://bugs.launchpad.net/openstack-manuals/+bug/1370934 :) Seems reasonable to set dhcp_agents_per_network > 1. What happens when a DHCP agent dies? Does the s

[openstack-dev] [horizon] integration_tests : httplib timed out when running from eclipse

Running integration_test from command line is ok : (.venv)whg@whg-HP:/opt/stack/horizon$ nosetests openstack_dashboard.test.integration_tests.tests.test_user_settings openstack_dashboard.test.integration_tests.tests.test_user_settings.TestUserSettings.test_user_settings_change ... ok --

Re: [openstack-dev] [All] Maintenance mode in OpenStack during patching/upgrades

> -Original Message- > From: Christopher Aedo [mailto:d...@aedo.net] > Sent: 21 October 2014 04:45 > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [All] Maintenance mode in OpenStack during > patching/upgrades > ... > > Also, I would like

Re: [openstack-dev] [cinder][nova] Are disk-intensive operations managed ... or not?

On 10/19/2014 09:33 AM, Avishay Traeger wrote: Hi Preston, Replies to some of your cinder-related questions: 1. Creating a snapshot isn't usually an I/O intensive operation. Are you seeing I/O spike or CPU? If you're seeing CPU load, I've seen the CPU usage of cinder-api spike sometimes - not s

Re: [openstack-dev] [api] Request Validation - Stoplight

Hi Chris, 2014-10-21 13:41 GMT+09:00 Christopher Yeoh : > > On Tue, Oct 21, 2014 at 12:15 PM, Kenichi Oomichi > wrote: >> >> Hi Amit, >> >> Thanks for picking this topic up, >> >> Honestly I don't have a strong opinion about validation libraries. >> Each project implements based on different web

Re: [openstack-dev] [api] Request Validation - Stoplight

On Tue, Oct 21, 2014 at 12:15 PM, Kenichi Oomichi wrote: > Hi Amit, > > Thanks for picking this topic up, > > Honestly I don't have a strong opinion about validation libraries. > Each project implements based on different web frameworks and > the options of validation libraries would be limited f

Re: [openstack-dev] [neutron] HA of dhcp agents?

See dhcp_agents_per_network in neutron.conf. https://bugs.launchpad.net/neutron/+bug/1174132 2014-10-21 6:47 GMT+08:00 Noel Burton-Krahn : > I've been working on failover for dhcp and L3 agents. I see that in [1], > multiple dhcp agents can host the same network. However, it looks like I > hav

Re: [openstack-dev] [TripleO] Removing nova-bm support within os-cloud-config

On Mon, Oct 20, 2014 at 8:00 PM, Steve Kowalik wrote: > With the move to removing nova-baremetal, I'm concerned that portions > of os-cloud-config will break once python-novaclient has released with > the bits of the nova-baremetal gone -- import errors, and such like. > Nova won't be removing n

Re: [openstack-dev] [Neutron] Why doesn't ml2-ovs work when it's "host" != the dhcp agent's host?

The current suggested way for DHCP agent fault tolerance is multiple agents per network. Is there a reason you don't want to use that option? On Oct 20, 2014 5:13 PM, "Noel Burton-Krahn" wrote: > Thanks, Robert. > > So, ML2 needs the host attribute to match to bind the port. My other > requireme

[openstack-dev] [nova][log] output of the x-openstack-request-id

when checking the nova/api.log , I found the following entry as below 2014-10-20 11:26:11.387 3549 INFO nova.osapi_compute.wsgi.server [req-d7cc3757-f1e3-4af9-8700-a6f7fa096a6b None] 10.104.0.138 "GET /v2/896bfb02c3f945d8a397c79f0741557a/os-floating-ips HTTP/1.1" status: 200 len: 192 time: 0.11191

Re: [openstack-dev] [api] Request Validation - Stoplight

- Original Message - > However I don't think we should be mandating specific libraries, but we > can make recommendations (good or bad) based on actual experience. This > will be especially useful to new projects starting up to benefit from > the pain other projects have experienced. +1

[openstack-dev] [TripleO] Removing nova-bm support within os-cloud-config

With the move to removing nova-baremetal, I'm concerned that portions of os-cloud-config will break once python-novaclient has released with the bits of the nova-baremetal gone -- import errors, and such like. I'm also concerned about backward compatibility -- in that we can't really remove the fu

Re: [openstack-dev] [All] Maintenance mode in OpenStack during patching/upgrades

I'm glad to see there's more than one interested person here too :) Regarding the Xen-specific host maintenance mode, if it gets dropped I would not complain since it's useful only to those running Xen at the moment. The issues around when it works and doesn't work are my bigger concern - as simi

Re: [openstack-dev] [api] Request Validation - Stoplight

Hi Amit, Thanks for picking this topic up, Honestly I don't have a strong opinion about validation libraries. Each project implements based on different web frameworks and the options of validation libraries would be limited from its web framework. For example, Nova implements its own wsgi framew

Re: [openstack-dev] [api] API recommendation

On 10/15/2014 11:49 AM, Kevin L. Mitchell wrote: Now that we have an API working group forming, I'd like to kick off some discussion over one point I'd really like to see our APIs using (and I'll probably drop it in to the repo once that gets fully set up): the difference between synchronous and

Re: [openstack-dev] [Ironic] disambiguating the term "discovery"

On 10/20/2014 07:11 PM, Devananda van der Veen wrote: > Hi all, > > I was reminded in the Ironic meeting today that the words "hardware > discovery" are overloaded and used in different ways by different > people. Since this is something we are going to talk about at the > summit (again), I'd like

Re: [openstack-dev] [rally][users]

Hi Boris, Does rally provide any synchronization mechanism to synchronize between multiple scenario, when running in parallel? Rally spawns multiple processes, with each process running the scenario. We need a way to synchronize between these to start a perf test operation at the same time. r

[openstack-dev] [Ironic] disambiguating the term "discovery"

Hi all, I was reminded in the Ironic meeting today that the words "hardware discovery" are overloaded and used in different ways by different people. Since this is something we are going to talk about at the summit (again), I'd like to start the discussion by building consensus in the language tha

Re: [openstack-dev] [api] Request Validation - Stoplight

On Mon, 20 Oct 2014 10:38:58 -0400 Jay Pipes wrote: > > > For stackers who are interested in different validation frameworks > > to implement validation, I recommend checking out Stoplight. > > Just my two cents on this particular topic, I think it's more > important to standardize ways in which

[openstack-dev] [Ironic] [Triple-O] Openstack Onboarding

I made a similar comment to the Triple-O design summmit etherpad in hopes others have a similar interest in Kilo but I wanted to share evangelize my thoughts with the community for discussion: For better or for worse, one thing I've heard over and over is how Openstack community/TC approves/prefer

Re: [openstack-dev] [nova] APIImpact flag for nova specs

On Mon, 20 Oct 2014 14:44:15 -0500 Anne Gentle wrote: > > > > > I think adding APIImpact will be useful. > > I also want to point to the addition of Compute v2 (haven't yet > proposed a spec for v2.1) to the nova-specs repo here: > > https://review.openstack.org/#/c/129329/ > > The goal is to m

[openstack-dev] [neutron] HA of dhcp agents?

I've been working on failover for dhcp and L3 agents. I see that in [1], multiple dhcp agents can host the same network. However, it looks like I have to manually assign networks to multiple dhcp agents, which won't work. Shouldn't multiple dhcp agents automatically fail over? [1] http://docs.o

Re: [openstack-dev] [Nova] Cells conversation starter

Hi Andrew, great that you have started the “cells” discussion. Looking forward to see cells as default setup in Kilo. The feature gap is really painful for current cells users. We are looking into these features for some time and the main concern is really where these concepts should live.

Re: [openstack-dev] [oslo] request_id deprecation strategy question

On Mon, Oct 20, 2014 at 11:12 AM, gordon chung wrote: > > The issue I'm highlighting is that those projects using the code now have > > to update their api-paste.ini files to import from the new location, > > presumably while giving some warning to operators about the impending > > removal of the

Re: [openstack-dev] [all] Tentative schedule for Kilo Design Summit in Paris

Chance we can move the congress session from Monday 14:30-16:00 to co-locate Tuesday with GBP? either before or after... ~ sean On Oct 7, 2014, at 1:25 AM, Thierry Carrez wrote: > Sylvain Bauza wrote: >> I only see 3 slots for discussing about other projects. Do you know if >> it would be poss

[openstack-dev] [NFV] NFV BoF session for OpenStack Summit Paris

Hi all, I took an action item in one of the meetings to try and find a date/time/space to do another NFV BoF session for Paris to take advantage of the fact that many of us will be in attendance for a face to face session. To try and avoid clashing with the general and design summit sessions I

Re: [openstack-dev] [OpenStack] [Barbican] [Cinder] Cinder and Barbican

> is Cinder capable today to use Barbican for encryption? Yes, Cinder has a KeyManager abstraction, and one of the implementations is Barbican. Checkout cinder.keymgr.barbican.py. We have successfully used Barbican within Cinder. I think the python-barbicanclient has recently changed. This change

Re: [openstack-dev] [Neutron] Why doesn't ml2-ovs work when it's "host" != the dhcp agent's host?

Thanks, Robert. So, ML2 needs the host attribute to match to bind the port. My other requirement is that the dhcp agent must be able to migrate to a new host on failover. The issue there is that if the dhcp service starts on a new host with a new host name, then it will not take over the network

Re: [openstack-dev] [Ironic][Ceilometer] Proposed Change to Sensor meter naming in Ceilometer

On Mon, 20 Oct 2014, Jim Mankovich wrote: I'll propose something via a spec to ceilometer for sensor naming which will include the ability to support the new health sensor information. Excellent. Do you happen to know what some of the use cases are for the current reporting of sensor informa

Re: [openstack-dev] [Keystone] external AuthN Identity Backend

On 10/16/2014 02:58 PM, David Chadwick wrote: Dave when federation is used, the user's group is stored in a mapping rule. So we do have a mechanism for storing group memberships without using LDAP or creating an entry for the user in the SQL backend. (The only time this is kinda not true is if w

Re: [openstack-dev] [Keystone] external AuthN Identity Backend

On 10/16/2014 03:18 PM, Dave Walker wrote: On 16 October 2014 20:07, David Stanek wrote: I may be missing something, but can you use the external auth method with the LDAP backend? No, as the purpose of the LDAP backend is to validate user/pass combination are valid. With the external auth

Re: [openstack-dev] [Neutron] Neutron documentation to update about new vendor plugin, but without code in repository?

On Mon, Oct 20, 2014 at 2:42 PM, Vadivel Poonathan < vadivel.openst...@gmail.com> wrote: > Hi, > > > > > > > > * On Fri, Oct 10, 2014 at 7:36 PM, Kevin Benton > wrote:>> I think you will probably have to > wait until after the summit so we can> see the direction that will be > tak

Re: [openstack-dev] [nova] APIImpact flag for nova specs

On Wed, Oct 15, 2014 at 5:52 AM, Christopher Yeoh wrote: > On Wed, Oct 15, 2014 at 8:58 PM, Sylvain Bauza wrote: > >> >> Le 15/10/2014 11:56, Christopher Yeoh a écrit : >> >> >> On Wed, Oct 15, 2014 at 7:31 PM, Alex Xu wrote: >> >>> On 2014年10月15日 14:20, Christopher Yeoh wrote: >>> Hi, >>

[openstack-dev] [neutron] [oslo.db] model_query() future and neutron specifics

As I’ve established oslo.db blueprints which will roll out new SQLAlchemy connectivity patterns for consuming applications within both API [1] and tests [2], one of the next big areas I’m to focus on is that of querying. If one looks at how SQLAlchemy ORM queries are composed across Openstack,

Re: [openstack-dev] [Neutron] Neutron documentation to update about new vendor plugin, but without code in repository?

Hi, * On Fri, Oct 10, 2014 at 7:36 PM, Kevin Benton > wrote:>> I think you will probably have to wait until after the summit so we can> see the direction that will be taken with the rest of the in-tree> drivers/plugins. It seems like we are moving towards removing all of

Re: [openstack-dev] [Ironic][Ceilometer] Proposed Change to Sensor meter naming in Ceilometer

Chris, Use case point well taken :-) I'll propose something via a spec to ceilometer for sensor naming which will include the ability to support the new health sensor information. From a use case perspective, I want to provide the health of every platform so an administrator can be notified

Re: [openstack-dev] FreeBSD host support

On Sat, Oct 18, 2014 at 10:04 AM, Roman Bogorodskiy < rbogorods...@mirantis.com> wrote: > Hi, > > In discussion of this spec proposal: > https://review.openstack.org/#/c/127827/ it was suggested by Joe Gordon > to start a discussion on the mailing list. > > So I'll share my thoughts and a long ter

Re: [openstack-dev] [Nova] Cells conversation starter

On 2014-10-20 2:00 PM, Andrew Laski wrote: One of the big goals for the Kilo cycle by users and developers of the cells functionality within Nova is to get it to a point where it can be considered a first class citizen of Nova. [...] Shortcomings: Flavor syncing This needs to be address

Re: [openstack-dev] [nova] Pulling nova/virt/hardware.py into nova/objects/

> OK, so in reviewing Dan B's patch series that refactors the virt > driver's get_available_resource() method [1], I am stuck between two > concerns. I like (love even) much of the refactoring work involved in > Dan's patches. They replace a whole bunch of our nested dicts that are > used in the re

Re: [openstack-dev] [oslo] request_id deprecation strategy question

> The issue I'm highlighting is that those projects using the code now have > to update their api-paste.ini files to import from the new location, > presumably while giving some warning to operators about the impending > removal of the old code. This was the issue i ran into when trying to switch p

Re: [openstack-dev] [Neutron] Why doesn't ml2-ovs work when it's "host" != the dhcp agent's host?

Hi Noel, The ML2 plugin uses the binding:host_id attribute of port to control port binding. For compute ports, nova sets binding:host_id when creating/updating the neutron port, and ML2's openvswitch mechanism driver will look in agents_db to make sure the openvswitch L2 agent is running on t

[openstack-dev] [Nova] Cells conversation starter

One of the big goals for the Kilo cycle by users and developers of the cells functionality within Nova is to get it to a point where it can be considered a first class citizen of Nova. Ultimately I think this comes down to getting it tested by default in Nova jobs, and making it easy for devel

[openstack-dev] [Infra] Meeting Tuesday October 21st at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is hosting our weekly meeting on Tuesday October 21st, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting (anyone is welcome to to add agenda items) Everyone interested

[openstack-dev] [nova] Pulling nova/virt/hardware.py into nova/objects/

Hi Dan, Dan, Nikola, all Nova devs, OK, so in reviewing Dan B's patch series that refactors the virt driver's get_available_resource() method [1], I am stuck between two concerns. I like (love even) much of the refactoring work involved in Dan's patches. They replace a whole bunch of our neste

[openstack-dev] [Neutron] Why doesn't ml2-ovs work when it's "host" != the dhcp agent's host?

I'm running OpenStack Icehouse with Neutron ML2/OVS. I've configured the ml2-ovs-plugin on all nodes with host = the IP of the host itself. However, my dhcp-agent may float from host to host for failover, so I configured it with host="floating". That doesn't work. In this case, the ml2-ovs-plugi

Re: [openstack-dev] [novaclient] E12* rules

On Fri, Oct 17, 2014 at 6:40 AM, Andrey Kurilin wrote: > Hi everyone! > > I'm working on enabling E12* PEP8 rules in novaclient(status of my work > listed below). Imo, PEP8 rules should be ignored only in extreme cases/for > important reasons and we should decrease a number of ignored rules. This

Re: [openstack-dev] [all] add cyclomatic complexity check to pep8 target

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10/16/2014 11:09 PM, Joe Gordon wrote: > First step in fixing this, put a cap on it: > https://review.openstack.org/129125 To get the maximums down to more reasonable levels, I have two patches that bring the libvirt driver _get_guest_config() fro

[openstack-dev] [oslo] proposed summit session topics

After today’s meeting, we have filled our seven session slots. Here’s the proposed list, in no particular order. If you think something else needs to be on the list, speak up today because I’ll be plugging all of this into the scheduling tool in the next day or so. https://etherpad.openstack.or

Re: [openstack-dev] [Ironic][Ceilometer] Proposed Change to Sensor meter naming in Ceilometer

On Mon, 20 Oct 2014, Jim Mankovich wrote: On 10/20/2014 6:53 AM, Chris Dent wrote: On Fri, 17 Oct 2014, Jim Mankovich wrote: See answers inline. I don't have any concrete answers as to how to deal with some of questions you brought up, but I do have some more detail that may be useful to furthe

[openstack-dev] [mistral] Team meeting minutes - 10/20/2014

Thanks for joining us today at #openstack-meeting. Meeting minutes: http://eavesdrop.openstack.org/meetings/mistral/2014/mistral.2014-10-20-16.02.html Full log: http://eavesdrop.openstack.org/meetings/mistral/

[openstack-dev] [Ironic] Summit scheduling

As hopefully everyone is aware by now, the format of this summit will be somewhat different from previous summits. Monday will be dedicated to an Ops Summit, and Tuesday is dedicated to cross-project discussions. Wednesday and Thursday are project-specific design tracks, and on Friday projects have

Re: [openstack-dev] [oslo] request_id deprecation strategy question

Phew :) Thanks Steve. From: Steven Hardy [sha...@redhat.com] Sent: Monday, October 20, 2014 12:52 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [oslo] request_id deprecation strategy question On Mon, Oct

Re: [openstack-dev] [oslo] request_id deprecation strategy question

On Mon, Oct 20, 2014 at 02:17:54PM +, Sandy Walsh wrote: > Does this mean we're losing request-id's? No, it just means the implementation has moved from oslo-incubator[1] to oslo.middleware[2]. The issue I'm highlighting is that those projects using the code now have to update their api-paste

Re: [openstack-dev] [Ironic][Ceilometer] Proposed Change to Sensor meter naming in Ceilometer

On 10/20/2014 6:53 AM, Chris Dent wrote: On Fri, 17 Oct 2014, Jim Mankovich wrote: See answers inline. I don't have any concrete answers as to how to deal with some of questions you brought up, but I do have some more detail that may be useful to further the discussion. That seems like progr

Re: [openstack-dev] [api] Request Validation - Stoplight

On 20 October 2014 15:38, Jay Pipes wrote: > On 10/20/2014 10:26 AM, Amit Gandhi wrote: > >> Thanks for the clarification Sam. >> >> Its good to know where the mission of the API working group starts and >> stops. During the meetup discussions, my understanding was that the >> working group woul

Re: [openstack-dev] [api] Request Validation - Stoplight

On 10/20/14, 10:38 AM, "Jay Pipes" wrote: >On 10/20/2014 10:26 AM, Amit Gandhi wrote: >> Thanks for the clarification Sam. >> >> Its good to know where the mission of the API working group starts and >> stops. During the meetup discussions, my understanding was that the >> working group would

Re: [openstack-dev] [api] Request Validation - Stoplight

On 10/20/2014 10:26 AM, Amit Gandhi wrote: Thanks for the clarification Sam. Its good to know where the mission of the API working group starts and stops. During the meetup discussions, my understanding was that the working group would recommend the technologies to use while building apis (e.g.

Re: [openstack-dev] Horizon and Keystone: API Versions and Discovery

On Mon, Oct 20, 2014 at 7:04 AM, Jamie Lennox wrote: > > > - Original Message - > > From: "Dolph Mathews" > > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > > Sent: Tuesday, October 7, 2014 6:56:15 PM > > Subject: Re: [openstac

Re: [openstack-dev] [TripleO] Summit scheduling - using our time together wisely.

I guess my only concern would be whether either of those things are contentious (both sound like must-do's at some point) and whether there is anything on either topic that requires f2f conversation to resolve. There's a spec out for Cinder HA already (https://review.openstack.org/#/c/101237/) that

Re: [openstack-dev] [Fuel] Pluggable framework in Fuel: first prototype ready

Hi guys, *Romans' questions:* >> I feel like we should not require user to unpack the plugin before installing it. >> Moreover, we may chose to distribute plugins in our own format, which we >> may potentially change later. E.g. "lbaas-v2.0.fp". I like the idea of putting plugin installation fun

Re: [openstack-dev] [api] Request Validation - Stoplight

Thanks for the clarification Sam. Its good to know where the mission of the API working group starts and stops. During the meetup discussions, my understanding was that the working group would recommend the technologies to use while building apis (e.g. Pecan, validation frameworks, etc) and were

Re: [openstack-dev] [oslo] request_id deprecation strategy question

Does this mean we're losing request-id's? Will they still appear in the Context objects? And there was the effort to keep consistent request-id's in cross-service requests, will this deprecation affect that? -S From: Steven Hardy [sha...@redhat.com] Sen

Re: [openstack-dev] [Ceilometer] Ceilometer-Alarm-Not Working

Hi, Thanks for your response Chris, Ceilometer-api Pls let me know if /etc/ceilometer/ceilometer.conf file is correct: [DEFAULT] # # Options defined in ceilometer.middleware # # Exchanges name to listen for notifications (multi valued) http_control_exchanges=nova http_control_exchanges=glance h

[openstack-dev] [oslo] request_id deprecation strategy question

Hi all, I have a question re the deprecation strategy for the request_id module, which was identified as a candidate for removal in Doug's recent message[1], as it's moved from oslo-incubator to oslo.middleware. The problem I see is that oslo-incubator deprecated this in Juno, but (AFAICS) all pr

Re: [openstack-dev] [Keystone] Question regarding Service Catalog and Identity entries...

On 10/20/2014 08:12 AM, Jamie Lennox wrote: > - Original Message - >> From: "Ben Meyer" >> To: openstack-dev@lists.openstack.org >> Cc: "Jamie Painter" >> Sent: Tuesday, October 7, 2014 4:31:16 PM >> Subject: [openstack-dev] [Keystone] Question regarding Service Catalog and >> Identity

Re: [openstack-dev] [api] Request Validation - Stoplight

+1 that's a great way to state it Sam. regards, mike - Original Message - > Hi Amit, > > Keeping in mind this viewpoint is nothing but my own personal view, my > recommendation would be to not mandate the use of a particular validation > framework, but to instead define what kind of val

Re: [openstack-dev] [Nova] Turbo hipster problems

Thanks. Yes, it is up and running again! From: Joshua Hesketh mailto:joshua.hesk...@rackspace.com>> Reply-To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Date: Monday, October 20, 2014 at 3:45 AM To: OpenStack List mailto:openstack-dev@lists.openstack.org>> Subject: Re: [openstack

[openstack-dev] [openstack][keystone] why is lxml only in test-requirements.txt?

I am trying to understand why lxml is only in test-requirements.txt... The default pipelines do contain xml_body and xml_body_v2 filters, which depends on lxml to function properly. Since lxml is not in requirements.txt, my packaging system won't include lxml in the deployment drop. At the same ti

Re: [openstack-dev] [Ironic][Ceilometer] Proposed Change to Sensor meter naming in Ceilometer

On Fri, 17 Oct 2014, Jim Mankovich wrote: See answers inline. I don't have any concrete answers as to how to deal with some of questions you brought up, but I do have some more detail that may be useful to further the discussion. That seems like progress to me. Personally, I would like to se

Re: [openstack-dev] [novaclient] E12* rules

Hi Andrey, Generally I'm opposed to such changes enabling random PEP8 checks, but in this particular case I kind of like the fact you fix the mess with indents in the code. python-novaclient code base is fairly small, CI nodes are not overloaded at this point of the release cycle, code looks bett

Re: [openstack-dev] [all][policy][keystone] Better Policy Model and Representing Capabilites

- Original Message - > From: "Nathan Kinder" > To: openstack-dev@lists.openstack.org > Sent: Tuesday, October 14, 2014 2:25:35 AM > Subject: Re: [openstack-dev] [all][policy][keystone] Better Policy Model and > Representing Capabilites > > > > On 10/13/2014 01:17 PM, Morgan Fainberg

Re: [openstack-dev] [Ceilometer] Ceilometer-Alarm-Not Working

On Mon, 20 Oct 2014, david jhon wrote: 2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service CommunicationError: Error communicating with http://193.168.4.121:8777 [Errno 111]$ 2014-10-20 16:33:07.854 30437 TRACE ceilometer.alarm.service How do I fix it? It looks like it may be that ei

Re: [openstack-dev] [Keystone] Question regarding Service Catalog and Identity entries...

- Original Message - > From: "Ben Meyer" > To: openstack-dev@lists.openstack.org > Cc: "Jamie Painter" > Sent: Tuesday, October 7, 2014 4:31:16 PM > Subject: [openstack-dev] [Keystone] Question regarding Service Catalog and > Identity entries... > > I am trying to use the Python Ke

Re: [openstack-dev] Horizon and Keystone: API Versions and Discovery

- Original Message - > From: "Dolph Mathews" > To: "OpenStack Development Mailing List (not for usage questions)" > > Sent: Tuesday, October 7, 2014 6:56:15 PM > Subject: Re: [openstack-dev] Horizon and Keystone: API Versions and Discovery > > > > On Tuesday, October 7, 2014, Adam Y

[openstack-dev] [Murano] Murano 2014.2 "Juno" is released

I'm glad to announce release of Murano 2014.2 code-named "Juno". This release includes 39 implemented blueprints and 140 bugfixes. Source tarballs along with detailed list of features and bugfixes can be found at the following link: https://launchpad.net/murano/+milestone/2014.2 Release notes:

Re: [openstack-dev] [Ceilometer] Ceilometer-Alarm-Not Working

Hi, Just opened /var/log/ceilometer/ceilometer-alarm-evaluator.log file and found following errors: 2014-10-20 16:32:15.263 23166 TRACE ceilometer.alarm.service 2014-10-20 16:33:07.854 30437 ERROR ceilometer.alarm.service [-] alarm evaluation cycle failed 2014-10-20 16:33:07.854 30437 TRACE ceilo

Re: [openstack-dev] [Fuel][Fuel-dev] Detailed Fuel release version definition

I'm agree with Dmitry. We can change version text. Use '2014.2-6.0-pre' in openstack.yaml and '6.0-pre' in PRODUCT_VERSION. Yep, we need to test it first. Also think about sorting on ui and other places where we can compare versions. On Mon, Oct 20, 2014 at 2:36 PM, Aleksandra Fedorova wrote: >

[openstack-dev] [Ceilometer] Ceilometer-Alarm-Not Working

Hi all, I am working with Ceilometer, Havana-All-in-one on Ubuntu 12.04. Initially, ceilometer configuration installed four ceilometer services: ceilometer-agent-central ceilometer-agent-compute ceilometer-api ceilometer-collector but later I came to know that there should be two other services

Re: [openstack-dev] [Neutron] BGPVPN implementation discussions

Hi, 1. From where the MPLS traffic will be initiated ? 2. How it will be mapped ? Regards, Keshava From: Damon Wang [mailto:damon.dev...@gmail.com] Sent: Friday, October 17, 2014 12:42 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev]

Re: [openstack-dev] [Fuel][Fuel-dev] Detailed Fuel release version definition

Hi, everyone, NOTE: I am moving this discussion into openstack-dev@ as we plan to deprecate fuel-...@lists.launchpad.net mailing list. Regarding the problem discussed: could you please add a bit more details about this versioning and how should it fit into our build process. Let's say we have 6

Re: [openstack-dev] [all][oslo] projects still using obsolete oslo modules

On 10/13/2014 03:20 PM, Doug Hellmann wrote: > I’ve put together a little script to generate a report of the projects using > modules that used to be in the oslo-incubator but that have moved to > libraries [1]. These modules have been deleted, and now only exist in the > stable/juno branch of t

Re: [openstack-dev] [horizon] Passing multiple values in table.Column in Horizon DataTable

On 19/10/14 12:52, Rajdeep Dua wrote: > Hi, > I need to pass two values in the link generated from the table.Column as > shown below. > > > class DatasourcesTablesTable(tables.DataTable): > data_source = tables.Column("column1", verbose_name=_("Column1")) > id = tables.Column("id", verbos

Re: [openstack-dev] [devstack] Mysql issue

Swapnil, Thanks for your response, i tried after running ./clean.sh and it worked on a new installation. I wonder if it was a local issue i was facing Thanks Rajdeep On Mon, Oct 20, 2014 at 2:25 PM, Swapnil Kulkarni wrote: > Rajdeep, I did couple of different devstack runs today and did not run

Re: [openstack-dev] [devstack] Mysql issue

Rajdeep, I did couple of different devstack runs today and did not run into any issue as you mentioned. Can you give more information about your installation? localrc contents would help Best Regards, Swapnil Kulkarni irc : coolsvap On Mon, Oct 20, 2014 at 1:03 PM, Rajdeep Dua wrote: > Facing t

Re: [openstack-dev] FreeBSD host support

On Sat, Oct 18, 2014 at 09:04:20PM +0400, Roman Bogorodskiy wrote: > Hi, > > In discussion of this spec proposal: > https://review.openstack.org/#/c/127827/ it was suggested by Joe Gordon > to start a discussion on the mailing list. > > So I'll share my thoughts and a long term plan on adding Fre

[openstack-dev] [Zaqar] Today's (October 20th) meeting time change

Greetings, Since we need to do a final discussion on the design session topics, I'm moving today's meeting to our second reserved time slot. That is, instead of being at 15 UTC, the meeting will be at 21 UTC. The main reason is that I won't be able to join our meeting at 15 UTC since I'll be trav

[openstack-dev] [devstack] Mysql issue

Facing this issue on trying to start a devstack installation Tried with an existing as well as new installation. 42201 CRITICAL keystone [-] DBConnectionError: (OperationalError) (2013, 'Lost connection to MySQL server during query') 'ALTER TABLE domain ADD CONSTRAINT ixu_domain_name UNIQUE (name

Re: [openstack-dev] [Fuel] Propose adding Igor K. to core reviewers for fuel-web projects

Igor, congratulations! Will be happy to see even more thorough reviews from you! On Tue, Oct 14, 2014 at 11:54 AM, Aleksey Kasatkin wrote: > > +1 > > Aleksey Kasatkin > > > Hi everyone! >> >> I would like to propose Igor Kalnitsky as a core reviewer on the >> Fuel-web team. Igor has been working

[openstack-dev] [Nova] Boot up 1,000 homogeneous VMs in 1 minite

Dear all, We proposed a new blueprint (at https://review.openstack.org/#/c/129116/) for booting up a large number of homogeneous VMs in a very short period of time. This feature may be targeted to the Kilo version. All requirements, suggestions and comments are welcome. Thank you! VMThunder Grou