Phoenix: Concepts, Services, Technology Brief
Introduction
The Phoenix environment is a suite of technologies and services, developed and supported by BlueDot Insight. Phoenix services and technologies merge the rapid evolution and adaptability of Software Defined Networking (SDN) with the most advanced programmable silicon available, the E2100 Infrastructure Processing Unit (IPU) chip from Intel.
The Phoenix suite also incorporates the use of standard Broadcom networking chips as “front end” classification and load partitioning. Together, our SDN software, Intel IPUs, and Broadcom silicon are combined in configurations that deliver state-of-the-art, next-generation solutions. New functionality and lower price points are the result.
The Phoenix environment comprises concept designs, templates, prototypes, training materials, and consulting services. These items are delivered in six packages:
- Pheonix Concept
- Pheonix Frameworks
- Pheonix Platforms
- Pheonix Application Prototypes
- Phoenix POC (Proof of Concept) Consulting
- Phoenix Learning Center
- Phoenix ‘Concierge’ Training Services
Each of the Phoenix packages is highlighted below.
Phoenix Concept
The Phoenix Concept is an architecture for the next generation of SDN solutions. It is highly flexible, programmable, and scaleable.
Central to this architecture is the Intel® IPU , a cutting-edge P4-based parser and pipeline. This programmable hardware accelerator plays a crucial role in enhancing the capabilities of SDN devices, enabling them to deliver unprecedented levels of innovation, performance, security, and flexibility.
The target markets of the Phoenix Concept Telecommunication and Intelligence services. Both markets have demanding throughput requirements that exceed the capabilities of a single Intel IPU. Therefore, the Phoenix architecture is designed with a cluster of Intel IPU, with each a P4-based programmable chip acting in a “service” role running the same algorithm.
The final two major component of the Phoenix Cluster are the controller and analytics.
The AMD IPU is built on a P4-based programmable architecture, which allows network administrators to tailor data processing tasks to meet specific requirements. This flexibility is essential for implementing complex SDN functions, such as dynamic traffic management, advanced security protocols, and real-time analytics.
The advent of Software Defined Networking (SDN) has revolutionized the way networks are managed, controlled, and optimized. Central to this revolution is the Intel IPU (Infrastructure Processing Unit), a cutting-edge technology developed in conjuction with Google. This programmable hardware accelerator plays a crucial role in enhancing the capabilities of SDN devices, enabling them to deliver unprecedented levels of performance, security, and flexibility.
Phoenix Frameworks
Phoenix Frameworks are high-level concepts and designs. Each Phoenix Framework addesses a specific
These always start with a concept statement that defines the problem or issue we are trying to solve.
Next is the element functional block diagram. This lays out the overall architecture of the software and silicon for the concept. This set also includes descriptions of the key algorithms derived, followed by an algorithm description.
For example, our basic training framework focuses on the problem of getting engineers new to the P4 programming environment, used with x86, up to speed. Here, the framework is based on a virtual P4 device, a NodeJS controller environment, and x86 traffic generation software.
In another framework, the large flow table framework focuses on applications requiring a very large state model. An example is volumetric DDoS attack analytics. The concept is a single design that can scale from a 100G device to a multi-terabit device. Here, the framework is a Broadcom switch chip partitioning traffic to a fleet of IPUs, a NodeJS controller environment, and an x86 cluster for traffic generators.
In summary, a Phoenix Framework includes:
- A concept statement
- A high-level element architecture with a block diagram
- Detailed descriptions of key algorithms
- Detailed roles/functionality of each element
Phoenix Platforms
A Pheonix Platform is an operational template that implements a Pheonix Framework. It consists of:
- A specific hardware infrastructure
- A specific revision controlled software BOM. This includes the Intel IPU and Broadcom software plus Bluedot Insight P4 pipeline code and nodeJS controller
- Design and implementation scripts for x86 base traffic generation
- Procedures and installation scripts
- User documentation including wiring diagrams, life-of-a-packet documentation, and how-to cookbooks
The goal of a Phoenix Platform is to provide a operational application development base that supports a specific SDN Use Case. Phoenix platforms that can be operational in about one day.
The benefit is effort saved and time to solution, Your development team can immediately focus on application development, thus saving the weeks to month of infrastrucure setup.
Common application infrastructure – ie Large flow state tables or encapsulation header remove and reapplied.
Phoenix Application Prototypes
Pheonix Application Prototypes address a specific Use Case. They are built on top of a Pheonix Framework. Together the framework and prototype provide an operational environment. This environment is used to validate that is requirements of the Use Case are met.
These prototypes can be “pre-package” solutions made available by BlueDot Insight, or custom prototypes developed by BlueDot Insight in a Phoenix POC engagement.
A Pheonix Application Prototype is an operational environment that implements Use Case requirements on top of one or more Phoenix Platforms. It consists of:
- A specific hardware infrastructure
- A specific revision controlled software BOM. This includes Intel IPU and Broadcom software plus Bluedot Insight P4 pipeline code and nodeJS controller
- Detailed definitions of key algorithms developed for the specific Use Case
- Design and implementation scripts for x86 base traffic generation
- Procedures and installation scripts
- User documentation including wiring diagrams, life-of-a-packet documentation, and how-to cookbooks
Phoenix POC (Proof of Concept) Consulting
Phoenix POC Consulting is conducted by BlueDot Insight with a proprietary collaborative and incremental methodology. From initial requirements, through multiple “micro drops” of prototype functionality, to the final release, we work together to discover the full requirements of the client’s Use Case and validate each phase of the prototype development.
A Phoenix POC includes:
- Initial Requirements definition
- Selection of Pheonix Platform
- Development of
- P4 pipelines for Intel IPU
- ARM core code (if any)
- Configuration of Sonic/Broadcom environment
- Classify packets for the type of processing they require
- Partition traffic to the IPU cluster
- Crafting of nodeJS controller
- Design and implementation scripts for x86 base traffic generation
- Procedures and installation scripts
- User documentation including wiring diagrams, life-of-a-packet documentation, and how-to cookbooks
