Updated openstack/openstack
Project: openstack/heat  6f3c0e987793e775ede88fe44027cf88903e3cd7
null
heat_keystoneclient migrate create_ec2_keypair to v3 API

Convert create_ec2_keypair to use the v3/credentials API, which
is the v3-compatible way to manage ec2 keypairs.

NOTE: requires the fix for keystone bug #1259584 (now in keystone
master) or signature validation with these credentials will fail.

Change-Id: I9fbc1611c53cd14177b5c0dfe25a96a3922fd1cc
blueprint: keystone-v3-only
Updated openstack/openstack
Project: openstack-dev/devstack  b53dbad8ac42417960f39bbd1f0901ffae808075
null
remove setting up fatal_deprecations

using fatal deprecations only means you can't add new deprecations
to the code base, which isn't helpful in actually deprecating
features in a user friendly way.

Change-Id: I26468f4c221a14f2eea746439d46e5fa192cfc57
Updated openstack/openstack
Project: openstack/heat  b8ba7d796efc23cfae1f1f3f71efd6297d1b0a0b
null
Store credential ID for AccessKey and SignalResponder

These resources create an ec2 keypair, which when managed via the
keystone v3/credentials should be accessed via credential ID not
the access key ID, so store the credential ID for performing any
operations (get/update/delete) on the credential, as it's preferable
to having to do a brute-force lookup by access key (no way to filter
on the access key via v3/credentials)

Change-Id: I5995fb003c998fc2d7f331c6da7430adcab168b2
blueprint: keystone-v3-only