CloudCenter 4.8 has reached End of Life (EOL) as of November 14, 2018. See End of Support Notices for additional context.

Resource Propagation for Federated CCMs

Overview

If you propagate a resource to a Child CCM, that resource is available when that user logs in directly into the Child CCM.

Resource Propagation

The option to automatically propagate a resource on the Parent CCM is available via a flag that you associate with the resource and the target Child CCM. This flag allows you to identify if the resource should be automatically propagated to Child CCM when you update or delete the resource.

Propagation Guidelines

If you opt to propagate resources to Child CCMs, be aware of these prerequisites:

  • You can configure propagation for:

    • One level (child level) below your current level. To propagate to the two levels below (grandchild level), you must follow a two-step process:

      • Propagate to the child level first.

      • From that child level, propagate to the level below (grand-child level).

    • The following CloudCenter resources:

      • Applications (an example and details are provided later in this section)

      • Application Profiles

      • Services

      • Policies (action policy, custom action, scaling policy, and aging policy):

        • The Auto Enable for shared users and the Restrict users from disabling this Policy settings are controlled by the Policy owner.

        • Any policy that is enabled on the parent is also enforced on the child.

  • The propagation is dependent on all configured resources being available in the Child CCM. For example, if any referenced image or service is used it/they must already be configured in the Child CCM.

  • If the Parent CCM is not working for any reason, then you can still use the Child CCM to submit a job. If submitted, your application is deployed and the following conditions apply:

    • CloudCenter will not be able to verify your plan information and quota limits.

    • If your credit runs out, overage fees may apply.

  • You cannot:

    • Modify propagated resources.

    • Delete propagated resources in a Child CCM  if that resource is used or referenced anywhere in CloudCenter.

  • If you update the resource at a later time (using either the UI or API), the change is automatically propagated to the corresponding Child CCM.

  • On the Parent CCM, if you delete:

    • A resource and if this resource is:

      • Used by the Child CCM, it becomes a local resource on the Child CCM.

      • Not used by the Child CCM, it is deleted on the Child CCM as well.

    • An established link, all propagated resources become local resources on the Child CCM.

  • User permissions:

    • Any user on the Parent CCM can propagate a federated resource as long as this user has:

      • Access permission on the link

      • View permission for the resource

    • Any propagated resource on the Child CCM is owned by the user initiating the resource propagation.

    • Different users can maintain copies of propagated resources on the Child CCM.

      • For example, both User1 and User2 initiate their own propagation of App1 to the same Child CCM.

      • On the child CCM, these users will have two propagated App1 resources, one owned by User1 and another by User2, each with their own Permission Control.

      • If App1 is modified on the Parent CCM, the change is auto-propagated to the Child CCM. Both copies of App1 on the child CCM will be affected accordingly.

      • If App1 is deleted on the Parent CCM, both copies of App1 on the Child CCM will continue to exist as local resources on the Child CCM.

Sample Propagation Process (Applications)

Use this reference index for the images in this section:

    • CCM1 = Child CCM and CCM2 = Parent CCM
    • The SleepJob application is propagated from the Parent CCM (CCM2) to the Child CCM (CCM1).
    • The icon in the SleepJob application on CCM1 (Child CCM) indicates that this application is propagated from the Parent CCM.

To propagate a resource from the Parent CCM to the Child CCM, follow this process:

This procedure uses the application resource, SleepJob.


    1. From the Application Tasks dropdown, select Copy to to display the propagation popup.

      This link is only visible if a Child CCM is configured.

    2. In the Copy “SleepJob” to … propagation popup, select the Child CCM checkbox (in this example, childccm1) to which this application must be propagated. If you have multiple linked CCMs, all are displayed in this popup and you can multi-select the applicable CCMs.
    3. Click OK to save your changes. If the changes are accepted by CloudCenter:
      1. You see a green circle with a "√" next to the selected CCM(s) in this popup.

        If you encounter errors during this process, you see a red circle with a "x" along with the corresponding error messages in the adjacent column.

      2. You also receive a notification in the Parent CCM’s Notifications section.

Automatic Propagation

Verify the propagation feature by following this process:

    1. Make changes to the SleepJob application profile in the Parent CCM and save the application.
    2. Access the SleepJob application in the Child CCM and you see the changes propagated to the SleepJob application profile in the Child CCM.
    3. You also receive a notification in the Parent CCM’s Notification section.

Propagation-Related Icons

The resource propagation feature now provides multiple icons and indicators to propagate existing resources.

  • Applications and Application Profiles:
    • The Applications > Actions dropdown list for application or application profile in a Parent CCM displays the Copy To... option.

      •  If an application or application profile is propagated from the Parent CCM, the Child CCM displays the This App is copied from parent manager icon to indicate this state. The Child CCM applications or applications profiles can only be Shared and cannot be deleted by the Child CCM admin.
  • Policies:
    • Copy Policy to Child CCMs – Parent CCM UI > Policies > Enabled Policy (green ON button) > click the Copy this policy to subordinate manager icon
    • If a policy is propagated from the Parent CCM, the Child CCM displays the green ON button in a dull state to indicate that the Child CCM admin cannot change or update this propagated policy. The Child CCM policies can only be Shared and cannot be deleted by the Child CCM admin.

  • Services:
    • The Admin > Services > Actions dropdown list for services in a Parent CCM displays the Copy To... option.
    •  If a Service is propagated from the Parent CCM, the Child CCM displays the This Service is copied from parent manager icon to indicate this state. The Child CCM services can only be Shared and cannot be deleted by the Child CCM admin.

Other References

  • Federated CCM Management
  • Federated Management APIs

    To target the Child CCM from the Parent CCM, use the x-ccid header for all published APIs. See Submit Job for an example (submit deployments from the Parent CCM to the Child CCM).

    Once a link is established and a user has the required permission in a federated CCM environment, this user can use the Parent CCM credentials and DNS name to make REST calls to the Child CCM. Parent CCM users must remember to use the Child CCM Resource ID if they want to configure the corresponding resource on the Child CCM.

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved