From Fedora Project Wiki

< XavierLamien

Revision as of 15:55, 25 January 2009 by Laxathom (talk | contribs)

<DRAFT>

Fedora Cloud

This page is has been setup to track down what is actually going on our fedora cloud test instance which is running on xen6 box for now. It will also a start page about what we need to do, what work need to be done.


Overview

technologies we'll use

  • Virtualization : KVM
  • Platform management : Ovirt (http://ovirt.org)
  • Storage : ISCSI share
  • Disk management : LVM


Cloud instance

Currently, the cloud instance is running under a ovirt-appliance provided by the ovirt team.
We need to know how we will deploy the cloud instance in fedora infrastructure.

  • Use configured ovirt-appliance (just like the test instance)
  • Deploy and manage all apps that ovirt uses (cobbler, collectd, db, etc)

i'm for the second choice.


oVIRT

Puppet Files

You will find below all files which need to be puppet managed.

# In /puppet/config/cloud
/etc/ovirt-server/database.yml
/etc/ovirt-server/db
/etc/ovirt-server/development.rb
/etc/ovirt-server/production.rb
/etc/ovirt-server/test.rb
/etc/sysconfig/ovirt-mongrel-rails
/etc/sysconfig/ovirt-rails
# In /puppet/config/web /etc/httpd/conf.d/ovirt-server.conf

[more]


Authentication (web access)

The default authentication for ovirt is handles by krb5 through LDAP database (it's also includes a IPA instance). It's not the way we want to follow.
Fedora people should be able to log in through their FAS account (or trusted CA ?).
Now i'm wondering if we'll follow that way which will imply to hack a bit ovirt (e.g don't let fedora people see Redhat pool through the web interface) or just handle a trac instance where they could request a virtual machine or again, by apply to a new-cloud-specific group with additional tools which will handle vms.

  • Current ETA:

I currently setup the web interface to deals with Apache Authentication.
The password file is stored in /srv

User and Permissions management

[to edit]


Hosts management

Ovirt is able to manage different hosts from different places.
Hosts informations are indexes and stored in its database (table Host).
From all i know, you cannot register any hosts from the web interface. That should be "Add first host to this..." button but it doesn't work.
You only able to add hosts from available registered hosts (means stored in the DB) to pools or smart pools or anythings else.

  • How to register hosts

You can register hosts through the ovirt-add-hosts python-shell-script.

Storage management

[to edit]


Pools management

[to edit]


Smart Pools

I don't need to talk about what is a pool, i mean for now. We will need to have different pools to dissociate the usage.
So, a pool to handle all redhat VM, one for fedora people, another for specific user and so on.

  • Current ETA:

I just start create smart pool. If you see the same pool more than once don't worry about that.
it's just lynks which screwed it up when i did my tries.

I'll need a good web access to go forward, lynx is very limited to work on ovirt webUI.

Cobbler

Cobbler is the way where ovirt handles OS provisioning and profile management. We'll need to prevent from people question such as :
Could we request a specific profile for our vm or it's just up to us ?

Authentication

We'll also need to bind it to FAS

</DRAFT>