Instantly Run An App in the Cloud 2
|Title||Instantly Run An App in the Cloud Using OpenShift Part 2|
|Overview||A follow-on to teaching students about creating apps in an online open source cloud environment - OpenShift. This time students focus on command-line driven tools, and the backends of building and deploying new application code via git.|
What is the rational for this activity? This second portion of the cloud app activity goes a little deeper and focuses on de-facto technologies like ssh / shell-access and git / github. Students will now take their new-found knowledge of the cloud paradigm and start to understand how it can link to a more technically flexible solution set. They can now customize their apps via editing and pushing code via a git publication process.
You will want to have already stepped through this preceding activity: Instantly_Run_An_App_in_the_Cloud
Give Instructor SSH Access:
In order to fully inspect your work, the instructor will need access to your SSH shell that you created. You do not, however, want to give your same private key away. You could, but it is not the best industry practice. Instead, you will want to setup access for the instructors Username and his particular Public Key. Given a Public Key and username access, the instructor can get in with their secret Private Key.
You are encouraged to look up instructions on the web or help each other in the classroom.
You will need:
- THE INSTRUCTORS USERNAME - THE INSTRUCTORS PUBLIC KEY
Instructor will need:
- YOUR APP'S URL or IP ADDRESS
Do this early, so that you can work through issues. Undoubtedly there will be issues and a need to troubleshoot them. You will be graded on your ability to navigate these issues early.
Ensure proper file access rights
Additionally, assure that the user you create for your instructor has the right file and directory access privileges.
- Hint: learn about and use the chmod command
- Read http://www.grymoire.com/Unix/Permissions.html or something like it.
OpenShift Tutorial 2
Priorly, we setup Wordpress blogging software and used it. Now we will dive into more usage of the command line, specifically the rhc command, and what occurs when new code is added via git push. Additionally we will learn how to run it all on your local laptop, so that you can test and develop in a safe environment before you push it live (into production).
Follow this tutorial:
- Optional: Step 6 - SSL Setup
- Take screenshots as you go
- These will be used in your blog hand-in
- Annotate them to make emphasis clear
Get instructor access to your applications SSH shell, so that they can check your work.
Create another blog post, with public URL, that tells:
- What troubles or more info you came across
- This 2nd edition was much more technical and likely lead to some troubleshooting.
- Tell a small story; 1-2 paragraphs.
- Your understanding of what steps OpenShift implements when you do a simple "git push"
- This is the build and deploy process
- Talk about what you added to customize the build process
- The pro's and con's of synchronizing to a Local / Test coding environment
- Why might you want to do testing locally on your laptop, instead of out on the Live / Production cloud app?
- Is the process given in the tutorial cumbersome? Could you find anything better?
|Criteria||Level 1 (fail)||Level 2 (pass)||Level 3 (exceptional)|
|Give instructor SSH access||No access; Didnt attempt||Instructor can login but may not have access to files||Instructor can login and proper user access is given|
|Understand behind-the-scenes workflow of "git push"||No explanation in blog about this||Explanation in the blog of the five steps||Explanation in the blog of the five steps and which files can be customized and when they are triggered (hooked)|
|Add custom build and deployment code||Hook files not edited or working||Customized action_hooks files that are documented in the blog writeup||Customized action_hooks files that are documented in the blog writeup and that tried something *different* from what the tutorial did|
|Synchronize Local and Live Environments (Test vs Prod)||No explanation in blog||Explanation in blog telling the pro's and con's of this method||Explanation in blog telling the difference between Testing and Production, why this is beneficial, and what other methods might be available or better/worse|
What should the instructor know before using this activity?
- Instructor should become familiar with the SSH public/private access mechanism
What are some likely difficulties that an instructor may encounter using this activity?
- Getting yourself SSH access to each students application shell may prove to be some upfront work for yourself
- Make it clear to students that you want this done early (give them a deadline)
- Grade them on this
- Work through it with them; Give them feedback so that they can troubleshoot
- This is a very realistic professional situation:
- Not a lot of direction
- given an end-goal
- need to work with another person (you)
- explorative troubleshooting is likely
- Assure that YOU are crystal clear with sharing SSH access
- Practice it with another teacher or colleague or system
- Otherwise, you could be doing something wrong on your end, and the students wont be able to properly troubleshoot
|Knowledge Area/Knowledge Unit||PD. Parallel and Distributed Computing / PD - Cloud Computing, PBD - Platform-based Development / PBD Web Platforms from ACM_Body_of_Knowledge|
|Topic||Cloud services , Infrastructure as a service, Web programming languages (e.g., HTML5, Java Script, PHP, CSS) , Web platform constraints|
|Level of Difficulty||Difficult|
|Estimated Time to Completion||5-6 hours|
|Materials/Environment||What does the student need? Internet access, Wordpress application from prior activity, Their own laptop with shell access|
|Author||Nick Yeates, Vinh Quốc Nguyễn|
|License||Creative Commons CC-BY|
Suggestions to Open Source Mentors:
Suggestions for an open source community member who is working in conjunction with the instructor.
This work is licensed under a Creative Commons Attribution 4.0 International License