, September 27, 2018 12:35 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting
goal selection for T series
On 9/27/2018 2:33 PM, Fox, Kevin M wrote:
> If the project plugins were maintained by the OSC project still, maybe there
>
On 9/27/2018 2:33 PM, Fox, Kevin M wrote:
If the project plugins were maintained by the OSC project still, maybe there
would be incentive for the various other projects to join the OSC project,
scaling things up?
Sure, I don't really care about governance. But I also don't really care
about
27, 2018 12:12 PM
To: openstack-dev@lists.openstack.org
Subject: Re: [openstack-dev] [Openstack-sigs] [goals][tc][ptl][uc] starting
goal selection for T series
On 9/27/2018 10:13 AM, Dean Troyer wrote:
> On Thu, Sep 27, 2018 at 9:10 AM, Doug Hellmann wrote:
>> Monty Taylor writes:
On 9/27/2018 10:13 AM, Dean Troyer wrote:
On Thu, Sep 27, 2018 at 9:10 AM, Doug Hellmann wrote:
Monty Taylor writes:
Main difference is making sure these new deconstructed plugin teams
understand the client support lifecycle - which is that we don't drop
support for old versions of services
On Thu, Sep 27, 2018 at 9:10 AM, Doug Hellmann wrote:
> Monty Taylor writes:
>> Main difference is making sure these new deconstructed plugin teams
>> understand the client support lifecycle - which is that we don't drop
>> support for old versions of services in OSC (or SDK). It's a shift from
On Thu, Sep 27, 2018 at 9:06 AM, Doug Hellmann wrote:
> I definitely think having details about the gaps would be a prerequisite
> for approving a goal, but I wonder if that's something 1 person could
> even do alone. Is this an area where a small team is needed?
Maybe, but it does break down
Monty Taylor writes:
> Main difference is making sure these new deconstructed plugin teams
> understand the client support lifecycle - which is that we don't drop
> support for old versions of services in OSC (or SDK). It's a shift from
> the support lifecycle and POV of python-*client, but
Dean Troyer writes:
> On Wed, Sep 26, 2018 at 3:44 PM, Matt Riedemann wrote:
>> I started documenting the compute API gaps in OSC last release [1]. It's a
>> big gap and needs a lot of work, even for existing CLIs (the cold/live
>> migration CLIs in OSC are a mess, and you can't even boot from
First I think that is a great goal, but I want to pick up on Dean's comment:
Dean Troyer wrote:
[...]
The OSC core team is very thin, yes, it seems as though companies
don't like to spend money on client-facing things...I'll be in the
hall following this thread should anyone want to talk...
I
On 09/26/2018 04:33 PM, Dean Troyer wrote:
On Wed, Sep 26, 2018 at 3:44 PM, Matt Riedemann wrote:
I started documenting the compute API gaps in OSC last release [1]. It's a
big gap and needs a lot of work, even for existing CLIs (the cold/live
migration CLIs in OSC are a mess, and you can't
ooperation,Silicon Valley Research Center
From:Mathieu Gagné
To:openstack-s...@lists.openstack.org,
Cc:OpenStack Development Mailing List (not for usage questions),OpenStack
Operators,
Date:2018-09-26 12:41:24
Subject:Re: [Openstack-sigs] [openstack-dev] [goals][tc][ptl][uc] starting goal
selection fo
On Wed, Sep 26, 2018 at 3:44 PM, Matt Riedemann wrote:
> I started documenting the compute API gaps in OSC last release [1]. It's a
> big gap and needs a lot of work, even for existing CLIs (the cold/live
> migration CLIs in OSC are a mess, and you can't even boot from volume where
> nova creates
usage questions)"
Date: Wednesday, 26 September 2018 at 18:00
To: openstack-dev , openstack-operators
, openstack-sigs
Subject: [openstack-dev] [goals][tc][ptl][uc] starting goal selection for T
series
It's time to start thinking about community-wide goals for the T series.
We use
l that goals should include this audience also.
>
> Tim
>
> -Original Message-
> From: Doug Hellmann
> Reply-To: "OpenStack Development Mailing List (not for usage questions)"
>
> Date: Wednesday, 26 September 2018 at 18:00
> To: openstack-dev , opensta
14 matches
Mail list logo
