Skip to content

Conversation

@dupremathieu
Copy link
Member

The 1.5 release of the ABB SSC600 template adds support for the protection communication port. This is a PCI passthrough interface that allows the VM to communicate with the protection devices.

Update the template to include the protection communication port and update the example inventory file to include the new configuration.

@dupremathieu dupremathieu requested a review from eroussy April 11, 2025 08:30
@dupremathieu
Copy link
Member Author

dupremathieu commented Apr 11, 2025

TODO:

  • test the configuration with an SSC600 VM
  • update the documentation in the README and the wiki

@dupremathieu
Copy link
Member Author

dupremathieu commented Apr 11, 2025

It was not clear to me if the protection interface replaces the process bus interface, or if it is another interface.

The ABB SSC600 documentation: https://techdoc.relays.protection-control.abb/r/SSC600-and-SSC600-SW-Engineering-Manual/1.5/en-US/VM-configuration

@dupremathieu dupremathieu force-pushed the ssc600_1.5 branch 2 times, most recently from 4f052b1 to 048cb9e Compare April 30, 2025 09:27
@dupremathieu dupremathieu force-pushed the ssc600_1.5 branch 3 times, most recently from 3b68e57 to 44cdd20 Compare May 7, 2025 16:35
@dupremathieu dupremathieu marked this pull request as ready for review May 7, 2025 16:38
Copy link
Member

@eroussy eroussy left a comment

Choose a reason for hiding this comment

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

Can you upload the schema in svg ?
It will allow to modify it later if we need.

The rest seems good to me

@dupremathieu
Copy link
Member Author

Can you upload the schema in svg ? It will allow to modify it later if we need.

The rest seems good to me

The schema sources are exported as PNG metadata.
It was created using draw.io. You can open it in the same way you open .drawio files.

eroussy
eroussy previously approved these changes May 13, 2025
Copy link
Member

@eroussy eroussy left a comment

Choose a reason for hiding this comment

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

I validate, but please wait for ABB test before merging that.

@n-pochet
Copy link

@dupremathieu Please be aware that during our tests we've figured out that there's some discrepancy between what's in the inventory and in the template regarding the PCI passthrough interface.
See

{% if vm.protection_port is defined %}
vs
protection_ports: # Protection communication port

protection_port vs protection_ports

And there's another typo in

<address domain="{{ vm.protection_portci.domain }}" bus="{{ vm.protection_port.bus }}" slot="{{ vm.protection_port.slot }}" function="{{ vm.protection_port.function }}"/>

where it says protection_portci.

It should ideally be decided if the plural or singular form should be used and ensure that all used variables have the same name.

@eroussy eroussy force-pushed the ssc600_1.5 branch 2 times, most recently from 1f18688 to bd6fd0b Compare August 19, 2025 13:31
The 1.5 release of the ABB SSC600 template adds support for the
protection communication port. This is a PCI passthrough interface
that allows the VM to communicate with the protection devices.

Update the template to include the protection communication port
and update the example inventory file to include the new
configuration.

Also update the process_bus_interfaces to be pci_passthrough as
requested by ABB.

The 1.5.1 release of ABB SSC600 requires at least two management
interfaces to work properly.
Add a second management interface on br0.

Also remove the xml encoding to prepare switching to debian13.

Signed-off-by: Mathieu Dupré <mathieu.dupre@savoirfairelinux.com>
Signed-off-by: Erwann Roussy <erwann.roussy@savoirfairelinux.com>
upload_files: # This file is given with the ssc600 sw package
- src: '../files/qemu.hook'
dest: '/etc/libvirt/hooks/'
mode: "0744"
Copy link
Member Author

Choose a reason for hiding this comment

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

I am not sure if it is still needed. It's for MacVTap only.

Copy link
Member

Choose a reason for hiding this comment

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

good question, I will look into it with ABB R&D team.

Copy link

Choose a reason for hiding this comment

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

Yes, it's for MacVTap only, and if you don't use it, you don't need the hook.

Copy link
Member Author

Choose a reason for hiding this comment

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

Maybe we can describe the interface inside the VM:

  • "Rear"
  • "Process bus"
  • "Protection communication"

Copy link
Member Author

Choose a reason for hiding this comment

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

We no longer have MacVTap, right?

Copy link
Member

Choose a reason for hiding this comment

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

Indeed.
I need to clarify that.

@eroussy eroussy linked an issue Sep 16, 2025 that may be closed by this pull request
@dupremathieu dupremathieu marked this pull request as draft December 15, 2025 09:19
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.

ABB SSC600 SW test deployment

5 participants