Congratulations on your first Pull Request and welcome to the Apache CloudStack community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/cloudstack/blob/main/CONTRIBUTING.md)
Here are some useful points:

• In case of a new feature add useful documentation (raise doc PR at https://github.com/apache/cloudstack-documentation)
• Be patient and persistent. It might take some time to get a review or get the final approval from the committers.
• Pay attention to the quality of your code, ensure tests are passing and your PR doesn't have conflicts.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Issues, Mailing list and Slack.
• Be sure to read the CloudStack Coding Conventions.
  Apache CloudStack is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: dev@cloudstack.apache.org (https://cloudstack.apache.org/mailing-lists.html)
  Slack: https://apachecloudstack.slack.com/

@blueorangutan package

@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 3.66%. Comparing base (30e6c22) to head (10b2a77).
⚠️ Report is 614 commits behind head on main.

❗ There is a different number of reports uploaded between BASE (30e6c22) and HEAD (10b2a77). Click for more details.

HEAD has 1 upload less than BASE

Flag	BASE (30e6c22)	HEAD (10b2a77)
unittests	1	0

@@             Coverage Diff              @@
##               main   #8251       +/-   ##
============================================
- Coverage     17.92%   3.66%   -14.26%     
============================================
  Files          5939     454     -5485     
  Lines        533181   38540   -494641     
  Branches      65237    7126    -58111     
============================================
- Hits          95585    1414    -94171     
+ Misses       426856   36938   -389918     
+ Partials      10740     188    -10552     

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 7806

@PeterBackroll , nice to see this coming in. Will you add a documentation PR as well? I think you'll have a lot of reviews ;)

@blueorangutan test

@DaanHoogland a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

[SF] Trillian test result (tid-8383)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 45945 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr8251-t8383-kvm-centos7.zip
Smoke tests completed. 117 look OK, 1 have errors, 0 did not run
Only failed and skipped tests results shown below:

Hi @DaanHoogland Yes I will add a documentation PR as soon as possible :)

@blueorangutan package

@rohityadavcloud a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 7834

@PeterBackroll can you please have a look at the GH actions failures

@PeterBackroll do we have any docs on how to configure the plugin, what kind of storage is supported, any limitations, etc?
Thx!

@PeterBackroll Since this is for the 4.22.1 release, could you retarget the PR to the 4.22 branch?

@PeterBackroll , is work on this still progressing?

Hello there, we are working on experimental changes on other branches and then we merge on the PR’s branch.

While I was testing the plugin, I faced an error. Before starting to dig into the issue, I thought that it could be better to be up-to-date with the main branch.

So I updated the main branch and merged it into my working branch but it was no longer compiling. Then I tried to compile the main branch with mvn install -f pom.xml -DskipTests -Dcheckstyle.skip=true but it failed. Each time I launched the command the compilation went further and previously failing-to-compile projects were starting to compile.

To understand better what was happening, I had a look at these pages :
https://cloudstack.apache.org/developers/
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment+on+Linux

So I tried mvn clean and then mvn clean install -P developer,systemvm but it kept failing on cloud-framework-managed-context.

I ended up with two questions :

• should the main branch compile ?
• is there a tutorial on how to update from the main branch on a daily basis ?

@m-dhellin , we keep phony PRs like #12198 to regularly test release branches (main, 4.22, 4.20) . internally as a company we have a daily build as well, but that is not shared. Last night’s passed on all branches.

Did you check java versions?

Thank you @DaanHoogland, I reviewed and updated my development environment (java + maven) and it’s compiling again.

Hello, I’m no longer able to test the plugin because of this error :

org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.springframework.beans.factory.config.PropertyPlaceholderConfigurer#0' defined in URL [jar:file:/opt/cloudstack/cli ent/target/cloud-client-ui-4.23.0.0-SNAPSHOT.jar!/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml]: Cannot resolve reference to bean 'DefaultConfigResources' while setting bean proper ty 'locations'; nested exception is org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean named 'DefaultConfigResources' available

I run mvn clean install -P systemvm,developer -DskipTests -Dcheckstyle.skip=true on the main branch but the error is still there. Any thoughts ?

java --version

openjdk 17.0.15 2025-04-15
OpenJDK Runtime Environment (build 17.0.15+6-Ubuntu-0ubuntu120.04)
OpenJDK 64-Bit Server VM (build 17.0.15+6-Ubuntu-0ubuntu120.04, mixed mode, sharing

mvn --version

Apache Maven 3.9.12 (848fbb4bf2d427b72bdb2471c22fced7ebd9a7a1)
Maven home: /root/apache-maven-3.9.12
Java version: 17.0.15, vendor: Ubuntu, runtime: /usr/lib/jvm/java-17-openjdk-amd64
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "5.4.0-131-generic", arch: "amd64", family: "unix

git log -n 1

commit 30e6c224bdd2e33f35349e808ec75428853f2aa0 (HEAD -> main, upstream/main, origin/main, origin/HEAD)
Merge: c0db75b9fa 5caf6cd043
Author: Suresh Kumar Anaparti <sureshkumar.anaparti@gmail.com>
Date:   Thu Feb 19 13:20:04 2026 +0530

    Merge branch '4.22'

@m-dhellin , this sounds like some bean cannot load (maybe because the DB-scheme doesn’t match its current definition??)

Do or did your beans use ‘locations’ and did that get changed or did an update of the upstream repository contain such a change?

Thank you @DaanHoogland for your quick reply, I reset the DB with mvn -P developer -pl developer -Ddeploydb but it’s not working yet. I will try to understand why the bean is not found while I can find its definition.

I’ve been able to fix the issue by adding a dependency link with a temporary absolute path and recompiling :

core/src/main/resources/META-INF/cloudstack/bootstrap/spring-bootstrap-context-inheritable.xml

Added this line :

<import resource="file:/opt/cloudstack/framework/spring/module/src/main/resources/org/apache/cloudstack/spring/module/model/impl/defaults-context.xml"/>

The resulting XML :

<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:context="http://www.springframework.org/schema/context"
       xmlns:aop="http://www.springframework.org/schema/aop"
       xsi:schemaLocation="http://www.springframework.org/schema/beans
                      http://www.springframework.org/schema/beans/spring-beans.xsd
                      http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop.xsd
                      http://www.springframework.org/schema/context
                      http://www.springframework.org/schema/context/spring-context.xsd"
                      >

    <context:annotation-config />

    <import resource="file:/opt/cloudstack/framework/spring/module/src/main/resources/org/apache/cloudstack/spring/module/model/impl/defaults-context.xml"/>

    <bean class="org.springframework.beans.factory.config.PropertyPlaceholderConfigurer">
        <property name="order" value="100" />
        <property name="ignoreResourceNotFound" value="true" />
        <property name="ignoreUnresolvablePlaceholders" value="true" />
        <property name="locations" ref="DefaultConfigResources" />
    </bean>

</beans>

But know that’s the bean « registryRegistry » which is not found. I may try this for every « ref » attribute I find in beans definitions if I don’t find a better solution.

@m-dhellin , I never heard of this being needed before. If it works for you it work, but I am really curious about the root cause and whether this is specific to your component/project/plugin/change???

Hi @PeterBackroll @m-dhellin is this PR ready for review, or are you still working on it?

Hi there, we are still working on the plugin and Backroll. The connection between the plugin and Backroll needs to be stabilized and the authentication model was changed. I will try to test the fix soon.