|
hi, I am trying to compose a manifest with network type as dynamic on aws. I have a manifest which is similar to the one described in https://bosh.io/docs/networks#dynamic. I am getting an error Started compiling packages > nothing/1f163bd552d500098d236e67284465da39bfdbef. Failed: Missing properties: resource_pool.availability_zone (00:00:12) Error 100: Missing properties: resource_pool.availability_zone Has anyone faced a similar issue before for the AWS cpi? The cloud config: vm_types: - name: small cloud_properties: instance_type: t2.micro ephemeral_disk: {size: 3000, type: gp2} disk_types: - name: disks disk_size: 200 cloud_properties: {type: gp2} networks: - name: dyn type: dynamic dns: [10.0.16.2] cloud_properties: subnet: subnet-bb1884df availability_zone: eu-west-1a compilation: workers: 5 reuse_compilation_vms: true vm_type: small network: dyn The deployment manifest: --- name: red director_uuid: f7671e76-95eb-481e-9dfa-edd4096ecd78 stemcells: - alias: trusty name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent version: latest releases: - name: empty-box-release version: latest jobs: - name: nothing instances: 1 templates: - {name: do_nothing, release: empty-box-release} vm_type: small stemcell: trusty networks: - name: dyn update: canaries: 1 canary_watch_time: 30000-300000 update_watch_time: 30000-300000 max_in_flight: 1 max_errors: 2 serial: false
|
|
|
toggle quoted messageShow quoted text
On Aug 30, 2016, at 5:51 AM, Jatin Naik <jnaik(a)pivotal.io> wrote:
hi,
I am trying to compose a manifest with network type as dynamic on aws. I have a manifest which is similar to the one described in https://bosh.io/docs/networks#dynamic.
I am getting an error
Started compiling packages > nothing/1f163bd552d500098d236e67284465da39bfdbef. Failed: Missing properties: resource_pool.availability_zone (00:00:12)
Error 100: Missing properties: resource_pool.availability_zone
Has anyone faced a similar issue before for the AWS cpi?
The cloud config:
vm_types:
- name: small
cloud_properties:
instance_type: t2.micro
ephemeral_disk: {size: 3000, type: gp2}
disk_types:
- name: disks
disk_size: 200
cloud_properties: {type: gp2}
networks:
- name: dyn
type: dynamic
dns: [10.0.16.2]
cloud_properties:
subnet: subnet-bb1884df
availability_zone: eu-west-1a
compilation:
workers: 5
reuse_compilation_vms: true
vm_type: small
network: dyn
The deployment manifest:
---
name: red
director_uuid: f7671e76-95eb-481e-9dfa-edd4096ecd78
stemcells:
- alias: trusty
name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent
version: latest
releases:
- name: empty-box-release
version: latest
jobs:
- name: nothing
instances: 1
templates:
- {name: do_nothing, release: empty-box-release}
vm_type: small
stemcell: trusty
networks:
- name: dyn
update:
canaries: 1
canary_watch_time: 30000-300000
update_watch_time: 30000-300000
max_in_flight: 1
max_errors: 2
serial: false
|
|
|
Hi Dmitriy, Thanks for getting back. It doesn't seem to work for me for me even without the availability_zone in the network section. I had the impression that availability_zone is optional in the cloud config, i.e. The deployment would work without any az's specified - is that correct? I am trying to use the feature documented here https://bosh.io/docs/networks#dynamic, specifically the first example without az's. My updated cloud_config looks like this with availability_zone removed, I am still getting the same issue: vm_types: - name: small cloud_properties: instance_type: t2.micro ephemeral_disk: {size: 3000, type: gp2} disk_types: - name: disks disk_size: 200 cloud_properties: {type: gp2} networks: - name: dyn type: dynamic dns: [10.0.16.2] cloud_properties: subnet: subnet-bb1884df compilation: workers: 5 reuse_compilation_vms: true vm_type: small network: dyn On Tue, Aug 30, 2016 at 3:41 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote: hey,
here is a simple example of cloud config: http://bosh.io/docs/aws-cpi.
html#cloud-config
availability_zone goes into azs section, not on a network.
once you ve defined azs, you should also specify azs on the
instance_groups as well: http://bosh.io/docs/manifest-v2#instance-groups.
Sent from my iPhone
On Aug 30, 2016, at 5:51 AM, Jatin Naik <jnaik(a)pivotal.io> wrote:
hi,
I am trying to compose a manifest with network type as dynamic on aws. I
have a manifest which is similar to the one described in
https://bosh.io/docs/networks#dynamic.
I am getting an error
Started compiling packages > nothing/1f163bd552d500098d236e67284465da39bfdbef.
Failed: Missing properties: resource_pool.availability_zone (00:00:12)
Error 100: Missing properties: resource_pool.availability_zone
Has anyone faced a similar issue before for the AWS cpi?
The cloud config:
vm_types:
- name: small
cloud_properties:
instance_type: t2.micro
ephemeral_disk: {size: 3000, type: gp2}
disk_types:
- name: disks
disk_size: 200
cloud_properties: {type: gp2}
networks:
- name: dyn
type: dynamic
dns: [10.0.16.2]
cloud_properties:
subnet: subnet-bb1884df
availability_zone: eu-west-1a
compilation:
workers: 5
reuse_compilation_vms: true
vm_type: small
network: dyn
The deployment manifest:
---
name: red
director_uuid: f7671e76-95eb-481e-9dfa-edd4096ecd78
stemcells:
- alias: trusty
name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent
version: latest
releases:
- name: empty-box-release
version: latest
jobs:
- name: nothing
instances: 1
templates:
- {name: do_nothing, release: empty-box-release}
vm_type: small
stemcell: trusty
networks:
- name: dyn
update:
canaries: 1
canary_watch_time: 30000-300000
update_watch_time: 30000-300000
max_in_flight: 1
max_errors: 2
serial: false
|
|
|
Hi,
I understand the problem with my deployment now, I have to specify
either a availability_zone
in the cloud properties of the vm_type or az the property on the instance
group for 'first class' az support.
If anyone else is facing a similar issue, my working cloud-config looks
like:
vm_types:
- name: small
cloud_properties:
instance_type: t2.micro
ephemeral_disk: {size: 3000, type: gp2}
availability_zone: eu-west-1a
disk_types:
- name: disks
disk_size: 200
cloud_properties: {type: gp2}
networks:
- name: dyn
type: dynamic
dns: [10.0.16.2]
cloud_properties:
subnet: subnet-bb1884df
compilation:
workers: 5
reuse_compilation_vms: true
vm_type: small
network: dyn
toggle quoted messageShow quoted text
On Tue, Aug 30, 2016 at 5:27 PM, Jatin Naik <jnaik(a)pivotal.io> wrote: Hi Dmitriy,
Thanks for getting back.
It doesn't seem to work for me for me even without the availability_zone
in the network section.
I had the impression that availability_zone is optional in the cloud
config, i.e. The deployment would work without any az's specified - is that
correct? I am trying to use the feature documented here
https://bosh.io/docs/networks#dynamic, specifically the first example
without az's.
My updated cloud_config looks like this with availability_zone removed, I
am still getting the same issue:
vm_types:
- name: small
cloud_properties:
instance_type: t2.micro
ephemeral_disk: {size: 3000, type: gp2}
disk_types:
- name: disks
disk_size: 200
cloud_properties: {type: gp2}
networks:
- name: dyn
type: dynamic
dns: [10.0.16.2]
cloud_properties:
subnet: subnet-bb1884df
compilation:
workers: 5
reuse_compilation_vms: true
vm_type: small
network: dyn
On Tue, Aug 30, 2016 at 3:41 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:
hey,
here is a simple example of cloud config: http://bosh.io/docs/aws-cpi.ht
ml#cloud-config
availability_zone goes into azs section, not on a network.
once you ve defined azs, you should also specify azs on the
instance_groups as well: http://bosh.io/docs/manifest-v2#instance-groups.
Sent from my iPhone
On Aug 30, 2016, at 5:51 AM, Jatin Naik <jnaik(a)pivotal.io> wrote:
hi,
I am trying to compose a manifest with network type as dynamic on aws. I
have a manifest which is similar to the one described in
https://bosh.io/docs/networks#dynamic.
I am getting an error
Started compiling packages > nothing/1f163bd552d500098d236e67284465da39bfdbef.
Failed: Missing properties: resource_pool.availability_zone (00:00:12)
Error 100: Missing properties: resource_pool.availability_zone
Has anyone faced a similar issue before for the AWS cpi?
The cloud config:
vm_types:
- name: small
cloud_properties:
instance_type: t2.micro
ephemeral_disk: {size: 3000, type: gp2}
disk_types:
- name: disks
disk_size: 200
cloud_properties: {type: gp2}
networks:
- name: dyn
type: dynamic
dns: [10.0.16.2]
cloud_properties:
subnet: subnet-bb1884df
availability_zone: eu-west-1a
compilation:
workers: 5
reuse_compilation_vms: true
vm_type: small
network: dyn
The deployment manifest:
---
name: red
director_uuid: f7671e76-95eb-481e-9dfa-edd4096ecd78
stemcells:
- alias: trusty
name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent
version: latest
releases:
- name: empty-box-release
version: latest
jobs:
- name: nothing
instances: 1
templates:
- {name: do_nothing, release: empty-box-release}
vm_type: small
stemcell: trusty
networks:
- name: dyn
update:
canaries: 1
canary_watch_time: 30000-300000
update_watch_time: 30000-300000
max_in_flight: 1
max_errors: 2
serial: false
|
|
|
Out of curiosity any reason why not to use first class azs?
toggle quoted messageShow quoted text
On Tue, Aug 30, 2016 at 10:36 AM, Jatin Naik <jnaik(a)pivotal.io> wrote: Hi,
I understand the problem with my deployment now, I have to specify either
a availability_zone in the cloud properties of the vm_type or az the
property on the instance group for 'first class' az support.
If anyone else is facing a similar issue, my working cloud-config looks
like:
vm_types:
- name: small
cloud_properties:
instance_type: t2.micro
ephemeral_disk: {size: 3000, type: gp2}
availability_zone: eu-west-1a
disk_types:
- name: disks
disk_size: 200
cloud_properties: {type: gp2}
networks:
- name: dyn
type: dynamic
dns: [10.0.16.2]
cloud_properties:
subnet: subnet-bb1884df
compilation:
workers: 5
reuse_compilation_vms: true
vm_type: small
network: dyn
On Tue, Aug 30, 2016 at 5:27 PM, Jatin Naik <jnaik(a)pivotal.io> wrote:
Hi Dmitriy,
Thanks for getting back.
It doesn't seem to work for me for me even without the availability_zone
in the network section.
I had the impression that availability_zone is optional in the cloud
config, i.e. The deployment would work without any az's specified - is that
correct? I am trying to use the feature documented here
https://bosh.io/docs/networks#dynamic, specifically the first example
without az's.
My updated cloud_config looks like this with availability_zone removed,
I am still getting the same issue:
vm_types:
- name: small
cloud_properties:
instance_type: t2.micro
ephemeral_disk: {size: 3000, type: gp2}
disk_types:
- name: disks
disk_size: 200
cloud_properties: {type: gp2}
networks:
- name: dyn
type: dynamic
dns: [10.0.16.2]
cloud_properties:
subnet: subnet-bb1884df
compilation:
workers: 5
reuse_compilation_vms: true
vm_type: small
network: dyn
On Tue, Aug 30, 2016 at 3:41 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:
hey,
here is a simple example of cloud config: http://bosh.io/docs/aws-cpi.ht
ml#cloud-config
availability_zone goes into azs section, not on a network.
once you ve defined azs, you should also specify azs on the
instance_groups as well: http://bosh.io/docs/manifest-v2#instance-groups
.
Sent from my iPhone
On Aug 30, 2016, at 5:51 AM, Jatin Naik <jnaik(a)pivotal.io> wrote:
hi,
I am trying to compose a manifest with network type as dynamic on aws. I
have a manifest which is similar to the one described in
https://bosh.io/docs/networks#dynamic.
I am getting an error
Started compiling packages > nothing/1f163bd552d500098d236e67284465da39bfdbef.
Failed: Missing properties: resource_pool.availability_zone (00:00:12)
Error 100: Missing properties: resource_pool.availability_zone
Has anyone faced a similar issue before for the AWS cpi?
The cloud config:
vm_types:
- name: small
cloud_properties:
instance_type: t2.micro
ephemeral_disk: {size: 3000, type: gp2}
disk_types:
- name: disks
disk_size: 200
cloud_properties: {type: gp2}
networks:
- name: dyn
type: dynamic
dns: [10.0.16.2]
cloud_properties:
subnet: subnet-bb1884df
availability_zone: eu-west-1a
compilation:
workers: 5
reuse_compilation_vms: true
vm_type: small
network: dyn
The deployment manifest:
---
name: red
director_uuid: f7671e76-95eb-481e-9dfa-edd4096ecd78
stemcells:
- alias: trusty
name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent
version: latest
releases:
- name: empty-box-release
version: latest
jobs:
- name: nothing
instances: 1
templates:
- {name: do_nothing, release: empty-box-release}
vm_type: small
stemcell: trusty
networks:
- name: dyn
update:
canaries: 1
canary_watch_time: 30000-300000
update_watch_time: 30000-300000
max_in_flight: 1
max_errors: 2
serial: false
|
|
|
No strong reason in particular. My existing manifests didn't use first class azs, I didn't want to covert them for this change. On Tue, Aug 30, 2016 at 6:46 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote: Out of curiosity any reason why not to use first class azs?
On Tue, Aug 30, 2016 at 10:36 AM, Jatin Naik <jnaik(a)pivotal.io> wrote:
Hi,
I understand the problem with my deployment now, I have to specify either
a availability_zone in the cloud properties of the vm_type or az the
property on the instance group for 'first class' az support.
If anyone else is facing a similar issue, my working cloud-config looks
like:
vm_types:
- name: small
cloud_properties:
instance_type: t2.micro
ephemeral_disk: {size: 3000, type: gp2}
availability_zone: eu-west-1a
disk_types:
- name: disks
disk_size: 200
cloud_properties: {type: gp2}
networks:
- name: dyn
type: dynamic
dns: [10.0.16.2]
cloud_properties:
subnet: subnet-bb1884df
compilation:
workers: 5
reuse_compilation_vms: true
vm_type: small
network: dyn
On Tue, Aug 30, 2016 at 5:27 PM, Jatin Naik <jnaik(a)pivotal.io> wrote:
Hi Dmitriy,
Thanks for getting back.
It doesn't seem to work for me for me even without the availability_zone
in the network section.
I had the impression that availability_zone is optional in the cloud
config, i.e. The deployment would work without any az's specified - is that
correct? I am trying to use the feature documented here
https://bosh.io/docs/networks#dynamic, specifically the first example
without az's.
My updated cloud_config looks like this with availability_zone removed,
I am still getting the same issue:
vm_types:
- name: small
cloud_properties:
instance_type: t2.micro
ephemeral_disk: {size: 3000, type: gp2}
disk_types:
- name: disks
disk_size: 200
cloud_properties: {type: gp2}
networks:
- name: dyn
type: dynamic
dns: [10.0.16.2]
cloud_properties:
subnet: subnet-bb1884df
compilation:
workers: 5
reuse_compilation_vms: true
vm_type: small
network: dyn
On Tue, Aug 30, 2016 at 3:41 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:
hey,
here is a simple example of cloud config:
http://bosh.io/docs/aws-cpi.html#cloud-config
availability_zone goes into azs section, not on a network.
once you ve defined azs, you should also specify azs on the
instance_groups as well: http://bosh.io/docs/manifest-v
2#instance-groups.
Sent from my iPhone
On Aug 30, 2016, at 5:51 AM, Jatin Naik <jnaik(a)pivotal.io> wrote:
hi,
I am trying to compose a manifest with network type as dynamic on aws.
I have a manifest which is similar to the one described in
https://bosh.io/docs/networks#dynamic.
I am getting an error
Started compiling packages > nothing/1f163bd552d500098d236e67284465da39bfdbef.
Failed: Missing properties: resource_pool.availability_zone (00:00:12)
Error 100: Missing properties: resource_pool.availability_zone
Has anyone faced a similar issue before for the AWS cpi?
The cloud config:
vm_types:
- name: small
cloud_properties:
instance_type: t2.micro
ephemeral_disk: {size: 3000, type: gp2}
disk_types:
- name: disks
disk_size: 200
cloud_properties: {type: gp2}
networks:
- name: dyn
type: dynamic
dns: [10.0.16.2]
cloud_properties:
subnet: subnet-bb1884df
availability_zone: eu-west-1a
compilation:
workers: 5
reuse_compilation_vms: true
vm_type: small
network: dyn
The deployment manifest:
---
name: red
director_uuid: f7671e76-95eb-481e-9dfa-edd4096ecd78
stemcells:
- alias: trusty
name: bosh-aws-xen-hvm-ubuntu-trusty-go_agent
version: latest
releases:
- name: empty-box-release
version: latest
jobs:
- name: nothing
instances: 1
templates:
- {name: do_nothing, release: empty-box-release}
vm_type: small
stemcell: trusty
networks:
- name: dyn
update:
canaries: 1
canary_watch_time: 30000-300000
update_watch_time: 30000-300000
max_in_flight: 1
max_errors: 2
serial: false
|
|
|
