🌄 CDF Landscape: a living document that developers, investors, vendors, researchers and others can use as a resource on the landscape of continuous delivery
Home Page: https://l.cd.foundation
License: Apache License 2.0
###Category request:
The CDF landscape should have a security and compliance category for projects such as OPA.
Appium is an open-source test automation framework for use with native, hybrid and mobile web apps. http://appium.io/
Hey all,
Was looking to do some updates to the cdf-landscape and wanted to clarify one of the lines in the README:
'Projects must be open source and hosted on or mirrored to GitHub.'
Is this accurate for new entries ? I noticed there's a few closed source projects on the landscape and wanted to clarify ahead of time.
Brought up by @tracymiranda and @sbtaylor15 at landscape wg meeting.
To cover reporting and dashboards, etc.
potential projects
Four Keys Project
Open Telementry -- potential category of Observability
Daily Motion's Dora metrics project
Hygieia- end to end monitoring
The @cdfoundation/toc should consider scoping out a basic ROADMAP on what type of projects it is seeking and some mid-long term goals.
To the best of my knowledge, Flux does not have the concept of pipelines. It is only a set of gitops controllers.
It should be moved to a new category called "GitOps" along with Argo CD
Related to #175
After over a year of existence, the CDF landscape merits a reconsideration of the categories informing its view on the CI/CD ecosystem.
We welcome suggestions on how the categories can be altered with new additions, different/more logical groupings, etc.
If you have a suggestion for new categories or on how the projects should be grouped, please Raise An Issue for discussion and link that issue to this one.
In addition, we welcome additions or edits to projects on the CDF landscape. To do so, please raise a PR to add/edit a project, see New Entries.
Handle policy management tools that fit into the pipeline.
Event driven projects and tools, ie CDEvents
Cloud native is a characteristic/trait. It doesn't make sense to have a category, because then 90% of the other cards should also be here.
It also gives the false impression that tools that are not there are "not" cloud native.
Isn't Tekton cloud native?
Isn't ArgoCD cloud native?
Isn't Shipwright cloud native?
The current contents of this "category" are unrelated. Terraform is a CLI that implements infrastructure as code, Rancher is a cluster orchestration/management platform, Alibaba is a whole cloud provider, while Ketch is an application for Kubernetes deployments.
Related to #175
Raising this as an issue, despite the guidelines, as I'm waiting to hear back from puppet on if the current category was a deliberate choice. Once I've heard back I'll open a PR if required. Wanted to make sure this was visible in case anyone else has the same query.
Puppet generally is viewed as a tool in the same space as Chef/Saltstack/Ansible/etc. As we have a category for those tools, I /think/ puppet should sit under there.
For the Jenkins X card, no CII badge is being referenced:
However, Jenkins X does have a CII badge.
The CII badge for Jenkins X is 3237: https://bestpractices.coreinfrastructure.org/en/projects/3237
We would appreciate it if this could be updated.
Thank you.
If you see an error in the cards or missing ones, please don't create an issue here. Instead, edit landscape.yml (you can even do it via the GitHub web interface) and open a pull request. Then, review the preview staging server that's posted to your pull request and add a comment if your new or updated card looks correct and is ready to merge. Before going forward, please carefully review the sections of the Readme covering new entries, corrections, and logos: https://github.com/cncf/landscape/blob/master/README.md.
Argo is actually 4 independent and self-contained projects
For the Jenkins X card, the incorrect CII badge is being referenced.
In the processed_landscape.yml, the incorrect badge is referenced here: https://github.com/cdfoundation/cdf-landscape/blob/master/processed_landscape.yml#L257
The correct CII badge for Jenkins X is 3237: https://bestpractices.coreinfrastructure.org/en/projects/3237
We would appreciate it if this could be updated.
Thank you.
Jenkins, Jenkins X, Spinnaker and Tekton are all "graduated" CDF projects and shouldn't be labeled as "incubating."
Ref: #84
Looking for clarification and potential documentation update around handling of inactive landscape entries
Request made to add Linkedin Qark to the CDF Landscape. Presently the repository ( https://github.com/linkedin/qark ) has been inactive for ~15 months.
Are there any hard guidelines at the moment around project activity, and if not should there be. Additionally if there are it could be useful to include this in the documentation
by removing guidance around OSS and github minimum stars, we need new language to provide guidance on how TOC will review (and some tooling to support this).
The text is overlapping here, and google search console informed me about it
Please replace this line with a brief summary of your issue.
Please note by far the quickest way to get a new feature is to file a Pull Request.
To the best of my knowledge, Flagger does not have the concept of pipelines. It is only a canary/blue/green deployment mechanism
It should be moved to a new category called "Progressive Delivery" along with Argo Rollouts
Related to #175
There should be a category for SCM systems for CI/CD
We used to have one in the CNCF landscape but decided that was out of scope, I think it's in perfect scope for CDF... see this post for an older picture: https://medium.com/memory-leak/cloud-native-landscape-celebrates-first-anniversary-69a4eb829505
OSS requirement for landscape presence should probably be lifted
Add missing QR code
Need to add the circle I on the category and backed with the category description documentation.
current restrictions of layout means cards are per company/organization and can only be in one category. Proposal is to allow for better granularity by allowing for a single organization to be represented in multiple categories, need guidelines for this
longer term since we're solely focusing on continuous delivery issues and we have technology that spans multiple parts of that process, consider changing how the groupings are organized to reflect that more accurately (this would replace having replicated cards in multiple categories)
This is a list of potential project to consider adding to the CDF landscape, not a task list.
These projects are part of the CNCF landscape within the Continuous Integration & Delivery category.
Note: We don't want to simply replicate the CNCF landscape, but there will be cross over within the CI/CD and other categories.
For PRs which add a project listed below, please link to this issue.
If you have a doubt on the best category for a project, please discuss on this issue, or on the PR which adds the project.
We should have a category around 'catalogs.' This is really where tools like Ortelius and Backstage should go. There are also commercial tools like LeanIX, Effx, Cortex and Opslevel would go.
Please note by far the quickest way to get a new feature is to file a Pull Request.
Move SAP to General Members
Add all CDF members to landscape.
General members:
End User member:
Associate members:
Note:
Twistlock listed as General Member on website Members list
Twistlock on hold, as Palo Alto Networks is in landscape in its stead
Prisma Cloud by Palo Alto Networks is in landscape in General Member category
Prisma Cloud logo would appear much better in landscape if it was a stacked logo.
We should align website member list and landscape.
To the best of my knowledge, Helm does not build docker images. It should not be under the "image build" category.
It should be moved to a new category called "Application Delivery" along with Ketch (currently under cloud native).
Related to #175
Argo - Pipeline Orchestration
Looks like this was snagged from the Deep Learning Foundation and missed on fixup:
"This landscape is intended as a map to explore open source artificial intelligence (AI), machine learning (ML), and deep learning (DL) projects, and also shows the member companies of the LF Deep Learning Foundation. "
Setup CNAME for landscape
need to setup landscape.cd.foundation to be a CNAME to cdf-landscape.netlify.com and to have both http://l.cd.foundation and https://l.cd.foundation redirect to https://landscape.cd.foundation
right now we have ansible, e.g., but no puppet or chef
OpenMake logo needs to be SVG in cached_logos and hosted_logos
I know real estate is limited on the landscape, but the multitude of testing workloads across the lifecycle (shift left, shift right, release testing) could warrant a dedicated box for testing perhaps called "Continuous Quality". Allows for painting a broader (but connected) picture of testing across the lifecycle. Unit testing through post deployment testing.
add screwdriver.cd as incubating project
Please replace this line with a brief summary of your issue
Please note by far the quickest way to get a new feature is to file a Pull Request.
To add a new item, edit the landscape.yml (you can even do it via the GitHub web interface) and open a pull request. Then, review the preview staging server that's posted to your pull request and add a comment if your new or updated card looks correct and is ready to merge. Before going forward, please carefully review the sections of the Readme covering new entries, corrections, and logos: https://github.com/cncf/landscape/blob/master/README.md.
Ref: #84
Looking for clarification and potential documentation update around handling of projects which don't have a presence on crunchbase
Request made to add MobSF ( https://github.com/MobSF/Mobile-Security-Framework-MobSF) to the CDF Landscape. The company which created the tool ( https://opensecurity.in/ ) don't have a presence on crunchbase.
I imagine this is something which has been encountered with the CNCF Landscape so any experience from that would be great. It would be useful to understand if Crunchbase is a hard requirement. I'm uncertain as to how widely adopted crunchbase is internationally.
now that we've refined the process, need to take that badge off and re-add them as projects 'officially' graduate
Ref #4
1:19:14 PM: `cat src/iframeResizer.js`" > "$PROJECT_PATH"/dist/iframeResizer.js
1:19:14 PM: cp: cannot stat '/opt/build/repo/node_modules/iframe-resizer/js/iframeResizer.min.js': No such file or directory
1:19:15 PM: > [email protected] setup-robots /opt/build/repo/node_modules/interactive-landscape
1:19:15 PM: > babel-node tools/sitemap && babel-node tools/addRobots
1:19:19 PM: > [email protected] stop-old-ci /opt/build/repo/node_modules/interactive-landscape
1:19:19 PM: > (kill -9 `ps ux | grep ciServer | grep -v grep | awk -F ' ' '{print $2}'` 2>/dev/null || true)
1:19:20 PM: > [email protected] start-ci /opt/build/repo/node_modules/interactive-landscape
1:19:20 PM: > (babel-node tools/ciServer &) && sleep 10
1:19:22 PM: running a dist server on http://localhost:4000 ...
1:19:22 PM: [Browsersync] Access URLs:
1:19:22 PM: -------------------------------------
1:19:22 PM: Local: http://localhost:4000
1:19:22 PM: External: http://10.5.115.227:4000
1:19:22 PM: -------------------------------------
1:19:22 PM: UI: http://localhost:4001
1:19:22 PM: UI External: http://localhost:4001
1:19:22 PM: -------------------------------------
1:19:22 PM: [Browsersync] Serving files from: /opt/build/repo/dist
1:19:22 PM: [Browsersync] Watching files...
1:19:31 PM: > [email protected] integration-test /opt/build/repo/node_modules/interactive-landscape
1:19:31 PM: > jest
1:19:37 PM: PASS specs/tools/actualTwitter.spec.js
1:20:52 PM: FAIL specs/main.spec.js (77.372s)
1:20:52 PM: ● Console
1:20:52 PM: console.info specs/main.spec.js:69
1:20:52 PM: about to open a page http://localhost:4000/format=card-mode
1:20:52 PM: console.info specs/main.spec.js:71
1:20:52 PM: page is open
1:20:52 PM: console.info specs/main.spec.js:97
1:20:52 PM: about to open a main landscape page
1:20:52 PM: console.info specs/main.spec.js:41
1:20:52 PM: about to open a page http://localhost:4000
1:20:52 PM: console.info specs/main.spec.js:43
1:20:52 PM: page is open
1:20:52 PM: console.log specs/main.spec.js:138
1:20:52 PM: Checking we see CircleCI when filtering by organization CircleCI
1:20:52 PM: console.log specs/main.spec.js:142
1:20:52 PM: Checking we don't see CircleCI when filtering by organization CloudBees
1:20:52 PM: console.info specs/main.spec.js:69
1:20:52 PM: about to open a page http://localhost:4000/format=card-mode
1:20:52 PM: console.info specs/main.spec.js:71
1:20:52 PM: page is open
1:20:52 PM: console.info specs/main.spec.js:97
1:20:52 PM: about to open a main landscape page
1:20:52 PM: ● Normal browser › Main test › I visit a main page and have all required elements
1:20:52 PM: TimeoutError: waiting for XPath "//h1[text() = 'CDF Landscape']" failed: timeout 30000ms exceeded
1:20:52 PM: at new WaitTask (node_modules/puppeteer/lib/DOMWorld.js:561:28)
1:20:52 PM: at DOMWorld._waitForSelectorOrXPath (node_modules/puppeteer/lib/DOMWorld.js:490:22)
1:20:52 PM: at DOMWorld.waitForXPath (node_modules/puppeteer/lib/DOMWorld.js:453:17)
1:20:52 PM: at Frame.waitForXPath (node_modules/puppeteer/lib/FrameManager.js:643:47)
1:20:52 PM: at Frame.<anonymous> (node_modules/puppeteer/lib/helper.js:112:23)
1:20:52 PM: at Page.waitForXPath (node_modules/puppeteer/lib/Page.js:1098:29)
1:20:52 PM: at Object.waitForXPath (specs/main.spec.js:73:18)
1:20:52 PM: ● iPhone simulator › Main test › I visit a main page and have all required elements
1:20:52 PM: TimeoutError: waiting for XPath "//h1[text() = 'CDF Landscape']" failed: timeout 30000ms exceeded
1:20:52 PM: at new WaitTask (node_modules/puppeteer/lib/DOMWorld.js:561:28)
1:20:52 PM: at DOMWorld._waitForSelectorOrXPath (node_modules/puppeteer/lib/DOMWorld.js:490:22)
1:20:52 PM: at DOMWorld.waitForXPath (node_modules/puppeteer/lib/DOMWorld.js:453:17)
1:20:52 PM: at Frame.waitForXPath (node_modules/puppeteer/lib/FrameManager.js:643:47)
1:20:52 PM: at Frame.<anonymous> (node_modules/puppeteer/lib/helper.js:112:23)
1:20:52 PM: at Page.waitForXPath (node_modules/puppeteer/lib/Page.js:1098:29)
1:20:52 PM: at Object.waitForXPath (specs/main.spec.js:73:18)
1:20:52 PM: Test Suites: 1 failed, 1 passed, 2 total
1:20:52 PM: Tests: 2 failed, 12 passed, 14 total
1:20:52 PM: Snapshots: 0 total
1:20:52 PM: Time: 79.269s
1:20:52 PM: Ran all test suites.
1:20:53 PM: npm ERR! code ELIFECYCLE
1:20:53 PM: npm ERR! errno 1
1:20:53 PM: npm ERR!
1:20:53 PM: [email protected] integration-test: `jest`
1:20:53 PM: npm
1:20:53 PM: ERR! Exit status 1
1:20:53 PM: npm ERR!
1:20:53 PM: npm ERR!
1:20:53 PM: Failed at the [email protected] integration-test script.
1:20:53 PM: npm
1:20:53 PM: ERR! This is probably not a problem with npm. There is likely additional logging output above.
1:20:53 PM: npm
1:20:53 PM: ERR! A complete log of this run can be found in:
1:20:53 PM: npm ERR! /opt/buildhome/.npm/_logs/2019-09-23T20_20_53_092Z-debug.log
1:20:53 PM: > [email protected] stop-old-ci /opt/build/repo/node_modules/interactive-landscape
1:20:53 PM: > (kill -9 `ps ux | grep ciServer | grep -v grep | awk -F ' ' '{print $2}'` 2>/dev/null || true)
1:20:53 PM: npm
1:20:53 PM: ERR! code ELIFECYCLE
1:20:53 PM: npm ERR!
1:20:53 PM: errno 1
1:20:53 PM: npm ERR!
Some feedback about the CDF Landscape was raised as part of the SwampUP days.
Specifically the lack of categorisation for tools such as white source, blackduck, etc.
I'm happy to create some pull requests, but wanted to check here on a couple of points:
I feel like there is value in having these tools on the landscape, and potentially a new category for them. Although I'm not sure on the naming (OSS Compliance Management doesn't feel quite right )
Would be great to get some feedback on it.
Make the landscape bigger and enable scrolling.
@markyjackson-taulia to create new issue templates and actions automation once org access is granted.
Cc @tequilarista as per the discussion on Friday’s landscape meeting
Dependency Management is a hot topic for the software supply chain these days. It would be nice to have a dedicated category for that. It could include both dependency update automation (Dependabot, Renovate, UpdateCLI) and tools focused on dependency scanning like Whitesource or Snyk
key tech should be represented
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.