Define node personas in the graph file

[josibake]

Such as:

• Raspi - low RAM, low CPU
• Wumbo node - big CPU, big RAM
• bad latency
• regularly offline (pops up every now and again)

These are basically things that cannot be defined in bitcon.conf

[josibake]

• flakey nodes (disconnects, poor latency)
• slow nodes (dont propagate txs or blocks quickly)
• spy nodes
• lightning nodes
• NPC nodes
• berserker nodes (do crazy shit)

As a UI, id imagine some interface where users can click through nodes and pick the ones they want. very video game style, where you get an explanation of the nodes "stats", maybe some animation?

[willcl-ark]

Linked this to #99

[willcl-ark]

@m3dwards Does k8s support limiting resouce usage like docker? So could I make a RasPi node with 2 CPU, 1GB RAM and 10 GB HDD for example?

If so we can keep this open and perhaps I can adapt #99 for k8s, otherwise we can close.

[m3dwards]

Yep you can specify resource limits.

[willcl-ark]

OK great, will keep this open while I: try k8s & modify #99 for k8s

[josibake]

@m3dwards this seems easy enough to model with the new yaml based configs with Helm. Is something we want for Tabconf?

[pinheadmz]

We could just have a few macros available for this, ie profile: raspi would automatically set the more verbose settings:

    resources:
      requests:
        cpu: 100m
        memory: 1Gi

[m3dwards]

@pinheadmz would also need limit as well as request but yes.

We might need to consider putting the current config under a key called helmValues or something because I'm not starting to like that some of the keys below a node are special and some just get passed along to helm. I think it's going to get confusing.