PROGRESS

Still 20 hours behind 30/week goal.

Week 4 - Friday - 7/18

hours:8
week: 36/48

Overview:

- fixing destroy scenario to remove a records associated with a scenario

- changing databse schema to make groups easier

- how to add/split players to seperate Teams

- tyring to fix booting two scenarios at once

- learning more git

- made commit for scenario destroying

Week 4 - Thrusday - 7/17

hours:8
week: 26/48

Overview:

-  more student groups

- rails action view for group assignment

- how to launch a scenario with group assignment

Week 4 - Wedensday - 7/16

hours:8
week: 18/48

Overview:

- finished admin home, now working on instructor home

- learning rails security

- more tutorial learning

- doing some git learning

- learning more on models and migrations (updating and changing the database)

- cleaned up admin page a little

- need to fix buckets names

- working on group assignment for instructors

Week 4 - Tuesday - 7/15

hours:8
week: 10/48

Overview:

- working with forms

- working with stylesheets and rails styling pipeline

- doing the admin home page

Week 4 - Monday - 7/14

hours: 2
week: 2/48

Overview:

- did some databse modeling for users

- should we use public keys for users to login to instances, will stick with random generated passwords for now but in the future their should be options for public keys

Week 3 - Sunday - 7/13

Sick today, sinus problems :(

Week 3 - Saturday - 7/12

hours:4
week: 40/48

Overview:

- how to do admin account, set default password on new installation should there be a different login page for admins?

- having trouble with rails routes and views, had to watch more tutorials on them

Week 3 - Friday - 7/11

hours:6.5
week: 36/48

Overview:

- had Skype meeting

- Started to work on user accounts, making admin, instructor and student roles

- should we encrypt AWS credentials, i.e. not put them in plaintext on the instructor machine.

- worked with login page

Week 3 - Thursday - 7/10

hours:7.5
week: 29.5/48

Overview:

- Made first pull request to github.com/edurange/edurange. added functionality for unbooting

- Made scenario status pushable

- Fixed progress pushes during boot

- Watched more video tutorials

- Tyring to understand why boot sometimes fails. Think it is a timing issue with AWS resource creation

- Need to move bucket names into config possibly

- Trying to figure out how to do dynamic configuring

- Studying how scoring works

- How to boot two scenarios at once?

- How to do user management?

Week 3 - Wedensday - 7/09

hours:7
week: 22/48

Overview: 

- watching more video tutorial for Ruby on Rails

- learned who to update status on scenario page

- learned more about calling conventions in concerns

- learned to call update_attribute to make changes to objects

- refactoring unboot code

- weird looping of console output (needed to switch from delay to normal boot when debugging)

- unboot code successful! scenarios can now boot then unboot and reboot as much times as they like

- I think their might need to be another scenario status like if an instructor wants to "pause" the scenario (stopping all the instances but not deleting them) then starting it up back later. Right now unboot deletes all resources and their data.

Week 3 - Tuesday - 7/08

hours:7
week: 15/48

Overview: 

- working on updating scenario page when unbooting

- watching video tutorials of Ruby on Rails to become more familiar with the framework

- learning to add UI elements

- learning to print to the console log

- learning about the faye server

- made stop.sh work for me

- trying to figure out how to update status on scenario page

Week 3 - Monday - 7/07

hours:8
week: 8/48

Overview:

- emailed Stefan to see who is working on the project he said that he didn't think that Nick Stephens would be working on it much. I though Nick was working on it this summer.

- updated journal

- working on unboot script

- learning AWS Ruby SDK in more depth.

- learned to mark volumes as delete on termination for their corresponging instances

- trying to sort out all the dependencies for resource deletion (proving to be rather difficult)

- learning what I can from Davids cleanup-script (which is rather crude but works)

- implenting per scenario AWS resource deletion (not finished, hopefully will be by tomorrow)

Hours Worked

12 weeks goal: 360

Week 1: 20 / 30

behind: 10

Week 2: 4 / 30

behind: 36

Was camping at a family reunion this week and didn't get much work done. Will have to do extra hours the following weeks.

Week 3:

Goal is to catch up on the 36 hours i am behind in this week and week 4 which would mean working 48 hours each week. I will do this by doing six 8 hour days each week.

NOTICE

I was 10 hours short of the 30 I am trying to do each week. I will make up the time in future weeks. The contract for SURF states "It is reasonable for faculty to expect a minimum commitment of 240 hours for the 12 week program" which comes out to 20 hours a week but I am still aiming for 30 hours a week.

Also I am currently sick and I didn't work at all on Tuesday and Wedensday of this week. Also I will be attending a family reunion for the rest of the week in a remote area. I will try to do as much work as I can but if I fall short on hours I will make them up.

Week 01 - Sunday - 6/29

hours:5
week: 20/ 30

Overview:

- Fixing cleanup script to delete resources per scenario

- Learning basics of Ruby on Rails

- Learning about HAML markup

- Learned how to add items to the UI

- Problems writing a bash block in Chef script. Ruby blocks work though

- Trouble booting two scenarios at once

- Scenarios partly boot on errors they should probably delete themselves if an error occurs.

- Learned how to add controllers in Ruby on Rails

Week 01 - Saturday - 6/28

hours:2
week: 15 / 30

Overview:

- Understanding database schema

- Dealing with problems logging into player instances

- Need to look at each Yaml more closely to understand why some scenarios have users on the NAT and others have users on the instance.

Week 01 - Friday - 6/27

hours:3
week: 13 / 30

Overview:

- Troubleshooting strace scenario yaml and cookbook.

- Learning how yaml sets up users

- Trying to understand how scoring works

- Reading the cleanup script

- Unexpected errors on boot (error when local database is not purged)

- How to ssh into each machine in scenario

Week 01 - Thursday - 6/26

hours: 4
week: 10 / 30

Overview:

- Setup this blog.

- Accomplished setting up laptop as instructor machine.

- Successfully launched a scenario.

- Started wriritng yaml and cookbook for the Strace scenario

Week 01 - Wedensday 6-25 - 4 hours - 6/30 total this week

Overview: 

Still trying to get a working instructor machine going. 

Goal:

Set up an instructor machine so I then can integrate the strace scenario.

Accomplished

- Troubleshooted through many errors.

- Read Edrurange code more in depth to understand what it is doing.

- Understanding Ruby better.

- Set up VPC, Internet Gateway, Subnet, Route Table and Network ACL in the East region.

Problems:

- My default AWS region was US-West while Edurange software uses US-East by default. I believe this is why the scenario failed to boot.

- Amazon provides a default VPC, Subnet, etc.. which got deleted by the edurange software when I was cleaning up scenarios so I had to go in and manually recreate these which is probably for the best because I understand them more now.

- Poor documentation for command line tools I am using. Was trying to assign public IP addresses to instances created on the command line but the docs for the command line tools i'm using are not fully correct.

Future

- Create instructor instance in the US-East region and run the software.

Week 01 - Tuesday 6-24 - 2 hours - 2/30 total this week

Overview:

Time was spend trying to set up an instructor machine on my personal AWS account. Goal was not met of getting an instructor machine to boot a scenario. Need to find out what errors are happening.

Goal:

Run a scenario on personal aws account.

Accomplished:

- Created an EC2 instance, put Edurange software on instance.

- Read up on all the different authentication keys for AWS and which ones are used in edurange.

- Placed the correct keys in config/settings.yml

Problems:

- Error messages when trying to boot a scenario.

Future:

- Debug error messages and fix problems.



-