docs/index.xml at main · eclipse-symphony/docs · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Eclipse Symphony Documentation on Project Symphony Docs</title>
    <link>https://eclipse-symphony.github.io/docs/</link>
    <description>Recent content in Eclipse Symphony Documentation on Project Symphony Docs</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="https://eclipse-symphony.github.io/docs/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Overview</title>
      <link>https://eclipse-symphony.github.io/docs/concepts/overview/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>https://eclipse-symphony.github.io/docs/concepts/overview/</guid>
      <description>Symphony operates within an orchestration layer, strategically positioned atop preexisting tools and services. To establish uniformity amidst the diverse edge environment, Symphony relies on a set of fundamental high-level abstractions. These encompass state-seeking, graph, workflow, and orchestration models. These foundational abstractions empower Symphony to deliver robust functionalities across various technologies and platforms while maintaining a concise object model.
Abstractions Information graph: How Symphony organizes, accesses, and synchronizes enterprise information. Orchestration model: How Symphony defines the components that make up a scenario.</description>
    </item>

    <item>
      <title>Run Symphony as a Single Process</title>
      <link>https://eclipse-symphony.github.io/docs/tutorials/run-symphony-as-single-process/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>https://eclipse-symphony.github.io/docs/tutorials/run-symphony-as-single-process/</guid>
      <description>This tutorial shows you how to launch Symphony as a single process and call the Symphony APIs. Since all state is kept in memory, you can shut it down safely with no cleanup and no leftovers.
Part 1: Launch Symphony in a Process Install Maestro and launch Symphony as a process (enabled by the --no-k8s switch):
Bash (Linux/WSL/Mac) PowerShell (Windows) wget -q https://raw.githubusercontent.com/eclipse-symphony/symphony/master/cli/install/install.sh -O - | /bin/bash maestro up --no-k8s powershell -Command &amp;#34;iwr -useb https://raw.</description>
    </item>

    <item>
      <title>Run Symphony on Kubernetes</title>
      <link>https://eclipse-symphony.github.io/docs/tutorials/run-symphony-on-k8s/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>https://eclipse-symphony.github.io/docs/tutorials/run-symphony-on-k8s/</guid>
      <description>This tutorial shows you how to deploy Symphony to a Kubernetes cluster and use kubectl to interact with Symphony API in addition to REST API.
Part 1: Deploy Symphony to a Kubernetes cluster Install Maestro and deploy Symphony to a Kubernetes cluster, to which your kubectl is currently pointing:
Bash (Linux/WSL/Mac) PowerShell (Windows) wget -q https://raw.githubusercontent.com/eclipse-symphony/symphony/master/cli/install/install.sh -O - | /bin/bash maestro up powershell -Command &amp;#34;iwr -useb https://raw.githubusercontent.com/eclipse-symphony/symphony/master/cli/install/install.ps1 | iex&amp;#34; maestro up You should see outputs like:</description>
    </item>

    <item>
      <title>Embracing the Ecosystem</title>
      <link>https://eclipse-symphony.github.io/docs/ecosystem/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>https://eclipse-symphony.github.io/docs/ecosystem/</guid>
      <description>As a platform-neutral orchestrator, Symphony is designed to work with existing ecosystems through its extensibility model. The following summary highlights how Symphony natively integrates with various projects, services, platforms, and tools, while allowing additional extensions to be introduced at any time.
Target Providers Symphony Target Providers are responsible for applying updates to target devices or clusters. Symphony currently includes the following built-in target providers:
Azure Device Update for IoT Hub Azure Resource Manager (ARM) Bash Script Docker Eclipse Ankaios Eclipse uProtocol Helm Kubernetes ConfigMap Kubernetes Ingress Kubernetes Pods PowerShell RESTful API Windows 10/11 Sideloading Symphony Components Symphony system components can be swapped out to support different deployment needs and scenarios.</description>
    </item>

    <item>
      <title>Counter Campaign</title>
      <link>https://eclipse-symphony.github.io/docs/samples/counter-campaign/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>https://eclipse-symphony.github.io/docs/samples/counter-campaign/</guid>
      <description>This is a simple campaign that counts from a given value up to 20. It contains a single providers.stage.counter stage, which takes an input value, val, increments it by 1, and passes the updated value through the trigger for the next stage.
A conditional stage selector selects the next stage. If val is less than 20, the selector routes execution back to the same counter stage, creating a loop. Once val reaches 20, the selector chooses an empty stage instead, terminating the campaign.</description>
    </item>

    <item>
      <title>Information Graph</title>
      <link>https://eclipse-symphony.github.io/docs/concepts/abstractions/info_graph/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>https://eclipse-symphony.github.io/docs/concepts/abstractions/info_graph/</guid>
      <description>Symphony provides a generic graph data structure through the object type Catalog. A catalog can be used to model any information ontologies, hardware topologies, asset trees, BOMs, artifact catalogs and more.
Typically, an enterprise needs to manage diverse catalogs encompassing assets, software packages, configurations, and policies. Various personnel within an organization often require access to these catalogs, each with their unique perspectives and scopes. Unfortunately, this valuable information is frequently dispersed across multiple storage repositories behind different systems.</description>
    </item>

    <item>
      <title>Orchestration Model</title>
      <link>https://eclipse-symphony.github.io/docs/concepts/abstractions/orch_model/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>https://eclipse-symphony.github.io/docs/concepts/abstractions/orch_model/</guid>
      <description>As an orchestrator, Symphony purposefully designs a modeling language for orchestration purposes. We refer to this model as the orchestration model. Objects in the orchestration model establish desired state of a system. Symphony runs a continuous state seeking loop that brings the probed system current state towards the desired state.
Three core object types Symphony desired state is described using three core object types: Solution, Target, and Instance.
A Solution describes a software stack.</description>
    </item>

    <item>
      <title>State Seeking</title>
      <link>https://eclipse-symphony.github.io/docs/concepts/abstractions/state_seeking/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>https://eclipse-symphony.github.io/docs/concepts/abstractions/state_seeking/</guid>
      <description>Many software management problems can be viewed as a state seeking problem: a system reports its current state, a user specifies a new desired state, and a state seeking system brings the current state towards the desired state.
With this high-level abstraction, Symphony unifies the workflow of software deployment, software update, configuration management, policy management, device update, firmware update, OS update and many other tasks where a system needs to be updated according to a given new state.</description>
    </item>

    <item>
      <title>Workflows</title>
      <link>https://eclipse-symphony.github.io/docs/concepts/abstractions/workflows/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>

      <guid>https://eclipse-symphony.github.io/docs/concepts/abstractions/workflows/</guid>
      <description>Symphony employs a state-seeking approach to maintain a system according to user-defined desired states. Nevertheless, there are situations where orchestrating system control necessitates capabilities beyond state-seeking. For example, a scenario may require an approval process prior to initiating a deployment; in such cases, Symphony needs the capability to trigger an approval workflow before proceeding with its state-seeking operations. Another example is managing canary deployments, which requires the multi-step operation of rolling out a new version, adjusting your traffic shapes, validating the new version, and then gradually shifting traffic to the new version (and rolling back as needed).</description>
    </item>

  </channel>
</rss>