November 2015 - hawkular-dev - Jboss List Archives

by Juraci Paixão Kröhling

Team, TL;DR: use 1.1.1.Final for the next MS. If it breaks, use 1.0.18.Final. I'll be out for about a week and unfortunately, I was not able yet to get the PRs updating Accounts to the Cassandra version into all projects. Because of that, I decided to release 1.0.x, in case Accounts breaks something that can't be worked around during my absence. If that's the case, then please use the following version: 1.0.18.Final . It's the non-Cassandra version and should be almost the same version as the last MS. I also fixed a bug in the way that Cassandra session is handled for the secret store, and did a new release: 1.1.1.Final. This is the one that should go into the next MS (for now, at least). As this does not affect the dependent modules, I'll not be sending PRs around this time. I hope to be able to get the remaining PRs merged today. - Juca.

9 years, 1 month

1
0
0 / 0

the name of our hawkular agent/wildfly monitor/feed is confusing - I'm fixing it

by John Mazzitelli

As I'm writing code and docs and javadocs all around, I realize that the name of our "agent" is utterly confused. We need to fix this or we will eventually confuse users/customers. Right now in code, or comments, or docs, or just in talking, the names of the "agent" have been at one time or another: agent wildfly monitor wildfly hawkular feed wildfly monitor agent wildfly extension wildfly agent module wildfly agent etc. etc. etc. Over the weekend, I'm going to start renaming this so it is consistent across the board. It will be called "Hawkular WildFly Agent" This will affect maven artifact names moving forward. But we need to fix this now, because its confusing ME. I can only imagine the confusion when people start to ask "what do you call the hawkular thing that monitors Wildfly?"

9 years, 1 month

4
5
0 / 0

Discussion, Planning, and status on Testing Openshift & Hawk-Metrics Integration for Openshift 3.1

by Michael Foley

A single instance of the following meeting has been modified: Subject: Discussion, Planning, and status on Testing Openshift & Hawk-Metrics Integration for Openshift 3.1 Organizer: "Michael Foley" <mfoley(a)redhat.com> Location: Bluejeans http://www.bluejeans.com/mfoley51 Time: Wednesday, November 4, 2015, 3:00:00 PM - 3:30:00 PM GMT -05:00 US/Canada Eastern Required: pruan(a)redhat.com; mmahoney(a)redhat.com; vnguyen(a)redhat.com; snegrea(a)redhat.com; jsanda(a)redhat.com; mwringe(a)redhat.com Optional: jon-qa-list(a)redhat.com; jboss-on-team(a)redhat.com; hawkular-dev(a)lists.jboss.org *~*~*~*~*~*~*~*~*~* Hi, Let's have a discussion and planning session on testing Openshift & Hawkular Integration! Let's use this etherpad to coordinate the discussion -->> http://pad.engineering.redhat.com/Management-nextAndOpenshiftTestPlanning 5 Point Plan for Openshift 3.1 GA * Unit tests .... owned by Hawk-Metrics developers * Integration tests ... owned by Hawk-Metrics developers and Hawk-Metrics QE * Performance CI on Hawk-Metrics (this one is actually new and was not discussed on Wednesday , but I now see it makes sense) * Functional Integration tests on Hawk-Metrics latest + Openshift Origin latest * Funtional/UI .... Cucumber/Ruby tests ...owned by Openshift QE * Functional/Rest ... Cucumber/Ruby tests ... owned by Openshift QE * Performance & Scalability .... owned by Openshift QE Regards, Michael Foley QE Supervisor, Middleware BU

9 years, 1 month

1
0
0 / 0

Accounts 1.1.0.Final released

by Juraci Paixão Kröhling

Team, Alerts and BTM have requested a release of Accounts with the latest changes, so, here it is: Accounts 1.1.0.Final is now released. The bump in the version reflects the move of Accounts from using an RDBMS to Cassandra. I expect it to still have a few bugs here and there, so, there might be a 1.1.1.Final version before the next milestone. - Juca.

9 years, 1 month

1
0
0 / 0

Demo.hawkular.org Is Available

by Matthew Mahoney

FYI: While LOTE (livingontheedge.hawkular.org) continues to be down due to TravisCI build issues, http://demo.hawkular.org/ is available and is deployed with Hawkular Snapshot-6 Thanks, Matt

9 years, 1 month

1
0
0 / 0

Welcome Valerii Sorokin to JON/Hawkular QE!

by Michael Foley

Hi, Please join me in welcoming Valerii Sorokin to JON/Hawkular QE! Valerii brings a lot of experience as a software engineer, tools developer, and QE Engineer. We are very happy to have him on JON/Hawkular QE! Valerii will be contributing to areas such as: * Legacy JON patch stream * regression testing, * test automation execution * ON_QA bug verification * upgrade testing * testcase migration to Polarion * Hawkular testing * UI automation, * REST API automation, * Performance CI * Hawk-Metrics integration into Openshift * and maintaining the Continuous Delivery Pipleline for Hawkular We have a lot of work to do ...so we are very happy to have Valerii with us. Please be welcoming and helpful. Email = vsorokin(a)redhat.com . And can be found on IRC as vsorokin. Regards, Michael Foley QE Supervisor, Middleware BU

9 years, 1 month

7
6
0 / 0

Accounts on Cassandra

by Juraci Paixão Kröhling

Team, I'm moving Accounts to Cassandra, so that Hawkular won't need a RDMBS just because of it. I tried to keep backwards compatibility, but there's one part that could break your code: the models are now using UUIDs for the IDs. Previously, the IDs were strings, which were UUIDs as string by default, but your component had the freedom to specify an own ID. As far as I know, only Inventory specifies its own ID for the Resource class. It seems that Jirka is OK with changing it to UUID, but if you have any problems with that, let me know and I'll remove this requirement. Note that if all you do is consume the IDs generated by Accounts, you should *not* be affected, as all old methods are converting the UUIDs that you send as String back to UUID. Apart from that, it should be fully backwards compatible, but in any case, I'll be releasing accounts 1.0.17.Final and branching 1.0.x. Cassandra changes will be applied to 1.1.0.Final. All changes from 1.1.0.Final and on will be backported to 1.0.x *up to the next MS*. If everything goes right for the next MS, I'll stop maintaining 1.0.x. - Juca.

9 years, 1 month

2
4
0 / 0

Openshift Origin release candidate 1 is now available ....

by Michael Foley

Hi, Openshift Origin Release Candidate 1 is now available. Unfortunately, Metrics is not in this release candidate ...and will be in the next version 1.0.8, which I presume will be Release Candidate 2. So ...when Release Candidate 2 becomes available ... we will have to test extremely quickly ..as GA is scheduled for November 19th. Here's a strawman of the QE Plan: * When Openshift 3.1 Release Candidate 2 is available (I think it is November 9th ...from looking at the document from the OSE PM call) ...we need to jump right on this. * We have a 5-point QE Plan ... but with just 10 days to test ...I don't think we will make enough progress with automation in that limited amount of time. * Let's focus on a manual qualification ... * a visual inspection of the Openshift Admin Console to see if metrics from Hawk-metrics are appearing * re-execute the few testcases we have (ie, the curl command ... and visually inspect the data) * If there is an issue detected, we will need fast turnaround time from Hawk-Metrics developers. Please. * QE Deliverable is a documented testcase execution run in Polarion, and a QE Sign-off document ...so I can communicate what was done and the test results. Regards, Michael Foley QE Supervisor, Middleware QE ----- Forwarded Message ----- From: "Clayton Coleman" <ccoleman(a)redhat.com> To: "aos-devel" <aos-devel(a)redhat.com> Sent: Thursday, October 29, 2015 12:27:14 PM Subject: Re: [aos-devel] v1.0.7 is out for download (release candidate 1 for Origin 1.1) FYI On Thu, Oct 29, 2015 at 2:26 PM, Clayton Coleman <ccoleman(a)redhat.com> wrote: > v1.0.7 has been tagged, pushed to the Docker Hub, and uploaded to > GitHub. The release notes are here > https://github.com/openshift/origin/releases/tag/v1.0.7 > > This is the first release candidate for Origin 1.1. There are a ton > of new features, a massive amount of new UI, and lots of exciting new > features. > > Some features are still in the process of being merged (Jobs, > Horizontal Pod Autoscaler, Metrics, Logging) - expect to see them in > v1.0.8 > > Please note that v1beta3 is now no longer supported in the UI, and you > will need to change your master config to use a different storage > version if you are still using v1beta3 (old data will continue to > work). If you hit any issues upgrading your clusters, please let us > know!

9 years, 1 month

2
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

hawkular-dev November 2015