Sorry, I guess I skipped a bit of that.
I did run hosted-engine --deploy and it failed while waiting for vdsm to
respond and at that point I sent the original email because I wasn't quite
certain if it was a supported to migrate from non-hosted engine to a hosted
engine which seems to be
On Tue, Sep 20, 2016 at 4:40 PM, Logan Kuhn wrote:
> It's still running on a physical machine. I saw that article, is the way
> forward to migrate my physical engine to a hosted engine and then I can
> deploy more hosted engines?
>
>
In hosted-engine scenario, the engine is
It's still running on a physical machine. I saw that article, is the way
forward to migrate my physical engine to a hosted engine and then I can deploy
more hosted engines?
Regards,
Logan
- On Sep 20, 2016, at 9:36 AM, Simone Tiraboschi
wrote:
| On Tue, Sep 20,
On Tue, Sep 20, 2016 at 4:28 PM, Logan Kuhn wrote:
> I tried this and I get the attached error message.
>
> Error while executing action: Cannot add Host. You are using an unmanaged
> hosted engine VM. Please upgrade the cluster level to 3.6 and wait for the
> hosted engine
I tried this and I get the attached error message.
Error while executing action: Cannot add Host. You are using an unmanaged
hosted engine VM. Please upgrade the cluster level to 3.6 and wait for the
hosted engine storage domain to be properly imported.
I used only the required information.
On Tue, Sep 20, 2016 at 3:00 PM, Logan Kuhn wrote:
> Perfect, thank you.
>
> Just out of curiosity, why is that only available when a host is added.
> It seems like something that should be addable after the host is live.
>
I thinks that is just because it needs to detect
Perfect, thank you.
Just out of curiosity, why is that only available when a host is added. It
seems like something that should be addable after the host is live.
Regards,
Logan
- On Sep 19, 2016, at 3:06 PM, Simone Tiraboschi
wrote:
| On Mon, Sep 19, 2016 at
On Mon, Sep 19, 2016 at 9:58 PM, Logan Kuhn wrote:
> Hm, I bet it's because the original install was via engine-setup instead
> of hosted-engine --deploy ?
>
Did it imported the hosted-engine storage domain and the engine VM?
>
> Regards,
> Logan
>
> - On Sep 19,
Hm, I bet it's because the original install was via engine-setup instead of
hosted-engine --deploy ?
Regards,
Logan
- On Sep 19, 2016, at 2:44 PM, Simone Tiraboschi
wrote:
| On Mon, Sep 19, 2016 at 6:59 PM, Logan Kuhn < log...@wolfram.com > wrote:
|| When I
I understand and I would prefer that as well, but for the life of me I cannot
seem to find where that is available in the web admin.
Regards,
Logan
- On Sep 19, 2016, at 2:44 PM, Simone Tiraboschi
wrote:
| On Mon, Sep 19, 2016 at 6:59 PM, Logan Kuhn <
On Mon, Sep 19, 2016 at 6:59 PM, Logan Kuhn wrote:
> When I try to deploy a second hosted engine it errors out at Environment,
> items. Full log attached.
>
> The host I'm deploying to is actually going to end up being our production
> instance of the image. I've also tried
11 matches
Mail list logo