[GitHub] [cloudstack-documentation] harikrishna-patnala commented on pull request #238: Update service offering section with new compute offering and disk offering changes

[GitBox]

harikrishna-patnala commented on pull request #238:
URL: 
https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909172197






-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-go] pdion891 commented on pull request #7: Fix generator for map parameters that are lists of objects

[GitBox]

pdion891 commented on pull request #7:
URL: https://github.com/apache/cloudstack-go/pull/7#issuecomment-909192455


   @psycofdj , Thanks for the PR,
   
   I fixed some output issues in `cloudstack/HostService.go` recently, and I 
was not aware of the interaction with `generate/generate.go`. 
   


-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] harikrishna-patnala removed a comment on pull request #238: Update service offering section with new compute offering and disk offering changes

[GitBox]

harikrishna-patnala removed a comment on pull request #238:
URL: 
https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909172197






-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-go] pdion891 merged pull request #7: Fix generator for map parameters that are lists of objects

[GitBox]

pdion891 merged pull request #7:
URL: https://github.com/apache/cloudstack-go/pull/7


   


-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] blueorangutan removed a comment on pull request #238: Update service offering section with new compute offering and disk offering changes

[GitBox]

blueorangutan removed a comment on pull request #238:
URL: 
https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909172731






-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] blueorangutan commented on pull request #238: Update service offering section with new compute offering and disk offering changes

[GitBox]

blueorangutan commented on pull request #238:
URL: 
https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-909172731






-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] harikrishna-patnala commented on a change in pull request #238: Update service offering section with new compute offering and disk offering changes

[GitBox]

harikrishna-patnala commented on a change in pull request #238:
URL: 
https://github.com/apache/cloudstack-documentation/pull/238#discussion_r699254953



##
File path: source/adminguide/storage.rst
##
@@ -661,6 +661,37 @@ The following table shows possible combinations of Service 
offering supported re
Shrinking the Root disk is not supported via the service offering resizing 
workflow. All the combinations above assume a transition to Root disks with 
size equals or bigger than the original.
Service Offerings with Root size of 0GB do not change the disk size to Zero 
and indicates that the offering do not enforces a Root disk size.
 
+Change disk offering for volume
+~~~
+
+There are volume operations like migrate volume and resize volume and both 
accepts new disk offering to replace the existing disk offering of volume.
+Instead of those APIs, Disk offering of a volume can be changed directly using 
changeOfferingForVolume API, also supported from UI.

Review comment:
   I've updated with Daan's version.




-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-go] psycofdj commented on pull request #7: Fix generator for map parameters that are lists of objects

[GitBox]

psycofdj commented on pull request #7:
URL: https://github.com/apache/cloudstack-go/pull/7#issuecomment-909104097


   Everything works fine on my production environment, I removed the WIP status.


-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-documentation] rhtyd removed a comment on pull request #238: Update service offering section with new compute offering and disk offering changes

[GitBox]

rhtyd removed a comment on pull request #238:
URL: 
https://github.com/apache/cloudstack-documentation/pull/238#issuecomment-907083590


   @blueorangutan docbuild


-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[DISCUSS] SystemVM template upgrade improvements

