Mark,
> Enter the name which will be used to identify this host inside the
> Administrator Portal [hosted_engine_1]:
This is the name used for the host inside the Administrator Portal, so basically
the name of the VM inside the system.
This does not have to be the hostname, bu
Hello,
i did a deploy of hosted engine with an hostname that i'm willing to
change now. Is there any procedure to do this?
Luca
--
"E' assurdo impiegare gli uomini di intelligenza eccellente per fare
calcoli che potrebbero essere affidati a chiunque se si usassero delle
macchine"
Gottfried Wilh
On Tue, Dec 6, 2016 at 8:48 PM, Marcelo Leandro wrote:
> sorry, this is correct src-vdsm.log
Perhaps try to edit the VM, choose Host tab, and tweak migration options.
You can set policy to Legacy, and a high-enough "custom migration downtime".
See also e.g.:
http://lists.ovirt.org/pipermail/use
I cant put host in maintenance mode before, because the host-egnie is a VM
inside the single host.
... unfortunately the shutdown problem persist ... :-(
2016-11-23 18:06 GMT+01:00 Pavel Gashev :
> Luigi,
>
>
>
> It’s necessary to put a host into maintenance mode before shutdown.
>
>
>
> That pan
Hi all,
This is a discussion on the RFE[1] to provide a tool to perform full vacuum
on our DBs.
First if you are not familiar with vacuum please read this [2]
# Backgroud
ovirt 'engine' DB have several busy table with 2 differnt usage patten. One
is audit_log and the others are the 'v*_statistic
Marcin,
- Marcin Mirecki wrote:
> Mark,
>
> > Enter the name which will be used to identify this host inside the
> > Administrator Portal [hosted_engine_1]:
>
> This is the name used for the host inside the Administrator Portal, so
> basically
> the name of the VM insid
On Wed, Dec 7, 2016 at 11:36 AM, Mark Steckel wrote:
> Marcin,
>
> - Marcin Mirecki wrote:
>> Mark,
>>
>> > Enter the name which will be used to identify this host inside
>> > the
>> > Administrator Portal [hosted_engine_1]:
>>
>> This is the name used for the host inside
2016-12-07 10:27 GMT+02:00 Luca 'remix_tj' Lorenzetto
:
> Hello,
>
> i did a deploy of hosted engine with an hostname that i'm willing to
> change now. Is there any procedure to do this?
I don't think so.
If you have another host, you can migrate all VMs to the other host,
move current to mainten
Mark,
hosted_engine_1 is of course the name of the host in the system.
Sorry for the confusion.
Marcin
- Original Message -
> From: "Mark Steckel"
> To: "Marcin Mirecki"
> Cc: users@ovirt.org
> Sent: Wednesday, December 7, 2016 10:36:58 AM
> Subject: Re: [ovirt-users] Hosted-engine --d
On Wed, Dec 7, 2016 at 9:57 AM, Roy Golan wrote:
> Hi all,
>
> This is a discussion on the RFE[1] to provide a tool to perform full vacuum
> on our DBs.
>
> First if you are not familiar with vacuum please read this [2]
>
> # Backgroud
> ovirt 'engine' DB have several busy table with 2 differnt us
Hello,
On Wed, Dec 7, 2016 at 10:53 AM, Yedidyah Bar David wrote:
[cut]
>
> If you have another host, you can migrate all VMs to the other host,
> move current to maintenance, remove it, then add it with the new name
> you want. You might have to also clean up the shared meta-data, see:
>
> https
On Wed, Dec 7, 2016 at 12:08 PM, Piotr Kliczewski
wrote:
> On Wed, Dec 7, 2016 at 9:57 AM, Roy Golan wrote:
>> Hi all,
>>
>> This is a discussion on the RFE[1] to provide a tool to perform full vacuum
>> on our DBs.
>>
>> First if you are not familiar with vacuum please read this [2]
>>
>> # Back
Yedidyah - very helpful! Thanks.
A follow-up question re the FQDN for the hosted engine: My understanding is
that the FQDN must be resolvable when "hosted-engine --deploy" is executed.
However, should the IP that the FQDN resolves to also be assigned/up when
"hosted-engine --deploy" is executed
On Wed, Dec 7, 2016 at 10:57 AM, Roy Golan wrote:
> Hi all,
>
> This is a discussion on the RFE[1] to provide a tool to perform full
> vacuum on our DBs.
>
> First if you are not familiar with vacuum please read this [2]
>
> # Backgroud
> ovirt 'engine' DB have several busy table with 2 differnt
On Tue, Dec 6, 2016 at 9:51 PM, Gianluca Cecchi
wrote:
>
>
> Here the HostedEngine.log generated under /var/log/libvirt/qemu
>
> https://drive.google.com/file/d/0BwoPbcrMv8mvZ0V5RTFBZXJfMzA/
> view?usp=sharing
>
> I see at the end of it the line
>
> warning: host doesn't support requested feature
On Wed, Dec 7, 2016 at 12:20 PM, Luca 'remix_tj' Lorenzetto
wrote:
> Hello,
>
> On Wed, Dec 7, 2016 at 10:53 AM, Yedidyah Bar David wrote:
> [cut]
>>
>> If you have another host, you can migrate all VMs to the other host,
>> move current to maintenance, remove it, then add it with the new name
>>
On Wed, Dec 7, 2016 at 12:26 PM, Mark Steckel wrote:
> Yedidyah - very helpful! Thanks.
>
> A follow-up question re the FQDN for the hosted engine: My understanding is
> that the FQDN must be resolvable when "hosted-engine --deploy" is executed.
> However, should the IP that the FQDN resolves to
I see exactly the same issue in ovirt-engine-4.0.6.2-1
Please note the issue produces no logs in /var/log/ovirt-engine/*log
From: on behalf of "Maton, Brett"
Date: Tuesday 6 December 2016 at 16:42
To: Alexander Wels
Cc: Ovirt Users
Subject: Re: [ovirt-users] web-ui issues
Ok thanks.
I've
This didn't get sent to the list...
-- Forwarded message --
From: Alexander Wels
Date: 6 December 2016 at 16:43
Subject: Re: [ovirt-users] web-ui issues
To: "Maton, Brett"
On Tuesday, December 6, 2016 4:41:35 PM EST you wrote:
> Not odd at all, but yes it does work for awhile b
On Wed, Dec 7, 2016 at 1:53 PM, Marcelo Leandro wrote:
> Hello,
> I am try this and migration successful now and it is not happening downtime.
> Use custom migration downtime = 5000
> Logs Attached.
>
> Migration Start = 8:33 AM
> Migration Completed = 8:37 AM
Glad it worked, thanks for the repor
We are looking into the issue.
>From what I saw this is specific in the VMs tab, so we're trying to
understand what might have caused it.
Thanks,
Oved
On Wed, Dec 7, 2016 at 1:21 PM, Maton, Brett
wrote:
> This didn't get sent to the list...
>
> -- Forwarded message --
> From: A
No, I did not tested that.
I did not renamed my HE.
Thanks in advance.
Best regards,
Nikolai
Nikolai Sednev
Senior Quality Engineer at Compute team
Red Hat Israel
34 Jerusalem Road,
Ra'anana, Israel 43501
Tel: +972 9 7692043
Mobile: +972 52 7342734
Email: nsed
Happens in the dashboard tab when I login also, but that does display if I
persist in closing the error dialogs.
VM tab doesn't display.
On 7 December 2016 at 12:44, Oved Ourfali wrote:
> We are looking into the issue.
> From what I saw this is specific in the VMs tab, so we're trying to
> und
On 6-12-2016 9:38, Sandro Bonazzola wrote:
> Hi,
> any feedback on 4.1 beta we released last week?
> Thanks,
>
> -
I upgraded from 4.0 to 4.1pre yesterday and had a couple of problems
that I think are of my own doing.
I'm running hosted-engine on my laptop with a NFS data domain (I know
about the d
On Tue, Dec 6, 2016 at 9:38 AM, Sandro Bonazzola
wrote:
> Hi,
> any feedback on 4.1 beta we released last week?
> Thanks,
>
>
>
I see that in storage tab the NFS domain is marked as V4, while in 4.0.5 is
marked as V3.
The nfs mount from host is still v3, but I think it is not related and
instead
Folks,
I executed "hosted-engine --deploy" on a fresh CentOS 7.2 install. Before
executing the cmd I also installed the he-appliance. (Also ran yum update,
installed a few packages and rebooted before doing the hosted engine deploy.)
The process seems to go well but then it hangs here:
On Wed, Dec 7, 2016 at 4:36 PM, Mark Steckel wrote:
> Folks,
>
> I executed "hosted-engine --deploy" on a fresh CentOS 7.2 install. Before
> executing the cmd I also installed the he-appliance. (Also ran yum update,
> installed a few packages and rebooted before doing the hosted engine deploy.)
Log attached.
- Yedidyah Bar David wrote:
> On Wed, Dec 7, 2016 at 4:36 PM, Mark Steckel wrote:
> > Folks,
> >
> > I executed "hosted-engine --deploy" on a fresh CentOS 7.2 install. Before
> > executing the cmd I also installed the he-appliance. (Also ran yum update,
> > installed a few pa
On Wed, Dec 7, 2016 at 4:46 PM, Mark Steckel wrote:
> Log attached.
>
> - Yedidyah Bar David wrote:
>> On Wed, Dec 7, 2016 at 4:36 PM, Mark Steckel wrote:
>> > Folks,
>> >
>> > I executed "hosted-engine --deploy" on a fresh CentOS 7.2 install. Before
>> > executing the cmd I also installed
- Yedidyah Bar David wrote:
> On Wed, Dec 7, 2016 at 4:46 PM, Mark Steckel wrote:
> > Log attached.
> >
> > - Yedidyah Bar David wrote:
> >> On Wed, Dec 7, 2016 at 4:36 PM, Mark Steckel wrote:
> >> > Folks,
> >> >
> >> > I executed "hosted-engine --deploy" on a fresh CentOS 7.2 install.
Hi,
+cc back to the list
Mark Steckel writes:
> Hi Derek,
>
> I solved the first networking issue by changing how Hetzner config'ed
> the /32 on the host. (They were scoping the IP to the gateway which
> was confusing OVirt.)
>
> So now I'm trying to get the /29 working for the VMs... continue b
On Tuesday, December 6, 2016 1:42:33 PM EST Maton, Brett wrote:
> Ok thanks.
>
> I've restarted the ui a few times today, still nothing ( at all ) in
> ui.log
>
> The errors do look like 'iffy' queries, no errors in PostgreSQL logs
> though.
>
Hi Brett,
Some my wonderful team mates worked
Cheers Alex,
The bug is a PITA, but at least an engine restart makes the UI usable if
only for awhile.
Looking forward to the next 4.0.6 release :)
On 7 December 2016 at 15:36, Alexander Wels wrote:
> On Tuesday, December 6, 2016 1:42:33 PM EST Maton, Brett wrote:
> > Ok thanks.
> >
> >
Hi All,
I'm planning to install oVirt 4 with the HC setup from this blogpost and did a
demo setup.
http://www.ovirt.org/blog/2016/08/up-and-running-with-ovirt-4-0-and-gluster-storage/
I've managed to install everything just fine and thought that enabling a
storage network would move all the br
Quack,
The old server is going to retire, so we prepared a replacement.
Tomorrow, between 23:30-00:30 JST, the switch will happen. Any mails on
the ovirt.org domain, including mailing-lists, are affected.
We now have backup servers for imcoming mails, so they will not be lost,
but the processing
Hello group,
I noticed that my dashboard does not show little colored "cubes" which show
storage CPU and RAM usage history status.
Attached an image and logs from /var/log/ovirt-engine-dwh/ovirt-engine-dwhd.log
Here's an extract:
Exception in component tJDBCInput_5
org.postgresql.util.PSQLExcepti
On 07 Dec 2016, at 11:28, Yaniv Kaul wrote:
On Wed, Dec 7, 2016 at 10:57 AM, Roy Golan wrote:
> Hi all,
>
> This is a discussion on the RFE[1] to provide a tool to perform full
> vacuum on our DBs.
>
> First if you are not familiar with vacuum please read this [2]
>
> # Backgroud
> ovirt 'eng
On 7 December 2016 at 21:00, Michal Skrivanek wrote:
>
>
> On 07 Dec 2016, at 11:28, Yaniv Kaul wrote:
>
>
>
> On Wed, Dec 7, 2016 at 10:57 AM, Roy Golan wrote:
>
>> Hi all,
>>
>> This is a discussion on the RFE[1] to provide a tool to perform full
>> vacuum on our DBs.
>>
>> First if you are n
On 7 December 2016 at 21:44, Roy Golan wrote:
>
>
> On 7 December 2016 at 21:00, Michal Skrivanek wrote:
>
>>
>>
>> On 07 Dec 2016, at 11:28, Yaniv Kaul wrote:
>>
>>
>>
>> On Wed, Dec 7, 2016 at 10:57 AM, Roy Golan wrote:
>>
>>> Hi all,
>>>
>>> This is a discussion on the RFE[1] to provide a t
Folks,
Thanks to Didi in another thread I'm making progress. (Lesson learned, choose
'disk' and not 'cdrom' when using the he-appliance.)
So I reset to a fresh CentOS 7, installed various software packages including
ovirt.
I configed eth0 with a /32 public IP. I also added an alias for a x.x.x
Hi Mark,
The error is correct, hosted-engine-1.pcstrac.com is not a valid hostname:
$ host hosted-engine-1.pcstrac.com
$
I'm lost, tho -- was this an error that occurred on the host during
hosted-engine --deploy, or was it an error that occurred in the hosted
enging VM when running engine-setup?
Hi Derek,
- Derek Atkins wrote:
> Hi Mark,
>
> The error is correct, hosted-engine-1.pcstrac.com is not a valid hostname:
>
> $ host hosted-engine-1.pcstrac.com
> $
>
> I'm lost, tho -- was this an error that occurred on the host during
> hosted-engine --deploy, or was it an error that occ
Hi,
Ensure dnsmasq is working and can be accessed by the engine VM?
Log in to the engine VM and test from there?
Maybe set up *real* DNS?
-derek
On Wed, December 7, 2016 3:41 pm, Mark Steckel wrote:
> Hi Derek,
>
> - Derek Atkins wrote:
>> Hi Mark,
>>
>> The error is correct, hosted-engine-
I tested dnsmasq from the host by
dig hostname @local-ip
Worked fine.
The engine VM never comes up to the point where I can access it via the
console...
- Derek Atkins wrote:
> Hi,
>
> Ensure dnsmasq is working and can be accessed by the engine VM?
> Log in to the engine VM and test
In terms of measuring I used pgclu couple of times and it powerfull,easy to
use, and provide very nice HTML reports
http://pgcluu.darold.net/
And also provide autovacum analysis
http://pgcluu.darold.net/example/dolibarr-table-vacuums-analyzes.html
On Wed, Dec 7, 2016 at 9:55 PM, Roy Golan wrot
just forgot to mention that no customization required just plug & play he
will collect a large set of informative data by deafult
On Wed, Dec 7, 2016 at 10:54 PM, Eldad Marciano wrote:
> In terms of measuring I used pgclu couple of times and it powerfull,easy
> to use, and provide very nice HTML
Hi,
You need to make sure resolv.conf is correct (both on the host AND on the
engine vm).
So: dig hostname
(without the @local-ip)
As for the VM not coming up... I'm not sure how to delay "engine-setup"
run. I presume you're running an engine appliance -- I ran my own CentOS
install on the e
Hi,
OK, I reset things and tried again but was more more careful regarding the DNS
setup which I believe was correct this. In other words, the FQDNs were resolved
from both the host and the HE VM.
After the latest failure I execute 'ip address' to see the state of the
interfaces. And lo and be
48 matches
Mail list logo