Administrator Management: Create Separate users with Nilavu

[jaeko44]

We should create a subsequent account in OpenNebula like we do with WHMCS, specific to the user. So user management can be achieved in OpenNebula Admin Portal.

[indykish]

@rajthilakmca We discussed on a bug in Vertice last nite. Here is a tie for that. ?
@vijaykanthm28
Can we discuss the design today. ?

[indykish]

@jaeko44 Is it just usermanagement in ON - I mean suspending/activating/deleting ?

So an administrator will use ONonly. rest will be handled by launcher.

Since we have to customize/build/support and upgrade on ON releases - might be easier to shield ON with one admin user.

Thinking on adding this to nilavu (if its just usermanagement).

[jaeko44]

VM Management should be handled by ON since that's the purpose of ON in the first place (for example monitoring usage etc.), while Billing management should be handled by WHMCS/(future billing integration).

So specific VM's can be suspended in OpenNebula etc.

In WHMCS, we allow the provider to de-activate accounts (since WHMCS already supports all this), and then in Nilavu we just do API checks.

For example, with Suspended VM's - we do a check to see if the state is suspended, then if it is we remove control of the VM from Nilavu and display a 'Suspended page' when a user clicks the VM/Instance. Where as with creating VM's etc, we do a check in WHMCS to see if

• There is sufficient credit
• The WHMCS account is not deactivated
• Other rules

If they pass then we proceed to create VM.

Launcher should only handle launching & scaling infrastructure, it's purpose is not to manage the platform.

We can ofcourse also do User Management inside Nilavu, but this will take time for development - so I feel like if we add the functionality to manage users in OpenNebula first -> then we can proceed to develop our own User Management inside Nilavu in the future and proceed to add the functionality incrementally into the project without disturbance.

[indykish]

@jaeko44 Sure, will discuss on it, make sense on the roles of different systems..

Requirements are:

• Allow our customer admin to deactivate accounts.
• Customer admin shall suspend or active VMs in ON
• Nilavu shall display status of VM as it is in ON
• Nilavu shall allow launch if there are credits. I belive this is-in-progres - fix done by @vinomca-megam @rathishvbr

@rajthilakmca Lets discuss the way forward on design today.