Hi @edwarnicke, @fkautz, @mestery, will you consider adding (via PR) a listing for Network Service Mesh to the service mesh landscape? We'd love to have an accurate listing of the tool described here.

An update to both the non-functional.yml and the meshes.yml files would do the trick.

1. Create social icon for youtube
2. Include in site footer
3. Include in mailing list footer

Tracing Integration:
| Istio - Jaeger | Linkerd - Zipkin | Linkerd2 - None | Consul Connect - Pluggable |

Hi @taylor, @robertstarmer, will you consider adding (via PR) to include the CNCF Testbed in the list of service mesh to the service mesh landscape? We'd love to have an accurate listing of the tool described here.

An update to the service-mesh-tools.html would do the trick.

The https://github.com/layer5io/layer5/blob/master/CONTRIBUTING.md could use instructions on how to add/update an entry in the service mesh landscape. It should point to the yml files where entries belong. Given that columns / specific details included in those files may change, it should not itemize each associated attribute for an entry in the non-functional.yml or meshes.yml or other.

It should include instructions on how to build and preview changes.

ServiceMesher community is the biggest and professional Service Mesh community, based in China with more than 2000 members now. It is also run the Istio community in China. @leecalcote
Website: http://www.servicemesher.com
Twitter: https://twitter.com/ServiceMesher
GitHub: https://github.com/ServiceMesher

It's API Management including an API Gateway (uses NGINX). It looks like that should go in the non-functional list. There is an Istio Mixer adapter for it as well. Not 100% sure on the dates, but something like this:

- name: 3Scale
  opensource: "Yes"
  link: https://github.com/3scale
  governance: Red Hat
  primary-lang: Lua
  announce-date: December 2014
  ga-1-date: December 2014
  commerical: Red Hat 
  category: API Gateway

Issue Description
The service mesh workshop delivered at KubeCon 2018 NA was recorded. The card on https://layer5.io/workshops does not have a link to the recording, though.

Desired

• Add this recording to KubeCon NA 2018 workshop card.

When a user subscribes to Mailing list on Layer5.io , the status of subscription opens up in a new tab or window and the current page doesn't show any update.

Instead , the desired enhancement would update the status of subscription in the same page.

Hi @rvansa, will you consider adding a listing for Hyperfoil to the service mesh landscape under the Tools section? Given its use for load testing istio and envoy, we'd love to have an accurate listing of the tool described here.

@dtzar @paulbouwer should we consider inclusion of Azure's Istio Mixer adapter to the service mesh landscape - https://layer5.io/landscape? Under Tools or a new integrated systems section?

Hi @JoeDog, @sohamm17, @jmarantz, will you consider adding a listing for https://github.com/JoeDog/siege to the service mesh landscape under the Tools section? Given its use within the envoy-perf project, we'd love to have an accurate listing of the tool described here.

Displace much of current text within the Contributing section by adding a series of icons representing calendar, docs, youtube, folder to the Contributing section - https://layer5.io/meshery/#contributing

SOFAMosn is a modular observable smart network which can be used in service mesh deployed as a data plane sidecar. See https://github.com/alipay/sofa-mosn
It is a part of SOFAMesh, see Introducing SOFAMesh — A solution for large-scale Service Mesh based on Istio open-sourced by Ant Financial

Hi @suryadu, will you consider adding a listing for https://ibmcloud-perf.istio.io/regpatrol/ to the service mesh landscape under the Tools section?

The social icons for Slack on the site (top and bottom of page) link to https://layer5io.slack.com. This hyperlink should be changed to https://slack.layer5.io and leverage slackin (https://github.com/rauchg/slacki) to allow the public to join the community slack account.

Please add Grey Matter to the functional service mesh list.

Decipher Technology Studios' Grey Matter intelligent service mesh is a cloud-native, cloud agnostic intelligent service mesh that saw its formal 1.0 release on 14 Feb.

A pathway for enterprise transformation and cost control, Grey Matter is comprised of three layers, Fabric, Data, and Sense, working in unison to manage enterprise microservice fleets. The capture and analysis of over 100 telemetry types powers SLA management and control. Grey Matter is also designed to optimize enterprise network availability and performance through the innovative use of AI neural networks, enabling AIOPs.

Repositories and other documentation can be found here: https://demo.deciphernow.com/

Tool: Gloo Shot
Written in
Written for: Istio
Supported by: Solo.io
Description: Service Mesh delivered chaos engineering. Gloo Shot works on any mesh that supports fault injection.

URL: https://glooshot.solo.io

We need to update the language on the Grey Matter hover over to the following "Grey Matter is an Istio-compliant, Envoy proxy based hybrid cloud service mesh platform for business insight and secure data control with your Microservices."

Also, Grey Matter should be marked YES for the following Functional table sections: Multi-cluster, Multi-tenant, Auto Proxy Injection, and Encryption.

For the Non-Functional Section:

Grey Matter | Service Mesh | No | Decipher Technology Studios | Go | Nov 2017 | Feb 2019 | Grey Matter

Encryption:
| Istio - Yes | Linkerd - Yes | Linkerd2 - Experimental | Consul Connect - Yes |

As the layer5 community expands, so should the information architecture on the site. There is a need for additional content to be posted on different topics such as service meshes, api gateways, modern proxies, deployment strategies, troubleshooting, etc. A new collection type named "topics" can provide a landing place for such content that is more timeless in nature than a blog post.

Over time, particular genres of topics may amass to a size that they should be pulled out into a separate new collection or certain topics (e.g. labs) may need their own collection type created.

Description: Next generation API Gateway

link to
www.solo.io/glooe

Use of a Google sheet is temporary. Let's displace with a table native to the site's theme akin to that used in the "tools" section.

@DewaldV, @Joseph-Irving it'd be great to have Yggdrasil represented in the landscape. The contributing doc has instructions on how to update. Will you consider contributing a PR to ensure its accuracy?

1. Move tooltip style from service-meshes.html into materialize.css
2. Using this tooltip style, create new descriptive tips for social icons in partials/hori-social.html
   2.1. YouTube - "Watch community meeting recordings"
   2.2 GitHub - "Contribute to Layer5 projects"
   2.3. Twitter - "Follow Layer5 on Twitter"
   2.4. etc...

the "please submit an issue" hyperlink points to the old repo location - https://github.com/leecalcote/layer5/issues. Needs updating.

@liljenstolpe, @kprabhak, @ahrkrak it'd be great to have Tigera represented in the landscape. Will you consider a contributing a PR to ensure its accuracy?

Tool: Service Mesh Hub
Written In:
Written For: Istio, AWS App Mesh, Linkerd
Supported by: Solo.io
Description: Unified dashboard to install and operate any mesh on any infrastructure. Manage all your meshes, services and extensions.

URL: https://servicemeshhub.io

@tianxiaoliang, would you like to assist in providing details of Mesher into the this landscape? - https://layer5.io/landscape

@tigerlinux1688 are you able to assist in getting A10's offering represented?

Hi @paib, @sudswasavi, @rangar, @oletizi, will you consider adding a listing for AVI's service mesh to the service mesh landscape? We'd love to have an accurate listing of the tool described here.

Hi @qiangdavidliu, @tbak, will you consider adding (via PR) a listing for Eureka to the service mesh landscape? We'd love to have an accurate listing of this load balancers described here.

Contribution instructions - an update to both the non-functional.yml file would do the trick.

Thanks!

Current Behavior:
The service mesh landscape, the Non-Functional section has a table of four different categories of technologies (service mesh, API Gateway, service proxy, load balancer). Readability of the table would be improved if the first column of the table was the Category column, not the Name column.

Desired Behavior:
Have the Category column as the leftmost column in the table in the Non-Function section of the landscape.

@dstiliadis @satyamsi it'd be great to have Aporeto represented in the landscape. Will you consider a contributing a PR to ensure its accuracy?

Perhaps, under the "Commercial Offerings" column for Istio?

As of Linkerd 2's stable-2.3 release, the mTLS feature is no longer experimental; in fact, it's now enabled by default. See https://linkerd.io/2019/04/16/announcing-linkerd-2.3/

We might want to remove Conduit from the list

Annoucment: https://blog.conduit.io/2018/07/06/conduit-0-5-and-the-future/

"Books" as a new collection should will be a home for listing of relevant books on service meshes.

January 24, 2019 at 09:02PM

Enhance landscape table usability with:

1. sorting by descending alphabetical order on the leftmost column by default)

• This would be the ability for a user to click on the column name and have the table sorted by that column.
• The ability to click to switch between asc/desc

2. alternating colors in rows

@thoraxe, it'd be great to have OpenShift represented in the landscape. Will you consider a contributing a PR to ensure its accuracy?

Perhaps, under the "Commercial Offerings" column for Istio?

Prometheus Integration:
| Istio - Yes | Linkerd - Yes | Linkerd2 - Yes | Consul Connect - Yes |

With the insertion of all categories of projects related to service meshes, the Functional table has become hard to read and garner insight from. Either by row color or some other mechanism, let's provide visual indication of groupings of items in by category in the functional table in the landscape.

@subfuzion it'd be great to have App Mesh accurately represented under the Functional section of the landscape? Will you consider contributing a PR to ensure its accuracy? Nate Taber assisted with the non-functional already.

Tool: SuperGloo
Written in
Written for: Istio, Hashicorp Consul, Linkerd, AWS App Mesh
Supported by: Solo.io
Description: Service mesh agnostic orchestrator

URL: https://supergloo.solo.io

"Projects" as a new collection should will be a home for describing projects stewarded by Layer5 contributors (e.g. Meshery).

When a “projects” collection is created and meshery (for example) is added, we’ll want to retain the /meshery url for ease of reference, understanding that it’ll also show under /projects/meshery.

@nrjpoddar, if you're inclined to add Istio Vet to the tools (code here)section of this landscape, we'd welcome its listing.

Recent updates have undone #3. SOFAMosn is listed under proxies, but SOFAMesh has gone missing.