[openstack-dev] [ceilometer] upgrades from juno to kilo

I tracked down the cause of the check-grenade-dsvm failure on https://review.openstack.org/#/c/167370 . As I understand it, grenade is taking the previous stable release, deploying it, then upgrading to the current master (plus the proposed changeset) without changing any of the config from the

Re: [openstack-dev] [glance] Removing python-swiftclient from requirements.txt

be fighting over this in the review... [1] https://launchpad.net/bugs/1475737 [2] https://review.openstack.org/#/c/203200/ [3] https://review.openstack.org/#/c/203242/ - Erno From: William M Edmonds [mailto:edmon...@us.ibm.com] Sent: Monday, July 27, 2015 10:42 PM To: openstack-dev

Re: [openstack-dev] [glance] Removing python-swiftclient from requirements.txt

From: Doug Hellmann d...@doughellmann.com To: openstack-dev openstack-dev@lists.openstack.org Date: 07/28/2015 07:59 PM Subject: Re: [openstack-dev] [glance] Removing python-swiftclient from requirements.txt snip I replied on both patches, but I'll repeat it here for a broader audience:

[openstack-dev] [glance] Removing python-swiftclient from requirements.txt

python-swiftclient is only needed by operators that are using the swift backend, so it really doesn't belong in requirements.txt. Listing it in requirements forces all operators to install it, even if they're not going to use the swift backend. When I proposed a change [1] to move this from

Re: [openstack-dev] [cross-project] Admin

Adam Young wrote on 10/19/2015 09:53:14 AM: > While I tend to play up bug 968696 for dramatic effect, the reality is > we have a logical contradiction on what we mean by 'admin' when talking > about RBAC. > > In early iterations of OpenStack, roles were global. This is

Re: [openstack-dev] [cross-project] Admin

Adam Young <ayo...@redhat.com> wrote on 10/22/2015 10:31:12 AM: > On 10/22/2015 05:16 AM, William M Edmonds wrote: > Adam Young <ayo...@redhat.com> wrote on 10/19/2015 09:53:14 AM: > > While I tend to play up  bug 968696 for dramatic effect, the reality is > > w

Re: [openstack-dev] Requests + urllib3 + distro packages

Cory Benfield writes: > > The problem that occurs is the result of a few interacting things: > > - requests has very very specific versions of urllib3 it works with. > > So specific they aren't always released yet. > > This should no longer be true. Our downstream redistributors

Re: [openstack-dev] Requests + urllib3 + distro packages

Robert Collins writes: > - Linux vendors often unbundle urllib3 from requests and then apply > what patches were needed to their urllib3; while not updating their > requests package dependencies to reflect this. I opened a bug on Fedora for them to update their requests package

Re: [openstack-dev] [telemetry] [ceilometer] [panko] ceilometer API deprecation

On 01/10/2017 09:26 AM, gordon chung wrote: > On 10/01/17 07:27 AM, Julien Danjou wrote: > > On Mon, Jan 09 2017, William M Edmonds wrote: > > > >> I started the conversation on IRC [5], but wanted to send this to the > >> mailing list and see if others have thou

Re: [openstack-dev] [nova] Let's kill quota classes (again)

On 12/16/2016 05:03 PM, Jay Pipes wrote: > On 12/16/2016 04:36 PM, Matt Riedemann wrote: > > On 12/16/2016 2:20 PM, Jay Pipes wrote: > >> > >> For problems with placing data like this as configuration options, see > >> the hassle we went through in making the allocation_ratio options into > >>

[openstack-dev] [telemetry] [ceilometer] [panko] ceilometer API deprecation

It's just come to my attention that the Newton release notes indicated deprecation of the events support in favor of Panko [1] and that it has already been removed in master [2]. But I don't believe there were any deprecation warnings for this in the Newton code, which is the typical way many

Re: [openstack-dev] [keystone][api] Backwards incompatible changes based on config

Lance Bragstad wrote on 08/04/2017 02:37:40 PM: > Properly fixing this would result in a 403 -> 204 status code, which > requires an API version bump according to the interoperability > guidelines [5] (note that keystone has not implemented microversions at > this point). At

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

Julien Danjou wrote on 08/16/2017 02:13:10 PM: > From: Julien Danjou > To: "Eric S Berglund" > Cc: openstack-dev@lists.openstack.org > Date: 08/16/2017 02:14 PM > Subject: Re: [openstack-dev] [release] [telemetry] Ceilometer >

Re: [openstack-dev] [release] [telemetry] Ceilometer stable/pike branch outlook

nch outlook > > Tony Breeds wrote: > > On Wed, Aug 16, 2017 at 02:37:50PM -0400, William M Edmonds wrote: > >> > >> Julien Danjou <jul...@danjou.info> wrote on 08/16/2017 02:13:10 PM: > >>> AFAIU it's impossible to cut a branch for our projects and rel

Re: [openstack-dev] [keystone] Does the policy.json for trustsworks?

Adrian Turjak wrote on 09/18/2017 01:39:20 AM: > > Bug submitted: > > https://urldefense.proofpoint.com/v2/url? > u=https-3A__bugs.launchpad.net_keystone_-2Bbug_1717847=DwIGaQ=jf_iaSHvJObTbx- >

Re: [openstack-dev] [keystone][zuul] A Sad Farewell

Jamie Lennox wrote on 10/02/2017 10:13:49 PM: > > Hi All, > I'm really sad to announce that I'll be leaving the OpenStack > community (at least for a while), I've accepted a new position > unrelated to OpenStack that'll begin in a few weeks, and am going to > be mostly on

Re: [openstack-dev] [policy] AWS IAM session

+1 Lance Bragstad wrote on 10/03/2017 04:08:31 PM: > Hey all, > > It was mentioned in today's keystone meeting [0] that it would be useful > to go through AWS IAM (or even GKE) as a group. With all the recent > policy discussions and work, it seems useful to get our eyes on

[openstack-dev] summit free passes

It has been stated that attending the PTG will get you a free code for the summit. Is that still true even though the PTG falls after the early registration deadline in this case, or will it simply be a discount of the early-registration cost? Similarly, would someone with a free registration

Re: [openstack-dev] [all][requirements] a plan to stop syncing requirements into projects

Doug Hellmann wrote on 05/14/2018 08:52:08 AM: > ... snip ... > > We still have about 50 open patches related to adding the > lower-constraints test job. I'll keep those open until the third > milestone of the Rocky development cycle, and then abandon the rest to > clear

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

> From: Matt Riedemann > To: "OpenStack Development Mailing List (not for usage questions)" > > Date: 01/03/2018 07:03 PM > Subject: [openstack-dev] [nova] Working toward Queens feature freeze and RC1 > ... snip ... > The rest of the

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

> From: William M Edmonds/Raleigh/IBM > To: "OpenStack Development Mailing List \(not for usage questions\)" > <openstack-dev@lists.openstack.org> > Date: 01/08/2018 03:11 PM > Subject: Re: [openstack-dev] [nova] Working toward Queens feature > freeze and RC1

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

keystone may have taken "domain", but it didn't take "dns-domain" Dean Troyer wrote on 02/12/2018 10:24:05 AM: > > On Mon, Feb 12, 2018 at 9:13 AM, Graham Hayes wrote: > > OSC only predates Designate by 5 months ... > > My bad, I didn't check dates. > > > "Zone"

Re: [openstack-dev] [osc][python-openstackclient] Consistency of option name

Graham Hayes <g...@ham.ie> wrote on 02/12/2018 11:17:45 AM: > On 12/02/18 16:04, William M Edmonds wrote: > > keystone may have taken "domain", but it didn't take "dns-domain" > > No, but the advice at the time was to move to zone, and match DNS > RFCs

Re: [openstack-dev] [requirements] we are now unfrozen and branched

I'm not seeing a stable/queens branch for openstack/requirements yet. Is that not what you meant? When is that projected? Matthew Thode wrote on 02/12/2018 11:25:44 AM: > This means we are back to business as usual. > > cycle trailing projects have been warned not to

