Re: Increase root disk size in latest cloudstack

[Erik Weber]

The design spec is here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Root+Resize+Support

You can find the Jira ticket with a lot of information here:
https://issues.apache.org/jira/browse/CLOUDSTACK-6181

As far as I can see, you can atleast resize the disk by using the API. UI
tends to lag a bit behind new API functionality, so I would hope for it to
arrive in a later version.

But, after reading through the ticket it seems that root disk resize might
only be supported on KVM, which hypervisor are you using?

-- 
Erik


On Tue, Oct 21, 2014 at 8:31 AM, Asanka sanjaya Herath 
wrote:

> Hi Erik,
> I'm using the master branch. Could you please tell me how can I do that?
>
> Thank you.
>
> On Tue, Oct 21, 2014 at 11:59 AM, Erik Weber  wrote:
>
> > On Tue, Oct 21, 2014 at 7:54 AM, Asanka sanjaya Herath <
> angal...@gmail.com
> > >
> > wrote:
> >
> > > I'm using the latest cloudstack(Cloned from github and built from
> > source).
> > > I need to know whether there is any way to re-size the root disk
> capacity
> > > after creating the instance.(Using UI or using api).
> > >
> > >
> > Which branch did you build?
> >
> > I believe root disk resizing has been there since 4.4, but it might be
> > lacking if you're using managed storage.
> >
> > Mike can probably chime in on the latter
> >
> > --
> > Erik
> >
>
>
>
> --
> Thanks,
> Regards,
> ASH
>

Re: Increase root disk size in latest cloudstack

[Asanka sanjaya Herath]

Hi Erik,
I'm using the master branch. Could you please tell me how can I do that?

Thank you.

On Tue, Oct 21, 2014 at 11:59 AM, Erik Weber  wrote:

> On Tue, Oct 21, 2014 at 7:54 AM, Asanka sanjaya Herath  >
> wrote:
>
> > I'm using the latest cloudstack(Cloned from github and built from
> source).
> > I need to know whether there is any way to re-size the root disk capacity
> > after creating the instance.(Using UI or using api).
> >
> >
> Which branch did you build?
>
> I believe root disk resizing has been there since 4.4, but it might be
> lacking if you're using managed storage.
>
> Mike can probably chime in on the latter
>
> --
> Erik
>



-- 
Thanks,
Regards,
ASH

Re: Increase root disk size in latest cloudstack

[Erik Weber]

On Tue, Oct 21, 2014 at 7:54 AM, Asanka sanjaya Herath 
wrote:

> I'm using the latest cloudstack(Cloned from github and built from source).
> I need to know whether there is any way to re-size the root disk capacity
> after creating the instance.(Using UI or using api).
>
>
Which branch did you build?

I believe root disk resizing has been there since 4.4, but it might be
lacking if you're using managed storage.

Mike can probably chime in on the latter

-- 
Erik

Increase root disk size in latest cloudstack

[Asanka sanjaya Herath]

I'm using the latest cloudstack(Cloned from github and built from source).
I need to know whether there is any way to re-size the root disk capacity
after creating the instance.(Using UI or using api).

-- 
Thanks,
Regards,
ASH

RE: Failed Site-to-Site VPN 4.4.0 - Error due semicolon

[Amin]

Hi David,

Could you please share how did you colleagues resolve this issue, which script 
and what is the code? We facing the same on our labs and that is holding us 
from upgrading to 4.4.

Cheers

-Original Message-
From: David Amorín [mailto:david.amo...@adderglobal.com] 
Sent: Friday, 29 August 2014 4:44 PM
To: users@cloudstack.apache.org
Subject: RE: Failed Site-to-Site VPN 4.4.0 - Error due semicolon

Thanks Erik for your response. My colleagues have resolved this issue in CS 
4.4.0 modifying one script in XenServer, at least we have VPN Site-to-Site 
tunnels with this version.  I hope this issue is resolved with CS 4.4.1

Best

-Mensaje original-
De: Erik Weber [mailto:terbol...@gmail.com] Enviado el: jueves, 28 de agosto de 
2014 22:05
Para: users@cloudstack.apache.org
Asunto: Re: Failed Site-to-Site VPN 4.4.0 - Error due semicolon

On Thu, Aug 28, 2014 at 8:53 PM, David Amorín 
wrote:

> Hi,
> We are having issues to establish VPN Site-to-Site with our VPC based 
> in CS 4.4.0
>
> We see this issue already identified
> https://issues.apache.org/jira/browse/CLOUDSTACK-7124 but it says that 
> only affects the version 4.5.0.
>
> Can somebody confirm if this issue affects also the version 4.4.0?
>

My experience is that 'Affected version(s)' is entered with the version someone 
first experience it in. That doesn't mean it doesn't exist in any other release.

If you have the same error message and have excluded typos etc. it is very 
likely that you experience the same bug.


--
Erik

Re: Do primary and secondary storage must be served by different servers ?

[Tim Mackey]

What that statement means is if you explicitly define a dedicated storage
network (aka for primary storage), then that storage network can't be
pingable from the management network.  This is no different than if you
define a storage management network in XenServer directly.

Where things get a bit more complicated is with Secondary Storage which
uses a VM as a proxy to the storage.  That VM is known as SSVM, and some
details on how to debug it can be found here:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Secondary+storage+troubleshooting

The net of this is that primary and secondary can definitely be on the same
file.  Things can get more complicated if you need different storage for
primary and secondary, or multipath, and for XenServer the CloudStack
storage option you might also want to look into is called PreSetup.

-tim

On Fri, Oct 3, 2014 at 2:44 PM, Yiping Zhang  wrote:

> I need some clarifications regarding primary and secondary storage devices.
>
> From following document,
> http://cloudstack-installation.readthedocs.org/en/latest/hypervisor/xenserver.html
>
> In section "Separate Storage Network for XenServer (Optional)”, it states,
> I quote:
>
> For the separate storage network to work correctly, it must be the only
> interface that can ping the primary storage device’s IP address. For
> example, if eth0 is the management network NIC, ping -I eth0  storage device IP> must fail. In all deployments, secondary storage devices
> must be pingable from the management network NIC or bond. If a secondary
> storage device has been placed on the storage network, it must also be
> pingable via the storage network NIC or bond on the hosts as well.
>
> In my case, since both primary and secondary storage are from the same
> NetApp filer, just two different volumes,  so those two sentences
> highlighted red above can’t possibly be true at the same time !  As it is
> now,  I can ping my filer from storage bond, as well as from management
> bond on xen hypervisor.
>
> Does this mean my primary and secondary storage volumes can not be served
> by the same filer ?
>
> Thanks for your help in advance.
>
> Yiping
>

答复: About ACS with OVM

[Star Guo]

Thanks ! I just still wait for the newer version.

Best Regards,
Star Guo

-邮件原件-
发件人: sebgoa [mailto:run...@gmail.com] 
发送时间: 2014年10月20日 15:47
收件人: users@cloudstack.apache.org
主题: Re: About ACS with OVM

The OVM stuff should have been removed from the UI, I suppose this is what
you are seeing.

However there is work to reintroduce OVM support for OVM 3, but it's not yet
ready.



-sebastien

On Oct 19, 2014, at 5:37 PM, Star Guo  wrote:

> Hello,
> 
> 
> 
>  I found that ACS support OVM as the physical host .However , I can't 
> find any document about ACS+OVM. Could Some one give me some suggestion?
> 
>  Thanks for help.
> 
> 
> 
> Best Regards,
> 
> Star Guo
> 

RE: Initial install issues

[Geoff Higginbottom]

You need to add /client on the end

http://ipaddress:8080/client

Regards

Geoff Higginbottom

D: +44 20 3603 0542 | S: +44 20 3603 0540 | M: +447968161581

geoff.higginbot...@shapeblue.com

-Original Message-
From: Piers [mailto:pi...@rowan.id.au]
Sent: 20 October 2014 11:21
To: users@cloudstack.apache.org
Subject: Re: Initial install issues

On 18/10/14 01:22, scot gabriel wrote:
> Installed on Ubuntu 14.04 TLS
> followed this guide:
> https://joshuarogers.net/installing-cloudstack-43-ubuntu-1404
>
> I'm very new to the product (first time trying to play with it).
> When I try to open http://localhost:8080 it gives me a blank screen
> (nothing) no time out, just a blank screen.
>


Go to the IP address:8080/clients

Cheers

