OpenStack Summit 2016, brought to you by the OpenStack Foundation and headline sponsors, Red Hat and Cisco. Now here are your hosts, Stu Miniman and Brian Graceley. Welcome back to OpenStack Summit 2016, here in Austin, Texas. This is theCUBE, happy to have back on the program. Chris Wright, who is the VP and Chief Technologist with the Red Hat. Chris, thanks so much for coming on the program again. Yeah, you're back, glad to be here. All right, so day one here at the show, big keynote, 7,500 people here, lot of excitement, talking about the maturity of what's going on, talking about, you know, more production environments, talking about some, you know, solidification of some of the key use cases. So what are some of your, you know, main takeaways from the keynote this morning? Well, just that, I mean, we're really seeing OpenStack move into the next wave of maturity and that's what's so exciting. We're seeing it go from, you know, I kind of call it early stage, almost technology experiment to the POCs and into real production, where we're seeing companies, like today we announced customers Verizon and NASA bringing OpenStack to production, solving real business problems. So it's not just about technology, it's about actually, you know, what are we doing to harness that technology and change how these companies are running their businesses? A lot of things come in full circle here. The first OpenStack summit was here in Austin. And you talk about NASA, I mean, originally it was like, you know, it was Rackspace and NASA, those were the ones. Talk a bit about, you know, how Red Hat's fitting here.  Of course, we're happy to have a lot of Red Hat people on our program here. So, you know, how's that matured from Red Hat standpoint? Well, I mean, we've grown ourselves. So we've gone from just putting our toe in the water initially to being a significant part of the community. And from a product point of view, we have hundreds of customers. So we've gone from, it really is just a technology experiment to a real production product. And so what we're trying to do is help mature OpenStack, not just in terms of bringing it to production, but in terms of bringing it to production across a wide set of use cases. I really believe that for OpenStack's long-term success, we need to see the community bringing, you know, collaborating to allow a lot of different use cases, some of which five years ago, when we got involved initially, weren't use cases we were thinking about at all? We're thinking about private cloud or large-scale public cloud with a really specific meaning. Today, we're talking about use cases spreading across different industry verticals. Interesting one would be NFV. So yeah, it's interesting, Chris. I mean, from the early days, I've always thought of, you know, Red Hat community always went well together. What I've seen over the last couple of years that has even matured more, talk about some of the partnerships. So, you know, we just had somebody on from Microsoft from talking about Red Hat, you know, sitting in a juror. You know, talking about the announcements on NFV, you had some partners involved in this. Can you speak a little bit to how, you know, where Red Hat sits and, you know, where they need to reach out to some of the partners in the community to help put the solutions together? Yeah, well, Red Hat's always had a kind of a partner-centric, broad ecosystem view of the world. Because in order for us to be successful, we can build the core platform and our key technologies, but we're never gonna be able to satisfy all the use cases without working together with partners who have different areas of expertise. OpenStack's no different. And in the OpenStack context, you know, we're partnering with, if you look at OpenStack as a set of components, some of those components themselves are pluggable. So we have partners that, like in the networking case, Neutron, we have quite a few partners that help us build out the software-defined networking story for OpenStack, similar for storage. And it's, for the whole industry, for this project to be successful, it has to have a broad reach and a big ecosystem. And for us, that's partner-centric. Yeah, it's interesting, you know, we were talking to some people just prior to this and kind of giving them a lay on the land to new people to the community. And they said, you know, I'm trying to understand all of, there's lots of different companies here. And we said, you know, four or five years ago, there's a lot of companies saying, hey, we want to be the Red Hat of OpenStack. It's sort of come around that the Red Hat of OpenStack is Red Hat.  There's OpenShift. There's now a lot of different ways to consume it.  It's huge. I mean, it's a big part of the value that we bring to the customers. It's not just, you know, we're not focused on one layer of the stack. We bring in not just products, but a real depth of engineering expertise across all layers of the stack. And what we're seeing is these things are not, you know, while they're layers, they're not living in isolation. So we need to make modifications up and down the stack to really realize kind of an end-to-end solution.  It's infrastructure. You made that point today. It's, you know, it's sort of got its place, but it needs help with a lot of other things. Yeah, they care about storage. I mean, we're talking about significant, you know, major rollouts of storage. We're talking applications that need to sit in whether it's middleware or whether it's next generation infrastructure, building cloud native applications. These are all things that OpenStack is the foundation for and enabling, but from a full stack point of view, you know, it's actually what we've been talking about internally a little bit with some of my colleagues is it's kind of nice when we can get to the point where OpenStack actually isn't part of the story. It's a critical component, but we're starting to really focus not on just the infrastructure, the core technology components, but the real problems we're trying to solve. And those are application-layered problems. I love that. I actually, I made the analogy my sum up from last year is Linux took a long time to go from, you know, something that, you know, was really useful, but, you know, it's ubiquitous. I mean, it's in every part of the infrastructure today. And I feel like just some of the dialogue around where OpenStack should be. It's not, you know, let's rip out your entire stack and put OpenStack in there. I've talked to some software companies that when you dig into what they're doing, it's like, oh, look, there's OpenStack under the covers and it's doing some really cool stuff there. So, you know, the discussion of it as an integration engine, the discussion of where it can fit in, you know, is in some ways, you know, an extension of what had gone on in Linux in the past. Yep, I totally agree. I was thinking the exact same thing in terms of analogy is Linux is ubiquitous for OpenStack to be successful. We need to see that kind of ubiquity at that infrastructure orchestration layer. And to achieve that, if you look at where Linux was focused 10 years ago, SMP scaling, maybe 15 years ago, SMP scaling. Today, it's on your phone, it's in your car, it's on your TV, it's all these places that we weren't even thinking about, you know, when we were focused on scale up to big iron. And similar for OpenStack, we want to make sure from, you know, from a technology point of view that we're building this infrastructure in ways that we're solving a variety of use cases and, you know, some things that really stick out to me are in the Telco use case or even managed services, where you may have your control nodes for OpenStack pretty geographically separate from the compute nodes. Across a WAN, that immediately creates a new strain on the infrastructure on the OpenStack project. You know, if we can't solve those problems when somebody else can, that's, you know, that means we're missing an opportunity where we could be in that industry. Chris, in previous years, it was like, all right, what's the big component that needs work?  Neutron took a little bit longer, but you know, seems we're getting their adoptions up quite a bit.   It's going to be use case specific. So in some use cases, it's still important to get a lot of features, functionality, or maybe robustness directly into Nova and Neutron. But in other cases, we're looking at, what does it mean to, you know, it's not day zero anymore. We're not just getting a POC going. It's actual operations, run time, upgrades. And so, you know, we saw in the OpenStack user survey and we hear from our customers a lot of interest in improving the robustness of the platform, making it easier to deploy and making it easier to upgrade because you're not going to just deploy once and walk away. This is something you're going to have in your data center ongoing. So maybe if you can unpack for us a little bit, kind of that telco NFV story. So, you know, you talked about Verizon, you know, as a customer AT&T, was also a keynote, Ericsson's here.   It's, you know, four or five more nines than that to keep things up and running. So, you know, maybe you can help us unpack that. Well, it's the kind of reliability, availability, and serviceability are the kind of core features for carrier-grade technologies. And we've looked at it from the point of view of we're not trying to create for NFV some special variant of OpenStack. We're trying to ensure that OpenStack itself is carrier-grade and can satisfy these use cases for the carriers. You know, availability is measured in different ways. Historically, it starts, you know, in the carrier world, it starts at a hardware level.  In a large-scale data center, we've learned from companies like Google and Facebook and Twitter running massive infrastructure that components fail. And we need to help this industry move forward to define availability at the service level, not just at the infrastructure level. And that's something that we're really focused on is how do we, you know, we don't want to marginalize the NFV operator community by saying we're not, we don't care about your use cases, we don't care about your reliability and availability. We want to really help them see how we can build next-generation applications that take advantage of the fact that they're scaled out and failure has a different meaning. You can manage the failure at the application level. So, you know, everybody's got one of these these days, right? We're talking about Verizon, we're talking about Swisscom, and like that whole telco NFV space. What happens when, you know, people, like give us an example of the types of things that are changing when this becomes the most mission-critical application for almost every employee, the way you interact with, like how does that change? What is NFV doing? What are those big kind of like, we don't do this anymore, we have to think about this. Is there anything kind of immediately relatable that you can say this is a problem that Verizon had to solve that they wouldn't have had five years ago that you're now looking at? I mean, the main thing, it's, I'd say maybe less the actual applications and more of the fact that people, and so this isn't in the business context, this is in the consumer context, more of the fact that people are using the network to download so much video content. So there's just a huge strain on the network and in order to scale up the network to satisfy that demand, with a bunch of bespoke, you know, special purpose physical hardware boxes, it just is like the economics, the math doesn't work out. So the first phase is just satisfy that massive growing network demand with something that's infrastructure that's more flexible, it's made out of software, commoditized hardware. The next phase is trying to understand, okay, now that we have, you know, the phone has a first hop into the network. What kind of applications can you build when you have a great compute power right at the edge?  You know, we're looking at things like, we already have self-driving cars and there's research going into augmented and virtual reality and things that require low latency because you've got a short hop to that first point into the network. You know, we're kind of just tip of the iceberg scratching into what NFE can mean as we build out this next generation network. Yeah, it has fantastic ramifications.  It's centralized, it's decentralized, it's centralized.  And now, even if they're first use cases like sort of auto-scaling, dynamic scalability, that means I watch my sporting events more enjoyably, I communicate with my family more, you know, like all those things are the things they're now selling based upon. You know, are you available? Are we the fastest downloads? That's totally different than like, you know, when it was wired connected or now they're going to be relied on for cars and for wind turbines and those things. It's fantastic to see what that begins to start to unlock and what it means from a technology perspective. Yeah, I was at Mobile World Congress over the winter and that really summed up into two buzzwords, 5G and IoT. 5G is the next generation network. IoT is an application, you know, a way to connect sensors and smart devices across the network doing new things, whether it's kind of machine to machine transactions or enabling kind of new technologies for consumers or business. It's, you know, that's, we're building infrastructure. We don't 100% know how it'll be used but we know that the ramifications are significant. Right, right. No, it's fantastic. So, you know, in your role as CTO, obviously, you're up on stage in the keynote. You've got to be able to sort of project the vision but behind the scenes, you're trying to look out three years, five years. How does that work, especially when you think about what you do with your Red Hat hat on and what you do in the community? Can you give folks a sense of how you think about what the future might look like and then how do you think about, you know, steering Red Hat resources and community resources? Well, for one thing, when you're looking out on the time horizon like that, the Red Hat and the community hat are kind of much more blurred because we don't have products built out of those next generation technologies so we're really technology focused. I think another thing that's unique and interesting in that context is historically companies would, you know, they're confined by their own resources. So they're investing into the future just based on their own ideas. What we're doing is looking around the industry where open source software is enabling tons of innovation all across the board and so part of what we do is get engaged in these new emerging communities, kick the tires, understand what it means, look at what the ramifications might be for our existing products or how it, you know, might take us to a completely new place. So it's, you know, the Red Hat, the community hat, one of the things I love about being in a technology role is that line is much more blurry and it's, you know, we're as blindsided as anybody else when something pops up on GitHub that just goes viral. And, you know, the best we can do is monitor and watch and get involved quickly and see how we can, you know, work with those innovative projects. Yeah, so Chris, one of the interesting things we've seen, especially in the OpenStack communities, Red Hat's been an acquirer of a number of technologies. The thing I looked at is I'd look at the OpenStack survey and be like, oh, okay, let me look at some of the things there.  Talk about, you know, how Red Hat looks at those acquisitions in kind of the interaction with the community. Oh, well, community is always front and center in these acquisitions, so we are looking, you know, first of all, what is the business justification? Why are we bringing this company in? Is it a technology tuck in? Is it a services augmentation? You know, what are we trying to achieve from a Red Hat business goals point of view? Any technology that comes with a company is something that we're going to take an open source. So, you know, how are we going to build communities around that? How are we going to sort of intersect other existing communities with this technology? Those are all important parts of the conversation when we're bringing companies in. And it's a way that we can really grow, you know, our products and our skill sets internally because the world's moving quickly and as much as we can hire and go within our own resources, go in new directions, bringing in new companies is another way to help us. Yeah, I love, there was a great, you know, parable, I guess, or not parable, but a description by Jim Whitehurst in his book talking about there was one acquisition that was like, ah, we'll keep it kind of close source for a little bit, but then move it to open source eventually and the end of the story was we will never do that again. It will always start day one open source and we'll do that. I guess the last question I have for you is, you know, Red Hat's much more than Linux these days. You know, how long have you been with the company now? About 10, 10 and a half years. Can you just give us a little bit of insight as to, you know, how things have changed inside for yourself, kind of the breadth of what's going on inside Red Hat? Well, it's huge, it's top to bottom, it's a full stack, it's low level operating system infrastructure, it's, you know, infrastructure orchestration, it's application middleware, it's application orchestration, it's management, you know, all of these components. You're a cloud provider in some cases and, you know, a little bit of everything. We provide OpenShift as a service online. Yeah, so we've got this broad product portfolio. We're trying to address all of our customer's needs. What it means internally is, you know, there's, I'll roll back in time, we brought in JBoss, a big consumer of JBoss technology, we're Windows developers. The Linux people at Red Hat, like, this is oil and water at this point in time, right? And today, we're seeing how all these products are complementary, we do have to keep an eye on how we're developing different components so we can see how we can put them together to build comprehensive solutions. But it's, you know, it makes for an exciting time and we're really focused today on these integrated solutions and what that means from a product engineering point of view, how we bring teams together and sort of share ideas and share information. Yeah, all right, well, Chris, thank you so much for joining us. We'll actually be happy on a little bit later in the show, digging a little bit more on the solutions that you're doing in partnership with Cisco. So Chris Wright, chief technologist, Brian gave him a portion to CTO with Red Hat. And thanks so much for joining us. We'll be right back with our next guest after this quick break. It's always fun to come back to theCUBE.


