This document discusses the need for a standardized information model and high-level northbound API for SDN to abstract away the low-level details of existing protocols like OpenFlow. It proposes defining a common data-centric information model using UML that existing SDN protocols and middleware platforms can map to in order to provide interoperability and simplify development. RTI and Cisco believe this model-driven approach will help unify and evolve SDN systems to accommodate multiple protocols and legacy networks.
Software Defined Networking (SDN): A Revolution in Computer NetworkIOSR Journals
Abstract: SDN creates a dynamic and flexible network architecture that can change as the business
requirements change. The growth of the SDN market and cloud computing are very much connected. As the
applications change and the network is abstracted, virtualization become a necessary step and SDN serves as
the fundamental building blocks for the network. Traditional networking devices are composed of an embedded
control plane that manages switching, routing and traffic engineering activities while the data plane forwards
packet/frames based on traffic. In SDN architecture, control plane functions are removed from individual
networking devices and embedded in a centralizedserver. The SDN controller makes all traffic related decisions
in the network without nodes active participation, as opposed to today’s networks.
Keyword-API, cloud computing, IT, middleware, OpenFlow, SDN
Software Defined Networking (SDN): A Revolution in Computer NetworkIOSR Journals
Abstract: SDN creates a dynamic and flexible network architecture that can change as the business
requirements change. The growth of the SDN market and cloud computing are very much connected. As the
applications change and the network is abstracted, virtualization become a necessary step and SDN serves as
the fundamental building blocks for the network. Traditional networking devices are composed of an embedded
control plane that manages switching, routing and traffic engineering activities while the data plane forwards
packet/frames based on traffic. In SDN architecture, control plane functions are removed from individual
networking devices and embedded in a centralizedserver. The SDN controller makes all traffic related decisions
in the network without nodes active participation, as opposed to today’s networks.
Keyword-API, cloud computing, IT, middleware, OpenFlow, SDN
Applications Drive Secure Lightpath Creation Across Heterogeneous DomainsTal Lavian Ph.D.
We realize an open, programmable paradigm for application-driven network control by way of a novel network plane — the “service plane” — layered above legacy networks. The service plane bridges domains, establishes trust, and exposes control to credited users/applications while preventing unauthorized access and resource theft. The Authentication, Authorization, Accounting subsystem and the Dynamic Resource Allocation Controller are the two defining building blocks of our service plane. In concert, they act upon an interconnection request or a restoration request according to application requirements, security credentials, and domain-resident policy. We have experimented with such service
plane in an optical, large-scale testbed featuring two hubs (NetherLight in Amsterdam, StarLight in Chicago) and attached network clouds, each representing an independent domain. The dynamic interconnection of the heterogeneous domains occurred at Layer 1. The interconnections ultimately resulted in an optical end-to-end path (lightpath) for use by the
requesting Grid application.
Air Force Provides Any Service, Anytime, Anywhere, Securely. Royal Saudi Air Force consolidates IT infrastructure with new Cisco network to improve operations, reduce cost, and easily and quickly launch new services.
Architecture evolution for automation and network programmabilityEricsson
http://www.ericsson.com/review
Automation and network programmability are key concepts in the evolution of telecom networks. Architecture designed with high degrees of automation and network programmability can rapidly adapt to emerging requirements, and as such improve operational efficiency and time to market for new services.
Ericsson Review: Software-Defined-NetworkingEricsson
An architecture based on software-defined networking (SDN) techniques gives operators greater freedom to balance operational and business parameters, such as network resilience, service performance and QoE against opex and capex. With its beginnings in data-center technology, software-defined networking (SDN) technology has developed to the point where it can offer significant opportunities to service providers.
The traditional way of describing network architecture and how a network behaves is through the fixed designs and behaviors of its various elements. The concept of software-defined networking (SDN) describes networks and how they behave in a more flexible way – through software tools that describe network elements in terms of programmable network states.
To maximize the potential benefits and deliver superior user experience, software-defined networking (SDN) needs to be implemented outside the sphere of the data center across the entire network. This can be achieved through enabling network programmability based on open APIs. Service Provider SDN will help operators to scale networks and take advantage of new revenue-generating possibilities.
For more from Ericsson Review visit: http://www.ericsson.com/thinkingahead/technology_insights
SDN Performance evaluation for floodlight controller and OVS controller using adaptive approaches (i.e. statistical approach and genetic algorithm approach).
This volume of the Open Datacenter Interoperable Network (ODIN) describes software defined networking (SDN) and OpenFlow. SDN is used to simplify network control and management, automate network virtualization services, and provide a platform from which to build agile ....
Stuart Elby
VP, Network Architecture & Technology
Verizon
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
ENHANCING AND MEASURING THE PERFORMANCE IN SOFTWARE DEFINED NETWORKINGIJCNCJournal
Software Defined Networking (SDN) is a challenging chapter in today’s networking era. It is a network design approach that engages the framework to be controlled or 'altered' adroitly and halfway using programming applications. SDN is a serious advancement that assures to provide a better strategy than displaying the Quality of Service (QoS) approach in the present correspondence frameworks. SDN etymologically changes the lead and convenience of system instruments using the single high state program. It separates the system control and sending functions, empowering the network control to end up specifically. It provides more functionality and more flexibility than the traditional networks. A network administrator can easily shape the traffic without touching any individual switches and services which are needed in a network. The main technology for implementing SDN is a separation of data plane and control plane, network virtualization through programmability. The total amount of time in which user can respond is called response time. Throughput is known as how fast a network can send data. In this paper, we have design a network through which we have measured the Response Time and Throughput comparing with the Real-time Online Interactive Applications (ROIA), Multiple Packet Scheduler, and NOX.
Applications Drive Secure Lightpath Creation Across Heterogeneous DomainsTal Lavian Ph.D.
We realize an open, programmable paradigm for application-driven network control by way of a novel network plane — the “service plane” — layered above legacy networks. The service plane bridges domains, establishes trust, and exposes control to credited users/applications while preventing unauthorized access and resource theft. The Authentication, Authorization, Accounting subsystem and the Dynamic Resource Allocation Controller are the two defining building blocks of our service plane. In concert, they act upon an interconnection request or a restoration request according to application requirements, security credentials, and domain-resident policy. We have experimented with such service
plane in an optical, large-scale testbed featuring two hubs (NetherLight in Amsterdam, StarLight in Chicago) and attached network clouds, each representing an independent domain. The dynamic interconnection of the heterogeneous domains occurred at Layer 1. The interconnections ultimately resulted in an optical end-to-end path (lightpath) for use by the
requesting Grid application.
Air Force Provides Any Service, Anytime, Anywhere, Securely. Royal Saudi Air Force consolidates IT infrastructure with new Cisco network to improve operations, reduce cost, and easily and quickly launch new services.
Architecture evolution for automation and network programmabilityEricsson
http://www.ericsson.com/review
Automation and network programmability are key concepts in the evolution of telecom networks. Architecture designed with high degrees of automation and network programmability can rapidly adapt to emerging requirements, and as such improve operational efficiency and time to market for new services.
Ericsson Review: Software-Defined-NetworkingEricsson
An architecture based on software-defined networking (SDN) techniques gives operators greater freedom to balance operational and business parameters, such as network resilience, service performance and QoE against opex and capex. With its beginnings in data-center technology, software-defined networking (SDN) technology has developed to the point where it can offer significant opportunities to service providers.
The traditional way of describing network architecture and how a network behaves is through the fixed designs and behaviors of its various elements. The concept of software-defined networking (SDN) describes networks and how they behave in a more flexible way – through software tools that describe network elements in terms of programmable network states.
To maximize the potential benefits and deliver superior user experience, software-defined networking (SDN) needs to be implemented outside the sphere of the data center across the entire network. This can be achieved through enabling network programmability based on open APIs. Service Provider SDN will help operators to scale networks and take advantage of new revenue-generating possibilities.
For more from Ericsson Review visit: http://www.ericsson.com/thinkingahead/technology_insights
SDN Performance evaluation for floodlight controller and OVS controller using adaptive approaches (i.e. statistical approach and genetic algorithm approach).
This volume of the Open Datacenter Interoperable Network (ODIN) describes software defined networking (SDN) and OpenFlow. SDN is used to simplify network control and management, automate network virtualization services, and provide a platform from which to build agile ....
Stuart Elby
VP, Network Architecture & Technology
Verizon
ONS2015: http://bit.ly/ons2015sd
ONS Inspire! Webinars: http://bit.ly/oiw-sd
Watch the talk (video) on ONS Content Archives: http://bit.ly/ons-archives-sd
ENHANCING AND MEASURING THE PERFORMANCE IN SOFTWARE DEFINED NETWORKINGIJCNCJournal
Software Defined Networking (SDN) is a challenging chapter in today’s networking era. It is a network design approach that engages the framework to be controlled or 'altered' adroitly and halfway using programming applications. SDN is a serious advancement that assures to provide a better strategy than displaying the Quality of Service (QoS) approach in the present correspondence frameworks. SDN etymologically changes the lead and convenience of system instruments using the single high state program. It separates the system control and sending functions, empowering the network control to end up specifically. It provides more functionality and more flexibility than the traditional networks. A network administrator can easily shape the traffic without touching any individual switches and services which are needed in a network. The main technology for implementing SDN is a separation of data plane and control plane, network virtualization through programmability. The total amount of time in which user can respond is called response time. Throughput is known as how fast a network can send data. In this paper, we have design a network through which we have measured the Response Time and Throughput comparing with the Real-time Online Interactive Applications (ROIA), Multiple Packet Scheduler, and NOX.
Cloud computing and Software defined networkingsaigandham1
This is my Graduate defense presentation. I have interest in various topics like cloud computing and software defined networking. This slides includes the research of various researchers on cloud computing and SDN, presented their work as my comprehensive exam.
IT teams face unprecedented challenges to support dynamic application requirements on top of a rigid legacy infrastructure. A vendor-agnostic orchestration helps deliver rapid network
services for multi-vendor infrastructure. Anuta NCX platform with it’s layered, YANG model-driven and abstraction approach helps in delivering vendor neutral, extensible and maintainable
services for multiple domains such as Branch/CPE, Data Center, Cloud, and Carrier Core networks. The NCX platform enables customers and partners to develop their own Service and Device models for complete customization within few days. Many large enterprises and service providers have deployed NCX to orchestrate their brownfield and greenfield networks.
Similar to RTI/Cisco response to the OMG Software Defined Networks (SDN) RFI (20)
DDS Security Version 1.2 was adopted in 2024. This revision strengthens support for long runnings systems adding new cryptographic algorithms, certificate revocation, and hardness against DoS attacks.
From its first use case that enabled distributed communications for US Navy ships to the autonomous systems of today, the DDS family of standards has enabled new generations of applications to run reliably, rapidly and securely, regardless of distance or scale.
To commemorate the 20th year milestone, the DDS Foundation is creating presentations that highlight the 14 specifications in the DDS standard, along with selected real-world use cases.
This presentation introduces some of the original use-cases and experiments, along with a brief history of the Standards.
A recorded video of the presentation is available at this URL
https://www.brighttalk.com/webcast/12231/602966
Introduction to DDS: Context, Information Model, Security, and Applications.Gerardo Pardo-Castellote
Introduction to the Data-Distribution Service (DDS): Context and Applications.
This 50 minute presentation summarizes the main features of DDS including the information model, the type system, and security as well as how typical applications use DDS.
It was presented at the Canadian Government Information Day in Ottawa on September 2018.
There is also a video of this presentation at https://www.youtube.com/watch?v=6iICap5G7rw.
This Object Management Group (OMG) RFP solicits submissions identifying and defining mechanisms to achieve integration between DDS infrastructures and TSN networks. The goal is to provide all artifacts needed to support the design, deployment and execution of DDS systems over TSN networks.
The DDS-TSN integration specification sought shall realize the following functionality:
● Define mechanisms that provide the information required for TSN-enabled networks to calculate any network schedules needed to deploy a DDS system.
OMG RFP
● Identify those parts of the set of the IEEE TSN standards that are relevant for a DDS-TSN integration and indicate how the DDS aspects are mapped onto, or related to, the associated TSN aspects. Examples include TSN- standardized information models for calculating system-wide schedules and configuring network equipment.
● Identify and specify necessary extensions to the [DDSI-RTPS] and [DDS- SECURITY] specifications, if any, to allow DDS infrastructures to use TSN- enabled networks as their transport while maintaining interoperability between different DDS implementations.
● Identify and specify necessary extensions to the DDS and DDS- XML specification, if any, to allow declaration of TSN-specific properties or quality of service attributes.
A NEW ARCHITECTURE PROPOSAL TO INTEGRATE OPC UA, DDS & TSN.
Suppliers and end users need a complete solution to address the complexity of future industrial automation systems. These systems require:
• Interoperability to allow devices and independent software applications from multiple suppliers to work together seamlessly
• Extensibility to incorporate future large or intelligent systems
• Performance and flexibility to handle challenging deployments and use cases
• Robustness to guarantee continuity of operation despite partial failures
• Integrity and fine-grained security to protect against cyber attacks
• Widespread support for an industry standard
This document proposes a new technical architecture to build this future. The design combines the best of the OPC Unified Architecture (OPC UA), Data Distribution Service (DDS), and Time-Sensitive Networking (TSN) standards. It will connect the factory floor to the enterprise, sensors to cloud, and real-time devices to work cells. This proposal aims to define and standardize the architecture to unify the industry.
Technical overview of the DDS for Extremely Resource-Constrained Environments (DDS-XRCE) specification.
This specification was adopted by the OMG in March 2018.
Demonstrates interoperability of 5 independent products that implement the Data-Distribution Service (DDS) Security Standard
(https://www.omg.org/spec/DDS-SECURITY/).
Tests the following implementations: RTI Connext DDS, Twin Oaks Computing CoreDX DDS, Kongsberg InterComm DDS, ADLink Vortex DDS Cafe, and Object Computing Inc OpenDDS.
This demonstration was performed at the OMG Meeting held in Reston, VA, USA in March 2018
Applying MBSE to the Industrial IoT: Using SysML with Connext DDS and SimulinkGerardo Pardo-Castellote
The benefits of Model-Based Systems Engineering (MBSE) and SysML are well established. As a result, users want to apply MBSE to larger and more complex Industrial IoT applications.
Industrial IoT applications can be very challenging: They are distributed. They deploy components across nodes spanning from small Devices to Edge computers to the Cloud. They often need mathematically-complex software. Moreover, they have strict requirements in terms of performance, robustness, and security.
SysML can model requirements, system components, behavior, interactions, and more. However, SysML does not provide a robust way to connect components running across different computers, especially when the security and quality of service of individual data-flows matter. SysML also does not provide all the tools needed to model and generate the (mathematical) code for complex dynamic systems.
A new “DDS + Simulink” MagicDraw SysML plugin has been developed to addresses these needs. It brings to MagicDraw users the capabilities of Connext DDS from RTI and Simulink from Mathworks:
The OMG Data-Distribution Service (DDS) is a secure and Qos-aware connectivity “databus”. DDS is considered the core connectivity framework for Software Integration and Autonomy by the Industrial Internet Consortium. Connext DDS is the leading implementation of the DDS standard, proven in 1000s of critical deployments.
Simulink is a tool for modeling and implementing the code needed for complex dynamic systems. It is widely deployed in many application domains including Automotive, Robotics, and Control Systems.
The new MagicDraw plugin defines a “DDS profile” for SysML that can model a distributed application connected using the DDS databus. The plugin can also generate the artifacts that configure the DDS databus (Topics, Data Types, Qos, etc.) and the adapters to Simulink and native code (e.g. C++ or Java).
By integrating three best-of class technologies: SysML, DDS and Simulink it is now possible to do MBSE for a wide range of Industrial IoT applications.
One of the most important challenges that system designers and system integrators face when deploying complex Industrial Internet of Things (IoT) systems is the integration of different connectivity solutions and standards. At RTI, we are constantly working to accelerate the Industrial IoT revolution. Over the past few years, we have developed standard connectivity gateways to ensure that DDS systems can easily integrate with other core connectivity frameworks.
This year, we developed a standard OPC UA/DDS Gateway, a bridge between two of the most well-known Industrial IoT connectivity frameworks. We are excited to announce that the gateway was just adopted by the Object Management Group (OMG).
In this webinar, we will dive deeper into the importance of choosing a baseline core connectivity standard for the Industrial IoT and how to ensure all system components are fully integrated. Attendees will also learn:
How the OPC UA/DDS Gateway specification was developed and how it works
How to leverage the Gateway to enable DDS and OPC UA applications to interoperate transparently
About the first standard connectivity gateway released with RTI Web Integration Service in Connext DDS 5.3
Gateways are a critical component of system interoperability and we will keep working to help companies accelerate Industrial IoT adoption.
This is the Beta 1 version of the OPC UA / DDS Gateway specification released by the Object Management Group in March 2018.
This specification defines a standard, vendor-independent, configurable gateway that enables interoperability and information exchange between systems that use DDS and systems that use OPC UA.
Data Distribution Service (DDS) is a family of standards from the Object Management Group (OMG) that provide connectivity, interoperability, and portability for Industrial Internet, cyber-physical, and mission-critical applications.
The DDS connectivity standards cover Publish-Subscribe (DDS), Service Invocation (DDS-RPC), Interoperability (DDS-RTPS), Information Modeling (DDS-XTYPES), Security (DDS-SECURITY), as well as programing APIs for C, C++, Java and other languages.
The OPC Unified Architecture (OPC UA) is an information exchange standard for Industrial Automation and related systems created by the OPC Foundation. The OPC UA standard provides an Addressing and Information Model for Data Access, Alarms, and Service invocation layered over multiple transport-level protocols such as Binary TCP and Web-Services.
DDS and OPC UA exhibit significant deployment similarities:
• Both enable independently developed applications to interoperate even when those applications come from different vendors, use different programming languages, or run on different platforms and operating systems.
• Both have significant traction within Industrial Automation systems.
• Both define standard protocols built on top of the TCP/ UDP/IP Internet stacks.
The two technologies may coexist within the same application domains; however, while there are solutions that bridge between DDS and OPC UA, these are based on custom mappings and cannot be relied to work across vendors and products.
This is the DDS-XRCE 1.0 Beta specification adopted by the OMG March 2018.
The purpose of DDS-XRCE is to enable resource-constrained devices to participate in DDS communication, while at the same time allowing those devices to be disconnected for long periods of time but still be discoverable by other DDS applications.
DDS-XRCE defines a wire protocol, the DDS-XRCE protocol, to be used between an XRCE Client and XRCE Agent. The XRCE Agent is a DDS Participant in the DDS Global Data Space. The DDS-XRCE protocol allows the client to use the XRCE Agent as a proxy in order to produce and consume data in the DDS Global Data Space.
Demonstrates interoperability of 5 independent products that implement the Data-Distribution Service (DDS) Security Standard
(https://www.omg.org/spec/DDS-SECURITY/).
Tests the following implementations: RTI Connext DDS, Twin Oaks Computing CoreDX DDS, Kongsberg InterComm DDS, ADLink Vortex DDS Cafe, and Object Computing Inc OpenDDS.
Demonstrates interoperability of 3 independent products that implement the Data-Distribution Service (DDS) Security Standard
(https://www.omg.org/spec/DDS-SECURITY/).
Tests the following implementations: RTI Connext DDS, Twin Oaks Computing CoreDX DDS, and Kongsberg InterComm DDS.
This specification provides the following additional facilities to DDS [DDS] implementations and users:
* Type System. The specification defines a model of the data types that can be used for DDS Topics. The type system is formally defined using UML. The Type System is de- fined in section 7.2 and its subsections. The structural model of this system is defined in the Type System Model in section 7.2.2. The framework under which types can be modi- fied over time is summarized in section 7.2.3, “Type Extensibility and Mutability.” The concrete rules under which the concepts from 7.2.2 and 7.2.3 come together to define compatibility in the face of such modifications are defined in section 7.2.4, “Type Com- patibility.”
* Type Representations. The specification defines the ways in which types described by the Type System may be externalized such that they can be stored in a file or communi- cated over a network. The specification adds additional Type Representations beyond the
DDS-XTypes version 1.2 1
one (IDL [IDL41]) already implied by the DDS specification. Several Type Representa- tions are specified in the subsections of section 7.3. These include IDL (7.3.1), XML (7.3.2), XML Schema (XSD) (7.3.3), and TypeObject (7.3.4).
* Data Representation. The specification defines multiple ways in which objects of the types defined by the Type System may be externalized such that they can be stored in a file or communicated over a network. (This is also commonly referred as “data serializa- tion” or “data marshaling.”) The specification extends and generalizes the mechanisms already defined by the DDS Interoperability specification [RTPS]. The specification in- cludes Data Representations that support data type evolution, that is, allow a data type to change in certain well-defined ways without breaking communication. Two Data Repre- sentations are specified in the subsections of section 7.4. These are Extended CDR (7.4.1, 7.4.2, and 7.4.3) and XML (7.4.4).
* Language Binding. The specification defines multiple ways in which applications can access the state of objects defined by the Type System. The submission extends and gen- eralizes the mechanism currently implied by the DDS specification (“Plain Language Binding”) and adds a Dynamic Language Binding that allows application to access data without compile-time knowledge of its type. The specification also defines an API to de- fine and manipulate data types programmatically. Two Language Bindings are specified in the subsections of section 7.5. These are the Plain Language Binding and the Dynamic Language Binding.
This specification defines the Security Model and Service Plugin Interface (SPI) architecture for compliant DDS implementations. The DDS Security Model is enforced by the invocation of these SPIs by the DDS implementation. This specification also defines a set of builtin implementations of these SPIs.
* Authentication Service Plugin. Provides the means to verify the identity of the application and/or user that invokes operations on DDS. Includes facilities to perform mutual authentication between participants and establish a shared secret.
* AccessControl Service Plugin. Provides the means to enforce policy decisions on what DDS related operations an authenticated user can perform. For example, which domains it can join, which Topics it can publish or subscribe to, etc.
* Cryptographic Service Plugin. Implements (or interfaces with libraries that implement) all cryptographic operations including encryption, decryption, hashing, digital signatures, etc. This includes the means to derive keys from a shared secret.
* Logging Service Plugin. Supports auditing of all DDS security-relevant events Data Tagging Service Plugin. Provides a way to add tags to data samples.
This document specifies the OMG Interface Definition Language (IDL). IDL is a descriptive language used to define data types and interfaces in a way that is independent of the programming language or operating system/processor platform.
The IDL specifies only the syntax used to define the data types and interfaces. It is normally used in connection with other specifications that further define how these types/interfaces are utilized in specific contexts and platforms.
This the the formal version 1.0 of the DDS Security specification released September 2016. OMG document number formal/2016-08-01.
DDS-Security defines the Security Model and Service Plugin Interface (SPI) architecture for compliant DDS implementations.
The DDS Security Model is enforced by the invocation of these SPIs by the DDS implementation. This specification also defines a set of builtin implementations of these SPIs.
* The specified builtin SPI implementations enable out-of-the box security and interoperability between compliant DDS applications.
* The use of SPIs allows DDS users to customize the behavior and technologies that the DDS implementations use for Information Assurance, specifically customization of Authentication, Access Control, Encryption, Message Authentication, Digital Signing, Logging and Data Tagging.
This specification is a response to the OMG RFP "eXtremely Resource Constrained Environments DDS (DDS- XRCE)"
It defines a DDS-XRCE Service based on a client-server protocol between a resource constrained, low-powered device (client) and an Agent (the server) that enables the device to communicate with a DDS network and publish and subscribe to topics in a DDS domain. The specifications purpose and scope is to ensure that applications based on different vendor’ implementations of the DDS-XRCE Service are compatible and interoperable.
This is the Joint submission by RTI, TwinOaks, and eProsima. Updated September 2017, OMG document number mars/2017-09-18.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Accelerate your Kubernetes clusters with Varnish CachingThijs Feryn
A presentation about the usage and availability of Varnish on Kubernetes. This talk explores the capabilities of Varnish caching and shows how to use the Varnish Helm chart to deploy it to Kubernetes.
This presentation was delivered at K8SUG Singapore. See https://feryn.eu/presentations/accelerate-your-kubernetes-clusters-with-varnish-caching-k8sug-singapore-28-2024 for more details.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Essentials of Automations: Optimizing FME Workflows with ParametersSafe Software
Are you looking to streamline your workflows and boost your projects’ efficiency? Do you find yourself searching for ways to add flexibility and control over your FME workflows? If so, you’re in the right place.
Join us for an insightful dive into the world of FME parameters, a critical element in optimizing workflow efficiency. This webinar marks the beginning of our three-part “Essentials of Automation” series. This first webinar is designed to equip you with the knowledge and skills to utilize parameters effectively: enhancing the flexibility, maintainability, and user control of your FME projects.
Here’s what you’ll gain:
- Essentials of FME Parameters: Understand the pivotal role of parameters, including Reader/Writer, Transformer, User, and FME Flow categories. Discover how they are the key to unlocking automation and optimization within your workflows.
- Practical Applications in FME Form: Delve into key user parameter types including choice, connections, and file URLs. Allow users to control how a workflow runs, making your workflows more reusable. Learn to import values and deliver the best user experience for your workflows while enhancing accuracy.
- Optimization Strategies in FME Flow: Explore the creation and strategic deployment of parameters in FME Flow, including the use of deployment and geometry parameters, to maximize workflow efficiency.
- Pro Tips for Success: Gain insights on parameterizing connections and leveraging new features like Conditional Visibility for clarity and simplicity.
We’ll wrap up with a glimpse into future webinars, followed by a Q&A session to address your specific questions surrounding this topic.
Don’t miss this opportunity to elevate your FME expertise and drive your projects to new heights of efficiency.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
Slack (or Teams) Automation for Bonterra Impact Management (fka Social Soluti...Jeffrey Haguewood
Sidekick Solutions uses Bonterra Impact Management (fka Social Solutions Apricot) and automation solutions to integrate data for business workflows.
We believe integration and automation are essential to user experience and the promise of efficient work through technology. Automation is the critical ingredient to realizing that full vision. We develop integration products and services for Bonterra Case Management software to support the deployment of automations for a variety of use cases.
This video focuses on the notifications, alerts, and approval requests using Slack for Bonterra Impact Management. The solutions covered in this webinar can also be deployed for Microsoft Teams.
Interested in deploying notification automations for Bonterra Impact Management? Contact us at sales@sidekicksolutionsllc.com to discuss next steps.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
RTI/Cisco response to the OMG Software Defined Networks (SDN) RFI
1. OMG
SDN
RFI
Response
from
RTI
and
Cisco
Contacts:
Gerardo
Pardo-‐Castellote
(RTI)
gerardo
AT
rti
DOT
com
Gary
Berger
(Cisco)
gaberger
AT
cisco
DOT
com
1 Summary
It
is
well
understood
that
OpenFlow
is
a
low-‐level
interface
for
network
programming
surfacing
the
need
for
a
high-‐level
programming
model
to
help
developers
reap
the
benefits
of
simplified
network
management.
SDN
programming
relies
on
the
ability
to
query
network
state,
define
forwarding
policies
and
update
policies
in
a
consistent
way.
Another
important
aspect
is
the
management
and
configuration
interfaces
across
heterogeneous
devices.
Current
northbound
API’s
still
force
developers
to
think
in
terms
of
match-‐action
rules
and
not
in
higher
level
abstractions
with
proper
compositional
semantics
[12-‐
14].
Part
of
the
problem
lies
in
the
various
protocols
being
adopted
for
SDN
including
OpenFlow,
OF-‐CONFIG,
PCEP,
I2RS,
OVSDB,
IF-‐MAP,
OnePK,
etc.
Vendors
must
either
build
adapters
for
each
or
rely
on
a
mediation
server
such
as
OpenDaylight
Controller
Service
Abstraction
Layer
[20]
to
provide
the
mediation
between
protocols.
Each
of
these
protocols
expands
the
feature
space
with
sometimes
conflicting
behaviors
and
representations
making
it
difficult
to
design
a
high-‐level
interface
which
addresses
the
developers
need
to
build
applications
out
of
multiple
independent
and
reusable
network
policies
that
must
act
on
the
same
traffic
[12].
With
this
in
mind,
the
first
step
towards
developing
and/or
standardizing
a
Northbound
protocol
and/or
API
should
be
the
standardization
of
the
information
model
that
represents
the
observable
and
controllable
state
of
the
SDN
network
elements.
Model
Driven
Architectures
are
fundamental
to
building
platform
and
computation
independent
services
[18].
SDN
adopts
some
of
these
principals
leveraging
schema
driven
approaches
[16]
and
data
driven
models
[17]
but
there
are
no
efforts
to
converge
onto
a
well-‐understood
model
that
can
be
used
to
define
the
protocol
and
API
interaction.
In
this
respect
our
motivation
is
to
leverage
existing
middleware
technologies
and
architectures
such
as
DDS,
XMPP,
AMQP
and
REST
to
provide
an
extensible
and
www.rti.com
www.cisco.com
2. adaptable
protocol,
which
will
promote
unification
and
simplify
access
to
the
goals
of
querying
state,
notification
of
changes,
forwarding
policy,
security
and
performance
policies.
For
instance
leveraging
middleware
platforms
which
can
automatically
define
the
network
data
representations,
network
protocols,
discovery
mechanism,
and
the
means
to
scale
in
a
fault
tolerant
way
would
allow
more
concentration
on
the
higher
level
abstractions,
composition
and
segmentation
of
controller
logic.
In
addition
these
middleware
platforms
provide
standard
APIs
in
different
programming
languages,
so
the
API
also
comes
“for
free”
once
the
mapping
is
done.
While
technically
it
may
be
possible
we
do
not
believe
that
it
would
be
practical
to
define
a
single
middleware
platform
because
different
providers
have
strong
preferences
and
deployed
technologies
and
are
unlikely
to
simply
agree
to
a
common
middleware
platform.
Beyond
practical
agreement,
having
multiple
middleware
platforms
leaves
the
door
open
for
innovation
and
evolution,
and
moreover
it
may
provide
technical
advantages
as
different
middleware
technologies
differ
in
scalability,
performance
and
support
for
communications
patterns
and
QoS.
The
support
and
co-‐existence
of
multiple
middleware
platforms
is
also
necessary
to
accommodate
legacy
systems
and
should
not
introduce
too
much
complexity
as
long
as
they
all
map
a
common
SDN
information
model.
2 RFI
Response
SDN
systems
provide
opportunity
to
separate
control
plane
services
from
the
data
plane.
Traditional
networks
distribute
state
through
embedded
control
algorithms
leveraging
many
different
protocols
(RIP,
LLDP,
OSPF,
etc).
This
model
has
been
proven
inflexible
and
complex
due
to
the
diversity
of
devices
and
the
use
of
closed
proprietary
vendor-‐specific
interfaces
and
the
need
to
individually
configure
each
device.
Recently
OpenFlow
has
emerged
as
a
standard
protocol
that
can
be
used
to
configure
these
devices
and
query
their
state.
It
is
already
supported
by
many
network
device
vendors
and
deployed
in
datacenters
and
backbone
networks.
However,
it
is
a
low-‐level
protocol,
has
been
difficult
to
program
against,
and
it
is
but
one
of
many
approaches
currently
being
explored
[21].
It
is
also
desirable
to
offer
incremental
ways
to
migrate
legacy
systems
to
SDN
and
provide
leave
the
door
open
for
innovation
and
evolution.
Our
perspective
is
that
multiple
protocols
and
APIs
will
necessarily
co-‐exist
and
therefore
the
first
step
to
add
a
layer
of
abstraction
creating
a
unified
architecture.
It
is
our
goal
to
define
a
solid
and
evolvable
information
model
that
can
be
used
as
the
foundation
to
map
and
bridge
existing
protocols.
The
model
should
be
www.rti.com
www.cisco.com
3. independent
of
specific
middleware
platforms
or
technologies
and
be
comprehensive
enough
to
allow
those
existing
platforms
to
be
mapped.
We
believe
that
the
most
promising
approach
would
be
use
UML
to
define
a
data-‐
centric
information
model.
A
data-‐centric
model
has
the
advantage
of
making
no
assumptions
about
protocols,
interactions,
or
APIs.
It
simply
models
the
information:
flows,
access
rules,
statistics,
these
are
things
that
are
reasonable
well
understood
and
agreed
in
the
SDN
community.
Being
grounded
in
the
physics
of
network
flows
the
model
is
also
more
stable
than
APIs,
protocols,
and
policies.
Once
a
the
UML
data-‐centric
information
model
is
developed
it
can
be
mapped
to
legacy
technologies,
such
as
SNMP,
standards
like
Open
Flow,
and
vendor-‐
proprietary
mechanisms
such
as
Cisco
OnePK,
Juniper
Contrail,
VmWare
NSX.
This
provides
an
open
and
evolvable
way
to
interact
with
the
network
devices.
In
addition
to
mapping
to
low
level
device
oriented
protocols
such
as
OpenFlow,
the
data-‐centric
information
model
can
also
be
mapped
to
existing
middleware
platforms
such
as
DDS,
XMPP,
and
AMQP.
These
mappings
provide
the
scalable
distribution
protocols,
network
representations,
and
language
APIs
needed
to
interact
remotely.
Controllers
could
use
one
or
more
of
these
technologies
to
access
the
state
of
the
network
devices
and
modify
their
configuration.
Using
standard
middleware
technologies
avoids
“reinventing
the
wheel”
and
leverages
the
middleware
technology
platform
for
the
things
it
is
very
good
at:
scalable
and
robust
distribution
of
information.
For
example
DDS
already
provides
mechanisms
for
discovery,
asynchronous
notification,
scalable
content-‐based
subscription,
reliability
in
the
presence
of
connection
failures,
data-‐distribution
Qos,
robust
management
of
DIL
environments,
etc.
Other
middleware
technologies,
XMPP,
AMQP,
REST,
also
provide
valuable
capabilities
that
would
be
automatically
leveraged.
3 Response
to
the
specific
questions
in
the
RFI
3.1 How
does
the
SDN
ecosystem
maintain
an
open,
vendor-‐neutral,
abstract
set
of
APIs
for
network
related
entities
including
but
not
limited
to
elements,
flows,
policies
and
applications?
Rationale:
To
simplify
network
related
application
development
for
new
and
existing
SDN
controllers
This
could
be
accomplished
in
two
steps:
a) A
vendor-‐neutral
data-‐centric
information
model
could
be
defined
that
covers
the
observable
state
of
the
software-‐controlled
network
elements
(controllers,
switches,
etc.),
the
controllable
services
it
offers,
and
the
mechanisms
to
control
that
state.
b)
The
information
model
could
be
mapped
to
a
variety
of
standard
protocols
offering
API
portability
and
network
interoperability.
For
example
DDS,
REST,
or
XMPP
www.rti.com
www.cisco.com
4. The
vendor
neutral
information
model
could
be
defined
using
UML.
This
higher-‐
level
model
expresses
the
kind
of
information
that
can
be
observed
from
the
network
elements,
such
as
flow
information,
the
associated
schemas,
neighboring
information,
link-‐status,
etc.
It
also
describes
the
kinds
of
control-‐commands
that
are
accepted
by
the
switch.
While
a
normalization
of
this
is
desirable
it
is
not
strictly
necessary
as
the
model
could
encompass
different
versions
(as
would
be
derived
from
different
versions
of
open
flow
versus
Cisco
OnePK,
and
even
multiple
versions
of
those).
The
information
model
would
be
data-‐centric
because
it
focuses
on
exposing
the
state
of
the
network
elements
and
their
controllable
elements
and
not
specifically
on
sequences
of
commands,
message-‐exchange
or
handshakes.
This
approach
maps
well
to
middleware
technologies
such
as
REST
and
DDS
and
has
been
proven
to
be
simpler
and
more
scalable
than
an
RPC
or
RMI
oriented
model.
The
mapping
of
the
data-‐centric
information
model
two
different
middleware
platforms
would
provide
the
portable
and
interoperable
APIs
to
interact
with
the
network
elements.
The
set
of
mapped
middleware
technologies
can
remain
open
and
evolve.
Supporting
more
than
one
approach
provides
significant
benefits:
(a)
(b)
Different
middleware
technologies
offer
different
tradeoffs
with
regards
to
performance,
scalability,
and
ease
of
use,
and
Practically
it
would
be
next
to
impossible
to
have
everyone
“agree”
on
a
single
middleware
given
that
existing
players
have
strong
preferences
for
technologies
they
are
familiar
with
or
have
vested
interest
in
(XMPP,
AMQP,
HTTP/REST,
DDS).
Beyond
the
practical
advantages,
the
effort
of
mapping
a
middleware
is
reasonably
small.
Protocols,
data-‐formats,
language
APIs,
etc.
are
all
defined
and
provided
by
each
middleware
platform.
All
it
takes
is
a
mapping
of
the
information
model
to
the
artifacts
the
middleware
provides)
and
having
multiple
does
not
create
significant
complexity.
Since
all
the
middleware
mappings
originate
from
a
common
information
model
the
bridging
can
be
done
by
automatic
tools
or
well
defined
gateway
services.
3.2 How
does
the
SDN
ecosystem
support
network
related
entity
discovery,
connection,
configuration,
performance
and
fault
management?
Rationale:
To
maintain
the
functional
network
management
capabilities
available
to
legacy
non-SDN
networks
These
features
would
come
from
the
facilities
provided
by
the
middleware
platform
and
the
mapping
of
the
SDN
information
model
to
the
corresponding.
Middleware
platform.
When
using
DDS
entity
discovery
would
be
provided
by
the
built-‐in
DDS-‐
Entity
discovery
mechanism
similarly
for
XMPP
and
other
middleware
platforms.
www.rti.com
www.cisco.com
5. 3.3 How
does
the
SDN
ecosystem
support
interoperability
of
network
control
and
operational
data
at-‐rest
and
in-‐motion?
Rationale:
Exposure
and
marshaling
in
consistent
data
formats,
structures
simplifies
network
related
application
development.
Similar
to
the
previous.
This
would
simply
leverage
the
mechanisms
provide
by
the
middleware
platforms.
3.4 How
does
the
SDN
ecosystem
support
multiple
programming
languages?
Rationale:
To
enable
an
evolving
and
diverse
SDN
ecosystem
for
application
development.
Similar
to
the
previous.
This
is
already
provided
by
the
different
middleware
platforms.
3.5 What
architectural
patterns
could
mitigate
the
Controller
choke
point
problem?
(e.g.,
Could
separation
of
operational
data
collection
from
network
data
achieve
this?)
Rationale:
Existing
network
architectures
create
a
constricted
conduit
through
which
operational
data
flows
to
network
controllers.
Scaling
up
the
number
of
controllers,
switches,
and
appliances
compounds
the
problem.
Scaling
the
information
distribution
is
something
that
middleware
platforms
are
already
doing.
This
one
of
their
fundamental
value-‐adds
to
a
system.
The
key
point
is
that
the
proposed
approach
leverages
the
technology
and
investment
that
the
middleware
providers
are
doing.
It
would
seem
that
the
publish-‐subscribe
pattern
offered
y
technologies
such
as
DDS,
XMPP,
and
AMQP
could
be
one
of
the
main
architectural
patterns.
Beyond
that,
using
peer-‐to-‐peer
middleware
platforms
such
as
DDS
and
XMPP,
which
unlike
AMQP
do
not
force
messages
to
flow
via
intermediate
points
or
brokers,
would
be
important
to
avoid
introducing
additional
choke
points.
3.6 How
does
the
SDN
ecosystem
support
existing
networking
standards?
Rationale:
To
enable
co-existence
for
legacy
network
components
such
as
Simple
Network
Management
Protocol
(SNMP).
Existing
network
standards
would
be
mapped
to
the
SDN
information
model,
similar
to
how
the
new
middleware
platforms
are
mapped.
Once
this
is
done
it
is
possible
to
develop
gateways
that
would
translate
between
those
standards
and
the
ones
the
operator
chooses
to
deploy.
www.rti.com
www.cisco.com
6. 3.7 Does
the
response
relate
to
other
SDN
efforts
underway?
Rationale:
To
enable
collaboration
and
avoid
conflicts
and
redundancies
between
SDN
community
efforts.
The
OMG
would
focus
on
the
areas
in
its
areas
of
core
expertise,
namely
leveraging
the
existing
UML
and
middleware
standards
to
providing
suitable
ways
to
model
the
SDN
information
and
map
it
to
middleware
technologies
such
as
DDS,
REST,
and
XMPP.
The
SDN
information
model
is
proposed
here
would
provide
a
framework
in
which
multiple
standards
would
co-‐exists
and
also
provide
the
tools
necessary
to
bridge
and
harmonize
between
those
standards.
3.8 How
are
SDN
ecosystem
events
from
data
and
controller
planes
etc.
handled?
Rationale:
Existing
SDN
architectures
are
perceived
to
have
scaling
issues
attributed
to
network
status
and
configuration
polling.
These
mechanisms
are
provided
by
the
middleware
platform.
The
use
of
middleware
platforms
that
support
scalable
event-‐distribution
mechanisms
would
address
this.
For
example
when
using
DDS
the
publish-‐subscribe
pattern
combined
with
the
writer-‐side
content-‐based
filtering
that
DDS
offers
would
provide
the
scalable
event
distribution.
3.9 How
does
the
ecosystem
interoperate
with
legacy
network
architectures?
Rationale:
To
enable
co-existence
for
legacy
network
components
and
support
evolving
network
topologies.
Yes.
To
the
extent
that
legacy
approaches
can
be
mapped
to
the
Information
Model
and
a
proper
gateway
is
developed.
3.10 How
does
the
SDN
ecosystem
support
federated
data
centers?
Rationale:
The
purpose
of
aggregating
Control
Planes
is
to
optimize
data
requests
from
SDN
applications.
In
a
distributed
data
center
environment,
aggregation
into
a
single
Control
Plane
can
cause
unacceptable
latency.
This
is
also
typically
provided
by
the
different
middleware
platforms.
DDS
for
example
supports
smart
federations.
3.11 How
does
the
SDN
ecosystem
handle
Disconnected,
Intermittent,
and
Limited
(DIL)
environments?
Rationale:
Many
controllers,
switches,
and
appliances
are
deployed
within
mobile
environments
such
as
airplanes,
ships,
trains,
and
cars.
These
environments
will
experience
intermittent
connectivity
with
times
of
no
connectivity
or
restricted
bandwidth.
www.rti.com
www.cisco.com
7. Similar
to
the
previous
this
type
of
facility
is
already
provided
by
middleware
platforms
such
as
DDS
so
it
would
become
automatically
available
when
using
that
platform.
Since
multiple
middleware
platforms
can
co-‐exist
and
be
bridged
it
is
always
possible
to
choose
one
of
the
most
appropriate
middleware
platform
to
handle
the
DIL
portions
of
the
system.
4 References
1)
OpenFlow
https://www.opennetworking.org/images/stories/downloads/sdn-‐
resources/onf-‐specifications/openflow/openflow-‐spec-‐v1.4.0.pdf
2)
Cisco
OnePK.
http://www.cisco.com/en/US/prod/iosswrel/onepk.html
3)
Opendaylight
project.
http://www.opendaylight.org/
4)
Juniper
Contrail
Architecture
http://www.juniper.net/us/en/local/pdf/whitepapers/2000535-‐en.pdf
5)
Conry
Murray,
Andrew
“Cisco
and
OpenDaylight:
The
SDN
Application
Land
Grab”
6)
VMWare
NSX
http://cto.vmware.com/introducing-‐vmware-‐nsx-‐the-‐platform-‐
for-‐network-‐virtualization/
7)
OMG
Data-‐Distribution
Service
specification
(DDS).
www.omg.org/spec/DDS/1.2/
8)
The
Real-‐Time
Publish-‐Subscribe
Wire
Protocol
DDS
Interoperability
Wire
Protocol
(DDS-‐RTPS)
http://www.omg.org/spec/DDS-‐RTPS/
9)
Extensible
And
Dynamic
Topic
Types
For
DDS
(DDS-‐XTypes).
http://www.omg.org/spec/DDS-‐XTypes/
10)
Extensible
Messaging
and
Presence
Protocol
(XMPP)
.
http://tools.ietf.org/html/rfc6120
11)
Advanced
Message
Queuing
Protocol
(AMQP)
http://docs.oasis-‐
open.org/amqp/core/v1.0/amqp-‐core-‐complete-‐v1.0.pdf
12)
Christopher
Monsanto,
Joshua
Reich,
Nate
Foster,
Jennifer
Rexford,
and
David
Walker.
Composing
Software
Defined
Networks.
In
USENIX
Symposium
on
Networked
Systems
Design
and
Implementation
(NSDI),
Lombard,
IL,
April
2013
13)
Nate
Foster,
Michael
J.
Freedman,
Arjun
Guha,
Rob
Harrison,
Naga
Praveen
Katta,
Christopher
Monsanto,
Joshua
Reich,
Mark
Reitblatt,
Jennifer
Rexford,
Cole
Schlesinger,
Alec
Story,
and
David
Walker.
Languages
for
software-‐
defined
networks.
IEEE
Communications
Magazine,
51(2):128-‐134,
2013.
www.rti.com
www.cisco.com
8. 14)
Joshua
Reich,
Christopher
Monsanto,
Nate
Foster,
Jennifer
Rexford,
and
David
Walker.
Modular
SDN
Programming
with
Pyretic.
;login
Magazine,
38(5):128-‐
134,
2013.
15)
A.
Voellmy,
H.
Kim,
and
N.
Feamster.
Procera:
a
language
for
high-‐level
reactive
network
control.
In
Proceedings
of
the
first
workshop
on
hot
topics
in
software
defined
networks,
HotSDN
'12,
pages
43{48,Helsinki,
Finland,
2012.
16)
http://git.openvswitch.org/cgi-‐
bin/gitweb.cgi?p=openvswitch;a=blob;f=vswitchd/vswitch.ovsschema
17)
https://wiki.opendaylight.org/view/YANG_Tools:YANG_to_Java_Mapping
18)
http://www.omg.org/cgi-‐bin/doc?omg/03-‐06-‐01
19)
http://tools.ietf.org/html/rfc6020
20)
OpenDaylight
Controller
https://wiki.opendaylight.org/view/OpenDaylight_Controller:MD-‐
SAL:Architecture
21)
Guide:
Vendors
take
alternatives
to
OpenFlow
SDN.
http://searchsdn.techtarget.com/guides/Guide-‐OpenFlow-‐SDN-‐not-‐the-‐only-‐
show-‐in-‐town-‐for-‐vendors
www.rti.com
www.cisco.com