Archive for January 19th, 2010
ANGEL Update
Just a quick note to let you know that Cable has another meeting tomorrow with the director of Angel Hosting and a large number of other key players involved in network and hosting issues.
We are wanting to take into the meeting as much new information as possible about the performance of our Angel Learning instance over the weekend and today. If you could fill out the survey that was mentioned in Cable’s message and the previous blog post it would help us greatly. Also, if you could update the Angel Support ticket #596-8312283 with as much specific information as you can, we will take that data to the meeting and put it to good use.
Is Angel performing with the same slowness?
Has Angel gotten worse?
Has Angel improved?
We need to know this through the survey and/or open ticket to continue moving forward.
On a similar note we are working with Angel Support to turn back on the “What’s New” nugget in all of the Winter classrooms. We turned it off at Angel Support’s suggestion to help with the slowness issue some of us are seeing. You can track this conversation with this open ticket at Angel Support. #596-8313119
Add comment January 19, 2010
WAOL ANGEL Performance Update
Audience: WAOL ANGEL Administrators, Faculty and Staff
As many of you know, WashingtonOnline (WAOL) ANGEL has experienced intermittent performance slowdowns since January 7. This note is an update of current system status, next steps, and a request to complete a very short survey.
What’s New:
Current Status (January 15-17):
- 7.4 patch was successfully applied on Friday, Jan 15
- It has been reported that WAOL ANGEL is running normally from Longview, Olympia and Spokane since the 7.4 patch was applied.
- There have been no emails re: WAOL ANGEL performance sent system list serves or to SBCTC staff since Friday, Jan 15.
- The last update to the priority ANGEL ticket (# 596-8312283) was on Friday, Jan 15 (The ticket was likely entered after an ANGEL DBA brought down system for 15 min. while testing performance problem. ANGEL caught it immediately, shut down the test, and the system returned to normal).
- While we hope the 7.4 patch fixed the performance problem, SBCTC and ANGEL are diligently moving forward to diagnose the cause of the problem.
SBCTC / ANGEL Meeting
Most recently SBCTC technical and program staff and ANGEL teams had a productive meeting on Friday, January 15 to discuss performance and recent changes to the WAOL ANGEL hosting environment. We’ve also been in contact with Angel senior technical staff over the weekend.
Outcomes from the meeting included:
- a thorough review of the performance timeline
- a work plan detailing next steps (see “next steps” below)
- leads for SBCTC and ANGEL:
o Frank Leeds (Service Management Director) is SBCTC’s team lead and will oversee and coordinate all technical aspects of diagnosing and testing performance.
o Cable Green (eLearning Director) is SBCTC’s lead on system communication.
o Jason O’Brien (Director, ANGEL Managed Hosting) is lead for ANGEL / Blackboard.
Next Steps
1. URGENT: College ANGEL Domain Administrators: please complete this short survey ASAP.
a. https://www.surveymonkey.com/s/ZFPY66P
b. We will use your responses in our next SBCTC / ANGEL meeting (Jan 20th) … and use the data to update the priority ANGEL ticket.
2. SBCTC collects trouble tickets from Presidium, ANGEL and from survey (see above). Review knowledge base info on proxy from ANGEL. ANGEL provides details on which (if any) of its ASP clients are having performance issues with 7.4 and what solutions have been implemented.
3. Determine if patterns arise with respect to sites and performance types by college and activity in ANGEL.
4. Send out a technology survey to college CIOs to determine what network infrastructure is in place at their campus related to proxy, web application firewalls, and traffic management.
5. Collect and collate survey data – look for patterns, trends that help direct troubleshooting.
6. SBCTC sets up a stress test environment for ANGEL to test with current TCP persistence environment at ANGEL.
7. SBCTC runs stress test against ANGEL in TCP persistence mode.
8. ANGEL sets up a separate instance of IP persistence load balancing for WAOL ANGEL environment.
9. SBCTC changes hostname so that we point to IP persistence based front end for our ANGEL instance.
10. SBCTC runs stress test against ANGEL in IP persistence mode.
11. Review and compare the data from here with (9) to see if obvious benefits are gained from IP persistence or if side effects are too great.
12. If 9 and 11 are inconclusive then we will have to regroup – likely go towards creating an independent path from SBCTC Bellevue to ANGEL without proxy, removing IP persistence, and rerunning stress tests.
13. Document findings: test results, conclusions, standard operating procedure for ANGEL and Washington CTC system integration.
Frequent updates will continue to be posted both to the ELC and ITC lists and to the WAOL blog.
College domain administrators: a reminder to please collect and report (through the ANGEL ticketing system – ticket # 596-8312283) detailed information on any performance problems at your college. Detailed information about your users’ experiences is critical information in solving this issue.
Thank you for your patience and cooperation.
Sincerely,
Cable
Cable Green, PhD
eLearning Director
SBCTC
Add comment January 19, 2010
Choose Your College to Log into WAOL ANGEL
Audience: All WAOL ANGEL Users
What’s New: If you have an account in WAOL ANGEL, you can now only log in through the college where you are enrolled or where you work. This change will allow each college to manage and communicate with its own faculty and students using ANGEL.
What does this mean? If you are logging in from your college web site, you are probably already using your college’s URL. If you have been logging in from the WAOL web site, you now need to choose your college from the drop-down menu first. Then you can log into your college domain as usual.
If you are taking classes or teaching classes for more than one college, you will need to log in to each college separately.
Add comment January 19, 2010
