We are very excited to announce our sites integration with Clef. Clef replaces passwords with a simple and secure way to log in with your smartphone. Download the app and try it with your AllisonHouse account today!
How It Works
- You create a profile that will never leave your phone.
- Clef will then use that profile to generate a new digital signature every time you log in.
- Sync with Clef Wave to send your signature and identity yourself.
- The Clef app generates a public and private key. The private key will stay on your phone to generate the unique signature to identify you
- After you sync the Clef Wave, your digital signature is sent to Clef. Clef verifies the signature and connects you to our servers to log in.
- Download the Clef iOS App or Clef Android App.
- Sign up for Clef using your AllisonHouse account email address.
- Log in to your AllisonHouse account using the Clef “Log in with your phone” button.
We received this from the FAA a short time ago:
Please ensure widest dissemination as deemed necessary:
– *Vermilion 26C (VNP)*: Platform is shut-in; slated to be plugged and abandoned. AWOS is *permanently* out-of-service. FAA will be exploring possible alternatives to replace VNP with Gulf industry partners.****
– *East Breaks 165 (EMK): *New telephone access number is 281-921-0775.****
– *Ship Shoal 354 (SQE): *FAA received approval from Mexico to use VHF; now awaiting FCC approval. Upon receipt of FCC license, FAA will commission AWOS. SS 354 will replace ST 301B AWOS.****
– *South Timbalier 301B (STZ): *AWOS will be permanently disabled with activation of SQE. FAA will remove AWOS when SQE is commissioned. ST 301B is projected to be plugged and abandoned in 2014.****
– *Cameron, LA:* FAA received owner/operator approval to install AWOS in Cameron, LA. This facility will replace the decommissioned AWOS at East Cameron 47JP (CMB).****
– FAA has completed formal operational and safety inspections at the following locations in 2013: Garden Banks 668/Gunnison Spar (GUL); West Cameron 368A (CRH); Eugene Island 215B (EIR); Brazos 133B (BBF).****
To display the most recent METAR (weather report) for one or more observing locations, enter the 4-letter ICAO Location Identifier (‘K’ followed by the FAA 3-letter ID) in the space, separated by one or more blanks.****
Surveillance and Broadcast Services Program Office****
HQ FAA, Washington, DC****
On Tuesday, April 2nd between 00:10Z and 00:45Z, AllisonHouse encountered an unexpected service outage. All services were impacted during this outage. A piece of hardware which directs load between our backend servers was downed inadvertently. During routine website changes which typically do not influence other services, this piece of hardware misinterpreted a website error as the backend servers failing. Due to the complexity of our systems, the root cause took 30 minutes to identify and temporarily correct.
Following the temporary repairs, a Scheduled Maintenance Window of Saturday, April 6th from 10:00PM CDT to Sunday, April 7th at 1:00AM CDT, was established to allow us to implement a permanent fix.
All Services – 35 Minutes; Between 00:10Z and 00:45Z
Websites – 45 Minutes; Between 00:10Z and 00:51Z and various periods thereafter.
Confirmation of these outage lengths can be seen at http://status.allisonhouse.com/
Outage notifications began at 00:11Z and were triggered by a botched website upgrade. The website changes had numerous errors which prevented the websites from being properly displayed. Because the AllisonHouse website was not displaying, our Load Balancer interpreted this as server unavailability. The internal state of the Load Balancer was changed from Up to Down. Services which rely on this piece of hardware were no longer available due to the state change.
The outage was immediately recognized and so debugging began within minutes. Initially different variables were removed to isolate the root cause. Unfortunately the Load Balancer was one of the last pieces to be removed from the equation. This happened at or around 00:40Z, after which most services were restored.
The website remained down following the Load Balancer removal due to the previously mentioned errors. We began to debug and publish fixes for the website until it was fully restored at 01:21Z.
The Load Balancer is targeting incorrect locations to test server availability. These locations rely on a number of services to be operating properly. If any single service which the website relies on fails, the Load Balancer could be improperly taken down.
A solution has been found and will be implemented during scheduled maintenance on Saturday, April 6th. Additional maintenance windows are likely to result from this outage. Notifications will be posted to Facebook and Twitter as those windows near.
Please contact email@example.com with any questions.