mmgaggle

#!/bin/bash

usage() {
  cat << EOF

Generate an OCS Provider/Consumer onboarding ticket to STDOUT
USAGE: $0 [-h]

EOF
}

mmgaggle

_CUDA_COMPAT_STATUS=CUDA Driver UNAVAILABLE (cuInit(0) returned 100)
NVIDIA_PYTORCH_VERSION=19.05
MOFED_VERSION=4.4-1.0.0
COCOAPI_VERSION=2.0+nv0.3.1
CUDNN_VERSION=7.6.0.64
HOSTNAME=ssd
DATADIR=/ocs-ml-data/coco
NVIDIA_REQUIRE_CUDA=cuda>=5.0
KUBERNETES_PORT=tcp://172.30.0.1:443
KUBERNETES_PORT_443_TCP_PORT=443

mmgaggle

Kyles-Mac-mini:infra-nodes kylebader$ oc logs -f ssd
_CUDA_COMPAT_STATUS=CUDA Driver UNAVAILABLE (cuInit(0) returned 100)
NVIDIA_PYTORCH_VERSION=19.05
MOFED_VERSION=4.4-1.0.0
COCOAPI_VERSION=2.0+nv0.3.1
CUDNN_VERSION=7.6.0.64
HOSTNAME=ssd
DATADIR=/ocs-ml-data/coco
NVIDIA_REQUIRE_CUDA=cuda>=5.0
KUBERNETES_PORT_443_TCP_PORT=443

mmgaggle

Red Hat Ceph Storage 3.x

Performance and Sizing Guides

• Micron® 9300 MAX NVMe™ SSDs + Red Hat® Ceph® Storage for 2nd Gen AMD EPYC™ Processors
• Micron® 7300 MAX NVMe™ SSDs + Red Hat® Ceph® Storage for 2nd Gen AMD EPYC™ Processors
• Dell EMC Ready Architecture for Red Hat Ceph Storage 3.2 Cost Optimized Block Storage Architecture Guide
• Red Hat Ceph Storage on Dell EMC servers Object storage performance and sizing guide
• [Dell EMC Ready Architecture for Red Hat Ceph Storage 3.2 Performance Optimized Block Storage Architecture Guide](https://www.delle

mmgaggle

Edit /usr/lib/python2.7/site-packages/blivet/arch.py. Modify isMactel() function to always return False

mmgaggle

Extend Cinder Volume Type QoS Functionality
===========================================

AWS EBS provides a deterministic number of IOPS based on the capacity of the
provisioned volume with Provisioned IOPS. Similarly, the newly announced
throughput optimized volumes provide deterministic throughput based on the
capacity of the provisioned volume. Cinder should, in addition to current per
volume maximums, be able to set lower qos limits based on the provisioned
capacity.

mmgaggle

QoS for clouds

* The universal scalability law applies to you, too.
* The x value shifts to the left, when you have a failure (less capacity)
* the y value shifts up when you have a failure (recovery is effectively a client workload)
* Thus, you need to be below the point of contention to avoid service degradation upon failure.
* To capacity plan for adversarial workloads, provided throughput/iops needs to be a function
  tied to the amount of provisioned storage.
* Total throughput per unit of storage should be derived from a value far enough below the point
  of contention to compensate for failures.

mmgaggle

[client]

socket=/mnt/mysql/mysql.sock

[server]

table_open_cache = 512

thread_cache = 512

mmgaggle

-->
--> ==== interactive mode ====
-->
--> follow the prompts to complete the interactive mode
--> if specific actions are required (e.g. just install Calamari)
--> cancel this script with Ctrl-C, and see the help menu for details
--> default values are presented in brackets
--> press Enter to accept a default value, if one is provided
--> do you want to continue?
--> this script will setup Calamari, package repo, and ceph-deploy

mmgaggle

#!/usr/local/bin/Rscript

printf <- function(...) invisible(print(sprintf(...)))

filenames <- list.files("./",pattern="output*",full.names=TRUE)
files <- lapply(filenames, function(filename){ read.csv(file=filename,sep=';',stringsAsFactors=FALSE,skip=4) })
post_ramp_subsets <- lapply(files, function(file) { subset(file,file[50]>=60000) })
thread_iops_means <- lapply(post_ramp_subsets, function(thread_subset) {
  threads <- unique(thread_subset[,3])
  thread_subsets <- lapply(threads, function(thread){ subset(thread_subset,thread_subset[,3]==thread) })