search

CCI-MOC / epics

The Issues within this repo will provide a space for us to track discussions around the creation of our epics. It will allow us to have a single location to track our planning and decisions for epics.
0 stars 0 forks source link

[Epic] ESI Information Gathering #1

Closed joachimweyl closed 10 months ago

joachimweyl commented 2 years ago

Gathering the motivation and the requirements for ESI. Having the motivation part of the discussion be driven by the PIs. Gather an understanding of what part MOC should have in ESI's next steps. Translate into a set of epics/requirements that we can start investigating.

Epic

msdisme commented 2 years ago

this is not a complete list; but a starting point. ESI Folder ESI install on CloudLab boss node The Current State of ESI presentation , to set context. The Pilot Deployment Test Cases - ESI System Testing ESI Operate First Use Cases 2021

hpdempsey commented 2 years ago

On Tue, Sep 13, 2022 at 3:03 PM Heidi Dempsey @.***> wrote:

Kim,

We have been working on this for a while already (i.e. years). Let's talk about it when I get back from Brno next week. I'm not quite sure what you have in mind from this brief note, but I'm sure we should coordinate on it. Heidi

Do you want to set up a time to talk Thurs or Friday?

On Fri, Sep 9, 2022 at 9:34 PM Joachim Weyl @.***> wrote:

Gathering the motivation and the requirements for ESI. Having the motivation part of the discussion be driven by the PIs. Gather an understanding of what part MOC should have in ESI's next steps. Translate into a set of epics/requirements that we can start investigating.

— Reply to this email directly, view it on GitHub https://github.com/CCI-MOC/epics/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMGMIELH4B2NG76KH7VVE2TV5OGKTANCNFSM6AAAAAAQI6NAG4 . You are receiving this because you are subscribed to this thread.Message ID: @.***>

joachimweyl commented 2 years ago

Some highlights from the meeting:

  1. How do we connect ESI and Onboarding
  2. Orran brought up a new version concept with limited API access and does not use OpenStack so that we can close down and limit operations to maximize security
    1. This would not be the main version but a version for consumers who need higher security
  3. Naved noticed some commands that work differently than anticipated
    1. Trunk attach to a node
    2. Need support for more types of switches
  4. Mike Z would like CloudLab to work with ESI
  5. How are we going to prioritize between ESI and RHODS?
  6. What are next steps with IBM?
  7. Need to work with Orran to further define next steps for ESI and what we should be focusing on
hpdempsey commented 2 years ago

Kim,

We have been working on this for a while already (i.e. years). Let's talk about it when I get back from Brno next week. I'm not quite sure what you have in mind from this brief note, but I'm sure we should coordinate on it. Heidi

On Fri, Sep 9, 2022 at 9:34 PM Joachim Weyl @.***> wrote:

Gathering the motivation and the requirements for ESI. Having the motivation part of the discussion be driven by the PIs. Gather an understanding of what part MOC should have in ESI's next steps. Translate into a set of epics/requirements that we can start investigating.

— Reply to this email directly, view it on GitHub https://github.com/CCI-MOC/epics/issues/1, or unsubscribe https://github.com/notifications/unsubscribe-auth/AMGMIELH4B2NG76KH7VVE2TV5OGKTANCNFSM6AAAAAAQI6NAG4 . You are receiving this because you are subscribed to this thread.Message ID: @.***>

joachimweyl commented 2 years ago

Initial meeting planned and attended. Meeting came to the conclusion that we will require more input from Orran.