Changes

Tensorboard is a monitoring tool for machine learning training, which provides a web browser interface on a port of the server (6116 in our cluster). Each compute node has its own instance of Tensorboard running, which is thus exported exposed on node-addressdomain:6116. Tensorboard parses the content of a particular directory of the node, which . Subdirectories can be mounted as a certain the persistent volume storage class"local-tensorboard" and used to write logs.

TODO: following was copy/pasted === Local persistent volumes for reference, finish tutorial page.Tensorboard logging ===

A The following obtains a persistent volume in Kubernetes is a cluster resource which can be requested by a container. For this, you have to claim for a persistent volume (local PV) using a persistent volume claim (PVC), which you apply in your namespace. The persistent volume claim can then be mounted to directories within a container. The important point is that the PVC survives the end of the container, i.e. the for data in the PV will be permanent until the PVC is released. If the PVC is mounted again to a new containerstorage, the data will still be present. A persistent volume which is bound to as well as a claim can not be assigned to any other claim. '''If the PVC is released, the PV is also released and immediately and automatically wiped clean of all data'''. If you want to keep your data, copy it to some other permanent storage first. On the cluster, there are two types of persistent volumes currently configured:* Local persistent volumes* Host directoriesLocal persistent volumes should be used to import training data and store results and log files of your training. There are special PVs for monitoring the training using Tensorboardlogging. Host directories are meant for common training data sets stored permanently on the host. They are always read only.  === Local persistent volumes === These are persistent volumes which are mapped to special folders of the host filesystem of the node. Each node exposes several persistent volumes which Note that both can be claimed. The user can not control exactly which volume is bound to done with a claim, but can request a minimum size. A persistent volume claim for a local PV is configured like thissingle config file. Code examples can be found in the subdirectory "kubernetes/example_2example_3" of the tutorial sample code, [[File:Kubernetes_samples.zip|Kubernetes samples]].

name: your-username-tf-mnist-pvc

# the requested storage class, see tutorialhere is fast data storage.

The following spec: resources: requests: # Tensorboard logging typically requires not that much storage. storage classes are configured in the cluster:2Gi

 Remember to prepend names with your username to make them unique. When the claim is defined to your satisfaction, apply it like this:

You can again check on the status of this (and every other) claim:

NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGEtf-mnist-pvc Pending local-ssd 11stf-mnist-tb-pvc Pending local-ssd tensorboard 11s