[one-users] set user quotas be valid for a given period of time

[knawnd]

Dear all,

as far as I understand from [1] in the current stable OpenNebula release (v.4.4) it's not possible 
to set user quotas be valid for a given period of time.
We would like to implement the following scenario. Split all cloud users into two categories: 1) 
permanent and 2) temporal. Users from the second category can use cloud resources only during 
certain period of time. And e.g. one week/month before quotas are expired the user will get 
notification via email. He can ignore it if he is not going to use cloud resources any longer or ask 
for prolongation.


Best regards,
Nikolay.

[1] 
http://docs.opennebula.org/4.4/administration/users_and_groups/quota_auth.html
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Images from Images (Ceph) Datastore Not Deploying

[Steve @ MyEvolve]

Any suggestions on this?


On Tue, Apr 8, 2014 at 7:37 PM, Steve @ MyEvolve  wrote:

> Hi Ruben,
>
> So I've been trying to experiment a bit.  I started over. Re-imported
> ttylinux into ceph datastore.  Created new template and new vm and I logged
> in as oneadmin and defined the secret as instructed on all hosts.
>
> In creating the new VM, the process failed as before.
>
> I tried as you suggested:
>
> [oneadmin@cloud2 54]$ virsh create -c qemu:///system deployment.0
>
> error: unexpected data 'qemu:///system'
>
> But as you can see I got an error message I'm not sure what to do with.
>
>
> Also, I have a new log that looks different -- seems adding the port to
> the CEPH_HOST was the distinguishing factor.
>
>
> Tue Apr 8 19:30:04 2014 [DiM][I]: New VM state is ACTIVE.
> Tue Apr 8 19:30:04 2014 [LCM][I]: New VM state is PROLOG.
> Tue Apr 8 19:30:09 2014 [LCM][I]: New VM state is BOOT
> Tue Apr 8 19:30:10 2014 [VMM][I]: Generating deployment file:
> /var/lib/one/vms/54/deployment.0
> Tue Apr 8 19:30:10 2014 [VMM][I]: ExitCode: 0
> Tue Apr 8 19:30:10 2014 [VMM][I]: Successfully execute network driver
> operation: pre.
> Tue Apr 8 19:30:10 2014 [VMM][I]: Command execution fail: cat << EOT |
> /var/tmp/one/vmm/kvm/deploy '/var/lib/one//datastores/125/54/deployment.0'
> 'cloud2' 54 cloud2
> Tue Apr 8 19:30:10 2014 [VMM][I]: error: Failed to create domain from
> /var/lib/one//datastores/125/54/deployment.0
> Tue Apr 8 19:30:10 2014 [VMM][I]: error: internal error process exited
> while connecting to monitor: qemu-kvm: -drive
> file=rbd:one/one-28-54-0:auth_supported=none:mon_host=cloudweb12\:6789,if=none,id=drive-ide0-0-0,format=raw,cache=none:
> error connecting
> Tue Apr 8 19:30:10 2014 [VMM][I]: qemu-kvm: -drive
> file=rbd:one/one-28-54-0:auth_supported=none:mon_host=cloudweb12\:6789,if=none,id=drive-ide0-0-0,format=raw,cache=none:
> could not open disk image
> rbd:one/one-28-54-0:auth_supported=none:mon_host=cloudweb12\:6789:
> Operation not supported
> Tue Apr 8 19:30:10 2014 [VMM][I]:
> Tue Apr 8 19:30:10 2014 [VMM][E]: Could not create domain from
> /var/lib/one//datastores/125/54/deployment.0
> Tue Apr 8 19:30:10 2014 [VMM][I]: ExitCode: 255
> Tue Apr 8 19:30:10 2014 [VMM][I]: Failed to execute virtualization driver
> operation: deploy.
> Tue Apr 8 19:30:10 2014 [VMM][E]: Error deploying virtual machine: Could
> not create domain from /var/lib/one//datastores/125/54/deployment.0
> Tue Apr 8 19:30:10 2014 [DiM][I]: New VM state is FAILED
>
>
> And also here is deployment.0:
>
> 
>
> one-54
>
> 
>
> 1024
>
> 
>
> 524288
>
> 
>
> hvm
>
> 
>
> 
>
> 
>
> /usr/libexec/qemu-kvm
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
>  file='/var/lib/one//datastores/125/54/disk.1'/>
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
> 
>
>
> Thank you!
>
> Steve
>
>
>
>
> On Tue, Apr 8, 2014 at 10:13 AM, Ruben S. Montero <
> rsmont...@opennebula.org> wrote:
>
>> Hi
>>
>> I've tested with the very same environment and it should work. Could you
>> try to define the secret with the oneadmin account and:
>>
>> -c qemu:///system
>>
>> option for virsh command.
>>
>> Also to manually test it, once the vm is in failed state go to the vm
>> directory in the host and simply execute:
>>
>> virsh create -c qemu:///system deployment.0
>>
>> Cheers
>>
>> Ruben
>> On Apr 8, 2014 7:05 PM, "Steve @ MyEvolve"  wrote:
>>
>>> Hi Bill,
>>>
>>> I am using Centos 6.5 and CephX.  I installed the following rpm versions
>>> from Ceph on the nodes and I also followed the procedure for authentication
>>> :
>>>
>>> rpm -Uvh
>>> http://ceph.com/packages/ceph-extras/rpm/centos6.4/x86_64/qemu-kvm-0.12.1.2-2.415.el6.3ceph.x86_64.rpm
>>> http://ceph.com/packages/ceph-extras/rpm/centos6.4/x86_64/qemu-img-0.12.1.2-2.415.el6.3ceph.x86_64.rpm
>>> http://ceph.com/packages/ceph-extras/rpm/centos6.4/x86_64/qemu-guest-agent-0.12.1.2-2.415.el6.3ceph.x86_64.rpm
>>> http://ceph.com/packages/ceph-extras/rpm/centos6.4/x86_64/qemu-kvm-tools-0.12.1.2-2.415.el6.3ceph.x86_64.rpm
>>>
>>>
>>> CephX
>>>
>>> virsh secret-define --file secret.xml; virsh secret-set-value --secret
>>> 34afabcd-8ee0-45fd-a880-09df24fef603 --base64 $(cat client.libvirt.key)
>>>
>>>
>>> Also, Ruben -- how do I:
>>>
>>> "1.- could you try manually to add port to the >> check if the VM boots with virsh create"
>>>
>>>
>>> Thank you,
>>>
>>> Steve
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Apr 8, 2014 at 6:20 AM, Campbell, Bill <
>>> bcampb...@axcess-financial.

Re: [one-users] Assigning limited admin rights

[Wilma Hermann]

Hi,

To answer my own mail, I could resolve both problems. For the sake of
completeness, here's how:

   1. I'm using a hook to change a new user's group after creation using
   the approach from this thread:
   
http://lists.opennebula.org/pipermail/users-opennebula.org/2013-September/024648.html
   2. The problem here was that I used the vdcadmin view in Sunstone for
   the user. By debugging I found out that the list of groups in Sunstone is
   populated by some javascript loaded by the groups panel. In the vdcadmin
   view, the groups panel is disabled by default, therefore the list of groups
   is empty. It's arguably either a bug or a strict permission management
   thing, I can't justice on that. However, if I enable the groups panel and
   prevent the user from doing changes to the groups, I have everything I
   wanted to build.

Greetings
Wilma


2014-04-07 13:35 GMT+02:00 Wilma Hermann :

> Hi,
>
> Thanks for the info, it was very useful. I'm still having two issues:
>
>
>1. The default group of a new user is the same as the creating user's
>one. I would like to have new users in the "users" group by default. Is
>there a way to change this behavior?
>2. In Sunstone, the user doing the user management does not see the
>existing groups even though he ought to. I created an ACL "#
>GROUP/* USE+MANAGE+ADMIN", but still the list of groups I can assign to a
>user through Sunstone is empty (Even the string "Please select" does not
>appear). On the command line, a "oneuser chgrp" works flawlessly using this
>account, so I guess it's a bug in Sunstone.
>
> Greetings
> Wilma
> 2014-04-04 10:34 GMT+02:00 Carlos Martín Sánchez :
>
> > Hi,
> >
> > Adding to what Rubén said, the acl modification is only allowed for
> users in
> > the oneadmin group.
> >
> > Make sure you use the reference command-auth tables in the xml-rpc doc
> [1]
> > to create your rules.
> >
> > For example, oneuser passwd requires USER:MANAGE. The rule "#
> > USER/* USE+MANAGE+ADMIN" will allow your user to change oneadmin's
> password.
> > In this case, you will want to create a rule targeting each group
> (excluding
> > oneadmin).
> >
> > Regards
> >
> > [1]
> >
> http://docs.opennebula.org/4.4/integration/system_interfaces/api.html#authorization-requests-reference
> > --
> > Carlos Martín, MSc
> > Project Engineer
> > OpenNebula - Flexible Enterprise Cloud Made Simple
> > www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula
> >
> >
> > On Thu, Apr 3, 2014 at 2:19 PM, Ruben S. Montero <
> rsmont...@opennebula.org>
> > wrote:
> >>
> >> Hi
> >>
> >> Probably, the following may work...
> >>
> >> oneacl create "# USER/* CREATE"
> >> oneacl create "# USER/* USE+MANAGE+ADMIN"
> >>
> >> Take a look to the ACL guide for more info:
> >>
> >>
> >>
> http://docs.opennebula.org/4.4/administration/users_and_groups/manage_acl.html
> >>
> >> Cheers
> >>
> >> Ruben
> >>
> >>
> >>
> >> On Thu, Apr 3, 2014 at 12:08 PM, Wilma Hermann  >
> >> wrote:
> >>>
> >>> Hi,
> >>>
> >>> Is it possible to assign limited admin rights to certain accounts? I
> >>> would like to have a user that is allowed to do all the user
> >>> management (creating users, adding users to existing groups, etc.)
> >>> without adding this user to the oneadmin-group. In particular, I would
> >>> like to deny this user access to all other users' VMs, templates,
> >>> images, etc. The user also shouldn't have write-access to the ACLs
> >>> (otherwise limits would make no sense obviously).
> >>>
> >>> Greetings
> >>> Wilma
> >>> ___
> >>> Users mailing list
> >>> Users@lists.opennebula.org
> >>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >>
> >>
> >>
> >>
> >> --
> >> --
> >> Ruben S. Montero, PhD
> >> Project co-Lead and Chief Architect
> >> OpenNebula - Flexible Enterprise Cloud Made Simple
> >> www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula
> >>
> >> ___
> >> 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

Re: [one-users] (anti-) affinity groups support for scheduler

[Paul Batchelor]

We would definitely see a use for this as well. We have had multiple instances 
of a supposedly redundant service start on the same hypervisor. An 
"anti-affinity" attribute in the template sounds like the perfect fix.

-Original Message-
From: users-boun...@lists.opennebula.org 
[mailto:users-boun...@lists.opennebula.org] On Behalf Of Stefan Kooman
Sent: 09 April 2014 14:41
To: users@lists.opennebula.org
Subject: [one-users] (anti-) affinity groups support for scheduler

Hi List,

I'm trying to accomplish the following. I want to have the "match making 
scheduler" schedule two or more vm's on the same hypervisor (webserver and 
database server, to reduce network traffic between HOSTS. I know there is a way 
of doing this with "CURRENT_VMS". CURRENT_VMS only seems to accept "VM ID's" 
and not the name of a VM. The drawback of having an ID hardcoded in a template 
is that if the VM gets recreated from a template somewhere in the future 
(because of some changes in the template) the REQUIREMENT will never be 
fullfilled and the vm never deployed.
One way to get around this would be to create so called "(anti-)affinity 
groups. So in a VM TEMPLATE you would define "AFFINITY_GROUP=$AFFINITY_GROUP"
and the scheduler would check if a VM with that particular AFFINITY_GROUP is 
running on a hypervisor. If so, it would place this VM on the same hypervisor. 
If not it deploys the VM on a hypervisor that has highest priority after 
filtering. You might wonder why I would not just select a HOST for these 
particular VM's. With HOST=$HOST I would not be able to bring those VM's up on 
a different hypervisor in case of a disaster without modifying a template or 
manually forcing a deploy. Not something you've got time for while battling a 
(major) outage.

You can think of an AFFINITY_GROUP as a selective "black hole": Sucking up VM's 
it has affinity with.

What do you think of this? Does it makes sense to you? Would you have use for 
this funtionality?

Gr. Stefan


-- 
| BIT BV  http://www.bit.nl/Kamer van Koophandel 09090351
| GPG: 0xD14839C6   +31 318 648 688 / i...@bit.nl
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
-
BlackBerry UK Limited
Registered in England and Wales. Registered No. 04022422, with registered 
office at 200 Bath Road, Slough, Berkshire, SL1 3XE, United Kingdom

This transmission (including any attachments) may contain confidential 
information, privileged material (including material protected by the 
solicitor-client or other applicable privileges), or constitute non-public 
information. Any use of this information by anyone other than the intended 
recipient is prohibited. If you have received this transmission in error, 
please immediately reply to the sender and delete this information from your 
system. Use, dissemination, distribution, or reproduction of this transmission 
by unintended recipients is not authorized and may be unlawful.

___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] One 4.6 and ozones

[Ondrej Hamada]

Thank you for the information.

How is it going to affect the upgrade procedure? I would like to enlarge my 
current vm lab and I would like to divide it into more VDCs and at least two 
zones. Question is: do it now or wait for the One 4.6 to avoid potential 
upgrade issues?

Ondra

On 03/24/2014 06:14 PM, Ruben S. Montero wrote:
Hi Ondrej,

Ozones has been redesign and integrated in OpenNebula core, you can have more 
information about the VDC part here [1]. We need to find some time to make a 
screencast of the federation part, meanwhile take a look to the new 
documentation [2,3] Note that we are working on the docs

Cheers

[1] http://opennebula.org/partitioning-clouds-with-virtual-data-centers-vdcs/
[2] 
http://docs.opennebula.org/4.6/advanced_administration/data_center_federation/federationconfig.html
[3] 
http://docs.opennebula.org/4.6/advanced_administration/data_center_federation/federationmng.html


On Mon, Mar 24, 2014 at 4:51 PM, Ondrej Hamada 
mailto:ondrej.ham...@acision.com>> wrote:
Hi,
I was briefly looking at roadmap for one 4.6 and discovered the feature
#2691: Remove ozones code.
What kind of change is that? Just some refactoring or are you remove
ozones completely? If yes, what will replace them?

Thank you in advance

Ondra

This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you for understanding.


___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org



--
--
Ruben S. Montero, PhD
Project co-Lead and Chief Architect
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | 
rsmont...@opennebula.org | @OpenNebula




This e-mail and any attachment is for authorised use by the intended 
recipient(s) only. It may contain proprietary material, confidential 
information and/or be subject to legal privilege. It should not be copied, 
disclosed to, retained or used by, any other party. If you are not an intended 
recipient then please promptly delete this e-mail and any attachment and all 
copies and inform the sender. Thank you for understanding.

___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Unable to deploy VMs - OpenVswitch issues

[Rodolfo Conte Brufatto]

Got it solved by using raring (3.8) datapath modules package provided in
12.04.3 and also enabling brcompat support once again.
Had to remove actual openvswitch module and restart openvswitch services.
It is all working now.

Thanks!


On Wed, Apr 9, 2014 at 7:51 AM, Rodolfo Conte Brufatto  wrote:

> Of course, there you go:
>
> I am using Precise here too (12.04)
>
> * OpenVswitch:
>
> ii  openvswitch-common   1.4.6-0ubuntu1.12.04.2   Open
> vSwitch common components
> ii  openvswitch-controller   1.4.6-0ubuntu1.12.04.2   Open
> vSwitch controller implementation
> ii  openvswitch-datapath-dkms1.4.6-0ubuntu1.12.04.2   Open
> vSwitch datapath module source - DKMS version
> ii  openvswitch-pki  1.4.6-0ubuntu1.12.04.2   Open
> vSwitch public key infrastructure dependency package
> ii  openvswitch-switch   1.4.6-0ubuntu1.12.04.2   Open
> vSwitch switch implementations
>
> * libvirt
>
> ii  libvirt-bin  0.9.8-2ubuntu17.17   programs
> for the libvirt library
> ii  libvirt0 0.9.8-2ubuntu17.17   library
> for interfacing with different virtualization systems
>
> The module bridge is blacklisted already.
>
> Cheers!
>
>
> On Wed, Apr 9, 2014 at 4:54 AM, Leszek Master  wrote:
>
>> What OS do you use ? I've had similiar problem with ubuntu 12.04 LTS with
>> old version of libvirtd and openvswitch, where i had to remove bridge
>> module and add brcompat module. Show us your OS version, libvirtd and
>> openvswitch.
>>
>>
>> 2014-04-08 23:44 GMT+02:00 Rodolfo Conte Brufatto :
>>
>>> Hello everyone,
>>> I am facing some issues when trying to deploy some new VM instances on a
>>> new host (I am using OpenNebula 3.8.3 here).
>>> In the logs I get:
>>>
>>> Tue Apr  8 18:28:32 2014 [VMM][I]: error: Unable to add bridge XXX port 
>>> vnet0: Operation not supported
>>>
>>> I've properly configured the bridges and attached the interfaces using
>>> ovs-vsctl and the users are already added in sudoers.
>>>
>>> Is there someone out there facing similar issues that can help me out?
>>>
>>>  Thanks in advance,
>>>
>>> Regards.
>>>
>>> --
>>> Have you tried turning it off and on again?
>>>
>>> ___
>>> Users mailing list
>>> Users@lists.opennebula.org
>>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>>
>>>
>>
>
>
> --
> Have you tried turning it off and on again?
>



-- 
Have you tried turning it off and on again?
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] data store not created in VMHosts

[Jaime Melis]

Well, the patch was simply to add a mkdir -p $DATASTORE_LOCATION to the
monitor_ds.sh script at the top. Can you try it and let us know if that
works for you?



On Fri, Apr 4, 2014 at 3:50 PM, Hyun Woo Kim  wrote:

>  Hi Jaime and Carlos,
>
>  Thanks very much for the explanations.
> Until you release a new version that deals with this bug,
> we can manually mkdir /var/lib/one/datastores in each of our VMHosts to
> avoid this issue.
>
>  Thanks again!
> HyunWoo KIM
> FermiCloud
>
>
>   From: Jaime Melis 
> Date: Friday, April 4, 2014 6:53 AM
> To: Hyunwoo Kim 
> Cc: users , Carlos Martín Sánchez <
> cmar...@opennebula.org>
>
> Subject: Re: [one-users] data store not created in VMHosts
>
>   Hi Hyun,
>
>  I've looked at this issue and you're completely right. If
> /var/lib/one/datastores does not exist in the VMHost it will report that it
> doesn't have free space and therefore it will never deploy the VM, which
> means that the directory will never be created, which is a Catch 22.
>
>  We haven't noticed this earlier because usually people share
> /var/lib/one/datastores and therefore you don't hit this issue. And people
> using SSH and upgrading from earlier version will not hit it because in
> previous pervious the disk capacity wasn't checked so it always created the
> directory.
>
>  Long story short, bug confirmed, applying patch to monitor_ds.sh
>
>  Thanks for the heads up.
>
>  Cheers,
> Jaime
>
>
> On Mon, Mar 31, 2014 at 11:25 AM, Carlos Martín Sánchez <
> cmar...@opennebula.org> wrote:
>
>>  Hi,
>>
>>  On Fri, Mar 28, 2014 at 7:40 PM, Hyun Woo Kim  wrote:
>>
>>>  If HostXML::test_ds_capacity only creates  $DATASTORE_LOCATION/
>>> assuming  $DATASTORE_LOCATION itself exists,
>>> my next question here might be,
>>> which code creates  $DATASTORE_LOCATION itself and when?
>>>
>>>  I don't think I missed an instruction to create  $DATASTORE_LOCATION
>>> manually in the ON documentation..
>>> i.e.  $DATASTORE_LOCATION must be created by ON codes (maybe) during the
>>> first VM deployment.
>>>
>>>  But like I described in the original email, our test ON4.4  fails at
>>> this.
>>>
>>>  Hyunwoo Kim
>>> FermiCloud
>>>
>>
>>  The $DATASTORE_LOCATION/ dir is created by the tm drivers on the
>> first deployment, using the ssh_make_path function (mkdir -p). As I said, I
>> think the problem is not the dir creation, is with the mechanism to decide
>> the first deployment on a new host.
>>
>>  Regards
>>
>> --
>> Carlos Martín, MSc
>> Project Engineer
>> OpenNebula - Flexible Enterprise Cloud Made Simple
>> www.OpenNebula.org  | cmar...@opennebula.org
>>  | @OpenNebula 
>>
>> ___
>> Users mailing list
>> Users@lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>
>
>  --
>  Jaime Melis
> Project Engineer
> OpenNebula - Flexible Enterprise Cloud Made Simple
> www.OpenNebula.org | jme...@opennebula.org
>



-- 
Jaime Melis
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | jme...@opennebula.org
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

[one-users] (anti-) affinity groups support for scheduler

[Stefan Kooman]

Hi List,

I'm trying to accomplish the following. I want to have the "match making
scheduler" schedule two or more vm's on the same hypervisor (webserver and
database server, to reduce network traffic between HOSTS. I know
there is a way of doing this with "CURRENT_VMS". CURRENT_VMS only seems
to accept "VM ID's" and not the name of a VM. The drawback of having an
ID hardcoded in a template is that if the VM gets recreated from a
template somewhere in the future (because of some changes in the template)
the REQUIREMENT will never be fullfilled and the vm never deployed.
One way to get around this would be to create so called "(anti-)affinity
groups. So in a VM TEMPLATE you would define "AFFINITY_GROUP=$AFFINITY_GROUP"
and the scheduler would check if a VM with that particular
AFFINITY_GROUP is running on a hypervisor. If so, it would place this VM
on the same hypervisor. If not it deploys the VM on a hypervisor that
has highest priority after filtering. You might wonder why I would not
just select a HOST for these particular VM's. With HOST=$HOST I would not be 
able to
bring those VM's up on a different hypervisor in case of a disaster
without modifying a template or manually forcing a deploy. Not something
you've got time for while battling a (major) outage.

You can think of an AFFINITY_GROUP as a selective "black hole": Sucking up VM's 
it
has affinity with.

What do you think of this? Does it makes sense to you? Would you have use
for this funtionality?

Gr. Stefan


-- 
| BIT BV  http://www.bit.nl/Kamer van Koophandel 09090351
| GPG: 0xD14839C6   +31 318 648 688 / i...@bit.nl
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Problem boot VM template with opennebula

[Javier Fontan]

I think it is better to let OpenNebula choose the port as you can use
the same template to start several VMs and the VNC ports wont clash.

On Wed, Apr 2, 2014 at 9:57 AM, Cuquerella Sanchez, Javier
 wrote:
> Hi,
>
> actually I specify the port manually. and there is no other service using 
> port 5902. I should do in my template to enable VNC OpenNebula autonomously?
>
> Regards.
> Javier.
>
> ---
> Javier Cuquerella Sánchez
>
> javier.cuquere...@atos.net
> Atos Research & Innovation
> Systems Administrator
> Albarracin 25
> 28037-Madrid (SPAIN)
> Tfno: +34.91.214.8080
> www.atosresearch.eu
> es.atos.net
>
>
> -Original Message-
> From: Javier Fontan [mailto:jfon...@opennebula.org]
> Sent: Tuesday, April 01, 2014 3:38 PM
> To: Cuquerella Sanchez, Javier
> Cc: users@lists.opennebula.org
> Subject: Re: Problem boot VM template with opennebula
>
> Are you specifying the port manually. It may be that there's another VM 
> already using that port. Do not set it, let OpenNebula chose one for you.
>
> If this does not work try also unsetting the keymap. I can not think of any 
> other problem with that.
>
> On Tue, Apr 1, 2014 at 11:43 AM, Cuquerella Sanchez, Javier 
>  wrote:
>> Hi,
>>
>> I have instantiated the machine, removing and setting parameters and end the 
>> problem is on the line of the VNC:
>>
>> GRAPHICS=[ KEYMAP=es, LISTEN=0.0.0.0, PORT=5902,
>> TYPE=vnc ]
>>
>>  If I remove the template the machine boots into Xen and opennebula
>> and I access the virtual machine using the command
>>
>> xm console IDMachine
>>
>> The template instantiate is:
>>
>> [root@VTSS003 CUQUE]# cat VMencourageprueba4.tmpl
>> NAME   = Encourageprueba4
>> MEMORY = 4096
>> CPU= 1
>> OS=[ KERNEL = "/boot/vmlinuz-2.6.32-279.el6.x86_64", INITRD =
>> "/boot/initramfs-2.6.32-279.el6.x86_64.img", root = "xvda1" ] DISK =[
>> DRIVER="file:", IMAGE_ID="29", TARGET="xvda1" ] DISK =[ TYPE  =
>> "swap", SIZE = 1024, TARGET = "sdb"  ] NIC = [ NETWORK_ID = 3 ] RAW=[
>> DATA="device_model='/usr/lib64/xen/bin/qemu-dm'", TYPE=xen ]
>>
>> And the deployment created:
>>
>> [root@VTSS003 124]# cat deployment.0
>> name = 'one-124'
>> #O CPU_CREDITS = 256
>> memory  = '4096'
>> kernel = '/boot/vmlinuz-2.6.32-279.el6.x86_64'
>> ramdisk = '/boot/initramfs-2.6.32-279.el6.x86_64.img'
>> root = '/dev/xvda1'
>> disk = [
>> 'file:/var/lib/one//datastores/0/124/disk.0,xvda1,w',
>> 'tap:aio:/var/lib/one//datastores/0/124/disk.1,sdb,w',
>> ]
>> vif = [
>> ' mac=02:00:5f:d3:e8:04,ip=95.211.232.4,bridge=br0',
>> ]
>> device_model='/usr/lib64/xen/bin/qemu-dm'
>>
>>
>> can you see any error on line to VNC:   GRAPHICS=[ KEYMAP=es, 
>> LISTEN=0.0.0.0, PORT=5902, TYPE=vnc ]
>>
>> regards.
>> Javier.
>>
>> ---
>> Javier Cuquerella Sánchez
>>
>> javier.cuquere...@atos.net
>> Atos Research & Innovation
>> Systems Administrator
>> Albarracin 25
>> 28037-Madrid (SPAIN)
>> Tfno: +34.91.214.8080
>> www.atosresearch.eu
>> es.atos.net
>>
>>
>> -Original Message-
>> From: Javier Fontan [mailto:jfon...@opennebula.org]
>> Sent: Wednesday, March 26, 2014 4:19 PM
>> To: Cuquerella Sanchez, Javier
>> Cc: users@lists.opennebula.org
>> Subject: Re: Problem boot VM template with opennebula
>>
>> Let's try taking out a couple of parameters. KERNEL_CMD, swap disk, 
>> device_model and VNC. I'm using the template you provided in a previous 
>> email:
>>
>> NAME   = Encourage7
>> MEMORY = 4096
>> CPU= 1
>> OS=[ KERNEL = "/boot/vmlinuz-2.6.32-279.el6.x86_64", INITRD =
>> "/boot/initramfs-2.6.32-279.el6.x86_64.img", root = "xvda1" ] DISK =[
>> DRIVER="file:", IMAGE_ID="27", TARGET="xvda1" ] NIC = [ NETWORK_ID = 3
>> ]
>>
>> In case this works you can start adding some other parameters. I'll start 
>> with the swap disk.
>>
>> On Wed, Mar 26, 2014 at 3:55 PM, Cuquerella Sanchez, Javier 
>>  wrote:
>>> Hi,
>>>
>>> The deployment file generated by OpenNebula is:
>>>
>>> [root@VTSS003 114]# cat deployment.0
>>> name = 'one-114'
>>> #O CPU_CREDITS = 256
>>> memory  = '4096'
>>> kernel = '/boot/vmlinuz-2.6.32-279.el6.x86_64'
>>> ramdisk = '/boot/initramfs-2.6.32-279.el6.x86_64.img'
>>> root = '/dev/xvda1'
>>> extra = 'ro xencons=tty console=tty1'
>>> disk = [
>>> 'file:/var/lib/one//datastores/0/114/disk.0,xvda1,w',
>>> 'tap:aio:/var/lib/one//datastores/0/114/disk.1,sdb,w',
>>> ]
>>> vif = [
>>> ' mac=02:00:5f:d3:e8:04,ip=95.211.232.4,bridge=br0',
>>> ]
>>> vfb = ['type=vnc,vnclisten=0.0.0.0,vncdisplay=2,keymap=es']
>>> device_model='/usr/lib64/xen/bin/qemu-dm'
>>>
>>>
>>> Thanks
>>>
>>> Regards
>>>
>>> ---
>>> Javier Cuquerella Sánchez
>>>
>>> javier.cuquere...@atos.net
>>> Atos Research & Innovation
>>> Systems Administrator
>>> Albarracin 25
>>> 28037-Madrid (SPAIN)
>>> Tfno: +34.91.214.8080
>>> www.atosresearch.eu
>>> es.atos.net
>>>
>>>
>>> -Original Message-
>>> From: Javier

Re: [one-users] Unable to deploy VMs - OpenVswitch issues

[Rodolfo Conte Brufatto]

Of course, there you go:

I am using Precise here too (12.04)

* OpenVswitch:

ii  openvswitch-common   1.4.6-0ubuntu1.12.04.2   Open
vSwitch common components
ii  openvswitch-controller   1.4.6-0ubuntu1.12.04.2   Open
vSwitch controller implementation
ii  openvswitch-datapath-dkms1.4.6-0ubuntu1.12.04.2   Open
vSwitch datapath module source - DKMS version
ii  openvswitch-pki  1.4.6-0ubuntu1.12.04.2   Open
vSwitch public key infrastructure dependency package
ii  openvswitch-switch   1.4.6-0ubuntu1.12.04.2   Open
vSwitch switch implementations

* libvirt

ii  libvirt-bin  0.9.8-2ubuntu17.17   programs
for the libvirt library
ii  libvirt0 0.9.8-2ubuntu17.17   library
for interfacing with different virtualization systems

The module bridge is blacklisted already.

Cheers!


On Wed, Apr 9, 2014 at 4:54 AM, Leszek Master  wrote:

> What OS do you use ? I've had similiar problem with ubuntu 12.04 LTS with
> old version of libvirtd and openvswitch, where i had to remove bridge
> module and add brcompat module. Show us your OS version, libvirtd and
> openvswitch.
>
>
> 2014-04-08 23:44 GMT+02:00 Rodolfo Conte Brufatto :
>
>> Hello everyone,
>> I am facing some issues when trying to deploy some new VM instances on a
>> new host (I am using OpenNebula 3.8.3 here).
>> In the logs I get:
>>
>> Tue Apr  8 18:28:32 2014 [VMM][I]: error: Unable to add bridge XXX port 
>> vnet0: Operation not supported
>>
>> I've properly configured the bridges and attached the interfaces using
>> ovs-vsctl and the users are already added in sudoers.
>>
>> Is there someone out there facing similar issues that can help me out?
>>
>>  Thanks in advance,
>>
>> Regards.
>>
>> --
>> Have you tried turning it off and on again?
>>
>> ___
>> Users mailing list
>> Users@lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>


-- 
Have you tried turning it off and on again?
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Datablock ceph errors.

[Leszek Master]

It worked. Thank you very much ! :)


2014-04-08 22:44 GMT+02:00 Ruben S. Montero :

> Hi
>
> This is a known issue[1] for 4.4, it's been fixed for 4.6. You may apply
> this patch[2] to the kvm driver file and sync your hosts[3].
>
> [1] http://dev.opennebula.org/issues/2822
> [2]
> http://dev.opennebula.org/projects/opennebula/repository/revisions/3098252c03b5da69835129992b06bcb761ae3131/diff/src/vmm_mad/remotes/kvm/attach_disk
> [3]
> http://docs.opennebula.org/4.4/administration/hosts_and_clusters/host_guide.html#sync
>
>
> On Tue, Apr 8, 2014 at 8:34 PM, Leszek Master  wrote:
>
>> I noticed that OpenNebula don't add this lines:
>>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>>
>>  to the /var/lib/one/rbd.attach file. How can i add this automatically to
>> any new rbd datablock i want to add? It's annooying that i need to put it
>> in this file manually. There must be someway.
>>
>> Please help.
>>
>>
>>
>> 2014-04-08 20:16 GMT+02:00 Leszek Master :
>>
>> Hi. I want to create a Datablock in my ceph and attach it to my VM. I
>>> created 100 GB datablock and when i try to attach it to my VM i've got
>>> error:
>>>
>>> error: operation failed: open disk image file failed
>>>
>>> But i can map it onto my hypervisor host from ceph storage. How can i
>>> attack this datablock to my VM's ?
>>>
>>> Please help.
>>>
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>> --
>> 
>> --
>> Ruben S. Montero, PhD
>> Project co-Lead and Chief 
>> Architect
>> OpenNebula - Flexible Enterprise Cloud Made Simple
>>  
>> www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula
>>
>
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] occi-storage create error with big images

[Daniel Molina]

On 9 April 2014 10:03, Marco Mancini  wrote:

> Hello,
>
> sorry, it was a problem with disk space.
>
> I did some other tests and I noticed that there was not enough space on
> /var/tmp where 2 copies of the image are created during the upload.
> After resizing /var/tmp, the occi-storage create works now.
>
>
Great, thank you for the info


> Cheers,
> Marco.
>
>
>  
> Marco Mancini, PhD
>
> Scientific Computing & Operations Division
> Euro Mediterranean Center on Climate Change (CMCC)
> Via Augusto Imperatore 16 - 73100 Lecce (Italy)
> http://www.cmcc.it/
> email: marco.manc...@cmcc.it
> *
>
> Il giorno 08/apr/2014, alle ore 18:48, Daniel Molina <
> dmol...@opennebula.org> ha scritto:
>
> Hi,
>
>
> On 3 April 2014 12:17, Marco Mancini  wrote:
>
>> Hello,
>>
>> I have installed opennebula 4.4.1.
>> I got a 'Send Failure: Broken pipe' error by using occi-storage with a
>> 11GB image file. After the error it is also necessary to restart the
>> occi-server.
>> If i use occi-storage with a small file (ttylinux image 40MB), the image
>> is uploaded successfully.
>>
>> In the following, the output of the command occi-storage with --debug
>> option by using the file storage.xml
>> 
>> Ubuntu Server
>> Ubuntu server
>> OS
>> file:///repository/ubuntu-server-12.04-1.3.img
>> 
>>
>>
>> oneadmin@one:~/test_occi$ occi-storage --debug create storage.xml
>> * About to connect() to localhost port 4567 (#0)
>> *   Trying 127.0.0.1... * connected
>> * Server auth using Basic with user 'oneadmin'
>> > POST /storage HTTP/1.1
>> Authorization:
>> Basic b25lYWRtaW46NGJkOTAxY2RlOTVjY2QxYWJmNzBkMzM0ZWM5MTg4N2E0MzI5NDliNg==
>> Host: localhost:4567
>> Accept: */*
>> Content-Length: 11811160571
>> Expect: 100-continue
>> Content-Type: multipart/form-data;
>> boundary=10171bec94ac
>>
>> * Done waiting for 100-continue
>> * Send failure: Broken pipe
>> * Closing connection #0
>> Curl::Err::SendError
>>
>>
> Could you try using the -M option in the occi-storage command?
>
> Cheers
>
>
>
>> 
>>
>> Best Regards,
>> Marco.
>>
>>
>> 
>> Marco Mancini, PhD
>>
>> Scientific Computing & Operations Division
>> Euro Mediterranean Center on Climate Change (CMCC)
>> Via Augusto Imperatore 16 - 73100 Lecce (Italy)
>> http://www.cmcc.it/
>> email: marco.manc...@cmcc.it
>> *
>>
>>
>> ___
>> Users mailing list
>> Users@lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>>
>
>
> --
> --
> Daniel Molina
> Project Engineer
> OpenNebula - Flexible Enterprise Cloud Made Simple
> www.OpenNebula.org  | dmol...@opennebula.org| 
> @OpenNebula
>
>
>


