On Wed, Apr 12, 2017 at 11:15 PM, Jamie Lawrence
wrote:
>
> > On Apr 12, 2017, at 1:31 AM, Evgenia Tokar wrote:
> >
> > Hi Jamie,
> >
> > Are you trying to setup hosted engine using the "hosted-engine --deploy"
> command, or are you trying to migrate existing he vm?
> >
> > For hosted engine set
> On Apr 12, 2017, at 1:31 AM, Evgenia Tokar wrote:
>
> Hi Jamie,
>
> Are you trying to setup hosted engine using the "hosted-engine --deploy"
> command, or are you trying to migrate existing he vm?
>
> For hosted engine setup you need to provide a clean storage domain, which is
> not a p
Hi Jamie,
Are you trying to setup hosted engine using the "hosted-engine --deploy"
command, or are you trying to migrate existing he vm?
For hosted engine setup you need to provide a clean storage domain, which
is not a part of your 4.1 setup, this storage domain will be used for the
hosted engin
Or at least, refusing to mount a dirty pool.
I have 4.1 set up, configured and functional, currently wired up with two VM
hosts and three Gluster hosts. It is configured with a (temporary) NFS data
storage domain, with the end-goal being two data domains on Gluster; one for
the hosted engine, o
Or at least, refusing to mount a dirty pool. I’m having trouble getting the
hosted engine installed.
I have 4.1 set up, configured and functional, currently wired up with two VM
hosts and three Gluster hosts. It is configured with a (temporary) NFS data
storage domain, with the end-goal being t
5 matches
Mail list logo