9/05/2015 07:57 PM
Subject: Re: [openstack-dev] [nova-docker] Status update
John,
Good questions. Remarks in-line from the Magnum perspective.
On May 9, 2015, at 2:51 AM, John Garbutt wrote:
On 1 May 2015 at 16:14, Davanum Srinivas wrote:
Anyone still interested in this work? :)
* there&
Adam,
Please follow the discussion on the nova-spec review:
https://review.openstack.org/#/c/128753/
At the moment, we need folks actively watching the project in terms of
reviews, gate/check job failures, keeping up with Nova trunk etc.
Please let me know if you or anyone else is interested.
th
Has there been any decision made on if and when the nova-docker driver will
move back to the Nova tree and out of Stackforge?
-Steve Adams
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack
k Development Mailing List (not for usage questions)"
>
> Date: 17/05/2015 11:28 PM
> Subject: Re: [openstack-dev] [nova-docker] Status update
>
> Good questions Matt and Alex. Currently Magnum creates Bays (places
> that can run containers, or pods of containers, and oth
on 09/05/2015 07:55:47 PM:
>>
>> > From: Adrian Otto
>> > To: "OpenStack Development Mailing List (not for usage questions)"
>> >
>> > Date: 09/05/2015 07:57 PM
>> > Subject: Re: [openstack-dev] [nova-docker] Status update
>> >
ailing List (not for usage questions)"
>
> Date: 09/05/2015 07:57 PM
> Subject: Re: [openstack-dev] [nova-docker] Status update
>
> John,
>
> Good questions. Remarks in-line from the Magnum perspective.
>
> On May 9, 2015, at 2:51 AM, John Garbutt wrote:
ot;
>
> Date: 09/05/2015 07:57 PM
> Subject: Re: [openstack-dev] [nova-docker] Status update
>
> John,
>
> Good questions. Remarks in-line from the Magnum perspective.
>
> On May 9, 2015, at 2:51 AM, John Garbutt wrote:
>
> > On 1 May 2015 at 16:14, Davanum S
On Sat, May 09, 2015 at 04:55:47PM +, Adrian Otto wrote:
> I will also mention that it’s natural to be allergic to the idea of
> nested virtualization. We all know that creating multiple levels of
> hardware virtualization leads to bad performance outcomes.
This seems to paint an overly blea
On Sat, 2015-05-09 at 16:55 +, Adrian Otto wrote:
> I will also mention that it’s natural to be allergic to the idea of
> nested virtualization. We all know that creating multiple levels of
> hardware virtualization leads to bad performance outcomes. However,
> "nested containers" do not carry
On Mon, May 11, 2015 at 10:06 AM, Dan Smith wrote:
> > +1 Agreed nested containers are a thing. Its a great reason to keep
> > our LXC driver.
>
> I don't think that's a reason we should keep our LXC driver, because you
> can still run containers in containers with other things. If anything,
> us
Just as a reminder, not only libvirt-lxc can be used as an os-like
container provider but
also recently added libvirt-parallels driver. And regarding nested
Docker support, we
have just implemented it thus, anyone will be able to use nested
application Docker
containers via libvirt-parallels co
On Mon, May 11, 2015 at 02:57:08PM +0100, John Garbutt wrote:
> On 9 May 2015 at 17:55, Adrian Otto wrote:
> > On the subject of extending the Nova API to accommodate special use cases
> > of containers that are beyond the scope of the Nova API, I think we should
> > resist that, and focus those
> +1 Agreed nested containers are a thing. Its a great reason to keep
> our LXC driver.
I don't think that's a reason we should keep our LXC driver, because you
can still run containers in containers with other things. If anything,
using a nova vm-like container to run application-like containers
On 9 May 2015 at 17:55, Adrian Otto wrote:
> On the subject of extending the Nova API to accommodate special use cases of
> containers that are beyond the scope of the Nova API, I think we should
> resist that, and focus those container-specific efforts in Magnum.
+1
The API is my biggest worry
John,
Good questions. Remarks in-line from the Magnum perspective.
On May 9, 2015, at 2:51 AM, John Garbutt wrote:
> On 1 May 2015 at 16:14, Davanum Srinivas wrote:
>> Anyone still interested in this work? :)
>>
>> * there's a stable/kilo branch now (see
>> http://git.openstack.org/cgit/stack
On 1 May 2015 at 16:14, Davanum Srinivas wrote:
> Anyone still interested in this work? :)
>
> * there's a stable/kilo branch now (see
> http://git.openstack.org/cgit/stackforge/nova-docker/).
> * CI jobs are running fine against both nova trunk and nova's
> stable/kilo branch.
> * there's an upda
Anyone still interested in this work? :)
* there's a stable/kilo branch now (see
http://git.openstack.org/cgit/stackforge/nova-docker/).
* CI jobs are running fine against both nova trunk and nova's
stable/kilo branch.
* there's an updated nova-spec to get code back into nova tree (see
https://rev
17 matches
Mail list logo