-- 
--
Daniel Molina
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] occi-storage create error with big images

[Marco Mancini]

Hello,

sorry, it was a problem with disk space.

I did some other tests and I noticed that there was not enough space on 
/var/tmp where 2 copies of the image are created during the upload.
After resizing /var/tmp, the occi-storage create works now.

Cheers,
Marco.

 

Marco Mancini, PhD

Scientific Computing & Operations Division
Euro Mediterranean Center on Climate Change (CMCC)
Via Augusto Imperatore 16 - 73100 Lecce (Italy)
http://www.cmcc.it/
email: marco.manc...@cmcc.it
*

Il giorno 08/apr/2014, alle ore 18:48, Daniel Molina  
ha scritto:

> Hi,
> 
> 
> On 3 April 2014 12:17, Marco Mancini  wrote:
> Hello,
> 
> I have installed opennebula 4.4.1.
> I got a ‘Send Failure: Broken pipe’ error by using occi-storage with a 11GB 
> image file. After the error it is also necessary to restart the occi-server.  
> If i use occi-storage with a small file (ttylinux image 40MB), the image is 
> uploaded successfully.
> 
> In the following, the output of the command occi-storage with —debug option 
> by using the file storage.xml
> 
> Ubuntu Server
> Ubuntu server
> OS
> file:///repository/ubuntu-server-12.04-1.3.img
> 
> 
> 
> oneadmin@one:~/test_occi$ occi-storage --debug create storage.xml
> * About to connect() to localhost port 4567 (#0)
> *   Trying 127.0.0.1... * connected
> * Server auth using Basic with user 'oneadmin'
> > POST /storage HTTP/1.1
> Authorization: Basic 
> b25lYWRtaW46NGJkOTAxY2RlOTVjY2QxYWJmNzBkMzM0ZWM5MTg4N2E0MzI5NDliNg==
> Host: localhost:4567
> Accept: */*
> Content-Length: 11811160571
> Expect: 100-continue
> Content-Type: multipart/form-data; 
> boundary=10171bec94ac
> 
> * Done waiting for 100-continue
> * Send failure: Broken pipe
> * Closing connection #0
> Curl::Err::SendError
> 
> 
> Could you try using the -M option in the occi-storage command?
> 
> Cheers
> 
>  
> 
> 
> Best Regards,
> Marco.
> 
> 
> 
> Marco Mancini, PhD
> 
> Scientific Computing & Operations Division
> Euro Mediterranean Center on Climate Change (CMCC)
> Via Augusto Imperatore 16 - 73100 Lecce (Italy)
> http://www.cmcc.it/
> email: marco.manc...@cmcc.it
> *
> 
> 
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> 
> 
> 
> 
> -- 
> --
> Daniel Molina
> Project Engineer
> OpenNebula - Flexible Enterprise Cloud Made Simple
> www.OpenNebula.org | dmol...@opennebula.org | @OpenNebula

___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Unable to deploy VMs - OpenVswitch issues

[Leszek Master]

What OS do you use ? I've had similiar problem with ubuntu 12.04 LTS with
old version of libvirtd and openvswitch, where i had to remove bridge
module and add brcompat module. Show us your OS version, libvirtd and
openvswitch.


2014-04-08 23:44 GMT+02:00 Rodolfo Conte Brufatto :

> Hello everyone,
> I am facing some issues when trying to deploy some new VM instances on a
> new host (I am using OpenNebula 3.8.3 here).
> In the logs I get:
>
> Tue Apr  8 18:28:32 2014 [VMM][I]: error: Unable to add bridge XXX port 
> vnet0: Operation not supported
>
> I've properly configured the bridges and attached the interfaces using
> ovs-vsctl and the users are already added in sudoers.
>
> Is there someone out there facing similar issues that can help me out?
>
> Thanks in advance,
>
> Regards.
>
> --
> Have you tried turning it off and on again?
>
> ___
> 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