Skip to content
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

Release Candidate 2024.12.1.5 #261

Merged
merged 35 commits into from
Dec 18, 2024
Merged

Release Candidate 2024.12.1.5 #261

merged 35 commits into from
Dec 18, 2024

Conversation

jacderida
Copy link
Contributor

@jacderida jacderida commented Dec 17, 2024

This is all the changes that were accumulated for the 2024.12.1.5 release.

This can't be merged until the first publish of ant-service-management.

ermineJose and others added 30 commits November 28, 2024 15:40
feat: enable json as default log format
For a while the network dashboard will also use an intermediate branch.

This also fixes a clippy warning in a new version of Rust.
Various things were updated in accordance with the branding alignment for the binaries and
repository:

* Renamed version arguments on various commands from `safe` -> `ant`
* Renamed version variables/arguments/fields from `safe` -> `ant`
* Ansible: renamed `safe_user` role -> `ant_user`
* Ansible: renamed `node-manager` role -> `antctl`
* General: updated lots of small references over the whole codebase, from `safe` -> `ant`.
Initially the Telegraf configurations don't seem to be working with this new version.
In the base images, Telegraf has been disabled from automatically starting, because we don't want it
to start transmitting new metric names to the production database. Various lines for starting the
service have been commented out. These can be enabled again when we have the setup working.

Environment variables related to Telegraf are now prefixed with `ANTNODE_` or `ANT_` rather than
safe-based prefixes.

There's also a change in here to get `antcltd` to deploy correctly when a version-based deployment
is used.
This also re-enables the automatic start for Telegraf.
We now need to check `autonomi` rather than `safe_network`.
It is sometimes possible that the application of the `node` role will result in an error, such as
some nodes failing to start. In this case, Ansible will stop applying remaining roles on hosts where
the failure occurred. For this reason, we want to configure and start Telegraf before we attempt to
start the nodes, so that we will still collect monitoring data even if one or two nodes fail to
start.
- We'd run into problems if we are generating the infra options from a
  DeploymentInventory if the environment had issues while spining up
- Thus get all the values for the InfraRunOptions from the
  terraform::show command
It was recommended we use 100MB files to reduce gas fees.

The gas fee drain rate is also affected by the upload speed, so a sleep between each upload was
also recommended.

I've also introduced a banner, which should help to differentiate between each upload when scrolling
through the service log.
Since there is a one-to-one mapping between an `antX` user and an uploader service, the number of
uploader instances is determined by how many users there are.
This was the spec discussed and agreed for the next production environment.
The versioning output was changed for this binary.
The service should now be started automatically rather than be in a stopped state, which was
requested for development work.
This is necessary for for the monitoring setup.
@jacderida jacderida added the DoNotMerge Do not merge this branch yet label Dec 17, 2024
The ant-related crates have now been published, so these Git references can be replaced.

The `alloy` crate also needed to be updated.
@jacderida jacderida merged commit 3a70a29 into main Dec 18, 2024
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
DoNotMerge Do not merge this branch yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants