<div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">Definitely DevOps. VM managers like proxmox, vmware etc. are going to be overkill. </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">You'll probably spend way too much time trying to figure out how to configure/use the </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">manager rather than the real work which is the LAMP server config. Because your </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">running Linux you really have 2 options: 1) build VM's on a hypervisor (VirtualBox on top of Linux) </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">or; 2) build VM's using LXC containers (native to the Linux kernel). Each has pros and cons. </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">Hypervisor - VirtualBox</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">Pros:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">- Easy to implement and configure.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">- More tutorials online to help with.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">- File sharing between guest and host systems built in.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">Cons:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">- Hypervisor takes up RAM and CPU resources</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">- File sharing can be very slow.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">- File sharing large qty's of files can be problematic.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">LXC containers with Docker</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">Pros:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">- Much smaller resource foot print on OS </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">- Extremely fast </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">Cons:</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">- Not as many tutorials </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">- Harder to implement </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">- File sharing not as simple.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">While there are ways to mitigate the Cons of both cases, IMHO containers are the future. </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">They have so many advantages that save space, overhead, and power consumption</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">in servers and now that Docker has made them much easier to implement they will be the </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">norm in a few years. But VirtualBox is still easily the solid leader in DevOps use cases </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">especially in smaller workflows.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">As I said My workflow for server builds is Vagrant -> VirtualBox -> Puppet or BASH = New server.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">Now that I use Vagrant and Puppet I will never build another server from scratch again period.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">I have avery simple LAMP dev sever script on GitHub here that you are welcome to use modify steal whatever.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">It is very basic. Vagrant initializes the box and hands it off to BASH as the provisioner. I use this for</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">Drupal sandbox servers. It works thought the BASH needs work and there are things that could be </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)">added/altered especially to make it idempotent. </div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small;color:rgb(11,83,148)"><br></div><div class="gmail_default" style><font color="#0b5394" face="arial, helvetica, sans-serif"><a href="https://github.com/netwidget/vagrant-bash-webserver/blob/master/centos64-webserv.sh">https://github.com/netwidget/vagrant-bash-webserver/blob/master/centos64-webserv.sh</a></font><br></div><div class="gmail_default" style><font color="#0b5394" face="arial, helvetica, sans-serif"><br></font></div><div class="gmail_default" style><font color="#0b5394" face="arial, helvetica, sans-serif">Good luck, hope this helps.</font></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 9, 2014 at 4:19 PM, <span dir="ltr"><<a href="mailto:techlists@phpcoderusa.com" target="_blank">techlists@phpcoderusa.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
The testing I want to do is simple. I want to be able to test current PHP apps (ones I support) on future versions of Apache, PHP, MariaDB. I am on the CentOS upgrade path and would like to do some testing to include CentOS 7.x and the versions of Apache, PHP, MariaDB before they are included in the upgrade path. Basically I want to get way ahead of any issues so I will have plenty of time to resolve them before I am required to by an O/S upgrade or a change in distro.<br>
<br>
I am thinking I will install the complete Mint 17 KDE on the test server and load Virtualbox on to that. That way I can stay consistent between by desktop and laptop. I'm hoping I can do the experimenting on the server so if I hose it I can just rebuild it. Once I find what I want I can test it and if I want to take it with me on the go I can copy the image to my laptop. This way my desktop and laptop stay stable.<br>
<br>
Any thoughts are much appreciated.<div><div class="h5"><br>
<br>
<br>
<br>
On 2014-10-09 17:16, James Dugger wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
It depends. What is the purpose of your testing? Proxmox, is a virtual<br>
server manager, much like VMware ESXi & XenServer they simply manage<br>
and monitor VM's. I would use (and have used) Proxmox to manage<br>
servers in a VLAN (just one example). However if you are<br>
developing/configuring LAMP servers and testing them individually for<br>
optimization (more DevOps) I would stay with VirtualBox (or Docker<br>
assuming your bare metal Linux kernel has LXC, kernel 3.0 or later)<br>
and look into provisioning with Vagrant, Chef, Puppet, Ansible,<br>
SaltStack or even BASH. Vagrant builds the base box and then hands<br>
it off to a provisioner.<br>
<br>
To give you an example currently at my work we develop and maintain<br>
large enterprise web applications on LAMP servers. One of our<br>
systems consist of a Blade enclosure (bare metal),<br>
OS/Hypervisor/manager is VMware ESXi, running VM's configured in a<br>
VLAN. On top of this we use Vagrant and Puppet to provision, test,<br>
implement, & destroy LAMP servers as we need them. Because we<br>
maintain the entire LAMP config in code we can version control all of<br>
our servers in Git plus the base box (pick your distro). The entire<br>
versioned codebase including the base ISO's can fit on a 32GB usb<br>
drive. I can rebuild these LAMP servers on any environment as long<br>
as it has enough physical memory and compute speed. regardless of the<br>
hypervisor/vm manager.<br>
<br>
Don't know if this helps, but just thought I'd share a perspective.<br>
<br>
Check out:<br></div></div>
Vagrant - <a href="https://www.vagrantup.com/" target="_blank">https://www.vagrantup.com/</a> [5]<br>
<br>
Puppet -<br>
<a href="http://info.puppetlabs.com/download-puppet-enterprise-PPC-1.html?utm_source=google&utm_medium=cpc&utm_campaign=Blu-Jae_Puppet&gclid=CjwKEAjw5NihBRCZmdLkuuTHyWYSJACtCY0JoA5k8d3FtnsJ-Lb9DOKsKGCBo2AXRRB37aqC49xN-RoCnIfw_wcB" target="_blank">http://info.puppetlabs.com/<u></u>download-puppet-enterprise-<u></u>PPC-1.html?utm_source=google&<u></u>utm_medium=cpc&utm_campaign=<u></u>Blu-Jae_Puppet&gclid=<u></u>CjwKEAjw5NihBRCZmdLkuuTHyWYSJA<u></u>CtCY0JoA5k8d3FtnsJ-<u></u>Lb9DOKsKGCBo2AXRRB37aqC49xN-<u></u>RoCnIfw_wcB</a><br>
[6]<br>
<br>
Docker - <a href="https://www.docker.com/" target="_blank">https://www.docker.com/</a> [7]<span class=""><br>
<br>
On Thu, Oct 9, 2014 at 12:43 PM, <<a href="mailto:techlists@phpcoderusa.com" target="_blank">techlists@phpcoderusa.com</a>> wrote:<br>
<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
Thanks!!<br>
<br>
On 2014-10-09 14:23, Sean Roe wrote:<br>
Im going to have to go with JD. Proxmox is the best opensource VM<br>
solution period.<br>
Sean<br>
<br>
On Thu, Oct 9, 2014 at 11:40 AM, JD Austin <<a href="mailto:jd@twingeckos.com" target="_blank">jd@twingeckos.com</a>><br>
wrote:<br>
<br>
Proxmox, your preferred Linux OS with Virtualbox, or using your<br>
preferred Linux OS's KVM/Qemu virtualization will all work about as<br>
well. Proxmox gives you a nice interface to manage it all; there<br>
are some 'free' VMWare versions you can use as well. <br>
<br>
-- JD Austin<br></span>
Voice: <a href="tel:480.269.4335" value="+14802694335" target="_blank">480.269.4335</a> [1] [1] (480 2MY Geek)<div><div class="h5"><br>
<a href="mailto:jd@twingeckos.com" target="_blank">jd@twingeckos.com</a><br>
<br>
On Thu, Oct 9, 2014 at 11:12 AM, <<a href="mailto:techlists@phpcoderusa.com" target="_blank">techlists@phpcoderusa.com</a>> wrote:<br>
<br>
I provided the wrong specs here is the specs of the box I want to<br>
use<br>
<br>
i3-3220 with visualization <br>
<br>
<br>
</div></div></blockquote><div><div class="h5">
<a href="http://ark.intel.com/products/65693/Intel-Core-i3-3220-Processor-3M-Cache-3_30-GHz" target="_blank">http://ark.intel.com/products/<u></u>65693/Intel-Core-i3-3220-<u></u>Processor-3M-Cache-3_30-GHz</a><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[2]<br>
[2]<br>
<br>
8GB RAM.<br>
<br>
Thank you for your help!!<br>
<br>
Keith<br>
<br>
On 2014-10-09 13:01, <a href="mailto:techlists@phpcoderusa.com" target="_blank">techlists@phpcoderusa.com</a> wrote:<br>
Hi,<br>
<br>
I'd like to configure a test box for LAMP development. What I<br>
have in<br>
mind is setting up multiple VM's on the box and loading a different<br>
distro in each VM. Probably only need 2 or 3 VMs. The number<br>
might<br>
grow over time. Will not be configuring X on any of the VM's -<br>
they<br>
will be LAMP servers only.<br>
<br>
I seem to recall someone saying I would need a base system on the<br>
box<br>
and then load the VM's on top of that. Or can I use something<br>
like<br>
Mint and load the VM's on top of that? Is there a disadvantage to<br>
doing it with Mint as the base system?<br>
<br>
The box is an i3 with visualization -<br>
<br>
<br>
</blockquote>
<a href="http://ark.intel.com/products/81018/Intel-Core-i3-4030U-Processor-3M-Cache-1_90-GHz" target="_blank">http://ark.intel.com/products/<u></u>81018/Intel-Core-i3-4030U-<u></u>Processor-3M-Cache-1_90-GHz</a><br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
[3]<br>
[3]<br>
It has 4GB of RAM which I assume might not be enough.<br>
<br>
This box will only be used for testing so I assume each VM will<br>
only<br>
need 1GB of RAM and will probably use much less.<br>
<br>
Any direction is much appreciated.<br>
<br>
Thanks!!<br>
<br>
Keith<br>
------------------------------<u></u>---------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.<u></u>org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
</div></div><a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/<u></u>mailman/listinfo/plug-discuss</a> [4] [4]<span class=""><br>
------------------------------<u></u>---------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.<u></u>org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
</span><a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/<u></u>mailman/listinfo/plug-discuss</a> [4] [4]<span class=""><br>
<br>
------------------------------<u></u>---------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.<u></u>org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br></span>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/<u></u>mailman/listinfo/plug-discuss</a> [4] [4]<br>
<br>
Links:<br>
------<br>
[1] tel:<a href="tel:480.269.4335" value="+14802694335" target="_blank">480.269.4335</a> [1]<br>
[2]<br>
<br>
</blockquote>
<a href="http://ark.intel.com/products/65693/Intel-Core-i3-3220-Processor-3M-Cache-3_30-GHz" target="_blank">http://ark.intel.com/products/<u></u>65693/Intel-Core-i3-3220-<u></u>Processor-3M-Cache-3_30-GHz</a><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[2]<br>
[3]<br>
<br>
</blockquote>
<a href="http://ark.intel.com/products/81018/Intel-Core-i3-4030U-Processor-3M-Cache-1_90-GHz" target="_blank">http://ark.intel.com/products/<u></u>81018/Intel-Core-i3-4030U-<u></u>Processor-3M-Cache-1_90-GHz</a><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
[3]<br>
[4] <a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/<u></u>mailman/listinfo/plug-discuss</a> [4]<span class=""><br>
<br>
------------------------------<u></u>---------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.<u></u>org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/<u></u>mailman/listinfo/plug-discuss</a> [4]<br>
</span></blockquote><span class="">
<br>
------------------------------<u></u>---------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.<u></u>org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/<u></u>mailman/listinfo/plug-discuss</a> [4]<br>
<br></span>
--<br>
<br>
James<br>
<br>
LINKEDIN [8]<span class=""><br>
<br>
<br>
Links:<br>
------<br>
[1] tel:<a href="tel:480.269.4335" value="+14802694335" target="_blank">480.269.4335</a><br>
[2]<br>
<a href="http://ark.intel.com/products/65693/Intel-Core-i3-3220-Processor-3M-Cache-3_30-GHz" target="_blank">http://ark.intel.com/products/<u></u>65693/Intel-Core-i3-3220-<u></u>Processor-3M-Cache-3_30-GHz</a><br>
[3]<br>
<a href="http://ark.intel.com/products/81018/Intel-Core-i3-4030U-Processor-3M-Cache-1_90-GHz" target="_blank">http://ark.intel.com/products/<u></u>81018/Intel-Core-i3-4030U-<u></u>Processor-3M-Cache-1_90-GHz</a><br>
[4] <a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/<u></u>mailman/listinfo/plug-discuss</a><br></span>
[5] <a href="https://www.vagrantup.com/" target="_blank">https://www.vagrantup.com/</a><br>
[6]<br>
<a href="http://info.puppetlabs.com/download-puppet-enterprise-PPC-1.html?utm_source=google&utm_medium=cpc&utm_campaign=Blu-Jae_Puppet&gclid=CjwKEAjw5NihBRCZmdLkuuTHyWYSJACtCY0JoA5k8d3FtnsJ-Lb9DOKsKGCBo2AXRRB37aqC49xN-RoCnIfw_wcB" target="_blank">http://info.puppetlabs.com/<u></u>download-puppet-enterprise-<u></u>PPC-1.html?utm_source=google&<u></u>amp;utm_medium=cpc&utm_<u></u>campaign=Blu-Jae_Puppet&<u></u>gclid=<u></u>CjwKEAjw5NihBRCZmdLkuuTHyWYSJA<u></u>CtCY0JoA5k8d3FtnsJ-<u></u>Lb9DOKsKGCBo2AXRRB37aqC49xN-<u></u>RoCnIfw_wcB</a><br>
[7] <a href="https://www.docker.com/" target="_blank">https://www.docker.com/</a><br>
[8] <a href="http://www.linkedin.com/pub/james-h-dugger/15/64b/74a/" target="_blank">http://www.linkedin.com/pub/<u></u>james-h-dugger/15/64b/74a/</a><span class=""><br>
<br>
------------------------------<u></u>---------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.<u></u>org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/<u></u>mailman/listinfo/plug-discuss</a><br>
</span></blockquote><div class="HOEnZb"><div class="h5">
------------------------------<u></u>---------------------<br>
PLUG-discuss mailing list - <a href="mailto:PLUG-discuss@lists.phxlinux.org" target="_blank">PLUG-discuss@lists.phxlinux.<u></u>org</a><br>
To subscribe, unsubscribe, or to change your mail settings:<br>
<a href="http://lists.phxlinux.org/mailman/listinfo/plug-discuss" target="_blank">http://lists.phxlinux.org/<u></u>mailman/listinfo/plug-discuss</a></div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr"><font color="#0b5394">James</font><div><br><span style="color:rgb(255,255,255)"><span style="background-color:rgb(11,83,148)"><b><a href="http://www.linkedin.com/pub/james-h-dugger/15/64b/74a/" target="_blank"><span style="background-color:rgb(255,255,255)"><span></span><span style="color:rgb(11,83,148)">Linkedin<span></span></span></span></a></b></span></span><br></div></div>
</div>