cf-bosh@lists.cloudfoundry.org

Home Messages Hashtags Subgroups

Messages

Between

and

You can specify the avaibility_zone under the resource_pool cloud properties field. resource_pools: - name: common network: default size: 8 stemcell: name:

By Gwenn Etourneau · #121 ·

deployment to OpenStack with Keystone v3 (domains)

Fog recently added support for authentication with OpenStack's Keystone v3 APIs, allowing deployment to domains other than the default domain. Is anyone working on enhancing the BOSH CPI for OpenStack

By Koper, Dies <diesk@...> · #122 ·

Re: Regarding installation of bosh

Hi james , thanks for the replay. I am attaching my terminal output screen along with this mail. you can also see the ping to google.com is successful but the ping for rubygems.org is

By Bharath · #126 ·

Re: Multi-AZ CF Deployment in Openstack

It solved the issue. Thank you very much! -- View this message in context: http://cf-bosh.70367.x6.nabble.com/cf-bosh-Multi-AZ-CF-Deployment-in-Openstack-tp64p67.html Sent from the CF BOSH mailing

By ryunata <ricky.yunata@...> · #123 ·

Re: Regarding installation of bosh

looks like you have a firewall or network connectivity issue between your OS and the destination, in this case rubygems.org. i would talk to your network administrator. for example, this is my curl

By James Bayer · #124 ·

Re: Most bosh director commands fail with a HTTP 500

Thanks Dmitriy – this fixed our issue J Sent: 26 May 2015 19:54 To: Scott Taggart Cc: CF BOSH Mailing List Subject: Re: [cf-bosh] Most bosh director commands fail with a HTTP 500 There

By Scott Taggart <staggart@...> · #125 ·

Re: Regarding installation of bosh

Isn't it wrong that ping to google.com goes out of 216.59.196.14 address but ping to rubygems.org goes out of 10.0.0.2? Looks like routing or default gateway settings is broken on that machine. Check

By Kamil Burzynski <nopik@...> · #127 ·

bosh vms failing with http 500

Hi All, Post a sudden restart of Bosh director (due to issues with cloud provider), bosh vms command started giving http 500. Below are some observations and logs. Appreciate any help on this: $ bosh

By jaffar.yelavalli@... · #128 ·

Re: deployment to OpenStack with Keystone v3 (domains)

Not to my knowledge. wrote:

By Dmitriy Kalinin · #129 ·

Re: bosh vms failing with http 500

Please see solution in this thread: https://lists.cloudfoundry.org/pipermail/cf-bosh/2015-May/000112.html We have a story at the top of the backlog to fix

By Dmitriy Kalinin · #130 ·

Resuming UAA work

Hey all, We have resumed BOSH & UAA integration work: https://www.pivotaltracker.com/n/projects/1285490 to be worked on by a single pair. As part of this work we are going to provide two options how

By Dmitriy Kalinin · #131 ·

Re: Resuming UAA work

Sounds great! I assume you'll use a uaa oauth scope to determine if the given user actually has access to bosh? bosh.admin? wrote:

By Mike Youngstrom · #132 ·

Re: Resuming UAA work

From the perspective of using BOSH without CF, moving the users to the manifest is actually an improvement, as it allows you to list the actual users without logging in to the DB. Are there any plans

By Aristoteles Neto · #133 ·

Re: Resuming UAA work

The UAA doesn't depend on CF, it can be leveraged as a stand alone product. aristoteles.neto(a)webdrive.co.nz> wrote:

By Filip Hanik · #134 ·

Re: Resuming UAA work

True - silly me. Sounds great :) -- Neto

By Aristoteles Neto · #135 ·

Re: Resuming UAA work

Love it! I'm wondering what are your thoughts for authorization? Wondering if the Director will introduce roles of any kind... Alberto Twitter: albertoaflores

By Alberto A. Flores · #136 ·

Re: Resuming UAA work

We will ask the UAA team to start producing uaa-release shortly, which will be independent of cf-release. Eventually I expect people will remove uaa job from cf-release and just use

By Dmitriy Kalinin · #137 ·

Re: Resuming UAA work

I've added a bosh-notes page about UAA integration: https://github.com/cloudfoundry/bosh-notes/blob/master/uaa.md (and associated issue: https://github.com/cloudfoundry/bosh-notes/issues/8) wrote:

By Dmitriy Kalinin · #138 ·

Re: Resuming UAA work

Thanks for the response! +1 on the "bosh-director.DIRECTOR-UUID.admin" scope. I assume this means that in the event of multiple directors, users will have to have multiple scopes associated to their

By Alberto A. Flores · #139 ·

Re: Resuming UAA work

Sure feel free to leave comments on the issue ( https://github.com/cloudfoundry/bosh-notes/issues/8) or file a PR against that document and I will try to incorporate it. wrote:

By Dmitriy Kalinin · #140 ·

121 - 140 of 2763

Home Hashtags Subgroups Terms