{"metadata":{"image":[],"title":"","description":""},"api":{"url":"","auth":"required","params":[],"results":{"codes":[]}},"next":{"description":"","pages":[]},"title":"Components","type":"basic","slug":"components","excerpt":"These are the components that make Paz","body":"[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Administrative Dashboard\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Repo\",\n  \"body\": \"```\\ngit clone https://github.com/paz-sh/paz-web\\n```\"\n}\n[/block]\nA beautiful and easy-to-use web UI for managing your services and observing the health of your cluster. Proudly built with Ember.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Command Line Administrative Interface\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Repo\",\n  \"body\": \"```\\ngit clone https://github.com/paz-sh/paz.sh.git\\n```\"\n}\n[/block]\nThe Paz command-line interface\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Scheduler\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Repo\",\n  \"body\": \"```\\ngit clone https://github.com/paz-sh/paz-scheduler.git\\n```\"\n}\n[/block]\nScheduler receives HTTP POST commands to deploy services that are defined in the service directory. A history of deployments and associated configurations is also available from the scheduler.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Service Directory\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Repo\",\n  \"body\": \"```\\ngit clone https://github.com/paz-sh/paz-service-directory.git\\n```\"\n}\n[/block]\nA catalog of your services and their configuration (e.g. environment variables, data volumes, port mappings and number of instances to launch)\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Orchestrator\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Repo\",\n  \"body\": \"```\\ngit clone https://github.com/paz-sh/paz-orchestrator.git\\n```\"\n}\n[/block]\nOrchestrator ties all of the other services together, providing a single access-point for the front-end to interface with. Also offers a web socket endpoint for realtime updates to the web front-end.\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"HTTP Load Balancer\"\n}\n[/block]\n\n[block:callout]\n{\n  \"type\": \"info\",\n  \"title\": \"Repo\",\n  \"body\": \"```\\ngit clone https://github.com/paz-sh/paz-haproxy.git\\n```\"\n}\n[/block]\n\n[block:api-header]\n{\n  \"type\": \"basic\",\n  \"title\": \"Monitoring and Logging\"\n}\n[/block]\nCurrently cAdvisor is used for monitoring, and there is not yet any centralised logging. Monitoring and logging are high-priority features on the roadmap.","updates":["54fb3f47019b2537006d0112","5528469f60c60f230003fb6f"],"order":0,"isReference":false,"hidden":false,"sync_unique":"","link_url":"","link_external":false,"_id":"54fa477e08b56339003791c3","__v":9,"category":{"sync":{"isSync":false,"url":""},"pages":["54fa0051f63cf9210041c3c4","54fa46d9c6db4517005b011b","54fa477e08b56339003791c3","54fad90cf63cf9210041c667"],"title":"APIs","slug":"apis","order":2,"from_sync":false,"reference":false,"_id":"54fa0050f63cf9210041c3c2","__v":4,"project":"54fa004ff63cf9210041c3be","createdAt":"2015-03-06T19:30:24.800Z","version":"54fa0050f63cf9210041c3c1"},"createdAt":"2015-03-07T00:34:06.740Z","githubsync":"","version":{"version":"1.0","version_clean":"1.0.0","codename":"","is_stable":true,"is_beta":false,"is_hidden":false,"is_deprecated":false,"categories":["54fa0050f63cf9210041c3c2","54fa42b3961fea210092068e","54facefd5c41173700ecf296","54fad9d5f63cf9210041c669","54fae9ed5c41173700ecf2ad"],"_id":"54fa0050f63cf9210041c3c1","__v":5,"createdAt":"2015-03-06T19:30:24.258Z","project":"54fa004ff63cf9210041c3be","releaseDate":"2015-03-06T19:30:24.258Z"},"project":"54fa004ff63cf9210041c3be","user":"54fa0018e7a0ba2f00306211"}

Components

These are the components that make Paz

[block:api-header] { "type": "basic", "title": "Administrative Dashboard" } [/block] [block:callout] { "type": "info", "title": "Repo", "body": "```\ngit clone https://github.com/paz-sh/paz-web\n```" } [/block] A beautiful and easy-to-use web UI for managing your services and observing the health of your cluster. Proudly built with Ember. [block:api-header] { "type": "basic", "title": "Command Line Administrative Interface" } [/block] [block:callout] { "type": "info", "title": "Repo", "body": "```\ngit clone https://github.com/paz-sh/paz.sh.git\n```" } [/block] The Paz command-line interface [block:api-header] { "type": "basic", "title": "Scheduler" } [/block] [block:callout] { "type": "info", "title": "Repo", "body": "```\ngit clone https://github.com/paz-sh/paz-scheduler.git\n```" } [/block] Scheduler receives HTTP POST commands to deploy services that are defined in the service directory. A history of deployments and associated configurations is also available from the scheduler. [block:api-header] { "type": "basic", "title": "Service Directory" } [/block] [block:callout] { "type": "info", "title": "Repo", "body": "```\ngit clone https://github.com/paz-sh/paz-service-directory.git\n```" } [/block] A catalog of your services and their configuration (e.g. environment variables, data volumes, port mappings and number of instances to launch) [block:api-header] { "type": "basic", "title": "Orchestrator" } [/block] [block:callout] { "type": "info", "title": "Repo", "body": "```\ngit clone https://github.com/paz-sh/paz-orchestrator.git\n```" } [/block] Orchestrator ties all of the other services together, providing a single access-point for the front-end to interface with. Also offers a web socket endpoint for realtime updates to the web front-end. [block:api-header] { "type": "basic", "title": "HTTP Load Balancer" } [/block] [block:callout] { "type": "info", "title": "Repo", "body": "```\ngit clone https://github.com/paz-sh/paz-haproxy.git\n```" } [/block] [block:api-header] { "type": "basic", "title": "Monitoring and Logging" } [/block] Currently cAdvisor is used for monitoring, and there is not yet any centralised logging. Monitoring and logging are high-priority features on the roadmap.