I'll check it out. We're safe. You should. Good thing we found each other. The police station's not much farther. They'll know something. They're for the only ones. What if there's no survivors? No, there's survivors. It's a big city. There has to be. Looks like we're walking from here.


Hey, good morning, everyone. Thank you for joining us today. My name is Sintil, and he's Venkat. We are both from Dell Technologies, a CTO team, part of Sonic for a long time. So before we dive into Suzuki today, I wanted to provide a quick overview on observability. So what is observability? Imagine you have a black box. You cannot see what's going on inside it. But you can observe its external outputs. Observability is that very ability to understand the internal state of a system based on its solely about its external outputs. This means we can identify and troubleshoot the problem swiftly and more precisely using the only information we receive from the outside. So now let's deep dive into what, a bit deeper into what network observability is. What does it mean? Well, it is an extension of the concept of observability into the realm of networks. It is all about gaining insight into your internal network, internal workings of a network, understanding how the internal state impacts the business objectives and user experience. It is about being able to answer your questions about your network quickly and easily. So that brings us to an important question. Is network monitoring the same as network observability? The short answer is no. Although the terms are often used interchangeably, there are crucial differences between the two. Network monitoring focuses on measuring and tracking the performance of the system. On the other hand, network observability provides you a deep understanding of the system itself. So to sum up, while monitoring keeps a constant eye on your system performance, observability goes a step further, offers insight into the inner workings of your network itself. So that's a major difference. So it's good to understand both the concept, knowing how to implement them successfully, significantly enhances your network performance and understanding of your network. So choosing is not about whether you're choosing monitoring or observability. It's basically how you can integrate both in your system management principles. So show our fans how many people are aware of tools SuzyQ before coming here. Today, we are going to introduce to a fascinating tool that has been revolutioning network observability. It is called SuzyQ. What exactly is SuzyQ? SuzyQ is an open source multi-vendor network observability framework and tool. This tool allows us to analyze your network using vendor agnostic queries and methods. This means you can use SuzyQ to understand, diagnose, and improve your network, regardless of what hardware or software vendors are using. The story of SuzyQ began in early 2020 when it was founded by Dinesh and Justin, two experts who foresaw the need for a better way to observe and analyze the networks itself. The main goal of SuzyQ is to improve understanding of your network. It does that by gathering data using an agentless approach. That means that you don't need to have specific installations in the vendor NOS itself. So you are able to collect all the information in abstracted form. So that way, it's basically it's standardized the data format so that it's easy for you to compare and analyze. And SuzyQ stores all the data files in a pocket, a popular big data format known for its efficiency and flexibility. So you will be able to have fast queries based on the data and then you can gather much more insights into the network. So you can use, it provides multiple management interface, the command line interface, a graphical user, REST API, and even a Python programmatic interface to go and analyze the data you collected via that platform. It has a very simple architecture. So as you can see, you have a telemetry collector which collects the information from multiple things using SSH and REST API. And then it has parser, which parses the data. And then it comes back and normalizes the data and then updates into the universal repository. So from there, you will be able to query the system. So one thing which amazed me, I'll tell you a real life example, right? So let's take how SuzyQ can empower you without actionable insights and about your network, right? That's what the most compelling feature of SuzyQ, that's what I love about it when I initially saw the tool. Immediately the tool, I think they started development around April. I think I made my first contribution from Dell to support Sonic in around September timeframe itself. So because I took the tool and then I see the value it provided, right? You can ask what kind of questions I can ask the network, right? In terms of what kind of, what are the software versions I'm running in the system, right? It could be either a trivial SRNO questions or it could be a very complex question. What happened to my network at 3 a.m. in the morning? Why Node A cannot talk to Node B? That it can go that deep to give a quick example, right? So we were in the customer environment trying to deploy Sonic. We are asking them how much Mac table scale they need and they were talking about 140,000. Our devices doesn't support it. We need to implement Mac carving in order to increase the Mac L2 table size because they are an L2 network. And then we ask them, can we try this one tool which doesn't do much harm to their network? It just reads one variable. We tested it a couple of times in their production network and then it has a feature called gather once. And then we gathered the data and what we found out immediately within one hour, the customer was so surprised, right? They had only 28,000 unique Mac address. Whatever they thought about their network, they had 130,000 Mac address is not true. So it was so powerful and to understand your network, what you're running. So today it's all very complicated. So this one, what impressed me was you have thousands of devices across your data center. It gives you one CLI to you. So in the singles, you don't have to log into any of the devices. It provides you one single CLI. You can query all your devices and see what their state are. You can combine the queries in multiple ways. You can assert the system. So that's what brings the power of Suzuki in my opinion, right? So typically the other user example I could think of is after we deployed, typically in one of the customers, whenever we go deploy and troubleshoot, when the network is done, we need to find, they'll say, okay, this is the Mac address or IP address which is having a slow problem. So now the networking team has to go and find where exactly the problem is. So what happens is it took us, so we need to go into log into a system, go into a central part and see where the Mac address or the IP address subnet is. Okay, okay, this goes to this part. So okay, let me log into the border gateway of that part. And then I log into border gateway of that part and then see, okay, where this subnet is located and then I track that down to the actual rack. It takes me about 20 to 30 minutes to do that process itself. When the network is down, we don't want to go and do that kind of things. You just ask a simple query in Suzuki, find this IPR Mac. It gives you where all the Mac really, where it is originated, where all it is there across all the systems. So it's very easy for you to go and immediately tell and pinpoint what's going on in the system. So that's what I really love about Suzuki, right? So as I said, Sonic Integration at Suzuki was introduced by Dell at September. Suzuki uses, I initially, when I started using it, I didn't want to use Rester Management API. So I wanted to be really native so that we can support not only community distribution as well as distribution, but other distributions where people are supporting like us, Dell. So we wanted to work on both sides. So we used the regular SSH, Sonic CLI, Linux CLI and FRR CLI so that it works both on community Sonic as well as the enterprise distributions. And then it supports almost all the features that today, being it interface, BGP or BGP, VPN, MC lag. So all those features are already supported in Sonic. We wanted to give a quick glimpse of it. So I just, so this is how simple it is. In a sense that you go to a Suzuki CLI, you say what is ARP? And then it gives you what you want to do summarize. And then it tells you, I want to see what all the ARPs at leaf one. You can dump for the entire data center or entire part, what you have. And you can specifically query, okay, I want to do this leaf. I want to do this namespace. Or I want to do, look at this part, right? It's the entire, it's one CLI. You don't have to log into any devices. It's one CLI where you can gather that insight, right? More better is the programmable interface. You can assert your network. You can do an upgrade and after upgrade and before upgrade. You can say whether is there anything down in my network? Right, it's BGPs. It's the way it's behaving. I'm getting all the routes which I supposed to get it. So you can programmatically verify, you can put it into your CI CD systems and programmatically verify this thing. And it also has a simple GUI to understand the path and other stuff. Whatever you're doing in CLI, it can be done via GUI as well. But I prefer CLI, we are network engineers. We're still using CLIs. But the way I think about CLI and seeing that as a single management pain, that's what opened my eyes in SuzyQ. That's why I allowed about the tool because it's immediately I've been able to understand the network. We just wanted to give a quick glimpse of what SuzyQ is today to you. So we have a short demo. Hello everyone. So we took this sample topology wherein we have two parts and then connected together with the central part. So in this demo, we are going to focus more on the part one. And then I have the SuzyQ inventory files. Basically, I have all the IP addresses mentioned there with the SSH connection towards all these part one nodes. So basically what I have is all leaf nodes running Community Sonic 2022 November release. And then the spine nodes are basically the Enterprise Sonic version distribution by Dell Technologies. So this is what the versions. No, I'm just showing what are all the things present in the Sonic switches. This is the version and all the various containers running in each switch. So now, and then we are going to the inventory file. Just I mentioned like the inventory file as the all the nodes IP address and then the username password. And this is the Docker I'm running for the SuzyQ with the port exposed 85 01 for the GUI. And then I'm basically starting the polar for the inventory file. So the polar could be continuous or the snapshots or continuous basically periodically pulls all the nodes and then stores the information in the big data like central mentioned. And then there's a snapshot view as well. So you don't want to continuously monitor, pull the nodes and then do it. If you want to just get what is the snapshot of my part and a given point in time, you can do that as well. So right now I'm just going into the Sonic SuzyQ CLI and then giving various queries, right? For example, device show. Device show is gonna tell us for a given part of what are all the nodes available and the IP addresses and the image being used in those nodes, et cetera. So and then there are various options as well in the device show. For example, you can group by columns, right? There are various columns you can just put. Okay, for a given part, what are all the most names available? So you can just group by most names and then there are other options under the device. Basically you can get what are all the images running on this part. So you can just basically based on this information you can see, okay, these are all the nodes needs upgrade for security or whatever reasons, right? So you can do all that. So and then the current tables, these are all the tables being supported in various NAS today. So we have enabled that support for Sonic as well. So this is gonna provide all the, you know, R, BGP, MLAG and all those informations are available currently. So you can very well enhance the code to have additional capabilities as well. So and then this talks about what are all the, what is the interval and how many rows are there in the database and all that. So based on this information, we are gonna execute the various other queries that are available, for example, BGP show. So BGP show is gonna show what are, how many BGP sessions are available across pod, right? So what is the AS number being used and what is the session state and et cetera. So and then there is a BGP asset. So it's gonna basically solve pass right now. So if there are some problems in the nodes and basically it's gonna mention that what is the problem and what is the current state of that particular node. So this way you can quickly debug and what's going on this particular node and then we can quickly recover from that. So the various routes summarize is gonna provide how many routes are there and then the various ARP information available in there and then you can see their status. You can basically filter by the particular leaf node, filter by IP address, filter by MAC address and the various options are available. In fact, you can use the regular expression as well to pinpoint a particular IP address from a given node and then the MLAG, MCLAG information is available as well. So what are all the nodes available and what is the MLAG role on that particular node? And then the VLAN show. So this is basically gonna give you the global view of what's available in the pod. So the VLAN is one example where how many VLANs are available, how many ports are members of those VLANs, all that information you can query and as usual you can put all the filters like any other commands we have. So and then you can route show, you can very well filter the various columns, various OS names, namespace, all those filtering logic and apply on the data available in the DB. So I'm going inside the core router now to basically bring down to showcase the asset functionality available in the Susie queue. So I'm just brought down one of the link. So this should reflect on the BGP session right now. So I'll just go back to the Susie queue CLI to execute the BGP asset to see what's the status of the, so right now in the Sonic you see the session went to idle state from established. So if I go back to the Susie queue CLI it's gonna reflect on the state and you can easily see it. So the result would be failed saying BGP notifications and the whole time it expired because we brought down the link. So this is one example. So there could be many things you can observe with this Susie queue. So like Sandil mentioned, there are times start time, end time and all those things are there. You can execute complex queries in order to get what's happening in the part network. So these are all the information. So you're available with Susie queue. With that I would like to end this demo and hand over to Sandil for any closing thoughts and call for action. Thank you. So I think, thank you Vangat. I think hopefully this would have provided a glimpse of what Sonic is and a good introduction to you. So Susie queue is a license and an Apache license so which makes it freely available to use for modification and an enterprise version is also available offering additional features and support. So here are the key resources. I wouldn't walk you through all these things. So there is your first stop is a GitHub where you can go and play around it. It's just four commands for you. You do a Docker pull, put your IPs and start the polar, you're done. So since it's a column or database, you can filter and query, you can slice and dice it any way you want. So that's what's more powerful about it. So key takeaways, right? So network observatory is not just another bus word in the IT industry. It's a crucial concept that has tangible impacts on the organization of all sizes, right? Achieving network observability comes with a plethora of benefits.  The first thing and foremost, I keep repeating this myself. Most of the customers we went and maybe go into, right? So they don't clearly understand what's going on in their network. So this provides you first and foremost to better understand your network. What is there in my network? I'm a running VLANs. How many VLANs are in my network in total? How many MAC address, what is the scale? Did I, my uplink is all almost done or how much is the bandwidth? Do I need to upgrade in the next cycle? Do I need to upgrade for higher grade switches? How many ports are still open? How much bandwidth still I can support? So some basic questions to start with some basic questions, some complicated questions at times. How my network has grown over the period of time. But it can do all those things for you, right? The key thing is about, so Suzuki also allows you to access information without risk of logging in, right? So that's a key feature I already talked about. So you don't have to log in each and every device. It's just one CLI, you do it. And then it takes away all the mechanics of parsing, coding and all those things from you because it's an abstract information. You can compare all this data across Sonic, Arista, Cisco, Juniper, everyone together, right? It gives you the same format for everybody. So it's easy for you to understand because most of the network has an heterogeneous network. So it provides a holistic over time. So that's the benefits of Suzuki and Sonic. So I would like to take a shot. And finally, as we come to the end of this discussion, the profound impact SuzukiQ can have in your network observability space. We'd like to take few calls of action. Firstly, encourage you to explore and understand what SuzukiQ is. It's much more simple. So take it for a test drive. I was telling Tim, it's just one command. Just right now we can pull in and then show we actually have a live demo we wanted to show you. So we didn't want this laptop. So that's why I stopped it. If somebody is interested, Wengat has this in his laptop. So you can play around with Suzuki if you want.  So take it for a test drive. Try to deploy it in your lab networks whenever you do lab. So see how powerful it is for yourself. And then come back and contribute, right? In conclusion, SuzukiQ is more than just a tool. It's a community as well. Like how Sonic, a growing community of dedicated network enthusiasts who are trying to make network much better, to manage the network much better. So we invite you to join this community, learn and contribute. Thanks for listening to us. If you have any questions, I'd be happy to take that. Yeah. I don't want to specify any names, but I know that few companies are already using it. It's been deployed. And they are all happy and they're asking for you and other nurses support for us from DelVial. So they're asking why can't you do this for other centers, right? So it's already deployed. It's not part of foundation. No, I don't think so. I'd love the question. Thank you. So I think this is valuable. I have not seen this tool anywhere in the open source out there. There are a lot of tools for monitoring and other stuff for observability in the application world. For networking, there's nothing there. This is the first tool, which we've seen and then got impressive. Right now, there's a very small community, which works on it. It's all GitHub. So there's no, it's not under any foundation. It's all in GitHub. Dinesh, Dinesh from Cumulus. If you... No, former cumulus employee and Amazon, Justin from Amazon. Now I think even Linux foundation, Nila is the co-founder right now because they saw the traction. I think they started an enterprise version of it. And Nila and Dinesh are heading that. Nothing, nothing. Yeah, just as I said, right? So when I implemented this for Sonic, we used, we didn't want it at the time because it's just 2020, the management framework is not there yet. It is not. So I tried to use, even though we internally had management framework, I didn't want to just support management framework. I wanted to be, it supports both community and Dell versions of it. So I used to implement this with the CLI piece of it. One thing, because it's already supported cumulus and FRR, it's much more easier to adopt to Sonic that way as well. So that is another reason why we went that route. So it was very, it's not a big effort to integrate Sonic into ZUZIQ. For that matter, any NOS, it's a straightforward way to implement, to bring in other stuff. Yeah, it is SSS access. Venkatak showed you how you can pull the inventory. You can pull the inventory from Netbox. You can pull the inventory from Ansible. You can use the keys. You don't have to use an Mpassword. So all those are supported. You just download the Docker. Update your inventory. Start the polar. That's about it. Once you have it, you have access to the CLI. And you'll be really amazed. I'm telling you. When you see that, the entire network and then seeing it one shot and then going for all the CLIs, if I do a MAC address and then say unique MAC address in the system or unique, how much devices I have. So it's one CLI for all the boxes. You have 1000 boxes, you just dump. It's thousands and thousands of rows. So it's up to you. How do you want to dice it and slide it in? Because there's a column at a database and it can go across tables. So you can mix and match however you want. Yes. Yes. And it's just scraping the data. And then if you think that it'll be a bigger burden, that each polar, each table has a separate timer. So you can tune it according to your network, how big your network. You don't want to pull that much. You can slow it down, fast speed it up. So those things are possible. It's pure CLI scraping kind of thing today. And you can use REST API as well. I would eventually want to migrate to the REST API and structured format, but right now it's all purely CLI. Oh no, REST API, Suzuki is still outside, right? There is no agent. So we are just making the REST calls to the Sonic and then get the data back, right? But it comes as a structured data. Right now I am trying to scrape the data with regular expression and everything. If somebody changes Sonic CLI, changes tomorrow, somebody will introduce a new CLI. My regular expression might not work going forward, right? I have to keep updating this text there for some formats to make sure that it's always compactable, right? So that's what the consides are. I would like to migrate to, as soon as we have the full management framework support. So we have the management, we are planning to additional supports for management framework is coming in Sonic, right? With that, we should be able to support all the future via the standard REST API formats. No, there is work required in Suzuki. It's other way around. It's reverse way. So what I do is because I am supporting Sonic, so I will go when the release comes out, I'll run Suzuki once, make sure that everything is there. It's not only me, there are a lot of folks in the community who actually deployed in Sonic, they are really interested in this one. So they have actually provided a lot of fixes as well, patches as well to this one. No, nothing like that. Yeah, anything more? Thank you. Thank you so much. I appreciate all your time listening in. Thank you.


