Open Stack

I've written up a high-level summary of the discussions we had at the
PTG -- please feel free to reply to this thread to fill in anything I've
missed.

Sorry about the delay, I was really tied up after the PTG

We used our PTG etherpad:
https://etherpad.openstack.org/p/cyborg-ptg-stein

Cyborg Centric:

1. Stein Specs:
        a. os-acc e2e (in queue) -- probably needs to be refactored to move
REST API signatures to Nova specs, and Cyborg-specific details in this spec
        b. DB evolution introducing VAR and device profile concept (need to
add) Yes (part of the Rolling upgrade req)
            i. VAR related APIs spec:
                - GET /vars (optionally with request body of a list of VAR
UUIDs)
                - GET /vars/instance/{instance_uuid}
                - GET, POST, PUT, DELETE  /vars/unbound
                - GET, POST, PUT, DELETE  /vars/bound
            ii. Device profiles spec
        c. device discovery (in queue)
        d. pci_white_list (low priority for S ?) low priority.

    2. Drivers:
        a. Land current drivers in the queue: opae, gpu, clock
        b. add Xilinx driver
        c. add NPU driver (possibly from Huawei first, other NPU cards are
welcomed as well)
        d. add RISC-V driver support

    3. DOC: We will catch up with the documentation for Cyborg in the up
coming cycle

    4. Infra:
        a. fake driver to facilitate end-to-end function testing (part of
the Rolling upgrade request)(check with shaohe)
        b. utilize storyboard for task mgmt and tracing

Nova-Cyborg:
    Discussion with Nova details can be found
https://etherpad.openstack.org/p/cyborg-nova-ptg-stein
    1. Nova Stein Specs:
        a. device-profile e2e (for phase 1)
        b. new nova attach-device api (for phase 2)
    2. Need Nova to complete:
        a. Nested Resource Provider: Keep your eyes on this series and its
associated blueprint:
https://review.openstack.org/#/q/topic:use-nested-allocation-candidates

Note: Nova has made it clear that they do not expect Nova changes needed
for Cyborg to be upstreamed in Stein, because the bar for integration is
high. Cyborg needs to prove rolling upgrade etc., we need to pass CI/gates
with Nova, Nova changes need to be tested at unit/functional/tempest
levels. We have to make a push to get this done against expectations.

Neutron-Cyborg:
    1. Neutron Stein Specs:
        a. Propose a ML2 Plugin (networking-cyborg)
        b. neutron notification : add notification support in cyborg

MISC:
    1. work with SKT team on LOCI (OCI container image) support for
OpenStack-Helm (after stein-1 or stein-2)
       Is SKT the SIG-K8 team?(they are one of the biggest Korean Telco
Operators :) )
    2. work with SKT team and Dims on the k8s integration design/discussion

-- 
Thank you

Regards

Li Liu
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20180927/82cc18a3/attachment.html>