[Users] Gluster storage
by tristano82＠libero.it
Hello everybody,
i'm successful using ovirt with 16 physical node, in a FC cluster with a very
BIG dell compellent (and so expensive) enterprise storage ;)
I'm researching a new architecture for a new cluster, and i want to
understand
more better the glusterFS integration in ovirt.
As i understand you have to install a normal physical node, with also the
glusterFS package… right ? after that you have to create a new cluster in
ovirt
, new datacenter and put in this new node. in that datacenter you can create
a
new data domain ( glusterFS ) that reside on that host. right ?
and… after that ? ok i have 1 node that are also my " storage ", and if i
want
to all more compute node ? … every new compute node are a new " brick " for
glusterFS so i can expand/redundant the first one ?
i don't have the architecture very clear in my mind, and the documentation
don't clarify the final architecture for this type of usage.
Thanks for help guys
Luke
11 years
[Users] Minor HTML5 Spice Bug
by Thomas Suckow
I have been using the HTML5 Spice websocket plug-in and so far it works
extremely well. I just have two comments/bugs about it. I look on the
issue tracker and I did not see an appropriate component listed, so I
will list them here:
* When the virtual screen is resized (such as during boot when the GUI
login is displayed) the mouse cursor gets messed up and clicking only
clicks the upper left corner of the screen.
* The SSL key has to be readable by the ovirt user rather than root
*cough*. Maybe the proxy_wstunnel apache module could be of use to avoid
SSL in the plugin.
--
Thomas
11 years
[Users] Bug cron 3.3.1-2 ?
by Sven Kieske
Hi,
It seems, the ovirt-cron does something which does not work
out of the box:
From: Anacron <root(a)management.test>
To: root(a)management.test
Content-Type: text/plain; charset="ANSI_X3.4-1968"
Subject: Anacron job 'cron.daily' on management.test
Message-Id: <20131025010702.1A48740038F(a)management.test>
Date: Fri, 25 Oct 2013 03:07:02 +0200 (CEST)
/etc/cron.daily/ovirt-cron:
ls: cannot access /var/log/ovirt-engine/server.log.*: No such file or
directory
ls: cannot access /var/log/ovirt-engine/jasperserver.log.*: No such file
or directory
ls: cannot access /var/log/ovirt-engine/server.log.*.gz: No such file or
directory
ls: cannot access /var/log/ovirt-engine/jasperserver.log.*.gz: No such
file or directory
Is this intended behaviour?
ovirt-engine 3.3.1-2 on CentOS 6.4.
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
11 years
[Users] RFE/Bug? Cloud-Init in oVirt 3.3.1 / IPv6 Support
by Sven Kieske
Hi,
currently, you can not set
a static network via Cloud-Init.
How to reproduce:
Select a shutdown vm, click run once.
Click Initial Run, select Cloud-Init
Now select "Network" and "add new"
Name your interface, e.g. eth0
Do not configure DHCP, instead,
fill in IP Address, Netmask, Gateway, etc.
I would suppose that this would pass the following options
into the meta-data:
iface eth0 inet static
but if you mount the meta-data cd-rom into any vm and read
the meta-data.json it says:
iface eth0 inet none
the rest of the information seems to be correct, though.
You can see this from 2 point of views:
1. If I do not select DHCP and I configure IP Address etc. I want
a static configuration, therefore "static" should be in the meta-data.
If I would have wanted "none", I wouldn't bother configuring the
interface, would I? -> Bug
2. There is no button for "static" in the GUI, therefore the option
get's not passed, "none" may be the default option.
In this case, it would be cool to have a checkbox for "static".
--> RFE
I didn't test this from the API yet, but I hope there is an option
to set the networking to static from there?
What do you think? Bug or RFE? Can this be fixed in 3.3.1.1 maybe (fix
should be small, without looking into the code)?
I can't always do full upgrades (3.3.2 would be next).
My second topic would be IPv6 Support:
It simply does not exist in Cloud-Init to pass this option to the
guest, I read this old thread:
http://lists.ovirt.org/pipermail/engine-devel/2013-June/004893.html
My Question: Are there any plans to improve this?
I will work around it maybe through custom parsing and file injecting
the IPv6 data through Cloud-Init, but would prefer to pass this
information simply to Cloud-Init.
--
Mit freundlichen Grüßen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
Königsberger Straße 6
32339 Espelkamp
T: +49-5772-293-100
F: +49-5772-293-333
https://www.mittwald.de
Geschäftsführer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen
Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen
11 years
[Users] Self contained engine ETA
by Juan Pablo Lorier
Hi,
Is there any estimated time for self contained engine release? Will it
be possible to migrate engine to existing DC? I'm now buying a new
server just for the engine that actually runs in a vm on a different
virtualization platform, and I'll like to know if it's woth the effort
of migration at this time our I should wait a bit to get the feature.
Regards,
11 years
[Users] Installation fails on Fedora 19 - Failed to execute stage 'Closing up': Engine unreachable
by Peter Lerche
Hi,
I new to oVirt want to install a all-in-one package for testing only.
Installed a vanilla Fedora 19 64bit and followed the guide.
sudo yum localinstall http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm
sudo yum install -y ovirt-engine-setup-plugin-allinone
sudo engine-setup
I get following error when running engine-setup:
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ ERROR ] Failed to execute stage 'Closing up': Engine unreachable
[ INFO ] Stage: Clean up
Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20131128155012.log
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
When trying to access the webinterface i get:
javax.ejb.EJBException: java.lang.IllegalStateException: Could not obtain connection to the database. Please make sure that DB is up and accepting connections, and restart the application.
org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:166)
I have tried to re-run the engine-setup and re-install Fedora/oVirt several times but it does not help.
Is this a common error which I just can't find the documentation ?
Here is the full installation output and the last part of the logfile:
-----------------------------------------------------------------------
[ INFO ] Stage: Initializing
[ INFO ] Stage: Environment setup
Configuration files: ['/etc/ovirt-engine-setup.conf.d/10-packaging-aio.conf', '/etc/ovirt-engine-setup.conf.d/10-packaging.conf']
Log file: /var/log/ovirt-engine/setup/ovirt-engine-setup-20131128155012.log
Version: otopi-1.1.2 (otopi-1.1.2-1.fc19)
[ INFO ] Hardware supports virtualization
[ INFO ] Stage: Environment packages setup
[ INFO ] Stage: Programs detection
[ INFO ] Stage: Environment setup
[ INFO ] Stage: Environment customization
--== PACKAGES ==--
[ INFO ] Checking for product updates...
[ INFO ] No product updates found
--== ALL IN ONE CONFIGURATION ==--
Configure VDSM on this host? (Yes, No) [No]: yes
Local storage domain path [/var/lib/images]:
Local storage domain name [local_storage]:
--== NETWORK CONFIGURATION ==--
Host fully qualified DNS name of this server [mydomain.com]:
firewalld was detected on your computer. Do you wish Setup to configure it? (yes, no) [yes]:
--== DATABASE CONFIGURATION ==--
Where is the database located? (Local, Remote) [Local]:
Setup can configure the local postgresql server automatically for the engine to run. This may conflict with existing applications.
Would you like Setup to automatically configure postgresql, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
Using existing credentials
--== OVIRT ENGINE CONFIGURATION ==--
Engine admin password:
Confirm engine admin password:
Application mode (Both, Virt, Gluster) [Both]: Virt
Default storage type: (NFS, FC, ISCSI, POSIXFS) [NFS]:
--== PKI CONFIGURATION ==--
Organization name for certificate [myCompany.com]: myCompany
--== APACHE CONFIGURATION ==--
Setup can configure the default page of the web server to present the application home page. This may conflict with existing applications.
Do you wish to set the application as the default page of the web server? (Yes, No) [Yes]:
Setup can configure apache to use SSL using a certificate issued from the internal CA.
Do you wish Setup to configure that, or prefer to perform that manually? (Automatic, Manual) [Automatic]:
--== SYSTEM CONFIGURATION ==--
Configure an NFS share on this server to be used as an ISO Domain? (Yes, No) [Yes]:
Local ISO domain path [/var/lib/exports/iso]:
Local ISO domain name [ISO_DOMAIN]:
Configure WebSocket Proxy on this machine? (Yes, No) [Yes]:
--== END OF CONFIGURATION ==--
[ INFO ] Stage: Setup validation
--== CONFIGURATION PREVIEW ==--
Database name : engine
Database secured connection : False
Database host : localhost
Database user name : engine
Database host name validation : False
Datbase port : 5432
NFS setup : True
PKI organization : myCompany
NFS mount point : /var/lib/exports/iso
Application mode : virt
Firewall manager : firewalld
Configure WebSocket Proxy : True
Host FQDN : mydomain.com
Datacenter storage type : nfs
Configure local database : True
Set application as default page : True
Configure Apache SSL : True
Configure VDSM on this host : True
Local storage domain directory : /var/lib/images
Please confirm installation settings (OK, Cancel) [OK]:
[ INFO ] Stage: Transaction setup
[ INFO ] Stopping engine service
[ INFO ] Stopping websocket-proxy service
[ INFO ] Stage: Misc configuration
[ INFO ] Stage: Package installation
[ INFO ] Stage: Misc configuration
[ INFO ] Initializing PostgreSQL
[ INFO ] Creating PostgreSQL database
[ INFO ] Configurating PostgreSQL
[ INFO ] Creating database schema
[ INFO ] Creating CA
[ INFO ] Configurating WebSocket Proxy
[ INFO ] Generating post install configuration file '/etc/ovirt-engine-setup.conf.d/20-setup-ovirt-post.conf'
[ INFO ] Stage: Transaction commit
[ INFO ] Stage: Closing up
--== SUMMARY ==--
An ISO NFS share has been created on this host.
If IP based access restrictions are required, edit:
entry /var/lib/exports/iso in /etc/exports.d/ovirt-engine-iso-domain.exports
SSH fingerprint: XX XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
Internal XX XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX:XX
Web access is enabled at:
http://mydomain.com:80/ovirt-engine
https://mydomain.com:443/ovirt-engine
Please use the user "admin" and password specified in order to login into oVirt Engine
--== END OF SUMMARY ==--
[ INFO ] Starting engine service
[ INFO ] Restarting httpd
[ ERROR ] Failed to execute stage 'Closing up': Engine unreachable
[ INFO ] Stage: Clean up
Log file is located at /var/log/ovirt-engine/setup/ovirt-engine-setup-20131128155012.log
[ INFO ] Stage: Pre-termination
[ INFO ] Stage: Termination
[ ERROR ] Execution of setup failed
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV OVESETUP_SYSTEM/selinuxRestorePaths=list:'['/var/lib/images', '/var/lib/exports/iso']'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV OVESETUP_SYSTEM/shmmax=int:'35554432'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV OVESETUP_SYSTEM/userApache=str:'apache'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV OVESETUP_SYSTEM/userEngine=str:'ovirt'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV OVESETUP_SYSTEM/userPostgres=str:'postgres'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV OVESETUP_SYSTEM/userRoot=str:'root'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV OVESETUP_SYSTEM/userVdsm=str:'vdsm'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV PACKAGER/keepAliveInterval=int:'30'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV PACKAGER/yumDisabledPlugins=list:'[]'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV PACKAGER/yumEnabledPlugins=list:'[]'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV PACKAGER/yumExpireCache=bool:'True'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV PACKAGER/yumRollback=bool:'True'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV PACKAGER/yumpackagerEnabled=bool:'True'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV SYSTEM/clockMaxGap=int:'5'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV SYSTEM/clockSet=bool:'False'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV SYSTEM/commandPath=str:'/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV SYSTEM/reboot=bool:'False'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV SYSTEM/rebootAllow=bool:'True'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:456 ENV SYSTEM/rebootDeferTime=int:'10'
2013-11-28 16:05:51 DEBUG otopi.context context.dumpEnvironment:458 ENVIRONMENT DUMP - END
2013-11-28 16:05:51 DEBUG otopi.context context._executeMethod:123 Stage pre-terminate METHOD otopi.plugins.otopi.dialog.cli.Plugin._pre_terminate
2013-11-28 16:05:51 DEBUG otopi.context context._executeMethod:129 condition False
2013-11-28 16:05:51 INFO otopi.context context.runSequence:380 Stage: Termination
2013-11-28 16:05:51 DEBUG otopi.context context.runSequence:384 STAGE terminate
2013-11-28 16:05:51 DEBUG otopi.context context._executeMethod:123 Stage terminate METHOD otopi.plugins.ovirt_engine_common.core.misc.Plugin._terminate
2013-11-28 16:05:51 ERROR otopi.plugins.ovirt_engine_common.core.misc misc._terminate:146 Execution of setup failed
2013-11-28 16:05:51 DEBUG otopi.context context._executeMethod:123 Stage terminate METHOD otopi.plugins.otopi.dialog.human.Plugin._terminate
2013-11-28 16:05:51 DEBUG otopi.context context._executeMethod:123 Stage terminate METHOD otopi.plugins.otopi.dialog.machine.Plugin._terminate
2013-11-28 16:05:51 DEBUG otopi.context context._executeMethod:129 condition False
2013-11-28 16:05:51 DEBUG otopi.context context._executeMethod:123 Stage terminate METHOD otopi.plugins.otopi.core.log.Plugin._terminate
11 years
[Users] Introductory email
by Peter Lerche
Hi,
Just to introduce myself, I am Peter Lerche co-founder of a Danish hosting provider. We have for some years been looking at cloud/VPS solutions for our customers but until now have not found a suitable platform.
oVirt looks promising....... on paper and now we want to test it.
--
Best regards
Peter Lerche
EasySpeedy ApS
377, Diplomvej
Scion-DTU Science Park
DK-2800, Kgs. Lyngby
Denmark
Phone: +45 4594 1401
http://EasySpeedy.com
_____________________________________________________
European Quality Unmanaged Server Hosting
Permanent KVMoIP included in all dedicated servers
Network and Power Uptime - 99,98% Since 16 Jan 2006
Follow us on Twitter - https://twitter.com/easyspeedy
_____________________________________________________
11 years
[Users] oVirt 3.4 SLA & Scheduling feature overview
by Gilad Chaplik
------=_Part_42557408_1097164829.1385655491891
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
The following is a new meeting request:
Subject: oVirt 3.4 SLA & Scheduling feature overview
Organizer: "Gilad Chaplik" <gchaplik(a)redhat.com>
Time: Monday, December 2, 2013, 5:00:00 PM - 6:00:00 PM GMT +02:00 Jerusalem
Invitees: users(a)ovirt.org; arch(a)ovirt.org
*~*~*~*~*~*~*~*~*~*
Hi all,
I invite you to a overview for planed SLA & Scheduling features for oVirt 3.4.
We will talk briefly about every suggested feature including:
- positive/negative affinity between group of VMs
- power saving policy moving hosts to sleep
- time based policy (SLA during the day, power saving at night)
- application level HA (monitor the service inside the VM)
People are welcome to join in the #ovirt channel on irc.OFTC.net.
Thanks
------=_Part_42557408_1097164829.1385655491891
Content-Type: text/calendar; charset=utf-8; method=REQUEST; name=meeting.ics
Content-Transfer-Encoding: 7bit
BEGIN:VCALENDAR
PRODID:Zimbra-Calendar-Provider
VERSION:2.0
METHOD:REQUEST
BEGIN:VTIMEZONE
TZID:Asia/Jerusalem
BEGIN:STANDARD
DTSTART:16010101T020000
TZOFFSETTO:+0200
TZOFFSETFROM:+0300
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=10;BYDAY=-1SU
TZNAME:IST
END:STANDARD
BEGIN:DAYLIGHT
DTSTART:16010101T020000
TZOFFSETTO:+0300
TZOFFSETFROM:+0200
RRULE:FREQ=YEARLY;WKST=MO;INTERVAL=1;BYMONTH=3;BYDAY=-1FR
TZNAME:IDT
END:DAYLIGHT
END:VTIMEZONE
BEGIN:VEVENT
UID:4191272a-a49b-42d1-8571-2384c9793ddd
SUMMARY:oVirt 3.4 SLA & Scheduling feature overview
ATTENDEE;CN=oVirt Mailing List;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RS
VP=TRUE:mailto:users@ovirt.org
ATTENDEE;ROLE=REQ-PARTICIPANT;PARTSTAT=NEEDS-ACTION;RSVP=TRUE:mailto:arch@ov
irt.org
ORGANIZER;CN=Gilad Chaplik:mailto:gchaplik@redhat.com
DTSTART;TZID="Asia/Jerusalem":20131202T170000
DTEND;TZID="Asia/Jerusalem":20131202T180000
STATUS:CONFIRMED
CLASS:PUBLIC
X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
TRANSP:OPAQUE
LAST-MODIFIED:20131128T161811Z
DTSTAMP:20131128T161811Z
SEQUENCE:0
DESCRIPTION:The following is a new meeting request:\n\nSubject: oVirt 3.4 SL
A &\; Scheduling feature overview \nOrganizer: "Gilad Chaplik" <gchaplik@
redhat.com> \n\nTime: Monday\, December 2\, 2013\, 5:00:00 PM - 6:00:00 PM G
MT +02:00 Jerusalem\n \nInvitees: users(a)ovirt.org\; arch(a)ovirt.org \n\n\n*~*
~*~*~*~*~*~*~*~*\n\nHi all\, \n\nI invite you to a overview for planed SLA &
Scheduling features for oVirt 3.4.\nWe will talk briefly about every sugges
ted feature including:\n- positive/negative affinity between group of VMs\n-
power saving policy moving hosts to sleep\n- time based policy (SLA during
the day\, power saving at night)\n- application level HA (monitor the servic
e inside the VM) \n\nPeople are welcome to join in the #ovirt channel on irc
.OFTC.net.\n\nThanks\n\n
BEGIN:VALARM
ACTION:DISPLAY
TRIGGER;RELATED=START:-PT5M
DESCRIPTION:Reminder
END:VALARM
END:VEVENT
END:VCALENDAR
------=_Part_42557408_1097164829.1385655491891--
11 years
[Users] oVirt vdsm network problem
by Jakub Bittner
Hello,
I found strange problem in vdsm 4.13.0 with oVirt 3.3.1. After 30 hours
from update (ovirt -> 3.3.1, vdsm -> 4.13) my one vlan network does not
work. There is nothing in log, I can see network trafic from not working
vlan on node in tcpdump, but it not come to VM.
After vdsm restart on node it works like expected.
I take a look in to oVirt -> Host -> Network Interface and all nodes has
bond interface changed from "Mode 4 Dynamic link agregation" to "Custom:
mode=4" and Custom mode is filled by "mode=4" Mabe it is the same, but
who change that?
I can have one node in this status if someone will want more info or logs.
11 years
