You are browsing a read-only backup copy of Wikitech. The live site can be found at wikitech.wikimedia.org
Help:Cloud VPS project
This page describes what a Cloud VPS project is, how to find existing projects, and how to request and manage new Cloud VPS projects
About Cloud VPS projects
A Cloud VPS project is the basic unit of organization in the Cloud VPS OpenStack environment. The use of the term "project" comes from the upstream documentation of OpenStack.
A Cloud VPS project is:
- a group of zero or more users
- the owner of a 'quota' for the maximum amount of CPU, RAM, and disk storage that can be used to create virtual machine instances
- the owner of virtual machine instances
- the owner of other configuration related to virtual machine instances such as sudo rules, Puppet configuration, and DNS entries.
Find existing Cloud VPS projects
A list of all Cloud VPS projects is available at toolforge:openstack-browser/project/.
Request a new Cloud VPS project
Before you request a new Cloud VPS project, review At-a-glance: Cloud VPS and Toolforge. This will help you determine which development environment is appropriate for your project. Depending on your workflow and available resources, Toolforge may be a better choice.
When you are ready to request a Cloud VPS Project see instructions at the #Cloud-VPS (Project-requests) Phabricator project.
Your Cloud VPS project will be reviewed by Cloud Services administrators.
Reviews of Cloud VPS Project requests
The majority of project requests are approved, but there are some things which will cause further discussion:
- Intentionally limiting membership to a closed group.
- There are valid reasons for a project to limit participants (sensitive data stored/transmitted, infrastructure for larger initiatives, etc). Because we prefer to dedicate resources to inclusive projects, projects that limit membership will require additional scrutiny.
- "Umbrella" projects with a broad scope, such as all the work to be done by an engineering team or a large problem space.
- "Umbrella" projects with broad scopes are difficult to track over time because of organizational changes and lack of continuity in ownership.
- "Laptop in the cloud" projects for a single individual to use as a personal development machine
- Projects for use by single individuals raise a problem of fairness and inclusivity. The Cloud VPS environment does not have the resources to accommodate these projects. The Hardware donation program or another Wikimedia grant program may provide an alternative for some individuals.
- Projects intended to build content wikis
- These are generally not in scope for Cloud VPS, but there may be exceptions such as the Beta Cluster where the content is a necessary side effect of testing at scale.
- Projects needing larger than the default quota.
- The default quota for a new project allows up to 8 instances. New Cloud VPS projects that require more than this will need further discussion. The Cloud VPS environment has limited resources, and these must be distributed fairly between users.
- "Emergency" requests are very unlikely to be granted without the normal review process.
- Cloud VPS administrators do not accommodate emergency requests.
Managing a Cloud VPS project
Communication and support
We communicate and provide support through several primary channels. Please reach out with questions and to join the conversation.
|Phabricator Workboard||#Cloud-Services||Task tracking and bug reporting|
|IRC Channel||#wikimedia-cloud connect
|General discussion and support|
|Mailing List||cloud@||Information about ongoing initiatives, general discussion and support|
|Announcement emails||cloud-announce@||Information about critical changes (all messages mirrored to cloud@)|
|News wiki page||News||Information about major near-term plans|
|Cloud Services Blog||Clouds & Unicorns||Learning more details about some of our work|
|Wikimedia Technical Blog||techblog.wikimedia.org||News and stories from the Wikimedia technical movement|