Re: [PROPOSAL] Update the 4.20.0.0 release schedule

[Suresh Anaparti]

Hi João Jandre,

I think, it's better to do 4.19.1.0 before 4.20.0.0, and schedule 4.20.0.0 
release a month or two after 4.19.1.0 release. Considering the 4.19.1.0 
timelines proposed [1], you can target 4.20.0.0 in Q3, around Aug end (or early 
Sept). Please let me know your thoughts.

[1] https://lists.apache.org/thread/fo8s9qzh625c4fk8rgzjhpdn9kfgoqsp


Regards,
Suresh

From: João Jandre 
Date: Monday, 6 May 2024 at 7:37 PM
To: d...@cloudstack.apache.org , 
users@cloudstack.apache.org 
Subject: [PROPOSAL] Update the 4.20.0.0 release schedule
Hi all,

Regarding the original 4.20.0.0 release schedule proposed here:
https://lists.apache.org/thread/nyoddmwydz2t59hsfs7gf0vozlf7n434, I
would like to propose an update to it.

Considering that:
1. The community expended a lot of time working to fix the CVEs that
were recently found;
2. The community is busy with 4.19.1.0;
3. The original schedule would put the COCEU 2024 and the RC1 on the
same week;

I think we should postpone the 4.20.0.0 release for at least a month.
That being said, here is the updated schedule I propose:

- On the first week of July, we freeze the main branch. That means any
feature must be in by the last week of June. Only accept
critical/blocker issues until the second week of July.
- On the second week of July, cut 4.20.0.0 RC1 and further RCs if
necessary, start/conclude vote, and finish release work.

What are your thoughts?

Best Regards,
João Jandre

 

Re: [PROPOSE] RM for 4.19.1.0

[Suresh Anaparti]

Hi All,

It's been few months since the proposal, and we've fixed/tested/merged 139 
Issues and PRs in the 4.19.1.0 milestone [1]. Currently, we've 202 open items 
in the 4.19.1.0 milestone, tracked/triaged through the GitHub project 'Apache 
CloudStack 4.19.1' [2].

We can target for the "Must have" - 14 [3] and "Should have" - 23 [4] items. 
Feel free to work on "Good to have" / any other items in case anyone wants it 
in 4.19.1.0. Ping me (@sureshanaparti) on your issues and PRs, that are to be 
included in 4.19.1.0.

With that target, I propose the following timelines for 4.19.1.0 release, which 
is targeted for end of Q2 2024. Please let me know if you have any feedback, 
thoughts.

- (Ongoing) till Mid-Jun 2024, 16-Jun: Accept all bugs, issues, minor 
improvements allowed in LTS [5]
- (1 week) 17-Jun till 23-Jun: Accept only critical/blocker fixes if any, and 
stabilise 4.19 branch
- (1 week) from 24-Jun Onwards: Cut 4.19.1.0 RC1 (and further RCs if 
necessary), start/conclude vote, and finish release work

Looking forward for your support on bug fixes, reviews, tests, etc. Thanks.

[1] https://github.com/apache/cloudstack/milestone/31
[2] https://github.com/orgs/apache/projects/341
[3] 
https://github.com/orgs/apache/projects/341/views/1?filterQuery=repo%3Aapache%2Fcloudstack+milestone%3A4.19.1.0++priority%3A%22Must+have%22+-status%3ADone
[4] 
https://github.com/orgs/apache/projects/341/views/1?filterQuery=repo%3Aapache%2Fcloudstack+milestone%3A4.19.1.0+priority%3A%22Should+have%22+-status%3ADone
[5] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS


Regards,
Suresh

From: Suresh Anaparti 
Date: Monday, 12 February 2024 at 5:19 PM
To: d...@cloudstack.apache.org , 
users@cloudstack.apache.org 
Subject: [PROPOSE] RM for 4.19.1.0
Hi All,

CloudStack 4.19.0.0 is the latest LTS release. There are already some open 
issues [1]  and pull requests [2] targeted for 4.19.1.0 [3] release.

I'd like to propose and put myself forward as the release manager for 4.19.1.0 
if no objections there. Please ping me (@sureshanaparti) on GitHub, in case you 
want to include any Issue/PR in 4.19.1.0.

I propose to have a window of at least 8 weeks (2 months), which allows the 
community / users to test, use 4.19.0.0 and report any issues. We can aim to 
cut RC1 in Q2 2024 (maybe, sometime in May-2024). I'll propose the timeline 
details soon. I hope to have your support.

Please let me know if you have any thoughts/comments.

[1] 
https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.19.1.0
[2] 
https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.19.1.0+is%3Aopen
[3] https://github.com/apache/cloudstack/milestone/31


Regards,
Suresh

 

Re: new committer: Vishesh Jindal (vishesh)

[Suresh Anaparti]

Congratulations Vishesh!

Regards,
Suresh

From: Daan Hoogland 
Date: Monday, 26 February 2024 at 7:35 PM
To: users , dev 
Subject: new committer: Vishesh Jindal (vishesh)
users and devs,

The Project Management Committee (PMC) for Apache CloudStack
has invited Vishesh Jindal to become a committer and we are pleased
to announce that they have accepted.

Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.

Please join me in congratulating Vishesh.

--
on behalf of the PMC, Daan

 

[PROPOSE] RM for 4.19.1.0

[Suresh Anaparti]

Hi All,

CloudStack 4.19.0.0 is the latest LTS release. There are already some open 
issues [1]  and pull requests [2] targeted for 4.19.1.0 [3] release.

I'd like to propose and put myself forward as the release manager for 4.19.1.0 
if no objections there. Please ping me (@sureshanaparti) on GitHub, in case you 
want to include any Issue/PR in 4.19.1.0.

I propose to have a window of at least 8 weeks (2 months), which allows the 
community / users to test, use 4.19.0.0 and report any issues. We can aim to 
cut RC1 in Q2 2024 (maybe, sometime in May-2024). I'll propose the timeline 
details soon. I hope to have your support.

Please let me know if you have any thoughts/comments.

[1] 
https://github.com/apache/cloudstack/issues?q=is%3Aopen+is%3Aissue+milestone%3A4.19.1.0
[2] 
https://github.com/apache/cloudstack/pulls?q=is%3Apr+milestone%3A4.19.1.0+is%3Aopen
[3] https://github.com/apache/cloudstack/milestone/31


Regards,
Suresh

 

Re: [VOTE] Apache CloudStack 4.19.0.0 RC4

[Suresh Anaparti]

+1

Performed the below operations, on Advanced Zone and KVM hosts.

- Register Template / ISO
- Create Isolated / Shared network
- Deploy VM (on Isolated / Shared network)
- Deploy VM with DATA disk
- Deploy VM using ISO
- VM stop / start / reboot / reinstall / live migrate / storage migration 
operations
- Migrate system VM
- Take VM snapshot & Revert to snapshot
- Create / Attach / Detach Volume
- Take Volume Snapshot
- Create template from snapshot
- Create volume from snapshot
- Enable & Cancel maintenance on Host / Primary storage
- Random UI navigation/check

Regards,
Suresh

From: Abhishek Kumar 
Date: Monday, 29 January 2024 at 12:28 PM
To: users , d...@cloudstack.apache.org 

Cc: PMC 
Subject: [VOTE] Apache CloudStack 4.19.0.0 RC4
Hi All,

I've created a 4.19.0.0 release (RC4), with the following artifacts up for
a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.19.0.0-RC20240129T1021
Commit: 2746225b999612f156e421199e34ef8de98a3664

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.19.0.0/

PGP release keys (signed using 65518106473A09D7AF26B384A70BD2EAA74E2866):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

For testing purposes, I have uploaded the different distro packages to:
http://download.cloudstack.org/testing/4.19.0.0-RC4/

Since 4.16 the system VM template registration is no longer mandatory
before upgrading, however, it can be downloaded from here if needed:
https://download.cloudstack.org/systemvm/4.19/

The vote will be open for 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)

Regards,
Abhishek

 

Re: new PMC member Harikrishna Patnala

[Suresh Anaparti]

Congratulations Harikrishna!

Regards,
Suresh

From: Daan Hoogland 
Date: Monday, 15 January 2024 at 2:55 PM
To: dev , users 
Subject: new PMC member Harikrishna Patnala
users and dev,

The PMC have invited Harikrishna to join their ranks and he has
gracefully accepted. Please join me in congratulating Hari.

--
Daan

 

Re: New committer: Alexandre Mattioli

[Suresh Anaparti]

Congratulations Alex!

Regards,
Suresh

From: Nux 
Date: Thursday, 11 January 2024 at 3:58 AM
To: Dev , Users 
Subject: New committer: Alexandre Mattioli
All,

The Project Management Committee (PMC) for Apache CloudStack
has invited Alexandre Mattioli to become a committer and we are pleased
to announce that they have accepted.

Alex has been instrumental in many features present today in Cloudstack,
with a focus on networking and VMWare:
- IPv6 static routing
- Edge Zones
- Autoscaling with VR
- VNF appliances
- VMWare NSX support
- Tungsten Fabric / OpenSDN
- Backup & recovery framework
- VLAN trunking and security policies in ESX
and so on.


Please join me in congratulating Alex!

 

Re: [VOTE] Apache Cloudstack 4.17.0.0 RC4

[Suresh Anaparti]

+1

Continues tests from previous RC, covered VM & Volume operations with KVM, 
VMware hypervisors (in Advanced zone, on fresh installation).

 
Regards,
Suresh

On 31/05/22, 11:10 PM, "Nicolas Vazquez"  wrote:

Hi all,

I have created a 4.17.0.0 release (RCR) with the following artefacts up for 
testing and a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack/tree/4.17.0.0-RC20220531T1433
Commit: c56220fcf2348c7809331dcc266775f3d7130fe6

Source release (checksums and signatures are available at the same 
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.17.0.0/

PGP release keys (signed using 239A653975E13A0EEF5122A1656E1BCC8CB54F84):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 6th June 2022.

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)

Regards,
Nicolas Vazquez






 

Re: XenServer Agent is not coming up after upgrading from 7.1 to 8.2

[Suresh Anaparti]

Hi Vivek,

This discussion thread might provide you some inputs: 
https://lists.apache.org/thread/7q6yybm3qcms21qcd8945kvrygpr1v86 

Also, check the docs here: 
http://docs.cloudstack.apache.org/en/4.16.1.0/installguide/hypervisor/xenserver.html#upgrading-xenserver-versions,
 and see if you have missed any upgrade step.


Regards,
Suresh

On 01/06/22, 2:17 PM, "Vivek Kumar"  wrote:

Hello Guys,


We have recently upgraded our XenServer  from 7.1 to 8.2. We are using 
CloudStack 4.16.1. But after the upgradation my status of host is showing 
alert. I have gone through the logs getting below error. Can someone help me 
out for this.



—



rZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw=listSystemVms=json=3=2022-06-01T08%3A43%3A33%2B=x7KQg4LW2XPtTf%2BHHVn0Fm599xA%3D
2022-06-01 14:00:51,613 DEBUG [c.c.u.s.SSHCmdHelper] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Executing cmd: rm -f 
/opt/xensource/sm/hostvmstats.py 
/opt/xensource/bin/copy_vhd_to_secondarystorage.sh 
/opt/xensource/bin/copy_vhd_from_secondarystorage.sh 
/opt/xensource/bin/create_privatetemplate_from_snapshot.sh 
/opt/xensource/bin/vhd-util /opt/cloud/bin/copy_vhd_to_secondarystorage.sh 
/opt/cloud/bin/copy_vhd_from_secondarystorage.sh 
/opt/cloud/bin/create_privatetemplate_from_snapshot.sh /opt/cloud/bin/vhd-util
2022-06-01 14:00:52,750 DEBUG [c.c.a.ApiServlet] 
(qtp1850777594-19:ctx-5c391d12) (logid:fb2dbf4b) ===START===  172.31.29.44 -- 
GET  
listall=True=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw=listVpnConnections=json=3=2022-06-01T08%3A43%3A35%2B=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
2022-06-01 14:00:52,756 DEBUG [c.c.a.ApiServer] 
(qtp1850777594-19:ctx-5c391d12 ctx-9cd12123) (logid:fb2dbf4b) CIDRs from which 
account 'Acct[0d808973-19be-11eb-9555-005056961200-admin] -- Account {"id": 2, 
"name": "admin", "uuid": "0d808973-19be-11eb-9555-005056961200"}' is allowed to 
perform API calls: 0.0.0.0/0,::/0
2022-06-01 14:00:52,761 DEBUG [c.c.a.ApiServlet] 
(qtp1850777594-19:ctx-5c391d12 ctx-9cd12123 ctx-6326bb8c) (logid:fb2dbf4b) 
===END===  172.31.29.44 -- GET  
listall=True=W0EWPYRPQu51YPDQ8s_0b4wDDuSqrZCUKmFN6d4veFOrfeDI3u_9aDd-feyXbqPD-9Ua0Le6m9_Y7LciAVHmSw=listVpnConnections=json=3=2022-06-01T08%3A43%3A35%2B=TBKYjvgMLESFTna9iXeGTJdKtc0%3D
2022-06-01 14:00:52,862 INFO  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Host 172.31.21.5 
OpaqueRef:d1a2d70a-25bd-37b3-c581-2249ccf88fc0: Host 172.31.21.5 is already 
setup.
2022-06-01 14:00:52,868 WARN  [c.c.h.x.r.CitrixResourceBase] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) callHostPlugin failed for cmd: 
setIptables with args  due to The requested plugin could not be found.
2022-06-01 14:00:52,869 WARN  [c.c.h.x.r.w.x.CitrixSetupCommandWrapper] 
(DirectAgent-13:ctx-797e05c2) (logid:3256e16e) Unable to setup
com.cloud.utils.exception.CloudRuntimeException: callHostPlugin failed for 
cmd: setIptables with args  due to The requested plugin could not be found.
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.callHostPlugin(CitrixResourceBase.java:367)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.setIptables(CitrixResourceBase.java:4706)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:63)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixSetupCommandWrapper.execute(CitrixSetupCommandWrapper.java:45)
at 
com.cloud.hypervisor.xenserver.resource.wrapper.xenbase.CitrixRequestWrapper.execute(CitrixRequestWrapper.java:122)
at 
com.cloud.hypervisor.xenserver.resource.CitrixResourceBase.executeRequest(CitrixResourceBase.java:1758)
at 
com.cloud.agent.manager.DirectAgentAttache$Task.runInContext(DirectAgentAttache.java:315)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at 
java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
   

Re: NPE while listing Snapshots

[Suresh Anaparti]

Hi Antoine,

Thanks for the update, good to know that no more issues with snapshots listing.

The query result confirms why the snapshot location for the volume ids 110 and 
112 exists, these volumes are not yet removed.

Regards,
Suresh

From: Antoine Boucher 
Reply to: "users@cloudstack.apache.org" 
Date: Friday, 27 May 2022 at 10:09 PM
To: users 
Subject: Re: NPE while listing Snapshots

Hello Suresh,

I did your 2 commands on all 4 ids and I have no more issues on the listing the 
Snapshot from the webUI.

Here is the result of the query you requested:

mysql> SELECT id, uuid, name, account_id, pool_id, path, size, volume_type, 
state, removed FROM cloud.volumes WHERE id IN (110, 111, 112, 155);
+-+--+--++-+--+--+-+--+-+
| id  | uuid | name | account_id | pool_id 
| path | size | volume_type | state
| removed |
+-+--+--++-+--+--+-+--+-+
| 110 | 390198b4-45d4-425e-87c3-d0f11ef2ca11 | ROOT-109 | 16 |   4 
| 390198b4-45d4-425e-87c3-d0f11ef2ca11 |  42949672960 | ROOT| Ready
| NULL|
| 111 | NULL | ROOT-110 | 16 |   5 
| da585fd4-b10f-480b-9287-45ecb28b6355 |  85899345920 | DATADISK| Expunged 
| 2022-04-19 01:29:08 |
| 112 | 285140e4-555e-4cac-a2ec-afb4bd6921a8 | ROOT-111 | 16 |   3 
| 285140e4-555e-4cac-a2ec-afb4bd6921a8 |  53687091200 | ROOT| Ready
| NULL|
| 155 | da585fd4-b10f-480b-9287-45ecb28b6355 | ROOT-110 | 16 |  17 
| 4f29b0d2-a1e2-45bc-932a-31d67fd3c572 | 128849018880 | ROOT| Ready
| NULL|
+-+--+--++-+--+--+-+--+-+
4 rows in set (0.00 sec)


Thank you for all your help.

Regards,
Antoine

Antoine Boucher
antoi...@haltondc.com<mailto:antoi...@haltondc.com>
[o] +1-226-505-9734
www.haltondc.com<http://www.haltondc.com>

“Data security made simple and affordable”


[cid:image001.png@01D875B3.631C6270]




Confidentiality Warning: This message and any attachments are intended only for 
the use of the intended recipient(s), are confidential, and may be privileged. 
If you are not the intended recipient, you are hereby notified that any review, 
retransmission, conversion to hard copy, copying, circulation or other use of 
this message and any attachments is strictly prohibited. If you are not the 
intended recipient, please notify the sender immediately by return e-mail, and 
delete this message and any attachments from your system.





 

On May 20, 2022, at 4:56 AM, Suresh Anaparti 
mailto:suresh.anapa...@shapeblue.com>> wrote:

Hi Antoine,

Thanks for sharing these details. The delete snapshot cmd failed with NPE, as 
the underlying primary storage doesn't exists.

Usually, when a snapshot is deleted, the backed up snapshot file is removed 
from the secondary storage, the status in the cloud.snapshots table for that 
snaphshot is marked as Destroyed, and the state in the cloud.snapshot_store_ref 
table marked as Destroyed for the entries of that snapshot (both, for 
store_role Primary and Image). Later, the storage garbage collector (when 
enabled), sets the removed date in cloud.snapshots table and removes the 
entries in cloud.snapshot_store_ref table.

You can manually update the DB with the same behavior, first try with one 
snapshot (117) and if no issues, apply it to others (109,127,138).

Sample sqls for snapshot id=117 below.

- UPDATE cloud.snapshots SET status = 'Destroyed', removed = now() WHERE id = 
117;

- DELETE FROM cloud.snapshot_store_ref WHERE snapshot_id = 117;


'111' corresponds to volume id, in the snapshot location 
'snapshots/16/111/66210b31-7445-4586-89ea-52a37f5b1ab5'. I see the record with 
volume id 111 is expunged (migrated to new id) from the email thread, not sure 
about volume ids 110 and 112. What's the output of the sql below.

- SELECT id, uuid, name, account_id, pool_id, path, size, volume_type, state, 
removed FROM cloud.volumes WHERE id IN (110, 111, 112, 155);


Regards,
Suresh

On 17/05/22, 4:36 AM, "Antoine Boucher" 
mailto:antoi...@haltondc.com>> wrote:

Hi Suresh,

Here ids the logs of Cmk delete snapshot id=117 and similar for id=109,127,138


2022-05-16 18:18:49,667 DEBUG [c.c.a.ApiServer] 
(qtp515715487-147449:ctx-9470efda ctx-7b642401) (logid:dc836839) CIDRs from 
which account 'Acct[2cee75f9-8bc4-11ec-9c43-001e67fd4838-admin] -- Account 
{"id": 2, "name": "admin&q

Re: Palette Sidebar Gone.

[Suresh Anaparti]

Good, thanks for the update.

Regards,
Suresh

From: Rafael del Valle 
Reply to: Rafael del Valle 
Date: Monday, 23 May 2022 at 4:51 PM
To: "users@cloudstack.apache.org" 
Cc: Suresh Anaparti 
Subject: Re: Palette Sidebar Gone.

Ahh,

The setting is there, and it is true.

Actually this installation is an upgrade.

I tried several reloads with shift and control pressed, and eventually it came. 
I think it was due to browser cache.

Thanks.
R.



On Mon, 2022-05-23 01:09 PM, Suresh Anaparti  
wrote:
Hi,

You can enable / disable it using the UI property 'allowSettingTheme' in 
config.json (can be located at the path /etc/cloudstack/management/ in the 
management server). I think, by default, it is true and shows the settings 
icon/page customization view.

Check with the sample cmds below, in the management server. Refresh (/reopen) 
the browser after the property is updated.

- to check the property 'allowSettingTheme' set:
grep "allowSettingTheme" /etc/cloudstack/management/config.json

- to enable the customization view: (check the output from the above cmd, and 
use it to search and replace)
sed -i 's/"allowSettingTheme": false/"allowSettingTheme": true/g' 
/etc/cloudstack/management/config.json

- to disable the customization view:
sed -i 's/"allowSettingTheme": true/"allowSettingTheme": false/g' 
/etc/cloudstack/management/config.json


Regards,
Suresh

On 23/05/22, 12:21 PM, "rva...@privaz.io.INVALID" 
<mailto:%22rva...@privaz.io.invalid%22%20%3crva...@privaz.io.INVALID%3e>
 wrote:

​Hi!

I upgraded 2 cloudstack installations to 4.16.1 from 4.15.2

However, only one of them is showing the UI Side Panel for Palette 
customization. !? I have no idea why, and I did not do anything to enable or 
disable it that I am aware of.

How do I turn the sidebar palette on?

I really like the dark mode, by the way.

R.




 

Re: ACS 4.16.1 Adding a Zone

[Suresh Anaparti]

Hi,

It seems some issue with the 'mount' permissions for the user. Are you able to 
manually mount with the same user account?

 
Regards,
Suresh

On 23/05/22, 3:51 PM, "Rafael del Valle"  wrote:

Hi!

I added a new zone to an ACS 4.16.1 with its own NFS server.

All is green in the UI, but the secondary storage vm is not starting.

I see nfs errors in the logs, and I suspect the error is related to the 
SystemVM not been in the new zone secondary storage:

com.cloud.exception.StorageUnavailableException: Resource [StoragePool:6] 
is unreachable: Unable to create 
Vol[271|vm=227|ROOT]:com.cloud.utils.exception.CloudRuntimeException: 
org.libvirt.LibvirtException: internal error: Child process (/bin/mount 
10.71.0.102:/export/secon
dary/template/tmpl/1/209 /mnt/e6706577-0d39-356c-a016-757d32dd4cfa) 
unexpected exit status 32: mount.nfs: Operation not permitted

I have checked nfs connectivity between hosts and server in new zone and it 
works.

I wonder how does the SystemVM get there, in the first place. Because when 
Installing ACS, or for the first zone, there was an specific step.

​What could be going wrong?

R.


 

Re: Palette Sidebar Gone.

[Suresh Anaparti]

Hi,

You can enable / disable it using the UI property 'allowSettingTheme' in 
config.json (can be located at the path /etc/cloudstack/management/ in the 
management server). I think, by default, it is true and shows the settings 
icon/page customization view.

Check with the sample cmds below, in the management server. Refresh (/reopen) 
the browser after the property is updated.

- to check the property 'allowSettingTheme' set:
grep "allowSettingTheme" /etc/cloudstack/management/config.json

- to enable the customization view: (check the output from the above cmd, and 
use it to search and replace)
sed -i 's/"allowSettingTheme": false/"allowSettingTheme": true/g' 
/etc/cloudstack/management/config.json

- to disable the customization view:
sed -i 's/"allowSettingTheme": true/"allowSettingTheme": false/g' 
/etc/cloudstack/management/config.json
 

Regards,
Suresh

On 23/05/22, 12:21 PM, "rva...@privaz.io.INVALID"  
wrote:

​Hi!

I upgraded 2 cloudstack installations to 4.16.1 from 4.15.2

However, only one of them is showing the UI Side Panel for Palette 
customization. !?  I have no idea why, and I did not do anything to enable or 
disable it that I am aware of.

How do I turn the sidebar palette on?

I really like the dark mode, by the way.

R.


 

Re: NPE while listing Snapshots

[Suresh Anaparti]

.java:186)
at 
org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:215)
at com.sun.proxy.$Proxy218.deleteSnapshot(Unknown Source)
at 
org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd.execute(DeleteSnapshotCmd.java:103)
at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
at 
com.cloud.api.ApiAsyncJobDispatcher.runJob(ApiAsyncJobDispatcher.java:108)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.runInContext(AsyncJobManagerImpl.java:620)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
at 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
at 
org.apache.cloudstack.framework.jobs.impl.AsyncJobManagerImpl$5.run(AsyncJobManagerImpl.java:568)
at 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
2022-05-16 18:18:49,748 INFO  [o.a.c.f.j.i.AsyncJobMonitor] 
(API-Job-Executor-204:ctx-1a4cbdc0 job-2964) (logid:e6172481) Remove job-2964 
from job monitoring
2022-05-16 18:18:50,692 DEBUG [c.c.a.ApiServlet] 
(qtp515715487-147221:ctx-4c1cd6c0) (logid:3652b6cf) ===START===  
0:0:0:0:0:0:0:1 -- GET  
command=queryAsyncJobResult=e6172481-968c-4ee4-993e-a9851af91c29=json=zLfGQdrCq6kxldkzrnAxYZ8HWQE
2022-05-16 18:18:50,706 DEBUG [c.c.a.ApiServer] 
(qtp515715487-147221:ctx-4c1cd6c0 ctx-9cbca8dc) (logid:3652b6cf) CIDRs from 
which account 'Acct[2cee75f9-8bc4-11ec-9c43-001e67fd4838-admin] -- Account 
{"id": 2, "name": "admin", "uuid": "2cee75f9-8bc4-11ec-9c43-001e67fd4838"}' is 
allowed to perform API calls: 0.0.0.0/0,::/0
2022-05-16 18:18:50,723 DEBUG [c.c.a.ApiServlet] 
(qtp515715487-147221:ctx-4c1cd6c0 ctx-9cbca8dc) (logid:3652b6cf) ===END===  
0:0:0:0:0:0:0:1 -- GET  
command=queryAsyncJobResult=e6172481-968c-4ee4-993e-a9851af91c29=json=zLfGQdrCq6kxldkzrnAxYZ8HWQE

My snapshot.backup.to.secondary is configured to ‘true’

The snapshot location 
'snapshots/16/111/66210b31-7445-4586-89ea-52a37f5b1ab5’ for id=117 no longer 
exist. All of the concerned snapshots reference 'snapshots/16/111/...' for 
location but but directory 111 no longer exist.  110 and 112 exists.

    Regards,
    Antoine



Antoine Boucher
antoi...@haltondc.com
[o] +1-226-505-9734
www.haltondc.com




 

> On May 13, 2022, at 9:18 AM, Suresh Anaparti  
> wrote:
> 
> Hi Antoine,
>  
> What is the error in the management server logs while deleting the 
‘BackedUp’ snapshots? Can you share the log if possible.
>  
> Are these snapshots backed up to secondary storage as well (and what’s 
the config ‘snapshot.backup.to.secondary’ value when taking snapshot )? If yes, 
can you find the snapshot files at the install_path there? You can check the 
install_path details in cloud.snapshot_store_ref  table with volume_id: 155 and 
store_role: Image.
>  
>  
> Regards,
> Suresh
>  
> 
>   
>   
> From: Antoine Boucher mailto:antoi...@haltondc.com>>
> Reply to: "users@cloudstack.apache.org 
<mailto:users@cloudstack.apache.org>" mailto:users@cloudstack.apache.org>>
> Date: Wednesday, 11 May 2022 at 9:15 PM
> To: users 
> Subject: Re: NPE while listing Snapshots
>  
> Too fast id=146 also failed
>  
> {
>   "accountid": "2cee75f9-8bc4-11ec-9c43-001e67fd4838",
>   "cmd": 
"org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd",
>   "completed": "2022-05-11T11:43:01-0400",
>   "created": "2022-05-11T11:38:00-0400",
>   "jobid": "0bd30e5c-2e61-4988-8152-36835b791769",
>   "jobinstanceid": "875d0298-6ed7-43fc-a468-da6042388ac0",
>   "jobinstancetype": "Snapshot",
>   "jobprocstatus": 0,
>   "jobresult": {
> "errorcode": 530,
> "errortext": "Failed 

Re: NPE while listing Snapshots

[Suresh Anaparti]

---+--+---+--+-+-+---+
| id  | uuid | name | 
status| path | created | removed | location_type |
+-+--+--+---+--+-+-+---+
| 101 | 13870bbd-d7d7-4664-a22f-f09c80a56d41 | TS01_ROOT-110_20220414054855 | 
Destroyed | NULL | 2022-04-14 05:48:55 | NULL| NULL  |
| 109 | 77d84bf6-f601-44a6-a239-821f735a7f48 | TS01_ROOT-110_20220415054855 | 
BackedUp  | NULL | 2022-04-15 05:48:55 | NULL| NULL  |
| 117 | 7db02f43-a9d8-4c73-905a-1524d90f570a | TS01_ROOT-110_20220416054855 | 
BackedUp  | NULL | 2022-04-16 05:48:55 | NULL| NULL  |
| 127 | 47288ab9-2da2-40f2-98e3-9ced3f8e87df | TS01_ROOT-110_20220417054855 | 
BackedUp  | NULL | 2022-04-17 05:48:55 | NULL| NULL  |
| 138 | e9639f4a-fa09-4698-849b-572011045993 | TS01_ROOT-110_20220418054855 | 
BackedUp  | NULL | 2022-04-18 05:48:55 | NULL| NULL  |
| 146 | 875d0298-6ed7-43fc-a468-da6042388ac0 | TS01_ROOT-110_20220419054747 | 
BackedUp  | NULL | 2022-04-19 05:47:47 | NULL| NULL  |
| 154 | 0122c9b3-a9f8-473f-a8d7-6e69ba77265b | TS01_ROOT-110_20220420054748 | 
Destroyed | NULL | 2022-04-20 05:47:48 | NULL| NULL  |
| 157 | fe2248c6-aa80-4e9f-b539-7f495f1ff39f | Manual - Apr 20  | 
Destroyed | NULL | 2022-04-21 01:50:16 | NULL| NULL  |
| 163 | 32923ad7-cbe3-4708-95d8-23eca921d711 | TS01_ROOT-110_20220421054817 | 
Destroyed | NULL | 2022-04-21 05:48:17 | NULL| NULL  |
| 172 | 6e03ea90-e8b0-4405-aed6-7bd17a40de57 | TS01_ROOT-110_20220422054933 | 
Destroyed | NULL | 2022-04-22 05:49:33 | NULL| NULL  |
| 181 | 9059a26a-0e4e-4d46-95f2-b0a9236ba90a | TS01_ROOT-110_20220423054933 | 
Destroyed | NULL | 2022-04-23 05:49:33 | NULL| NULL  |
| 193 | c9828cbc-f282-4dfe-b4cf-9df792c522c2 | TS01_ROOT-110_20220424054934 | 
BackedUp  | NULL | 2022-04-24 05:49:34 | NULL| NULL  |
| 207 | 2e5dfd48-c4de-45ff-bbe1-4cf0d90bb698 | TS01_ROOT-110_20220425054934 | 
Destroyed | NULL | 2022-04-25 05:49:34 | NULL| NULL  |
| 217 | 99d9d9ff-44ae-41a9-9761-f722b370c01c | TS01_ROOT-110_20220426054934 | 
Destroyed | NULL | 2022-04-26 05:49:34 | NULL| NULL  |
| 227 | 1df14a7b-ba56-4d26-aeb4-c79d4de978fc | TS01_ROOT-110_20220427054934 | 
BackedUp  | NULL | 2022-04-27 05:49:34 | NULL| NULL  |
| 237 | 657479e0-3587-4a72-a8c8-bd7dff54a5e4 | TS01_ROOT-110_20220428054934 | 
BackedUp  | NULL | 2022-04-28 05:49:34 | NULL| NULL  |
| 248 | 2ef0b539-be01-4b0c-9fa5-5fc9c60a6a96 | TS01_ROOT-110_20220429054935 | 
BackedUp  | NULL | 2022-04-29 05:49:35 | NULL| NULL  |
| 257 | 8ab75270-8e3d-471e-8e4a-8d5f3cbc6bc1 | TS01_ROOT-110_20220430054935 | 
BackedUp  | NULL | 2022-04-30 05:49:35 | NULL| NULL  |
| 259 | a1e77bec-8fc7-457f-b0a5-961c339487f7 | TS01_ROOT-110_20220430060935 | 
Destroyed | NULL | 2022-04-30 06:09:35 | 2022-05-09 20:02:38 | NULL  |
| 313 | 8ad0c04a-1d74-4d51-8223-a6aa3a82d62c | TS01_ROOT-110_20220509015742 | 
BackedUp  | NULL | 2022-05-09 01:57:42 | NULL| NULL  |
| 327 | 0f5e9366-747f-4a34-bec4-1fd31c461ac3 | TS01_ROOT-110_20220509170242 | 
BackedUp  | NULL | 2022-05-09 17:02:42 | NULL| NULL  |
+-+--+--+---+--+-+-+---+

How would you suggest I resolve the issue moving forward?

I tried the following with error…

(nimbus)  > delete snapshot id=109
{
  "accountid": "2cee75f9-8bc4-11ec-9c43-001e67fd4838",
  "cmd": "org.apache.cloudstack.api.command.user.snapshot.DeleteSnapshotCmd",
  "completed": "2022-05-11T11:32:08-0400",
  "created": "2022-05-11T11:32:08-0400",
  "jobid": "29661b2b-46c5-42bd-9974-d1a226f3fe68",
  "jobinstanceid": "77d84bf6-f601-44a6-a239-821f735a7f48",
  "jobinstancetype": "Snapshot",
  "jobprocstatus": 0,
  "jobresult": {
"errorcode": 530,
"errortext": "Command failed due to Internal Server Error"
  },
  "jobresultcode": 530,
  "jobresulttype": "object",
  "jobstatus": 2,
  "userid": "2cefb708-8bc4-11ec-9c43-001e67fd4838"
}
 Error: async API failed for job 29661b2b-46c5-42bd-9974-d1a226f3fe68


Deleting some table rows in the right sequence?

Same issue with id=117 to

Re: [VOTE] Apache CloudStack 4.17.0.0 RC2

[Suresh Anaparti]

-1

Agree with Rohit, it's better to continue testing this week. Found an issue 
with change disk offering, created issue here: 
https://github.com/apache/cloudstack/issues/6372

 
Regards,
Suresh

On 11/05/22, 5:37 PM, "Rohit Yadav"  wrote:

-1 (binding)

There are a few issues found in RC2 testing, a few of them are to do with 
systemvmtemplate patching [1] which is a blocker. I suggest we continue testing 
this week and cut RC3 next week to give users/testers more time to test and 
report issues as 4.17 is a major release.

I found an issue with UI which appears to be a build issue, in the first 
RC2 pkgs for testing systemvmtemplate weren't included and in the next re-build 
the UI elements were not following right css which were fixed with the correct 
packaging builds (with no changes in the code).

[1] https://github.com/apache/cloudstack/pull/6371


Regards.


From: Wei ZHOU 
Sent: Monday, May 9, 2022 20:33
To: users 
Subject: [VOTE] Apache CloudStack 4.17.0.0 RC2

+1 (binding)

Tested vm/volume lifecycles on ubuntu 20 and vmware 70u3
Tested IPv6 static routing
Tested kubernetes cluster with k8s 1.24.0. (found a bug and fixed it by
https://github.com/apache/cloudstack/pull/6368, but I think it is not a
blocker/critical issue for RC2)

-Wei

On Sun, 8 May 2022 at 05:53, Nicolas Vazquez 
wrote:

> Hi all,
>
> I have created a 4.17.0.0 release (RC2) with the following artefacts up
> for testing and a vote:
>
> Git Branch and Commit SH:
> https://github.com/apache/cloudstack/tree/4.17.0.0-RC20220507T2233
> Commit: 6a36c59d341fb76fc6f9c90762ba5ca924e8d048
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.17.0.0/
>
> PGP release keys (signed using 239A653975E13A0EEF5122A1656E1BCC8CB54F84):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> For testing purposes, I have uploaded convenience packages to:
> https://download.cloudstack.org/testing/4.17.0.0-RC2/
>
> The system VM template can be downloaded from here if needed:
> https://download.cloudstack.org/systemvm/4.17
>
> The vote will be open until 11th May 2022.
>
> 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)
>
> Regards,
> Nicolas Vazquez
>
>
>
>





 

Re: Report issue

[Suresh Anaparti]

Hi Mariusz,

You can check the details in the documentation here: 
http://docs.cloudstack.apache.org/en/4.16.1.0/adminguide/ui.html#basic-ui-customization


Regards,
Suresh

From: Mariusz Wojtarek 
Reply to: "users@cloudstack.apache.org" 
Date: Wednesday, 11 May 2022 at 6:19 PM
To: "users@cloudstack.apache.org" 
Subject: Report issue

Hi,

Where can i change the Report ISSUE link, it’s under the footer, at the bottom 
of the page, I use CloudStack 4.16.1.0 



 



Mariusz Wojtarek
Administrator iT
P: 22 335 28 00  
E: mailto:mariusz.wojta...@support-online.pl
http://www.support-online.pl/
Poleczki 23 | 02-822 Warszawa 





Support OnLine Sp. z o.o., ul. Poleczki 23, 02-822 Warszawa, NIP: 
951-20-32-692, Regon: 017431965, KRS: 078497,
XIII Wydział Gospodarczy Krajowego Rejestru Sądowego w Warszawie, Kapitał 
zakładowy: 50 000 PLN - opłacony w pełnej wysokości.
W przypadku podania w ramach niniejszej korespondencji Państwa danych 
osobowych, prosimy zapoznać się z następującą informacją 
https://www.support-online.pl/dane-osobowe
In case any of your private data was included within this conversation, please 
consult this website https://www.support-online.pl/en/personal-data 


 

Re: Using public cloud images as templates

[Suresh Anaparti]

Hi Felipe,

Thanks for sharing the libvirt / qemu versions. May be, some compatibility 
issue with these versions. You can try with other cloud images there.

 
Regards,
Suresh

On 05/05/22, 4:45 PM, "Felipe Polanco"  wrote:

Hi,

# virsh version
Compiled against library: libvirt 6.0.0
Using library: libvirt 6.0.0
Using API: QEMU 6.0.0
Running hypervisor: QEMU 4.2.1

On Thu, May 5, 2022 at 6:00 AM Suresh Anaparti <
suresh.anapa...@shapeblue.com> wrote:

> Hi Felipe,
>
> I've tried with cloudimg-amd64.img (as raw template) in hypervisor with
> libvirt 4.5.0 / qemu 1.5.3, on cloudstack 4.16.1, and it is booting fine.
>
> Got the same issue with images cloudimg-amd64-disk-kvm.img,
> cloudimg-ppc64el.img (as raw templates) in hypervisor with libvirt 4.5.0 /
> qemu v1.5.3 and v2.12.0. Not sure of the issue yet, with these images.
>
> What is your the libvirt / qemu versions in hypervisor (check with 'virsh
> version' cmd)
>
>
> Regards,
> Suresh
>
> On 04/05/22, 8:50 PM, "Felipe Polanco"  wrote:
>
> Hello,
>
> Is it possible to use cloud images from popular Linux OS like Ubuntu 
or
> Centos?
>
> I have added them as templates but none of the boot on a new instance,
> the
> bootloader is stuck at "Booting from hard disk..."
>
> URL:
> https://cloud-images.ubuntu.com/focal/current/
> Using the amd64-disk-kvm.img as qcow2 template.
>
> Thanks,
>
>
>
>
>


 

Re: Using public cloud images as templates

[Suresh Anaparti]

Hi Felipe,

I've tried with cloudimg-amd64.img (as raw template) in hypervisor with libvirt 
4.5.0 / qemu 1.5.3, on cloudstack 4.16.1, and it is booting fine.

Got the same issue with images cloudimg-amd64-disk-kvm.img, 
cloudimg-ppc64el.img (as raw templates) in hypervisor with libvirt 4.5.0 / qemu 
v1.5.3 and v2.12.0. Not sure of the issue yet, with these images.

What is your the libvirt / qemu versions in hypervisor (check with 'virsh 
version' cmd)

 
Regards,
Suresh

On 04/05/22, 8:50 PM, "Felipe Polanco"  wrote:

Hello,

Is it possible to use cloud images from popular Linux OS like Ubuntu or
Centos?

I have added them as templates but none of the boot on a new instance, the
bootloader is stuck at "Booting from hard disk..."

URL:
https://cloud-images.ubuntu.com/focal/current/
Using the amd64-disk-kvm.img as qcow2 template.

Thanks,


 

Re: No longer able to see any "Snapshots"

[Suresh Anaparti]

Hi Antoine,

It seems, there are recurring snapshots scheduled on volume id: 
390198b4-45d4-425e-87c3-d0f11ef2ca11. Is that volume still exists and in Ready 
state (Is it listed in UI? else, check with listVolumes API). Also, check the 
snapshot policies for that volume (from UI if listed, else with API 
listSnapshotPolicies using volumeid param) and remove them (from UI, or with 
API deleteSnapshotPolicies using id from the listSnapshotPolicies API response).


Regards,
Suresh

From: Antoine Boucher 
Reply to: "users@cloudstack.apache.org" 
Date: Sunday, 1 May 2022 at 5:04 AM
To: users 
Subject: Re: No longer able to see any "Snapshots"

Hi Suresh,

Thank you for your reply, Yes this is the local storage of a Hiost that was 
removed.  It is strange since all VM where migrated before. The host was then 
put in maintenance and eventually removed.

What would be the fix?  Removing the snapshot record(s)?

Is this also related?  I’m seeing this events every 5 minutes,..



ERROR<https://nimbus.haltondc.com:8443/client/#/event/d8ae2255-0f91-4041-9a19-ecd81bb38244>
SNAPSHOT.CREATE
Created
Error while creating entity for allocating snapshot
system<https://nimbus.haltondc.com:8443/client/#/accountuser?username=system=088d13e7-8bc4-11ec-9c43-001e67fd4838>
system<https://nimbus.haltondc.com:8443/client/#/account?name=system=088d13e7-8bc4-11ec-9c43-001e67fd4838=true>
ROOT<https://nimbus.haltondc.com:8443/client/#/domain/088d13e7-8bc4-11ec-9c43-001e67fd4838>
30 Apr 2022 19:32:41
INFO<https://nimbus.haltondc.com:8443/client/#/event/50ea9c36-745d-4a44-935e-551f6294e439>
SNAPSHOT.CREATE
Scheduled
creating snapshot for volume Id:390198b4-45d4-425e-87c3-d0f11ef2ca11
system<https://nimbus.haltondc.com:8443/client/#/accountuser?username=system=80dc2363-7b2b-4614-a02f-b0e5a1782b11>
Networth-Abrams<https://nimbus.haltondc.com:8443/client/#/account?name=Networth-Abrams=80dc2363-7b2b-4614-a02f-b0e5a1782b11=true>
Networth<https://nimbus.haltondc.com:8443/client/#/domain/80dc2363-7b2b-4614-a02f-b0e5a1782b11>
30 Apr 2022 19:32:41
ERROR<https://nimbus.haltondc.com:8443/client/#/event/40bd9bc2-5899-49ff-9833-fb29dea7c0ba>
SNAPSHOT.CREATE
Created
Error while creating entity for allocating snapshot
system<https://nimbus.haltondc.com:8443/client/#/accountuser?username=system=088d13e7-8bc4-11ec-9c43-001e67fd4838>
system<https://nimbus.haltondc.com:8443/client/#/account?name=system=088d13e7-8bc4-11ec-9c43-001e67fd4838=true>
ROOT<https://nimbus.haltondc.com:8443/client/#/domain/088d13e7-8bc4-11ec-9c43-001e67fd4838>
30 Apr 2022 19:27:41
INFO<https://nimbus.haltondc.com:8443/client/#/event/1dce5b57-4dbe-4201-b04a-6dfa63363014>
SNAPSHOT.CREATE
Scheduled
creating snapshot for volume Id:390198b4-45d4-425e-87c3-d0f11ef2ca11
system<https://nimbus.haltondc.com:8443/client/#/accountuser?username=system=80dc2363-7b2b-4614-a02f-b0e5a1782b11>
Networth-Abrams<https://nimbus.haltondc.com:8443/client/#/account?name=Networth-Abrams=80dc2363-7b2b-4614-a02f-b0e5a1782b11=true>
Networth<https://nimbus.haltondc.com:8443/client/#/domain/80dc2363-7b2b-4614-a02f-b0e5a1782b11>
30 Apr 2022 19:27:41
ERROR<https://nimbus.haltondc.com:8443/client/#/event/3c443f26-0e93-4f9e-9d69-192794c1efec>
SNAPSHOT.CREATE
Created
Error while creating entity for allocating snapshot
system<https://nimbus.haltondc.com:8443/client/#/accountuser?username=system=088d13e7-8bc4-11ec-9c43-001e67fd4838>
system<https://nimbus.haltondc.com:8443/client/#/account?name=system=088d13e7-8bc4-11ec-9c43-001e67fd4838=true>
ROOT<https://nimbus.haltondc.com:8443/client/#/domain/088d13e7-8bc4-11ec-9c43-001e67fd4838>
30 Apr 2022 19:22:41
INFO<https://nimbus.haltondc.com:8443/client/#/event/ca2e5d1a-9ad1-4f9f-9d5a-45f3e9ec42ef>
SNAPSHOT.CREATE
Scheduled
creating snapshot for volume Id:390198b4-45d4-425e-87c3-d0f11ef2ca11
system<https://nimbus.haltondc.com:8443/client/#/accountuser?username=system=80dc2363-7b2b-4614-a02f-b0e5a1782b11>
Networth-Abrams<https://nimbus.haltondc.com:8443/client/#/account?name=Networth-Abrams=80dc2363-7b2b-4614-a02f-b0e5a1782b11=true>
Networth<https://nimbus.haltondc.com:8443/client/#/domain/80dc2363-7b2b-4614-a02f-b0e5a1782b11>
30 Apr 2022 19:22:41




Regards,
Antoine



Antoine Boucher
antoi...@haltondc.com<mailto:antoi...@haltondc.com>
[o] +1-226-505-9734
www.haltondc.com<http://www.haltondc.com>

“Data security made simple and affordable”


[cid:image001.png@01D85FB6.402DF570]




Confidentiality Warning: This message and any attachments are intended only for 
the use of the intended recipient(s), are confidential, and may be privileged. 
If you are not the intended recipient, you are hereby notified that any review, 
retransmission, conversion to hard copy, copying, circulation or other use of 
this message and any attachments is strictly prohibited. If you are not the 
intended recip

Re: Secondary Storage timeout for ISO registration

[Suresh Anaparti]

Hi Peter,

Did you notice any error in secondary storage VM logs when downloading the ISO? 
Are you facing this issue with a specific ISO? Can you reach that ISO url using 
curl / wget for secondary storage VM?

Also, try to register ISO with different url, and see if you notice the same 
issue. From the code, I see the timeout is 30s, and if the download cmd doesn't 
progress, it'll fail with timeout error.


Regards,
Suresh

On 04/05/22, 2:19 AM, "Peter Stine"  wrote:

Hello all,

I am running CloudStack 4.16.1.0 on a Ubuntu 20.04 system. I am also using 
a Ceph array for primary storage with an nfs share also located on it. The 
management servers are also in a cluster.
I am having issues downloading new ISOs. When I enter the information for 
the ISO, it says it registers successfully, but then after a short wait shows 
"Timeout waiting for response from storage host". I can still create VMs from 
templates in secondary storage and live migrate VMs. 

Any thoughts on what might be causing this?

I checked the firewall and iptables to see if anything was being blocked 
and it does not appear so.

Here is the management log: 
https://gist.github.com/PeterS-gd/3baf67c2fbe9dc984246055e85fdd23c
iptables for both: 
https://gist.github.com/PeterS-gd/269070bc663a47f1eb67788cd1fcbe56

NB: This was working before. There was some network trouble, but I 
restarted the servers one by one and that cleared up most of the issues except 
for this one.

Thanks!

Peter Stine



 

Re: No longer able to see any "Snapshots"

[Suresh Anaparti]

Hi Antoine,

The NPE error seems to be due to the primary storage with id '5', when checking 
for snapshot revertible or not during list snapshots cmd. Is that primary 
storage removed? Can you check with sql below.

SELECT name, uuid, pool_type, scope, created, removed FROM cloud.storage_pool 
WHERE id = 5


I think, the account/user might not have the permissions to list all snapshots. 
You can check the account / domain details in snapshots table.

 
Regards,
Suresh

On 21/04/22, 6:50 PM, "Antoine Boucher"  wrote:

Thank you Suresh, you will find my answers below, 



 

> On Apr 21, 2022, at 1:02 AM, Suresh Anaparti  
> wrote:
> 
> Hi Antoine,
> 
> What is the CloudStack version, where you see this issue.

Latest - 4.16.1


> When you noticed this issue, is it while listing snapshots for a 
particular volume, or all volumes? Try list snapshots from API/cmk as well.

This is a customer VM, the account may have hit its snapshot limit during a 
snapshot. 

cmk list snapshots > only lists 26 snapshots out of 62

cmk list snapshots volumeid= > Works for some volume ids, provides null 
result while the WebUI lists the correct snapshots for others and provides null 
results while show undefined error for one VM mentioned below


> 
> Also, Check the snapshots details for the volume (with issue) in the db, 
using the following sql queries.
> 
> 1. SELECT id, uuid, state, pool_id, path, size, removed FROM 
cloud.volumes WHERE name LIKE ''
> 

mysql> SELECT id, uuid, state, pool_id, path, size, removed FROM 
cloud.volumes WHERE name LIKE 'ROOT-110';

+-+--+--+-+--+-+-+
| id  | uuid | state| pool_id | path
 | size| removed |

+-+--+--+-+--+-+-+
| 111 | NULL | Expunged |   5 | 
da585fd4-b10f-480b-9287-45ecb28b6355 | 85899345920 | 2022-04-19 01:29:08 |
| 138 | da585fd4-b10f-480b-9287-45ecb28b6355 | Ready|   6 | 
04bd5d13-72ca-4240-93ce-ed1b015d3437 | 85899345920 | NULL|

+-+--+--+-+--+-+-+


> 2. SELECT id, uuid, name, status, path, created, removed, location_type 
FROM cloud.snapshots WHERE volume_id = ;

mysql> SELECT id, uuid, name, status, path, created, removed, location_type 
FROM cloud.snapshots WHERE volume_id = '138';

+-+--+--+---+--+-+-+---+
| id  | uuid | name 
| status| path | created | removed | location_type |

+-+--+--+---+--+-+-+---+
| 101 | 13870bbd-d7d7-4664-a22f-f09c80a56d41 | TS01_ROOT-110_20220414054855 
| Destroyed | NULL | 2022-04-14 05:48:55 | NULL| NULL  |
| 109 | 77d84bf6-f601-44a6-a239-821f735a7f48 | TS01_ROOT-110_20220415054855 
| BackedUp  | NULL | 2022-04-15 05:48:55 | NULL| NULL  |
| 117 | 7db02f43-a9d8-4c73-905a-1524d90f570a | TS01_ROOT-110_20220416054855 
| BackedUp  | NULL | 2022-04-16 05:48:55 | NULL| NULL  |
| 127 | 47288ab9-2da2-40f2-98e3-9ced3f8e87df | TS01_ROOT-110_20220417054855 
| BackedUp  | NULL | 2022-04-17 05:48:55 | NULL| NULL  |
| 138 | e9639f4a-fa09-4698-849b-572011045993 | TS01_ROOT-110_20220418054855 
| BackedUp  | NULL | 2022-04-18 05:48:55 | NULL| NULL  |
| 146 | 875d0298-6ed7-43fc-a468-da6042388ac0 | TS01_ROOT-110_20220419054747 
| BackedUp  | NULL | 2022-04-19 05:47:47 | NULL| NULL  |
| 154 | 0122c9b3-a9f8-473f-a8d7-6e69ba77265b | TS01_ROOT-110_20220420054748 
| BackedUp  | NULL | 2022-04-20 05:47:48 | NULL| NULL  |
| 157 | fe2248c6-aa80-4e9f-b539-7f495f1ff39f | Manual - Apr 20  
| BackedUp  | NULL | 2022-04-21 01:50:16 | NULL| NULL  |
| 163 | 32923ad7-cbe3-4708-95d8-23eca921d711 | TS01_ROOT-110_20220421054817 
| BackedUp  | NULL | 2022-04-21 05:48:17 | NULL| NULL  |

+-+--+--+---+--+-+-+---+


> 
> 3. SELECT volume_id, store_id, store_role, install_path, size, state FROM 
cloud.snapshot_store_ref WHERE snapshot_id = 
> 

mysql> SELECT volume_id, store_id, store_role, i

Re: No longer able to see any "Snapshots"

[Suresh Anaparti]

Hi Antoine,

What is the CloudStack version, where you see this issue. When you noticed this 
issue, is it while listing snapshots for a particular volume, or all volumes? 
Try list snapshots from API/cmk as well.

Also, Check the snapshots details for the volume (with issue) in the db, using 
the following sql queries.

1. SELECT id, uuid, state, pool_id, path, size, removed FROM cloud.volumes 
WHERE name LIKE ''

2. SELECT id, uuid, name, status, path, created, removed, location_type FROM 
cloud.snapshots WHERE volume_id = ;

3. SELECT volume_id, store_id, store_role, install_path, size, state FROM 
cloud.snapshot_store_ref WHERE snapshot_id = 

 
Regards,
Suresh

On 21/04/22, 8:45 AM, "Antoine Boucher"  wrote:

Unfortunately I spoke too fast. The list is back but listing the snapshots 
of the volume with issue still show a blank list with error “undefined”. 


 

On Apr 20, 2022, at 23:11, Antoine Boucher  wrote:

I was able to recover from the situation by forcing a snapshot on the 
volume with issue.

On Apr 20, 2022, at 22:00, Antoine Boucher  wrote:

I pin-pointed the volume with the issue by going through all volumes and 
clicking the “view snapshot"


> On Apr 20, 2022, at 9:35 PM, Antoine Boucher  
wrote:
> 
> I’m no longer able to see my list of snapshots (storage > snapshots), 
instead I see a small popup window with the word “undefined" on an empty list 
snapshot list.
> 
> Has anyone seen this issue?  I restart and rebooted the Management server 
but no resolution. 
> 
> Here are my logs:
> 
> 2022-04-20 21:17:02,428 DEBUG [c.c.a.ApiServlet] 
(qtp515715487-292:ctx-a220f915) (logid:624389ae) ===START===  10.101.254.1 -- 
GET  listall=true=1=20=listSnapshots=json
> 2022-04-20 21:17:02,439 DEBUG [c.c.a.ApiServer] 
(qtp515715487-292:ctx-a220f915 ctx-c0fe9f91) (logid:624389ae) CIDRs from which 
account 'Acct[2cee75f9-8bc4-11ec-9c43-001e67fd4838-admin] -- Account {"id": 2, 
"name": "admin", "uuid": "2cee75f9-8bc4-11ec-9c43-001e67fd4838"}' is allowed to 
perform API calls: 0.0.0.0/0,::/0
> 2022-04-20 21:17:02,675 ERROR [c.c.a.ApiServer] 
(qtp515715487-292:ctx-a220f915 ctx-c0fe9f91) (logid:624389ae) unhandled 
exception executing api command: [Ljava.lang.String;@42fa8f7d
> java.lang.NullPointerException
>   at 
org.apache.cloudstack.storage.snapshot.StorageSystemSnapshotStrategy.canHandle(StorageSystemSnapshotStrategy.java:985)
>   at 
org.apache.cloudstack.storage.helper.StorageStrategyFactoryImpl$3.canHandle(StorageStrategyFactoryImpl.java:72)
>   at 
org.apache.cloudstack.storage.helper.StorageStrategyFactoryImpl$3.canHandle(StorageStrategyFactoryImpl.java:69)
>   at 
org.apache.cloudstack.storage.helper.StorageStrategyFactoryImpl.bestMatch(StorageStrategyFactoryImpl.java:95)
>   at 
org.apache.cloudstack.storage.helper.StorageStrategyFactoryImpl.getSnapshotStrategy(StorageStrategyFactoryImpl.java:69)
>   at 
org.apache.cloudstack.storage.snapshot.SnapshotObject.isRevertable(SnapshotObject.java:156)
>   at 
com.cloud.api.ApiResponseHelper.createSnapshotResponse(ApiResponseHelper.java:591)
>   at 
org.apache.cloudstack.api.command.user.snapshot.ListSnapshotsCmd.execute(ListSnapshotsCmd.java:117)
>   at com.cloud.api.ApiDispatcher.dispatch(ApiDispatcher.java:156)
>   at com.cloud.api.ApiServer.queueCommand(ApiServer.java:772)
>   at com.cloud.api.ApiServer.handleRequest(ApiServer.java:596)
>   at com.cloud.api.ApiServlet.processRequestInContext(ApiServlet.java:321)
>   at com.cloud.api.ApiServlet$1.run(ApiServlet.java:134)
>   at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
>   at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
>   at 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
>   at com.cloud.api.ApiServlet.processRequest(ApiServlet.java:131)
>   at com.cloud.api.ApiServlet.doGet(ApiServlet.java:93)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:645)
>   at javax.servlet.http.HttpServlet.service(HttpServlet.java:750)
>   at 
org.eclipse.jetty.servlet.ServletHolder$NotAsync.service(ServletHolder.java:1450)
>   at 
org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:799)
>   at 
org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:550)
>   at 
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:143)
>   at 
org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:600)
>   at 
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:127)
>   at 
org.eclipse.jetty.server.handler.ScopedHandler.nextHandle(ScopedHandler.java:235)
>   at 
org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:1624)
>   at 

Re: Remove Primary storage

[Suresh Anaparti]

Hi Biswajit,

You can enable maintenance for the primary storage, and then remove it (when it 
is in maintenance mode).

 
Regards,
Suresh

On 20/04/22, 7:59 AM, "Biswajit Banerjee"  
wrote:

Hi

I am looking for removing one  primary storage when i have multiple 
primary storage mapped to ACS 4.15.1

Any guidance ?

TIA

Biswajit



 

Re: extraconfig

[Suresh Anaparti]

Thanks Piotr, for confirming it. 

 
Regards,
Suresh

On 21/03/22, 4:55 PM, "Piotr Pisz"  wrote:

Yes, that's exactly it.

Only modifying Constrained VM settings doesn't work, the rest work fine.

Regards,
Piotr


-Original Message-
From: Suresh Anaparti  
Sent: Monday, March 21, 2022 10:34 AM
To: users@cloudstack.apache.org; pi...@piszki.pl
Subject: Re: extraconfig

Hi Piotr,

Similar issue was logged here: 
https://github.com/apache/cloudstack/issues/6131 and fixed recently. Is it the 
same issue?


Regards,
Suresh

On 19/03/22, 2:19 PM, "Piotr Pisz"  wrote:

Hi,



In CS 4.16.1 I am not able to add any additional settings in the VM. It 
ends
with the following message:





Request Failed (530)

Failed to update VM, due to: The cpu speed of this offering
id:84225c4c-1cbd-4439-ac17-333299e560b2 is not customizable. This is
predefined in the template.



The message is independent of the compute profile type.

Could someone check if can add new settings to vm w cs 4.16.1?





Regards,

Piotr








 

Re: extraconfig

[Suresh Anaparti]

Hi,

I'll see if I can update this in the release notes.


Regards,
Suresh

On 21/03/22, 3:56 PM, "vas...@gmx.de"  wrote:

@suresh

Just for understanding in this context:
The issue you linked basically stated that if one upgrades to CS 4.16.1 all
VMs created using a custome constrained offering can't
- be updated / migrated to another service offering
- be edited with new settings
- be changed as new values for existing settings can't be changed

So basically the whole functionality of adding & changeing settings as well
as migrateing to "open" service offerings as a "work aroind" is broken for
these kind of VMs?
Sounds like a quiet big issue tbh which might be werth to mention in the
actual release notes?

Am Mo., 21. März 2022 um 10:34 Uhr schrieb Suresh Anaparti <
suresh.anapa...@shapeblue.com>:

> Hi Piotr,
>
> Similar issue was logged here:
> https://github.com/apache/cloudstack/issues/6131 and fixed recently. Is
> it the same issue?
>
>
> Regards,
> Suresh
>
> On 19/03/22, 2:19 PM, "Piotr Pisz"  wrote:
>
> Hi,
>
>
>
> In CS 4.16.1 I am not able to add any additional settings in the VM.
> It ends
> with the following message:
>
>
>
>
>
> Request Failed (530)
>
> Failed to update VM, due to: The cpu speed of this offering
> id:84225c4c-1cbd-4439-ac17-333299e560b2 is not customizable. This is
> predefined in the template.
>
>
>
> The message is independent of the compute profile type.
>
> Could someone check if can add new settings to vm w cs 4.16.1?
>
>
>
>
>
> Regards,
>
> Piotr
>
>
>
>
>
>


 

Re: extraconfig

[Suresh Anaparti]

Hi Piotr,

Similar issue was logged here: https://github.com/apache/cloudstack/issues/6131 
and fixed recently. Is it the same issue?

 
Regards,
Suresh

On 19/03/22, 2:19 PM, "Piotr Pisz"  wrote:

Hi,



In CS 4.16.1 I am not able to add any additional settings in the VM. It ends
with the following message:





Request Failed (530)

Failed to update VM, due to: The cpu speed of this offering
id:84225c4c-1cbd-4439-ac17-333299e560b2 is not customizable. This is
predefined in the template.



The message is independent of the compute profile type.

Could someone check if can add new settings to vm w cs 4.16.1?





Regards,

Piotr



 

Re: [!!Mass Mail]Re: Build CS from Sources

[Suresh Anaparti]

Hi Evgeniy,

Can you re-try with java version 11.

 
Regards,
Suresh

On 14/03/22, 5:47 PM, "Дикевич Евгений Александрович" 
 wrote:

Thx, Slavka!

But when I try command `mvn clean install -DskipTests` in tools directory 
now I have new error:

[INFO] --- exec-maven-plugin:1.2.1:exec (compile) @ cloud-apidoc ---
Error: A JNI error has occurred, please check your installation and try 
again
Exception in thread "main" java.lang.UnsupportedClassVersionError: 
com/cloud/api/doc/ApiXmlDocWriter has been compiled by a more recent version of 
the Java Runtime (class file version 55.0), this version of the Java Runtime 
only recognizes class file versions up to 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
at 
java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:473)
at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at 
sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:601)
[INFO] 

[INFO] Reactor Summary:
[INFO]
[INFO] Apache CloudStack Developer Tools . SUCCESS [1.058s]
[INFO] Apache CloudStack apidocs . FAILURE [4.473s]
[INFO] Apache CloudStack marvin .. SKIPPED
[INFO] Apache CloudStack DevCloud4 ... SKIPPED
[INFO] Apache CloudStack DevCloud-KVM  SKIPPED
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Total time: 5.715s
[INFO] Finished at: Mon Mar 14 15:14:59 MSK 2022
[INFO] Final Memory: 36M/154M
[INFO] 

[ERROR] Failed to execute goal 
org.codehaus.mojo:exec-maven-plugin:1.2.1:exec (compile) on project 
cloud-apidoc: Command execution failed. Process exited with an error: 1 (Exit 
value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, 
please read the following articles:
[ERROR] [Help 1] 
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the 
command
[ERROR]   mvn  -rf :cloud-apidoc





-Original Message-
From: Slavka Peleva [mailto:slav...@storpool.com.INVALID]
Sent: Monday, March 14, 2022 1:53 PM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Build CS from Sources

Hi Evgeniy,

I don't tell that this solution is perfect, but I had this problem once and 
those steps helped me to solve it:
- In the main CS directory, execute - `mvn clean install -DskipTests` (this 
will download all required dependencies and build the CS modules locally. I use 
the option `-DskipTests` because in this case, you don't want to run all tests )
- when the build finishes you should go to the `tools` directory and 
execute the same command `mvn clean install -DskipTests` it could fail like 
this:

[INFO] Apache CloudStack Developer Tools .. SUCCESS [
 0.781 s]
[INFO] Apache CloudStack apidocs .. SUCCESS [
10.257 s]
[INFO] Apache CloudStack marvin ... SUCCESS [
 3.650 s]
[INFO] Apache CloudStack DevCloud4  FAILURE [
 0.059 s]
[INFO] Apache CloudStack DevCloud-KVM . SKIPPED

But you can proceed after that with packaging.

Best regards,
Slavka



 

On Mon, Mar 14, 2022 at 11:12 AM Дикевич Евгений Александрович < 
evgeniy.dikev...@becloud.by> wrote:

> Hi all!
>
> Does somebody try to build CS from sources?
> Try It with official documentation and on one step I get ERROR:
>
> Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2.1:exec
> (compile) on project cloud-apidoc: Command execution failed. Process
> exited with an error: 1 (Exit 

Re: cant run vm after upgrade to 4.16.1

[Suresh Anaparti]

Hi,

Can you share the hypervisor (and its version) details.


Regards,
Suresh

On 10/03/22, 3:26 PM, "Piotr Pisz"  wrote:

Hi,



This is a problem with offering, before upgrade the CPU Mhz was in turbo 
mode, now I have to change the clock speed to normal mode in offering and 
everything works.

Has anything changed in the way we interpret the CPU clock speed?



Regards,

Piotr







From: Wei ZHOU  
Sent: Thursday, March 10, 2022 10:55 AM
To: users ; pi...@piszki.pl
Subject: Re: cant run vm after upgrade to 4.16.1



Hi,



Please check the cpu speed of service offering, which should not be bigger 
than the cpu frequency of physical hosts.



-Wei




 

On Thu, 10 Mar 2022 at 10:23, Piotr Pisz mailto:pi...@piszki.pl> > wrote:

Hi,

I have upgraded to cs 4.16.1 in the lab and I have a problem, I am not able
to run any vm, I get the following message:



Cannot deploy the VM to specified host 1; host has cpu capability? false,
host has capacity? True



How could this message be interpreted?

The upgrade was successful, there are no errors in the management log when
starting vm.



Regards,

Piotr

[RESULT][VOTE] Apache CloudStack 4.16.1.0 (RC2)

[Suresh Anaparti]

Hi All,

The vote for Apache CloudStack 4.16.1.0 *passes* with
7 PMC + 4 non-PMC votes.

+1 (PMC / binding)
7 persons (Boris, Nux, Rohit, Nicolas, Wei, Daan, Andrija)

+1 (non binding)
4 persons (Vladi, Harikrishna, Suresh, Slavka)

0
none

-1
none

Thank you everyone for participating.

I will now prepare the release announcement to go out after 24-48 hours to give 
the mirrors time to catch up.

 
Regards,
Suresh

On 03/03/22, 3:56 PM, "Andrija Panic"  wrote:

+1 (binding)

Tested upgrading 4.13.1 with multiple hypervisors, automatic-systemVM
template registration; basic VM/network lifecycle, Advanced Zone.

On Wed, 2 Mar 2022 at 16:48, Slavka Peleva 
wrote:

> +1 Tested on KVM (CentOS7) with NFS/Ceph/StorPool a few storage operations
> with a Basic Zone.
>
> Best regards,
> Slavka
>
> On Wed, Mar 2, 2022 at 4:02 PM Suresh Anaparti <
> suresh.anapa...@shapeblue.com> wrote:
>
> > +1
> >
> > Adding my vote as well. Manually tested various VM, Volume and Network
> > operations in Advanced Zone, on fresh and upgrade(from 4.15.2)
> environments
> > (MS: CentOS 7 + Hypervisor: CentOS 7 KVM). Also, verified the automated
> > smoke tests results in environments with MS on CentOS 7 and Hypervisors 
-
> > CentOS 7 KVM, XenServer 7.1, and VMware 6.5u2. No issues noticed.
> >
> >
> > Regards,
> > Suresh
> >
> > On 02/03/22, 6:03 PM, "Daan Hoogland"  wrote:
> >
> > +1
> >
> >
> >
> >
> 
 

> On Wed, Mar 2, 2022 at 1:29 PM Wei ZHOU  wrote:
> >
> > > +1 (binding)
> > >
> > > tested vm lifecycle on vmware70u3.
> > >
> > > -Wei
> > >
> > > On Fri, 25 Feb 2022 at 16:09, Suresh Anaparti <
> > > suresh.anapa...@shapeblue.com>
> > > wrote:
> > >
> > > > Hi All,
> > > >
> > > > I have created a 4.16.1.0 release (RC2), with the following
> > artifacts up
> > > > for testing and a vote:
> > > >
> > > > Git Branch and Commit SHA:
> > > >
> https://github.com/apache/cloudstack/tree/4.16.1.0-RC20220225T1901
> > > > Commit: cad9332082a1f85eedc30cf547ae28224be170c2
> > > >
> > > > Source release (checksums and signatures are available at the
> same
> > > > location):
> > > > https://dist.apache.org/repos/dist/dev/cloudstack/4.16.1.0/
> > > >
> > > > PGP release keys (signed using
> > D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
> > > > https://dist.apache.org/repos/dist/release/cloudstack/KEYS
> > > >
> > > > The vote will be open until 2nd March 2022.
> > > >
> > > > 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)
> > > >
> > > > For users convenience, the packages from this release candidate
> > (RC2) and
> > > > 4.16.1 systemvm templates are available here:
> > > > https://download.cloudstack.org/testing/4.16.1.0-RC2/
> > > > https://download.cloudstack.org/systemvm/4.16/
> > > >
> > > > Documentation is not published yet, but the following may be
> > referenced
> > > > for upgrade related tests:
> > > > (there's a new 4.16.1 systemvm template to be registered prior 
to
> > > upgrade)
> > > >
> > > >
> > >
> >
> 
https://github.com/apache/cloudstack-documentation/tree/4.16/source/upgrading/upgrade
> > > >
> > > > NOTES on the issues fixed in this RC2 release:
> > > >
> > > > (these do *NOT* require a full retest if you were testing RC1
> > already -
> > > > just if you were affected by these issues):
> > > > - https://github.com/apache/cloudstack/issues/6017 (regression
> in
> > > > register template form
> > > > when select/unselect check boxes using space in keyboard)
> > > > - https://github.com/apache/cloudstack/issues/6026 (affects
> > volumes on
> > > > managed storages when
> > > > stopping or migrating a VM)
> > > > - https://github.com/apache/cloudstack/issues/6038 (regression
> in
> > SSVM
> > > > scaling down behavior,
> > > > new config 'secstorage.vm.auto.scale.down' added to control
> > scaling down)
> > > >
> > > >
> > > > Regards,
> > > > Suresh
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> >
> >
> > --
> > Daan
> >
> >
>


-- 

Andrija Panić

Re: Procedure to remove management server

[Suresh Anaparti]

Hi Ricardo,

The management server remove option is currently not available from webui.

You can manually remove by updating cloud.mshost table (using below sql) for 
that management server host.
UPDATE cloud.mshost SET state='Down', removed=NOW() WHERE id=
 
Regards,
Suresh

On 02/03/22, 4:26 AM, "Ricardo Pertuz"  wrote:

Hi,

What is the best option to remove management servers from webui not longer 
used?

Thanks!

Regards


 

[VOTE] Apache CloudStack 4.16.1.0 (RC2)

[Suresh Anaparti]

Hi All,

I have created a 4.16.1.0 release (RC2), with the following artifacts up for 
testing and a vote:

Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.16.1.0-RC20220225T1901
Commit: cad9332082a1f85eedc30cf547ae28224be170c2

Source release (checksums and signatures are available at the same location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.16.1.0/

PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 2nd March 2022.

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)

For users convenience, the packages from this release candidate (RC2) and
4.16.1 systemvm templates are available here:
https://download.cloudstack.org/testing/4.16.1.0-RC2/
https://download.cloudstack.org/systemvm/4.16/

Documentation is not published yet, but the following may be referenced for 
upgrade related tests:
(there's a new 4.16.1 systemvm template to be registered prior to upgrade)
https://github.com/apache/cloudstack-documentation/tree/4.16/source/upgrading/upgrade

NOTES on the issues fixed in this RC2 release:

(these do *NOT* require a full retest if you were testing RC1 already -
just if you were affected by these issues):
- https://github.com/apache/cloudstack/issues/6017 (regression in register 
template form
when select/unselect check boxes using space in keyboard)
- https://github.com/apache/cloudstack/issues/6026 (affects volumes on managed 
storages when
stopping or migrating a VM)
- https://github.com/apache/cloudstack/issues/6038 (regression in SSVM scaling 
down behavior,
new config 'secstorage.vm.auto.scale.down' added to control scaling down)

 
Regards,
Suresh


 

Re: [VOTE] Apache CloudStack 4.16.1.0 (RC1)

[Suresh Anaparti]

Hi All,

There is a bug [1] reported, impacting the migrate and stop VM operations in 
KVM and this seems to be a blocker for most of the storage drivers. I'll cut 
another RC shortly as soon as there is a working fix. So, let's stop the voting 
process for RC1.

Thanks for your testing effort on RC1. Your work is not in-vain. Please, 
re-test the specific issue/patches (to be shared in RC2 thread).

[1] https://github.com/apache/cloudstack/issues/6026

 
Regards,
Suresh

On 21/02/22, 4:35 PM, "Daan Hoogland"  wrote:

+1 (binding)
checked keys
started network
registered several templates
started VMs based on those templates
also I was involved with the merging and triaging of the PRs for this
release and am quite confident we have a nice set of fixes here ;)


On Fri, Feb 18, 2022 at 5:10 PM Suresh Anaparti <
suresh.anapa...@shapeblue.com> wrote:

> Hi All,
>
> I have created a 4.16.1.0 release (RC1), with the following artifacts up
> for testing and a vote:
>
> Git Branch and Commit SHA:
> https://github.com/apache/cloudstack/tree/4.16.1.0-RC20220218T1649
> Commit: 711f0412967b34ea5284b403e4fcba759b1288b7
>
> Source release (checksums and signatures are available at the same
> location):
> https://dist.apache.org/repos/dist/dev/cloudstack/4.16.1.0/
>
> PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
> https://dist.apache.org/repos/dist/release/cloudstack/KEYS
>
> The vote will be open until 24th February 2022.
>
> 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)
>
> For users convenience, the packages from this release candidate (RC1) and
> 4.16.1 systemvm templates are available here:
> https://download.cloudstack.org/testing/4.16.1.0-RC1/
> https://download.cloudstack.org/systemvm/4.16/
>
> Documentation is not published yet, but the following may be referenced
> for upgrade related tests:
> (there's a new 4.16.1 systemvm template to be registered prior to upgrade)
>
> 
https://github.com/apache/cloudstack-documentation/tree/4.16/source/upgrading/upgrade
>
>
> Regards,
> Suresh
>
>
>
>
>

-- 
Daan


 

[VOTE] Apache CloudStack 4.16.1.0 (RC1)

[Suresh Anaparti]

Hi All,

I have created a 4.16.1.0 release (RC1), with the following artifacts up for 
testing and a vote:

Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.16.1.0-RC20220218T1649
Commit: 711f0412967b34ea5284b403e4fcba759b1288b7

Source release (checksums and signatures are available at the same location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.16.1.0/

PGP release keys (signed using D6E0581ECF8A2FBE3FF6B3C9D7CEAE3A9E71D0AA):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 24th February 2022.

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)

For users convenience, the packages from this release candidate (RC1) and
4.16.1 systemvm templates are available here:
https://download.cloudstack.org/testing/4.16.1.0-RC1/
https://download.cloudstack.org/systemvm/4.16/

Documentation is not published yet, but the following may be referenced for 
upgrade related tests:
(there's a new 4.16.1 systemvm template to be registered prior to upgrade)
https://github.com/apache/cloudstack-documentation/tree/4.16/source/upgrading/upgrade

 
Regards,
Suresh


 

Re: Disable Storage Pool behaviour

[Suresh Anaparti]

Hi Mevludin,

When you disable a primary storage pool, that pool is not considered for any 
further storage allocation when deploying instances, creating volumes.


Regards,
Suresh

On 16/02/22, 2:33 PM, "Mevludin Blazevic"  wrote:

Hi all,

what happens in detail if I disable a Primary Storage pool using the 
"Disable Storage Pool" button? I've found a Wiki document relating to 
ACS v4.6 but I don't know if it has any changes related to the current 
ACS version.

Regards

Mevludin


-- 
Diese E-Mail wurde von Avast Antivirus-Software auf Viren geprüft.
https://www.avast.com/antivirus



 

Re: 4.16.1.0 release

[Suresh Anaparti]

Hi All,

There are no outstanding items on the 4.16.1 milestone [1] currently. I'll 
start the stabilisation work from tomorrow, only blocker issues will be 
accepted. I would like to cut RC1 between 17-21 Feb 2022 depending on the 4.16 
branch stability. Please let me know if there are any questions or concerns.

[1] https://github.com/apache/cloudstack/milestone/22

 
Regards,
Suresh

On 07/02/22, 7:30 PM, "Suresh Anaparti"  wrote:

Hi All,

There are about 30 open items (and about 200+ merged/closed) in the 
4.16.1.0 milestone [1] currently.

Considering the open items and the previously proposed timelines, I would 
like to propose 4.16 branch soft freeze around 16th Feb 2022, thereafter only 
blocker and critical fixes will be allowed with the RC1 cut during End-Feb 2022 
depending on branch stability. Any questions / concerns?

[1] https://github.com/apache/cloudstack/milestone/22


Regards,
Suresh




 

4.16.1.0 release

[Suresh Anaparti]

Hi All,

There are about 30 open items (and about 200+ merged/closed) in the 4.16.1.0 
milestone [1] currently.

Considering the open items and the previously proposed timelines, I would like 
to propose 4.16 branch soft freeze around 16th Feb 2022, thereafter only 
blocker and critical fixes will be allowed with the RC1 cut during End-Feb 2022 
depending on branch stability. Any questions / concerns?

[1] https://github.com/apache/cloudstack/milestone/22


Regards,
Suresh



 

Re: Add vsphere host

[Suresh Anaparti]

Hi Alessandro,

When the vCenter cluster is added to CloudStack, all the hosts in that cluster 
are auto discovered and added. If any host is added to the vCenter cluster 
after creating the cluster in CloudStack, you can add that host from the UI or 
addHost API/cmk.


Regards,
Suresh

On 01/02/22, 8:19 PM, "Alireza Eskandari"  wrote:

Hi
First add the host to the cluster in vcenter.
Then try to add it from cloudstack ui.


On Tue, Feb 1, 2022, 6:15 PM Alessandro Caviglione 
wrote:

> Hi,
> in past we've had a XenServer cluster in Cloudstack and adding a node was
> quite simple.
> Now we're managing a 2 node vSphere cluster and we need to add an
> additional host to this cluster.
> In the documentation I see:
>
> Adding a Host (vSphere)
> <
> 
https://docs.cloudstack.apache.org/en/latest/installguide/configuration.html#adding-a-host-vsphere
> >
>
> For vSphere servers, we recommend creating the cluster of hosts in vCenter
> and then adding the entire cluster to CloudStack. See Add Cluster: 
vSphere.
>
>
> So what?
>
> Someone can explain me how to add an host to vsphere/cloudstack cluster?
>
>
> Thank you
>


 

Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0

[Suresh Anaparti]

+1

Performed some VM and Network operations on KVM in ACS 4.16.0, works fine.

I've noticed same issue as Rohit, first run failed to create firewall rules and 
the management server log indicates that the router is still starting (so need 
to wait a while before applying the firewall rules).


Regards,
Suresh

On 31/01/22, 1:12 PM, "Pearl d'Silva"  wrote:

+1

Did some basic lifecycle operations on a VM, network - such as creation, 
update and destroy, adding secondary IP to a VM.
Performed the operations as an admin and a user.
Did similar operations in a project as a user. Also attempted resetting the 
VMs SSH key.
Encountered a small issue with respect to adding a secondary IP to a NIC 
for a VM deployed in a project, but I wouldn't categorize it as a blocker and 
can be addressed in the next release.


Thanks,
Pearl


From: Daan Hoogland 
Sent: Friday, January 28, 2022 9:29 PM
To: dev 
Cc: users@cloudstack.apache.org 
Subject: Re: [VOTE] Release Apache CloudStack Terraform Provider v0.4.0

+1 (binding)

performed similar tests as Rohit but in a dual zone and with a vpc in one
of the zones. Two different configurations one with one zone and one with
both. destroy went fine ;) in the vpc firewall rules would not create. I am
not sure this is a known issue, but the error message is clear, so I'm not
calling it a bug:

"Unable to create firewall rule for the IP address ID=204 as IP is not
associated with any network and no networkId is passed in"

The only weird thing is that the network is not an allowed parameter.


On Fri, Jan 28, 2022 at 9:55 AM Rohit Yadav 
wrote:

> +1 (binding)
>
> I checked the source tarball checksum and gpg signature, and using the RC1
> build was able to test a simple VM deployment in a zone in an isolated
> network with some firewall rules applied, against a KVM based ACS 4.16.0.0
> env.
>
> (note: in my testing, in the first run the firewall application met with
> some failure but on second try of terraform apply it worked, see run log
> below)
>
> Source tarball verification:
> gpg: Signature made Wed Jan 19 15:33:18 2022 IST
> gpg:using RSA key 1031D6946F8A7C4B0C3E9EEFAEA5313845ADC482
> gpg: Good signature from "Harikrishna Patnala (github gpg) <
> harikrishna.patn...@gmail.com>" [unknown]
> gpg: WARNING: This key is not certified with a trusted signature!
> gpg:  There is no indication that the signature belongs to the
> owner.
> Primary key fingerprint: 1031 D694 6F8A 7C4B 0C3E  9EEF AEA5 3138 45AD 
C482
>
> Run log for reference:
>
> # terraform apply
>
> Terraform used the selected providers to generate the following execution
> plan. Resource actions are indicated with the
> following symbols:
>   + create
>
> Terraform will perform the following actions:
>
>   # cloudstack_egress_firewall.default will be created
>   + resource "cloudstack_egress_firewall" "default" {
>   + id  = (known after apply)
>   + managed = false
>   + network_id  = (known after apply)
>   + parallelism = 2
>
>   + rule {
>   + cidr_list = [
>   + "10.200.0.0/24",
> ]
>   + icmp_code = (known after apply)
>   + icmp_type = (known after apply)
>   + ports = [
>   + "21",
>   + "22",
>   + "443",
>   + "80",
> ]
>   + protocol  = "tcp"
>   + uuids = (known after apply)
> }
> }
>
>   # cloudstack_firewall.default will be created
>   + resource "cloudstack_firewall" "default" {
>   + id= (known after apply)
>   + ip_address_id = (known after apply)
>   + managed   = false
>   + parallelism   = 2
>
>   + rule {
>   + cidr_list = [
>   + "0.0.0.0/0",
> ]
>   + icmp_code = (known after apply)
>   + icmp_type = (known after apply)
>   + ports = [
>   + "22",
>   + "443",
>   + "80",
> ]
>   + protocol  = "tcp"
>   + uuids = (known after apply)
> }
> }
>
>   # cloudstack_instance.web will be created
>   + resource "cloudstack_instance" "web" {
>   + display_name = "VM1Test"
>   + expunge  = true
>   + group= (known after apply)
>   + id   = (known after apply)
>   + ip_address   = (known after apply)
>   + name = "VM1Test"
>   + network_id   = (known after apply)
>

Re: New zone in ACS 4.16 - Unable to add the external cluster

[Suresh Anaparti]

Hi Cristian,

Have you noticed the same issue as this: 
https://github.com/apache/cloudstack/issues/5732 (this issue is already fixed, 
and will be available in 4.16.1). If not, you can log a ticket. Thanks.


Regards,
Suresh

On 19/01/22, 12:48 PM, "Suresh Anaparti"  wrote:

Hi Cristian,

Thanks for the update. Can you log a ticket (with the UI problem you 
noticed) here: https://github.com/apache/cloudstack/issues.


Regards,
Suresh

On 19/01/22, 12:40 PM, "cristian.c@istream.today" 
 wrote:

Hi  Suresh,

I think you can ignore this, I removed the zone from UI and added again 
and works fine...  btw, at the step where you can add multiple physical 
networks, if I add more than 1 there is no way to click on "next button" is not 
working, tired multiple times. ( I had to add after I added the zone)

Regards,
Cristian


-Original Message-
From: Suresh Anaparti  
Sent: Tuesday, January 18, 2022 4:14 PM
To: users@cloudstack.apache.org
Subject: Re: New zone in ACS 4.16 - Unable to add the external cluster

Hi Cristian,

It seems server discoverer couldn't detect the hosts on the cluster in 
VMware DC. Can you check the management port group in the hosts is same as in 
the global setting 'vmware.management.portgroup', and traffic label configured 
in the zone is in sync with the virtual switch on the hosts.


Regards,
Suresh

On 18/01/22, 7:27 PM, "cristian.c@istream.today" 
 wrote:

Hi Suresh,

I just tested via API, same error, but something is strange in 
the log:

2022-01-18 08:44:21,900 INFO  [c.c.h.v.u.VmwareContext] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) New 
VmwareContext object, current outstanding count: 14
2022-01-18 08:44:21,904 ERROR [c.c.h.v.u.VmwareContext] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) Path 
element points to an un-existing inventory entity
2022-01-18 08:44:21,904 ERROR [c.c.h.v.m.VmwareManagerImpl] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Unable to find host from inventory path:
2022-01-18 08:44:21,906 INFO  [c.c.h.v.VmwareServerDiscoverer] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Found 0 hosts.
2022-01-18 08:44:21,906 ERROR [c.c.h.v.VmwareServerDiscoverer] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Unable to find host or cluster based on url:
2022-01-18 08:44:21,906 INFO  [c.c.h.v.u.VmwareContext] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Disconnecting VMware session
2022-01-18 08:44:21,908 WARN  [c.c.r.ResourceManagerImpl] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Unable to find the server resources at https://vmware-ams-002.domain.com
2022-01-18 08:44:21,909 INFO  [c.c.u.e.CSExceptionErrorCode] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Could not find exception: com.cloud.exception.DiscoveryException in error code 
list for exceptions
2022-01-18 08:44:21,918 WARN  [o.a.c.a.c.a.c.AddClusterCmd] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Exception:
com.cloud.exception.DiscoveryException: Unable to add the external 
cluster


I see " Unable to find host from inventory path:" but no path .

Regards,
Cristian

    -----Original Message-
From: Suresh Anaparti  
Sent: Tuesday, January 18, 2022 3:02 PM
To: users@cloudstack.apache.org
Subject: Re: New zone in ACS 4.16 - Unable to add the external 
cluster

Hi Cristian,

I'm not sure if this is a bug. Have you tried with api/cmk?

Can you share the complete log of zone creation. If possible, 
please create a ticket with details here: 
https://github.com/apache/cloudstack/issues.


Regards,
Suresh

On 18/01/22, 2:41 PM, "cristian.c@istream.today" 
 wrote:

Hello,



Is this a bug?   I'm trying to add a new ZONE in a upgraded 
cloudstack
environment but fails. I have already 4 active zones which are 
created long
time ago.



Unable to connect to Vmware vSphere server. service address:
vmware-ams-002.domain.com. java.lang.NumberFormatException: For 
input
string: "null"

2022-01-18 04:03:30,849 INFO  [c.c.h.v.u.VmwareContext]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) 
(logid:91c422ef)
Disconnecting VMware session

  

Re: New zone in ACS 4.16 - Unable to add the external cluster

[Suresh Anaparti]

Hi Cristian,

Thanks for the update. Can you log a ticket (with the UI problem you noticed) 
here: https://github.com/apache/cloudstack/issues.


Regards,
Suresh

On 19/01/22, 12:40 PM, "cristian.c@istream.today"  
wrote:

Hi  Suresh,

I think you can ignore this, I removed the zone from UI and added again and 
works fine...  btw, at the step where you can add multiple physical networks, 
if I add more than 1 there is no way to click on "next button" is not working, 
tired multiple times. ( I had to add after I added the zone)

Regards,
Cristian


-Original Message-----
From: Suresh Anaparti  
Sent: Tuesday, January 18, 2022 4:14 PM
To: users@cloudstack.apache.org
Subject: Re: New zone in ACS 4.16 - Unable to add the external cluster

Hi Cristian,

It seems server discoverer couldn't detect the hosts on the cluster in 
VMware DC. Can you check the management port group in the hosts is same as in 
the global setting 'vmware.management.portgroup', and traffic label configured 
in the zone is in sync with the virtual switch on the hosts.


Regards,
Suresh

On 18/01/22, 7:27 PM, "cristian.c@istream.today"  
wrote:

Hi Suresh,

I just tested via API, same error, but something is strange in the 
log:

2022-01-18 08:44:21,900 INFO  [c.c.h.v.u.VmwareContext] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) New 
VmwareContext object, current outstanding count: 14
2022-01-18 08:44:21,904 ERROR [c.c.h.v.u.VmwareContext] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) Path 
element points to an un-existing inventory entity
2022-01-18 08:44:21,904 ERROR [c.c.h.v.m.VmwareManagerImpl] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Unable to find host from inventory path:
2022-01-18 08:44:21,906 INFO  [c.c.h.v.VmwareServerDiscoverer] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Found 0 hosts.
2022-01-18 08:44:21,906 ERROR [c.c.h.v.VmwareServerDiscoverer] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Unable to find host or cluster based on url:
2022-01-18 08:44:21,906 INFO  [c.c.h.v.u.VmwareContext] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Disconnecting VMware session
2022-01-18 08:44:21,908 WARN  [c.c.r.ResourceManagerImpl] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Unable to find the server resources at https://vmware-ams-002.domain.com
2022-01-18 08:44:21,909 INFO  [c.c.u.e.CSExceptionErrorCode] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Could not find exception: com.cloud.exception.DiscoveryException in error code 
list for exceptions
2022-01-18 08:44:21,918 WARN  [o.a.c.a.c.a.c.AddClusterCmd] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Exception:
com.cloud.exception.DiscoveryException: Unable to add the external 
cluster


I see " Unable to find host from inventory path:" but no path .

Regards,
Cristian

-Original Message-
From: Suresh Anaparti  
Sent: Tuesday, January 18, 2022 3:02 PM
To: users@cloudstack.apache.org
Subject: Re: New zone in ACS 4.16 - Unable to add the external cluster

Hi Cristian,

I'm not sure if this is a bug. Have you tried with api/cmk?

Can you share the complete log of zone creation. If possible, please 
create a ticket with details here: https://github.com/apache/cloudstack/issues.


Regards,
Suresh

On 18/01/22, 2:41 PM, "cristian.c@istream.today" 
 wrote:

Hello,



Is this a bug?   I'm trying to add a new ZONE in a upgraded 
cloudstack
environment but fails. I have already 4 active zones which are 
created long
time ago.



Unable to connect to Vmware vSphere server. service address:
vmware-ams-002.domain.com. java.lang.NumberFormatException: For 
input
string: "null"

2022-01-18 04:03:30,849 INFO  [c.c.h.v.u.VmwareContext]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) (logid:91c422ef)
Disconnecting VMware session

2022-01-18 04:03:30,851 WARN  [c.c.r.ResourceManagerImpl]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) (logid:91c422ef) 
Unable to
find the server resources at
http://vmware-ams-002.domain.com/AMS-BR-01/SAO-01

2022-01-18 04:03:30,851 INFO  [c.c.u.e.CSExceptionErrorCode]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) (logid:91c422ef) 
Could not
find exception: com.cloud.exception.DiscoveryException in error 
code list

Re: New zone in ACS 4.16 - Unable to add the external cluster

[Suresh Anaparti]

Hi Cristian,

It seems server discoverer couldn't detect the hosts on the cluster in VMware 
DC. Can you check the management port group in the hosts is same as in the 
global setting 'vmware.management.portgroup', and traffic label configured in 
the zone is in sync with the virtual switch on the hosts.

 
Regards,
Suresh

On 18/01/22, 7:27 PM, "cristian.c@istream.today"  
wrote:

Hi Suresh,

I just tested via API, same error, but something is strange in the log:

2022-01-18 08:44:21,900 INFO  [c.c.h.v.u.VmwareContext] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) New 
VmwareContext object, current outstanding count: 14
2022-01-18 08:44:21,904 ERROR [c.c.h.v.u.VmwareContext] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) Path 
element points to an un-existing inventory entity
2022-01-18 08:44:21,904 ERROR [c.c.h.v.m.VmwareManagerImpl] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Unable to find host from inventory path:
2022-01-18 08:44:21,906 INFO  [c.c.h.v.VmwareServerDiscoverer] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Found 0 hosts.
2022-01-18 08:44:21,906 ERROR [c.c.h.v.VmwareServerDiscoverer] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Unable to find host or cluster based on url:
2022-01-18 08:44:21,906 INFO  [c.c.h.v.u.VmwareContext] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Disconnecting VMware session
2022-01-18 08:44:21,908 WARN  [c.c.r.ResourceManagerImpl] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Unable to find the server resources at https://vmware-ams-002.domain.com
2022-01-18 08:44:21,909 INFO  [c.c.u.e.CSExceptionErrorCode] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Could not find exception: com.cloud.exception.DiscoveryException in error code 
list for exceptions
2022-01-18 08:44:21,918 WARN  [o.a.c.a.c.a.c.AddClusterCmd] 
(qtp2053591126-20:ctx-3ffe2578 ctx-d0c69f6d ctx-5e23a0d3) (logid:812d3e06) 
Exception:
com.cloud.exception.DiscoveryException: Unable to add the external cluster


I see " Unable to find host from inventory path:" but no path .

Regards,
Cristian

-Original Message-----
From: Suresh Anaparti  
Sent: Tuesday, January 18, 2022 3:02 PM
To: users@cloudstack.apache.org
Subject: Re: New zone in ACS 4.16 - Unable to add the external cluster

Hi Cristian,

I'm not sure if this is a bug. Have you tried with api/cmk?

Can you share the complete log of zone creation. If possible, please create 
a ticket with details here: https://github.com/apache/cloudstack/issues.


Regards,
Suresh

On 18/01/22, 2:41 PM, "cristian.c@istream.today"  
wrote:

Hello,



Is this a bug?   I'm trying to add a new ZONE in a upgraded 
cloudstack
environment but fails. I have already 4 active zones which are created 
long
time ago.



Unable to connect to Vmware vSphere server. service address:
vmware-ams-002.domain.com. java.lang.NumberFormatException: For input
string: "null"

2022-01-18 04:03:30,849 INFO  [c.c.h.v.u.VmwareContext]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) (logid:91c422ef)
Disconnecting VMware session

2022-01-18 04:03:30,851 WARN  [c.c.r.ResourceManagerImpl]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) (logid:91c422ef) 
Unable to
find the server resources at
http://vmware-ams-002.domain.com/AMS-BR-01/SAO-01

2022-01-18 04:03:30,851 INFO  [c.c.u.e.CSExceptionErrorCode]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) (logid:91c422ef) Could 
not
find exception: com.cloud.exception.DiscoveryException in error code 
list
for exceptions

2022-01-18 04:03:30,863 WARN  [o.a.c.a.c.a.c.AddClusterCmd]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) (logid:91c422ef) 
Exception:

com.cloud.exception.DiscoveryException: Unable to add the external 
cluster

at

com.cloud.resource.ResourceManagerImpl.discoverCluster(ResourceManagerImpl.j
ava:586)

at 
jdk.internal.reflect.GeneratedMethodAccessor2020.invoke(Unknown
Source)

at

java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Delegatin
gMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)





  I get this error over an over no matter what, I'm not sure why is
saying that is unable to find the server resources at .. 



 ( I use the same vCenter for other zones and I do not have any 
issues
with this, version 6.5 u3.)



  I highly apprecia

Re: [PROPOSE] RM for 4.16.1

[Suresh Anaparti]

Hi All,

Happy New Year!

It's been about a month since the proposal, and we've fixed/tested/merged more 
than 140 Issues and PRs in the 4.16.1.0 milestone [1]. Currently, we've 45 open 
items in the 4.16.1.0 milestone, which are being tracked/triaged through the 
GitHub project 'CloudStack 4.16.1' [2].

We still have about 4 weeks for the soft freeze as proposed. Please continue 
your support on bug fixes, reviews, tests, etc. If you notice any issues in 
testing, please report here: https://github.com/apache/cloudstack/issues. Thank 
you.


[1] https://github.com/apache/cloudstack/milestone/22 
[2] https://github.com/orgs/apache/projects/24 


Regards,
Suresh

On 17/12/21, 4:45 PM, "Suresh Anaparti"  wrote:

Hi All,

I propose the following timelines for 4.16.1.0 release, which is targeted 
for Q1 2022. Please let me know if you have any feedback, thoughts.

- (8 weeks) Ongoing - Mid-Feb 2022: Accept all bugs, issues, improvements 
allowed in LTS [1]
- (1-2 weeks) Accept only critical/blocker fixes
- (1 week) End-Feb 2022: Stabilise 4.16 branch, accept only blocker issues 
if any
- End-Feb 2022 and Onwards: Cut 4.16.1.0 RC1 and further RCs if necessary, 
start/conclude vote, and finish release work

You can find all the open issues and PRs at the 4.16.1.0 release milestone 
[2]. Ping me (@sureshanaparti) and Nicolas (@nvazquez) on your issues and PRs, 
that are to be included in 4.16.1.0.

Looking forward for your support on bug fixes, reviews, tests, etc. Thanks.

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
[2] https://github.com/apache/cloudstack/milestone/22


Regards,
Suresh

From: Suresh Anaparti 
Date: Monday, 13 December 2021 at 6:39 PM
To: "d...@cloudstack.apache.org" 
Cc: "users@cloudstack.apache.org" 
Subject: [PROPOSE] RM for 4.16.1

Hi All,

I'd like to put myself forward as the release manager for 4.16.1.0. My 
colleague Nicolas Vazquez will support me as the co-RM for the PR 
reviews/tests/merges, and others are welcome to support as well.

I propose, we've a window of at least 8 weeks (2 months) to allow the 
community / users to test 4.16.0.0 and report issues, and aim to cut RC1 in Q1 
2022 (may be, in late Feb-2022, or early Mar-2022 onwards). I'll propose the 
timeline details by end of this week. I hope to have your support.

Please let me know if you have any thoughts / comments.


Regards,
Suresh





 

Re: New zone in ACS 4.16 - Unable to add the external cluster

[Suresh Anaparti]

Hi Cristian,

I'm not sure if this is a bug. Have you tried with api/cmk?

Can you share the complete log of zone creation. If possible, please create a 
ticket with details here: https://github.com/apache/cloudstack/issues.

 
Regards,
Suresh

On 18/01/22, 2:41 PM, "cristian.c@istream.today"  
wrote:

Hello,



Is this a bug?   I'm trying to add a new ZONE in a upgraded cloudstack
environment but fails. I have already 4 active zones which are created long
time ago.



Unable to connect to Vmware vSphere server. service address:
vmware-ams-002.domain.com. java.lang.NumberFormatException: For input
string: "null"

2022-01-18 04:03:30,849 INFO  [c.c.h.v.u.VmwareContext]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) (logid:91c422ef)
Disconnecting VMware session

2022-01-18 04:03:30,851 WARN  [c.c.r.ResourceManagerImpl]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) (logid:91c422ef) Unable to
find the server resources at
http://vmware-ams-002.domain.com/AMS-BR-01/SAO-01

2022-01-18 04:03:30,851 INFO  [c.c.u.e.CSExceptionErrorCode]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) (logid:91c422ef) Could not
find exception: com.cloud.exception.DiscoveryException in error code list
for exceptions

2022-01-18 04:03:30,863 WARN  [o.a.c.a.c.a.c.AddClusterCmd]
(qtp2053591126-636108:ctx-62b88abf ctx-06a37bc9) (logid:91c422ef) Exception:

com.cloud.exception.DiscoveryException: Unable to add the external cluster

at
com.cloud.resource.ResourceManagerImpl.discoverCluster(ResourceManagerImpl.j
ava:586)

at jdk.internal.reflect.GeneratedMethodAccessor2020.invoke(Unknown
Source)

at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(Delegatin
gMethodAccessorImpl.java:43)

at java.base/java.lang.reflect.Method.invoke(Method.java:566)





  I get this error over an over no matter what, I'm not sure why is
saying that is unable to find the server resources at .. 



 ( I use the same vCenter for other zones and I do not have any issues
with this, version 6.5 u3.)



  I highly appreciate any suggestions.



Thank you,

Cristian





 

Re: How Cloudstack choose Primary Storage?

[Suresh Anaparti]

Hi Mauro,

Happy new year!

Cloudstack chooses the storage pool using the disk/storage specs (size, pool 
type: local/shared, tags, etc) mentioned in compute offering, when deploying a 
VM. For shared pool, it picks cluster-wide or zone-wide pool first based on the 
order mentioned in the global setting 'storage.pool.allocators.order'.

In order to select a particular storage pool while deploying a VM, you can add 
a tag to the storage pool and specify that storage tag in the compute offering, 
and then use that compute offering to pick the storage pool with the tag. 
Similarly, use storage tags in the disk offering for data disks.
 
btw, what is the cloudstack release used for deployment?


Regards,
Suresh

On 17/01/22, 9:49 PM, "Mauro Ferraro - G2K Hosting"  
wrote:

Hi guys, how are you?. Happy new year!

We are deploying a new cloudstack integration with 2 primary storages 
and we are wondering how cloudstack choose the storage to deploy de VM.

Somebody knows the criteria to select?, can we configure cloudstack to 
decide automatically with some criteria?.

Thanks

Mauro


 

Re: Cloudstack 4.16 - GUI unable to submit SSL

[Suresh Anaparti]

Hi,

I'm not sure how to validate the certs there. Have you noticed any error / warn 
messages in the console proxy log.


Regards,
Suresh

On 10/01/22, 3:22 PM, "Hean Seng"  wrote:

I not sure related to this or not,  I ssh login to Console Proxy , and
seems port 443 is not listening  there .

Is there anyway I can can check in the console proxy, see if the cert is
properly deploy to the console proxy vm.

On Mon, Jan 10, 2022 at 5:31 PM Suresh Anaparti <
suresh.anapa...@shapeblue.com> wrote:

> Hi,
>
> I could see a related issue created here
> https://github.com/apache/cloudstack/issues/5634
>
> If you have the similar issue with Letsencrypt certs, you add more details
> there. Otherwise, please create a new issue with the details.
>
>
> Regards,
> Suresh
>
> On 08/01/22, 11:59 AM, "Hean Seng"  wrote:
>
> hi. Suresh
>
> I am gemnerating Letsenctyp and instll the cert using the API .
> I running.time as show in the shapeblue document.  It successfully
> running
> the API
>
>
>   "customcertificate": {
>
> "message": "Certificate has been successfully updated, if its the
> server certificate we would reboot all running console proxy VMs and
> secondary storage VMs to propagate the new certificate, please give a
> few
> minutes for console access and storage services service to be up and
> working again"
>
>   }
>
> }
>
>
>
> running 2time, first time is chain +  root
> second time is cert. perm and privatekey pkcs8
>
> after upload, destroy and let it rebuild the console proxy ,   after
> all
> up, it seems https://ip-.domain in console cannot load as expected
>
>
>
>
> On Wed, Jan 5, 2022 at 8:12 PM Suresh Anaparti <
> suresh.anapa...@shapeblue.com> wrote:
>
> > Hi,
> >
> > You can check the certificate configuration process through API/cmk
> here:
> > https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/
> >
> >
> > Regards,
> > Suresh
> >
> > On 05/01/22, 4:55 PM, "Hean Seng"  wrote:
> >
> > Any body know how to use the API to upload this cert for console
> proxy,
> > Otherwise this  4.16 is not workable .  This function seems no
> > alternative to make it work
> >
> >
    >     >
> >
>
>
>
> 
 

> On Mon, Jan 3, 2022 at 4:08 PM Hean Seng  wrote:
> >
> > > Is there anyway to manual update it before 4.16.1 release ,
> > otherwise the
> > > SSL cannot be install.
> > >
> > > On Mon, Jan 3, 2022 at 3:06 PM Suresh Anaparti <
> > > suresh.anapa...@shapeblue.com> wrote:
> > >
> > >> Good, thanks for the update Pearl!
> > >>
> > >>
> > >> Regards,
> > >> Suresh
> > >>
> > >> On 03/01/22, 12:31 PM, "Pearl d'Silva" <
> pearl.dsi...@shapeblue.com>
> > >> wrote:
> > >>
> > >> Hi,
> > >>
> > >> This seems to be an issue in 4.16.0 but has been
> addressed with:
> > >> https://github.com/apache/cloudstack/pull/5682/ and should be
> > available
> > >> in 4.16.1.
> > >>
> > >> Thanks,
> > >> Pearl
> > >>
> > >> [
> > >>
> >
> 
https://opengraph.githubassets.com/a85d63087cbc026a03525dcc5d491e900913e0ad6e2b09a6dd8eb27f392c60a8/apache/cloudstack/pull/5682
> > >> ]<https://github.com/apache/cloudstack/pull/5682/>
> > >> UI : Fix SSL certificate submit button not working by
> dhslove ·
> > Pull
> > >> Request #5682 · apache/cloudstack<
> > >> https://github.com/apache/cloudstack/pull/5682/>
> > >> Description

Re: Cloudstack 4.16 - GUI unable to submit SSL

[Suresh Anaparti]

Hi,

I could see a related issue created here 
https://github.com/apache/cloudstack/issues/5634

If you have the similar issue with Letsencrypt certs, you add more details 
there. Otherwise, please create a new issue with the details.

 
Regards,
Suresh

On 08/01/22, 11:59 AM, "Hean Seng"  wrote:

hi. Suresh

I am gemnerating Letsenctyp and instll the cert using the API .
I running.time as show in the shapeblue document.  It successfully running
the API


  "customcertificate": {

"message": "Certificate has been successfully updated, if its the
server certificate we would reboot all running console proxy VMs and
secondary storage VMs to propagate the new certificate, please give a few
minutes for console access and storage services service to be up and
working again"

  }

}



running 2time, first time is chain +  root
second time is cert. perm and privatekey pkcs8

after upload, destroy and let it rebuild the console proxy ,   after all
up, it seems https://ip-.domain in console cannot load as expected




    On Wed, Jan 5, 2022 at 8:12 PM Suresh Anaparti <
suresh.anapa...@shapeblue.com> wrote:

> Hi,
>
> You can check the certificate configuration process through API/cmk here:
> https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/
>
>
> Regards,
> Suresh
>
> On 05/01/22, 4:55 PM, "Hean Seng"  wrote:
>
> Any body know how to use the API to upload this cert for console 
proxy,
> Otherwise this  4.16 is not workable .  This function seems no
> alternative to make it work
>
>
>
>

 

> On Mon, Jan 3, 2022 at 4:08 PM Hean Seng  wrote:
>
> > Is there anyway to manual update it before 4.16.1 release ,
    > otherwise the
