Deployment manifest issues - BOSH Developers

The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Message from discussion Deployment manifest issues
Received-SPF: neutral (google.com: 209.85.160.169 is neither permitted nor denied by best guess record for domain of ol...@rbcon.com) client-ip=209.85.160.169;
MIME-Version: 1.0
In-Reply-To: <fb550810-cf86-4c7e-b722-62ec95f1c...@f8g2000pbf.googlegroups.com>
References: <e15017e4-bac7-4461-a652-0971331e2...@ra8g2000pbc.googlegroups.com>
 <fb550810-cf86-4c7e-b722-62ec95f1c...@f8g2000pbf.googlegroups.com>
From: Oleg Shaldybin <ol...@rbcon.com>
Date: Fri, 8 Jun 2012 11:45:23 -0700
Message-ID: <CABz6BSNJkh245x6pUafWf9RXZmFXwejYCSq2YBeUju7TY2o...@mail.gmail.com>
Subject: Re: [bosh-dev] Re: Deployment manifest issues
To: bosh-...@cloudfoundry.org
Content-Type: multipart/alternative; boundary=14dae93408075d7e2004c1fa68e4

--14dae93408075d7e2004c1fa68e4
Content-Type: text/plain; charset=ISO-8859-1

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?

On Thu, Jun 7, 2012 at 2:02 PM, Nick Terry <nick.i.te...@gmail.com> wrote:

> 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
>
>
> On Jun 7, 3:01 pm, Nick Terry <nick.i.te...@gmail.com> wrote:
> > 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?
>



-- 
Best,
Oleg

--14dae93408075d7e2004c1fa68e4
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Right now job network section doesn&#39;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 &q=
uot;networks.nats&quot; property to your manifest.<div>

<br></div><div>net: &lt;%=3D spec.networks.send(properties.networks.nats).i=
p %&gt;</div><div><br></div><div>This might alleviate the problem but it al=
so required changing your release. You could make it backward-compatible by=
 defaulting to &quot;networks.apps&quot; if &quot;networks.nats&quot; is un=
defined.=A0</div>

<div><br></div><div>Your original deployment error is still strange though:=
 have you been using a deployment manifest without &quot;properties.network=
s.apps&quot; defined?</div><div><br><div class=3D"gmail_quote">On Thu, Jun =
7, 2012 at 2:02 PM, Nick Terry <span dir=3D"ltr">&lt;<a href=3D"mailto:nick=
.i.te...@gmail.com" target=3D"_blank">nick.i.te...@gmail.com</a>&gt;</span>=
 wrote:<br>

<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Ive tried setting the property in the indivi=
dual jobs, but bosh just<br>
uses the one defined in the networks section. I was hoping it was<br>
transient. Heres an example of a job:<br>
<br>
<br>
- name: debian_nfs_server<br>
 =A0template: debian_nfs_server<br>
 =A0instances: 1<br>
 =A0resource_pool: infrastructure<br>
 =A0persistent_disk: 2048<br>
 =A0networks:<br>
 =A0- name: dynamic_network<br>
 =A0 =A0default: [dns, gateway]<br>
 =A0 =A0cloud_properties:<br>
 =A0 =A0 =A0security_groups:<br>
 =A0 =A0 =A0- cf-nfs_server<br>
 =A0- name: vip_network<br>
 =A0 =A0static_ips:<br>
 =A0 =A0- 23.23.175.5<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
On Jun 7, 3:01=A0pm, Nick Terry &lt;<a href=3D"mailto:nick.i.te...@gmail.co=
m">nick.i.te...@gmail.com</a>&gt; wrote:<br>
&gt; I made a special security group (Amazon EC2) for the nats server that<=
br>
&gt; allows only the ip address of the individual components to connect. I<=
br>
&gt; added a new dynamic network to the cf deployment manifest and got this=
<br>
&gt; error:<br>
&gt;<br>
&gt; Preparing configuration<br>
&gt; =A0 binding configuration: Error filling in template nats/nats.yml.erb=
:2<br>
&gt; for nats/0: &#39;undefined method `ip&#39; for nil:NilClass&#39; (00:0=
0:00)<br>
&gt; =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =
=A0 |oooooooooooooooooooooooo| 1/1<br>
&gt; 00:00:00 =A0ETA: --:--:--<br>
&gt; The task has returned an error status, do you want to see debug log?<b=
r>
&gt; [Yn]:<br>
&gt;<br>
&gt; Looking through the cf-release and deployment manifest i notice that<b=
r>
&gt; the release depends on the networks.apps property to work. Out of the<=
br>
&gt; box, we have:<br>
&gt;<br>
&gt; networks:<br>
&gt; =A0 =A0 apps: dynamic_network<br>
&gt; =A0 =A0 management: dynamic_network<br>
&gt;<br>
&gt; I want to add another app to this callsed nats_dynamic_network. I need=
<br>
&gt; to know how to add multiple apps and their corresponding management<br=
>
&gt; field. Any ideas?<br>
</div></div></blockquote></div><br><br clear=3D"all"><div><br></div>-- <br>=
Best,<div>Oleg</div><br>
</div>

--14dae93408075d7e2004c1fa68e4--
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
Account Options
