pytorch2.0_ttnn support master issue

[tt-rkim]

Introduction

We are putting all relevant issues + action items for supporting https://github.com/tenstorrent-metal/pytorch2.0_ttnn/ and related infrastructure issues here.

cc: @ayerofieiev-tt @TT-billteng @ttmchiou

• ensure everyone who currently has access, has access after the move too (need to open OSPO ticket w/ John Hawley, @ayerofieiev-tt to finalize list of people)
• move the actual repo (need to open OSPO ticket w/ John Hawley)
• Create starter CI VM @ttmchiou
• Finalize list of all system and software requirements for CI VM @ayerofieiev-tt

[tt-rkim]

From @kevinwuTT :

• On a completely fresh python virtual environment, I can successfully install ttnn from the github direct whl link and other requirements from pytorch2.0_ttnn requirements.txt. I can import ttnn successfully from here.
  • However, the tests do depend on tests.ttnn.utils_for_testing module which isn't in the release whl from github. I'm not sure if I can remove this dependency since many of the unit tests from tt-metal/ttnn also uses the functions from that module.
• I will include a dev version of requirements.txt which won't install the whl and rely on the user creating the python virtual env with ./create_venv.sh from tt-metal. That creates an egg link to the ttnn source directory which makes development easier.
• I can push the changes to requirements.txt to main, but I am still not sure how to address the issue with the tests module from the first point.

[ayerofieiev-tt]

tests.ttnn.utils_for_testing is currently only used for a pcc check.
We agreed that @kevinwuTT will remove it.

[ayerofieiev-tt]

@ttmchiou @tt-rkim

[ttmchiou]

tt-metal-pytorch-vm-1 CI VM added to repo with sample GH workflow provided
tenstorrent/pytorch2.0_ttnn#4
https://github.com/tenstorrent-metal/pytorch2.0_ttnn/actions
Will need follow-up from @ayerofieiev-tt for list of deps needed for installation.

[ttmchiou]

@tt-rkim
@ayerofieiev-tt has finished shifting the pytorch repo to the TT org and current members are ported over to have same access.
Would be prudent to start planning VM consolidation soon