Re: [openstack-dev] [kolla][release][requirements] providing constraints for transitive dependencies

Tony A+ on the explanation. Thanks, dude, you rock! That solves the exact problem. I think what we need is an override for upper-constraints.txt in Kolla. Regards -steve -Original Message- From: Tony Breeds Reply-To: "OpenStack Development Mailing List (not

Re: [openstack-dev] [QA] The end-user test suite for OpenStack clusters

Hi team, here is a short update: 1) The QA user story for destructive testing of OpenStack cloud is on review [1]. 2) The spec for a new framework which will focus on HA/failover and destructive testing is no review [2]. 3) The commit for the new repository is on review [3] as well. [1]

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 27/11/16 23:54 +0100, Thomas Goirand wrote: On 10/12/2016 02:50 PM, Flavio Percoco wrote: Greetings, One of the common complains about the existing project organization in the big tent is that it's difficult to wrap our heads around the many projects there are, their current state (in/out

Re: [openstack-dev] [Openstack-operators] Destructive / HA / fail-over scenarios

Timur Nurlygayanov wrote: > Hi OpenStack developers and operators, > > we are going to create the test suite for destructive testing of > OpenStack clouds. We want to hear your feedback and ideas > about possible destructive and failover scenarios which we need > to

Re: [openstack-dev] [neutron] [tap-as-a-service] stable/newton 'broken'

Anil, do you have any opinion? i'm thinking to branch stable/newton at around 675af77205d4e404bc7c185c13ab6d86f300d185 On Thu, Nov 24, 2016 at 6:25 PM, Takashi Yamamoto wrote: > hi, > > On Thu, Nov 24, 2016 at 6:00 PM, Gary Kotton wrote: >> Please

Re: [openstack-dev] [all][tc] Exposing project team's metadata in README files

On 28/11/16 03:31 +, joehuang wrote: Hello, Flavio, Thank you to move this forward. Is it possible to put the badges at the bottom of README.rst file? Just from the code contributors point of view. Hi :D You're free to move it at the bottom if that's the preference for your project.

[openstack-dev] [Openstack-operators] Destructive / HA / fail-over scenarios

Hi OpenStack developers and operators, we are going to create the test suite for destructive testing of OpenStack clouds. We want to hear your feedback and ideas about possible destructive and failover scenarios which we need to check. Which scenarios we need to check if we want to make sure

Re: [openstack-dev] [tripleo] CI scenarios design - how to add more services

On 11/22/2016 09:02 PM, Emilien Macchi wrote: > == Context > > In Newton we added new multinode jobs called "scenarios". > The challenged we tried to solve was "how to test the maximum of > services without overloading the nodes that run tests". > > Each scenarios deploys a set of services,

Re: [openstack-dev] [stackalytics][neutron] some big tent projects included into 'Neutron Official'

Hi Ihar, This sounds like a bug - the contents of official group should be in sync with the governance repo. I'll take a look what went wrong with it. Thanks, Ilya 2016-11-26 2:28 GMT+03:00 Ihar Hrachyshka : > Hi all, > > I am looking at

[openstack-dev] [tripleo] [ironic] Need to update kernel parameters on local boot

Hi, good afternoon I wanted to start an email thread about how to properly setup kernel parameters on local boot, for our overcloud images on TripleO. These parameters may vary depending on the needs of our end users, and even can be different ( for different roles ) per deployment. As an

Re: [openstack-dev] [tripleo] [ironic] Need to update kernel parameters on local boot

> On Nov 28, 2016, at 7:36 AM, Yolanda Robla Mota wrote: > > Hi, good afternoon > > I wanted to start an email thread about how to properly setup kernel > parameters on local boot, for our overcloud images on TripleO. > These parameters may vary depending on the needs of

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

Hi, This is a reminder that we’ll have a team meeting today at #openstack-meeting at 16.00 UTC. Agenda: * Review action items * Current status (progress, issues, roadblocks, further plans) * Custom Actions API update * Open discussion Renat Akhmerov @Nokia

Re: [openstack-dev] [heat][zaqar][telemetry] Subscribing to events

On 28/10/16 08:32, Julien Danjou wrote: > 2. Content Format > The info/data forwarded by Aodh is alarm, not the original event. At here, > I assume most of the users would like to see the original event, not the alarm. That sounds easy. :) Not that easy:

Re: [openstack-dev] [glance][oslo] oslo.log 3.17.0 use_stderr default change

-Original Message- From: Tony Breeds Reply: OpenStack Development Mailing List (not for usage questions) , OpenStack Development Mailing List Date: November 28, 2016 at 00:19:36 To: OpenStack

Re: [openstack-dev] [infra][neutron] Intel NFV CI voting permission in Neutron

> On 28 Nov 2016, at 12:18, Ihar Hrachyshka wrote: > > I suggest we disable votes for the setup until it’s fixed. UPD: done, the CI is disabled for voting. Ihar __ OpenStack Development Mailing List

[openstack-dev] [nova] away from Nova development for forseeable future

Hi Folks, I was recently tasked with spending some months working full time on another project unrelated to OpenStack Nova. As such I am not likely to be participating in any Nova related work for at least the Ocata development cycle. At this time, I don't know whether I'll be returning to Nova

[openstack-dev] [charms] regular bug day

Hi Folks We have an organised bug day prior to the OpenStack Summit in Barcelona; I felt that this focused everyone onto collaborating on bugs in a good way, and gave us a great checkpoint on what the key issues are that people are hitting and reporting back on the charms. I'd like to proposed

[openstack-dev] [ironic] this week's priorities and subteam reports

Hi, We are nonplussed to present this week's priorities and subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. This Week's Priorities (as of the weekly ironic meeting) 1. portgroup:

Re: [openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

Thanks a bunch for all hard work and contributions! Edgar On 11/28/16, 10:58 AM, "Assaf Muller" wrote: Hi all, For the past few months I've been gaining more responsibilities within Red Hat. I have less time to dedicate to personal contribution and it's

Re: [openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

Sorry to see you go, I hope you stick around to participate on any good bike-shedding sessions! On Mon, Nov 28, 2016 at 11:58 AM, Assaf Muller wrote: > Hi all, > > For the past few months I've been gaining more responsibilities within > Red Hat. I have less time to dedicate to

[openstack-dev] [all] The Future of OpenStack Needs You

Hi All, I’m reaching out to you because we are looking for people who would like to get involved in the __activities around on boarding and the Upstream training__ we are holding before the Summits. We had a very successful training before the Barcelona Summit [1] with around 90 attendees

Re: [openstack-dev] [heat][zaqar][telemetry] Subscribing to events

On 11/28/16, 9:57 AM, "Zane Bitter" wrote: >On 28/10/16 08:32, Julien Danjou wrote: >>> > 2. Content Format >>> > The info/data forwarded by Aodh is alarm, not the original event. At >>> > here, >>> > I assume most of the users would like to see the original event, not

[openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

Hi all, For the past few months I've been gaining more responsibilities within Red Hat. I have less time to dedicate to personal contribution and it's had a considerable tole on my ability to perform my duties upstream to the degree of effectiveness I am satisfied with. To that end, I've decided

Re: [openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

Hey Assaf, It was great to have you as a core member and we still learn a lot from.your valuable blog on networking. All the best of luck for your future endeavors On Nov 29, 2016 00:35, "Vasudevan, Swaminathan (PNB Roseville)" < swaminathan.vasude...@hpe.com> wrote: > Hi Assaf, > Sorry to

[openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

The OpenStack community wants to encourage collaboration by emphasizing contributions to projects that abstract differences between vendor-specific products, while still empowering vendors to integrate their products with OpenStack through drivers that can be consumed by the abstraction layers.

Re: [openstack-dev] [heat][sahara][magnum][tripleo] Scaling nested stack validation

On 23/11/16 17:58, Zane Bitter wrote: I also investigated another issue, which is that since the fix for https://bugs.launchpad.net/heat/+bug/1388140 landed (in Kilo) I believe we are validating nested stacks multiple times (specifically, m times, where m is the stack's depth in the tree):

Re: [openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

Hi Assaf, Sorry to hear that you are stepping down. Thanks for your contribution to neutron and making the test suite more stable. Wish you all success in your current job. Thanks Swami -Original Message- From: Assaf Muller [mailto:as...@redhat.com] Sent: Monday, November 28, 2016

Re: [openstack-dev] [all][tc] Allowing Teams Based on Vendor-specific Drivers

On 11/28/2016 01:33 PM, Doug Hellmann wrote: I'm raising this as an issue because it's not just a hypothetical problem. The Cisco networking driver team, having been removed from the Neutron stadium, is asking for status as a separate official team [1]. I would very much like to find a way to

Re: [openstack-dev] [keytone] Pike PTL

Thank you for your selfless community service, Steve! It takes a LOT of commitment to be a successful PTL, and I think you delivered in spades. We owe you a lot of gratitude. -Dolph On Mon, Nov 21, 2016 at 11:54 AM Steve Martinelli wrote: > Keystoners, > > I do not

Re: [openstack-dev] [glance][oslo] oslo.log 3.17.0 use_stderr default change

Hello Glance team! Hello Tony! About a month ago the oslo team released 3.17.0 of oslo.log which contains [1] which switches the default for use_stderr from True to False. It hasn't made it into upper-constraints.txt because glance is failing[2]. There are 2 easy fixes: 1) switch the glance

[openstack-dev] [nova] Quick recap on where we sit with blueprints

Now that we're past the spec freeze and have a more clear picture of what we're tracking blueprint-wise for Ocata I wanted to give a recap on where we're sitting and level set on expectations. Based on [1] I'm currently tracking 69 blueprints. 3 of those are still pending spec reviews but I'm

Re: [openstack-dev] [glance][oslo] oslo.log 3.17.0 use_stderr default change

On Mon, Nov 28, 2016 at 10:55:56AM -0500, Ian Cordasco wrote: > So, I'm not entirely certain we actually want use_stderr on for > everything by default. If you look at that failing test, it's > asserting there's stderr output from running one of Glance's > administrative commands (in this case

Re: [openstack-dev] [nova] away from Nova development for forseeable future

On 11/28/2016 10:27 AM, Daniel P. Berrange wrote: Hi Folks, I was recently tasked with spending some months working full time on another project unrelated to OpenStack Nova. As such I am not likely to be participating in any Nova related work for at least the Ocata development cycle. At this

Re: [openstack-dev] [kolla] the alternative of log processing tool

I don't really like logstash as it's big memory eating beast. We had good arch without it, and I'd like to keep it this way. Even with logstash we still would need to use rsyslog to push logs around to logstash, and that's a pita (trust me, I wrote it.). Fluentd just became cncf-backed project so

Re: [openstack-dev] [Neutron][neutron-lbaas][octavia] Not be able to ping loadbalancer ip

Thanks Michael I still have the following questions: 1) For active-standby, do the amphorae VM pair really communicate with each other using vrrp protocol, like using multicast vrrp IP? 2) How do we install/configure the Octavia so that amphorae instances are spun as containers or on bare

Re: [openstack-dev] [kolla] the alternative of log processing tool

On Tue, Nov 29, 2016 at 7:29 AM, Michał Jastrzębski wrote: > I don't really like logstash as it's big memory eating beast. We had > good arch without it, and I'd like to keep it this way. Even with > logstash we still would need to use rsyslog to push logs around to > logstash,

[openstack-dev] [nova][bugs] Nova Bugs Team Meeting this Tuesday at 1800 UTC

The next Nova Bugs Team meeting will be Tuesday, November 29 at 1800UTC in #openstack-meeting-4 http://www.timeanddate.com/worldclock/fixedtime.html?iso=20161129T18 Feel free to add to the meeting agenda: https://wiki.openstack.org/wiki/Meetings/Nova/BugsTeam -- Augustina Ragwitz Señora

Re: [openstack-dev] [release] Re: [neutron][networking-midonet] [Openstack-stable-maint] Stable check of openstack/networking-midonet failed

release team, can we (networking-midonet) branch stable/newton from a past commit with a RC tag, backport some changes [1], and then cut the first release on the branch? [1] some addititonal features without db migrations (qos, lbaasv2, ...) and removal of some unsupported code (lbaasv1, ...)

Re: [openstack-dev] [kolla] the alternative of log processing tool

Having custom /dev/log was real pain in few occasions. Also syslog was particularly bad in working with multi-line logging (like python tracebacks). Heka reads local log files, makes things easier, and parses things like tracebacks in it. It's my understanding that fluentd can do the same. On 28

[openstack-dev] [aodh] about alarm update with --query

Hi all, I use aodh cli to create a event alarm with query condition, the cli runs successfully. But when i want to update the query condition, the cli runs failed. The help info about `--query` para with these two cli have no difference. The information is as follows, Does anyone else know

Re: [openstack-dev] [neutron] Stepping down as testing lieutenant and from the core & drivers teams

Hi Assaf, Wish you all the best for your future endeavor! Thanks Vikram -Original Message- From: Vasudevan, Swaminathan (PNB Roseville) [mailto:swaminathan.vasude...@hpe.com] Sent: 29 November 2016 00:35 To: OpenStack Development Mailing List (not for usage questions) Subject: Re:

Re: [openstack-dev] [kolla] Kolla-ansible is available

Jeffrey Zhang wrote: Because the role and dockerfile are tight couplings. For example, the container/Dockerfile may need an environment variable passed by ansible role. without it, the service may not work. Why do they need to be tightly coupled?

[openstack-dev] [vitrage] datasources terminology

Hi, I think we have a confusing terminology in Vitrage datasources. The following parameters are used in the drivers and transformers: * event_type: the type of event/notification that comes from the datasource. For example: ‘compute.instance.delete.end’, ‘volume.detach.start’ *

[openstack-dev] [Horizon] Meeting at 20:00 UTC this Wednesday, 30th November

Hi folks, The Horizon team will be having our next meeting at 20:00 UTC this Wednesday, 30th November in #openstack-meeting-3 Meeting agenda is here: https://wiki.openstack.org/wiki/Meetings/Horizon Anyone is welcome to to add agenda items and everyone interested in Horizon is encouraged to

Re: [openstack-dev] [kolla] the alternative of log processing tool

Why are people/things parsing tracebacks out of log files when the following exists: http://docs.openstack.org/developer/oslo.log/api/formatters.html#oslo_log.formatters.JSONFormatter Seems like oslo.log also has a fluent formatter @

Re: [openstack-dev] [kolla] Kolla-ansible is available

Jeffrey Zhang wrote: ​​ ​​ does ​ anyone ​ ​ has an idea to leverage zuul's cross project testing[0] for kolla and kolla-ansibe gate? ​ Here is a use case: when implementing A service, we need * add dockerfile in kolla project * add ansible role in kolla-ansible project Just curious, but

Re: [openstack-dev] [kolla] Kolla-ansible is available

Because the role and dockerfile are tight couplings. For example, the container/Dockerfile may need an environment variable passed by ansible role. without it, the service may not work. On Tue, Nov 29, 2016 at 1:48 PM, Joshua Harlow wrote: > Jeffrey Zhang wrote: > >>

Re: [openstack-dev] [kolla] the alternative of log processing tool

On Tue, Nov 29, 2016 at 11:28 AM, Michał Jastrzębski wrote: > Having custom /dev/log was real pain in few occasions. Also syslog was > particularly bad in working with multi-line logging (like python > tracebacks). > Heka reads local log files, makes things easier, and parses

Re: [openstack-dev] [kolla] the alternative of log processing tool

On Tue, Nov 29, 2016 at 12:47 PM, Joshua Harlow wrote: > Why are people/things parsing tracebacks out of log files when the > following exists: > > http://docs.openstack.org/developer/oslo.log/api/formatters. > html#oslo_log.formatters.JSONFormatter > > Seems like oslo.log

Re: [openstack-dev] [kolla] Kolla-ansible is available

If we can implement loose coupling, there will be optimal. But it is hard to do this. On Tue, Nov 29, 2016 at 2:50 PM, Joshua Harlow wrote: > Jeffrey Zhang wrote: > >> Because the role and dockerfile are tight couplings. >> >> For example, the container/Dockerfile may

Re: [openstack-dev] [kolla][release][requirements] providing constraints for transitive dependencies

Clark, Cool didn’t know the transitive deps were specified in upper-constraints.txt. Learning new things 24/7 it seems ☺ I’m pretty sure we can work with that and just override the upper constraints file we use. Regards -steve -Original Message- From: Clark Boylan

Re: [openstack-dev] [neutron] NeutronLibImpact: Adoption of db *_FIELD_SIZE constants from neutron-lib

Ok, makes sense. Lets continue as you proposed. On 11/27/16, 10:44 PM, "Henry Gessau" wrote: Gary Kotton wrote: > Would it be worth considering have the three patches: > https://review.openstack.org/399891, https://review.openstack.org/398113

Re: [openstack-dev] [kolla][release][requirements] providing constraints for transitive dependencies

Tony, Are you indicating that all transitive dependencies (e.g. nova depends on x depends on y, y = version of dep we want to specify) are in global-requirements.txt? Regards -steve -Original Message- From: Tony Breeds Reply-To: "OpenStack Development

[openstack-dev] [daisycloud-core] Meeting minutes for IRC meeting 0800UTC Nov. 25 2016

Minutes: http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-11-25-08.00.html Minutes (text): http://eavesdrop.openstack.org/meetings/daisycloud/2016/daisycloud.2016-11-25-08.00.txt Log:

Re: [openstack-dev] [stable][sahara] Drop icehouse branches from repositories

On Tue, Nov 22, 2016 at 06:17:59PM +0300, Vitaly Gridnev wrote: > Hello, > > Several days ago I’ve noticed that sahara-extra and sahara-image-elements > repositories still have icehouse branch. Could someone help us with removing > these branches? Thanks in advance. I can help you to take care

[openstack-dev] [vitrage] common vs utils

Currently, we have `common/utils.py`, `common/file_utils.py` and an empty module `utils` in `vitrage`. In my understanding, `common` means *common to vitrage package* and utils are more *general purpose utility* functions. Would it better that we move `utils.py`, `file_utils.py` and

Re: [openstack-dev] [kolla] the alternative of log processing tool

> On 27 Nov 2016, at 06:55, Jeffrey Zhang wrote: > > * Fluentd > * Logstash I do not have a strong behaviour. At the moment we use the E and K of the ELK stack. Because of that I think it makes sense to go with Logstash. In this way, we have a stack developed by one

Re: [openstack-dev] [kolla][release][requirements] providing constraints for transitive dependencies

On Mon, Nov 28, 2016 at 08:15:17AM +, Steven Dake (stdake) wrote: > Tony, > > Are you indicating that all transitive dependencies (e.g. nova depends on x > depends on y, y = version of dep we want to specify) are in > global-requirements.txt? So in order to reduce confusion I'll try to

Re: [openstack-dev] [kolla] Notes on Ansible fact gathering

> On 23 Nov 2016, at 12:12, Paul Bourke wrote: > > In the cases where users have 500 control nodes and want to add five more > sequentially (the value of doing more than one sequentially is still not > clear to me), we could look into turning on fact caching. At

Re: [openstack-dev] [new][nimble] New project: Nimble

On Mon, Nov 28, 2016 at 1:37 PM, Jay Pipes wrote: > > > For the RackScale Architecture stuff, the Valence project seems to be > doing that and I'm not sure what role Nimble would play. > For Valence, as my understanding, it provides interfaces to help compose/release nodes.

Re: [openstack-dev] [ALU] [vitrage] common vs utils

Sounds good to me ☺ From: Yujun Zhang [mailto:zhangyujun+...@gmail.com] Sent: Monday, November 28, 2016 10:43 AM To: OpenStack Development Mailing List (not for usage questions) Subject: [ALU] [openstack-dev] [vitrage] common vs utils Currently, we have `common/utils.py`, `common/file_utils.py`

Re: [openstack-dev] [infra][neutron] Intel NFV CI voting permission in Neutron

> On 26 Nov 2016, at 00:06, Ihar Hrachyshka wrote: > >> >> On 14 Nov 2016, at 11:44, Znoinski, Waldemar >> wrote: >> >> Hi Neutron, Infra Cores et al, >> I would like to acquire voting (+/-1 Verified) permission for our Intel NFV >> CI. >>