I am a bit surprised that in your previous message you said you built something on top of glu without understanding those concepts. Before you deep dive into changing the state machine or whatever else, I would strongly advise that you really get comfortable with what glu has to offer out of the box before tweaking it (changing the state machine...). I would also strongly suggest that if there is a requirement you have that does not seem to fit in the stock glu, you should ask on the forum about it because maybe there is a way to do it without changing glu.
"Deploy" is the generic term that will bring whatever state your system is into the "desired state" (aka defaultEntryState), which by default is "running". So if you have an entry e1, that is not installed and another one (e2) that is "stopped", then glu will generate a plan to bring both of them to state "running".
For this it will look for a "path" in the state machine to bring each entry to their desired state. In this example, for e1, it will run install, configure and start. For e2, it will run start only. You can see this in action by simply selecting the plan: the steps will be displayed in the right column (using the tutorial (e1=/sample/i001 and e2=/sample/i002) try to uninstall one of the entry and stop another one, then click deploy and you will see exactly what I am talking about).
Bounce is a shortcut which calls stop and start on all the entries (note that bounce only works with the default state machine) which are in a state that allow them to be called this way.
Undeploy brings all the entries to state NONE: glu will look for a "path" in the state machine to bring each entry to state NONE and execute all the actions involved to get there. After executing this, the entry is fully removed from the host (hence the name undeploy).
Redeploy first brings all the entries to state NONE then all the entries to state "desired state" or in other word, it is a shortcut to execute undeploy/deploy.
and that is all you have to do. Of course you need to define your own state names and transitions but that is all you have to do. I would strongly suggest to start from the state machine that comes with glu and modify it to suit your needs rather than defining a completely new one.
When you then generate the distributions (this corresponds to step 3 of the easy production setup), glu will automatically use your state machine.