Hi Bruno/Gordon,
Thanks for the initial feedback. Gordon it's slightly worrying your
comment "The problem seems to stem from using the qpid jars from trunk
(or indeed it seems from 0.20 rc4)". Unfortunately to date I've only had
a chance to run it against qpidd 0.12 because as I've mentioned
previously I always had a bit of a fight getting qpidd to make on
Ubuntu. Now that I've finally got the GUI out there I'll upgrade and see
if there's any desnagging. There really should be no issues unless
someone has messed with how qpidd sends QMF messages. The biggest change
I was aware of was between 0.8 and 0.10 when QMF Events went from Map
Messages to List Messages, indeed there's actually a bit of your code in
the QMF2 implementation that does the ampq List Message deserialisation.
If someone has messed with any of that there could be some issues (I'll
also be a bit cross because it's not something that was communicated :-))
Re "The default broker has an empty URL" actually that is deliberate,
but perhaps there needs to be a way to make things more obvious. So what
happens is that on the REST side you can configure a "default" broker -
by default that will be a broker running on the same host as the REST
Server on port 5672. So when the web page loads its initial port of
call is to create a connection to the default broker (you can add
connections to different brokers too as you've probably seen). So
because it's a default that's actually controlled by the REST Server the
GUI specifies a connection URL of "" initially to mean connect me to the
default broker.
When you add a new QMF Console Connection you can specifiy whatever
connection URL you want and the idea is you can give it a memorable name.
Hope that makes sense?
You mention "I also seem to be unable to edit anything or add a qmf
connection, the text boxes for URL, connection options etc aren't
editable" That's odd. What browser are you using? The grey bit that says
guest/guest@host:10000 is just an HTML5 placeholder in a basic input
type="text" for modern browsers it uses genuine HTML5 placeholders but
for older ones I wrote a shim, but I've tested it on IE6-9 and Opera 9 -
12 and I've never has any problems. Stupid question, you did click on
the box and try typing didn't you? In all the cases I've tried the
placeholder disappears as intended and the text you want gets entered?
Do let me know if it's anything more than finger trouble and if so what
browser as I say I've tried to try this stuff out across as many
browsers as I can lay my hands on and I've never experienced the text
inputs not being editable.
Bruno's comment "the text boxes had the default values, and they only
disappear after start writing and not on focus, but it worked fine."
that's exactly it. Actually this might depend on the browser, with the
recent Firefox I'm using the placeholders disappear only after starting
typing, with a previous version they disappeared on focus on iOS6 they
only disappear after starting to type. Placeholders are quite a common
UI pattern now, sorry if they caused confusion. I had a bit of a design
goal that the app would look like a "native app" if you ran it on
something like an iPhone so (as is probably obvious) most of the styling
attempts to emulate the look and feel of that sort of app.
BTW there's no difference between the "guest" and "admin" accounts at
present, my intention is to add a permissions type thing so that not
everyone can add/delete things, but at present they are both exactly the
same - sorry should have spelled that out. I can't think of any reason
why you wouldn't be able to click on the text input and start typing.
Bruno you said "Sometimes it take some seconds" when you first log in
(from my experience anyway) or hit browser refresh it should connect
pretty quickly. The page might take a little while to load depending on
your network speed as it's a fairly big app, but once you see the
settings page if you aren't seeing a red banner saying Broker
Disconnected then it should be running fine. The stats updates are every
10 seconds, they are actually triggered by QMF events, so mostly they
get updated when the QMF heartbeat happens every 10 seconds but if you
do something like add a queue or whatever then that will trigger a
refresh too so if you look on the queues page on one browser and add a
queue on another the new queue should appear pretty much instantly. Hmm
as I say it's primarily triggered by QMF hearbeats I guess that if you
have a broker configured with --mgmt-pub-interval to something other
than the default the refresh could be affected by that..
Bruno you also say "Just make sure that you have the new connection
selected and see the Broker tab" as I said earlier you shouldn't
necessarily *have to* add and select a new connection as the GUI tries
to connect to the default url configured on the QpidRestAPI. If you're
having to explicitly create a new QMF Console Connection then my guess
is that you are running QpidRestAPI on a host that doesn't have qpidd
running and you haven't configured QpidRestAPI with an explicit default
broker it's worth doing ./QpidRestAPI -h
-a <address>, --broker-addr=<address>
broker-addr is in the form: [username/password@]
hostname | ip-address [:<port>] e.g.
localhost, 10.1.1.7:10000, broker-host:10000,
guest/guest@localhost,
guest/guest@broker-host:10000
default is the host QpidRestAPI runs on & port
5672.
From the post below Gordon it sounds like you've now got it up and
running. It's a shame that it didn't "just work" for you as I'd hoped.
If there's any specific gotchas that you came across feel free to add
them to the Jira comments. I've tried pretty hard to do a good job with
things like JavaDoc (do take a look at the docs subdirectory in the
source tree) and the -h switch on the command line, but I've been
playing with this for such a long time that things which may be obvious
to me aren't actually obvious at all.
I hope that once you got over the initial snags you've found the pages
and navigation to be pretty intuitive. I've tried to protect people from
themselves a bit, so for example all of the QMF related queues and
exchanges have management functions like add/delete etc. disabled 'cause
it would be a bad idea to delete a QMF queue :-) Similarly when adding
bindings I've tried to populate as much information as I can
automatically so if you add a binding from a queue that queue is filled
in and you get a dynamically populated radio selector for exchanges,
similarly when you add a binding from an exchange you will see a radio
selector with all queues except the QMF ones.
Hope you're now in a position to have a good play, I'm hoping that you
don't come across too many other oddities.
I guess that my main motivation behind all of this this it to help
"sell" Qpid.
You'll remember my comment the other day about selecting products and
persuading the "hard of thinking" and also needing to be cognescente of
the "branding" and "product placement". One issue that I've come across
several times is that command line management tools are great for
techies but they aren't very "CEO friendly", so having a slightly
(possibly over) flashy modern looking UI might be the bit of bling
needed to get people to realise that Qpid is every bit as professional
as some expensive commercial offering. I *really* hope that it can help
to further the Qpid cause :-)
Cheers,
Frase
On 22/01/13 15:52, Gordon Sim wrote:
On 01/22/2013 03:09 PM, Bruno Matos wrote:
On Tue, 2013-01-22 at 15:08 +0000, Gordon Sim wrote:
On 01/22/2013 02:50 PM, Gordon Sim wrote:
On 01/22/2013 02:37 PM, Bruno Matos wrote:
Try to add a new QMF Console Connection in the settings page. It
worked
for me.
That's what I did try. But I can't edit any of the fields on the
screen
that presents. Its as if there is no edit permission.
Ok, that may have been stupidity on my part first time around. I can
now
add a connection that way... however I can't yet get any stats or
entities to show up...
Sometimes it take some seconds... Just make sure that you have the new
connection selected and see the Broker tab, it should have the basic
information.
The problem seems to stem from using the qpid jars from trunk (or
indeed it seems from 0.20 rc4). The 0.18 jars work (against either a
0.18 qpidd or a 0.20/trunk qpidd).
Fraser, this is indeed a *really* nice tool. Far better than anything
else we have currently for qpidd! Really nice job!
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
