For cloud computing personal experience, I'd approach it in 3 ways:<div><br></div><div>1) Set up a Centos or OpenSuse in your easiest VM program (maybe VMWare Fusion, Workstation, or if you're farther along, KVM (native to Centos > 5.6)</div>
<div><br></div><div>Then write for Centos kickstart scripts and the equillivant in OpenSuse for automated deployment</div><div><br></div><div>2) I would say setup your own VMWare ESXi and then deploy VMS into it, but realisticly if you don't know how the networking is setup in the real world, you could teach yourself something that's too way off.</div>
<div><br></div><div>I'd focus on automated deployments of Linux OS's (particualy Centos and OpenSuse (a la Red Hat and Suse)).</div><div><br></div><div>If you can get that down and already have a history of normal system administration, then at least you can build a server based on the customer's specs <br>
<br><div class="gmail_quote">On Wed, Feb 15, 2012 at 4:33 PM, JD <span dir="ltr"><<a href="mailto:jdp@algoloma.com">jdp@algoloma.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
R u certain <a href="http://openbox.org/" target="_blank">http://openbox.org/</a> is what you meant?<br>
<br>
Perhaps OpenStack, VirtualBox, KVM/QEMU, Xen, OpenVz, LXC, or one of the many,<br>
many VMware virtualization products would help your cloud understanding?<br>
<br>
Nothing against Openbox, I use it with LXDE all the time.<br>
<br>
Or perhaps I'm confused and Box.net was understood by everyone?<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On 02/15/2012 12:34 PM, Mike Thornton wrote:<br>
> Thanks Leam,<br>
> I noticed one of your previous post recommended skills in cloud based<br>
> virtualization,<br>
> so I'm setting up a private cloud with centos and openbox. Thoughts anyone?<br>
> Are there gotcha's I should know about ?<br>
><br>
><br>
> On 2/13/2012 7:39 PM, Leam Hall wrote:<br>
>> On 02/13/2012 07:00 PM, Mike Thornton wrote:<br>
>>> Prelancing is described by some as 'pre-compensation freelancing'. AKA<br>
>>> working for free.<br>
>> Mike,<br>
>><br>
>> I'll chime in with what has worked for me, and a few hopefully useful<br>
>> ideas.<br>
>><br>
>> First, I think your plan is a great one. I started on Linux on an i386<br>
>> that took until 2 AM to compile the kernel. I started because we were so<br>
>> poor I couldn't afford a Windows upgrade. One time my wife splurged and<br>
>> bought me OS2 Warp. Gotta love her, even if the OS is gone...<br>
>><br>
>> My background is sort of similar; as a kid I played with those<br>
>> electronics sets. In the military I worked on old teletype hardware;<br>
>> computers were the "new" thing coming in. After the military I tried<br>
>> some different tracks but found my enjoyment playing with/on my computer.<br>
>><br>
>> I volunteered to help a friend with a Netware based FidoNet BBS. My<br>
>> first remote sysadmin work. I took a class in C, played with Solaris,<br>
>> and my wife got me a Slackware book with a CD. The BBS friend gave me an<br>
>> old Mitsumi single speed cdrom and off I went.<br>
>><br>
>> We moved to Italy and I got a "job" working for an ISP. I mostly<br>
>> volunteered so I could do stuff there; the phone rates were high and<br>
>> speeds were slow. Whenever they asked me if I could do something in<br>
>> Linux, my response was "Oggi no, domani possible." Today, no. Tomorrow,<br>
>> possibly. I'd go home, figure it out, and come back the next day and set<br>
>> it up.<br>
>><br>
>> Came back to the states and found a part-time job doing SCO Unix (uk!)<br>
>> that lasted long enough to get a full time SA position based on<br>
>> experience. Yup. that ISP, the part time SCO job, and the BBS stuff were<br>
>> enough to get me in with the Wall Street Journal. My hiring manager once<br>
>> said he wanted "someone who does this stuff at home" and I fit the bill<br>
>> perfectly.<br>
>><br>
>> To answer your question more directly, look at non-profits, churches,<br>
>> schools, etc. Lots of places don't the the money to buy Windows capable<br>
>> hardware but they need file servers, web servers, etc. Setting up<br>
>> networks wouldn't hurt either. Many places could use web services where<br>
>> they're not charged an arm and a leg for a decent site. They also often<br>
>> have custom needs to resolve and no real backups or recovery postures.<br>
>><br>
>> Another idea for you is to look at the "Go" programming language from<br>
>> Google. It is my feeling that some good things will happen with it and<br>
>> your background seems well suited to utilize a good systems language.<br>
>><br>
>> Really, I think your possibilities are pretty good. Your attitude will<br>
>> be a key ingredient. Don't overlook places like LinkedIn, either.<br>
>><br>
>> Figure out what really energizes you and follow that path. Your<br>
>> happiness will show and help sell you.<br>
>><br>
>> Leam<br>
>> ________________<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</div></div></blockquote></div><br></div>