modular VDEplug: switchless switching networks (and libslirp)
Davoli, Renzo
The new VDEplug code now supports a URL-like syntax to define the virtualnetworking system to use. While it is backward compatible, and it is supportedby many VM (kvm/qemu, virtualbox, user-mode linux, umview), now it is possibleto add the compatibility layer for current and future virtual networkingenvironments. Currently VDEplug supports: legacy VDE, point-to-point AF_UNIX or UDP, tap,vxlan, vxvde, slirp. In the developing phase of the slirp plugin, we have implemented a generalpurpose slirp library (derived from qemu's slirp implementation). VDEplug4 together with new tools for the management of namespaces andcapability create a new ecosystem for the support of virtual networking.
 Okay. All right. We're ready to start our next session. Again, this will be a short 25-minute session. The next thing about modular VDE plug is Professor Renzo Davali from the University of Bologna. Okay. Welcome. Hi. Is my working? I don't think so. Maybe. Okay. Now I think it's great. I'm presenting this talk trying to get you to update about the new developments of the virtual square tools and concepts, especially in the part regarding the networking. It will be a common line seminar. So these slides are VI's slides. Just... So, VDE, the name of this development is a tool that is quite used in the world to create the virtual design. The name says all of it. There are virtual switches which are processes that works as physical switches so you can plug the virtual machines. Now we're designing all the tools. And we'll start with the VDE plug. The new plug is a tool and a ladder. It's the ladder that many common virtual machines and other tools use to connect with VDE. And it's a tool to connect several networks. What we designed this for many point of view. First of all, we have created a new syntax app to name the VDE networks. It's similar to a URL and you can see which technology you're using and specifications. And it's playable so you can add your own implementation of the network. If you want to use a technology, say, full, you just have to create a VDE plug, the underscore full, but I saw a short ladder. And you have to plug the VDE to use that kind of implementation. We have implemented the connection with the latest VDE switches. But this is not interesting. We're going to pass to. We can join top VDE interfaces, VDP, PDP, and so on. This is just a new point in the dimension of flexibility. But there is much more. We're going to come back to this slide. I'm going to show you this. The XVDE, I live in Tories today, Tories ago here, is called SEM. It's a way to create a local data cloud. Instead of connecting a virtual machine to a local switch, you connect a local virtual machine or as you can see in a moment, your main space to a local cloud. This local cloud is identified by a multicast IP address. So you can have so many local cloud relays as many IP multicast addresses you have. And the usage is like the world. Because we just put a VDE specification. That's strange. And we have connected. I couldn't come here with an entire data center. But I have a RascalPy on the table and so I have a space that is centered in this by my laptop and the RascalPy. Which are just on the same run. There are no processes running. And I can start the virtual machine on my laptop. Let's say a KDM. So X3 disk answers. Let's talk this. There is a comma, you can say on the top. I just have one more specification. You can say it's a laptop. But it's really interface is a little bit clear. Because now my default cloud is on the Wi-Fi. So I have to say that I have a lot of use with the cloud on the internet there. I can start this. And now I can show you another tool. I can here. Again. When you're in a hurry you get your own U2. That is okay. I log in to my RascalPy. Provide a network. Okay. Run password. Okay. And now I use another tool. VDNM space, VDNS. Which creates a username space that is connected to VD. So VDNM space. And now I can say mix VDN. I got a username space. I just use a null taxes, not capabilities. And here I can add an address. Then I do a URL. It links to the VDNM app. And now on the VDNM machine which runs on my laptop. I pay at $10.00. That was $2.00 for one. There is an error in configuration. That was $80.00. IP address. Okay. That is okay. I've seen a mistake. There is not the mask. So I have to delete this and add the mask. Add the mask slash 24 otherwise it's not working. 10.01. That's working. So there it is. I have to do that way. There it is. You can have so many hosts in every little center connected to the local network. And then you can start any kind of VN namespace on any host in your local network and connect it to VDNM. VDNM creates a VDNM switch on the network. And I can, I, is it implemented? The reason that the MIDI plug library which is on H2 is I can multicast to send all the one packets, broadcast, unknown circuits, and multicast packets. So if you're sending an app packet, the app packet is an embedded in a multicast packet and sent to a multicast address. So everybody is receiving and that multicast group is receiving the packet. But in the same time it gets the IP address and port of the sender. So like a switch, this will be plugged, this will be plugged, and this will be plugged into the IP address and port of this as the sender of the packet. So like a normal switch, an IP address and port have the same meaning for this is you put a switch at the port and a physical switch. So from now on, if this will be plugged, it can send just the two packets, the multicast packets back. It is similar to what happens with the Wix LAN. But Wix LAN needs what is called a WicTep, a kind of switcher, which is a switch that has to be configured on it, and it can send the Wix LAN to the network. So this is the Wix LAN. So this is the Wix LAN. So this is the Wix LAN. So this will create a meaning in space and plug it to the network. So... So in DNS, we can create a network of these spaces. So you can create namespaces and plug together as an network, and you decide that a number of tools, as per the wrong address, and they are working on the same network. So in the next two tools are working on landing on different hosts. Let me recall that if now you want to migrate the left-right machine to another host, you don't need any of the configuration right on the host now on the switches. And it is as fast as the Wix LAN. So you can have some other things, but the traffic is just a unique host, just with 50 bytes per packet of the developer. It's the same of the Wix LAN. So it works on any network. It puts a network, supports a jumbo packet, or big giants, so more than 1500 bytes per packet if you are able to reach 22,000 bytes per packet. But one more. So the next one is a two-pan model, that can give users their own networking environment, or even no environment. So I have a user in my laptop named Renzononetta. The name says all. So if I SSH Renzononetta at localhost, I try to write the right password. There is no way to link a presentation. Now, I have one network at all, so you can create a dial-in only account. But the thing is, it will be not very useful. Maybe you can give somebody exhausted, but it will be very powerful. Host is out of the ability to create further connections. But it's like these people, to have the ability to create their own localizer cloud, but private localizer cloud. In a way, that the localizer cloud of a user cannot interfere, I mean, send by arrow or on purpose, practice to another matter, or even talking to the natural health care somebody else. So we want these users to be able to create their own natural. The idea is being implemented in the tool, which will be expanded, which is a combination of a video cloud, a video cloud tool, and a kernel module. This kernel module provides the user with the ability just to send packets to virtual networks, not to other hosts. And all the packets sent on the network by this link, I can say that they are orthogonal one to the others. So the network of user A, as a specific point in the header, a link, an ID, a virtual network ID, and the kernel module is able to let the user send only packets with that ID. And if by arrow, by on purpose, a packet is received on the wrong ID, it's just discovered. So there is no way for one user to interface with the other. So what's the point? All of that. What's the point? The matter is you have a data center. So you have a set of hosts. You have a set of users that want to do their own job. So, now, if you give your users as a data center owner, if you give your user just a bit to run with the machine, you can force your user to do just the right things by limiting the ability to configure their data machine. What you can do now is to give the ability to use it to have full shell access, and at the same time, they are limited to do just their own local area and working. Local area, cloud networking, nothing more. So, as standard users, there is no way to limit the access to the internet. As standard users, there is no way to limit the access to the local area. So, that's it. And you can open a socket, open a socket, buy a socket to load host address, and so on. And you can use the same thing that you can do that. Instead, the X-ray and X-cannon models provide a different address family, which is not an internet, which is another family, in which the only operation permitted is to create the local area network of the user, which is the point. Security is always a relative matter. So, my laptop is safe. It depends. If somebody is able to top the system bus of my laptop, it is possible to link passwords to enter the memory and whatever. What's interesting is the level of security in a data center. That model of which we would say that no user must be able to top the real line, and no user, a part of the system administrator, should have a limited chance. If all the users enter the system using PAM nonette, they can add, they can add, links to links, metrics, and can create their own lookalike cloud in a safe way. That was a bad one. Doing this stuff, we believe in the UNIX model 12, similar tools. Each one is doing its job in the best way it can, and then you can combine all these tools to have services, to have more powerful services. One tool we are creating is Cable, Capability Tool. It's like a SUV, but at Capability Layer. It's not that related to networking, but it's a little bit to provide if we want users with just the capability they need. There is a cable that calls for configuration file, and you can say that this user can help you with that capability. Our tool is ZIP. ZIP is a famous piece of software which is managed by machine. It's in the camera, in the KVM, obviously, and on rhythm of Linux and Linux of OX. It creates an emulated IP network that is simple to emulate a router and permit the user of the machine to connect to the internet as it were connected by a masquerade, not a router. To create the new model for the computer, we have to take a code from KMO. We have taken a code from KMO. Exactly as a piece, we have just added three lines to add any code file, so we can follow the evolution of KMO, of KMO-slip implementation. I will create a library, so if you need to select your project, not only is it a library, it just provides you with facilities. So, for example, I can create a... I can create a new beginning space like this. Now, this beginning space is real, but there is a tunnel to Belonga where it runs a very easy approach. So, this new space is in Belonga. I can show it to... I can take... I can configure it at any space, it isn't the ACP. And now, I can run... I suppose... For example... I can... What is my address? Okay. We are in Belonga, Italy, but just this space has been moved in, and I have no access in Belonga. In Belonga, there is just one place that is for more than my epitaphic, as if it were an autotrautor. From the Internet platform, we have open traffic lines generating here. Okay. It seems to be generated by my person, Belonga. Somebody is telling me that the time is over. Unfortunately, I have a bunch of more things to tell you. So, if you have a better part of it, there is a problem with identification. If you have questions, make a question, please. Not questions? I am positive. I don't know if it is positive or negative. It is not neutral. I actually do have a question, which is how far is this from production, already, at the point, because it should have more to use this introduction right now on every high-components network. I think very closely. So, how far is the state of the tools from production, so to use it in a real data center? Is it really near? We are going to, very soon, we are going to create a tax for the distributions and to release to the general public. Other stuff will change the undergoing, like the output, the self-generation of the output, the six addresses by action, so that we can just give a name to each process and the address will be generated in an out-of-much way. And there will be a DAS server able to ask the DNS server to change the address that the host must be able to do both for the world-ever-lose resolution. Okay, thank you very much.
 Okay.  All right.  We're ready to start our next session.  Again, this will be a short 25-minute session.  The next thing about modular VDE plug is Professor Renzo Davali from the University of Bologna.  Okay.  Welcome.  Hi.  Is my working?  I don't think so.  Maybe.  Okay.  Now I think it's great.  I'm presenting this talk trying to get you to update about the new developments of the virtual square tools and concepts, especially in the part regarding the networking.  It will be a common line seminar.  So these slides are VI's slides.  Just...  So, VDE, the name of this development is a tool that is quite used in the world to create the virtual design.  The name says all of it.  There are virtual switches which are processes that works as physical switches so you can plug the virtual machines.  Now we're designing all the tools.  And we'll start with the VDE plug.  The new plug is a tool and a ladder. It's the ladder that many common virtual machines and other tools use to connect with VDE.  And it's a tool to connect several networks.  What we designed this for many point of view. First of all, we have created a new syntax app to name the VDE networks.  It's similar to a URL and you can see which technology you're using and specifications.  And it's playable so you can add your own implementation of the network.  If you want to use a technology, say, full, you just have to create a VDE plug, the underscore full, but I saw a short ladder.  And you have to plug the VDE to use that kind of implementation.  We have implemented the connection with the latest VDE switches.  But this is not interesting. We're going to pass to.  We can join top VDE interfaces, VDP, PDP, and so on.  This is just a new point in the dimension of flexibility.  But there is much more.  We're going to come back to this slide.  I'm going to show you this. The XVDE, I live in Tories today, Tories ago here, is called SEM.  It's a way to create a local data cloud.  Instead of connecting a virtual machine to a local switch, you connect a local virtual machine or as you can see in a moment,  your main space to a local cloud.  This local cloud is identified by a multicast IP address.  So you can have so many local cloud relays as many IP multicast addresses you have.  And the usage is like the world.  Because we just put a VDE specification.  That's strange. And we have connected.  I couldn't come here with an entire data center.  But I have a RascalPy on the table and so I have a space that is centered in this by my laptop and the RascalPy.  Which are just on the same run.  There are no processes running.  And I can start the virtual machine on my laptop.  Let's say a KDM.  So X3 disk answers.  Let's talk this.  There is a comma, you can say on the top.  I just have one more specification.  You can say it's a laptop.  But it's really interface is a little bit clear.  Because now my default cloud is on the Wi-Fi.  So I have to say that I have a lot of use with the cloud on the internet there.  I can start this.  And now I can show you another tool.  I can here.  Again.  When you're in a hurry you get your own U2.  That is okay.  I log in to my RascalPy.  Provide a network.  Okay.  Run password.  Okay.  And now I use another tool.  VDNM space, VDNS.  Which creates a username space that is connected to VD.  So VDNM space.  And now I can say mix VDN.  I got a username space.  I just use a null taxes, not capabilities.  And here I can add an address.  Then I do a URL.  It links to the VDNM app.  And now on the VDNM machine which runs on my laptop.  I pay at $10.00.  That was $2.00 for one.  There is an error in configuration.  That was $80.00.  IP address.  Okay.  That is okay.  I've seen a mistake.  There is not the mask.  So I have to delete this and add the mask.  Add the mask slash 24 otherwise it's not working.  10.01.  That's working.  So there it is.  I have to do that way.  There it is.  You can have so many hosts in every little center connected to the local  network.  And then you can start any kind of VN namespace on any host in your local  network and connect it to VDNM.  VDNM creates a VDNM switch on the network.  And I can, I, is it implemented?  The reason that the MIDI plug library which is on H2 is I can  multicast to send all the one packets, broadcast, unknown circuits,  and multicast packets.  So if you're sending an app packet, the app packet is an  embedded in a multicast packet and sent to a multicast address.  So everybody is receiving and that multicast group is receiving the packet.  But in the same time it gets the IP address and port of the sender.  So like a switch, this will be plugged, this will be plugged,  and this will be plugged into the IP address and port of this as the sender of the packet.  So like a normal switch, an IP address and port have the same meaning for this  is you put a switch at the port and a physical switch.  So from now on, if this will be plugged, it can send just the  two packets, the multicast packets back.  It is similar to what happens with the Wix LAN.  But Wix LAN needs what is called a WicTep, a kind of switcher,  which is a switch that has to be configured on it,  and it can send the Wix LAN to the network.  So this is the Wix LAN.  So this is the Wix LAN.  So this is the Wix LAN.  So this will create a meaning in space and plug it to the network.  So...  So in DNS, we can create a network of these spaces.  So you can create namespaces and plug together as an network,  and you decide that a number of tools, as per the wrong address,  and they are working on the same network.  So in the next two tools are working on landing on different hosts.  Let me recall that if now you want to migrate the left-right machine  to another host, you don't need any of the configuration right  on the host now on the switches.  And it is as fast as the Wix LAN.  So you can have some other things,  but the traffic is just a unique host,  just with 50 bytes per packet of the developer.  It's the same of the Wix LAN.  So it works on any network.  It puts a network, supports a jumbo packet,  or big giants, so more than 1500 bytes per packet  if you are able to reach 22,000 bytes per packet.  But one more.  So the next one is a two-pan model,  that can give users their own networking environment,  or even no environment.  So I have a user in my laptop named Renzononetta.  The name says all.  So if I SSH Renzononetta at localhost,  I try to write the right password.  There is no way to link a presentation.  Now, I have one network at all,  so you can create a dial-in only account.  But the thing is, it will be not very useful.  Maybe you can give somebody exhausted,  but it will be very powerful.  Host is out of the ability to create further connections.  But it's like these people,  to have the ability to create their own localizer cloud,  but private localizer cloud.  In a way, that the localizer cloud of a user cannot  interfere, I mean, send by arrow or on purpose,  practice to another matter,  or even talking to the natural health care somebody else.  So we want these users to be able to create their own natural.  The idea is being implemented in the tool,  which will be expanded,  which is a combination of a video cloud,  a video cloud tool, and a kernel module.  This kernel module provides the user with the ability  just to send packets to virtual networks,  not to other hosts.  And all the packets sent on the network by this link,  I can say that they are orthogonal one to the others.  So the network of user A,  as a specific point in the header,  a link, an ID, a virtual network ID,  and the kernel module is able to let the user send  only packets with that ID.  And if by arrow, by on purpose,  a packet is received on the wrong ID,  it's just discovered.  So there is no way for one user to interface with the other.  So what's the point?  All of that. What's the point?  The matter is you have a data center.  So you have a set of hosts.  You have a set of users that want to do their own job.  So, now, if you give your users as a data center owner,  if you give your user just a bit to run with the machine,  you can force your user to do just the right things  by limiting the ability to configure their data machine.  What you can do now is to give the ability to use it  to have full shell access,  and at the same time,  they are limited to do just their own local area and working.  Local area, cloud networking, nothing more.  So, as standard users,  there is no way to limit the access to the internet.  As standard users, there is no way to limit the access to the local area.  So, that's it.  And you can open a socket,  open a socket, buy a socket to load host address, and so on.  And you can use the same thing that you can do that.  Instead, the X-ray and X-cannon models  provide a different address family,  which is not an internet, which is another family,  in which the only operation permitted  is to create the local area network of the user,  which is the point.  Security is always a relative matter.  So, my laptop is safe.  It depends.  If somebody is able to top the system bus of my laptop,  it is possible to link passwords to enter the memory and whatever.  What's interesting is the level of security in a data center.  That model of which we would say that  no user must be able to top the real line,  and no user, a part of the system administrator,  should have a limited chance.  If all the users enter the system using PAM nonette,  they can add, they can add,  links to links, metrics,  and can create their own lookalike cloud in a safe way.  That was a bad one.  Doing this stuff, we believe in the UNIX model 12,  similar tools.  Each one is doing its job in the best way it can,  and then you can combine all these tools to have services,  to have more powerful services.  One tool we are creating is Cable, Capability Tool.  It's like a SUV, but at Capability Layer.  It's not that related to networking,  but it's a little bit to provide if we want users  with just the capability they need.  There is a cable that calls for configuration file,  and you can say that this user can help you  with that capability.  Our tool is ZIP. ZIP is a famous piece of software  which is managed by machine.  It's in the camera, in the KVM, obviously,  and on rhythm of Linux and Linux of OX.  It creates an emulated IP network  that is simple to emulate a router  and permit the user of the machine  to connect to the internet  as it were connected by a masquerade,  not a router.  To create the new model for the computer,  we have to take a code from KMO.  We have taken a code from KMO.  Exactly as a piece, we have just added three lines  to add any code file,  so we can follow the evolution of KMO,  of KMO-slip implementation.  I will create a library,  so if you need to select your project,  not only is it a library,  it just provides you with facilities.  So, for example, I can create a...  I can create a new beginning space  like this.  Now, this beginning space is real,  but there is a tunnel to Belonga  where it runs a very easy approach.  So, this new space is in Belonga.  I can show it to...  I can take...  I can configure it at any space,  it isn't the ACP.  And now, I can run...  I suppose...  For example...  I can...  What is my address?  Okay.  We are in Belonga, Italy,  but just this space has been moved in,  and I have no access in Belonga.  In Belonga, there is just one place  that is for more than my epitaphic,  as if it were an autotrautor.  From the Internet platform,  we have open traffic lines generating here.  Okay. It seems to be generated by my person, Belonga.  Somebody is telling me that the time is over.  Unfortunately, I have a bunch of more things to tell you.  So, if you have a better part of it,  there is a problem with identification.  If you have questions,  make a question, please.  Not questions?  I am positive.  I don't know if it is positive or negative.  It is not neutral.  I actually do have a question,  which is how far is this from production,  already, at the point,  because it should have more to use this introduction right now  on every high-components network.  I think very closely.  So, how far is the state of the tools from production,  so to use it in a real data center?  Is it really near?  We are going to, very soon,  we are going to create a tax for the distributions  and to release to the general public.  Other stuff will change the undergoing,  like the output, the self-generation of the output,  the six addresses by action,  so that we can just give a name to each process  and the address will be generated in an out-of-much way.  And there will be a DAS server able to ask the DNS server  to change the address that the host must be able to do both  for the world-ever-lose resolution.  Okay, thank you very much.
modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_0_47.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_48_107.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_108_515.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_516_839.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_840_5519.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_5520_8243.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_8244_8315.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_8316_8387.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_8388_8483.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_8484_9659.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_9660_9719.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_9720_9839.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_9840_10043.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_10044_10127.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_10128_10379.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_10380_12299.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_12300_12527.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_12528_12587.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_12588_12995.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_12996_18935.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_18936_19187.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_19188_22499.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_22500_22547.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_22548_36839.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_36840_36899.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_36900_37007.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_37008_37187.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_37188_38471.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_38472_38543.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_38544_42719.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_42720_42767.png modular_VDEplug_switchless_switching_networks_and_libslirp_VDEplug_now_supports_plugins_incl_42768_42838.png
Okay. All right. We're ready to start our next session. Again, this will be a short 25-minute session. The next thing about modular VDE plug is Professor Renzo Davali from the University of Bologna. Okay. Welcome. Hi. Is my working? I don't think so. Maybe. Okay. Now I think it's great. I'm presenting this talk trying to get you to update about the new developments of the virtual square tools and concepts, especially in the part regarding the networking. It will be a common line seminar. So these slides are VI's slides. Just... So, VDE, the name of this development is a tool that is quite used in the world to create the virtual design. The name says all of it. There are virtual switches which are processes that works as physical switches so you can plug the virtual machines. Now we're designing all the tools. And we'll start with the VDE plug. The new plug is a tool and a ladder. It's the ladder that many common virtual machines and other tools use to connect with VDE. And it's a tool to connect several networks. What we designed this for many point of view. First of all, we have created a new syntax app to name the VDE networks. It's similar to a URL and you can see which technology you're using and specifications. And it's playable so you can add your own implementation of the network. If you want to use a technology, say, full, you just have to create a VDE plug, the underscore full, but I saw a short ladder. And you have to plug the VDE to use that kind of implementation. We have implemented the connection with the latest VDE switches. But this is not interesting. We're going to pass to. We can join top VDE interfaces, VDP, PDP, and so on. This is just a new point in the dimension of flexibility. But there is much more. We're going to come back to this slide. I'm going to show you this. The XVDE, I live in Tories today, Tories ago here, is called SEM. It's a way to create a local data cloud. Instead of connecting a virtual machine to a local switch, you connect a local virtual machine or as you can see in a moment, your main space to a local cloud. This local cloud is identified by a multicast IP address. So you can have so many local cloud relays as many IP multicast addresses you have. And the usage is like the world. Because we just put a VDE specification. That's strange. And we have connected. I couldn't come here with an entire data center. But I have a RascalPy on the table and so I have a space that is centered in this by my laptop and the RascalPy. Which are just on the same run. There are no processes running. And I can start the virtual machine on my laptop. Let's say a KDM. So X3 disk answers. Let's talk this. There is a comma, you can say on the top. I just have one more specification. You can say it's a laptop. But it's really interface is a little bit clear. Because now my default cloud is on the Wi-Fi. So I have to say that I have a lot of use with the cloud on the internet there. I can start this. And now I can show you another tool. I can here. Again. When you're in a hurry you get your own U2. That is okay. I log in to my RascalPy. Provide a network. Okay. Run password. Okay. And now I use another tool. VDNM space, VDNS. Which creates a username space that is connected to VD. So VDNM space. And now I can say mix VDN. I got a username space. I just use a null taxes, not capabilities. And here I can add an address. Then I do a URL. It links to the VDNM app. And now on the VDNM machine which runs on my laptop. I pay at $10.00. That was $2.00 for one. There is an error in configuration. That was $80.00. IP address. Okay. That is okay. I've seen a mistake. There is not the mask. So I have to delete this and add the mask. Add the mask slash 24 otherwise it's not working. 10.01. That's working. So there it is. I have to do that way. There it is. You can have so many hosts in every little center connected to the local network. And then you can start any kind of VN namespace on any host in your local network and connect it to VDNM. VDNM creates a VDNM switch on the network. And I can, I, is it implemented? The reason that the MIDI plug library which is on H2 is I can multicast to send all the one packets, broadcast, unknown circuits, and multicast packets. So if you're sending an app packet, the app packet is an embedded in a multicast packet and sent to a multicast address. So everybody is receiving and that multicast group is receiving the packet. But in the same time it gets the IP address and port of the sender. So like a switch, this will be plugged, this will be plugged, and this will be plugged into the IP address and port of this as the sender of the packet. So like a normal switch, an IP address and port have the same meaning for this is you put a switch at the port and a physical switch. So from now on, if this will be plugged, it can send just the two packets, the multicast packets back. It is similar to what happens with the Wix LAN. But Wix LAN needs what is called a WicTep, a kind of switcher, which is a switch that has to be configured on it, and it can send the Wix LAN to the network. So this is the Wix LAN. So this is the Wix LAN. So this is the Wix LAN. So this will create a meaning in space and plug it to the network. So... So in DNS, we can create a network of these spaces. So you can create namespaces and plug together as an network, and you decide that a number of tools, as per the wrong address, and they are working on the same network. So in the next two tools are working on landing on different hosts. Let me recall that if now you want to migrate the left-right machine to another host, you don't need any of the configuration right on the host now on the switches. And it is as fast as the Wix LAN. So you can have some other things, but the traffic is just a unique host, just with 50 bytes per packet of the developer. It's the same of the Wix LAN. So it works on any network. It puts a network, supports a jumbo packet, or big giants, so more than 1500 bytes per packet if you are able to reach 22,000 bytes per packet. But one more. So the next one is a two-pan model, that can give users their own networking environment, or even no environment. So I have a user in my laptop named Renzononetta. The name says all. So if I SSH Renzononetta at localhost, I try to write the right password. There is no way to link a presentation. Now, I have one network at all, so you can create a dial-in only account. But the thing is, it will be not very useful. Maybe you can give somebody exhausted, but it will be very powerful. Host is out of the ability to create further connections. But it's like these people, to have the ability to create their own localizer cloud, but private localizer cloud. In a way, that the localizer cloud of a user cannot interfere, I mean, send by arrow or on purpose, practice to another matter, or even talking to the natural health care somebody else. So we want these users to be able to create their own natural. The idea is being implemented in the tool, which will be expanded, which is a combination of a video cloud, a video cloud tool, and a kernel module. This kernel module provides the user with the ability just to send packets to virtual networks, not to other hosts. And all the packets sent on the network by this link, I can say that they are orthogonal one to the others. So the network of user A, as a specific point in the header, a link, an ID, a virtual network ID, and the kernel module is able to let the user send only packets with that ID. And if by arrow, by on purpose, a packet is received on the wrong ID, it's just discovered. So there is no way for one user to interface with the other. So what's the point? All of that. What's the point? The matter is you have a data center. So you have a set of hosts. You have a set of users that want to do their own job. So, now, if you give your users as a data center owner, if you give your user just a bit to run with the machine, you can force your user to do just the right things by limiting the ability to configure their data machine. What you can do now is to give the ability to use it to have full shell access, and at the same time, they are limited to do just their own local area and working. Local area, cloud networking, nothing more. So, as standard users, there is no way to limit the access to the internet. As standard users, there is no way to limit the access to the local area. So, that's it. And you can open a socket, open a socket, buy a socket to load host address, and so on. And you can use the same thing that you can do that. Instead, the X-ray and X-cannon models provide a different address family, which is not an internet, which is another family, in which the only operation permitted is to create the local area network of the user, which is the point. Security is always a relative matter. So, my laptop is safe. It depends. If somebody is able to top the system bus of my laptop, it is possible to link passwords to enter the memory and whatever. What's interesting is the level of security in a data center. That model of which we would say that no user must be able to top the real line, and no user, a part of the system administrator, should have a limited chance. If all the users enter the system using PAM nonette, they can add, they can add, links to links, metrics, and can create their own lookalike cloud in a safe way. That was a bad one. Doing this stuff, we believe in the UNIX model 12, similar tools. Each one is doing its job in the best way it can, and then you can combine all these tools to have services, to have more powerful services. One tool we are creating is Cable, Capability Tool. It's like a SUV, but at Capability Layer. It's not that related to networking, but it's a little bit to provide if we want users with just the capability they need. There is a cable that calls for configuration file, and you can say that this user can help you with that capability. Our tool is ZIP. ZIP is a famous piece of software which is managed by machine. It's in the camera, in the KVM, obviously, and on rhythm of Linux and Linux of OX. It creates an emulated IP network that is simple to emulate a router and permit the user of the machine to connect to the internet as it were connected by a masquerade, not a router. To create the new model for the computer, we have to take a code from KMO. We have taken a code from KMO. Exactly as a piece, we have just added three lines to add any code file, so we can follow the evolution of KMO, of KMO-slip implementation. I will create a library, so if you need to select your project, not only is it a library, it just provides you with facilities. So, for example, I can create a... I can create a new beginning space like this. Now, this beginning space is real, but there is a tunnel to Belonga where it runs a very easy approach. So, this new space is in Belonga. I can show it to... I can take... I can configure it at any space, it isn't the ACP. And now, I can run... I suppose... For example... I can... What is my address? Okay. We are in Belonga, Italy, but just this space has been moved in, and I have no access in Belonga. In Belonga, there is just one place that is for more than my epitaphic, as if it were an autotrautor. From the Internet platform, we have open traffic lines generating here. Okay. It seems to be generated by my person, Belonga. Somebody is telling me that the time is over. Unfortunately, I have a bunch of more things to tell you. So, if you have a better part of it, there is a problem with identification. If you have questions, make a question, please. Not questions? I am positive. I don't know if it is positive or negative. It is not neutral. I actually do have a question, which is how far is this from production, already, at the point, because it should have more to use this introduction right now on every high-components network. I think very closely. So, how far is the state of the tools from production, so to use it in a real data center? Is it really near? We are going to, very soon, we are going to create a tax for the distributions and to release to the general public. Other stuff will change the undergoing, like the output, the self-generation of the output, the six addresses by action, so that we can just give a name to each process and the address will be generated in an out-of-much way. And there will be a DAS server able to ask the DNS server to change the address that the host must be able to do both for the world-ever-lose resolution. Okay, thank you very much.
VDE plug. The new plug is a tool and a ladder. It's the ladder that many common virtual machines the VDE to use that kind of implementation. We have implemented the connection with the latest and add the mask. Add the mask slash 24 otherwise right on the host now on the switches. And it is networking environment, or even no environment. and no user, a part of the system administrator, create the new model for the computer, we have to take a code from KMO. We have taken a code from can create a... I can create a new beginning