This article was accepted into the corpus but its outbound wikilinks were never NER-processed — typical at the deepest BFS hop or when the run's entity cap was reached. No expansion funnel to show.
| LISA (conference) | |
|---|---|
| Name | LISA |
| Status | Defunct |
| Genre | Technical conference |
| Frequency | Annual |
| Country | United States |
| First | 1987 |
| Last | 2017 |
| Organizer | USENIX Association |
LISA (conference) The Large Installation System Administration (LISA) conference was an annual technical conference focused on system administration and IT infrastructure best practices, organized by the USENIX Association and attracting practitioners from institutions such as Google, Facebook, Netflix, Amazon (company), Microsoft, Apple Inc., IBM, Intel, Red Hat, Oracle Corporation. The event served as a forum for operations engineers, site reliability engineers, and security professionals from organizations including NASA, CERN, National Aeronautics and Space Administration, National Security Agency, Department of Defense (United States), United States Postal Service to exchange operational experience and tooling. Presenters often came from projects and products like Kubernetes, Docker, Linux, OpenStack, Ansible, Puppet (software), Chef (software), Prometheus (software), Nagios, Zabbix, Splunk.
LISA began in 1987 under the auspices of the USENIX Association and developed alongside influential events such as DEF CON, Black Hat (conference), SIGCOMM, O’Reilly Open Source Convention and PyCon. Early contributors included engineers affiliated with Berkeley Software Distribution, Sun Microsystems, Digital Equipment Corporation, Hewlett-Packard, AT&T Bell Labs. The conference evolved through eras marked by shifts toward cloud computing vendors like Amazon Web Services, Google Cloud Platform, Microsoft Azure and by the rise of orchestration tools from Cloud Foundry and Mesosphere. LISA’s timeline intersected with major industry inflection points including the proliferation of IPv6, the adoption of TLS, the aftermath of the ILOVEYOU worm and lessons from outages such as those experienced by Amazon (company) and GitHub. In 2017 USENIX reorganized its practitioner conferences, folding LISA’s remit into broader USENIX events.
The program covered operational topics including monitoring and observability (presentations referencing Prometheus (software), Graphite, Elasticsearch), configuration management (Puppet (software), Chef (software), Ansible), systems performance (Linux, BSD, Solaris), automation and orchestration (Kubernetes, Docker), site reliability engineering practices influenced by Google SRE and incident response case studies from Facebook, Twitter, LinkedIn, Airbnb. Security and compliance talks often cited frameworks or agencies like NIST, ISO/IEC 27001, Payment Card Industry Data Security Standard. Topics also encompassed storage systems such as Ceph, GlusterFS, ZFS, distributed databases like Cassandra (database), HBase, MongoDB, and networking staples like BGP, OpenFlow and Software-defined networking projects from ONF.
USENIX organized LISA with program committees composed of practitioners and academics from institutions including Carnegie Mellon University, Massachusetts Institute of Technology, Stanford University, University of California, Berkeley, Princeton University; corporate sponsors ranged from Google and Amazon (company) to Red Hat and VMware. Vendor booths and training sessions featured companies such as HashiCorp, Splunk, Datadog, PagerDuty, New Relic. Funding and governance involved collaboration with groups like IEEE, ACM, and occasionally with government research labs such as Los Alamos National Laboratory and Sandia National Laboratories for joint workshops.
Notable LISA editions showcased influential talks and tutorials that later shaped operational practice. Presentations by engineers associated with Netflix popularized chaos engineering concepts related to Chaos Monkey; Google-affiliated speakers disseminated Site Reliability Engineering principles; talks touching on containerization dovetailed with announcements from Docker, Inc. and demonstrations of Kubernetes deployments. LISA editions often paralleled content seen later at Velocity Conference and SREcon, and featured collaborations with community projects like OpenStack Summit and LinuxCon. Key panels included incident postmortems from outages at Amazon (company), GitHub, and large-scale migrations performed by LinkedIn and Pinterest.
USENIX published LISA proceedings, technical reports and slide decks alongside tutorial materials; these were archived in association with USENIX technical paper series and indexed similarly to collections from ACM Digital Library and IEEE Xplore for cross-referencing. Proceedings documented case studies involving implementations of LVM, RAID, Ceph clusters, performance analyses involving Linux kernel tunings, and security assessments addressing SELinux and AppArmor. Many papers informed later standards work or RFCs circulated through the IETF and inspired tooling maintained on platforms such as GitHub and GitLab.
LISA presented awards and recognition for operational excellence and community service, highlighting contributors who influenced practice through open-source projects like Puppet (software), Chef (software), Ansible, SaltStack; notable honorees included engineers later recognized by institutions such as USENIX Lifetime Achievement Award, ACM SIGOPS Hall of Fame, and recipients who moved into leadership roles at Google, Facebook, Netflix, Microsoft. The conference’s tutorials and training courses were frequently cited in professional development tracks alongside certifications offered by Red Hat, Linux Professional Institute and vendor-specific programs from AWS.
LISA had substantive impact on the professionalization of operations, accelerating practices later codified by Site Reliability Engineering (book), The Phoenix Project, and operational tooling ecosystems. It served as a nexus for cross-pollination between practitioners at NASA, CERN, Facebook and open-source communities. Criticism targeted perceived vendor influence from major sponsors like Amazon (company), Google and Microsoft, occasional gaps between academic research presented at SIGCOMM and practitioner needs, and debates over inclusivity similar to discussions at FOSDEM and PyCon. The consolidation of conferences within USENIX and the emergence of specialized events such as SREcon and vendor-run summits contributed to LISA’s eventual integration into broader practitioner programming.
Category:Computer conferences