Thanks for adding the response about civix and naming convention.
Out of idle curiosity... what's wrong with doing "civix generate:module org.civicrm.osdi" and using the default/convention?
Actually I had developed the people's endpoint page in a file index.php which lies at “/sites/default/ext/org.civicrm.osdi/api/v3/People/” on the camus (remote server).
So Eileen figured out when I was using this path as a link to people's resource on my AEP (API Entry Point) it didn't work because of the dots present in org.civicrm.osdi extension name . Though it does works on my local machine as I am using Apache and didn't work on the camus (remote server) may be because it runs on nginx and has some other configuration, I am exactly not sure about this.
The command "civix generate:module org.civicrm.osdi” works perfectly fine, well I started developing the extension with this only. The problem was because of the path I was using for index.php that didn't work out on camus, so I renamed the extension directory to “osdi” just to make the new path work ie “/sites/default/ext/osdi/api/v3/People/ “