Open Stack

@ 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 apis for
all coes. For example "magnum container" commands work only with swarm not
k8s or mesos.
It will not be justified if k8s is providing a way to monitor at more
granular level but magnum will not allow user to use it just beacuse other
coes does not provide this feature.

Agree that it will be nice if could support this feature for all. I will
prefer to start with k8s first and if similar feature is supported by mesos
and swarm also, incrementally will implement that also.

Regards
Vikas Choudhary

On Wed, Oct 21, 2015 at 6:50 AM, Qiao,Liyong <liyong.qiao at intel.com> wrote:

> 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 wrote:
>
> 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
> coe-component-status" leveraging coe provided rest api and result will be
> shown to user.
>
> [1] https://blueprints.launchpad.net/magnum/+spec/coe-component-status
>
>
>
> -Vikas Choudhary
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribehttp://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> --
> BR, Eli(Li Yong)Qiao
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/7ec26801/attachment.html>