OOBM nestedcloudstack

[returntrip]

What is this for? Can I use it for nested Cloudstack env that I use for testing?

[DaanHoogland]

yes you should (your milage may vary)

[returntrip]

Would you know what to use for host, password and credentials?

[DaanHoogland]

not sure, but I think the root credentials for the VM. (you are talking about the NestedCloudStackOutOfBandManagementDriver right?)

[returntrip]

Yep trying that. I wonder if the port would be 22 then.... Will give it a try

[returntrip]

No luck. If anyone knows what details I should use for host/port/user/password that woukd help me a lot. Thanks.

[DaanHoogland]

Have a look at test/integration/smoke/test_outofbandmanagement.py and test/integration/smoke/test_outofbandmanagement_nestedplugin.py. These are the related test suites that use the OOB functionality.

[TadiosAbebe]

@returntrip , I managed to test this today based on @DaanHoogland recommendation and here is how you make nested cloudstack plugin to work

• First generate API/Secret Keys of the cloudstack that is hosting your nested cloudstack deployment
• Then use the following information to confiugre out-of-band management for the compute hosts inside your nested cloudstack environment
  • Address: http://x.x.x.x:8080/client/api (where x.x.x.x is the ip of the management server of the cloudstack that is hosting your nested cloudstack)
  • Port: c4783e16-7898-475e-a073-d8ff6257e5a6 (where c4783e16-7898-475e-a073-d8ff6257e5a6 is the uuid of the instances that is created on the cloudstack that is hosting your nested cloudstack)
  • Username: api key you previously generated
  • Password: the api secret you previously generated
  • Driver: nestedcloudstack
• Then you can test if it is working by issuing out-of-band management power action
• If you are having trouble you can tail the management server log and you will find some ERROR there if it is not working, for example when i first tried to use username and password instead of api credential i got the following error logged

2025-11-04 06:40:01,846 ERROR [o.a.c.o.d.n.NestedCloudStackOutOfBandManagementDriver] (pool-2-thread-38:[ctx-58d91513]) (logid:) Nested CloudStack oobm plugin failed due to API error: Status code [401], with response [{"listvirtualmachinesresponse":{"uuidList":[],"errorcode":401,"errortext":"unable to verify user credentials and/or request signature"}}] for request [http://x.x.x.x:8080/client/api?apiKey=admin&command=listVirtualMachines&forced=true&id=c4783e16-7898-475e-a073-d8ff6257e5a6&response=json&signature=FNBGA8uZs2rb5zQdNehfSdgpUtY%3D]
        at br.com.autonomiccs.apacheCloudStack.client.ApacheCloudStackClient.executeRequestGetResponseAsString(ApacheCloudStackClient.java:186)
        at br.com.autonomiccs.apacheCloudStack.client.ApacheCloudStackClient.executeRequest(ApacheCloudStackClient.java:166)
        at org.apache.cloudstack.outofbandmanagement.driver.nestedcloudstack.NestedCloudStackOutOfBandManagementDriver.execute(NestedCloudStackOutOfBandManagementDriver.java:129)
        at org.apache.cloudstack.outofbandmanagement.driver.nestedcloudstack.NestedCloudStackOutOfBandManagementDriver.execute(NestedCloudStackOutOfBandManagementDriver.java:45)
        at org.apache.cloudstack.outofbandmanagement.OutOfBandManagementServiceImpl.executePowerOperation(OutOfBandManagementServiceImpl.java:422)
        at org.apache.cloudstack.outofbandmanagement.PowerOperationTask.run(PowerOperationTask.java:51)
        at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
        at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
        at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
        at java.base/java.lang.Thread.run(Thread.java:840)

[returntrip]

Thanks folks. This solution works nicely!

[weizhouapache]

very good @TadiosAbebe

just a comment: if you use ubuntu 24 or debian 12, some changes are needed, refer to
a839e25