cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Parth Patel <parthpatel2...@gmail.com>
Subject Re: Cloud (Infrastructure reselling) = VPC ?
Date Mon, 05 Mar 2018 16:27:33 GMT
Thank you very much Andrija, I was scraping through cloudstack
administration docs to properly understand this. I'll certainly ask for
your guidance if I get stuck somewhere. Thank you again :)

On Mon 5 Mar, 2018, 19:03 Andrija Panic, <andrija.panic@gmail.com> wrote:

> Doman architecture setup:
>
> Domain: /PARTNER1/client1/
> Domain:  /PARTNER1/client2/...
>
> Domain:  /PARTNER2/client1/
> Domain:  /PARTNER2/client2/ ...
>
> partner=reseler, while you keep to be provider of IaaS for your reselers...
> This all above is if you leave the "selling" to you "partners"
>
> In each PARTNERX domain, you will make one DOMAIN ADMIN account for your
> partner/resseler to be able to administer it's user's VMs/resources
> Inside each /client1/ or /client2/ subdomains (subdomains inside partner's
> domains) you would create regular user accounts (with optionally multiple
> users for such account)
>
> If you have more specific question, I might be able to help (we have such
> setup in place)
>
> You could build central user (web) portal, where users can apply for
> registration, than when an Portal Admin approves, client's would be
> provisioned from Portal via API/root keys on CloudStack side, or similar.
> (you need some mechanism of applying for account on CloudStack - and later
> for user to be able to see some details, or to change their passwords - via
> User portal for example, etc)
>
> Then, white-labeling with custom CSS and logos, etc... :)
>
> Cheers
>
> On 4 March 2018 at 10:33, Parth Patel <parthpatel2597@gmail.com> wrote:
>
> > Thank you DAG and Ivan. I will go ahead with this.
> >
> > On Sun 4 Mar, 2018, 14:08 Ivan Kudryavtsev, <kudryavtsev_ia@bw-sw.com>
> > wrote:
> >
> > > I suppose sometimes It's wise to use Domains rather than accounts, but
> If
> > > you have single-rank customers (every customer fits the same rules)
> then
> > > accounts are just fine.
> > >
> > > 2018-03-04 15:35 GMT+07:00 Dag Sonstebo <Dag.Sonstebo@shapeblue.com>:
> > >
> > > > Hi Parth
> > > >
> > > > To maintain current and future client isolation you should look at
> > > setting
> > > > up an account (not just a user) for each client, then in each account
> > you
> > > > can configure a VPC or simple isolated network for the webservers.
> > > >
> > > > Hope this helps,
> > > > Dag Sonstebo
> > > >
> > > > Get Outlook for iOS<https://aka.ms/o0ukef>
> > > > ________________________________
> > > > From: Parth Patel <parthpatel2597@gmail.com>
> > > > Sent: Saturday, March 3, 2018 9:45:27 PM
> > > > To: users@cloudstack.apache.org
> > > > Subject: Cloud (Infrastructure reselling) = VPC ?
> > > >
> > > > Hi,
> > > >
> > > > I just recently got a bit experience in CloudStack. My company wants
> to
> > > > host web servers for clients who from their panel or administration
> > > > dashboard have only basic privileges with the servers/VMs that are
> > > running.
> > > > For this reselling type of requirement, I started to dig into
> Projects
> > > view
> > > > and user permission control but did not find much. From my
> > understanding
> > > > what I need to create is a VPC (Virtual Private Cloud) offering for
> > each
> > > > client. right ? can anybody guide me o
> <https://maps.google.com/?q=%0A%3E+%3E+%3E+client.+right+?+can+anybody+guide+me+o&entry=gmail&source=g>n
> this, I just want to know I am
> > > > heading in right direction.
> > > >
> > > > Regards,
> > > > Parth Patel
> > > >
> > > > Dag.Sonstebo@shapeblue.com
> > > > www.shapeblue.com
> > > > 53 Chandos Place, Covent Garden, London  WC2N 4HSUK
> > > > @shapeblue
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > With best regards, Ivan Kudryavtsev
> > > Bitworks Software, Ltd.
> > > Cell: +7-923-414-1515
> > > WWW: http://bitworks.software/ <http://bw-sw.com/>
> > >
> >
>
>
>
> --
>
> Andrija Panić
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message