search

MattToegel / IT490

Samples for Systems Integration Class
4 stars 37 forks source link

Deployment work #38

Open cmm-66 opened 2 years ago

cmm-66 commented 2 years ago

image

cmm-66 commented 2 years ago
Assignment: IT490 - Milestone 2 - Deployment Code Promotion System
Student: Christopher Mayer(cmm66)
Generated: 8/8/2022 11:44:40 PM
Grading Link: Grading
Instructions:
  1. Create a new branch per the Desired Branch Name below
  2. For this milestone, as a team you'll be developing a custom deployment system via bash scripts
  3. You will not be able to use GitHub for migrating files between DEV -> QA -> Prod
  4. If you haven't done so yet, create 4 new VMs replicating the installtion of your DEV lane but mark/label these as QA
    1. You may preemtively do the same for Prod, but it's not required for this deliverable
  5. You will implement a system that allows transferring of files from VM A to VM B
    1. Let me know if it'll be a push (A -> B), a pull system (B <- A), or both
  6. Received files should go to a landing point directory, not directly to the live data
  7. Any live files should be backed up into a backup directory (may want to include the timestamp in the backup name)
  8. Once live files are backed up, overwrite/replace those files with the recently received changes
  9. After this process, the new files should be usable/working on VM B
    1. Note: You may need/want to stop services during this process and start them upon completion
  10. File/Data Support
    1. Server-side code like PHP files
    2. Config files
    3. Any content
    4. DB structural changes (preferrably via record SQL files)
    5. Ensure you don't copy dev data/content to QA/Prod, each lane may need its own config data in some cases
  11. The system should support reverting changes / restoration of backups
    1. Create a new backup of the current/original file
    2. Restore the previously backed up files from a specific "transaction" (note the timestamp comment above)
    3. After the process, the application should be in the state of the backup files (a previous version of whatever was restored)
  12. Create a deployment_system.md file and fill in the content from this deliverable
  13. Add/Commit/Push to the Desired Branch Name
  14. Submit the direct link to the .md file from this branch to Canvas
Grades will be based on how well it works and meets the criteria. 
Points will be deducted for missing sections or not following instructions.
Deliverable 1: Promoting New Files
Status:
Sub-Task 1: Screenshots of the process between VM A and VM B
Caption:

Transfer between servers rabbitmq-1 and rabbitmq-2, showing that testfolder(once empty) received the contents
of testFOlder, which had a file titled 'crap' in it

Deliverable 2: Promoting Updates
Status:
Sub-Task 1: Screenshots of the process between VM A and VM B
Missing Image
Caption: (missing)
Deliverable 3: Restoring previous versions
Status:
Sub-Task 1: Screenshots of file restoration
Missing Image
Caption: (missing)
Deliverable 4: Deployment/Promotion System
Status:
Sub-Task 1: Screenshots of scripts
Missing Image
Caption: (missing)
Sub-Task 2: Walk through the process
Response:

(missing)


Deliverable 5: Contributions
Status:
Sub-Task 1: Team member contribution
Response:

No other member had this running


Sub-Task 2: As a team
Response:

Pain.


Grading Link: Grading