This issue was really hard to debug: first, I was able to reproduce it only in production environment, not in development env. It's still unclear how it affects Internet Explorer's behaviour.
As it turned out, IE caches every ajax requests. It means that e.g. on the deployments#show page clicking on the Properties tab, then the Instances tab and then back to the Properties tab does not fire any request to the server to update the content of the Properties tab. Needless to say that it's not broken in FF or Chrome.
The solution is quite simple, jQuery provides a 'cache' parameter for the global ajaxSetup config. If it's false, then jQuery will append a timestamp to the url avoiding the IE browser cache.
This patchset contains the remaining patches from the first round
rebased against the current head with the whitespace errors removed.
Additionally it incorporates more fixes from the list of tasks
from the controller audit.
Scott's feedback to the original patchset has been incorporated
into this revision.
Just created a set of Aeolus 0.9.0 rpms, for F16/F17 and RHEL/CentOS 6.2
(64-bit only), and put them in a new 0.9.0 repo on our site.
The Conductor rpms for this release are from the 0.9-maint branch in
Everything else is from our testing repo. *Seems ok* in my limited
testing on F15, F16, and RHEL6.
(configure works, EC2 deployment goes ok, that kind of thing)
Also updated our "latest-release" repository link, so anyone using
the "Stable" installation instructions now gets 0.9.0.
If anyone has questions, feel free to ask. :)
Regards and best wishes,
Aeolus Community Manager
Deltacloud is going to implement a stateful app on top of DC API. This
app will do very similar job to what we planned with Cloud State. Some
basic ideas/thoughts about Cloud State are described on wiki:
So for us it would be much easier to use this deltacloud app instead of
implementing the same thing.
Here are some basic requirements which we would need on Conductor side
from the stateful app:
1) the app should check state of not only instances but also other
resources - we need especially realms because we check availability status
2) it should be possible to register hooks for a resource I want to
watch, hook could be just an URL, when the resource is changed data are
POSTed to the registered URL.
TODO: authentication when posting data to hook url? we use oauth between
other components now
TODO: how to handle hook failures (conductor is not accessible and hook
can't be invoked)?
TODO: how to handle credentials? will the stateful app keep credentails
permanently for each instance being checked?
3) frequency of instance status checking: we probably don't need to have
this configurable, but the checking frequency should be as low as
possible - various actions are hooked to instance state changes (for
example runtime is measured by this). It should be also scalable - if
there are 100 instances for one provider account, we still need check
all of them. Would be nice to use multiple parallel requests to provider
if possible or checking interval might be dynamically increased
according to the actual length of queue).
Just installed aeolus-all 0.10.0 from our F16 testing repo (screenshot attached).
The whole top menu area looks weird/broken -> completely black, no logo.
That's not how it's supposed to be is it?
Aeolus Community Manager
Based on the discussion with Martyn and Jan, I wrote a short design doc
for Tracker; I hope I captured what we have discussed so far.
The doc is at http://people.apache.org/~lutter/deltacloud/tracker.html
and also attached as Markdown; it's also in my deltacloud git repo.
Comments and improvements (ideally as patches against the markdown ;)
more than welcome
 In the file site/content/tracker.mdown on the tracker/design branch