Jira (FACT-909) Processor facts are incorrect in SPARC Solaris
Title: Message Title Michael Smith commented on FACT-909 Re: Processor facts are incorrect in SPARC Solaris kstat_read appears to return EACCES(13) on Solaris 10 SPARC when we call it to get cpu_info at https://github.com/puppetlabs/facter/blob/master/lib/src/util/solaris/k_stat.cc#L38. According to http://docs.oracle.com/cd/E19253-01/816-5172/kstat-read-3kstat/index.html, that error should only happen with kstat_write; I'm a bit stumped on what might be setup incorrectly. The testing instance is setup in an LDOM, which may cause to lack of permission. This problem doesn't appear to affect the kstat command-line tool, so we may have to fall-back to that on SPARC. /cc Geoffrey Gardella would love suggestions if there's other documentation I should look at related to this. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1177) Add swap facts to OpenBSD memory resolver
Title: Message Title Michael Smith updated an issue Facter / FACT-1177 Add swap facts to OpenBSD memory resolver Change By: Michael Smith Scope Change Category: Found Adopted Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1177) Add swap facts to OpenBSD memory resolver
Title: Message Title Michael Smith updated an issue Facter / FACT-1177 Add swap facts to OpenBSD memory resolver Change By: Michael Smith Scope Change Category: Found Scope Change Reason: CommunityPRmerged Story Points: 0 Release Notes Summary: PartofOpenBSDsupport. Sprint: Client2015-09-02 Scrum Team: ClientPlatform Release Notes: NotNeeded Add Comment
Jira (FACT-918) Virtualization facts are incorrect in SPARC Solaris LDoms
Title: Message Title Michael Smith assigned an issue to Michael Smith Facter / FACT-918 Virtualization facts are incorrect in SPARC Solaris LDoms Change By: Michael Smith Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-918) Virtualization facts are incorrect in SPARC Solaris LDoms
Title: Message Title
Michael Smith commented on FACT-918
Re: Virtualization facts are incorrect in SPARC Solaris LDoms
$ /opt/puppetlabs/bin/facter os processors is_virtual virtual
is_virtual = true
os = {
architecture = sun4v,
family = Solaris,
hardware = sun4v,
name = Solaris,
release = {
full = 10.0,
major = 10,
minor = 0
Jira (PUP-5063) Puppet 4 --profile is not complete compared to 3
Title: Message Title Henrik Lindberg commented on PUP-5063 Re: Puppet 4 --profile is not complete compared to 3 Very likely that profiling is not called for 4.x function calls. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5063) Puppet 4 --profile is not complete compared to 3
Title: Message Title Kylo Ginsberg commented on PUP-5063 Re: Puppet 4 --profile is not complete compared to 3 Ping Henrik Lindberg. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1179) Investigate improving dmi facts in SPARC Solaris
Title: Message Title
Michael Smith updated an issue
Facter / FACT-1179
Investigate improving dmi facts in SPARC Solaris
Change By:
Michael Smith
Investigatebetterwaystoimplement{{serialnumber}}lookup-itcurrentlyrelieson{{SUNWsneep}},whichisnotpartofadefaultinstall.Severalotherdmifacts -{{bios.release_date}},{{bios.vendor}},{{bios.version}},{{chassis.asset_tag}},{{chassis.type}},{{product.uuid}}- arealsonotyetimplementedonSPARC.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5103) Puppet is checking attributes in a strict consecutive order
Title: Message Title Kylo Ginsberg commented on PUP-5103 Re: Puppet is checking attributes in a strict consecutive order Eric B. Hymowitz can you try this out with a current puppet release, either 3.8.2 or 4.2.1? Thanks! Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-915) Serialnumber fact doesn't resolve in SPARC Solaris
Title: Message Title Michael Smith assigned an issue to Michael Smith Facter / FACT-915 Serialnumber fact doesn't resolve in SPARC Solaris Change By: Michael Smith Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4892) Create catalog_metadata model and JSON and REST termini
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4892
Create catalog_metadata model and JSON and REST termini
Change By:
Josh Cooper
Createacatalog_metadatamodel containing{{catalog_id}} and a JSONandREST terminii termini forserializinglocallyandremotely. Themodelshouldcontain: {code:json}{properties:{mode:{enum:[normal,cached]},use_code_id:{type:string}},required:[mode,use_code_id],}{code} Addcatalog_metadatatoschemaandapidocs.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4892) Create catalog_metadata model and JSON and REST termini
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4892 Create catalog_metadata model and JSON and REST termini Change By: Josh Cooper Story Points: 3 2 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4893) Update configurer to send catalog_metadata request
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4893
Update configurer to send catalog_metadata request
Change By:
Josh Cooper
Theconfigurershouldbemodifiedto loaditscurrent senda {{catalog_metadata}} ,extractthe requestpriortoits {{ catalog_id node }} .Aftersendingitsnode request andbeforepluginsync,theconfigurershouldsenda .The{{ catalog_metadata }} request shouldincludeits{{cached_code_id}},{{desired_code_id}},and{{job_id}}.Theresponse ( find asspecifiedinPUP-4892 ) sendingalongits shouldbecachedin {{ catalog_id $client_data/catalog_metadata/host.json }} usingtheJSONterminus . The configurer {{cached_code_id}} should process beobtainedbyloading the responseandeitherskiptherun,useits cached catalog {{catalog_metadata}}object , ordoanormalrun andusingthe{{use_code_id}}fieldwithin . Iftold The{{desired_code_id}}and{{job_id}}default to doa nil,butmaybespecifiedontheagent'scommandline.Thisticketshouldassumethattheserveralwaysrespondswith{{( normal run , save nil)}}.Additionalticketswillhandle the newcatalog_metadata caseswheretheserverrespondswith{{cached}}oraspecific{{code_id}}touse .
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit
Jira (PUP-4893) Update configurer to send catalog_metadata request
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4893 Update configurer to send catalog_metadata request Change By: Josh Cooper Story Points: 3 5 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PDB-1210) PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger
Title: Message Title Kylo Ginsberg commented on PDB-1210 Re: PSQLException: Can't infer the SQL type to use for an instance of java.math.BigInteger Circling back to this one, here are a couple misc notes: Background re facter: the GCE facts are created mechanically by processing the json blob returned by GCE and described at https://cloud.google.com/compute/docs/metadata?hl=en. (Btw, I can't find a json schema for that API, but the sample at https://github.com/puppetlabs/facter/blob/2.x/spec/fixtures/unit/gce/metadata/metadata.json#L14 uses that field as an integer.) Re fixing it in facter: We could definitely special case handling of that one fact in facter (and force it to be a string). I'm not opposed to doing that to relieve an immediate pain point, but it feels like it's kicking the can down the road. In general I think we should decide what contract we want the puppet ecosystem to support wrt integer types, and then: update components as needed. This may merit some discussion, e.g. if we decide we want to retain the current PDB limits of signed 64-bit, I wonder if that should be enforced in puppet rather than in facter, since facter knows nothing of pdb and puppet is the actual interface point. enforce that contract as gracefully as possible. Wrt PDB, I definitely don't know what the options are to improve things (and I suppose that's what this ticket is about) Thoughts? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- You received this message because you are subscribed to the Google Groups Puppet Bugs group. To unsubscribe from this group
Jira (FACT-918) Virtualization facts are incorrect in SPARC Solaris LDoms
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-918 Virtualization facts are incorrect in SPARC Solaris LDoms Change By: Michael Smith Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-3318) Puppet prints warning when environment is set using classifier rather than local puppet.conf
Title: Message Title Michael Smith assigned an issue to qa Puppet / PUP-3318 Puppet prints warning when environment is set using classifier rather than local puppet.conf Change By: Michael Smith Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1177) Add swap facts to OpenBSD memory resolver
Title: Message Title Michael Smith assigned an issue to qa Facter / FACT-1177 Add swap facts to OpenBSD memory resolver Change By: Michael Smith Status: Readyfor CI Test Assignee: qa Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5103) Puppet is checking attributes in a strict consecutive order
Title: Message Title Kylo Ginsberg assigned an issue to Eric B. Hymowitz Puppet / PUP-5103 Puppet is checking attributes in a strict consecutive order Change By: Kylo Ginsberg Assignee: KyloGinsberg EricB.Hymowitz Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-911) manufacturer and productname facts are missing in SPARC Solaris
Title: Message Title Michael Smith assigned an issue to Michael Smith Facter / FACT-911 manufacturer and productname facts are missing in SPARC Solaris Change By: Michael Smith Assignee: MichaelSmith Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-911) manufacturer and productname facts are missing in SPARC Solaris
Title: Message Title Michael Smith commented on FACT-911 Re: manufacturer and productname facts are missing in SPARC Solaris William Hopper I don't see serialnumber in Facter 2.4.4 output, you sure that was present on SPARC? Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (FACT-1179) Investigate improving dmi facts in SPARC Solaris
Title: Message Title Michael Smith created an issue Facter / FACT-1179 Investigate improving dmi facts in SPARC Solaris Issue Type: New Feature Assignee: Unassigned Created: 2015/08/30 8:09 PM Fix Versions: FACT 3.x Priority: Normal Reporter: Michael Smith Investigate better ways to implement serialnumber lookup - it currently relies on SUNWsneep, which is not part of a default install. Several other dmi facts are also not yet implemented on SPARC. Add Comment
Jira (PUP-5110) Refactor configurer.rb to support different application modes
Title: Message Title Josh Cooper created an issue Puppet / PUP-5110 Refactor configurer.rb to support different application modes Issue Type: Task Assignee: Unassigned Created: 2015/08/30 8:44 PM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper Currently Configurer contains a single method for all of the apply/agent logic. The method can either be passed the catalog, e.g. from puppet apply, load the catalog from cache, or retrieve the catalog from the master. Depending on which mode we're in, we sometimes send a node request, sometimes send facts and pluginsync. This ticket is to refactor the Configurer logic to support each mode, so it's possible to reason about what actions are performed when running puppet apply (manifest) vs puppet apply (catalog) vs puppet agent (retrieves a new catalog) vs puppet agent (and use_cached_catalog=true). And in the future, we'll be adding puppet agent (and is told to reuse it's cached catalog). I'm giving this a high estimate because we need to do some design work about how this should work, and there is a lot of interdependent code, e.g. FactHandler is mixed into Configurer and calling FactHandler#find_facts can change global state Puppet[:node_name_value] unexpectedly.
Jira (PUP-5111) Implement logic for applying a cached catalog when told to do so by the catalog_metadata response
Title: Message Title Josh Cooper created an issue Puppet / PUP-5111 Implement logic for applying a cached catalog when told to do so by the catalog_metadata response Issue Type: New Feature Assignee: Unassigned Created: 2015/08/30 8:51 PM Priority: Normal Reporter: Josh Cooper The catalog_metadata response may tell the agent to apply a cached catalog, and specify which code_id to use.. This ticket is to support that mode of catalog application. The logic for loading a cached catalog is similar what we do now when use_cached_catalog is true. The agent should skip the node, pluginsync and catalog requests, apply the catalog, and send a report. The report specific changes are covered in PUP-4891. The agent should send its current code_id for all requests after catalog_metadata. Add Comment
Jira (PUP-5112) Add code_content model and REST terminus
Title: Message Title Josh Cooper created an issue Puppet / PUP-5112 Add code_content model and REST terminus Issue Type: New Feature Assignee: Unassigned Created: 2015/08/30 9:04 PM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper Add code_content model in puppet/file_serving/code_content.rb. It should have a line like: indirects :code_content, :terminus_class = :rest It should only support `binary` format as the serialization format. It should have a from_binary method, that creates an instance of the model, and sets its contents to whatever was passed in. It would be nice if we supported streaming, e.g. caller provides an IO object, but it's not required given that we don't support streaming with the file_content model. We should raise if to_binary is ever called, as the agent will only get code content, not send, and this code
Jira (PUP-5114) Retrieve content using content_uri
Title: Message Title Josh Cooper created an issue Puppet / PUP-5114 Retrieve content using content_uri Issue Type: New Feature Assignee: Unassigned Created: 2015/08/30 9:19 PM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper Modify the catalog application process to retrieve content for file resources using the content_uri parameter instead of source. This affects: Puppet::Type::File::Source#content Puppet::Type::File::Content#get_from_source For example, instead of calling
Jira (PUP-5116) Handle error if catalog request fails due to code mismatch
Title: Message Title Josh Cooper created an issue Puppet / PUP-5116 Handle error if catalog request fails due to code mismatch Issue Type: New Feature Assignee: Unassigned Created: 2015/08/30 9:29 PM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper The catalog_metadata endpoint may tell the agent to request a new catalog and give it the code_id to use. The agent's catalog request for that code_id may fail if the code was updated in between. The agent should have logic for handling this error. Add Comment
Jira (PUP-4900) Fail compilation if client catalog version doesn't match
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4900
Fail compilation if client catalog version doesn't match
Change By:
Josh Cooper
The{{compiler}}catalogterminusshouldfailthecompilation,iftheclientrequestsa{{ catalog_id desired_code_id }}thatdoesnotmatchtheserver's{{ catalog_id code_id }}.Thiscanhappenifthecatalog_metadatasaystouseversionA,butbeforetheagentrequeststhecatalog,newcodeispromoted,andthecompilerwillhavenowaytoproduceacatalogforversionA. Inthefuture,theservercouldtelltheagenttoretry,sostarttherunover,sendcatalog_metadatarequest,etc.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5111) Implement logic for applying a cached catalog when told to do so by the catalog_metadata response
Title: Message Title Josh Cooper updated an issue Puppet / PUP-5111 Implement logic for applying a cached catalog when told to do so by the catalog_metadata response Change By: Josh Cooper Fix Version/s: PUP4.3.0 Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5113) Support HTTP API versioning changes
Title: Message Title Josh Cooper created an issue Puppet / PUP-5113 Support HTTP API versioning changes Issue Type: Task Assignee: Unassigned Created: 2015/08/30 9:07 PM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper We may create the code_content REST API in the v3 namespace, or we may create a v4 namespace. The latter will be more work for the client as we can't mix and match APIs from different versions. Add Comment
Jira (PUP-5115) Send code_id in all requests
Title: Message Title Josh Cooper created an issue Puppet / PUP-5115 Send code_id in all requests Issue Type: New Feature Assignee: Unassigned Created: 2015/08/30 9:25 PM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper The agent should send its current code_id in all REST requests after catalog_metadata, e.g. node, file_metadata, file_content, catalog, code_content, report, etc. The value of code_id can be nil. Add Comment
Jira (PUP-5111) Implement logic for applying a cached catalog when told to do so by the catalog_metadata response
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-5111
Implement logic for applying a cached catalog when told to do so by the catalog_metadata response
Change By:
Josh Cooper
The{{catalog_metadata}}responsemaytelltheagenttoapplyacachedcatalog,andspecifywhich{{code_id}}touse..Thisticketistosupportthatmodeofcatalogapplication.Thelogicforloadingacachedcatalogissimilarwhatwedonowwhen{{use_cached_catalog}}istrue.Theagentshouldskipthenode,pluginsyncandcatalogrequests,applythecatalog,andsendareport.ThereportspecificchangesarecoveredinPUP-4891. Theagentshouldsenditscurrent{{code_id}}forallrequestsafter{{catalog_metadata}}.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5120) File metadata inlining should handle unspecified checksum types
Title: Message Title Josh Cooper created an issue Puppet / PUP-5120 File metadata inlining should handle unspecified checksum types Issue Type: Task Assignee: Unassigned Created: 2015/08/30 10:20 PM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper Currently, when the agent applies a catalog, it sends a file_metadata request for each file resource along with the checksum_type that the master should use to compute the checksum. The checksum_type is either specified in the manifest and contained in the JSON catalog, or if none was specified, then the agent gets to choose the default value based on Puppet[:digest_algorithm]. The latter is problematic because the master won't know what the agent's digest algorithm is. When direct puppet is enabled, the file metadata inlining process will need to choose a digest algorithm if none is specified. It could either use the Puppet[:digest_algorithm] on the master (which may not be suitable for the agent), it could hardcode to md5 (as is the default digest algorithm), or something else. See PUP-1840 for background.
Jira (PUP-5117) Inline file metadata
Title: Message Title Josh Cooper created an issue Puppet / PUP-5117 Inline file metadata Issue Type: New Feature Assignee: Unassigned Created: 2015/08/30 9:45 PM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper If direct puppet is enabled for the request's environment, the compiler should inline file metadata for file resources that have a source parameter and whose ensure is not absent. It should handle file, directory and links, including owner, group, mode. For files, it should also include checksum_value, checksum, and content_uri of the resolved file path relative to Puppet[:codedir]. This ticket should only handle cases where the content is in codedir. Add Comment
Jira (PUP-5119) Handle file sources outside codedir
Title: Message Title Josh Cooper created an issue Puppet / PUP-5119 Handle file sources outside codedir Issue Type: New Feature Assignee: Unassigned Created: 2015/08/30 10:04 PM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper When inlining file metadata, the compiler should skip file sources that are outside codedir, e.g. custom mount points. The agent should continue to retrieve latest metadata and content using the existing file_metadata and file_content endpoints without any changes to the agent. Add Comment
Jira (PUP-5121) Add profiling for file inlining
Title: Message Title Josh Cooper created an issue Puppet / PUP-5121 Add profiling for file inlining Issue Type: New Feature Assignee: Unassigned Created: 2015/08/30 10:22 PM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper Add profiling metrics when inlining file metadata. Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
Jira (PUP-4891) Add code_id and related fields to report
Title: Message Title Josh Cooper updated an issue Puppet / PUP-4891 Add code_id and related fields to report Change By: Josh Cooper Summary: Add catalog_id code_idandrelatedfields toreport Add Comment This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) -- 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 http://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.
Jira (PUP-4891) Add catalog_id to report
Title: Message Title
Josh Cooper updated an issue
Puppet / PUP-4891
Add catalog_id to report
Change By:
Josh Cooper
Add a{{catalog_id}} fields to{{Puppet::Transaction::Report}} whichis :{{code_id}}-fromthecatalog,maybenil(FOSS){{catalog_uuid}}-fromthecatalog,shouldnotbenil{{job_id}}-fromthecommandline,maybenil{{cached_catalog}}-whethertheagentappliedacachedcatalogornot.Thefieldsshouldbe serialized over with the wire catalog .Alsoupdatethereportschemaandapidocs.
Add Comment
This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c)
--
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 http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.
Jira (PUP-5118) Handle duplicate resources when inlining file metadata
Title: Message Title
Josh Cooper created an issue
Puppet / PUP-5118
Handle duplicate resources when inlining file metadata
Issue Type:
New Feature
Assignee:
Unassigned
Created:
2015/08/30 10:01 PM
Fix Versions:
PUP 4.3.0
Priority:
Normal
Reporter:
Josh Cooper
Given a manifest like:
file { '/path/to/dir':
ensure = directory,
recurse = true,
source = 'puppet:///modules/foo/dir'
Jira (PUP-5122) Acceptance tests for direct puppet running from cache
Title: Message Title Josh Cooper created an issue Puppet / PUP-5122 Acceptance tests for direct puppet running from cache Issue Type: Task Assignee: Unassigned Created: 2015/08/30 10:40 PM Fix Versions: PUP 4.3.0 Priority: Normal Reporter: Josh Cooper Add acceptance tests for the scenario where the server tells the agent to run from its cached catalog containing file resources and remediates local drift to file content. This will require either server settings to execute scripts for retrieving code_id and related code, or the perhaps test only settings or environment variables to control which code_id it returns. Add Comment
