Open Stack

Again, a conversation that should include the ops list.

On Wed, May 13, 2015 at 6:28 AM, Adrian Otto <adrian.otto at rackspace.com>
wrote:

>  Solum uses it in our Vagrant setup. It makes the dev environment perform
> very nicely, and is compatible with the Docker containers Solum generates.
>
>
>
>  Sent from my Verizon Wireless 4G LTE smartphone
>
>
> -------- Original message --------
> From: John Griffith <john.griffith8 at gmail.com>
> Date: 05/12/2015 9:42 PM (GMT-08:00)
> To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org>
> Subject: Re: [openstack-dev] Who is using nova-docker? (Re: [nova-docker]
> Status update)
>
>
>
> On Tue, May 12, 2015 at 12:09 PM, Fawad Khaliq <fawad at plumgrid.com> wrote:
>
>>
>> On Mon, May 11, 2015 at 7:14 PM, Davanum Srinivas <davanum at gmail.com>
>> wrote:
>>
>>> Good points, Dan and John.
>>>
>>> At this point it may be useful to see who is actually using
>>> nova-docker. Can folks who are using any version of nova-docker,
>>> please speak up with a short description of their use case?
>>>
>>  I am using Kilo in a multi-hypervisor mode, some applications running
>> on Docker containers and some backend work provisioned as VMs.
>>
>>>
>>> Thanks,
>>> dims
>>>
>>> On Mon, May 11, 2015 at 10:06 AM, Dan Smith <dms at danplanet.com> 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,
>>> > using a nova vm-like container to run application-like containers
>>> inside
>>> > them is going to beg the need to tweak more detailed things on the
>>> > vm-like container to avoid restricting the application one, I think.
>>> >
>>> > IMHO, the reason to keep the seldom-used, not-that-useful LXC driver in
>>> > nova is because it's nearly free. It is the libvirt driver with a few
>>> > conditionals to handle different things when necessary for LXC. The
>>> > docker driver is a whole other nova driver to maintain, with even less
>>> > applicability to being a system container (IMHO).
>>> >
>>> >> I am keen we set the right expectations here. If you want to treat
>>> >> docker containers like VMs, thats OK.
>>> >>
>>> >> I guess a remaining concern is the driver dropping into diss-repair
>>> >> if most folks end up using Magnum when they want to use docker.
>>> >
>>> > I think this is likely the case and I'd like to avoid getting into this
>>> > situation again. IMHO, this is not our target audience, it's very much
>>> > not free to just put it into the tree because "meh, some people might
>>> > like it instead of the libvirt-lxc driver".
>>> >
>>> > --Dan
>>> >
>>> >
>>> __________________________________________________________________________
>>> > 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
>>>
>>>
>>>
>>> --
>>> Davanum Srinivas :: https://twitter.com/dims
>>>
>>>
>>> __________________________________________________________________________
>>> 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
>>>
>>
>>
>> __________________________________________________________________________
>> 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
>>
>>  ​I'm using nova-docker, started out as just learning the pieces...
> ended up being useful for some internal test and dev work on my side.
> Including building/shipping apps to customers that I used to send out as
> qcows.  I could certainly do this without nova-docker and go straight to
> docker, but this is "more fun", and fits with my existing workflow/usage of
> OpenStack for various things.
>
>  Also FWIW Magnum currently is way overkill for what I'm doing, just like
> some other projects.​  I do plan to check that out before long, but for now
> it's a bit overkill for me.
>
>
> __________________________________________________________________________
> 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-operators/attachments/20150514/011d136e/attachment.html>