-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
a1780f9
commit fb2a773
Showing
1 changed file
with
17 additions
and
17 deletions.
There are no files selected for viewing
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 |
---|---|---|
|
@@ -15,25 +15,25 @@ Now that everything is installed and your VM “laptop” is up and running you | |
|
||
1. Run the following command to connect your data center to Colony | ||
|
||
```bash | ||
colony init -–apiKey= $COLONY_API_KEY –apiURL=https//colony-api-virtual.konstruct.io | ||
``` | ||
```bash | ||
colony init -–apiKey= $COLONY_API_KEY –apiURL=https//colony-api-virtual.konstruct.io | ||
``` | ||
|
||
2. Next, exit to return the shell back to the data center. | ||
|
||
```bash | ||
exit | ||
``` | ||
```bash | ||
exit | ||
``` | ||
|
||
3. Finally, from the data center context run this command to turn on one of the reserved servers every 30 seconds, and auto-enroll them with Colony, making them available for provisioning operations. | ||
|
||
```bash | ||
bash ./virtual-datacenter/power-on.sh | ||
``` | ||
```bash | ||
bash ./virtual-datacenter/power-on.sh | ||
``` | ||
|
||
:::info | ||
If you connect to Colony and (*in the UI*) nothing appears after a minute or two there’s definitely an issue with the setup. Get in touch with us and we’ll be happy to get you sorted out. | ||
::: | ||
:::info | ||
If you connect to Colony and (*in the UI*) nothing appears after a minute or two there’s definitely an issue with the setup. Get in touch with us and we’ll be happy to get you sorted out. | ||
Check failure on line 35 in docs/install/virtual-install2.md GitHub Actions / check-markdown (.md, **.md, md.markdownlint.json)Emphasis style
Check failure on line 35 in docs/install/virtual-install2.md GitHub Actions / check-markdown (.md, **.md, md.markdownlint.json)Emphasis style
|
||
::: | ||
|
||
4. Now imagine you’re walking around in the data center to “turn on” the virtual machines. | ||
|
||
|
@@ -51,12 +51,12 @@ After your assets are all listed as “discovered” you can navigate to the **C | |
In a real-world set up data centers have network segmentation rules governing the IP address ranges in use. | ||
::: | ||
|
||
1. Select **Create Cluster** and choose **Kubernetes** from the menu to open the initial configuration. *For this example we’re going to create a new cluster with Talos.* | ||
1. Select **Create Cluster** and choose **Kubernetes** from the menu to open the initial configuration. _For this example we’re going to create a new cluster with Talos._ | ||
2. Complete the cluster details as follows: | ||
- Select a cluster type - Talos (*simplicity and security*) | ||
- Cluster Name - talos-demo (*or something similar*) | ||
- Global Gateway IP - 10.0.10.1 (*static for the vagrant data center environment*) | ||
- Additional SANS (*not required*) | ||
- Select a cluster type - Talos (_simplicity and security_) | ||
- Cluster Name - talos-demo (_or something similar_ | ||
- Global Gateway IP - 10.0.10.1 (_static for the vagrant data center environment_) | ||
- Additional SANS (_not required_) | ||
|
||
3. Select **Next** to continue to select a Control Plane (*you can choose one or multiples, these instructions are for one*) | ||
Check failure on line 61 in docs/install/virtual-install2.md GitHub Actions / check-markdown (.md, **.md, md.markdownlint.json)Emphasis style
Check failure on line 61 in docs/install/virtual-install2.md GitHub Actions / check-markdown (.md, **.md, md.markdownlint.json)Emphasis style
|
||
4. Select the top disk (the multi-disk setup is just to show support) | ||
|