From taget at linux.vnet.ibm.com  Mon Jul  2 02:34:44 2012
From: taget at linux.vnet.ibm.com (Eli Qiao)
Date: Mon, 02 Jul 2012 10:34:44 +0800
Subject: [node-devel] Failed build node on F16 and F15
In-Reply-To: <CAGi==UWRDN7n2XcXJb=7s52Z1jKWLt2d5hKcPudcvedBX+6+kA@mail.gmail.com>
References: <4FED64D3.4060401@linux.vnet.ibm.com>
	<1340959338.2280.4.camel@fdeutsch-laptop.local>
	<CAGi==UWRDN7n2XcXJb=7s52Z1jKWLt2d5hKcPudcvedBX+6+kA@mail.gmail.com>
Message-ID: <4FF108C4.6070503@linux.vnet.ibm.com>

? 2012?06?29? 17:57, Alan Pevec ??:
> On Fri, Jun 29, 2012 at 10:42 AM, Fabian Deutsch<fabiand at redhat.com>  wrote:
>> >  Am Freitag, den 29.06.2012, 16:18 +0800 schrieb Eli Qiao:
>>> >>  I think the {_unitdir} are difference between F17 and F16&F15 , so I
>>> >>  give a ugly fix in ovirt-node.spec.in:
>>> >>
>>> >>  %define is_f17 %(test "0%{?fedora}" == "017"&&  echo 1 || echo 0)
>>> >>  %if %is_f17
>>> >>  %else
>>> >>  %define _unitdir /usr/lib/systemd/system
>>> >>  %endif
>>> >>
>>> >>  I can build it successfully , but I am not sure it is correct.
>> >
>> >  That sounds reasonable, I wonder why systemd-units (which AFAIK defines
>> >  _unitdir) isn't providing a different path on F15/F16.
on f17 and f16,f15 , the_unitdir has difference path

[root at ovirt ~]# rpm --showrc | grep unit
-14: _unitdir /lib/systemd/system
[root at ovirt ~]# uname -a
Linux ovirt 3.0.0-1.fc16.x86_64 #1 SMP Fri Jul 22 16:09:29 UTC 2011 
x86_64 x86_64 x86_64 GNU/Linux
------------------------------------------------
[root at ovirt-node ~]# rpm --showrc | grep unit
-14: _unitdir /lib/systemd/system
[root at ovirt-node ~]# uname -a
Linux ovirt-node 2.6.38.6-26.rc1.fc15.i686.PAE #1 SMP Mon May 9 20:36:50 
UTC 2011 i686 i686 i386 GNU/Linux
------------------------------------------------
[root at ovirt ~]# rpm --showrc | grep unit
-14: _unitdir /usr/lib/systemd/system
[root at ovirt ~]# uname -a
Linux ovirt 3.3.4-5.fc17.x86_64 #1 SMP Mon May 7 17:29:34 UTC 2012 
x86_64 x86_64 x86_64 GNU/Linux


-- 
Thanks. Best regards. --Eli Qiao



From taget at linux.vnet.ibm.com  Mon Jul  2 02:38:22 2012
From: taget at linux.vnet.ibm.com (Eli Qiao)
Date: Mon, 02 Jul 2012 10:38:22 +0800
Subject: [node-devel] Failed build node on F16 and F15
In-Reply-To: <CAGi==UWRDN7n2XcXJb=7s52Z1jKWLt2d5hKcPudcvedBX+6+kA@mail.gmail.com>
References: <4FED64D3.4060401@linux.vnet.ibm.com>
	<1340959338.2280.4.camel@fdeutsch-laptop.local>
	<CAGi==UWRDN7n2XcXJb=7s52Z1jKWLt2d5hKcPudcvedBX+6+kA@mail.gmail.com>
Message-ID: <4FF1099E.8000201@linux.vnet.ibm.com>

? 2012?06?29? 17:57, Alan Pevec ??:
> F17 has that /usr-move feature, where all moved under /usr, it is
> different on F16:
> $ rpm -qf /etc/rpm/macros.systemd
> systemd-units-37-25.fc16.x86_64
> $ cat /etc/rpm/macros.systemd
> %_unitdir /lib/systemd/system
>
> The problem for F16 is in services/Makefile.am:
> systemunitdir=$(prefix)/lib/systemd/system
>
> so ovirt *.services end up in %{buildroot}/usr/lib/systemd/system/  on
> both F16 and F17.
> F16 systemd Makefile has: systemunitdir=$(rootdir)/lib/systemd/system
> so you'd need some conditional in ovirt makefile if you want to
> support building on both F16/17.
>
> Cheers,
> Alan
>
OK ,thanks Alan

-- 
Thanks. Best regards. --Eli Qiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120702/927de073/attachment.html>

From wenyi at linux.vnet.ibm.com  Tue Jul  3 06:21:54 2012
From: wenyi at linux.vnet.ibm.com (Wenyi Gao)
Date: Tue, 03 Jul 2012 14:21:54 +0800
Subject: [node-devel] Failed to build ovirt-node on Fedora 17
Message-ID: <4FF28F82.5080501@linux.vnet.ibm.com>

Hi guys,

I ran autobuild.sh to build ovirt-node on Fedora 17 with the latest 
release pykickstart-1.99.13 and ran into following problems:


......

nstalling: vdsm                         ##################### [482/485]
   Installing: vdsm-reg                     ##################### [483/485]
   Installing: python-libguestfs            ##################### [484/485]
   Installing: libguestfs-tools-c           ##################### [485/485]
   Installing: systemtap-runtime            ##################### [486/485]
E: Dracut module "ovirtnode" cannot be found.
E: Dracut module "ovirtnode" cannot be found.

Removing password for user root.
passwd: Success
Note: Forwarding request to 'systemctl enable auditd.service'.
Note: Forwarding request to 'systemctl enable ntpd.service'.
ln -s '/usr/lib/systemd/system/ntpd.service' 
'/etc/systemd/system/multi-user.target.wants/ntpd.service'
Note: Forwarding request to 'systemctl enable ntpdate.service'.
ln -s '/usr/lib/systemd/system/ntpdate.service' 
'/etc/systemd/system/multi-user.target.wants/ntpdate.service'
Note: Forwarding request to 'systemctl enable iptables.service'.
Note: Forwarding request to 'systemctl enable rsyslog.service'.
Note: Forwarding request to 'systemctl enable multipathd.service'.
Note: Forwarding request to 'systemctl enable snmpd.service'.
ln -s '/usr/lib/systemd/system/snmpd.service' 
'/etc/systemd/system/multi-user.target.wants/snmpd.service'
Note: Forwarding request to 'systemctl enable ovirt-early.service'.
ln -s '/usr/lib/systemd/system/ovirt-early.service' 
'/etc/systemd/system/multi-user.target.wants/ovirt-early.service'
Note: Forwarding request to 'systemctl enable ovirt.service'.
ln -s '/usr/lib/systemd/system/ovirt.service' 
'/etc/systemd/system/multi-user.target.wants/ovirt.service'
Note: Forwarding request to 'systemctl enable ovirt-post.service'.
ln -s '/usr/lib/systemd/system/ovirt-post.service' 
'/etc/systemd/system/multi-user.target.wants/ovirt-post.service'
Note: Forwarding request to 'systemctl enable ovirt-cim.service'.
ln -s '/usr/lib/systemd/system/ovirt-cim.service' 
'/etc/systemd/system/multi-user.target.wants/ovirt-cim.service'
Note: Forwarding request to 'systemctl enable collectd.service'.
ln -s '/usr/lib/systemd/system/collectd.service' 
'/etc/systemd/system/multi-user.target.wants/collectd.service'
Note: Forwarding request to 'systemctl enable libvirtd.service'.
error reading information on service cgconfig: No such file or directory
umount: /tmp/lorax.imgutils.D_C5VP: target is busy.
         (In some cases useful info about processes that use
          the device is found by lsof(8) or fuser(1))
