CORD : SEBA 1.0 Release

Verify End-end ping with

ONU in Correct Location

Validates E2E Ping Connectivity and object states for the given scenario:

• Configure whitelist with correct ONU location
• Validate successful authentication/DHCP/E2E ping

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha16_cord-6.1_test/

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha-master_master_test/

Test by removing ONU from Whitelist,

and re-add ONU to Whitelist for a

successful ping

Validates E2E Ping Connectivity and object states for the given scenario:

• Configure whitelist with correct ONU location
• Validate successful authentication/DHCP/E2E ping
• Remove ONU from whitelist
• Validate failed authentication/DHCP/E2E ping
• Add ONU to whitelist
• Validate successful authentication/DHCP/E2E ping

Yes

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha16_cord-6.1_test/

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha-master_master_test/

Test with ONU in Wrong Location

and re-add ONU in Correct Location

for a successful ping

Validates E2E Ping Connectivity and object states for the given scenario:

• Configure whitelist with correct ONU location
• Validate successful authentication/DHCP/E2E ping
• Update whitelist with wrong ONU location
• Validate failed authentication/DHCP/E2E ping
• Update whitelist with correct ONU location
• Validate successful authentication/DHCP/E2E ping

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha16_cord-6.1_test/

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha-master_master_test/

Test by Removing Subscriber and

re-creating the Subscriber for a

successful ping

Validates E2E Ping Connectivity and object states for the given scenario:

• Configure whitelist with correct ONU location
• Validate successful authentication/DHCP/E2E ping
• Remove subscriber model
• Validate successful authentication (expected with the ONF pod setup) but failed DHCP/E2E ping
• Recreate subscriber model
• Validate successful authentication/DHCP/E2E ping

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha16_cord-6.1_test/

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha-master_master_test/

Validates E2E Ping Connectivity and object states for the given scenario:

• Configure whitelist with correct ONU location and skip provisioning subscriber
• Validate successful authentication (expected with the ONF pod setup) but failed DHCP/E2E ping
• Provision subscriber
• Validate successful authentication/DHCP/E2E ping

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha16_cord-6.1_test/

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha-master_master_test/

Validates failed authentication/DHCP/E2E Ping with the following scenario:

• Configure whitelist with correct ONU location and skip RG authentication
• Validate failed DHCP/E2E Ping

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha16_cord-6.1_test/

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha-master_master_test/

Validates failed E2E Ping Connectivity and object states for the given scenario:

• Skip whitelist configuration for ONU
• Validate authentication fails
• Validate that DHCP/E2E ping fail

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha16_cord-6.1_test/

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha-master_master_test/

Test with ONU not in Whitelist and by skipping Subscriber

Provisioning

Validates E2E Ping Connectivity and object states for the given scenario:

• Skip whitelist configuration for ONU and subscriber provisioning
• Validate successful authentication but DHCP/E2E pings fails
• Configure whitelist with correct ONU location
• Validate successful authentication (expected with the ONF pod setup) but failed DHCP/E2E ping
• Provision subscriber
• Validate successful authentication/DHCP/E2E ping

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha16_cord-6.1_test/

https://jenkins.opencord.org/view/ATT-Workflow/job/build_att-workflow_flex-ocp-cord-voltha-master_master_test/

Validates E2E Ping Connectivity and object states for the given scenario:

• Configure whitelist with wrong ONU location
• Validate that authentication/DHCP/E2E ping fail

test9: ATT_Test001

Test with ONU in Wrong Location and Skip Subscriber Provisioning,

Then fix ONU in Correct Location and Provision Subscriber

Validates E2E Ping Connectivity and object states for the given scenario:

• Configure whitelist with wrong ONU location and skip subscriber provisioning
• Validate failed authentication/DHCP/E2E ping
• Configure whitelist with correct ONU location
• Validate successful authentication (expected with the ONF pod setup) but failed DHCP/E2E ping
• Provision subscriber
• Validate successful authentication/DHCP/E2E ping

• Reboot RG

• Reboot OLT

• Reboot Fabric Switch (Leaf attached to OLT)

• Possibly after testing a successful build -> upgrade helm charts and re-test

• Perform tests after any upgrade of helm charts

• Matrix of upgradable versions is required

• Validate migrations are successful and tests succeed after migration

• Use BBSim to scale SEBA with 16 ONUs (one OLT) and test scale and performance on the POD

• Implemented in a SIAB virtual pod environment

• Test has ability to dynamically scale