 Good afternoon everybody It's really nice to see everyone here and it's you know something like I just want to pinch myself and check If this is real because two years we have been on the virtual mode and I have been in a mode which says Good morning. Good afternoon. Good evening. Everybody wherever you are and I could stop with good afternoon today Which is really nice So I hope the session will be interesting and we'll have questions I'm like everyone. I'm here today tomorrow. I think some of you may not come tomorrow, but we can catch up later So we can get started I'm going to talk about this product called Open-ship Dev Spaces. I am the product manager for this product We'll see where this is placed in the overall developers life So this is how we are going to spend our time for next couple of minutes We're going to talk about why Dev Spaces, you know, we keep talking about products So you can ask me why should I use another product? So we'll answer that question What is it and where does this reside? All of that will be answered We'll also talk about a bit of background and history because every product is born with a purpose So we'll understand what's the purpose for Dev Spaces and then yeah The introduction will continue probably one more slide and then where is all of this supported? That that's something we'll talk about what's your roadmap and this is a product, right? So this is not yes I had an idea but that idea has been built and Some of the resources that you can use to kind of learn more about it talk to us Give us some ideas and then we'll have a small demo of yes This is all not slide where it does work in real life. So that that's how the next couple of minutes will go between us So why Dev Spaces? This is the key question. I want to answer before going any further Now, I think this slide you will see for probably All all presentations, but this is the start right? I mean, this is how everybody's life is every day I mean, we all live breathe this slide. So as an individual, I mean, I think I Need not go in detail but in our developer Flow we have two things one is the inner loop. The other is the outer loop, right? So in a loop is where Dev Spaces sits and and that's been used by an individual as a developer We use it every day where our day-to-day job is to code to build that test that debug Deploy at some point in time. We are kind of yes, you know, I I got my task. I did it beautiful I think everyone will like it then you push then the outer loop kicks in so Dev Spaces sits here now And and there are plethora of developers available today, right? So because everyone of us Who has spoken before me we're asking how many of you are developers? How many of you are using VS code and and then for everything there are a couple of fans that go up and down, right? So we have Developers are not just using one tool one language, you know, they are familiar sets for everyone And that's not a mistake, right? I mean that's how the world is and tomorrow by the time I talk There are a million tools coming million tools shutting down. So that that's the life, right? So there are multiple developers and and and all of this means the skill sets need to be upgraded Which is really tough. I mean these are some of the sessions you come to but there will be parallel session happening for another product so we have A wide range of developer and and now everything is cloud, right? I mean wherever you glow it's cloud So some people like cloud some people have time to learn cloud some some applications are born on the cloud And so are the developers, right? Somehow like I only want to code wherever it is. So, you know, it's it's cloud not cloud Wherever it is. Give me something. I just want to Code and that are the majority set of people. That's what we have found out and then there is the mixed bag, right? Yes I started as a carrier when I did everything on my laptop Then the cloud came, you know, I joined the journey. I know a bit of it And then there are some like yes, you know, I know everything in cloud So they are this set of people and I know everything on cloud is a very small set So what happens when most of your production application moves on the cloud? But you know development is still happening locally, you know, how how do we bridge the gap? So that is an important question that you know remains unanswered or it's there somewhere in the mind But we just keep developing So this is a double clip of the developer flow. So we have a set of products That that help you code that help you debug the set of product that will help you build package And that is what you've been seeing in the individual sessions. So if you see um Dev spaces And and and these set of developers like I said someone some some people are like give me something to code I will code finish it and then my life is done Dev spaces fits that kind of cloud Crowd where it says I just need to develop an environment. I have a task in hand I just want to spin up something get coded get done with it, right That that that's where um dev space is like it's in the in the upper quadrant there And then the other tools we are hearing and listening to Now these are some of the challenges that we have seen as we speak to many people out there one is Productivity right like I said a developer comes in. I mean that's the challenge for all of us a developer comes in Then you have to get the laptop, you know put multiple tools then security to it Then I mean there's so much of complexity to get a developer up and running So that that productivity is lost, right? I mean and then you get bored you join an organization It takes you so long to get familiar with the tools and end of it They may not be some familiar tools. You'll have to relearn right and then the complexity starts and then this term, right? I mean This is something like we were looking forward to kovat We want to eradicate kovat and one thing as developers or products when we develop one word we want to eradicate is It runs on my mission, right That's that's the word I hate the I hate the most like it runs on my mission. It doesn't run on mine I mean I'm not bluffing So this fight is something that is again making it unproductive. That's something we wanted to solve the third one is Production environment versus your dev environment, right? I mean this is like I keep you know telling people this is like us coming out of colleges, right? So we studied like 16 subjects 18 subjects and when I came first joined the job None of it or till they have not used anything been 15 years in it again So this is like that, right in the development system. Everything works when it moves to production. There are issues So this is trying to bridge the gap as close as the production environment is that is one of the key challenges that we have seen Skill sets. I spoke about it like As I talk, I know there's another product. Somebody's coming up. My company is coming up with something I'm myself. I'm getting ideas. So I'll come up with another product And to bridge the skills. It's going to take us a long time. So that's something we said, okay skills that side but The basic thing is to code and have a nice application that runs and kind of meets the user needs So that was something and and and then to upskill is is really a hard task So that is something that we wanted to solve Hardware legacy security, right? The code should never lie on the edge Right. I mean on the networks There are a lot of applications that are sensitive. We were talking about some of the very important applications Even in the morning panel discussion and there are some security issues and stuff like that and sometimes Having the source code on the laptop itself is a risky situation for some of the customer applications So we said how we could all you know come up with something that solves This basic purpose and that's how dev spaces was born So we thought we want to keep development very simple And very fast and as close as cloud native and that is the thought we We thought that would solve all of these three problems Keep it very simple and it has to be fast Right because today everything is agile, right? I mean that's the other misused words agile means fast Sometimes it's fragile, right? So That we have to still keep it fast as fast as possible And then you know skills needs to be upskilled. I'm not saying, you know, you should never skill But you know that gap shouldn't hit you really hard when when you're putting things on production So those are the teams that if you actually look at our roadmap We actually build every release and our release cycle typically for this product is about six to eight weeks Again, we are agile, but uh, our themes are simple keep You know, we try to make dev spaces as simple as possible Because and then as fast as possible, right? I mean, you don't want to click a button and then wait forever, you know that Round and round and round not that and then as seamless as it's cloud native So those are the three themes we keep in mind and every feature that we put in the product as to hit one of these buckets So that that's the check gate for us now I'm talking about dev spaces, but Until june or until may we had this product called the code ready workspaces We renamed that as dev spaces. So these two are same Some of us we keep saying code ready workspaces dev spaces We just not got that lingo sometimes right because code ready workspaces is deep in our, you know, brain So the new name for that is open ship dev spaces and we did the rebrand I'm more to align to the overall branding and stuff like that But the intention of the product to be simple fast and cloud native hasn't changed So this is more aligning to the so when when we came up with a new release 3.0 in june, we came up with all new and shiny, right? We had a new logo Used to have the c some of us joke. This is like a neck pillow, but Now we have a nice logo And then we have a new name and then new documentation. Everything is new But the intent or the the problems that the product solves is remain the same And we also had used this opportunity to kind of Change a bit of architectural switch. We wanted to make to make things more again simple faster and cloud native So this is typically compares what was there before 3.0 and you know, what what's there in the new and Just to bring in what what was changed in the architectural side, right? So we had All of our works places managed by a java rest api, but now it's it's all managed by as a Kubernetes api which kind of gave us more flexibility Make it making it more scalable a bit more faster because when you launch a workspace It's much faster now than before And then it also we also kind of sorted some of the authentication things I mean we used to use a red add as a so now we use open shift or So it makes it much much flexible simpler and and easy. So this is we'll see some part of 3.0 as a demo Now, so this is in in in kind of summary what dev space is it? So you can use your familiar tools on the cloud and get a workspace started to develop so You can use a familiar ideas at the moment Chetia I mean eclipsed the is is the id by default But our next release is get up to support vs code as the as the default ide and eventually intelligent and vs code and intelligent are tech preview So you could go and try now and have a hang but we're trying to get get that on production And then some of these customers as we talk in the next slide Are secure environments, you know, I think a lot of question came up on the security as well And this product like I said is a downstream of an upstream product called xlips j So a bit of background on that is When I said code ready workspaces. So it's there in the market for last six years or so It was I mean it we acquired it from a company called code envy So it's been in the market for some time and the upstream for us is j So Che whatever you see Probably six weeks prior will be in dev spaces six weeks later. So That that's the stuff and there are a lot of financial companies and a lot of security. I think today they were questions on You know You are open, but is it secure? You know, there are customers who work with really secure environments and yes, this is secure So we wanted to take care of that aspect as well right because Putting on cloud should not put you in that risk or fear of you know, where this is going to land So that is also happening. But with vs code coming in We have some cool stuff happening like, you know, pair programming and stuff like that So and and then this is all using a dev file I think we've seen enough of dev file as well in our in our topic and that is how I mean and dev spaces is comes free with open shift and that that's the good news as well I mean, you don't have to pay extra or more for dev spaces. It comes free with open subscription and It's available on the operator hub So you could go and search for dev spaces and you would See that and I will also and and if you want to really try this without buying open shift There's something called the developer sandbox that we've been talking about. I think more did talk about the the free subscription. So Dev spaces is there the latest version is up there So you can go and try and and see how really all of this, you know, is is is truth So this is, you know, what you typically support I mean, I think this is one thing that I get asked wherever I go is All is fine. But what do you support? What languages do you support? What repositories that you can support? You know, what browsers can this run? What ocp version is the bare minimum? So this slide is more details into, you know, what stack do we support and what all you can use to run And this one the logo below is to kind of more fill confidence saying, you know, I'm not doing this Um Presentation for the first time and I'm saying, okay guys try out. Tell me how this is. Did you like it? No? Yes, I mean, this is not my cooking, right? So this has been there for some time customers have embraced it and customers have embraced it across verticals So we have customers from telco health care. Some of them I cannot name for confidential reasons We have government customers as well, not just in asia pacific, but north North america and and emia name it. We have customers there big customers secure, you know, small and medium customers So customers of all size and from all vertical So that this is more to kind of say that, you know, you're not going to be, you know, testing this first and then, you know Getting the pain. Um, but but this is being time just tested So this is more to fill confidence. And then what do we support? And this will only increase right so I like I said bs code is going to be the default and now it's tech preview It's going to become the the default Stuff so let's see the demo I will Before we see the demo So so what we can do is you can let's you you could just do your development using dev spaces And what all you can do you can have an ide choose an idea of your choice Like I said developers, you know, don't want to leave their comfort zone zones and come so you can bring your familiar tools It'll be here. You want a particular idea? Yes You could do that and that that's going to be soon a reality as well So what we will try now is I'm just going to take a git url And and see how quickly you can spin up a dev spaces and how quickly you can shed on and and and you know You can just carry on with the remaining work. So let's let's try that We'll come back to this after the demo Okay, so I kept this ready So this is how uh, I'm I'm I'm doing this on the dev sandbox. I'm not on the open shift cluster This is I just want to show that dev sandbox things are real And it's a mimic of how it really looks on on your open shift as well, right? So this is how typically, uh, it it looks This is the facade page of it And then you have spaces to create a new workspace you can also see uh on on the Left hand side on some of the you know Workspaces that I had worked in the past and stuff like that and you also have a set of sample That you can you know start off if you don't you know have an application in her So we have dev files configured and all of that done here Um, or you can you know, just spin up an empty workspace and get going So now I I'll use my demo workspace. I'll put in the git Of url and and I say, you know create a workspace for me So I'll just open up in in the next step Yeah, this depends on the speed and the strength of my internet. Yeah, it's quick So if you actually see it says I'm creating workspace It's looking for a dev file if it doesn't have a dev file when it takes the default And it applies dev file is essentially the configuration file for your workspace And then you know, it starts creating. So if you go back to the dashboard This is starting this workspace called the dev spaces demo And here you also have logs So it's pretty fast. Um, it's almost beginning to run So it will now open up a nice visual code. I mean you you'll see a Visual studio, um, kind of feel this is eclipsed here We actually see here in the url. You would see chaitya workspace So the default workspace now is chaitya But in the future view, you will have a new x to say, okay, I want chaitya or I want vs code or I want intelligent and we'll and the list will keep improving. So this is how uh, you know, uh, the workspace is launched And then you could do, you know You can do whatever you want and this is as quick as you having a development environment and getting started So this is as simple as that you can bring in your own git repository And if i'm done with You know, whatever development I want to do all I do is Go back and say stop workspaces That's it. So this is as simple as get your git, you know, wherever you your source code resides Put it there it'll spin up an environment for you with with your familiar ides You have all the tool sets. You don't have to install anything is it all you need Is a laptop and a browser. I think that that's the basic Anybody has today, right? I mean, this is like having food and water in the house today You know having a laptop and a browser. I don't think is very tough. So Your plane requirement is that and once you have that Development becomes so much easier simpler and It it's simpler because you don't have to install anything. It's as fast as you saw And then it's it's as cloud native as you could. So this is What we you know, we idealized that a developer's life should be and you know We are continuously working to make that as seamless as possible Let's get back to the This is a very small demo. I wanted to Like I said, you could you know start an empty workspace and and you know get started Or you could choose the list of you can just put URLs of okay. I want this You know repository with this ID on on the url and it will start so there are multiple ways of starting or you can just start off with a specific branch of a workspace stuff So these are some of the free resources we have. Um, this is getting updated regularly like I said With the 3.0 release, um, we also revamped our documentation because the architecture and everything changed So we ensured that we have a new shiny documentation as well The upstream documentation is chair documentation and you will see what is going to come in the downstream six weeks ahead of What is there and we also have a lot of community Developers who are contributing and some of the important blogs that said why did we want to do 3.1 and some of what I've been talking For the last, uh, you know the 20 plus minutes And so what what do I want from you all from the session is go to the developer sandbox It's a 30 day free. You know, it's a mimicking, um, open shift You can try my product and see if I Last 20 minutes I bluffed or everything is a reality, right? So I will leave it there. Uh, you could always reach out to me at kmoan at red dot com Um, we can interact if you have any ideas. Yes If you want to contribute to us, you have a great idea or you think whatever we're doing is not as great as you Wanted to be please free to reach out to me and then we can get started But yeah, try and tell me if I bluffed or I was truthful. So That's pretty much it. Thank you Yeah It's a very good session. I enjoyed it. Thank you one question like if you have the code base locally You can make local commit, right? Okay. I didn't hear you If you have the github, uh, code base in our local mission. Yes, you can make commit and then push it later Yes, how does it work here? Uh, how does this work? You want to see that working or you just want to know I mean, is it feasible in this, uh, scenario? Yes, I don't have a Week I I'll show that probably after during the coffee break or something. Yeah, we can show that Like uh, we saw a github's now we explained about the uh, dev space, right? Yes, okay starting from development till end. All right, like we can connect, right? Everything now open. Yes, open shift. Yes Okay, right like now if I want to segregate Uh, saying right like I will be using a doze a cups, uh, dough spaces And like I want to maintain these dev ops process on a different Environment altogether, right? I'll get that piece. Okay. I will do a kind of a development on a open shift with the dough spaces Okay, okay. Now right like from there. I wanted to rest of the activities, right? CICD everything like I wanted to do it on a different environments. Yes, you could I mean, this is part of an inner loop, right? So this is all about once you're familiar. I mean you are satisfied and once you push to the outer loop Then you have a plethora of tools to Carry on with the rest of the whole Cycle, so yes, okay. Like now I'm having my own proprietary ID How to onboard that into your a doze spaces May not I mean depends on How famous and stuff it is how to I mean you could um One is you can reach out to the che community and see but but yeah, I mean to be very honest Adding a new ID which is not being used not for the public. Just like a couple of you want to try your own ID on this You could I mean you can try that. I mean, maybe you can just put the url Of that like I said, right? You can put your git and then the url of you know, which whichever ID you want to support But at the moment I will not be able to guarantee you if it will work Because for now we are only doing a thea We scored an intelligent. We are not tested. So technically it should work But but you know, I will not guarantee the right. That's what the problem At the moment it may not work. I have to onboard. It may not work. Yes. It may not work and for us to onboard It has to be There is a process. Yes pre-process plus must be famous and others will also use right because once it goes And then you will have to test And everything else right so Okay, I will send a mail to you Sure thing. Yes, you can send me and yes, we can see if that works. But technically yes An ID is an ID right should work Yes, what is when you start the workspace and you're shutting down that so does it persist the changes like which are No, at the moment It goes off. It goes Okay, so it has to we have to leave it open. Yes I mean for some time and then this is all about F Meryl development, right? So So there is no way we can Posses the developers changes or not persisted. No Okay, and you know, this is okay if we have single repo right typically in microservices We have you know multiple repositories. I mean if depends how we have implemented it So we have to create one for each of them is I mean every time And at at this point we only have one workspace running at a time Uh, it's in our roadmap to have multiple workspaces spinning up at the same time So at the moment the architecture doesn't allow you to run more than one workspace at a time Yes, sir Yes So all of this is configured in something called your dev file, right? I mean that's where And then your git has your code. So this is this is all like, you know, a containerized Application thing so you just run on the browser. Everything is in that container So you you put your git repository where your code lies Rest all is being taken care by dev spaces. So it just picks your git where your code is And you and your teammate will have similar environments because that's how it is configured in the dev file. So that's how it picks it up It will not be saved. So that's why when you log off, you know, because that's a security breach, right? We don't want to get into that So Once you log off again, you put it. Yes, I mean It it it uses the authentication from whatever your git is at the moment And then you have open shift to earth as well. So it it will not stay there or the code will not be saved None of that Will happen. So it's it's as secure as You're doing it on your local as simple as that Which if you use Yes, yes Yes, so the setting at this point doesn't allow you to Yeah, so eventually we are I mean, we are contemplating that thought but at the moment Thank you. Uh, ma'am. Recently I started using github core spaces Like I just want to know like how is like despaces different than core space. It's very similar, right? I mean, this is a similar product as this Dev spaces runs on open shift only at the moment. I mean code spaces will have its own environment It's it's a comparative product for us recently like github core spaces like Yes, so they have also yes the github recently and and they are using che at some point in time So if you actually read the documentation, there's their reference to che and stuff like that But all of these products fall under This is the same stuff. It's from a different Um concrete. Okay They're similar even the name sounds sounded very similar to our old code ready workspace Thank you