If you just want to make quick progress, you can copy your iso file to your
images directory. You will want to put the .iso file (it must have a .iso
extension) in the correct directory. e.g.
cp my.iso /export/iso-images/some
uuid/images/----
The actual
I decided to start over and reinstall with the latest nightly build. When
trying to get the system setup, I get the following error when trying to add a
host.
Host mech is compatible with versions (3.0,3.1) and cannot join Cluster
DCCluster which is set to version 3.2
I saw no way to create a
least to look into the
problem.
Can you try it with nfs3 and tell us if it works?
Note, more comments in the email body.
Regards,
Vered
- Original Message -
From: Brian Vetter bjvet...@gmail.com
To: users@ovirt.org
Sent: Tuesday, October 23, 2012 5:06:06 AM
Subject: [Users
.
--
Federico
- Original Message -
From: Brian Vetter bjvet...@gmail.com
To: Federico Simoncelli fsimo...@redhat.com
Cc: Vered Volansky ve...@redhat.com, users@ovirt.org, David Teigland
teigl...@redhat.com
Sent: Tuesday, October 23, 2012 6:10:36 PM
Subject: Re: [Users] Error creating
-- on
sanlock_use_samba -- off
Do I turn these all on or is there some other setting I need to enable?
Brian
On Oct 23, 2012, at 9:54 PM, Brian Vetter wrote:
That was the problem. I checked the sanlock_use_nfs boolean and it was off. I
set it and then created and attached the storage and it all works
I get the following AVC msg when trying to run a VM from the ovirt admin tool:
type=AVC msg=audit(1351051834.851:720): avc: denied { read } for pid=979
comm=sanlock name=8798edc0-dbd2-466d-8be9-1997f63e196f dev=dm-4
ino=3145737 scontext=system_u:system_r:sanlock_t:s0-s0:c0.c1023
I have reinstalled my ovirt installation using the nightly builds so that I can
try out non-admin REST API access to ovirt. After installing the engine,
connecting to my directory system, creating a domain, and adding a host (all
successfully), I tried to add my first storage domain (NFS).
On Oct 3, 2012, at 12:55 AM, Itamar Heim wrote:
snip ...
So based upon what I see in this log file, it would seem that the
connect API wants to make sure that I am an admin and not a regular user.
Which gets me back to my original question: Do the REST API and the
ovirt-shell require
I've been scouring through the install notes and the architecture documents but
didn't find my answer. Is there a way to cluster or replicate the userportal
app or is it strictly a single instance? Any thoughts to the scale of a large
VDI system with 10,000 desktops and their VMs and how that
, Itamar Heim wrote:
On 10/02/2012 06:28 AM, Brian Vetter wrote:
I've done two different things. First, I associated one of my groups in my
directory with being a VMUser which gave members access to a particular VM.
If I login with one of those users via the User portal, I can see their VM
(or VMs
Heim wrote:
On 10/02/2012 04:52 PM, Brian Vetter wrote:
Adding the Filter:true header to the curl request doesn't change anything.
If the user account is not an admin account, I get a 401 status result. So
my question still stands, can the REST API be used by a mere, non-admin
mortal
admin portal, I see the following
permissions for the VM:
UserRole
Brian Vetter (bjvetter@domain) UserRole
Brian
On Oct 2, 2012, at 10:27 AM, Itamar Heim wrote:
On 10/02/2012 05:20 PM, Brian Vetter wrote:
3.1 added support for non admin to use
a proper permissions in order to view these VMs
Yair
On 10/02/2012 05:09 AM, Brian Vetter wrote:
I was trying to use both the rest api to view a user's vm information. I
found that the REST APIs always returned an authentication error if the
account I had logged into was not an ovirt
13 matches
Mail list logo
