- Infra - oVirt List Archives

[JIRA] (OVIRT-2187) Create master suite based on FC 28
by Gal Ben Haim (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2187?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2187: -------------------------------- Status: Blocked (was: In Progress) > Create master suite based on FC 28 > ---------------------------------- > > Key: OVIRT-2187 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2187 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2260) Automate container builds for kubevirt-ansible
by Eyal Edri (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2260?page=com.atlassian.jira.… ] Eyal Edri reassigned OVIRT-2260: -------------------------------- Assignee: Gal Ben Haim (was: infra) > Automate container builds for kubevirt-ansible > ---------------------------------------------- > > Key: OVIRT-2260 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2260 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: KubeVirt-Ansible > Reporter: Eyal Edri > Assignee: Gal Ben Haim > Priority: High > > One of the pain points we see now for KubeVirt projects is not having automated builds, mostly for downstream, I suggest to try automating one project and see how it goes and if we can implement the same flow for other projects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2260) Automate container builds for kubevirt-ansible
by Eyal Edri (oVirt JIRA) 26 Jun '18

26 Jun '18

Eyal Edri created OVIRT-2260: -------------------------------- Summary: Automate container builds for kubevirt-ansible Key: OVIRT-2260 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2260 Project: oVirt - virtualization made easy Issue Type: Improvement Components: KubeVirt-Ansible Reporter: Eyal Edri Assignee: infra Priority: High One of the pain points we see now for KubeVirt projects is not having automated builds, mostly for downstream, I suggest to try automating one project and see how it goes and if we can implement the same flow for other projects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2260) Automate container builds for kubevirt-ansible
by Eyal Edri (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2260?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2260: ----------------------------- Epic Link: OVIRT-2247 > Automate container builds for kubevirt-ansible > ---------------------------------------------- > > Key: OVIRT-2260 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2260 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: KubeVirt-Ansible > Reporter: Eyal Edri > Assignee: infra > Priority: High > > One of the pain points we see now for KubeVirt projects is not having automated builds, mostly for downstream, I suggest to try automating one project and see how it goes and if we can implement the same flow for other projects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2259) Failed to add ovirt-host which runs on FC28
by Gal Ben Haim (oVirt JIRA) 26 Jun '18

26 Jun '18

Gal Ben Haim created OVIRT-2259: ----------------------------------- Summary: Failed to add ovirt-host which runs on FC28 Key: OVIRT-2259 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 Project: oVirt - virtualization made easy Issue Type: Bug Components: OST Reporter: Gal Ben Haim Assignee: infra engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm From engine.log: ``` 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER ``` Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2259) Failed to add ovirt-host which runs on FC28
by Gal Ben Haim (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2259?page=com.atlassian.jira.… ] Gal Ben Haim updated OVIRT-2259: -------------------------------- Epic Link: OVIRT-2177 > Failed to add ovirt-host which runs on FC28 > ------------------------------------------- > > Key: OVIRT-2259 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2259 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: OST > Reporter: Gal Ben Haim > Assignee: infra > > engine version: ovirt-engine-4.3.0-0.0.master.20180626082905.gitede62008318.fc28.noarch.rpm > VDSM version: vdsm-4.30.0-429.git05bfb8731.fc28.x86_64.rpm > From engine.log: > ``` > 2018-06-26 07:12:41,455-04 DEBUG [org.ovirt.engine.core.uutils.ssh.SSHClient] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Connected: 'root@lago-basic-fc-suite-master-host-1' > 2018-06-26 07:12:41,456-04 ERROR [org.ovirt.engine.core.uutils.ssh.OpenSSHUtils] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] The key algorithm 'EC' is not supported, will return null. > 2018-06-26 07:12:41,462-04 ERROR [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Failed to establish session with host 'lago-basic-fc-suite-master-host-1': null > 2018-06-26 07:12:41,462-04 WARN [org.ovirt.engine.core.bll.hostdeploy.AddVdsCommand] (default task-17) [ec8e0859-5d6e-48c9-90b9-e6ffb35ebc8a] Validation of action 'AddVds' failed for user admin@internal-authz. Reasons: VAR__ACTION__ADD,VAR__TYPE__HOST,$server lago-basic-fc-suite-master-host-1,VDS_CANNOT_CONNECT_TO_SERVER > ``` > Full engine log: https://jenkins.ovirt.org/job/ovirt-system-tests_standard-check-patch/1349/… > [~danken@redhat.com][~nsoffer@redhat.com][~mwperina] any advise? -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2258) Automate RPM builds for kubevirt-ansible
by Eyal Edri (oVirt JIRA) 26 Jun '18

