Date   
Re: Option -N for bosh no longer available with bosh-cli v2?

Tyler Schultz
 

You may want to lobby Dmitriy to add the '--no-track' feature to the v2
cli. He is the product owner and prioritizes our backlog.

As a workaround, you can run `$ bosh -e my-env -d my-dep deploy my-dep *&*`.
The ampersand will cause the deploy to run in the background, and your
script will continue on.

On Thu, Jul 13, 2017 at 8:21 AM, Holger Oehm <holger.oehm(a)sap.com> wrote:

Well, it was there in bosh cli v1.

And I am aware of the Ctrl-C thing. But what I want to do is run
bosh -nN in a script from concourse. (And it should run asynchronously
because the bosh task will be to update concourse (the same instance
that runs the script)).

On 07/13/2017 04:16 PM, Tyler Schultz wrote:

There is no --no-track option, but you can ctl-c and the task will
continue. 'bosh task 123' will reattach to the output.
--Tyler

On Thu, Jul 13, 2017 at 5:17 AM Holger Oehm <holger.oehm(a)sap.com <mailto:
holger.oehm(a)sap.com>> wrote:

Hi,

is something similar to the -N (--no-track) option in bosh v1 still
available in bosh-cli v2? I didn't find it in the documentation or in
the output of bosh help.

Best Regards,
Holger.

Re: Option -N for bosh no longer available with bosh-cli v2?

Holger Oehm
 

Well, it was there in bosh cli v1.

And I am aware of the Ctrl-C thing. But what I want to do is run
bosh -nN in a script from concourse. (And it should run asynchronously
because the bosh task will be to update concourse (the same instance
that runs the script)).

On 07/13/2017 04:16 PM, Tyler Schultz wrote:
There is no --no-track option, but you can ctl-c and the task will
continue. 'bosh task 123' will reattach to the output.
--Tyler

On Thu, Jul 13, 2017 at 5:17 AM Holger Oehm <holger.oehm(a)sap.com
<mailto:holger.oehm(a)sap.com>> wrote:

Hi,

is something similar to the -N (--no-track) option in bosh v1 still
available in bosh-cli v2? I didn't find it in the documentation or in
the output of bosh help.

Best Regards,
Holger.

Re: How to Deploy a CF Tile in BOSH

Mikey Boldt
 

Hi Imesh,

Just to be explicit, a tile is *Pivotal* CF-specific packaging around your
components. Since BOSH lite and PCF Dev do not have Pivotal's Ops Manager,
you cannot deploy a tile on them.

You should work on implementing your service broker and getting your WSO2
middleware packaged into a BOSH release outside of a tile first. One
approach you could take is to implement your service broker as a CF app and
develop it against PCF Dev, and develop your WSO2 middleware BOSH release
against BOSH lite. Even if your end goal is a tile, you will need these
components as input to Tile Generator, and developing them outside of a
tile will let you debug faster. Tile Generator doesn't help you with
developing these components (not yet, at least).

Once those components are solid, you can wrap them up in a tile using Tile
Generator. (And at some point you'll need to talk to PIvotal if you want
your tile published on Pivotal Network...the sooner the better, really.)

Hope that helps,
Mikey

On Fri, Jun 30, 2017 at 4:11 AM Imesh Gunaratne <imesh.gunaratne(a)gmail.com>
wrote:

Hi Alex,

Thank you very much for your quick response! Let me explain things in
detail.

My attempt to is to implement a sample service broker and see how services
work on CloudFoundry (CF). The end goal of this process is to implement
service brokers for WSO2 middleware similar to Redis, MySQL and other
service brokers currently available on the Pivotal network.

As I understood, to do this I need to things:
1. A service broker API
2. WSO2 middleware deployment automation

My plan is to deploy the service broker API on CF as an application and
deploy WSO2 middleware on BOSH using a Tile. The idea is to make it work on
any CF environment (on-premise & public cloud).

I started by generating a sample Tile using the Tile Generator and tried
to deploy it on AWS by setting up a CF environment using the CloudFormation
templates given. There I found that CF itself requires nearly 45 EC2
instances and thought of using BOSH lite and PCF Dev instead.

Now I have setup BOSH lite and PCF Dev on my local machine and trying to
deploy the above sample Tile on it. This sample Tile has a simple bash
script with an echo command. When I build the Tile, I can see that it is
generating a BOSH release and a .pivotal file containing the BOSH release
to be deployed via the Ops Manager.

