chore(ansible): added the spconv installation to ansible

[knzo25]

Description

As discussed in

• feat(autoware.repos): added ros2_spconv #5658

Instead of a ros2 package, spconv could be installed as a deb package.
This PR adds its installation via ansible

How was this PR tested?

Run the setup script in my local machine

Notes for reviewers

None.

Effects on system behavior

None.

[github-actions]

Thank you for contributing to the Autoware project!

🚧 If your pull request is in progress, switch it to draft mode.

Please ensure:

• You've checked our contribution guidelines.
• Your PR follows our pull request guidelines.
• All required CI checks pass before marking the PR ready for review.

[xmfcx]

Thanks! Could you fix https://github.com/autowarefoundation/autoware/actions/runs/13363617410/job/37317278911?pr=5794 errors?

Also if it's ok with you we can move this to AWF, do you need any help on that?

[xmfcx]

Could you also add a playbook that only installs this role? For easy manual installation of only this role.

Similar to: https://github.com/autowarefoundation/autoware/blob/ef1a495aa6a8bdf298ae5f22f6998fd6dd98490b/ansible/playbooks/download_artifacts.yaml

[amadeuszsz]

I think arm64 workflow will fail after merge. We can release binaries for arm64 and get current system arch in ansible task file directly.

[knzo25]

@amadeuszsz
Created the assets in https://github.com/knzo25/spconv_cpp/releases

[knzo25]

@xmfcx
Added in cb08f0d

Annoyingly, the health-check fails for unrelated reasons.

@amadeuszsz
Regarding the arm release, I will need to try on an ECU...
Using my machine + docker + qemu results in segfults for nvcc 😢

[xmfcx]

Annoyingly, the health-check fails for unrelated reasons.

This one is caused by:

• Autoware stable compilation fails on main branch #5792
  • chore(motion_velocity_planner_universe): fix build depends (#10122) autoware.universe#10139
  • The PR is ready but it required this chore(motion_velocity_planner_universe): fix build depends (#10122) autoware.universe#10139 (comment) CI update where the CI for universe both supports pushing to main and humble branches. I'll work on it now.

As for ARM support, I personally didn't build the ARM image on my machine before, please consult @youtalk @amadeuszsz @oguzkaganozt on this one 🙇‍♂️ And if you can manage, adding these detailed steps to documentation would be appreciated 😶‍🌫️

[knzo25]

It seems this is expected
https://forums.developer.nvidia.com/t/building-cuda-files-in-a-jetson-container-using-qemu/110963

[xmfcx]

Does TIER IV require this package to work in ARM/Jetson devices?

If not maybe we can also make an exception and add it anyways and somehow disable it for ARM builds.

It depends on how much additional work making it work for ARM requires though.

@mitsudome-r @youtalk could you comment as well?

[knzo25]

@xmfcx
In the end I managed to build it on the arm image, my problems were wither from my machine or qemu+nvidia themselves.
Tested ansible-playbook autoware.dev_env.install_spconv.yaml -e cumm_version=0.5.3 -e spconv_version=2.3.8 --ask-become-pass in both amd64 (native) and arm64 (docker) environments.

Once the PR is approved, but before merging, I will transfer the repo to the AWF (have done it before) and update the links. At that point, please add me as an admin so I can fix any problems down the line

[xmfcx]

@knzo25 now created:

• chore: bump version to 0.41.2 autoware.universe#10161

Once that is merged, we'll bump the reference to this Universe repo from autoware.repos and then it should pass the health check.

Finally waiting for:

• feat(autoware.repos): patch update autowarefoundation/autoware.universe to 0.41.2 #5806