Open Horizon project QA Working Group Meeting August

  • Slides: 9
Download presentation
Open Horizon project QA Working Group Meeting August 12, 2020

Open Horizon project QA Working Group Meeting August 12, 2020

Meeting Details August 12, 2020 (@ 11: 30 am ET/8: 30 am PT) Meeting

Meeting Details August 12, 2020 (@ 11: 30 am ET/8: 30 am PT) Meeting Info: https: //zoom. us/j/92413737960 Meeting ID: 924 1373 7960 One tap mobile +12532158782, , 92413737960# US (Tacoma) +13462487799, , 92413737960# US (Houston) Dial by your location +1 253 215 8782 US (Tacoma) +1 346 248 7799 US (Houston) +1 669 900 6833 US (San Jose) +1 301 715 8592 US (Germantown) +1 312 626 6799 US (Chicago) +1 929 205 6099 US (New York) 877 853 5247 US Toll-free 888 788 0099 US Toll-free Meeting ID: 924 1373 7960 Find your local number: https: //zoom. us/u/aego. N 37 Nsj

LF Antitrust Policy Notice LF Edge meetings involve participation by industry competitors, and it

LF Antitrust Policy Notice LF Edge meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at LF Edge meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http: //www. linuxfoundation. org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

Topics 1. 2. 3. 4. 5. Welcome and Introductions A. B. C. Meeting every

Topics 1. 2. 3. 4. 5. Welcome and Introductions A. B. C. Meeting every other week Mission Statement Participation i. ii. Roles and responsibilities How to get started Tools and Processes A. B. Project code repository › QA has no single repository and instead has tools, commits and code in several existing repos Zen. Hub for project board and swim lanes Technical Architecture Overview Recommended Review Material Next Meeting

Technical Architecture Overview Postgresql Mongo Postgresql Exchange CSS Agbot API Edge Management Hub Device

Technical Architecture Overview Postgresql Mongo Postgresql Exchange CSS Agbot API Edge Management Hub Device Registrations SDO API message security (*) • Edge components are Blue/Light Blue • Edge Management Hub Components are • Docker containers • Deployed in a Kubernetes cluster • Each has multiple instances • Cross Component communication is through APIs • All remote communication (arrows) is via HTTPS • All remote communication is authenticated via basic auth • Remote communication is not bidirectional • (*) Message security is additional message protection on top of HTTPS • Combination of symmetric and RSA key pair encryption • Agents and Agbots exchange messages via the Exchange API, never directly. • There are thousands of Edge Nodes message security keys ESS • • • Agent Edge Node root protected file system local object database message security keys There is NO remote API for this component

Recommended Review Material & Documentation 1. 2. 3. 4. Working Groups Architecture Overview Detail

Recommended Review Material & Documentation 1. 2. 3. 4. Working Groups Architecture Overview Detail (highly recommended for more detail on agent behavior) › › Agent Management-Hub Systemic Test Tools › E 2 E-Dev (End to End Testing) – Main Functional Systemic Test › › › Stands up containers for the exchange, agbot and agent components to test them end to end. Most of the pre-test setup script including test build runs in the Makefile (but not all) The Gov directory under anax/test contains most of the test scripts & test utility scripts gov-combined is the main test thread in which all other test script are executed from & contains more pre-test setup Notable Utility scripts: verify_agreements. sh (test validation used in several test scripts) Functional Test Tools & Unit Test › › › Exchange (Part of Mgmt Hub) – Scala Test (Great API test coverage at a component level with a mock API) Main Scala Test Suites Agent – Anax Repo Link – Unit tests built in go throughout the code

Next Meeting

Next Meeting

Next Meeting › Next Meeting: Wednesday, September 9 @ 8: 30 am PT/11: 30

Next Meeting › Next Meeting: Wednesday, September 9 @ 8: 30 am PT/11: 30 am ET › Discussion of Test Frameworks in more detail

Thank You

Thank You