Development

This page will be used to teach us what the ovirt developers use to do nice things in the git builds. Things that are important but quickly forgotten because you only see it in IRC.


[edit]

update database after upgrade

When updating the fresh build rpms from the latest and greatest code (see: http://ovirt.org/build-instructions-rawhide.html) for the already installed ovirt manager. You should upgrade your database for possible changes. To do this type this on your ovirt server installation, as root(#): 

# cd /usr/share/ovirt-server
# export RAILS_ENV=production
# rake db:migrate

This should update your database with any changes since your last update.

[edit]

Recreate postgres database when something went wrong

Do you have the feeling that a node should be available but isn't? You can recreate the ovirt database following the commands below, as root(#): 

# /etc/init.d/ovirt-db-o-matic stop
# su postgres
bash-ver$ psql
postgres=# drop database ovirt;
postgres=# create database ovirt;
postgres=# \q
bash-ver$ exit
# cd /usr/share/ovirt-server
# export RAILS_ENV=production
# rake db:migrate
# cd scripts
# ./grant_admin_privileges ovirtadmin

The ovirt-server database is now empty and you should reboot your ovirt server. Then boot up some nodes and test again.

[edit]

Ok i wanna make a patch how can i send it to the list?

To send a patch you will have to create one with git. I had a small crash course so wil explain it below.

follow the build instruction for rawhide. When it is done change to the directory where you wanna change something, I created a small patch for the save settings button. Note that you should have a .gitconfig file in your home directory. Some useful example settings are: 

[user]
       email = you@you.com
       name = Your Name
[sendemail]
       smtpserver = your-server.com
[alias]
       st = status
       co = checkout
       ci = commit
       br = branch
[color]
       diff = auto
       status = auto
       branch = auto

Assuming that is set: 

# cd ovirt/server
# git branch patch-for-popup
# git checkout patch-for-popup
# vi src/app/views/vm/edit.rhtml
# git rebase next
# git add src/app/views/vm/_list.rhtml
# git commit (enter a small description on the first line and change the email adres)
# git format-patch -s HEAD~1
Send the email using git, or attach the created file to a regular email to the list:
# git send-email --to ovirt-devel@redhat.com <patch>
Retrieved from "http://www.ovirt.org/page/Development"
MediaWiki