We are managing Galaxy/Cloudman clusters on AWS for a few research groups on campus. As is so often the case, we need to separate usage for billing purposes. This this is fairly simple to do with Amazon's CSV billing report with the "clusterName" tag included. However, it doesn't appear that I can configure Cloudman to set that tag on every resource it creates. This is forcing us to keep the scaling of the clusters under our control so that we can set the tags manually.
What I was hoping, is that this feature could be added. It seems like a fairly simple patch; once the ID (instance, volume, or snapshot) is available, it's one more API call to create/set the clusterName tag.
Any chance of getting this included?
Thanks! -Shea
Hi Shea, This is a reasonable feature so we'll add it on the todo list. To make the search for all untagged resources easier, did you have a list of the ones that are currently not getting tagged?
Thanks, Enis
On Tue, Dec 4, 2012 at 7:34 AM, Shea Lovan shea.lovan@lscg.ucsb.edu wrote:
We are managing Galaxy/Cloudman clusters on AWS for a few research groups on campus. As is so often the case, we need to separate usage for billing purposes. This this is fairly simple to do with Amazon's CSV billing report with the "clusterName" tag included. However, it doesn't appear that I can configure Cloudman to set that tag on every resource it creates. This is forcing us to keep the scaling of the clusters under our control so that we can set the tags manually.
What I was hoping, is that this feature could be added. It seems like a fairly simple patch; once the ID (instance, volume, or snapshot) is available, it's one more API call to create/set the clusterName tag.
Any chance of getting this included?
Thanks! -Shea
--
Shea A. Lovan Manager, Server Operations and Architecture UCSB Life Sciences Computing Group Santa Barbara, CA 93106 805.893.2405
______________________________**_____________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at:
Enis-
These are the ones that I know of:
* Snapshots created via Cloudman "Persist changes to filesystem" command. * Spot instances created by manually adding worker nodes. I have not tested auto-scale or on-demand worker-instances. * The ephemeral storage volumes associated with worker nodes.
Thanks a bunch! -Shea
On 12/04/2012 03:35 PM, Enis Afgan wrote:
Hi Shea, This is a reasonable feature so we'll add it on the todo list. To make the search for all untagged resources easier, did you have a list of the ones that are currently not getting tagged?
Thanks, Enis
On Tue, Dec 4, 2012 at 7:34 AM, Shea Lovan <shea.lovan@lscg.ucsb.edu mailto:shea.lovan@lscg.ucsb.edu> wrote:
We are managing Galaxy/Cloudman clusters on AWS for a few research groups on campus. As is so often the case, we need to separate usage for billing purposes. This this is fairly simple to do with Amazon's CSV billing report with the "clusterName" tag included. However, it doesn't appear that I can configure Cloudman to set that tag on every resource it creates. This is forcing us to keep the scaling of the clusters under our control so that we can set the tags manually. What I was hoping, is that this feature could be added. It seems like a fairly simple patch; once the ID (instance, volume, or snapshot) is available, it's one more API call to create/set the clusterName tag. Any chance of getting this included? Thanks! -Shea -- ------------------------ Shea A. Lovan Manager, Server Operations and Architecture UCSB Life Sciences Computing Group Santa Barbara, CA 93106 805.893.2405 <tel:805.893.2405> ___________________________________________________________ Please keep all replies on the list by using "reply all" in your mail client. To manage your subscriptions to this and other Galaxy lists, please use the interface at: http://lists.bx.psu.edu/
galaxy-dev@lists.galaxyproject.org
-
Enis Afgan -
Shea Lovan