- Infra - oVirt List Archives

[JIRA] (OVIRT-2359) Set environment variable in jenkins user's env to inidicate it's a container
by Daniel Belenky (oVirt JIRA) 30 Jul '18

30 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2359?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2359: ------------------------------------- Assignee: Daniel Belenky (was: infra) > 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: Daniel Belenky > > 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)

1 0

[JIRA] (OVIRT-2382) Refactor global_setup and slave_cleanup to have different setup/cleanup flows for container slaves
by Daniel Belenky (oVirt JIRA) 30 Jul '18

30 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2382?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2382: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Refactor global_setup and slave_cleanup to have different setup/cleanup flows for container slaves > -------------------------------------------------------------------------------------------------- > > Key: OVIRT-2382 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2382 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Since setup/cleanup in a container can end up being very different than for VM/BM, it's better to have different main functions instead of skipping inside individual configuration functions. > So for example, the current main will become main_native and we'll also have main_container while main will just switch between the two. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2382) Refactor global_setup and slave_cleanup to have different setup/cleanup flows for container slaves
by Daniel Belenky (oVirt JIRA) 30 Jul '18

30 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2382?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2382: ---------------------------------- Epic Link: OVIRT-2326 > Refactor global_setup and slave_cleanup to have different setup/cleanup flows for container slaves > -------------------------------------------------------------------------------------------------- > > Key: OVIRT-2382 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2382 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > Since setup/cleanup in a container can end up being very different than for VM/BM, it's better to have different main functions instead of skipping inside individual configuration functions. > So for example, the current main will become main_native and we'll also have main_container while main will just switch between the two. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2382) Refactor global_setup and slave_cleanup to have different setup/cleanup flows for container slaves
by Daniel Belenky (oVirt JIRA) 30 Jul '18

30 Jul '18

Daniel Belenky created OVIRT-2382: ------------------------------------- Summary: Refactor global_setup and slave_cleanup to have different setup/cleanup flows for container slaves Key: OVIRT-2382 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2382 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra Since setup/cleanup in a container can end up being very different than for VM/BM, it's better to have different main functions instead of skipping inside individual configuration functions. So for example, the current main will become main_native and we'll also have main_container while main will just switch between the two. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2355) https://resources.ovirt.org/pub/ovirt-master-snapshot/iso/ is corrupted
by Ehud Yonasi (oVirt JIRA) 30 Jul '18

30 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2355?page=com.atlassian.jira.… ] Ehud Yonasi commented on OVIRT-2355: ------------------------------------ i can see under the job below how repoman stores it as master-e/7... http://jenkins.ovirt.org/job/deploy-to_ovirt-master_tested/4430/console > https://resources.ovirt.org/pub/ovirt-master-snapshot/iso/ is corrupted > ----------------------------------------------------------------------- > > Key: OVIRT-2355 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2355 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Components: Repositories Mgmt > Reporter: sbonazzo > Assignee: infra > > https://resources.ovirt.org/pub/ovirt-master-snapshot/iso/ has a broken tree > . > ├── ovirt-node-ng-installer-HEAD > ├── ovirt-node-ng-installer-master > ├── ovirt-node-ng-installer-master---- > │ └── 020204 > ├── ovirt-node-ng-installer-master----- > │ └── 20204 > ├── ovirt-node-ng-installer-master------ > │ └── 3104 > ├── ovirt-node-ng-installer-master------- > │ └── 104 > ├── ovirt-node-ng-installer-master-------- > │ └── 04 > ├── ovirt-node-ng-installer-master--------- > │ ├── 4 > │ └── 9 > ├── ovirt-node-ng-nightly-boot > └── oVirt-toolsSetup > └── 4.2-0_master.20170126155024.git44a8701.fc24 > looks like the publishing job is either not publishing isos or not working > correctly. > -- > SANDRO BONAZZOLA > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2381) Don't create /var/lib/lago/subnets
by Daniel Belenky (oVirt JIRA) 30 Jul '18

30 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2381?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2381: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Don't create /var/lib/lago/subnets > ---------------------------------- > > Key: OVIRT-2381 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2381 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Lago creates this directory by itself under lago home dir so we don't need to create it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2381) Don't create /var/lib/lago/subnets
by Daniel Belenky (oVirt JIRA) 30 Jul '18

30 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2381?page=com.atlassian.jira.… ] Daniel Belenky updated OVIRT-2381: ---------------------------------- Epic Link: OVIRT-2326 > Don't create /var/lib/lago/subnets > ---------------------------------- > > Key: OVIRT-2381 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2381 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: infra > > Lago creates this directory by itself under lago home dir so we don't need to create it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2381) Don't create /var/lib/lago/subnets
by Daniel Belenky (oVirt JIRA) 30 Jul '18

30 Jul '18

Daniel Belenky created OVIRT-2381: ------------------------------------- Summary: Don't create /var/lib/lago/subnets Key: OVIRT-2381 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2381 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra Lago creates this directory by itself under lago home dir so we don't need to create it. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2380) Mock data dirs should be $slave_home/{var/lib,/var/cache}/mock
by Daniel Belenky (oVirt JIRA) 30 Jul '18

30 Jul '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2380?page=com.atlassian.jira.… ] Daniel Belenky reassigned OVIRT-2380: ------------------------------------- Assignee: Daniel Belenky (was: infra) > Mock data dirs should be $slave_home/{var/lib,/var/cache}/mock > -------------------------------------------------------------- > > Key: OVIRT-2380 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2380 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Daniel Belenky > Assignee: Daniel Belenky > > Currently, mock data dirs that being mounted to STDCI containerized slaves is $slave_home/mock/{cache,lib} where it should be $slave_home/{var/lib,/var/cache}/mock -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0

[JIRA] (OVIRT-2380) Mock data dirs should be $slave_home/{var/lib,/var/cache}/mock
by Daniel Belenky (oVirt JIRA) 30 Jul '18

30 Jul '18

Daniel Belenky created OVIRT-2380: ------------------------------------- Summary: Mock data dirs should be $slave_home/{var/lib,/var/cache}/mock Key: OVIRT-2380 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2380 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Daniel Belenky Assignee: infra Currently, mock data dirs that being mounted to STDCI containerized slaves is $slave_home/mock/{cache,lib} where it should be $slave_home/{var/lib,/var/cache}/mock -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100090)

1 0