Status aggregation is complicated, but I guess we have to start with built-in policies.
I'm not sure what "alive" means to an Service
tho, when there's "ready"... Does the policy apply to both?
type StatusPolicy string
const (
#!/usr/bin/env bash | |
# Resizing a vagrant centos disk... the hard way | |
set -o errexit | |
set -o nounset | |
set -o pipefail | |
set -o xtrace | |
vagrant up |
$ KUBECONFIG=~/.kube/config ./hack/conformance-test.sh -ginkgo.dryRun -ginkgo.randomizeAllSpecs=false | |
Conformance test using current-context of /Users/karl/.kube/config | |
Conformance test run date:Mon Nov 30 16:21:19 PST 2015 | |
Conformance test SHA:e7a2d3090f83bc0860d8c64945e9986c453a003e | |
Conformance test version tag(s): | |
Conformance test checking conformance with Kubernetes version 1.0 | |
Conformance test: not doing test setup. | |
I1130 16:21:20.178892 96376 e2e_test.go:106] The --provider flag is not set. Treating as a conformance test. Some tests may not be run. | |
Nov 30 16:21:20.180: INFO: >>> testContext.KubeConfig: /Users/karl/.kube/config |
0. Install DCOS & DCOS CLI | |
> Install DCOS Community Edition: https://mesosphere.com/product/ | |
> Follow directions from DCOS dashboard to install dcos-cli | |
1. Install Frameworks w/ DCOS CLI | |
dcos config prepend package.sources https://github.com/mesosphere/multiverse/archive/version-1.x.zip | |
dcos package update --validate | |
cat >/tmp/cassandra.json <<EOF |
#!/usr/bin/env bash | |
set -e | |
set -o nounset | |
KUBE_UI=$(dcos kubectl cluster-info | grep "KubeUI" | cut -d " " -f 5 | sed -e 's,/api,/service/kubernetes/api,') | |
KUBE_UI=$(echo $KUBE_UI | sed $'s,\x1b\\[[0-9;]*[a-zA-Z],,g') | |
#echo $KUBE_UI | |
OINKER=$(echo $KUBE_UI | sed -e 's/kube-system/default/' | sed -e 's/kube-ui/oinker/') | |
#echo $OINKER |
$ ./cluster/test-smoke.sh | |
Testing cluster with provider: mesos/docker | |
Running e2e tests: | |
./hack/ginkgo-e2e.sh -ginkgo.focus=Guestbook.application | |
Setting up for KUBERNETES_PROVIDER="mesos/docker". | |
TODO: prepare-e2e | |
KUBE_MASTER_IP: 172.17.0.17:6443 | |
>>> testContext.KubeConfig: /Users/karl/.kube/config | |
Sep 23 13:20:08.027: INFO: Waiting up to 10m0s for all pods (need at least 0) in namespace 'kube-system' to be running and ready | |
Sep 23 13:20:13.059: INFO: 2 / 2 pods in namespace 'kube-system' are running and ready (5 seconds elapsed) |
$ docker-compose -f "${provider_root}/docker-compose.yml rm -f | |
Removing docker_scheduler_1... | |
Removing docker_mesosslave1_1... | |
Removing docker_mesosslave2_1... | |
Removing docker_controller_1... | |
Removing docker_keygen_1... | |
Removing docker_apiserver_1... | |
Removing docker_mesosmaster1_1... | |
Removing docker_etcd_1... | |
Removing docker_ambassador_1... |
#!/usr/bin/env bash | |
hours=$1 | |
script_dir="$(cd "$(dirname "${BASH_SOURCE}")" && pwd)" | |
drive_mount="$(cd "${script_dir}/.." && pwd)" | |
key_path="${script_dir}/id_rsa" | |
if [ -z ${hours} ]; then | |
hours=1 | |
fi |
Kubernetes repo analyzed with gitm.
git log --numstat --no-merges | ~/workspace/gitdm/gitdm -u -s -a -n -o results -b ~/workspace/gitdm -l 25
Source tree analysis includes generated, third-party, and vendored dependency files.
--- | |
name: mesos | |
director_uuid: 737bd8ee-f4f9-4aec-9b82-80f3d0be26f1 | |
releases: | |
- name: mesos | |
version: latest | |
compilation: | |
workers: 8 |