Loading...

XML

Word

Printable

Type: Story
Resolution: Unresolved
Priority: Undefined
Fix Version/s: None
Affects Version/s: None
Component/s: None
Labels:
None

Story Points:
8
Epic Link:
Test Ceph Rados Gateway on the public network
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Ready:
False
Intelligence Requested:
Market:

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

The Problem

Five unified jobs are using the deployment network, not the storage network, to host Ceph

Each link above shows a line of job configuration to be removed. Epsilon no longer has this problem.

How did it happen?

Tempest pods cannot access the storage network by default so if Manila or Object tests were needed by the above jobs, we worked around it by deploying Ceph on a network they could access (the provisioning network `networks.ctlplane.network`).

What does the NFS network have to do with it?

If I move the Gamma and Delta tests from the provisioning network to another network, then I know which network I should move them to but what will configure that network?

Jobs which test manila are currently using the same provisioning network. They should instead be using the storage network for CephFS (OSPRH-7488) or a new NFS network for Ganesha (OSPRH-7417) – both as provider networks. The patches to configure this for both jobs are included in the patches to resolve this issue (OSPRH-6675).

What does an RGW network have to do with it?

The RGW network is not necessary. An early attempt to solve this problem involved adding a new RGW network but those changes were abandoned.

Phase 1

Three of the five jobs will be fixed directly with patches to the ci-framework jobs repository which remove the workaround and expose the storage network to tempest so it can access the services it needs.

Delta-IPv4 (tests GaneshaNFS + RGW)

Gamma (tests CephFS + RGW)

Day2 (tests only test_network_basic_ops)

https://gitlab.cee.redhat.com/ci-framework/ci-framework-jobs/-/merge_requests/1319 [merged]

Phase 2?

The following improvements could be added to the backlog or left incomplete.

Shiftstack-pipeline-base-jobs (tests GaneshaNFS + RGW)

A patch like architecture/pull/405 from Delta-IPv4 above could be created for dt/osasinfra
Because a similar scenario is tested by Delta-IPv4 but without Shift on Stack do we want to leave this incomplete?

Delta-ipv6 (tests GaneshaNFS + RGW)

A patch like architecture/pull/405 from Delta-IPv4 above could be created for dt/uni04delta-ipv6
Manila is being tested with IPv6 but it's not using a dedicated network. Do we want to leave this incomplete?
OSPRH-10419 tracks this