On Mar 16, 2011, at 3:39 PM, Justin Santa Barbara wrote:
> I agree that we could have a better marker, but I'm just going off the spec
> at the moment.
>
> I've checked the agreed blueprint, and caching in zones is out of scope for
> Cactus.
>
> Please propose a discussion topic for the Design Summit.
Can we get back to the original topic? The only reason caching came up
was as an alternative to a single DB to hold all instance information. That was
an implementation solution suggested for multi-cluster/zones, so it is
definitely in scope for Cactus.
-- Ed Leafe
Confidentiality Notice: This e-mail message (including any attached or
embedded documents) is intended for the exclusive and confidential use of the
individual or entity to which this message is addressed, and unless otherwise
expressly indicated, is confidential and privileged information of Rackspace.
Any dissemination, distribution or copying of the enclosed material is
prohibited.
If you receive this transmission in error, please notify us immediately by
e-mail
at ab...@rackspace.com, and delete the original message.
Your cooperation is appreciated.
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
