I'll try to provide a very practical approach to what you have discussed, Daniela. You brought some theory into this. I'll try to bring some practice into building this interface. And this is actually, over the years, as an urban metabolism researcher, I have been extremely frustrated into many things. And I'll try to share my frustrations and hopefully together we can solve our frustrations all together by developing common tools. And I think that today we have mentioned how important it is to collaborate and how important it is to build collaborative tools that can communicate between one case study to another, between one city to another, between one context to another. Just a context. So I also did my PhD on urban metabolism. I struggled to find data. Luckily Brussels was a rich data case study and there was already back in the 70s a lot of data. So it was quite easy to work in this field although back in the day there was not a lot being done. But I also felt, because I was alone in this sphere, that I had to reach out to many other researchers out there that are working on the same field. And actually many of my colleagues were in South Africa, in the US, in other European cities and they also felt the same thing. They did urban metabolism and they felt alone in this concept because it's so systemic you have to bridge a number of things and because in academia you're very siloed as well we kind of didn't find a place for us to fit. So this is where metabolism of cities was created before it was called actually MFA tools. And the idea was how can we develop a place where information, knowledge and tools can be gathered, centralized and also develop open source tools for the community. So I'll present to you some of the tools we have created and I think would be useful for this community. Some other tools were presented this morning and I really am very eager to join forces in order to make them compatible. And the tools I kind of see two or three different tools to bridge this gap between science, policy and practice. I think there are tools into knowledge and learning. A lot of people mentioned we're missing information. Where do we find this information? It's so complex but I want to get started but how do I start? So Andre who's right somewhere over here was actually the first one that they commissioned us to do an online course on urban metabolism for policy makers. That was done already some years ago. And the idea was to provide some knowledge for policy makers. Of course we should rethink of doing this for other segments of population. It could be for practitioners. It could be for citizens. It could be for many other segments. But the idea was to start with already something, an online course on urban metabolism and how it can be applied in policy making. So this is out there already. And also gathering the knowledge out there. We have a number of case studies we have found actually articles, reports, policy documents. I'll try to show you that directly so you can, the next time when you have time to lose you'll procrastinate on our website. So this is the website. It has known some iterative changes. In resources you can find a number of things including the publication list. And over there you can find if you're interested into one, let's say publication in one city for one flow, you can start filtering them up over here. We have around 300 publications, four cities, but we have 700 publications at other scales as well. So countries or regions or islands. And then you can start seeing where they are, see which city it is, see which publication it is, et cetera, et cetera. And then you can also filter them by flow or by sector, et cetera, et cetera. So that was already something to be done. We needed to centralize all of the information because there is so much production today. We kind of need to know what is out there and kind of pass the excuse of where is it? Now of course that's one thing to put everything together. The other thing is of course to know that this exists and this is out there. The second one is analysis. We definitely have mentioned an analysis today and we definitely have mentioned the need of common analytical tools. So that was the second, let's say, challenge that we wanted to face was when you look at urban metabolism studies in the literature, many of the researchers and practitioners are actually using different ways to approach the thing. They measure different flows. They measure flows in different ways. And because it's so different, we can compare them and we're stuck and we have to start all over again. And the same thing starts if one of you starts to analyze Brussels, well, there have been already two or three studies in Brussels. But if you don't find the data and if the data are not there, then you have to start all over again. So you're losing your time. You're losing money again, et cetera, et cetera. So how do we come about this? So there are some challenges around urban metabolism data. And we think we should not have these challenges anymore. We should go to the extra step, which is actually analysis. So the challenges are, of course, it's a time-consuming fact. A number of people are mentioning this and you mentioned it as well, Daniela. We're lacking time and we want more funding to have more time into doing all of this. So collecting data is data-consuming. Many times it's difficult to access because of confidentiality issues, but also because we don't find it. And sometimes this data is open data, but open data does not mean it's accessible. You have to find it and you can spend hours and hours into do that. It's also scattered because of the silos and all of this. I spent two years to kind of find information on Brussels, knocking on doors, looking in archives and all of this, and the next person has to do it all over again. And then it's inconsistent format. So energy can be measured in gigawatt hours, in calories in many different ways. And so the different agencies will have different formats. So this is one of the main challenges. And this is why I'm going to show you one of the dashboards that we're developing on urban metabolism. And the idea is to have a centralized platform where we can put all of the data there. It's, as whatever we do in Metabolism of Cities, open source. So you can just copy all of our codes and use it in your own city or case study for free. But of course, we're trying to have an academic rigor behind all of this. So we're trying to have as much as a rigorous database system and a rigorous way to account flows. And what's very different from most of the examples out there is that is community driven. So all of you can actually upload data. Any of the citizens in the world can upload the data. And you don't need a commission from a city to actually do that. It can be a bottom up initiative and not only a top down initiative. Let me just show you how this works in a second. So over here, if you go to Cities, you can look at some prototypes. And of course, we have online video tutorials of how to do all of this. So you have your city. You have some sectors that you want to analyze. And what you can see are data sets, maps, information on, let's say, documents. And then some photos, reports, and all of that. Let's go into a specific sector for Cape Town to have a look how this works. So let's take the waste sector. What we generally try to do is to provide general information on a sector. So waste generation, waste collection, all of the kind of segment of waste. Then we kind of visualize some of the data sets that we could find. You can very easily upload it into the system. Let me just show you something over here. So this is the general waste entering disposal facilities. You see what is the source of the data sets. You see how many data points, who has included this. And you can of course download the file and do it yourself. And there is also some data quality. So because data is so, well, you know how difficult it is sometimes to trust some of the data, we also have some data quality insurance. But all of this is based on open community things. So someone can add the data. Someone else can say, wait, this data set I'm not sure is so relevant. Perhaps I would give different scores. And then you can visualize it as you want in different formats. You can visualize it in table forms and you can download the data if you want. So this is the data components. And then we mentioned a lot of space. How do we specialize data? We've also tried to specialize the infrastructure of some flows. And then if you have information, of course, you can also add information for specific infrastructures every time. So this is one refuse transfer site because we know where it is. We know what it looks like. And then we have data for this specific site over there, et cetera, et cetera. And this is just for the, so this is how it works in general. But all of you can very easily upload data. You can choose what type of data you want. It can be material flows, material stocks, but also articles. And you can build your own dashboard for your own city immediately if you want. So we're trying to take out all of the barriers and all of the excuses why urban metabolism is not really being used. One of it is cost. The other one is, well, we need to centralize information. The other one is, we need to visualize it somehow. And because we think that policymakers and city officials should not spend all of their money into actually doing the data collection practice, but actually changing the metabolism really and working on experimentations, we're trying to lift off these barriers. Now, this is only at the city level. The next plans are we have some friends that are very interested into the islands. And because islands are like the quick census, well, if you want to work on circular economy, islands are a perfect laboratory because they have the limited spaces. So we also have a sister website called Metabolism of Islands, where researchers are doing the same for islands. And the idea is now that we're doing metabolism of nations and metabolism of regions. We're not there yet, but we want to have these extra steps. The idea is that all of these, of course, websites are interlinked. So when someone adds a publication somewhere, you can see it from the other websites. And when you're gonna have, let's say, a national metabolism of nations, then you would know what are all of the cities that I have in the other platform and then see it there. Vice versa, we were talking with Mariana in the morning about what are the scaling factors at the national scale. So if we have the nation for the city we're studying in, then you look directly at all of the data at the national scale and you can do this process automatically. And then the last thing we're trying to do, which was actually funded by Vlinder and Circuler is do the same thing, but for companies. So a material flow accounting for companies, where companies can, well, input all their information about input flows, output flows. And once you have this information, you can do many solutions. So if you know all of the output flows and the input flows of one company, then you can start doing the famous matchmaking of flows, for instance. You can also start thinking about where do I centralize infrastructure. If I know that companies are actually have this type of waste flow, etc, etc. And the idea behind all of this, and it's not there yet, but the idea behind all of this is that as all of these platforms are linked, you would know where the flows from the companies are within your city. So if you know that a company has exchanged materials with another company within your city, then you directly know that your city has increased their circularity by a bit. So all of this can help us to have more streamlined and updated information on all of these data sets. It's not only top down information anymore, but we can start populating it from the bottom up. There is one segment I didn't discuss, but it's on our to-do list. But at the very bottom, it's metabolism of households. Of course, all of us live in households and we consume, and perhaps there is more to be done over there. So in the analytical perspective, this is, let's say, the tools that we have been developing and we think might be relevant. Of course, the more inputs and the more collaboration we have for all of this would be great. Again, all of this is free, it's open source. So please use it as much as you can. And then there's the last elements I wanted to add over here for the open tools. So I mentioned multiplicity, so far where we are is in the data warehouse phase, which means this is an urban metabolism dashboard. We don't refuse any type of data set. We include everything, but of course, it's very difficult because every city has a different amount of data sets than others. And other flows are represented in one city and not in the other. The next step would be to have a much more streamlined approach. So we want to have the same flows for all of the cities. And if there is not a bit what was mentioned in the morning, if there is no sufficient data, then we provide estimations for this. And the last one would be the data analyzer analysis phase, which anyone could plug in any tool or model within this data warehouse or data dashboards and you could predict scenarios. So what if Brussels had 200,000 more inhabitants by 2030? Which is more or less the scenario. What if we have more circular economy jobs in Flanders? What if and all of that? Because today we are very much at the, we're struggling already to get data, but we're not very good at doing these scenarios, as mentioned, Daniela. So this would be the ultimate phase of these tools. I showed you how we can include all of these. And the idea is we have been, so these are the tutorials. You can find them on the website. How to include all of the data quite easily. We have been now doing what we call datathons. So we go to cities, some cities ask us to go there and they implement the data in the course of afternoon, a day, two days. It depends on the case study. We've done this in a couple of cities. And we hope that normally we shouldn't be there anymore as well. This could be a self-provided service by city officials that do that for themselves. And we also had back in the day online material flow analysis tool. But this is a bit in the graveyard right now. This is typical material flow analysis, but this was not as appealing as the dashboard I mentioned. This was the material flow accounting for companies. And then the last bit I wanted to touch a moment about is we need community building tools. Learning is one thing, knowledge is one thing, analysis is the other thing. But we need to figure out ways that the wonderful people that you are remain in the loop of information and continue to work together and we need to find ways to do that. There are easy ways. So we've tried to develop this circular metabolism community. Some of you are already part of it. The ones that are not, please email me and I'll include you. This is informal community around people. So there is a forum where we kind of exchange information about all of this. There's a calendar because there are so many events out there in the topic. We hardly have time to actually know what they are and keep up with all of these. So if you have more events, you can put them there and everybody can receive them in their calendars. And while in the case of Belgium we've tried to pinpoint all of the initiatives that exist out there, but of course there are thousands and thousands more in Belgium and thousand and thousand more in the Netherlands and in other countries. But it could be a centralized place to have information. There's also we're trying to, well, we have a podcast around all of these topics and we try to interview relevant stakeholders and experts to continue this discussion after this event. So continue having some information on all of this. Three years ago we did this seminar. We're trying to have, unfortunately we should do this more often I guess. I don't know what the structure is and we will have this discussion very soon. But so far we're trying informally to develop some more tools. I think we need to go the extra mile in the very near future and we have to think together, what are those tools that we need to build our community? These are the couple of things that we have been doing. But your input will be most welcome at the end of the debate of this. So thanks.


I am happy to note that we have accomplished the objective of what has brought us here. That is to resolve the long-standing UQT issues. I am glad that the matter is now settled and we will go forward as a stronger and united union. Again, I want to thank you for helping us through this process and without you, we would not have achieved that. This is a union that is a multilateral institution where decisions are made lightly on consensus. We had to go into a voting system unless it becomes up to this. What I have seen yesterday is that the most difficult topic that we had is resolved by an acclimation and not by a vote. Let's give that again the very option of a big round of applause. We are a family. We are a real family. We have found it yesterday. We have together demonstrated the value of multilateralism and at the moment we have adapted one of the most important reforms for this union to know the system of global hostile immigration. It is therefore a modern country that is going to suffer 145 refugees on October 9. A multilateral, modern international organisation is working. The public service is working. So how can we not see the future of the sector, the future of the UPU, with exploit?


Good morning. Good afternoon. Good evening. Wherever you're hailing from welcome back to another KBE insider show I am Chris short host of the most of this thing we call redhead live streaming I'm joined by a special guest host today Steve spiker as well as our special guest machek shuluk but you know and machek is a Great contributor to the community. I've lost the page with all his descriptions all of a sudden the tabs, which are Rooney Hang on that he we're gonna talk to machek today about you know being a software engineer at redhead obviously But also about what it's like being a double SIG lead and his work on the Kubernetes CLI and controllers But first the news Mina take it away. Welcome back by the way. Thank you. Hi. Good morning everyone Gonna talk about some highlights here as I do on on all episodes except I guess Gordon did a really really good job last last month, so I do have a heart to uphold But security has been But a big issue I think with Kubernetes in the last couple of months and one of the Couple of the articles that I want to highlight There's a new tool that wants to save open source from Supply chain attacks SIG store will make a code signing frigate easy for software developers providing an important first line of defense this is I think a really really good first step in in in You know Defending those attacks and then there's a NSAC is a Kubernetes hardening guidance, which also Identifies the common areas of Kubernetes security risks as supply chain malicious actors and insider threats It aims to educate engineers to avoid common Misconfiguration issues and safeguard applications the guidance suggests that supply chain risks are hard to mitigate and can emerge in the container building cycle Or infrastructure provisioning especially in cloud environments And then we have Helga labors coming in talking about how to secure Kubernetes as it becomes Mainstream this is an actually an interview with the CEO of ARMA who talks about security and Kubernetes systems What makes them susceptible to cyber attacks and what should organizations expect when deploying them? He answers, you know attackers are looking for targets And how do they choose their targets by a combination of key parameters the value of the target and how easy it is to attack it? So after talking about this stuff Obviously, we need to have a way of knowing if our Kubernetes network security strategy is solid And then I think there are four critical questions that must be asked to understand Where these vulnerabilities persist and where steps need to be taken to ensure adequate protection within your container network? So before you decide anything ask these five questions to yourself does your network inspection achieve complete visibility? What isn't protected by your security deployment or service mesh? What are the limitations of your existing web application firewall protection? Are you addressing security drift and how fast can your Kubernetes security mitigate threats? Again very very important theme in the world of Kubernetes now I will drop in the links for for the for these specific opinion pieces and news articles that I've addressed right now and then going in What are the main drivers and challenges of container technology today? Obviously security being one of the main challenges They're related to the application container technology They limit its its adoption There's a lack of internal alignment and experience in Kubernetes management That are also named among the key barriers to adoption Main drivers are increasing number of enterprises Are opting in for the powerful deployment options invisibility over complex deployments Efficient distribution of workload across clusters resources and accelerated software delivery powered by kubernetes But despite the challenges the idea of a simplified and automated service delivery continues to drive The deployment of kubernetes across across the world Then we want to highlight the five DevSecOps DevSecOps open source projects Again, you can go in and look at this article to learn more about these projects But teams that embrace the DevSecOps approach make security an integral part of the entire application life cycle And these specific open source projects aim to help that Claire six-door cubelenter open policy agent and gatekeeper and falco So I will again drop all of these links into the chat Feel free to go and check those out come back to kubernetes KBE news page every week. We have great articles coming up today as well And giving it back to you chris and steve Thank you. Meena. Awesome. And yes, security has been a huge issue lately um Machek Machek who is your daddy and what do you do? That will depend on the context and everything around it, but I we I think we can figure it out eventually over the course of the rest of the meeting So your software engineer here at red hat Collead of two sigs sounds like you're like me. You wear mini hats at red hat and Yeah, that's true an interesting challenge um It is uh Let's start that I was a six cli lead for Almost four years now and I said was because last week I officially stepped down from the six cli chair role in six cli we have a division of What a chair does and what a tech lead does so theoretically all of us are wearing both hats But over time when we want to appreciate someone else or I will be slowly stepping down, but I want to help with the technical side of things I'm giving away the organizational hat and we'll take care of the technical stuff, especially that I have a lot of knowledge that Most importantly historical knowledge And decision that we that we did over the past years and I know that the other chairs and tech leads We're asking me to be around to help them because That historical knowledge is sometimes helpful for resolving conflicts and situations Which are basically on a daily basis so That's that Yeah, the context why we did this this way or the other way in the past Have we tried to look into this or something else? And yes, we usually have but the decision from the past was that because there are those Other stuff that might interact We have to make this hard decision of doing this or or differently So this definitely saves a lot of time when When I can look it up in my head somehow I don't know how I Managed to to to keep a hold of this many information, but somehow I do But I think it has so many people Yeah Yeah, there's a how many people are usually interacting with and that's six y'all. I kind of like uh six y'all varies But I think it'll be somewhere between 10 and 20 people that are constantly on our well currently We have this many meetings that we are meeting every Week because there's the official six y'all I meeting is every other week and that's That's in the other weeks. We are doing box crops and just recently Katrina started doing Customized box crops. So No matter what's Wednesday, there's usually a six y'all I meeting whether they'll be box crop Or customized crop or a regular meeting It's all in the calendar So, uh, you should be good Good one. On top of that you also do work in SIG apps too. So as part of your community participation Right. So I was part of the SIG apps basically since The initial days when I started working on cube uh, because my My initials to my original story with Kubernetes started with jobs. Uh, well at the time it was called Actually scheduler jobs. So that that was the idea of adding Uh, something like crons in Linux if you're familiar with Linux systems You know that there is an ability to schedule some tasks at any given point in time Initially, that was called scheduler jobs over time It was renamed to cron jobs And that was the original idea During the initial discussions we divided that into jobs and cron jobs So this is how we uh, how my story I think that was around 2016 Yeah, that's what I'd say that 2017 very early on. Yeah. Yeah, that was very early on in Barely a couple months after I joined red hat if I remember correctly But since then I was jumping the train in couple Places and if you look at my contributions and I I don't know what I was doing, but I was looking for something and I was looking for What I did what I touched. I touched very different Places in the cube ecosystem And even though I'm on a daily basis Uh, the team that I'm leading at red hat Is overlooking both 6c li sig apps and also six scheduling, but thankfully I have amazing folks working with me that are Uh Handling the six scheduling. I don't have to do it because uh, my mind would blow what I would have to look at the third sick but even still, uh, I'm also participating in sig api machinery and trying to Uh, to look into what they are, uh, cooking both from sig apps perspective because Controllers are interacting with api one way or the other A lot of primitives that makes the api machinery is working on Is being used heavily in both sig apps and 6c li So it's somehow natural to me to also follow along with those folks interesting So hello out there everybody in the audience Just wanted to make sure we get a hello then I was just gonna jump in you mentioned like you're starting the kubernetes and it sound like part of it was your Your role in in red hat. I don't know if you can talk a little bit more about how that kind of started Hmm. Well that was an interesting, uh turn of events Uh, I was basically And invited to a conference that was happening in southern poland pretty close by where I was living in a very small city Nearby and a friend of mine asked me. Oh, there's an open source days happening in bios kobyawa Uh, that was like seven years ago In march if I remember correctly and I was like, oh, yeah I I promised to go with you on a conference a couple of uh months before and but I couldn't make it Oh, yeah, I'll join Also, that was a time when um, I was a couple months after switching my previous previous job to the current one at the time and I was like very Disappointed by the pick that I did like literally after a week of working there. I was like, yeah, that's not the place that I want to be in um Well happens and um I went to the open source days and I've met uh, my wonderful friends and co-workers until today uh, jirka uh folta whose currently in charge of hr and check republic And michael foitig and michael is uh stuff engineer in open shift until this day And he was my team lead for a very very long time And I consider him and my friend. So and we started chatting and it was like Oh, it would be so cool to be able to work with you Uh, there was one little at the time Is that open shift back then I was seven years ago Was at the version two that was written in ruby And I'm being Pythonista and I was like, yeah, that's not my game um So I applied for two positions actually one was for open stack and other one was for open shift And because of being and having my heart with python I cared more about the open stack role more than the uh, the open shift It turns out that uh, I didn't get the open stack Because I was missing some proper virtual machine knowledge But I got the uh, open shift role soon after Open shift started working on v3 And we switched from ruby to go and I was like, oh, yeah, that's fine because I worked with java before I work with c So switching from uh, from ruby over to go Was pretty uh, was pretty exciting for me actually And that's how I landed over at red hat. Uh, I did touch the ruby codes for quite a while I think I was one of the last person that was Still, uh, maintaining v2. I think folks that were joining red hat, uh, after me Did not maintain the v2 already because they were already Jumping into v3 and go base solution. So I was exciting chips that you uh That have happened out worked out for you. I mean worked out for the team overall Um, so that's great to hear. Um, the one thing it I think it was an interesting story I hearing folks like you work upstream so much in the community Is it there's a lot of pieces there that are kind of hard to pull together But at the same time you're managing delivering I want to call downstream But you know a thing that's taking those bits from the upstream and then downstream China practice I'm dealing with behest releases. So you're working with many versions of cube or cube c cubes cuddle cube ctl whatever you want to call it right and And have to deal with those challenges. So I'd be kind of interested to hear your story there What that's like dealing with not only the community parts But now you're kind of in a some ways going back and porting forward like all the different challenges or or ways of working day to day Okay, so before I jump into that one, uh, let me straight up one thing about the cube cuddle cube ctl, whichever Um, I'm going to use both interchangeably Love it. Uh, although although a couple years back Uh, if you are familiar cube cuddle ahead of has a logo And we struggle with it and talking with phil and shon at the time Who we're leading sick to you like? Well are still on to today We figure out that maybe something like cuddle fish for cube cuddle which is cuddling the cube logo Uh, so if you haven't uh, check the logo if you go to kubernetes cube cuddle on github You'll see the our logo proudly presented on the front page Uh, but both names even though we went with the cuddle Both names are perfectly Okay, and I've seen lots of questions Debites And it's actually something that we we are being asked almost Every single time when we're talking about six cli during cube cons For the past three four years, I would say And now going back to your original question I must admit that the fact that cube decided to switch from four to three releases a year Was a significant improvement from my point of view because If you're thinking about just cube You're thinking about past four releases currently three releases But for me as you said that means Double the digit So it was eight releases a year or six releases currently because for me Uh, my life cycle looks like this I'm done with let's say Kubernetes 122 which was released Uh, a couple weeks back And I'm jumping immediately into Into open shift four point Where we were for point nine Which will be which is based on on Kubernetes 122 and that will be released in a short while And then immediately I need to jump on the track and start working on 123 already And we will be slowly preparing for another version of open shift. So we're constantly between Uh, feature freeze I'm literally chasing every single date, whether that's cube feature freeze Or open shift feature freeze, whether that's cube, uh, code freeze or open shift Code freeze and jumping, uh with those dates is challenging at times Um, and it sometimes is overwhelming But thankfully I have an amazing team both upstream in 6cli as well in a sig apps That does a lot of the work Uh, and can help me with pretty much delivering any And any single feature whether that's downstream or upstream So backing up a little bit further, you know, when did you get your starting like open source? Like how did you discover open source software in general? Yeah, so with open source the story goes back to python Uh, and all the way back to the my to my university years Like 20 years ago or something along those lines um I took a class on python and I was like, yeah, well Ma, I'm not sure if that's something for me A couple months went by And I had an internship and during the internship I got to work with python heavily And that's where where uh where I filed them off with python And over the years I figure out Well, uh the community Here with specifically the python, uh community was delivering was providing with this amazing tool Uh for free So I figure out that I want to give back something And my initial contributions, uh were to python itself. Uh, I think I did a couple prs Uh to python itself specifically imap and smtp libraries Over time also helped with box python orc, which is the buck tracker for python And that's uh, I think that that was the initial Story where I started with open source. I was doing As much as I could in my free time And I'm trying still to be active in the python, although Live work and everything else Uh is not always in line with uh with my willingness to work on python stuff That's interesting. You said that you get to play much with python these days or it's I mean, I wouldn't say that uh, I don't have a time I Every single time I'm working on something simple that I want to scrape data or somehow analyze the data I'm going to reach out for python every single time that I'm doing something like that Uh over the past years whenever I was preparing some kind of a demo for open shift Um Or presenting some ideas. I was always uh preparing a an application and that application always Reused python under the covers just because I wanted to give it a try In the past in the earlier days when we started shipping v3 I was also involved in uh source to image, which is the the build technology for uh for open shift And I was the primary owner for uh for the python builder I kick off that one so So I've always tried to use whatever I built and make sure that uh the experience that I'm Feeling is actually legit and whether I should improve something and make it better Or whether it the ux simply to say is Is reasonable for uh for a regular user so Source to image I think fondly called s2i. I'm dropping link to that in chat if you're not familiar with it folks Yeah, the the one thing I don't know if you want to maybe jump back into kind of the what's happening in the cli space So around kubernetes and six cli. I don't know if you want to Spend a little time about you know, I'll talk about the plugin model like exploration around crew and then kind of integration with Customize and any plugin ecosystem kind of throwing a broad statement That there are sort of like cli topics So kind of curious right, so six cli itself we have Actually three main sub projects That we are overlooking You didn't mention customize And I I also mentioned earlier Today that we are doing box crops and one box crop is actually tomorrow Uh, it's around 6 p.m. Central European time and it's around noon eastern time 9 a.m. Pacific Uh, we will be going through customize box. We have a very talented group of people who is working on customize and pushing this forward listening to what the customers and users Want to have at it? There are cases where we are trying to simplify a lot of stuff for customize because It was a problem for some time where customize moved forward And before that we decided that we want to ship kubectl with customize embedded And the fact that customize went so far in with features and Capabilities we were left in kubectl with a pretty old customize Uh, and the dependencies Unfortunately made the problem even harder for us to upgrade. So we had to Refactor a little bit of customize to To be able to update the version And jeff did an amazing job here and worked tirelessly to bring The necessary changes into customize and then update the customize in in kubectl So that's on that end of the next project crew And the entire plugin model So that was basically in line with what the majority of kubectl was doing so kubectl decided that the core would be pretty much closed And we would open up a lot of places. However, you can inject or add Additional capabilities kubectl wasn't different Um, we look at other tools namely git and other Binary's how they implement their own plugin models And we came up with the current plugin implementation that your plugin It has to just it just have to have a prefix of kubectl Uh, and that will make it a plugin to kubectl out of that Ahmed and friends figure out that it would be nice to have something to manage the plugins for for kubectl That's how the crew started its thing and it's pretty popular And we're very happy to have crew on board and lastly, which is a pretty new addition To this 6cli sub project is koi. It's a project initially started by ibm and Uh driven by nick especially, which is a Gui approach to Kind of like a wrapper to kubectl it has a much richer Uh capabilities of presenting the output of the kubectl commands Um, so it's like a combination. It's not like a web console But it's definitely a much richer kubectl wrapper than if you would use normal kubectl It has a live preview of let's say if you start watching pods And it allows a little bit more freedom around sorting and formatting the The output of the kubectl commands So there are pretty interesting stuff and lastly because You did mention the plugins during the Uh, the work that we did on plugins We extracted a library called cli runtimes and that exists on github other Kubernetes Where we are providing Outdoors of the plugins with a lot of the primitives for printing data for Reading configuration, etc. So that you don't uh, first of all you can be um Your output your way of doing stuff is similar to what kubectl does by default But it also deals a lot of for a lot of the stuff for you So you don't have to write anything from scratch when you want to I don't know parts kubectl for example Do you have a is there a place listing? Uh, kind of common or popular plugins that exist? Um I mean i'm on the pru website right now. There's 154 plugins. I'm not sure I think there was or There's not like a support function But Okay, you can you have your own number of stars. I'll drop it in the chat I guess do you have any favorite or one you use often or when you want to plug? um My favorite I would probably call out to debug uh, which was which originally started as a plugin But we're currently in a process of uh pulling debug into the as a default command in kubectl It's it's rather lengthy process. Uh, if you're a plugin, it's obviously in you can have a little bit faster iteration of your releases if you're in a Um In a core the process is you just you basically have to follow What kubectl does but on on the other hand? What is something that we're we've been working for I would probably say three years maybe even four years Is we're trying to simplify the kubectl code so that we can um Move the entire kubectl code to a separate repository even though that If you will start if you check out github Uh, you'll notice that kubernetes slash kubectl exist as a separate repository It's actually not a repository where the entire development is happening on a daily basis Uh, kubernetes has a notion of staging repose So if you look under main kubernetes kubernetes repository, there is a staging directory and if you drill down you'll notice that there is a kubectl directory That means we are publishing the contents of that Directory into a separate repo the goal for that was that We can And we ensure that the libraries that are used within the staging repo are not Using any of the dependencies from the main kubernetes kubernetes repo and that eventually we will be Uh, we'll be publishing from entirely new repo. We're currently Discussing how to uh, how to do it because it's a lot of Challenges are still ahead of us for how to release because if you look at how kube currently releases It is basically publishing all of the artifacts from a single repo I was talking with Sig release. I think that was last week or two weeks ago About us wanting to publish kubectl code Or basically kubectl artifacts from a separate repo It will take a little bit of time still But we're hoping that within a couple next releases to three maybe We will be able to uh to publish from a separate repo As soon as we reached that point where we have a separate repo um, we will return to the discussion of Maybe shipping kubectl faster Then kube then kube itself is because that was one of the goal if we move to separate repo We will try eventually cut the court For releasing. Obviously there are some challenges um Coming from that because currently we are required to support plus minus one version Which is the default policy for all of kube If we start for example Publishing kubectl every month That means we need to make sure that the support Matrix is not plus minus one, but we will be supporting about Four or five releases back and forth So there's a lot of Maybe none of the code changes required, but there's a lot of Discussion that needs to happen around processes mostly How to proceed with this approach So there's a lot of work around that But we're very hopeful with with regards to that Sounds very interesting. Um that you kind of curious In a lot of work that's going on in there So I appreciate it from you and all the your team and the community members that are doing it I'm just kind of curious as I think about Like if I was a plugin if I wanted to develop a plugin like either You know, how would I look at what's available? And I think we talked about that and talk about what do I do to get started you talked about this This stk that's available. I didn't know any other tools or recommendations you might have For them, especially in light of this Making sure it works across multiple versions of whatever's interacting with on the cube and back and Right. So we also thought about that one. Um, and there are a couple resources available Uh, first of all a shameless plug with who on We did a presentation during one of the past cube cons about how uh, what it takes to write a plugin if you Search with my name and six you lie. I'm pretty sure that you should be able to find it I think that might have been either Seattle Or um that time um Additionally within the main Kubernetes Again staging repo. We are publishing A uh a repo that has a sample cli plugin And if I remember correctly, the repo is literally called sample cli plugin Uh, similarly to how There is one for sample controller And I think maybe even uh, simple API server there is one. So if you go to github slash Kubernetes sample cli plugin, it's a very minimal plugin That allows you to switch namespaces Permanently But most importantly it shows how to write a plugin And how to reuse the libraries that we are shipping The cli runtimes. I mentioned before How to build on top of Kubernetes API Kubernetes client go to achieve the necessary Stuff to build your simple plugin Put your up in a wing to that right now and chat for you Makes sense. Um, thanks um I guess um, I was just thinking through some of the other pieces of of the cli you mentioned um Uh, customize or anything you see kind of coming down the road as other cli integrations people are then Or kind of core features that people are trying to work their way in as far as uh, or a sub project Hmm, that's an interesting question Uh, honestly, I haven't seen anything New in that territory although at the same time with This many duties that I'm dealing with and prs and approvals and whatnot Both upstream and downstream. I'm not very closely following um The area of either cli or controllers And as always takes me well, sometimes it takes me by surprise Uh, but if people are showing up, uh, either for sig apps or six you like with something new Uh, then yes, uh, I will be aware but nothing like that Uh, showed up sounds like the pretty full pretty full plate there. So yeah, the plugin model really allows for uh Allows for anything to happen at this point too. So that's yes, that's true Sounds like that's the right thing to allow there. So curious a bit more You talked a little bit about your involvement in sig apps early days as far as jobs and I know kind of recently Become the co-lead of of sig apps. So I don't know if we'd talk a little bit about what's What's going on the kind of the key things and sig apps these days Right so Yeah, a lot of the So equally as with sig 60 li where there's a lot of moving pieces Uh going on there's a lot happening in the sig apps area as well um Most importantly, we're trying to align some of the controllers By adding the capabilities that were Previously available in other controllers For example, the ability to say oh during a rollout. I want to have this many pots unavailable Which is something that we had since always in deployments Over daemon sets. We're currently adding similar capability to stateful sets so that Before stateful sets were always going one by one pod Now you will be able to pass a little bit Greater Unavailability rates. So for example, you you will be able to move faster with your With your upgrade There are other Issues that we're overlooking From sig apps point of view as well the biggest one that we're that we're looking at in the very Long term Is we're trying to unify the statuses of all the controllers If you've ever looked at the controllers You need to know how to read properly deployment status Separately stateful set status separately job or cron job or any other controller There is literally close to zero Common interface between those The reason for that is because each of those controllers were written by a completely different person So everyone had a different opinion how the status should look like The biggest downside of that is if you're building tools on top of the controllers You have to write a logic That will know oh, I'm dealing with a deployment. This is how I should interpret the status If I'm dealing with a stateful set Well the logic has to be Different So we're trying to figure out a way how to combine the current statuses in all the controllers and make them Somehow unified so that you will be able to just write one uh One implementation and that will have the necessary information whether Your workload is just starting or it's progressing whether it it is done or it's like running And that will depend there are various different cases Because If you think about it Most of the workloads controller so stateful set deployments Damon sets Their end state is that they are running But if you look at for example the batch workloads where you just run a task And the task has an end Their state will be a completed So we need to figure out those common statuses somehow And present them in a unified way to users. So we're slowly working on Um on enhancement for Kubernetes where we will try to combine those statuses And then eventually slowly over time. We will be implementing I'm positive that during the implementation phase even though We're already spent a couple of weeks or even months Looking at the statuses And trying to figure out with something reasonable I'm positive that as soon as we start implementing those Uh additional edge cases will pop up And we will have to modify the initial uh Requirements that we put Ourselves That sounds like a pretty uh pretty decent task and I've run into this multiple times We're trying to build experiences around extensions and trying to get the the status of what's going on And it's Bit challenging to write that kind of common tool to to roll that up One thing is kind of curious like we're what is sig apps is you can say apps You can put anything under apps in a sense. So how do you define the scope Of what really goes into sig apps or how is it defined as far as the everything that's is it I know you mentioned workloads kind of aspects of of kubernetes But I don't know if you talk a little bit about what all what all happens there When's the decision of keep punting it to other sigs Well, that's that's a very good question. So I'll probably refer to the sig apps charter So basically every special interest group within kubernetes Has a its own charter as As as it sends it basically lists Who is the chair? What are the sub projects and what basically we do and what are our responsibilities? So if you look at the sig apps charter, uh, we are Saying that everything From controllers all the way up to that is running on top of the platform is considered as part part of the sig apps so There are multiple topics that went through sig apps controllers are obviously the most Primary one I would call it that way So whenever you want to discuss any changes Whether to api or functionality to one of the core controllers The sig apps will be the place although Some of the controllers are primarily owned by a different sig So for example endpoints or services those will be owned by the Uh by the networking sig Sig apps will be mostly controller so All the stateful sets uh daemon sets replica sets replication controllers all of that And then everything on top of that is running There's there was a lot of work around and we still have a sub project called an application Which is actually in a grouping primitive for a set of workloads together Just recently we had a very interesting presentation About operator for higher level Uh like over operator That is overlooking the penises between deployments That was Last monday if I remember correctly the recording is up And that was pretty interesting and I remember that the person that was explaining the The project they mentioned that they are working on Open sourcing the solution currently So there's a hope that there will be more uh stuff like that available If you look in the past um a helm was For a very long time one of the primary topics During sig apps calls And probably a couple other topics And um it was sometimes hard Or overwhelming but I think at this point in time Um the majority of the sig apps calls are devoted to the controllers If there are no topics we started doing box crops and pr crops and go through issues because there's uh, there's quite a big backlog Of the issues that we have against the controllers and we're slowly going through Through those and we're trying to make sure that the people People's voices get heard Yeah, that was got involved in uh sig apps a long time ago And we jokingly refer to it early days as sig helmet. Um because of what's dominated as helmet is a topic One of the things I was going to say is like if you look at the um the GitHub page talk about uh sig apps It's one of the things I think is great about it is the non-goals kind of part of what it describes it doesn't Endors one particular ecosystem tool does not pick which apps run on top of kubernetes Does not recommend one way to do things or I think so. I think that's really helps clarify what the group is there to do so, uh, even to the point of um the app definition I know there's the the label recommendations that that the sig apps actually Um overseas as well so Overall kind of kudos to a complicated topic I think the that sig has worked pretty well to handle over the years as far as scope of applications Yeah exactly so You know, we only have Wapping 15 minutes left and obviously we don't have to take the whole hour if we don't fill it, but What do you think are some of? unique challenges of kubernetes today and You know people starting out the things the sharp edges. They might catch themselves on potentially, right? Like if they're getting going with kubernetes Hmm That's that's that's a very interesting question uh For me personally I think the biggest issue is the volume of the changes And something that I'm personally struggling is how to keep up with all of the changes All of the requests for reviews um I know that There there are multiple issues and pull requests with my name on it And whenever I'm talking with people during kube cons or during uh, sig meetings I'm always asking them to reach out to me on slack Because my github notifications and my email are way off charts Yeah, and um I'm always promising myself to keep up with those and It happens a couple every I don't know every couple of months. I'm gonna okay. I'm gonna clean my inbox uh I'm gonna go to all the way to zero And and then only two three days later or I don't know something happens Uh that there will be other topics that I need to deal with Uh for two three days, I'm gonna neglect those Those emails and they will pile up very quickly and then It just goes by For the next couple of weeks and then I have to go back to the initial. Oh, I need to go through I don't know a couple hundred emails and figure out which I care about and which don't Um, so that's unfortunately Uh a big problem for me personally That's why I'm always always asking if you care about your pr Please reach out to me directly on slack. I don't mind if you haven't heard from me Because you ping me once or twice and if you haven't heard from me Ping me again in a week. I will respond Uh, I've had a number of uh, many people are pinging me Uh, literally every week for Extended period of time like really extended period of time And eventually I got it through every time I apologize for uh for neglecting that But I always try to If I don't respond within a week, feel free to ping me. I don't mind honestly, I don't mind because There's life. There's so many things going on in parallel That I it just might slip my attention or Plenty forget about stuff So I don't mind being pinged again and again About prs or reviews That that's how it that's how it works. Yeah, if you don't I couldn't imagine Yeah Could imagine your inbox and the backlog. Yeah, there it is I I used to use someone travel dead time to like kind of catch up on those things and don't have that anymore so But also don't have travel dead time. So anyways, um The the thing that I was thinking of sort of much is like kind of that involvement of the community and how you adjust Because I think back like I remember in uh In the 2019 in san diego at kubecon and we're you know, we're I think three of us are probably the same height Like we're pretty tall and we're like talking, you know People walking by and just hanging out there between the exhibit hall Let's just such a great way to connect with people and with kubecon coming up in north america again I was kind of curious how you have you adjusted to engaging with the kube community and the more of a virtual presence or so Since day one, I'm every mode at red hat But as we were talking with chris I do enjoy Meeting people in person In the early days, I have a pretty big red house office in check republic Which is two two and a half hour drive from where I live.  I do miss, uh, kubecon I'll be missing it even more in Two weeks if I remember correctly at the beginning of october. I can't Join folks in in la, but I would love to be Around because it is just nicer to talk with people. I think Most of the communication most of discussion can happen. It's that that's not a problem Either through a slack or zoom that works But the bonding part, you know having a Beverage of your choice with the person and just chatting about silly stuff. I don't know. Disney world trip Yeah, uh visiting parents about kids about Uh life in general Poor transportation in Detroit exactly. I mean literally anything and most often that's not even work or project related That would make a huge difference and even though kubecon Did a pretty well job with, uh virtualizing those events It's not the same. I do miss the interaction where I can see Stand in front of the people and talk with them ask the questions. We literally did Instead of doing any kind of presentation for 60 light back in san diego two years ago What we did with phil and shan we stood there and we answered questions about 60 light everything For uh for 90 minutes. You can't do something like that with the current Pre-recorded sessions for kubecons. It is not that easy and even though There are slacks. Uh, there are some virtual chats. It just doesn't work that way Uh, the ability that I can come to person ask the question poke them And or have most importantly the hallway conversation That's invaluable. So I I do miss that part and even though I I usually attended kubecon both in In north america and then in europe that was enough for me for a year I did those two conference then dafcon as well In bruno and I was done for a year three times. I did more once or twice Well, I was like, yeah, that's way too much for me. I'm I'm okay with doing A conference per quarter. That's enough for for my introvert Character So, yeah, it's a good point. I'm flying out next saturday to kubecon And yeah, like I remember being in san diego and like at the conservator summit and like There was all kinds of technical issues and then like, you know It's much easier to say.  You need to know now you're a good contributor and like Having that face-to-face discussion where there's you know body language and everything else. It's a lot easier to interpret Exactly the work that's happening, right? Like that's it's It is very different, right and even like life dream like we are right now It's not quite the same as sitting down at a table with our computers and talking about a problem, right? Like it's very much a Hey, we're going to talk. We're going to work. We'll talk some more. We'll work some more, right? Like it's not the same flow, right? Yeah, exactly Yeah, I even have to confess though. Even at san diego when I was there Like I'm not a not a crowd person either like, you know a bit of an introvert So like the keynote sessions. I don't go wake in line. Whatever. I stream them from my room So there I am in san diego Sitting looking around at poles Away So Finally being an introvert I actually sat during all of the keynote sessions and actually I if I remember correctly The keynote sessions were the only ones that I actually attended because the the remaining ones I usually end up talking with folks in the corridors or in the both halls or you know basically wandering around and eventually Just popping in for for my session or one or two either Sessions so the key notes were like the ones that you can actually find me on And then the ones that where I'm presenting others. Well, I usually try to set up my schedule somehow Oh, yes, these are the stuff that I want to see I probably don't see I don't know like 20 30 of what I check like yeah, I want to check this one out.  Exactly exactly That someone just mentioned in chat Rapscallion Reeves at least most people at those conferences tend to be introverts too. So you're kind of amongst your own people um And then yeah Tanawa three points out acoustics for the uh exhibition hall in san diego was awful If anybody remembers that it was just constantly loud In this big domed space with music playing in the background 20 000 of our favorite friends or whatever Can't remember the attendance numbers, but it was just loud I mean, I remember the I remember when we were in london. I think that was the first kubecon um in europe and there was like 100 and something people we We barely had like two or three rooms Just a little bit of people Berlin was pretty much similar and then it just grew exponentially over the years. That was crazy Yeah And this kubecon I feel like is gonna be a little bit like that where it's like A little smaller more, you know quaint environment compared to the the tens of thousands we're used to Yeah, but the the downside of that one is that we will be missing a lot of the contributors to the core Because of different reasons. They're not traveling to us or they are not even traveling within the us I spoke with many people and It's not as easy or they are just not willing to To do so at this point in time. So Yeah, no, I was just talking to a friend on twitter a few minutes before the show started before we got on air and it was like Yeah, no, they can't come because they're in the uk or you know, berlin or whatever and Yeah, the the lack of international folks is going to be very obvious, right? Like it'll feel very You know us based right like as opposed to international conference where people kind of gather But With two minutes left, there's no questions in chat for oh, there is one question in chat. I don't want to ask. Sorry What's the best way for random people slash developers to help out with kube projects? I have my opinion, but I like to hear yours or steves for that matter Honestly, I always say that it's easiest to Show up during one of the calls. Yep, whether that'll be 60 lie or say gaps Especially the ones that are going through box crops. So for example, we will be going through customized box crop tomorrow or there's a 60 lie box crop in two weeks from from tomorrow Those are the places where we literally asked is anyone interested in working on this one Anyone? It's a good place for For asking questions if you're new Even during the sig apps or 60 lie calls We try to give a little bit of space at the beginning for everyone to introduce themselves with they are what they want to Work on so it's perfectly fine to also show up for any of those calls and And explain. Oh, this is the issue that I noticed. I want to work on it Can you help me and just ask questions? There's no dumb questions about any of those topics. So it's the right place to ask that That's that's usually my my simple answer Yeah, and that's my answer too to be honest with you steve. I'm curious if you have a different opinion Yeah, I mean I think also the contributions are very valuable across the board. So talking about like Getting started early and looking at some of the setup instructions might be wrong helping fix those up opening bugs for You know issues you see for different things that seem a little off So all of those things are a good way to get started and like I think one time I started was I was even a go Coder and I fixed one of the The cli issues just because the new lines were screwed up So I knew how to insert new line and compile the code and contribute that back So it was like I could even just fix it was like easy enough said describing the problem It's like here you go, you know, so I think the little things like that are a good way It just depends on your context and background so Yeah, I mean I started off in sick docs very early on and then made my way over to Contrabex and that's kind of where I live now. That's fine with me That that'll work for anybody else. I feel like too Yeah, there are multiple options. So just Pick one Yeah, and if you really you know want to talk about it feel free to ping me on the kubernetes slack folks for short Wide open there. I'm sure machek and steve Are welcome to answer your questions exactly And Yeah, so thank you machek. Thank you steve for guest hosting. Thank you audience for attending Really appreciate everybody here on this call blighting out there. Thank you very much It's good to talk. Yeah Coming up later today. We have the call for code for rachel justice. We'll be talking about take two It's a project that will help folks Analyze data about the justice system in a way that will Make people rethink about sentencing and things like that. So should be an interesting call and lots of fun stuff for the ibm team On the call for code side. So yeah, good stuff. So thank you everyone for joining and have a great day and stay safe out there


We are now in the final four hours of the countdown for the launch of Space Shuttle Discovery on the STS-70 mission with launch occurring from Pad B at Launch Complex 39. Here we see a replay of the astronaut crew breakfast this morning, which occurred about 5.15. Mission Specialist Mary Ellen Weber, who will be working with the deployment of the tracking and data relay satellite. And our Flight Engineer, Mission Specialist Nancy Curry, our Commander for STS-70, Tom Henricks, and next to him is Pilot Kevin Kriegel. And Mission Specialist Dr. Don Thomas, who together with Dr. Mary Ellen Weber will be working later today, about six hours after launch to deploy the TDRSG tracking and data relay satellite. And our STS-70 cake with the emblem there on the table. Meanwhile, out at Launch Pad 39B, the final inspection team has been going through their routine inspections, looking for any buildup of ice on the external tank or any of the flight surfaces that could break off and strike Space Shuttle Discovery during launch. The ice team has a number of tools, which includes a portable infrared scanner to obtain temperature measurements on the surface of the vehicle, and it can spot any leaks in the external tank or the umbilicals. And the team also takes this as a last opportunity to look at the pad to assure that there's no loose debris around, which could also strike the orbiter at launch. There we see our Commander, Tom Henricks, ready to go, suited up with his helmet, and Pilot Kevin Kriegel. He's also ready to go. He's completed a fit check of the helmets. Kevin's first flight, and we'll be hearing from him later on on what he's anticipating for his first mission. And Mission Specialist Dr. Don Thomas, who will be busy later this afternoon, working with the deployment of the tracking and data ray satellite, which is the main order of business for today. There is Dr. Mary Ellen Weber, working with Dr. Thomas later this afternoon on the deployment of the IUS TDRS and our Flight Engineer, Mission Specialist Nancy Curry. She'll be seated in the aft center seat during launch and re-entry, and the suit up activities are about completed so that the crew will be headed out for the pad here in about another 15 minutes. Now we can see the crew somewhat better, Pilot Kevin Kriegel without his helmet. This is shuttle launch control at T-minus three hours and holding. We're preparing now to come out of the built-in hold in three, two, one, and the clock is now at T-minus three hours and counting. All of our activities continue to be on schedule this morning. We're not working any technical problems, and the weather appears favorable. And as we mentioned just a few moments ago, the astronauts are just about to leave for the launch pad and we'll begin boarding discovery on time. Now at T-minus two hours, 59 minutes, 35 seconds and counting. This is shuttle launch control. This is shuttle launch control at T-minus two hours, 56 minutes, two seconds and counting. And we see the astronauts have just left the suit up room. It's our Pilot Kevin Kriegel with the good luck sign and being wished well by some of the astronaut support personnel. Our activities right now are proceeding right to the minute. There's our pilot or our Commander Tom Hendricks, Pilot Kevin Kriegel, Mission Specialist Don Thomas. The missions are being advised now that the astronauts are leaving the crew quarters and to expect them shortly. And here we see the astronauts now arriving at the 190-foot, 5-foot level of the fixed service structure at Pad B, walking over to the orbiter access arm. And some of them will wait out on the orbiter access arm while other crew members are being assisted with their helmets and other attire so that it doesn't get too crowded, the white room is not very large. And of course Tom Hendricks will be the first one aboard. This is shuttle launch control at T-minus two hours, 27 minutes, 27 seconds and counting. As we see Commander Tom Hendricks boarding space shuttle discovery. This is his third flight into space, his first as commander. And we see Dr. Mary Ellen Weber and like Kevin Kriegel she's also making her first flight today. Pilot Kevin Kriegel now preparing to board discovery. This is his first flight. Good morning Tom and loud and clear. And we're seeing now Mission Specialist Don Thomas preparing for boarding. Just in front here we see Mission Specialist Nancy Curry being assisted with her flight crew equipment and she was raised in Troy, Ohio. Discovery Houston, Don we have you loud and clear, how me? Good morning Curt, have you loud and clear also? You're the same and welcome aboard. So out we're ready to go here. NASA crew is ready for copy that. And in the meantime if you could perform your close out for flight per your checklist please. Do you have the copies? Discovery is ready for air-to-air altitude voice check. Discovery Houston for the CDR and POT, voice check on air to ground two how do you read? Loud and clear. CLT, loud and clear. Discovery Houston read you both loud and clear configured for air-to-air voice check. We get a CQC on 143 for Catalina. Go ahead OVCC. You broke up OVCC repeat. Hatch is going shut. Copy that. And the hatch is being closed and sealed exactly on time. And here is Bob Cabana returning in the shuttle training aircraft. He has been doing approaches to runway 15 at the shuttle landing facility assessing those conditions and will be going up for another pass. Runway 15 has been designated as the runway we would use in the event of an emergency today. Which is basically a northwest to southeast approach. CLT, OTC, configure fuel cell, essential bus stop switches. Essential buses are connected. Let's go for OAA repack. And the orbiter access arm can be moved back into position around the hatch in about 30 seconds should an emergency occur. T-minus 7 minutes in counting. Next milestone is the start of the auxiliary power units by pilot Kevin Griegel. He'll flip three switches on the cockpit to start each of the three APUs and then port that's complete. JRPSOTC, captain, start APU on Hydraulics, drip trot recorder. And that's a good... OOTC perform APU pre-start. APU pre-start's in work. The flight controls through their test pattern. Three main engines now being gibbled. All of these steering checks to assure that we have proper control during ascent. Now to retract the Gox beanie cap. CLT, OTC, clear caution and warning memory. Verify no one expected errors. That's in work. T-minus 2 minutes 30 seconds. Cursion, warning memory is clear. No one expected errors. Copy. The gaseous oxygen fin hood which vents... Close and lock your visors and initiate O2 slow. And on behalf of everyone in the control room have a great mission. So looking forward to it. Thanks for your help. And the vent arm retraction underway on schedule. CLS is go for ET LH2 pressure 6. T-minus 90 seconds. Sound suppression water system now being armed. Quantity of 300,000 gallons of water in the water tank at the pad which will flow at a rate of 900,000 gallons. A minute starting at T-minus 16 seconds. T-minus 1 minute now. Being by for the handoff to discoveries on board flight computers at T-minus 31 seconds. NTG, CBRS. Go ahead, B.R. Call a hold. We do have a hold. We'd like permission to run a multi-path test contingency. That's the entity. Understood. Let's go ahead and do it. CBRS, you have a go. Take care of the results. 15 seconds. Cab A1. Okay, the results of the contingency. I copy. FCE. FCE, understand. We're ready to go. I copy. Launch director entity. There you go. Thank you. All personnel. At that clock we'll begin momentarily. This is BLS. We have a go to resume. BLS, go ahead and pick up the count. I'll zoom on my mark. Two. One. Marks. BLS, go for auto sequence start. And we've had the handoff to discoveries on board computers. 20. Sound suppression water system activated. 13 seconds. 10, 9, 8, 7, 6, 5. Main engine ignition, 4, 3, 2, 1. And liftoff of space shuttle discovery to complete NASA's constellation of tracking stations in the sky. Houston now controlling the flight of discovery. Roger roll discovery. Discovery completes the roll to place the shuttle in a heads down wings level position for the 8 and a half minute ride to orbit. 27 seconds into the flight. Discovery's three liquid fuel main engines now throttling back in a three step fashion to 67% of rated performance to lessen the stress on the shuttle's zero surfaces as it passes through the sound barrier. 50 seconds into the flight the main engines now beginning to rev up once again to 104% of rated performance including the new block one engine. All three main engines performing normally as are the three power producing fuel cells and Discovery's three hydraulic power units. Discovery Houston, go ahead throttle up.  Discovery now 63,000 feet in altitude, 8 miles down range. All systems continue to function normally in the early stage of the fourth shuttle flight of the year. 20 seconds left in first stage performance of the solid rocket boosters. Discovery approaching the 155,000 foot mark in altitude some 26 miles down range. Booster officer confirms solid rocket booster separation. Discovery Houston, performance nominal. Copy nominal performance. Discovery we have a good picture. Discovery Houston the folks at Sunnyvale would like to know where that ice came from. Did you see where it departed from? It's difficult for us to tell where it originated from. The first time we saw it was just after the IE West cleared the bay and it could have come from around the back of the ASC. Understand that sounds likely. The circumference appeared to be very similar to the IUS circumference. Oh I see, yeah the shape of the curve. Now we were about 90 seconds from the TDRS handover we may lose the picture here shortly. Okay it looks like the show's about over anyway. We'd love more. Well we'll keep it coming throughout the following week. Commander Seed up front watching the Orbiter Systems, Tom's in the back and ready to do the step maneuver. He is running the cameras and Don is over on the left hand side controlling the IUS controls and Mary Ellen is over on the right hand side monitoring the IUS systems. And you could tell today that was a very well trained team that we're seeing. This is a real team effort up here. Everybody was busy operating cameras, flying the orbiter and deploying the satellite up here. This is a team effort in our part and also a big effort on the ground. We had people at White Sand, Sunnyvale, all around the world helping to support the satellite deploy and we really appreciate the great help and support that made it possible today. That's a gorgeous picture discovery and all of you working together put another big building block in the space infrastructure. You can see it's on its way, it's just leaving the support equipment here. And on its way out to Geosynchronous orbit where we'll be supporting future missions, space station freedom and the Hubble Space Telescope to name just a few applications. That's a beautiful deploy discovery. We didn't see any rates on the satellite at all. Copy discovery. It's interesting, six years ago the IUS put Galileo on the way to Jupiter and they just released their probe towards that planet last night. And discovery, we see that very clearly. Thanks. What is there?  It went by the window previous to this view and we verified it was ice and it did break in a couple of pieces. Okay, thanks discovery. I'm sure we would have asked you about that and thanks for allaying that concern.


