Given the recent announcement of BOSH on Azure; is there any news coming
about managing Windows VMs using BOSH?

I'm wondering if this is a:

* Not even on the roadmap; never going to happen
* Technically feasible; but way down the list of priorities
* Exciting announcements coming at CFSummit...

Thanks!

I was playing around with the CLI and I noticed that the output of `bosh
public stemcells` indicates there should be a `--full` parameter; however,
it doesn't seem to work?
```
$ bosh public stemcells
...
To download use 'bosh download public stemcell <stemcell_name>'. For full
url use --full.
$ bosh download public stemcell --full
https://d26ekeud912fhb.cloudfront.net/bosh-stemcell/aws/light-bosh-stemcell-2957-aws-xen-ubuntu-trusty-go_agent.tgz
invalid option: --full
Usage: bosh download public stemcell <stemcell_filename>
```
Is the `--full` parameter deprecated?
Thanks!
Quinn

I think "bosh public stemcells" is deprecated in lieu of bosh.io. I think.



On Fri, May 1, 2015 at 9:09 AM, Quintessence Anx <qanx(a)starkandwayne.com>
wrote:

I was playing around with the CLI and I noticed that the output of `bosh
public stemcells` indicates there should be a `--full` parameter;
however, it doesn't seem to work?

```
$ bosh public stemcells
...
To download use 'bosh download public stemcell <stemcell_name>'. For
full url use --full.

$ bosh download public stemcell --full
https://d26ekeud912fhb.cloudfront.net/bosh-stemcell/aws/light-bosh-stemcell-2957-aws-xen-ubuntu-trusty-go_agent.tgz
invalid option: --full
Usage: bosh download public stemcell <stemcell_filename>
```

Is the `--full` parameter deprecated?

Thanks!

Quinn

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

It has not been officially deprecated just yet (thanks for the reminder!),
but it's definitely better to look at https://bosh.io/stemcells.

On Fri, May 1, 2015 at 9:59 AM, Dr Nic Williams <drnicwilliams(a)gmail.com>
wrote:

I think "bosh public stemcells" is deprecated in lieu of bosh.io. I
think.



On Fri, May 1, 2015 at 9:09 AM, Quintessence Anx <qanx(a)starkandwayne.com>
wrote:

I was playing around with the CLI and I noticed that the output of `bosh
public stemcells` indicates there should be a `--full` parameter;
however, it doesn't seem to work?

```
$ bosh public stemcells
...
To download use 'bosh download public stemcell <stemcell_name>'. For
full url use --full.

$ bosh download public stemcell --full
https://d26ekeud912fhb.cloudfront.net/bosh-stemcell/aws/light-bosh-stemcell-2957-aws-xen-ubuntu-trusty-go_agent.tgz
invalid option: --full
Usage: bosh download public stemcell <stemcell_filename>
```

Is the `--full` parameter deprecated?

Thanks!

Quinn

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Aha. I was using bosh.io and I was trying to see if users could still
download the stemcells locally using both the BOSH CLI as well as
wget/curl. Is the intention moving forward that eventually users won't be
able to download stemcells with `bosh download public stemcell`?

On Fri, May 1, 2015 at 1:39 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io>
wrote:

It has not been officially deprecated just yet (thanks for the
reminder!), but it's definitely better to look at
https://bosh.io/stemcells.

On Fri, May 1, 2015 at 9:59 AM, Dr Nic Williams <drnicwilliams(a)gmail.com>
wrote:

I think "bosh public stemcells" is deprecated in lieu of bosh.io. I
think.



On Fri, May 1, 2015 at 9:09 AM, Quintessence Anx <qanx(a)starkandwayne.com

wrote:

I was playing around with the CLI and I noticed that the output of `bosh
public stemcells` indicates there should be a `--full` parameter;
however, it doesn't seem to work?

```
$ bosh public stemcells
...
To download use 'bosh download public stemcell <stemcell_name>'. For
full url use --full.

$ bosh download public stemcell --full
https://d26ekeud912fhb.cloudfront.net/bosh-stemcell/aws/light-bosh-stemcell-2957-aws-xen-ubuntu-trusty-go_agent.tgz
invalid option: --full
Usage: bosh download public stemcell <stemcell_filename>
```

Is the `--full` parameter deprecated?

Thanks!

Quinn

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Hi ,



I am using the features of BOSH DNS resolution. Deployed a microbosh. In
my deployment manifest I specify for a default network to use 10.0.0.6 as
my DNS.



The behavior is: in AWS

It is able to resolve BOSH deployed VM DNS like
“0.docker.default.docker-sample.microbosh” but it is unable to resolve
yahoo.com. How can I fix this behavior so that this resolves both.



In OpenStack I had a similar issue – I had to put properties:dns:recursor
with the name server that resolves the company network and the “www” to get
around this.



How do I solve this for AWS?



Thanks,

Sumanth

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

I tried putting 10.0.0.2 as my dns.recursor…I am still having issues
with DNS resolution on nodes which use network with DNS entry of micro-bosh
(10.0.0.6) for the other nodes provisioned there is no issue.



Thanks,

Sumanth







*From:* Dmitriy Kalinin [mailto:dkalinin(a)pivotal.io]
*Sent:* Friday, May 01, 2015 3:39 PM
*To:* Sumanth Yamala
*Cc:* cf-bosh(a)lists.cloudfoundry.org
*Subject:* Re: [cf-bosh] AWS DNS resolution + micro bosh



You should be able to use dns.recursor exactly the same way on AWS as you
did on OpenStack.



Btw AWS provides 10.0.0.2 address in your subnet as a full DNS.



On Fri, May 1, 2015 at 11:43 AM, Sumanth Yamala <Sumanth.Yamala(a)sas.com>
wrote:

Hi ,



I am using the features of BOSH DNS resolution. Deployed a microbosh. In
my deployment manifest I specify for a default network to use 10.0.0.6 as
my DNS.



The behavior is: in AWS

It is able to resolve BOSH deployed VM DNS like
“0.docker.default.docker-sample.microbosh” but it is unable to resolve
yahoo.com. How can I fix this behavior so that this resolves both.



In OpenStack I had a similar issue – I had to put properties:dns:recursor
with the name server that resolves the company network and the “www” to get
around this.



How do I solve this for AWS?



Thanks,

Sumanth


_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Hey all,
I'm happy to announce beta release of bosh-init.
bosh-init is a tool used to create and update the Director (its VM and
persistent disk) in a BOSH environment. It's meant to replace the micro CLI
plugin.
You can find more information about bosh-init on the following pages:
- http://bosh.io/docs#install section now lists guides for how to use
bosh-init with different IaaSes
- http://bosh.io/docs/install-bosh-init.html shows how to install bosh-init
- http://bosh.io/docs/using-bosh-init.html describes how to use its
deploy/delete commands
- http://bosh.io/docs/migrate-to-bosh-init.html describes how to migrate
from the micro CLI plugin
Let us know about issues you find via Github:
https://github.com/cloudfoundry/bosh-init/issues
Dmitriy & BOSH team

There is no error. That VM hangs when I execute apt-get update or do a
traceroute to Yahoo.

Thanks
Sumanth

Sent from my iPhone

On May 1, 2015, at 6:04 PM, "Dmitriy Kalinin" <dkalinin(a)pivotal.io> wrote:

Does it not work at all or is some error is shown?

On Fri, May 1, 2015 at 1:28 PM, Sumanth Yamala <Sumanth.Yamala(a)sas.com>
wrote:

I tried putting 10.0.0.2 as my dns.recursor…I am still having issues
with DNS resolution on nodes which use network with DNS entry of micro-bosh
(10.0.0.6) for the other nodes provisioned there is no issue.



Thanks,

Sumanth







*From:* Dmitriy Kalinin [mailto:dkalinin(a)pivotal.io]
*Sent:* Friday, May 01, 2015 3:39 PM
*To:* Sumanth Yamala
*Cc:* cf-bosh(a)lists.cloudfoundry.org
*Subject:* Re: [cf-bosh] AWS DNS resolution + micro bosh



You should be able to use dns.recursor exactly the same way on AWS as
you did on OpenStack.



Btw AWS provides 10.0.0.2 address in your subnet as a full DNS.



On Fri, May 1, 2015 at 11:43 AM, Sumanth Yamala <Sumanth.Yamala(a)sas.com>
wrote:

Hi ,



I am using the features of BOSH DNS resolution. Deployed a microbosh. In
my deployment manifest I specify for a default network to use 10.0.0.6 as
my DNS.



The behavior is: in AWS

It is able to resolve BOSH deployed VM DNS like
“0.docker.default.docker-sample.microbosh” but it is unable to resolve
yahoo.com. How can I fix this behavior so that this resolves both.



In OpenStack I had a similar issue – I had to put properties:dns:recursor
with the name server that resolves the company network and the “www” to get
around this.



How do I solve this for AWS?



Thanks,

Sumanth


_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

I create 2 VMs one with elastic IP and the other one is default network
with 10.0.0.6 as the DNS. Both are created in the same subnet/vpc

The vm with elastic IP has no issues. The Vm with DNS turned on can
resolve other VMs via powerDNS but cannot resolve www.

It eventually times out.

Sent from my iPhone

On May 2, 2015, at 1:48 PM, "John Wong" <gokoproject(a)gmail.com> wrote:

By hanging I supposed eventually timeout? If so...you sure you have the
routing table configured for that subnet of your VPC? Create a vm in the
same subnet and try if you get the same hanging.

On Fri, May 1, 2015 at 9:02 PM, Sumanth Yamala <Sumanth.Yamala(a)sas.com>
wrote:

There is no error. That VM hangs when I execute apt-get update or do a
traceroute to Yahoo.

Thanks
Sumanth

Sent from my iPhone

On May 1, 2015, at 6:04 PM, "Dmitriy Kalinin" <dkalinin(a)pivotal.io>
wrote:

Does it not work at all or is some error is shown?

On Fri, May 1, 2015 at 1:28 PM, Sumanth Yamala <Sumanth.Yamala(a)sas.com>
wrote:

I tried putting 10.0.0.2 as my dns.recursor…I am still having issues
with DNS resolution on nodes which use network with DNS entry of micro-bosh
(10.0.0.6) for the other nodes provisioned there is no issue.



Thanks,

Sumanth







*From:* Dmitriy Kalinin [mailto:dkalinin(a)pivotal.io]
*Sent:* Friday, May 01, 2015 3:39 PM
*To:* Sumanth Yamala
*Cc:* cf-bosh(a)lists.cloudfoundry.org
*Subject:* Re: [cf-bosh] AWS DNS resolution + micro bosh



You should be able to use dns.recursor exactly the same way on AWS as
you did on OpenStack.



Btw AWS provides 10.0.0.2 address in your subnet as a full DNS.



On Fri, May 1, 2015 at 11:43 AM, Sumanth Yamala <Sumanth.Yamala(a)sas.com>
wrote:

Hi ,



I am using the features of BOSH DNS resolution. Deployed a microbosh.
In my deployment manifest I specify for a default network to use 10.0.0.6
as my DNS.



The behavior is: in AWS

It is able to resolve BOSH deployed VM DNS like
“0.docker.default.docker-sample.microbosh” but it is unable to resolve
yahoo.com. How can I fix this behavior so that this resolves both.



In OpenStack I had a similar issue – I had to put
properties:dns:recursor with the name server that resolves the company
network and the “www” to get around this.



How do I solve this for AWS?



Thanks,

Sumanth


_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

_______________________________________________
cf-bosh mailing list
cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh

Cool, thank you. Will try it out this week.

------------------------
Alex Lomov
*Altoros* — Cloud Foundry deployment, training and integration
*Twitter:* @code1n <https://twitter.com/code1n> *GitHub:* @allomov
<https://gist.github.com/allomov>

On Thu, Apr 30, 2015 at 5:15 PM, Dr Nic Williams <drnicwilliams(a)gmail.com>
wrote:

http://bosh.io/releases/github.com/cloudfoundry-incubator/bosh-openstack-cpi-release is
the OpenStack CPI

It should work like the AWS one if you have original flat networking.

If you have neutron the you'll need to put in slightly different
networking into the manifest.yml



On Thu, Apr 30, 2015 at 4:23 AM, Alexander Lomov <
alexander.lomov(a)altoros.com> wrote:

bosh-init needs BOSH release for CPI you want to use.

Unfortunately, at this moment there is no CPI BOSH release
for OpenStack, at least I don't know about it. There is nothing in BOSH
repo and http://bosh.io/releases.

So to start deployment to OpenStack you need to find or implement BOSH
CPI release for OpenStack CPI first.

Best wishes,
Alex L.

------------------------
Alex Lomov
*Altoros* — Cloud Foundry deployment, training and integration
*Twitter:* @code1n <https://twitter.com/code1n> *GitHub:* @allomov
<https://gist.github.com/allomov>

On Thu, Apr 30, 2015 at 11:44 AM, 王天青 <wang.tianqing.cn(a)gmail.com>
wrote:

Hi all,

I have read a blog from Dr. Nic Williams, New bosh-init can deploy
anything to a single server. In this blog, he explained very well on how
bosh-init works and gave three examples. One of them is deploying BOSH on
AWS.

I'd like to try to use bosh-init to deploy BOSH on OpenStack, but could
not find any reference doc from bosh.io/docs. Is anyone working the
same thing and could share the manifest? Thanks.

Best Regards~!
Grissom

_______________________________________________
Cf-bosh mailing list
Cf-bosh(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh