- Infra - oVirt List Archives

[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)
by Greg Sheremeta (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1170: --------------------------------------- Nod, I'll test it. > add option to disable networking (or have it off by default) > ------------------------------------------------------------ > > Key: OVIRT-1170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Greg Sheremeta > Assignee: infra > > Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.… ) > In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail. -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Michal Skrivanek (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1154: ----------------------------------------- Hmm, I suppose CR+1 from a maintainer is a good idea anyway. Though I'm not sure whther the actual list of maintainers is truly up to date and easy to get....but if it is it does sound good enough if the previously mentioned method of git log is not feasible > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Barak Korren (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1154: ------------------------------------- We can use other things - maybe a +1 from a maintainer? > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Michal Skrivanek (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Michal Skrivanek commented on OVIRT-1154: ----------------------------------------- if you by "confirm" mean something like those "ci build" comments then please no. I never remember what's the right abracadabra magic word....it just sucks > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)
by Barak Korren (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1170: ------------------------------------- Oh sorry that should have been: {code} rm /etc/resolv.conf {code} Or perhaps more safely: {code} truncate /etc/resolv.conf {code} This should be safe enough, and will block anything that does not use direct IP addresses to access outside resources. > add option to disable networking (or have it off by default) > ------------------------------------------------------------ > > Key: OVIRT-1170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Greg Sheremeta > Assignee: infra > > Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.… ) > In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail. -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mechanism
by Barak Korren (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Summary: Improve and automate the jenkins-whitelist mechanism (was: Improve and automate the jenkins-whitelist mecahnism) > Improve and automate the jenkins-whitelist mechanism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1154) Improve and automate the jenkins-whitelist mecahnism
by Barak Korren (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1154?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1154: -------------------------------- Summary: Improve and automate the jenkins-whitelist mecahnism (was: Make jenkins-whitelist use Gerrit groups) > Improve and automate the jenkins-whitelist mecahnism > ---------------------------------------------------- > > Key: OVIRT-1154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1154 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > > Right now our white list is based on a text file with email addresses in it. Its kinda silly when we already have lists and groups of users in Gerrit. > Some suggestions: > * make any members of a project's "maintainers" group automatically white-listed > * make a specific group for other white-listed people -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1170) add option to disable networking (or have it off by default)
by Greg Sheremeta (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.… ] Greg Sheremeta commented on OVIRT-1170: --------------------------------------- I'm not familiar with what removing /etc/hosts would do (I would have guessed nothing helpful) Shutting off access to known problematic domains is helpful, but won't catch when we pull in new dependencies that access domains we don't know about. So I'm afraid this won't really help anything. > add option to disable networking (or have it off by default) > ------------------------------------------------------------ > > Key: OVIRT-1170 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1170 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Greg Sheremeta > Assignee: infra > > Add option to disable networking (or have it off by default). Basically, we want to prevent a job from accessing the internet if we want repeatable builds and/or are doing a downstream build somewhere else. Other/downstream build environments often have networking off. Copr has an option: (See: https://lists.fedorahosted.org/archives/list/copr-devel@lists.fedorahosted.… ) > In particular, the ovirt-engine-nodejs-modules build-artifacts job *tries* to stay offline, but an evil node module called 'phantomjs' connects to the internet in a post-offline-install hook. I'd like the option to disallow that and have the build fail. -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1176) [jenkins-whitelist] add user to jenkins whitelist
by Shlomo Ben David (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1176?page=com.atlassian.jira.… ] Shlomo Ben David updated OVIRT-1176: ------------------------------------ Resolution: Fixed Status: Done (was: To Do) > [jenkins-whitelist] add user to jenkins whitelist > ------------------------------------------------- > > Key: OVIRT-1176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1176 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Shlomo Ben David > > Adding infra-support to open a ticket > On Tue, Feb 21, 2017 at 6:38 PM, Denis Chaplygin <dchaplyg(a)redhat.com> > wrote: > > Hello! > > > > I suppose i should be in whitelist: > > > > Patch Set 1: > > > > No Builds Executed > > > > http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_c > > heck-patch-el7-x86_64/139/ : To avoid overloading the infrastructure, a > > whitelist for > > running gerrit triggered jobs has been set in place, if > > you feel like you should be in it, please contact infra at > > ovirt dot org. > > > > > > http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_c > > heck-patch-fc25-x86_64/25/ : To avoid overloading the infrastructure, a > > whitelist for > > running gerrit triggered jobs has been set in place, if > > you feel like you should be in it, please contact infra at > > ovirt dot org. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0

[JIRA] (OVIRT-1176) [jenkins-whitelist] add user to jenkins whitelist
by Shlomo Ben David (oVirt JIRA) 21 Feb '17

21 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1176?page=com.atlassian.jira.… ] Shlomo Ben David updated OVIRT-1176: ------------------------------------ Summary: [jenkins-whitelist] add user to jenkins whitelist (was: Re: Jenkins whitelist) > [jenkins-whitelist] add user to jenkins whitelist > ------------------------------------------------- > > Key: OVIRT-1176 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1176 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Gil Shinar > Assignee: Shlomo Ben David > > Adding infra-support to open a ticket > On Tue, Feb 21, 2017 at 6:38 PM, Denis Chaplygin <dchaplyg(a)redhat.com> > wrote: > > Hello! > > > > I suppose i should be in whitelist: > > > > Patch Set 1: > > > > No Builds Executed > > > > http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_c > > heck-patch-el7-x86_64/139/ : To avoid overloading the infrastructure, a > > whitelist for > > running gerrit triggered jobs has been set in place, if > > you feel like you should be in it, please contact infra at > > ovirt dot org. > > > > > > http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_master_c > > heck-patch-fc25-x86_64/25/ : To avoid overloading the infrastructure, a > > whitelist for > > running gerrit triggered jobs has been set in place, if > > you feel like you should be in it, please contact infra at > > ovirt dot org. > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > -- This message was sent by Atlassian JIRA (v1000.773.2#100032)

1 0