Well, hello everyone and welcome to the 5 p.m. 5 30 session of the 2020 open simulator community conference in this session We are happy to introduce a presentation called SOS extended environment supports for expansion and educators, please Our speaker is dr. Eileen O'Connor She is my mentor in VR I am happy to say and she is the director of the SUNY master of arts in learning through emerging technologies program Please check out the website found at conference open simulator org for speaker bios details the session and full schedules of events This session is being live streamed and recorded So if you have questions or comments during the session, you may send tweets to at open sim cc with the hashtag Hashtag OS cc 20 welcome everyone and let's begin the session Hi everybody. I'm Eileen O'Connor and And the brilliant gentleman who just spoke previously is one of the ones who has graduated from the mallet program at SUNY Empire State College And really reflects well on the wonderful students we've had and keep in mind our students are not Typical, you know, going to college or going to graduate school as you know mom and dad wanting them to these are adults Who have made strong commitments with their lives and what I'm going to be doing is showing The kind of progress we've had as a program at SUNY with virtual reality and then show some of the challenges we want to grow And what Scott just talked about was a conference that we've done locally residency, but we want to be able to do more But um Empire State College started into virtual reality Way back in about 2005 I got involved in 2006 And Scott said I'm the stem person. I love this stuff My background had been I had been a chemist Then I worked for IBM for 10 years and then it took a buyout and went back to school to combine both science and technology And went on from phd So I bring that to the background. I love all things technical I particularly enjoy the communication aspects, but I am not at all artistic So what I need to do is work with teams And so when we first started Empire State College had funding for Second Life We enjoyed it um My work itself I was adventuresome, but at one point The work I had done was so fundamental that they literally moved me into the sky And had other people develop a nice looking island and Eileen had the sky island Anyway, what happened was you know funding didn't remain And then when we did try to have our students work with Second Life It was very limited. So what we eventually did was found something called open sim And kitely we started worth early on you could get islands for very reasonable prices And the students not just the instructors could develop So what we've done since about 2012 and the masters program began shortly before that We've had meetings there. We've had classes there And scott just talked about the virtual residency, which we've been doing now for three years It's been very successful and we keep on getting better at it So not only that we've really benefited from what many artists have made available to us And use those as jumping off points Quite a number of students of our of almost half of our graduates have made their own islands and moved out on their own But we still have a lot of challenges, which are kind of endemic in the business So that's what I want to let me go to my next slide Review here as we're looking at Looking at how do we continue to expand? And scott mentioned too that the residency Was supported not only by our efforts within SUNY, but we've had an institute for new paradigms Which started several years back and we've brought in wonderful people who've continued to help us grow Bethany who will be speaking soon has been a real Supporter of our efforts. So we're seeing that partnerships can work What I'm interested in doing now though, you know, I've We've been very fortunate with kitely. They've done a wonderful job and what I always though Being a bit of a nervous Nellie and wanting to be able to have more control want to understand How we can get to some of the next steps So what I'm going to be doing now is simply just showing you Something that I started as a mind map To look at where are those next steps? We have this institute looking at pieces of this We've had some groundwork and what we need to do now is how to start networking in others and I was able to go to one of the meetings of the developers At during a break and realize they're doing and looking at a lot of the same things that we're trying to start on a mini level So we're looking at ways to partner Ways to find resources Ways to go get well beyond excuse me, which what any of us know individually. So I went from the mind map. I was really actively working on this So I'm you're going to see most of my mind map. It's not aesthetically beautiful Again, I'm the stem person, but what I'm trying to do is create a hub This time I just am starting with Google docs and you know is warned again because be careful of permissions, but I'm going to try to ask those of you Who can start giving information? Relative to any of these pieces that I'm going to show If you might please jump in jump into google docs put it in the chat I'll try to catch the chat But start helping us populate these so this is more my request for things. I don't know how to do and could use help so, um, yeah Yeah, none of us can do it all and certainly I can't now This I'm not excited. I by the way, you will have all of these I do have the slides and I do have the google doc that came from this, but um Okay, I'll put the google doc in here now. I was warned I'm going to have to ask you to be to be good and You know, if you wouldn't mind the google doc The google doc took What this mind map has I was using mind maesters very nice You can populate the subsections and then I pushed that out as a word document brought it up into Google and went from there and you'll see I'd love to have a wiki someday But I've been wondering what are the best types of wiki. So I'm going to put this out here And let's see Okay there If you feel inspired As you go through to populate any one of these sections and I'd ask if you put your name on it You know, it's a google doc if I I work a lot with students and I really encourage people To be creative at this point. This is just a set of groundwork. See if there are others who might want to Come in and You know help me down the road. So just put your name and I won't be able to get to it right away because I have three days of conferences that I have to hold at the school So what I'm doing now is taking some of those sections that you saw Yeah, and Please put any recommendations. You'll see at the end. I'm going to really ask for Good platforms, but I thought Google docs I could get my head around so what I'm trying to think of is what is this hub? and We need to have shareable information But it also has to be understandable And now I'm thinking I'm I'm willing to mucky around with technology, but I'm not an expert in it You know, I listen I learn about things But I will I'm not an IT person I would love IT people to be willing to work with us. So you're going to see here I'm going to be asking For people to think I'm looking at both an organizational level and kind of a functional level areas that I know we need Just because I've been doing this now for 15 years and I know what students need My population is adults Are the students but they in turn work with their own students So the real audience are the students that my students work with Which couldn't be anything from high school teachers Elementary school teachers corporate trainers. So I'm looking to create resources that can be used on many different levels The first though most consistent thing I have When people land they do not like the avatars They don't like the fact that the closing are are skin tight I try to go on and explain why they kind of have to be that way because of the way the The models work and that if they really want this flowing clothing It's going to take a lot more money and expertise than I have but I've been asking for artists to please sell us stuff that we can then You know modify what we I don't have a lot of money I work for state university and honestly, I pretty much fund myself on this So what I'm looking for are ways, you know to get leverage get more More and more appropriate avatars one of the first things I always hear is You know, these are over sexualized. They're you know, all sorts of problems And so I sure you hear that but consider that very often. I'm really trying to expand over to k12 There's a big need right now and that's the first problem They all have so I have a whole section if you can fill it in if you know artists who are willing to You know for reasonable prices, maybe develop clothes all of those things. So I this is just kind of my plea of things that I need and again, I just took screen captures of the different parts of the Mind map that I had so again, it's not aesthetically pleasing, but I had to actively work on this till the last minute Uh the it systems Now I work for the state university of new york, which is big and you think that they would be real helpful Well, they just always aren't as helpful as I would like So I have to be my own it right now. So I'm looking for More information there K. McClellan was very good a couple of years back explaining what her it department did I wish I could say I have that now I do work for the third fourth largest city, which is the state university in new york It's a large school But we're spread over the state as god said and so consequently there isn't just a computer department I can go and buddy up with so I'm looking for lots of things there. This is all the stuff that you guys know the The privacy issues security Downloading opening ports, you know, I would love to someday have my own server Ideally run by the school, but there's a lot of different things. I want hopefully I made that document open permissions um So we'll see if people aren't respectful, but I think you know You're a bunch of adults and I I can move comments out if they're inappropriate so it department the it department and avatars are things I can't do on my own So but what I want to do is also is I think we all keep on talking about it And we mean it on different levels, but we're pulled in many directions Join up with others But joining what they're doing and also sharing Well, I have another one for sharing the tutorials, but shared projects grants Even things like how do we acquire the institutional support? And again, my mind map had some arrows connecting things. So that's why you see arrows just showing up They're not really meaningful in this context We do have Events we have our institute of new paradigms Which we started about three years ago, which really is a mini think tank And we've had a lot of projects created by students And over the years we've had really wonderful projects. Scott has done one of them And uh, he has a whole island dedicated to art history So we we have a base But we need more now. This is really a big to do to do list that I would like to have The way the courses run that I have I get them to kindergarten opens them They're they're at kindergarten, uh, but there are many more things that I'm not qualified to teach them, but Students like scott go on and take a second class where they do a lot of their own work And you know, but I want to make that more official There's a whole lot of things that I don't know And I know there are community groups doing a lot of this And so if you can help me by populating where, you know, these community groups are Where you might know there are free things. I love what out worlds has We we find scripts and all that but if you could help by putting in resources, you know places, you know, that would be great um So, you know, those are the areas that I can't really do on my own but What I was thinking about and I always had a little meeting where people were talking about this Okay, as you get this together right now, I had to go down and dirty with what I could do Which is kind of always my approach. I I start with proof of concept. I I have to work too independently So I have to go with what I can do and so google docs is about what I can handle I know there are a lot of other wikis That are available But I went with a rather simple interface But what I'm seeing and I think this is kind of where I end I'm going to show you there are a lot more interfaces coming out for wikis and for community groups and I think Bethany is going to be showing you some of these groups. There's alt space vr There's mozilla hubs and I think I have some pictures of other interfaces that might be a little more modern looking That I was hearing from another meeting here how people are looking to find ways That the interface looks more up to date than some of the big wikis that we have historically And I I'm looking for things that could be on a couple of levels Documentation is going to be very important. There can be the academic quality But there can also be the user quality and so What I'm going to do is I'm almost through here What and I'm looking at the time If people can jump in again Eventually I would like to have a coding system. So right now I'm starting out Just with the basics But down the road we'll find out who might want to contribute something on the user level kind of tutorial level But maybe somebody sees an academic level that they could be able to work with so again There are resources and there are other models not only are mozilla hubs and all space enviable because they have Web-based interface which also means they have very simplistic avatars at this point, but there's a feature I would love to see Mozilla hubs has something that you can send out an invite very easily and you can use Twitter and other things as well. So I when I'm putting together my wish list I wish I could have some of these things Some of this is an example of some of the documentation. So as We get the different sections together I think we should look also at how other people are presenting this and see if we can learn from what they're doing And I interestingly heard that same discussion Just earlier. So What I'm going to wrap this up with is Again, I think this should come back These were just at the end. I took some examples From other places just to show What their interface looks like and I think I'm actually at the end of my slides I'm going to go right back to the beginning for a minute to see if I can get to My phone my access and my wet and the emails so What I'm doing is trying to lay out the groundwork of all You saw my wish list The things that I wish could get together Get different people together to work with this Kitely has been wonderful and But at the same point you can't be so dependent on one vendor Particularly in the world today. So I think What I want to do is broaden out and and get the partnerships get better avatars Understand better the it pieces and if any of you could help even just by putting in Links or information that you know at this point. I would greatly appreciate that And you don't have to commit for more But if you want to join in later as I get a chance to assimilate this I would appreciate it and so I think I'm just about at my time limit here and so Thank you very much and I will see if I can push out that URL again Yeah, that should get you to the google doc And if you can't get to it this evening, you know, I'll try to Make it available in the future But thank you for giving me the opportunity to get my plea forward. I love this stuff Learned a lot more and I'm a hundred percent. I am the choir So thank you for being part of the choir with me And thank you Eileen for a terrific presentation Give her a big round of applause Now as a reminder to our audience, you can see what's coming up on the conference schedule at conference.opensimulator.org Following this session the next session will begin at 5 30 in this keynote region here And is entitled using browser based virtual environments as a gateway drug to get people hooked on virtual worlds Also, we encourage you to visit the oscc 20 poster expo in the oscc expo 3 region And find accompanying information on presentations and explore the hyper grid tour resources in oscc expo 2 region Along with sponsor and crowd funder booths located throughout all of the oscc expo regions Thank you again to our speaker eileen and to you the audience