Apache CloudStack vs. F5 Distributed Cloud Network Connect

Whether our clients are VPS hosting providers or operate private cloud infrastructure for their internal enterprise requirements, CloudStack provides solutions in an easy to implement and operate way that is simple to provide training for. The learning curve for our customesr adopting CloudStack for the management of their cloud infrastructure is shallow, enabling our clients to come up to speed quickly without having to outsource their administrative functions any longer than necessary

F5 Distributed Cloud Network Connect Would be incredibly useful when having to juggle multiple cloud providers. Also XC would be fantastic for standardization and consistency of the whole networking stack. It may be less useful for incredibly specialized cases where very specific traffic manipulation is needed. Any use-cases with heavy APM usage would have to be carefully considered as those features didn’t make it into XC yet.

Incentivized

• Low-cost solution
• Open-source
• Engaged community
• Solid documentation
• Is a very reliable tool for orchestration with good usability

Incentivized

• Centralized Hybrid ingress for our cloud workloads
• Centralized ingress for our existing on-prem BIG-IP devices
• Application visibility to address end-to-end visibility into the end-user experience

Incentivized

• Sometimes you can find undocumented bugs that can compromise the entire infrastructure.
• [If] you don't have an official support channel, you have try to find out the source of the problem by yourself.
• Volume size limitation. Other players allow you to create volumes up to 64TB while ACS allows only 2TB volumes

• The support model needs a quite a bit of work. I personally have experienced an outage on the platform. due to mis-configureation Although the outage was due to engineer error it took over 2 hours before we were able to speak to an engineer
• Proxy v2 protocol to allow our organization to capture and view the source IP address

Incentivized

Overall, F5 Distributed Cloud Network Connect is responsive and has many features. There is minor clunkiness in how certain scroll bars are layered. This may cause some adverse experience when trying to manage this product through a zoomed browser. Page loading and refresh timers were all very much responsive. There is a good amount of feedback from the interface as well.

Incentivized

The University, my first large implementation, had a big issue with 149 small data centers spread on São Paulo State, this data centers costs to university were very high, the consolidation idea in two data centers were awesome, but were worried with the management, so we adopted ACS to management of all 576 physical hosts. Now a days the university is delivering IaaS for all staff, students, teachers and researchers, they are using these resources to delivery services to their clients and have a great results in research area

Aviatrix operates like a slightly different version of XC. Mostly it relies on routing, where cloud connect takes a whole stack into consideration. Not sure if XC can fully replace Aviatrix, but after a couple of implementations, it may become apparent. There are similar routing features in both. XC has more overall features.

Incentivized

• Low-cost solution (free and open-source)
• More than 2000 users using it simultaneously
• Stable and reliable
• Up and running since 2012

Incentivized

• As it helps monitor for any attacks, it can definitely save the business money in case of attacks by finding it quickly

Incentivized