[one-users] SaaS with opennebula cloud

Daniel Molina dmolina at opennebula.org
Wed Apr 11 03:47:42 PDT 2012


Hi Biro,

On 2 April 2012 16:37, biro lehel <lehel.biro at yahoo.com> wrote:

> I'll just put this on the list, it seems like Daniel is busy, but maybe
> someone else can help me with an answer.
>
>
> Thank you in anticipation,
> Lehel.
>
>
> Daniel, two more things..
>
> When creating a new occi template, can I use as IMAGE_ID an ID of an
> existing peristent image (of course one that is not currently USED)?
> At the moment I have some persistent images, from which I configured and
> set-up VM's with some specific software (I'm working on building a kind of
> "platform" above the "infrastructure"), and I intend these VM's to be used
> by end-users. In my original templates (that are using the persistent
> images), besides the image disk definition, I had some further disks
> defined (type FS and SWAP). Would these disks be available if I pass only
> the persistent image ID in my new_occi_template.erb? I mean, would I get
> "the very same VM back"?
>
>
You can add those disks in your ERB templates (i.e
new_occi_template.erb) using the same OpenNebula template syntax. OCCI will
merge the information provided in those templates and the parameters
provided by the user using the common.erb template.

You can use a persisten image but you can start only one instance per image.


>
> Also, I read that Self Service currently supports only ranged networks.
> Does this mean that there is no way to set for a specific VM a specific IP
> address?
>
>
You can only create ranged networks using Self Service, but you can use
fixed/ranged networks in your templates. Also you can create fixed networks
through sunstone and make them available to the self service users, hence
they can select them in the compute creation. However you cannot select a
specific IP. The OCCI API allows it but the self service does not expose
it.

You can open a feature request in our dev site [1], and we can consider it
for the next release.

Cheers

[1] http://dev.opennebula.org/


>
> Thank you in anticipation,
> Lehel.
>
> --- On *Fri, 3/30/12, Daniel Molina <dmolina at opennebula.org>* wrote:
>
>
> From: Daniel Molina <dmolina at opennebula.org>
> Subject: Re: [one-users] SaaS with opennebula cloud
> To: "biro lehel" <lehel.biro at yahoo.com>
> Cc: users at lists.opennebula.org
> Date: Friday, March 30, 2012, 1:23 PM
>
> On 30 March 2012 07:46, biro lehel <lehel.biro at yahoo.com> wrote:
> >
> > I would also be interested, too, on this question. Not precisely on the
> SaaS aspect, since I think I got the idea about that, but instead: is there
> any way for an end-user (NON-OpenNebula user) to "communicate" with / pass
> commands to OpenNebula (eventually by using a designated OpenNebula
> account, but at the same time not being aware of this)?
>
>
> OpenNebula Self-Service is a simplified GUI aimed to end-users,
> offering a simplified access to shared infrastructure for non-IT end
> users.
>
> The administrator will configure a set of instance_types that the
> end-user will be able to select without taking care of the VM
> configuration. The user can login to this portal and interact with his
> resources.
>
> The VirtualNetworks and Images can be exposed in three different ways:
> 1. The administrator creates the VNETs and Images through the one*
> tools and distributes these resources in different instance_types. The
> end-user will just have to select the desired instance_type
>
> $ onevnet create occi_vnet
> ID: 2
> $ oneimage create occi_image
> ID:3
> $ cat $ONE_LOCATION/etc/occi_templates/new_occi_template.erb
> CPU=1
> MEMORY=1024
> DISK=[IMAGE_ID=3]
> NIC=[NETWORK_ID=2]
> $ cat $ONE_LOCATION/etc/occi.conf
> [...]
> :instance_types:
>   [...]
>   :new_occi_template:
>     :template: new_occi_template.erb
>     :cpu: 1
>     :memory: 1024
>
>
> 2. The administrator creates the VNETs and Images through the one*
> tools and makes them available for the end-user. The end-user selects
> which instance_type he wants to use and what image and network
> throught the GUI interface.
>
> $ onevnet create occi_vnet
> ID: 2
> $ oneimage create occi_image
> ID:3
> $ cat $ONE_LOCATION/etc/occi_templates/new_occi_template.erb
> CPU=1
> MEMORY=1024
> $ cat $ONE_LOCATION/etc/occi.conf
> [...]
> :instance_types:
>   [...]
>   :new_occi_template:
>     :template: new_occi_template.erb
>     :cpu: 1
>     :memory: 1024
>
> 3. The end-user is allowed to create VNETs (you can also define a base
> template for this) and upload Images and can select them for a new
> instance through the GUI interface
>
> $ cat $ONE_LOCATION/etc/occi_templates/new_occi_template.erb
> CPU=1
> MEMORY=1024
> DISK=[IMAGE_ID=3]
> NIC=[NETWORK_ID=2]
> $ cat $ONE_LOCATION/etc/occi.conf
> [...]
> :instance_types:
>   [...]
>   :new_occi_template:
>     :template: new_occi_template.erb
>     :cpu: 1
>     :memory: 1024
>
> If you want to enable VNC you have to add the following line to the
> templates:
> GRAPHICS = [
>   TYPE    = "vnc",
>   LISTEN  = "0.0.0.0",
>   PORT    = "5"]
>
> Hope this helps
>
> Refs:
> * Self Service UI:
> http://www.opennebula.org/documentation:rel3.4:selfservice
> * Adding new VM types:
>
> http://www.opennebula.org/documentation:rel3.4:occicg#defining_compute_types
> * VNET base template:
>
> http://www.opennebula.org/documentation:rel3.4:occicg#configuring_occi_virtual_networks
> * Permissions: http://www.opennebula.org/documentation:rel3.4:manage_acl
> * Vm template: http://www.opennebula.org/documentation:rel3.4:template
>
> >
> >
> > Cheers,
> > Lehel.
> >
> > --- On Thu, 3/29/12, TARUN TANK <08bit044 at nirmauni.ac.in> wrote:
> >
> >
> > From: TARUN TANK <08bit044 at nirmauni.ac.in>
> > Subject: [one-users] SaaS with opennebula cloud
> > To: users at lists.opennebula.org
> > Date: Thursday, March 29, 2012, 12:46 PM
> >
> >
> > hi, we have developed the opennebula cloud with front end and 5 worker
> nodes , we can successfully create the VM and can deploy them on the worker
> nodes.Hence we are able to run the windows as well as linux on the dom U of
> the worker nodes(using XEN) . We are using centos 5.0 on the worker nodes
> as the host os.We can also manage using Sunstone GUI.
> >
> > now we want to provide the software/application to the end user via
> browser/web interface but we don't have proper guidance for that, can we
> enable the end user to use the software (i.e matlab) via browser and if yes
> then what configuration is left ? , please guide us on that .
> >
> >
> > -----Inline Attachment Follows-----
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >
> >
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >
>
> --
> Daniel Molina
> Project Engineer
> OpenNebula - The Open Source Solution for Data Center Virtualization
> www.OpenNebula.org | dmolina at opennebula.org | @OpenNebula
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>


-- 
Daniel Molina
Project Engineer
OpenNebula - The Open Source Solution for Data Center Virtualization
www.OpenNebula.org | dmolina at opennebula.org | @OpenNebula
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20120411/1c259f7a/attachment-0003.htm>


More information about the Users mailing list