Cloud Foundry Deployment using bosh


Arpit Sharma
 

Dear Team,

I am getting below mentioned error, when I am trying to deploy cloudfoundry using cf-deployment.


07:35:43 | Preparing deployment: Preparing deployment (00:00:00)
L Error: Required property 'networks' was not specified in object ({})

07:35:44 | Error: Required property 'networks' was not specified in object ({})

Started Tue Aug 8 07:35:43 UTC 2017
Finished Tue Aug 8 07:35:44 UTC 2017
Duration 00:00:01

Task 101 error

Updating deployment:
Expected task '101' to succeed but state is 'error'

Exit code 1


Anybody can help me with this?


David Sabeti
 

Hi Arpit,

It looks like you're missing a cloud-config
<http://bosh.io/docs/cloud-config.html>. You'll need to write a
cloud-config and upload it to your bosh director.

Which IaaS are you using? I may be able to help you find an example
cloud-config to use.

David

On Tue, Aug 8, 2017 at 1:16 AM Arpit Sharma <arpitvipulsharma(a)gmail.com>
wrote:

Dear Team,

I am getting below mentioned error, when I am trying to deploy
cloudfoundry using cf-deployment.


07:35:43 | Preparing deployment: Preparing deployment (00:00:00)
L Error: Required property 'networks' was not specified in
object ({})

07:35:44 | Error: Required property 'networks' was not specified in object
({})

Started Tue Aug 8 07:35:43 UTC 2017
Finished Tue Aug 8 07:35:44 UTC 2017
Duration 00:00:01

Task 101 error

Updating deployment:
Expected task '101' to succeed but state is 'error'

Exit code 1


Anybody can help me with this?


Arpit Sharma
 

Hi David,

Thanks for your response. Yes.. I am using Openstack for cloud. If possible send me sample file for cloud config.


Arpit Sharma
 

Hey David!
I have updated cloud-config as follows:

bosh -e bosh-1 cloud-config
Using environment '10.100.10.18' as client 'admin'

azs:
- cloud_properties:
availability_zone: nova
name: z1
compilation:
az: z1
network: default
reuse_compilation_vms: true
vm_type: default
workers: 5
disk_types:
- disk_size: 3000
name: default
- disk_size: 50000
name: large
networks:
- name: default
subnets:
- az: z1
cloud_properties:
net_id: 6274c624-e262-4ba1-845f-7548c91a813f
dns:
- 8.8.8.8
gateway: 192.168.1.1
range: 192.168.1.0/24
type: manual
- name: vip
type: vip
vm_types:
- cloud_properties:
instance_type: default
name: default

but now I am getting below mentioned error


14:02:48 | Preparing deployment: Preparing deployment (00:00:00)
L Error: Instance group 'smoke-tests' references an unknown vm type 'm1.tiny'

14:02:48 | Error: Instance group 'smoke-tests' references an unknown vm type 'm1.tiny'

Started Wed Aug 9 14:02:48 UTC 2017
Finished Wed Aug 9 14:02:48 UTC 2017
Duration 00:00:00

Task 117 error

Updating deployment:
Expected task '117' to succeed but state is 'error'

Exit code 1


can you help with this? I have not uploaded cpi config till now. Do you think that cpi config is required?


David Sabeti
 

Hey Arpit,

I don't think you need to use CPI config for this. You can define VM types
in your *cloud-config:* http://bosh.io/docs/cloud-config.html#vm-types

You probably just need to add an `m1.tiny` VM type to your cloud config.

On Wed, Aug 9, 2017 at 7:13 AM Arpit Sharma <arpitvipulsharma(a)gmail.com>
wrote:

Hey David!
I have updated cloud-config as follows:

bosh -e bosh-1 cloud-config
Using environment '10.100.10.18' as client 'admin'

azs:
- cloud_properties:
availability_zone: nova
name: z1
compilation:
az: z1
network: default
reuse_compilation_vms: true
vm_type: default
workers: 5
disk_types:
- disk_size: 3000
name: default
- disk_size: 50000
name: large
networks:
- name: default
subnets:
- az: z1
cloud_properties:
net_id: 6274c624-e262-4ba1-845f-7548c91a813f
dns:
- 8.8.8.8
gateway: 192.168.1.1
range: 192.168.1.0/24
type: manual
- name: vip
type: vip
vm_types:
- cloud_properties:
instance_type: default
name: default

but now I am getting below mentioned error


14:02:48 | Preparing deployment: Preparing deployment (00:00:00)
L Error: Instance group 'smoke-tests' references an unknown vm
type 'm1.tiny'

14:02:48 | Error: Instance group 'smoke-tests' references an unknown vm
type 'm1.tiny'

Started Wed Aug 9 14:02:48 UTC 2017
Finished Wed Aug 9 14:02:48 UTC 2017
Duration 00:00:00

Task 117 error

Updating deployment:
Expected task '117' to succeed but state is 'error'

Exit code 1


can you help with this? I have not uploaded cpi config till now. Do you
think that cpi config is required?


Arpit Sharma
 

Hi David Sabeti,

Done. Thanks for your response. I have done these changes. But still I am getting error due to vm_extensions, which I have not defined in cloud config. Is it really required? what you suggest?


David Sabeti
 

Hey Arpit,

The VM extensions in cf-deployment are required, as they instruct the CPI
to integrate routers with load balancers and to add more disk to some of
the jobs that need it. For example, on GCP, the VM extension adds a tag to
the routers so that they get include in the GCP "Backend Service" that the
load balancers will route to. Similarly, for AWS, the VM extensions
actually name the ELB that will get reconfigured to route traffic to the
routers.

We don't yet have a working cloud-config for OpenStack, but there's a team
working on it as we speak. For now, you could take a look at the BOSH
documentation for the OpenStack CPI[1]. Anything that goes in
`cloud_properties` for the resource_pools can also be added to the
`cloud_properties` of a VM extension in your cloud-config, so it looks like
you could try adding `loadbalancer_pools` as part of the VM extensions
necessary for the routers.

David


[1] http://bosh.io/docs/openstack-cpi.html

On Fri, Aug 11, 2017 at 1:31 AM Arpit Sharma <arpitvipulsharma(a)gmail.com>
wrote:

Hi David Sabeti,

Done. Thanks for your response. I have done these changes. But still I am
getting error due to vm_extensions, which I have not defined in cloud
config. Is it really required? what you suggest?


Arpit Sharma
 

Hi David Sabeti,
Got it. Let me do some exercise with it. Thanks for your response.