-
Notifications
You must be signed in to change notification settings - Fork 3.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow specifying additional tenants for sharing OpenStack images. #4113
Comments
@varikin Do you know if this requires Glance support? |
@rickard-von-essen I would assume so, but I am haven't looked at that functionality. We are happy with just making images public to all projects (tenants). |
looks like the API is here https://github.com/rackspace/gophercloud/blob/HEAD/openstack/imageservice/v2/members/requests.go which is an api call against glance, so it would be required. It's been a few years since I've worked with openstack, so I'm not sure if glance is common to all infrastructures. we'll have to update the library at a minimum. The version we're using has been deprecated, so it might be worth taking a look at the new version (https://github.com/gophercloud/gophercloud/) and seeing if it's drop-in replaceable. |
@clstokes 0.12.0 will come out next week and we'll get this in immediately after in 0.12.1 before 1.0 |
Thanks Matt! |
@mwhooker Could you also look into throwing in a option for visibility, private or public. See |
There's a PR for upgrading the library here, but it looks like some functionality will be lost #4211 |
When building an OpenStack image using Packer, the resulting image is available only to the tenant (or project) that was specified in the builder. Additional tenant ids should be able to be set (optionally) to share the resulting image with multiple tenants. This is functionally equivalent to the ami_users option for the
amazon-ebs
builder.The text was updated successfully, but these errors were encountered: