[openstack-dev] [neutron] Metering can't count traffic for floating ip, or internal ip.

hi all， neutron metering can only count traffic that we send to *remote_ip*(egress), and *remote_ip* send to us(ingress), I think we should add method to count the traffic for floating ip or internal ip. Any suggestions is welcome. Best regards Ran

[openstack-dev] [neutron] Metering can't count traffic for floating ip, or internal ip.

hi all， neutron metering can only count traffic that we send to *remote_ip*(egress), and *remote_ip* send to us(ingress), I think we should add method to count the traffic for floating ip or internal ip. Any suggestions is welcome. Best regards Ran

Re: [openstack-dev] zuulv3 log structure and format grumblings

On Thu, 4 Jan 2018, 11:15 pm Matt Riedemann, wrote: > On 1/4/2018 12:20 PM, Clark Boylan wrote: > > I've pushed uphttps://review.openstack.org/531208 as a quick check > that this is indeed the general problem, but for longer term fix I think we > want to update our log

Re: [openstack-dev] [TripleO][CI] Which network templates to use in CI (with and without net isolation)?

On Thu, Jan 4, 2018 at 5:26 PM, Sagi Shnaidman wrote: > Hi, all > > we have now network templates in tripleo-ci repo[1] and we'd like to move > them to tht repo[2] and to use them from there. They've already been moved from tripleo-ci to tripleo-heat-templates:

[openstack-dev] [TripleO][CI] Which network templates to use in CI (with and without net isolation)?

Hi, all we have now network templates in tripleo-ci repo[1] and we'd like to move them to tht repo[2] and to use them from there. We have also default templates defined in overcloud-deploy role[3]. So the question is - which templates should we use and how to configure them? One option for

Re: [openstack-dev] zuulv3 log structure and format grumblings

On 1/4/2018 12:20 PM, Clark Boylan wrote: I've pushed uphttps://review.openstack.org/531208 as a quick check that this is indeed the general problem, but for longer term fix I think we want to update our log publishing ansible roles to compress everything that isn't already compressed. Yup

Re: [openstack-dev] [all] propose to upgrade python kubernetes (the k8s python client) to 4.0.0 which breaks oslo.service

On Tue, Jan 2, 2018 at 1:56 AM, Eyal Leshem wrote: > Hi , > > According to https://github.com/eventlet/eventlet/issues/147 - it's looks > that eventlet > has issue with "multiprocessing.pool". > > The ThreadPool used in code that auto-generated by swagger. > > Possible

Re: [openstack-dev] [nova] Working toward Queens feature freeze and RC1

Folks- >> - NRP affordance in GET /allocation_candidates >>    . PATCHES: - >>    . STATUS: Not proposed >>    . PRIORITY: Critical >>    . OWNER: jaypipes >>    . DESCRIPTION: In the current master branch, the placement API will >> report allocation candidates from [(a single non-sharing

[openstack-dev] [castellan] Transferring ownership of secrets to another user

Has there been any previous discussion on providing a mechanism for transferring ownership of a secret from one user to another? Cinder supports the notion of transferring volume ownership to another user, who may be in another tenant/project. However, if the volume is encrypted it's possible

[openstack-dev] [tripleo] TripleO CI end of sprint status

Hello, On January 03 we came the end of sprint using our new team structure, and here’s the highlights. Sprint Review: This was a tech debt sprint, and due the holidays and mostly of the team out, we haven't set a goal for this sprint, leaving the team free to work on the tech debt cards, as

Re: [openstack-dev] [nova] Working toward Queens feature freeze and RC1

On 01/04/2018 01:38 PM, Eric Fried wrote: Matt, et al- * Nested resource providers: I'm going to need someone closer to this work like Jay or Eric to provide an update on where things are at in the series of changes and what absolutely needs to get done. I have personally found it hard to

Re: [openstack-dev] [Ironic] Removal of tempest plugin code from openstack/ironic & openstack/ironic-inspector

Note: I am proposing in the next Ironic meeting ( https://wiki.openstack.org/wiki/Meetings/Ironic#Agenda_for_next_meeting ) that we move forward on removing the tempest plugin code from openstack/ironic and openstack/ironic-inspector. It will have been over three weeks since the initial email in

Re: [openstack-dev] [nova] Working toward Queens feature freeze and RC1

Matt, et al- > * Nested resource providers: I'm going to need someone closer to this > work like Jay or Eric to provide an update on where things are at in the > series of changes and what absolutely needs to get done. I have > personally found it hard to track what the main focus items are for

Re: [openstack-dev] zuulv3 log structure and format grumblings

On Thu, Jan 4, 2018, at 6:46 AM, Matt Riedemann wrote: > I've talked to a few people on the infra team about this but I'm not > sure what is temporary and transitional and what is permanent and needs > to be fixed, and how to fix it. > > The main issue is for newer jobs like tempest-full, the

Re: [openstack-dev] [openstack-ansible] problems with bringing up openstack in AIO flavor with OVS

Hello, On 04/01/18 10:29, Periyasamy Palanisamy wrote: > Hi OSA Experts, > >   > > I’m trying to bring up openstack using openstack-ansible in AIO flavor > by having neutron ml2 plugin set to ovs. > > OSA is being executed from OPNFV XCI deployer with attached > openstack_user_config and

[openstack-dev] [all][api] POST /api-sig/news

Greetings OpenStack community, Happy new year to all and welcome to the first API-SIG meeting of 2018. As the SIG is ramping back up after the holiday break we had a few topics to kick off the new year and get the ball rolling. The SIG is working to complete our year in review report that

Re: [openstack-dev] [kolla] Re: About maridb 10.1 on kolla

W dniu 29.12.2017 o 07:58, Jeffrey Zhang pisze: > recently, a series patches about mariadb is pushed. Current issue is > > - using different mariadb binary from different repo ( from percona, > Mariadb official, linux distro ) > - using different version number of mariadb ( 10.0 and 10.1 ) > >

Re: [openstack-dev] [api] APIs schema consumption discussion

On 22/11/17 20:04, Graham Hayes wrote: > When I was talking to Gil about it, I suggested writing a new sphinx / > docutils formatter. I am not sure how feasible it would be, but it could > be possible (as sphinx has the whole page tree in memory when writing it > out, we may be able to output

Re: [openstack-dev] [QA] No QA meetings until next year

Dear all, The first QA meeting of the year will be next week. Andrea Frittoli On Wed, 20 Dec 2017, 3:56 pm Andrea Frittoli, wrote: > Dear all, > > due to the holiday season, there will be no QA meetings until 2018. > > Andrea Frittoli (andreaf) >

Re: [openstack-dev] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref

On 04/01/18 15:39, Stephen Finucane wrote: > I'm not sure what the procedure for this is but here goes. > > I've noticed that the 'os-api-ref' project seems to have its own group > of cores [1], many of whom are no longer working on OpenStack (at > least, not full-time), and has a handful of open

[openstack-dev] [os-api-ref][doc] Adding openstack-doc-core to os-api-ref

I'm not sure what the procedure for this is but here goes. I've noticed that the 'os-api-ref' project seems to have its own group of cores [1], many of whom are no longer working on OpenStack (at least, not full-time), and has a handful of open patches against it [2]. Since the doc team has

Re: [openstack-dev] [tripleo] containers-multinode is broken, what's our plan

This is a situation where having temprevert/pin/cherrypick functionality again would have been really helpful. I realize that doesn't help in the immediate circumstance, but it's something to consider for the future. On 01/02/2018 10:05 PM, Emilien Macchi wrote: Mistral broke us with

[openstack-dev] zuulv3 log structure and format grumblings

I've talked to a few people on the infra team about this but I'm not sure what is temporary and transitional and what is permanent and needs to be fixed, and how to fix it. The main issue is for newer jobs like tempest-full, the logs are under controller/logs/ and we lose the log analyze

Re: [openstack-dev] [oslo][oslo.log]Error will be occurred if watch_log_file option is true

Excerpts from Rikimaru Honjo's message of 2018-01-04 18:22:26 +0900: > Hello, > > The below bug was reported in Masakari's Launchpad. > I think that this bug was caused by oslo.log. > (And, the root cause is a bug of pyinotify using by oslo.log. The detail is > written in the bug report.) > > *

[openstack-dev] [qa] [api] [all] use gabbi and tempest with just YAML

(this is a request for assistance and verification) Back in July[1] I wrote about some experiments with using gabbi[2] with tempest. In that message I said: At some point it may be interesting to explore the option of "put a gabbit in dir X" and tempest will run it for you. I've

Re: [openstack-dev] [kolla] LXD driver in nova

There is a python nova-lxd binary (.deb) as part of Ubuntu OpenStack. To enable this a good place to start is James Page's blog: https://javacruft.wordpress.com/2017/09/01/openstack-pike-for-ubuntu-16-04-lts/ The cloud archive wiki page is also worth checking:

[openstack-dev] [watcher] January holidays

Hi Watcher team. I’m on vacation till January 9. Our next weekly meeting is scheduled on January 10, I’d be happy to see you all there:) Alex __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [kolla] LXD driver in nova

Hi João, It would be possible but there is not any container image with the nova-lxc code on it at the moment. (No binary rpm in RDO neither) Only supported drivers (for now) are: kvm, qemu, vmware and hyperv (xen in progress). Feel free to add lxd as driver into the project :) Regards

[openstack-dev] [kolla] LXD driver in nova

Hello! Is it possible to use the LXD driver for nova compute instead of the KVM? Kind regards, João __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [charms] evolving the ha interface type

Hi James, I like option 2 but I think there is a problem with it. I don't think the hacluster charm sets any data down the relation with the principle until it has first received data from the principle. As I understand it option 2 would change this behaviour so that hacluster immediately sets

[openstack-dev] [openstack-ansible] problems with bringing up openstack in AIO flavor with OVS

Hi OSA Experts, I'm trying to bring up openstack using openstack-ansible in AIO flavor by having neutron ml2 plugin set to ovs. OSA is being executed from OPNFV XCI deployer with attached openstack_user_config and user_variables*.yml files. I can see installation [1] is being successful, but

[openstack-dev] [qa] Office Hours Report 2018-01-04

Hello, Thanks everyone for attending QA office hour. Since It's the starting of the year so attendance is low. We managed to triaged some bugs opened/changed in last 14 days. The IRC report [0] and full log [1] are available through meetbot. **Bug Traiged Summary** * Bug #1740194 in devstack:

[openstack-dev] [oslo][oslo.log]Error will be occurred if watch_log_file option is true

Hello, The below bug was reported in Masakari's Launchpad. I think that this bug was caused by oslo.log. (And, the root cause is a bug of pyinotify using by oslo.log. The detail is written in the bug report.) * masakari-api failed to launch due to setting of watch_log_file and log_file

Re: [openstack-dev] [ironic-inspector] Resigning my core-reviewer duties

On 01/03/2018 04:24 PM, milanisko k wrote: Folks, as announced already on the Ironic upstream meeting, I'm hereby resigning my core-reviewer duties. I've changed my downstream occupation recently and I won't be able to keep up anymore. As I said many times, I'm really sad to hear it, but