JuJu, LXC, OpenStack charm problem w/Nova & Quantum

[Tim Fall]

Brian,
	I think you’re right about some things here, so let me chime in a bit:

Giant Disclaimer: I work for an OpenStack SDN company.

	You’re point about LXC as a good “base” for cloud use is well taken. My personal feeling is (unbeknownst to my employer) is that non-virtualization offers so much more than virtualization, that it should replace any virtualized systems. But that’s likely another discussion.

	More to this point, I have been working with at least two unnamed large private cloud providers that intend to build their OpenStack deployments onto of LXC, so you may see it in production soon than you think.

	I also agree with you that LXC should be treated as a full-fledged option within Juju. I know it was originally just intended as a way for developers to test charms on their own machines, but it seems much more useful for deployments beyond just what you’ve mentioned.

	As I mentioned before, I do work for an SDN company, so my view may be jaded here, but I would like that VxLAN as a virtualized network solution limits LXC deployments more than it helps. Since LXC supports the OpenVSwitch kernel module, any number of virtualization solutions could take advantage of that to provide networking that is more flexible and scalable than pure VxLAN.

-Tim

On Mar 17, 2014, at 2:05 PM, brian mullan <bmullan.mail at gmail.com> wrote:

> Here are a couple of scenario's for openstack/lxc that I think are interesting.
> 
> ARM x64 cpu are now available and use 1/8th the power of an intel cpu ... given its hard to compare apples to oranges here.
> 
> Ubuntu & LXC can both be used on ARM x64 systems.
> 
> For today's DataCenters the biggest constraint & expense is power.
> 
> I am thinking that running Linux based work-loads in LXC "virtual machines" may, combined ARM x64 cpu, actually perform better than intel cpu w/hw virtualization (kvm, vmware et al) at a much lower power utilization.
> 
> If you are a Cloud SP that can be a big deal.    
> 
> But what if we looked at a end goal and worked backward using some assumptions::
> Linux work-loads only
> JuJu and JuJu-gui... provide seamless cloud, server & application deployment, scaling and network connectivity management.
> LXC is a choice for the virtualizaton
> SDN - OVS (openvswitch), ovsdb and VxLAN supported
> OpenStack, Horizon Gui, Neutron/Quantum networking (via plugins), etc to allow utilization of all of the above
> Networking could become really interesting here.   Implementation of VxLAN support enables a physical server to become a multi-tenant, LXC based "cloud" with point-to-point interconnect to any other like machines/clusters/clouds as a VTEP (Virtual Tunnel End-Point).   
> 
> The beauty of it is that you can have Multiple VTEPs for a single LXC "host" Server.
> 
> Each VTEP "could" be the VxLAN network connection for a different tenant's "cloud" of lxc based applications managed by Nova on that server.
> This has a good overview of OpenStack over VxLAN:    
> 
> http://www.openstack.org/assets/presentation-media/OpenStackOverVxlan.pdf
> 
> 
> Staying focused on my original post regarding the possibilities "if you could" use OpenStack to manage an LXC based "cloud" interconnected via an SDN VxLAN network setup.
> 
> The above URL describes how to configure VxLAN via OpenStack using Neutron (sorry I realized in prev email's I was still calling it Quantum).
> 
> -- 
> Juju mailing list
> Juju at lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/juju

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20140317/db0ad177/attachment-0001.html>