You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In addition, there were some notes the team dropped, to make sure things work smoothly:
please communicate how the packaging will be done, so they can prepare it if a distro packaged is required
make sure all configuration nobs are exposed, at least via the configuration file (i.e. no hard coded constants)
their end goal would be to have a CI/CD setup, so we would not have access keys, and instead the CI would get a temporary access token to do the deployment
they do have a standard for servers, which is a suite of packages they are used to. We need to learn what these are to do our metrics
they need to know how the healthchecking will be done, that is attached to the way the software is deployed, and we need to answer the packaging question above, because that affects the healthchecking
they noted that containers may have IOPS limits, that starts to be an issue around 1TB of data
Feedback from the DevOps team on our issues
We want to DevOps team to give us feedback to the following issues:
In order to let ppl use Miden, we need a remote node deployed, see https://0xpolygonmiden.github.io/miden-base/introduction/getting-started.html
We already reached out to the DevOps team and got the following information
Notes from the first call
@hackaugusto thanks for the notes.
To summarize the meeting we had with the dev ops. These are the things that they need to get started:
Our answers
Additional notes
In addition, there were some notes the team dropped, to make sure things work smoothly:
Feedback from the DevOps team on our issues
We want to DevOps team to give us feedback to the following issues:
Next steps
Timeline
I need a stable remote Miden Node for our workshops in Denver. To have buffer, can you please ensure we have something running Thursday 22th Feb?
The text was updated successfully, but these errors were encountered: