Anuket Project

  • Created by Unknown User (tsalagi), last modified on Apr 24, 2018

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

04/17/2018 --

  • Spoke with DMA project team.  They are ok with working in a separate container.  They will swing back in a few weeks with a demo.

  • Standards with Al Morton

    • No updates

  • VES with Bryan Sullivan

    • Most work done by Goku

    • Bryan will update VES for latest release to make sure it works with everything

    • Plan is place to move items forward in Barometer

  • RPMs with Leif

    • Making progress

  • Func tests

    • Will not support Compass this cycle

  • Collectd pull requests

  • Release

    • Gambia path or something else?

    • Which track do we follow?

    • Continuous delivery

      • Flexibility with milestones, since you establish them yourself?

      • Bryan doesn’t think we should do traditional path -- not enough resources

      • FCI could be a good thing if it marries VES and Barometer

  • Edge Cloud

    • What are the requirements?

      • Need categories

      • Always about latency for faults and metrics

      • Framework and edge computing use cases would be good

    • Is VES a good fit?

      • Good for cloud-native

      • What is a cloud?  What value does opensource ecosystem get from:

        • Common telemetry date model

        • Consistent set of mechanisms by which data delivered to collector

    • How lightweight?

      • Less than 1% CPU, and 5% memory

      • Two VES encodings: C and Java

      • Goku: tokenized VES data structure

      • Overhead of data and complexity of stack

      • Go from binary XML to tokenized JSON

      • Current implementation is not lightweight but is “easy”

      • Use gzip, as it is natively available to HTTP stack (works out of box)

04/10/18 --

  • DMA Project discussion

    • Positive feedback on DMA proposal.  Want to move forward.

    • Work should be done in a separate container.

  • Standards

    • Al has been reviewing Alok’s VES proposals.  Found some VMWare specific items. Vendor-specific provisions are discouraged.  Al to talk with Alok ;).

    • VES is starting to incorporate some TOSCA information.

  • Collectd

    • Emma suggested that all collectd PRs be from the same fork, Barometer, in order to make collectd aware of who the reviews are for.

    • Also, should have more Red Hat people reviewing collectd.  Need to talk with local Red Hatters.

  • VES

    • Bryan returned.  Wants to keep the VES agent development moving forward.  Did not know about DDS messaging stuff in ONAP. However, see’s that Kafka is not set in stone.  What to do at the edge.

  • General

    • Next week I will be out.  Andrew Bays will run meeting.

04/03/18 --

  • DMA Project

    • Presentation given by Tomofumi Hayashi.  Slides available on the wiki.

    • Major takeaways…

      • Run time reconfiguration of collectd.  There were some questions as to whether this should be a feature of something like an Ansible playbook.

      • Topology annotation.  Questions about security and what information would be included.  It was stated that only infrastructure information would be annotated.  

      • Data reduction and analysis at the edge.

      • DMA project should be an add-on.  Might need to be able to “unwind” project in the future.

    • OPNFV Bottlenecks project using Barometer container

  • Development

    • Thanks to Emma for updating the docs and helping track down Funtest issues

    • Still seeing an error with Functest… seems to be related to Functest, not Barometer.  Emma tracked down the internal Barometer issues!

    • Barometer container -> multistage build from RPMs progressing slowly..

  • ONS recap

03/20/18 --

  • Made MS6...

  • Next upcoming milestone, MS7, April 6th -- last day to request a stable branch.  Can request one anytime until then.

  • After than MS8, April 16, completion of testing

  • Current Fraser status

    • api_check failing

      • test_add_remove_volume

      • test_attach_volume_nowait

      • test_detach_volume_nowait

      • ….

      • Perhaps it was a system / connectivity failure?

    • Emma good catch on Hugepages failing fix

    • Gnocchi failures

      • Results not appearing quickly enough due to Gnocchi archive policy

      • Change default policy to High

    • AODH failures

      • Need to modify the tests to perform specific failure action

  • REDFISH Plugin

    • Purpose  -- node or rack?

    • Design review

  • Standards Update

  • VES Updates

    • Progress on ETSI?

    • VES Mobile edge platforms?

    • Is there a cadvisor plugin for collectd?

    • C, Java VES libraries

    • Microservice heatbeat

      • ONAP flow

      • Vendor VNF

      • Closed loop control

      • Services goes into VNF

      • Any missing heatheats

      • At the FM layer

03/13/18 --

  • Functest debug and then power loss ;(

03/06/18 --

  • Milestone 5 complete

    • Scenario deployment passed

    • Functest failing

  • MS6 03/16/18

    • Test case implementation completed.

    • Preliminary documentation completed.

    • First day that projects may request creation of the stable branch for their project.

  • APEX

    • Functests failing

    • Virtual deploy -- RDT, Hugepages…  Should we skip during virtual deploy?

    • APEX deployment help -- Aaron has a test setup running and can answer questions.

  • Collectd

  • DMA project would like to have another meeting (possibly at ONS)

  • Did you get your feedback to Alok?  I know I didn’t yet :(.

    • Want to get comments by the 15th

    • Produce a spec update by end of March

    • Have a weekly update

  • VES Update

    • VES Project into ETSI

    • Parts of the project, metric / event definitions, transport

    • Pair things down to what’s important

    • 10’s of collectors at present

  • VES mobile edge platforms

    • CAdvisor plugin for collectd?

    • Maybe try in the Barometer container?

02/27/18 --

  • Milestone 5 approaching

    • Thanks for the help on Apex and Barometer

    • Tracked down issue with deploy

  • Standards Update

  • VES Update

  • Barometer containers to be part of RDO release

    • Team to work on building Kolla containers

    • AMQP1.0 container being built

02/20/18 --

  • Collectd on Cumulus

    • Open Compute / Networking

  • Standards Updates?

  • VES Updates?

  • Development

    • Apex scenarios are currently failing

    • Ansible script reviews in progress

    • MS5 approaching

  • Barometer next?

02/13/18 --

  • Should Barometer Graduate? (https://www.opnfv.org/software/technical-project-governance/project-lifecycle)

    • Are we a part of enough scenarios (another installer)?

    • Would be a good recognition of the work done by Barometer

    • Have had good recognition at shows (OpenStack Summit, OPNFV, etc)

    • Bryan would be supportive of applying for graduation

    • No definitive answer, but positive reception

  • Standards Update (Al)

    • Meeting with IFA working group completed work on all measurement content.  Al provided an edit / rewrite of the document and resubmitted.

    • Discussion of GAPs in Baromter

  • VES Update

    • Bryan working on Barometer Kubernetes scenario.  Should be ready soon. Barometer as DaemonSet

    • Conversion of VES to gRPC in the testing phase.

  • Development Update

    • Ansible scripts submitted to Gerrit

    • Clarification that plugins not in collectd yet should still make it into Barometer / Fraser

  • (MS5) Scenario integration and feature freeze -- 03/02/18

  • Good discussion on “What’s next for Barometer”

    • Scope expansion -- Should Barometer move beyond metrics / events to policy

    • Scope continuation into container space --

  • OPNFV Barometer people going to ONS in March

    • Aaron

    • Al

    • Bryan

    • ??


  • No labels