Skip to content

Conversation

@phip1611
Copy link
Member

@phip1611 phip1611 commented Jan 7, 2026

  • basic plumbing for interfaces of network type bridge (what OpenStack uses)
  • basic plumbing for interfaces of network type network (libvirt managed networks)
  • add infrastructure for usable networking in hotplugged devices + test that
  • add documentation for our network overview

Hints for Reviewers

The table in the last commit (in the markdown document) will help you a lot reviewing this!

@phip1611 phip1611 self-assigned this Jan 7, 2026
@phip1611 phip1611 marked this pull request as draft January 7, 2026 16:31
@phip1611 phip1611 closed this Jan 8, 2026
@phip1611 phip1611 force-pushed the network-type-network branch from 9fc3c9a to 9bdfb26 Compare January 8, 2026 07:56
@phip1611 phip1611 reopened this Jan 8, 2026
@phip1611 phip1611 changed the title XXX add test network type network Add plumbing for interface types network and bridge + tests Jan 8, 2026
@phip1611 phip1611 marked this pull request as ready for review January 8, 2026 07:58
@phip1611 phip1611 force-pushed the network-type-network branch from 9bdfb26 to cce7fef Compare January 8, 2026 08:04
Not use anyway as we prefer static IPs in the guest for much
quicker boots.

Signed-off-by: Philipp Schuster <[email protected]>
On-behalf-of: SAP [email protected]
@phip1611 phip1611 force-pushed the network-type-network branch 2 times, most recently from 9af363c to 2d88976 Compare January 8, 2026 08:07
@phip1611 phip1611 force-pushed the network-type-network branch 2 times, most recently from 506239e to a928928 Compare January 8, 2026 08:10
This refactors the hotplug test in a way that it ssh's into the VM
via the hotplugged interface. As a prerequisite, we have to assign
the tap device that libvirt creates into an existing bridge with a
valid IP range. I decided to reuse bridge br0 for that.

To better identify test networks, I also streamlined the MAC
addresses. Now, they match the test IP net:

IP: 192.168.X.0/24 => MAC: ...::0X
    192.168.1.0/24 => MAC: ...::01
    192.168.2.0/24 => MAC: ...::02
    ...

A document summarizing all guest/test networks follows in a
subsequent commit.

Signed-off-by: Philipp Schuster <[email protected]>
On-behalf-of: SAP [email protected]
@phip1611 phip1611 force-pushed the network-type-network branch from a928928 to 86b5cd4 Compare January 8, 2026 09:06
@scholzp
Copy link
Contributor

scholzp commented Jan 8, 2026

Very very nit, feel free to ignore, but the message of commit "tests: hotplug interface connected to libvirt managed network" contains odd whitespace (double space).

From the commit's message:
Adding a network interface of [double space here] type 'network' that can be hotplugged.

This is relevant for interfaces that use the type 'network' in
their XML definition. Although not used by OpenStack (they use type
'bridge' which follows later in this PR), it is good to test this.

Co-authored-by: Pascal Scholz <[email protected]>
Signed-off-by: Philipp Schuster <[email protected]>
On-behalf-of: SAP [email protected]
@phip1611 phip1611 force-pushed the network-type-network branch from 86b5cd4 to 248db89 Compare January 8, 2026 09:18
Adding a network interface of type 'network' that can be hotplugged.
Also, using it in the hotplug test.

Signed-off-by: Philipp Schuster <[email protected]>
On-behalf-of: SAP [email protected]
Adding a network interface of type 'bridge' that can be hotplugged.
Also, using it in the hotplug test. This is the technology that
OpenStack uses for setting up networking.

Signed-off-by: Philipp Schuster <[email protected]>
On-behalf-of: SAP [email protected]
Signed-off-by: Philipp Schuster <[email protected]>
On-behalf-of: SAP [email protected]
Signed-off-by: Philipp Schuster <[email protected]>
On-behalf-of: SAP [email protected]
@phip1611 phip1611 force-pushed the network-type-network branch from 248db89 to ed8b899 Compare January 8, 2026 09:19
Copy link
Collaborator

@hertrste hertrste left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks very nice and concise now :)

Copy link
Contributor

@scholzp scholzp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nicely done! I especially like that you took the time to write proper documentation of the network setup! :)

@phip1611 phip1611 enabled auto-merge January 8, 2026 09:31
@phip1611 phip1611 disabled auto-merge January 8, 2026 09:34
@phip1611 phip1611 added this pull request to the merge queue Jan 8, 2026
Merged via the queue into cyberus-technology:main with commit ccbde8d Jan 8, 2026
3 checks passed
@phip1611 phip1611 deleted the network-type-network branch January 8, 2026 09:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants