on how
this would work.
Ton Ngo,
From: Hongbin Lu <hongbin...@huawei.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Date: 12/09/2015 03:09 PM
Subject: Re: [openstack-dev] Mesos Con
(not for usage questions)
Subject: Re: [openstack-dev] Mesos Conductor using container-create operations
I think extending the container object to Mesos via command like
container-create is a fine idea. Going into details, however, we run into some
complication.
1. The user would still have to choose
As Bharath mentioned, I am +1 to extend the "container" object to Mesos bay. In
addition, I propose to extend "container" to k8s as well (the details are
described in this BP [1]). The goal is to promote this API resource to be
technology-agnostic and make it portable across all COEs. I am
[1]https://review.openstack.org/#/c/252789/
From: bharath_...@hotmail.com
To: openstack-dev@lists.openstack.org
Date: Wed, 9 Dec 2015 10:10:17 +0530
Subject: [openstack-dev] Mesos Conductor using container-create operations
Hi,
As we have discussed in last meeting, we cannot continue with
