Re: [VOTE] Apache Cloudstack 4.15.0.0 and UI [RC3]

[Boris Stoyanov]

+1 (binding) 

In shared effort with Vladimir Petrov, we've done upgrade testing from latest 
of: 
4.11
4.13
4.14 

Also did a basic lifecycle operations of: 
VMs, Networks, Storage, Infra(pod, cluster, zone, hosts). 

And we couldn't find any stopping issues with this RC. 

Thanks,
Bobby.

On 24.12.20, 5:14, "Rohit Yadav"  wrote:


All,

Here are the convenience packages build from 4.15.0.0-RC3 if you don't want 
to build CloudStack from the source artifacts:

Packages: (Debian, CentOS7, and CentOS8)
http://download.cloudstack.org/testing/4.15.0.0-rc3/

4.15 systemvmtemplate:
http://download.cloudstack.org/systemvm/4.15/

Build from the master branch of 
https://github.com/apache/cloudstack-documentation (if/after voting passes, 
we'll update and publish the docs):
http://docs.cloudstack.apache.org/en/master/upgrading/

Additional notes:
  *   The new UI is bundled within the cloudstack-management package and is 
shipped as the default UI served at /client, old UI will be served 
via /client/legacy. Most users don't need to do any separate 
installation or perform an installation step.
  *   We've added support for CentOS8 with 4.15 but CentOS8 will EOL in Dec 
2021 (https://wiki.centos.org/About/Product).


Regards.


From: Daan Hoogland 
Sent: Wednesday, December 23, 2020 23:13
To: users ; dev 
Subject: [VOTE] Apache Cloudstack 4.15.0.0 and UI [RC3]

LS,
After fixing another few blockers, we have an RC3, The changes (other than
bundling) are mostly interesting for those working with templates and on
vmware.

We are voting for the new UI and the main code.

The candidate release branch is 4.15.0.0-RC20201223T1632. The UI is still
separate but as agreed upon before this will be merged in coming releases,
at least from a version management point of view.
I've created a 4.15.0.0 release candidate, with the following artifacts up
for a vote:Git Branches:
main code:

https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.15.0.0-RC20201223T1632


ui code:



https://git-wip-us.apache.org/repos/asf?p=cloudstack-primate.git;a=tag;h=refs/tags/1.0
and Commit SH:
main code: 01b3e361c7bb81fd1ea822faddd6594e52bb00c1
ui code: 0593302dd53ac3203d3ab43b62d890605910f3e1

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.15.0.0/ (rev. 45059)
PGP release keys (signed using 7975062401944786):
https://dist.apache.org/repos/dist/release/cloudstack/KEYSVote will be open
for (at least) 72 hours.For sanity in tallying the vote, can PMC members
please be sure to indicate "(binding)" with their vote?[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

I will work with community members to provide convenience packaging over
the next few days.
The documentation repo will be updated as we move along.



--
Daan

rohit.ya...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue





boris.stoya...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue
  
 

Re: [VOTE] Apache Cloudstack 4.15.0.0 and UI [RC3]

[Gabriel Bräscher]

Another key point for IPv6 regards the hypervisor and network setup;
CloudStack supports IPv6 only for KVM, and when deploying zones with the
advanced network and security groups enabled.

Em qui., 31 de dez. de 2020 às 08:35, Andrija Panic 
escreveu:

> afaik, IPv6 is only supported in Shared networks, and can't be used for
> Public network.
>
> On Thu, 31 Dec 2020 at 11:29, Chirag Katbamna  wrote:
>
> >
> >
> > Hello
> > I am trying to enter IPv6 addresses as my Public IP address. I am unable
> > to enter it during a fresh setup. I have verified my IPv6's are correct
> and
> > valid. But it seems only IPv4 is expected on the screen. See attached
> > screenshot.
> >
> > My assumption is that IPv6 for public IP is supported to start with (my
> > first time trying it so not 100% sure). Do I need to enable anything
> > specific before it works? IPv6 on the local network is enabled already.
> >
> > Thanks
> > Chirag K
> >
> >
> >
> >
>
> --
>
> Andrija Panić
>

Re: [VOTE] Apache Cloudstack 4.15.0.0 and UI [RC3]

[Gabriel Bräscher]

+1 (binding)

I could not find any blocker issue neither on CloudStack nor
CloudStack-primate.

Details:
1. Environment:
- Apache CloudStack: Management server + DB (Ubuntu 18.04)
- Hosts: KVM (Ubuntu 18.04)
- Primary Storage: NFS, RBD, KVM Local- Secondary Storage: NFS
- Zone Network: Advanced network + Security Groups
- Tests were performed on both Primate UI and legacy UI

2. Tests:
- Build 4.15.0.0 from source
- Upgrade from 4.13.1.0 to 4.15.0.0
- Deploy SystemVMs
- create user VMs on different primary storages (local, NFS, RBD)
- Live Migrate VMs (tested with local, NFS, and RBD)
- Put host in maintenance
- Remove/add host
- Add/remove primary storage (local and NFS)
- Add secondary storage (NFS)
- Deploy new Zone
- Register template
- Configure Service Offerings
- Change VM's offering
- Enable OOBM (Redfish)
- Perform OOBM actions (Redfish)

Em qui., 31 de dez. de 2020 às 06:03, Rohit Yadav 
escreveu:

> +1 (binding)
>
> I ran smoketests with the following combination (fresh installation only)
> and all tests passed except for one case on KVM (see below), few cases
> known to fail intermittently were checked and ignored (test_01_scale_vm,
> test_04_rvpc_privategw_static_routes which passed in other environments):
>
> CentOS7 mgmt server + vmware-65u2 + adv zone
> CentOS7 mgmt server + kvm-centos7 + adv zone
> CentOS7 mgmt server + xenserver-71 + adv zone
>
> On the KVM CentOS7 env this failed:
> test_03_deploy_and_upgrade_kubernetes_cluster | `Failure` | 240.74 |
> test_kubernetes_clusters.py
>
> On manual investigation, the above turned out to be an intermittent issue
> (passed on manual attempt and already passed in other env). I've also
> manually tested the following:
> - Basic VM lifecycle tests using default built-in CentOS template on an
> isolated network
> - CKS cluster setup with v1.16.0 with CoreOS template, also tested upgrade
> CKS cluster to v1.16.3
> - Several basic views of the modern UI, and legacy UI on the
> /client/legacy to check basic VM lifecycle views and actions
> - The new novnc console both over unsecured and SSL-enabled environments
>
>
> Proposed a minor document change based on testing Kubernetes/CKS cluster:
>
> https://github.com/apache/cloudstack-documentation/pull/174/files
>
>
> Regards.
>
> 
> From: Daan Hoogland 
> Sent: Wednesday, December 23, 2020 23:13
> To: users ; dev 
> Subject: [VOTE] Apache Cloudstack 4.15.0.0 and UI [RC3]
>
> LS,
> After fixing another few blockers, we have an RC3, The changes (other than
> bundling) are mostly interesting for those working with templates and on
> vmware.
>
> We are voting for the new UI and the main code.
>
> The candidate release branch is 4.15.0.0-RC20201223T1632. The UI is still
> separate but as agreed upon before this will be merged in coming releases,
> at least from a version management point of view.
> I've created a 4.15.0.0 release candidate, with the following artifacts up
> for a vote:Git Branches:
> main code:
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.15.0.0-RC20201223T1632
> <
> https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.15.0.0-RC20201214T1124
> >
> ui code:
> <
> https://git-wip-us.apache.org/repos/asf?p=cloudstack-primate.git;a=shortlog;h=refs/tags/1.0
> >
>
> https://git-wip-us.apache.org/repos/asf?p=cloudstack-primate.git;a=tag;h=refs/tags/1.0
> and Commit SH:
> main code: 01b3e361c7bb81fd1ea822faddd6594e52bb00c1
> ui code: 0593302dd53ac3203d3ab43b62d890605910f3e1
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.15.0.0/ (rev. 45059)
> PGP release keys (signed using 7975062401944786):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYSVote will be
> open
> for (at least) 72 hours.For sanity in tallying the vote, can PMC members
> please be sure to indicate "(binding)" with their vote?[ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> I will work with community members to provide convenience packaging over
> the next few days.
> The documentation repo will be updated as we move along.
>
>
>
> --
> Daan
>
> rohit.ya...@shapeblue.com
> www.shapeblue.com
> 3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
> @shapeblue
>
>
>
>

Re: Management server added each reboot

[Andrija Panic]

that indeed has somthing to do with your setup.
check the cluster.node.ip inside the db.properties on each mgmt server -
value of this should be == the local IP of the mgmt server.

Accessing (externally) UI via HAProxy should not affect this...

can you share the "select * from mshost;"

You can also set "removed" value for those "old" records in the mshost
table (which are already down) to some date in past - so if they have the
"removed" date set, ACS considers them removed, and you will not see them
in the UI.

Best,

On Mon, 21 Dec 2020 at 03:48, Niclas Lindblom
 wrote:

> Hi all,
>
> I have 2 management servers load balanced with HA Proxy which all appears
> to be working properly. However, each time a reboot a server a new
> management server is added in the UI (database) and I now have a long list
> of servers showing as down and the 2 currently in use showing as up all
> with different uuid's.
>
> I am guess this have something to do with the HA proxy load balancing, but
> not sure how to troubleshoot and would appreciate any pointers.
>
> Thanks
>
> Niclas



-- 

Andrija Panić

Re: reserved CPU?

[Andrija Panic]

Hi Adam,

try reducing the global setting: capacity.skipcounting.hours

Without the logs, there's not much we can conclude. Usually, if you are
i.e. FULL in terms of CPU capacity (i.e. reached the limit above which no
new VMs can be deployed) - then when you STOP an existing VM, host will
reserve the amount of CPU used by that stopped VM - so that you can
immediately/within the " capacity.skipcounting.hours " start it again - but
it will not allow you to deploy new VMs even while that existing VM is
stopped.

Hope that helps,

On Tue, 22 Dec 2020 at 12:37, Adam Witwicki  wrote:

> That setting seems fine, I can start an instance.
>
> I cannot start a system VM due to reserved capacity?
>
> Thanks
>
> Adam
>
> -Original Message-
> From: Alireza Eskandari 
> Sent: 22 December 2020 11:33
> To: users@cloudstack.apache.org
> Subject: Re: reserved CPU?
>
> ** This mail originated from OUTSIDE the Oakford corporate network. Treat
> hyperlinks and attachments in this email with caution. **
>
> Hi,
> From "Home > Infrastructure > Clusters > your_cluster" click on "Settings"
> tab. In search bar type "cpu" and you will see a list of variables that
> controls CPU usage and allocation in your cluster.
> You can "increase cpu.overprovisioning.factor" or change
> "cluster.cpu.allocated.capacity.disablethreshold"
> Regards
>
> On Tue, Dec 22, 2020 at 12:39 PM Adam Witwicki 
> wrote:
>
> > Hello
> >
> > I am unable to start any routers due to this error
> >
> > Host does not have enough reserved CPU available, cannot allocate to
> > this host.
> >
> > I cannot find any setting to adjust the reserved CPU for a host -
> > these have plenty
> >
> > Can someone point me in the right direction please
> >
> > CS 4.13.1.0 - KVM hosts
> >
> >
> > Adam
> >
> >
> >
> > Disclaimer Notice:
> > This email has been sent by Oakford Technology Limited, while we have
> > checked this e-mail and any attachments for viruses, we can not
> > guarantee that they are virus-free. You must therefore take full
> > responsibility for virus checking.
> > This message and any attachments are confidential and should only be
> > read by those to whom they are addressed. If you are not the intended
> > recipient, please contact us, delete the message from your computer
> > and destroy any copies. Any distribution or copying without our prior
> > permission is prohibited.
> > Internet communications are not always secure and therefore Oakford
> > Technology Limited does not accept legal responsibility for this message.
> > The recipient is responsible for verifying its authenticity before
> > acting on the contents. Any views or opinions presented are solely
> > those of the author and do not necessarily represent those of Oakford
> Technology Limited.
> > Registered address: Oakford Technology Limited, The Manor House,
> > Potterne, Wiltshire. SN10 5PN.
> > Registered in England and Wales No. 5971519
> >
> >
> Disclaimer Notice:
> This email has been sent by Oakford Technology Limited, while we have
> checked this e-mail and any attachments for viruses, we can not guarantee
> that they are virus-free. You must therefore take full responsibility for
> virus checking.
> This message and any attachments are confidential and should only be read
> by those to whom they are addressed. If you are not the intended recipient,
> please contact us, delete the message from your computer and destroy any
> copies. Any distribution or copying without our prior permission is
> prohibited.
> Internet communications are not always secure and therefore Oakford
> Technology Limited does not accept legal responsibility for this message.
> The recipient is responsible for verifying its authenticity before acting
> on the contents. Any views or opinions presented are solely those of the
> author and do not necessarily represent those of Oakford Technology Limited.
> Registered address: Oakford Technology Limited, The Manor House, Potterne,
> Wiltshire. SN10 5PN.
> Registered in England and Wales No. 5971519
>
>

-- 

Andrija Panić

Re: SSVM and CPVM agent unable to start after console proxy SSL certificate update

[Andrija Panic]

The issue, most probably, is due to different SSL provider or different
names used for the certificates - I've seen this in past.

I would *strongly* suggest, removing all relevant records from the
cloud.keystore table (all records related to the domain you are using -
that probably means indeed ALL records from the table...)
Then upload the SSL and it's intermediate/Root certificates again, i.e.
from scratch.
restart mgmt, and ensure SSVM/CPVM are destroyed

Best,



On Mon, 28 Dec 2020 at 11:43, Rohit Yadav  wrote:

> Hi,
>
> Can you try to manually start the cloud service, for example: "service
> cloud start" and tail/share the logs which may explain why the java process
> is not running.
> If that does not work, you may also try to validate/verify the
> certificates (including any chain/intermediate certificates) you've
> uploaded and destroy the old CPVM/SSVM.
>
> For more information on SSL certificate setup, you may read this
> 4.11-specific blog
> https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/ which
> I think is applicable for 4.9 as well.
>
>
> Regards.
>
> 
> From: Cloud List 
> Sent: Saturday, December 26, 2020 09:42
> To: users@cloudstack.apache.org ; dev <
> d...@cloudstack.apache.org>
> Subject: SSVM and CPVM agent unable to start after console proxy SSL
> certificate update
>
> Hi,
>
> Merry Christmas to all.
>
> We are using Cloudstack with KVM hypervisor. Since our console proxy SSL
> certificate has expired, we updated our new SSL certificate using below
> method:
>
>
> http://docs.cloudstack.apache.org/projects/cloudstack-administration/en/4.9/systemvm.html#using-a-ssl-certificate-for-the-console-proxy
>
> We have done the above method in the past years without any issues, however
> this time round, both the SSVM and CPVM agents are not able to start after
> the update.
>
> The state for both VMs are up but agents are in "disconnected" state. We
> are still able to login to the SSVM, and found out that the cloud service
> is not running.
>
> root@s-4200-VM:~# service cloud status
> CloudStack cloud service is not running
>
> Tried to start the service:
>
> root@s-4200-VM:~# service cloud start
> Starting CloudStack cloud service (type=secstorage) Success
>
> But the service is not started:
>
> root@s-4200-VM:~# service cloud status
> CloudStack cloud service is not running
>
> Below is the logs from /var/log/cloud.log:
>
> =
> Sat Dec 26 03:45:04 UTC 2020 Executing cloud-early-config
> Sat Dec 26 03:45:04 UTC 2020 Detected that we are running inside kvm guest
> Sat Dec 26 03:45:04 UTC 2020 Found a non empty cmdline file. Will now exit
> the loop and proceed with configuration.
> Sat Dec 26 03:45:04 UTC 2020 Patching  cloud service
> Sat Dec 26 03:45:10 UTC 2020 Updating log4j-cloud.xml
> Sat Dec 26 03:45:10 UTC 2020 Setting up secondary storage system vm
> Sat Dec 26 03:45:10 UTC 2020 checking that eth0 has IP
> Sat Dec 26 03:45:11 UTC 2020 waiting for eth0 interface setup with ip
> timer=0
> Sat Dec 26 03:45:11 UTC 2020 checking that eth1 has IP
> Sat Dec 26 03:45:11 UTC 2020 checking that eth2 has IP
> Sat Dec 26 03:45:20 UTC 2020 checking that eth3 has IP
> Sat Dec 26 03:45:20 UTC 2020 Successfully setup storage network with
> STORAGE_IP:10.19.22.67, STORAGE_NETMASK:255.255.240.0, STORAGE_CIDR:
> Sat Dec 26 03:45:20 UTC 2020 Setting up route of RFC1918 space to
> 10.19.16.1
> Sat Dec 26 03:45:20 UTC 2020 Setting up apache web server
> Sat Dec 26 03:45:20 UTC 2020 setting up apache2 for post upload of
> volume/template
> Sat Dec 26 03:45:20 UTC 2020 rewrite rules already exist in file
> /etc/apache2/sites-available/default-ssl
> Sat Dec 26 03:45:20 UTC 2020 adding cors rules to file:
> /etc/apache2/sites-available/default-ssl
> Sat Dec 26 03:45:21 UTC 2020 cloud: disable rp_filter
> Sat Dec 26 03:45:21 UTC 2020 disable rpfilter
> Sat Dec 26 03:45:21 UTC 2020 cloud: enable_fwding = 0
> Sat Dec 26 03:45:21 UTC 2020 enable_fwding = 0
> Sat Dec 26 03:45:21 UTC 2020 Enable service haproxy = 0
> Sat Dec 26 03:45:21 UTC 2020 Processors = 1  Enable service  = 0
> Sat Dec 26 03:45:21 UTC 2020 Enable service dnsmasq = 0
> Sat Dec 26 03:45:21 UTC 2020 Enable service cloud-passwd-srvr = 0
> Sat Dec 26 03:45:21 UTC 2020 Enable service cloud = 1
> =
>
> Result of /usr/local/cloud/systemvm/ssvm-check.sh:
>
> =
> root@s-4200-VM:/var/log# /usr/local/cloud/systemvm/ssvm-check.sh
> 
> First DNS server is  8.8.8.8
> PING 8.8.8.8 (8.8.8.8): 48 data bytes
> 56 bytes from 8.8.8.8: icmp_seq=0 ttl=122 time=0.531 ms
> 56 bytes from 8.8.8.8: icmp_seq=1 ttl=122 time=0.676 ms
> --- 8.8.8.8 ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max/stddev = 0.531/0.604/0.676/0.073 ms
> Good: Can ping DNS server
> 
> Good: DNS resolves download.cloud.com
> 
> ERROR: 

Re: [VOTE] Apache Cloudstack 4.15.0.0 and UI [RC3]

[Andrija Panic]

afaik, IPv6 is only supported in Shared networks, and can't be used for
Public network.

On Thu, 31 Dec 2020 at 11:29, Chirag Katbamna  wrote:

>
>
> Hello
> I am trying to enter IPv6 addresses as my Public IP address. I am unable
> to enter it during a fresh setup. I have verified my IPv6's are correct and
> valid. But it seems only IPv4 is expected on the screen. See attached
> screenshot.
>
> My assumption is that IPv6 for public IP is supported to start with (my
> first time trying it so not 100% sure). Do I need to enable anything
> specific before it works? IPv6 on the local network is enabled already.
>
> Thanks
> Chirag K
>
>
>
>

-- 

Andrija Panić

Re: [VOTE] Apache Cloudstack 4.15.0.0 and UI [RC3]

[Chirag Katbamna]

Hello
I am trying to enter IPv6 addresses as my Public IP address. I am unable to
enter it during a fresh setup. I have verified my IPv6's are correct and
valid. But it seems only IPv4 is expected on the screen. See attached
screenshot.

My assumption is that IPv6 for public IP is supported to start with (my
first time trying it so not 100% sure). Do I need to enable anything
specific before it works? IPv6 on the local network is enabled already.

Thanks
Chirag K

Public IPv6 address in 4.15 RC2

[Chirag Katbamna]

Hello
I am trying to enter IPv6 addresses as my Public IP address. I am unable to
enter it during a fresh setup. I have verified my IPv6's are correct and
valid. But it seems only IPv4 is expected on the screen. See attached
screenshot.

My assumption is that IPv6 for public IP is supported to start with (my
first time trying it so not 100% sure). Do I need to enable anything
specific before it works? IPv6 on the local network is enabled already.

Thanks
Chirag K

Re: [VOTE] Apache Cloudstack 4.15.0.0 and UI [RC3]

[Rohit Yadav]

+1 (binding)

I ran smoketests with the following combination (fresh installation only) and 
all tests passed except for one case on KVM (see below), few cases known to 
fail intermittently were checked and ignored (test_01_scale_vm, 
test_04_rvpc_privategw_static_routes which passed in other environments):

CentOS7 mgmt server + vmware-65u2 + adv zone
CentOS7 mgmt server + kvm-centos7 + adv zone
CentOS7 mgmt server + xenserver-71 + adv zone

On the KVM CentOS7 env this failed:
test_03_deploy_and_upgrade_kubernetes_cluster | `Failure` | 240.74 | 
test_kubernetes_clusters.py

On manual investigation, the above turned out to be an intermittent issue 
(passed on manual attempt and already passed in other env). I've also manually 
tested the following:
- Basic VM lifecycle tests using default built-in CentOS template on an 
isolated network
- CKS cluster setup with v1.16.0 with CoreOS template, also tested upgrade CKS 
cluster to v1.16.3
- Several basic views of the modern UI, and legacy UI on the 
/client/legacy to check basic VM lifecycle views and actions
- The new novnc console both over unsecured and SSL-enabled environments


Proposed a minor document change based on testing Kubernetes/CKS cluster:

https://github.com/apache/cloudstack-documentation/pull/174/files


Regards.


From: Daan Hoogland 
Sent: Wednesday, December 23, 2020 23:13
To: users ; dev 
Subject: [VOTE] Apache Cloudstack 4.15.0.0 and UI [RC3]

LS,
After fixing another few blockers, we have an RC3, The changes (other than
bundling) are mostly interesting for those working with templates and on
vmware.

We are voting for the new UI and the main code.

The candidate release branch is 4.15.0.0-RC20201223T1632. The UI is still
separate but as agreed upon before this will be merged in coming releases,
at least from a version management point of view.
I've created a 4.15.0.0 release candidate, with the following artifacts up
for a vote:Git Branches:
main code:
https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;a=shortlog;h=refs/heads/4.15.0.0-RC20201223T1632

ui code:

https://git-wip-us.apache.org/repos/asf?p=cloudstack-primate.git;a=tag;h=refs/tags/1.0
and Commit SH:
main code: 01b3e361c7bb81fd1ea822faddd6594e52bb00c1
ui code: 0593302dd53ac3203d3ab43b62d890605910f3e1

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.15.0.0/ (rev. 45059)
PGP release keys (signed using 7975062401944786):
https://dist.apache.org/repos/dist/release/cloudstack/KEYSVote will be open
for (at least) 72 hours.For sanity in tallying the vote, can PMC members
please be sure to indicate "(binding)" with their vote?[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

I will work with community members to provide convenience packaging over
the next few days.
The documentation repo will be updated as we move along.



--
Daan

rohit.ya...@shapeblue.com 
www.shapeblue.com
3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK
@shapeblue