Re: [one-users] Image in used state but no VM associte with it

[Anandharaj Subramaniam]

Hi Carlos,

Thank you for your feedback. I will do it accordingly.


--
Regards,
Anandharaj
Server & Storage Support Team
MIMOS Berhad

From: Carlos Martín Sánchez [mailto:cmar...@opennebula.org]
Sent: Tuesday, February 17, 2015 6:28 PM
To: Anandharaj Subramaniam
Cc: users@lists.opennebula.org
Subject: Re: [one-users] Image in used state but no VM associte with it

Hi,

That IP looks good (202.45.142.114). It might be a bug that can be affected by 
the ruby version.
Since this is a 4.2 version and the leases were completely redone for new 
versions, maybe the best thing to do is comment out the whole vnet section in 
fsck.rb, lines 920-1066.

Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | 
cmar...@opennebula.org | 
@OpenNebula

On Thu, Feb 12, 2015 at 4:58 AM, Anandharaj Subramaniam 
mailto:anandharaj.man...@mimos.my>> wrote:
Hi Carlos,

Below is the last few lines of output before it throwing the error. How do I 
proceed to troubleshoot on this.

row[:ip]: 3391983169
doc: 
3391983169512339198316911371

row[:ip]: 3391983218
doc: 
3391983218512339198321811372
Exception `ArgumentError' at /usr/lib/ruby/1.8/ipaddr.rb:481 - address family 
mismatch
address family mismatch
Error running fsck version 4.2.0
The database will be restored


--
Regards,
Anandharaj
Server & Storage Support Team
MIMOS Berhad

From: Carlos Martín Sánchez 
[mailto:cmar...@opennebula.org]
Sent: Friday, January 16, 2015 10:49 PM

To: Anandharaj Subramaniam
Cc: users@lists.opennebula.org
Subject: Re: [one-users] Image in used state but no VM associte with it

Hi,

I don't know what can be causing the error. Can you to add the following lines 
right before line 929 in /usr/lib/one/ruby/onedb/fsck.rb?

warn ""
warn "row[:ip]: #{row[:ip]}"
warn "doc: #{doc.to_s}"

https://github.com/OpenNebula/one/blob/release-4.2/src/onedb/fsck.rb#L929

Maybe that will show if there is something wrong with that IP that is throwing 
the error.


--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | 
cmar...@opennebula.org | 
@OpenNebula

On Fri, Jan 16, 2015 at 3:16 AM, Anandharaj Subramaniam 
mailto:anandharaj.man...@mimos.my>> wrote:
Hi Carlos,

What is your ruby version?

==> ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]

Are all of your leases IPv4?

==> Yes, all IPv4

--
Regards,
Anandharaj

From: Carlos Martín Sánchez 
[mailto:cmar...@opennebula.org]
Sent: Tuesday, January 13, 2015 6:55 PM
To: Anandharaj Subramaniam
Cc: users@lists.opennebula.org
Subject: Re: [one-users] Image in used state but no VM associte with it

Hi,

What is your ruby version?
Are all of your leases IPv4?

Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | 
cmar...@opennebula.org | 
@OpenNebula

On Tue, Dec 30, 2014 at 3:19 AM, Anandharaj Subramaniam 
mailto:anandharaj.man...@mimos.my>> wrote:
Hi All,

When I run using debug mode, I see this message.

….
/usr/lib/ruby/gems/1.8/gems/sequel-3.46.0/lib/sequel/dataset/actions.rb:151: 
warning: instance variable @row_proc not initialized
VNet 25 has used lease 10.1.66.8 (VM 858)   but it is free
Exception `ArgumentError' at /usr/lib/ruby/1.8/ipaddr.rb:481 - address family 
mismatch
address family mismatch
Error running fsck version 4.2.0
The database will be restored


--
Regards,
Anandharaj

From: Anandharaj Subramaniam
Sent: Monday, December 29, 2014 7:34 PM

To: users@lists.opennebula.org
Subject: RE: Image in used state but no VM associte with it

Hi All,

I restored the mysql database and run the onedb fsck, still the process 
terminate with “Error running fsck version 4.2.0” but the messages of the 
inconsistency is less.
Appreciate the expert help on this.

Note: We are still using 4.2 because we have our own apps integrated with it. 
We already have plan to setup another ONE with version 4.10

--
Regards,

Anandharaj
MIMOS Bhd

From: Anandharaj Subramaniam
Sent: Monday, December 29, 2014 3:36 PM
To: users@lists.opennebula.org
Subject: RE: Image in used state but no VM associte with it

Hi All,

When I run onedb fck, got the following messages but ended with error.

[oneadmin@server 101]$ onedb fsck -f -S localhost -u oneadmin  -d opennebula
MySQL Password:
MySQL dump stored in /var/lib/one/mysql_localhost_opennebula.sql
Use 'onedb restore' or restore the DB using the mysql command:
mysql -u user -h server -P port db_name < backup_file

Host 20 is in Cluster 101 h

Re: [one-users] "Official" Debian packages

[Daniel Dehennin]

Jaime Melis  writes:

>> Hmm, writing the question seems to gives my answer, it looks like the
>> cherry-picking of master commits on the one- branches are the
>> reasons of the merge conflicts.
>>
>
> Yes... that's the way we usually do it: by cherry picking the commits.

Ok, I'll broke everything to rebase on master then.

> Unfortunately we don't think there's an easier way.

Personally, I prefer to use DaggyFix[1][2] over cherry-picking.

This requires to base the commits on the oldest supported release and
then merge them everywhere needed, which can be seen as a lot of work,
but not that much different from doing cherry-picking ;-)

I think DaggyFix is more GIT friendly and respect the context as explain
in an article I just found[3].

For example, here is the GIT graph to apply a foo-bar patch (issue #42):

o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-o-M₃ <- master
   \ \   \   \ /
\ \   \   o-o-o-o-M₂  /<- prod/4/master (integration branch for 
version 4)
 \ \   \ /   /
  \ \   \ o-o---+  <- prod/3/42-foo-bar (short living branch)
   \ \   \   /   \
\ \   o-o-o-o-M₁   <- prod/3/master (integration branch for 
version 3)
 \ \
  \ o-o-o-o-o-o-o-M₀   <- prod/2/master (integration branch for 
version 2)
   \ \   /
\ o-o-o-o  <- prod/2/41-fix-something
 \
  o-o-o-o-o-o  <- prod/1/master (integration branch for 
version 1)

in this example:

- version 1 is not supported anymore

- version 2 is supported but not concerned by #42: foo-bar

A temporary branch is created based on version 3 named prod/3/42-foo-bar and
the commits are done here.

I use do to prefix my branch names by the name of the release branch it
first apply to, it help to sort them when doing “git branch” ;-)

