[openstack-dev] [tripleo] improving logs / config path in oooq-container jobs

By reviewing https://review.openstack.org/#/c/447176 which is solving an urgent issue in Infra to save space in logs server, I found out that container jobs store config and logs in paths that are not easy to find by newcomers. Example: http://logs.openstack.org/76/447176/4/check-tripleo/gate-tri

[openstack-dev] [publiccloud-wg] Reminder meeting PublicCloudWorkingGroup

Hi everyone, Don't forget todays meeting for the PublicCloudWorkingGroup. 1400 UTC in IRC channel #openstack-meeting-3 Etherpad: https://etherpad.openstack.org/p/publiccloud-wg Focus will be to set the goals for the current cycle! Talk to you this afternoon! Tobias tob...@citynetwork.se sm

[openstack-dev] [neutron] pep8 broken

Hi, It seems that the pep8 is broken due to https://github.com/openstack/requirements/commit/99fae827973465147359cc7032c83003802612a7 Should we revert this? Thanks Gary __ OpenStack Development Mailing List (not for usage ques

Re: [openstack-dev] [neutron] pep8 broken

I think this was meant to fix it. https://review.openstack.org/#/c/471512/ On Wed, Jun 7, 2017 at 4:51 AM, Gary Kotton wrote: > Hi, > > It seems that the pep8 is broken due to https://github.com/openstack/ > requirements/commit/99fae827973465147359cc7032c83003802612a7 > > Should we revert this?

Re: [openstack-dev] [neutron] pep8 broken

Thanks! Maybe this is the source of the failures that we are seeing now and we need to address that in the decomposed projects. From: Kevin Benton Reply-To: OpenStack List Date: Wednesday, June 7, 2017 at 11:59 AM To: OpenStack List Subject: Re: [openstack-dev] [neutron] pep8 broken I think

Re: [openstack-dev] [nova][out-of-tree drivers] InstanceInfo/get_info getting a haircut

Thanks for posting this, we do have an out-of-tree driver ,and as you pointed out in the patch , those parameters seems not used and this change didn't modify the compute layer functions and params so it should be no impact Best Regards! Kevin (Chen) Ji 纪 晨 Engineer, zVM Development, CSTL Notes:

[openstack-dev] [watcher] migration to storyboard

Hi Watcher folks, On the previous meeting we have decided to take a look at Storyboard and to decide if we want to migrate from Launchpad. It would be great if you take a look at it and give your opinion on today meeting [1] https://storyboard.openstack.org/ Thanks a lot! Alex ___

Re: [openstack-dev] [neutron] pep8 broken

Seems like the whole world is broken now: 2017-06-07 09:56:23.336255 | pep8 runtests: PYTHONHASHSEED='681905263' 2017-06-07 09:56:23.336291

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On 06.06.2017 18:08, Emilien Macchi wrote: > Following-up the session that we had in Boston: > https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management > > Here's an update on where we are and what is being done. > > > == Machine Readable Sample Config > > Ben's spec has be

[openstack-dev] [tripleo] [ci] Adding idempotency job on overcloud deployment.

Hi, I don't think we have such a job in place. Basically that would check that re-running the "openstack deploy ..." command won't do anything. We had such an error by the past[1], but I'm not sure this has been captured by an associated job. WDYT ? [1] https://bugs.launchpad.net/tripleo/+bug/

[openstack-dev] [all] etcd3 as base service - update

Team, Here's the update to the base services resolution from the TC: https://governance.openstack.org/tc/reference/base-services.html First request is to Distros, Packagers, Deployers, anyone who installs/configures OpenStack: Please make sure you have latest etcd 3.x available in your environmen

Re: [openstack-dev] [tripleo] [ci] Adding idempotency job on overcloud deployment.

On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot wrote: > Hi, > > I don't think we have such a job in place. Basically that would check > that re-running the "openstack deploy ..." command won't do anything. > > We had such an error by the past[1], but I'm not sure this has been > captured by

