Instalando o docker host no Windows Server

Já tínhamos divulgado no lançamento da versão 1.6 que o cliente Docker já estava disponível para instalação no Windows, agora vamos demonstrar que é possível instalar o docker host no Windows Server 16 TP3.

O ambiente ainda está em beta, tanto o Windows Server 16 TP3, quanto a compatibilidade do Docker para Windows. A função push por exemplo ainda não está habilitada.

Mesmo sendo beta, acho que vale a pena testar pra ao menos entender como funciona.

Caso você use GNU/Linux e não queira instalar o Windows no seu disco rígido, você pode usar o virtualbox pra isso, mas não se esqueça de instalar a versão mais nova dele. Eu precisei instalar o VirtualBox da Sun na versão 5.0.2.

Primeiro baixe o CD do Windows Server 16 TP3.

Depois crie uma nova máquina virtual do tipo “Windows” e versão “Other Windows 64-bit”

Monte a ISO que acabou de baixar e inicie a instalação.

Quando solicitar qual o tipo de instalação, instale a que não requer experiência de usuário.

A instalação será bem rápida. (Por mais incrível que pareça). Ele solicitará a mudança de senha, para alternar entre campos de senha use “tab” e não “enter”.

Quando lhe for concedido acesso ao console digite:

powershell

Depois digite:

wget -uri http://aka.ms/setupcontainers -OutFile C:\ContainerSetup.ps1

Após baixar o script, digite o comando abaixo para instalar o docker:

C:\.\ContainerSetup.ps1

Ele reiniciará sua máquina virtual e demorará um pouco nessa tela (Caso sua internet seja tão lenta quanto a minha):

Essa é a tela que demonstra que o Docker foi instalado com sucesso:

Obs: Caso apresente um erro de “timeout” tente o comando novamente Isso aconteceu comigo e logo em seguida funcionou tranquilamente. Apenas demorou um pouco

Para iniciar uma máquina é muito simples

docker.exe run -it windowsservercore cmd.exe

Infelizmente ainda não é possível executar containers do GNU/Linux no Docker Host Windows, nem vice-versa, porem é possível usar os comandos docker e Dockerfile da mesma forma, apenas usando os as chamadas de comandos “RUN” equivalentes com cada sistema operacional.

O Docker funciona no Windows de forma semelhante ao GNU/Linux, ou seja, a promessa é que ele execute os containers de forma isolada também.

Divirta-se!

Fonte:

http://www.virtualclouds.info/?p=3393

https://blog.docker.com/2015/08/tp-docker-engine-windows-server-2016/

Como adicionar virtualhost aos logs do Varnish

Há algum tempo atrás escrevi um post mostrando como configurar o Varnish para escrever logs num formato modificado do Combined Log Format do Apache, esta modificação foi feita para adicionar o virtualhost %v no início de cada registro do log e na sintaxe do Apache se parece com o seguinte:

LogFormat "%v %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined

Isto foi feito com o varnishncsa-vhost, um script que faz o Varnish armazenar logs seguindo o formato acima, este script deveria estar obsoleto já que versões recentes do Varnish suportam customizar o formato dos logs através da opção -F, mas um problema no pacote Debian impede de fazer isto do “jeito certo”™.

Este problema foi citado em Workaround for broken varnishncsa logging due to shell mishandling of spaces in LOG_FORMAT variables e algumas soluções foram sugeridas, mas todas elas tem um “ar” de armengue. O problema já foi relatado no Debian em #657449 varnishncsa: please add a config option to allow a custom logging format (patch) mas ainda não foi solucionado.

Porque estou contando esse “blá blá blá”?

Recentemente precisei alterar o formato dos logs do Varnish em um servidor de produção e acabei utilizando o varnishncsa-vhost novamente e ele funcionou muito bem, isto me salvou dos sedutores “armengues que quebram na próxima atualização”.