Piers
Find out more about ShapeBlue and our range of CloudStack related services

IaaS Cloud Design & Build
CSForge – rapid IaaS deployment framework
CloudStack Consulting
CloudStack Infrastructure 
Support
CloudStack Bootcamp Training Courses

This email and any attachments to it may be confidential and are intended 
solely for the use of the individual to whom it is addressed. Any views or 
opinions expressed are solely those of the author and do not necessarily 
represent those of Shape Blue Ltd or related companies. If you are not the 
intended recipient of this email, you must neither take any action based upon 
its contents, nor copy or show it to anyone. Please contact the sender if you 
believe you have received this email in error. Shape Blue Ltd is a company 
incorporated in England & Wales. ShapeBlue Services India LLP is a company 
incorporated in India and is operated under license from Shape Blue Ltd. Shape 
Blue Brasil Consultoria Ltda is a company incorporated in Brasil and is 
operated under license from Shape Blue Ltd. ShapeBlue SA Pty Ltd is a company 
registered by The Republic of South Africa and is traded under license from 
Shape Blue Ltd. ShapeBlue is a registered trademark.

Re: Initial install issues

[Piers]

On 18/10/14 01:22, scot gabriel wrote:

Installed on Ubuntu 14.04 TLS
followed this guide:
https://joshuarogers.net/installing-cloudstack-43-ubuntu-1404

I'm very new to the product (first time trying to play with it).
When I try to open http://localhost:8080 it gives me a blank screen
(nothing) no time out, just a blank screen.




Go to the IP address:8080/clients

Cheers

Piers

Re: Primary Storage Allocated issue

[Denis Finko]

Hello

I have tried this and set expunge.interval and expunge.delay to 120 on weekend. 
But it wasn't helpful. Old VMs (not all but some of them) still present in 
VMware environment.
Looks like I am need to create a bug.

Is the any way to correctly remove them from CloudStack?

Just several examples:

mysql> select vm.name,vm.state AS VM_state,v.id as VOLUME_id,v.size,v.state AS 
VOLUME_state,v.removed,d.root_disk_tag,v.chain_info from volumes v, vm_instance 
vm, vm_root_disk_tags d where v.instance_id=vm.id and d.vm_id=vm.id and 
vm.instance_name like 'i-132-1967-VM' \G
*** 1. row ***
 name: Test4UbuntuDesktop14-04
 VM_state: Expunging
VOLUME_id: 2013
 size: 21474836480
 VOLUME_state: Expunged
  removed: 2014-09-29 20:33:12
