ASDK: Extended network connectivity
I like the default ASDK setup that do not need extended network knowledge to get it up and running. That should stay as it is.
At the other hand, more advanced network setups where connectivity outside the ASDK environment can be needed. Some use cases:
In our case we are running a Azure Stack proof-of-concept that includes connectivity to other systems and the internet
Development use case were you are developing / testing your application and the application need existing test systems that are outside the ASDF environment. Think of: enterprise message busses, datawarehouses / databases, integration with cloud services, etc
- Possibility to 'publish' the ASDK endpoints on the external / enterprise network. This should include a DNS that contains the external addresses to which forwarding can be done.
- Possibility to add a public network pool to ASDK that consists of external addresses (to be used as public ip address resources)
Thanks for your feedback.
This is currently under review.
Anang Siswanto commented
any update on this ? its should be great for as CSP cause many customer want to do POC before onboard to production
Derek Gabriel commented
We just ordered a machine for ASDK from Lenovo. This is a POC setup, and we really intend to drop it into the same rack in the DC that the full stack will end up in. It's important to test the networking environment as well if we're going to be spending $300k eventually...