You are here
Announcing TurnKey OpenVZ optimized builds (+ Proxmox VE channel)
OpenVZ and Proxmox VE has been a recurring topic of discussion on the forums, for which we have Jeremy to blame thank. He's done tons of research, testing, preaching, and then some.
What I love about Open Source is that if you have an itch, and the drive to scratch it yourself, you can.
That's exactly what Jeremy and Adrian did. They wanted OpenVZ optimized builds for their Proxmox VE deployments, so they developed a TKLPatch that would convert an ISO into an OpenVZ container. And if that wasn't enough, took the time to upload some of the builds to sourceforge so it would be easier for others to leverage their work.
Hats off to you guys, you rock!
TurnKey OpenVZ optimized builds
Based on Adrian's and Jeremy's work, we were able to add OpenVZ support to our build infrastructure in no time, and after some initial testing, triggered the whole appliance library to be built as optimized OpenVZ containers.
You can get them from the "Download -> More Builds" link on the appliance pages.
Pre-seeding / default passwords
Because OpenVZ builds are used in headless deployments (without a console), they include an inithook which preseeds default values and passwords (excluding the root password which is handled by the VZ CLI tools).
/usr/lib/inithooks/firstboot.d/29preseed DB_PASS=turnkey APP_PASS=turnkey APP_EMAIL=admin@example.com APP_DOMAIN=DEFAULT HUB_APIKEY=SKIP SEC_UPDATES=FORCE
Depending on your use case, you can preseed the values before the system is booted for the first time, or once the system has booted by executing turnkey-init.
It would be great if someone would add preseeding support to PVE...
TurnKey Proxmox VE channel
A while back the Proxmox folks came up with the idea of adding a TurnKey channel to PVE, to allow users to download TKL appliances in the same way their custom built appliances are downloaded.
It was a great idea, but unfortunately it never got off the ground.
As I mentioned above, the great thing about Open Source is that you can scratch your own itch, and I was curious how the channel mechanism worked - so I dived in. When I came up for air I had added minimal third party channel support and a TurnKey Linux channel (github).
What this basically means is you can now download and deploy any TurnKey appliance on your PVE server in a couple of clicks without leaving your browser.
I hope to see this integrated in the upcoming PVE 2.0 release [update: it's coming...]. If you're running PVE 1.9 then you can add the TurnKey channel as follows:
cd /usr/share/perl5/PVE mv APLInfo.pm APLInfo.pm.bak wget https://raw.github.com/turnkeylinux/pve-patches/master/PVE/APLInfo.pm # update appliance list pveam update
Comments
Are you using PVE v1.9?
Because it works fine for me on my v1.9 host:
And the TKL entries are now there under 'Appliance Templates' >> Download.
I don't think you can do anything 'wrong'
It's pretty much a case of copy/paste the commands (the beauty of CLI). So I would suspect that something is not quite right in your PVE install. Did you install from a 1.9 ISO, or did you update from an earlier ISO install, or did you install on top of Debian? Probably the first thing I'd try is to make sure that you have everything up to date. See here (it details upgrading to 1.9 from an earlier release, but should still apply in your instance).
That is so cool! :)
I'm loving it Alon! :)
And I think your solution to the firstboot passwords is the best (and quite obvious in retrospect).
Nice work all round. Thanks heaps.
Unfreaking-believable!
Absolutely love it! No more downloading the ISO, uploading it to PVE and then getting it going!
It all makes sence looking back on how PVE works but I never connected the dots.
Have you guys seen the beta for 2.0?
I barely got it running and started to play with it when I got called away to something else but I could not see immediatly any similarity.
Keep it going guys! Awesome work!
Chris Musty
Director
Specialised Technologies
Thanks for the cool
Thanks for the cool work.
Maybe this is the kick in the pants I need to try out ProxMox VE. I have a server all set to install but haven't given it a whirl yet because I am so familiar with ESXi. Maybe today.
EDIT: Just a heads up for anyone else wanting to trying this and planning on using the ProxMox VE 2.0 beta. As of beta3... appliance templates are not visible in the UI yet.
First Crack
Had a go at it and am a happy camper.
Now I can download ISO's directly to PVE!!!
w00t!!!
Chris Musty
Director
Specialised Technologies
I reckon Chris means OVZ template
And if he doesn't then he knows something I don't!
:-)
ok when i typed that i was creating an iso for a client.
Chris Musty
Director
Specialised Technologies
Oh Snap.
I also had to ignore certification, but no big deal. I'm downloading a VZ now, and excited to give it a go.
This is so handy it makes me feel like I got away with something. Turnkey, you make me look like I know what I'm doing. :)
Thanks!
Great added resource to another great resource, Thanks for working this out.
TurnKey channel to be integrated by default in PVE 2.0
Martin just announced that the TurnKey channel will be integrated by default in PVE 2.0, and is already available in PVE 2.0rc1.
Fantastic news Alon! :)
Yay! I'm excited!
Personally I think this is a huge win for both projects and their communities. TKL users wanting a solid base for deploying multiple TKL appliances to hardware have a fantastic OOTB option in PVE. And PVE users have an almost too easy way to access a huge range of ready-to-run TKL OVZ templates at their fingertips, without even leaving the PVE WebUI!
IMO this is the power of open source in action and great to see this sort of cross polination between projects. I think this will have flow on benefits for both PVE and TKL, and I would imagine increased exposure to both.
Thanks again for your efforts on this front Alon. And what great timing too. This will mean that from the first stable release, PVE will include access to TKL templates OOTB. Yay! Can you tell I'm excited? :D
I guess I'll have to have a proper test of PVE v2.0 now then! :)
Perhaps...?
But only one way to find out! I'm inclined to ask why you are still running v1.6...
Problems with update
Apreciate help
Yo solo se que no se nada...
Castris Hosting
Not sure what's happening for you
Mine is working ok this morning:
Have you retried it?
Guessing you probably found the answer by now...
Because it is readily available info (although in fairness not quite so obvious from OVZ builds because no confconsole auto running). Anyway it is port 12321 (https only).
What do you mean "could not get to it"?
Do you mean that you can't login as the Admin user?
I just downloaded the TKL Magento OVZ template from the PVE2 WebUI and it all seemed to be going ok, until I tried to log in. It wouldn't let me log in. I tried resetting the login info a few times (turnkey-init) and no dice. I even tried the 'forgot password' link and the email said it sent but I never got it.
Out of interest I launched a Small TKL Magento instance on AWS and same deal!? So I'm not sure what's going on...?!
I've had a bit of a dig through the firstboot scripts and I think this may be a bug. But I'm not sure. If what I think is going on is right, then others should have complained about this previously and it's not just limited to OVZ installs, all Magento appliances should be affected.
I'm tired and going to bed now so not going to do anymore hunting. Some links that may (or may not) be of use are here:
http://www.magentocommerce.com/boards/viewthread/272236/
http://www.magentocommerce.com/boards/viewthread/4957/
http://www.magentocommerce.com/wiki/recover/resetting-admin-password
Need to run 'turnkey-init'
Because OVZ appliances don't have a true console, firstboot scripts don't run properly (they cause Webmin and other services to hang because they run and wait for input but there is no way to access the dialog to provide the input).
As a workaround, firstboot scripts don't auto run in OVZ templates, they need to be run manually. Hence the 'turnkey-init' script. By running turnkey-init all the firstboot scripts that run automatically when appliances are installed in other mediums (such as ISO install, VM image, etc) are triggered (with the exception of setting the root account password as that is done prior to boot on the host OS).
But as I said, even after running the firstboot scripts I still couldn't login (to the Magento appliance). Not sure why? I'd be interested to hear your experience.
TurnKey Core 12.0rc now available in TurnKey PVE channel
Following the announcement of TurnKey Core 12.0rc (ISO , Amazon EC2), we've released an OpenVZ optimized build which is available in the TurnKey PVE channel. You can force the channels update as follows (or wait for the daily refresh):
If you come across any issues, or have ideas on improving the optimized build, please post a comment.
Changes from TurnKey 11.3 OpenVZ optimized builds:
How about a video??
Jeremy, if you'd do a video tutorial I'll nominate you to the Academy Award! A step by stepper would be perfect!! Let us know when you create it! I've installed ProxMox 2.1 and am having some basic problems wrapping my head around setting things up. I've been around for what seems like ages, but virtualization is a completely new concept for me. Thanks for your service!! Let me know where to send the pizza! Ric
Officebox or Datacenter video?
I have toyed with the idea of doing a video for a while so I can get others to set up PVE without me being there.
I use mine predominately in my office for speed and cost then deploy to the cloud so the setup I do will probably not suit everyone.
If I can get a list of what should be included I will have a crack at a video!
Anything else (this list is just top of my head)?
PS if I setup one in a data center it will take me some time to organise the server (and cost money) so may take alot longer!
Chris Musty
Director
Specialised Technologies
Good on you Chris!
I think that'd be awesome. My personal opinion is that an officebox setup would be more generally useful, especially for newbs that just want to have a play. Also with TKLBAM transfering to the cloud (eg AWS) is pretty straightforward.
Will do it tonight
During geek hour tonight 9PM+ 12/7/12 AEST when the kids are in bed I will setup an old laptop.
Thinking more about the datacenter setup, its probably not going to be what everyone needs so I will just do a quick and dirty office (home) setup. This will exclude all the DNS, hostname and more advanced settings and concentrate on just provisioning a service on the home/office network.
I will also just concentrate on containers and skip ISO's for another day, purely for brevity.
So I will cover
Chris Musty
Director
Specialised Technologies
Sounds perfect
That sounds ideal I think and is probably what most TKL users would be looking for. I look forward to seeing how you go with it.
CamStudio makes huge files!
Just did it with cam studio and have a 1Gb file!!!
I am converting it right now but I was surprised.
Does anyone use anything better for screen capture?
Will upload the tutorial as soon as its shrunk to a respectable net freindly size!
Chris Musty
Director
Specialised Technologies
Here It Is!
I am sorry for the quality but after I shrunk the size things got fuzzy, audio is fine (especially considering I am using a cheap logitec webcam!).
There is a little rambling and I get a little toungue tied but the process is there.
Hope someone benefits from it.
http://dl.dropbox.com/u/20051174/ProxmoxContainers.zip
PS After converting it to mwv and zipping it is 77Mb - hope noone has dialup!
Chris Musty
Director
Specialised Technologies
Youtube limit is 10 mins
so when I do a more professional one and edit out the boring bits makiing it less than 10 mins I will youtube it. (currently it is 1 second shy of 24 mins.)
This video was done completely unplanned and is full of babble but hopefully it will get someone going!
Chris Musty
Director
Specialised Technologies
Where do I send the pizza?
I can't help with the hardware budget, but I can feed you! I think you have all the elements that needs to be covered there. This is NEW to me and I'm getting confused with the new jargon that comes with new territory. Thanks! I hope you do this soon. I know you all will do a great job. Ric
Long way for a pizza!
When you hear my accent you will know immediatly where I am from.
Virginia to New South Wales (Australia) would be a heck of a trip for a pizza.
I wonder if it will take longer than 30 mins (and hence be free?)...
Chris Musty
Director
Specialised Technologies
Long way for a pizza!
No worries Mate! I have friends in low places all over. Some of my rowdiest online friends are from AussieLand and New Zealand. We'll get a pizza to you somehow. If a kangaroo knocks at the door, let him in. Ric
:) Ric
Missed some things
Not critical but while you have putty open (or the console) you can initialise with you API key so you can do TKLBAM backups. Just type tklbam init XXXXXXXXXXX and you will be linked with your account.
I may even redo it later because the video quality is crap.
Chris Musty
Director
Specialised Technologies
That video helped me a lot!
Thanks! Yes, the video quality could have been better, but it would have been a huger dnload. I did get what I needed to know. I was letting DHCP assign the IP addresses which kept moving around. Thanks! Ric
Next video??
I hope you keep on producing videos. That really helped me iron out several issues. Thanks again. Ric
Video Requests
Made a new topic for some ideas for tutorials - http://www.turnkeylinux.org/forum/general/20120719/video-tutorials
Chris Musty
Director
Specialised Technologies
TurnKey 12.1 now available in PVE channel + initialization fence
Following the announcement of 12.1, we've updated the TurnKey PVE channel with the new appliances, both 32-bit and 64-bit. You can force the channels update as follows (or wait for the daily refresh):
/usr/bin/pveam updateAs noted in the announcement, 12.1 comes with the 'headless initialization fence' which leverages iptables to create a sort of virtual fence around an appliance
In PVE 1.9 (please leave a comment if this is also true in later versions), the default configuration doesn't support VM iptables, so the fence won't be created. The fix is simple though (source):
Edit /etc/vz/vz.conf, comment out the default IPTABLES and add the following:
Then restart the service:
/etc/init.d/vz restartGlad you got it sorted!
Thanks for the feedback! :)
Glad to hear that you like our work!
If you have any questions/advice/etc please feel free to post in our forums. Bugs and feature requests go on our GitHub based Issue tracker. All of the appliance specific code can also be found on GitHub.
Thanks for using TurnKey!
BTW your English is fine, if you hadn't have added the footnote I never would have guessed that English wasn't your first language! :)
Sorry I missed you post (all those years ago)
Wrong Checksum
From Proxmox, downloaded Turnkey - Core 14.2-1 LXC and get this at the end. Any ideas?
additional page links are a bug :(
FWIW the additional page links on blog posts is a bug that started after our most recent website upgrade (wasn't initially noticed and we haven't been able to fix it yet).
Also sorry that I missed your post. FWIW new posts on old blog posts often slip through the cracks. Generally a new post in the forums is much better at getting attention.
Regarding your issue, TBH I'm unclear, and it's not one that I've hit. Although it is worth noting, that we only actively support the latest version of Proxmox (and the latest v15.x appliances). So I'm guessing that you must be running PVE v4.x (rather than the current v5.x). I'm almost certain that if you update to v5.x, then it should all "just work" (although you won't be able to get v14.x appliances, only v15.x).
Having said that, you can manually download our appliances for Proxmox, like this:
Then read the instruction in the hash file to (optionally) check that you have the legitimate file (the hash file should be signed by us) and that the image is not corrupt (via the hashes). Although, it's also worth noting, that whilst I did do early testing of v15.0 on PVE v4.x, I updated to v5.x prior to the official v15.0 release (to ensure that they worked flawlessly with the lastest Proxmox).
I hope that helps.
Pages
Add new comment