Yandex information technology courses. Life before and after

    Hello! My name is Danil Akhmetov, and a year ago I was not an employee of Yandex. And now I work in a team that develops an internal IaaS solution on a Yandex-wide scale. I did not get into it right away - at first there were Information Technology courses and an internship in one of the most critical areas in terms of fault tolerance - the banner system.

    Since Yandex recently announced a new kit at KIT , I decided to tell you about what experience I got there and what they can give you. Registration is open until October 7, and although there are not so many places, I hope that someone will help my story to decide to go to study and, perhaps, change my life a little.

    A couple of years ago I graduated from Ulyanovsk State University with a degree in Applied Informatics. He wrote his thesis on clusters, supercomputers and the prospects of distributed computing. I was invited to administer in a not-so-large company developing a legal reference and information system. The work was interesting, there was almost complete freedom in solving existing problems - everything went on as usual. It is unlikely that much would have changed if on October 18, 2013, the team leader for the development of the web version of the help product did not send me a link to the page of the upcoming CIT, the fourth in a row.

    Perhaps not all people treat Yandex the same way. In general, Yandex services left me a good impression, but, like the vast majority of my acquaintances from the field of information technology, I searched on Google. The default browser since the early beta versions was Chrome, and mail from the first year was Gmail in a personal domain. Only my father, a candidate of chemistry and a doctor of pedagogical sciences, preferred Yandex, and in discussions about my future career and plans for life, he said that the best programmers in Russia and Yandex services were always cited as an example, claiming that they resolutely best of all others. I used to trust my father, and that was probably why I had respect for people who made Yandex. And not only to programmers.

    To register for CIT it was proposed to write about yourself, optionally you could attach a resume. After a successful submission of the form, I received a test with questions that did not cause difficulties. That was probably what was intended, because the coolest thing was ahead.

    The whale has begun. In a huge and prohibitively bright office, a complete audience of CITs was gathering. Each time, “fighters” came to us from different “fronts” - Mail, Drive, Market, financial services - and shared success stories. I was greatly impressed by Victor Ashik , a permanent leader of CIT and a mentor to many, many specialists who met him at least once. From the first minutes he aroused my personal respect.

    I discovered Cgroups, immersed myself in IPv6 specifications, consolidated the skills of everyday encryption of data and connections with public and private keys and, most importantly, discovered Python as an everyday system administrator tool . KIT gave me a huge push, which was very lacking to reach a new level. But I still had no idea how soon and cool my life would change.

    The courses ended with pizza and the award of certificates of completion. I learned that some prominent participants were offered internships at the company. Honestly, I also really wanted to be in their place, but I didn’t really count on such an opportunity, because I thought that I was much weaker than those who studied at CIT with me.

    However, luck smiled at me. On December 14th, a phone rang and I received an invitation to an internship. The next three months I spent all my free time from my main job in the Yandex Banner System Operation Group. It was a difficult, but amazing time: my colleagues were the creators of services that process many millions of click throughs on banners per day, and those on whose shoulders all the fun called "Yandex" rests. In addition, I worked with a man who hacked SPS3. Working with the guys, I added the possibility of ultra-high-speed network loading of the loaded machines to the intraproject system of server filling using the barely announced lpxelinux, finalized the network file system remotefs for the needs of the department, mastered the automation of routine tasks using jenkins, and better understood the packaging of its Linux software.

    When my internship came to an end, it turned out that I split off from the operating group of the banner system to the development group of the infrastructure cloud as junior devops. Perhaps the key role was played by the fact that my thesis at the university was devoted to computing clusters.

    For many, it will not be a secret that Yandex already has one cloud technology - Cocaine, but this is not about it. Cocaine is a system that makes it possible to create cloud applications using the cocaine API - that is, PaaS (Platform as a Service). The team I smoothly rolled into is developing a company-wide scale IaaS solution (Infrastructure as a Service), which is used in so many projects. Simply put, this is such an internal DigitalOcean where a user (administrator, developer or tester from any Yandex department) can easily deploy any number of virtual servers with any characteristics in any network and domain zone. And, as if by magic, manage them, forgetting that there are physical servers. Only all this without billing and not DigitalOcean, of course.

    The IaaS of Yandex is based on the modified OpenStack , which is closely integrated with intra-index authentication (a small version of Yandex.Passport), monitoring, cross-center infrastructure and many improvements that claim to include the original OpenStack in the upstream. The cloud is a very, very complex thing, consisting of a large number of components, some of which are not found anywhere outside the company. The service has several levels of abstraction, through which it sometimes happens with a crash to fall to the very bottom, to bare iron, but even today we guarantee internal users a quality of service in which productive servers can be placed in the cloud.

    Corporate IaaS is perhaps one of the youngest and most promising for today. Being constantly between the development of administrative tools and the actual administration of the infrastructure cloud, working in tandem with the developers of IaaS'a components, you can see the problem from several sides at once and solve it in the best way. Even walking along the obvious rake, it’s nice to understand that you go first on them.

    When I went to CIT, I wanted to learn from the best and apply what I learn, wherever I go. Working in Yandex and solving everyday tasks together with those who can teach a lot is interesting and cool. I am happy to be here now. But this would not have been possible not only without CIT, but also without all those who have been with me all the last time: a scientific adviser at the university, colleagues at a previous job, CIT students with whom I studied and got an internship, friends, and, of course the parents. Thanks everyone!

    Perhaps your story will seem too personal to you, but I will be glad if it helps someone to get together, and maybe take a new important step in life. And we will tell you more about our internal IaaS.

    PS By the way, all the lectures of past courses posted on Habrébut the program is updated every year. A list of upcoming lectures can be found here .

    Also popular now: