Re: [ovirt-users] ovirt and CAS SSO

2016-03-11 Thread Martin Perina 
Hi,

I'm glad to hear that you were able to successfully configure aaa-misc
and mod_auth_cas to allow CAS based login for oVirt.

Unfortunately regarding CAS authorization for oVirt I have somewhat bad
news for you. But let me explain the issue a bit:

1. Using aaa-misc we are able to pass only user name of the authenticated
   user from apache to ovirt.

2. After that we have authenticated user on oVirt and then we pass
   its username to authz extension to fetch full principal record including
   group memberships. At the moment we don't pass anything else to authz
   extension, just principal name (username).

So here are options how to enable CAS authorization for oVirt:

1. Implement new authz extension which will fetch principal record for CAS
   server (if this is possible, I don't know much about CAS)

2. Or implement new authn/authz extensions specific to CAS which will use
   CAS API do both authn and authz.

3. Use LDAP as a backend for you CAS server (if possible) and configure
   authz part using ovirt-engine-extension-aaa-ldap

4. You could also create an RFE bug on oVirt to add CAS support, but
   no promises from me :-) you are the first user asking about CAS support

Regarding documentation:

  - oVirt engine extensions API JavaDoc is contained in package
ovirt-engine-extensions-api-impl-javadoc

  - Ondra wrote some great articles about oVirt AAA configurations and
published them on his blog [1]

  - You can also take a look at some presentations about oVirt extensions:

  The New oVirt Extension API: Taking AAA to the next level [2] [3]
  oVirt Extension API: The first step for fully modular oVirt [4] [5]

  - And you can also take a look at sources of existing aaa-ldap [6],
aaa-misc [7] and aaa-jdbc [8] extensions

And of course feel free to ask!

Regards

Martin Perina

[1] http://machacekondra.blogspot.cz/
[2] https://www.youtube.com/watch?v=bSbdqmRNLi0
[3] 
http://www.slideshare.net/MartinPeina/the-new-ovirt-extension-api-taking-aaa-authentication-authorization-accounting-to-the-next-level
[4] https://www.youtube.com/watch?v=9b9WVFsy_yg
[5] 
http://www.slideshare.net/MartinPeina/ovirt-extension-api-the-first-step-for-fully-modular-ovirt
[6] https://github.com/oVirt/ovirt-engine-extension-aaa-ldap
[7] https://github.com/oVirt/ovirt-engine-extension-aaa-misc
[8] https://github.com/oVirt/ovirt-engine-extension-aaa-jdbc

- Original Message -
> From: "Fabrice Bacchella" 
> To: Users@ovirt.org
> Sent: Tuesday, March 8, 2016 11:54:13 AM
> Subject: [ovirt-users] ovirt and CAS SSO
> 
> I'm trying to add CAS SSO to ovirt.
> 
> For authn (authentication),
> org.ovirt.engineextensions.aaa.misc.http.AuthnExtension is OK, I put jboss
> behind an Apache with mod_auth_cas.
> 
> Now I'm fighting with authz (authorization). CAS provides everything needed
> as header. So I don't need ldap or jdbc extensions. Is there anything done
> about that or do I need to write my own extension ? Is there some
> documentation about that ?
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
> 
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] New install of hosted-engine using FibreChannel storage presenting Errors

2016-03-11 Thread Paxton, Darren 
Hi all
Set up a brand new cluster with hosted-engine. Chose Fibre-Channel as the 
storage mechanism however on completion, running hosted-engine -vm-status I get 
the following;

# hosted-engine --vm-status
Traceback (most recent call last):
  File "/usr/lib64/python2.7/runpy.py", line 162, in _run_module_as_main
"__main__", fname, loader, pkg_name)
  File "/usr/lib64/python2.7/runpy.py", line 72, in _run_code
exec code in run_globals
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/vm_status.py", line 
117, in 
if not status_checker.print_status():
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_setup/vm_status.py", line 
60, in print_status
all_host_stats = ha_cli.get_all_host_stats()
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", 
line 160, in get_all_host_stats
return self.get_all_stats(self.StatModes.HOST)
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", 
line 107, in get_all_stats
stats = self._parse_stats(stats, mode)
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/client/client.py", 
line 146, in _parse_stats
md = metadata.parse_metadata_to_dict(host_id, data)
  File 
"/usr/lib/python2.7/site-packages/ovirt_hosted_engine_ha/lib/metadata.py", line 
156, in parse_metadata_to_dict
constants.METADATA_FEATURE_VERSION))
ovirt_hosted_engine_ha.lib.exceptions.FatalMetadataError: Metadata version 5 
from host 20 too new for this agent (highest compatible version: 1)

This also results in adding a 2nd host failing due to a similar problem. I saw 
a previous post regarding iscsi storage resulting in similar errors but not 
FibreChannel.

I can provide engine logs and such like if someone can guide me to what exact 
files to provide.

I had cleared down the fibre-chaannel storage but do I need to wipe the devices 
fully before trying again?

Thanks

Darren
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

2016-03-11 Thread Jean-Marie Perron 
Hi Uwe,

Thank you for your reply.

I tested versions 0.6, 0.7, 0.11 and 0.12 of qxlwddm. It's always the same.

Jean-Marie

-Message d'origine-
De : users-boun...@ovirt.org [mailto:users-boun...@ovirt.org] De la part de Uwe 
Laverenz
Envoyé : vendredi 11 mars 2016 10:49
À : users@ovirt.org
Objet : Re: [ovirt-users] Windows 10

Hi,

Am 10.03.2016 um 17:18 schrieb Jean-Marie Perron:
> Hello,
>
> OVirt 3.6.3 is installed on CentOS 7.
>
> I use 64-bit Windows 10 client with spice display.
>
> After installing the spice-guest-tools and oVirt-tools-setup on the VM 
> Windows 10, the display always lag and slow.
>
> The display on a Windows 7 VM is fluid.
>
> On Device Manager and Display adapters, I see see the graphics card 
> "Red Hat QLX Controller"
>
> Are Windows 10 is fully supported by oVirt?

I haven't tested this but please have a look at the qxlwddm driver here:

https://people.redhat.com/vrozenfe/qxlwddm/


Some people reported that this works for Win 8/8.1/10:

https://bugzilla.redhat.com/show_bug.cgi?id=895356

cu,
Uwe
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] Windows 10

2016-03-11 Thread Sandro Bonazzola 
On Fri, Mar 11, 2016 at 10:48 AM, Uwe Laverenz  wrote:

> Hi,
>
> Am 10.03.2016 um 17:18 schrieb Jean-Marie Perron:
>
>> Hello,
>>
>> OVirt 3.6.3 is installed on CentOS 7.
>>
>> I use 64-bit Windows 10 client with spice display.
>>
>> After installing the spice-guest-tools and oVirt-tools-setup on the VM
>> Windows 10, the display always lag and slow.
>>
>> The display on a Windows 7 VM is fluid.
>>
>> On Device Manager and Display adapters, I see see the graphics card "Red
>> Hat QLX Controller"
>>
>> Are Windows 10 is fully supported by oVirt?
>>
>
It's supposed to be fully supported.


>
> I haven't tested this but please have a look at the qxlwddm driver here:
>
> https://people.redhat.com/vrozenfe/qxlwddm/
>
>
> Some people reported that this works for Win 8/8.1/10:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=895356



Adding SPICE and WGT relevant people


>
>
> cu,
> Uwe
>
> ___
> Users mailing list
> Users@ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>



-- 
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

[ovirt-users] a KVM Host has different UUIDs ?

2016-03-11 Thread Jean-Pierre Ribeauville 
Hi,


When retrieving KVM Host UUID   via virsh  getcapabilities()  or via  ovirt 
Python SDK ( by using  obj.get_id() ), then both UUIDs are not identical .

(FYI, Guest UUIDs retrieved via both ways , i.e. virDomainGetUUIDString() or 
python ovirt sdk ,  are identical.)


Did I miss something ?

Thx for help

Regards,


Jean-Pierre RIBEAUVILLE

+33 1 4717 2049

[axway_logo_tagline_87px]

___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users

Re: [ovirt-users] [ovirt-devel] Welcome: New ovirt.org website!

2016-03-11 Thread Nathanaël Blanchet 

Hello,

it seems that some links are not the good ones, in particular for some 
pictures, for instance 
http://www.ovirt.org/develop/release-management/features/infra/python-sdk/

But it was perhaps already the case before the new site...

Le 08/03/2016 16:13, Mikey Ariel a écrit :

Thanks Rene for the heads up! As I wrote, we welcome contributions, so
if you have the bandwidth to submit a PR with fixing the links it would
be really helpful. Otherwise, please open an issue for this on GitHub
and we'll try to route the task accordingly :)

Cheers,
Mikey

On 03/03/2016 03:53 PM, René Koch wrote:

Hi Mikey,

The new page looks really good.

I figured out, that all of the links to presentations and templates are
still pointing to the old Mediawiki url and so all presentations are
unavailable:
https://www.ovirt.org/community/get-involved/resources/slide-decks/


