FAQ
I have just checked my microbosh with "netstat -ntpl"
tcp 0 0 0.0.0.0:53 0.0.0.0:* LISTEN
      2319/pdns_server

So there should be something listening on port 53.
You could check the logs on of the powerdns job on your microbosh.
On Friday, July 12, 2013 3:47:14 PM UTC+2, Jamie van Dyke wrote:

Okay, so everything is re-deployed and has the correct network name now.
The powerdns records on my microbosh have the correct records in. However I
am unable to nslookup from any host and successfully get info back. Also,
nothing is listening on port 53 (DNS) on my microbosh, although powerdns is
running. Should it be listening there?

How do I debug this, where do I start looking on the hosts? The best I can
think of is to look in my /etc/resolv.conf, which correctly has my
microbosh listed as a name server.
On Friday, 12 July 2013 11:58:20 UTC+1, ferdy wrote:

The DNS record names follow this pattern:
<job-index>.<job-name>.<network-name>.<deployment-name>.<domain_name>. So
at your deployment manifest file you must change the DNS hostnames to match
that pattern, specifically, you must change <deployment-name>, so instead
of 'bosh-ec2' it should say 'bosh', and the <domain_name.>, if you're
deploying from a microBOSH, then it should say 'microbosh'. An example for
postgres should be '0.postgres.default.bosh.microbosh'.

Bonus: if you're using the latest gems, you can use the 'bosh vms --dns'
command, it'll show you the DNS A record for every job.

- Ferdy


2013/7/11 Jamie van Dyke <ja...@fearoffish.com>
I'm working on getting a bosh deployed from a microbosh, on EC2. I'm
using the docs from cloudfoundry, except I'm using the OpenStack version
and converting it to EC2 (drnic assures me the ec2 docs are out of date, so
I'm updating them as I go).

Here's my manifest:

---
name: bosh
director_uuid: cf9b9337-b165-4102-8a24-11f49c6eb3c1 # CHANGE: Director
UUID

release:
name: bosh
version: latest

compilation:
workers: 3
network: default
reuse_compilation_vms: true
cloud_properties:
instance_type: m1.small

update:
canaries: 1
canary_watch_time: 3000-120000
update_watch_time: 3000-120000
max_in_flight: 4
max_errors: 1

networks:
- name: elastic
type: vip
cloud_properties: {}
- name: default
type: dynamic
cloud_properties:
security_groups:
- default # CHANGE: Security Group

resource_pools:
- name: small
network: default
size: 7
stemcell:
name: bosh-stemcell
version: latest
cloud_properties:
instance_type: m1.small

- name: medium
network: default
size: 1
stemcell:
name: bosh-stemcell
version: latest
cloud_properties:
instance_type: m1.medium

jobs:
- name: powerdns
template: powerdns
instances: 1
resource_pool: small
networks:
- name: default
default: [dns, gateway]
- name: elastic
static_ips:
- ELASTIC_IP_!

- name: nats
template: nats
instances: 1
resource_pool: small
networks:
- name: default
default: [dns, gateway]
- name: elastic
static_ips:
- ELASTIC_IP_2

- name: postgres
template: postgres
instances: 1
resource_pool: small
persistent_disk: 2048
networks:
- name: default
default: [dns, gateway]
- name: elastic
static_ips:
- ELASTIC_IP_3

- name: redis
template: redis
instances: 1
resource_pool: small
networks:
- name: default
default: [dns, gateway]
- name: elastic
static_ips:
- ELASTIC_IP_4

- name: director
template: director
instances: 1
resource_pool: medium
persistent_disk: 4096
networks:
- name: default
default: [dns, gateway]
- name: elastic
static_ips:
- ELASTIC_IP_5

- name: blobstore
template: blobstore
instances: 1
resource_pool: small
networks:
- name: default
default: [dns, gateway]
- name: elastic
static_ips:
- ELASTIC_IP_6

- name: registry
template: registry
instances: 1
resource_pool: small
networks:
- name: default
default: [dns, gateway]
- name: elastic
static_ips:
- ELASTIC_IP_7

- name: health_monitor
template: health_monitor
instances: 1
resource_pool: small
networks:
- name: default
default: [dns, gateway]

properties:
nats:
address: 0.nats.default.bosh-ec2.bosh
user: nats
password: nats

redis:
address: 0.redis.default.bosh-ec2.bosh
password: redis

postgres: &bosh_db
host: 0.postgres.default.bosh-ec2.bosh
user: postgres
password: postgres
database: bosh

dns:
address: ELASTIC_IP_1
db: *bosh_db
recursor: MICROBOSH_IP

blobstore:
address: 0.blobstore.default.bosh-ec2.bosh
agent:
user: agent
password: agent
director:
user: director
password: director

director:
name: bosh
address: ELASTIC_IP_5
db: *bosh_db
snapshot_schedule: false
self_snapshot_schedule: false

registry:
address: 0.registry.default.bosh-ec2.bosh
db: *bosh_db
http:
user: registry
password: registry

hm:
http:
user: hm
password: hm
director_account:
user: admin
password: admin
resurrector_enabled: true

ntp:
- 0.north-america.pool.ntp.org
- 1.north-america.pool.ntp.org

aws:
access_key_id: SNIP
secret_access_key: SNIP
default_security_groups: ["default", "ssh", "bosh_registry",
"bosh_blobstore", "bosh_nats_server", "bosh_director", "bosh_agent_http"]
default_key_name: microbosh
ec2_private_key: ~/.ssh/microbosh.pem
region: us-east-1

The error I get when I bosh deploy is:

Error 400007: `director/0' is not running after update

On my director the error seems to be:

/var/vcap/packages/director/gem_home/gems/sequel-3.43.0/lib/sequel/adapters/postgres.rb:208:in
`initialize': PG::Error: could not translate host name
"0.postgres.default.bosh-ec2.bosh" to address: Name or service not known
(Sequel::DatabaseConnectionError)

NSLookup says:

$ nslookup 0.postgres.default.bosh-ec2.bosh
Server: 172.16.0.23
Address: 172.16.0.23#53

** server can't find 0.postgres.default.bosh-ec2.bosh: NXDOMAIN

So. I clearly don't understand how DNS works in BOSH. My resolv.conf
says:

nameserver 10.32.39.62 # This is my MicroBOSH IP
nameserver 172.16.0.23 # No idea, I'm guessing an AWS nameserver
domain ec2.internal
search ec2.internal

So, what am I misunderstanding here. Please help!

Thanks very much.
--

------------------------------

Have an innovative day

*Innovation Factory *De Lairessestraat 180* *1075 HM Amsterdam* *+31
20 7787008 www.innovationfactory.eu

*
Disclaimer*
*The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
delete the material from any computer. Innovation Factory does not accept
liability for any errors, viruses or omissions in the contents of this
message, which may arise as a result of e-mail transmission. No employee or
agent is authorized to conclude any binding agreement on behalf of
Innovation Factory with another party by email.*

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 10 of 18 | next ›
Discussion Overview
groupbosh-users @
postedJul 11, '13 at 11:03p
activeJul 12, '13 at 3:44p
posts18
users5

People

Translate

site design / logo © 2021 Grokbase