Support pre-signed URLs for Zaqar queues

Bug #1628691 reported by Zane Bitter
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Fix Released
Wishlist
Thomas Herve

Bug Description

Zaqar supports creating a pre-signed URL for reading from/writing to a queue without needing to authenticate with Keystone credentials:

openstack queue signed url myqueue --methods GET,POST --paths messages,subscriptions

We need to expose this in Heat so that users can insert it into SoftwareDeployments (so that applications can use queues... which is kind of the point), or pass it to Aodh as an alarm action.

Tags: spec-lite
Zane Bitter (zaneb)
Changed in heat:
milestone: none → ocata-1
importance: Undecided → Wishlist
tags: added: spec-lite
Changed in heat:
status: New → Triaged
Revision history for this message
Thomas Herve (therve) wrote :

Just to be clear, you're talking about the ZaqarQueue resource?

Revision history for this message
Zane Bitter (zaneb) wrote :

Yes, although I'm not 100% sure whether it should be an attribute of the existing OS::Zaqar::Queue resource or a new OS::Zaqar::PresignedURL resource type. (Ideally it would be the former, but it seems like there's a lot of options that can be passed.)

Thomas Herve (therve)
Changed in heat:
assignee: nobody → Thomas Herve (therve)
Revision history for this message
Zane Bitter (zaneb) wrote :

After thinking about this a bit over the weekend, I actually see a big advantage for having a separate resource type for the pre-signed URL: that would make it easy to generate a new one by marking the URL resource unhealthy and updating the stack. So you could create a stack with:

* A server
* A Zaqar queue
* A presigned-url resource for the queue
* A SW Deployment to pass the URL to the server
* A Mistral workflow to act on messages from the queue
* A Zaqar subscription to trigger the workflow from messages
* A second Mistral workflow to mark the presigned-url resource unhealthy
* A Mistral timed trigger to periodically kick off the workflow to regenerate the URL

and you'd have effectively recreated something similar to the system of rotating keys that AWS has for IAM Roles, except with much more flexibility and fine-grained control.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to heat (master)

Fix proposed to branch: master
Review: https://review.openstack.org/391846

Changed in heat:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to heat (master)

Reviewed: https://review.openstack.org/391846
Committed: https://git.openstack.org/cgit/openstack/heat/commit/?id=571740f07d5415df83580042e93eeefffeb57b9f
Submitter: Jenkins
Branch: master

commit 571740f07d5415df83580042e93eeefffeb57b9f
Author: Thomas Herve <email address hidden>
Date: Mon Oct 31 14:19:40 2016 +0100

    Support Zaqar signed queue URLs

    This adds new resource to generate a signed URL for a Zaqar queue.

    Change-Id: Ib42f11bf13d1e836563023a9fa587b93c875ec61
    Closes-Bug: #1628691

Changed in heat:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/heat 8.0.0.0b1

This issue was fixed in the openstack/heat 8.0.0.0b1 development milestone.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.