Re: [openstack-dev] [nova] Should we delete the (unexposed) os-pci API?

On Mar 17, 2017, at 3:23 PM, Sean Dague wrote: >> So I move that we delete the (dead) code. Are there good reasons not to? > > Yes... with fire. > > Realistically this was about the pinnacle of the extensions on > extensions API changes, which is why we didn't even let it into

Re: [openstack-dev] [tripleo] introducing python-tripleo-helper

Gonéri, any update on this one? On Mon, Mar 6, 2017 at 2:28 PM, Emilien Macchi wrote: > On Fri, Feb 24, 2017 at 3:02 PM, Gonéri Le Bouder wrote: >> Hi all, >> >> TL/DR: >> >> - use Python to do drive TripleO deployment >> - RPM based >> - used to be a

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

On Fri, Mar 17, 2017, at 08:23 AM, Jordan Pittier wrote: > On Fri, Mar 17, 2017 at 3:11 PM, Sean Dague wrote: > > > On 03/17/2017 09:24 AM, Jordan Pittier wrote: > > > > > > > > > On Fri, Mar 17, 2017 at 1:58 PM, Sean Dague > > > wrote: >

Re: [openstack-dev] [lbaas][neutron] Is possible the lbaas commands are missing completely from openstack cli ?

Yes, as previously announced, we deferred development of the OpenStack Client (OSC) until Pike. Work has started on the OSC plugin for Octavia and we expect it to be available in Pike. Neutron CLI is deprecated which means it will go away in the future, but is still available for use and is still

Re: [openstack-dev] [nova] Should we delete the (unexposed) os-pci API?

On 03/17/2017 04:23 PM, Sean Dague wrote: On 03/17/2017 04:19 PM, Matt Riedemann wrote: I was working on writing a spec for a blueprint [1] that would have touched on the os-pci API [2] and got to documenting about how it's not even documented [3] when Alex pointed out that the API is not even

Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octa

On Fri, Mar 17, 2017 at 5:43 PM Sarabia, Solio wrote: > Hi. > > We’ve completed integrating manager.py into openstack/ironic. > > https://review.openstack.org/#/c/439252/ (include local copy) > > https://review.openstack.org/#/c/446844/ (prune local copy) > Thank you,

Re: [openstack-dev] [nova] Should we delete the (unexposed) os-pci API?

On 03/17/2017 04:19 PM, Matt Riedemann wrote: > I was working on writing a spec for a blueprint [1] that would have > touched on the os-pci API [2] and got to documenting about how it's not > even documented [3] when Alex pointed out that the API is not even > enabled [4][5]. > > It turns out

Re: [openstack-dev] [dib] diskimage-builder v2 RC1 release; request for test

Hello! Thanks for the bug report. Can you please file this as a bug? There is a very high probability that I introduced a change that leads to the failure [1] - even if this is fixed now there is a high probability that it will fail again when [2] is merged. The reason is, that there are no

[openstack-dev] [nova] Should we delete the (unexposed) os-pci API?

I was working on writing a spec for a blueprint [1] that would have touched on the os-pci API [2] and got to documenting about how it's not even documented [3] when Alex pointed out that the API is not even enabled [4][5]. It turns out that the os-pci API was added in the Nova V3 API and

Re: [openstack-dev] [all][ironic] Kubernetes-based long running processes

I've got a PS in progress for kolla-kubernetes to do keystone fernet token rolling too. Having a cluster aware cron job like function is really nice. From: Taryma, Joanna [joanna.tar...@intel.com] Sent: Friday, March 17, 2017 11:00 AM To: OpenStack

[openstack-dev] Third Bi-Annual Community Contributor Awards

Hello All! As we approach the Boston Summit and Forum we also approach another round of Community Contributor Awards (CCA's)! The nomination runs how through April 23rd. So please nominate those you look to for guidance, those that ask the challenging questions, those that don't get enough

Re: [openstack-dev] [dib] diskimage-builder v2 RC1 release; request for test

On Thu, Feb 9, 2017 at 12:22 AM, Ian Wienand wrote: > Hi > > diskimage-builder has been working on a feature/v2 branch > incorporating some largely internal changes to the way it finds and > calls elements, enhancements to partitioning and removal of some > long-deprecated

Re: [openstack-dev] [all][ironic] Kubernetes-based long running processes

Thank you for this explanation, Clint. Kuberentes gets more and more popular and it would be great if we could also take advantage of it. There are already projects in Openstack that have a mission that aligns with task scheduling, like Mistral, that could possibly support Kubernetes as a

Re: [openstack-dev] [QA][blazar][ceilometer][congress][intel-nfv-ci-tests][ironic][manila][networking-bgpvpn][networking-fortinet][networking-sfc][neutron][neutron-fwaas][neutron-lbaas][nova-lxd][octa

Hi. We’ve completed integrating manager.py into openstack/ironic. https://review.openstack.org/#/c/439252/ (include local copy) https://review.openstack.org/#/c/446844/ (prune local copy) -Solio From: Andrea Frittoli Reply-To: "OpenStack Development Mailing List (not

Re: [openstack-dev] [kolla][kolla-kubernetes][helm] global value inconsistent cause install result unpredicatable

Commented on the bug. From: Hung Chung Chih [lyanc...@gmail.com] Sent: Thursday, March 16, 2017 11:35 PM To: openstack-dev@lists.openstack.org Subject: [openstack-dev] [kolla][kolla-kubernetes][helm] global value inconsistent cause install result unpredicatable

Re: [openstack-dev] [lbaas][neutron] Is possible the lbaas commands are missing completely from openstack cli ?

On Fri, Mar 17, 2017 at 8:20 AM, Saverio Proto wrote: > Is LBaaS even going to be implemented in the unified openstack client ? No, it will be implemented as a separate OSC plugin. This is true for all of Neutron's "advanced services" projects. dt -- Dean Troyer

[openstack-dev] [nova] notification update week 11

Hi, Here is the status update / focus setting mail about notification work for week 11. Bugs [Medium] https://bugs.launchpad.net/nova/+bug/1657428 The instance notifications are sent with inconsistent timestamp format. Fix is ready for the cores to review

Re: [openstack-dev] [tc][appcat] The future of the App Catalog

On 13/03/17 17:20, Davanum Srinivas wrote: Zane, Sorry for the top post, Can you please submit a TC resolution? I can help with it as well. Let's test the waters. OK, here is a start: https://review.openstack.org/#/c/447031/ - ZB Thanks, Dims On Mon, Mar 13, 2017 at 5:10 PM, Zane Bitter

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

Well my crazy idea was the addition[10] of an extra argument(—men-trace) on the pbr binary creation. The idea is to be able to use it from any openstack binary and print those methods that are differences in the memory consumption[11]. Regards/Saludos Victor Morales irc: electrocucaracha

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

On Fri, Mar 17, 2017 at 3:11 PM, Sean Dague wrote: > On 03/17/2017 09:24 AM, Jordan Pittier wrote: > > > > > > On Fri, Mar 17, 2017 at 1:58 PM, Sean Dague > > wrote: > > > > On 03/17/2017 08:27 AM, Jordan Pittier wrote: > > > The

Re: [openstack-dev] [Openstack-operators] [nova] [neutron] Hooks for instance actions like creation, deletion

On 3/17/2017 9:13 AM, Matt Riedemann wrote: There is also dynamic vendordata v2 which was added in Newton: https://docs.openstack.org/developer/nova/vendordata.html We got feedback during the Pike PTG from some people, using hooks during instance create, that the dynamic vendordata serves

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

On 03/17/2017 09:24 AM, Jordan Pittier wrote: > > > On Fri, Mar 17, 2017 at 1:58 PM, Sean Dague > wrote: > > On 03/17/2017 08:27 AM, Jordan Pittier wrote: > > The patch that reduced the number of Tempest Scenarios we run in every > > job and

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

On 03/17/2017 09:39 AM, Andrea Frittoli wrote: > > > On Fri, Mar 17, 2017 at 1:03 PM Sean Dague > wrote: > > On 03/17/2017 08:27 AM, Jordan Pittier wrote: > > The patch that reduced the number of Tempest Scenarios we run in every > > job and

[openstack-dev] [deployment][tripleo] Next steps for configuration management in TripleO (and other tools?)

[adding deployment tag because it might be interesting for other tools since it would engage cross-project work] If you're not working on TripleO, feel free to comment on how your team plans to solve the problem (or don't), so we can maybe discuss and work together. Hey, Things are moving in

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

On Fri, Mar 17, 2017 at 1:03 PM Sean Dague wrote: > On 03/17/2017 08:27 AM, Jordan Pittier wrote: > > The patch that reduced the number of Tempest Scenarios we run in every > > job and also reduce the test run concurrency [0] was merged 13 days ago. > > Since, the situation (i.e

Re: [openstack-dev] [lbaas][neutron] Is possible the lbaas commands are missing completely from openstack cli ?

Hey Saverio, 2017-03-17 8:20 GMT-05:00 Saverio Proto : > Client version: openstack 3.9.0 > > I cant find any lbaas commands. I have to use the 'neutron' client. It's highly possible, that LBaaS commands are not in OSC. > > Everycommand I get: > neutron CLI is deprecated

[openstack-dev] [keystone] [horizon] Keystone-Horizon meeting on 2017-03-23 cancelled

Hey everyone, I'm away next week, so the Keystone-Horizon meeting on the 23rd is cancelled Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe:

Re: [openstack-dev] [all][deployment] Deployment Working Group (DWG)

On Thu, Mar 16, 2017 at 12:59 PM, Jeremy Stanley wrote: > On 2017-03-16 11:42:25 -0500 (-0500), Devdatta Kulkarni wrote: > [...] >> Related to the work that would be produced by the group, what is >> the thought around where would deployment artifacts live? Within >> each

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

On Fri, Mar 17, 2017 at 1:58 PM, Sean Dague wrote: > On 03/17/2017 08:27 AM, Jordan Pittier wrote: > > The patch that reduced the number of Tempest Scenarios we run in every > > job and also reduce the test run concurrency [0] was merged 13 days ago. > > Since, the situation (i.e

[openstack-dev] [lbaas][neutron] Is possible the lbaas commands are missing completely from openstack cli ?

Client version: openstack 3.9.0 I cant find any lbaas commands. I have to use the 'neutron' client. Everycommand I get: neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead. Is LBaaS even going to be implemented in the unified openstack client ? thank you

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

On 03/17/2017 08:45 AM, Ihar Hrachyshka wrote: > I had some patches to collect more stats about mlocks > here: https://review.openstack.org/#/q/topic:collect-mlock-stats-in-gate > but they need reviews. Done, sorry I hadn't seen those earlier. -- Sean Dague http://dague.net

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

On 03/17/2017 08:27 AM, Jordan Pittier wrote: > The patch that reduced the number of Tempest Scenarios we run in every > job and also reduce the test run concurrency [0] was merged 13 days ago. > Since, the situation (i.e the high number of false negative job results) > has not improved

[openstack-dev] [nova] placement/resource providers update 15

This week in resource providers and placement the main news is we've made a change in priorities, see "What's Changed" below. If this update seems more terse or more riddled with errors than usual, I blame the great scheduler in the sky placing a virus upon me that is messing with my savoir

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

I had some patches to collect more stats about mlocks here: https://review.openstack.org/#/q/topic:collect-mlock-stats-in-gate but they need reviews. Ihar On Fri, Mar 17, 2017 at 5:28 AM Jordan Pittier wrote: > The patch that reduced the number of Tempest Scenarios

Re: [openstack-dev] [QA][gate][all] dsvm gate stability and scenario tests

The patch that reduced the number of Tempest Scenarios we run in every job and also reduce the test run concurrency [0] was merged 13 days ago. Since, the situation (i.e the high number of false negative job results) has not improved significantly. We need to keep looking collectively at this.

Re: [openstack-dev] [keystone][all] Reseller - do we need it?

Yes, that was indeed the model originally proposed (some referred to it as “nested domains”). Back then we didn’t have project hierarchy support in keystone (actually the two requirements emerged together and intertwined - and for a while there was a joint spec). Today, there are some

Re: [openstack-dev] [neutron][lbaasv2] Migrate LBaaS instance

Hello there, I am just back from the Ops Midcycle where Heidi Joy Tretheway reported some data from the user survey. So if we look at deployments with more than 100 servers NO ONE IS USING NEWTON yet. And I scream this loud. Everyone is still in Liberty or Mitaka. I am just struggling to

Re: [openstack-dev] [all][deployment] Deployment Working Group (DWG)

+1 and big thanks for bringing this up! OpenStack Chef will most likely use Ansible as an orchestrator for multi node deployments in the near future and i love the idea about sharing “common configuration options”. Cheers, Jan On 14 March 2017 at 21:39:19, Emilien Macchi (emil...@redhat.com)

Re: [openstack-dev] [keystone][all] Reseller - do we need it?

This actually sounds a lot like a domain per reseller, with a sub-domain per reseller customer. With the reseller themselves probably also running a sub-domain or two for themselves. Mayb even running their own external federated user system for that specific reseller domain.That or something like

[openstack-dev] [all] [quotas] Unified Limits Conceptual Spec RFC

Background: At the Atlanta PTG there was yet another attempt to get hierarchical quotas more generally addressed in OpenStack. A proposal was put forward that considered storing the limit information in Keystone (https://review.openstack.org/#/c/363765/). While there were some concerns on details

[openstack-dev] [kolla][fuel-ccp][openstack-helm][magnum][all] Deliverables of OpenStack projects for container runtimes

Team, I am asking some questions here: https://etherpad.openstack.org/p/single-approach-to-containers-for-projects Main question is, Is it time to collaborate across teams? Please add your name on top with the color you are using so it's easy to track who said what. Thanks, Dims -- Davanum

[openstack-dev] [horizon] No meeting on 2017-03-22 (next week)

Hey everyone, I'm away for a week, so there'll be no Horizon meeting on the 22nd. Rob __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe

[openstack-dev] [release] Release countdown for week R-23 and R-22, March 20-31

Welcome back to our regular release countdown email. This one will serve both for the R-23 and R-22 weeks. Development Focus - Teams should be working on specs approval and implementation for priority features for this cycle. Actions --- All project teams should be

Re: [openstack-dev] [keystone][all] Reseller - do we need it?

OK, so I worked on the original spec for this in Keystone, based around real world requirements we (IBM) saw. For the record, here’s the particular goal we wanted to achieve: 1) A cloud owner (i.e. the enterprise owns and maintains the core of the cloud), wants to attract more traffic by

Re: [openstack-dev] [nova][vmware] CI results show up about a week late, if at all

Yes unfortunately I am aware of it and we are struggling to correct it. We recently have some new infrastructure that we can add to help with this. I have a meeting early next week with the team to make this available and I hope for a quickish resolution. I’ll update you here with the plan.

[openstack-dev] [kolla][kolla-kubernetes][helm] global value inconsistent cause install result unpredicatable

Hi all, This is my first time to send mailing list, if I had made mistake please tell me, thank you. When I try to helm install keystone service, I found it can installed succeeded but sometimes will failed with unexpected nil value for field spec.externalIPs[0]. Then I report bug at launchpad

Re: [openstack-dev] [keystone][all] Reseller - do we need it?

Lance, I had understood that the resellers was about having users/groups at the different points in the tree. I think the basic resource management is being looked at as part of the nested quotas functionality. For CERN, we’d look to delegate the quota and roles management but not support

Re: [openstack-dev] [dib][heat] dib-utils/dib-run-parts/dib v2 concern

On 03/17/2017 03:46 AM, Steven Hardy wrote: > (undercloud) [stack@undercloud ~]$ rpm -qf /usr/bin/dib-run-parts > dib-utils-0.0.11-1.el7.noarch > (undercloud) [stack@undercloud ~]$ rpm -qf /bin/dib-run-parts > dib-utils-0.0.11-1.el7.noarch /bin is a link to /usr/bin? So I think this is the same