Deployment manifest issues

82 views
Skip to first unread message

Nick Terry

unread,
Jun 7, 2012, 5:01:04 PM6/7/12
to bosh-dev
I made a special security group (Amazon EC2) for the nats server that
allows only the ip address of the individual components to connect. I
added a new dynamic network to the cf deployment manifest and got this
error:

Preparing configuration
binding configuration: Error filling in template nats/nats.yml.erb:2
for nats/0: 'undefined method `ip' for nil:NilClass' (00:00:00)
|oooooooooooooooooooooooo| 1/1
00:00:00 ETA: --:--:--
The task has returned an error status, do you want to see debug log?
[Yn]:

Looking through the cf-release and deployment manifest i notice that
the release depends on the networks.apps property to work. Out of the
box, we have:

networks:
apps: dynamic_network
management: dynamic_network

I want to add another app to this callsed nats_dynamic_network. I need
to know how to add multiple apps and their corresponding management
field. Any ideas?

Nick Terry

unread,
Jun 7, 2012, 5:02:37 PM6/7/12
to bosh-dev
Ive tried setting the property in the individual jobs, but bosh just
uses the one defined in the networks section. I was hoping it was
transient. Heres an example of a job:


- name: debian_nfs_server
template: debian_nfs_server
instances: 1
resource_pool: infrastructure
persistent_disk: 2048
networks:
- name: dynamic_network
default: [dns, gateway]
cloud_properties:
security_groups:
- cf-nfs_server
- name: vip_network
static_ips:
- 23.23.175.5

Oleg Shaldybin

unread,
Jun 8, 2012, 2:45:23 PM6/8/12
to bosh...@cloudfoundry.org
Right now job network section doesn't support overriding network cloud_properties, however we might want to allow it in the future. What you could do is to change nats.yml.erb template to use your network and introduce "networks.nats" property to your manifest.

net: <%= spec.networks.send(properties.networks.nats).ip %>

This might alleviate the problem but it also required changing your release. You could make it backward-compatible by defaulting to "networks.apps" if "networks.nats" is undefined. 

Your original deployment error is still strange though: have you been using a deployment manifest without "properties.networks.apps" defined?
--
Best,
Oleg

Reply all
Reply to author
Forward
0 new messages