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.

Sign up for GitHub

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

Jump to bottom

Can not use NFS volume for Tensorboard logs #708

Closed
SinaChavoshi opened this issue Jan 20, 2019 · 2 comments
Closed

Can not use NFS volume for Tensorboard logs #708

SinaChavoshi opened this issue Jan 20, 2019 · 2 comments
Assignees
@IronPan

Comments

@SinaChavoshi
Copy link
Contributor

I don't seem to be able to use an NFS mount as a source for the tensorboard data. Currently the only option seems to be to copy the data to a GCS bucket however this is a blocker for on prem deployment.

Also related to #489 and #699
@IronPan
Copy link
Member

IronPan commented Jan 20, 2019

Agreed. We plan to use PersistentVolume to decouple actual storage from the artifact store. I will send out a proposal publicly soon.

@jinchihe jinchihe mentioned this issue Jan 23, 2019
Closed
@vicaire
Copy link
Contributor

vicaire commented Mar 26, 2019

Resolving in favor of related issues. Please re-open if needed.

@vicaire vicaire closed this as completed Mar 26, 2019
HumairAK pushed a commit to red-hat-data-services/data-science-pipelines that referenced this issue Mar 11, 2024
@Tomcli
Remove containerOp for pipelineparam and raw input samples (kubeflow#708
386ad23 
)

* remove containerOp for pipelineparam and raw input samples

* fix-typo
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@IronPan IronPan

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@IronPan @SinaChavoshi @vicaire