# Portal, the Cloud Director alternative

Know what Portal takes over from Cloud Director, and what you need before starting.

## What your customers see, what you run

Each of your customers has a **portal under your brand**: its domain, your logo, your colors, their language. They see their machines, deploy from your catalog, power them on and off, take snapshots, open their console, and follow their usage against their quotas. They only do what you open to them.

You run everything from the **Cloud services** section of the Naoshift sidebar: sites, tenants, VDCs, catalog, brands, billing. The portal itself has neither database nor logic: everything is decided on the Naoshift side.

## The vocabulary

| In Cloud Director | In Naoshift Portal |
|---|---|
| Organization | **Tenant**: always a new company, isolated from yours |
| Provider VDC | **Site**: a Proxmox VE cluster or an XCP-ng pool, already collected |
| Organization VDC | **VDC**: a tenant's resource pool, networks, quotas, storage tiers and catalog on a site |
| Storage policy | **Storage class** and VDC **tier** |
| Catalog, vApp templates | **Catalog**: items, each placed on a template of each site |
| VM sizing policy | **Size templates**, and the **Catalog sizes only** box |
| VM placement policy | **Placement policies**: groups of nodes |
| Org VDC network | **VDC networks**: VLAN, or VXLAN on Proxmox VE 9 |
| Tenant portal | **Portal under your brand** |

## What Portal does not do

Portal covers a hosting provider's everyday uses, not all of Cloud Director. It provides no edge gateway, NAT or security groups: its building blocks are the pool, the network, the template, the storage and the quota. The allocation model is pay as you go. Tenants do not create their networks: you add them.

## If you start from Cloud Director

Connect your Cloud Director as a source: **Data sources › Connect Cloud Director**, with a read-only account of the System organization. Naoshift reads its structure (organizations, VDCs, networks, edge gateways, vApps, policies, affinity rules) and lays it over the machines of your vCenter source, without counting them twice. Its **Structure** page shows, VDC by VDC, what a Portal VDC will take over, and what Portal does not take over: the services of the edge gateways, left to your network team.

To create a tenant's Portal VDC, start from its Cloud Director VDC: on the tenant's page, **New virtual data center**, choose the site, then the VDC under **Start from a Cloud Director virtual data center**. The form fills itself (networks with the same subnets, the VLAN kept when it is free in the site's pools, quotas, tiers) and the **Differences with Cloud Director** table says, line by line, what is recreated, matched, left to your choice, done by hand, or not carried over. Saving the draft opens the tenant's **migration case**, under **Migrations**: it follows the tenant until its sources are retired, and gives the edge handover sheet for your network team.

Once the VDC is in service, plan the migration from the case. **Analyse against the virtual data center**, check the **Mappings** (the network, tier and placement policy each Cloud Director object lands on), then **Create the checked waves as drafts**: one wave per vApp, each machine placed on a node of its policy, its disks on its tier, its adapters on the networks of the VDC. When a machine arrives, Naoshift recreates its high availability, its affinity rules (a rule marked by Naoshift on Proxmox; a tag for the load-balancer plugin on Xen Orchestra) and its power-on with the host, then adds it to the VDC as soon as a collection shows it. The start order is left to set by hand, except on Proxmox when your action account has `Sys.Modify` on `/`: the wave report says what is left. The case's **Arrivals in the virtual data center** say where each machine stands. Your customer follows the same machines in their portal, under **Migrations**, and validates each one once it has arrived — or reports a problem, which reaches you by e-mail. The case's **Customer acceptance** column, and each wave's **Wave report (CSV)**, keep the trace to hand over.

You can also put your Cloud Director behind your portal first, and change platform later: **Cloud services › Sites › Add a Cloud Director site** (one of its vCenters, collected by your vSphere source), then **Adopt** each tenant's organization VDC from the site's page. Your customers find their machines in your branded portal, and their console — no other gesture for now; nothing is created in Cloud Director, and the machines follow it at each collection. Each virtual data center opens the console with ITS vCenter account, which holds the console of its own machines and nothing more: prepare these accounts once from the site's page (with the vCenter SSO administrator, erased right after), or enter one you created yourself on the virtual data center's page. Naoshift checks each account before it serves, then every day.

## Isolation is built on the hypervisor

For each VDC, Naoshift itself creates on the platform the resource pool, the dedicated network and a native account whose rights stop at the VDC. Every action of a tenant leaves with its VDC's account: the hypervisor bounds it, and its log names it.

## What Naoshift enables first

- **Hosting mode**: the **Cloud services** section appears in your sidebar.
- **The Portal isolation (sites and VDCs) capability** for your company: it lets Naoshift create pools, networks and accounts on your infrastructure.
- **Your front instance**: the website that serves your portals.

## Who does what in your team

Under **Settings › Cloud services › Portal team**, each team member holds one level: **Administration**, **Operations** or **Billing**. The menu only shows what their level opens. Acting on the hypervisor also takes the **Infrastructure operator** role and the **Portal isolation (sites and VDCs)** capability, like any action in Naoshift.

### The Cloud services section does not appear

Hosting mode is not active for your company yet, or your account holds no access level. The **MSP mode** card in **Settings › Organization › Company** says whether the mode is active: if not, ask Naoshift.

### A colleague sees the section, but not all its menus

That is their access level: Billing sees neither **Branding** nor **Maintenance**, Operations sees neither **Billing** nor **Portal team**. An administrator changes their level under **Portal team**.
