(Migrated) Installers roadmap - SuSE, Vagrant, GitHub, Docker and Windows

(This message has been automatically imported from the retired mailing list)

Hello,

please find the current state of installers and the roadmap below.

What we have right now:

  • Packages/repository for Ubuntu 12.04
  • Packages/repository for Debian 7
  • Packages/repository for RHEL/CentOS 6

What is the course of action, roughly in that order:

  • Packages for Ubuntu 14.04 [1]
  • Vagrantfile for OS X and other systems [1]
  • Packages/repository for SuSE SLES 11
  • More automated build scripts for packages [2]
  • Repository for GH master
  • Dockerfile
  • Windows installer

Items marked [1] are pretty much done (thanks again to everyone who
helped out in preparing them!) - I’ll be working on it in upcoming days.

Two colleagues of mine will be working on the rest of the tasks.

Item marked [2] means scripts to build packages for all systems in one
command, basically I envision something akin to …

$ ./build-zato.sh support/1.1 1.1 4

… and that will start a process to compile and package everything
needed for Ubuntu, Debian, RHEL and SuSE, for each architecture.

GH master repository will certainly come in handy because a lot has been
added since the 1.1 release so in addition to the stable one, there will
also be a development repo at https://zato.io

Dockerfile - not sure about that one. At the very least this should
install Zato binaries under some Ubuntu LTS. However we probably should
also make it a bit smarter and have it configure Postgres, Redis and
start a quickstart cluster as well.

Windows installer - this will be split into two sub-releases.

First one will download and install VirtualBox, Vagrant, putty and
install a quickstart inside. This will let Windows users quickly get
started with Zato.

Another sub-release of the installer will prepare a set of mapped
directories between (say) C:\Documents and Settings\user\zato\env and
/vagrant/env so that Windows users will be able to save their work in
their C:\ drive which will be translated to a directory inside the VM
and Zato will pick the changes up.

In other words, it will be possible to develop on Windows without
porting Zato to Windows - this is year 2014, we have so many great
virtualization technologies at our disposal so we definitely should make
use of them.

I expect for everything to be ready within 3 months, and certainly
before the next major Zato release.