root_disk_tag: auto
   chain_info: {"diskDeviceBusName":"scsi0:0","diskChain":["[AUTO1] 
i-132-1967-VM/4e34b5f5d1214296a762c633507acfd8.vmdk"]}
1 row in set (0.03 sec)

mysql>


mysql> select vm.name,vm.state AS VM_state,v.id as VOLUME_id,v.size,v.state AS 
VOLUME_state,v.removed,d.root_disk_tag,v.chain_info from volumes v, vm_instance 
vm, vm_root_disk_tags d where v.instance_id=vm.id and d.vm_id=vm.id and 
vm.instance_name like 'i-161-1922-VM' \G
*** 1. row ***
 name: FCtest
 VM_state: Expunging
VOLUME_id: 1970
 size: 42949672960
 VOLUME_state: Expunged
  removed: 2014-09-22 20:33:01
root_disk_tag: auto
   chain_info: {"diskDeviceBusName":"scsi0:0","diskChain":["[AUTO2] 
i-161-1922-VM/ROOT-1922.vmdk"]}
1 row in set (0.02 sec)

mysql>


mysql> select vm.name,vm.state AS VM_state,v.id as VOLUME_id,v.size,v.state AS 
VOLUME_state,v.removed,d.root_disk_tag,v.chain_info from volumes v, vm_instance 
vm, vm_root_disk_tags d where v.instance_id=vm.id and d.vm_id=vm.id and 
vm.instance_name like 'i-2-1630-VM' \G
*** 1. row ***
 name: myserver
 VM_state: Expunging
VOLUME_id: 1676
 size: 10737418240
 VOLUME_state: Expunged
  removed: 2014-08-14 11:37:24
root_disk_tag: sata
   chain_info: {"diskDeviceBusName":"scsi0:0","diskChain":["[SATA1] 
i-2-1630-VM/ROOT-1630.vmdk"]}
1 row in set (0.03 sec)

mysql>


On 10/17/2014 03:11 PM, GopalaKrishnan wrote:
> Hi Denis,
>
> Try to reduce expunge interval values to 120 and expunge delay. When you 
> delete VMs or disk, etc., CloudStack will keep its details in the database 
> and disks on the primary storage for 24 hours.
>
> You can shorten this period to expunge 120 seconds.
>
> expunge.interval = 120
> expunge.delay=120
>
> Restart cloudstack once these changes completed.
>
> Thank You.
> Gopalakrishnan.S
> Cloud Consultant - Fogpanel.
>
>
>
> - Original Message - From: "Denis Finko" 
> To: ; 
> Sent: Friday, October 17, 2014 5:21 PM
> Subject: Re: Primary Storage Allocated issue
>
>
>> GopalaKrishnan, I am appreciate you for quick reply!
>>
>> But unfortunately "expunge.interval" is not helpful. I have several time 
>> updated it recently and it wasn't removed old VMs from VMware.
>>
>> Currently I have:
>> expunge.interval = 86400
>>
>>> There is no need to push manually to remove expunged volumes.
>> Yes, I am agree with you that it's supposed to be. But unfortunately I still 
>> have a lot of volumes in 'Expunged' state and don't know how correctly 
>> remove them from CloudStack side. It looks like a bug in CloudStack.
>>
>> On 10/17/2014 01:35 PM, GopalaKrishnan wrote:
>>> Hi Denis,
>>>
>>> I think, it should be calculated disk size also from 'Expunged' volumes. 
>>> Try to update "expunge.interval" in cloudstack global settings.
>>>
>>> There is no need to push manually to remove expunged volumes.
>>>
>>> Thank You.
>>> Gopalakrishnan.S
>>> Cloud Consultant.
>>> - Original Message - From: "Denis Finko" 
>>> To: ; 
>>> Sent: Friday, October 17, 2014 1:47 PM
>>> Subject: Primary Storage Allocated issue
>>>
>>>
 Hello CloudStack community,

 Could you please take a look to following issue. The similar was described 
 it that topic 
 http://comments.gmane.org/gmane.comp.apache.cloudstack.user/13848 but 
 looks like wasn't resolved.

 In my environment I have:
 CloudStack v. 4.2.1
 VMware v. 5.1

 Recently I have found that CloudStack UI provide following information for 
 SATA storage:
 Disk Total   5.00 TB
 Disk Allocated7.26 TB

 I have looked to VMware side and found absolutely different data:
 Capacity:5.00 TB
 Provisioned Space:4.27 TB

 As you can see CloudStack show allocated disk space on 3 TB more.

 My Global Settings that could be helpful for investigation:
 storage.overprovisioning.factor = 4
 storage.cleanup.enabled = true
 storage.cleanup.interval = 86400
 storage.stats.interval = 6
 capacity.check.period = 6
 expunge.delay=60
 expunge.i

Re: firewall problems and proxy problems

[Marc Leeman]

> I cleared the database and re-did the installation and all seems to be

> > working now.
> > ​
> > Thanks for the help.
> >
> > It seems that something must have been off during the initial install.
>
> Hi Marc, I was at the guy at the booth :)
>

Yeah, thank you; you were very patient. Thank you for helping me out in
Cloudstack; it was pretty new to me :-)


> In my angst to get things working I probably messed up the installed when
> upgrading rather quickly to 4.3.
>
> In any case, glad it's working now, please confirm that you can launch
> instances.
>

Truth be said, the config I am running now is probably not what I was
initially looking but I thought go for the out-of-the-box installation and
take it from there.

I have assigned the internal addresses to be a range of the external
network, but I noticed that though I see the connections from the VMs
coming from the correct IP (when e.g. ssh-ing to an external server); but I
cannot connect back (ingress rules are very strict).

Is there any resource you'd recommend to convert the basic guest network to
a configuration where all the VMs are exposed to the network as if they
were machines sitting on that network?

One thing I've also noticed when deploying test software on the cloud is
that I cannot use DHCP:

The machines are installed by default with a static IP (software needs to
be predictable and on the network). When changing over the static IP to a
DHCP address; I see that the system gets a DHCP address that seems (need to
verify this, but I would need to check the DHCP server on the switch to
which I do not have access atm) to come from the network. However the
system is muted on the network.

Only when I set the IP to the IP it got assigned by cloudstack can I access
the network.


> I have kept track of your bugs for debian packaging and we will try to
> address those.
>
>

RE: Cloudstack 4.3.0 UI impossible login problem : browsers hang

[Vincent Jean-François]

The three failed. We had to install a third one.

Regards
JF

-Message d'origine-
De : Ian Duffy [mailto:i...@ianduffy.ie]
Envoyé : lundi 20 octobre 2014 10:17
À : users@cloudstack.apache.org
Objet : Re: Cloudstack 4.3.0 UI impossible login problem : browsers hang

Hi Jean-Francois,

What browser are you experiencing this issue with?

Can you try using firefox, it is the primary one the UI team use for testing.

Thanks,
Ian

On 17 October 2014 08:51, Vincent Jean-François < 
jean-francois.vinc...@worldline.com> wrote:

>
> Hello,
>
> Configuration : Cloudstack 4.3.0. with two management servers (named 1
> and
> 2) behind a LVS with a configured charge of 100/1 for server1/server2
> (direct routing)
>
> Since two days, we have a login problem on server 1. The login pages
> load correctly. But after typing the correct password (local or LDAP
> one) the browser hangs.
> The first occurrence, two days ago. We restart the management server
> and the problem went away. Today, we cannot anymore use the server 1
> and we have to user the server 2.
> Both servers are to our knowledge identical. And no change neither
> have been done on the infrastructure configuration.
>
> Is anybody here has experienced a such problem or have any clue ?
>
> The server ran for many weeks without any outage like this until now.
>
> apilog.log when we have recurring events :
> 2014-10-17 09:05:44,446 INFO  [a.c.c.a.ApiServer]
> (http-6443-exec-442:ctx-8a23b456)  10.26.238.65 -- GET
> command=listCapabilities&response=json&sessionkey=null&_=1413529544423
> 401 unable to verify user credentials But we have also the same INFO
> message on the working server.
>
> Catalina.out :
>
> 2014-10-17 09:42:22,888 DEBUG [c.c.a.ApiServlet]
> (http-6443-exec-467:ctx-86fe168f) ===START===  10.26.238.65 -- POST
> 2014-10-17 09:42:22,891 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-467:ctx-86fe168f) Attempting to log in user: jf in
> domain 1
> 2014-10-17 09:42:22,892 DEBUG [c.c.s.a.SHA256SaltedUserAuthenticator]
> (http-6443-exec-467:ctx-86fe168f) Retrieving user: jf
> 2014-10-17 09:42:22,900 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-467:ctx-86fe168f) User: jf in domain 1 has
> successfully logged in
>
> But browser's stucked...
>
>
> Thank you
>
>
> Jean-Francois
>
>
> Ce message et les pièces jointes sont confidentiels et réservés à
> l'usage exclusif de ses destinataires. Il peut également être protégé
> par le secret professionnel. Si vous recevez ce message par erreur,
> merci d'en avertir immédiatement l'expéditeur et de le détruire.
> L'intégrité du message ne pouvant être assurée sur Internet, la
> responsabilité de Worldline ne pourra être recherchée quant au contenu
> de ce message. Bien que les meilleurs efforts soient faits pour
> maintenir cette transmission exempte de tout virus, l'expéditeur ne
> donne aucune garantie à cet égard et sa responsabilité ne saurait être
> recherchée pour tout dommage résultant d'un virus transmis.
>
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive
> this e-mail in error, please notify the sender immediately and destroy
> it. As its integrity cannot be secured on the Internet, the Worldline
> liability cannot be triggered for the message content. Although the
> sender endeavours to maintain a computer virus-free network, the
> sender does not warrant that this transmission is virus-free and will
> not be liable for any damages resulting from any virus transmitted.
>


Ce message et les pièces jointes sont confidentiels et réservés à l'usage 
exclusif de ses destinataires. Il peut également être protégé par le secret 
professionnel. Si vous recevez ce message par erreur, merci d'en avertir 
immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant 
être assurée sur Internet, la responsabilité de Worldline ne pourra être 
recherchée quant au contenu de ce message. Bien que les meilleurs efforts 
soient faits pour maintenir cette transmission exempte de tout virus, 
l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne 
saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Worldline liability cannot be triggered for the 
message content. Although the sender endeavours to maintain a computer 
virus-free network, the sender does not warrant that this transmission is 
virus-free and will not be liable for any damages resulting from any virus 
transmitted.

Re: Cloudstack 4.3.0 UI impossible login problem : browsers hang

[Ian Duffy]

Hi Jean-Francois,

What browser are you experiencing this issue with?

Can you try using firefox, it is the primary one the UI team use for
testing.

Thanks,
Ian

On 17 October 2014 08:51, Vincent Jean-François <
jean-francois.vinc...@worldline.com> wrote:

>
> Hello,
>
> Configuration : Cloudstack 4.3.0. with two management servers (named 1 and
> 2) behind a LVS with a configured charge of 100/1 for server1/server2
> (direct routing)
>
> Since two days, we have a login problem on server 1. The login pages load
> correctly. But after typing the correct password (local or LDAP one) the
> browser hangs.
> The first occurrence, two days ago. We restart the management server and
> the problem went away. Today, we cannot anymore use the server 1 and we
> have to user the server 2.
> Both servers are to our knowledge identical. And no change neither have
> been done on the infrastructure configuration.
>
> Is anybody here has experienced a such problem or have any clue ?
>
> The server ran for many weeks without any outage like this until now.
>
> apilog.log when we have recurring events :
> 2014-10-17 09:05:44,446 INFO  [a.c.c.a.ApiServer]
> (http-6443-exec-442:ctx-8a23b456)  10.26.238.65 -- GET
> command=listCapabilities&response=json&sessionkey=null&_=1413529544423 401
> unable to verify user credentials
> But we have also the same INFO message on the working server.
>
> Catalina.out :
>
> 2014-10-17 09:42:22,888 DEBUG [c.c.a.ApiServlet]
> (http-6443-exec-467:ctx-86fe168f) ===START===  10.26.238.65 -- POST
> 2014-10-17 09:42:22,891 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-467:ctx-86fe168f) Attempting to log in user: jf in domain 1
> 2014-10-17 09:42:22,892 DEBUG [c.c.s.a.SHA256SaltedUserAuthenticator]
> (http-6443-exec-467:ctx-86fe168f) Retrieving user: jf
> 2014-10-17 09:42:22,900 DEBUG [c.c.u.AccountManagerImpl]
> (http-6443-exec-467:ctx-86fe168f) User: jf in domain 1 has successfully
> logged in
>
> But browser's stucked...
>
>
> Thank you
>
>
> Jean-Francois
>
>
> Ce message et les pièces jointes sont confidentiels et réservés à l'usage
> exclusif de ses destinataires. Il peut également être protégé par le secret
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir
> immédiatement l'expéditeur et de le détruire. L'intégrité du message ne
> pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra
> être recherchée quant au contenu de ce message. Bien que les meilleurs
> efforts soient faits pour maintenir cette transmission exempte de tout
> virus, l'expéditeur ne donne aucune garantie à cet égard et sa
> responsabilité ne saurait être recherchée pour tout dommage résultant d'un
> virus transmis.
>
> This e-mail and the documents attached are confidential and intended
> solely for the addressee; it may also be privileged. If you receive this
> e-mail in error, please notify the sender immediately and destroy it. As
> its integrity cannot be secured on the Internet, the Worldline liability
> cannot be triggered for the message content. Although the sender endeavours
> to maintain a computer virus-free network, the sender does not warrant that
> this transmission is virus-free and will not be liable for any damages
> resulting from any virus transmitted.
>

Re: About ACS with OVM

[sebgoa]

The OVM stuff should have been removed from the UI, I suppose this is what you 
are seeing.

However there is work to reintroduce OVM support for OVM 3, but it's not yet 
ready.



-sebastien

On Oct 19, 2014, at 5:37 PM, Star Guo  wrote:

> Hello, 
> 
> 
> 
>  I found that ACS support OVM as the physical host .However , I can't find
> any document about ACS+OVM. Could Some one give me some suggestion?
> 
>  Thanks for help.
> 
> 
> 
> Best Regards,
> 
> Star Guo
>