CLOUDSTACK-8987 call s3xen/swiftxen plugins with their name - #970
CLOUDSTACK-8987 call s3xen/swiftxen plugins with their name#970remibergsma wants to merge 3 commits into
Conversation
|
Verified this is also broken in |
|
makes sense. just code reviewed. will review the breaking commit to see if I can spot other superfluent changes in there as well. |
|
Based on code review, LGTM 👍 I haven't spun up a cluster to run integration tests... |
|
@borisroman Thanks, will ask @wilderrodrigues to run some integration tests. |
|
@remibergsma @wilderrodrigues Thanks! |
|
@remibergsma @borisroman - I'm starting tests now. |
|
Code look good to me, no rocket science involved. I will test it with XenServer 6.5, but I might need help figuring out how to get it covered. Cheers, |
|
Since a8212d9 changed names from "xen" to "xenserver", shouldn't the change be to rename the files s3xen to s3xenserver and swiftxen to swiftxenserver in scripts/vm/hypervisor/xenserver/? |
|
Ping @Runseb. |
|
Good point, @koushik-das. @remibergsma: do you agree on that one as well? |
|
@koushik-das One of the goals of a8212d9 was to ensure that we have clarity in which hypervisor we support since Xen != XenServer. Reverting based on name IMO might be the simple solution, but could ultimately cause additional confusion as we don't currently have a pure Xen hypervisor implementation. @wilderrodrigues @remibergsma, I didn't have s3 or swift storage to test with at the time of my changes. Would not the better solution be to rename the plugin s3xenserver and swiftxenserver? |
|
I will test if renaming the plugin works (and make sure there are no links to its name). |
… the calls Renaming introduced in a8212d9 This PR is to address comments in PR apache#970
|
New PR #982 |
… the calls Renaming introduced in a8212d9 This PR is to address comments in PR apache#970
CLOUDSTACK-9014 Rename xapi plugins for s3 and swift to make them work after renaming the callsMake renaming introduced in a8212d9 work for S3 and Swift xapi plugins. This PR is to address comments in PR #970 * pr/982: Rename xapi plugins for s3 and swift to make them work after renaming the calls Signed-off-by: Remi Bergsma <[email protected]>
It's called
s3xen, nots3xenserver. While investigating, I found the same issue forswiftxen.Regresion from a8212d9 where things were massively renamed, without proper verification.
Error seen:
Here we see the correct name:
And:
These plugins are pushed to the hypervisor.
Finally, s3xen logrotate wasn't setup properly as the logfile was missing
.log.Build succeeds:
After this, S3 works as expected on XenServer. Couldn't test swift but it's the same issue. Pinging @pdion891 to have look at swift.