Then, this 42/foo-bar branch is merge back into version 3 integration
branch (commit M₁), to prepare a new release 3.X.

This 42/foo-bar branch is merge into version 4 integration branch
(commit M₂) if it apply to it like in my example.

Finally, this 42/foo-bar branch is merge into the main development
branch (commit M₃) if it apply to it like in my example.

This is based on the “successful Git branching model[4]” I extended with
the packaging branches.

I hope it will help you, it took me time to find some kind of best
practice I agree with, like “Is it better to rebase or merge?[5]”.

Regards.

Footnotes: 
[1]  by mercurial http://mercurial.selenic.com/wiki/DaggyFixes

[2]  by monotone http://wiki.monotone.ca/DaggyFixes/

[3]  https://queue.acm.org/detail.cfm?id=1595636

[4]  http://nvie.com/posts/a-successful-git-branching-model/

[5]  http://www.randyfay.com/node/91

-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF


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

Re: [one-users] Getting an "HTTP-Error: 500" when executing oneacct -g group

[RubEn DIez LAzaro]

Compile our own OpenNebula will break the package system maintenance. 
You can forget use yum or any other package management system. You can 
forget about the updating scripts associate to the package for 
automatically migrate and adapt the database schemes to updated versions


Compile our own OpenNebula in a production infrastructure means return 
to the Dark Ages from a sysadmin point of view... for EVERY site with 
this issue...


In the easy way, OpenNebula staff should use a fixed version of 
libxmlrpc-c and so distribute a fixed package of OpenNebula.


Other possibility is that libxmlrpc-c become a dynamically linked 
library instead statically linked one. In this way each site could use a 
fixed version of libxmlrpc-c


Regards.


On 17/02/15 11:15, Esteban Freire wrote:

Hi Carlos,

Thank you very much for letting us know, we need to think it deeply :)

Just one question, which are the pros and cons of compiling oned? It 
is a serious thing for us since the infrastructure is on production 
and I am not sure if it will break future updates trough yum/rpm and 
also, if we could break something in current ON installation at CESGA. 
Personally, I don't like this decision but it is my humble opinion and 
in any case, we need to discuss about it.


Thanks in advance,
Esteban

On 02/17/2015 11:05 AM, Carlos Martín Sánchez wrote:

Hi,

I forgot to add that if you want to test the new libxmlrpc version 
yourself, it's not that difficult to compile oned with the 'xmlrpc' 
scons option:

http://docs.opennebula.org/4.10/integration/references/compile.html

Regards.

--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org  | 
cmar...@opennebula.org  | @OpenNebula 



On Fri, Feb 13, 2015 at 10:39 AM, RubEn DIez LAzaro > wrote:


Hi:

I Does not know really if some recent version of libxmlrpc-c fix
this bug... bug the patch seems to be into some branch

http://sourceforge.net/p/xmlrpc-c/code/2520/

I don't pretend to confuse you with how we discover this bug, but
in short it appears when executing some accounting software by
Boris Parak for the Federate cloud of the EGI project

I hope the patch i link help to clarify the situation.

Best regards.



On 12/02/15 22:53, Alejandro Feijóo wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi to all.

As Esteban say,  we have a planned updated to last stable
opennebula
release the Wednesday 18th, but i think we can wait if the
libxmlrpc-c
is updated in the next days or maybe weeks.

I think we can wait because the new ON not have critical
changes (we
have pached one-flow yet) and make 2 updates in the same
month can be a
problem for our costumers... (we use oneflow in a lot of critical
services and is a problem make 2 scheduled stops)


But if the change is programated to 4.12 we going to update
and patch it
(I think Ruben have a special love story paching software hehe)


Again, a lot of thanks.


El 12/02/15 a las 19:32, Esteban Freire escribió:

Hi Carlos,

Thank you very much for checking it :)

About if it should be fixed in 1.33.14, I hope Rubén
answer to this
tomorrow since it is the one looking at this issue.

When do you think we could test this? Sorry for the
question/hurry but
we are failing accounting due to this issue in FedCloud
(EGI). In
principle, we are going to update to last ON version next
Wednesday 18th.

Thanks in advance,
Esteban

On 02/12/2015 07:23 PM, Carlos Martín Sánchez wrote:

Hi,

I'm not directly involved in the packaging, but as
far as I can tell,
OpenNebula 4.8 comes with libxmlrpc-c version 1.33.6.
If I understand correctly, the problem you report
should be fixed in
1.33.14?

I've checked and the current super stable version is
1.33.16 [1]. We
will see if the static library can be updated without
breaking
anything [2].

Regards.

[1]
http://xmlrpc-c.sourceforge.net/change_super_stable.html
[2] http://dev.opennebula.org/issues/3594

-- 
Carlos Martín, MSc

Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org 
 |
cmar...@opennebula.org
  

Re: [one-users] wrong gateway detected by vm-context

[Javier Fontan]

We should probably take out the code that generates the gateway as it only
gives problems:

https://github.com/OpenNebula/addon-context-linux/blob/master/base_rpm/etc/one-context.d/00-network#L68-L73

Concerning the GATEWAY_INTERFACE, this variable contains a number or the
ETH that appears in the context file. In fact it is not the name of
the interface as with the new naming scheme it can be called with a
different name, for example en3p8.

http://en.wikipedia.org/wiki/Consistent_Network_Device_Naming

Cheers

On Fri Feb 13 2015 at 1:49:42 PM Madko  wrote:

> I have found the solution. GATEWAY_IFACE must be set, but in upper case. I
> don't know why. Any idea? If I put GATEWAY_IFACE=eth1 (eth1 is the real
> name) it doesn't work, but GATEWAY_IFACE=ETH1 works...
>
> Le Fri Feb 13 2015 at 10:03:33, Madko  a écrit :
>
> Hi,
>>
>> It seems vmcontext scripts try to guess the gateway IP as soon as any
>> interface has a gateway set.
>>
>> Here is my case:
>> one vm with eth0 to internal admin network, and eth1 to wan. Only eth1
>> has a gateway set.
>> When init script vmcontext start, it found out that there is a gateway
>> (but on eth1), and so is_gateway function on eth0 seems to returns true.
>> After that the gateway is guessed with NETWORK_ADDRESS.1 but I don't know
>> why?
>>
>> here is my context:
>> ETH0_IP='192.168.199.109'
>> ETH0_MAC='02:00:c0:a8:c7:6d'
>> ETH1_DNS='10.156.255.245'
>> ETH1_GATEWAY='10.156.0.1'
>> ETH1_IP='10.156.24.93'
>> ETH1_MAC='02:00:0a:9c:18:5d'
>> ETH1_MASK='255.255.224.0'
>> ETH1_NETWORK='10.156.0.0'
>>
>> Here is the ifcfg-eth0 written by vmcontext init script:
>> DEVICE=eth0
>> BOOTPROTO=none
>> ONBOOT=yes
>> TYPE=Ethernet
>> NETMASK=255.255.255.0
>> IPADDR=192.168.199.109
>> GATEWAY=192.168.199.1
>>
>> ifcfg-eth1 is good and has its gateway correctly set.
>>
>> Here is my vnet template where no gateway is set (same problem if I
>> remove the empty GATEWAY key):
>> VIRTUAL NETWORK TEMPLATE
>>
>> BRIDGE="br0"
>> DESCRIPTION="réseau admin vm"
>> GATEWAY=""
>> PHYDEV=""
>> ROLE="admin"
>> VLAN="YES"
>> VLAN_ID="199"
>>
>> is it a bug?
>>
>> Attached here is the vmcontext network script log
>>
>> best regards,
>>
>> Edouard
>>
> ___
> 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] SET Hostname VM

[Carlos Martín Sánchez]

Hi,

If you mean the OpenNebula VM name, it is automatically set to
-. It can be changed when the template is
instantiated in the Sunstone wizard, or with the --name option in the cli.

Regards.

--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula
 

2015-02-10 11:54 GMT+01:00 barbieri vincenzo <
vincenzo.barbi...@vbarbieri.com>:

>  Hi
>
>  I do not have to change it on the hypervisor, but when I launch the
> installation via OpenNebula
>
>
>  --
> *Da:* Carlos Martín Sánchez [cmar...@opennebula.org]
> *Inviato:* martedì 10 febbraio 2015 10.26
> *A:* barbieri vincenzo
> *Cc:* users@lists.opennebula.org
> *Oggetto:* Re: [one-users] SET Hostname VM
>
>   Hi,
>
>  2015-02-09 14:18 GMT+01:00 barbieri vincenzo <
> vincenzo.barbi...@vbarbieri.com>:
>
>>  Hi
>> I am creating a vm with the installation from scratch, but I can not set
>> the name is always set to one-vid .
>> Please help me
>>
>
> The name of the VM in the hypervisor cannot be changed.
>
>  Regards.
>  --
> Carlos Martín, MSc
> Project Engineer
> OpenNebula - Flexible Enterprise Cloud Made Simple
> www.OpenNebula.org  | cmar...@opennebula.org
>  | @OpenNebula  
>
>
>
> --
> This message has been scanned for viruses and dangerous content by
> *E.F.A. Project* , and is believed to be
> clean.
> Click here to report this message as spam.
> 
>   Le comunicazioni Internet non sono sicure e quindi Vbarbieri non
> accetta alcuna responsabilita' per il contenuto di questo messaggio.
> Sebbene vbarbieri abbia attivato programmi anti-virus, non accetta
> responsabilita' per qualsiasi tipo di danno che possa derivare dal
> trasferimento di virus.Qualsiasi punto di vista od opinione espressa sono
> esclusivamente quelli dell'autore e non rappresentano necessariamente
> quelli di Vbarbieri . Le risposte a questo messaggio elettronico possono
> essere controllate da Vbarbieri per ragioni di sicurezza, operative o
> aziendali. Nel rispetto delle disposizioni di legge e regolamento
> applicabili, Vbarbieri si riserva il diritto di monitorare le comunicazioni
> elettroniche attraverso apposite attivita' di monitoraggio finalizzate
> all'identificazione e alla prevenzione della diffusione accidentale e/o
> fraudolenta di informazioni. Qualsiasi uso non autorizzato di questo
> messaggio elettronico o dei suoi allegati e' proibito e potrebbe costituire
> un reato. Se non siete il destinatario desiderato di questa mail, qualunque
> comunicazione, copia, distribuzione oqualunque azione od omissione in
> relazione ai dati in essa contenuti e' illecita, e siete pregato di
> informare immediatamente il mittente utilizzando l'opzione "Rispondi" nel
> vostro software di postaelettronica e di distruggere il messaggio e tutti i
> suoi allegati.
>
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] Image in used state but no VM associte with it

[Carlos Martín Sánchez]

Hi,

That IP looks good (202.45.142.114). It might be a bug that can be affected
by the ruby version.
Since this is a 4.2 version and the leases were completely redone for new
versions, maybe the best thing to do is comment out the whole vnet section
in fsck.rb, lines 920-1066.

Regards
--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula
 

On Thu, Feb 12, 2015 at 4:58 AM, Anandharaj Subramaniam <
anandharaj.man...@mimos.my> wrote:

>  Hi Carlos,
>
>
>
> Below is the last few lines of output before it throwing the error. How do
> I proceed to troubleshoot on this.
>
>
>
> row[:ip]: 3391983169
>
> doc:
> 3391983169512339198316911371
>
>
>
> row[:ip]: 3391983218
>
> doc:
> 3391983218512339198321811372
>
> Exception `ArgumentError' at /usr/lib/ruby/1.8/ipaddr.rb:481 - address
> family mismatch
>
> address family mismatch
>
> Error running fsck version 4.2.0
>
> The database will be restored
>
>
>
>
>
> --
>
> *Regards,*
>
> Anandharaj
>
> Server & Storage Support Team
>
> MIMOS Berhad
>
>
>
> *From:* Carlos Martín Sánchez [mailto:cmar...@opennebula.org]
> *Sent:* Friday, January 16, 2015 10:49 PM
>
> *To:* Anandharaj Subramaniam
> *Cc:* users@lists.opennebula.org
> *Subject:* Re: [one-users] Image in used state but no VM associte with it
>
>
>
> Hi,
>
>
>
> I don't know what can be causing the error. Can you to add the following
> lines right before line 929 in /usr/lib/one/ruby/onedb/fsck.rb?
>
>
>
> warn ""
>
> warn "row[:ip]: #{row[:ip]}"
>
> warn "doc: #{doc.to_s}"
>
>
>
> https://github.com/OpenNebula/one/blob/release-4.2/src/onedb/fsck.rb#L929
>
>
>
> Maybe that will show if there is something wrong with that IP that is
> throwing the error.
>
>
>
>
>   --
>
> Carlos Martín, MSc
> Project Engineer
>
> OpenNebula - Flexible Enterprise Cloud Made Simple
>
> www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula
> 
>
>
>
> On Fri, Jan 16, 2015 at 3:16 AM, Anandharaj Subramaniam <
> anandharaj.man...@mimos.my> wrote:
>
> Hi Carlos,
>
>
>
> What is your ruby version?
>
> è ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
>
>
>
> Are all of your leases IPv4?
>
> è Yes, all IPv4
>
>
>
> --
>
> Regards,
>
> Anandharaj
>
>
>
> *From:* Carlos Martín Sánchez [mailto:cmar...@opennebula.org]
> *Sent:* Tuesday, January 13, 2015 6:55 PM
> *To:* Anandharaj Subramaniam
> *Cc:* users@lists.opennebula.org
> *Subject:* Re: [one-users] Image in used state but no VM associte with it
>
>
>
> Hi,
>
>
>
> What is your ruby version?
>
> Are all of your leases IPv4?
>
>
>
> Regards
>
> --
>
> Carlos Martín, MSc
> Project Engineer
>
> OpenNebula - Flexible Enterprise Cloud Made Simple
>
> www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula
> 
>
>
>
> On Tue, Dec 30, 2014 at 3:19 AM, Anandharaj Subramaniam <
> anandharaj.man...@mimos.my> wrote:
>
> Hi All,
>
>
>
> When I run using debug mode, I see this message.
>
>
>
> ….
>
> /usr/lib/ruby/gems/1.8/gems/sequel-3.46.0/lib/sequel/dataset/actions.rb:151:
> warning: instance variable @row_proc not initialized
>
> VNet 25 has used lease 10.1.66.8 (VM 858)   but it is free
>
> Exception `ArgumentError' at /usr/lib/ruby/1.8/ipaddr.rb:481 - address
> family mismatch
>
> address family mismatch
>
> Error running fsck version 4.2.0
>
> The database will be restored
>
>
>
>
>
> --
>
> Regards,
>
> Anandharaj
>
>
>
> *From:* Anandharaj Subramaniam
> *Sent:* Monday, December 29, 2014 7:34 PM
>
>
> *To:* users@lists.opennebula.org
> *Subject:* RE: Image in used state but no VM associte with it
>
>
>
> Hi All,
>
>
>
> I restored the mysql database and run the onedb fsck, still the process
> terminate with “Error running fsck version 4.2.0” but the messages of the
> inconsistency is less.
>
> Appreciate the expert help on this.
>
>
>
> Note: We are still using 4.2 because we have our own apps integrated with
> it. We already have plan to setup another ONE with version 4.10
>
>
>
> --
>
> Regards,
>
>
>
> *Anandharaj*
>
> MIMOS Bhd
>
>
>
> *From:* Anandharaj Subramaniam
> *Sent:* Monday, December 29, 2014 3:36 PM
> *To:* users@lists.opennebula.org
> *Subject:* RE: Image in used state but no VM associte with it
>
>
>
> Hi All,
>
>
>
> When I run onedb fck, got the following messages but ended with error.
>
>
>
> [oneadmin@server 101]$ onedb fsck -f -S localhost -u oneadmin  -d
> opennebula
>
> MySQL Password:
>
> MySQL dump stored in /var/lib/one/mysql_localhost_opennebula.sql
>
> Use 'onedb restore' or restore the DB using the mysql command:
>
> mysql -u user -h server -P port db_name < backup_file
>
>
>
> Host 20 is in Cluster 101 host id list, but it should not
>
> VM 373 is using Host 20, but it does not exist
>
> VM 401 is using Host 20, but it does not exist
>
> VM 522 is using Host 20, but it does not exist
>
> VM 531 is using Host 20, but it does not exist
>
> VM 585 is using Host 20, bu

Re: [one-users] Getting an "HTTP-Error: 500" when executing oneacct -g group

[Esteban Freire]

Hi Carlos,

Thank you very much for letting us know, we need to think it deeply :)

Just one question, which are the pros and cons of compiling oned? It is 
a serious thing for us since the infrastructure is on production and I 
am not sure if it will break future updates trough yum/rpm and also, if 
we could break something in current ON installation at CESGA. 
Personally, I don't like this decision but it is my humble opinion and 
in any case, we need to discuss about it.


Thanks in advance,
Esteban

On 02/17/2015 11:05 AM, Carlos Martín Sánchez wrote:

Hi,

I forgot to add that if you want to test the new libxmlrpc version 
yourself, it's not that difficult to compile oned with the 'xmlrpc' 
scons option:

http://docs.opennebula.org/4.10/integration/references/compile.html

Regards.

--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org  | 
cmar...@opennebula.org  | @OpenNebula 



On Fri, Feb 13, 2015 at 10:39 AM, RubEn DIez LAzaro > wrote:


Hi:

I Does not know really if some recent version of libxmlrpc-c fix
this bug... bug the patch seems to be into some branch

http://sourceforge.net/p/xmlrpc-c/code/2520/

I don't pretend to confuse you with how we discover this bug, but
in short it appears when executing some accounting software by
Boris Parak for the Federate cloud of the EGI project

I hope the patch i link help to clarify the situation.

Best regards.



On 12/02/15 22:53, Alejandro Feijóo wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi to all.

As Esteban say,  we have a planned updated to last stable
opennebula
release the Wednesday 18th, but i think we can wait if the
libxmlrpc-c
is updated in the next days or maybe weeks.

I think we can wait because the new ON not have critical
changes (we
have pached one-flow yet) and make 2 updates in the same month
can be a
problem for our costumers... (we use oneflow in a lot of critical
services and is a problem make 2 scheduled stops)


But if the change is programated to 4.12 we going to update
and patch it
(I think Ruben have a special love story paching software hehe)


Again, a lot of thanks.


El 12/02/15 a las 19:32, Esteban Freire escribió:

Hi Carlos,

Thank you very much for checking it :)

About if it should be fixed in 1.33.14, I hope Rubén
answer to this
tomorrow since it is the one looking at this issue.

When do you think we could test this? Sorry for the
question/hurry but
we are failing accounting due to this issue in FedCloud
(EGI). In
principle, we are going to update to last ON version next
Wednesday 18th.

Thanks in advance,
Esteban

On 02/12/2015 07:23 PM, Carlos Martín Sánchez wrote:

Hi,

I'm not directly involved in the packaging, but as far
as I can tell,
OpenNebula 4.8 comes with libxmlrpc-c version 1.33.6.
If I understand correctly, the problem you report
should be fixed in
1.33.14?

I've checked and the current super stable version is
1.33.16 [1]. We
will see if the static library can be updated without
breaking
anything [2].

