[jira] [Updated] (YUNIKORN-296) cleanup documents from all but release repo
[ https://issues.apache.org/jira/browse/YUNIKORN-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg updated YUNIKORN-296: --- Target Version: 0.10 (was: 0.9) > cleanup documents from all but release repo > --- > > Key: YUNIKORN-296 > URL: https://issues.apache.org/jira/browse/YUNIKORN-296 > Project: Apache YuniKorn > Issue Type: Task > Components: documentation >Reporter: Wilfred Spiegelenburg >Assignee: Weiwei Yang >Priority: Blocker > > After the move of all the documentation to the website is done the two repos > need to be cleaned up: > * incubator-yunikorn-core > * incubator-yunikorn-k8shim > Following tasks for both repos: > * All content in the docs directory for both repos need to be removed. > * README needs to be updated to point to the website for the docs > Update the SI repo to point to the correct location for the doc -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-350) Implement the revamped ux for yunikorn-web
[ https://issues.apache.org/jira/browse/YUNIKORN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17175194#comment-17175194 ] Sunil G commented on YUNIKORN-350: -- Sorry for a bit late here. [~akhilpb] [~cheersyang] Few comments: # Many of the app status is hardcoded in UI, Could we rely the data which is coming from backend to consider the label name as well. In dashboard.component.ts ? More like defining texts and all labels from a defined JSON or CSV file which can be loaded in UI, so its more easy to change labels and help contents. # fullUrl for site is [https://yunikorn.apache.org/]. protocol scheme ? (app.component.ts) # how is the landing path for yunikorn ui? should that be like cluster/dashboard ? I can raise another JIRA as this is closed or merged already. > Implement the revamped ux for yunikorn-web > -- > > Key: YUNIKORN-350 > URL: https://issues.apache.org/jira/browse/YUNIKORN-350 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-332) Add events for reserved pods
[ https://issues.apache.org/jira/browse/YUNIKORN-332?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17175137#comment-17175137 ] Wilfred Spiegelenburg commented on YUNIKORN-332: This should mirror the internal updates we do in the scheduler when we process the result. All these cases are handled in the scheduling context to keep the internal state in sync. See my comment in the PR. > Add events for reserved pods > > > Key: YUNIKORN-332 > URL: https://issues.apache.org/jira/browse/YUNIKORN-332 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: core - scheduler, shim - kubernetes >Reporter: Adam Antal >Assignee: Adam Antal >Priority: Critical > Labels: pull-request-available > > Pod Event > - When a pod gets reserved to some node, we need to publish the event to the > pod and let user know this pod reserved a spot. > Node Event > - When a node is reserved by a pod, we need to publish an event to node to > let user know the node is reserved by some pod. > - When the pod is unreserved from the node, we also need to publish another > event -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-363) Document REST API ws/v1/config
[ https://issues.apache.org/jira/browse/YUNIKORN-363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang updated YUNIKORN-363: - Summary: Document REST API ws/v1/config (was: Document REST API ws/v1/configs) > Document REST API ws/v1/config > -- > > Key: YUNIKORN-363 > URL: https://issues.apache.org/jira/browse/YUNIKORN-363 > Project: Apache YuniKorn > Issue Type: Improvement > Components: documentation >Reporter: Weiwei Yang >Assignee: Wilfred Spiegelenburg >Priority: Major > > YUNIKORN-273 has introduced a new API to dump scheduler configs, we need to > doc this API. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-363) Document REST API ws/v1/configs
Weiwei Yang created YUNIKORN-363: Summary: Document REST API ws/v1/configs Key: YUNIKORN-363 URL: https://issues.apache.org/jira/browse/YUNIKORN-363 Project: Apache YuniKorn Issue Type: Improvement Components: documentation Reporter: Weiwei Yang Assignee: Wilfred Spiegelenburg YUNIKORN-273 has introduced a new API to dump scheduler configs, we need to doc this API. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-354) Update YK base docker images to UBI
[ https://issues.apache.org/jira/browse/YUNIKORN-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17175120#comment-17175120 ] Wilfred Spiegelenburg commented on YUNIKORN-354: We do not need an image with go installed to run yunikorn. I did not realise that we did use one. It is not needed. The executable that is generated is fully self contained without the need for any extra libraries etc. We need to pick an image that has the smallest number of dependencies and go is certainly not one of them. > Update YK base docker images to UBI > --- > > Key: YUNIKORN-354 > URL: https://issues.apache.org/jira/browse/YUNIKORN-354 > Project: Apache YuniKorn > Issue Type: Task >Reporter: Adam Antal >Assignee: Adam Antal >Priority: Major > Labels: pull-request-available > > In order to YuniKorn run smoothly on OpenShift we should update the base > image to a > [UBI|https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image] > one. This has some further advantages as described in the article. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-24) UT compatibility issue with GO 1.13.x
[
https://issues.apache.org/jira/browse/YUNIKORN-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Weiwei Yang updated YUNIKORN-24:
Priority: Blocker (was: Major)
> UT compatibility issue with GO 1.13.x
> -
>
> Key: YUNIKORN-24
> URL: https://issues.apache.org/jira/browse/YUNIKORN-24
> Project: Apache YuniKorn
> Issue Type: Test
> Components: test - unit
>Reporter: Wilfred Spiegelenburg
>Priority: Blocker
>
> UT starts to fail on flag after upgrade GO to 1.13.x.
> This seems to be caused by us relying on undefined behaviour and fixes in the
> go language.
> Calling {{flag.Parse()}} in an init is considered an incorrect behaviour.
> This is part of the 1.13 release notes:
> [https://tip.golang.org/doc/go1.13#testing]
> We currently call {{flag.Parse()}} in the init of the {{SchedulerConf}} which
> we need to change.
> * not to use {{init()}} functions, the cost of convenience is some
> un-expected behaviors like this.
> * remove these init functions and replace them with {{sync.once}}
> {{init()}} functions could be problematic. However it is simpler than having
> to check in each location that the package is initialised. Using
> {{sync.once}} could add overhead or wrapping which we do not need. I think we
> need to look at a combination of the two: {{init()}} when we know it is
> package local initialisation only. If we have interaction with other packages
> or optional initialisation use the {{sync.once}}
> This {{flag.Parse()}} is a case of interacting with multiple packages, I
> don't think we will have many more of these cases.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-349) Remove installCRD option during helm install for e2e test
[ https://issues.apache.org/jira/browse/YUNIKORN-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang resolved YUNIKORN-349. -- Fix Version/s: 0.10 Resolution: Fixed > Remove installCRD option during helm install for e2e test > - > > Key: YUNIKORN-349 > URL: https://issues.apache.org/jira/browse/YUNIKORN-349 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: test - e2e >Reporter: Weiwei Yang >Assignee: Ting Yao,Huang >Priority: Major > Labels: pull-request-available > Fix For: 0.10 > > > Since this option has been removed by YUNIKONR-346, the following line can be > also removed: > https://github.com/apache/incubator-yunikorn-k8shim/blob/657c62c92687614bf4f089cfaff6b7f5a0db9ad8/scripts/run-e2e-tests.sh#L111 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-356) Add e2e tests for state aware app scheduling
[ https://issues.apache.org/jira/browse/YUNIKORN-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang resolved YUNIKORN-356. -- Fix Version/s: 0.10 Resolution: Fixed > Add e2e tests for state aware app scheduling > > > Key: YUNIKORN-356 > URL: https://issues.apache.org/jira/browse/YUNIKORN-356 > Project: Apache YuniKorn > Issue Type: Test > Components: test - e2e >Reporter: Ayub Pathan >Assignee: Ayub Pathan >Priority: Critical > Labels: pull-request-available > Fix For: 0.10 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-350) Implement the revamped ux for yunikorn-web
[ https://issues.apache.org/jira/browse/YUNIKORN-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Akhil PB resolved YUNIKORN-350. --- Resolution: Fixed > Implement the revamped ux for yunikorn-web > -- > > Key: YUNIKORN-350 > URL: https://issues.apache.org/jira/browse/YUNIKORN-350 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Akhil PB >Assignee: Akhil PB >Priority: Major > Labels: pull-request-available > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-362) Support for "state" query param filter
[ https://issues.apache.org/jira/browse/YUNIKORN-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174949#comment-17174949 ] Weiwei Yang commented on YUNIKORN-362: -- Sounds good to add query parameters for both of these 2. thanks [~maniraj...@gmail.com]. > Support for "state" query param filter > -- > > Key: YUNIKORN-362 > URL: https://issues.apache.org/jira/browse/YUNIKORN-362 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Manikandan R >Assignee: Manikandan R >Priority: Major > > Support "state" query param filter for the following handlers: > > 1. /ws/v1/apps > Filter apps based on application "state". Also it should be based on allowed > states. > 2. /ws/v1/queues > Filter queues based on queue "status". Also it should be based on allowed > status. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-360) Support for "partition" query param filter
[ https://issues.apache.org/jira/browse/YUNIKORN-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang resolved YUNIKORN-360. -- Resolution: Won't Do hi [~maniraj...@gmail.com] This might be a good one for future work. Let's work on the rest of APIs first. > Support for "partition" query param filter > -- > > Key: YUNIKORN-360 > URL: https://issues.apache.org/jira/browse/YUNIKORN-360 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Manikandan R >Assignee: Manikandan R >Priority: Major > > Support "partition" query param filter for the following handlers: > 1. /ws/v1/queues > Filter queues based on "partition" query param. > 2. /ws/v1/clusters > Filter partitions based on "partition" query param. > 3. /ws/v1/apps > Filter apps based on "partition" query param. > 4. /ws/v1/nodes > Filter Nodes based on "partition" query param. > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-361) Support for "node" query param filter
[ https://issues.apache.org/jira/browse/YUNIKORN-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174944#comment-17174944 ] Weiwei Yang commented on YUNIKORN-361: -- Currently, I think it is good enough if we can add the query param "node" for "/ws/v1/nodes". > Support for "node" query param filter > - > > Key: YUNIKORN-361 > URL: https://issues.apache.org/jira/browse/YUNIKORN-361 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Manikandan R >Assignee: Manikandan R >Priority: Major > > Support "node" query param filter for the following handlers: > 1. /ws/v1/nodes > Filter Nodes based on "node" query param. > 2. /ws/v1/apps > Filter apps based on "node" query param. Actually filter would be applied > using Allocation info. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-359) Support for "queue" query param filter
[ https://issues.apache.org/jira/browse/YUNIKORN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174943#comment-17174943 ] Weiwei Yang commented on YUNIKORN-359: -- Thanks [~maniraj...@gmail.com] for creating this. I do think we need to add queue query parameter for "/ws/v1/queues" But I do not think it is necessary to add this for "/ws/v1/nodes", at least for now I do not see any use case for this. Can we use this JIRA to track item #1? Thanks > Support for "queue" query param filter > -- > > Key: YUNIKORN-359 > URL: https://issues.apache.org/jira/browse/YUNIKORN-359 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Manikandan R >Assignee: Manikandan R >Priority: Major > > Support "queue" query param filter to the following handlers: > > 1. /ws/v1/queues > Return only queue info whose name exactly matches with "queue" query param > 2. /ws/v1/nodes > As of now, Each Node Info has all allocations made on that Node. With this > change, it returns only Node info of Nodes whose allocation queue name > exactly matches with "queue" query param. In effect, filter happens on > allocations. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-338) Change order in the sidebar
[ https://issues.apache.org/jira/browse/YUNIKORN-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Weiwei Yang resolved YUNIKORN-338. -- Fix Version/s: 0.9 Resolution: Fixed > Change order in the sidebar > --- > > Key: YUNIKORN-338 > URL: https://issues.apache.org/jira/browse/YUNIKORN-338 > Project: Apache YuniKorn > Issue Type: Task > Components: website >Reporter: Adam Antal >Assignee: Adam Antal >Priority: Major > Labels: pull-request-available > Fix For: 0.9 > > > Remaining item from > [site/#10|https://github.com/apache/incubator-yunikorn-site/pull/10]. Let's > change the order of the sections in the sidebar in the YK website. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-112) Fix ASF release issues
[ https://issues.apache.org/jira/browse/YUNIKORN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174938#comment-17174938 ] Weiwei Yang commented on YUNIKORN-112: -- Awesome, thanks for getting all these things sorted out. Thanks for everyone's contribution, [~wilfreds], [~kmarton], [~trots], [~Huang Ting Yao]! > Fix ASF release issues > -- > > Key: YUNIKORN-112 > URL: https://issues.apache.org/jira/browse/YUNIKORN-112 > Project: Apache YuniKorn > Issue Type: Task > Components: release >Reporter: Weiwei Yang >Assignee: Wilfred Spiegelenburg >Priority: Blocker > Fix For: 0.9 > > > Felix gives us some feedback on our first release, we should make sure they > are fixed in the next release, items include: > - incubating in name > - signature and hash fine > - DISCLAIMER is ok - as above > - LICENSE and NOTICE are fine > - Ok with binary files - see note below > - See note below on ASF headers > - didn't compile from source > 1. SHOULD: instead of a personal directory, release SHOULD be staged on > [https://dist.apache.org/repos/dist/dev/incubator/yunikorn]. > [https://incubator.apache.org/guides/releasemanagement.html#podling_constraints] > this include the signing KEYS file that should be kept as a project KEYS file > instead of a personal one/location > 2. it is a bit strange that you have 5 LICENSE files, you can exclude the one > in subdirectories when you build the source tarball? > 3. might want to check the license for the image files: png, jpg - where are > they from? > 4. SHOULD: a large number of files should also have ASF headers, eg. .mod, > .yaml, .md, .go > 5. nice to have: more details on go setup for dev environment (maybe just a > quick link), go setup info without GoLand IDE. It could be helpful to know > more on how to build (is this the build step? > [https://github.com/apache/incubator-yunikorn-core/blob/master/docs/developer-guide.md#core-component-build]) > 6. SHOULD: put Apache Incubator logo on the > websitehttps://[incubator.apache.org/guides/press-kit.html|http://incubator.apache.org/guides/press-kit.html] > [http://yunikorn.apache.org/] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-362) Support for "state" query param filter
Manikandan R created YUNIKORN-362: - Summary: Support for "state" query param filter Key: YUNIKORN-362 URL: https://issues.apache.org/jira/browse/YUNIKORN-362 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Manikandan R Support "state" query param filter for the following handlers: 1. /ws/v1/apps Filter apps based on application "state". Also it should be based on allowed states. 2. /ws/v1/queues Filter queues based on queue "status". Also it should be based on allowed status. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-362) Support for "state" query param filter
[ https://issues.apache.org/jira/browse/YUNIKORN-362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R reassigned YUNIKORN-362: - Assignee: Manikandan R > Support for "state" query param filter > -- > > Key: YUNIKORN-362 > URL: https://issues.apache.org/jira/browse/YUNIKORN-362 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Manikandan R >Assignee: Manikandan R >Priority: Major > > Support "state" query param filter for the following handlers: > > 1. /ws/v1/apps > Filter apps based on application "state". Also it should be based on allowed > states. > 2. /ws/v1/queues > Filter queues based on queue "status". Also it should be based on allowed > status. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-361) Support for "node" query param filter
Manikandan R created YUNIKORN-361: - Summary: Support for "node" query param filter Key: YUNIKORN-361 URL: https://issues.apache.org/jira/browse/YUNIKORN-361 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Manikandan R Support "node" query param filter for the following handlers: 1. /ws/v1/nodes Filter Nodes based on "node" query param. 2. /ws/v1/apps Filter apps based on "node" query param. Actually filter would be applied using Allocation info. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-361) Support for "node" query param filter
[ https://issues.apache.org/jira/browse/YUNIKORN-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R reassigned YUNIKORN-361: - Assignee: Manikandan R > Support for "node" query param filter > - > > Key: YUNIKORN-361 > URL: https://issues.apache.org/jira/browse/YUNIKORN-361 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Manikandan R >Assignee: Manikandan R >Priority: Major > > Support "node" query param filter for the following handlers: > 1. /ws/v1/nodes > Filter Nodes based on "node" query param. > 2. /ws/v1/apps > Filter apps based on "node" query param. Actually filter would be applied > using Allocation info. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-355) Update latest helm chart version on helm hub
[ https://issues.apache.org/jira/browse/YUNIKORN-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174448#comment-17174448 ] Weiwei Yang commented on YUNIKORN-355: -- It makes sense to only publish the released versions of helm charts to the helm hub. But we still need to publish the latest version of helm charts somewhere because our e2e test is consuming it. Maybe we can publish onto our release repo, as a tarball. We can think about how to automate this with a proper github workflow action. > Update latest helm chart version on helm hub > > > Key: YUNIKORN-355 > URL: https://issues.apache.org/jira/browse/YUNIKORN-355 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Weiwei Yang >Assignee: Kinga Marton >Priority: Major > > Up to latest version -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-360) Support for "partition" query param filter
Manikandan R created YUNIKORN-360: - Summary: Support for "partition" query param filter Key: YUNIKORN-360 URL: https://issues.apache.org/jira/browse/YUNIKORN-360 Project: Apache YuniKorn Issue Type: Sub-task Reporter: Manikandan R Support "partition" query param filter for the following handlers: 1. /ws/v1/queues Filter queues based on "partition" query param. 2. /ws/v1/clusters Filter partitions based on "partition" query param. 3. /ws/v1/apps Filter apps based on "partition" query param. 4. /ws/v1/nodes Filter Nodes based on "partition" query param. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-360) Support for "partition" query param filter
[ https://issues.apache.org/jira/browse/YUNIKORN-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R reassigned YUNIKORN-360: - Assignee: Manikandan R > Support for "partition" query param filter > -- > > Key: YUNIKORN-360 > URL: https://issues.apache.org/jira/browse/YUNIKORN-360 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Manikandan R >Assignee: Manikandan R >Priority: Major > > Support "partition" query param filter for the following handlers: > 1. /ws/v1/queues > Filter queues based on "partition" query param. > 2. /ws/v1/clusters > Filter partitions based on "partition" query param. > 3. /ws/v1/apps > Filter apps based on "partition" query param. > 4. /ws/v1/nodes > Filter Nodes based on "partition" query param. > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-359) Support for "queue" query param filter
[ https://issues.apache.org/jira/browse/YUNIKORN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174442#comment-17174442 ] Manikandan R commented on YUNIKORN-359: --- [~wilfreds] [~cheersyang] Please validate. > Support for "queue" query param filter > -- > > Key: YUNIKORN-359 > URL: https://issues.apache.org/jira/browse/YUNIKORN-359 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Manikandan R >Assignee: Manikandan R >Priority: Major > > Support "queue" query param filter to the following handlers: > > 1. /ws/v1/queues > Return only queue info whose name exactly matches with "queue" query param > 2. /ws/v1/nodes > As of now, Each Node Info has all allocations made on that Node. With this > change, it returns only Node info of Nodes whose allocation queue name > exactly matches with "queue" query param. In effect, filter happens on > allocations. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-359) Support for "queue" query param filter
[ https://issues.apache.org/jira/browse/YUNIKORN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R updated YUNIKORN-359: -- Parent: YUNIKORN-283 Issue Type: Sub-task (was: Task) > Support for "queue" query param filter > -- > > Key: YUNIKORN-359 > URL: https://issues.apache.org/jira/browse/YUNIKORN-359 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Manikandan R >Priority: Major > > Support "queue" query param filter to the following handlers: > > 1. /ws/v1/queues > Return only queue info whose name exactly matches with "queue" query param > 2. /ws/v1/nodes > As of now, Each Node Info has all allocations made on that Node. With this > change, it returns only Node info of Nodes whose allocation queue name > exactly matches with "queue" query param. In effect, filter happens on > allocations. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-359) Support for "queue" query param filter
[ https://issues.apache.org/jira/browse/YUNIKORN-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manikandan R reassigned YUNIKORN-359: - Assignee: Manikandan R > Support for "queue" query param filter > -- > > Key: YUNIKORN-359 > URL: https://issues.apache.org/jira/browse/YUNIKORN-359 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Manikandan R >Assignee: Manikandan R >Priority: Major > > Support "queue" query param filter to the following handlers: > > 1. /ws/v1/queues > Return only queue info whose name exactly matches with "queue" query param > 2. /ws/v1/nodes > As of now, Each Node Info has all allocations made on that Node. With this > change, it returns only Node info of Nodes whose allocation queue name > exactly matches with "queue" query param. In effect, filter happens on > allocations. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-359) Support for "queue" query param filter
Manikandan R created YUNIKORN-359: - Summary: Support for "queue" query param filter Key: YUNIKORN-359 URL: https://issues.apache.org/jira/browse/YUNIKORN-359 Project: Apache YuniKorn Issue Type: Task Reporter: Manikandan R Support "queue" query param filter to the following handlers: 1. /ws/v1/queues Return only queue info whose name exactly matches with "queue" query param 2. /ws/v1/nodes As of now, Each Node Info has all allocations made on that Node. With this change, it returns only Node info of Nodes whose allocation queue name exactly matches with "queue" query param. In effect, filter happens on allocations. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-338) Change order in the sidebar
[ https://issues.apache.org/jira/browse/YUNIKORN-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YUNIKORN-338: Labels: pull-request-available (was: ) > Change order in the sidebar > --- > > Key: YUNIKORN-338 > URL: https://issues.apache.org/jira/browse/YUNIKORN-338 > Project: Apache YuniKorn > Issue Type: Task > Components: website >Reporter: Adam Antal >Assignee: Adam Antal >Priority: Major > Labels: pull-request-available > > Remaining item from > [site/#10|https://github.com/apache/incubator-yunikorn-site/pull/10]. Let's > change the order of the sections in the sidebar in the YK website. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-130) add condensed build instructions to release
[ https://issues.apache.org/jira/browse/YUNIKORN-130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YUNIKORN-130. Fix Version/s: 0.9 Resolution: Fixed Left the instructions as a MD file instead of converting them to a txt file. Most OS'es and tools can display the MD file. Changes committed: https://github.com/apache/incubator-yunikorn-release/commit/c6255e414a18cfcbb02f967894e244399a7e2a54 > add condensed build instructions to release > --- > > Key: YUNIKORN-130 > URL: https://issues.apache.org/jira/browse/YUNIKORN-130 > Project: Apache YuniKorn > Issue Type: Sub-task >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Minor > Fix For: 0.9 > > > The current release information only shows what to run to get the images > build from a ready system. It does not explain how and what to install > (command line, not IDE) to get the code to compile from scratch. > We need to add a limited set of instructions or scripts to install a build > system from nothing. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-112) Fix ASF release issues
[ https://issues.apache.org/jira/browse/YUNIKORN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YUNIKORN-112. Fix Version/s: 0.9 Resolution: Fixed Add missing instructions for tagging a release and updating mod files. Changes are spread over README and procedure documentation. Move to DISCLAIMER (not WIP anymore) Add .gitignore to prevent staging directory from being committed. files committed: https://github.com/apache/incubator-yunikorn-release/commit/c782ae04afa1cbea1092427f63b6c92856e455d9 All subtasks closed marking as fixed > Fix ASF release issues > -- > > Key: YUNIKORN-112 > URL: https://issues.apache.org/jira/browse/YUNIKORN-112 > Project: Apache YuniKorn > Issue Type: Task > Components: release >Reporter: Weiwei Yang >Assignee: Wilfred Spiegelenburg >Priority: Blocker > Fix For: 0.9 > > > Felix gives us some feedback on our first release, we should make sure they > are fixed in the next release, items include: > - incubating in name > - signature and hash fine > - DISCLAIMER is ok - as above > - LICENSE and NOTICE are fine > - Ok with binary files - see note below > - See note below on ASF headers > - didn't compile from source > 1. SHOULD: instead of a personal directory, release SHOULD be staged on > [https://dist.apache.org/repos/dist/dev/incubator/yunikorn]. > [https://incubator.apache.org/guides/releasemanagement.html#podling_constraints] > this include the signing KEYS file that should be kept as a project KEYS file > instead of a personal one/location > 2. it is a bit strange that you have 5 LICENSE files, you can exclude the one > in subdirectories when you build the source tarball? > 3. might want to check the license for the image files: png, jpg - where are > they from? > 4. SHOULD: a large number of files should also have ASF headers, eg. .mod, > .yaml, .md, .go > 5. nice to have: more details on go setup for dev environment (maybe just a > quick link), go setup info without GoLand IDE. It could be helpful to know > more on how to build (is this the build step? > [https://github.com/apache/incubator-yunikorn-core/blob/master/docs/developer-guide.md#core-component-build]) > 6. SHOULD: put Apache Incubator logo on the > websitehttps://[incubator.apache.org/guides/press-kit.html|http://incubator.apache.org/guides/press-kit.html] > [http://yunikorn.apache.org/] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-289) local build uses wrong sha
[
https://issues.apache.org/jira/browse/YUNIKORN-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wilfred Spiegelenburg resolved YUNIKORN-289.
Fix Version/s: 0.9
Resolution: Fixed
Multiple changes to fix the issue(s) found while investigating the sha issue:
- replace shell script with Makefile
- pull commit sha while building source tarball
- make version push consistent
- add admission controller version update
https://github.com/apache/incubator-yunikorn-release/commit/b87f514a46923297221c7b3100c767dd67ba03ee
> local build uses wrong sha
> --
>
> Key: YUNIKORN-289
> URL: https://issues.apache.org/jira/browse/YUNIKORN-289
> Project: Apache YuniKorn
> Issue Type: Sub-task
> Components: release
>Reporter: Wilfred Spiegelenburg
>Assignee: Wilfred Spiegelenburg
>Priority: Major
> Fix For: 0.9
>
>
> When a {{replace}} is in the go.mod file the build does not handle is nicely
> and the SHA that we retrieve for the docker build tag shows strange info:
> {code}
> go list -m "github.com/apache/incubator-yunikorn-core" | cut -d "-" -f6
> 4ea58b502d38 => ../incubator
> {code}
> We only want the first part of the info.
> The second thing we need to be careful with is the tag: if the semver tag
> changes to include any dashes we will be generating the wrong info.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Comment Edited] (YUNIKORN-355) Update latest helm chart version on helm hub
[ https://issues.apache.org/jira/browse/YUNIKORN-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174291#comment-17174291 ] Kinga Marton edited comment on YUNIKORN-355 at 8/10/20, 12:39 PM: -- [~wwei] I don't think it is a good idea to publish the latest charts on Helm hub. It is changing frequently and even if it is just one command and one commit, it is annoying that we have to perform it manually each time something is changed. The idea for having the latest charts was to make our work during development/testing easier, but if it means that we should change the package each time something is changed I don't think it worth it. Also we will have troubles with the versioning as well, since helm will accept only 3 difit version, so right now we are using 0.9.0 version for the latest version, what is wrong and may cause a lot of misunderstandings. My suggestion is to publish only the charts for the released versions and remove the latest one. During development we can use the charts from the release repository. [~wwei], [~wilfreds], [~adam.antal], [~rreti] what do you think? was (Author: kmarton): [~wwei] I don't think it is a good idea to publish the latest charts on Helm hub. It is changing frequently and even if it is just one command and one commit, it is annoying that we have to perform it manually each time something is changed. The idea for having the latest charts was to make our work during development/testing easier, but if it means that we should change the package each time something is changed I think it not worth it. Also we will have troubles with the versioning as well, since helm will accept only 3 difit version, so right now we are using 0.9.0 version for the latest version, what is wrong and may cause a lot of misunderstandings. My suggestion is to publish only the charts for the released versions and remove the latest one. During development we can use the charts from the release repository. [~wwei], [~wilfreds], [~adam.antal], [~rreti] what do you think? > Update latest helm chart version on helm hub > > > Key: YUNIKORN-355 > URL: https://issues.apache.org/jira/browse/YUNIKORN-355 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Weiwei Yang >Assignee: Kinga Marton >Priority: Major > > Up to latest version -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-355) Update latest helm chart version on helm hub
[ https://issues.apache.org/jira/browse/YUNIKORN-355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174291#comment-17174291 ] Kinga Marton commented on YUNIKORN-355: --- [~wwei] I don't think it is a good idea to publish the latest charts on Helm hub. It is changing frequently and even if it is just one command and one commit, it is annoying that we have to perform it manually each time something is changed. The idea for having the latest charts was to make our work during development/testing easier, but if it means that we should change the package each time something is changed I think it not worth it. Also we will have troubles with the versioning as well, since helm will accept only 3 difit version, so right now we are using 0.9.0 version for the latest version, what is wrong and may cause a lot of misunderstandings. My suggestion is to publish only the charts for the released versions and remove the latest one. During development we can use the charts from the release repository. [~wwei], [~wilfreds], [~adam.antal], [~rreti] what do you think? > Update latest helm chart version on helm hub > > > Key: YUNIKORN-355 > URL: https://issues.apache.org/jira/browse/YUNIKORN-355 > Project: Apache YuniKorn > Issue Type: Sub-task > Components: release >Reporter: Weiwei Yang >Assignee: Kinga Marton >Priority: Major > > Up to latest version -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Resolved] (YUNIKORN-358) tag release 0.9.0 and update go mod files
[ https://issues.apache.org/jira/browse/YUNIKORN-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg resolved YUNIKORN-358. Fix Version/s: 0.9 Resolution: Fixed changes made to all repos v0.9.0 has been tagged and mod files updated > tag release 0.9.0 and update go mod files > - > > Key: YUNIKORN-358 > URL: https://issues.apache.org/jira/browse/YUNIKORN-358 > Project: Apache YuniKorn > Issue Type: Task > Components: core - common, shim - kubernetes >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Blocker > Fix For: 0.9 > > > After tagging for the 0.9.0 release the dependencies for the core and shim > need to be updated to point to the new tag. > Order: > * tag si and web > * tag core and go mod update (si ref) > * tag shim and go mod update (core and si ref) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-338) Change order in the sidebar
[ https://issues.apache.org/jira/browse/YUNIKORN-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174277#comment-17174277 ] Wilfred Spiegelenburg commented on YUNIKORN-338: We have time to update the docs. Side bars must be versioned anyway. We have to change the side bar for 0.9.0 from 0.8.0 as there are docs in the new version that we do not have in the older version. We also will move more docs into the next release. So yes we can and should do this. > Change order in the sidebar > --- > > Key: YUNIKORN-338 > URL: https://issues.apache.org/jira/browse/YUNIKORN-338 > Project: Apache YuniKorn > Issue Type: Task > Components: website >Reporter: Adam Antal >Assignee: Adam Antal >Priority: Major > > Remaining item from > [site/#10|https://github.com/apache/incubator-yunikorn-site/pull/10]. Let's > change the order of the sections in the sidebar in the YK website. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Comment Edited] (YUNIKORN-338) Change order in the sidebar
[ https://issues.apache.org/jira/browse/YUNIKORN-338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17170190#comment-17170190 ] Wilfred Spiegelenburg edited comment on YUNIKORN-338 at 8/10/20, 12:20 PM: --- Thanks [~adam.antal]. Before you make the change, let's get some feedback from [~wilfreds] first. was (Author: wwei): Thanks [~adam.antal]. Before you make the change, let's get some feedback from [~wilfred] first. > Change order in the sidebar > --- > > Key: YUNIKORN-338 > URL: https://issues.apache.org/jira/browse/YUNIKORN-338 > Project: Apache YuniKorn > Issue Type: Task > Components: website >Reporter: Adam Antal >Assignee: Adam Antal >Priority: Major > > Remaining item from > [site/#10|https://github.com/apache/incubator-yunikorn-site/pull/10]. Let's > change the order of the sections in the sidebar in the YK website. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Comment Edited] (YUNIKORN-112) Fix ASF release issues
[
https://issues.apache.org/jira/browse/YUNIKORN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174206#comment-17174206
]
Wilfred Spiegelenburg edited comment on YUNIKORN-112 at 8/10/20, 12:04 PM:
---
Updates that do not fit under the rest of the jiras:
- fix issues in the readme and release instructions on how we release
- add a {{.gitignore}} file that excludes the staging directory from commits
- moved from DISCLAIMER-WIP to DISCLAIMER
- LICENSE file turned out to be empty and in the wrong location (introduced in
YUNIKORN-127)
- remove landmark directory from the released artefacts
was (Author: wifreds):
Updates that do not fit under the rest of the jiras:
- fix issues in the readme and release instructions on how we release
- add a {{.gitignore}} file that excludes the staging directory from commits
- moved from DISCLAIMER-WIP to DISCLAIMER
- NOTICE file turned out to be empty and in the wrong location (introduced in
YUNIKORN-127)
- remove landmark directory from the released artefacts
> Fix ASF release issues
> --
>
> Key: YUNIKORN-112
> URL: https://issues.apache.org/jira/browse/YUNIKORN-112
> Project: Apache YuniKorn
> Issue Type: Task
> Components: release
>Reporter: Weiwei Yang
>Assignee: Wilfred Spiegelenburg
>Priority: Blocker
>
> Felix gives us some feedback on our first release, we should make sure they
> are fixed in the next release, items include:
> - incubating in name
> - signature and hash fine
> - DISCLAIMER is ok - as above
> - LICENSE and NOTICE are fine
> - Ok with binary files - see note below
> - See note below on ASF headers
> - didn't compile from source
> 1. SHOULD: instead of a personal directory, release SHOULD be staged on
> [https://dist.apache.org/repos/dist/dev/incubator/yunikorn].
> [https://incubator.apache.org/guides/releasemanagement.html#podling_constraints]
> this include the signing KEYS file that should be kept as a project KEYS file
> instead of a personal one/location
> 2. it is a bit strange that you have 5 LICENSE files, you can exclude the one
> in subdirectories when you build the source tarball?
> 3. might want to check the license for the image files: png, jpg - where are
> they from?
> 4. SHOULD: a large number of files should also have ASF headers, eg. .mod,
> .yaml, .md, .go
> 5. nice to have: more details on go setup for dev environment (maybe just a
> quick link), go setup info without GoLand IDE. It could be helpful to know
> more on how to build (is this the build step?
> [https://github.com/apache/incubator-yunikorn-core/blob/master/docs/developer-guide.md#core-component-build])
> 6. SHOULD: put Apache Incubator logo on the
> websitehttps://[incubator.apache.org/guides/press-kit.html|http://incubator.apache.org/guides/press-kit.html]
> [http://yunikorn.apache.org/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-358) tag release 0.9.0 and update go mod files
[ https://issues.apache.org/jira/browse/YUNIKORN-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174208#comment-17174208 ] Wilfred Spiegelenburg commented on YUNIKORN-358: shim tagged and go mod changes pushed: https://github.com/apache/incubator-yunikorn-k8shim/commit/b1a1f173a02e4e872fa3535112e514a8816bdd70 > tag release 0.9.0 and update go mod files > - > > Key: YUNIKORN-358 > URL: https://issues.apache.org/jira/browse/YUNIKORN-358 > Project: Apache YuniKorn > Issue Type: Task > Components: core - common, shim - kubernetes >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Blocker > > After tagging for the 0.9.0 release the dependencies for the core and shim > need to be updated to point to the new tag. > Order: > * tag si and web > * tag core and go mod update (si ref) > * tag shim and go mod update (core and si ref) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-112) Fix ASF release issues
[
https://issues.apache.org/jira/browse/YUNIKORN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174206#comment-17174206
]
Wilfred Spiegelenburg commented on YUNIKORN-112:
Updates that do not fit under the rest of the jiras:
- fix issues in the readme and release instructions on how we release
- add a {{.gitignore}} file that excludes the staging directory from commits
- moved from DISCLAIMER-WIP to DISCLAIMER
- NOTICE file turned out to be empty and in the wrong location (introduced in
YUNIKORN-127)
- remove landmark directory from the released artefacts
> Fix ASF release issues
> --
>
> Key: YUNIKORN-112
> URL: https://issues.apache.org/jira/browse/YUNIKORN-112
> Project: Apache YuniKorn
> Issue Type: Task
> Components: release
>Reporter: Weiwei Yang
>Assignee: Wilfred Spiegelenburg
>Priority: Blocker
>
> Felix gives us some feedback on our first release, we should make sure they
> are fixed in the next release, items include:
> - incubating in name
> - signature and hash fine
> - DISCLAIMER is ok - as above
> - LICENSE and NOTICE are fine
> - Ok with binary files - see note below
> - See note below on ASF headers
> - didn't compile from source
> 1. SHOULD: instead of a personal directory, release SHOULD be staged on
> [https://dist.apache.org/repos/dist/dev/incubator/yunikorn].
> [https://incubator.apache.org/guides/releasemanagement.html#podling_constraints]
> this include the signing KEYS file that should be kept as a project KEYS file
> instead of a personal one/location
> 2. it is a bit strange that you have 5 LICENSE files, you can exclude the one
> in subdirectories when you build the source tarball?
> 3. might want to check the license for the image files: png, jpg - where are
> they from?
> 4. SHOULD: a large number of files should also have ASF headers, eg. .mod,
> .yaml, .md, .go
> 5. nice to have: more details on go setup for dev environment (maybe just a
> quick link), go setup info without GoLand IDE. It could be helpful to know
> more on how to build (is this the build step?
> [https://github.com/apache/incubator-yunikorn-core/blob/master/docs/developer-guide.md#core-component-build])
> 6. SHOULD: put Apache Incubator logo on the
> websitehttps://[incubator.apache.org/guides/press-kit.html|http://incubator.apache.org/guides/press-kit.html]
> [http://yunikorn.apache.org/]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org
For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-358) tag release 0.9.0 and update go mod files
[ https://issues.apache.org/jira/browse/YUNIKORN-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174200#comment-17174200 ] Wilfred Spiegelenburg commented on YUNIKORN-358: Core tagged and go mod changes pushed: https://github.com/apache/incubator-yunikorn-core/commit/e119e4578a96b1c04286ea4f79015dbea5107360 > tag release 0.9.0 and update go mod files > - > > Key: YUNIKORN-358 > URL: https://issues.apache.org/jira/browse/YUNIKORN-358 > Project: Apache YuniKorn > Issue Type: Task > Components: core - common, shim - kubernetes >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Blocker > > After tagging for the 0.9.0 release the dependencies for the core and shim > need to be updated to point to the new tag. > Order: > * tag si and web > * tag core and go mod update (si ref) > * tag shim and go mod update (core and si ref) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-358) tag release 0.9.0 and update go mod files
[ https://issues.apache.org/jira/browse/YUNIKORN-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174191#comment-17174191 ] Wilfred Spiegelenburg commented on YUNIKORN-358: SI and web have been tagged > tag release 0.9.0 and update go mod files > - > > Key: YUNIKORN-358 > URL: https://issues.apache.org/jira/browse/YUNIKORN-358 > Project: Apache YuniKorn > Issue Type: Task > Components: core - common, shim - kubernetes >Reporter: Wilfred Spiegelenburg >Assignee: Wilfred Spiegelenburg >Priority: Blocker > > After tagging for the 0.9.0 release the dependencies for the core and shim > need to be updated to point to the new tag. > Order: > * tag si and web > * tag core and go mod update (si ref) > * tag shim and go mod update (core and si ref) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Created] (YUNIKORN-358) tag release 0.9.0 and update go mod files
Wilfred Spiegelenburg created YUNIKORN-358: -- Summary: tag release 0.9.0 and update go mod files Key: YUNIKORN-358 URL: https://issues.apache.org/jira/browse/YUNIKORN-358 Project: Apache YuniKorn Issue Type: Task Components: core - common, shim - kubernetes Reporter: Wilfred Spiegelenburg Assignee: Wilfred Spiegelenburg After tagging for the 0.9.0 release the dependencies for the core and shim need to be updated to point to the new tag. Order: * tag si and web * tag core and go mod update (si ref) * tag shim and go mod update (core and si ref) -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Assigned] (YUNIKORN-112) Fix ASF release issues
[ https://issues.apache.org/jira/browse/YUNIKORN-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wilfred Spiegelenburg reassigned YUNIKORN-112: -- Assignee: Wilfred Spiegelenburg > Fix ASF release issues > -- > > Key: YUNIKORN-112 > URL: https://issues.apache.org/jira/browse/YUNIKORN-112 > Project: Apache YuniKorn > Issue Type: Task > Components: release >Reporter: Weiwei Yang >Assignee: Wilfred Spiegelenburg >Priority: Blocker > > Felix gives us some feedback on our first release, we should make sure they > are fixed in the next release, items include: > - incubating in name > - signature and hash fine > - DISCLAIMER is ok - as above > - LICENSE and NOTICE are fine > - Ok with binary files - see note below > - See note below on ASF headers > - didn't compile from source > 1. SHOULD: instead of a personal directory, release SHOULD be staged on > [https://dist.apache.org/repos/dist/dev/incubator/yunikorn]. > [https://incubator.apache.org/guides/releasemanagement.html#podling_constraints] > this include the signing KEYS file that should be kept as a project KEYS file > instead of a personal one/location > 2. it is a bit strange that you have 5 LICENSE files, you can exclude the one > in subdirectories when you build the source tarball? > 3. might want to check the license for the image files: png, jpg - where are > they from? > 4. SHOULD: a large number of files should also have ASF headers, eg. .mod, > .yaml, .md, .go > 5. nice to have: more details on go setup for dev environment (maybe just a > quick link), go setup info without GoLand IDE. It could be helpful to know > more on how to build (is this the build step? > [https://github.com/apache/incubator-yunikorn-core/blob/master/docs/developer-guide.md#core-component-build]) > 6. SHOULD: put Apache Incubator logo on the > websitehttps://[incubator.apache.org/guides/press-kit.html|http://incubator.apache.org/guides/press-kit.html] > [http://yunikorn.apache.org/] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-354) Update YK base docker images to UBI
[ https://issues.apache.org/jira/browse/YUNIKORN-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174147#comment-17174147 ] Kinga Marton commented on YUNIKORN-354: --- [~adam.antal], [~wwei] before merging this change it would be good to make sure that it is OK from licensing point of view as well. [~wwei] do you know who should we ask about the legal parts? > Update YK base docker images to UBI > --- > > Key: YUNIKORN-354 > URL: https://issues.apache.org/jira/browse/YUNIKORN-354 > Project: Apache YuniKorn > Issue Type: Task >Reporter: Adam Antal >Assignee: Adam Antal >Priority: Major > Labels: pull-request-available > > In order to YuniKorn run smoothly on OpenShift we should update the base > image to a > [UBI|https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image] > one. This has some further advantages as described in the article. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Commented] (YUNIKORN-354) Update YK base docker images to UBI
[ https://issues.apache.org/jira/browse/YUNIKORN-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17174134#comment-17174134 ] Adam Antal commented on YUNIKORN-354: - Added the simple base image change and tested it locally. Created a list with the remaining items in the PR. > Update YK base docker images to UBI > --- > > Key: YUNIKORN-354 > URL: https://issues.apache.org/jira/browse/YUNIKORN-354 > Project: Apache YuniKorn > Issue Type: Task >Reporter: Adam Antal >Assignee: Adam Antal >Priority: Major > Labels: pull-request-available > > In order to YuniKorn run smoothly on OpenShift we should update the base > image to a > [UBI|https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image] > one. This has some further advantages as described in the article. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
[jira] [Updated] (YUNIKORN-354) Update YK base docker images to UBI
[ https://issues.apache.org/jira/browse/YUNIKORN-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated YUNIKORN-354: Labels: pull-request-available (was: ) > Update YK base docker images to UBI > --- > > Key: YUNIKORN-354 > URL: https://issues.apache.org/jira/browse/YUNIKORN-354 > Project: Apache YuniKorn > Issue Type: Task >Reporter: Adam Antal >Assignee: Adam Antal >Priority: Major > Labels: pull-request-available > > In order to YuniKorn run smoothly on OpenShift we should update the base > image to a > [UBI|https://www.redhat.com/en/blog/introducing-red-hat-universal-base-image] > one. This has some further advantages as described in the article. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: issues-unsubscr...@yunikorn.apache.org For additional commands, e-mail: issues-h...@yunikorn.apache.org
