[Engine-devel] 答复: Engine-devel Digest, Vol 20, Issue 39
wlbleaboy@126
wlbleaboy at 126.com
Tue May 14 07:09:51 UTC 2013
Re: ovirt-engine-sdk with C (Jarod. w)
Yes, you understanded my idea, I want to use c to invoke ovirt
engine RestAPI directly,
I'll try it(libcurl), but is there any exist example in ovirt-engine
project. I just want to connect
to ovirt-engine and get vms info, console vm and do some action(start,
stop.).
thinks.
-----邮件原件-----
发件人: engine-devel-bounces at ovirt.org
[mailto:engine-devel-bounces at ovirt.org] 代表 engine-devel-request at ovirt.org
发送时间: 2013年5月14日 14:19
收件人: engine-devel at ovirt.org
主题: Engine-devel Digest, Vol 20, Issue 39
Send Engine-devel mailing list submissions to
engine-devel at ovirt.org
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.ovirt.org/mailman/listinfo/engine-devel
or, via email, send a message with subject or body 'help' to
engine-devel-request at ovirt.org
You can reach the person managing the list at
engine-devel-owner at ovirt.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Engine-devel digest..."
Today's Topics:
1. Re: ovirt-engine-sdk with C (Jarod. w)
2. Re: [ANN] New development environment for ovirt-engine
(Yair Zaslavsky)
3. Re: [ANN] New development environment for ovirt-engine
(Alon Bar-Lev)
4. Re: [ANN] New development environment for ovirt-engine
(Alon Bar-Lev)
----------------------------------------------------------------------
Message: 1
Date: Tue, 14 May 2013 10:27:11 +0800
From: "Jarod. w" <work.iec23801 at gmail.com>
To: "leaboy at 126" <wlbleaboy at 126.com>
Cc: engine-devel at ovirt.org
Subject: Re: [Engine-devel] ovirt-engine-sdk with C
Message-ID:
<CAGEoUW8a4XP=VA_NHXd1wD6sqA5dBdPPauMPrQE0RiKQ4Za8Aw at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
2013/5/13 leaboy at 126 <wlbleaboy at 126.com>
> Hi?All****
>
> I felt oivrt-engine-sdk coded with Python is slowly to connect***
> *
>
> ovirt-engine and console vm when a user have many vms, So, I just****
>
> want to rewrite the sdk with C(ANSI C Language). Just rewrite a sdk****
>
> with C to connect overt-engine and console vm, would anyone give ****
>
> me some suggestion.
>
Do you want to use c to invoke ovirt engine RestAPI, right?
If yes, you can use libcurl to do the thing, and it'll make you happy.
> ****
>
> ** **
>
> Now, the problem is how can I connect to ovit-engine with C, and*
> ***
>
> how can I get some information of vms, and how ovirrt-engine can ****
>
> respond my action(start,stop, .eg)
>
Agree with Michael Pasternak.
You should parse your code into the mail list, or someone can't help
you.
> ****
>
> ** **
>
>
> Leaboy at beijing****
>
> Thinks***
> *
>
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
>
--
---
Best Regards
Jarod.W
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.ovirt.org/pipermail/engine-devel/attachments/20130514/1aed1a4f
/attachment-0001.html>
------------------------------
Message: 2
Date: Mon, 13 May 2013 22:39:19 -0400 (EDT)
From: Yair Zaslavsky <yzaslavs at redhat.com>
To: Eli Mesika <emesika at redhat.com>
Cc: engine-devel <engine-devel at ovirt.org>, arch <arch at ovirt.org>
Subject: Re: [Engine-devel] [ANN] New development environment for
ovirt-engine
Message-ID: <975472192.855606.1368499159787.JavaMail.root at redhat.com>
Content-Type: text/plain; charset=utf-8
Alon,
I have FC17, and followed the steps at the wiki , i defined the ovirt
nightly repo
[ovirt-nightly]
name=ovirt-nightly
baseurl=http://resources.ovirt.org/releases/nightly/rpm/Fedora/17/
enabled=1
gpgcheck=0
priority=1
protect=1
And performed yum install according to your guidelines.
It fails to find python-m2crypto
Can you please advise on the matter?
Many thanks,
Yair
----- Original Message -----
> From: "Eli Mesika" <emesika at redhat.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: "engine-devel" <engine-devel at ovirt.org>, "arch" <arch at ovirt.org>
> Sent: Tuesday, May 14, 2013 3:45:41 AM
> Subject: Re: [Engine-devel] [ANN] New development environment for
ovirt-engine
>
>
>
> ----- Original Message -----
> > From: "Alon Bar-Lev" <alonbl at redhat.com>
> > To: "engine-devel" <engine-devel at ovirt.org>
> > Cc: "arch" <arch at ovirt.org>, "Sharad Mishra" <snmishra at us.ibm.com>,
"Limor
> > Gavish" <lgavish at gmail.com>
> > Sent: Sunday, May 12, 2013 2:52:51 PM
> > Subject: [Engine-devel] [ANN] New development environment for
ovirt-engine
> >
> > Hello all ovirt-engine developers,
> >
> > When I first joined the ovirt project, it took me about two weeks to
setup
> > a
> > development environment, I needed to work on a bug related to
host-deploy
> > so
> > I needed an environment that could use the ssh, PKI, vdsm-bootstrap and
> > communicate with vdsm using SSL, this was virtually impossible to do so
> > without tweaking the product in a way that it is so different from
> > production use, that I cannot guarantee that whatever tested in
development
> > will actually work in production.
> >
> > I peeked at the installation script in a hope that I can create partial
> > environment similar to production, but I found that the packaging
> > implementation makes to much assumption and is very difficult to adopt.
The
> > fact that I do not use fedora/rhel for my development made it even
worse.
> >
> > I had no other option than to create rpms after each of my changes and
test
> > each in real production like setup.
> >
> > It was obvious to me that the manual customization of developers to
achieve
> > working product will eventually break as product grow and move away from
> > being developer friendly to production friendly. For example, product
> > defaults cannot be these which serve developers, but these which serve
> > production the best, or having a valid PKI setup cannot be optional any
> > more
> > as components do need to use it. Same for location of files and
> > configuration, for example, if we write a pluggable infrastructure for
> > branding, we cannot damage the interface just because developers runs
the
> > product in their own manual customization.
> >
> > I took the opportunity handed to me to port the ovirt-engine to other
> > distributions in order to provide a development environment that is
similar
> > to production setup. Together with Sandro Bonazzola and Alex Lourie we
> > re-wrote the whole installation of the product which can also be used to
> > setup the desired development environment.
> >
> > Within this environment the product is set up using the same tools and
> > configuration as in production, while the process does not require
special
> > privileges nor changes the state of the developer machine.
> >
> > A complete documentation is available[1], I preferred to use README
within
> > the source tree as wiki tend to quickly become obsolete, while
> > documentation
> > within source tree can be modified by the commit that introduces a
change.
> > I
> > will redirect to this file from the current wiki once the site will be
up.
> >
> > In a nut shell, after installing prerequisites, build and install the
> > product
> > using:
> >
> > $ make clean install-dev PREFIX=$HOME/ovirt-engine
> >
> > This will run maven and create product installation at
$HOME/ovirt-engine
> > Next, a setup phase is required just like in production, to initialize
> > configuration and database:
> >
> > $ $HOME/ovirt-engine/bin/engine-setup-2
> >
> > You have now fully functional product, including PKI, SSL, host-deploy,
> > tools.
> > No manual database updates are required, no lose of functionality.
> >
> > All that is left is to start the engine service:
> >
> > $ $HOME/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py start
> >
> > Access to application:
> > http://localhost:8080
> > https://localhost:8443
> > Debugging port is opened at port 8787.
> >
> > Farther information exists in the documentation[1].
> >
> > There are several inherit benefits of the new environment, the major one
is
> > the ability to manage several environments in parallel on the same host.
> > For
> > example, if we develop two separate features on two branches we can
install
> > the product into $HOME/ovirt-engine-feature1 and
> > $HOME/ovirt-engine-feature-2 and have a separate database for each, if
we
> > modify the ports jboss is listening to we can run two instances of
engine
> > at
> > the same time!
>
> It is not clear to me why working on 2 bugs needs 2 installations of the
> development environment.
> If you have 2 different git branches and a separate database for each, its
> enough , am I missing something ?
> I was used to create a git branch with the name of the BZ# and use
> create_db.sh script to create a new database with the BZ# name.
> Is this possible in the new method?
> Also, does this mean that I will have to create/configure a new workspace
for
> eclipse each time I am starting to work on a new bug?
>
>
> Thanks
>
>
> >
> > We will be happy to work with all developers to assist in porting into
the
> > new development environment, the simplest is to create a new database
for
> > this effort. Moti has a sequence of converting the existing database
owned
> > by postgres to be owned by the engine, Moti, can you please share that?
> >
> > We are sure there are missing bits, we will be happy to know these so we
> > can
> > improve.
> >
> > I am aware that developers (especially java) are conservative, but I ask
> > you
> > to give us a chance, so that we make it easy for developers to join the
> > project, and to allow us to drop the parallel effort of packaging to
> > production and fixing the broken development environment.
> >
> > A special thanks to developers who took the time to test and provide
> > feedback
> > before the merged:
> > - Yaniv Bronheim
> > - Moti Asayag
> > - Limor Gavish
> > - Sharad Mishra
> > - Ofer Schreiber
> >
> > We are hoping that after migration you will be find this environment
useful
> > and friendly,
> >
> > Sandro Bonazzola,
> > Alex Lourie,
> > Alon Bar-Lev.
> >
> > [1]
> >
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=README.developer;
hb=HEAD
> > _______________________________________________
> > Engine-devel mailing list
> > Engine-devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/engine-devel
> >
> _______________________________________________
> Engine-devel mailing list
> Engine-devel at ovirt.org
> http://lists.ovirt.org/mailman/listinfo/engine-devel
>
------------------------------
Message: 3
Date: Tue, 14 May 2013 01:58:06 -0400 (EDT)
From: Alon Bar-Lev <alonbl at redhat.com>
To: Yair Zaslavsky <yzaslavs at redhat.com>
Cc: engine-devel <engine-devel at ovirt.org>, arch <arch at ovirt.org>
Subject: Re: [Engine-devel] [ANN] New development environment for
ovirt-engine
Message-ID: <998811568.829527.1368511086124.JavaMail.root at redhat.com>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> From: "Yair Zaslavsky" <yzaslavs at redhat.com>
> To: "Eli Mesika" <emesika at redhat.com>
> Cc: "Alon Bar-Lev" <alonbl at redhat.com>, "engine-devel"
<engine-devel at ovirt.org>, "arch" <arch at ovirt.org>
> Sent: Tuesday, May 14, 2013 5:39:19 AM
> Subject: Re: [Engine-devel] [ANN] New development environment for
ovirt-engine
>
> Alon,
> I have FC17, and followed the steps at the wiki , i defined the ovirt
nightly
> repo
>
> [ovirt-nightly]
> name=ovirt-nightly
> baseurl=http://resources.ovirt.org/releases/nightly/rpm/Fedora/17/
> enabled=1
> gpgcheck=0
> priority=1
> protect=1
>
> And performed yum install according to your guidelines.
> It fails to find python-m2crypto
Has nothing to do with ovirt :)
Try m2crypto please.
>
> Can you please advise on the matter?
>
> Many thanks,
> Yair
>
>
>
> ----- Original Message -----
> > From: "Eli Mesika" <emesika at redhat.com>
> > To: "Alon Bar-Lev" <alonbl at redhat.com>
> > Cc: "engine-devel" <engine-devel at ovirt.org>, "arch" <arch at ovirt.org>
> > Sent: Tuesday, May 14, 2013 3:45:41 AM
> > Subject: Re: [Engine-devel] [ANN] New development environment for
> > ovirt-engine
> >
> >
> >
> > ----- Original Message -----
> > > From: "Alon Bar-Lev" <alonbl at redhat.com>
> > > To: "engine-devel" <engine-devel at ovirt.org>
> > > Cc: "arch" <arch at ovirt.org>, "Sharad Mishra" <snmishra at us.ibm.com>,
> > > "Limor
> > > Gavish" <lgavish at gmail.com>
> > > Sent: Sunday, May 12, 2013 2:52:51 PM
> > > Subject: [Engine-devel] [ANN] New development environment for
> > > ovirt-engine
> > >
> > > Hello all ovirt-engine developers,
> > >
> > > When I first joined the ovirt project, it took me about two weeks to
> > > setup
> > > a
> > > development environment, I needed to work on a bug related to
host-deploy
> > > so
> > > I needed an environment that could use the ssh, PKI, vdsm-bootstrap
and
> > > communicate with vdsm using SSL, this was virtually impossible to do
so
> > > without tweaking the product in a way that it is so different from
> > > production use, that I cannot guarantee that whatever tested in
> > > development
> > > will actually work in production.
> > >
> > > I peeked at the installation script in a hope that I can create
partial
> > > environment similar to production, but I found that the packaging
> > > implementation makes to much assumption and is very difficult to
adopt.
> > > The
> > > fact that I do not use fedora/rhel for my development made it even
worse.
> > >
> > > I had no other option than to create rpms after each of my changes and
> > > test
> > > each in real production like setup.
> > >
> > > It was obvious to me that the manual customization of developers to
> > > achieve
> > > working product will eventually break as product grow and move away
from
> > > being developer friendly to production friendly. For example, product
> > > defaults cannot be these which serve developers, but these which serve
> > > production the best, or having a valid PKI setup cannot be optional
any
> > > more
> > > as components do need to use it. Same for location of files and
> > > configuration, for example, if we write a pluggable infrastructure for
> > > branding, we cannot damage the interface just because developers runs
the
> > > product in their own manual customization.
> > >
> > > I took the opportunity handed to me to port the ovirt-engine to other
> > > distributions in order to provide a development environment that is
> > > similar
> > > to production setup. Together with Sandro Bonazzola and Alex Lourie we
> > > re-wrote the whole installation of the product which can also be used
to
> > > setup the desired development environment.
> > >
> > > Within this environment the product is set up using the same tools and
> > > configuration as in production, while the process does not require
> > > special
> > > privileges nor changes the state of the developer machine.
> > >
> > > A complete documentation is available[1], I preferred to use README
> > > within
> > > the source tree as wiki tend to quickly become obsolete, while
> > > documentation
> > > within source tree can be modified by the commit that introduces a
> > > change.
> > > I
> > > will redirect to this file from the current wiki once the site will be
> > > up.
> > >
> > > In a nut shell, after installing prerequisites, build and install the
> > > product
> > > using:
> > >
> > > $ make clean install-dev PREFIX=$HOME/ovirt-engine
> > >
> > > This will run maven and create product installation at
$HOME/ovirt-engine
> > > Next, a setup phase is required just like in production, to initialize
> > > configuration and database:
> > >
> > > $ $HOME/ovirt-engine/bin/engine-setup-2
> > >
> > > You have now fully functional product, including PKI, SSL,
host-deploy,
> > > tools.
> > > No manual database updates are required, no lose of functionality.
> > >
> > > All that is left is to start the engine service:
> > >
> > > $ $HOME/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py start
> > >
> > > Access to application:
> > > http://localhost:8080
> > > https://localhost:8443
> > > Debugging port is opened at port 8787.
> > >
> > > Farther information exists in the documentation[1].
> > >
> > > There are several inherit benefits of the new environment, the major
one
> > > is
> > > the ability to manage several environments in parallel on the same
host.
> > > For
> > > example, if we develop two separate features on two branches we can
> > > install
> > > the product into $HOME/ovirt-engine-feature1 and
> > > $HOME/ovirt-engine-feature-2 and have a separate database for each, if
we
> > > modify the ports jboss is listening to we can run two instances of
engine
> > > at
> > > the same time!
> >
> > It is not clear to me why working on 2 bugs needs 2 installations of the
> > development environment.
> > If you have 2 different git branches and a separate database for each,
its
> > enough , am I missing something ?
> > I was used to create a git branch with the name of the BZ# and use
> > create_db.sh script to create a new database with the BZ# name.
> > Is this possible in the new method?
> > Also, does this mean that I will have to create/configure a new
workspace
> > for
> > eclipse each time I am starting to work on a new bug?
> >
> >
> > Thanks
> >
> >
> > >
> > > We will be happy to work with all developers to assist in porting into
> > > the
> > > new development environment, the simplest is to create a new database
for
> > > this effort. Moti has a sequence of converting the existing database
> > > owned
> > > by postgres to be owned by the engine, Moti, can you please share
that?
> > >
> > > We are sure there are missing bits, we will be happy to know these so
we
> > > can
> > > improve.
> > >
> > > I am aware that developers (especially java) are conservative, but I
ask
> > > you
> > > to give us a chance, so that we make it easy for developers to join
the
> > > project, and to allow us to drop the parallel effort of packaging to
> > > production and fixing the broken development environment.
> > >
> > > A special thanks to developers who took the time to test and provide
> > > feedback
> > > before the merged:
> > > - Yaniv Bronheim
> > > - Moti Asayag
> > > - Limor Gavish
> > > - Sharad Mishra
> > > - Ofer Schreiber
> > >
> > > We are hoping that after migration you will be find this environment
> > > useful
> > > and friendly,
> > >
> > > Sandro Bonazzola,
> > > Alex Lourie,
> > > Alon Bar-Lev.
> > >
> > > [1]
> > >
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=README.developer;
hb=HEAD
> > > _______________________________________________
> > > Engine-devel mailing list
> > > Engine-devel at ovirt.org
> > > http://lists.ovirt.org/mailman/listinfo/engine-devel
> > >
> > _______________________________________________
> > Engine-devel mailing list
> > Engine-devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/engine-devel
> >
>
------------------------------
Message: 4
Date: Tue, 14 May 2013 02:18:44 -0400 (EDT)
From: Alon Bar-Lev <alonbl at redhat.com>
To: Eli Mesika <emesika at redhat.com>
Cc: engine-devel <engine-devel at ovirt.org>, arch <arch at ovirt.org>
Subject: Re: [Engine-devel] [ANN] New development environment for
ovirt-engine
Message-ID: <1732269511.831688.1368512324398.JavaMail.root at redhat.com>
Content-Type: text/plain; charset=utf-8
----- Original Message -----
> From: "Eli Mesika" <emesika at redhat.com>
> To: "Alon Bar-Lev" <alonbl at redhat.com>
> Cc: "engine-devel" <engine-devel at ovirt.org>, "arch" <arch at ovirt.org>
> Sent: Tuesday, May 14, 2013 3:45:41 AM
> Subject: Re: [Engine-devel] [ANN] New development environment for
ovirt-engine
>
>
>
> ----- Original Message -----
> > From: "Alon Bar-Lev" <alonbl at redhat.com>
> > To: "engine-devel" <engine-devel at ovirt.org>
> > Cc: "arch" <arch at ovirt.org>, "Sharad Mishra" <snmishra at us.ibm.com>,
"Limor
> > Gavish" <lgavish at gmail.com>
> > Sent: Sunday, May 12, 2013 2:52:51 PM
> > Subject: [Engine-devel] [ANN] New development environment for
ovirt-engine
> >
> > Hello all ovirt-engine developers,
> >
> > When I first joined the ovirt project, it took me about two weeks to
setup
> > a
> > development environment, I needed to work on a bug related to
host-deploy
> > so
> > I needed an environment that could use the ssh, PKI, vdsm-bootstrap and
> > communicate with vdsm using SSL, this was virtually impossible to do so
> > without tweaking the product in a way that it is so different from
> > production use, that I cannot guarantee that whatever tested in
development
> > will actually work in production.
> >
> > I peeked at the installation script in a hope that I can create partial
> > environment similar to production, but I found that the packaging
> > implementation makes to much assumption and is very difficult to adopt.
The
> > fact that I do not use fedora/rhel for my development made it even
worse.
> >
> > I had no other option than to create rpms after each of my changes and
test
> > each in real production like setup.
> >
> > It was obvious to me that the manual customization of developers to
achieve
> > working product will eventually break as product grow and move away from
> > being developer friendly to production friendly. For example, product
> > defaults cannot be these which serve developers, but these which serve
> > production the best, or having a valid PKI setup cannot be optional any
> > more
> > as components do need to use it. Same for location of files and
> > configuration, for example, if we write a pluggable infrastructure for
> > branding, we cannot damage the interface just because developers runs
the
> > product in their own manual customization.
> >
> > I took the opportunity handed to me to port the ovirt-engine to other
> > distributions in order to provide a development environment that is
similar
> > to production setup. Together with Sandro Bonazzola and Alex Lourie we
> > re-wrote the whole installation of the product which can also be used to
> > setup the desired development environment.
> >
> > Within this environment the product is set up using the same tools and
> > configuration as in production, while the process does not require
special
> > privileges nor changes the state of the developer machine.
> >
> > A complete documentation is available[1], I preferred to use README
within
> > the source tree as wiki tend to quickly become obsolete, while
> > documentation
> > within source tree can be modified by the commit that introduces a
change.
> > I
> > will redirect to this file from the current wiki once the site will be
up.
> >
> > In a nut shell, after installing prerequisites, build and install the
> > product
> > using:
> >
> > $ make clean install-dev PREFIX=$HOME/ovirt-engine
> >
> > This will run maven and create product installation at
$HOME/ovirt-engine
> > Next, a setup phase is required just like in production, to initialize
> > configuration and database:
> >
> > $ $HOME/ovirt-engine/bin/engine-setup-2
> >
> > You have now fully functional product, including PKI, SSL, host-deploy,
> > tools.
> > No manual database updates are required, no lose of functionality.
> >
> > All that is left is to start the engine service:
> >
> > $ $HOME/ovirt-engine/share/ovirt-engine/services/ovirt-engine.py start
> >
> > Access to application:
> > http://localhost:8080
> > https://localhost:8443
> > Debugging port is opened at port 8787.
> >
> > Farther information exists in the documentation[1].
> >
> > There are several inherit benefits of the new environment, the major one
is
> > the ability to manage several environments in parallel on the same host.
> > For
> > example, if we develop two separate features on two branches we can
install
> > the product into $HOME/ovirt-engine-feature1 and
> > $HOME/ovirt-engine-feature-2 and have a separate database for each, if
we
> > modify the ports jboss is listening to we can run two instances of
engine
> > at
> > the same time!
>
> It is not clear to me why working on 2 bugs needs 2 installations of the
> development environment.
> If you have 2 different git branches and a separate database for each, its
> enough , am I missing something ?
You have two different git branches, so you have two different binaries out
of the build, right?
These binaries should reside some where.
Currently you are probably use maven deploy or something similar into single
jboss, without proper environment, overriding each time the other branch's
binaries.
What if there is a change in configuration between the two? more
prerequisites, different service configuration? different database schema?
To make it easy, you can just duplicate the development environment, and be
sure you are up and running.
If you still want to take the chance you can... just make install-dev
PREFIX=$HOME/same-place and you will have the behavior of overriding the
same environment, and hoping for the best.
> I was used to create a git branch with the name of the BZ# and use
> create_db.sh script to create a new database with the BZ# name.
> Is this possible in the new method?
Yes.
You create an empty database manually, let's say engine-branch1.
Then you install the environment to own location, let say make install-dev
PREFIX=$HOME/ovirt-engine-branch1
When running engine-setup-2 you instruct the setup to use engine-branch1
database.
This database will be created out of the new branch's create_db.sh.
create_db.sh should not run manually now.
However, if you insist of creating a database manually and modify an
existing environment to use the new database, it is possible as well.
Edit $PREFIX/etc/ovirt-engine/engine.conf.d/10-setup-database.conf, and
specify where database is, then start the engine service.
> Also, does this mean that I will have to create/configure a new workspace
for
> eclipse each time I am starting to work on a new bug?
This I do not know. How does it work now when you switch branches?
>
>
> Thanks
>
>
> >
> > We will be happy to work with all developers to assist in porting into
the
> > new development environment, the simplest is to create a new database
for
> > this effort. Moti has a sequence of converting the existing database
owned
> > by postgres to be owned by the engine, Moti, can you please share that?
> >
> > We are sure there are missing bits, we will be happy to know these so we
> > can
> > improve.
> >
> > I am aware that developers (especially java) are conservative, but I ask
> > you
> > to give us a chance, so that we make it easy for developers to join the
> > project, and to allow us to drop the parallel effort of packaging to
> > production and fixing the broken development environment.
> >
> > A special thanks to developers who took the time to test and provide
> > feedback
> > before the merged:
> > - Yaniv Bronheim
> > - Moti Asayag
> > - Limor Gavish
> > - Sharad Mishra
> > - Ofer Schreiber
> >
> > We are hoping that after migration you will be find this environment
useful
> > and friendly,
> >
> > Sandro Bonazzola,
> > Alex Lourie,
> > Alon Bar-Lev.
> >
> > [1]
> >
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=blob;f=README.developer;
hb=HEAD
> > _______________________________________________
> > Engine-devel mailing list
> > Engine-devel at ovirt.org
> > http://lists.ovirt.org/mailman/listinfo/engine-devel
> >
>
------------------------------
_______________________________________________
Engine-devel mailing list
Engine-devel at ovirt.org
http://lists.ovirt.org/mailman/listinfo/engine-devel
End of Engine-devel Digest, Vol 20, Issue 39
********************************************
More information about the Engine-devel
mailing list