Open Stack

On Fri, Dec 12, 2014 at 1:48 AM, Pasquale Porreca <
pasquale.porreca at dektech.com.au> wrote:

> From my point of view it is not advisable to base some functionalities
> of the instances on direct calls to Openstack API. This for 2 main
> reasons, the first one: if the Openstack code changes (and we know
> Openstack code does change) it will be required to change the code of
> the software running in the instance too; the second one: if in the
> future one wants to pass to another cloud infrastructure it will be more
> difficult to achieve it.
>


Thoughts on your two reasons:

1) What happens if OpenStack code changes?

While OpenStack is under very active development we have stable APIs,
especially around something like booting an instance. So the API call to
boot an instance with a specific image *should not* change as you upgrade
OpenStack (unless we deprecate an API, but this will be a slow multi year
process).

2) "if in the future one wants to pass to another cloud infrastructure it
will be more difficult to achieve it."

Why not use something like apache jcloud to make this easier?
https://jclouds.apache.org/





>
> On 12/12/14 01:20, Joe Gordon wrote:
> > On Wed, Dec 10, 2014 at 7:42 AM, Pasquale Porreca <
> > pasquale.porreca at dektech.com.au> wrote:
> >
> >> >  Well, one of the main reason to choose an open source product is to
> avoid
> >> > vendor lock-in. I think it is not
> >> > advisable to embed in the software running in an instance a call to
> >> > OpenStack specific services.
> >> >
> > I'm sorry I don't follow the logic here, can you elaborate.
> >
> >
>
> --
> Pasquale Porreca
>
> DEK Technologies
> Via dei Castelli Romani, 22
> 00040 Pomezia (Roma)
>
> Mobile +39 3394823805
> Skype paskporr
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20141212/4794050e/attachment.html>