losetup: /dev/loop2: detach failed: Device or resource busy
Traceback (most recent call last):
   File "/sbin/mkefiboot", line 139, in <module>
     opt.diskname)
   File "/sbin/mkefiboot", line 38, in mkmacboot
     mkhfsimg(None, outfile, label=label, graft=graft)
   File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line 
310, in mkhfsimg
     mkfsargs=["-v", label], graft=graft)
   File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line 
293, in mkfsimage
     do_grafts(graft, mnt, preserve)
   File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line 
206, in __exit__
     umount(self.mnt)
   File "/usr/lib/python2.7/site-packages/pylorax/imgutils.py", line 
120, in umount
     os.rmdir(mnt)
OSError: [Errno 16] Device or resource busy: '/tmp/lorax.imgutils.D_C5VP'
Starting Kickstart Post
Creating shadow files
Lock root account
Locking password for user root.
passwd: Success
Saved 1 file(s)
Saved 1 file(s)
Saved 1 file(s)
patching file sosreport.py
patching file plugins/general.py
Listing /usr/lib/python2.7/site-packages/sos ...
Listing /usr/lib/python2.7/site-packages/sos/plugins ...
Compiling /usr/lib/python2.7/site-packages/sos/plugins/general.py ...
Compiling /usr/lib/python2.7/site-packages/sos/sosreport.py ...
Saved 1 file(s)
Saved 1 file(s)
Saved 2 file(s)
Configuring IPTables
Listing /usr/share/virt-manager ...
Listing /usr/share/virt-manager/virtManager ...
Listing /usr/share/virt-manager/virtManagerTui ...
Listing /usr/share/virt-manager/virtManagerTui/importblacklist ...
Configuring SELinux
Compiling targeted ovirt module
/usr/bin/checkmodule:  loading policy configuration from tmp/ovirt.tmp
/usr/bin/checkmodule:  policy configuration loaded
/usr/bin/checkmodule:  writing binary representation (version 15) to 
tmp/ovirt.mod
Creating targeted ovirt.pp policy package
rm tmp/ovirt.mod tmp/ovirt.mod.fc
Attempting to install module 'ovirt.pp':
Ok: return value of 0.
Committing changes:
Ok: transaction number 0.
Fixing boot menu
Error creating Live CD : Failed to execute %post script with 
'image-minimizer' : No such file or directory
lazy umount succeeded on 
/ovirt-cache/node-creator-x86_64-tmp/imgcreate-khsGd7/install_root//var/cache/yum




Does anyone experience the problem? Thanks.

Best Regards
Wenyi





From fabiand at redhat.com  Tue Jul  3 07:13:27 2012
From: fabiand at redhat.com (Fabian Deutsch)
Date: Tue, 03 Jul 2012 09:13:27 +0200
Subject: [node-devel] Failed to build ovirt-node on Fedora 17
In-Reply-To: <4FF28F82.5080501@linux.vnet.ibm.com>
References: <4FF28F82.5080501@linux.vnet.ibm.com>
Message-ID: <1341299607.2403.0.camel@fdeutsch-laptop.local>

Am Dienstag, den 03.07.2012, 14:21 +0800 schrieb Wenyi Gao:
> Fixing boot menu
> Error creating Live CD : Failed to execute %post script with 
> 'image-minimizer' : No such file or directory
> lazy umount succeeded on 
> /ovirt-cache/node-creator-x86_64-tmp/imgcreate-khsGd7/install_root//var/cache/yum
> 
> 
> 
> 
> Does anyone experience the problem? Thanks. 

Hey Wenyi,

seems to be that the appliance-tools-minimizer package is missing.

Greetings
fabian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120703/e654a66a/attachment.sig>

From wenyi at linux.vnet.ibm.com  Tue Jul  3 07:36:18 2012
From: wenyi at linux.vnet.ibm.com (Wenyi Gao)
Date: Tue, 03 Jul 2012 15:36:18 +0800
Subject: [node-devel] Failed to build ovirt-node on Fedora 17
In-Reply-To: <1341299607.2403.0.camel@fdeutsch-laptop.local>
References: <4FF28F82.5080501@linux.vnet.ibm.com>
	<1341299607.2403.0.camel@fdeutsch-laptop.local>
Message-ID: <4FF2A0F2.70905@linux.vnet.ibm.com>

On 2012-07-03 15:13, Fabian Deutsch wrote:
> Am Dienstag, den 03.07.2012, 14:21 +0800 schrieb Wenyi Gao:
>> Fixing boot menu
>> Error creating Live CD : Failed to execute %post script with
>> 'image-minimizer' : No such file or directory
>> lazy umount succeeded on
>> /ovirt-cache/node-creator-x86_64-tmp/imgcreate-khsGd7/install_root//var/cache/yum
>>
>>
>>
>>
>> Does anyone experience the problem? Thanks.
> Hey Wenyi,
>
> seems to be that the appliance-tools-minimizer package is missing.
>
> Greetings
> fabian
Hello Fabian,

Yes, I installed the package and built successfully. Many thanks.



From mburns at redhat.com  Tue Jul  3 13:37:19 2012
From: mburns at redhat.com (Mike Burns)
Date: Tue, 03 Jul 2012 09:37:19 -0400
Subject: [node-devel] oVirt Node Weekly Meeting minutes -- 2012-07-03
Message-ID: <1341322639.3574.2.camel@beelzebub.mburnsfire.net>

Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-03-13.02.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-03-13.02.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-03-13.02.log.html


=================================
#ovirt: ovirt-node weekly meeting
=================================


Meeting started by mburns at 13:02:06 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-03-13.02.log.html
.



Meeting summary
---------------
* roll call and agenda  (mburns, 13:02:34)

* Action Item Review  (mburns, 13:05:53)
  * LINK:
    http://ovirt.org/meetings/ovirt/2012/ovirt.2012-06-26-13.00.html
    (mburns, 13:06:01)
  * 2 bz's filed for stateless  (mburns, 13:06:16)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=837323   (mburns,
    13:06:27)
  * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=837322   (mburns,
    13:06:56)
  * i double checked vdsm version and we're pulling latest one in, but
    there are still registration problems  (mburns, 13:07:25)
  * ACTION: mburns and dougsland to debug registration issue  (mburns,
    13:07:51)
  * bz to be filed today  (mburns, 13:08:02)
  * bz's for 2.4.1 moved to modified as appropriate by fabiand  (mburns,
    13:08:26)
  * LINK: http://gerrit.ovirt.org/#/c/5600/   (mburns, 13:09:36)
  * vdsm patch for registration  (mburns, 13:09:43)
  * ACTION: jboggs to follow up on 832163  (mburns, 13:11:39)
  * ACTION: mburns to build vdsm with patch 5600 and rebuild ovirt-node
    (mburns, 13:11:57)

