Jira (BOLT-804) Bolt unable to connect to customer windows 2012 server over winrm
Title: Message Title Marc McKinley updated an issue Puppet Task Runner / BOLT-804 Bolt unable to connect to customer windows 2012 server over winrm Change By: Marc McKinley Priority: Normal Blocker 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-791) Support running a task on a proxy node targeting a device or API with run-on
Title: Message Title David Schmitt commented on BOLT-791 Re: Support running a task on a proxy node targeting a device or API with run-on This sounds very much like what devices would need from bolt. I'd love to see an end-to-end example of how this will look like to the user to get a better understanding of the proposed UX. Open questions: would the _target metaparam contain the device's credentials (or credential reference) similar to the device.conf of puppet device? how does bolt connect to the run-on proxy node? Is that "just" a reference to another target in the inventory? 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-791) Support running a task on a proxy node targeting a device or API with run-on
Title: Message Title
David Schmitt updated an issue
Puppet Task Runner / BOLT-791
Support running a task on a proxy node targeting a device or API with run-on
Change By:
David Schmitt
h2. ProblemSome tasks such as those targetting network devices or HTTP APIs may execute on a proxy target but in the users mind the target is the device or HTTP API itself. Bolt should support this in a more natural fashion by allowing targets to specify arbitrary connection information and a reference to a different target to run-on.h2. ProposalWe should support run-on as an option for bolt targets that specifies the target is remote.h4. Task spec changesmetadata should support a new {{remote: true}} option. When set the task runner will run the task on the 'run-on' value for the target and pass a new _target metaparam to the task that includes the real target's config.h4. Inventory changes*A new top level option on targets "run-on".*targets will with run-on set will fail for all run_* commands except run_task where the task has remote: true.* The config for targets with run-on will accept arbitrary values* setting run-on and a transport will fail.h4. Plan language changes* The Target object in the plan language should expose run_on as an attribute of targets that is undef unless run-on is set.h2. Questions* What should we call the run-on option? run-on/proxy ?* What should transport be for run-on nodes? 'remote' * Do we need to support anything other than remote tasks?* When should other run_* fail.
Add Comment
This message was se
Jira (PUP-8987) add resource_api gem to puppet gemspec
Title: Message Title David Schmitt updated an issue Puppet / PUP-8987 add resource_api gem to puppet gemspec Change By: David Schmitt Team: Network Automation 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 (PUP-8987) add resource_api gem to puppet gemspec
Title: Message Title David Schmitt commented on PUP-8987 Re: add resource_api gem to puppet gemspec Yes. 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 (PUP-9086) Add dummy job to local Jenkins deployment
Title: Message Title Mihai Buzgau commented on PUP-9086 Re: Add dummy job to local Jenkins deployment Example on how to add tests can be found here: https://github.com/puppetlabs/ci-job-configs/tree/d0e65b5f9b5de83e5ccc3646dc94109464151d44/jenkii/localhost/projects You can upload a project using jenkins-jobs CLI: example: jenkins-jobs --conf jenkii/localhost/builder.conf update resources:jenkii/platform/projects/puppet-agent.yaml 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 (PUP-9085) Setup local Jenkins server
Title: Message Title Mihai Buzgau commented on PUP-9085 Re: Setup local Jenkins server I was able to setup a local Jenkins server using Vagrant. The local setup doesn't seem to be vey useful for running the PA jobs. Most of the Jobs have hardcoded credentials example: https://github.com/puppetlabs/ci-job-configs/blob/master/jenkii/platform/builder.conf https://github.com/puppetlabs/ci-job-configs/blob/d0e65b5f9b5de83e5ccc3646dc94109464151d44/resources/job-groups/modules.yaml#L248 Thus, running the tests on the local Jenkins server might be destructive 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 (PUP-8942) Support issuing certificates with IP Address Subject Alternative Names
Title: Message Title
Jeffrey Clark commented on PUP-8942
Re: Support issuing certificates with IP Address Subject Alternative Names
A quick monkey patch, and IP sans signing works.
require 'puppet/ssl/certificate_factory'
require 'puppet/ssl/certificate_authority'
# PUP-8942 doesnt work, so make it work
module Puppet::SSL::CertificateAuthorityExtensions
def check_internal_signing_policies(hostname, csr, options = {})
begin
return super
rescue Puppet::SSL::CertificateAuthority::CertificateSigningError => msg
if msg.to_s.include?('contains a subjectAltName outside the DNS label space')
return true
end
raise
Jira (PUP-9087) Investigate process for building the PA
Title: Message Title Mihai Buzgau assigned an issue to Sebastian Miclea Puppet / PUP-9087 Investigate process for building the PA Change By: Mihai Buzgau Assignee: Sebastian Miclea 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 (PUP-9086) Add dummy job to local Jenkins deployment
Title: Message Title Mihai Buzgau assigned an issue to Mihai Buzgau Puppet / PUP-9086 Add dummy job to local Jenkins deployment Change By: Mihai Buzgau Assignee: Mihai Buzgau 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 (PUP-9084) Build CI image for Ubuntu 18.10 x86
Title: Message Title Sebastian Miclea commented on PUP-9084 Re: Build CI image for Ubuntu 18.10 x86 I managed to build the images for vmware.base.json and vmware.vsphere.nocm.json for Ubuntu 18.10 Notes: -new template files need to be committed in git in order to be discovered when building the image Notes for vmware.vsphere.nocm.json: -this image is being built upon the vmware.base.json, first you have to build the vmware.base.json image and use the resulted vmware image as source when building for vsphere. Example: platform-ci-utils imaging-packer-build ubuntu/18.10/x86_64 vmware.vsphere.nocm.json --packer_repo_path=/Users/sebastian.miclea/projects/puppetlabs-packer --packer-vm-src-dir=/Users/sebastian.miclea/projects/tmp/packer/src --packer-cache-dir=/Users/sebastian.miclea/projects/tmp/packer/cache --packer-vm-out-dir=/Users/sebastian.miclea/projects/tmp/packer/out 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.
