2019-10-25 Meeting Notes

Date

  

Attendees

Goals

  • Updates on continuing development
  • Review, organize and add to work items


Focus points for this meeting

General update

Discussion items

TimeItemWhoNotes
Welcome
  • Greetings and salutations

Vacations

 Vince vacation


Developer Portal Migration to Drupal 8Ian Lessing (Unlicensed)

Motes: Drupal 8 Migration Notes

Links:

 Waiting to settle the setup with Pantheon. 

 Emailed Shea for an update. On holding pattern until we hear from Shea. Denise is out most of October.

 Shea scheduled a meeting with the Pantheon reps for  . Ian will attend if he can. Notes: Pantheon Hosting Support Meeting 2019-10-10

2019-10-18

Ian met with Pantheon's Matt Paladino yesterday and discussed options for our Drupal 8 developer portal and hosting with Pantheon.

Matt and Ian discussed various options to setup the site and maintain it over time.
Objective was to have Drupal 8 core, Drupal community modules (which includes the Apigee modules) and UCSB Public Affairs theme and modules all as upstreams to our Drupal 8 developer portal. The good news is I think we can do this.

The bad news is we can not have ALL these flow into our developer portal at the click up a few buttons in our Pantheon dashboard.

So... of those three:

  • 1.) Drupal core
  • 2.) Drupal community modules
  • 3.) UCSB Public Affairs theme/distro

Q: Which is the most important to have updates deployed via the pantheon dashboard?
A: Drupal core updates.
Because we want to be able to deploy security updates as quickly and easily as possible.
And we can do this. Pantheon's basic Drupal 8 site template comes with updates from Pantheon deployable via the dashboard.

For community modules....
We'll need to use composer (PHP dependecy manager) and Git to make updates on community modules including the Apigee modules.

For UCSB Public affairs theme & distro
We'll need to define the UCSB Public Affairs code a second "remote" in our Git repo. This will allow us to fold any changes made by UCSB Public Affairs into our codebase with minimal effort.

Note: If we had money to throw at the problem we could purchase a higher tier of service from Pantheon called "Mangaged updates". With this service Pantheon would also manage and deploy updates to Drupal community modules for us.



Reports and alertsDiana Antova 
  • christian.montecino (Unlicensed) Google analytics api usage reports - there is an issue with recording API usage. it does not match the gateway data. (APIGEE-189) Christian will start logging into a text file the API execution to compare with google analytics. 

  • Christian asked the Loggly cloud service provider rep to create a report for us to compare with the Google analytics report. 

  • The free account is expiring and Christian requested and extension. 

  • First we will compare Loggly usage to Google analytics. Then we will move the functionality to Splunk. 

  •  The apigee portal reports more requests than what we see in analytics. But, loggly events show a matching number to what apigee is showing. Christian will continue to look into why it isn't recording the information.
  •  no update
  •  We might require to adjust the flow. If the EV (event value) value is not properly formatted it will not be recorded in Google Analytics. Christian will test it with a static value of 1 and test the week after the numbers. 
  •  Christian made change in the apigee gateway to record the event in google analytics. 
  •  Christian is putting another change as the previous change did not help. Diana will email Jordan Wyatt to ask him for help next week if the numbers are still off. 
  •  Christian - testing new code. Shea has a contact person on google cloud that might help. Shea sent the issue to his contact. Another option is to modify Steven's solution to export by API. We can use AWS, possibly the Redshift database, or another database.
  •  Christian contacted Shea Lovan to get in contact with a google technician for troubleshooting.
  •  Shea will talk to the google person on Monday. Our account is capped at 500 calls per session. Christian requested from the ETS infrastructure team to push data to Splunk. 
  •  Christian is setting up Splunk in the ETS instance. It will provide good reports om usage. 
  •  Splunk is ready for Apigee. Christian will turn it on and add a few new data pieces.

Student Developed Applications
  • GoGaucho Team: Hengyu Lui / Jimmy Lin
  • Professors: Chandra Krintz / Tobias Hollerrer
  • GoGaucho Improvements
      • Good news. The iOS application had the username/password form removed from the application and it no longer retrieves students data which has been screen scraped from GOLD.
      • Jimmy (the Android Developer) is going to add a security token to the Heroku endpoint and will be upgrading the Android application to use it before we next meet.
      • Henry (iOS) will update the iOS application to use the secured Heroku endpoint before the end of the summer.
  •  Today we met with the iOS developer. The user name and password are still there. Asked Henry to remove it. We also found functionality to view meal plans also with screen scraping. We will be asking Gary Scott if there is an API. We will meet with the android developer on Monday and ask him to remove the meal plan information. We gave them by 8/16 to remove the password screens. Henry thinks he can implement the schedules API by start of Fall quarter. 
  •  Meal Plan display in go gaucho - ARIT (Mike Blakemore) is checking with Blackboard what APIs they have available.
  • Diana Antova to follow up with Henry and Jimmy on making the changes  

 All screen scraping is gone now! (smile) 

 Next meeting with the student is on  

 Met today. 2 new students joined the team. Developing a planning tool. Still an issue with the API performance. 

 Steven suggested to start working with them to setup alerts on system status as the app is seeing quite a bit of usage.

 Need to schedule next meeting


Account Cleanup

 Database that collects weekly statistics was moved to a SIST dev server. Will move it to AWS when we get an account, possibly using Lambda functions. For now, the code (powershell) will be put in Github Apigee team.


General Data Usage AgreementKevin Wu
  • Sam Horowitz gave Kevin a heads up that in the IT Council that they are having conversation about developing an overall campus Expected Data Usage policy for how we use data between our departments. It's sort of like if we are the provider passing data to a consumer, then the consumer bears some responsibility for safe guarding the data and using it responsibly. If they share that data with another party, then they are responsible for the 3rd party's appropriate usage of the data.

Private Department Courses Extract API RetirementSteven Maglio

The Registrar's Office has completed enough APIs that it's possible to replace the functionality of the private Department Courses Extract API with 

The Registrar's Office is currently working on a Student Gender Pronoun project which will probably affect the private Department Courses Extract API and the Student Basic Student Info API. That project is set to wrap up in mid-September (before students return). Since there will be communication with API customers of the update to the APIs, it might be best to start the conversation about deprecating the private Department Courses Extract API after the completion of the Gender Pronoun project. This would give us 2 months to think about what's the best way to communicate a deprecation.

 we will need to create an extended Curriculums endpoint that includes the instructor employee id. 

 Diana will schedule a meeting with Gaucho Space and Reg team to discuss necessary changes.

 Reg IS team will be adding pronouns to the student API. And will prioritize the curriculum improvements. Meeting with Gaucho Space scheduled for Nov 5th

Action items

  •