...
- Marek Chwal Most projects are in M4. However, not all documentation is available to the community, but at least we have references so we can ask for details and check/approve release candidates
- Need references, blueprints and release plan to be verified by stakeholders and an update sent to the mailing list.
- New release mailing list for tracking the release tf-release@lists.tungsten.io
- Stakeholders, please join the mailing list here.
...
- James Kelly has moved from the marketing team to the Juniper Product lead. He is excited to work with the TF community.
- Working internally to shift development processes to the upstream community to reduce the duplication of work within the Juniper engineering team.
- Internally at Juniper, we are adjusting our strategies to be better open source citizens.
- We are advocating for a shift to K8-Native. We would like to see TF shift from being a layer on top of the cloud to something that runs inside of Kubernetes.
- We are also recommending that we have an optional Prometheus native support for analytics and telemetry federation.
- We want to continue to support OpenStack and refine legacy components.
- James Kelly recommended that we realign to an open GUI and shift away from Contrail Command.
- Possibly even extend the Kubernetes.
- James Kelly if we align more to K8's we have an opportunity to change the engineering culture at Juniper to be more aligned to the Open Source.
- We could start a new repository to support the effort
- There is still a need to identify how to support service mesh and other important areas of TF.
Developer & Testing Forum
- Registration
- Topic Proposals
- Dates:
- -
- Proposals are due by
- Schedule to be announced by
- Casey Cain asks that you submit your topics as soon as possible.
Action items
- James Kellyto attacheattach slides from his presentation to the minutes and start a mailing list thread to continue the discussion of deeper Kubernetes integration