On Premise deployment of Hyperledger Fabric without cloud

If peers, orderers,ca server of all organizations are deployed in a cloud then how come hyperledger fabric is distribued?

Each service (orderer, peer, etc) would be run on a different (virtual) machine within the same environment/cloud provider. Those machines could be distributed across various data-centers globally, or across different cloud providers, or even on many varying organisation's hardware. It makes relatively little difference, so long as they're not all on the same box, under the control of one organisation/person. Then it will be distributed.

Can this setup can be made in distributed , "in premise" infrastructure?

Yes - it can be set up to run however you like, although you may run into access issues, from firewalls, etc. Perhaps you'd have different departments run their own peers within a single organisation across many offices.

Is there any source for reference/links to do this sort of setup?

I believe most people start using the scripts from the hyperledger fabric codebase. Theres documentation here https://hyperledger-fabric.readthedocs.io/en/release-1.4/build_network.html about spinning up the "build your first network" script - byfn.sh (looks like this may have been removed)

https://github.com/hyperledger/fabric-samples has a ci folder. Within it there's some steps to build/run/test the codebase examples. Eg. https://github.com/hyperledger/fabric-samples/blob/main/ci/scripts/run-test-network-basic.shcalls network.sh which is here: https://github.com/hyperledger/fabric-samples/blob/main/test-network/network.sh

If you really want to understand the necessary steps you'll need to work through it all. There's also some good documentation on what the various parts of the hyperledger-fabric system do here: https://github.com/hyperledger/fabric/tree/345a08b5cd30ef937a8270d1722462e4cad1caa9/docs/source - you'll need to navigate through the directories to the parts you're interested in and locate the .md files which contain the documentation : eg.

• Peer docs/source/peers/peers.md
• Orderer docs/source/orderer/ordering_service.md
• Smart Contracts (aka Chaincode) - docs/source/smartcontract/smartcontract.md
• Channels - docs/source/create_channel/channel_policies.md

You may also find some Dockerfiles in various repositories with different setups.