Managed Services description
Valid since 13 April 2018
- This document defines the following Canonical service offerings:
- BootStack, a service in which Canonical manages and operates an OpenStack cloud computing environment.
- Managed Kubernetes, a service in which Canonical manages and operates a Kubernetes computing environment.
- “Cloud” means the deployment of the OpenStack cloud computing environment to be managed by Canonical.
- “Cluster” means the deployment of the Kubernetes computing environment to be managed by Canonical.
- “Container Instance” means a container instance running in the Cluster.
- “Environment” means a Cloud or Cluster, as applicable to the particular service offering.
- “Guest Instance” means a virtual machine instance running in the Cloud.
- “Kubernetes” means the container orchestration software known as “Kubernetes” as distributed by Canonical.
- “OpenStack” means the cloud computing software known as “OpenStack” as distributed by Canonical with Ubuntu.
- This document defines the following Canonical service offerings:
The service offering includes access to Canonical’s knowledge base and the services as defined below.
Following Canonical’s building and initializing of the Environment (subject to separate service engagement), Canonical will re-deploy the Environment to reset credentials and validate the deployment process. Canonical will also provide documentation providing further detail on the working relationship with Canonical.
Canonical will remotely operate, monitor, and manage the Environment. Examples include:
- Backing up and restoring of the management infrastructure suite
- Hardware and software failure monitoring and alerting
- Capacity and performance reporting
Patching and updates
Canonical will install applicable (e.g. security) patches and updates from the Ubuntu Cloud Archive to:
- The Ubuntu operating system
- OpenStack or Kubernetes and its dependencies
- OpenStack or Kubernetes Charms
- Other software deployed as part of the Environment
Canonical will provide customer with access to the following applications and/or services:
- The OpenStack or Kubernetes dashboard, API and CLI
- Landscape (restricted to read only access)
- Monitoring and logging system (restricted to read only access)
Canonical will add or remove nodes from the Environment as requested by the customer through a support ticket, provided that the Environment does not go under the minimum size requirement. All Environment nodes must be covered under the BootStack service, so additional fees may apply.
Ubuntu, OpenStack and Kubernetes upgrades
Canonical will ensure the customer’s Environment remains on a supported version of Ubuntu and OpenStack or Kubernetes. In most cases, Canonical will upgrade only to LTS releases where applicable, or to a specific release as agreed with the customer . Support lifecycles can be found at: www.ubuntu.com/info/release-end-of-life
Out of scope
Canonical is not responsible for the following:
- Relating to Guest Instances or Container Instances:
- Managing the operating system or applications running within a Guest Instance or Container Instances.
- Monitoring of Guest Instances.
- Backup or recovery of customer generated data (e.g. any applications or databases running) within Guest Instances or Container Instances.
- Support for the ability to run Guest Instances using images other than those provided by Canonical. (Support for Ubuntu Guest Instances can be purchased as part of Ubuntu Advantage as an add on service.)
- Architectural changes to the Environment.
- Alternative scheduling of updates or upgrades.
- Installation of packages or software other than those in the applicable Ubuntu Main Repository or updates those packages delivered in the Ubuntu Cloud Archive.
- Extended Security Maintenance contract does not constitute a supported version of Ubuntu, OpenStack or Kubernetes.
- Installation of additional components (e.g. LBaaS, VPNaaS, SDN or SDS) beyond the software installed as part of the building of the Environment
- Relating to Guest Instances or Container Instances:
- Service initiation
At the end of the BootStack service term, Canonical will initiate an operational transfer.
Operational transfer includes:
- hand over of all credentials of the hosts and management software to the customer.
- hand over of the administrative credentials of Landscape (The continued operation of Landscape is subject to purchase and agreement of appropriate license terms.)
- coordination of any applicable training (if purchased).
- Ensure there is continuous VPN access for Canonical support personnel to the Environment.
- Keep the utilization parameters per node below the maximum specified in the design document provided by Canonical when the Environment is delivered to the customer.
- Ensure the facility where the Environment is hosted complies with the minimum required measures to function, including but not limited to, connectivity, sufficient power supply, sufficient cooling system, and physical access control to the environment.
- Make at least 12 host nodes continuously available for the Cloud or 10 host nodes continuously available for the Cluster.
Severity levels and target response times
- Once a support request is opened, a Canonical Support Engineer will validate the case information and determine the severity level, working with the customer to assess the urgency of the case.
- Response times will be as set forth in the Service Description for the applicable service offering.
- When setting the severity level, Canonical's Support Team will use the definitions as stated below:
Severity Level 1 — Core functionality not available
Canonical will use continuous effort according to the service level purchased, through appropriate support engineer(s) and/or development engineer(s), to provide a work-around or permanent solution. As soon as core functionality is available, the severity level will be lowered to the new appropriate severity level.
Severity Level 2 — Core functionality severely degraded
Canonical will provide concerted efforts during the applicable business hours to provide the customer with a work-around or permanent solution. As soon as core functionality is no longer severely degraded, the severity level will be lowered to level 3.
Severity Level 3 — Standard support request
Canonical will use reasonable efforts during the applicable business hours to provide the customer with a work-around or permanent solution as soon as possible, balanced against higher severity level cases. If a work-around is provided, Canonical's support engineers will continue to work on developing a permanent resolution to the case.
Severity Level 4 — Non-urgent request
Level 4 requests include cosmetic issues, informational requests, feature requests, and similar matters. Canonical does not provide a timeline or guarantee for inclusion of any feature requests. Canonical will review each level 4 case and determine whether it is a product enhancement to be considered for a future release, an issue to be fixed in the current release or an issue to be fixed in a future release. Canonical will review and respond to information requests with a reasonable level of effort during coverage hours. Canonical may close cases representing level 4 issues after responding if Canonical believes it is appropriate to do so.
- Canonical will use reasonable efforts to respond to support requests made by the customer within the response times set forth below, based on the applicable service and severity level.
- “Business hours” are defined as 08:00 - 18:00 Monday - Friday local to the customer’s headquarters unless another location is agreed. All times exclude public holidays.
|Severity Level 1||2 business hours||1 hour|
|Severity Level 2||4 business hours||4 business hours|
|Severity Level 3||10 business hours||6 business hours|
|Severity Level 4||20 business hours||10 business hours|
|Data plane for customer workloads which are distributed across two regions||99.9%|
|Data plane for customer workloads which are in a single region||99.5%|
|Control plane (OpenStack/Kubernetes API, Web UI and CLI)||99.0%|
Data plane includes:
- Virtualization (for workloads which are architected to not depend on a single compute node)
- Storage (Block & Object)
- Network for instances
Downtime must be directly attributable to Canonical in order for it to count against the Service Level and is measured across a 12 month period. Planned maintenance windows and any requests by the customer are not taken into account when calculating uptime.
Canonical will use reasonable efforts to resolve support cases, but Canonical does not guarantee a work-around, resolution or resolution time.
- The customer is entitled to participate in the Ubuntu Assurance Programme, subject to its terms and conditions. Canonical may update the Assurance Programme and its terms periodically. The current Ubuntu Assurance Programme and its IP indemnification terms are available at our Ubuntu Assurance page: www.ubuntu.com/legal/ubuntu-advantage/assurance
Appendix 1 - Support Process
- Upon commencement of the services, Canonical will provide access for a single technical representative to Landscape, the support portal and the online knowledge base.
- The customer - through their initial technical representative - may select their chosen technical representatives to interface with Canonical based on the number of systems under support as represented in the table below. These technical representatives will hold credentials to the support portal and will act as primary points of contact for support requests.
- The customer may change their specified technical representatives at any time by submitting a support request via the support portal.
Table of machines under support Number of machines under Ubuntu Advantage support Technical representatives 1-20 2 21-50 3 51-250 6 251-1000 9 1001-5000 12 5001+ 15
Submitting support requests
- The customer may open a support request once the customer account has been provisioned within the support portal.
- The customer may submit support cases through the support portal or by contacting the support team by telephone, unless otherwise noted.
- A support case should consist of a single discrete problem, issue, or request.
- Cases are assigned a ticket number and responded to automatically. All correspondence not entered directly into the case, including emails and telephone calls, will be logged into the case with a timestamp for quality assurance.
- When reporting a case, the customer should provide an impact statement to help Canonical determine the appropriate severity level. Customers with multiple concurrent support cases may be asked to prioritize cases according to severity of business impact.
- The customer is expected to provide all information requested by Canonical as we work to resolve the case.
- Canonical will keep a record of each case within the support portal enabling the customer to track and respond to all current cases and allowing for review of historical cases.
To temporarily resolve critical support cases, Canonical may provide a version of the affected software (e.g. package) that applies a patch. Such versions are referred as “hotfixes”. Hotfixes provided by Canonical are valid until 90 days after the corresponding patch has been incorporated into a release of the software in the Ubuntu Archives. However, if a patch is rejected by the applicable upstream project, the hotfix will no longer be supported and the case will remain open.
Canonical will provide support in English. Other languages may be available at certain times.
Canonical may offer to access the customer's supported system using a remote access service. In such case, Canonical will determine which remote access service to use.
Canonical may provide services from any location, including but not limited to the following countries:
- New Zealand
- South Korea
- United Kingdom
- United States of America
Appendix 2 - Management Escalation
In the event of an unsatisfactory service of any kind, there are several ways to escalate this situation to Canonical management.
Feedback at end of case
When a case is closed, a survey will be emailed to the case owner concerning overall experience with Canonical's support. All surveys are reviewed by management.
Ask for a Peer Review
As a normal business practice, Canonical performs peer reviews on a percentage of all cases. Customers can specifically request a peer review on a case within the case comments or by calling the phone number listed in the support portal. An impartial engineer will be assigned to review the case and provide feedback.
- Please request a management escalation within the case itself. A manager will be contacted to review the case and post a response within 1 business day.