Þ•ÇT_Œ& & &&+& E&S&)b&OŒ&OÜ&,,'Y',w'"¤'‡Ç'nO(w¾( 6)@)V)^)t)„) )Žª)]9* —*¤*µ*¾* Á* Ë*×*&à* ++ (+72+#j+0Ž+¿+Ü+Aò+|4,±, Í,Û,ö, ü,-- 7-4E-*z-3¥-FÙ-A .tb.5×. / /"/=/U/k/‚/ /$§/Ì/DÕ/L0g0m0 r00š0‚¯0v21p©1{2–2±2 Ç2Ó2è2 ý23œ63Ó3ó304 44 B4P4X4j4ˆ4¦4µ4Ë4GÚ4"595ëQ5æ=6$7%87^7c7i7‡7 7-7 Ë7Õ7å7$ø79-9J9 Q9^9|9D’9×9ò9::!:?:øQ:J;\;r;;ª;Æ;Û;ô;ù; < < "<",<O<U<h<2o<5¢<Ø<ß<õ< =,!=WN=¦=Â=È= Þ=Öì=>Ã> ??#?>? B?N?]?|?Œ? •?£? ¹?Æ?Û?ó?@ @ @**@#U@ y@‡@š@«@¿@äÄ@ß©A‰BB¨B¾B ×B+ãBC'C•WFÔWmX$‰XH®XÌ÷XØÄYWZ õZÿZ[ %[ 2[ @[N[ ][=i[J§[ò[\(\@\Y\8^\—\ ­]&»]â]&ý]3$^X^9q^#«^7Ï^_"_ 8_ Y_#e_2‰_&¼_,ã_ `` !`/`B`T` h`t`F{`GÂ`| a@‡a¬Èb_ucUÕc1+dC]d6¡d@Øde+el:e8§eKàe ,f.6feftfzf)•ft¿f4g;g'@ghgng tgV•gìg h&h‡܇+à‡ ˆ0ˆ0Dˆuˆ|ˆƒˆ¢ˆœ©ˆ F‰ P‰q‰‰Œ¬‰9ŠUŠ \ŠiŠ |Š‰Š_œŠüŠ ‹‹/‹ 6‹C‹\‹u‹ Ž‹˜‹ ¨‹ µ‹‹á‹ è‹õ‹ŒŒ +ŒQ8ŒŠŒŒ!°ŒÒŒ ÙŒæŒ'ùŒ!!5Wj z„ ‹˜ Ÿ¬ÁŸà €Ž Ž —Ž ¢Ž­ŽÊŽÑŽäŽ'÷Ž- M Zdt“šª ºoÇ 7„DÉãÿ9‘sL‘“À‘T’l’<~’»’6Ô’' ”3”O”!h”Š””¶”ϔ┠é”ó” ú” •• • "•/•6•L•h• „•Ž••• ¨•µ•Ë• Û• å•ò• – – – 9– F–"S–v–c•–!ù–l—ˆ—¤—À—KÙ—.%˜LT˜*¡˜0̘iý˜!g™H‰™¦Ò™²yšH,› u›‚›’› ¨› µ› Û Ñ› Þ›<ë›<(œeœxœ—œªœ½œ3Äœÿøœ øž#ž$<ž3až•ž?«žëž- Ÿ8ŸNŸaŸ zŸ(‡Ÿ4°Ÿ$åŸ.   9 F J ] s ‰  Ÿ ­ 9´ Kî u:¡J°¡¥û¢g¡£6 ¤$@¤0e¤!–¤6¸¤ï¤¥W¥2p¥?£¥ ã¥+í¥ ¦&¦-¦B¦r[¦ΦÕ¦ܦû¦§ §]*§ˆ§¢§¾§اò§ ¨¨ )¨$3¨X¨n¨‚¨ †¨¨¬¨³¨è˨Þ¨£ã÷àJûcßr’c_ŽéukÁIŠ¹oe*ÿ óòƒZﻧ}´%—Gƒo¢f:[®Ø@N Ë/fõŸXÞ8–,“PIJi¹~w@‡"… Oè';m²¿˜°—ÄS/3¾‘ð½…"Å휎›z¬Ïu|; 5#§R5Xñ­ìÍ83¦Ñ¥Bæ-!62Ôaø›&©£ÜT4hD¨gœZ=êšÆq˜Ç™v6Œ« *S·L‡{ôs:™žAµ])°tLY\'Ѐ ŸP?².€q¤îxy2xe šçidˆ CÇCÛ’̳jˆ_‹‰pý¯jQ#äW•ÆUU1­0 dN1üÎ(B<Š“¼w(WOÀa9]H\Váºz¢½l sյ¤&R 0‰[•E^`–¬bù‚¦}QD9Tkס ªEŸKÚ³»¯âÉÀŒÒÊ«¶±<M=‹!ÃV)Fn¶·-åFlGv¥¡H,Á`%>K Ý¿n$AÙr‘Yñ+ëÄÈt>7¾ª.g†¼öúÖmh4†ºž”®+ b$Mþy„‚”^|„´~{?¨Ó©¸p7%s%s ago%s job has been invoked%{description} on %{host}, and %s more...and %s more...and %{count} more...and %{count} moreA comma separated list of input names to be excluded from the foreign template.A comma separated list of input names to be included from the foreign template.A job '%{job_name}' has %{status} at %{time}A job '%{subject}' has failedA job '%{subject}' has finished successfullyA notification when a job finishesA plugin bringing remote execution to the Foreman, completing the config management functionality with remote management functionality.A special label for tracking a recurring job. There can be only one active job with a given purpose at a time.A user to be used for executing the script. If it differs from the SSH user, su or sudo is used to switch the accounts.Abort JobAction with sub plansActionsAdd Foreign Input SetAdvanced fieldsAll fields are required.AlphabeticalAmount of workers in the pool to handle the execution of the remote execution jobs. Restart of the dynflowd/foreman-tasks service is required.Another interface is already set as execution. Are you sure you want to use this one instead?Any LocationAny OrganizationApply toAtAt minuteBack to JobBookmarkCan't find Job Invocation for an id %sCancel JobCancel job invocationCancelledCannot resolve hosts without a bookmark or search queryCannot resolve hosts without a userCannot specify both bookmark_id and search_queryCategories list failed with:Category and TemplateChoose a job template that is pre-selected in job invocation formCircular dependency detected in foreign input set '%{template}' -> '%{target_template}'. Templates stack: %{templates_stack}Cleanup working directoriesClear filtersClone a provision templateCloseCockpit URLConcurrency levelConcurrency level limited toConnect by IPControl concurrency level and distribution over timeCould not display data for job invocation.Could not find any suitable interface for executionCould not render the preview because no host matches the search query.Could not rerun job %{id} because its template could not be foundCould not use any proxy for the %{provider} job. Consider configuring %{global_proxy}, %{fallback_proxy} in settingsCould not use any template used in the job invocationCreateCreate ReportCreate a foreign input setCreate a job invocationCreate a job templateCreate a recurring jobCreate report for this jobCron lineCron line format 'a b c d e', where:CronlineCurrent location %{loc_c} is different from job's location %{loc_j}.Current organization %{org_c} is different from job's organization %{org_j}.DailyDaysDays of weekDefault SSH key passphraseDefault SSH passwordDefault key passphrase to use for SSH. You may override per host by setting a parameter called remote_execution_ssh_key_passphraseDefault password to use for SSH. You may override per host by setting a parameter called remote_execution_ssh_passwordDefault user to use for SSH. You may override per host by setting a parameter called remote_execution_ssh_user.Default user to use for executing the script. If the user differs from the SSH user, su or sudo is used to switch the user.Delete a foreign input setDelete a job templateDescriptionDescription TemplateDescription templateDesignation of a special purposeDisplay advanced fieldsDistribute execution over N seconds. If this is set and proxy batch triggering is enabled, then tasks are triggered on the smart proxy in batches of size 1.Distribute tasks over N secondsDoes not repeatDuplicated inputs detected: %{duplicated_inputs}Dynamic QueryDynamic queryEdit %sEdit Job TemplateEdit Remote Execution FeatureEdit job description templateEffective UserEffective User MethodEffective userEffective user method "%{current_value}" is not one of %{valid_methods}Effective user optionsEffective user passwordEffective user password is only applicable for SSH provider. Other providers ignore this field.
Password is stored encrypted in DB until the job finishes. For future or recurring executions, it is removed after the last execution.Effective user password is only applicable for SSH provider. Other providers ignore this field. Password is stored encrypted in DB until the job finishes. For future or recurring executions, it is removed after the last execution.Enable Global ProxyEnd time needs to be after start timeEndsErrorError loading data from proxyErrors:Evaluated at:Execute the jobs on hosts in randomized orderExecutionExecution orderExecution orderingExecution ordering determines whether the jobs should be executed on hosts in alphabetical order or in randomized order.
Exit status: %sExport a job template to ERBFailedFailed hostsFailed rendering template: %sFallback to Any ProxyFeature input %{input_name} not defined in template %{template_name}Filter by host collectionsFilter by host groupsFilter by hostsFinishedFor example: 1, 2, 3, 4, 5...Foreign input setForeman can run arbitrary commands on remote hosts using different providers, such as SSH or Ansible. Communication goes through the Smart Proxy so Foreman does not have to have direct access to the target hosts and can scale to control many hosts.Form Job TemplateGet output for a hostGet outputs of hosts in a jobGet raw output for a hostHas to be a positive numberHide advanced fieldsHide all advanced fieldsHostHost collectionsHost detailHost groupsHost taskHost with id '%{id}' was not foundHostsHosts gone missingHourlyHow often the job should occur, in the cron formatIdentifier of the Host interface for Remote executionImportImport Puppet classesImport a job template from ERBImport factsInclude all inputs from the foreign templateIndicates that the action should be cancelled if it cannot be started before this time.Inherit from host parameterInputInput set descriptionInputs to useInterface with the '%s' identifier was specified as a remote execution interface, however the interface was not found on the host. If the interface exists, it needs to be created in Foreman during the registration.Internal proxy selector can only be used if Katello is enabledInvalid dateInvalid time formatInvocation type, one of %sJobJob DetailsJob InvocationJob Invocation Report TemplateJob InvocationsJob TaskJob TemplatesJob cancelled by userJob categoryJob execution failedJob finished with errorJob invocationJob invocationsJob resultJob templateJob template ID to be used for the featureJob template imported successfully.Job templatesJobTemplate|LockedJobTemplate|NameJobTemplate|SnippetJobsKey passhprase is only applicable for SSH provider. Other providers ignore this field.
Passphrase is stored encrypted in DB until the job finishes. For future or recurring executions, it is removed after the last execution.Key passphrase is only applicable for SSH provider. Other providers ignore this field. Passphrase is stored encrypted in DB until the job finishes. For future or recurring executions, it is removed after the last execution.LabelLast execution cancelledLast execution failedLast execution succeededLatest JobsLearn more about this in the documentation.List foreign input setsList job invocationsList job templatesList job templates per locationList job templates per organizationList of proxy IDs to be used for remote executionList remote execution featuresList template invocations belonging to job invocationLocationManual selectionMonthlyMust select a bookmark or enter a search queryN/ANameNeverNew Job TemplateNo (override)No Target HostsNo execution finished yetNo hosts found.No jobs availableNo results foundNo template mapped to feature %{feature_name}Not all required inputs have values. Missing inputs: %sOnOnly one of feature or job_template_id can be specifiedOrganizationOverride the description format from the template for this invocation onlyOverride the timeout interval from the template for this invocation onlyOverviewOverwriteOverwrite template if it already existsPasswordPassword is stored encrypted in DB until the job finishes. For future or recurring executions, it is removed after the last execution.PendingPerform a single Puppet runPerform no more executions after this timePlease refine your search.Port to use for SSH communication. Default port 22. You may override per host by setting a parameter called remote_execution_ssh_port.Prefer IPv6 over IPv4PreviewPreview HostsPreview job descriptionPreview templatesPrivate key passphraseProblem with previewing the template: %{error}. Note that you must save template input changes before you try to preview it.Provider typeProviders and templatesProxiesPurposeQuery typeREX job has failed - %sREX job has finished - %sREX job has succeeded - %sRandomizedRecent jobsRecurrenceRecurring logicRecursive rendering of templates detectedRefreshRemote ExecutionRemote Execution FeaturesRemote Execution InterfaceRemote action:Remote executionRemote execution feature label that should be triggered, job template assigned to this feature will be usedRemote execution jobRepeat a maximum of N timesRepeat amount can only be a positive numberRepeatsRerunRerun failedRerun job on failed hostsRerun on %sRerun on failed hostsRerun the jobReset to defaultResolves toResultsReview detailsRunRun JobRun Puppet OnceRun at most N tasks at a timeRun at most N tasks at a time. If this is set and proxy batch triggering is enabled, then tasks are triggered on the smart proxy in batches of size 1.Run jobRunningSSH PortSSH UserSSH provider specific optionsScheduleSchedule Remote JobSchedule a jobSchedule the job for a future timeSchedule the job to start at a later timeSchedule typeScheduledScheduled to start atScheduled to start beforeScriptScroll to bottomScroll to topSearch QuerySearch for remote execution proxy outside of the proxies assigned to the host. The search will be limited to the host's organization and location.Search querySearch the host for any proxy with Remote Execution, useful when the host has no subnet or the subnet does not have an execution proxySee more details at %sSee the last task detailsSee the task detailsSelect a report template used for generating a report for a particular remote execution jobSelect an ERB file to upload in order to import a job template. The template must contain metadata in the first ERB comment.Select as many remote execution proxies as applicable for this subnet. When multiple proxies with the same provider are added, actions will be load balanced among them.Set SSH key passphraseSet SSH passwordSet password for effective user (using sudo-like mechanisms)Set to distribute overShould the ip addresses on host interfaces be preferred over the fqdn? It is useful when DNS not resolving the fqdns properly. You may override this per host by setting a parameter called remote_execution_connect_by_ip. For dual-stacked hosts you should consider the remote_execution_connect_by_ip_prefer_ipv6 settingShould this interface be used for remote execution?Show Job status for the hostsShow all advanced fieldsShow foreign input set detailsShow job invocationShow job template detailsShow remote execution featureSnippetStartStartedStartsStarts atStarts beforeStateStatic QueryStatic queryStatusSubscribe to all my jobsSubscribe to my failed jobsSubscribe to my succeeded jobsSucceededSuccessSync Job TemplatesTarget hostsTarget hosts and inputsTarget template IDTarget: Task DetailsTask cancelledTemplate ERBTemplate Invocation for %sTemplate failed with:Template nameTemplate versionTemplate with id '%{id}' was not foundTemplates list failed with:The dynamic query '%{query}' was not resolved yet. The list of hosts to which it would resolve now can be seen %{here}.The execution interface is used for remote executionThe final host list may change because the selected query is dynamic. It will be rerun during execution.The job cannot be aborted at the moment.The job cannot be cancelled at the moment.The job could not be cancelled.The job template to use, parameter is required unless feature was specifiedThe only applicable proxy %{proxy_names} is downAll %{count} applicable proxies are down. Tried %{proxy_names}The template %{template_name} mapped to feature %{feature_name} is not accessible by the userThere are no available input fields for the selected template.There was an error while updating the status, try refreshing the page.This can happen if the host is removed or moved to another organization or location after the job was startedThis template is locked for editing.This template is locked. Please clone it to a new template to customize.This template is used to generate the description. Input values can be used using the syntax %{package}. You may also include the job category and template name using %{job_category} and %{template_name}.This template is used to generate the description.
Input values can be used using the syntax %{package}.
You may also include the job category and template
name using %{job_category} and %{template_name}.Time in seconds from the start on the remote host after which the job should be killed.Time spanTimeout to killTimeout to kill afterToggle DEBUGToggle STDERRToggle STDOUTToggle commandTotal hostsTry to abort the job on a host without waiting for its resultTry to abort the job without waiting for the results from the remote hostsTry to cancel the jobTry to cancel the job on a hostTrying to abort the jobTrying to cancel the jobTypeType has impact on when is the query evaluated to hosts.Type has impact on when is the query evaluated to hosts.
Type of queryUnable to create mail notification: %sUnable to fetch public keyUnable to remove host from known hostsUnable to save template. Correct highlighted errorsUnknown execution statusUnknown input %{input_name} for template %{template_name}Unknown remote execution feature %sUnsupported or no operating system found for this host.Update a foreign input setUpdate a job templateUse default description templateUser InputsUser can not execute job on host %sUser can not execute job on infrastructure host %sUser can not execute this job templateUser can not execute this job template on %sUser inputValueView all jobsView finished jobsView running jobsView scheduled jobsWeb ConsoleWeeklyWhat command should be used to switch to the effective user. One of %sWhat user should be used to run the script (using sudo-like mechanisms)What user should be used to run the script (using sudo-like mechanisms). Defaults to a template parameter or global setting.When connecting using ip address, should the IPv6 addresses be preferred? If no IPv6 address is set, it falls back to IPv4 automatically. You may override this per host by setting a parameter called remote_execution_connect_by_ip_prefer_ipv6. By default and for compatibility, IPv4 will be preferred over IPv6 by defaultWhen enabled, working directories will be removed after task completion. You may override this per host by setting a parameter called remote_execution_cleanup_working_dirs.Where to find the Cockpit instance for the Web Console button. By default, no button is shown.Whether it should be allowed to override the effective user from the invocation form.Whether or not the template is locked for editingWhether the current user login should be used as the effective userWhether to overwrite the template if it already existsWhether we should sync templates from disk when running db:seed.Workers pool sizeYes (override)You are not allowed to see the currently assigned template. Saving the form now would unassign the template.You have %s results to display. Showing first %s resultsadd an input set for this template to reference a different template inputscancelleddefault_capsule method missing from SmartProxyeffective usererrorerror during rendering: %sevaluates just after you submit this formevaluates just before the execution is started, so if it's planed in future, targeted hosts set may change before itfailedherehost already has an execution interfacehostsin %sincluded template '%s' not foundinput macro with name '%s' used, but no input with such name defined for this templateis day of month (range: 1-31)is day of week (range: 0-6)is hour (range: 0-23)is minute (range: 0-59)is month (range: 1-12)noopen-help-tooltip-buttonqueuedqueued to start executing in %{time}remove template input setrunning %{percent}%%secondssucceededtasks at a timetemplateunknown statususing using Smart ProxyyesProject-Id-Version: foreman_remote_execution 9.0.1 Report-Msgid-Bugs-To: PO-Revision-Date: 2016-02-15 13:54+0000 Last-Translator: FULL NAME Language-Team: Chinese (China) (http://www.transifex.com/foreman/foreman/language/zh_CN/) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Language: zh_CN Plural-Forms: nplurals=1; plural=0; %s%s å‰%s 任务已被调用%{host} çš„ %{description}, å’Œ %s 个更多...å’Œ %s 个更多...å’Œ %{count} 个更多以逗å·åˆ†éš”的输入å称列表,将从外部模æ¿ä¸­æŽ’除。è¦ä»Žå¤–部模æ¿ä¸­åŒ…å«çš„输入å称的列表,以逗å·åˆ†éš”。作业 '%{job_name}' çš„ %%{status}(在 %%{time})作业 '%%{subject}' 已失败作业 '%{subject}' å·²æˆåŠŸå®Œæˆä½œä¸šå®ŒæˆåŽçš„通知一个将远程执行带到 Foreman çš„æ’件,通过远程管ç†åŠŸèƒ½æ¥å®Œæˆé…置管ç†åŠŸèƒ½ã€‚用于跟踪周期性作业的特殊标签。一次åªèƒ½æœ‰ä¸€ä¸ªå…·æœ‰ç»™å®šç›®çš„的活跃作业。è¦ä½¿ç”¨åŸ·è¡Œé€™ script 的使用者。如果使用者與 SSH 使用者ä¸åŒï¼Œæœƒç”¨ su 或 sudo 來切æ›ä½¿ç”¨è€…。终止作业有å­è®¡åˆ’çš„æ“作æ“作添加外部输入集高级项å„个项都需è¦ã€‚按字æ¯åœ¨æ± ä¸­ç”¨æ¥å¤„ç†è¿œç¨‹æ‰§è¡Œä»»åŠ¡çš„工作节点的数é‡ã€‚需è¦é‡å¯ dynflowd/foreman-tasks æœåŠ¡ã€‚å·²ç»å°†å¦ä¸€ä¸ªæŽ¥å£è®¾ç½®ä¸ºæ‰§è¡Œã€‚您确定è¦æ”¹ç”¨è¿™ä¸ªå—?任æ„ä½ç½®ä»»æ„机构应用到ä½äºŽäºŽåˆ†é’Ÿå›žåˆ°ä½œä¸šä¹¦ç­¾æ— æ³•ä¸º ID %s 找到作业调用å–消作业å–消作业调用已å–消无法解æžæ²¡æœ‰ä¹¦ç­¾æˆ–æœç´¢æŸ¥è¯¢çš„主机无法解æžæ²¡æœ‰ç”¨æˆ·çš„主机无法åŒæ—¶æŒ‡å®š bookmark_id å’Œ search_query类别列表失败并带有:类别和模æ¿é€‰æ‹©åœ¨ä½œä¸šè°ƒç”¨è¡¨å•ä¸­é¢„先选择的作业模æ¿åœ¨å¤–部输入设置中å‘现了循环的ä¾èµ–关系 '%{template}' -> '%{target_template}'。模æ¿å †æ ˆï¼š%{templates_stack}清ç†å·¥ä½œç›®å½•æ¸…除过滤器克隆置备模æ¿å…³é—­Cockpit URL并å‘等級对...的并å‘等级é™åˆ¶æŒ‰ IP 连接控制并å‘级别和时间分布无法显示用于作业调用的数æ®ã€‚无法找到适åˆæ‰§è¡Œçš„接å£ç”±äºŽæ²¡æœ‰ä¸»æœºåŒ¹é…æœç´¢æŸ¥è¯¢ï¼Œå› æ­¤æ— æ³•å‘ˆçŽ°é¢„览。无法é‡æ–°è¿è¡Œä½œä¸š %{id},因为它的模æ¿æ²¡æœ‰æ‰¾åˆ°æ— æ³•ä¸º %%{provider} 作业使用任何代ç†ã€‚考虑在设置中é…ç½® %{global_proxy} å’Œ %{fallback_proxy}无法使用作业调用中使用的任何模æ¿åˆ›å»ºåˆ›å»ºæŠ¥å‘Šå»ºç«‹å¤–部输入集创建一个作业调用创建作业模æ¿åˆ›å»ºä¸€ä¸ªé‡å¤è¿è¡Œçš„作业为这个作业创建报告Cron è¡ŒCron è¡Œæ ¼å¼ 'a b c d e', 其中:Cronline当å‰ä½ç½® ï¼…{loc_c} 与作业ä½ç½® ï¼…{loc_j} ä¸åŒã€‚当å‰æœºæž„ ï¼…{org_c} 与作业机构 ï¼…{org_j} ä¸åŒã€‚æ¯æ—¥å¤©æ˜ŸæœŸå‡ é»˜è®¤çš„ SSH 密钥å£ä»¤é»˜è®¤ SSH 密ç SSH 默认使用的密钥å£ä»¤ã€‚å¯é€šè¿‡è®¾ç½®å为 remote_execution_ssh_key_passphrase çš„å‚æ•°æ¥æŒ‰ä¸»æœºè¦†ç›–SSH 默认使用的密ç ã€‚å¯é€šè¿‡è®¾ç½®å为 remote_execution_ssh_password çš„å‚æ•°æ¥æŒ‰ä¸»æœºè¦†ç›–SSH 默认使用的用户。å¯é€šè¿‡è®¾ç½®å为 remote_execution_ssh_user çš„å‚æ•°æ¥æŒ‰ä¸»æœºè¦†ç›–用于执行脚本的默认用户。如果用户与 SSH 用户ä¸åŒï¼Œåˆ™ä½¿ç”¨ su 或 sudo 切æ¢ç”¨æˆ·ã€‚删除外部输入集删除作业模æ¿æè¿°æ述模æ¿æ述模æ¿è®¾è®¡ç‰¹æ®Šç›®çš„显示高级字段在 N 秒内分é…执行。如果设置了此选项并å¯ç”¨äº†ä»£ç†æ‰¹å¤„ç†è§¦å‘,则将在智能代ç†ä¸Šä»¥å¤§å°ä¸º 1 的批处ç†è§¦å‘任务。在 N 秒内分é…任务没有创建检测到é‡å¤çš„输入:%{duplicated_inputs}动æ€æŸ¥è¯¢åŠ¨æ€æŸ¥è¯¢ç¼–辑 %s编辑作业模æ¿ç¼–辑远程执行功能编辑作业æ述模æ¿æœ‰æ•ˆç”¨æˆ·æœ‰æ•ˆç”¨æˆ·æ–¹æ³•æœ‰æ•ˆçš„用户有效的用户方法 "%{current_value}" ä¸æ˜¯ %{valid_methods} 之一有效的用户选项有效用户密ç æœ‰æ•ˆç”¨æˆ·å¯†ç åªé€‚用于 SSH æ供商。其他æ供商会忽略此字段。
在任务完æˆä¹‹å‰ï¼Œå¯†ç ä¼šä»¥åŠ å¯†æ–¹å¼å­˜å‚¨åœ¨æ•°æ®åº“中。对于未æ¥æˆ–周期性执行,该密ç å°†åœ¨æœ€åŽä¸€æ¬¡æ‰§è¡ŒåŽåˆ é™¤ã€‚有效用户密ç åªé€‚用于 SSH æ供商。其他æ供商会忽略此字段。在任务完æˆä¹‹å‰ï¼Œå¯†ç ä¼šä»¥åŠ å¯†æ–¹å¼å­˜å‚¨åœ¨æ•°æ®åº“中。对于未æ¥æˆ–周期性执行,该密ç å°†åœ¨æœ€åŽä¸€æ¬¡æ‰§è¡ŒåŽåˆ é™¤ã€‚å¯ç”¨å…¨å±€ä»£ç†æœåŠ¡å™¨ç»“æŸæ—¶é—´éœ€è¦åœ¨å¼€å§‹æ—¶é—´åŽç»“æŸé”™è¯¯ä»Žä»£ç†åŠ è½½æ•°æ®æ—¶å‡ºé”™é”™è¯¯ï¼šè¯„估于:以éšæœºé¡ºåºåœ¨ä¸»æœºä¸Šæ‰§è¡Œä½œä¸šæ‰§è¡Œæ‰§è¡Œé¡ºåºæ‰§è¡Œé¡ºåºæ‰§è¡Œé¡ºåºç¡®å®šäº†åº”按字æ¯é¡ºåºè¿˜æ˜¯éšæœºé¡ºåºåœ¨ä¸»æœºä¸Šæ‰§è¡Œä½œä¸šã€‚
  • Ordered - 以字æ¯é¡ºåºåœ¨ä¸»æœºä¸Šæ‰§è¡Œä½œä¸š
  • Randomized - 以éšæœºé¡ºåºåœ¨ä¸»æœºä¸Šæ‰§è¡Œä½œä¸š
退出状æ€ï¼š%s把作业模æ¿å¯¼å‡ºåˆ° ERB失败失败的主机呈现模æ¿å¤±è´¥ï¼š%s退回至任何代ç†æœåŠ¡å™¨åŠŸèƒ½è¾“入%{input_name} 未在模æ¿ï¼…{template_name} 中定义按主机集过滤按主机组过滤按主机过滤完æˆä¾‹å¦‚:1, 2, 3, 4, 5...外æ¥è¾“入集Foreman å¯ä»¥åœ¨è¿œç¨‹ä¸»æœºä¸Šä½¿ç”¨ä¸åŒçš„方法(如 SSH 或 Ansible)è¿è¡Œå‘½ä»¤ã€‚网络交æµä¼šé€šè¿‡æ™ºèƒ½ä»£ç†è¿›è¡Œï¼Œå› æ­¤ Foreman ä¸éœ€è¦ç›´æŽ¥è®¿é—®ç›®æ ‡ä¸»æœºï¼Œå¹¶å¯ä»¥æ‰©å±•æ¥æŽ§åˆ¶å¤šä¸ªä¸»æœºã€‚æ¥è‡ªä½œä¸šæ¨¡æ¿èŽ·å–主机的输出获å–作业中主机的输出获å–主机的原始输出必须为一个正数éšè—高级字段éšè—所有高级字段主机主机集åˆä¸»æœºè¯¦æƒ…主机组主机任务找ä¸åˆ° id 为 '%{id}' 的主机主机主机丢失æ¯å°æ—¶ä½œä¸šè¿è¡Œçš„频率,使用 cron æ ¼å¼ä¸»æœºæŽ¥å£çš„标识符,用于远程执行导入导入 Puppet 类从 ERB 导入作业模版导入事实在外部模æ¿ä¸­åŒ…å«æ‰€æœ‰è¾“入格å¼è¿™ä»£è¡¨ï¼Œå¦‚æžœæ“作无法在这个时间å‰å¼€å§‹åˆ™æ“作应该被å–消。从主机å‚数继承输入输入集æè¿°è¦ä½¿ç”¨çš„輸入带有'%s'标识符的接å£è¢«æŒ‡å®šä¸ºè¿œç¨‹æ‰§è¡ŒæŽ¥å£ï¼Œä½†æ˜¯åœ¨ä¸»æœºä¸Šæ‰¾ä¸åˆ°è¯¥æŽ¥å£ã€‚如果该接å£å­˜åœ¨ï¼Œåˆ™éœ€è¦åœ¨æ³¨å†Œè¿‡ç¨‹ä¸­åœ¨ Foreman 中创建该接å£ã€‚如果å¯ç”¨äº†Katello,则åªèƒ½ä½¿ç”¨å†…部代ç†é€‰æ‹©å™¨æ— æ•ˆçš„日期无效的时间格å¼è°ƒç”¨ç±»åž‹ï¼Œ%s 其中之一任务作业详情作业调用作业调用报告模æ¿ä½œä¸šè°ƒç”¨ä½œä¸šä»»åŠ¡ä½œä¸šæ¨¡æ¿ä½œä¸šè¢«ç”¨æˆ·å–消作业类别作业执行失败作业完æˆä½†å¸¦æœ‰é”™è¯¯å·¥ä½œè°ƒç”¨ä½œä¸šè°ƒç”¨ä½œä¸šç»“果作业模æ¿ç”¨äºŽåŠŸèƒ½çš„ä½œä¸šæ¨¡æ¿ IDæˆåŠŸå¯¼å…¥ä½œä¸šæ¨¡ç‰ˆã€‚作业模æ¿JobTemplate|LockedJobTemplate|NameJobTemplate|Snippet工作密钥å£ä»¤åªé€‚用于 SSH æ供商。其他æ供商会忽略此字段。
在任务完æˆä¹‹å‰ï¼Œéƒ½ä¼šä»¥åŠ å¯†æ–¹å¼å­˜å‚¨åœ¨æ•°æ®åº“中。对于未æ¥æˆ–周期性执行,该密ç å°†åœ¨æœ€åŽä¸€æ¬¡æ‰§è¡ŒåŽè¢«åˆ é™¤ã€‚密钥å£ä»¤åªé€‚用于 SSH æ供商。其他æ供商会忽略此字段。在任务完æˆä¹‹å‰ï¼Œéƒ½ä¼šä»¥åŠ å¯†æ–¹å¼å­˜å‚¨åœ¨æ•°æ®åº“中。对于未æ¥æˆ–周期性执行,该密ç å°†åœ¨æœ€åŽä¸€æ¬¡æ‰§è¡ŒåŽè¢«åˆ é™¤ã€‚标签最åŽçš„执行已å–消最åŽçš„执行失败最åŽæˆåŠŸçš„执行最新的作业如需了解更多信æ¯ï¼Œè¯·å‚阅文档。列出外部输入集列出作业调用列出作业模æ¿åˆ—出å„個ä½ç½®ä¸Šçš„工作範本列出æ¯ä¸ªæœºæž„的作业模æ¿ç”¨äºŽè¿œç¨‹æ‰§è¡Œçš„ä»£ç† ID 列表列出远程执行功能列出属于作业调用的模æ¿è°ƒç”¨ä½ç½®æ‰‹åŠ¨é€‰æ‹©æ¯æœˆå¿…须选择一个书签或输入一个æœç´¢æŸ¥è¯¢ä¸é€‚用å称决ä¸æ–°ä½œä¸šæ¨¡æ¿å¦ï¼ˆè¦†ç›–)没有目标主机尚未执行完毕找ä¸åˆ°ä¸»æœºã€‚没有å¯ç”¨çš„作业没有找到结果没有映射到功能 %{feature_name} 的模æ¿ä¸¦ä¸æ˜¯æ‰€æœ‰éœ€è¦çš„輸入都有值。缺少的输入:%s上åªèƒ½æŒ‡å®šä¸€ä¸ªåŠŸèƒ½æˆ– job_template_id机构åªä¸ºæ­¤è°ƒç”¨è¦†ç›–æ¥è‡ªæ¨¡æ¿çš„æè¿°æ ¼å¼åªä¸ºæ­¤è°ƒç”¨ä½¿ç”¨è¯¥æ¨¡æ¿è¦†ç›–超时间隔概况覆盖如果已存在则覆盖模版密ç åœ¨ä½œä¸šå®Œæˆä¹‹å‰ï¼Œå¯†ç éƒ½ä¼šä»¥åŠ å¯†æ–¹å¼å­˜å‚¨åœ¨æ•°æ®åº“中。对于未æ¥æˆ–周期性执行,该密ç å°†åœ¨æœ€åŽä¸€æ¬¡æ‰§è¡ŒåŽè¢«åˆ é™¤ã€‚待处ç†æ‰§è¡Œä¸€ä¸ªå•ç‹¬ Puppet è¿è¡Œåœ¨æ­¤æ—¶é—´åŽä¸å†æ‰§è¡Œè¯·é‡æ–°è°ƒæ•´æ‚¨çš„æœç´¢ã€‚è¦ç”¨äºŽ SSH 通信的端å£ã€‚é»˜è®¤ç«¯å£ 22。您å¯ä»¥é€šè¿‡è®¾ç½®å为 remote_execution_ssh_port çš„å‚æ•°æ¥æŒ‰ä¸»æœºè¿›è¡Œè¦†ç›–。首选 IPv6 而ä¸æ˜¯ IPv4 预览预览主机预览作业æ述预览模æ¿ç§é’¥å¯†ç å£ä»¤é¢„览模æ¿æœ‰é—®é¢˜ï¼š%{error}。请注æ„,在预览å‰éœ€è¦ä¿å­˜æ¨¡æ¿è¾“入的改å˜ã€‚供应商类型供应商和模æ¿ä»£ç†æœåŠ¡å™¨ç›®çš„查询类型REX 作业已失败 - %sREX ä½œä¸šå·²å®Œæˆ - %sREX 作业已æˆåŠŸ - %séšæœºåŒ–最近的作业é‡å¤å‘生é‡å¤é€»è¾‘检测到递归的模æ¿å‘ˆçŽ°åˆ·æ–°è¿œç¨‹æ‰§è¡Œè¿œç¨‹æ‰§è¡ŒåŠŸèƒ½è¿œç¨‹æ‰§è¡ŒæŽ¥å£è¿œç¨‹æ“作:远程执行应触å‘的远程执行功能标签,将使用分é…给此功能的任务模æ¿è¿œç¨‹æ‰§è¡Œä½œä¸šæœ€å¤šé‡å¤ N 次é‡å¤æ•°é‡åªèƒ½æ˜¯ä¸€ä¸ªæ­£æ•°é‡å¤é‡æ–°è¿è¡Œé‡æ–°è¿è¡Œå¤±è´¥åœ¨å¤±è´¥çš„主机上é‡æ–°è¿è¡Œä½œä¸šåœ¨ %s é‡æ–°è¿è¡Œåœ¨å¤±è´¥çš„主机上é‡æ–°è¿è¡Œé‡æ–°è¿è¡Œä½œä¸šé‡ç½®ä¸ºé»˜è®¤è§£æžåˆ°ç»“果审阅详情è¿è¡Œè¿è¡Œä½œä¸šè¿è¡Œ Puppet 一次一次最多è¿è¡Œ N 个任务一次最多è¿è¡Œ N 个任务。如果设置了此选项并å¯ç”¨äº†ä»£ç†æ‰¹å¤„ç†è§¦å‘,则将在智能代ç†ä¸Šä»¥å¤§å°ä¸º 1 的批处ç†è§¦å‘任务。è¿è¡Œä½œä¸šåŸ·è¡Œä¸­SSH 端å£SSH 用户SSH 供应商特定的选项调度调度远程作业调度一个作业把作业调度到一个以åŽçš„时间把作业调度在一个以åŽçš„时间开始调度类型调度的调度开始于调度在这个时间å‰å¼€å§‹è„šæœ¬æ»šåŠ¨åˆ°åº•éƒ¨æ»šåŠ¨åˆ°é¡¶éƒ¨æœç´¢æŸ¥è¯¢åœ¨åˆ†é…给主机的代ç†ä¹‹å¤–æœç´¢è¿œç¨‹æ‰§è¡Œä»£ç†ã€‚æœç´¢å°†ä¼šé™åˆ¶åœ¨ä¸»æœºçš„机构和ä½ç½®å†…。æœç´¢æŸ¥è¯¢åœ¨ä¸»æœºä¸Šæœç´¢å…·æœ‰è¿œç¨‹æ‰§è¡ŒåŠŸèƒ½çš„任何代ç†ï¼Œå½“主机没有å­ç½‘或å­ç½‘没有执行代ç†æ—¶ï¼Œæ­¤å‘½ä»¤å¾ˆæœ‰ç”¨åœ¨ %s å‚阅更多细节查看最åŽçš„任务详情查看任务详情选择用于生æˆç‰¹å®šè¿œç¨‹æ‰§è¡Œä½œä¸šçš„报告模æ¿é€‰æ‹©è¦ä¸Šä¼ çš„ ERB 文件æ¥å¯¼å…¥ä»»åŠ¡æ¨¡ç‰ˆã€‚这个模版必须包å«ç¬¬ä¸€ä¸ª ERB 注释里的元数æ®ã€‚选择适用于该å­ç½‘çš„å°½å¯èƒ½å¤šçš„远程执行代ç†ã€‚当添加具有相åŒæ供者的多个代ç†æ—¶ï¼Œå°†åœ¨å®ƒä»¬ä¹‹é—´å¹³è¡¡æ“作。设置 SSH 密钥å£ä»¤è®¾ç½® SSH 密ç ä¸ºæœ‰æ•ˆç”¨æˆ·è®¾ç½®å¯†ç ï¼ˆä½¿ç”¨ç±»ä¼¼ sudo 的机制)设置为通过...分é…相比 fqdn,是å¦åº”优先使用主机接å£ä¸Šçš„ ip 地å€ï¼Ÿå½“ DNS 未能æˆåŠŸè§£æž fqdns 时,它很有用。您å¯ä»¥é€šè¿‡è®¾ç½®å‚æ•° remote_execution_connect_by_ip æ¥è¦†ç›–æ¯ä¸ªä¸»æœºçš„这个地å€ã€‚对于多堆栈的主机,您应该考虑 remote_execution_connect_by_ip_prefer_ipv6 设置该接å£åº”该用于远程执行å—?显示主机的作业状æ€çŽ°å®žæ‰€æœ‰é«˜çº§å­—段显示外部输入集详细信æ¯æ˜¾ç¤ºä½œä¸šè°ƒç”¨æ˜¾ç¤ºä½œä¸šæ¨¡æ¿è¯¦æƒ…显示远程执行功能程åºä»£ç ç‰‡æ®µå¼€å§‹å·²å¯åŠ¨å¼€å§‹å¼€å§‹äºŽå¼€å§‹å‰çŠ¶æ€é™æ€æŸ¥è¯¢é™æ€æŸ¥è¯¢çŠ¶æ€è®¢é˜…到所有主机订阅到我失败的作业订阅到我æˆåŠŸçš„作业已æˆåŠŸæˆåŠŸåŒæ­¥ä½œä¸šæ¨¡æ¿ç›®æ ‡ä¸»æœºç›®æ ‡ä¸»æœºå’Œè¾“å…¥ç›®æ ‡æ¨¡æ¿ ID目标:任务详情任务被å–消模版 ERB%s 的模æ¿è°ƒç”¨æ¨¡æ¿å¤±è´¥å¹¶å¸¦æœ‰ï¼šæ¨¡æ¿å称模æ¿ç‰ˆæœ¬æ‰¾ä¸åˆ° id 为 '%{id}' 的模æ¿æ¨¡æ¿åˆ—表失败并带有:动æ€æŸ¥è¯¢ '%{query}' 还没有解æžã€‚现在应该解æžçš„主机列表å¯åœ¨ %{here} 查看。用于远程执行的执行接å£ç”±äºŽæ‰€é€‰æŸ¥è¯¢æ˜¯åŠ¨æ€çš„,因此最终主机列表å¯èƒ½ä¼šæ›´æ”¹ã€‚将在执行期间é‡æ–°è¿è¡Œã€‚ç›®å‰æ— æ³•ç»ˆæ­¢ä½œä¸šã€‚ç›®å‰æ— æ³•å–消作业。此作业无法å–消。è¦ä½¿ç”¨çš„任务模æ¿ï¼Œé™¤éžå·²æŒ‡å®šåŠŸèƒ½ï¼Œå¦åˆ™å‚数是必需的唯一å¯ç”¨çš„ä»£ç† %{proxy_names} å·²åœæœºç”¨æˆ·æ— æ³•è®¿é—®æ˜ å°„到功能 %{feature_name} çš„æ¨¡æ¿ %{template_name}所选模æ¿æ²¡æœ‰å¯ç”¨çš„输入字段。更新状æ€æ—¶å‡ºé”™ï¼Œè¯·å°è¯•åˆ·æ–°é¡µé¢ã€‚如果在作业开始åŽå°†ä¸»æœºåˆ é™¤æˆ–移动到其他机构或ä½ç½®ï¼Œåˆ™å¯èƒ½ä¼šå‘生这ç§æƒ…况该模æ¿è¢«é”定进行编辑。此模æ¿å·²é”定。请将它克隆到一个新的模æ¿è¿›è¡Œå®šåˆ¶ã€‚这个模å—用æ¥ç”Ÿæˆæ述。输入值å¯ä»¥ä½¿ç”¨è¯­æ³• %{package}。您å¯ä»¥ä½¿ç”¨ %{job_category} å’Œ %{template_name} æ¥åŒ…括作业类型和模æ¿å称。这个模å—用æ¥ç”Ÿæˆæ述。
输入值å¯ä»¥ä½¿ç”¨è¯­æ³•%{package}。
您å¯ä»¥ä½¿ç”¨ {job_category} å’Œ {template_name} æ¥
包括作业类型和模æ¿å称。在远程主机上开始åŽï¼Œä»¥ç§’计算时间,之åŽç»“æŸä½œä¸šã€‚时间跨度超时至结æŸè¶…æ—¶è‡³ç»ˆæ­¢æ—¶é—´åˆ‡æ¢ DEBUGåˆ‡æ¢ STDERRåˆ‡æ¢ STDOUT切æ¢å‘½ä»¤ä¸»æœºæ€»æ•°å°è¯•åœ¨ä¸ç­‰å¾…结果的情况下终止主机中的作业å°è¯•åœ¨ä¸ç­‰å¾…远程主机的结果情况下终止作业å°è¯•å–消作业å°è¯•å–消主机上的作业å°è¯•ä¸­æ­¢ä½œä¸šå°è¯•å–消作业类型类型会影å“到什么时候会评估到主机。类型会对何时评估主机查询产生影å“。
  • é™æ€ - æ交此表格åŽç«‹å³è¯„ä¼°
  • åŠ¨æ€ - 开始执行å‰è¿›è¡Œè¯„估,因此,如果以åŽè®¡åˆ’,则目标主机集å¯èƒ½ä¼šåœ¨å®ƒä¹‹å‰å‘生å˜åŒ–
查询类型无法创建邮件通知:%s无法获å–公共密钥无法从已知主机中删除主机无法ä¿å­˜æ¨¡ç‰ˆã€‚纠正高亮显示的错误。未知的执行状æ€æœªçŸ¥è¾“入%{input_name}模æ¿ç”¨äºŽæ¨¡æ¿ï¼…{template_name}未知的远程执行功能 %s该主机ä¸æ”¯æŒæˆ–找ä¸åˆ°æ“作系统。更新外部输入集更新作业模æ¿ä½¿ç”¨é»˜è®¤æ述模æ¿ç”¨æˆ·è¾“入用户ä¸èƒ½åœ¨ä¸»æœº %s 上执行作业用户无法在基础架构主机 %s 上执行作业用户无法执行这个作业模æ¿ç”¨æˆ·ä¸èƒ½åœ¨ %s 上执行这个作业模æ¿ç”¨æˆ·è¾“入值查看所有作业查看完æˆçš„作业查看è¿è¡Œçš„作业查看调度的作业Web 控制å°æ¯å‘¨åº”该使用什么命令切æ¢åˆ°æœ‰æ•ˆç”¨æˆ·ã€‚%s 之一应该使用什么用户æ¥è¿è¡Œè„šæœ¬ï¼ˆä½¿ç”¨ç±»ä¼¼äºŽ sudo 的机制)应该使用什么用户æ¥è¿è¡Œè„šæœ¬ï¼ˆä½¿ç”¨ç±»ä¼¼äºŽ sudo 的机制)。默认为模æ¿å‚数或全局设置。使用 ip 地å€è¿›è¡Œè¿žæŽ¥æ—¶ï¼Œæ˜¯å¦åº”该首选 IPv6 地å€ï¼Ÿå¦‚果没有设置 IPv6 地å€ï¼Œå®ƒä¼šè‡ªåŠ¨å›žé€€åˆ°ä½¿ç”¨ IPv4。您å¯ä»¥é€šè¿‡è®¾ç½®å为remote_execution_connect_by_ip_prefer_prefer_ipv6 çš„å‚æ•°æ¥é’ˆå¯¹å•ä¸ªä¸»æœºè¿›è¡Œè¦†ç›–。默认情况下,为了实现兼容的目的,IPv4 将优先于 IPv6。如果å¯ç”¨ï¼Œå·¥ä½œç›®å½•ä¼šåœ¨ä»»åŠ¡å®ŒæˆåŽè¢«åˆ é™¤ã€‚使用å为 remote_execution_cleanup_working_dirs çš„å‚æ•°å¯ä»¥åœ¨ç›¸å…³ä¸»æœºä¸Šè¦†ç›–这个设置。在哪里å¯ä»¥æ‰¾åˆ° Web Console 按钮的 Cockpit 实例。默认情况下,ä¸æ˜¾ç¤ºä»»ä½•æŒ‰é’®ã€‚是å¦åº”å…许从调用表å•ä¸­è¦†ç›–有效用户。此模æ¿æ˜¯å¦è¢«é”定用于编辑当å‰ç”¨æˆ·ç™»å½•å是å¦åº”用作有效用户如果已存在是å¦è¦†ç›–模版è¿è¡Œ db:seed 时是å¦åº”该从ç£ç›˜åŒæ­¥æ¨¡æ¿ã€‚工作节点池的大å°æ˜¯ï¼ˆè¦†ç›–)您没有æƒé™æŸ¥çœ‹å½“å‰åˆ†é…的模æ¿ã€‚现在ä¿å­˜è¡¨å•å°†å–消分é…模æ¿ã€‚您有 %s ä¸ªç»“æžœçŽ°å®žã€‚æ˜¾ç¤ºå‰ %s 个结果为此模æ¿æ·»åŠ ä¸€ä¸ªè¾“入集,以引用其他模æ¿è¾“入已å–消SmartProxy 中缺少 default_capsule 方法有效用户错误呈现时出错:%sæ交此表å•åŽè¯„估在执行å¯åŠ¨å‰è¿›è¡Œè¯„估,因此如果将æ¥éœ€è¦å®ƒï¼Œåˆ™ç›®æ ‡ä¸»æœºè®¾ç½®å¯èƒ½ä¼šåœ¨å®ƒä¹‹å‰æ”¹å˜ã€‚失败这里主机已有一个执行接å£ä¸»æœºåœ¨ %sæ²¡æœ‰æ‰¾åˆ°åŒ…æ‹¬çš„æ¨¡æ¿ '%s'使用å称为 '%s' 的输入å®ï¼Œå½“没有为这个模æ¿å®šä¹‰ä½¿ç”¨è¿™ä¸ªå称的输入日期(范围:1-31)星期几(范围:0-6)å°æ—¶ï¼ˆèŒƒå›´ï¼š0-23)分钟(范围:0-59)月份(范围:1-12)å¦open-help-tooltip-button已排队已排队,在 %{time} 开始实施删除模æ¿è¾“入集è¿è¡Œ %{percent}%%秒已æˆåŠŸåœ¨ä¸€ä¸ªæ—¶é—´ç‚¹çš„任务模æ¿æœªçŸ¥çš„状æ€ä½¿ç”¨ 使用智能代ç†æ˜¯