[occi-wg] Meeting notes

[Sill, Alan]

Thijs,

That is great! Can we encourage you to use the issue and/or documents tracker in the OGF Redmine to start documentation threads there? This would help others find and contribute to these as needed.

Is there a list of current documents somewhere that you can use to start this?

Thanks,
Alan

On Jan 16, 2014, at 3:47 AM, Metsch, Thijs <thijs.metsch at intel.com> wrote:

> Hi all,
>  
> First of all thanks to all for (remotely) attending, prepping and adding to the discussions yesterday.
>  
> tl;dr:
>  
> ·         We will start writing an experience document plotting out some clarifications
> ·         We plotted out plans for OCCI 1.2 (roadmap for documents)
> ·         Minor semantic issues were discussed and resolved to get better interop between implementations.
>  
> With that said we want to start using our bi-weekly calls to track progress.
>  
> Meeting notes:
>  
> ·         “ issues” within current documents
> o   Infra: The usage of storage links vs OS templates for image selection was discussed. Suggestion (as the spec hints but needs to clarified in experience doc) to use template mechanism for image selection
> o   Typing of attributes: Suggestion to keep core clean from types but where necessary define them in the rendering docs.
> o   how to resize -> impl looks after that
> ·         Experience document
> o   Suggestion to write experience document – start with a google doc; Implementations which could be covered:
> §  rOCCI
> §  pyocci
> §  erocci
> §  pySSF
> §  ???
> o   Should be written from the PoV of Infrastructure – a ToC has been suggested and has been put in a google doc for sharing later.
> ·         OCCI 1.2 – will become 6 docs:
> o   Note: MUST be backwards compatible!
> o   Infra model
> §  For 1.2 it would be worth thinking on a router mixin for the networking part
> §  Error state needs to be added
> §  default method for actions in infrA should be defined.
> o   Platform model
> §  Should hold a suggestion for supporting PaaS
> o   Core
> §  pagination
> §  sub resources
> §  QI enhancements (default values, hierarchies etc, better queries)
> o   http protocol
> §  split from current doc
> o   text rendering (text/plain + text/occi -> text/occi+plain etc)
> §  split from current doc
> o   JSON document
> §  Will go into public comment asap
> o   Other possible docs/models
> §  Contextualization
> §  key management/Security
> §  Monitoring
> §  SLA
> §  Billing
> §  Interdomain networking
> §  OCCI-DRMAA
> ·         OCCI for OpenStack questions:
> o   We discussed how floating IPs are implemented in the OpenStack OCCI api.
> o   firewalls are OS specific 
> o   how to transfer and keep IP address -> change link source
> o   how to supply your own IP address to the VM?
> ·         Misc
> o   Website should list specs in draft state too!
>  
> Please feel free to ping questions and suggestions on where you could contribute and help - I’ll ping people with the action items we’ve assigned to them in parallel J
>  
> Again thanks for making OCCI very much alive and kicking – Much appreciated,
>  
> -Thijs
>  
> Intel GmbH
> Dornacher Strasse 1
> 85622 Feldkirchen/Muenchen, Deutschland
> Sitz der Gesellschaft: Feldkirchen bei Muenchen
> Geschaeftsfuehrer: Christian Lamprechter, Hannes Schwaderer, Douglas Lusk
> Registergericht: Muenchen HRB 47456
> Ust.-IdNr./VAT Registration No.: DE129385895
> Citibank Frankfurt a.M. (BLZ 502 109 00) 600119052
> 
> _______________________________________________
> occi-wg mailing list
> occi-wg at ogf.org
> https://www.ogf.org/mailman/listinfo/occi-wg