S3: Update maxconn and npthread values from haproxy config

[sachitanands]

S3: Update maxconn and npthread values from haproxy config if setup size defined in solution.yaml as "large"

we are pointing to maxconn -> 1000 and nbthread -> 16 only in case of setup_size=large.

Signed-off-by: Sachitanand Shelake sachitanand.shelake@seagate.com

Problem Statement

• Problem statement

Design

• For Bug, Describe the fix here.
• For Feature, Post the link for design

Coding

Checklist for Author

• [ ] Coding conventions are followed and code is consistent

Testing

Checklist for Author

• [ ] Unit and System Tests are added
• [ ] Test Cases cover Happy Path, Non-Happy Path and Scalability
• [ ] Testing was performed with RPM

Impact Analysis

Checklist for Author/Reviewer/GateKeeper

• [ ] Interface change (if any) are documented
• [ ] Side effects on other features (deployment/upgrade)
• [ ] Dependencies on other component(s)

Review Checklist

Checklist for Author

• [ ] JIRA number/GitHub Issue added to PR
• [ ] PR is self reviewed
• [ ] Jira and state/status is updated and JIRA is updated with PR link
• [ ] Check if the description is clear and explained

Documentation

Checklist for Author

• [ ] Changes done to WIKI / Confluence page / Quick Start Guide

[sachitanands]

creating custom ci job : http://eos-jenkins.colo.seagate.com/job/GitHub-custom-ci-builds/job/centos-7.9/job/custom-ci/2604/

[vimalraghwani20]

@sachitanands 1N deployment job failed. please check

[stale[bot]]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @nileshgovande @bkirunge7 @knrajnambiar76 @t7ko-seagate for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.

[sachitanands]

Started 1 node k8 deployment http://eos-jenkins.mero.colo.seagate.com/job/Cortx-kubernetes/job/deploy-cortx-k8-cluster/985/ we will debug failure today

[stale[bot]]

This issue/pull request has been marked as needs attention as it has been left pending without new activity for 4 days. Tagging @nileshgovande @bkirunge7 @knrajnambiar76 @t7ko-seagate for appropriate assignment. Sorry for the delay & Thank you for contributing to CORTX. We will get back to you as soon as possible.