A lot of this is set to change in the near future to make things more
clear. But here is what is currently going on.

BOSH will pre-create machines it is going to need, and it does that without
any input from the jobs that will eventually run on them. A machine needs a
network to be created, so that is the reason it is needed in the resource
pool section.

Later when BOSH configures the machine for running a job on it, it will
update the network to match the details provided in the job.

You'll probably get a faster response to questions like this in the cf-bosh
mailing list in the future.

Joseph
OSS Release Integration Team

On Tue, Sep 8, 2015 at 6:09 PM, ronak banka <ronakbanka.cse(a)gmail.com>
wrote:

Hello All,

I have a resource pool , let say small_z1

- name: small_z1
network: cf1
stemcell: stemcell-xyz
cloud_properties:
instance_type: m1.small
availability_zone: zone1

and a Job , router having two networks assigned to it

- name: router
instances: 1
networks:
- name: router_internal
default: [dns, gateway]
static_ips:
- xy.xy.xy.xy
- name: router_external
static_ips:
- yz.yz.yz.yz
gateway: yy.yy.yy.yy
networks:
apps: router_internal
management: router_internal
resource_pool: small_z1

With these properties there are no issues anywhere.

what is the network property in resource pool responsible for, if the
created job networks and not linked to the one in pool??

Regards,
Ronak



--
View this message in context:
http://cf-dev.70369.x6.nabble.com/Relation-between-Network-property-in-Resource-pool-block-and-Network-property-in-Actual-Job-block-tp1562.html
Sent from the CF Dev mailing list archive at Nabble.com.