youre probably not technically allowed to add shared storage to bare metal hosts... at least not at this moment. so daves assertion about the assumption and my irrelevant comment are correct, IMO. waiting for frank for the definitive answer on this, since he implemented the feature originally and is working on the modern bare metal.
On Mon, May 6, 2013 at 7:26 PM, Jessica Tomechak <jessica.tomec...@gmail.com > wrote: > On Mon, May 6, 2013 at 9:29 AM, David Nalley <da...@gnsa.us> wrote: > > > On Mon, May 6, 2013 at 10:38 AM, Jessica Tomechak > > <jessica.tomec...@gmail.com> wrote: > > > Does it matter whether Offer HA is checked when creating a compute > > offering > > > for use with a bare metal deployment? My understanding of HA is that it > > > will restart a VM on another host in the same zone if the VM crashes. > In > > > the case of bare metal, instead of a VM, we have a baremetal instance, > > one > > > per machine. Would checking Offer HA mean that if a bare metal host > > > crashes, another baremetal instance would be created on a different > host > > in > > > the zone? Has anyone tried / tested this scenario? > > > > > > Jessica T. > > > > > > No assumption of shared storage - as a matter of fact, I think the > > assumption is the opposite. > > > > --David > > > > I think you check "Shared" for Storage Type when creating a compute > offering for an HA host. So I'm not sure whether your assumption about the > assumption is correct. I'd love to hear more about this. > > Since we're talking about these settings, there are a few others which I'm > not sure how to document. These are in the Add Compute Offering dialog. > When the offering is for a bare metal host, would there be any restrictions > on setting these, or perhaps would some or all of them not make sense with > bare metal even if they're technically allowed: > > Network Rate > Storage Tags > CPU Cap > isVolatile > > Jessica T. >
