Sent from my iPhone
> On Nov 5, 2018, at 10:19 AM, Thierry Carrez <thie...@openstack.org> wrote: > > Monty Taylor wrote: >> [...] >> What if we added support for serving vendor data files from the root of a >> primary URL as-per RFC 5785. Specifically, support deployers adding a json >> file to .well-known/openstack/client that would contain what we currently >> store in the openstacksdk repo and were just discussing splitting out. >> [...] >> What do people think? > > I love the idea of public clouds serving that file directly, and the user > experience you get from it. The only two drawbacks on top of my head would be: > > - it's harder to discover available compliant openstack clouds from the > client. > > - there is no vetting process, so there may be failures with weird clouds > serving half-baked files that people may blame the client tooling for. > > I still think it's a good idea, as in theory it aligns the incentive of > maintaining the file with the most interested stakeholder. It just might need > some extra communication to work seamlessly. I’m thinking out loud here but perhaps a simple linter that a cloud provider can run will help them make sure that everything is functional. > -- > Thierry Carrez (ttx) > > __________________________________________________________________________ > 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
