Sprint 225

This document summarizes the Sprint 234 review meeting which took place on April 3, 2024. The meeting covered UI fixes and enhancements by Jeffrey Bonson, provider updates by Adam Grare, and platform changes by Joe Rafaniello such as adding region counts to audit reporting and upgrading dependencies. Bugs addressed include tagging and workflow credential issues while enhancements included updating UI components. Questions were invited for discussion with the next Sprint 235 review scheduled for April 17, 2024.

This document summarizes the Sprint 211 review meeting that took place on May 3rd, 2023. The following topics were discussed: - Melody Seda provided updates on UI enhancements and bug fixes. - Adam Grare discussed enhancements and bug fixes to various cloud providers including Core, Amazon, Cisco Intersight, IBM PowerVirtualServers, IBM PowerVC, Kubernetes. - Joe Rafaniello covered platform enhancements and bugs including testing, configuration scripts, and dependencies. - Keenan Brock mentioned API enhancements around StorageService and multi_repo. - Jason Frey noted the new multi_repo gem extracted from manageiq-release and thanked participants.

This document summarizes the Sprint 167 review meeting of August 4, 2021. It discusses updates to the UI, providers, platform, API, and developer work. Key points include: fixes and enhancements to the UI like react forms and authentication; added support for collecting cloud databases and IBM Cloud events in providers; using Kafka for event handling in the platform; new API options calls; and rake tasks, schema changes, and setup improvements for developers. The next sprint review is scheduled for August 18, 2021.

Sprint Statistics (John Prause) Community Update (Carol Chen) UI (Harpreet Kataria) Providers (Adam Grare) Platform (Joe VLcek) API (Alberto Bellotti) QE (Mike Shriver) Documentation (Suyog) Summary

The Sprint 159 review covered updates across UI, providers, platform, API, and developer work. Key points included: - 13 UI PRs were merged focusing on bugs and one enhancement. - Provider work focused on Azure, Google, OpenStack, and NSX-T inventory improvements. - Platform enhancements included regex event detection and messaging updates. - API changes added endpoints for cloud subnets and template importing. - Developer documentation was updated and a new provider authoring guide was added.

This document summarizes the Sprint 204 review for ManageIQ which occurred on February 1, 2023. It outlines bugs fixed and enhancements made to the UI, providers, platform, and API. Key items include removing the SCVMM provider, adding host initiator groups to the storage dashboard, fixing a schedule edit bug, and adding support for querying the native console protocol in the API. The next sprint review will be on February 8, 2023.

- Sprint 156 review meeting on March 3rd covered UI, Providers, Platform, and API work - UI team worked on rewriting a cloud volume form to React and other enhancements - Provider team fixed bugs for Amazon, AutoSDE, Azure, IBM Cloud, and Openstack and added support for Oracle Cloud - Platform team merged 20 PRs including bugs fixes and enhancements - API team added actions for simulating policies on VMs, querying ISO images, safely deleting cloud volumes, and exposing the cloud subnet create form

The sprint review covered work done in Sprint 175 from the UI, Providers, Platform, and API teams. Key highlights included: - The UI team worked on 18 pull requests focused on bugs, enhancements, and refactoring including converting forms to React and removing unused code. - The Providers team added new metrics collection and region support for various cloud platforms and made improvements to standardization. - The Platform team focused on technical debt removal, documentation updates, and adding TLS configuration for pods. - The API team enhanced the metrics and event streaming endpoints.

Play and Grails are Java web frameworks that aim to enhance developer experience. The author developed the same application using both frameworks to compare their features. Some key differences included: - Database configuration and schema generation were simpler in Grails using GORM, while Play used EBean and evolutions. - URL mapping was defined in a Groovy file in Grails, and a routes file in Play. - Grails used Groovy Server Pages for views with tags, while Play used Scala templates. - Both supported features like validation, jobs, feeds, and email, but implementations differed, such as using plugins in Grails and direct APIs in Play. - Testing was supported through plugins

This document summarizes the Sprint 221 review meeting which took place on September 20, 2023. The meeting covered bug fixes and enhancements across various components including the UI, providers, and platform. Specific issues that were addressed included fixing tenants list viewing, adding sorting options to chargeback, and converting collection forms from HAML to React. Presenters also provided updates on IBM CIC, Openstack, VMware, workflows, upgrading dependencies, and dropping Ems destroy callbacks. The next sprint review is scheduled for October 4, 2023.

With more than 14,000 customers in 110+ countries, Splunk is the market leader in analyzing machine data to deliver operational intelligence for security, IT and the business. Our rapid growth as a company meant that our Infrastructure Engineering Team, responsible for all the common tooling, build and test systems and frameworks utilized by the Splunk engineers, was bogged down with a sprawl of virtual machines and physical servers that were becoming incredibly difficult to manage. And as our customer’s demand for data has grown, testing at the scale of petabytes/day has become our new normal. We needed a reliable and scalable “Test Lab” for functional and performance testing. With Docker Enterprise Edition, our engineers are able to create small test stacks on their laptop just as easily as creating multi-petabyte stacks in our Test Lab. Support for Windows, Role Based Access Control and having support for both the orchestration platform and the container engine were key in deciding to go with Docker over other solutions. In this talk, we will cover the architecture, tooling, and frameworks we built to manage our workloads, which have grown to run on over 600 bare-metal servers, with tens of thousands of containers being created every day. We will share the lessons learned from running at scale. Lastly, we will demonstrate how we use Splunk to monitor and manage Docker Enterprise Edition.

This document summarizes the Sprint 180 review meeting held on February 23, 2022. It includes sections on UI improvements, provider updates, platform changes, API refactoring, and developer initiatives. Some key updates include improved representation of volumes and host initiator groups in the UI, PowerVS snapshot support, using the OS certificate bundle, allowing Rails 6.1, and replacing Hakiri with Whitesource for security. Questions were invited at the end.