* release status  (mburns, 13:12:58)
  * LINK: http://goo.gl/DqyqZ   (mburns, 13:13:26)
  * all modified except the 1 that jboggs is following up on  (mburns,
    13:13:54)
  * we are currently blocked on a registration issue which mburns is
    investigating with vdsm team  (mburns, 13:14:29)
  * pending patch backlog:  all pep8 related patches other than 1 for bz
    832163  (mburns, 13:15:22)
  * all others merged  (mburns, 13:15:32)
  * target release date is July 9  (mburns, 13:16:08)
  * ACTION: jboggs to double check that uefi patches are included
    (mburns, 13:18:32)

* Other Topics  (mburns, 13:18:47)
  * Automation:  the basics are working, I'm doing nightly automated
    installations and a login into the tui  (mburns, 13:21:04)
  * ACTION: fabiand to follow up on getting node tests repo into gerrit
    (mburns, 13:22:27)
  * jboggs finishing manifests now, should be on track to demo next week
    (mburns, 13:23:44)

Meeting ended at 13:25:54 UTC.




Action Items
------------
* mburns and dougsland to debug registration issue
* jboggs to follow up on 832163
* mburns to build vdsm with patch 5600 and rebuild ovirt-node
* jboggs to double check that uefi patches are included
* fabiand to follow up on getting node tests repo into gerrit




Action Items, by person
-----------------------
* dougsland
  * mburns and dougsland to debug registration issue
* fabiand
  * fabiand to follow up on getting node tests repo into gerrit
* jboggs
  * jboggs to follow up on 832163
  * jboggs to double check that uefi patches are included
* mburns
  * mburns and dougsland to debug registration issue
  * mburns to build vdsm with patch 5600 and rebuild ovirt-node
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* mburns (56)
* fabiand (8)
* jboggs (7)
* dougsland (5)
* ovirtbot (4)
* READ10 (2)
* pmyers (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot



From fabiand at redhat.com  Wed Jul  4 10:48:14 2012
From: fabiand at redhat.com (Fabian Deutsch)
Date: Wed, 04 Jul 2012 12:48:14 +0200
Subject: [node-devel] Update on Automated Continous Integration Testing
Message-ID: <1341398894.2376.20.camel@fdeutsch-laptop.local>

Hey,

currently CI tests are run nightly on the master branch (with sometimes
additional patches) and the results are posted to the node-patches ml.

The tests (currently the basic_tui testsuite) are run internally but the
testcases itself are now kept in oVirt's gerrit [1, 2].

Some initial ideas of how to improve and what testcases to add to the
testsuites are summarized in the wiki [3].
The testcases outlined there are just the basics, if you got a special
testcase you want to cover, you are welcome to contribute a testcase and
get it reviewed.
This way you will get an nightly automated testing of your special
testcase (which should be relevant to oVirt Node) "for free" :)

It is even possible to do TUI testing by writing appropriate testcases
[4] and using the provided common.input [5] python library (which builds
upon uinput). There is also an example provided: [6]

There is still work to do: The wiki pages need to be reorganized and
cleaned up a bit. Additionall testcases can be written (like for the
TUI, or TUI installation), ?

Greetings
fabian

--
[1] http://gerrit.ovirt.org/gitweb?p=ovirt-node-tests.git
[2] http://gerrit.ovirt.org/#/q/status:open+project:ovirt-node-tests,n,z
[3] http://ovirt.org/wiki/Node_Testing#Basic_Testcases
[4] http://gerrit.ovirt.org/gitweb?p=ovirt-node-tests.git;a=blob;
f=docs/Writing_TUI_Tests.rst;hb=HEAD
[5] http://gerrit.ovirt.org/gitweb?p=ovirt-node-tests.git;a=tree;
f=libs/common;hb=HEAD
[6] http://gerrit.ovirt.org/gitweb?p=ovirt-node-tests.git;a=blob;
f=tcs/uinput_login_as_admin.py;hb=HEAD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120704/d6e4879e/attachment.sig>

From fabiand at redhat.com  Thu Jul  5 15:46:11 2012
From: fabiand at redhat.com (Fabian Deutsch)
Date: Thu, 05 Jul 2012 17:46:11 +0200
Subject: [node-devel] Running doctests on Node and improving them
Message-ID: <1341503171.4948.19.camel@fdeutsch-laptop.local>

Hey,

some of our "backing libraries" like ovirtfunctions.py contain doctests.
Those are small for documenting the usage of the function but can also
be used for testing [1].
As pointed out on the wiki [2] thos tests can't be run at dev. time,
because they partially rely on runtime functionality.

Just a minute ago I tested to run the doctest on ovirtfunctions.py on a
running node:
1. Installed a node
2. Dropped to console
3. ran::
  cd /usr/lib/python2.7/site-packages/ovirtnode
  python -m doctest ovirtfunctions.py

This failed, but is actually expected - as no work has gone into
enabling this feature.

There are two things we should do:
1. Fix the error that prevented running the doctest (smome indentation 
   problem!?)
2. Add doctests to python functions to cover more functions

doctests are a fine granular piece in our CI testing effort - but are
easy to create.
One question is if we should also add real unit tests covering wider
parts?
I'd rather go with higher-level testcases (e.g. TUI tests [3]), which
should cover the core functionality.

That was an update on how to run doctests - but don't hesitate to join
in to make Node more stable.

Greetings
fabian

--
[1] http://docs.python.org/library/doctest.html
[2] http://ovirt.org/wiki/Node_Testing
[3] http://gerrit.ovirt.org/gitweb?p=ovirt-node-tests.git;a=blob;
f=docs/Writing_TUI_Tests.rst;hb=HEAD
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120705/a2a8b13e/attachment.sig>

From mburns at redhat.com  Thu Jul  5 15:58:33 2012
From: mburns at redhat.com (Mike Burns)
Date: Thu, 05 Jul 2012 11:58:33 -0400
Subject: [node-devel] Running doctests on Node and improving them
In-Reply-To: <1341503171.4948.19.camel@fdeutsch-laptop.local>
References: <1341503171.4948.19.camel@fdeutsch-laptop.local>
Message-ID: <1341503913.10141.10.camel@mburns-laptop>

On Thu, 2012-07-05 at 17:46 +0200, Fabian Deutsch wrote:
> Hey,
> 
> some of our "backing libraries" like ovirtfunctions.py contain doctests.
> Those are small for documenting the usage of the function but can also
> be used for testing [1].
> As pointed out on the wiki [2] thos tests can't be run at dev. time,
> because they partially rely on runtime functionality.
> 
> Just a minute ago I tested to run the doctest on ovirtfunctions.py on a
> running node:
> 1. Installed a node
> 2. Dropped to console
> 3. ran::
>   cd /usr/lib/python2.7/site-packages/ovirtnode
>   python -m doctest ovirtfunctions.py
> 
> This failed, but is actually expected - as no work has gone into
> enabling this feature.
> 
> There are two things we should do:
> 1. Fix the error that prevented running the doctest (smome indentation 
>    problem!?)

Please file a bz (and provide a patch ;-) )

> 2. Add doctests to python functions to cover more functions

Please file bz's with "RFE: " in the summary for this.  This is a longer
term goal
> 
> doctests are a fine granular piece in our CI testing effort - but are
> easy to create.
> One question is if we should also add real unit tests covering wider
> parts?
> I'd rather go with higher-level testcases (e.g. TUI tests [3]), which
> should cover the core functionality.

Agreed that we should lean more toward the testcases to cover our
testing, but having unit tests is absolutely useful as well.  I'd stick
to simple unit tests with doctest and have a higher level test case that
will run the doctest stuff as well.