> > SSL cannot be install.
> >
> > On Mon, Jan 3, 2022 at 3:06 PM Suresh Anaparti <
> > suresh.anapa...@shapeblue.com> wrote:
> >
> >> Good, thanks for the update Pearl!
> >>
> >>
> >> Regards,
> >> Suresh
> >>
> >> On 03/01/22, 12:31 PM, "Pearl d'Silva" 
> >> wrote:
> >>
> >> Hi,
> >>
> >> This seems to be an issue in 4.16.0 but has been addressed 
with:
> >> https://github.com/apache/cloudstack/pull/5682/ and should be
> available
> >> in 4.16.1.
> >>
> >> Thanks,
> >> Pearl
> >>
> >> [
> >>
> 
https://opengraph.githubassets.com/a85d63087cbc026a03525dcc5d491e900913e0ad6e2b09a6dd8eb27f392c60a8/apache/cloudstack/pull/5682
> >> ]<https://github.com/apache/cloudstack/pull/5682/>
> >> UI : Fix SSL certificate submit button not working by dhslove ·
> Pull
> >> Request #5682 · apache/cloudstack<
> >> https://github.com/apache/cloudstack/pull/5682/>
> >> Description This PR fixes an issue where clicking the Submit
> button
> >> in the SSL Certificates dialog in the Infrastructure Summary UI did
> not
> >> work. Types of changes Breaking change (fix o...
> >> github.com
> >>
> >>
> >> 
> >> From: Deepak Kumar 
> >> Sent: Monday, January 3, 2022 12:23 PM
> >> To: users@cloudstack.apache.org 
> >> Subject: Re: Cloudstack 4.16 - GUI unable to submit SSL
> >>
> >> Hi  Hean Seng,
> >>
> >> I am facing the same issue.
> >>
> >> Thanks & Regards,
> >> Deepak Kumar
> >> IndiQus Global Technical Support
> >> www.indiqus.com<http://www.indiqus.com>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> On Sun, Jan 2, 2022 at 11:55 PM Hean Seng 
> wrote:
> >>
> >> > Hi
> >> >
> >> > I am using Cloudstack 4.16 , Ubuntu 20 for Mgmt server.
> >> >
> >> > Infrastructure ->. Summary -> SSL Certification
> &g

Re: Cloudstack 4.16 - GUI unable to submit SSL

[Suresh Anaparti]

Hi,

You can check the certificate configuration process through API/cmk here: 
https://www.shapeblue.com/securing-cloudstack-4-11-with-https-tls/


Regards,
Suresh

On 05/01/22, 4:55 PM, "Hean Seng"  wrote:

Any body know how to use the API to upload this cert for console proxy,
Otherwise this  4.16 is not workable .  This function seems no
alternative to make it work


 

On Mon, Jan 3, 2022 at 4:08 PM Hean Seng  wrote:

> Is there anyway to manual update it before 4.16.1 release ,  otherwise the
> SSL cannot be install.
>
> On Mon, Jan 3, 2022 at 3:06 PM Suresh Anaparti <
> suresh.anapa...@shapeblue.com> wrote:
>
>> Good, thanks for the update Pearl!
>>
>>
>> Regards,
>> Suresh
>>
>> On 03/01/22, 12:31 PM, "Pearl d'Silva" 
>> wrote:
>>
>> Hi,
>>
>> This seems to be an issue in 4.16.0 but has been addressed with:
>> https://github.com/apache/cloudstack/pull/5682/ and should be available
>> in 4.16.1.
>>
>> Thanks,
>> Pearl
>>
>> [
>> 
https://opengraph.githubassets.com/a85d63087cbc026a03525dcc5d491e900913e0ad6e2b09a6dd8eb27f392c60a8/apache/cloudstack/pull/5682
>> ]<https://github.com/apache/cloudstack/pull/5682/>
>> UI : Fix SSL certificate submit button not working by dhslove · Pull
>> Request #5682 · apache/cloudstack<
>> https://github.com/apache/cloudstack/pull/5682/>
>> Description This PR fixes an issue where clicking the Submit button
>> in the SSL Certificates dialog in the Infrastructure Summary UI did not
>> work. Types of changes Breaking change (fix o...
>> github.com
>>
>>
>> 
>> From: Deepak Kumar 
>> Sent: Monday, January 3, 2022 12:23 PM
>> To: users@cloudstack.apache.org 
>> Subject: Re: Cloudstack 4.16 - GUI unable to submit SSL
>>
>> Hi  Hean Seng,
>>
>> I am facing the same issue.
>>
>> Thanks & Regards,
>> Deepak Kumar
>> IndiQus Global Technical Support
>> www.indiqus.com<http://www.indiqus.com>
>>
>>
>>
>>
>>
>>
>>
>>
>> On Sun, Jan 2, 2022 at 11:55 PM Hean Seng  wrote:
>>
>> > Hi
>> >
>> > I am using Cloudstack 4.16 , Ubuntu 20 for Mgmt server.
>> >
>> > Infrastructure ->. Summary -> SSL Certification
>> >
>> > Entering all the SSL detail, and click submit ,  but the click has
>> no
>> > responding .
>> > Clecking the MGMT log, and nothing seems processed .
>> >
>> > Tried on both  Chrome, Safari and same issue .
>> > Tried the same SSL to  Cloudstack 4.15 , and it has no issue
>> submitting the
>> > SSL
>> >
>> > Anybody facing the same issue ?
>> >
>> >
>> > --
>> > Regards,
>> > Hean Seng
>> >
>>
>> --
>> This message is intended only for the use of the individual or entity
>> to
>> which it is addressed and may contain confidential and/or privileged
>> information. If you are not the intended recipient, please delete the
>> original message and any copy of it from your computer system. You 
are
>> hereby notified that any dissemination, distribution or copying of
>> this
>> communication is strictly prohibited unless proper authorization has
>> been
>> obtained for such action. If you have received this communication in
>> error,
>> please notify the sender immediately. Although IndiQus attempts to
>> sweep
>> e-mail and attachments for viruses, it does not guarantee that both
>> are
>> virus-free and accepts no liability for any damage sustained as a
>> result of
>> viruses.
>>
>>
>
> --
> Regards,
> Hean Seng
>


-- 
Regards,
Hean Seng

Re: Cloudstack 4.16 - GUI unable to submit SSL

[Suresh Anaparti]

Good, thanks for the update Pearl!

 
Regards,
Suresh

On 03/01/22, 12:31 PM, "Pearl d'Silva"  wrote:

Hi,

This seems to be an issue in 4.16.0 but has been addressed with: 
https://github.com/apache/cloudstack/pull/5682/ and should be available in 
4.16.1.

Thanks,
Pearl


[https://opengraph.githubassets.com/a85d63087cbc026a03525dcc5d491e900913e0ad6e2b09a6dd8eb27f392c60a8/apache/cloudstack/pull/5682]
UI : Fix SSL certificate submit button not working by dhslove · Pull 
Request #5682 · 
apache/cloudstack
Description This PR fixes an issue where clicking the Submit button in the 
SSL Certificates dialog in the Infrastructure Summary UI did not work. Types of 
changes Breaking change (fix o...
github.com



From: Deepak Kumar 
Sent: Monday, January 3, 2022 12:23 PM
To: users@cloudstack.apache.org 
Subject: Re: Cloudstack 4.16 - GUI unable to submit SSL

Hi  Hean Seng,

I am facing the same issue.

Thanks & Regards,
Deepak Kumar
IndiQus Global Technical Support
www.indiqus.com






 

On Sun, Jan 2, 2022 at 11:55 PM Hean Seng  wrote:

> Hi
>
> I am using Cloudstack 4.16 , Ubuntu 20 for Mgmt server.
>
> Infrastructure ->. Summary -> SSL Certification
>
> Entering all the SSL detail, and click submit ,  but the click has no
> responding .
> Clecking the MGMT log, and nothing seems processed .
>
> Tried on both  Chrome, Safari and same issue .
> Tried the same SSL to  Cloudstack 4.15 , and it has no issue submitting 
the
> SSL
>
> Anybody facing the same issue ?
>
>
> --
> Regards,
> Hean Seng
>

--
This message is intended only for the use of the individual or entity to
which it is addressed and may contain confidential and/or privileged
information. If you are not the intended recipient, please delete the
original message and any copy of it from your computer system. You are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited unless proper authorization has been
obtained for such action. If you have received this communication in error,
please notify the sender immediately. Although IndiQus attempts to sweep
e-mail and attachments for viruses, it does not guarantee that both are
virus-free and accepts no liability for any damage sustained as a result of
viruses.

Re: Cloudstack 4.16 - GUI unable to submit SSL

[Suresh Anaparti]

Hi Hean Seng,

I could notice 'uploadCustomCertificate' API fired on submitting the SSL 
Certificates form, and the same is logged in the management server log. Can you 
re-check (may be in private/incognito browser window, or after browser cache 
cleanup). If you still see the issue, please log a ticket with details here: 
https://github.com/apache/cloudstack/issues.


Regards,
Suresh

On 02/01/22, 11:55 PM, "Hean Seng"  wrote:

Hi

I am using Cloudstack 4.16 , Ubuntu 20 for Mgmt server.

Infrastructure ->. Summary -> SSL Certification

Entering all the SSL detail, and click submit ,  but the click has no
responding .
Clecking the MGMT log, and nothing seems processed .

Tried on both  Chrome, Safari and same issue .
Tried the same SSL to  Cloudstack 4.15 , and it has no issue submitting the
SSL

Anybody facing the same issue ?


-- 
Regards,
Hean Seng


 

Re: Failed to update VM, due to: Invalid cpu speed value, specify a value between 1 and 2147483647

[Suresh Anaparti]

Hi Cristian,

Have you chosen the fixed or custom service offering, while scaling the VM? If 
custom, are you able to specify the CPU speed from UI.

Regards,
Suresh

On 19/12/21, 2:45 PM, "cristian.c@istream.today"  
wrote:

Hello,



When I want to save a new value for CPU speed I get this error "Failed
to update VM, due to: Invalid cpu speed value, specify a value between 1 and
2147483647"  in the UI, no matter what I set, I get this in the new
CloudStack version 4.16.





Regards,

Cristian



 

Re: [PROPOSE] RM for 4.16.1

[Suresh Anaparti]

Hi All,

I propose the following timelines for 4.16.1.0 release, which is targeted for 
Q1 2022. Please let me know if you have any feedback, thoughts.

- (8 weeks) Ongoing - Mid-Feb 2022: Accept all bugs, issues, improvements 
allowed in LTS [1]
- (1-2 weeks) Accept only critical/blocker fixes
- (1 week) End-Feb 2022: Stabilise 4.16 branch, accept only blocker issues if 
any
- End-Feb 2022 and Onwards: Cut 4.16.1.0 RC1 and further RCs if necessary, 
start/conclude vote, and finish release work

You can find all the open issues and PRs at the 4.16.1.0 release milestone [2]. 
Ping me (@sureshanaparti) and Nicolas (@nvazquez) on your issues and PRs, that 
are to be included in 4.16.1.0.

Looking forward for your support on bug fixes, reviews, tests, etc. Thanks.

[1] https://cwiki.apache.org/confluence/display/CLOUDSTACK/LTS
[2] https://github.com/apache/cloudstack/milestone/22


Regards,
Suresh

From: Suresh Anaparti 
Date: Monday, 13 December 2021 at 6:39 PM
To: "d...@cloudstack.apache.org" 
Cc: "users@cloudstack.apache.org" 
Subject: [PROPOSE] RM for 4.16.1

Hi All,

I'd like to put myself forward as the release manager for 4.16.1.0. My 
colleague Nicolas Vazquez will support me as the co-RM for the PR 
reviews/tests/merges, and others are welcome to support as well.

I propose, we've a window of at least 8 weeks (2 months) to allow the community 
/ users to test 4.16.0.0 and report issues, and aim to cut RC1 in Q1 2022 (may 
be, in late Feb-2022, or early Mar-2022 onwards). I'll propose the timeline 
details by end of this week. I hope to have your support.

Please let me know if you have any thoughts / comments.


Regards,
Suresh

 

[PROPOSE] RM for 4.16.1

[Suresh Anaparti]

Hi All,

I'd like to put myself forward as the release manager for 4.16.1.0. My 
colleague Nicolas Vazquez will support me as the co-RM for the PR 
reviews/tests/merges, and others are welcome to support as well.

I propose, we've a window of at least 8 weeks (2 months) to allow the community 
/ users to test 4.16.0.0 and report issues, and aim to cut RC1 in Q1 2022 (may 
be, in late Feb-2022, or early Mar-2022 onwards). I'll propose the timeline 
details by end of this week. I hope to have your support.

Please let me know if you have any thoughts / comments.


Regards,
Suresh

 

Re: host cache

[Suresh Anaparti]

Hi Piotr,

These options are supported for KVM only (in 4.16). Details below.

vm.configdrive.primarypool.enabled: zone level configuration -  if enabled, the 
config drives are created and hosted on a primary storage pool.

vm.configdrive.force.host.cache.use: zone level configuration - if enabled, 
host cache path is used for the config drives.

vm.configdrive.use.host.cache.on.unsupported.pool: zone level configuration -  
if enabled, host cache path is used for config drives when 
'vm.configdrive.primarypool.enabled' is enabled and the storage pool doesn't 
support config drive (mainly managed storages).


The host cache path can be specified using "host.cache.location" parameter in 
/etc/cloudstack/agent/agent.properties file on the KVM host(s). The cache 
directory path will be used to host config drive ISOs for VMs, in configdrive 
directory in it. The default path is '/var/cache/cloud'.

 
Regards,
Suresh

On 25/11/21, 11:20 PM, "Piotr Pisz"  wrote:

Hi,



I noticed new options in 4.16:




vm.configdrive.force.host.cache.use













vm.configdrive.primarypool.enabled













vm.configdrive.use.host.cache.on.unsupported.pool







Could someone write more about what these options do?



Regards,

Piotr





 

Re: What is the impact which add custom attributes in VMware obuject like instance, datastore?

[Suresh Anaparti]

`out of band` means operations done outside CloudStack (and CloudStack doesn’t 
know about it).

You can add custom attributes to VMware object. CloudStack would only refer / 
modify the attributes it adds. 

Regards,
Suresh

On 16/11/21, 8:17 AM, "小林 美佳子"  wrote:

Thanks for the reply.
I wish added after deployment.
What `out of band` mean?
Is it means can't use naming which starting 'cloud.~' name?

On 2021/11/15 08:10:59 Daan Hoogland wrote:
> Do you wish to have them added after deployment or before?
> ACS doesn't have facilities to add them. They should have no influence if
> you add them out of band.
> 

 

> On Mon, Nov 15, 2021 at 6:57 AM 小林 美佳子  wrote:
> 
> >
> > Hi.
> >
> > We hope to add Custom attributes in VMware object.
> >
> > So, We want to know the impact which add custom attributes in VMware
> > obuject on CloudStack
> >
> 
> 
> -- 
> Daan
> 

Re: [VOTE] Apache CloudStack 4.16.0.0 (RC3)

[Suresh Anaparti]

+1

Tested VM & Volume life cycle operations with KVM hypervisor hosts in advanced 
zone, on fresh installation.

Regards,
Suresh

On 08/11/21, 10:05 PM, "Abhishek Kumar"  wrote:

+1

Tested upgrade for a 4.14.1 env to 4.16.0.0 RC3 packages
Advanced zone; 1 VMware cluster with 2x ESXi 6.7 hosts.
Tested following:

  *   VM lifecycle tests
  *   Kubernetes cluster deployment
  *   Changing network rate for isolated networks
  *   Template, ISO registration
  *   Basic operations with accounts and domains
  *   Import-export VM functionality
  *   Group action in UI

Regards,
Abhishek

From: Nicolas Vazquez 
Sent: 05 November 2021 00:11
To: users ; d...@cloudstack.apache.org 

Subject: [VOTE] Apache CloudStack 4.16.0.0 (RC3)

Hi All,
I have created a 4.16.0.0 release (RC3), with the following artifacts up 
for testing and a vote:

Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.16.0.0-RC20211104T1414
Commit: 44c08b5acc598972b4f0af576ffdea4e2447cb41

Source release (checksums and signatures are available at the same 
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.16.0.0/

PGP release keys (signed using 656E1BCC8CB54F84):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 8th November 2021.

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)

For users convenience, the packages from this release candidate (RC3) and
4.16.0 systemvmtemplates are available here:
https://download.cloudstack.org/testing/41600-RC3/
https://download.cloudstack.org/systemvm/4.16/

Regards,
Nicolas Vazquez








 

Re: [VOTE] Apache CloudStack 4.16.0.0 (RC2)

[Suresh Anaparti]

+1

Performed VM, Volume life cycle tests and random tests for VM/Volume snapshots, 
templates, networks (isolated / vpc) on fresh env (MS: CentOS 7.6 + KVM 
hypervisor). No issues noticed.

Regards,
Suresh

On 25/10/21, 7:26 PM, "Nicolas Vazquez"  wrote:

Hi All,

I have created a 4.16.0.0 release (RC2), with the following artifacts up 
for testing and a vote:

Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.16.0.0-RC20211025T0851
Commit: 1e070be4c9a87650f48707a44efff2796dfa802a

Source release (checksums and signatures are available at the same 
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.16.0.0/

PGP release keys (signed using 656E1BCC8CB54F84):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until 28th October 2021, 16.00 CET (72h).

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)

For users convenience, the packages from this release candidate (RC2) and
4.16.0 systemvmtemplates are available here:
https://download.cloudstack.org/testing/41600-RC2/
https://download.cloudstack.org/systemvm/4.16/

Regards,
Nicolas Vazquez






 

Re: [VOTE] Release Apache CloudStack CloudMonkey 6.2.0

[Suresh Anaparti]

As discussed over Github, these issues are not regression and doesn't block 
this release. Based on the release notes, I thought that the validation is done 
for all the arguments while setting cloudmonkey configuration, but it is for 
subset of arguments only. I've reviewed the latest release notes, and it looks 
good. 

I'm changing my vote to +1. Thanks.

Regards,
Suresh

On 30/09/21, 7:02 PM, "Suresh Anaparti"  wrote:

-1

Tested some API calls with 'cmk.darwin.x86-64'. No issues observed with 
respect to API calls, but noticed some issues (raised in Github) with 
"Validation of arguments while setting cloudmonkey configuration" (mentioned in 
v6.2.0 Release Notes).

- https://github.com/apache/cloudstack-cloudmonkey/issues/100
- https://github.com/apache/cloudstack-cloudmonkey/issues/102

Regards,
Suresh

On 24/09/21, 1:14 PM, "Pearl Dsilva"  wrote:

Hi All,

I've created a v6.2.0 release of CloudMonkey, with the following
artifacts up for a vote:

Git Branch and commit SHA:

https://github.com/apache/cloudstack-cloudmonkey/commits/8aae61e20c6789133c1d97d49e58f354ba7428c3

Commit:
8aae61e20c6789133c1d97d49e58f354ba7428c3

GitHub pre-release (for RC1 testing, contains changelog,
artifacts/binaries to test, checksums/usage details):
https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.2.0

Source release (checksums and signatures are available at the same 
location):
https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-6.2.0/

PGP release keys (signed using 986611B4A5B7090D0145B230E7DB9FC18F16C6AE)
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until October 1st, 2021.

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 the reason why)

Regards,
Pearl Dsilva






 

Re: [VOTE] Release Apache CloudStack CloudMonkey 6.2.0

[Suresh Anaparti]

-1

Tested some API calls with 'cmk.darwin.x86-64'. No issues observed with respect 
to API calls, but noticed some issues (raised in Github) with "Validation of 
arguments while setting cloudmonkey configuration" (mentioned in v6.2.0 Release 
Notes).

- https://github.com/apache/cloudstack-cloudmonkey/issues/100
- https://github.com/apache/cloudstack-cloudmonkey/issues/102

Regards,
Suresh

On 24/09/21, 1:14 PM, "Pearl Dsilva"  wrote:

Hi All,

I've created a v6.2.0 release of CloudMonkey, with the following
artifacts up for a vote:

Git Branch and commit SHA:

https://github.com/apache/cloudstack-cloudmonkey/commits/8aae61e20c6789133c1d97d49e58f354ba7428c3

Commit:
8aae61e20c6789133c1d97d49e58f354ba7428c3

GitHub pre-release (for RC1 testing, contains changelog,
artifacts/binaries to test, checksums/usage details):
https://github.com/apache/cloudstack-cloudmonkey/releases/tag/6.2.0

Source release (checksums and signatures are available at the same 
location):
https://dist.apache.org/repos/dist/dev/cloudstack/cloudmonkey-6.2.0/

PGP release keys (signed using 986611B4A5B7090D0145B230E7DB9FC18F16C6AE)
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open until October 1st, 2021.

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 the reason why)

Regards,
Pearl Dsilva


 

Re: root disk resize KVM

[Suresh Anaparti]

Hi Cristian,

Yes, root disk resize is allowed from UI/API while deploying a VM. It is 
supported through the 'rootdisksize' parameter in deployVirtualMachine API.

Regards,
Suresh

On 16/09/21, 8:23 PM, "cristian.c@istream.today"  
wrote:

Hello,



   It is possible to use root disk resize on the wizard page? Or via API
when you deploy a KVM instance?





Regards,

Cristian



 

Re: [VOTE] Apache CloudStack 4.15.2.0 (RC2)

[Suresh Anaparti]

+1

Performed some VM (template/ISO) and volume life cycle tests manually, in fresh 
installation (MS: CentOS 7.6 + Hypervisor: VMware 6.7.0).

Regards,
Suresh

On 10/09/21, 9:21 PM, "Rohit Yadav"  wrote:

All,

I've created a 4.15.2.0 release, with the following artifacts up for a vote:

Git Branch and Commit SHA:
https://github.com/apache/cloudstack/tree/4.15.2.0-RC20210910T2119
Commit: 4aaa850b63c34e0f312002f79bf9e4f699bf314a

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.15.2.0/

PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open for a week until 17 September 2021.

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)

For users convenience, the packages from this release candidate (RC1)
will be available here shortly:
https://download.cloudstack.org/testing/4.15.2.0-RC2/

There is no new systemvmtemplate for 4.15.2, the 4.15.1
systemvmtemplate can be used from here:
https://download.cloudstack.org/systemvm/4.15/

Docs are not published yet but upgrade notes are similar to the one
below without the requirement of registering a new systemvmtemplate:

https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade

Regards.


 

Re: GSoC 2021 Completes

[Suresh Anaparti]

Congratulations to the GSoC students for successfully completing their 
projects, and mentors for helping them out. Hope the students have learnt 
something new, outside of their academic programme. 

Regards,
Suresh

On 03/09/21, 4:45 PM, "Abhishek Kumar"  wrote:

Congratulations to both students and mentors, and the community in general!
Some great work started with these projects. Looking forward to seeing them 
in action in upcoming releases.
Students - hoping ACS community will continue to interest you and will look 
forward to seeing you around.


Regards,
Abhishek

From: Rohit Yadav 
Sent: 03 September 2021 16:10
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org ; Bikram Biswas 
; Sangwoo Bae ; Apurv 
Gupta ; atrocityth...@gmail.com 
Cc: Apache CloudStack Marketing 
Subject: GSoC 2021 Completes

All,

I'm happy to share with the community that our project participation at 
Google Summer of Code 2021 comes to an end with four successful projects [1][2] 
by our four students passing with flying colours. Results were available 
earlier this week on 31st Aug 2021 [3].

Let's use this opportunity to congratulate our students and mentors and ask 
them to share any feedback on the project - hope we'll participate next year 
too!

Let me start;

Congratulate Apurv, Junxuan, Bikram, and Sangwoo for your hard work and 
successful projects! We look forward to seeing you around in the community!

Thank you mentors for your hard work and mentoring the students - Pearl, 
David, Suresh, Bobby, Hari, and Nicolas!

Two of our students have blogged about their experiences, you may read them 
here:
Apurv's blog: 
https://apurv-gupta.medium.com/google-summer-of-code-apachecloudstack-final-report-bae911b0bd44
Bikram's blog: 
https://medium.com/@bickrombishsass/gsoc-2021-experience-at-apache-cloudstack-8946fe31ff5b

[1] GSoC 2021 at Apache CloudStack Project: 
https://cwiki.apache.org/confluence/display/CLOUDSTACK/GSoC+2021
[2] Student PR submissions: 
https://github.com/apache/cloudstack/pulls?q=is%3Aopen+is%3Apr+label%3Agsoc2021
[3] https://summerofcode.withgoogle.com/how-it-works/#timeline

Regards.








 

Re: CloudMonkey v6.2.0 Test Binaries

[Suresh Anaparti]

Performed some API tests, profile and autocomplete settings with 
'cmk.darwin.x86-64'. No issues noticed.

Regards,
Suresh

On 13/08/21, 5:58 PM, "Pearl d'Silva"  wrote:

Hi All,

The test binaries for the potential CloudMonkey v6.2.0 have been placed at 
https://download.cloudstack.org/testing/cmk/. It would be helpful if you'll 
could help in a round of testing for any issues / regression. On a high-level, 
some of the major changes include:

  *   Validation of arguments while setting CloudMonkey configuration
  *   Verifying user access to CloudMonkey configuration file
  *   Allowing sync command to be used as a verb for CloudStack API calls
  *   Printing response with newlines if output format chosen is "text"
  *   Providing an option to turn-off autocompletion

Please do help in testing, so that if there are any issues, we can work 
towards getting them fixed and releasing CloudMonkey 6.2.0. I'll cut rc1 
sometime next week.

Thanks for the support.


Thanks & Regards,
Pearl Dsilva





 

Re: How to create a multiple GPU passthrough offering

[Suresh Anaparti]

Correct, right now I'm not sure of the support in future releases.

Regards,
Suresh

On 13/08/21, 12:36 PM, "SVI"  wrote:

I see, thanks Suresh for this information. So just so I understand it 
correctly, at the moment, there is no support for specifying the no. of GPU 
that will be used by a compute offering, correct? Will this be supported in the 
future releases?

Thanks,
Irvin


 

> On Aug 13, 2021, at 2:37 PM, Suresh Anaparti  
> wrote:
> 
> There is no provision to specify GPU count through service offering.
> 
> Regards,
> Suresh
> 
> On 13/08/21, 11:52 AM, "SVI"  wrote:
> 
>Sorry, I’m not sure I follow. So right now, my XCP-NG hypervisor 
detects 8 GPU cards (Tesla K80). I added a compute offering with passthrough as 
vgpuType and I was able to successfully create an instance and passthrough 1 
gpu. I was able to validate this as well in the guest VM. I was actually hoping 
that in the createServiceOffering API that there’s a GPU count (just like cpu 
count) so whenever I use that compute offering it will passthrough that no. of 
GPU count in the guest VM.
> 
>Thanks,
>Irvin
    > 
> 
> 
> 
>> On Aug 13, 2021, at 1:48 PM, Suresh Anaparti 
 wrote:
>> 
>> May be, you can try this out-of-band. Check / test with the following - 
stop VM, add GPUs and start VM from the hypervisor.
>> 
>> Regards,
>> Suresh
>> 
>> On 13/08/21, 10:31 AM, "SVI"  wrote:
>> 
>>   Hi Suresh,
>> 
>>   I’m using Cloudstack 4.15.1 and XCP-NG 8.2.0 as the hypervisor host. 
Does this means that multiple GPU passthrough to 1 guest VM is not supported at 
the moment? What could be my other options here? I have a requirement for 
multiple GPUs in 1 VM that’s why I’m looking for this solution.
>> 
>> 
>>   Thanks,
>>   Irvin
>> 
>> 
>> 
>> 
>>> On Aug 13, 2021, at 12:31 PM, Suresh Anaparti 
 wrote:
>>> 
>>> Hi Irvin,
>>> 
>>> The compute service offering in CloudStack currently supports 1 GPU 
specification (using createServiceOffering  API through 
'serviceofferingdetails' parameters, with the keys pciDevice and vgpuType for 
GPU card and vGPU type respectively), and so 1 card is created for a VM.
>>> 
>>> You can find some documentation here:
>>> 
>>> - 
http://docs.cloudstack.apache.org/en/latest/adminguide/virtual_machines.html#assigning-gpu-vgpu-to-guest-vms
>>> 
>>> - 
http://docs.cloudstack.apache.org/en/latest/adminguide/service_offerings.html#creating-a-new-compute-offering
>>> 
>>> May I know the CloudStack release and Hypervisor version you are 
testing.
>>> 
>>> Regards,
>>> Suresh
>>> 
>>> On 13/08/21, 7:03 AM, "SVI"  wrote:
>>> 
>>>  Hi,
>>> 
>>>  I was able to create a GPU passthrough offering but at the moment it’s 
1 VM = 1 GPU passthrough. I have 8 GPUs in my hypervisor and technically I can 
create 8 instance with 1 GPU passthrough each. What I want to do now is to 
create at least 2 GPU to be passthrough 1 guest VM. I can’t see any 
configuration or document to do that as of the moment, is there a hidden API (I 
checked already the service offering API and doesn’t say much) that is out 
there to do this?
>>> 
>>>  Thanks,
>>>  Irvin
>>> 
>>> 
>>> 
>>> 
>>> 
>> 
>> 
> 
> 

Re: Will Cloudstack work with existing KVM server?

[Suresh Anaparti]

Correct, importing existing (unmanaged) VMs from the KVM server is not directly 
supported.

Regards,
Suresh

On 13/08/21, 11:22 AM, "Eric Green"  wrote:

Cloudstack will not, however, manage existing KVM virtual machines, 
which is what Chris wants to do. While that is theoretically possible, 
there's currently no practical way to populate the Cloudstack MySQL 
database with the information needed to make that happen. It appears his 
desire is to manage his current virtual machines with CloudStack, and 
currently the only way to do that is to upload their disk image to 
Cloudstack as a template, then deploy them to Cloudstack as a new 
virtual machine.

On 8/12/2021 10:43 PM, Suresh Anaparti wrote:
> Hi Chris,
>
> Yes, CloudStack works with existing KVM, you can check the server 
requirements and installation details here: 
http://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/kvm.html#host-kvm-installation
>   
> Regards,
> Suresh
>
> On 13/08/21, 11:04 AM, "Chris Jefferies"  wrote:
>
>  I have an existing server running ubuntu 16.04 and it's been running 
KVM for quite a while.  Mostly I use virt-manager GUI over xwindows to manage 
my VMs.  Looking now for a web UI that can work with that.
>
>  Can Cloudstack be used as a remote manager, perhaps even running in 
a separate VM instance, which is configured to manage the parent libvirt/qemu.
>
>  Can it discover the existing setup and be retrofitted with the 
existing configs, storage pools (mostly LVM), etc.
>
>  If not, does anyone have suggestions.  Thanks.
>
>
>
>   
>


 

Re: How to create a multiple GPU passthrough offering

[Suresh Anaparti]

There is no provision to specify GPU count through service offering.

Regards,
Suresh

On 13/08/21, 11:52 AM, "SVI"  wrote:

Sorry, I’m not sure I follow. So right now, my XCP-NG hypervisor detects 8 
GPU cards (Tesla K80). I added a compute offering with passthrough as vgpuType 
and I was able to successfully create an instance and passthrough 1 gpu. I was 
able to validate this as well in the guest VM. I was actually hoping that in 
the createServiceOffering API that there’s a GPU count (just like cpu count) so 
whenever I use that compute offering it will passthrough that no. of GPU count 
in the guest VM.

Thanks,
Irvin


 

> On Aug 13, 2021, at 1:48 PM, Suresh Anaparti  
> wrote:
> 
> May be, you can try this out-of-band. Check / test with the following - 
stop VM, add GPUs and start VM from the hypervisor.
> 
> Regards,
> Suresh
> 
> On 13/08/21, 10:31 AM, "SVI"  wrote:
> 
>Hi Suresh,
> 
>I’m using Cloudstack 4.15.1 and XCP-NG 8.2.0 as the hypervisor host. 
Does this means that multiple GPU passthrough to 1 guest VM is not supported at 
the moment? What could be my other options here? I have a requirement for 
multiple GPUs in 1 VM that’s why I’m looking for this solution.
> 
> 
>Thanks,
>Irvin
    > 
> 
> 
> 
>> On Aug 13, 2021, at 12:31 PM, Suresh Anaparti 
 wrote:
>> 
>> Hi Irvin,
>> 
>> The compute service offering in CloudStack currently supports 1 GPU 
specification (using createServiceOffering  API through 
'serviceofferingdetails' parameters, with the keys pciDevice and vgpuType for 
GPU card and vGPU type respectively), and so 1 card is created for a VM.
>> 
>> You can find some documentation here:
>> 
>> - 
http://docs.cloudstack.apache.org/en/latest/adminguide/virtual_machines.html#assigning-gpu-vgpu-to-guest-vms
>> 
>> - 
http://docs.cloudstack.apache.org/en/latest/adminguide/service_offerings.html#creating-a-new-compute-offering
>> 
>> May I know the CloudStack release and Hypervisor version you are testing.
>> 
>> Regards,
>> Suresh
>> 
>> On 13/08/21, 7:03 AM, "SVI"  wrote:
>> 
>>   Hi,
>> 
>>   I was able to create a GPU passthrough offering but at the moment it’s 
1 VM = 1 GPU passthrough. I have 8 GPUs in my hypervisor and technically I can 
create 8 instance with 1 GPU passthrough each. What I want to do now is to 
create at least 2 GPU to be passthrough 1 guest VM. I can’t see any 
configuration or document to do that as of the moment, is there a hidden API (I 
checked already the service offering API and doesn’t say much) that is out 
there to do this?
>> 
>>   Thanks,
>>   Irvin
>> 
>> 
>> 
>> 
>> 
> 
> 

Re: How to create a multiple GPU passthrough offering

[Suresh Anaparti]

May be, you can try this out-of-band. Check / test with the following - stop 
VM, add GPUs and start VM from the hypervisor.

Regards,
Suresh

On 13/08/21, 10:31 AM, "SVI"  wrote:

Hi Suresh,

I’m using Cloudstack 4.15.1 and XCP-NG 8.2.0 as the hypervisor host. Does 
this means that multiple GPU passthrough to 1 guest VM is not supported at the 
moment? What could be my other options here? I have a requirement for multiple 
GPUs in 1 VM that’s why I’m looking for this solution.


Thanks,
Irvin


 

> On Aug 13, 2021, at 12:31 PM, Suresh Anaparti  
> wrote:
> 
> Hi Irvin,
> 
> The compute service offering in CloudStack currently supports 1 GPU 
specification (using createServiceOffering  API through 
'serviceofferingdetails' parameters, with the keys pciDevice and vgpuType for 
GPU card and vGPU type respectively), and so 1 card is created for a VM.
> 
> You can find some documentation here:
> 
> - 
http://docs.cloudstack.apache.org/en/latest/adminguide/virtual_machines.html#assigning-gpu-vgpu-to-guest-vms
> 
> - 
http://docs.cloudstack.apache.org/en/latest/adminguide/service_offerings.html#creating-a-new-compute-offering
> 
> May I know the CloudStack release and Hypervisor version you are testing.
> 
> Regards,
> Suresh
> 
> On 13/08/21, 7:03 AM, "SVI"  wrote:
> 
>Hi,
> 
>I was able to create a GPU passthrough offering but at the moment it’s 
1 VM = 1 GPU passthrough. I have 8 GPUs in my hypervisor and technically I can 
create 8 instance with 1 GPU passthrough each. What I want to do now is to 
create at least 2 GPU to be passthrough 1 guest VM. I can’t see any 
configuration or document to do that as of the moment, is there a hidden API (I 
checked already the service offering API and doesn’t say much) that is out 
there to do this?
> 
>Thanks,
>Irvin
> 
> 
> 
> 
> 

Re: Will Cloudstack work with existing KVM server?

[Suresh Anaparti]

Hi Chris,

Yes, CloudStack works with existing KVM, you can check the server requirements 
and installation details here: 
http://docs.cloudstack.apache.org/en/latest/installguide/hypervisor/kvm.html#host-kvm-installation
 
Regards,
Suresh

On 13/08/21, 11:04 AM, "Chris Jefferies"  wrote:

I have an existing server running ubuntu 16.04 and it's been running KVM 
for quite a while.  Mostly I use virt-manager GUI over xwindows to manage my 
VMs.  Looking now for a web UI that can work with that.

Can Cloudstack be used as a remote manager, perhaps even running in a 
separate VM instance, which is configured to manage the parent libvirt/qemu.

Can it discover the existing setup and be retrofitted with the existing 
configs, storage pools (mostly LVM), etc.

If not, does anyone have suggestions.  Thanks.



 

Re: How to create a multiple GPU passthrough offering

[Suresh Anaparti]

Hi Irvin,

The compute service offering in CloudStack currently supports 1 GPU 
specification (using createServiceOffering  API through 
'serviceofferingdetails' parameters, with the keys pciDevice and vgpuType for 
GPU card and vGPU type respectively), and so 1 card is created for a VM.

You can find some documentation here:

- 
http://docs.cloudstack.apache.org/en/latest/adminguide/virtual_machines.html#assigning-gpu-vgpu-to-guest-vms

- 
http://docs.cloudstack.apache.org/en/latest/adminguide/service_offerings.html#creating-a-new-compute-offering

May I know the CloudStack release and Hypervisor version you are testing.

Regards,
Suresh

On 13/08/21, 7:03 AM, "SVI"  wrote:

Hi,

I was able to create a GPU passthrough offering but at the moment it’s 1 VM 
= 1 GPU passthrough. I have 8 GPUs in my hypervisor and technically I can 
create 8 instance with 1 GPU passthrough each. What I want to do now is to 
create at least 2 GPU to be passthrough 1 guest VM. I can’t see any 
configuration or document to do that as of the moment, is there a hidden API (I 
checked already the service offering API and doesn’t say much) that is out 
there to do this?

Thanks,
Irvin



 

Re: [VOTE] Apache CloudStack Kubernetes Provider v1.0.0 (RC1)

[Suresh Anaparti]

+1

Tested basic deployment for the Traefik ingress controller, using the 
Kubernetes Provider with the below RC build (Env: ACS main + KVM + K8s Cluster 
v1.16.3).
 
Regards,
Suresh

On 04/08/21, 5:12 PM, "David Jumani"  wrote:

Hi All,

I've created the initial CloudStack Kubernetes Provider release v1.0.0, 
with the following artifacts up for a vote:

Git Branch and Commit SH:
https://github.com/apache/cloudstack-kubernetes-provider/tree/1.0
Commit: a8fccd9fe5c145bc3a12e3681bdf33e9f6ed382c

Source release (checksums and signatures are available at the same
location):

https://dist.apache.org/repos/dist/dev/cloudstack/kubernetes-provider-v1.0.0/

PGP release keys (signed using 92D88ECF4D63C923):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The docker image can be found at 
https://hub.docker.com/r/apache/cloudstack-kubernetes-provider

The documentation for the same can be found at

https://github.com/apache/cloudstack-documentation/blob/main/source/plugins/cloudstack-kubernetes-provider.rst

https://github.com/apache/cloudstack-kubernetes-provider/blob/main/README.md#deployment
(be sure to replace the image version 
`apache/cloudstack-kubernetes-provider:v1.0.0` with 
`apache/cloudstack-kubernetes-provider:v1.0.0-RC20210804T0500`)

The vote will be open until 08 August 2021.

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)

Thanks,
David





 

Re: [PROPOSE] RM for CloudStack Kubernetes Provider v1.0

[Suresh Anaparti]

+1

Good luck David!

Regards,
Suresh

On 15/07/21, 12:02 PM, "David Jumani"  wrote:

Hi,

I'd like to put myself forward as the release manager for CloudStack 
Kubernetes Provider 
v1.0.

This will be the first release of CloudStack Kubernetes Provider which 
facilitates Kubernetes deployments on Cloudstack.
It allows Kubernetes to dynamically allocate IP addresses and the 
respective networking rules on CloudStack to ensure seamless TCP, UDP and 
TCP-Proxy LoadBalancer deployments on Kubernetes.

It was initially the Cloudstack provider in Kubernetes which was later 
extracted to allow for pluggable providers.
A lot of work and effort has gone into developing it, and we are looking 
forward to its grand debut.

The list of open issues triaged for the v1.0 milestone can be found at 
https://github.com/apache/cloudstack-kubernetes-provider/milestone/1
If you encounter any issues, please do report them at 
https://github.com/apache/cloudstack-kubernetes-provider/issues

Looking forward to your support

Thanks,
David





 

Re: Primary Storage Volume detach issue

[Suresh Anaparti]

Hi Pradeep,

When any disk is detached, it will be moved to 'fcd' folder on that primary 
storage (for VMware hypervisor). So, in your case, as the DATADISK is located 
in 'fcd' folder, that means it is detached from the VM.

Regards,
Suresh

On 12/07/21, 11:06 AM, "pradeep pal"  wrote:

Hi Suresh,

the DATADISK is located in fcd folder, and it is the shared iscsi primary 
volume.

Thanks
Pradeep

From: Suresh Anaparti 
Sent: Monday, July 12, 2021 10:11 AM
To: users@cloudstack.apache.org 
Subject: Re: Primary Storage Volume detach issue

Hi Pradeep,

Can you share some more details.

Is the path mentioned correctly for DATATDISK in the volumes table, and Are 
you able to locate the disk “4b1e297907f14fbaad3b7a5e57ff8793.vmdk” (in 'fcd' 
or VM folder) from the file system? Is the primary storage shared or local.

Regards,
Suresh

From: pradeep pal 
Reply to: "users@cloudstack.apache.org" 
Date: Saturday, 10 July 2021 at 2:44 PM
To: "users@cloudstack.apache.org" 
Subject: Primary Storage Volume detach issue

Hi,

When i create a vm and attached a DATADISK, after that when we detach this 
DATADISK, we are getting below error message, can you please help me to rectify 
this.

Infra Details:
ESXi Hypervisor:  6.7 U3
vCenter: 6.7u3
CloudStack: 4.15.0

2021-07-10 11:43:59,113 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) Search file 
4b1e297907f14fbaad3b7a5e57ff8793.vmdk on [PROD_VPC_SZ_CLS1_PRIM_VOL1] fcd
2021-07-10 11:43:59,901 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) File [PROD_VPC_SZ_CLS1_PRIM_VOL1] 
fcd/4b1e297907f14fbaad3b7a5e57ff8793.vmdk does not exist on datastore
2021-07-10 11:43:59,903 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) Search file 
4b1e297907f14fbaad3b7a5e57ff8793.vmdk on [PROD_VPC_SZ_CLS1_PRIM_VOL1]
2021-07-10 11:43:59,938 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) File [PROD_VPC_SZ_CLS1_PRIM_VOL1] 
4b1e297907f14fbaad3b7a5e57ff8793.vmdk does not exist on datastore

2021-07-10 11:44:03,525 ERROR [c.c.s.r.VmwareStorageProcessor] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) Failed to detach volume: Server returned HTTP 
response code: 500 for URL: 
https://10.xx.5.100/folder/i-2-30-VM?dcPath=YTTMTLSZCLDDC01=PROD_VPC_SZ_CLS1_PRIM_VOL1
java.io.IOException: Server returned HTTP response code: 500 for URL: 
https://10.xx.5.100/folder/i-2-30-VM?dcPath=YTTMTLSZCLDDC01=PROD_VPC_SZ_CLS1_PRIM_VOL1


ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-40:ctx-841f3323 
job-539/job-540 ctx-a90238bd) (logid:34cdbaf7) Invocation exception, caused by: 
com.cloud.utils.exception.CloudRuntimeException: Failed to detach volume 
100Gpradeep from VM pp-testvm01
FAILED, resultCode: 530, result: 
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"530","errortext":"Failed
 to detach volume 100Gpradeep from VM pp-testvm01"}

But when i check volume on vcenter i can able to see attached volume.


[cid:af75051e-d1ee-4121-be66-c1feee27fa76]

Thanks & Regards
Pradeep





 

Re: [PROPOSE] RM for CloudMonkey v6.2.0

[Suresh Anaparti]

+1

Good luck Pearl!

Regards,
Suresh

On 09/07/21, 10:52 AM, "Pearl d'Silva"  wrote:

Hi All,

I'd like to put myself forward as the release manager for CloudMonkey 6.2.0.

Our last release was almost a year ago, and since then we've had a few 
minor fixes that have gone in, and it seems about the right time to have the 
next release for CloudMonkey. There are a few open issues triaged for the 6.2.0 
milestone: https://github.com/apache/cloudstack-cloudmonkey/milestone/3. If 
you'll do encounter any further issues, please do report them at 
https://github.com/apache/cloudstack-cloudmonkey/issues.


I hope to have your support.

Thanks,
Pearl Dsilva






 

Re: Primary Storage Volume detach issue

[Suresh Anaparti]

Hi Pradeep,

Can you share some more details.

Is the path mentioned correctly for DATATDISK in the volumes table, and Are you 
able to locate the disk “4b1e297907f14fbaad3b7a5e57ff8793.vmdk” (in 'fcd' or VM 
folder) from the file system? Is the primary storage shared or local.

Regards,
Suresh

From: pradeep pal 
Reply to: "users@cloudstack.apache.org" 
Date: Saturday, 10 July 2021 at 2:44 PM
To: "users@cloudstack.apache.org" 
Subject: Primary Storage Volume detach issue

Hi,

When i create a vm and attached a DATADISK, after that when we detach this 
DATADISK, we are getting below error message, can you please help me to rectify 
this.

Infra Details:
ESXi Hypervisor:  6.7 U3
vCenter: 6.7u3
CloudStack: 4.15.0

2021-07-10 11:43:59,113 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) Search file 
4b1e297907f14fbaad3b7a5e57ff8793.vmdk on [PROD_VPC_SZ_CLS1_PRIM_VOL1] fcd
2021-07-10 11:43:59,901 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) File [PROD_VPC_SZ_CLS1_PRIM_VOL1] 
fcd/4b1e297907f14fbaad3b7a5e57ff8793.vmdk does not exist on datastore
2021-07-10 11:43:59,903 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) Search file 
4b1e297907f14fbaad3b7a5e57ff8793.vmdk on [PROD_VPC_SZ_CLS1_PRIM_VOL1]
2021-07-10 11:43:59,938 INFO  [c.c.h.v.m.DatastoreMO] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) File [PROD_VPC_SZ_CLS1_PRIM_VOL1] 
4b1e297907f14fbaad3b7a5e57ff8793.vmdk does not exist on datastore

2021-07-10 11:44:03,525 ERROR [c.c.s.r.VmwareStorageProcessor] 
(DirectAgent-125:ctx-3364032d 10.xx.5.102, job-539/job-540, cmd: 
DettachCommand) (logid:34cdbaf7) Failed to detach volume: Server returned HTTP 
response code: 500 for URL: 
https://10.xx.5.100/folder/i-2-30-VM?dcPath=YTTMTLSZCLDDC01=PROD_VPC_SZ_CLS1_PRIM_VOL1
java.io.IOException: Server returned HTTP response code: 500 for URL: 
https://10.xx.5.100/folder/i-2-30-VM?dcPath=YTTMTLSZCLDDC01=PROD_VPC_SZ_CLS1_PRIM_VOL1


ERROR [c.c.v.VmWorkJobHandlerProxy] (Work-Job-Executor-40:ctx-841f3323 
job-539/job-540 ctx-a90238bd) (logid:34cdbaf7) Invocation exception, caused by: 
com.cloud.utils.exception.CloudRuntimeException: Failed to detach volume 
100Gpradeep from VM pp-testvm01
FAILED, resultCode: 530, result: 
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":"530","errortext":"Failed
 to detach volume 100Gpradeep from VM pp-testvm01"}

But when i check volume on vcenter i can able to see attached volume.


[cid:af75051e-d1ee-4121-be66-c1feee27fa76]

Thanks & Regards
Pradeep

 

Re: [VOTE] Apache CloudStack 4.15.1.0 (RC3)

[Suresh Anaparti]

+1

Performed some manual tests for VMs, Volumes, Templates, ISOs, Isolated  
Networks, Volume Snapshots & VM Snapshots, in fresh installation (MS: CentOS 7 
+ KVM Hosts: CentOS 7).

Regards,
Suresh

On 30/06/21, 11:38 AM, "Rohit Yadav"  wrote:

+1 (binding) based on automated smoketests results with CentOS7 based mgmt 
server and CentOS7 KVM, XenServer 7.1, and Vmware 6.5/6.7.


Regards.


From: Boris Stoyanov 
Sent: Wednesday, June 30, 2021 10:30
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: [VOTE] Apache CloudStack 4.15.1.0 (RC3)

+1 (binding), considering the latest changes, I’ve did a quick test and 
checked the smoketests results, all looking good.

Bobby.

From: Rohit Yadav 
Date: Monday, 28 June 2021, 13:58
To: d...@cloudstack.apache.org , 
users@cloudstack.apache.org 
Subject: [VOTE] Apache CloudStack 4.15.1.0 (RC3)
Hi All,

I've created a 4.15.1.0 release, with the following artifacts up for a vote:

Git Branch:
https://github.com/apache/cloudstack/tree/4.15.1.0-RC20210628T1527
Commit SHA:
379454caae76279329c52aa6ae3eea389741d935

Source release (checksums and signatures are available at the same
location):
https://dist.apache.org/repos/dist/dev/cloudstack/4.15.1.0/

PGP release keys (signed using 5ED1E1122DC5E8A4A45112C2484248210EE3D884):
https://dist.apache.org/repos/dist/release/cloudstack/KEYS

The vote will be open this week until 2 July 2021.

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)

For users convenience, the packages from this release candidate and 4.15.1
systemvmtemplates are available here:
https://download.cloudstack.org/testing/4.15.1.0-RC3/
https://download.cloudstack.org/systemvm/4.15/

Documentation is not published yet, but the following may be referenced for
upgrade related tests: (there's a new 4.15.1 systemvmtemplate to be
registered prior to upgrade)

https://github.com/apache/cloudstack-documentation/tree/4.15/source/upgrading/upgrade

Regards.








 

Re: DEBUG message: Cannot release reservation, Found VM: VM[User|i-5-106-VM] Stopped but reserved on host 1. How to fixed?

[Suresh Anaparti]

Hi Kalil,

Can you check the config setting 'capacity.skipcounting.hours ', which is the 
wait time before releasing the VM resources.

The setting 'host.reservation.release.period' is the time interval to check and 
release the host reservations, but the resources are not released until the 
duration specified through 'capacity.skipcounting.hours' setting after VM is 
stopped. 

Regards,
Suresh

On 25/06/21, 7:28 PM, "Kalil de Albuquerque Carvalho" 
 wrote:

Hello all.

Some days ago I asked how to release the resources when my instances 
been halted. A member reply me with "host.reservation.release.period" 
setting, on global configuration. I changed to 5, the statement, reboot 
the CloudStack service but it is not releasing the resources and it is 
showing me this messages in the management server:

2021-06-25 09:45:54,680 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
(HostReservationReleaseChecker:ctx-6a943f41) (logid:fa97e34d) Checking 
if any host reservation can be released ...
2021-06-25 09:45:54,686 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
(HostReservationReleaseChecker:ctx-6a943f41) (logid:fa97e34d) Cannot 
release reservation, Found VM: VM[User|i-5-106-VM] Stopped but reserved 
on host 1
2021-06-25 09:45:54,691 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
(HostReservationReleaseChecker:ctx-6a943f41) (logid:fa97e34d) Cannot 
release reservation, Found VM: VM[User|i-2-105-VM] Stopped but reserved 
on host 3
2021-06-25 09:45:54,695 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
(HostReservationReleaseChecker:ctx-6a943f41) (logid:fa97e34d) Cannot 
release reservation, Found 1 VMs Running on host 4
2021-06-25 09:45:54,700 DEBUG [c.c.d.DeploymentPlanningManagerImpl] 
(HostReservationReleaseChecker:ctx-6a943f41) (logid:fa97e34d) Cannot 
release reservation, Found 3 VMs Running on host 5


this situation keep going and not release the resources.

All my instances are halted, just System VM's and Virtual Routers are 
running.

My environment is:

What am I doing wrong?

Where can I fix this?

CloudStack: 4.15

Distro: CentOS 7.9

Kernel: 3.10.0-1160.25.1.el7.x86_64

Best regards.




 

Re: [RESULT][VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness

[Suresh Anaparti]

Thanks Dahn.

So far, no issues with Travis CI, Jenkins. Packaging also seems fine. Smoke 
tests in progress, not observed any issues with renaming until now. I think, we 
still have to wait few more weeks (until most of us adapts to default branch 
'main') and watch for any issues reported with renaming.

Please let us know if you have noticed any issues.

Regards,
Suresh

On 18/06/21, 1:40 PM, "Daan Hoogland"  wrote:

thanks Suresh for the hard work,

Are there any remaining actions or arisen issues on this?

On Fri, Jun 11, 2021 at 12:23 PM Suresh Anaparti <
suresh.anapa...@shapeblue.com> wrote:

> Hi All,
>
> The default branch has been renamed to 'main' (from 'master'), for the
> following CloudStack project repos.
>
>- cloudstack
>- cloudstack-documentation
>- cloudstack-www
>- cloudstack-cloudmonkey
>- cloudstack-kubernetes-provider
>- cloudstack-ec2stack
>- cloudstack-gcestack
>
> Next steps, I'll run health checks and see if there are any issues with
> the integrated jobs/systems (Travis CI, Jenkins, etc).
>
> Please run the below cmds to update your existing cloned repos.
>
> git branch -m master main
> git fetch origin
> git branch -u origin/main main
> git remote set-head origin -a
>
>
> Regards,
> Suresh
>
> On 08/06/21, 6:55 PM, "Suresh Anaparti" 
> wrote:
>
> Hi All,
>
> Here is the update, All the PRs that addressed the inclusive changes
> (changing the default branch name from 'master' to 'main' and replacing
> some offensive words) in the CloudStack repos are accepted/merged. I've
> created INFRA ticket: https://issues.apache.org/jira/browse/INFRA-21978,
> to rename the default branch to 'main' (which should automatically
> re-target all the open/draft PRs against 'master' to 'main'). I'll let you
    > know once renaming is done, and the next steps.
>
> Regards,
> Suresh
>
> On 11/05/21, 1:12 PM, "Suresh Anaparti" 

> wrote:
>
> Hi all,
>
> The vote [1] for renaming default git branch name from 'master' to
> 'main' and replace offensive words as appropriate for inclusiveness, in 
the
> Apache CloudStack project has passed with the following votes:
>
> +1 (PMC / binding)
> 4 persons (Daan, Gabriel, Rohit, Wei)
>
> +1 (non-binding)
> 5 persons (David, Rene, Nathan, Hari, Suresh)
>
> +0
> 1 person (Andrija)
>
> Thank you all for participating. Next steps, I'll close any review
> feedback on the PRs and get them accepted. Once the PRs are accepted, we
> can merge them to 'master' (may be after 4.15.1 release) and will request
> ASF infra (track through new INFRA ticket) to disable pushes to 'master',
> rename 'master' to 'main and set 'main' as the default branch, for all the
> CloudStack repos.
>
> [1] https://markmail.org/message/n6sbl3vgm7hy77zj
>
>
> Regards,
> Suresh
>
>
>
>
>
>
>
>
>
>
>
>
>

-- 
Daan


 

Re: Snapshots are not working after upgrading to 4.15.0

[Suresh Anaparti]

Hi Andrei,

Have you checked the 'status' and 'removed' timestamp in snapshots table, and 
'state' in snapshot_store_ref table for these snapshots.

Similar issue logged (by Ed, as mentioned in his email) here: 
https://github.com/apache/cloudstack/issues/4797. Is it the same issue? 

Regards,
Suresh

On 17/06/21, 2:18 PM, "Andrei Mikhailovsky"  wrote:

Hi Suresh, Please see below the answers to your questions.


 

- Original Message -
    > From: "Suresh Anaparti" 
> To: "users" 
> Sent: Thursday, 17 June, 2021 06:36:27
> Subject: Re: Snapshots are not working after upgrading to 4.15.0

> Hi Andrei,
> 
> Can you check if the storage garbage collector is enabled or not in your 
env
> (specified using the global setting 'storage.cleanup.enabled'). If it is
> enabled, check the interval & delay setting: 'storage.cleanup.interval' 
and
> 'storage.cleanup.delay', and see the logs to confirm cleanup is performed 
or
> not.

storage.cleanup.enabled is true
storage.cleanup.interval is 3600
storage.cleanup.delay is 360086400

> 
> Also, check the snapshot status / state in snapshots & snapshot_store_ref 
tables
> for the snapshots that are not deleted during the cleanup. Is 'removed'
> timestamp set for them in snapshots table?
> 


The table snapshots has NULL under the removed column in all snapshots that 
I've removed. The table snapshot_store_ref has no such column, but the state 
shown as Destroyed.




> Regards,
> Suresh
> 
>On 16/06/21, 9:46 PM, "Andrei Mikhailovsky"  
wrote:
> 
>Hello,
> 
>I've done some more investigation and indeed, the snapshots were not 
taken
>because the secondary storage was over 90% used. I have started 
cleaning some
>of the older volumes and noticed another problem. After removing 
snapshots,
>they do not seem to be removed from the secondary storage. I've 
removed all
>snapshots over 24 hours ago and it looks like  the disk space hasn't 
been freed
>up at all.
> 
>Looks like there are issues with snapshotting function after all.
> 
>Andrei
> 
> 
> 
>
> 
> 
> - Original Message -
>> From: "Harikrishna Patnala" 
>> To: "users" 
>> Sent: Tuesday, 8 June, 2021 03:33:57
>> Subject: Re: Snapshots are not working after upgrading to 4.15.0
> 
>> Hi Andrei,
>> 
>> Can you check the following things and let us know?
>> 
>> 
>>  1.  Can you try creating a new volume and then create snapshot of 
that, to check
>>  if this an issue with old entries
>>  2.  For the snapshots which are failing can you check if you are 
seeing any
>>  error messages like this "Can't find an image storage in zone with 
less than".
>>  This is to check if secondary storage free space check failed.
>>  3.  For the snapshots which are failing and if it is delta snapshot 
can you
>>  check if its parent's snapshot entry exists in "snapshot_store_ref" 
table with
>>  'parent_snapshot_id' of the current snapshot with 'store_role' 
"Image". This is
>>  to find the secondary storage where the parent snapshot backup is 
located.
>> 
>> Regards,
>> Harikrishna
>> 
>> From: Andrei Mikhailovsky 
>> Sent: Monday, June 7, 2021 7:00 PM
>> To: users 
>> Subject: Snapshots are not working after upgrading to 4.15.0
>> 
>> Hello everyone,
>> 
>> I am having an issue with volume snapshots since I've upgraded to 
4.15.0. None
>> of the volumes are being snapshotted regardless if the snapshot is 
initiated
>> manually or from the schedule. The strange thing is that if I 
manually take the
>> snapshot, the GUI shows Success status, but the Storage>Snapshots 
show an Error
>> status. Here is what I see in the management server logs:
>> 
>> 2021-06-07 13:55:20,022 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
>> (Work-Job-Executor-81:ctx-08dd4222 job-86141/job-86143) 
(logid:be34ce01) Done
>> executing com.cloud.vm.VmWorkTakeVolumeSnapshot for job-86143
>> 2021-06-07 13:55:20,024 INFO [o.a.c.f.j.i.AsyncJobMonitor]
>> (Work-Job-Executor-81:ctx-08dd4222 job

Re: Snapshots are not working after upgrading to 4.15.0

[Suresh Anaparti]

Hi Andrei,

Can you check if the storage garbage collector is enabled or not in your env 
(specified using the global setting 'storage.cleanup.enabled'). If it is 
enabled, check the interval & delay setting: 'storage.cleanup.interval' and 
'storage.cleanup.delay', and see the logs to confirm cleanup is performed or 
not.

Also, check the snapshot status / state in snapshots & snapshot_store_ref 
tables for the snapshots that are not deleted during the cleanup. Is 'removed' 
timestamp set for them in snapshots table?
 
Regards,
Suresh

On 16/06/21, 9:46 PM, "Andrei Mikhailovsky"  wrote:

Hello,

I've done some more investigation and indeed, the snapshots were not taken 
because the secondary storage was over 90% used. I have started cleaning some 
of the older volumes and noticed another problem. After removing snapshots, 
they do not seem to be removed from the secondary storage. I've removed all 
snapshots over 24 hours ago and it looks like  the disk space hasn't been freed 
up at all.

Looks like there are issues with snapshotting function after all.

Andrei




 

- Original Message -
> From: "Harikrishna Patnala" 
> To: "users" 
> Sent: Tuesday, 8 June, 2021 03:33:57
> Subject: Re: Snapshots are not working after upgrading to 4.15.0

> Hi Andrei,
> 
> Can you check the following things and let us know?
> 
> 
>  1.  Can you try creating a new volume and then create snapshot of that, 
to check
>  if this an issue with old entries
>  2.  For the snapshots which are failing can you check if you are seeing 
any
>  error messages like this "Can't find an image storage in zone with less 
than".
>  This is to check if secondary storage free space check failed.
>  3.  For the snapshots which are failing and if it is delta snapshot can 
you
>  check if its parent's snapshot entry exists in "snapshot_store_ref" 
table with
>  'parent_snapshot_id' of the current snapshot with 'store_role' "Image". 
This is
>  to find the secondary storage where the parent snapshot backup is 
located.
> 
> Regards,
> Harikrishna
> 
> From: Andrei Mikhailovsky 
> Sent: Monday, June 7, 2021 7:00 PM
> To: users 
> Subject: Snapshots are not working after upgrading to 4.15.0
> 
> Hello everyone,
> 
> I am having an issue with volume snapshots since I've upgraded to 4.15.0. 
None
> of the volumes are being snapshotted regardless if the snapshot is 
initiated
> manually or from the schedule. The strange thing is that if I manually 
take the
> snapshot, the GUI shows Success status, but the Storage>Snapshots show an 
Error
> status. Here is what I see in the management server logs:
> 
> 2021-06-07 13:55:20,022 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> (Work-Job-Executor-81:ctx-08dd4222 job-86141/job-86143) (logid:be34ce01) 
Done
> executing com.cloud.vm.VmWorkTakeVolumeSnapshot for job-86143
> 2021-06-07 13:55:20,024 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> (Work-Job-Executor-81:ctx-08dd4222 job-86141/job-86143) (logid:be34ce01) 
Remove
> job-86143 from job monitoring
> 2021-06-07 13:55:20,094 DEBUG [o.a.c.s.s.SnapshotServiceImpl]
> (BackupSnapshotTask-3:ctx-744796da) (logid:607dbb0e) Failed to copy 
snapshot
> com.cloud.utils.exception.CloudRuntimeException: can not find an image 
stores
> at
> 
org.apache.cloudstack.storage.snapshot.SnapshotServiceImpl.backupSnapshot(SnapshotServiceImpl.java:271)
> at
> 
org.apache.cloudstack.storage.snapshot.DefaultSnapshotStrategy.backupSnapshot(DefaultSnapshotStrategy.java:171)
> at
> 
com.cloud.storage.snapshot.SnapshotManagerImpl$BackupSnapshotTask.runInContext(SnapshotManagerImpl.java:1238)
> at
> 
org.apache.cloudstack.managed.context.ManagedContextRunnable$1.run(ManagedContextRunnable.java:48)
> at
> 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext$1.call(DefaultManagedContext.java:55)
> at
> 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.callWithContext(DefaultManagedContext.java:102)
> at
> 
org.apache.cloudstack.managed.context.impl.DefaultManagedContext.runWithContext(DefaultManagedContext.java:52)
> at
> 
org.apache.cloudstack.managed.context.ManagedContextRunnable.run(ManagedContextRunnable.java:45)
> at
> 
java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> 
java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
> at
> 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at
> 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at 

Re: Unable to add template to new deployment

[Suresh Anaparti]

HI Joshua,

What is the agent state of secondarystoragevm in the UI. If it is not 'Up', you 
can SSH to it and check the status of agent service there (service cloud 
status). Have you noticed any errors in the ssvm log at ' 
/var/log/cloud/cloud.out' if the service is running.


Regards,
Suresh

On 16/06/21, 4:11 AM, "Joshua Schaeffer"  wrote:

I've setup ACS 4.15 and created the first zone on it using the wizard 
through primate. The zone is enabled and isn't showing any issues in the UI. I 
can see two system vm's running (secondarystoragevm and consoleproxy) and can 
SSH into the VM's from the compute node. However when I try to add a template 
through the UI I get the following error:

There is no secondary storage VM for downloading template to image store 
LXC_SEC_STOR1

And on the controller I can see the corresponding log entries when I try to 
submit the new template:

2021-06-15 22:13:35,884 DEBUG [c.c.a.ApiServlet] 
(qtp1644231115-348:ctx-aab81632) (logid:ac328268) ===START===  172.16.44.18 -- 
GET  
name=Ubuntu+20.04=Ubuntu+20.04+(Focal)+64-bit=9f6f5b49-0e12-4af4-a13b-2ace6c47de43=LXC=TAR=aa18f3ad-cd73-11eb-b1da-5254008f72d5=true=getUploadParamsForTemplate=json
2021-06-15 22:13:35,924 DEBUG [c.c.a.ApiServer] 
(qtp1644231115-348:ctx-aab81632 ctx-da7281d3) (logid:ac328268) CIDRs from which 
account 'Acct[f8d6949d-cd74-11eb-b1da-5254008f72d5-admin]' is allowed to 
perform API calls: 0.0.0.0/0,::/0
2021-06-15 22:13:36,093 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl] 
(qtp1644231115-348:ctx-aab81632 ctx-da7281d3) (logid:ac328268) template 203 is 
not in store:1, type:Image
2021-06-15 22:13:36,138 DEBUG [o.a.c.s.i.TemplateDataFactoryImpl] 
(qtp1644231115-348:ctx-aab81632 ctx-da7281d3) (logid:ac328268) template 203 is 
already in store:1, type:Image
2021-06-15 22:13:36,142 WARN  [c.c.t.HypervisorTemplateAdapter] 
(qtp1644231115-348:ctx-aab81632 ctx-da7281d3) (logid:ac328268) There is no 
secondary storage VM for downloading template to image store LXC_SEC_STOR1
2021-06-15 22:13:36,146 DEBUG [c.c.u.d.T.Transaction] 
(qtp1644231115-348:ctx-aab81632 ctx-da7281d3) (logid:ac328268) Rolling back the 
transaction: Time = 98 Name =  qtp1644231115-348; called by 
-TransactionLegacy.rollback:888-TransactionLegacy.removeUpTo:831-TransactionLegacy.close:655-Transaction.execute:38-Transaction.execute:47-HypervisorTemplateAdapter.createTemplateForPostUpload:298-TemplateManagerImpl.registerPostUploadInternal:361-TemplateManagerImpl.registerTemplateForPostUpload:423-NativeMethodAccessorImpl.invoke0:-2-NativeMethodAccessorImpl.invoke:62-DelegatingMethodAccessorImpl.invoke:43-Method.invoke:566
2021-06-15 22:13:36,229 ERROR [c.c.a.ApiServer] 
(qtp1644231115-348:ctx-aab81632 ctx-da7281d3) (logid:ac328268) unhandled 
exception executing api command: [Ljava.lang.String;@2ad13bf5
com.cloud.utils.exception.CloudRuntimeException: There is no secondary 
storage VM for downloading template to image store LXC_SEC_STOR1
at 
com.cloud.template.HypervisorTemplateAdapter$1.doInTransaction(HypervisorTemplateAdapter.java:363)
at 
com.cloud.template.HypervisorTemplateAdapter$1.doInTransaction(HypervisorTemplateAdapter.java:298)
at com.cloud.utils.db.Transaction$2.doInTransaction(Transaction.java:50)
at com.cloud.utils.db.Transaction.execute(Transaction.java:40)
at com.cloud.utils.db.Transaction.execute(Transaction.java:47)
at 
com.cloud.template.HypervisorTemplateAdapter.createTemplateForPostUpload(HypervisorTemplateAdapter.java:298)
at 
com.cloud.template.TemplateManagerImpl.registerPostUploadInternal(TemplateManagerImpl.java:361)
at 
com.cloud.template.TemplateManagerImpl.registerTemplateForPostUpload(TemplateManagerImpl.java:423)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
at 
org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:344)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:198)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:163)
at 
org.apache.cloudstack.network.contrail.management.EventUtils$EventInterceptor.invoke(EventUtils.java:107)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
at 
com.cloud.event.ActionEventInterceptor.invoke(ActionEventInterceptor.java:51)
at 
org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:175)
at 

Re: Failure creating a template from a snapshot

[Suresh Anaparti]

Hi Jeremy,

Can you share the env details (mainly: cloudstack version, primary storage, 
hypervisor) where this error is seen. The snapshot db entries and few more log 
snippets before the error would be helpful, to debug the issue.

Regards,
Suresh

On 16/06/21, 9:46 AM, "Jeremy Hansen"  wrote:


I see this error:

Create template
(GSA Security Scanner) Failed to copy snapshot:java.lang.RuntimeException: 
InvocationTargetException when invoking RPC callback for command: 
copySnapshotAsyncCallback

Any clues on this?

Thanks
-jeremy



 

Default branch is 'main' now, for the CloudStack repos

[Suresh Anaparti]

Hi All,

As updated last week, the default branches for the CloudStack repos has been 
renamed to 'main' (from 'master'). Please check the process outlined below, to 
update your repos.

- To update the default branch to 'main' in your local repos cloned from 
apache/cloudstack (or other cloudstack repos), run the below cmds in sequence:

git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a

- To update the forked repos from apache/cloudstack (or other cloudstack 
repos), rename the default branch using the GitHub tool mentioned here: 
https://github.com/github/renaming#rename-existing (which also re-targets the 
open/draft PRs, Note: The PRs will be closed if the source repo/branch doesn't 
exist) and then run the above cmds to update your local repos cloned from that 
repo.

- To fork the CloudStack source code and setup new local repo, rebase or create 
pull requests, follow the steps mentioned here: 
https://cloudstack.apache.org/developers.html. 


Regards,
Suresh


 

Re: [RESULT][VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness

[Suresh Anaparti]

Hi All,

The default branch has been renamed to 'main' (from 'master'), for the 
following CloudStack project repos.

   - cloudstack 
   - cloudstack-documentation 
   - cloudstack-www 
   - cloudstack-cloudmonkey 
   - cloudstack-kubernetes-provider 
   - cloudstack-ec2stack 
   - cloudstack-gcestack

Next steps, I'll run health checks and see if there are any issues with the 
integrated jobs/systems (Travis CI, Jenkins, etc).

Please run the below cmds to update your existing cloned repos.

git branch -m master main
git fetch origin
git branch -u origin/main main
git remote set-head origin -a


Regards,
Suresh

On 08/06/21, 6:55 PM, "Suresh Anaparti"  wrote:

Hi All,

Here is the update, All the PRs that addressed the inclusive changes 
(changing the default branch name from 'master' to 'main' and replacing some 
offensive words) in the CloudStack repos are accepted/merged. I've created 
INFRA ticket: https://issues.apache.org/jira/browse/INFRA-21978, to rename the 
default branch to 'main' (which should automatically re-target all the 
open/draft PRs against 'master' to 'main'). I'll let you know once renaming is 
done, and the next steps.

Regards,
Suresh

On 11/05/21, 1:12 PM, "Suresh Anaparti"  
wrote:

Hi all,

The vote [1] for renaming default git branch name from 'master' to 
'main' and replace offensive words as appropriate for inclusiveness, in the 
Apache CloudStack project has passed with the following votes:

+1 (PMC / binding)
4 persons (Daan, Gabriel, Rohit, Wei)

+1 (non-binding)
5 persons (David, Rene, Nathan, Hari, Suresh)

+0
1 person (Andrija)

Thank you all for participating. Next steps, I'll close any review 
feedback on the PRs and get them accepted. Once the PRs are accepted, we can 
merge them to 'master' (may be after 4.15.1 release) and will request ASF infra 
(track through new INFRA ticket) to disable pushes to 'master', rename 'master' 
to 'main and set 'main' as the default branch, for all the CloudStack repos.

[1] https://markmail.org/message/n6sbl3vgm7hy77zj


Regards,
Suresh










 

Re: [RESULT][VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness

[Suresh Anaparti]

Hi All,

Here is the update, All the PRs that addressed the inclusive changes (changing 
the default branch name from 'master' to 'main' and replacing some offensive 
words) in the CloudStack repos are accepted/merged. I've created INFRA ticket: 
https://issues.apache.org/jira/browse/INFRA-21978, to rename the default branch 
to 'main' (which should automatically re-target all the open/draft PRs against 
'master' to 'main'). I'll let you know once renaming is done, and the next 
steps.

Regards,
Suresh

On 11/05/21, 1:12 PM, "Suresh Anaparti"  wrote:

Hi all,

The vote [1] for renaming default git branch name from 'master' to 'main' 
and replace offensive words as appropriate for inclusiveness, in the Apache 
CloudStack project has passed with the following votes:

+1 (PMC / binding)
4 persons (Daan, Gabriel, Rohit, Wei)

+1 (non-binding)
5 persons (David, Rene, Nathan, Hari, Suresh)

+0
1 person (Andrija)

Thank you all for participating. Next steps, I'll close any review feedback 
on the PRs and get them accepted. Once the PRs are accepted, we can merge them 
to 'master' (may be after 4.15.1 release) and will request ASF infra (track 
through new INFRA ticket) to disable pushes to 'master', rename 'master' to 
'main and set 'main' as the default branch, for all the CloudStack repos.

[1] https://markmail.org/message/n6sbl3vgm7hy77zj


Regards,
Suresh






 

Re: Cloudstack source code compilation - RPMs build failed - LDAP

[Suresh Anaparti]

Hi Hemalatha Pal,

You can refer to the following wiki pages, to setup dev environment and build 
process. The CloudStack build, using mavin (mvn), would download the required 
dependencies from the maven repo. Only need to download external dependency 
jars manually, copy to 'deps' folder and 'mvn install' (check 
'deps/install-non-oss.sh').

https://cwiki.apache.org/confluence/display/CLOUDSTACK/Setting+up+CloudStack+Development+Environment

https://cwiki.apache.org/confluence/display/CLOUDSTACK/How+to+build+CloudStack#HowtobuildCloudStack-InstallingMaven

Regards,
Suresh


 

On 28/05/21, 2:46 PM, "Hemalatha Pal"  wrote:

Hi,

I am new to this cloudstack. So I would need some pointers on how to 
proceed with resolving the below error.

I understand from the error that the build is looking for these jars in 
https://repo.maven.apache.org/maven2  link and it couldn't find the cloudstack 
directory under org.apache directory. 

Questions :
1) Why is cloudstack folder not found in the 
https://repo.maven.apache.org/maven2  - org.apache path provided in the source 
build files ?
2) If not found in this link https://repo.maven.apache.org/maven2 , then 
which url should I give for accessing these files ?
3) If I need to modify with the new url which has those jar files, then 
which pom.xml file should I modify ? Since I don't see a common pom.xml file 
which has both these jars (eg. cloud-server.jar) and url 
(https://repo.maven.apache.org/maven2 ) referred in the same file ?

Thanks in advance for your guidance.

Regards,
Hema

[root@centos8 ldap]# pwd 
/home/hema/apache-cloudstack-4.15.0.0-src/plugins/user-authenticators/ldap 
[root@centos8 ldap]# 

[root@centos8 ldap]# ls -lrt 
total 12 
drwxrwxr-x. 4 hema hema   30 Jan  5 10:51 src 
-rw-rw-r--. 1 hema hema 9515 Jan  5 10:51 pom.xml  

[root@centos8 ldap]# mvn -X install 
Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d) 
Maven home: /home/hema/cloudstack/apache-maven-3.8.1 
Java version: 11.0.11, vendor: Red Hat, Inc., runtime: 
/usr/lib/jvm/java-11-openjdk-11.0.11.0.9-0.el8_3.x86_64 
Default locale: en_IN, platform encoding: UTF-8 
OS name: "linux", version: "4.18.0-240.22.1.el8_3.x86_64", arch: "amd64", 
family: "unix" 
[DEBUG] Created new class realm maven.api 

[DEBUG] Using mirror maven-default-http-blocker (http://0.0.0.0/) for 
maven2-repository.dev.java.net (http://download.java.net/maven/2/). 
[WARNING] The POM for org.apache.cloudstack:cloud-server:jar:4.15.0.0 is 
missing, no dependency information available 
[WARNING] The POM for org.apache.cloudstack:cloud-api:jar:4.15.0.0 is 
missing, no dependency information available 
[WARNING] The POM for org.apache.cloudstack:cloud-utils:jar:4.15.0.0 is 
missing, no dependency information available 
[WARNING] The POM for 
org.apache.cloudstack:cloud-framework-config:jar:4.15.0.0 is missing, no 
dependency information available 
[WARNING] The POM for org.apache.cloudstack:cloud-api:jar:tests:4.15.0.0 is 
missing, no dependency information available 


[ERROR] Failed to execute goal on project 
cloud-plugin-user-authenticator-ldap: Could not resolve dependencies for 
project 
org.apache.cloudstack:cloud-plugin-user-authenticator-ldap:jar:4.15.0.0: The 
following artifacts could not be resolved: 
org.apache.cloudstack:cloud-server:jar:4.15.0.0, 
org.apache.cloudstack:cloud-api:jar:4.15.0.0, 
org.apache.cloudstack:cloud-utils:jar:4.15.0.0, 
org.apache.cloudstack:cloud-framework-config:jar:4.15.0.0, 
org.apache.cloudstack:cloud-api:jar:tests:4.15.0.0: 
org.apache.cloudstack:cloud-server:jar:4.15.0.0 was not found in 
https://repo.maven.apache.org/maven2 during a previous attempt. This failure 
was cached in the local repository and resolution is not reattempted until the 
update interval of central has elapsed or updates are forced ->

Re: [!!Mass Mail]Re: Hypervisor limits

[Suresh Anaparti]

Hi,

You can add hypervisor capabilities for XenServer 8.2.0 using below sql, to fix 
your issue. Please note that XenServer 8.2.0 is not a supported hypervisor 
version in 4.14.1 and so the capabilities are not included by default, you can 
check the compatibility matrix here: 
http://docs.cloudstack.apache.org/en/4.14.1.0/releasenotes/compat.html.

INSERT IGNORE INTO cloud.hypervisor_capabilities(uuid, hypervisor_type, 
hypervisor_version, max_guests_limit, max_data_volumes_limit, 
max_hosts_per_cluster, storage_motion_supported) VALUES (UUID(), 'XenServer', 
'8.2.0', 1000, 253, 64, 1)

Regards,
Suresh

On 18/05/21, 5:58 PM, "Дикевич Евгений Александрович" 
 wrote:

HI
Servers marked as XenServer 8.2:

https://ibb.co/tLjgy0N

How I can add cababitilies for it?
-Original Message-
From: Harikrishna Patnala [mailto:harikrishna.patn...@shapeblue.com] 
Sent: Tuesday, May 18, 2021 12:57 PM
To: users@cloudstack.apache.org
Subject: [!!Mass Mail]Re: Hypervisor limits

Hi,

The management server could have taken the default value for the max data 
volumes limit.
| default|  6 |

Please check the hypervisor version in the host table to know which version 
it has detected. You can view it from the host section in UI.

If it is correctly marked to 8.2.0, adding hypervisor capabilities entry 
for 8.2.0 in the "hypervisor_capabilities" table will fix your problem. You can 
try keeping the old values as in 8.0.0 version.

If the management server has the support for the XenServer version in its 
release, then these entries would have been there.

Regards,
Harikrishna

From: Дикевич Евгений Александрович 
Sent: Tuesday, May 18, 2021 12:21 PM
To: users@cloudstack.apache.org 
Subject: Hypervisor limits

Hi all!
I have ACS 4.14.1 with XCP-NG 8.2 with PreSetup iSCSI storage.
When I add more than 6 data disks it says me that 6 volumes are maximum.
This is hypervisor limits for XenServer lower than 6.x.
In DB we can see:
mysql> select hypervisor_version,max_data_volumes_limit from 
cloud.hypervisor_capabilities where hypervisor_capabilities.hypervisor_type = 
'XenServer';
+++
| hypervisor_version | max_data_volumes_limit |
+++
| 5.6|  6 |
| 5.6 FP1|  6 |
| 5.6 SP2|  6 |
| 6.0| 13 |
| 6.0.2  | 13 |
| 6.1.0  | 13 |
| 6.2.0  | 13 |
| 6.5.0  | 13 |
| 7.0.0  | 13 |
| 7.1.0  | 13 |
| 7.1.1  |253 |
| 7.1.2  |253 |
| 7.2.0  | 13 |
| 7.3.0  | 13 |
| 7.4.0  | 13 |
| 7.5.0  | 13 |
| 7.6.0  |253 |
| 8.0.0  |253 |
| default|  6 |
| XCP 1.0|  6 |
| XCP-ng 7.4.0   | 13 |
+++
21 rows in set (0.00 sec)

My question is - why ACS detects my hosts are "XenServer 6.1.x and before" 
and how I can change it?
Внимание!
Это электронное письмо и все прикрепленные к нему файлы являются 
конфиденциальными и предназначены исключительно для использования лицом 
(лицами), которому (которым) оно предназначено. Если Вы не являетесь лицом 
(лицами), которому (которым) предназначено это письмо, не копируйте и не 
разглашайте его содержимое и удалите это сообщение и все вложения из Вашей 
почтовой системы. Любое несанкционированное использование, распространение, 
раскрытие, печать или копирование этого электронного письма и прикрепленных к 
нему файлов, кроме как лицом (лицами) которому (которым) они предназначены, 
является незаконным и запрещено. Принимая во внимание, что передача данных 
посредством Интернет не является безопасной, мы не несем никакой 
ответственности за любой потенциальный ущерб, причиненный в результате ошибок 
при передаче данных или этим сообщением и прикрепленными к нему файлами.

Attention!
This email and all attachments to it are confidential and are intended 
solely for use by the person (or persons) referred to (mentioned) as the 
intended recipient (recipients). If you are not the intended recipient of this 
email, do not copy or disclose its contents and delete the message and any 
attachments to it from your e-mail system. Any 

[RESULT][VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness

[Suresh Anaparti]

Hi all,

The vote [1] for renaming default git branch name from 'master' to 'main' and 
replace offensive words as appropriate for inclusiveness, in the Apache 
CloudStack project has passed with the following votes:

+1 (PMC / binding)
4 persons (Daan, Gabriel, Rohit, Wei)

+1 (non-binding)
5 persons (David, Rene, Nathan, Hari, Suresh)

+0
1 person (Andrija)

Thank you all for participating. Next steps, I'll close any review feedback on 
the PRs and get them accepted. Once the PRs are accepted, we can merge them to 
'master' (may be after 4.15.1 release) and will request ASF infra (track 
through new INFRA ticket) to disable pushes to 'master', rename 'master' to 
'main and set 'main' as the default branch, for all the CloudStack repos.

[1] https://markmail.org/message/n6sbl3vgm7hy77zj


Regards,
Suresh


 

Re: [VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness

[Suresh Anaparti]

Hi Nathan,

Appreciate your feedback on the PR(s). I've addressed your comments on these 
PR(s), please take a look.

On the other questions/comments you had,

- Is there a overarching ASF criteria for what words are inappropriate for 
future development?
=> I am not aware of any criteria in ASF. I've contacted Gabriel on this, and 
he started a mail thread (at 'divers...@apache.org') here: 
https://lists.apache.org/thread.html/r0e076ffb20dbf80ee3e60c61f37cee69aa648c4860182ecfabb3abbf%40%3Cdiversity.apache.org%3E.
 Thanks Gabriel for initiating this discussion.

If you are interested in further diversity discussions at Apache, subscribe to 
the mailing lists mentioned here: https://diversity.apache.org/.

Recently, some words/terms are updated here: 
https://cwiki.apache.org/confluence/display/EDI/Nomenclature+alternatives.

- Should there be git hooks similar to scan for such terms?
=> I think, No need of hooks for such terms.

- How about when upstream projects use a inappropriate term? (for external / 
third party projects, MySQL, network interfaces)
=> the third party / dependency libraries, the terminologies used from external 
systems are excluded from this change.

Regards,
Suresh

On 03/05/21, 10:54 AM, "Suresh Anaparti"  wrote:

Hi Nathan,

Thanks for your feedback. I'll update the PR(s) as necessary.

You can added your comments to the PR directly, so that these can be 
tracked and discussed there. Please note we'll go ahead with this rename change 
only after passing through the first step i.e. "Accepting all the CloudStack 
repo's (rename) PRs".

Coming to the changes (over 5000 files) in repo "cloudstack-www", these are 
mainly the html pages in the apidocs with different CloudStack versions (may be 
unmaintained now, will check what can be done there).

Regards,
Suresh





 

On 30/04/21, 9:23 PM, "Nathan McGarvey"  wrote:

+1, -1, and +0:

   Overall idea: +1  (Agree with Rene regarding context being important,
too.)


   Some specific pull requests: -1 or 0:

   -1: How is this related? It seems to be a commit that shouldn't
have been a part of this pull request since it is a brand new file that
is unrelated:

https://github.com/apache/cloudstack-www/pull/83/commits/9545ce619b377326daae5b303ffe89b5ea90a288


+0 or -1: I can't reasonably review this:

https://github.com/apache/cloudstack-www/pull/83/commits/9ce732ceeb47bf6dee73073d892a51fbeea39f09
as it changed over 5000 files going back many many years in the past to
now-dead/unmaintained code. This is a huge repo-bloat commit of doom.
(You're changing API docs for dead code on something that can't even be
manually reviewed). I'd suggest just adding an explanatory file for
unsupported releases instead of changing thousands of files that are a
decade old. Maybe even removing old API docs would be an option. Or just
change the latest X releases, and gracefully age off the old ones.
(Related: How much bigger does this make the git repo and how much
longer does it take to apply diffs when cloning?)


Other questions/comments:

Is there a overarching ASF criteria for what words are
inappropriate for future development?

Should there be git hooks similar to scan for such terms?

How about when upstream projects use a inappropriate term? E.g.
MySQL pre-8.0.23 uses "master" in their configs, variables, and
documents, but uses "replication source" or "replica", etc. after that
point in time. (Ref:

https://dev.mysql.com/doc/refman/8.0/en/binlog-replication-configuration-overview.html)
Having a disjuncture between the implementation code and the upstream
project makes it really hard to cross-reference documentation. The
client/conf/db.properties.in file was changed to be db.cloud.backup, but
why not make that db.cloud.replica or something that lines up with their
documentation? Another example is with network interfaces. The "slave"
term is different than the proposed "secondary" in Linux. A secondary
interface actually means an alias or a fully separate physical device.
Maybe "member device" or something is more correct.



Thanks,
-Nathan McGarvey



On 4/30/21 6:43 AM, Suresh Anaparti wrote:
> Hi All,
> 
> Following the discussion thread on renaming default git branch name 
and inclusiveness [1], I would like to start a vote to gather consensus on the 
following plan:
> 
> 1. Accept the following rename PRs (raised against 'master' branch) 
which renames git default branch to 'main' and replaces some offensive

Re: [VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness

[Suresh Anaparti]

+1 , adding my vote as well.

Regards,
Suresh


 

On 07/05/21, 2:10 PM, "Harikrishna Patnala"  
wrote:

+1  from me.

Regards,
Harikrishna

From: Suresh Anaparti 
Sent: Friday, April 30, 2021 5:13 PM
To: d...@cloudstack.apache.org ; 
priv...@cloudstack.apache.org 
Cc: users@cloudstack.apache.org 
Subject: [VOTE] Renaming default git branch name from 'master' to 'main' 
and replace offensive words as appropriate for inclusiveness

Hi All,

Following the discussion thread on renaming default git branch name and 
inclusiveness [1], I would like to start a vote to gather consensus on the 
following plan:

1. Accept the following rename PRs (raised against 'master' branch) which 
renames git default branch to 'main' and replaces some offensive words, and 
Merge them post acceptance.
- cloudstack => PR: https://github.com/apache/cloudstack/pull/4922
- cloudstack-documentation => PR: 
https://github.com/apache/cloudstack-documentation/pull/155
- cloudstack-www => PR: 
https://github.com/apache/cloudstack-www/pull/83
- cloudstack-cloudmonkey => PR: 
https://github.com/apache/cloudstack-cloudmonkey/pull/76
- cloudstack-kubernetes-provider => PR: 
https://github.com/apache/cloudstack-kubernetes-provider/pull/29
- cloudstack-ec2stack => PR: 
https://github.com/apache/cloudstack-ec2stack/pull/2
- cloudstack-gcestack => PR: 
https://github.com/apache/cloudstack-gcestack/pull/3

2. Request ASF infra to disable pushes to 'master' branch.

3. Rename 'master' branch to 'main' [2][3], and Request ASF infra (open 
INFRA ticket) to make 'main' as the default branch [4], in GitHub repo settings 
for all the CloudStack repos. This will also re-target the current PRs against 
'master' branch to 'main'.

3a. The update on the central repo will be done as follows (only by a PMC 
or Infra member with access)
- Clone the repo (git clone 
https://github.com/apache/cloudstack.git)
- Sync local 'master' with the cloudstack repo (cd cloudstack && 
git checkout master && git fetch --all -p && git pull)
- Rename local 'master' branch to 'main' (git branch -m master main)
- Push renamed 'main' branch (git push -u origin main)
- Update Default Branch on GitHub [4]
- Delete 'master' branch (git push origin --delete master)
3b. After the central renaming has been done. New users can clone and 
directly checkout 'main' branch. Existing users can start using 'main' locally, 
using the below steps.
- Switch to master branch (git checkout master)
- Rename local 'master' branch to 'main' (git branch -m master main)
- Sync local 'main' with repo (git fetch)
- Remove the existing tracking connection with “origin/master” (git 
branch --unset-upstream)
- Create a new tracking connection with the new “origin/main” 
branch (git branch -u origin/main)
- All local branches should still point to the same commit as base 
revision. If there is a problem (git checkout  && git 
rebase main)

4. Update the integrated systems with CloudStack repos, mainly Travis CI 
and Jenkins configuration with 'main' branch. Check and update UI building, 
apidocs, systemvmtemplate builds; project website and docs (cwiki); and any 
other build/release jobs. Track them through the issue: 
https://github.com/apache/cloudstack/issues/4887.

5. Perform Health Checks (using a dummy PR), and ensure there are no issues 
with the build/release configuration. This PR needs to run full matrix of 
tests. Fix the issues noticed during the health checks.

6. Announce the default branch change to 'main' (and 'master' deprecation) 
on the mailing list.

The vote will be open until Fri 7th May 2021.

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)

[1] https://markmail.org/message/k767evgjnmzogyhf
[2] https://github.com/github/renaming
[3] 
https://docs.github.com/en/github/administering-a-repository/renaming-a-branch
[4] 
https://docs.github.com/en/github/administering-a-repository/changing-the-default-branch

Regards,
Suresh

Re: [VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness

[Suresh Anaparti]

 > > longer does it take to apply diffs when cloning?)
> >
> >
> > Other questions/comments:
> >
> > Is there a overarching ASF criteria for what words are
> > inappropriate for future development?
> >
> > Should there be git hooks similar to scan for such terms?
> >
> > How about when upstream projects use a inappropriate term? E.g.
> > MySQL pre-8.0.23 uses "master" in their configs, variables, and
> > documents, but uses "replication source" or "replica", etc. after that
> > point in time. (Ref:
> >
> >
> 
https://dev.mysql.com/doc/refman/8.0/en/binlog-replication-configuration-overview.html
> > )
> > Having a disjuncture between the implementation code and the upstream
> > project makes it really hard to cross-reference documentation. The
    > > client/conf/db.properties.in file was changed to be db.cloud.backup, but
> > why not make that db.cloud.replica or something that lines up with their
> > documentation? Another example is with network interfaces. The "slave"
> > term is different than the proposed "secondary" in Linux. A secondary
> > interface actually means an alias or a fully separate physical device.
> > Maybe "member device" or something is more correct.
> >
> >
> >
> > Thanks,
> > -Nathan McGarvey
> >
> >
> >
> > On 4/30/21 6:43 AM, Suresh Anaparti wrote:
> > > Hi All,
> > >
> > > Following the discussion thread on renaming default git branch name 
and
> > inclusiveness [1], I would like to start a vote to gather consensus on
> the
> > following plan:
> > >
> > > 1. Accept the following rename PRs (raised against 'master' branch)
> > which renames git default branch to 'main' and replaces some offensive
> > words, and Merge them post acceptance.
> > >   - cloudstack => PR:
> https://github.com/apache/cloudstack/pull/4922
> > >   - cloudstack-documentation => PR:
> > https://github.com/apache/cloudstack-documentation/pull/155
> > >   - cloudstack-www => PR:
> > https://github.com/apache/cloudstack-www/pull/83
> > >   - cloudstack-cloudmonkey => PR:
> > https://github.com/apache/cloudstack-cloudmonkey/pull/76
> > >   - cloudstack-kubernetes-provider => PR:
> > https://github.com/apache/cloudstack-kubernetes-provider/pull/29
> > >   - cloudstack-ec2stack => PR:
> > https://github.com/apache/cloudstack-ec2stack/pull/2
> > >   - cloudstack-gcestack => PR:
> > https://github.com/apache/cloudstack-gcestack/pull/3
> > >
> > > 2. Request ASF infra to disable pushes to 'master' branch.
> > >
> > > 3. Rename 'master' branch to 'main' [2][3], and Request ASF infra 
(open
> > INFRA ticket) to make 'main' as the default branch [4], in GitHub repo
> > settings for all the CloudStack repos. This will also re-target the
> current
> > PRs against 'master' branch to 'main'.
> > >
> > > 3a. The update on the central repo will be done as follows (only by a
> > PMC or Infra member with access)
> > >   - Clone the repo (git clone
> > https://github.com/apache/cloudstack.git)
> > >   - Sync local 'master' with the cloudstack repo (cd cloudstack &&
> > git checkout master && git fetch --all -p && git pull)
> > >   - Rename local 'master' branch to 'main' (git branch -m master
> > main)
> > >   - Push renamed 'main' branch (git push -u origin main)
> > >   - Update Default Branch on GitHub [4]
> > >   - Delete 'master' branch (git push origin --delete master)
> > > 3b. After the central renaming has been done. New users can clone and
> > directly checkout 'main' branch. Existing users can start using 'main'
> > locally, using the below steps.
> > >   - Switch to master branch (git checkout master)
> > >   - Rename local 'master' branch to 'main' (git branch -m master
> > main)
> > >   - Sync local 'main' with repo (git fetch)
> > >   - Remove the existing tracking connection with “origin/master”
> > (git branch --unset-upstream)
> > >   - Create a new tracking connection w

Re: [VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness

[Suresh Anaparti]

Hi Nathan,

Thanks for your feedback. I'll update the PR(s) as necessary.

You can added your comments to the PR directly, so that these can be tracked 
and discussed there. Please note we'll go ahead with this rename change only 
after passing through the first step i.e. "Accepting all the CloudStack repo's 
(rename) PRs".

Coming to the changes (over 5000 files) in repo "cloudstack-www", these are 
mainly the html pages in the apidocs with different CloudStack versions (may be 
unmaintained now, will check what can be done there).

Regards,
Suresh


 

On 30/04/21, 9:23 PM, "Nathan McGarvey"  wrote:

+1, -1, and +0:

   Overall idea: +1  (Agree with Rene regarding context being important,
too.)


   Some specific pull requests: -1 or 0:

   -1: How is this related? It seems to be a commit that shouldn't
have been a part of this pull request since it is a brand new file that
is unrelated:

https://github.com/apache/cloudstack-www/pull/83/commits/9545ce619b377326daae5b303ffe89b5ea90a288


+0 or -1: I can't reasonably review this:

https://github.com/apache/cloudstack-www/pull/83/commits/9ce732ceeb47bf6dee73073d892a51fbeea39f09
as it changed over 5000 files going back many many years in the past to
now-dead/unmaintained code. This is a huge repo-bloat commit of doom.
(You're changing API docs for dead code on something that can't even be
manually reviewed). I'd suggest just adding an explanatory file for
unsupported releases instead of changing thousands of files that are a
decade old. Maybe even removing old API docs would be an option. Or just
change the latest X releases, and gracefully age off the old ones.
(Related: How much bigger does this make the git repo and how much
longer does it take to apply diffs when cloning?)


Other questions/comments:

Is there a overarching ASF criteria for what words are
inappropriate for future development?

Should there be git hooks similar to scan for such terms?

How about when upstream projects use a inappropriate term? E.g.
MySQL pre-8.0.23 uses "master" in their configs, variables, and
documents, but uses "replication source" or "replica", etc. after that
point in time. (Ref:

https://dev.mysql.com/doc/refman/8.0/en/binlog-replication-configuration-overview.html)
Having a disjuncture between the implementation code and the upstream
project makes it really hard to cross-reference documentation. The
client/conf/db.properties.in file was changed to be db.cloud.backup, but
why not make that db.cloud.replica or something that lines up with their
documentation? Another example is with network interfaces. The "slave"
term is different than the proposed "secondary" in Linux. A secondary
interface actually means an alias or a fully separate physical device.
Maybe "member device" or something is more correct.



Thanks,
-Nathan McGarvey



On 4/30/21 6:43 AM, Suresh Anaparti wrote:
> Hi All,
> 
> Following the discussion thread on renaming default git branch name and 
inclusiveness [1], I would like to start a vote to gather consensus on the 
following plan:
> 
> 1. Accept the following rename PRs (raised against 'master' branch) which 
renames git default branch to 'main' and replaces some offensive words, and 
Merge them post acceptance.
>   - cloudstack => PR: https://github.com/apache/cloudstack/pull/4922
>   - cloudstack-documentation => PR: 
https://github.com/apache/cloudstack-documentation/pull/155
>   - cloudstack-www => PR: https://github.com/apache/cloudstack-www/pull/83
>   - cloudstack-cloudmonkey => PR: 
https://github.com/apache/cloudstack-cloudmonkey/pull/76
>   - cloudstack-kubernetes-provider => PR: 
https://github.com/apache/cloudstack-kubernetes-provider/pull/29
>   - cloudstack-ec2stack => PR: 
https://github.com/apache/cloudstack-ec2stack/pull/2
>   - cloudstack-gcestack => PR: 
https://github.com/apache/cloudstack-gcestack/pull/3
> 
> 2. Request ASF infra to disable pushes to 'master' branch.
> 
> 3. Rename 'master' branch to 'main' [2][3], and Request ASF infra (open 
INFRA ticket) to make 'main' as the default branch [4], in GitHub repo settings 
for all the CloudStack repos. This will also re-target the current PRs against 
'master' branch to 'main'.
> 
> 3a. The update on the central repo will be done as follows (only by a PMC 
or Infra member with access)
>   - Clone the repo (git clone https://github.com/apache/cloudstack.git)
>   - Sync local 'master' with the cloudstack repo (cd cloudstack && git 
checkout master && git fetch --all -p && git pull)
>   - Rename local 'm

[VOTE] Renaming default git branch name from 'master' to 'main' and replace offensive words as appropriate for inclusiveness

[Suresh Anaparti]

Hi All,

Following the discussion thread on renaming default git branch name and 
inclusiveness [1], I would like to start a vote to gather consensus on the 
following plan:

1. Accept the following rename PRs (raised against 'master' branch) which 
renames git default branch to 'main' and replaces some offensive words, and 
Merge them post acceptance.
- cloudstack => PR: https://github.com/apache/cloudstack/pull/4922
- cloudstack-documentation => PR: 
https://github.com/apache/cloudstack-documentation/pull/155
- cloudstack-www => PR: https://github.com/apache/cloudstack-www/pull/83
- cloudstack-cloudmonkey => PR: 
https://github.com/apache/cloudstack-cloudmonkey/pull/76
- cloudstack-kubernetes-provider => PR: 
https://github.com/apache/cloudstack-kubernetes-provider/pull/29
- cloudstack-ec2stack => PR: 
https://github.com/apache/cloudstack-ec2stack/pull/2
- cloudstack-gcestack => PR: 
https://github.com/apache/cloudstack-gcestack/pull/3

2. Request ASF infra to disable pushes to 'master' branch.

3. Rename 'master' branch to 'main' [2][3], and Request ASF infra (open INFRA 
ticket) to make 'main' as the default branch [4], in GitHub repo settings for 
all the CloudStack repos. This will also re-target the current PRs against 
'master' branch to 'main'.

3a. The update on the central repo will be done as follows (only by a PMC or 
Infra member with access)
- Clone the repo (git clone https://github.com/apache/cloudstack.git)
- Sync local 'master' with the cloudstack repo (cd cloudstack && git 
checkout master && git fetch --all -p && git pull)
- Rename local 'master' branch to 'main' (git branch -m master main)
- Push renamed 'main' branch (git push -u origin main)
- Update Default Branch on GitHub [4]
- Delete 'master' branch (git push origin --delete master)
3b. After the central renaming has been done. New users can clone and directly 
checkout 'main' branch. Existing users can start using 'main' locally, using 
the below steps.
- Switch to master branch (git checkout master)
- Rename local 'master' branch to 'main' (git branch -m master main)
- Sync local 'main' with repo (git fetch)
- Remove the existing tracking connection with “origin/master” (git 
branch --unset-upstream)
- Create a new tracking connection with the new “origin/main” branch 
(git branch -u origin/main)
- All local branches should still point to the same commit as base 
revision. If there is a problem (git checkout  && git 
rebase main)

4. Update the integrated systems with CloudStack repos, mainly Travis CI and 
Jenkins configuration with 'main' branch. Check and update UI building, 
apidocs, systemvmtemplate builds; project website and docs (cwiki); and any 
other build/release jobs. Track them through the issue: 
https://github.com/apache/cloudstack/issues/4887.

5. Perform Health Checks (using a dummy PR), and ensure there are no issues 
with the build/release configuration. This PR needs to run full matrix of 
tests. Fix the issues noticed during the health checks.

6. Announce the default branch change to 'main' (and 'master' deprecation) on 
the mailing list.

The vote will be open until Fri 7th May 2021.

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)

[1] https://markmail.org/message/k767evgjnmzogyhf
[2] https://github.com/github/renaming
[3] 
https://docs.github.com/en/github/administering-a-repository/renaming-a-branch
[4] 
https://docs.github.com/en/github/administering-a-repository/changing-the-default-branch

Regards,
Suresh


 

Re: [VOTE] New life to Terraform Provider CloudStack with Apache CloudStack project

[Suresh Anaparti]

+1 , on this new repo under Apache. Hope the community takes it forward, with 
further improvements and maintenance of this provider.

Regards,
Suresh

On 15/04/21, 2:35 PM, "Rohit Yadav"  wrote:

Hi All,

Following the discussion thread on Terraform [1], I would like to start a 
vote to gather consensus on the following actions:

  1.  Create a new "cloudstack-terraform-provider" repository based on 
Apache Licence v2.0 using re-licensed codebase of the archived/former terraform 
cloudstack provider repository: 
https://github.com/hashicorp/terraform-provider-cloudstack (note: re-licensing 
from MPL to AL will be done by Hashicorp)
  2.  Request ASF infra to enable issues, PR, and wiki features on the 
repository
  3.  Work with the community towards any further maintenance, development, 
and releases of the provider
  4.  Publish official releases on the official registry [2] if/after 
Apache CloudStack project gets a verified account (published by PMC members 
with access to the registry, or following guidelines from ASF infra if they've 
any)

The vote will be open for 120 hours, until Wed 21 April 2021.
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)

[1] https://markmail.org/message/iuggxin7kj6ri4hb
[2] https://registry.terraform.io/browse/providers


Regards.

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





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

Re: Congratulations to Sven - Apache Software Foundation Member

[Suresh Anaparti]

Congratulations Sven


Regards,
Suresh

On 18/03/21, 2:44 AM, "Paul Angus"  wrote:

Hi All,



More great news.



Please join me in congratulating Sven,  for being made a Member of the
Apache Software Foundation. 



Congratulations Sven, keep up the good work!



Kind regards



Paul Angus





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

Re: Congratulations to Gabriel - CloudStack PMC Chair

[Suresh Anaparti]

Congratulations Gabriel.

Regards,
Suresh

On 18/03/21, 2:42 AM, "Paul Angus"  wrote:

Hi All CloudStack enthusiasts!



Please join me in congratulating Gabriel for becoming the next CloudStack
PMC Chair.

Congratulations Gabriel, very well deserved!



I would also like to thank Sven for his great work of the past year!







Kind regards



Paul Angus





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

Re: Goggle Summer of Code 2021

[Suresh Anaparti]

Hi,



I would like to propose the idea of Cloning a Virtual Machine (with all the 
data disks) – using a new VM cmd (cloneVirtualMachine API) to create a copy of 
the VM. This will ease creating a copy of the VM without following series of 
API cmds to achieve that in CloudStack. Some hypervisors (Eg. VMware) already 
supports clone VM operation, and CloudStack can leverage that. This will be a 
good addition to the VM operations supported in CloudStack. More details here: 
https://github.com/apache/cloudstack/issues/4818



Regards,

Suresh



On 16/02/21, 3:00 PM, "Giles Sirett"  wrote:



Hi all



It would be great if the CloudStack project were able to get a few Google 
Summer of Code  [1] students this year to work on projects within our 
community. We've had a number of previous GSoC students (examples at [2] ), who 
have worked on innovative features/ projects within cloudstack and have then 
gone on to become significant contributors to Cloudstack .





In order to be able to attract students to work on Cloudstack, we need 2 
things:



  1.  A number of candidate projects for students to work on. Students 
browse all GSoC the candidate projects and choose one that interests them- 
effectively every organisation is competing for the students interest.  These 
projects therefore need to be reasonably interesting looking projects to 
attract potential students. The students spend approximately 9 weeks coding, so 
the projects need to be appropriately scaled

  2.  Somebody prepared to mentor the student throughout the duration of 
the project (usually the person who suggests the project)



The student application period starts 29 March [3]

The ASF  has registered itself as a mentor  organisation with Google , 
allowing individual Apache projects to list candidate projects  for students to 
work on. A wiki page [4]  has been created at the ASF level to allow ASF 
projects to  list their ideas for students





I'm happy to coordinate this from a Cloudstack perspective.

If others are happy with this approach, then I ask for two things at this 
stage:





  1.  Could people suggest appropriate projects. This could be a piece of 
integration that you've always considered and not got around to or could be an 
improvement that you've always wanted to do. If people can reply to this thread 
with ANY ideas, it would be a good start (irrespective of whether you wish to 
be a mentor or not)

  2.  At the same time, could people say whether they'd be prepared to be a 
student mentor or not









[1] https://summerofcode.withgoogle.com/





[2]


https://blog.netapp.com/blogs/mentoring-with-google-summer-of-code-and-lessons-in-cloudstack/

https://dzone.com/articles/cloudstack-google-summer-code


https://opensource.googleblog.com/2014/07/gsoc-students-create-google-compute.html





[3]https://summerofcode.withgoogle.com/how-it-works/#timeline



[4] https://cwiki.apache.org/confluence/display/COMDEV/GSoC+2021+Ideas+list







Kind regards

Giles





giles.sir...@shapeblue.com

www.shapeblue.com

3 London Bridge Street,  3rd floor, News Building, London  SE1 9SGUK

@shapeblue







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

Re: [ANNOUNCE] new committer: Nguyen Mai Hoang

[Suresh Anaparti]

Congrats Hoang!

Regards,
Suresh

On 18/11/20, 4:19 AM, "Sven Vogel"  wrote:

Hi everyone,



 The Project Management Committee (PMC) for Apache CloudStack
has invited Nguyen Mai Hoang to become a committer and we are pleased 
to announce that he has accepted.

Please join me in congratulating Hoang on this accomplishment.


Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.


Thanks and Cheers,



Sven Vogel
Apache CloudStack PMC member


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

Re: [ANNOUNCE] new committer: Rakesh Venkatesh

[Suresh Anaparti]

Congrats Rakesh!

Regards,
Suresh

On 18/11/20, 4:18 AM, "Sven Vogel"  wrote:

Hi everyone,



 The Project Management Committee (PMC) for Apache CloudStack
has invited Rakesh Venkatesh to become a committer and we are pleased

to announce that he has accepted.

Please join me in congratulating Rakesh on this accomplishment.


Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.


Thanks and Cheers,



Sven Vogel
Apache CloudStack PMC member


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

Re: [ANNOUNCE] new committer: Abhishek Kumar

[Suresh Anaparti]

Congrats Abhishek...

Regards,
Suresh

On 18/11/20, 4:18 AM, "Sven Vogel"  wrote:

Hi everyone, 


The Project Management Committee (PMC) for Apache CloudStack
has invited Abhishek Kumar to become a committer and we are pleased 
to announce that he has accepted.

Please join me in congratulating Abhishek on this accomplishment.


Being a committer enables easier contribution to the
project since there is no need to go via the patch
submission process. This should enable better productivity.




Thanks and Cheers,



Sven Vogel
Apache CloudStack PMC member


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

Re: New Joiner

[Suresh Anaparti]

Hi Hoang, Welcome to the community!

Regards,
Suresh

On 04/11/20, 5:25 PM, "Pearl d'Silva"  wrote:

Welcome Hoang!

Regards,
Pearl Dsilva


From: Abhishek Kumar 
Sent: Wednesday, November 4, 2020 5:23 PM
To: d...@cloudstack.apache.org ; 
users@cloudstack.apache.org 
Subject: Re: New Joiner

Hi,

Welcome Hoang!

Regards,
Abhishek

From: Unitech Mai Nguyen 
Sent: 04 November 2020 08:01
To: users@cloudstack.apache.org ; 
d...@cloudstack.apache.org 
Cc: sven.vo...@qform.de 
Subject: New Joiner

Hello Everyone,

My name is Hoang and I'm currently working for Ewerk.
It is my great pleasure to have a chance to join the Cloudstack Primate 
project.
It has been a wonderful time for me since last December when I started my 
first task.

I would look forward to being a part of this team for a long time to go. 
And I hope to have your kind help.
Thank you so much.
__
Hoang Nguyen
Frontend Developer

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P +49 341 42649 - 99
F +49 341 42649 - 98

www.ewerk.xn--com-zq0a>

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Frank Richter
Registergericht: Leipzig HRB 9065

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

__

Unitech Mai Nguyen
Frontend Developer

EWERK DIGITAL GmbH
Brühl 24, D-04109 Leipzig
P
F +49 341 42649 - 98
hoang.ngu...@ewerk.com
www.ewerk.com

Geschäftsführer:
Dr. Erik Wende, Hendrik Schubert, Tassilo Möschke
Registergericht: Leipzig HRB 9065

Support:
+49 341 42649 555

Zertifiziert nach:
ISO/IEC 27001:2013
DIN EN ISO 9001:2015
DIN ISO/IEC 2-1:2011

ISAE 3402 Typ II Assessed

EWERK-Blog | 
LinkedIn | 
Xing | 
Twitter | 
Facebook


Auskünfte und Angebote per Mail sind freibleibend und unverbindlich.

Disclaimer Privacy:
Der Inhalt dieser E-Mail (einschließlich etwaiger beigefügter Dateien) ist 
vertraulich und nur für den Empfänger bestimmt. Sollten Sie nicht der 
bestimmungsgemäße Empfänger sein, ist Ihnen jegliche Offenlegung, 
Vervielfältigung, Weitergabe oder Nutzung des Inhalts untersagt. Bitte 
informieren Sie in diesem Fall unverzüglich den Absender und löschen Sie die 
E-Mail (einschließlich etwaiger beigefügter Dateien) von Ihrem System. Vielen 
Dank.

The contents of this e-mail (including any attachments) are confidential 
and may be legally privileged. If you are not the intended recipient of this 
e-mail, any disclosure, copying, distribution or use of its contents is 
strictly prohibited, and you should please notify the sender immediately and 
then delete it (including any attachments) from your system. Thank you.

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




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





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