Hi, my name is Prabhakar, I am with IIT Kanpur. In this lecture, let us look at phones, smartphones, phablets and tablets. So we know that there are phones and there are smartphones. So what is the difference between a phone and a smartphone? A smartphone typically is an advanced computing device. It has what we call apps, apps is an acronym for applications. It can run small programs. The user can program, anybody in the world can program which are loaded into the smartphone and they can be executed. Of course it also has advanced computing and connectivity features. By this we mean it has Wi-Fi and so on. And what is a phablet?  It is actually in between a phone and a tablet whereas a tablet may not be able to make a phone call, a phablet typically has the ability to make a phone call. So if you look at the progression of these devices, the smallest is the phone in size. The next is the smartphone and then we have a phablet and then we have a tablet. So what is the typical size of a phone or a smartphone to a tablet? So the sizes look like this. The size of device is measured by the diagonal of the screen. So it's normally measured in inches and if you take a phone or a smartphone it is in the range of 3 to 5 inches and a phablet is bigger in the range of 5 to 7 inches and tablets are in the range of 7 to 11 inches. Another parameter of a phone is how much does it weigh? So smartphones and phablets are in the region of 100 to 170 grams. Normally we are carrying them on our body in our pockets or purses and we don't want them to be very heavy and tablets because they are bigger, they are in the range of 500 to 700 grams, half a kilo. In terms of connectivity, these phones allow us to connect using cellular networks. We know about 3G, 2G kind of networks, we are going to study more of these in the rest of the course and then there is connectivity using Wi-Fi or Bluetooth. Many of them have speakers, loud speakers that in the sense you can get the volume loud. Some of you want to hear it together, you can keep the speaker on or sometimes when the voice is not coming out clearly having the loud speaker on is helpful. It has a microphone into which you talk to and then there are cameras, some of these smartphone cameras are actually very good and very powerful. They are even actually replacing point and click cameras. It has capacitive multi-touch screens and then you can connect through a what is called a USB port, it's a micro USB port. This is normally how it looks, this is the standard USB and this is the micro USB. Now what are capacitive multi-touch screens? These are screens with which you interact with the phone. You can give input to the screen to the phone. Capacitive as against resistive touch. Some phones earlier generation touch devices used to be resistive touch but they are no longer in vogue. So these capacitive devices actually rely on the electrical property of the human skin, the body to detect a touch. So that's why they are very sensitive and of course then you cannot use it with gloves and if you want to ride you need a special pen. If you are using a capacitive touch screen phone and you want to use a stylus then you need a different kind of pen to write with. These phones are supposed to be oleophobic. What is oleophobic screen? It basically means it doesn't smudge, the oil is repelling. Suppose for example I have the phone here with fingerprints on it, I just need to wipe it off and it will go away. So oleum is Latin, in Latin is oil and phobos is fierce, oil doesn't stick, oil is repelled. The screen is made of what is called Gorilla Glass which is very powerful and strong glass thin and strong and that's what is used in most of the phones. You can connect keyboards or mouse to interact with the phone and this connectivity is normally through Bluetooth connection. Now the battery is a very, very important parameter of the phone, normally it gives about 5 to 10 hours of working time. So the capacity of a battery is measured in what is called milli ampere hours and this number is in the range of 2000 to 10,000 milli ampere hours based on the size of the phone and whether it's a tablet or a tablet and so on. Obviously, a larger size means the phone will last longer before the second charge. Now a phone is consuming energy, right? It's you charge it every day or once into three days. So how much does it consume? Is it like an electric lamp or like a refrigerator or how much is it? So typically a smartphone is in the range of 2 to 4 kilowatt hours per year. A kilowatt hour is one unit, right? That means if you take a 100 watt lamp and run it for 10 hours, you will consume 1 unit. So that is the amount of energy that a smartphone consumes in one full year. Of course, a laptop for comparison consumes a lot more energy. It's about 20 times the consumption of a smartphone and of course, this is assuming that you charge it fully one every day. So whatever the capacity of the phone is, you charge it in the morning and let's say by you discharge it by evening fully, that means you have consumed all the energy in the battery, okay? That's when you get these kinds of estimates. It's about 3 to 4 units of energy per year. So homework for you, what is the capacity of your phone battery? Find out, thank you.


