|
7 | 7 | <title>reveal.js</title>
|
8 | 8 |
|
9 | 9 | <link rel="stylesheet" href="css/reveal.css">
|
10 |
| - <link rel="stylesheet" href="css/theme/black.css"> |
| 10 | + <link rel="stylesheet" href="css/theme/white.css"> |
11 | 11 |
|
12 | 12 | <!-- Theme used for syntax highlighting of code -->
|
13 | 13 | <link rel="stylesheet" href="lib/css/zenburn.css">
|
|
69 | 69 | </tr>
|
70 | 70 | <tr>
|
71 | 71 | <p>
|
72 |
| - <th>40% of all mobile traffic</th> |
| 72 | + <th>40% of all mobile traffic crunching data</th> |
73 | 73 | </p>
|
74 | 74 | </tr>
|
75 | 75 | <aside class="notes">
|
|
88 | 88 | Our customers are typically telecom operators ... well, and a taxi company ... in Dubai ... and Panasonic Avionics for entertainment on board of flights, and many other such examples.
|
89 | 89 | What is NFVi?
|
90 | 90 | For many years at Ericsson, we made SW and HW very dependent on each other. Customers bought whole racks of custom HW and the Ericsson SW applications deployed and running on top of that HW.
|
91 |
| -NFV means, more or less, decoupling the SW from HW. It means you can run the telecom applications(the SW) on any HW (like Dell, HP, Qanta, SuperMicro, Fujitsu servers, whatnot), in VMs or containers. |
| 91 | +NFVi is part of the NFV framework and it means, more or less, decoupling the SW from HW for network nodes using virtualization. It means you can run the telecom applications(the SW) on any HW (like Dell, HP, Qanta, SuperMicro, Fujitsu servers, whatnot), in VMs or containers. |
92 | 92 | Traces of this decoupling of the network functions from proprietary hardware appliances are there for many years now.
|
93 | 93 | Around the year 2003, I worked in an ISP. We used Cisco routers to do BGP with customers and the upstream provider. I was in awe when GNU Zebra came out and I could run BGP in a Linux box. Fast forward to today, part of SDN, we use opendaylight with Quagga soft router for BGP ( Quagga is what followed after zebra, it is actually an extinct sub-specie of the African zebra.)
|
94 | 94 |
|
|
170 | 170 | <!–– Slide10 ––>
|
171 | 171 | <section> Openstack working with SmartNICs
|
172 | 172 | <aside class="notes">
|
| 173 | +Now the question is where are we in Openstack when it comes to integrating the new coming smartNICs? |
| 174 | +Work is done in several Openstack components, like ironic and neutron of course. |
| 175 | +Some smartNIC vendors use native virtio driver while other use proprietary |
| 176 | + |
| 177 | +https://specs.openstack.org/openstack/nova-specs/specs/pike/implemented/netronome-smartnic-enablement.html |
| 178 | + |
173 | 179 | Openstack working with SmartNICs - TO BE ADDED
|
174 | 180 | Openstack support for smartNICs starting with Rocky, Stein - TO BE ADDED
|
175 | 181 | Neutron integration with SmartNICs - TO BE ADDED
|
|
0 commit comments