mcc assignment info
play

MCC assignment info Slides will be available in Noppa Assignment - PowerPoint PPT Presentation

MCC assignment info Slides will be available in Noppa Assignment assistants: Rasmus Eskola (phases 1-2) Teemu Kmrinen (phase 3) Structure of the lecture We will discuss important tools for completing the assignment. Overview of the


  1. MCC assignment info Slides will be available in Noppa Assignment assistants: Rasmus Eskola (phases 1-2) Teemu Kämäräinen (phase 3)

  2. Structure of the lecture We will discuss important tools for completing the assignment. Overview of the assignment phases OpenStack demo Git usage with echo.niksula.hut.fi as remote

  3. Assignment schedule Deadlines at 23:59: Phase 1: 19 Oct 2014 Phase 2: 09 Nov 2014 Phase 3: 07 Dec 2014

  4. Assignment sessions Assignment sessions every Wednesday starting next week, 16:15 in room B353. Not mandatory Assistant will be present for answering questions about the assignment Possibility to discuss with other groups

  5. Assignment overview Developing and deploying a "full stack" application The assignment has a little bit of overlap with the old Network Application Frameworks course. If you have taken the NAF course, you have the option to replace phases 2 and 3 with an alternative assignment. Everybody does assignment 1 The alt assignment is about measurements regarding video playback on mobile devices. More details on the alt assignment later...

  6. Assignment overview Goal is to learn a little bit about every layer in a cloud application You will learn how to: Set up some parts of an OpenStack cloud Configure a Linux server inside a virtual machine instance Write a simple, scalable backend service that provides a REST API Write web and mobile frontends for the application Use a third party API for syncing the address book. It would be a lot of work if you'd have to perfect every little detail in your application: but you don't have to do that... :-) We give you the grading criteria in the assignment description so you should know when it's "good enough"

  7. Phase 1 Simple address book backend service REST API Node.js & express recommended as platform Address book only needs to support a single user Entries stored in a database, MongoDB recommended Deploying to cloud OpenStack & server configuration

  8. Phase 2 Web frontend for the backend written in phase 1 Should be usable but doesn't need to look very fancy Syncing entire address book with a third party address book service Recommended: Google's Contacts API Can be done either via web application or by improving the backend

  9. Phase 3 Mobile frontend Native app, it's not allowed to just make a webview of the phase 2 web application. :) Recommended platform: Android Syncing address book entries with phone's address book Single entries at a time is enough in this phase

  10. Mandatory demos following all assignment phases! Demo session is a short 10 min checkup Prepare to present your work: code, running application, documentation Time reservation opens around submission deadline When doing assignment in pairs both group members need to be present. Noppa news will be sent when time reservation opens

  11. OpenStack Any questions so far?

  12. OpenStack IaaS cloud platform In phase 1 you'll configure your personal OpenStack network Detailed help available in Noppa: Assignments -> Assignment 1 -> OpenStack usage The OpenStack online documentation is also a good resource if you get stuck After that you'll configure an Ubuntu Linux server instance with the software you decide to develop the address book application on You have root access to the VM instances that you spawn, so you can install any needed Ubuntu packages

  13. OpenStack web interface There's both a CLI (command line interface) and web-based interface A lot of overlap; many tasks can be done from both Web interface is at http://quebec.niksula.hut.fi/horizon , but it's behind the school firewall. Can be accessed by tunneling through echo.niksula.hut.fi with a SOCKS proxy, use ssh here

  14. OpenStack command line interface Command line interface can be accessed by setting a few environment variables to contain OpenStack credentials Handy shell script that does this can be downloaded via web interface: Compute -> Access & Security -> API Access -> Download OpenStack RC File

  15. OpenStack command line interface Send the RC file to to echo.niksula.hut.fi using scp: scp openrc.sh mccgroupXX@echo.niksula.hut.fi: and on echo, source it with: source openrc.sh Now you can use the OpenStack command line tools! E.g: nova boot --flavor <flavor_name> --image <image_name> \ --nic net-id=<network_id> --security-group <secgroup_name> \ --key-name <key_name> <instance_name> in order to boot a VM instance.

  16. Live OpenStack demo! We'll take a look at the horizon web interface... To do that we need to set up a SOCKS proxy to echo Before the demo I've already set up the OpenStack network. Also some SSH and Git stuff. SSH keys, SSH config SOCKS proxy Creating a git repo on echo

  17. Thanks for attending! Questions? You can reach me via rasmus.eskola@aalto.fi I'll send out your echo.niksula.hut.fi & OpenStack credentials today We had some issues getting the list of students who registered to the course, so if you don't receive any mail by the end of today, please contact me and we'll sort it out ASAP I'll also send a mail via Noppa news reminding everyone to check they got the credentials Good luck with the assignment! Come to the assignment session next Wednesday if you get stuck!

Download Presentation
Download Policy: The content available on the website is offered to you 'AS IS' for your personal information and use only. It cannot be commercialized, licensed, or distributed on other websites without prior consent from the author. To download a presentation, simply click this link. If you encounter any difficulties during the download process, it's possible that the publisher has removed the file from their server.

Recommend


More recommend