Open tpodowd opened 1 month ago
@blueorangutan package
@DaanHoogland 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.
Attention: Patch coverage is 74.67700%
with 196 lines
in your changes missing coverage. Please review.
Project coverage is 15.88%. Comparing base (
2fa1761
) to head (f239762
). Report is 28 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Packaging result [SF]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 11244
Thanks for the PR @tpodowd since we don't have the cloudian system to test against, we'll help with regression testing.
@blueorangutan test
@rohityadavcloud a [SL] Trillian-Jenkins test job (ol8 mgmt + kvm-ol8) has been kicked to run smoke tests
Hi @rohityadavcloud - I updated the PR to fix the README.md lint issue and also added a bit more unit test coverage in the main driver code.
You mentioned the following:
since we don't have the cloudian system to test against, we'll help with regression testing.
Thanks, let me know what information you need and I'll do my best to get back to you.
[SF] Trillian test result (tid-11583) Environment: kvm-ol8 (x2), Advanced Networking with Mgmt server ol8 Total time taken: 56540 seconds Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr9748-t11583-kvm-ol8.zip Smoke tests completed. 141 look OK, 0 have errors, 0 did not run Only failed and skipped tests results shown below:
Test | Result | Time (s) | Test File |
---|
Hi @DaanHoogland - I think I have got the pre-commit stuff nailed now. I ran pre-commit locally and it fixed the end of files for me. Then I reviewed that and pushed commit 40c0366
Sorry. I was reviewing the beautiful code coverage report and reviewing code I had not tested when I noticed a bad typo that means CloudianClient
won't timeout. I have a fix locally and have added unit tests. I am doing a full build and a bit more testing and then I'll push another commit.
Ok. Hopefully that is it. I have pre-commit hooked in now also so I know that is clean. Code coverage should be a little better again also.
@blueorangutan package
@DaanHoogland 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]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 11283
Hi @DaanHoogland / @rohityadavcloud - There seems to be an error in one of the checks. I'm not sure that it is related to my changes though. Let me know if I need to do anything about it. Thanks!
Hi @DaanHoogland / @rohityadavcloud - There seems to be an error in one of the checks. I'm not sure that it is related to my changes though. Let me know if I need to do anything about it. Thanks!
rerunning, let's see. It doesn't seem related to me either.
I realised that I should not change the key names that the Object Store Details use as they may be read/updated outside of the plugin. Thanks!
@blueorangutan package
@DaanHoogland 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]: ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 11332
Hi @JoaoJandre - I have pushed another commit to address your review comments. Thanks for your time and let me know if you have any other concerns or questions.
Hi @JoaoJandre - I have pushed another commit to address your review comments. Thanks for your time and let me know if you have any other concerns or questions.
@tpodowd I did my best with no knowledge of Cloudian :smile: . In any case, overall it looks good to me. There is only one thing (https://github.com/apache/cloudstack/pull/9748#discussion_r1806353907) left that I think should be addressed.
@tpodowd I did my best with no knowledge of Cloudian 😄 . In any case, overall it looks good to me. There is only one thing (#9748 (comment)) left that I think should be addressed.
Hi @JoaoJandre - No worries. Thank you so much again for your time on this. I have addressed your last comment and have pushed an update.
Hi @tpodowd, I understand Cloudian doesn't support per bucket Quota. Does it support per user quota? Is there a way to configure it from within CloudStack?
cc @rohityadavcloud @sureshanaparti
Hi @abh1sar - Thanks for your comment/question.
I understand Cloudian doesn't support per bucket Quota.
Yes, Cloudian HyperStore does not currently support a bucket storage quota.
Does it support per user quota?
Yes, Cloudian HyperStore does support per user quota. We have a warning level and a hard limit for storage bytes and we also have some other related settings.
Is there a way to configure it from within CloudStack?
Unfortunately not. There are some issues here:
Currently, the administrator would have to login to the HyperStore system and either:
Thanks @tpodowd for your response. If we had to implement the functionality to set Account level Quota in cloudstack, how do you think that could be done? Does the HyperStore plugin has API to do something like that? I am asking because I am working on a PR which adds resource limits to Object Storage space usage.
Hi @abh1sar. The current plugin does not have any API support itself for setting Account level QoS (as it only implements the provided plugin APIs). The HyperStore Admin API itself does support setting QoS for a user though so that could be made available to CloudStack if it was implemented in CloudianClient (which is easy enough). If I know more about what you are doing, I guess I can also chip in.
FYI. I have another PR pending this one also which adds the ability to edit the Object Store details. https://github.com/tpodowd/cloudstack/tree/edit_object_storage
Description
This PR Adds A New Object Storage Provider Plugin for Cloudian HyperStore
More Details:
UI Changes - Add Object Storage for Cloudian HyperStore:
Other Bug fixes and improvements as part of this fix I kept in separate commits.
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?