[openstack-dev] [Bareon][Fuel] Stevedore extensions system for Nailgun

Hi, Recently I was working on making Nailgun extensions more usable. Current extensions system has great potential to be used to extend Nailgun's features e.g. integration with other services. This potential is blocked by the fact that all extensions must be placed in Nailgun's source code and be

Re: [openstack-dev] [api] api working group proposed actions guideline needs input

There's related work going on in ironic - https://review.openstack.org/#/c/224022/ - it proposes a way by which a user may query the transitions (actions) of the underlying FSM: "Get me all the valid actions/transitions". Other comments on the review.

[openstack-dev] [kolla] Heka POC

Hi Kolla devs So I've identified the following tests/POCs: * Verify Heka can read logs from containers that log to stdout * Verify Heka can read logs from containers that log to Syslog (/dev/log) * Verify Heka can write logs to local files (as currently done using Rsyslog) If these three POCs

[openstack-dev] Add new plugins to neutron by the way of sub-project

A very Happy New Year 2016 !! At first , I don't know whether  the neutron‘s contributors can receive this letter. If not, could you tell me how to contact with them?I'm sorry to bother you in this way ,but I can't find another way that can get your  reply. We are a neutron  team .  we  add  a  

[openstack-dev] changing in neutron code

Hi All, I am a newbie in an Open Stack developers community. I want to do some modification in Devstack/kilo neutron part. Can anyone guide me how to test the modification in the code part. (1) Should I need to define my own module/class. (2) Can I add some def in neutron code. and

Re: [openstack-dev] [cinder] Object backporting and the associated service

