Date   
Error: Required property 'compilation' was not specified -Bosh v2-Openstack

Gw .
 

Dear Team,

I am trying to deploy CF on Openstack using bosh .

I am now using Bosh v2 for deployment. As per the document
https://docs.cloudfoundry.org/deploying/openstack/cf-stub.html , I
configured manifest.yml (Manifest I used : my-manifest
<https://gist.github.com/gowriln/936dd0f488bfd981c999ed56c9016579> ) . I
also faced issue mentioned in
https://github.com/cloudfoundry/cf-release/issues/1224
and as per suggestions in the issue, I created release using CLI v1 and
uploaded the release using CLI v2.

Now when I excute deploy using :
$bosh -e my-env -d my-dep deploy manifest.yml

I get the following error :

14:39:40 | Deprecation: Ignoring cloud config. Manifest contains 'networks'
section.
14:39:40 | Preparing deployment: Preparing deployment (00:00:01)
L Error: Required property 'compilation' was not specified in
object ({"networks"=>[{"cloud_properties"=>{"net_id"=>"15...",
"security_groups"=>[]}, "name"=>"floating", "type"=>"vip"}, {"name"=>"cf1",
"subnets"=>[{"cloud_properties"=>{"net_id"=>"3a...",
"security_groups"=>["bosh-TestCF", "CF-TestCF"]}, "dns"=>["8.8.8.8"],
"gateway"=>"172.10.0.1", "range"=>"172.10.0.0/24",
"reserved"=>["172.10.0.16 - 172.10.0.100", "172.10.0.200 - 172.10.0.254"],
"static"=>["172.10.0.125 - 172.10.0.175"]}], "type"=>"manual"},
{"name"=>"cf2", "subnets"=>[{"cloud_properties"=>{"net_id"=>"3a...",
"security_groups"=>["bosh-TestCF", "CF-TestCF"]}, "dns"=>["8.8.8.8"],
"gateway"=>"172.10.0.1", "range"=>"172.10.0.0/24",
"reserved"=>["172.10.0.16 - 172.10.0.100", "172.10.0.200 - 172.10.0.254"],
"static"=>["172.10.0.125 - 172.10.0.175"]}], "type"=>"manual"}]})


Any suggestions ?

Re: Error: Required property 'compilation' was not specified -Bosh v2-Openstack

Ronak Banka
 

Hi,

As the error says compilation block in missing in manifest.

Add compilation block and redeploy.

Thanks
Ronak

On Tue, Aug 22, 2017 at 21:15 Gowri LN <gowri.ln123(a)gmail.com> wrote:

Dear Team,

I am trying to deploy CF on Openstack using bosh .

I am now using Bosh v2 for deployment. As per the document
https://docs.cloudfoundry.org/deploying/openstack/cf-stub.html , I
configured manifest.yml (Manifest I used : my-manifest
<https://gist.github.com/gowriln/936dd0f488bfd981c999ed56c9016579> ) .
I also faced issue mentioned in https://github.com/cloudfoundry/cf-release/issues/1224
and as per suggestions in the issue, I created release using CLI v1 and
uploaded the release using CLI v2.

Now when I excute deploy using :
$bosh -e my-env -d my-dep deploy manifest.yml

I get the following error :

14:39:40 | Deprecation: Ignoring cloud config. Manifest contains
'networks' section.
14:39:40 | Preparing deployment: Preparing deployment (00:00:01)
L Error: Required property 'compilation' was not specified in
object ({"networks"=>[{"cloud_properties"=>{"net_id"=>"15...",
"security_groups"=>[]}, "name"=>"floating", "type"=>"vip"}, {"name"=>"cf1",
"subnets"=>[{"cloud_properties"=>{"net_id"=>"3a...",
"security_groups"=>["bosh-TestCF", "CF-TestCF"]}, "dns"=>["8.8.8.8"],
"gateway"=>"172.10.0.1", "range"=>"172.10.0.0/24",
"reserved"=>["172.10.0.16 - 172.10.0.100", "172.10.0.200 - 172.10.0.254"],
"static"=>["172.10.0.125 - 172.10.0.175"]}], "type"=>"manual"},
{"name"=>"cf2", "subnets"=>[{"cloud_properties"=>{"net_id"=>"3a...",
"security_groups"=>["bosh-TestCF", "CF-TestCF"]}, "dns"=>["8.8.8.8"],
"gateway"=>"172.10.0.1", "range"=>"172.10.0.0/24",
"reserved"=>["172.10.0.16 - 172.10.0.100", "172.10.0.200 - 172.10.0.254"],
"static"=>["172.10.0.125 - 172.10.0.175"]}], "type"=>"manual"}]})


Any suggestions ?

Re: Not able to install symantec endpoint protection antivirus on bosh deployed ubuntu(14.04) servers

Dmitriy Kalinin
 

if vcloud cpi allows to specify root disk size this might be one way to
bypass this problem.

On Tue, Aug 22, 2017 at 5:15 AM, Suman Raja <suman.raja(a)accenture.com>
wrote:

We have tried to install SEP(symantec endpoint protection) on bosh
deployed ubuntu 14.04(bosh-vcloud-esxi-ubuntu-trusty-go_agent) VM's
manually but it was not successful as SEP need more than 2GB free space
under "/" directory.

Is there any other way so we can use SEP in bosh deployed VM's.

Error Log:-
15:38:17.732511 Result Code: 0x80010803
15:38:17.732546 Result Message: FAIL - not enough disk space to
install update
15:38:17.732573 [Package Install - END]
15:38:17.732610 [Finalize Package Installs - START]
15:38:17.735686 Result Code: 0x00010000
15:38:17.735728 Result Message: OK
15:38:17.735761 Component Status Changes:

Bosh - creating an aws instance - merge two calls into one

ram sajja
 

Hello Every one,

we are currently using bosh version 262.3. The question I have is on how bosh provisions ec2 instances in AWS through bosh-aws-cpi.

To give a little context on how provisioning on AWS used to happen

In March, AWS Blog announced two new features we’re implementing:
Ability to enforce required tags on RunInstances with IAM policy
Ability to include tags on RunInstances with API and CLI

Which means, before this date all provisioning was done in two steps:

ec2 run-instances --image-id <ami-id> --count 1 --instance-type t2.micro --subnet-id <subnet-id>

ec2-create-tags <instanceid> --tag "Name=<name_value>" --tag "App=<app_value>" --tag "AppOwner=<app_owner_value>" --tag "Environment=<env_value>"

The new workflow assured that instance creation and tag management can be done in a single call.

ec2 run-instances --image-id <ami-id> --count 1 --instance-type t2.micro --subnet-id <subnet-id> --tag-specifications 'ResourceType=instance,Tags=[{Key=Name,Value=<name_value>},{Key=App,Value=<app_value>},{Key=AppOwner,Value=<app_owner_value>},{Key=Environment,Value=<env_value>}]'

Bosh ( tested with version 262.3 ) still seem to be provisioning instances in multiple calls instead of a single one. Bosh is issuing 1 api call just to create the instance, and then following that up with a 2nd api call to create-tags.

Does anyone know if this is addressed in newer versions of bosh ? I looked at the code but did not seem like it and am not sure if this can be easily done ? any thoughts ?

Thanks,
Ram

Problem with Azure Internal Load Balancer

Jonathan Stockley
 

Hi,
We have deployed BOSH 261.4 with Azure-CPI 260.5 with stemcell bosh-azure-hyperv-ubuntu-trusty-go_agent version 3363.27.
I have deployed a BOSH release of our own application that uses two VMs and an Azure Internal Load Balancer.

Everything works great for about an hour and then the ILB stops responding. The two VMs that are in the backend pool are still working fine and the health check probe URL is still responsive in both VMs.
However after the ILB stops responding, there is no sign that it is sending the health check probe.

I have been working with Microsoft Azure Support but so far we have not discovered any cause for this. It doesn’t help that there are no logs or diagnostics in Azure for an Internal LB, only for External LB.

As a comparison, I manually deployed two Ubuntu Trusty (14.04) VMs using the Azure marketplace and setup an ILB in front of them and it has been working for the past 3 days without a problem.

Has anyone else tried to use Azure Internal LB with BOSH?

Could it be that the Azure stemcell we are using has a problem?


Any help or suggestions would be most welcome.

Thanks,
Jo

Re: Bosh - creating an aws instance - merge two calls into one

Dmitriy Kalinin
 

hey,

we currently have two separate cpi methods for creating vms (create_vm) and
setting metadata on the vms (set_vm_metadata). create_vm call does not
receive necessary metadata to apply tags to the vm at creation time.
potentially such functionality could be added in future. i would recommend
adding an issue to
https://github.com/cloudfoundry-incubator/bosh-aws-cpi-release.

dmitriy

On Thu, Aug 31, 2017 at 4:02 PM, ram sajja <s_vrk(a)outlook.com> wrote:

Hello Every one,

we are currently using bosh version 262.3. The question I have is on how
bosh provisions ec2 instances in AWS through bosh-aws-cpi.

To give a little context on how provisioning on AWS used to happen

In March, AWS Blog announced two new features we’re implementing:
Ability to enforce required tags on RunInstances with IAM policy
Ability to include tags on RunInstances with API and CLI

Which means, before this date all provisioning was done in two steps:

ec2 run-instances --image-id <ami-id> --count 1 --instance-type t2.micro
--subnet-id <subnet-id>

ec2-create-tags <instanceid> --tag "Name=<name_value>" --tag
"App=<app_value>" --tag "AppOwner=<app_owner_value>" --tag
"Environment=<env_value>"

The new workflow assured that instance creation and tag management can be
done in a single call.

ec2 run-instances --image-id <ami-id> --count 1 --instance-type t2.micro
--subnet-id <subnet-id> --tag-specifications 'ResourceType=instance,Tags=[{
Key=Name,Value=<name_value>},{Key=App,Value=<app_value>},{
Key=AppOwner,Value=<app_owner_value>},{Key=Environment,
Value=<env_value>}]'

Bosh ( tested with version 262.3 ) still seem to be provisioning instances
in multiple calls instead of a single one. Bosh is issuing 1 api call just
to create the instance, and then following that up with a 2nd api call to
create-tags.

Does anyone know if this is addressed in newer versions of bosh ? I looked
at the code but did not seem like it and am not sure if this can be easily
done ? any thoughts ?

Thanks,
Ram

CF Summit EU Unconference - Registration Open; Talks & Sponsors Requested

Daniel Jones
 

Hi all,

You can now register for the (free!) Unconference
<https://www.eventbrite.co.uk/e/cf-summit-europe-2017-unconference-tickets-37837803890>
at CF Summit Europe 2017. It'll take place between 1800-2200 on Tuesday
10th October, in the same venue as the Summit, and will feature food,
drink, lightning talks, open space, and a pub quiz.

If you think you may attend, *please* register, so we can make sure we have
enough space, beer and food for everyone.

Would you like to *talk at the Unconference*? We're looking for lightning
talks (<= 10 minutes) to go along with the open space sessions.

If you'd like to talk then please fill in our Google Form:
https://goo.gl/forms/xB0beLDZ4Tk8AZjR2

We're open to novel talks, or cut-down versions of talks that didn't make
the cut for the Summit itself. I expect that a fair few engineering folks
will be in attendance, so excruciatingly technical talks are welcome!

We're also *looking for sponsors* - if your organisation is interested,
please contact Sara Lenz (slenz(a)anynines.com) for more information. Sponsor
benefits include top-of-agenda lightning talks, signage, and online
promotion.

Regards,
Daniel Jones - CTO
+44 (0)79 8000 9153
@DanielJonesEB <https://twitter.com/DanielJonesEB>
*EngineerBetter* Ltd <http://www.engineerbetter.com> - UK Cloud Foundry
Specialists

Bosh Director/CredHub API question

Michael Stancampiano
 

In CredHub documentation there are manifest identifiers defined with dot notation that seem to conform to the JSON objects for certificates (and other types) that can be specified in CredHub API calls. For example:
tls:
ca: ((database-tls.ca))
certificate: ((database-tls.certificate))
private_key: ((database-tls.private_key))

Does the CredHub API support the usage of the dot notation to retrieve a specific value (such as a private_key)? For example:
curl "https://example.com/api/v1/data?name=/database-tls.private_key"

Does the Bosh Director when processing this manifest sample make one call to CredHub and retrieve all 3 values, using ?name=/database-tls ?

No progress can be seen with bosh create-env

Ushani Balasooriya
 

When I tried to install Bosh Lite and executed the below step [2], it does not show any progress except the below [1] for few hours right now. Is it because of a network delay or anything wrong in my command? How can I know it is downloading correctly.

[1] Started validating
Downloading release 'bosh'...

[2]
$ bosh create-env ~/workspace/bosh-deployment/bosh.yml \
--state state.json \
--vars-store ./creds.yml \
-o ~/workspace/bosh-deployment/virtualbox/cpi.yml \
-o ~/workspace/bosh-deployment/virtualbox/outbound-network.yml \
-o ~/workspace/bosh-deployment/bosh-lite.yml \
-o ~/workspace/bosh-deployment/jumpbox-user.yml \
-v director_name=vbox \
-v internal_ip=192.168.56.6 \
-v internal_gw=192.168.56.1 \
-v internal_cidr=192.168.56.0/24 \
-v network_name=vboxnet0 \
-v outbound_network_name=NatNetwork

Re: No progress can be seen with bosh create-env

Ushani Balasooriya
 

Below is what I get for past few hours.

bosh create-env bosh-deployment/bosh.yml \
--state vbox/state.json \
-o bosh-deployment/virtualbox/cpi.yml \
-o bosh-deployment/virtualbox/outbound-network.yml \
-o bosh-deployment/bosh-lite.yml \
-o bosh-deployment/bosh-lite-runc.yml \
-o bosh-deployment/jumpbox-user.yml \
--vars-store vbox/creds.yml \
-v director_name="Bosh Lite Director" \
-v internal_ip=192.168.50.6 \
-v internal_gw=192.168.50.1 \
-v internal_cidr=192.168.50.0/24 \
-v outbound_network_name=NatNetwork
Deployment manifest: '/home/wso2/BOSH/bosh-deployment/bosh.yml'
Deployment state: 'vbox/state.json'

Started validating
Downloading release 'bosh'...

Re: No progress can be seen with bosh create-env

Ushani Balasooriya
 

I found the reason. I had CF DEV VM running on my machine. When I had quit it showed me progress of downloading being done.

Finished (00:02:20)
Validating release 'bosh'... Finished (00:00:00)
Downloading release 'bosh-virtualbox-cpi'... Finished (00:02:39)
Validating release 'bosh-virtualbox-cpi'... Finished (00:00:01)
Downloading release 'bosh-warden-cpi'...
....

When I try to save the environment with the alias vbox it gives Missing PEM block

Ushani Balasooriya
 

bosh -e 192.168.50.6 alias-env vbox --ca-cert vbox/creds.yml

Validating Director connection config:
Parsing certificate 1: Missing PEM block

Exit code 1


Please explain me the below command. What is the --path parameter? I do not have a director_ssl folder. Also Is my above command correct? I have a folder called vox and creds.yml inside it.
bosh -e 192.168.50.6 alias-env vbox --ca-cert <(bosh int vbox/creds.yml --path /director_ssl/ca)

Re: When I try to save the environment with the alias vbox it gives Missing PEM block

Ushani Balasooriya
 

Issue was I had extra ) at the end of the command.
bosh -e 192.168.50.6 alias-env vbox --ca-cert <(bosh int vbox/creds.yml --path /director_ssl/ca) should be
bosh -e 192.168.50.6 alias-env vbox --ca-cert <(bosh int vbox/creds.yml --path /director_ssl/ca

Re: When I try to save the environment with the alias vbox it gives Missing PEM block

Ushani Balasooriya
 

Pls ignoe prvious comment

Issue was a space before the ( bracer. Correct command is as below.

bosh -e 192.168.50.6 alias-env vbox --ca-cert <(bosh int vbox/creds.yml --path /director_ssl/ca)
Using environment '192.168.50.6' as anonymous user

Name Bosh Lite Director
UUID 575074fe-09db-4c88-8aae-eb8284b3d702
Version 263.2.0 (00000000)
CPI warden_cpi
Features compiled_package_cache: disabled
config_server: disabled
dns: disabled
snapshots: disabled
User (not logged in)

Succeeded

Unknown disk type '5GB' in consul instance group when

Karan Shukla
 

I've been trying to deploy Cloud Foundry on a local machine using Bosh Lite on a VM via cf-deployment.

According to the documentation, the following command should build Cloud Foundry

bosh -e 192.168.50.6 -d cf deploy cf-deployment.yml \
-o operations/bosh-lite.yml \
--vars-store deployment-vars.yml \
-v system_domain=bosh-lite.com

The process successfully completes the first thirty tasks or so, and then I run into the following error.

Error: Instance group 'consul' references an unknown disk type '5GB'

Anyone have some insight on what 'consul' is and how I can fix it? Seems to be related to cloud-config.yml but I'm not sure which one in particular I should be looking into (there's one for both cf-deployment and bosh-deployment).

Re: Unknown disk type '5GB' in consul instance group when

Dmitriy Kalinin
 

you might have to update your cloud config with one that cf-deployment
wants:

bosh -e 192.168.50.6 ucc <(wget -O-
https://raw.githubusercontent.com/cloudfoundry/cf-deployment/master/bosh-lite/cloud-config.yml
)

On Sun, Sep 17, 2017 at 10:39 PM, Karan Shukla <shuklak13(a)gmail.com> wrote:

I've been trying to deploy Cloud Foundry on a local machine using Bosh
Lite on a VM via cf-deployment.

According to the documentation, the following command should build Cloud
Foundry

bosh -e 192.168.50.6 -d cf deploy cf-deployment.yml \
-o operations/bosh-lite.yml \
--vars-store deployment-vars.yml \
-v system_domain=bosh-lite.com

The process successfully completes the first thirty tasks or so, and then
I run into the following error.

Error: Instance group 'consul' references an unknown disk type '5GB'

Anyone have some insight on what 'consul' is and how I can fix it? Seems
to be related to cloud-config.yml but I'm not sure which one in particular
I should be looking into (there's one for both cf-deployment and
bosh-deployment).

/config/blobs.yml: no such file or directory

Ushani Balasooriya
 

It seems the config/blolbs.yml is not available. How can I resolve this?


bosh -e vbox add-blob /home/wso2/Downloads/jdk-8u144-linux-x64.tar.gz oraclejdk/jdk-8u144-linux-x64.tar.gz
Tracking blob:
Reading blobs index:
Opening file /home/wso2/newBOSH/config/blobs.yml:
open /home/wso2/newBOSH/config/blobs.yml: no such file or directory

Re: /config/blobs.yml: no such file or directory

Ushani Balasooriya
 

Executing bosh init-release command created it for me.

not running after update. Review logs for failed jobs - deploy fails

Ushani Balasooriya
 

bosh -e vbox -d wso2is deploy wso2is-manifest.yml.

This is what I get,

Task 29 | 13:24:38 | Deprecation: Ignoring cloud config. Manifest contains 'networks' section.
Task 29 | 13:24:38 | Preparing deployment: Preparing deployment (00:00:00)
Task 29 | 13:24:38 | Preparing package compilation: Finding packages to compile (00:00:00)
Task 29 | 13:24:38 | Updating instance wso2is: wso2is/ba4e43c5-9202-4f60-aa74-d0bdef66af81 (0) (canary)



(00:03:16)
Error: 'wso2is/ba4e43c5-9202-4f60-aa74-d0bdef66af81 (0)' is not running after update. Review logs for failed jobs: wso2is
Task 29 | 13:27:54 | Error: 'wso2is/ba4e43c5-9202-4f60-aa74-d0bdef66af81 (0)' is not running after update. Review logs for failed jobs: wso2is


===========

After spending sometime learnt to check debug logs and When I checked the debug logs it shows only this,

Mon Sep 18 13:27:29 UTC 2017 Kicking off ctl script as root with start
Mon Sep 18 13:27:32 UTC 2017 JAVA_HOME: /var/vcap/packages/oraclejdk/jdk1.8.0_144/
Mon Sep 18 13:27:32 UTC 2017 JAVA_BINARY: /var/vcap/packages/oraclejdk/jdk1.8.0_144//bin/java

I googled and found to increase the canary_watch_time and update_watch_time as a solution. But still it didnt work

I see 2 // in JAVA_BINARY: /var/vcap/packages/oraclejdk/jdk1.8.0_144//bin/java and cannot figure out how it comes. can it be the reason? I removed 1 / from the ctl.erb as well. But no luck.

Re: not running after update. Review logs for failed jobs - deploy fails

Ushani Balasooriya
 

Could not figure out any solution. Created the same project from scratch with same configs and it started working