How do you deal with isolating deployments of multiple versions of an app?
I noticed the initial application – looked like localhost:8080 – so if I want to use the cloud, I’ve already established a local application server where I’m running this war file you’ve delivered to me just to deploy my war file to the cloud?
Describe how the management nodes interact with the agents running on the other nodes?
Something along the lines of “two nodes in the cluster at the same time, how do you distinguish…”? Basically, how does cluster partitioning work?
I noticed that Deltacloud has been submitted to the incubator at Apache. Are there any similar plans, or do you know the history of that, or whether other projects such as Cooling Tower or other projects related to the ecosystem are going to also be submitted?
Can you show an example of how Cooling Tower is configured?
What is the Upload button for? Is there a RESTful API that is engaged before I even take advantage of these parameters here?
What’s involved in setting all this up locally on my developer desktop so I can try this stuff out?
So get everything from the Linux command line, vmware, virtualbox…?
Wouldn’t corporate firewalls block access to EC2? From my desktop out to the world?
So for initial adoption, it would be per-developer, so if I have 5000 developers in one organization, and 50 want to try this out – they’re all installing locally – and they decide they like it as a corporate standard, then they build a team server…?
The agents are part of …?
Those are written in …?
I’m a bit concerned about the proliferation of agents…
And the management node is not a JON node?
You’re saying that the management node and the management server – I’m getting confused on the terminology – one’s a Ruby thing, and one’s really a JBoss server?
This sounds great as, you mentioned earlier, a corporation service. But right now …, what is the roadmap and direction that we can move forward to make this fully fleshed out?