Welcome to Ortelius. Ortelius is a unified 'evidence store' of supply chain data designed to simplify a decoupled microservices environment. Ortelius builds relationships between service (package) and consuming 'logical' applications. With Ortelius, open-source and API developers can register their services and track their consumers. Enterprise developers register their 'logical' application's base version and are notified when a dependency change causes the creation of a new application version, new SBOM, CVE, and dependency map. By centralizing and tracking detailed supply chain data, Ortelius provides the enterprise open-source consumers and open-source developers a coordinated view of who is using a service, its version, and inventory across all end-points. We are creating a central store for development teams to define provenance, apply zero-trust policies, and eventually score risk factors of both internal common code and open-source packages. In other words, we answer the question, "who is using Log4j." For more information, see the comprehensive documentation at Ortelius' documentation.
Our mission is to simplify the adoption of modern architecture through a world-class microservice governance catalog driven by a supportive and diverse global open source community.
- We want Members to learn and understand solutions around microservice use and their challenges through a diverse contributor base.
- We want our members to develop their careers, skills and gain community recognition for their work and expertise.
- We want our members to have the opportunity to share and reuse open source microservices to further the adoption of a cloud native development.
- We want members to learn how to contribute to an open source community and become part of the broader conversation around cloud native architecture.
The benefits of the Ortelius Open Source Project are:
- Adds automated supply chain management of microservices and other shared components across application teams
- Tracks the 'blast radius' of a single shared component across all consuming applications that are using it.
- Tracks the logical applications and aggregates component SBOM and CVE data to the logical applicaiton level.
- Simplifies the path to adopting cloud native development practices without a major redesign of their CD pipeline.
- Performs container versioning and applicaiton pakcage versions.
- Serve as a central market place to share reusable components with their SBOM and CVE information.
Goals for Q1 and Q2 of 2023
- Implementation of XRP Ledger to create immutable SBOMs.
- Improve data graphs and maps.
- Increase adoption of the catalog.
Contributor Covenant Code of Conduct
- Review the Ortelius Contributor Guide
- Add yourself to the Ortelius Google Group
- Join the Discord community channel
Calendar of meetings with times and zoom info.
Create a CD process for managing pull requests, builds, tests and releases.
Contributors:
- Anand Bhagwat
- Steve Taylor
- Sanjay Sheel
- Sacha Wharton
- Sagar Utekar
- Nael Fridhi
- Sanchit Khurana
- Natch Khongpasuk
- Brad McCoy
- Zach Jones
- Aditi Agarwal
- Jesse Gonzalez
- Jimmy Malhan
- Arvind Singharpuria
- Interas LLC - Corporate Contributer
- Ujwal Yelmareddy
- Lakshmi Viswanath
- Hamid Gholami
- Kingsathurthi
- Bassem Riahi
- Arnab Maity
- Steven Carrato
Create integrations with documentation and videos for the following CI/CD Solutions:
- Jenkins: 90% work completed
- Jenkins X
- Screwdriver
- Tekton (Tekton Catalog)
- Spinnaker
- Argo
Contributors:
- Steve Taylor
- Sacha Wharton
- Sagar Utekar
- Nael Fridhi
- Sanchit Khurana
- Karamjot Singh
- Sergio Canales
- Zach Jones
- Aditi Agarwal
- Jesse Gonzalez
- Lakshmi Viswanath
- Kingsathurthi
- Bassem Riahi
- Arnab Maity
Enhance the current Domain structure to make it more like a Marketplace for sharing Microservices. Think API marketplace.
Contributors:
- Christopher Hicks
- Steve Taylor
- Ayesha Khaliq
- Nael Fridhi
- Karamjot Singh
Review User Interface and make recommendations for improving with a focus on ease of use. Define test cases with automation.
Contributors:
- Tracy Ragan
- Parijat Kalita
- Ashutosh Srivastava
- Poovaraj Thangamariappan
- Yasaman Khazaie
- Nik Poputko
- Anirudh Sharma
Review documentation and re-write or clarify complexities.
Contributors:
- Tracy Ragan
- Divya Mohan
- Mark Peters
- Arijeet Majumdar
- Pawel Kulecki
- Jayesh Srivastava
Work to begin breaking down the monolithic into services. Starting with logging as a good first step. Integration with Istio with Routing. Solving onboarding efforts (AWS scraping for existing microservice customers)
Contributors:
- Christopher Hicks
- Steve Taylor
- Ayesha Khaliq
- Drishti Dhamejani
- Rahul Agrawal
- Sacha Wharton
- Sagar Utekar
- Nael Fridhi
- Sanchit Khurana
- Karamjot Singh
- Zach Jones
- Jesse Gonzalez
- Neil Chen
- Devendran Nehru
- Arvind Singharpuria
- Turker Aslan
- Leniuska Alvarado
- Ankur Kumar
- Lakshmi Viswanaths
- Bassem Riahi
- Paul Li
- Joseph Akayesi
- Christian De Leon
- Ian Anderson
Work on existing enhancements and bug fixes. Add them to the core Ortelius repository unless a doc change.
Contributors:
- Steve Taylor
- Drishti Dhamejani
- Melissa Albarella
- Sagar Utekar
- Nael Fridhi
- Sanchit Khurana
- Zach Jones
- Jesse Gonzalez
- Temitope Bimbo Babatola
- Munirat Sulaimon
- Neil Chen
- Atul Tiwari
- Devendran Nehru
- Utkarsh Kumar Sharma
- Avikam Jha
- Jayesh Srivastava
- Arvind Singharpuria
- Aman Saxena
- Ashutosh Srivastava
- Leniuska Alvarado
- Bassem Riahi
- Paul Li
- Joseph Akayesi
- Christian De Leon
- Akshat Jain
- Website, branding, outreach
- Review messaging, update logo, submit blogs.
- Personas, Journey Maps, service maps, roadmaps, Value Canvas, Go-to-Market strategies, product metrics.
- What problem or opportunity is being explored?
- How is the solution being framed to tackle this?
- What is being measured to determine if this is successful?
- Who are the people that this solution serves?
- How are they being informed about it?
- How are they learning to actually use or benefit from it?
- How are they involved in collaborating on the solution with us?
- What is the experience like for new collaborators getting started?
- How does the solution fit with both the immediate and wider ecosystem?
- Are there any roadblocks that can be removed in how we operate?
- What additional resources could be made available? Where would those resources help most?
- Where is the documentation being maintained on the project?
- Do we understand accessibility requirements? Are we meeting them?
Contributors:
- Tracy Ragan
- Neetu Jain
- Divya Mohan
- Mark Peters
- Alok Tanna
- Arijeet Majumdar
- Tatiana Lazebnyk
- Turker Aslan
Track progress, define process, work with Steve and Marky managing pull requests and releases dates.
Contributors:
- Tracy Ragan
- Neetu Jain
Research, define and Automate GitOps with Ortelius
Contributors,
- Brad McCoy
- Arvind Singharpuria
- Amit Dsouza
- Ayesha Khaliq
- Saif Ul Islam
- Kingsathurthi
- Hamid Gholami
- Anuja Kumari
- Vrukshali Torawane
- Joseph Akayesi
- Rakesh Arumalla
- Arnab Maity
Browse through the Installation and Support Guide for detailed guidance on how to sign up for & set up Ortelius.