Regards.

[1]
http://xmlrpc-c.sourceforge.net/change_super_stable.html
[2] http://dev.opennebula.org/issues/3594

-- 
Carlos Martín, MSc

Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org 
 |
cmar...@opennebula.org 
> | @OpenNebula


On Thu, Feb 12, 2015 at 12:08 PM, RubEn DIez LAzaro
mailto:rd...@cesga.es>
>> wrote:

 HI:

 The distro is Scientific Linux release 6.4
(Carbon) and ONE is
 installed from repo (it seems be the repo for
CentOS 6)

 [root@cloud yum.repos.d]# cat opennebula.repo
 [opennebula]
 name=opennebula
   
 baseurl=http://downloads.opennebula.org/repo/

Re: [one-users] "Official" Debian packages

[Jaime Melis]

Hi,

Should I rebase[2] all my branches on master directly and then follow
> the OpenNebula releases or is there a path to merge master and one-4.10?
>
>
> Hmm, writing the question seems to gives my answer, it looks like the
> cherry-picking of master commits on the one- branches are the
> reasons of the merge conflicts.
>

Yes... that's the way we usually do it: by cherry picking the commits.
Unfortunately we don't think there's an easier way.



-- 
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

Re: [one-users] Getting an "HTTP-Error: 500" when executing oneacct -g group

[Carlos Martín Sánchez]

Hi,

I forgot to add that if you want to test the new libxmlrpc version
yourself, it's not that difficult to compile oned with the 'xmlrpc' scons
option:
http://docs.opennebula.org/4.10/integration/references/compile.html

Regards.

--
Carlos Martín, MSc
Project Engineer
OpenNebula - Flexible Enterprise Cloud Made Simple
www.OpenNebula.org | cmar...@opennebula.org | @OpenNebula
 

On Fri, Feb 13, 2015 at 10:39 AM, RubEn DIez LAzaro  wrote:

> Hi:
>
> I Does not know really if some recent version of libxmlrpc-c fix this
> bug... bug the patch seems to be into some branch
>
> http://sourceforge.net/p/xmlrpc-c/code/2520/
>
> I don't pretend to confuse you with how we discover this bug, but in short
> it appears when executing some accounting software by Boris Parak for the
> Federate cloud of the EGI project
>
> I hope the patch i link help to clarify the situation.
>
> Best regards.
>
>
>
> On 12/02/15 22:53, Alejandro Feijóo wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA512
>>
>> Hi to all.
>>
>> As Esteban say,  we have a planned updated to last stable opennebula
>> release the Wednesday 18th, but i think we can wait if the libxmlrpc-c
>> is updated in the next days or maybe weeks.
>>
>> I think we can wait because the new ON not have critical changes (we
>> have pached one-flow yet) and make 2 updates in the same month can be a
>> problem for our costumers... (we use oneflow in a lot of critical
>> services and is a problem make 2 scheduled stops)
>>
>>
>> But if the change is programated to 4.12 we going to update and patch it
>> (I think Ruben have a special love story paching software hehe)
>>
>>
>> Again, a lot of thanks.
>>
>>
>> El 12/02/15 a las 19:32, Esteban Freire escribió:
>>
>>> Hi Carlos,
>>>
>>> Thank you very much for checking it :)
>>>
>>> About if it should be fixed in 1.33.14, I hope Rubén answer to this
>>> tomorrow since it is the one looking at this issue.
>>>
>>> When do you think we could test this? Sorry for the question/hurry but
>>> we are failing accounting due to this issue in FedCloud (EGI). In
>>> principle, we are going to update to last ON version next Wednesday 18th.
>>>
>>> Thanks in advance,
>>> Esteban
>>>
>>> On 02/12/2015 07:23 PM, Carlos Martín Sánchez wrote:
>>>
 Hi,

 I'm not directly involved in the packaging, but as far as I can tell,
 OpenNebula 4.8 comes with libxmlrpc-c version 1.33.6.
 If I understand correctly, the problem you report should be fixed in
 1.33.14?

 I've checked and the current super stable version is 1.33.16 [1]. We
 will see if the static library can be updated without breaking
 anything [2].

 Regards.

 [1] http://xmlrpc-c.sourceforge.net/change_super_stable.html
 [2] http://dev.opennebula.org/issues/3594

 --
 Carlos Martín, MSc
 Project Engineer
 OpenNebula - Flexible Enterprise Cloud Made Simple
 www.OpenNebula.org  |
 cmar...@opennebula.org  | @OpenNebula
 

 On Thu, Feb 12, 2015 at 12:08 PM, RubEn DIez LAzaro >>> > wrote:

  HI:

  The distro is Scientific Linux release 6.4 (Carbon) and ONE is
  installed from repo (it seems be the repo for CentOS 6)

  [root@cloud yum.repos.d]# cat opennebula.repo
  [opennebula]
  name=opennebula
  baseurl=http://downloads.opennebula.org/repo/4.8/CentOS/6/x86_64
  enabled=1
  gpgcheck=0


  The installed (from standard repos) version of libxmlrpc-c is
 1.16.24:

  # yum info xmlrpc-c
  [.]
  Installed Packages
  Name: xmlrpc-c
  Arch: x86_64
  Version : 1.16.24
  Release : 1209.1840.el6
  Size: 263 k
  Repo: installed
  From repo   : sl
  Summary : A lightweight RPC library based on XML and HTTP
  URL : http://xmlrpc-c.sourceforge.net/
  License : BSD and MIT
  Description : XML-RPC is a quick-and-easy way to make procedure
  calls over the
  : Internet. It converts the procedure call into XML
  document, sends
  : it to a remote server using HTTP, and gets back the
  response as
  : XML.
  :
  : This library provides a modular implementation of
  XML-RPC for C.

  but this is no matter since you claims that ONE is statically
  linked What version of xmlrpc-c is linked to the ONE from the
  showed repo??

  We get a source path for 1.33.14 and we build a possible (yet
  untested, done by hand using patch we have for 1.33.14) patch for
  1.16.24 Perhaps we can send you these 

Re: [one-users] "Official" Debian packages

[Jaime Melis]

Hello Alberto,

yes, of course. But due to resources we can only try and help out people
from the community like yourself or Daniel who want to collaborate in
creating these packages. We can assist and try to change this around in the
codebase to make things easier for package maintainers.

On Tue, Feb 17, 2015 at 10:14 AM, Alberto Zuin - Liste  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Hi Jamie and Daniel,
> I perfectly understand the problems with Debian official packaging
> guidelines.
> I asked this, because at the moment I'm collaborating with Devuan, an
> upcoming Debian fork which is aimed to not have systemd mandatory.
> Could be interesting for you, in the near future, to have official
> packages for this distro?
> Cheers,
> Alberto
>
>
> Il 17/02/2015 8:53 am, Jaime Melis ha scritto:
> > Hi Alberto,
> >
> > I can confirm what Daniel said. We have no current plans of
> > updating the offical Debian package of OpenNebula. Debian packaing
> > guidelines are very strict and as Daniel mentioned it's a very big
> > job.
> >
> > Daniel, I apologize, but somehow I was not aware of #3129. I will
> > update the ticket now.
> >
> > regards, Jaime
> >
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG/MacGPG2 v2.0.22 (Darwin)
>
> iQIcBAEBAgAGBQJU4wZfAAoJEAzproFXfBTIVTMP/ikHyyCGKeyZtEIWRLZXaGi8
> tlve4syO0xqhRCJz6vHjodaPjFoBPGFf33uoJfJUj9RurMIaxuL6ry6bAc3cSil0
> 2MEDcOlbM2q6J778BHzLUN5viFJ0lx+bTElD75WmEO0MYjV0dhxnW/h7gw5R4Laa
> DXs6qSuIrcjlxLAz3+C7PiRuo8E7cxNA59x9/20WbLMEwcTeF8jpGbK70LZbxehv
> ZKU7RteWx+vo1MQ+9VZTQpLAvYqqO6Cv03SFTnQlIdEZZqNJTtRdo97lR4XSHXQO
> 9E+KW9ZZ4Jw8oR/dsPzLmDClz9STeqGAFhZsZXcDoPrrxAJv7kWNvcRD/QiXWm6E
> MHNeaIoF1ILy4Hzcat3jjYDHOvCeqBIwE1VsG7DdueuYzRgVFREM0rhKvjgWxD7C
> uFnC3gesNyILGMHEcfBjozIjCkjDxmRSKC3dq+SmsGdmIO6A7W9DHSPUL91hSfq3
> P0Enn0odAGfw9G59OwSjsVnb/lFS85lL5JK2pxKnWKnr8kBazUZ/YGr7+yz69D/w
> cNvrquOTGi6cdJxjc3tgCUwxwKAY2KFEDLSd/1pW1KYak7Yj3jqfyqvWgy2EXIWO
> bTURrWb4ihfp8rqdRnCRrNbwZMzqjTUfOSQekenRu8gIg4kQosORQf7DxrpLtLwV
> +C9nghRVk7QD8ROaIi3N
> =5AYH
> -END PGP SIGNATURE-
> ___
> 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
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] "Official" Debian packages

[Daniel Dehennin]

Jaime Melis  writes:

> Hi Alberto,
>
> I can confirm what Daniel said. We have no current plans of updating the
> offical Debian package of OpenNebula. Debian packaing guidelines are very
> strict and as Daniel mentioned it's a very big job.
>
> Daniel, I apologize, but somehow I was not aware of #3129. I will update
> the ticket now.

Thanks, I have one issue with OpenNebula branches.

I based my work on the 4.10 package[1] to compare the original package
content with mine.

Now, I would like to follow master and derive the packaging based on OpenNebula
version, but I have a lot of conflicts when I merge master into my
packaging branch.

The base idea is to have one packaging branch following OpenNebula
master branch.

On a new release, a “release dedicated” packaging branch is
derived from the master packaging branch to follow the OpenNebula release.

Should I rebase[2] all my branches on master directly and then follow
the OpenNebula releases or is there a path to merge master and one-4.10?


Hmm, writing the question seems to gives my answer, it looks like the
cherry-picking of master commits on the one- branches are the
reasons of the merge conflicts.

Any hints?

Footnotes: 
[1]  http://downloads.opennebula.org/packages/opennebula-4.10.1/

[2]  so changing history

-- 
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF


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

Re: [one-users] "Official" Debian packages

[Alberto Zuin - Liste]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi Jamie and Daniel,
I perfectly understand the problems with Debian official packaging
guidelines.
I asked this, because at the moment I'm collaborating with Devuan, an
upcoming Debian fork which is aimed to not have systemd mandatory.
Could be interesting for you, in the near future, to have official
packages for this distro?
Cheers,
Alberto


Il 17/02/2015 8:53 am, Jaime Melis ha scritto:
> Hi Alberto,
> 
> I can confirm what Daniel said. We have no current plans of
> updating the offical Debian package of OpenNebula. Debian packaing
> guidelines are very strict and as Daniel mentioned it's a very big
> job.
> 
> Daniel, I apologize, but somehow I was not aware of #3129. I will
> update the ticket now.
> 
> regards, Jaime
> 

-BEGIN PGP SIGNATURE-
Version: GnuPG/MacGPG2 v2.0.22 (Darwin)

iQIcBAEBAgAGBQJU4wZfAAoJEAzproFXfBTIVTMP/ikHyyCGKeyZtEIWRLZXaGi8
tlve4syO0xqhRCJz6vHjodaPjFoBPGFf33uoJfJUj9RurMIaxuL6ry6bAc3cSil0
2MEDcOlbM2q6J778BHzLUN5viFJ0lx+bTElD75WmEO0MYjV0dhxnW/h7gw5R4Laa
DXs6qSuIrcjlxLAz3+C7PiRuo8E7cxNA59x9/20WbLMEwcTeF8jpGbK70LZbxehv
ZKU7RteWx+vo1MQ+9VZTQpLAvYqqO6Cv03SFTnQlIdEZZqNJTtRdo97lR4XSHXQO
9E+KW9ZZ4Jw8oR/dsPzLmDClz9STeqGAFhZsZXcDoPrrxAJv7kWNvcRD/QiXWm6E
MHNeaIoF1ILy4Hzcat3jjYDHOvCeqBIwE1VsG7DdueuYzRgVFREM0rhKvjgWxD7C
uFnC3gesNyILGMHEcfBjozIjCkjDxmRSKC3dq+SmsGdmIO6A7W9DHSPUL91hSfq3
P0Enn0odAGfw9G59OwSjsVnb/lFS85lL5JK2pxKnWKnr8kBazUZ/YGr7+yz69D/w
cNvrquOTGi6cdJxjc3tgCUwxwKAY2KFEDLSd/1pW1KYak7Yj3jqfyqvWgy2EXIWO
bTURrWb4ihfp8rqdRnCRrNbwZMzqjTUfOSQekenRu8gIg4kQosORQf7DxrpLtLwV
+C9nghRVk7QD8ROaIi3N
=5AYH
-END PGP SIGNATURE-
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] LVM over iSCSI or NFS for OpenNebula

