-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #25 from Keysight/bogdan-updates
ORAN SIM CE 3.0 resources
- Loading branch information
Showing
183 changed files
with
61,118 additions
and
0 deletions.
There are no files selected for viewing
Binary file not shown.
Binary file not shown.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
Copyright Keysight Technologies 2021. | ||
|
||
IMPORTANT: If the Software includes one or more computer programs bearing a Keysight copyright notice and in source code format (“Source Files”), such Source Files are subject to the terms and conditions of the Keysight Software End-User License Agreement (“EULA”) www.Keysight.com/find/sweula and these Supplemental Terms. BY USING THE SOURCE FILES, YOU AGREE TO BE BOUND BY THE TERMS AND CONDITIONS OF THE EULA INCLUDING THESE SUPPLEMENTAL TERMS. IF YOU DO NOT AGREE TO THESE TERMS AND CONDITIONS, DO NOT COPY OR DISTRIBUTE THE SOURCE FILES. | ||
|
||
Additional Rights and Limitations. Keysight grants you a limited, non-exclusive license, without a right to sub-license, to copy and modify the Source Files solely for use with Keysight products, or systems that contain at least one Keysight product. You own any such modifications and Keysight retains all right, title and interest in the underlying Source Files. All rights not expressly granted are reserved by Keysight. | ||
|
||
General. Capitalized terms used in these Supplemental Terms and not otherwise defined herein shall have the meanings assigned to them in the EULA. To the extent that any of these Supplemental Terms conflict with terms in the EULA, these Supplemental Terms control solely with respect to the Source Files. |
1,469 changes: 1,469 additions & 0 deletions
1,469
Azure/Open RAN SIM CE 3.0/Templates/azure_deployment_3.4_release_arm_template.json
Large diffs are not rendered by default.
Oops, something went wrong.
65 changes: 65 additions & 0 deletions
65
Azure/Open RAN SIM CE 3.0/terraform/deploy_LoadCore_from_Azure_Images/README.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,65 @@ | ||
# Terraform templates | ||
|
||
## Prerequisites | ||
The prerequisites are: | ||
- Latest version of Terraform installed. https://learn.hashicorp.com/tutorials/terraform/install-cli | ||
- Authenticate to Azure platform usign Azure CLI tool. https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/azure_cli | ||
|
||
## How to use: | ||
|
||
You can start learning terraform from the official website: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs | ||
|
||
Before running any terraform command, you need to authenticate using Azure CLI. | ||
|
||
When you create a new configuration — or check out an existing configuration from version control — you need to initialize the directory with **terraform init** command. | ||
You can also make sure your configuration is syntactically valid and internally consistent by using the **terraform validate** command. | ||
|
||
The **terraform apply** command executes the actions proposed in a terraform template. All the default deployment variables may be changed. The variables will be explained in each of the proposed templates. | ||
|
||
|
||
### One LoadCore MDW and two LoadCore Agents | ||
|
||
The template deploys Virtual Machine using **Azure Images**: | ||
- One LoadCore MDW | ||
- Two LoadCore Agents with three interfaces each. The first interface will be used for mananagament and the rest of the interfaces will be used for testing | ||
Each test interface will get 8 private IPs. | ||
|
||
The folder contains three files: | ||
|
||
**main.tf** contains the main set of configuration | ||
|
||
**variables.tf** contains the variable definitions. The variables can be also modified from here. | ||
|
||
**terraform.tfvars** is a variable definitions file in which you can provide values for variables | ||
|
||
|
||
## Template variables | ||
In order to modify the default values, you should modify the **terraform.tfvars** file. | ||
|
||
| **Parameter label (name)** | **Default** | **Description** | | ||
| ----------------------- | ----------------- | ----- | | ||
| prefix | Requires input |The Azure stack name. | | ||
| ssh_key_name | Requires input | Specify an existing Azure SSH key name. | | ||
| allowed_cidr | ["0.0.0.0/0"] |List of ip allowed to access the deployed machines. Default value will provide access to everyone from the internet. | | ||
| location | "eastus" | The Azure region for deployment. | | ||
| images_resource_group_name | Requires input | The Azure resource group name | | ||
| loadcore_mdw_name | Requires input | The Azure Image name for LoadCore MDW | | ||
| loadcore_agent_name | Requires input | The Azure Image name for LoadCore Agent | | ||
| loadcore_mdw_size | Standard_D8s_v3 | The VM size | | ||
| loadcore_agents_size | Standard_F4s | The VM size | | ||
| virtual_network_cidr | "10.0.0.0/16" | The Virtual Network CIDR. | | ||
| virtual_network_mgmt_subnet | "10.0.0.0/24" | The management CIDR. | | ||
| virtual_network_test_subnet | "10.0.1.0/24" | The test CIDR. | | ||
|
||
|
||
## Destruction | ||
|
||
The **terraform destroy** command will destroy the previous deployed infrastructure. | ||
|
||
|
||
# Post deployment | ||
After successful deployment, please follow the next steps: | ||
- Terraform will display the Outputs where you can find the LoadCore UI IP address. Always wait a few more minutes to boot-up. | ||
- Terraform will also display what private IPs can be used in LoadCore test for each test interface. | ||
- Default LoadCore UI username and password: admin/admin | ||
- The LoadCore Agents should be automatically registered to LoadCore MDW |
Oops, something went wrong.