Open rohansx opened 3 months ago
@Phoenix500526 Pleaase review this PR and let me know the changes and then I'll proceed with the documentation
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 75.16%. Comparing base (
eadf2d9
) to head (eaea991
).
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
@liangyuanpeng adjusted port configurations for xLine nodes and added client container for enhanced interaction. @Phoenix500526 updated node2 and node3 ports to avoid special port conflicts and included --client-listen-urls and --peer-listen-urls for clearer networking. Also added a client service for testing and interaction purposes.
@Phoenix500526 I have done the necessary modification as you mentioned above. I updated client container image for CI validation process to ghcr.io/xline-kv/etcdctl:v3.5.9
There are still some problems with the validation CI. Please fix them so that this pr can pass the CI. You can run the validation on your local via executing scripts/validation_test.sh
.
There are still some problems with the validation CI. Please fix them so that this pr can pass the CI. You can run the validation on your local via executing
scripts/validation_test.sh
.
working on this.
There are several issues in this pr:
client
. @Phoenix500526 @liangyuanpeng , I am encountering a validation check error, and I have tried to resolve it without success. Could you please explain why this validation check is failing and provide guidance on how I can address the issue?
@Phoenix500526 @liangyuanpeng , I am encountering a validation check error, and I have tried to resolve it without success. Could you please explain why this validation check is failing and provide guidance on how I can address the issue?
I think there are several reasons behind this validation failure:
ci-client-1
, not client
. Hence, the validation test will get an error like "No such container named client"172.20.0.0/16
to 172.22.0.0/16
, but you forgot to update the ip address in the validation_test.sh
. quick_start.sh
mounts ./scripts
to /mnt
and the validation_test.sh
uses the ./scripts/validation_lock_client
to do some test stuff. Finally, please modify our quick start doc to make it unify with the code change in this pr. Thanks 😄
Hi, @rohansx ! This pr has been stalled for 3 weeks. Would you like to update it? 😄
Hi, @rohansx ! This pr has been stalled for 3 weeks. Would you like to update it? 😄
@Phoenix500526 yes I'll update in the next week.. sorry for the delay.. actually kind of looking for a job and got stuck in the interview process and therefore i couldn't look into it..
@Mergifyio rebase
rebase
@rohansx Your PR is in conflict and cannot be merged.
Key Changes:
docker-compose.yml
file to manage the Xline cluster configuration, ensuring all services are correctly networked and equipped with the necessary volumes, ports, and environment settings.validation.sh
script to utilize Docker Compose for starting and stopping services, aligning it with the new docker-compose.yml configuration. This update simplifies the validation process and ensures compatibility with the Docker Compose setup.benchmark.sh
andquick_start.sh
documentation to reflect the new Docker Compose-based approach. This includes instructions on how to use the docker-compose file for setting up a development or testing environment and guidelines for executing validation and benchmark tests.These changes aim to streamline the project's testing framework, reduce redundancy, and improve the overall developer experience when testing and validating the Xline cluster's functionality.
Resolves: #692