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

On 03/06/2017 06:26 AM, Thierry Carrez wrote: Hello everyone, The App Catalog was created early 2015 as a marketplace of pre-packaged applications that you can deploy using Murano. Initially a demo by Mirantis, it was converted into an open upstream project team, and deployed as a "beta" as

[openstack-dev] [cinder][glance][horizon][keystone][nova][qa][swift] Feedback needed: Removal of legacy per-project vanity domain redirects

Hey all, We have a set of old vanity redirect URLs from back when we made a URL for each project: cinder.openstack.org glance.openstack.org horizon.openstack.org keystone.openstack.org nova.openstack.org qa.openstack.org swift.openstack.org They are being served from an old server we'd like to

Re: [openstack-dev] [nova][placement-api] Is there any document about openstack-placement-api for installation and configure?

On Wed, 8 Mar 2017, Yu Wei wrote: When I tried to configure placement-api, I met following problems, AH01630: client denied by server configuration: /usr/bin/nova-placement-api That can be fixed by doing (somewhere in your apache config): Require all granted but rather

Re: [openstack-dev] [nova][placement-api] Is there any document about openstack-placement-api for installation and configure?

On Wed, 8 Mar 2017, Yu Wei wrote: I'm new to openstack. I tried to install openstack-ocata. As placement-api is required since Ocata, is there any detailed document about how to install and configure placement-api? There are two different things which might be useful to you. Some nova

[openstack-dev] [ironic] Pike PTG report

Hi all! I've finished my Pike PTG report. It is spread over four blog posts: http://dtantsur.github.io/posts/ironic-ptg-atlanta-2017-1.html http://dtantsur.github.io/posts/ironic-ptg-atlanta-2017-2.html http://dtantsur.github.io/posts/ironic-ptg-atlanta-2017-3.html

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

The App Catalog, to me, sounds sort of like a weird message that OpenStack somehow requires applications to be packaged/installed/deployed differently. If anything, perhaps we should spend more effort on advertising that OpenStack provides bare metal or virtual compute resources and that apps will

Re: [openstack-dev] [oslo] question about oslo_utils and oslo_versonedobjects

I'm contributing on Karbor (https://wiki.openstack.org/wiki/Karbor). Recently, I find a bug in the following codes. def resume_operation(self, operation_id, **kwargs): end_time = kwargs.get('end_time_for_run') now = datetime.utcnow() if not isinstance(end_time, datetime) or now >

Re: [openstack-dev] [Neutron] ImportError: No module named neutron_lib

I found this: from oslo_config import ... from oslo_db import ... from neutron_lib import ... actually these libraries is oslo.config, oslo.db, neutron.lib Why not write like this: from oslo.config import ... ? And for local package, its: from neutron.api import ... WHY ? 2017-03-08 5:28

Re: [openstack-dev] [oslo] question about oslo_utils and oslo_versonedobjects

On 03/08/2017 09:07 PM, zengchen wrote: Hi, jay Thanks for your reply. Do you means it is no need to do that optimization? In my opinion, It is better if do some change. Thanks again. I'm not quite following you. I don't believe there's any need to change anything nor any need to optimize

Re: [openstack-dev] [QA] Meeting Thursday Mar 9th at 9:00 UTC

Thanks Luz, We will discuss the same in today meeting. Saw your report on etherpad too. -gmann On Thu, Mar 9, 2017 at 7:22 AM, Cazares, Luz wrote: > Hey gmann > > > > I did bug triage last weeks (27th Feb – 3rd March). > > > > So far 7 new bugs arrived: > > 3 confirmed

Re: [openstack-dev] [Neutron] ImportError: No module named neutron_lib

Sorry, it's oslo_db, I'm wrong 2017-03-09 14:22 GMT+08:00 Sam : > I found this: > > from oslo_config import ... > from oslo_db import ... > from neutron_lib import ... > > actually these libraries is oslo.config, oslo.db, neutron.lib > > Why not write like this: from

Re: [openstack-dev] [oslo] question about oslo_utils and oslo_versonedobjects

Hi, jayThanks for your reply. Do you means it is no need to do that optimization?In my opinion, It is better if do some change. Thanks again. Best Wishes zeng chen At 2017-03-08 00:57:51, "Jay Pipes" wrote: >On 03/07/2017 01:34 AM, zengchen wrote: >> Hi, guys: >>

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

On 03/08/2017 05:38 PM, Amrith Kumar wrote: > Sounds like a good candidate for a cross-project release goal. > > A non-controversial situation, the work is a no-op for most, a specific > deliverable for a few, and a mechanism to close the loop and make sure it > gets done in a specific timeframe?

