Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-372 Associate jobs with plans when using the PCP transport Change By: Alex Dreyer Fix Version/s: BOLT Next Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-372 Associate jobs with plans when using the PCP transport Change By: Alex Dreyer Release Notes Summary: This is really a PE feature so it doens't need bolt docs or release notes. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title David Kramer assigned an issue to Lucy Wyman Puppet Task Runner / BOLT-372 Associate jobs with plans when using the PCP transport Change By: David Kramer Assignee: Lucy Wyman Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Lucy Wyman
During the first action that uses the PCP transport with a new config while running a plan attempt to use {{/command/plan_start}} (providing the plan name of the top level plan called from the CLI, parameters and to orch) to get a plan_job id. If the command is not supported by Orchestrator, continue without a plan_job id and use the {{task}} command instead of {{plan_task}}. Other errors should halt the plan.The plan job id should be logged at notice level.Subsequent actions over the PCP transport with the same config should use the same plan_job id.On completion ] Bolt should call {{/command/plan_finish}} for every orchestrator it's tracking a {{plan_job}} id for. This indicates that transports need a concept of setup and teardown and the orchestrator transport needs to track "connections". Teardown should not be called on control+c.The name and parameters of nested plans are essentially ignored by the PCP transport. Only the plan named from the CLI should be used.Executor will need to pass information about the CLI invocation to transports to support this. It needs to know if it is running as part of a plan and if so what the plan info is. We may be able to simplify some logging using this too.Plan descriptions are out of scope for this ticket. It will eventually be a CLI --description argument (see BOLT-410)
Add Comment
This message was sent by Atlassian
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Lucy Wyman
During the first action that uses the PCP transport with a new config while running a plan attempt to use {{/ commands command /plan_start}} (providing the plan name of the top level plan called from the CLI, parameters and to orch) to get a plan_job id. If the command is not supported by Orchestrator, continue without a plan_job id and use the {{task}} command instead of {{plan_task}}. Other errors should halt the plan.The plan job id should be logged at notice level.Subsequent actions over the PCP transport with the same config should use the same plan_job id.On completion] Bolt should call {{/ commands command /plan_finish}} for every orchestrator it's tracking a {{plan_job}} id for. This indicates that transports need a concept of setup and teardown and the orchestrator transport needs to track "connections". Teardown should not be called on control+c.The name and parameters of nested plans are essentially ignored by the PCP transport. Only the plan named from the CLI should be used.Executor will need to pass information about the CLI invocation to transports to support this. It needs to know if it is running as part of a plan and if so what the plan info is. We may be able to simplify some logging using this too.Plan descriptions are out of scope for this ticket. It will eventually be a CLI --description argument (see BOLT-410)
Add Comment
This message was
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Lucy Wyman updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Lucy Wyman
During the first action that uses the PCP transport with a new config while running a plan attempt to use {{/commands/plan_start}} (providing the plan name of the top level plan called from the CLI, parameters and to orch) to get a plan_job id. If the command is not supported by Orchestrator, continue without a plan_job id and use the {{task}} command instead of {{plan_task}}. Other errors should halt the plan.The plan job id should be logged at notice level.Subsequent actions over the PCP transport with the same config should use the same plan_job id.On completion] Bolt should call {{/commands/ plan_end plan_finish }} for every orchestrator it's tracking a {{plan_job}} id for. This indicates that transports need a concept of setup and teardown and the orchestrator transport needs to track "connections". Teardown should not be called on control+c.The name and parameters of nested plans are essentially ignored by the PCP transport. Only the plan named from the CLI should be used.Executor will need to pass information about the CLI invocation to transports to support this. It needs to know if it is running as part of a plan and if so what the plan info is. We may be able to simplify some logging using this too.Plan descriptions are out of scope for this ticket. It will eventually be a CLI --description argument (see BOLT-410)
Add Comment
This message was sent by
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Alex Dreyer assigned an issue to Unassigned Puppet Task Runner / BOLT-372 Associate jobs with plans when using the PCP transport Change By: Alex Dreyer Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Michael Smith assigned an issue to Alex Dreyer Puppet Task Runner / BOLT-372 Associate jobs with plans when using the PCP transport Change By: Michael Smith Assignee: Alex Dreyer Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Michael Smith
During the first action that uses the PCP transport with a new config while running a plan attempt to use {{/commands/plan_start}} (providing the plan name of the top level plan called from the CLI, parameters and to orch) to get a plan_job_id plan_job id . If the command is not supported by Orchestrator, continue without a plan_job_id plan_job id and use the {{task}} command instead of {{plan_task}}. Other errors should halt the plan.The plan job id should be logged at notice level.Subsequent actions over the PCP transport with the same config should use the same plan_job_id plan_job id .On completion] Bolt should call {{/commands/plan_end}} for every orchestrator it's tracking a {{ plan_job_id plan_job }} id for. This indicates that transports need a concept of setup and teardown and the orchestrator transport needs to track "connections". Teardown should not be called on control+c.The name and parameters of nested plans are essentially ignored by the PCP transport. Only the plan named from the CLI should be used.Executor will need to pass information about the CLI invocation to transports to support this. It needs to know if it is running as part of a plan and if so what the plan info is. We may be able to simplify some logging using this too.Plan descriptions are out of scope for this ticket. It will eventually be a CLI --description argument (see BOLT-410)
Add Comment
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Yasmin Rajabi updated an issue Puppet Task Runner / BOLT-372 Associate jobs with plans when using the PCP transport Change By: Yasmin Rajabi Sprint: Bolt Ready for Grooming Kanban Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Alex Dreyer updated an issue Puppet Task Runner / BOLT-372 Associate jobs with plans when using the PCP transport Change By: Alex Dreyer Sprint: Bolt Discover/Design Ready for Grooming Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Alex Dreyer
During the first action that uses the PCP transport with a new config while running a plan attempt to use {{/commands/plan_start}} (providing the plan name of the top level plan called from the CLI, parameters and description to orch) to get a plan_job_id. If the command is not supported by Orchestrator, continue without a plan_job_id and use the {{task}} command instead of {{plan_task}}. Other errors should halt the plan.The plan job id should be logged at notice level.Subsequent actions over the PCP transport with the same config should use the same plan_job_id.On completion] Bolt should call {{/commands/plan_end}} for every orchestrator it's tracking a {{plan_job_id}} for. This indicates that transports need a concept of setup and teardown and the orchestrator transport needs to track "connections". Teardown should not be called on control+c.The name and parameters of nested plans are essentially ignored by the PCP transport. Only the plan named from the CLI should be used. Executor will need to pass information about the CLI invocation to transports to support this. It needs to know if it is running as part of a plan and if so what the plan info is. We may be able to simplify some logging using this too.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Alex Dreyer
During the first action that uses the PCP transport with a new config while running a plan attempt to use {{/commands/plan_start}} (providing the plan name of the top level plan called from the CLI, parameters and description to orch) to get a plan_job_id. If the command is not supported by Orchestrator, continue without a plan_job_id and use the {{task}} command instead of {{plan_task}}. Other errors should halt the plan.The plan job id should be logged at notice level.Subsequent actions over the PCP transport with the same config should use the same plan_job_id.On completion] Bolt should call {{/commands/plan_end}} for every orchestrator it's tracking a {{plan_job_id}} for. This indicates that transports need a concept of setup and teardown and the orchestrator transport needs to track "connections". Teardown should not be called on control+c.The name and parameters of nested plans are essentially ignored by the PCP transport. Only the plan named from the CLI should be used.Executor will need to pass information about the CLI invocation to transports to support this. It needs to know if it is running as part of a plan and if so what the plan info is. We may be able to simplify some logging using this too. Plan descriptions are out of scope for this ticket. It will eventually be a CLI --description argument (see BOLT-410)
Add Comment
This message was sent
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Alex Dreyer updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Alex Dreyer
During the first action that uses the PCP transport with a new config while running a plan attempt to use {{/commands/plan_start}} (providing the plan name of the top level plan called from the CLI, parameters and description to orch ) to get a plan_job_id. If the command is not supported by Orchestrator, continue without a plan_job_id and use the {{task}} command instead of {{plan_task}} . Other errors should halt the plan. The plan job id should be logged at notice level. Subsequent actions over the PCP transport with the same config should use the same plan_job_id.On completion , error, or Ctrl-C, ] Bolt should call {{/commands/plan_end}} if for every orchestrator it's tracking a {{ plan_start plan_job_id }} was previously used for . This indicates that transports need a concept of setup and teardown and the orchestrator transport needs to track "connections" . Teardown should not be called on control+c. The name and parameters of nested plans are essentially ignored by the PCP transport. Executor will need to pass information about the CLI invocation to transports to support this. It needs to know if it is running as part of a plan and if so what the plan info is.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Michael Smith commented on BOLT-372 Re: Associate jobs with plans when using the PCP transport Should probably drop anything dealing with plan_end, as ORCH-2194 doesn't include that. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Michael Smith commented on BOLT-372 Re: Associate jobs with plans when using the PCP transport Provide a description for any Bolt action, so we can pass it to Orchestrator? Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Michael Smith
During the first action that uses the PCP transport while running a plan attempt to use {{/commands/plan_start}} (providing the plan name) to get a plan_job_id. If the command is not supported by Orchestrator, continue without a plan_job_id. Other errors should halt the plan.Subsequent actions over the PCP transport should use the same plan_job_id.On completion, error, or Ctrl-C, Bolt should call {{/commands/plan_end}} if {{plan_start}} was previously used. This indicates that transports need a concept of setup and teardown.The name and parameters of nested plans are essentially ignored by the PCP transport.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it,
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Alex Dreyer commented on BOLT-372 Re: Associate jobs with plans when using the PCP transport ending the 'plan' on ctrl+c without ending any in process jobs might be strange. Perhaps handling ctrl+c when interacting with orch should be a related ticket. Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Michael Smith
During the first action that uses the PCP transport while running a plan attempt to use {{/commands/plan_start}} (providing the plan name) to get a plan_job_id. If the command is not supported by Orchestrator, continue without a plan_job_id. Other errors should halt the plan.Subsequent actions over the PCP transport should use the same plan_job_id. On completion, error, or Ctrl-C, Bolt should call {{/commands/plan_end}} if {{plan_start}} was previously used. This indicates that transports need a concept of setup and teardown.The name of nested plans are essentially ignored by the PCP transport.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title
Michael Smith updated an issue
Puppet Task Runner / BOLT-372
Associate jobs with plans when using the PCP transport
Change By:
Michael Smith
add an attribute During the first action that uses the PCP transport while running a plan attempt to use {{/commands/plan_start}} ( “ providing the plan execution id” name ) to jobs to indicate which plan execution they are part of so that in get a plan_job_id. If the PE console jobs can be associated with command is not supported by Orchestrator, continue without a plan_job_id. Other errors should halt the plan . It would also be nice to include Subsequent actions over the plan name PCP transport should use the same plan_job_id.
Add Comment
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
--
You received this message because you are subscribed to the Google Groups "Puppet Bugs" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to
Jira (BOLT-372) Associate jobs with plans when using the PCP transport
Title: Message Title Michael Smith updated an issue Puppet Task Runner / BOLT-372 Associate jobs with plans when using the PCP transport Change By: Michael Smith Summary: Associate jobs with plans for pe when using the PCP transport Add Comment This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
