Skip to content

Commit

Permalink
Deployed 7d0674e with MkDocs version: 1.5.3
Browse files Browse the repository at this point in the history
  • Loading branch information
pboers1988 committed Mar 13, 2024
1 parent 1097863 commit 21fac15
Show file tree
Hide file tree
Showing 3 changed files with 2 additions and 3 deletions.
3 changes: 1 addition & 2 deletions index.html
Original file line number Diff line number Diff line change
Expand Up @@ -542,8 +542,7 @@ <h2 id="core-tooling">Core tooling:</h2>
<a href="https://pepy.tech/project/orchestrator-core"><img alt="pypi-downloads" src="https://static.pepy.tech/badge/orchestrator-core" /></a></li>
<li><a href="https://github.com/workfloworchestrator/orchestrator-ui-library">Orchestrator-UI</a> Component library for our NextJS
app on top of the Orchestrator-core. Downloads:
[<img alt="npm-downloads" src="https://img.shields.io/npm/dt/%40orchestrator-ui%2Forchestrator-ui-components" />]
(https://github.com/workfloworchestrator/orchestrator-ui-library)</li>
<a href="https://github.com/workfloworchestrator/orchestrator-ui-library"><img alt="npm-downloads" src="https://img.shields.io/npm/dt/%40orchestrator-ui%2Forchestrator-ui-components" /></a></li>
<li><a href="https://github.com/workfloworchestrator/example-orchestrator-ui/">Orchestrator Example UI</a> Example ui with a NextJS
implementation of our component library. </li>
</ul>
Expand Down
2 changes: 1 addition & 1 deletion search/search_index.json
Original file line number Diff line number Diff line change
@@ -1 +1 @@
{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Workflow Orchestrator Programme","text":"<p>Welcome to the Workflow Orchestrator Programme homepage. This opensource collaboration develops software, tools and best practices for automating and orchestrating networks. Our vision is to create an ecosystem of Software that enables users to Automate and Orchestrate their network.</p>"},{"location":"#core-tooling","title":"Core tooling:","text":"<p>The Core tooling developed by the programme:</p> <ul> <li>Orchestrator-Core: This Python Programme leverages the power of FastAPI to create an orchestration engine. Downloads: </li> <li>Orchestrator-UI Component library for our NextJS app on top of the Orchestrator-core. Downloads: [] (https://github.com/workfloworchestrator/orchestrator-ui-library)</li> <li>Orchestrator Example UI Example ui with a NextJS implementation of our component library. </li> </ul>"},{"location":"#other-software","title":"Other Software:","text":"<p>Software maintained by the Workflow Orchestrator programme:</p> <ul> <li>LSO: This application provides an API layer on top of Ansible playbooks.</li> <li>Example Orchestrator: This repository houses a Docker-compose running a full stack of the Orchestrator, UI and Netbox. It includes examples our best (coding) practices and an example integration with Netbox</li> <li>PyNSO-Restconf: A thin client for interfacing with Cisco NSO using Restconf</li> <li>Pydantic-Forms: A library that includes standardised Python Form classes that can be used when generating form components from JSON-schema</li> <li>SuPA: An NSI Ultimate provider agent with a gRPC api</li> <li>PolyNSI: A Soap to gRPC NSI proxy</li> </ul>"},{"location":"about/","title":"About","text":"<p>The purpose of the Workflow Orchestrator programme is to provide an easy-to-use set of tools, samples and documentation for automating and orchestrating order, administration and provisioning processes. The programme was started to facilitate worldwide collaboration in the field of (network) automation and orchestration, by sharing code, knowledge, examples and ideas. The Workflow Orchestrator programme has been established under The Commons Conservancy foundation and runs its own governance. </p>"},{"location":"about/#current-positions","title":"Current positions:","text":""},{"location":"about/#board-members","title":"Board Members","text":"<ul> <li>Migiel de Vos (Chair) [until May 2023]</li> <li>Hans Trompert [until May 2024] </li> <li>John Macauley [until May 2023]</li> </ul>"},{"location":"about/#core-developers","title":"Core Developers","text":"<ul> <li>Peter Boers (Technical Lead)</li> <li>Scott Richmond</li> </ul> <p>Several projects with code, examples and documentation have been defined and are available here. You can also visit our github page.</p>"},{"location":"board-elections/","title":"Leadership","text":"<p>Elections will take place to fill two seats on the Workflow Orchestrator Board for two-year terms. </p> <p>The Workflow Orchestrator programme is now receiving nominations to the Workflow Orchestrator Board. The terms for the following Workflow Orchestrator Board members will expire in May 2021: - Migiel de Vos (chair) - John Macauley There will be an election to fill the vacant seats at the Workflow Orchestrator board meeting on May 26th 2021. These seats will be filled for two-year terms. You can nominate yourself or be nominated by a member of the Workflow Orchestrator programme. All nominees must accept the nomination and confirm that they agree to the Workflow Orchestrator statutes. They are then listed as nominees. You can nominate an individual by sending an email to the Workflow Orchestrator Board. The nomination period will end on May 19th 2021 00:00 GMT. Current listed nominees: - Migiel de Vos (chair) - John Macauley</p>"},{"location":"contact/","title":"Contact","text":"<p>We'd love to hear your thoughts, inspiration and ideas! Feel free to contact us via one of the channels below: </p> <p>Email: [email protected] Github: https://github.com/workfloworchestrator/</p>"},{"location":"members/","title":"Programme Members","text":"<p>Organisations that are involved with the Workflow Orchestrator programme are:</p>"},{"location":"members/#partners","title":"Partners","text":""},{"location":"members/#founding-partners","title":"Founding Partners","text":""},{"location":"members/#partners_1","title":"Partners","text":""},{"location":"members/#graduates","title":"Graduates","text":"<p>If you or your organisation would like to contribute please get in touch!</p>"}]}
{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Workflow Orchestrator Programme","text":"<p>Welcome to the Workflow Orchestrator Programme homepage. This opensource collaboration develops software, tools and best practices for automating and orchestrating networks. Our vision is to create an ecosystem of Software that enables users to Automate and Orchestrate their network.</p>"},{"location":"#core-tooling","title":"Core tooling:","text":"<p>The Core tooling developed by the programme:</p> <ul> <li>Orchestrator-Core: This Python Programme leverages the power of FastAPI to create an orchestration engine. Downloads: </li> <li>Orchestrator-UI Component library for our NextJS app on top of the Orchestrator-core. Downloads: </li> <li>Orchestrator Example UI Example ui with a NextJS implementation of our component library. </li> </ul>"},{"location":"#other-software","title":"Other Software:","text":"<p>Software maintained by the Workflow Orchestrator programme:</p> <ul> <li>LSO: This application provides an API layer on top of Ansible playbooks.</li> <li>Example Orchestrator: This repository houses a Docker-compose running a full stack of the Orchestrator, UI and Netbox. It includes examples our best (coding) practices and an example integration with Netbox</li> <li>PyNSO-Restconf: A thin client for interfacing with Cisco NSO using Restconf</li> <li>Pydantic-Forms: A library that includes standardised Python Form classes that can be used when generating form components from JSON-schema</li> <li>SuPA: An NSI Ultimate provider agent with a gRPC api</li> <li>PolyNSI: A Soap to gRPC NSI proxy</li> </ul>"},{"location":"about/","title":"About","text":"<p>The purpose of the Workflow Orchestrator programme is to provide an easy-to-use set of tools, samples and documentation for automating and orchestrating order, administration and provisioning processes. The programme was started to facilitate worldwide collaboration in the field of (network) automation and orchestration, by sharing code, knowledge, examples and ideas. The Workflow Orchestrator programme has been established under The Commons Conservancy foundation and runs its own governance. </p>"},{"location":"about/#current-positions","title":"Current positions:","text":""},{"location":"about/#board-members","title":"Board Members","text":"<ul> <li>Migiel de Vos (Chair) [until May 2023]</li> <li>Hans Trompert [until May 2024] </li> <li>John Macauley [until May 2023]</li> </ul>"},{"location":"about/#core-developers","title":"Core Developers","text":"<ul> <li>Peter Boers (Technical Lead)</li> <li>Scott Richmond</li> </ul> <p>Several projects with code, examples and documentation have been defined and are available here. You can also visit our github page.</p>"},{"location":"board-elections/","title":"Leadership","text":"<p>Elections will take place to fill two seats on the Workflow Orchestrator Board for two-year terms. </p> <p>The Workflow Orchestrator programme is now receiving nominations to the Workflow Orchestrator Board. The terms for the following Workflow Orchestrator Board members will expire in May 2021: - Migiel de Vos (chair) - John Macauley There will be an election to fill the vacant seats at the Workflow Orchestrator board meeting on May 26th 2021. These seats will be filled for two-year terms. You can nominate yourself or be nominated by a member of the Workflow Orchestrator programme. All nominees must accept the nomination and confirm that they agree to the Workflow Orchestrator statutes. They are then listed as nominees. You can nominate an individual by sending an email to the Workflow Orchestrator Board. The nomination period will end on May 19th 2021 00:00 GMT. Current listed nominees: - Migiel de Vos (chair) - John Macauley</p>"},{"location":"contact/","title":"Contact","text":"<p>We'd love to hear your thoughts, inspiration and ideas! Feel free to contact us via one of the channels below: </p> <p>Email: [email protected] Github: https://github.com/workfloworchestrator/</p>"},{"location":"members/","title":"Programme Members","text":"<p>Organisations that are involved with the Workflow Orchestrator programme are:</p>"},{"location":"members/#partners","title":"Partners","text":""},{"location":"members/#founding-partners","title":"Founding Partners","text":""},{"location":"members/#partners_1","title":"Partners","text":""},{"location":"members/#graduates","title":"Graduates","text":"<p>If you or your organisation would like to contribute please get in touch!</p>"}]}
Binary file modified sitemap.xml.gz
Binary file not shown.

0 comments on commit 21fac15

Please sign in to comment.