OSPF instead of static routes

Hey everyone, first post here so bear with me. I just started overseeing a network of about 28 sites all inside city limits. They're all connected to AT&T OEM/ASE clouds (two clouds, currently migrating all to ASE), and all sites are connected with static routes (and very large ACLs).

So I am planning on doing OSPF and get rid of all static routes (along with new L3 and L2 equipment, the current gear is about 10 years old), and create Lo0 addresses for management.

I will be using RFC1918 addresses and want to use 10.x.x.x for the management VLAN and 172.x.x.x. for the Lo0. Company is growing so I need to account for that. So my questions for you experts would be

1) Any issues with using Lo0 addresses starting 172.16.1.254/32, 172.16.2.254/32 and so forth?

2) The existing routers are currently addressed starting at 10.1.1.1, 10.2.1.1 and ending in 10.28.1.1. Any issues with addressing the new one starting at 10.30.1.254/24, 10.31.1.254/24, etc?

3) I want to start the OSPF zones at 0.0.0.0 (DataCenter) and go up from there using odd numbers (0.0.0.3 for the DR site, 0.0.0.5, etc). This will leave the even numbers for future growth.

I am well aware that everything need to be re-IP'd and management is OK with that.

Suggestions are appreciated.

Thanks!