Stefano Maffulli stef...@openstack.org writes:
On 12/09/2014 04:11 PM, by wrote:
[vad] how about the documentation in this case?... bcos it needs some
place to document (a short desc and a link to vendor page) or list these
kind of out-of-tree plugins/drivers... just to make the user aware
On Tue, Dec 16, 2014 at 4:05 AM, Neil Jerram neil.jer...@metaswitch.com
wrote:
Stefano Maffulli stef...@openstack.org writes:
On 12/09/2014 04:11 PM, by wrote:
[vad] how about the documentation in this case?... bcos it needs some
place to document (a short desc and a link to vendor page)
On 12/09/2014 04:11 PM, by wrote:
[vad] how about the documentation in this case?... bcos it needs some
place to document (a short desc and a link to vendor page) or list these
kind of out-of-tree plugins/drivers... just to make the user aware of
the availability of such plugins/driers which
Dear neutron community,
Can you please clarify couple points on the vendor code decomposition?
- Assuming I would like to create the new driver now (Kilo development
cycle) - is it already allowed (or mandatory) to follow the new process?
https://review.openstack.org/#/c/134680/
- Assuming the
On 12 December 2014 at 23:01, Yuriy Shovkoplias yshovkopl...@mirantis.com
wrote:
Dear neutron community,
Can you please clarify couple points on the vendor code decomposition?
- Assuming I would like to create the new driver now (Kilo development
cycle) - is it already allowed (or
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
+100. I vote -1 there and would like to point out that we *must* keep
history during the split, and split from u/s code base, not random
repositories. If you don't know how to achieve this, ask oslo people,
they did it plenty of times when
On 12/11/14, 12:50 PM, Ihar Hrachyshka ihrac...@redhat.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
+100. I vote -1 there and would like to point out that we *must* keep
history during the split, and split from u/s code base, not random
repositories. If you don't know how to
Remove everything out of tree, and leave only Neutron API framework as
integration
platform, would lower the attractions of the whole Openstack Project.
Without a default good enough reference backend from community, customers
have to depends on packagers to fully test all backends for them.
https://review.openstack.org/#/c/140191/
2014-12-09 18:32 GMT+01:00 Armando M. arma...@gmail.com:
By the way, if Kyle can do it in his teeny tiny time that he has left
after his PTL duties, then anyone can do it! :)
https://review.openstack.org/#/c/140191/
Fully cloning Dave Tucker's
@lists.openstack.org
Cc: openst...@lists.openstack.org openst...@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron] Core/Vendor code decomposition
Gary, you are still miss the point of this proposal. Please see my
comments in review. We are not forcing things out of tree, we are thinning
them
, December 7, 2014 at 7:19 PM
To: OpenStack List openstack-dev@lists.openstack.org
Cc: openst...@lists.openstack.org openst...@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron] Core/Vendor code decomposition
Gary, you are still miss the point of this proposal. Please see my
comments
Subject: [openstack-dev] [Neutron] Core/Vendor code decomposition
Hi folks,
For a few weeks now the Neutron team has worked tirelessly on [1].
This initiative stems from the fact that as the project matures,
evolution of processes and contribution guidelines need to evolve
, December 7, 2014 at 7:19 PM
To: OpenStack List openstack-dev@lists.openstack.org
Cc: openst...@lists.openstack.org openst...@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron] Core/Vendor code decomposition
Gary, you are still miss the point of this proposal. Please see my
comments
-To: OpenStack List openstack-dev@lists.openstack.org
Date: Sunday, December 7, 2014 at 7:19 PM
To: OpenStack List openstack-dev@lists.openstack.org
Cc: openst...@lists.openstack.org openst...@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron] Core/Vendor code
decomposition
Gary, you
-To: OpenStack List openstack-dev@lists.openstack.org
Date: Sunday, December 7, 2014 at 7:19 PM
To: OpenStack List openstack-dev@lists.openstack.org
Cc: openst...@lists.openstack.org openst...@lists.openstack.org
Subject: Re: [openstack-dev] [Neutron] Core/Vendor code
decomposition
Gary
Remove everything out of tree, and leave only Neutron API framework as
integration platform, would lower the attractions of the whole
Openstack Project. Without a default good enough reference backend
from community, customers have to depends on packagers to fully test
all backends for them. Can
: [openstack-dev] [Neutron] Core/Vendor code decomposition
Gary, you are still miss the point of this proposal. Please see my comments
in review. We are not forcing things out of tree, we are thinning them. The
text you quoted in the review makes that clear. We will look at further
decomposing
To: OpenStack List
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org,
openst...@lists.openstack.orgmailto:openst...@lists.openstack.org
openst...@lists.openstack.orgmailto:openst...@lists.openstack.org
Subject: [openstack-dev] [Neutron] Core/Vendor code decomposition
Hi
] [Neutron] Core/Vendor code decomposition
Hi folks,
For a few weeks now the Neutron team has worked tirelessly on [1].
This initiative stems from the fact that as the project matures,
evolution of processes and contribution guidelines need to evolve with it.
This is to ensure that the project
@lists.openstack.orgmailto:openstack-dev@lists.openstack.org,
openst...@lists.openstack.orgmailto:openst...@lists.openstack.org
openst...@lists.openstack.orgmailto:openst...@lists.openstack.org
Subject: [openstack-dev] [Neutron] Core/Vendor code decomposition
Hi folks,
For a few weeks now the Neutron team has worked
Hi folks,
For a few weeks now the Neutron team has worked tirelessly on [1].
This initiative stems from the fact that as the project matures, evolution
of processes and contribution guidelines need to evolve with it. This is to
ensure that the project can keep on thriving in order to meet the
Hello,
As follow-up action after the Design Summit Session on Core/Vendor split,
please find the proposal outlined here:
https://review.openstack.org/#/c/134680/
I know that Anita will tell me off since I asked for reviews on the ML, but
I felt that it was important to raise awareness, even
22 matches
Mail list logo
