Add keystone support

[sunloverz]

No description provided.

[sunloverz]

@thousandsofthem @pyeremenko could you please review

[pyeremenko]

I can't find any call of getToken :(

[thousandsofthem]

it's there - https://github.com/iron-io/iron_mq_php/pull/38/files

[pyeremenko]

Oh, sorry, it's iron_core

[pyeremenko]

@thousandsofthem, please, look at this PR. I think it could be merged.

[thousandsofthem]

tenantId as far as I understand how it works , names are not reliable

[pyeremenko]

@thousandsofthem, could you clarify?

[thousandsofthem]

This one works for sure, using it in HUD-e:
https://github.com/iron-io/iron_core_ruby/blob/master/lib/iron_core/keystone_token_provider.rb#L16

[thousandsofthem]

P.S. Also, tenantId always equal to project_id so could be derived from it
P.P.S. tenantName is not unique therefore can't be used as a key

[pyeremenko]

@thousandsofthem,

• @edsrzf said we should support not tenantId, but tenantName, please discuss it with him.
• Why 'tenantName' string is not unique key?

[thousandsofthem]

tenantName means "project name", and user can set any name he wants to, including duplicate ones.
@edsrzf do you know anything else?

[thousandsofthem]

Some notes:

• only project_id required (with tenantId), project name is extra dependency
• tenantId actually works with test server and on AT&T installation

[thousandsofthem]

any update so far?

[pyeremenko]

@edsrzf, @carimura, @treeder

We implemented support of format "keystone": { "server": ..., "tenant": ..., "username": ..., "password": ... } because we discussed it with Evan and he accepted this way. @thousandsofthem wants to change this format and we will change it if somebody of you confirm it.

[rjocoleman]

I know this is WIP but it's out of sync with https://github.com/iron-io/iron_mq_php/tree/v3

Perhaps a note in the iron-io/iron_mq_php v3 branch README would be appropriate?

Specific issue is Notice: Undefined property: IronMQ::$use_keystone, it's easy enough to patch to workaround but still an issue!