[JIRA] (OVIRT-2361) Remove 4.1 tested repo
by Ehud Yonasi (oVirt JIRA)
Ehud Yonasi created OVIRT-2361:
----------------------------------
Summary: Remove 4.1 tested repo
Key: OVIRT-2361
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2361
Project: oVirt - virtualization made easy
Issue Type: Outage
Reporter: Ehud Yonasi
Assignee: infra
current utilization is 93G under: /srv/resources/repos/ovirt/tested/4.1
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
6 years, 5 months
[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env
to inidicate it's a container
by Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jir... ]
Daniel Belenky edited comment on OVIRT-2359 at 7/22/18 11:11 AM:
-----------------------------------------------------------------
But we're off-topic for this ticket. The task here is to have some indication we're inside a container. I think mounting a file in read-only mode with some system infomration about stdci in /etc/stdci is a good solution. WDYT?
was (Author: dbelenky(a)redhat.com):
But we're off-topic for this ticket. The task here is to have some indication we're inside a container. I think mounting a file in read-only mode that some system infomration about stdci in /etc/stdci is a good solution. WDYT?
> Set environment variable in jenkins user's env to inidicate it's a container
> ----------------------------------------------------------------------------
>
> Key: OVIRT-2359
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Reporter: Daniel Belenky
> Assignee: infra
>
> We need to set a variable under the jenkins user that will indicate we're running inside a container.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
6 years, 5 months
[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env
to inidicate it's a container
by Daniel Belenky (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jir... ]
Daniel Belenky commented on OVIRT-2359:
---------------------------------------
I think that systemd drops environment information by design in order to ensure clean environment for every process it starts. Maybe there is a workaround but what's wrong with EnvironmentFiles? You'll have to provide this infomration to systemd anyway, so by having a well know directory in a host with N systemd environment files, one for every container, you have all the needed information you need to run them.
> Set environment variable in jenkins user's env to inidicate it's a container
> ----------------------------------------------------------------------------
>
> Key: OVIRT-2359
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2359
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Reporter: Daniel Belenky
> Assignee: infra
>
> We need to set a variable under the jenkins user that will indicate we're running inside a container.
--
This message was sent by Atlassian Jira
(v1001.0.0-SNAPSHOT#100090)
6 years, 5 months