Fwd: RE: placement groups

[Adrian Cole <ad...@opscode.com>]

In case you guys are curious. Jclouds supports the new cluster instances and placement groups. We should talk about how whirr can use this info.  

Adrian

-------- Original Message --------
Subject: RE: placement groups
From: "Lipscomb, Trenton" <tr...@amazon.com>
To: Adrian Cole <ad...@opscode.com>
CC: null

Sorry I missed a follow up on this. I haven't written up my trip report, and your question was buried in there. Apologies.

I asked the principal engineer on HPC and here was his repose. We've also asked the PMs (who write the docs) to improve the explanations.


Clustered placement groups are relegated to a single AZ, and that will be true forever. You can currently start more than one placement group in a single AZ, and we expect that to be common. Each group will independently experience the "clustering" benefits within the group, but not necessarily between groups even in the same AZ.



As the placement group API evolves, it's possible that future strategies will straddle multiple AZs or even regions.

Let me know if you need anything else.

I hope, too, using the boot device flag helped you to keep track of which volumes go with which hosts.

*trenton


From: Adrian Cole [mailto:adrian@opscode.com]
Sent: Friday, July 30, 2010 1:09 PM
To: Lipscomb, Trenton
Subject: placement groups

Hi, Trenton,

Thanks for chatting with me at length during oscon.  Let me know, if you've found anything out about those new placement groups for the cluster instances.  I'm working with cloudera and would like to understand the scope and usage correctly.

Cheers,
Adrian
jclouds & opscode

Re: RE: placement groups

[Tom White <to...@cloudera.com>]

Thanks for this Adrian. I've opened
https://issues.apache.org/jira/browse/WHIRR-63.

Tom

On Fri, Jul 30, 2010 at 4:35 PM, Adrian Cole <ad...@opscode.com> wrote:
> In case you guys are curious. Jclouds supports the new cluster instances and placement groups. We should talk about how whirr can use this info.
>
> Adrian
>
> -------- Original Message --------
> Subject: RE: placement groups
> From: "Lipscomb, Trenton" <tr...@amazon.com>
> To: Adrian Cole <ad...@opscode.com>
> CC: null
>
> Sorry I missed a follow up on this. I haven't written up my trip report, and your question was buried in there. Apologies.
>
> I asked the principal engineer on HPC and here was his repose. We've also asked the PMs (who write the docs) to improve the explanations.
>
>
> Clustered placement groups are relegated to a single AZ, and that will be true forever. You can currently start more than one placement group in a single AZ, and we expect that to be common. Each group will independently experience the "clustering" benefits within the group, but not necessarily between groups even in the same AZ.
>
>
>
> As the placement group API evolves, it's possible that future strategies will straddle multiple AZs or even regions.
>
> Let me know if you need anything else.
>
> I hope, too, using the boot device flag helped you to keep track of which volumes go with which hosts.
>
> *trenton
>
>
> From: Adrian Cole [mailto:adrian@opscode.com]
> Sent: Friday, July 30, 2010 1:09 PM
> To: Lipscomb, Trenton
> Subject: placement groups
>
> Hi, Trenton,
>
> Thanks for chatting with me at length during oscon.  Let me know, if you've found anything out about those new placement groups for the cluster instances.  I'm working with cloudera and would like to understand the scope and usage correctly.
>
> Cheers,
> Adrian
> jclouds & opscode
>