nimbus.kiln: enable --*-light-client-data

[etan-status]

No description provided.

[etan-status]

• Rebase to master.

[etan-status]

• Updated variable names, and marked as draft until the kiln branch is up to date and actually has support for the new feature.

[etan-status]

• Rename branch to kiln-dev-auth.

[etan-status]

• Move light client variables below eth1 sync config and separate with comment

[etan-status]

kiln-dev-auth head is the branch to use for kiln network. The issue highlighted in comment has been fixed:
https://github.com/status-im/nimbus-eth2/blob/7054421a8379e1ebffa76a962b45314232482e6c/beacon_chain/networking/network_metadata.nim#L208

kiln-dev-auth also supports light client data config:
https://github.com/status-im/nimbus-eth2/blob/7054421a8379e1ebffa76a962b45314232482e6c/beacon_chain/conf.nim#L429-L440

[jakubgs]

When I try to deploy this I get:

{"lvl":"FAT","ts":"2022-03-28 07:05:59.468+00:00","msg":"Could not load head state, database corrupt?","head":"3f54beeb:1599","tail":"d30e447c:0","genesis":"d30e447c:0"}

If I try to start from a fresh DB I get:

{"lvl":"FAT","ts":"2022-03-28 07:32:51.131+00:00","msg":"No database and no genesis snapshot found: supply a genesis.ssz with the network configuration, or compile the beacon node with the -d:has_genesis_detection option in order to support monitoring for genesis events","topics":"beacnde"}

So the current state of kiln-dev-auth is not usable. The second issue appears to be fixed in status-im/nimbus-eth2#3549.

[jakubgs]

Deployment worked after merging status-im/nimbus-eth2#3549:

 > a nimbus.kiln -a "systemctl cat 'beacon-node-*' | grep light-client"      
metal-01.he-eu-hel1.nimbus.kiln | CHANGED | rc=0 >>
    --serve-light-client-data=true \
    --import-light-client-data=only-new \
    --serve-light-client-data=true \
    --import-light-client-data=only-new \
    --serve-light-client-data=true \
    --import-light-client-data=only-new \
    --serve-light-client-data=true \
    --import-light-client-data=only-new \