Cloudlet Pools

Cloudlet pools are collections of cloudlets that are defined on a per-regional basis. As an Operator, you may set up a pool membership where only users within the organization associated with the cloudlet pool can access the cloudlets defined for that particular pool. Setting up a cloudlet pool is useful in cases where you need to segment your private (enterprise) cloudlets from your public cloudlets. Cloudlet pools may also be used to isolate cloudlets in the production phase of development and, therefore, will only be available for internal use. Here are some general guidelines to keep in mind when creating cloudlet pools.

  • As an Operator, you must own the cloudlets if you wish to add Developers to a cloudlet pool.

  • If a cloudlet is not part of a pool, it's considered a public cloudlet.

  • Cloudlets assigned to one or more pools are considered private cloudlets.

  • A cloudlet pool may be associated with one or more organizations, allowing users within that organization to access and use those cloudlets to deploy their applications.

  • Organizations not associated with a cloudlet pool will not see or have access to those cloudlets.

  • Targeted organizations that are associated to cloudlet pools may still deploy their applications to other public cloudlets, or to other private cloudlets from other organizations or pools.

  • Operators that are part of a cloudlet pool can view Developer logs and events from the monitoring dashboard.

To create a cloudlet pool

Step 1: Navigate to the Cloudlet Pools submenu, and click the + sign on the top right-hand corner of the screen. The Step 1 Create Cloudlet Pool screen opens.

Create Cloudlet Pool screen

Step 2: Specify a Region. Once specified, the Cloudlets selection box auto-populates with all available cloudlets for that region.

Step 3: Type in a name for the Pool Name.

The Operator field is required and will auto-populate with the name of the organization you are currently managing.

Step 4: From the Cloudlet selection box, highlight the cloudlet(s) and select the single arrow to add individual cloudlets and associate them to the cloudlet pool, or you can select the double arrows to select all available cloudlets at once to add them to the pool.

Step 5: Click Create. The Step 2 Invite Organizations screen opens.
Note: If you wish to invite organizations to your cloudlet pool at a later time, click Cancel. You will be brought back to the Cloudlets Pools screen. Otherwise, proceed to Step 6.

Step 6: RegionPool Name, and Operator fields will all auto-populate with the information specified during Step 1 Create Pool.

Step 7: From the Organization selection box, type in the name of the Organization you wish to invite to include as part of the cloudlet pool.

Step 8: Click Create Invitation. As an OperatorManager or OperatorContributor, you're sending an invite as a query to the DeveloperManager of the organization you wish to invite to become a member of your cloudlet pool. They, in turn, will create a query response to either accept or reject the invite.

Invite Organization to Cloudlet Pool

If you wish to invite additional organizations or remove organizations as members of your cloudlet pool(s), you can do so from the Cloudlet Pools page using the Actions menu, as shown below.

Cloudlet Pools: Actions menu options

Permissions and Roles

The following table outlines the permissions and roles associated with sending and viewing cloudlet pool invitations.


















Example Request/Response Query
mcctl --addr --skipverify org create name=mydevorg  type=developer
Organization created
mcctl --addr --skipverify org create name=myoporg  type=operator
Organization created
mcctl --addr --skipverify cloudletpool create region=US name=mypoolxxx org=myoporg
mcctl --addr --skipverify cloudletpoolinvitation create region=US cloudletpool=mypoolxxx cloudletpoolorg=myoporg org=mydevorg
Invitation created
mcctl --addr --skipverify cloudletpoolresponse create region=US cloudletpool=mypoolxxx cloudletpoolorg=myoporg org=mydevorg decision=accept
Response created
mcctl --addr --skipverify cloudletpoolresponse showgranted region=US cloudletpool=mypoolxxx cloudletpoolorg=myoporg org=mydevorg
- org: mydevorg
  region: US
  cloudletpool: mypoolxxx
  cloudletpoolorg: myoporg
mcctl --addr --skipverify cloudletpoolresponse delete region=US cloudletpool=mypoolxxx cloudletpoolorg=myoporg org=mydevorg
Response deleted
mcctl --addr --skipverify cloudletpoolresponse showpending region=US cloudletpool=mypoolxxx cloudletpoolorg=myoporg org=mydevorg
- org: mydevorg
  region: US
  cloudletpool: mypoolxxx
  cloudletpoolorg: myoporg