[ngurjar]

On 2015-02-17 02:58, Jaime Melis wrote:

Hi,
 


- I can create VMs successfully but very very slow performance.


Are you using virtio drivers? I also recommend playing with the
'cache' parameter. How well does it perform compared with I/O
operations in the hypervisor? Is the storage the problem here or the
Virtualization layer?


I am using KVM hypervisor. I also used Chachefilesd but while launching 
vms it takes long time. Also poor writing speed inside the vm.






- Also when I created VM on node1 and try to migrate it other vm it
does not work as logical volume of that VM on node2 is inactive.


have you set up cLVMd? I think for your setup the best approach is:
http://docs.opennebula.org/4.10/administration/storage/fs_lvm_ds.html
[2]

Or something like GFS2.


No I did not configure CLVMd or GFS as it needs fencing device.


Regards
Neelesh Gurjar



cheers,
Jaime 

On Tue, Feb 10, 2015 at 12:08 PM,  wrote:


Hi,
I am setting up OpenNebula on 2 nodes and 1 storage on 1Gb Network.
- installed Nexenta Community Version on Storage and created iSCSI
LUN.
- Access those LUNs on both nodes and created Volume Group on it.
- Configured LVM Block Datastore in OpenNebula.
- I can create VMs successfully but very very slow performance.
- Also when I created VM on node1 and try to migrate it other vm it
does not work as logical volume of that VM on node2 is inactive.

What do you recommend for this type of setup for Shared Storage
LVM, NFS? Please note that I need to use 1GbE copper due to budget
limitations.

Regards
Neelesh Gurjar
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org [1]


--

OpenNebula - Flexible Enterprise Cloud Made Simple

--
Jaime Melis
Senior Infrastructure Architect at OpenNebula Systems (formerly C12G
Labs)
jmelis@opennebula.systems | @OpenNebula
--
Confidentiality Warning: The information contained in this e-mail and
any accompanying documents, unless otherwise expressly indicated, is
confidential and privileged, and is intended solely for the person
and/or entity to whom it is addressed (i.e. those identified in the
"To" and "cc" box). They are the property of OpenNebula.Systems S.L..
Unauthorized distribution, review, use, disclosure, or copying of this
communication, or any part thereof, is strictly prohibited and may be
unlawful. If you have received this e-mail in error, please notify us
immediately by e-mail at abuse@opennebula.systems and delete the
e-mail and attachments and any copy from your system. OpenNebula's
thanks you for your cooperation.

Links:
--
[1] http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
[2] 
http://docs.opennebula.org/4.10/administration/storage/fs_lvm_ds.html

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

Re: [one-users] about firewall

[Jaime Melis]

Hi,

you are right, we don't have this. I just created this in order to document
http://dev.opennebula.org/issues/3602

Answering your specific question:

What is not clear is about the tm driver. An ssh connection is open from
> oned admin server to the hypervisors, to run the clone/cp/etc actions. I
> need to know if the hypervisor will in those actions initiate some SSH
> connection back to the oned admin server? (we are using ssh, shared, and
> lvm drivers). We want to block this king of traffic (ssh to oned admin
> server from the nodes).


The ssh connection to the frontend from the nodes **is** required. It's
used in actions like undeploy or stop.

In any case as you say, creating a reference guide for the connections in
OpenNebula would come in very handy.

cheers,
Jaime

On Fri, Feb 6, 2015 at 11:07 AM, Madko  wrote:

> Hi,
>
> Is there any documentation about the ports and network traffic in use with
> OpenNebula?
>
> To go in production we need to have a firewall between our oned admin
> server and the hypervisors nodes.
> So I need to know if there is any network traffic to be initiated (state
> NEW) from the hypervisor nodes to the oned admin server?
> So far I found the UDP port 4124 for collectd, with metrics comming from
> the hypervisors.
>
> What is not clear is about the tm driver. An ssh connection is open from
> oned admin server to the hypervisors, to run the clone/cp/etc actions. I
> need to know if the hypervisor will in those actions initiate some SSH
> connection back to the oned admin server? (we are using ssh, shared, and
> lvm drivers). We want to block this king of traffic (ssh to oned admin
> server from the nodes).
>
> To sum up, here is what we know for sure:
> oned 4124/udp <= nodes
> oned => 22/tcp nodes
>
> We need to know what traffic and who initiate it. I don't see anything
> about it in the documentation. If anyone has this information that would be
> of great help. Untill then I will try to find it out myself by playing with
> iptables.
>
> Best regards
>
> ___
> 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
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] LVM over iSCSI or NFS for OpenNebula

[Jaime Melis]

Hi,


> - I can create VMs successfully but very very slow performance.
>
Are you using virtio drivers? I also recommend playing with the 'cache'
parameter. How well does it perform compared with I/O operations in the
hypervisor? Is the storage the problem here or the Virtualization layer?

- Also when I created VM on node1 and try to migrate it other vm it does
> not work as logical volume of that VM on node2 is inactive.

have you set up cLVMd? I think for your setup the best approach is:
http://docs.opennebula.org/4.10/administration/storage/fs_lvm_ds.html

Or something like GFS2.

cheers,
Jaime

On Tue, Feb 10, 2015 at 12:08 PM,  wrote:

> Hi,
> I am setting up OpenNebula on 2 nodes and 1 storage on 1Gb Network.
> - installed Nexenta Community Version on Storage and created iSCSI LUN.
> - Access those LUNs on both nodes and created Volume Group on it.
> - Configured LVM Block Datastore in OpenNebula.
> - I can create VMs successfully but very very slow performance.
> - Also when I created VM on node1 and try to migrate it other vm it does
> not work as logical volume of that VM on node2 is inactive.
>
> What do you recommend for this type of setup for Shared Storage LVM, NFS?
> Please note that I need to use 1GbE copper due to budget limitations.
>
> Regards
> Neelesh Gurjar
> ___
> Users mailing list
> Users@lists.opennebula.org
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>



-- 
OpenNebula - Flexible Enterprise Cloud Made Simple
--
Jaime Melis
Senior Infrastructure Architect at OpenNebula Systems (formerly C12G Labs)
jmelis@opennebula.systems | @OpenNebula
--
Confidentiality Warning: The information contained in this e-mail and any
accompanying documents, unless otherwise expressly indicated, is
confidential and privileged, and is intended solely for the person and/or
entity to whom it is addressed (i.e. those identified in the "To" and "cc"
box). They are the property of OpenNebula.Systems S.L.. Unauthorized
distribution, review, use, disclosure, or copying of this communication, or
any part thereof, is strictly prohibited and may be unlawful. If you have
received this e-mail in error, please notify us immediately by e-mail at
abuse@opennebula.systems and delete the e-mail and attachments and any copy
from your system. OpenNebula's thanks you for your cooperation.
___
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org

