Re: [openstack-dev] [tc][all] Plugins for all

On Fri, Jul 22, 2016 at 2:08 PM, Hayes, Graham wrote: > * OpenStack Client > > OpenStack CLI privileged projects have access to more commands, as > plugins cannot hook in to them (e.g. quotas) > It's been OSC's intention to allow for command hooking, we just don't

Re: [openstack-dev] [tc][all] Plugins for all

On 21/07/2016 16:49, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-07-19 16:59:20 +: >> On 19/07/2016 16:39, Doug Hellmann wrote: >>> Excerpts from Hayes, Graham's message of 2016-07-18 17:13:09 +: On 18/07/2016 17:57, Thierry Carrez wrote: > Hayes, Graham

Re: [openstack-dev] [tc][all] Plugins for all

Excerpts from Hayes, Graham's message of 2016-07-19 16:59:20 +: > On 19/07/2016 16:39, Doug Hellmann wrote: > > Excerpts from Hayes, Graham's message of 2016-07-18 17:13:09 +: > >> On 18/07/2016 17:57, Thierry Carrez wrote: > >>> Hayes, Graham wrote: > [...] > The point is that

Re: [openstack-dev] [tc][all] Plugins for all

Excerpts from Doug Wiegley's message of 2016-07-19 13:58:59 -0600: > > > On Jul 19, 2016, at 9:36 AM, Doug Hellmann wrote: > > > > Excerpts from Hayes, Graham's message of 2016-07-18 17:13:09 +: > >> On 18/07/2016 17:57, Thierry Carrez wrote: > >>> Hayes, Graham

Re: [openstack-dev] [tc][all] Plugins for all

On 07/18/2016 06:49 AM, Dmitry Tantsur wrote: On 07/17/2016 11:04 PM, Jay Pipes wrote: On 07/14/2016 12:21 PM, Hayes, Graham wrote: A lot of the effects are hard to see, and are not insurmountable, but do cause projects to re-invent the wheel. For example, quotas - there is no way for a

Re: [openstack-dev] [tc][all] Plugins for all

> On Jul 19, 2016, at 9:36 AM, Doug Hellmann wrote: > > Excerpts from Hayes, Graham's message of 2016-07-18 17:13:09 +: >> On 18/07/2016 17:57, Thierry Carrez wrote: >>> Hayes, Graham wrote: [...] The point is that we were supposed to be a level field as a

Re: [openstack-dev] [tc][all] Plugins for all

I've been trying to follow this thread, but I'll admit I'm confused about what is being asked about or proposed. I'm not sure what "plugins for all" means. Is "plugins for all" a way to make every plugin in an OpenStack project work the same way? How would that work? There's a huge set of

Re: [openstack-dev] [tc][all] Plugins for all

On 19/07/2016 16:39, Doug Hellmann wrote: > Excerpts from Hayes, Graham's message of 2016-07-18 17:13:09 +: >> On 18/07/2016 17:57, Thierry Carrez wrote: >>> Hayes, Graham wrote: [...] The point is that we were supposed to be a level field as a community but if we have examples

Re: [openstack-dev] [tc][all] Plugins for all

Excerpts from Hayes, Graham's message of 2016-07-18 17:13:09 +: > On 18/07/2016 17:57, Thierry Carrez wrote: > > Hayes, Graham wrote: > >> [...] > >> The point is that we were supposed to be a level field as a community > >> but if we have examples like this, there is not a level playing

Re: [openstack-dev] [tc][all] Plugins for all

