[ 
https://ovirt-jira.atlassian.net/browse/OVIRT-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=27531#comment-27531
 ] 

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-de...@lists.fedorahosted.org/thread/LZZPJ534ZDRD7YYFDC3BXDUVVPF5B735/
>  )
> 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)
_______________________________________________
Infra mailing list
Infra@ovirt.org
http://lists.ovirt.org/mailman/listinfo/infra

Reply via email to