Date   

Re: RethinkDB BOSH Release

Rob Day-Reynolds <rdayreynolds@...>
 

On a first look, it looks like it could be nice to use links (
https://bosh.io/docs/links.html) to get the addresses of the other servers
in the cluster. So rather than using a property (
https://github.com/cloudfoundry-community/rethinkdb-boshrelease/blob/master/jobs/rethinkdb/spec#L13),
you could reference the link for that job (using something like
https://bosh.io/docs/links.html#templates) in your job templates. This
would allow for greater flexibility in network usage (allowing both manual
and dynamic networks and no longer requiring static ip allocation), and
reduce the complexity of deployment manifests (along with making them more
consistent across IaaSes). I don't know RethinkDB well enough to make any
suggestions on the exact setup scripts for it though. :)

-Rob

On Thu, Apr 20, 2017 at 4:48 AM, Leandro David Cacciagioni <
leandro.21.2008(a)gmail.com> wrote:

Guys,

I have created a RethinkDB bosh release in here: https://github.com/
cloudfoundry-community/rethinkdb-boshrelease can you please take a look
and tell me if there is anything wrong or what could I do different to
improve it?

I hope that what's already there works for some of you.

Thanks,
Leandro.-

PS: Riak release is possibly coming this week also.


--
Thanks,
RDR


RethinkDB BOSH Release

Leandro David Cacciagioni
 

Guys,

I have created a RethinkDB bosh release in here:
https://github.com/cloudfoundry-community/rethinkdb-boshrelease can you
please take a look and tell me if there is anything wrong or what could I
do different to improve it?

I hope that what's already there works for some of you.

Thanks,
Leandro.-

PS: Riak release is possibly coming this week also.


Re: error: VT-x is not available (VERR_VMX_NO_VMX)

Adrian.Kurt@...
 

I suggest to try to run your bosh-lite vm from the same host OS your starting your Ubuntu vm.
If you connect both to the same virtual network you can interact with your bosh-lite from the Ubuntu machine.

It is possible to nest virtualization but it's not recommended. You would have to enable the virtualization inside the advanced cpu config of virtualbox.

-----Original Message-----
From: DONG ZHOU [mailto:wlbcheng(a)gmail.com]
Sent: Donnerstag, 20. April 2017 03:14
To: cf-bosh(a)lists.cloudfoundry.org
Subject: [cf-bosh] Re: error: VT-x is not available (VERR_VMX_NO_VMX)

Thank you Tushar, I have checked BIOS and virtualbox setting, all looks as expected.
But the issue persistence.

My test environment is i installed Ubuntu in a virtualbox on my local PC. and now i'm going to install BOTH-LITE into the Ubuntu. (both is trying to startup VMs in the Ubuntu, then i get the error) There is a hint from internet that CPU can not be nested virtual.
Is this true?
If there is any way to overcome this limitation?

Thank you.


Re: error: VT-x is not available (VERR_VMX_NO_VMX)

DONG ZHOU
 

Thank you Tushar, I have checked BIOS and virtualbox setting, all looks as expected.
But the issue persistence.

My test environment is i installed Ubuntu in a virtualbox on my local PC. and now i'm going to install BOTH-LITE into the Ubuntu. (both is trying to startup VMs in the Ubuntu, then i get the error)
There is a hint from internet that CPU can not be nested virtual.
Is this true?
If there is any way to overcome this limitation?

Thank you.


Re: error: VT-x is not available (VERR_VMX_NO_VMX)

DONG ZHOU
 

Thank you Tushar, I have checked BIOS and virtualbox setting, all looks as expected.
But the issue persistence.

My test environment is i installed Ubuntu in a virtualbox on my local PC. and now i'm going to install BOTH-LITE into the Ubuntu. (both is trying to startup VMs in the Ubuntu, then i get the error)
There is a hint from internet that CPU can not be nested virtual.
Is this true?
If there is any way to overcome this limitation?

Thank you.


Re: error: VT-x is not available (VERR_VMX_NO_VMX)

Tushar Dadlani
 

On Tue, Apr 18, 2017 at 2:12 AM DONG ZHOU <wlbcheng(a)gmail.com> wrote:

Dear Experts,

We are going to install CF by BOSH-Lite, i have vagrant_1.9.3_x86_64 and
virtualbox-5.1_5.1.18 installed on Ubuntu 14.

When i try to vagrant up --provider=virtualbox follow the guide below, i
get the error message that VM can not created.
Could you please advise how can i fix this?


https://github.com/cloudfoundry/bosh-lite/blob/master/README.md#install-bosh-lite

~/workspace/bosh-lite$ vagrant up --provider=virtualbox

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'cloudfoundry/bosh-lite' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "5fa64433-4b6a-4b81-9d14-fb7fb2e59f8b", "--type",
"headless"]

Stderr: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component
ConsoleWrap, interface IConsole


error: VT-x is not available (VERR_VMX_NO_VMX)

DONG ZHOU
 

Dear Experts,

We are going to install CF by BOSH-Lite, i have vagrant_1.9.3_x86_64 and virtualbox-5.1_5.1.18 installed on Ubuntu 14.

When i try to vagrant up --provider=virtualbox follow the guide below, i get the error message that VM can not created.
Could you please advise how can i fix this?

https://github.com/cloudfoundry/bosh-lite/blob/master/README.md#install-bosh-lite

~/workspace/bosh-lite$ vagrant up --provider=virtualbox

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'cloudfoundry/bosh-lite' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: hostonly
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "5fa64433-4b6a-4b81-9d14-fb7fb2e59f8b", "--type", "headless"]

Stderr: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole


Re: Error while creating bosh release on 'learn-bosh-release' project

Tushar Dadlani
 

Hey,

Can you outline the steps you followed and what OS are you running this on
?

Looks like your bosh target is incorrectly set up . What's the output of
"bosh status" command?

- Tushar

On Fri, Apr 14, 2017 at 7:50 AM Akshay Kapoor <akapoor87(a)gmail.com> wrote:

Hello

I have just started evaluating Bosh and CF and can't just get past the
bosh release creation process for 'learn-bosh-release' project repo. I get
the following error on my machine and don't find any support or information
on google/stackoverflow for this

Syncing blobs...
/usr/lib/ruby/2.0.0/fileutils.rb:349:in `symlink': Protocol error -
(/home/vagrant/workspace/learn-bosh-release/.blobs/c8a000f75b6a6f60d9fb727f8076ec9171e14c20,
/home/vagrant/workspace/learn-bosh-release/blobs/ruby/bundler-1.6.3.gem)
(Errno::EPROTO)
from /usr/lib/ruby/2.0.0/fileutils.rb:349:in `block in ln_s'
from /usr/lib/ruby/2.0.0/fileutils.rb:1568:in `fu_each_src_dest0'
from /usr/lib/ruby/2.0.0/fileutils.rb:347:in `ln_s'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/blob_manager.rb:344:in
`install_blob'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/blob_manager.rb:235:in
`block in process_index'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/blob_manager.rb:214:in
`each_pair'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/blob_manager.rb:214:in
`process_index'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/blob_manager.rb:157:in
`sync'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/commands/release/create_release.rb:146:in
`dirty_blob_check'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/commands/release/create_release.rb:82:in
`create_from_spec'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/commands/release/create_release.rb:51:in
`create'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/command_handler.rb:57:in
`run'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/runner.rb:59:in `run'
from /var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/bin/bosh:19:in
`<top (required)>'
from /usr/local/bin/bosh:23:in `load'
from /usr/local/bin/bosh:23:in `<main>'


Can someone please guide me what I am doing wrong ?


Regards,
Akshay


Error while creating bosh release on 'learn-bosh-release' project

Akshay Kapoor <akapoor87@...>
 

Hello

I have just started evaluating Bosh and CF and can't just get past the bosh
release creation process for 'learn-bosh-release' project repo. I get the
following error on my machine and don't find any support or information on
google/stackoverflow for this

Syncing blobs...
/usr/lib/ruby/2.0.0/fileutils.rb:349:in `symlink': Protocol error -
(/home/vagrant/workspace/learn-bosh-release/.blobs/c8a000f75b6a6f60d9fb727f8076ec9171e14c20,
/home/vagrant/workspace/learn-bosh-release/blobs/ruby/bundler-1.6.3.gem)
(Errno::EPROTO)
from /usr/lib/ruby/2.0.0/fileutils.rb:349:in `block in ln_s'
from /usr/lib/ruby/2.0.0/fileutils.rb:1568:in `fu_each_src_dest0'
from /usr/lib/ruby/2.0.0/fileutils.rb:347:in `ln_s'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/blob_manager.rb:344:in
`install_blob'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/blob_manager.rb:235:in
`block in process_index'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/blob_manager.rb:214:in
`each_pair'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/blob_manager.rb:214:in
`process_index'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/blob_manager.rb:157:in
`sync'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/commands/release/create_release.rb:146:in
`dirty_blob_check'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/commands/release/create_release.rb:82:in
`create_from_spec'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/commands/release/create_release.rb:51:in
`create'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/command_handler.rb:57:in
`run'
from
/var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/lib/cli/runner.rb:59:in `run'
from /var/lib/gems/2.0.0/gems/bosh_cli-1.3262.24.0/bin/bosh:19:in
`<top (required)>'
from /usr/local/bin/bosh:23:in `load'
from /usr/local/bin/bosh:23:in `<main>'


Can someone please guide me what I am doing wrong ?


Regards,
Akshay


Re: [ann] docker-boshrelease v30 - bosh loves docker - everything is easier with bosh links, cloud-config, bosh2

Amit Kumar Gupta
 

Great stuff Dr Nic, lovely blog post!

On Thu, Apr 13, 2017 at 7:26 AM, Dr Nic Williams <drnicwilliams(a)gmail.com>
wrote:

*Release notes*: https://github.com/cloudfoundry-community/docker-
boshrelease/releases/tag/v30.0.0

The docker-boshrelease was first introduced Apr 14, 2014 - three years ago
- by the legendary Ferdy. It has been used in production systems for years
- both running static clusters of containers, and as an API allowing
dynamic provisioning/deprovisioning of containers (historically this was
via Cloud Foundry) via the https://github.com/cloudfoundry-community/cf-
containers-broker companion project.

*To celebrate the dual birthdays* - this repository turning three and
BOSH itself turning five https://www.cloudfoundry.org/bosh-turns-five/ -
we've done a major upgrade to this project to bring it into line with the
exciting features in BOSH 2.0.

This release also includes the introduction of a companion project
https://github.com/cloudfoundry-community/docker-broker-deployment - the
one-stop shop for deploying the Open Service Broker API that can deploy
anything as a service, via Docker!

I've also published a "getting started" guide at
https://www.starkandwayne.com/blog/adding-docker-based-
services-to-your-cloud-foundry-with-bosh2/ which includes links to
getting started with bosh 2.0, and deploying CF using the fabulous new
bosh2 cli and *-deployment repos.

Happy birthday BOSH!
Dr Nic

--
Dr Nic Williams
Stark & Wayne LLC
http://starkandwayne.com
+61 437 276 076 <+61%20437%20276%20076>
twitter @drnic


[ann] docker-boshrelease v30 - bosh loves docker - everything is easier with bosh links, cloud-config, bosh2

Dr Nic Williams
 

*Release notes*:
https://github.com/cloudfoundry-community/docker-boshrelease/releases/tag/v30.0.0

The docker-boshrelease was first introduced Apr 14, 2014 - three years ago
- by the legendary Ferdy. It has been used in production systems for years
- both running static clusters of containers, and as an API allowing
dynamic provisioning/deprovisioning of containers (historically this was
via Cloud Foundry) via the
https://github.com/cloudfoundry-community/cf-containers-broker companion
project.

*To celebrate the dual birthdays* - this repository turning three and BOSH
itself turning five https://www.cloudfoundry.org/bosh-turns-five/ - we've
done a major upgrade to this project to bring it into line with the
exciting features in BOSH 2.0.

This release also includes the introduction of a companion project
https://github.com/cloudfoundry-community/docker-broker-deployment - the
one-stop shop for deploying the Open Service Broker API that can deploy
anything as a service, via Docker!

I've also published a "getting started" guide at
https://www.starkandwayne.com/blog/adding-docker-based-services-to-your-cloud-foundry-with-bosh2/
which includes links to getting started with bosh 2.0, and deploying CF
using the fabulous new bosh2 cli and *-deployment repos.

Happy birthday BOSH!
Dr Nic

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


Re: VMs are not added to AWS ELB target groups

Tsvetan Valchev
 

Thank you very much for that info.

Do you have any timeline when an official release with AWS v2 can be expected ?


Re: Question on stemcell (userid/password)

Hari Guru
 

Actually vcap/c1oudc0w worked


Re: Question on stemcell (userid/password)

Dmitriy Kalinin
 

response from gh issue:

we recommend that you dont use vcap for ssh access. consider colocating
os-conf's user_add job for additional user configuration:
https://github.com/cloudfoundry/os-conf-release/blob/master/jobs/user_add/spec

On Wed, Apr 5, 2017 at 2:18 PM, Hari Guru <harirtp(a)gmail.com> wrote:

I am also looking for same. Any Luck? Appreciate if you can share


Re: Question on stemcell (userid/password)

Hari Guru
 

I am also looking for same. Any Luck? Appreciate if you can share


Persistent disk with windows stemcell

Xiangyi Meng <xmeng@...>
 

Hi,

We want to deploy our products to windows stemcell. But I found windows bosh agent doesn't mount the persistent disk specified in deployment manifest file. It even doesn't use the ephemeral disk specified in resource pool. It only put all data into C:\, the root file system delivered with windows stemcell. How could we keep persistent data with windows stemcell? If current bosh agent doesn't support such features, is there ETA about when this feature will be supported?

Thanks,
Maggie


Re: vcap password not set after stemcell upgrade

Dr Nic Williams
 

Hey Jo,

I believe the vcap password has become randomized... to discourage use.

Instead, simply add the user_add job from os-conf release to create an
explicit user with ssh keys/password you control:

https://github.com/cloudfoundry/os-conf-release/blob/master/jobs/user_add/spec

Nic


vcap password not set after stemcell upgrade

Jonathan Stockley
 

Hi,
We have been using ubuntu vsphere stemcell 3263.8 and are now attempting to upgrade a test deployment to 3363.12.
The upgrade went successfully and the application is running.
However, we cannot login to the VM using ssh vcap(a)AA.BB.CC.DD
It seems as if the vcap password has been changed.
Using 'bosh ssh app 0' is successful and checking the /etc/shadow file it show that the vcap entry's password field is '*'.

Switching back to 3263.8 and the vcap password is back.

Is this an intentional change to the stemcell?
How to we get the former behaviour?
Is this documented somewhere?

Thanks,
Jo


Re: Creating & Deploying BOSH Releases on Windows

A William Martin
 

Hi Jo,

We have a sample windows bosh release here:
https://github.com/cloudfoundry-incubator/sample-windows-bosh-release

We're also planning on writing some reference docs about this, so whatever questions you may have along the way would be helpful for us to gain perspective.

Cheers,
William


Re: [cf-dev] BOSH Links: Why and How

Amit Kumar Gupta
 

Thanks Nic, your early feedback on that note was helpful, keep it coming if
you have more!

On Wed, Mar 29, 2017 at 3:41 PM, Dr Nic Williams <drnicwilliams(a)gmail.com>
wrote:

Amit, this doc has been awesomely helpful to me over the last week or so.
I've been steadily upgrading bosh releases. I like them & the deployment
manifests a lot more.


------------------------------
*From:* Amit Gupta <agupta(a)pivotal.io>
*Sent:* Thursday, March 30, 2017 8:35:53 AM
*To:* Discussions about the Cloud Foundry BOSH project.; Discussions
about Cloud Foundry projects and the system overall.
*Subject:* [cf-dev] BOSH Links: Why and How

Hi all,

"BOSH Links" is a feature which simplifies how data is shared between
BOSH-deployed jobs that need to collaborate with one another (e.g. a web
server and its backing database). Like many BOSH things, the whole "BOSH
Links" thing can seem counter-intuitive at first, and it may not be clear
why things are the way they are. This note linked below hopes to show some
of the powerful benefits of BOSH Links, and provide examples and
explanations that make things more intuitive.

Hope folks find it useful!

https://gist.github.com/Amit-PivotalLabs/c39528248b8cdc4ba8e347f8aa68abb6

Best,
Amit

601 - 620 of 2761