It'd be honored to announce our product OpenVNet, which offers efficient and seamless network virtualization. This is an open source project under LGPL 3.0, hosted on GitHub (https://github.com/axsh/openvnet)
This document discusses secure LXC networking using various methods like MACVLAN, VETH, VLAN, and OpenVSwitch. It provides code samples for generating MAC addresses in Bash, PLPGSQL, and Python. Bridging with Linux bridge and OpenVSwitch is also covered. The document emphasizes securing network traffic within and between containers by limiting traffic to assigned IP/MAC addresses and enforcing rules with OpenFlow.
Mininet is a network emulator that creates virtual networks using software switches and hosts. It allows testing and experimenting with Software Defined Networking (SDN) and OpenFlow. The document discusses downloading and setting up a Mininet virtual machine, creating simple network topologies within Mininet using commands, and adding basic flow rules to allow connectivity between hosts. It also covers starting Wireshark to observe OpenFlow traffic and loading the POX SDN controller.
This document provides an agenda for a presentation on vNetworks. It will introduce standard and distributed vSwitches, key vNetwork terms, and review a common single NIC configuration scenario. The lab portion will provide hands-on experience with vNetwork configuration and management.
The document discusses MidoNet, a network virtualization platform that provides a boost to OpenStack Neutron. MidoNet uses a distributed model to avoid single points of failure and bottlenecks seen in the OpenStack OVS plugin. It implements logical L2 and L3 switching, interconnectivity with physical networks, distributed firewalling, load balancing and tunneling using technologies like VxLAN and GRE. MidoNet aligns with Neutron APIs for integration into cloud management software.
This document discusses secure LXC networking using various methods like MACVLAN, VETH, VLAN, and OpenVSwitch. It provides code samples for generating MAC addresses in Bash, PLPGSQL, and Python. Bridging with Linux bridge and OpenVSwitch is also covered. The document emphasizes securing network traffic within and between containers by limiting traffic to assigned IP/MAC addresses and enforcing rules with OpenFlow.
Mininet is a network emulator that creates virtual networks using software switches and hosts. It allows testing and experimenting with Software Defined Networking (SDN) and OpenFlow. The document discusses downloading and setting up a Mininet virtual machine, creating simple network topologies within Mininet using commands, and adding basic flow rules to allow connectivity between hosts. It also covers starting Wireshark to observe OpenFlow traffic and loading the POX SDN controller.
This document provides an agenda for a presentation on vNetworks. It will introduce standard and distributed vSwitches, key vNetwork terms, and review a common single NIC configuration scenario. The lab portion will provide hands-on experience with vNetwork configuration and management.
The document discusses MidoNet, a network virtualization platform that provides a boost to OpenStack Neutron. MidoNet uses a distributed model to avoid single points of failure and bottlenecks seen in the OpenStack OVS plugin. It implements logical L2 and L3 switching, interconnectivity with physical networks, distributed firewalling, load balancing and tunneling using technologies like VxLAN and GRE. MidoNet aligns with Neutron APIs for integration into cloud management software.
VXLAN Integration with CloudStack was presented at the Advanced Zone CCCEU13 conference in Amsterdam on November 21, 2013. The presentation discussed integrating VXLAN to overcome the VLAN ID limitation in CloudStack and allow for more scalable network isolation. VXLAN was demonstrated working with CloudStack to provide isolated networks and inter-tier connectivity within VPCs while maintaining network isolation. Basic functions like VM connectivity, migration, and network availability were tested under VXLAN and found to work as expected. Feedback was welcomed on the VXLAN integration in CloudStack.
This document discusses upgrading an Openstack network to SDN with Tungsten Fabric. It evaluates three solutions: 1) using the same database across regions, 2) hot-swapping Open vSwitch and virtual routers, and 3) using an ML2 plugin. The recommended solution is #3 as it provides minimum downtime. Key steps include installing the OpenContrail driver, synchronizing network resources between Openstack and Tungsten, and live migrating VMs. Topology 2 is also recommended as it requires minimum changes. The upgrade migrated 80 VMs and 16 compute nodes to the SDN network without downtime. Issues discussed include synchronizing resources and migrating VMs between Open vSwitch and virtual routers.
Docker networking basics & coupling with Software Defined NetworksAdrien Blind
This presentation reminds Docker networking, exposes Software Defined Network basic paradigms, and then proposes a mixed-up implementation taking benefits of a coupled use of these two technologies. Implementation model proposed could be a good starting point to create multi-tenant PaaS platforms.
As a bonus, OpenStack Neutron internal design is presented.
You can also have a look on our previous presentation related to enterprise patterns for Docker:
http://fr.slideshare.net/ArnaudMAZIN/docker-meetup-paris-enterprise-docker
1) The document provides an agenda and instructions for a hands-on tutorial on OVS/NFV basics using Open vSwitch, Linux containers, Docker, and virtual private networks.
2) It describes how to access two provided virtual machines and configure port mirroring with Open vSwitch to monitor network traffic between VMs.
3) Instructions are given for installing Linux containers on the VMs, configuring network interfaces and scripts, and testing connectivity between containers using GRE tunnels.
4) The tutorial also covers installing and configuring Docker containers on the VMs, creating virtual networks between them using GRE tunnels, and deploying example containers from Docker Hub.
This document discusses network virtualization and its history. It provides the following key points:
1) Network virtualization aims to decouple virtual networks from physical infrastructure through techniques like tunneling and encapsulation, allowing independent address spaces and topologies.
2) Early work included overlay networks for deployment and experimentation. Virtualization is now used in data centers to isolate tenant traffic and connect virtual machines across sites.
3) The OpenVirteX project aims to advance network virtualization by exposing the entire physical topology to virtual network controllers and allowing independent address spaces and topologies through header rewriting. This would provide more flexibility than existing solutions.
PLNOG 13: Alexis Dacquay: Architectures for Universal Data Centre Networks, t...PROIDEA
Alexis Dacquay – is CCIE with over 10 years experience in the networking industry. He has in the past been designing, deploying, and supporting some large corporate LAN/WAN networks. He has in the last 4 years specialised in high performance datacenter networking to satisfy the needs of cloud providers, web2.0, big data, HPC, HFT, and any other enterprise for which high performing network is critical to their business. Originally from Bretagne, privately a huge fan of polish cuisine.
Topic of Presentation: Architectures for Universal Data Centre Networks, topologies and overlays
Language: English
Abstract: Network integration with single- and multi-hypervisor virtualization environments.
Meetup docker using software defined networksOCTO Technology
Docker networking by default isolates containers but allows communication through exposed ports or linking. Software defined networking (SDN) provides alternatives to group related containers across multiple hosts. SDNs use tunnels between hosts and bridges within each host to isolate tenant networks without VLAN limits. Containers connect to bridges using pipework while avoiding Docker's default bridge isolation. This allows resilient, multi-tenant container networks spanning multiple hosts.
This document discusses OpenStack SDN using Neutron and GRE tunneling. It explains that Neutron provides networking as a service and uses plugins like ml2 with Open vSwitch for SDN. GRE tunneling is used to encapsulate VM traffic between compute and network nodes. Network namespaces are used to create isolated virtual routers and DHCP servers without collisions on each node. The packet flow between an external network, routers, bridges and a VM is outlined.
The document discusses applying OpenStack at iNET, an IT company in Vietnam. It introduces the author who is leading OpenStack deployment and operations. It then outlines iNET's architecture which uses Mitaka OpenStack with bonded network and Ceph storage. Their plans are to migrate more servers and all customer VPS to OpenStack. Key challenges discussed are selecting an OpenStack version, covering all components, and testing performance with limited lab devices.
This document provides an overview of Open vSwitch, including what it is, its main components, features, and how it can be used to build virtual network topologies. Open vSwitch is a software-defined networking switch that can be used to create virtual networks and handle network traffic between virtual machines and tunnels. It uses a distributed database, ovsdb-server, and a userspace daemon, ovs-vswitchd, to implement features like virtual switching, tunneling protocols, and OpenFlow support. Examples are provided for using Open vSwitch with KVM virtual machines and GRE tunnels to create virtual network topologies.
Securing & Enforcing Network Policy and Encryption with Weave NetLuke Marsden
This talk starts with a primer on container networking, then goes on to cover two distinct areas of container network security: encryption, enabled by IPsec in Weave Net and container firewalls, enabled by Kubernetes Network Policy and enforced by the Weave Net Network Policy Controller. A discussion of thread models is included.
This document provides an overview of Open vSwitch, a software-based virtual switch. It discusses what a virtual switch is, how Open vSwitch uses a userspace controller and kernel datapath to provide network abstractions. The document outlines Open vSwitch components like ovsdb-server and ovs-vswitchd, and demonstrates how to use Open vSwitch to build virtual network topologies with VMs, tunnels, and bridges. Examples of QoS configuration and a GRE tunnel demo are also presented.
DCCN 2016 - Tutorial 1 - Communication with LAN/WLANrudndccn
The document introduces a tutorial on simulating communication between devices within LAN and WLAN networks using the Network Simulator 3 (NS-3). It describes creating a virtual machine with NS-3 and Eclipse for developing network simulations and demonstrates simulating a simple network topology with point-to-point, CSMA/CD Ethernet, and CSMA/CA WiFi links between nodes, including capturing traffic between an echo client and server using pcap tracing.
Deep Dive in Docker Overlay Networks - Laurent Bernaille - Architect, D2SIDocker, Inc.
Docker overlay networks allow containers on different hosts to communicate by encapsulating traffic in VXLAN tunnels. The overlay network uses Consul for service discovery and stores network state like MAC address tables. Containers connect to the overlay network via veth interfaces attached to a bridge in the overlay namespace. When a container sends traffic to an unknown destination, the bridge floods it over VXLAN tunnels to other nodes to discover the destination's location.
OpenNebulaConf2015 2.05 OpenNebula at the Leibniz Supercomputing Centre - Mat...OpenNebula Project
The Leibniz Supercomputing Centre (shortly LRZ) is the IT service provider of the Bavarian Academy of Science and Humanities. LRZ decided to set up a cloud computing service for its institutional customers, such as the students and the researchers of the Munich universities, to meet their peek demands and to provide a very flexible compute service to them. This talk will describe the reasons and the benefits behind the choice of OpenNebula for this task, with a particular focus on the customisations that were required, such as:
– network isolation among different groups of users, similarly to a private VLAN;
– management of network security through four different security zones and OpenVswitch
– the introduction of a mechanism to limit the usage of shared resources over time rather than just partitioning the cluster
Author Biography
Matteo Lanati received a MS in Electronic Engineering from the University of Pavia (Italy) in 2004. In 2007 he completed his Ph.D. program at the same University, starting a post-doc cooperation with EUCENTRE (European Centre for Training and Research in Earthquake Engineering) to work on two European projects involving grid computing and body area networks. In 2011 he joined LRZ where he built on his distributed computing skills. He is currently part of the team that takes care of the institution’s compute cloud platform.
The document provides an overview of software-defined networking (SDN) concepts and introduces Open vSwitch (OVS). It discusses:
- The objectives of explaining SDN concepts, introducing OVS, and demonstrating its features through KVM virtualization and the Opendaylight controller.
- Key takeaways around getting familiar with OVS CLI utilities, when to use different features, and creating VLANs for testbeds using KVM.
- How SDN separates the control plane that makes forwarding decisions from the data plane that performs forwarding, allowing centralized network control.
- An overview of OVS architecture with userspace control tools communicating with kernel-level datapath through a database, and support for
Sensor networks are a fundamental building block of Internet of Things (IoT) applications, as they provide the interface to the physical world. In fact, many techniques used for resource-constrained IoT devices originated in the research area of Wireless Sensor Networks (WSNs). This talk will present the transition from research prototypes to standardized Internet protocols, give an overview how sensor networks are connected today (with a practical hands-on), and discuss a few challenges that need to be addressed in the future.
This document provides an introduction to Open vSwitch (OVS), including what a virtual switch is, examples of virtual network topologies using OVS, the main components of OVS, and how to use OVS to build network topologies. It discusses features of OVS like visibility into inter-VM communication and support for tunnels. It also demonstrates OVS configurations for virtual machine to virtual machine communication using GRE tunnels and a demo topology with OVS bridges communicating over a GRE tunnel.
VMworld 2013: Troubleshooting VXLAN and Network Services in a Virtualized Env...VMworld
This document discusses troubleshooting VXLAN and network services in a virtualized environment using VMware NSX. It covers VXLAN packet flow, NSX enhancements to the data and control planes, configuration and consumption demos, packet walks in unicast mode, troubleshooting demos using NSX Manager tools, dynamic routing details and demos, and network virtualization operations. The key takeaways are that multicast is not required in the physical network for VXLAN, NSX provides tools to troubleshoot networks and services, and NSX integrates with operations tools for analysis and alerting.
The document provides an overview of networking in OpenStack with Neutron. It discusses:
- The history of cloud computing and OpenStack.
- An introduction to OpenStack and its core services.
- Neutron architecture and plugins that allow integration with different networking technologies.
- The process of instance creation and how Neutron components work together.
- Tips for troubleshooting common network issues like DHCP failures and connectivity problems.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
VXLAN Integration with CloudStack was presented at the Advanced Zone CCCEU13 conference in Amsterdam on November 21, 2013. The presentation discussed integrating VXLAN to overcome the VLAN ID limitation in CloudStack and allow for more scalable network isolation. VXLAN was demonstrated working with CloudStack to provide isolated networks and inter-tier connectivity within VPCs while maintaining network isolation. Basic functions like VM connectivity, migration, and network availability were tested under VXLAN and found to work as expected. Feedback was welcomed on the VXLAN integration in CloudStack.
This document discusses upgrading an Openstack network to SDN with Tungsten Fabric. It evaluates three solutions: 1) using the same database across regions, 2) hot-swapping Open vSwitch and virtual routers, and 3) using an ML2 plugin. The recommended solution is #3 as it provides minimum downtime. Key steps include installing the OpenContrail driver, synchronizing network resources between Openstack and Tungsten, and live migrating VMs. Topology 2 is also recommended as it requires minimum changes. The upgrade migrated 80 VMs and 16 compute nodes to the SDN network without downtime. Issues discussed include synchronizing resources and migrating VMs between Open vSwitch and virtual routers.
Docker networking basics & coupling with Software Defined NetworksAdrien Blind
This presentation reminds Docker networking, exposes Software Defined Network basic paradigms, and then proposes a mixed-up implementation taking benefits of a coupled use of these two technologies. Implementation model proposed could be a good starting point to create multi-tenant PaaS platforms.
As a bonus, OpenStack Neutron internal design is presented.
You can also have a look on our previous presentation related to enterprise patterns for Docker:
http://fr.slideshare.net/ArnaudMAZIN/docker-meetup-paris-enterprise-docker
1) The document provides an agenda and instructions for a hands-on tutorial on OVS/NFV basics using Open vSwitch, Linux containers, Docker, and virtual private networks.
2) It describes how to access two provided virtual machines and configure port mirroring with Open vSwitch to monitor network traffic between VMs.
3) Instructions are given for installing Linux containers on the VMs, configuring network interfaces and scripts, and testing connectivity between containers using GRE tunnels.
4) The tutorial also covers installing and configuring Docker containers on the VMs, creating virtual networks between them using GRE tunnels, and deploying example containers from Docker Hub.
This document discusses network virtualization and its history. It provides the following key points:
1) Network virtualization aims to decouple virtual networks from physical infrastructure through techniques like tunneling and encapsulation, allowing independent address spaces and topologies.
2) Early work included overlay networks for deployment and experimentation. Virtualization is now used in data centers to isolate tenant traffic and connect virtual machines across sites.
3) The OpenVirteX project aims to advance network virtualization by exposing the entire physical topology to virtual network controllers and allowing independent address spaces and topologies through header rewriting. This would provide more flexibility than existing solutions.
PLNOG 13: Alexis Dacquay: Architectures for Universal Data Centre Networks, t...PROIDEA
Alexis Dacquay – is CCIE with over 10 years experience in the networking industry. He has in the past been designing, deploying, and supporting some large corporate LAN/WAN networks. He has in the last 4 years specialised in high performance datacenter networking to satisfy the needs of cloud providers, web2.0, big data, HPC, HFT, and any other enterprise for which high performing network is critical to their business. Originally from Bretagne, privately a huge fan of polish cuisine.
Topic of Presentation: Architectures for Universal Data Centre Networks, topologies and overlays
Language: English
Abstract: Network integration with single- and multi-hypervisor virtualization environments.
Meetup docker using software defined networksOCTO Technology
Docker networking by default isolates containers but allows communication through exposed ports or linking. Software defined networking (SDN) provides alternatives to group related containers across multiple hosts. SDNs use tunnels between hosts and bridges within each host to isolate tenant networks without VLAN limits. Containers connect to bridges using pipework while avoiding Docker's default bridge isolation. This allows resilient, multi-tenant container networks spanning multiple hosts.
This document discusses OpenStack SDN using Neutron and GRE tunneling. It explains that Neutron provides networking as a service and uses plugins like ml2 with Open vSwitch for SDN. GRE tunneling is used to encapsulate VM traffic between compute and network nodes. Network namespaces are used to create isolated virtual routers and DHCP servers without collisions on each node. The packet flow between an external network, routers, bridges and a VM is outlined.
The document discusses applying OpenStack at iNET, an IT company in Vietnam. It introduces the author who is leading OpenStack deployment and operations. It then outlines iNET's architecture which uses Mitaka OpenStack with bonded network and Ceph storage. Their plans are to migrate more servers and all customer VPS to OpenStack. Key challenges discussed are selecting an OpenStack version, covering all components, and testing performance with limited lab devices.
This document provides an overview of Open vSwitch, including what it is, its main components, features, and how it can be used to build virtual network topologies. Open vSwitch is a software-defined networking switch that can be used to create virtual networks and handle network traffic between virtual machines and tunnels. It uses a distributed database, ovsdb-server, and a userspace daemon, ovs-vswitchd, to implement features like virtual switching, tunneling protocols, and OpenFlow support. Examples are provided for using Open vSwitch with KVM virtual machines and GRE tunnels to create virtual network topologies.
Securing & Enforcing Network Policy and Encryption with Weave NetLuke Marsden
This talk starts with a primer on container networking, then goes on to cover two distinct areas of container network security: encryption, enabled by IPsec in Weave Net and container firewalls, enabled by Kubernetes Network Policy and enforced by the Weave Net Network Policy Controller. A discussion of thread models is included.
This document provides an overview of Open vSwitch, a software-based virtual switch. It discusses what a virtual switch is, how Open vSwitch uses a userspace controller and kernel datapath to provide network abstractions. The document outlines Open vSwitch components like ovsdb-server and ovs-vswitchd, and demonstrates how to use Open vSwitch to build virtual network topologies with VMs, tunnels, and bridges. Examples of QoS configuration and a GRE tunnel demo are also presented.
DCCN 2016 - Tutorial 1 - Communication with LAN/WLANrudndccn
The document introduces a tutorial on simulating communication between devices within LAN and WLAN networks using the Network Simulator 3 (NS-3). It describes creating a virtual machine with NS-3 and Eclipse for developing network simulations and demonstrates simulating a simple network topology with point-to-point, CSMA/CD Ethernet, and CSMA/CA WiFi links between nodes, including capturing traffic between an echo client and server using pcap tracing.
Deep Dive in Docker Overlay Networks - Laurent Bernaille - Architect, D2SIDocker, Inc.
Docker overlay networks allow containers on different hosts to communicate by encapsulating traffic in VXLAN tunnels. The overlay network uses Consul for service discovery and stores network state like MAC address tables. Containers connect to the overlay network via veth interfaces attached to a bridge in the overlay namespace. When a container sends traffic to an unknown destination, the bridge floods it over VXLAN tunnels to other nodes to discover the destination's location.
OpenNebulaConf2015 2.05 OpenNebula at the Leibniz Supercomputing Centre - Mat...OpenNebula Project
The Leibniz Supercomputing Centre (shortly LRZ) is the IT service provider of the Bavarian Academy of Science and Humanities. LRZ decided to set up a cloud computing service for its institutional customers, such as the students and the researchers of the Munich universities, to meet their peek demands and to provide a very flexible compute service to them. This talk will describe the reasons and the benefits behind the choice of OpenNebula for this task, with a particular focus on the customisations that were required, such as:
– network isolation among different groups of users, similarly to a private VLAN;
– management of network security through four different security zones and OpenVswitch
– the introduction of a mechanism to limit the usage of shared resources over time rather than just partitioning the cluster
Author Biography
Matteo Lanati received a MS in Electronic Engineering from the University of Pavia (Italy) in 2004. In 2007 he completed his Ph.D. program at the same University, starting a post-doc cooperation with EUCENTRE (European Centre for Training and Research in Earthquake Engineering) to work on two European projects involving grid computing and body area networks. In 2011 he joined LRZ where he built on his distributed computing skills. He is currently part of the team that takes care of the institution’s compute cloud platform.
The document provides an overview of software-defined networking (SDN) concepts and introduces Open vSwitch (OVS). It discusses:
- The objectives of explaining SDN concepts, introducing OVS, and demonstrating its features through KVM virtualization and the Opendaylight controller.
- Key takeaways around getting familiar with OVS CLI utilities, when to use different features, and creating VLANs for testbeds using KVM.
- How SDN separates the control plane that makes forwarding decisions from the data plane that performs forwarding, allowing centralized network control.
- An overview of OVS architecture with userspace control tools communicating with kernel-level datapath through a database, and support for
Sensor networks are a fundamental building block of Internet of Things (IoT) applications, as they provide the interface to the physical world. In fact, many techniques used for resource-constrained IoT devices originated in the research area of Wireless Sensor Networks (WSNs). This talk will present the transition from research prototypes to standardized Internet protocols, give an overview how sensor networks are connected today (with a practical hands-on), and discuss a few challenges that need to be addressed in the future.
This document provides an introduction to Open vSwitch (OVS), including what a virtual switch is, examples of virtual network topologies using OVS, the main components of OVS, and how to use OVS to build network topologies. It discusses features of OVS like visibility into inter-VM communication and support for tunnels. It also demonstrates OVS configurations for virtual machine to virtual machine communication using GRE tunnels and a demo topology with OVS bridges communicating over a GRE tunnel.
VMworld 2013: Troubleshooting VXLAN and Network Services in a Virtualized Env...VMworld
This document discusses troubleshooting VXLAN and network services in a virtualized environment using VMware NSX. It covers VXLAN packet flow, NSX enhancements to the data and control planes, configuration and consumption demos, packet walks in unicast mode, troubleshooting demos using NSX Manager tools, dynamic routing details and demos, and network virtualization operations. The key takeaways are that multicast is not required in the physical network for VXLAN, NSX provides tools to troubleshoot networks and services, and NSX integrates with operations tools for analysis and alerting.
The document provides an overview of networking in OpenStack with Neutron. It discusses:
- The history of cloud computing and OpenStack.
- An introduction to OpenStack and its core services.
- Neutron architecture and plugins that allow integration with different networking technologies.
- The process of instance creation and how Neutron components work together.
- Tips for troubleshooting common network issues like DHCP failures and connectivity problems.
Monitoring and Managing Anomaly Detection on OpenShift.pdfTosin Akinosho
Monitoring and Managing Anomaly Detection on OpenShift
Overview
Dive into the world of anomaly detection on edge devices with our comprehensive hands-on tutorial. This SlideShare presentation will guide you through the entire process, from data collection and model training to edge deployment and real-time monitoring. Perfect for those looking to implement robust anomaly detection systems on resource-constrained IoT/edge devices.
Key Topics Covered
1. Introduction to Anomaly Detection
- Understand the fundamentals of anomaly detection and its importance in identifying unusual behavior or failures in systems.
2. Understanding Edge (IoT)
- Learn about edge computing and IoT, and how they enable real-time data processing and decision-making at the source.
3. What is ArgoCD?
- Discover ArgoCD, a declarative, GitOps continuous delivery tool for Kubernetes, and its role in deploying applications on edge devices.
4. Deployment Using ArgoCD for Edge Devices
- Step-by-step guide on deploying anomaly detection models on edge devices using ArgoCD.
5. Introduction to Apache Kafka and S3
- Explore Apache Kafka for real-time data streaming and Amazon S3 for scalable storage solutions.
6. Viewing Kafka Messages in the Data Lake
- Learn how to view and analyze Kafka messages stored in a data lake for better insights.
7. What is Prometheus?
- Get to know Prometheus, an open-source monitoring and alerting toolkit, and its application in monitoring edge devices.
8. Monitoring Application Metrics with Prometheus
- Detailed instructions on setting up Prometheus to monitor the performance and health of your anomaly detection system.
9. What is Camel K?
- Introduction to Camel K, a lightweight integration framework built on Apache Camel, designed for Kubernetes.
10. Configuring Camel K Integrations for Data Pipelines
- Learn how to configure Camel K for seamless data pipeline integrations in your anomaly detection workflow.
11. What is a Jupyter Notebook?
- Overview of Jupyter Notebooks, an open-source web application for creating and sharing documents with live code, equations, visualizations, and narrative text.
12. Jupyter Notebooks with Code Examples
- Hands-on examples and code snippets in Jupyter Notebooks to help you implement and test anomaly detection models.
Essentials of Automations: The Art of Triggers and Actions in FMESafe Software
In this second installment of our Essentials of Automations webinar series, we’ll explore the landscape of triggers and actions, guiding you through the nuances of authoring and adapting workspaces for seamless automations. Gain an understanding of the full spectrum of triggers and actions available in FME, empowering you to enhance your workspaces for efficient automation.
We’ll kick things off by showcasing the most commonly used event-based triggers, introducing you to various automation workflows like manual triggers, schedules, directory watchers, and more. Plus, see how these elements play out in real scenarios.
Whether you’re tweaking your current setup or building from the ground up, this session will arm you with the tools and insights needed to transform your FME usage into a powerhouse of productivity. Join us to discover effective strategies that simplify complex processes, enhancing your productivity and transforming your data management practices with FME. Let’s turn complexity into clarity and make your workspaces work wonders!
Ivanti’s Patch Tuesday breakdown goes beyond patching your applications and brings you the intelligence and guidance needed to prioritize where to focus your attention first. Catch early analysis on our Ivanti blog, then join industry expert Chris Goettl for the Patch Tuesday Webinar Event. There we’ll do a deep dive into each of the bulletins and give guidance on the risks associated with the newly-identified vulnerabilities.
Building Production Ready Search Pipelines with Spark and MilvusZilliz
Spark is the widely used ETL tool for processing, indexing and ingesting data to serving stack for search. Milvus is the production-ready open-source vector database. In this talk we will show how to use Spark to process unstructured data to extract vector representations, and push the vectors to Milvus vector database for search serving.
How to Get CNIC Information System with Paksim Ga.pptxdanishmna97
Pakdata Cf is a groundbreaking system designed to streamline and facilitate access to CNIC information. This innovative platform leverages advanced technology to provide users with efficient and secure access to their CNIC details.
HCL Notes und Domino Lizenzkostenreduzierung in der Welt von DLAUpanagenda
Webinar Recording: https://www.panagenda.com/webinars/hcl-notes-und-domino-lizenzkostenreduzierung-in-der-welt-von-dlau/
DLAU und die Lizenzen nach dem CCB- und CCX-Modell sind für viele in der HCL-Community seit letztem Jahr ein heißes Thema. Als Notes- oder Domino-Kunde haben Sie vielleicht mit unerwartet hohen Benutzerzahlen und Lizenzgebühren zu kämpfen. Sie fragen sich vielleicht, wie diese neue Art der Lizenzierung funktioniert und welchen Nutzen sie Ihnen bringt. Vor allem wollen Sie sicherlich Ihr Budget einhalten und Kosten sparen, wo immer möglich. Das verstehen wir und wir möchten Ihnen dabei helfen!
Wir erklären Ihnen, wie Sie häufige Konfigurationsprobleme lösen können, die dazu führen können, dass mehr Benutzer gezählt werden als nötig, und wie Sie überflüssige oder ungenutzte Konten identifizieren und entfernen können, um Geld zu sparen. Es gibt auch einige Ansätze, die zu unnötigen Ausgaben führen können, z. B. wenn ein Personendokument anstelle eines Mail-Ins für geteilte Mailboxen verwendet wird. Wir zeigen Ihnen solche Fälle und deren Lösungen. Und natürlich erklären wir Ihnen das neue Lizenzmodell.
Nehmen Sie an diesem Webinar teil, bei dem HCL-Ambassador Marc Thomas und Gastredner Franz Walder Ihnen diese neue Welt näherbringen. Es vermittelt Ihnen die Tools und das Know-how, um den Überblick zu bewahren. Sie werden in der Lage sein, Ihre Kosten durch eine optimierte Domino-Konfiguration zu reduzieren und auch in Zukunft gering zu halten.
Diese Themen werden behandelt
- Reduzierung der Lizenzkosten durch Auffinden und Beheben von Fehlkonfigurationen und überflüssigen Konten
- Wie funktionieren CCB- und CCX-Lizenzen wirklich?
- Verstehen des DLAU-Tools und wie man es am besten nutzt
- Tipps für häufige Problembereiche, wie z. B. Team-Postfächer, Funktions-/Testbenutzer usw.
- Praxisbeispiele und Best Practices zum sofortigen Umsetzen
In his public lecture, Christian Timmerer provides insights into the fascinating history of video streaming, starting from its humble beginnings before YouTube to the groundbreaking technologies that now dominate platforms like Netflix and ORF ON. Timmerer also presents provocative contributions of his own that have significantly influenced the industry. He concludes by looking at future challenges and invites the audience to join in a discussion.
Unlocking Productivity: Leveraging the Potential of Copilot in Microsoft 365, a presentation by Christoforos Vlachos, Senior Solutions Manager – Modern Workplace, Uni Systems
Climate Impact of Software Testing at Nordic Testing DaysKari Kakkonen
My slides at Nordic Testing Days 6.6.2024
Climate impact / sustainability of software testing discussed on the talk. ICT and testing must carry their part of global responsibility to help with the climat warming. We can minimize the carbon footprint but we can also have a carbon handprint, a positive impact on the climate. Quality characteristics can be added with sustainability, and then measured continuously. Test environments can be used less, and in smaller scale and on demand. Test techniques can be used in optimizing or minimizing number of tests. Test automation can be used to speed up testing.
OpenID AuthZEN Interop Read Out - AuthorizationDavid Brossard
During Identiverse 2024 and EIC 2024, members of the OpenID AuthZEN WG got together and demoed their authorization endpoints conforming to the AuthZEN API
Let's Integrate MuleSoft RPA, COMPOSER, APM with AWS IDP along with Slackshyamraj55
Discover the seamless integration of RPA (Robotic Process Automation), COMPOSER, and APM with AWS IDP enhanced with Slack notifications. Explore how these technologies converge to streamline workflows, optimize performance, and ensure secure access, all while leveraging the power of AWS IDP and real-time communication via Slack notifications.
AI-Powered Food Delivery Transforming App Development in Saudi Arabia.pdfTechgropse Pvt.Ltd.
In this blog post, we'll delve into the intersection of AI and app development in Saudi Arabia, focusing on the food delivery sector. We'll explore how AI is revolutionizing the way Saudi consumers order food, how restaurants manage their operations, and how delivery partners navigate the bustling streets of cities like Riyadh, Jeddah, and Dammam. Through real-world case studies, we'll showcase how leading Saudi food delivery apps are leveraging AI to redefine convenience, personalization, and efficiency.
Ocean lotus Threat actors project by John Sitima 2024 (1).pptxSitimaJohn
Ocean Lotus cyber threat actors represent a sophisticated, persistent, and politically motivated group that poses a significant risk to organizations and individuals in the Southeast Asian region. Their continuous evolution and adaptability underscore the need for robust cybersecurity measures and international cooperation to identify and mitigate the threats posed by such advanced persistent threat groups.
Have you ever been confused by the myriad of choices offered by AWS for hosting a website or an API?
Lambda, Elastic Beanstalk, Lightsail, Amplify, S3 (and more!) can each host websites + APIs. But which one should we choose?
Which one is cheapest? Which one is fastest? Which one will scale to meet our needs?
Join me in this session as we dive into each AWS hosting service to determine which one is best for your scenario and explain why!
2. What is OpenVNet?
•
•
•
•
•
•
Spin-off project from Wakame-vdc
4 developers
1170 commits
Written in Ruby
9619 LOCs (13033 LOCs with test codes)
Started March 2013, now it is 7 month old
Wednesday, October 30, 13
3. Why OpenVNet?
•
There are many products offering network virtualization
but not free
•
Is there any product to freely try out network
virtualization?
•
•
Wakame-vdc offers network virtualization
Extract virtual network functionality from Wakame-vdc to
make an independent package
Wednesday, October 30, 13
4. Advantages of OpenVNet
Freely and easily create/destroy networks
•
e.g.) quickly preparing an isolated network for experiment
Reduce the maintaining cost of the physical networks
•
•
Users can create complex networks on top of OpenVNet
Keep the physical networks simple
No need expensive network switches
•
Wednesday, October 30, 13
Edge-overlay architecture enables creating complex multi-tenant
networks
5. Advantages of OpenVNet
Seamless network virtualization
•
•
Virtualizing entire network is difficult
•
OpenVNet supports association with legacy network
Why not to start network virtualization from smaller
part?
Wednesday, October 30, 13
7. Network model of datacenter
Internet
DNAT / LB
Datacenter
network
Physical/Virtual server clusters
Wednesday, October 30, 13
SNAT
DHCP
DNS
8. Network model of datacenter
Internet
External network
DNAT / LB
WAN edge network
Datacenter
network
SNAT
DHCP
DNS
Datacenter
physical network
LAN edge network
General
servers
Appliance
servers
Physical/Virtual server clusters
Resources
Wednesday, October 30, 13
Storage
servers
9. Deployment of agent program
Internet
DNAT / LB
agent
agent
agent
Datacenter
network
agent
agent
SNAT
DHCP
DNS
agent
Physical/Virtual server clusters
Wednesday, October 30, 13
Deploy agents for
packet control
10. Message queue
Internet
DNAT / LB
agent
agent
agent
Datacenter
Queue
network
agent
agent
SNAT
DHCP
DNS
agent
Physical/Virtual server clusters
Wednesday, October 30, 13
Agents communicate to
each other through
message queue system
11. Components of OpenVNet
vna (virtual network agent)
•
•
Agent
Configure OpenvSwitch (version 1.10.0)
Include an OpenFlow controller implemented with Trema-edge
vnmgr (virtual network manager)
other
components
•
•
•
Manage the datacenter network
Provide database access back-ended by MySQL
Command vna to do some specific actions e.g.) update flows
vnapi (virtual network API)
•
WebAPI to talk to vnmgr
•
Command line interface to use vnapi
vnctl (virtual network controller)
Wednesday, October 30, 13
13. Deployment
External network
WAN edge network
Datacenter
physical network
A dedicated line for management
Packets for the service go through
the public line
management line
public line
eth0
LAN edge network
General
servers
Appliance
servers
Storage
servers
Resources
Wednesday, October 30, 13
Open
vSwitch
VM
eth1
eth0
eth1
vna
Open
vSwitch
vna
VM
14. Packet forwarding in OpenVNet
• MAC2MAC
• OpenVNet original way of packet forwarding
• Forward packet based on MAC address
• GRE Tunnel
• Over L3 routing
• VNet edge
• Perform VLAN ID translation
• Associate with legacy network
Wednesday, October 30, 13
15. MAC2MAC
Suppose that both VM1 and VM2 exist on the same virtual network
public line
eth0
Open
vSwitch
eth1
eth0
eth1
vna
Open
vSwitch
vna
virtual network1
VM1
MAC = 00:00:00:00:01
IP = 10.102.0.10
Wednesday, October 30, 13
VM2
MAC = 00:00:00:00:02
IP = 10.102.0.11
16. MAC2MAC
both vna know that VM1 and VM2 exist on virtual network1
public line
eth0
Open
vSwitch
VM1
eth1
eth0
eth1
vna
Open
vSwitch
vna
virtual network1
VM2
VM1 = 00:00:00:00:01
VM2 = 00:00:00:00:02
Wednesday, October 30, 13
17. MAC2MAC
VM1 sends ARP request
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
eth0
eth1
vna
Open
vSwitch
vna
src_ip = 10.102.0.10
dst_ip = 10.102.0.11
src_mac = 00:00:00:00:00:01
dst_mac = ff:ff:ff:ff:ff:ff
VM2
18. MAC2MAC
Open vSwitch broadcasts the packet
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
eth0
eth1
src_ip = 10.102.0.10
vna
dst_ip = 10.102.0.11
src_mac = 00:00:00:00:00:01
dst_mac = ff:ff:ff:ff:ff:ff
Open
vSwitch
vna
VM2
19. MAC2MAC
The other hosts receive the packet
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
eth0
eth1
src_ip = 10.102.0.10
vna
dst_ip = 10.102.0.11
src_mac = 00:00:00:00:00:01
dst_mac = ff:ff:ff:ff:ff:ff
Open
vSwitch
vna
VM2
20. MAC2MAC
Open vSwitch checks the src_mac, then it founds
the packet is of virtual network1
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
vna
src_mac = 00:00:00:00:00:01
eth0
eth1
Open
vSwitch
vna
VM2
21. MAC2MAC
Remember src_mac in case of other packets
whose destination is 00:00:00:00:00:01
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
eth0
eth1
vna
Open
vSwitch
vna
dst_mac = 00:00:00:00:00:01
⇛ output:eth0
VM2
22. MAC2MAC
Forward a packet according to the network
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
eth0
eth1
vna
Open
vSwitch
vna
src_ip = 10.102.0.10
dst_ip = 10.102.0.11
src_mac = 00:00:00:00:00:01
dst_mac = ff:ff:ff:ff:ff:ff
VM2
23. MAC2MAC
ARP reply comes in the Open vSwitch
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
eth0
eth1
vna
Open
vSwitch
vna
src_ip = 10.102.0.11
dst_ip = 10.102.0.10
src_mac = 00:00:00:00:00:02
dst_mac = 00:00:00:00:00:01
VM2
24. MAC2MAC
Open vSwitch knows that the packet should be
forwarded to eth0
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
vna
dst_mac = 00:00:00:00:00:01
⇛ output:eth0
src_ip = 10.102.0.11
dst_ip = 10.102.0.10
src_mac = 00:00:00:00:00:02
dst_mac = 00:00:00:00:00:01
eth0
eth1
Open
vSwitch
vna
VM2
25. MAC2MAC
The packet is forwarded from eth0
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
src_ip = 10.102.0.11
dst_ip = 10.102.0.10
vna
src_mac = 00:00:00:00:00:02
dst_mac = 00:00:00:00:00:01
eth0
eth1
Open
vSwitch
vna
VM2
26. MAC2MAC
The another host receives the ARP reply packet
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
src_ip = 10.102.0.11
dst_ip = 10.102.0.10
vna
src_mac = 00:00:00:00:00:02
dst_mac = 00:00:00:00:00:01
eth0
eth1
Open
vSwitch
vna
VM2
27. MAC2MAC
Remember the source mac address
public line
eth0
Open
vSwitch
eth1
eth0
eth1
vna
Open
vSwitch
vna
src_mac = 00:00:00:00:00:02
⇛ output:eth0
VM1
Wednesday, October 30, 13
VM2
28. MAC2MAC
Output the packet to the specific VM
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
eth0
eth1
vna
Open
vSwitch
vna
src_ip = 10.102.0.11
dst_ip = 10.102.0.10
src_mac = 00:00:00:00:00:02
dst_mac = 00:00:00:00:00:01
VM2
29. GRE Tunnel
Prepare GRE tunnels in case of L3 routing required
Use MAC2MAC over GRE tunnels
GRE tunnel
L3 switch
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
eth0
vna
Open
vSwitch
VM2
eth1
eth0
eth1
vna
Open
vSwitch
vna
VM3
30. Overall
Any complex packet forwarding is done by Open vSwitch
Just normal L2 and L3 switch are required
No need to buy expensive network switches!!
L3 switch
public line
eth0
Open
vSwitch
VM1
Wednesday, October 30, 13
eth1
eth0
vna
Open
vSwitch
VM2
eth1
eth0
eth1
vna
Open
vSwitch
vna
VM3
31. Advantages of OpenVNet
Seamless network virtualization
•
•
Virtualizing entire network is difficult
•
OpenVNet supports association with legacy network
Why not to start network virtualization from smaller
part?
Wednesday, October 30, 13
32. VNet edge
Perform VLAN ID translation
•
•
•
legacy line
Associate the legacy machine to the virtual network ID 2
Edge server is responsible for VLAN ID translation
Legacy machine is connected to the edge server over L2 network
Legacy
L2 switch
eth0
Legacy machine
public line
eth2
eth0
Open
vSwitch
eth1
eth0
eth1
vna
Open
vSwitch
vna
VM1
Edge server
Wednesday, October 30, 13
Network ID 2
33. VNet edge
Send a packet from a legacy machine
•
legacy line
Suppose the legacy machine is associated with VLAN ID 100
Legacy
L2 switch
eth0
Legacy machine
public line
eth2
eth0
Open
vSwitch
eth1
eth0
eth1
vna
Open
vSwitch
vna
VM1
Edge server
Wednesday, October 30, 13
34. VNet edge
Open vSwitch forwards the packet to the OF
controller
Translates VLAN ID 100 to network ID 2
legacy line
Legacy
L2 switch
eth0
Legacy machine
public line
eth2
eth0
eth1
VLAN
100
vnet
2
Edge server
Wednesday, October 30, 13
eth1
vna
Open
vSwitch
eth0
Open
vSwitch
vna
VM1
35. VNet edge
After the translation, the packet is forwarded by
MAC2MAC
legacy line
Legacy
L2 switch
eth0
Legacy machine
public line
eth2
eth0
eth1
VLAN
100
vnet
2
Edge server
Wednesday, October 30, 13
eth1
vna
Open
vSwitch
eth0
Open
vSwitch
vna
VM1
36. VNet edge
The legacy machine can participate in the virtual network
legacy line
Legacy
L2 switch
eth0
Legacy machine
public line
eth2
eth0
eth1
VLAN
100
vnet
2
Edge server
Wednesday, October 30, 13
eth1
vna
Open
vSwitch
eth0
Open
vSwitch
vna
VM1
37. Conclusion
•
•
Advantages of OpenVNet
•
•
•
Reduce the cost for maintaining the physical networks
No need to buy expensive network switches
Association with the legacy networks
Github
•
https://github.com/axsh/openvnet
Wednesday, October 30, 13