Então se isto for útil para você de alguma forma utilize o repositório abaixo, eu subi uma nova versão do pacote Debian do varnishncsa-vhost lá:

deb http://debian.joenio.me unstable/

c3video for debconf #4

This is a follow-up to my previous post related the DebConf videoteam using a new software stack for the next conferences: http://acaia.ca/~tiago/posts/c3video-for-dc-take-3/.

As mentioned before, C3TT provides a set of scripts which will work in background for most reviewing and video processing tasks. The first will just check if the talk is done and mark the related ticket as recorded.

The second script, B-mount4cut, does a nice job by mounting a custom fuse filesystem providing the following files (more detailed explanation here:

uncut.dv: full original dv file used as input file for the final trimming.

project.kdenlive: Kdenlive project file for the operator. Once it's saved with the trim marks, fuse-vdv will do a parse on it and use the marks for cutting.

cut.dv: contains only the frames between the trim marks extracted from project.kdenlive.

cut-complete.dv: contains the frames between the trim marks extracted from project.kdenlive, plus a prepended intro and an appended video. Paths for these files should be previously set in the web interface as properties Processing.Path.Outro and Processing.Path.Intros. The outro file can be, for instance, an appended video file with a common thanks for sponsors. The intro files is usually an individual frame for each talk, being a colorful presentation poster. We can also set the intro duration in the Processing.Duration.Intro property.

cut.wav: demuxed audio from cut.dv

Note: in fact, fuse-vdv provides virtual video files as a concatenation of original input files, so avoiding copying large and redundant data. Ideally, these fuse mountpoints will be shared over the network for operators via glusterFS, but I'll skip that for now.

After adding the trimming marks and saving the project using Kdenlive, the operator should go to the web interface and mark the ticket as cut:

Mark ticket as cut

Note: I've been able to do the marks in Kdenlive using double-click in the video, then editing the crop start/end options. The buttons "[" and "]" didn't work in my Kdenlive version for some unknown reason.

In the current DebConf video environment I had to make a link builder for translating the path/file names to the C3TT format. So, for the Amsterdam/2015-08-13/09:57:02.dv we should have a amsterdam-2015.08.13-09_57_02.dv symlink.

From now the system will delivery the next tasks to C-cut-postprocessor script. This script will just check the marks from the Kdenlive project file and do the cutting job. So far it has worked perfectly here for the first video sessions in DebCamp, with zero hack in the original code, wow!

Next post will be about the encoding script, named D-encoding.

c3video for debconf #2

This is a follow-up to my previous post related the DebConf videoteam using a new software stack for the next conferences: http://acaia.ca/~tiago/posts/c3video-for-dc-take-1/.

Installing C3TT scripts

There's a video (in German) which gives an idea about how the C3TT works: https://www.youtube.com/watch?v=K-KHbAcTo9I

It basically gives the volunteers a web interface to cut and review the recordings, wich communicates with a set of scripts running in background which will automate some tasks.

"Installing" the set of scripts is just a matter of placing them in a common directory and installing some Perl dependencies, mostly which are already packaged for Debian.

First check it out from the svn repository (fun fact: the web interface is coded in php in a git repository, the scripts are mostly written in perl with a little of bash, in a subversion repository. Both the conference and media system is are in ruby :)

$ svn co https://subversion.fem.tu-ilmenau.de/repository/cccongress
$ mkdir /opt/crs; mv cccongress/trunk/tools /opt/crs/

A few libraries required:

$ apt-get install libboolean-perl libmath-round-perl libdatetime-perl libwww-curl-perl libconfig-inifiles-perl libxml-simple-perl
$ perl -MCPAN -e 'install XML::RPC::Fast'

In the web tracker create a project, go to all projects => workers and create a worker (I'll try to explain it later). Go edit the worker and we'll see the token and secret that should be used in the scripts to talk to the interface.

cd  /opt/crs/tools/tracker3.0

Create a file tracker-profile.sh with the follow lines (using our correct values):

export CRS_TRACKER=http://localhost/rpc
export CRS_TOKEN=2q24M7LW4Rk31YNW4tWKv8koNvyM3V4s
export CRS_SECRET=5j8SyCS35W2SBk2XIM4IWeDUqF9agG1x

We also need to build and install the fuse-vdv package from trunk/tools (if working with dv files, otherwise fuse-ts package).

Next step is run the scripts. Fortunatelly a nice UI has been done using screen with multiple tabs, which can be alternated using a <Ctrl+a> <number> combination.

cd  /opt/crs/tools/tracker3.0 && /start-screenrc-dv.sh

We'll get the following:

Screen tabs from C3TT

In a next post I'll try to explain a bit of how the web system work together with the scripts and how to do a basic setup for a real conference. I hope to get there soon!

Elixir in Debian, MiniDebconf at FISL, and Debian CI updates

In June I started keeping track of my Debian activities, and this is my July update.

Elixir in Debian

Elixir is a functional language built on top of the Erlang virtual machine. If features imutable data structures, interesting concurrency primitives, and everything else that Erlang does, but with a syntax inspired by Ruby what makes it much more aproachable in my opinion.

Those interested in Elixir for Debian are encouraged to hang around in #debian-elixir on the OFTC IRC servers. There are still a lot of things to figure out, for example how packaging Elixir libraries and applications is going to work.

MiniDebconf at FISL, and beyond

I helped organize a MiniDebconf at this year’s FISL, in Porto Alegre on the 10th of July. The whole program was targetted at getting more people to participate in Debian, so there were talks about translation, packaging, and a few other more specific topics.

I myself gave two talks: one about Debian basics, “What is Debian, and how it works”, and second one on “packaging the free software web”, which I will also give at Debconf15 later this month.

The recordings are available (all talks in Portuguese) at the Debian video archive thanks to Holger Levsen.

We are also organizing a new MiniDebconf in October as part of the Latinoware schedule.

Ruby

We are in the middle of a transition to switch to Ruby 2.2 as default in Debian unstable, and we are almost there. The Ruby transition is now on hold while GCC 5 one is going on, but will be picked up as soon as were are done with GCC 5.

ruby-defaults has been uploaded to experimental for those that want to try having Ruby 2.2 as default before that change hits unstable. I myself have been using Ruby 2.2 as default for several weeks without any problem so far, including using vagrant on a daily basis and doing all my development on sid with it.

I started taking notes about Ruby interpreter transitions work to make sure that knowledge is registered.

I have uploaded minor security updates of both ruby2.1 and ruby2.2 to unstable. They both reached testing earlier today.

I have also fixed another bug in redmine, which I hope to get into stable as well as soon as possible.

gem2deb has seen several improvements through versions 0.19, 0.20, 0.20.1 and 0.20.2.

I have updated a few packages:

• ruby-rubymail
• ruby-ferret
• ruby-omniauth
• ruby-hashie
• ruby-rack-accept
• chef-zero
• nailgun-agent
• ruby-serialport
• ruby-gnome2
• ruby-mysql2
• ruby-dataobjects-postgres
• ruby-standalone
• thin
• ruby-stringex
• ruby-i18n

Two NEW packages, ruby-rack-contrib and ruby-grape-logging ,were ACCEPTED into the Debian archive. Kudos to the ftp-master team who are doing an awesome job reviewing new packages really fast.

Debian Continuous Integration

This month I have made good progress with the changes needed to make debci work as a distributed system with one master/scheduler node and as many worker nodes (running tests) as possible.

While doing my tests, I have submitted a patch to lxc and updated autodep8 in unstable. At some point I plan to upload both autodep8 and autopkgtest to jessie-backports.

Sponsoring

I have sponsored a few packages:

• ruby-rack-mount, ruby-grape-entity, and ruby-grape for Hleb Valoshka.
• redir and tmate twice for Lucas Kanashiro.
• lxc to wheezy-backports for Christian Seiler.