Re: [openstack-dev] [neutron] pep8 broken

Sorry my bad. The problem is that our requirements use six and in 1.10 files are missing From: Gary Kotton Reply-To: OpenStack List Date: Wednesday, June 7, 2017 at 1:00 PM To: OpenStack List Subject: Re: [openstack-dev] [neutron] pep8 broken Seems like the whole world is broken now: 2017-06

Re: [openstack-dev] [neutron] pep8 broken

Hi, More details: The urllib, urllib2, and urlparse modules have been combined in the urllib

[openstack-dev] [horizon] seeing another users panel in Mitaka ?

Has anyone seen the following behavior / issue ? I am using Mitaka. Sometimes ... with many users using the OpenStack installation, I can be logged into Horizon as User-A/Tenant-A, on the Compute-->Instances panel showing my running instances. and then For a few seconds (~3-4 seconds), my panel w

Re: [openstack-dev] [tripleo] [ci] Adding idempotency job on overcloud deployment.

Hi, Emilien Macchi writes: > On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot > wrote: >> Hi, >> >> I don't think we have such a job in place. Basically that would check >> that re-running the "openstack deploy ..." command won't do anything. >> >> We had such an error by the past[1], but

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Tue, Jun 6, 2017 at 6:08 PM, Emilien Macchi wrote: > Following-up the session that we had in Boston: > https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management > > Here's an update on where we are and what is being done. > > > == Machine Readable Sample Config > > Ben's spe

[openstack-dev] [neutron] pep8 breakage

Hi, Please see bug https://bugs.launchpad.net/neutron/+bug/1696403. Seems like six 1.10.0 has broken us. I have posted a patch in the requirements project. Not 100% sure that this is the right way to go. At least that will enable us to address this in neutron. Thanks Gary

Re: [openstack-dev] [neutron] pep8 breakage

Six 1.10.0 is not the root cause. The root cause is the version bump of pylint (and astroid). Regarding pylint and astroid, I think the issue will go once https://review.openstack.org/#/c/469491/ is merged. However, even after the global requirement is merged, neutron pylint will fail because pylin

Re: [openstack-dev] [tripleo] [ci] Adding idempotency job on overcloud deployment.

On Wed, Jun 7, 2017 at 1:20 PM, Sofer Athlan-Guyot wrote: > Hi, > > Emilien Macchi writes: > >> On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot >> wrote: >>> Hi, >>> >>> I don't think we have such a job in place. Basically that would check >>> that re-running the "openstack deploy ..." com

Re: [openstack-dev] [nova] allow vfs to be trusted

On Fri, Apr 28, 2017 at 10:52:47AM +0200, Sahid Orentino Ferdjaoui wrote: > Hello Matt, > > There is a serie of patches pushed upstream [0] to configure virtual > functions of a SRIOV device to be "trusted". > > That is to fix an issue when bonding two SRIOV nics in failover mode, > basically wit

Re: [openstack-dev] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

> On Jun 7, 2017, at 7:20 AM, Emilien Macchi wrote: > > On Tue, Jun 6, 2017 at 6:08 PM, Emilien Macchi > wrote: >> Following-up the session that we had in Boston: >> https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management >> >> Here's an update

[openstack-dev] [nova] bug/1686116 - using more than 6 scsi disks with virtio-scsi

Hello, We have an issue in Nova which makes no possible to configure more than 6 SCSI disks with virtio-scsi where the controller could handle up to 256 disks. The fix has been reviewed by Stephen Finucane (thanks to him) and some other contributors (thanks to them), any chance to get one core to

Re: [openstack-dev] [tc] [all] TC Report 23

On 06/06/2017 09:52 PM, Matt Riedemann wrote: On 6/6/2017 5:10 PM, Chris Dent wrote: This week had a scheduled TC meeting for the express purpose of discussing what to do about PostgreSQL. The remainder of this document has notes from that meeting. Just wanted to say thanks for the nice summar

