Re: [DISCUSS] SystemVM template upgrade improvements

[Nathan McGarvey]

+1

This is also helpful for restricted-from-internet installations. (E.g.
places with on-site installs and strong firewall/proxy/air-gap rules.)
Which is a feature that is increasingly hard to come by for cloud-based
underpinnings, but increasingly of interest for many organizations who
like to have control of where their data resides. (Banks, medical
institutions, governments, etc.)


Should it be in the same packaging, or be a separate package entirely?
That way the current packaging could still remain as-is but have the
option of obtaining the seperately packaged systemVMs in package-manager
format. If you really wanted to, you could even break out the KVM vs Xen
vs VMWare into separate packages to help reduce size and increase
modularity. Then you still are hooking into the turnkey-method since it
lends itself to a apt-get upgrade or yum upgrade, and can update
components individually and maintain that certain versions of SystemVMs
require certain cloudstack versions and vice-versa.



Thanks,
-Nathan McGarvey

On 9/2/21 9:29 AM, Rohit Yadav wrote:
> Hi Hean,
> 
> Yes I think the old approach of registering systemvm template prior to 
> upgrade as well as the option to switch between systemvmtemplate continues to 
> be supported. What this feature primarily aims is to make CloudStack turnkey 
> operationally.
> 
> May I ask if anyone has any objections on the increased package size? Due to 
> the trade off of including systemvmtemplates in the management package the 
> size increased to about 1-1.5GB which is the only thing I didn't like. 
> However I think this can be optimised in future releases.
> 
> Regards.
> 
> From: Hean Seng 
> Sent: Thursday, September 2, 2021 7:34:32 AM
> To: users@cloudstack.apache.org 
> Cc: d...@cloudstack.apache.org 
> Subject: Re: [DISCUSS] SystemVM template upgrade improvements
> 
> This is good idea.  Or else , we shall allow  manual upload via. GUI, and
> mark for system template .
> 
> On Wed, Sep 1, 2021 at 9:08 PM Pearl d'Silva 
> wrote:
> 
>> 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: d...@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
>>
>>
>>
>>
>>
>>
>>
> 
> --
> Regards,
> Hean Seng
> 
>  
> 
> 

Re: Console proxy creation failure

[David Jumani]

If that's the case, you can remove the host, reset the IP table rules, 
reinstall the cloudstack agent and add the required IP tables rules as 
mentioned here (as some iptable rules are added to allow the console proxy 
communicate with the vnc port on the host)
https://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/kvm.html
https://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/kvm.html#open-ports-in-rhel-centos

From: technologyrss.mail 
Sent: Thursday, September 2, 2021 11:13 AM
To: David Jumani ; users@cloudstack.apache.org 
; d...@cloudstack.apache.org 

Subject: Re: Console proxy creation failure


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: users@cloudstack.apache.org 
; David Jumani 
; 
d...@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.2E081B89.7FF30886@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: users@cloudstack.apache.org 
; 
d...@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: Plugin not working after upgrade to 4.15

[David Jumani]

With the introduction of the new UI, the method to add plugins has changed a 
bit, you can find more information here
https://docs.cloudstack.apache.org/en/latest/adminguide/ui.html#basic-ui-customization



 

From: Gross, Christian
Sent: Thursday, September 2, 2021 7:54 PM
To: users@cloudstack.apache.org
Subject: Plugin not working after upgrade to 4.15

Hello Community

Just updated ACS to 4.15 from 4.14. Now, our plugin is not working anymore. I 
tried it with restarting the management-server, but still no success.

According the following guide, this should still work:
https://docs.cloudstack.apache.org/en/latest/developersguide/plugins.html#third-party-ui-plugins

Our folder structure is as follows:

# pwd
/usr/share/cloudstack-management/webapp

# tree -L 1
.
|-- WEB-INF
|-- assets
|-- cloud.ico
|-- color.less
|-- config.json -> /etc/cloudstack/management/config.json
|-- config.json_bak
|-- css
|-- error.html
|-- example.html
|-- index.html
|-- js
|-- legacy
|-- locales
|-- plugins
`-- primate

# tree -L 1 plugins/
plugins/
|-- myplugin
`-- plugins.js

# tree -L 1 plugins/ncReports/
plugins/myplugin/
|-- config.js
|-- icon.png
|-- myplugin.css
|-- myplugin.js
|-- myplugin.png
`-- webfonts

Maybe someone of you has an idea, why this is not working anymore..

Best Regards
Chris

Can I use only LAN for Advanced Zone

[technologyrss.mail]

*Hi,*

Can I use only LAN for Advanced Zone? is it possible ? If possible so 
how can I setup network from.


    Management, Public & Guest interface.

All interface connected is LAN then set value is cloudbr0, is it correct?

*or,*

How can I create Advanced Zone without public ip for testing purposes?

please give me some idea


*---**
**Thanks, alamin*

Re: XCP-ng Backup Cloudstack 4.15

[benoit lair]

Is there a way to implement ourself a custom external provider in order to
backup VMs ?

Le jeu. 2 sept. 2021 à 15:52, benoit lair  a écrit :

> Hello,
>
> I am interested too in doing Backup VM for Xcp-NG
> Would you have a solution for using Veeam like Yordan aims ?
>
> Le lun. 12 juil. 2021 à 13:30, Abishek Budhathoki  a
> écrit :
>
>> Thank You for the response. Really apricated.
>>
>> On 2021/07/12 09:41:07, Rohit Yadav  wrote:
>> > Hi Abishek,
>> >
>> > That's right, the current Backup & Recovery framework only supports
>> Veeam provider on VMware.
>> >
>> > For XenServer/xcpng, we don't have a plugin/provider, however volume
>> snapshots can be used to backup snapshots on secondary storage.
>> >
>> > Regards.
>> >
>> > Regards,
>> > Rohit Yadav
>> >
>> > 
>> > From: Abishek Budhathoki 
>> > Sent: Saturday, July 10, 2021 7:42:12 PM
>> > To: users@cloudstack.apache.org 
>> > Subject: XCP-ng Backup Cloudstack 4.15
>> >
>> > Hello EveryOne,
>> >
>> > I am trying cloudstack with xen environment. I was trying out the
>> backup feature of the cloudstack and was not able to achieve it. Does the
>> backup work in xen environment or it strictly only works with vmware only.
>> >
>> >
>> >
>> >
>> >
>> >
>>
>

Status after volume is deleted

[li jerry]

Hi,All

I am using 4.15.0.0+KVM +CEPH,I found that the deleted volumes in the 
cloud.volumes table are divided into two situations;

1. removed!=null, state=Expunged  , pool_id !=null

2. removed!=null, state=Destroy,pool_id=null


After VOLUME is deleted, why are two different states recorded in the database?



-Jerry

Re: [DISCUSS] SystemVM template upgrade improvements

[Rohit Yadav]

Hi Hean,

Yes I think the old approach of registering systemvm template prior to upgrade 
as well as the option to switch between systemvmtemplate continues to be 
supported. What this feature primarily aims is to make CloudStack turnkey 
operationally.

May I ask if anyone has any objections on the increased package size? Due to 
the trade off of including systemvmtemplates in the management package the size 
increased to about 1-1.5GB which is the only thing I didn't like. However I 
think this can be optimised in future releases.

Regards.

From: Hean Seng 
Sent: Thursday, September 2, 2021 7:34:32 AM
To: users@cloudstack.apache.org 
Cc: d...@cloudstack.apache.org 
Subject: Re: [DISCUSS] SystemVM template upgrade improvements

This is good idea.  Or else , we shall allow  manual upload via. GUI, and
mark for system template .

On Wed, Sep 1, 2021 at 9:08 PM Pearl d'Silva 
wrote:

> 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: d...@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
>
>
>
>
>
>
>

--
Regards,
Hean Seng

 

Plugin not working after upgrade to 4.15

[Gross, Christian]

Hello Community

Just updated ACS to 4.15 from 4.14. Now, our plugin is not working anymore. I 
tried it with restarting the management-server, but still no success.

According the following guide, this should still work:
https://docs.cloudstack.apache.org/en/latest/developersguide/plugins.html#third-party-ui-plugins

Our folder structure is as follows:

# pwd 
/usr/share/cloudstack-management/webapp 

# tree -L 1 
. 
|-- WEB-INF 
|-- assets 
|-- cloud.ico 
|-- color.less 
|-- config.json -> /etc/cloudstack/management/config.json 
|-- config.json_bak 
|-- css 
|-- error.html 
|-- example.html 
|-- index.html 
|-- js 
|-- legacy 
|-- locales 
|-- plugins 
`-- primate 
 
# tree -L 1 plugins/ 
plugins/ 
|-- myplugin 
`-- plugins.js 
 
# tree -L 1 plugins/ncReports/
plugins/myplugin/ 
|-- config.js 
|-- icon.png 
|-- myplugin.css 
|-- myplugin.js 
|-- myplugin.png 
`-- webfonts 

Maybe someone of you has an idea, why this is not working anymore..

Best Regards
Chris


smime.p7s
Description: S/MIME cryptographic signature

Re: instance backup designs?

[benoit lair]

Hello Rohit,

How could it be possible to implement a custom backup provider ?

Le ven. 18 juin 2021 à 09:39, Yordan Kostov  a écrit :

> Thank you Rohit,
>
> I am all over it 😊.
>
> Regards,
> Jordan
>
> -Original Message-
> From: Rohit Yadav 
> Sent: Thursday, June 17, 2021 6:21 PM
> To: users@cloudstack.apache.org
> Subject: Re: instance backup designs?
>
>
> [X] This message came from outside your organization
>
>
> Hi Yordan,
>
> We do have a backup & recovery framework which can be extended to
> implement support for new solutions, the current provider/plugin is
> available only for Vmware/Veeam and which can be used to implement support
> for other backup solutions for other hypervisors.
>
> While there is no choice now, for XenServer/XCP-NG you can use volume
> snapshots as a way to have backups volumes on secondary storage.
>
>
> Regards.
>
> 
> From: Yordan Kostov 
> Sent: Wednesday, June 16, 2021 18:46
> To: users@cloudstack.apache.org 
> Subject: instance backup designs?
>
> Hey everyone,
>
> I was wondering what choice does one have for backup when
> underlying hypervisor is XenServer/XCP-NG?
> Any high level ideas or just sharing any doc that may
> exist will be great!
>
> Best regards,
> Jordan
>
>
>
>

Re: XCP-ng Backup Cloudstack 4.15

[benoit lair]

Hello,

I am interested too in doing Backup VM for Xcp-NG
Would you have a solution for using Veeam like Yordan aims ?

Le lun. 12 juil. 2021 à 13:30, Abishek Budhathoki  a
écrit :

> Thank You for the response. Really apricated.
>
> On 2021/07/12 09:41:07, Rohit Yadav  wrote:
> > Hi Abishek,
> >
> > That's right, the current Backup & Recovery framework only supports
> Veeam provider on VMware.
> >
> > For XenServer/xcpng, we don't have a plugin/provider, however volume
> snapshots can be used to backup snapshots on secondary storage.
> >
> > Regards.
> >
> > Regards,
> > Rohit Yadav
> >
> > 
> > From: Abishek Budhathoki 
> > Sent: Saturday, July 10, 2021 7:42:12 PM
> > To: users@cloudstack.apache.org 
> > Subject: XCP-ng Backup Cloudstack 4.15
> >
> > Hello EveryOne,
> >
> > I am trying cloudstack with xen environment. I was trying out the backup
> feature of the cloudstack and was not able to achieve it. Does the backup
> work in xen environment or it strictly only works with vmware only.
> >
> >
> >
> >
> >
> >
>

Re: Unable to start a VM due to insufficient capacity

[Michael Kesper]

Am 02.09.21 um 09:54 schrieb technologyrss.mail:
> *Hi,*
> 
> I setup Advanced zone using *ACS v4.15.1* but can't instance properly. I 
> attached ACS log file with my system dashboard as like below image.
> 
> For small environment for testing purposes. All servers are centos 7.8 with 
> separate NFS storage.
> 
> *This is ACS log.*

Please do not post screenshots of logfiles but the text instead.

Michael



OpenPGP_signature
Description: OpenPGP digital signature

Re: Unable to start a VM due to insufficient capacity

[Ivan Kudryavtsev]

Hi, the actual error is earlier (above) the mentioned log part. Please
provide about 100 lines before.

On Thu, Sep 2, 2021 at 2:55 PM technologyrss.mail <
technologyrss.m...@gmail.com> wrote:

> *Hi,*
>
> I setup Advanced zone using *ACS v4.15.1* but can't instance properly. I
> attached ACS log file with my system dashboard as like below image.
>
> For small environment for testing purposes. All servers are centos 7.8
> with separate NFS storage.
>
> *This is ACS log.*
>
>
> *This is web browser error when I create instance.*
>
>
> *This is my server system capacity,*
>
>
> Please give me some idea what is issue for my system capacity?
>
>
> *---*
> *alamin*
>
>
>