kshailen

#Suppose both files are presenen in functionalTest directory. There is following way to run context on this.

#Method 1
[root@marx-vagrant-setup coreos-vagrant]# run-contexts functionalTest
10
.....
----------------------------------------------------------------------
PASSED!
2 contexts, 3 assertions
(0.2 seconds)

kshailen

#Go to the directory where you have put this docker file.
cd <Path to the DockerFile>

# Run following to build an docker image
docker build -t go-container .

#Check image by using docker images. It will show like this.

shailendra-kumar:Docker shailendra.kumar$ docker images
REPOSITORY          TAG                 IMAGE ID            CREATED             SIZE

kshailen

1.Test procedure   
A- Take cluster of 3 etcd noses as shown below
	core@core-02 ~ $ etcdctl cluster-health
	member 348dd9a63bc9c9d3 is healthy: got healthy result from http://172.17.8.102:2379
	member 7d26e3d2ee11a98e is healthy: got healthy result from http://172.17.8.103:2379
	member 95d2e7af71fc961d is healthy: got healthy result from http://172.17.8.101:2379
	cluster is healthy
	core@core-02 ~ $ etcdctl member list
	348dd9a63bc9c9d3: name=219d42232433483c8ad19163ba1c6020 peerURLs=http://172.17.8.102:2380 clientURLs=http://172.17.8.102:2379 isLeader=true
	7d26e3d2ee11a98e: name=edbfd19500b0496485e286801bdfa04b peerURLs=http://172.17.8.103:2380 clientURLs=http://172.17.8.103:2379 isLeader=false

kshailen

Other way of intracting with ETCD is HTTP/JSON API.

Etcd HTTP/JSON API Usage
The other way to interacting with etcd is with the simple HTTP/JSON API.

To access the API, you can use a simple HTTP program like curl. You must supply the -L flag to follow any redirects that are passed back. From within your cluster, you can use the local 127.0.0.1 interface and port 4001/2379 for most queries.


The normal keyspace can be reached by going to http://127.0.0.1:4001/v2/keys/ on any of the host machines. For instance, to get a listing of the top-level keys/directories, type:

kshailen

##################### ElasticSearch Configuration Example #####################

# This file contains an overview of various configuration settings,
# targeted at operations staff. Application developers should
# consult the guide at <http://elasticsearch.org/guide>.
#
# The installation procedure is covered at
# <http://elasticsearch.org/guide/en/elasticsearch/reference/current/setup.html>.
#
# ElasticSearch comes with reasonable defaults for most settings,

kshailen

name: ${HOSTNAME}

# The cluster should be named with the name of the AD domain
cluster:
  name: bldrprod-0.14.0
  routing:
    allocation:
      # As small as possible, very large performance hits during recovery
      concurrent_recoveries: 1

kshailen

#!/bin/bash

#Check for paas-cluster-manager
HOST=`fleetctl list-units | grep paas-cluster-manager| grep -w active | grep running |head -1 | awk '{print $2}' | awk -F"/" '{print $NF}'`


if [ -z $HOST ]then
    echo "paas-cluster-manager is not running in this Cluster"
    exit 1

kshailen

import requests
import json
import os
import subprocess
import skycommon


class When_getting_machine_list_from_fleet_and_comparing_with_elastic_machine_list:

    def __init__(self):

kshailen

When it comes to databases and AWS VPC, best practice is to place your database in private subnet. By definition, private subnet in AWS is not reachable from the Internet because no Internet gateway is attached to private subnet. This is the way you protect your data. This kind of configuration is good for security but bad for data management.

How can you easily access and manage your secured data?

There are two basic ways to acees it.

1. Access postgres RDS from bastion host. There are following requirements for this.

kshailen

import boto3
print(boto3.client('sts').get_caller_identity()['Account'])