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:

Hi,

As the error says compilation block in missing in manifest.

Add compilation block and redeploy.

Thanks
Ronak

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 ?

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:

Hi All,

Check your command according to this. Replace values according to your environment.




bosh create-env bosh-deployment/bosh.yml \
--state=state.json \
--vars-store=creds.yml \
-o bosh-deployment/openstack/cpi.yml \
-v director_name=bosh-1 \
-v internal_cidr=192.168.1.0/24 \
-v internal_gw=192.168.1.1 \
-v internal_ip=192.168.1.7 \
-v auth_url=http://10.100.10.151:5000/v2.0 \
-v az=nova \
-v default_key_name=mykey \
-v default_security_groups=[default] \
-v net_id=54093c23-1a21-4e1c-ab3d-88a70986bf38 \
-v openstack_password=4b61a9e4bcc64b5d \
-v openstack_username=admin \
-v openstack_domain=Default \
-v openstack_project=admin \
-v private_key=/root/.ssh/privroot_rsa \
-v region=RegionOne

Hi,

I have deployed bosh successfully. But I have not checked further. I was trying to install cloudfoundy. But due to limited resources, I was unable to do it.

Was able to resolve this issue. Virtualbox 5.1 was having some issues with the Secure boot option on my Ubuntu machine. Reverting to VB5.0 version fixed the above error. I also ran into another issue, wherein I had to enable Intel Virtualization on my BIOS for Bosh to succeed in creating Virtualbox VMs. Stackoverflow has some useful posts on each of these issues.

Hi

When trying to execute bosh2 create-env, I am getting the following error. I was able to setup the bosh director on my Mac but its giving me following trouble when following the same steps on by Ubuntu machine. Steps that I followed: http://www.starkandwayne.com/blog/bosh-lite-on-virtualbox-with-bosh2/

Looking forward to your help.

$ bosh create-env bosh.yml --state ./state.json -o virtualbox/cpi.yml -o virtualbox/outbound-network.yml -o bosh-lite.yml -o bosh-lite-runc.yml -o jumpbox-user.yml --vars-store ./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

Deploying:
Creating instance 'bosh/0':
Creating VM:
Creating vm with stemcell cid 'sc-c03d5f5c-8529-4329-6192-f57289daf395':
CPI 'create_vm' method responded with error: CmdError{"type":"Bosh::Clouds::CloudError","message":"Creating VM with agent ID '{{286d04ec-a153-4364-7545-ce8bb289f719}}': Enabling networks: Retried '30' times: Running command: 'VBoxManage hostonlyif create', stdout: '', stderr: '0%!.(MISSING).\nProgress state: NS_ERROR_FAILURE\nVBoxManage: error: Failed to create the host-only adapter\nVBoxManage: error: VBoxNetAdpCtl: Error while adding new interface: VBoxNetAdpCtl: ioctl failed for /dev/vboxnetctl: Inappropriate ioctl for devic\nVBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface\nVBoxManage: error: Context: \"RTEXITCODE handleCreate(HandlerArg*)\" at line 94 of file VBoxManageHostonly.cpp\n': exit status 1","ok_to_retry":false}

Exit code 1

Regards
Atish

Hi All,

I am trying to deploy CF on openstack using bosh .
I am following the documentation https://bosh.io/docs/init-openstack.html

When I execute :

bosh create-env bosh-deployment/bosh.yml --state=state.json

--vars-store=creds.yml -o bosh-deployment/openstack/cpi.yml -v
director_name=bosh-1 -v internal_cidr=172.10.0.0/24 -v
internal_gw=172.10.0.1 -v internal_ip=172.10.0.6 -v auth_url=
https://mycontrollerip:5000/v2.0 -v az=test -v
default_key_name=mykeypairname -v default_security_groups=[bosh,CF] -v
net_id=3a374103-4b4a-49aa-b2e7-d113cb6939c3 -v
openstack_password=mypassword -v openstack_username=myusername -v
openstack_project=projectname -v private_key=/path/to/mykeypair.pem -v
region=RegionOne -v openstack_domain=test -v tenant=projectname

