Skip to content

Issues: hashgraph/solo

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

80 Open 253 Closed
80 Open 253 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Add installer through common package managers P3 Low priority issue. Will not impact the release schedule if not complete.
#1001 opened Dec 17, 2024 by jeromy-cannon
Support to upgrade hedera version through solo commands Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. P0 An issue impacting production environments or impacting multiple releases or multiple individuals.
#1000 opened Dec 17, 2024 by JeffreyDallas
@JeffreyDallas
2
reduce redundancy on context to cluster flags in solo deployment create Internal Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P1 High priority issue. Required to be completed in the assigned milestone.
#977 opened Dec 10, 2024 by jeromy-cannon
@instamenta
solo deployment create should use the context and cluster provided for where to save the remote config instead of using the k8s current context Internal Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P1 High priority issue. Required to be completed in the assigned milestone.
#976 opened Dec 10, 2024 by jeromy-cannon
@instamenta
solo deployment create should use email address in local-config if it is already there instead of prompting the user for it Internal Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P1 High priority issue. Required to be completed in the assigned milestone.
#975 opened Dec 10, 2024 by jeromy-cannon
@instamenta
solo network destroy should update remote-config Internal Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P1 High priority issue. Required to be completed in the assigned milestone.
#965 opened Dec 9, 2024 by jeromy-cannon
@instamenta
update documentation to use solo deployment deploy and solo deployment destroy for quick start Documentation Issue related to enhancing documentation Needs Refinement The issue needs more refinement and/or design before it can be worked P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.
#964 opened Dec 9, 2024 by jeromy-cannon
solo deployment destroy - take down everything, but has flags and prompts for certain items that normally would not be taken down such as cluster, with warnings if other deployments are in the cluster (alias to solo destroy) Needs Refinement The issue needs more refinement and/or design before it can be worked P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.
#963 opened Dec 9, 2024 by jeromy-cannon
solo deployment deploy - single command for all, takes options necessary to do everything, creates a single cluster deployment if one is not supplied using defaults (alias to solo install) (might go well with #877) Needs Refinement The issue needs more refinement and/or design before it can be worked P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.
#962 opened Dec 9, 2024 by jeromy-cannon
solo deployment list -cluster solo-1 - give cluster and return a list of solo deployments on that cluster Internal Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.
#961 opened Dec 9, 2024 by jeromy-cannon
Capture the full command line call, not just the command and subcommand, but all flags and their parameters as it was called P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.
#960 opened Dec 9, 2024 by jeromy-cannon
Capture email address of user that ran the command in the command history P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.
#959 opened Dec 9, 2024 by jeromy-cannon
give options on how to set stake recalculate back to 24 hours (from 1 minute setting) after we initialize the network, or flags to override/not override, etc Internal Requirement Needs Refinement The issue needs more refinement and/or design before it can be worked P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.
#958 opened Dec 9, 2024 by jeromy-cannon
@jeromy-cannon
Production Readiness: Ensure Solo is passing the consensus node's NodeID as an environment variable and/or command line argument Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments.
#943 opened Dec 6, 2024 by nathanklick
Production Readiness: Ensure HashIO (JSON RPC Relay) has been validated and is deployed/configured correctly
#942 opened Dec 6, 2024 by nathanklick
@JeffreyDallas
Production Readiness: Verify Mirror Node returns address book with correct IP/FQDN for service endpoints and certificate information
#940 opened Dec 6, 2024 by nathanklick
@JeffreyDallas
Production Readiness: Verify Ledger File 0.0.101 & 0.0.102 has correct IP/FQDN for service endpoints and certificate information
#939 opened Dec 6, 2024 by nathanklick
Production Readiness: Verify gossip ports are exposed via either a direct LoadBalancer or via HAProxy w/ TCP passthrough Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments.
#938 opened Dec 6, 2024 by nathanklick
Production Readiness: Support for an external S3 bucket and not deploying a minio server instance
#936 opened Dec 6, 2024 by nathanklick
Production Readiness: Update account init/rekey logic to also update the Node admin keys
#935 opened Dec 6, 2024 by nathanklick
@JeffreyDallas
Production Readiness: Pass custom Mirror Node PostgreSQL credentials and server address along with disabling stackgres deployment
#934 opened Dec 6, 2024 by nathanklick
Production Readiness: Ability to specify custom throttle configuration file
#933 opened Dec 6, 2024 by nathanklick
Add proxy/ingress/gateway to Mirror Node and provide ability for user to pass in a reserved static IP address Internal Requirement Needs Refinement The issue needs more refinement and/or design before it can be worked P0 An issue impacting production environments or impacting multiple releases or multiple individuals.
#929 opened Dec 5, 2024 by jeromy-cannon
@jeromy-cannon
Split current Readme into multiple pages and restructure docs Epic Lv2 A body of work that can be broken down into specific tasks. P2 Required to be completed in the assigned milestone, but may or may not impact release schedule.
#914 opened Dec 3, 2024 by jeromy-cannon
@JeffreyDallas
Implement solo context connect - connects to a deployment and pulls back the RemoteConfig for two cluster deployment Internal Requirement Multiple Cluster Support Issues which are only required to enable Solo support for multi-cluster deployments. P1 High priority issue. Required to be completed in the assigned milestone.
#913 opened Dec 3, 2024 by jeromy-cannon
1 task
@Ivo-Yankov
ProTip! Find all open issues with in progress development work with linked:pr.