User specific for install?

[tomsherrod]

Could you explain below a bit more? Why would it prevent additional installs?

You must create a separate user just for this purpose, that does not have admin privileges. If the user does, you will be unable to create more than one CloudFoundry instance per Openstack install, even if you have them in separate tenants.

[lnguyen]

Hi there!
The problem with user having admin privilege for given tenant is that bosh bootstrap might find other bosh stemcells that it doesn't actually have access to them. It's a known issue that I haven't been able to investigate why I can see other images in openstack but not use them. You should be able to create a CF per tenant with this. I'm under assumption that tenant is CF system.

Long

[tomsherrod]

Thanks. Yes it works. One thing I noticed...it deletes & recreate keypairs of the CF manifest name, regardless of tenant. I need to re-test to be absolutely sure....I certainly don't see duplicates. Can prove an issue for multiple active and same named CFs.

[lnguyen]

Oh is bosh workspace deleting firstbosh key regardless of tenant? We can def make this unique quite easily.

On Apr 6, 2015, at 4:50 PM, tomfuie notifications@github.com wrote:

Thanks. Yes it works. One thing I noticed...it deletes & recreate keypairs of the CF manifest name, regardless of tenant. I need to re-test to be absolutely sure....I certainly don't see duplicates. Can prove an issue for multiple active and same named CFs.

—
Reply to this email directly or view it on GitHub
.

[lnguyen]

Ok changed it so it would be unique key per tenant 29732f3