I get error :

Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)
Deploying:
Creating instance 'bosh/0':
Creating VM:
Creating vm with stemcell cid 'a8833ec1-7b3c-4904-a522-329ab1233302':
CPI 'create_vm' method responded with error:
CmdError{"type":"Bosh::Clouds::CloudError","message":"OpenStack API service
not found error: Expected([201]) \u003c=\u003e Actual(404 Not
Found)\nexcon.error.response\n :body =\u003e
\"{\\\"NeutronError\\\": {\\\"message\\\": \\\"Security group
0ccd1f3f-a064-49d7-899a-1ea450c518fa does not exist\\\", \\\"type\\\":
\\\"SecurityGroupNotFound\\\", \\\"detail\\\": \\\"\\\"}}\"\n :cookies
=\u003e [\n ]\n :headers =\u003e {\n \"Content-Length\"
=\u003e \"146\"\n \"Content-Type\" =\u003e
\"application/json; charset=UTF-8\"\n \"Date\" =\u003e
\"Sat, 19 Aug 2017 13:28:29 GMT\"\n \"X-Openstack-Request-Id\" =\u003e
\"req-8b903ed9-7c62-4433-b43b-cd784fd0fbeb\"\n }\n :host =\u003e
\"controllerip\"\n :local_address =\u003e \"172.10.0.15\"\n :local_port
=\u003e 39862\n :path =\u003e \"/v2.0/ports\"\n :port
=\u003e 9696\n :reason_phrase =\u003e \"Not Found\"\n :remote_ip
=\u003e \"132.186.17.131\"\n :status =\u003e 404\n :status_line
=\u003e \"HTTP/1.1 404 Not Found\\r\\n\"\n\nCheck task debug log for
details.","ok_to_retry":false}
Exit code 1

Can anyone help me with this ?

Thanks,
Gowri

hi ,

I tried with the above ( added -v tenant=mytenantname) , but I still get the following error :
creating stemcell (bosh-openstack-kvm-ubuntu-trusty-go_agent 3421.9):
CPI 'create_stemcell' method responded with error: CmdError{"type":"InvalidCall","message":"Arguments are not correct, details: 'Invalid OpenStack cloud properties: #\u003cMembrane::SchemaValidationError: { openstack =\u003e { tenant =\u003e Missing key } }\u003e'","ok_to_retry":false}

If i exclude -v openstack_project it says
- Expected to find variables:
- openstack_project
Any suggestions ?

Hi - the cloudfoundry/bosh repository is a regular BOSH release, so once
you have made your changes, you can create a new release tarball with `bosh
create-release --tarball=/tmp/bosh-dev.tgz`.

If you used the `bosh create-env` to deploy your director, you can then
update the manifest file and replace bosh release's URL with a local file
path (`file:///tmp/bosh-dev.tgz`), followed by re-running your `bosh
create-env ...` command.

If you used `bosh deploy`, you can use `bosh upload-release
/tmp/bosh-dev.tgz` to upload, then update your director's manifest file
with the new version number, and then rerun your `bosh deploy ...` command.

Here are a few links which I think may be helpful to you to learn more
background and a few additional scenarios you might run into...

- create-release command – http://bosh.io/docs/cli-v2.html#create-release
- general release management workflows –
http://bosh.io/docs/create-release.html
- some general release scenarios –
http://bosh.io/docs/managing-releases.html

Danny

On Thu, Aug 17, 2017 at 7:54 AM, PARTHASARATHI KUNDU <
parthasarathi_kundu(a)yahoo.com> wrote:

After modifying code of https://github.com/cloudfoundry/bosh.git, I can
create and update the bosh release using bosh cli . How can I deploy the
changes(newly updated release) of bosh director ?

--
Danny Berger

After modifying code of https://github.com/cloudfoundry/bosh.git, I can create and update the bosh release using bosh cli . How can I deploy the changes(newly updated release) of bosh director ?

are you still deploying? I have installed director on ocata, but when 'bosh deploy', I hava the issue 'Compiling packages incompatible character encodings: UTF-8 and US-ASCII'

bosh-gen is getting closer to v1.0. For five years it has been the most
awesome tool for creating new BOSH releases, extracting packages and jobs
from other releases, and more.

Today it adds the following bosh2 improvements:


- extract-job and extract-pkg commands use bosh add-blob for blobs
- extract-job and extract-pkg commands correctly glob for many files
across both src/ and blobs/ directories
- If bosh2 is installed then it is used; else assumes bosh is the latest
bosh2 CLI
- gem install bosh-gen will no longer install old bosh_cli gem and its
old bosh CLI.

To upgrade:

gem install bosh-gen
gem uninstall bosh_cli # whilst you're in the mood for cleaning up


--
Dr Nic Williams
Stark & Wayne LLC
http://starkandwayne.com
+61 437 276 076
twitter @drnic

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

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?

Hi,

I am trying to set up diego on bosh-lite using the following document
https://github.com/cloudfoundry/diego-release/tree/develop/examples/bosh-lite
.
Here is a series of issues I have faced which finally has lead to the error
"the requested IP is already allocated' in 'create_vm' CPI method".

First error which I hit was 'Error 100: can't alloc thread" and the bosh
deployment just hanged finally I had to manually kill this process.

As a next step I tried re deploying diego but that hit another set of
errors as follows
tar/f2ea61c537d8eb8cb2d691ce51e8516b28fa5bb7: CPI error
'Bosh::Clouds::CloudError' with message 'Creating VM with agent ID
'a8b3abd7-6a37-4ac9-b439-e12cb1b9d830': Creating container: the requested
IP is already allocated' in 'create_vm' CPI method (00:00:00)
Failed compiling packages >
apparmor/d2a9bb24b85a144e874e7627a5fefb4e9b8b30f3: CPI error
'Bosh::Clouds::CloudError' with message 'Creating VM with agent ID
'1a2f4b8a-28ca-409f-92da-6b5caf2b1875': Creating container: the requested
IP is already allocated' in 'create_vm' CPI method (00:00:00)
Failed compiling packages >
iptables/70cd40ad87371de73d6bdfc34967e94422fc2cc4: CPI error
'Bosh::Clouds::CloudError' with message 'Creating VM with agent ID
'd643d43d-6e93-481a-b11f-48b506f738ab': Creating container: the requested
IP is already allocated' in 'create_vm' CPI method (00:00:00)

Error 100: CPI error 'Bosh::Clouds::CloudError' with message 'Creating VM
with agent ID 'a8b3abd7-6a37-4ac9-b439-e12cb1b9d830': Creating container:
the requested IP is already allocated' in 'create_vm' CPI method


As a next steps when I list bosh vms I see 3 compilation vms. Suspecting
these vms could be the cause of the problem I have been trying to delete
these vms. While on the CLI I get a confirmation that the VMs have been
deleted, however they are still present when I run bosh vms.

Now I have no more steps left and I am stuck with the error "CPI error
'Bosh::Clouds::CloudError' the requested IP is already allocated' in
'create_vm' CPI method" and need advice/help in successfully deploying
diego.

Regards
Hachis

We are offering free passes for contributors to the project again for the
CF Summit Europe coming up on October 11 and 12 in Basel Switzerland
<https://www.cloudfoundry.org/event/europe-2017/>. This code can be used by
anyone that is a contributor to a Cloud Foundry or BOSH project. We
consider contributions to be project leads, dedicated committers or even if
you have sent in a pull request to one of the projects. Use of the code is
on the honor system... ;-)
Register here:
https://www.regonline.com/registration/Checkin.aspx?EventID=1980409 Code:
CFEU17CONT Feel free to reach out to me or to events(a)cloudfoundry.org if
you have any questions. See you there!

-chip
--
Chip Childers
CTO, Cloud Foundry Foundation
1.267.250.0815

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?

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?