[one-users] OpenNebula 3.0 and libxenlight (new Xen toolstack)
Hello, I've been trying to get the new Xen toolstack (libxl) to work with OpenNebula, but I have an unusual install (my Xen Hypervisor is installed in /usr/xen42) and my Dom0 machines are NetBSD powered. I've changed my paths in remotes/vmm/xen/xenrc, but it seems like scripts in remotes/im have hardcoded paths and ignore xenrc completely. Also I was wondering why /bin/bash is used in all scripts, most Linux distros come with bash by default, but this is not a rule, other OSes only come with /bin/sh, and bash is installed locally (in /usr/local/bin/bash or /usr/pkg/bin/bash), so I think all scripts should use /bin/sh instead of /bin/bash. I will continue trying to get this working, and post the results/changes if necessary. Anyone had any luck in running OpenNebula using the xl toolstack? Regards, Roger. ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] How to use LVM storage backend with OCCI
Hi, On 28 September 2011 12:48, Prakhar Srivastava wrote: > I wish if someone has any idea how to use LVM backend with OCCI. The OCCI > compute template file only takes the storage URL for the uploaded image. > What if I have done a pre-staging of OS images on the hosts and want to use > the LVM transfer manager with SOURCE=/dev/vg-name/lv-name Using the OCCI interface you cannot define source paths for images. If you want to use the LVM backend you have to create an Image using the OpenNebula cli (oneimage create image_template). The image_template has to define the SOURCE value (/dev/vg-name/lv-name) instead of the PATH. You will be able to list these images using the GET /storage command and add them to any POST /compute request. The tm_lvm will use the defined device specified in the SOURCE. Hope this helps. -- Daniel Molina Project Engineer OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | @dmamolina ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Sunstone issue
On 20 October 2011 17:48, Faarooq Lowe wrote: > > We are using x509 to authenticate across the board and our KCA credentials > work fine using command line and running one commands from the shell. > However, when we attempt to log into sunstone we receive the following error: > > Wed Oct 19 13:11:20 2011 [AuM][I]: Command execution fail: > /var/lib/one/remotes/auth/server/authentica > te lowe > Wed Oct 19 13:11:20 2011 [AuM][D]: Message received: LOG E 617 login token > expired > When the login token is generated you have to define a expiration time for the token. It looks like your token is not valid and you should generate a new one. > > Now using our x509 DOE certificate we are allowed to get in. Now the only > difference I see is our KCA has a colon in it as opposed to our DOE which > does not. I recall hearing there were issues with colons and parsing, is > that still an issue in the general release? If not, is there a fix that > should be applied to our installation? In OpenNebula 3.0, passwords containing colons are not supported so that certificates whose DNs contain colons cannot be authenticated. We are solving this limitation for OpenNebula 3.2. I will let you know when the code is ready in the repo. You can follow up its development in the following ticket: http://dev.opennebula.org/issues/847 Cheers. -- Daniel Molina Project Engineer OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | @dmamolina ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Add storage backend management
PS (pre-scriptum :) : please view this mail with fixed sized font and without the 80 column maximum limit. Hi all, My name is Paul (paulg) Grandperrin and I'm working as a engineer intern at a french company called Alterway Hosting specialized in open source services. My mission is to implement in Opennebula a way to manage a pool of storage backends (like iSCSI targets). A storage backend (SB) will be similar to a host except its role is to manage images instead of VMs. The objective is to manage a pool of heterogeneous storage backends to store the images and the VM's block devices. A typical use case could be: 20 hypervisors 5 high performance iSCSI targets with SSD 10 low performance iSCSI targets 1 ceph cluster We want Opennebula to automaticaly allocate and attach the VMs storage on the different storage backends. SB attributes are: ID(int), NAME(string), STATE(enum), TM(string), CAPACITY(int), FREE(int), TM_RAW(string), COST(int), ROLE(enum) TM is the name of the Transfer Manager to use to communicate with the SB. MAX_STORAGE, FREE_STORAGE and USED_STORAGE give information about the used space on the SB. TM_RAW is an optionnal argument to directly pass to the TM. COST is an integer choosen by the administrator to prioritize some SB over others. ROLE would represent the usage, it could be SAN or REPOSITORY. We might also add these attribute: TAGS ( a list of string to do some filtering), NBIMAGE(int), NBVM(int), USER, GROUP... We would create a new Transfer Manager (TM2), supporting multiple drivers at opnce. The TM2 (and it's drivers) will provide the following actions: COMMAND ARG1 ARG2 OTHER get[HOSTNAME]:[IMAGENAME] /path stores an image on a path push /path[HOSTNAME]:[IMAGENAME] stores an image clone [HOSTNAME]:[IMAGENAMESRC][IMAGENAMEDST] clones an image on the same storage backend. delete [HOSTNAME]:[IMAGENAME] simply delete an image get-size [HOSTNAME]:[IMAGENAME] returns the size of the image allocate [HOSTNAME]:[IMAGENAME] size creates a data block on the HOSTNAME storage resize [HOSTNAME]:[IMAGENAME] size resize the image read [HOSTNAME]:[IMAGENAME] reads an image, outputs to stdout write [HOSTNAME]:[IMAGENAME] write the content of stdin to an image attach [HOSTNAME]:[IMAGENAME] /path attach the image IMAGENAME stored on HOSTNAME to the path "/path" dettach[HOSTNAME]:[IMAGENAME] /path disconnect the image/remove the symlink, etc Some other things to do : Add a command called onestoragebackend with the following actions: create, delete, list, top, show (enable, disable, update) Add a new table in the BDD named storagebackend_pool. In the source code add the needed classes: StorageBackend,StorageBackendPool, RequestManagerStorageBackend... For backward compatibility, it should be possible to write a TM2 driver (named LEGACYTM) which will use the old TM drivers to complete the requested actions. In the futur (depending if we have enough time), we might add: Cluster awareness Permission management Tags filtering: We want to be able to tell Opennebula that one VM needs some special storage properties (ex: HDD7K HDD15K, SSD, DISTRIBUTED, whatever). Then the scheduler will filter the storagebackends providing all theses properties and choose on of them. Please feel free to comment and make suggestions. Regards, Paul Grandperrin, AlterWay Hosting ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] OpenNebula 3.0 and libxenlight (new Xen toolstack)
Hi Roger, It is true that /bin/bash is not installed in every *nix, although it can be installed and also a symlink can be created. Taking into account that bash syntax is not completely the same as "sh" syntax, so I think is not that unreasonable to have "bash" as a requirement for OpenNebula. Regarding the remotes/im script, they won't use "xenrc" (only applies to remotes/vmm/xen scripts), but you can change remotes/im/xen.d/xen.rb, lines 21-22. XCP also offers the XCP toolstack, just saying because we are collaborating with Xen.org [1][2], although the integration is based on XAPI rather than libxl. Regards, -Tino [1] http://blog.opennebula.org/?p=2118 [2] http://blog.xen.org/index.php/2011/10/24/building-opennebula-clouds-on-xcp/ -- Constantino Vázquez Blanco, MSc OpenNebula Project Engineer www.OpenNebula.org | @tinova79 On Mon, Oct 24, 2011 at 11:21 AM, Roger Pau Monné wrote: > Hello, > > I've been trying to get the new Xen toolstack (libxl) to work with > OpenNebula, but I have an unusual install (my Xen Hypervisor is > installed in /usr/xen42) and my Dom0 machines are NetBSD powered. I've > changed my paths in remotes/vmm/xen/xenrc, but it seems like scripts > in remotes/im have hardcoded paths and ignore xenrc completely. Also I > was wondering why /bin/bash is used in all scripts, most Linux distros > come with bash by default, but this is not a rule, other OSes only > come with /bin/sh, and bash is installed locally (in > /usr/local/bin/bash or /usr/pkg/bin/bash), so I think all scripts > should use /bin/sh instead of /bin/bash. I will continue trying to get > this working, and post the results/changes if necessary. > > Anyone had any luck in running OpenNebula using the xl toolstack? > > Regards, Roger. > ___ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] Migrate Kvms to open nebula
Hi All, I have around 40 KVMs set up separately . I want to move this to Open Nebula . What is the best way to do this ? Can I run something such that it finds the images already in /var/lib/one and adds it to the software ? thanks Madhurranjan ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] RANK expression
Are there any pre-defined values for disk space that may be used for the RANK expression in a template? Also is there away to evaluate expressions in a specific order such as; FREEMEMORY, DISKSPACE, - RUNNING_VMS etc.? ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
Re: [one-users] Bare-metal
Hi Alex, actually what we're asking is how do you think this feature should be implemented. What features should OpenNebula offer to integrate with bare-metal? Besides technical detals, such as specific distributions, could you describe what you'd like to see OpenNebula doing with bare-metal? Thanks again, Jaime On Fri, Oct 14, 2011 at 9:36 PM, Alexandre Emeriau wrote: > Hi Jaime, > > Do you mean dependency upon the choosed os ? or a particular project among > anothers of mine ? > Just trying to follow and bring the answer you're waiting for. > > Regards, > Alex > > Le 14/10/2011 09:40, Jaime Melis a écrit : > > Hello, > > that's something we're certainly considering. Could you please ellaborate > a bit more on your use case? > > This also applies to anyone interested in this feature, how would you use > it? > > cheers, > Jaime > > On Wed, Oct 12, 2011 at 9:41 PM, Alexandre Emeriau < > alexandre.emer...@ainsidonc.com> wrote: > >> Hi, >> >> Is a bare-metal OpenNebula is planned ? Something like Proxmox or >> Opennode. >> >> Regards >> >> ___ >> Users mailing list >> Users@lists.opennebula.org >> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org >> >> > > > -- > Jaime Melis > Project Engineer > OpenNebula - The Open Source Toolkit for Cloud Computing > www.OpenNebula.org | jme...@opennebula.org > > -- Jaime Melis Project Engineer OpenNebula - The Open Source Toolkit for Cloud Computing www.OpenNebula.org | jme...@opennebula.org ___ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[one-users] EC2 API authentication error :- User not authorized
Hi All
I am using EC2 API for user authentication but it gives me an error: USER NOT
AUTHORIZED. I am working on this error for last 5 days but donno able to
understand what is the exact cause.
[oneadmin@frontend etc]$ econe-describe-instances -K oneadmin -S -U
http://localhost:4567
econe-describe-instances: User not authorized
The following are the configuration of econe.conf
---
:one_xmlrpc: http://localhost:2633/RPC2
# Host and port where econe server will run
:server: localhost
:port: 4567
:auth: ec2
:instance_types:
:m1.small:
:template: m1.small.erb
--
When i change the localhost to hostname or IP Address, error still remains same.
econe.log
-
:port=>4567,
:template_location=>"/var/lib/one/etc/ec2query_templates",
:instance_types=>{:"m1.small"=>{:template=>"m1.small.erb"}},
:views=>"/var/lib/one/lib/ruby/cloud/econe/views",
:one_xmlrpc=>"http://localhost:2633/RPC2"}
== Sinatra/1.3.1 has taken the stage on 4567 for development with backup from Th
in
- - [20/Oct/2011 19:22:03] "POST / HTTP/1.1" 500 139 0.0106
- - [20/Oct/2011 19:22:05] "POST / HTTP/1.1" 500 139 0.0074
- - [20/Oct/2011 19:22:06] "POST / HTTP/1.1" 500 139 0.0078
- - [20/Oct/2011 19:22:07] "POST / HTTP/1.1" 500 139 0.0076
- - [20/Oct/2011 19:25:39] "POST / HTTP/1.1" 500 139 0.0088
- - [20/Oct/2011 19:25:41] "POST / HTTP/1.1" 500 139 0.0070
- - [20/Oct/2011 19:25:42] "POST / HTTP/1.1" 500 139 0.0076
- - [20/Oct/2011 19:25:42] "POST / HTTP/1.1" 500 139 0.0072
- - [20/Oct/2011 19:25:43] "POST / HTTP/1.1" 500 139 0.0083
- - [20/Oct/2011 19:25:59] "POST / HTTP/1.1" 500 139 0.0080
- - [20/Oct/2011 19:26:00] "POST / HTTP/1.1" 500 139 0.0087
- - [20/Oct/2011 19:26:01] "POST / HTTP/1.1" 500 139 0.0073
127.0.0.1 - - [20/Oct/2011 19:42:45] "POST / HTTP/1.1" 400 139 0.0107
- - [20/Oct/2011 19:43:06] "POST / HTTP/1.1" 400 139 0.0076
- - [25/Oct/2011 12:04:44] "POST / HTTP/1.1" 400 139 0.0113
127.0.0.1 - - [25/Oct/2011 12:05:01] "POST / HTTP/1.1" 400 139 0.0098
--
m1.small.erb
---
NAME = eco-vm
#Adjust Capacity for this instance type
CPU= 0.2
MEMORY = 256
# Put here specific OS configurations for the cloud hypervisors
#OS = [ kernel = /vmlinuz,
# initrd = /initrd.img,
# root = sda1,
# kernel_cmd = "ro xencons=tty console=tty1"]
DISK = [ IMAGE_ID = <%= erb_vm_info[:img_id] %> ]
# Put here the ID of the VNET with the IPs for the EC2 VMs
NIC=[NETWORK_ID= 4]
IMAGE_ID = <%= erb_vm_info[:ec2_img_id] %>
INSTANCE_TYPE = <%= erb_vm_info[:instance_type ]%>
<% if erb_vm_info[:user_data] %>
#CONTEXT = [
# EC2_USER_DATA="<%= erb_vm_info[:user_data] %>",
# TARGET="hdc"
# ]
<% end %>
--
Thanks in Advance
(Bharat Bagai)
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
