[Tendrl-devel] [TRACKING] Summary for the week of 12th Dec, priorities for the week of 19th Dec

[Mrugesh Karnik]

Firstly, apologies for the delay, as this update was to be sent on
Friday. However, I was not able to to send it due to an unexpected
situation at home.

All the listed ids are of issues on the specifications repository
(https://github.com/specifications/issues)

Progress from last week, December 12th to 16th, in no particular order:

* Pluggable delivery endpoints for alerts (#40).
* API integration to expose time series data (#62). This enables the
display of graphs and utilisation information on the UI.
* Inventory for disks and networks per node (#41, #43).
* Fixes to be compatible with the get-state output changes introduced
in gluster upstream, post 3.9 (#30).
* Object specific flows, to enable per object actions to be displayed
on the UI (#34).
* Versioned namespaces, to allow dynamic and backwards compatible
support for newer versions of the storage systems and upgrades for the
storage systems and tendrl components (#36).
* Some streamlining to provide a centralised view of the definitions
to ensure that all the tendrl components have a single view of the
available functionality (#39), optimisations to reduce etcd traffic
for definitions (#37) and additional attributes to aid dynamic API
generation (#33, #35, #38).
* Refactoring to remove duplication of functionality between
components and segretate the core framework into the common library
(#31).
* Built-in utilities that can be referenced in flows and reused across
various components (#72).
* Additional common classes to provide an abstracted view of the
definitions (#32).



Priorities for the week of 19th to 23rd December:

The following considerations have influenced the priorities this week:
* Couple of our component owners are on leave: Anmol (alerting and
monitoring), Darshan (node agent).
* The import cluster workflow needs to be enhanced to provide
auto-detection of the deployed storage system and complete UI flows.
However, on Friday, it was discovered that additional details need to
be spec'd out for the node agent. This specification (#87) would
impact the provisioning support for the storage systems and the
monitoring stack, along with the import cluster workflow itself.
* The impending holidays in Europe and the US.

Here are the priorities:

* Finish off the list views in the UI. Along with the implementation
of the UI itself (#75, #84, #65), it also requires some enhancements
from the monitoring stack (#62, #79) and the API (#35). Ceph pool
utilisation data needs to be gathered in the ceph integration
component (#80), as part of the core stack and is being worked on as
well.
    ** In parallel the node agent specification (#87) mentioned above
will be finished which enables all the following features to proceed.
    ** Also in parallel is the specification for auto detection of
various services by the node agent (#46).
    ** Also in parallel is the specification that enables real-time
updates from in-flight operations to be gathered in the backend (#55).
* The above three specifications would be completed along with the
list views, to enable the enhanced import cluster workflow from the UI
(#54, #56) to picked up.
* In parallel to all of the above, the logging is being improved
across the stack (#28) with machine parseable logs that would allow
tracing.
* The alerting component will be paused this week, since Anmol is on
leave. However, it will be picked up immediately after the import
cluster workflow, which should be completed by the time Anmol is back
from leave.
* Discussions and Q/A on the UX designs before the UX team is
unavailable due to the holidays.
* The specifications being worked in parallel to the list views and
import cluster workflows contribute to the provisioning support as
well. In addition to these, in the second half of the week, we'll be
picking up specifications for defining the Ceph and Gluster flows
(#51, #49), the exact scope and integration of the provisioning
modules (#47).


--
Mrugesh