On 18/07/2016 17:57, Thierry Carrez wrote: > Hayes, Graham wrote: >> [...] >> The point is that we were supposed to be a level field as a community >> but if we have examples like this, there is not a level playing field. > > While I generally agree on your goals here (avoid special-casing some >

Re: [openstack-dev] [tc][all] Plugins for all

Hayes, Graham wrote: [...] The point is that we were supposed to be a level field as a community but if we have examples like this, there is not a level playing field. While I generally agree on your goals here (avoid special-casing some projects in generic support projects like Tempest), I

Re: [openstack-dev] [tc][all] Plugins for all

On 07/17/2016 11:04 PM, Jay Pipes wrote: On 07/14/2016 12:21 PM, Hayes, Graham wrote: A lot of the effects are hard to see, and are not insurmountable, but do cause projects to re-invent the wheel. For example, quotas - there is no way for a project that is not nova, neutron, cinder to hook

Re: [openstack-dev] [tc][all] Plugins for all

On 17/07/2016 22:08, Jay Pipes wrote: > On 07/14/2016 12:21 PM, Hayes, Graham wrote: >> A lot of the effects are hard to see, and are not insurmountable, but >> do cause projects to re-invent the wheel. >> >> For example, quotas - there is no way for a project that is not nova, >> neutron, cinder

Re: [openstack-dev] [tc][all] Plugins for all

On 18/07/2016 01:59, Matt Riedemann wrote: > On 7/17/2016 4:13 PM, Jay Pipes wrote: >> On 07/15/2016 08:36 AM, Hayes, Graham wrote: >>> On 14/07/2016 21:20, Matt Riedemann wrote: And does this also include plugins within projects, like storage backends in cinder and hypervisor drivers in

Re: [openstack-dev] [tc][all] Plugins for all

On 7/17/2016 4:13 PM, Jay Pipes wrote: On 07/15/2016 08:36 AM, Hayes, Graham wrote: On 14/07/2016 21:20, Matt Riedemann wrote: And does this also include plugins within projects, like storage backends in cinder and hypervisor drivers in nova? This is aimed at cross project interaction. So,

Re: [openstack-dev] [tc][all] Plugins for all

On 07/15/2016 08:36 AM, Hayes, Graham wrote: On 14/07/2016 21:20, Matt Riedemann wrote: And does this also include plugins within projects, like storage backends in cinder and hypervisor drivers in nova? This is aimed at cross project interaction. So, if there is a project in projects.yaml

Re: [openstack-dev] [tc][all] Plugins for all

On 07/14/2016 12:21 PM, Hayes, Graham wrote: A lot of the effects are hard to see, and are not insurmountable, but do cause projects to re-invent the wheel. For example, quotas - there is no way for a project that is not nova, neutron, cinder to hook into the standard CLI, or UI for setting

Re: [openstack-dev] [tc][all] Plugins for all

On 15/07/2016 18:24, Luigi Toscano wrote: > On Friday, 15 July 2016 17:05:41 CEST Hayes, Graham wrote: >> On 15/07/2016 17:52, Luigi Toscano wrote: >>> On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: On 15/07/2016 17:10, Andrew Laski wrote: >> Tempest plugins are another

Re: [openstack-dev] [tc][all] Plugins for all

On Friday, 15 July 2016 17:05:41 CEST Hayes, Graham wrote: > On 15/07/2016 17:52, Luigi Toscano wrote: > > On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: > >> On 15/07/2016 17:10, Andrew Laski wrote: > Tempest plugins are another example. Approximately 30 of the 36 > current

Re: [openstack-dev] [tc][all] Plugins for all

On 15/07/2016 17:52, Luigi Toscano wrote: > On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: >> On 15/07/2016 17:10, Andrew Laski wrote: > Tempest plugins are another example. Approximately 30 of the 36 current plugins are using resources that are not supposed to be used,

Re: [openstack-dev] [tc][all] Plugins for all

On Friday, 15 July 2016 16:42:22 CEST Hayes, Graham wrote: > On 15/07/2016 17:10, Andrew Laski wrote: > >> Tempest plugins are another example. Approximately 30 of the 36 > >> current plugins are using resources that are not supposed to be > >> used, and are an unstable interface. Projects in

Re: [openstack-dev] [tc][all] Plugins for all

On 15/07/2016 17:10, Andrew Laski wrote: > > > On Thu, Jul 14, 2016, at 03:21 PM, Hayes, Graham wrote: >> I just proposed a review to openstack/governance repo [0] that aims >> to have everything across OpenStack be plugin based for all cross >> project interaction, or allow all projects access to

Re: [openstack-dev] [tc][all] Plugins for all

On Thu, Jul 14, 2016, at 03:21 PM, Hayes, Graham wrote: > I just proposed a review to openstack/governance repo [0] that aims > to have everything across OpenStack be plugin based for all cross > project interaction, or allow all projects access to the same internal > APIs and I wanted to give a

Re: [openstack-dev] [tc][all] Plugins for all

On 14/07/2016 21:20, Matt Riedemann wrote: > On 7/14/2016 2:21 PM, Hayes, Graham wrote: >> I just proposed a review to openstack/governance repo [0] that aims >> to have everything across OpenStack be plugin based for all cross >> project interaction, or allow all projects access to the same

Re: [openstack-dev] [tc][all] Plugins for all

On 7/14/2016 2:21 PM, Hayes, Graham wrote: I just proposed a review to openstack/governance repo [0] that aims to have everything across OpenStack be plugin based for all cross project interaction, or allow all projects access to the same internal APIs and I wanted to give a bit of background on

[openstack-dev] [tc][all] Plugins for all

I just proposed a review to openstack/governance repo [0] that aims to have everything across OpenStack be plugin based for all cross project interaction, or allow all projects access to the same internal APIs and I wanted to give a bit of background on my motivation, and how it came about.