The Brainerd Salvation Army is continuing its long tradition of supplying gifts for kids through their Christmas angel tree and their partnership with the Marines for the Toys for Kids program. This week the Salvation Army opened up the sign up applications to parents wishing to participate in the programs. Logan Gay has more. It's about time to get into the spirit of giving. The Salvation Army and Brainerd along with the Heartland Attachment of the Marine Corps League is now setting applications for kids in Southern Croain County wishing to have a Merry Christmas. Right now we're taking intakes for our angel tree program and we're doing the Toys for Kids applications. We partner with the Marines every year and so we've got people coming in and applying for Christmas gifts and the food card. Last year we gave out about $16,000 in cup gift cards. The Toys for Kids and Christmas angel tree sign up started on Monday. Joining a child up for the programs is very simple. So when they come here we ask that they bring their identification, some mail showing they're in our area and identification for the children.  The Salvation Army is also seeking volunteers for their Red Kettle campaign. We're looking for bell ringers at register to ring dot com so you can go right online and register to be a volunteer and ring bells for us. And if you don't want a Kettle ring by yourself you can choose to ring with your family or friends. I've seen a lot of families that do that every year go bell ringing as a family and you know teach their family the joy of giving back. The Christmas tree angel and Toys for Kids sign up will end on Wednesday, November 2nd. And Brainerd Logan Gaye Lakeland News. If requested the Salvation Army can supply businesses with their own personal Red Kettle. If you've enjoyed this segment of Lakeland News please consider making a tax deductible contribution to Lakeland Public Television.


But no That would be we could use CO2 we'll figure out what's CO2 that's that So remember this is going remember down the periodic table and then back up it so remember we went carbon had four right bonding pairs and So for electron pairs for bonding pairs no one right I can have four electron pairs You know three bonding pairs one long pair oxygen two and two right flooring one and three like one bonding pair three long pairs, right? We looked at four on what did it have? you guys remember three Bonding pairs and how many long pairs? Zero right so what would be the one that has two bonding pairs and zero electron? Be yeah, we're really Well, if you make sense if you look at the period table, you know, that's all this is doing going up and down the periodic table So if you're tearing your hair out in frustration, it's because You don't understand the periodic table. Okay, so just remember that you do understand And something like BE is going to have how many electrons we count up take one two So one two like that And then hydrogen of course only has the one I think it has the one Be each to so Is that got two electron pairs? Yes. Does he got two bonding pairs? Yes. No long pairs Linear what's its molecular gene? linear linear as well, right and This one is a linear molecule which we can have a bond angle for 180 180 Any questions on that one


The way we think can significantly impact the quality of our relationships. As philosopher Marcus Aurelius said, the happiness of your life depends upon the quality of your thoughts. So whether you're currently single and searching for love are already in a committed relationship. Cultivating the right mindset can help you navigate the highs and lows of love with greater ease.  Here are six mindsets to improve your love life. Let's go. Believe in your self-worth. One of the biggest obstacles to finding love can be a lack of self-worth. It can be all too easy to settle for less. Overlook toxic behaviors or push away potential partners when we don't believe we're worthy of love. However, studies have shown that having a strong sense of self-worth can lead to a more positive relationship and less conflict or breakups. When you have a positive self-image, you're more likely to attract healthy and fulfilling relationships. And you'll be better equipped to navigate relationship ups and downs. It can also help you to set boundaries that promote your well-being and avoid tolerating unhealthy behaviors from your partner. It's important to remember that you're inherently deserving of love and affection simply by existing. Remember to be kind and compassionate towards yourself and try to focus on your positive qualities rather than your perceived flaws. Self-love and acceptance are important steps towards finding happiness and fulfillment. Foster a growth mindset. Are you a firm believer in soulmates or the one? Even if the one does exist, there's no such thing as a perfect person. No relationship is perfect and it's natural to experience challenges and setbacks along the way. But instead of seeking these challenges as obstacles, try reframing them as opportunities for growth and learning. According to researchers Baker, McNulty and overall, having a growth mindset where couples adapt and grow together as they face challenges is linked to a closer and more positive relationship. A growth mindset also helps you focus on personal development and becoming the best version of yourself, ultimately improving your love life. Try to avoid placing your significant other on a pedestal. Instead, both parties should work together to build a strong and lasting relationship. The three C's. You always hear people talking about how communication is the most important thing in a healthy relationship. But what if you told you there are two other big C's as well? Can you guess what they are? Comprehension and compromise. These are all essential in improving your relationship with your partner. In fact, research shows that couples who prioritize communication are closer emotionally and understand and support one another. So make an effort to express your thoughts and feelings and encourage your partner to do the same. With that being said though, it's no use communicating if your partner doesn't understand or comprehend what you're saying. Your partner may be listening, but are they understanding you? Comprehension is just as important as communication. By understanding where your partner's coming from, you can actively work towards solving a problem. This will make compromising with your partner a lot easier, as you can understand your partner's point of view. In order to perform the three C's effectively, it's important to be honest and transparent, which requires emotional vulnerability with your partner. Embrace vulnerability. Do you tend to put up walls? Being vulnerable can be scary, especially when it comes to matters of the heart. You may even see vulnerability as a weakness. While it's natural to want to protect ourselves from emotional pain, psychology professors Harry Rice and Phillip Shaver have found that being vulnerable with your partner is actually a key component of intimacy and connection. So don't be afraid to open up and share your feelings with your partner or potential partners. Try to embrace your flaws and share them in a safe and trusting environment. It could be the key to a deeper, more fulfilling relationship. Practice gratitude. It may sound a little cheesy or cliche, but when we take the time to appreciate the little things our partner does for us, it can really help strengthen our connection with them. Gratitude is a powerful mindset that can help you appreciate the good things in your life, including your relationships. According to psychologist Amy Corden and colleagues, couples who have a grateful mindset have a higher quality relationship and are more likely to feel committed to their partner. Take some time each day to reflect on the things you're grateful for in your relationship. This can shift your focus away from negative thoughts or complaints, ultimately leading to a happy relationship. It's important to note that this does not apply to toxic or abusive relationships. Expressing gratitude to your partner is an essential part of a healthy relationship, but it should not come at the cost of ignoring toxic behavior. Remember a relationship without mutual respect is a relationship doomed to fail. A relationship built on mutual respect and gratitude results in long-lasting connection where both parties feel heard, appreciated, and loved. Cultivate empathy. Have you ever heard the saying, put yourself in someone else's shoes? That's empathy. Empathy involves actively listening to your partner, trying to understand their perspective and responding with kindness and support. When couples engage in empathetic behavior, it fosters a deeper emotional connection and helps them feel more understood and validated. Psychologist and professor Nathaniel Lambert found that couples who adopt an empathetic mindset when facing conflicts tend to engage in collaborative and constructive problem-solving rather than resorting to attacking, blaming one another, or becoming defensive. Prioritizing empathy and conflict resolution helps you and your partner find solutions and strengthen your relationship rather than causing further harm. Remember the three Cs we talked about before? Well, having an empathetic mindset makes achieving the three Cs even easier. So next time you find yourself in an argument, try to approach it with empathy by acknowledging and validating each other's feelings. Did any of these points surprise you? Mindset shapes our attitudes and behaviors towards those we love. Adopting the right mindset can greatly improve the quality of your love life. If you enjoyed this video, feel free to like and share it with someone you think could benefit from it. Thanks for watching. Until next time. And if you're hungry for more valuable insights and practical tips, make sure to dive into our captivating relationship video playlist where we explore a wide range of topics to help you build thriving connections and deepen your understanding of love and relationships. Get ready to unlock the secrets to lasting happiness. Keep watching and discover the transformative power of healthy relationships.


