Merge development into master branch for publishing Capri RC-01 #806
Conversation
Development
Development
…id with "--" and we store with "-"
Signed-off-by: leonwanghui <[email protected]>
Shrink size of hotpot binary files
Add access API for fileshare
POST API to collect metrics and send to registered adapters
Fixed printing bug, make the summary info printing more limpid
Signed-off-by: leonwanghui <[email protected]>
Uniform naming access protocol
* load configuration URLs for Grafana and Alert manager * regenerate mocks * updated response JSON after discussing with Anvith
Add opensds controller api spec validation
File share profile test cases
…and create/delete filesharesnapshots
Add fileshare controller unit test cases for create/delete fileshare and create/delete filesharesnapshots
* file share and acl cli * Modify the Metadata display format * Modify the keys to be displayed by cli * Modify the code based on the review
* add metrics driver for huawei osceanStor * Fix commented issue, and optimize some code
* Adding profile to CreateFileShareAcl and snapshot issue * Dock and controller code for deleteaccess api
Signed-off-by: leonwanghui <[email protected]>
Signed-off-by: leonwanghui <[email protected]>
Add keystone to fileshare
Move exporters under contrib folder
Patch 799 - Create file share fails because of no availability pool
NFS Driver FileshareAcl AccessTo is limited to one user
Codecov Report
@@ Coverage Diff @@
## master #806 +/- ##
=========================================
Coverage ? 31.44%
=========================================
Files ? 82
Lines ? 14928
Branches ? 0
=========================================
Hits ? 4694
Misses ? 9544
Partials ? 690
Continue to review full report at Codecov.
|
add protoc version precheck
|
@leonwanghui @xing-yang @wisererik
|
|
I actually prefer to get rid of development branch. All changes should be merged to Master directly. Then cut a stable branch from master at release time. After that, we need to cherry-pick each change to stable branch. Even for each regular PR merge (non release related), we should ask PR author to squash all those merge commits to make commits clean. Let's start this after Capri release. |
|
I agree with @skdwriting and @xing-yang, the initial thought why we split |
What this PR does / why we need it:
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Release note: