On Thu, 18 Oct 2012, Matthew Miller wrote:
On Thu, Oct 18, 2012 at 06:24:10PM -0400, Seth Vidal wrote:
I bring this up not just to be annoying :) but wanted to make sure you're
aware of it when designing anything. (I think practically that means:
store things as key value pair per resource, and try to keep below
Amazon's arbitrary limit of 10 tags per resource.)
I can say right now that keeping below 10 tags per resource is
unlikely to happen.
That's ten _keys_ per resource. You can have many more than ten values. Is
that still a problem?
Ultimately, yes - and of course my other problem is I need this data
available ACROSS reboots/rebuilds of the cloud cluster.
For our persistent instances plan I need to be able to know that I need to
bring up 10 instances as m1.xlarge. Instance 1 needs to get this ip:
allocate it accordingly, instance 1 needs this volume attached, etc, etc.
See where I'm going? If the instance is down that's not very functional
Yeah, crickets for openstack too.
maybe cloudstack? David was telling me about their options.
-sv
_______________________________________________
infrastructure mailing list
infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/infrastructure
