We need to spin up three additional Wowza Engine instances. One of the three should be in an AWS data center in Europe. All three should be BYOB versions of the engine appliance. All three should be on the same size EC2 instance we're using now.
Richard, please set up a meeting with you, me, and :cshields to discuss this. I'd like to better understand your current and future needs before we go much farther.
(In reply to Richard Weiss [:r2] from comment #1) > Richard, please set up a meeting with you, me, and :cshields to discuss > this. I'd like to better understand your current and future needs before we > go much farther. Will do. Is IT yet at the point where we can automate spinning-up and tearing down (or sleeping) an AWS EC-2 instance? Ultimately I'd like to spin them up for an event and tear them down when the event finishes. If we can do that, then we can scale as needed and actually reduce the overall cost. Right now we're coming up on a bunch of events in Europe (Workweek, View Source Berlin, Mozfest) so I'd rather aim an encoder at an AWS Wowza instance in Europe than the ones in Portland. I also want to EOL the Wowza engine in SCL3, and we're now occasionally having to shift people's meeting times because we run short of Wowza capacity. I'll try to schedule the meeting for tomorrow.
Richard, let me know when you're back from PTO and we can work on this.
Flags: needinfo?(riweiss) → needinfo?(richard)
Thanks Richard. I'll be back in the office on Friday, July 1. I'll touch bases then.
You need to log in before you can comment on or make changes to this bug.