Re: [openstack-dev] [goal][python3] week 2 update

Doug Hellmann wrote on 08/20/2018 11:27:09 AM: > If your team is ready to have your zuul settings migrated, please > let us know by following up to this email. We will start with the > volunteers, and then work our way through the other teams. I think PowerVMStackers is ready (so nova-powervm,

Re: [openstack-dev] [nova] keypair quota usage info for user

Ghanshyam Mann wrote on 07/25/2018 05:44:46 AM: ... snip ... > 1. is it ok to show the keypair used info via API ? any original > rational not to do so or it was just like that from starting. keypairs aren't tied to a tenant/project, so how could nova track/report a quota for them on a given

Re: [openstack-dev] [tempest][CI][nova compute] Skipping non-compute-driver tests

Ghanshyam Mann wrote on 09/07/2018 02:18:13 AM: snip.. > neutron-tempest-plugin or other service test you can always avoid to > run with regex. And i do not think compute negative or DB test will > take much time to run. But still if you want to avoid to run then, I > think it is easy to

Re: [openstack-dev] [keystone] Keystone Team Update - Week of 15 January 2018

welcome, Gage! Congrats! Boris, Steve, Brant, Brad... you are and will be missed. W. Matthew Edmonds Sr. Software Engineer, IBM Power Systems Email: edmon...@us.ibm.com Phone: (919) 543-7538 / Tie-Line: 441-7538 From: Colleen Murphy To: "OpenStack Development

Re: [openstack-dev] [docs] When should we say 'run as root' in the docs?

Matt Riedemann wrote on 04/19/2018 06:11:58 PM: > How loose are we with saying things like, "you should run this as root" > in the docs? > > I was triaging this nova bug [1] which is saying that the docs should > tell you to run nova-status (which implies also nova-manage)

Re: [openstack-dev] [nova] VMware NSX CI - no longer running?

melanie witt wrote on 03/29/2018 06:03:26 AM: > I would like to see the VMware CI running again and it need only run on > changes under the nova/virt/vmwareapi/ tree, to save on your resources. > And on our side, I'd like us to add VMware subteam members to VMware > driver

Re: [openstack-dev] [requirements][horizon][neutron] plugins depending on services

Monty Taylor wrote on 04/25/2018 09:40:47 AM: ... > Introduce a whitelist of git repo urls, starting with: > >* https://git.openstack.org/openstack/neutron >* https://git.openstack.org/openstack/horizon > We would also need to include at least nova (e.g. [1]) and

[openstack-dev] [zVM] [python3] tox/zuul issues for zVM OpenStack

The current tox.ini for ceilometer-zvm includes this line [1] similar to what ceilometer-powervm was doing up until recently: -egit+https://github.com/openstack/ceilometer@master#egg=ceilometer We found that this no longer works since ceilometer was added to upper-constraints [2]. We first

Re: [openstack-dev] [python3] Enabling py37 unit tests

Corey Bryant wrote on 10/15/2018 05:34:24 PM: ... > From an ubuntu perspective, ubuntu is going to support stein on 18. > 04 LTS (3.6) and 19.04 (3.7) only. ... So folks with Ubuntu 16.04 LTS compute nodes will have to upgrade them all to 18.04 before upgrading to Stein? Of course this would

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

melanie witt wrote on 10/25/2018 02:14:40 AM: > 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 > >

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

Zane Bitter wrote on 10/22/2018 03:12:46 PM: > On 22/10/18 10:33 AM, Thomas Goirand wrote: > > On 10/19/18 5:17 PM, Zane Bitter wrote: > >> Integration Tests > >> - > >> > >> Integration tests do test, amongst other things, integration with > >> non-openstack-supplied things

Re: [openstack-dev] [goal][python3] week 7 update

Doug Hellmann wrote on 09/26/2018 06:29:11 PM: > * We do not want to set the override once in testenv, because that > breaks the more specific versions used in default environments like > py35 and py36 (at least under older versions of tox). I assume that something like