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

node_master should be able to provision workers without network messaging #519

Closed
godber opened this issue Aug 30, 2017 · 1 comment
Closed

Comments

@godber
Copy link
Member

godber commented Aug 30, 2017

node_master can provision slicers and workers based on something (file or ENV variable) that doesn't rely on network messaging.

@godber
Copy link
Member Author

godber commented Sep 7, 2017

The node master should use the following environment variables:

  • CLUSTER_MANAGER_TYPE - Should be native or kubernetes, it indicates what "mode" the Node master is running in. If the variable is not present, or set to native then it is implied that we are using the original network based node manager activities. If set to kubernetes the node master should get its node type and execution context from the environment variables below.
  • NODE_TYPE - Should be slicer or worker. When set to slicer then the node master should create a slicer, when set to worker the node master should create a worker.
  • EX - Should be set to the JSON representation of the execution context.

In the kubernetes mode all of these will be set as environment variables in the deployments created by the cluster manager.

@godber godber closed this as completed in f867e87 Sep 14, 2017
godber added a commit that referenced this issue Sep 14, 2017
first round of starting slicer/worker on startup resolves #519
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant