-
Notifications
You must be signed in to change notification settings - Fork 301
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
HPCC-25955 implemented static pvs #17607
Conversation
Signed-off-by: Gavin Halliday <[email protected]>
Signed-off-by: Gavin Halliday <[email protected]> # Conflicts: # helm/hpcc/Chart.yaml # helm/hpcc/templates/_helpers.tpl # helm/hpcc/templates/dafilesrv.yaml # helm/hpcc/templates/dali.yaml # helm/hpcc/templates/dfuserver.yaml # helm/hpcc/templates/eclagent.yaml # helm/hpcc/templates/eclccserver.yaml # helm/hpcc/templates/eclscheduler.yaml # helm/hpcc/templates/esp.yaml # helm/hpcc/templates/localroxie.yaml # helm/hpcc/templates/roxie.yaml # helm/hpcc/templates/sasha.yaml # helm/hpcc/templates/thor.yaml # version.cmake
Signed-off-by: Jake Smith <[email protected]>
Signed-off-by: Gavin Halliday <[email protected]>
Signed-off-by: Gavin Halliday <[email protected]>
Signed-off-by: Gordon Smith <[email protected]>
…_DOCS HPCC-29828 Dev docs failing to build/publish Reviewed-by: Gavin Halliday <[email protected]> Merged-by: Gavin Halliday <[email protected]>
Signed-off-by: Gordon Smith <[email protected]>
Signed-off-by: Gordon Smith <[email protected]>
Removed 'optional' keywords from existing SCM files because they were not added correctly. The keyword requires a string value in the form optional("value") where "value" creates a category of optional fields exposed via the interface when the category "value" is included as a URL query parameter. Signed-Off-By: Kenneth Rowland [email protected]
Signed-off-by: Gavin Halliday <[email protected]>
Signed-off-by: Gordon Smith <[email protected]>
HPCC-29744 Remove existing 'optional' keywords from SCM files Reviewed-By: Shamser Ahmed <[email protected]> Reviewed-By: Anthony Fishbeck <[email protected]> Merged-by: Gavin Halliday <[email protected]>
Signed-off-by: Jake Smith <[email protected]>
Replaced explicit XSD and WSDL generation in genreated code by using existing library function. Signed-Off-By: Kenneth Rowland [email protected]
HPCC-29858 Update the platform version rules
Signed-off-by: Gordon Smith <[email protected]> # Conflicts: # helm/hpcc/Chart.yaml # helm/hpcc/templates/_helpers.tpl # helm/hpcc/templates/dafilesrv.yaml # helm/hpcc/templates/dali.yaml # helm/hpcc/templates/dfuserver.yaml # helm/hpcc/templates/eclagent.yaml # helm/hpcc/templates/eclccserver.yaml # helm/hpcc/templates/eclscheduler.yaml # helm/hpcc/templates/esp.yaml # helm/hpcc/templates/localroxie.yaml # helm/hpcc/templates/roxie.yaml # helm/hpcc/templates/sasha.yaml # helm/hpcc/templates/thor.yaml # version.cmake
HPCC-29381 Improve XSD generation for ESP services
https://track.hpccsystems.com/browse/HPCC-25955 |
@g-pan please remove examples/efs/README.md |
Signed-off-by: Gordon Smith <[email protected]> # Conflicts: # helm/hpcc/Chart.yaml # helm/hpcc/templates/_helpers.tpl # helm/hpcc/templates/dafilesrv.yaml # helm/hpcc/templates/dali.yaml # helm/hpcc/templates/dfuserver.yaml # helm/hpcc/templates/eclagent.yaml # helm/hpcc/templates/eclccserver.yaml # helm/hpcc/templates/eclscheduler.yaml # helm/hpcc/templates/esp.yaml # helm/hpcc/templates/localroxie.yaml # helm/hpcc/templates/roxie.yaml # helm/hpcc/templates/sasha.yaml # helm/hpcc/templates/thor.yaml # version.cmake
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.
Only one comment/question otherwise approved.
helm uninstall myhpcc | ||
``` | ||
## 2. Static storage within Kubernetes with values-retained-efs.yaml | ||
In this method, storage lives on the Kubernetes cluster level. It uses the helm chart "hpcc-efs-dynamic-pv" to manually create PVCs. The PVs are dynamically generated. The PVCs will persist after the HPCC cluster is deleted, meaning that the storage can be reused across different HPCC clusters.<br/> |
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.
The PVs are dynamically, should it be PVCs ??
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.
No, the PVCs aren't dynamically created, in the hpcc-efs-dynamic-pv/templates/create-pvc.yaml, they are actually manually created.
Signed-off-by: Richard Chapman <[email protected]>
helm/examples/efs/create-ap.sh
Outdated
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.
Add comment that For RISK user tag "owner" and "owner_email" are may required
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.
I added this just now to the README under the explanation of the 3rd storage method.
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.
Generally looks good. The tags need "owner" and "owner_email" for RISK users.
HPCC-29838 Add false sharing test case
…rvice Changed TpQueryType to string to produce correct type in XSD Signed-Off-By: Kenneth Rowland [email protected]
HPCC-29963 Correct XSD type conversion for TpQueryType in WsTopology Service
Signed-off-by: Gordon Smith <[email protected]> # Conflicts: # helm/hpcc/Chart.yaml # helm/hpcc/templates/_helpers.tpl # helm/hpcc/templates/dafilesrv.yaml # helm/hpcc/templates/dali.yaml # helm/hpcc/templates/dfuserver.yaml # helm/hpcc/templates/eclagent.yaml # helm/hpcc/templates/eclccserver.yaml # helm/hpcc/templates/eclscheduler.yaml # helm/hpcc/templates/esp.yaml # helm/hpcc/templates/localroxie.yaml # helm/hpcc/templates/roxie.yaml # helm/hpcc/templates/sasha.yaml # helm/hpcc/templates/thor.yaml # version.cmake
The way record lengths were fetched caused significant extra work for the localAgent where a temporary roxie row would be allocated and released for each count. Signed-off-by: Richard Chapman <[email protected]>
…/regression suite These options are only applied when Roxie us run in workunit mode in containerized systems. Signed-off-by: Richard Chapman <[email protected]>
…/regression suite Fix some issues with setting topology when localAgent is false Signed-off-by: Richard Chapman <[email protected]>
Changed loop to return immediately when element erased from map Signed-Off-By: Kenneth Rowland [email protected]
Signed-off-by: Jake Smith <[email protected]> # Conflicts: # helm/hpcc/Chart.yaml # helm/hpcc/templates/_helpers.tpl # helm/hpcc/templates/dafilesrv.yaml # helm/hpcc/templates/dali.yaml # helm/hpcc/templates/dfuserver.yaml # helm/hpcc/templates/eclagent.yaml # helm/hpcc/templates/eclccserver.yaml # helm/hpcc/templates/eclscheduler.yaml # helm/hpcc/templates/esp.yaml # helm/hpcc/templates/localroxie.yaml # helm/hpcc/templates/roxie.yaml # helm/hpcc/templates/sasha.yaml # helm/hpcc/templates/thor.yaml # version.cmake
The existing code uses the FileSpray.FileList to list the log files of each HPCC component in bare metal enviroment, which does not make sense. In this PR, a similar funcitonality is added to WsTopology. Signed-off-by: wangkx <[email protected]>
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.
couple of comments in line.
helm/examples/efs/README.md
Outdated
``` | ||
An example values file to be supplied when installing the HPCC chart. | ||
NB: Either use the output auto-generated when installing the "hpcc-efs" helm chart, or ensure the names in your values files for the storage types match the PVC names created. "values-retained-efs.yaml" expects that helm chart installation name is "awsstorage". Change the PVC name accordingly if another name is used. | ||
NB: Either use the output auto-generated when installing the "hpcc-efs" helm chart, or ensure the names in your values files for the storage types match the PVC names created. "values-retained-efs.yaml" expects that helm chart installation name is "awsstorage". Change the PVC name accordingly if another name is used.<br/> |
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.
Change: "values-retained-efs to: The "values-retained-efs
helm/examples/efs/README.md
Outdated
``` | ||
## 3. Static storage beyond Kubernetes with values-retained-efs.yaml | ||
In this method, the storage lives beyond the Kubernetes cluster. It uses the helm chart "hpcc-efs-static-pv" to manually create PVs and PVCs and to configure access points in EFS with the Kubernetes cluster. This means that even if the Kubernetes cluster is deleted, the storage will remain and can be reused across different Kubernetes clusters.<br/> | ||
The create-ap.sh script creates five access points in EFS for each of dali, dll, sasha, data, and mydropzone, and it displays a description for each access point. You may need to add additional tags to the access points depending on your organization. For example, for RISK users, the "owner" and "owner_email" tags are required; add these to the script as needed.<br/> |
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.
grammar: remove the "and" before mydropzone, s/b: for each of dali, dll, sasha, data, mydropzone, and it displays a description for each access point.
or could rewrite
The create-ap.sh script creates five access points in EFS. One for each component dali, dll, sasha, data, and mydropzone. It also displays a description for each access point.
helm/examples/efs/README.md
Outdated
|
||
helm uninstall will not delete EFS persistant volumes claims (PVC). You can either run "kubectl delete pv <pv name> or --all". | ||
Again, the storage needs to be created before starting the HPCC cluster. Under the helm directory, run the following command: |
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.
remove the word "Again"
helm/examples/efs/README.md
Outdated
Navigate to the EFS service and click "Create file system". Select the same VPC as the one your EKS cluster is running in. | ||
### Configuring the Mount Targets | ||
Click on the file system you just created and navigate to "Network". Your mount targets should be displayed.<br/> | ||
Click on "Manage", and you should see that the security groups for the mount targets are the default security group. Replace these with the EKS cluster security group. To find the EKS cluster security group, navigate to EKS, click on your cluster, click on "Networking", and it is the security group displayed under "Cluster security group". After replacing the default security group for all mount targets, save your changes. |
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.
run on sentence: To find the EKS cluster security group, navigate to EKS, click on your cluster, click on "Networking", and it is the security group displayed under "Cluster security group".
Can rewrite as : To find the EKS cluster security group navigate to EKS. Click on your cluster. Click on "Networking" and find the security group displayed under "Cluster security group".
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.
Thanks for the review. I've updated the parts you mentioned.
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.
approved.
HPCC-27303 Coverity scan reported new defects related to Configuration Reviewed-By: Attila Vamos <[email protected]> Merged-by: Gavin Halliday <[email protected]>
HPCC-29972 Add WsTopology.TpListLogFiles Reviewed-By: Anthony Fishbeck <[email protected]> Merged-by: Gavin Halliday <[email protected]>
…acker HPCC-30005 Refactor IMessageUnpackCursor Reviewed-by: Gavin Halliday <[email protected]> Merged-by: Gavin Halliday <[email protected]>
HPCC-29831 Allow localAgent setting to be set in workunit/regression suite Reviewed-by: Jake Smith <[email protected]> Reviewed-by: Gavin Halliday <[email protected]> Merged-by: Gavin Halliday <[email protected]>
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.
Ready to merge
Please squash ready for merging |
Signed-off-by: Jake Smith <[email protected]> # Conflicts: # helm/hpcc/Chart.yaml # helm/hpcc/templates/_helpers.tpl # helm/hpcc/templates/dafilesrv.yaml # helm/hpcc/templates/dali.yaml # helm/hpcc/templates/dfuserver.yaml # helm/hpcc/templates/eclagent.yaml # helm/hpcc/templates/eclccserver.yaml # helm/hpcc/templates/eclscheduler.yaml # helm/hpcc/templates/esp.yaml # helm/hpcc/templates/localroxie.yaml # helm/hpcc/templates/roxie.yaml # helm/hpcc/templates/sasha.yaml # helm/hpcc/templates/thor.yaml # version.cmake
Hi Gavin, I rebased the commits into one, which is "HPCC-25955 implemented static pvs". Let me know if its ok to merge, or if I should create a new pull request. Thanks, |
I think you need to execute something like: git fetch upstream Assuming upstream refers to hpcc-systems/HPCC-Platform To remove all the other commits from your PR. I suspect your local candidate-9.2.x branch is out of sync with the hpcc-systems branch. |
Closed, new PR #17687 has been created with the correct base and same changes. |
Implemented static pvs in order to create storage beyond the eks cluster.
Signed off by [email protected]
Type of change:
Checklist:
Smoketest:
Testing:
I tested the changes using AWS EKS.