Hi, all...
I have a bit a related question and I am trying to decide the
best path. Currently we have 3.1 in production and an entirely new
Setup in our internal DC that is waiting to be built out.
Should I start with 3.2 to begin with? Or 3.1 then migrate to 3.2 to
gain the
On 06/26/2013 04:35 AM, Tony Feldmann wrote:
I was messing around with some things and force removed my DC. My
cluster is still there with the 2 gluster volumes, however I cannot move
that cluster into a new dc, I just get the following error in engine.log:
2013-06-25 20:26:15,218 ERROR
Ii won't let me move the hosts as they have gluster volumes in that cluster.
On Wed, Jun 26, 2013 at 6:49 AM, Itamar Heim ih...@redhat.com wrote:
On 06/26/2013 04:35 AM, Tony Feldmann wrote:
I was messing around with some things and force removed my DC. My
cluster is still there with the 2
On 06/26/2013 02:55 PM, Tony Feldmann wrote:
Ii won't let me move the hosts as they have gluster volumes in that cluster.
so the cluster is both virt and gluster?
On Wed, Jun 26, 2013 at 6:49 AM, Itamar Heim ih...@redhat.com
mailto:ih...@redhat.com wrote:
On 06/26/2013 04:35 AM, Tony
yes.
On Wed, Jun 26, 2013 at 6:57 AM, Itamar Heim ih...@redhat.com wrote:
On 06/26/2013 02:55 PM, Tony Feldmann wrote:
Ii won't let me move the hosts as they have gluster volumes in that
cluster.
so the cluster is both virt and gluster?
On Wed, Jun 26, 2013 at 6:49 AM, Itamar Heim
On 06/26/2013 02:59 PM, Tony Feldmann wrote:
yes.
what's the content of this table?
vds_spm_id_map
(also of vds_static)
thanks
On Wed, Jun 26, 2013 at 6:57 AM, Itamar Heim ih...@redhat.com
mailto:ih...@redhat.com wrote:
On 06/26/2013 02:55 PM, Tony Feldmann wrote:
Ii won't
I am not sure how to retrieve that info.
On Wed, Jun 26, 2013 at 7:00 AM, Itamar Heim ih...@redhat.com wrote:
On 06/26/2013 02:59 PM, Tony Feldmann wrote:
yes.
what's the content of this table?
vds_spm_id_map
(also of vds_static)
thanks
On Wed, Jun 26, 2013 at 6:57 AM, Itamar
On 06/26/2013 03:41 PM, Tony Feldmann wrote:
I am not sure how to retrieve that info.
psql engine postgres -c select * from vds_static;
psql engine postgres -c select * from vds_spm_id_map;
On Wed, Jun 26, 2013 at 7:00 AM, Itamar Heim ih...@redhat.com
mailto:ih...@redhat.com wrote:
I ended up removing the gluster volumes and then the cluster. I was a
little frustrated with why I couldn't get it to work and made a hasty
decision. Thank you very much for your response, but I am basically going
to have to re-build at this point.
On Wed, Jun 26, 2013 at 7:48 AM, Itamar Heim
I have a 2 node cluster with engine running on one of the nodes. It has 2
gluster volumes that replicate between the hosts as its shared storage.
Last night one of my systems crashed. It looks like all of my data is
present, however the ids file seems to be corrupt on my master domain. I
tried
I was messing around with some things and force removed my DC. My cluster
is still there with the 2 gluster volumes, however I cannot move that
cluster into a new dc, I just get the following error in engine.log:
2013-06-25 20:26:15,218 ERROR
[org.ovirt.engine.core.bll.AddVdsSpmIdCommand]
11 matches
Mail list logo
