Yeah, ComputerCraft would be the simplest way by far. However, it should also be doable using the Programmable Rednet Controller in the same amount of space (although I have no clue how you'd need to program it) or in much more space (but with no code) with a dozen State Cells (ProjectRed has them for sure, and BluePower probably has something similar).
When you look at a state cell in-world, you'll notice that it has two input sides and two output sides. I'll refer to the output that the pointer points to by default as the "front output", even though it faces to the side when you place it, and to the other output as the side output. To my understanding, the two inputs work the same way.
When you sent a pulse to either input, the front output turns on briefly (the time is set in the timer's GUI), and when that output turns off, the other output turns on for a tick or two. So, if you put a bunch of them side by side and send a pulse to the one at the end (the left end by default; note that you can flip the cells by shift-clicking them with a screwdriver), each will trigger the next one when its front output turns off. So, if you set each to a 15-second delay and wire the sixth one back to the first (or have the leftmost state cell be triggered by a 90-second Timer), a 15-second-long pulse will cycle through all six state cells.
However, that's not quite what you're trying to do. The simplest way to make each pulse last only two seconds would be to use six more state cells. If you put another state cell directly in front of one of the first six and set if to two seconds, it should shorten the 15-second pulse to two seconds. However, if you place 2-second state cells directly in front of all the 15-second cells, they'll all trigger each other and cause all sorts of chaos. However, if you move every other one forward a block, away from the 15-second cells, and fill the gaps with red alloy wire with a microblock strip (or cover) on either side, it should work just fine.