-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: deployment documentation for Azure and Azure Private #110
base: master
Are you sure you want to change the base?
Conversation
Signed-off-by: Jared Weinfurtner <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See individual comments.
needs to be updated once https://github.com/carbynestack/carbynestack/pull/103has been merged and released
@@ -1,8 +1,8 @@ | |||
# Infrastructure as Code | |||
|
|||
!!! warning | |||
Carbyne Stack Infrastructure as Code (IaC) is still in *proof-of-concept* | |||
stage. Reach out in case you encounter problems. | |||
Carbyne Stack Infrastructure as Code (IaC) is still in *proof-of-concept* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cd carbynestack | ||
``` | ||
|
||
3. Checkout the tag `sdk-v0.5.0` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
needs to be updated once carbynestack/#103 has been merged and released
cd carbynestack | ||
``` | ||
|
||
3. Checkout the tag `sdk-v0.5.0` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
needs to be updated once carbynestack/#103 has been merged and released
Jump Host in the CDKTF output. | ||
|
||
```shell | ||
ssh caliper@<jump_host_ip> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
caliper?
export ARM_SUBSCRIPTION_ID=<subscription id> | ||
``` | ||
|
||
## Deploy the Jump Host |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we expect people interested in a private deployment to know why it is required to have a jump host or should we add a description?
export ARM_SUBSCRIPTION_ID=<subscription id> | ||
``` | ||
|
||
## Deploy the Jump Host |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The deployment till this point (and the "Destroy and Clean Up" section) are identical for public and private azure deployment.
Would it make sense to have private and public azure deployment as individual paths in one file to get rid of redundancy and the hassle of keeping both up to date
Adding documentation on deploying a 2-party Carbyne Stack cluster onto Azure and onto a private Azure cluster.