You're welcome back to the breakfast on PlusCV Africa. It's now time for Off the Press and I guess Mr. Crisland joins us now. Good morning sir, thanks for being here. Thank you very much for having a good party. All right, let's begin this morning with a daily independent newspaper. The headline reads Banks Boards Jittery as CBN moves to clamp down on insider abuse. Analysts ask APIS Bank to publish street stress tests on banks, once DMBs to improve and corporate governance disclosure. Above the headline on the daily independence, shut on site against Ibo Yute's call for another genocide and that's according to Orhanizind Ibo. NEF spokesman says Buhari should be impitched if he can't secure us. Below the headline on the daily independence, troops eliminate top bandits commanders, 48 others. FG considers 223 building component firms for social housing projects. Abdul Salami Ibo Bokhar denies link with bandits and tourists. COVID-19, FG reintroduces restriction on mass gathering. PDP demands AMHE Usman's sack over MPA's unremitted 165 billion Naira. Reps Minority Caucus asks EFCC to probe Hadiza Bala Usman. Peter will be alleged plot to link him with Southeast violence. And lastly, on the daily independence, Song Oulu gets Legations backing to tackle security challenges. All right, let's see what we can find on the nation. Newspapers this morning. The big one there says Southern Governors to take crucial decisions on insecurity. Delta to host Pali today. IG plans a synergy, rather with military. 11-man panel to probe NPA activities on that Bala Usman. Presidency confirms attempted raid on Gambari's house. 1,200 to benefit from quara interest-free loans. All right, it also says here, Diboye's son didn't die, but sleeping, says Wido. Don't understand that. Why COVID-19 restrictions are back, and that's from the Federal Government. Also on the nation this morning, Song Oulu gets full back into tackle security challenges. We can also find here. Wednesday and Thursday, of course, are holidays. That's the big ones on the nation. Newspapers this morning. On the punch newspaper, deadly COVID-19 variants. Experts warn as FG restricts gatherings, revives curfew, bans nightclubs and others. Government says worship centres shouldn't exceed 50% capacity, revives 12 midnight to 4am curfew. Learn from India's predicaments, virologist, advices Nigerians and Tamari backs federal government. Above the headline on the punch newspaper, Nigeria's fintech revenue to hit $543 million by 2022, and that's according to a report. Subsidy removal advice, wrong. Implementation, suicidal, says Nupeng. Presidency confirms attempted bogglary of Gambari's villa residence. Nigeria's economy is still fragile, despite exit in recession, Buhari's advices. Below the headline on the punch newspaper, our Mechi inaugurates panel to probe alleged NPA on rummated cash. iPob denies planned attack on Lagos. Police order probe. Cora floats 900 million naira, interest-free loans for 1,200 young entrepreneurs. Family kicks as murder suspect dies in police custody. Federal government declares Wednesday, Thursday holidays, and Nasrada predicts moon sighting. Minister leads delegation Sagana over Nigerian traders or deal. And we see pictures here, St Lagos's environmental special officers, units and tax wars at the Igomu on the bridge. And they're basically doing a three-day removal of illegal structures and vehicles there. That's the picture we're seeing there on the punch newspaper this morning. Alright, and now on the Nigerian Tribune. Security breach at Buhari's Chief of Staff, Aso Rock Residence. Presidency confirms burglars made foolish attempt. Arrested helicopter, ACF calls for full investigation, and the Salami denies any link with bandits. And also Buhari should be removed if he can't guarantee security. Baba Med, and that's a northern eldest forum, Spokesman. We're gonna be having a conversation with him this morning. COVID-19, security personnel to enforce use of face masks. It also says there, okay, all on public transport. Federal government reinstates restrictions on mass gatherings, event centers, nightclubs, and the likes. We can also find on the Tribune this morning, or your government promises to pay salaries and allowances of SAC, local government chairman, counselors. Another INEC office set ablaze. Also, gunmen abduct many in Katsina, Mosque, police rescue 30. Buhari moves to resolve Ghana-Nigeria trade conflicts, sends delegations. And also, a Mechi-Nogorets panel to probe policies and contracts done by HDISA since 2016. We can also see here NLC to ground Kaduna from May 16th over Worker's SAC. And Lagos Hold Security Summit issues 12-point resolution. That's most of the stories we're taking this morning. Mr. Chris Wando, good morning once again. Thanks for joining us. Thank you very much for having me. All right. I guess we can start from the tempted, like it's been described, or the boglary at Gambari's residence. Pretty embarrassing. What do you think? Very, very embarrassing for the Hoodlums or Amropas or whatever you call them to have found their way into Asorok. It's worrisome because Asorok is the seat of power. We are the president besides. And my first year of knowledge of Asorok is that we have about four gates into Asorok. So we are able to make their way into Asorok. And even with, apart from the gates, there are also about three or four levels of movement before you can get to the inner palace as I use it, of the villa. So the dead jump defense, which is impossible because that place is called the security appliances and all the rest of them. So that to me is it is a level of a security breach. And then to get as fast to the home of the chief of power to the president is as good as getting to the president. Because the chief of stars is the last point of command. And before they see the president, so I don't know how they were able to do it. And we had their cuts in the ads that are not true. So that's a very tough one. And that also shows that the level of insecurity in Asorok, the seat of power is not secured. Then you cannot imagine what's happened to the rest of us. So I think those in charge of security in Asorok should be questioned. Let me also bring in this. Yeah. Let me also bring in this quick angle to this. I'm just in a statement now from someone and it's asking, you know, is it important that we know if this happened with people from the outside or from insiders, because anyone who can get that level of access might have insiders that help them out. So should that be scary for the presidency? And should that also tell, you know, that there are people inside Asorok that cannot be trusted with president's security? Yes. I don't know if you know, you have the knowledge of Asorok as it's where my, I've been to Asorok several times. And also know that it's not just the seat of power that's in Asorok. There are several parameters in Asorok. I know that even EFCC used to be around there. There are some MBC, EFCC and some of those parameters were used to be in Asorok. But as I said, Asorok, there is Asorok and there is also Asorok. So there is other Asorok and the inside Asorok, because the presidential bill that you have to pass about four levels of security before you can get to the actual presidential. But within the Asorok also, I also know that some people that are not working in the presidency are living in Asorok. So I don't know, so whether it's an insiders job or people that came from outside, but we're not able to do that. We have hard access into Asorok, either as the people living there or people that came from outside. And whether they are able to enter Asorok is what is something. And that's why I said that the security actors within the villa should be regained and the investigation should be carried out thoroughly to be able to find out where this book came from. It could have been worse. I don't know what they had if they had other motives and they could have done a lot of damage in Asorok. Because what's the idea? You don't know what the person have. Suppose if the person have a propeller or if you understand what I mean, those high caliber hands and the rest of them can shoot into the villa and the rest of them. That in a sense is a serious security breach which should be investigated and should be carried out. But Gerva Sheva, just this one has dictated that treat if you are aware. He has dictated that treat, but he made that treat acknowledging that invasion. All right. Moving away from security matters to, well, still health security more specifically.  But the thing here is that many Nigerians seem to have the impression that there's, you know, no more COVID-19 in Nigeria. You know, but with this new curfew now, it might gel to Nigeria back to reality, you know, in some ways. But do you think a curfew is enough to create that social distance to prevent the spread of COVID-19? Or do you think what Nigeria needs to prevent being in the situation where India is right now is a total lockdown? Mr. Wando, it seems to have lost you there. All right. I think we've lost sound from Chris Wando who would have to reconnect with him and continue this conversation. And good point, there's COVID only come out at night. Of course, or does it of course exist in the daytime also. I think, you know, there's maybe some way to tackle the, you know, the people going to nightclubs and having night events and things like that. But if there is already a ban on nightclubs and I don't know why there is a curfew, you know, and why there's restriction of movement to 4 a.m. There's people who've complained about flights leaving as early as 7 a.m., so people need to leave at 4 or leave early at 4 to get to the airport, you know, which I feel there's still enough time by 4 a.m. to get to the airport or whatnot. But the government will probably have to give a clearer picture of why there's a 4, a 12, a midnight to 4 a.m. curfew and what that is, you know, hoping to achieve. And there's all the other things, you know. So let's not have the conversation as, you know, the curfew is the only COVID-19 guideline that has been put in place. It's not just the curfew. There's also limiting movements. It's shut down of gyms and nightclubs and cinemas and the likes. There's also a reduced number of people in churches and the likes of 250 people. Chris, I want to welcome back. Thank you very much. So, but it's not just the curfew alone. Also the restriction. When it comes to gym, places, event centers have been shut down and the address is no more than 50. Those are part of the protocols they put in place. But for me, the most important thing is that how far have we gone with our vaccination because that seems to have totally stopped. And so many millions of Nigerians who are willing to get themselves vaccinated have now been vaccinated. The last count, without only about 3.9 or 4 million doses shared into two, that is about 2 million averagely Nigerians out of 200 million Nigerians that have been vaccinated. I got, of course, in the first job and this was in my second job in about a few weeks time for me to go for my second job. But there are so many Nigerians who are willing to have this vaccination and they don't have it. And what has the government been doing about it? What is happening in India? Don't forget that India is a serious challenge and India in the past has been able to provide us with some thousands of vaccines. And there is no place, most countries are not given out or selling vaccines now because they are also in gravity. We should see what is happening in Brazil and other parts of the world. So, Bex, let's see how it goes. The government, the authorities must have gotten their reasons, have their reason for the best. My issue of, my problem is that of social distancing, we don't observe social distancing. And a lot of people are not using their masks. In fact, people are practically discarded their masks.  And let's see how they are going to be able to take these and moving forward. All right, Miss, I want to do another story here. It's on the nation newspaper. It says 11-man panel to probe NPA. That's the Nigeria Port Authority activities under Balakusman. So, there's been lots of controversy regarding the story. Recall that she's first of all been suspended ever since last Thursday.  You know that 1.5 billion era was in trillion era was involved. And that there's allegation that she had reduced the amount that Dangute should pay for what he clears at the port. And they're basically saying that there's lots of irregularities with her policies, while as boss of the NPA. So, they're now calling for an investigation. Your thoughts on this, Miss, I want to. I don't think it was the APC caucus. I think it's the PDP. The PDP. Yes, it's the PDP, the minority party. But as it were, it's also within the range of allegations and an accused is deemed to be innocent until he or she must have proved committed offense. So, I think which, yes. So, for me, is still within the range of accusation. An 11-man panel has been tutors to look into that. And they've been narrated by the minister. Yes, the former or the suspended MP is also fighting back with certain information and stuff like that. I think everybody should wait for the outcome of that panel. My problem is that the way we do this set of panels at the end of it are nothing comes out of it. Don't forget the one of NDIC. I'm sure you still remember that we have practically gone to sleep with that. NDIC. Yes, yes, yes, NDIC, yes. They were practically going to sleep with that. Yes, the president also set up a forestry investigation panel to look into that. Couple with that of, you remember the drama that happened of your mic on the door or for your mic, put on your mic and painting and not painting. And at the end of it, what came out of it is like we are human drive. So there are several investigations in the past that we don't even into what we see is just the beginning. We don't get to see what happens at the end of it all. And whatever recommendations we made, we are not implemented. I hope this will be another one. The NPA is one of our cash cow. If you take away the oil, take away the IRS and that of customs revenue generation, NPA stands within the big five, six organizations that we get remittances from. So we shouldn't let this be like what it used to be. It should be a holistic investigation, devoid of any political learning and the rest of them. So make sure that whoever is copy it is able to book. All right. There's also a question I want to ask. Why do we keep going through the root of certain panels when we have the ICPC, we have the EFCC, we have forensic agencies that can do a proper audit of their funds and of their finances in the last couple of years? So why are we setting up a panel? Isn't that just wasting time? I agree to which is wasting time most often than not. Even after the panel must have submitted or you come to see that another subcommittee or panel will be set up to look into the recommendation of that panel. You know that's how we go in this country. So, but also a panel can do a job more quickly, I believe, than the graph agencies. Don't forget they have so many things on their table. They have so many things that they're investigating and that EFCC for one, I agree that EFCC has gone overboard. It's not focusing fully on the score mandate. They are engaging so many other things that personally I think is taking so much of their time where you go and pick some boys. You see that for them, where you are who boys, we go and pick hundreds and hundreds of them, procedures and the rest of them. They don't have the capacity and you just forget. Don't forget a few days ago, Inspector General Police, we drew several senior officers from EFCC. Those are part of the group that helped them in their investigation. So, they have the capacity to be able to run through all these ICPs in this. For me, it's neither here nor there. So, if there is a need to set up a panel that can equally wrap up this, for a panel, you can give a mandate and a time frame for them to finish. You can say within two weeks, within three weeks, within four weeks, and they get that wrap up. But if you're looking for graph agencies, they might continue investigation for a whole year or two and at the end of it, so that's where we stretch. But, ordinarily, that's what they're supposed to do. Even the police, don't forget that the police, it's also how they mandate. There's the fraud units within the Nigerian police that are supposed to handle issues like this. You remember the police have that mandate too and they could have been engaged.  But it's not just the ICPC, not just the EFCC. The police have that mandate and they have a special unit that investigates such. So, I believe that if you can be able to get them to be able to get this job done as quickly as possible, well, I'm going back. The panel has a mandate. We cannot give the police a time frame of two weeks to submit a report because the police would probably not be able to finish their investigation. But the panel has a mandate within which to be able to do this and that is what they do, 100% and they come up with it. Remember, if the apologists were dragging this so too long, if they had even the graft agencies, the actual graft agency or anti-graft agencies that have been set up, including the police, need a specific amount of time. They need to investigate for two months or for one month. I'm not sure how long it takes. Maybe because of their inadequacies or because that's the time that a proper investigation is required, a proper investigation will be carried out. Then how does a panel finish in two weeks and what do we hope to achieve from a panel in two weeks? If the graft agencies will take six months. I'm using two weeks as a time frame. I don't know the time frame that was given, but what I'm saying is that for the panel, that is the sole job they're going to do, 100%. If we put that time 100%. Why I'm asking is because... Obviously, you're going to get from EFCC or... Yeah, why I'm asking is because if we need to do a proper job, then, of course, these anti-graft agencies should be involved and not a panel that should be given a time frame or whatnot. Not a panel that we also trust has people that are certified and qualified to do a proper forensic investigation into a financial fraud, but we would see. It's another opportunity, I believe. Let's quickly come in there. It's just a short call. What I would rather stress about that is that, whether we can aim for some... EFCC1 is into that group panel. You understand what I'm trying to say? So, if we can embed people from EFCCC, from EFCCC, from EFCCC and other from the front unit of EFCCC, add them to the party, then they'll take a more good thing. But the members of this panel, I don't know who they are. I don't know that they are coming from my press talk. That's what it's very, very important to be thinking to their time frame on their mandate. Let's just see what happens. Okay, well, it's another opportunity for the government to show its stance with regards to corruption and fighting corruption. There has been Babacir Lawal. There has been the NDDC, like you mentioned. There's been numerous different opportunities. So, let's see how this one turns out and how it plays out. But thanks anyway for joining us this morning, Chris Wando. Thank you. Thanks for your time and for sharing your thoughts with us. Thank you very much. Do have a nice day. Absolutely. Stay with us this beautiful Tuesday morning. We, of course, have taken a short break. When we come back, we're sharing with you what happened on this day in history, the 11th of May, many years ago. We'll be back.


Not the best day. My knee kept me hesitant. I couldn't jump 100%, so that kind of shut down the session. But I had some really high jumps when I was feeling good, but it was hard to push it because every jump I was thinking about it a lot. But other than that, feeling really good. Drip was feeling really good. But again, the knee just isn't letting me go 100% or push it. So until next time, I guess. Who's this hair doing? But I don't know. It was fun. It's still a lot of fun. I should have done a lot better, but I'm going to take it easy. Gotta be smart. Gotta be patient.


Live from Las Vegas, Nevada, it's theCUBE. Covering Accelerate 2017, brought to you by Fortinet. Now, here are your hosts, Lisa Martin and Peter Burris. Welcome back to theCUBE. I'm Lisa Martin joined by Peter Burris. We have been in Vegas all day at Accelerate 2017. What an exciting, buzz-filled day that we've had, Peter. I feel like we've learned, I've learned a lot myself, but also just that the passion and the opportunity for helping companies become more secure as securities evolving is really palpable. Well, yeah, I totally agree with you, Lisa. In fact, if there's one kind of overarching theme of what we heard and what we experienced, this is one of the first conferences, security conferences that I've been to where we spent more time talking about business opportunity, business outcome, the role that security is going to play in facilitating business change, and we spent a lot less time talking about security speeds, security feeds, geeking out about underlying security technologies. And I think that portends a pretty significant seismic shift in how people regard security. We'll still always have to be very focused and understand those underlying technologies and the speeds and feeds. But increasingly, the business conversation is creeping into and, in fact, starting to dominate how we regard security. It has to become viewed in a digital world, it has to become viewed as a strategic business asset, and not just as the thing you do to make sure your devices don't get stolen or appropriated. Right, and that context was set from the beginning with the keynotes this morning, the CEO, Kenzie. A lot of folks that we talked to today said he normally gets quite technical in keynotes, and today kept things really at a business level. And we heard that many people thought it was the best keynote they've seen him give in a long time. That's right, that's a great point. And one of his key messages was that at the end of the day, digital business is not about some new observations on channels or new observations on products, it really is about how you use data to differentiate, differentially create and sustain customers. My words, not his, but it's very, very much in line. The difference between any business and digital business is how you use your data. Right. And we heard that over and over and over today and how security technologies and practices and capabilities have to evolve to focus more on what businesses want to do with data. And that is where certainly Fortnet sees the market going and they're trying to steer their customers so that they can take advantage of those opportunities. Right, and that's a great point that you made. There's CFO, who we had on the program as well, Drew D'Amato talked about in his keynote that it's critical for a company to be able to have digital trust. We talk about trust in lots of different contexts, but what does trust mean to a business? Well, and he was, and as you said, he's the CFO. So, yeah, absolutely. It's interesting to, you know, CFO is typically focused on things like how are we, is the ownership getting a return on the capital that they've invested in this company? And it was very, to me anyway, refreshing to hear a CFO expressly state data is becoming an increasing feature of the capital stock of the company. And we have to take explicit steps to start to protect it and secure it because in fact, it's through security that data is turned into an asset. If you don't secure your data, it's everywhere because it's easily copied, it flies around. Data and security are, at least data asset, the concept of data asset and security are inextricably bound because it is through security that you create the asset notion of data, the thing that generates value. Because if you don't, it's everywhere. It's easy to copy. And it was, I thought he did a wonderful job of starting to tie together the idea of data in business in a very straightforward tactical CFO approach. And it was a good conversation about where business people are starting to think about how this is going to evolve. Right, he also talked about the role of the CISO and there was a panel on during the general session of three CISOs from different industries. That's an interesting evolution as security has evolved from perimeter to only to web to cloud now where we need to be as Kenzie talked about, we're at this third generation, right, it's about fabric. He talked about that and the importance of that and the capabilities. It is also interesting to hear, security is now a conversation in the boardroom. This is not something that is simply owned by a CIO or a CISO that that role has to facilitate kind of this, a company becoming a digital army in order to create value from that data. And a lot of folks said today too that mindset of, if I can't see it, I can't protect it. Yeah, we heard that from, we heard that this morning from, as you said, the CFO. We also heard from George from the CISO of Azure. Yes. Microsoft Azure. We heard this, we heard the relationship, the evolving role of the CISO or the Chief Security Officer multiple times today. Look, security's hard. Let's, you know, this is not easy stuff. We can bring a lot of automation and we can bring a lot of technology to bear on making it easier and simplifying it. And we heard a lot about how that's happening. But this is a hard, hard thing to do for a lot of reasons. But it's one that must be done, especially in a digital world. And the role or the impact on the CISO role is profound because you're not going to have everybody in the organization be have a, they all have a stake in it, but they're all not going to perform security routines necessarily. Yet it's too big, as we heard from George, for one person. And so we have to start increasingly thinking about security as a strategic business capability that may be championed by the CISO, but is going to be, is going to be undertaking in a lot of different places. And one of the things that the Microsoft gentleman, George Moore bought up, was the idea that increasingly, if you do security right, you can secure things at a relatively technical level and present them as services so that other parts of the business can start to consume them and they become part of their security architecture. And that goes into their products or it goes into their services or it goes into how they engage customers or whatever else it might be, logistics. And I think that that is a very powerful way of thinking about how security is going to work through a fabric being able to present a hierarchy of security capabilities that go all the way out to your customers and actually allow you to engage your customers at a security conversation level. Which is, we also heard that talked about a little bit today, the role that, you know, the brand value of trust. But we still don't have an answer for how that's going to play out. Right. So we look at some of the other things that were talked about in Ken's hyper-connectivity. So from the proliferation of mobile and IoT, which IoT devices is what, 20 billion that are predicted to be connected by 2020, which is just a few years away. As that sounds, well it doesn't sound, it is increasing the threat surface. And we are also hearing from some of the folks that were on the program today, Derek Mankey being one of them who wrote a great blog just published recently on Fortinet talking about the major trends that are being seen and the challenges there. I think we're also seeing that companies like Fortinet and their suite of technology alliance partners like Microsoft, like Nizomi, going all the way out to the endpoints and back that these companies are coming together to collaborate to start mitigating the risks that are increasingly there with the threat surface being larger. I think there was a lot more positivity than I honestly anticipated when you hear of all these attacks that it's daily and that's such a common thing. The collaboration of the technology and the integration is exciting to hear where these companies are going to be able to limit damage. Well, yeah, and to put one more number on it, the 20 billion devices, but it's what those devices are doing. So again, George Moore from Microsoft Azure talked about, I think he said it was 800 billion events that they're dealing with today. And in 2017, Microsoft Azure is going across the threshold of dealing with one trillion events a day that they have to worry about from a security standpoint. And that if you think about that industry wide, Microsoft Azure's big, but there are others, we're talking today probably somewhere I just estimated, he said, yeah, that sounds about right, about five trillion, five trillion events a day that businesses have to worry about in aggregate from a security standpoint. And that number is just going to keep growing exponentially. In a year's time, he talked about three, four, five X. So we're talking about hundreds of trillions of events within the next decade or so. And there is virtually no way that human beings are set up to deal with those kinds of numbers. It's going to require great technology that provides great automation, that nonetheless works with humans. So that the discretion that human beings bring, the smarts and the collaboration that human beings bring to bear and the value that they create stays there. So we're going to see more productivity coming out of these incredibly smart people that are doing security because the tooling's going to improve and make it possible. And if it doesn't happen, then that's going to put a significant break on how fast a lot of this digital business revolution takes place. Right, from another point that was quite prevalent a lot among our conversations today was that there isn't, with the exception maybe of healthcare, it's quite an agnostic problem that enterprises are facing in terms of security threats. When we talked to Derek, he mentioned healthcare being one because that information is so pervasive, it's very personal and private. But something that kind of surprised me, I almost thought we might see or hear about a hierarchy maybe healthcare or financial services. But really what everyone talked about today was that the security threats are really pervasive across all industries, all the way even to industrial control systems and HVAC systems, which shows you the breadth of the challenge ahead. But to your point, and some of the points that some of our guests made, it's going to be a combination of the humans and the machines coming together to combat these challenges. Well, I think what we're seeing is that, is that there's a high degree of data specialization within a lot of industries based on different terms, different tactics, is different risk profiles, et cetera, but that many of the algorithms necessary to understand exceptions or deal with anomalies or one of those other things are applicable across a lot of different industries. What we are likely to see over the next few years is we're still likely to see some of that specialization by industry, by data, nonetheless become featured in the output, but the algorithms are going to be commonly applied. And they'll get better and better and better. So there's still likely to be some degree of specialization if only because the data itself is somewhat specialized. But the other thing that we heard is that it's pretty clear that the bad guys want to get access, well, let's put it this way, not all data is of equal value. And the bad guys want to get access to the data that is especially valuable to them. And a lot of that data is in healthcare systems. And so to bring these common algorithms that specialize data to secure the especially challenging problems associated with healthcare is a real, real big issue for a lot of businesses today. Not just healthcare businesses, but people who are buying insurance for their employees and et cetera. Yeah, exactly. So it becomes a pervasive problem. You were mentioning today that this was very much a business conversation versus speeds and fees. We did hear about a couple of technologies moving forward. There are going to be key to driving security forward analytics, data science. In fact, we also talked about kind of the difference between security fabric, which Fortinet rolled out last year and a platform and how a business needs to kind of mobilize around that. And the difference is their control versus spreading that out. But one of the things that Fortinet did about, I think it was in June of last year was they acquired ExcelOps. So bringing in monitoring, bringing in real-time analytics. And a lot of our guests talked about the essentialness of that real-time capability to discover, detect, remediate, and clear things up. So that was from a 2017 perspective, besides analytics and data science, what are some of the other things that you see here as essential technologies to facilitate where the security evolution trajectory is going? Well, I think, in many respects, it comes back to some of the things we just talked about, that as digital business increasingly, I mean, well, let's step back. The way we define at Wikibon Silicon Angle what digital business is, what differentiates a digital business from any other kind of business is data. It's how you use your data to create and sustain customers. Now, that's a pretty big world. There's a lot of, you know, most of us operate in the analog world, and there's some very interesting ways of turning that analog information into digital information. There's voice, there's photographs, there's a lot of other different, we talked a little bit about industrial internet of things. There's an enormous set of investments being made today to turn that analog world that all of us operate in and the processes that we normally think about into digital representations that then can be turned into models for action, models for insight, new software systems that can then have an impact on how the business actually operates. And I think that if we think, you know, that the notion of analytics and data science, and by the way, security is one of those places where that set of disciplines have really, really matured through fraud detection and other types of things. But I think what we're going to look at is as new types of data are created by different classes of business or different classes of industry or different roles and responsibilities, that that data too will have to be made secure. And so what we're going to see is as the world figures out new ways of using data to create new types of value that the security industry is going to have to be moving and lock step so that security doesn't once again become the function that says no to everything, but rather the function that says, yeah, we can do that. We can go from idea to execution, really fast because we know how to make that data secure. Exactly. Well, Peter, it's been such a pleasure and honor co-hosting with you today. Thank you so much for sharing the desk with me. Absolutely Lisa. Look forward to doing it some other time. And we want to thank you so much for joining us on theCUBE today as well. Want to also point you to some of the upcoming events, go to SiliconANGLE.tv. Just next week we've got the VTUG winter warmer going on. You'll also be able to see that on the website. Women in Data Science with yours truly in early February and then the SPARK Summit in February, that's seven through nine in Boston. Again, that's SiliconANGLE.tv. For my co-host Peter Burris, I'm Lisa Martin. And thanks so much for watching and we'll see you next time.


Okay. Hello everyone. This is Thierry Carras and I'm the release cycle management PTIL, which means I'm leading the team that is working on release cycle management things. And if we look at the next slide, you'll see that we usually describe release cycle management like this, like six months ago I would have said we do integrated release management, we do the coordinated release at the end of the cycle where we produce on time the set of projects that were part of the integrated release, we do stable branch maintenance, and we also looked over the team that does vulnerability management in OpenStack. But that changed a lot in the new cycle and on the next slide you can see that there are a few words that are crossed. And the reason for that is we pushed a number of changes in the governance of the project. On the next slide you can see that there was a project structure reform that was put in place during the Keto cycle. And it can basically be summarized as big tent and tags. The big tent side of things is that we are now recognizing projects as being part of OpenStack if they help with the OpenStack mission and if they are developed in the OpenStack way, which is way more inclusive than the previous way of describing OpenStack more as an integrated release single product. Now it's more like a collection of projects that all help in the same problem space and are all developed with the same values. The second part of the reform is that while we are adding more projects inside OpenStack, we are also providing clearer information about those projects and provide more precise answers to the questions that our downstream consumers of that ecosystem will have. So rather than have a single answer and say, well, you're part of the integrated release or you're not part of the integrated release, we are now providing a much richer explanation of where a project does fit in the ecosystem and what type of attributes it has. So that project structure reform basically created a few differences. One of them is that it's way easier to create project teams now in OpenStack than it used to be. So on the next slide you can see that we've been forming a new team dedicated to security called the OpenStack security team, and that's the reunion of the previously called OpenStack security group which was a set of experts working on security architecture in OpenStack and the reunion management team which was part of the release cycle management team and that team handles incident vulnerabilities and makes sure that we issue patches for vulnerabilities found in OpenStack projects. So those two were pretty linked. They were acting pretty close but they were not an official OpenStack team until the big tent was set up. So now we have a single team called the OpenStack security team which is led by Robert Clark and that team has two subgroups, the previous OpenStack security group and the reunion management team. And they all have a single portal that lives at security.openstack.org so if you're interested in security things that's your way to go. So it's no longer part of the release management team. It's one of the changes we've made. The second change on the next slide is that we no longer have an open stack release per se. We no longer have this closed set of projects that make up the OpenStack product release every six months. We have a larger collection of projects that are all OpenStack projects. There are still, according to the release, at the end of a six months development cycle though. There will still be an OpenStack release at the end of the liberty cycle that we are currently in. But it's an opt-in release for all the projects in OpenStack that make a release at the end of the cycle. They can be part of this coordinated release at the end of the cycle. It's no longer a closed set that is excluding most projects from appearing inside the project that is available. We are also working on refining processes and tools so that they are more self-service. Since we'll have to support a lot more projects, we also need to make sure that it's way easier to do releases and to do them in a very common and streamlined way. So we are working a lot on the tools, on the processes so that every project can be more independent in the ways they are doing their releases. And what binds the demo is the development cycle. We still do a six months long development cycle. We are still organizing the development of OpenStack projects in six months increments. And that's what binds all those projects together. Next slide. We are seeing another change that we need to push in liberty, is we are switching release tracking from predicting to reporting. We used to try to predict what features and what is being worked on and when that will land in the next cycle. And during the last few cycles it was pretty unreliable. We did a pretty bad job at trying to predict what would be in a given milestone in a given version of the software. So rather than doing a very bad job at trying to predict what will be in the next milestone, next development milestones and next releases, we decided to do a much better job at reporting what was actually done during those milestones. And let groups that are more focused on the long term view like the product managers that are working on trying to get a more roadmap-like approach to what gets done in OpenStack let those people actually work on predicting the trends and the next future, next priorities for the development. So as far as release management goes, we are only tracking what gets done rather than trying to predict what will get done which makes our job a lot easier so we can replace the sync points we had with the PTLs every week with office hours. So the PTLs and the release liaisons for each project can join us during office hours and ask questions they have about release management rather than have set sync points every week which was extremely time consuming for the release management team. We also have a new page at status.openstack.org slash release which shows this new release tracking report and shows all the features that are being already landed in the current development cycle and what is in the pipeline coming up. Next slide. Yes, so with the release management, we have a number of changes we need to push due to that switch to not having an integrated release anymore. So we support more release models than we used to. A lot of projects want to now follow on the footsteps of SWIFT and do intermediary releases in the middle of the cycle. So we are enabling them to do so. It's a natural consequence of projects getting more mature and more stable. You can actually release more often and deliver new features to your user base rather than have to wait for six months at the end of the cycle. To that effect, we are pushing for separate versioning for components. That means since every project will be able to do intermediary releases, we need to have version numbers that enable them to do so. So rather than have these date-based version numbers that we had previously like 2015.1, we recently switched all projects to a new major version number based on the number of integrated releases they had in the past. So the next NOVA release, for example, will not be 2015.2 but 12.00. And that will let projects evolve at their own pace rather than the time-based pace. And we'll be more precise for going forward. Each project will be able to switch to a version number that describes better the number of releases they are making. We are working on streamlining the library release process which used to be a bit of a mess. Every project was releasing libraries, announcing them, maybe not announcing them, sometimes tracking other projects because they weren't releasing at the right moment. So the release management team is expanding so that we can handle the process of tagging new library releases and ensure that all the processes follow along the way. Next slide. So in summary, in the Liberty Development Cycle you will have projects following a six-month time-based cycle and those will have a number of development milestones. The first one is this week on Thursday. The next one is at the end of July. And the third one will be September 3rd and that coincides with feature freeze for those projects. Then they will do release candidates like we always did up to a final release on October 15, 2015. And at the same time we'll have projects like SWIFT and Ironic, maybe others that will do releases, intermediary releases as needed. And they will do a final Liberty release which will also be included in this final release of the Liberty Cycle on October 15. So you can see that you will have projects on one side that are more traditionally in very active development mode that can only do development milestones during the six-month cycle and projects that are slightly more mature which can do more usable intermediary releases and will have a final release in October as well. Next slide. So what makes that final release different is that we'll have a stable branch out of it. That means we'll maintain a branch where we can push back ports of bug fixes, important bug fixes, vulnerabilities. And only this final release, the final release of the Liberty Cycle will be supported like this. So if you have intermediary releases and you install them, you don't have the additional comfort of having a stable branch that you can get critical bug fixes out of. Those stable branches, there will only be one per development cycle, like I just said. We also have a single stable branch policy across them. We have a team which ensures that only appropriate fixes are merged into those branches. We make sure that we don't break backward compatibility, that we don't add new configuration options, we don't add new features, we make sure we don't change the database structure. So those fixes are relatively safe to apply. We have been questioning the interest of doing stable point releases on those stable branches. We traditionally did, at the moment in time, like two months after the kilo release, we planned to have a kilo point one, basically a tag for all the projects that were part of the integrated release to mark the passage of time, basically. And we don't think that has that much value anymore, and it's becoming more costly to organize due to having a lot more projects that do stable branches. So it's still being discussed on the main list, but we might switch to just maintaining stable branches rather than also doing stable point releases as well. As far as stable branch support phase go, Juno will be supported until the Liberty release, that's 12 months. And for the kilo release, the current plan is to support it for nine months. And the reason why is we have a pretty complex setup for handling requirements around stable branches. We hope to make fast progress in fixing that in the upcoming cycle. If we do fix it, then we'll be able to extend the kilo support period, the kilo stable branch period, up to 12 or 15 months, but the current plan is to play it safe and announce that we'll support it for nine months unless we manage to fix the world. Okay, to have the next slide. No, that's all. So that's all for release management. It's more changes than we used to do. And like I said, we've been ramping up new members in the team. Doug Elman has been joining as co-release manager for this cycle. We have a number of library release managers working on that streamlining library release process. And so that's a lot more than I used to present on those PTL webinars. I hope you found it interesting. And see you probably in six months.