Mike

> 
> That was an update on how to run doctests - but don't hesitate to join
> in to make Node more stable.
> 
> Greetings
> fabian
> 
> --
> [1] http://docs.python.org/library/doctest.html
> [2] http://ovirt.org/wiki/Node_Testing
> [3] http://gerrit.ovirt.org/gitweb?p=ovirt-node-tests.git;a=blob;
> f=docs/Writing_TUI_Tests.rst;hb=HEAD
> _______________________________________________
> node-devel mailing list
> node-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/node-devel




From fabiand at redhat.com  Thu Jul  5 16:38:21 2012
From: fabiand at redhat.com (Fabian Deutsch)
Date: Thu, 05 Jul 2012 18:38:21 +0200
Subject: [node-devel] Running doctests on Node and improving them
In-Reply-To: <1341503913.10141.10.camel@mburns-laptop>
References: <1341503171.4948.19.camel@fdeutsch-laptop.local>
	<1341503913.10141.10.camel@mburns-laptop>
Message-ID: <1341506301.4948.23.camel@fdeutsch-laptop.local>

Am Donnerstag, den 05.07.2012, 11:58 -0400 schrieb Mike Burns:
> > There are two things we should do:
> > 1. Fix the error that prevented running the doctest (smome
> indentation 
> >    problem!?)
> 
> Please file a bz (and provide a patch ;-) )

It wasn't much:
http://gerrit.ovirt.org/5985

But one interesting thing: 
1. doctests on .pyc files fail
2. python -m doctest to_the_same_prefix_of_file_but_with_py_suffix.py
   works _ even if the file doesn't exist! (Asking this upstream)

> > 2. Add doctests to python functions to cover more functions
> 
> Please file bz's with "RFE: " in the summary for this.  This is a
> longer
> term goal

Yes, good point to track this.

> > 
> > doctests are a fine granular piece in our CI testing effort - but
> are
> > easy to create.
> > One question is if we should also add real unit tests covering wider
> > parts?
> > I'd rather go with higher-level testcases (e.g. TUI tests [3]),
> which
> > should cover the core functionality.
> 
> Agreed that we should lean more toward the testcases to cover our
> testing, but having unit tests is absolutely useful as well.  I'd
> stick
> to simple unit tests with doctest and have a higher level test case
> that
> will run the doctest stuff as well. 

Right. Unit tests are also important to achieve the goal of a stable
Node.

Greetings
fabian

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120705/b2d698ba/attachment.sig>

From taget at linux.vnet.ibm.com  Mon Jul  9 08:43:44 2012
From: taget at linux.vnet.ibm.com (Eli Qiao)
Date: Mon, 09 Jul 2012 16:43:44 +0800
Subject: [node-devel] install error and debug method
In-Reply-To: <1341503171.4948.19.camel@fdeutsch-laptop.local>
References: <1341503171.4948.19.camel@fdeutsch-laptop.local>
Message-ID: <4FFA99C0.6040801@linux.vnet.ibm.com>


hi all:

    * I failed to install a version of build (I built it myself) base on
      F17, it show nothing just tell me to log as admin ,but I didn't
      set up a password for admin and root. what the passwd is ?
    * And also , I have some question about how to debug the ovirt-node,
      would someone kindly give me a hand ?
    * Can I ask that what should I do if I want to set a password in the
      bootparameters such rootpw=XXX

what XXX like ?

I generate the passwd by doing this :
  perl -e 'print crypt("123",q($1$IPPBXADM)),"\n"'
$1$IPPBXADM$UwX5u7LVJoJ/EJfG4d8HC1

but when I type 123 , it's shows I am input a wrong password , what 
encryption does node use ? md5 or sha1 ?




-- 
Thanks. Best regards. --Eli Qiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120709/462d6422/attachment.html>

From fabiand at redhat.com  Mon Jul  9 08:49:40 2012
From: fabiand at redhat.com (Fabian Deutsch)
Date: Mon, 09 Jul 2012 10:49:40 +0200
Subject: [node-devel] install error and debug method
In-Reply-To: <4FFA99C0.6040801@linux.vnet.ibm.com>
References: <1341503171.4948.19.camel@fdeutsch-laptop.local>
	<4FFA99C0.6040801@linux.vnet.ibm.com>
Message-ID: <1341823780.2332.9.camel@fdeutsch-laptop.local>

Hey,

Am Montag, den 09.07.2012, 16:43 +0800 schrieb Eli Qiao:
>       * I failed to install a version of build (I built it myself)
>         base on F17, it show nothing just tell me to log as admin ,but
>         I didn't set up a password for admin and root. what the passwd
>         is ?

If no password is given at an auto-ionstall the the admin and root
accounts will be disabled. You need to provide an admin/rootpw at
install time (via kargs, see below)-

>       * And also , I have some question about how to debug the
>         ovirt-node, would someone kindly give me a hand ?

Most ovirt node specific log messages go to /var/log/ovirt.log .
But the base components log to their predefined locations.
Might I ask what you want to debug?

>       * Can I ask that what should I do if I want to set a password in
>         the bootparameters such rootpw=XXX 
> what XXX like ?
> 
> I generate the passwd by doing this :
>  perl -e 'print crypt("123",q($1$IPPBXADM)),"\n"'
> $1$IPPBXADM$UwX5u7LVJoJ/EJfG4d8HC1
> 
> but when I type 123 , it's shows I am input a wrong password , what
> encryption does node use ? md5 or sha1 ?

I just know that you can use the openssl passwd command to generated a
valid password hash, e.g.:

$ openssl passwd -salt foo bar
foXrpAKGo3142

This hash can be used as a karg: adminpw=foXrpAKGo3142

Greetings
fabian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120709/d1df69a1/attachment.sig>

From mburns at redhat.com  Mon Jul  9 10:24:25 2012
From: mburns at redhat.com (Mike Burns)
Date: Mon, 09 Jul 2012 06:24:25 -0400
Subject: [node-devel] install error and debug method
In-Reply-To: <1341823780.2332.9.camel@fdeutsch-laptop.local>
References: <1341503171.4948.19.camel@fdeutsch-laptop.local>
	<4FFA99C0.6040801@linux.vnet.ibm.com>
	<1341823780.2332.9.camel@fdeutsch-laptop.local>
Message-ID: <1341829465.26430.3.camel@beelzebub.mburnsfire.net>

On Mon, 2012-07-09 at 10:49 +0200, Fabian Deutsch wrote:
> Hey,
> 
> Am Montag, den 09.07.2012, 16:43 +0800 schrieb Eli Qiao:
> >       * I failed to install a version of build (I built it myself)
> >         base on F17, it show nothing just tell me to log as admin ,but
> >         I didn't set up a password for admin and root. what the passwd
> >         is ?
> 
> If no password is given at an auto-ionstall the the admin and root
> accounts will be disabled. You need to provide an admin/rootpw at
> install time (via kargs, see below)-

This sounds like a problem with the TUI loading, but without more
information, I can't say for sure.  

Is this the first boot that you've done?  Did the TUI ever load at all?
What changes did you make before doing the build?  

