How to submit a Managed Fusion promotion request for a Production environment

Issue:

How do I submit a Managed Fusion promotion request from Staging to Production?

Environment:

Managed Fusion Production environments, post go-live.

Resolution:

Pre-Promotion Steps:

• Implement and test changes in your Development environment
• Promote the tested changes to your Staging environment
• Confirm the tested changes in your Staging environment are stable and complete

Ticket Submission Steps:

Note: Promotion requests are typically fulfilled within 3 business days, assuming all of the required information (see below) has been included in the ticket description.

Note: Everything in Staging will be promoted to Production at the time of request unless specifically indicated as a partial promotion in the ticket description.

• Once the pre-promotion steps have been completed, visit the Lucidworks Support Portal and select Submit a request:
• Select the Managed Services Promotion Request form from the list, and fill out the subject and description fields per the template below:
  
  • Ticket Template:

    • Ticket Subject: Promotion Request - [High level summary] (e.g. Promotion Request - Add new datasource)

• • • Ticket Description:

      • Description:

        1. Nature of the change completed in lower environments:
        2. If multiple apps, which app(s) does the change apply to?:
        3. What part of the system is impacted?: (i.e. specific datasources/index vs query pipeline, files, rules, or profiles)
      • Testing: 
        1. Has this been tested in all lower environments?
        2. How was the new feature tested and validated? (e.g. set of queries this change was tested with, or set of fields that populated as expected)
        3. Is the Staging/Pre-prod environment in sync with Production for the area of the system being changed?
      • Validation:
        1. Is this a partial promotion? (e.g. making a change just to a stage rather than entire pipeline)
        2. How should the Managed Services Team validate the change after promotion? (e.g. set of queries this change was tested with, or set of fields that populated as expected)
      • Performance:
        1. Does this change impact performance? Was any load testing done? (e.g. substantial increase in the index with adding a new collection or introducing wildcards)
      • Special Considerations:
        1. A request to clear a collection without an outage may require scheduling the delete for off-hours /weekends depending on how long it would take to repopulate the collection
        2. If there is a special request to do promotion “off-hours”, please specify the window of time that is considered off-hours
        3. If environments (Staging and Production) are out of sync, the Managed Services Team will need confirmation for the promotion since we cannot be sure that the change was properly tested
        4. On rare occasions, the promotion may cause issues in the environment that will need troubleshooting and time to resolve

 Promotion Steps:

• Lucidworks Managed Services Team promotes outlined changes from Staging to Production
• Managed Services Team notifies customer that changes are live in Production
• Customer confirms and Managed Services Team closes ticket