Hi, I'm Julien Spauber. I'm going to talk about my journey or my experience creating my first GTK application called Teleport. Like a year ago or so, I wanted to create a GTK application, but didn't know what actually, at least at the beginning. And then with a friend, who is actually a designer, we were in the same room. And we had to share a file. How do you do that? How do you share a file on a local network normally? Do you use Sambar, network share, own cloud, next cloud? Instant messaging? Email? No, you just give up. You give up. You speaky. Best way to speaky, I guess. Who does use speaky? I use speaky to share a file, the local network. I do that too. So we were thinking about how could we resolve that problem by connecting something like instant messaging to sharing a file, but not to have the file shared with a remote server to upload it somewhere else. Because most of the time, we don't have a really good internet connection, although it's not everybody. Yeah, in Italy, it's getting better. Whatever, we focus on the local network to have something like this, a push notification that you send somebody a file. I'm Julian, by the way, so I'm sending my friend a file, and he will see something like that. Julian's laptop is sending you a file MD as a markdown file, and he can accept it or reject it if he doesn't like to work with me, whatever. So yeah, we start to think about this. And so we can directly go to a demo, because it will be really quick. I did. Why are you not on my Wi-Fi? Yeah, the problem with this is that, do you see it now, that on public Wi-Fi, for example, many clients can't, normally clients can't talk to each other, luckily. And telegram doesn't work. Do you see it now? Why? Now? Let's start telegram, teleport. I confused those two. Maybe we should change the name. So this is teleport. We keep using the face quite simple. Oh, OK. I have, because before my laptop died, no, I can't do it from here. That's so bad. Can I do it? Can I use a pseudo like this? Oh, yeah, I can do. Oh, nice. So now I'm searching for devices. And you still can't see me? That's crazy. We tried it before. That's so sad. I can try to switch off the Wi-Fi and switch it back. Maybe your Wi-Fi is just bad. I can use 5G, actually. OK. Whatever. Not going to show you the demo, sadly. I don't even have pictures. Whatever. Can you try to keep connection to my Wi-Fi? So let's go back to the project. It's actually design-driven. So from the very beginning, we focused on we defined a task we want to resolve. What do we want to do? Like solving the problem I described before, sharing a file on a local network. Obviously, sometimes we have additional problems that Wi-Fi doesn't work. Oh, now it works, actually. Now it works. Oh, thanks. Awesome. Oh, yes. Oh, all righty. So we see here that I got a notification from a photo, actually. Let's see what it is. I save it. And I can directly open it here or show it in the folder, but open it. And that's the portal. Does anybody know what's a portal? Flatback thing. We're going to talk about it later, slightly. Yeah, they're selling stocks. It works. And we also have, like, a really nice, let's put it there. Like, we can drop it there. And he got the same notification or sent it there. So it's quite basic. We have minimal settings for now. Why do we are working on that? Let's go back to the design-driven project and the description. So we focused on the task to simplify also the user interaction. And we tried, at the beginning, to start with just an application which works. That we can directly test it on users and see what we have to change in the user experience. Like, you saw showing folder. Previously, it was move to folder. And we had to implement something like, actually, a file dialogue which allows the file to be saved somewhere else. But we figured out that it's much easier that we're just showing the download folder and the user can copy it from now to those somewhere else. And that's the awesome thing about an MVP, what means a minimal available product, which is a minimum set of specifications we really need to have a working application which user can already use. Also, like many designers say, best UI is no UI. We expected that. But we went the step forward. We think the best UI are notifications because they are not distracting as much as the UI when you have to switch to another application. It's much better integrated in your workflow. Also, a tip for developers. How many developers are here most? Who is not a developer? Yeah, more than expected, actually. So my suggestion is to get a developer on board. Obviously, not everybody can have a really good friend who is awesome developer like Tobias is, designer, sorry. But still, try to get one on board so that you as a developer can focus on what you're really good at, like actually coding. Actually coding, and you can do what you love and you don't have to mess with. Where should I put this button? Do I really care about that? But I care about user experience. I care about having users. If my application isn't usable, why do I do the work? So at the beginning, we tried to create an electron app, which is not native at all. But I actually wanted to create a GTK application. So we wanted to write a native application for GNOME, actually. And also, C is not that hard. Who writes C code? Who loves writing C code? Oh, fewer. Yeah, I like writing C code because it's quite simple. Like you have really basic constructs like F4 and variables. And more or less, that's it. Yeah. I saw those confused faces. But it's not. For the beginning, you can already do something with that. And also, we have really awesome, at least in the GNOME community, we have really awesome applications. And one advantage of advantage of open source and free software is that we can look at each other. We can look at code of other people. And for example, if you want to start GTK development with C, you can have a look at GNOME to do, which is a really awesome app, at least code-wise. And the UI is getting improved constantly. So now, we somehow know how to start. But how can we ship an application to users and test the usability and the user experience and get an immediate feedback? Because we are working with designers. And also, they need to know what users think. How do they interact? Therefore, we used Flatpak, which is a really awesome, let's say, container system package management, not a technical description. And we used Natalie belts. For most of the change, we build it, publish it, and got often a feedback already. Or we could really easily test it on friends' machines or also on a second we had a home. Then for the first release, we didn't have to do much because it's already Flatpak. So we created a release. It's done. And you can immediately install it to all GNOME Linux-based machines that's the advantage of Flatpak. There is FlatHub, which is like an app store for Flatpaks. But since, for now, we only created a really basic version of Teleport, we obviously have already, from the start, plans for the future. Most people, I think, have plans for the future for their projects. And we are thinking about adding, sending multiple files. But that's not essential to be able to use the app. Also, we would like to add a more complete settings menu, let's call it menu, that, for example, users can change the device name on inside Teleport. Also, we would really like to have encryption because when we are on a public network, yeah, safety should be an issue. Also, we would really like, which actually was one of the main goals to have clients for different platforms like Android, iOS, Windows, and macOS. If somebody is interested in contributing like a client for another platform, talk to me. I would be excited to get something done there. So we have future plans. So I really hope I got for designers some insight in my progress how I got started with GTK and how I work. And I hope also that I showed a good reason to developers to get designers on board already in the start, already way before writing code, but also to let them participate to the project because they can take off your shoulders a lot of load, which, for example, when you're learning a new language, it's quite difficult if you have also to think where should I put that button, which font should the text be? What should I write there? And in this sense, this is my Twitter handle, julian underscore sparmer, or drop me an email. Yeah, thank you. Yeah, please. No straining because it's either. Actually, since, let's say, my personal designer, is quite involved in GNOME, and the GNOME designer. So he actually knows what he can do with GNOME technology. But I often talk to him, no, we can't do that because it's way too complicated to implement. And then we had really often front and back and forth to discuss how we could do something. And it's an interaction between two people or more people. It's not like a designer is coming to your project and he is saying, we have to do it this way. You will, on the way, also learn. You can also learn something about design and then create together something like a project. Does that respond to your question? Oh, I have to repeat the question. The question was, can you repeat the question? OK, the question was, if GTK is limiting the possibility of implementing a design proposed by a designer, other questions? Yeah, please? Yeah. So it wasn't actually a question, it was more a suggestion. Oh, the question was, what am I using on the back end to send files? It's Lib Soap, which is a web server. Yeah, it's a basic web server, a library, a GTK library. It's part of, how does the client know? The question was, isn't it easier that the client is pulling the file than pushing it? It's actually that way. The computer, which is sending a file, sending a notification that I'm offering you that file, you can download it from that URL. So it's actually the same as creating your own HTTP server from the terminal and then sharing the link with somebody. It's the same thing, just with a different user experience. I do that all the time, like creating an HTTP server and sharing the link, but it's too much work, actually. And the discovery is handled by Avai. Do I pronounce it right? I don't think so. Yeah, that would be also nice, but different use case, actually, because you still have to use Telegram or any instant messenger to share it. Yeah, yeah. In two parts. The first part is, this has anything to do with the people nearby functionality of the laptop itself. Yeah. And the second part of this is, I know that that communicates with Macs quite well. With Macs, sorry? With Macs. Ah, Macs, yeah. OK. Is it possible that this could be a problem with AirDrop? I actually don't know how AirDrop works. I don't have a Mac, so I couldn't try it on my own computer and never around to try it. But it could be possible. We are using, actually, Avai, which is an implementation of Bonjour. So it could be possible. But we should, like, the AirDrop is proprietary. And I think it is proprietary. I think so. Yeah, I think so. They didn't. I don't think they allow third people to develop applications for that, I guess. Thanks. Other questions? The project, by the way, is public on gitlab.known.arc. But you can find it also on GitHub. Or just search for teleport. You will find it.


