Reg. OAuth2 integration in CloudStack
Hi all, These days I’m working on a new feature to enable OAuth2 logins in CloudStack assuming corresponding account/user is already created in CloudStack. Currently I’ve made it work with Google and Github. I’m here to ask for any suggestions or quick information on how you are using OAuth in enterprise products. 1. Any other default OAuth providers would you like to have like Microsoft or Apple (I already have it working with Google and Github) 2. Any known single package (that supports vue and java) that gives a way to configure all OAuth2 providers? I tried with “vue3-social-login” but for some reasons I could not make it work. Currently it is in development stage but looks something like below [cid:image001.png@01D9DFDD.2937A7A0] Thanks, Harikrishna
Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)
Top job! PS: I know technically we cover this by invoking "-R" in the docs example, but do you think the issue warrants dropping few words in there to underline the issue? Something like "do note the -R switch which backs up the MySQL database routines" On 2023-09-04 15:22, Rohit Yadav wrote: Wei pointed out privately to me that it's already in our docs at https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.17.html#database-preparation My bad, I didn't notice it earlier :) Regards. From: Nux Sent: Monday, September 4, 2023 19:44 To: dev@cloudstack.apache.org Cc: users Subject: Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2) Cheers Rohit, I'm for including the routines bit in the release or upgrade notes. We haven't had such a gotcha until now, even though it's not strictly within scope. Regards On 2023-09-04 14:03, Rohit Yadav wrote: +1 (binding) Upgraded a multi-zone (edge and core) KVM env with NFS, local storage and Linstor storage from 4.18.0.0 to 4.18.1.0. Post upgrade tested VM deployment as root admin and normal user account. I hit the issue of procedures not found as I had moved my DB from one host to another and didn't export the routines using mysqldump -R flag. I could apply them manually courtesy of Wei. I think we should document this that people moving their DBs must also backup/dump the routines (procedures), though I don't think that's a usual thing that users would normally do - and is outside of scope of CloudStack. Regards. From: Wei ZHOU Sent: Friday, September 1, 2023 13:09 To: dev@cloudstack.apache.org ; users Subject: [VOTE] Apache CloudStack 4.18.1.0 (RC2) Hi all, I've created a 4.18.1.0-RC2, with the following artifacts up for a vote: Git Branch and Commit SH: https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817 Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c Source release (checksums and signatures are available at the following location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/ PGP release keys (signed using 1503DFE7C8226103): https://dist.apache.org/repos/dist/release/cloudstack/KEYS 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)
Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)
Wei pointed out privately to me that it's already in our docs at https://docs.cloudstack.apache.org/en/latest/upgrading/upgrade/upgrade-4.17.html#database-preparation My bad, I didn't notice it earlier :) Regards. From: Nux Sent: Monday, September 4, 2023 19:44 To: dev@cloudstack.apache.org Cc: users Subject: Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2) Cheers Rohit, I'm for including the routines bit in the release or upgrade notes. We haven't had such a gotcha until now, even though it's not strictly within scope. Regards On 2023-09-04 14:03, Rohit Yadav wrote: > +1 (binding) > > Upgraded a multi-zone (edge and core) KVM env with NFS, local storage > and Linstor storage from 4.18.0.0 to 4.18.1.0. Post upgrade tested VM > deployment as root admin and normal user account. > > I hit the issue of procedures not found as I had moved my DB from one > host to another and didn't export the routines using mysqldump -R flag. > I could apply them manually courtesy of Wei. I think we should document > this that people moving their DBs must also backup/dump the routines > (procedures), though I don't think that's a usual thing that users > would normally do - and is outside of scope of CloudStack. > > > > Regards. > > > From: Wei ZHOU > Sent: Friday, September 1, 2023 13:09 > To: dev@cloudstack.apache.org ; users > > Subject: [VOTE] Apache CloudStack 4.18.1.0 (RC2) > > Hi all, > > I've created a 4.18.1.0-RC2, with the following artifacts up for a > vote: > > Git Branch and Commit SH: > https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817 > Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c > > Source release (checksums and signatures are available at the following > location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/ > > PGP release keys (signed using 1503DFE7C8226103): > https://dist.apache.org/repos/dist/release/cloudstack/KEYS > > 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)
Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)
Cheers Rohit, I'm for including the routines bit in the release or upgrade notes. We haven't had such a gotcha until now, even though it's not strictly within scope. Regards On 2023-09-04 14:03, Rohit Yadav wrote: +1 (binding) Upgraded a multi-zone (edge and core) KVM env with NFS, local storage and Linstor storage from 4.18.0.0 to 4.18.1.0. Post upgrade tested VM deployment as root admin and normal user account. I hit the issue of procedures not found as I had moved my DB from one host to another and didn't export the routines using mysqldump -R flag. I could apply them manually courtesy of Wei. I think we should document this that people moving their DBs must also backup/dump the routines (procedures), though I don't think that's a usual thing that users would normally do - and is outside of scope of CloudStack. Regards. From: Wei ZHOU Sent: Friday, September 1, 2023 13:09 To: dev@cloudstack.apache.org ; users Subject: [VOTE] Apache CloudStack 4.18.1.0 (RC2) Hi all, I've created a 4.18.1.0-RC2, with the following artifacts up for a vote: Git Branch and Commit SH: https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817 Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c Source release (checksums and signatures are available at the following location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/ PGP release keys (signed using 1503DFE7C8226103): https://dist.apache.org/repos/dist/release/cloudstack/KEYS 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)
Re: [VOTE] Apache CloudStack 4.18.1.0 (RC2)
+1 (binding) Upgraded a multi-zone (edge and core) KVM env with NFS, local storage and Linstor storage from 4.18.0.0 to 4.18.1.0. Post upgrade tested VM deployment as root admin and normal user account. I hit the issue of procedures not found as I had moved my DB from one host to another and didn't export the routines using mysqldump -R flag. I could apply them manually courtesy of Wei. I think we should document this that people moving their DBs must also backup/dump the routines (procedures), though I don't think that's a usual thing that users would normally do - and is outside of scope of CloudStack. Regards. From: Wei ZHOU Sent: Friday, September 1, 2023 13:09 To: dev@cloudstack.apache.org ; users Subject: [VOTE] Apache CloudStack 4.18.1.0 (RC2) Hi all, I've created a 4.18.1.0-RC2, with the following artifacts up for a vote: Git Branch and Commit SH: https://github.com/apache/cloudstack/commits/4.18.1.0-RC20230901T0817 Commit: 0e7f7d42f0ec68a360fafa7de21ea06577ed032c Source release (checksums and signatures are available at the following location):https://dist.apache.org/repos/dist/dev/cloudstack/4.18.1.0/ PGP release keys (signed using 1503DFE7C8226103): https://dist.apache.org/repos/dist/release/cloudstack/KEYS 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)
Unable to deploy vm instance
Hello,
Unable to deploy vm instance,
My server is alam 8.
1. MGMT+NFS
2. KVM
+
Unable to start a VM [55d71859-ae54-4e12-8de3-8f84fe9627bf] due to
[Unable to create a deployment for VM instance
{"id":15,"instanceName":"i-2-15-VM","type":"User","uuid":"55d71859-ae54-4e12-8de3-8f84fe9627bf"}].
+
MGMT server log
++
2023-09-04 14:53:15,711 DEBUG [c.c.a.ApiServlet]
(qtp649329985-505:ctx-d4b80649) (logid:550584ab) ===START=== 10.66.10.22
-- GET
zoneid=cd6b9366-3982-42be-b3b2-8c4361239e4f=97b8385b-baf9-4818-97b1-4ca141dcddce=94385c60-5970-447c-926b-11653ac04a5a=7cad36ca-ddb9-404f-99ae-4f9f446138d8=BIOS=LEGACY=0b13fe5d-af8a-4247-b473-20fb19723a9a=KVM=true=d13efba9-4f06-429c-a697-7a46a7c0f9b4=961fd360-ca5e-4d2a-9813-cbd9eb392412==3388fc57-4a57-11ee-acdf-08002737abca==deployVirtualMachine=json
2023-09-04 14:53:15,711 DEBUG [c.c.a.ApiServlet]
(qtp649329985-505:ctx-d4b80649) (logid:550584ab) Two factor
authentication is already verified for the user 2, so skipping
2023-09-04 14:53:15,729 DEBUG [c.c.a.ApiServer]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) CIDRs from
which account 'Account
[{"accountName":"admin","id":2,"uuid":"33862365-4a57-11ee-acdf-08002737abca"}]'
is allowed to perform API calls: 0.0.0.0/0,::/0
2023-09-04 14:53:15,736 INFO [o.a.c.a.DynamicRoleBasedAPIAccessChecker]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) Account
[Account
[{"accountName":"admin","id":2,"uuid":"33862365-4a57-11ee-acdf-08002737abca"}]]
is Root Admin or Domain Admin, all APIs are allowed.
2023-09-04 14:53:15,738 WARN [o.a.c.a.ProjectRoleBasedApiAccessChecker]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) Project is
null, ProjectRoleBasedApiAccessChecker only applies to projects,
returning API [deployVirtualMachine] for user [User
{"username":"admin","uuid":"33884ade-4a57-11ee-acdf-08002737abca"}.] as
allowed.
2023-09-04 14:53:15,742 DEBUG [o.a.c.a.StaticRoleBasedAPIAccessChecker]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab)
RoleService is enabled. We will use it instead of
StaticRoleBasedAPIAccessChecker.
2023-09-04 14:53:15,744 DEBUG [o.a.c.r.ApiRateLimitServiceImpl]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) API rate
limiting is disabled. We will not use ApiRateLimitService.
2023-09-04 14:53:15,815 DEBUG [c.c.u.AccountManagerImpl]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) Access
granted to Account
[{"accountName":"admin","id":2,"uuid":"33862365-4a57-11ee-acdf-08002737abca"}]
to
org.apache.cloudstack.quota.vo.ServiceOfferingVO$$EnhancerByCGLIB$$24a01240@4ca3d6c4
by AffinityGroupAccessChecker
2023-09-04 14:53:15,820 DEBUG [c.c.u.AccountManagerImpl]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) Access
granted to Account
[{"accountName":"admin","id":2,"uuid":"33862365-4a57-11ee-acdf-08002737abca"}]
to com.cloud.storage.DiskOfferingVO$$EnhancerByCGLIB$$cd698f33@64fe404
by AffinityGroupAccessChecker
2023-09-04 14:53:16,073 INFO [c.c.v.UserVmManagerImpl]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) VM cannot
be configured to be dynamically scalable if any of the service
offering's dynamic scaling property, template's dynamic scaling property
or global setting is false
2023-09-04 14:53:16,078 DEBUG [c.c.v.UserVmManagerImpl]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab)
Rootdisksize override validation successful. Template root disk size
(1.13 GB) 1215168512 Root disk size specified 20 GB
2023-09-04 14:53:16,084 DEBUG [c.c.v.UserVmManagerImpl]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) Allocating
in the DB for vm
2023-09-04 14:53:16,104 INFO [c.c.v.VirtualMachineManagerImpl]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) allocating
virtual machine from template:0b13fe5d-af8a-4247-b473-20fb19723a9a with
hostname:i-2-15-VM and 1 networks
2023-09-04 14:53:16,110 DEBUG [c.c.v.VirtualMachineManagerImpl]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) Allocating
entries for VM: VM instance
{"id":15,"instanceName":"i-2-15-VM","type":"User","uuid":"55d71859-ae54-4e12-8de3-8f84fe9627bf"}
2023-09-04 14:53:16,113 DEBUG [c.c.v.VirtualMachineManagerImpl]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) Allocating
nics for VM instance
{"id":15,"instanceName":"i-2-15-VM","type":"User","uuid":"55d71859-ae54-4e12-8de3-8f84fe9627bf"}
2023-09-04 14:53:16,118 DEBUG [o.a.c.e.o.NetworkOrchestrator]
(qtp649329985-505:ctx-d4b80649 ctx-698d5d78) (logid:550584ab) Allocating
nic for vm VM instance
{"id":15,"instanceName":"i-2-15-VM","type":"User","uuid":"55d71859-ae54-4e12-8de3-8f84fe9627bf"}
in network Network {"id": 213, "name": "defaultGuestNetwork", "uuid":
"1d3be879-f75b-4ba9-83e8-aa1bb32c858c", "networkofferingid": 7} with
requested profile NicProfile
{"broadcastUri":null,"iPv4Address":null,"id":0,"reservationId":null,"vmId":0}