Welcome back to Tennis Talk, my name's Cam Williams and world number four, Alexander Zverev has commented on the interview that came out last week involving his ex-girlfriend and allegations of domestic abuse. Zverev has just come out with a statement over on Twitter talking about the legal proceedings against this article. This is what Zverev had to say over on Twitter. He writes, I have engaged my German and American lawyers in the matter. They have already obtained a preliminary injunction against the source and the author who published the false allegations. The court followed our arguments and states, the accusations aroused a defamatory and false. The lawyers have therefore initiated further proceedings against the source and the author. Categorically and unequivocally the night having abused Ola, I also fully support the creation of an ATP domestic violence policy. I will not address this matter any further. So there you have it, the statement from Alexander Zverev and he has been questioned over the last couple of days at press conferences regarding this issue and regarding comments about the article in general that he doesn't want to talk about any further and it's only days away from the US Open. The US Open is starting on Monday and he is one of the contenders to win the whole tournament. He's in great form right now. So let me know down in the comments below. Do you think this is going to affect his on court performance? Because we have seen in the past when he's had battles off court with lawyers and legal matters, he had problems on court and affected his on court performance. So let me know down in the comments below. Do you think this is going to affect his chances of winning the US Open or do you think he's going to be fine and he's still going to be a big contender going into the US Open starting on Monday? So Alexander Zverev, he's in another legal battle just days away from the US Open starting.