--
~~~~~
Register Today for Cloud Slam 2010 at official website - http://cloudslam10.com
Posting guidelines: http://groups.google.ca/group/cloud-computing/web/frequently-asked-questions
Follow us on Twitter http://twitter.com/cloudcomp_group or @cloudcomp_group
Post Job/Resume at http://cloudjobs.net
Buy 88 conference sessions and panels on cloud computing on DVD at
http://www.amazon.com/gp/product/B002H07SEC, http://www.amazon.com/gp/product/B002H0IW1U or get instant access to downloadable versions at http://cloudslam09.com/content/registration-5.html
~~~~~
You received this message because you are subscribed to the Google Groups "Cloud Computing" group.
To post to this group, send email to cloud-c...@googlegroups.com
To unsubscribe from this group, send email to cloud-computi...@googlegroups.com
What I'm seeing with a lot of Xen deployments is that people are using
networking to recreate the tiers in the cloud. Even though apps are
deployed on shared hardware, the network is set up such that the vm's
cannot communicate with each other, so basically they are either using
physical or virtual networking separate the apps into subnets that
retain the legacy tiered infrastructure.
-Tal
Do you mean N-tier apps as defined by hardware vendors or more real-world deployments?
One of the examples I'm thinking of is a company that has their web
and application tiers virtualized on the same hardware. The web
servers are on one VLAN1 and the app servers are on VLAN2. The VLAN1
traffic is mapped to physical NIC 1 and VLAN 2 is mapped to physical
NIC 2 on each physical host. In other environments I've seen companies
do the same thing but higher up the OSI stack, essentially assigning
each "tier" IP ranges on different subnets and then using a layer 3
device to essentially act as referee.
-Tal