WEBVTT

99:59:59.999 --> 99:59:59.999
Welcome back, the next talk will be
Jan Kiszka

99:59:59.999 --> 99:59:59.999
on Getting more Debian into our
civil infrastructure.

99:59:59.999 --> 99:59:59.999
Thank you Michael.

99:59:59.999 --> 99:59:59.999
So my name is Jan Kiszka,

99:59:59.999 --> 99:59:59.999
you may not know me, I'm not a Debian
Developer, not a Debian Maintainer.

99:59:59.999 --> 99:59:59.999
I'm just an upstream hacker.

99:59:59.999 --> 99:59:59.999
I'm working for Siemens

99:59:59.999 --> 99:59:59.999
and part of the Linux team there
for now 10 years actually,

99:59:59.999 --> 99:59:59.999
more than 10 years.

99:59:59.999 --> 99:59:59.999
We are supporting our business units
in getting Linux into the products successfully

99:59:59.999 --> 99:59:59.999
for that long time, even longer actually.

99:59:59.999 --> 99:59:59.999
Today, I'm representing a collaborative
project that has some relationship

99:59:59.999 --> 99:59:59.999
with Debian, and more soon.

99:59:59.999 --> 99:59:59.999
First of all, maybe a surprise to some
of you,

99:59:59.999 --> 99:59:59.999
our civilization is heavily running on Linux
and you may now think about

99:59:59.999 --> 99:59:59.999
this kind of devices where some kind of
Linux inside,

99:59:59.999 --> 99:59:59.999
or you may think of the cloud servers
running Linux inside.

99:59:59.999 --> 99:59:59.999
But actually, this is about devices closer
to us.

99:59:59.999 --> 99:59:59.999
In all our infrastructure,

99:59:59.999 --> 99:59:59.999
there are control systems, there are
management systems included

99:59:59.999 --> 99:59:59.999
and many many of them run Linux inside.

99:59:59.999 --> 99:59:59.999
Maybe if you are traveling with Deutsche
Bahn to this event these days,

99:59:59.999 --> 99:59:59.999
there was some Linux system on the train
as well,

99:59:59.999 --> 99:59:59.999
as they were on the ???,
so on the control side.

99:59:59.999 --> 99:59:59.999
Energy generation.

99:59:59.999 --> 99:59:59.999
Power plants, they are also run with Linux

99:59:59.999 --> 99:59:59.999
in very interesting ways, in positive ways

99:59:59.999 --> 99:59:59.999
Industry automation, the factories, they
have control systems inside

99:59:59.999 --> 99:59:59.999
and quite a few are running Linux inside.

99:59:59.999 --> 99:59:59.999
And also other systems like health care,
diagnostic systems.

99:59:59.999 --> 99:59:59.999
These big balls up there, they're magnetic
resonance imaging systems,

99:59:59.999 --> 99:59:59.999
they're running on Linux for over
a decade now.

99:59:59.999 --> 99:59:59.999
Building automation, not at home but in
the professional building area.

99:59:59.999 --> 99:59:59.999
Actually, as I said, the train systems are
going to be more on Debian soon.

99:59:59.999 --> 99:59:59.999
We have Debian for quite a while in
power generation.

99:59:59.999 --> 99:59:59.999
"We", in this case, Siemens.

99:59:59.999 --> 99:59:59.999
We have the box underneath,
on the third row,

99:59:59.999 --> 99:59:59.999
the industrial switch there is running
Debian.

99:59:59.999 --> 99:59:59.999
And the health care device is still
on Ubuntu, but soon will be Debian as well.

99:59:59.999 --> 99:59:59.999
Just to give some examples.

99:59:59.999 --> 99:59:59.999
These are the areas where we, as a group,
and we, as Siemens, are active.

99:59:59.999 --> 99:59:59.999
But there are some problems with this.

99:59:59.999 --> 99:59:59.999
Just take an example from a railway
system.

99:59:59.999 --> 99:59:59.999
Usually, this kind of devices installation,
they have a lifetime

99:59:59.999 --> 99:59:59.999
of 25, 30 years.

99:59:59.999 --> 99:59:59.999
It used to be quite simple with these
old devices,

99:59:59.999 --> 99:59:59.999
simple in the sense that it was mechanic,
it was pretty robust

99:59:59.999 --> 99:59:59.999
I was once told that one of these locking
systems,

99:59:59.999 --> 99:59:59.999
they were basically left in a box out there
for 50 years and no one entered the ???

99:59:59.999 --> 99:59:59.999
No one touched the whole thing for 50 years

99:59:59.999 --> 99:59:59.999
These times are a little bit over.

99:59:59.999 --> 99:59:59.999
Nowadays, we have more electronic systems
in these systems

99:59:59.999 --> 99:59:59.999
and they contain of course software.

99:59:59.999 --> 99:59:59.999
What does it mean?

99:59:59.999 --> 99:59:59.999
Just to give you an idea, how this kind
of development looks like in this domain.

99:59:59.999 --> 99:59:59.999
So ???

99:59:59.999 --> 99:59:59.999
development takes quite a long time
until the product is ready,

99:59:59.999 --> 99:59:59.999
3 to 5 years.

99:59:59.999 --> 99:59:59.999
Then, in the railway domain, it's mostly
about customizing the systems

99:59:59.999 --> 99:59:59.999
for specific installations of the railway
systems,

99:59:59.999 --> 99:59:59.999
not only in Europe, they are kind of messy
regarding the differences.


99:59:59.999 --> 99:59:59.999
So you have specific requirements of the
customer, the railway operators

99:59:59.999 --> 99:59:59.999
to adjust these systems for their needs.

99:59:59.999 --> 99:59:59.999
And you see by then,

99:59:59.999 --> 99:59:59.999
after 5 years already, a Debian version
would be out of maintenance and

99:59:59.999 --> 99:59:59.999
if you add an other year, you can start
over again.

99:59:59.999 --> 99:59:59.999
So, in the development time, you may
change still the system

99:59:59.999 --> 99:59:59.999
but later on, it's getting hard to change
the system ???

99:59:59.999 --> 99:59:59.999
because then the interesting parts start
in this domain, not only in this domain,

99:59:59.999 --> 99:59:59.999
that's safety and security assessment and
approval for these systems.

99:59:59.999 --> 99:59:59.999
And that also takes time.

99:59:59.999 --> 99:59:59.999
For example, in Germany, you go for the
Eisenbahn ???

99:59:59.999 --> 99:59:59.999
and you ask to get a permission to run
that train on the track

99:59:59.999 --> 99:59:59.999
and if they say "Mmh, not happy with it",
you do it over again

99:59:59.999 --> 99:59:59.999
and it takes time

99:59:59.999 --> 99:59:59.999
and if you change something in the
system, it becomes interesting

99:59:59.999 --> 99:59:59.999
because some of these certification
aspects become invalid,

99:59:59.999 --> 99:59:59.999
you have to redo it.

99:59:59.999 --> 99:59:59.999
And then of course, these trains on
the installation,

99:59:59.999 --> 99:59:59.999
the have a long life as I mentioned
before.

99:59:59.999 --> 99:59:59.999
So how do you deal with this in
an electronic device and

99:59:59.999 --> 99:59:59.999
in software-driven devices over
this long phase?

99:59:59.999 --> 99:59:59.999
That our challenge