On 5 January 2016 at 18:55, Ryan Rossiter wrote: > This is definitely good to know. Are you planning on setting up something > off to the side of o.vo within that holds a dictionary of all values for a > release? Something like: > > {‘liberty’: {‘volume’: ‘1.3’, …},

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

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

Re: [openstack-dev] [glance][artifacts] FFE for Glare specs

On 14/01/16 14:59 +, Alexander Tivelkov wrote: Hi, Unfortunately I skipped the "spec freeze exception week" due to a long holiday season, so I'd like to ask for the freeze exception for the following two specs now: 1. Add more implementation details to 'deprecate-v3-api' [1] 2. Glare

Re: [openstack-dev] [all] [api] API Working Group Refresher

On Jan 17, 2016, at 8:56 PM, Qiming Teng > wrote: On Fri, Jan 15, 2016 at 12:48:51PM +, Chris Dent wrote: At yesterday's API Working Group meeting we decided it would be a good idea to send out a refresher on the existence of

Re: [openstack-dev] [Fuel] nova-network removal

Roman, Sheena, You meant to remove nova-network completely? Or only for new environments? Should we support nova-network for old (let's say, 7.0) clusters? Thanks, Igor On Fri, Jan 15, 2016 at 10:03 PM, Sheena Gregson wrote: > Adrian – can someone from the PI team please

Re: [openstack-dev] [Fuel] How to auto allocate VIPs for roles in different network node groups?

> Random choices aren't good IMHO, let's use defaults. What if neither of node is in default group? Still use default group? And prey that some third-party plugin will handle this case properly? AFAIU, default nodegroup is slightly artificial thing. There's no such thing like *default*

[openstack-dev] [Fuel][infra] Gerrit UX seems dropped, few patches had been merged without the Fuel CI verified mark

Here is the list of patches merged w/o the verified mark from the Fuel CI [0]. Note that some of them contain "Fuel-CI: disabled", therefore were good to go as is, by design. But the rest was merged by mistake. Sorry for that. Errare humanum est. PS. Would be nice to improve the gerrit UI somehow

[openstack-dev] Closing voting for midcycle agenda on January 25th

On January 25th, I will finalize the agenda for the Kolla midcycle based upon voting in the midcycle agenda document. Feel free to vote, even if your not a core reviewer, on any particular topic (either vote +1, or +0). A +0 vote will be helpful when I craft the agenda to show me that you did

Re: [openstack-dev] [Neutron] OVS flow modification performance

At Mon, 18 Jan 2016 00:42:32 -0500, Kevin Benton wrote: > > Thanks for doing this. A couple of questions: > > What were your rootwrap settings when running these tests? Did you just > have it calling sudo directly? I used devstack's default, which runs root_helper_daemon. > Also, you mention

Re: [openstack-dev] Shovel (RackHD/OpenStack)

Heck, Joseph wrote: Thanks for the links Jeremy! I'm still reading through what exactly "bigtent" means, not sure I grok the placement for littler/ancillary things like this effort, but the the links are hugely helpful! Hey Joe, welcome back :P Rather than defining OpenStack around the

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

We have weekly Nova API meeting tomorrow. 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

Re: [openstack-dev] Exception request : [stable] Ironic doesn't use cacert while talking to Swift ( https://review.openstack.org/#/c/253460/)

On 01/17/2016 09:25 AM, Nisha Agarwal wrote: Hello Team, This patch got approval long back(Jan 6) but due to Jenkins failure in the merge pipeline of the Kilo branch, this patch was not merged. Hence I request for an exception for this patch as this was not merged due to Jenkins issue. Hi.

Re: [openstack-dev] [kolla] Heka v ELK stack logistics

On Fri, Jan 15, 2016 at 2:40 PM, Michał Jastrzębski wrote: > Yeah that's true. We did all of openstack systems but we didn't > implement infra around yet. I'd guess most of services can log either > to stdout or file, and both sources should be accessible by heka. > Also, I'd be

Re: [openstack-dev] changing in neutron code

Hi Atif, you can find all the answers in the Neutron developer guide [1]. cheers, Rossella [1] http://docs.openstack.org/developer/neutron/devref/index.html On 01/17/2016 08:17 PM, Atif Saeed wrote: Hi All, I am a newbie in an Open Stack developers community. I want to do some modification

Re: [openstack-dev] [glance] allow a ranking mechanism for glance-api to order image locations

On Wed, Jan 13, 2016 at 4:07 PM, Jake Yip wrote: > > I am wondering anyone else have solved this before? I would like to hear > your opinions on how we can achieve this, and whether ranking it by > metadata is the way to go. > I spoke with an operator in Vancouver

Re: [openstack-dev] [cinder] Object backporting and the associated service

On 01/18/2016 03:31 PM, Duncan Thomas wrote: > On 5 January 2016 at 18:55, Ryan Rossiter > wrote: > > This is definitely good to know. Are you planning on setting up > something off to the side of o.vo within that holds a

Re: [openstack-dev] [TripleO] Should we have a TripleO API, or simply use Mistral?

- Original Message - > On Thu, 2016-01-14 at 16:04 -0500, Tzu-Mainn Chen wrote: > > > > - Original Message - > > > On Wed, Jan 13, 2016 at 04:41:28AM -0500, Tzu-Mainn Chen wrote: > > > > Hey all, > > > > > > > > I realize now from the title of the other TripleO/Mistral thread > >

Re: [openstack-dev] [Fuel] Diagnostic snapshot generation is broken due to lack of disk space

Igor: It seems that fqdn -> ipaddr will indeed be resolved. Please share your feedback in review: https://review.openstack.org/#/c/266964/3 On Fri, Jan 15, 2016 at 4:25 PM, Igor Kalnitsky wrote: > Sheena - > > What do you mean by *targeted*? Shotgun's designed to be a

[openstack-dev] [release][cinder] os-brick release 0.8.0 (mitaka)

We are stoked to announce the release of: os-brick 0.8.0: OpenStack Cinder brick library for managing local volume attaches This release is part of the mitaka release series. With source available at: http://git.openstack.org/cgit/openstack/os-brick With package available at:

[openstack-dev] [mistral] No team meeting today - 01/18/2016

We won't have a team meeting today because a number of key members won't be able to attend. Renat Akhmerov @Mirantis Inc. __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [Fuel] nova-network removal

We should continue to support nova-network for 7.0 and prior environments, so it won't be removed completely. We should prevent users from creating new environments on Mitaka/8.0 versions and later which use nova-network. On Mon, Jan 18, 2016 at 9:18 AM, Igor Kalnitsky

[openstack-dev] [ironic] wsmanclient

Hi all, We have the openwsman bug[1] for long which affects the AMT and DRAC drivers. I added a simple protocol implementation[2] to python-dracclient a couple months ago using requests and lxml and refactored the DRAC driver to use that instead of openwsman. It's far from being a complete

Re: [openstack-dev] [api] api working group proposed actions guideline needs input

On 01/18/2016 10:05 AM, Michael Krotscheck wrote: Also: I like using the same word for things. Is there a meaningful enough difference between "Actions", "Transitions", and "Tasks", that requires different words? not that i have detected, although i would love hear other opinions on this. i

Re: [openstack-dev] [Nova] notification subteam meeting

Hi, The next meeting of the nova notification subteam will happen 2016-01-19 Tuesday 20:00 UTC [1] on #openstack-meeting-alt on freenode Agenda: - Status of the outstanding specs and code reviews - Agree on the new (reduced) frequency of the meeting - AOB See you there. Cheers, Gibi [1]

Re: [openstack-dev] changing in neutron code

I don’t foget to help us to improve the neutron documentation in the networking guide: http://docs.openstack.org/liberty/networking-guide/ Edgar From: Atif Saeed > Reply-To: "OpenStack Development Mailing List (not for usage questions)"

[openstack-dev] [kolla] Please Vote - Closing voting January 25th for Kolla Midcycle Event

On January 25th, I will finalize the agenda for the Kolla midcycle based upon voting in the midcycle agenda etherpad. Feel free to vote, even if your not a core reviewer, on any particular topic (either vote +1, or +0). A +0 vote will be helpful when I craft the agenda to show me that you did

Re: [openstack-dev] [Fuel] nova-network removal

Sheena, I can confirm, that configurations with both DVS and NSX backends were successfully tested for 7.0 by PI. This backend works also for 8.0 Regards, Andrian On Fri, Jan 15, 2016 at 10:03 PM, Sheena Gregson wrote: > Adrian – can someone from the PI team please

[openstack-dev] [TripleO] Mitaka Milestone 2

Hola Otripletas, According to the official schedule[1], this week is scheduled for Mitaka milestone 2. Do we intend to have something working for this milestone? I have been tracking the issues when deploying with current from all other projects[2] (as opposed to using an old pinned delorean for

[openstack-dev] [Monasca] alarms based on events

Hello, we are just evaluating Monasca for our new cloud infrastructure and I would like to ask if there are any possibilities in current Monasca or some development plans to address following use case: We have a box which we need to monitor and when something goes wrong with the box, it sends

[openstack-dev] [mistral] how to split mistral log files

Hi All I have three linux service file for mistral api, engine and executor All of them running with different param in the "server" (api/ E.g api is /usr/bin/mistral-server --config-file=/etc/mistral/mistral.conf --server=api All of the logs goes to /var/log/mistral/mistral-server.log I would

Re: [openstack-dev] [release] Release countdown for week R-11, Jan 18-22, Mitaka-2 milestone

On Fri, Jan 15, 2016 at 7:55 AM, Doug Hellmann wrote: > Excerpts from Doug Hellmann's message of 2016-01-14 16:20:54 -0500: > > Focus > > - > > > > Next week is the second milestone for the Mitaka cycle. Major feature > > work should be making good progress or be

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Should subnet be optional on member create?

If member port (IP address) is allocated by neutron, then why do we need to specify it explicitly? It can be derived by LBaaS driver implicitly. Thanks, Vivek On 1/17/16, 1:05 AM, "Samuel Bercovici" wrote: >Btw. > >I am still in favor on associating the subnets to

[openstack-dev] [ironic] weekly status report

Hi, We are cool to present this week's subteam report for Ironic. As usual, this is pulled directly from the Ironic whiteboard[0] and formatted. Bugs (dtantsur) === - Stats (diff with 11.01.2016): - Ironic: 148 bugs (+1) + 162 wishlist items (+4). 15 new (+1), 102 in progress

Re: [openstack-dev] [magnum] Temporarily remove swarm func test from gate

Hongbin, I did some digging and found that docker storage driver wasn’t configured correctly at agent nodes. Also it looks like Atomic folks recommend use deicated volumes for DeviceMapper (http://www.projectatomic.io/blog/2015/06/notes-on-fedora-centos-and-docker-storage-drivers/). So added

[openstack-dev] [Nova] sponsor some LVM development

Hello everybody, we are a Europe based operator and we have a case for LVM based nova instances in our new cloud infrastructure. We are currently considering to contribute to OpenStack Nova to implement some features which are currently not supported for LVM based instances (they are only

Re: [openstack-dev] [mistral] how to split mistral log files

Hi, Tomer, If you really want Mistral services to be running on different processes or different servers, I recommend you use different config file respectively, log file path can be configured differently, which can achieve what you said. On Tue, Jan 19, 2016 at 5:19 AM, SHTILMAN, Tomer (Tomer)

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

Hi all! We are skipping the cross-project meeting since we are currently establishing the Cross Project Spec Liaison team [1]. Please check and make sure your team has someone registered in the wiki table [2] by this week, in order to make sure someone from your team is responsible for

Re: [openstack-dev] [cross-project] Cross-Project Specs and Your Project

On 11:24 Jan 14, Mike Perez wrote: > Hello all! > > We've been discussing cross-project spec liaisons on the mailing list [1] and > cross-project meeting [2][3] for a bit, and we're now stating the official > responsibilities [4] of the group. Hey all, The Project Team Guide for Cross-Project

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

On 11/01/16 15:52 -0500, Flavio Percoco wrote: 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:

Re: [openstack-dev] [Neutron] MTU configuration pain

On Mon, Jan 18, 2016 at 4:14 PM, Kevin Benton wrote: > Thanks for the awesome writeup. > > >5) A bridge or veth pair with an IP address can participate in path MTU > discovery (PMTUD). However, these devices do not appear to understand > namespaces and originate the ICMP

[openstack-dev] [all][clients] Enable hacking in python-*clients

Hi Devs, As of now all OpenStack projects has hacking checks which take cares about OpenStack guidelines issues are caught while running PEP8 checks using tox. There are no such checks in any of the python-*client. IMO its worth to enable hacking checks in python-*clients as well which will

Re: [openstack-dev] [magnum] Temporarily remove swarm func test from gate

Hi Egor, Do we need to add a cinder volume to the master nodes for Kubernetes as well? We did not run Docker on the master node before so the volume was not needed. Ton Ngo, From: Hongbin Lu To: Egor Guz , OpenStack Development Mailing

[openstack-dev] [heat] Convergence status

Hi, This is to discuss the status of convergence patches and plans for making it default. The convergence gate jobs have been running successfully since more than a month now. There were three integration tests skipped: 1. StackValidationTest 2. UpdateStackTest.test_stack_update_alias_type 3.

[openstack-dev] [Neutron] [Docs] Definition of a provider Network

Hi everybody, I stumbled over a definition that explains the difference between a Provider network and a self service network. [1] To summarize it says: - Provider Network: primarily uses layer2 services and vlan segmentation and cannot be used for advanced services (fwaas,..) - Self-service

[openstack-dev] [vitrage] Vitrage meeting tomorrow

Hi, We will have Vitrage weekly meeting tomorrow, Wednesday at 9:00 UTC, on #openstack-meeting-3 channel. Agenda: * Current status and progress from last week * Review action items * Next steps * Open Discussion You are welcome to join. Thanks, Ifat.

Re: [openstack-dev] [all][clients] Enable hacking in python-*clients

Hi Abishek, In my understanding, hacking check is enabled for most (or all) of python-*client. For example, flake8 is run for each neutronclient review [1]. test-requirements installs hacking, so I believe hacking check is enabled. openstackclient and novaclient do the same [2] [3]. Am I missing

Re: [openstack-dev] [Neutron] MTU configuration pain

>Yup. We mostly attempt to do that now. Right, but not by default. Can you think of a scenario where advertising it would be harmful? On Jan 18, 2016 23:57, "Matt Kassawara" wrote: > > > On Mon, Jan 18, 2016 at 4:14 PM, Kevin Benton wrote: > >> Thanks

Re: [openstack-dev] [mistral] how to split mistral log files

Thanks Not sure that duplicating mistral.conf three times will be the best in this case , will make things very hard to manage -Original Message- From: EXT Lingxian Kong [mailto:anlin.k...@gmail.com] Sent: Tuesday, January 19, 2016 2:29 AM To: OpenStack Development Mailing List (not

Re: [openstack-dev] [heat] Convergence status

Anant, thank you for the summary. I planned to announce it (enabling convergence by default) on the next week (after m-2). I think, that we need to land two first mentioned patches before it ^. On 19 January 2016 at 09:44, Anant Patil wrote: > > Hi, > > This is to discuss

[openstack-dev] [infra] Blocked access to Gerrit account.

Hello everyone, Yesterday I merged my two accounts on launchpad and after that I cannot log in to my account using SSO on OpenStack gerrit. When I'm logging using my merged account I'm landing in a new account, without any reviews, commits and anything else. Additionally right now there are

Re: [openstack-dev] [magnum] Temporarily remove swarm func test from gate

Hi Egor, Thanks for investigating on the issue. I will review the patch. Agreed. We can definitely enable the swarm tests if everything works fine. Best regards, Hongbin -Original Message- From: Egor Guz [mailto:e...@walmartlabs.com] Sent: January-18-16 2:42 PM To: OpenStack

Re: [openstack-dev] [Neutron] MTU configuration pain

On Sun, Jan 17, 2016 at 8:30 PM, Matt Kassawara wrote: > Prior attempts to solve the MTU problem in neutron simply band-aid it or > become too complex from feature creep or edge cases that mask the primary > goal of a simple implementation that works for most deployments.

Re: [openstack-dev] [Neutron] MTU configuration pain

Thanks for the awesome writeup. >5) A bridge or veth pair with an IP address can participate in path MTU discovery (PMTUD). However, these devices do not appear to understand namespaces and originate the ICMP message from the host instead of a namespace. Therefore, the message never reaches the

Re: [openstack-dev] [Nova] sponsor some LVM development

On 01/18/2016 02:49 PM, Premysl Kouril wrote: > Hello everybody, > > we are a Europe based operator and we have a case for LVM based nova > instances in our new cloud infrastructure. We are currently > considering to contribute to OpenStack Nova to implement some features > which are currently

[openstack-dev] [stable] No stable team meeting on Tuesday 1/26

There are three meetups happening next week and I'll be at one of them, so we're going to cancel next week's meeting. So the next meeting will be on Monday 2/1 at 2100 UTC. -- Thanks, Matt Riedemann __ OpenStack

Re: [openstack-dev] [nova][stable] Proposal to add Tony Breeds to nova-stable-maint

Congrats Tony! -- Michael Davies mich...@the-davies.net Rackspace Cloud Builders Australia __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [OpenStack-Infra] Mitaka Infra Sprint

On Wed, Dec 9, 2015 at 9:17 PM, Joshua Hesketh wrote: > Hi all, > As discussed during the infra-meeting on Tuesday[0], the infra team will > be holding a mid-cycle sprint to focus on infra-cloud[1]. > The sprint is an opportunity to get in a room and really work through

Re: [openstack-dev] [ironic] virtual midcycle dates

On Mon, Jan 11, 2016 at 05:54:30PM -0800, Jim Rollenhagen wrote: > 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 The results appear to indicate February 16-18 works best, so we'll be

Re: [openstack-dev] [kolla] Heka POC

Eric, One request. Please convert the google doc at your earliest convience into a spec, because we require majority approval of all specs, and it takes awhile to get specs merged. If you can get specs in, the review process can begin earlier rather then later :) Thanks! -steve On 1/18/16,

Re: [openstack-dev] [Neutron][LBaaS][Octavia] Should subnet be optional on member create?

Vivek-- "Member" in this case refers to an IP address that (probably) lives on a tenant back-end network. We can't specify just the IP address when talking to such an IP since tenant subnets may use overlapping IP ranges (ie. in this case, subnet is required). In the case of the namespace driver

Re: [openstack-dev] [nova][stable] Proposal to add Tony Breeds to nova-stable-maint

On 1/15/2016 5:44 AM, John Garbutt wrote: On 14 January 2016 at 10:45, Michael Still wrote: I think Tony would be a valuable addition to the team. +1 +1 +1 John On 14 Jan 2016 7:59 AM, "Matt Riedemann" wrote: I'm formally proposing

[openstack-dev] [astara] Outstanding mitaka-2 bugs

Hi All- I mentioned this in todays meeting but wanted to drop a note here since most of us are out on a US holiday... This week is Mitaka-2 [1] and we still have quite a few outstanding bugs that still need resolution. The good news is that (i think) all of them have had patches up for review

Re: [openstack-dev] [Neutron] MTU configuration pain

The MTU setting is an issue because it involves knowledge of the network outside of openstack. That's why it was just a config value that was expected to be set by an operator. This thread is working to see if we can figure that out, or maybe at least come up with a different sub-optimal default.