I guess a known fact, but most people behind RacherOS were original
authors of CloudStack. They should have no issues integrating with
CloudStack - assuming you are Rancher customer - you can ask them to
extend support for it.
On 9/12/16 4:38 AM, Helge Waastad wrote:
> Hi,
> and thanks for answe
Does the original qcow2 still exist on local storage? You might have to dig
into the DB to figure out what the name would be.
From: Mohammad Rastgoo
Sent: Monday, September 12, 2016 3:32 PM
To: users@cloudstack.apache.org
Subject: Re: Unable to start a Migrated V
It was successful first time.
No signs of qcow2 image on secondary storage.
We use local storage.
On Mon, Sep 12, 2016 at 4:19 PM Simon Weller wrote:
> Did the migration succeed the first time? Is the qcow2 image still on
> secondary storage?
>
>
> What type of primary storage?
>
>
Did the migration succeed the first time? Is the qcow2 image still on
secondary storage?
What type of primary storage?
From: Mohammad Rastgoo
Sent: Monday, September 12, 2016 3:08 PM
To: users@cloudstack.apache.org
Subject: Unable to start a Migrated VM to wro
Hi,
Thanks in advance.
Our setup:
ACS 4.5.2 Advance zone - KVM Hypervisor
Issue:
We mistakenly migrated a VM to from cluster A to cluster B and VM is no
longer starting. Attempts to migrate it back also fails.
Log:
2016-09-12 15:39:25,648 ERROR [c.c.v.VirtualMachineManagerImpl]
(Work-Job-Execut
Hi Dag,
thank you for your feedback.We're going to introduce a new cluster. Not
really happy with that, but way better than risking any data loss.
- Stephan
Am Montag, den 12.09.2016, 08:24 + schrieb Dag Sonstebo:
> Hi Stephan,
>
> Zone-wide (i.e. multi-cluster) primary storage is only sup
Hi,
and thanks for answering.
Yeah, I've read the docs and I've seen the cloudstack cloud-init
implementation in ubuntu cloud-image
So since configdrive is not supported I think I need to follow your
advice and rather make a script fetching needed information from
cloudstack instead and then star
Hi Stephan,
Zone-wide (i.e. multi-cluster) primary storage is only supported on KVM and
VMware, not XenServer.
Just so we are on the same page though – this applies at a LUN level – in other
words two XenServer pools can never share a LUN, but they can both use
different LUNs from the same st
