keyser wrote: » 1. I'm in Phoenix. Powering the lab in summer kills me. From one side I pay to power the lab that throws heat into my home office. From the other side I pay a huge cooling bill. The power company has me coming and going. For that reason I tend not to work on it in the summer. That's a bad solution.
keyser wrote: » 2. I travel a bit so I sprung for the remote access server and APC power switches. Now that Junosphere is out would I be better off purchasing time on their system and sell the lab? The problem with moving to the cloud is timing. A 24 hr chunk of time is hard to bite off. I'd prefer it in 4 or 6 hour windows, specifically in the evening. I have a Mac Book Pro running Virtual Box. I can run 4 olives, doing it now, but wonder how far I can scale that solution...6, 8, 10, instances before I run into issues? I need find out what my limit is here.Moving to the Olive or Junosphere solution has limitations, right? Limited switching on Junosphere and Mulitcast with Olive?
keyser wrote: » 3. This is my primary issue -- Lets presume I can get the lab sorted...Olive, Junosphere, keep my lab etc. What then? Pick up a workbook (Proteus or Inetzero) and start plugging away? Dive into the Sybex books and create my own material where they come up short? If I keep the lab Juniper training material is out, unless I upgrade the 2300's to SRX's. (J2300's are at 9.5, Juniper labs are at 10.4?) I don't feel like I have the time or the experience to come up with the workbook on my own. If the Proteus or Inetzero workbooks are a good resource then I'm leaning that direction using my Mac with Olives. Sell the lab, spend $4-500 on workbook, max the memory in my mac, and be done! What's the reality?