paulstack.co.uk Report : Visit Site

Technical data of the paulstack.co.uk

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host paulstack.co.uk. Currently, hosted in Netherlands and its service provider is Digital Ocean Inc. .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called WEBrick/1.3.1 (Ruby/2.0.0/2015-12-16) containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

ranting within rss about me blog contact details archives building an autodiscovering apache zookeeper cluster in aws using packer, ansible and terraform jan 15 th , 2016 following my pattern of building amis for applications, i create my apache zookeeper cluster with packer for my ami and terraform for the infrastructure. this zookeeper cluster is auto-discovering of the other nodes that are determined to be in the cluster building zookeeper amis with packer the packer template looks as follows: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 { "variables" : { "ami_id" : "" , "private_subnet_id" : "" , "security_group_id" : "" , "packer_build_number" : "" , }, "description" : "zookeeper image" , "builders" : [ { "ami_name" : "zookeeper-{{user `packer_build_number`}}" , "availability_zone" : "eu-west-1a" , "iam_instance_profile" : "app-server" , "instance_type" : "t2.small" , "region" : "eu-west-1" , "run_tags" : { "role" : "packer" }, "security_group_ids" : [ "{{user `security_group_id`}}" ], "source_ami" : "{{user `ami_id`}}" , "ssh_timeout" : "10m" , "ssh_username" : "ubuntu" , "subnet_id" : "{{user `private_subnet_id`}}" , "tags" : { "name" : "zookeeper-packer-image" }, "type" : "amazon-ebs" } ], "provisioners" : [ { "type" : "shell" , "inline" : [ "sleep 10" ] }, { "type" : "shell" , "script" : "install_dependencies.sh" , "execute_command" : "echo '' | {{ .vars }} sudo -e -s sh '{{ .path }}'" }, { "type" : "ansible-local" , "playbook_file" : "zookeeper.yml" , "extra_arguments" : [ "--module-path=./modules" ], "playbook_dir" : "../../" } ] } the install_dependencies.sh script is as described previously the ansible playbook for zookeeper looks as follows: 1 2 3 4 5 6 7 8 9 10 11 - hosts : all sudo : yes pre_tasks : - ec2_tags : - ec2_facts : roles : - base - zookeeper - exhibitor the base playbook installs a base role for all the base pieces of my system (e.g. logstash, sensu-client, prometheus node_exporter) and then proceeds to install zookeeper. as a last step, i install exhibitor . exhibitor is a co-process for monitoring, backup/recovery, cleanup and visualization of zookeeper. the zookeeper ansible role looks as follows: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 - name : download zookeeper get_url : url=http://www.mirrorservice.org/sites/ftp.apache.org/zookeeper/current/zookeeper-{{ zookeeper_version }}.tar.gz dest=/tmp/zookeeper-{{ zookeeper_version }}.tar.gz mode=0440 - name : unpack zookeeper command : tar xzf /tmp/zookeeper-{{ zookeeper_version }}.tar.gz -c /opt/ creates=/opt/zookeeper-{{ zookeeper_version }} - name : link to zookeeper directory file : src=/opt/zookeeper-{{ zookeeper_version }} dest=/opt/zookeeper state=link force=yes - name : create zookeeper group group : name=zookeeper system=true state=present - name : create zookeeper user user : name=zookeeper groups=zookeeper system=true home=/opt/zookeeper - name : create zookeeper config dir file : path={{zookeeper_conf_dir}} owner=zookeeper group=zookeeper recurse=yes state=directory mode=0644 - name : create zookeeper transations dir file : path=/opt/zookeeper/transactions owner=zookeeper group=zookeeper recurse=yes state=directory mode=0644 - name : create zookeeper log dir file : path={{zookeeper_log_dir}} owner=zookeeper group=zookeeper recurse=yes state=directory mode=0644 - name : create zookeeper datastore dir file : path={{zookeeper_datastore_dir}} owner=zookeeper group=zookeeper recurse=yes state=directory mode=0644 - name : setup log4j template : dest="{{zookeeper_conf_dir}}/log4j.properties" owner=root group=root mode=644 src=log4j.properties.j2 the role itself is very simple. the zookeeper cluster is managed by exhibitor so there are very few settings passed to zookeeper at this point. one thing to note though, this requires an installation of the java jdk to work. the exhibitor playbook looks as follows: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 - name : install maven apt : pkg=maven state=latest update_cache=yes - name : create exhibitor install dir file : path={{ exhibitor_install_dir }} state=directory mode=0644 - name : create exhibitor build dir file : path={{ exhibitor_install_dir }}/{{ exhibitor_version }} state=directory mode=0644 - name : create exhibitor pom template : src=pom.xml.j2 dest={{ exhibitor_install_dir }}/{{ exhibitor_version }}/pom.xml - name : build exhibitor jar command : '/usr/bin/mvn clean package -f {{ exhibitor_install_dir }}/{{ exhibitor_version }}/pom.xml creates={{ exhibitor_install_dir }}/{{ exhibitor_version }}/target/exhibitor-{{ exhibitor_version }}.jar' - name : copy exhibitor jar command : 'cp {{ exhibitor_install_dir }}/{{ exhibitor_version }}/target/exhibitor-{{ exhibitor_version }}.jar {{exhibitor_install_dir}}/exhibitor-standalone-{{ exhibitor_version }}.jar creates={{exhibitor_install_dir}}/exhibitor-standalone-{{ exhibitor_version }}.jar' - name : exhibitor properties config template : src=exhibitor.properties.j2 dest={{ exhibitor_install_dir }}/exhibitor.properties - name : exhibitor upstart config template : src=upstart.j2 dest=/etc/init/exhibitor.conf mode=644 owner=root - service : name=exhibitor state=started this role has a lot more configuration to set as it essentially manages zookeeper. the template files for configuration are all available to download. the variables for the entire playbook look as follows: 1 2 3 4 5 6 7 8 9 zookeeper_hosts : ":2181" zookeeper_version : 3.4.6 zookeeper_conf_dir : /etc/zookeeper/conf zookeeper_log_dir : /var/log/zookeeper zookeeper_datastore_dir : /var/lib/zookeeper zk_s3_bucket_name : "mys3bucket" monasca_log_level : warn exhibitor_version : 1.5.5 exhibitor_install_dir : /opt/exhibitor the main thing to note here is that the exhibitor process starts with the following configuration: 1 exec java -jar {{ exhibitor_install_dir }} /exhibitor-standalone- {{ exhibitor_version }} .jar --port 8181 --defaultconfig /opt/exhibitor/exhibitor.properties --configtype s3 --s3config {{ zk_s3_bucket_name }} : {{ ansible_ec2_placement_region }} --s3backup true --hostname {{ ec2_private_ip_address }} > /var/log/exhibitor.log 2>&1 this means that the node will check itself into a configuration file in s3 and that all other zookeepers will read the same configuration file and can form the cluster required. you can read more about exhibitor shared configuration on their github wiki . when i launch the instances now, the zookeeper cluster will be formed deploying zookeeper infrastructure with terraform the infrastructure of the zookeeper cluster is pretty simple: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 resource "aws_security_group" "zookeeper" { name = "digit-zookeeper-sg" description = "zookeeper security group" vpc_id = "${aws_vpc.default.id}" ingress { from_port = 0 to_port = 0 protocol = "-1" cidr_blocks = [ "0.0.0.0/0" ] } egress { from_port = "0" to_port = "0" protocol = "-1" cidr_blocks = [ "0.0.0.0/0" ] } tags { name = "zookeeper node" } } resource "aws_launch_configuration" "zookeeper_launch_config" { image_id = "${var.zookeeper_ami_id}" instance_type = "${var.zookeeper_instance_type}" iam_instance_profile = "zookeeper-server" key_name = "${aws_key_pair.terraform.key_name}" security_groups = [ "${aws_security_group.zookeeper.id}" , "${aws_security_group.node.id}" ] enable_monitoring = false lifecycle { create_before_destroy = true } root_block_device { volume_size = "${var.digit_zookeeper_volume_size}" } } resource "aws_autoscaling_group" "zookeeper_autoscale_group" { name = "zookeeper-autoscale-group" availability_zones = [ "${aws_subnet.primary-private.availability_zone}" , "${aws_subnet.secondary-private.availability_zone}" , "${aws_subnet.tertiary-private.availability_zone}" ] vp

URL analysis for paulstack.co.uk

http://www.paulstack.co.uk/gist%20goes%20here
http://www.paulstack.co.uk/blog/2016/01/15/replacing-a-node-in-a-riak-cluster/
http://www.paulstack.co.uk/blog/2016/01/06/building-a-riak-cluster-in-aws-with-packer-and-terraform/
http://www.paulstack.co.uk/blog/2016/01/15/building-an-autodiscovering-apache-zookeeper-cluster-in-aws-using-packer-ansible-and-terraform/
http://www.paulstack.co.uk/blog/2016/01/04/replacing-the-nodes-in-an-aws-elasticsearch-cluster/
http://www.paulstack.co.uk/atom.xml
http://www.paulstack.co.uk/blog/2015/11/09/the-quest-for-infra-management-2-dot-0/
http://www.paulstack.co.uk/blog/2015/11/09/the-quest-for-infra-management-2-dot-0/
http://www.paulstack.co.uk/blog/2015/12/30/autoscaling-group-notifications-with-terraform-and-aws-lambda/
http://www.paulstack.co.uk/about-me
http://www.paulstack.co.uk/contact
http://www.paulstack.co.uk/blog/2016/01/02/building-an-elasticsearch-cluster-in-aws-with-packer-and-terraform/
http://www.paulstack.co.uk/blog/2016/01/06/building-a-riak-cluster-in-aws-with-packer-and-terraform/
http://www.paulstack.co.uk/blog/page/2/
http://www.paulstack.co.uk/blog/2016/01/04/replacing-the-nodes-in-an-aws-elasticsearch-cluster/

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain name:
paulstack.co.uk

Data validation:
Nominet was able to match the registrant's name and address against a 3rd party data source on 23-Aug-2015

Registrar:
eNom LLC [Tag = ENOM]
URL: http://www.enom.com

Relevant dates:
Registered on: 05-Aug-2009
Expiry date: 05-Aug-2019
Last updated: 04-Aug-2018

Registration status:
Registered until expiry date.

Name servers:
ns1.dnsimple.com
ns2.dnsimple.com
ns3.dnsimple.com
ns4.dnsimple.com

WHOIS lookup made at 00:39:41 30-Aug-2018

--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:

Copyright Nominet UK 1996 - 2018.

You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REFERRER http://www.nominet.org.uk

  REGISTRAR Nominet UK

SERVERS

  SERVER co.uk.whois-servers.net

  ARGS paulstack.co.uk

  PORT 43

  TYPE domain

DOMAIN

SPONSOR
eNom LLC [Tag = ENOM]
URL: http://www.enom.com
Relevant dates:

  CREATED 05-Aug-2009

  CHANGED 04-Aug-2018

STATUS
Registered until expiry date.

NSERVER

  NS1.DNSIMPLE.COM 162.159.24.4

  NS2.DNSIMPLE.COM 162.159.25.4

  NS3.DNSIMPLE.COM 162.159.26.4

  NS4.DNSIMPLE.COM 162.159.27.4

  NAME paulstack.co.uk

DISCLAIMER
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2018.
You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REGISTERED no

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .