TurnKey 12.1 64-bit maintenance release built with new tkldev build appliance

Once that sunk in I think Alon and I both felt we needed to work on fixing that before daring to metaphorically "show our faces".

Happily, tkldev will very soon be out, and not long after so should TurnKey 13. I think after that most of the shame will go away. I might even get back to sharing random thoughts and discoveries on the TurnKey Blog. It's been pitifully inactive of late.

tkldev won't be everything we envision in a community build infrastructure, but it will be a very important step forward. Further down the road, I'd like to create a cloud service that automatically builds and distributes community appliances. OTOH, I also have a few other important projects on my plate so when that will happen is anyone's guess.

If I could just figure out how to get fork() working in real life...

I'm with Adrian. Looking forward to tkldev.

As always...thanks to you (Liraz) and Alon for your hard work and dedication.

I know that you'll find you have a devout group of followers & supporters aching to become contributors as well. I'm certainly one of them.

Cheers boys.

Liraz! Nice to have news from you! It seems that you guys are in good path of modernizing the project and be more open, as we discussed a lot in the past. 

The upgraded upstream versions are very welcome, and 64bit support is excelent news. I really like the way the project is evolving (deprecating 32 bit appliances).

Of course I'm still waiting for a chance to get my hands on the new tkldev. I'll be watching this space as usual, willing to see the results of your work on this field. 

Cheers! 

I'll cast my vote for Turnkeylinux on SourceForge right now!

We're really hoping the new development infrastructure will encourage the community to forgive us for past mistakes that closed the project down and get some real collaboration going.

Having to maintain every bit of TurnKey ourselves has evolved into the archetypical Red Queen's race. With more development resources we could crank out releases more quickly, expand the library, and work on all the innovations we've been dreaming up but haven't had time to implement.

Heck, I might even have time to read my email and respond to community feedback within a more reasonable timeframe. Speaking of which, sorry for the late reply!

Nice work! I know that you guys have been slaving away on this release (and the infrastructure that built it) and I'm so happy to see the fruits of your labour! IMO this is a major milestone release (which I guess is a bit funny in that it's a point release) and obvioulsy there is still plenty of work to be done but it's a huge step forward...

I think releasing the build infrastructure as an appliance is a fantastic idea and also providing the source for each appliance via GitHub is brilliant! I am assumimng that with these in place, individuals could choose to build an 'official' TKL appliance themselves?

And whilst I know it has been a lot of work for you guys, it will change the way and the degree to which the community can engage with the project. Hopefully (eventually) you may even see your workload decrease (and/or give room for new innovations and ideas to be fulfilled). Using GitHub will allow bug fixes and tweaks to be provided by the community and merged as appropriate. Also customised and new appliances will be able to be added to the fold relatively easily (community developers can use GitHub to host there custom appliance code and TKL could fork it to bring it in as a new official appliance).

I have a ton of questions about TKLDev and the implications for TKLPatch (like will it be depreciated or is it part of TKLDev) but I think I should wait for the announcement before I start rattling through them as I'm sure you will answer many before I even ask them!

And the detailed comment (you linked to on the OVZ announcement).

I'll endevour to have a play over the weekend and give some feedback on how that goes (I run PVE 3.0 at home and as you know use OVZ lots).

Thanks for the initial feedback guys!

Just a quick note for those using the OpenVZ builds in Proxmox VE, the TurnKey channel has been updated for 12.1, so you'll be able to take advantage of inline downloading and deployment. Regarding the initialization fence and iptables, please see my comment.

IIRC if you use a Linux desktop it's really easy... I'm pretty sure that you can just dd the ISO to the USB (you'll need to ensure that the USB is bootable first...). The instructions for PVE (which I have successfully used to create an install USB of PVE; PVE is also based on Debian) should work: http://pve.proxmox.com/wiki/Install_from_USB_Stick

If you are using Windows then another option that should work is: http://www.pendrivelinux.com/yumi-multiboot-usb-creator/

Seeing as it's a old PC though, are you sure that it will support booting from the USB you're using? Even if it technically does support booting from USB I have found some older motherboards can be a bit finiky on whether a USB will work or not... Some seem to only work with 4GB or smaller USBs and even then I have found that some brand USBs will work while others refuse to...

Although having said that, in my experience if you manage to get as far as the bootloader then that probably isn't the problem...

A plan isn't required for HubDNS, but your Hub account does need an Amazon account with Route53 enabled to manage custom domains (as always).

Hello

That all sounds good... but one query: I use the 'HubDNS' which integrates with Amazon's Route 53 service, which seems to require a 'pay per use' (previously 'hobby') plan.  But I have no need to run EC2 instances as I host a server on my own hardware.  

Does the new 'pay per use' plan pricing, with the new $10/month charge, have to apply in that situation?  I have no need for EC2 instances etc., so it seems a bit much if so, as it would mean you would have to pay $10/month just to access the dynamic DNS / HubDNS service.  If the $10/month plan is the only option for enabling HubDNS, do you have any other recommendations for achieving a dynamic DNS solution?

Many thanks.

I was under the impression the only Linux AMIs that are not eligable for the Free Tier are licenced ones (like SUSE Enterprise Linux and Red Hat Enterprise Linux)... But perhaps that has changed. I found it difficult to confirm or deny this on the Amazon site. Some of my reading suggests that I am right, but it doesn't explicitly say and looking at the listing (that has the stars) it seems that there are only a few that are explicitly supported...

Are you using a micro instance? If so then it's probably worth contacting the TKL devs direct - best way IMO is via the Hub 'feedback' (blue button on left hand side whan logged in).

Good Job....

Just like the others, I can't wait to get involved in the new TKLDev environment.

I will start this weekend in taking one of the OpenVZ builds and see how easy it is to use this for LXC or what is needed to convert them.

 Thanks for the hard work.

Hans

So you will have OOTB 32 bit support (with security updates) until at least 12 months after Debian 8/Jessie is released (which should be a year or 2 away at least).

As Alon mentioned building 32 bit in 64 bit environment is possible so even beyond that hopefully TKLDev will be able to build 32 bit appliances...

I'm not sure which type of image you're looking for, but the 32 bit iso is found at http://sourceforge.net/projects/turnkeylinux/files/iso/turnkey-postgresq...

If you can find the link to the 64 bit image, then edit the link and replace 'amd64' with 'i386'.  It works for iso images and I'm guessing it would work for other types as well.

I have 3 older HP Servers that will do 64 Bit bare metal, but only host 32 Bit Virtual Machines.  They will get upgraded, but only eventually.

It is critical, for me anyway, to have 32 Bit Builds available that can be  upgraded to 64 Bit when the pieces are in place.  Running into this just now with the PostgreSQL server  (at least I can't find the 32 bit images)

I've got some perfectly good hosts that I'd like to keep using a few more years, but they're not 64-bit capable.  I'd rather not get locked into either upgrade hardware or live with 12.0.

Yep, the architecture of the host needs to match ISO you are patching. This holds true for TKLPatch as well as the soon-to-be-released TKLDev.

It is technically possible to support patching/building 32bit on 64bit with some hacks, but not the other way around IIRC.

As for TKLPatch, it will continue to be maintained as it's useful for patching ISO's. But, for developing and building appliances, TKLDev will be the tool you'll want to use.

I would expect that the architechture of your build environment would have to match the ISO.

Although I'm not sure about the upcoming TKLDev...

My first test of TKLPatch with a 12.1 iso failed 🙂

root@tklpatch ~/patches# tklpatch iso/turnkey-core-12.1-squeeze-amd64.iso example
# extracting root filesystem and isolinux from ISO
Parallel unsquashfs: Using 2 processors
24885 inodes (25366 blocks) to write

[===========================================================\] 25366/25366 100%
created 23257 files
created 2794 directories
created 1069 symlinks
created 38 devices
created 1 fifos
TKLPATCH_ISOLABEL: example
# applying patch example
# executing config script example/conf/pre-debs
chroot: failed to run command `dpkg-divert': Exec format error

This is probably because I'm running TKLPatch on a 12.0 core, i.e. 32 bit virtual host.  Guess I'll need to create a 64 bit host for testing.

And I believe that it is not being depreciated, but will live alongside TKLDev as an alternative pathway to develop appliances...

environment.  One capability I hope is present is the ablity to create combo appliances.  I have an application that needs both the Drupal7 plus OpenLDAP for a directory application.  Client can't afford multiple hosted servers, so both must be combined into a single appliance.  I hope the new build process will allow us to build these combo appliances.

My next question (probably a dumb one) is, will TKLpatch work with the 12.1 iso's, or do we need to wait for more info on setting up the new development platform?

Just wanna say that after finaly getting my hands on it as well as "my grips".., 64bit TurnKey is da bomb! TurnKey's new "build system in a box" certainly made my life a lot easier. Many many thanks for the very hard dev-work! I'm pretty surprices as well at the combo appliances creation ability. Will have to spend some more time on it. Thanks again, Joann.

If you post in the support forum with a clear indication of what you are trying to do, what isn't working, etc. then perhaps someone can help!?

Having said that, perhaps the 'getting started with TurnKey' tutorial might be of some use?

If using ProcessMaker is your issue, then perhaps check out what resources they have on their website, like the tutorials or their wiki.