similar to: Updated ovirt-build and ovirt-release RPMs...

The ovirt-server package has started to slip behind the curve WRT Ruby on Rails development; i.e., the current version of ovirt-server is not quite runnable as is on F12. And with F13 coming, the gap's only going to widen. So I'm considering the idea of freezing the version of Rails on the ovirt-server project for the time being. I'll check with the Fedora packaging team to see if

(cc'ing the ovirt-devel mailing list) On Mon, Mar 08, 2010 at 09:13:43PM +0100, Arthur CLEMENT wrote: > I need an non-reachable ip to increase the security (nobody have to log on the > node from this interface). The interface does'nt require an ip, the ethernet > connection is sufficient to be bridged, only vms will get an ip. I already use > unconfigured interface

Hi, I'm having some problems building ovirt. The build fails during the final ovirt build stage in the instructions. The failure is because it can't find "/usr/share/ovirt-node-tools/ovirt-node-recipe.ks". I've checked and sure enough it's not there. Has anyone else come across this problem? Building on FC13 using the instructions found here:

Are we ready to push a new update to the ovirt.org website? And does the ChangeLog document reflect the latest changes? -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors. http://www.redhat.com/promo/vendor/ -------------- next part -------------- A non-text attachment was scrubbed... Name: not available

Due to some issues around channel ownership and spamming, we've decided to move the IRC channel for discussing issues over to the OFTC IRC network[1]. I'll continue to be available in the channel on freenode for a while, but I'll be redirecting people to our new channel. Thanks for your understanding. Any questions, please feel free to ask. [1] - http://www.oftc.net/oftc/ -- Darryl

So in working on making the node more generic, I've initially taken on the startup processes. Right now I have patches that I'm finishing which will give a more generic way of performing the following functions: * AWAKE - notify the management system the node is awake * READY - notify the management system the node is ready to perform tasks and run VMS * OFFLINE -

I've been pulling together some ideas for extending the messaging interface for the managed node. I've put together the ideas I've had initially on the following wiki page: http://www.ovirt.org/page/MessagingInterface Questions? Comments? -- Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc. Delivering value year after year. Red Hat ranks #1 in value among software vendors.

Now the execution order for the ovirt sysvinit scripts is: ovirt-early -> ovirt-awake -> ovirt -> ovirt-post Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt | 2 +- scripts/ovirt-awake | 1 + scripts/ovirt-early | 1 - 3 files changed, 2 insertions(+), 2 deletions(-) diff --git a/scripts/ovirt b/scripts/ovirt index 752564a..d2e338d 100755

One task I'm working on is to make the managed node more generic, so that it can be leveraged by other hypervisor managers in the same way that it is managed by the ovirt-wui. One thing I'm considering doing is to add a new configuration file to the node, /etc/sysconfig/node-config. This will be a central point for defining specific elements, such as management servers, user names, etc.

I meant to send this out a while back, but don't see that I ever actually sent it. I'm currently reworking the matahari agents to clean up the code, refactor elements and also enhance the agents. And the one that has me stumped is the NIC agent. The main problem is that, if we're going to represent network interfaces, we shouldn't limit it to only physical devices. Instead, I

Added new files to track changes, development plans, as well as to inform developers of how they can provide contributions to the project. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- .gitignore | 1 + CONTRIBUTING | 4 ++++ ChangeLog | 2 ++ TODO | 6 ++++++ configure.ac | 2 +- 5 files changed, 14 insertions(+), 1 deletions(-) create mode

Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- recipe/Makefile.am | 4 +++- 1 files changed, 3 insertions(+), 1 deletions(-) diff --git a/recipe/Makefile.am b/recipe/Makefile.am index 0bd139f..6c97ed0 100644 --- a/recipe/Makefile.am +++ b/recipe/Makefile.am @@ -3,6 +3,7 @@ CUR_RAWHIDE = 14 CUR_DEVEL = 13 CUR_PREVIEW = 12 PREVIEW_URL ?=

If the address is not blank then it is validated. Only those that are properly formed are accepted. Otherwise an error message is displayed and the user is prompted again. Resolves: rhbz#536912 - validation for static IP should be optimized Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- scripts/ovirt-config-networking | 28 +++++++++++++++++++++++++--- 1 files changed, 25

Hi, Ovirt, I was trying to download and see Ovirt ruby and rail server code, but I see all python code under ovirtserver folder. Where can I see Ovirt management server's web ui codes?

Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- src/app/controllers/application_controller.rb | 2 +- src/config/environment.rb | 2 +- src/config/initializers/new_rails_defaults.rb | 6 +++++- 3 files changed, 7 insertions(+), 3 deletions(-) diff --git a/src/app/controllers/application_controller.rb b/src/app/controllers/application_controller.rb

It provides an initial implementation, LinuxPlatform, which is by default included in the build. Later code will refactor the build process to include the appropriate implementation depending on the target platform. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- src/Makefile.am | 4 ++ src/linux_platform.cpp | 117 ++++++++++++++++++++++++++++++++++++++++++++++++

Added a new subdirectory called "isobuilder" to the project. Created a new Makefile that only allows for creating the livecd version of the oVirt node. Adjusted the build environment to work with the kickstart files that are found in the repo and not ones installed via any previous RPM. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- configure.ac | 1 +

Users select a virtual machine on their current libvirt host. They then select a target machine, which must have been previously configured as a connection. They confirm the migration and then it runs. Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- nodeadmin/addhost.py | 10 ++++- nodeadmin/libvirtworker.py | 6 +++ nodeadmin/migratedomain.py | 81

The user can: * select a remote machine * add a remote machine * remove a remote machine Signed-off-by: Darryl L. Pierce <dpierce at redhat.com> --- Makefile.am | 5 ++ nodeadmin/addhost.py | 129 ++++++++++++++++++++++++++++++++++++++++++++ nodeadmin/changehost.py | 58 ++++++++++++++++++++ nodeadmin/configscreen.py | 36 ++++++++++++-

The Multiplexer lets Matahari register APIs and then call them by that registered name. APIs are function pointers in the form of: const char* function(const char *); where the API takes as input a descriptor containing any arguments, and returns an array containing the response or result. Also adds a testing directory and unit tests to validate the Multiplexer. The new directory, src/tests,