[Pearl d'Silva]

Hi All,

We have been working on a feature that simplifies SystemVM template install and 
upgrades for CloudStack. Historically we've required users to seed the template 
on secondary storage during fresh installation and register the template before 
an upgrade - this really does not make CloudStack turnkey, as we end up 
maintaining and managing them as a separate component - for example, users 
can't simply do an apt-get upgrade or yum upgrade to upgrade CloudStack.

The feature works by automatically initiating registration of the SystemVM 
templates during upgrades or when the first secondary storage is added to a 
zone where the SystemVM template hasn't been seeded. This feature addresses 
several operational pain points for example, when the admin user forgets to 
register the SystemVM template prior to an upgrade and faces the issue of 
having to roll back the database midway during the upgrade process. With this 
feature the upgrade process is seamless, such that the end users do not need to 
worry about having to perform template registration, but rather have the 
upgrade process take care of everything that is required.

In order to facilitate this feature, the SystemVM templates have to be bundled 
with the cloudstack-management rpm/deb package which causes the total noredist 
cloudstack-management package size to increase to about 1.6GB. We currently are 
packaging templates of only the three widely supported hypervisors - KVM, 
XenServer/XCP-ng and VMWare.
(These templates are only packaged if the build is initiated with the noredist 
flag.)

We'd like to get your opinion on this idea.

Thanks & Regards,
Pearl Dsilva

 

Re: [DISCUSS] SystemVM template upgrade improvements

[Rohit Yadav]

+1

Love this idea, I had actually tweeted about it and many from the community on 
Twitter really liked it at the time:
https://twitter.com/rhtyd/status/1420364812056350720

Regards.


From: Pearl d'Silva 
Sent: Wednesday, September 1, 2021 17:49
To: dev@cloudstack.apache.org 
Subject: [DISCUSS] SystemVM template upgrade improvements

Hi All,

We have been working on a feature that simplifies SystemVM template install and 
upgrades for CloudStack. Historically we've required users to seed the template 
on secondary storage during fresh installation and register the template before 
an upgrade - this really does not make CloudStack turnkey, as we end up 
maintaining and managing them as a separate component - for example, users 
can't simply do an apt-get upgrade or yum upgrade to upgrade CloudStack.

The feature works by automatically initiating registration of the SystemVM 
templates during upgrades or when the first secondary storage is added to a 
zone where the SystemVM template hasn't been seeded. This feature addresses 
several operational pain points for example, when the admin user forgets to 
register the SystemVM template prior to an upgrade and faces the issue of 
having to roll back the database midway during the upgrade process. With this 
feature the upgrade process is seamless, such that the end users do not need to 
worry about having to perform template registration, but rather have the 
upgrade process take care of everything that is required.

In order to facilitate this feature, the SystemVM templates have to be bundled 
with the cloudstack-management rpm/deb package which causes the total noredist 
cloudstack-management package size to increase to about 1.6GB. We currently are 
packaging templates of only the three widely supported hypervisors - KVM, 
XenServer/XCP-ng and VMWare.
(These templates are only packaged if the build is initiated with the noredist 
flag.)

We'd like to get your opinion on this idea.

Thanks & Regards,
Pearl Dsilva




 

Re: [DISCUSS] SystemVM template upgrade improvements

[Pearl d'Silva]

I probably missed adding the PR link to the feature - 
https://github.com/apache/cloudstack/pull/4329. Please do provide you inputs.


Thanks,
Pearl


From: Pearl d'Silva 
Sent: Wednesday, September 1, 2021 5:49 PM
To: dev@cloudstack.apache.org 
Subject: [DISCUSS] SystemVM template upgrade improvements

Hi All,

We have been working on a feature that simplifies SystemVM template install and 
upgrades for CloudStack. Historically we've required users to seed the template 
on secondary storage during fresh installation and register the template before 
an upgrade - this really does not make CloudStack turnkey, as we end up 
maintaining and managing them as a separate component - for example, users 
can't simply do an apt-get upgrade or yum upgrade to upgrade CloudStack.

The feature works by automatically initiating registration of the SystemVM 
templates during upgrades or when the first secondary storage is added to a 
zone where the SystemVM template hasn't been seeded. This feature addresses 
several operational pain points for example, when the admin user forgets to 
register the SystemVM template prior to an upgrade and faces the issue of 
having to roll back the database midway during the upgrade process. With this 
feature the upgrade process is seamless, such that the end users do not need to 
worry about having to perform template registration, but rather have the 
upgrade process take care of everything that is required.

In order to facilitate this feature, the SystemVM templates have to be bundled 
with the cloudstack-management rpm/deb package which causes the total noredist 
cloudstack-management package size to increase to about 1.6GB. We currently are 
packaging templates of only the three widely supported hypervisors - KVM, 
XenServer/XCP-ng and VMWare.
(These templates are only packaged if the build is initiated with the noredist 
flag.)

We'd like to get your opinion on this idea.

Thanks & Regards,
Pearl Dsilva




 

[GitHub] [cloudstack-cloudmonkey] pdion891 commented on pull request #95: Display output in human readable format

[GitBox]

pdion891 commented on pull request #95:
URL: 
https://github.com/apache/cloudstack-cloudmonkey/pull/95#issuecomment-910433133


   that's already better! 
   


-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-cloudmonkey] pdion891 edited a comment on pull request #95: Display output in human readable format

[GitBox]

pdion891 edited a comment on pull request #95:
URL: 
https://github.com/apache/cloudstack-cloudmonkey/pull/95#issuecomment-910433133


   that's already better!  but not quite I'm hoping we could expose.


-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-cloudmonkey] pdion891 commented on issue #94: add human readable output

[GitBox]

pdion891 commented on issue #94:
URL: 
https://github.com/apache/cloudstack-cloudmonkey/issues/94#issuecomment-910436978


   The #95  make reading better than before but I think it would be cleaner if 
we could get a more human interpreted version. 
   
   is such code could help ?  
   ```
   func convert(i int64) string {
v := []string{"B", "KB", "MB", "GB", "TB", "PB", "EB"}
l := 0
for ; i > 1024; i = i / 1024 {
l++
}
return fmt.Sprintf("%d %s", i, v[l])
   }
   ```
   
   This could work for any field that are `size` or `memory`,  but cannot be 
use for all integer type because that would not make sense for cpu count as 
example.
   


-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-cloudmonkey] rhtyd commented on issue #94: add human readable output

[GitBox]

rhtyd commented on issue #94:
URL: 
https://github.com/apache/cloudstack-cloudmonkey/issues/94#issuecomment-910438699


   That looks good - but then the issue is on which int64 inputs (i.e. response 
keys) should we apply this logic? (probably anything with size in the 
substring? however it may fail if it's not storage related key)


-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

[GitHub] [cloudstack-cloudmonkey] pdion891 commented on issue #94: add human readable output

[GitBox]

pdion891 commented on issue #94:
URL: 
https://github.com/apache/cloudstack-cloudmonkey/issues/94#issuecomment-910439645


   `int64` in that snippet can be changed. 
   


-- 
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: dev-unsubscr...@cloudstack.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Re: Console proxy creation failure

[David Jumani]

Could you send the /var/log/cloud.log in the console proxy VM ? Also try 
destroying and recreating the proxy VM

From: technologyrss.mail 
Sent: Wednesday, September 1, 2021 6:58 AM
To: us...@cloudstack.apache.org ; David Jumani 
; dev@cloudstack.apache.org 

Subject: Fwd: Console proxy creation failure



Thank you so much ! Yes, RAM issue. I increase RAM then fix but I see different 
error like I can't access vm console from browser. Please see below image.


ACS log file from below link.

https://drive.google.com/file/d/15C20k1wYlDFNReyY1iYoyfRdJodwdxiU/view?usp=sharing


[cid:part2.B70A23A0.CADBC208@gmail.com]


---
Alamin.


On 8/31/2021 2:38 PM, David Jumani wrote:
Hi

At just a glance, It looks like there isn't sufficient memory for the Console 
proxy to come up (by default it needs 1024 MB)
Try adding more memory or increasing the memory overprovisioning factor in the 
configuration / global settings tab






From: technologyrss.mail 

Sent: Tuesday, August 31, 2021 12:31 PM
To: us...@cloudstack.apache.org 
; 
dev@cloudstack.apache.org 

Subject: Console proxy creation failure


Hi,

I am able to setup ACS using centos 7.9. all service are properly working fine. 
But when I create basic zone then I see error like below .

ACS server : Centos 0s 7.9
NFS server : Centos 0s 7.8
KVM server : Centos 0s 7.8

[cid:part1.B6819867.0C83CE47@gmail.com]

Secondary Storage VM working fine but can't start proxy vm. what is issue?

[cid:part2.99CE7C85.B5717BC5@gmail.com]

This is system capacity like as below.


[cid:part3.389FB6FD.77D44A7C@gmail.com]


Please give me any idea..


Thanks, Alamin

 

Re: Console proxy creation failure

[technologyrss.mail]

I see iptables issue from my kvm host. after some time iptables service 
stop then I can't access any vm.



*---*

*Alamin*



On 9/2/2021 10:12 AM, David Jumani wrote:
Could you send the /var/log/cloud.log in the console proxy VM ? Also 
try destroying and recreating the proxy VM




*From:* technologyrss.mail 
*Sent:* Wednesday, September 1, 2021 6:58 AM
*To:* us...@cloudstack.apache.org ; David 
Jumani ; dev@cloudstack.apache.org 


*Subject:* Fwd: Console proxy creation failure

*Thank you so much ! *Yes, RAM issue. I increase RAM then fix but I 
see different error like I can't access vm console from browser. 
Please see below image.



ACS log file from below link.

https://drive.google.com/file/d/15C20k1wYlDFNReyY1iYoyfRdJodwdxiU/view?usp=sharing 





*---**
**Alamin.*


On 8/31/2021 2:38 PM, David Jumani wrote:

Hi

At just a glance, It looks like there isn't sufficient memory for the 
Console proxy to come up (by default it needs 1024 MB)
Try adding more memory or increasing the memory overprovisioning 
factor in the configuration / global settings tab




*From:* technologyrss.mail  


*Sent:* Tuesday, August 31, 2021 12:31 PM
*To:* us...@cloudstack.apache.org 
  
; dev@cloudstack.apache.org 
  


*Subject:* Console proxy creation failure

*Hi,*

I am able to setup ACS using centos 7.9. all service are properly 
working fine. But when I create basic zone then I see error like below .


ACS server : Centos 0s 7.9
NFS server : Centos 0s 7.8
KVM server : Centos 0s 7.8

Secondary Storage VM working fine but can't start proxy vm. what is 
issue?


This is system capacity like as below.



Please give me any idea..


*Thanks, Alamin*