feelobot

About

Script that ingests ``*.robot` files and either outputs the json to the screen or uploads the data to the JAMA API

Config

1. Create an API Token, Click Username in GUI -> Set API Credentils -> Create API Credentials (or use an existing credential)
2. set the following ENVS: * JAMA_CLIENT_ID (created above) * JAMA_CLIENT_SECRET (created above)

feelobot

rules:
  # The following requests were manually identified as high-volume and low-risk,
  # so drop them.
  - level: None
    users: ["system:kube-proxy"]
    verbs: ["watch"]
    resources:
      - group: "" # core
        resources: ["endpoints", "services"]
  - level: None

feelobot

# clusters refers to the remote service.
clusters:
  - name: name-of-remote-authn-service
    cluster:
      certificate-authority: ""
      server: http://logs-01.loggly.com/bulk/42c2afa6-ebe9-4a0f-968e-e973b2223e73/tag/bulk/

# users refers to the API server's webhook configuration.
users:
  - name: name-of-api-server

feelobot

E0825 10:53:43.259870       1 runtime.go:52] Recovered from panic: "invalid memory address or nil pointer dereference" (runtime error: invalid memory address or nil pointer dereference)
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/util/runtime/runtime.go:58
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/util/runtime/runtime.go:51
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/util/runtime/runtime.go:41
/usr/local/go/src/runtime/asm_amd64.s:472
/usr/local/go/src/runtime/panic.go:443
/usr/local/go/src/runtime/panic.go:62
/usr/local/go/src/runtime/sigpanic_unix.go:24
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/pkg/client/unversioned/clientcmd/config.go:342
/go/src/k8s.io/kubernetes/_output/dockerized/go/src/k8s.io/kubernetes/plugin/pkg/client/auth/gcp/gcp.go:101

feelobot

```
user FELIX has entered room

analyst CEILO has entered room

CEILO: Hello FELIX_, Thank you for contacting Comcast Live Chat Support. My name is CEILO. Please give me one moment to review your information.

CEILO: Welcome to Comcast! I'd be more than happy to assist you! You can call me Cei. How's your day going?

FELIX: im doing well and yourself?

feelobot

Running a Rancher Server

docker pull rancher/server && docker run -d --restart=always -p 8080:8080 rancher/server

I used a coreos machine to have docker installed already, I used https://coreos.com/docs/cluster-management/setup/switching-channels/ to help me update it to a new version.

Running a Rancher Agent on a Host

sudo docker run -e CATTLE_AGENT_IP=IP_OF_HOST -d --privileged -v /var/run/docker.sock:/var/run/docker.sock rancher/agent:v0.7.8 HOST_URL /v1/scripts/23FBC72A18294F01194B:1432918800000:RANCHER_TOKEN

feelobot

Micro Services with Docker & Elastic Beanstalk

Summary

So far we have made great strides at moving towards creating more micro services vs monolithic applications. With Docker + Elastic beanstalk we are pushing the boundries and setting a trend for future compaines to follow. As more people use these tools we will continue to discover new challenges. One challenge we began to see immediately was how to deploy these microservices.

Deploying

feelobot

Setup

1. Make a new rails app and initilize through git

$ chruby 2.0.0
$ gem install rails
$ rails new myapp ~/src
$ cd ~/src/myapp
$ git init

1. Install elastic beanstalk command line tools and initialize

feelobot

Once this is included in your project you can use

Helper.find_web_element("div#ad_banner")

If if does not work then the element does not exist. I am sure the code can be cleaned up but this is how I managed to solve my issues with hybrid app testing.