From fbrychta at redhat.com Wed Jun 1 08:46:50 2016 From: fbrychta at redhat.com (Filip Brychta) Date: Wed, 1 Jun 2016 08:46:50 -0400 (EDT) Subject: [Hawkular-dev] H-metrics perf test results - Optimal message size In-Reply-To: <368803055.33331119.1464782543262.JavaMail.zimbra@redhat.com> Message-ID: <488588809.33337173.1464785210957.JavaMail.zimbra@redhat.com> Hello, I tried to find optimal message size for POST requests which will result into the highest total throughput. I tried 1, 100, 500 and 5000 metrics per request. Test: - h-metrics VM: 4 CPU cores, 8GB memory (gradually increasing heap size for WF in each test run - 1GB, 2GB, 4GB, 6GB, 8GB) - cassandra node VM: 2 CPU cores, 4GB memory Summary: - small messages (1 metrics/request) were the worst for all test runs -> total throughput ~ 4500 metrics/sec - medium messages (100 metrics/request) were performing the best almost for all test runs -> total throughput ~ 8600 -- 9000 metrics/sec - bigger messages (500 and 5000 metrics/request) were significantly worst than medium messages when having low heap size (1GB) - bigger messages were worst than medium even for bigger heap sizes but it was getting close - big messages (5000 metrics/request) overloaded h-metrics when having only 1GB heap -> Full GC all the time - when adding additional cassandra node and having sufficient heap size the bigger messages were performing better -> with sufficient heap size (4GB) and cassandra cluster the bigger messages the better performance (measured only up to 5000, I'm not sure if it make sense to try even bigger messages) Details: 4 CPU cores 1GB for WF msg size=1 4400 req/sec -> total throughput = 4400 avg-cpu: %user %nice %system %iowait %steal %idle 68.47 0.00 12.39 0.00 0.67 18.46 msg size=100 87 req/sec -> total throughput = 8700 avg-cpu: %user %nice %system %iowait %steal %idle 24.94 0.00 11.15 0.05 0.28 63.58 msg size=500 13 req/sec -> total throughput = 6500 avg-cpu: %user %nice %system %iowait %steal %idle 41.80 0.00 7.19 0.08 0.15 50.78 msg size=5000 0.879 req/sec -> total throughput = 4395 - GC all the time avg-cpu: %user %nice %system %iowait %steal %idle 66.35 0.00 4.08 0.00 0.08 29.50 =================================== 2GB for WF msg size=1 4574 req/sec -> total throughput = 4574 avg-cpu: %user %nice %system %iowait %steal %idle 67.84 0.00 12.67 0.05 0.87 18.57 msg size=100 87 req/sec -> total throughput = 8700 - GC each 5-6 minutes avg-cpu: %user %nice %system %iowait %steal %idle 26.99 0.00 10.25 0.13 0.21 62.43 msg size=500 16 req/sec -> total throughput = 8000 - GC each 1 min avg-cpu: %user %nice %system %iowait %steal %idle 28.48 0.00 8.22 0.15 0.59 62.55 msg size=5000 1.432 req/sec -> total throughput = 7160 - GC each 30s avg-cpu: %user %nice %system %iowait %steal %idle 36.44 0.00 10.04 0.18 0.08 53.27 =================================== 4GB for WF msg size=1 4498 req/sec -> total throughput = 4498 avg-cpu: %user %nice %system %iowait %steal %idle 63.28 0.00 13.03 0.03 0.58 23.10 msg size=100 90.79 req/sec -> total throughput = 9079 - GC after > 6 minutes avg-cpu: %user %nice %system %iowait %steal %idle 25.86 0.00 10.44 0.08 0.26 63.37 msg size=500 16.07 req/sec -> total throughput = 8035 - GC after > 6 minutes avg-cpu: %user %nice %system %iowait %steal %idle 23.73 0.00 8.18 0.13 0.46 67.50 msg size=5000 1.545 req/sec -> total throughput = 7725 - GC after > 6 minutes avg-cpu: %user %nice %system %iowait %steal %idle 31.35 0.00 10.20 0.05 0.16 58.24 =================================== 6GB for WF msg size=1 4556 req/sec -> total throughput = 4556 avg-cpu: %user %nice %system %iowait %steal %idle 67.59 0.00 12.24 0.15 0.50 19.52 msg size=100 86 req/sec -> total throughput = 8600 avg-cpu: %user %nice %system %iowait %steal %idle 27.40 0.00 10.36 0.13 0.28 61.83 msg size=500 18 req/sec -> total throughput = 9000 avg-cpu: %user %nice %system %iowait %steal %idle 29.30 0.00 8.49 0.18 0.26 61.77 msg size=5000 1.45 req/sec -> total throughput = 7250 avg-cpu: %user %nice %system %iowait %steal %idle 32.26 0.00 11.61 0.34 0.10 55.69 =================================== 8GB for WF msg size=1 4718 req/sec -> total throughput = 4718 avg-cpu: %user %nice %system %iowait %steal %idle 44.19 0.00 17.05 0.33 0.22 38.22 msg size=100 82.27 req/sec -> total throughput = 8227 avg-cpu: %user %nice %system %iowait %steal %idle 30.77 0.00 10.95 0.08 0.13 58.07 msg size=500 17.86 req/sec -> total throughput = 7725 avg-cpu: %user %nice %system %iowait %steal %idle 52.56 20.32 11.16 0.20 0.00 15.76 msg size=5000 failed =================================== 2GB for WF + 2 cassandra nodes msg size=1 total throughput = 6741 msg size=100 total throughput = 12900 msg size=500 total throughput = 11250 msg size=5000 total throughput = 13100 =================================== 4GB for WF + 2 cassandra nodes msg size=1 total throughput = 6533 msg size=100 total throughput = 12280 msg size=500 total throughput = 12650 msg size=5000 total throughput = 15950 Filip From lkrejci at redhat.com Wed Jun 1 12:58:26 2016 From: lkrejci at redhat.com (Lukas Krejci) Date: Wed, 01 Jun 2016 18:58:26 +0200 Subject: [Hawkular-dev] Reform Inventory REST API In-Reply-To: <3686951.SjXrC94kPK@localhost.localdomain> References: <3686951.SjXrC94kPK@localhost.localdomain> Message-ID: <29314945.zSftH06uXn@localhost.localdomain> This is feature complete and is pending a review. If you are interested, please read through the massively updated REST docs (I've written a very thorough guide to how to query for different stuff in inventory): https://github.com/metlos/hawkular-inventory/blob/264d5445d6089355057c162f038b885529e1c651/hawkular-inventory-rest-api/src/main/rest-doc/base.adoc Once this PR and also a website PR (https://github.com/hawkular/hawkular.github.io/pull/177) are merged, I think we will finally have a much more capable and "meaningful" inventory interface. With it in place, I'm looking forward to porting inventory to Tinkerpop3 and hopefully deleting large swaths of the codebase while doing that ;) On Monday, May 02, 2016 10:13:16 PM Lukas Krejci wrote: > Hi everyone, > > tl;dr > Inventory's REST API is ambiguous and doesn't reflect the generic structure > of the inventory well. Let's change that before it's too late! > > The access patterns in inventory's REST API predate the concept of the > canonical path that we now use extensively throughout the model to uniquely > identify the entities and because of that we're running into various issues > with the REST API. From slight inconveniences to outright breakage due to > ambiguous URLs. > > Here I propose a reformed REST API centered around the canonical paths. It > should have the same expressive power as the original REST API but should > not suffer from the ambiguities and should be much more cohesive and > "logical". The only thing that was possible using 1 call in the old API > that will require 2 calls in the new API is disassociation of 2 entities > (i.e. disassociate a metric from a resource, etc.). These operations are > IMHO rather rare so I am not too worried about this. > > I'd like to know your opinions on the new API: > > URIs below are defined in EBNF, > CP stands for canonical path of some entity, > REL stands for a name of some relationship (pre-defined or user defined) > > == sync endpoint > URI = "/", "sync", "/", CP; > > This is the same as it is currently. There is a parallel thread from the > last week about the evolution of sync that will be addressed, too. > > == bulk endpoint > URI = "/", "bulk"; > might go away - we have sync doing almost the same thing > > == GET URLs > > This is a little bit complex but what this does is that it enhances a > canonical path as is currently known with the ability to define filters on > each path progression step. > Basically, this is an attempt to express a graph traversal using an URL. > > ANY = ? just a URI path-escaped string representing an entity ID or > relationship name ? ; > FILTER_NAME = "type" | "id" | "name" | "cp" | "identical" | "propertyName" | > "propertyValue" ; > FILTER = FILTER_NAME , [ "=", ANY ] ; (* value is not required for the > "identical" filter *) > PATH_SEGMENT_TYPE = "t" | "e" | "mp" | "f" | "rt" | "mt" | "ot" | "r" | "m" > | "d" ; > PATH_SEGMENT_ID = ANY ; > PATH_STEP = "/", PATH_SEGMENT_TYPE, ";", PATH_SEGMENT_ID, { ";", FILTER } ; > WELL_KNOWN_REL = "contains" | "defines" | "incorporates" | "isParentOf" ; > ANY_REL = ANY ; > DIR_FILTER = ";", ( "in" | "out" | "both" ) > REL_FILTER = ( "propertyName" | "propertyValue"), "=", ANY ; > REL_STEP = "/rl;", ( WELL_KNOWN_REL | ANY_REL ), [ DIR_FILTER ], { > REL_FILTER } ; > FILTER_STEP = FILTER, { ";", FILTER } ; > RETURN_TYPE = "" | "treeHash" ; > PATH_END = ( PATH_STEP | FILTER_STEP ), RETURN_TYPE ; > URI = { ( PATH_STEP | FILTER_STEP ), [ REL_STEP ] }, [ PATH_END ]; > > The "identical" bit is currently not present in the REST API but is in the > Java API. What it'd do here is that it would "widen" the start of the query > from the one entity specified by the CP to all entities that are identical > to it according to the identity hash rules (same id, same significant > structure). > > This is useful for scenarios like "querying all EAPs". The way this would > work is that you'd have your resource type that you expect defined and a > global level, possibly contained in a metadata pack. You'd then look for > resources that are defined by the resource types identical to yours. > Because feeds are free to (re-)define their resource types, this would > match resources from feeds that have types identical to the global one. > Note that there is no special relationship needed between the types - > inventory figures this out automagically. This way we loosen the > requirement for synchronizing the updates to the types defined by feeds and > the user at the cost of "eventually consistent behavior" once the parties > upgrade at their own pace. > > === Examples > > ==== Return a tenant > > / > > ==== Access Entity By Canonical Path > > /t;tenant_id/f;feed_id/rt;resourceType_id > > This is actually equivalent to: > > /t;tenant_id/rl;contains;out/f;feed_id/rl;contains;out/rt;resourceType_id > > which is no longer a canonical path but showcases how we declare "hops" over > specific relationships. "rl;contains;out" translates to "relationship with > name contains in the outgoing direction" and is implicit, if no other "hop" > between entities is specified. > > To return the tree hash of the entity instead of the entity itself, one can: > > /f;feed_id/r;resource/treeHash > > Note that the tenant in the path is optional because it can be deduced from > the authorization details. > > ==== Accessing Targets of Relationships > > /f;feed_id/r;resource_id/rl;incorporates/type=metric > > This is equivalent to the current > `/feeds/feed_id/resources/resource_id/metrics`. > > /f;feed_id/r;resource_id/rl;isParentOf/ > > (notice the trailing slash) > "give me all children of resource with id 'resource_id'". > > ==== Accessing Relationships > > /f;feed_id/rl;contains > > (notice the lack of trailing slash) > "find all the 'contains' relationships going out of the feed with id > 'feed_id'." > > To access a single relationship with known id: > > /rl;relationship_id > > ==== More Complex Example > > > /f;feed_id/type=rt;name=My%20EAP;identical/rl;defines/type=resource/rl;isPa > rentOf/type=resource?recursive=true > > "get a feed with id 'feed_id' and find all resource types called "My EAP" > that it contains and all other resource types that are identical to it > (them). Then find all the resources that those resource types define and > find all the resources (recursively) that those resources are parents of." > > === Query Parameters > > ==== Paging `per_page`, `page`, `sort`, `order` > Paging is very expensive, because it implies fully iterating through the > result set (to be able to sort or determine the total). We may think about > some kind of server-side "live result set" that would hold the results on > the server and be accessed using some kind of token (with a TTL). This is > how neo4j does it and would avoid having to fetch the full result set on > each paged request. > > ==== `recursive` > This causes the last hop (relationship + entity filter) to be recursively > searched and added to the results. Tinkerpop defines a more generic concept > of "loop" using a label as a marker of the start of the "recursive hop" but > I don't think we need to be that powerful in a REST interface. Advanced > users may want to use the `query` endpoint with the full power of Gremlin > query. > > == POST URLs > URI = "/", CP, "/", "resource" | "metric" | "resourceType" | ...; > > The idea here is that you can create the entities only at their canonical > positions. While the Java API allows for creation after a non-canonical > traversal, I think this would be unnecessarily complicated for the REST API. > The users would pass the familiar blueprint objects to these endpoints as > they do currently. > > Examples: > > /feed - send a feed blueprint and this will create a new feed > /resourceType - send a resource type blueprint and it will create a new > global resource type > /metricType > ... > /f;feed/resourceType - creates a feed-local resource type > > == PUT URLs > URI = "/", CP > > just send an update object corresponding to the type of entity on the path > > == DELETE URLs > URI = "/", CP > > deletes the entity on the path > > disassociation needs to be 2 steps - find the relationship in question and > then > delete the relationship, e.g.: > > GET /f;feed_id/r;resource/rl;defines > DELETE /rl;id-found-in-the-results-from-the-previous-query > > == Advanced Querying > URI = "/", "query" > > free form, read-only gremlin query for more complex queries (this needs > to wait for the port to Tinkerpop3) > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev -- Lukas Krejci From snegrea at redhat.com Wed Jun 1 15:07:00 2016 From: snegrea at redhat.com (Stefan Negrea) Date: Wed, 1 Jun 2016 14:07:00 -0500 Subject: [Hawkular-dev] Hawkular Metrics 0.16.0 - Release Message-ID: Hello Everybody, I am happy to announce release 0.16.0 of Hawkular Metrics. This release is anchored by overall enhancements in the API and updates to String metric type. Here is a list of major changes: 1. String Metric Type - Enhancements - /strings endpoint was enhanced with querying capabilities similar to other metric types, including tag related features (HWKMETRICS-402 ) - The endpoints under /strings are still experimental, so changes which break backwards compatibility could be introduced in future releases. The experimental tag allows time for feedback to better determine what the API should be. 2. */stats & */raw Replace */data - second deprecation warning! - */data has been deprecated and functionality split into two single purpose endpoints, this is applicable for all metric types (gauge, counter, availability, and string) - */stats endpoints return bucketed, statistical or query-time aggregated data - */raw endpoints accept and return raw data for a metric - Please update your code to use the new endpoints and follow the release notes for more details regarding removal. - For more details: HWKMETRICS-24 , HWKMETRICS-57 3. REST API Updates - Empty buckets are now reported with default values and no samples ( HWKMETRICS-345 ) - Rate of change stats can be retrieved for Gauge metrics. This feature was exclusive for Counter metrics but was expanded to Gauge metrics. The rates are computed at query time based on stored data ( HWKMETRICS-365 ) - Min and max timestamps of stored datapoints are now returned when querying for metric definitions (HWKMETRICS-383 ) - The endpoint for fetching rates now supports standard query parameters and sort behavior (HWKMETRICS-390 ) 4. Hawkular Metrics - Hawkular Services distribution - Hawkular Metrics distribution build for inclusion in Hawkular Services is now independent of Hawkular Accounts. - Only for this distribution, the authentication is done at container level and tenant id header becomes required. - For more details: HWKMETRICS-399 , HWKMETRICS-401 Hawkular Metrics Clients - Python: https://github.com/hawkular/hawkular-client-python - Go: https://github.com/hawkular/hawkular-client-go - Ruby: https://github.com/hawkular/hawkular-client-ruby - Java: https://github.com/hawkular/hawkular-client-java Release Links Github Release: https://github.com/hawkular/hawkular-metrics/releases/tag/0.16.0 JBoss Nexus Maven artifacts: http://origin-repository.jboss.org/nexus/content/repositories/public/org/hawkular/metrics/ Jira release tracker: https://issues.jboss.org/browse/HWKMETRICS/fixforversion/12330316 A big "Thank you" goes to John Sanda, Thomas Segismont, Matt Wringe, Mike Thompson, Michael Burman, and Heiko Rupp for their project contributions. Thank you, Stefan Negrea Software Engineer -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160601/abebac9d/attachment.html From gbrown at redhat.com Thu Jun 2 03:36:06 2016 From: gbrown at redhat.com (Gary Brown) Date: Thu, 2 Jun 2016 03:36:06 -0400 (EDT) Subject: [Hawkular-dev] Hawkular Metrics 0.16.0 - Release In-Reply-To: References: Message-ID: <200931542.54391880.1464852966845.JavaMail.zimbra@redhat.com> Congratulations! Regards Gary ----- Original Message ----- > > > Hello Everybody, I am happy to announce release 0.16.0 of Hawkular Metrics. > This release is anchored by overall enhancements in the API and updates to > String metric type. > > > > Here is a list of major changes: > > 1. > > String Metric Type - Enhancements > * /strings endpoint was enhanced with querying capabilities similar > to other metric types, including tag related features ( > HWKMETRICS-402 ) > * The endpoints under /strings are still experimental, so changes > which break backwards compatibility could be introduced in future > releases. The experimental tag allows time for feedback to better > determine what the API should be. > 2. > > */stats & */raw Replace */data - second deprecation warning! > * */data has been deprecated and functionality split into two single > purpose endpoints, this is applicable for all metric types (gauge, > counter, availability, and string) > * */stats endpoints return bucketed, statistical or query-time > aggregated data > * */raw endpoints accept and return raw data for a metric > * Please update your code to use the new endpoints and follow the > release notes for more details regarding removal. > * For more details: HWKMETRICS-24 , HWKMETRICS-57 > 3. > > REST API Updates > * Empty buckets are now reported with default values and no samples ( > HWKMETRICS-345 ) > * Rate of change stats can be retrieved for Gauge metrics. This > feature was exclusive for Counter metrics but was expanded to Gauge > metrics. The rates are computed at query time based on stored data ( > HWKMETRICS-365 ) > * Min and max timestamps of stored datapoints are now returned when > querying for metric definitions ( HWKMETRICS-383 ) > * The endpoint for fetching rates now supports standard query > parameters and sort behavior ( HWKMETRICS-390 ) > 4. > > Hawkular Metrics - Hawkular Services distribution > * Hawkular Metrics distribution build for inclusion in Hawkular > Services is now independent of Hawkular Accounts. > * Only for this distribution, the authentication is done at container > level and tenant id header becomes required. > * For more details: HWKMETRICS-399 , HWKMETRICS-401 > > > > Hawkular Metrics Clients > > * Python: https://github.com/hawkular/hawkular-client-python > * Go: https://github.com/hawkular/hawkular-client-go > * Ruby: https://github.com/hawkular/hawkular-client-ruby > * Java: https://github.com/hawkular/hawkular-client-java > > Release Links > > Github Release: > https://github.com/hawkular/hawkular-metrics/releases/tag/0.16.0 > > JBoss Nexus Maven artifacts: > http://origin-repository.jboss.org/nexus/content/repositories/public/org/hawkular/metrics/ > > Jira release tracker: > https://issues.jboss.org/browse/HWKMETRICS/fixforversion/12330316 > > > A big "Thank you" goes to John Sanda, Thomas Segismont, Matt Wringe, Mike > Thompson, Michael Burman, and Heiko Rupp for their project contributions. > > > Thank you, > Stefan Negrea > > Software Engineer > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From jpkroehling at redhat.com Thu Jun 2 04:15:58 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Thu, 2 Jun 2016 10:15:58 +0200 Subject: [Hawkular-dev] SSL by default In-Reply-To: References: Message-ID: It seems that there's an effort to have this on Wildfly by default[1]. So, the only thing we would need is to redirect from HTTP to HTTPS by default. Also, the certificate is still a self signed one, although each instance would have its own certificate. So, no risk of providing the same private key to all instances of a given release. 1 - http://lists.jboss.org/pipermail/wildfly-dev/2016-June/005040.html - Juca. From tsegismo at redhat.com Thu Jun 2 08:18:54 2016 From: tsegismo at redhat.com (Thomas Segismont) Date: Thu, 2 Jun 2016 14:18:54 +0200 Subject: [Hawkular-dev] Hawkular Metrics 0.16.0 - Release In-Reply-To: References: Message-ID: The new string metric type could be used to store small text info about events in production. Such as "Feature xyz was introduced", "New firewall activated"... etc, along with a timestamp. That is a nice source for Grafana annotations[1], but could serve in our own charts as well. [1] http://docs.grafana.org/reference/annotations/ 2016-06-01 21:07 GMT+02:00 Stefan Negrea : > > > 1. > > String Metric Type - Enhancements > - /strings endpoint was enhanced with querying capabilities similar to > other metric types, including tag related features (HWKMETRICS-402 > ) > - The endpoints under /strings are still experimental, so changes > which break backwards compatibility could be introduced in future releases. > The experimental tag allows time for feedback to better determine what the > API should be. > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160602/21299d98/attachment.html From mazz at redhat.com Thu Jun 2 20:51:23 2016 From: mazz at redhat.com (John Mazzitelli) Date: Thu, 2 Jun 2016 20:51:23 -0400 (EDT) Subject: [Hawkular-dev] need peer review of commons PR In-Reply-To: <1695478453.2309473.1464915011776.JavaMail.zimbra@redhat.com> Message-ID: <1140802836.2309496.1464915083830.JavaMail.zimbra@redhat.com> I just submitted this PR: https://github.com/hawkular/hawkular-commons/pull/71 This adds some more cmdgw stuff so we can support deploying and undeploying apps to a EAP domain. I need that merged so I can get the agent to be able to use it. How are we going to work releases for commons now? Now there is so much in here, I suspect we are going to want to do releases of commons very frequently. Can anyone do a release on demand? Or is someone handling release duties for the commons repo? From garethahealy at gmail.com Sat Jun 4 16:51:08 2016 From: garethahealy at gmail.com (Gareth Healy) Date: Sat, 4 Jun 2016 21:51:08 +0100 Subject: [Hawkular-dev] Invalid persona exception Message-ID: I am trying to get hawkular working with a simple camel app ( https://github.com/fabric8io/ipaas-quickstarts/tree/master/quickstart/cdi/camel-jetty). I've got the following config: -javaagent:/deployments/bin/hawkular-btm-agent-rest-0.8.0.Final.jar -Dhawkular-btm.uri=http://172.17.0.2:8080/hawkular/btm -Dhawkular-btm.config.refresh=10 -Dhawkular-btm.username=jdoe -Dhawkular-btm.password=password -Dhawkular-btm.tenantId=d189128c-2a7b-11e6-b67b-9e71128cae77 -Dhawkular-btm.config=/deployments/lib/cdi-camel-jetty.jar/btm-org-apache-camel.json -Dhawkular-btm.log.level=FINEST I can see the rules loaded and working when i hit the endpoint: FINEST: [BusinessTransactionPublisherRESTClient] [Thread[pool-1-thread-2,5,main]] Publish btxns [tenant=d189128c-2a7b-11e6-b67b-9e71128cae77][url= http://172.17.0.2:8080/hawkular/btm/fragments]: [BusinessTransaction [id=312ffe46-392a-4e61-b476-a6eb974f24e8, startTime=1465073191501, name=null, principal=null, hostName=373b52df563f, hostAddress=172.17.0.3, nodes=[Component [componentType=JettyHttpEndpoint9, getOperation()=null, getIn()=null, getOut()=null, getNodes()=[], getBaseTime()=32847207863876, getDuration()=11775543, getFault()=null, getFaultDescription()=null, getDetails()={btm_source=org.apache.camel}, getCorrelationIds()=[], getIssues()=[]]], properties={}]] FINEST: [BusinessTransactionPublisherRESTClient] [Thread[pool-1-thread-2,5,main]] Status code is: 500 FINER: [BusinessTransactionPublisherRESTClient] [Thread[pool-1-thread-2,5,main]] Failed to publish business transaction fragments: status=[500] But the server is returning an error, stating "AccessDeniedException: Invalid persona.": 1576144 [default task-13] ERROR org.jboss.as.ejb3.invocation - WFLYEJB0034: EJB Invocation failed on component PersonaServiceImpl for method public abstract org.hawkular.accounts.api.model.Persona org.hawkular.accounts.api.PersonaService.getCurrent() javax.ejb.EJBException: org.hawkular.accounts.api.AccessDeniedException: Invalid persona. at org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:187) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277) at org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327) at org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.security.AuthorizationInterceptor.processInvocation(AuthorizationInterceptor.java:138) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636) at org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) at org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) at org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) at org.hawkular.accounts.api.PersonaService$$$view130.getCurrent(Unknown Source) at sun.reflect.GeneratedMethodAccessor491.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:436) at org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:127) at org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) at org.jboss.weld.bean.proxy.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:67) at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) at org.hawkular.accounts.api.internal.impl.PersonaService$599410865$Proxy$_$$_Weld$EnterpriseProxy$.getCurrent(Unknown Source) at sun.reflect.GeneratedMethodAccessor491.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88) at org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78) at org.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMethodProducer.java:99) at org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMemberProducer.java:161) at org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:181) at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:70) at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) at org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:179) at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:99) at org.hawkular.btm.server.security.hwkaccs.HawkularAccountsSecurityProvider.getTenantId(HawkularAccountsSecurityProvider.java:39) at org.hawkular.btm.server.rest.BusinessTransactionHandler.addBusinessTransactions(BusinessTransactionHandler.java:92) at org.hawkular.btm.server.rest.BusinessTransactionHandler$Proxy$_$$_WeldClientProxy.addBusinessTransactions(Unknown Source) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139) at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:395) at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202) at org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) at org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.keycloak.adapters.undertow.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66) at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) at io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) at io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) at io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) at io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) at io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) at io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) at io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) at io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) at io.undertow.server.handlers.MetricsHandler.handleRequest(MetricsHandler.java:62) at io.undertow.servlet.core.MetricsChainHandler.handleRequest(MetricsChainHandler.java:59) at io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) at io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) at io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) at io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:745) Caused by: org.hawkular.accounts.api.AccessDeniedException: Invalid persona. at org.hawkular.accounts.api.internal.impl.PersonaServiceImpl.getCurrent(PersonaServiceImpl.java:195) at sun.reflect.GeneratedMethodAccessor508.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) at org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) at org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) at org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64) at org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) at org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) at org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) at org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275) ... 109 more I presume its to do with the username/password options i set on the client, but not sure what i should be using if not the default user. I get this error with Alpha11 release, as well as very latest Alpha13. Any pointers would be helpful. Cheers. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160604/618f6c7d/attachment-0001.html From garethahealy at gmail.com Sun Jun 5 16:46:45 2016 From: garethahealy at gmail.com (Gareth Healy) Date: Sun, 5 Jun 2016 21:46:45 +0100 Subject: [Hawkular-dev] Invalid persona exception In-Reply-To: References: Message-ID: Problem fixed. After some more playing around, i realised that the hawkular-btm.tenantId didn't match the account organisation "jdoe" was in. Cheers. On Sat, Jun 4, 2016 at 9:51 PM, Gareth Healy wrote: > I am trying to get hawkular working with a simple camel app ( > https://github.com/fabric8io/ipaas-quickstarts/tree/master/quickstart/cdi/camel-jetty). > I've got the following config: > > -javaagent:/deployments/bin/hawkular-btm-agent-rest-0.8.0.Final.jar > -Dhawkular-btm.uri=http://172.17.0.2:8080/hawkular/btm > -Dhawkular-btm.config.refresh=10 > -Dhawkular-btm.username=jdoe > -Dhawkular-btm.password=password > -Dhawkular-btm.tenantId=d189128c-2a7b-11e6-b67b-9e71128cae77 > > -Dhawkular-btm.config=/deployments/lib/cdi-camel-jetty.jar/btm-org-apache-camel.json > -Dhawkular-btm.log.level=FINEST > > > I can see the rules loaded and working when i hit the endpoint: > > FINEST: [BusinessTransactionPublisherRESTClient] > [Thread[pool-1-thread-2,5,main]] Publish btxns > [tenant=d189128c-2a7b-11e6-b67b-9e71128cae77][url= > http://172.17.0.2:8080/hawkular/btm/fragments]: [BusinessTransaction > [id=312ffe46-392a-4e61-b476-a6eb974f24e8, startTime=1465073191501, > name=null, principal=null, hostName=373b52df563f, hostAddress=172.17.0.3, > nodes=[Component [componentType=JettyHttpEndpoint9, getOperation()=null, > getIn()=null, getOut()=null, getNodes()=[], getBaseTime()=32847207863876, > getDuration()=11775543, getFault()=null, getFaultDescription()=null, > getDetails()={btm_source=org.apache.camel}, getCorrelationIds()=[], > getIssues()=[]]], properties={}]] > FINEST: [BusinessTransactionPublisherRESTClient] > [Thread[pool-1-thread-2,5,main]] Status code is: 500 > FINER: [BusinessTransactionPublisherRESTClient] > [Thread[pool-1-thread-2,5,main]] Failed to publish business transaction > fragments: status=[500] > > But the server is returning an error, stating "AccessDeniedException: > Invalid persona.": > > 1576144 [default task-13] ERROR org.jboss.as.ejb3.invocation - > WFLYEJB0034: EJB Invocation failed on component PersonaServiceImpl for > method public abstract org.hawkular.accounts.api.model.Persona > org.hawkular.accounts.api.PersonaService.getCurrent() > javax.ejb.EJBException: org.hawkular.accounts.api.AccessDeniedException: > Invalid persona. > at > org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:187) > at > org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:277) > at > org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:327) > at > org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ejb3.component.interceptors.CurrentInvocationContextInterceptor.processInvocation(CurrentInvocationContextInterceptor.java:41) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ejb3.component.invocationmetrics.WaitTimeInterceptor.processInvocation(WaitTimeInterceptor.java:43) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ejb3.security.AuthorizationInterceptor.processInvocation(AuthorizationInterceptor.java:138) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ejb3.security.SecurityContextInterceptor.processInvocation(SecurityContextInterceptor.java:100) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ejb3.component.interceptors.ShutDownInterceptorFactory$1.processInvocation(ShutDownInterceptorFactory.java:64) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ejb3.component.interceptors.LoggingInterceptor.processInvocation(LoggingInterceptor.java:66) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ee.component.NamespaceContextInterceptor.processInvocation(NamespaceContextInterceptor.java:50) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ejb3.component.interceptors.AdditionalSetupInterceptor.processInvocation(AdditionalSetupInterceptor.java:54) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.invocation.ContextClassLoaderInterceptor.processInvocation(ContextClassLoaderInterceptor.java:64) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at > org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:636) > at > org.jboss.invocation.AccessCheckingInterceptor.processInvocation(AccessCheckingInterceptor.java:61) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at org.jboss.invocation.InterceptorContext.run(InterceptorContext.java:356) > at > org.jboss.invocation.PrivilegedWithCombinerInterceptor.processInvocation(PrivilegedWithCombinerInterceptor.java:80) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at org.jboss.as.ee.component.ViewService$View.invoke(ViewService.java:195) > at > org.jboss.as.ee.component.ViewDescription$1.processInvocation(ViewDescription.java:185) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at > org.jboss.as.ee.component.ProxyInvocationHandler.invoke(ProxyInvocationHandler.java:73) > at org.hawkular.accounts.api.PersonaService$$$view130.getCurrent(Unknown > Source) > at sun.reflect.GeneratedMethodAccessor491.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.jboss.weld.util.reflection.Reflections.invokeAndUnwrap(Reflections.java:436) > at > org.jboss.weld.bean.proxy.EnterpriseBeanProxyMethodHandler.invoke(EnterpriseBeanProxyMethodHandler.java:127) > at > org.jboss.weld.bean.proxy.EnterpriseTargetBeanInstance.invoke(EnterpriseTargetBeanInstance.java:56) > at > org.jboss.weld.bean.proxy.InjectionPointPropagatingEnterpriseTargetBeanInstance.invoke(InjectionPointPropagatingEnterpriseTargetBeanInstance.java:67) > at > org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:100) > at > org.hawkular.accounts.api.internal.impl.PersonaService$599410865$Proxy$_$$_Weld$EnterpriseProxy$.getCurrent(Unknown > Source) > at sun.reflect.GeneratedMethodAccessor491.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:88) > at > org.jboss.weld.injection.StaticMethodInjectionPoint.invoke(StaticMethodInjectionPoint.java:78) > at > org.jboss.weld.injection.producer.ProducerMethodProducer.produce(ProducerMethodProducer.java:99) > at > org.jboss.weld.injection.producer.AbstractMemberProducer.produce(AbstractMemberProducer.java:161) > at > org.jboss.weld.bean.AbstractProducerBean.create(AbstractProducerBean.java:181) > at > org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:70) > at > org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101) > at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50) > at > org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742) > at > org.jboss.weld.bean.builtin.InstanceImpl.getBeanInstance(InstanceImpl.java:179) > at org.jboss.weld.bean.builtin.InstanceImpl.get(InstanceImpl.java:99) > at > org.hawkular.btm.server.security.hwkaccs.HawkularAccountsSecurityProvider.getTenantId(HawkularAccountsSecurityProvider.java:39) > at > org.hawkular.btm.server.rest.BusinessTransactionHandler.addBusinessTransactions(BusinessTransactionHandler.java:92) > at > org.hawkular.btm.server.rest.BusinessTransactionHandler$Proxy$_$$_WeldClientProxy.addBusinessTransactions(Unknown > Source) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:139) > at > org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:295) > at > org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:249) > at > org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:236) > at > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:395) > at > org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:202) > at > org.jboss.resteasy.plugins.server.servlet.ServletContainerDispatcher.service(ServletContainerDispatcher.java:221) > at > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:56) > at > org.jboss.resteasy.plugins.server.servlet.HttpServletDispatcher.service(HttpServletDispatcher.java:51) > at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) > at > io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85) > at > io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62) > at > io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36) > at > org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78) > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at > org.keycloak.adapters.undertow.UndertowAuthenticatedActionsHandler.handleRequest(UndertowAuthenticatedActionsHandler.java:66) > at > io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131) > at > io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57) > at > io.undertow.server.handlers.DisableCacheHandler.handleRequest(DisableCacheHandler.java:33) > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at > io.undertow.security.handlers.AuthenticationConstraintHandler.handleRequest(AuthenticationConstraintHandler.java:51) > at > io.undertow.security.handlers.AbstractConfidentialityHandler.handleRequest(AbstractConfidentialityHandler.java:46) > at > io.undertow.servlet.handlers.security.ServletConfidentialityConstraintHandler.handleRequest(ServletConfidentialityConstraintHandler.java:64) > at > io.undertow.servlet.handlers.security.ServletSecurityConstraintHandler.handleRequest(ServletSecurityConstraintHandler.java:56) > at > io.undertow.security.handlers.AuthenticationMechanismsHandler.handleRequest(AuthenticationMechanismsHandler.java:60) > at > io.undertow.servlet.handlers.security.CachedAuthenticatedSessionHandler.handleRequest(CachedAuthenticatedSessionHandler.java:77) > at > io.undertow.security.handlers.NotificationReceiverHandler.handleRequest(NotificationReceiverHandler.java:50) > at > io.undertow.security.handlers.AbstractSecurityContextAssociationHandler.handleRequest(AbstractSecurityContextAssociationHandler.java:43) > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at > org.wildfly.extension.undertow.security.jacc.JACCContextIdHandler.handleRequest(JACCContextIdHandler.java:61) > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at > org.keycloak.adapters.undertow.ServletPreAuthActionsHandler.handleRequest(ServletPreAuthActionsHandler.java:69) > at > io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43) > at > io.undertow.server.handlers.MetricsHandler.handleRequest(MetricsHandler.java:62) > at > io.undertow.servlet.core.MetricsChainHandler.handleRequest(MetricsChainHandler.java:59) > at > io.undertow.servlet.handlers.ServletInitialHandler.handleFirstRequest(ServletInitialHandler.java:284) > at > io.undertow.servlet.handlers.ServletInitialHandler.dispatchRequest(ServletInitialHandler.java:263) > at > io.undertow.servlet.handlers.ServletInitialHandler.access$000(ServletInitialHandler.java:81) > at > io.undertow.servlet.handlers.ServletInitialHandler$1.handleRequest(ServletInitialHandler.java:174) > at io.undertow.server.Connectors.executeRootHandler(Connectors.java:202) > at io.undertow.server.HttpServerExchange$1.run(HttpServerExchange.java:793) > at > java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > at > java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > at java.lang.Thread.run(Thread.java:745) > Caused by: org.hawkular.accounts.api.AccessDeniedException: Invalid > persona. > at > org.hawkular.accounts.api.internal.impl.PersonaServiceImpl.getCurrent(PersonaServiceImpl.java:195) > at sun.reflect.GeneratedMethodAccessor508.invoke(Unknown Source) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at > org.jboss.as.ee.component.ManagedReferenceMethodInterceptor.processInvocation(ManagedReferenceMethodInterceptor.java:52) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at > org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.doMethodInterception(Jsr299BindingsInterceptor.java:82) > at > org.jboss.as.weld.ejb.Jsr299BindingsInterceptor.processInvocation(Jsr299BindingsInterceptor.java:93) > at > org.jboss.as.ee.component.interceptors.UserInterceptorFactory$1.processInvocation(UserInterceptorFactory.java:63) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ejb3.component.invocationmetrics.ExecutionTimeInterceptor.processInvocation(ExecutionTimeInterceptor.java:43) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.jpa.interceptor.SBInvocationInterceptor.processInvocation(SBInvocationInterceptor.java:47) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.invocation.InterceptorContext$Invocation.proceed(InterceptorContext.java:437) > at > org.jboss.weld.ejb.AbstractEJBRequestScopeActivationInterceptor.aroundInvoke(AbstractEJBRequestScopeActivationInterceptor.java:64) > at > org.jboss.as.weld.ejb.EjbRequestScopeActivationInterceptor.processInvocation(EjbRequestScopeActivationInterceptor.java:83) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ee.concurrent.ConcurrentContextInterceptor.processInvocation(ConcurrentContextInterceptor.java:45) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.invocation.InitialInterceptor.processInvocation(InitialInterceptor.java:21) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.invocation.ChainedInterceptor.processInvocation(ChainedInterceptor.java:61) > at > org.jboss.as.ee.component.interceptors.ComponentDispatcherInterceptor.processInvocation(ComponentDispatcherInterceptor.java:52) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ejb3.component.pool.PooledInstanceInterceptor.processInvocation(PooledInstanceInterceptor.java:51) > at > org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:340) > at > org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275) > ... 109 more > > I presume its to do with the username/password options i set on the > client, but not sure what i should be using if not the default user. > > I get this error with Alpha11 release, as well as very latest Alpha13. > > Any pointers would be helpful. > > Cheers. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160605/29bd997a/attachment-0001.html From gbrown at redhat.com Mon Jun 6 03:27:20 2016 From: gbrown at redhat.com (Gary Brown) Date: Mon, 6 Jun 2016 03:27:20 -0400 (EDT) Subject: [Hawkular-dev] Any objections to using gitbooks? In-Reply-To: <582386706.55212718.1465197962737.JavaMail.zimbra@redhat.com> Message-ID: <1924615614.55212837.1465198040061.JavaMail.zimbra@redhat.com> Hi Wondering if gitbooks was ever considered for the documentation? Seems ideal as we can version each book with the component(s) it relates to, and users can download a pdf version for use offline. Was thinking about experimenting with it for the updated APM docs? Any objections? Regards Gary From theute at redhat.com Mon Jun 6 04:36:15 2016 From: theute at redhat.com (Thomas Heute) Date: Mon, 6 Jun 2016 10:36:15 +0200 Subject: [Hawkular-dev] Any objections to using gitbooks? In-Reply-To: <1924615614.55212837.1465198040061.JavaMail.zimbra@redhat.com> References: <582386706.55212718.1465197962737.JavaMail.zimbra@redhat.com> <1924615614.55212837.1465198040061.JavaMail.zimbra@redhat.com> Message-ID: I mostly have concerns about having docs spread over multiple solutions. But if the plan is to move all to gitbook, it should be ok. Also we should still use AsciiDoc (I see that gitbook supports AscissDoc and Markdown) Thomas On Mon, Jun 6, 2016 at 9:27 AM, Gary Brown wrote: > Hi > > Wondering if gitbooks was ever considered for the documentation? Seems > ideal as we can version each book with the component(s) it relates to, and > users can download a pdf version for use offline. > > Was thinking about experimenting with it for the updated APM docs? > > Any objections? > > Regards > Gary > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160606/2e32ed5a/attachment.html From jpkroehling at redhat.com Tue Jun 7 05:29:10 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Tue, 7 Jun 2016 11:29:10 +0200 Subject: [Hawkular-dev] Hawkular Services 0.0.1.Final Message-ID: <83ec7dd9-5580-afbc-b93c-6eeebd6bcce3@redhat.com> Team, The first release of Hawkular Services is out: 0.0.1.Final . This should be seen as a base distribution for adjusting the current Hawkular clients to work with the authentication, authorization and tenancy changes. The plan is to have one release per week, every Tuesday. If you want to catch the release train, I'd suggest to have your component ready by Friday. The distribution can be downloaded here: https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/hawkular/services/hawkular-services-dist/0.0.1.Final/hawkular-services-dist-0.0.1.Final.zip As the previous distributions, the Agent has to be configured with an user. This can be accomplished by: - Adding an user via bin/add-user.sh like: ./bin/add-user.sh -a -u -p - Changing the Agent's credential on standalone.xml to the credentials from the previous step - Juca. From theute at redhat.com Tue Jun 7 05:35:13 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 7 Jun 2016 11:35:13 +0200 Subject: [Hawkular-dev] Hawkular Services 0.0.1.Final In-Reply-To: <83ec7dd9-5580-afbc-b93c-6eeebd6bcce3@redhat.com> References: <83ec7dd9-5580-afbc-b93c-6eeebd6bcce3@redhat.com> Message-ID: Awesome ! On Tue, Jun 7, 2016 at 11:29 AM, Juraci Paix?o Kr?hling < jpkroehling at redhat.com> wrote: > Team, > > The first release of Hawkular Services is out: 0.0.1.Final . This should > be seen as a base distribution for adjusting the current Hawkular > clients to work with the authentication, authorization and tenancy changes. > > The plan is to have one release per week, every Tuesday. If you want to > catch the release train, I'd suggest to have your component ready by > Friday. > > The distribution can be downloaded here: > > https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/hawkular/services/hawkular-services-dist/0.0.1.Final/hawkular-services-dist-0.0.1.Final.zip > > As the previous distributions, the Agent has to be configured with an > user. This can be accomplished by: > > - Adding an user via bin/add-user.sh like: > ./bin/add-user.sh -a -u -p > > - Changing the Agent's credential on standalone.xml to the credentials > from the previous step > > - Juca. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160607/994e0369/attachment.html From tsegismo at redhat.com Tue Jun 7 06:24:23 2016 From: tsegismo at redhat.com (Thomas Segismont) Date: Tue, 7 Jun 2016 12:24:23 +0200 Subject: [Hawkular-dev] CORS Filter in commons? Message-ID: Hi everyone, When Hawkular servers were secured by Keycloack, it was possible to configure allowed origins for CORS requests. Now we no longer have a common solution. Standalone Metrics has JAX-RS filters and config parameters to configure allowed headers and origins (this was developed for Openshift Metrics IIRC). The hawkular-metrics-component does not have them currently, because it used to be deployed along with Keycloack... So is there interest in sharing the Metrics solution in commons? For those who wonder what CORS support brings, it allows to develop your own web pages (dashboard or hawkular-charts) on top of Hawkular servers. Otherwise I will simply add the filters back to the Metrics component. Regards, -- Thomas Segismont JBoss ON Engineering Team -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160607/97827fde/attachment.html From theute at redhat.com Tue Jun 7 06:59:07 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 7 Jun 2016 12:59:07 +0200 Subject: [Hawkular-dev] Any objections to using gitbooks? In-Reply-To: References: <582386706.55212718.1465197962737.JavaMail.zimbra@redhat.com> <1924615614.55212837.1465198040061.JavaMail.zimbra@redhat.com> Message-ID: So Hawkular APM will give it a try... The Git repo is here: https://github.com/hawkular/hawkular-apm-user-guide And the published book will be here: https://www.gitbook.com/book/hawkular/hawkular-apm-user-guide/welcome PS: At least another project/product used it successfully it seems: Keycloak / Red Hat SSO On Mon, Jun 6, 2016 at 10:36 AM, Thomas Heute wrote: > I mostly have concerns about having docs spread over multiple solutions. > But if the plan is to move all to gitbook, it should be ok. > > Also we should still use AsciiDoc (I see that gitbook supports AscissDoc > and Markdown) > > Thomas > > On Mon, Jun 6, 2016 at 9:27 AM, Gary Brown wrote: > >> Hi >> >> Wondering if gitbooks was ever considered for the documentation? Seems >> ideal as we can version each book with the component(s) it relates to, and >> users can download a pdf version for use offline. >> >> Was thinking about experimenting with it for the updated APM docs? >> >> Any objections? >> >> Regards >> Gary >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160607/81393521/attachment.html From jshaughn at redhat.com Tue Jun 7 08:29:23 2016 From: jshaughn at redhat.com (Jay Shaughnessy) Date: Tue, 7 Jun 2016 08:29:23 -0400 Subject: [Hawkular-dev] Hawkular Services 0.0.1.Final In-Reply-To: <83ec7dd9-5580-afbc-b93c-6eeebd6bcce3@redhat.com> References: <83ec7dd9-5580-afbc-b93c-6eeebd6bcce3@redhat.com> Message-ID: Excellent! On 6/7/2016 5:29 AM, Juraci Paix?o Kr?hling wrote: > Team, > > The first release of Hawkular Services is out: 0.0.1.Final . This should > be seen as a base distribution for adjusting the current Hawkular > clients to work with the authentication, authorization and tenancy changes. > > The plan is to have one release per week, every Tuesday. If you want to > catch the release train, I'd suggest to have your component ready by Friday. > > The distribution can be downloaded here: > https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/hawkular/services/hawkular-services-dist/0.0.1.Final/hawkular-services-dist-0.0.1.Final.zip > > As the previous distributions, the Agent has to be configured with an > user. This can be accomplished by: > > - Adding an user via bin/add-user.sh like: > ./bin/add-user.sh -a -u -p > > - Changing the Agent's credential on standalone.xml to the credentials > from the previous step > > - Juca. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160607/8a7e0e64/attachment-0001.html From gbrown at redhat.com Tue Jun 7 11:36:05 2016 From: gbrown at redhat.com (Gary Brown) Date: Tue, 7 Jun 2016 11:36:05 -0400 (EDT) Subject: [Hawkular-dev] Any objections to using gitbooks? In-Reply-To: References: <582386706.55212718.1465197962737.JavaMail.zimbra@redhat.com> <1924615614.55212837.1465198040061.JavaMail.zimbra@redhat.com> Message-ID: <204773108.55559243.1465313765688.JavaMail.zimbra@redhat.com> Was fairly straightforward - I've just transferred BTM content with some changes (related to rename) - so more work is required on the content, and need to setup travis to install changes to REST docs, but: 1) Content is automatically made available here: https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ 2) Can also obtain PDF from this page: https://www.gitbook.com/book/hawkular/hawkular-apm-user-guide/details 3) Once github repo has been setup, and initial README.adoc SUMMARY.adoc and .gitignore have been created, can run: npm install gitbook-cli -g gitbook serve and then see content on localhost:4000 Regards Gary ----- Original Message ----- > So Hawkular APM will give it a try... > > The Git repo is here: > https://github.com/hawkular/hawkular-apm-user-guide > > And the published book will be here: > https://www.gitbook.com/book/hawkular/hawkular-apm-user-guide/welcome > > > PS: At least another project/product used it successfully it seems: Keycloak > / Red Hat SSO > > > > On Mon, Jun 6, 2016 at 10:36 AM, Thomas Heute < theute at redhat.com > wrote: > > > > I mostly have concerns about having docs spread over multiple solutions. But > if the plan is to move all to gitbook, it should be ok. > > Also we should still use AsciiDoc (I see that gitbook supports AscissDoc and > Markdown) > > Thomas > > On Mon, Jun 6, 2016 at 9:27 AM, Gary Brown < gbrown at redhat.com > wrote: > > > Hi > > Wondering if gitbooks was ever considered for the documentation? Seems ideal > as we can version each book with the component(s) it relates to, and users > can download a pdf version for use offline. > > Was thinking about experimenting with it for the updated APM docs? > > Any objections? > > Regards > Gary > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From anuj1708 at gmail.com Wed Jun 8 13:10:45 2016 From: anuj1708 at gmail.com (Anuj Garg) Date: Wed, 8 Jun 2016 22:40:45 +0530 Subject: [Hawkular-dev] Corrections and suggestions on Explorer for android client Message-ID: Hello everyone, A tree structure of the explorer is approx ready for the android client and I was curious if i am wrong somewhere. First of all, All feeds are collected by call to /inventory/feeds feed call for resources /inventory/feeds/{feed}/resources call for rec resources and metrics /inventory/feeds/{feed}/resources/{resid}/recursiveChildren /inventory/{feed}/resources/{resid}/metrics Am I missing something? Thanks Anuj Garg -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160608/6af7b5f9/attachment.html From vnguyen at redhat.com Wed Jun 8 16:18:49 2016 From: vnguyen at redhat.com (Viet Nguyen) Date: Wed, 8 Jun 2016 16:18:49 -0400 (EDT) Subject: [Hawkular-dev] Hawkular + MIQ CI news In-Reply-To: <814417559.34764063.1465415547219.JavaMail.zimbra@redhat.com> Message-ID: <1944587926.34765651.1465417129335.JavaMail.zimbra@redhat.com> The OS1 Kubernetes cluster[*] hosting livingontheedge.hawkular.org was recently upgraded from v1 to 1.2. Along with this upgrade two new useful pods are added to the cluster: - ManageIQ: https://miq.cloud1.hawkular.org - Wildfly with Hawkular agent. You should see this instance listed on livingontheedge's Application Server tab. These two are currently deployed manually on demand. Auto deployment triggers to be added soon. Feel free ping me (viet) or Matt Mahoney (mmahoney) on irc if you have comments or questions. [*] OS1 Kubernetes cluster https://docs.google.com/a/redhat.com/presentation/d/1nj6_8Dr35GWMcYnSMrFYfetsxV9IO8ybtCf26cfGEQU/edit?usp=sharing From jpkroehling at redhat.com Thu Jun 9 02:45:17 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Thu, 9 Jun 2016 08:45:17 +0200 Subject: [Hawkular-dev] Who owns OpenShift 'hawkular' namespace? Message-ID: Team, I'm looking for the owner of the OpenShift namespace 'hawkular'. To check if you own it, open the following URL and check the "Domains" part. In my case, I see only "jpkroehling". https://openshift.redhat.com/app/console/settings Thanks! - Juca. From theute at redhat.com Thu Jun 9 05:13:46 2016 From: theute at redhat.com (Thomas Heute) Date: Thu, 9 Jun 2016 11:13:46 +0200 Subject: [Hawkular-dev] Any objections to using gitbooks? In-Reply-To: <204773108.55559243.1465313765688.JavaMail.zimbra@redhat.com> References: <582386706.55212718.1465197962737.JavaMail.zimbra@redhat.com> <1924615614.55212837.1465198040061.JavaMail.zimbra@redhat.com> <204773108.55559243.1465313765688.JavaMail.zimbra@redhat.com> Message-ID: The main drawback I see is the lack of integration with hawkular.org , any thoughts how we can overcome that issue ? On Tue, Jun 7, 2016 at 5:36 PM, Gary Brown wrote: > Was fairly straightforward - I've just transferred BTM content with some > changes (related to rename) - so more work is required on the content, and > need to setup travis to install changes to REST docs, but: > > 1) Content is automatically made available here: > https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > > 2) Can also obtain PDF from this page: > https://www.gitbook.com/book/hawkular/hawkular-apm-user-guide/details > > 3) Once github repo has been setup, and initial README.adoc SUMMARY.adoc > and .gitignore have been created, can run: > > npm install gitbook-cli -g > > gitbook serve > > and then see content on localhost:4000 > > Regards > Gary > > > ----- Original Message ----- > > So Hawkular APM will give it a try... > > > > The Git repo is here: > > https://github.com/hawkular/hawkular-apm-user-guide > > > > And the published book will be here: > > https://www.gitbook.com/book/hawkular/hawkular-apm-user-guide/welcome > > > > > > PS: At least another project/product used it successfully it seems: > Keycloak > > / Red Hat SSO > > > > > > > > On Mon, Jun 6, 2016 at 10:36 AM, Thomas Heute < theute at redhat.com > > wrote: > > > > > > > > I mostly have concerns about having docs spread over multiple solutions. > But > > if the plan is to move all to gitbook, it should be ok. > > > > Also we should still use AsciiDoc (I see that gitbook supports AscissDoc > and > > Markdown) > > > > Thomas > > > > On Mon, Jun 6, 2016 at 9:27 AM, Gary Brown < gbrown at redhat.com > wrote: > > > > > > Hi > > > > Wondering if gitbooks was ever considered for the documentation? Seems > ideal > > as we can version each book with the component(s) it relates to, and > users > > can download a pdf version for use offline. > > > > Was thinking about experimenting with it for the updated APM docs? > > > > Any objections? > > > > Regards > > Gary > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160609/54cd2b59/attachment.html From gbrown at redhat.com Thu Jun 9 06:10:43 2016 From: gbrown at redhat.com (Gary Brown) Date: Thu, 9 Jun 2016 06:10:43 -0400 (EDT) Subject: [Hawkular-dev] Any objections to using gitbooks? In-Reply-To: References: <582386706.55212718.1465197962737.JavaMail.zimbra@redhat.com> <1924615614.55212837.1465198040061.JavaMail.zimbra@redhat.com> <204773108.55559243.1465313765688.JavaMail.zimbra@redhat.com> Message-ID: <346916381.56621531.1465467043905.JavaMail.zimbra@redhat.com> Hi Once I have a reason version, I was thinking about changing the link from the Documentation->Sub-projects->Application Performance Management to link to the content link: https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ The first part of the intro could then be able it being a component of the Hawkular project, and having a link back to the website? Regards Gary ----- Original Message ----- > The main drawback I see is the lack of integration with hawkular.org , any > thoughts how we can overcome that issue ? > > On Tue, Jun 7, 2016 at 5:36 PM, Gary Brown < gbrown at redhat.com > wrote: > > > Was fairly straightforward - I've just transferred BTM content with some > changes (related to rename) - so more work is required on the content, and > need to setup travis to install changes to REST docs, but: > > 1) Content is automatically made available here: > https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > > 2) Can also obtain PDF from this page: > https://www.gitbook.com/book/hawkular/hawkular-apm-user-guide/details > > 3) Once github repo has been setup, and initial README.adoc SUMMARY.adoc and > .gitignore have been created, can run: > > npm install gitbook-cli -g > > gitbook serve > > and then see content on localhost:4000 > > Regards > Gary > > > ----- Original Message ----- > > So Hawkular APM will give it a try... > > > > The Git repo is here: > > https://github.com/hawkular/hawkular-apm-user-guide > > > > And the published book will be here: > > https://www.gitbook.com/book/hawkular/hawkular-apm-user-guide/welcome > > > > > > PS: At least another project/product used it successfully it seems: > > Keycloak > > / Red Hat SSO > > > > > > > > On Mon, Jun 6, 2016 at 10:36 AM, Thomas Heute < theute at redhat.com > wrote: > > > > > > > > I mostly have concerns about having docs spread over multiple solutions. > > But > > if the plan is to move all to gitbook, it should be ok. > > > > Also we should still use AsciiDoc (I see that gitbook supports AscissDoc > > and > > Markdown) > > > > Thomas > > > > On Mon, Jun 6, 2016 at 9:27 AM, Gary Brown < gbrown at redhat.com > wrote: > > > > > > Hi > > > > Wondering if gitbooks was ever considered for the documentation? Seems > > ideal > > as we can version each book with the component(s) it relates to, and users > > can download a pdf version for use offline. > > > > Was thinking about experimenting with it for the updated APM docs? > > > > Any objections? > > > > Regards > > Gary > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From gbrown at redhat.com Thu Jun 9 10:34:28 2016 From: gbrown at redhat.com (Gary Brown) Date: Thu, 9 Jun 2016 10:34:28 -0400 (EDT) Subject: [Hawkular-dev] Any objections to using gitbooks? In-Reply-To: <346916381.56621531.1465467043905.JavaMail.zimbra@redhat.com> References: <582386706.55212718.1465197962737.JavaMail.zimbra@redhat.com> <1924615614.55212837.1465198040061.JavaMail.zimbra@redhat.com> <204773108.55559243.1465313765688.JavaMail.zimbra@redhat.com> <346916381.56621531.1465467043905.JavaMail.zimbra@redhat.com> Message-ID: <1731525526.56670674.1465482868562.JavaMail.zimbra@redhat.com> Would this work? https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ Then it just needs to be linked from the hawkular.org documentation menu? Regards Gary ----- Original Message ----- > Hi > > Once I have a reason version, I was thinking about changing the link from the > Documentation->Sub-projects->Application Performance Management to link to > the content link: > https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > > The first part of the intro could then be able it being a component of the > Hawkular project, and having a link back to the website? > > Regards > Gary > > ----- Original Message ----- > > The main drawback I see is the lack of integration with hawkular.org , any > > thoughts how we can overcome that issue ? > > > > On Tue, Jun 7, 2016 at 5:36 PM, Gary Brown < gbrown at redhat.com > wrote: > > > > > > Was fairly straightforward - I've just transferred BTM content with some > > changes (related to rename) - so more work is required on the content, and > > need to setup travis to install changes to REST docs, but: > > > > 1) Content is automatically made available here: > > https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > > > > 2) Can also obtain PDF from this page: > > https://www.gitbook.com/book/hawkular/hawkular-apm-user-guide/details > > > > 3) Once github repo has been setup, and initial README.adoc SUMMARY.adoc > > and > > .gitignore have been created, can run: > > > > npm install gitbook-cli -g > > > > gitbook serve > > > > and then see content on localhost:4000 > > > > Regards > > Gary > > > > > > ----- Original Message ----- > > > So Hawkular APM will give it a try... > > > > > > The Git repo is here: > > > https://github.com/hawkular/hawkular-apm-user-guide > > > > > > And the published book will be here: > > > https://www.gitbook.com/book/hawkular/hawkular-apm-user-guide/welcome > > > > > > > > > PS: At least another project/product used it successfully it seems: > > > Keycloak > > > / Red Hat SSO > > > > > > > > > > > > On Mon, Jun 6, 2016 at 10:36 AM, Thomas Heute < theute at redhat.com > > > > wrote: > > > > > > > > > > > > I mostly have concerns about having docs spread over multiple solutions. > > > But > > > if the plan is to move all to gitbook, it should be ok. > > > > > > Also we should still use AsciiDoc (I see that gitbook supports AscissDoc > > > and > > > Markdown) > > > > > > Thomas > > > > > > On Mon, Jun 6, 2016 at 9:27 AM, Gary Brown < gbrown at redhat.com > wrote: > > > > > > > > > Hi > > > > > > Wondering if gitbooks was ever considered for the documentation? Seems > > > ideal > > > as we can version each book with the component(s) it relates to, and > > > users > > > can download a pdf version for use offline. > > > > > > Was thinking about experimenting with it for the updated APM docs? > > > > > > Any objections? > > > > > > Regards > > > Gary > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > > > > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From jpkroehling at redhat.com Thu Jun 9 11:17:13 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Thu, 9 Jun 2016 17:17:13 +0200 Subject: [Hawkular-dev] Hawkular Commons 0.7.3.Final released Message-ID: Team, Hawkular Commons 0.7.3.Final was just released. This release includes the JAX-RS filter for requiring Hawkular-Tenant, as well as the annotation `@TenantRequired`, where you can mark a specific class or method as required or not required. PRs to Alerts and Inventory will follow shortly. I also expect to be able to send a PR to Metrics soon. - Juca. From snegrea at redhat.com Thu Jun 9 13:58:19 2016 From: snegrea at redhat.com (Stefan Negrea) Date: Thu, 9 Jun 2016 12:58:19 -0500 Subject: [Hawkular-dev] Hawkular Organization - Repositories - Vote In-Reply-To: References: Message-ID: Hello Everybody, The results of the vote are in and the option to keep obsolete repositories in the current org won by a large majority (9-4). The initial feedback that I got on the mailing list looked like it is going to be a tie, but the doodle made it easy to get feedback from people that did not get involved in the initial email thread, hence almost double the vote participation. As a result, the option to create a separate archive org will be tabled indefinitely. The deprecated repositories and projects will be kept in the current org but marked prominently as such and write access will be revoked on all of them. Thank you for voting! Thank you, Stefan Negrea Software Engineer On Mon, May 23, 2016 at 11:15 AM, Stefan Negrea wrote: > Hello Everybody, > > Based on the emails and discussions from the past few weeks, I created a > community poll to finalize the decision on unmaintained Hawkular > repositories. The current Github org has a significant number of projects > that no longer receive development. For a full list of projects please see > [1], projects below red line are not active. > > Please vote on what to do with repos below the red line and future repos > that will no longer be developed by Hawkular: > > 1) Move to new Hawkular-Archive organization > 2) Keep in Hawkular organization marked as "obsolete" > > > Voting will be open until Monday, May 31st, 7:00 am (US Central). > > > Doodle Poll - http://doodle.com/poll/vnaqgppvunhaweks > > > Please contact me if you have any questions about the two options or have > any comments/feedback. > > > [1] > https://docs.google.com/spreadsheets/d/1IzoBP9glz3GgkcwTRF6cobQCylUaZFLhFgqxRfuQCn0 > > > Thank you, > Stefan Negrea > > Software Engineer > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160609/2554d490/attachment.html From snegrea at redhat.com Thu Jun 9 23:07:33 2016 From: snegrea at redhat.com (Stefan Negrea) Date: Thu, 9 Jun 2016 22:07:33 -0500 Subject: [Hawkular-dev] Hawkular Commons 0.7.3.Final released In-Reply-To: References: Message-ID: Hello, Can you please give more details about the proposed changes to use the Commons filter in other projects? What dependencies need to be introduced? Where is the filter located (module, code)? Also, what are the implications of not using the filter from Commons? Thank you, Stefan Negrea Software Engineer On Thu, Jun 9, 2016 at 10:17 AM, Juraci Paix?o Kr?hling < jpkroehling at redhat.com> wrote: > Team, > > Hawkular Commons 0.7.3.Final was just released. This release includes > the JAX-RS filter for requiring Hawkular-Tenant, as well as the > annotation `@TenantRequired`, where you can mark a specific class or > method as required or not required. > > PRs to Alerts and Inventory will follow shortly. I also expect to be > able to send a PR to Metrics soon. > > - Juca. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160609/8f1885ec/attachment.html From jpkroehling at redhat.com Fri Jun 10 02:36:09 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Fri, 10 Jun 2016 08:36:09 +0200 Subject: [Hawkular-dev] Hawkular Commons 0.7.3.Final released In-Reply-To: References: Message-ID: <5226b379-6967-35ac-55d7-91afff0e0ecf@redhat.com> On 10.06.2016 05:07, Stefan Negrea wrote: > Can you please give more details about the proposed changes to use the > Commons filter in other projects? What dependencies need to be > introduced? Where is the filter located (module, code)? The tenant filter is a JAX-RS filter and the dependency is defined as org.hawkular.commons:hawkular-tenant-jaxrs-filter [1]. It's a "pure" Java EE module, depending on nothing else. All you need to do is to have your WAR module depending on this filter module and the filter will be applied automatically to all JAX-RS endpoints in your application. If you have an endpoint or method that you don't want to protect, use the `@TenantRequired(false)` annotation. 1 - https://git.io/vosci > Also, what are the implications of not using the filter from Commons? If you don't use the filter, you risk having a different behavior when comparing to other modules. For instance, you might return JSON when no JSON is expected (or vice-versa), or you might have a slightly different semantic than the current agreement, ... - Juca. From snegrea at redhat.com Fri Jun 10 11:24:33 2016 From: snegrea at redhat.com (Stefan Negrea) Date: Fri, 10 Jun 2016 10:24:33 -0500 Subject: [Hawkular-dev] Hawkular Commons 0.7.3.Final released In-Reply-To: <5226b379-6967-35ac-55d7-91afff0e0ecf@redhat.com> References: <5226b379-6967-35ac-55d7-91afff0e0ecf@redhat.com> Message-ID: Hello, Thanks for the clarifications and the PR for Metrics. I looked at the code and module they are really minimal, nice work! In the long run Metrics would benefit from adopting it however at this time the project is not ready to get additional external dependencies. I closed the PR for now, we will reopen the PR once we are ready to adopt the filter. Thank you, Stefan Negrea Software Engineer On Fri, Jun 10, 2016 at 1:36 AM, Juraci Paix?o Kr?hling < jpkroehling at redhat.com> wrote: > On 10.06.2016 05:07, Stefan Negrea wrote: > >> Can you please give more details about the proposed changes to use the >> Commons filter in other projects? What dependencies need to be >> introduced? Where is the filter located (module, code)? >> > > The tenant filter is a JAX-RS filter and the dependency is defined as > org.hawkular.commons:hawkular-tenant-jaxrs-filter [1]. It's a "pure" Java > EE module, depending on nothing else. > > All you need to do is to have your WAR module depending on this filter > module and the filter will be applied automatically to all JAX-RS endpoints > in your application. If you have an endpoint or method that you don't want > to protect, use the `@TenantRequired(false)` annotation. > > 1 - https://git.io/vosci > > Also, what are the implications of not using the filter from Commons? >> > > If you don't use the filter, you risk having a different behavior when > comparing to other modules. For instance, you might return JSON when no > JSON is expected (or vice-versa), or you might have a slightly different > semantic than the current agreement, ... > > - Juca. > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160610/34d8e60e/attachment.html From mazz at redhat.com Fri Jun 10 13:08:46 2016 From: mazz at redhat.com (John Mazzitelli) Date: Fri, 10 Jun 2016 13:08:46 -0400 (EDT) Subject: [Hawkular-dev] something is not right with hawkular-services websockets In-Reply-To: <1985414171.5379660.1465578458545.JavaMail.zimbra@redhat.com> Message-ID: <407037939.5379711.1465578526892.JavaMail.zimbra@redhat.com> There is something wrong with Hawkular-Services, specifically, the websocket stuff. I'm having a hard time getting its embedded agent to create and maintain its websocket - many times it gets closed with an odd reason code of 1006 (no other explanation). In addition, sometimes (a lot of times) when I try to connect to it via websockets using a third-party tool, I'm getting the same behavior (code 1006). The end result is we can't send messages to the embedded agent over that command-gateway stuff. It is very unstable, unlike the previous hawkular server distro (which was very reliable and always worked). I don't know what changed, but something did when we moved to hawkular-services builds. As part of this, I'm also suspecting there is a problem with the ActiveMQ message bus stuff - I'm not convinced messages are always flowing correctly - but that could just be a result of the cmdgw stuff and how subscribers are removed when websocket clients are disconnected. From hrupp at redhat.com Fri Jun 10 23:15:34 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Sat, 11 Jun 2016 05:15:34 +0200 Subject: [Hawkular-dev] Hawkular Services 0.0.1.Final In-Reply-To: <83ec7dd9-5580-afbc-b93c-6eeebd6bcce3@redhat.com> References: <83ec7dd9-5580-afbc-b93c-6eeebd6bcce3@redhat.com> Message-ID: On 7 Jun 2016, at 11:29, Juraci Paix?o Kr?hling wrote: > The first release of Hawkular Services is out: 0.0.1.Final . This should Very nice! > As the previous distributions, the Agent has to be configured with an > user. This can be accomplished by: > > - Adding an user via bin/add-user.sh like: > ./bin/add-user.sh -a -u -p > > - Changing the Agent's credential on standalone.xml to the credentials > from the previous step Could we "automate" this with some wrapper script? I understand that in -Pdev builds they are set though Heiko From jpkroehling at redhat.com Mon Jun 13 04:01:51 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Mon, 13 Jun 2016 10:01:51 +0200 Subject: [Hawkular-dev] Hawkular Services 0.0.1.Final In-Reply-To: References: <83ec7dd9-5580-afbc-b93c-6eeebd6bcce3@redhat.com> Message-ID: On 11.06.2016 05:15, Heiko W.Rupp wrote: > Could we "automate" this with some wrapper script? > I understand that in -Pdev builds they are set though I doubt we'll see any real benefits for that in the real world, as I expect the user database to come from some external system for all production instances of Hawkular. Besides, we'd need to ensure backwards compatibility with Wildfly's add-user.[sh|bat|[ps1] script. I propose that we create a JIRA for this and watch the community's interest in such feature. - Juca. From jpkroehling at redhat.com Mon Jun 13 04:36:29 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Mon, 13 Jun 2016 10:36:29 +0200 Subject: [Hawkular-dev] something is not right with hawkular-services websockets In-Reply-To: <407037939.5379711.1465578526892.JavaMail.zimbra@redhat.com> References: <407037939.5379711.1465578526892.JavaMail.zimbra@redhat.com> Message-ID: <84c7f851-7427-23ee-a500-9a6fd8e4b309@redhat.com> On 10.06.2016 19:08, John Mazzitelli wrote: > I'm having a hard time getting its embedded agent to create and maintain its websocket - many times it gets closed with an odd reason code of 1006 (no other explanation). In addition, sometimes (a lot of times) when I try to connect to it via websockets using a third-party tool, I'm getting the same behavior (code 1006). Are you able to reproduce it with the nest? If so, it should be possible to identify the commit that introduced this by using "git bisect". I can help you with that. - Juca. From ppalaga at redhat.com Mon Jun 13 04:53:03 2016 From: ppalaga at redhat.com (Peter Palaga) Date: Mon, 13 Jun 2016 10:53:03 +0200 Subject: [Hawkular-dev] something is not right with hawkular-services websockets In-Reply-To: <84c7f851-7427-23ee-a500-9a6fd8e4b309@redhat.com> References: <407037939.5379711.1465578526892.JavaMail.zimbra@redhat.com> <84c7f851-7427-23ee-a500-9a6fd8e4b309@redhat.com> Message-ID: <91902609-6b58-83f7-b645-63e1208e6533@redhat.com> I think that Mazz has found the cause in timeouts that we had to start to care for with okhttp 2.6 https://issues.jboss.org/browse/HWKAGENT-105 -- P On 2016-06-13 10:36, Juraci Paix?o Kr?hling wrote: > On 10.06.2016 19:08, John Mazzitelli wrote: >> I'm having a hard time getting its embedded agent to create and maintain its websocket - many times it gets closed with an odd reason code of 1006 (no other explanation). In addition, sometimes (a lot of times) when I try to connect to it via websockets using a third-party tool, I'm getting the same behavior (code 1006). > > Are you able to reproduce it with the nest? If so, it should be possible > to identify the commit that introduced this by using "git bisect". I can > help you with that. > > - Juca. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From hrupp at redhat.com Mon Jun 13 05:30:01 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Mon, 13 Jun 2016 11:30:01 +0200 Subject: [Hawkular-dev] something is not right with hawkular-services websockets In-Reply-To: <91902609-6b58-83f7-b645-63e1208e6533@redhat.com> References: <407037939.5379711.1465578526892.JavaMail.zimbra@redhat.com> <84c7f851-7427-23ee-a500-9a6fd8e4b309@redhat.com> <91902609-6b58-83f7-b645-63e1208e6533@redhat.com> Message-ID: On 13 Jun 2016, at 10:53, Peter Palaga wrote: > I think that Mazz has found the cause in timeouts that we had to start > to care for with okhttp 2.6 https://issues.jboss.org/browse/HWKAGENT-105 Can we roll back to 2.4 to get a stable hawkular-services release and then fix this outside of "master"? From jpkroehling at redhat.com Mon Jun 13 05:33:10 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Mon, 13 Jun 2016 11:33:10 +0200 Subject: [Hawkular-dev] something is not right with hawkular-services websockets In-Reply-To: References: <407037939.5379711.1465578526892.JavaMail.zimbra@redhat.com> <84c7f851-7427-23ee-a500-9a6fd8e4b309@redhat.com> <91902609-6b58-83f7-b645-63e1208e6533@redhat.com> Message-ID: <5bee517c-601e-17f2-9bff-599cb8da8991@redhat.com> On 13.06.2016 11:30, Heiko W.Rupp wrote: > On 13 Jun 2016, at 10:53, Peter Palaga wrote: > >> I think that Mazz has found the cause in timeouts that we had to start >> to care for with okhttp 2.6 https://issues.jboss.org/browse/HWKAGENT-105 > > Can we roll back to 2.4 to get a stable hawkular-services release and then > fix this outside of "master"? As a reminder: we have a Hawkular-Services release tomorrow. If the fix is ready and released by today, it can be included into this week's H-Services. - Juca. From jpkroehling at redhat.com Mon Jun 13 05:37:09 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Mon, 13 Jun 2016 11:37:09 +0200 Subject: [Hawkular-dev] Inventory and alerts release for tomorrow's H-Services Message-ID: Team, There were a couple of commits last week on Alerts and Inventory that fixes the auth and H-Tenant headers. Would it be possible to have a release of those components by today, so that tomorrow's H-Services incorporates those fixes? - Juca. From lponce at redhat.com Mon Jun 13 08:33:42 2016 From: lponce at redhat.com (Lucas Ponce) Date: Mon, 13 Jun 2016 08:33:42 -0400 (EDT) Subject: [Hawkular-dev] Hawkular Client Ruby In-Reply-To: <1915066650.1885733.1464270524457.JavaMail.zimbra@redhat.com> References: <1915066650.1885733.1464270524457.JavaMail.zimbra@redhat.com> Message-ID: <1560762093.5804380.1465821222252.JavaMail.zimbra@redhat.com> Hello, Thanks for the comment on the document. I am not sure if there have been some progress on this topic. In special I am failing to see how to address the "blocked situation" given as an example that is blocking some scenarios today. So, some action plan about next steps on the client could be good. Thanks, Lucas ----- Mensaje original ----- > De: "Lucas Ponce" > Para: "Discussions around Hawkular development" > Enviados: Jueves, 26 de Mayo 2016 15:48:44 > Asunto: [Hawkular-dev] Hawkular Client Ruby > > Hello, > > These days we have had several discussions about the hawkular client ruby. > > Today there are two main uses cases (Hawkular Metrics from OpenShift and > Hawkular Services for MiQ provider) and there are some complexity in the > side effects of updating the clients related to the backward compatibility. > > I have started to collect some notes about this > > https://docs.google.com/document/d/17bAPbBJ6_2wdXAAg_XIQRMi0_RQfODyOEmdOsRjk2v8/edit > > I hope it can help to gather all requeriments to have a clear picture of what > could be a good decision for future implementations, studying the pros/cons. > > Please, feel free to add your comments or thoughts about the topic. > > Thanks, > Lucas > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From mazz at redhat.com Mon Jun 13 08:47:00 2016 From: mazz at redhat.com (John Mazzitelli) Date: Mon, 13 Jun 2016 08:47:00 -0400 (EDT) Subject: [Hawkular-dev] something is not right with hawkular-services websockets In-Reply-To: <5bee517c-601e-17f2-9bff-599cb8da8991@redhat.com> References: <407037939.5379711.1465578526892.JavaMail.zimbra@redhat.com> <84c7f851-7427-23ee-a500-9a6fd8e4b309@redhat.com> <91902609-6b58-83f7-b645-63e1208e6533@redhat.com> <5bee517c-601e-17f2-9bff-599cb8da8991@redhat.com> Message-ID: <1752424508.5811492.1465822020174.JavaMail.zimbra@redhat.com> I think I fixed this (Peter mentioned the JIRA) and I released the agent. So it should be good if you use the latest agent release - 0.18.1.Final I'm on PTO today - will be back later tonight. ----- Original Message ----- > On 13.06.2016 11:30, Heiko W.Rupp wrote: > > On 13 Jun 2016, at 10:53, Peter Palaga wrote: > > > >> I think that Mazz has found the cause in timeouts that we had to start > >> to care for with okhttp 2.6 https://issues.jboss.org/browse/HWKAGENT-105 > > > > Can we roll back to 2.4 to get a stable hawkular-services release and then > > fix this outside of "master"? > > As a reminder: we have a Hawkular-Services release tomorrow. If the fix > is ready and released by today, it can be included into this week's > H-Services. > > - Juca. > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From jpkroehling at redhat.com Tue Jun 14 04:21:22 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Tue, 14 Jun 2016 10:21:22 +0200 Subject: [Hawkular-dev] Hawkular Services 0.0.2.Final Message-ID: <196b4fd0-3af9-df6c-95dd-7a3ab47f753e@redhat.com> Team, Hawkular Services 0.0.2.Final has just been released. It includes the fixes for /status and a consistent Hawkular-Tenant filter between Alerts and Inventory. Metrics might follow later. The distribution can be downloaded here: https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/hawkular/services/hawkular-services-dist/0.0.2.Final/hawkular-services-dist-0.0.2.Final.zip As the previous distributions, the Agent has to be configured with an user. This can be accomplished by: - Adding an user via bin/add-user.sh like: ./bin/add-user.sh \ -a \ -u \ -p \ -g read-write,read-only - Changing the Agent's credential on standalone.xml to the credentials from the previous step or by passing hawkular.rest.user / hawkular.rest.password as system properties (-Dhawkular.rest.user=jdoe) Known issue: https://issues.jboss.org/browse/HWKINVENT-186 - Juca. From hrupp at redhat.com Tue Jun 14 04:35:05 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 14 Jun 2016 10:35:05 +0200 Subject: [Hawkular-dev] Hawkular Services 0.0.2.Final In-Reply-To: <196b4fd0-3af9-df6c-95dd-7a3ab47f753e@redhat.com> References: <196b4fd0-3af9-df6c-95dd-7a3ab47f753e@redhat.com> Message-ID: <69F776B2-5674-4937-8EA7-65BBA4F432AB@redhat.com> On 14 Jun 2016, at 10:21, Juraci Paix?o Kr?hling wrote: > Hawkular Services 0.0.2.Final has just been released. It includes the Great! Congrats to all involved. From jpkroehling at redhat.com Tue Jun 14 06:20:11 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Tue, 14 Jun 2016 12:20:11 +0200 Subject: [Hawkular-dev] Removal of embedded Cassandra Message-ID: Team, As mentioned on IRC, we should not ship an embedded Cassandra with Hawkular Services. Here are a couple of approaches we can follow to accomplish that: - Keep everything as is, but change the default value for `hawkular.backend` to `remote` instead of the current `embedded_cassandra` - Remove the embedded Cassandra entirely from Nest. This has implications on how the integration tests are executed: we'd need to ensure that each integration test suite starts an embedded Cassandra before the test is executed. Or use an approach like Metrics, which requires Cassandra to be running before the tests are started. Which approach should be the one to follow? - Juca. From theute at redhat.com Tue Jun 14 06:25:02 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 14 Jun 2016 12:25:02 +0200 Subject: [Hawkular-dev] Hawkular.org Message-ID: With the recent repackaging effort + the ManageIQ UI, we need to rethink hawkular.org. It's tricky to keep it simple, what to download, for what usecase... And at the moment it's getting outdated. IMO, it should be trivial for end users to figure out: - What to download - where to download and how to install the server - find/browse/download the various options to feed the server with data (WF agent, ptrans supported protocoles, ...) - find/browse/download options to use/read the data: (ManageIQ, Grafana...) and for the developers - find/browse/download the client libraries (Ruby, Python...) - Find client libraries documentation - Find examples... We should probably not separate/fork Hawkular Services from Hawkular "community" too much, beside the installation procedure and few things that we would mention as only available in the "larger" package. I use the term "Hawkular Server" in the mind map for the 2 "flavors". Please propose improvements to the draft attached that represents the website structure. (A square is not necessarily a page, it may be a section of a page) Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/5d6fb528/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Hawkular.org.png Type: image/png Size: 91123 bytes Desc: not available Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/5d6fb528/attachment-0001.png From theute at redhat.com Tue Jun 14 06:26:40 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 14 Jun 2016 12:26:40 +0200 Subject: [Hawkular-dev] Removal of embedded Cassandra In-Reply-To: References: Message-ID: We should not embed Cassandra at all in that package. It would be confusing if there is a security issue in Cassandra. Thomas On Tue, Jun 14, 2016 at 12:20 PM, Juraci Paix?o Kr?hling < jpkroehling at redhat.com> wrote: > Team, > > As mentioned on IRC, we should not ship an embedded Cassandra with > Hawkular Services. Here are a couple of approaches we can follow to > accomplish that: > > - Keep everything as is, but change the default value for > `hawkular.backend` to `remote` instead of the current `embedded_cassandra` > > - Remove the embedded Cassandra entirely from Nest. This has > implications on how the integration tests are executed: we'd need to > ensure that each integration test suite starts an embedded Cassandra > before the test is executed. Or use an approach like Metrics, which > requires Cassandra to be running before the tests are started. > > Which approach should be the one to follow? > > - Juca. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/4700d843/attachment.html From lponce at redhat.com Tue Jun 14 06:31:59 2016 From: lponce at redhat.com (Lucas Ponce) Date: Tue, 14 Jun 2016 06:31:59 -0400 (EDT) Subject: [Hawkular-dev] Removal of embedded Cassandra In-Reply-To: References: Message-ID: <1617347530.6051895.1465900319950.JavaMail.zimbra@redhat.com> ----- Mensaje original ----- > De: "Juraci Paix?o Kr?hling" > Para: "Discussions around Hawkular development" > Enviados: Martes, 14 de Junio 2016 12:20:11 > Asunto: [Hawkular-dev] Removal of embedded Cassandra > > Team, > > As mentioned on IRC, we should not ship an embedded Cassandra with > Hawkular Services. Here are a couple of approaches we can follow to > accomplish that: > > - Keep everything as is, but change the default value for > `hawkular.backend` to `remote` instead of the current `embedded_cassandra` > > - Remove the embedded Cassandra entirely from Nest. This has > implications on how the integration tests are executed: we'd need to > ensure that each integration test suite starts an embedded Cassandra > before the test is executed. Or use an approach like Metrics, which > requires Cassandra to be running before the tests are started. > > Which approach should be the one to follow? > Personally I prefer one that takes less steps to maintain our integration tests as they are. I'm not a fan of big refactoring just by this reason. So, if we can solve these things with a variable better than change the whole nest and try to package it again for itests. > - Juca. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From theute at redhat.com Tue Jun 14 06:42:49 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 14 Jun 2016 12:42:49 +0200 Subject: [Hawkular-dev] Hawkular in 1 slide Message-ID: Here is an attempt to depict Hawkular in 1 slide. Please let me know if I forgot something, or ideas for improvement Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/6ced8580/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: hawkular.png Type: image/png Size: 81504 bytes Desc: not available Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/6ced8580/attachment-0001.png From lponce at redhat.com Tue Jun 14 06:52:49 2016 From: lponce at redhat.com (Lucas Ponce) Date: Tue, 14 Jun 2016 06:52:49 -0400 (EDT) Subject: [Hawkular-dev] Hawkular in 1 slide In-Reply-To: References: Message-ID: <426769006.6060610.1465901569957.JavaMail.zimbra@redhat.com> Perhaps some reference to the Hawkular UI components as another consumer ? ----- Mensaje original ----- > De: "Thomas Heute" > Para: "Discussions around Hawkular development" > Enviados: Martes, 14 de Junio 2016 12:42:49 > Asunto: [Hawkular-dev] Hawkular in 1 slide > > Here is an attempt to depict Hawkular in 1 slide. > Please let me know if I forgot something, or ideas for improvement > > Thomas > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From hrupp at redhat.com Tue Jun 14 06:58:54 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 14 Jun 2016 12:58:54 +0200 Subject: [Hawkular-dev] Removal of embedded Cassandra In-Reply-To: References: Message-ID: <19DDDD1A-B7AB-4D90-9C00-680503ECFD75@redhat.com> On 14 Jun 2016, at 12:20, Juraci Paix?o Kr?hling wrote: > - Keep everything as is, but change the default value for > `hawkular.backend` to `remote` instead of the current `embedded_cassandra` I think this needs to be the default no matter what is decided for the next item. > - Remove the embedded Cassandra entirely from Nest. This has I think this is the right thing to do. > before the test is executed. Or use an approach like Metrics, which > requires Cassandra to be running before the tests are started. Yes, +1 From hrupp at redhat.com Tue Jun 14 07:02:25 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 14 Jun 2016 13:02:25 +0200 Subject: [Hawkular-dev] Hawkular in 1 slide In-Reply-To: References: Message-ID: <62A0CA96-9578-41D9-B83A-CF36AA698ACA@redhat.com> On 14 Jun 2016, at 12:42, Thomas Heute wrote: > Here is an attempt to depict Hawkular in 1 slide. > Please let me know if I forgot something, or ideas for improvement Looks good. Of course you forgot to mention https://github.com/pilhuhn/hawkfx *joking* From theute at redhat.com Tue Jun 14 07:04:46 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 14 Jun 2016 13:04:46 +0200 Subject: [Hawkular-dev] Hawkular in 1 slide In-Reply-To: <426769006.6060610.1465901569957.JavaMail.zimbra@redhat.com> References: <426769006.6060610.1465901569957.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Jun 14, 2016 at 12:52 PM, Lucas Ponce wrote: > Perhaps some reference to the Hawkular UI components as another consumer ? > Good point, not sure about the status there though. > > ----- Mensaje original ----- > > De: "Thomas Heute" > > Para: "Discussions around Hawkular development" < > hawkular-dev at lists.jboss.org> > > Enviados: Martes, 14 de Junio 2016 12:42:49 > > Asunto: [Hawkular-dev] Hawkular in 1 slide > > > > Here is an attempt to depict Hawkular in 1 slide. > > Please let me know if I forgot something, or ideas for improvement > > > > Thomas > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/449ae970/attachment.html From theute at redhat.com Tue Jun 14 07:05:37 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 14 Jun 2016 13:05:37 +0200 Subject: [Hawkular-dev] Hawkular in 1 slide In-Reply-To: <62A0CA96-9578-41D9-B83A-CF36AA698ACA@redhat.com> References: <62A0CA96-9578-41D9-B83A-CF36AA698ACA@redhat.com> Message-ID: On Tue, Jun 14, 2016 at 1:02 PM, Heiko W.Rupp wrote: > On 14 Jun 2016, at 12:42, Thomas Heute wrote: > > > Here is an attempt to depict Hawkular in 1 slide. > > Please let me know if I forgot something, or ideas for improvement > > Looks good. > > Of course you forgot to mention https://github.com/pilhuhn/hawkfx > *joking* > Regarding my other topic about hawkular.org, we could put that in "labs" BTW, I was actually trying out hawkfx as we speak :) > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/86ec7281/attachment.html From jpkroehling at redhat.com Tue Jun 14 07:09:01 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Tue, 14 Jun 2016 13:09:01 +0200 Subject: [Hawkular-dev] Removal of embedded Cassandra In-Reply-To: References: Message-ID: <5b2c5889-7222-8d1c-742f-c10ba2d23dab@redhat.com> On 14.06.2016 12:26, Thomas Heute wrote: > We should not embed Cassandra at all in that package. It would be > confusing if there is a security issue in Cassandra. +1 , that's my preferred approach as well. - Juca. From jpkroehling at redhat.com Tue Jun 14 07:10:14 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Tue, 14 Jun 2016 13:10:14 +0200 Subject: [Hawkular-dev] Removal of embedded Cassandra In-Reply-To: <19DDDD1A-B7AB-4D90-9C00-680503ECFD75@redhat.com> References: <19DDDD1A-B7AB-4D90-9C00-680503ECFD75@redhat.com> Message-ID: <90db2c2c-3fc3-0fe6-7fb0-6c30570fdc4b@redhat.com> On 14.06.2016 12:58, Heiko W.Rupp wrote: > On 14 Jun 2016, at 12:20, Juraci Paix?o Kr?hling wrote: > >> before the test is executed. Or use an approach like Metrics, which >> requires Cassandra to be running before the tests are started. > > Yes, +1 > Alright, that adds a bit of complexity, as developers have to remember to start Cassandra before running tests. But I think it's a fair price to pay. I'll start working on that then, but we can keep discussing this :) - Juca. From jpkroehling at redhat.com Tue Jun 14 07:21:00 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Tue, 14 Jun 2016 13:21:00 +0200 Subject: [Hawkular-dev] Removal of embedded Cassandra In-Reply-To: <19DDDD1A-B7AB-4D90-9C00-680503ECFD75@redhat.com> References: <19DDDD1A-B7AB-4D90-9C00-680503ECFD75@redhat.com> Message-ID: <91045a57-2b5c-1c9c-b556-add964f6209b@redhat.com> On 14.06.2016 12:58, Heiko W.Rupp wrote: > On 14 Jun 2016, at 12:20, Juraci Paix?o Kr?hling wrote: > >> - Keep everything as is, but change the default value for >> `hawkular.backend` to `remote` instead of the current `embedded_cassandra` > > I think this needs to be the default no matter what is decided for the > next item. If we don't ship Cassandra, then it makes no sense to have this property, no? Or am I missing something? - Juca. From abonas at redhat.com Tue Jun 14 07:24:23 2016 From: abonas at redhat.com (Alissa Bonas) Date: Tue, 14 Jun 2016 14:24:23 +0300 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: Message-ID: 1. I would put REST api as a separate section, and also not in the same hierarchy/section as client libraries, because REST is part of the project, and clients consume it. 2. Having sections named "clients" and "client libraries" can be confusing. Perhaps "integrations" or "applications that consume hawkular" is better for "clients"? 3. Is there a section dedicated to community events (meetups/conferences/hackaton/summit, etc.) where there are talks about the project? Didn't see it in the diagram. 4. Overview can link to quick start imo 5. What should be the difference between quick start and the download sections? 6. Ways to contact community? I saw only social links in the footer, but what about mailing list/irc,etc.? p.s. I wrote an article couple of years ago on usability of community websites, maybe some ideas from there would be helpful as well https://opensource.com/business/14/8/open-source-project-front-door thanks, Alissa On Tue, Jun 14, 2016 at 1:25 PM, Thomas Heute wrote: > With the recent repackaging effort + the ManageIQ UI, we need to rethink > hawkular.org. > > It's tricky to keep it simple, what to download, for what usecase... And > at the moment it's getting outdated. > > IMO, it should be trivial for end users to figure out: > - What to download > - where to download and how to install the server > - find/browse/download the various options to feed the server with data > (WF agent, ptrans supported protocoles, ...) > - find/browse/download options to use/read the data: (ManageIQ, > Grafana...) > > and for the developers > - find/browse/download the client libraries (Ruby, Python...) > - Find client libraries documentation > - Find examples... > > We should probably not separate/fork Hawkular Services from Hawkular > "community" too much, beside the installation procedure and few things that > we would mention as only available in the "larger" package. I use the term > "Hawkular Server" in the mind map for the 2 "flavors". > > Please propose improvements to the draft attached that represents the > website structure. (A square is not necessarily a page, it may be a section > of a page) > > Thomas > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/ae4602e3/attachment-0001.html From theute at redhat.com Tue Jun 14 07:46:34 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 14 Jun 2016 13:46:34 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: Message-ID: On Tue, Jun 14, 2016 at 1:24 PM, Alissa Bonas wrote: > 1. I would put REST api as a separate section, and also not in the same > hierarchy/section as client libraries, because REST is part of the project, > and clients consume it. > I'm not sure, from a developer perspective it doesn't really matter if REST is part of the project (except that you have nothing else to download/use), but it should be clear what options, as a developer, you have. One has the choice between Ruby, Python, Go or plain REST. At least that was my way of thinking. > 2. Having sections named "clients" and "client libraries" can be > confusing. > Agreed. > Perhaps "integrations" or "applications that consume hawkular" is better > for "clients"? > I thought of "consumers" for a short name. As we have "feeds" that feed data and "consumers" that consumed and display or do something with the data. Still not convinced about that name though.... > 3. Is there a section dedicated to community events > (meetups/conferences/hackaton/summit, etc.) where there are talks about the > project? Didn't see it in the diagram. > Good point. We should probably splash them on the front page + blog. > 4. Overview can link to quick start imo > Not sure what you mean, after one read the overview he should definitely be invited to get started. > 5. What should be the difference between quick start and the download > sections? > Quick start explains how to install the quickest way and get something out of the product. The download section allows to find links of latest and previous releases. > 6. Ways to contact community? I saw only social links in the footer, but > what about mailing list/irc,etc.? > That would be in Community>Connect > > > p.s. I wrote an article couple of years ago on usability of community > websites, maybe some ideas from there would be helpful as well > https://opensource.com/business/14/8/open-source-project-front-door > I'll have a look, thanks ! Thomas > > > thanks, > Alissa > > On Tue, Jun 14, 2016 at 1:25 PM, Thomas Heute wrote: > >> With the recent repackaging effort + the ManageIQ UI, we need to rethink >> hawkular.org. >> >> It's tricky to keep it simple, what to download, for what usecase... And >> at the moment it's getting outdated. >> >> IMO, it should be trivial for end users to figure out: >> - What to download >> - where to download and how to install the server >> - find/browse/download the various options to feed the server with data >> (WF agent, ptrans supported protocoles, ...) >> - find/browse/download options to use/read the data: (ManageIQ, >> Grafana...) >> >> and for the developers >> - find/browse/download the client libraries (Ruby, Python...) >> - Find client libraries documentation >> - Find examples... >> >> We should probably not separate/fork Hawkular Services from Hawkular >> "community" too much, beside the installation procedure and few things that >> we would mention as only available in the "larger" package. I use the term >> "Hawkular Server" in the mind map for the 2 "flavors". >> >> Please propose improvements to the draft attached that represents the >> website structure. (A square is not necessarily a page, it may be a section >> of a page) >> >> Thomas >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> >> > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/592ea1c1/attachment.html From gbrown at redhat.com Tue Jun 14 08:12:24 2016 From: gbrown at redhat.com (Gary Brown) Date: Tue, 14 Jun 2016 08:12:24 -0400 (EDT) Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: Message-ID: <1116808792.57915324.1465906344235.JavaMail.zimbra@redhat.com> Hi Currently only have one observation - under User Guide it has Hawkular Server and Hawkular Metrics - however I believe Metrics is part of Hawkular Server. So should the User Guide be broken down into functional areas, rather than be based on packaging, as I guess that its usage will be the same (mostly) whether standalone or packaged? And where differences occur, then the guide can highlight the differences? If this change is appropriate, then it might be possible for some/all of the 'clients' to be described under the functionality area they are related to. Regards Gary ----- Original Message ----- > With the recent repackaging effort + the ManageIQ UI, we need to rethink > hawkular.org . > > It's tricky to keep it simple, what to download, for what usecase... And at > the moment it's getting outdated. > > IMO, it should be trivial for end users to figure out: > - What to download > - where to download and how to install the server > - find/browse/download the various options to feed the server with data (WF > agent, ptrans supported protocoles, ...) > - find/browse/download options to use/read the data: (ManageIQ, Grafana...) > > and for the developers > - find/browse/download the client libraries (Ruby, Python...) > - Find client libraries documentation > - Find examples... > > We should probably not separate/fork Hawkular Services from Hawkular > "community" too much, beside the installation procedure and few things that > we would mention as only available in the "larger" package. I use the term > "Hawkular Server" in the mind map for the 2 "flavors". > > Please propose improvements to the draft attached that represents the website > structure. (A square is not necessarily a page, it may be a section of a > page) > > Thomas > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From tsegismo at redhat.com Tue Jun 14 08:22:19 2016 From: tsegismo at redhat.com (Thomas Segismont) Date: Tue, 14 Jun 2016 14:22:19 +0200 Subject: [Hawkular-dev] Removal of embedded Cassandra In-Reply-To: <90db2c2c-3fc3-0fe6-7fb0-6c30570fdc4b@redhat.com> References: <19DDDD1A-B7AB-4D90-9C00-680503ECFD75@redhat.com> <90db2c2c-3fc3-0fe6-7fb0-6c30570fdc4b@redhat.com> Message-ID: 2016-06-14 13:10 GMT+02:00 Juraci Paix?o Kr?hling : > On 14.06.2016 12:58, Heiko W.Rupp wrote: > > On 14 Jun 2016, at 12:20, Juraci Paix?o Kr?hling wrote: > > > >> before the test is executed. Or use an approach like Metrics, which > >> requires Cassandra to be running before the tests are started. > > > > Yes, +1 > > > > Alright, that adds a bit of complexity, as developers have to remember > to start Cassandra before running tests. But I think it's a fair price > to pay. > The added complexity is minimal really. For 'pip install ccm' works on all platforms (well, Windows devs must install Python first) And then you can create/manage the cluster you need in the version you need. In just a few commands. https://github.com/pcmanus/ccm > > I'll start working on that then, but we can keep discussing this :) > > - Juca. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -- Thomas Segismont JBoss ON Engineering Team -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/d44b560b/attachment.html From tsegismo at redhat.com Tue Jun 14 08:24:29 2016 From: tsegismo at redhat.com (Thomas Segismont) Date: Tue, 14 Jun 2016 14:24:29 +0200 Subject: [Hawkular-dev] Hawkular in 1 slide In-Reply-To: References: Message-ID: Java as a library ? Vert.x Hawkular Metrics as a feed (WIP) ? 2016-06-14 12:42 GMT+02:00 Thomas Heute : > Here is an attempt to depict Hawkular in 1 slide. > Please let me know if I forgot something, or ideas for improvement > > Thomas > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -- Thomas Segismont JBoss ON Engineering Team -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/bd4f7d6d/attachment.html From theute at redhat.com Tue Jun 14 08:26:36 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 14 Jun 2016 14:26:36 +0200 Subject: [Hawkular-dev] Hawkular in 1 slide In-Reply-To: References: Message-ID: On Tue, Jun 14, 2016 at 2:24 PM, Thomas Segismont wrote: > Java as a library ? > I was wondering about the status of it, will add it. > Vert.x Hawkular Metrics as a feed (WIP) ? > Indeed, will add it Thanks, Thomas > > 2016-06-14 12:42 GMT+02:00 Thomas Heute : > >> Here is an attempt to depict Hawkular in 1 slide. >> Please let me know if I forgot something, or ideas for improvement >> >> Thomas >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> >> > > > -- > Thomas Segismont > JBoss ON Engineering Team > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/0eb83f13/attachment-0001.html From tsegismo at redhat.com Tue Jun 14 08:29:26 2016 From: tsegismo at redhat.com (Thomas Segismont) Date: Tue, 14 Jun 2016 14:29:26 +0200 Subject: [Hawkular-dev] Hawkular in 1 slide In-Reply-To: References: Message-ID: And there is also Hawkular-Charts 2016-06-14 14:26 GMT+02:00 Thomas Heute : > > > On Tue, Jun 14, 2016 at 2:24 PM, Thomas Segismont > wrote: > >> Java as a library ? >> > > I was wondering about the status of it, will add it. > > >> Vert.x Hawkular Metrics as a feed (WIP) ? >> > > Indeed, will add it > > Thanks, > > Thomas > > > >> >> 2016-06-14 12:42 GMT+02:00 Thomas Heute : >> >>> Here is an attempt to depict Hawkular in 1 slide. >>> Please let me know if I forgot something, or ideas for improvement >>> >>> Thomas >>> >>> _______________________________________________ >>> hawkular-dev mailing list >>> hawkular-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>> >>> >> >> >> -- >> Thomas Segismont >> JBoss ON Engineering Team >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> >> > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -- Thomas Segismont JBoss ON Engineering Team -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/8e5a6da1/attachment.html From theute at redhat.com Tue Jun 14 08:31:12 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 14 Jun 2016 14:31:12 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: <1116808792.57915324.1465906344235.JavaMail.zimbra@redhat.com> References: <1116808792.57915324.1465906344235.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Jun 14, 2016 at 2:12 PM, Gary Brown wrote: > Hi > > Currently only have one observation - under User Guide it has Hawkular > Server and Hawkular Metrics - however I believe Metrics is part of Hawkular > Server. > is *also* part of Hawkular server, yes. So should the User Guide be broken down into functional areas, rather than > be based on packaging, as I guess that its usage will be the same (mostly) > whether standalone or packaged? And where differences occur, then the guide > can highlight the differences? > Yes that the dilemma. As a user I think I would prefer based on packaging as I want to have the documentation for what I am running, today there is a split per functional area (actually it's per "component"), it makes it harder to grasp what one can do and how, plus it's missing the link between the components, as how to use them together. Thomas. > If this change is appropriate, then it might be possible for some/all of > the 'clients' to be described under the functionality area they are related > to. > > > Regards > Gary > > ----- Original Message ----- > > With the recent repackaging effort + the ManageIQ UI, we need to rethink > > hawkular.org . > > > > It's tricky to keep it simple, what to download, for what usecase... And > at > > the moment it's getting outdated. > > > > IMO, it should be trivial for end users to figure out: > > - What to download > > - where to download and how to install the server > > - find/browse/download the various options to feed the server with data > (WF > > agent, ptrans supported protocoles, ...) > > - find/browse/download options to use/read the data: (ManageIQ, > Grafana...) > > > > and for the developers > > - find/browse/download the client libraries (Ruby, Python...) > > - Find client libraries documentation > > - Find examples... > > > > We should probably not separate/fork Hawkular Services from Hawkular > > "community" too much, beside the installation procedure and few things > that > > we would mention as only available in the "larger" package. I use the > term > > "Hawkular Server" in the mind map for the 2 "flavors". > > > > Please propose improvements to the draft attached that represents the > website > > structure. (A square is not necessarily a page, it may be a section of a > > page) > > > > Thomas > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/43cff0da/attachment.html From abonas at redhat.com Tue Jun 14 08:32:16 2016 From: abonas at redhat.com (Alissa Bonas) Date: Tue, 14 Jun 2016 15:32:16 +0300 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: Message-ID: On Tue, Jun 14, 2016 at 2:46 PM, Thomas Heute wrote: > > > On Tue, Jun 14, 2016 at 1:24 PM, Alissa Bonas wrote: > >> 1. I would put REST api as a separate section, and also not in the same >> hierarchy/section as client libraries, because REST is part of the project, >> and clients consume it. >> > > I'm not sure, from a developer perspective it doesn't really matter if > REST is part of the project (except that you have nothing else to > download/use), but it should be clear what options, as a developer, you > have. > One has the choice between Ruby, Python, Go or plain REST. > > At least that was my way of thinking. > > > >> 2. Having sections named "clients" and "client libraries" can be >> confusing. >> > > Agreed. > > >> Perhaps "integrations" or "applications that consume hawkular" is better >> for "clients"? >> > > I thought of "consumers" for a short name. As we have "feeds" that feed > data and "consumers" that consumed and display or do something with the > data. Still not convinced about that name though.... > consumers sounds good. > 3. Is there a section dedicated to community events >> (meetups/conferences/hackaton/summit, etc.) where there are talks about the >> project? Didn't see it in the diagram. >> > > Good point. > We should probably splash them on the front page + blog. > > >> 4. Overview can link to quick start imo >> > > Not sure what you mean, after one read the overview he should definitely > be invited to get started. > my point was that the navigation should be as simple and efficient as possible. so if a user reads the overview page, there's no need to go to the homepage again in order to go to "get started", but rather navigate directly/have an inviting link from overview to get started. > > >> 5. What should be the difference between quick start and the download >> sections? >> > > Quick start explains how to install the quickest way and get something out > of the product. > > The download section allows to find links of latest and previous releases. > like above, I would also link between quick start and download pages so the user will get a convenient flow of "here's how to" and "here's where you can download from" > > >> 6. Ways to contact community? I saw only social links in the footer, but >> what about mailing list/irc,etc.? >> > > That would be in Community>Connect > >> >> > >> p.s. I wrote an article couple of years ago on usability of community >> websites, maybe some ideas from there would be helpful as well >> https://opensource.com/business/14/8/open-source-project-front-door >> > > > I'll have a look, thanks ! > > Thomas > > > >> >> >> thanks, >> Alissa >> >> On Tue, Jun 14, 2016 at 1:25 PM, Thomas Heute wrote: >> >>> With the recent repackaging effort + the ManageIQ UI, we need to rethink >>> hawkular.org. >>> >>> It's tricky to keep it simple, what to download, for what usecase... And >>> at the moment it's getting outdated. >>> >>> IMO, it should be trivial for end users to figure out: >>> - What to download >>> - where to download and how to install the server >>> - find/browse/download the various options to feed the server with >>> data (WF agent, ptrans supported protocoles, ...) >>> - find/browse/download options to use/read the data: (ManageIQ, >>> Grafana...) >>> >>> and for the developers >>> - find/browse/download the client libraries (Ruby, Python...) >>> - Find client libraries documentation >>> - Find examples... >>> >>> We should probably not separate/fork Hawkular Services from Hawkular >>> "community" too much, beside the installation procedure and few things that >>> we would mention as only available in the "larger" package. I use the term >>> "Hawkular Server" in the mind map for the 2 "flavors". >>> >>> Please propose improvements to the draft attached that represents the >>> website structure. (A square is not necessarily a page, it may be a section >>> of a page) >>> >>> Thomas >>> >>> _______________________________________________ >>> hawkular-dev mailing list >>> hawkular-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>> >>> >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> >> > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/fdae0199/attachment-0001.html From theute at redhat.com Tue Jun 14 08:37:49 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 14 Jun 2016 14:37:49 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: Message-ID: On Tue, Jun 14, 2016 at 2:32 PM, Alissa Bonas wrote: > > > On Tue, Jun 14, 2016 at 2:46 PM, Thomas Heute wrote: > >> >> >> On Tue, Jun 14, 2016 at 1:24 PM, Alissa Bonas wrote: >> >>> 1. I would put REST api as a separate section, and also not in the same >>> hierarchy/section as client libraries, because REST is part of the project, >>> and clients consume it. >>> >> >> I'm not sure, from a developer perspective it doesn't really matter if >> REST is part of the project (except that you have nothing else to >> download/use), but it should be clear what options, as a developer, you >> have. >> One has the choice between Ruby, Python, Go or plain REST. >> >> At least that was my way of thinking. >> >> >> >>> 2. Having sections named "clients" and "client libraries" can be >>> confusing. >>> >> >> Agreed. >> >> >>> Perhaps "integrations" or "applications that consume hawkular" is better >>> for "clients"? >>> >> >> I thought of "consumers" for a short name. As we have "feeds" that feed >> data and "consumers" that consumed and display or do something with the >> data. Still not convinced about that name though.... >> > > consumers sounds good. > > >> 3. Is there a section dedicated to community events >>> (meetups/conferences/hackaton/summit, etc.) where there are talks about the >>> project? Didn't see it in the diagram. >>> >> >> Good point. >> We should probably splash them on the front page + blog. >> >> >>> 4. Overview can link to quick start imo >>> >> >> Not sure what you mean, after one read the overview he should definitely >> be invited to get started. >> > > my point was that the navigation should be as simple and efficient as > possible. so if a user reads the overview page, there's no need to go > to the homepage again in order to go to "get started", but rather navigate > directly/have an inviting link from overview to get started. > ok, agreed > > >> >> >>> 5. What should be the difference between quick start and the download >>> sections? >>> >> >> Quick start explains how to install the quickest way and get something >> out of the product. >> >> The download section allows to find links of latest and previous releases. >> > > like above, I would also link between quick start and download pages so > the user will get a convenient flow of "here's how to" and "here's where > you can download from" > In the current quick start (Step 1, option A), it directly points to the latest version, no need to go to the download page at all: http://www.hawkular.org/docs/user/quick-start.html Thomas > > >> >> >>> 6. Ways to contact community? I saw only social links in the footer, but >>> what about mailing list/irc,etc.? >>> >> >> That would be in Community>Connect >> >>> >>> >> >>> p.s. I wrote an article couple of years ago on usability of community >>> websites, maybe some ideas from there would be helpful as well >>> https://opensource.com/business/14/8/open-source-project-front-door >>> >> >> >> I'll have a look, thanks ! >> >> Thomas >> >> >> >>> >>> >>> thanks, >>> Alissa >>> >>> On Tue, Jun 14, 2016 at 1:25 PM, Thomas Heute wrote: >>> >>>> With the recent repackaging effort + the ManageIQ UI, we need to >>>> rethink hawkular.org. >>>> >>>> It's tricky to keep it simple, what to download, for what usecase... >>>> And at the moment it's getting outdated. >>>> >>>> IMO, it should be trivial for end users to figure out: >>>> - What to download >>>> - where to download and how to install the server >>>> - find/browse/download the various options to feed the server with >>>> data (WF agent, ptrans supported protocoles, ...) >>>> - find/browse/download options to use/read the data: (ManageIQ, >>>> Grafana...) >>>> >>>> and for the developers >>>> - find/browse/download the client libraries (Ruby, Python...) >>>> - Find client libraries documentation >>>> - Find examples... >>>> >>>> We should probably not separate/fork Hawkular Services from Hawkular >>>> "community" too much, beside the installation procedure and few things that >>>> we would mention as only available in the "larger" package. I use the term >>>> "Hawkular Server" in the mind map for the 2 "flavors". >>>> >>>> Please propose improvements to the draft attached that represents the >>>> website structure. (A square is not necessarily a page, it may be a section >>>> of a page) >>>> >>>> Thomas >>>> >>>> _______________________________________________ >>>> hawkular-dev mailing list >>>> hawkular-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>>> >>>> >>> >>> _______________________________________________ >>> hawkular-dev mailing list >>> hawkular-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>> >>> >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> >> > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/5ca3470e/attachment.html From gbrown at redhat.com Tue Jun 14 08:46:12 2016 From: gbrown at redhat.com (Gary Brown) Date: Tue, 14 Jun 2016 08:46:12 -0400 (EDT) Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1116808792.57915324.1465906344235.JavaMail.zimbra@redhat.com> Message-ID: <337879363.57923420.1465908372272.JavaMail.zimbra@redhat.com> How will the common content between the Hawkular Server and Hawkular Metrics user guides be managed? Although not related to structure - if we do continue to use gitbook for docs, I assume there will actually be a separate doc then for the installation and user guide - so in terms of the APM gitbook I will need to move the installation and API sections out? If so, could you create the repo for the APM installation guide, and also an agent guide. Regards Gary ----- Original Message ----- > > On Tue, Jun 14, 2016 at 2:12 PM, Gary Brown < gbrown at redhat.com > wrote: > > > Hi > > Currently only have one observation - under User Guide it has Hawkular Server > and Hawkular Metrics - however I believe Metrics is part of Hawkular Server. > > is *also* part of Hawkular server, yes. > > > > So should the User Guide be broken down into functional areas, rather than be > based on packaging, as I guess that its usage will be the same (mostly) > whether standalone or packaged? And where differences occur, then the guide > can highlight the differences? > > Yes that the dilemma. As a user I think I would prefer based on packaging as > I want to have the documentation for what I am running, today there is a > split per functional area (actually it's per "component"), it makes it > harder to grasp what one can do and how, plus it's missing the link between > the components, as how to use them together. > > > Thomas. > > > If this change is appropriate, then it might be possible for some/all of the > 'clients' to be described under the functionality area they are related to. > > > > > > Regards > Gary > > ----- Original Message ----- > > With the recent repackaging effort + the ManageIQ UI, we need to rethink > > hawkular.org . > > > > It's tricky to keep it simple, what to download, for what usecase... And at > > the moment it's getting outdated. > > > > IMO, it should be trivial for end users to figure out: > > - What to download > > - where to download and how to install the server > > - find/browse/download the various options to feed the server with data (WF > > agent, ptrans supported protocoles, ...) > > - find/browse/download options to use/read the data: (ManageIQ, Grafana...) > > > > and for the developers > > - find/browse/download the client libraries (Ruby, Python...) > > - Find client libraries documentation > > - Find examples... > > > > We should probably not separate/fork Hawkular Services from Hawkular > > "community" too much, beside the installation procedure and few things that > > we would mention as only available in the "larger" package. I use the term > > "Hawkular Server" in the mind map for the 2 "flavors". > > > > Please propose improvements to the draft attached that represents the > > website > > structure. (A square is not necessarily a page, it may be a section of a > > page) > > > > Thomas > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From theute at redhat.com Tue Jun 14 08:53:24 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 14 Jun 2016 14:53:24 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: <337879363.57923420.1465908372272.JavaMail.zimbra@redhat.com> References: <1116808792.57915324.1465906344235.JavaMail.zimbra@redhat.com> <337879363.57923420.1465908372272.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Jun 14, 2016 at 2:46 PM, Gary Brown wrote: > How will the common content between the Hawkular Server and Hawkular > Metrics user guides be managed? > If we could use the same source and build the 2 docs, that would be optimal IMO. Not sure if that's doable. My priority is really hawkular-services and that the services makes sense together so the Hawkular Metrics doc could also just link to a specific chapter of Hawkular services. > Although not related to structure - if we do continue to use gitbook for > docs, I assume there will actually be a separate doc then for the > installation and user guide - so in terms of the APM gitbook I will need to > move the installation and API sections out? > > If so, could you create the repo for the APM installation guide, and also > an agent guide. > We're not there yet, but possibly. We can also link to a chapter of the guide, at least temporarily. > > Regards > Gary > > ----- Original Message ----- > > > > On Tue, Jun 14, 2016 at 2:12 PM, Gary Brown < gbrown at redhat.com > wrote: > > > > > > Hi > > > > Currently only have one observation - under User Guide it has Hawkular > Server > > and Hawkular Metrics - however I believe Metrics is part of Hawkular > Server. > > > > is *also* part of Hawkular server, yes. > > > > > > > > So should the User Guide be broken down into functional areas, rather > than be > > based on packaging, as I guess that its usage will be the same (mostly) > > whether standalone or packaged? And where differences occur, then the > guide > > can highlight the differences? > > > > Yes that the dilemma. As a user I think I would prefer based on > packaging as > > I want to have the documentation for what I am running, today there is a > > split per functional area (actually it's per "component"), it makes it > > harder to grasp what one can do and how, plus it's missing the link > between > > the components, as how to use them together. > > > > > > Thomas. > > > > > > If this change is appropriate, then it might be possible for some/all of > the > > 'clients' to be described under the functionality area they are related > to. > > > > > > > > > > > > Regards > > Gary > > > > ----- Original Message ----- > > > With the recent repackaging effort + the ManageIQ UI, we need to > rethink > > > hawkular.org . > > > > > > It's tricky to keep it simple, what to download, for what usecase... > And at > > > the moment it's getting outdated. > > > > > > IMO, it should be trivial for end users to figure out: > > > - What to download > > > - where to download and how to install the server > > > - find/browse/download the various options to feed the server with > data (WF > > > agent, ptrans supported protocoles, ...) > > > - find/browse/download options to use/read the data: (ManageIQ, > Grafana...) > > > > > > and for the developers > > > - find/browse/download the client libraries (Ruby, Python...) > > > - Find client libraries documentation > > > - Find examples... > > > > > > We should probably not separate/fork Hawkular Services from Hawkular > > > "community" too much, beside the installation procedure and few things > that > > > we would mention as only available in the "larger" package. I use the > term > > > "Hawkular Server" in the mind map for the 2 "flavors". > > > > > > Please propose improvements to the draft attached that represents the > > > website > > > structure. (A square is not necessarily a page, it may be a section of > a > > > page) > > > > > > Thomas > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/8cffefbc/attachment-0001.html From gbrown at redhat.com Tue Jun 14 08:57:46 2016 From: gbrown at redhat.com (Gary Brown) Date: Tue, 14 Jun 2016 08:57:46 -0400 (EDT) Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1116808792.57915324.1465906344235.JavaMail.zimbra@redhat.com> <337879363.57923420.1465908372272.JavaMail.zimbra@redhat.com> Message-ID: <1277792358.57927873.1465909066393.JavaMail.zimbra@redhat.com> ----- Original Message ----- > > > On Tue, Jun 14, 2016 at 2:46 PM, Gary Brown < gbrown at redhat.com > wrote: > > > How will the common content between the Hawkular Server and Hawkular Metrics > user guides be managed? > > If we could use the same source and build the 2 docs, that would be optimal > IMO. Not sure if that's doable. > My priority is really hawkular-services and that the services makes sense > together so the Hawkular Metrics doc could also just link to a specific > chapter of Hawkular services. > > > > Although not related to structure - if we do continue to use gitbook for > docs, I assume there will actually be a separate doc then for the > installation and user guide - so in terms of the APM gitbook I will need to > move the installation and API sections out? > > If so, could you create the repo for the APM installation guide, and also an > agent guide. > > We're not there yet, but possibly. We can also link to a chapter of the > guide, at least temporarily. Ok will just continue to build content in the one gitbook for now. > > > > > Regards > Gary > > ----- Original Message ----- > > > > On Tue, Jun 14, 2016 at 2:12 PM, Gary Brown < gbrown at redhat.com > wrote: > > > > > > Hi > > > > Currently only have one observation - under User Guide it has Hawkular > > Server > > and Hawkular Metrics - however I believe Metrics is part of Hawkular > > Server. > > > > is *also* part of Hawkular server, yes. > > > > > > > > So should the User Guide be broken down into functional areas, rather than > > be > > based on packaging, as I guess that its usage will be the same (mostly) > > whether standalone or packaged? And where differences occur, then the guide > > can highlight the differences? > > > > Yes that the dilemma. As a user I think I would prefer based on packaging > > as > > I want to have the documentation for what I am running, today there is a > > split per functional area (actually it's per "component"), it makes it > > harder to grasp what one can do and how, plus it's missing the link between > > the components, as how to use them together. > > > > > > Thomas. > > > > > > If this change is appropriate, then it might be possible for some/all of > > the > > 'clients' to be described under the functionality area they are related to. > > > > > > > > > > > > Regards > > Gary > > > > ----- Original Message ----- > > > With the recent repackaging effort + the ManageIQ UI, we need to rethink > > > hawkular.org . > > > > > > It's tricky to keep it simple, what to download, for what usecase... And > > > at > > > the moment it's getting outdated. > > > > > > IMO, it should be trivial for end users to figure out: > > > - What to download > > > - where to download and how to install the server > > > - find/browse/download the various options to feed the server with data > > > (WF > > > agent, ptrans supported protocoles, ...) > > > - find/browse/download options to use/read the data: (ManageIQ, > > > Grafana...) > > > > > > and for the developers > > > - find/browse/download the client libraries (Ruby, Python...) > > > - Find client libraries documentation > > > - Find examples... > > > > > > We should probably not separate/fork Hawkular Services from Hawkular > > > "community" too much, beside the installation procedure and few things > > > that > > > we would mention as only available in the "larger" package. I use the > > > term > > > "Hawkular Server" in the mind map for the 2 "flavors". > > > > > > Please propose improvements to the draft attached that represents the > > > website > > > structure. (A square is not necessarily a page, it may be a section of a > > > page) > > > > > > Thomas > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From miburman at redhat.com Tue Jun 14 09:06:32 2016 From: miburman at redhat.com (Michael Burman) Date: Tue, 14 Jun 2016 09:06:32 -0400 (EDT) Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: Message-ID: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> Consumers is terrible word for any client, as they both consume as well as produce the data. For example for Heapster, we currently produce the data, however at the moment I'm creating a change that will consume the data from HWKMETRICS. Integration / clients is far more used and known word, while consumer/producer is something more specific and implies a design pattern. - Micke ----- Original Message ----- From: "Alissa Bonas" To: "Discussions around Hawkular development" Sent: Tuesday, June 14, 2016 3:32:16 PM Subject: Re: [Hawkular-dev] Hawkular.org On Tue, Jun 14, 2016 at 2:46 PM, Thomas Heute < theute at redhat.com > wrote: On Tue, Jun 14, 2016 at 1:24 PM, Alissa Bonas < abonas at redhat.com > wrote: 1. I would put REST api as a separate section, and also not in the same hierarchy/section as client libraries, because REST is part of the project, and clients consume it. I'm not sure, from a developer perspective it doesn't really matter if REST is part of the project (except that you have nothing else to download/use), but it should be clear what options, as a developer, you have. One has the choice between Ruby, Python, Go or plain REST. At least that was my way of thinking. 2. Having sections named "clients" and "client libraries" can be confusing. Agreed. Perhaps "integrations" or "applications that consume hawkular" is better for "clients"? I thought of "consumers" for a short name. As we have "feeds" that feed data and "consumers" that consumed and display or do something with the data. Still not convinced about that name though.... consumers sounds good. 3. Is there a section dedicated to community events (meetups/conferences/hackaton/summit, etc.) where there are talks about the project? Didn't see it in the diagram. Good point. We should probably splash them on the front page + blog. 4. Overview can link to quick start imo Not sure what you mean, after one read the overview he should definitely be invited to get started. my point was that the navigation should be as simple and efficient as possible. so if a user reads the overview page, there's no need to go to the homepage again in order to go to "get started", but rather navigate directly/have an inviting link from overview to get started. 5. What should be the difference between quick start and the download sections? Quick start explains how to install the quickest way and get something out of the product. The download section allows to find links of latest and previous releases. like above, I would also link between quick start and download pages so the user will get a convenient flow of "here's how to" and "here's where you can download from" 6. Ways to contact community? I saw only social links in the footer, but what about mailing list/irc,etc.? That would be in Community>Connect p.s. I wrote an article couple of years ago on usability of community websites, maybe some ideas from there would be helpful as well https://opensource.com/business/14/8/open-source-project-front-door I'll have a look, thanks ! Thomas thanks, Alissa On Tue, Jun 14, 2016 at 1:25 PM, Thomas Heute < theute at redhat.com > wrote: With the recent repackaging effort + the ManageIQ UI, we need to rethink hawkular.org . It's tricky to keep it simple, what to download, for what usecase... And at the moment it's getting outdated. IMO, it should be trivial for end users to figure out: - What to download - where to download and how to install the server - find/browse/download the various options to feed the server with data (WF agent, ptrans supported protocoles, ...) - find/browse/download options to use/read the data: (ManageIQ, Grafana...) and for the developers - find/browse/download the client libraries (Ruby, Python...) - Find client libraries documentation - Find examples... We should probably not separate/fork Hawkular Services from Hawkular "community" too much, beside the installation procedure and few things that we would mention as only available in the "larger" package. I use the term "Hawkular Server" in the mind map for the 2 "flavors". Please propose improvements to the draft attached that represents the website structure. (A square is not necessarily a page, it may be a section of a page) Thomas _______________________________________________ hawkular-dev mailing list hawkular-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev _______________________________________________ hawkular-dev mailing list hawkular-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev _______________________________________________ hawkular-dev mailing list hawkular-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev _______________________________________________ hawkular-dev mailing list hawkular-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev From theute at redhat.com Tue Jun 14 09:09:40 2016 From: theute at redhat.com (Thomas Heute) Date: Tue, 14 Jun 2016 15:09:40 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> Message-ID: On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman wrote: > Consumers is terrible word for any client, as they both consume as well as > produce the data. Well that was actually reflecting the current state, we have "things" that feed data to the server and "things" that consume data from the server. The client libraries provide an API to feed and consume. > For example for Heapster, we currently produce the data, however at the > moment I'm creating a change that will consume the data from HWKMETRICS. > Why does it consume data now ? Thomas > Integration / clients is far more used and known word, while > consumer/producer is something more specific and implies a design pattern. > > - Micke > > ----- Original Message ----- > From: "Alissa Bonas" > To: "Discussions around Hawkular development" < > hawkular-dev at lists.jboss.org> > Sent: Tuesday, June 14, 2016 3:32:16 PM > Subject: Re: [Hawkular-dev] Hawkular.org > > > > On Tue, Jun 14, 2016 at 2:46 PM, Thomas Heute < theute at redhat.com > wrote: > > > > > > On Tue, Jun 14, 2016 at 1:24 PM, Alissa Bonas < abonas at redhat.com > wrote: > > > > 1. I would put REST api as a separate section, and also not in the same > hierarchy/section as client libraries, because REST is part of the project, > and clients consume it. > > I'm not sure, from a developer perspective it doesn't really matter if > REST is part of the project (except that you have nothing else to > download/use), but it should be clear what options, as a developer, you > have. > One has the choice between Ruby, Python, Go or plain REST. > > At least that was my way of thinking. > > > > > 2. Having sections named "clients" and "client libraries" can be confusing. > > Agreed. > > > > Perhaps "integrations" or "applications that consume hawkular" is better > for "clients"? > > I thought of "consumers" for a short name. As we have "feeds" that feed > data and "consumers" that consumed and display or do something with the > data. Still not convinced about that name though.... > > consumers sounds good. > > > > > > > 3. Is there a section dedicated to community events > (meetups/conferences/hackaton/summit, etc.) where there are talks about the > project? Didn't see it in the diagram. > > Good point. > We should probably splash them on the front page + blog. > > > > 4. Overview can link to quick start imo > > Not sure what you mean, after one read the overview he should definitely > be invited to get started. > > my point was that the navigation should be as simple and efficient as > possible. so if a user reads the overview page, there's no need to go > to the homepage again in order to go to "get started", but rather navigate > directly/have an inviting link from overview to get started. > > > > > > > 5. What should be the difference between quick start and the download > sections? > > Quick start explains how to install the quickest way and get something out > of the product. > > The download section allows to find links of latest and previous releases. > > like above, I would also link between quick start and download pages so > the user will get a convenient flow of "here's how to" and "here's where > you can download from" > > > > > > > 6. Ways to contact community? I saw only social links in the footer, but > what about mailing list/irc,etc.? > > That would be in Community>Connect > > > > > > > > p.s. I wrote an article couple of years ago on usability of community > websites, maybe some ideas from there would be helpful as well > https://opensource.com/business/14/8/open-source-project-front-door > > > I'll have a look, thanks ! > > Thomas > > > > > > > thanks, > Alissa > > On Tue, Jun 14, 2016 at 1:25 PM, Thomas Heute < theute at redhat.com > wrote: > > > > With the recent repackaging effort + the ManageIQ UI, we need to rethink > hawkular.org . > > It's tricky to keep it simple, what to download, for what usecase... And > at the moment it's getting outdated. > > IMO, it should be trivial for end users to figure out: > - What to download > - where to download and how to install the server > - find/browse/download the various options to feed the server with data > (WF agent, ptrans supported protocoles, ...) > - find/browse/download options to use/read the data: (ManageIQ, Grafana...) > > and for the developers > - find/browse/download the client libraries (Ruby, Python...) > - Find client libraries documentation > - Find examples... > > We should probably not separate/fork Hawkular Services from Hawkular > "community" too much, beside the installation procedure and few things that > we would mention as only available in the "larger" package. I use the term > "Hawkular Server" in the mind map for the 2 "flavors". > > Please propose improvements to the draft attached that represents the > website structure. (A square is not necessarily a page, it may be a section > of a page) > > Thomas > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/a0bd85c0/attachment-0001.html From hrupp at redhat.com Tue Jun 14 09:21:42 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 14 Jun 2016 15:21:42 +0200 Subject: [Hawkular-dev] Removal of embedded Cassandra In-Reply-To: <91045a57-2b5c-1c9c-b556-add964f6209b@redhat.com> References: <19DDDD1A-B7AB-4D90-9C00-680503ECFD75@redhat.com> <91045a57-2b5c-1c9c-b556-add964f6209b@redhat.com> Message-ID: <71F5C98C-6803-4592-9808-0F6B278A54D9@redhat.com> On 14 Jun 2016, at 13:21, Juraci Paix?o Kr?hling wrote: > On 14.06.2016 12:58, Heiko W.Rupp wrote: >> On 14 Jun 2016, at 12:20, Juraci Paix?o Kr?hling wrote: >> >>> - Keep everything as is, but change the default value for >>> `hawkular.backend` to `remote` instead of the current >>> `embedded_cassandra` >> >> I think this needs to be the default no matter what is decided for >> the >> next item. > > If we don't ship Cassandra, then it makes no sense to have this > property, no? Or am I missing something? I recall that multiple components evaluate this flag and set the connection accordingly. But maybe I am confusing it with CASSANDRA_NODES env variable right now. This variable is only used though when hawkular.backend is set to != embedded From mazz at redhat.com Tue Jun 14 09:38:02 2016 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 14 Jun 2016 09:38:02 -0400 (EDT) Subject: [Hawkular-dev] Fwd: [wildfly-dev] Wildfly Provisioning In-Reply-To: References: Message-ID: <1204111076.6136786.1465911482339.JavaMail.zimbra@redhat.com> just passing this along... ----- Forwarded Message ----- From: "Stuart Douglas" To: wildfly-dev at lists.jboss.org Sent: Tuesday, June 14, 2016 4:53:32 AM Subject: [wildfly-dev] Wildfly Provisioning Hi Everyone, Recently a few of us had a meeting to discuss a new provisioning/patching system for Wildfly. I have written up the notes for this meeting which are at [1]. The document contains the full details, but the basic idea is to design a provisioning/patching/package management system for Wildfly and downstream products. This will not be based on our existing patching or feature pack code, but should take over the responsibilities of both. Obviously this is still in the early stages, and any feedback is welcome. Stuart [1] https://github.com/stuartwdouglas/wildfly-provisioning/blob/master/docs/src/main/asciidoc/design-doc.asciidoc From mazz at redhat.com Tue Jun 14 09:49:14 2016 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 14 Jun 2016 09:49:14 -0400 (EDT) Subject: [Hawkular-dev] Removal of embedded Cassandra In-Reply-To: <91045a57-2b5c-1c9c-b556-add964f6209b@redhat.com> References: <19DDDD1A-B7AB-4D90-9C00-680503ECFD75@redhat.com> <91045a57-2b5c-1c9c-b556-add964f6209b@redhat.com> Message-ID: <1150831036.6138860.1465912154065.JavaMail.zimbra@redhat.com> Wait, what? I didn't finish this thread but I just jumped out of my chair. You mean I have to separately run and manage a C* cluster just to run itests?? Why would we require that? So now the tests will always fail unless you have some extra server that you run manually outside of the tests? Plus, with that, it is not so simple anymore for Joe Developer to simply git clone and "mvn clean install -Pitest" and see things work. They will now have to separately install and run their own C* cluster (and first know that that has to be done). -1 that. Forcing someone to run something OUTSIDE of the itest framework just to get the itests to pass is wrong. Or am I missing something? Will the itests framework run a standalone C* at the start and shut it down after it finishes? ----- Original Message ----- > On 14.06.2016 12:58, Heiko W.Rupp wrote: > > On 14 Jun 2016, at 12:20, Juraci Paix?o Kr?hling wrote: > > > >> - Keep everything as is, but change the default value for > >> `hawkular.backend` to `remote` instead of the current `embedded_cassandra` > > > > I think this needs to be the default no matter what is decided for the > > next item. > > If we don't ship Cassandra, then it makes no sense to have this > property, no? Or am I missing something? > > - Juca. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From jpkroehling at redhat.com Tue Jun 14 10:28:44 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Tue, 14 Jun 2016 16:28:44 +0200 Subject: [Hawkular-dev] Removal of embedded Cassandra In-Reply-To: <1150831036.6138860.1465912154065.JavaMail.zimbra@redhat.com> References: <19DDDD1A-B7AB-4D90-9C00-680503ECFD75@redhat.com> <91045a57-2b5c-1c9c-b556-add964f6209b@redhat.com> <1150831036.6138860.1465912154065.JavaMail.zimbra@redhat.com> Message-ID: I agree with Mazz about the tests: tests should be predictable and fail only when there's a failure on the *code*, so, having to install a database, or having pre-existing data should *not* be something that would break tests. At least for JPA modules, it's common to use an embedded database for the tests, while the real module uses datasources configured on the application server. This problem could be avoided by having the integration tests to add the embedded Cassandra WAR to the nest, binding it to a different port (to avoid conflicting with possible Cassandra nodes running on the machine). For dev builds: I'm not sure I like the idea of having embedded Cassandra for dev builds but not for release builds. IMO, we should try to not deviate too much, specially because we would catch problems only when it's "too late". I'd rather require developers to install Cassandra locally, on this scenario. - Juca. From jpkroehling at redhat.com Tue Jun 14 11:51:38 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Tue, 14 Jun 2016 17:51:38 +0200 Subject: [Hawkular-dev] Hawkular Commons 0.7.4.Final Message-ID: Team, Based on the IRC discussion and on the related thread, I removed the Embedded Cassandra from Nest and did a release of Commons (0.7.4.Final). The integration tests for Nest are deploying the Embedded Cassandra, while the feature pack is not shipping it. If you need help achieving this on your module, let me know. Next week's Hawkular Services will be based on this version of Commons, so, it won't be shipping Cassandra anymore. - Juca. From mazz at redhat.com Tue Jun 14 12:12:44 2016 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 14 Jun 2016 12:12:44 -0400 (EDT) Subject: [Hawkular-dev] Hawkular Commons 0.7.4.Final In-Reply-To: References: Message-ID: <333401323.6175032.1465920764578.JavaMail.zimbra@redhat.com> I just tried quickly building itests for agent - I assumed it would fail during the itest run because C* isn't there, but I can't even build. Any idea what this is telling me? [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.6.Final:build (server-provisioning-hawkular) on project hawkular-wildfly-agent-installer-itest: Execution server-provisioning-hawkular of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.6.Final:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Feature pack /home/mazz/source/hawkular-agent/hawkular-wildfly-agent-itest-parent/hawkular-wildfly-agent-itest-feature-pack/target/hawkular-wildfly-agent-itest-feature-pack-0.18.2.Final-SNAPSHOT.zip template file configuration/standalone/hawkular-nest-template.xml not found It seems there is some file - hawkular-nest-template.xml - that used to exist but no longer does. ----- Original Message ----- > Team, > > Based on the IRC discussion and on the related thread, I removed the > Embedded Cassandra from Nest and did a release of Commons (0.7.4.Final). > > The integration tests for Nest are deploying the Embedded Cassandra, > while the feature pack is not shipping it. If you need help achieving > this on your module, let me know. > > Next week's Hawkular Services will be based on this version of Commons, > so, it won't be shipping Cassandra anymore. > > - Juca. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From jpkroehling at redhat.com Tue Jun 14 12:21:20 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Tue, 14 Jun 2016 18:21:20 +0200 Subject: [Hawkular-dev] Hawkular Commons 0.7.4.Final In-Reply-To: <333401323.6175032.1465920764578.JavaMail.zimbra@redhat.com> References: <333401323.6175032.1465920764578.JavaMail.zimbra@redhat.com> Message-ID: Yes, true. We don't have any more customization on the template, so, we are just using the one that we get from upstream. On your pom.xml , replace this: configuration/standalone/hawkular-nest-template.xml by this: configuration/standalone/template.xml - Juca. On 14.06.2016 18:12, John Mazzitelli wrote: > I just tried quickly building itests for agent - I assumed it would fail during the itest run because C* isn't there, but I can't even build. > > Any idea what this is telling me? > > [ERROR] Failed to execute goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.6.Final:build (server-provisioning-hawkular) on project hawkular-wildfly-agent-installer-itest: Execution server-provisioning-hawkular of goal org.wildfly.build:wildfly-server-provisioning-maven-plugin:1.1.6.Final:build failed: java.lang.RuntimeException: java.lang.RuntimeException: Feature pack /home/mazz/source/hawkular-agent/hawkular-wildfly-agent-itest-parent/hawkular-wildfly-agent-itest-feature-pack/target/hawkular-wildfly-agent-itest-feature-pack-0.18.2.Final-SNAPSHOT.zip template file configuration/standalone/hawkular-nest-template.xml not found > > It seems there is some file - hawkular-nest-template.xml - that used to exist but no longer does. > > ----- Original Message ----- >> Team, >> >> Based on the IRC discussion and on the related thread, I removed the >> Embedded Cassandra from Nest and did a release of Commons (0.7.4.Final). >> >> The integration tests for Nest are deploying the Embedded Cassandra, >> while the feature pack is not shipping it. If you need help achieving >> this on your module, let me know. >> >> Next week's Hawkular Services will be based on this version of Commons, >> so, it won't be shipping Cassandra anymore. >> >> - Juca. >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> From miburman at redhat.com Tue Jun 14 13:08:58 2016 From: miburman at redhat.com (Michael Burman) Date: Tue, 14 Jun 2016 13:08:58 -0400 (EDT) Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> Message-ID: <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> Currently Heapster stores in internal memory few minutes of data and allows queries that request this data (through its REST-interface). The consume part will just request the data from the HWKMETRICS instead. - Micke ----- Original Message ----- From: "Thomas Heute" To: "Discussions around Hawkular development" Sent: Tuesday, June 14, 2016 4:09:40 PM Subject: Re: [Hawkular-dev] Hawkular.org On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman < miburman at redhat.com > wrote: Consumers is terrible word for any client, as they both consume as well as produce the data. Well that was actually reflecting the current state, we have "things" that feed data to the server and "things" that consume data from the server. The client libraries provide an API to feed and consume. For example for Heapster, we currently produce the data, however at the moment I'm creating a change that will consume the data from HWKMETRICS. Why does it consume data now ? Thomas Integration / clients is far more used and known word, while consumer/producer is something more specific and implies a design pattern. - Micke From mazz at redhat.com Tue Jun 14 14:25:46 2016 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 14 Jun 2016 14:25:46 -0400 (EDT) Subject: [Hawkular-dev] Hawkular Commons 0.7.4.Final In-Reply-To: References: Message-ID: <1109379391.6199678.1465928746048.JavaMail.zimbra@redhat.com> FYI: I got the agent to install its own embedded C* when running itests. https://github.com/hawkular/hawkular-agent/pull/209 The agent has its own feature pack for its itest hawkular server - I just copied the embC war via the feature pack build. And in each of my itests, I just pass the sys prop in. This works and passes on my box. How travis will do is a roll of the dice.... ----- Original Message ----- > Team, > > Based on the IRC discussion and on the related thread, I removed the > Embedded Cassandra from Nest and did a release of Commons (0.7.4.Final). > > The integration tests for Nest are deploying the Embedded Cassandra, > while the feature pack is not shipping it. If you need help achieving > this on your module, let me know. > > Next week's Hawkular Services will be based on this version of Commons, > so, it won't be shipping Cassandra anymore. > > - Juca. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From snegrea at redhat.com Tue Jun 14 16:32:09 2016 From: snegrea at redhat.com (Stefan Negrea) Date: Tue, 14 Jun 2016 15:32:09 -0500 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> Message-ID: I do not see the idea proposed yet, but why not structure the website around major projects? We have Hawkular community, Hawkular Services, Hawkular Metrics, and APM. Projects like Inventory or the clients would fall under Hawkular Services umbrella. So rather than designing a generic structure with everything make individual sub-sites and then apply the structure you proposed. The current website was designed when the direction of the community was different so a re-org along the previous structure is not sufficient. Thank you, Stefan Negrea On Tue, Jun 14, 2016 at 12:08 PM, Michael Burman wrote: > Currently Heapster stores in internal memory few minutes of data and > allows queries that request this data (through its REST-interface). The > consume part will just request the data from the HWKMETRICS instead. > > - Micke > > ----- Original Message ----- > From: "Thomas Heute" > To: "Discussions around Hawkular development" < > hawkular-dev at lists.jboss.org> > Sent: Tuesday, June 14, 2016 4:09:40 PM > Subject: Re: [Hawkular-dev] Hawkular.org > > > > On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman < miburman at redhat.com > > wrote: > > > Consumers is terrible word for any client, as they both consume as well as > produce the data. > > Well that was actually reflecting the current state, we have "things" that > feed data to the server and "things" that consume data from the server. The > client libraries provide an API to feed and consume. > > > For example for Heapster, we currently produce the data, however at the > moment I'm creating a change that will consume the data from HWKMETRICS. > > Why does it consume data now ? > > Thomas > > > > > Integration / clients is far more used and known word, while > consumer/producer is something more specific and implies a design pattern. > > - Micke > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160614/3b986b3a/attachment-0001.html From theute at redhat.com Wed Jun 15 02:22:53 2016 From: theute at redhat.com (Thomas Heute) Date: Wed, 15 Jun 2016 08:22:53 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> Message-ID: Yes, that's also reasonable. Would you put Grafana support under Hawkular Services or Metrics or somewhere else ? On Tue, Jun 14, 2016 at 10:32 PM, Stefan Negrea wrote: > I do not see the idea proposed yet, but why not structure the website > around major projects? We have Hawkular community, Hawkular Services, > Hawkular Metrics, and APM. Projects like Inventory or the clients would > fall under Hawkular Services umbrella. So rather than designing a generic > structure with everything make individual sub-sites and then apply the > structure you proposed. > > The current website was designed when the direction of the community was > different so a re-org along the previous structure is not sufficient. > > Thank you, > Stefan Negrea > > On Tue, Jun 14, 2016 at 12:08 PM, Michael Burman > wrote: > >> Currently Heapster stores in internal memory few minutes of data and >> allows queries that request this data (through its REST-interface). The >> consume part will just request the data from the HWKMETRICS instead. >> >> - Micke >> >> ----- Original Message ----- >> From: "Thomas Heute" >> To: "Discussions around Hawkular development" < >> hawkular-dev at lists.jboss.org> >> Sent: Tuesday, June 14, 2016 4:09:40 PM >> Subject: Re: [Hawkular-dev] Hawkular.org >> >> >> >> On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman < miburman at redhat.com > >> wrote: >> >> >> Consumers is terrible word for any client, as they both consume as well >> as produce the data. >> >> Well that was actually reflecting the current state, we have "things" >> that feed data to the server and "things" that consume data from the >> server. The client libraries provide an API to feed and consume. >> >> >> For example for Heapster, we currently produce the data, however at the >> moment I'm creating a change that will consume the data from HWKMETRICS. >> >> Why does it consume data now ? >> >> Thomas >> >> >> >> >> Integration / clients is far more used and known word, while >> consumer/producer is something more specific and implies a design pattern. >> >> - Micke >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160615/27390de6/attachment.html From hrupp at redhat.com Wed Jun 15 04:17:16 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Wed, 15 Jun 2016 10:17:16 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> Message-ID: <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> On 14 Jun 2016, at 22:32, Stefan Negrea wrote: > I do not see the idea proposed yet, but why not structure the website > around major projects? We have Hawkular community, Hawkular Services, > Hawkular Metrics, and APM. Projects like Inventory or the clients > would > fall under Hawkular Services umbrella. So rather than designing a > generic > structure with everything make individual sub-sites and then apply the > structure you proposed. I think even if/when Hawkular-metrics gets its own section (which is well warranted as we create a metrics distribution), we need to make sure that it blends well into the Hawkular-services documentation. We can for sure use some include tags to accomplish this. I think Hawkular-services should now be the main/default focus area of hawkular.org (at least from the non-APM side) Likewise we should also be careful with external documentation like gitbook. I have seen some pretty good and comprehensive documentation there, so the idea behind is good. An issue is certainly that it is yet another place for stuff and dilutes the content on hawkular.org. Perhaps there is a way to include/iframe it, the experience could potentially be good, as some of the current (long) pages have issues with the navigation via the page-tree in the left part. On the other hand (and I think this was mentioned already) there may be a way to include content from hawkular.org into the gitbook, so that it exists in both forms, but from one source (-> consistency) From hrupp at redhat.com Wed Jun 15 04:25:13 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Wed, 15 Jun 2016 10:25:13 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> Message-ID: <9343924D-352E-45A1-8A34-9760BD50F6B5@redhat.com> On 15 Jun 2016, at 10:17, Heiko W.Rupp wrote: > use some include tags to accomplish this. I think Hawkular-services > should now be the main/default focus area of hawkular.org (at least Well, in fact as Hawkular-services is the core of Hawkular-community release, the two can be seen as two factes of the same, as Thomas mentioned with "Hawkular server": two downloads, a bit of a different setup guide (h-c includes C*, while h-s is byoC* and UI). From theute at redhat.com Wed Jun 15 04:29:10 2016 From: theute at redhat.com (Thomas Heute) Date: Wed, 15 Jun 2016 10:29:10 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> Message-ID: On Wed, Jun 15, 2016 at 10:17 AM, Heiko W.Rupp wrote: > On 14 Jun 2016, at 22:32, Stefan Negrea wrote: > > > I do not see the idea proposed yet, but why not structure the website > > around major projects? We have Hawkular community, Hawkular Services, > > Hawkular Metrics, and APM. Projects like Inventory or the clients > > would > > fall under Hawkular Services umbrella. So rather than designing a > > generic > > structure with everything make individual sub-sites and then apply the > > structure you proposed. > > I think even if/when Hawkular-metrics gets its own section (which is > well > warranted as we create a metrics distribution), we need to make sure > that > it blends well into the Hawkular-services documentation. We can for sure > use some include tags to accomplish this. I think Hawkular-services > should now be the main/default focus area of hawkular.org (at least > from the non-APM side) > +1 > > Likewise we should also be careful with external documentation like > gitbook. I have seen some pretty good and comprehensive documentation > there, so the idea behind is good. An issue is certainly that it is yet > another > place for stuff and dilutes the content on hawkular.org. > Perhaps there is a way to include/iframe it, the experience could > potentially > be good, as some of the current (long) pages have issues with the > navigation > via the page-tree in the left part. > On the other hand (and I think this was mentioned already) there may be > a way to include content from hawkular.org into the gitbook, so that it > exists in both forms, but from one source (-> consistency) > Agreed. Gary could you look into the options to "blend" gitbook.io content better into hawkular.org ? Here is the reference point: http://www.hawkular.org/docs/components/btm/index.html Maybe iFraming https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ would work... Maybe using a custom theme that adds our hawkular.org header/footer in gitbook.io would work (I didn't see how to apply a theme to all books though)... I gave you admin rights if you need to poke around, but I didn't see anything there that would help us... Thomas > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160615/cd35b224/attachment.html From gbrown at redhat.com Wed Jun 15 04:36:40 2016 From: gbrown at redhat.com (Gary Brown) Date: Wed, 15 Jun 2016 04:36:40 -0400 (EDT) Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> Message-ID: <500415568.58218328.1465979799999.JavaMail.zimbra@redhat.com> ----- Original Message ----- > > > On Wed, Jun 15, 2016 at 10:17 AM, Heiko W.Rupp < hrupp at redhat.com > wrote: > > > On 14 Jun 2016, at 22:32, Stefan Negrea wrote: > > > I do not see the idea proposed yet, but why not structure the website > > around major projects? We have Hawkular community, Hawkular Services, > > Hawkular Metrics, and APM. Projects like Inventory or the clients > > would > > fall under Hawkular Services umbrella. So rather than designing a > > generic > > structure with everything make individual sub-sites and then apply the > > structure you proposed. > > I think even if/when Hawkular-metrics gets its own section (which is > well > warranted as we create a metrics distribution), we need to make sure > that > it blends well into the Hawkular-services documentation. We can for sure > use some include tags to accomplish this. I think Hawkular-services > should now be the main/default focus area of hawkular.org (at least > from the non-APM side) > > +1 > > > > Likewise we should also be careful with external documentation like > gitbook. I have seen some pretty good and comprehensive documentation > there, so the idea behind is good. An issue is certainly that it is yet > another > place for stuff and dilutes the content on hawkular.org . > Perhaps there is a way to include/iframe it, the experience could > potentially > be good, as some of the current (long) pages have issues with the > navigation > via the page-tree in the left part. > On the other hand (and I think this was mentioned already) there may be > a way to include content from hawkular.org into the gitbook, so that it > exists in both forms, but from one source (-> consistency) > > Agreed. > Gary could you look into the options to "blend" gitbook.io content better > into hawkular.org ? > > Here is the reference point: > http://www.hawkular.org/docs/components/btm/index.html > Maybe iFraming https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > would work... > Maybe using a custom theme that adds our hawkular.org header/footer in > gitbook.io would work (I didn't see how to apply a theme to all books > though)... > > I gave you admin rights if you need to poke around, but I didn't see anything > there that would help us... Ok will take a look. Regards Gary > > Thomas > > > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From gbrown at redhat.com Wed Jun 15 06:01:42 2016 From: gbrown at redhat.com (Gary Brown) Date: Wed, 15 Jun 2016 06:01:42 -0400 (EDT) Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> Message-ID: <1420071396.58230186.1465984902159.JavaMail.zimbra@redhat.com> Hi http://pasteboard.co/1HmIxzsJ.png Tried using an iframe - problems are: 1) Border around iframe - not sure if this can be reduced/removed 2) When left hand menu showing, it is not possible to add comments (i.e. no + sign appears) 3) When menu hidden, plus sign shows, but asks to sign in to comment - when link selected the iframe content goes blank So not sure iframe is a workable solution. Will see what customisations can be made to the gitbook itself to look more integrated - however wondering whether we should do much customisation, as I think users know they are navigating from a website to documentation, so would not be concerned with a different look and feel - as long as a consistent approach was used for all documentation. Regards Gary ----- Original Message ----- > > > On Wed, Jun 15, 2016 at 10:17 AM, Heiko W.Rupp < hrupp at redhat.com > wrote: > > > On 14 Jun 2016, at 22:32, Stefan Negrea wrote: > > > I do not see the idea proposed yet, but why not structure the website > > around major projects? We have Hawkular community, Hawkular Services, > > Hawkular Metrics, and APM. Projects like Inventory or the clients > > would > > fall under Hawkular Services umbrella. So rather than designing a > > generic > > structure with everything make individual sub-sites and then apply the > > structure you proposed. > > I think even if/when Hawkular-metrics gets its own section (which is > well > warranted as we create a metrics distribution), we need to make sure > that > it blends well into the Hawkular-services documentation. We can for sure > use some include tags to accomplish this. I think Hawkular-services > should now be the main/default focus area of hawkular.org (at least > from the non-APM side) > > +1 > > > > Likewise we should also be careful with external documentation like > gitbook. I have seen some pretty good and comprehensive documentation > there, so the idea behind is good. An issue is certainly that it is yet > another > place for stuff and dilutes the content on hawkular.org . > Perhaps there is a way to include/iframe it, the experience could > potentially > be good, as some of the current (long) pages have issues with the > navigation > via the page-tree in the left part. > On the other hand (and I think this was mentioned already) there may be > a way to include content from hawkular.org into the gitbook, so that it > exists in both forms, but from one source (-> consistency) > > Agreed. > Gary could you look into the options to "blend" gitbook.io content better > into hawkular.org ? > > Here is the reference point: > http://www.hawkular.org/docs/components/btm/index.html > Maybe iFraming https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > would work... > Maybe using a custom theme that adds our hawkular.org header/footer in > gitbook.io would work (I didn't see how to apply a theme to all books > though)... > > I gave you admin rights if you need to poke around, but I didn't see anything > there that would help us... > > Thomas > > > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From theute at redhat.com Wed Jun 15 06:47:09 2016 From: theute at redhat.com (Thomas Heute) Date: Wed, 15 Jun 2016 12:47:09 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: <1420071396.58230186.1465984902159.JavaMail.zimbra@redhat.com> References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> <1420071396.58230186.1465984902159.JavaMail.zimbra@redhat.com> Message-ID: On Wed, Jun 15, 2016 at 12:01 PM, Gary Brown wrote: > Hi > > http://pasteboard.co/1HmIxzsJ.png > > Tried using an iframe - problems are: > > 1) Border around iframe - not sure if this can be reduced/removed > > 2) When left hand menu showing, it is not possible to add comments (i.e. > no + sign appears) > > 3) When menu hidden, plus sign shows, but asks to sign in to comment - > when link selected the iframe content goes blank > > So not sure iframe is a workable solution. > > Will see what customisations can be made to the gitbook itself to look > more integrated - however wondering whether we should do much > customisation, as I think users know they are navigating from a website to > documentation, so would not be concerned with a different look and feel - > as long as a consistent approach was used for all documentation. > Unless they arrive on the documentation from a Google search ;) Thomas > > Regards > Gary > > ----- Original Message ----- > > > > > > On Wed, Jun 15, 2016 at 10:17 AM, Heiko W.Rupp < hrupp at redhat.com > > wrote: > > > > > > On 14 Jun 2016, at 22:32, Stefan Negrea wrote: > > > > > I do not see the idea proposed yet, but why not structure the website > > > around major projects? We have Hawkular community, Hawkular Services, > > > Hawkular Metrics, and APM. Projects like Inventory or the clients > > > would > > > fall under Hawkular Services umbrella. So rather than designing a > > > generic > > > structure with everything make individual sub-sites and then apply the > > > structure you proposed. > > > > I think even if/when Hawkular-metrics gets its own section (which is > > well > > warranted as we create a metrics distribution), we need to make sure > > that > > it blends well into the Hawkular-services documentation. We can for sure > > use some include tags to accomplish this. I think Hawkular-services > > should now be the main/default focus area of hawkular.org (at least > > from the non-APM side) > > > > +1 > > > > > > > > Likewise we should also be careful with external documentation like > > gitbook. I have seen some pretty good and comprehensive documentation > > there, so the idea behind is good. An issue is certainly that it is yet > > another > > place for stuff and dilutes the content on hawkular.org . > > Perhaps there is a way to include/iframe it, the experience could > > potentially > > be good, as some of the current (long) pages have issues with the > > navigation > > via the page-tree in the left part. > > On the other hand (and I think this was mentioned already) there may be > > a way to include content from hawkular.org into the gitbook, so that it > > exists in both forms, but from one source (-> consistency) > > > > Agreed. > > Gary could you look into the options to "blend" gitbook.io content > better > > into hawkular.org ? > > > > Here is the reference point: > > http://www.hawkular.org/docs/components/btm/index.html > > Maybe iFraming > https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > > would work... > > Maybe using a custom theme that adds our hawkular.org header/footer in > > gitbook.io would work (I didn't see how to apply a theme to all books > > though)... > > > > I gave you admin rights if you need to poke around, but I didn't see > anything > > there that would help us... > > > > Thomas > > > > > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160615/3a50ebaf/attachment.html From gbrown at redhat.com Wed Jun 15 06:54:17 2016 From: gbrown at redhat.com (Gary Brown) Date: Wed, 15 Jun 2016 06:54:17 -0400 (EDT) Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> <1420071396.58230186.1465984902159.JavaMail.zimbra@redhat.com> Message-ID: <1588701406.58239517.1465988057901.JavaMail.zimbra@redhat.com> Its possible to customise the header/footer html with the current gitbook version being used by APM: header: http://pasteboard.co/1Hq9NDo9.png footer: http://pasteboard.co/1HqbdKdx.png Just need a suitable html fragment/ banner image to be provided. The header is same line as the search box, so needs to be constrained. Regards Gary ----- Original Message ----- > > > On Wed, Jun 15, 2016 at 12:01 PM, Gary Brown < gbrown at redhat.com > wrote: > > > Hi > > http://pasteboard.co/1HmIxzsJ.png > > Tried using an iframe - problems are: > > 1) Border around iframe - not sure if this can be reduced/removed > > 2) When left hand menu showing, it is not possible to add comments (i.e. no + > sign appears) > > 3) When menu hidden, plus sign shows, but asks to sign in to comment - when > link selected the iframe content goes blank > > So not sure iframe is a workable solution. > > Will see what customisations can be made to the gitbook itself to look more > integrated - however wondering whether we should do much customisation, as I > think users know they are navigating from a website to documentation, so > would not be concerned with a different look and feel - as long as a > consistent approach was used for all documentation. > > Unless they arrive on the documentation from a Google search ;) > > Thomas > > > > Regards > Gary > > ----- Original Message ----- > > > > > > On Wed, Jun 15, 2016 at 10:17 AM, Heiko W.Rupp < hrupp at redhat.com > wrote: > > > > > > On 14 Jun 2016, at 22:32, Stefan Negrea wrote: > > > > > I do not see the idea proposed yet, but why not structure the website > > > around major projects? We have Hawkular community, Hawkular Services, > > > Hawkular Metrics, and APM. Projects like Inventory or the clients > > > would > > > fall under Hawkular Services umbrella. So rather than designing a > > > generic > > > structure with everything make individual sub-sites and then apply the > > > structure you proposed. > > > > I think even if/when Hawkular-metrics gets its own section (which is > > well > > warranted as we create a metrics distribution), we need to make sure > > that > > it blends well into the Hawkular-services documentation. We can for sure > > use some include tags to accomplish this. I think Hawkular-services > > should now be the main/default focus area of hawkular.org (at least > > from the non-APM side) > > > > +1 > > > > > > > > Likewise we should also be careful with external documentation like > > gitbook. I have seen some pretty good and comprehensive documentation > > there, so the idea behind is good. An issue is certainly that it is yet > > another > > place for stuff and dilutes the content on hawkular.org . > > Perhaps there is a way to include/iframe it, the experience could > > potentially > > be good, as some of the current (long) pages have issues with the > > navigation > > via the page-tree in the left part. > > On the other hand (and I think this was mentioned already) there may be > > a way to include content from hawkular.org into the gitbook, so that it > > exists in both forms, but from one source (-> consistency) > > > > Agreed. > > Gary could you look into the options to "blend" gitbook.io content better > > into hawkular.org ? > > > > Here is the reference point: > > http://www.hawkular.org/docs/components/btm/index.html > > Maybe iFraming > > https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > > would work... > > Maybe using a custom theme that adds our hawkular.org header/footer in > > gitbook.io would work (I didn't see how to apply a theme to all books > > though)... > > > > I gave you admin rights if you need to poke around, but I didn't see > > anything > > there that would help us... > > > > Thomas > > > > > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From theute at redhat.com Wed Jun 15 07:04:49 2016 From: theute at redhat.com (Thomas Heute) Date: Wed, 15 Jun 2016 13:04:49 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: <1588701406.58239517.1465988057901.JavaMail.zimbra@redhat.com> References: <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> <1420071396.58230186.1465984902159.JavaMail.zimbra@redhat.com> <1588701406.58239517.1465988057901.JavaMail.zimbra@redhat.com> Message-ID: But can it be applied to all books for an organization or does it need to be copied over all the books GItHub repos ? On Wed, Jun 15, 2016 at 12:54 PM, Gary Brown wrote: > Its possible to customise the header/footer html with the current gitbook > version being used by APM: > > header: http://pasteboard.co/1Hq9NDo9.png > footer: http://pasteboard.co/1HqbdKdx.png > > Just need a suitable html fragment/ banner image to be provided. > > The header is same line as the search box, so needs to be constrained. > > Regards > Gary > > ----- Original Message ----- > > > > > > On Wed, Jun 15, 2016 at 12:01 PM, Gary Brown < gbrown at redhat.com > > wrote: > > > > > > Hi > > > > http://pasteboard.co/1HmIxzsJ.png > > > > Tried using an iframe - problems are: > > > > 1) Border around iframe - not sure if this can be reduced/removed > > > > 2) When left hand menu showing, it is not possible to add comments (i.e. > no + > > sign appears) > > > > 3) When menu hidden, plus sign shows, but asks to sign in to comment - > when > > link selected the iframe content goes blank > > > > So not sure iframe is a workable solution. > > > > Will see what customisations can be made to the gitbook itself to look > more > > integrated - however wondering whether we should do much customisation, > as I > > think users know they are navigating from a website to documentation, so > > would not be concerned with a different look and feel - as long as a > > consistent approach was used for all documentation. > > > > Unless they arrive on the documentation from a Google search ;) > > > > Thomas > > > > > > > > Regards > > Gary > > > > ----- Original Message ----- > > > > > > > > > On Wed, Jun 15, 2016 at 10:17 AM, Heiko W.Rupp < hrupp at redhat.com > > wrote: > > > > > > > > > On 14 Jun 2016, at 22:32, Stefan Negrea wrote: > > > > > > > I do not see the idea proposed yet, but why not structure the website > > > > around major projects? We have Hawkular community, Hawkular Services, > > > > Hawkular Metrics, and APM. Projects like Inventory or the clients > > > > would > > > > fall under Hawkular Services umbrella. So rather than designing a > > > > generic > > > > structure with everything make individual sub-sites and then apply > the > > > > structure you proposed. > > > > > > I think even if/when Hawkular-metrics gets its own section (which is > > > well > > > warranted as we create a metrics distribution), we need to make sure > > > that > > > it blends well into the Hawkular-services documentation. We can for > sure > > > use some include tags to accomplish this. I think Hawkular-services > > > should now be the main/default focus area of hawkular.org (at least > > > from the non-APM side) > > > > > > +1 > > > > > > > > > > > > Likewise we should also be careful with external documentation like > > > gitbook. I have seen some pretty good and comprehensive documentation > > > there, so the idea behind is good. An issue is certainly that it is yet > > > another > > > place for stuff and dilutes the content on hawkular.org . > > > Perhaps there is a way to include/iframe it, the experience could > > > potentially > > > be good, as some of the current (long) pages have issues with the > > > navigation > > > via the page-tree in the left part. > > > On the other hand (and I think this was mentioned already) there may be > > > a way to include content from hawkular.org into the gitbook, so that > it > > > exists in both forms, but from one source (-> consistency) > > > > > > Agreed. > > > Gary could you look into the options to "blend" gitbook.io content > better > > > into hawkular.org ? > > > > > > Here is the reference point: > > > http://www.hawkular.org/docs/components/btm/index.html > > > Maybe iFraming > > > https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > > > would work... > > > Maybe using a custom theme that adds our hawkular.org header/footer in > > > gitbook.io would work (I didn't see how to apply a theme to all books > > > though)... > > > > > > I gave you admin rights if you need to poke around, but I didn't see > > > anything > > > there that would help us... > > > > > > Thomas > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160615/8eddeb7b/attachment-0001.html From gbrown at redhat.com Wed Jun 15 07:12:39 2016 From: gbrown at redhat.com (Gary Brown) Date: Wed, 15 Jun 2016 07:12:39 -0400 (EDT) Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> <1420071396.58230186.1465984902159.JavaMail.zimbra@redhat.com> <1588701406.58239517.1465988057901.JavaMail.zimbra@redhat.com> Message-ID: <141898707.58266862.1465989159373.JavaMail.zimbra@redhat.com> Its per book so would need to be copied: header/footer html files: https://github.com/hawkular/hawkular-apm-user-guide/tree/master/layouts referenced from: https://github.com/hawkular/hawkular-apm-user-guide/blob/master/book.json#L9-L10 Regards Gary ----- Original Message ----- > But can it be applied to all books for an organization or does it need to be > copied over all the books GItHub repos ? > > On Wed, Jun 15, 2016 at 12:54 PM, Gary Brown < gbrown at redhat.com > wrote: > > > Its possible to customise the header/footer html with the current gitbook > version being used by APM: > > header: http://pasteboard.co/1Hq9NDo9.png > footer: http://pasteboard.co/1HqbdKdx.png > > Just need a suitable html fragment/ banner image to be provided. > > The header is same line as the search box, so needs to be constrained. > > Regards > Gary > > ----- Original Message ----- > > > > > > On Wed, Jun 15, 2016 at 12:01 PM, Gary Brown < gbrown at redhat.com > wrote: > > > > > > Hi > > > > http://pasteboard.co/1HmIxzsJ.png > > > > Tried using an iframe - problems are: > > > > 1) Border around iframe - not sure if this can be reduced/removed > > > > 2) When left hand menu showing, it is not possible to add comments (i.e. no > > + > > sign appears) > > > > 3) When menu hidden, plus sign shows, but asks to sign in to comment - when > > link selected the iframe content goes blank > > > > So not sure iframe is a workable solution. > > > > Will see what customisations can be made to the gitbook itself to look more > > integrated - however wondering whether we should do much customisation, as > > I > > think users know they are navigating from a website to documentation, so > > would not be concerned with a different look and feel - as long as a > > consistent approach was used for all documentation. > > > > Unless they arrive on the documentation from a Google search ;) > > > > Thomas > > > > > > > > Regards > > Gary > > > > ----- Original Message ----- > > > > > > > > > On Wed, Jun 15, 2016 at 10:17 AM, Heiko W.Rupp < hrupp at redhat.com > > > > wrote: > > > > > > > > > On 14 Jun 2016, at 22:32, Stefan Negrea wrote: > > > > > > > I do not see the idea proposed yet, but why not structure the website > > > > around major projects? We have Hawkular community, Hawkular Services, > > > > Hawkular Metrics, and APM. Projects like Inventory or the clients > > > > would > > > > fall under Hawkular Services umbrella. So rather than designing a > > > > generic > > > > structure with everything make individual sub-sites and then apply the > > > > structure you proposed. > > > > > > I think even if/when Hawkular-metrics gets its own section (which is > > > well > > > warranted as we create a metrics distribution), we need to make sure > > > that > > > it blends well into the Hawkular-services documentation. We can for sure > > > use some include tags to accomplish this. I think Hawkular-services > > > should now be the main/default focus area of hawkular.org (at least > > > from the non-APM side) > > > > > > +1 > > > > > > > > > > > > Likewise we should also be careful with external documentation like > > > gitbook. I have seen some pretty good and comprehensive documentation > > > there, so the idea behind is good. An issue is certainly that it is yet > > > another > > > place for stuff and dilutes the content on hawkular.org . > > > Perhaps there is a way to include/iframe it, the experience could > > > potentially > > > be good, as some of the current (long) pages have issues with the > > > navigation > > > via the page-tree in the left part. > > > On the other hand (and I think this was mentioned already) there may be > > > a way to include content from hawkular.org into the gitbook, so that it > > > exists in both forms, but from one source (-> consistency) > > > > > > Agreed. > > > Gary could you look into the options to "blend" gitbook.io content better > > > into hawkular.org ? > > > > > > Here is the reference point: > > > http://www.hawkular.org/docs/components/btm/index.html > > > Maybe iFraming > > > https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > > > would work... > > > Maybe using a custom theme that adds our hawkular.org header/footer in > > > gitbook.io would work (I didn't see how to apply a theme to all books > > > though)... > > > > > > I gave you admin rights if you need to poke around, but I didn't see > > > anything > > > there that would help us... > > > > > > Thomas > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From theute at redhat.com Wed Jun 15 08:01:57 2016 From: theute at redhat.com (Thomas Heute) Date: Wed, 15 Jun 2016 14:01:57 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: <141898707.58266862.1465989159373.JavaMail.zimbra@redhat.com> References: <2700492A-2471-4F99-8E8C-A14DF16412BB@redhat.com> <1420071396.58230186.1465984902159.JavaMail.zimbra@redhat.com> <1588701406.58239517.1465988057901.JavaMail.zimbra@redhat.com> <141898707.58266862.1465989159373.JavaMail.zimbra@redhat.com> Message-ID: On Wed, Jun 15, 2016 at 1:12 PM, Gary Brown wrote: > Its per book so would need to be copied: > That's quiet annoying :( And Gitbook doesn't support gitmodules it seems: https://github.com/theute/test2 --> https://theute.gitbooks.io/test2/content/ Thomas > > header/footer html files: > https://github.com/hawkular/hawkular-apm-user-guide/tree/master/layouts > > referenced from: > https://github.com/hawkular/hawkular-apm-user-guide/blob/master/book.json#L9-L10 > > Regards > Gary > > ----- Original Message ----- > > But can it be applied to all books for an organization or does it need > to be > > copied over all the books GItHub repos ? > > > > On Wed, Jun 15, 2016 at 12:54 PM, Gary Brown < gbrown at redhat.com > > wrote: > > > > > > Its possible to customise the header/footer html with the current gitbook > > version being used by APM: > > > > header: http://pasteboard.co/1Hq9NDo9.png > > footer: http://pasteboard.co/1HqbdKdx.png > > > > Just need a suitable html fragment/ banner image to be provided. > > > > The header is same line as the search box, so needs to be constrained. > > > > Regards > > Gary > > > > ----- Original Message ----- > > > > > > > > > On Wed, Jun 15, 2016 at 12:01 PM, Gary Brown < gbrown at redhat.com > > wrote: > > > > > > > > > Hi > > > > > > http://pasteboard.co/1HmIxzsJ.png > > > > > > Tried using an iframe - problems are: > > > > > > 1) Border around iframe - not sure if this can be reduced/removed > > > > > > 2) When left hand menu showing, it is not possible to add comments > (i.e. no > > > + > > > sign appears) > > > > > > 3) When menu hidden, plus sign shows, but asks to sign in to comment - > when > > > link selected the iframe content goes blank > > > > > > So not sure iframe is a workable solution. > > > > > > Will see what customisations can be made to the gitbook itself to look > more > > > integrated - however wondering whether we should do much > customisation, as > > > I > > > think users know they are navigating from a website to documentation, > so > > > would not be concerned with a different look and feel - as long as a > > > consistent approach was used for all documentation. > > > > > > Unless they arrive on the documentation from a Google search ;) > > > > > > Thomas > > > > > > > > > > > > Regards > > > Gary > > > > > > ----- Original Message ----- > > > > > > > > > > > > On Wed, Jun 15, 2016 at 10:17 AM, Heiko W.Rupp < hrupp at redhat.com > > > > > wrote: > > > > > > > > > > > > On 14 Jun 2016, at 22:32, Stefan Negrea wrote: > > > > > > > > > I do not see the idea proposed yet, but why not structure the > website > > > > > around major projects? We have Hawkular community, Hawkular > Services, > > > > > Hawkular Metrics, and APM. Projects like Inventory or the clients > > > > > would > > > > > fall under Hawkular Services umbrella. So rather than designing a > > > > > generic > > > > > structure with everything make individual sub-sites and then apply > the > > > > > structure you proposed. > > > > > > > > I think even if/when Hawkular-metrics gets its own section (which is > > > > well > > > > warranted as we create a metrics distribution), we need to make sure > > > > that > > > > it blends well into the Hawkular-services documentation. We can for > sure > > > > use some include tags to accomplish this. I think Hawkular-services > > > > should now be the main/default focus area of hawkular.org (at least > > > > from the non-APM side) > > > > > > > > +1 > > > > > > > > > > > > > > > > Likewise we should also be careful with external documentation like > > > > gitbook. I have seen some pretty good and comprehensive documentation > > > > there, so the idea behind is good. An issue is certainly that it is > yet > > > > another > > > > place for stuff and dilutes the content on hawkular.org . > > > > Perhaps there is a way to include/iframe it, the experience could > > > > potentially > > > > be good, as some of the current (long) pages have issues with the > > > > navigation > > > > via the page-tree in the left part. > > > > On the other hand (and I think this was mentioned already) there may > be > > > > a way to include content from hawkular.org into the gitbook, so > that it > > > > exists in both forms, but from one source (-> consistency) > > > > > > > > Agreed. > > > > Gary could you look into the options to "blend" gitbook.io content > better > > > > into hawkular.org ? > > > > > > > > Here is the reference point: > > > > http://www.hawkular.org/docs/components/btm/index.html > > > > Maybe iFraming > > > > https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > > > > would work... > > > > Maybe using a custom theme that adds our hawkular.org header/footer > in > > > > gitbook.io would work (I didn't see how to apply a theme to all > books > > > > though)... > > > > > > > > I gave you admin rights if you need to poke around, but I didn't see > > > > anything > > > > there that would help us... > > > > > > > > Thomas > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > hawkular-dev mailing list > > > > hawkular-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > hawkular-dev mailing list > > > > hawkular-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160615/f3f8fe6a/attachment.html From gbrown at redhat.com Wed Jun 15 08:40:41 2016 From: gbrown at redhat.com (Gary Brown) Date: Wed, 15 Jun 2016 08:40:41 -0400 (EDT) Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1420071396.58230186.1465984902159.JavaMail.zimbra@redhat.com> <1588701406.58239517.1465988057901.JavaMail.zimbra@redhat.com> <141898707.58266862.1465989159373.JavaMail.zimbra@redhat.com> Message-ID: <718764524.58286629.1465994441285.JavaMail.zimbra@redhat.com> I know, but how often would you expect the header/footer to change? ----- Original Message ----- > > > On Wed, Jun 15, 2016 at 1:12 PM, Gary Brown < gbrown at redhat.com > wrote: > > > Its per book so would need to be copied: > > That's quiet annoying :( And Gitbook doesn't support gitmodules it seems: > https://github.com/theute/test2 --> https://theute.gitbooks.io/test2/content/ > > > > Thomas > > > > header/footer html files: > https://github.com/hawkular/hawkular-apm-user-guide/tree/master/layouts > > referenced from: > https://github.com/hawkular/hawkular-apm-user-guide/blob/master/book.json#L9-L10 > > Regards > Gary > > ----- Original Message ----- > > But can it be applied to all books for an organization or does it need to > > be > > copied over all the books GItHub repos ? > > > > On Wed, Jun 15, 2016 at 12:54 PM, Gary Brown < gbrown at redhat.com > wrote: > > > > > > Its possible to customise the header/footer html with the current gitbook > > version being used by APM: > > > > header: http://pasteboard.co/1Hq9NDo9.png > > footer: http://pasteboard.co/1HqbdKdx.png > > > > Just need a suitable html fragment/ banner image to be provided. > > > > The header is same line as the search box, so needs to be constrained. > > > > Regards > > Gary > > > > ----- Original Message ----- > > > > > > > > > On Wed, Jun 15, 2016 at 12:01 PM, Gary Brown < gbrown at redhat.com > wrote: > > > > > > > > > Hi > > > > > > http://pasteboard.co/1HmIxzsJ.png > > > > > > Tried using an iframe - problems are: > > > > > > 1) Border around iframe - not sure if this can be reduced/removed > > > > > > 2) When left hand menu showing, it is not possible to add comments (i.e. > > > no > > > + > > > sign appears) > > > > > > 3) When menu hidden, plus sign shows, but asks to sign in to comment - > > > when > > > link selected the iframe content goes blank > > > > > > So not sure iframe is a workable solution. > > > > > > Will see what customisations can be made to the gitbook itself to look > > > more > > > integrated - however wondering whether we should do much customisation, > > > as > > > I > > > think users know they are navigating from a website to documentation, so > > > would not be concerned with a different look and feel - as long as a > > > consistent approach was used for all documentation. > > > > > > Unless they arrive on the documentation from a Google search ;) > > > > > > Thomas > > > > > > > > > > > > Regards > > > Gary > > > > > > ----- Original Message ----- > > > > > > > > > > > > On Wed, Jun 15, 2016 at 10:17 AM, Heiko W.Rupp < hrupp at redhat.com > > > > > wrote: > > > > > > > > > > > > On 14 Jun 2016, at 22:32, Stefan Negrea wrote: > > > > > > > > > I do not see the idea proposed yet, but why not structure the website > > > > > around major projects? We have Hawkular community, Hawkular Services, > > > > > Hawkular Metrics, and APM. Projects like Inventory or the clients > > > > > would > > > > > fall under Hawkular Services umbrella. So rather than designing a > > > > > generic > > > > > structure with everything make individual sub-sites and then apply > > > > > the > > > > > structure you proposed. > > > > > > > > I think even if/when Hawkular-metrics gets its own section (which is > > > > well > > > > warranted as we create a metrics distribution), we need to make sure > > > > that > > > > it blends well into the Hawkular-services documentation. We can for > > > > sure > > > > use some include tags to accomplish this. I think Hawkular-services > > > > should now be the main/default focus area of hawkular.org (at least > > > > from the non-APM side) > > > > > > > > +1 > > > > > > > > > > > > > > > > Likewise we should also be careful with external documentation like > > > > gitbook. I have seen some pretty good and comprehensive documentation > > > > there, so the idea behind is good. An issue is certainly that it is yet > > > > another > > > > place for stuff and dilutes the content on hawkular.org . > > > > Perhaps there is a way to include/iframe it, the experience could > > > > potentially > > > > be good, as some of the current (long) pages have issues with the > > > > navigation > > > > via the page-tree in the left part. > > > > On the other hand (and I think this was mentioned already) there may be > > > > a way to include content from hawkular.org into the gitbook, so that it > > > > exists in both forms, but from one source (-> consistency) > > > > > > > > Agreed. > > > > Gary could you look into the options to "blend" gitbook.io content > > > > better > > > > into hawkular.org ? > > > > > > > > Here is the reference point: > > > > http://www.hawkular.org/docs/components/btm/index.html > > > > Maybe iFraming > > > > https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ > > > > would work... > > > > Maybe using a custom theme that adds our hawkular.org header/footer in > > > > gitbook.io would work (I didn't see how to apply a theme to all books > > > > though)... > > > > > > > > I gave you admin rights if you need to poke around, but I didn't see > > > > anything > > > > there that would help us... > > > > > > > > Thomas > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > hawkular-dev mailing list > > > > hawkular-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > hawkular-dev mailing list > > > > hawkular-dev at lists.jboss.org > > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From hrupp at redhat.com Wed Jun 15 12:28:00 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Wed, 15 Jun 2016 18:28:00 +0200 Subject: [Hawkular-dev] Merging of own pull-requests ( please don't ) Message-ID: Hey, I want to remind everyone (including myself :-) that one should not merge ones own pull-requests (and also abstain from directly committing to master). There are many reasons why this is good practice - peer review finds issues - peer review allows discussions on the concrete implementation of a bugfix/feature request - other findings can be addressed in the same pull-request and do not need a subsequent one. - It gives oneself some time to reflect what was done. - It gives time to also add this one little file that was not git-add'ed I totally understand that we are in some areas rather thin on developers (Juca's work on hawkular-services and accounts come to mind) and that there are always situations where a direct commit or self-merged PR is needed. But it should not be the default. I do not want us to get to a structure where only a handful of managers have push rights to force this above mentioned peer review. Thanks Heiko From theute at redhat.com Wed Jun 15 14:08:53 2016 From: theute at redhat.com (Thomas Heute) Date: Wed, 15 Jun 2016 20:08:53 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> Message-ID: Based on that suggestion, here is another proposal. Rectangle means a page Underline is more likely a section on a page Green arrows mean links (To Travis, to gitbook.io...) Let me know what you think of that updated section Thomas On Tue, Jun 14, 2016 at 10:32 PM, Stefan Negrea wrote: > I do not see the idea proposed yet, but why not structure the website > around major projects? We have Hawkular community, Hawkular Services, > Hawkular Metrics, and APM. Projects like Inventory or the clients would > fall under Hawkular Services umbrella. So rather than designing a generic > structure with everything make individual sub-sites and then apply the > structure you proposed. > > The current website was designed when the direction of the community was > different so a re-org along the previous structure is not sufficient. > > Thank you, > Stefan Negrea > > On Tue, Jun 14, 2016 at 12:08 PM, Michael Burman > wrote: > >> Currently Heapster stores in internal memory few minutes of data and >> allows queries that request this data (through its REST-interface). The >> consume part will just request the data from the HWKMETRICS instead. >> >> - Micke >> >> ----- Original Message ----- >> From: "Thomas Heute" >> To: "Discussions around Hawkular development" < >> hawkular-dev at lists.jboss.org> >> Sent: Tuesday, June 14, 2016 4:09:40 PM >> Subject: Re: [Hawkular-dev] Hawkular.org >> >> >> >> On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman < miburman at redhat.com > >> wrote: >> >> >> Consumers is terrible word for any client, as they both consume as well >> as produce the data. >> >> Well that was actually reflecting the current state, we have "things" >> that feed data to the server and "things" that consume data from the >> server. The client libraries provide an API to feed and consume. >> >> >> For example for Heapster, we currently produce the data, however at the >> moment I'm creating a change that will consume the data from HWKMETRICS. >> >> Why does it consume data now ? >> >> Thomas >> >> >> >> >> Integration / clients is far more used and known word, while >> consumer/producer is something more specific and implies a design pattern. >> >> - Micke >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160615/1bb12da4/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: Hawkular.org2.xmind Type: application/octet-stream Size: 101406 bytes Desc: not available Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160615/1bb12da4/attachment-0001.obj From theute at redhat.com Wed Jun 15 14:18:27 2016 From: theute at redhat.com (Thomas Heute) Date: Wed, 15 Jun 2016 20:18:27 +0200 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> Message-ID: Sorry, I meant to sent the PNG file... here it is On Wed, Jun 15, 2016 at 8:08 PM, Thomas Heute wrote: > Based on that suggestion, here is another proposal. > > Rectangle means a page > Underline is more likely a section on a page > Green arrows mean links (To Travis, to gitbook.io...) > > Let me know what you think of that updated section > > Thomas > > On Tue, Jun 14, 2016 at 10:32 PM, Stefan Negrea > wrote: > >> I do not see the idea proposed yet, but why not structure the website >> around major projects? We have Hawkular community, Hawkular Services, >> Hawkular Metrics, and APM. Projects like Inventory or the clients would >> fall under Hawkular Services umbrella. So rather than designing a generic >> structure with everything make individual sub-sites and then apply the >> structure you proposed. >> >> The current website was designed when the direction of the community was >> different so a re-org along the previous structure is not sufficient. >> >> Thank you, >> Stefan Negrea >> >> On Tue, Jun 14, 2016 at 12:08 PM, Michael Burman >> wrote: >> >>> Currently Heapster stores in internal memory few minutes of data and >>> allows queries that request this data (through its REST-interface). The >>> consume part will just request the data from the HWKMETRICS instead. >>> >>> - Micke >>> >>> ----- Original Message ----- >>> From: "Thomas Heute" >>> To: "Discussions around Hawkular development" < >>> hawkular-dev at lists.jboss.org> >>> Sent: Tuesday, June 14, 2016 4:09:40 PM >>> Subject: Re: [Hawkular-dev] Hawkular.org >>> >>> >>> >>> On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman < miburman at redhat.com > >>> wrote: >>> >>> >>> Consumers is terrible word for any client, as they both consume as well >>> as produce the data. >>> >>> Well that was actually reflecting the current state, we have "things" >>> that feed data to the server and "things" that consume data from the >>> server. The client libraries provide an API to feed and consume. >>> >>> >>> For example for Heapster, we currently produce the data, however at the >>> moment I'm creating a change that will consume the data from HWKMETRICS. >>> >>> Why does it consume data now ? >>> >>> Thomas >>> >>> >>> >>> >>> Integration / clients is far more used and known word, while >>> consumer/producer is something more specific and implies a design pattern. >>> >>> - Micke >>> >>> _______________________________________________ >>> hawkular-dev mailing list >>> hawkular-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>> >> >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> >> > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160615/01fe46cf/attachment-0001.html -------------- next part -------------- A non-text attachment was scrubbed... Name: hawkular.org2.png Type: image/png Size: 72864 bytes Desc: not available Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160615/01fe46cf/attachment-0001.png From gbrown at redhat.com Thu Jun 16 03:20:26 2016 From: gbrown at redhat.com (Gary Brown) Date: Thu, 16 Jun 2016 03:20:26 -0400 (EDT) Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> Message-ID: <1838408380.58534009.1466061626977.JavaMail.zimbra@redhat.com> I think the structure is ok, but prefer having Downloads and Documentation at the top level. But instead of the previous structure, still organise based on package, so: Documentation Hawkular Server (link) Quick Start ... Hawkular APM (link) ... Hawkular Metrics (link) ... Hawkular Clients Libraries Java ... Clients ... and similar for downloads. So top level is similar to first structure, but second tier is organised by package rather than book (in terms of docs). Regards Gary ----- Original Message ----- > Sorry, I meant to sent the PNG file... here it is > > On Wed, Jun 15, 2016 at 8:08 PM, Thomas Heute < theute at redhat.com > wrote: > > > > Based on that suggestion, here is another proposal. > > Rectangle means a page > Underline is more likely a section on a page > Green arrows mean links (To Travis, to gitbook.io...) > > Let me know what you think of that updated section > > Thomas > > On Tue, Jun 14, 2016 at 10:32 PM, Stefan Negrea < snegrea at redhat.com > wrote: > > > > I do not see the idea proposed yet, but why not structure the website around > major projects? We have Hawkular community, Hawkular Services, Hawkular > Metrics, and APM. Projects like Inventory or the clients would fall under > Hawkular Services umbrella. So rather than designing a generic structure > with everything make individual sub-sites and then apply the structure you > proposed. > > The current website was designed when the direction of the community was > different so a re-org along the previous structure is not sufficient. > > Thank you, > Stefan Negrea > > On Tue, Jun 14, 2016 at 12:08 PM, Michael Burman < miburman at redhat.com > > wrote: > > > Currently Heapster stores in internal memory few minutes of data and allows > queries that request this data (through its REST-interface). The consume > part will just request the data from the HWKMETRICS instead. > > - Micke > > ----- Original Message ----- > From: "Thomas Heute" < theute at redhat.com > > To: "Discussions around Hawkular development" < hawkular-dev at lists.jboss.org > > > Sent: Tuesday, June 14, 2016 4:09:40 PM > Subject: Re: [Hawkular-dev] Hawkular.org > > > > On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman < miburman at redhat.com > > wrote: > > > Consumers is terrible word for any client, as they both consume as well as > produce the data. > > Well that was actually reflecting the current state, we have "things" that > feed data to the server and "things" that consume data from the server. The > client libraries provide an API to feed and consume. > > > For example for Heapster, we currently produce the data, however at the > moment I'm creating a change that will consume the data from HWKMETRICS. > > Why does it consume data now ? > > Thomas > > > > > Integration / clients is far more used and known word, while > consumer/producer is something more specific and implies a design pattern. > > - Micke > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From theute at redhat.com Thu Jun 16 04:52:36 2016 From: theute at redhat.com (Thomas Heute) Date: Thu, 16 Jun 2016 10:52:36 +0200 Subject: [Hawkular-dev] Merging of own pull-requests ( please don't ) In-Reply-To: References: Message-ID: On Wed, Jun 15, 2016 at 6:28 PM, Heiko W.Rupp wrote: > Hey, > > I want to remind everyone (including myself :-) that one should not merge > ones own pull-requests (and also abstain from directly committing to > master). > > There are many reasons why this is good practice > > - peer review finds issues > - peer review allows discussions on the concrete implementation of > a bugfix/feature request > If you are the one who open a PR, please be reactive on the comments/questions that may be asked so that you don't become the bottleneck yourself. (and if you are busy, please send a quick note on when one can expect an answer, that's less stressful than no answer) If there is no reviewer please chase one, raise to #hawkular/hawkular-dev/Heiko/Alissa if you found noone. > - other findings can be addressed in the same pull-request and do > not need a subsequent one. > - It gives oneself some time to reflect what was done. > - It gives time to also add this one little file that was not git-add'ed > > I totally understand that we are in some areas rather thin on developers > (Juca's work on hawkular-services and accounts come to mind) and that > there are always situations where a direct commit or self-merged PR is > needed. But it should not be the default. > > I do not want us to get to a structure where only a handful of managers > have push rights to force this above mentioned peer review. > Managers with push rights !??! that would be horrible ! THomas > > Thanks > Heiko > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160616/c881c703/attachment.html From hrupp at redhat.com Thu Jun 16 06:28:07 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Thu, 16 Jun 2016 12:28:07 +0200 Subject: [Hawkular-dev] Hawkular Client Ruby In-Reply-To: <1560762093.5804380.1465821222252.JavaMail.zimbra@redhat.com> References: <1915066650.1885733.1464270524457.JavaMail.zimbra@redhat.com> <1560762093.5804380.1465821222252.JavaMail.zimbra@redhat.com> Message-ID: <5ED6B4A8-91BC-4644-835B-C814EEC983DD@redhat.com> Hello, On 13 Jun 2016, at 14:33, Lucas Ponce wrote: > I am not sure if there have been some progress on this topic. Lucas is right. We had a lot of discussions and many pros and cons so that we have to now take a direction and move on. We should go with one single gem - even with the danger that other groups may veto its use inside of ManageIQ until we have fixed the issue they are seeing. If we were to split the gem into two the only sensible way from my point of view would be metrics and other. This would on one side allow us to make 'random' changes to the 'other' part, but also require duplication of the code (or some clever build magic) for everything that is in the base client and deals with connection handling etc. Such a split would also not solve the issue that the 'metrics' part needs to deal with hawkular-metrics version 0.8 servers and hawkular-metrics version 0.15+. Splitting to have 2 versions of the metrics gem for each api-version is not an option either as consumers like ManageIQ may very well need to simultaneously talk to different instances of Hawkular-metrics that run different api-versions. With respect of the valid question about changes being vetoed: - breaking (Ruby) api changes (especially in the metrics area) must not happen in the same major version of the gem - adding of new api methods is still possible - we need to be transparent what we do in the changelog - I expect that other groups also have tests, that are run when we upgrade the gem version in MiQ, so that the pull-request checks show breakage - If s* hits the fan, we need to be quick to react. So going forward: - 1 gem - metrics-client reads on connect the /status endpoint and remembers the hawkular-metrics rest-api version - Endpoints for calls to metrics need to switch according to the api version - For inventory we do not need to support the old rest-api once the new one is available in hawkular-services Heiko From abonas at redhat.com Thu Jun 16 08:04:44 2016 From: abonas at redhat.com (Alissa Bonas) Date: Thu, 16 Jun 2016 15:04:44 +0300 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> Message-ID: +1 to Gary's suggestion to make links from documentation to components, from download to components, etc. Also, I didn't see REST api and ManageIQ in the new proposal - are they gone? Regarding "getting started for developers/developer guide" - I tend to say that documentation section is not the right place for that. Or at least in most of the open source community websites I've seen, it's a separate section either as a top level item or under community section. Worth to put "events" on the main page as already discussed earlier (and if there are photos from past events - even better), and perhaps a splash of a twitter feed that mentions hawkular as well on the main page. It gives a feeling of a "live" project. On Wed, Jun 15, 2016 at 9:08 PM, Thomas Heute wrote: > Based on that suggestion, here is another proposal. > > Rectangle means a page > Underline is more likely a section on a page > Green arrows mean links (To Travis, to gitbook.io...) > > Let me know what you think of that updated section > > Thomas > > On Tue, Jun 14, 2016 at 10:32 PM, Stefan Negrea > wrote: > >> I do not see the idea proposed yet, but why not structure the website >> around major projects? We have Hawkular community, Hawkular Services, >> Hawkular Metrics, and APM. Projects like Inventory or the clients would >> fall under Hawkular Services umbrella. So rather than designing a generic >> structure with everything make individual sub-sites and then apply the >> structure you proposed. >> >> The current website was designed when the direction of the community was >> different so a re-org along the previous structure is not sufficient. >> >> Thank you, >> Stefan Negrea >> >> On Tue, Jun 14, 2016 at 12:08 PM, Michael Burman >> wrote: >> >>> Currently Heapster stores in internal memory few minutes of data and >>> allows queries that request this data (through its REST-interface). The >>> consume part will just request the data from the HWKMETRICS instead. >>> >>> - Micke >>> >>> ----- Original Message ----- >>> From: "Thomas Heute" >>> To: "Discussions around Hawkular development" < >>> hawkular-dev at lists.jboss.org> >>> Sent: Tuesday, June 14, 2016 4:09:40 PM >>> Subject: Re: [Hawkular-dev] Hawkular.org >>> >>> >>> >>> On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman < miburman at redhat.com > >>> wrote: >>> >>> >>> Consumers is terrible word for any client, as they both consume as well >>> as produce the data. >>> >>> Well that was actually reflecting the current state, we have "things" >>> that feed data to the server and "things" that consume data from the >>> server. The client libraries provide an API to feed and consume. >>> >>> >>> For example for Heapster, we currently produce the data, however at the >>> moment I'm creating a change that will consume the data from HWKMETRICS. >>> >>> Why does it consume data now ? >>> >>> Thomas >>> >>> >>> >>> >>> Integration / clients is far more used and known word, while >>> consumer/producer is something more specific and implies a design pattern. >>> >>> - Micke >>> >>> _______________________________________________ >>> hawkular-dev mailing list >>> hawkular-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>> >> >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> >> > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160616/3bd9bc95/attachment.html From snegrea at redhat.com Thu Jun 16 09:33:21 2016 From: snegrea at redhat.com (Stefan Negrea) Date: Thu, 16 Jun 2016 08:33:21 -0500 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: <1838408380.58534009.1466061626977.JavaMail.zimbra@redhat.com> References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> <1838408380.58534009.1466061626977.JavaMail.zimbra@redhat.com> Message-ID: On Thu, Jun 16, 2016 at 2:20 AM, Gary Brown wrote: > I think the structure is ok, but prefer having Downloads and Documentation > at the top level. But instead of the previous structure, still organise > based on package, so: > There is no point having top level Downloads and Documentation if everything is sectioned the way Thomas proposed in the last email. There are a lot of projects and subprojects so mixing downloads or documentation will take the user out of context and present them with something large and hard to navigate. Take documentation for example, it will be very confusing content because it will be a large section with content from unrelated projects mixed together. > > Documentation > Hawkular Server (link) > Quick Start > ... > Hawkular APM (link) > ... > Hawkular Metrics (link) > ... > Hawkular Clients > Libraries > Java > ... > Clients > ... > > and similar for downloads. So top level is similar to first structure, but > second tier is organised by package rather than book (in terms of docs). > > Regards > Gary > > > ----- Original Message ----- > > Sorry, I meant to sent the PNG file... here it is > > > > On Wed, Jun 15, 2016 at 8:08 PM, Thomas Heute < theute at redhat.com > > wrote: > > > > > > > > Based on that suggestion, here is another proposal. > > > > Rectangle means a page > > Underline is more likely a section on a page > > Green arrows mean links (To Travis, to gitbook.io...) > > > > Let me know what you think of that updated section > > > > Thomas > > > > On Tue, Jun 14, 2016 at 10:32 PM, Stefan Negrea < snegrea at redhat.com > > wrote: > > > > > > > > I do not see the idea proposed yet, but why not structure the website > around > > major projects? We have Hawkular community, Hawkular Services, Hawkular > > Metrics, and APM. Projects like Inventory or the clients would fall under > > Hawkular Services umbrella. So rather than designing a generic structure > > with everything make individual sub-sites and then apply the structure > you > > proposed. > > > > The current website was designed when the direction of the community was > > different so a re-org along the previous structure is not sufficient. > > > > Thank you, > > Stefan Negrea > > > > On Tue, Jun 14, 2016 at 12:08 PM, Michael Burman < miburman at redhat.com > > > wrote: > > > > > > Currently Heapster stores in internal memory few minutes of data and > allows > > queries that request this data (through its REST-interface). The consume > > part will just request the data from the HWKMETRICS instead. > > > > - Micke > > > > ----- Original Message ----- > > From: "Thomas Heute" < theute at redhat.com > > > To: "Discussions around Hawkular development" < > hawkular-dev at lists.jboss.org > > > > > Sent: Tuesday, June 14, 2016 4:09:40 PM > > Subject: Re: [Hawkular-dev] Hawkular.org > > > > > > > > On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman < miburman at redhat.com > > > wrote: > > > > > > Consumers is terrible word for any client, as they both consume as well > as > > produce the data. > > > > Well that was actually reflecting the current state, we have "things" > that > > feed data to the server and "things" that consume data from the server. > The > > client libraries provide an API to feed and consume. > > > > > > For example for Heapster, we currently produce the data, however at the > > moment I'm creating a change that will consume the data from HWKMETRICS. > > > > Why does it consume data now ? > > > > Thomas > > > > > > > > > > Integration / clients is far more used and known word, while > > consumer/producer is something more specific and implies a design > pattern. > > > > - Micke > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160616/0515d25e/attachment-0001.html From snegrea at redhat.com Thu Jun 16 12:11:18 2016 From: snegrea at redhat.com (Stefan Negrea) Date: Thu, 16 Jun 2016 11:11:18 -0500 Subject: [Hawkular-dev] Hawkular.org In-Reply-To: References: <1265553183.102271604.1465909592402.JavaMail.zimbra@redhat.com> <43292415.102368387.1465924138218.JavaMail.zimbra@redhat.com> Message-ID: I really like this last revision because the content is sectioned along the way we deliver to users. So when a user navigates the website, the content is always related to what they can directly download and use and not mixed together. I have 3 small proposals: 1) Hawkular and Overview can be combined into one Hawkular Overview or Hawkular (which has the overview of the projects). 2) The Grafana plugin should be moved under Metrics because is for Metrics and only Metrics. 3) Hawkular Server should be renamed Hawkular Services because that the official project name. Thank you, Stefan Negrea Software Engineer On Wed, Jun 15, 2016 at 1:18 PM, Thomas Heute wrote: > Sorry, I meant to sent the PNG file... here it is > > On Wed, Jun 15, 2016 at 8:08 PM, Thomas Heute wrote: > >> Based on that suggestion, here is another proposal. >> >> Rectangle means a page >> Underline is more likely a section on a page >> Green arrows mean links (To Travis, to gitbook.io...) >> >> Let me know what you think of that updated section >> >> Thomas >> >> On Tue, Jun 14, 2016 at 10:32 PM, Stefan Negrea >> wrote: >> >>> I do not see the idea proposed yet, but why not structure the website >>> around major projects? We have Hawkular community, Hawkular Services, >>> Hawkular Metrics, and APM. Projects like Inventory or the clients would >>> fall under Hawkular Services umbrella. So rather than designing a generic >>> structure with everything make individual sub-sites and then apply the >>> structure you proposed. >>> >>> The current website was designed when the direction of the community was >>> different so a re-org along the previous structure is not sufficient. >>> >>> Thank you, >>> Stefan Negrea >>> >>> On Tue, Jun 14, 2016 at 12:08 PM, Michael Burman >>> wrote: >>> >>>> Currently Heapster stores in internal memory few minutes of data and >>>> allows queries that request this data (through its REST-interface). The >>>> consume part will just request the data from the HWKMETRICS instead. >>>> >>>> - Micke >>>> >>>> ----- Original Message ----- >>>> From: "Thomas Heute" >>>> To: "Discussions around Hawkular development" < >>>> hawkular-dev at lists.jboss.org> >>>> Sent: Tuesday, June 14, 2016 4:09:40 PM >>>> Subject: Re: [Hawkular-dev] Hawkular.org >>>> >>>> >>>> >>>> On Tue, Jun 14, 2016 at 3:06 PM, Michael Burman < miburman at redhat.com >>>> > wrote: >>>> >>>> >>>> Consumers is terrible word for any client, as they both consume as well >>>> as produce the data. >>>> >>>> Well that was actually reflecting the current state, we have "things" >>>> that feed data to the server and "things" that consume data from the >>>> server. The client libraries provide an API to feed and consume. >>>> >>>> >>>> For example for Heapster, we currently produce the data, however at the >>>> moment I'm creating a change that will consume the data from HWKMETRICS. >>>> >>>> Why does it consume data now ? >>>> >>>> Thomas >>>> >>>> >>>> >>>> >>>> Integration / clients is far more used and known word, while >>>> consumer/producer is something more specific and implies a design pattern. >>>> >>>> - Micke >>>> >>>> _______________________________________________ >>>> hawkular-dev mailing list >>>> hawkular-dev at lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>>> >>> >>> >>> _______________________________________________ >>> hawkular-dev mailing list >>> hawkular-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>> >>> >> > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160616/7546d48b/attachment.html From anuj1708 at gmail.com Thu Jun 16 14:26:26 2016 From: anuj1708 at gmail.com (Anuj Garg) Date: Thu, 16 Jun 2016 23:56:26 +0530 Subject: [Hawkular-dev] Updates on android Client of hawkular Message-ID: Last 10 days haven't been so handsome to me or android client. Most of it upgraded including ->aerogear Library ->butterknife ->gsm ->support libraries Gradle update is not possible at present as sdkmanager plugin by jake warthon haven't been upgraded and its alternative is forcing me to build multidex application. So I am back to old gradle until I find a workaround. Some part in journey gave happiness too. With PR on hawkular android client accepted. It will work like https://drive.google.com/open?id=0B8tYKC1-UERHNWhSeUZQdmVtS2M Next I am planning to direct clicks on metrics to their chart presentation Thanks Anuj Garg -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160616/0a5af444/attachment.html From mazz at redhat.com Thu Jun 16 15:50:32 2016 From: mazz at redhat.com (John Mazzitelli) Date: Thu, 16 Jun 2016 15:50:32 -0400 (EDT) Subject: [Hawkular-dev] memory footprint with swarm In-Reply-To: <1289634796.7166715.1466106146552.JavaMail.zimbra@redhat.com> Message-ID: <1519301787.7168133.1466106632149.JavaMail.zimbra@redhat.com> I was running the swarm agent and so while I was here, I decided to take a quick look at memory footprint. I took these numbers from the Gnome System Monitor GUI utility. swarm agent: Memory=188M, Resident Memory=208M full wildfly agent: Memory=351M, Resident Memory=378M So swarm agent was roughly half the size of full wildfly agent. This was not a scientific study :) I just started the agent, when I saw it finished initializing, I looked at the System Monitor and read the memory numbers. And Jay claims if he put his mind to it, he can shrink the swarm agent further. :) But we aren't doing any more work on it at the moment. From gbrown at redhat.com Fri Jun 17 05:09:09 2016 From: gbrown at redhat.com (Gary Brown) Date: Fri, 17 Jun 2016 05:09:09 -0400 (EDT) Subject: [Hawkular-dev] Anyone available to review...... Message-ID: <720935067.58743833.1466154549788.JavaMail.zimbra@redhat.com> https://github.com/hawkular/hawkular-apm/pull/444 Thanks. Regards Gary From hrupp at redhat.com Fri Jun 17 05:16:46 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Fri, 17 Jun 2016 11:16:46 +0200 Subject: [Hawkular-dev] Updates on android Client of hawkular In-Reply-To: References: Message-ID: On 16 Jun 2016, at 20:26, Anuj Garg wrote: > Some part in journey gave happiness too. > With PR on hawkular android client accepted. It will work like > https://drive.google.com/open?id=0B8tYKC1-UERHNWhSeUZQdmVtS2M That looks good > Next I am planning to direct clicks on metrics to their chart presentation +1 From theute at redhat.com Fri Jun 17 06:00:56 2016 From: theute at redhat.com (Thomas Heute) Date: Fri, 17 Jun 2016 12:00:56 +0200 Subject: [Hawkular-dev] memory footprint with swarm In-Reply-To: <1519301787.7168133.1466106632149.JavaMail.zimbra@redhat.com> References: <1289634796.7166715.1466106146552.JavaMail.zimbra@redhat.com> <1519301787.7168133.1466106632149.JavaMail.zimbra@redhat.com> Message-ID: Very cool ! On Thu, Jun 16, 2016 at 9:50 PM, John Mazzitelli wrote: > I was running the swarm agent and so while I was here, I decided to take a > quick look at memory footprint. I took these numbers from the Gnome System > Monitor GUI utility. > > swarm agent: > Memory=188M, Resident Memory=208M > > full wildfly agent: > Memory=351M, Resident Memory=378M > > So swarm agent was roughly half the size of full wildfly agent. > > This was not a scientific study :) I just started the agent, when I saw it > finished initializing, I looked at the System Monitor and read the memory > numbers. > > And Jay claims if he put his mind to it, he can shrink the swarm agent > further. :) But we aren't doing any more work on it at the moment. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160617/1a14835c/attachment.html From hrupp at redhat.com Fri Jun 17 06:37:08 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Fri, 17 Jun 2016 12:37:08 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services Message-ID: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> Hey, I was able to make some progress with Dockerizing Hawkular-services More technical details below As it is relatively hard (not impossible) to do stuff like adding a user inside a (immutable) docker container or to edit standalone.xml to enable the agent, we need to decide how we add the (default) user to hawkular docker container and also if/how to enable the embedded agent. Also as we more understand hawkular-services as one package, we should perhaps figure out if we really need the flexibility to modify standalone.xml on the fly with all our snippets and templates or if we create a 'hardcoded' one that can be used for the process going forward. At the moment wildfly10 is our base and will be for a longer period, so the server-supplied standalone.xml will not change anyway. Anyway my Poc is at https://github.com/pilhuhn/hawkular-services/tree/dockerize-all-the-things There are 3 routes that I went (basically refining the process) (If you want to run any you first need to $ mkdir -p /tmp/opt/hawkular as this is where the docker run commands expect the data for now To get a 'working server' you need to "mvn install -Pdev first" 1) dist/ creating a Dockerfile by hand and manually running docker build Dockerfile and then docker-compose to run a container from this image linked to a C* 3.5 one. Base image is the jboss/base-jdk:8 one and the Dockerfile basically overlays the whole hawkular-services distribution on top You can run this with $ docker-compose up 2) docker-dist/ here maven creates the Dockerfile on the fly and feeds it to Docker. This uses the fabric8.io docker plugin from Roland Huss. Again it uses the same base image + overlay as 1). The container tag is derived from the maven properties. To build and run you can go into the directory and then $ mvn docker:build $ mvn docker:start 3) docker-dist2/ Similar to 2) this uses the mvn docker plugin, but this time is uses jboss/wildfly:10.0.0.Final as the base image. Unfortunately it still overlays the whole wildfly from us, but we should be able to filter that out. The good thing is though that the image is already much smaller as in 2) To build and run the same process as 2) applies * The next step is now to figure out how to only apply our changes and not to supply the base wildfly into the conatiner. I certainly need help from someone with maven-fu :) But while the current state is not optimal it shows that this is very much doable and we should proceed. Heiko From hrupp at redhat.com Fri Jun 17 08:50:57 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Fri, 17 Jun 2016 14:50:57 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> Message-ID: On 17 Jun 2016, at 12:37, Heiko W.Rupp wrote: > The next step is now to figure out how to only apply our changes and > not > to > supply the base wildfly into the conatiner. I certainly need help from > someone > with maven-fu :) I have this now in the docker-dist3 module https://github.com/pilhuhn/hawkular-services/tree/dockerize-all-the-things/docker-dist3 As before: $ mvn -Pdev install $ mvn cd docker-dist3 $ mkdir -p /tmp/opt/hawkular $ mvn docker:build $ mvn docker:start == Http2/ssl Dockerizing of services could now also allow to also add the correct alpn jar to the container to enable http2, as the underlying JVM is known and constant (until the underlying base image changes) $ docker run -it hawkular/hawkular-services-mvn3 bash [root at 275fc8b436f7 jboss]# java -version openjdk version "1.8.0_91" OpenJDK Runtime Environment (build 1.8.0_91-b14) OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode) So according to http://www.eclipse.org/jetty/documentation/current/alpn-chapter.html#alpn-versions for 1.8.0u91 alpn 8.1.7.v20160121 is required, which can be retrieved from http://mvnrepository.com/artifact/org.mortbay.jetty.alpn/alpn-boot There is a guide for further work on this http://undertow.io/blog/2015/03/26/HTTP2-In-Wildfly.html It requires SSL though and also away to configure this. From mazz at redhat.com Fri Jun 17 09:25:53 2016 From: mazz at redhat.com (John Mazzitelli) Date: Fri, 17 Jun 2016 09:25:53 -0400 (EDT) Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> Message-ID: <731329596.7332854.1466169953099.JavaMail.zimbra@redhat.com> > As it is relatively hard (not impossible) to do stuff like adding a user > inside a (immutable) docker container or to edit standalone.xml to > enable the agent, we need to decide how we add the (default) user > to hawkular docker container and also if/how to enable the embedded > agent. So I assume what you mean by "hard" is you can't CHANGE the docker image after it is built. Right? Just making sure that is what you mean. To enable the agent would involve running a jboss cli command: ./jboss-cli.sh --connect --controller=127.0.0.1 \ '/subsystem=hawkular-wildfly-agent/:write-attribute(name=enabled,value=true)' Similar CLI commands to get the agent's credentials set up: ./jboss-cli.sh --connect --controller=127.0.0.1 \ /subsystem=hawkular-wildfly-agent/storage-adapter=default/:write-attribute(name=user,value=jdoe) ./jboss-cli.sh --connect --controller=127.0.0.1 \ /subsystem=hawkular-wildfly-agent/storage-adapter=default/:write-attribute(name=password,value=password) You would have to restart the container once you do that to make the change take effect (if we want this to happen without a restart, write a HWKAGENT JIRA, that is probably not hard to get to work). The more difficult part is getting the user to know to run that and where the user gets jboss-cli.sh. I guess you can't run a script that is found inside a docker container? From jpkroehling at redhat.com Fri Jun 17 09:39:53 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Fri, 17 Jun 2016 15:39:53 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: <731329596.7332854.1466169953099.JavaMail.zimbra@redhat.com> References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> <731329596.7332854.1466169953099.JavaMail.zimbra@redhat.com> Message-ID: <4a170b2e-772d-e501-d407-158c5eebffa2@redhat.com> On 17.06.2016 15:25, John Mazzitelli wrote: > You would have to restart the container once you do that to make the change take effect If the server is not up (which is probably the case for the docker image), you might want to use the "offline" flag. - Juca. From hrupp at redhat.com Fri Jun 17 09:42:57 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Fri, 17 Jun 2016 15:42:57 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: <731329596.7332854.1466169953099.JavaMail.zimbra@redhat.com> References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> <731329596.7332854.1466169953099.JavaMail.zimbra@redhat.com> Message-ID: On 17 Jun 2016, at 15:25, John Mazzitelli wrote: > So I assume what you mean by "hard" is you can't CHANGE the docker > image after it is built. Right? Just making sure that is what you > mean. Yes. Mostly There seems to be a way of mounting an image as data image of another container and then from this other container modifying the original one. See "Using the Dockerfile for provisioning" in http://oliverguenther.de/2015/05/docker-containers-for-development/ but I am not yet sure what exactly happens. I think Roland Huss may be able to enlighten us a bit on this. > To enable the agent would involve running a jboss cli command: > > ./jboss-cli.sh --connect --controller=127.0.0.1 \ I think you can do all that -- see https://goldmann.pl/blog/2014/07/23/customizing-the-configuration-of-the-wildfly-docker-image/#_summary You have probably seen that I mount /opt/hawkular from inside the container to /tmp/opt/hawkular on the host. If we would move the config into /opt/hawkular, it would be writable and even modifiable from outside of the container (of course it would still need a restart in the current state). -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht M?nchen HRB 153243 Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander From kurrent93 at gmail.com Fri Jun 17 09:48:53 2016 From: kurrent93 at gmail.com (Anton) Date: Fri, 17 Jun 2016 15:48:53 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> <731329596.7332854.1466169953099.JavaMail.zimbra@redhat.com> Message-ID: On Fri, Jun 17, 2016 at 3:42 PM, Heiko W.Rupp wrote: > > So I assume what you mean by "hard" is you can't CHANGE the docker > > image after it is built. Right? Just making sure that is what you > > mean. > > Yes. Mostl Perhaps having bash access to the running docker container is what you are looking for? If yes, try docker exec -it bash -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160617/e14dc675/attachment.html From jpkroehling at redhat.com Fri Jun 17 09:55:39 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Fri, 17 Jun 2016 15:55:39 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> <731329596.7332854.1466169953099.JavaMail.zimbra@redhat.com> Message-ID: <22803a1a-d83c-5a41-ffe3-4b5b9f2672f9@redhat.com> On 17.06.2016 15:42, Heiko W.Rupp wrote: > I think you can do all that -- see > https://goldmann.pl/blog/2014/07/23/customizing-the-configuration-of-the-wildfly-docker-image/#_summary Confirm with Marek if that's still the way to go. This is almost 2 years old already :) For some Keycloak operations, I know that the offline mode works fine. It probably works for our case as well. - Juca. From hrupp at redhat.com Fri Jun 17 10:03:36 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Fri, 17 Jun 2016 16:03:36 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> <731329596.7332854.1466169953099.JavaMail.zimbra@redhat.com> Message-ID: <79A6B6EF-DEF2-40E3-8328-512D557E5A17@redhat.com> On 17 Jun 2016, at 15:48, Anton wrote: > Perhaps having bash access to the running docker container is what you are > looking for? If yes, try > docker exec -it bash I know. You mean accessing the container this way, making the modifications and then persisting those in the r/w layer and afterwards calling the above generated container without a cmd and using it as defined in the Dockerfile? From jdoyle at redhat.com Fri Jun 17 10:59:53 2016 From: jdoyle at redhat.com (John Doyle) Date: Fri, 17 Jun 2016 10:59:53 -0400 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> Message-ID: On Fri, Jun 17, 2016 at 6:37 AM, Heiko W.Rupp wrote: > Hey, > > I was able to make some progress with Dockerizing Hawkular-services > More technical details below > > As it is relatively hard (not impossible) to do stuff like adding a user > inside a (immutable) docker container or to edit standalone.xml to > enable the agent, we need to decide how we add the (default) user > to hawkular docker container and also if/how to enable the embedded > agent. > > Also as we more understand hawkular-services as one package, > we should perhaps figure out if we really need the flexibility to > modify standalone.xml on the fly with all our snippets and templates > or if we create a 'hardcoded' one that can be used for the process > going forward. Very few layered products have created their own dedicated standalone.xml. To be honest I don't understand the reluctance. Configuration changes in maintenance releases are rejected unless absolutely needed for security purposes, so breakage is very unlikely. > At the moment wildfly10 is our base and will be for a longer period, > so the server-supplied standalone.xml will not change anyway. > > > Anyway my Poc is at > https://github.com/pilhuhn/hawkular-services/tree/dockerize-all-the-things > > There are 3 routes that I went (basically refining the process) > > (If you want to run any you first need to > $ mkdir -p /tmp/opt/hawkular > as this is where the docker run commands expect the data for now > > To get a 'working server' you need to "mvn install -Pdev first" > > 1) dist/ creating a Dockerfile by hand and manually running docker build > Dockerfile > and then docker-compose to run a container from this image linked to a > C* 3.5 one. > Base image is the jboss/base-jdk:8 one and the Dockerfile basically > overlays the > whole hawkular-services distribution on top > > You can run this with $ docker-compose up > > > 2) docker-dist/ here maven creates the Dockerfile on the fly and feeds > it to Docker. > This uses the fabric8.io docker plugin from Roland Huss. > Again it uses the same base image + overlay as 1). The container tag is > derived from the > maven properties. > To build and run you can go into the directory and then > > $ mvn docker:build > $ mvn docker:start > > 3) docker-dist2/ Similar to 2) this uses the mvn docker plugin, but this > time is uses > jboss/wildfly:10.0.0.Final as the base image. Unfortunately it still > overlays the whole > wildfly from us, but we should be able to filter that out. > The good thing is though that the image is already much smaller as in 2) > > To build and run the same process as 2) applies > > * > The next step is now to figure out how to only apply our changes and not > to > supply the base wildfly into the conatiner. I certainly need help from > someone > with maven-fu :) > > But while the current state is not optimal it shows that this is very > much doable > and we should proceed. > > Heiko > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev From vnguyen at redhat.com Fri Jun 17 11:45:14 2016 From: vnguyen at redhat.com (Viet Nguyen) Date: Fri, 17 Jun 2016 11:45:14 -0400 (EDT) Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> Message-ID: <1888456498.36637952.1466178314610.JavaMail.zimbra@redhat.com> Heiko, How about using regular Dockerfile instead of the maven plugin? you can 'burn' changes (adding users, configuring standalone.xml...) into the final image? https://github.com/RedHatQE/hawkular-docker Viet ----- Original Message ----- From: "Heiko W.Rupp" To: "Discussions around Hawkular development" Sent: Friday, June 17, 2016 5:50:57 AM Subject: Re: [Hawkular-dev] Some progress on Dockerization of Hawkular-services On 17 Jun 2016, at 12:37, Heiko W.Rupp wrote: > The next step is now to figure out how to only apply our changes and > not > to > supply the base wildfly into the conatiner. I certainly need help from > someone > with maven-fu :) I have this now in the docker-dist3 module https://github.com/pilhuhn/hawkular-services/tree/dockerize-all-the-things/docker-dist3 As before: $ mvn -Pdev install $ mvn cd docker-dist3 $ mkdir -p /tmp/opt/hawkular $ mvn docker:build $ mvn docker:start == Http2/ssl Dockerizing of services could now also allow to also add the correct alpn jar to the container to enable http2, as the underlying JVM is known and constant (until the underlying base image changes) $ docker run -it hawkular/hawkular-services-mvn3 bash [root at 275fc8b436f7 jboss]# java -version openjdk version "1.8.0_91" OpenJDK Runtime Environment (build 1.8.0_91-b14) OpenJDK 64-Bit Server VM (build 25.91-b14, mixed mode) So according to http://www.eclipse.org/jetty/documentation/current/alpn-chapter.html#alpn-versions for 1.8.0u91 alpn 8.1.7.v20160121 is required, which can be retrieved from http://mvnrepository.com/artifact/org.mortbay.jetty.alpn/alpn-boot There is a guide for further work on this http://undertow.io/blog/2015/03/26/HTTP2-In-Wildfly.html It requires SSL though and also away to configure this. _______________________________________________ hawkular-dev mailing list hawkular-dev at lists.jboss.org https://lists.jboss.org/mailman/listinfo/hawkular-dev From kurrent93 at gmail.com Fri Jun 17 11:53:37 2016 From: kurrent93 at gmail.com (Anton) Date: Fri, 17 Jun 2016 17:53:37 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: <1888456498.36637952.1466178314610.JavaMail.zimbra@redhat.com> References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> <1888456498.36637952.1466178314610.JavaMail.zimbra@redhat.com> Message-ID: On Fri, Jun 17, 2016 at 5:45 PM, Viet Nguyen wrote: > How about using regular Dockerfile I think the problem with this is you need to rebuild each time you want to add a new user. What about externalizing the standalone? So that it is outside of the docker image. Or have a env var with username/password? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160617/3a0b8519/attachment.html From jpkroehling at redhat.com Fri Jun 17 12:00:33 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Fri, 17 Jun 2016 18:00:33 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> <1888456498.36637952.1466178314610.JavaMail.zimbra@redhat.com> Message-ID: On 17.06.2016 17:53, Anton wrote: > On Fri, Jun 17, 2016 at 5:45 PM, Viet Nguyen > wrote: > > How about using regular Dockerfile > > > I think the problem with this is you need to rebuild each time you want > to add a new user. On a production setup, users should not be managed via text files. Ideally, it should come from something like Keycloak or a backing LDAP. So, it would be a one time configuration. Also, it should be possible for consumers to extend our image and change the configuration files to their needs. > What about externalizing the standalone? So that it is outside of the > docker image. > Or have a env var with username/password? No. That's not the proper way to go with this. - Juca. From hrupp at redhat.com Fri Jun 17 12:02:26 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Fri, 17 Jun 2016 18:02:26 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: <1888456498.36637952.1466178314610.JavaMail.zimbra@redhat.com> References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> <1888456498.36637952.1466178314610.JavaMail.zimbra@redhat.com> Message-ID: Hey Viet, On 17 Jun 2016, at 17:45, Viet Nguyen wrote: > How about using regular Dockerfile instead of the maven plugin? you > can 'burn' changes (adding users, configuring standalone.xml...) into > the final image? Yes I know. I did that in my first step - see older email. The maven plugin has the beauty to me that it is all automated and repeatable and consumes the maven properties we have. Your Dockerfile certainly looks good as well. In the past we had one in hawkular/hawkular that always required editing after we released a new Hawkular version, which is not sustainable. The changes of you mention above are some that most probably need to be deferred to container instantiation time unless we build a dev-container/-image. Heiko From hrupp at redhat.com Fri Jun 17 12:10:04 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Fri, 17 Jun 2016 18:10:04 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> <1888456498.36637952.1466178314610.JavaMail.zimbra@redhat.com> Message-ID: <2D506BAE-588A-4827-92C1-45ED445DE016@redhat.com> I forgot: On 17 Jun 2016, at 18:02, Heiko W.Rupp wrote: > The maven plugin has the beauty to me that it is all automated > and repeatable and consumes the maven properties we have. I am now layering on top of a wf10 container. The maven plugin also allows to select me what to put into the container, as we certainly don't need everything. Of course we could create a tar/zip via the standard assembly and then put that in the Dockerfile via ADD instruction. In this case it just happens in one go. From theute at redhat.com Fri Jun 17 12:52:54 2016 From: theute at redhat.com (Thomas Heute) Date: Fri, 17 Jun 2016 18:52:54 +0200 Subject: [Hawkular-dev] Some progress on Dockerization of Hawkular-services In-Reply-To: References: <4040A180-9C2B-4235-A812-C651D2453010@redhat.com> Message-ID: On Fri, Jun 17, 2016 at 4:59 PM, John Doyle wrote: > On Fri, Jun 17, 2016 at 6:37 AM, Heiko W.Rupp wrote: > > Hey, > > > > I was able to make some progress with Dockerizing Hawkular-services > > More technical details below > > > > As it is relatively hard (not impossible) to do stuff like adding a user > > inside a (immutable) docker container or to edit standalone.xml to > > enable the agent, we need to decide how we add the (default) user > > to hawkular docker container and also if/how to enable the embedded > > agent. > > > > Also as we more understand hawkular-services as one package, > > we should perhaps figure out if we really need the flexibility to > > modify standalone.xml on the fly with all our snippets and templates > > or if we create a 'hardcoded' one that can be used for the process > > going forward. > > Very few layered products have created their own dedicated > standalone.xml. To be honest I don't understand the reluctance. > Configuration changes in maintenance releases are rejected unless > absolutely needed for security purposes, so breakage is very unlikely. > > +1 -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160617/2748a7a9/attachment.html From mazz at redhat.com Fri Jun 17 17:12:08 2016 From: mazz at redhat.com (John Mazzitelli) Date: Fri, 17 Jun 2016 17:12:08 -0400 (EDT) Subject: [Hawkular-dev] services build has a problem In-Reply-To: <1546729534.7441309.1466197515118.JavaMail.zimbra@redhat.com> Message-ID: <522372856.7442006.1466197928223.JavaMail.zimbra@redhat.com> This recently changed and doesn't work like it did before. I can't figure out what's wrong. The -Pdev build isn't working correctly (and neither is the non-dev build). When you build without -Pdev, the agent should be disabled by default. But it is not, and you will get agent errors on startup. When you build with -Pdev, the agent should be enabled and with the hawkualr.rest.user/password properties set inside standalone.xml. But they are not, and you again get agent startup errors. This used to work a few days ago. The .xsl that used to tweak the standalone.xml doesn't seem to be doing what it was supposed to do. Look here: https://github.com/hawkular/hawkular-services/blob/master/feature-pack/src/main/xsl/configuration/standalone/hawkular-services-template.xsl#L30-L51 See where it sets the system properties to control the agent enabled flag and the credentials? This isn't doing anyting that I can see because the distro doesn't have any system proeprties in standalone.xml, but this used to work. We'd get those elements in standalone.xml. I can't figure out what changed. Hoping someone knows the deal and can put this back. From mazz at redhat.com Fri Jun 17 17:34:40 2016 From: mazz at redhat.com (John Mazzitelli) Date: Fri, 17 Jun 2016 17:34:40 -0400 (EDT) Subject: [Hawkular-dev] services build has a problem In-Reply-To: <522372856.7442006.1466197928223.JavaMail.zimbra@redhat.com> References: <522372856.7442006.1466197928223.JavaMail.zimbra@redhat.com> Message-ID: <669383949.7443788.1466199280602.JavaMail.zimbra@redhat.com> For the record, I just checked out hawkular-services tag 0.0.2.Final, built the dist, and I see this in standalone.xml now: which means all of this will work. But now, in master, I don't get any section at all. ----- Original Message ----- > This recently changed and doesn't work like it did before. I can't figure out > what's wrong. > > The -Pdev build isn't working correctly (and neither is the non-dev build). > > When you build without -Pdev, the agent should be disabled by default. But it > is not, and you will get agent errors on startup. > > When you build with -Pdev, the agent should be enabled and with the > hawkualr.rest.user/password properties set inside standalone.xml. But they > are not, and you again get agent startup errors. > > This used to work a few days ago. > > The .xsl that used to tweak the standalone.xml doesn't seem to be doing what > it was supposed to do. Look here: > > https://github.com/hawkular/hawkular-services/blob/master/feature-pack/src/main/xsl/configuration/standalone/hawkular-services-template.xsl#L30-L51 > > See where it sets the system properties to control the agent enabled flag and > the credentials? This isn't doing anyting that I can see because the distro > doesn't have any system proeprties in standalone.xml, but this used to work. > We'd get those elements in standalone.xml. > > I can't figure out what changed. Hoping someone knows the deal and can put > this back. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From mazz at redhat.com Fri Jun 17 17:42:48 2016 From: mazz at redhat.com (John Mazzitelli) Date: Fri, 17 Jun 2016 17:42:48 -0400 (EDT) Subject: [Hawkular-dev] services build has a problem In-Reply-To: <669383949.7443788.1466199280602.JavaMail.zimbra@redhat.com> References: <522372856.7442006.1466197928223.JavaMail.zimbra@redhat.com> <669383949.7443788.1466199280602.JavaMail.zimbra@redhat.com> Message-ID: <1373804706.7446398.1466199768883.JavaMail.zimbra@redhat.com> I wrote this up here: https://issues.jboss.org/browse/HAWKULAR-1090 ----- Original Message ----- > For the record, I just checked out hawkular-services tag 0.0.2.Final, built > the dist, and I see this in standalone.xml now: > > > value="${hawkular.backend:embedded_cassandra}"/> > value="${hawkular.agent.enabled:false}"/> > > > which means all of this will work. > > But now, in master, I don't get any section at all. > > ----- Original Message ----- > > This recently changed and doesn't work like it did before. I can't figure > > out > > what's wrong. > > > > The -Pdev build isn't working correctly (and neither is the non-dev build). > > > > When you build without -Pdev, the agent should be disabled by default. But > > it > > is not, and you will get agent errors on startup. > > > > When you build with -Pdev, the agent should be enabled and with the > > hawkualr.rest.user/password properties set inside standalone.xml. But they > > are not, and you again get agent startup errors. > > > > This used to work a few days ago. > > > > The .xsl that used to tweak the standalone.xml doesn't seem to be doing > > what > > it was supposed to do. Look here: > > > > https://github.com/hawkular/hawkular-services/blob/master/feature-pack/src/main/xsl/configuration/standalone/hawkular-services-template.xsl#L30-L51 > > > > See where it sets the system properties to control the agent enabled flag > > and > > the credentials? This isn't doing anyting that I can see because the distro > > doesn't have any system proeprties in standalone.xml, but this used to > > work. > > We'd get those elements in standalone.xml. > > > > I can't figure out what changed. Hoping someone knows the deal and can put > > this back. > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From jpkroehling at redhat.com Mon Jun 20 02:33:59 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Mon, 20 Jun 2016 08:33:59 +0200 Subject: [Hawkular-dev] services build has a problem In-Reply-To: <669383949.7443788.1466199280602.JavaMail.zimbra@redhat.com> References: <522372856.7442006.1466197928223.JavaMail.zimbra@redhat.com> <669383949.7443788.1466199280602.JavaMail.zimbra@redhat.com> Message-ID: <783cf72e-d7df-e683-e973-cc13c8c37d3b@redhat.com> On 17.06.2016 23:34, John Mazzitelli wrote: > For the record, I just checked out hawkular-services tag 0.0.2.Final, built the dist, and I see this in standalone.xml now: > > > > > > > which means all of this will work. > > But now, in master, I don't get any section at all. This is probably my fault: I removed the backend property from the template on the nest when I removed embedded Cassandra. I suppose that we have no system properties on Nest now, which makes the XSL fail. Once this is fixed, would you mind adding a simple integration test for the agent on h-services? - Juca. From jpkroehling at redhat.com Mon Jun 20 04:43:48 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Mon, 20 Jun 2016 10:43:48 +0200 Subject: [Hawkular-dev] Prepare for Hawkular Services 0.0.3.Final Message-ID: <55f55f53-32be-985a-1f60-77c6461806e2@redhat.com> Team, We'll have a release of Hawkular Services tomorrow, for version 0.0.3.Final. This release will include the removal of embedded Cassandra. There should not be anything required for individual components, but it would be good if you'd test the current Hawkular Services master to see if your component is working as expected. If there are version changes required, send a PR by EOD today. - Juca. From lkrejci at redhat.com Mon Jun 20 07:03:45 2016 From: lkrejci at redhat.com (Lukas Krejci) Date: Mon, 20 Jun 2016 13:03:45 +0200 Subject: [Hawkular-dev] Hawkular Commons 0.7.3.Final released In-Reply-To: References: <5226b379-6967-35ac-55d7-91afff0e0ecf@redhat.com> Message-ID: <2190855.FqJ3qYG5Xq@localhost.localdomain> On Friday, June 10, 2016 10:24:33 AM Stefan Negrea wrote: > Hello, > > Thanks for the clarifications and the PR for Metrics. I looked at the code > and module they are really minimal, nice work! > > In the long run Metrics would benefit from adopting it however at this time > the project is not ready to get additional external dependencies. I closed > the PR for now, we will reopen the PR once we are ready to adopt the filter. > With the pending PR https://github.com/hawkular/hawkular-commons/pull/77 the tenant filter introduces no new dependency compared to what metrics is already depending on. I assume that would remove all the barriers for you to adopt a common way of handling tenants in all Hawkular components? > > Thank you, > Stefan Negrea > > Software Engineer > > > On Fri, Jun 10, 2016 at 1:36 AM, Juraci Paix?o Kr?hling < > > jpkroehling at redhat.com> wrote: > > On 10.06.2016 05:07, Stefan Negrea wrote: > >> Can you please give more details about the proposed changes to use the > >> Commons filter in other projects? What dependencies need to be > >> introduced? Where is the filter located (module, code)? > > > > The tenant filter is a JAX-RS filter and the dependency is defined as > > org.hawkular.commons:hawkular-tenant-jaxrs-filter [1]. It's a "pure" Java > > EE module, depending on nothing else. > > > > All you need to do is to have your WAR module depending on this filter > > module and the filter will be applied automatically to all JAX-RS > > endpoints > > in your application. If you have an endpoint or method that you don't want > > to protect, use the `@TenantRequired(false)` annotation. > > > > 1 - https://git.io/vosci > > > > Also, what are the implications of not using the filter from Commons? > > > > > > If you don't use the filter, you risk having a different behavior when > > comparing to other modules. For instance, you might return JSON when no > > JSON is expected (or vice-versa), or you might have a slightly different > > semantic than the current agreement, ... > > > > - Juca. -- Lukas Krejci From miburman at redhat.com Mon Jun 20 09:46:21 2016 From: miburman at redhat.com (Michael Burman) Date: Mon, 20 Jun 2016 09:46:21 -0400 (EDT) Subject: [Hawkular-dev] Performance testing (and PR #519) In-Reply-To: <693032929.282283.1466429864497.JavaMail.zimbra@redhat.com> Message-ID: <5850996.286774.1466430381779.JavaMail.zimbra@redhat.com> Hi, So the discussion on #hawkular pointed out that our current metrics performance testing is seeing a regression in the performance, after the merging of PR #519. I found this odd as I had done a lot of testing for this feature, including multiple runs of JMH (OpenJDK's Java benchmarking tool) and using a profiler to witness reduced CPU usage as well as reduced GC activity. The issue surrounds over RxJava's concatWith vs. mergeWith. Now, concatWith creates internal Queues and other stuff to keep track of the stuff, whereas mergeWith does not. So, Filip's tools say mergeWith is slower, my intuition/profiler and benchmarking says otherwise. Odd situation, but there's a small difference in testing methologies here. I've done testing against hawkular-core-service (that is, only the internal handling), while Filip uses the whole Wildfly in his testing. Although the performance degredation is quite severe with JAX-RS involved, it shouldn't cause different end results. The test results for my runs with JMH are here (with first the end results and then individual runs and statistics). https://gist.github.com/burmanm/e3b1ab0e67bcae189072718d39b66b6c The test that is run here is: https://github.com/hawkular/hawkular-metrics/blob/master/integration-tests/jmh-benchmark/src/main/java/org/hawkular/metrics/benchmark/jmh/InsertBenchmark.java#L141 Which mimics the behavior in which multiple concurrent senders are sending 1 metric in each call. With our backend, there's not a huge difference if we send everything in one request or single requests (this is more JAX-RS issue). The tests are using both 1 datapoint per 1 metric and 10 datapoints per 1 metric. The performance is returned as inserted metrics per second (so multiply by 10 the second result -> 9012 metrics / second -> 90120 datapoints / second). Let the flaming begin.. or something ;) Other notes: There are other important optimization strategies involved with the 1 metric 1 datapoint scenario. First one is changing the behavior of indexUpdates. Removing unnecessary index updates doubles the performance from 13k metrics to 26k metrics per second. Second optimization strategy with single Cassandra node deployments is to force datapoint writing to use batch statements (with different partitions - which isn't normally recommended), that increases the performance from the 26k to >60k. I'm trying to find better solution for the latter case, but haven't so far found one. - Micke From gbrown at redhat.com Mon Jun 20 11:13:32 2016 From: gbrown at redhat.com (Gary Brown) Date: Mon, 20 Jun 2016 11:13:32 -0400 (EDT) Subject: [Hawkular-dev] PR to review Message-ID: <1285148918.258393.1466435612343.JavaMail.zimbra@redhat.com> Hi https://github.com/hawkular/hawkular-apm/pull/449 Any takers? Regards Gary From mazz at redhat.com Mon Jun 20 12:02:44 2016 From: mazz at redhat.com (John Mazzitelli) Date: Mon, 20 Jun 2016 12:02:44 -0400 (EDT) Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <237696699.428385.1466438408497.JavaMail.zimbra@redhat.com> Message-ID: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> I just submitted a new PR for hawkular services: https://github.com/hawkular/hawkular-services/pull/22 This re-introduces the ability to build Hawkular Services with embedded Cassandra if you want. This will ONLY embed Cassandra IF you build with the special Maven profile -Pembeddedc. If you never build with that profile, Hawkular Services will build as it does now (that is, requires you to install and start your own Cassandra separately). So this will allow developers to continue doing what they've been doing (that is, no need to run a standalone C*) if they want. Again, the default build is NOT to embed Cassandra. You must explicitly tell Maven you want to embed C* via -Pembeddedc to get this feature. From jshaughn at redhat.com Mon Jun 20 12:08:46 2016 From: jshaughn at redhat.com (Jay Shaughnessy) Date: Mon, 20 Jun 2016 12:08:46 -0400 Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> Message-ID: <36b04807-05cd-6dcd-0019-ed0ad25e691d@redhat.com> On 6/20/2016 12:02 PM, John Mazzitelli wrote: > I just submitted a new PR for hawkular services: > > https://github.com/hawkular/hawkular-services/pull/22 > > This re-introduces the ability to build Hawkular Services with embedded Cassandra if you want. > > This will ONLY embed Cassandra IF you build with the special Maven profile -Pembeddedc. I'm +1 on this option and external c* being the default. But -1 on that profile name, can you make it something obvious like -Pembedded-cassandra > > If you never build with that profile, Hawkular Services will build as it does now (that is, requires you to install and start your own Cassandra separately). > > So this will allow developers to continue doing what they've been doing (that is, no need to run a standalone C*) if they want. > > Again, the default build is NOT to embed Cassandra. You must explicitly tell Maven you want to embed C* via -Pembeddedc to get this feature. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From mazz at redhat.com Mon Jun 20 12:17:59 2016 From: mazz at redhat.com (John Mazzitelli) Date: Mon, 20 Jun 2016 12:17:59 -0400 (EDT) Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <36b04807-05cd-6dcd-0019-ed0ad25e691d@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <36b04807-05cd-6dcd-0019-ed0ad25e691d@redhat.com> Message-ID: <996941243.431501.1466439479134.JavaMail.zimbra@redhat.com> > I'm +1 on this option and external c* being the default. But -1 on that > profile name, can you make it something obvious like -Pembedded-cassandra I tried limiting the number of characters I'm gonna have to type every time I build this now :) How about something smaller than "embedded-cassandra"?? :) From fbrychta at redhat.com Mon Jun 20 12:40:04 2016 From: fbrychta at redhat.com (Filip Brychta) Date: Mon, 20 Jun 2016 12:40:04 -0400 (EDT) Subject: [Hawkular-dev] Performance testing (and PR #519) In-Reply-To: <5850996.286774.1466430381779.JavaMail.zimbra@redhat.com> References: <5850996.286774.1466430381779.JavaMail.zimbra@redhat.com> Message-ID: <1568476701.143562.1466440804581.JavaMail.zimbra@redhat.com> Because it's really odd I double checked that it's not caused by environment. I retested with build from commit 547b8a (last one before Use mergeWith instead of concat ) and the performance was up again. So the drop is really caused by "Use mergeWith instead of concat" commit. The performance drop is not visible when sending small msgs (1 datapoint per request) but I can see it for 10, 100, 500 datapoints per request. So the question is how is that possible. I checked following: - CPU usage is slightly lower after that commit - GC is not causing it because the full GC did not happened during the test run at all in both cases Filip ----- Original Message ----- > Hi, > > So the discussion on #hawkular pointed out that our current metrics > performance testing is seeing a regression in the performance, after the > merging of PR #519. I found this odd as I had done a lot of testing for this > feature, including multiple runs of JMH (OpenJDK's Java benchmarking tool) > and using a profiler to witness reduced CPU usage as well as reduced GC > activity. The issue surrounds over RxJava's concatWith vs. mergeWith. Now, > concatWith creates internal Queues and other stuff to keep track of the > stuff, whereas mergeWith does not. > > So, Filip's tools say mergeWith is slower, my intuition/profiler and > benchmarking says otherwise. Odd situation, but there's a small difference > in testing methologies here. I've done testing against hawkular-core-service > (that is, only the internal handling), while Filip uses the whole Wildfly in > his testing. Although the performance degredation is quite severe with > JAX-RS involved, it shouldn't cause different end results. > > The test results for my runs with JMH are here (with first the end results > and then individual runs and statistics). > > https://gist.github.com/burmanm/e3b1ab0e67bcae189072718d39b66b6c > > The test that is run here is: > > https://github.com/hawkular/hawkular-metrics/blob/master/integration-tests/jmh-benchmark/src/main/java/org/hawkular/metrics/benchmark/jmh/InsertBenchmark.java#L141 > > Which mimics the behavior in which multiple concurrent senders are sending 1 > metric in each call. With our backend, there's not a huge difference if we > send everything in one request or single requests (this is more JAX-RS > issue). The tests are using both 1 datapoint per 1 metric and 10 datapoints > per 1 metric. The performance is returned as inserted metrics per second (so > multiply by 10 the second result -> 9012 metrics / second -> 90120 > datapoints / second). > > Let the flaming begin.. or something ;) > > Other notes: > > There are other important optimization strategies involved with the 1 metric > 1 datapoint scenario. First one is changing the behavior of indexUpdates. > Removing unnecessary index updates doubles the performance from 13k metrics > to 26k metrics per second. Second optimization strategy with single > Cassandra node deployments is to force datapoint writing to use batch > statements (with different partitions - which isn't normally recommended), > that increases the performance from the 26k to >60k. I'm trying to find > better solution for the latter case, but haven't so far found one. > > - Micke > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From jshaughn at redhat.com Mon Jun 20 13:04:44 2016 From: jshaughn at redhat.com (Jay Shaughnessy) Date: Mon, 20 Jun 2016 13:04:44 -0400 Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <996941243.431501.1466439479134.JavaMail.zimbra@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <36b04807-05cd-6dcd-0019-ed0ad25e691d@redhat.com> <996941243.431501.1466439479134.JavaMail.zimbra@redhat.com> Message-ID: <7ddda959-187b-a667-d8df-8d28c49b8a5e@redhat.com> -Pmazz -Pembedded -Pdev-cassandra I dunno, leave it as -Pembeddedc if you like. On 6/20/2016 12:17 PM, John Mazzitelli wrote: >> I'm +1 on this option and external c* being the default. But -1 on that >> profile name, can you make it something obvious like -Pembedded-cassandra > I tried limiting the number of characters I'm gonna have to type every time I build this now :) > > How about something smaller than "embedded-cassandra"?? :) > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160620/09095a20/attachment.html From jpkroehling at redhat.com Mon Jun 20 15:57:34 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Mon, 20 Jun 2016 21:57:34 +0200 Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> Message-ID: <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> Mazz, I have nothing against your PR in particular, but I'm against this feature in principle: it's more code that we have to take care of for "development only". And as it's more code, it also means more bugs. Perhaps not now, but in a week or two (or once we have a change in the XML templates). To me, requiring the developer to install Cassandra is similar to requiring a developer to install MariaDB or PostgreSQL and that's acceptable, specially if we don't have to maintain code that is to be used only for development purposes. On a Fedora machine, Cassandra can be installed and started by: # dnf config-manager --add-repo=http://rpm.datastax.com/community # dnf install dsc30 # systemctl start cassandra ( plus, there might some required changes related to networking in /etc/cassandra/conf/cassandra.yaml ) That said, I suggest -Paio (all-in-one) for the profile name :) - Juca. On 20.06.2016 18:02, John Mazzitelli wrote: > I just submitted a new PR for hawkular services: > > https://github.com/hawkular/hawkular-services/pull/22 > > This re-introduces the ability to build Hawkular Services with embedded Cassandra if you want. > > This will ONLY embed Cassandra IF you build with the special Maven profile -Pembeddedc. > > If you never build with that profile, Hawkular Services will build as it does now (that is, requires you to install and start your own Cassandra separately). > > So this will allow developers to continue doing what they've been doing (that is, no need to run a standalone C*) if they want. > > Again, the default build is NOT to embed Cassandra. You must explicitly tell Maven you want to embed C* via -Pembeddedc to get this feature. > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From jsanda at redhat.com Mon Jun 20 16:04:44 2016 From: jsanda at redhat.com (John Sanda) Date: Mon, 20 Jun 2016 16:04:44 -0400 Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> Message-ID: <20D94F2C-7D4A-4A43-A3FD-089E05B5E44F@redhat.com> I know that there has been reluctance to using ccm, but that really should be part of the development environment. It can run on any platform that has python. You can easily manage single- or multi-node clusters that run locally. I walked Jay through it in less than 5 minutes and had him up and running with these simple steps: 1. pip install ccm 2. ccm create test -v 3.7 -n 1 ?nodes 3. Edit ~/.ccm/test/node1/conf/cassandra.yaml and set the start_rpc property to true (needed for inventory) 4. ccm stop 5. ccm start > On Jun 20, 2016, at 3:57 PM, Juraci Paix?o Kr?hling wrote: > > Mazz, > > I have nothing against your PR in particular, but I'm against this > feature in principle: it's more code that we have to take care of for > "development only". And as it's more code, it also means more bugs. > Perhaps not now, but in a week or two (or once we have a change in the > XML templates). > > To me, requiring the developer to install Cassandra is similar to > requiring a developer to install MariaDB or PostgreSQL and that's > acceptable, specially if we don't have to maintain code that is to be > used only for development purposes. > > On a Fedora machine, Cassandra can be installed and started by: > # dnf config-manager --add-repo=http://rpm.datastax.com/community > # dnf install dsc30 > # systemctl start cassandra > > ( plus, there might some required changes related to networking in > /etc/cassandra/conf/cassandra.yaml ) > > That said, I suggest -Paio (all-in-one) for the profile name :) > > - Juca. > > > On 20.06.2016 18:02, John Mazzitelli wrote: >> I just submitted a new PR for hawkular services: >> >> https://github.com/hawkular/hawkular-services/pull/22 >> >> This re-introduces the ability to build Hawkular Services with embedded Cassandra if you want. >> >> This will ONLY embed Cassandra IF you build with the special Maven profile -Pembeddedc. >> >> If you never build with that profile, Hawkular Services will build as it does now (that is, requires you to install and start your own Cassandra separately). >> >> So this will allow developers to continue doing what they've been doing (that is, no need to run a standalone C*) if they want. >> >> Again, the default build is NOT to embed Cassandra. You must explicitly tell Maven you want to embed C* via -Pembeddedc to get this feature. >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160620/0bebba38/attachment.html From mazz at redhat.com Mon Jun 20 16:43:10 2016 From: mazz at redhat.com (John Mazzitelli) Date: Mon, 20 Jun 2016 16:43:10 -0400 (EDT) Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <20D94F2C-7D4A-4A43-A3FD-089E05B5E44F@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> <20D94F2C-7D4A-4A43-A3FD-089E05B5E44F@redhat.com> Message-ID: <908219261.496660.1466455390802.JavaMail.zimbra@redhat.com> Honestly, I don't get it. We have a nice all-in-one way to run hawkular server. I don't want to have to spend even 5 minutes learning how great ccm is, or how to download/install/start C* on its own, when the feature exists that I can just build and run. We have a way to embed our datasource! That's awesome! Why are we afraid to use it or support it - even from just a dev or demo standpoint? BTW: We are still using embedded C* in our itests - so we are still in need to support it. Anyway, as I say, this is a completely separate, standalone maven profile. You never have to use it - you don't even need to know it exists. Just ignore it if you want. But for people who want it, its there. Win-win. As for the fact it is more code, I will see if I can get the pom to generate its own feature-branch xml file so we only have one. When that happens, there will be no real extra config to maintain. The only thing extra will be the use of this hawkular.embeddedc property - which really just mimics the hawkular.rest.url/password stuff. From mazz at redhat.com Mon Jun 20 17:39:04 2016 From: mazz at redhat.com (John Mazzitelli) Date: Mon, 20 Jun 2016 17:39:04 -0400 (EDT) Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <908219261.496660.1466455390802.JavaMail.zimbra@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> <20D94F2C-7D4A-4A43-A3FD-089E05B5E44F@redhat.com> <908219261.496660.1466455390802.JavaMail.zimbra@redhat.com> Message-ID: <2121668270.502749.1466458744099.JavaMail.zimbra@redhat.com> > As for the fact it is more code, I will see if I can get the pom to generate > its own feature-branch xml file so we only have one. When that happens, > there will be no real extra config to maintain. The only thing extra will be > the use of this hawkular.embeddedc property - which really just mimics the > hawkular.rest.url/password stuff. This is done. No more duplicated feature pack build xml files. Back to just having the one. From auszon3 at gmail.com Mon Jun 20 22:20:33 2016 From: auszon3 at gmail.com (Austin Kuo) Date: Tue, 21 Jun 2016 02:20:33 +0000 Subject: [Hawkular-dev] Sync with Inventory Message-ID: Hi all, I?m currently investigating how to sync with inventory server. Here?s the example scenario: Consider the following problem. A user creates version 1 of the app with two http servers, one listening on port 8080, the other on port 8181. In version 2, the http server listening on port 8181 is no longer needed. When the old version is stopped and the new version started, there will be just one http server listening. The application is not aware of the previous state. What should we do so that the second http server is removed from Inventory? Thanks in advance. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160621/563e5744/attachment.html From auszon3 at gmail.com Mon Jun 20 23:49:20 2016 From: auszon3 at gmail.com (Austin Kuo) Date: Tue, 21 Jun 2016 03:49:20 +0000 Subject: [Hawkular-dev] =?utf-8?q?Can=E2=80=99t_run_inventory_hawkular-ser?= =?utf-8?q?vice?= Message-ID: Hi all, I started a cassandra cluster with: > ccm create test -v 2.2.6 -n 1 -s && ccm start test and then I tried to start the service with: > ./dist/target/hawkular-services-dist-0.0.3.Final-SNAPSHOT/bin/standalone.sh And it showed the warning and I checked the sever status at localhost:8080. It said that inventory is unavailable. WARN [org.hawkular.inventory.cdi] (ServerService Thread Pool -- 69) HAWKINV003501: Inventory backend failed to initialize in an attempt 14 of 15 with message: Could not instantiate implementation: com.thinkaurelius.titan.diskstorage.cassandra.thrift.CassandraThriftStoreManager. Anyone who has encountered this? Thanks! -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160621/1a938782/attachment-0001.html From hrupp at redhat.com Tue Jun 21 02:33:52 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 21 Jun 2016 08:33:52 +0200 Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> Message-ID: On 20 Jun 2016, at 21:57, Juraci Paix?o Kr?hling wrote: > That said, I suggest -Paio (all-in-one) for the profile name :) Which reminds me that we (Hi Stefan :-) are working on an AIO download which then indeed includes embedded-Cassandra, hawkular-services and explorer UI. Perhaps that build could also satisfy that "C* for developers" need(?) -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht M?nchen HRB 153243 Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander From hrupp at redhat.com Tue Jun 21 02:55:35 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 21 Jun 2016 08:55:35 +0200 Subject: [Hawkular-dev] =?utf-8?q?Can=E2=80=99t_run_inventory_hawkular-ser?= =?utf-8?q?vice?= In-Reply-To: References: Message-ID: <4EDC857D-B790-4034-9CC8-671BD30229C0@redhat.com> Hi, On 21 Jun 2016, at 5:49, Austin Kuo wrote: > I started a cassandra cluster with: >> ccm create test -v 2.2.6 -n 1 -s && ccm start test I think you could use v 3.7 of Cassandra. > 15 with message: Could not instantiate implementation: > com.thinkaurelius.titan.diskstorage.cassandra.thrift.CassandraThriftStoreManager. You need to enable RPC either via setting the env variable of CASSANDRA_START_RPC to true or by editing cassandra.yml and setting it there: # Whether to start the thrift rpc server. start_rpc: true From tsegismo at redhat.com Tue Jun 21 03:54:01 2016 From: tsegismo at redhat.com (Thomas Segismont) Date: Tue, 21 Jun 2016 09:54:01 +0200 Subject: [Hawkular-dev] =?utf-8?q?Can=E2=80=99t_run_inventory_hawkular-ser?= =?utf-8?q?vice?= In-Reply-To: <4EDC857D-B790-4034-9CC8-671BD30229C0@redhat.com> References: <4EDC857D-B790-4034-9CC8-671BD30229C0@redhat.com> Message-ID: Le 21/06/2016 ? 08:55, Heiko W.Rupp a ?crit : > Hi, > > > On 21 Jun 2016, at 5:49, Austin Kuo wrote: > >> I started a cassandra cluster with: >>> ccm create test -v 2.2.6 -n 1 -s && ccm start test > > I think you could use v 3.7 of Cassandra. Correct. > >> 15 with message: Could not instantiate implementation: >> com.thinkaurelius.titan.diskstorage.cassandra.thrift.CassandraThriftStoreManager. > > You need to enable RPC > > either via setting the env variable of CASSANDRA_START_RPC to true > > or by editing cassandra.yml and setting it there: > > # Whether to start the thrift rpc server. > start_rpc: true Given your cluster is named "test", the file would be: ~/.ccm/test/node1/conf/cassandra.yaml > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -- Thomas Segismont JBoss ON Engineering Team From jpkroehling at redhat.com Tue Jun 21 04:07:29 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Tue, 21 Jun 2016 10:07:29 +0200 Subject: [Hawkular-dev] Hawkular Services 0.0.3.Final Message-ID: <3d093e72-9a2f-0b04-672d-101b8ff9ece6@redhat.com> Team, Hawkular Services 0.0.3.Final has just been released. This version includes Agent 0.19.0.Final and features the removal of the embedded Cassandra. You'll need a local installation of Cassandra running before you start the server. The distribution can be downloaded here: https://repository.jboss.org/nexus/service/local/repositories/releases/content/org/hawkular/services/hawkular-services-dist/0.0.3.Final/hawkular-services-dist-0.0.3.Final.zip As the previous distributions, the Agent has to be configured with an user. This can be accomplished by: - Adding an user via bin/add-user.sh like: ./bin/add-user.sh \ -a \ -u \ -p \ -g read-write,read-only - Changing the Agent's credential on standalone.xml to the credentials from the previous step or by passing hawkular.rest.user / hawkular.rest.password as system properties (-Dhawkular.rest.user=jdoe) Known issue: https://issues.jboss.org/browse/HWKINVENT-186 - Juca. From hrupp at redhat.com Tue Jun 21 06:31:15 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 21 Jun 2016 12:31:15 +0200 Subject: [Hawkular-dev] Hawkular Services 0.0.3.Final In-Reply-To: <3d093e72-9a2f-0b04-672d-101b8ff9ece6@redhat.com> References: <3d093e72-9a2f-0b04-672d-101b8ff9ece6@redhat.com> Message-ID: <4A0965B1-3972-4EEE-ADA3-A9C6687EF39E@redhat.com> On 21 Jun 2016, at 10:07, Juraci Paix?o Kr?hling wrote: > Hawkular Services 0.0.3.Final has just been released. Great! I love these weekly releases. -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht M?nchen HRB 153243 Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander From hrupp at redhat.com Tue Jun 21 06:31:44 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 21 Jun 2016 12:31:44 +0200 Subject: [Hawkular-dev] Want to try hawkular-services via Docker? Message-ID: <27E77FC8-F395-4AF8-B53C-F83A2D9C4359@redhat.com> If you want to give it a try you can save the following into a file docker-compose.yml and then run docker-compose up hawkular This image has the -Pdev user jdoe/password. hawkular: image: "pilhuhn/hawkular-services:latest" ports: - "8080:8080" - "8443:8443" - "9990:9990" volumes: - /tmp/opt/hawkular/data:/opt/data links: - myCassandra environment: - HAWKULAR_BACKEND=remote - CASSANDRA_NODES=myCassandra myCassandra: image: cassandra:3.7 environment: - CASSANDRA_START_RPC=true volumes: - /tmp/opt/hawkular/cassandra:/var/lib/cassandra -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht M?nchen HRB 153243 Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander From gbrown at redhat.com Tue Jun 21 07:00:00 2016 From: gbrown at redhat.com (Gary Brown) Date: Tue, 21 Jun 2016 07:00:00 -0400 (EDT) Subject: [Hawkular-dev] PR to be reviewed In-Reply-To: <1316234036.453072.1466506629403.JavaMail.zimbra@redhat.com> Message-ID: <927579148.453236.1466506800676.JavaMail.zimbra@redhat.com> https://github.com/hawkular/hawkular-apm/pull/454 https://issues.jboss.org/browse/HWKAPM-484 Consolidation of how processing of bulk and individual events are handled. Regards Gary From lkrejci at redhat.com Tue Jun 21 07:55:04 2016 From: lkrejci at redhat.com (Lukas Krejci) Date: Tue, 21 Jun 2016 13:55:04 +0200 Subject: [Hawkular-dev] Sync with Inventory In-Reply-To: References: Message-ID: <2103173.GQyceoZSXW@localhost.localdomain> Hi Austin, Inventory offers a /hawkular/inventory/sync endpoint that is used to synchronize the "world view" of feeds (feed being something that pushes data into inventory). You said though that a "user creates" the resources, so I am not sure if /sync would be applicable to your scenario. Would you please elaborate more on where in the inventory hierarchy you create your resources and how? I.e. are you using some sort of feed akin to Hawkular's Wildfly Agent or are you just creating your resources "manually" under environments? On Tuesday, June 21, 2016 02:20:33 AM Austin Kuo wrote: > Hi all, > > I?m currently investigating how to sync with inventory server. > Here?s the example scenario: > Consider the following problem. A user creates version 1 of the app with > two http servers, one listening on port 8080, the other on port 8181. In > version 2, the http server listening on port 8181 is no longer needed. > When the old version is stopped and the new version started, there will be > just one http server listening. The application is not aware of the > previous state. What should we do so that the second http server is removed > from Inventory? > > Thanks in advance. -- Lukas Krejci From mazz at redhat.com Tue Jun 21 08:03:34 2016 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 21 Jun 2016 08:03:34 -0400 (EDT) Subject: [Hawkular-dev] =?utf-8?q?Can=E2=80=99t_run_inventory_hawkular-ser?= =?utf-8?q?vice?= In-Reply-To: References: <4EDC857D-B790-4034-9CC8-671BD30229C0@redhat.com> Message-ID: <687093973.751320.1466510614146.JavaMail.zimbra@redhat.com> Why would we ever want to provide a hawkular-services build that includes Embedded c*? It's so easy to install and run an external cassandra. :-) > Le 21/06/2016 ? 08:55, Heiko W.Rupp a ?crit : > > Hi, > > > > > > On 21 Jun 2016, at 5:49, Austin Kuo wrote: > > > >> I started a cassandra cluster with: > >>> ccm create test -v 2.2.6 -n 1 -s && ccm start test > > > > I think you could use v 3.7 of Cassandra. > > Correct. > > > > >> 15 with message: Could not instantiate implementation: > >> com.thinkaurelius.titan.diskstorage.cassandra.thrift.CassandraThriftStoreManager. > > > > You need to enable RPC > > > > either via setting the env variable of CASSANDRA_START_RPC to true > > > > or by editing cassandra.yml and setting it there: > > > > # Whether to start the thrift rpc server. > > start_rpc: true > > Given your cluster is named "test", the file would be: > ~/.ccm/test/node1/conf/cassandra.yaml From mazz at redhat.com Tue Jun 21 08:14:19 2016 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 21 Jun 2016 08:14:19 -0400 (EDT) Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> Message-ID: <1165588036.753000.1466511259705.JavaMail.zimbra@redhat.com> ----- Original Message ----- > On 20 Jun 2016, at 21:57, Juraci Paix?o Kr?hling wrote: > > > That said, I suggest -Paio (all-in-one) for the profile name :) > > Which reminds me that we (Hi Stefan :-) are working on an AIO > download which then indeed includes embedded-Cassandra, > hawkular-services and explorer UI. > Perhaps that build could also satisfy that "C* for developers" need(?) > Which tells me we probably shouldn't call this maven profile "aio" since it may be confused with that hawkular build (i.e. it really isn't all in one because it won't have that explorer UI for one thing). This maven profile only includes embedded C* and is part of the hawkular-services repo, not the hawkular repo. And as we just saw with Austin's timely post, it is clear to me that we need to provide this - let's make it as easy as possible for people to start doing development on Hawkular. Why put more roadblocks in their way when we don't need to? It also makes it easier on people like me who don't want to deal with it when I don't have to. :) From hrupp at redhat.com Tue Jun 21 08:45:31 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 21 Jun 2016 14:45:31 +0200 Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <1165588036.753000.1466511259705.JavaMail.zimbra@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> <1165588036.753000.1466511259705.JavaMail.zimbra@redhat.com> Message-ID: <5FC51A42-2CF9-40D9-9840-96B707FD8999@redhat.com> On 21 Jun 2016, at 14:14, John Mazzitelli wrote: > need to provide this - let's make it as easy as possible for people to > start doing development on Hawkular. Why put more roadblocks in their > way when we don't need to? It also makes it easier on people like me > who don't want to deal with it when I don't have to. :) For those just "consuming" it, $ docker-compose docker-compose.yml from attached file could be even easier :) -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht M?nchen HRB 153243 Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: docker-compose.yml Url: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160621/c495d469/attachment.ksh From mazz at redhat.com Tue Jun 21 09:20:52 2016 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 21 Jun 2016 09:20:52 -0400 (EDT) Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <5FC51A42-2CF9-40D9-9840-96B707FD8999@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> <1165588036.753000.1466511259705.JavaMail.zimbra@redhat.com> <5FC51A42-2CF9-40D9-9840-96B707FD8999@redhat.com> Message-ID: <1966818630.772757.1466515252153.JavaMail.zimbra@redhat.com> > On 21 Jun 2016, at 14:14, John Mazzitelli wrote: > > need to provide this - let's make it as easy as possible for people to > > start doing development on Hawkular. Why put more roadblocks in their > > way when we don't need to? It also makes it easier on people like me > > who don't want to deal with it when I don't have to. :) > > For those just "consuming" it, > > $ docker-compose docker-compose.yml > from attached file could be even easier :) Is the file system mounted somewhere locally so its easy to read or tail the logs? If hawkular-services can be built like this and give me everything: 1. mvn -Pdocker clean install 2. docker run ./target/hawkular-services-docker (or whatever the command is) 3. ...See the logs on the console and be able to read the log file as if its on a local mount point... Then that's good enough for me. Of course, that would probably be more code to have to maintain, so that's bad :) From mazz at redhat.com Tue Jun 21 09:23:31 2016 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 21 Jun 2016 09:23:31 -0400 (EDT) Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <1966818630.772757.1466515252153.JavaMail.zimbra@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> <1165588036.753000.1466511259705.JavaMail.zimbra@redhat.com> <5FC51A42-2CF9-40D9-9840-96B707FD8999@redhat.com> <1966818630.772757.1466515252153.JavaMail.zimbra@redhat.com> Message-ID: <1777179132.773415.1466515411147.JavaMail.zimbra@redhat.com> I guess I should also ask - how long does it take to build that docker container? A minute? Or a half-hour? ----- Original Message ----- > > On 21 Jun 2016, at 14:14, John Mazzitelli wrote: > > > need to provide this - let's make it as easy as possible for people to > > > start doing development on Hawkular. Why put more roadblocks in their > > > way when we don't need to? It also makes it easier on people like me > > > who don't want to deal with it when I don't have to. :) > > > > For those just "consuming" it, > > > > $ docker-compose docker-compose.yml > > from attached file could be even easier :) > > Is the file system mounted somewhere locally so its easy to read or tail the > logs? > > If hawkular-services can be built like this and give me everything: > > 1. mvn -Pdocker clean install > 2. docker run ./target/hawkular-services-docker (or whatever the command is) > 3. ...See the logs on the console and be able to read the log file as if its > on a local mount point... > > Then that's good enough for me. Of course, that would probably be more code > to have to maintain, so that's bad :) > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From hrupp at redhat.com Tue Jun 21 09:30:35 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 21 Jun 2016 15:30:35 +0200 Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <1777179132.773415.1466515411147.JavaMail.zimbra@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> <1165588036.753000.1466511259705.JavaMail.zimbra@redhat.com> <5FC51A42-2CF9-40D9-9840-96B707FD8999@redhat.com> <1966818630.772757.1466515252153.JavaMail.zimbra@redhat.com> <1777179132.773415.1466515411147.JavaMail.zimbra@redhat.com> Message-ID: On 21 Jun 2016, at 15:23, John Mazzitelli wrote: > I guess I should also ask - how long does it take to build that docker > container? A minute? Or a half-hour? It will take the initial time to download the image(s) and then the startup is as quick as directly calling bin/standalone.sh -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht M?nchen HRB 153243 Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander From mazz at redhat.com Tue Jun 21 09:39:32 2016 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 21 Jun 2016 09:39:32 -0400 (EDT) Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> <1165588036.753000.1466511259705.JavaMail.zimbra@redhat.com> <5FC51A42-2CF9-40D9-9840-96B707FD8999@redhat.com> <1966818630.772757.1466515252153.JavaMail.zimbra@redhat.com> <1777179132.773415.1466515411147.JavaMail.zimbra@redhat.com> Message-ID: <1768875358.781914.1466516372819.JavaMail.zimbra@redhat.com> But what about "code-build-run" cycles as you are developing something? I am assuming the docker container can be built right into the target/ directory of the hawkular-services/dist directory (or I guess a new hawkular-services/docker location) and I just run the docker container from there. Why would you have to download the image after you just built it locally? ----- Original Message ----- > On 21 Jun 2016, at 15:23, John Mazzitelli wrote: > > > I guess I should also ask - how long does it take to build that docker > > container? A minute? Or a half-hour? > > It will take the initial time to download the image(s) and then the > startup is as quick as directly calling bin/standalone.sh > > > -- > Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, > Werner-von-Siemens-Ring 14, D-85630 Grasbrunn > Handelsregister: Amtsgericht M?nchen HRB 153243 > Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, > Eric Shander > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From hrupp at redhat.com Tue Jun 21 09:58:53 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 21 Jun 2016 15:58:53 +0200 Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <1966818630.772757.1466515252153.JavaMail.zimbra@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> <1165588036.753000.1466511259705.JavaMail.zimbra@redhat.com> <5FC51A42-2CF9-40D9-9840-96B707FD8999@redhat.com> <1966818630.772757.1466515252153.JavaMail.zimbra@redhat.com> Message-ID: <69149E40-2E29-4D08-A753-0FEFA2E41DCB@redhat.com> On 21 Jun 2016, at 15:20, John Mazzitelli wrote: > Is the file system mounted somewhere locally so its easy to read or > tail the logs? When you start docker with -it argument it will just forward the console log of the server to stdout. This is of course not enough for development inside the server. Right now, only the data directory is exposed, but that can be changed. > If hawkular-services can be built like this and give me everything: > > 1. mvn -Pdocker clean install > 2. docker run ./target/hawkular-services-docker (or whatever the > command is) > 3. ...See the logs on the console and be able to read the log file as > if its on a local mount point... This mostly works like this in the docker-dist3 directory of my branch. You do $ mvn -Pdev install $ cd docker-dist3 $ mvn docker:build $ mvn docker:run I am not saying this is a panacea, but certainly helpful to some > Then that's good enough for me. Of course, that would probably be more > code to have to maintain, so that's bad :) Well. That Docker route is getting some traction at the moment, so it is certainly something we may want to keep going forward. -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht M?nchen HRB 153243 Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander From auszon3 at gmail.com Tue Jun 21 10:31:08 2016 From: auszon3 at gmail.com (Austin Kuo) Date: Tue, 21 Jun 2016 14:31:08 +0000 Subject: [Hawkular-dev] Has to provide tenant header to look up tenant Message-ID: I found something weird when I was playing with the rest api. When I GET ?inventory/tenant?, this request has to provide tenant header. It does not make sense to me because I look up my tenants because I don?t know them. Austin. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160621/629f93e8/attachment.html From mazz at redhat.com Tue Jun 21 10:40:00 2016 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 21 Jun 2016 10:40:00 -0400 (EDT) Subject: [Hawkular-dev] Has to provide tenant header to look up tenant In-Reply-To: References: Message-ID: <389046795.799620.1466520000738.JavaMail.zimbra@redhat.com> Well, the issue is - we no longer have the concept of a tenant being assigned to login credentials (like we had before in the Hawkular-Accounts integration). In that case, the mere fact you logged in as a user "foo" would mean you were assigned tenant(s) that were assigned to user "foo". That isn't the case anymore. Your log-in credentials no longer simply determine your tenants. You have to tell the system what tenant you want to use. I'm not sure what the plan is for the future to bring back the "your log credentials determine your tenants". ----- Original Message ----- > I found something weird when I was playing with the rest api. > > When I GET ?inventory/tenant?, this request has to provide tenant header. > It does not make sense to me because I look up my tenants because I don?t > know them. > > Austin. > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From snegrea at redhat.com Tue Jun 21 13:50:53 2016 From: snegrea at redhat.com (Stefan Negrea) Date: Tue, 21 Jun 2016 12:50:53 -0500 Subject: [Hawkular-dev] Hawkular Community - Distribution Message-ID: Hello Everybody, I want to give an update on the Hawkular Community distribution since Hawkular Services is now on a good track. The Hawkular Community distribution will be built on top of the Hawkular Services with two additions: Embedded Cassandra and Hawkular UI. The Embedded Cassandra was removed from the Hawkular Services but will make its way into the community distribution. The Hawkular UI will be the original web interface from previous Hawkular bundle but updated to work with Hawkular Services. In the short term, the Hawkular Community distributions will be just a rebundling of Hawkular Services with the Embedded Cassandra. The repository for this effort is: https://github.com/hawkular/hawkular-community The Hawkular UI updates are now in the planning stages and I will provide an update as soon as the timeline becomes more clear. The code has been relocated this new repository: https://github.com/hawkular/hawkular-ui Lastly, I renamed old hawkular/hawkular repository hawkular/hawkular-dist-old, marked it as archived, and removed access to it. The new url: https://github.com/hawkular/hawkular-dist-old . My initial reaction was to update hawkular/hawkular for the new community distribution. But after looking at the commit and pull request history it did not make sense to continue using that repository. Also, it would have been really confusing to keep the repository with the old name knowing it will probably be never be updated again, if somebody takes a look at the org and spots that repository it may wonder if the community is still active. A note about the hawkular/hawkular rename, Github has automatic redirects for renamed repositories. If somebody navigates to the old url, they will be redirected to the new name. So as long we do not have another hawkular/hawkular, the old url will keep working (which is is a good idea given existing links and forks). But we should never ever name anything again hawkular/hawkular because it is a very misleading name. Thank you, Stefan Negrea -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160621/1d9dba5e/attachment-0001.html From jpkroehling at redhat.com Tue Jun 21 14:19:18 2016 From: jpkroehling at redhat.com (=?UTF-8?Q?Juraci_Paix=c3=a3o_Kr=c3=b6hling?=) Date: Tue, 21 Jun 2016 20:19:18 +0200 Subject: [Hawkular-dev] Hawkular Community - Distribution In-Reply-To: References: Message-ID: <86cfae4f-21ff-1e60-1ced-36066ba7fe5b@redhat.com> On 21.06.2016 19:50, Stefan Negrea wrote: > Lastly, I renamed old hawkular/hawkular repository > hawkular/hawkular-dist-old, marked it as archived, and removed access to > it. The new url: https://github.com/hawkular/hawkular-dist-old . Just to share with the list the feedback I already gave privately on IRC: I think this should have not been renamed, and should be renamed back to hawkular/hawkular . Even if GitHub performs redirects, we should not rename repositories unless we are forced to, as there are a good number of places referencing to that. People reading "hawkular/hawkular" in some (old?) documentation might be confused when they look at the list of repositories and not find this repository. And I don't think our reasons are strong enough to deserve a rename. Besides, we voted for not renaming the repositories, adding appropriate descriptions instead. As for the contents of hawkular/hawkular, I see two options: 1) For the case where we really want to dismiss hawkular/hawkular entirely and never go back, let's just do a "git rm -rf ." and push the commit, with an appropriate README file 2) A less drastic option is to have the community build come from this repository. It might be confusing, but the contents of -community are similar in purpose to that of hawkular/hawkular . So, it could be seen as an evolution. The appropriate thing then is to "git rm" everything that will not be in the new community distribution. - Juca. From hrupp at redhat.com Tue Jun 21 15:36:17 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 21 Jun 2016 21:36:17 +0200 Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: <1768875358.781914.1466516372819.JavaMail.zimbra@redhat.com> References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <63537775-ea13-4fbd-5370-069681e73c23@redhat.com> <1165588036.753000.1466511259705.JavaMail.zimbra@redhat.com> <5FC51A42-2CF9-40D9-9840-96B707FD8999@redhat.com> <1966818630.772757.1466515252153.JavaMail.zimbra@redhat.com> <1777179132.773415.1466515411147.JavaMail.zimbra@redhat.com> <1768875358.781914.1466516372819.JavaMail.zimbra@redhat.com> Message-ID: On 21 Jun 2016, at 15:39, John Mazzitelli wrote: > But what about "code-build-run" cycles as you are developing > something? I am assuming the docker container can be built right into > the target/ directory of the hawkular-services/dist directory (or I > guess a new hawkular-services/docker location) and I just run the > docker container from there. Yes. > > Why would you have to download the image after you just built it > locally? This was more meant if you only want to consume the hawkular-services server like in the scenario of working on the MiQ provider or writing a new external agent. For local server development it is probably best to just run the server "bare metal". C* could still live in Docker though. But here the advantage is certainly less. -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht M?nchen HRB 153243 Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander From mazz at redhat.com Tue Jun 21 16:29:19 2016 From: mazz at redhat.com (John Mazzitelli) Date: Tue, 21 Jun 2016 16:29:19 -0400 (EDT) Subject: [Hawkular-dev] hawkular services with embedded c profile - need PR reviewed/merged In-Reply-To: References: <1600816477.429053.1466438564113.JavaMail.zimbra@redhat.com> <1165588036.753000.1466511259705.JavaMail.zimbra@redhat.com> <5FC51A42-2CF9-40D9-9840-96B707FD8999@redhat.com> <1966818630.772757.1466515252153.JavaMail.zimbra@redhat.com> <1777179132.773415.1466515411147.JavaMail.zimbra@redhat.com> <1768875358.781914.1466516372819.JavaMail.zimbra@redhat.com> Message-ID: <459139812.870602.1466540959591.JavaMail.zimbra@redhat.com> > > Why would you have to download the image after you just built it locally? > > This was more meant if you only want to consume the hawkular-services > server like in the scenario of working on the MiQ provider or writing > a new external agent. > > For local server development it is probably best to just run the > server "bare metal". C* could still live in Docker though. But here > the advantage is certainly less. Hence, why I want -Pembeddedc in hawkular services build - no need for separate C* docker container to run! :) Am I going to be able to get this PR merged? Again, it is not the default, and no one even has to know it exists if you don't want to use it - you never have to use it if you love running C* externally. And the change isn't even large. There isn't a lot going on under the covers here to support this. https://github.com/hawkular/hawkular-services/pull/22 From tsegismo at redhat.com Tue Jun 21 17:59:49 2016 From: tsegismo at redhat.com (Thomas Segismont) Date: Tue, 21 Jun 2016 23:59:49 +0200 Subject: [Hawkular-dev] Metrics performance testing PR#520 Message-ID: <44a65614-99cd-c58e-b792-5db712980dd9@redhat.com> Hi, Today I've been looking at Metrics insertion performance. My setup is the following: - on my laptop I run the Gatling load scenario (which is very similar to the perf test job scenario) - I also run a Metrics standalone instance - on another machine connected to my LAN, I run a single node C* cluster In order to avoid problems due to memory constraints, I set min and max heap size to 2048m. Below this value the server spends significant time in garbage collection (with high number of concurrent clients). I ran Gatling 3 times with different number of clients (think agents): 100,1000,2000 ---- mvn gatling:execute -Dclients=X -Dramp=0 -Dloops=50 ---- From 100 to 1000 virtual clients, the throughput raised accordingly (x10). From 1000 to 2000, I hit the same kind of plateau Filip was observing: I got barely 15% throughput increase. None of the machines had reached cpu/io/memory limits. So I ran the 2000 virtual clients test again and jstack (result attached). As you can see, most of the task handler threads are in state WAITING inside the com.datastax.driver.core.HostConnectionPool.awaitAvailableConnection method. Then, following the "Monitoring and tuning the pool" section of the driver doc, I added some code to print the number of open connections, active requests, and maximum capacity. It confirmed that the maximum capacity was reached. Note that by default with the V3 protocol, the driver creates just one connection per host and allows a maximum of 1024 concurrent requests. After that I added new options in the code to let the user define the max number of connections per host as well as requests per connection. In my tests, I set the maximum connection limit to 10 and maximum concurrency to 5000. These are arbitrary values, they are simply bigger than the default. Best values would depend on the environment and should be determined with testing. Then I ran Gatling 3 times again (100, 1000, 2000 virtual clients). This time throughput increased linearly with the number of clients, from 100 to 1000 and then 2000. I also tried with 3000, but this time throughput did not increase as much. This was certainly due to both machines now using more than 80% cpu. I sent a pull request [2] with the changes needed for the new configuration parameters. Hopefully it can help in Filip's tests as well. Regards, -- Thomas Segismont JBoss ON Engineering Team [1] http://datastax.github.io/java-driver/manual/pooling/#monitoring-and-tuning-the-pool [2] https://github.com/hawkular/hawkular-metrics/pull/520 -------------- next part -------------- A non-text attachment was scrubbed... Name: stack.tar.gz Type: application/gzip Size: 16416 bytes Desc: not available Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160621/8f63b78c/attachment-0001.bin From gbrown at redhat.com Wed Jun 22 04:45:24 2016 From: gbrown at redhat.com (Gary Brown) Date: Wed, 22 Jun 2016 04:45:24 -0400 (EDT) Subject: [Hawkular-dev] JMS/MDB related PR to be reviewed In-Reply-To: <693148924.617114.1466584483459.JavaMail.zimbra@redhat.com> Message-ID: <1725383634.618214.1466585124775.JavaMail.zimbra@redhat.com> https://github.com/hawkular/hawkular-apm/pull/456 Hawkular APM uses JMS as its event processing backbone, with events being passed around in batches. When some or all of a batch of events fails to be processed by a particular component, it has a retry mechanism that resubmits the failed events to be processed again (subject to a max retry count). The problem with the current approach is that it is resubmitting the events to the source topic upon which the events were received - however this topic may also be used by other processing components that had processed the events successfully. For example, processing components A and B subscribe to a particular topic T - A processes all of the events in batch B1 successfully, and B only processes half, retrying the other half. When the failed half are published back to topic T again, then A receives them a second time, even though they were processed successfully the first time. Therefore the retry mechanism needs to be more targetted, so that the resubmitted events are only processed by the component that failed to process the events before. There are two possible ways to do this: 1) Define a retry queue - this means doubling up on all of the subscribers, so that each subscriber (i.e. processing capability) would have a topic subscriber to receive the initial events, and a retry queue to handle failed attempts. Its possible a single retry queue could be used with a message selector to distinguish the target processing unit. 2) Use a message selector on the original topic - so in this case, no more destinations need to be added, the initial message has no property defined so will be received by all topic subscribers, whereas when the message is resubmitted, it will have a target subscriber named, which will be routed through to the correct subscriber based on a message selector. This PR implements this second approach. On initial tests the performance hit of using a message selector appears negligible, although this was my initial concern. If this does prove to be an issue in the future, then the single queue with message selector approach in (1) could be used. Anyone able to review/merge the PR for me? Thanks in advance. Regards Gary From fbrychta at redhat.com Wed Jun 22 06:56:57 2016 From: fbrychta at redhat.com (Filip Brychta) Date: Wed, 22 Jun 2016 06:56:57 -0400 (EDT) Subject: [Hawkular-dev] Metrics performance testing PR#520 - big perf improvement In-Reply-To: <44a65614-99cd-c58e-b792-5db712980dd9@redhat.com> References: <44a65614-99cd-c58e-b792-5db712980dd9@redhat.com> Message-ID: <1161086950.337807.1466593017922.JavaMail.zimbra@redhat.com> This PR increased throughput 0 -- 200% depending on msg size!!! Performance increase based on msg size: 1 datapoint per request - no change 10 datapoints per request - 100% throughput increase 100 datapoints per request - 200% throughput increase 500 datapoints per request - 180% throughput increase 5000 datapoints per request - 130% throughput increase CPU usage is significantly higher, before it was 70% idle, after it's just 12% idle. Filip ----- Original Message ----- > Hi, > > Today I've been looking at Metrics insertion performance. > > My setup is the following: > - on my laptop I run the Gatling load scenario (which is very similar to > the perf test job scenario) > - I also run a Metrics standalone instance > - on another machine connected to my LAN, I run a single node C* cluster > > In order to avoid problems due to memory constraints, I set min and max > heap size to 2048m. Below this value the server spends significant time > in garbage collection (with high number of concurrent clients). > > I ran Gatling 3 times with different number of clients (think agents): > 100,1000,2000 > ---- > mvn gatling:execute -Dclients=X -Dramp=0 -Dloops=50 > ---- > > From 100 to 1000 virtual clients, the throughput raised accordingly > (x10). From 1000 to 2000, I hit the same kind of plateau Filip was > observing: I got barely 15% throughput increase. None of the machines > had reached cpu/io/memory limits. > > So I ran the 2000 virtual clients test again and jstack (result > attached). As you can see, most of the task handler threads are in state > WAITING inside the > com.datastax.driver.core.HostConnectionPool.awaitAvailableConnection method. > > Then, following the "Monitoring and tuning the pool" section of the > driver doc, I added some code to print the number of open connections, > active requests, and maximum capacity. It confirmed that the maximum > capacity was reached. > > Note that by default with the V3 protocol, the driver creates just one > connection per host and allows a maximum of 1024 concurrent requests. > > After that I added new options in the code to let the user define the > max number of connections per host as well as requests per connection. > > In my tests, I set the maximum connection limit to 10 and maximum > concurrency to 5000. These are arbitrary values, they are simply bigger > than the default. Best values would depend on the environment and should > be determined with testing. > > Then I ran Gatling 3 times again (100, 1000, 2000 virtual clients). This > time throughput increased linearly with the number of clients, from 100 > to 1000 and then 2000. I also tried with 3000, but this time throughput > did not increase as much. This was certainly due to both machines now > using more than 80% cpu. > > I sent a pull request [2] with the changes needed for the new > configuration parameters. > > Hopefully it can help in Filip's tests as well. > > Regards, > > -- > Thomas Segismont > JBoss ON Engineering Team > > [1] > http://datastax.github.io/java-driver/manual/pooling/#monitoring-and-tuning-the-pool > [2] https://github.com/hawkular/hawkular-metrics/pull/520 > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From jsanda at redhat.com Wed Jun 22 07:33:53 2016 From: jsanda at redhat.com (John Sanda) Date: Wed, 22 Jun 2016 07:33:53 -0400 Subject: [Hawkular-dev] Metrics performance testing PR#520 - big perf improvement In-Reply-To: <1161086950.337807.1466593017922.JavaMail.zimbra@redhat.com> References: <44a65614-99cd-c58e-b792-5db712980dd9@redhat.com> <1161086950.337807.1466593017922.JavaMail.zimbra@redhat.com> Message-ID: <8E18B2D5-90E3-4E0C-8651-A885DD99CCC1@redhat.com> This is awesome. Nice work Thomas! > On Jun 22, 2016, at 6:56 AM, Filip Brychta wrote: > > This PR increased throughput 0 -- 200% depending on msg size!!! > > Performance increase based on msg size: > 1 datapoint per request - no change > 10 datapoints per request - 100% throughput increase > 100 datapoints per request - 200% throughput increase > 500 datapoints per request - 180% throughput increase > 5000 datapoints per request - 130% throughput increase > > CPU usage is significantly higher, before it was 70% idle, after it's just 12% idle. > > Filip > > ----- Original Message ----- >> Hi, >> >> Today I've been looking at Metrics insertion performance. >> >> My setup is the following: >> - on my laptop I run the Gatling load scenario (which is very similar to >> the perf test job scenario) >> - I also run a Metrics standalone instance >> - on another machine connected to my LAN, I run a single node C* cluster >> >> In order to avoid problems due to memory constraints, I set min and max >> heap size to 2048m. Below this value the server spends significant time >> in garbage collection (with high number of concurrent clients). >> >> I ran Gatling 3 times with different number of clients (think agents): >> 100,1000,2000 >> ---- >> mvn gatling:execute -Dclients=X -Dramp=0 -Dloops=50 >> ---- >> >> From 100 to 1000 virtual clients, the throughput raised accordingly >> (x10). From 1000 to 2000, I hit the same kind of plateau Filip was >> observing: I got barely 15% throughput increase. None of the machines >> had reached cpu/io/memory limits. >> >> So I ran the 2000 virtual clients test again and jstack (result >> attached). As you can see, most of the task handler threads are in state >> WAITING inside the >> com.datastax.driver.core.HostConnectionPool.awaitAvailableConnection method. >> >> Then, following the "Monitoring and tuning the pool" section of the >> driver doc, I added some code to print the number of open connections, >> active requests, and maximum capacity. It confirmed that the maximum >> capacity was reached. >> >> Note that by default with the V3 protocol, the driver creates just one >> connection per host and allows a maximum of 1024 concurrent requests. >> >> After that I added new options in the code to let the user define the >> max number of connections per host as well as requests per connection. >> >> In my tests, I set the maximum connection limit to 10 and maximum >> concurrency to 5000. These are arbitrary values, they are simply bigger >> than the default. Best values would depend on the environment and should >> be determined with testing. >> >> Then I ran Gatling 3 times again (100, 1000, 2000 virtual clients). This >> time throughput increased linearly with the number of clients, from 100 >> to 1000 and then 2000. I also tried with 3000, but this time throughput >> did not increase as much. This was certainly due to both machines now >> using more than 80% cpu. >> >> I sent a pull request [2] with the changes needed for the new >> configuration parameters. >> >> Hopefully it can help in Filip's tests as well. >> >> Regards, >> >> -- >> Thomas Segismont >> JBoss ON Engineering Team >> >> [1] >> http://datastax.github.io/java-driver/manual/pooling/#monitoring-and-tuning-the-pool >> [2] https://github.com/hawkular/hawkular-metrics/pull/520 >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev From lkrejci at redhat.com Wed Jun 22 08:49:08 2016 From: lkrejci at redhat.com (Lukas Krejci) Date: Wed, 22 Jun 2016 14:49:08 +0200 Subject: [Hawkular-dev] Has to provide tenant header to look up tenant In-Reply-To: References: Message-ID: <4487170.vuVg13tfed@localhost.localdomain> Inventory's REST API currently doesn't have a mechanism to tell you the list of tenants it knows about. I'm not sure it actually is a desirable thing to do, because the knowledge of tenant IDs are an external concern that might be up for some kind of authorization checks that are out of control of inventory. As such, inventory just goes with the tenant ID you give it and assumes you are authorized to know it. The tenant endpoint exists solely because you can ask questions about the tenant (of which you only know the ID otherwise) like what properties are stored with it, what relationships it participates in, etc. On Tuesday, June 21, 2016 02:31:08 PM Austin Kuo wrote: > I found something weird when I was playing with the rest api. > > When I GET ?inventory/tenant?, this request has to provide tenant header. > It does not make sense to me because I look up my tenants because I don?t > know them. > > Austin. -- Lukas Krejci From lkrejci at redhat.com Wed Jun 22 08:54:08 2016 From: lkrejci at redhat.com (Lukas Krejci) Date: Wed, 22 Jun 2016 14:54:08 +0200 Subject: [Hawkular-dev] Request for PR review - build-tools - https://github.com/hawkular/hawkular-build-tools/pull/25 Message-ID: <3677845.47cshoex4K@localhost.localdomain> Hi all, I've made some adjustments to our swagger -> asciidoc script so that it is able to emit information about inheritance of the data definitions. I'd like to use this for the next Inventory release, because the REST docs are border-line useless without it. I made biiig updates to the REST docs for the new inventory REST API and would like to have it in shape before the imminent release of it. Therefore I humbly ask for review of the above mentioned PR so that we can release new build-tools and parent that I could then consume in inventory for the new release. Thanks, -- Lukas Krejci From gbrown at redhat.com Wed Jun 22 12:17:46 2016 From: gbrown at redhat.com (Gary Brown) Date: Wed, 22 Jun 2016 12:17:46 -0400 (EDT) Subject: [Hawkular-dev] Request for PR review - build-tools - https://github.com/hawkular/hawkular-build-tools/pull/25 In-Reply-To: <3677845.47cshoex4K@localhost.localdomain> References: <3677845.47cshoex4K@localhost.localdomain> Message-ID: <26281432.718566.1466612266788.JavaMail.zimbra@redhat.com> Hi Lukas I ran the script locally (rather than pulling in via the build tools plugin), and mostly it seemed fine, although I had one strange situation with the InteractionNode data type, which has two fields both of type Message - however in the adoc they are listed with type 'null'. I've attached the files. Otherwise it looks good to me - and something APM definitely needs :) Regards Gary ----- Original Message ----- > Hi all, > > I've made some adjustments to our swagger -> asciidoc script so that it is > able to emit information about inheritance of the data definitions. > > I'd like to use this for the next Inventory release, because the REST docs > are > border-line useless without it. > > I made biiig updates to the REST docs for the new inventory REST API and > would > like to have it in shape before the imminent release of it. > > Therefore I humbly ask for review of the above mentioned PR so that we can > release new build-tools and parent that I could then consume in inventory for > the new release. > > Thanks, > > -- > Lukas Krejci > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- A non-text attachment was scrubbed... Name: swagger.json Type: application/json Size: 78356 bytes Desc: not available Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160622/f30843b6/attachment-0001.bin -------------- next part -------------- A non-text attachment was scrubbed... Name: rest-apm.adoc Type: application/octet-stream Size: 52469 bytes Desc: not available Url : http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160622/f30843b6/attachment-0001.obj From auszon3 at gmail.com Thu Jun 23 04:01:42 2016 From: auszon3 at gmail.com (Austin Kuo) Date: Thu, 23 Jun 2016 08:01:42 +0000 Subject: [Hawkular-dev] Sync with Inventory In-Reply-To: <2103173.GQyceoZSXW@localhost.localdomain> References: <2103173.GQyceoZSXW@localhost.localdomain> Message-ID: Yes, I?m gonna build the inventory for vertx applications. So I have to create a feed for it. Thanks! On Tue, Jun 21, 2016 at 7:55 PM Lukas Krejci wrote: > Hi Austin, > > Inventory offers a /hawkular/inventory/sync endpoint that is used to > synchronize the "world view" of feeds (feed being something that pushes > data > into inventory). > > You said though that a "user creates" the resources, so I am not sure if > /sync > would be applicable to your scenario. Would you please elaborate more on > where > in the inventory hierarchy you create your resources and how? I.e. are you > using some sort of feed akin to Hawkular's Wildfly Agent or are you just > creating your resources "manually" under environments? > > On Tuesday, June 21, 2016 02:20:33 AM Austin Kuo wrote: > > Hi all, > > > > I?m currently investigating how to sync with inventory server. > > Here?s the example scenario: > > Consider the following problem. A user creates version 1 of the app with > > two http servers, one listening on port 8080, the other on port 8181. In > > version 2, the http server listening on port 8181 is no longer needed. > > When the old version is stopped and the new version started, there will > be > > just one http server listening. The application is not aware of the > > previous state. What should we do so that the second http server is > removed > > from Inventory? > > > > Thanks in advance. > > -- > Lukas Krejci > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160623/84b0fa36/attachment.html From tsegismo at redhat.com Thu Jun 23 04:27:12 2016 From: tsegismo at redhat.com (Thomas Segismont) Date: Thu, 23 Jun 2016 10:27:12 +0200 Subject: [Hawkular-dev] Sync with Inventory In-Reply-To: References: <2103173.GQyceoZSXW@localhost.localdomain> Message-ID: <6b0e30d4-bb89-1062-427b-dcb4a53275b6@redhat.com> Hey Lukas, Thank you for pointing us in the sync endpoint. Austin will look into this and will certainly come back with more questions. With respect to the user creating resources question, the difference between Vert.x and Wildfly is that the user creates resources grammatically. So in version 1 of the application, there might be two HTTP servers as well as 7 event bus handlers, but only 1 http server in version 2. And a named worker pool in version 3. In the end, I believe it doesn't matter if it's container which creates resources or if it's the user himself. Does it? As for the feed question, the Vert.x feed will be the Metrics SPI implementation (vertx-hawkular-metrics project). Again I guess it's not much different than the Hawkular Agent. Maybe the wording around user creating resources was confusing? Did you thought he would do so from application code? In this case, the answer is no. Regards, Thomas Le 23/06/2016 ? 10:01, Austin Kuo a ?crit : > Yes, I?m gonna build the inventory for vertx applications. > So I have to create a feed for it. > > Thanks! > > On Tue, Jun 21, 2016 at 7:55 PM Lukas Krejci > wrote: > > Hi Austin, > > Inventory offers a /hawkular/inventory/sync endpoint that is used to > synchronize the "world view" of feeds (feed being something that > pushes data > into inventory). > > You said though that a "user creates" the resources, so I am not > sure if /sync > would be applicable to your scenario. Would you please elaborate > more on where > in the inventory hierarchy you create your resources and how? I.e. > are you > using some sort of feed akin to Hawkular's Wildfly Agent or are you just > creating your resources "manually" under environments? > > On Tuesday, June 21, 2016 02:20:33 AM Austin Kuo wrote: > > Hi all, > > > > I?m currently investigating how to sync with inventory server. > > Here?s the example scenario: > > Consider the following problem. A user creates version 1 of the > app with > > two http servers, one listening on port 8080, the other on port > 8181. In > > version 2, the http server listening on port 8181 is no longer needed. > > When the old version is stopped and the new version started, there > will be > > just one http server listening. The application is not aware of the > > previous state. What should we do so that the second http server > is removed > > from Inventory? > > > > Thanks in advance. > > -- > Lukas Krejci > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -- Thomas Segismont JBoss ON Engineering Team From lkrejci at redhat.com Thu Jun 23 09:59:37 2016 From: lkrejci at redhat.com (Lukas Krejci) Date: Thu, 23 Jun 2016 15:59:37 +0200 Subject: [Hawkular-dev] Sync with Inventory In-Reply-To: <6b0e30d4-bb89-1062-427b-dcb4a53275b6@redhat.com> References: <6b0e30d4-bb89-1062-427b-dcb4a53275b6@redhat.com> Message-ID: <37609601.21BcKnHFje@rpi.lan> On Thursday, June 23, 2016 10:27:12 AM Thomas Segismont wrote: > Hey Lukas, > > Thank you for pointing us in the sync endpoint. Austin will look into > this and will certainly come back with more questions. > > With respect to the user creating resources question, the difference > between Vert.x and Wildfly is that the user creates resources > grammatically. So in version 1 of the application, there might be two > HTTP servers as well as 7 event bus handlers, but only 1 http server in > version 2. And a named worker pool in version 3. > > In the end, I believe it doesn't matter if it's container which creates > resources or if it's the user himself. Does it? > It does not really (inventory has just a single API, so it does not really know who is talking to it - if a feed or if a user) - but resources inside and outside feeds have slightly different semantics. Right now the logic is this: Feeds are "agents" that don't care about anything else but their own little "world". That's why they can create their own resource types, metric types and they also declare resources and metrics of those types. Feed does not need to look "outside" of its own data and is in full charge of it. Hence the /sync endpoint applies to a feed nicely - since it is in charge, it merely declares what is the view it has currently of the "world" it sees and inventory will make sure it has the same picture - under that feed. Now if you have an application that spans multiple vms/machines and is composed of multiple processes, there is no such clear distinction of "ownership". While indeed a "real" user can just act like a feed, the envisioned workflow is that the user operates directly in environments and at the top level. I.e. a user assigns feeds to environments (i.e. this feed reports on my server in staging environment, etc) and the user creates "logical" resources in the environment (i.e. "My App" resource in staging env is composed of a load balancer managed by this feed, mongodb managed by another feed there and clustered wflys there, there and there). To model this, inventory supports 2 kinds of tree hierarchies - 1 created using the "contains" relationship, which expresses existential ownership - i.e. a feed contains its resources and if a feed disappears, so do the resources, because no one else can report on them. The entities bound by the contains relationship form a tree - no loops or diamonds in it (this is enforced by inventory). But there can also be a hierarchy created using an "isParentOf" relationship (which represents "logical" ownership). Resources bound by "isParentOf" can form an acyclic graph - i.e. 1 resource can have multiple parents as well as many children (isParentOf is applicable only to resources, not other types of entities). The hierarchies formed by "contains" and "isParentOf" are independent. So you can create a resource "My App" in the staging environment and declare it a parent (using "isParentOf") of the resources declared by feeds that manage the machines where the constituent servers live. That is the envisaged workflow for "apps". Now the downside to that is that (currently) there is no "sync" for that. The reason is that the application really is a logical concept and the underlying servers can be repurposed to serve different applications (so if app stops using it, it shouldn't really disappear from inventory, as is the case with /sync - because if a feed doesn't "see" a resource, then it really is just gone, because the feed is solely responsible for reporting on it). We can think about how to somehow help clients with "App sync" but I'm not sure if having a feed for vertx is the right thing to do. On the other hand I very well may not be seeing some obvious problems of the above or parallels that make the 2 approaches really the same because the above model is just ingrained in my brain after so many hours thinking about it ;) > As for the feed question, the Vert.x feed will be the Metrics SPI > implementation (vertx-hawkular-metrics project). Again I guess it's not > much different than the Hawkular Agent. > A feed would only be appropriate if vertx app never reported on something that would also be reported by other agents. I.e. if a part of a vertx application is also reported on by a wfly agent, because that part is running in a wfly server managed by us, then that will not work - 1 resource cannot be "contained" in 2 different feeds (not just API wise, but logically, too). > Maybe the wording around user creating resources was confusing? Did you > thought he would do so from application code? In this case, the answer > is no. > Yeah, we should probably get together and discuss what your plans are to get on the same page with everything. > Regards, > Thomas > > Le 23/06/2016 ? 10:01, Austin Kuo a ?crit : > > Yes, I?m gonna build the inventory for vertx applications. > > So I have to create a feed for it. > > > > Thanks! > > > > On Tue, Jun 21, 2016 at 7:55 PM Lukas Krejci > > > > wrote: > > Hi Austin, > > > > Inventory offers a /hawkular/inventory/sync endpoint that is used to > > synchronize the "world view" of feeds (feed being something that > > pushes data > > into inventory). > > > > You said though that a "user creates" the resources, so I am not > > sure if /sync > > would be applicable to your scenario. Would you please elaborate > > more on where > > in the inventory hierarchy you create your resources and how? I.e. > > are you > > using some sort of feed akin to Hawkular's Wildfly Agent or are you > > just > > creating your resources "manually" under environments? > > > > On Tuesday, June 21, 2016 02:20:33 AM Austin Kuo wrote: > > > Hi all, > > > > > > I?m currently investigating how to sync with inventory server. > > > Here?s the example scenario: > > > Consider the following problem. A user creates version 1 of the > > > > app with > > > > > two http servers, one listening on port 8080, the other on port > > > > 8181. In > > > > > version 2, the http server listening on port 8181 is no longer > > > needed. > > > When the old version is stopped and the new version started, there > > > > will be > > > > > just one http server listening. The application is not aware of the > > > previous state. What should we do so that the second http server > > > > is removed > > > > > from Inventory? > > > > > > Thanks in advance. > > > > -- > > Lukas Krejci > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev -- Lukas Krejci From kurrent93 at gmail.com Thu Jun 23 14:53:52 2016 From: kurrent93 at gmail.com (Anton) Date: Thu, 23 Jun 2016 20:53:52 +0200 Subject: [Hawkular-dev] Want to try hawkular-services via Docker? In-Reply-To: <27E77FC8-F395-4AF8-B53C-F83A2D9C4359@redhat.com> References: <27E77FC8-F395-4AF8-B53C-F83A2D9C4359@redhat.com> Message-ID: Thanks Heiko This is really useful! Can you tell me, once running - what is the url to login? Thanks On Tue, Jun 21, 2016 at 12:31 PM, Heiko W.Rupp wrote: > > If you want to give it a try you can save the following > into a file docker-compose.yml > and then run docker-compose up hawkular > This image has the -Pdev user jdoe/password. > > hawkular: > image: "pilhuhn/hawkular-services:latest" > ports: > - "8080:8080" > - "8443:8443" > - "9990:9990" > volumes: > - /tmp/opt/hawkular/data:/opt/data > links: > - myCassandra > environment: > - HAWKULAR_BACKEND=remote > - CASSANDRA_NODES=myCassandra > myCassandra: > image: cassandra:3.7 > environment: > - CASSANDRA_START_RPC=true > volumes: > - /tmp/opt/hawkular/cassandra:/var/lib/cassandra > > > -- > Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, > Werner-von-Siemens-Ring 14, D-85630 Grasbrunn > Handelsregister: Amtsgericht M?nchen HRB 153243 > Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, > Eric Shander > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160623/e061c2a2/attachment.html From gbrown at redhat.com Fri Jun 24 07:42:25 2016 From: gbrown at redhat.com (Gary Brown) Date: Fri, 24 Jun 2016 07:42:25 -0400 (EDT) Subject: [Hawkular-dev] PR to review: https://github.com/hawkular/hawkular-apm/pull/461 In-Reply-To: <1803764400.1183613.1466768518811.JavaMail.zimbra@redhat.com> Message-ID: <205071982.1183624.1466768545476.JavaMail.zimbra@redhat.com> Hi Hopefully should be quick to review, just about making previously hard coded defaults for retry mechanism configurable via system properties/environment variables. Any takers? Regards Gary From jsanda at redhat.com Sat Jun 25 11:20:33 2016 From: jsanda at redhat.com (John Sanda) Date: Sat, 25 Jun 2016 11:20:33 -0400 Subject: [Hawkular-dev] hawkular metrics schema upgrade bug Message-ID: New schema change management code was introduced in hawkular-metrics 0.15.0. There were some bugs that break upgrades. Upgrading with 0.15.0 and 0.16.0 will not work. A few people have run into this. I have already submitted a PR with the fixes to be included in the next release. The ticket for this is https://issues.jboss.org/browse/HWKMETRICS-425 . - John -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160625/f14fe140/attachment.html From auszon3 at gmail.com Sat Jun 25 20:38:32 2016 From: auszon3 at gmail.com (Austin Kuo) Date: Sun, 26 Jun 2016 00:38:32 +0000 Subject: [Hawkular-dev] Sync with Inventory In-Reply-To: <37609601.21BcKnHFje@rpi.lan> References: <6b0e30d4-bb89-1062-427b-dcb4a53275b6@redhat.com> <37609601.21BcKnHFje@rpi.lan> Message-ID: yeah thanks for this :) Lukas Krejci ? 2016?6?23? ???21:59??? > On Thursday, June 23, 2016 10:27:12 AM Thomas Segismont wrote: > > Hey Lukas, > > > > Thank you for pointing us in the sync endpoint. Austin will look into > > this and will certainly come back with more questions. > > > > With respect to the user creating resources question, the difference > > between Vert.x and Wildfly is that the user creates resources > > grammatically. So in version 1 of the application, there might be two > > HTTP servers as well as 7 event bus handlers, but only 1 http server in > > version 2. And a named worker pool in version 3. > > > > In the end, I believe it doesn't matter if it's container which creates > > resources or if it's the user himself. Does it? > > > > It does not really (inventory has just a single API, so it does not really > know who is talking to it - if a feed or if a user) - but resources inside > and > outside feeds have slightly different semantics. > > Right now the logic is this: > > Feeds are "agents" that don't care about anything else but their own little > "world". That's why they can create their own resource types, metric types > and > they also declare resources and metrics of those types. Feed does not need > to > look "outside" of its own data and is in full charge of it. > > Hence the /sync endpoint applies to a feed nicely - since it is in charge, > it > merely declares what is the view it has currently of the "world" it sees > and > inventory will make sure it has the same picture - under that feed. > > Now if you have an application that spans multiple vms/machines and is > composed of multiple processes, there is no such clear distinction of > "ownership". > > While indeed a "real" user can just act like a feed, the envisioned > workflow > is that the user operates directly in environments and at the top level. > I.e. > a user assigns feeds to environments (i.e. this feed reports on my server > in > staging environment, etc) and the user creates "logical" resources in the > environment (i.e. "My App" resource in staging env is composed of a load > balancer managed by this feed, mongodb managed by another feed there and > clustered wflys there, there and there). > > To model this, inventory supports 2 kinds of tree hierarchies - 1 created > using the "contains" relationship, which expresses existential ownership - > i.e. a feed contains its resources and if a feed disappears, so do the > resources, because no one else can report on them. The entities bound by > the > contains relationship form a tree - no loops or diamonds in it (this is > enforced by inventory). But there can also be a hierarchy created using an > "isParentOf" relationship (which represents "logical" ownership). Resources > bound by "isParentOf" can form an acyclic graph - i.e. 1 resource can have > multiple parents as well as many children (isParentOf is applicable only to > resources, not other types of entities). > > The hierarchies formed by "contains" and "isParentOf" are independent. So > you > can create a resource "My App" in the staging environment and declare it a > parent (using "isParentOf") of the resources declared by feeds that manage > the > machines where the constituent servers live. > > That is the envisaged workflow for "apps". Now the downside to that is that > (currently) there is no "sync" for that. The reason is that the application > really is a logical concept and the underlying servers can be repurposed to > serve different applications (so if app stops using it, it shouldn't really > disappear from inventory, as is the case with /sync - because if a feed > doesn't "see" a resource, then it really is just gone, because the feed is > solely responsible for reporting on it). > > We can think about how to somehow help clients with "App sync" but I'm not > sure if having a feed for vertx is the right thing to do. On the other > hand I > very well may not be seeing some obvious problems of the above or parallels > that make the 2 approaches really the same because the above model is just > ingrained in my brain after so many hours thinking about it ;) > > > As for the feed question, the Vert.x feed will be the Metrics SPI > > implementation (vertx-hawkular-metrics project). Again I guess it's not > > much different than the Hawkular Agent. > > > > A feed would only be appropriate if vertx app never reported on something > that > would also be reported by other agents. I.e. if a part of a vertx > application > is also reported on by a wfly agent, because that part is running in a wfly > server managed by us, then that will not work - 1 resource cannot be > "contained" in 2 different feeds (not just API wise, but logically, too). > > > Maybe the wording around user creating resources was confusing? Did you > > thought he would do so from application code? In this case, the answer > > is no. > > > > Yeah, we should probably get together and discuss what your plans are to > get > on the same page with everything. > > > Regards, > > Thomas > > > > Le 23/06/2016 ? 10:01, Austin Kuo a ?crit : > > > Yes, I?m gonna build the inventory for vertx applications. > > > So I have to create a feed for it. > > > > > > Thanks! > > > > > > On Tue, Jun 21, 2016 at 7:55 PM Lukas Krejci > > > > > > wrote: > > > Hi Austin, > > > > > > Inventory offers a /hawkular/inventory/sync endpoint that is used > to > > > synchronize the "world view" of feeds (feed being something that > > > pushes data > > > into inventory). > > > > > > You said though that a "user creates" the resources, so I am not > > > sure if /sync > > > would be applicable to your scenario. Would you please elaborate > > > more on where > > > in the inventory hierarchy you create your resources and how? I.e. > > > are you > > > using some sort of feed akin to Hawkular's Wildfly Agent or are you > > > just > > > creating your resources "manually" under environments? > > > > > > On Tuesday, June 21, 2016 02:20:33 AM Austin Kuo wrote: > > > > Hi all, > > > > > > > > I?m currently investigating how to sync with inventory server. > > > > Here?s the example scenario: > > > > Consider the following problem. A user creates version 1 of the > > > > > > app with > > > > > > > two http servers, one listening on port 8080, the other on port > > > > > > 8181. In > > > > > > > version 2, the http server listening on port 8181 is no longer > > > > needed. > > > > When the old version is stopped and the new version started, > there > > > > > > will be > > > > > > > just one http server listening. The application is not aware of > the > > > > previous state. What should we do so that the second http server > > > > > > is removed > > > > > > > from Inventory? > > > > > > > > Thanks in advance. > > > > > > -- > > > Lukas Krejci > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > _______________________________________________ > > > hawkular-dev mailing list > > > hawkular-dev at lists.jboss.org > > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -- > Lukas Krejci > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160626/79d077a5/attachment.html From hrupp at redhat.com Sat Jun 25 12:44:27 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Sat, 25 Jun 2016 18:44:27 +0200 Subject: [Hawkular-dev] Avail-percentage query in metrics? Message-ID: <6B852775-D521-42E7-9108-71C7D0AE43D0@redhat.com> Hey, is there a way to query Hawkular-metrics like this: "give me the distribution of availability (up, down, ..) over a given time range" The result could be aggregated time per value or relative percentages - this does not matter. Heiko From jsanda at redhat.com Sun Jun 26 07:31:06 2016 From: jsanda at redhat.com (John Sanda) Date: Sun, 26 Jun 2016 07:31:06 -0400 Subject: [Hawkular-dev] Avail-percentage query in metrics? In-Reply-To: <6B852775-D521-42E7-9108-71C7D0AE43D0@redhat.com> References: <6B852775-D521-42E7-9108-71C7D0AE43D0@redhat.com> Message-ID: <734D1718-3E52-4BF2-BA29-1ECBE66A54C9@redhat.com> Jay?s work for HWKMETRICS-420 was merged into master the other day. I think that provides what you want. The availability bucket point now has properties that report the total time (per bucket) by availability type, and these properties are: * adminDuration * downDuration * unknownDuration * upDuration * notUpDuration (which is a combination of everything other than UP) > On Jun 25, 2016, at 12:44 PM, Heiko W.Rupp wrote: > > Hey, > > is there a way to query Hawkular-metrics like this: > > "give me the distribution of availability (up, down, ..) over a given > time range" > > The result could be aggregated time per value or relative percentages - > this > does not matter. > > Heiko > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev From hrupp at redhat.com Sun Jun 26 15:59:46 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Sun, 26 Jun 2016 21:59:46 +0200 Subject: [Hawkular-dev] Avail-percentage query in metrics? In-Reply-To: <6B852775-D521-42E7-9108-71C7D0AE43D0@redhat.com> References: <6B852775-D521-42E7-9108-71C7D0AE43D0@redhat.com> Message-ID: <00DC778C-750F-4024-9682-899807C14B45@redhat.com> And another one: is there a way to RLE the list of availabilities returned? So instead of returning each raw availability point, only returning a series of ? And if I use the 'classic bucketing' - what do I get for buckets where the availability changes? Do I see when this happened? On 25 Jun 2016, at 18:44, Heiko W.Rupp wrote: > Hey, > > is there a way to query Hawkular-metrics like this: > > "give me the distribution of availability (up, down, ..) over a given > time range" > > The result could be aggregated time per value or relative percentages > - this > does not matter. > > Heiko -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht M?nchen HRB 153243 Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander From tsegismo at redhat.com Mon Jun 27 05:30:44 2016 From: tsegismo at redhat.com (Thomas Segismont) Date: Mon, 27 Jun 2016 11:30:44 +0200 Subject: [Hawkular-dev] =?utf-8?q?Can=E2=80=99t_run_inventory_hawkular-ser?= =?utf-8?q?vice?= In-Reply-To: References: <4EDC857D-B790-4034-9CC8-671BD30229C0@redhat.com> Message-ID: <64bc4379-790f-f0ac-9dc3-054addea5a82@redhat.com> For the record, for those working with ccm: ccm updateconf 'start_rpc: true' Will do just as fine as editing the generated config file. Le 21/06/2016 ? 09:54, Thomas Segismont a ?crit : > > > Le 21/06/2016 ? 08:55, Heiko W.Rupp a ?crit : >> Hi, >> >> >> On 21 Jun 2016, at 5:49, Austin Kuo wrote: >> >>> I started a cassandra cluster with: >>>> ccm create test -v 2.2.6 -n 1 -s && ccm start test >> >> I think you could use v 3.7 of Cassandra. > > Correct. > >> >>> 15 with message: Could not instantiate implementation: >>> com.thinkaurelius.titan.diskstorage.cassandra.thrift.CassandraThriftStoreManager. >>> >> >> You need to enable RPC >> >> either via setting the env variable of CASSANDRA_START_RPC to true >> >> or by editing cassandra.yml and setting it there: >> >> # Whether to start the thrift rpc server. >> start_rpc: true > > Given your cluster is named "test", the file would be: > ~/.ccm/test/node1/conf/cassandra.yaml > >> >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> > -- Thomas Segismont JBoss ON Engineering Team From hrupp at redhat.com Mon Jun 27 10:26:38 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Mon, 27 Jun 2016 16:26:38 +0200 Subject: [Hawkular-dev] Want to try hawkular-services via Docker? In-Reply-To: References: <27E77FC8-F395-4AF8-B53C-F83A2D9C4359@redhat.com> Message-ID: Hi Anton, On 23 Jun 2016, at 20:53, Anton wrote: > Can you tell me, once running - what is the url to login? Sorry, this took me a while to respond. I put my current setup into a blog post: http://pilhuhn.blogspot.com/2016/06/using-hawkular-services-via-docker.html basically you would access the server at localhost:8080 - but this has no UI, which is what may be confusing. You can use HawkFx (https://github.com/pilhuhn/hawkfx) to browse through the available data. Or curl :) I hope that helps Heiko > > Thanks > > On Tue, Jun 21, 2016 at 12:31 PM, Heiko W.Rupp > wrote: > >> >> If you want to give it a try you can save the following >> into a file docker-compose.yml >> and then run docker-compose up hawkular >> This image has the -Pdev user jdoe/password. >> >> hawkular: >> image: "pilhuhn/hawkular-services:latest" >> ports: >> - "8080:8080" >> - "8443:8443" >> - "9990:9990" >> volumes: >> - /tmp/opt/hawkular/data:/opt/data >> links: >> - myCassandra >> environment: >> - HAWKULAR_BACKEND=remote >> - CASSANDRA_NODES=myCassandra >> myCassandra: >> image: cassandra:3.7 >> environment: >> - CASSANDRA_START_RPC=true >> volumes: >> - /tmp/opt/hawkular/cassandra:/var/lib/cassandra >> >> >> -- >> Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, >> Werner-von-Siemens-Ring 14, D-85630 Grasbrunn >> Handelsregister: Amtsgericht M?nchen HRB 153243 >> Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael >> O'Neill, >> Eric Shander >> _______________________________________________ >> hawkular-dev mailing list >> hawkular-dev at lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/hawkular-dev >> > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht M?nchen HRB 153243 Gesch?ftsf?hrer: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric Shander From snegrea at redhat.com Mon Jun 27 10:37:09 2016 From: snegrea at redhat.com (Stefan Negrea) Date: Mon, 27 Jun 2016 09:37:09 -0500 Subject: [Hawkular-dev] hawkular metrics schema upgrade bug In-Reply-To: References: Message-ID: Is it possible to backport the fix to 0.15.0 and/or 0.16.0 branches too? Thank you, Stefan Negrea Software Engineer On Sat, Jun 25, 2016 at 10:20 AM, John Sanda wrote: > New schema change management code was introduced in hawkular-metrics > 0.15.0. There were some bugs that break upgrades. Upgrading with 0.15.0 and > 0.16.0 will not work. A few people have run into this. I have already > submitted a PR with the fixes to be included in the next release. The > ticket for this is https://issues.jboss.org/browse/HWKMETRICS-425. > > - John > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160627/44ef3397/attachment.html From hrupp at redhat.com Mon Jun 27 10:43:43 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Mon, 27 Jun 2016 16:43:43 +0200 Subject: [Hawkular-dev] Avail-percentage query in metrics? In-Reply-To: <734D1718-3E52-4BF2-BA29-1ECBE66A54C9@redhat.com> References: <6B852775-D521-42E7-9108-71C7D0AE43D0@redhat.com> <734D1718-3E52-4BF2-BA29-1ECBE66A54C9@redhat.com> Message-ID: On 26 Jun 2016, at 13:31, John Sanda wrote: > Jay?s work for HWKMETRICS-420 was merged into master the other day. > I think that provides what you want. The availability bucket point now > has properties that report the total time (per bucket) by availability > type, and these properties are: > > * adminDuration > * downDuration > * unknownDuration > * upDuration > * notUpDuration (which is a combination of everything other than UP) That's interesting -thanks From gbrown at redhat.com Mon Jun 27 11:07:21 2016 From: gbrown at redhat.com (Gary Brown) Date: Mon, 27 Jun 2016 11:07:21 -0400 (EDT) Subject: [Hawkular-dev] Hawkular APM (formerly BTM) version 0.9.0.Final released In-Reply-To: <2024513403.1748107.1467039825707.JavaMail.zimbra@redhat.com> Message-ID: <1040235158.1749420.1467040041209.JavaMail.zimbra@redhat.com> Hi I'm pleased to announce that Hawkular APM 0.9.0.Final has been released. The main purpose of this release is the rename of the project from BTM (Business Transaction Management) to APM (Application Performance Management), to reflect the wider scope of the project's capabilities. This is the first release under the new project name, and consequently there are a number of naming related changes (e.g. REST endpoints, Java package/class names, model, etc) that mean this release is not backward compatible with the previous release. The details of the release can be found here: https://github.com/hawkular/hawkular-apm/releases/tag/0.9.0.Final As part of this release, we have also moved the documentation for the project to gitbook: https://hawkular.gitbooks.io/hawkular-apm-user-guide/content/ Regards Gary From anuj1708 at gmail.com Tue Jun 28 04:30:24 2016 From: anuj1708 at gmail.com (Anuj Garg) Date: Tue, 28 Jun 2016 14:00:24 +0530 Subject: [Hawkular-dev] Update on Hawkular android client Message-ID: Hello Guys, I am back to tell what is new going on in Android client of Hawkular - Old metrics related classes modified to adjust metric from explorer - Metric data is now fetched in terms of buckets - Metric chart fragment now contain list to choose time limits - Some other beutififation related to axis lables Last but not the least Aerogear Pipe for android is modified to handle special symbols in path param of REST call. As always there is a visual video to enjoy the progress https://drive.google.com/file/d/0B8tYKC1-UERHWVluZDlkSUN5eG8/view?usp=sharing What is next :- - Most changes are added to only Gauge type at present and will be extended to others after acceptace Thanks Anuj Garg -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160628/7fb01d81/attachment.html From hrupp at redhat.com Tue Jun 28 04:41:45 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 28 Jun 2016 10:41:45 +0200 Subject: [Hawkular-dev] Update on Hawkular android client In-Reply-To: References: Message-ID: <18E61FE3-D9E5-4D0A-BAC9-58D2002E852C@redhat.com> Hey Anuj, > https://drive.google.com/file/d/0B8tYKC1-UERHWVluZDlkSUN5eG8/view?usp=sharing > Great! I think it would be good to display the name of the metric (resource+metric?) at the top of the screen with the graph. Heiko From anuj1708 at gmail.com Tue Jun 28 04:44:56 2016 From: anuj1708 at gmail.com (Anuj Garg) Date: Tue, 28 Jun 2016 14:14:56 +0530 Subject: [Hawkular-dev] Update on Hawkular android client In-Reply-To: <18E61FE3-D9E5-4D0A-BAC9-58D2002E852C@redhat.com> References: <18E61FE3-D9E5-4D0A-BAC9-58D2002E852C@redhat.com> Message-ID: Thats true, I am adjusting it :) Anuj Garg -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160628/744340ee/attachment-0001.html From gbrown at redhat.com Tue Jun 28 05:14:22 2016 From: gbrown at redhat.com (Gary Brown) Date: Tue, 28 Jun 2016 05:14:22 -0400 (EDT) Subject: [Hawkular-dev] PR review request: https://github.com/hawkular/hawkular-apm/pull/463 In-Reply-To: <1258866462.2143894.1467105073597.JavaMail.zimbra@redhat.com> Message-ID: <103033863.2144823.1467105262293.JavaMail.zimbra@redhat.com> Hi In the client (instrumented) environment, Hawkular APM uses the ServiceLoader to obtain implementations for various components. This enhancement introduces a 'ServiceStatus' check, to determine whether an implementation is suitable to be returned (i.e. has all the config it needs). This will enable the client to be packaged with multiple implementations of a particular interface, and enable selection of the appropriate impl at runtime based on the configuration (e.g. environment variables). Regards Gary From ploffay at redhat.com Tue Jun 28 08:44:04 2016 From: ploffay at redhat.com (Pavol Loffay) Date: Tue, 28 Jun 2016 14:44:04 +0200 Subject: [Hawkular-dev] Master's thesis: Alert Prediction in Metric Data Based on Time Series Analysis Message-ID: Hello, yesterday I successfully defended my thesis [1]. I would like to thank to everyone from Hawkular team who helped me with the problems I was facing. Last but not least I would like to thank to company Red Hat for the opportunity to work on this project. [1]: https://is.muni.cz/auth/th/374115?lang=en Pavol -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160628/f59533a3/attachment.html From gbrown at redhat.com Tue Jun 28 08:46:20 2016 From: gbrown at redhat.com (Gary Brown) Date: Tue, 28 Jun 2016 08:46:20 -0400 (EDT) Subject: [Hawkular-dev] Master's thesis: Alert Prediction in Metric Data Based on Time Series Analysis In-Reply-To: References: Message-ID: <132512084.2202316.1467117980561.JavaMail.zimbra@redhat.com> Congratulations Pavol! Now you can have a well deserved rest :) Regards Gary ----- Original Message ----- > Hello, > > yesterday I successfully defended my thesis [1]. I would like to thank to > everyone from Hawkular team who helped me with the problems I was facing. > Last but not least I would like to thank to company Red Hat for the > opportunity to work on this project. > > [1]: https://is . muni . cz / auth / th /374115? lang =en > > Pavol > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From lponce at redhat.com Tue Jun 28 08:52:16 2016 From: lponce at redhat.com (Lucas Ponce) Date: Tue, 28 Jun 2016 08:52:16 -0400 (EDT) Subject: [Hawkular-dev] Master's thesis: Alert Prediction in Metric Data Based on Time Series Analysis In-Reply-To: References: Message-ID: <241378302.431608.1467118336653.JavaMail.zimbra@redhat.com> Congrats Pavol ! A great milestone on your career. ----- Mensaje original ----- > De: "Pavol Loffay" > Para: "Discussions around Hawkular development" > Enviados: Martes, 28 de Junio 2016 14:44:04 > Asunto: [Hawkular-dev] Master's thesis: Alert Prediction in Metric Data Based on Time Series Analysis > > Hello, > > yesterday I successfully defended my thesis [1]. I would like to thank to > everyone from Hawkular team who helped me with the problems I was facing. > Last but not least I would like to thank to company Red Hat for the > opportunity to work on this project. > > [1]: https://is . muni . cz / auth / th /374115? lang =en > > Pavol > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > From hrupp at redhat.com Tue Jun 28 09:02:21 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 28 Jun 2016 15:02:21 +0200 Subject: [Hawkular-dev] Master's thesis: Alert Prediction in Metric Data Based on Time Series Analysis In-Reply-To: References: Message-ID: <649465AF-F10B-428A-9BDB-C7279FB119AB@redhat.com> On 28 Jun 2016, at 14:44, Pavol Loffay wrote: > yesterday I successfully defended my thesis [1]. I would like to thank Yay, Awesome, Congrats! From hrupp at redhat.com Tue Jun 28 10:34:19 2016 From: hrupp at redhat.com (Heiko W.Rupp) Date: Tue, 28 Jun 2016 16:34:19 +0200 Subject: [Hawkular-dev] Hawkular-services 0.0.4 released Message-ID: <3C271CFD-4E25-4509-9D9D-9980FBB6A57E@redhat.com> Hi, hawkular-services 0.0.4 has been released Notable changes are: - bump agent to 0.19.2 - retry talking to the server until connection succeeds - 'Hostname' property of server has been brought back - Hawkular-metrics updated to master from yesterday evening - HWKMETRICS-420 Add ADMIN AvailabilityType - HWKMETRICS-393 endpoints for fetching raw data for multiple metrics You can find the release .zip at: https://github.com/hawkular/hawkular-services/releases/tag/0.0.4.Final Thanks for Stefan helping me with the bits. I have made docker images for this and a wildfly with included hawkular-agent 0.19.2 available. See http://pilhuhn.blogspot.de/2016/06/using-hawkular-services-via-docker.html From ploffay at redhat.com Tue Jun 28 10:46:05 2016 From: ploffay at redhat.com (Pavol Loffay) Date: Tue, 28 Jun 2016 16:46:05 +0200 Subject: [Hawkular-dev] Master's thesis: Alert Prediction in Metric Data Based on Time Series Analysis In-Reply-To: <649465AF-F10B-428A-9BDB-C7279FB119AB@redhat.com> References: <649465AF-F10B-428A-9BDB-C7279FB119AB@redhat.com> Message-ID: Thanks, I realized that the link is not working. Here is the correct one https://is. muni.cz/th/374115?lang=en On Tue, Jun 28, 2016 at 3:02 PM, Heiko W.Rupp wrote: > On 28 Jun 2016, at 14:44, Pavol Loffay wrote: > > > yesterday I successfully defended my thesis [1]. I would like to thank > > Yay, Awesome, Congrats! > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160628/2a64decb/attachment.html From mithomps at redhat.com Tue Jun 28 10:52:17 2016 From: mithomps at redhat.com (mike thompson) Date: Tue, 28 Jun 2016 07:52:17 -0700 Subject: [Hawkular-dev] Master's thesis: Alert Prediction in Metric Data Based on Time Series Analysis In-Reply-To: References: Message-ID: <44136DFB-CC52-44D9-938B-81B12B259451@redhat.com> Congrats Pavol. Great Work! > On 28 Jun 2016, at 05:44, Pavol Loffay wrote: > > Hello, > > yesterday I successfully defended my thesis [1]. I would like to thank to everyone from Hawkular team who helped me with the problems I was facing. Last but not least I would like to thank to company Red Hat for the opportunity to work on this project. > > [1]: https://is .muni.cz/auth/th/374115?lang=en > > Pavol > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160628/0886826d/attachment.html From tsegismo at redhat.com Wed Jun 29 04:53:00 2016 From: tsegismo at redhat.com (Thomas Segismont) Date: Wed, 29 Jun 2016 10:53:00 +0200 Subject: [Hawkular-dev] Master's thesis: Alert Prediction in Metric Data Based on Time Series Analysis In-Reply-To: References: <649465AF-F10B-428A-9BDB-C7279FB119AB@redhat.com> Message-ID: <582738e7-8281-e4ab-1062-e28af744b173@redhat.com> Congrats Pavol! Le 28/06/2016 ? 16:46, Pavol Loffay a ?crit : > Thanks, > > I realized that the link is not working. Here is the correct > one https://is.muni.cz/th/374115?lang=en > > > On Tue, Jun 28, 2016 at 3:02 PM, Heiko W.Rupp > wrote: > > On 28 Jun 2016, at 14:44, Pavol Loffay wrote: > > > yesterday I successfully defended my thesis [1]. I would like to thank > > Yay, Awesome, Congrats! > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -- Thomas Segismont JBoss ON Engineering Team From tsegismo at redhat.com Wed Jun 29 08:39:27 2016 From: tsegismo at redhat.com (Thomas Segismont) Date: Wed, 29 Jun 2016 14:39:27 +0200 Subject: [Hawkular-dev] Sync with Inventory In-Reply-To: <37609601.21BcKnHFje@rpi.lan> References: <6b0e30d4-bb89-1062-427b-dcb4a53275b6@redhat.com> <37609601.21BcKnHFje@rpi.lan> Message-ID: <8a239b8f-8f4f-e2c4-9dab-791110dd22a1@redhat.com> Thank you very much for the thorough reply Lukas. A few questions/comments inline. Le 23/06/2016 ? 15:59, Lukas Krejci a ?crit : > On Thursday, June 23, 2016 10:27:12 AM Thomas Segismont wrote: >> Hey Lukas, >> >> Thank you for pointing us in the sync endpoint. Austin will look into >> this and will certainly come back with more questions. >> >> With respect to the user creating resources question, the difference >> between Vert.x and Wildfly is that the user creates resources >> grammatically. So in version 1 of the application, there might be two >> HTTP servers as well as 7 event bus handlers, but only 1 http server in >> version 2. And a named worker pool in version 3. >> >> In the end, I believe it doesn't matter if it's container which creates >> resources or if it's the user himself. Does it? >> > > It does not really (inventory has just a single API, so it does not really > know who is talking to it - if a feed or if a user) - but resources inside and > outside feeds have slightly different semantics. > > Right now the logic is this: > > Feeds are "agents" that don't care about anything else but their own little > "world". That's why they can create their own resource types, metric types and > they also declare resources and metrics of those types. Feed does not need to > look "outside" of its own data and is in full charge of it. Does that mean that creating a feed is the only way to create resource/metric types? I suppose the benefit of creating resource types is that then you can search for different resources of the same type easily. And if feeds create resource types, how do you know that resource types created by the Hawkular Agent feed running on server A are the same as those created by another agent running on server B? > > Hence the /sync endpoint applies to a feed nicely - since it is in charge, it > merely declares what is the view it has currently of the "world" it sees and > inventory will make sure it has the same picture - under that feed. > > Now if you have an application that spans multiple vms/machines and is > composed of multiple processes, there is no such clear distinction of > "ownership". Good point, Vert.x applications are often distributed and communicating over the EventBus. > > While indeed a "real" user can just act like a feed, the envisioned workflow > is that the user operates directly in environments and at the top level. I.e. > a user assigns feeds to environments (i.e. this feed reports on my server in > staging environment, etc) and the user creates "logical" resources in the > environment (i.e. "My App" resource in staging env is composed of a load > balancer managed by this feed, mongodb managed by another feed there and > clustered wflys there, there and there). > > To model this, inventory supports 2 kinds of tree hierarchies - 1 created > using the "contains" relationship, which expresses existential ownership - > i.e. a feed contains its resources and if a feed disappears, so do the > resources, because no one else can report on them. The entities bound by the How does a feed "disappear"? That would be by deleting it through the REST API, correct? Something the ManageIQ provider would do through the Ruby client? > contains relationship form a tree - no loops or diamonds in it (this is > enforced by inventory). But there can also be a hierarchy created using an > "isParentOf" relationship (which represents "logical" ownership). Resources > bound by "isParentOf" can form an acyclic graph - i.e. 1 resource can have > multiple parents as well as many children (isParentOf is applicable only to > resources, not other types of entities). > > The hierarchies formed by "contains" and "isParentOf" are independent. So you > can create a resource "My App" in the staging environment and declare it a > parent (using "isParentOf") of the resources declared by feeds that manage the > machines where the constituent servers live. Interesting, that may be the way to model a Vert.x app deployed on two machines. Each process would have its own feed reporting discovered resources (http servers, event bus handlers, ... etc), and a logical app resource as parent. > > That is the envisaged workflow for "apps". Now the downside to that is that > (currently) there is no "sync" for that. The reason is that the application > really is a logical concept and the underlying servers can be repurposed to > serve different applications (so if app stops using it, it shouldn't really > disappear from inventory, as is the case with /sync - because if a feed > doesn't "see" a resource, then it really is just gone, because the feed is > solely responsible for reporting on it). What happens to the resources exactly? Are they marked as gone or simply deleted? Do you know how dependent services are updated? For example, when a JMS queue is gone, are alert definitions on queue depth removed as well? How does that happen? > > We can think about how to somehow help clients with "App sync" but I'm not > sure if having a feed for vertx is the right thing to do. On the other hand I > very well may not be seeing some obvious problems of the above or parallels > that make the 2 approaches really the same because the above model is just > ingrained in my brain after so many hours thinking about it ;) > >> As for the feed question, the Vert.x feed will be the Metrics SPI >> implementation (vertx-hawkular-metrics project). Again I guess it's not >> much different than the Hawkular Agent. >> > > A feed would only be appropriate if vertx app never reported on something that > would also be reported by other agents. I.e. if a part of a vertx application > is also reported on by a wfly agent, because that part is running in a wfly > server managed by us, then that will not work - 1 resource cannot be > "contained" in 2 different feeds (not just API wise, but logically, too). I'm not too worried about this use case. First the vast majority of Vert.x applications I know about are not embedded. Secondly the Vert.x feed would not report resources already reported by the Hawkular Agent. > >> Maybe the wording around user creating resources was confusing? Did you >> thought he would do so from application code? In this case, the answer >> is no. >> > > Yeah, we should probably get together and discuss what your plans are to get > on the same page with everything. I believe that presenting to you (and to whoever is interested) the conclusions of investigations would be beneficial indeed. > >> Regards, >> Thomas >> >> Le 23/06/2016 ? 10:01, Austin Kuo a ?crit : >>> Yes, I?m gonna build the inventory for vertx applications. >>> So I have to create a feed for it. >>> >>> Thanks! >>> >>> On Tue, Jun 21, 2016 at 7:55 PM Lukas Krejci >> >>> > wrote: >>> Hi Austin, >>> >>> Inventory offers a /hawkular/inventory/sync endpoint that is used to >>> synchronize the "world view" of feeds (feed being something that >>> pushes data >>> into inventory). >>> >>> You said though that a "user creates" the resources, so I am not >>> sure if /sync >>> would be applicable to your scenario. Would you please elaborate >>> more on where >>> in the inventory hierarchy you create your resources and how? I.e. >>> are you >>> using some sort of feed akin to Hawkular's Wildfly Agent or are you >>> just >>> creating your resources "manually" under environments? >>> >>> On Tuesday, June 21, 2016 02:20:33 AM Austin Kuo wrote: >>> > Hi all, >>> > >>> > I?m currently investigating how to sync with inventory server. >>> > Here?s the example scenario: >>> > Consider the following problem. A user creates version 1 of the >>> >>> app with >>> >>> > two http servers, one listening on port 8080, the other on port >>> >>> 8181. In >>> >>> > version 2, the http server listening on port 8181 is no longer >>> > needed. >>> > When the old version is stopped and the new version started, there >>> >>> will be >>> >>> > just one http server listening. The application is not aware of the >>> > previous state. What should we do so that the second http server >>> >>> is removed >>> >>> > from Inventory? >>> > >>> > Thanks in advance. >>> >>> -- >>> Lukas Krejci >>> >>> _______________________________________________ >>> hawkular-dev mailing list >>> hawkular-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev >>> >>> _______________________________________________ >>> hawkular-dev mailing list >>> hawkular-dev at lists.jboss.org >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev > -- Thomas Segismont JBoss ON Engineering Team From lkrejci at redhat.com Wed Jun 29 09:20:32 2016 From: lkrejci at redhat.com (Lukas Krejci) Date: Wed, 29 Jun 2016 15:20:32 +0200 Subject: [Hawkular-dev] Sync with Inventory In-Reply-To: <8a239b8f-8f4f-e2c4-9dab-791110dd22a1@redhat.com> References: <37609601.21BcKnHFje@rpi.lan> <8a239b8f-8f4f-e2c4-9dab-791110dd22a1@redhat.com> Message-ID: <1652727.ThqZrOltYD@rpi.lan> Btw. I've slightly updated the inventory organization description on the hawkular site (http://www.hawkular.org/docs/components/inventory/ index.html#inventory-organization). I hope it explains the structure and intent of the entities in inventory in a slightly more comprehensible manner. My answers are inline below... On st?eda 29. ?ervna 2016 14:39:27 CEST Thomas Segismont wrote: > Thank you very much for the thorough reply Lukas. A few > questions/comments inline. > > Le 23/06/2016 ? 15:59, Lukas Krejci a ?crit : > > On Thursday, June 23, 2016 10:27:12 AM Thomas Segismont wrote: > >> Hey Lukas, > >> > >> Thank you for pointing us in the sync endpoint. Austin will look into > >> this and will certainly come back with more questions. > >> > >> With respect to the user creating resources question, the difference > >> between Vert.x and Wildfly is that the user creates resources > >> grammatically. So in version 1 of the application, there might be two > >> HTTP servers as well as 7 event bus handlers, but only 1 http server in > >> version 2. And a named worker pool in version 3. > >> > >> In the end, I believe it doesn't matter if it's container which creates > >> resources or if it's the user himself. Does it? > > > > It does not really (inventory has just a single API, so it does not really > > know who is talking to it - if a feed or if a user) - but resources inside > > and outside feeds have slightly different semantics. > > > > Right now the logic is this: > > > > Feeds are "agents" that don't care about anything else but their own > > little > > "world". That's why they can create their own resource types, metric types > > and they also declare resources and metrics of those types. Feed does not > > need to look "outside" of its own data and is in full charge of it. > > Does that mean that creating a feed is the only way to create > resource/metric types? No, you can also create resource types and metric types directly under the tenant. > I suppose the benefit of creating resource types is that then you can > search for different resources of the same type easily. > > And if feeds create resource types, how do you know that resource types > created by the Hawkular Agent feed running on server A are the same as > those created by another agent running on server B? > Inventory automatically computes "identity hashes" of resource types and metric types - if 2 resource types in 2 feeds have the same ID and exactly the same configuration definitions, they are considered identical. If you know 1 resource type, you can find all the identical ones using the following REST API (since 0.17.0.Final, the format of the URLs is thoroughly explained here: http://www.hawkular.org/docs/rest/rest-inventory.html#_api_endpoints): /hawkular/inventory/traversal/f;feedId/rt;resourceTypeId/identical If for example some resource types should be known up-front and "shared" across all feeds, some kind of "gluecode" could create "global" resource types under the tenant, that would have the same id and structure as the types that the feeds declare. If then you want to for example find all resources of given type, you can: /hawkular/inventory/traversal/rt;myType/identical/rl;defines/type=resource I.e. for all types identical to the global one, find all resources defined by those types. > > Hence the /sync endpoint applies to a feed nicely - since it is in charge, > > it merely declares what is the view it has currently of the "world" it > > sees and inventory will make sure it has the same picture - under that > > feed. > > > > Now if you have an application that spans multiple vms/machines and is > > composed of multiple processes, there is no such clear distinction of > > "ownership". > > Good point, Vert.x applications are often distributed and communicating > over the EventBus. > > > While indeed a "real" user can just act like a feed, the envisioned > > workflow is that the user operates directly in environments and at the > > top level. I.e. a user assigns feeds to environments (i.e. this feed > > reports on my server in staging environment, etc) and the user creates > > "logical" resources in the environment (i.e. "My App" resource in staging > > env is composed of a load balancer managed by this feed, mongodb managed > > by another feed there and clustered wflys there, there and there). > > > > To model this, inventory supports 2 kinds of tree hierarchies - 1 created > > using the "contains" relationship, which expresses existential ownership - > > i.e. a feed contains its resources and if a feed disappears, so do the > > resources, because no one else can report on them. The entities bound by > > the > How does a feed "disappear"? That would be by deleting it through the > REST API, correct? Something the ManageIQ provider would do through the > Ruby client? > yes > > contains relationship form a tree - no loops or diamonds in it (this is > > enforced by inventory). But there can also be a hierarchy created using an > > "isParentOf" relationship (which represents "logical" ownership). > > Resources > > bound by "isParentOf" can form an acyclic graph - i.e. 1 resource can have > > multiple parents as well as many children (isParentOf is applicable only > > to > > resources, not other types of entities). > > > > The hierarchies formed by "contains" and "isParentOf" are independent. So > > you can create a resource "My App" in the staging environment and declare > > it a parent (using "isParentOf") of the resources declared by feeds that > > manage the machines where the constituent servers live. > > Interesting, that may be the way to model a Vert.x app deployed on two > machines. Each process would have its own feed reporting discovered > resources (http servers, event bus handlers, ... etc), and a logical app > resource as parent. > Exactly. > > That is the envisaged workflow for "apps". Now the downside to that is > > that > > (currently) there is no "sync" for that. The reason is that the > > application > > really is a logical concept and the underlying servers can be repurposed > > to > > serve different applications (so if app stops using it, it shouldn't > > really > > disappear from inventory, as is the case with /sync - because if a feed > > doesn't "see" a resource, then it really is just gone, because the feed is > > solely responsible for reporting on it). > > What happens to the resources exactly? Are they marked as gone or simply > deleted? Right now they are deleted. That is of course not optimal and versioning is in the pipeline right after the port of inventory to Tinkerpop3. Basically all the entities and relationships will get "from" and "to" timestamps. Implicitly, you'd look at the "present", but you'd be able to look at how things looked in the past by specifying a different "now" in your query. > Do you know how dependent services are updated? For example, when a JMS > queue is gone, are alert definitions on queue depth removed as well? How > does that happen? > Inventory sends events on the bus about every C/U/D of every entity or relationship, so other components can react on that. > > We can think about how to somehow help clients with "App sync" but I'm not > > sure if having a feed for vertx is the right thing to do. On the other > > hand I very well may not be seeing some obvious problems of the above or > > parallels that make the 2 approaches really the same because the above > > model is just ingrained in my brain after so many hours thinking about it > > ;) > > > >> As for the feed question, the Vert.x feed will be the Metrics SPI > >> implementation (vertx-hawkular-metrics project). Again I guess it's not > >> much different than the Hawkular Agent. > > > > A feed would only be appropriate if vertx app never reported on something > > that would also be reported by other agents. I.e. if a part of a vertx > > application is also reported on by a wfly agent, because that part is > > running in a wfly server managed by us, then that will not work - 1 > > resource cannot be "contained" in 2 different feeds (not just API wise, > > but logically, too). > I'm not too worried about this use case. First the vast majority of > Vert.x applications I know about are not embedded. Secondly the Vert.x > feed would not report resources already reported by the Hawkular Agent. > > >> Maybe the wording around user creating resources was confusing? Did you > >> thought he would do so from application code? In this case, the answer > >> is no. > > > > Yeah, we should probably get together and discuss what your plans are to > > get on the same page with everything. > > I believe that presenting to you (and to whoever is interested) the > conclusions of investigations would be beneficial indeed. > +1 > >> Regards, > >> Thomas > >> > >> Le 23/06/2016 ? 10:01, Austin Kuo a ?crit : > >>> Yes, I?m gonna build the inventory for vertx applications. > >>> So I have to create a feed for it. > >>> > >>> Thanks! > >>> > >>> On Tue, Jun 21, 2016 at 7:55 PM Lukas Krejci >>> > >>> > wrote: > >>> Hi Austin, > >>> > >>> Inventory offers a /hawkular/inventory/sync endpoint that is used to > >>> synchronize the "world view" of feeds (feed being something that > >>> pushes data > >>> into inventory). > >>> > >>> You said though that a "user creates" the resources, so I am not > >>> sure if /sync > >>> would be applicable to your scenario. Would you please elaborate > >>> more on where > >>> in the inventory hierarchy you create your resources and how? I.e. > >>> are you > >>> using some sort of feed akin to Hawkular's Wildfly Agent or are you > >>> just > >>> creating your resources "manually" under environments? > >>> > >>> On Tuesday, June 21, 2016 02:20:33 AM Austin Kuo wrote: > >>> > Hi all, > >>> > > >>> > I?m currently investigating how to sync with inventory server. > >>> > Here?s the example scenario: > >>> > Consider the following problem. A user creates version 1 of the > >>> > >>> app with > >>> > >>> > two http servers, one listening on port 8080, the other on port > >>> > >>> 8181. In > >>> > >>> > version 2, the http server listening on port 8181 is no longer > >>> > needed. > >>> > When the old version is stopped and the new version started, there > >>> > >>> will be > >>> > >>> > just one http server listening. The application is not aware of > >>> > the > >>> > previous state. What should we do so that the second http server > >>> > >>> is removed > >>> > >>> > from Inventory? > >>> > > >>> > Thanks in advance. > >>> > >>> -- > >>> Lukas Krejci > >>> > >>> _______________________________________________ > >>> hawkular-dev mailing list > >>> hawkular-dev at lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev > >>> > >>> _______________________________________________ > >>> hawkular-dev mailing list > >>> hawkular-dev at lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/hawkular-dev -- Lukas Krejci From mazz at redhat.com Wed Jun 29 09:44:42 2016 From: mazz at redhat.com (John Mazzitelli) Date: Wed, 29 Jun 2016 09:44:42 -0400 (EDT) Subject: [Hawkular-dev] inventory/deprecated not so easy to use In-Reply-To: <1812400653.727219.1467207462729.JavaMail.zimbra@redhat.com> Message-ID: <365206528.728964.1467207882421.JavaMail.zimbra@redhat.com> From: http://www.hawkular.org/docs/rest/rest-inventory.html#_api_endpoints "The old API has been kept so that clients can gradually move to the new API, but the old API has moved from /hawkular/inventory to /hawkular/inventory/deprecated. The clients using the old API will have to be modified to use the new endpoint but are otherwise unaffected." This isn't exactly true. Not ALL the API from <0.17.0.Final is there at /deprecated - if I'm using some of the old API I have to modify the code, but not all. Jay tried using the old agent with the new inventory, and he switched the inventory context from "hawkular/inventory" to "hawkular/inventory/deprecated" (there is a inventory-context attribute on in the agent config for just such an emergency - just a change to the standalone.xml setting). However, it failed because the "/bulk" API isn't available under /deprecated. So if anyone has a client that wants to talk to the old inventory, they need to know WHICH API was deprecated (feeds/ deprecated, bulk/ was not) and ONLY change those calls to use the /deprecated URL (e.g. change the code to use /entity/feed, but leaving /bulk alone). Which kinda sucks because now you have to pinpoint what calls need to change in the code and change code - when it would be much easier to simply be able to change a configuration setting and not have to change or recompile/build any code - you can just use the old client as is with the config change. In other words, if I have an inventory client wants to use the old inventory API, it should switch to "/deprecated" URL and expect it all to work as before. From lkrejci at redhat.com Wed Jun 29 10:00:28 2016 From: lkrejci at redhat.com (Lukas Krejci) Date: Wed, 29 Jun 2016 16:00:28 +0200 Subject: [Hawkular-dev] inventory/deprecated not so easy to use In-Reply-To: <365206528.728964.1467207882421.JavaMail.zimbra@redhat.com> References: <365206528.728964.1467207882421.JavaMail.zimbra@redhat.com> Message-ID: <4934966.p2u0uu3spW@rpi.lan> Crap, I thought I did redirect even those I haven't deprecated... Let me look at that and release 0.17.1... Sorry for the confusion... On st?eda 29. ?ervna 2016 9:44:42 CEST John Mazzitelli wrote: > From: http://www.hawkular.org/docs/rest/rest-inventory.html#_api_endpoints > > "The old API has been kept so that clients can gradually move to the new > API, but the old API has moved from /hawkular/inventory to > /hawkular/inventory/deprecated. The clients using the old API will have to > be modified to use the new endpoint but are otherwise unaffected." > > This isn't exactly true. Not ALL the API from <0.17.0.Final is there at > /deprecated - if I'm using some of the old API I have to modify the code, > but not all. > > Jay tried using the old agent with the new inventory, and he switched the > inventory context from "hawkular/inventory" to > "hawkular/inventory/deprecated" (there is a inventory-context attribute on > in the agent config for just such an emergency - just a > change to the standalone.xml setting). > > However, it failed because the "/bulk" API isn't available under > /deprecated. So if anyone has a client that wants to talk to the old > inventory, they need to know WHICH API was deprecated (feeds/ deprecated, > bulk/ was not) and ONLY change those calls to use the /deprecated URL (e.g. > change the code to use /entity/feed, but leaving /bulk alone). Which kinda > sucks because now you have to pinpoint what calls need to change in the > code and change code - when it would be much easier to simply be able to > change a configuration setting and not have to change or recompile/build > any code - you can just use the old client as is with the config change. > > In other words, if I have an inventory client wants to use the old inventory > API, it should switch to "/deprecated" URL and expect it all to work as > before. _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev -- Lukas Krejci From jkremser at redhat.com Wed Jun 29 16:47:48 2016 From: jkremser at redhat.com (Jiri Kremser) Date: Wed, 29 Jun 2016 22:47:48 +0200 Subject: [Hawkular-dev] Master's thesis: Alert Prediction in Metric Data Based on Time Series Analysis In-Reply-To: <582738e7-8281-e4ab-1062-e28af744b173@redhat.com> References: <649465AF-F10B-428A-9BDB-C7279FB119AB@redhat.com> <582738e7-8281-e4ab-1062-e28af744b173@redhat.com> Message-ID: Congratulations, the A was well deserved. jk On Wed, Jun 29, 2016 at 10:53 AM, Thomas Segismont wrote: > Congrats Pavol! > > Le 28/06/2016 ? 16:46, Pavol Loffay a ?crit : > > Thanks, > > > > I realized that the link is not working. Here is the correct > > one https://is.muni.cz/th/374115?lang=en > > > > > > On Tue, Jun 28, 2016 at 3:02 PM, Heiko W.Rupp > > wrote: > > > > On 28 Jun 2016, at 14:44, Pavol Loffay wrote: > > > > > yesterday I successfully defended my thesis [1]. I would like to > thank > > > > Yay, Awesome, Congrats! > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > > > > > > > _______________________________________________ > > hawkular-dev mailing list > > hawkular-dev at lists.jboss.org > > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > > > -- > Thomas Segismont > JBoss ON Engineering Team > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160629/7f4e4bc0/attachment.html From miburman at redhat.com Thu Jun 30 09:46:13 2016 From: miburman at redhat.com (Michael Burman) Date: Thu, 30 Jun 2016 09:46:13 -0400 (EDT) Subject: [Hawkular-dev] Metrics and use of metrics_idx In-Reply-To: <2031761900.4108094.1467293089854.JavaMail.zimbra@redhat.com> Message-ID: <1961450804.4126707.1467294373087.JavaMail.zimbra@redhat.com> Hi, This sparked my interest after the discussions in PR #523 (adding cache to avoid metrics_idx writes). Stefan commented that he still wants to write to this table to keep metrics available instantly, jsanda wants to write them asynchronously. Maybe we should instead just stop writing there? Why? We do the same thing in tenants also at this time, we don't write there if someone writes a metric to a new tenant. We fetch the partition keys from metrics_idx table. Now, the same ideology could be applied to the metrics_idx writing, read the partition keys from data. There's a small performance penalty, but the main thing is that we don't really need that information often - in most use cases never. If we want to search something with for example tags, we search it with tags - that metricId has been manually added to the metrics_idx table. No need to know if there's metrics which were not initialized. This should be the preferred way of doing things in any case - use tags instead of pushing metadata to the metricId. If we need to find out if id exists, fetching that from the PK (PartitionKey) index is fast. The only place where we could slow down is if there's lots of tenants with lots of metricIds each and we want to fetch all the metricIds of a single tenant. In that case the fetching of definitions could slow down. How often do users fetch all the tenant metricIds without any filtering? And how performance critical is this sort of behavior? And what use case does list of ids serve (without any information associated to them) ? If you need to fetch datapoints from a known metricId, there's no need for metrics_idx table writing or reading. So this index writing only applies to listing metrics. - Micke From theute at redhat.com Thu Jun 30 21:39:29 2016 From: theute at redhat.com (Thomas Heute) Date: Fri, 1 Jul 2016 03:39:29 +0200 Subject: [Hawkular-dev] Master's thesis: Alert Prediction in Metric Data Based on Time Series Analysis In-Reply-To: References: Message-ID: Congrats ! Enjoy your time off ! On Tue, Jun 28, 2016 at 2:44 PM, Pavol Loffay wrote: > Hello, > > yesterday I successfully defended my thesis [1]. I would like to thank to > everyone from Hawkular team who helped me with the problems I was facing. > Last but not least I would like to thank to company Red Hat for the > opportunity to work on this project. > > [1]: https://is.muni.cz/auth/th/374115?lang=en > > Pavol > > _______________________________________________ > hawkular-dev mailing list > hawkular-dev at lists.jboss.org > https://lists.jboss.org/mailman/listinfo/hawkular-dev > > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.jboss.org/pipermail/hawkular-dev/attachments/20160701/f7242d51/attachment.html