These days I can have better performance for less money. And I can spent the money in things like pizza, beer and so on in our family money socks. Yeah!

So what’s wrong? Is it too much weird command line kung fu to create such an machine image? Or is there no demand for Gentoo x86_64 images? People don’t use Gentoo anymore since the Gentoo hype was over long before there was AWS? Gentoo people are unaware there is 64bit available and still stick to 32bit? AWS people don’t want Gentoo people to use Gentoo images since the Fedora machine images are much better for everyone? Yeah.

I deceided to roll out my own AMI. I did some research and read lots of articles about the different ways to create those machine images. Twenty minutes later I felt enlightened:

1. You can convert an existing xen image or
2. create your AMI with VMware and convert this or
3. you can use an existing AMI and base your AMI on it and so forth.

Sounds like crap. I like building things by my own and have more control on the inside of the result.
It took some time to figure out how to proceed and how to solve small emerging hurdles.

Working on a good build host it takes maybe twenty to thirty minutes from zero to have a basic AMI ready to go. Basically you need to create the AMI file, format it with some filesystem, mount the file as a loop device, extract an stage3 archive, install some requirements and modify some config files. The most time is wasted waiting for ec2-upload-bundle to complete. It’s enough time to get another cup of coffee, sit on the sofa and read some pages in the newspapers.

I think the result is pretty good already. I have completed different automations and have begun working on the details to create almost autonomous clusters, this is again funny stuff with crons, bash, sed, awk and perl.

EC2 is definitly very interesting. If you need some help with gentoo AMIs you can just sent me an email or put a line in the comments.

All the best, Emil

P.S. If anyone at HP Compaq wants his name eternally remembered – you know what do ;P

So this is some kind of a minimal HowTo, hope this helps someone.

If you are like me, you don’t like the idea to rely on 3rd party websites like younameit.xyz. There are a few good reasons to keep the video on your site – you have the physical control and you don’t need to accept confusing licence agreements. So here we go!

First I piped the output of dvgrab directly from the firewire to ffmpeg. This deinterlaced, converted and scaled the dv file to something more useful for a web page. I think that the following options are fine, feel free to change them and of course make use of man dvgrab and man ffmpeg.

dvgrab -format dv1 – | ffmpeg -deinterlace -f dv -i – -f flv -vcodec flv -s qvga -aspect 1.333 -qscale 3.5 -acodec libmp3lame -ab 32k -ar 22050 example.flv

Next I uploaded the example.flv file into the root directory of the domain. I use the open-source FlowPlayer Flash applet to actually embed the FLV video in my web page. I had to get a copy of the flowplayer.swf and flashembed.js from their page and copied the files to the root directory as well.

And finally I added the following lines to the html page.

<!– include flashembed –>
<script src=”flashembed.js”></script>

<!– this DIV is where your Flowplayer will be placed. –>
<div id=”videodiv” style=”width:640px;height:503px”></div>

<script>
// place Flowplayer to our DIV
flashembed(“videodiv”, “FlowPlayer.swf”, {config: {

// Flowplayer configuration as comma separated list
videoFile: ‘example.flv’,
initialScale: ‘scale’

}});
</script>

That’s it. You should now have your video embedded in your page.