Nexus Console Tour

N

NexusPrivate Cloud Platform

Your Infrastructure.
Your Control.

A powerful and secure cloud platform for modern teams. Deploy, manage and scale with confidence.

Secure & isolatedBuilt for your environment
Flexible & scalableGrow without limits
Everything in one placeCompute, storage, network and more

Welcome to Nexus

Sign in to your cloud console

User Name

ops-lead

Password

••••••••••

Region

Islamabad — Cluster A

Project / Overview

Islamabad · Cluster A OL

Overview

Project production · last 30 days

All services healthy

Instances

12 / 50

vCPUs

34 / 128

Memory

96 / 256 GB

Block storage

7.4 / 10 TB

Recent activity

web-03	launched	09:41
db-data	snapshot created	08:12
analytics	IAM policy updated	Yesterday
cache-01	stopped	Yesterday

Clusters

Islamabad

Primary · healthy

Lahore

DR · replicating

Shortcuts

⌘K

Command palette

Theme

Light / dark, per user

Clusters

Regions available to this console

Add cluster

Label	Keystone endpoint	Role	Status	Instances
Islamabad	https://keystone.cluster-a.internal:5000/v3	Primary	Healthy	34
Lahore	https://keystone.cluster-b.internal:5000/v3	DR	Healthy	11

Add cluster

Label

Karachi

Keystone URL

https://keystone.cluster-c.internal:5000/v3

Add cluster

What this replaces

A new region used to mean editing a settings file on every node and restarting the dashboard. Here it is a form, validated against a live identity handshake before it saves.

DR Migration

Moving db-primary from Islamabad to Lahore

Step 4 of 7 running

IslamabadPrimary · db-primary

LahoreDR · db-primary-dr

2 volumes · 540 GB mirrored

✓Verify mirroringEvery attached volume is mirroring; a fresh snapshot was taken before staging.rbd mirror image status <pool>/db-dataDone
✓Stage network pre-reqs on DR siteReserves a port with the same MAC and private IP as the primary. Nothing inside the VM changes.Done
✓Adopt mirrored volumes into CinderAdoption only — no data copy. The bytes are already on DR Ceph.Done
4Cut over the mirrorDemotes the primary image and promotes the DR image for every attached volume.rbd mirror image demote <pool>/db-data # primary rbd mirror image promote <pool>/db-data # DRRunning
5Create the DR instanceBoots from the adopted boot volume on the pre-created port.Queued
6Shut down the primaryStops — never deletes — the primary instance.Queued
7Record the migrationTimestamps, IDs and step results logged for audit and fail-back.Queued

⚠Step 4 is the one step that cannot be undone by re-running it. The console flags it before you start, and every other step is safe to repeat.

AI Assistant

Describe what you need in plain English

Plan — not yet applied

>3 web servers, 4GB RAM 2 vCPU each, ubuntu image, on the private network, web-sg security group, install nginx, user deploy password ChangeMe123

Interpreted plan

count: 3 — web-01, web-02, web-03
flavor: m1.medium — matched on 2 vCPU / 4 GB
image: ubuntu-22.04-server
network: private-net · 10.0.0.0/24
security: web-sg
cloud-init: installs nginx, creates user deploy

Quota check

instances: 12 → 15 of 50 room
vCPUs: 34 → 40 of 128 room
memory: 96 → 108 of 256 GB room

Nothing is created until you confirm. The assistant resolves every name against your real catalogue first, so an unknown image or network fails as a message, not a half-built stack.

IAM

Policies that decide what each project sees

Grant access

Effect	Principal	Resource type	Resources
Allow	analytics	Images	ubuntu-22.04, rocky-9
Allow	analytics	Flavors	m1.small, m1.medium
Allow	analytics	Networks	private-net
Implicit deny	analytics	Volume types	— nothing granted
Allow	staging	Instances	all in project

An allow-list, and honest about its scope. A resource stays hidden from a non-admin until a policy names it. This controls what the console shows — it tidies a crowded catalogue down to what a team actually uses. It sits alongside the access-control boundary that governs the API, rather than replacing it.

Instances

Project production · Islamabad

Launch instance

Name	Image	Flavor	IP address	Status
web-01	ubuntu-22.04	m1.medium	10.0.0.11	Active
web-02	ubuntu-22.04	m1.medium	10.0.0.12	Active
db-primary	rocky-9	m1.large	10.0.0.20	Migrating
api-gw-01	debian-12	m1.small	10.0.0.31	Active
cache-01	ubuntu-22.04	m1.small	10.0.0.40	Shut off

Volumes

Name	Size	Type	Attached to	Status
db-data	500 GB	ssd-replicated	db-primary	In use
db-boot	40 GB	ssd-replicated	db-primary	In use
web-01-boot	40 GB	ssd	web-01	In use
archive-2026-08	2 TB	hdd-bulk	—	Available

Networks

Project production · topology and security

Create network

Network	Subnet	Attached	Shared	Status
private-net	10.0.0.0/24	5 ports	No	Active
mgmt-net	10.10.0.0/24	3 ports	No	Active
public-ext	203.0.113.0/24	2 ports	Yes	Active

Security groups

web-sg: ingress 80, 443, 22 — from 0.0.0.0/0
db-sg: ingress 5432 — from web-sg only
mgmt-sg: ingress 22 — from 10.10.0.0/24

Floating IPs

203.0.113.14: web-01 Associated
203.0.113.22: api-gw-01 Associated
203.0.113.37: reserved for DR Held

What Nexus adds on top

Everything stock stays exactly where your team expects it. These five are what Nexus adds on top.

ClustersAdd a region from a form, not a config file. Islamabad and Lahore in one console.

DR MigrationA seven-step, auditable failover that preserves MAC and private IP, and flags the one step that cannot simply be run again.

AI AssistantPlain English to a validated, quota-checked plan. Nothing is created until you confirm.

IAMAllow-list policies that tidy a crowded catalogue down to what each team actually uses.

The console itselfLight and dark as a per-user choice, a command palette on ⌘K, and a sign-in that puts people in the right region.

Standard foundationsCompute, storage, networking, images and identity work on standard APIs your tooling already speaks. Nothing forked to maintain.

Your Infrastructure.Your Control.

Welcome to Nexus

Overview

Clusters

DR Migration

AI Assistant

IAM

Instances

Volumes

Networks

What Nexus adds on top

Your Infrastructure.
Your Control.