26 Jun '18

Eyal Edri created OVIRT-2258: -------------------------------- Summary: Automate RPM builds for kubevirt-ansible Key: OVIRT-2258 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2258 Project: oVirt - virtualization made easy Issue Type: Improvement Components: KubeVirt-Ansible Reporter: Eyal Edri Assignee: infra Priority: High One of the pain points we see now for KubeVirt projects is not having automated builds, mostly for downstream, I suggest to try automating one project and see how it goes and if we can implement the same flow for other projects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2258) Automate RPM builds for kubevirt-ansible
by Eyal Edri (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2258?page=com.atlassian.jira.… ] Eyal Edri updated OVIRT-2258: ----------------------------- Epic Link: OVIRT-2247 > Automate RPM builds for kubevirt-ansible > ---------------------------------------- > > Key: OVIRT-2258 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2258 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: KubeVirt-Ansible > Reporter: Eyal Edri > Assignee: infra > Priority: High > > One of the pain points we see now for KubeVirt projects is not having automated builds, mostly for downstream, I suggest to try automating one project and see how it goes and if we can implement the same flow for other projects. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2254?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2254: -------------------------------- Assignee: Barak Korren (was: infra) Status: In Progress (was: To Do) > Create slave borrowing flow > --------------------------- > > Key: OVIRT-2254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2254 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: Barak Korren > > Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another Jenkins master. > h3. Acceptance criteria > # We define a borrower and a borrowing Jenkins instances. Ans support the use case where both are the same instance > # Borrowing is done by setting up a JNLP connection from the slave of the borrower instance to to borrowing instance. > # On the borrower instance: > ## We have a "borrow" job that: > ##* Takes slave requirement details, allocates a matching slaves and make it connect via JNLP to the borrowing instance > ##* If all matching slaves are already borrowed by other instances, try to call the garbage collector jobs (see below) on borrowing instances to free the slaves. > ## We have a "return" job that is called by a borrowing instance to return a slave > # On the borrowing instance > ## STDCI tries to borrow slaves from a predefined instance if not matching slaves are available locally > ## Once borrowed - slaves stay attached to the borrowing instance so they can be reused by other STDCI jobs. > ## We have a "garbage collector" job that is triggered periodically or by the borrower instance. It looks at borrowed slaves, and frees ones that were not used recently. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2254) Create slave borrowing flow
by Barak Korren (oVirt JIRA) 26 Jun '18

26 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2254?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2254: ------------------------------------- Some design details: * The "borrow" job takes the following parameters: ** The IP and JNLP port of the Jenkins that is borrowing the slave ** The JNLP secret to register to the Jenkins that is borrowing the slave ** A YAML/JSON structure with node requirements that includes: *** A *kind* field set to "{{stdci_node_req}}" *** An *apiVersion* field set to "{{1}}". *** The project *name*. *** The project *clone_ur*, *branch* and *refspec*. *** The STDCI thread *stage*, *substage*, *distro* and *arch*. *** The STDCI *runtime_requirements*. > Create slave borrowing flow > --------------------------- > > Key: OVIRT-2254 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2254 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > Create a set of jobs and groovy functions that will enable one Jenkins master to borrow slaves from another Jenkins master. > h3. Acceptance criteria > # We define a borrower and a borrowing Jenkins instances. Ans support the use case where both are the same instance > # Borrowing is done by setting up a JNLP connection from the slave of the borrower instance to to borrowing instance. > # On the borrower instance: > ## We have a "borrow" job that: > ##* Takes slave requirement details, allocates a matching slaves and make it connect via JNLP to the borrowing instance > ##* If all matching slaves are already borrowed by other instances, try to call the garbage collector jobs (see below) on borrowing instances to free the slaves. > ## We have a "return" job that is called by a borrowing instance to return a slave > # On the borrowing instance > ## STDCI tries to borrow slaves from a predefined instance if not matching slaves are available locally > ## Once borrowed - slaves stay attached to the borrowing instance so they can be reused by other STDCI jobs. > ## We have a "garbage collector" job that is triggered periodically or by the borrower instance. It looks at borrowed slaves, and frees ones that were not used recently. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0