Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-11-15 Thread Matthew Thode
On 17-11-15 09:32:33, Dmitry Tantsur wrote: > On 10/31/2017 12:11 AM, richard.pi...@dell.com wrote: > > > From: Dmitry Tantsur [mailto:dtant...@redhat.com] > > > > > Cons: > > > 1. more work for both the requirements team and the vendor teams > > > > Please elaborate on the additional work you

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-11-15 Thread Dmitry Tantsur
On 10/31/2017 12:11 AM, richard.pi...@dell.com wrote: From: Dmitry Tantsur [mailto:dtant...@redhat.com] Cons: 1. more work for both the requirements team and the vendor teams Please elaborate on the additional work you envision for the vendor teams. Any requirements updates with have to

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-11-15 Thread Dmitry Tantsur
To: openstack-dev <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements? Excerpts from Dmitry Tantsur's message of 2017-10-30 17:51:49 +0100: Hi all, So far driver requirements [1] have been managed outside of

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-11-15 Thread Dmitry Tantsur
, Arkady -Original Message- From: Doug Hellmann [mailto:d...@doughellmann.com] Sent: Monday, October 30, 2017 2:47 PM To: openstack-dev <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements? Excerpts from

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-10-31 Thread Tony Breeds
On Mon, Oct 30, 2017 at 08:07:10PM -0400, Doug Hellmann wrote: > Excerpts from Richard.Pioso's message of 2017-10-30 23:11:31 +: > > 2. And would that be correctly handled? > > Good question. We should test the requirements update script to see. It does. I did a quick fictional test: This:

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-10-31 Thread Tony Breeds
On Mon, Oct 30, 2017 at 05:51:49PM +0100, Dmitry Tantsur wrote: > Hi all, > > So far driver requirements [1] have been managed outside of > global-requirements. This was mostly necessary because some dependencies > were not on PyPI. This is no longer the case, and I'd like to consider > managing

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-10-31 Thread Mike Perez
On 17:51 Oct 30, Dmitry Tantsur wrote: > Hi all, > > So far driver requirements [1] have been managed outside of > global-requirements. This was mostly necessary because some dependencies > were not on PyPI. This is no longer the case, and I'd like to consider > managing them just like any other

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-10-31 Thread Pavlo Shchelokovskyy
On Mon, Oct 30, 2017 at 9:46 PM, Doug Hellmann wrote: > Excerpts from Dmitry Tantsur's message of 2017-10-30 17:51:49 +0100: > > Hi all, > > > > So far driver requirements [1] have been managed outside of > global-requirements. > > This was mostly necessary because some

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-10-30 Thread Doug Hellmann
Excerpts from Richard.Pioso's message of 2017-10-30 23:11:31 +: > > From: Dmitry Tantsur [mailto:dtant...@redhat.com] > > > Cons: > > 1. more work for both the requirements team and the vendor teams > > Please elaborate on the additional work you envision for the vendor teams. > > > 2.

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-10-30 Thread Richard.Pioso
> From: Dmitry Tantsur [mailto:dtant...@redhat.com] > Cons: > 1. more work for both the requirements team and the vendor teams Please elaborate on the additional work you envision for the vendor teams. > 2. inability to use ironic release notes to explain driver requirements > changes Where

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-10-30 Thread Matthew Thode
> -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Monday, October 30, 2017 2:47 PM > To: openstack-dev <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [ironic] [requirements] moving driver > dependencies to global-r

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-10-30 Thread Matthew Thode
> -Original Message- > From: Doug Hellmann [mailto:d...@doughellmann.com] > Sent: Monday, October 30, 2017 2:47 PM > To: openstack-dev <openstack-dev@lists.openstack.org> > Subject: Re: [openstack-dev] [ironic] [requirements] moving driver > dependencies to global-r

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-10-30 Thread Arkady.Kanevsky
, October 30, 2017 2:47 PM To: openstack-dev <openstack-dev@lists.openstack.org> Subject: Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements? Excerpts from Dmitry Tantsur's message of 2017-10-30 17:51:49 +0100: > Hi all, > > So far driver requir

Re: [openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-10-30 Thread Doug Hellmann
Excerpts from Dmitry Tantsur's message of 2017-10-30 17:51:49 +0100: > Hi all, > > So far driver requirements [1] have been managed outside of > global-requirements. > This was mostly necessary because some dependencies were not on PyPI. This is > no > longer the case, and I'd like to

[openstack-dev] [ironic] [requirements] moving driver dependencies to global-requirements?

2017-10-30 Thread Dmitry Tantsur
Hi all, So far driver requirements [1] have been managed outside of global-requirements. This was mostly necessary because some dependencies were not on PyPI. This is no longer the case, and I'd like to consider managing them just like any other dependencies. Pros: 1. making these