Friday afternoon folks Ted Rolston downtown Honolulu here in our think tech studios with our show where the drone leads and In the east coast studio of think tech studios Hawaii in Sturbridge, Georgia. We have standing by dr. Mike Brown of one way one world one way Mike Welcome on board the show again Thanks, and Ted, I'm in Stockbridge Stockbridge. Well, we'll push in the stockade. How's that? Halfway in between and it's evident Mike that the Sun has set on the east coast judging by the color of the Of the outside and in the environment there, but you have all blue going you got blue lights You got your blue kung fu outfit on and so night has fallen and behavior Deviations start to show up. Anyway, Mike. Hey welcome on board again and Dr. Mike Brown is an incredibly interesting individual who sees Change in an interesting light. He's changed in the light of disruption and how we how disruption needs to be disruption Automatically accompanies new technology. It also has to be dealt with as Organizations and users start dealing with new technology UAS, which is the subject of our show or groans is all about new technology We happen to have one on the table here one of our Thanksgiving table guests has joined us It's a gate wing professional mapping system a UAS on manned air system on her drone And the reason I have it here on the table is just to open the discussion that Mike and I are about to have But in the in the show last week, we had a gentleman named like a mortis on and his associate Kainoa M&S and we were talking about the Community involvement aspect and the reason we need to think of community involvement and the reason we have Mike on is But we have something novel and different and new such as what we're seeing here It has to be introduced into the user community and into the benefiting community in a very careful way to make sure that the proper positives are understood and any negatives are Understood also and managed and kept out of control in a very simple example If you saw one surveyor on your street doing some surveying No big deal if you saw two surveyors they kind of come in pairs that makes a lot of sense If you saw 500 surveyors on your street, you might wonder exactly what's going on If you saw one of these drones somewhere nearby you might Say hey one's okay. What if what if you saw 500? It's a whole different way to think in a and there's a The the incorporation of this in our daily thought process Has to be carefully managed and that extends to the community of youths of drones Which is going to be public safety the environmental people agriculture All the organizations that can benefit from surveillance and from information gathered by drones are still going to have to deal with the Community involvement and the incorporation of this kind of technology into their Business operations just because it is novel and new and doesn't replace something that's already there a better Telephone replacing an old telephone that's easy, but something like this It does not replace something that's existing but actually adds a whole new dimension of operation is can be frightening and certainly Stressful and therefore has to be properly managed that sounds like disruption and for disruption You always turn to who dr. Mike Brown dr. Mike Brown of destruction Like in blue there you are That's the consequence got it so Mike you were just at the at the International Association of Emergency Managers meeting last week and presented to that group a View of the disruptive aspects that I was bringing at the game. How'd that go? It went well. I was a little worried because Part of what I was trying to get across to them is this is that right now? There's a lot of frustration amongst the emergency managers for and public safety individuals because Their feeling is though they've been kicked to the side because they want what's on your desk right now They're saying we need these tools because there's a paradigm shift this new tool changes The way that we can conduct all of our mission areas Response recovery all of that, you know, it's we know what it can do for the agricultural community for the real estate community for all of those Different areas, but what it does for us we see as being life-saving and and it adds to the Quality of life and helps us to mitigate Certain issues by being able to have these and so I'm hearing Why do I have to jump through hoops to get the co-op? Why is this exemption and why won't my governor give me a waiver? And and so they don't understand it So what I tried to do at the conference was to explain to them in a way that they would understand what is occurring and The method that I used Was things that they are used to lessons learned observations and best practices now everyone in the room could relate to that and They were very excited about that and I said well You know you have to look at Congress and what Congress has stuck with is what we call with bounded rationality I said I know that that's a strange comment having rationality in Congress in the same sentence I said but the bottom line is we can look at this from a rational action Perspective and so I said we're not going to go into rational theory I said but understand this there's a couple of conditions that need to be met in order for you to make rational decisions and I said what they add up to our lessons learned So when I started doing that I said if Congress right now has no lessons learned It I think I think the bill went off So you're breaking this thing down to sort of an executable strategy as opposed to a frightening Barrier yes, because what happened was I you know they want to know why there's such a delay Well, I told them that usually we are always complaining about having top-down Applications where something is decided at the federal level and then shoved down our throat and I said as we know all Response all preparedness Starts at the local level the Stafford act it all tells us that we all learn this in academics It starts from the lowest level local level and we appreciate bottom up And I said this is an opportunity right now for those of you who do have access Who have met the requirements for part 107 or coat? Got your coas got your exemptions and your using these start documenting and Coordinating with the with the national emergency response and rescue training center with the with the Ted Rousen or the person Who I call uncle start connecting with the national Disaster preparedness training center and in FAA. They're not your enemies What we're doing right now is we're a period of structured Lessons learn and if I can enter introduce to another comment there community involvement What you just spoke of is about six different communities that are all involved and in some way relate and overlay on top of each other Not completely, but to a certain extent so what you're saying is Involve yourself with all of these be open be communicative put information out including things that don't work failures problems Let them be shared as well That's lesson learned if you know you if you're gonna do it We look I will be the two examples I use and it resonated with them was the in the 1970s We had duck and cover and Then we had on the other side with civil defense. We had the national We had natural disasters Remember the governor's got together and said we got a problem You're giving us all this money for duck and cover because we might get nuke from mutually assured destruction What we really need to use this federal funding for is for natural disasters Can we do that so they developed a dual use system where they said, okay? You can use this funding and their Jimmy Jimmy Carter came around and then we've got FEMA and Barabing by the boom so we developed the system where we we learned well that happened again The most significant time that happened was fire scope with the firefighters in California where they left their egos at the door They said look guys We've got a pool or resources together in order to try to deal with the situation But they learned there was a lesson learned well, that's what we're doing now But this this time it's more structured what's happening now is that Congress has said You're the whipping boy is the FAA let's stop whipping them what they've done is the best They can they've issued us a couple of guidelines some policies that we can deal with and they're going please work with us to tell us How we should approach it because there are so many alternatives How do we deal with protection of privacy? How do we deal with the retailers and the manufacturers that want to sell these items? How do we deal with the people that want to use these for recreation? And then how do we deal with these people for for for that want to use these for public safety? Well all the alternatives and different issues are out there Those have to be weighed in what's called a cost-to-benefit ratio not necessarily an equal economic Standards but also for social standards, which means the values some people value Their privacy and don't want their neighbor to be utilizing a drone Well when needs when Congress finally gives us a law or some guidelines Everybody all these situations have to be weighed so we get the best Possible law for all those six different layers of the communities and players that you were talking about With the most benefit not everybody's gonna win what we have to do is identify that benefit Somehow characterize it write it down and put it in simple terms so people can understand it I like the point you made earlier about The FAA having been the whipping boy for a certain several years here now FAA came through and has made massive changes They put the 333 exemptions on the street two years ago But 107 on the street this year and educational interpretation the FAA has done all they can and they're actually doing even more our state here in Hawaii along with Oregon and Alaska is involved in one of the FAA test centers are seven across the country so issues at I AEM or the International Association of Chiefs of Police or any disaster agency Can bring forward to us the test states can be turned into test programs to go find that relevant information about how that Device kids head that's part of the problem What a question came up from one of the person that was in the audience and he said well dr. Brown let me ask you if we Do this and we had these observations and I said I told myself you know what? These seven test centers is one thing, but that's a controlled environment What George Purdy did recently your guy there at the airport there tonight? That's that's fine And we need that information because that gives us an idea how we can operate operationalized and Functionalized certain ideas that we may have but there's nothing better There's nothing that can replace a firefighters or an emergency managers and incident commanders actual Observation doing a real incident or disaster because those are things where they're not Calculated they're not scripted and what they do In that situation is something that can be shared with all of us because we learned from it The problem is there's no pipeline direct one the policy-making Organization that's a repository collecting all this information We're sure we can talk with the FAA we can talk with the with the comport with the consortium for national disaster preparedness Consortium a lot of those but there needs to be one Organization that filters this in brings it in and is able to do a three a Throughput and put this information out to all they would be great with using it Oh, this should go here Oh that has to do with this and this should go here or that should go to Las Vegas to leave to our group there That's dealing with C toast issues. Mike. Let's let's let's let's do this Let's take they one world one way as an example of an agency that could assist in promoting this idea Let's figure out after we get back from our first break here Let's figure out how we're actually gonna do this. Let's take on the task. It is the open gap right now as us After we get back from our first break Sure Aloha, my name is Mark Shklav. I am the host of law across the sea. Please join me every other Monday to hear lawyers from Hawaii Discussing ways to reach across the sea and help people and bring people together Aloha, oh, huh. How you doing? It's me Angus mctech wishing you know welcome and join us to see us on Hibachi talk I'm think tech Hawaii to all my co-hosts Gotta know the tags up and enter the security guy every Friday from 1300 to 1345 we look forward to see it. We'll talk tech and we'll have some wee bit of fun And remember let your wing gang free where area B. Aloha. Aloha. My name is Danelia D. A. N. E. L. I a And I'm the other half of the duo John Newman We are the co-hosts of keys to success which is live on think tech live streaming network series weekly on Thursdays at 11 a.m. a Low ha a low ha We are back folks for the second half of our show where the drone leads today. We have dr. Mike Brown of one world one way in Stockbridge, Georgia our east coast studio As you can see the Sun has set on the east coast hasn't quite set here as you can see by the background Anyway, Mike welcome again, and thanks very much for that stimulating conversation We just talked about it a bit at the break your idea was that the gap of communication and understanding in You're about the only person I could I know who could see it this way But that is such an important issue part of the community involvement expressed in the what's how good is this thing for me? How can it work for me? What are the issues? How am I going to make something like this novel anew go forward? So what we're talking about before the break is the gap the absence of a Repository a place where on a safe basis everything associated with the use of drones in the world of Emergency management for example could be collected and could be sorted could be shared and the things that work Shared and understood the things that don't work Advertise as well so people can begin gaining the the the experience the the muscle memory of how this stuff really ought to go Right, that's right. So we were just talking at the break is you know We have a lot of other new technology that's come in like social media and stuff I don't think in social media that we necessarily have that mixing box where everything gets to come in and get sorted out I think we probably in the social media domain call that the marketplace things that don't work Don't survive in a marketplace things that you can ask them something about that Say again, you can ask Sam something about that their phone. Well, there you go. Right. Yeah Now of course really old people like me don't do social media So we're not really we our information doesn't contribute to the the DNA increase here. So what are we going to do Mike? How are we going to get? In fact, why don't we do this you had the meeting with I am we had a similar meeting you and I together with in my and Steve Johnson Steve Jensen as well with NFPA a while ago. We have a meeting coming up Tuesday with the International Association of the Chiefs of Police. I think we're going to head in the same direction You get three major organizations here Would they have any place where they come together and share thoughts? Would they as three organizations be interested in owning this box into which we deposit this kind of experience? Well, of course they would you know I reached out to the Atlanta Police Department here and I asked them if they had had drones and even though Georgia has a Law a state law now for drones for UAV's the Atlanta Police Department has not yet adopted the use of of drones Same thing with their fire department is quite a large fire department and police department But they're they're not utilizing even though the state has already implemented a law on the contrary You know Chicago was one of the first major cities to come up with a I think I sent you a copy of that of their drone Ordinance that they're using so they're kind of a disconnect my interest with the Chief of Police would be this That there are some gaps in what they call the communications assistance for law enforcement act That needs to be updated That law needs to be updated to include violations and use of new technologies so that they can have access to certain tools In order to investigate in prosecute Acts using that so that's one of the laws that I think Congress needs to look at and that needs to be brought up Doing this Chief's meeting the other issue is you get these organizations the IEM and the International Association of Chiefs of Police and the National Fire Department, but None of these individuals there's not one specific place within FEMA Or within the consortium where they can download and send and format videos and or narratives of their Incidents That they've been involved in or their exercise and say look this is what we found out that would make for an excellent Excellent and that would be a no fault. No no follow-up type issue. You whatever it is. You report it You know, there's an interesting situation about 15 years ago either the FAA or the NTSB created a No, no follow no harm type reporting system for aviation Whatever you did that might have deviated from the rules or whatever you Experienced observed or saw happen or cause yourself you could report it and there was no Recommendation for there was nothing coming back to you It was simply a data point that went into a box of some kind and then decisions were made about where regulations need to Be changed for training needs to be changed something like that So we're talking the same thing here. It's been done before You know, then that that's one of the things every day across the country There are different situations no matter how small they are that are utilizing that tool That's on that table in the front of you. Well, these are things a lot of this is being lost They're filed away. Nobody ever knows about them. Look how we're doing this now We could have a repository and what needs to happen is that it needs to be interacting Someone on the other end or group needs to review this information and get back with them and say look We appreciate your input. It was wonderful. We saw this We have another question for you. Let us ask you this and from that you start to build an actual algorithm of narrative Technical and narrative Qualitative you where you can see where you really can filter and get the best You know what Mike this is starting to sound like an intelligence situation just like you and I have talked about before We're talking about semantic analysis of multivariate narrative and such We're talking about correlation and deconfliction all the rules of intelligence play out here as well That's right. And as you know, this is such a as all the ideas come from you are You know beyond the the limits that were used to us. So this this is this is shocking and incredible at the same time Oh Man, I ain't got that much money. Okay. We have one more guy who often is at this table named general Daryl Wong Same thing we limit him to two bright ideas per show because we can't handle any more than that But what what this is this is critical for the nation this very discussion that you're leading and this idea You're taking us into what but it was here's another here's another way that it works Well, because it's tied into if it's tied into Congress's database they do research constantly if it's tied into their research in the GAO government accounting office They would have access and be able to go and look at things are being done In other words, they could review and look at these lessons being learned and observations as They were trying to get together to develop law going forward in the future So it would help them as well, but it'd be one central place where public safety could deposit Their experiences that they thought were noteworthy having to do with new technology stingray technology In other technology, I've been I'm a big proponent of the communications act of 1934 is completely outdated And it doesn't allow under the FCC rule for any use of jamming technologies At some point we're going to realize that with this new technology in the front of you and others that Some of our intelligence agencies and some of our national security agencies will have to be able to use Some technologies that we are saying are forbidden You're giving them to individuals so that we can fight an asymmetric battle Of changing things that mean that thing in the front of you is a wonderful tool But it's also a platform for disaster And I've you've heard me state that once before you saw what happened with the president last year When the Secret Service had to stop the one guy in Hawaii and Compliant the drone. There's a reason for that, you know in Dallas, Texas They slapped C4 on a robot and sent it in a room and got rid of a problem Well, they could do the same, you know, somebody that's nefarious can put C4 on a on a UAV And put it in and our national security Apparatus and our public safety need to have the tools that they need in order to address That probability that something like that will be that will happen particularly since it's easier to get a recreational drone Then it is for our public safety This very issue you're speaking of the the malicious use and this sort of thing would fit that same pattern It's a it's a it's a pat it's a data identification and pattern recognition situation and that same intelligence system that would collect the Issues associated with positive and negatives of use in disaster operations would have a section in it. It deals with this malicious use So you could use that same system to collect those Factors and those there's indicators of emerging patterns, right? So okay Mike So we have an obligation. I think between the two of us to take this story forward You know, I was just thinking as you're talking And I don't want to put anybody on on the spot here But we have been talking with our partners in Alaska about using our congressional delegations to in a shared way To see this picture and start taking some of start taking an interest in some of these issues at the at that level I think that and you're you're correct on that. It is the that's the level that has to occur and in fact all of the I Would should say in fact all the work in getting UAS into the business in the first place was really came out of Congress FAA took care of a lot of actions, but they were mandated by congressional acts and by the Revitalization Act of the FAA. So that's where it starts. That's where it ends. It's in Congress, isn't it? Right? Well, and we have some friends in Congress. I've mentioned Charles Schumer. Yeah, he's Schumer. Yeah, Senator Schumer He is introduced acts and he's he's looking to push Geofencing and the question came up last week when I was at the conference about geofencing and I I avoided the question to some degree. I Don't like going into to Certain technology because I believe that those particular geofencing is a key a very key Technology that will put us in a position to protect critical infrastructure and also to strengthen it or the national information and infrastructural protection program Because they got to be working hand-to-hand and that's something that I haven't seen Lately and that would be under PPD 8 PPD 21 But I think the the main issue is Congress has their hands tied to Because none of those gentlemen know as much about the instrument on that Table in front of you as the people that are actually using it and they're waiting for us to give them ideas ways and means and Lessons learned they have to you can't make policy or laws based on you know If I can intercept your thoughts for a minute might which is is the second you've given two brilliant ideas on a table And that's the limit for the show We don't allow more than two as I mentioned it because if we just can't handle that many more bright ideas But but the as an analog of that what the FAA has done with these test centers is exactly a Small-scale version of what you're speaking of the purpose of the test centers is to find out what works What doesn't work what the issues are what fails and where the success has to be done either technology or regulations so the model is there we've seen that model play out several times and This idea you've got of taking a story to senator Schumer. Let's do it. Let's obligate ourselves right here on TV I reached out. I reached out the week before last. I haven't heard anything back, but I did reach out The problem with the test centers Uncle is that those test centers Like I said, and I stated before are those are controlled environments We can fix that. We'll take that challenge and go fix it. My god. That's that's what we're all about Now I can guarantee you the same scenarios that they're using and that they're putting out there Given in the real-world situation There are gonna be three or four other variables that many many more variables no question about that But we can do it and that's the thing that you know, you you're preparing you say you got your you got your you got your You got you a be under air operations. You got all the resources yet tight ready You got everything set everybody's ready for the next window next for the next period everything's fine And then you get a telephone call that there's four or five drones because a little group of teenagers are Out there and they're all trying to suit and get the best picture of whatever it is is happening now You're ready for one UAP, but you're not ready for five right or or 500 and in fact the whole world counter drones all about that We're reaching the end of our rope here in in the show Again, I can't thank you enough for the the brilliant ideas We'll see you on the telephone on Tuesday We talk to the chief of the chiefs of police and let's follow up on this idea of At least starting to present the idea to our congressional delegation and the senator Schumer at the same time what I want you to do is reach out to the National disaster preparedness consortium and see if they can have a policy report Pository we'll do that. We've already suggested that to them many many times. So we are out of time at this point in time Mike Brown in Stockbridge, Georgia and his wonderful family standing by off-camera. You may now return to your 1030 Friday night activities, whatever they may be and Okay, Mike