> 
> >       * And also , I have some question about how to debug the
> >         ovirt-node, would someone kindly give me a hand ?
> 
> Most ovirt node specific log messages go to /var/log/ovirt.log .
> But the base components log to their predefined locations.
> Might I ask what you want to debug?
> 
> >       * Can I ask that what should I do if I want to set a password in
> >         the bootparameters such rootpw=XXX 
> > what XXX like ?
> > 
> > I generate the passwd by doing this :
> >  perl -e 'print crypt("123",q($1$IPPBXADM)),"\n"'
> > $1$IPPBXADM$UwX5u7LVJoJ/EJfG4d8HC1
> > 
> > but when I type 123 , it's shows I am input a wrong password , what
> > encryption does node use ? md5 or sha1 ?
> 
> I just know that you can use the openssl passwd command to generated a
> valid password hash, e.g.:
> 
> $ openssl passwd -salt foo bar
> foXrpAKGo3142
> 
> This hash can be used as a karg: adminpw=foXrpAKGo3142

Better to use openssl passwd -1 and then enter and verify the password.

$ openssl passwd -1
Password: 
Verifying - Password: 
$1$9RXa7lLR$RV46M2aZyxadZQudooryH.

To set the root password, you use:
rootpw=$1$9RXa7lLR$RV46M2aZyxadZQudooryH.

Mike

> 
> Greetings
> fabian
> _______________________________________________
> node-devel mailing list
> node-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/node-devel




From taget at linux.vnet.ibm.com  Tue Jul 10 01:47:33 2012
From: taget at linux.vnet.ibm.com (Eli Qiao)
Date: Tue, 10 Jul 2012 09:47:33 +0800
Subject: [node-devel] install error and debug method
In-Reply-To: <1341823780.2332.9.camel@fdeutsch-laptop.local>
References: <1341503171.4948.19.camel@fdeutsch-laptop.local>
	<4FFA99C0.6040801@linux.vnet.ibm.com>
	<1341823780.2332.9.camel@fdeutsch-laptop.local>
Message-ID: <4FFB89B5.9010804@linux.vnet.ibm.com>

? 2012?07?09? 16:49, Fabian Deutsch ??:
> Most ovirt node specific log messages go to /var/log/ovirt.log .
> But the base components log to their predefined locations.
> Might I ask what you want to debug?
I 'd like to add a boot parameters such as multipath_enabled, I am not 
very clear about how to process the bootparams in function 
start_ovirt_early ().
-- 
Thanks. Best regards. --Eli Qiao



From taget at linux.vnet.ibm.com  Tue Jul 10 01:49:07 2012
From: taget at linux.vnet.ibm.com (Eli Qiao)
Date: Tue, 10 Jul 2012 09:49:07 +0800
Subject: [node-devel] install error and debug method
In-Reply-To: <1341829465.26430.3.camel@beelzebub.mburnsfire.net>
References: <1341503171.4948.19.camel@fdeutsch-laptop.local>
	<4FFA99C0.6040801@linux.vnet.ibm.com>
	<1341823780.2332.9.camel@fdeutsch-laptop.local>
	<1341829465.26430.3.camel@beelzebub.mburnsfire.net>
Message-ID: <4FFB8A13.2000504@linux.vnet.ibm.com>

? 2012?07?09? 18:24, Mike Burns ??:
> On Mon, 2012-07-09 at 10:49 +0200, Fabian Deutsch wrote:
>> Hey,
>>
>> Am Montag, den 09.07.2012, 16:43 +0800 schrieb Eli Qiao:
>>>        * I failed to install a version of build (I built it myself)
>>>          base on F17, it show nothing just tell me to log as admin ,but
>>>          I didn't set up a password for admin and root. what the passwd
>>>          is ?
>> If no password is given at an auto-ionstall the the admin and root
>> accounts will be disabled. You need to provide an admin/rootpw at
>> install time (via kargs, see below)-
> This sounds like a problem with the TUI loading, but without more
> information, I can't say for sure.
>
> Is this the first boot that you've done?  Did the TUI ever load at all?
> What changes did you make before doing the build?
>
yes , it's first boot, the TUI didn't loading
>>>        * And also , I have some question about how to debug the
>>>          ovirt-node, would someone kindly give me a hand ?
>> Most ovirt node specific log messages go to /var/log/ovirt.log .
>> But the base components log to their predefined locations.
>> Might I ask what you want to debug?
>>
>>>        * Can I ask that what should I do if I want to set a password in
>>>          the bootparameters such rootpw=XXX
>>> what XXX like ?
>>>
>>> I generate the passwd by doing this :
>>>   perl -e 'print crypt("123",q($1$IPPBXADM)),"\n"'
>>> $1$IPPBXADM$UwX5u7LVJoJ/EJfG4d8HC1
>>>
>>> but when I type 123 , it's shows I am input a wrong password , what
>>> encryption does node use ? md5 or sha1 ?
>> I just know that you can use the openssl passwd command to generated a
>> valid password hash, e.g.:
>>
>> $ openssl passwd -salt foo bar
>> foXrpAKGo3142
>>
>> This hash can be used as a karg: adminpw=foXrpAKGo3142
> Better to use openssl passwd -1 and then enter and verify the password.
>
> $ openssl passwd -1
> Password:
> Verifying - Password:
> $1$9RXa7lLR$RV46M2aZyxadZQudooryH.
>
> To set the root password, you use:
> rootpw=$1$9RXa7lLR$RV46M2aZyxadZQudooryH.
>
> Mike
>
thanks very much Mike.
>> Greetings
>> fabian
>> _______________________________________________
>> node-devel mailing list
>> node-devel at ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/node-devel
>


-- 
Thanks. Best regards. --Eli Qiao



From taget at linux.vnet.ibm.com  Tue Jul 10 02:34:58 2012
From: taget at linux.vnet.ibm.com (Eli Qiao)
Date: Tue, 10 Jul 2012 10:34:58 +0800
Subject: [node-devel] install error and debug method
In-Reply-To: <4FFB8A13.2000504@linux.vnet.ibm.com>
References: <1341503171.4948.19.camel@fdeutsch-laptop.local>
	<4FFA99C0.6040801@linux.vnet.ibm.com>
	<1341823780.2332.9.camel@fdeutsch-laptop.local>
	<1341829465.26430.3.camel@beelzebub.mburnsfire.net>
	<4FFB8A13.2000504@linux.vnet.ibm.com>
Message-ID: <4FFB94D2.9090506@linux.vnet.ibm.com>

? 2012?07?10? 09:49, Eli Qiao ??:
> ? 2012?07?09? 18:24, Mike Burns ??:
>> On Mon, 2012-07-09 at 10:49 +0200, Fabian Deutsch wrote:
>>> Hey,
>>>
>>> Am Montag, den 09.07.2012, 16:43 +0800 schrieb Eli Qiao:
>>>>        * I failed to install a version of build (I built it myself)
>>>>          base on F17, it show nothing just tell me to log as admin 
>>>> ,but
>>>>          I didn't set up a password for admin and root. what the 
>>>> passwd
>>>>          is ?
>>> If no password is given at an auto-ionstall the the admin and root
>>> accounts will be disabled. You need to provide an admin/rootpw at
>>> install time (via kargs, see below)-
>> This sounds like a problem with the TUI loading, but without more
>> information, I can't say for sure.
>>
>> Is this the first boot that you've done?  Did the TUI ever load at all?
>> What changes did you make before doing the build?
>>
> yes , it's first boot, the TUI didn't loading
>>>>        * And also , I have some question about how to debug the
>>>>          ovirt-node, would someone kindly give me a hand ?
>>> Most ovirt node specific log messages go to /var/log/ovirt.log .
>>> But the base components log to their predefined locations.
>>> Might I ask what you want to debug?
>>>
>>>>        * Can I ask that what should I do if I want to set a 
>>>> password in
>>>>          the bootparameters such rootpw=XXX
>>>> what XXX like ?
>>>>
>>>> I generate the passwd by doing this :
>>>>   perl -e 'print crypt("123",q($1$IPPBXADM)),"\n"'
>>>> $1$IPPBXADM$UwX5u7LVJoJ/EJfG4d8HC1
>>>>
>>>> but when I type 123 , it's shows I am input a wrong password , what
>>>> encryption does node use ? md5 or sha1 ?
>>> I just know that you can use the openssl passwd command to generated a
>>> valid password hash, e.g.:
>>>
>>> $ openssl passwd -salt foo bar
>>> foXrpAKGo3142
>>>
>>> This hash can be used as a karg: adminpw=foXrpAKGo3142
>> Better to use openssl passwd -1 and then enter and verify the password.
>>
>> $ openssl passwd -1
>> Password:
>> Verifying - Password:
>> $1$9RXa7lLR$RV46M2aZyxadZQudooryH.
>>
>> To set the root password, you use:
>> rootpw=$1$9RXa7lLR$RV46M2aZyxadZQudooryH.
>>
>> Mike
>>
I install the node again with this boot parameter
rootpw=$1$9WKUWRlf$JHCMWqVRi4BwKabafB43o.

it showed that screen ,and the TUI didn't load

and

The password is incorrect.
ps : I install this build in a virtual machine, is that matter ?

> thanks very much Mike.
>>> Greetings
>>> fabian
>>> _______________________________________________
>>> node-devel mailing list
>>> node-devel at ovirt.org
>>> http://lists.ovirt.org/mailman/listinfo/node-devel
>>
>
>




-- 
Thanks. Best regards. --Eli Qiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120710/8a9dcf55/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot-liyongsnode ???.png
Type: image/png
Size: 39516 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120710/8a9dcf55/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot-liyongsnode ???-1.png
Type: image/png
Size: 34915 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120710/8a9dcf55/attachment-0001.png>

From fabiand at redhat.com  Tue Jul 10 12:30:19 2012
From: fabiand at redhat.com (Fabian Deutsch)
Date: Tue, 10 Jul 2012 14:30:19 +0200
Subject: [node-devel] install error and debug method
In-Reply-To: <4FFB94D2.9090506@linux.vnet.ibm.com>
References: <1341503171.4948.19.camel@fdeutsch-laptop.local>
	<4FFA99C0.6040801@linux.vnet.ibm.com>
	<1341823780.2332.9.camel@fdeutsch-laptop.local>
	<1341829465.26430.3.camel@beelzebub.mburnsfire.net>
	<4FFB8A13.2000504@linux.vnet.ibm.com>
	<4FFB94D2.9090506@linux.vnet.ibm.com>
Message-ID: <1341923419.2248.4.camel@fdeutsch-laptop.local>

Am Dienstag, den 10.07.2012, 10:34 +0800 schrieb Eli Qiao:
> > > > >        * Can I ask that what should I do if I want to set a
> > > > > password in 
> > > > >          the bootparameters such rootpw=XXX 
> > > > > what XXX like ? 
> > > > > 
> > > > > I generate the passwd by doing this : 
> > > > >   perl -e 'print crypt("123",q($1$IPPBXADM)),"\n"' 
> > > > > $1$IPPBXADM$UwX5u7LVJoJ/EJfG4d8HC1 
> > > > > 
> > > > > but when I type 123 , it's shows I am input a wrong password ,
> > > > > what 
> > > > > encryption does node use ? md5 or sha1 ? 
> > > > I just know that you can use the openssl passwd command to
> > > > generated a 
> > > > valid password hash, e.g.: 
> > > > 
> > > > $ openssl passwd -salt foo bar 
> > > > foXrpAKGo3142 
> > > > 
> > > > This hash can be used as a karg: adminpw=foXrpAKGo3142 
> > > Better to use openssl passwd -1 and then enter and verify the
> > > password. 
> > > 
> > > $ openssl passwd -1 
> > > Password: 
> > > Verifying - Password: 
> > > $1$9RXa7lLR$RV46M2aZyxadZQudooryH. 
> > > 
> > > To set the root password, you use: 
> > > rootpw=$1$9RXa7lLR$RV46M2aZyxadZQudooryH. 
> > > 
> > > Mike 
> > > 
> I install the node again with this boot parameter
> rootpw=$1$9WKUWRlf$JHCMWqVRi4BwKabafB43o.
> 
> it showed that screen ,and the TUI didn't load 

Did you install the system via auto-install or a normal TUI
installation?

Greetings
fabian


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120710/14099ddd/attachment.sig>

From mburns at redhat.com  Tue Jul 10 12:55:09 2012
From: mburns at redhat.com (Mike Burns)
Date: Tue, 10 Jul 2012 08:55:09 -0400 (EDT)
Subject: [node-devel] oVirt Node weekly meeting
Message-ID: <1401903716.2652055.1341924909104.JavaMail.root@zmail17.collab.prod.int.phx2.redhat.com>

An HTML attachment was scrubbed...
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120710/e46c3b68/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: invite.ics
Type: text/calendar
Size: 1641 bytes
Desc: not available
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120710/e46c3b68/attachment.ics>

From mburns at redhat.com  Tue Jul 10 13:20:54 2012
From: mburns at redhat.com (Mike Burns)
Date: Tue, 10 Jul 2012 09:20:54 -0400
Subject: [node-devel] oVirt Node Weekly Meeting Minutes -- 2012-07-10
Message-ID: <1341926454.26430.27.camel@beelzebub.mburnsfire.net>

Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-10-13.00.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-10-13.00.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-10-13.00.log.html

=================================
#ovirt: ovirt-node weekly meeting
=================================


Meeting started by mburns at 13:00:34 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-10-13.00.log.html
.



Meeting summary
---------------
* agenda and roll call  (mburns, 13:00:41)

* action item review  (mburns, 13:03:56)
  * LINK:
    http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-03-13.02.html
    (mburns, 13:03:58)
  * registration issue has patches posted to vdsm by dougsland  (mburns,
    13:04:21)
  * also built with patch 5600 to make sure that the registration issue
    was unrelated to that patch  (mburns, 13:05:00)
  * that patch did not solve the problem  (mburns, 13:05:06)
  * efi patches are in sync, but due to some changes in upstream
    livecd-tools, an additional patch will be needed  (mburns, 13:05:55)
  * node-tests repo created and populated by fabiand  (mburns, 13:06:07)
  * 832163 still waiting on info from the user  (mburns, 13:07:23)

* release status  (mburns, 13:10:56)
  * oVirt release delayed until July 25  (mburns, 13:11:22)
  * ACTION: mburns to review 2.5.0 bugs and see if that is feasible
    (mburns, 13:14:41)
  * that in above action item refers to whether we can do 2.5.0 release
    instead of 2.4.1  (mburns, 13:15:03)

* other topics  (mburns, 13:17:08)

Meeting ended at 13:20:03 UTC.




Action Items
------------
* mburns to review 2.5.0 bugs and see if that is feasible




