I hereby claim:
- I am aweiteka on github.
- I am aweiteka (https://keybase.io/aweiteka) on keybase.
- I have a public key whose fingerprint is 04AA 2FAA 4762 69AB 3407 FA45 FD5E B4DB 4807 17ED
To claim this, I am signing this object:
| #!/bin/sh -e | |
| yum install -y git | |
| mkdir -p $GOPATH/src/github.com/GoogleCloudPlatform/ | |
| cd $GOPATH/src/github.com/GoogleCloudPlatform/ | |
| git clone https://github.com/GoogleCloudPlatform/kubernetes.git | |
| cd kubernetes | |
| hack/test-go.sh | |
| # TODO: upstream end-to-end tests |
| package main | |
| import "fmt" | |
| import "encoding/json" | |
| import "os" | |
| import "io/ioutil" | |
| import "path/filepath" | |
| import "github.com/ghodss/yaml" | |
| const openshiftApiVer = "v1beta1" |
| #!/bin/bash | |
| # curl -v $hostname/<path> --key /etc/pki/entitlement/<id>-key.pem --cert /etc/pki/entitlement/<id>.pem --cacert cert.crt | |
| # docker pull calls | |
| #/v1/_ping | |
| #/v1/repositories/acme/app/images | |
| #/v1/repositories/acme/app/tags | |
| # these are all redirects | |
| #/v1/images/5f28cecd443d0503f9350f690ae6896b3e18e6c8ae59e9556b6ac157180b61e7/ancestry |
I hereby claim:
To claim this, I am signing this object:
| { | |
| "kind": "Template", | |
| "apiVersion": "v1", | |
| "metadata": { | |
| "name": "automated-build", | |
| "creationTimestamp": null, | |
| "annotations": { | |
| "description": "An OpenShift v3 template that sets up an automated build pipeline for building docker images from Dockerfile. Assumes the base FROM image has been created as an ImageStream.", | |
| "provider": "[email protected]" | |
| } |
There is no standard application installation technology for linux like MSI for Windows. Projects are increasingly turning to Ansible and Heat for installing their distributed applications. However there is no standard way to distribute ansible playbooks or heat templates outside of Github or RPM.
Joe is relatively new to his job. He has been contributing to a new service in the Flubber project and was asked to create a container for it. His container integrates with the "Bounce" service. He's been pulling the flubber/bounce image anonomously from an internal Docker registry but didn't know anything else about the registry. He tried to push to the registry the image he was working on but got 401 Unauthorized. Curious, he loaded the registry URL in the browser and was redirected to a login page. His corporate single sign-on credentials worked!
He browsed a huge, flat list of images but it was too big to sort through. He noticed a filter field and typed "flu". A dynamic list of all of the "flubber" images was displayed. He clicked the Flubber project link and noticed a list of project admins. He recognized Amy's name and sent her an email asking how to get his image pushed into the registry.
While he waited to hear back from Amy he decided to try creating his own project to put hi
| #!/bin/bash | |
| # start all-in-one container | |
| sudo docker run -it --name "origin" --privileged --pid=host --net=host -v /:/rootfs:ro -v /var/run:/var/run:rw -v /sys:/sys -v /var/lib/docker:/var/lib/docker:rw -v /var/lib/origin/openshift.local.volumes:/var/lib/origin/openshift.local.volumes -v `pwd`/config/:/var/lib/origin/openshift.local.config:Z --entrypoint bash openshift/origin | |
| # gen config | |
| openshift start --write-config=./openshift.local.config | |
| # edit config | |
| #sudo vim config/master/master-config.yaml |
| oauthConfig: | |
| assetPublicURL: https://localhost:8443/console/ | |
| grantConfig: | |
| method: auto | |
| identityProviders: | |
| - name: github | |
| challenge: false | |
| login: true | |
| mappingMethod: claim | |
| provider: |