Good evening, we'd like to call the Durham City Council meeting to order at 7.01 p.m. I'd like to welcome all of you that are here with us this evening. If we could just take a moment of silent meditation, please. Thank you. I would ask Councilman Brown if he would lead us in the pledge of allegiance. Madam Clerk, would you call the roll please? Mayor Bell. Present. Mayor Pro Tem Cole McFadden. Councilmember Brown. Councilmember Cattidy. Councilmember Davis. Councilmember Moffitt. And Councilmember Shul. We have proclamation, well actually not proclamation, some recognitions to be given this evening. And I'd like to invite the following people to join me at the podium, Tanya Dotlik, Co-ordinative Keep Durham Beautiful, Joel Reitzer, Director of General Services, Robert Williams, Assistant Director of Solid Waste Management Department, Laura Webb, Smith, the Education Coordination, Director for Stormwater Services of the Public Works Department. Thank you. We're here this evening to recognize Keep Durham Beautiful for assisting the City in preventing stormwater pollution, reducing litter, and promoting recycling through a grant product that was provided by Waste Management. The grant implementation is a partnership between City staff from Departments of General Services, the Public Works Division of Stormwater Services, Solid Waste Management, and Keep Durham Beautiful. And I want to turn this over to Tanya for her to make some comments on this if you don't mind. Good evening, Mayor Bell and members of City Council. Thank you for providing an opportunity to share this exciting program with you this evening. Keep Durham Beautiful is a non-profit volunteer organization working in public-private partnerships along with the City of Durham and Durham County. We are located within the City of Durham Department of General Services. Keep Durham Beautiful encourages residents, businesses, and community organizations to collaborate to conserve and enhance the appearance and environment of Durham and reduce waste through cleanup events, beautification projects, and educational activities. The grant that we are talking about tonight is called the City of Durham Urban Tier Litter Prevention and Recycling Outreach through Social Media. We are so grateful to our friends who are here to present a grant to us from Waste Management. This is really generous and will really support our efforts to reduce waste and increase the beautification of the City of Durham. I'd also like to recognize the many contributions that are being provided by the City Department of Public Works, Division of Stormwater Services, and the Department of Solid Waste Management. Durham is experiencing an exciting period of growth, and with this increased activity comes a responsibility to increase our attention to the impact on the environment of litter while decreasing the blight that is caused by litter. Roadside litter negatively impacts economic vitality and environmental quality, particularly in the waterways. Together with this grant award, we have initiated a pilot study to assess, educate, and find ways to decrease the litter at five litter hotspots within Durham's urban tier, and we are beginning to work with the organizers of large public events within Durham to increase the rate of recycling at these events. Finally, we will assess the opportunities to add permanent recycling to public spaces in Durham. We look forward to this grant enhancing Durham's public spaces. I'd like to ask the person from Waste Management, Amanda Farrelly, Amanda Taylor, and Chip Dodd if you would come to the podium for a few comments. Mayor Bell and members of the City Council, thank you for the opportunity to be here with you tonight. Waste Management has sponsored this Keep America Beautiful Think Green grant for the past five years. There are a total of five grants and each one is of $10,000, and Waste Management helps to award these grants every year. The grant process is very competitive and Durham stood out as a worthy recipient due to its dedication to community improvement activities. This is evident in the City's effort to revitalize the downtown. We are excited to be part of this revitalization, and we look forward to working with the City through the effort of litter prevention and recycling improvement activities funded by the grant. Thank you. I'm members of the Council. I recognize Councilor Moffitt. I just wanted to welcome a group of college students in the back of the room from Duke this time. And I understand it's a class on ethics in an unjust world, and I wanted to just say welcome everybody. I'm going to tell you that much of the discussion around the agenda topics much, but not all, transpired at that work session 10 days ago. We have another work session on Thursday for the meeting in two weeks, and that's just my part of what you see. Great. Any other comments? If not, we will proceed with the agenda and recognize the City Manager for any prior attendance. Thank you, Mr. Mayor. Good evening, everyone. No priority items. Likewise, City Attorney. Thank you, Mr. Mayor. No priority items. And likewise, City Clerk. No items, Mr. Mayor. The agenda is the consent agenda initially that can be approved with a single vote. If a member pulls an item or a member pulls an item, we will discuss that later in the meeting. I'll just read the heading of each consent agenda item. Item 1 is approval of City Council Minutes. Item 2 is a grant agreement for construction of bicycle and pedestrian facilities on University Drive. Tip number EB-5514. Item number 3 is Barbey Road, Herndon Road, Massey Chalper Road, Roundabout, Sidewalk Agreement. Item 4 is a bid report for December 2014. Item 5 is the lease between the City of Durham and Yarborough and Hesse warehouses, LLC at 700 North Austin Avenue, Parcel ID, 111 319. Item 7 is resolution authorizing a public art project on the North Carolina 147 retaining wall on the south side of Willard Street, and I'll pull that item. Item 8 is an item that can be found on the General Business Agenda's public hearings. I entertain a motion for approval of the consent agenda items, with the exception of item 7. So moved. Second. Second by the Mayor Pro Tem, second by Councilor Brown. Madam Clerk, will you open the vote? You close the vote? It passes. 7 is 0. Thank you. We've moved to item 8, General Business Agenda Public Hearings. Item 8 is public hearing and recommended agreement for economic development incentive with ANJ, Councilor Corporation. Mayor Bell, members of Council, my name is Chris Dickey with the Office of Economic and Workforce Development. Okay. How's that? Okay. Mayor Bell, members of Council, my name is Chris Dickey with the Office of Economic and Workforce Development. This agenda item for consideration is a proposed economic development incentive agreement between the City of Durham and AJ Capital Corporation. According to the agreement, the city will appropriate to ANJ Capital Corporation up to $170,000 for capital improvements within the community development area located at 406 South Driver and Durham, North Carolina. The total project cost of Ashley Corners is $525,000, $336. The proposed project will produce approximately $355,000 in private investment with $170,000 coming from city funding, pusing a 2.09 to one ratio of public to private funding. The thrust of the neighborhood revitalization grant program is to redevelop commercial buildings that will have a substantial impact on the physical economic vitality of the affected neighborhood, which will ultimately over the years strengthen the City of Durham tax base in that area. The proposed project is located along an OED targeted commercial area located in Northeast Central Durham. Prior to the building being purchased in August of 2014, the City of Durham's Neighborhood Improvement Services Department in September of 2013 cited 406 South Driver Street as an unsafe building which contributed to a condition of blight, disease, and vacancy. The AJ Capital Corporation proposed project would eliminate these hazards that poses these imminent threat to the health and safety of the general public and is being recommended for funding based upon its alignment with the goals and objectives of the neighborhood revitalization program. The project when completed, the building will be redeveloped into an 8,500-square-foot mixed-use commercial residential two-level building. The floors for it will consist of four commercial bays totaling 6,250 feet, and the second level is slayed for two residential partons. Each will be approximately 1,125 square feet. The project when completed will stimulate new business development and provide additional housing opportunities in the neighborhood. City support is needed to assist AJ Capital Corporation to securing additional funding for this project. I'm here to address questions. You've heard the staff report. This is a public hearing. I remember so the council have questions. Recognize Councilman Schuhl. Thank you, Mr. Mayor. Thank you so much for this. I think this is a great project and I'm really happy that we're doing it. It's a really important building at a really important corner. I do have a couple of questions. Excuse me. Which? Yes, sir. Is there any way we can put a photo of the picture of this building on there? Are you trying to replace my picture with a picture of the building? Just temporarily. Go ahead and see. It would be nice to have the photo up there. So again, I emailed you these questions over the weekend and I apologize for being so late with them. But the first one is do we require any kind of operating pro former for the building? Do we feel confident in the success of the enterprise? I know that we're not. What we're doing here is renovating a building with our money. But do we have confidence in this, in the sense that we've reviewed their pro former and we feel pretty good about their opportunity for success? Yes, we do. Any project that, well, neighborhood revitalization grant project that comes for you, we do an independent study within our office and a lot of times what happens will contact a local bank and do a check and balances with the number and based upon the pro former that we've examined and the sources and uses of fund, this is a viable project. And it's important to know is that no fund, no city funds will be dispersed on this project until it's completely finished. Great. And then thank you for that. And then my second question is that the developer says that they'll be, their housing units will be affordable units on the second floor. They'll be, as I understand it, from what they've presented to housing units. And I wondered is with this public subsidy, do we want to, are we getting any kind of guarantee of long term affordability of these units? Well, the purpose of the neighborhood revitalization fund does not address affordable housing. As I indicated there in the, as I indicated, the thrust of the program is commercial revitalization. This project just happens to be a mixed use project. The commercial developer based upon my conversations with him basically saw that there was a need in a particular area and said that he would like to put some affordable housing there. But as a, as something that's in the economic development agreement, that's, that's not an agreement. Okay. Yeah, I mean, let me just say, I think that in the future it's something to think about. Obviously it's too late for this one, but I understand that this is a neighborhood revitalization project. But when someone says they're gonna do affordable housing, that makes me think, okay, and we're subsidizing it, are we gonna give them, you know, can we get some sort of guarantee of a time period at a certain AMI? So I just hope that's something that we'll, we'll keep in mind. Okay. Thank you very much. Thank you, Mr. Mayor. Thank you, Steve. Are there other questions? Well, the reason I asked the photo to be displayed, I think it's important to at least convey to the public what type of facility we're making an investment in. And what it does, this is a major corridor we've invested in, and it's the neighborhood that we're very focused and invested in, and I think it's just gonna be very positive. Now another reason I wanted to put up there is a selfish reason. You see those, the way those stop lights are hanging up there, the arms and all this stuff, no wires. And you go down to South Point, Southside, the loss, and you look at all the strings of the way the lights are hanging. You know, give us some thought, Mr. Mayor, as we go forward, because it makes a definite difference in appearance, but good, good, good shot here. But I appreciate your question, Steve. Appreciate the staff, and I appreciate the fact that we're able to support this project. Are there other questions? Recognize Councilman Brown and then the Mayor Pro Tem. Councilman Davis and the Mayor Pro Tem, Davis. Well, thank you, Mr. Mayor. I also want to mention that this is right on the edge of the census tract that we've been dealing with in terms of the Mayor's Poverty Initiative. So it's also important for that revitalization also. Recognize the Mayor Pro Tem. I think it's important to note too that the developer has strong ties with the city of Durham. In fact, we have raised him in this community. Attorney Rogers, and so congratulations on getting this far on your project. Thank you. Are there other comments, questions? Does anyone in the public want to speak on this item? If not, let the record reflect on the one else and the public who wanted to speak. I'll declare the public hand to be closed as a matter of fact for the Council. Move the item. It's been properly moved by the Mayor Pro Tem and seconded it down that way. Madam Clerk, will you open the vote and close the vote? It passes seven to zero. Thank you. We'll move back to the Consent Agenda Item Seven, Resolution Authorizing Public Art Project on NC 147, Retaining Wall on South Side of Willow Street. Mark Owinski, is that, is he present? Mr. Mayor, City Council, thank you very much. I'm actually here. You have three minutes, I'm sorry. Three minutes? Yes, there's a clock there. All right. My name is Mark Owinski. At 2902 Quincemore Road in Durham and I'm a visual artist and teacher residing here. I am here actually to support this mural and would like to address something that I saw that came up in the newspaper and I was concerned that the mural was being discussed on issues with regard to whether or not it supported the Durham Bulls or it had a baseball kind of dynamic. And I really felt that this, having seen some of the design elements for it, drawings for it, that this really sold the mural short. I feel that in many ways it's aesthetic quality and the character of it, it's tradition and optical art and it's the linear quality in terms of wood enhance, the otherwise kind of drab character of that chunk of concrete retaining wall. I feel that it goes a long way to add dynamic color to sometimes rather, how should I say, overuse of beige in city planning and designing. Hope no one takes offense at that. But I feel it's important that as we consider these kinds of issues in terms of the kind of city and the character of the city that we want to see, have the outside world see. I feel it's important that quality art be considered, that it have aesthetic worth, and that we support this work as we go forward and as the city of Durham becomes a much more vibrant place that we should have works of art that reflect that vibrancy. And I feel that in many ways the character of this mural does exactly that, that it will take this rather small little area, the swath of concrete and begin in a small way to address that concern. And I would like the city council to seriously consider supporting it and to pass the amendment to do so. Thank you very much. You're welcome. Are there further comments on this item? This is before us. If not, I would entertain the motion on the item. It's been properly moved in a second by the mayor pro tem, second by councilman Schuyl. Madam clerk, will you open the vote? Close the vote. It passes seven is zero. Okay, are there any other items to come before the council this evening? Well, I want to thank councilman Schuyl for his comments. She said you guys had a rather short work session which reflected in this meeting. And it was a work session and I was not present. So we'll see if we can do something else about that. Have more shorter work meetings and meetings. But anyway, I appreciate everybody being here this evening. Meetings adjourned at seven, 22 p.m.


