Keyauth support not available for Openstack providers
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Go OpenStack Exchange |
Fix Released
|
Medium
|
Данило Шеган | ||
| juju-core |
Fix Released
|
High
|
Данило Шеган | ||
Bug Description
The boiler plate template for HP Cloud has a section for key pair authentication:
# auth-mode: keypair
# Usually set via the env variable AWS_ACCESS_KEY_ID, but can be specified here
# access-key: <secret>
# Usually set via the env variable AWS_SECRET_
# secret-key: <secret>
however when I try to use keypair authentication I get the error:
$ juju --debug bootstrap -e hpcloud
2013/02/27 18:53:59 JUJU environs/openstack: opening environment "hpcloud"
2013/02/27 18:53:59 JUJU juju bootstrap command failed: secret-key: expected nothing, got "<redacted>"
error: secret-key: expected nothing, got "<redacted>"
I am able to deploy on HP Cloud with keyparis on Py-Juju, and I successfully deployed on AWS, but I confirmed in #juju-dev authenticating with keypairs is not yet enabled. Thus, I am filing this bug to track the work to enable keypair authentication on HP Cloud (openstack).
I am running the recent released Juju-Core version: 1.9.9-2~
-Thanks,
Antonio
Related branches
- Juju Engineering: Pending requested
-
Diff: 191 lines (+85/-14)4 files modifiedenvirons/openstack/config.go (+42/-13)
environs/openstack/config_test.go (+38/-0)
environs/openstack/local_test.go (+1/-1)
environs/openstack/provider.go (+4/-0)
- Juju Engineering: Pending requested
-
Diff: 758 lines (+471/-88)15 files modifiedclient/client.go (+2/-0)
client/client_test.go (+4/-2)
client/local_test.go (+9/-1)
identity/identity.go (+9/-3)
identity/identity_test.go (+51/-0)
identity/keypair.go (+39/-0)
identity/keystone.go (+88/-0)
identity/local_test.go (+1/-1)
identity/userpass.go (+1/-75)
nova/local_test.go (+1/-1)
swift/local_test.go (+2/-1)
testservices/identityservice/keypair.go (+123/-0)
testservices/identityservice/keypair_test.go (+130/-0)
testservices/openstackservice/openstack.go (+10/-3)
tools/secgroup-delete-all/main_test.go (+1/-1)
| summary: |
- Openstack does not support keyauth + Keyauth support not available for Openstack providers |
| Changed in goose: | |
| importance: | Undecided → Medium |
| status: | New → Triaged |
| Changed in goose: | |
| assignee: | nobody → Данило Шеган (danilo) |
| Данило Шеган (danilo) wrote | #1 |
| Данило Шеган (danilo) wrote | #2 |
| Changed in juju-core: | |
| assignee: | nobody → Данило Шеган (danilo) |
| status: | New → Incomplete |
| Changed in juju-core: | |
| status: | Incomplete → In Progress |
| Changed in goose: | |
| status: | Triaged → In Progress |
| Changed in goose: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | In Progress → Fix Committed |
| Changed in juju-core: | |
| status: | Fix Committed → Fix Released |
| Changed in goose: | |
| status: | Fix Committed → Fix Released |
From reading the docs at https:/
* "access_key": NOVA_API_KEY env variable
* "secret_key": EC2_SECRET_KEYS env variable (or AWS_SECRET_
* "project-name": OS_TENANT_NAME (but also NOVA_PROJECT_NAME, NOVA_PROJECT_ID)
* "authorized-keys": not part of the credentials, and I assume it's already supported (documenting it for the sake of completeness)