[Pkg-opennebula-devel] Packaging opennebula 3.6 in parallel with git-buildpackage

[Martin Steigerwald]

Am Dienstag, 31. Juli 2012 schrieb Damien Raude-Morvan:
> Hi Martin (and Guido),

Hi Damien, hi everyone,

> Le 31/07/2012 09:39, Martin Steigerwald a écrit :
> > Am Montag, 30. Juli 2012 schrieb Guido Günther:
> >> In order to avoid branch renaming I'd use:
> >> 
> >> debian/experimental -> experimental
> >> upstream/experimental -> upstream-experimental
> >> 
> >> instead for now. I'd do this by starting with:
> >> 
> >> git branch experimental master
> >> git branch upstream-experimental upstream
> >> 
> >> and then put the branch names into debian/gbp.conf.
> > 
> > I will choose this approach for now, unless I read some objection here.
> > If someone wants to veto, please do soon. I'd like to start this after
> > noon, so say in 3-4 hours.
> 
> Plan proposed by Guido is perfectly fine ! I remember using something
> like that for another package than OpenNebula.
> 
> Don't hesitate to push your changes to git.debian.org and describe
> branches used in :
> http://wiki.debian.org/Teams/pkg-opennebula/GitWorkflow

[x] done

I have some OpenNebula 3.6 snapshot packages somewhat working. Commit 
b3b72344ae09b4b32e165c2f5428836d78ad4c03 from experimental branch.

The changelog just auto-generated for now and needs quite some editing before 
first upload.

oned seems to be running and sunstone as well, but there are issues, like:

oneadmin at cloudmaster:~$ onehost list
[HostPoolInfo] User couldn't be authenticated, aborting call.

I bet there might be some files missing. Or I misconfigured something, but I 
think it worked with 3.4.


I can login to sunstone however. "Historical monitoring information" just 
display progress circles. It never displayed anything for me with previous 
package versions (3.2 / 3.4).


And there is other stuff to look at. See debian/TODO file I added TODOs for 3.6 
in a separate section.

opennebula-node is untested yet. But I think that auth issue is more 
important.


I will work through the issues one at a time and test stuff. Any hints that 
help me to get up to speed greatly appreciated. As well as any review. This is 
my first time I am working on complex packages like this.


Database needed to be upgraded. Whidch seemed to work fine:

oneadmin at cloudmaster:~$ onedb upgrade -s one.db
Sqlite database backup stored in /var/lib/one/one.db.bck
Use 'onedb restore' or copy the file back to restore the DB.
Database migrated from 3.4.1 to 3.6.0 (OpenNebula 3.6.0) by onedb command.

Thanks,
-- 
Martin Steigerwald - teamix GmbH - http://www.teamix.de
gpg: 19E3 8D42 896F D004 08AC A0CA 1E10 C593 0399 AE90