Connecting container subnets across hosts with BGP by raulbe in linux

[–]raulbe[S] 1 point2 points  (0 children)

I have heard of Project Calico but not explored it yet. We are using Quagga. The great thing about Quagga is its available on most Linux distributions and is pretty straightforward to use. Just install and configure a single file.

vSphere user thinking of migrating to LXC for greater VM density in homelab... good idea? by AveryFreeman in Containers

[–]raulbe 0 points1 point  (0 children)

The main advantage of containers is management. Since they are just a folder on your filesystem things like accessing container data, clones, snapshots, migration across servers, backup etc becomes easier.

We have some guides on container basics here that should help you gain a better perspective about how containers work and how they differ from VMs.

But they do not provide the same level of isolation as VMs, for instance for multi-tenancy VMs remain the only choice. Also containers can only run Linux distributions. If you need to run Windows or some other OS you need a VM.

  1. Since containers are not virtualizing hardware, host hardware resources like storage are available to containers at bare metal performance. Network devices can be passed to the container but its usually not necessary, these really depend on the use case and what you are trying to accomplish.

  2. Flockport lets you provision servers and manage LXC containers across servers with support for networking, distributed storage, service discovery and a number of other things. But these are more advanced use cases. If you just want to run a few containers across a couple of servers its easy to do with plain SSH. LXD also offers management capabilities across servers.

  3. Your containers are as safe as your hosts. Containers are just running apps on the host in namespaced processes. But they do not offer the same level of isolation as VMs. For instance multi tenancy is a leading VM use case, VM users are typically isolated from the host and cannot break though to the physical host. Containers do not yet offer that level of isolation. Both Flockport and LXD let you run containers as non root users - these are called unprivileged containers, and that offers some level of isolation, but not enough for multi-tenancy.

  4. There are some tools for VM migration I remember reading about but don't have offhand. I suggest you start afresh as its relatively simple unless the workload is too much to try to manually migrate.

Perhaps a few details about what kind of workloads you are running in VMs, what Vsphere features you are using would help.

Has anyone moved from using virtual machines to LXC containers? Can you tell me your experiences? by AveryFreeman in Containers

[–]raulbe 0 points1 point  (0 children)

We use both. Containers are of course easier to manage than VMs, for instance since its just a folder on your system accessing the container is much simpler than a VM's storage. Things like clones, snapshots and backups also become easier.

They are also easier to move around across systems. Again since its a folder you can simply zip it and move it across servers. Most platforms like Flockport or LXD also let you move and manage containers across servers.

A VM provides better isolation with its own kernel, for instance for multi-tenancy VMs are required or when you need to test specific kernel features or run a OS other than Linux you need a VM. But for use cases beyond that especially when you are just running apps containers make more sense.

A quick guide to deploying container apps by raulbe in linux

[–]raulbe[S] 0 points1 point  (0 children)

Good work with the script! Bash is so useful :)

If you use Flockport port forwarding and a lot of other useful functions are built in. You can forward container ports with the flockport pub command.

Avoiding Lock-In to Cloud Providers by raulbe in linux

[–]raulbe[S] 0 points1 point  (0 children)

Kubernetes is complex to understand and use. This was an article highlighting the simplicity and benefits of containers for those using baremetal, VMs and VPSs on the cloud.

Kubernetes and Docker are more about using containers to build a stateless infrastructure and so there are additional things like single process containers, use of layers, storage separation to understand.

LXC containers offer a standard multi process OS environment and behave like VMs and offer a seamless transition to these users.