Skip to main content

State of One Platform - Apr 2021

· 5 min read
Ghanshyam Lohar

This is a summary of the development goals achieved by the One Platform team in the month of April 2021. This month the team had the following goals:

  • Application Development: Federated Notifications UI, Developer Console UI, Architecture of monitoring microservice, DSAL Ansible Dashboard, User Group Rover integration, Lighthouse Microservice GA release

  • Onboarding: Lifecycle Admin SPA on Prod, Onboarding discussions for Attachment viewer SPA & Cert SPA

  • Infrastructure update: Monitoring the pod status on OpenShift using OpenShift's inbuilt monitoring service, Monitoring SPAs & Microservices using their health-check endpoints from Catchpoint

  • E2E test automation: Test report automation & notification over the email. Test suite development for search module

OKRs

ObjectivesStatusIMP Summary from Key Results
Accelerate and provide consistent SPA development & delivery experienceOn Track (Continued)
  • Lighthouse microservice setup is complete and released to production.
  • Developer console UI and integration to the App Service is in progress
  • Catchpoint checks configurations for Microservices and SPAs is completed
  • E2E test cases for Feedback, SSI, Home & Search are completed
  • E2E tests for dev console & user groups are In Progress
  • List of use cases & statuses for polishing microservices & SPAs are, as in the table below
Evolve one.redhat.com as a single place to host internal applications and accessible outside VPN. On Track

(Continued)

  • Ticket to update new domains in http://hdn.corp.redhat.com/proxy.pac - Completed
  • Escalation watchlist: Initiated the discussion with the team they are evaluating One Platform & will get back to us
  • Pantheon - Decision pending on Pantheon team due to architectural changes they are making
  • Enhanced home designs to improve user experience and look and feel of the homepage
Non-native Application developmentOn Track
  • Outage Management SPA: POV demoed, decision on the use of statuspage vs service now in the coming weeks
  • DSAL Ansible migration & UI fixes
  • Lifecycle Admin SPA - Released on production

Polishing microservice/SPA use cases:

MicroserviceUse casesStatus
FeedbackPublished the opc-feedback component and testing the SPA, Microservice in QA and Stage.Completed
NotificationsRevamped Notifications microserviceCompleted
Revamped Notifications UI is underway.In Progress
SearchRover integration.In Progress
Suggestions based on user search history.Not Started
User GroupsRover integration to get user dataCompleted
Build API authorization based on user-groupsNot Started
Apps Service (previously Home Service)Deployment and testing of Apps Service on QAIn Progress
Developer console UIIn Progress
API gatewayPeriodic GraphQL IntrospectSchema refresh, for up-to-date schema on the API GatewayNot Started

Key highlights

The team was able to close 16 JIRAs across a range of development priorities. The highlights are:

  • Application development and readiness:

    • Native Apps:

      • Developer Console:
        • UI implemented for Developer Console
        • UI integrations with One Platform Microservices for enabling and customizing the microservice features for an App
      • Notifications:
        • Implementation of a federated UI for notifications management went into further discussion to make a common consumable component
      • Lighthouse CI GA’ed:
        • Catalog team adopted the lighthouse CI
        • Lighthouse SPA & Microservice Development - Microservice & SPA development in progress.
      • Home Page enhancements
    • Non Native Apps:

      • Outage SPA
        • Proof of Value demoed, decision on the use of statuspage vs service now in the coming weeks.
      • DSAL
        • Dashboard migration
        • Ansible Pipelines migration nearing completion
    • Designs:

      • Design for Lighthouse SPA
      • Design for POC for app monitoring & analytics
      • New one platform home design is finalized
  • Onboarding

    • Lifecycle admin SPA released on production at /lifecycle
    • Followed up on Pantheon onboarding, The Pantheon team is weighing the options available
  • E2E test automation:

    • Generation of HTML reports & send them across the email as an attachment.
    • Test suite implementation for search is completed

What's coming?

  • Deploy to One Platform automation
    • Develop a button, Form, SPA metadata
    • Automate the deployment process
    • Integration with SPAship, API Key generation
  • Developer Console GA Release
  • SPA Continuous Deployment (CD) automation
  • SPA Onboarding:
    • Cert Apps SPA onboarding discussions
    • Escalation Watchlist SPA onboarding discussions
    • Pantheon followup
  • Development and Adoption Priorities
    • Lighthouse GA release
    • One platform to work with IT, Legal, InfoSec to make one.redhat.com externally available
  • One Platform Test Automation:
    • Send test reports as an inline mail body to the configured Email IDs
    • Further implementation of test suites for remaining One Platform native modules
  • Adopt and Implement recommended solutions as a result of 3D Developer Experience research and brainstorming.
  • One Platform home page enhancements

For more updates related to One Platform, please check out the One Platform Blog at one.redhat.com/get-started/blog

Meta

Completed Sprint: One Platform – Apr'21

Ongoing/Upcoming Sprint: One Platform – May'21

One Platform: one.redhat.com

JIRA: https://projects.engineering.redhat.com/projects/ONEPLAT/issues

GitHub: https://github.com/1-Platform/one-platform/issues

Questions

For any questions, please reach out to the One Platform team over one-platform-devs@redhat.com or ping us over One Platform GChat Room. For more information please view FAQs.