-
Notifications
You must be signed in to change notification settings - Fork 54
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
chore: add supervisor for lpt infra #3176
Conversation
… to ease infra deployment
…ra.env defines defaults for run, in case image tag of lpt docker image is deploy it will build a specific image for infra deployment.
You can find the image built from this PR at
Built from c939756 |
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.
Thank you!
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.
LGTM! Thanks for it! 💯
I just added some minor comments
--build-arg="MAKE_TARGET=liteprotocoltester" \ | ||
--build-arg="NIMFLAGS=$(DOCKER_LPT_NIMFLAGS)" \ | ||
--build-arg="NIM_COMMIT=$(DOCKER_NIM_COMMIT)" \ | ||
--build-arg="LOG_LEVEL=TRACE" \ | ||
--label="commit=$(shell git rev-parse HEAD)" \ | ||
--label="version=$(GIT_VERSION)" \ | ||
--target $(TARGET) \ | ||
--target $(if $(filter deploy,$(DOCKER_LPT_TAG)),deployment_lpt,standalone_lpt) \ |
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.
what's the diff between deployment_lpt
and standalone_lpt
?
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.
It is the distinction between the different use. deployment_lpt
stands for running in our infra environment with its own constraints. - main diff is that in deployment we need to run a supervisor ahead of tests that can control restarts.
standalone_lpt
is the normal usage, so in lpt_runner you can easily run your tests on demand.
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 clarifying! I was wondering if we could add a comment somewhere, if not done already:)
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.
Yeah must add it to lpt readme at least!
apps/liteprotocoltester/infra.env
Outdated
TEST_INTERVAL_MINUTES=10 | ||
START_PUBLISHING_AFTER=120 | ||
NUM_MESSAGES=300 | ||
DELAY_MESSAGES=1000 |
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.
Maybe we could have a more explicit var name;P
DELAY_MESSAGES=1000 | |
MSG_INTERVAL_MILLIS=1000 |
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.
Good idea! I need to apply such change more deep. I will check!
apps/liteprotocoltester/infra.env
Outdated
@@ -0,0 +1,11 @@ | |||
TEST_INTERVAL_MINUTES=10 | |||
START_PUBLISHING_AFTER=120 |
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.
START_PUBLISHING_AFTER=120 | |
START_PUBLISHING_AFTER_SECS=120 |
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.
Just as above, thanks for the suggestion.
…notice about infra deployment
…defined test setup
Description
This PR is based upon the previous one, and serves the same sole purpose: enable infra deployment.
Prev PR: #3158
Changes