|
AWS DNS resolution + micro bosh
John Wong
By default everything in a VPC outbound is restricted, whether you are in a
"public subnet" or "private subnet" or not. http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/VPC_NAT_Instance.html The only thing that makes "public subnet" public is that you have a public IP attached. Regardless, you can tune how traffic is routed via the routing table. Amazon has a VPC service and there you can create subnets. One of the options provides one-click to create public and private subnet with NAT. This NAT is address translation unit. Basically all outbound traffic in private subnet will go through this NAT (which resides in the public subnet with EIP). This is enabled via routing table, which Amazon does the creation for you. You can also choose to update the routing table yourself, or create the routing tables and subnets all together on your own (manually or cloudformation, doesn't matter). Now, I don't know if your VPC is set up with the concept of public and private subnet. If not, I urge you run in such mode. I hope this helps you debug your issue. Run CF in your private subnet. To allow people to get inside your CF apps use some webserver like nginx; to allow CF to have outgoing traffic (such as getting packages), go through the NAT. On Sat, May 2, 2015 at 3:03 PM, Sumanth Yamala <Sumanth.Yamala(a)sas.com> wrote: I create 2 VMs one with elastic IP and the other one is default network
|
|
|
|
Re: AWS DNS resolution + micro bosh
John Wong
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
|
|
|
|
Re: bosh-init beta release
Dr Nic Williams
Congrats BOSH team!
I'll upgrade my little tutorial repos to use new GitHub releases asap. On Fri, May 1, 2015 at 6:04 PM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote: Hey all,
|
|
|
|
bosh-init beta release
Dmitriy Kalinin
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
|
|
|
|
Re: AWS DNS resolution + micro bosh
Sumanth Yamala <Sumanth.Yamala@...>
There is no error. That VM hangs when I execute apt-get update or do a traceroute to Yahoo.
toggle quoted messageShow quoted text
Thanks Sumanth Sent from my iPhone
On May 1, 2015, at 6:04 PM, "Dmitriy Kalinin" <dkalinin(a)pivotal.io<mailto: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<mailto: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<mailto:dkalinin(a)pivotal.io>] Sent: Friday, May 01, 2015 3:39 PM To: Sumanth Yamala Cc: cf-bosh(a)lists.cloudfoundry.org<mailto: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<mailto: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<http://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<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh
|
|
|
|
Re: AWS DNS resolution + micro bosh
Dmitriy Kalinin
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
|
|
|
|
Re: AWS DNS resolution + micro bosh
Sumanth Yamala <Sumanth.Yamala@...>
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<mailto: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<http://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<mailto:cf-bosh(a)lists.cloudfoundry.org> https://lists.cloudfoundry.org/mailman/listinfo/cf-bosh
|
|
|
|
Cannot Upload Warden Stemcell
Quintessence Anx
I was experimenting with the warden stemcells and found that I could upload
a locally downloaded stemcell, but that neither of the following worked: ``` $ bosh upload stemcell https://bosh.io/d/stemcells/bosh-warden-boshlite-ubuntu-trusty-go_agent $ bosh upload stemcell https://bosh.io/d/stemcells/bosh-warden-boshlite-ubuntu-trusty-go_agent?v=2776 ``` Should we be able to upload the stemcells directly to BOSH lite with a URL? I based what I was doing off here: http://bosh.io/stemcells/bosh-warden-boshlite-ubuntu-trusty-go_agent
|
|
|
|
Re: AWS DNS resolution + micro bosh
Dmitriy Kalinin
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 ,
|
|
|
|
Re: Download Public Stemcell Parameter?
Dmitriy Kalinin
Correct. Two options of getting stemcells are downloading them locally
(curl/wget) or directly uploading them to the Director (e.g. see https://bosh.io/stemcells/bosh-aws-xen-hvm-ubuntu-trusty-go_agent). On Fri, May 1, 2015 at 12:29 PM, Quintessence Anx <qanx(a)starkandwayne.com> wrote: Aha. I was using bosh.io and I was trying to see if users could still
|
|
|
|
Re: Download Public Stemcell Parameter?
Quintessence Anx
Aha. I was using bosh.io and I was trying to see if users could still
toggle quoted messageShow quoted text
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!),
|
|
|
|
AWS DNS resolution + micro bosh
Sumanth Yamala <Sumanth.Yamala@...>
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
|
|
|
|
Re: Download Public Stemcell Parameter?
Rob Day-Reynolds <rdayreynolds@...>
The command isn't deprecated yet, but the `--full` flag is used for `bosh
public stemcells`, rather than `bosh download public stemcell`. The idea behind the `--full` was to display a full URL from `bosh public stemcells`, rather than providing one to download. The help text is worded slightly strangely, but since the command is being deprecated, I would guess that it won't be reworded. On Fri, May 1, 2015 at 10:39 AM, Dmitriy Kalinin <dkalinin(a)pivotal.io> wrote: It has not been officially deprecated just yet (thanks for the reminder!),
|
|
|
|
Re: Download Public Stemcell Parameter?
Dmitriy Kalinin
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.
|
|
|
|
Re: Download Public Stemcell Parameter?
Dr Nic Williams
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
|
|
|
|
Re: BOSH Agent / Stemcell for Windows?
Chip Childers
On Fri, May 1, 2015 at 5:27 AM, David Laing <david(a)davidlaing.com> wrote:
Given the recent announcement of BOSH on Azure; is there any news comingThere have been some early discussions (and I believe there might be a closed source prototype out there), but it's a logical step at some point. -chip
|
|
|
|
Download Public Stemcell Parameter?
Quintessence Anx
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
|
|
|
|
BOSH Agent / Stemcell for Windows?
David Laing <david@...>
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! D -- David Laing logsearch.io - build your own open source cloud logging cluster http://davidlaing.com
|
|
|
|
Bosh AWS deployment issue - was working before
Sumanth Yamala <Sumanth.Yamala@...>
Hi,
I was able to deploy my release a few weeks back, now it fails with strange errors including some manifest schema and default VPC being used. Bosh CLI version: BOSH 1.2950.0 (updated it) Deployed microbosh using bosh - VPC,subnet, security group [ nothing was created as everything was already in place] When the release was uploaded and bosh deploy was called 1) First issue - a new element became mandatory - in the manifest file section for resource pools - size element became mandatory- this was not there before and it is not needed for openstack it complaints only for AWS. I added the size=3 to get over the first issue resource_pools: - name: common size: 3 network: default stemcell: name: bosh-aws-xen-ubuntu-trusty-go_agent version: latest cloud_properties: instance_type: m3.large 2) The second issue was when the deployment happens I get the below issue Failed creating bound missing vms > common/0: The security group 'bosh' does not exist in default VPC 'vpc-16940b73' (00:00:01) - although the microbosh, my deployment manifest and network all point to the subnet tied to the microbosh. The entire set up worked well for AWS a few weeks before - the only changes are I installed the micro bosh VM instance again and updated my BOSH CLI. Any thoughts on where this could have gone wrong ? any documentation on the schema change ? Thanks for help in advance. Thanks Sumanth
|
|
|
|
Re: curl vs wget to download stemcells
Long Nguyen
Hey Quinn. 6.2kb seem like right size for light stem cell. If you want
toggle quoted messageShow quoted text
full stemcell it's around 400mb and there is different url for that. Long
On 30 Apr 2015 16:53, "Quintessence Anx" <qanx(a)starkandwayne.com> wrote:
I am experiencing something a bit unexpected when I try to download the
|
|
|