SupportConsoleDevelopersStart a trialContact

3.3. Creating a Container in the Cloud

Abstract

Creating a root container in the cloud uses jCloud to connect to your cloud service, create a new server instance, and install a container on the new server.

Overview

Creating a container in the cloud installs a new Fuse container on a server instance in your cloud. The management console will do the following:
  1. Connect to your cloud service.
  2. Create a new server instance in the cloud.
  3. Download the binary files required to install a Fuse container.
  4. Install the container in the user's home folder.
  5. Start the container and provision all of the specified profiles.
Important
Before you can create a container in the cloud, you must install a cloud service as described in Section 7.2, “Adding a Cloud Provider”.

Procedure

To create a remote root container:
  1. Select Containers from the main menu.
    The Containers page opens.
  2. Click Create Fuse Container.
    The Create Fuse Container page opens.
  3. In the Name field, enter a name for the new container.
  4. If you want to make the new container a registry server check Make container a distributed registry server.
    Important
    It is recommended that if you create a registry server that you do not deploy any other services into the container.
  5. If you want to pass any special flags to the container's JVM:
    1. Check JVM Options.
    2. Enter the options to pass to the JVM in the field next to the check box.
  6. If you need to use a Maven proxy to access the repository containing your Fuse artifacts, check the Maven Proxy URL field and enter the URL for your Maven proxy.
  7. If you want to create multiple instances of the container enter a number greater than one in the Count field.
    When you create multiple containers the container's number is appended to the value specified in the Name field.
  8. Select how the container will report its IP address to other containers from the options in the Resolver drop-down list.
    The options are:
    Local Hostname
    When a requests for the container's location are made, the container's local hostname is returned.
    Local IP
    When a requests for the container's location are made, the container's local IP address is returned.
    Public Hostname
    When a requests for the container's location are made, the container's public hostname address is returned.
    Public IP
    When a requests for the container's location are made, the container's public IP address is returned.
    Important
    Cloud containers that use Local IP or Local Hostmane will not be accessible to containers that do not reside in the same cloud provider.
  9. Click Next.
    The Select profiles to install on the container page opens.
  10. Select the version of profiles you want to use for provisioning the container.
    The value of this drop down defaults to the value set on the Profiles page.
  11. Select one or more profiles to deploy to the container.
  12. Click Next.
    The Select the type of container page opens.
  13. Select Cloud-managed Fuse container.
    Important
    If you have not initiated a cloud service provider in the Cloud tab, this option will not be visible.
  14. Click Next.
    The Cloud Service Configuration page opens.
  15. Select your cloud service from the Cloud Provider drop-down list.
  16. Select a size for the new server instance from the Instance Type drop-down list.
  17. In the Instance Selection section, choose if you want to configure the new server instance by operating system or by image ID.
  18. Click Next.
    The second Cloud Service Configuration page opens.
  19. Configure the server instance that will be created.
    If you are configuring the server instance by operating system:
    1. In the OS Family field, select the operating system the server will use.
    2. In the OS Version field, select the version of the operating system the server will use.
    If you are configuring the server instance by ID and location:
    1. In the Image ID field, enter the ID of the image to use when instantiating the virtual machine.
    2. In the Location ID field, enter the ID of the location where the new server instance will be deployed.
  20. Click Next.
    The second Cloud Service Configuration page opens.
  21. In the User Account field, enter the name of the user used to install the new container on the new server instance.
    The specified user will be created on the new server instance and granted the required permissions to install the container.
  22. If the specified user does not have administrative privileges on the cloud image, check the User does not have administrative access box.
  23. Enter an optional image owner in the Image Owner field.
  24. Enter an optional group tag in the Group Tag field.
  25. Click Finish.
    The wizard closes and the new container will appear in the list of containers. Initially the Active indicator may be red, but should turn green shortly after adding it. The Provisioned indicator may also show gray bars, but should turn green when the specified profiles are fully provisioned.
Red Hat logoGithubRedditYoutubeTwitter

Learn

Try, buy, & sell

Communities

About Red Hat Documentation

We help Red Hat users innovate and achieve their goals with our products and services with content they can trust.

Making open source more inclusive

Red Hat is committed to replacing problematic language in our code, documentation, and web properties. For more details, see the Red Hat Blog.

About Red Hat

We deliver hardened solutions that make it easier for enterprises to work across platforms and environments, from the core datacenter to the network edge.

© 2024 Red Hat, Inc.