Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
On Mon, Dec 14, 2015 at 9:28 AM, Ian Cordasco wrote: > > > On 12/14/15, 02:18, "Kuvaja, Erno" wrote: > > >> -Original Message- > >> From: McLellan, Steven > >> Sent: Friday, December 11, 2015 6:37 PM > >> To: OpenStack Development Mailing List (not for usage questions) > >> Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service > >>Catalog > >> name for Glance Artifact Repository API > >> > >> Hi Alex, > >> > >> Searchlight uses port 9393 (it also made sense to us when we spun out of > >> Glance!), so we would prefer it if there's another one that makes sense. > >> Regarding the three hardest things in computer science, searchlight's > >>already > >> dealing with cache invalidation so I'll stay out of the naming > >>discussion. > >> > >> Thanks! > >> > >> Steve > > > >Thanks for the heads up Steve, > > > >Mind to make sure that it gets registered for Searchlight as well. It's > >not listed in config-reference [0] nor iana [1] (seems that at least > >glance ports are not registered in iana either fwiw): > > Are any of the OpenStack projects actually listed on IANA? > > Searching through > https://www.iana.org/assignments/service-names-port-numbers/service-names-p > ort-numbers.txt for service names (nova, swift, etc.) I don't see *any* > openstack services. > > We've got Identity's port 35357 reserved: openstack-id 35357 tcpOpenStack ID Service [Rackspace_Hosting] [Ziad_Sawalha] 2011-08-15 Despite the reservation it still caused issues since this port is in Linux's default range for ephemeral ports. So some other process might get this port before keystone did and then keystone would fail to start. Also note that this is the "admin" port, which keystone only needs for v2 (to be deprecated) since we've got policy support in v3. Just goes to show that we shouldn't be using distinct ports for web services, put them on a path on :443 or :80 like the web was designed for. - Brant > > > >[0] > > > http://docs.openstack.org/liberty/config-reference/content/firewalls-defau > >lt-ports.html > >[1] > > > http://www.iana.org/assignments/service-names-port-numbers/service-names-p > >ort-numbers.xhtml > > > >- Erno > >> > >> From: Alexander Tivelkov > >> mailto:ativel...@mirantis.com>> > >> Reply-To: "OpenStack Development Mailing List (not for usage questions)" > >> mailto:openstack- > >> d...@lists.openstack.org>> > >> Date: Friday, December 11, 2015 at 11:25 AM > >> To: "OpenStack Development Mailing List (not for usage questions)" > >> mailto:openstack- > >> d...@lists.openstack.org>> > >> Subject: [openstack-dev] [glance][keystone][artifacts] Service Catalog > >>name > >> for Glance Artifact Repository API > >> > >> Hi folks! > >> > >> As it was decided during the Mitaka design summit, we are separating the > >> experimental Artifact Repository API from the main Glance API. This API > >>will > >> have a versioning sequence independent from the main Glance API and will > >> be run as a standalone optional service, listening on the port > >>different from > >> the standard glance-api port (currently the proposed default is 9393). > >> Meanwhile, it will remain an integral part of the larger Glance > >>project, sharing > >> the database, implementation roadmap, development and review teams > >> etc. > >> > >> Since this API will be consumed by both end-users and other Openstack > >> services, its endpoint should be discoverable via regular service > >>catalog API. > >> This rises the question: what should be the service name and service > >>type for > >> the appropriate entree in the service catalog? > >> > >> We've came out with the idea to call the service "glare" (this is our > >>internal > >> codename for the artifacts initiative, being an acronym for "GLance > >>Artifact > >> REpository") and set its type to "artifacts". Other alternatives for > >>the name > >> may be "arti" or "glance_artifacts" and for the type - "assets" or > >>"objects" >
Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
On 12/14/15, 02:18, "Kuvaja, Erno" wrote: >> -Original Message- >> From: McLellan, Steven >> Sent: Friday, December 11, 2015 6:37 PM >> To: OpenStack Development Mailing List (not for usage questions) >> Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service >>Catalog >> name for Glance Artifact Repository API >> >> Hi Alex, >> >> Searchlight uses port 9393 (it also made sense to us when we spun out of >> Glance!), so we would prefer it if there's another one that makes sense. >> Regarding the three hardest things in computer science, searchlight's >>already >> dealing with cache invalidation so I'll stay out of the naming >>discussion. >> >> Thanks! >> >> Steve > >Thanks for the heads up Steve, > >Mind to make sure that it gets registered for Searchlight as well. It's >not listed in config-reference [0] nor iana [1] (seems that at least >glance ports are not registered in iana either fwiw): Are any of the OpenStack projects actually listed on IANA? Searching through https://www.iana.org/assignments/service-names-port-numbers/service-names-p ort-numbers.txt for service names (nova, swift, etc.) I don't see *any* openstack services. > >[0] >http://docs.openstack.org/liberty/config-reference/content/firewalls-defau >lt-ports.html >[1] >http://www.iana.org/assignments/service-names-port-numbers/service-names-p >ort-numbers.xhtml > >- Erno >> >> From: Alexander Tivelkov >> mailto:ativel...@mirantis.com>> >> Reply-To: "OpenStack Development Mailing List (not for usage questions)" >> mailto:openstack- >> d...@lists.openstack.org>> >> Date: Friday, December 11, 2015 at 11:25 AM >> To: "OpenStack Development Mailing List (not for usage questions)" >> mailto:openstack- >> d...@lists.openstack.org>> >> Subject: [openstack-dev] [glance][keystone][artifacts] Service Catalog >>name >> for Glance Artifact Repository API >> >> Hi folks! >> >> As it was decided during the Mitaka design summit, we are separating the >> experimental Artifact Repository API from the main Glance API. This API >>will >> have a versioning sequence independent from the main Glance API and will >> be run as a standalone optional service, listening on the port >>different from >> the standard glance-api port (currently the proposed default is 9393). >> Meanwhile, it will remain an integral part of the larger Glance >>project, sharing >> the database, implementation roadmap, development and review teams >> etc. >> >> Since this API will be consumed by both end-users and other Openstack >> services, its endpoint should be discoverable via regular service >>catalog API. >> This rises the question: what should be the service name and service >>type for >> the appropriate entree in the service catalog? >> >> We've came out with the idea to call the service "glare" (this is our >>internal >> codename for the artifacts initiative, being an acronym for "GLance >>Artifact >> REpository") and set its type to "artifacts". Other alternatives for >>the name >> may be "arti" or "glance_artifacts" and for the type - "assets" or >>"objects" >> (the latter may be confusing since swift's type is object-store, so I >>personally >> don't like it). >> >> Well... we all know, naming is complicated... anyway, I'll appreciate >>any >> feedback on this. Thanks! >> >> -- >> Regards, >> Alexander Tivelkov >> >> __ >> >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: OpenStack-dev- >> requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >__ >OpenStack Development Mailing List (not for usage questions) >Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
On 12/11/2015 08:25 PM, Alexander Tivelkov wrote: Hi folks! As it was decided during the Mitaka design summit, we are separating the experimental Artifact Repository API from the main Glance API. This API will have a versioning sequence independent from the main Glance API and will be run as a standalone optional service, listening on the port different from the standard glance-api port (currently the proposed default is 9393). Meanwhile, it will remain an integral part of the larger Glance project, sharing the database, implementation roadmap, development and review teams etc. Since this API will be consumed by both end-users and other Openstack services, its endpoint should be discoverable via regular service catalog API. This rises the question: what should be the service name and service type for the appropriate entree in the service catalog? We've came out with the idea to call the service "glare" (this is our internal codename for the artifacts initiative, being an acronym for "GLance Artifact REpository") and set its type to "artifacts". Other alternatives for the name may be "arti" or "glance_artifacts" and for the type - "assets" or "objects" (the latter may be confusing since swift's type is object-store, so I personally don't like it). I don't care about the name. In fact, I don't think the "name" should even exist in the service catalog at all. I think the type should be "artifact". Best, -jay __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
On 12/11/2015 08:51 PM, Alexander Tivelkov wrote:
Hi Steve,
Thanks for the note on port. Any objections on glare using 9494 then?
Anyone?
Yes, I object to 9494. There should be no need to use any custom port
for Glare's API service. Just use 80/443, which are HTTP(S)'s standard
ports. It was a silly thing that we ever used custom port numbers to
begin with, IMHO.
Best,
-jay
Пт, 11 дек. 2015 г. в 21:39, McLellan, Steven mailto:steve.mclel...@hpe.com>>:
Hi Alex,
Searchlight uses port 9393 (it also made sense to us when we spun
out of Glance!), so we would prefer it if there's another one that
makes sense. Regarding the three hardest things in computer science,
searchlight's already dealing with cache invalidation so I'll stay
out of the naming discussion.
Thanks!
Steve
From: Alexander Tivelkov mailto:ativel...@mirantis.com><mailto:ativel...@mirantis.com
<mailto:ativel...@mirantis.com>>>
Reply-To: "OpenStack Development Mailing List (not for usage
questions)" mailto:openstack-dev@lists.openstack.org><mailto:openstack-dev@lists.openstack.org
<mailto:openstack-dev@lists.openstack.org>>>
Date: Friday, December 11, 2015 at 11:25 AM
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org><mailto:openstack-dev@lists.openstack.org
<mailto:openstack-dev@lists.openstack.org>>>
Subject: [openstack-dev] [glance][keystone][artifacts] Service
Catalog name for Glance Artifact Repository API
Hi folks!
As it was decided during the Mitaka design summit, we are separating
the experimental Artifact Repository API from the main Glance API.
This API will have a versioning sequence independent from the main
Glance API and will be run as a standalone optional service,
listening on the port different from the standard glance-api port
(currently the proposed default is 9393). Meanwhile, it will remain
an integral part of the larger Glance project, sharing the database,
implementation roadmap, development and review teams etc.
Since this API will be consumed by both end-users and other
Openstack services, its endpoint should be discoverable via regular
service catalog API. This rises the question: what should be the
service name and service type for the appropriate entree in the
service catalog?
We've came out with the idea to call the service "glare" (this is
our internal codename for the artifacts initiative, being an acronym
for "GLance Artifact REpository") and set its type to "artifacts".
Other alternatives for the name may be "arti" or "glance_artifacts"
and for the type - "assets" or "objects" (the latter may be
confusing since swift's type is object-store, so I personally don't
like it).
Well... we all know, naming is complicated... anyway, I'll
appreciate any feedback on this. Thanks!
--
Regards,
Alexander Tivelkov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Regards,
Alexander Tivelkov
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
> -Original Message- > From: McLellan, Steven > Sent: Friday, December 11, 2015 6:37 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog > name for Glance Artifact Repository API > > Hi Alex, > > Searchlight uses port 9393 (it also made sense to us when we spun out of > Glance!), so we would prefer it if there's another one that makes sense. > Regarding the three hardest things in computer science, searchlight's already > dealing with cache invalidation so I'll stay out of the naming discussion. > > Thanks! > > Steve Thanks for the heads up Steve, Mind to make sure that it gets registered for Searchlight as well. It's not listed in config-reference [0] nor iana [1] (seems that at least glance ports are not registered in iana either fwiw): [0] http://docs.openstack.org/liberty/config-reference/content/firewalls-default-ports.html [1] http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml - Erno > > From: Alexander Tivelkov > mailto:ativel...@mirantis.com>> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" > mailto:openstack- > d...@lists.openstack.org>> > Date: Friday, December 11, 2015 at 11:25 AM > To: "OpenStack Development Mailing List (not for usage questions)" > mailto:openstack- > d...@lists.openstack.org>> > Subject: [openstack-dev] [glance][keystone][artifacts] Service Catalog name > for Glance Artifact Repository API > > Hi folks! > > As it was decided during the Mitaka design summit, we are separating the > experimental Artifact Repository API from the main Glance API. This API will > have a versioning sequence independent from the main Glance API and will > be run as a standalone optional service, listening on the port different from > the standard glance-api port (currently the proposed default is 9393). > Meanwhile, it will remain an integral part of the larger Glance project, > sharing > the database, implementation roadmap, development and review teams > etc. > > Since this API will be consumed by both end-users and other Openstack > services, its endpoint should be discoverable via regular service catalog API. > This rises the question: what should be the service name and service type for > the appropriate entree in the service catalog? > > We've came out with the idea to call the service "glare" (this is our internal > codename for the artifacts initiative, being an acronym for "GLance Artifact > REpository") and set its type to "artifacts". Other alternatives for the name > may be "arti" or "glance_artifacts" and for the type - "assets" or "objects" > (the latter may be confusing since swift's type is object-store, so I > personally > don't like it). > > Well... we all know, naming is complicated... anyway, I'll appreciate any > feedback on this. Thanks! > > -- > Regards, > Alexander Tivelkov > > __ > > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev- > requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
> -Original Message- > From: Ian Cordasco [mailto:ian.corda...@rackspace.com] > Sent: Friday, December 11, 2015 8:13 PM > To: OpenStack Development Mailing List (not for usage questions) > Subject: Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog > name for Glance Artifact Repository API > > > > On 12/11/15, 12:25, "Alexander Tivelkov" wrote: > > >Hi folks! > > > > > >As it was decided during the Mitaka design summit, we are separating > >the experimental Artifact Repository API from the main Glance API. This > >API will have a versioning sequence independent from the main Glance > >API and will be run as a standalone optional service, listening on the > >port different from the standard glance-api port (currently the > >proposed default is 9393). Meanwhile, it will remain an integral part > >of the larger Glance project, sharing the database, implementation > >roadmap, development and review teams etc. > > +1 to 9494 for DevStack so developers can run Arti and Searchlight along > side each other. > > >Since this API will be consumed by both end-users and other Openstack > >services, its endpoint should be discoverable via regular service > >catalog API. This rises the question: what should be the service name > >and service type for the appropriate entree in the service catalog? > > > > > >We've came out with the idea to call the service "glare" (this is our > >internal codename for the artifacts initiative, being an acronym for > >"GLance Artifact REpository") and set its type to "artifacts". Other > >alternatives for the name may be "arti" or "glance_artifacts" > > and for the type - "assets" or "objects" (the latter may be confusing > >since swift's type is object-store, so I personally don't like it). > > For the type, I would think either "asset" or "artifact" (along the lines of > how > glance is "image", and neutron is "network"). I tend to lean towards > "artifact" > though. > > As for the "default" (I assume DevStack) name, why not just "glare", the > description should be "Glance Artifact Service" (which I think is slightly > more > end-user important than the name). ++ - Erno > > >Well... we all know, naming is complicated... anyway, I'll appreciate > >any feedback on this. Thanks! > > > > > > > >-- > > > >Regards, > >Alexander Tivelkov > > > > -- > Cheers, > Ian > > __ > > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev- > requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
On 12/11/15, 3:13 PM, "Ian Cordasco" wrote: >On 12/11/15, 12:25, "Alexander Tivelkov" wrote: > >>Hi folks! >> >> >>As it was decided during the Mitaka design summit, we are separating the >>experimental Artifact Repository API from the main Glance API. This API >>will have a versioning sequence independent from the main Glance API and >>will be run as a standalone optional >> service, listening on the port different from the standard glance-api >>port (currently the proposed default is 9393). Meanwhile, it will remain >>an integral part of the larger Glance project, sharing the database, >>implementation roadmap, development and review >> teams etc. > >+1 to 9494 for DevStack so developers can run Arti and Searchlight along >side each other. +1 to port 9494 >>Since this API will be consumed by both end-users and other Openstack >>services, its endpoint should be discoverable via regular service catalog >>API. This rises the question: what should be the service name and service >>type for the appropriate entree in >> the service catalog? >> >> >>We've came out with the idea to call the service "glare" (this is our >>internal codename for the artifacts initiative, being an acronym for >>"GLance Artifact REpository") and set its type to "artifacts". Other >>alternatives for the name may be "arti" or "glance_artifacts" >> and for the type - "assets" or "objects" (the latter may be confusing >>since swift's type is object-store, so I personally don't like it). > >For the type, I would think either "asset" or "artifact" (along the lines >of how glance is "image", and neutron is "network"). I tend to lean >towards "artifact" though. +1 to type 'artifact' (singular, as Ian suggests, to be consistent with the other services) >As for the "default" (I assume DevStack) name, why not just "glare", the >description should be "Glance Artifact Service" (which I think is slightly >more end-user important than the name). +1 to name 'glare' +1 to description 'Glance Artifact Service' > >>Well... we all know, naming is complicated... anyway, I'll appreciate any >>feedback on this. Thanks! >> >>-- >> >>Regards, >>Alexander Tivelkov > >-- >Cheers, >Ian Guess I could've just said, "what Ian said". cheers, brian __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
On 12/11/15, 12:25, "Alexander Tivelkov" wrote: >Hi folks! > > >As it was decided during the Mitaka design summit, we are separating the >experimental Artifact Repository API from the main Glance API. This API >will have a versioning sequence independent from the main Glance API and >will be run as a standalone optional > service, listening on the port different from the standard glance-api >port (currently the proposed default is 9393). Meanwhile, it will remain >an integral part of the larger Glance project, sharing the database, >implementation roadmap, development and review > teams etc. +1 to 9494 for DevStack so developers can run Arti and Searchlight along side each other. >Since this API will be consumed by both end-users and other Openstack >services, its endpoint should be discoverable via regular service catalog >API. This rises the question: what should be the service name and service >type for the appropriate entree in > the service catalog? > > >We've came out with the idea to call the service "glare" (this is our >internal codename for the artifacts initiative, being an acronym for >"GLance Artifact REpository") and set its type to "artifacts". Other >alternatives for the name may be "arti" or "glance_artifacts" > and for the type - "assets" or "objects" (the latter may be confusing >since swift's type is object-store, so I personally don't like it). For the type, I would think either "asset" or "artifact" (along the lines of how glance is "image", and neutron is "network"). I tend to lean towards "artifact" though. As for the "default" (I assume DevStack) name, why not just "glare", the description should be "Glance Artifact Service" (which I think is slightly more end-user important than the name). >Well... we all know, naming is complicated... anyway, I'll appreciate any >feedback on this. Thanks! > > > >-- > >Regards, >Alexander Tivelkov > -- Cheers, Ian __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
The port is an arbitray choice for developers running on standalone services over HTTP. Just don't choose something in the linux ephemeral port range :) In production, assume all services can be deployed on 443. As for service *type*, it should not include project names, code names, API versions, or branding. It should be unique specific, and non-ambiguous. Keystone provides an "identity" type service, Nova provides a "compute" type service, etc. On Friday, December 11, 2015, Alexander Tivelkov wrote: > Hi Steve, > > Thanks for the note on port. Any objections on glare using 9494 then? > Anyone? > Пт, 11 дек. 2015 г. в 21:39, McLellan, Steven >: > >> Hi Alex, >> >> Searchlight uses port 9393 (it also made sense to us when we spun out of >> Glance!), so we would prefer it if there's another one that makes sense. >> Regarding the three hardest things in computer science, searchlight's >> already dealing with cache invalidation so I'll stay out of the naming >> discussion. >> >> Thanks! >> >> Steve >> >> From: Alexander Tivelkov > > ativel...@mirantis.com >> >> >> Reply-To: "OpenStack Development Mailing List (not for usage questions)" < >> openstack-dev@lists.openstack.org >> >> <mailto:openstack-dev@lists.openstack.org >> >> >> Date: Friday, December 11, 2015 at 11:25 AM >> To: "OpenStack Development Mailing List (not for usage questions)" < >> openstack-dev@lists.openstack.org >> >> <mailto:openstack-dev@lists.openstack.org >> >> >> Subject: [openstack-dev] [glance][keystone][artifacts] Service Catalog >> name for Glance Artifact Repository API >> >> Hi folks! >> >> As it was decided during the Mitaka design summit, we are separating the >> experimental Artifact Repository API from the main Glance API. This API >> will have a versioning sequence independent from the main Glance API and >> will be run as a standalone optional service, listening on the port >> different from the standard glance-api port (currently the proposed default >> is 9393). Meanwhile, it will remain an integral part of the larger Glance >> project, sharing the database, implementation roadmap, development and >> review teams etc. >> >> Since this API will be consumed by both end-users and other Openstack >> services, its endpoint should be discoverable via regular service catalog >> API. This rises the question: what should be the service name and service >> type for the appropriate entree in the service catalog? >> >> We've came out with the idea to call the service "glare" (this is our >> internal codename for the artifacts initiative, being an acronym for >> "GLance Artifact REpository") and set its type to "artifacts". Other >> alternatives for the name may be "arti" or "glance_artifacts" and for the >> type - "assets" or "objects" (the latter may be confusing since swift's >> type is object-store, so I personally don't like it). >> >> Well... we all know, naming is complicated... anyway, I'll appreciate any >> feedback on this. Thanks! >> >> -- >> Regards, >> Alexander Tivelkov >> >> __ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > -- > Regards, > Alexander Tivelkov > __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
Hi Steve, Thanks for the note on port. Any objections on glare using 9494 then? Anyone? Пт, 11 дек. 2015 г. в 21:39, McLellan, Steven : > Hi Alex, > > Searchlight uses port 9393 (it also made sense to us when we spun out of > Glance!), so we would prefer it if there's another one that makes sense. > Regarding the three hardest things in computer science, searchlight's > already dealing with cache invalidation so I'll stay out of the naming > discussion. > > Thanks! > > Steve > > From: Alexander Tivelkov ativel...@mirantis.com>> > Reply-To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org > >> > Date: Friday, December 11, 2015 at 11:25 AM > To: "OpenStack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org > >> > Subject: [openstack-dev] [glance][keystone][artifacts] Service Catalog > name for Glance Artifact Repository API > > Hi folks! > > As it was decided during the Mitaka design summit, we are separating the > experimental Artifact Repository API from the main Glance API. This API > will have a versioning sequence independent from the main Glance API and > will be run as a standalone optional service, listening on the port > different from the standard glance-api port (currently the proposed default > is 9393). Meanwhile, it will remain an integral part of the larger Glance > project, sharing the database, implementation roadmap, development and > review teams etc. > > Since this API will be consumed by both end-users and other Openstack > services, its endpoint should be discoverable via regular service catalog > API. This rises the question: what should be the service name and service > type for the appropriate entree in the service catalog? > > We've came out with the idea to call the service "glare" (this is our > internal codename for the artifacts initiative, being an acronym for > "GLance Artifact REpository") and set its type to "artifacts". Other > alternatives for the name may be "arti" or "glance_artifacts" and for the > type - "assets" or "objects" (the latter may be confusing since swift's > type is object-store, so I personally don't like it). > > Well... we all know, naming is complicated... anyway, I'll appreciate any > feedback on this. Thanks! > > -- > Regards, > Alexander Tivelkov > > __ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -- Regards, Alexander Tivelkov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
Hi Alex, Searchlight uses port 9393 (it also made sense to us when we spun out of Glance!), so we would prefer it if there's another one that makes sense. Regarding the three hardest things in computer science, searchlight's already dealing with cache invalidation so I'll stay out of the naming discussion. Thanks! Steve From: Alexander Tivelkov mailto:ativel...@mirantis.com>> Reply-To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Date: Friday, December 11, 2015 at 11:25 AM To: "OpenStack Development Mailing List (not for usage questions)" mailto:openstack-dev@lists.openstack.org>> Subject: [openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API Hi folks! As it was decided during the Mitaka design summit, we are separating the experimental Artifact Repository API from the main Glance API. This API will have a versioning sequence independent from the main Glance API and will be run as a standalone optional service, listening on the port different from the standard glance-api port (currently the proposed default is 9393). Meanwhile, it will remain an integral part of the larger Glance project, sharing the database, implementation roadmap, development and review teams etc. Since this API will be consumed by both end-users and other Openstack services, its endpoint should be discoverable via regular service catalog API. This rises the question: what should be the service name and service type for the appropriate entree in the service catalog? We've came out with the idea to call the service "glare" (this is our internal codename for the artifacts initiative, being an acronym for "GLance Artifact REpository") and set its type to "artifacts". Other alternatives for the name may be "arti" or "glance_artifacts" and for the type - "assets" or "objects" (the latter may be confusing since swift's type is object-store, so I personally don't like it). Well... we all know, naming is complicated... anyway, I'll appreciate any feedback on this. Thanks! -- Regards, Alexander Tivelkov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [glance][keystone][artifacts] Service Catalog name for Glance Artifact Repository API
Hi folks! As it was decided during the Mitaka design summit, we are separating the experimental Artifact Repository API from the main Glance API. This API will have a versioning sequence independent from the main Glance API and will be run as a standalone optional service, listening on the port different from the standard glance-api port (currently the proposed default is 9393). Meanwhile, it will remain an integral part of the larger Glance project, sharing the database, implementation roadmap, development and review teams etc. Since this API will be consumed by both end-users and other Openstack services, its endpoint should be discoverable via regular service catalog API. This rises the question: what should be the service name and service type for the appropriate entree in the service catalog? We've came out with the idea to call the service "glare" (this is our internal codename for the artifacts initiative, being an acronym for "GLance Artifact REpository") and set its type to "artifacts". Other alternatives for the name may be "arti" or "glance_artifacts" and for the type - "assets" or "objects" (the latter may be confusing since swift's type is object-store, so I personally don't like it). Well... we all know, naming is complicated... anyway, I'll appreciate any feedback on this. Thanks! -- Regards, Alexander Tivelkov __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
