Live from Vancouver, Canada, it's theCUBE. Covering OpenStack Summit North America 2018, brought to you by Red Hat, the OpenStack Foundation, and its ecosystem partners. Welcome back, I'm Stu Miniman, and you're watching theCUBE's live coverage of OpenStack Summit 2018 in Vancouver. My co-host, John Troyers here, and happy to welcome back to the program Mark Baker, who's a product manager with Canonical. Mark, how's the show treating you so far? The show's been going very well. So we've seen people coming to us on the show floor, coming to the sessions. We're seeing real interest in building scalable production clouds. And so, and coupling that with other container technologies and a lot of other complementary technologies like machine learning. So a lot of the discussion is, can we build clouds? But also much more about the workloads and the kind of integration with parallel, if you like, or adjoining technologies. Great, I want to talk about the customers really, Mark. So as you said, you've been to a few of these shows. Oh yeah, yeah. You know, we've been to a few of these also. And the makeup of the attendees has changed a bit. One of the things I heard, it is 2X the number of cloud architects with their title compared just to last year. Little bit of a broadening into the scope. What are you hearing from customers? What brings them here? What's exciting them in this environment? So, I mean, yes, certainly cloud architects and economical, we regularly talk to cloud architects. And because architecture or the cloud is something that evolves, it's not something that's pinned, right? As workloads evolve and new technologies come along, you need to be able to evolve that architecture. And therefore people that understand that are important. I think it's also noticeable, you know, I'm sat here wearing my blazer. It's noticeable seeing quite a few people around the show wearing blazers. And so you go back in a couple of years ago or even a year or so ago, it was very much a sort of developer-centric type of event. We're seeing more business conversations now and even discussing things such as money and economics, which weren't necessarily conversations that we were getting too heavily in a couple of years ago.  Oh, for sure. You hear lots of cool T-shirts and, yeah, ironic facial hair and the like. So, maybe from your standpoint at Canonical, talk a little bit about those constituencies of Huda-Selter. We've got the operators, you've got the developers, you've got the, you know, C-Suite.  Maybe help walk us through some of those roles that you're talking to, some of the biggest concerns that they're having and how you're helping them. So in most enterprises that we're going to talk to, we're typically talking to initially operations, right? Because they know that they need to be able to provide these services to cloud services and container services to their customers internally within the business. And they're looking at, okay, how can we operate this? How can we secure it? How can we scale it in smart ways? And they're looking for our help and assistance doing that. Very soon after that, we'll need to go and talk to developers or engage the line of business developers. Primarily because we need to, this represents change for them. Moving into a cloud or moving their applications to containers represents change. And we want to get them onboarded into this environment and to start to begin that change as quickly as possible. The cloud to succeed, it needs to have many running workloads on it. And so engaging with the developers to take advantage of the capabilities the platform can provide is really important. We'd love to be able to go and talk to at that sea level. And we are starting to have more of those conversations. But I think the type of infrastructure that OpenStack and Container Technologies provides, the initial interest is very much coming from those operators, from the architects, and from the developers. Well, let's talk about operators for a minute. I mean, once upon a time, there was a tribe of people called Sysadmins. They were kind of surly and they took care of things like Linux, right? And now out of that Linux framework, there's a huge set of technologies that have grown all based on Linux, all that Canonical works with. And there's a new set of skills required. Can you talk a little bit about what the new operator needs to know and how you can help train people? And Canonical can help train people? And if you're an assistant man working with Linux, what different things do I need to care about now in the cloud management world, cloud operator world? Yeah, sure. You're right, it used to be relatively simple. And that you would run a VM or you'd run an application on top of their metal and there'd be certain things you'd need to be able to tweak, to scale it, and to up the performance. But when you're running in, as we say, more agile infrastructure, so whether it's cloud and containers or combinations of both, there are very many different variables and how an application is able to take advantage of the storage or the capabilities that a platform provides means there's many different knobs and dials that you can turn. We tend to be advising right now, people on bringing in services such as CICD, Continuous Integration, Continuous Deployment so that they can start to adopt some of these newer ways of working. Operators now, they need to be much more aware of what the workload characteristics are and how that might behave on a hypervisor or how it might behave within a containerized environment. I just came out of a conversation with a customer, for example, that was asking detailed questions about storage performance. They have applications that require certain levels of storage performance and different types of storage that we can bring to bear in conjunction with an OpenStack which is going to be the appropriate one and how do they segment them? And so it's definitely become more complex but I think through collaboration events like this, we're actually getting much better at being able to provide them with the information and the choices they need to make. Yeah, Mark, speak to us a little bit about the community. OpenStack started heavy users in the community, contributing to the community. How do you see that dynamic playing out today? Well, there's still lots of contribution coming into OpenStack so that's good to see. We are starting to see, as OpenStack has matured, as the marketplace has matured, some of the focus no longer being purely on contributing code but now sharing experiences around operations. And that's starting to move into this area where people use this phrase infrastructure as code to be able to access infrastructure programmatically. I think we're seeing collaboration now in the OpenStack community and the adjacent communities around collaborating on the operations, especially when those operations themselves are encapsulated in code. So very simple things, sounds simple, not necessarily easy to do but being able to upgrade and update in place, how you would sort of suspend a system whilst you perform some maintenance and evacuating the workloads and bringing them back in and those kinds of very common tasks for cloud operators. We saw even just a few years ago how operators would each have their own way of doing it, their own preferred methods and this was generally not so efficient so collaborating on those and sharing best practices is one of the really interesting things to see within this community today. Sure, sure, I think the evolution goes, everybody then starts to write scripts but you all write scripts in your own ways and eventually you have to come up with a framework. Yes. And you all have developed a couple of different frameworks in terms of installation and upgrades and things like that as well. Absolutely and it's one of the things that once the customers start to understand that we've developed a framework around operations, those operations are encapsulated within code and it means that if we have a customer, Deutsche Telecom for example, one of our customers that is understandably very security conscious because they run the telco network, has best practices around the security of their cloud and we're able, when they start to make recommendations or updates to that, we're able to take those and share them with a broad audience and get that sort of collaborative spirit around what's the best way to be able to do this, right? Yeah, so you mentioned security there, any other kind of key pain points what are you hearing out in the marketplace is GDPR, something that a lot of your customers are beating on you and what's the canonical position there? Yeah, absolutely, so GDPR has been a real catalyst for people to look at areas for security that they probably meant to get around to at some point but never had, so. Some people said it's the Y2K of this generation. Yes, exactly, it's definitely a forcing function and so one of the areas that we've seen a lot of activity around and certainly we've committed resources to it within the last couple of months has been around encryption of data at rest. So obviously in the cloud, you're going to have a lot of data that's there with the relevant workloads and some of that regulation, GDPR regulation is about what happens if somebody removes a disk from a server, does that mean that they have access to the data as we start looking at things such as edge cloud? So we've very many clouds close to the customer or close to the edge which don't necessarily have the same data center infrastructure around them. How do we secure the data there, right? So encryption of data but doing it in a way that doesn't require you to manually type passwords in to be able to access them all of the time is not a simple problem and we've spent quite a few resources working out how do we address that, how can we do it in a way that's going to allow it to be dealt with economically and scalably. We've been a lot of talk about open infrastructure in general here at the show and open stack obviously is designed to manage infrastructure but we've already talked about containers here with you in this segment. There's a lot of container news, Kubernetes news, open dev summit going on at the same time. So how do you as a product manager you can't just be worried about one part of the stack how do you and your teams worry about that integration and that unified platform and bringing together these interactions with all these different open source projects. Oh yes, for sure and that's, I mean certainly it's one of the things that Canonical has been cognizant of or working on for quite a long time is a Linux distribution at its heart is really the integration of very many different components from a kernel and libraries and compilers and all the various other pieces that go with that. So understanding how these components plug together that's open stack with containers and open V-switch for the networking and set for storage for example, that's very much part of what we've been doing. We're learning with customers as we go very much that how they want to plug these things together with Kubernetes could be Kubernetes is running alongside open stack, Kubernetes is running on top of open stack. Open stack even running on Kubernetes some of them are looking at. So understanding how they, people want to be able to plug technologies together and we standardize very much on sort of reference architectures of combination of open stack plus Kubernetes as a really simple example. But then as part of our QA process, testing process all the reference architectures that we build with hardware partners and other partners too is ensuring that we're able to deliver that as a standalone products as required but also as effectively solutions together that are fully integrated, fully supportable and they're going to deliver the capability of the customer needs. Okay, first of all the open stack on top of Kubernetes really is that something you'd recommend to customers or is there a specific use case for that? It's not something that we recommend today. So there's been certainly a lot of discussion in the open stack community around the control plane and what's the best way to deliver the control plane. Canonical made a very strategic or specific choice several years ago that actually containerizing the services is the right way to do this. So we containerize basically all of the control plane services apart from Neutron Gateway which can be a little tricky to do that but we containerize all of those services and it gives us flexibility when we want to perform updates and migrate services between different systems for example. How do you manage those containerized services though? There's lots of diversity of opinion. Some people want to be able to do that with Kubernetes and that's great and we certainly track those efforts and work with those people if they're using Ubuntu or some of our technologies but I think it's still yet to be decided what's the best way to be able to do this. Yeah so you have an interesting job as a product manager you always want to productize and in general standardize as much as possible and in these communities you have the diversity of opinions oh I'll take this piece, I'll get rid of the core, I'll do something over here, I'll flip it upside down. How do you balance that giving customers choice that making sure you can deliver solid offerings that you can support? And so I mean that's very much it, it's a choice we can say look we can deliver a robust high performing cloud with these reference architectures we've learned that through experience with customers and working with our partners we understand customers all believe they're special and they all have their own special requirements often with good valid reason and so but we'll always try and start from a base and then say let's start to iterate through that adding in additional capabilities or maybe tweaking something for your particular use case if you do that and see how it impacts the cloud because for us to be successful of us the OpenStack community to be successful we need to ensure that those clouds can live and breathe and evolve over time and if they're making too many or too heavy a customization of that cloud then it can start to impact their ability to do that. So we're all for that choice. Speaking a little bit on the line of standardized services I'm really intrigued by managed OpenStack from Canonical can you talk a little bit about what customers it's right for and when it comes into the conversation and then we're in the life cycle because I guess then it can also eventually go away as the control gets handed back over to the customers when they're finished with managed. Absolutely so we started providing what we call BootStack as a fully managed OpenStack service primarily to address the skills gap within the OpenStack community. So we saw a lot of companies interested in deploying OpenStack a lot of enterprises looking for OpenStack but they couldn't find the talent or the people with the experience of deploying a managing OpenStack. There weren't the people around right hiring was hard so and that was becoming a blocker for us to be able to deliver clouds to those customers and so we started to offer a managed service. We had a lot of those reference architectures and best practices pretty well nailed down but it was a facilitator for them to get up and running with the cloud and it's a point where they became comfortable in operating it, managing themselves, hand control back. We've seen that as a very popular model and that period where they're having us manage it can be six months or 12 months or 18 months but the customers know they have the reassurance that they can take it back control in house that they can operate it themselves and they can manage their own environment. They become self-sufficient but they're not doing that from day one. We're holding their hand and taking them along that path. So that's been a very popular offer. All right, Mark Baker really appreciate you giving us an update on really the broad spectrum of customer use cases and all the updates from Canonical. For John Troyer, I'm Stu Miniman back with more coverage here from the OpenStack Summit 2018 in Vancouver. Thanks for watching theCUBE.


All right, I think we're going to go ahead and get started for a couple minutes into the hour. Looks like we have a good group of folks here. So I'd like to thank everyone joining us. Welcome to today's CNCF webinar, which is a bit of a mouthful, but Automation AI and ML for Network Management. It's already here. Our organization's ready. So the good news is I'm just the moderator.  My name is actually Phil Estes. I'm a Distinguished Engineer and CTO for Container and Linux Strategy at IBM. I'm also a cloud native ambassador, and I'm moderating today's webinar. And so I'd really like to welcome our presenter, Andy Singer, who's the VP of Marketing at Kentick. Before I turn it over to Andy, just a few housekeeping items. Obviously, as a webinar setup, you're not able to talk as an attendee. We'll hear from Andy, obviously. But if you have questions, we'd love for you to use the Q&A box at the bottom of your screen. Obviously, if you've been on Zoom before, it's easy to use chat, but the Q&A box would be a great spot. Taylor from the CNCF will probably point you there if you post a question in chat. But that way we can actually track questions and make sure they get answered. So feel free to drop questions in there. This is an official webinar of the CNCF. And as such, it's subject to the CNCF Code of Conduct. Please don't add anything to the chat or the Q&A that would be a violation of that code. Obviously, what we mean there is please be respectful of all your fellow participants and the presenter today. So with all that said, I'd love to hand it over to Andy to kick off today's presentation. Thank you, Phil. Just making sure you guys can hear me okay. I think so. Sounds good. All right. Good morning, good afternoon, and good evening to everyone. And thank you for joining today's webinar. Phil, I'm, you know, Kentick is honored to be able to present to this audience and we appreciate you moderating today's sessions or session. If anybody has questions during today's presentation, feel free to ask. Phil will moderate and I will do my best to answer them. And if I can't, we will get you a response after the webinar. So today's topic is automation, AI and machine learning for network management. It's already here. Our organization's ready. On the agenda for today, I'm going to quickly tell you about Kentick, who we are and what we do. We'll talk about why automation is important, kind of a state of the market overview. Then we'll go into some findings from a survey that we released earlier this year, specifically talking about artificial intelligence, machine learning, cloud adoption, and some interesting trends. We'll talk about AI ops, which is what Kentick is talking about these days, and go over a summary of our findings and some recommendations for everybody. And then we'll do Q&A. So first, a little bit about me and Kentick. So I lead the marketing function here at Kentick. Kentick provides revolutionary insights and automation to make every network excellent. We power up operations teams with AI ops for network professionals. We were founded in 2014. Our headquarters based in San Francisco, and we have employees all over the world. And we have over 250 customers. So first, I want to spend a few minutes talking about why automation is important. And I'm sure a lot of you deal with automation every day, but I thought it'd be interesting to give you Kentick's perspective on how we see the industry moving, what's happening, and what are some of the challenges that network professionals are facing today, and why that's relevant for cloud. So many of you already know that digital businesses drive the fastest revenue growth in history. And you can take a look at companies that have come to market today, and just over the last 10 years, they've had explosive growth.  Today, it's very much a cloud centric world. And I think we all know that just by nature that we're on a CNCF webinar. But it's an important thing to call out that the cloud is really at the center of everything that happens today with digital businesses and most businesses in general and for consumers. We know that all this data is flowing to and from different clouds to and from different cloud based applications. Many enterprises and businesses and providers have lots of data centers, whether new or software defined or legacy data centers. In addition, companies and enterprises and organizations still have and rely on headquarters and branch offices. All that connectivity flows to and through the internet and to and through and from the cloud. We know that networks are changing. And in my experience in the last, you know, 20, 25 years, I've seen tremendous change in networks. But I think some of the most transformative changes come in the last 10 years that we've seen the rise of the cloud and what that's done for networking. So now today we have multiple architectures in place, physical, virtual. We've got increased traffic complexity. We've got a ton of API driven use cases. So the rise of API interconnectivity is really driving a lot of the explosive growth that's taking to place today, both in networks and in applications. We've got an increasing amount of automation and we're going to talk about that. But when we talk about automation, we're specifically talking about manual tasks that can be automated to drive increase efficiency and efficacy. We've also got varied security threats. So with the rise of cloud, we've seen a whole new wave of security threats, everything from endpoint based attacks to network based DDoS attacks. We know in all of our conversations with our customers and prospects and the market that we engage that network teams, network professionals, all up and down the market, small companies, medium companies, large companies are struggling to some degree. We know that network outages are becoming a problem, largely due to the complexity that's there today with networks. A recent Amazon outage was estimated to cost about $99 million in lost revenue. Southwest Airlines network outage costs had the potential to reach approximately $82 million. And when we think about and when we talk to the people that are thinking about outages every day, here are some of the things that bubble up. Here's what they tell us. They say, number one, we need to be able to quickly detect problems. And we know it's difficult because of the complexity of the networks that we have today, whether we're 100% cloud, multi cloud, or even hybrid cloud, there's a huge need to be able to quickly detect problems. We know that performing root cause analysis is even more complicated, just by nature of the fact that there's so many different types of data coming in that you need to be able to analyze and need to be able to look back at data, historically to be able to really understand the root cause of a network problem. Migrating applications is becoming increasingly complicated, not just because it's hard to begin with, but because of things like different architectures, whether you're using containers or not, whether you have single cloud or multi cloud, multiple operating systems in place, even multiple hypervisors and virtualization platforms, migrating applications is a big challenge. Planning for capacities, another one. Capacity is really important because of the demand out there for applications in the cloud. You need to be able to understand, do you have enough capacity, where are you going to need new capacity, where are you exceeding your plan capacity, and are you paying too much for that capacity. And then that leads me to allocating network costs. More and more, as different types of transit are out there on different types of networks are in place, network professionals have the ability to play a bigger role in helping businesses maintain and manage the costs for network. So I want to now transition into a survey that we conducted called the state of automation, artificial intelligence and machine learning and network management. So we went to Cisco live earlier this year, we executed our survey and we got 388 conference attendees to give us really valuable data on everything from their business and industry to their thoughts on several key questions around this specific topic. The respondents were had lots of different titles we got C level folks SVPs VPs, but a majority of respondents about 50% reported having a title of network engineer. So the biggest group of respondents to our survey were actually the people who were working on the network hands on every day. So here's a brief summary of our findings. So the move to cloud is still underway for a few, but multi cloud is the reality for many. And I think that's big, even just one or two years ago, hybrid cloud or multi cloud wasn't as popular as it is today. Network automation is taking shape. And we'll provide some data that talks about how the types of automation that are being used goes across many different categories and even taking place more and more on network management tasks. The third finding is networking processes like compliance and incident response are less likely to be automated. So when it comes to things that have to do with regulatory issues or even security, those tasks are still being performed today by people and not being automated. And finally, machine learning is growing in importance for network management. More and more people are realizing that the complexity of today's networks and the speed at which we operate and the real time nature of all of our businesses requires more and more machine learning to be used to be able to help everybody better manage the networks and we this was true across the board industry title regardless of who you ask. Phil, I'm going to pause right there just for a quick second. Do we have any questions in the Q&A. We don't yet at this point. Okay. All right. So let's jump into some of the findings. So as the move to cloud continues multi cloud looms large. So our analysis found that 53% of respondents are using a single cloud provider, but nearly half are using multiple cloud providers. Some additional data are includes for example, the greatest adopters of cloud services are the education sector. The last majority of respondents said that 50% or more use only one cloud technology and finance sectors gave the strongest responses confirming multi cloud use at 43% and 38% and the energy sector was a close third at 37%. In addition, you know, we think about these results. Well, our takeaway is that networking pros are already dealing with significant operational complexity. It's hard enough to move from a physical to a virtualized environment. It's even harder to move networking into a cloud providers environment, and it's even more complicated to work with multiple cloud environments. Hey Phil, I see a question here that we've got do we want to see if we want to take it real quick. Yeah, absolutely. So, Josh asks, do you have any stats on how much of the industry invite industry move to cloud, either completely or partially. So, I think from our report, we've got a couple different stats we've got some things by vertical showing that how they moved to the cloud and actually a great way to get you this information is to actually get you the report, which has actually cloud and multi cloud by industry. So what we'll do is we'll put the link in the q&a to be able to download the report and that will better answer your question. All right, great. Thanks. So our second key finding is around network automation. It's definitely taking shape. So what we asked our that what we asked respondents is how ready is your organization for full automation to manage network performance and network security. Our takeaway is that 85% of respondents reported having at least one network automation deployment in place. 55% reported having two or more deployments and 27% of respondents reported that their organization is either extremely prepared or very prepared for full automation. Now, this in my view is actually really exciting because even as long as just last year or even two years ago, network automation was kind of largely shunned as something that's maybe frightening or unreliable. But that's changed the more and more companies are adopting software defined networking automation takes a bigger and bigger role. But I see broader IT organizations in general are no longer willing to wait for networks to be manually configured. So when it comes to cloud, we know that things like provisioning, bursting, these are all things that happen automatically. And a lot of the networking in there is automatically provisioned. But when it comes to network management, troubleshooting and remediation, these are the things where automation is taking the next big leap. You know, when we look back at last year, we did the same survey and same question and last year survey, and we show that only 15% of respondents felt their organization was prepared for automation. So we've had a huge increase in the number of companies saying, yeah, we're ready for automation. When we look at the specific industry results we got, the energy sector is really ahead in terms of adopting automation. Obviously technology is big, but energy was up at 30%. And they're very prepared or fully prepared for full automation. We think about why the energy sector is leading. You know, we think that their industry is more hands off in many network management processes. Just because of the distributed nature of their environments. And they're probably more worried about managing and real time production issues. So when we dive deeper into automation, when we ask the respondents kind of what are they using automation for? These are the top categories, cloud bursting, configuration, compliance, incident response, policy management and workload management. A majority of respondents 53% are deploying automation for configuration purposes. And that makes total sense. There's a ton of manual effort required in doing configuration around networking. And it makes sense to automate those tasks. 40% reported using automation for policy management. And this is actually a very interesting step. More and more automation is being used for policy configuration. So whether you're getting your creating policy on a daily basis or you're modifying policy in real time. Let's say you're moving a network interface from A to B, or you're configuring different routes, all those policy changes are becoming increasingly automated. It's also worth noting that despite the rise of hybrid and multi cloud environments, cloud bursting is being automated the least for organizations. What we think about this is that the whole point of cloud bursting is to do so on an automated and dynamic basis. Our thought is that the networking components to enable cloud bursting are most likely already in place and don't need to change. So cloud bursting is a special enough use case that's not common amongst all these respondents. Now, there's two ways to look at it. One way people could just say it's already automated in my virtualization platform. Therefore, I don't need to worry about it. I don't think it's truly automated. It's kind of built in. The other way to look at it is to say, yeah, we're actually using additional automation. I think it's a mix of both. Then when we get into machine learning, we know that machine learning is growing in importance for network management. So when we take a look and we asked everybody their stance on machine learning and overwhelming 65% of respondents said that machine learning is now extremely or very important for network management. That represents a 20% year over year change. We asked that same question last year was only at about 40% or so. It's a huge increase and our take in our analysis of the data and based on conversations with lots of people in the network industry is that this increase in adoption of machine learning is really driven by the pain experienced in trying to apply and scale manual processes. So I see another question coming in Phil. Let's see if you want to take it right now. Yeah, sure. So it's a little bit long. I'll read it. What are the major concerns? Is that a simple mistake in a single network configuration? For example, default route or something could bring down an entire macro network. What kind of tools or mechanisms can we adopt to make it foolproof? Well, maybe I'll stop there and see if you want to save that one or take it now. Yeah, I think that's a great point.  I mean, we've seen horror stories of VM where administrators in kind of accidentally knocking out thousands of VMs through the push of a configuration script. Same thing can happen in network configuration, especially when it comes to route information.  You know, I would say personally, things like having two levels of approval to implement changes are making sure that you have someone check your work before you issue it. Those kind of processes are always good to have, whether they're manual or automated. I also think that there are some things that, you know, when you're talking about scale or operating a production, maybe they shouldn't be automated. So automation really needs to make sense for your organization. So, and how you apply it depends on your level of risk. Do you want to take the second part of the question, Phil? Yeah, yeah, so there's a there's a discussion about, you know, we do a lot of manual verification of a config today.  Is there something similar we can do in the network world before pushed to production? Yeah, I think that's actually another great question. So being able to kind of forecast what your configuration changes are going to look like before you actually implement them. I think that's a great way to approach it. Well, like I said before, I think it's also good to have more than one person be able to validate configuration changes. And again, I think it also depends on your environment. So I think using a test suite, or, you know, in your platform being able to kind of forecast changes or even pause changes before you implement them, just to get them validated is a great step. Okay. I want to jump in quickly now and talk about AI ops. So we talked before about how machine learning adoption is really increasing across the board, especially when it comes to folks working in cloud. The reason for the increase really comes from the increase in number of manual processes that are out there and the complexity associated with them. So having a platform that can help you make sense of all the information is really critical. And this is how we get into AI ops. So first, a quick definition. AI ops is a category and a term created by Gardner. It first came out in 2017. And in last year in November, they produced something called the market guide for AI ops platforms. And their definition as is as follows AI ops platforms enhance it operations through greater insights by combining big data machine learning and visualization. And they produce this great diagram that basically talks about all the data coming in, whether it's historical or real time, funneling that through and correlating it and making an applying context to logs metrics wire data and documents. And then a continuous process of observation engagement and acting using big data machine learning produces historical analysis, it improves anomaly detection. It improves performance analysis and it greatly helps with correlation and contextualization. Gardner has thought about this particular category and applied it to network management and has come out with this with a recommendation or at least a forecast that says by 2024 60% of network performance monitoring buyers will require improved AI ops capabilities. And this is up from 30% in 2018. So we can see that this trend of greater complexity, greater embracing and implementation of machine learning is driving a need for AI ops. Now one of the surprises that we got from our survey was when we asked all the network professionals that we talked to about whether they're actively using AI ops today. The majority of them said they're prepared for full network automation and 65% machine learning is important for network management. AI ops adoption is in the early stages. In fact, only about 10% said that they were using AI ops today. So this is something that we found very interesting and we found about it. We tried to figure out you know why if the need is there, why is AI ops adoption kind of relatively low. Well, I really, you know, we think about AI ops. It's really a collection of capabilities inside a platform, you know, and we see that while it's there, the platform availability and the platform adoption is something that we think is going to increase. And we think that our prediction is that more and more network professionals will turn to AI ops platforms to be able to kind of resolve some of the issues that they're having with the increasing network complexity. So quick overview of Kentic. Kentic is AI ops for network professionals. We provide revolutionary analytics to make every network excellent. We have an AI ops platform that takes information from context and labels geolocation threat data routing and business. We incorporate traffic and metrics using net flow and s flow and SNMP VPC flow logs, lots of data for coming from the cloud. And we provide from that queries and insights in an automated way and actions through an integration through lots of different integration with with different vendors and platforms. We're a SaaS based platform. We can function at any scale. We can work with every network and we provide all this information and insights in real time. We provide a unified management platform for diverse infrastructures cloud when SD when traditional data center, all these inputs. We deliver interaction through automation and notifications and allow you the ability to query and investigate your network. So looking back at the survey. Let's go over some of the key findings and some of our recommendations. So first of all, it's a cloud centric world. Again, everybody on this call knows that and we appreciate the CNC F giving us the opportunity today to talk about AI ops automation insights in relation to the cloud. We know that running today's networks is dramatically harder and everybody out there is really having a hard time in many ways trying to keep up and also think do things like prevent outages while also helping the business succeed. We know that adoption of machine learning and automation are both on the rise. And we also know that insights and automation restore manageability. And with that can tick powers up network teams with AI ops and we invite everyone here to download our report. You can get the link will put it in the webinar. It will also be in the presentation that's posted on the CNC F website to take a look at more detail and you can get a lot more interesting insights from the report is including stats around adoption of cloud and multi cloud by industry. So Phil, I'll turn it over to you to see if we have any more questions. Sure. Yeah, thanks Andy. Great presentation. So we've had a few questions kind of interspersed. While Andy presented, we definitely have plenty of time if someone has additional questions so we can, there's nothing open at the, at this very moment. So we can see if anyone dropped something in there. But I'm sure you know if there's other ways people can get in touch with you I know this recording will be online. As well but actually we just had a question is your platform already integrated with past solutions such as open shift. Yeah, I think that's actually a great question. So we talk a lot about orchestration and the importance of integration with orchestration platforms and platform as a service capabilities. Such that you can kind of automate a lot of the insights that we that we export and conversely in just a lot of the context that comes from platform as a service and also the related tools. So for example, information from like labels and tags that come from the cloud infrastructure. We do this today through API. So our platform is fully programmable and you have the ability to program it through API ingest or actually export data out. We've got another question. Do you have your own probes for us to install and an on premise implementation or you or you can work with existing probes. We do have the ability to deploy agents. We do have the ability to deploy our platform. It's available in both a SAS and on premise version. We have the ability to work. There was a question talks about routers. I'm not quite sure of the question there Phil maybe if you want to try. It may be connected. So there's two there. Can we have a demo of your tool. And then it says in routers networks. I don't know if that was meant to be connected. Well, I think the answer is that, yes, you can absolutely have a demo of this tool will capture your information and we'll get we'll reach out to you to set something up. And in our demo we have the ability to incorporate data from your network your own routers and then allow you to interact with the platform and see your data. Hopefully that answers that question. Great. Thanks Andy. Yep. So, yeah, so we've, we've cleared out the Q&A. I think we'll. Yeah, it sounds like Josh. Also, we can collect that name for you as well. Another great in a demo. Yeah. Yeah, great presentation. If anything else pops up in the next 30 seconds will catch it otherwise. I know Taylor and the CNC F will handle get this getting this recording online along with the slides, which as Andy just said has some links there at the end for you to follow up if you want more info. So yeah, thanks so much everyone for joining today's webinar and have a great day. Yeah, thank you everybody.


Okay, so we'll get started. This is the Development Review Board for Burlington for August 17th, so to get to December. And this is a mostly Zoom, but not entirely Zoom meeting. We will take up items that they are on the agenda. And when we call each item, Scott will be admitting people to participate at that point. And when appropriate, some of the items that we have to swear people in on, we will do that at that point. Also, when people are going to participate, we ask that they give Scott a mailing address so they can follow up for party status or other issues. I guess we'll go right into the agenda. There are no changes to the agenda. Is that right, Scott? That's correct. Okay, well, communications. I think there were some updated plans for the May 49 Main Street that were posted today. Yeah, UVM, and I think there was some updated info for the sketch plan as well. Okay, that's right, some other surveys, I think came through. Okay, well, minutes, I think posted too, let's see. Posted after the last meeting. Oh, okay. Got a couple to sign. Okay, thanks, Allie. Okay, if you can review the minutes that are posted from last week's, with last week's minutes, last week's meeting, I mean, if there's any comments, let me know. Then we will go right into the public hearing. First item is 92 Farrington Parkway. This is a continuation, I think, from a previous hearing. And I see the applicants is here. Is anybody else here to participate on 92 Farrington Parkway? Anyone on Zoom wishes to speak to this? Raise your hand. And I can enable you to speak. Are there any speakers to speak on that now? Looks like just the appellant, Brad. So, Brad, you can speak. Ray Ingram, I just swear you in. Do you swear to tell the whole truth and nothing but the truth on the pain and penalty of perjury? I do. Okay, so you're back. I believe you have some signed affidavits. Is that correct? Yes, I did. I got the documents. She said you needed, and I didn't know what you needed earlier. And I appreciate you giving me the time to get that. So, I have a question. Is this your Scott, or? Yeah, right. So, Ray, I just wanted to ask Scott a question, if you don't mind. So, if I understand correctly, there was a notice of violation, but when the applicant was informed that he was in violation, he moved the van to not be in violation at that point. The warning letter went out in October in 2020, I believe, and the vehicle was moved in March. So, if I, I'm just trying to understand the timeline here. So, we have affidavits now that show the 15 year continuous. And the staff's position is that since, if I understand this correctly, that since he moved the vehicle at the point he was told it was in violation, he lost his 15 year non-continuous use. Is that, am I understand that correctly? That's our take, and I believe it was AJ who pointed that out at the April hearing that he's corrected it, and it seems to remain corrected. Brad, that's right. I don't know if you can hear me. Yeah, I can hear you. Yeah, that's right. I mean, that was something that we brought up. I was like, wait, is it corrected? What do we have in front of us? So, Ray, did you follow that to some extent? Only one of final one came because the complaint was in October, the fall of October. Right, and the issue was that you moved the vehicle so that you were- Right before our first meeting, yeah, in April. Right. Not until then, and I was working on it. So, April, April, May, June, July, August. So, it's not exactly six months, right? Is it 60 days though? That was the- So, 15 years, 60 days, a non-conformity of the year. What was that? The issue was that it's 15 years without continuous use and that if you don't use it continuously for 60 days or more, it's deemed not continuous. And what was pointed out was that if you moved it in April, and I'm entirely sure I'm comfortable with this position, but if you moved in April because of the violation, then you weren't continuous. You had a 60-day break, more than a 60-day break. Yeah, this one's a little strange to me. I mean, you know, I think it came before us not in exactly the form we thought it should be in, and we asked for additional information and it seems like it's part of that. We've gotten the information we wanted in the form of affidavits saying that there was 15 years of continuous use, but Ray was trying to be responsive to the violation notice and corrected the violation in the middle of the proceeding. Right. So I'm not entirely sure what to do with this. I was the one who was asking for something more than the signature of neighbors because they were unclear. I think the affidavits are much more clear about the 15 years of continuous use. And we do have signed affidavits now, notarized. I have a question for the appellant. Like, what is your goal from this outcome? Is your goal to have parking in this location or is your goal to have the violation go away and not have this be an issue anymore, or both? I think if my goal is to park there, both is gonna have to happen. The way you put the question, my goal is to park there. And the only reason I... The second part of your question, please. Yeah, I mean, I think that you have addressed it, that obviously you want the zoning violation to go away, but you moved the vehicle then in response to the violation because that was your understanding of what you needed to do until this was worked out. Is that right? I waited till April to move it. The violation was reported in October. I believe it was October. Yeah, so, and I was also working on it. It was easier to work on it when I moved it away from the fence. I've been parking my pickup truck there too, off and on since I moved it. So you've still been using that space as parking? Yeah, I have. Since April. Correct. Off and on. Was there a period of 60 days or more where there was no vehicle there since April? No, matter of fact, there wasn't a period of 60 days or more where that van wasn't there. The vehicle you see in the pictures, never. It can probably wasn't more than three or four days. If I moved it on the driveway, I put it back over there afterwards. So the only time it's been moved is, well, since we were undecided in April and I didn't know the outcome. I got it running and moved it. I felt like moving it back. So I'm not, I kind of, the 60 days, I suppose I should have tried to hustle up and get the affidavits quicker. Because that's kind of where the 60 days are going from. Well, we have the affidavits. I think this might be in our court to talk about a deliberative, I don't know, are there more questions that we have for the volunteer? I'd like to use it because another reason is the garage is too close to that fence by the ordinance. Yeah. So that reduces the billability of the driveway. Yeah. Are there any other questions from the board for the applicant here? And Ray, I think this is on, we need to discuss. We see here affidavits, they seem to cover the period that it's supposed to, they're notarized, that's helpful. And I think we just have to discuss this at the end of the meeting. Okay. Okay. Thank you for hearing. Okay. Well, thank you. Thank you. We'll close this public hearing. Okay. The next item on the agenda is 64 East Avenue. It's a two lot subdivision to create, creating one new single family building. And is the applicant here for this one? Right. It's one of them. Yeah. Matt and Doug Gillette. So Matt, you can speak and Doug, you can as well. I'll do a screen share with your round. Is there anybody from the public wanting to speak on this one, Scott? So raise your hand and zoom the folks here in person aren't speaking to it. Can you guys hear me by the way? Yeah. So it's just the two applicants. Yeah. Okay. So Matt and Doug, if I could swear that you two in, that you would swear to tell the whole truth and nothing but the truth on the pain and penalty of perjury. I do. I do. Okay. So if you want to present what you have on this, that would be great. So I'll do an overview if that's okay, Doug Gillette. Yeah. From Lamarrow and Dickinson Engineering, 14 Morse Drive S extension. So this project is a two lot subdivision on a property with a street address of 64 East Avenue. The existing parcel has a house on it, fronting on East Ave. It's got a driveway coming off University Road and it has sewer and water services on East Avenue as well. It's in the RL Zoning District and it's approximately 12,400 square feet in size. The proposal is simply to split it almost in half to create one new building lot, which is seen as lot two on the plan. So lot one would contain the existing single family home and the driveway in the garage and be 6,036 square feet. To meet the coverage requirements, portions of the existing garage and driveway are proposed to be removed to get it within the maximum lot coverage as well as having the garage meet the new setback to the new property subdivision line. Lot two is proposed for single family lot, single family house, 6,406 square feet. Its access is also proposed to be off University Road. It has, we're connecting or proposing to connect municipal water to a water main along University Road and to connect municipal sewer to the West across University property to an existing city sewer line. I don't know, in a nutshell, that's about it. And I will stop here and oh, I guess one other point of clarification. University Road is privately owned by the University of Vermont, it's not city owned. So the applicant, Matt has obtained an access easement to be able to use University Road for lot two as well as utility easements for the water and sewer lines. He's obtained easements for that as well from the University. Matt, did I miss anything that you need? I think that's about all of it. They should have a copy of the easements as well, if needed. One minor point, I went through the staff report it all looks in order. One minor discrepancy, there's some lot coverage calculations on page two that are slightly different than what show on this plan sheet one. And I think that just represents that staff was provided an earlier version, slightly different than what we're looking at now. And Ryan, correct me if I'm wrong, maybe whoever wrote the staff report might have been referencing a slightly older version. Sounds accurate. Okay. So the new one's got the correct lot coverage that we're looking at right now. Yes. Yep, so long as it doesn't exceed the 35 and 10% bonus for the amenity structures on lot one, you should be fine. I think you were pretty well in the clear the first time around in whatever change I don't see much with regard to the lot lines that would affect the lot coverage in a negative way. So it would be leaving the how much of that slab gets removed to address your coverage issues if you have any, is that right? I mean, I'm the existing property of removing for setback reasons, but also maybe a lot coverage reasons. That's right. Yes, there's a lot of hatching going on but right there's about half the garage structure is going away. The structure itself is going away. Some of the concrete slab underneath that will be retained for storage and such. The gray area is the portion of the paved driveway that is also going away, one to bring it into compliance with the 18 foot minimum width. And coincidentally, that area also brings it slightly under the lot coverage requirements. Okay, so Brian, do we have those corrected numbers? That I'm trying to verify. I didn't realize that I didn't know that they were changing from the first plan that I saw and based my staff report on this, Vanim can't pull up the ability to pull the staff report because my internet's not working. Yeah, and the plan blown up, I guess. Well, we can ask for verification in the conditions of approval, Brian. Thanks. Okay, any questions from members of the board for the applicant? I don't see any, okay. Anything else that the applicant wants to add at this point? So I don't know. So we will probably deliberate at the end of the meeting tonight. Okay, thank you. We will close this public hearing. All right, thank you for your time. Thanks. Okay, the next application is actually 489 Main Street and 184 94 South Prospect Street University of Vermont. And I see the applicant is up. Is there anybody else who's gonna speak on this side? Scott? Well, Lani, who else should be speaking tonight as a part of the applicant team? And the second part of that question is, do you want to present or should I just screen share? The team with me tonight is Cheryl Dowling from SAS Architects. Scott Goodwin from a physical plant department at UVM. Derek Reed from Krebs and Lansing. And I believe Luce Hill is also here. So that's the entire team here. Okay, you can all talk. Need to present, let me know. Otherwise, I'll just screen share. Any members of the public, Scott? We do have some folks here in person to speak. And I know Sharon Busher wants to speak as well. She's on the phone. Okay, so the two folks who are there, Sharon Busher on the phone and the five members of the applicant team, I'd like to swear you all in that you would tell the truth and hold truth on the pain and penalty of perjury. I do. I do. I think everybody has it. Could Cheryl Dowling? Can you hear me? Yes. Okay, hi. Okay, so I just wanted to say that this is a project that is part of a larger landscape and building removal project for the university. A plan is to beautify the area that is one of the first views on campus, for students who are considering UVM as their potential cognitive choice. So it's part of a larger story of both making improvements to a sensitive and important area of campus, as well as fitting in with the university's overall historic preservation priorities. So you may know that we did some prior work in combining the lots so that we could have a comprehensive unified project. The other thing I'd like to say before we get into more of what the project is about is that we reviewed staff recommendations and we support those recommendations. Cheryl, would you like to take us through the project? Sure. Well, we are, I mean, the goal of the project is to provide an inviting accessible pedestrian friendly and just plain enjoyable experience from the moment of perspective, UVM student comes to campus with their guardian or parent, parks their car, makes their way to the admissions barn and here's the information that moves through to campus. The current path that students have to take to do that is really lacking in terms of what is offered at UVM and I think this project is really addressing that. But there are a lot of other pieces that are sort of tied into that. So current students, can you see my mouse? Am I presenting or is somebody? I'm presenting, Cheryl, if you want to, I can let you or I can just screen share. Okay, so I can't, okay. So could you go to SP 1.0, which is down maybe four or five, yeah, let's get some, almost there, get in there. You'll see some green, so that's a good sign. Maybe that's, yeah, that's probably a good place to start if you want to do full screen there. So the admissions barn, can you give me control so I can point or? If you want, Cheryl, hold your breath for 20 seconds and we'll switch this around, all right? All right, sorry. Okay, Cheryl, you can present if you wish. You need to do the share screen. I do. Yep. Okay, maybe that's not possible with my, wait, I got it. Many of us have the plans up, if you want to show us, just direct us to where to flip through to. Okay, so I thought I'd be able to do this quickly. Let's see, it's telling me I have to leave the meeting and come back to it, so. You're in as a panelist now, Cheryl. All you need to do is have the plans up on one screen with the Zoom and then you do the share screen, the green button at the bottom, or I can go back to it. Sometimes on Zoom, it is necessary to leave the meeting and come back to be able to share. Hold on, maybe it'll work. Can you see my screen now? Yep. Awesome, okay, thank you. Thanks for being patient. So currently the admissions barn sits right here and folks have come to campus, come down Prospect and come into this two-way driveway and park here, close to the barn and here.  So it's not accessible. There aren't, anybody who needs a wheelchair has to once again come back at the front, gather, come down the driveway and gather with the rest of the folks. It's just not an equitable, equitable situation and it's not accessible. So what we did is we created a link from the admissions building through to campus. And by doing that, it's a path that anybody can traverse. We've added two parking ADA parking spots here in addition to the ones that are already in the spot. So folks can park in this newly created parking lot and the Allen lot, come up to the admissions building and participate fully. We've got spines out from this main walkway into the parking area. So we park in this area, you can come up to the building on a walkway that's fully landscaped and be safe basically from cars that are coming through that space. We disconnected these two parking lots to create that car free zone essentially. And we're taking the slot down total parking number from 149 to 146. So it's a minor reduction of parking spaces. Let's see. So I talked a little bit about how these lots were reconfigured. So we added park, well, one of the things, another thing we had is the Wadams Barn which is right here, these two are also historic structures had parking pulled up right against it. We pulled that away when we had, and so we had a creation of green space as we, and then there's also a strong connection now between this lot and the admissions barn which wasn't there before. So anybody can park here or here, have a safe pedestrian and accessible way to get to the barn. They can park in this lot, come up through the space or here as well. Just changes the whole dynamic of the pieces of property that we're touching here. Additionally, this is where 172 was located and there were two driveways out to prospect that we're now removing and adding a pedestrian way. So you can still get out to the city sidewalk if you need to be, but just really pulling all that driving parking, excuse me, all those driveways away from the buildings. And then we also added a sudden, an electric charging station, double charging station here as well. I think it's the second one in the slot. Third thing we did was landscaping this entire space. I mean, we're trying to create an area that people can truly enjoy when they're walking through the space. There's a birch grove here and we're continuing that through this space as well. All these historic buildings, the barn, Wadham's house and Wadham's, excuse me, Wadham's barn and Wadham's house all have plantings, seasonal flowering and leaves, alternating season. So there's always something blooming. We've got a screen hedge here that creates a lawn space with some tall grasses behind. So you're screening the parking and creating a pause point if people wanted to stop. Benches and then in the Pomeranian barn area, we have the plaza, which is more of a destination for admissions where folks come and they gather their benches here and there's a row of trees for shade and trees here with some other round granite benches for folks to sit. And that's where you can gather for presentations before people enter campus and go on the tour. Another piece of that landscape was the UVM arch. We've shown it moving from, if well, this piece of property is the city of Burlington's and if UVM does obtain it, the arch which is currently located down here on UVM property will be moved closer to Main Street and really act as a gateway to, between Main Campus and Redstone Campus. It works from the south as you enter in and also from the road, you're gonna be able to see it as a sort of placard, as demarking where they are. Lighting is also part of the project. We're adding walkway lighting, which is the historic lantern type design typical of UVM campuses along the walkways. And in the parking lot, there's more of a pole and shoebox type design fixture that is also standard for UVM. I know in one of the design review comments that we've gotten was that the foot candle levels were a little bit high. We did a little bit of adjusting and got those down to 0.5 and below on that latest set of plans you'll notice. The other comment we were addressing is there was a setback, a hardscape setback along this property line that we changed in this concrete in this corner. And we think this is what someone was referring to. We're gonna make that green space and pull that hardscape back from the property line to make that work. So let's see, so I guess the last thing I kinda wanted to touch on is that we've been working closely with Vermont Division of Historic Preservation when it comes to the Pomeray Barn and how to demolish that and also the 172 self-prostate. And they're fully, they've approved that work and we've been working with them on mitigation as to that we're gonna document it and prior to taking it down. And then in addition, the two other historic buildings on the property, which is the Wadams Barn and the Wadams House. Wadams House is currently undergoing some repairs and repainting foundation work to really restore that back to a better maintained building and the Wadams House as well is slated for a full exterior restoration next spring. And we've been working on those plans as well. So I guess in conclusion, I guess between the demolition of the two buildings, creating new accessible walkways that everyone can use, reconfiguring the parking, providing new lighting, restoring historic structures and landscaping the entire area. I mean, I think this is a project that I'm really excited to see this portion of campus, transformed into a place that, the university community, the prospective students and existing current students can really use and truly enjoy just was really a transformative project. So thanks. And can you just explain one thing as long as you're on the site plan as to the property line that you're talking about relative to the arch in the city? Sure. This right here, this North South property line separates UVM property from the city's property. So currently as this line comes down, the arch's current location is right here. And we're proposing to move it up onto this, into this location. Is that the new property line you're proposing there? You've got a property line that sort of runs parallel with the walk for ways. This is a bubble showing the area. No, there's another line there that looks like it's property line. This one? Yeah. I think the property is a triangle. It's a small wedge. So I think this is... I believe the line that you're referring to is a fence. Oh, that's right here. Yeah, that will be the property line. I haven't seen it. Can I answer that? The property line to the east of the triangle has not been determined yet. So we don't know that yet. I think Scott's right that this is a fence currently. Yeah. Okay, thank you. Yeah, so Alani, is there more that you wanna be presenting? Well, like I said, we accept all the conditions. We've already addressed most of the conditions actually. The property line adjusted, the property line negotiation with the city is ongoing. It's probably not gonna happen right away. We're going to move forward with the project prior to completing that negotiation. And when we do, I've already been informed that we'll need to get another zoning permit for the arch, which is what we'll do. Okay. Okay. It looks like a very nice project. Some of the detailed landscaping is quite nice and rich in a lot of ways. Are there questions from the board for the applicant? Seen anybody with any questions here? Quietly forward. No, our review, I mean, the review is really focused on exactly what you're presenting though, the landscaping and the site plan there. And I think that the drawings are fairly explicit in terms of what's been presented. So you're gonna maintain two driveways off of Prospect Street. Is that correct rather than three? Lonnie? Well, we're getting rid of two driveways. The main driveway that Cheryl is showing, those are the two driveways that are gonna remain. Right, right. And that both, if somebody's coming to the university and wanting to go to admissions, both of them will get them there. Is that the sign that you're gonna show that or is one of them favored in the future? They can both get you there. So they're both labeled that way? Yeah, they're both accessible. Okay. So aren't any other questions from the board at this point? I'm not seeing any. I know there's members of the public here who wanted to speak. Scott, you mentioned there's two people who are present at the... Two folks in person and Sharon Bush was on the phone, on the line. And who is it that's there? I miss what you just said. We have Barbara Hedrick in person and... Nelson. Nelson, well, I like Nelson. Okay. How about if Barbara Hedrick is first? Can you let her speak? All right, so let's start with Sharon. Okay. So Sharon, you're up. Yes, hi. Good evening. I understand. I appreciate DRB and the staff for facilitating or trying to facilitating a meeting that has public presence and then people remotely participating. I know that's no easy feat, so thank you. I wanna speak in support of what looks like a beautiful plan. There is one thing that is incredibly troubling to me and it's addressed in the staff comments and the DRB can't do anything about it, but I do want to just state that it's of great concern to me as a resident of Burlington to have a residential structure torn down and not have an entity responsible for the housing replacement ordinance. I know Article 9 doesn't allow us to do that with the University of Vermont, but I just need to state that since they create so much stress for housing, it seems ironic that they can do this without replacing or contributing to a fund. And I find that frustrating and I just wanted to share that with you and plan to try to go to the legislature to have them look at this again because it doesn't, maybe it made sense when it was first brought forward, but I don't think it makes sense anymore with the housing crisis that the country is in. The other thing, and I know this isn't a, I can't ask a question, but I wasn't clear about this. With the land negotiation where the arch will be, I heard Lonnie say that they would have to come back for approval for the arch. Would that be administrative or would that go before the DRB? And maybe that could be referenced in writing as you discuss it and I can read it, but that's just a question that I have. So that's it. I think the project is as usual well thought out and well planned, but I have great concern about housing replacement. Thank you. Thank you, Cheryl. Barbara or Nelson? I'm going to call you the next bit for the next one. I want to sketch my end. Oh, I take that back, Brad. It looks like folks are in person here to speak to the last one. Oh, of course you already won that for the public. And can you answer the question on that, Scott? Or is that? If it's just the arch being relocated, that would be an administrative permit. Okay, thank you. And I guess I'll ask Lonnie one question too. That is at 172, is that the right number? Is that currently, what's that building currently used for? That building originally was a residential structure. It had been used for a few years for visitor, visiting professor, housing. It's a very small unit. A few years ago, it got damaged accidentally. So it's actually not usable. It hasn't been usable for a while. So it didn't make any, it was not repairable. It has deteriorated. Animals were using it. So it's not like it was a useful, it wasn't really a residence for the last few years. Okay. Thank you. Okay, unless there's any other questions for the board, we will, thank you, Lonnie and the whole team there. We will close the public hearing. Thank you. Thank you. Thank you so much. So the next item on the agenda is four different lots on Elbow Street and on North Avenue. Is the applicant here for that one? Hey, Brett, I have to accuse myself in this one. Okay. I'm gonna stick around for deliberative later. Great, thank you. They have the applicant or, yeah, the applicant James C4. James, is there anyone else speaking to us tonight with your applicant team? Yeah, Doug, sorry. Doug Hansen from LEMRO, Dixon. Oh, that's funny. I see Doug with an ace. Looks like Doug, hey Doug, I'll get a dog. And then the two people who are there, are they there for this application? Yes, definitely. Okay. So four people, can I swear you in that you would, oh, this is sketch plan. So we'll be a little later on this. So this is for a create, I guess creating the four lots there. And I guess it was some question about the lot sizes. And I believe that was clarified in a recently resubmitted survey. Is that right? That seems to be the case, yes. There's lot sizes were questionable there. I think that got resolved in that latest thing. Do you want to present this? Either James or Doug? This is Doug Hansen from LEMRO and Dickinson. Yeah. Also go by Doe, because I'm Doug H. So these are four lots, two of them front are between Elbow Road or Elbow Street and the lake. And the other two are between what we refer to as Elbow Road and North Avenue extension. And so the two that are between Elbow and the lake are both over 10,000 square feet and the other two are both over 4,000 square feet. And so what Scott's got up on his screen, or Ryan, I'm not sure who. So the lot one and lot two are the ones that I'm saying are over 4,000 square feet a piece and lots three and four are over 10,000 square feet. So the acreages, the areas that are shown on the table on the right hand side of that plan are correct. This, these lots are in an area that nobody and I'll say nobody because I spent days and days as have other attorneys. Nobody knows where those properties came from. There was a, we traced them all back to Anelizakowski or Kuzowski and, there's no evidence of any estate being closed or. So Mark Brodsky, who's the owner of 2751 North Miami Ave, filed a quiet title action to basically clarify where those property lines are. That quiet title action was resolved in let's see 2008 and the judge in that judgment clarified these lots to say this is where they are and this is how big they are. So that's, I know Ryan had looked at a plan done by Vermont land surveyors and that plan was taken into account but was essentially overridden by the decree. So we're very comfortable with the acreages, lot sizes that show on this plan and believe those should stand. And with those sizes, as Ryan mentioned in his staff report there's some setback questions because of the way setbacks are calculated down there. But for as far as the sketch plan is concerned this is just to show that the lots are there. The lots are that size and the lots are capable of holding either a single family or a duplexed row in respectively. The elbow street or duplex and the other ones are a single family, right? That's correct. Okay. And the topo information on this survey is that sort of light our general? No. No, actual survey? Yep. Yeah, this plan was done long before a lot there was considered something good. Okay, okay. And so this is sketch plan. So one thing that strikes me is just having a little bit more information on existing conditions would be helpful just for the actual final application in terms of understanding maybe some photos of the existing buildings and the adjacent properties and things like that that would be helpful just as part of the application. Sure. And obviously more information on the buildings proposed but that's not necessary at this point. And the survey that this one is is from 2000, I'm looking at the date right now. This drawing is from 2021. Is the drawing that's in front of us? Is that the latest survey or this is based on the 2016 survey? This is based on our survey, which we did in 2000, the property lines are based on our survey, which we did in 2016, which is the plan that the judge issued his order on. And just to understand what's being presented there's a lot of the connection between Elbow Street and North Avenue. Is that a street there that's shown on this? Next to your North Avenue, got one. You could generously call it a street. Yes, it's really, I'll be honest, I hadn't been down there in about a year and a half, but the last time I was down there it was more packed dirt than anything. And is that how one accesses this property though? Is that the path? Yes. And again, that connection on the north side of lot one, that was a vacant parcel that nobody had any idea who owned. And so the judge said that my client can use that as access. And the north side of lot one. Yes. So lot one, let's see, how do I describe this? Yeah, above lot one as you're looking at the plan. So your client uses to access the other lots, is that? Yes. The Elbow Street lots, yeah, okay. Because there's no empty space between Elbow and North Ave other than that. Well, other people must use that same connection, I would assume. They do. Okay, good. And I guess we're not concerned about the adjacent properties and their setbacks. So, okay, other, you know, a sketch plan seems, if we believe all the setback information, it seems pretty straightforward. Lot coverage would become an issue for all these lots, but you can address that and the actual plan that you have. Again, we will stand behind the coverage that shows on this plan. Well, we wanna see the buildings and everything else that goes on with it so that- No, I understand that. But the buildings that we're showing in the driveways and the parking, as they're shown on this, allow all four of those lots to meet the coverage requirement. Right, okay. We just have to look at that in some kind of detail. And obviously the actual buildings themselves, but- Certainly. And that will be part of the actual application. Other questions from the board for this applicant? Any concerns about this? Can you explain some more about, I guess this is Elbow Street that is on the property of lot one, two, three and four? Is that right? That's correct. Yes. And so that currently exists within the setback. Yes, that's correct. Okay. And that access, so to speak, continues to access the property to the south of your lot four. Is that correct? No, they do not use that because they all, in addition to the building directly south of lot four, they also own the building to the east of that. So they use North Avenue for that. Correct. And my client has a letter from them saying that he can connect all four of those properties to Mr. Brown's pump station, which is that circle that's between the two buildings, which is how he connects to the municipal sewer lines. It pumps up and across the old rail trail and connects into a manhole just on the far side of the tracks. And power, how does power get to this, these properties? There are a series of poles down through there. As you say, unfortunately, it's a little tough to see, but there's a pole. Are they on your drawing? Yes. Is he sewer? Yeah, no. So how do I describe where they are? Beautiful. Oh, okay, I found, I'm blowing up the plan here. So I think really just next to the shoreline on lot two, like there's a power pole right there, but it looks like it's in the middle of the street there. It is. It is in the middle of the street. Well, it's in the middle of what could be a right of way. It is in the gravel. Okay. And that's serving the adjacent properties, it looks like. As well as the buildings on lots three and four, yes. And it's trying to figure out where the lines come from. So that's coming down Elbow Road overhead power to that pole. Correct. And then serving the last, this property and the property to the north. The several properties to the north, that's correct. I mean, typically we would, I mean, things low question was to say that power is supposed to underground, but that's sort of what the ordinance for new property. So would you be proposing and move that pole? So it's not in the middle of the street? We would need to, yes. Okay. And that pole is gonna provide for all four of these houses. Is that correct? No, lots one and two actually could be served. There are poles along North Ave extension as well. So they could be served off of that. And is it gas out here? I do not know the answer to that. Okay, so those are some of the questions asking about how the utilities serve these buildings are the discussion and the final understanding how that works, it's an interesting plan. Okay. And obviously landscaping that also be an issue going down. Understood. And at this point, you're not planning to do anything with that existing concrete retaining wall that's on the lake front. No. I have no desire to open that permit process. Okay. And you get to be above elevation 103, which is that's pretty much the new flood plain, isn't it 103? I believe it's 102. Yeah. So what was that Scott? 102 is the base flood elevation. So 103 is out of it. Okay. Okay. Good. Any other questions from the board on this? Okay. Any other questions that the applicant might have on this? And we have two people who are there, Scott, who wish to ask questions or participate. Can you- Yeah, I can sit there. Is that the screen over here? The screen over here. You can use that computer and I'll slide this. I don't know how you- You can just sit there and it should be on. If you can just introduce yourself when you speak, that would be helpful. My name is Janice LaPlante with the E of the N. And you can address- I'll mute that one so we can make feedback. Oh, all right. Can you hear it? Can you hear that Brad? She wants to speak up into this. This is the microphone essentially. Janice LaPlante. Yeah, I hear that. And if you can just give your address that would be helpful. Okay. Well, we go by 3211 North Avenue. Okay, great. So right nearby. Right next door. Okay. So the floor is yours. I just wonder if they're going to do one duplex and tear down that two houses that they're empty. One and two, I think on the lake shore, they got two buildings. They can do duplexes on that lot, on those locks. That's what they're- They're planning to make in four sets of duplex. Two sets. Two single-family houses and two duplexes. That's what the proposal was showing right now. So on North Avenue, it's two single-family and all of Elbow Street on the lake, it's two duplexes. What they're showing? Single-family, single-family, those two, and duplexes. So they are going to fix it up because they have done anything for years. I suspect they're tearing everything down. Okay. We'll ask the actor. They're not going to fix the walls. From the lake to shore, because that's falling down, but... The applicant said that he was not looking at doing that at this time, the seawalls or the lake walls. Move some of the trees. Well, they haven't come back with a landscape plan, so I'll have to- Apparently, they're dying anyways, but I just mostly came here to see what they're planning on doing because they didn't say very much on the favor. So this is just, you know, this is a sketch plan, which is a preliminary presentation. They'll be back and you'll get notice about that when they actually have more detailed plans. Okay, yeah, I came here for information, so. Yeah, yeah, well, I had you. I had you at any time, too, so. Yeah. All right, they were planning on four duplexes and two single-tips. Okay. That's the current direction to go again. When Abol Lane on our property is next door, on the north side, we own half the right away on some of that, so I want to make sure that's not interferable with it. Okay, and so which property are you to the north of what they're calling their lot one? Lot three. Lot three, oh, north of lot three, okay. Yeah, I'm right there. I see, and it does look like the right away does is shown over part of your property and part of their property. Yes. And that's how you access your property. No, we got a driveway in between, right away between Mitchell's and our property. That's the next one over. I see. Okay. So does anybody use Elbow Street now? Oh, yes. That's the people that used to own the other place and a couple of families, Mitchell's and somebody just bought the other place. So yeah, there's three or four of us that use that. Okay, okay, so it doesn't, I don't think they're planning to move it. Are you worried about moving it or anything else about it? No, I don't mind. Okay. They don't interfere. Yeah, in our section, our driveway. Yeah. Looks like the one thing that might affect you is if they move the power pole, they'll reconnect but it may affect your power for a day or when they move that pole.  Okay, good. Any other questions? No, thank you. And somebody else is there too, Scott? They're together, she spoke for the two of them. Okay, good. Okay, any other questions from the board on this one? Okay. I guess I have one other question for the applicant is the right-of-way for Elbow Road defined at all on this survey, is that definitive or is that just sort of an approximate location of it? That says the judge defined it. The judge defined it. That's the hatched area on the drawing. Yeah, there is no deeded, other than that decree, there is no deeded right-of-way with for Elbow Road or Elbow Street. Okay, good. The same can be said for North Avenue Extension from the tracks north. Good, if there's no other questions or anything the applicant wants to add, we will close this public hearing. Thank you, I guess it's not a public hearing sketch plan. Well, we'll see you back for the final. Very good. All right, and I think that's all we have on our agenda. Is that right, Scott? That's correct. Is it? So we will close the developer review board meeting and move on to our deliberative session. So I think AJ- The recording has stopped, is being recorded. Let's see, so on item agenda in front of me. Item ZP 21-136, 92 Farrington Parkway. I move that we grant the appeal and issue the 15-year determination. Got a second on that? Okay. Caitlyn, seconds it. I'm just curious, I guess for Scott, is how come the, on the, I'm just curious why the number is different on the staff report than on the hearing notice? Is there some staff report is 2106-290T? Am I just looking at different numbers kind of thing? Yeah, that's because this started in the old service system and I know it's in the new one. That's only different thread. Okay, so the ZP is the right one. Okay. Any other discussion? Okay, all in favor? Aye. Opposed? So it's 7-0. The recording is being recorded. On ZP 21-559-64 East Ave, I move that we approve the application and adopt staff findings with the added condition of aligning the lot coverage numbers with the staff making sure that that's there. Second? Keenan, great. Thank you. Any discussion? All in favor? Opposed? Okay. The recording has been recorded for both ZP 21-514 which is 489 Main Street and ZP 21-515 which is 184-194 South Prospect. I move that we approve the application and adopt staff's findings and recommendations or conditions. Second. Broke second. I have a question just for Scott on this. I'm always amazed when they have quick open permits going back 10 or 15 years on this. Yeah. So just... Yeah, more than 20 for one of them, I think. Does that really get tracked? I mean, they really do bring those into compliance. That's a condition. Yeah, we've really been tracking it for the past, oh, I don't know, three or four years. And so we're seeing a lot of these old ones get closed out. Yeah, that'd be nice. Okay. Any other discussion on this one? All in favor? Aye. No. Okay. And we're done. The recording has...


Hello and welcome to the International Daily Roundup where we bring you some of the top stories from across the globe. Let's take a look at today's headlines. Mexico's Supreme Court decriminalizes abortion in historic ruling. Palestinian security officers face charges for the killing of Nizar Banat. Mass protests against her Bolsonaro head across 200 cities in Brazil. Morocco holds elections as demands for political reforms continue and in the video section take a look at the necessary changes required in the public health response to COVID-19. Mexico's Supreme Court has ruled that criminalizing abortion is unconstitutional. The landmark ruling was issued in relation to an abortion law. In the Cuiwala state, the measure punished people for having an abortion with up to three years in prison including in cases of rape. The 10 judges present in the Supreme Court ruled unanimously that the law was unconstitutional on September 7th, while the decision itself is limited to Cuiwala. It has established obligatory criteria for all judges. This has paved the way for the legalization of abortion care across Mexico. It will also set a precedent for dozens of people currently imprisoned for having an abortion. An estimated 750,000 to 1 million clandestine abortions are performed in Mexico every year. According to L-Pays, at least one third lead to some kind of medical complication. Currently, abortions are legal up to 12 weeks in Mexico City, Ozaca, Hidalgo and work crews. Tuesday's ruling was followed by a demonstration in the state of Cuiwala, activists are now pushing for the complete legalization of voluntary abortion services. 14 officers from the Palestinian Security Services will be charged for the custodial killing of Nizar Manat. He died after an arrest raid at his home in Hebron on the occupied West Bank in the occupied West Bank on June 24th. Manat's relatives stated that he was badly beaten using metal bars and dragged away. An autopsy revealed injuries on his head, neck, chest, hands and legs. The PAs Independent Commission for Human Rights said that the wounds indicated an unnatural death. Manat had been a prominent critic of the Palestinian Authority government led by Mahmoud Abbas. His death sparked weeks of protests which were met with a violent crackdown by PA forces. Several activists and protesters were also arrested. The Manat family's lawyer told Middle East Thai that the assassination case had been referred to the military court. The family's request for the trial to be public has also been granted. The indictments include beating, leading to death with premeditated murder, use of torture and disobeying military orders. However, no indictments have been issued for higher-level officials such as those who issued the arrest warrant. Manat's family has said that they have no confidence that the PA will deliver justice. They have called for an international probe into the killing. Brazil witnessed another round of protests against President Hir Bolsonaro on Tuesday. The Fora Bolsonaro campaign estimated that 300,000 people took to the streets across 200 cities. September 7th also marked the country's independence day. The protests against Bolsonaro coincided with rallies organized by his supporters. The far-right leader had instructed his followers to march to Brasilia. Bolsonaro previously called the march a counter coup. He also targeted the Supreme Court during the rallies in the capital and São Paulo. We are not going to deliver our freedom to them. We are not going to deliver and not even give up our fight and our dreams. We are going to the end. Nearly 18 million people were eligible to vote in Morocco's parliamentary elections on September 8th. This is the country's third election since the constitution was adopted in 2011. This followed the country's February 20th movement demanding a democratic system. Protesters demanded an end to corruption and the separation of powers in the constitution that was introduced did not change the major powers given to the king. The monarch retained extensive judicial, legislative and administrative powers. The protest movement rejected the constitution and Morocco has witnessed low election turnouts since then. People have also pointed to continued corruption in the series of neoliberal austerity measures adopted by the state. The committee appointed by the king has also presented a new development agenda. The Bandar Network has also pointed to a decline in democratic freedoms including the targeting of opposition movements. Eight leaders on a democratic way organization were arrested during protests demanding democratization. The left-wing group had been mobilizing in several areas and called for a boycott of the election. It has argued that the elections are under control of the interior ministry and the king still holds sweeping powers. Several news and media outlets have also stopped publishing prominent journalists have been arrested and tried on allegations of human trafficking and assault. Rights groups argue that these have been used as a tool by the state to target independent journalists. And for a final story we look at a recent study on mask wearing to contain the spread of COVID-19. The research was led by professors from the Yale and Stanford universities in the US. It was conducted across 600 villages in Bangladesh, covering over 340,000 people over a period of five months. Researchers rolled out programs to distribute free masks and promote their usage. They found that mask wearing increased by 30% among the people encouraged to use them. Research has also reported an 11.9% decrease in symptomatic COVID-19 symptoms. Given that vaccine doses access still remains highly unequal, measures such as masking are important. While we have been planning and arguing about public health facilities for severely ill COVID-19 people, while we have been arguing about vaccine accessibility and so on and so forth, the one thing that none of us have argued about with any traction in public discourse is shouldn't the public health system in India begin be providing masks for use by financially underprivileged people in communities? And shouldn't those masks have supply chains of their own setup which are sustainable, which are biodegradable, which are reusable? All of these boxes can be checked. It's not that technologies are not available for this. It is that we've spent a year and a half with no traction about mask as a public health intervention from the state. And I think that this study underlines the pressing need. Let me make an additional science-based point. We all talk about variants. We all keep pointing out discussions about whether vaccines of one generation are going to be useful and to what degree in protecting against variants of the next generation. Masks are independent of variants. And yet we have not planned a durable public health policy intervention that incorporates mask distribution. Across the world, all scientific communities have said this. Vaccines are never going to provide 100% protection. Nothing is going to provide 100% protection. All vaccines currently provide more than 90% protection, quite surprisingly, robust protection against serious illness and death, even from the current variants, current crop of variants. There is no guarantee that this is going to continue into the future. But suddenly new generation vaccines are being developed and will be distributed. But the reality is vaccinated communities do not completely stop transmission of the virus. They slow it down, they reduce it, they do not halt it completely. As the Bangladesh US study points out for masks, masks again reduce transmission and are therefore a very useful, low-cost intervention, but they do not eradicate it. All of these COVID-appropriate policies and individual choices that we are talking about all provide incremental control over this rate of spread, the numbers hospitalized, and the strain that the public health system is put under. None of these eradicates or eliminates the disease. And therefore all of these become matters for the long term, become policy choices for the long term, and therefore the durability of these policies and the sustainability of these choices, such as with vaccine accessibility, such as with mask accessibility, become major issues for us to keep in mind. Again and again we've discussed this issue and I bring it up again. We need to get out of dealing with COVID-19 policies in the immediate acute crisis mode and think about them over the long term. And this is all we have for this episode of the International Daily Roundup. For more such stories and videos visit our website peoplecispatch.org, subscribe to our YouTube channel and follow us on Facebook, Twitter and Instagram. Thank you for watching.