Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Date

  

Attendees

Goals

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

...

TimeItemWhoNotes
Welcome
  • Greetings and salutations

Vacations


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.

View file
name2019-10-17 update models for UCSB.pdf
height250

 Diana and Ian met with Cara Kalnow and Matt Paladino from Pantheon to understand what we get for the 6K. They admitted that we just get the hosting which we already pay for through the UCSB contract. If we want Pantheon to take care of the updates for us, we need to commit our website in their Github repo, and they will take care of all updates. They will ask us to test it and a verbal confirmation to proceed. This is a "white glove" service and is 9K/year. Diana and Ian didn't think that we get much from this service as the Apigee modules don't change that often, and we will still have to build the site ourselves. Denise and Ian will start to work on the site.

 Ian emailed Denise and asked her to schedule a meeting the week of the 18th to continue to work on the portal. 


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 - sending traffic to Splunk since last week. The counts match! Christian has requested accounts for us. UCSB has an Enterprise license of Splunk. 
  •  We all have access to Splunk now. https://splunkweb.ets.ucsb.edu/. Christian will ask ETS to give us access to the dataset. Christian will add a documentation page Splunk Integrator to the developer portal, Gateway Admin section.

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

 Conversation with Registrar about student API use. 

Account Cleanup

 Conversation with Registrar about student API use. 

 Diana Antova Emailed CSO to start the security conversation in regards to liability and oversight on student developed apps.


Account Cleanup - on hold

 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 WuSam 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

 performance issue that Diane Soini brought up. every night around 2 am the app pool recycles and the system calls the APIs. We are adding his call to the public APIs to make sure Gaucho Space is not the first one that calls them. 

 Gaucho Space will continue to use the DeptCourses API as they need an extract of all courses. We need to contact Patrick Windmiller to switch to the new APIs. We can ask ESCI and Library as well. 


Uptime monitor check on API system updatesDiana Antova
  • Currently when we deploy a change to the gateway, the uptime monitor reports APIs down if the time coincides with the monitor check.
  • Do we want to be able to pause th emonitorthe monitor?
  • Do we prefer to receive notifications that APIs are down and up?




...