1. 08 Mar, 2024 1 commit
    • Barnabas Busa's avatar
      refactor!: participant_network & rename participant fields. (#508) · fab341b1
      Barnabas Busa authored
      # Important!
      There are many participant fields that have been renamed to be more
      consistent with the rest of the package. The following fields have been
      renamed:
      ### EL Flags
      ```
      el_client_type -> el_type
      el_client_image -> el_image
      el_client_log_level -> el_log_level
      el_client_volume_size -> el_volume_size
      ```
      ### CL Flags
      ```
      cl_client_type -> cl_type
      cl_client_image -> cl_image
      cl_client_volume_size -> cl_volume_size
      cl_client_log_level -> cl_log_level
      beacon_extra_params -> cl_extra_params
      beacon_extra_labels -> cl_extra_labels
      bn_min_cpu -> cl_min_cpu
      bn_max_cpu -> cl_max_cpu
      bn_min_mem -> cl_min_mem
      bn_max_mem -> cl_max_mem
      use_separate_validator_client -> use_separate_vc
      ```
      ### Validator flags
      ```
      validator_client_type -> vc_type
      validator_tolerations -> vc_tolerations
      validator_client_image -> vc_image
      validator_extra_params -> vc_extra_params
      validator_extra_labels -> vc_extra_labels
      v_min_cpu -> vc_min_cpu
      v_max_cpu -> vc_max_cpu
      v_min_mem -> vc_min_mem
      v_max_mem -> vc_max_mem
      ```
      ### Global flags
      ```
      global_client_log_level -> global_log_level
      ```
      
      
      Once this PR is merged, the old names will no longer work, and you will
      have to bulk rename all your yaml files.
      
      A rename.sh bash script is added, which can be used to do bulk `find and
      replace` operations.
      ```bash
      rename.sh yourFile.yaml
      ```
      
      ---------
      Co-authored-by: default avatarGyanendra Mishra <anomaly.the@gmail.com>
      fab341b1
  2. 06 Mar, 2024 1 commit
    • pk910's avatar
      fix: fix end index in validator ranges file (#509) · da55be84
      pk910 authored
      The ranges.yaml currently looks like this:
      ```
      0-250: cl-1-lighthouse-geth
      250-500: cl-2-prysm-reth
      500-750: cl-3-lodestar-besu
      ```
      
      but the end index should be inclusive:
      ```
      0-249: cl-1-lighthouse-geth
      250-499: cl-2-prysm-reth
      500-749: cl-3-lodestar-besu
      ```
      da55be84
  3. 05 Mar, 2024 2 commits
  4. 04 Mar, 2024 1 commit
  5. 01 Mar, 2024 1 commit
  6. 29 Feb, 2024 1 commit
  7. 27 Feb, 2024 4 commits
  8. 22 Feb, 2024 1 commit
  9. 20 Feb, 2024 2 commits
  10. 12 Feb, 2024 2 commits
  11. 10 Feb, 2024 1 commit
  12. 09 Feb, 2024 1 commit
  13. 08 Feb, 2024 1 commit
  14. 02 Feb, 2024 2 commits
  15. 01 Feb, 2024 5 commits
  16. 29 Jan, 2024 1 commit
  17. 23 Jan, 2024 1 commit
  18. 22 Jan, 2024 1 commit
  19. 20 Jan, 2024 1 commit
  20. 18 Jan, 2024 1 commit
  21. 17 Jan, 2024 1 commit
  22. 16 Jan, 2024 2 commits
  23. 15 Jan, 2024 1 commit
  24. 11 Jan, 2024 2 commits
  25. 10 Jan, 2024 3 commits