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

[TASK] Simplify the Overall Cardano Shelly Node Setup #1538

Open
lazaridiscom opened this issue Jan 12, 2020 · 4 comments
Open

[TASK] Simplify the Overall Cardano Shelly Node Setup #1538

lazaridiscom opened this issue Jan 12, 2020 · 4 comments
Labels

Comments

@lazaridiscom
Copy link
Contributor

@lazaridiscom lazaridiscom commented Jan 12, 2020

(draft)

Situation

The setup of a Cardano Test Node is currently not very straightforward.

Goal

  • Any non-dev should be able to setup a (Cardano Shelly) node without much "trouble"

Steps

(ordered by expected difficulty)

Basic

  • #1528 - Simplify README
  • #1534 - Negate the Need to Manually Lookup Latest Release Tag
  • #1574 - Provide a Test-Net Incident Process
  • #1561 - Simplify the Cardano Shelly Testnet Documentation

Advanced

  • #1529 - Move "bootstrap" functionality into "jcli"
  • draft: functionality should be kept within the node, the cli, and config-files)
  • draft: functionality should be reusable "as-is" for other networks
  • #1562 - Consider Rebranding "jormungandr" to "cardano-node-rust"

Compatibility

This involves most possibly some slight architectural additions/changes, mostly within config.

Requirements

This task should not distract the core-devs from their current production-flow (except the usual merge-reviews).

@rdlrt

This comment has been minimized.

Copy link

@rdlrt rdlrt commented Jan 13, 2020

Thanks for this, but a basic counter-query:
Use of bootstrap script or the equivalent functionality (to set up a seperate network) is not required for the node set up. I dont see why a regular node operator who does not qualify for basline skills and requirements would need to use this.
Moreover, someone interested in setting up a seperate network will need to customise the parameters he would like for his seperate network, not very useful to move to a static setting in jcli instead.

@lazaridiscom

This comment has been minimized.

Copy link
Contributor Author

@lazaridiscom lazaridiscom commented Jan 13, 2020

Oh, I cannot answer you at this point, as I'm still in "draft, high-level" mode, so I need to postpone any answers to your query. Be aware that it is possible that I mention things that are not applicable, in that case I simply revise the draft text / issues.

@NicolasDP

This comment has been minimized.

Copy link
Collaborator

@NicolasDP NicolasDP commented Jan 17, 2020

I salute the initiative!

Keep in mind that jcli is meant to be a developer tool and not a management of the node tool or a wallet. It aims is to be as low level as possible in order to be able to quickly create a key, an address and do some testing. It is possible to build on top though, I am thinking https://github.com/rinor/jorcli for example.

@lazaridiscom

This comment has been minimized.

Copy link
Contributor Author

@lazaridiscom lazaridiscom commented Jan 18, 2020

re jcli, see #1529 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.