Welcome back everyone. We'll give a few more minutes for folks to come on in. Hi everyone. Good morning. Hi Amy. Greetings. And as I look at the deck, two groups didn't provide updates this time around, but I know that tag security is really going to want to be able to say things, so Emily, I might lean on you to be able to talk about the security con that just happened. Yeah, of course. That's fine. Cool. I didn't think you might at all, but it was like the heads up. I think they're all a little busy this week recovering from that. So, you know, good times. Should we get started? Yeah, we've got 20 folks here. We can rock and roll. So, yeah. Welcome. Welcome. You have made it to the meeting. You are here, or you're watching the recording, one of the two. And this is my opportunity to be able to welcome in our new members, Duffy and Nikita. So we have new people. Hooray. Hooray is going to be fun. We also want to thank Aaron and Harry. Yes. About going members. Absolutely. Our emeritus members that are joining the illustrious group, people that have helped us out a lot. So, and welcome back to Dave and Kathy. Tim's your meeting rock and roll. Okay, so let's start with the tax storage. Anybody here from tax storage? Yeah. Hi. Yeah. Okay, so on tax storage. We had a cloud native PG project presented last year. We're trying to bring them back for another presentation. And they were also reapplying for the sandbox project. So the first initiative we have is that tax storage and the community are collaborating on a white paper. That describes the patterns of running data on Kubernetes. Focusing on databases initially. We have been discussing it in the last few meetings. We have been wrapped by paper outline. Folks from the tag and the okay, helping discussing and providing feedback. We also working on building a use case template for the story projects based on our CNCF storage landscape by paper. We will also be using information from our database by paper that we're working on to fill in that template. And we got the, the cognitive disaster recovery paper completed published. And we still need some work to do to finish the to finalize the performance by paper. That's all from tax storage. Sounds good. Let me, can I ask you a couple of questions? The cloud native PG, did they share what was the issue last time when they applied and how they are doing better than now? They didn't really say there's any issues. I think they last time when they presented, we have some follow up questions. They say they will come back. We just haven't set a time for them to come, but they say they will come back. Okay, so you're, you're going to set up a meeting and then they're going to come and present. Yeah. Okay. Yeah. The second one I was very while you were seeing white papers a few times, like how do we know that folks are looking at the white paper and it, it's actually, you know, being used in the wild. So to say, do we have any metrics or something? That's actually a good question. So, so I know that for the, for those two white papers, the, the landscape by paper, I did see someone send out some messages on LinkedIn saying hey, this is a great paper. Some feedback. I'm not sure how to measure the metrics and for the, and also the other one, the clownating disaster recovery. Yeah. There are a few people who actually asked me about that paper. So I know that paper. Right. People. I'm not sure if there is a better way of measuring, you know. Yeah, maybe we should ask Amy, Amy. Is there a way we can like, publicize these and, you know, get some download statistics or something, right? We don't want to be yelling to the wide. No, I totally get that I'm kind of struggling a little bit in terms of like the, what would be a meaningful metric and how would we capture that downloads is one way to be able to do it, but Emily you had a hand. Yeah, so I would highly recommend coordinating with the CNCF to formulate blog posts around these. So that will drive both visibility because there's a lot of folks that watch the blog posts and sending them out to the TOC public mailing list so that you get more visibility and awareness through that channel. We've often in the past when tax security does papers, we've also leveraged our Twitter account so you can coordinate with CNCF on getting a retweet of that paper going out, as well as on LinkedIn as well. So there's a couple of different things for the blog post I would recommend filing an issue with the service desk to go ahead and get that started. Beyond that I think those are really good high visibility platforms for elevating this and kind of getting that content out there. As far as confirming the metrics for who's accessing that content as long as your content is stored within the GitHub repo. There are some metrics in GitHub about how that page is being accessed and where it's coming from. So you can actually see who's been looking at that information. Yeah, so basically what we are saying is, let's try to do some post activities after white papers are launched. Maybe write it down so it'll be useful for both tax storage as well as other folks. Yeah, all the time. Exactly. Okay, yeah, yeah, that's such a good idea. Yeah, we should do that. Yeah. We just have been discussing that, presenting that at the QCOM, but we have not done blog posts or even LinkedIn treatment and stuff like that. So, great idea. Yeah. Good one. Okay. Anything else? Yeah, but I think the information they have is a little old. I think it's by it's like 2021 that's the last day what they have. Anything else? That's it. Okay, can we go to the next one. I've skipped the security slide. So runtime will be up in a moment, but I'm going to pass to Emily to be able to chat a little bit about the security tag. Um, so everyone is in full recovery from cloud native security con, which happened in Seattle last week for those of you that were able to join us. Thank you so much. We appreciate your attendance for those of you that couldn't make it. We hope you were able to stream the live keynotes. Everything was fantastic. We had excellent, excellent feedback from attendees. A lot of the responses and feedback we received were that the content was more, it was significantly deeper and more enriching to their work. In some cases, it was suggested that like, while the security track at cube con provides a great first level of information for individuals in a domain specific space like security looking for that additional content. Having that dedicated event just to focus on those has been extremely beneficial for them attendees walked away with a lot of really good technical technically deep discussions. There was great feedback about the size of the conference as well. It wasn't too big. It was a good size. People were able to network and communicate with each other effectively and actually meet new peers. So overall smashing success across the board, I would say. Sounds good. A couple of questions for you, Emily. So did you have the team dinner and how many people showed up. So tax security was actually able to hold a dinner like they used to pre pandemic. They had a ton of people show up. They're working on, I believe, updating the repo for those meetups with that picture. But it was a very, very large table of community members that were able to meet and in person and talk about how they've been enjoying the conference. Nice. That was one PR that I kept, you know, getting feedback notifications on I want to join I want to join kind of thing. So that's why I was curious. The other one was, do you see this as a pattern that we can replicate with other. I do. And we've been talking about this a lot within both cube con co chairs as well as the tag security about what is the next iteration of the color into the standalone event while still providing that same level of content within cube con. So what right now is going on is we're exploring the creation of a security village within cube con proper is like a mini conference within the primary conference itself. If this model is successful. I believe that other additional technical domains can follow suit and creation of those specialized villages within cube con to really drive attendees to those more advanced topics of information that are really centered around like storage or networking or runtime or app delivery. I think that I think we have a high likelihood of that being successful but we do need to try things out and figure out how it'll work. The village will first show up in EU as I understand it. And then from there we'll figure out how it's going to look for North America but this is all like very much in flux discussions are still going on live so I don't want to commit anybody to anything but we're looking at how we can make this work across the board. So Amy. CNC was involved in this. Right and. Yes. Yes, yes, this is cloud native security con. Yes. Okay, so if any of the other six other tags want to do this then the process would be, you know, reach out to you all and get get the ball rolling. Yeah, I think so I mean part of it is sort of like the security tag has had so much history and so much like you know pieces coming together that I'm not sure if we have like a process yet to be able to replicate it but yeah if you're interested we can we can look towards what would be possible. Okay, sounds good. I'm asking because I know it's a sick storage. Pre pandemic in the Kubernetes side of things. They used to have like today. You know, everybody shows up somewhere in the valley kind of thing. So, maybe it's time to revive something like that string. Yeah, we have not had that for a long time. Even for the cube con we just don't have the amount of people that we used to have. Yeah, so we'll see at least last time we didn't really get the critical mass. Okay, for, yeah, for a meet up. Yeah, good goal to work towards. Yeah, yeah sure sure yeah I'll see yeah. Maybe we should talk about this one and see how many people will be there. We've got plenty of time. I mean, we don't have plenty of time for for everything but we can, we can work towards like being able to have a group.  So, Duffy Nikita jumping anytime. I don't want to be the only one talking either. So, these are informal and fun. This is our tag update meeting. Exactly. So, tag runtime. So Nikita is going to provide the update she's been working. So yeah, so like for tag runtime, we've had a couple of projects present at our meetings and there's also been some great progress happening in our working group activities. So, talking about the projects we've had presentations from go and capsule. So if you're not familiar with go it helps you build container images from go programs and pushes them to container registries. The interesting part is that it does all of this without requiring you to write a Docker file or even installing Docker itself on your machine. And it's also been recently accepted into the CNCS framework. So something that we talked about them were about expanding the pool of contributors and things on the roadmap like publishing case studies, adding support for finding images and adding some more ecosystem integration. So moving over to capsule, the presentation and demo work awesome I recommend really checking out the meeting recording. So that's why the project. So, essentially what happens is it provides a multi running environment for communities that has this abstraction called a tenant, which is basically a grouping of communities namespaces and within each tenant users are free to create their services and share all the assigned resources. So, one thing that was really nice from the meeting was that they also invited an end user from gaming company, if I recall correctly, who had been using this in production successfully to share their experience. And actually so like the end users also been contributing to the project will develop a pretty cool to pay. They wanted to consider applying to the CNCS framework. So we gave them a rundown of the process that contributions seem to be mostly from a single company. So we also suggested that they expand the first pool of contributors interact with the multi time and the working group in Kubernetes, and especially the hierarchy or namespaces project was in that working group. We also have a few more products in our pipeline for next meetings, including flat cut, who have also recently applied for incubation. In fact, actually the project and this has been so great lately that we've also had to schedule a few additional meetings compared to a regular. So that's been really nice. Good problem to have. So moving over to working group activities. So the IOT edge working group published the first edition of the edge native applications principles right people, which is the name suggests that list down a set of principles for being at native. And it also took it a step further by using these principles to consolidate an edge landscape. This is a work in progress currently, but I think we already have like 136 projects on there. It was nice to see a shout out to this working group with notes on how folks can actually get involved in this working group itself. This is a presentation from I think an engineer from Sony that was in the Alibaba cloud developer summit in China. And similar to what the edge working group is doing we also have the batch working group that's going to be putting out one page or two mainly layout the main tools in the CNC batch landscape today that's going to just get started with it. And the CDI that is the container device interface side of things. There was some improvements made to the dynamic resource allocation cap for communities 127. This feature essentially use a CDI under the hood to do it's device injection so the improvements mainly sent out around like passing information about CDI devices more efficiently and for the CRI is now extended to accept CDI devices directly. There's also been discussion about CDI support for Docker. So this was discussed in the movies, maintain a call in the last week. And the working group members are now working with movie maintainers to figure out what Docker engine changes very quiet and it will support. We also submitted a session for KubeCon Amsterdam and I guess it's probably a condition of this year because it's small group and we got accepted over to the session and conference. Yeah, for time and time. Sounds good. So the CDI is it already there in continuity. Yes. Okay, sounds good.  It would be good to write, do a one pager or white paper, you know, whatever you've been doing for other areas. Do that for multi tenancy and try to get folks from the project like capsule v cluster and those kinds of things and like get get them together and figure out like okay who's doing what what works what doesn't work or things like that. Do you think that that would be a good good thing to do go do. Yeah, that sounds like a good idea. I think it's a great idea. I mean the capsule team seem pretty interested in growing the ecosystem. And I think they're thinking about applying for incubation. So I think we can reach out to them and see if they're interested in, you know, drive in a white paper and maybe reaching out to other projects and see if they're interested. Okay. Sounds good. Any other questions from to see folks or anybody else on the call. Yeah, I have a suggestion I think this is this is what close OS this project. You know, for example, for the confidential computing with Western. It's very interesting there's a there are a lot of you know initiative on that side. Yeah, we can consolidate those efforts. That would be great, you know, so I think like white paper or some introduction about each of these party to promote, you know, the visibility so that other contributors working in the same areas. That would be good. Yeah makes sense. I like Kathy suggestion because I think it is very useful, especially as a blog post because wasn't as such an, you know, area where a lot of teams are working on it. Also a lot of, you know, different projects right so again, you know, we're having that comparison available in a searchable format is always helpful. Yeah, and I think there's some other projects in the CSCF that are in the wasm ecosystem so we can also reach out to them. Justin, have you been following the confidential computing assets, not the wasm side. Is there any other recent activities or something that folks are doing. Well, actually the most recent thing is that profi and the company that's sponsoring an inox has just shut down. But, um, yeah, I mean there is a bunch of other stuff going on. But yeah, I'm not sure what's going on. I need to catch up with some people that just happened a couple of days ago. Okay. Sounds good. Thank you. Let's go on to the next one. Observability. Hi, everyone. Good morning. We had some some amount of activity, you know, during the first couple of months here. And just wanted to kind of call out what's in progress, a couple of exciting initiatives that have picked up steam. And this is based on the first initiative, which was the observability query standard work group that has been actually a hot topic for a few, quite a few months now and there was a lot of good conversation and discussion around the need for a query standard as different vendors build their own query standards and or query languages and DSL and roll them out. Really the fragmentation that is felt at the end user level right and and a work group has been proposed in the in the tag observability area where you know we are encouraging different folks who had actually had a quite an in depth discussion at KubeCon in Detroit, leading up to actually making a proposal for an initial you know scope as well as a charter so that's ongoing that's really exciting to see that initiative pick up eBay as well as Netflix have been coming from you know these two core, you know, end users have been leading this discussion. And looking forward to kind of driving that. And perhaps you know actually spinning it off as a web group so that discussion is ongoing and there's also a proposal available. So exciting. So I decided as a community as an observability community cross projects to kind of keep it at the tag level because again, and reference spec could be suggested from such a work group and then implementation could be you know easily embedded in open telemetry or other projects, you know why which are really working with closely. So that's the update on that. Matt, did you want to give an update quickly on land growth of the landscape graph project. So the this project I've spoken about last summer, when we kind of conceptualized it and proved out some concepts. It's been dormant for a quarter or two but later this month, we intend to open the door to contribution and start having project meetings for anyone interested. I'll speak to a little bit in today's tag meeting but I don't want to spend a ton of time. There's some links there for those that are interested. In short, it takes the data behind the landscape and builds a labeled property graph so that we can use graph analysis techniques versus more rectangular relational, if you will, techniques. So that that's happening. The group that's the Kubernetes observability work group or observe k8s that group will have an update in next month's TOC meeting, but the TLDR is it remains to be seen what the end end point of this is sort of in parallel there's the open telemetry demo application stack which really has an earlier fork up so we might actually roll changes there, but we'll back to open telemetry and call it a day or perhaps leave something more permanent in place but we'll have an update next month. I did want to just mention that tell all your friends. If you have any case studies or end user sort of stories or experiences using observability tooling or open source projects within the CNCF or otherwise. Please send us a message to us up or friendly case in point in today's tag observability meeting which immediately follows to see me in here. This is Samuel from eBay. I will lead a long time ago but he's talking about how and why you be pivoted to open telemetry. There's a blog post from a few months ago. It's actually a really cool story that's a good blend of business and technical and and highlights why hotel is gaining adoption at the rates we've been seeing, which is great for the project on the 14th. This is still pending. This is a quick update from Quine. If you're not familiar with Quine, it's a streaming graph interpreter, which is kind of a new thing. It's an MIT licensed project that's the result of 78 years of DARPA funded research into basically something that can work in streaming pipelines and read a bunch of little things. At the other side, I have more interesting correlated aggregated things, but unlike a lot of existing solutions that use a timing window, you know, and you only have that it uses a stateful graph. So you don't have a top number of stores to do that. So you effectively don't have a timing window anymore. So it's quite good for a lot of observability use cases. We posit. And so he will come to give a talk hopefully about that project. Yeah, so that's kind of what's on the immediate agenda for the tag. Do you want to finish out on that? Yeah, yeah, sure, sure. And then thanks Matt. I mean, again, just wanted to highlight that our speaker series has been pretty successful, you know, again, just engaging as well as pulling in different, you know, case studies from the end user world as well as from actual project subject matter experts from maintainers from different projects in the observability space. There's also a lot of energy, you know, in specific topics, such as cost management, you know, leveraging observability techniques. So again, you know, all these talks are recorded. It might be worth, you know, kind of leveraging some of these for a special series that is available and tagged on our YouTube channel. We wanted to call out the cube con planning, because I think that there's a fair bit of excitement around the observability day which again super, you know, happy to see a convergence of multiple, you know, events kind of happening, converging into one day because it really enables all the projects to work together as well as the larger community to really converge together. Again, every project has made a significant effort to again reiterate the call for proposals and the observability track also is kind of enriched from a lot of the activity in this, you know, around the observability day. So looking forward to kind of having that energy at you at keep calling you and also the maintainer track where we do plan to, you know, again have a set of discussions around some of the key topics that have been important to all the different maintainers as well as end users who participate. And just to wrap it up, again, I'm sorry we're running a bit late but it wanted to call out, you know, again, how do we better communicate with the to see because I think that there's a lot of activity that is happening on the projects you know both innovative features as well as you know various projects going through different phases of growth as from a contributor standpoint, but I think that it would be useful to have more formal mechanism of communicating with the to see in some amount of detail on these projects because often you know there is a lot of interest from different community members who want to participate in the tag, but don't necessarily have a process for participation other than just joining in and attending. I can totally understand that it is you know as much as what people want to contribute to and how people get involved, but it's also encouraging folks you know with a clear process. So folks want to become tech leads or co chairs, you know, again having some of that process established and published would be useful so really working closely with the to see to define at least some criteria which you know then the larger projects and communities can leverage to to get more involved. So wanted to call that out because I think we'd like to have a more detailed conversation about you know how do we actually leverage perhaps even contributor strategy. The tag, you know, experts there as well as the to see itself to get some guidance. If you could write you, you talked about a lot of different areas that I think we've discussed in the past with the tag chairs as well as with the to see it at previous cube kinds. If you could write down a couple of those points and send that to the to see mailing list that way we we have some form of documentation around them because I believe we already have an open issue on talk and tag communication and better partnership there. Yep, James, an issue would actually probably that's great. That's great. That's a great suggestion. I'm really happy to do that. And again, you know, we can absolutely, if that's an easy way to do it. Absolutely. That's great. Yeah, I would be great to file the issue that way we have something we can work off and they open on February 21 we have that meeting. Sounds good. Yeah, yeah, that's a really hoping that one stays because February 21. I want to get all of the chairs together and to see members to be able to come talk about this. And separately, the to see liaisons are about to shake up because we've got a new to see so. Oh, fantastic. Thank you. Perfect timing for all of this. Exactly. And if you if you need like ongoing engagement with the to see we should figure out like what shape or form it takes, because we need to scale as well. So far we've been trying to do like, Hey, here are two liaisons. You can talk to you. But I don't know if that is working as well. Right. In fact, in fact, there's an issue. I don't know if you've seen it on the at least the tags observability side where folks are have raised the question who's our list. So speaking to the to the need, you know, just to just to be clear that we've seen obviously the explosive growth in the open source project, you know, the number of them over the last several years right now we see the vendor ecosystem leveraging those projects to bring various open source projects to market in that, you know, in this whole ecosystem so now we're going to see another, you know, iteration. And so as that happens, just to be we'll put this in the github issues but what level of technical interfight deal or interchange do you want to have between not just tags observability but other tags are in similar situation. Yeah, absolutely. I don't get it. Yeah. There's also one thing I forgot to put on a slide and I just didn't want to lose to lose sight of it. And that's the effort to add profiling continuous profiling or profiling reports as a formal signal type to open telemetry, which we've reported on it in past months that that is ongoing. It's transitioned to a more technical implementation focus discussion in open telemetry itself within that umbrella now that it's a formalized work stream there. And so open telemetry will be reporting on it but we can continue to give updates in the future but but that is still successfully on that's a good call out Matt. Thank you. I think I would like to say I like the idea of you know the tag defining some criteria or some governance, you know how to ramp up new contributors right so how to how they can become you know reviewers or leader or chair something like that. I think that's a that's a good thing you know to do. I can also, if you have some ideas, you know, we can help together. Yeah, I do I look forward to that conversation in a few weeks. Yeah, yeah. Thank you. Also please review what is already there in sick security and I think tax security I think Emily always talks about. We've done it before a follow our lead kind of thing so take a look at that also so we can have a good conversation there. Awesome. Yeah, that's that's a great suggestion. Thank you. One other question. There was some issue around one of the vendors having some trouble with PR from somebody else. Yeah, did that get resolved or you know that was that was resolved. And again, the open telemetry project GC does plan to meet around you know, having guidelines from the CNCF to kind of handle, you know, different intervendor, you know, conversations are in public because I think that, you know, at some point, the project itself is focused on the technical aspects right and really when there are intervendor, you know, discussions or, you know, some kind of which shows up and influences the project. It is something where we would love to have the CNCF, you know, press liaison, for example, to kind of help in there because again, there were, you know, a couple of reporters who reached out and kind of pressurized some of the maintainers to make statements. So it is something that I think needs to have again, the same kind of communication where there is a clear guideline that he projects can reach out to press, you know, the press liaison and this is what you would do so we are putting together some guidelines on the open telemetry side to be able to work at CNCF and Amy just heads up I think if folks have reached out to you, we will be. So, you know, we were all watching it. So, and we were waiting to see if you can resolve it within the tag or you would come to us and, you know, we are waiting for that. But I'm glad it got sorted out but yes, I think it took some time and some effort from all of you to like get everything in a line. But yes, I agree with you, we should have a little bit more set of things that we need to. So, next time when this happens, we are better prepared for it. Yes and and you know, again, these kind of things can happen right because there are CNCF is, you know, has a amazing set of contributors, you know, coming in from the different members of the industry but also they are competitors often and and you know it is something that where we really don't want our projects to be affected by, you know, that kind of an interaction. So, having some clear guidelines there and perhaps, you know, having some clear process, even if it is, hey, you know, just reach out to this email ID and reach out to CNCF's press, you know, team would be. So let's log this as another issue. Sure. We'll see what we can do. All right, awesome. Thanks. Thank you for bringing that up. Sounds good. Thank you. Next one, please. Tag network. All right. We've, we've been struggling a bit for agenda. For a while. They've got a potential upcoming presentation from slime. And I actually don't know if they ended up submitting sent to sandbox or not, but that was to be a sandbox presentation. I haven't seen it go by yet. Okay. Okay. Then I'll reach out to them to get them to get them hooked in. They're an interesting project. We do have an upcoming agenda, a project update from network service mesh, which I think we'll focus on fact that that service mesh can run as a foundation for other service meshes and so on. So, yeah, and I think that's a good thing to do. I think that's a good thing to do. And as a result of that, I think that's a good thing to do. I think that that's a good thing to do. Thank you. So, yes, I want to thank you for being here. I'm glad to be here. And I think you should be presenting there. While we've had trouble with some of the agenda over the last couple of months, one thing that's been a consistent effort has been, well, commissioned by him to help create a, well, back then I think it was just called demo, the CNCF demo, and it was to try to get Kubernetes and Prometheus stood up in a scriptable way, such that people, you know, users could get familiar with Kubernetes and Prometheus as the first two projects inside of this demo. And so like carrying along in that same vein, this cloud native playground is something that I wanted to raise up today as an initiative from the Measury project, that I wanted to get some visibility to TLC members, maybe see how much you all feel like this makes sense that other projects might want to participate in this. The cloud native playground, this concept is that, well, in a visual and collaborative way, there would be a way of designing your infrastructure, your cloud native infrastructure. And so this playground is yet to be launched, but the hope is that there will be a set of, well, project specific best practices for how to configure individual projects and an easy way for users to come by and visually comprehend how their infrastructure is configured. Measury as a project has been originally focused on service mesh management, multi mesh management and performance management for those, but is an extensible platform for general infrastructure management. And one of the things that we've yearned to do is, well, is continuing that same vein in which the project was initially created kind of in a similar way as to what you find with playwithdocker.com or playwithkubernetes.com, that people get this sandbox environment to learn and explore. And so that's the sort of the genesis of this particular initiative. And as we go to socialize this with other projects, I figured we'd raise it up here. So something for people to potentially familiarize it with a little bit. It's a, Measury is a sandbox project. And so as we go to have a hosted version of Measury running and try to provide something of a safe environment in which people can learn about all of the individual CNCF projects. Yeah, it sounds good, Lee. I think you can send an intro email to the CNCF TOC and then we can make sure that it flows down to other, I mean, to the tags and the people not on the call and see how we can get the word out. Is this running on CNCF infrastructure? No, it's not. That's actually what I was in a roundabout way trying to get to right there at the end, which was, I don't know that that is afforded to sandbox projects or not, but. We can think of something. Yeah. Yeah, we can think of something, drop something into service desk and we'll take care of you. Absolutely. Equinix is very easy. Like just in the last week, I was able to set up some stuff for one of the projects. So yeah, we should be able to get something together, especially if you want other projects to do more here, it would make sense for it to be not tied just to one sandbox project, but also okay. So one question I had for you was I've been hearing fragments of conversations around like a CMI v2 of the specification. Is the tag one of the places where we would be able to collect people together because it's happening all over the place? Like some stuff in continuity, some in Kubernetes, some in like a rapport called container networking. So I don't know if you want to pull together people to say, hey, let's go do this and let's see, especially because there's a lot of good people in this tag and they've seen it all before. So that's why I'm curious if it would be something that you would like to continue. Yeah, absolutely. Actually, CNI was for me specifically one of the first projects that I'd done diligence on. And so yeah, do you consider that the best place to initiate that conversation is with the CNI maintainers and that they would know? Yeah, just figure out where it is happening at this point and figure out who's talking about it and let's see where it would naturally fall just because most of the people are coming from one place or the other. Gotcha. Yeah, we'll do. I'll gather some info, see if we can organize that, present some of that info for you guys to figure out. Get the people together in the room. I don't care exactly where it falls specifically. But as a leadership team, we should like, hey, you all should talk to each other and here is something to march towards. Yeah, I like the idea of this, like the playground, the sandbox environment for people to try out different projects. I think that's good. And if that can take off, I think the follow on what you can do is to publish some data on users' experience of using these different projects. So I think that information will be very useful for the end user to know, to choose, for example, if there are multiple service mesh projects and users' experiences. Yeah, to regurgitate that briefly. Yeah, not only is it for the service mesh projects, but just really any workload or any project that runs on Kubernetes and basically all of the CNCF projects, but like I think in part what Kathy, what you were saying is, yeah, it gives some of the projects an alternative venue to promote best practices with their projects that they're able to share some of those configuration best practices in a sandbox type environment. So as users come through to learn that they might do it in context of what the projects themselves are promoting or suggesting in terms of the configuration of those projects. Yeah, right, right. Or that could see how the developer velocity each party provides, right? Is the configuration simple or is it very complicated? I think those experiences, those are good information for the community to know. Okay, tag environmental sustainability. Hello, so a few updates from the tag. We created two new working groups, so these are also the first working groups. The first one is around communications with the streams events survey, like in general communication between like also different organizations and projects and so on. And then also we plan to do a website. So for example, about the survey last year, end of last year, we created the survey. We plan to do this not like every month or so, but if it like makes sense. So maybe we have like a small team around events, a small team around survey and so on. So you will see how it goes, but this is like roughly the plan. Maybe this will also change, maybe create like new working groups or not. But this is like the starting point. The second one is around tools and practices. For now, we plan to do like in addition to the current cloud native maturity model, or like do a separate one or do both. So this is not 100% clear. We are at the moment in contact with the green software foundation because they are also looking into the same direction and they have not yet something set up. So one possibility and maybe this is like also likely that we have both things. So we integrate with the cloud native maturity model and also contribute to the green software foundation or just collaborate in that way. About the landscape. So we have been working on collecting tools and like in general like landscape staff, organizations and so on for quite some time. It's like not yet finished. It's obviously, it's also not yet finished for the first version, but we plan to release it or the first version to show it in KubeCon.eu. And like the third stream in the second working group is around best practices. So there's already a few best practices in the green software space, but they're not mapped to cloud native and not to the cloud space. They're like general to software engineering. So our idea was to basically frame this in the software space and the cloud native space. And yeah, we are starting with these working groups. We plan to do a maybe bi-weekly meeting or something like this, see how it goes. And yeah, about the next topic, I already like briefly talked about the survey. So we collected a few responses to the survey and we are working on a presentation. We are currently thinking about how to publicize this. It's not finalized, but it looks interesting. So probably we will write the blog post.  This is probably something that we will discuss next week in the meeting. So the next one also about KubeCon.eu. So our idea currently is that we have like two milestones, roughly two milestones. So KubeCon.eu milestone and the KubeCon.na milestone and that we have like a couple of things that we want to like do in half a year, roughly. So for example, for KubeCon.eu we have a milestone where we want to like have a landscape document ready and show already like our first idea is about the maturity model. And we will have a discussion tomorrow about the milestones itself and also like meetups, tag meetups, what we want to do, what went well like in KubeCon.na last year and what we can improve and so on. And the next item is about project presentations. So we discussed in the tag meetings that we would like to have project meetings just to connect with the creators of these projects and also to introduce them to the CNCF and just to have this communication flowing. So we want to have like every month or maybe we also can increase this but every month roughly a presentation half an hour or something about some tool. The first one would be KubeGreen and the one after that is it would be Kepler. And there are a lot of tools so this can take a while. And right, so next one. I'll let you pause here. We have one more group that I want to be able to make sure that we get to. Okay, I'll keep it like short. In the last meeting one contributor raised the issue that we would like to like elaborate a little bit more how to contribute to the tags or to the CNCF from like a non-technical point of view. So if you don't know GitHub, if you don't know anything like this, so we look into this and we agreed on an abbreviation because environmental sustainability is very long. Yeah, I remember you had trouble trying to shorten it. So tag in me, I like it. It rolls well. So thank you for that update. Our last group, tag contributor strategy, come on in. Okay, howdy. So real quickly, we're analyzing the data from the CNCF contributor survey that we held late last year. The main goal that the tag had in running the survey was to find out what common blockers are for people, trying to contribute to CNCF projects and maybe not being successful, so that we could provide advice to projects. And when we have a report on that, you all get it. We have yet another mentorship cycle. CNCF is in planning and enrolling in Google Summer Code, which means any CNCF project would be eligible to propose a project for it. And the next LFX cohort is now accepting mentee applications. There's 55 different proposals across the CNCF project for things for mentees to work on. So if anybody is connected, particularly with universities, please share out that information, which you can get from our mentorship repo. We already proposed this to the TOC, adding governance review as part of graduation. And you all said, yeah, that sounds like a good idea and immediately gave us two projects. So we're working on that. And one of the things that we'll get out of that is we're going to create a template for how the governance review should run. And in the meantime, we're working with both Cilliam and Kata on governance improvements. And we have restarted because of a new member of the TAG. We have restarted maintainers here. So again, please share this with any maintainers that you work with. We're going to have one in February 13th on managing non-code contributors for your project because we find that a lot of projects are missing out on a very good source of contributors because they don't have specific programs for non-code contributors. And we're also planning on trying to have an in-person maintainer circle in Amsterdam space permitting. But please share that first one with anybody you know and you'll see a follow-up in the millions. That is perfect. Thank you. Sounds good, Josh. I'm so happy seeing the mentoring working group launched and I hope folks are coming to help out there as well. So we can always use more. At this point, like a lot of other TAGs, the limitation of our TAG is we need more volunteers, more people involved to do more things. I always spread the word out for you, Josh. And also technically, I should be grooming my own successor because I've been TAG chair since we founded the TAG, which is a little bit longer than we really want the CNCF. It's going on the list for this year. Other questions? Are we doing like a press push for more people for the mentoring side? Or have we got a mechanism for that? Just to call out, Josh, thank you again for calling this out. Because again, as projects, even a hotel is not aware of this. So this GSOC push, so that would be useful to communicate to the projects. If we can help in any way, and you can point me to some material, we can gladly remind different projects. But it's also that Outreachee, for example, is also accepting applications. Again, maybe having a more comprehensive mentoring list may be useful. Because we all participate in Outreachee also. So one of the things we're doing is actually doing some reorganizing. The CNCF has a new beta tool called Clotributor, which lists help-wanted issues across all projects. And we're looking to incorporate that, which would give us a better and sort of continuous pipeline into projects creating mentorship opportunities, which is currently the really time-consuming and slow part of the process for all of the mentorship programs. And once we get that working, it'll become a lot easier to just participate into whatever program currently has a cycle. Yeah. Awesome. But again, I think I'd love to understand more so that we can actually get more involved. But thank you again, Josh. Josh, let's send one message out about the next cohort for the LFX, at least, to the TOC mailing list. Okay. We'll do. Okay. That's perfect. Thank you. Exactly on time. We've got a couple of projects in voting. I was hoping to be able to check in with Ricardo on being able to move over key cloak. Any other updates around projects that have not? I think Fasila had a question on the meeting chat asking about which one was this. Istio. Istio. Yeah. Projects waiting on sponsors are over on the meeting minutes doc. They are not included here. Right. That's where we currently are on the sponsor pieces. So, all right. No one's putting their hand up to one, be able to talk about like further projects in here. We will be convening on the 21st with TAG chairs and the TOC together. So, I expect like lots of fun in that one. Elita, bring your issues. Thank you. Bye, everyone. Thank you so much for your time today. See you all.