-
Notifications
You must be signed in to change notification settings - Fork 21
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
Need some kind of ability to dynamically increase the number of nodes #1737
Comments
It might very well be possible already with the right configuration( Please feel free to do some experimentation :) |
@timaa2k That won't work because a cluster is identified by its |
As a workaround you can vertically scale the agents. This works in cases where resources, memory are storage are insufficient but not in cases where extra ports are required. |
I'll enumerate a few criteria:
The way I see this working, psuedocode: @click.command()
def provision_agent(cluster_id, role):
existing_cluster = ...(cluster_id)
# add multiple options from `provision`?
# Or work stuff out from the existing cluster?
cluster_backend = Docker()
new_cluster = Cluster(
cluster_backend=cluster_backend,
# Or different if the role != agent
agents=1,
public_agents=0,
masters=0,
)
print(new_node_id) @click.command()
def agent_install(cluster_id, node_id):
existing_cluster = ...(cluster_id)
agent = get_node(cluster_id, node_id)
# This is not an existing function but we could work it out
config = get_config_from_existing_cluster()
agent.install_dcos_from_path(
dcos_installer=dcos_installer,
dcos_config=config,
role=role,
)
existing_cluster.wait_for_dcos() |
I'm not sure whether this functionality is already available in minidcos.
RIght now once the cluster the created using below command
minidcos docker/vagrant create ./dcos_generate_config.sh --agents n
We will endup with constant nodes. If we want to add few nodes extra we don't have any options other than creating new cluster.
The text was updated successfully, but these errors were encountered: