—
> Egor
>
> From: Vikas Choudhary choudharyvika...@gmail.com>>
> Date: Wednesday, October 21, 2015 at 16:04
> To: Walmart Associate mailto:e...@walmartlabs.com>>
> Subject: Re: [openstack-dev] [Magnum] Coe components status
>
> @Egor,
>
> Kubectl commnad is &qu
estions)"
mailto:openstack-dev@lists.openstack.org>>
Date: Tuesday, October 20, 2015 at 20:56
To: "OpenStack Development Mailing List (not for usage questions)"
mailto:openstack-dev@lists.openstack.org>>
Subject: Re: [openstack-dev] [Magnum] Coe components status
@ Eli ,
I will look
+ 1 to vikas.
As we have monitor framework only to docker swarm COE at present and we are
pushing other COE drivers in future. So it is better to have component
status for one COE at first and will push other COEs support later. Correct
me if I am wrong.
Regards
Bharath T
On Wed, Oct 21, 2015 at
@ Eli ,
I will look into how to support this feature for other COEs also(mesos and
swarm). But anyways Magnum's goal is to provide users *atleast* what other
coes are providing (if not something extra). All coes dont have common
features, so we cant be very strict on providing common interface api
hi Vikas,
thanks for propose this changes, I wonder if you can show some examples
for other coes we currently supported:
swarm, mesos ?
if we propose a public api like you proposed, we'd better to support all
coes instead of coe specific.
thanks
Eli.
On 2015年10月20日 18:14, Vikas Choudhary wr
Hi Team,
I would appreciate any opinion/concern regarding "coe-component-status"
feature implementation [1].
For example in k8s, using API api/v1/namespaces/{namespace}/componentstatuses,
status of each k8s component can be queried. My approach would be to
provide a command in magnum like "magnum