Action Items, by person
-----------------------
* mburns
  * mburns to review 2.5.0 bugs and see if that is feasible
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* mburns (41)
* jboggs (6)
* fabiand (4)
* ovirtbot (3)
* pmyers (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot



From taget at linux.vnet.ibm.com  Wed Jul 11 10:26:53 2012
From: taget at linux.vnet.ibm.com (Eli Qiao)
Date: Wed, 11 Jul 2012 18:26:53 +0800
Subject: [node-devel] install error and debug method
In-Reply-To: <1341923419.2248.4.camel@fdeutsch-laptop.local>
References: <1341503171.4948.19.camel@fdeutsch-laptop.local>
	<4FFA99C0.6040801@linux.vnet.ibm.com>
	<1341823780.2332.9.camel@fdeutsch-laptop.local>
	<1341829465.26430.3.camel@beelzebub.mburnsfire.net>
	<4FFB8A13.2000504@linux.vnet.ibm.com>
	<4FFB94D2.9090506@linux.vnet.ibm.com>
	<1341923419.2248.4.camel@fdeutsch-laptop.local>
Message-ID: <4FFD54ED.5000804@linux.vnet.ibm.com>

? 2012?07?10? 20:30, Fabian Deutsch ??:
> Am Dienstag, den 10.07.2012, 10:34 +0800 schrieb Eli Qiao:
>>>>>>         * Can I ask that what should I do if I want to set a
>>>>>> password in
>>>>>>           the bootparameters such rootpw=XXX
>>>>>> what XXX like ?
>>>>>>
>>>>>> I generate the passwd by doing this :
>>>>>>    perl -e 'print crypt("123",q($1$IPPBXADM)),"\n"'
>>>>>> $1$IPPBXADM$UwX5u7LVJoJ/EJfG4d8HC1
>>>>>>
>>>>>> but when I type 123 , it's shows I am input a wrong password ,
>>>>>> what
>>>>>> encryption does node use ? md5 or sha1 ?
>>>>> I just know that you can use the openssl passwd command to
>>>>> generated a
>>>>> valid password hash, e.g.:
>>>>>
>>>>> $ openssl passwd -salt foo bar
>>>>> foXrpAKGo3142
>>>>>
>>>>> This hash can be used as a karg: adminpw=foXrpAKGo3142
>>>> Better to use openssl passwd -1 and then enter and verify the
>>>> password.
>>>>
>>>> $ openssl passwd -1
>>>> Password:
>>>> Verifying - Password:
>>>> $1$9RXa7lLR$RV46M2aZyxadZQudooryH.
>>>>
>>>> To set the root password, you use:
>>>> rootpw=$1$9RXa7lLR$RV46M2aZyxadZQudooryH.
>>>>
>>>> Mike
>>>>
>> I install the node again with this boot parameter
>> rootpw=$1$9WKUWRlf$JHCMWqVRi4BwKabafB43o.
>>
>> it showed that screen ,and the TUI didn't load
> Did you install the system via auto-install or a normal TUI
> installation?
>
I think so , I just add rootpw in the boot parameters
> Greetings
> fabian
>
>


-- 
Thanks. Best regards. --Eli Qiao



From mburns at redhat.com  Tue Jul 17 13:32:27 2012
From: mburns at redhat.com (Mike Burns)
Date: Tue, 17 Jul 2012 09:32:27 -0400
Subject: [node-devel] oVirt Node Weekly Meeting minutes
Message-ID: <1342531947.6902.54.camel@beelzebub.mburnsfire.net>

Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-17-13.00.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-17-13.00.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-17-13.00.log.html

==============================
#ovirt: ovirt-node weekly sync
==============================


Meeting started by mburns at 13:00:16 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-17-13.00.log.html
.



Meeting summary
---------------
* roll call and agenda  (mburns, 13:00:24)

* action item review  (mburns, 13:02:13)
  * LINK:
    http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-10-13.00.html
    (mburns, 13:02:32)
  * mburns moved all 2.4.1 bugs to 2.5.0  (mburns, 13:03:17)
  * mburns deferred non-applicable 2.5.0 bugs to 2.5.1 (temporarily)
    (mburns, 13:03:34)
  * LINK: http://goo.gl/OqoE3   (mburns, 13:03:38)
  * ACTION: mburns to add 2.7.0 release and future release, and move
    2.6.0/2.5.1 bugs around appropriately  (mburns, 13:04:49)

* Release Status  (mburns, 13:05:26)
  * we're going to be shipping 2.5.0 with the ovirt 3.1 release
    (mburns, 13:05:39)
  * bz on mburns -- move to modified, merged a while ago -- patch
    supplied by community (yay!)  (mburns, 13:12:18)
  * ACTION: jboggs -- 753302 -- split the bz into multiple parts, target
    unfinished to 2.5.1 and mark original as MODIFIED  (mburns,
    13:14:50)
  * ACTION: fabiand -- review 831668 to see if it is fixed or not
    (mburns, 13:15:12)
  * ACTION: mburns to review all patches posted -- including patch for
    811584  (mburns, 13:15:45)
  * ACTION: mburns to follow up on vdsm build  (mburns, 13:17:18)

* Other Topics  (mburns, 13:18:12)

Meeting ended at 13:28:57 UTC.




Action Items
------------
* mburns to add 2.7.0 release and future release, and move 2.6.0/2.5.1
  bugs around appropriately
* jboggs -- 753302 -- split the bz into multiple parts, target
  unfinished to 2.5.1 and mark original as MODIFIED
* fabiand -- review 831668 to see if it is fixed or not
* mburns to review all patches posted -- including patch for 811584
* mburns to follow up on vdsm build




Action Items, by person
-----------------------
* fabiand
  * fabiand -- review 831668 to see if it is fixed or not
* jboggs
  * jboggs -- 753302 -- split the bz into multiple parts, target
    unfinished to 2.5.1 and mark original as MODIFIED
* mburns
  * mburns to add 2.7.0 release and future release, and move 2.6.0/2.5.1
    bugs around appropriately
  * mburns to review all patches posted -- including patch for 811584
  * mburns to follow up on vdsm build
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* mburns (75)
* fabiand (32)
* jboggs (7)
* RobertM (4)
* ovirtbot (4)
* eedri (3)
* READ10 (2)
* pmyers (1)
* gestahlt (1)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot



From mburns at redhat.com  Tue Jul 24 13:19:04 2012
From: mburns at redhat.com (Mike Burns)
Date: Tue, 24 Jul 2012 09:19:04 -0400
Subject: [node-devel] oVirt Node Weekly Meeting Minutes 2012-07-24
Message-ID: <1343135944.14396.6.camel@beelzebub.mburnsfire.net>

Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-24-13.00.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-24-13.00.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-24-13.00.log.html

                   #ovirt: ovirt node weekly meeting
Meeting started by mburns at 13:00:31 UTC (full logs). 


Meeting summary
     1. agenda and roll call (mburns, 13:00:37) 
     2. action item review (mburns, 13:01:57)
             a. http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-17-13.00.html (mburns, 13:02:04)
             b. ACTION: fabiand -- review 831668 to see if it is fixed
                or not (might be fixed by previous patch for nic
                ordering (mburns, 13:03:20)
             c. ACTION: mburns to add 2.7.0 release and future release,
                and move 2.6.0/2.5.1 bugs around appropriately (mburns,
                13:04:11)
             d. ACTION: jboggs to review 753302 and update
                accordingly (mburns, 13:04:33)
             e. mburns reviewed all outstanding patches as of thursday
                last week (mburns, 13:04:55)
             f. there are 15 patches pending now (mburns, 13:05:23)
             g. ACTION: mburns jboggs fabiand_ to review
                patches (mburns, 13:05:31)
             h. new vdsm build was made available and new ovirt-node
                (2.5.0-1) was delivered into beta repo (mburns,
                13:06:28)
             i. then respun as 2.5.0-2 (mburns, 13:06:38)
             j. 2.5.0-2 build is available in beta repo (mburns,
                13:07:25)
             k. 1 possible issue encountered with 2.5.0 builds (mburns,
                13:08:52)
             l. ACTION: jboggs to follow up with dougsland (mburns,
                13:09:00)
        
        
     3. Other topics (mburns, 13:13:44)


Meeting ended at 13:17:29 UTC (full logs). 


Action items
     1. fabiand -- review 831668 to see if it is fixed or not (might be
        fixed by previous patch for nic ordering
     2. mburns to add 2.7.0 release and future release, and move
        2.6.0/2.5.1 bugs around appropriately
     3. jboggs to review 753302 and update accordingly
     4. mburns jboggs fabiand_ to review patches
     5. jboggs to follow up with dougsland



Action items, by person
     1. dougsland
             1. jboggs to follow up with dougsland
     2. fabiand
             1. fabiand -- review 831668 to see if it is fixed or not
                (might be fixed by previous patch for nic ordering
             2. mburns jboggs fabiand_ to review patches
     3. fabiand_
             1. mburns jboggs fabiand_ to review patches
     4. jboggs
             1. jboggs to review 753302 and update accordingly
             2. mburns jboggs fabiand_ to review patches
             3. jboggs to follow up with dougsland
     5. mburns
             1. mburns to add 2.7.0 release and future release, and move
                2.6.0/2.5.1 bugs around appropriately
             2. mburns jboggs fabiand_ to review patches



People present (lines said)
     1. mburns (39)
     2. jboggs (6)
     3. fabiand_ (5)
     4. ovirtbot (4)
     5. RobertM (3)
     6. READ10 (1)
     7. dougsland (1)
     8. pmyers (0)
     9. fabiand (0)


Generated by MeetBot 0.1.4.



From fabiand at redhat.com  Wed Jul 25 10:36:18 2012
From: fabiand at redhat.com (Fabian Deutsch)
Date: Wed, 25 Jul 2012 12:36:18 +0200
Subject: [node-devel] Update on Node automation - testing on real hardware
	w/ igor-0.2.1
Message-ID: <1343212578.2346.8.camel@fdeutsch-laptop.local>

Hey,

igor [1] is running silently in the background each night and checking
nightly ISO builds against some [2, 3] testsuites.

As of today igor (0.2.1, [4]) also supports testing the testsuites on
real hardware (just tested with existing cobbler system whose power
control works). That means you can now easily run testsuites against
Node builds transparently on VMs and real hardware.
There is also a recipe in the works which documents how to get igor
running [5].

It's time to specify more testsuites, e.g. registering to oVirt Engine.
Volunteers?

Greetings
fabian

[1] https://gitorious.org/ovirt/igord
[2]
http://gerrit.ovirt.org/gitweb?p=ovirt-node.git;a=tree;f=tests/igor;hb=HEAD
[3] http://wiki.ovirt.org/wiki/Node_Testing#Basic_Testcases
[4] https://gitorious.org/ovirt/igord/trees/igor-0.2.1
[5] http://gerrit.ovirt.org/#/c/6529/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120725/a215ddf8/attachment.sig>

From fabiand at redhat.com  Mon Jul 30 08:41:02 2012
From: fabiand at redhat.com (Fabian Deutsch)
Date: Mon, 30 Jul 2012 10:41:02 +0200
Subject: [node-devel] Bringing common python checks to Node
Message-ID: <1343637662.2270.11.camel@fdeutsch-laptop.local>

Hey,

currently it's quite impossible to run common python code checkers like
pyflakes, pylint, doctests, and nose tests on the Node sources. There
are several reasons and the main two beeing:
(a) Functions (unit-/doctests) require runtime informations
(b) Imports fail b/c of a non-standard filesystem hierarchy

Igor was introduced to solve (a). Igor now provisions VMs and real
hardware to run tests at runtime (covering installation and the TUI).

For (b) I've started to refactor some code, restructure some files [1],
and added some basic Makefile targets [2] to solve this. 
My goal is to be able to run at least pep8, pylint and pyflakes checks
"offline" - so without a running Node, e.g. with a pre-commit git hook.
The first batch of patches can be found in gerrit, in the pychecks
topic-branch.
This is a work in progress.

Greetings
fabian


[1] http://gerrit.ovirt.org/#/c/6725/
[2] http://gerrit.ovirt.org/#/c/6726/
[3] http://gerrit.ovirt.org/p/ovirt-node
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://lists.ovirt.org/pipermail/node-devel/attachments/20120730/f4350749/attachment.sig>

From mburns at redhat.com  Tue Jul 31 13:11:37 2012
From: mburns at redhat.com (Mike Burns)
Date: Tue, 31 Jul 2012 09:11:37 -0400
Subject: [node-devel] oVirt Node Weekly Meeting Minutes -- 2012-07-31
Message-ID: <1343740297.28966.17.camel@beelzebub.mburnsfire.net>

Minutes:        http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-31-13.00.html
Minutes (text): http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-31-13.00.txt
Log:            http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-31-13.00.log.html

==============================
#ovirt: ovirt node weekly sync
==============================


Meeting started by mburns at 13:00:40 UTC. The full logs are available
at http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-31-13.00.log.html
.



Meeting summary
---------------
* roll call and agenda  (mburns, 13:00:49)

* action item review  (mburns, 13:01:57)
  * LINK:
    http://ovirt.org/meetings/ovirt/2012/ovirt.2012-07-24-13.00.html
    (mburns, 13:01:59)
  * bug 831668 closed by fabiand  (mburns, 13:03:14)
  * 753302 moved to post by jboggs  (mburns, 13:03:55)
  * ACTION: mburns to handle 2.7.0/2.6.0/2.5.1 bug triage  (mburns,
    13:04:35)
  * issue with vdsm in 2.5.0 -- patch posted and merged into vdsm,
    awaiting new build to include in ovirt-node iso  (mburns, 13:05:15)
  * patch queue was down to just a handful of patches, but is now back
    up around 40-50 patches  (mburns, 13:05:53)
  * thanks to fabiand ...  (mburns, 13:06:02)
  * ACTION: jboggs mburns fabiand to review patches  (mburns, 13:06:22)

* release status  (mburns, 13:06:51)
  * no release blockers for ovirt-node  (mburns, 13:07:02)
  * waiting on new vdsm package to build final iso  (mburns, 13:07:12)
  * release date for oVirt Project is 8-Aug  (mburns, 13:08:08)

* other topics  (mburns, 13:08:27)
  * jboggs on vacation  (mburns, 13:09:09)

Meeting ended at 13:09:20 UTC.




Action Items
------------
* mburns to handle 2.7.0/2.6.0/2.5.1 bug triage
* jboggs mburns fabiand to review patches




Action Items, by person
-----------------------
* fabiand
  * jboggs mburns fabiand to review patches
* jboggs
  * jboggs mburns fabiand to review patches
* mburns
  * mburns to handle 2.7.0/2.6.0/2.5.1 bug triage
  * jboggs mburns fabiand to review patches
* **UNASSIGNED**
  * (none)




People Present (lines said)
---------------------------
* mburns (31)
* fabiand (5)
* ovirtbot (4)
* pmyers (1)
* jboggs (0)




Generated by `MeetBot`_ 0.1.4

.. _`MeetBot`: http://wiki.debian.org/MeetBot