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

Support multi-platform storages for Tensorboard #337

Closed
IronPan opened this issue Nov 20, 2018 · 5 comments
Closed

Support multi-platform storages for Tensorboard #337

IronPan opened this issue Nov 20, 2018 · 5 comments
Assignees

Comments

@IronPan
Copy link
Member

IronPan commented Nov 20, 2018

Currently tensorboard pod mounts the GCP service accounts and can access to GCS.

const pod = {
kind: 'Pod',
metadata: {
generateName: 'tensorboard-',
},
spec: {
containers: [{
args: [
'tensorboard',
'--logdir',
logdir,
],
image: 'tensorflow/tensorflow',
name: 'tensorflow',
ports: [{
containerPort: 6006,
}],
env: [{
name: 'GOOGLE_APPLICATION_CREDENTIALS',
value: '/secret/gcp-credentials/user-gcp-sa.json'
}],
volumeMounts: [{
mountPath: '/secret/gcp-credentials',
name: 'gcp-credentials',
}],
}],
volumes:[{
name: 'gcp-credentials',
secret:{
secretName: 'user-gcp-sa',
},
}],
},
};

The credential should be a configurable parameter that user specifies, to read data from various storage, S3, PV, etc.

@Jeffwan
Copy link
Member

Jeffwan commented May 7, 2019

@IronPan

Any idea how could we improve this manifest? The most straightforward way is check logdir protocol?

  1. for gcs, s3 and minio, pod can mount cloud provider specific environment and secrets
  2. for local disk, we need pvc name and mountPath?

@sarahmaddox
Copy link
Contributor

@IronPan Can we close this issue, after the merge of the above PRs? We have a note in the docs that we can remove when this issue and #1700 are closed.

@IronPan
Copy link
Member Author

IronPan commented Oct 23, 2019

/close

@k8s-ci-robot
Copy link
Contributor

@IronPan: Closing this issue.

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@IronPan
Copy link
Member Author

IronPan commented Oct 23, 2019

@sarahmaddox thanks! close it for now

Linchin pushed a commit to Linchin/pipelines that referenced this issue Apr 11, 2023
…ubeflow#338)

* Add a playbook and describe how to deal with the CI infrastructure running
  out of GCP quota.

* The cron/batch job for the CI system should not be pinned to checkout
  the code at PR 300; we should be using master.

* We are seeing socket errors contacting the DM service so add some retries
  and in the event of permanent failure try to keep going.

Related to: kubeflow#337
magdalenakuhn17 pushed a commit to magdalenakuhn17/pipelines that referenced this issue Oct 22, 2023
* Add Alibi Anchors Image Explanation

* Update explainers for tabular, text and image

* add spacy to setup.py

* Reformat code

* Fix lint errors

* Fix lint errors

* initial commit

* remove notebook checkpoint

* Updates from testing Anchor Text

* Update moviesentiment README for local training

* Updates for income explainer

* test for anchor images

* test for anchor images - missing updates

* Updates for new storageUri

* Add Route for Explainer

* Add Seldon predict path formats

* Fix protocol check

* Updates from testing

* Update Docker file to use alibi master and allow tftensor payloads for seldon

* remove logging from kgserving seldon

* Add anchor text config

* Allow custom config of explainers

* Move Alibi demos to subfolder

* updates from review

* Fix lint errors

* Fix lint errors

* Update docs

* change explainer errors on validation

* abstract Defaults for endpointSpec

* Add Explainer Test

* Fix lint errors

* clean up code logging

* replace default image patch for controler to gcr

* Fix lint errors

* Fix lint errors

* Fix hostnames in explanation samples

* Add docs links to Alibi
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this issue Mar 11, 2024
* KFP 1.0.3 Rebase

* comment out line 130-142 in metrics_reporter.go (not supported in Tekton)

* fix merge conflicts in metrics_reporter.go#readNodeMetricsJSONOrEmpty()

* remove OWNERS file

* include changes from KFP 1.0.4
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

8 participants