Re: [openstack-dev] [goals][upgrade-checkers] Week R-25 Update

On Tue, 2018-10-23 at 16:40 -0500, Matt Riedemann wrote: > On 10/23/2018 1:41 PM, Sean McGinnis wrote: > > > Yeah, but part of the reason for placeholders was consistency > > > across all of > > > the services. I guess if there are never going to be upgrade > > > checks in > > > adjutant then I cou

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

On Mon, 2018-10-22 at 07:50 -0700, Morgan Fainberg wrote: > Also, doesn't bitbucket have a git interface now too (optionally)? > It does :) But I think it requires a new repo, so it means that could as well move to somewhere else like github or openstack infra :p ___

Re: [openstack-dev] [heat][senlin] Action Required. Idea to propose for a forum for autoscaling features integration

Hi all, I'm glad to notify you all that our forum session has been accepted [1] and that forum time schedule (Thursday, November 15, 9:50am-10:30am) should be stable by now. So please save your schedule for it!! Any feedback are welcome! [1] https://www.openstack.org/summit/berlin-2018/summit-sc

Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed

Tony Breeds wrote: AFACIT the upload was successful: shade-1.27.2-py2-none-any.whl : 2018-10-24T03:20:00 d30a230461ba276c8bc561a27e61dcfd6769ca00bb4c652a841f7148a0d74a5a shade-1.27.2-py2.py3-none-any.whl : 2018-10-24T03:20:11 8942b56d7d02740fb9c799

Re: [openstack-dev] [ClusterLabs Developers] [HA] future of OpenStack OCF resource agents (was: resource-agents v4.2.0)

[cross-posting to openstack-dev] Oyvind Albrigtsen wrote: ClusterLabs is happy to announce resource-agents v4.2.0. Source code is available at: https://github.com/ClusterLabs/resource-agents/releases/tag/v4.2.0 The most significant enhancements in this release are: - new resource agents: [sn

Re: [openstack-dev] [nova][NFS] Inexplicable utime permission denied when launching instance

I think that there's a change that AppArmor is blocking the access. Have you checked the dmesg messages related with apparmor? Em sex, 19 de out de 2018 às 09:38, Neil Jerram escreveu: > Wracking my brains over this one, would appreciate any pointers... > > Setup: Small test deployment with just

Re: [openstack-dev] [nova][NFS] Inexplicable utime permission denied when launching instance

PS. Don't forget that if you change or disable AppArmor you will have to reboot the host so the kernel gets reloaded. Em qua, 24 de out de 2018 às 09:40, Erlon Cruz escreveu: > I think that there's a change that AppArmor is blocking the access. Have > you checked the dmesg messages related with

Re: [openstack-dev] [cinder] [nova] Problem of Volume(in-use) Live Migration with ceph backend

On 10/23/2018 9:01 AM, Jon Bernard wrote: * melanie witt wrote: On Mon, 22 Oct 2018 11:45:55 +0800 (GMT+08:00), Boxiang Zhu wrote: I created a new vm and a new volume with type 'ceph'[So that the volume will be created on one of two hosts. I assume that the volume created on host dev@rbd-1#c

Re: [openstack-dev] [nova][NFS] Inexplicable utime permission denied when launching instance

Thanks so much for these hints, Erlon. I will look closer at AppArmor. Neil On Wed, Oct 24, 2018 at 1:41 PM Erlon Cruz wrote: > > PS. Don't forget that if you change or disable AppArmor you will have to > reboot the host so the kernel gets reloaded. > > Em qua, 24 de out de 2018 às 09:40,

Re: [openstack-dev] [goals][upgrade-checkers] Week R-25 Update

On 10/23/18 9:55 PM, Adrian Turjak wrote: On 24/10/18 2:09 AM, Ben Nemec wrote: On 10/22/18 5:40 PM, Matt Riedemann wrote: On 10/22/2018 4:35 PM, Adrian Turjak wrote: The one other open question I have is about the Adjutant change [2]. I know Adjutant is very new and I'm not sure what upg

Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed

On 2018-10-24 16:08:26 +1100 (+1100), Tony Breeds wrote: > On Wed, Oct 24, 2018 at 03:23:53AM +, z...@openstack.org wrote: > > Build failed. > > > > - release-openstack-python3 > > http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python3/e84da68/

Re: [openstack-dev] [Release-job-failures] Release of openstack-infra/shade failed

On Wed, Oct 24, 2018 at 12:08 AM Tony Breeds wrote: > On Wed, Oct 24, 2018 at 03:23:53AM +, z...@openstack.org wrote: > > Build failed. > > > > - release-openstack-python3 > http://logs.openstack.org/ab/abac67d7bb347e1caba4d74c81712de86790316b/release/release-openstack-python3/e84da68/ > : PO

[openstack-dev] [TripleO][OVN] Switching the default network backend to ML2/OVN

Hi Stackers! The purpose of this email is to share with the community the intention of switching the default network backend in TripleO from ML2/OVS to ML2/OVN by changing the mechanism driver from openvswitch to ovn. This doesn’t mean that ML2/OVS will be dropped but users deploying OpenStack wit

[openstack-dev] [magnum][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Magnum team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [horizon][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Horizon team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guid

[openstack-dev] [trove][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Trove team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [sahara][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Sahara team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [murano][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Murano team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [freezer][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Freezer team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guid

[openstack-dev] [solum][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Solum team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [masakari][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Masakari team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help gui

[openstack-dev] [mistral][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Mistral team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guid

[openstack-dev] [telemetry][aodh][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Telemetry team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help gu

[openstack-dev] [heat][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Heat team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide d

[openstack-dev] [senlin][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Senlin team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [blazar][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Blazar team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [zaqar][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Zaqar team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [zun][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Zun team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide de

[openstack-dev] [nova][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Nova team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide d

[openstack-dev] [qinling][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Qinling team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guid

[openstack-dev] [neutron][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Neutron team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guid

[openstack-dev] [octavia][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Octavia team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guid

[openstack-dev] [designate][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Designate team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help gu

[openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

Nova's API has the ability to create "quota classes", which are basically limits for a set of resource types. There is something called the "default quota class" which corresponds to the limits in the CONF.quota section. Quota classes are basically templates of limits to be applied if the calli

[openstack-dev] [ironic][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Ironic team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [cyborg][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Cyborg team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [swift][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Swift team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [manila][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Manila team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [cinder][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Cinder team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [keystone][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Keystone team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help gui

[openstack-dev] [glance][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Glance team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] [barbican][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Barbican team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help gui

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

Forwarding to openstack-operators per Jay. On 10/24/18 10:10, Jay Pipes wrote: > Nova's API has the ability to create "quota classes", which are > basically limits for a set of resource types. There is something called > the "default quota class" which corresponds to the limits in the > CONF.quota

[openstack-dev] [searchlight][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Searchlight team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help

[openstack-dev] [monasca][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Monasca team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guid

[openstack-dev] [karbor][tc] Seeking feedback on the OpenStack cloud vision

Greetings, Karbor team! As you may be aware, I've been working with other folks in the community on documenting a vision for OpenStack clouds (formerly known as the 'Technical Vision') - essentially to interpret the mission statement in long-form, in a way that we can use to actually help guide

[openstack-dev] Registration Prices Increase Today - OpenStack Summit Berlin

Hi everyone, Friendly reminder that the ticket price for the OpenStack Summit Berlin increases today, October 24 at 11:59pm PDT (October 25 at 6:59 UTC). Also, ALL registration codes (sponsor, speaker, ATC, AUC) will expire on November 2. Register now before the price increases! 

[openstack-dev] Use of capslock on the mailing lists

Hello Gentle Reader: I'm writing to share my thoughts on how I feel when I open my inbox on my account subscribed to OpenStack mailing lists. I've been subscribed to various lists for some time and have accommodated my consumption style to suit the broadcast nature of the specific lists; use

Re: [openstack-dev] [ClusterLabs Developers] [HA] future of OpenStack OCF resource agents (was: resource-agents v4.2.0)

Adam, Personally, I would prefer the approach where the OpenStack resource agents are part of the repository in which they are used. This is also the approach taken in other open source projects such as Kubernetes and avoids the inconsistency where, for example, Azure resource agents are in the

Re: [openstack-dev] [all] [tc] [api] Paste Maintenance

On Wed, 24 Oct 2018, Jean-Philippe Evrard wrote: On Mon, 2018-10-22 at 07:50 -0700, Morgan Fainberg wrote: Also, doesn't bitbucket have a git interface now too (optionally)? It does :) But I think it requires a new repo, so it means that could as well move to somewhere else like github or ope

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

On 10/24/2018 10:10 AM, Jay Pipes wrote: I'd like to propose deprecating this API and getting rid of this functionality since it conflicts with the new Keystone /limits endpoint, is highly coupled with RAX's turnstile middleware and I can't seem to find anyone who has ever used it. Deprecating

Re: [openstack-dev] [cinder] [nova] Problem of Volume(in-use) Live Migration with ceph backend

On Tue, 23 Oct 2018 10:01:42 -0400, Jon Bernard wrote: * melanie witt wrote: On Mon, 22 Oct 2018 11:45:55 +0800 (GMT+08:00), Boxiang Zhu wrote: I created a new vm and a new volume with type 'ceph'[So that the volume will be created on one of two hosts. I assume that the volume created on host

Re: [openstack-dev] Proposal for a process to keep up with Python releases

There seems to be agreement that this is broadly a good direction to pursue, so I proposed a TC resolution. Let's shift discussion to the review: https://review.openstack.org/613145 cheers, Zane. On 19/10/18 11:17 AM, Zane Bitter wrote: There hasn't been a Python 2 release in 8 years, and duri

[openstack-dev] Announcing the First Release of StarlingX, an open source edge computing platform

Hi, You may have heard, StarlingX[1] is a new independent, top-level, open source pilot project that's supported by the OpenStack Foundation. StarlingX joins other pilot projects hosted at OpenStack Foundation[2], including Airship, Kata Containers and Zuul. Today the first release of Starling

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

On 10/24/2018 02:57 PM, Matt Riedemann wrote: On 10/24/2018 10:10 AM, Jay Pipes wrote: I'd like to propose deprecating this API and getting rid of this functionality since it conflicts with the new Keystone /limits endpoint, is highly coupled with RAX's turnstile middleware and I can't seem to

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

On Wed, 24 Oct 2018 13:57:05 -0500, Matt Riedemann wrote: On 10/24/2018 10:10 AM, Jay Pipes wrote: I'd like to propose deprecating this API and getting rid of this functionality since it conflicts with the new Keystone /limits endpoint, is highly coupled with RAX's turnstile middleware and I can

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

On Wed, Oct 24, 2018 at 2:49 PM Jay Pipes wrote: > On 10/24/2018 02:57 PM, Matt Riedemann wrote: > > On 10/24/2018 10:10 AM, Jay Pipes wrote: > >> I'd like to propose deprecating this API and getting rid of this > >> functionality since it conflicts with the new Keystone /limits > >> endpoint, is

Re: [openstack-dev] [tripleo][ui][tempest][oooq] Refreshing plugins from git

Here is an etherpad with all of the open patches that Chandan and I have been working on. https://etherpad.openstack.org/p/selenium-testing-ci On 2018-10-22 18:25, Chandan kumar wrote: > Hello Honza, > > On Thu, Oct 18, 2018 at 6:15 PM Bogdan Dobrelya wrote: > > > > On 10/18/18 2:17 AM, Honza P

Re: [openstack-dev] [nova] nova cellsv2 and DBs / down cells / quotas

> On 24 Oct 2018, at 4:01 pm, melanie witt wrote: > > On Wed, 24 Oct 2018 10:54:31 +1100, Sam Morrison wrote: >> Hi nova devs, >> Have been having a good look into cellsv2 and how we migrate to them (we’re >> still on cellsv1 and about to upgrade to queens and still run cells v1 for >> now).

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

so FYI, in case people missing this spec, there is spec from John https://review.openstack.org/#/c/602201/3/specs/stein/approved/unified-limits-stein.rst@170 the roadmap of this spec is also saying deprecate the quota-class API. melanie witt 于2018年10月25日周四 上午3:54写道： > On Wed, 24 Oct 2018 13:57:

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

> On 10/24/18 10:10, Jay Pipes wrote: > > Nova's API has the ability to create "quota classes", which are > > basically limits for a set of resource types. There is something called > > the "default quota class" which corresponds to the limits in the > > CONF.quota section. Quota classes are basica

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

Hi All, We were having a similar use case like *Preemptible Instances* called as *Rich-VM’s* which are high in resources and are deployed each per hypervisor. We have a custom code in production which tracks the quota for such instances separately and for the same reason we have *rich_instances

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

On Wed, 24 Oct 2018 12:54:00 -0700, Melanie Witt wrote: On Wed, 24 Oct 2018 13:57:05 -0500, Matt Riedemann wrote: On 10/24/2018 10:10 AM, Jay Pipes wrote: I'd like to propose deprecating this API and getting rid of this functionality since it conflicts with the new Keystone /limits endpoint, is

Re: [openstack-dev] [nova][limits] Does ANYONE at all use the quota class functionality in Nova?

On Thu, 25 Oct 2018 14:12:51 +0900, ボーアディネシュ[bhor Dinesh] wrote: We were having a similar use case like *Preemptible Instances* called as *Rich-VM’s* which are high in resources and are deployed each per hypervisor. We have a custom code in production which tracks the quota for such instance

Re: [openstack-dev] [nova] nova cellsv2 and DBs / down cells / quotas

On Thu, 25 Oct 2018 10:55:15 +1100, Sam Morrison wrote: On 24 Oct 2018, at 4:01 pm, melanie witt wrote: On Wed, 24 Oct 2018 10:54:31 +1100, Sam Morrison wrote: Hi nova devs, Have been having a good look into cellsv2 and how we migrate to them (we’re still on cellsv1 and about to upgrade to