{"action":"created","issue":{"url":"https://api.github.com/repos/CMSCompOps/WorkflowWebTools/issues/6","repository_url":"https://api.github.com/repos/CMSCompOps/WorkflowWebTools","labels_url":"https://api.github.com/repos/CMSCompOps/WorkflowWebTools/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/CMSCompOps/WorkflowWebTools/issues/6/comments","events_url":"https://api.github.com/repos/CMSCompOps/WorkflowWebTools/issues/6/events","html_url":"https://github.com/CMSCompOps/WorkflowWebTools/issues/6","id":177372609,"number":6,"title":"Testing Tool and Adjusting Parameters","user":{"login":"dabercro","id":7958662,"avatar_url":"https://avatars0.githubusercontent.com/u/7958662?v=3","gravatar_id":"","url":"https://api.github.com/users/dabercro","html_url":"https://github.com/dabercro","followers_url":"https://api.github.com/users/dabercro/followers","following_url":"https://api.github.com/users/dabercro/following{/other_user}","gists_url":"https://api.github.com/users/dabercro/gists{/gist_id}","starred_url":"https://api.github.com/users/dabercro/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/dabercro/subscriptions","organizations_url":"https://api.github.com/users/dabercro/orgs","repos_url":"https://api.github.com/users/dabercro/repos","events_url":"https://api.github.com/users/dabercro/events{/privacy}","received_events_url":"https://api.github.com/users/dabercro/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":59,"created_at":"2016-09-16T08:40:58Z","updated_at":"2017-03-07T16:43:58Z","closed_at":null,"body":"@vlimant @prozober @areinsvo @mcremone\n\nSince I don't really know everything the workflow team or Unified needs, feel free to make any comments or pull requests. We can also track the testing progress here.\n## From Jean-Roch:\n\nalthough we have a unified wired to testbed\n\nhttps://cmst2.web.cern.ch/cmst2/unified-testbed/\n\n it might be simpler to have it wired to production and run this in \"commissioning mode\".\n\n I have the feeling, looking at the example actions, that there is too many parameters passed down. Many of the them should not be needed for recovery & clone (proc version, sites, lfn, ...) since all these can be taken from the original workflow and such.\n let's tune this to what is actually needed.\n\n We should modify the recoveror module to read the action json, and be able to operate it by hand. The way I see it for a fast integration is:\n- one inputs a couple of actual actions to be taken.\n- one runs the recoveror command line to feed on this action, in test mode, convince itself that it's fine, and does apply it.\n## Viewing Actions\n\nIn order to view these actions <b>from inside the CERN network</b>, one can look at https://vocms0113.cern.ch:80/getaction. This shows actions submitted today. You can also pass a parameter \"days\" to look farther back. For example looking at https://vocms0113.cern.ch:80/getaction?days=20 will show some old testing actions.\n## Changing Parameters\n\nTo make it easier for everyone to track and comment on parameters, they are generated with these variables here:\nhttps://github.com/CMSCompOps/WorkflowWebTools/blob/d167a94ff822d7a80d3350eeadc4efe014621f75/runserver/static/js/addreason.js#L145-L184\nThe variable params results in a \"decrease\" \"same\" \"increase\" table, texts and bools are just text and \"true/false\" fields, and the opts variable results in more general radio buttons.\n\nThe site list is generated here:\nhttps://github.com/CMSCompOps/WorkflowWebTools/blob/d167a94ff822d7a80d3350eeadc4efe014621f75/runserver/templates/workflowtables.html#L19-L27 the form field is then made here https://github.com/CMSCompOps/WorkflowWebTools/blob/d167a94ff822d7a80d3350eeadc4efe014621f75/runserver/static/js/addreason.js#L231-L236\n"},"comment":{"url":"https://api.github.com/repos/CMSCompOps/WorkflowWebTools/issues/comments/284780429","html_url":"https://github.com/CMSCompOps/WorkflowWebTools/issues/6#issuecomment-284780429","issue_url":"https://api.github.com/repos/CMSCompOps/WorkflowWebTools/issues/6","id":284780429,"user":{"login":"vlimant","id":4989875,"avatar_url":"https://avatars0.githubusercontent.com/u/4989875?v=3","gravatar_id":"","url":"https://api.github.com/users/vlimant","html_url":"https://github.com/vlimant","followers_url":"https://api.github.com/users/vlimant/followers","following_url":"https://api.github.com/users/vlimant/following{/other_user}","gists_url":"https://api.github.com/users/vlimant/gists{/gist_id}","starred_url":"https://api.github.com/users/vlimant/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vlimant/subscriptions","organizations_url":"https://api.github.com/users/vlimant/orgs","repos_url":"https://api.github.com/users/vlimant/repos","events_url":"https://api.github.com/users/vlimant/events{/privacy}","received_events_url":"https://api.github.com/users/vlimant/received_events","type":"User","site_admin":false},"created_at":"2017-03-07T16:43:58Z","updated_at":"2017-03-07T16:43:58Z","body":"For the sites in drain, the acdc might require it the hard way (the data is only at that site) and therefore the site should be in the whitelist, and used in assignment if the action is set.\r\nSo assignment should go on (the use case would be that the operator knows that the site is going to come back soon and it's ok to assign it already like this leaving the agent to start submitting when the site comes back online)\r\nhttp://dabercro.web.cern.ch/dabercro/unified/showlog/?search=critical&module=GQ&limit=100\r\n\r\nis picking up the ACDC that cannot run in these situations, BTW.\r\nSo let's just not build more complication into the this. \r\n\r\n1. globalerror displays the errors the same way as in the unified errorreport\r\n1. operator/AI makes a judgement call on what to do\r\n1. the action is enacted regardless of what is it\r\n\r\nleaving the operator/AI to judge whether or not to act this way\r\n"}}
{"actor":{"display_login":"vlimant"}}