[openstack-dev] [acceleration]Cyborg Team Weekly Meeting 2017.06.07

Hi Team, Kind reminder for our regular weekly meeting today about one hour later on #openstack-cyborg. We will continue to discuss the open spec patches, as well as the initial code developments. -- Zhipeng (Howard) Huang Standard Engineer IT Standard & Patent/IT Product Line Huawei Technologi

[openstack-dev] [tripleo] Ansible roles repo and how to inject them into the overcloud

Hi folks! I would like to know if there are thoughts about where to put tripleo-specific ansible roles. I've been working lately on a role that would deploy ipsec tunnels for most networks in an overcloud [1]. And I think that would be quite useful for folks as an alternative to TLS everywhere. H

Re: [openstack-dev] [EXTERNAL] Re: [Tripleo] deploy software on Openstack controller on the Overcloud

Hi, On cinder node- we need to modify the cinder.conf. We don’t change any config apart from this. We want to keep the config changes in heat template, package installation in puppet, and trigger rest of the operations via Horizon (as it’s done today). We are also trying to get rid of the nova.

Re: [openstack-dev] [Openstack-operators] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

On Wed, Jun 7, 2017 at 3:31 PM, Doug Hellmann wrote: > > On Jun 7, 2017, at 7:20 AM, Emilien Macchi wrote: > > On Tue, Jun 6, 2017 at 6:08 PM, Emilien Macchi wrote: > > Following-up the session that we had in Boston: > https://etherpad.openstack.org/p/BOS-forum-future-of-configuration-management

Re: [openstack-dev] [tripleo] [ci] Adding idempotency job on overcloud deployment.

On Wed, Jun 7, 2017 at 5:20 AM, Sofer Athlan-Guyot wrote: > Hi, > > Emilien Macchi writes: > >> On Wed, Jun 7, 2017 at 12:45 PM, Sofer Athlan-Guyot >> wrote: >>> Hi, >>> >>> I don't think we have such a job in place. Basically that would check >>> that re-running the "openstack deploy ..." com

Re: [openstack-dev] [cinder] [nova] How to provide additional options to NFS backend?

V Wed, 31 May 2017 11:34:20 -0400 Eric Harney napsáno: > On 05/25/2017 05:51 AM, Jiri Suchomel wrote: > > Hi, > > it seems to me that the way of adding extra NFS options to the > > cinder backend is somewhat confusing. > > > > 1. There is nfs_mount_options in cinder config file [1] > > > > 2.

[openstack-dev] [nova] How to move on from live_migration_uri?

The [libvirt]/live_migration_uri config option was deprecated in Ocata [1] in favor of two other config options: live_migration_scheme: defaults to tcp (could be ssh), only used for kvm/qemu virt types live_migration_inbound_addr: defaults to None, only used if doing a non-tunneled live migr

Re: [openstack-dev] [horizon] seeing another users panel in Mitaka ?

This isn’t ringing any bells. Do you have any logs you could share? Rob On 7 Jun 2017, at 12:15, Waines, Greg mailto:greg.wai...@windriver.com>> wrote: Has anyone seen the following behavior / issue ? I am using Mitaka. Sometimes ... with many users using the OpenStack installation, I can be l

Re: [openstack-dev] [nova] allow vfs to be trusted

On 6/7/2017 8:28 AM, Sahid Orentino Ferdjaoui wrote: I still have a question do I need to provide a spec for this? There is a spec for it: https://review.openstack.org/#/c/397932/ So why not just revive that for Queens? Specs also serve as documentation of a feature. Release notes are not a

Re: [openstack-dev] [nova][vlan trunking] Guest networking configuration for vlan trunk

Hi Bence, Thanks for the pointers. I was aware of this https://bugs.launchpad.net/neutron/+bug/1631371, but not the blueprint you wrote. As suggested by Matt in https://bugs.launchpad.net/nova/+bug/1693535, I wrote a blueprint https://blueprints.launchpad.net/nova/+spec/expose-vlan-trunking,

[openstack-dev] [I18n] Inviting to Zanata (translation platform) webinar: June 8th at 13:00 UTC

Hello, I am organizing a webinar by inviting Zanata (OpenStack translation platform) development team as an invited speaker and seeing #openstack-meeting IRC channel for questions and answers on tomorrow (June 8th) 13:00 UTC. I would like to invite to all who are interested in OpenStack tran

Re: [openstack-dev] [nova] allow vfs to be trusted

On Wed, Jun 07, 2017 at 11:23:23AM -0500, Matt Riedemann wrote: > On 6/7/2017 8:28 AM, Sahid Orentino Ferdjaoui wrote: > > I still have a question do > > I need to provide a spec for this? > > There is a spec for it: > > https://review.openstack.org/#/c/397932/ > > So why not just revive that fo

Re: [openstack-dev] [nova] How to move on from live_migration_uri?

On Wed, 2017-06-07 at 10:20 -0500, Matt Riedemann wrote: > The [libvirt]/live_migration_uri config option was deprecated in Ocata  > [1] in favor of two other config options: > > live_migration_scheme: defaults to tcp (could be ssh), only used for  > kvm/qemu virt types > > live_migration_inbound

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Jun 6, 2017, at 9:56 AM, Chris Dent wrote: > > For clarity and completeness in the discussion some questions for > which we have explicit answers would be useful. Some of these may > appear ignorant or obtuse and are mostly things we've been over > before. The goal is to draw out some clear st

[openstack-dev] [searchlight] Cancelling IRC meeting June 8th

Hi, I won't be around tomorrow so I'm cancelling the searchlight IRC meeting. We'll resume next week and apologies for the short notice. Steve __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: open

Re: [openstack-dev] [trove] Trove reboot meeting

From the last call (see original message below), and in the trove meeting today[1]. We agreed to hosting another trove reboot meeting tomorrow, June 8th, at 1500 UTC. The meeting will be announced in the same fashion, as an impromptu hangout session. I will post the link to join on the mailing

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On 06/07/2017 01:00 PM, Edward Leafe wrote: On Jun 6, 2017, at 9:56 AM, Chris Dent mailto:cdent...@anticdent.org>> wrote: For clarity and completeness in the discussion some questions for which we have explicit answers would be useful. Some of these may appear ignorant or obtuse and are mostly

Re: [openstack-dev] [nova] bug/1686116 - using more than 6 scsi disks with virtio-scsi

I'm on it. On 06/07/2017 09:42 AM, Sahid Orentino Ferdjaoui wrote: Hello, We have an issue in Nova which makes no possible to configure more than 6 SCSI disks with virtio-scsi where the controller could handle up to 256 disks. The fix has been reviewed by Stephen Finucane (thanks to him) and s

Re: [openstack-dev] [neutron] pep8 breakage

UPD: in case you wonder if that's fixed, we are waiting for https://review.openstack.org/#/c/471763/ to land. Ihar On 06/07/2017 05:23 AM, Akihiro Motoki wrote: Six 1.10.0 is not the root cause. The root cause is the version bump of pylint (and astroid). Regarding pylint and astroid, I think

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

> -Original Message- > From: Jay Pipes [mailto:jaypi...@gmail.com] > Sent: Wednesday, June 7, 2017 6:47 PM > To: openstack-dev@lists.openstack.org > Subject: Re: [openstack-dev] [nova][scheduler][placement] Allocating > Complex Resources > > On 06/07/2017 01:00 PM, Edward Leafe wrote: >

Re: [openstack-dev] [Openstack-operators] [deployment] [oslo] [ansible] [tripleo] [kolla] [helm] Configuration management with etcd / confd

Excerpts from Emilien Macchi's message of 2017-06-07 16:42:13 +0200: > On Wed, Jun 7, 2017 at 3:31 PM, Doug Hellmann wrote: >> >> On Jun 7, 2017, at 7:20 AM, Emilien Macchi wrote: >> >> On Tue, Jun 6, 2017 at 6:08 PM, Emilien Macchi wrote: >> >> Following-up the session that we had in Boston:

[openstack-dev] Queens Project Teams Gathering- Denver September 11-15th

The second Project Teams Gathering will be held September 11-15th at the Renaissance Hotel

Re: [openstack-dev] [all] etcd3 as base service - update

One clarification: Since https://pypi.python.org/pypi/etcd3gw just uses the HTTP API (/v3alpha) it will work under both eventlet and non-eventlet environments. Thanks, Dims On Wed, Jun 7, 2017 at 6:47 AM, Davanum Srinivas wrote: > Team, > > Here's the update to the base services resolution from

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Jun 7, 2017, at 1:44 PM, Mooney, Sean K mailto:sean.k.moo...@intel.com>> wrote: > [Mooney, Sean K] neutron will need to use nested resource providers to track > Network backend specific consumable resources in the future also. One example > is > is hardware offloaded virtual(e.g. vitio/vhost-u

Re: [openstack-dev] [nova][scheduler][placement] Allocating Complex Resources

On Jun 7, 2017, at 1:44 PM, Mooney, Sean K mailto:sean.k.moo...@intel.com>> wrote: > [Mooney, Sean K] neutron will need to use nested resource providers to track > Network backend specific consumable resources in the future also. One example > is > is hardware offloaded virtual(e.g. vitio/vhost-u

Re: [openstack-dev] [forum] Future of Stackalytics

2017-05-17 11:55 GMT-07:00 Jeremy Stanley : > On 2017-05-17 16:16:30 +0200 (+0200), Thierry Carrez wrote: > [...] >> we need help with completing the migration to infra. If interested >> you can reach out to fungi (Infra team PTL) nor mrmartin (who >> currently helps with the transition work). > [.

[openstack-dev] [oslo.messaging]Optimize RPC performance by reusing callback queue

Hi, Currently, I find our RPC client always need create a new callback queue for every call requests to track the reply belongs, at least in Newton. That's pretty inefficient and lead to poor performance. I also find some RPC implementations no need to create a new queue, they track the request a

[openstack-dev] [Nova] Deprecating localfs?

Greetings from an ancient thread (but the most recent on to openstack-dev about localfs that I can find). In 2014, which were heady times, we decided that we couldn't deprecate nova.virt.disk.vfs.localfs because we theorised that FreeBSD and containers would soon need it. Oh, and xenapi uses it a

Re: [openstack-dev] [all] etcd3 as base service - update

So just out of curiosity, but do people really even know what etcd is good for? I am thinking that there should be some guidance from folks in the community as to where etcd should be used and where it shouldn't (otherwise we just all end up in a mess). Perhaps a good idea to actually give exa

[openstack-dev] [telemetry][ceilometer][gnocchi] Query on adding new meters to Gnocchi

Hi, I am trying to add new meters/resource types in gnocchi. I came across 2 files: Gnocchi_resources.yaml and ceilometer_update script which will make Gnocchi api calls for resource_type addition. I have a few queries. Could you please clarify them. 1. Is it sufficient to add the resource t

Re: [openstack-dev] [forum] Future of Stackalytics

I wish I'd made it to that Forum session, but here's my two cents now: As a core reviewer for LBaaS I actually find Stackalytics quite helpful for giving me a quick snapshot of contributions, and it lines up almost perfectly in my experience with what I see when I'm actually reviewing and working

Re: [openstack-dev] [oslo.messaging]Optimize RPC performance by reusing callback queue

Hi, First of all, the correlation_id is needed for tracking the response for callback queue per client. What you said is the inefficiency of callback queue per request. In any case, callback queue is needed. About oslo_messaging, you can see the correlation_id in the driver of amqp. Br, Tuan/No