Monitoring Docker converted Russ Mckendrick download
Monitoring Docker converted Russ Mckendrick download
download
https://ebookgate.com/product/monitoring-docker-converted-russ-
mckendrick/
https://ebookgate.com/product/learning-docker-pethry-raj/
ebookgate.com
https://ebookgate.com/product/contract-law-11th-edition-ewan-
mckendrick/
ebookgate.com
https://ebookgate.com/product/mastering-docker-1st-edition-scott-
gallagher/
ebookgate.com
https://ebookgate.com/product/the-docker-book-18-09-2-b71a7e7-edition-
james-turnbull/
ebookgate.com
Learning Docker 2nd Revised Edition Jeeva S. Chelladhurai
https://ebookgate.com/product/learning-docker-2nd-revised-edition-
jeeva-s-chelladhurai/
ebookgate.com
https://ebookgate.com/product/contract-law-text-cases-and-
materials-5th-edition-ewan-mckendrick/
ebookgate.com
https://ebookgate.com/product/elementary-korean-workbook-converted-
epub-1st-edition-insun-lee/
ebookgate.com
https://ebookgate.com/product/the-image-processing-handbook-seventh-
edition-russ/
ebookgate.com
https://ebookgate.com/product/nessus-network-auditing-2nd-edition-
russ-rogers/
ebookgate.com
Monitoring Docker
Table of Contents
Monitoring Docker
Credits
About the Author
About the Reviewer
www.PacktPub.com
Support files, eBooks, discount offers, and more
Why subscribe?
Free access for Packt account holders
Preface
What this book covers
What you need for this book
Who this book is for
Conventions
Reader feedback
Customer support
Downloading the example code
Downloading the color images of this book
Errata
Piracy
Questions
1. Introduction to Docker Monitoring
Pets, Cattle, Chickens, and Snowflakes
Pets
Cattle
Chickens
Snowflakes
So what does this all mean?
Docker
Launching a local environment
Cloning the environment
Running a virtual server
Halting the virtual server
Summary
2. Using the Built-in Tools
Docker stats
Running Docker stats
What just happened?
What about processes?
Docker top
Docker exec
Summary
3. Advanced Container Resource Analysis
What is cAdvisor?
Running cAdvisor using a container
Compiling cAdvisor from source
Collecting metrics
The Web interface
Overview
Processes
CPU
Memory
Network
Filesystem
Viewing container stats
Subcontainers
Driver status
Images
This is all great, what’s the catch?
Prometheus
Launching Prometheus
Querying Prometheus
Dashboard
The next steps
Alternatives?
Summary
4. A Traditional Approach to Monitoring Containers
Zabbix
Installing Zabbix
Using containers
Using vagrant
Preparing our host machine
The Zabbix web interface
Docker metrics
Create custom graphs
Compare containers to your host machine
Triggers
Summary
5. Querying with Sysdig
What is Sysdig?
Installing Sysdig
Using Sysdig
The basics
Capturing data
Containers
Further reading
Using Csysdig
Summary
6. Exploring Third Party Options
A word about externally hosted services
Deploying Docker in the cloud
Why use a SaaS service?
Sysdig Cloud
Installing the agent
Exploring your containers
Summary and further reading
Datadog
Installing the agent
Exploring the web interface
Summary and further reading
New Relic
Installing the agent
Exploring the web interface
Summary and further reading
Summary
7. Collecting Application Logs from within the Container
Viewing container logs
ELK Stack
Starting the stack
Logspout
Reviewing the logs
What about production?
Looking at third party options
Summary
8. What Are the Next Steps?
Some scenarios
Pets, Cattle, Chickens, and Snowflakes
Pets
Cattle
Chickens
Snowflakes
Scenario one
Scenario two
Scenario three
A little more about alerting
Chickens
Cattle and Pets
Sending alerts
Keeping up
Summary
Index
Monitoring Docker
Monitoring Docker
Copyright © 2015 Packt Publishing
All rights reserved. No part of this book may be reproduced, stored in a retrieval system,
or transmitted in any form or by any means, without the prior written permission of the
publisher, except in the case of brief quotations embedded in critical articles or reviews.
Every effort has been made in the preparation of this book to ensure the accuracy of the
information presented. However, the information contained in this book is sold without
warranty, either express or implied. Neither the author, nor Packt Publishing, and its
dealers and distributors will be held liable for any damages caused or alleged to be caused
directly or indirectly by this book.
Packt Publishing has endeavored to provide trademark information about all of the
companies and products mentioned in this book by the appropriate use of capitals.
However, Packt Publishing cannot guarantee the accuracy of this information.
First published: December 2015
Production reference: 1041215
Published by Packt Publishing Ltd.
Livery Place
35 Livery Street
Birmingham B3 2PB, UK.
ISBN 978-1-78588-275-3
www.packtpub.com
Credits
Author
Russ McKendrick
Reviewer
Marcelo Correia Pinheiro
Commissioning Editor
Veena Pagare
Acquisition Editor
Rahul Nair
Content Development Editor
Anish Sukumaran
Technical Editor
Saurabh Malhotra
Copy Editor
Trishya Hajare
Project Coordinator
Izzat Contractor
Proofreader
Safis Editing
Indexers
Mariammal Chettiyar
Priya Sane
Production Coordinator
Shantanu N. Zagade
Cover Work
Shantanu N. Zagade
About the Author
Russ McKendrick is an experienced solutions architect who has been working in IT and
IT-related industries for the better part of 23 years. During his career, he has had varied
responsibilities in a number of industries, ranging from looking after entire IT
infrastructures to providing first line, second line, and senior support in client facing, and
internal teams for corporate organizations.
He works almost exclusively with Linux, using open source systems and tools on various
platforms ranging from dedicated hardware and virtual machines to public clouds.
About the Reviewer
Marcelo Correia Pinheiro is a Brazilian software engineer from Porto Alegre. He started
to work as a web designer and programmer in 2000 with ASP and PHP, naturally getting
in touch with the Microsoft .NET framework and Java running respective databases of
choice for web applications. Since 2003, he has used Linux and UNIX-related operational
systems, from Slackware to Gobo Linux, Archlinux, CentOS, Debian, and today OSX,
having some contact with BSD distributions too. He has lost some nights compiling and
applying patches to the Linux kernel to make its desktop work. Since the beginning, he
has been acting as a problem solver, no matter what the programming language, database,
or platform is—open source enthusiast.
After a few years, he decided to live in São Paulo to work with newer technologies such as
NoSQL, cloud computing, and Ruby, where he started to conduct tech talks with this
language in Locaweb. He created some tools to standardize development using tools such
as vagrant and Ruby gems—some of these in their GitHub—in Locaweb to ensure fast
application packaging and reduced deployment rollbacks. In 2013, he changed his career
to be a full-stack developer following the DevOps movement. Since 2012, he has
attended, as a speaker, some of the biggest software conferences in Brazil—RS on Rails,
QConSP, The Developer’s Conference, and RubyConf Brazil—talking not only about
Ruby, but also about some of the well-known DevOps tools such as Terraform, Packer,
Ansible, and Docker. Today, he works as a DevOps consultant in their company.
In his free time, he loves playing the guitar, having some fun with cats, traveling, and
drinking beer. He can be found on his blog (http://salizzar.net), Twitter
(https://twitter.com/salizzar), GitHub (https://github.com/salizzar) and Linkedin
(https://www.linkedin.com/in/salizzar).
He has worked as a reviewer for Vagrant Virtual Development Environment Cookbook, a
Packt Publishing book with useful recipes using vagrant with configuration management
tools such as Puppet, Chef, Ansible, and SaltStack.
I want to thank all my friends, who believed in my potential since the beginning and who
still follow me despite the distance. I would also like to thank my mentors, Gleicon
Moraes, Roberto Gaiser, and Rodrigo Campos, who gave me the incentive and tips to be a
better software engineer and person.
www.PacktPub.com
Support files, eBooks, discount offers, and
more
For support files and downloads related to your book, please visit www.PacktPub.com.
Did you know that Packt offers eBook versions of every book published, with PDF and
ePub files available? You can upgrade to the eBook version at www.PacktPub.com and as
a print book customer, you are entitled to a discount on the eBook copy. Get in touch with
us at <service@packtpub.com> for more details.
At www.PacktPub.com, you can also read a collection of free technical articles, sign up
for a range of free newsletters and receive exclusive discounts and offers on Packt books
and eBooks.
https://www2.packtpub.com/books/subscription/packtlib
Do you need instant solutions to your IT questions? PacktLib is Packt’s online digital
book library. Here, you can search, access, and read Packt’s entire library of books.
Why subscribe?
Fully searchable across every book published by Packt
Copy and paste, print, and bookmark content
On demand and accessible via a web browser
Free access for Packt account holders
If you have an account with Packt at www.PacktPub.com, you can use this to access
PacktLib today and view 9 entirely free books. Simply use your login credentials for
immediate access.
Preface
With the increase in the adoption of Docker containers, the need to monitor which
containers are running, what resources they are consuming, and how it affects the overall
performance of the system, has become a time-related need. Monitoring Docker will teach
you how monitoring containers and keeping a keen eye on the working of applications
help to improve the overall performance of the applications that run on Docker.
This book will cover monitoring containers using Docker’s native monitoring functions,
various plugins, and also third-party tools that help in monitoring. The book will first
cover how to obtain detailed stats for the active containers, resources consumed, and
container behavior. This book will also show the readers how to use these stats to improve
the overall performance of the system.
What this book covers
Chapter 1, Introduction to Docker Monitoring, discusses how different it is to monitor
containers compared to more traditional servers such as virtual machines, bare metal
machines, and cloud instances (Pets versus Cattle and Chickens versus Snowflakes). This
chapter also details the operating systems covered in the examples later in this book and
also gives a little information on how to get a local test environment up and running using
vagrant, so that installation instructions and practical examples can be easily followed.
Chapter 2, Using the Built-in Tools, helps you learn about the basic metrics you can get
out of the vanilla Docker installation and how you can use them. Also, we will understand
how to get real-time statistics on our running containers, how to use commands that are
familiar to us, and how to get information on the processes that are launched as part of
each container.
Chapter 3, Advanced Container Resource Analysis, introduces cAdvisor from Google,
which adds a lot more precision to the basic tools provided by Docker. You will also learn
how to install cAdvisor and start collecting metrics.
Chapter 4, A Traditional Approach to Monitoring Containers, looks at a traditional tool for
monitoring services. By the end of this chapter, you should know your way around Zabbix
and the various ways you can monitor your containers.
Chapter 5, Querying with Sysdig, describes Sysdig as “an open source, system-level
exploration tool to capture system state and activity from a running Linux instance, then
save, filter, and analyze it.” In this chapter, you will learn how to use Sysdig to both view
your containers’ performance metrics in real time and also record sessions to query later.
Chapter 6, Exploring Third Party Options, walks you through a few of the Software as a
Service (SaaS) options that are available, why you would use them, and how to install
their clients on the host server.
Chapter 7, Collecting Application Logs from within the Container, looks at how we can
get the content of the log files for the applications running within our containers to a
central location so that they are available even if you have to destroy and replace a
container.
Chapter 8, What Are the Next Steps?, looks at the next steps you can take in monitoring
your containers by talking about the benefits of adding alerting to your monitoring. Also,
we will cover some different scenarios and look at which type of monitoring is appropriate
for each of them.
What you need for this book
To ensure the experience is as consistent as possible, we will be installing vagrant and
VirtualBox to run the virtual machine that will act as a host to run our containers. Vagrant
is available for Linux, OS X, and Windows; for details on how to install this, see the
vagrant website at https://www.vagrantup.com/. The details of how to download and
install VirtualBox can be found at https://www.virtualbox.org/; again, VirtualBox can be
installed on Linux, OS X, and Windows.
Who this book is for
This book is for DevOps engineers and system administrators who want to manage
Docker containers, better manage these containers using expert techniques and methods,
and better maintain applications built on Docker.
Conventions
In this book, you will find a number of text styles that distinguish between different kinds
of information. Here are some examples of these styles and an explanation of their
meaning.
Code words in text, database table names, folder names, filenames, file extensions,
pathnames, dummy URLs, user input, and Twitter handles are shown as follows: “We can
include other contexts through the use of the include directive.”
A block of code is set as follows:
{
"fields": {
"@timestamp": [
1444567706641
]
},
"sort": [
1444567706641
]
}
When we wish to draw your attention to a particular part of a code block, the relevant
lines or items are set in bold:
{
"fields": {
"@timestamp": [
1444567706641
]
},
"sort": [
1444567706641
]
}
New terms and important words are shown in bold. Words that you see on the screen,
for example, in menus or dialog boxes, appear in the text like this: “Clicking the Next
button moves you to the next screen.”
Note
Warnings or important notes appear in a box like this.
Tip
Tips and tricks appear like this.
Reader feedback
Feedback from our readers is always welcome. Let us know what you think about this
book—what you liked or disliked. Reader feedback is important for us as it helps us
develop titles that you will really get the most out of.
To send us general feedback, simply e-mail <feedback@packtpub.com>, and mention the
book’s title in the subject of your message.
If there is a topic that you have expertise in and you are interested in either writing or
contributing to a book, see our author guide at www.packtpub.com/authors.
Customer support
Now that you are the proud owner of a Packt book, we have a number of things to help
you to get the most from your purchase.
Downloading the example code
You can download the example code files from your account at http://www.packtpub.com
for all the Packt Publishing books you have purchased. If you purchased this book
elsewhere, you can visit http://www.packtpub.com/support and register to have the files e-
mailed directly to you.
Downloading the color images of this book
We also provide you with a PDF file that has color images of the screenshots/diagrams
used in this book. The color images will help you better understand the changes in the
output. You can download this file from:
http://www.packtpub.com/sites/default/files/downloads/Monitoring_Docker_ColorImages.pdf
Errata
Although we have taken every care to ensure the accuracy of our content, mistakes do
happen. If you find a mistake in one of our books—maybe a mistake in the text or the
code—we would be grateful if you could report this to us. By doing so, you can save other
readers from frustration and help us improve subsequent versions of this book. If you find
any errata, please report them by visiting http://www.packtpub.com/submit-errata,
selecting your book, clicking on the Errata Submission Form link, and entering the
details of your errata. Once your errata are verified, your submission will be accepted and
the errata will be uploaded to our website or added to any list of existing errata under the
Errata section of that title.
To view the previously submitted errata, go to
https://www.packtpub.com/books/content/support and enter the name of the book in the
search field. The required information will appear under the Errata section.
Piracy
Piracy of copyrighted material on the Internet is an ongoing problem across all media. At
Packt, we take the protection of our copyright and licenses very seriously. If you come
across any illegal copies of our works in any form on the Internet, please provide us with
the location address or website name immediately so that we can pursue a remedy.
Please contact us at <copyright@packtpub.com> with a link to the suspected pirated
material.
We appreciate your help in protecting our authors and our ability to bring you valuable
content.
Questions
If you have a problem with any aspect of this book, you can contact us at
<questions@packtpub.com>, and we will do our best to address the problem.
Chapter 1. Introduction to Docker
Monitoring
Docker has been a recent but very important addition to a SysAdmins toolbox.
Docker describes itself as an open platform for building, shipping, and running distributed
applications. This means that developers can bundle their code and pass it to their
operations team. From here, they can deploy safe in the knowledge that it will be done so
in a way that introduces consistency with the environment in which the code is running.
When this process is followed, it should make the age-old developers versus operations
argument of “it worked on my local development server”—a thing of the past. Since
before its “production ready” 1.0 release back in June 2014, there had been over 10,000
Dockerized applications available. By the end of 2014, that number had risen to over
71,000. You can see how Docker grew in 2014 by looking at the infographic that was
published by Docker in early 2015, which can be found at
https://blog.docker.com/2015/01/docker-project-2014-a-whirlwind-year-in-review/.
While the debate is still raging about how production ready the technology is, Docker has
gained an impressive list of technology partners, including RedHat, Canonical, HP, and
even Microsoft.
Companies such as Google, Spotify, Soundcloud, and CenturyLink, have all open sourced
tools that support Docker in some way, shape, or form and there has also been numerous
independent developers who have released apps that provide additional functionality to the
core Docker product set. Also, all the companies have sprung up around the Docker
ecosystem.
This book assumes that you have had some level of experience building, running, and
managing Docker containers, and that you would now like to start to metrics from your
running applications to further tune them, or that you would like to know when a problem
occurs with a container so that you can debug any ongoing issues.
If you have never used Docker before, you may want to try one of the excellent books that
serve and introduce you to all the things that Docker provides, books such as Learning
Docker, Packt Publishing, or Docker’s own introduction to containers, which can be
found at their documentation pages, as follows:
Learning Docker: https://www.packtpub.com/virtualization-and-cloud/learning-
docker
Official Docker docs: https://docs.docker.com/
Now, we have a brought ourselves up to speed with what Docker is; the rest of this chapter
will cover the following topics:
How different is it to monitor containers versus more traditional servers such as
virtual machines, bare metal machine, and cloud instances (Pets, Cattle, Chickens,
and Snowflakes).
What are the minimum versions of Docker you should be running?
How to follow instructions on bringing up an environment locally using Vagrant in
order to follow the practical exercises in this book
Pets, Cattle, Chickens, and Snowflakes
Before we start discussing the various ways in which you can monitor your containers, we
should get an understanding of what a SysAdmins world looks like these days and also
where containers fit into it.
A typical SysAdmin will probably be looking after an estate of servers that are hosted in
either an on-site or third-party data center, some may even manage instances hosted in a
public cloud such as Amazon Web Services or Microsoft Azure, and some SysAdmins
may juggle all their server estates across multiple hosting environments.
Each of these different environments has its own way of doing things, as well as
performing best practices. Back in February 2012, Randy Bias gave a talk at Cloudscaling
that discussed architectures for open and scalable clouds. Towards the end of the slide
deck, Randy introduced the concept of Pets versus Cattle (which he attributes to Bill
Baker, who was then an engineer at Microsoft).
You can view the original slide deck at http://www.slideshare.net/randybias/architectures-
for-open-and-scalable-clouds.
Pets versus Cattle is now widely accepted as a good analogy to describe modern hosting
practices.
Other documents randomly have
different content
Nacha creyó que su amistad con mademoisselle, después de lo
ocurrido, sería más íntima que nunca. Una semana después,
mademoisselle le pidió el pago del mes que le debía.
—Oh, señorita Nashá, no es por nada, usted sabe, pero las cosas
andan mal. Los pensionistas... algunos... no pagan puntualmente.
—Yo le pido que espere un poquito, mademoisselle. Un mes no es
nada para usted. Mire que estoy muy pobre. He vendido las
pobrecitas alhajas que tenía. Buscaré un empleo, trabajaré... Pero
no me apremie. Sí, sea buena, por favor...
Y le tomó una mano, cosa que mademoisselle solía antes hacer con
ella, y que había hecho sin fin de veces aquel domingo cuando
rogaba a su pupila para que no revelase a nadie el tremendo secreto
que le sorprendiera. Mademoiselle retiró la mano con alguna
sequedad y se levantó.
—No, no puedo esperar, señorita. Mañana me trae su pensión. No le
cuesta nada ganarla. Usted tiene amigos muy... benévolos, que se la
darán gustosamente. ¡Oh, gustosamente! C'est ça.
Nacha enrojeció de vergüenza y de ira y contestó:
—Está bien. Mañana tendrá el importe de mi pensión.
Toda la noche la pasó Nacha llorando.
Una de las cosas que más le preocuparon fué la conducta de
mademoisselle para con ella. La creyó una persona excelente,
buena, cariñosa; y ahora veía que se había equivocado. La creyó
una alma pura, sin defectos, y había sorprendido un secreto que
estaba lejos de certificar su pureza. Pero si no era pura, ¿por qué
afectaba serlo? Nacha se desesperaba. Había creído conocer la
pureza de cerca, había imaginado que era cosa factible y bella la
virtud, y ahora sabía lo que eran la pureza y la virtud.
—Porque mademoisselle—pensaba—, no sólo se dice pura sino que
los demás también lo creen. Sí, lo creen, y la prueba es que tiene
sacerdotes amigos que vienen a visitarla. Si no fuese tenida por
santa, esos sacerdotes no vendrían, no serían sus amigos...
Entonces, quiere decir que la virtud consiste en ocultar las cosas...
Sí, así debe de ser. Y ahora me acuerdo de muchos señores
considerados como personas respetabilísimas, que, en las casas de
citas, me proponían... Claro, así es. La virtud no existe. Los
virtuosos, los honestos, los puros son los que se ocultan, "los que se
cuidan", como suele decirse.
Pero Nacha no lloraba por esto, aunque había tenido una inmensa
desilusión. Lloraba porque sus esfuerzos por ser honrada, como ella
decía, eran inútiles. Al día siguiente volvería a ser lo que fué. Y todo
por culpa de mademoisselle, que, pura y de tan santos principios, la
arrojaba en el mal tranquilamente y como pago de su discreción. Ya
no dudaba de que el destino era cruel con ella, de que se había
empeñado en que fuese una perdida. Y bueno: lo sería, ya que no
había otro modo de vivir, ya que todos se lo ordenaban.
Al día siguiente, a las tres de la tarde, se vistió con su mejor vestido
y—cosa que desde un mes y medio atrás no hacía—, se puso en la
cara crema Simón y en los labios un poco de rojo. Elegante,
voluptuosa, tentadora, salió a la calle y se dirigió en un coche al
escritorio de un abogado amigo, de aquél íntimo de Torres que
durante varios meses la protegiera.
—Cien pesos, nada menos—decía el abogado, moviendo la cabeza
de arriba a abajo, con los labios apretados y el inferior alargado en
una mueca de asombro.
—Para usted no es nada—argüía Nacha, intimidada por la frialdad
del recibimiento.
—Es mucho m'hijita. ¡Cien patacones en estos tiempos! Te daré
cincuenta... Es todo lo que puedo. ¡Tantos gastos! Mi mujer es muy
gastadora, y después las niñeras, las amas, qué sé yo. ¡Un titeo! En
fin, yo creo que con cincuenta del páis se pueden hacer muchas
cosas...
Nacha tomó los cincuenta pesos desilusionada, y dijo que se los
devolvería. El abogado hizo un vasto gesto redondo sobre su cabeza,
como diciendo que no pensara en ello y se ocupó en mirar a su
visitante. Debió gustarle, porque se puso un poco nervioso. La
miraba con los ojos brillantes, cuando ella se levantó para irse.
—¿Ya? Pero no nos podemos despedir así. Eso no, m'hijita. ¿Nunca
te acordaste de mí, de aquellos tiempos?...
Nacha había ido a pedir dinero a este hombre porque lo creía el más
desinteresado de sus amigos y tenía la esperanza de que por simple
simpatía y amistad le prestase o le diese la suma que necesitaba. Y
así cuando el abogado se le acercó, la abrazó y fué a cerrar la puerta
con llave, ella tuvo un gran disgusto. Intentó defenderse, pedirle que
la dejara, decirle que ahora quería ser honrada; pero pensó que no
tenía derecho a nada de eso. ¿Qué era ella, sino una...? Además,
¿no le había dado dinero él? Entonces podía hacer lo que quisiera.
Eso era lo lógico y lo humano.
Una hora después, medio llorosa y muy triste, entregó a
mademoisselle los cincuenta pesos correspondientes a la primera
quincena.
—Oh, pero aquí falta, señorita. ¿Y la otra quincena? Pardon, yo no
puedo, absolutamente no puedo esperar.
—Unos días, dos o tres, nada más—dijo Nacha, con rabia, mirando
agresivamente a mademoisselle.
—No, pas possible. Hoy estamos a catorce de octubre. Tiene su
pensión pagada hasta mañana. Esperaré sólo hasta mañana.
Había pensado Nacha en recurrir a Torres, cuando al día siguiente,
muy temprano, la sirvienta le dijo que uno de los Padres deseaba
hablarla. Nacha fué a la salita. Allí el Padre la esperaba. Era un
hombre redondo. Redonda la figura, la cabeza, la cara. Redondos los
gestos, los gruesos y cortos dedos. Hablaba redondeando la
pequeña boca. Nacha no salía de su asombro por aquella visita
inimaginada.
—Sí, pues... es el caso... que... mademoisselle...
El Padre, de pie, parecía meditar en el modo de salir del paso.
Miraba al suelo y tenía una mano derecha sobre la boca, retirándola
sólo para hacer un molinete en el aire con los dedos o una ligera
castañuela.
—Usted sabe bien lo que es mademoisselle. ¡Una señorita tan
austera, tan perfecta! Sus padres, desgraciadamente, no habían
recibido la Luz, eran protestantes. Pero buenas personas, gentes
muy virtuosas, a pesar de todo, que temían a Dios... La Providencia
había velado por mademoisselle. Usted sabe que sus padres
murieron y que la recogió una tía, muy buena católica, y que en
casa de esta santa señora devino católica...
Nacha miraba con asombro al Padre, sin saber a dónde iría a
terminar todo aquello. El Padre tenía actitudes pilluelescas, y a veces
daba tales saltitos que parecía que le hiciesen cosquillas. A lo mejor,
no encontrando una palabra, se detenía, levantaba los ojos al cielo,
los bajaba, hacía un molinete complicado, luego una castañuela y un
pequeño salto cambiando la colocación de las piernas, como en un
cuadro de baile. Pero ni por ésas aparecía la palabra, y el buen
Padre debía hacer un rodeo que resultaba a Nacha interminable.
—Y bueno, usted sabe, comprende que... En fin, señorita, me parece
que su vida no ha sido... ¿cómo diré?... precisamente... ejemplar...
No sé si me explico... Y usted sabe, comprende, que en esta casa,
donde... donde... ¿cómo diré?...
Aquí una castañuela, un blanqueo de los ojos y un par de
movimientos de costado. Preparaba un magnífico molinete cuando la
palabra buscada apareció, y radiante, feliz, exclamó:
—Donde... resplandece... precisamente... resplandece la más
acrisolada virtud... usted, con su vida, con sus costumbres, no...
no... es decir... en fin, que no conviene que permanezca aquí...
—En una palabra: me echa de la casa—dijo Nacha, roja de
indignación.
—Oh, precisamente, echarla... usted sabe... usted comprende...
—Está bien, Padre. Hoy mismo me iré. Y hágame el favor de
dejarme sola.
El Padre le hizo una gentil y redonda reverencia, y salió. Pero apenas
había puesto los pies en el corredor, volvió, oyendo que Nacha le
llamaba.
—¿Alguna cosa...?
Nacha había pensado decirle quién era la virtuosa mademoisselle y
las exactas noticias que ella tenía sobre su "acrisolada" pureza.
¡Cómo iba a gozar viendo la cara del Padre Chatelain al oir evocar la
escena del dormitorio! Ahora se vengaría de aquella mujer perversa,
hipócrita, canallesca hasta ser repugnante.
—¿Y bien, señorita? Yo estoy esperando...
Pero Nacha se entristeció de pronto y pensó que las miserias de la
vieja maldita no justificaban su venganza. No sería mala por nada de
este mundo. Que la echara a la calle la francesa, que contase a los
Padres cuanto ella le contó en secreto para consolarla, que la
injuriase, que hiciera con ella lo que quisiese, jamás revelaría a
nadie lo que prometió callar.
—No es nada, Padre. Déjeme sola, no más...
Apenas el sacerdote desapareció, la infeliz se arrojó sobre una silla.
Y con el cuerpo doblado hacia adelante, las manos en la cara y los
ojos estupefactos, permaneció casi un cuarto de hora. Después
suspiró hondamente, sacudió la cabeza con violencia como para
alejar algún pensamiento triste, y exclamó:
—¡Es mi destino!
Luego se vistió poniéndose el mismo vestido que el día antes y salió
a la calle. Detuvo un automóvil que pasaba y le dió la dirección de
una casa de huéspedes de la calle Lavalle, donde vivían muchachas
de mala vida.
XI
ebookgate.com