1 |
On 8 April 2015 14:43:02 GMT-07:00, lee <lee@××××××××.de> wrote: |
2 |
>hydra <hydrapolic@×××××.com> writes: |
3 |
> |
4 |
>> On Sat, Apr 4, 2015 at 3:20 PM, lee <lee@××××××××.de> wrote: |
5 |
>> |
6 |
>>> symack <symack@×××××.com> writes: |
7 |
>>> |
8 |
>>> Other than that, unless you really do need full virtualization: I'm |
9 |
>>> finding Linux containers to be far more manageable than virtual |
10 |
>>> machines, and much more efficient. |
11 |
>>> |
12 |
>>> |
13 |
>> Can you please post some more details? |
14 |
> |
15 |
>About containers? |
16 |
> |
17 |
>There's very useful documentation about them like |
18 |
>https://wiki.gentoo.org/wiki/LXC ... |
19 |
> |
20 |
>What can I say? Virtualization with xen is like juggling with a set of |
21 |
>black boxes each of which aren't exactly accessible; the |
22 |
>documentation sucks, it's hard work to get it running and likewise hard |
23 |
>to maintain. |
24 |
|
25 |
I disagree. Been using Xen for over 10 years now and find it very easy to use. |
26 |
The documentation could be better on the Xen site itself, but there is plenty of decent documentation available via Google. |
27 |
|
28 |
>Virtualization with containers is basically as simple as running just |
29 |
>another daemon. |
30 |
|
31 |
Not quite. I use virtualization to minimizer the physical hardware. Xen is easy for that. Containers are what chroot jails should have been. |
32 |
But there is no simple method to set these up when security isolation is your goal. |
33 |
|
34 |
>Which the "better" tool, or combination of tools is, depends on what |
35 |
>you |
36 |
>want to accomplish. You could use containers in a VM, too, or use |
37 |
>virtualbox along with containers to run the odd VMs that require full |
38 |
>virtualzation. |
39 |
|
40 |
Virtualbox is nice for a quick test. I wouldn't use it for production. |
41 |
|
42 |
-- |
43 |
Joost |
44 |
|
45 |
|
46 |
-- |
47 |
Sent from my Android device with K-9 Mail. Please excuse my brevity. |