<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<div dir="auto">Hi stephane,<br>
<br>
</div>
<div dir="auto">We ran into this issue upon initial install on release day and we ended up creating a bond called eth0(messy i know) inside the autoyast.In the newer versions of caas (you would have to update to latest version of the admin node before the
bootstrap) saltstack actually looks at the grains I believe to set the interface name so you should be ok.<br>
<br>
</div>
<div dir="auto">We have recently also updated from 1g to 10g networking in the cluster but as caas does not like us changing the interface name we simply changed the actually bond binding to 10g nics and updated dhcp with the reservation with the new mac. as
far as caas is concerned we have not changed anything and this has been running fine in production for around a week now. I plan on doing the first update since this change later this week so lets see if it lives.<br>
<br>
</div>
<div dir="auto">Although this upgrade is completely unsupported by suse it seems to work :D.<br>
<br>
<br>
</div>
<div dir="auto">If you like I should be able to send over the section of autoyast dealing with bonding tomorrow?<br>
<br>
</div>
<div dir="auto">This was sent from my phone so please excuse my complete lack of punctuation.<br>
<br>
</div>
<div dir="auto">Cheers,<br>
<br>
</div>
<div dir="auto">Liam<br>
<br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->Sent from BlueMail<!-- tmjah_g_1299e --> <br>
<br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->On 5 Mar 2018, 10:08 pm, at 10:08 pm, Rob de Canha-Knight <rob.decanha-knight@suse.com> wrote:<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Hi Stephane,<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>In general, changing the network interface setup after install is not<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>possible and I believe it is unsupported at this time.<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>If you’ve got a mix of KVM and physical nodes the best thing to do is<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>to download the autoyast generated by the admin node and modify it. You<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>can then serve it up yourself from a normal SLES machine and Apache.<!-- tmjah_g_1299e -->
<br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>That way you can have an autoyast suitable for KVM based VMs and a<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>different autoyast file suitable for the physical hosts with network<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>bonding.<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>I strongly recommend setting up the bond inside of the autoyast file<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>directly. I don’t however have any examples of how to do this.<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>You can then reinstall the worker nodes or the cluster and they’ll get<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>more appropriate installation settings to deal with network bonding.<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>We also recently released some updates to CaaS Platform to remove the<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>hardcoded eth0 references and instead use the default network interface<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>inside all of the salt states/components. In your case this will be<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>bond0 (but only if setup correctly or like that during install).<!-- tmjah_g_1299e -->
<br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>So please make sure that your existing cluster is up to date both admin<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>and worker nodes but also more importantly make sure you’re enabling<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>updates during install for when you reinstall the cluster (this can be<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>set in the autoyast file and is enabled by default in the autoyast I<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>think as long as a registration code was provided to the admin node<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>during installation.<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>You’ll need all the <do_registration> and <reg_code> and<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><install_updates> filled in correctly and enabled.<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Further information on updates to a cluster the process and how to<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>recover from errors can be found at<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><a href="https://wiki.microfocus.com/index.php/SUSE_CaaS_Platform/Cluster_Update">https://wiki.microfocus.com/index.php/SUSE_CaaS_Platform/Cluster_Update</a><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>We have a couple of customers that have achieved bonding network cards<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>with CaaSP. I am adding in Liam to this thread as he was successful in<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>achieving this and he may be able to share some examples or some<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>insights into network bonding. Anything you’re able to share or input<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>to the discussion is much appreciated Liam :)<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>If I’ve said anything that’s incorrect then someone from Engineering<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>will be able to comment (it’s been a while since I’ve looked into the<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>issue of network bonding).<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Kind regards,<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Rob<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>-----<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Rob de Canha-Knight<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>EMEA Platform and Management Technical Strategist<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>SUSE<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>rob.decanha-knight@suse.com<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>(P) +44 (0) 1635 937689<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>(M) +44 (0) 7869 113493<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>(TW) rssfed23<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>I work on GMT time zone<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>----<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>From: <caasp-beta-bounces@lists.suse.com> on behalf of "Le Bihan<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Stéphane (AMUNDI-ITS)" <stephane.lebihan@amundi.com><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Date: Monday, 26 February 2018 at 10:53<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>To: "caasp-beta@lists.suse.com" <caasp-beta@lists.suse.com><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Subject: [caasp-beta] Use another interface after install<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Hello,<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>My admin is installed in KVM, so he use eth0 for kubernetes.<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>I want to add a physical node (baremetal) to kubernetes cluster. But on<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>it, I want to use a bond with two card 10Go.<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>But when I join host baremetal to cluster, deployement want to use<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>eth0.<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>How I can fix interface change just for this host ? I think it’s on<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Saltstack deployement, but I don’t want who I can change it ?<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Any idea ?<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Regards,<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Stéphane Le Bihan<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>SDE/DSI/IPR/SSD/UNX<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>90, Boulevard Pasteur - 75015 Paris<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Web: <a href="http://www.amundi.com">www.amundi.com</a><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Tel: +33 1 76 32 32 08<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Tel Unix Team: +33 1 76 32 02 30<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>@: stephane.lebihan@amundi.com<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>@: sits.unix@amundi.com<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Visit us on:<!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->> <!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --> <br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>______________________________________________________________________<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>This email has been scanned by the Symantec Email Security.cloud<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>service.<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>For more information please visit <a href="http://www.symanteccloud.com">
http://www.symanteccloud.com</a><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>______________________________________________________________________<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->><!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>This e-mail and any files transmitted with it are confidential and may<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>be legally privileged. If you receive it in error or are not the<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>intended recipient you must not copy, distribute or take any action in<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>reliance upon it. Instead, please notify us immediately by telephoning<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>+44 (20) 7482 0077 and delete the material from your systems. Smartodds<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>is a business carried on by Smartodds Limited, a company registered<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>with the Registrar of Companies for England and Wales with number<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>05108548. Registered office: Unit 540 Highgate Studios, 53-79 Highgate<!-- tmjah_g_1299e --><br>
</div>
<div dir="auto"><!-- tmjah_g_1299s -->>Road, London NW5 1TL<!-- tmjah_g_1299e --><br>
</div>
<br clear="both">
______________________________________________________________________<BR>
This email has been scanned by the Symantec Email Security.cloud service.<BR>
For more information please visit http://www.symanteccloud.com<BR>
______________________________________________________________________<BR>
<BR>
This e-mail and any files transmitted with it are confidential and may be legally privileged. If you receive it in error or are not the intended recipient you must not copy, distribute or take any action in reliance upon it. Instead, please notify us immediately by telephoning +44 (20) 7482 0077 and delete the material from your systems. Smartodds is a business carried on by Smartodds Limited, a company registered with the Registrar of Companies for England and Wales with number 05108548. Registered office: Unit 531 Highgate Studios, 53-79 Highgate Road, London NW5 1TL<BR>
</body>
</html>