Hi, Can I get a new gerrit repo added for ovirt-node-iso? An empty repo should be fine initially. The purpose of this repo is to package the ovirt-node iso image in an rpm for delivery. Ideally, this could be done as a sub-package of ovirt-node, but there is a chicken and egg problem. You need the ovirt-node rpm in order to generate the iso which you need to build the ovirt-node-iso rpm. We also need to keep the generation of the ovirt-node rpm and the iso image in separate steps so we could create multiple images from a single ovirt-node rpm. This would allow something like an update to a package that isn't ovirt-node to be included. For example, if vdsm had a critical update, we need to be able to regenerate the ovirt-node iso image without have to rebuild the ovirt-node rpm. Thanks Mike
On 02/09/2012 05:07 AM, Mike Burns wrote:
Hi,
Can I get a new gerrit repo added for ovirt-node-iso? An empty repo should be fine initially.
The purpose of this repo is to package the ovirt-node iso image in an rpm for delivery. Ideally, this could be done as a sub-package of ovirt-node, but there is a chicken and egg problem. You need the ovirt-node rpm in order to generate the iso which you need to build the ovirt-node-iso rpm. We also need to keep the generation of the ovirt-node rpm and the iso image in separate steps so we could create multiple images from a single ovirt-node rpm. This would allow something like an update to a package that isn't ovirt-node to be included. For example, if vdsm had a critical update, we need to be able to regenerate the ovirt-node iso image without have to rebuild the ovirt-node rpm.
Thanks
Mike
I'm assuming the only issue is you want to keep the single package per repo policy, rather than any technical/logistical issue with managing the code? I have no problem creating it, it is same project as far as i am concerned, just needs separation due to packaging. let's give a day for comments in case someone has an issue for some reason, and I'll create it if no objections. karsten/ofer/barak/doron/anyone - thoughts/comments/issues/support? thanks, Itamar
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 02/08/2012 10:38 PM, Itamar Heim wrote:
On 02/09/2012 05:07 AM, Mike Burns wrote:
Hi,
Can I get a new gerrit repo added for ovirt-node-iso? An empty repo should be fine initially.
The purpose of this repo is to package the ovirt-node iso image in an rpm for delivery. Ideally, this could be done as a sub-package of ovirt-node, but there is a chicken and egg problem. You need the ovirt-node rpm in order to generate the iso which you need to build the ovirt-node-iso rpm. We also need to keep the generation of the ovirt-node rpm and the iso image in separate steps so we could create multiple images from a single ovirt-node rpm. This would allow something like an update to a package that isn't ovirt-node to be included. For example, if vdsm had a critical update, we need to be able to regenerate the ovirt-node iso image without have to rebuild the ovirt-node rpm.
Thanks
Mike
I'm assuming the only issue is you want to keep the single package per repo policy, rather than any technical/logistical issue with managing the code? I have no problem creating it, it is same project as far as i am concerned, just needs separation due to packaging. let's give a day for comments in case someone has an issue for some reason, and I'll create it if no objections. karsten/ofer/barak/doron/anyone - thoughts/comments/issues/support?
+1 ... makes sense to me, too. - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPM4mA2ZIOBq0ODEERApL9AJ9wR29oMlpzWSGdiXMJ9lZxMblmgACfZn7A UKOxB/zSHY93Xt9ZUOvMLYY= =xX0c -----END PGP SIGNATURE-----
On 09/02/12 10:53, Karsten 'quaid' Wade wrote:
On 02/08/2012 10:38 PM, Itamar Heim wrote:
On 02/09/2012 05:07 AM, Mike Burns wrote:
Hi,
Can I get a new gerrit repo added for ovirt-node-iso? An empty repo should be fine initially.
The purpose of this repo is to package the ovirt-node iso image in an rpm for delivery. Ideally, this could be done as a sub-package of ovirt-node, but there is a chicken and egg problem. You need the ovirt-node rpm in order to generate the iso which you need to build the ovirt-node-iso rpm. We also need to keep the generation of the ovirt-node rpm and the iso image in separate steps so we could create multiple images from a single ovirt-node rpm. This would allow something like an update to a package that isn't ovirt-node to be included. For example, if vdsm had a critical update, we need to be able to regenerate the ovirt-node iso image without have to rebuild the ovirt-node rpm.
Thanks
Mike
I'm assuming the only issue is you want to keep the single package per repo policy, rather than any technical/logistical issue with managing the code? I have no problem creating it, it is same project as far as i am concerned, just needs separation due to packaging. let's give a day for comments in case someone has an issue for some reason, and I'll create it if no objections. karsten/ofer/barak/doron/anyone - thoughts/comments/issues/support?
+1 ... makes sense to me, too.
It's simply a new project in current gerrit.ovort.org, which will create a new git repo. I'm all for repo separation to minimize dangers of corruptions. +1. -- /d "Common sense is not so common." --Voltaire, Dictionnaire Philosophique (1764)
----- Original Message -----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 02/08/2012 10:38 PM, Itamar Heim wrote:
On 02/09/2012 05:07 AM, Mike Burns wrote:
Hi,
Can I get a new gerrit repo added for ovirt-node-iso? An empty repo should be fine initially.
The purpose of this repo is to package the ovirt-node iso image in an rpm for delivery. Ideally, this could be done as a sub-package of ovirt-node, but there is a chicken and egg problem. You need the ovirt-node rpm in order to generate the iso which you need to build the ovirt-node-iso rpm. We also need to keep the generation of the ovirt-node rpm and the iso image in separate steps so we could create multiple images from a single ovirt-node rpm. This would allow something like an update to a package that isn't ovirt-node to be included. For example, if vdsm had a critical update, we need to be able to regenerate the ovirt-node iso image without have to rebuild the ovirt-node rpm.
Thanks
Mike
I'm assuming the only issue is you want to keep the single package per repo policy, rather than any technical/logistical issue with managing the code? I have no problem creating it, it is same project as far as i am concerned, just needs separation due to packaging. let's give a day for comments in case someone has an issue for some reason, and I'll create it if no objections. karsten/ofer/barak/doron/anyone - thoughts/comments/issues/support?
+1 ... makes sense to me, too.
+1, same here
- -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iD8DBQFPM4mA2ZIOBq0ODEERApL9AJ9wR29oMlpzWSGdiXMJ9lZxMblmgACfZn7A UKOxB/zSHY93Xt9ZUOvMLYY= =xX0c -----END PGP SIGNATURE-----
On Thu, 2012-02-09 at 08:38 +0200, Itamar Heim wrote:
On 02/09/2012 05:07 AM, Mike Burns wrote:
Hi,
Can I get a new gerrit repo added for ovirt-node-iso? An empty repo should be fine initially.
The purpose of this repo is to package the ovirt-node iso image in an rpm for delivery. Ideally, this could be done as a sub-package of ovirt-node, but there is a chicken and egg problem. You need the ovirt-node rpm in order to generate the iso which you need to build the ovirt-node-iso rpm. We also need to keep the generation of the ovirt-node rpm and the iso image in separate steps so we could create multiple images from a single ovirt-node rpm. This would allow something like an update to a package that isn't ovirt-node to be included. For example, if vdsm had a critical update, we need to be able to regenerate the ovirt-node iso image without have to rebuild the ovirt-node rpm.
Thanks
Mike
I'm assuming the only issue is you want to keep the single package per repo policy, rather than any technical/logistical issue with managing the code? I have no problem creating it, it is same project as far as i am concerned, just needs separation due to packaging. let's give a day for comments in case someone has an issue for some reason, and I'll create it if no objections. karsten/ofer/barak/doron/anyone - thoughts/comments/issues/support?
Thanks! Ownership should be the ovirt-node-maintainers group. Mike
thanks, Itamar _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
On 02/09/2012 10:26 PM, Mike Burns wrote:
On Thu, 2012-02-09 at 08:38 +0200, Itamar Heim wrote:
On 02/09/2012 05:07 AM, Mike Burns wrote:
Hi,
Can I get a new gerrit repo added for ovirt-node-iso? An empty repo should be fine initially.
The purpose of this repo is to package the ovirt-node iso image in an rpm for delivery. Ideally, this could be done as a sub-package of ovirt-node, but there is a chicken and egg problem. You need the ovirt-node rpm in order to generate the iso which you need to build the ovirt-node-iso rpm. We also need to keep the generation of the ovirt-node rpm and the iso image in separate steps so we could create multiple images from a single ovirt-node rpm. This would allow something like an update to a package that isn't ovirt-node to be included. For example, if vdsm had a critical update, we need to be able to regenerate the ovirt-node iso image without have to rebuild the ovirt-node rpm.
Thanks
Mike
I'm assuming the only issue is you want to keep the single package per repo policy, rather than any technical/logistical issue with managing the code? I have no problem creating it, it is same project as far as i am concerned, just needs separation due to packaging. let's give a day for comments in case someone has an issue for some reason, and I'll create it if no objections. karsten/ofer/barak/doron/anyone - thoughts/comments/issues/support?
Thanks!
Ownership should be the ovirt-node-maintainers group.
should be there. try it out.
On Thu, 2012-02-09 at 22:27 +0200, Itamar Heim wrote:
On 02/09/2012 10:26 PM, Mike Burns wrote:
On Thu, 2012-02-09 at 08:38 +0200, Itamar Heim wrote:
On 02/09/2012 05:07 AM, Mike Burns wrote:
Hi,
Can I get a new gerrit repo added for ovirt-node-iso? An empty repo should be fine initially.
The purpose of this repo is to package the ovirt-node iso image in an rpm for delivery. Ideally, this could be done as a sub-package of ovirt-node, but there is a chicken and egg problem. You need the ovirt-node rpm in order to generate the iso which you need to build the ovirt-node-iso rpm. We also need to keep the generation of the ovirt-node rpm and the iso image in separate steps so we could create multiple images from a single ovirt-node rpm. This would allow something like an update to a package that isn't ovirt-node to be included. For example, if vdsm had a critical update, we need to be able to regenerate the ovirt-node iso image without have to rebuild the ovirt-node rpm.
Thanks
Mike
I'm assuming the only issue is you want to keep the single package per repo policy, rather than any technical/logistical issue with managing the code? I have no problem creating it, it is same project as far as i am concerned, just needs separation due to packaging. let's give a day for comments in case someone has an issue for some reason, and I'll create it if no objections. karsten/ofer/barak/doron/anyone - thoughts/comments/issues/support?
Thanks!
Ownership should be the ovirt-node-maintainers group.
Looks good, thanks! Mike
should be there. try it out. _______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/mailman/listinfo/infra
participants (5)
-
Doron Fediuck -
Itamar Heim -
Karsten 'quaid' Wade -
Mike Burns -
Ofer Schreiber