BYOL for AWS and Azure in Mist #744

Chr1st0ph3rTurn3r · 2024-07-24T20:14:47Z

No description provided.

MichaelBaj · 2024-07-24T20:37:54Z

docs/intro_installation_azure_mist.md

 * Hourly Plan: This provides a free trial period for 30 days and an hourly software cost after the trial expires. This plan is recommended for Proof of Concepts and Trials only. Software upgrades and deployments outside of the cloud, (on premises) require a software access token. Select the Hourly plan of the [Session Smart Networking Platform](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/juniper-networks.session-smart-networking-payg?tab=Overview) offering.

+* Bring Your Own License (BYOL): This allows you to install your own licensed copy of the SSR software on an Azure VM. A token or certificate is required to install the software. If a token or certificate is not in your possession, please contact your Juniper Sales representative. Refer to the [Session Smart Networking Platform (BYOL)]


we should not be referencing the use of certificates any more for software download.

MichaelBaj · 2024-07-24T20:38:54Z

docs/intro_installation_quickstart_mist_aws.md

 * Hourly: This provides a free trial period for 30 days and an hourly software cost after the trial expires. This plan is recommended for Proof of Concepts and Trials only. Software upgrades and deployments outside of the cloud, (on premises) require a token or certificate. The software can not be purchased via the marketplace. Refer to the [Session Smart Networking Platform (PAYG)](https://aws.amazon.com/marketplace/pp/prodview-l5kwn7puwvt3g?sr=0-1&ref_=beagle&applicationId=AWSMPContessa) offering.

-Once you have selected the AMI that better suits the needs of your deployment, proceed to the [Session Smart Router Deployment](#session-smart-router-deployment) to deploy a Session Smart Router.
+* Bring Your Own License (BYOL): This allows you to install your own licensed copy of the SSR software on an AWS VM. A token or certificate is required to install the software. If a token or certificate is not in your possession, please contact your Juniper Sales representative. Refer to the [Session Smart Networking Platform (BYOL)](https://aws.amazon.com/marketplace/pp/prodview-lz6cjd43qgw3c?sr=0-2&ref_=beagle&applicationId=AWSMPContessa) offering.


No more certificates.

…t' of github.com:128technology/docs into byol-aws-azure-mist

haberkornsam

Good start. It might make sense to separate BYOL from the rest of the azure/aws stuff. It is pretty different as far as templates/fields/process goes. Mist managed doesn't use artifactory tokens, but they are required for conductor/conductor-managed

There are also some version restrictions that are at play. i.e. mist > 6.x, conductor > 6.3, etc. And initially only mist-managed is available.

haberkornsam · 2024-07-25T12:46:10Z

docs/intro_installation_azure_mist.md

 * Hourly Plan: This provides a free trial period for 30 days and an hourly software cost after the trial expires. This plan is recommended for Proof of Concepts and Trials only. Software upgrades and deployments outside of the cloud, (on premises) require a software access token. Select the Hourly plan of the [Session Smart Networking Platform](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/juniper-networks.session-smart-networking-payg?tab=Overview) offering.

+* Bring Your Own License (BYOL): This allows you to install your own licensed copy of the SSR software on an Azure VM. A token or certificate is required to install the software. If a token or certificate is not in your possession, please contact your Juniper Sales representative. Refer to the [Session Smart Networking Platform (BYOL)]


A token or certificate is required to install the software

This is only true for conductor/conductor managed onboarding. For mist managed we use the mist proxy repos.

haberkornsam · 2024-07-25T12:49:54Z

docs/intro_installation_azure_mist.md

+  * Provide the name of the VNet in the **Virtual Network Name** field (for example: `128T-VNet`).
+  * Provide the name of the availability set in the **Availability Set Name** field (for example: `128TRouterSet`).
+  * Provide the name of the **Public Subnet Name**
+  * Provide the name of the **Private Subnet Name**


The final template will have 3 subnets. Public, Private, Management

haberkornsam · 2024-07-29T20:06:28Z

docs/intro_installation_azure_mist.md

+
+![CloudFormation Template](/img/azure-byol-template.png)
+
+Answer the following 4 questions to launch the deployment of an SSR. For additional information refer to [Launch the Template](#launch-the-template). 


BYOL will have another "question" to answer What SSR version do you want to install?

This goes in the version field in the templates

haberkornsam · 2024-07-29T20:07:39Z

docs/intro_installation_azure_mist.md

@@ -164,11  168,11 @@ write_files:
 | Option | Meaning |
 | ------ | ------- |
 | name | The name of the router to use for Mist onboarding. By default, the instance name will be used. |
-| registration-code | The Mist registration used for adoption of the instance to a Mist org. |
+| registration-code | The Mist registration used for adoption of the instance to a Mist organization. |


Need to add ssr-version to the onboarding config for BYOL

haberkornsam · 2024-07-29T20:08:07Z

docs/intro_installation_azure_mist.md

@@ -265,21  267,21 @@ A description of the parameters of the template are listed in the following tabl
 | Private Subnet Allowed CIDR    | It corresponds to the source IP CIDR range of the internal workloads/endpoints allowed to originate traffic to the private interface of the router. This field allows for defining a well defined and trusted IP address range. By default is set to 0.0.0.0/0 to allow every workload/endpoint to communicate with the router.                                                                             |
 | Management Subnet Name  | The name of the management subnet within the VNet. |
 | Admin Allowed CIDR      | It allows for restricting reachability to the management interface of the router to a well known source IP address CIDR range. By default is set to 0.0.0.0/0 allowing every IP address to reach the management interface. Once the deployment completes, it is highly recommended to update the configuration of the network security group to allow only access from the source IP address/es where the Session Smart Router will be administered. |
-| Registration Code   | The Mist registration used for adoption of the instance to a Mist org. |
+| Registration Code   | The Mist registration used for adoption of the instance to a Mist organization. |


The template also has version which corresponds to ssr-version

haberkornsam · 2024-07-29T20:15:16Z

docs/intro_installation_quickstart_mist_aws.md

@@ -280,10  283,10 @@ aws ec2 create-launch-template \
 :::important
 When logging to the Linux instance via SSH use `t128` as the username and the SSH public key of the IAM user provided in the template.
 If a template of the Bring Your Own License image was used, SSH to the EC2 instance using `t128` as the username as indicated in the `SSHLogin` field. Launch the software installation process with the command `sudo install-ssr`.


I don't think this applies anymore

docs/intro_installation_byol_azure_mist.md

agrawalkaushik · 2024-08-02T14:23:32Z

docs/intro_installation_byol_azure_mist.md

+  * Provide the name of the **Public Subnet Name**
+  * Provide the name of the **Private Subnet Name**
+  * Provide the name of the **Management Subnet**
+* Which Mist organization is going to manage it?


@haberkornsam we need to insert a step here to Provide the SSR version.

That step is at the top of the list. I assumed it was the first thing on the template. I probably should have looked more closely at the azure template.

docs/intro_installation_byol_azure_mist.md

agrawalkaushik · 2024-08-02T14:24:44Z

docs/intro_installation_byol_azure_mist.md

+
+<img src={useBaseUrl('/img/platforms_azure_private_image_version_mismatch.png')} alt="Private Image Version Mismatch" width="75%" height="75%" />
+
+### Device Does Not Exist In Mist after ZTP


@haberkornsam we added a new lite TSI for this case, can you please update the section based on those instructions.

Additionally, we added a command line tool that a user can run to onboard the router (if they do not use cloud-formation/cloud-init etc). So please make sure we capture that as well.

agrawalkaushik · 2024-08-02T14:29:16Z

static/img/azure-byol-template.png

@haberkornsam we'll need a new screenshot that includes the SSR version

The SSR version is included in the screenshot. It's just called version. Should we update the templates to say SSR Version?

agrawalkaushik · 2024-08-02T14:29:55Z

static/img/aws-byol-template.png

The graphic is a bit small - but just checking to make sure the SSR version is included here? If not, we need a new screenshot with that - @haberkornsam please help with this

…milar flow

…nto byol-aws-azure-mist

Chr1st0ph3rTurn3r added 6 commits July 10, 2024 15:53

updating for byol

942aead

add some text

3625638

adding template image

cbd311b

interim commit

6863e3a

adding azure template graphic

c7ceb10

for review, added template image, other clean up.

2826991

Chr1st0ph3rTurn3r requested review from haberkornsam and agrawalkaushik July 24, 2024 20:14

Chr1st0ph3rTurn3r requested a review from MichaelBaj as a code owner July 24, 2024 20:14

MichaelBaj requested changes Jul 24, 2024

View reviewed changes

Chr1st0ph3rTurn3r and others added 3 commits July 25, 2024 08:54

Merge branch 'master' into byol-aws-azure-mist

26ad0c1

removed reference to certificates and unnecessary Introduction header.

1fde53b

merging updated content from master Merge branch 'byol-aws-azure-mis…

49fa083

…t' of github.com:128technology/docs into byol-aws-azure-mist

MichaelBaj self-requested a review July 25, 2024 18:15

MichaelBaj previously approved these changes Jul 25, 2024

View reviewed changes

haberkornsam reviewed Jul 29, 2024

View reviewed changes

Chr1st0ph3rTurn3r added 2 commits July 30, 2024 14:38

intrim checkin

9224aaa

updates based on Sam's review, and general attempts at cleanup.

a18970e

Chr1st0ph3rTurn3r dismissed MichaelBaj’s stale review via a18970e July 30, 2024 21:16

Chr1st0ph3rTurn3r requested a review from haberkornsam July 31, 2024 14:31

separating aws and azure byol topics

abbaaf2

agrawalkaushik reviewed Aug 2, 2024

View reviewed changes

docs/intro_installation_byol_azure_mist.md Outdated Show resolved Hide resolved

agrawalkaushik reviewed Aug 2, 2024

View reviewed changes

docs/intro_installation_byol_azure_mist.md Show resolved Hide resolved

agrawalkaushik reviewed Aug 2, 2024

View reviewed changes

Chr1st0ph3rTurn3r and others added 3 commits August 2, 2024 16:19

made a couple edits per the review, and a couple others that I found.

e110ce9

make tweaks per review comments and rearrange azure/aws to be more si…

fabb0b9

…milar flow

Add notes about enabling ENA

3bfb270

MichaelBaj self-requested a review August 9, 2024 13:22

Chr1st0ph3rTurn3r and others added 3 commits August 9, 2024 13:47

Merge branch 'master' into byol-aws-azure-mist

916816a

updating graphic

adb387d

Merge remote-tracking branch 'origin/master' into byol-aws-azure-mist

32089f3

MichaelBaj previously approved these changes Aug 26, 2024

View reviewed changes

update byol docs for ol7

2083c57

haberkornsam dismissed MichaelBaj’s stale review via 2083c57 August 26, 2024 19:41

Merge branch 'master' into byol-aws-azure-mist

c5c8460

Chr1st0ph3rTurn3r requested review from MichaelBaj and agrawalkaushik August 27, 2024 12:28

agrawalkaushik added 3 commits August 27, 2024 13:13

Merge branch 'byol-aws-azure-mist' of github.com:128technology/docs i…

061345f

…nto byol-aws-azure-mist

Fixup some language around troubleshooting

8035060

Remove the AWS Byol from sidebar for now

41637bb

agrawalkaushik approved these changes Aug 28, 2024

View reviewed changes

MichaelBaj approved these changes Aug 29, 2024

View reviewed changes

agrawalkaushik merged commit 4a99749 into master Aug 29, 2024
1 check passed

agrawalkaushik deleted the byol-aws-azure-mist branch August 29, 2024 01:46

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

BYOL for AWS and Azure in Mist #744

BYOL for AWS and Azure in Mist #744

Chr1st0ph3rTurn3r commented Jul 24, 2024

MichaelBaj Jul 24, 2024

MichaelBaj Jul 24, 2024

haberkornsam left a comment

haberkornsam Jul 25, 2024

haberkornsam Jul 25, 2024

haberkornsam Jul 29, 2024

haberkornsam Jul 29, 2024

haberkornsam Jul 29, 2024

haberkornsam Jul 29, 2024

haberkornsam Jul 29, 2024

agrawalkaushik Aug 2, 2024

Chr1st0ph3rTurn3r Aug 2, 2024

agrawalkaushik Aug 2, 2024

agrawalkaushik Aug 2, 2024

agrawalkaushik Aug 2, 2024

haberkornsam Aug 2, 2024

agrawalkaushik Aug 2, 2024

		* Hourly Plan: This provides a free trial period for 30 days and an hourly software cost after the trial expires. This plan is recommended for Proof of Concepts and Trials only. Software upgrades and deployments outside of the cloud, (on premises) require a software access token. Select the Hourly plan of the [Session Smart Networking Platform](https://azuremarketplace.microsoft.com/en-us/marketplace/apps/juniper-networks.session-smart-networking-payg?tab=Overview) offering.

		* Bring Your Own License (BYOL): This allows you to install your own licensed copy of the SSR software on an Azure VM. A token or certificate is required to install the software. If a token or certificate is not in your possession, please contact your Juniper Sales representative. Refer to the [Session Smart Networking Platform (BYOL)]


		![CloudFormation Template](/img/azure-byol-template.png)

		Answer the following 4 questions to launch the deployment of an SSR. For additional information refer to [Launch the Template](#launch-the-template).


		<img src={useBaseUrl('/img/platforms_azure_private_image_version_mismatch.png')} alt="Private Image Version Mismatch" width="75%" height="75%" />

		### Device Does Not Exist In Mist after ZTP

BYOL for AWS and Azure in Mist #744

BYOL for AWS and Azure in Mist #744

Conversation

Chr1st0ph3rTurn3r commented Jul 24, 2024

Choose a reason for hiding this comment

Choose a reason for hiding this comment

haberkornsam left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment