Project lifecycle¶
A project has a type (cloud or corporate), a stage (POC or client), a status and a review date. They are shown in the projects list and changed on the project's Edit project page.
Stage and review date¶
A new project is a POC unless the order says client. A POC is reviewed a month after it is ordered by default; an organization ordering a POC can set its review date up to 3 months ahead. When the stage becomes client, the review date is cleared (a client's review dates come with the statuses below); when it goes back to POC without a review date, one a month ahead is set.
- The stage is changed by a resource manager, a support engineer, a super admin, or the organization's sales rep.
- The review date is changed by a resource manager or a super admin (any date), or by the organization's sales rep (a POC's, up to 3 months after it was made).
For platform users the projects list has a Review column: the date is amber when it is close (a week for a POC, 3 months for a client) and red when it has come.
Statuses¶
| Status | Account | VMs | Connectivity | Resources |
|---|---|---|---|---|
| OK | active | running | working | kept |
| Paused (2 weeks) | blocked | running | blocked | kept |
| Suspended (1 month) | blocked | powered off | blocked | kept |
| Saved (1 month) | deleted | deleted, one full backup of each kept | — | — |
| Archived | nothing left on the platform; the record stays |
The table is what each status stands for. The portal keeps the status and its review date; a change to Paused, Suspended or Saved does not yet block the account, power the VMs off or delete them on the platform. Archiving does: by hand or automatically on its date, it releases everything the project still has, the same as a deletion, on the platforms and in the portal (quotas, networks, subnets, gateways, L2 channels and memberships). Archived is a history record only. A subnet that is not bound to an active project is released.
Statuses are changed by hand by a resource manager or a super admin, on an approved project: OK → Paused → Suspended → Saved → Archived, and back to OK from Paused or Suspended. Each new status gets its review date: Paused at most 2 weeks, Suspended at most 1 month, Saved is archived on its date (a month by default). The one automatic change is Saved → Archived on that date.
A project being deleted has the status Being deleted, and Archived when the deletion is done (see Approvals). When a project has resource pools in more than one zone of the federation, its deletion lists, deletes and checks its resources in every one of them; the project's users, group and access rules go only when nothing of it is left in any zone. A zone that cannot be reached stops the deletion before anything is deleted; it can be run again. A project that was deployed on a platform the portal has no control or no credentials for is not deleted: the deletion stops before anything is touched, with the reason in its plan, and nothing of the project is released until the platform is configured again. A platform in read-only (adoption) mode, and a project that was never deployed, are deleted from the portal only, as before.
stateDiagram-v2
ok --> paused: by hand
paused --> ok
paused --> suspended: by hand
suspended --> ok
suspended --> saved: by hand
saved --> archived: on the review date (automatic) or by handstateDiagram-v2
ok --> paused: by hand
paused --> ok
paused --> suspended: by hand
suspended --> ok
suspended --> saved: by hand
saved --> archived: on the review date (automatic) or by hand
The whole journey of a project¶
flowchart TB
O[Ordered] --> AP[Approved] --> PR[Provisioned] --> OK[OK]
OK --> PA[Paused] --> SU[Suspended] --> SA[Saved] --> AR[Archived]
PA -. back .-> OK
SU -. back .-> OK
OK -. deletion .-> DE[Being deleted] -.-> AR
O -. rejected or cancelled .-> RJ[Rejected / Cancelled]flowchart TB
O[Ordered] --> AP[Approved] --> PR[Provisioned] --> OK[OK]
OK --> PA[Paused] --> SU[Suspended] --> SA[Saved] --> AR[Archived]
PA -. back .-> OK
SU -. back .-> OK
OK -. deletion .-> DE[Being deleted] -.-> AR
O -. rejected or cancelled .-> RJ[Rejected / Cancelled]
A rejected or cancelled request never became a project on the platform; it can be archived to take it out of the lists. Archived projects stay in the portal and are shown on demand.
Archiving an organization¶
An organization is never deleted; it is archived, and only when all its projects are archived (rejected and cancelled requests do not count). Its users are archived with it: no sign-in, no roles, no open invitation. An archived organization can be brought back; its users are not brought back with it.
Expiration notices¶
Expiration notices go to the organization admins: before a production contract ends — 90, 30 and 14 days before, then every day of the last week — and while a POC runs out — every week, then every day of the last week before its review date. They follow the e-mail to organization users switch in Settings → Mail: with it off they are kept on the portal and logged, never sent.
The contract number and date and the balance have been removed from the portal, and a project's contract end date can no longer be edited there. A contract notice goes only for a client project that still has a contract end date recorded.
| Ends | Notices to the organization admins |
|---|---|
| A production contract | 90, 30 and 14 days before; then every day of the last week |
| A POC | every week while it runs out; then every day of the last week |
flowchart LR
n90["−90 days"] --> n30["−30 days"] --> n14["−14 days"] --> n7["−7 … −1 days<br/>every day"] --> end0((contract ends))flowchart LR
n90["−90 days"] --> n30["−30 days"] --> n14["−14 days"] --> n7["−7 … −1 days<br/>every day"] --> end0((contract ends))