Re: [openstack-dev] [neutron] [infra] Depends-on tag effect

Hi, iiuc, neutron uses a released version of neutron-lib not neutron-lib master ... So the change should depends on a change in requirements repo incrementing neutron-lib version On Wed, Mar 8, 2017 at 3:16 PM, Hirofumi Ichihara < ichihara.hirof...@lab.ntt.co.jp> wrote: > Hi, > > I thought that

Re: [openstack-dev] [cinder][glance][horizon][keystone][nova][qa][swift] Feedback needed: Removal of legacy per-project vanity domain redirects

On Wed, Mar 08, 2017 at 09:12:59AM -0600, Monty Taylor wrote: > Hey all, > > We have a set of old vanity redirect URLs from back when we made a URL > for each project: > > cinder.openstack.org > glance.openstack.org > horizon.openstack.org > keystone.openstack.org > nova.openstack.org >

Re: [openstack-dev] [kolla] Proposing duonghq for core

+1 From: Mauricio Lima > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > Date: Wednesday, March 8, 2017 at 5:34 AM To: "OpenStack

Re: [openstack-dev] [infra][tripleo] initial discussion for a new periodic pipeline

On 2017-03-07 10:12:58 -0500 (-0500), Wesley Hayutin wrote: > The TripleO team would like to initiate a conversation about the > possibility of creating a new pipeline in Openstack Infra to allow > a set of jobs to run periodically every four hours [...] The request doesn't strike me as

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

Import path looks OK https://github.com/openstack/networking-sfc/blob/master/networking_sfc/services/sfc/agent/extensions/openvswitch/sfc_driver.py#L23 Are u suggesting something else? On Thu, Mar 9, 2017 at 3:02 AM, Kevin Benton wrote: > That location was recently changed

[openstack-dev] [magnum] [ocata] after installation, magnum is not found

Hi guys, After installing openstack ocata magnum, magnum is not found. However, magnum-api and magnum-conduct are running well. How could I fix such problem? Is this bug in ocata? [root@controller bin]# systemctl status openstack-magnum-api.service openstack-magnum-conductor.service ●

Re: [openstack-dev] [TripleO][Heat] Selectively disabling deployment resources

On Wed, Mar 8, 2017 at 4:08 AM, Steven Hardy wrote: > On Tue, Mar 07, 2017 at 02:34:50PM -0500, James Slagle wrote: >> I've been working on this spec for TripleO: >> https://review.openstack.org/#/c/431745/ >> >> which allows users to selectively disable Heat deployment

[openstack-dev] [kolla] kolla-ansible 4.0.0.0rc2 (ocata)

Hello everyone, A new release candidate for kolla-ansible for the end of the Ocata cycle is available! You can find the source code tarball at: https://tarballs.openstack.org/kolla-ansible/ Unless release-critical issues are found that warrant a release candidate respin, this candidate

Re: [openstack-dev] [cinder][glance][horizon][keystone][nova][qa][swift] Feedback needed: Removal of legacy per-project vanity domain redirects

On Wed, Mar 8, 2017 at 2:04 PM, Andreas Jaeger wrote: > > Very few people know about these URLs at all and there are only a few > places that use it in openstack (I just send a few patches for those). > ++ I had no idea they existed...

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

One of my goals for Barbican for this cycle is to migrate our code to use pyca/cryptography exclusively. We currently depend on both because at one point we needed things that were not available in early releases of cryptography. - Douglas Mendizábal (redrobot) > On Mar 8, 2017, at 1:11 PM,

Re: [openstack-dev] [cinder][glance][horizon][keystone][nova][qa][swift] Feedback needed: Removal of legacy per-project vanity domain redirects

On 8 Mar 2017, at 11:04, Andreas Jaeger wrote: > On 2017-03-08 17:23, Brian Rosmaita wrote: >> On 3/8/17 10:12 AM, Monty Taylor wrote: >>> Hey all, >>> >>> We have a set of old vanity redirect URLs from back when we made a URL >>> for each project: >>> >>> cinder.openstack.org >>>

Re: [openstack-dev] [kolla] Proposing duonghq for core

+1! -Original Message- From: Michał Jastrzębski Reply-To: "OpenStack Development Mailing List (not for usage questions)" Date: Wednesday, March 8, 2017 at 1:41 AM To: "OpenStack Development Mailing List (not for usage questions)"

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

I'm aware, iirc it was brought up when pysaml2 had to be fixed due to a CVE. This thread is more looking for a long term fix. On 03/08/2017 01:11 PM, Davanum Srinivas wrote: > Matthew, > > Please see the last time i took inventory: > https://review.openstack.org/#/q/pycryptodome+owner:dims-v >

Re: [openstack-dev] [cinder][glance][horizon][keystone][nova][qa][swift] Feedback needed: Removal of legacy per-project vanity domain redirects

On 03/08/2017 10:31 AM, Daniel P. Berrange wrote: > On Wed, Mar 08, 2017 at 09:12:59AM -0600, Monty Taylor wrote: >> Hey all, >> >> We have a set of old vanity redirect URLs from back when we made a URL >> for each project: >> >> cinder.openstack.org >> glance.openstack.org >>

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

Ack thanks Matthew! On Wed, Mar 8, 2017 at 2:24 PM, Matthew Thode wrote: > I'm aware, iirc it was brought up when pysaml2 had to be fixed due to a > CVE. This thread is more looking for a long term fix. > > On 03/08/2017 01:11 PM, Davanum Srinivas wrote: >> Matthew,

Re: [openstack-dev] [networking-sfc] patch test failed due to "import error: vlanmanager"

That location was recently changed in the Neutron side.[1] It sounds like sfc has to be updated. 1. https://github.com/openstack/neutron/commit/4ec456d31501f09c68b5c23c488878da32dce75e On Tue, Mar 7, 2017 at 9:41 PM, Vikash Kumar < vikash.ku...@oneconvergence.com> wrote: > Hi Igor, > >This

Re: [openstack-dev] [ironic] OpenStack client default ironic API version

On 03/07/2017 04:59 PM, Loo, Ruby wrote: On 2017-03-06, 3:46 PM, "Mario Villaplana" wrote: Hi ironic, At the PTG, an issue regarding the default version of the ironic API used in our python-openstackclient plugin was discussed. [0] In short, the

[openstack-dev] [acceleration] No team meeting today, resume next Wed

Hi team, As agreed per our PTG/VTG session, we will have the team meeting two weeks after to give people enough time to prepare the BPs we discussed. Therefore there will be no team meeting today, and the next meeting is on next Wed.

Re: [openstack-dev] [kolla] Proposing duonghq for core

+1 2017-03-08 7:34 GMT-03:00 Christian Berendt : > +1 > > > On 8 Mar 2017, at 07:41, Michał Jastrzębski wrote: > > > > Hello, > > > > I'd like to start voting to include Duong (duonghq) in Kolla and > > Kolla-ansible core teams. Voting will be

[openstack-dev] [TripleO][release][deployment] Packaging problems due to branch/release ordering

Hi all, I wanted to raise visibility of a problem we're experiencing in TripleO CI, which I think will potentially affect other projects that consume trunk builds from the RDO repositories (and potentially other distros too I guess) The problem is that we tag our final ocata releases after

Re: [openstack-dev] [nova] Question to clarify versioned notifications

On 3/8/2017 4:19 AM, Balazs Gibizer wrote: Honestly, If searchlight needs to be adapted to the versioned notifications then the smallest thing to change is to handle the removed prefix from the event_type. The biggest difference is the format and the content of the payload. In the legacy

[openstack-dev] [nova][placement-api] Is there any document about openstack-placement-api for installation and configure?

Hi Guys, I'm new to openstack. I tried to install openstack-ocata. As placement-api is required since Ocata, is there any detailed document about how to install and configure placement-api? Thanks, Jared __ OpenStack

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

Sounds like a good candidate for a cross-project release goal. A non-controversial situation, the work is a no-op for most, a specific deliverable for a few, and a mechanism to close the loop and make sure it gets done in a specific timeframe? Thanks for surfacing it Matthew. -amrith

Re: [openstack-dev] [TripleO][Heat] Selectively disabling deployment resources

On 08/03/17 10:05, James Slagle wrote: On Tue, Mar 7, 2017 at 7:24 PM, Zane Bitter wrote: On 07/03/17 14:34, James Slagle wrote: I've been working on this spec for TripleO: https://review.openstack.org/#/c/431745/ which allows users to selectively disable Heat deployment

Re: [openstack-dev] [neutron] [infra] Depends-on tag effect

On 2017-03-08 15:40, ZZelle wrote: > Hi, > > iiuc, neutron uses a released version of neutron-lib not neutron-lib > master ... So the change should depends on a change in requirements repo > incrementing neutron-lib version This is documented also at - together with some other caveats:

Re: [openstack-dev] [TripleO][Heat] Selectively disabling deployment resources

On Tue, Mar 7, 2017 at 7:24 PM, Zane Bitter wrote: > On 07/03/17 14:34, James Slagle wrote: >> >> I've been working on this spec for TripleO: >> https://review.openstack.org/#/c/431745/ >> >> which allows users to selectively disable Heat deployment resources >> for a given

Re: [openstack-dev] [nova][placement-api] Is there any document about openstack-placement-api for installation and configure?

@Chris, Thanks for replying. When I tried to configure placement-api, I met following problems, AH01630: client denied by server configuration: /usr/bin/nova-placement-api I will read the links you pointed out. Thanks again, Jared On 2017年03月08日 23:07, Chris Dent wrote: On Wed, 8 Mar 2017,

Re: [openstack-dev] [neutron] [infra] Depends-on tag effect

On 2017/03/08 23:59, Andreas Jaeger wrote: On 2017-03-08 15:40, ZZelle wrote: Hi, iiuc, neutron uses a released version of neutron-lib not neutron-lib master ... So the change should depends on a change in requirements repo incrementing neutron-lib version This is documented also at -

Re: [openstack-dev] [cinder][glance][horizon][keystone][nova][qa][swift] Feedback needed: Removal of legacy per-project vanity domain redirects

>From a keystone-perspective, I'm fine killing keystone.openstack.org. Unless another team member with more context/history has a reason to keep it around. On Wed, Mar 8, 2017 at 9:12 AM, Monty Taylor wrote: > Hey all, > > We have a set of old vanity redirect URLs from

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

On Wed, Mar 8, 2017 at 8:03 PM, Matthew Thode wrote: > So, pycrypto upstream is dead and has been for a while, we should look > at moving off of it for both bugfix and security reasons. > > Currently it's used by the following. > > barbican, cinder, trove, glance, heat,

[openstack-dev] [horizon] [keystone] [federated auth] [ocata] federated users with "admin" role not authorized for nova, cinder, neutron admin panels

I am on Ocata with Shibboleth auth enabled. I noticed that Federated users with the admin role no longer have authorization to use the Admin** panels in Horizon related to Nova, Cinder and Neutron. All regular Identity and Project tabs function, and there are no problems with authorization for

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

-Original Message- From: Christopher Aedo Reply: OpenStack Development Mailing List (not for usage questions) Date: March 7, 2017 at 22:11:22 To: OpenStack Development Mailing List (not for usage questions)

Re: [openstack-dev] [release][tripleo][fuel][kolla][ansible] Ocata Release countdown for R+2 Week, 6-10 March

Excerpts from Vladimir Kuklin's message of 2017-03-08 01:20:21 +0300: > Doug > > I have proposed the change for Fuel RC2 [0], but it has W-1 set as I am > waiting for the final tests result. If everything goes alright, I will > check the Worfklow off and this RC2 can be the cut as the release.

Re: [openstack-dev] [telemetry][requirements] ceilometer grenade gate failure

On 07/03/17 11:16 PM, Tony Breeds wrote: > Sure. > > I've approved it but it's blocked behind > https://review.openstack.org/#/c/442886/1 awesome! thanks Tony! cheers, -- gord __ OpenStack Development Mailing List (not

Re: [openstack-dev] [QA] Meeting Thursday Mar 9th at 9:00 UTC

Hey gmann I did bug triage last weeks (27th Feb – 3rd March). So far 7 new bugs arrived: 3 confirmed (2 low, 1 medium) #1669455 tempest run --regex '\[.*\bsmoke\b.*\]' --blacklist-file=/home/jenkins/tempest/skip.txt not able to run smoke tests

Re: [openstack-dev] [requirements] pycrypto is dead, long live pycryptodome... or cryptography...

On Wed, Mar 8, 2017 at 1:03 PM, Matthew Thode wrote: > So, pycrypto upstream is dead and has been for a while, we should look > at moving off of it for both bugfix and security reasons. > > Currently it's used by the following. > > barbican, cinder, trove, glance,

Re: [openstack-dev] [acceleration] No team meeting today, resume next Wed

Thanks for the update. Unfortunately I could not attend and can't seem to find a summary or anything about what took place. A pointer would be appreciated please ;-) Thanks for your time Harm Sluiman harm.slui...@gmail.com > On Mar 8, 2017, at 7:22 AM, Zhipeng Huang

[openstack-dev] [trove] today weekly meeting

While I try to schedule my life to not conflict with the weekly Trove meeting, it appears that Wednesday afternoon at 1pm is a particularly popular time for people to want to meet me. This week, and next week are no exception. While I'd tried to avoid these conflicts, I've managed to be unable

Re: [openstack-dev] [kolla][ubuntu][libvirt] Is libvirt 2.5.0 in ubuntu cloud archive ocata repo bust

On Tue, Mar 7, 2017 at 10:28 PM, Jeffrey Zhang wrote: > Kolla deploy ubuntu gate is red now. here is the related bug[0]. > > libvirt failed to access the console.log file when booting instance. After > made some debugging, i got following. > > Jeffrey, This is likely

Re: [openstack-dev] [ironic] OpenStack client default ironic API version

We want to deprecate ironic CLI soon, but I would prefer if that were discussed on a separate thread if possible, aside from concerns about versioning in ironic CLI. Feature parity should exist in Pike, then we can issue a warning in Queens and deprecate the cycle after. More information is on

[openstack-dev] [neutron] [infra] Depends-on tag effect

Hi, I thought that we can post neutron patch depending on neutron-lib patch under review. However, I saw it doesn't work[1, 2]. In the patches, neutron patch[1] has Depends-on tag with neutron-lib patch[2] but the pep8 and unit test fails because the test doesn't use the neutron-lib patch.

Re: [openstack-dev] [Murano] Newton version of Murano fails trying to auto-import a Liberty version of io.murano.applications.zip

It is probably that the package io.murano.applications is not present in the app catalog. io.murano and io.murano.applications are the packages that are bundled with Murano and usually should be preinstalled. You can obtain them here: https://github.com/openstack/murano/tree/stable/newton/meta

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

Personally I tend to agree with Christopher's POV. IMO the OpenStack community and TC could and should make a progress in perception how to make OpenStack more 'consumable' and useful for a broader audience. And IMO AppCatalog falls into this direction of making OpenStack more consumable and

[openstack-dev] [horizon] Horizon Weekly IRC Meeting

Hey everyone, Reminder that the weekly IRC meeting is 2000 UTC on Wednesday (about 10.5 hours from sending this email) in #openstack-meeting-3. Anyone is welcome to add to the agenda at https://wiki.openstack.org/wiki/Meetings/Horizon Previous logs, ICS files, and other info can be found at

Re: [openstack-dev] [kolla] Proposing duonghq for core

+1 On 08/03/17 08:29, Jeffrey Zhang wrote: +1 from me On Wed, Mar 8, 2017 at 2:41 PM, Michał Jastrzębski > wrote: Hello, I'd like to start voting to include Duong (duonghq) in Kolla and Kolla-ansible core teams. Voting will be open for 2

Re: [openstack-dev] [kolla] Proposing duonghq for core

+1 from me On Wed, Mar 8, 2017 at 2:41 PM, Michał Jastrzębski wrote: > Hello, > > I'd like to start voting to include Duong (duonghq) in Kolla and > Kolla-ansible core teams. Voting will be open for 2 weeks (ends at > 21st of March). > > Consider this my +1 vote. > > Cheers, >

[openstack-dev] [tricircle]weekly meeting of Mar. 8

Hello, team, Attention please, the new weekly meeting time slot is UTC 14:00~UTC 15:00 Agenda of Mar.8 weekly meeting: 1. Pike-1 feature priority discussion 2. Pike features development 3. Open Discussion How to join: # IRC meeting:

Re: [openstack-dev] [oslo_reports]Does GMR work for uwsgi mode service?

Hi, Roman Thank you very much! It works well when I used file handle event to trigger a generation of a report instead of signals. Thanks again, Wang Hao 2017-03-07 18:56 GMT+08:00 Roman Podoliaka : > Hi, > > My understanding is that it's not recommended for WSGI apps

Re: [openstack-dev] [TripleO][Heat] Selectively disabling deployment resources

On Tue, Mar 07, 2017 at 02:34:50PM -0500, James Slagle wrote: > I've been working on this spec for TripleO: > https://review.openstack.org/#/c/431745/ > > which allows users to selectively disable Heat deployment resources > for a given server (or server in the case of a *DeloymentGroup >

Re: [openstack-dev] [nova] Question to clarify versioned notifications

On Tue, Mar 7, 2017 at 8:42 PM, Matt Riedemann wrote: While digging through nova code today to compare versioned and unversioned notifications, and reading specs and seeing how seachlight handles nova notifications, I noticed that the unversioned notifications have a