 Hello everybody, sorry, hey, my name is Alex Lomov, I work at Alturas and that's my logo and that's the logo of Alturas and I work with Bosch for almost three years and it was quite a time and I had lots of stories about it to tell but the time frame is very short and I afraid that we need to move this discussion to the next sessions and after-party. I would be happy to talk with you about technical implementations of all features I will mention today but it would be impossible to describe them right now and I feel sorry about this. Anyway, I also wanted to say thank you all for staying, for surviving all this summit and being here talking about this perfect tool and also thank you all organizers that give me this opportunity to be with you and to make talk with you. Finally, I got the slides, okay, so from very long time ago I met Bosch for the first time and I saw its logo that is not official logo but still it is on Vicky page and you know, you think you kind of take it as official and here is it, if you don't know this is little shell and while I was not familiar with Bosch I was afraid of this logo because I thought that I will find pearl inside of this product but still it was Ruby and thank you. So after I got acquainted with this product I liked the way this logo is done because you know this is shell and it hides something and you never know what it is and you know because of the speed of how Bosch is developed and evolved you can go to the same court in a few, during two weeks and it will be completely rewritten and that makes Bosch something like a good book. So when you open it another time you will find something interesting there and you will find another clever thought and you can learn from it a lot. So for those who just starting to work with Bosch I need to say that there are lots of cute things inside of this shell but also there are quite dangerous things. So this was my feeling when I implemented CPI before external CPI mechanism was implemented. So I'm here to talk about Bosch 2.0 and this version, this bus around this version made me, gave me a desire to wrote a bot for Slack to answer the questions about what's Bosch 2.0 because in Bosch Slack channel there are every month such, every week such questions arrive. And I, first time I hear this term was from ONSI, there is his talk and if you haven't seen it you just need to do it right now, you can skip my session, you'll, okay, okay, yeah. Run, why are you here? So after I heard this term for first time I was wondering what is behind this, this second, this number two here. So it was very, very large question for me and I was wondering how versions are created in Bosch, how, is there any philosophy behind it and why we have, why we need to have this second version after you know 3,000 releases after the first one. So the current version is 1.3232 and that's, you know, large number. So I'm not quite sure that they haven't changed signs I made these slides yesterday so don't believe me on the wall, don't rely my words still. I have my personal feeling and I'm feeling like I have an idea of this version and to my mind it should be ended on 1.6180, it's, you know, it's a good number, number that describes golden ratio. So I'm here to tell you that I have feeling in my brain that there will, there will no be release two points or there will be release with this number, okay. And so when you look at how Bosch evolves it makes you feel that you look on some kind of evolution process here and that's really amazing how it can go so fast and so far. And there are several tools and approaches and things that I wanted to tell you about this evolution process. First of all, this evolution is continuous and you will never get another release with plenty of features in it that are new for you but features are added one by one, step by step and you'll never notice when you'll come to Bosch 2.0. So another thing is Bosch Notes project. So this is a project that was created by so-called Cardinal of Bosch, representative of Bosch team in open source as I take him and you can find a lot of interesting stuff about plans and about what should be done there. So I will place these slides on my speaker deck and you'll be able to get this link. And I think that it is extremely useful to go through these notes to get idea of direction where we go. And also you can influence these directions by creating pull requests to this project or creating issues. If you have something in mind, just create issue in this project and it will be reviewed. So after then, the second really great driving force of the progress here is concourse. If you don't know it, run from my section and try it right now because it's a really amazing thing. I can't imagine anything that it can do. So it can post slug messages, it can write your mail, it can brew coffee. It's really powerful thing, that's why I decided to coordinate with it and ask it to create me some slides about this topic. So here is concourse running on my machine and further slides will be provided from this concourse. And now I will describe you features that are most important personally for me and it is hard to decouple these features and make a list of groups because all of these features influence each other and maybe the list will be not so right for somebody. So first of all, I want to admit that there is a documentation update. So when I started to walk with dogs, to walk with Wash, there were no good documentations and the one documentation you had was source codes. After that, lots of updates are located in Manifest. Manifest is like the sole of all Bosch deployment and lots of new features are added to it. And there is a list, it is incomplete but still the main feature for me here is better naming. So it is sometimes it's hard to explain people why we have these jobs and so on and there are much more clear obstructions that people can get, something like clusters and so on. So at this moment, work is in progress and in future we will have better Manifest. And another great feature here is CloudConfig. So you already hear about it many times and just repeating that CloudConfig helps you to separate your infrastructure dependencies from your Manifest and it is quite amazing so you can have one file for every infrastructure you deploy. If you take a look on how concourse is implemented and how concourse Bosch release is made, you will find this stuff there and it is quite amazing and I like concourse also because it has a lot of really many new features from all over, from different technologies including Bosch first of all. You hear many times here about links and these links will work as relations between jobs deployed with releases. So this kind of brings us on the level of obstruction when we will be able to point take this job and connect with this job and you forget about messing with IP addresses and putting them in Manifest. Many different updates are here and this will allow Bosch to get rid of necessity to use PIF for instance for running networks, for creating IP addresses and so on. So it's quite good news. So this one uses the greatest one for my mind because sometimes there is such torches by Manifest when you have Manifest with 5,000 lines and you understand that guns don't kill people, Manifest kill people. So also global networking is here and partly it is in release with links. So with global networking you don't need to have IP addresses in your jobs, Bosch director will take care about all of this stuff so you can sit and relax. So but to connect to releases, to jobs you'll need to have these links in these releases and they will provide a mechanism how one job will figure out about how it can connect to another job. Another thing I wanted to mention is compiled releases here. That's like a great feature and it allows us to reduce time of deployment in many times but simply not compiling everything in the second time. And I also liked Bosch IO sites with the list of available releases and it kind of the place where you should go every time you need to deploy something new. So changes with stem cells. In stem cell was, in very beginning building stem cells with new stem cells was quite a bit hard just because you didn't know the whole process. And now there are stem cell pipelines where you can look and figure out how this works. Now you still need to fork these CI pipelines to be able to update them and you can't create your own asset like you can do with CPI for instance. But still it is a good move forward. Also the great feature here is the possibility of using addons. Addons are much the same as releases and the one thing is here you cannot use it in every release. You can just declare them with stem cell and it will appear in every stem cell. So if you have some agents that should be on every virtual machine with this stem cell they will be there. There are lots of other features I'm excited about. When Bosch in it appeared it was like a lightning and the happy time began. So now we have external CPI and it is really, really easy, much more easier to create new CPIs. I'm not telling you that it is easier because you need to consider different... They want to go to a chance to talk. That's great. I really like this talk because it has such solid view and perspective on where we should go and where community and people should appear. That's kind of amazing thing because such high levels view is not always so public. So another cool feature that make our security guys happy was your integration. So now Bosch can work with all stuff that is provided by UVA. So you can connect with LDAP and so on. Also there is such thing as dynamic provisioning and this is like an idea that Bosch will be used as service in call foundry. So Bosch will become service and whenever you run create service it will go to Bosch and tell it to deploy cluster and you will have lots of clusters separated without any interference between them and it kind of great stuff because there are lots of product that don't have multi-tenancy in them and this is kind of the one solution for them. So I know that there will be lunch here so I will not take your time because I guess you are quite of starving now. I'm just from lobby having to take the programming. So these two things that should go together stakes and programming and I'm not so starving as you so that's it and thank you for this opportunity to talk to you.