DataTenant Knowledgebase - User contributions [en]

Create local login for Linux VMs

2025-02-28T17:09:30Z

Dtadmin:

This article will help you inject a local username and password into Linux instances at boot.

Some users prefer to use private keys to grant themselves access to their virtual machines, but some users prefer to simply define a username and password that will allow them to login directly to the console or easily over SSH. With most Linux based operating systems, the process to do this is easy.

== Input a Cloud config ==
During instance creation, there is a menu called the 'Cloud config'. This is where special commands can be input that will be executed automatically during first boot. Here is an example of a block of commands that can be put into the Cloud config menu to create a local username and password. '''''Remember to update this block with the username and password you want to use.

<pre>
#cloud-config
users:
- name: myadmin
groups: sudo
sudo: ['ALL=(ALL) NOPASSWD:ALL']
shell: /bin/bash
lock_passwd: false
ssh-authorized-keys: [] # Ensure no SSH keys are required

ssh_pwauth: true # Enable password authentication

runcmd:
- echo "myadmin:MyEasyPassword1" | sudo chpasswd # Set password using chpasswd
- sudo sed -i 's/^#PasswordAuthentication no/PasswordAuthentication yes/' /etc/ssh/sshd_config
- sudo sed -i 's/^PasswordAuthentication no/PasswordAuthentication yes/' /etc/ssh/sshd_config
- sudo systemctl restart sshd
</pre>

'''''NOTE: The users created with this code block will be able to SSH to your virtual machine (if port 22 is allowed) and have root access. Protect the password carefully!

[[File:CloudConfig.png|border|600px]]

When the instance has been created, you should be able to login to the console (or SSH) with the username/password specified in your Cloud config block.

Create local login for Linux VMs

2025-02-28T17:08:16Z

Dtadmin:

This article will help you inject a local username and password into Linux instances at boot.

Some users prefer to use private keys to grant themselves access to their virtual machines, but some users prefer to simply define a username and password that will allow them to login directly to the console or easily over SSH. With most Linux based operating systems, the process to do this is easy.

== Input a Cloud config ==
During instance creation, there is a menu called the 'Cloud config'. This is where special commands can be input that will be executed automatically during first boot. Here is an example of a block of commands that can be put into the Cloud config menu to create a local username and password.

<pre>
#cloud-config
users:
- name: myadmin
groups: sudo
sudo: ['ALL=(ALL) NOPASSWD:ALL']
shell: /bin/bash
lock_passwd: false
ssh-authorized-keys: [] # Ensure no SSH keys are required

ssh_pwauth: true # Enable password authentication

runcmd:
- echo "myadmin:MyEasyPassword1" | sudo chpasswd # Set password using chpasswd
- sudo sed -i 's/^#PasswordAuthentication no/PasswordAuthentication yes/' /etc/ssh/sshd_config
- sudo sed -i 's/^PasswordAuthentication no/PasswordAuthentication yes/' /etc/ssh/sshd_config
- sudo systemctl restart sshd
</pre>

'''''NOTE: The users created with this code block will be able to SSH to your virtual machine (if port 22 is allowed) and have root access. Protect the password carefully!

[[File:CloudConfig.png|border|600px]]

File:CloudConfig.png

2025-02-28T17:07:57Z

Dtadmin:

Create local login for Linux VMs

2025-02-28T17:07:02Z

Dtadmin:

This article will help you inject a local username and password into Linux instances at boot.

Some users prefer to use private keys to grant themselves access to their virtual machines, but some users prefer to simply define a username and password that will allow them to login directly to the console or easily over SSH. With most Linux based operating systems, the process to do this is easy.

== Input a Cloud config ==
During instance creation, there is a menu called the 'Cloud config'. This is where special commands can be input that will be executed automatically during first boot. Here is an example of a block of commands that can be put into the Cloud config menu to create a local username and password.

<pre>
#cloud-config
users:
- name: myadmin
groups: sudo
sudo: ['ALL=(ALL) NOPASSWD:ALL']
shell: /bin/bash
lock_passwd: false
ssh-authorized-keys: [] # Ensure no SSH keys are required

ssh_pwauth: true # Enable password authentication

runcmd:
- echo "myadmin:MyEasyPassword1" | sudo chpasswd # Set password using chpasswd
- sudo sed -i 's/^#PasswordAuthentication no/PasswordAuthentication yes/' /etc/ssh/sshd_config
- sudo sed -i 's/^PasswordAuthentication no/PasswordAuthentication yes/' /etc/ssh/sshd_config
- sudo systemctl restart sshd
</pre>

'''''NOTE: The users created with this code block will be able to SSH to your virtual machine (if port 22 is allowed) and have root access. Protect the password carefully!

[[File:Putty_Generate.png|border|600px]]

Create local login for Linux VMs

2025-02-28T17:06:00Z

Dtadmin:

This article will help you inject a local username and password into Linux instances at boot.

Some users prefer to use private keys to grant themselves access to their virtual machines, but some users prefer to simply define a username and password that will allow them to login directly to the console or easily over SSH. With most Linux based operating systems, the process to do this is easy.

== Input a Cloud config ==
During instance creation, there is a menu called the 'Cloud config'. This is where special commands can be input that will be executed automatically during first boot. Here is an example of a block of commands that can be put into the Cloud config menu to create a local username and password.

<pre>
#cloud-config
users:
- name: myadmin
groups: sudo
sudo: ['ALL=(ALL) NOPASSWD:ALL']
shell: /bin/bash
lock_passwd: false
ssh-authorized-keys: [] # Ensure no SSH keys are required

ssh_pwauth: true # Enable password authentication

runcmd:
- echo "myadmin:MyEasyPassword1" | sudo chpasswd # Set password using chpasswd
- sudo sed -i 's/^#PasswordAuthentication no/PasswordAuthentication yes/' /etc/ssh/sshd_config
- sudo sed -i 's/^PasswordAuthentication no/PasswordAuthentication yes/' /etc/ssh/sshd_config
- sudo systemctl restart sshd
</pre>

Create local login for Linux VMs

2025-02-28T17:04:27Z

Dtadmin:

Create local login for Linux VMs

2025-02-28T17:01:19Z

Dtadmin: Created page with "test"

test

Networking

2024-10-15T17:10:39Z

Dtadmin:

This article will explain DataTenant public cloud networking.

The DataTenant public cloud makes it easy to create private networks for your virtual machines and to connect them or advertise them to the internet.

==Creating Private Networks==
In your project, you can create nearly endless numbers of private virtual networks for your use in each region currently available to you. To get started, login to the cloud and select the project you'd like to work in.

# In the Cloud menu on the left hand side, select 'Networking'.
# In the top right hand corner, select 'Create Network'.
# Select which region you'd like to create your network in. For more information about regions, please review our [[Regions]] article.
# Give your Network a name. You can name your network something descriptive, like 'SQL Database Network', or something specific, like '192.168.0.0/24'.
# Select the 'Enable DHCP' option if it is not already enabled.
## Enabling DHCP on these networks is important, as newly created virtual machines need network connectivity in order to process their cloud initialization configuration. In the rare cases where you do not wish to have DHCP enabled on these private networks, please review our [[Config Drive]] article to ensure cloud initialization is still performed successfully.
# In the CIDR field, enter the subnet you wish to use in this private network. It should be written in CIDR notation (as in, 10.0.1.0/24 or something similar).
# In the Allocation Pools field, you have the option to narrow the range of IPs that the cloud is allowed to hand out to virtual machines within this network. You can write this in the form of ''Starting IP address, Ending IP address''.
## For example, when creating a ''192.168.0.0/24'' network, you could opt to narrow the allocation range by entering ''192.168.0.10, 192.168.0.100''. This would ensure only those 90 addresses would be handed out.
# In the DNS Name Servers field, you can fill in what DNS servers you would like to be given to virtual machines that use this network. You can write this in the form of ''First DNS IP Second DNS IP Third DNS IP''.
## For example, if I wanted to make use of a private DNS server at ''192.168.0.5'' and a public DNS server at ''8.8.4.4'', I would enter ''192.168.0.5 8.8.4.4'' in that field.
# In the Host Routes field, you can enter any static routes you would like to be injected into virtual machines that make use of this network.
# If you wish to customize the default gateway IP that will be advertised to virtual machines that use this network, you can toggle the 'Custom Gateway IP' option and enter a custom gateway IP address. If not, the first address in the network will be assumed to be the gateway.

When you've entered in these details, select 'Create Network' at the bottom to create your private network in your selected region.

==Creating a Virtual Router==
Once you've created a private network, you have the option of creating a virtual router to bridge together multiple private networks, or to give your private network access to the internet. Once a private network has been linked to the internet, you will also have the option to use 'Floating IP addresses' to make your virtual machine accessible from the internet.

# In the Cloud menu on the left hand side, select 'Networking'.
# In the top menu, choose 'Routers'.
# Select 'Create router'.
#

Networking

2024-10-15T16:34:26Z

Dtadmin:

Networking

2024-10-15T16:29:45Z

Dtadmin:

Networking

2024-10-15T16:21:39Z

Dtadmin:

Networking

2024-10-15T16:20:29Z

Dtadmin:

Networking

2024-10-15T16:18:10Z

Dtadmin: Created page with "This article will explain DataTenant public cloud networking. The DataTenant public cloud makes it easy to create private networks for your virtual machines and to connect them or advertise them to the internet. ==Creating Private Networks=="

Regions

2024-10-15T16:11:47Z

Dtadmin:

This article explains DataTenant cloud regions.

Regions are geographically disparate instances of the DataTenant public cloud that you can deploy your workloads into. Deploying into multiple regions can be an effective high availability or disaster recovery strategy, as natural disasters/outages will likely only affect one region at a time.

{| class="wikitable" style="margin:auto"
|+ Current Regions
|-
! Region !! Location
|-
| Central || Bettendorf, Iowa
|-
| South || Springfield, MO
|}

== Notes on Regions ==

Each DataTenant cloud region is a standalone instance of the cloud, meaning the resources created in each cloud are unique to that region. So, for example, a keypair created in the Central region will not be available to use in the South region, and vice versa. In order to use the same keypair for both regions, you'd need to import the keypair into whichever region it is not currently available in.

This is also true for networking. A network that makes use of subnet ''192.168.0.0/24'' in one region will not automatically be able to communicate with devices that use the same subnet in a different region. The two networks would be considered isolated private networks, and would have to be bridged together with a pair of network appliances (one in each region).

DataTenant can create custom layer two stretched networks between multiple regions on request. Please contact support@datatenant.com to inquire about setting up this option.

Regions

2024-10-15T16:06:22Z

Dtadmin: Created page with "This article explains DataTenant cloud regions. Regions are geographically disparate instances of the DataTenant public cloud that you can deploy your workloads into. Deploying into multiple regions can be an effective high availability or disaster recovery strategy, as natural disasters/outages will likely only affect one region at a time. {| class="wikitable" style="margin:auto" |+ Current Regions |- ! Region !! Location |- | Central || Bettendorf, I..."

Logging in to a new virtual machine

2024-10-10T16:16:16Z

Dtadmin: Dtadmin moved page Logging in to a new virtual machine to Logging in to a new virtual machine (Advanced Console)

#REDIRECT [[Logging in to a new virtual machine (Advanced Console)]]

Logging in to a new virtual machine (Advanced Console)

2024-10-10T16:16:16Z

Dtadmin: Dtadmin moved page Logging in to a new virtual machine to Logging in to a new virtual machine (Advanced Console)

This article will help you log into a new virtual machine using your personal key pair.

''NOTE: This article does not apply to Virtual Appliances, which have a default username and password that can be used for console logins. To find these default username and passwords, please review our [[Virtual Appliance default username and passwords]] article.''

Before creating your first virtual machine/instance, you would have needed to create a personal key pair by following our [[Create a keypair]] article. Done correctly, you would have ended up with a public key imported into the DataTenant cloud and two copies of your private key saved somewhere you can access. This article will guide you through using those two private keys to access an instance created using your public key.

== Logging into a Windows virtual machine/instance ==
When you create a new virtual machine using a Windows image, your public key will be used to encrypt the Administrator password on the instance. You can use your private key to decrypt that password and then login using the Administrator account.

To begin, login to the [https://cloud.datatenant.com DataTenant Cloud]. Navigate to the Project, Compute, Instances menu.

[[File:Cloud_Instances.png|border|200px]]

In the 'Actions' menu for your instance, choose 'Retrieve Password'.

[[File:Cloud_RetrievePassword.png|border|400px]]

'''''NOTE: It takes a minute or two after a Windows instance is fully created for the Administrator password to be set. If it the encrypted password is not available right away, wait a couple of minutes and check again. If it is still not available, please contact support@datatenant.com for further assistance.'''''

In the 'Retrieve Instance Password' screen, copy and paste the contents of your OpenSSH key into the 'Private Key' text box, or locate the file you saved that contains your OpenSSH key. Click 'Decrypt Password'.

[[File:Cloud_RetrievePassword2.png|border|600px]]

The decrypted password will appear in the 'Password' field. Copy it somewhere accessible and return to the 'Instances' menu.

Click on the Instance Name of the instance you want to login to. Click on the 'Console' tab to interact with the console session of the instance.

[[File:Cloud_Console.png|border|600px]]

If your Windows instance prompts you to change the Administrator password, click 'Cancel'. Press the 'Send Ctrl Alt Delete' button in the top right hand corner of the console to bring you to the login screen. Enter the decrypted Administrator password to login.

[[File:Cloud_Console2.png|border|600px]]

'''''NOTE: This process only works to retrieve the password initially set on the instance. Once you change the Administrator password, this process can no longer be used to retrieve the current Administrator password.

== Logging into a Linux virtual machine/instance ==
When you create a new virtual machine/instance using a Linux image, your public key will be injected into the list of public keys that are allowed to login to the instance via SSH. You can then provide your private key to your SSH platform of choice to login to the instance.

To login, you will first need to have network access to the instance. Follow our [[Associate a floating IP]] article and review our [[Create or edit a security group]] article to ensure that:

* Your instance has an IP address that you can reach, such as a public IP address or an IP address you can reach through a virtual firewall appliance.

* Your instance is in a security group that allows SSH from your location.

Once that is completed, open your SSH application of choice. In this article we'll be using PuTTY, though most SSH applications will work.

In PuTTY, enter your Host Name in this format:

'''osname@IPADDRESS'''

For example, if connecting to an Ubuntu instance with a public IP address of 171.85.90.100, the PuTTY hostname would look like: '''ubuntu@171.85.95.100'''

[[File:Putty_HostName.png|border|600px]]

Navigate to the 'Connections', 'SSH', 'Auth', 'Credentials' menu. Then, in the 'Private Key for authentication' field, choose 'Browse' and locate the .ppk file that contains your private key.

[[File:Putty_Credentials.png|border|600px]]

Click 'Open' to start the connect. If prompted to accept the instance's server host key, click 'Accept'. You should be prompted for the private key password you set on your private key. Enter the password to complete the login.

Join an virtual machine to a network

2024-10-10T16:16:09Z

Dtadmin: Dtadmin moved page Join an virtual machine to a network to Join an virtual machine to a network (Advanced Console)

#REDIRECT [[Join an virtual machine to a network (Advanced Console)]]

Join an virtual machine to a network (Advanced Console)

2024-10-10T16:16:09Z

Dtadmin: Dtadmin moved page Join an virtual machine to a network to Join an virtual machine to a network (Advanced Console)

This article will help you join a virtual machine/instance to a network without pre-creating a network port.

In the [[Create a network port]] article, we detailed how to provision a network port in advance of creating a virtual machine/instance. This method works for private networks, but does not work for shared networks, like the Public Internet network. Also, sometimes there is no need to provision a network port in advance, even for private networks. In those cases, a virtual machine/instance can simply be joined directly to an available network. In these cases, the DataTenant cloud will create a port for you with a randomly IP address from that network.

'''''NOTE: Be very cautious when assigning a public IP address to your virtual machine! An instance with a public IP address assigned will be accessible to everyone on the internet. Please be sure you have carefully crafted the security group in use on this port and/or instance to prevent unauthorized access!

== Join your instance to a network ==
Begin creating your instance according to the [[Create a virtual machine]] article.

When you reach the Networking step, select the network you want to connect to.

[[File:Cloud_NetworkSelect.png|border|600px]]

Proceed on through the rest of the instance creation process.

When you are done, the DataTenant cloud will select an available IP address at random, create a port for you, and assign it to your instance.

Create or edit a security group

2024-10-10T16:15:41Z

Dtadmin: Dtadmin moved page Create or edit a security group to Create or edit a security group (Advanced Console)

#REDIRECT [[Create or edit a security group (Advanced Console)]]

Create or edit a security group (Advanced Console)

2024-10-10T16:15:41Z

Dtadmin: Dtadmin moved page Create or edit a security group to Create or edit a security group (Advanced Console)

This article will help you create or edit network security groups.

Security groups are like firewall rules that can be assigned to one or more network interfaces. A security group contains a list of allowed network ports, and any port not listed in the security group will be denied by default. Every network interface/port in must be assigned at least one security group, unless port security is intentionally disabled on that port.

Every project contains a 'default' security group. This group is set to allow all IPv4 and IPv6 traffic in the outbound (egress) direction, but denies all IPv4 and IPv6 traffic in the inbound direction. If you set up your first VM and find you can't ping it, this may very well be why! Following the steps below will allow you to create a new security group for your VM (or edit an existing security group).

== Create and edit a security group ==
Login to the [https://cloud.datatenant.com DataTenant Cloud]. Navigate to the Project, Network, Security Groups menu.

[[File:Cloud_SecurityGroups.png|border|200px]]

To edit an existing security group, choose 'Manage Rules' for the group you want to edit. Otherwise, to create a new security group, choose 'Create Security Group' and give your new security group a unique name.

In the 'Manage Security Group Rules' window, you can add or delete any rules you would like to control the flow of network traffic to/from your network interfaces. For example, a generic 'Web Server' security group might need to allow inbound HTTP and HTTPS traffic. To do this, click 'Add Rule' and select 'HTTP' from 'Rule' dropdown.

[[File:Cloud_AddRule.png|border|600px]]

In the 'CIDR' field, you can choose to only allow this new rule to be valid when coming from a certain IP address or range. For example, a user could choose to only allow HTTP traffic if the source IP address is in the '192.168.0.0/24' network. Leaving the default '0.0.0.0/0' in the 'CIDR' field will allow traffic from any IP address.

Click 'Add' to save the rule.

A fully completed ruleset for a public web server might look something like this:

[[File:Cloud_Ruleset.png|border|800px]]

In this example, the VM using this security group would be able to send all types of traffic inbound, and would allow inbound HTTP, HTTPS, and ICMP traffic from any source. All other inbound traffic would be denied.

For more information about how to change security groups on existing VMs, please review the [[Changing security groups]] article.

Create a volume

2024-10-10T16:15:33Z

Dtadmin: Dtadmin moved page Create a volume to Create a volume (Advanced Console)

#REDIRECT [[Create a volume (Advanced Console)]]

Create a volume (Advanced Console)

2024-10-10T16:15:33Z

Dtadmin: Dtadmin moved page Create a volume to Create a volume (Advanced Console)

This article will help you create a new block storage volume.

Volumes are the 'storage disks' in the DataTenant Cloud, like VMDKs in VMWare ESX or VHDs in Microsoft Hyper-V. If you already have a virtual machine running, you can create blank volumes and attach them to your VM for storage using this article. Otherwise, you can also create volumes from an image, which will contain the operating system you selected for a new VM.

== Create a volume ==
Login to the [https://cloud.datatenant.com DataTenant Cloud]. Navigate to the Project, Volumes, Volumes menu.

[[File:Cloud_Volumes.png|border|200px]]

Click 'Create Volume'. Enter a unique volume name. For example, a volume for a new Windows web server might be called 'WinWeb01_C'.

If you want to create a blank volume (for additional storage on a VM, for example), leave the 'Volume Source' dropdown set to the default. Otherwise, select 'Image' in the dropdown and then select the OS you want to clone from the resulting 'Use image as a source' dropdown.

[[File:Cloud_Volume1.png|border|600px]]

In the 'Type' dropdown, you can choose one of four storage tiers: Standard HDD, Ultra HDD, Standard SSD, and Ultra SSD. If you need help deciding which tier is best for your needs, please review the [[Understanding storage tiers]] article.

In the 'Size' field, enter the size you'd like your new volume to be. When you're done, click 'Create Volume'.

[[File:Cloud_Volume2.png|border|600px]]

Your new volume will now provision. This process can take anywhere from a few seconds (for a blank volume) to up to several minutes (for a large OS, like a Windows Server OS). Once the volume shows as 'Available', you'll be free to use the volume as a boot source for a new VM or to attach it to an existing VM. For more information on how to use your new volume, review the [[Create a virtual machine]] article or the [[Attaching a volume to an existing virtual machine]] article.

Create a virtual machine

2024-10-10T16:15:21Z

Dtadmin: Dtadmin moved page Create a virtual machine to Create a virtual machine (Advanced Console)

#REDIRECT [[Create a virtual machine (Advanced Console)]]

Create a virtual machine (Advanced Console)

2024-10-10T16:15:21Z

Dtadmin: Dtadmin moved page Create a virtual machine to Create a virtual machine (Advanced Console)

This article will help you create a new virtual machine (or instance).

In the DataTenant Cloud, a virtual machine is called an 'instance'. This article will guide you on creating a new instance.

== Prerequisites ==
In order to have a successful instance build, you'll want to make sure you have a few things squared away first.

* Ensure you have a keypair available to use. Your keypair will be used to grant you access to the virtual machine after it's been created.
** If you need help creating a keypair, please review our [[Create a keypair]] article.

* Ensure you have an acceptable security group created for your network purposes.
** If you want, you can accept the 'default' security group to get started and edit this later. But, best practice will always be to ensure you have a security group set up in advance and select it during provisioning. For help doing this, please review our [[Create or edit a security group]] article.

* Create a boot volume.
** You must provision a boot volume in advance or your instance creation will fail. To do this, please review our [[Create a volume]] article.

* Create a network port (optional)
** You can opt to have a network port auto-created during the instance creation process, but the IP address for the instance will be assigned at random. If you want to set a static IP address, please follow our article [[Create a network port]].

== Create a virtual machine (instance) ==
Login to the [https://cloud.datatenant.com DataTenant Cloud]. Navigate to the Project, Compute, Instances menu.

[[File:Cloud_Instances.png|border|200px]]

Click 'Launch Instance'.

Give your new instance a unique name. For instances other than virtual appliances, the name you provide here will be set as the hostname in the resulting instance OS.

[[File:Cloud_Instance1.png|border|600px]]

Click on 'Source'. In the 'Select Boot Source' menu, choose 'Volume'. Select the volume you provisioned earlier.

[[File:Cloud_Instance2.png|border|600px]]

Click on 'Flavor'. Choose whichever flavor will work best for your new instance. If you need help choosing, please review our [[Understanding flavors]] article.

[[File:Cloud_Instances3.png|border|600px]]

For networking, you have two options:

* If you did not provision a network port in advance, click 'Networks' and choose the network you'd like your new instance to be connected to. This is how you can directly assign a public IP address, for example. If you choose this option, a network port will be auto-created for you with a random IP address from that network. Please review the [[Join an virtual machine to a network]] article for more information.

* If you did provision a network port in advance, click 'Network Ports' and select the port you created. You can still assign a public IP address for this instance later if you choose this option. Follow the [[Associate a floating IP]] article for more information.

[[File:Cloud_Instance4.png|border|600px]]

Click on 'Security Groups'. You can leave the security group set to 'default' if you want, but be warned the unmodified default security denies any inbound traffic, so you won't be able to remotely connect (or even ping) your instance with this group unless you modify the security group. If you created a security group more fitting to this instance, select it here.

[[File:Cloud_Instance5.png|border|600px]]

Click on 'Key Pair'. Select your keypair.

[[File:Cloud_Instance6.png|border|600px]]

For the majority of users, the remaining options (Configuration, Server Groups, Scheduler Hints, etc. ) are unnecessary. Once you have defined your name, boot volume, flavor, network, security group, and key pair, you are ready to go. Simply click 'Launch Instance' and your virtual machine will be created!

The instance creation process should take less than a minute, but Windows instances may take a few minutes to complete their setup process, rebooting several times as new virtual hardware is installed.

For assistance in logging in to your new virtual machine, please review our [[Logging in to a new virtual machine]] article.

Create a network port

2024-10-10T16:15:09Z

Dtadmin: Dtadmin moved page Create a network port to Create a network port (Advanced Console)

#REDIRECT [[Create a network port (Advanced Console)]]

Create a network port (Advanced Console)

2024-10-10T16:15:09Z

Dtadmin: Dtadmin moved page Create a network port to Create a network port (Advanced Console)

This article will help you create a static network port.

Network ports are virtual interfaces that can be connected to virtual machines or virtual routers. The DataTenant Cloud can auto-create these network ports for you when you create a new virtual machine or virtual router, but if you prefer to pre-create your own network ports with static IP addresses, this article will illustrate how to do that.

'''''NOTE: Static network ports can only be created on private networks in your project. Static ports cannot be pre-provisioned in shared networks, like the Public Internet network. In order to join a virtual machine/instance directly to the public internet, please review the [[Join an virtual machine to a network]] article.'''''

== Create a network port ==
Login to the [https://cloud.datatenant.com DataTenant Cloud]. Navigate to the Project, Network, Networks menu.

[[File:Cloud_Networks.png|border|200px]]

You will be provided a list of networks that are available in your project. Click on the network you want to make your port in.

Click on the 'Ports' tab.

[[File:Cloud_NetworkPorts.png|border|600px]]

Click 'Create Port'.

Give your network port a unique name. For example, a new web server network port might have a name like 'PubWeb_01_External'. In the 'Specify IP address or subnet' dropdown, choose 'Fixed IP Address'. Enter the static IP address you want to be bound to this port.

[[File:Cloud_NetworkPort1.png|border|400px]]

Click the 'Security Groups' tab and select the security group you'd like this new port to be a member of. If you need help creating or editing a security group for this port, please review the [[Create or edit a security group]] article.

When you've set the security groups, click 'Create'.

[[File:Cloud_NetworkPort2.png|border|600px]]

Your new network port is now created and available to select when provisioning a new virtual machine (or for attaching to an existing virtual machine). If you need help attaching a network port to an existing virtual machine, please review the [[Attach a network port to a virtual machine]] article.

Create a keypair

2024-10-10T16:14:57Z

Dtadmin: Dtadmin moved page Create a keypair to Create a keypair (Advanced Console)

#REDIRECT [[Create a keypair (Advanced Console)]]

Create a keypair (Advanced Console)

2024-10-10T16:14:57Z

Dtadmin: Dtadmin moved page Create a keypair to Create a keypair (Advanced Console)

This article will help you create a keypair.

Keypairs are used for authentication to cloud VMs. A keypair consists of two parts, a public key and a private key, and are specific to a single user. The following steps will explain how to create a single keypair that can be used for authentication against new Windows and Linux cloud VMs. If you follow this process you will end up with three files: a public key, a private key for Linux VMs, and a private key for Windows VMs.

'''''NOTE: While keypairs are not used for Virtual Appliances, you will still be asked to select a keypair as part of the virtual machine creation process.

== Generate a keypair ==
Begin by downloading [https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html PuTTY] and installing it onto a Windows or Mac. This will automatically install PuTTYgen, which is a tool for creating keypairs. Open PuTTYgen, and click the 'Generate' option.

[[File:Putty_Generate.png|border|600px]]

PuTTYgen will prompt you to move your mouse around the screen to provide randomness to the software, allowing for the creation of a truly unique key. When you're done, your public key will be displayed in the 'Key' window. Copy and paste it somewhere safe, like in a text file on your local PC or in your preferred password management solution.

[[File:Putty_PubKey.png|border|600px]]

Enter a password of your choosing in the 'Key Passphrase' window and again in the 'Confirm passphrase' window. Select 'EdDSA' encryption in the 'Parameters' window, and click 'Save private key'. This will prompt you to save a .ppk file somewhere to your computer, and that file will contain your encrypted private key. This copy of your private key will be used to perform secure logins to cloud Linux VMs.

[[File:Putty_PrivKey1.png|border|600px]]

In the 'Conversions' menu, select 'Export OpenSSH Key'. Save the file somewhere to your local computer. This is a copy of your private key that will be used to encrypt Administrator passwords on cloud Windows VMs.

[[File:Putty_PrivKey2.png|border|600px]]

== Import your keypair ==
Login to the [https://cloud.datatenant.com DataTenant Cloud]. Navigate to the Project, Compute, Key Pairs menu.

[[File:Cloud_KeyPair.png|border|200px]]

Select the option to 'Import Public Key'. Give your keypair a unique name, and select 'SSH Key' as the Key Type. Copy and paste the contents of the public key file you created earlier into the 'Public Key' window (you can also select the public key file using the 'Choose File' button if you prefer). Click 'Import Public Key'.

[[File:Cloud_ImportKeyPair.png|border|600px]]

You now have everything you need for secure authentication to the DataTenant Cloud! If you need help using these keys, please review the [[Logging in to a new virtual machine]] article.

Changing security groups

2024-10-10T16:14:46Z

Dtadmin: Dtadmin moved page Changing security groups to Changing security groups (Advanced Console)

#REDIRECT [[Changing security groups (Advanced Console)]]

Changing security groups (Advanced Console)

2024-10-10T16:14:46Z

Dtadmin: Dtadmin moved page Changing security groups to Changing security groups (Advanced Console)

'''This article will explain how to change an existing virtual machine/instance's or network port's security group.'''

Sometimes you may want to change which network security group a virtual machine/instance belongs to, or change an individual network port's security group membership. Changing security group membership will change what ports an instance can communicate over.

== Change an instance security group ==
If an instance only has a single network port, or if you want all network ports connected to an instance to be in the same security group, you can change the security group easily with these steps.

First, login to the [https://cloud.datatenant.com DataTenant Cloud]. Navigate to the Project, Compute, Instances menu.

[[File:Cloud_Instances.png|border|200px]]

In the 'Actions' menu for your instance, choose 'Edit Security Groups'.

[[File:Cloud_EditSecurityGroups.png|border|400px]]

In the box that appears, add/remove security group memberships to fit your needs and choose 'Save' when complete.

[[File:Cloud_EditSecurityGroups2.png|border|600px]]

== Change a network port security group ==
If your instance has multiple network ports, and you want different ports to have different security postures, you can edit each network port's security group membership individually.

To begin, follow the steps from the previous section, but in the 'Actions' menu, choose 'Edit Port Security Groups' instead.

[[File:Cloud_EditSecurityGroups3.png|border|400px]]

In the 'Interfaces' screen, you will see all of the network ports attached to your instance. Click on 'Edit Security Groups' for any available network port to be brought to a screen where you can edit the port's security group membership. Save when completed.

Changing flavors

2024-10-10T16:12:46Z

Dtadmin: Dtadmin moved page Changing flavors to Changing flavors (Advanced Console)

#REDIRECT [[Changing flavors (Advanced Console)]]

Changing flavors (Advanced Console)

2024-10-10T16:12:46Z

Dtadmin: Dtadmin moved page Changing flavors to Changing flavors (Advanced Console)

This article explains how to change what flavor a virtual machine/instance is assigned.

In our [[Understanding flavors]] article, we explain what flavors are and why they are important. If you wish to change which flavor your virtual machine/instance is assigned (and therefore change its underlying virtual hardware and/or compute priority), please follow these steps.

== Change your instance's flavor ==
Login to the [https://cloud.datatenant.com DataTenant Cloud]. Navigate to the Project, Compute, Instances menu.

[[File:Cloud_Instances.png|border|200px]]

In the 'Actions' menu for your instance, choose 'Resize Instance'.

[[File:Cloud_Resize.png|border|200px]]

In the Resize Instance menu, choose the new flavor you'd like to change your instance to. Select 'Resize'.

'''''NOTE: Choosing to resize your instance will result in a reboot! Do not click 'resize' until you are prepared to let your instance reboot.'''''

[[File:Cloud_Resize2.png|border|600px]]

You will see the 'Task' column now display stages of resizing. When they are complete, you will see a 'Confirm' option in the 'Actions' column. '''You must click 'Confirm' to complete the resize operation!'''

[[File:Cloud_Resize3.png|border|600px]]

Once the resize operation is complete, your instance will show that it has the correct virtual hardware specifications and is operating on the correct tier as specified in the flavor.

Attaching a volume to an existing virtual machine

2024-10-10T16:12:34Z

Dtadmin: Dtadmin moved page Attaching a volume to an existing virtual machine to Attaching a volume to an existing virtual machine (Advanced Console)

#REDIRECT [[Attaching a volume to an existing virtual machine (Advanced Console)]]

Attaching a volume to an existing virtual machine (Advanced Console)

2024-10-10T16:12:34Z

Dtadmin: Dtadmin moved page Attaching a volume to an existing virtual machine to Attaching a volume to an existing virtual machine (Advanced Console)

'''This article will explain how to attach a volume to an existing virtual machine/instance'''

Every virtual machine/instance will be provisioned with a boot volume, but sometimes you will want to add additional virtual disks/volumes to your instance. To do this, begin by following the steps in the article [[Create a volume]] to create the volume you will attach to your existing instance.

== Attach your new volume ==
Login to the [https://cloud.datatenant.com DataTenant Cloud]. Navigate to the Project, Compute, Instances menu.

[[File:Cloud_Instances.png|border|200px]]

In the 'Actions' menu for your instance, choose 'Attach Volume'

[[File:Cloud_AttachVolume.png|border|400px]]

In the box that appears, choose the volume you want to attach and click 'Attach Volume'.

[[File:Cloud_AttachVolume2.png|border|600px]]

The new volume/virtual disk should now be visible to the guest OS.

Attach a network port to a virtual machine

2024-10-10T16:12:16Z

Dtadmin: Dtadmin moved page Attach a network port to a virtual machine to Attach a network port to a virtual machine (Advanced Console)

#REDIRECT [[Attach a network port to a virtual machine (Advanced Console)]]

Attach a network port to a virtual machine (Advanced Console)

2024-10-10T16:12:16Z

Dtadmin: Dtadmin moved page Attach a network port to a virtual machine to Attach a network port to a virtual machine (Advanced Console)

'''This article will instruct you on how to create and add additional network interfaces to your existing virtual machine/instances.'''

Every new virtual machine/instance will provision with at least one network interface/port, but in some cases you may want to add additional network interfaces linked to different networks and/or with different security group memberships. In order to do this, begin by creating a new network port through the steps in the [[Create a network port]] article.

== Attach your new network port ==
Login to the [https://cloud.datatenant.com DataTenant Cloud]. Navigate to the Project, Compute, Instances menu.

[[File:Cloud_Instances.png|border|200px]]

In the 'Actions' menu for your instance, choose 'Attach interface'

[[File:Cloud_AttachInterface.png|border|400px]]

In the box that appears, choose 'by Port' in the 'The way to specify an interface' dropdown. Then, select the Port you created earlier in the 'Port' dropdown. Click 'Attach Interface'.

[[File:Cloud_AttachInterface2.png|border|600px]]

''NOTE: If you did not pre-create a network port, you can also use this menu to create a new port by choosing 'by Network (and IP address)' and then selecting the Network you want to provision in and specifying a fixed IP address in the available field. The end result is the same.''

Your new network interface should now be visible in the guest OS.

Associate a floating IP

2024-10-10T16:11:54Z

Dtadmin: Dtadmin moved page Associate a floating IP to Associate a floating IP (Advanced Console)

#REDIRECT [[Associate a floating IP (Advanced Console)]]

Associate a floating IP (Advanced Console)

2024-10-10T16:11:54Z

Dtadmin: Dtadmin moved page Associate a floating IP to Associate a floating IP (Advanced Console)

'''This article explains how to associate a floating IP address to an existing virtual machine/instance.'''

The DataTenant cloud has the option to bind 'floating IP addresses' to virtual machines/instances to allow them to communicate across 'external networks' (like the public internet, for example). Floating IPs can have their bindings to network ports added or removed at will, and when in use, route traffic like in the style of [https://www.comptia.org/content/guides/what-is-network-address-translation Network Address Translation (i.e. NAT)].

The most common usage for floating IP addresses is to bind a public IP address to an instance in your environment that you want to be accessible from the WAN (like a web server, for example). To do this, follow the steps in this article.

== Associate a floating IP address ==
Login to the [https://cloud.datatenant.com DataTenant Cloud]. Navigate to the Project, Compute, Instances menu.

[[File:Cloud_Instances.png|border|200px]]

In the 'Actions' menu for your instance, choose 'Associate Floating IP'.

[[File:Cloud_AssociateIP.png|border|400px]]

Select one of the available IP addresses from the list. Click 'Associate'.

[[File:Cloud_AssociateIP2.png|border|600px]]

'''''NOTE: Be very cautious when associating a public IP address to your virtual machine! An instance with a public IP associated will be accessible to everyone on the internet. Please be sure you have carefully crafted the security group in use on this port and/or instance to prevent unauthorized access!'''''

When the association is complete, you will see two IP addresses listed in the IP Address column of your instance list. The first IP address is the private IP address assigned directly to the instance. This IP address is what will be configured inside the guest OS. The second IP address is the associated IP address, which the DataTenant Cloud will perform [https://www.comptia.org/content/guides/what-is-network-address-translation Network Address Translation] on to allow your instance to send/receive traffic from that second IP address as well.

Main Page

2024-10-09T19:23:54Z

Dtadmin:

DataTenant Knowledgebase

This repository of information should help you with any technical issues you have when using the DataTenant Cloud. Please check out our 'Getting Started' section below to find the most commonly read articles.

== Common Topics ==
Below are some shortcuts to some of the topics that are commonly inquired about.

* [[Create a keypair]]
* [[Create or edit a security group]]
* [[Create a volume]]
* [[Create a network port]] (optional)

If you're just looking to get started, please watch this Getting Started tutorial video. Or, you can read through the steps listed below.

{{#ev:youtube|Igo7nyhchQI}}

== Getting Started ==

* '''Sign in to DataTenant PubCloud'''

Navigate to [https://pubcloud.datatenant.com DataTenant PubCloud] and login. You can select 'Register' to create an account, which will prompt you to use an authenticator app like Microsoft Authenticator or FreeOTP to register an OTP code for 2FA purposes. Or, you simply login using your personal Google, Microsoft, or GitHub account.

[[File:SignIn.png|border|600px]]

* '''Create a Project'''

A project is a logical assortment of virtual machines, virtual networks, virtual volumes, SSH keypairs, security groups, object storage containers, and more. Each project you create will exist simultaneously in all compute regions. Once you've created your project, it will need to be activated before you can create virtual resources.

[[File:CreateProject.png|border|600px]]

''NOTE: If you are a business customer, and would like a free trial, please contact trials@datatenant.com''

In order to activate an account, you must deposit at least twenty dollars, which will become available as a credit that you can apply to any future balances. This can be done via several payment methods, including: credit/debit card, Amazon Pay (available through Stripe), CashApp (available through Stripe), and PayPal. Once your payment is completed, you will see your balance updated to reflect your deposit, and your project will become active.

[[File:AddFunds.png|border|400px]]

To learn more about billing and payments, please review our [[Billing]] article.

* '''Create a Network'''

Before creating a virtual machine, you'll want to create at least one private virtual network.

# On the right hand panel, under 'Cloud', select 'Networking'.
# The top right hand corner, select 'Create Network'.
#*[[File:Network1.png|border|800px]]
# Choose which region you'd like to create your virtual network in. For more information about regions, please review our [[Regions]] article.
# Toggle the option for 'Subnet' to 'On'.
# Toggle the option for 'DHCP' to 'On'.
# Define your subnet in the CIDR field. This can be any private IP range, like ''192.168.0.0/24'' or ''10.0.1.0/24''.
# Specify what DNS servers you'd like to be presented to devices that receive DHCP addresses from this network.
# By default, your private network will use the first address in the subnet as the default gateway. If you'd like to specify a custom gateway, you can toggle the 'Custom Gateway IP' option and specify whichever address you'd like. Likewise, you can narrow the DHCP allocation range or specify additional static routes on this screen.
# Once you've finished, add a name for this private network and select 'Create Network'.
#*[[File:Network2.png|border|800px]]

In order to link your private virtual network to the internet, please review our [[Networking]] article.

* '''Create a Security Group'''

Each virtual network interface in the DataTenant Public Cloud has a set of ACLs applied to it by default that act as a sort of mini-firewall. These ACL sets are called 'security groups', and the default security group only allows outbound network traffic, while denying all inbound network traffic. So, if you want to be able to control your virtual machine through SSH, RDP, VNC, etc. or allow any other inbound communication with your virtual machine, you'll need to create a new security group for this purpose.

# On the right hand panel, under 'Cloud', select 'Networking'.
# The top menu, select 'Security Groups'. At the bottom of that menu, choose 'Create Security Group'.
#*[[File:SG1.png|border|600px]]
# Select which region you'd like this security group to be used in. For more information about regions, please review our [[Regions]] article. Enter a name for your security group and select 'Create Security Group'.
#*[[File:SG2.png|border|600px]]
# Select your newly created security group from the list.
# By default, all egress traffic will be allowed. To create new rules, select 'Add rule'. In the box that appears, you can specify what sort of traffic you want to allow. Anything that isn't explicitly allowed is denied.
## In the Rule menu, you can either select 'All Protocols' to allow TCP, UDP, and ICMP, or you can choose 'Custom Protocol' to choose from one of these options.
## In the description field, you can optionally enter a brief description of what this rule does.
## In the Open Port menu, you select whether you'd like to allow traffic over a single port, a range of ports, or all ports. If you select Port or Port Range, you can either the specific port(s) in the field that appears.
## In the Remote menu, you can choose whether you'd like this rule to be applicable only to a specific group of endpoints or all endpoints. If you choose 'CIDR', you can enter a network subnet in the field that appears. This rule will only apply to endpoints coming from that subnet. To allow all traffic from all sources, enter 0.0.0.0/0. If you choose 'Security Group', you can select a different security group in your project, and this rule will only apply to interfaces in that security group.
## In the EtherType menu, you can select IPv4 or IPv6 for this rule.
#*[[File:SG3.png|border|600px]]
# When you are done, select 'Add Rule'. You can now apply this rule to any virtual interface in your project and the rule will be enforced.

* '''Create a Keypair (Linux Only)'''

If you are going to create new Linux virtual machines, you'll want to create a keypair so you can securely access your virtual machines after their creation.
# To do this, navigate to 'Access' and select 'Generate SSH Key'.
#*[[File:SSH1.png|border|600px]]
# Select which region you'd like the SSH keypair to be used in. For more information about regions, please review our [[Regions]] article. Give your Key Pair a name and select 'Generate'.
#*[[File:SSH2.png|border|600px]]
# A window will appear asking you to save your private key file. Save it somewhere secure, as DataTenant does not have a way to regenerate or access your private key!

Once completed, your public key will be saved and available to inject into your Linux virtual machines during creation. You can also create/import your own keypairs from this screen as well. Please review our [[Keypairs]] article to learn more.

* '''Create a Virtual Machine'''

Now that you've created a private network and a keypair (if you're intending to deploy Linux VMs), you're ready to create your first virtual machine.

# On the right hand panel, under 'Cloud', select 'Server'.
# The top right hand corner, select 'Create a Cloud Server'.
# Choose which region you'd like to create your virtual machine in. For more information about regions, please review our [[Regions]] article.
# A list of images will be available for you to select from in the 'Images' menu. Select one, or if you're wanting to create and select a custom image, please review our [[Images]] article.
# Performance tiers and hardware specifications are available to choose from in the 'Hardware' menu. Select the one that corresponds to what you'd like for your virtual machine. If you're unsure about the different performance tiers, please review our [[Compute Tiers]] article.
# A system disk/root volume will automatically be populated in the 'Volumes' menu. You can select a performance tier from the 'Type' menu', and input whatever size you'd like in the 'Size' field. For more information about disk performance tiers, please review our [[Storage Tiers]] article. You can also add additional volumes here, or you can opt to add them at any later time.
# In the Network menu, de-select the 'Public Network' option and select the 'Private Network' option.
## A 'Private Network' menu will appear. Choose from your available private networks. If there are no networks available to choose from, ensure you are creating your virtual machine in the correct region. You can also select 'Create Network' to create a virtual private network from here.
# If you are creating a Linux virtual machine, select one of your available keypairs in the Authentication menu. This will inject your public key into the Linux VM during creation. If you are creating a non-Linux VM, simply select 'No SSH Key'.
## If there are no keypairs available to choose from, ensure your keypair was created in the same region as the VM you are trying to create.
# You can skip the 'Cloud config' menu unless you have unique customization needs. You can read more about those in our [[Cloud configs]] article.
# If you created specific security group(s) earlier, select 'Add Security Group' in the 'Security Groups' menu and choose the one that you'd like to be applied to this server. If you don't choose a security group, the default security group will be applied, which will allow all outbound traffic but deny all inbound traffic.
# Finally, give your server a name and select 'Create Server'. Your server will be renamed in the guest OS to match whatever name you provide here. Once you click 'Create Server', you will be redirected back to the Server menu, where it will take a few minutes for your virtual server to fully provision.

Main Page

2024-10-09T19:18:32Z

Dtadmin:

DataTenant Knowledgebase

This repository of information should help you with any technical issues you have when using the DataTenant Cloud. Please check out our 'Getting Started' section below to find the most commonly read articles.

== Common Topics ==
Below are some shortcuts to some of the topics that are commonly inquired about.

* [[Create a keypair]]
* [[Create or edit a security group]]
* [[Create a volume]]
* [[Create a network port]] (optional)

If you're just looking to get started, please watch this Getting Started tutorial video. Or, you can read through the steps listed below.

{{#ev:youtube|Igo7nyhchQI}}

== Getting Started ==

* '''Sign in to DataTenant PubCloud'''

Navigate to [https://pubcloud.datatenant.com DataTenant PubCloud] and login. You can select 'Register' to create an account, which will prompt you to use an authenticator app like Microsoft Authenticator or FreeOTP to register an OTP code for 2FA purposes. Or, you simply login using your personal Google, Microsoft, or GitHub account.

[[File:SignIn.png|border|600px]]

* '''Create a Project'''

A project is a logical assortment of virtual machines, virtual networks, virtual volumes, SSH keypairs, security groups, object storage containers, and more. Each project you create will exist simultaneously in all compute regions. Once you've created your project, it will need to be activated before you can create virtual resources.

[[File:CreateProject.png|border|600px]]

''NOTE: If you are a business customer, and would like a free trial, please contact trials@datatenant.com''

In order to activate an account, you must deposit at least twenty dollars, which will become available as a credit that you can apply to any future balances. This can be done via several payment methods, including: credit/debit card, Amazon Pay (available through Stripe), CashApp (available through Stripe), and PayPal. Once your payment is completed, you will see your balance updated to reflect your deposit, and your project will become active.

[[File:AddFunds.png|border|400px]]

To learn more about billing and payments, please review our [[Billing]] article.

* '''Create a Network'''

Before creating a virtual machine, you'll want to create at least one private virtual network.

# On the right hand panel, under 'Cloud', select 'Networking'.
# The top right hand corner, select 'Create Network'.
#*[[File:Network1.png|border|800px]]
# Choose which region you'd like to create your virtual network in. For more information about regions, please review our [[Regions]] article.
# Toggle the option for 'Subnet' to 'On'.
# Toggle the option for 'DHCP' to 'On'.
# Define your subnet in the CIDR field. This can be any private IP range, like ''192.168.0.0/24'' or ''10.0.1.0/24''.
# Specify what DNS servers you'd like to be presented to devices that receive DHCP addresses from this network.
# By default, your private network will use the first address in the subnet as the default gateway. If you'd like to specify a custom gateway, you can toggle the 'Custom Gateway IP' option and specify whichever address you'd like. Likewise, you can narrow the DHCP allocation range or specify additional static routes on this screen.
# Once you've finished, add a name for this private network and select 'Create Network'.
#*[[File:Network2.png|border|800px]]

In order to link your private virtual network to the internet, please review our [[Networking]] article.

* '''Create a Security Group'''

Each virtual network interface in the DataTenant Public Cloud has a set of ACLs applied to it by default that act as a sort of mini-firewall. These ACL sets are called 'security groups', and the default security group only allows outbound network traffic, while denying all inbound network traffic. So, if you want to be able to control your virtual machine through SSH, RDP, VNC, etc. or allow any other inbound communication with your virtual machine, you'll need to create a new security group for this purpose.

# On the right hand panel, under 'Cloud', select 'Networking'.
# The top menu, select 'Security Groups'. At the bottom of that menu, choose 'Create Security Group'.
#*[[File:SG1.png|border|600px]]
# Select which region you'd like this security group to be used in. For more information about regions, please review our [[Regions]] article. Enter a name for your security group and select 'Create Security Group'.
#*[[File:SG2.png|border|600px]]
# Select your newly created security group from the list.
# By default, all egress traffic will be allowed. To create new rules, select 'Add rule'. In the box that appears, you can specify what sort of traffic you want to allow. Anything that isn't explicitly allowed is denied.
## In the Rule menu, you can either select 'All Protocols' to allow TCP, UDP, and ICMP, or you can choose 'Custom Protocol' to choose from one of these options.
## In the description field, you can optionally enter a brief description of what this rule does.
## In the Open Port menu, you select whether you'd like to allow traffic over a single port, a range of ports, or all ports. If you select Port or Port Range, you can either the specific port(s) in the field that appears.
## In the Remote menu, you can choose whether you'd like this rule to be applicable only to a specific group of endpoints or all endpoints. If you choose 'CIDR', you can enter a network subnet in the field that appears. This rule will only apply to endpoints coming from that subnet. To allow all traffic from all sources, enter 0.0.0.0/0. If you choose 'Security Group', you can select a different security group in your project, and this rule will only apply to interfaces in that security group.
## In the EtherType menu, you can select IPv4 or IPv6 for this rule.
#*[[File:SG3.png|border|600px]]
# When you are done, select 'Add Rule'. You can now apply this rule to any virtual interface in your project and the rule will be enforced.

* '''Create a Keypair (Linux Only)'''

If you are going to create new Linux virtual machines, you'll want to create a keypair so you can securely access your virtual machines after their creation.
# To do this, navigate to 'Access' and select 'Generate SSH Key'.
#*[[File:SSH1.png|border|600px]]
# Select which region you'd like the SSH keypair to be used in. For more information about regions, please review our [[Regions]] article. Give your Key Pair a name and select 'Generate'.
#*[[File:SSH2.png|border|600px]]
# A window will appear asking you to save your private key file. Save it somewhere secure, as DataTenant does not have a way to regenerate or access your private key!

Once completed, your public key will be saved and available to inject into your Linux virtual machines during creation. You can also create/import your own keypairs from this screen as well. Please review our [[Keypairs]] article to learn more.

* '''Create a Virtual Machine'''

Now that you've created a private network and a keypair (if you're intending to deploy Linux VMs), you're ready to create your first virtual machine.

# On the right hand panel, under 'Cloud', select 'Server'.
# The top right hand corner, select 'Create a Cloud Server'.
# Choose which region you'd like to create your virtual machine in. For more information about regions, please review our [[Regions]] article.
# A list of images will be available for you to select from in the 'Images' menu. Select one, or if you're wanting to create and select a custom image, please review our [[Images]] article.
# Performance tiers and hardware specifications are available to choose from in the 'Hardware' menu. Select the one that corresponds to what you'd like for your virtual machine. If you're unsure about the different performance tiers, please review our [[Compute Tiers]] article.
# A system disk/root volume will automatically be populated in the 'Volumes' menu. You can select a performance tier from the 'Type' menu', and input whatever size you'd like in the 'Size' field. For more information about disk performance tiers, please review our [[Storage Tiers]] article. You can also add additional volumes here, or you can opt to add them at any later time.
# In the Network menu, select the 'Private Network' option.
## A 'Private Network' menu will appear. Choose from your available private networks. If there are no networks available to choose from, ensure you are creating your virtual machine in the correct region. You can also select 'Create Network' to create a virtual private network from here.
# If you are creating a Linux virtual machine, select one of your available keypairs in the Authentication menu. This will inject your public key into the Linux VM during creation. If you are creating a non-Linux VM, simply select 'No SSH Key'.
## If there are no keypairs available to choose from, ensure your keypair was created in the same region as the VM you are trying to create.

File:SG3.png

2024-10-09T19:18:15Z

Dtadmin:

Main Page

2024-10-09T19:16:43Z

Dtadmin:

DataTenant Knowledgebase

This repository of information should help you with any technical issues you have when using the DataTenant Cloud. Please check out our 'Getting Started' section below to find the most commonly read articles.

== Common Topics ==
Below are some shortcuts to some of the topics that are commonly inquired about.

* [[Create a keypair]]
* [[Create or edit a security group]]
* [[Create a volume]]
* [[Create a network port]] (optional)

If you're just looking to get started, please watch this Getting Started tutorial video. Or, you can read through the steps listed below.

{{#ev:youtube|Igo7nyhchQI}}

== Getting Started ==

* '''Sign in to DataTenant PubCloud'''

Navigate to [https://pubcloud.datatenant.com DataTenant PubCloud] and login. You can select 'Register' to create an account, which will prompt you to use an authenticator app like Microsoft Authenticator or FreeOTP to register an OTP code for 2FA purposes. Or, you simply login using your personal Google, Microsoft, or GitHub account.

[[File:SignIn.png|border|600px]]

* '''Create a Project'''

A project is a logical assortment of virtual machines, virtual networks, virtual volumes, SSH keypairs, security groups, object storage containers, and more. Each project you create will exist simultaneously in all compute regions. Once you've created your project, it will need to be activated before you can create virtual resources.

[[File:CreateProject.png|border|600px]]

''NOTE: If you are a business customer, and would like a free trial, please contact trials@datatenant.com''

In order to activate an account, you must deposit at least twenty dollars, which will become available as a credit that you can apply to any future balances. This can be done via several payment methods, including: credit/debit card, Amazon Pay (available through Stripe), CashApp (available through Stripe), and PayPal. Once your payment is completed, you will see your balance updated to reflect your deposit, and your project will become active.

[[File:AddFunds.png|border|400px]]

To learn more about billing and payments, please review our [[Billing]] article.

* '''Create a Network'''

Before creating a virtual machine, you'll want to create at least one private virtual network.

# On the right hand panel, under 'Cloud', select 'Networking'.
# The top right hand corner, select 'Create Network'.
#*[[File:Network1.png|border|800px]]
# Choose which region you'd like to create your virtual network in. For more information about regions, please review our [[Regions]] article.
# Toggle the option for 'Subnet' to 'On'.
# Toggle the option for 'DHCP' to 'On'.
# Define your subnet in the CIDR field. This can be any private IP range, like ''192.168.0.0/24'' or ''10.0.1.0/24''.
# Specify what DNS servers you'd like to be presented to devices that receive DHCP addresses from this network.
# By default, your private network will use the first address in the subnet as the default gateway. If you'd like to specify a custom gateway, you can toggle the 'Custom Gateway IP' option and specify whichever address you'd like. Likewise, you can narrow the DHCP allocation range or specify additional static routes on this screen.
# Once you've finished, add a name for this private network and select 'Create Network'.
#*[[File:Network2.png|border|800px]]

In order to link your private virtual network to the internet, please review our [[Networking]] article.

* '''Create a Security Group'''

Each virtual network interface in the DataTenant Public Cloud has a set of ACLs applied to it by default that act as a sort of mini-firewall. These ACL sets are called 'security groups', and the default security group only allows outbound network traffic, while denying all inbound network traffic. So, if you want to be able to control your virtual machine through SSH, RDP, VNC, etc. or allow any other inbound communication with your virtual machine, you'll need to create a new security group for this purpose.

# On the right hand panel, under 'Cloud', select 'Networking'.
# The top menu, select 'Security Groups'. At the bottom of that menu, choose 'Create Security Group'.
#*[[File:SG1.png|border|600px]]
# Select which region you'd like this security group to be used in. For more information about regions, please review our [[Regions]] article. Enter a name for your security group and select 'Create Security Group'.
#*[[File:SG2.png|border|600px]]
# Select your newly created security group from the list.
# By default, all egress traffic will be allowed. To create new rules, select 'Add rule'. In the box that appears, you can specify what sort of traffic you want to allow. Anything that isn't explicitly allowed is denied.
## In the Rule menu, you can either select 'All Protocols' to allow TCP, UDP, and ICMP, or you can choose 'Custom Protocol' to choose from one of these options.
## In the description field, you can optionally enter a brief description of what this rule does.
## In the Open Port menu, you select whether you'd like to allow traffic over a single port, a range of ports, or all ports. If you select Port or Port Range, you can either the specific port(s) in the field that appears.
## In the Remote menu, you can choose whether you'd like this rule to be applicable only to a specific group of endpoints or all endpoints. If you choose 'CIDR', you can enter a network subnet in the field that appears. This rule will only apply to endpoints coming from that subnet. To allow all traffic from all sources, enter 0.0.0.0/0. If you choose 'Security Group', you can select a different security group in your project, and this rule will only apply to interfaces in that security group.
## In the EtherType menu, you can select IPv4 or IPv6 for this rule.
# When you are done, select 'Add Rule'. You can now apply this rule to any virtual interface in your project and the rule will be enforced.

* '''Create a Keypair (Linux Only)'''

If you are going to create new Linux virtual machines, you'll want to create a keypair so you can securely access your virtual machines after their creation.
# To do this, navigate to 'Access' and select 'Generate SSH Key'.
#*[[File:SSH1.png|border|600px]]
# Select which region you'd like the SSH keypair to be used in. For more information about regions, please review our [[Regions]] article. Give your Key Pair a name and select 'Generate'.
#*[[File:SSH2.png|border|600px]]
# A window will appear asking you to save your private key file. Save it somewhere secure, as DataTenant does not have a way to regenerate or access your private key!

Once completed, your public key will be saved and available to inject into your Linux virtual machines during creation. You can also create/import your own keypairs from this screen as well. Please review our [[Keypairs]] article to learn more.

* '''Create a Virtual Machine'''

Now that you've created a private network and a keypair (if you're intending to deploy Linux VMs), you're ready to create your first virtual machine.

# On the right hand panel, under 'Cloud', select 'Server'.
# The top right hand corner, select 'Create a Cloud Server'.
# Choose which region you'd like to create your virtual machine in. For more information about regions, please review our [[Regions]] article.
# A list of images will be available for you to select from in the 'Images' menu. Select one, or if you're wanting to create and select a custom image, please review our [[Images]] article.
# Performance tiers and hardware specifications are available to choose from in the 'Hardware' menu. Select the one that corresponds to what you'd like for your virtual machine. If you're unsure about the different performance tiers, please review our [[Compute Tiers]] article.
# A system disk/root volume will automatically be populated in the 'Volumes' menu. You can select a performance tier from the 'Type' menu', and input whatever size you'd like in the 'Size' field. For more information about disk performance tiers, please review our [[Storage Tiers]] article. You can also add additional volumes here, or you can opt to add them at any later time.
# In the Network menu, select the 'Private Network' option.
## A 'Private Network' menu will appear. Choose from your available private networks. If there are no networks available to choose from, ensure you are creating your virtual machine in the correct region. You can also select 'Create Network' to create a virtual private network from here.
# If you are creating a Linux virtual machine, select one of your available keypairs in the Authentication menu. This will inject your public key into the Linux VM during creation. If you are creating a non-Linux VM, simply select 'No SSH Key'.
## If there are no keypairs available to choose from, ensure your keypair was created in the same region as the VM you are trying to create.

File:SG2.png

2024-10-09T19:06:34Z

Dtadmin:

File:SG1.png

2024-10-09T19:05:04Z

Dtadmin: Dtadmin uploaded a new version of File:SG1.png

File:SG1.png

2024-10-09T19:02:21Z

Dtadmin:

Main Page

2024-10-07T20:53:49Z

Dtadmin:

DataTenant Knowledgebase

This repository of information should help you with any technical issues you have when using the DataTenant Cloud. Please check out our 'Getting Started' section below to find the most commonly read articles.

== Common Topics ==
Below are some shortcuts to some of the topics that are commonly inquired about.

* [[Create a keypair]]
* [[Create or edit a security group]]
* [[Create a volume]]
* [[Create a network port]] (optional)

If you're just looking to get started, please watch this Getting Started tutorial video. Or, you can read through the steps listed below.

{{#ev:youtube|Igo7nyhchQI}}

== Getting Started ==

* '''Sign in to DataTenant PubCloud'''

Navigate to [https://pubcloud.datatenant.com DataTenant PubCloud] and login. You can select 'Register' to create an account, which will prompt you to use an authenticator app like Microsoft Authenticator or FreeOTP to register an OTP code for 2FA purposes. Or, you simply login using your personal Google, Microsoft, or GitHub account.

[[File:SignIn.png|border|600px]]

* '''Create a Project'''

A project is a logical assortment of virtual machines, virtual networks, virtual volumes, SSH keypairs, security groups, object storage containers, and more. Each project you create will exist simultaneously in all compute regions. Once you've created your project, it will need to be activated before you can create virtual resources.

[[File:CreateProject.png|border|600px]]

''NOTE: If you are a business customer, and would like a free trial, please contact trials@datatenant.com''

In order to activate an account, you must deposit at least twenty dollars, which will become available as a credit that you can apply to any future balances. This can be done via several payment methods, including: credit/debit card, Amazon Pay (available through Stripe), CashApp (available through Stripe), and PayPal. Once your payment is completed, you will see your balance updated to reflect your deposit, and your project will become active.

[[File:AddFunds.png|border|400px]]

To learn more about billing and payments, please review our [[Billing]] article.

* '''Create a Network'''

Before creating a virtual machine, you'll want to create at least one private virtual network.

# On the right hand panel, under 'Cloud', select 'Networking'.
# The top right hand corner, select 'Create Network'.
#*[[File:Network1.png|border|800px]]
# Choose which region you'd like to create your virtual network in. For more information about regions, please review our [[Regions]] article.
# Toggle the option for 'Subnet' to 'On'.
# Toggle the option for 'DHCP' to 'On'.
# Define your subnet in the CIDR field. This can be any private IP range, like ''192.168.0.0/24'' or ''10.0.1.0/24''.
# Specify what DNS servers you'd like to be presented to devices that receive DHCP addresses from this network.
# By default, your private network will use the first address in the subnet as the default gateway. If you'd like to specify a custom gateway, you can toggle the 'Custom Gateway IP' option and specify whichever address you'd like. Likewise, you can narrow the DHCP allocation range or specify additional static routes on this screen.
# Once you've finished, add a name for this private network and select 'Create Network'.
#*[[File:Network2.png|border|800px]]

In order to link your private virtual network to the internet, please review our [[Networking]] article.

* '''Create a Security Group'''

Each virtual network interface in the DataTenant Public Cloud has a set of ACLs applied to it by default that act as a sort of mini-firewall. These ACL sets are called 'security groups', and the default security group only allows outbound network traffic, while denying all inbound network traffic. So, if you want to be able to control your virtual machine through SSH, RDP, VNC, etc. or allow any other inbound communication with your virtual machine, you'll need to create a new security group for this purpose.

# On the right hand panel, under 'Cloud', select 'Networking'.
# The top menu, select 'Security Groups'. At the bottom of that menu, choose 'Create Security Group'.
#

* '''Create a Keypair (Linux Only)'''

If you are going to create new Linux virtual machines, you'll want to create a keypair so you can securely access your virtual machines after their creation.
# To do this, navigate to 'Access' and select 'Generate SSH Key'.
#*[[File:SSH1.png|border|600px]]
# Select which region you'd like the SSH keypair to be used in. For more information about regions, please review our [[Regions]] article. Give your Key Pair a name and select 'Generate'.
#*[[File:SSH2.png|border|600px]]
# A window will appear asking you to save your private key file. Save it somewhere secure, as DataTenant does not have a way to regenerate or access your private key!

Once completed, your public key will be saved and available to inject into your Linux virtual machines during creation. You can also create/import your own keypairs from this screen as well. Please review our [[Keypairs]] article to learn more.

* '''Create a Virtual Machine'''

Now that you've created a private network and a keypair (if you're intending to deploy Linux VMs), you're ready to create your first virtual machine.

# On the right hand panel, under 'Cloud', select 'Server'.
# The top right hand corner, select 'Create a Cloud Server'.
# Choose which region you'd like to create your virtual machine in. For more information about regions, please review our [[Regions]] article.
# A list of images will be available for you to select from in the 'Images' menu. Select one, or if you're wanting to create and select a custom image, please review our [[Images]] article.
# Performance tiers and hardware specifications are available to choose from in the 'Hardware' menu. Select the one that corresponds to what you'd like for your virtual machine. If you're unsure about the different performance tiers, please review our [[Compute Tiers]] article.
# A system disk/root volume will automatically be populated in the 'Volumes' menu. You can select a performance tier from the 'Type' menu', and input whatever size you'd like in the 'Size' field. For more information about disk performance tiers, please review our [[Storage Tiers]] article. You can also add additional volumes here, or you can opt to add them at any later time.
# In the Network menu, select the 'Private Network' option.
## A 'Private Network' menu will appear. Choose from your available private networks. If there are no networks available to choose from, ensure you are creating your virtual machine in the correct region. You can also select 'Create Network' to create a virtual private network from here.
# If you are creating a Linux virtual machine, select one of your available keypairs in the Authentication menu. This will inject your public key into the Linux VM during creation. If you are creating a non-Linux VM, simply select 'No SSH Key'.
## If there are no keypairs available to choose from, ensure your keypair was created in the same region as the VM you are trying to create.

Main Page

2024-10-07T20:48:21Z

Dtadmin:

Main Page

2024-10-07T20:45:38Z

Dtadmin:

Main Page

2024-10-07T20:38:27Z

Dtadmin: