I think it makes sense to merge the triplo heat templates without m-dat
support, as including m-dat will require a bunch of dependent patches
and slow everything down. The lack of the m-dat service won't cause any
issues other than that the experimental share-migration APIs won't work.
We
Hi Marios,
I am ok with landing manila in tripleo with manila-data pending as you are
suggesting. Manila-data can be added later, thus not blocking your current
efforts.
Regards,
--
Rodrigo Barbieri
Computer Scientist
OpenStack Manila Contributor
Federal University of São Carlos
On 27/05/16
On 27/05/16 22:46, Rodrigo Barbieri wrote:
> Hello Marios,
>
Hi Rodrigo, thanks very much for taking the time, indeed that clarifies
quite a lot:
> The Data Service is needed for Share Migration feature in manila since the
> Mitaka release.
>
> There has not been any work done yet towards
Hello Marios,
The Data Service is needed for Share Migration feature in manila since the
Mitaka release.
There has not been any work done yet towards adding it to puppet. Since its
introduction in Mitaka, it has been made compatible only with devstack so
far.
I have not invested time thinking
Hi all, I explicitly cc'd a few folks I thought might be interested for
visibility, sorry for spam if you're not. This email is about getting
manila landed into tripleo asap, and the current obstacles to that (at
least those visible to me):
The current review [1] isn't going to land as is,
