This page links to the sessions that Infrastructure will be leading at UDS-O. It will only be used leading up to UDS to organize the information. Tracking through the cycle will happen via status.linaro.org as usual.

Attendees

Sessions

  • Consolidate hardware-dependent code between Android and Ubuntu

    • Aim:
      • Identify which pieces can be shared between Android and Ubuntu images (kernel, bootloader, ...?)
      • Create a plan to consolidate development efforts on those parts
      • Investigate how the binaries of those shared pieces can be delivered so that they can be shared at that level too (e.g. hwpack that works for Android/Ubuntu)
    • Session lead: JamesWestby

    • Stakeholders:
      • Android team
      • Developer Platform team
      • Landing teams
  • Continuous Integration of Linaro Components in LAVA

    • Aim:
      • Provide continuous integration of Linaro components in LAVA. For instance one aim is that kernels from linux-linaro should regularly be built and then booted on a variety of hardware in LAVA. This sessions will discuss the validation that can be done on the components, and how to go about it.
    • Session lead: MichaelHudson

    • Stakeholders:
      • Working groups
      • Developer Platform team
      • Android team
      • Validation team
  • Provide remote development board access to Linaro engineers

    • Aim:
      • Provide remote development board access to Linaro engineers for various tasks (porting tasks, benchmarking, power management measurements.) The boards should be available for exclusive use, with a lease system to avoid starvation if people forget and go on holiday. This may be a facility of lava, and the boards may be dedicated, leased from the validation pool, or a combination of the two.
    • Session lead: GuilhermeSalgado

    • Stakeholders:
      • Linaro engineers
      • Validation team
  • Better Android Build Service

  • Linaro Hardware Needs

    • Aim:
      • Determine what additional hardware do we need in Linaro, and prioritise those needs. This may be for automated builds/validation, remote developer access boards, or specific boards for certain engineers for testing/QA purposes.
    • Session lead: JamesWestby

    • Stakeholders:
      • Linaro engineers
  • Prebuilt images for Linaro

    • Aim:
      • Discuss the feasibility of providing downloads of pre-built Linaro images, avoiding the need for developers to run linaro-media-create locally. The following questions are important:
        • Is this something that we should be providing (e.g. can we QA them adequately)
        • If so, should we return to providing these rather than hardware packs?
        • If we do provide them should it be all combinations of images and hwpacks? If not, which combinations?
        • How should the image end up on a SD card?
        • What can be done to accommodate different sizes of SD card?
    • Session lead: GuilhermeSalgado

    • Stakeholders:
      • Developer Platform team
      • Validation team
      • Android team
  • Managing (Android) code differences

    • Aim:
      • Working on Android requires keeping track of changes across several trees, and when you are working on more than one thing at a time this adds up to tracking lots of commits in lots of trees. We will discuss what could be provided to make this task easier.
    • Session lead: MattiasBackman

    • Stakeholders:
      • Android team
      • RM/PMs

Other sessions of interest

These are sessions that may be of interest to Infrastructure engineers:

The rest of the time

We will have a team meeting at some point to go over a few things. Aside from that the rest of the time should be spent attending sessions led by other teams and looking for areas where help from Infrastructure would be of use.

In addition, if there are coding/design tasks not covered by a session then please bring them up and we will make some time to go over them outside sessions.

internal/archive/Platform/Infrastructure/LDS-O (last modified 2013-08-23 12:11:21)