December 2016 - Infra - oVirt List Archives

[JIRA] (OVIRT-866) 54606 infra-support
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-866?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-866: -------------------------------------------- > 54606 infra-support > ------------------- > > Key: OVIRT-866 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-866 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: m.kos(a)lycos.com > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-863) Delivery Notification, ID 1285359132561
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-863?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-863: -------------------------------------------- > Delivery Notification, ID 1285359132561 > --------------------------------------- > > Key: OVIRT-863 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-863 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: FedEx Standard Overnight > Assignee: infra > > Hello, > We could not deliver your parcel. You can review complete details of your order in the find attached. > Letizia Nenninger - Area Manager FedEx , CA > Sincerely. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-868) Delivery Notification, ID 837693
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-868?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-868: -------------------------------------------- > Delivery Notification, ID 837693 > -------------------------------- > > Key: OVIRT-868 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-868 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: FedEx Standard Overnight > Assignee: infra > > Hello, > We could not deliver your parcel. Please, open email attachment to print shipment label. > Valencia Lindbeck - Area Manager FedEx , CA > Thank you for choosing FedEx. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-867) Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing!
by Evgheni Dereveanchin (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-867?page=com.atlassian.jira.p… ] Evgheni Dereveanchin commented on OVIRT-867: -------------------------------------------- [~sbonazzo(a)redhat.com] is this issue still happening? If yes - can we specify several mirrors for this job as we do for mock configs? > Re: [oVirt Jenkins] repos_3.6_check-closure_el7_merged - Build # 92 - Still Failing! > ------------------------------------------------------------------------------------ > > Key: OVIRT-867 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-867 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: sbonazzo > Assignee: Evgheni Dereveanchin > > *00:01:53.955* Can't download or revert repomd.xml for > check-epel-el7*00:01:53.955* Some dependencies may not be complete for > this repository*00:01:53.956* Run as root to get all dependencies or > use -t to enable a user temp cache > Can you check? looks like it's not possible to update local cache of metadata. > On Fri, Nov 25, 2016 at 1:07 PM, <jenkins(a)jenkins.phx.ovirt.org> wrote: > > Project: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/ > > Build: http://jenkins.ovirt.org/job/repos_3.6_check-closure_el7_merged/92/ > > Build Number: 92 > > Build Status: Still Failing > > Triggered By: Started by user Sandro Bonazzola > > > > ------------------------------------- > > Changes Since Last Success: > > ------------------------------------- > > Changes for Build #89 > > [Eyal Edri] deploy ovirt-engine-cli 3.6 to 4.0 and master repos as well > > > > [Yedidyah Bar David] master_upgrade_from_master: Upgrade to self instead > > of snapshot > > > > > > Changes for Build #90 > > No changes > > > > Changes for Build #91 > > No changes > > > > Changes for Build #92 > > No changes > > > > > > > > ----------------- > > Failed Tests: > > ----------------- > > No tests ran. > > > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Sandro Bonazzola > Better technology. Faster innovation. Powered by community collaboration. > See how it works at redhat.com -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-895) mailing list memberships reminder - do we need that?
by Evgheni Dereveanchin (oVirt JIRA) 01 Dec '16

01 Dec '16

Evgheni Dereveanchin created OVIRT-895: ------------------------------------------ Summary: mailing list memberships reminder - do we need that? Key: OVIRT-895 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-895 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Evgheni Dereveanchin Assignee: infra Priority: Low I'm subscribed to a bunch of lists and every month I get membership reminder emails. Do we have them for a reason? If not - I'd like to disable them (can be done per-list in the settings or globally across the Mailman instance) -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-891) Add support for verification / testing of containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-891?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-891: ------------------------------------ {quote} You don't see a place to verify anything before the artifacts build? such as Validity of DockerFiles? {quote} You mean something like checking for syntax? Like you check PyFlakes and PEP8 from python files? This just goes in check_patch.sh, nothing special here... (Not sure anyone made such a tool for Dockerfiles yet) > Add support for verification / testing of containers in standard CI > ------------------------------------------------------------------- > > Key: OVIRT-891 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-891 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > > From check-patch scripts, verifying docker files to running system test suit on the new image. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-891) Add support for verification / testing of containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-891?page=com.atlassian.jira.p… ] Barak Korren edited comment on OVIRT-891 at 12/1/16 12:05 PM: -------------------------------------------------------------- {quote} You don't see a place to verify anything before the artifacts build? such as Validity of DockerFiles? {quote} You mean something like checking for syntax? Like you check PyFlakes and PEP8 for python files? This just goes in check_patch.sh, nothing special here... (Not sure anyone made such a tool for Dockerfiles yet) was (Author: bkorren(a)redhat.com) {quote} You don't see a place to verify anything before the artifacts build? such as Validity of DockerFiles? {quote} You mean something like checking for syntax? Like you check PyFlakes and PEP8 from python files? This just goes in check_patch.sh, nothing special here... (Not sure anyone made such a tool for Dockerfiles yet) > Add support for verification / testing of containers in standard CI > ------------------------------------------------------------------- > > Key: OVIRT-891 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-891 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > > From check-patch scripts, verifying docker files to running system test suit on the new image. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-894) Add support of sercers and credentials in Standard-CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

Barak Korren created OVIRT-894: ---------------------------------- Summary: Add support of sercers and credentials in Standard-CI Key: OVIRT-894 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-894 Project: oVirt - virtualization made easy Issue Type: New Feature Components: General Reporter: Barak Korren Assignee: infra Some task we'd like to carry out in Standard-CI require credentials. Examples for such tasks include: # Publishing artifacts to repositories (E.g containers to Dokcerhub, puppet code to Puppetmaster) # Launching remote processes (Check code with remote services) While Jenkins supports storing and managing secret data, we did not enable a way to use this capability from Standard-CI so far. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-890) Add support to publish containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-890?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-890: ------------------------------------ It shouldn't really matter _where_ we publish. As I see it there are two main option to publish _anything_ from standard CI: # Have build_artifacts.sh put it in "exported_artifacts" and then have "the system" publish it to where it needs to go - this is what the experimental flow is doing for example for RPMs. # Publish directly from build_artifacts.sh It should be obvious that solution #2 is more flexible and will require less maintenance from us in the long run, but it has a couple of issues: # For publishing typically some credentials are needed # The decision where to publish ends up being made at the discretion of the developer, as opposed to on an environment level. I don't think #2 is really an issue. WRT #1, this is something we've encountered before, and perhaps we should solve it by adding support for credentials and secrets in Standard CI (OVIRT-894). > Add support to publish containers in standard CI > ------------------------------------------------ > > Key: OVIRT-890 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-890 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: containers, docker, standard-ci > > Mostly likely to Dockerhub or OpenShift registry. > We'll need a pet project to try out the various options. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-894) Add support of sercers and credentials in Standard-CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-894?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-894: ------------------------------- Epic Link: OVIRT-400 > Add support of sercers and credentials in Standard-CI > ----------------------------------------------------- > > Key: OVIRT-894 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-894 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: General > Reporter: Barak Korren > Assignee: infra > Labels: standard-ci > > Some task we'd like to carry out in Standard-CI require credentials. Examples for such tasks include: > # Publishing artifacts to repositories (E.g containers to Dokcerhub, puppet code to Puppetmaster) > # Launching remote processes (Check code with remote services) > While Jenkins supports storing and managing secret data, we did not enable a way to use this capability from Standard-CI so far. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0