There are a few small points that are important to be aware of before diving into the Catalyst Cloud.
If you experience issues with the Catalyst Cloud, please check to see if the problem(s) are covered further on in this documentation. If no solution is found you will need to raise a support request with the support dropdown in the top right corner of the dashboard.
If you are an organisation with more complex support needs, you may want to consider our premium support.
Our status page shows the state of our services in each region and also informs you about planned maintenance. The status page can be found here: https://catalystcloud.nz/support/status/
If you need help, you can raise a support request with Catalyst via the Support Requests panel.
Most requests are resolved within one business day. If you would like faster response times or additional support, please consider purchasing one of our premium support packages. Our target response times for priority one incidents are listed on the premium support page.
Customers that have a premium support contract from Catalyst have a technical account manager. You should have received the contact details for your account manager when you applied for premium support.
Premium support customers have access to cloud solution architects who can provide guidance on the best way to implement your applications on the cloud. Please contact your account manager to arrange a discussion with a cloud solutions architect.
Catalyst provides training on how to use the Catalyst Cloud in Auckland, Wellington and Christchurch. Upcoming training sessions can be found at https://catalyst.net.nz/training/upcoming-training.
You can also request training to be delivered on your premises or customised for the needs of your team. Please contact Catalyst via our training page to discuss your needs: https://catalyst.net.nz/training-services
The Catalyst Cloud is delivered out of three data centres across New Zealand. On the dashboard, you can specify which data centre to host your resources in depending on your needs, with the dropdown in the top left corner. Each region is completely independent and isolated (each with their own control plane), providing fault tolerance and geographic diversity.
Please visit our website for more information about our national infrastructure: https://catalystcloud.nz/about/national-infrastructure/
PCI DSS certified?
ISO 27001 certified?
NZ Porirua 1
NZ Wellington 2
NZ Hamilton 1
We encourage customers to use Porirua as their primary region, as it has the greatest capacity of all our regions.
The web dashboard has a region selector dropbox on the top left corner. It indicates the current region you are connected to and allows you to easily switch to another region.
The command line interface picks up the region configuration from the
$OS_REGION_NAME environment variable. To define the variable:
The easiest way to get this information set is to download the RC file for your
project from the drop down tab at the top right of the dashboard; and use it as
your source file while working on the command line. The RC file sets a number
of variables like
OS_REGION_NAME. There is a comprehensive tutorial on
how to configure the CLI in our documentation
Alternatively you can use the
--os-region-name option to specify the region
on each call.
The API request you use to authenticate with the Catalyst Cloud allows you to scope a token on a given region. The token can then be used to interact with the API endpoints of the other services hosted in the same region.
The connectivity between compute instances hosted on different regions takes place over either our wide area network (WAN) or the Internet, when allowed by your security groups and network configuration.
Contrary to data traffic within a given region, there are data transfer costs applicable to data traffic between regions.
With the exception of multi-region object storage service, resources are not replicated automatically across regions unless you do so. This provides users the flexibility to introduce replication where required and to fail-over resources independently when needed.
The Catalyst Cloud does not use availability zones as a construct for high-availability within regions. Instead, it uses server groups with anti-affinity polices to ensure compute instances are scheduled in different physical servers.
For more information, please refer to the Anti-affinity groups for HA section of the documentation.
Everything you do on the Catalyst Cloud is in a
project. Use projects to
separate the different things you work on. For example, have a project for each
organisation you work with, or one for each branch of your organisation.
Something done in one project cannot effect any other projects.
You can change which project you’re working in on the dashboard, with the dropdown in the top left corner.
Information on how to invite new people to your project can be found here.
The Catalyst Cloud provides an isolated and multi-tenanted approach to creating
workspaces. These workspaces are typically referred to as a
project but for
historical reasons you may also see them referred to as a
Every project on the Catalyst Cloud has a
project name (a user friendly
name) and a
project id (an auto-generated UUID). There are a number of ways
to find your project ID and name.
If you are using the OpenStack command line interface you have most likely sourced an openrc file, as explained in Command line interface (CLI). If this is the case, you can find your project ID by issuing the following command:
$ echo $OS_PROJECT_ID 1234567892b04ed38247bab7d808e214 $ echo $OS_Project_NAME My-Example-Company-Ltd
Alternatively, you can use the
openstack configuration show command:
$ openstack configuration show -c auth.project_id -f value 1234567892b04ed38247bab7d808e214 $ openstack configuration show -c auth.project_name -f value My-Example-Company-Ltd
You can request the creation of more projects via the Support Requests panel.
On the dashboard, you can change which project you are working on using the dropdown on the top left corner.
The command line interface picks up the project configuration from the
$OS_PROJECT_ID environment variables.
To define these variable:
export OS_PROJECT_NAME="project-name" export OS_PROJECT_ID="UUID"
If a project ID is specified, the project name is not used. If only the project name is specified, the CLI will perform a lookup for the name to find the ID.
Alternatively you can use the
options to specify the project on each call.
Both of these variables are set when your source your project from an RC file in the command line.
The person who signed up to the Catalyst Cloud gets by default the
As a project administrator or moderator, you can invite and remove people from your projects using the Project Users Panel.
Each project comes with an initial
quota that sets a limit on the amount of
cloud resources that you can initially consume. This can be expanded if you
need more resources.
Please refer to the quota section of the documentation for more information on quotas.
While projects are inherently secure, it is considered better to use multiple projects where it’s feasible to do so. For example, it is sensible and useful to separate production workloads from development and testing environments, if only to help mitigate the possibility of human error impacting your business.
Now that you understand the basics of the Catalyst Cloud, lets dive into a hands on example using the web dashboard!