First VM 2: launch the instance
Create your first VM in Skyline, attach it to the project network, and choose how you will log in.
After the project network is ready, launch the VM from the Compute tab and attach it to that network.
If you only need dashboard access to the VM, choose a password during creation and log in later from the Skyline console. That path does not require a floating IP, a generated DNS name, an inbound SSH security group rule, or a mustelinet SSH route.
Decide how you will log in
For console-only access, use Login Type Password during instance creation. The password is set inside the VM's operating system and is used with the image's normal console username.
External SSH access to mustelinet VMs uses Pomerium-backed mustelinet SSH, not keypair-based direct SSH from the internet. You usually do not need an SSH keypair for the external tenant access path.
🔐 Console password is not your Skyline password
The password you enter for the VM is a local guest operating system password. It is not your OpenStack, Skyline, GitHub, or mustelinet SSO password.
Create or import an SSH keypair only if:
- Your selected image or launch form requires one.
- You want VM-to-VM SSH inside the same project network.
- Your project has a specific internal workflow that uses SSH keypairs.
If you need one:
- Open Compute, then Key Pairs.
- Create or import an SSH keypair.
- If Skyline generates a private key, download it immediately and keep it private.
See SSH keypairs for the full tenant guidance.
Create the instance
Choose compute shape
Pick the flavor and image that match the workload and quota available in the selected project.
Attach the first VM network
Select the network and subnet created in the previous guide.
Attach security group
Use a group for the workload. Console login does not need an inbound SSH rule.
Console password
Choose Password when you want Skyline console login without exposing SSH.
- Open Compute, then Instances.
- Click Create Instance.
- Choose an availability zone if Skyline asks for one.
- Choose a flavor under Specification.
- Choose an image under Start Source.
- Choose whether the system disk should be deleted with the instance.
- Click Next: Network Config.
- Select the network you created in First VM 1: create a network.
- Select the subnet or virtual interface for that network.
- Attach the security group for the workload. Console login does not require an inbound SSH rule.
- Click Next: System Config.
- Enter the instance name.
- For console login, choose Login Type
Password. - Set Login Name to the default user for the image, such as
ubuntufor Ubuntu. - Enter a strong Login Password and confirm it.
- Choose Keypair only when you created or imported one for this VM and need that workflow.
- Confirm the configuration and create the instance.
Skyline's official instance workflow describes the Network Config step as the place where you add networks, choose the virtual interface, and select security groups.
It also exposes Login Type options in System Config, including Password.
For common image usernames, see Default console usernames.
Wait for the VM
Return to Compute, Instances and wait for the VM to become active.
After the VM is active and has finished booting, open the instance Console action in Skyline and log in with the image username and the password you set during creation.
Use the instance details, console log, or web console if the VM does not boot as expected. Do not continue to floating IP and mustelinet SSH unless you need external tenant access.
