You are viewing a plain text version of this content. The canonical link for it is here.
Posted to reviews@yunikorn.apache.org by GitBox <gi...@apache.org> on 2022/05/04 04:49:47 UTC
[GitHub] [yunikorn-site] yuchaoran2011 commented on a diff in pull request #158: [YUNIKORN-992] website update for 1.0.0 release
yuchaoran2011 commented on code in PR #158:
URL: https://github.com/apache/yunikorn-site/pull/158#discussion_r864453316
##########
src/pages/release-announce/1.0.0.md:
##########
@@ -0,0 +1,135 @@
+---
+id: rn-1.0.0
+title: Release Announcement v1.0.0
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# Release Announcement v1.0.0
+We are pleased to announce that the Apache YuniKorn community has voted to release 1.0.0. This is the first release of Apache YuniKorn after graduation from the incubator.
+
+Apache YuniKorn is a standalone resource scheduler, designed for managing, and scheduling Big Data workloads on container orchestration frameworks like Kubernetes for on-prem and on-cloud use cases.
+
+## Overview
+The Apache YuniKorn community has fixed 173 [JIRAs](https://issues.apache.org/jira/issues/?filter=12350818) in this release.
+
+Release manager: Wilfred Spiegelenburg
+
+Release date: 3 May 2022
+
+## Incompatible changes
+As part of this release a number of incompatible changes have been introduced.
+
+### helm upgrade
+With the changes made to the helm charts running a helm upgrade from an older version to 1.0.0 might not work.
+The workaround is to first uninstall the old version and then perform a clean installation of the current release.
+
+### Configuration changes
+Size modifiers are now supported for the queue configuration.
+This changes the way quota values are interpreted in the configuration.
+Before 1.0.0 all memory values were interpreted as _megabytes_ and vcore (cpu) values as _milli cores_.
+From 1.0.0 onwards memory values are specified in **bytes** and vcores are specified in **cores** [YUNIKORN-629](https://issues.apache.org/jira/browse/YUNIKORN-629).
+
+To maintain the same interpretation of values in the configuration make the following changes to the pre 1.0.0 configuration:
Review Comment:
```suggestion
To maintain the same interpretation of values in the configuration make the following changes to the pre-1.0.0 configuration:
```
##########
src/pages/release-announce/1.0.0.md:
##########
@@ -0,0 +1,135 @@
+---
+id: rn-1.0.0
+title: Release Announcement v1.0.0
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# Release Announcement v1.0.0
+We are pleased to announce that the Apache YuniKorn community has voted to release 1.0.0. This is the first release of Apache YuniKorn after graduation from the incubator.
+
+Apache YuniKorn is a standalone resource scheduler, designed for managing, and scheduling Big Data workloads on container orchestration frameworks like Kubernetes for on-prem and on-cloud use cases.
+
+## Overview
+The Apache YuniKorn community has fixed 173 [JIRAs](https://issues.apache.org/jira/issues/?filter=12350818) in this release.
+
+Release manager: Wilfred Spiegelenburg
+
+Release date: 3 May 2022
+
+## Incompatible changes
+As part of this release a number of incompatible changes have been introduced.
+
+### helm upgrade
+With the changes made to the helm charts running a helm upgrade from an older version to 1.0.0 might not work.
+The workaround is to first uninstall the old version and then perform a clean installation of the current release.
+
+### Configuration changes
+Size modifiers are now supported for the queue configuration.
+This changes the way quota values are interpreted in the configuration.
+Before 1.0.0 all memory values were interpreted as _megabytes_ and vcore (cpu) values as _milli cores_.
+From 1.0.0 onwards memory values are specified in **bytes** and vcores are specified in **cores** [YUNIKORN-629](https://issues.apache.org/jira/browse/YUNIKORN-629).
+
+To maintain the same interpretation of values in the configuration make the following changes to the pre 1.0.0 configuration:
+
+| type | change | old value | new value |
+|--------|--------|--------------|---------------|
+| memory | add M | memory: 2048 | memory: 2048M |
+| vcore | add m | vcore: 250 | vcore: 250m |
+| other | none | license: 1 | license: 1 |
+
+### Resource Display and Communication
+The conversion of memory resources of pods and other objects by the k8shim into megabytes could cause a discrepancy between the size accounted for by the Kubernetes tools and YuniKorn.
+This could lead to issues around node fits and autoscaling of nodes.
+In 1.0.0 all memory resources are converted to **bytes** before being used in calculation and communications [YUNIKORN-1105](https://issues.apache.org/jira/browse/YUNIKORN-1105).
+
+Resources in all REST response objects are no longer a single string but are JSON structures using a key value pair for each resource type.
Review Comment:
```suggestion
Resources in all REST response objects are no longer a single string but are JSON structures using a key-value pair for each resource type.
```
##########
src/pages/community/download.md:
##########
@@ -29,24 +29,25 @@ The downloads for the latest release are distributed via mirror sites.
Older releases can be downloaded from the Apache archive site.
All release artifacts should be checked for tampering using GPG or SHA-512.
-The latest release of Apache YuniKorn is v0.12.2.
+We publish pre-build docker images for everyone's convenience.
Review Comment:
pre-built?
##########
src/pages/release-announce/1.0.0.md:
##########
@@ -0,0 +1,135 @@
+---
+id: rn-1.0.0
+title: Release Announcement v1.0.0
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# Release Announcement v1.0.0
+We are pleased to announce that the Apache YuniKorn community has voted to release 1.0.0. This is the first release of Apache YuniKorn after graduation from the incubator.
+
+Apache YuniKorn is a standalone resource scheduler, designed for managing, and scheduling Big Data workloads on container orchestration frameworks like Kubernetes for on-prem and on-cloud use cases.
+
+## Overview
+The Apache YuniKorn community has fixed 173 [JIRAs](https://issues.apache.org/jira/issues/?filter=12350818) in this release.
+
+Release manager: Wilfred Spiegelenburg
+
+Release date: 3 May 2022
+
+## Incompatible changes
+As part of this release a number of incompatible changes have been introduced.
+
+### helm upgrade
+With the changes made to the helm charts running a helm upgrade from an older version to 1.0.0 might not work.
+The workaround is to first uninstall the old version and then perform a clean installation of the current release.
+
+### Configuration changes
+Size modifiers are now supported for the queue configuration.
+This changes the way quota values are interpreted in the configuration.
+Before 1.0.0 all memory values were interpreted as _megabytes_ and vcore (cpu) values as _milli cores_.
+From 1.0.0 onwards memory values are specified in **bytes** and vcores are specified in **cores** [YUNIKORN-629](https://issues.apache.org/jira/browse/YUNIKORN-629).
+
+To maintain the same interpretation of values in the configuration make the following changes to the pre 1.0.0 configuration:
+
+| type | change | old value | new value |
+|--------|--------|--------------|---------------|
+| memory | add M | memory: 2048 | memory: 2048M |
+| vcore | add m | vcore: 250 | vcore: 250m |
+| other | none | license: 1 | license: 1 |
+
+### Resource Display and Communication
+The conversion of memory resources of pods and other objects by the k8shim into megabytes could cause a discrepancy between the size accounted for by the Kubernetes tools and YuniKorn.
+This could lead to issues around node fits and autoscaling of nodes.
+In 1.0.0 all memory resources are converted to **bytes** before being used in calculation and communications [YUNIKORN-1105](https://issues.apache.org/jira/browse/YUNIKORN-1105).
+
+Resources in all REST response objects are no longer a single string but are JSON structures using a key value pair for each resource type.
+An example of the new resource JSON response object:
+```json
+"allocatedResource": {
+ "memory": 54000000,
+ "vcore": 80
+}
+```
+The REST representation does not include or support size modifiers.
+The change for using **bytes** in all communication for memory flows through into the REST response objects.
+CPU values, i.e. vcore, communication has not changed and still uses **milli cores**.
+The REST documentation has been updated to show the new resource structures [YUNIKORN-165](https://issues.apache.org/jira/browse/YUNIKORN-165).
+
+### Timestamps in REST responses
+All timestamps in the rest API are now returned as the number of nanoseconds elapsed since 1 January 1970 UTC.
+The time range in a `int64` that can be displayed ranges from the year 1678 or to the year 2262, see [Go Time UnixNano](https://pkg.go.dev/time#Time.UnixNano) for details.
+Timestamps in earlier releases were converted to a string as part of the REST response creation with inconsistent layouts [YUNIKORN-1170](https://issues.apache.org/jira/browse/YUNIKORN-1170).
+
+### Removal of old REST API endpoints
+The REST API has been updated with endpoints that support specifying partitions. The old versions which do not take a partition argument have been removed:
+
+- `/ws/v1/queues` replaced with `/ws/v1/partition/{partitionName}/queues`
+- `/ws/v1/apps` replaced with `ws/v1/partition/{partitionName}/queues/{queueName}/application`
+- `/ws/v1/nodes` replaced with `/ws/v1/partition/{partitionName}/nodes`
+
+[YUNIKORN-954](https://issues.apache.org/jira/browse/YUNIKORN-954)
+
+## Highlights
+
+### Plugin mode technical Preview
+As part of this release a new deployment mode is added which is build on top of the Scheduler Plugin Framework.
+This is a major change in the way the scheduler k8shim works. As the implementation is not considered mature as yet the deployment mode is considered a tech preview.
Review Comment:
```suggestion
This is a major change in the way the scheduler k8shim works. As the implementation is not considered mature yet the deployment mode is considered a tech preview.
```
##########
src/pages/release-announce/1.0.0.md:
##########
@@ -0,0 +1,135 @@
+---
+id: rn-1.0.0
+title: Release Announcement v1.0.0
+---
+
+<!--
+Licensed to the Apache Software Foundation (ASF) under one
+or more contributor license agreements. See the NOTICE file
+distributed with this work for additional information
+regarding copyright ownership. The ASF licenses this file
+to you under the Apache License, Version 2.0 (the
+"License"); you may not use this file except in compliance
+with the License. You may obtain a copy of the License at
+
+ http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing,
+software distributed under the License is distributed on an
+"AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+KIND, either express or implied. See the License for the
+specific language governing permissions and limitations
+under the License.
+-->
+
+# Release Announcement v1.0.0
+We are pleased to announce that the Apache YuniKorn community has voted to release 1.0.0. This is the first release of Apache YuniKorn after graduation from the incubator.
+
+Apache YuniKorn is a standalone resource scheduler, designed for managing, and scheduling Big Data workloads on container orchestration frameworks like Kubernetes for on-prem and on-cloud use cases.
+
+## Overview
+The Apache YuniKorn community has fixed 173 [JIRAs](https://issues.apache.org/jira/issues/?filter=12350818) in this release.
+
+Release manager: Wilfred Spiegelenburg
+
+Release date: 3 May 2022
+
+## Incompatible changes
+As part of this release a number of incompatible changes have been introduced.
+
+### helm upgrade
+With the changes made to the helm charts running a helm upgrade from an older version to 1.0.0 might not work.
+The workaround is to first uninstall the old version and then perform a clean installation of the current release.
+
+### Configuration changes
+Size modifiers are now supported for the queue configuration.
+This changes the way quota values are interpreted in the configuration.
+Before 1.0.0 all memory values were interpreted as _megabytes_ and vcore (cpu) values as _milli cores_.
+From 1.0.0 onwards memory values are specified in **bytes** and vcores are specified in **cores** [YUNIKORN-629](https://issues.apache.org/jira/browse/YUNIKORN-629).
+
+To maintain the same interpretation of values in the configuration make the following changes to the pre 1.0.0 configuration:
+
+| type | change | old value | new value |
+|--------|--------|--------------|---------------|
+| memory | add M | memory: 2048 | memory: 2048M |
+| vcore | add m | vcore: 250 | vcore: 250m |
+| other | none | license: 1 | license: 1 |
+
+### Resource Display and Communication
+The conversion of memory resources of pods and other objects by the k8shim into megabytes could cause a discrepancy between the size accounted for by the Kubernetes tools and YuniKorn.
+This could lead to issues around node fits and autoscaling of nodes.
+In 1.0.0 all memory resources are converted to **bytes** before being used in calculation and communications [YUNIKORN-1105](https://issues.apache.org/jira/browse/YUNIKORN-1105).
+
+Resources in all REST response objects are no longer a single string but are JSON structures using a key value pair for each resource type.
+An example of the new resource JSON response object:
+```json
+"allocatedResource": {
+ "memory": 54000000,
+ "vcore": 80
+}
+```
+The REST representation does not include or support size modifiers.
+The change for using **bytes** in all communication for memory flows through into the REST response objects.
+CPU values, i.e. vcore, communication has not changed and still uses **milli cores**.
+The REST documentation has been updated to show the new resource structures [YUNIKORN-165](https://issues.apache.org/jira/browse/YUNIKORN-165).
+
+### Timestamps in REST responses
+All timestamps in the rest API are now returned as the number of nanoseconds elapsed since 1 January 1970 UTC.
+The time range in a `int64` that can be displayed ranges from the year 1678 or to the year 2262, see [Go Time UnixNano](https://pkg.go.dev/time#Time.UnixNano) for details.
+Timestamps in earlier releases were converted to a string as part of the REST response creation with inconsistent layouts [YUNIKORN-1170](https://issues.apache.org/jira/browse/YUNIKORN-1170).
+
+### Removal of old REST API endpoints
+The REST API has been updated with endpoints that support specifying partitions. The old versions which do not take a partition argument have been removed:
+
+- `/ws/v1/queues` replaced with `/ws/v1/partition/{partitionName}/queues`
+- `/ws/v1/apps` replaced with `ws/v1/partition/{partitionName}/queues/{queueName}/application`
+- `/ws/v1/nodes` replaced with `/ws/v1/partition/{partitionName}/nodes`
+
+[YUNIKORN-954](https://issues.apache.org/jira/browse/YUNIKORN-954)
+
+## Highlights
+
+### Plugin mode technical Preview
+As part of this release a new deployment mode is added which is build on top of the Scheduler Plugin Framework.
Review Comment:
```suggestion
As part of this release a new deployment mode is added which is built on top of the [Scheduling Framework](https://kubernetes.io/docs/concepts/scheduling-eviction/scheduling-framework/).
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: reviews-unsubscribe@yunikorn.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org