On 02/16/2017 11:21 AM, Jay Pipes wrote:
> On 02/16/2017 08:14 AM, Dean Troyer wrote:
>> On Thu, Feb 16, 2017 at 7:06 AM, Andrey Kurilin
>> wrote:
>>> Yes, I forgot about it. But it changes nothing.
>>> Custom implementation of particular service should cover the same API
On 02/16/2017 08:14 AM, Dean Troyer wrote:
On Thu, Feb 16, 2017 at 7:06 AM, Andrey Kurilin wrote:
Yes, I forgot about it. But it changes nothing.
Custom implementation of particular service should cover the same API as an
official one. For me, as for user, it doesn't
> To: OpenStack Development Mailing List (not for usage questions)
> <openstack-dev@lists.openstack.org>
> Subject: Re: [openstack-dev] [all] Do we need service types at all?!
> (Re: [octavia][sdk] service name for octavia)
>
>> On Thu, Feb 16, 2017 at 1:57 PM, Radom
t;openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [all] Do we need service types at all?!
(Re: [octavia][sdk] service name for octavia)
> On Thu, Feb 16, 2017 at 1:57 PM, Radomir Dopieralski > > wrote:
>
> > I think that you have to remember that OpenStack doesn't on
On Thu, Feb 16, 2017 at 7:06 AM, Andrey Kurilin wrote:
> Yes, I forgot about it. But it changes nothing.
> Custom implementation of particular service should cover the same API as an
> official one. For me, as for user, it doesn't metter if there is Keystone or
>
On Thu, Feb 16, 2017 at 1:57 PM, Radomir Dopieralski wrote:
> I think that you have to remember that OpenStack doesn't only work with
> officially approved OpenStack services, but with any services that have a
> conforming API.
>
Yes, I forgot about it. But it changes
I think that you have to remember that OpenStack doesn't only work with
officially approved OpenStack services, but with any services that have a
conforming API. OpenStack itself provides implementations of those
services, and you are right that it's unlikely that there will be two
competing
Hi everyone!
When I started contribution to OpenStack long time ago, I asked about the
reason of having two entities - service type and name; at that time I got
an answer that service name is a name of the project that implements
particular service type, so it is possible to have several projects