Re: [one-users] "Official" Debian packages

[Jaime Melis]

Hi Alberto,

I can confirm what Daniel said. We have no current plans of updating the
offical Debian package of OpenNebula. Debian packaing guidelines are very
strict and as Daniel mentioned it's a very big job.

Daniel, I apologize, but somehow I was not aware of #3129. I will update
the ticket now.

regards,
Jaime




On Fri, Feb 13, 2015 at 1:26 PM, Daniel Dehennin <
daniel.dehen...@baby-gnu.org> wrote:

> Daniel Dehennin  writes:
>
>
> [...]
>
> > It's a big work, for now lintian is far from being happy[3]
>
> [...]
>
> > [3]  c.f. attachement
>
> Missing attachement, sorry.
>
> --
> Daniel Dehennin
> Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
> Fingerprint: 3E69 014E 5C23 50E8 9ED6  2AAD CC1E 9E5B 7A6F E2DF
>
>
> P: opennebula source: source-contains-prebuilt-java-object
> src/oca/java/lib/xmlrpc-common-3.1.2.jar
> N:
> N:The source tarball contains a prebuilt Java class file. These are
> often
> N:included by mistake when developers generate a tarball without
> cleaning
> N:the source directory first. If there is no sign this was intended,
> N:consider reporting it as an upstream bug.
> N:
> N:Severity: pedantic, Certainty: possible
> N:
> N:Check: cruft, Type: source
> N:
> P: opennebula source: source-contains-prebuilt-java-object
> src/oca/java/lib/xmlrpc-client-3.1.2.jar
> P: opennebula source: source-contains-prebuilt-java-object
> src/oca/java/lib/ws-commons-util-1.0.2.jar
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/vendor/crypto-js/sha1-min.js
> N:
> N:The source tarball contains a prebuilt (minified) JavaScript object.
> N:They are usually left by mistake when generating the tarball by not
> N:cleaning the source directory first. You may want to report this as
> an
> N:upstream bug, in case there is no sign that this was intended.
> N:
> N:Severity: pedantic, Certainty: possible
> N:
> N:Check: cruft, Type: source
> N:
> E: opennebula source: source-is-missing
> src/sunstone/public/vendor/crypto-js/sha1-min.js
> N:
> N:The source of the following file is missing. Lintian checked a few
> N:possible paths to find the source, and do not find it.
> N:
> N:Please repack your package to include the source or add it to
> N:"debian/missing-sources" directory.
> N:
> N:If this is a false-positive, please report a bug against Lintian.
> N:
> N:Severity: serious, Certainty: possible
> N:
> N:Check: cruft, Type: source
> N:
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/vendor/crypto-js/enc-base64-min.js
> E: opennebula source: source-is-missing
> src/sunstone/public/vendor/crypto-js/enc-base64-min.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/vendor/crypto-js/core-min.js
> E: opennebula source: source-is-missing
> src/sunstone/public/vendor/crypto-js/core-min.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/bower_components/jquery-migrate/jquery-migrate.min.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/bower_components/jgrowl/jquery.jgrowl.min.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/bower_components/flot/excanvas.min.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/vendor/4.0/nouislider/jquery.nouislider.min.js
> E: opennebula source: source-is-missing
> src/sunstone/public/vendor/4.0/nouislider/jquery.nouislider.min.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/bower_components/sizzle/dist/sizzle.min.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/bower_components/no-vnc/include/logo.js mean line
> length is about 16184 characters
> E: opennebula source: source-is-missing
> src/sunstone/public/bower_components/no-vnc/include/logo.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/bower_components/no-vnc/include/keysymdef.js mean line
> length is about 3983 characters
> E: opennebula source: source-is-missing
> src/sunstone/public/bower_components/no-vnc/include/keysymdef.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/bower_components/jquery/dist/jquery.min.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/bower_components/foundation/js/foundation.min.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/bower_components/flot.tooltip/js/jquery.flot.tooltip.min.js
> P: opennebula source: source-contains-prebuilt-javascript-object
> src/sunstone/public/bower_components/flot.tooltip/js/excanvas.min.js
> E: opennebula source: source-is-missing
> src/sunstone/public/bower_components/flot.tooltip/js/excanvas.min.js
> P: opennebula source: source-contains-pre

Re: [one-users] datastore layout question

[ngurjar]

Hi Steve,
Normally If I have to use NFS based shared hosting then I mounted 
/var/lib/one directly on all nodes instead of mounting datastores 
seperately.


Else recently I configured multiple OpenNebula Nodes with local 
/var/lib/one directory added one Node just for backup and sync only 
datastores of all nodes on that backup node. So that I can easily live 
migrate VMs to that backup Node from any node.

It worked well for me. Pros:
1. Speedy managing instances as it uses local storage.
2. Live Migration works
3. Very Low cost compare to Fiber infrastructure
4. No need for separate Network storage as backup node can work as 
OpenNebula Host.


Cons:
1. It cannot be realtime sync but you set cron for every minute
2. Need to monitor syncing.

Regards
Neelesh Gurjar

On 2015-02-16 09:35, Steven Timm wrote:

My one4.8 installation is set up
with NFS-based shared image store #102 and local-based system
datastore #100 instantiated in local disk on each VM host.

Thus far it seems that I am forced to set up
the datastore path as

/var/lib/one/datastores/

So that means I have to NFS export datastore #102
to all VM nodes with exactly that path
(/var/lib/one/datastores/102) and then as long
as the /var/lib/one/datastores path is there on the VM
host the directory /var/lib/one/datastores/100 will
be made when the first VM is launched.

All of this works just fine but it does mean that I
have to be careful every time I reset the cloud to
make sure that the image datastore is created as datastore #102.
If I ever end up changing the number for whatever reason I will
have to change all the mount points all across the cluster.

Has anyone ever figured out a better way to deal with
mounting a shared NFS data store?

Steve Timm


--
Steven C. Timm, Ph.D  (630) 840-8525
t...@fnal.gov  http://home.fnal.gov/~timm/
Office:  Wilson Hall room 804
Fermilab Scientific Computing Division,
Scientific Computing Facilities Quadrant.,
Experimental Computing Facilities Dept.,
Project Lead for Virtual Facility Project.


___
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