기본 콘텐츠로 건너뛰기

2018의 게시물 표시

Ceph Storage Pros, Cons

Pros Highly resilient, almost every time we attempted to destroy the cluster it was able to recover from a failure. It struggled to when the nodes where down to about 30%(3 replicas on 10 nodes) The cache tiering feature of Ceph is especially nice. We attached solid state disks and assigned them as the cache tier. Our sio benchmarks beat the our Netapp when we benchmarked it years ago (no traffic, clean disks) by a very wide margin. Ceph effectively allows the admin to control the entire stack from top to bottom instead of being tied to any one storage vendor. The cluster can be decentralized and replicated across data centers if necessary although we didn't try that feature ourselves, it gave us some ideas for a disaster recovery solution. We really liked the idea that since we control the hardware and the software, we have infinite upgradability with off the shelf parts which is exactly what it was built for. Cons Ceph is very difficult to set up when we use...

kubeflow install

# Create a namespace for kubeflow deployment NAMESPACE=kubeflow kubectl create namespace ${NAMESPACE} # Initialize a ksonnet app. Set the namespace for it's default environment. APP_NAME=kf-j2m ks init ${APP_NAME} cd ${APP_NAME} ks env set default --namespace ${NAMESPACE} # Install Kubeflow components ks registry add kubeflow github.com/kubeflow/kubeflow/tree/master/kubeflow ks pkg install kubeflow/core ks pkg install kubeflow/tf-serving ks pkg install kubeflow/tf-job ks env add nocloud KF_ENV=nocloud ks env set ${KF_ENV} --namespace ${NAMESPACE} # Create templates for core components # ks generate kubeflow-core kubeflow-core ks generate core kubeflow-core --name=kubeflow-core ks env add nocloud KF_ENV=nocloud ks env set ${KF_ENV} --namespace ${NAMESPACE} # If your cluster is running on Azure you will need to set the cloud parameter. # If the cluster was created with AKS or ACS choose aks, it if was created # with acs-engine, choose acsengine # PLATFO...