$ oc describe quota <your_project_quota_object_name>
During the OpenShift Online (Next Gen) Developer Preview, consult the following sections for frequently asked questions and current usage considerations during the preview period.
OpenShift Online currently runs on the OpenShift 2.X platform. The Next Gen Developer Preview brings OpenShift 3, built on Docker and Kubernetes, to the public cloud in a multi-tenant environment. Learn more.
At this time, the current (v2) and next generation (v3) platforms will be available in parallel. As the OpenShift Online (Next Gen) platform matures, we will publish a sunset plan for the current (v2) offering and provide you with adequate time to migrate your applications to the new platform.
Each user can create a single project with up to 2 GiB memory, 4 CPU cores, and 2 x 1 GiB persistent volumes. For more detailed limits, see the Settings tab on your project’s Overview page in the web console.
You will have access to the OpenShift Online (Next Gen) Developer Preview environment for 30 days, at which point your account will expire.
Your account, applications, and data will be permanently deleted to free up resources for other users when your account expires. This means that you will no longer be able to log in to the web console, authenticate using the OpenShift CLI tools, or access your applications and related data.
If you are interested in trying the OpenShift Online (Next Gen) Developer Preview again, just complete the registration form after your account expires and we will provision a fresh set of resources for you as soon as they become available.
The OpenShift Online (Next Gen) Developer Preview currently supports a number of developer languages and database services, including JBoss Middleware services.
See the OpenShift features page for the list of available languages and services.
Yes, but with a few caveats. For
security reasons, no images
that run processes as root are allowed. Additionally, any Dockerfile
instruction must be mounted with either a persistent volume claim (PVC) or an
EmptyDir at this time. See more
The Developer Preview is a time bound environment which can be used for prototyping or experimenting. We recommend that users do not deploy any production workloads. However, you can deploy a copy of your production workload to see how it performs in the environment.
During our Developer Preview period, OpenShift Online (Next Gen) is FREE!
Not at this time. OpenShift Online (Next Gen) will offer paid tiers when the offering becomes generally available.
During our Developer Preview period, we do not offer a Service Level Agreement (SLA).
Red Hat will provide updates via status.preview.openshift.com.
During the Developer Preview there are no paid or official support channels, however, you can contact the Community Enablement team, create a bug report in Bugzilla, or create a post in the OpenShift Forums.
The best way to contact the community enablement team is to log a request in the Developer Portal. Make sure that you select "Developer Preview" in the Reason for contact drop down.
If you would like to ask a larger group of people for help, including OpenShift users, engineers, and operations team members, you can ask a question using the OpenShift Forums. Please make sure to use the "dev-preview" tag when creating a new post.
Red Hat’s Bugzilla instance can also be used to log security sensitive bug reports (Product=OpenShift Online, Version=3.X, Groups=security) by selecting the "Security Sensitive Bug" flag (automatically selected with the provided link).
The OpenShift Online (Next Gen) Developer Preview offering scopes the inventory of images it provides out of the box with a few considerations in mind, which also apply to any images you choose to import into your project. These conditions are enforced via the OpenShift quotas, limit ranges, and compute resources systems.
A memory limit of 2 GiB is in place. The 2 GiB is spread out across the project’s pods and containers.
Maximum counts are in place for pods, replication controllers, services, and secrets (though some amount of these secrets will be needed by the system’s build and deployer service accounts).
VOLUME instruction must be mounted with either a persistent
volume claim (PVC) or an EmptyDir at this time.
The project associated with a user can allocate up to two PVCs of up to 1 GiB each.
No images that run as root are allowed.
Only the Source-to-Image (S2I) build strategy is allowed for any build configurations imported into your project.
To check your project’s current resource usage, you can log into the web console and view them from the Settings tab of your project’s Overview, or use the following CLI command:
$ oc describe quota <your_project_quota_object_name>
As part of providing a set of templates out of the box, various publicly accessible templates have been updated with a memory limit template parameter with a default setting for the deployments, with the 2 GiB memory limit in mind.
You can change the defaults when instantiating any given template as you see fit, based on the needs of the specific scenario you want to try. However, you must keep in mind the 2 GiB overall memory limit when adjusting the settings of your various deployments.