Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

Here is why I am on board with this. As we have discovered, the logging with the syslog plugin leaves alot to be desired. It (to my understanding) still can't save tracebacks/stacktraces to the log files for whatever reason. stdout/stderr however works perfectly fine. That said the Docker log

[openstack-dev] 转发: [fuel] github can't sync with git because of big uploading

Hi: I have forward the email and can you help me see why no answers. Thanks. Bests Cathy 发件人: wuwenbin 发送时间: 2015年12月30日 10:35 收件人: 'openstack-dev@lists.openstack.org' 抄送: Jiangrui (Henry, R); Zhaokexue 主题: [fuel] github can't sync with git because of big uploading Hi all:

Re: [openstack-dev] [doc] DocImpact vs. reno

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 11/01/16 23:42, Sean Dague wrote: > > This conversation has gone on long enough I've completely lost the > problem we're trying to solve and the constraints around it. Thank you :) > > I'd like to reset the conversation a little. > >

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On Mon, Jan 11, 2016 at 12:57:05PM PST, Clark Boylan wrote: > On Mon, Jan 11, 2016, at 12:35 PM, Sean M. Collins wrote: > > Nice find. I actually pushed a patch recently that we should be > > advertising the MTU by default. I think this really shows that it should > > be enabled by default. > > >

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

Le 11 janv. 2016 18:45, "Michał Jastrzębski" a écrit : > > On 11 January 2016 at 10:55, Eric LEMOINE wrote: > > Currently the services running in containers send their logs to > > rsyslog. And rsyslog stores the logs in local files, located in the > >

[openstack-dev] [Infra] Meeting Tuesday January 12th at 19:00 UTC

Hi everyone, The OpenStack Infrastructure (Infra) team is having our next weekly meeting on Tuesday January 12th, at 19:00 UTC in #openstack-meeting Meeting agenda available here: https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Agenda_for_next_meeting Anyone is welcome to to add

[openstack-dev] Cross-Project Meeting, Tue Jan 12th, 21:00 UTC

Dear PTLs, cross-project liaisons and anyone else interested, We'll have a cross-project meeting January 12th at 21:00 UTC in the NEW #openstack-meeting-cp IRC channel, with the following agenda: * Team announcements (horizontal, vertical, diagonal) * API guides vision - developer.openstack.org

Re: [openstack-dev] [TripleO] Driving workflows with Mistral

- Original Message - > Background info: > > We've got a problem in TripleO at the moment where many of our > workflows can be driven by the command line only. This causes some > problems for those trying to build a UI around the workflows in that > they have to duplicate deployment logic

Re: [openstack-dev] [oslo][osdk] PrettyTable needs a home in OpenStack

Also using the fact that get_string() and __init__() of prettytable are the most complicated (both take kwargs that can tweak the behavior of the generated results) and that most projects (see below) don't seem to be customizing the behavior (that much) it makes me thing its safer to provide a

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

On 2016/01/12 5:14, Armando M. wrote: On 11 January 2016 at 12:04, Carl Baldwin > wrote: What do we do? My calendar was set up with the sane bi-weekly thing and it shows the meeting for tomorrow. The last word from our fearless

Re: [openstack-dev] [Horizon] Routing in Horizon

Rajat, Thanks for starting some discussion here. I think your target=“_self” is taken care of now, right? Re: ng-route vs ui-router - everything I have ever seen or been told supports using ui-router instead of ng-route. I know a quick google search supports that, but let me google that for

Re: [openstack-dev] [ironic][tests] approach to functional/integration tests

I like #1 as well since it would enable quick coding iteration, but I would also like to be able to run the tests against a running OpenStack cluster that includes Ironic, so put me down for #3 (Tempest) as well. Chris Dearborn Dell Inc From: John Villalovos

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

On 11 January 2016 at 13:54, Hirofumi Ichihara < ichihara.hirof...@lab.ntt.co.jp> wrote: > > > On 2016/01/12 5:14, Armando M. wrote: > > > > On 11 January 2016 at 12:04, Carl Baldwin wrote: > >> What do we do? My calendar was set up with the sane bi-weekly thing >> and it

[openstack-dev] [release][release] reno release 1.3.0 (_independent)

We are eager to announce the release of: reno 1.3.0: RElease NOtes manager This release is part of the _independent release series. With source available at: http://git.openstack.org/cgit/openstack/reno With package available at: https://pypi.python.org/pypi/reno For more details,

Re: [openstack-dev] [fuel] github can't sync with git because of big uploading

I understand this is an issue, but I don’t see why syncing to github is needed so urgently? You can still keep working and accessing the repo by developers/tools using openstack’s git farm [1] [1] http://git.openstack.org/cgit/openstack/fuel-plugin-onos/ From: wuwenbin

Re: [openstack-dev] [infra][stackalytics] some projects not visible in stackalytics now

2016-01-11 12:48 GMT+03:00 Thierry Carrez : > > I totally agree. Stackalytics contains data for non-OpenStack projects > anyway (see under "complementary"), so I think it's fine to list unofficial > projects under "Others" or "Unofficial". Will be renamed soon:

Re: [openstack-dev] [neutron] InvalidRequestError: This session is in 'prepared' state; no further SQL can be emitted within this transaction.

vendor specific mech driver code, where I am doing some read/write to sql. def _create_port(self, port): switchports = port['port']['switchports'] LOG.debug(_LE("_create_port switch: %s"), port) network_id = port['port'][' network_id'] subnets = db.get_subnets_by_network(self.context, network_id)

Re: [openstack-dev] [Glance] [Keystone][CI]

Hi bharath, I think it is better to create a bug about that to discuss this issue. I am not sure that Openstack Dev Mailing List is appropriate place to discuss bugs. BTW, your trouble looks similar to https://bugs.launchpad.net/devstack/+bug/1515352. Could you please try WA described in the bug?

Re: [openstack-dev] [oslo][osdk] PrettyTable needs a home in OpenStack

Le 11/01/2016 10:37, Thierry Carrez a écrit : Joshua Harlow wrote: [...] So I'd def help keep prettytable going, of course another option is to move to https://pypi.python.org/pypi/tabulate (which does seem active and/or maintained); tabulate provides pretty much the same thing (actually more

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Ihar Hrachyshka wrote: Sean M. Collins wrote: Just a quick update where we are: Increasing the verbosity of the SSH session into the instance that is created during the cinder portion is showing that we are actually connecting to the instance

[openstack-dev] [neutron] InvalidRequestError: This session is in 'prepared' state; no further SQL can be emitted within this transaction.

Hi All, In my mechanism driver, I am reading/writing into sql db in a fixed interval looping call. Sometimes I get the following error when I stop and start neutron server InvalidRequestError: This session is in 'prepared' state; no further SQL can be emitted within this transaction. I am

Re: [openstack-dev] [neutron] InvalidRequestError: This session is in 'prepared' state; no further SQL can be emitted within this transaction.

Hi! Can you point what mechanism driver is this or the piece of code that give this error? On Mon, Jan 11, 2016 at 11:58 AM, Koteswar wrote: > Hi All, > > > > In my mechanism driver, I am reading/writing into sql db in a fixed > interval looping call. Sometimes I get the

Re: [openstack-dev] [stable] [horizon] Horizon stable and fast increasing Django releases

Thomas Goirand wrote: [...] Best would be if this kind of cap was only a temporary solution until we really fix the issues. If possible (I perfectly know that in some case this may be difficult), I'd like to have Horizon stable to contain backports for Django last release (currently 1.9),

Re: [openstack-dev] [infra][stackalytics] some projects not visible in stackalytics now

Hi, Thierry, Thanks for explanation. One question is whether these projects (like Kingbird, Tacker, Tricircle) will be listed in stackalytics.com any more, maybe not in the "OpenStack others", but "Others" category? It's also important for Technical Committee/others to know the contribution of

Re: [openstack-dev] [oslo][osdk] PrettyTable needs a home in OpenStack

Joshua Harlow wrote: [...] So I'd def help keep prettytable going, of course another option is to move to https://pypi.python.org/pypi/tabulate (which does seem active and/or maintained); tabulate provides pretty much the same thing (actually more table formats @

Re: [openstack-dev] [OpenStack-Infra] [infra][stackalytics] some projects not visible in stackalytics now

Hi everyone! It appears that Stackalytics host is banned by review.openstack.org. It gets "Received disconnect from 2001:4800:7818:102:be76:4eff:fe05:9b12: 7: Too many concurrent connections" while attempting to execute "gerrit" command. As consequence Stackalytics fails to retrieve list of

Re: [openstack-dev] [nova] [all] Excessively high greenlet default + excessively low connection pool defaults leads to connection pool latency, timeout errors, idle database connections / workers

On 01/08/2016 09:51 PM, Mike Bayer wrote: On 01/08/2016 04:44 AM, Radomir Dopieralski wrote: On 01/07/2016 05:55 PM, Mike Bayer wrote: but also even if you're under something like mod_wsgi, you can spawn a child process or worker thread regardless. You always have a Python interpreter

[openstack-dev] Service password storage

Dear openstack developers, I installed openstack via devstack recently, and I found out that the admin passwords for services like cinder and nova are stored in plain text in their /etc/*/*.conf files. These files are rw--r--r-- by default, which I believe to be a pretty serious security risk. Is

Re: [openstack-dev] [Neutron] Heads up for decomposed plugin break

Sean M. Collins wrote: On Fri, Jan 08, 2016 at 07:50:47AM PST, Chris Dent wrote: On Fri, 8 Jan 2016, Gary Kotton wrote: The commit https://github.com/openstack/neutron/commit/5d53dfb8d64186- b5b1d2f356fbff8f222e15d1b2 may break the decomposed plugins that make use of the

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Sean M. Collins wrote: Just a quick update where we are: Increasing the verbosity of the SSH session into the instance that is created during the cinder portion is showing that we are actually connecting to the instance successfully. We get the dropbear SSH banner, but

Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating

On Sun, Jan 10 2016, AFEK, Ifat (Ifat) wrote: > I'm a bit confused. This thread started by liusheng asking to remove the > notifications to the bus[1], and I replied saying that we do want to use this > capability in Vitrage. What is the notifier plugin that you suggested? Is it > the same

[openstack-dev] [glance] Seeking FFE for "Prevention of Unauthorized errors in Swift driver"

Hello Glance Team! I would like to request FFE for the following spec: https://review.openstack.org/#/c/248681/. The change allows users not to bother about token expiration when uploading/downloading big images to/from swift backend which is pretty useful IMO. The change is not visible to end

Re: [openstack-dev] [nova][bugs] help needed: volunteers for bug skimming (1 week)

Augustina Ragwitz wrote on 01/08/2016 07:50:23 PM: > From: Augustina Ragwitz > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 01/08/2016 08:00 PM > Subject: Re: [openstack-dev]

Re: [openstack-dev] [oslo][cfg] Benefit of MultiStrOpt over ListOpt

John Stanford wrote on 01/10/2016 10:49:08 PM: > From: John Stanford > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 01/10/2016 10:55 PM > Subject: Re: [openstack-dev] [oslo][cfg] Benefit of

Re: [openstack-dev] [infra][stackalytics] some projects not visible in stackalytics now

joehuang wrote: Thanks for explanation. One question is whether these projects (like Kingbird, Tacker, Tricircle) will be listed in stackalytics.com any more, maybe not in the "OpenStack others", but "Others" category? It's also important for Technical Committee/others to know the

Re: [openstack-dev] [Horizon] Updating XStatic packages

In terms of process, obviously updating the data in the xstatic is relatively easy (for most packages) but I wonder from a review standpoint what sort of process we should have here. To approve a merge of an xstatic package update, I feel like I should have, in order of preference: 1. a link to

Re: [openstack-dev] [Horizon] Routing in Horizon

The tag addition has had to be reverted as it broke other parts of the application (notably lazy loaded tabs like Instance Details), sadly. Regarding which router to use - I've used the built-in router in the past quite successfully. I think I'd want to see a solid reason for using a 3rd party

[openstack-dev] How to get the current stable release

Sorry if this is a stupid question and I waste your time. I am looking for a file that speicifes the name and version number of the latest stable release. I have not found this information in the governance repository (I only found a hard coded variable called latest_stable_branch in the

[openstack-dev] [keystone][security] New BP for anti brute force in keystone

I have registered a new bp for keystone with the capability of anti brute force Problem Description: the attacks of account are increasing in the cloud the attacker steals the account information by guessing the password in brute force. therefore, the ability of account in anti brute force is

[openstack-dev] [puppet] list of blockers to deploy mitaka

Hi, I've listed the blockers I've found out when trying to deploy our Puppet modules with Mitaka: https://etherpad.openstack.org/p/puppet-openstack-ci-mitaka Until we don't fix all those issues, we can't bump our CI to Mitaka, so we really need to make progress if we want to synchronize our

[openstack-dev] Nova quota-show questions

https://bugs.launchpad.net/python-novaclient/+bug/1337990 nova quota-show seems to have a couple of issues 1) showing admin quotas (even if current tenant is demo) -this can be solved by the fix proposed in https://review.openstack.org/#/c/265971/ i think 2) But the problem is how to

[openstack-dev] [nova] Nova API sub-team meeting

Sorry for sending this mail late. We have weekly Nova API meeting today. The meeting is being held Tuesday UTC1200. The proposed agenda and meeting details are here: https://wiki.openstack.org/wiki/Meetings/NovaAPI Please feel free to add items to the agenda. Thanks

[openstack-dev] [ironic] virtual midcycle dates

Hi all, Here's a list of potential dates for our midcycle; please note which you would be able to attend. http://doodle.com/poll/2gnvq6eee3a6dfbk Note that since we're including people from lots of time zones, this will be basically running for much of the day. We'll have to coordinate sessions

Re: [openstack-dev] [nova] config options: IRC meeting at Jan. 11th

Hi Markus I am sorry that I missed the meeting. Bu it seems like sfinucan already asked what was in my mind, like getting the patches merged faster.. >From the logs I finally understood what "single point of entry for sample >config g eneration" is for. So I will wait that to be merged and

[openstack-dev] [release][stable] pbr release 0.11.1 (kilo)

We are jubilant to announce the release of: pbr 0.11.1: Python Build Reasonableness This release is part of the kilo stable release series. With source available at: http://git.openstack.org/cgit/openstack-dev/pbr With package available at: https://pypi.python.org/pypi/pbr For more

[openstack-dev] [all][i18n] Proposed change for consistent setup of translation - up for review

Projects that want to have translations, need to setup their repository in very specific ways which lead to quite a few questions from some of you and also quite different solutions. Let's make this easier - and consistent. I've written a spec that aims to provide a consistent set up for the

Re: [openstack-dev] [glance][all] glance_store drivers deprecation/stabilization: Volunteers needed

Greetings, Gentle reminder that this is happening next week. Cheers, Flavio - Original Message - > From: "Flavio Percoco" > To: openstack-dev@lists.openstack.org > Sent: Thursday, December 10, 2015 9:16:09 AM > Subject: [glance][all] glance_store drivers

[openstack-dev] [release][ironic] ironic-python-agent release 1.1.0 (mitaka)

We are glad to announce the release of: ironic-python-agent 1.1.0: Ironic Python Agent Ramdisk This release is part of the mitaka release series. With package available at: https://pypi.python.org/pypi/ironic-python-agent For more details, please see below. 1.1.0 ^ New Features

Re: [openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

On 11 January 2016 at 12:04, Carl Baldwin wrote: > What do we do? My calendar was set up with the sane bi-weekly thing > and it shows the meeting for tomorrow. The last word from our > fearless leader is that we'll have it today. So, I'll be there today > unless instructed

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Nice find. I actually pushed a patch recently that we should be advertising the MTU by default. I think this really shows that it should be enabled by default. https://review.openstack.org/263486l -- Sent from my Android device with K-9 Mail. Please excuse my

Re: [openstack-dev] [Horizon] Bug Day 2

Reminder about bug day! Just starting if you’re over in Australia ;) Rob On 4 Jan 2016, at 10:54, Rob Cresswell (rcresswe) > wrote: Hi folks, I think we should have another bug day to continue the good work started last time. I’d suggest Tuesday

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

On Mon, Jan 11, 2016, at 12:35 PM, Sean M. Collins wrote: > Nice find. I actually pushed a patch recently that we should be > advertising the MTU by default. I think this really shows that it should > be enabled by default. > > https://review.openstack.org/263486l > ++ Neutron should be able to

[openstack-dev] [release][stable][ironic] ironic-python-agent release 1.0.1 (liberty)

We are chuffed to announce the release of: ironic-python-agent 1.0.1: Ironic Python Agent Ramdisk This release is part of the liberty stable release series. With package available at: https://pypi.python.org/pypi/ironic-python-agent For more details, please see below. 1.0.1 ^ Bug

Re: [openstack-dev] [Fuel] Wipe of the nodes' disks

>As Andrew said already, in such case LVM meta data will remain on the hard drive. So if you remove partition table, reboot the node (env reset), then configure exactly the same partition table (like when you use the same >default disk allocation in Fuel), then Linux will find LVM info on the same

Re: [openstack-dev] [doc] [api] Vision and changes for OpenStack API Guides

On 01/08/2016 04:39 PM, Anne Gentle wrote: Hi all, With milestone 2 coming next week I want to have a chat about API guides, API reference information, and the http://developer.openstack.org site. We have a new tool, fairy-slipper [1], yep you read that right, that can migrate files from WADL

Re: [openstack-dev] [doc] DocImpact vs. reno

On 11/01/16 20:08, Sean Dague wrote: On 01/10/2016 11:31 PM, Lana Brindley wrote: Wow. That'll make the release notes process painful this round ... o.O Hmmm. In my mind it will make it a lot easier. In the past we end up getting to the release and sit around and go "hmmm, what did we change

Re: [openstack-dev] Cinder as generic volume manager

Hi Team, Let me introduce updates related to use-cinder-without-nova blueprint [1]. According to spec [2] we've introduced new python-brick-cinderclient-ext project [3]. It's an official Cinder project and implemented as an extension to python-cinderclient. For now, it supports only

[openstack-dev] [release] Release models to be frozen around mitaka-2

Hi everyone, This is a small warning that we'll be freezing the release model for deliverables in the Mitaka cycle at mitaka-2 (January 21). So for example if you wanted to switch from release:independent to one of the cycle-oriented models (release:cycle-with-intermediary or

[openstack-dev] [mistral] Team meeting - 01/11/2016

Hi, We’ll have a team meeting today at our regular time 16.00 UTC at #openstack-meeting. Please join to discuss the project status. Agenda: Review action items Current status (progress, issues, roadblocks, further plans) Open discussion Renat Akhmerov @ Mirantis Inc.

Re: [openstack-dev] [neutron] InvalidRequestError: This session is in 'prepared' state; no further SQL can be emitted within this transaction.

Is 'self.context' used to handle other requests as well? I would suggest generating a new context (neutron.context.get_admin_context()) for each fixed interval looping call to ensure you aren't sharing a DB session with another thread. On Mon, Jan 11, 2016 at 2:26 AM, Koteswar

Re: [openstack-dev] [nova][neutron][upgrade] Grenade multinode partial upgrade

Ihar Hrachyshka wrote: Ihar Hrachyshka wrote: Sean M. Collins wrote: Just a quick update where we are: Increasing the verbosity of the SSH session into the instance that is created during the cinder portion is showing that we

Re: [openstack-dev] [doc] DocImpact vs. reno

On 01/11/2016 07:55 AM, Tom Fifield wrote: > On 11/01/16 20:08, Sean Dague wrote: >> On 01/10/2016 11:31 PM, Lana Brindley wrote: >> >>> Wow. That'll make the release notes process painful this round ... o.O >> >> Hmmm. In my mind it will make it a lot easier. In the past we end up >> getting to

Re: [openstack-dev] [neutron] InvalidRequestError: This session is in 'prepared' state; no further SQL can be emitted within this transaction.

On 01/11/2016 03:58 AM, Koteswar wrote: > Hi All, > > > > In my mechanism driver, I am reading/writing into sql db in a fixed > interval looping call. Sometimes I get the following error when I stop > and start neutron server > > InvalidRequestError: This session is in 'prepared' state; no

Re: [openstack-dev] [nova] [all] Excessively high greenlet default + excessively low connection pool defaults leads to connection pool latency, timeout errors, idle database connections / workers

On 01/11/2016 05:39 AM, Radomir Dopieralski wrote: > On 01/08/2016 09:51 PM, Mike Bayer wrote: >> >> >> On 01/08/2016 04:44 AM, Radomir Dopieralski wrote: >>> On 01/07/2016 05:55 PM, Mike Bayer wrote: >>> but also even if you're under something like mod_wsgi, you can spawn a child

Re: [openstack-dev] [doc] DocImpact vs. reno

On 01/10/2016 11:31 PM, Lana Brindley wrote: > Wow. That'll make the release notes process painful this round ... o.O Hmmm. In my mind it will make it a lot easier. In the past we end up getting to the release and sit around and go "hmmm, what did we change in the last 6 months that people care

Re: [openstack-dev] [all] re-introducing twisted to global-requirements

On 01/08/2016 03:52 PM, Jim Rollenhagen wrote: > On Fri, Jan 08, 2016 at 03:39:51PM -0500, Jay Pipes wrote: >> >> No, nothing nefarious there. Sorry for letting my personal frustrations >> bubble over into this. >> >> I am not blocking anything from going forward and I definitely am not asking >>

[openstack-dev] [OpenStack-Infra] [fuel-plugin-mistral] Request to add group member into the new Openstack project

Hi openstack-infra team, Kindly please add nmakhot...@mirantis.com to the following Gerrit ACL groups: https://review.openstack.org/#/admin/groups/1156,members https://review.openstack.org/#/admin/groups/1155,members (ref. https://review.openstack.org/#/c/238890/) -- Best Regards, Nikolay

[openstack-dev] [puppet] weekly meeting #66

Hi folks! Tomorrow we will have our weekly meeting at UTC 1500. Here is our agenda: https://etherpad.openstack.org/p/puppet-openstack-weekly-meeting-20160112 Feel free to add more topics, reviews, bugs, as usual. See you there, -- Emilien Macchi signature.asc Description: OpenPGP digital

Re: [openstack-dev] [neutron] InvalidRequestError: This session is in 'prepared' state; no further SQL can be emitted within this transaction.

thanks a lot. I will try this. On Mon, Jan 11, 2016 at 7:26 PM, Mike Bayer wrote: > > > On 01/11/2016 03:58 AM, Koteswar wrote: > > Hi All, > > > > > > > > In my mechanism driver, I am reading/writing into sql db in a fixed > > interval looping call. Sometimes I get the

Re: [openstack-dev] [telemetry][aodh][vitrage] The purpose of notification about alarm updating

so one point i should mention is that the notification we propose on removing was originally attended for Ceilometer events. much in same way as disabling the aodh-notifier to allow Vitrage to consume alarm triggers, it isn't exactly safe for Vitrage to consume the existing messages as

Re: [openstack-dev] [doc] DocImpact vs. reno

Tom Fifield wrote on 01/11/2016 01:55:21 PM: > From: Tom Fifield > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 01/11/2016 01:55 PM > Subject: Re: [openstack-dev] [doc] DocImpact vs.

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

On Mon, Jan 11, 2016 at 5:01 PM, Michał Jastrzębski wrote: > On 11 January 2016 at 09:16, Eric LEMOINE wrote: >> * Logstash was designed for logs processing. Heka is a "unified data >> processing" software, designed to process streams of any type of

Re: [openstack-dev] [glance] Seeking FFE for "Support single disk image OVA/OVF package upload"

Hello Glance Team! Hope you had a wonderful vacation and wishing you health and happiness for 2016. Would very much appreciate your considering https://review.openstack.org/194868 for a feature freeze exception. I believe the spec is pretty solid, and we can deliver on the

Re: [openstack-dev] [doc] DocImpact vs. reno

Excerpts from Lana Brindley's message of 2016-01-11 14:31:17 +1000: > On 09/01/16 14:07, Tom Fifield wrote: > > On 08/01/16 21:15, Sean Dague wrote: > >> On 01/07/2016 06:21 PM, Lana Brindley wrote: > >>> > On 7 Jan 2016, at 2:09 AM, Sean Dague wrote: > > On

[openstack-dev] [TripleO] Driving workflows with Mistral

Background info: We've got a problem in TripleO at the moment where many of our workflows can be driven by the command line only. This causes some problems for those trying to build a UI around the workflows in that they have to duplicate deployment logic in potentially multiple places. There are

[openstack-dev] [neutron] FYI: Updated wiki on creating functional jobs

I revised the wiki page that I created previously on how to add functional jobs to the gate. I added more details, indicated about getting liaison review, and added some miscellaneous information on templates, skipping tests, and making tests release based. Ref:

[openstack-dev] [qa] [eslint-config-openstack] Nominating Beth Elwell to eslint-config-openstack core

Hello everyone! This email is to nominate Elizabeth "Beth" Elwell (aka betherly) to core on eslint-config-openstack. She provides valuable EU timezone coverage, as well as a friendly and inviting demeanor when discussing language rules. Also, she's been keeping up-to-date with the extant reviews,

Re: [openstack-dev] [doc] [api] Vision and changes for OpenStack API Guides

On Fri, Jan 8, 2016 at 7:35 PM, Anne Gentle wrote: > > > On Fri, Jan 8, 2016 at 3:39 PM, Anne Gentle > wrote: > >> Hi all, >> >> With milestone 2 coming next week I want to have a chat about API guides, >> API reference information,

[openstack-dev] [mistral] Team meeting minutes - 1/11/2016

Hi, Thank you for joining the meeting today. In case you’d like to see meeting minutes and log here they are: http://eavesdrop.openstack.org/meetings/mistral/2016/mistral.2016-01-11-16.00.html

[openstack-dev] [Neutron] Team meeting on Tuesday 1400UTC

Hi neutrinos, A kind reminder for tomorrow's meeting at 1400UTC. Cheers, Armando [1] https://wiki.openstack.org/wiki/Network/Meetings __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Nova][Neutron] Live Migration Issues with L3/L2

Hi Nova/Neutron Folks, Are we with an agreement on the Nova/Neutron related changes for addressing the Live Migration issues. We started this thread couple of weeks back and it went silent. The discussion is still active and being discussed as part of the bug.

Re: [openstack-dev] [Neutron] Heads up for decomposed plugin break

> On Jan 11, 2016, at 2:42 AM, Ihar Hrachyshka wrote: > > Sean M. Collins wrote: > >>> On Fri, Jan 08, 2016 at 07:50:47AM PST, Chris Dent wrote: On Fri, 8 Jan 2016, Gary Kotton wrote: The commit

Re: [openstack-dev] [ironic][tests] approach to functional/integration tests

Option 3 - to concentrate on Tempest tests https://review.openstack.org/#/c/253982/ Cheers, Serge Kovaleff http://www.mirantis.com cell: +38 (063) 83-155-70 On Mon, Jan 11, 2016 at 4:49 PM, Serge Kovaleff wrote: > Hi All, > > Last week I had a noble goal to write

Re: [openstack-dev] [API] [Glance] New v2 Image Import Specification Discussion

On 08/01/16 17:14 +, Ian Cordasco wrote: Hey all, Yo! Thanks for taking the time to read the spec and writing this email. I'm well aware that this isn't exactly timely because we've partially agreed on the import spec in large strokes. [1]_ I haven't had a great deal of time before

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

On 11 January 2016 at 09:16, Eric LEMOINE wrote: > Hi > > As discussed on IRC the other day [1] we want to propose a distributed > logs processing architecture based on Heka [2], built on Alicja > Kwasniewska's ELK work with > .

Re: [openstack-dev] [oslo][osdk] PrettyTable needs a home in OpenStack

Excerpts from Victor Stinner's message of 2016-01-11 11:15:56 +0100: > Le 11/01/2016 10:37, Thierry Carrez a écrit : > > Joshua Harlow wrote: > >> [...] > >> So I'd def help keep prettytable going, of course another option is to > >> move to https://pypi.python.org/pypi/tabulate (which does seem

Re: [openstack-dev] [ironic][tests] approach to functional/integration tests

We might want to implement all three options. The more tests the better :) Cheers, Serge Kovaleff http://www.mirantis.com cell: +38 (063) 83-155-70 On Mon, Jan 11, 2016 at 5:41 PM, John Villalovos wrote: > I personally like Option #1 as an additional goal is to

Re: [openstack-dev] [ironic][tests] approach to functional/integration tests

I personally like Option #1 as an additional goal is to make it easy for developers to also run the functional tests with 'tox -efunctional'. And also run the functional tests as part of a normal tox run. On Mon, Jan 11, 2016 at 6:54 AM, Serge Kovaleff wrote: > Option 3

Re: [openstack-dev] [oslo][osdk] PrettyTable needs a home in OpenStack

On 11/01/16 11:15 +0100, Victor Stinner wrote: Le 11/01/2016 10:37, Thierry Carrez a écrit : Joshua Harlow wrote: [...] So I'd def help keep prettytable going, of course another option is to move to https://pypi.python.org/pypi/tabulate (which does seem active and/or maintained); tabulate

Re: [openstack-dev] [nova] config options: IRC meeting at Jan. 11th

Markus Zoeller/Germany/IBM@IBMDE wrote on 01/08/2016 03:21:28 PM: > From: Markus Zoeller/Germany/IBM@IBMDE > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 01/08/2016 03:22 PM > Subject: [openstack-dev] [nova] config options: IRC

Re: [openstack-dev] [glance] Seeking FFE for "Support single disk image OVA/OVF package upload"

On 11/01/16 15:01 +, stuart.mcla...@hp.com wrote: An HTML attachment was scrubbed... URL: I downloaded the patch which implements the spec (https://review.openstack.org/#/c/214810): I can

Re: [openstack-dev] [Nova][Glance] Nova + Glance_v2 = Love

Sam, Flavio, Zhenyu, Daniel thank you for your responses! Indeed, we're in a difficult position with activating zero-size images... To fix it we have to solve 2 problems: one with disk and container formats parameters - glance v2 doesn't allow activate images if these two are unset; and the

[openstack-dev] [release] change to deliverable file schema: send-announcements-to

Liaisons, With the increase in release announcements on the openstack-announce list, we've had requests to move some of that traffic that isn't of immediate interest to most users to openstack-dev. Last week we merged changes to the schema of the deliverables files in the releases repository to

[openstack-dev] [kolla] Introduction of Heka in Kolla

Hi As discussed on IRC the other day [1] we want to propose a distributed logs processing architecture based on Heka [2], built on Alicja Kwasniewska's ELK work with . Please take a look at the design document I've started working on [3]. The document

[openstack-dev] [ironic][tests] approach to functional/integration tests

Hi All, Last week I had a noble goal to write "one-more" functional test in Ironic. I did find a folder "func" but it was empty. Friends helped me to find a WIP patch https://review.openstack.org/#/c/235612/ and here comes the question of this email: what approach we would like to implement:

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

I like the idea of using Heka. You and I have discussed this on IRC before. So my vote for this is +1. I can't think of any downside. I would like to hear Alicja Kwasniewska's view on this as she has done the majority of work with Logstash up until this point. Sam Yaple On Mon, Jan 11, 2016 at

Re: [openstack-dev] [ironic] RFC: stop using launchpad milestones and blueprints

FYI, this work was completed. Docs are here: http://docs.openstack.org/developer/ironic/dev/code-contribution-guide.html#adding-new-features // jim On Wed, Dec 09, 2015 at 01:58:34PM -0800, Jim Rollenhagen wrote: > On Fri, Dec 04, 2015 at 05:38:43PM +0100, Dmitry Tantsur wrote: > > Hi! > > > >

Re: [openstack-dev] [kolla] Introduction of Heka in Kolla

On 11 January 2016 at 10:55, Eric LEMOINE wrote: > On Mon, Jan 11, 2016 at 5:01 PM, Michał Jastrzębski wrote: >> On 11 January 2016 at 09:16, Eric LEMOINE wrote: > >>> * Logstash was designed for logs processing. Heka is a

Re: [openstack-dev] [oslo][osdk] PrettyTable needs a home in OpenStack

On Mon, Jan 11 2016, Doug Hellmann wrote: > I suspect we could skip porting a lot of those, since they look like > clients and we're working to move all command line programs into the > unified client. Not really in the telemetry roadmap honestly. But we could move away From prettytable without

Re: [openstack-dev] [oslo][osdk] PrettyTable needs a home in OpenStack

And here is a simple converter that uses tabulate but has somewhat like the pretty table object format that people are used to (could be away to get 90% of the common usage over to tabulate, minus the special prettytable users that are doing advanced things).

  1   2   >