Re: [openstack-dev] REST API access to configuration options

2014-07-16 Thread Oleg Gelbukh
On Tue, Jul 15, 2014 at 1:08 PM, Mark McLoughlin wrote: > > Also, this is going to tell you how the API service you connected to was > configured. Where there are multiple API servers, what about the others? > How do operators verify all of the API servers behind a load balancer > with this? > > A

Re: [openstack-dev] REST API access to configuration options

2014-07-16 Thread Chmouel Boudjnah
On Tue, Jul 15, 2014 at 9:54 AM, Henry Nash wrote: > Do people think this is a good idea? Useful in other projects? Concerned > about the risks? FWIW, we have this in Swift for a while and we actually uses it for different testing in cloud capabilities. I personally find it useful for clien

Re: [openstack-dev] REST API access to configuration options

2014-07-15 Thread joehuang
cLoughlin [mailto:mar...@redhat.com] 发送时间: 2014年7月15日 17:08 收件人: OpenStack Development Mailing List (not for usage questions) 主题: Re: [openstack-dev] REST API access to configuration options On Tue, 2014-07-15 at 08:54 +0100, Henry Nash wrote: > HI > > As the number of configuration opt

Re: [openstack-dev] REST API access to configuration options

2014-07-15 Thread Doug Hellmann
On Tue, Jul 15, 2014 at 10:25 AM, Mark McLoughlin wrote: > On Tue, 2014-07-15 at 13:00 +0100, Henry Nash wrote: >> Mark, >> >> >> Thanks for your comments (as well as remarks on the WIP code-review). >> >> >> So clearly gathering and analysing log files is an alternative >> approach, perhaps not a

Re: [openstack-dev] REST API access to configuration options

2014-07-15 Thread Mark McLoughlin
On Tue, 2014-07-15 at 13:00 +0100, Henry Nash wrote: > Mark, > > > Thanks for your comments (as well as remarks on the WIP code-review). > > > So clearly gathering and analysing log files is an alternative > approach, perhaps not as immediate as an API call. In general, I > believe that the mo

Re: [openstack-dev] REST API access to configuration options

2014-07-15 Thread Joe Gordon
On Tue, Jul 15, 2014 at 6:57 AM, Henry Nash wrote: > Joe, > > I'd imagine an API like this would be pretty useful for some of these > config tools - so I'd imagine they might well be consumers of this API. > This may solve the OpenStack case, but something like this wouldn't solve the general is

Re: [openstack-dev] REST API access to configuration options

2014-07-15 Thread Henry Nash
Joe, I'd imagine an API like this would be pretty useful for some of these config tools - so I'd imagine they might well be consumers of this API. Henry On 15 Jul 2014, at 13:10, Joe Gordon wrote: > > > > On Tue, Jul 15, 2014 at 5:00 AM, Henry Nash wrote: > Mark, > > Thanks for your comme

Re: [openstack-dev] REST API access to configuration options

2014-07-15 Thread Joe Gordon
On Tue, Jul 15, 2014 at 5:00 AM, Henry Nash wrote: > Mark, > > Thanks for your comments (as well as remarks on the WIP code-review). > > So clearly gathering and analysing log files is an alternative approach, > perhaps not as immediate as an API call. In general, I believe that the > more capab

Re: [openstack-dev] REST API access to configuration options

2014-07-15 Thread Henry Nash
Mark, Thanks for your comments (as well as remarks on the WIP code-review). So clearly gathering and analysing log files is an alternative approach, perhaps not as immediate as an API call. In general, I believe that the more capability we provide via easy-to-consume APIs (with appropriate per

Re: [openstack-dev] REST API access to configuration options

2014-07-15 Thread Mark McLoughlin
On Tue, 2014-07-15 at 08:54 +0100, Henry Nash wrote: > HI > > As the number of configuration options increases and OpenStack > installations become more complex, the chances of incorrect > configuration increases. There is no better way of enabling cloud > providers to be able to check the configu

[openstack-dev] REST API access to configuration options

2014-07-15 Thread Henry Nash
HI As the number of configuration options increases and OpenStack installations become more complex, the chances of incorrect configuration increases. There is no better way of enabling cloud providers to be able to check the configuration state of an OpenStack service than providing a direct R