-
Notifications
You must be signed in to change notification settings - Fork 241
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ft: ZENKO-319 adds sproxyd location type management #1242
ft: ZENKO-319 adds sproxyd location type management #1242
Conversation
83986f9
to
773ae09
Compare
PR has been updated. Reviewers, please be cautious. |
lib/management/configuration.js
Outdated
@@ -171,6 +171,20 @@ function patchConfiguration(instanceId, newConf, log, cb) { | |||
}; | |||
} | |||
break; | |||
case 'location-scality-sproxyd-v1': | |||
location.type = 'scality'; | |||
if (l.details && l.details.bootstrap && l.detaisl.path) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
typo, should be l.details.path
773ae09
to
c88c69b
Compare
PR has been updated. Reviewers, please be cautious. |
lib/management/configuration.js
Outdated
locations.details = { | ||
connector: { | ||
sproxyd: { | ||
chordCos: l.details.chordCos || null, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We may want to add ARC support here as well, or not (@rachedbenmustapha ?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jonathan-gramain you're the sproxyd guru so correct me if I'm wrong :) We rely on already-deployed sproxyd and I believe ARC settings will be bound to the proxyPath
we are clients of.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, since we're using the proxyPath
to an existing sproxyd that's what matters. But then is the chord COS used at all, aren't we passing the object bucket/key in the path directly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jonathan-gramain chord cos is passed to sproxydclient
c88c69b
to
85d3d40
Compare
Do it again human slave!:point_right: :runner: (Oh and the pull request has been updated, by the way.)
PR has been updated. Reviewers, please be cautious. |
85d3d40
to
b3d72a4
Compare
PR has been updated. Reviewers, please be cautious. |
b3d72a4
to
bc62d99
Compare
PR has been updated. Reviewers, please be cautious. |
|
bc62d99
to
d0d6acf
Compare
PR has been updated. Reviewers, please be cautious. |
d0d6acf
to
147f7dd
Compare
PR has been updated. Reviewers, please be cautious. |
@alexanderchan-scality Can you make this BertE compatible? |
147f7dd
to
323a69c
Compare
Do it again human slave!:point_right: :runner: (Oh and the pull request has been updated, by the way.)
PR has been updated. Reviewers, please be cautious. |
No description provided.