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

Teraslice worker versions should report NA in k8s clustering #981

Closed
godber opened this issue Jan 25, 2019 · 5 comments
Closed

Teraslice worker versions should report NA in k8s clustering #981

godber opened this issue Jan 25, 2019 · 5 comments
Labels
k8s Applies to Teraslice in kubernetes cluster mode only. pkg/teraslice
Milestone

Comments

@godber
Copy link
Member

godber commented Jan 25, 2019

In k8s mode, I think teraslice currently reports the master version as the teraslice_version for each worker node. It should probably report N/A. Perhaps each worker listed under active should report it's own stats.

    "10.6.6.6": {
        "node_id": "10.6.6.6",
        "hostname": "10.6.6.6",
        "pid": "N/A",
        "node_version": "v8.12.0",
        "teraslice_version": "0.44.4",
        "total": "N/A",
        "state": "connected",
        "available": "N/A",
        "active": [...
@godber godber added the k8s Applies to Teraslice in kubernetes cluster mode only. label Jan 25, 2019
@godber
Copy link
Member Author

godber commented Jan 25, 2019

Erik also asked about adding information about the execution controller to cluster state as well.

@godber godber added this to the v0.51.0 milestone Feb 25, 2019
@godber
Copy link
Member Author

godber commented Feb 25, 2019

Rather than reporting NA, it could report the worker's version (doing so would be ideal). I am not sure what's involved in that, probably a lot of fiddly messaging that may not be worth the effort. Unless it's stored in the deployment, oh, it probably is.

@peterdemartini
Copy link
Contributor

I think the reason why we used N/A was not that it was difficult to get information but the "node" could potentially have many executions running on it, with different teraslice versions.

@godber
Copy link
Member Author

godber commented Mar 6, 2019

Ok, for now, I am going to do this:

  • Set node_version and teraslice_version to N/A at the worker/node level since it doesn't really have meaning in the k8s case (there's not node manager, a single node can run workers with versions that differ)
  • Add an image property that reports the docker image used, including tag, which in our case provides version and build information.

I think this solution makes a decent compromise, maybe the /txt output should show image instead of node_version and teraslice_version in the k8s master case. We haven't introduced any differences at the /txt api based on cluster type, but I'll see if doing so is convenient.

@godber
Copy link
Member Author

godber commented Mar 6, 2019

/txt/workers will now read more usefully:

######  Workers  ######

assignment  job_id  ex_id  node_id    pod_name                           image
----------  ------  -----  ---------  ---------------------------------  ------------------
master      N/A     N/A    10.0.2.15  teraslice-master-794bdf85f6-dl49k  teraslice-k8sdev:1

@godber godber modified the milestones: v0.51.0, v0.50.0 Mar 6, 2019
@godber godber closed this as completed Mar 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
k8s Applies to Teraslice in kubernetes cluster mode only. pkg/teraslice
Projects
None yet
Development

No branches or pull requests

2 participants