I'd like to see the Head Geeks go over how Stacked APE's work, and what to take into account when deploying APE's in this way, rather than putting them on fresh metal (virtual or otherwise).
Great lab today, thanks guys!
Yes. I'm working on deploying our first APE, but wondering if i should create a second VM for it or just stack it on the same VM that our Primary one is on
All depends on the specifications on the host, really. If you have plenty of compute spare, and more importantly enough bandwidth on your polling network to cope with the additional traffic from the single host, then you could stack them. That said, if you have the OS licensing available and the compute resources free, deploying it on a separate server would be better. Sure, it'll make maintenance more of a pain when installing SW updates, as you'll have to update the APE separately, but it's the way to go if you resource isn't an issue.
The *only* problem I have with stacked pollers is that the only true ways you see it are in both licensing and polling load. Polling load should really be a number measured like % processor time or % idle time, so that if you had 3 polling engines your polling load could theoretically go up to 300% - like how %time is really %time times # of CPU's. That would make a lot more sense than the 1-100% as it's defined today. Thoughts, stevenwhunt / cobrien ?
If computing were only that simple.
