Google calendar in PT Administrative - OH & Piazzamsakr/15619-s19/recitations/S19... ·...
Transcript of Google calendar in PT Administrative - OH & Piazzamsakr/15619-s19/recitations/S19... ·...
1
● Make use of office hours○ Make sure that you are able to describe the problem and what you
have tried so far○ Piazza Course Staff○ Google calendar in ET○ Google calendar in PT
● Suggestions for using Piazza○ Contribute questions and answers○ Read the Piazza Post Guidelines (@6) before asking questions○ Read Piazza questions & answers carefully to avoid duplicates○ Don’t ask a public question about a quiz question○ Try to ask a public question if possible
Administrative - OH & Piazza
Administrative - Cloud spending
● Suggestion on cloud service usage○ Monitor AWS expenses regularly○ Always do the cost calculation before launching services○ Terminate your instances when not in use○ Stopped instances have EBS costs ($0.1/GB-Month)○ Make sure spot instances are tagged right after launch
Important Notice
● DON’T EVER EXPOSE YOUR AWS CREDENTIALS!○ Github○ Bitbucket○ Anywhere public…
● DON’T EVER EXPOSE YOUR GCP CREDENTIALS!● DON’T EVER EXPOSE YOUR Azure CREDENTIALS!
○ ApplicationId, ApplicationKey○ StorageAccountKey, EndpointUrl
● If your account is compromised, contact the CSP immediately, follow their instructions and post privately on Piazza.
Reflection of Last Week● Conceptual content on OLI
○ Modules 7, 8 & 9 and Quiz 4● Project theme - Containers: Docker and Kubernetes
○ Docker Intro / Profile Service■ Develop a Dockerfile using a provided Spring application
○ Deploying the Profile Service using GCR and GKE■ k8s YAML files, deploying applications to a remote cluster
○ Intro to Helm Charts / Deploying MySQL■ Working with Helm / Tiller, releasing applications using charts
○ WeCloud Chat Microservices■ Deploy the Login and Group Chat services to implement a
subset of the WeChat microservices architecture ○ Autoscaling, Multi-Cloud and Fault Tolerance
■ Replicate the Profile and Login services to Azure. Use HorizontalPodAutoscalers to scale based on CPU utilization.
This Week● Code Review - Project 2.1
○ Due on Wednesday, Feb 20th, 2019, 11:59PM ET● Quiz 5 (OLI Modules 10, 11 & 12)
○ Due on Friday, Feb 22th, 2019, 11:59PM ET● Project 2.3
○ Due on Sunday, Feb 24th, 2019, 11:59PM ET
● Primers released this week○ Team Project - Profiling a Cloud Service○ P3.1 - Storage I/O benchmarking○ P3.1 - NoSQL Primer○ P3.1 - HBase Basics
Team Project - Time to Team Up15-619 Students:● Start to form your teams
○ Choose carefully as you cannot change teams○ Look for a mix of skills in the team
■ Web tier: web framework performance■ Storage tier: deploy and optimize MySQL and HBase■ Extract, Transform and Load (ETL)
● Create a new AWS account only for the team project
15-319 Students:● You are allowed to participate in the team project● Once committed to a team, you cannot quit● Earn a significant bonus for participating in the team project● If you are a 15-319 student and want to participate in the team
project, please email the professor.
7
Team Formation - DeadlinesFollow the instructions in @1053 carefully● By Friday 2/22 at 11:59 PM ET
○ Identify your team members○ One team member should form a team on TPZ and all other team
members should accept the invitation■ Completing this step will freeze your team
● By Saturday 2/23 at 11:59 PM ET○ Create a new AWS account ⇒ only used for the team project○ Update the team profile in TPZ with the
■ New AWS ID aws-id
● By Sunday 2/24 at 11:59 PM ET○ Finish reading the Profiling a Cloud Service primer to get yourself
prepared for the team project
8
●
○○○○○○○
●
●
●
●
10
●
●○○
●●●●
●○○
●
13
P2.1
EC2 VMs
P2.2Containers
This week!
P2.3Functions
●
●●
●
○●
14
●●
○
●○
●○
15
●○○○
●●
●
16
●●
● …○
●○
17
●○○
●○
●●●
18
●○○○
●○
●○
20
●●
○●
○●
○••
21
●●
○●
○○
22
●●●
23
●○
○
○
25
●
●○○○
26
●
●
●
27
●
●●●
○ aws s3 cp video.mp4 s3://your-video-bucket●●
●
●○
●
○ 28
30
● Code Review - Project 2.1○ Due on Wednesday, Feb 20th, 2019, 11:59PM ET
● Quiz 5 (OLI Modules 10, 11 & 12)○ Due on Friday, Feb 22th, 2019, 11:59PM ET
● Team Project - Team Formation○ Due on Friday, Feb 22th, 2019, 11:59PM ET
● Project 2.3○ Due on Sunday, Feb 24th, 2019, 11:59PM ET
Team Formation - DeadlinesFollow the instructions in @1053 carefully● By Friday 2/22 at 11:59 PM ET
○ Identify your team members○ One team member should form a team on TPZ and all other team
members should accept the invitation■ Completing this step will freeze your team
● By Saturday 2/23 at 11:59 PM ET○ Create a new AWS account ⇒ only used for the team project○ Update the team profile in TPZ with the new AWS ID aws-id
● By Sunday 2/24 at 11:59 PM ET○ Finish reading the Profiling a Cloud Service primer to get yourself
prepared for the team project
31
32