Hey, Mathieu Thanks for bringing us the solution, Jay and I are willing to help
if you are looking for someone to coordinate at the Cinder side. TommyLike.Hu
On 2017-04-04 08:50 , Mathieu Gagné Wrote: Hi, On Mon, Apr 3, 2017 at 8:40 PM,
Jay S Bryant wrote: > > Thank you
On 4/3/2017 11:27 AM, Walter Boring wrote:
Actually, this is incorrect.
The sticking point of this all was doing the coordination and
initiation of workflow from Nova. Cinder already has the ability to
call the driver to do the resize of the volume. Cinder just prevents
this now, because
Hi,
On Mon, Apr 3, 2017 at 8:40 PM, Jay S Bryant wrote:
>
> Thank you for sharing this. Nice to see you have a solution that looks
> agreeable to Matt. Do you think you can get a spec pushed up and propose
> your code?
>
I will go ahead, write the spec and contribute the
Mathieu,
Thank you for sharing this. Nice to see you have a solution that looks
agreeable to Matt. Do you think you can get a spec pushed up and
propose your code?
Jay
On 4/3/2017 2:21 PM, Mathieu Gagné wrote:
On Mon, Apr 3, 2017 at 12:27 PM, Walter Boring wrote:
On 4/3/2017 5:30 PM, Matt Riedemann wrote:
On 4/3/2017 2:21 PM, Mathieu Gagné wrote:
I would like to share our private implementation (based on Mitaka):
https://gist.github.com/mgagne/9402089c11f8c80f6d6cd49f3db76512
The implementation makes it so Cinder leverages the existing Nova
On 4/3/2017 2:21 PM, Mathieu Gagné wrote:
I would like to share our private implementation (based on Mitaka):
https://gist.github.com/mgagne/9402089c11f8c80f6d6cd49f3db76512
The implementation makes it so Cinder leverages the existing Nova
external-events endpoint to trigger the BDM update and
On Mon, Apr 3, 2017 at 12:27 PM, Walter Boring wrote:
> Actually, this is incorrect.
>
> The sticking point of this all was doing the coordination and initiation of
> workflow from Nova. Cinder already has the ability to call the driver to
> do the resize of the volume.
Actually, this is incorrect.
The sticking point of this all was doing the coordination and initiation of
workflow from Nova. Cinder already has the ability to call the driver to
do the resize of the volume. Cinder just prevents this now, because there
is work that has to be done on the
On 4/1/2017 4:07 PM, Matt Riedemann wrote:
On 4/1/2017 12:17 PM, Jay Bryant wrote:
Matt,
I think discussion on this goes all the way back to Tokyo. There was
work on the Cinder side to send the notification to Nova which I believe
all the pieces were in place for. The missing part (sticking
On 4/1/2017 12:17 PM, Jay Bryant wrote:
Matt,
I think discussion on this goes all the way back to Tokyo. There was
work on the Cinder side to send the notification to Nova which I believe
all the pieces were in place for. The missing part (sticking point) was
doing a rescan of the SCSI bus in
Matt,
I think discussion on this goes all the way back to Tokyo. There was
work on the Cinder side to send the notification to Nova which I believe
all the pieces were in place for. The missing part (sticking point) was
doing a rescan of the SCSI bus in the node that had the extended volume
On 3/31/2017 8:55 PM, TommyLike Hu wrote:
There was a time when this feature had been both proposed in Cinder [1]
and Nova [2], but unfortunately no one (correct me if I am wrong) is
going to handle this feature during Pike. We do think extending an
online volume is a beneficial and mostly
There was a time when this feature had been both proposed in Cinder [1] and
Nova [2], but unfortunately no one (correct me if I am wrong) is going to
handle this feature during Pike. We do think extending an online volume is
a beneficial and mostly supported by venders feature. We really don't
13 matches
Mail list logo