davidjumani commented on issue #803:
URL:
https://github.com/apache/cloudstack-primate/issues/803#issuecomment-708200313
@andrijapanicsb I think supporting custom disk sizes will require several
backend chagnes since right now it isn't supported
--
andrijapanicsb commented on issue #803:
URL:
https://github.com/apache/cloudstack-primate/issues/803#issuecomment-708198401
It's always easy to see how the old UI works - what offerings are listed
there.
Afaik, this is multidisk template - where you match offering to a data disk
fr
davidjumani edited a comment on issue #803:
URL:
https://github.com/apache/cloudstack-primate/issues/803#issuecomment-708194558
@utchoang listDiskOfferings returns all the disk offerings, but Primate
filters offerings >= 5GB. Need to confirm whether custom disk offerings are
supported for
davidjumani commented on issue #803:
URL:
https://github.com/apache/cloudstack-primate/issues/803#issuecomment-708194558
@utchoang It already filters offerings >= 5GB. Need to confirm whehter
custom disk offerings are supported for datadisk templates or not
@andrijapanicsb
borisstoyanov commented on issue #803:
URL:
https://github.com/apache/cloudstack-primate/issues/803#issuecomment-708191701
I think so @utchoang, @andrijapanicsb @nvazquez can you confirm
cc: @davidjumani
This is an autom
davidjumani commented on pull request #17:
URL:
https://github.com/apache/cloudstack-kubernetes-provider/pull/17#issuecomment-708190591
@onitake Go ahead and merge this so that I can rebase and submit #22
This is an automate
A service account with only access to the listKubernetesCluster and
scaleKubernetesCluster should work.
But to prevent a single API key from being used to mess with all the clusters,
multiple users within the service account, mapping to each account which has a
cluster with autoscaling enabled w
utchoang commented on issue #805:
URL:
https://github.com/apache/cloudstack-primate/issues/805#issuecomment-708150003
@rhtyd There's one problem: This will take away a collapsed menu context.
What do you think?
This is an a
Maybe RBAC this is not a bad idea so it’s possible to grant different
permissions to users or the service user.
Von: Rakesh v
__
Sven Vogel
Lead Cloud Solution Architect
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
s.
Service account best suits the need. We can probably apply some RBAC on the
account if possible
Sent from my iPhone
> On 12-Oct-2020, at 2:19 PM, David Jumani wrote:
>
> Thanks Rakesh.
> Do you think it would be better to have the user provide the API keys or
> create a service account and u
andrijapanicsb opened a new issue #805:
URL: https://github.com/apache/cloudstack-primate/issues/805
For some time now, while testing and having to click around frequently, I've
been very irritated by having to click on Compute, then on Instances (in order
to reach Instances as the first m
blueorangutan commented on pull request #800:
URL:
https://github.com/apache/cloudstack-primate/pull/800#issuecomment-707723642
Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian
:heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/800 (JID-3
blueorangutan commented on pull request #800:
URL:
https://github.com/apache/cloudstack-primate/pull/800#issuecomment-707718967
@davidjumani a Jenkins job has been kicked to build primate packages. I'll
keep you posted as I make progress.
-
davidjumani commented on pull request #800:
URL:
https://github.com/apache/cloudstack-primate/pull/800#issuecomment-707718480
@blueorangutan package
This is an automated message from the Apache Git Service.
To respond to the
davidjumani commented on a change in pull request #800:
URL: https://github.com/apache/cloudstack-primate/pull/800#discussion_r503924846
##
File path: src/views/compute/KubernetesServiceTab.vue
##
@@ -327,14 +327,14 @@ export default {
this.resource.projectid !== '')
blueorangutan commented on pull request #804:
URL:
https://github.com/apache/cloudstack-primate/pull/804#issuecomment-707717014
Packaging result: :heavy_check_mark:centos :heavy_check_mark:debian
:heavy_check_mark:archive.
QA: http://primate-qa.cloudstack.cloud:8080/client/pr/804 (JID-3
blueorangutan commented on pull request #804:
URL:
https://github.com/apache/cloudstack-primate/pull/804#issuecomment-707712634
@davidjumani a Jenkins job has been kicked to build primate packages. I'll
keep you posted as I make progress.
-
davidjumani opened a new pull request #804:
URL: https://github.com/apache/cloudstack-primate/pull/804
- Adding option to copy resource name on avatar click
- Fixing alignment of console icon
### Before :
 {
+
shwstppr commented on a change in pull request #800:
URL: https://github.com/apache/cloudstack-primate/pull/800#discussion_r503880066
##
File path: src/views/compute/KubernetesServiceTab.vue
##
@@ -327,14 +327,14 @@ export default {
this.resource.projectid !== '') {
shwstppr commented on a change in pull request #800:
URL: https://github.com/apache/cloudstack-primate/pull/800#discussion_r503870382
##
File path: src/views/compute/KubernetesServiceTab.vue
##
@@ -327,14 +327,14 @@ export default {
this.resource.projectid !== '') {
Should it possible to grant other users the control about the service user?
__
Sven Vogel
Lead Cloud Solution Architect
EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98
s.vo...@ewerk.com
www.ewerk.com
Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tass
In the release notes for the old CCS we strongly recommended that the user
created a service account or at least a service 'user'. Ultimately it has to be
on the user to control 'who' can do what.
paul.an...@shapeblue.com
www.shapeblue.com
3 London Bridge Street, 3rd floor, News Building, Lon
Thanks Daan. Users within the same account can alter the cluster, so I'm
thinking of a service user within the same account and use the service user's
keys. This will also prevent any mess up if the user provides his keys and then
later regenerates them.
From: Da
That is a good question. Is the user going to be the only user responsible
for messing up the k8 cluster, or will other users be able to as well? For
convenience and if audit is to not lay false balme on a user, I'd say
create a system/service account, if several users can mess up each other
with i
DaanHoogland merged pull request #163:
URL: https://github.com/apache/cloudstack-documentation/pull/163
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
Sounds good. And do you think it would be better to have the user provide the
API keys or create a service account and use its keys?
From: Daan Hoogland
Sent: Monday, October 12, 2020 6:28 PM
To: dev
Subject: Re: [DISCUSS] CloudStack Kubernetes Cluster Auto-Scale
DaanHoogland commented on a change in pull request #162:
URL:
https://github.com/apache/cloudstack-documentation/pull/162#discussion_r503790186
##
File path: source/adminguide/storage.rst
##
@@ -617,6 +617,34 @@ To resize a volume:
#. Click OK.
+Root Volume size defined v
utchoang commented on issue #803:
URL:
https://github.com/apache/cloudstack-primate/issues/803#issuecomment-707585091
@borisstoyanov @rhtyd cc @svenvogel So does that mean the list disk offering
will include data disk offering with value `>= 5 GB` and the custom disk
offering?
-
33 matches
Mail list logo
