My dear friends, brave critics, silent readers and secret admirers, SDSM is coming to an end.
I cannot boast that in 7 years I have touched on all the topics of the network sphere or that at least one of them has been fully disclosed. But that was not the goal. And the purpose of this series of articles was to introduce the young student by the hand into this world and lead him step by step through the main gallery, giving a general idea, and save him from painful wanderings through the dark corners of the consciousness of Olifer and Olifer in painful attempts to find the answer to the question of how everything apply it to life.
SDSM was planned as a short practical course βhow to learn online in a monthβ, but resulted in 16 (actually 19) long issues, which we have even renamed into βNetworks For the Most Harshβ. The total number of characters has exceeded 1.
It would be correct to stop at BGP, but itβs not very successful to enter IP into MPLS - I had to capture it. Perhaps it would be better not to take on Traffic Engineering, but if you already took up L2VPN, how to stop? Hardware architecture is an essential preface to QoS. And QoS was demanded for so long that it was impossible not to write about it. Absolutely nothing to get rid of.
The last article planned a certain collection of best practices (offer a nice-sounding synonym - and I will replace this tracing paper) on the design of providing networks, but over time and experience it became clear that this is not only an immense layer of approaches, but also an excellent ground for verbal skirmishes. And why is it necessary to stop at providers? What about telecom operators? What about data centers? What about business networks?
You canβt say: do it and do it right. You can't teach an engineer how to design - he has to grow up to it himself, making his way through his thorn bushes.
This is exactly what SDSM offers - a barely noticeable path from simple to complex.
Here's how much it's been...
A bunch of people had a hand or a head in writing these articles:
Membersβ¦
- Max aka gluck - co-author of the first articles and author of the 4th part about STP and the IP SLA section in the 8th. Part-time for more than 5 years - the administrator of the project.
- Natasha Samoilenko β additional materials, tasks and their solutions to many editions. As well as support that cannot be overestimated.
- Dmitry aka JDima - Critic and proofreader.
- Alex Clipper - Critic and proofreader.
- Dmitry Figol - Critic and proofreader.
- Marat Babayan aka botmoglotx - author of issues about EVPN and photos for issue 14.
- Andrey Glazkov aka glazgoo - Critic and proofreader.
- Alexander Klimenko aka Volk - Critic and proofreader.
- Alexander Fatin - Critic and proofreader.
- Alexey Krotov - Critic and proofreader.
- linkmeup command - Proofreading materials.
- Anton Klochkov - organizer. Thanks to him, the project has a laboratory environment, a broadcast server, and now its own podcast hosting.
- Anton Avtushko - a website developer who has been faithfully serving for 6 years. Leavestreet is long gone, no plugins are maintained anymore, and the site is still alive. And for lookmeup.linkmeup.ru, stillborn but with a good idea.
- Timofey Kulin - Site administrator and developer
- Nikita Astashenko - website developer
- Nina Dolgopolova - illustrator. Logo and illustrations for the 9th and 10th issues.
- Pavel Silkin β illustrator (0th and 1st issue).
- Anastasia Metzler β illustrator (11th issue).
- Daria Kormanova β illustrator (12th issue).
- Artyom Chernobay - illustrator (13th, 14th and 15th editions and this final article).
The QoS article was the last in the series. By the time it was completed, it became obvious how simple and incomplete the first issues were written. What are the first ones? Up to BGP everything is very bad.
In addition, readers often find errors themselves and suggest corrections.
The idea to transfer all this to gitbook, brought by Natasha Samoylenko, looked so attractive that we did it:
Today there most of the articles are up to date.
Anyone can fork the project, make changes and make a Pull Request to master. After I commit it, the changes will appear in the gitbook.
So far, I believe that there will be no paper book on SDSM. While I'm not ready to devote time to rewriting the first articles in order to get a complete, beautiful and, most importantly, comprehensive material about networks. Still, there are many interesting things in this life, and I will somehow cope with perfectionism.
Not the most recent factor in completing the cycle and shifting interests is a job change.
And a short announcement: our hands are not for boredom, but for graphomania. Stay tuned for the next series of articles. About automation.
Source: habr.com