-
Notifications
You must be signed in to change notification settings - Fork 12
feat(block-node): implement 'solo block node add' command and modify remote config to support multiple relays, block nodes, mirror nodes and explorers #1821
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
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Zhan Milenkov <[email protected]>
…ition, added the new flag about the block nodes chart version together with the initial constants Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
…by using new types Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
… and initial setup for m4 apple chip compatibility Signed-off-by: Zhan Milenkov <[email protected]>
…block-nodes-deploy # Conflicts: # src/commands/base.ts # src/commands/flags.ts # src/core/constants.ts
Signed-off-by: Zhan Milenkov <[email protected]>
…ngs in the remote config related classes and worked on adding support for the new component type 'BlockNodeComponents' Signed-off-by: Zhan Milenkov <[email protected]>
…cy and make it less error prone Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
…the releaseName Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
…porting m4 apple chips Signed-off-by: Zhan Milenkov <[email protected]>
…and renamed ComponentType to ComponentTypes to follow convention Signed-off-by: Zhan Milenkov <[email protected]>
…nfig Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
…block-nodes-deploy
…rategy Signed-off-by: Zhan Milenkov <[email protected]>
…codebase to use them, fixed most unit tests, todo: fix all tests, add new logic for editing remote components which should only work for consensus node's node state field Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
…onExpressions to avoid having to have dublicated function return value difinitions Signed-off-by: Zhan Milenkov <[email protected]>
…o remote config Signed-off-by: Zhan Milenkov <[email protected]>
…Name Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
…block-nodes-deploy
…block-nodes-deploy
…block-nodes-deploy # Conflicts: # src/core/config/remote/components/consensus-node-component.ts # src/core/config/remote/components/relay-component.ts # src/core/config/remote/remote-config-manager.ts
52f085d
Signed-off-by: Zhan Milenkov <[email protected]>
…block-nodes-deploy # Conflicts: # src/commands/explorer.ts # src/commands/mirror-node.ts # version.ts
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
Signed-off-by: Zhan Milenkov <[email protected]>
@@ -137,7 +137,7 @@ export default [ | |||
'warn', | |||
{ | |||
allowExpressions: false, | |||
allowTypedFunctionExpressions: false, | |||
allowTypedFunctionExpressions: true, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
revert
} catch (error) { | ||
logger.showUserError(error); | ||
expect.fail(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you apply this to the block node destroy PR where the integration with consensus happens? I'm not sure what happens with block node for this test without consensus node actually integrated.
This is my original question that the image above was a response to:
What is the best way to see if Block Nodes is functional after Consensus Nodes are running?
name: 'block-node-version', | ||
definition: { | ||
describe: 'Block nodes chart version', | ||
defaultValue: version.MIRROR_NODE_VERSION, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copy/paste error?
defaultValue: version.MIRROR_NODE_VERSION, | ||
type: 'string', | ||
}, | ||
prompt: async function promptMirrorNodeVersion( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copy/paste error?
Flags.mirrorNodeVersion.definition.defaultValue as boolean, | ||
'Would you like to choose mirror node version? ', | ||
null, | ||
Flags.mirrorNodeVersion.name, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
copy/paste error?
|
||
if (isAppleM4SeriesChip) { | ||
valuesArgument += helpers.populateHelmArguments({ | ||
'blockNode.config.JAVA_OPTS': '"-Xms8G -Xmx8G -XX:UseSVE=0"', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hmm... this won't work if we deploy to GKE, AWS, or Latitude from our MacOS laptops that have a M4 chip and they have overrode the min/max JVM size in the values file.
task: async (context_): Promise<void> => { | ||
const config: BlockNodeDeployConfigClass = context_.config; | ||
|
||
config.isChartInstalled = await this.chartManager.isChartInstalled( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where is this being used?
}; | ||
} | ||
|
||
private displayHealthcheckData( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
private displayHealthcheckData( | |
private displayHealthCheckData( |
task: async (context_, task): Promise<void> => { | ||
const config: BlockNodeDeployConfigClass = context_.config; | ||
|
||
const displayHealthcheckCallback: ( |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
const displayHealthcheckCallback: ( | |
const displayHealthCheckCallback: ( |
Description
adds new command and command group
block node
with the classBlockNodeCommand
add
used to install the block node official helm chart inside the specified clusterAdds wrapper classes and logic for creating commands with 3 levels of depth
solo block node add
Related Issues
solo block-nodes deploy
#1755Pull request (PR) checklist
package.json
changes have been explained to and approved by a repository managerTesting