[openstack-dev] [Magnum] Coe components status
Qiao,Liyong
liyong.qiao at intel.com
Wed Oct 21 01:20:39 UTC 2015
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
> APIapi/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:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
BR, Eli(Li Yong)Qiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/23dd4886/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: liyong_qiao.vcf
Type: text/x-vcard
Size: 123 bytes
Desc: not available
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20151021/23dd4886/attachment.vcf>
More information about the OpenStack-dev
mailing list