Regards,
René


On 02/19/2016 04:57 PM, Mikey Ariel wrote:
Following yesterday's pre-launch email[1], I'm happy to announce that
the new ovirt.org[2] website is now live in **public beta** and
available for community review.

All the information in this email is also available in the first blog
post of our shiny new oVirt blog[3]. Read on for information about new
features, known issues, and a call for reviews.

The old MediaWiki site is still available in read-only[4], and will be
taken offline on **March 1, 2016**. This is to ensure that you can
compare pages and review migrated content.

What's New
==

The new Website is full of improvements and enhancements, check out
these highlights:

* Source content is now formatted in Markdown instead of MediaWiki.
This means that you can create and edit documentation, blog posts, and
feature pages with the same Markdown syntax you know.

* The Website is deployed with Middleman and stored on GitHub. This
means that you can make changes to content with the same GitHub
contribution workflow that you know (fork, clone, edit, commit, submit
pull request). We even have an "Edit this page on GitHub" link at the
bottom of every page!

* New layout and design, from breadcrumbs to sidebards and an upgraded
landing page. (This is still WIP, please see known issues.)

* Automatic redirects from the old MediaWiki site. This means that if
the wiki page exists in the new website, previously-released URLs will
redirect to that page. If the page was removed, the Search page will
open with the page title auto-filled in the search box.

* Hierarchical content structure. This means that instead of flat
Wiki-style files, the deployed Website reflects an organized source
repo with content sorted into directories and sub-directories.

* Official oVirt blog! Our new blog welcomes contributions. This means
that if you solved a problem with oVirt, want to share your oVirt
story, or describe a cool integration, you can submit a pull request
with a blog post and we will provide editorial reviews and help
publish your posts.

* Standardized contribution process. The GitHub repo now includes a
README.md[5] file that you can use to learn about how to add and edit
content on the website. We welcome pull requests!

Known Issues


Despite our best efforts, there are still a few kinks with the new
website that you should be aware of:

* Attempting to navigate to ovirt.org (without www.) leads to a
redirect loop. We have a ticket open with OpenShift, our hosting
service to fix this.

* Only http is available. We also have a ticket with OpenShift to add
SSL and enable https.

* Home page and Download page are still being upgraded by our UX
experts, expect some cool new changes soon!

* Feature pages look-and-feel is still under construction. You can
still edit and push feature pages as usual.

What's Next
===

Even though the Website is live, the work is hardly over. We'd like to
ask for your help in:

* Reviewing content for anything obsolete or outdated (each page in
the new website includes a header toolbar with metadata from the
original wiki page for your convenience)

* Submitting blog posts or any other content that you wish to share
with the oVirt community

* Reporting bugs and proposing enhancements, for example broken links
or missing pages

We hope you will enjoy the new oVirt Website, looking forward to your
feedback and contributions!

[1] http://lists.ovirt.org/pipermail/devel/2016-February/012372.html
[2] http://www.ovirt.org/
[3] http://www.ovirt.org/blog/2016/02/welcome-to-new-ovirt-site/
[4] http://old.ovirt.org/Home
[5] https://github.com/oVirt/ovirt-site/blob/master/README.md

-- Mikey Ariel
Community Lead, oVirt
www.ovirt.org

"To be is to do" (Socrates)
"To do is to be" (Jean-Paul Sartre)
"Do be do be do" (Frank Sinatra)

Mobile: +420-702-131-141
IRC: mariel / thatdocslady
Twitter: @ThatDocsLady



___
Devel mailing list
de...@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel





___
Users mailing

Re: [ovirt-users] Windows 10

2016-03-11 Thread Uwe Laverenz 

Hi,

Am 10.03.2016 um 17:18 schrieb Jean-Marie Perron:

Hello,

OVirt 3.6.3 is installed on CentOS 7.

I use 64-bit Windows 10 client with spice display.

After installing the spice-guest-tools and oVirt-tools-setup on the VM
Windows 10, the display always lag and slow.

The display on a Windows 7 VM is fluid.

On Device Manager and Display adapters, I see see the graphics card "Red
Hat QLX Controller"

Are Windows 10 is fully supported by oVirt?


I haven't tested this but please have a look at the qxlwddm driver here:

https://people.redhat.com/vrozenfe/qxlwddm/


Some people reported that this works for Win 8/8.1/10:

https://bugzilla.redhat.com/show_bug.cgi?id=895356

cu,
Uwe
___
Users mailing list
Users@ovirt.org
http://lists.ovirt.org/mailman/listinfo/users