Now, as I do not have Ops Manager running locally I tried deploying the
BOSH release generated by the tile build in BOSH lite. I also tried setting
up an Ops Manager locally but I could not find much information that and
its Git repository. Really appreciate your thoughts on this.

Thanks
Imesh

Re: Option -N for bosh no longer available with bosh-cli v2?

Tyler Schultz
 

There is no --no-track option, but you can ctl-c and the task will
continue. 'bosh task 123' will reattach to the output.
--Tyler

On Thu, Jul 13, 2017 at 5:17 AM Holger Oehm <holger.oehm(a)sap.com> wrote:

Hi,

is something similar to the -N (--no-track) option in bosh v1 still
available in bosh-cli v2? I didn't find it in the documentation or in
the output of bosh help.

Best Regards,
Holger.

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Arpit Sharma
 

No. Volume is not created on cinder level. Checked schedular logs and found that there is no enough host available. I have tried manually to create disk on cinder but unable to do it. I have checked and found that base machine havin around 5gb left. I think due to this I am facing issue. Let me provide some space to cinder and will try again.

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Johannes Hiemer
 

Hi Arpit,
can you see the volume being created in OS?

On Thu, 13 Jul 2017 at 15:38 Arpit Sharma <arpitvipulsharma(a)gmail.com>
wrote:

Hi Johannes,

Yesterday I have logged ticket for the same. I received response from Mr.
Mauro Morales that we can try to repack the stemcell with bosh-cli. After
that I have tried with this idea and followed this link
https://bosh.io/docs/repack-stemcell.html
finally I successed in changing hypervisor type to qemu. Now I am able to
launch VM with image. I have reduced flavor from x1.large to m1.medium. But
I am again getting new error

Started deploying
Creating VM for instance 'bosh/0' from stemcell
'197a22a9-0bc1-4365-9a43-035b0983179c'... Finished (00:01:15)
Waiting for the agent on VM 'b8db1076-2fd3-4d5e-a42b-2f539dc73468' to be
ready... Finished (00:08:26)
Creating disk... Failed (00:00:01)
Failed deploying (00:09:46)

Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

Deploying:
Creating instance 'bosh/0':
Updating instance disks:
Updating disks:
Deploying disk:
Creating disk with size 32768, cloudProperties property.Map{},
instanceID b8db1076-2fd3-4d5e-a42b-2f539dc73468:
CPI 'create_disk' method responded with error:
CmdError{"type":"Bosh::Clouds::CloudError","message":"Volume
`f303c75a-829b-4206-814c-f0adb913a581' state is error, expected
available","ok_to_retry":false}

Exit code 1


Can you help me with this?

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Arpit Sharma
 

I have reduced size from 32 GB to 22 GB. Let me try with this.

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Arpit Sharma
 

I am also sure that this is due to cinder insufficient space as I have seen logs. Can I choose small flavor for the same?

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Arpit Sharma
 

Hi Johannes,

Yesterday I have logged ticket for the same. I received response from Mr. Mauro Morales that we can try to repack the stemcell with bosh-cli. After that I have tried with this idea and followed this link
https://bosh.io/docs/repack-stemcell.html
finally I successed in changing hypervisor type to qemu. Now I am able to launch VM with image. I have reduced flavor from x1.large to m1.medium. But I am again getting new error

Started deploying
Creating VM for instance 'bosh/0' from stemcell '197a22a9-0bc1-4365-9a43-035b0983179c'... Finished (00:01:15)
Waiting for the agent on VM 'b8db1076-2fd3-4d5e-a42b-2f539dc73468' to be ready... Finished (00:08:26)
Creating disk... Failed (00:00:01)
Failed deploying (00:09:46)

Stopping registry... Finished (00:00:00)
Cleaning up rendered CPI jobs... Finished (00:00:00)

Deploying:
Creating instance 'bosh/0':
Updating instance disks:
Updating disks:
Deploying disk:
Creating disk with size 32768, cloudProperties property.Map{}, instanceID b8db1076-2fd3-4d5e-a42b-2f539dc73468:
CPI 'create_disk' method responded with error: CmdError{"type":"Bosh::Clouds::CloudError","message":"Volume `f303c75a-829b-4206-814c-f0adb913a581' state is error, expected available","ok_to_retry":false}

Exit code 1


Can you help me with this?

Option -N for bosh no longer available with bosh-cli v2?

Holger Oehm
 

Hi,

is something similar to the -N (--no-track) option in bosh v1 still
available in bosh-cli v2? I didn't find it in the documentation or in
the output of bosh help.

Best Regards,
Holger.

Option -N for bosh no longer available with bosh-cli v2?

Holger Oehm <holger@...>
 

Hi,

is something similar to the -N (--no-track) option in bosh v1 still available in bosh-cli v2? I didn't find it in the documentation or in the output of bosh help.

Best Regards,
Holger.

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Johannes Hiemer
 

Hi Arpit,
thanks for your kind words. This should be the right place, where you can
open a ticket:
https://github.com/cloudfoundry-incubator/bosh-openstack-cpi-release/issues

On Wed, 12 Jul 2017 at 16:45 Arpit Sharma <arpitvipulsharma(a)gmail.com>
wrote:

Hi Johannes,

Thanks for your response. Let me switch to other hardware. Heartly thanks
for your support. Hope will be in touch again and again. You have very
sound knowledge of Cloud automation and different other tools. Can you
share the link for this ticket opening? I think i need to open on pivotal...

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Arpit Sharma
 

Hi Johannes,

Thanks for your response. Let me switch to other hardware. Heartly thanks for your support. Hope will be in touch again and again. You have very sound knowledge of Cloud automation and different other tools. Can you share the link for this ticket opening? I think i need to open on pivotal...

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Johannes Hiemer
 

Hi Arpit,
I would switch to a different hardware and in the meanwhile open a ticket
to request configuration of this element as an option on the
bosh_openstack_cpi.

Best,
Johannes

On Wed, 12 Jul 2017 at 16:18 Arpit Sharma <arpitvipulsharma(a)gmail.com>
wrote:

Hi Johannes,

Any suggestion? I am waiting for your valuable suggestions. we caught the
problem but still dont have any solution. I can switch to other hardware if
you think it will be better.

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Arpit Sharma
 

Hi Johannes,

Any suggestion? I am waiting for your valuable suggestions. we caught the problem but still dont have any solution. I can switch to other hardware if you think it will be better.

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Arpit Sharma
 

I want that whenever I upload stemcell in openstack, hypervisor_type should be qemu.

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Arpit Sharma
 

Yes... I have changed hypervisor type from kvm to qemu after it uploaded by bosh env create command. Now image is working fine if i swap an instance. But In bosh env command hypervisor type is still kvm. How we can change with bosh env create command itself.

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Johannes Hiemer
 

Hi Arpit,
that means it works?

On Wed, 12 Jul 2017 at 14:03 Arpit Sharma <arpitvipulsharma(a)gmail.com>
wrote:

Hey Johannes,

I stucked here. I dont have any developer background. I am unable to find
solution on this. stemcells are using kvm as hypervisor type while I am
using qemu as a hypervisor in openstack. I want to change hypervisor_type
to qemu for these stemcells. I have tested and found that after changing,
these stemcells are working ok.

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Arpit Sharma
 

Hey Johannes,

I stucked here. I dont have any developer background. I am unable to find solution on this. stemcells are using kvm as hypervisor type while I am using qemu as a hypervisor in openstack. I want to change hypervisor_type to qemu for these stemcells. I have tested and found that after changing, these stemcells are working ok.

Re: Creating vm with stemcell failed.... No valid host was found. There are not enough hosts available..Filter ImagePropertiesFilter returned 0 hosts

Johannes Hiemer
 

Then take a look here:
https://github.com/cloudfoundry-incubator/bosh-openstack-cpi-release/issues/39

On Wed, 12 Jul 2017 at 10:34 Arpit Sharma <arpitvipulsharma(a)gmail.com>
wrote:

Johannes!

Custom Properties for bosh-openstack-kvm-centos-7-go_agent-raw/3421.11

os_distro: centos
Tags
hypervisor_type:kvm
version: 3421.11
file: /v2/images/103cb62d-c40b-481b-b821-74ec7fb9e9a9/file
auto_disk_config: true
os_type: linux
Virtual Size
schema: /v2/schemas/image

Custom Properties for samestemcellmanually
schema : /v2/schemas/image
Virtual Size
file: /v2/images/3e8eadc1-1171-49a7-affb-76b819105c9c/file
Tags


I think we are going in right direction. Here I am using qemu as a
hypervisor. In nova.conf , I defined virt_type = qemu. I am doing all these
on my personal workstation.