questions)
Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under
/bays
I don't see why the existent of /containers endpoint blocks your workflow.
However, with /containers gone, the alternate workflows are blocked.
As a counterexample, some users want to manage contai
> From: Kyle Kelley [mailto:kyle.kel...@rackspace.com]
> Sent: January-19-16 2:37 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under /bays
>
> With /containers gone, what Magnum offer
meaningful and sustainable way.
From: Hongbin Lu
Sent: Tuesday, January 19, 2016 9:43 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under /bays
Assume your logic is applied. Shou
om: Hongbin Lu
Sent: Tuesday, January 19, 2016 9:43 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under /bays
Assume your logic is applied. Should Nova remove the endpoint of managing VMs?
Should Cinder re
e.com]
Sent: January-19-16 5:19 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under /bays
+1
Doing this, and doing this well, provides critical functionality to OpenStack
while keeping said functionality reaso
: OpenStack List
Date: Saturday, 16 January 2016 02:24
To: OpenStack List
Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under /bays
The requirements that running a fully containerized application optimally &
effectively requires the usage of a dedicated COE tool such as S
for usage questions)"
Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under /bays
A reason is the container abstraction brings containers to OpenStack: Keystone
for authentication, Heat for orchestration, Horizon for UI, etc.
From: Kyle Kelley [mailto:rgb...@gmail.co
: [openstack-dev] [magnum] Nesting /containers resource under /bays
What are the reasons for keeping /containers?
On Fri, Jan 15, 2016 at 9:14 PM, Hongbin Lu
mailto:hongbin...@huawei.com>> wrote:
Disagree.
If the container managing part is removed, Magnum is just a COE deployment
tool. T
gt; *From:* Mike Metral [mailto:mike.met...@rackspace.com]
> *Sent:* January-15-16 6:24 PM
> *To:* openstack-dev@lists.openstack.org
>
> *Subject:* Re: [openstack-dev] [magnum] Nesting /containers resource
> under /bays
>
>
>
> I too believe that the /containers endpoin
te Cloud R&D - Rackspace
From: Hongbin Lu mailto:hongbin...@huawei.com>>
Sent: Thursday, January 14, 2016 1:59 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under /bays
I
mp;D - Rackspace
From: Hongbin Lu mailto:hongbin...@huawei.com>>
Sent: Thursday, January 14, 2016 1:59 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under /bays
In sh
through
Magnum’s endpoints.
Hope it is clear.
Best regards,
Hongbin
From: Kyle Kelley [mailto:kyle.kel...@rackspace.com]
Sent: January-14-16 11:39 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under /bays
area until these are put into further use.
From: Hongbin Lu
Sent: Wednesday, January 13, 2016 5:00 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [magnum] Nesting /containers resource under /bays
Hi Jamie,
I
] Nesting /containers resource under
/bays
On 01/13/2016 04:42 AM, Jamie Hannaford wrote:
> I've recently been gathering feedback about the Magnum API and one of
> the things that people commented on was the global /containers
> endpoints. One person highlighted the danger of U
have a bay on creation, such feature is impossible.
Best regards,
Hongbin
From: Jamie Hannaford [mailto:jamie.hannaf...@rackspace.com]
Sent: January-13-16 4:43 AM
To: openstack-dev@lists.openstack.org
Subject: [openstack-dev] [magnum] Nesting /containers resource under /bays
I've recently
On 01/13/2016 04:42 AM, Jamie Hannaford wrote:
I've recently been gathering feedback about the Magnum API and one of
the things that people commented on was the global /containers
endpoints. One person highlighted the danger of UUID collisions:
"""
It takes a container ID which is intended to
I've recently been gathering feedback about the Magnum API and one of the
things that people commented on? was the global /containers endpoints. One
person highlighted the danger of UUID collisions:
"""
It takes a container ID which is intended to be unique within that individual
cluster. Per
17 matches
Mail list logo