Here's the flowchart for a program that asks the user for a year and tells them whether it's a leap year or not Here's the code. There's nothing wrong with it, except that when we test the program It only does one year at a time If we want to test another year We have to run the program again and again What we'd really like is to run the program once and have it ask us over and over again for years This is a perfect use for a while loop. Here's a revised flowchart We'll ask for a year and then test a condition as long as the condition is true We process the year Ask for the next year and Loop back to see if we should continue or not The question now becomes what's a good condition to test? We need some value for the year that will tell the program. Okay, I'm finished This value is called a sentinel value. It's a special value that doesn't represent valid data But instead tells the while loop that it's time to stop In this case our sentinel value is zero. This is an ideal sentinel. There's no year zero So we can use that as our special. Okay, we've finished value That means we continue the loop as long as the year is not zero Let's update our code first We'll change the description of the program to add that we do this until the user gives us zero for the year We'll change our prompt to reflect that Enter a year or zero Says quit After we get the year we'll add our while with the condition year not equal to zero and an opening brace The test for leap year becomes the body of our loop We indent it and put a closing brace to close our while loop After we process one year, we have to add code to ask for the next year We'll print our prompt Enter another year or zero to quit And we'll get the user's next input Let's compile that and let's run it this time When I enter a year it asks me for another one and Another one and another one until I'm ready to stop I enter zero and the program ends and That's how you can use a loop to repeatedly ask for input


You might have played the game of hide-and-seek right think of some places where you would like to hide so that you are not seen by others Why did you choose those places? Would you have tried to hide behind a glass window? Obviously not right as your friends can see through that and spot you Can you see through all the materials? What about what about this piece of paper? Can you see what's behind this paper? Those substances or materials through which things can be seen are called transparent glass, water, air and some plastics are examples of transparent materials For example, you can easily see the burning candle behind this glass and also through the water These are called transparent substances Shopkeepers usually prefer to keep biscuits, sweets and other eatables in transparent containers of glass or plastic So that you can come and pick up your favorite candy. On the other hand, there are some materials through which you're not able to see For example this piece of paper. Now if I place this paper just like this, I'm sure you're not able to see the burning candle Yes, you can see some light, but you cannot see that candle and of course you cannot see the glass that is behind it You cannot tell what is kept inside a closed wooden box, a cardboard carton or a metal container, right?  Now, let's see something interesting So what I'll do is I will take this piece of paper and I will put I will rub some oil on top of it Okay, so here I have the original paper. We cannot see the candle, right? But now after rubbing some oil on it, see what happens Do you find that the candle is more clearly visible than before? But can you see clearly through the oiled paper? No, right? Not entirely Not everything on the other side is visible So these materials through which objects can be seen but not clearly are known as translucent materials Here is one more example of a translucent material. This glass sheet when I place it in front of the candle You can't entirely see the candle, but you know, there is something on the other side something glowing something burning This also shows that not all glasses are transparent. Some can also be translucent So this is one more way to group a substance You can group a substance either as opaque through which you cannot see anything You cannot see on the other side of an opaque object a transparent object Through which you can clearly see what is on the other side and finally a translucent object through which you can see What is on the other side but not clearly


