>> global ironic
>> if ironic is None:
>> ironic = importutils.import_module('ironicclient')
I believe ironic was an early example of a client library we hot-loaded,
and I believe at the time we said this was a pattern we were going to
follow. Personally, I think this
9 PM, Michael Still wrote: >Matt Riedemann ---04/12/2018
> 08:46:25 AM---On 4/11/2018 5:09 PM, Michael Still wrote: >
>
> From: Matt Riedemann <mriede...@gmail.com>
> To: openstack-dev@lists.openstack.org
> Dat
4/11/2018 5:09 PM, Michael Still wrote: >Matt Riedemann ---04/12/2018
> > 08:46:25 AM---On 4/11/2018 5:09 PM, Michael Still wrote: >
> >
> > From: Matt Riedemann <mriede...@gmail.com <mailto:mriede...@gmail.com>>
> > To: openstack-dev@lists.
>Matt Riedemann ---04/12/2018
> > 08:46:25 AM---On 4/11/2018 5:09 PM, Michael Still wrote: >
> >
> > From: Matt Riedemann <mriede...@gmail.com>
> > To: openstack-dev@lists.openstack.org
> > Date: 04/12/2018 08:46 AM
> > Subject: Re
Excerpts from Monty Taylor's message of 2018-04-12 13:54:46 -0500:
> On 04/12/2018 11:27 AM, Clark Boylan wrote:
> > On Wed, Apr 11, 2018, at 5:45 PM, Matt Riedemann wrote:
> >> I also seem to remember that [extras] was less than user-friendly for
> >> some reason, but maybe that was just because
On 04/12/2018 11:27 AM, Clark Boylan wrote:
On Wed, Apr 11, 2018, at 5:45 PM, Matt Riedemann wrote:
I also seem to remember that [extras] was less than user-friendly for
some reason, but maybe that was just because of how our CI jobs are
setup? Or I'm just making that up. I know it's pretty
On 4/12/2018 7:42 AM, Eric Fried wrote:
This sounds reasonable to me. I'm glad the issue was raised, but IMO it
shouldn't derail progress on an approved blueprint with ready code.
Jichen, would you please go ahead and file that blueprint template (no
need to write a spec yet) and link it in a
On Wed, Apr 11, 2018, at 5:45 PM, Matt Riedemann wrote:
> I also seem to remember that [extras] was less than user-friendly for
> some reason, but maybe that was just because of how our CI jobs are
> setup? Or I'm just making that up. I know it's pretty simple to install
> the stuff from extras
el Still wrote: >
From: Matt Riedemann <mriede...@gmail.com>
To: openstack-dev@lists.openstack.org
Date: 04/12/2018 08:46 AM
Subject: Re: [openstack-dev] [Nova][Deployers] Optional, platform
specific, dependancies in requirements.txt
--
08:46:25 AM---On 4/11/2018 5:09 PM, Michael Still wrote: >
>
> From: Matt Riedemann <mriede...@gmail.com>
> To: openstack-dev@lists.openstack.org
> Date: 04/12/2018 08:46 AM
> Subject: Re: [openstack-dev] [Nova][Deployers] Optional, platform
> specific, dependancies in r
/F Ring Building, ZhongGuanCun Software Park, Haidian District,
Beijing 100193, PRC
From: Matt Riedemann <mriede...@gmail.com>
To: openstack-dev@lists.openstack.org
Date: 04/12/2018 08:46 AM
Subject: Re: [openstack-dev] [Nova][Deployers] Optional, platform
sp
On 4/11/2018 5:09 PM, Michael Still wrote:
https://review.openstack.org/#/c/523387 proposes adding a z/VM specific
dependancy to nova's requirements.txt. When I objected the counter
argument is that we have examples of windows specific dependancies
(os-win) and powervm specific dependancies
On Wed, Apr 11, 2018, at 3:09 PM, Michael Still wrote:
> Hi,
>
> https://review.openstack.org/#/c/523387 proposes adding a z/VM specific
> dependancy to nova's requirements.txt. When I objected the counter argument
> is that we have examples of windows specific dependancies (os-win) and
> powervm
Hi,
https://review.openstack.org/#/c/523387 proposes adding a z/VM specific
dependancy to nova's requirements.txt. When I objected the counter argument
is that we have examples of windows specific dependancies (os-win) and
powervm specific dependancies in that file already.
I think perhaps all
14 matches
Mail list logo
