diff --git a/docs/assets/OrgStructure.png b/docs/assets/OrgStructure.png new file mode 100644 index 000000000..1d3227b82 Binary files /dev/null and b/docs/assets/OrgStructure.png differ diff --git a/docs/assets/landingZone.png b/docs/assets/landingZone.png new file mode 100644 index 000000000..86350f0d5 Binary files /dev/null and b/docs/assets/landingZone.png differ diff --git a/docs/meshstack.index.md b/docs/meshstack.index.md index 7170e84ec..97a49ad49 100644 --- a/docs/meshstack.index.md +++ b/docs/meshstack.index.md @@ -15,9 +15,12 @@ It is NOT a meta-layer across clouds. Users access native cloud APIs for their d ## Central Concepts -meshStack uses the concepts of Workspaces and Projects to represent the structure of existing application teams in the meshStack platform. Application Team can manage Tenants inside Projects. In order to reflect the organization's compliance and security standards in the cloud a Landing Zone is applied to every Tenant. Building Blocks can be leveraged either as part of a modular Landing Zone or additionally on top of a Tenant. Building Blocks are deployed based on the configuration provided in the Building Block definition. +meshStack uses the concepts of Workspaces and Projects to represent the structure of existing application teams in the meshStack platform. Application Team can manage Tenants inside Projects. +![meshModel](assets/OrgStructure.png) + +In order to reflect the organization's compliance and security standards in the cloud a Landing Zone is applied to every Tenant. Building Blocks can be leveraged either as part of a modular Landing Zone or additionally on top of a Tenant. Building Blocks are deployed based on the configuration provided in the Building Block definition. meshStack supports the management of multiple platforms of the same or different type. Below you can see an overview of the relations between the individual elements in meshStack as objects. -![meshModel](assets/meshModel.png) +![landingZones](assets/landingZone.png) ## Integrations diff --git a/website/blog/2024-05-15-Release-0.md b/website/blog/2024-05-15-Release-0.md new file mode 100644 index 000000000..e807bf06e --- /dev/null +++ b/website/blog/2024-05-15-Release-0.md @@ -0,0 +1,78 @@ +--- +author: meshcloud +title: Release 2024.22.0 +--- + +Release period: 2024-05-08 to 2024-05-15 + +This release includes the following issues: +* Fix deprecated Building Block Definitions +* Landing zone-only definitions not shown in Marketplace +* Lenient parsing of OpenStack catalogs +* Improved Tags Layouts with Hover-Activated Overflow +* Define Policies from Workspace to Landing Zone +* Better replication remarks for users without an EUID +* Manage your API Keys from within your workspace +* Manage projects with API Keys + + +## Ticket Details +### Fix deprecated Building Block Definitions +**Audience:** User
+ +#### Description +Previously, Building Block Definitions owned by a workspace with several published versions were incorrectly shown as deprecated. Now, they are accurately displayed as published. + +### Landing zone-only definitions not shown in Marketplace +**Audience:** User
+ +#### Description +Building Block Definitions marked as 'Use in Landing Zones only' were erroneously accessible in the Marketplace via the "Related to" section of a Platform. This allowed users to select and book these definitions without the required landing zone, contrary to their intended use. This issue has been fixed. + +### Lenient parsing of OpenStack catalogs +**Audience:** Operator
+ +#### Description +When configuring OpenStack, operators have a lot of freedom to configure catalog entries. +We fixed an error where meshStack failed to parse catalogs containing unexpected "interface" +values for a catalog entry. + +### Improved Tags Layouts with Hover-Activated Overflow +**Audience:** User
+ +#### Description +In this release, we've resolved container overflow issues caused by long tag values. Now, our application +displays approximately three tag values visibly, with the remaining tags shown when hovered over. This +enhancement ensures improved readability and user experience, addressing concerns about disrupted layouts +and extended content beyond screen boundaries. + +### Define Policies from Workspace to Landing Zone +**Audience:** Partner
+ +#### Description +It is now also possible to define a Policy from Workspace to Landing Zone. A good example for +such a policy is e.g. a policy for a matching Business Unit on your Workspaces and Landing Zones. +That way, you can restrict certain Landing Zones to only Workspaces that belong to a certain Business Unit. + +### Better replication remarks for users without an EUID +**Audience:** User
+ +#### Description +Users whose EUID is missing, can not be added to a platform tenant. But previously +the error replication remark was not consistent and on rare occasions could be missing. +This has been fixed. + +### Manage your API Keys from within your workspace +**Audience:** Customer
+ +#### Description +API Keys for their own workspace can now be managed by Workspace Owners and Workspace Managers. +Navigate to the 'API Keys' sub tab within the 'Workspace Access' tab on the Workspace Control Plane to do so. + +### Manage projects with API Keys +**Audience:** User
+ +#### Description +You can now use your API Keys to manage (create, update, delete) projects +within your workspace. More objects will be supported soon. +