|
Testing
Dr Nic Williams
Testing testing 10.1.2.3.
-- Dr Nic Williams Stark & Wayne LLC - consultancy for Cloud Foundry users http://drnicwilliams.com http://starkandwayne.com cell +1 (415) 860-2185 twitter @drnic |
|
|
|
Re: Testing
Wayne E. Seguin
bosh release upload mailman 10.1.2.3
On Wed, Apr 29, 2015 at 12:07 PM, Dr Nic Williams <drnicwilliams(a)gmail.com> wrote: Testing testing 10.1.2.3. |
|
|
|
Re: Testing
Armin Ranjbar
Message received, Exiting Zero :)
--- Armin ranjbar On Wed, Apr 29, 2015 at 8:37 PM, Dr Nic Williams <drnicwilliams(a)gmail.com> wrote: Testing testing 10.1.2.3. |
|
|
|
Re: Testing
Wayne E. Seguin
Tests PASS, SHIP IT !
toggle quoted message
Show quoted text
On Wed, Apr 29, 2015 at 1:33 PM, Armin Ranjbar <zoup(a)zoup.org> wrote:
Message received, Exiting Zero :) |
|
|
|
Re: Testing
Aristoteles Neto
10.1.2.3: Host Unreachable.
toggle quoted message
Show quoted text
-- Neto On 30/04/2015, at 5:42, Wayne E. Seguin <wayneeseguin(a)starkandwayne.com> wrote:
Tests PASS, SHIP IT ! |
|
|
|
Re: Testing
Wayne E. Seguin
Really? Mine had the following response packet contents:
THERE IS NO WAY YOU CAN HACK ME!!! MY IP ADDRESS IS 127.0.0.1 On Wed, Apr 29, 2015 at 2:51 PM, Aristoteles Neto < aristoteles.neto(a)webdrive.co.nz> wrote: 10.1.2.3: Host Unreachable. |
|
|
|
Re: Testing
Daniel Jones
Hi all,
toggle quoted message
Show quoted text
If this is the new mailing list address could that please be communicated so we can all change our email filters? At the moment these are showing up in my inbox as potentially important email as they're not from vcap-dev. On Wed, Apr 29, 2015 at 6:33 PM, Armin Ranjbar <zoup(a)zoup.org> wrote:
Message received, Exiting Zero :) --
Regards, Daniel Jones EngineerBetter.com |
|
|
|
Re: Testing
Chip Childers
This was communicated here >
https://groups.google.com/a/cloudfoundry.org/forum/#!topic/vcap-dev/GBrJNHNKxSU Please let me know directly if you have any further questions. -chip Chip Childers | Technology Chief of Staff | Cloud Foundry Foundation On Wed, Apr 29, 2015 at 3:45 PM, Daniel Jones < daniel.jones(a)engineerbetter.com> wrote: Hi all, |
|
|
|
Re: Testing
sabith ks
Hi Chip,
Any plans on using the gitter channel as well for live chats ? https://gitter.im/cloudfoundry-community/cf-release I Could see that this chat room is available : https://gitter.im/cloudfoundry-community/cf-java-component --Sabith On Wed, Apr 29, 2015 at 1:14 PM Chip Childers <cchilders(a)cloudfoundry.org> wrote: This was communicated here > |
|
|
|
Re: Testing
Chip Childers
No, that is not likely to be used at this point by the project's dedicated
toggle quoted message
Show quoted text
committers. Things change, but unlikely at this time. Chip Childers | Technology Chief of Staff | Cloud Foundry Foundation On Wed, Apr 29, 2015 at 4:16 PM, sabith ks <sabithksme(a)gmail.com> wrote:
Hi Chip, |
|
|
|
Re: Testing
Daniel Jones
Apologies, my bad!
toggle quoted message
Show quoted text
/me updates email filters, writes post-it to pay more attention On 29 Apr 2015 21:14, "Chip Childers" <cchilders(a)cloudfoundry.org> wrote:
This was communicated here > |
|
|
|
Using bosh-init to deploy BOSH on OpenStack
王天青 <wang.tianqing.cn at gmail.com...>
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 |
|
|
|
Re: Using bosh-init to deploy BOSH on OpenStack
Alexander Lomov
bosh-init needs BOSH release for CPI you want to use.
toggle quoted message
Show quoted text
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, |
|
|
|
Re: Using bosh-init to deploy BOSH on OpenStack
Dr Nic Williams
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. |
|
|
|
Re: Using bosh-init to deploy BOSH on OpenStack
Alexander Lomov
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:
|
|
|
|
curl vs wget to download stemcells
Quintessence Anx
I am experiencing something a bit unexpected when I try to download the AWS
stemcells with wget and curl. I'm trying to download the latest version, so for curl I enter: curl -L -J -O https://bosh.io/d/stemcells/bosh-aws-xen-ubuntu-trusty-go_agent For wget I enter: wget --content-disposition --no-check-certificate https://bosh.io/d/stemcells/bosh-aws-xen-ubuntu-trusty-go_agent For curl I get a file named: bosh-aws-xen-ubuntu-trusty-go_agent For wget I get a file named: light-bosh-stemcell-2950-aws-xen-ubuntu-trusty-go_agent.tgz In both cases the file is about 6.2KB, so it looks like I am actually getting the *light* stemcell both times, even though that's not the URL I'm using. Is this behavior expected? How would I use curl/wget to download the full stemcell since there's no separate URL? Thanks! |
|
|
|
Re: curl vs wget to download stemcells
Wayne E. Seguin
What you want is the *hvm* ones if you are going for the full size stemcell
vs a reference to a pre-existing AMI curl -sOL https://bosh.io/d/stemcells/bosh-aws-xen-hvm-ubuntu-trusty-go_agent Notice the -hvm- in the file name. All that said, did I see somewhere that the full stemcells are being depreciated in preference for the light stemcells on AWS? eg. Does that mean that only light will be available/generated from some point forward? On Thu, Apr 30, 2015 at 4:48 PM, Quintessence Anx <qanx(a)starkandwayne.com> wrote: I am experiencing something a bit unexpected when I try to download the |
|
|
|
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 message
Show 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 |
|
|
|
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 |
|
|
|
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 |
|
|