Sukhdev Kapur <sukhdevka...@gmail.com>
> Date: Mon, Apr 11, 2016 at 7:33 AM
> Subject: Re: [openstack-dev] [Neutron] Newton blueprints call for action
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev@lists.openstack.org>
> C
Forwarded message --
> From: Sukhdev Kapur <sukhdevka...@gmail.com <mailto:sukhdevka...@gmail.com>>
> Date: Mon, Apr 11, 2016 at 7:33 AM
> Subject: Re: [openstack-dev] [Neutron] Newton blueprints call for action
> To: "OpenStack Development Mailing Li
Hi Rossella,
Good to hear that you will follow through with this. Ironic is looking for
this API as well for bare metal deployments. We would love to work with you
to make sure that this API/Implementation works for all servers ( VMs as
well BMs)
Thanks
-Sukhdev
On Wed, Apr 6, 2016 at 4:32 AM,
Folks, thanks to everyone who has replied to the the thread. Much
appreciated it.
I'll reach out individually to figure out next steps and come back here to
provide a status update.
Cheers,
Armando
On 6 April 2016 at 07:17, Brent Eagles wrote:
> -BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Armando,
On 05/04/16 01:13 AM, Armando M. wrote:
> Hi Neutrinos,
>
> During today's team meeting [0], we went through the current
> milestone workload [1].
>
> This is mostly made of Mitaka backlog items, amongst which we
> discussed two
On 04/05/2016 05:43 AM, Armando M. wrote:
>
> With this email I would like to appeal to the people in CC to report
> back their interest in continuing working on these items in their
> respective capacities, and/or the wider community, in case new owners
> need to be identified.
>
> I look
Armando M. wrote:
> I would like to understand if these need new owners (both assignees and
> approvers). Code submitted [5,6] has not been touched in a while, and
> whilst I appreciate people have been busy focussing on Mitaka (myself
> included), the Newton master branch has been open for a
Hi Neutrinos,
During today's team meeting [0], we went through the current milestone
workload [1].
This is mostly made of Mitaka backlog items, amongst which we discussed two
blueprints [2, 3]. These two efforts had their spec approved during the
Mitaka timeframe, but code lagged behind, and