June 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1471) Add SSL to jenkins.ovirt.org
by Barak Korren (oVirt JIRA) 22 Jun '17

22 Jun '17

Barak Korren created OVIRT-1471: ----------------------------------- Summary: Add SSL to jenkins.ovirt.org Key: OVIRT-1471 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1471 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt Infra Reporter: Barak Korren Assignee: infra Priority: High We probably need SSL for '{{jenkins.ovirt.org}}'. That server has privileges on most stuff that is running in PHX, so better not have passwords to it be exposed to MITM attacks... -- This message was sent by Atlassian JIRA (v1000.1080.0#100052)

1 0

[JIRA] (OVIRT-1471) Add SSL to jenkins.ovirt.org
by Barak Korren (oVirt JIRA) 22 Jun '17

22 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1471?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1471: -------------------------------- Epic Link: OVIRT-403 > Add SSL to jenkins.ovirt.org > ---------------------------- > > Key: OVIRT-1471 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1471 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Priority: High > > We probably need SSL for '{{jenkins.ovirt.org}}'. That server has privileges on most stuff that is running in PHX, so better not have passwords to it be exposed to MITM attacks... -- This message was sent by Atlassian JIRA (v1000.1080.0#100052)

1 0

admin user list
by Marc Dequènes (Duck) 22 Jun '17

22 Jun '17

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --vAdlbqM5VnUgh0rrpCp5tB6gsn2xr5v32 Content-Type: multipart/mixed; boundary="Srpen3rvdd6Jg9rUjug6MvQDA9IhajUuC"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org> Message-ID: <01387b1d-0041-b599-deb2-c9db5efccc61(a)redhat.com> Subject: admin user list --Srpen3rvdd6Jg9rUjug6MvQDA9IhajUuC Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Quack, So I'm setting up admin users for infra-ansible and the associated machines to give you root access. I need some help to understand how this list is defined. In Puppet I could find 23 users (not counting the devel and system accounts). If I log onto backup I can only find 18 of them deployed. So for example account 'dfediuck' is not created while I can't find any difference with other properly created ones. It does not seem there are Puppet groups defined either. On the contrary if I log into resources I can find extra users like 'rafaelmartins' and they are nowhere to be found into Puppet. So I guess they were added manually. This makes removing users no more in the project very difficult, so I think we should audit user accounts. Could someone give a hand please? \_o< --Srpen3rvdd6Jg9rUjug6MvQDA9IhajUuC-- --vAdlbqM5VnUgh0rrpCp5tB6gsn2xr5v32 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAllLNs4ACgkQVen596wc RD9izBAAmDXovZTAmfBRBSu6Zwm3FNQz16Y3ewFxDpOEGe1U4VFIWVgoXjg6POEm 5QUjPHcwftDmUQZhyp1i1JLkMgxCzJ6JCRCgMoNKhOx0EeGecUE4tACVldbIU7aI p4/uEM5QXbd+bFrxFFEnzMA84tCyD0UXR0HKAKxjWZ1Uc40YB6N+VVW9pq+2L+lz r08DRpmr2LAQWGF0iVdjjh9HKQtASM2ezUl7cPMftn/G4S2cJ/hGJq+fa2IDohwS 9KgWOnnVU5Mfdz4IkugvdYfEycndedLOwudr/UZjG2pCDw0udYUhvUllXHmWgdI6 u94Hn/D6CdK0sHR9Eu/zhkQ4w/QELY2VnKFp/k7ORQXlT/UK4MSi0YYaTnLDB6vV wn+ceZ9N73CWoS7ZYdBGv2iy5bRZrXQQBd9uk1TkJxY65Hl412Y/zLVSV4U+cm9D ah4YQLCOqK5XYdM0csawpb8R3/mkUgx6WqfCXjp0WEHYy84yRVkcSHzKFET8LEMA MDuxkH43XvRCj6cKWzUk4ppNwYh4uDiq/BDiEde1A6nR+NsTxPccLvy1lSIYWWYy OG0Ifn6PXc2ZLh7pMb/MYWnaa8CfKjRp18Z9ZyUVeLRaTdnavtv3vJMFXQiLTvES 5s2+YrRXOU/ImBzkUKYTAdKwlCxLaHPd+uMvlOkKhQoWM2YVKHE= =BHjg -----END PGP SIGNATURE----- --vAdlbqM5VnUgh0rrpCp5tB6gsn2xr5v32--

4 5

[JIRA] (OVIRT-1468) Use CI mirrors for the slaves
by Barak Korren (oVirt JIRA) 22 Jun '17

22 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1468?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1468: ------------------------------------- [~eedri], [~ederevea] as you both talked to me about this, please add your comments here, or at least add yourselves as watchers ;) > Use CI mirrors for the slaves > ----------------------------- > > Key: OVIRT-1468 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1468 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt Infra > Reporter: Barak Korren > Assignee: infra > Labels: jenkins, mirrors, slaves > > Since we've seen that issues like OVIRT-1467 can very quickly break our entire infrastructure, it may be advisable to use out mirrors to isolate the slave VMs from the upstream repos as well, and not just the testing environments. -- This message was sent by Atlassian JIRA (v1000.1080.0#100052)

1 0

[JIRA] (OVIRT-1218) Merge infra-docs into the 'jenkins' repo
by Barak Korren (oVirt JIRA) 22 Jun '17

22 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1218?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1218: -------------------------------- Labels: documentation (was: ) > Merge infra-docs into the 'jenkins' repo > ---------------------------------------- > > Key: OVIRT-1218 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1218 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: documentation > > The 'jenkins' repo currently contains no documentation. The 'infra-docs' contains only docs, most of which deal with stuff that is in the 'jenkins' repo. > Both repos are maintained by the exact same people (The oVirt infra team). > Therefore it makes sense to unify these repos. > Pros: > * Easier discovery of docs for people looking to contribute to the 'jenkins' repo. > * Can now enforce including documentation for new features in 'jenkins' repo. > * Less repos to maintain for the infra team. -- This message was sent by Atlassian JIRA (v1000.1080.0#100052)

1 0

[JIRA] (OVIRT-1470) Create README for the 'jenkins' repo
by Barak Korren (oVirt JIRA) 22 Jun '17

22 Jun '17

Barak Korren created OVIRT-1470: ----------------------------------- Summary: Create README for the 'jenkins' repo Key: OVIRT-1470 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1470 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra The 'jenkins' repo does not have any 'readme' file ATM, this makes it very unfriendly for newcomers, especially if they find it in GitHub. We should add a '{{README.markdown}}' file that will include: # Explanation about what the repo contains # General explanation about the logic behind the repo and STD-CI with a link to infra-docs for further information. # Explanation about how to use JJB to create jobs # Explanation about how to run tests for code We should probably also include a more JJB specific README in '{{/jobs/confs}}' as well as a '{{requirements.txt}}' file to help installing JJB in virtualenv (This may be done as part of OVIRT-1466). -- This message was sent by Atlassian JIRA (v1000.1080.0#100052)

1 0

[JIRA] (OVIRT-1470) Create README for the 'jenkins' repo
by Barak Korren (oVirt JIRA) 22 Jun '17

22 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1470?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1470: -------------------------------- Epic Link: OVIRT-400 > Create README for the 'jenkins' repo > ------------------------------------ > > Key: OVIRT-1470 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1470 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: documentation, jenkins, jjb > > The 'jenkins' repo does not have any 'readme' file ATM, this makes it very unfriendly for newcomers, especially if they find it in GitHub. > We should add a '{{README.markdown}}' file that will include: > # Explanation about what the repo contains > # General explanation about the logic behind the repo and STD-CI with a link to infra-docs for further information. > # Explanation about how to use JJB to create jobs > # Explanation about how to run tests for code > We should probably also include a more JJB specific README in '{{/jobs/confs}}' as well as a '{{requirements.txt}}' file to help installing JJB in virtualenv (This may be done as part of OVIRT-1466). -- This message was sent by Atlassian JIRA (v1000.1080.0#100052)

1 0

[JIRA] (OVIRT-1469) Hypervisors flapping states in PHX engine
by Evgheni Dereveanchin (oVirt JIRA) 22 Jun '17

22 Jun '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1469?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1469: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Hypervisors flapping states in PHX engine > ----------------------------------------- > > Key: OVIRT-1469 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1469 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Hosting > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > Priority: High > > Hosts seem to be going to Non Responsive state for short periods of time in PHX. As we use local storage this does not affect VMs, yet this is not normal and needs to be fixed. -- This message was sent by Atlassian JIRA (v1000.1080.0#100052)

1 0

[JIRA] (OVIRT-1469) Hypervisors flapping states in PHX engine
by Evgheni Dereveanchin (oVirt JIRA) 22 Jun '17

22 Jun '17

Evgheni Dereveanchin created OVIRT-1469: ------------------------------------------- Summary: Hypervisors flapping states in PHX engine Key: OVIRT-1469 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1469 Project: oVirt - virtualization made easy Issue Type: Bug Components: Hosting Reporter: Evgheni Dereveanchin Assignee: infra Priority: High Hosts seem to be going to Non Responsive state for short periods of time in PHX. As we use local storage this does not affect VMs, yet this is not normal and needs to be fixed. -- This message was sent by Atlassian JIRA (v1000.1080.0#100052)

1 0

status of infra-ansible
by Marc Dequènes (Duck) 22 Jun '17

22 Jun '17

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bCKcAvMGt4BpcjOl0iE6xt6gROhkPshtG Content-Type: multipart/mixed; boundary="HuDRfGwQIqwOdThIN5AvLAXuqHbLJvJkM"; protected-headers="v1" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com> To: oVirt Infra <infra(a)ovirt.org> Message-ID: <ba28ca30-aa95-255b-6b88-8068fa0714eb(a)redhat.com> Subject: status of infra-ansible --HuDRfGwQIqwOdThIN5AvLAXuqHbLJvJkM Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Quack, I've tried to make friend with Gerrit and I was able to put the repository back into the race. So the current recipes match reality now. Please note I found and added support for using "Ansible Vault made easy". It requires adding a few line in your .gitconfig and you should enjoy full diff and merge support in a readable way from now on (see README.md). I moved over the web builder recipe to the repo (from the OSAS one). I added Quaid to the project group, Misc was already there. Plans for the future: - list of admin accounts: that's the last piece to give you full control over your own services (see "admin user list" thread); this does not change OSAS's involvement in any way - more improvements around ML/mail - configure CI (I would probably need help, volunteer?) - find contributors to Ansibilize more things and help review \_o< --HuDRfGwQIqwOdThIN5AvLAXuqHbLJvJkM-- --bCKcAvMGt4BpcjOl0iE6xt6gROhkPshtG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEcpcqg+UmRT3yiF+BVen596wcRD8FAllLPTwACgkQVen596wc RD/XWQ//ZVwZQQjeXzlggMzd7Ao+3j8zmuMqgAq3dzHDK3FBocxXed4JANCgDef1 kOiZ75gS//gRJAtYllTnXdC49jK6/nO3YWWXkQRzS89jM6eNBvDrxa9p1av8gdQh CQIOJdTxTW7k96urzl4ATTc2L7YBqKRkGUZCAU3LyjSCuB9AW9MmJogHFyWVmbLL DiJ56mPTMNP7FBRnolqw2dkD6NG0KhPSCz9N/gjdwPYm98QOSswKgB4Ua20sRW+R s/2rtVZWtPUG2bvWkMtwlabp2Lyw7Pdb+nuNbnqglsoq24pGaOm+O19kOpTQb/LK DyKRJM1CkNgh3qfSMGjLYxiWPw7Ujt8As5ylc+wzzigWGEo5XiIN5lz79Xc5S514 CMF1rrSYttfVsR/Kz/aCUjMoRN8eneHAf9fcovLhuvumF3jZejXFEjmbgLsJ/UUG ui7RQ+E5DZN17m3On8OAXUWyBeXZ9TPEGT85i8Xo7pI8kEReVOLzBtwDc9a2AkXc sKewTVpzg83Kn9ikLkbxkX7cavZve7EVTmp1znOL+vfVOQlUkCeV4pn310KC8c3L J5Js8YQp8PKb27UzHJ3LjGWFpi/crVNONSE2oViMIKupDzX5f8rMCKfDrqdeCSjN 4Ojj0OiRsSmB9vw6TF7QSkXgdC6vks3+jaQ2lzw9zc27BApyFR4= =8r6q -----END PGP SIGNATURE----- --bCKcAvMGt4BpcjOl0iE6xt6gROhkPshtG--

3 2