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.

Sign up for GitHub

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

Jump to bottom

Drop the go-waku fleets #18

Closed
richard-ramos opened this issue Jan 24, 2024 · 16 comments
Closed

Drop the go-waku fleets #18

richard-ramos opened this issue Jan 24, 2024 · 16 comments
Assignees
@yakimant

Comments

@richard-ramos
Copy link
Member

The following fleets are no longer necessary:

  • go-waku.test
  • go-waku.prod

cc: @chaitanyaprem, @fryorcraken
@jakubgs
Copy link
Member

jakubgs commented Feb 1, 2024 •
edited by yakimant

These fleets aren't really being widely used so no announcement or grace period should be required. It should be enough just to remove references from a few most important repositories:

@yakimant
Copy link
Member

yakimant commented Feb 2, 2024 •
edited

@yakimant
Copy link
Member

yakimant commented Feb 2, 2024 •
edited

ENRs to search

  • enr:-Ke4QExRcU9q8vpafzM7CDJT8i6izTXPvVTnhudE9CtnsQc8WJU1Fpzq8IxMiH6cX3Y6Hqxc4WUjpqTy8d2DOAd43e6GAYxFkWZwgmlkgnY0gmlwhIbRhj-CcnOLABAEAIABAAAgAECJc2VjcDI1NmsxoQLXeU4lGSJ1tZxRe52bZF68NIrqji8ld9f3-xIbjPxbPoN0Y3CCdl-DdWRwgiMohXdha3UyAQ
  • enr:-Ke4QCdzv_hJ-MofGck6JnWfl8BMVat_TRW6tPsf5meGosTzHhQZgIfx3syYZ3Kri1RM35V3UxDub5PWnbxBP1_ny2SGAYxFlQGFgmlkgnY0gmlwhCPft1uCcnOLABAEAQAAIABAAICJc2VjcDI1NmsxoQOoVQePH5eRqlcCf-0XwZsoJPeZp1Mq59un_jYM9hUc6YN0Y3CCdl-DdWRwgiMohXdha3UyAQ
  • enr:-Ke4QH5OS77duLmvpH-RZMaoZ-ATagcJdIbttDAsZo7TzBHuI6LN5dO2MmWstcR0KyrdLVvm16e7t1gecz6libHKX2CGAYxFlOsDgmlkgnY0gmlwhAjaAm6CcnOLABAEAEAAgAEAACCJc2VjcDI1NmsxoQLqosp15CMf5c4k-z9MGM7_aiR0DGdmSrpjQ_xWnmsTOIN0Y3CCdl-DdWRwgiMohXdha3UyAQ
  • enr:-Ke4QExRcU9q8vpafzM7CDJT8i6izTXPvVTnhudE9CtnsQc8WJU1Fpzq8IxMiH6cX3Y6Hqxc4WUjpqTy8d2DOAd43e6GAYxFkWZwgmlkgnY0gmlwhIbRhj-CcnOLABAEAIABAAAgAECJc2VjcDI1NmsxoQLXeU4lGSJ1tZxRe52bZF68NIrqji8ld9f3-xIbjPxbPoN0Y3CCdl-DdWRwgiMohXdha3UyAQ
  • enr:-Ke4QCdzv_hJ-MofGck6JnWfl8BMVat_TRW6tPsf5meGosTzHhQZgIfx3syYZ3Kri1RM35V3UxDub5PWnbxBP1_ny2SGAYxFlQGFgmlkgnY0gmlwhCPft1uCcnOLABAEAQAAIABAAICJc2VjcDI1NmsxoQOoVQePH5eRqlcCf-0XwZsoJPeZp1Mq59un_jYM9hUc6YN0Y3CCdl-DdWRwgiMohXdha3UyAQ
  • enr:-Ke4QH5OS77duLmvpH-RZMaoZ-ATagcJdIbttDAsZo7TzBHuI6LN5dO2MmWstcR0KyrdLVvm16e7t1gecz6libHKX2CGAYxFlOsDgmlkgnY0gmlwhAjaAm6CcnOLABAEAEAAgAEAACCJc2VjcDI1NmsxoQLqosp15CMf5c4k-z9MGM7_aiR0DGdmSrpjQ_xWnmsTOIN0Y3CCdl-DdWRwgiMohXdha3UyAQ

Not found on GitHub

@yakimant
Copy link
Member

yakimant commented Feb 2, 2024

For status-mobile need to update with
https://github.com/status-im/status-mobile/blob/4dded72878a4edc9140793e7ec0588e83e4a6c64/Makefile#L163-L166
after fleet is down.

@jakubgs
Copy link
Member

jakubgs commented Feb 2, 2024

You can just remove the fleet from the fleets script before the fleet is removed:
https://github.com/status-im/infra-misc/blob/da372af282cef6f0de2485bef34a2729ed5303e1/ansible/roles/status-fleets/files/eth_fleet_json.py#L128-L133

@yakimant yakimant mentioned this issue Feb 2, 2024
Merged
@yakimant
Copy link
Member

yakimant commented Feb 2, 2024 •
edited

Remove from status-fleets:
https://github.com/status-im/infra-misc/commit/d204c4beacc6d0fbde5da9835e856afc445cd49a

PR for status-mobile:
status-im/status-mobile#18708

PR for status-desktop:
status-im/status-desktop#13408

@yakimant yakimant mentioned this issue Feb 2, 2024
Merged
@yakimant
Copy link
Member

yakimant commented Feb 2, 2024 •
edited

@jakubgs, @richard-ramos, do you think we can decomission fleets before new versions of Status Desktop and Mobile are released (with fleets.json updated)?

Jakub kind of mentioned this already:

These fleets aren't really being widely used so no announcement or grace period should be required.

Just double checking about the release.

@richard-ramos
Copy link
Member Author

Yes, they can be decomissioned

@yakimant
Copy link
Member

yakimant commented Feb 6, 2024 •
edited

Also:

  • canary
  • metrics
  • grafana
  • terraform state on Consul K/V

@yakimant
Copy link
Member

yakimant commented Feb 6, 2024

Canaray and metrics cleanup:
https://github.com/status-im/infra-hq/commit/1cc0a2cbee034e3290ec270ba4a5ee8044b02776

@yakimant
Copy link
Member

yakimant commented Feb 6, 2024

Cleaned up / and /data volumes on prod with shred -vn 1 /dev/XXX

@yakimant
Copy link
Member

yakimant commented Feb 6, 2024

Grafana

Can we clean it?

@yakimant
Copy link
Member

yakimant commented Feb 6, 2024

All done.

@jakubgs, @richard-ramos, please review and help to decide on Grafana dashboards.
Everything else looks done, will archive the repo after review.

@jakubgs
Copy link
Member

jakubgs commented Feb 6, 2024

I think it's fine to keep go-waku dashboards on Grafana, just to move them to some kind of Archive folder.

@jakubgs
Copy link
Member

jakubgs commented Feb 6, 2024

And remember to add a warning at the top of readme about this being a legacy repo, like so:
https://github.com/status-im/infra-avalanche

@yakimant
Copy link
Member

yakimant commented Feb 9, 2024

All done, archiving.

@yakimant yakimant closed this as completed Feb 9, 2024
@jakubgs jakubgs mentioned this issue Feb 14, 2024
Merged
sushmitsarmah pushed a commit to sushmitsarmah/go-waku that referenced this issue Apr 29, 2024
@jakubgs
chore(ci): drop build discord noficiation
8e95f75 
No longer necessary due to fleet decomissioning:
status-im/infra-go-waku#18

Signed-off-by: Jakub Sokołowski <jakub@status.im>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@yakimant yakimant

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@richard-ramos @yakimant @jakubgs @apentori