oVirt 3.6.3 RC4 build starting
by Sandro Bonazzola
Fyi oVirt products maintainers,
An oVirt build for an official release is going to start right now.
If you're a maintainer for any of the projects included in oVirt
distribution and you have changes in your package ready to be released
please:
- bump version and release to be GA ready
- tag your release within git (implies a GitHub Release to be automatically
created)
- build your packages within jenkins / koji / copr / whatever
- verify all bugs on MODIFIED have target release and target milestone set.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
8 years, 9 months
[JIRA] (OVIRT-422) Create jenkins job to compose ovirt 4.0 snaphost early builds
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-422?page=com.atlassian.jira... ]
eyal edri [Administrator] commented on OVIRT-422:
-------------------------------------------------
[~gshinar]
> Create jenkins job to compose ovirt 4.0 snaphost early builds
> -------------------------------------------------------------
>
> Key: OVIRT-422
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-422
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Components: Jenkins, repoman
> Reporter: eyal edri [Administrator]
> Assignee: infra
> Priority: Highest
>
> We need a more static 4.0 snapshots that will be able to be consumed by people who want to verify a certain build without having a rolling nightly build.
> * Add a jjb jenkins job that will run manually/once a week and will create a snap 4.0 repo on
> resources.ovirt.org from latest nightlies (will need to create the repo on resources.ovirt.org/pub/ovirt-4.0/
> * Use repoman with the following cmd: "/usr/bin/repoman ovirt_4.0.0_snap1 add conf:ovirt-4.0-snapshots.repoman --keep-latest 1" [1]
> * This should collect all latest nightlies for 4.0 into a build dir called ovirt_4.0.0_snap1
> * We'll run repoclosure on it once the copy is finished
> * run sanity (either manually or via Lago manual if possible)
> * rhevh team run sanity on the node builds from nightly
> * Create latest_4.0.0_snapshot link to the repo and update it on each release + create new release rpm with that link.
> * Move bugs - either move all MODIFIED bugs with target milestone ovirt-4.0.0 or move only bugs with bug-url from the commit msg.
> * Send email to users/devel with info on release (list of bugs + link to release rpm).
> [2] cat ovirt-4.0-snapshots.repoman (the conf file)
> rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot:latest
> rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot-static:latest
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-02-009#72000)
8 years, 9 months
[JIRA] (OVIRT-423) Build oVirt 3.6.3 RC4
by Rafael Martins (oVirt JIRA)
Rafael Martins created OVIRT-423:
------------------------------------
Summary: Build oVirt 3.6.3 RC4
Key: OVIRT-423
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-423
Project: oVirt - virtualization made easy
Issue Type: Task
Components: Repositories Mgmt
Reporter: Rafael Martins
Assignee: infra
Priority: High
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-01-031#72000)
8 years, 9 months
[JIRA] (OVIRT-422) Create jenkins job to compose ovirt 4.0 snaphost early builds
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-422?page=com.atlassian.jira... ]
eyal edri [Administrator] commented on OVIRT-422:
-------------------------------------------------
[~sbonazzola(a)redhat.com] do you know if anyone from the infra team can handle it?
> Create jenkins job to compose ovirt 4.0 snaphost early builds
> -------------------------------------------------------------
>
> Key: OVIRT-422
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-422
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Components: Jenkins, repoman
> Reporter: eyal edri [Administrator]
> Assignee: infra
> Priority: Highest
>
> We need a more static 4.0 snapshots that will be able to be consumed by people who want to verify a certain build without having a rolling nightly build.
> * Add a jjb jenkins job that will run manually/once a week and will create a snap 4.0 repo on
> resources.ovirt.org from latest nightlies (will need to create the repo on resources.ovirt.org/pub/ovirt-4.0/
> * Use repoman with the following cmd: "/usr/bin/repoman ovirt_4.0.0_snap1 add conf:ovirt-4.0-snapshots.repoman --keep-latest 1" [1]
> * This should collect all latest nightlies for 4.0 into a build dir called ovirt_4.0.0_snap1
> * We'll run repoclosure on it once the copy is finished
> * run sanity (either manually or via Lago manual if possible)
> * rhevh team run sanity on the node builds from nightly
> * Create latest_4.0.0_snapshot link to the repo and update it on each release + create new release rpm with that link.
> * Move bugs - either move all MODIFIED bugs with target milestone ovirt-4.0.0 or move only bugs with bug-url from the commit msg.
> * Send email to users/devel with info on release (list of bugs + link to release rpm).
> [2] cat ovirt-4.0-snapshots.repoman (the conf file)
> rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot:latest
> rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot-static:latest
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-01-031#72000)
8 years, 9 months
[JIRA] (OVIRT-422) Create jenkins job to compose ovirt 4.0 snaphost early builds
by eyal edri [Administrator] (oVirt JIRA)
eyal edri [Administrator] created OVIRT-422:
-----------------------------------------------
Summary: Create jenkins job to compose ovirt 4.0 snaphost early builds
Key: OVIRT-422
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-422
Project: oVirt - virtualization made easy
Issue Type: Task
Components: Jenkins, repoman
Reporter: eyal edri [Administrator]
Assignee: infra
Priority: Highest
We need a more static 4.0 snapshots that will be able to be consumed by people who want to verify a certain build without having a rolling nightly build.
* Add a jjb jenkins job that will run manually/once a week and will create a snap 4.0 repo on
resources.ovirt.org from latest nightlies (will need to create the repo on resources.ovirt.org/pub/ovirt-4.0/
* Use repoman with the following cmd: "/usr/bin/repoman ovirt_4.0.0_snap1 add conf:ovirt-4.0-snapshots.repoman --keep-latest 1" [1]
* This should collect all latest nightlies for 4.0 into a build dir called ovirt_4.0.0_snap1
* We'll run repoclosure on it once the copy is finished
* run sanity (either manually or via Lago manual if possible)
* rhevh team run sanity on the node builds from nightly
* Create latest_4.0.0_snapshot link to the repo and update it on each release + create new release rpm with that link.
* Move bugs - either move all MODIFIED bugs with target milestone ovirt-4.0.0 or move only bugs with bug-url from the commit msg.
* Send email to users/devel with info on release (list of bugs + link to release rpm).
[2] cat ovirt-4.0-snapshots.repoman (the conf file)
rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot:latest
rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot-static:latest
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-01-031#72000)
8 years, 9 months
Fwd: Infra post from no-reply@rhcloud.com requires approval
by Eyal Edri
Related to the site migration?
---------- Forwarded message ----------
From: <infra-owner(a)ovirt.org>
Date: Feb 18, 2016 6:15 PM
Subject: Infra post from no-reply(a)rhcloud.com requires approval
To: <infra-owner(a)ovirt.org>
Cc:
As list administrator, your authorization is requested for the
following mailing list posting:
List: Infra(a)ovirt.org
From: no-reply(a)rhcloud.com
Subject: WARNING: Quota exceeded on wiki-ovirt.rhcloud.com
Reason: SpamAssassin identified this message as possible spam (score
3.3)
At your convenience, visit:
http://lists.ovirt.org/mailman/admindb/infra
to approve or deny the request.
---------- Forwarded message ----------
From: OpenShift guest <no-reply(a)rhcloud.com>
To: infra(a)ovirt.org
Cc:
Date: Thu, 18 Feb 2016 11:10:04 -0500
Subject: WARNING: Quota exceeded on wiki-ovirt.rhcloud.com
Disk quotas for user 847edb45aea84198838f915be6faa066 (uid 3689):
Filesystem blocks quota limit grace files quota limit
grace
/dev/mapper/EBSStore01-user_home01
18596M 0 20006M 31144 0 800k
---------- Forwarded message ----------
From: infra-request(a)ovirt.org
To:
Cc:
Date: Thu, 18 Feb 2016 11:15:33 -0500
Subject: confirm 9cfdf5334ff27f7a4f5a4093265e5035944d94b1
If you reply to this message, keeping the Subject: header intact,
Mailman will discard the held message. Do this if the message is
spam. If you reply to this message and include an Approved: header
with the list password in it, the message will be approved for posting
to the list. The Approved: header can also appear in the first line
of the body of the reply.
8 years, 9 months
https/ssl cert on www.ovirt.org
by Yedidyah Bar David
Firefox tells me:
www.ovirt.org uses an invalid security certificate. The certificate is
only valid for the following names: *.rhcloud.com, rhcloud.com (Error
code: ssl_error_bad_cert_domain)
Please handle. Thanks.
--
Didi
8 years, 9 months
