How Subscription Is Consumed

Each OmniDeq feature has a start date and end date and thus it is valid between these dates. The dates are referenced to your deployment system (Appliance or Saas).

(Example : Consider subscription mentioned in the image below, start date of subscription is 17th July, 2020. it means, benefits of subscription are effective from Date: 17th July 2020. and expiry date is calculated as longest end date amongst all features, so in our case it is 31st Dec 2020. (here last date of every feature is same))

Release subscription

  1. Whenever the subscription benefit is to be consumed it gets consumed from the active subscription which is having the nearest expiry date for that benefit. If two subscriptions have the same date, any subscription will be picked up randomly.
  2. It is possible to consume the benefits from multiple active subscriptions for an action to perform simultaneously (Example : simultaneous discovery of 10 hosts in a project).

Note :

Release subscription

(Example : let's take an example in above image, subscription has been released having 3,5,4 unused benefits for discover, transform and cruize respectively, but we can not consider those benefits for any action such as discover, transform etc. as the subscription status is released even though end date is yet to come)

You can view the usage of subscriptions in usage tab

1. Discover feature subscription:

Discover subscription is based on the successful phase 1 discovery of host in a project.

  1. If the phase 1 discovery of a host (either Linux or Windows) is completed successfully then one discover subscription is consumed.
  2. In case of phase 1 discovery failure no discover subscription is consumed.
  3. If you rediscover the same host multiple times, the discover subscription is not consumed.
  4. If the same host is added to different projets, then each host is considered as new and thus the discover subscription is consumed per host.
  5. If you delete and add the same host again then it is considered as new and thus it requires additional discover subscription for phase 1 discovery. Hence please be careful while deleting the successfully discovered node.
  6. There is no separate discover subscription for Windows and Linux hosts

2. Transform feature subscription:

Transform is the procedure of successful dockerization of the process on the host. You can say, the subscription for transformation is successful dockerization process. Transform subscription is based on per process

  1. One transform benefit gets consumed per process if you,

  2. View the dockerfile for the process or

  3. Download the dockerfile for the process or

  4. Build the docker containerize for the process successfully

  5. Only one benefit will get consumed if you view/download the docker file of the process, for any subsequent view/download, the benefit will not be consumed .

  6. If you containerize the same process on different build box multiple times, the benefit will not be consumed .

Overall No additional benefits of subscription will get consumed to view/download docker file and containerization of same process.

(Example : If you have one nginx process in a project and you viewed dockerfile for that process multiple times and also you have containerized that process with 3 buildboxes like buildBox1, buildBox2 and 3. Even though you have done multiple views/download on dockerfile and multiple containerizations on the same process it will consume only one benefit of transform subscription)

  1. If you combine two processes (example PHP + Nginx) and create a container out of it then two benefits will get consume .

  2. Transform feature depends on Discover feature for process data. Hence the transform subscription is not valid with discovery subscription.

  3. The same subscription is applicable for Windows and Linux processes. that is, you can use the benefits of a subscription for both Windows and Linux processes.

  4. One subscription is valid for 10 blueprint creations without consuming additional benefits. You can re-deploy the same application with different blueprint (max 10 blueprints allowed per application ) without consuming the benefit of subscription.

3. Cruize subscription:

Cruize subscription is based on per application

  1. You can define the application, by defining the deployment blue-print. A single cruize subscription is consumed whenever an application is deployed successfully on any cluster.

  2. You can redeploy the same application with different blueprint (max 10 blueprints allowed per application ) without consuming the subscription.

  3. If you delete the application and re-create it again it consumes additional subscription while deployment.