OK, brilliant. Fantastic. Good morning, everyone. I'm Chris Murray. I'm a technical specialist at Rakuten, specifically in Europe. So this is a VMware-sponsored session, but this is my customer story. This is how we did VMware Integrated OpenStack. And it's more than that. It's more just generally how we use OpenStack, the features we use, what we've done differently to make it work on our vSphere environment. So it is sponsored, but it's my honest point of view. I'm not going to be here doing a marketing pitch. OK, so Rakuten. Rakuten are a Tokyo-based e-commerce and internet services company, very big in Japan, less well-known in Europe at the moment. That's something we're trying to change. The Rakuten ecosystem is really our core business. So we're known for our e-commerce, but obviously there's a lot of other services that we offer around that. And it's really about providing a set of services for our customers, everything from the e-commerce side to e-banking, media streaming, e-books, et cetera. To give you an idea of the scale of the company, we're 110 million users registered in Japan now and a gross transaction volume of around 7.1 trillion Japanese yen. So it's about 62 billion euros. And we've expanded quite aggressively globally over the last few years, and there's a few names there that hopefully you'll recognize. My department was acquired as part of the Play.com acquisition in the UK. And we now have taken that infrastructure, and we've been providing a private cloud for European use. So we do have data centers globally, obviously, some acquired through the acquisitions, but also some more strategic. And the data center we're running in Luxembourg is a great location for a strategic data center for the European market. As an ops team, generally it's our role to provide the tool, support, and service so that our development teams can actually concentrate on delivering the business logic that drives our customer satisfaction, really. So after the acquisition, we took our vSphere platform and we looked at how we could make it multi-tenant. And the choice at that point was vCloud Director. We deployed vCloud Director and provided that multi-tenancy data center that was relatively easy to consume by our other companies. That's about 840 VMs at the moment, so it's not huge, about 36 different business units within Europe. Now, that platform was OK. It did the job at the time, but the world's moved on a lot since then in the last few years. We're very much more cloud aware now we're aware of what the developers want and we needed to replace the platform. So vCloud Director is End of Life as well for enterprise customers, although still available for service providers. So that was one big push. And we also wanted to move to the next generation of SDN software. So we were doing virtualized routers and virtualized networks with VXLAN in that environment, but we wanted to take it to the next level. We wanted to move to things like security groups rather than traditional enterprise firewall rules and things like that. Secure multi-tenancy was obviously still a key requirement. We're still acquiring companies and obviously if we can onboard them and have them using our data center, that helps with that onboarding process of new companies and also interoperability between those projects. And we still have pets. There's no way of avoiding it at the moment. We all want to go towards these new cattle cloud aware applications, but we still have lots of pets. So whatever we did had to be able to support both those, if you like, legacy or existing workloads, as well as the next generation of apps as we move forward. Some of the feedback we got about our vCloud Director environment as well was that it worked fine. You could use the GUI. You could deploy your instances. But it wasn't really enabling our developers to develop clever, intelligent workloads on there. So they couldn't autoscale. They couldn't use the APIs to define a blueprint for an entire application and deploy that. So we needed something that was more open, that people could use their tools like Terraform and Chef and all these wonderful tools beyond just the VMware ecosystem. And crucially, we had to do it quickly. This wasn't something that we need in two or three years' time. This is a problem we need to solve now, really, yesterday. So it was crucial that whatever we deployed had to be in and running and production ready as quickly as possible. So I spoke about pets and cattle. I'm sure it's been mentioned quite a few times this year or this week. We've got quite a lot of this middle workload. My automated pets, we've scripted them out. We're using Chef. We're using Ansible. We're using all sorts around the company, Puppet, a lot. I think we've got every tool deployed possible. But we're not fully cloud-ready for a lot of our applications yet. So OpenStack, we needed a new cloud platform. OpenStack, obviously, it's very widely known. It's probably the leader now in private cloud technology. There isn't really much else to compete with it. On top of that, we've made a company commitment globally. Neil Sato and Kintari Sasaki stood up at the Tokyo summit and declared that as a company, we were starting on our OpenStack path. And that's great. And we have a few teams globally working on OpenStack in various different flavors with different requirements. We were the same. We couldn't directly use one of the platforms that they were already working on, mainly down to the aggressive nature that we needed to deploy this quickly. So we went about understanding OpenStack. Now, obviously, there's the Summit Videos. We used Lyons Academy as well as a way of getting some sort of structured learning around understanding what OpenStack was, understanding my NOVA from my Neutron, and then lots and lots of reading. And I've joked here about the link rabbit hole. As soon as you start reading about OpenStack, you find a great document, and it's got a link going somewhere else, and then somewhere else, and somewhere else. And I had days when I'd have literally 100 tabs open on my machine for all these things I have to read. And it's great that all that information's out there. And we also attended some meetups. So the London OpenStack meetup was a great event to meet some new people and find out what other people are doing. And now, OpenStack attendee. We looked at the OpenStack components and tried to identify which ones were crucial to us. Obviously, I think that's some silly number of OpenStack projects now. But really, it came down to the real core components for us. We didn't need all the bells and whistles that some of the projects are doing right now. So NOVA, Neutron, Cinder, Glance, Keystone, obviously, and Horizon. They were the real ones for us. And then on top of that, we looked at, identified, Solometer and Heat as some of the ones that we wanted to use as well. We have mixed developer workloads, some that are keen to use the APIs and go straight in at that level, some that want to use CLI tools or Terraform. But we also wanted to provide some level of automation tool within the platform, if possible. And obviously, Heat provides that orchestration. Longer term, we'd love to look at things like Trove to support databases as a service designate for the DNS. And then there's also some work we need to do around the actual billing and making our billing a lot more automated than it currently is and obviously contain a support who doesn't want container support at the moment. So we identified the OpenStack components. And then we looked at what skills we had in-house. And again, about that aggressive time that we had to get this deployed. And really, the obvious choice for us was to use our existing vCenter platform, our existing ESXi. These are tools that we've been using now for seven plus years in production. We're very confident in using them. We know when they go wrong, if they go wrong, we know how to troubleshoot them. And that was really key for us. And there's a couple of extra tools on there, vRealize operations for services for monitoring, and vRealize log insight, which is just a syslog. It does a lot more, but syslog collector as well. To identify those, we knew that's the way we wanted to go. Now, VMware provides, and this is all open source. This isn't anything special we have to buy from VMware or anywhere else. The drivers for NOVA, Neutron, Cinder, and Glance so that you can take your OpenStack deployment, any OpenStack deployment, and use ESXi vCenter underneath. So that's all there. Anybody can use that. And that made our life easier, obviously. And then we looked at the VMware integrated OpenStack offering. And really, what this gave us was a way of wrapping that up into one easy-to-deploy platform. It's still using the same components that we could have deployed manually, but they've done all the hard work. They've done all the answerable playbooks to deploy this, to configure all the services in the best practice, the security, encrypting all the credentials, making it HA, as well as providing the ability to do backups and restores of the platform. So this was a no-brainer, really, with the speed to market that we needed. So where does this sit within our environment? We know we wanted it. We know we wanted the public cloud style of consumption for our developers. And so it was crucial that we made it accessible when it had the public IPs. But equally, we're an enterprise. We care about security. It had to be secure. So we presented our Horizon and our API endpoints behind our firewall, but it's on a no-natted IP address. So it appears public, but we actually block all external access at the moment. The only time that we'll open this up is when we've got maybe acquisitions of new companies that maybe aren't fully integrated onto our network, backbone networks yet. And obviously, we can expose or trust their IP addresses to allow them access to the OpenStack platform. Equally, we've got an un-natted public subnet that we present into our tenants that allow them to have floating IPs. And they see the actual public floating IPs that they have. But crucially, as an enterprise, because it's behind that firewall, we can still apply the security restrictions and policies that we like. So if we don't want to allow any SSH into the environment on those floating IPs, we can control that on our firewall. From a project point of view, it's great to be able to have these isolated projects for tenants. But as an enterprise, they need to be able to talk to other things. So we've provided a mechanism where we can deploy another small virtualized firewall using NSX and connect that to an existing VX LAN that we provision in the tenant. And then from there, we can route the traffic out to our core network. And as a cloud provider, we've got control about what traffic is allowed in and out of that tenant. So again, we retain control of our production network, our core networks. But we allow the tenants to have an amount of autonomy within their project without generating too many risks. OK, so just talk through some of the services, some of the decisions that we've made. Keystone, you can't really avoid Keystone. But we decided not to go with Active Directory for a few reasons. One, our Active Directory is quite large. I think we're at about 20,000 users at the moment. And because of the way we're doing quite a few migrations of data around, the scoping for AD for Keystone made it not that performant. It caused us some issues, especially around using Horizon. The other thing was we wanted to be able to quickly provision service accounts. And by keeping it a standalone authentication, it meant that we could provision service accounts for projects, for Terraform users, for example, without having to go through the policies of creating new Active Directory accounts in our environment. We also set every user up with a new user project. Now, this gives them an area that they can use to play around with OpenStack that's separate from the projects that they work on. But it also means that by making the default project for all of our users, if they want to use Terraform, their default is to use the user project. And they can't break anything or break an existing environment. If they know they will need to work in a specific project, then they can override that and set the project setting within their CLI or within their Terraform or whatever tool. And then we're just using standard roles within Keystone. So it's just member and admin. From an over point of view, we identified quite early on that we needed a way for the tenants to be able to define applications across multiple availability zones. If they're deploying something like RabbitMQ, they needed to be able to say, all right, these three nodes have to remain separate. And there are tools within VMware to do that historically with affinity and anti-affinity rules. And they are exposed into Open and Stack. You can use those. But we wanted to make sure that whatever we did on this cloud platform was interoperable. We weren't doing anything special because it was VMware. And so we decided to go with three availability zones for a start. We're using a single region at the moment. There may be scope in the future to expand that to maybe add a second region in a second data center for sort of DR workloads. But at the moment, we've concentrated on the primary region. All our instances are using persistent storage by default. Because we're using SAN for all of our storage, it made sense just to have everything persistent. We still have a lot of these pets, and we didn't want any mistakes of people accidentally losing their storage. As a future option, we've talked about potentially changing the way our clusters are designed, still having three availability zones. But behind the scenes, actually having more clusters in vCenter with a sort of tiered approach. So we might have our high end, maybe HP or whatever, hardware that's more of a higher price point, but it's more suitable for our pet workloads. And then offering a lower tier of hardware, less resilience, a lot cheaper. So effectively, we can pass that cost saving on to the tenant as well. And that we can do. We can flag the flavors as either a cloud flavor or as an enterprise flavor is what we discussed. And then those tags can flow through and effectively help decide what cluster in vCenter it goes on. That is a future thing. Moving on. So it's possible to run VMware Integrated OpenStack just with flat networks. And not using an SDN, excuse me. But for us, it was crucial to have the SDN features. We already had them in our vCloud platform. We allowed our tenants to create their own multi-tier applications, their own networks, their own routers. But we wanted to move to the next level. And NSX has given us that. Obviously, it does vXLAN behind the scenes, which is what we're used to. But there's a lot of optimizations on the vXLAN side of things from having multiple VTEP endpoints now on a host through to the simplicity of deployment with no requirements on your physical environment. So we're not doing the IGMP reports or anything like that anymore. It's just pure unicast in our environment. We also wanted to take advantage of distributed routing so we can optimize the east-west traffic within the data center. And load balancing as a service was also something that we wanted to offer for our tenants. Some tenants or projects are using the load balancing as a service. Some are bringing their own load balances with HA proxy or a brocade or whatever and running them as software instances. And then in terms of the connectivity back to the rest of the data center, we provide this sort of peer network. And it's created in OpenStack as a vXLAN. And it's then that we go behind the scenes and add our NSX edge to allow the routing into our back-end network. Now, I've got a rather complicated slide there to show how that works. I'm not going to talk for it now, but if anybody wants to know more details of how we're doing that, how we're using BGP and ECMP to distribute those routes into our core, please just speak to me afterwards and we can go through that. Cinder. So I mentioned earlier we're using Sans to back all our storage at the moment. It's all fiber channel connected. And we're actually using pure storage. It's pure flash at the moment in this environment. Now, we wanted to, again, provide our developers with a way of saying these machines shouldn't sit on the same storage. At the moment, we only have one storage provider presented into this platform. But we've set the scene now in terms of having a separation by having storage zones. Now, the storage zones are effectively volume types when you deploy your Cinder volume. And you choose that. That maps through from a volume type to a storage policy within the vCenter environment. And then that maps through, in turn, to tags on specific data stores. So we allow the tenant to choose that and that makes sure that the two of their machines, if they're in a cluster, don't end up on the same storage. Going forward, we want to extend that. We want to potentially offer different tiers of storage as well as making sure that those are more separated onto different storage platforms. The storage tags within vCenter are not one-to-one. So you can have one-to-many. So we can have, for example, SSD as one tag and storage zone one as another tag. And then set up the storage policies to map multiple tags and really give quite granular control to our tenants. And one other nice thing about the way that the presentation of storage into Cinder works within a vCenter environment is that it's abstracted away to a lower level. So if you've got fiber channel connected, NFS storage, if you've got a pure storage and HP or a vSAN or whatever storage you want to use, it's very easy to add those in because they're all presented as data stores and then that's all presented to Viya in a consistent manner. So there's no changes in Cinder for adding a new storage provider. So glance, I don't have time. We're using base images that we're building with Packer. At the moment, these are OVA-based, but we're looking to switch to a VMDK-based standard image just because it gives us a few more features. It is possible to import QCAN2 raw images as well. And that's just as simple as in Horizon, just adding a URL on saying, import this image for me. In reality, we've had some mixed results with that. Certainly, we haven't had the consistency that we'd like. And because this is going to be a production platform, we need our images to be 100% rock solid. They need to be fully optimized. They need to have VMware tools. They need to have the VMX net-free network driver and all the best practices for our images. So that's why we've chosen to go down the Packer route and build those images. Going forward, we're looking at potentially offering some standard images, but then also have some prepackaged applications, a MySQL or a RabbitMQ as a standard image. And we might not publish those to everybody, but use maybe the image sharing feature so that we can specifically target individual projects with those images. Interoperability, obviously that's been a big topic this week, and it's been a big topic for us. It is crucial that whatever we do here can be picked up and put on another OpenStack platform. So a developer can use the same Terraform recipes, the same everything end to end has to be identical. We have teams in Japan, in the US, other teams in Europe. They're also looking at OpenStack, and we don't want to have anything that is specific to us. So VMware's work to get Devcore compliant was obviously crucial in this. And obviously, we've seen yesterday's keynote that that interoperability is really becoming something that's there now. It's something we can rely on, which is fantastic. Now, we didn't want to just fully trust VMware on this. We actually engaged with Stack Evolution as an independent OpenStack for their expertise and had them have a look and make sure that we were doing things in the right way. We wanted somebody that didn't know anything about VMware to come in and say, yes, you're using OpenStack like an OpenStack engineer would use it. We were. So there were a few inconsistencies. I've already mentioned about image formats. So QCAP2 and Roar are supported. But realistically, we're going to build our own images just so we can get far more reliable images. We, like I said, the drivers and VMware tools are key. And the other big inconsistency for us is around the console log. And that's not currently there at the moment. It used to be in vSphere years ago. It used to be available. And it was, I believe, taken out for security reasons. So we're now badgering the guys at VMware to try and get that feature back in and exposed through to Vio. I can't really talk about Vio and the VMware platforms without at least touching on the data operations. We did have a speed to get it in. But that speed to get it in and in production really also meant that our data operations had to be right. We had to be ready to manage this once it was in use. And we've used our existing skills again. And the existing tools that we have were V-realized operations and log insight to manage that environment. And it's fully aware of OpenStack and Vio. Again, this is independent of Vio. You can use these tools with your own OpenStack and VMware platform. There's also an initial management box that you deploy when you deploy Vio. And as part of that, there's a set of CLI tools that you can use to manage backing up with the platform, restorations of the platform, some maintenance tasks as well around Cinder, and upgrades and patching. Now, I keep asking, but I'm yet to find another provider that can do upgrades as seamlessly as VMware could do it with their blue-green platform. It's really quite amazing what they've done. So in terms of futures, what I'd like to see from OpenStack, obviously, there is a policy or in place for roles. You can go in there and create your own custom roles with different permissions. But I'd really like to see that come on a little bit more in the future, really get some granular controls and some different roles that we can create. Maybe we want a read-only customer, or maybe we want a user that can only manage the networks and another that can only manage the instances. So it'd be really great to get that in the future. And really, we just want OpenStack to continue maturing some of the great projects that exist now, but maybe aren't quite ready for us. And then from VMware, I've mentioned the console log. I really want that console log. And generally, I just want them to keep doing what they're doing and bringing their enterprise-grade system and extending it to maybe for a container offering and designate. And just a little thing, I'd really like the storage cluster support. I'm missing that from vCenter. And what's next for us? We're going to be looking to upgrade to Viya 2.5. Viya 3 is out now, but we're going to hold off for that at the moment. There's a few really nice features that we're excited about in 2.5. So we're keen to get on that. But the problem is, my tenants are so pleased with their proof-of-concept environment that they're using it, and they keep putting more in there. And I need to move them on to our production platform. And until I've done that, I haven't got an environment that I can play around with my own leisure. And we're also going to be looking at billing improvements. So in our vClient environment, we used to bill on a sort of quota basis based on what we allocated to tenants. That's out of date now. People want to be billed on what they use on a per hour basis. So we're looking to move to that model. Right now, we're using the stats from NOVA so that we can get the memory hours and the CPU hours and do some billing on that. But really, we need to look at the next stage, especially if we start looking at different tiered storage with different costs and different tiered compute with different costs. We need a platform that can then do that. And there is a VMware product that does that. We will be looking at. And there's also other products within the community that we'll be looking into. And then there's the automation of some common tasks. So the network connectivity between our projects and our callback end is currently a manual process. So we manually deploy some separate NSX edges and do the configuration of BGP and ECMP, et cetera. We want to automate that. And there's an Ansible playbook for NSX that we're going to be looking at to automate that process and just make the onboarding of new tenants a lot more efficient. We're also looking at Rundeck for the automation of some of the administrative tasks. So whether that's a new user coming on and they want to request access to the platform, we want to use Rundeck in conjunction with JIRA to allow those users to request a ticket, go through the JIRA approval process, and then trigger a workflow in Rundeck to create the user for them so that we don't actually have to touch the platform or do anything for them. And that's it. I don't know how I'm doing on time. Pretty close. So if there are any questions, I'll be pleased to take any questions. I'm around today if anybody's got anything, and my contact details are there. So if you're thinking of Viya, if you're looking at maybe not using Viya, but you want to use the vSphere platform and OpenStack, please do get in contact. Be pleased to have conversations with anybody and everybody and share more of what we've done. Thank you very much. Are there any questions at this point? Yes? Yes? OK, so the question is around us using Terraform or whether we're using Heat. Generally, it depends on the development teams. So because we've got so many different development teams working on different projects within Europe and globally, some of them have chosen to go down the route of using Terraform. Some of them are already using Heat. Some of them are using the API directly. So from an ops point of view, we want to be able to support whatever they want to use. Whatever toolset they want to use, we should be able to support it. That's a tough task. In terms of the way we direct people during the onboarding, it's a real mix. It's a case of talking to them, finding out what their skill sets are, what they're trying to achieve. So one of the things with Terraform is around state management. And if you've got a large team, you need to share that state. Now Ansible has your court provide Atlas to be able to have a shared state. But if you don't want to run an Atlas survey, you don't want to run just Terraform, then Heat gives you that all in one and allows you to have that sort of state of your application. But we still have a lot of work to do on Heat to try and work out the best way of using it. We've got a team at the moment that are trying to use the callback feature so that they can be acknowledged when the instance is fully up and running, for the on-wait feature is in Heat and really build some quite intelligent stuff on top of Heat. So yeah, it really depends on the development teams and what they want to use. Thank you. Any other questions? Here you have it. I see you mentioned that you're using OVR apps for full operations. So my question would be, how do you monitor the low-pistic layer over here? OK. So VR ops obviously natively has management packs for the vSphere environment and the NSX environment. On top of that, they integrate with Hyperic. And then there's a Hyperic agent that gets deployed within the OpenStack management plane. And this is another thing that is managed by the VIO CLI. So you provide the agent and the configuration and it goes out and deploys it across the entire OpenStack estate and then configures all the monitoring for your salameter services, your NOVA neutron services, and pulls all that information through Hyperic and then up into VR ops. So in VR ops, you get full visibility from all of your services on the management plane right the way down to your data stores, your actual instances, your hosts, the whole one. It's all collated. So it's a really well integrated system. Have you been experimenting with endpoint operations? That's the new way beyond Hyperic. So the new endpoint monitoring removes the need for Hyperic going forward. And that's something that we're working with the guys at VMware to understand how that works. I think in VIO Free, they're going to be using those agents within the OpenStack management pack in VR ops. So it's just because we're on an older version, we're still using the Hyperic agents. OK. Thank you. OK. Just one more. OK. Did you work out some methods to do a data plane backup? I'm in the OpenStack configuration database. What you can do with the VIO CLI backup and something like the vCenter specific, because it can get out of sync if you're just restoring one and not restoring one. Yeah. So at the moment, the backup of the VIO platform is dependent on restoring into the same vCenter environment. So it's obviously crucial that you've then also got your backup of your vCenter environments. We use a couple of tools to do image level backups of our VMs. And our vCenters are all virtual. All of our NSX control plane is all virtual as well. So we can back up all of that, which means that if we had a full disaster recovery, we could take bare metal, restore the vCenter environment, build the NSX and restore that, and then restore the VIO platform on top of that. So we've got a full end-to-end plan for that. Which means you do snapshots of the vCenter appliance as well as the VMs for the OpenStack and back up them just binary way. So snapshot level backups of the main management components like the vCenter. But then the VIO CLI provides, say, it sends it to NFS. And it takes a backup of all the key configs. So we don't actually need to back up all the VIO management nodes themselves because we can rebuild all of those. It's very simple for us to just say, OK, this node's gone. Just rebuild it with VIO CLI. Because that management node is fully aware of what the configuration should be on that node, it's able to rebuild it. It's just backing up those main config files, effectively the configuration that goes behind the Ansible playbooks and the database. They're the two bits from VIO that we need to back up. And then it's NSX and vCenter backups beyond that. OK, thanks. No problem. OK. OK, thank you very much.