You want to provide both a default network and a VIP network.
- name: nginx
template: nginx
instances: 1
resource_pool: common
networks:
- name: default
default: [dns, gateway]
- name: nginx
static_ips:
- 23.23.245.179
Also, I don't think you need cloud_properties for the job since
they're not applicable there.
-Vadim
On Apr 15, 9:47 pm, Dr Nic Williams <
drnicwilli...@gmail.com> wrote:
> Thanks Vadim, I now have 3 lovely VMs booted.
>
> Though, the system doesn't currently work - none currently have elastic IPs, and if I point my browser at each AWS-generated public dns, one of them shows a 504 nginx error (yep, the random nginx VM).
>
> From chatting with Oleg on Friday, I think each VM needs a well-known elastic IP. How do I do this?
>
> My attempts to give each job a specific vip network that had a static IP end me back with the error from before: "Can't provide any defaults since this is a VIP network"
>
> The two manifests are athttps://
gist.github.com/75ced173309bba0d8b23. An example of a failing job is below:
>
> jobs:
> - name: nginx
> template: nginx
> instances: 1
> resource_pool: common
> networks:
> - name: nginx
> default: [dns, gateway]
> static_ips:
> - 23.23.245.179
> cloud_properties:
> instance_type: m1.small
>
> Thanks again for all help. Soon, we will have a lovely AWS tutorial :)
>
> Nic
>
> --
> Dr Nic Williams
> Engine Yard, VP Developer Evangelismhttp://engineyard.comhttp://drnicwilliams.comhttp://
about.me/drnic
> cell
+1 (415) 860-2185
>
>
>
>
>
>
>
> On Sunday, April 15, 2012 at 8:41 PM, Vadim Spivak wrote:
> > Add the following to the network section for each job.
>
> > - name: default
> > default: [dns, gateway]
>
> > -Vadim
>
> > On Apr 15, 2012, at 8:22 PM, Dr Nic Williams <
drnicwilli...@gmail.com (mailto:
drnicwilli...@gmail.com)> wrote:
>
> > > Currently I am combining:
> > > * code reading - though its still hard to figure out how the manifest files maps into the various Bosh::Director::XXX models; and
> > > * wild guessing of what schema to go with for an AWS configuration
>
> > > Do you have any suggestions for changes to the manifest file (in the gist debug output)?
>
> > > Nic
>
> > > --
> > > Dr Nic Williams
> > > Engine Yard, VP Developer Evangelism
> > >
http://engineyard.com
> > >
http://drnicwilliams.com
> > >
http://about.me/drnic
> > > cell
+1 (415) 860-2185
>
> > > On Sunday, April 15, 2012 at 8:16 PM, Vadim Spivak wrote:
>
> > > > You have to provide a dynamic network as well, since a VIP network is not known to the guest.
>
> > > > -Vadim
>
> > > > On Apr 15, 2012, at 8:13 PM, Dr Nic Williams <
drnicwilli...@gmail.com (mailto:
drnicwilli...@gmail.com)> wrote:
>
> > > > > Next error (getting close!) - "Can't provide any defaults since this is a VIP network"
>
> > > > > $ bosh deploy
> > > > > Getting deployment properties from director...
> > > > > Compiling deployment manifest...
> > > > > Please review all changes carefully
> > > > > Deploying `wordpress-aws.yml' to `yourboshname' (type 'yes' to continue): yes
> > > > > Tracking task output for task#20...
>
> > > > > Preparing deployment
> > > > > binding deployment (00:00:00)
> > > > > binding release (00:00:00)
> > > > > binding existing deployment (00:00:00)
> > > > > binding resource pools (00:00:00)
> > > > > binding stemcells (00:00:00)
> > > > > binding templates (00:00:00)
> > > > > binding unallocated VMs (00:00:00)
> > > > > binding instance networks (00:00:00)
> > > > > Done 7/7 00:00:00
>
> > > > > Preparing DNS
> > > > > binding DNS (00:00:00)
> > > > > Done 1/1 00:00:00
>
> > > > > Creating bound missing VMs
> > > > > common/0: Can't provide any defaults since this is a VIP network (00:00:00)
> > > > > Error 1/3 00:00:00
>
> > > > > Debug is athttps://
gist.github.com/87061a9b550cefbe7d16
> > > > > > > > > cell
+1 (415) 860-2185 (tel:%2B1%20%28415%29%20860-2185)
>
> > > > > > > > > On Sunday, April 15, 2012 at 6:26 PM, Oleg Shaldibin wrote:
>
> > > > > > > > > > This means your VMs have never been created in the first place, so there might be a problem with your infrastructure or CPI. VM references are in the BOSH DIrector database but they don't have cloud ids, so BOSH is unable to do anything meaningful. We'll need more context: can you provide us with either your original 'create deployment' debug task log or your director hostname (you can get debug task log with bosh tasks recent <n>, followed by 'bosh task <create-deployment-task-id> --debug').
>
> ...
>
> read more »