Deploy BOSH job in VPC resolves to external VPC IP address should resolve to internal


Oded Gold
 

Hi all

I am new to BOSH and starting my first complete BOSH deployment. I am trying to deploy BOSH within a VPC and have the jobs communicate with internal IP address assigned by BOSH not manually.
However every time I run the deployment and check which IP address is resolved it is always the VPC external IP address.

I am not sure if what I am trying to achieve is possible or if my configuration is wrong and I am just missing something (all this BOSH is new to me)

My manifest for the deployment looks like:
__________________________________________________
networks:
- name: default
type: manual
subnets:
- range: 10.2.1.0/25
gateway: 10.2.1.1
dns: [10.2.1.10, 10.2.1.2]
reserved: [10.2.1.2-10.2.1.16]
cloud_properties:
subnet: subnet-e1aca5b8
security_groups:
- sg-60d85b06

jobs:
- name: infra
templates:
- {name: bss_redis, release: bss-ci}
- {name: activemq, release: bss-ci}
- {name: router, release: bss-ci}
- {name: uaa, release: bss-ci}
instances: 1
resource_pool: c3-large
persistent_disk: 8192
networks:
- name: default
default: [dns, gateway]
- name: infra_network
static_ips:
- 52.2.222.22
properties:
db: databases

What happens when I dig the "0.infra.infra-network.bss-ci.bosh" DNS it resolves to "52.2.222.22" but what I need is for it to resolve in the assigned range 10.2.1.0/25

I hope what I am try to achieve is clear, again I am new to BOSH and any help would be appreciated.

Thank you


Dmitriy Kalinin
 

Instead of using 0.infra.infra-network.bss-ci.bosh you can use
0.infra.default.bss-ci.bosh to point to internal network.

On Thu, Nov 12, 2015 at 5:00 AM, Oded Gold <oded(a)nurego.com> wrote:

Hi all

I am new to BOSH and starting my first complete BOSH deployment. I am
trying to deploy BOSH within a VPC and have the jobs communicate with
internal IP address assigned by BOSH not manually.
However every time I run the deployment and check which IP address is
resolved it is always the VPC external IP address.

I am not sure if what I am trying to achieve is possible or if my
configuration is wrong and I am just missing something (all this BOSH is
new to me)

My manifest for the deployment looks like:
__________________________________________________
networks:
- name: default
type: manual
subnets:
- range: 10.2.1.0/25
gateway: 10.2.1.1
dns: [10.2.1.10, 10.2.1.2]
reserved: [10.2.1.2-10.2.1.16]
cloud_properties:
subnet: subnet-e1aca5b8
security_groups:
- sg-60d85b06

jobs:
- name: infra
templates:
- {name: bss_redis, release: bss-ci}
- {name: activemq, release: bss-ci}
- {name: router, release: bss-ci}
- {name: uaa, release: bss-ci}
instances: 1
resource_pool: c3-large
persistent_disk: 8192
networks:
- name: default
default: [dns, gateway]
- name: infra_network
static_ips:
- 52.2.222.22
properties:
db: databases

What happens when I dig the "0.infra.infra-network.bss-ci.bosh" DNS it
resolves to "52.2.222.22" but what I need is for it to resolve in the
assigned range 10.2.1.0/25

I hope what I am try to achieve is clear, again I am new to BOSH and any
help would be appreciated.

Thank you


Oded Gold
 

Thank you for pointing me in the right direction, "0.infra.infra-network.bss-ci.bosh" is the correct DNS but when I make the change in the manifest it and then look at the logs of my running services they still try to resolve to "0.infra.infra-network.bss-ci.bosh".

Am I making the changes in the wrong place? Is there something else I need to be doing? I even deleted the deployment and tried again


Dmitriy Kalinin
 

Well that depends how your release configuration works out this DNS record.
Is that a property specified in your job spec?

On Wed, Nov 25, 2015 at 2:29 AM, Oded Gold <oded(a)nurego.com> wrote:

Thank you for pointing me in the right direction,
"0.infra.infra-network.bss-ci.bosh" is the correct DNS but when I make the
change in the manifest it and then look at the logs of my running services
they still try to resolve to "0.infra.infra-network.bss-ci.bosh".

Am I making the changes in the wrong place? Is there something else I need
to be doing? I even deleted the deployment and tried again