Re: [openstack-dev] [all] Ubuntu 14.04 support in Newton and on

Hi Jeremy, thank you for the pointers and the background on Newton! On 1/19/17, 7:12 AM, "Jeremy Stanley" <fu...@yuggoth.org> wrote: >On 2017-01-18 15:19:36 -0800 (-0800), Eric K wrote: >> Hi all, Is there any community-wide policy on how long we strive >> to mai

[openstack-dev] [all] Ubuntu 14.04 support in Newton and on

Hi all, Is there any community-wide policy on how long we strive to maintain compatibility with Ubuntu 14.04? For example by avoiding relying on MySQL 5.7 features. I¹ve had a hard time finding it on openstack.org and ML discussions. Thanks lots!

Re: [openstack-dev] [Congress][Fuel] Fuel plugin for installing Congress

Hi Serg, That¹s awesome news. Thanks all for the great work! Please do let us know how the Congress team can be helpful. On 1/16/17, 11:33 AM, "Serg Melikyan" wrote: >I'd like to introduce you fuel plugin for installing and configuring >Congress for Fuel [0]. > >This

[openstack-dev] [congress][oslo.config][keystone] NoSuchOptError: no such option project_domain_name in group [keystone_authtoken]

On a freshly stacked devstack (Jan 12), attempting to access `cfg.CONF.keystone_authtoken.project_domain_name` gave the error: NoSuchOptError: no such option project_domain_name in group [keystone_authtoken] I¹m a little confused because it¹s part of the [keystone_authtoken] config section

[openstack-dev] [Congress] no meeting on December 29, 2016

No congress team meeting on December 29, 2016. Regular meeting resumes on January 5, 2016. Happy holidays all! __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

[openstack-dev] [Congress] [infra] tempest job timeout appears shorter than configured

The congress {pipeline}-congress-dsvm-api-{node}{suffix} check/gate job seems to timeout around the 60 minute mark even though the project config appears to set it for 70min. Any hints as to why? Are there two different measures of time? Thanks so much!

[openstack-dev] [gate][congress] subunit.parser failures in pythonXX gate job

Hi all, Does anyone know what could be causing these subunit.parser failures in some pythonXX check jobs (they do not show up on my local setup). I vaguely remember seeing them before, but can't remember what they were. And haven't been able to find relevant info online or in lists. Thanks so

[openstack-dev] [Congress] relevant horizontal efforts at PTG

Hi all! aimeeu asked during team meeting about relevant sessions on Monday and Tuesday. I don't have anything official. I think it's more a matter of you and your org's interest in contributing to those horizontal efforts.  If you're looking to contribute to a horizontal project, horizon, the

[openstack-dev] [Congress] ekcs away

Hi all! I have personal travels planned 11/8 - 11/25. I expect to have intermittent access and keep up with reviews and ML, but will likely miss the IRC meetings. thinrichs, masahito, and ramineni have kindly agreed to organize the IRC meetings (UTC): 11/10: thinrichs11/17: masahito11/24:

[openstack-dev] [Congress] Barcelona 2016 summit recap

Hi all, Welcome back from a great summit! Here¹s a brief recap of some Congress-related pieces. 1. Main conference A keynote demo featured Doctor, Congress, and Vitrage. A cellular phone call was made on an openstack NFV implementation. When network cables to a host was cut, an immediate

Re: [openstack-dev] [Congress] Restart Congress server

Hi Ruben, Awesome to hear about your progress! The error seems to be independent of adding a new driver. Could you try using the unchanged congress.conf and restarting again to see if the same problem shows up? Also, could you give the command you¹re using the launch congress-server? Mainly I

[openstack-dev] [Congress] IRC during summit

Hi all! To help us connect and coordinate during the upcoming summit, those who are interested can try IRCcloud (https://www.irccloud.com ; suggested by aimeeu) to communicate over the #congress channel. The service acts as an IRC bouncer to keep your nick connected and send push notifications to

Re: [openstack-dev] [Congress] PTG planning

ds, >Masahito > >On 2016/10/06 16:53, Thierry Carrez wrote: >> Good summary. It is true that for small-to-medium sized teams (which did >> not routinely organize midcycles), there is a tough choice to make. >> >> See a couple of remarks inline: >> >>

Re: [openstack-dev] [Congress] PTG planning

e a couple of remarks inline: > >Eric K wrote: >> Here are some of our choices as a team, as well as some first thoughts >>on >> pros and cons: >> >> 1. Do work sessions at PTGs; no organized work sessions at summits. >> Pro: schedule lines up wit beginnin

Re: [openstack-dev] [Congress] PTG planning

organize work sessions in the style of past mid-cycle sprints; no work sessions at any of the official openstack events. Pro: we can choose schedule and location Con: harder to collaborate with other teams 4. No work sessions at all. On 10/5/16, 4:18 PM, "Eric K" <ekcs.openst...@gma

[openstack-dev] [Congress] PTG planning

Hi all, As you know, the traditional design summit will be split into the work sessions at PTGs and the community forums at the summits. The release schedules will be re-aligned so that the PTGs coincide with the beginning of the dev cycle for each release. http://www.openstack.org/ptg As a

Re: [openstack-dev] [ceilometer] [Congress] ceilometer client `alarms.list()` HTTPException (HTTP N/A)

ubject: Re: [openstack-dev] [ceilometer] [Congress] ceilometer client `alarms.list()` HTTPException (HTTP N/A) To: Eric K <ekcs.openst...@gmail.com>, OpenStack Development Mailing List (not for usage questions) <openstack-dev@lists.openstack.org> Hi Eric, alarm list is not working f

[openstack-dev] [ceilometer] [Congress] ceilometer client `alarms.list()` HTTPException (HTTP N/A)

Hi all, Looking for some help to resolve a breakage in Congress ceilometer-driver. When Congress attempts to perform `alarms.list()` on ceilometer client, the following exception is generated. First suspicion is Congress-end configuration problem, but it¹s only `alarms.list()` that fails. Others

[openstack-dev] [Congress] error updating from nova

Hi all, I ran into this issue when Congress or Horizon attempts to get information from Nova. Same thing happened on multiple devstack attempts. But I want to make sure it's not something specific to my environment. Could someone try to reproduce it? Thanks! Nova client version: 6.0.0 Here¹s a

Re: [openstack-dev] [Congress] Default devstack deployment config

s feature. >>> > >>> > best regards, >>> > Masahito >>> > >>> > On 2016/09/13 11:00, Tim Hinrichs wrote: >>>> >> >>>> >> I'd agree with a single process version of Congress for devstack. I'd >>>> >

Re: [openstack-dev] [Congress] Congress horizon plugin - congressclient/congress API auth issue - help

Anusha and Aimee, Circling back on this issue: it seems that you are seeing different things with regards to horizon authentication using keystone v2. I think we can make good progress if we can clarify where we stand. Anusha said setting the auth_url explicitly to v2 works. Aimee said it

[openstack-dev] [Congress] Default devstack deployment config

Hi all, I want to get people¹s thoughts regarding what we should set as default devstack deployment config for Ocata. At the moment, it is set to deploy three processes: API, policy, and datasource-drivers. I see some potential arguments against that: 1. For most users installing via devstack,

[openstack-dev] [Congress] PTL candidacy

Hi all! I¹m writing to announce my candidacy for Congress PTL (Ocata). First, I¹d like to thank Tim for his outstanding leadership since the very beginning of the project. Under his leadership, Congress has grown from an interesting idea to a capable service. I would also like to thank

Re: [openstack-dev] [Congress] PTL non-candidacy

Thank you so much, Tim, for spearheading and guiding the project all this time! I'm especially grateful for your emphasis on supporting the development and the goals of the contributors. I hope we'll continue to benefit from your vision and your thought-leadership in the future! Eric From: Tim

Re: [openstack-dev] [Congress] Enabling Remote Debugging

Hi Aimee, Thanks for digging into it! Here¹s my understanding of our conventions (and I¹m happy to hear from others). a. If you think it¹s just a straightforward change with zero to minimal impact on architecture, users, and devs, then it makes sense to file a bug or just submit a patch. b. If

Re: [openstack-dev] [oslo] RPC call not appearing to retry

On 8/16/16, 9:28 AM, "Mehdi Abaakouk" <sil...@sileht.net> wrote: >Hi, > >Le 2016-08-15 04:50, Eric K a écrit : >> Hi all, I'm running into an issue with oslo-messaging PRC call not >> appearing to retry. If I do oslo_messaging.RPCClient(transport,

[openstack-dev] [oslo] RPC call not appearing to retry

Hi all, I'm running into an issue with oslo-messaging PRC call not appearing to retry. If I do oslo_messaging.RPCClient(transport, target, timeout=5, retry=10).call(self.context, method, **kwargs) using a topic with no listeners, I consistently get the MessagingTimeout exception in 5 seconds, with

Re: [openstack-dev] [Congress] Mascot

Thanks Tim! Here¹s another idea. It¹s pretty euro-centric, but well. Areopagus: * a place where (in Greek Mythology) Ares was tried by the other gods for murder. * also the site of an early governing council in ancient Athens, at one point charged with investigating corruption *

Re: [openstack-dev] [Congress] Progress on Congress support in OPNFV Colorado

Very exciting development indeed! From: "SULLIVAN, BRYAN L" Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Tuesday, June 14, 2016 at 8:58 PM To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [Congress] Austin recap

Thanks for the summary, Tim. Very productive summit! I¹ve added more notes and a diagram to the HA ether pad. Is that the best way to continue the discussion? https://etherpad.openstack.org/p/newton-congress-availability From: Tim Hinrichs Reply-To: "OpenStack Development

[openstack-dev] [Congress] Congress social at Austin 4/27

Hi Congress folks, We¹re going to have an evening get-together at Openstack Austin. Please shoot me an email at if you¹re planning to come. Hope to see you there! Information: Date: Wednesday, April 27 Time: 6:00PM Location: LAMBERTS DOWNTOWN BARBEQUE 401 West 2nd

Re: [openstack-dev] [Congress] Issue with glancev2 datasource driver

Hi Bryan, Based on our IRC conversation today, you seem to be experiencing this issue we only recently tracked down: https://bugs.launchpad.net/congress/+bug/1563495 The fix is in Mitaka, and still being back-ported to Liberty. Here¹s the Liberty patch if you want to try it out:

Re: [openstack-dev] [Congress] Issues with Tox testing

Thanks for the feedback, Bryan. Glad you got things working! 1. The instructions asking to install those packages are missing from kilo (we¹ll fix that), but they have been there since liberty. Was it perhaps unclear because the line is too long? * Additionally: * $ sudo apt-get install git gcc

[openstack-dev] [Congress] New bug for Mitaka: Glance authentication fails after token expiry

I just discovered a bug that¹s probably been around a long time but hidden by exception suppression. https://bugs.launchpad.net/congress/+bug/1563495 When an auth attempt fails due to token expiry, Congress Glance driver obtains a new token from keystone and sets it in Glance client, but for some

Re: [openstack-dev] [Congress] Push Type Driver implementation

I got the same behavior Tim Hinrichs did using DoctorDriver. The problem when listing datasources does not occur with the basic PushDriver in progress, but it has other issues when pushing and listing data. See From: Tim Hinrichs Reply-To: "OpenStack Development Mailing List

[openstack-dev] [Congress] HOL test completed

Happy to report that everything in Congress HOL* works as expected after all the merges today**. *https://docs.google.com/document/d/1ispwf56bX8sy9T0KZyosdHrSR9WHEVA1oGEIYA2 2Orw/pub **commit 5e2c7cde598fcb4ed781a211fb421a5e94afb406

Re: [openstack-dev] [Congress] Python 3 ready

as a replacement for antlr3. Additional thoughts and suggestions on antlr3 replacement always appreciated =) -Eric On 12/4/15, 3:45 AM, "Victor Stinner" <vstin...@redhat.com> wrote: >Hi, > >Le 04/12/2015 05:12, Eric K a écrit : >> Congress can finally pass python3

[openstack-dev] [Congress] Python 3 ready

Congress can finally pass python34 gating. Here¹s the last patch needed to make it happen. https://review.openstack.org/#/c/253298/ __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

<    1   2