Re: [ovirt-devel] ovirt can automatically save and load username password?
Hi, I'm not quite sure if I understood the exact requests here: The first one is about remembering the username and password in the GUI login page(s). This can refer to either: (a) browser-native username and password remembering (though this one will not cause an automatic login - just an auto-fill of the user-name ans password, I believe). The browser is not offering to remember the user-name and password field values within the web-admin/user-portal login pages, as opposed to other web-sites (see e.g. http://i.imgur.com/R4RNQ3d.png). @Greg - do we know why the browser doesn't offer to remember the user-name/password for the oVirt login pages? do we have any reason to not introduce such remembering to the login pages? [not sure how upcoming SSO changes (which include a new SSO login page) will affect / be affected by that] -- or: -- (b) application-specific username and password remembering (which can lead to a fully-automated login - see http://i.imgur.com/rG7nB9P.png) - this is a feature that should be implemented and designed carefully (see [1] for some references). if this feature is important for you - please open an oVirt RFE for that (again - I am not sure if upcoming SSO changes will affect / be affected by that). The second question [2] seems to be about automating the login process using a script. This may be related to [3]. @Greg - any thoughts? Thanks, Einav [1] some threads in stackoverflow.com about implementing 'remember me': - http://stackoverflow.com/questions/549/the-definitive-guide-to-form-based-website-authentication [part II] - http://stackoverflow.com/questions/244882/what-is-the-best-way-to-implement-remember-me-for-a-website [2] translation to English of the second question (by Google Translate): The second question: I Arm board, with firefox login to ovirt publish virtual desktop every time you need to enter a user name and password you, there is no way to specify a user name and password in the script, then the call firefox when the parameters passed to it let firefox automatically go landing? THX [3] https://gerrit.ovirt.org/#/c/38017/ [userportal, webadmin: allow SSO robots to fill in the login form] this patch ^^^ solved the following BZ: Bug 1154666 - Unable to authenticate if user is using http://indeed-id.com/index.html solution for authentication. [https://bugzilla.redhat.com/show_bug.cgi?id=1154666] - Original Message - From: 395459...@qq.com To: devel devel@ovirt.org Sent: Monday, June 1, 2015 10:54:34 PM Subject: [ovirt-devel] ovirt can automatically save and load username password? My ovirt-engine installed on centos with IP 192.168.0.202, When i use 192.168.0.202 to login in with user portal,It load me to the address https://192.168.0.202/ovirt-engine/userportal/?locale=en_US#login, Now i hope the browser(firefox) remember my username and password,so next time when i enter the address https://192.168.0.202/ovirt-engine/userportal/?locale=en_US#login ,it can login automatically. 第二个疑问： 我在Arm板上，用firefox登陆到ovirt发布的虚拟桌面，每次都需要输入用户名、密码吗，有没有办法实现在脚本中指定用户名、密码，然后在调用firefox的时候把参数传递给它，让firefox自动去登陆呢？ 谢谢 395459...@qq.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] ovirt can automatically save and load username password?
Greg/Ravi please work this out in the new login form. - Original Message - From: Einav Cohen eco...@redhat.com To: 395459...@qq.com, Greg Sheremeta gsher...@redhat.com Cc: devel devel@ovirt.org Sent: Sunday, June 7, 2015 11:58:51 PM Subject: Re: [ovirt-devel] ovirt can automatically save and load usernamepassword? Hi, I'm not quite sure if I understood the exact requests here: The first one is about remembering the username and password in the GUI login page(s). This can refer to either: (a) browser-native username and password remembering (though this one will not cause an automatic login - just an auto-fill of the user-name ans password, I believe). The browser is not offering to remember the user-name and password field values within the web-admin/user-portal login pages, as opposed to other web-sites (see e.g. http://i.imgur.com/R4RNQ3d.png). @Greg - do we know why the browser doesn't offer to remember the user-name/password for the oVirt login pages? do we have any reason to not introduce such remembering to the login pages? [not sure how upcoming SSO changes (which include a new SSO login page) will affect / be affected by that] -- or: -- (b) application-specific username and password remembering (which can lead to a fully-automated login - see http://i.imgur.com/rG7nB9P.png) - this is a feature that should be implemented and designed carefully (see [1] for some references). if this feature is important for you - please open an oVirt RFE for that (again - I am not sure if upcoming SSO changes will affect / be affected by that). The second question [2] seems to be about automating the login process using a script. This may be related to [3]. @Greg - any thoughts? Thanks, Einav [1] some threads in stackoverflow.com about implementing 'remember me': - http://stackoverflow.com/questions/549/the-definitive-guide-to-form-based-website-authentication [part II] - http://stackoverflow.com/questions/244882/what-is-the-best-way-to-implement-remember-me-for-a-website [2] translation to English of the second question (by Google Translate): The second question: I Arm board, with firefox login to ovirt publish virtual desktop every time you need to enter a user name and password you, there is no way to specify a user name and password in the script, then the call firefox when the parameters passed to it let firefox automatically go landing? THX [3] https://gerrit.ovirt.org/#/c/38017/ [userportal, webadmin: allow SSO robots to fill in the login form] this patch ^^^ solved the following BZ: Bug 1154666 - Unable to authenticate if user is using http://indeed-id.com/index.html solution for authentication. [https://bugzilla.redhat.com/show_bug.cgi?id=1154666] - Original Message - From: 395459...@qq.com To: devel devel@ovirt.org Sent: Monday, June 1, 2015 10:54:34 PM Subject: [ovirt-devel] ovirt can automatically save and load username password? My ovirt-engine installed on centos with IP 192.168.0.202, When i use 192.168.0.202 to login in with user portal,It load me to the address https://192.168.0.202/ovirt-engine/userportal/?locale=en_US#login, Now i hope the browser(firefox) remember my username and password,so next time when i enter the address https://192.168.0.202/ovirt-engine/userportal/?locale=en_US#login ,it can login automatically. 第二个疑问： 我在Arm板上，用firefox登陆到ovirt发布的虚拟桌面，每次都需要输入用户名、密码吗，有没有办法实现在脚本中指定用户名、密码，然后在调用firefox的时候把参数传递给它，让firefox自动去登陆呢？ 谢谢 395459...@qq.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] gerrit+ci improvement proposal
On 06/07, Oved Ourfali wrote: - Original Message - From: Eyal Edri ee...@redhat.com To: Eli Mesika emes...@redhat.com Cc: Oved Ourfali ov...@redhat.com, devel@ovirt.org, in...@ovirt.org Sent: Sunday, June 7, 2015 9:52:15 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Eli Mesika emes...@redhat.com To: Oved Ourfali ov...@redhat.com Cc: Eyal Edri ee...@redhat.com, in...@ovirt.org, devel@ovirt.org Sent: Thursday, June 4, 2015 3:49:05 PM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Oved Ourfali ov...@redhat.com To: Eyal Edri ee...@redhat.com Cc: devel@ovirt.org, in...@ovirt.org Sent: Thursday, June 4, 2015 10:03:02 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Eyal Edri ee...@redhat.com To: Sandro Bonazzola sbona...@redhat.com Cc: in...@ovirt.org, devel@ovirt.org Sent: Thursday, June 4, 2015 9:46:40 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Eyal Edri ee...@redhat.com, Max Kovgan mkov...@redhat.com Cc: devel@ovirt.org, in...@ovirt.org Sent: Thursday, June 4, 2015 9:11:10 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal Il 03/06/2015 21:46, Eyal Edri ha scritto: - Original Message - From: Max Kovgan mkov...@redhat.com To: devel@ovirt.org Cc: in...@ovirt.org Sent: Wednesday, June 3, 2015 8:22:54 PM Subject: [ovirt-devel] gerrit+ci improvement proposal Hi everyone! We really want to have reliable and snappy CI: to allow short cycles and encourage developers to write tests. # Problem Many patches are neither ready for review nor for CI upon submission, which is OK. But running all the jobs on those patches with limited resources results in: overloaded resources, slow response time, unhappy developers. # Proposed Solution To run less jobs we know we don’t need to, thus making more resources for the jobs we need to run. We have been experimenting to make our CI stabler and quicker to respond by using gerrit flags. This has improved in both directions very well internally. Now it seems a good time to let all the oVirt projects to use this. This solution indirectly promotes reviews and quick tests - “to fail early”, yet full blown static code analysis and long tests to run “when ready”. # How it works 2 new gerrit independent flags are added to gerrit. ## CI flag Will express patch CI status. Values: * +1 CI passed * 0 CI did not run yet * -1 CI failed Permissions for setting: project maintainers (for special cases) should be able to set/override (except Jenkins). ## Workflow flag Will express patch “workflow” state. Values: * 0 Work In Progress * +1 Ready For Review * +2 Ready For Merge Permissions for setting: Owner can set +1, Project Maintainers can set +2 ## Review + CI Integration: Merging [“Submit” button to appear] will require: Review+1, CI+1, Workflow+2 Patch lifecycle now is: --- patch state |owner |reviewer |maintainer |CI tests |pass --- added/updated |- |-|- |quick|CI+1 review|Workflow+1|Review+1 |- |heavy |CI+1 merge ready |- |-|Workflow+2 |gating |CI+1 merge |- |-|merge |merge|CI+1 Changes from current workflow: Owner only adds reviewers, now owner needs to set Workflow+1 for the patch to be reviewed, and heavily auto-tested. Maintainer now needs to set Workflow+2 and wait for Submit button to appear after CI has completed running gating tests. Next step will be to automate merge the change after Workflow+2 has been set by the Maintainer and gating tests passed. ## Why now? It is elimination of waste. The sooner - the better. The solution has been used for a while and it works. Resolving the problem without gerrit involved will lead to adding
Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message - From: Eyal Edri ee...@redhat.com To: Eli Mesika emes...@redhat.com Cc: Oved Ourfali ov...@redhat.com, devel@ovirt.org, in...@ovirt.org Sent: Sunday, June 7, 2015 9:52:15 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Eli Mesika emes...@redhat.com To: Oved Ourfali ov...@redhat.com Cc: Eyal Edri ee...@redhat.com, in...@ovirt.org, devel@ovirt.org Sent: Thursday, June 4, 2015 3:49:05 PM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Oved Ourfali ov...@redhat.com To: Eyal Edri ee...@redhat.com Cc: devel@ovirt.org, in...@ovirt.org Sent: Thursday, June 4, 2015 10:03:02 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Eyal Edri ee...@redhat.com To: Sandro Bonazzola sbona...@redhat.com Cc: in...@ovirt.org, devel@ovirt.org Sent: Thursday, June 4, 2015 9:46:40 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Eyal Edri ee...@redhat.com, Max Kovgan mkov...@redhat.com Cc: devel@ovirt.org, in...@ovirt.org Sent: Thursday, June 4, 2015 9:11:10 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal Il 03/06/2015 21:46, Eyal Edri ha scritto: - Original Message - From: Max Kovgan mkov...@redhat.com To: devel@ovirt.org Cc: in...@ovirt.org Sent: Wednesday, June 3, 2015 8:22:54 PM Subject: [ovirt-devel] gerrit+ci improvement proposal Hi everyone! We really want to have reliable and snappy CI: to allow short cycles and encourage developers to write tests. # Problem Many patches are neither ready for review nor for CI upon submission, which is OK. But running all the jobs on those patches with limited resources results in: overloaded resources, slow response time, unhappy developers. # Proposed Solution To run less jobs we know we don’t need to, thus making more resources for the jobs we need to run. We have been experimenting to make our CI stabler and quicker to respond by using gerrit flags. This has improved in both directions very well internally. Now it seems a good time to let all the oVirt projects to use this. This solution indirectly promotes reviews and quick tests - “to fail early”, yet full blown static code analysis and long tests to run “when ready”. # How it works 2 new gerrit independent flags are added to gerrit. ## CI flag Will express patch CI status. Values: * +1 CI passed * 0 CI did not run yet * -1 CI failed Permissions for setting: project maintainers (for special cases) should be able to set/override (except Jenkins). ## Workflow flag Will express patch “workflow” state. Values: * 0 Work In Progress * +1 Ready For Review * +2 Ready For Merge Permissions for setting: Owner can set +1, Project Maintainers can set +2 ## Review + CI Integration: Merging [“Submit” button to appear] will require: Review+1, CI+1, Workflow+2 Patch lifecycle now is: --- patch state |owner |reviewer |maintainer |CI tests |pass --- added/updated |- |-|- |quick|CI+1 review|Workflow+1|Review+1 |- |heavy |CI+1 merge ready |- |-|Workflow+2 |gating |CI+1 merge |- |-|merge |merge|CI+1 Changes from current workflow: Owner only adds reviewers, now owner needs to set Workflow+1 for the patch to be reviewed, and heavily auto-tested. Maintainer now needs to set Workflow+2 and wait for Submit button to appear after CI has completed running gating tests. Next step will be to automate merge the change after Workflow+2 has been set by the Maintainer and gating tests passed. ## Why now? It is elimination of waste. The sooner - the better. The solution has been used for a while and it works. Resolving the problem without gerrit involved will lead to adding unreliable code into jobs, and will still be prone to problems: Just recently, 3d ago we’ve tried detecting what to run from jenkins relying only on gerrit comments so that upon Verified+1,
Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message - From: Eli Mesika emes...@redhat.com To: Oved Ourfali ov...@redhat.com Cc: Eyal Edri ee...@redhat.com, in...@ovirt.org, devel@ovirt.org Sent: Thursday, June 4, 2015 3:49:05 PM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Oved Ourfali ov...@redhat.com To: Eyal Edri ee...@redhat.com Cc: devel@ovirt.org, in...@ovirt.org Sent: Thursday, June 4, 2015 10:03:02 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Eyal Edri ee...@redhat.com To: Sandro Bonazzola sbona...@redhat.com Cc: in...@ovirt.org, devel@ovirt.org Sent: Thursday, June 4, 2015 9:46:40 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Eyal Edri ee...@redhat.com, Max Kovgan mkov...@redhat.com Cc: devel@ovirt.org, in...@ovirt.org Sent: Thursday, June 4, 2015 9:11:10 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal Il 03/06/2015 21:46, Eyal Edri ha scritto: - Original Message - From: Max Kovgan mkov...@redhat.com To: devel@ovirt.org Cc: in...@ovirt.org Sent: Wednesday, June 3, 2015 8:22:54 PM Subject: [ovirt-devel] gerrit+ci improvement proposal Hi everyone! We really want to have reliable and snappy CI: to allow short cycles and encourage developers to write tests. # Problem Many patches are neither ready for review nor for CI upon submission, which is OK. But running all the jobs on those patches with limited resources results in: overloaded resources, slow response time, unhappy developers. # Proposed Solution To run less jobs we know we don’t need to, thus making more resources for the jobs we need to run. We have been experimenting to make our CI stabler and quicker to respond by using gerrit flags. This has improved in both directions very well internally. Now it seems a good time to let all the oVirt projects to use this. This solution indirectly promotes reviews and quick tests - “to fail early”, yet full blown static code analysis and long tests to run “when ready”. # How it works 2 new gerrit independent flags are added to gerrit. ## CI flag Will express patch CI status. Values: * +1 CI passed * 0 CI did not run yet * -1 CI failed Permissions for setting: project maintainers (for special cases) should be able to set/override (except Jenkins). ## Workflow flag Will express patch “workflow” state. Values: * 0 Work In Progress * +1 Ready For Review * +2 Ready For Merge Permissions for setting: Owner can set +1, Project Maintainers can set +2 ## Review + CI Integration: Merging [“Submit” button to appear] will require: Review+1, CI+1, Workflow+2 Patch lifecycle now is: --- patch state |owner |reviewer |maintainer |CI tests |pass --- added/updated |- |-|- |quick|CI+1 review|Workflow+1|Review+1 |- |heavy |CI+1 merge ready |- |-|Workflow+2 |gating |CI+1 merge |- |-|merge |merge|CI+1 Changes from current workflow: Owner only adds reviewers, now owner needs to set Workflow+1 for the patch to be reviewed, and heavily auto-tested. Maintainer now needs to set Workflow+2 and wait for Submit button to appear after CI has completed running gating tests. Next step will be to automate merge the change after Workflow+2 has been set by the Maintainer and gating tests passed. ## Why now? It is elimination of waste. The sooner - the better. The solution has been used for a while and it works. Resolving the problem without gerrit involved will lead to adding unreliable code into jobs, and will still be prone to problems: Just recently, 3d ago we’ve tried detecting what to run from jenkins relying only on gerrit comments so that upon Verified+1, we’d run the job. We could not use “Review+1”, because it makes no sense at all, so we left the job to set Verified+1. Meaning - re-trigger itself immediately more than 1 times. Jenkins and its visitors very unhappy, and we had to stop those jobs, clean up the queue, and spam developers. ## OK OK OK. Now what? Now we want your
Re: [ovirt-devel] gerrit+ci improvement proposal
On Jun 7, 2015 10:00 AM, Eyal Edri ee...@redhat.com wrote: - Original Message - From: Oved Ourfali ov...@redhat.com To: Eyal Edri ee...@redhat.com Cc: in...@ovirt.org, devel@ovirt.org Sent: Sunday, June 7, 2015 9:55:56 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Eyal Edri ee...@redhat.com To: Eli Mesika emes...@redhat.com Cc: Oved Ourfali ov...@redhat.com, devel@ovirt.org, in...@ovirt.org Sent: Sunday, June 7, 2015 9:52:15 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Eli Mesika emes...@redhat.com To: Oved Ourfali ov...@redhat.com Cc: Eyal Edri ee...@redhat.com, in...@ovirt.org, devel@ovirt.org Sent: Thursday, June 4, 2015 3:49:05 PM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Oved Ourfali ov...@redhat.com To: Eyal Edri ee...@redhat.com Cc: devel@ovirt.org, in...@ovirt.org Sent: Thursday, June 4, 2015 10:03:02 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Eyal Edri ee...@redhat.com To: Sandro Bonazzola sbona...@redhat.com Cc: in...@ovirt.org, devel@ovirt.org Sent: Thursday, June 4, 2015 9:46:40 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Eyal Edri ee...@redhat.com, Max Kovgan mkov...@redhat.com Cc: devel@ovirt.org, in...@ovirt.org Sent: Thursday, June 4, 2015 9:11:10 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal Il 03/06/2015 21:46, Eyal Edri ha scritto: - Original Message - From: Max Kovgan mkov...@redhat.com To: devel@ovirt.org Cc: in...@ovirt.org Sent: Wednesday, June 3, 2015 8:22:54 PM Subject: [ovirt-devel] gerrit+ci improvement proposal Hi everyone! We really want to have reliable and snappy CI: to allow short cycles and encourage developers to write tests. # Problem Many patches are neither ready for review nor for CI upon submission, which is OK. But running all the jobs on those patches with limited resources results in: overloaded resources, slow response time, unhappy developers. # Proposed Solution To run less jobs we know we don’t need to, thus making more resources for the jobs we need to run. We have been experimenting to make our CI stabler and quicker to respond by using gerrit flags. This has improved in both directions very well internally. Now it seems a good time to let all the oVirt projects to use this. This solution indirectly promotes reviews and quick tests - “to fail early”, yet full blown static code analysis and long tests to run “when ready”. # How it works 2 new gerrit independent flags are added to gerrit. ## CI flag Will express patch CI status. Values: * +1 CI passed * 0 CI did not run yet * -1 CI failed Permissions for setting: project maintainers (for special cases) should be able to set/override (except Jenkins). ## Workflow flag Will express patch “workflow” state. Values: * 0 Work In Progress * +1 Ready For Review * +2 Ready For Merge Permissions for setting: Owner can set +1, Project Maintainers can set +2 ## Review + CI Integration: Merging [“Submit” button to appear] will require: Review+1, CI+1, Workflow+2 Patch lifecycle now is: --- patch state |owner |reviewer |maintainer |CI tests |pass --- added/updated |- |- |- |quick |CI+1 review |Workflow+1|Review+1 |- |heavy |CI+1 merge ready |- |- |Workflow+2 |gating |CI+1 merge |- |- |merge |merge |CI+1 Changes from current workflow: Owner only adds reviewers, now owner needs to set Workflow+1 for the patch
Re: [ovirt-devel] gerrit+ci improvement proposal
- Original Message - From: Oved Ourfali ov...@redhat.com To: Eyal Edri ee...@redhat.com Cc: in...@ovirt.org, devel@ovirt.org Sent: Sunday, June 7, 2015 9:55:56 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Eyal Edri ee...@redhat.com To: Eli Mesika emes...@redhat.com Cc: Oved Ourfali ov...@redhat.com, devel@ovirt.org, in...@ovirt.org Sent: Sunday, June 7, 2015 9:52:15 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Eli Mesika emes...@redhat.com To: Oved Ourfali ov...@redhat.com Cc: Eyal Edri ee...@redhat.com, in...@ovirt.org, devel@ovirt.org Sent: Thursday, June 4, 2015 3:49:05 PM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Oved Ourfali ov...@redhat.com To: Eyal Edri ee...@redhat.com Cc: devel@ovirt.org, in...@ovirt.org Sent: Thursday, June 4, 2015 10:03:02 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Eyal Edri ee...@redhat.com To: Sandro Bonazzola sbona...@redhat.com Cc: in...@ovirt.org, devel@ovirt.org Sent: Thursday, June 4, 2015 9:46:40 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: Eyal Edri ee...@redhat.com, Max Kovgan mkov...@redhat.com Cc: devel@ovirt.org, in...@ovirt.org Sent: Thursday, June 4, 2015 9:11:10 AM Subject: Re: [ovirt-devel] gerrit+ci improvement proposal Il 03/06/2015 21:46, Eyal Edri ha scritto: - Original Message - From: Max Kovgan mkov...@redhat.com To: devel@ovirt.org Cc: in...@ovirt.org Sent: Wednesday, June 3, 2015 8:22:54 PM Subject: [ovirt-devel] gerrit+ci improvement proposal Hi everyone! We really want to have reliable and snappy CI: to allow short cycles and encourage developers to write tests. # Problem Many patches are neither ready for review nor for CI upon submission, which is OK. But running all the jobs on those patches with limited resources results in: overloaded resources, slow response time, unhappy developers. # Proposed Solution To run less jobs we know we don’t need to, thus making more resources for the jobs we need to run. We have been experimenting to make our CI stabler and quicker to respond by using gerrit flags. This has improved in both directions very well internally. Now it seems a good time to let all the oVirt projects to use this. This solution indirectly promotes reviews and quick tests - “to fail early”, yet full blown static code analysis and long tests to run “when ready”. # How it works 2 new gerrit independent flags are added to gerrit. ## CI flag Will express patch CI status. Values: * +1 CI passed * 0 CI did not run yet * -1 CI failed Permissions for setting: project maintainers (for special cases) should be able to set/override (except Jenkins). ## Workflow flag Will express patch “workflow” state. Values: * 0 Work In Progress * +1 Ready For Review * +2 Ready For Merge Permissions for setting: Owner can set +1, Project Maintainers can set +2 ## Review + CI Integration: Merging [“Submit” button to appear] will require: Review+1, CI+1, Workflow+2 Patch lifecycle now is: --- patch state |owner |reviewer |maintainer |CI tests |pass --- added/updated |- |-|- |quick|CI+1 review|Workflow+1|Review+1 |- |heavy |CI+1 merge ready |- |-|Workflow+2 |gating |CI+1 merge |- |-|merge |merge|CI+1 Changes from current workflow: Owner only adds reviewers, now owner needs to set Workflow+1 for the patch to be reviewed, and heavily auto-tested. Maintainer now needs to set Workflow+2 and wait for Submit button to appear after CI has completed running gating tests. Next step will be to automate merge the change after Workflow+2 has been set by the Maintainer and gating tests passed. ## Why now?
[ovirt-devel] ovirt can automatically save and load username password?
My ovirt-engine installed on centos with IP 192.168.0.202, When i use 192.168.0.202 to login in with user portal,It load me to the address https://192.168.0.202/ovirt-engine/userportal/?locale=en_US#login, Now i hope the browser(firefox) remember my username and password,so next time when i enter the address https://192.168.0.202/ovirt-engine/userportal/?locale=en_US#login,it can login automatically. 第二个疑问： 我在Arm板上，用firefox登陆到ovirt发布的虚拟桌面，每次都需要输入用户名、密码吗，有没有办法实现在脚本中指定用户名、密码，然后在调用firefox的时候把参数传递给它，让firefox自动去登陆呢？ 谢谢 395459...@qq.com ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
