Date: Thu, 28 Mar 2024 16:09:12 +0000 (UTC) Message-ID: <341044059.6621.1711642152706@ip-10-10-7-29.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6620_901415133.1711642152705" ------=_Part_6620_901415133.1711642152705 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Sponsor: TIER
Group Leader (Chair): Jim Jokl
Agenda and Collaborative scribing notes are here: https://goo.gl/aaidWa<= /a>.
Attendees are encouraged to participate in live-scribing the meetings on= the above Google doc.
Email List: tier-packa= ging@internet2.edu
=E2=80=93 To subscribe: https://lists.interne= t2.edu/sympa/subscribe/tier-packaging
Problem
Deploying and operating campus Shibboleth, Grouper, and COmana= ge environments that adequately support a school's federated and internal&n= bsp;application needs is a significant pain point for some schools and a ba= rrier for others. Many campuses do not have the skill sets or staffin= g resources required by the current application packaging techniques. Many = configuration options are possible for these tools and default settings don= 't necessarily do what schools need. Enhanced configuration tools cou= ld ease effort. Broader campus adoption and use of this software will= likely require significant progress towards simplified Shibboleth,&nb= sp;Grouper, and COmanage implementation and maintenance via an appropr= iate set of pre-configured containerized, virtualized, and/or cloud&nb= sp;software distributions that are curated for longer-term support.&nb= sp; Other TIER components will have similar packaging and operational needs= .
The mission of this packaging working group is to develop a set of speci= fications and recommendations for what needs to be done to make TIER compon= ents simple to deploy and easier to operate and maintain. These speci= fications and recommendations will be turned over to TIER staff for impleme= ntation, distribution, and long-term maintenance as pre-built TIER sof= tware components.
Specific goals for the Packaging for Ease-of-Deployment Working Gro= up include:
Membership in the Working Group is open to all interested parties. Membe= rs join the Working Group by subscribing to the mailing list, participating= in the phone calls, and otherwise actively engaging in the work of the gro= up.
The chair of the Working Group is appointed by TIER and is responsi= ble for keeping TIER and InCommon TAC informed regarding Working Group's pr= ogress.
The Packaging Shibboleth, Groupe= r, and COmanage for Ease-of-Deployment Working Group will = organize its work and develop a work plan to meet the key deliverables high= lighted below. The items documented below should be delivered in orde= r listed below.
Potential Deliverables Considered to be Out of Scope for this Ph= ase
The working group is likely to encounter other topics during its deliber= ations and may elect to tackle appropriate issues within the WG or suggest = that other groups or a follow-on work group address these topics.
This working group's efforts are in support of a possible TIER release i= n April 2016. Work needs to proceed to deliver core packaging design = by the end of calendar 2015. The details of for additional administra= tive and configuration tools and GUIs must be completed by Jan 31, 2016. &n= bsp;Depending on the complexity of the added configuration and administrati= ve tools, this software might or might not be included in the April 2016 re= lease.
See Also:
Background i= nformation on TIER, Internet2 initiative on Trust and Identity= in Education and Research