[jira] [Commented] (OAK-6179) Simplify collecting Oak setup details via Felix Inventory
[ https://issues.apache.org/jira/browse/OAK-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16019137#comment-16019137 ] Chetan Mehrotra commented on OAK-6179: -- Added optional dependency on Felix Inventory Bundle. > Simplify collecting Oak setup details via Felix Inventory > - > > Key: OAK-6179 > URL: https://issues.apache.org/jira/browse/OAK-6179 > Project: Jackrabbit Oak > Issue Type: Improvement > Components: core >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra >Priority: Minor > Fix For: 1.7.0, 1.8 > > Attachments: OAK-6179-v1.patch > > > Felix Inventory Support [1] provides a way for various components to provide > a dump of setup state in text or json format. Oak should provide inventory > printers which collect state across various sub systems so that we can > understand an Oak based setup in a better way. > For now we expose quite bit of information via JMX which helps if we have > access to the setup. With inventory support we can request the system admin > to provide a zip file which would contain dump from various inventory > printers. > Some possible printers > # Index Stats - Printer to dump stats related to various indexes. Build on > top of OAK-6080 > # Index Definitions - Dump of index definition in json format > # Checkpoints - Dump state of all checkpoints live in the setup > # DocumentNodeStore > ## Mongo - Dump indexes in Mongo, version, replica set info > ## ClusterNodeInfo - Dump state of all cluster nodes in the setup > *Implementation Note* > To use this we would need to add an optional dependency on Felix Inventory > Bundle. However we can inline the package and reimport that such that Oak can > be used in setups where this bundle is not present and if its present it gets > integrated in Felix WebConsole > [Discussion thread on oak-dev|http://markmail.org/thread/vrmptbzmgs34vyxr] > [1] > http://felix.apache.org/documentation/subprojects/apache-felix-inventory.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-6179) Simplify collecting Oak setup details via Felix Inventory
[ https://issues.apache.org/jira/browse/OAK-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007890#comment-16007890 ] Robert Munteanu commented on OAK-6179: -- Agreed, that makes sense for other oak modules. > Simplify collecting Oak setup details via Felix Inventory > - > > Key: OAK-6179 > URL: https://issues.apache.org/jira/browse/OAK-6179 > Project: Jackrabbit Oak > Issue Type: Epic > Components: core >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8 > > Attachments: OAK-6179-v1.patch > > > Felix Inventory Support [1] provides a way for various components to provide > a dump of setup state in text or json format. Oak should provide inventory > printers which collect state across various sub systems so that we can > understand an Oak based setup in a better way. > For now we expose quite bit of information via JMX which helps if we have > access to the setup. With inventory support we can request the system admin > to provide a zip file which would contain dump from various inventory > printers. > Some possible printers > # Index Stats - Printer to dump stats related to various indexes. Build on > top of OAK-6080 > # Index Definitions - Dump of index definition in json format > # Checkpoints - Dump state of all checkpoints live in the setup > # DocumentNodeStore > ## Mongo - Dump indexes in Mongo, version, replica set info > ## ClusterNodeInfo - Dump state of all cluster nodes in the setup > *Implementation Note* > To use this we would need to add an optional dependency on Felix Inventory > Bundle. However we can inline the package and reimport that such that Oak can > be used in setups where this bundle is not present and if its present it gets > integrated in Felix WebConsole > [Discussion thread on oak-dev|http://markmail.org/thread/vrmptbzmgs34vyxr] > [1] > http://felix.apache.org/documentation/subprojects/apache-felix-inventory.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-6179) Simplify collecting Oak setup details via Felix Inventory
[ https://issues.apache.org/jira/browse/OAK-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007888#comment-16007888 ] Chetan Mehrotra commented on OAK-6179: -- [~rombert] For now I added an optional maven dependency which makes the import optional. Also when oak-core is used by some other app the core logic flow would not require the inventory bundle. The printers would only get activated in OSGi env or someone has to explicitly use them > Simplify collecting Oak setup details via Felix Inventory > - > > Key: OAK-6179 > URL: https://issues.apache.org/jira/browse/OAK-6179 > Project: Jackrabbit Oak > Issue Type: Epic > Components: core >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8 > > Attachments: OAK-6179-v1.patch > > > Felix Inventory Support [1] provides a way for various components to provide > a dump of setup state in text or json format. Oak should provide inventory > printers which collect state across various sub systems so that we can > understand an Oak based setup in a better way. > For now we expose quite bit of information via JMX which helps if we have > access to the setup. With inventory support we can request the system admin > to provide a zip file which would contain dump from various inventory > printers. > Some possible printers > # Index Stats - Printer to dump stats related to various indexes. Build on > top of OAK-6080 > # Index Definitions - Dump of index definition in json format > # Checkpoints - Dump state of all checkpoints live in the setup > # DocumentNodeStore > ## Mongo - Dump indexes in Mongo, version, replica set info > ## ClusterNodeInfo - Dump state of all cluster nodes in the setup > *Implementation Note* > To use this we would need to add an optional dependency on Felix Inventory > Bundle. However we can inline the package and reimport that such that Oak can > be used in setups where this bundle is not present and if its present it gets > integrated in Felix WebConsole > [Discussion thread on oak-dev|http://markmail.org/thread/vrmptbzmgs34vyxr] > [1] > http://felix.apache.org/documentation/subprojects/apache-felix-inventory.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-6179) Simplify collecting Oak setup details via Felix Inventory
[ https://issues.apache.org/jira/browse/OAK-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16007886#comment-16007886 ] Robert Munteanu commented on OAK-6179: -- Looking at what optional does in Maven I don't think it's required here as you will always need the jar at compile time. It only makes the dependency not available transitively, which I'm not sure is desired here. So the simplest way might be to just have an optional OSGi Import-Package, as it exists in your patch. > Simplify collecting Oak setup details via Felix Inventory > - > > Key: OAK-6179 > URL: https://issues.apache.org/jira/browse/OAK-6179 > Project: Jackrabbit Oak > Issue Type: Epic > Components: core >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8 > > Attachments: OAK-6179-v1.patch > > > Felix Inventory Support [1] provides a way for various components to provide > a dump of setup state in text or json format. Oak should provide inventory > printers which collect state across various sub systems so that we can > understand an Oak based setup in a better way. > For now we expose quite bit of information via JMX which helps if we have > access to the setup. With inventory support we can request the system admin > to provide a zip file which would contain dump from various inventory > printers. > Some possible printers > # Index Stats - Printer to dump stats related to various indexes. Build on > top of OAK-6080 > # Index Definitions - Dump of index definition in json format > # Checkpoints - Dump state of all checkpoints live in the setup > # DocumentNodeStore > ## Mongo - Dump indexes in Mongo, version, replica set info > ## ClusterNodeInfo - Dump state of all cluster nodes in the setup > *Implementation Note* > To use this we would need to add an optional dependency on Felix Inventory > Bundle. However we can inline the package and reimport that such that Oak can > be used in setups where this bundle is not present and if its present it gets > integrated in Felix WebConsole > [Discussion thread on oak-dev|http://markmail.org/thread/vrmptbzmgs34vyxr] > [1] > http://felix.apache.org/documentation/subprojects/apache-felix-inventory.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-6179) Simplify collecting Oak setup details via Felix Inventory
[ https://issues.apache.org/jira/browse/OAK-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004339#comment-16004339 ] Carsten Ziegeler commented on OAK-6179: --- [~chetanm] Simply add the inventory jar in that case - I think embedding this will cause for trouble at some point > Simplify collecting Oak setup details via Felix Inventory > - > > Key: OAK-6179 > URL: https://issues.apache.org/jira/browse/OAK-6179 > Project: Jackrabbit Oak > Issue Type: Epic > Components: core >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8 > > Attachments: OAK-6179-v1.patch > > > Felix Inventory Support [1] provides a way for various components to provide > a dump of setup state in text or json format. Oak should provide inventory > printers which collect state across various sub systems so that we can > understand an Oak based setup in a better way. > For now we expose quite bit of information via JMX which helps if we have > access to the setup. With inventory support we can request the system admin > to provide a zip file which would contain dump from various inventory > printers. > Some possible printers > # Index Stats - Printer to dump stats related to various indexes. Build on > top of OAK-6080 > # Index Definitions - Dump of index definition in json format > # Checkpoints - Dump state of all checkpoints live in the setup > # DocumentNodeStore > ## Mongo - Dump indexes in Mongo, version, replica set info > ## ClusterNodeInfo - Dump state of all cluster nodes in the setup > *Implementation Note* > To use this we would need to add an optional dependency on Felix Inventory > Bundle. However we can inline the package and reimport that such that Oak can > be used in setups where this bundle is not present and if its present it gets > integrated in Felix WebConsole > [Discussion thread on oak-dev|http://markmail.org/thread/vrmptbzmgs34vyxr] > [1] > http://felix.apache.org/documentation/subprojects/apache-felix-inventory.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-6179) Simplify collecting Oak setup details via Felix Inventory
[ https://issues.apache.org/jira/browse/OAK-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004332#comment-16004332 ] Chetan Mehrotra commented on OAK-6179: -- bq. So I would rather not embed this as a private package [~cziegeler] That was done so that these printers can be used in non OSGi environments without explicit dependency on Felix Inventory Bundle > Simplify collecting Oak setup details via Felix Inventory > - > > Key: OAK-6179 > URL: https://issues.apache.org/jira/browse/OAK-6179 > Project: Jackrabbit Oak > Issue Type: Epic > Components: core >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8 > > Attachments: OAK-6179-v1.patch > > > Felix Inventory Support [1] provides a way for various components to provide > a dump of setup state in text or json format. Oak should provide inventory > printers which collect state across various sub systems so that we can > understand an Oak based setup in a better way. > For now we expose quite bit of information via JMX which helps if we have > access to the setup. With inventory support we can request the system admin > to provide a zip file which would contain dump from various inventory > printers. > Some possible printers > # Index Stats - Printer to dump stats related to various indexes. Build on > top of OAK-6080 > # Index Definitions - Dump of index definition in json format > # Checkpoints - Dump state of all checkpoints live in the setup > # DocumentNodeStore > ## Mongo - Dump indexes in Mongo, version, replica set info > ## ClusterNodeInfo - Dump state of all cluster nodes in the setup > *Implementation Note* > To use this we would need to add an optional dependency on Felix Inventory > Bundle. However we can inline the package and reimport that such that Oak can > be used in setups where this bundle is not present and if its present it gets > integrated in Felix WebConsole > [Discussion thread on oak-dev|http://markmail.org/thread/vrmptbzmgs34vyxr] > [1] > http://felix.apache.org/documentation/subprojects/apache-felix-inventory.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (OAK-6179) Simplify collecting Oak setup details via Felix Inventory
[ https://issues.apache.org/jira/browse/OAK-6179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16004295#comment-16004295 ] Carsten Ziegeler commented on OAK-6179: --- [~chetanm] Not 100% sure, but I think that would work. However as you mark the import already as optional the bundle will work without inventory being present, just the inventory printers would not work which is fine. So I would rather not embed this as a private package > Simplify collecting Oak setup details via Felix Inventory > - > > Key: OAK-6179 > URL: https://issues.apache.org/jira/browse/OAK-6179 > Project: Jackrabbit Oak > Issue Type: Epic > Components: core >Reporter: Chetan Mehrotra >Assignee: Chetan Mehrotra > Fix For: 1.8 > > Attachments: OAK-6179-v1.patch > > > Felix Inventory Support [1] provides a way for various components to provide > a dump of setup state in text or json format. Oak should provide inventory > printers which collect state across various sub systems so that we can > understand an Oak based setup in a better way. > For now we expose quite bit of information via JMX which helps if we have > access to the setup. With inventory support we can request the system admin > to provide a zip file which would contain dump from various inventory > printers. > Some possible printers > # Index Stats - Printer to dump stats related to various indexes. Build on > top of OAK-6080 > # Index Definitions - Dump of index definition in json format > # Checkpoints - Dump state of all checkpoints live in the setup > # DocumentNodeStore > ## Mongo - Dump indexes in Mongo, version, replica set info > ## ClusterNodeInfo - Dump state of all cluster nodes in the setup > *Implementation Note* > To use this we would need to add an optional dependency on Felix Inventory > Bundle. However we can inline the package and reimport that such that Oak can > be used in setups where this bundle is not present and if its present it gets > integrated in Felix WebConsole > [Discussion thread on oak-dev|http://markmail.org/thread/vrmptbzmgs34vyxr] > [1] > http://felix.apache.org/documentation/subprojects/apache-felix-inventory.html -- This message was sent by Atlassian JIRA (v6.3.15#6346)
