OPNFV overview and Edge Cloud

Transcription

1 Akraino Edge Stack Meetup, May 16-19, Intel Hillsboro OPNFV overview and Edge Cloud Wenjing Huawei, LFN, OPNFV 1

2 OPNFV does Integration & Testing For networking and NFV, and, edge. 2

3 A typical OPNFV stack view Many configurations possible, each is defined as a Scenario. Each physical POD has a descriptor (PDF) containing all info an installer needs. Current PODs are mainly NFV focused. Edge is gaining traction. 3

4 OPNFV Scenario examples Openstack Opendailight SDN controller Data path: ovsdpdk HA config Many variations are available with good components in each layer in the stack. How to focus on testing (>50). How to help choose. Cost multiplies. Kubernetes Container networking default Non HA config 4

5 OPNFV s integration challenges OPNFV is an integration project with MANY upstream projects and MANY possible combinations of stacks ( Scenarios ) CI/CD is what connects MANY moving parts together to serve MANY users And run fast (think Mad Max) Different users of release artifacts have different needs, e.g. A source code developer often commiting in an upstream project An end user wanting to try out a use case A test case developer in OPNFV A vendor developer testing with a reference implementation for interoperability or compliance Installers or downstreams composing one or more flavors of the stack A user or testor interested in long duration evaluations A user or testor interested in testing of services/applications and continuous deployments There may be similar challenges for Akraino 5

6 The initial CI/CD approach (from A to F) Good: Advanced and comprehensive. Shortcomings: 1. But upstream is not current which leads to slow progress 2. And combinatorial growth of Scenarios (Blue Prints) 3. And lack application continuous deployments 1. Pulls the most recent major release 2. Patches sent to Gerrit which runs automated verification tests that produces feedback results for Gerrit review and merge decision 3. Various hardware platforms (by Pharos project) are used to run automated deployments (by Installers) and smoke tests daily for all scenarios (combinatorial configurations), and increasingly more complex tests for selected scenarios. 6

7 What slows us down? As we can see, this is a common problem in complex open source projects. There is a shared interest to have a cross project CI/CD for a common target market. 7

8 XCI - cross project CI In Gambia release (starting May 2018), some OPNFV projects will transition to XCI process. Openstack, OpenDaylight, FD.IO are working on or interested in integrating into this process. 8

9 Manage the combinatorial growth A proposal is being discussed to use a test-based promotion mechanism to manage this complexity (Scenario consolidation): developer vs mature Daily/weekly scenario tests for promotion PODs (PDF) All scenarios 9

10 Intelligent, Cloud Native Continuous Deployment Fast-paced user driven/data driven CI/CD is a core competency for cloud DevOps. OPNFV Clover Project (wiki: is adopting Spinnaker for CD. Supports a modern way of managing application lifecycle, cloud agnosticity etc. Supports a cloud native service mesh architecture. Artifact repo Commit Build Test Bake Deploy A/B Test, Green/Blue, Canary... Rollback cloud1 cloud2 Edge cloud1 Edge cloud2 10

11 Edge cloud project in OPNFV A new Edge Cloud has just been launched with strong interests and participation from the OPNFV community. First release - Gambia (Oct 2018). *Source: project creation info slides. Disclaimer: i m not a project committer. 11

12 *Source: project creation info slides.

13 Lessons learned DevOps and CI/CD is a core value in its own right Different constituents of a project have different needs Manage the combinatorial complexity in a principled way early on Remove the inter-project roadblocks, and leverage CI/CD without sophisticated testing isn t as useful For references: XCI: Clover: Infrastructure WG: Edge cloud: 13

14 Thank you 14