Put Openstack credentials for Copr in private.git #4397

Closed
opened 2014-06-02 14:15:06 +00:00 by msuchy · 5 comments

I am trying to migrate Copr to Fedora 20. But ec2 module from ansible.fc20 does not work with current Fedora Cloud. And upstream have no intention to change it [1]
Therefore I have to migrate to use nova_compute module of ansible. But for that I would need keystonerc present in
{{ private }}/files/openstack/copr-copr/
Right now there is only ec2rc.sh
And ideally have OS_USERNAME, OS_PASSWORD, OS_TENANT_NAME, OS_AUTH_URL present as ansible variable as well. Likely with 'COPR_' prefix.

[1] https://github.com/ansible/ansible/pull/7603

I am trying to migrate Copr to Fedora 20. But ec2 module from ansible.fc20 does not work with current Fedora Cloud. And upstream have no intention to change it [1] Therefore I have to migrate to use nova_compute module of ansible. But for that I would need keystonerc present in {{ private }}/files/openstack/copr-copr/ Right now there is only ec2rc.sh And ideally have OS_USERNAME, OS_PASSWORD, OS_TENANT_NAME, OS_AUTH_URL present as ansible variable as well. Likely with 'COPR_' prefix. [1] https://github.com/ansible/ansible/pull/7603
Owner

Thats unfortunate. ;( We wanted to stick to ec2 in case we decided/wanted someday to run against amazon or rackspace or whatever. ;(

I'll try and figure out what we need in there...

Thats unfortunate. ;( We wanted to stick to ec2 in case we decided/wanted someday to run against amazon or rackspace or whatever. ;( I'll try and figure out what we need in there...
Author

And can I you pleas put those three variables in private.git as temporary solution. So I can proceed with upgrade to Fedora 20, which is blocking new release of Copr?

And can I you pleas put those three variables in private.git as temporary solution. So I can proceed with upgrade to Fedora 20, which is blocking new release of Copr?
Author

Additionally it would mean, that we will have to open port 5000 on fed-cloud02.cloud.fedoraproject.org. At least to 172.23.0.0/24 so all VM can talk to keystone.

Additionally it would mean, that we will have to open port 5000 on fed-cloud02.cloud.fedoraproject.org. At least to 172.23.0.0/24 so all VM can talk to keystone.
Owner

I'm really not finding a way to get that out of the cloud... in particular the password.

I can reset it in the dashboard, but will that invalidate the existing ec2 credentials?

Ping me when you are around and I can try it...

I'm really not finding a way to get that out of the cloud... in particular the password. I can reset it in the dashboard, but will that invalidate the existing ec2 credentials? Ping me when you are around and I can try it...
Author

For the record:

OS_PASSWORD is variable copr_nova_password

OS_TENANT_ID is variable copr_tenant_id

and

OS_AUTH_URL should be https://172.23.0.2:5000/v2.0

For the record: OS_PASSWORD is variable copr_nova_password OS_TENANT_ID is variable copr_tenant_id and OS_AUTH_URL should be https://172.23.0.2:5000/v2.0
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
infra/tickets#4397
No description provided.