<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN'>
<html><head><meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<style>BODY{font:10pt Tahoma,Verdana,sans-serif} .MsoNormal{line-height:120%;margin:0}</style></head><body>
Hi Jay,<br><br>I am using a Gelera master/master setup with Pacemaker providing an floating IP.<br><br>Best regards,<br><br>Tristan van Bokkem<br>Datacenter Operations<br><br>Contact:<br>E-mail Personal: <a href="mailto:tristanvanbokkem@i3d.net">tristanvanbokkem@i3d.net</a><br>E-mail Support: <a href="mailto:info@i3d.net">info@i3d.net</a><br>E-mail NOC: <a href="mailto:noc@i3d.net">noc@i3d.net</a><br>Website: <a href="http://www.i3d.net" target="_blank">http://www.i3d.net</a> Office:<br>Interactive 3D B.V.<br>Meent 93b<br>3011 JG Rotterdam<br>The Netherlands<br><br>Visit www.smartdc.net – SmartDC is our in-house 36,000 sq. ft. datacenter in Rotterdam, The Netherlands. High density hosting – multiple fiber carriers in-house – Level3 PoP.<br><br>Interactive 3D (i3D.net) is a company registered in The Netherlands at Meent 93b, Rotterdam. Registration #: 14074337 - VAT # NL 8202.63.886.B01. Interactive 3D (i3D.net) is CDSA certified on content protection and security. We are ranked in the Deloitte Technology Fast 50 as one of the fastest growing technology companies.<br><blockquote style="padding-left: 5px; margin-left: 5px; border-left: #0000ff 2px solid; margin-right: 0px"><hr><b>From:</b> Jay Pipes [mailto:jaypipes@gmail.com]<br><b>To:</b> openstack@lists.launchpad.net<br><b>Sent:</b> Mon, 27 Feb 2012 21:40:21 +0100<br><b>Subject:</b> Re: [Openstack] Howto Nova setup with HA?<br><br>On 02/27/2012 08:06 AM, i3D.net - Tristan van Bokkem wrote:<br>
> MySQL DB<br>
> * multi-master configuration with pacemaker providing an floating IP. <-<br>
> seems to work.<br>
<br>
The term "multi-master" in the MySQL world typically means something <br>
very specific: you are running multiple master nodes, all in an active <br>
setup using something like MMM, MySQL Cluster or Galera Cluster. I don't <br>
think this is what you are referring to above. Use of pacemaker is <br>
typically an active/passive setup, where Pacemaker can be used to <br>
redirect requests from a failed active master to the passive master node <br>
that is in standby mode (basically, DRBD is used to replicate the InnoDB <br>
and binary logs from the active master to the passive node).<br>
<br>
So, I would avoid using the term "multi-master" unless you are <br>
specifically talking about an active-active setup, but maybe that's just <br>
me being picky ;)<br>
<br>
> Glance<br>
> * Run on multiple servers <-- how do they get synced?<br>
<br>
For the Glance registry, you can set up a passive glance-registry node <br>
that has connection information to your main HA-setup MySQL database <br>
instance.<br>
<br>
You can do a number of things for the image storage side of things (the <br>
Glance API servers, not the Glance registry). You could set Glance to <br>
use a distributed storage backend (like Swift or RADOS) and let that <br>
distributed backend provide high availability.<br>
<br>
Alternately, for smaller setups, you could do like we are doing in the <br>
TryStack project and use the filesystem storage backend in Glance and <br>
have Pacemaker monitor a passive Glance API node with a simple rsync <br>
script that runs on a periodic interval that syncs the image data.<br>
<br>
> Compute servers<br>
> * Each run their own copy of nova-api (only instances running on the<br>
> node use this)<br>
<br>
No. Compute nodes run nova-compute, not nova-api.<br>
<br>
> * nova-network (multi-host configuration) with private network <-- Needs<br>
> its own discussion I guess.<br>
><br>
> Keystone<br>
> * How about keystone, same as glance I guess?<br>
<br>
Similar to glance-registry.<br>
<br>
Cheers,<br>
-jay<br>
<br>
> Best regards,<br>
><br>
> Tristan van Bokkem<br>
> Datacenter Operations<br>
><br>
> Contact:<br>
> E-mail Personal: <a href="mailto:tristanvanbokkem@i3d.net">tristanvanbokkem@i3d.net</a> <mailto:<a href="mailto:tristanvanbokkem@i3d.net">tristanvanbokkem@i3d.net</a>><br>
> E-mail Support: <a href="mailto:info@i3d.net">info@i3d.net</a> <mailto:<a href="mailto:info@i3d.net">info@i3d.net</a>><br>
> E-mail NOC: <a href="mailto:noc@i3d.net">noc@i3d.net</a> <mailto:<a href="mailto:noc@i3d.net">noc@i3d.net</a>><br>
> Website: <a href="http://www.i3d.net" target="_blank">http://www.i3d.net</a> Office:<br>
> Interactive 3D B.V.<br>
> Meent 93b<br>
> 3011 JG Rotterdam<br>
> The Netherlands<br>
><br>
> Visit www.smartdc.net – SmartDC is our in-house 36,000 sq. ft.<br>
> datacenter in Rotterdam, The Netherlands. High density hosting –<br>
> multiple fiber carriers in-house – Level3 PoP.<br>
><br>
> Interactive 3D (i3D.net) is a company registered in The Netherlands at<br>
> Meent 93b, Rotterdam. Registration #: 14074337 - VAT # NL<br>
> 8202.63.886.B01. Interactive 3D (i3D.net) is CDSA certified on content<br>
> protection and security. We are ranked in the Deloitte Technology Fast<br>
> 50 as one of the fastest growing technology companies.<br>
><br>
> ------------------------------------------------------------------------<br>
> *From:* Dan Wendlandt [mailto:<a href="mailto:dan@nicira.com">dan@nicira.com</a>]<br>
> *To:* Ghe Rivero [mailto:<a href="mailto:ghe.rivero@stackops.com">ghe.rivero@stackops.com</a>]<br>
> *Cc:* <a href="mailto:netstack@lists.launchpad.net">netstack@lists.launchpad.net</a>, <a href="mailto:darren.birkett@gmail.com">darren.birkett@gmail.com</a>,<br>
> <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> *Sent:* Tue, 21 Feb 2012 18:13:55 +0100<br>
> *Subject:* Re: [Openstack] Howto Nova setup with HA?<br>
><br>
><br>
><br>
> 2012/2/21 Ghe Rivero <<a href="mailto:ghe.rivero@stackops.com">ghe.rivero@stackops.com</a><br>
> <mailto:<a href="mailto:ghe.rivero@stackops.com">ghe.rivero@stackops.com</a>>><br>
><br>
> BigSwitch and Nicira have created different blueprints in<br>
> quantum to add their plugins for essex-4 about ten days ago,<br>
> Cisco already have it included almost from the beginning. No<br>
> news of them for the moment, but i really hope that both of them<br>
> make it in time!<br>
> Ghe Rivero<br>
><br>
> <a href="https://blueprints.launchpad.net/quantum/+spec/quantum-nvp-plugin" target="_blank">https://blueprints.launchpad.net/quantum/+spec/quantum-nvp-plugin</a><br>
> <a href="https://blueprints.launchpad.net/quantum/+spec/quantum-bigswitch-plugin" target="_blank">https://blueprints.launchpad.net/quantum/+spec/quantum-bigswitch-plugin</a><br>
><br>
><br>
> To be clear, there are several more existing and planned plugins for<br>
> Quantum, even beyond the three you mention. Each plugin will make<br>
> its own trade-offs in terms of HA for control plane and data plane<br>
> components. I'm planning on organizing a talk at the Folsom<br>
> summit/conference where people have a chance to talk about their<br>
> plugins. No need for a flame war here :)<br>
><br>
> One other point of confusion that I'd like to address is that there<br>
> is NO requirement that a plugin be merged into the main Quantum repo<br>
> for it to be a "valid" plugin. I know of several plugins that are<br>
> used despite not being merged in (in fact, at the summit, we're<br>
> going to discuss if ANY plugins should remain in the main repo...<br>
> this is likely a larger decision that should be made consistently<br>
> across all openstack projects).<br>
><br>
> Dan<br>
><br>
><br>
><br>
> 2012/2/21 Diego Parrilla Santamaría<br>
> <<a href="mailto:diego.parrilla.santamaria@gmail.com">diego.parrilla.santamaria@gmail.com</a><br>
> <mailto:<a href="mailto:diego.parrilla.santamaria@gmail.com">diego.parrilla.santamaria@gmail.com</a>>><br>
><br>
> This is the kind of flame war I love... ;-)<br>
><br>
> if you think the HA challenges in Openstack Nova are at<br>
> MySQL and Rabbit level, you are not putting the focus on the<br>
> right components. The biggest HA (and scalability)<br>
> challenges in Nova are in the networking side. There are a<br>
> lot of companies tackling the networking challenges of Nova<br>
> (BigSwitch, Nicira, Cisco, etc...), and I would like to see<br>
> how they evolve in the future and how they will address this<br>
> problem. Right now, only promises.<br>
><br>
> Fight!<br>
> --<br>
> Diego Parrilla<br>
> <<a href="http://www.stackops.com/" target="_blank">http://www.stackops.com/</a>>*CEO*<br>
> **www.stackops.com* <<a href="http://www.stackops.com/" target="_blank">http://www.stackops.com/</a>> |<br>
> *<a href="mailto:diego.parrilla@stackops.com">diego.parrilla@stackops.com</a><br>
> <mailto:<a href="mailto:diego.parrilla@stackops.com">diego.parrilla@stackops.com</a>>****| +34 649 94 43 29<br>
> <tel:%2B34%20649%2094%2043%2029> | skype:diegoparrilla*<br>
> * <<a href="http://www.stackops.com/" target="_blank">http://www.stackops.com/</a>><br>
> **<br>
><br>
><br>
><br>
> On Tue, Feb 21, 2012 at 1:04 PM, i3D.net - Tristan van<br>
> Bokkem <<a href="mailto:tristanvanbokkem@i3d.nl">tristanvanbokkem@i3d.nl</a><br>
> <mailto:<a href="mailto:tristanvanbokkem@i3d.nl">tristanvanbokkem@i3d.nl</a>>> wrote:<br>
><br>
> __<br>
> Hi Darren,<br>
><br>
> No, I am not looking at a performance increasment at<br>
> this moment. Just trying to make the different<br>
> components Nova is build on redundant. Of course a<br>
> master/master setup of mysql / rabbitmq with a floating<br>
> IP will probably work but it bugs me that Nova is not<br>
> really build with flexibility of it components in mind.<br>
><br>
> I understand it is impossible to cover every scenario<br>
> and you can make things redundant into the infinitive<br>
> but why doesn't have Nova any of this build in? Why do I<br>
> need to setup a Virtual IP/floating IP where Nova simple<br>
> could accept multiple locations and failover if the<br>
> first location fails. Or even round-robin to distribute<br>
> the load. All I am doing now is yet add another<br>
> component that can possibly fail as well.<br>
><br>
><br>
> Best regards,<br>
><br>
> Tristan van Bokkem<br>
> Datacenter Operations<br>
><br>
> Contact:<br>
> E-mail Personal: <a href="mailto:tristanvanbokkem@i3d.net">tristanvanbokkem@i3d.net</a><br>
> <mailto:<a href="mailto:tristanvanbokkem@i3d.net">tristanvanbokkem@i3d.net</a>><br>
> E-mail Support: <a href="mailto:info@i3d.net">info@i3d.net</a> <mailto:<a href="mailto:info@i3d.net">info@i3d.net</a>><br>
> E-mail NOC: <a href="mailto:noc@i3d.net">noc@i3d.net</a> <mailto:<a href="mailto:noc@i3d.net">noc@i3d.net</a>><br>
> Website: <a href="http://www.i3d.net" target="_blank">http://www.i3d.net</a> Office:<br>
> Interactive 3D B.V.<br>
> Meent 93b<br>
> 3011 JG Rotterdam<br>
> The Netherlands<br>
><br>
> Visit www.smartdc.net <<a href="http://www.smartdc.net" target="_blank">http://www.smartdc.net</a>> – SmartDC<br>
> is our in-house 36,000 sq. ft. datacenter in Rotterdam,<br>
> The Netherlands. High density hosting – multiple fiber<br>
> carriers in-house – Level3 PoP.<br>
><br>
> Interactive 3D (i3D.net) is a company registered in The<br>
> Netherlands at Meent 93b, Rotterdam. Registration #:<br>
> 14074337 - VAT # NL 8202.63.886 <tel:8202.63.886>.B01.<br>
> Interactive 3D (i3D.net) is CDSA certified on content<br>
> protection and security. We are ranked in the Deloitte<br>
> Technology Fast 50 as one of the fastest growing<br>
> technology companies.<br>
><br>
> ------------------------------------------------------------------------<br>
> *From:* Darren Birkett<br>
> [mailto:<a href="mailto:darren.birkett@gmail.com">darren.birkett@gmail.com</a><br>
> <mailto:<a href="mailto:darren.birkett@gmail.com">darren.birkett@gmail.com</a>>]<br>
> *To:* i3D.net - Tristan van Bokkem<br>
> [mailto:<a href="mailto:tristanvanbokkem@i3d.nl">tristanvanbokkem@i3d.nl</a><br>
> <mailto:<a href="mailto:tristanvanbokkem@i3d.nl">tristanvanbokkem@i3d.nl</a>>]<br>
> *Cc:* Florian Haas [mailto:<a href="mailto:florian@hastexo.com">florian@hastexo.com</a><br>
> <mailto:<a href="mailto:florian@hastexo.com">florian@hastexo.com</a>>],<br>
> <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
> *Sent:* Tue, 21 Feb 2012 12:51:11 +0100<br>
><br>
> *Subject:* Re: [Openstack] Howto Nova setup with HA?<br>
><br>
> Surely it depends what you want out of it? If just<br>
> pure high<br>
> availability (ie ability to continue functioning<br>
> when primary node<br>
> goes down), then doesn't a master/master with<br>
> floating IP fit the<br>
> bill?<br>
><br>
> It sounds like what you're after is better<br>
> performance/throughput<br>
> rather than HA - the ability to write to multiple<br>
> masters at the same<br>
> time. Even here if nova *was* able to hit multiple<br>
> databases, a<br>
> master/master setup isn't going to suit, as each<br>
> write to one master<br>
> still needs to be replicated to the other so<br>
> throughput is going to be<br>
> the same. You'd then need to look to something like<br>
> a native mysql<br>
> cluster to get actual increased throughput.<br>
><br>
> Darren<br>
><br>
> On 21 February 2012 11:34, i3D.net - Tristan van Bokkem<br>
><br>
> <<a href="mailto:tristanvanbokkem@i3d.nl">tristanvanbokkem@i3d.nl</a><br>
> <mailto:<a href="mailto:tristanvanbokkem@i3d.nl">tristanvanbokkem@i3d.nl</a>>> wrote:<br>
> > Ho Florian,<br>
> ><br>
> > I respect your opinion of course and I am not<br>
> here to start a fight. Point<br>
> > is, how I understand it Nova really isn't very<br>
> flexible on High Availability<br>
> > terms. I have now a master/master mysql setup<br>
> with a Virtual IP working just<br>
> > to work around the shortcomings Nova imo<br>
> introduces. This same story goes<br>
> > for RabbitMQ, I need to setup RabbitMQ in HA<br>
> (which is fine) but I need to<br>
> > setup a Virtual IP for it as well just so Nova<br>
> can correctly connect to it.<br>
> > Without the VIP the hole point of setting it up<br>
> in a cluster is useless as<br>
> > you still will point nova to one single host.<br>
> ><br>
> > It shouldn't be that hard to make Nova listen to<br>
> multiple mysql addresses<br>
> > and rabbitmq hosts in a cluster?<br>
> ><br>
> ><br>
> > Best regards,<br>
> ><br>
> > Tristan van Bokkem<br>
> > Datacenter Operations<br>
> ><br>
> > Contact:<br>
> > E-mail Personal: <a href="mailto:tristanvanbokkem@i3d.net">tristanvanbokkem@i3d.net</a><br>
> <mailto:<a href="mailto:tristanvanbokkem@i3d.net">tristanvanbokkem@i3d.net</a>><br>
> > E-mail Support: <a href="mailto:info@i3d.net">info@i3d.net</a> <mailto:<a href="mailto:info@i3d.net">info@i3d.net</a>><br>
> > E-mail NOC: <a href="mailto:noc@i3d.net">noc@i3d.net</a> <mailto:<a href="mailto:noc@i3d.net">noc@i3d.net</a>><br>
> > Website: <a href="http://www.i3d.net" target="_blank">http://www.i3d.net</a> Office:<br>
> > Interactive 3D B.V.<br>
> > Meent 93b<br>
> > 3011 JG Rotterdam<br>
> > The Netherlands<br>
> ><br>
> > Visit www.smartdc.net <<a href="http://www.smartdc.net" target="_blank">http://www.smartdc.net</a>> –<br>
> SmartDC is our in-house 36,000 sq. ft. datacenter in<br>
> > Rotterdam, The Netherlands. High density hosting<br>
> – multiple fiber carriers<br>
> > in-house – Level3 PoP.<br>
> ><br>
> > Interactive 3D (i3D.net) is a company registered<br>
> in The Netherlands at Meent<br>
> > 93b, Rotterdam. Registration #: 14074337 - VAT #<br>
> NL 8202.63.886 <tel:8202.63.886>.B01.<br>
> > Interactive 3D (i3D.net) is CDSA certified on<br>
> content protection and<br>
> > security. We are ranked in the Deloitte<br>
> Technology Fast 50 as one of the<br>
> > fastest growing technology companies.<br>
> ><br>
> > ________________________________<br>
> > From: Florian Haas [mailto:<a href="mailto:florian@hastexo.com">florian@hastexo.com</a><br>
> <mailto:<a href="mailto:florian@hastexo.com">florian@hastexo.com</a>>]<br>
> > To: <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
> > Sent: Fri, 17 Feb 2012 13:32:51 +0100<br>
> ><br>
> > Subject: Re: [Openstack] Howto Nova setup with HA?<br>
> ><br>
> > On Thu, Feb 16, 2012 at 3:28 PM, i3D.net -<br>
> Tristan van Bokkem<br>
> > <<a href="mailto:tristanvanbokkem@i3d.nl">tristanvanbokkem@i3d.nl</a><br>
> <mailto:<a href="mailto:tristanvanbokkem@i3d.nl">tristanvanbokkem@i3d.nl</a>>> wrote:<br>
> >> Hi Tom,<br>
> >><br>
> >> Thank you very much for sharing your knowledge,<br>
> this will help not only<br>
> >> me!<br>
> >> As I am still working on the MySQL part, you<br>
> mentioned multi-master which<br>
> >> I<br>
> >> have running indeed, but I suppose there still<br>
> will need to be some kind<br>
> >> of<br>
> >> entering point within the cluster. How did you<br>
> managed this?<br>
> ><br>
> > Virtual cluster IP addresses and highly available<br>
> MySQL (either DRBD<br>
> > or MySQL replication based). Pacemaker is very<br>
> well capable of<br>
> > managing this.<br>
> ><br>
> > Of course, since you also quoted<br>
> ><br>
> <a href="http://openlife.cc/blogs/2011/july/ultimate-mysql-high-availability-solution" target="_blank">http://openlife.cc/blogs/2011/july/ultimate-mysql-high-availability-solution</a><br>
> > parts of which I wholeheartedly disagree with (as<br>
> with all of Henrik's<br>
> > Pacemaker bashing, but he's of course entitled to<br>
> his own opinion),<br>
> > then you might run away screaming from anything<br>
> that barely mentions<br>
> > Pacemaker in passing. But in reality[1],<br>
> Pacemaker is an extremely<br>
> > capable HA stack that would be well suited for this.<br>
> ><br>
> > Cheers,<br>
> > Florian<br>
> ><br>
> > [1] To be polite, I should say "in my humble<br>
> opinion," but my opinion<br>
> > on this really isn't humble at all, so I prefer<br>
> being honest over<br>
> > being polite. :)<br>
> ><br>
> > --<br>
> > Need help with High Availability?<br>
> > <a href="http://www.hastexo.com/now" target="_blank">http://www.hastexo.com/now</a><br>
> ><br>
> > _______________________________________________<br>
> > Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>><br>
> > Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
> > Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>><br>
> > More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
> ><br>
> ><br>
> > _______________________________________________<br>
> > Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>><br>
> > Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
> > Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>><br>
> > More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
> ><br>
><br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
> Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
> Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Ghe Rivero<br>
> *OpenStack & Distribution Engineer<br>
> ***www.stackops.com* <<a href="http://www.stackops.com/" target="_blank">http://www.stackops.com/</a>> |<br>
> *<a href="mailto:ghe.rivero@stackops.com">ghe.rivero@stackops.com</a><br>
> <mailto:<a href="mailto:diego.parrilla@stackops.com">diego.parrilla@stackops.com</a>>****| +34 625 63 45 23 |<br>
> skype:ghe.rivero*<br>
> * <<a href="http://www.stackops.com/" target="_blank">http://www.stackops.com/</a>><br>
> *<br>
><br>
> ****<br>
><br>
> *<br>
><br>
> ******************** ADVERTENCIA LEGAL ********************<br>
> Le informamos, como destinatario de este mensaje, que el correo<br>
> electrónico y las comunicaciones por medio de Internet no<br>
> permiten asegurar ni garantizar la confidencialidad de los<br>
> mensajes transmitidos, así como tampoco su integridad o su<br>
> correcta recepción, por lo que STACKOPS TECHNOLOGIES S.L. no<br>
> asume responsabilidad alguna por tales circunstancias. Si no<br>
> consintiese en la utilización del correo electrónico o de las<br>
> comunicaciones vía Internet le rogamos nos lo comunique y ponga<br>
> en nuestro conocimiento de manera inmediata. Este mensaje va<br>
> dirigido, de manera exclusiva, a su destinatario y contiene<br>
> información confidencial y sujeta al secreto profesional, cuya<br>
> divulgación no está permitida por la ley. En caso de haber<br>
> recibido este mensaje por error, le rogamos que, de forma<br>
> inmediata, nos lo comunique mediante correo electrónico remitido<br>
> a nuestra atención y proceda a su eliminación, así como a la de<br>
> cualquier documento adjunto al mismo. Asimismo, le comunicamos<br>
> que la distribución, copia o utilización de este mensaje, o de<br>
> cualquier documento adjunto al mismo, cualquiera que fuera su<br>
> finalidad, están prohibidas por la ley.<br>
><br>
> ***************** PRIVILEGED AND CONFIDENTIAL ****************<br>
> We hereby inform you, as addressee of this message, that e-mail<br>
> and Internet do not guarantee the confidentiality, nor the<br>
> completeness or proper reception of the messages sent and, thus,<br>
> STACKOPS TECHNOLOGIES S.L. does not assume any liability for<br>
> those circumstances. Should you not agree to the use of e-mail<br>
> or to communications via Internet, you are kindly requested to<br>
> notify us immediately. This message is intended exclusively for<br>
> the person to whom it is addressed and contains privileged and<br>
> confidential information protected from disclosure by law. If<br>
> you are not the addressee indicated in this message, you should<br>
> immediately delete it and any attachments and notify the sender<br>
> by reply e-mail. In such case, you are hereby notified that any<br>
> dissemination, distribution, copying or use of this message or<br>
> any attachments, for any purpose, is strictly prohibited by law.<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> <mailto:<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
> Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> <<a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/%7Eopenstack</a>><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
><br>
><br>
><br>
><br>
> --<br>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
> Dan Wendlandt<br>
> Nicira Networks: www.nicira.com <<a href="http://www.nicira.com" target="_blank">http://www.nicira.com</a>><br>
> twitter: danwendlandt<br>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~<br>
><br>
><br>
><br>
> _______________________________________________<br>
> Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
> Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
> More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/%7Eopenstack" target="_blank">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp" target="_blank">https://help.launchpad.net/ListHelp</a><br>
</blockquote><style>
</style>
</body></html>