Resultados 1 a 3 de 3
  1. #1
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,030

    [EN] Amazon: AWS Management Portal for vCenter

    The AWS Connector for vCenter tech gives VMware administrators a way to buy, manage, and migrate VMs into AWS cloud resources from within VMware's vCenter management console.

    Amazon has teleported its cloud business into the management software of a rival that is used in thousands of data centers across the world.

    One of the great things about superficially boring tech plug-in announcements is that they usually conceal a nefarious and well thought-out strategic attack on another company's business. This is no different.

    Amazon announced on Friday afternoon that it was making available an "AWS Connector for vCenter", which lets admins import management tools for Amazon's cloud directly into an on-premise data center software package made by one of Amazon's rivals.

    The AWS Connector for vCenter tech gives VMware administrators a way to buy, manage, and migrate VMs into AWS cloud resources from within VMware's vCenter management console.
    vCenter is a widely used piece of software from VMware that lets admins manage large numbers of virtual machines, typically within enterprise data centers.

    "If you are already using VMware vCenter to manage your virtualized environment, you will be comfortable in this new environment right away, even if you are new to AWS, starting with the integrated sign-on process, which is integrated with your existing Active Directory," Amazon explains.

    "The look-and-feel and the workflow that you use to create new AWS resources will be familiar," they continue, "and you will be launching EC2 instances before too long. You can even import your existing 'golden' VMware images to EC2 through the portal (this feature makes use of VM Import)."

    Those two paragraphs alone are likely to summon up a feeling of dread at VMware, given that the company has recently launched the vCloud Hybrid Service in an attempt to get its customers to sling VMs up into its public cloud, not Amazon's.

    Along with this, service providers that sell VMware-based services can use the portal to offer their own customers "self-service access to AWS", Amazon explains. Another way of putting it is that Amazon has just managed to smuggle its own products into a grocery store that VMware thought it controlled.

    By giving developers a way to access AWS resources from within a familiar bit of management software, Bezos & Co have pulled off one of the greatest tricks in business: getting your competitor to help sell your product. Better still, the "VM Import" feature makes it trivial for admins to migrate existing applications up into the AWS cloud, guaranteeing Amazon a slice of the enterprise's IT budget.

    The free software is available immediately. It comes with enterprise features such as Role-Based Access Controls, templating, governance, and automatic tagging of creating resources so admins can keep track of all the money they may spend on Bezos's big yellow cloud.

    Amazon isn't the first to take this approach; a few months ago Microsoft started embedding its Azure cloud into on-premise software such as Systems Center and Visual Studio. The difference here, of course, is that Amazon has no on-premises software and is instead piggybacking, leech-like, on existing infrastructure built by another company. Watch out VMware, you've got a competitor loose among your customers!
    http://www.theregister.co.uk/2014/05..._stealth_bomb/

  2. #2
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,030

    Don’t Be Fooled By Import Tools Disguised as Hybrid Cloud Management

    June 2, 2014

    By Chris Wolf
    CTO, VMware

    The biggest part of my job is speaking with end user organizations and understanding their greatest current and future challenges. Oftentimes I hear about workloads that are initially developed on a particular cloud provider’s infrastructure that cannot be redeployed or migrated anywhere else. To be clear, nothing is technically impossible. It’s always a matter of the migration costs outweighing the benefits. Many times organizations want to move workloads developed in a public cloud to their private cloud for reasons such as security, compliance or lowering costs. In other cases, service stacks may need to be distributed globally to 40 or more countries and rebuilding those stacks on various infrastructures can cost millions.

    The bottom line – the organizations that I speak with daily are demanding the following with respect to their hybrid cloud strategies:
    • Flexibility and choice – Today’s platform decision may not be the best option in two years, or perhaps even in a few months. Organizations want choice, and they don’t want to pay a severe financial penalty for changing course.
    • Common management - Converting virtual machines, and moving applications and data is often not the challenge when it comes to managing hybrid cloud workloads. The true challenge is trying to manage workloads deployed to different data center or cloud environments requiring new API integration or new operational management tooling. IT decision makers want a consistent management and QA experience no matter where they deploy a workload.



    I discussed hybrid cloud management dependencies in greater depth in this post, so I won’t repeat them here, but I think you get the point.

    I mention all of this because today Amazon announced the AWS Management Portal for vCenter. Administrators will find this tool useful for importing virtual machines into Amazon and conducting basic management tasks from VMware vCenter. However, as I’ve said before, the virtual machine is the easy part. Consider all of the management dependencies above as well as third party integration. If you want to move those workloads or simply run additional instances in a region with no AWS presence, an outsourcer, another cloud provider, or your own data center, you may find that the cost and complexity associated with migration or a new deployment is too much. The service stack would likely be bound to proprietary APIs, and all or most of the third party management and operational software will have to be replaced. You will be burdened with new QA challenges and likely will need to reengage with the procurement teams.

    In summary, there are many things that the AWS Management Portal does not do that should lead you to question its strategic value:
    • There is no easy way to move workloads back to one of your data centers, or to another cloud provider
    • You cannot use your existing software licenses
    • You cannot automate and orchestrate across private and public clouds
    • You cannot enforce policy governance across multi-clouds
    • You lose all of the seamless third party integrations deployed through the VMware Solution Exchange

    Whether you are strategically aligned to VMware or not, you should demand consistent management, third party integration, and a common API that spans all hybrid cloud deployment scenarios. Don’t be fooled by basic management that is tactically useful today but can lead to increased lock-in down the road. The cloud service broker has to be multi-provider – vCloud Automation Center is today and has been for some time. Beyond that – the hybrid cloud platform should enable provider choice and seamless third party integration, regardless of where a workload is deployed. Deciding to run a workload somewhere else should not require a massive migration effort along with massive costs.

    Choosing a tool that addresses an immediate need can help today, but can create more problems down the road if you’re not careful. I applaud Amazon for creating this tool for its tenants, but I encourage all end user organizations to take this moment to reflect on your overall hybrid cloud management strategy, and choose a platform that is right for your long term strategic needs.

    Anyone who has been in IT long enough knows how easy it is for a tactical Band-Aid to unexpectedly become a permanent solution. In the cloud era more than ever, you must think strategically about management. To date, proprietary service provider tools have created management silos that drive up total cost of ownership while increasing provider lock-in. There is a better way. Our approach is to give you choice of a de-facto standard that is supported by thousands of cloud providers, outsourcers, partners, end user organizations, and ecosystem vendors world-wide. In addition, our OpenStack support allows customers to choose how they will integrate and manage services, while giving them the flexibility to change course anytime.

    When it comes to management, every product choice has implications. As the great Yoda once said, “Always in motion is the future.” What seems sensible today can cost you dearly tomorrow. Management tools that take away your ability to choose limit your future. Agility demands are picking up, but this is only the very beginning. Our bet is that a future with limited choice is a future with insufficient agility. How will you define your organization’s future?

    Hybrid cloud architects want as few variables in the architecture as possible because the greater the variation the more costly automation becomes at scale, and that extends to management products. Most IT decision makers see flexibility as the capability to run or move a workload wherever they choose, whether it be the public cloud, a private data center or to a new outsourcer of their choosing. When you get past the marketing and really examine technical architectures, converting the virtual machine, migrating the app and the data is the easy part. Rebuilding the management infrastructure is anything but “easy.” Management dependencies are massive and are like a game of Jenga. Take one away and the whole service stack can come tumbling down. Those that have played Jenga know that rebuilding is a daunting task, and the same can be said for rebuilding an IT operational management stack.
    http://cto.vmware.com/dont-be-fooled/

  3. #3
    WHT-BR Top Member
    Data de Ingresso
    Dec 2010
    Posts
    15,030

    VMware strikes back at Amazon cloud Trojan Horse with ... blog post

    VMware has responded to a Trojan Horse bit of tech from Amazon with a blog post disparaging the rival's approach.

    Last Friday, Bezos & Co. announced the "AWS Connector for vCenter" plug-in, which lets admins buy, manage, and migrate Amazon Web Services cloud VMs from within the familiar vCenter admin environment.

    This free bit of software is meant to make it easier for admins to shuffle VMs up into the cloud operated by Amazon, and also has the side effect of putting AWS up against VMware's rival service vCHS.

    VMware seems to be a bit miffed about the tech, and expressed its displeasure in some counter-marketing masquerading as a blog post that was published on Monday. "Don't be fooled by Import Tools disguised as Hybrid Cloud Management," thundered the company's chief technology officer for the Americas, Chris Wolf.

    "Hybrid cloud architects want as few variables in the architecture as possible because the greater the variation the more costly automation becomes at scale, and that extends to management products," he wrote. "When you get past the marketing and really examine technical architectures, converting the virtual machine, migrating the app and the data is the easy part. Rebuilding the management infrastructure is anything but 'easy.' Management dependencies are massive and are like a game of Jenga. Take one away and the whole service stack can come tumbling down."

    For readers not familiar with the veiled language that MBA-filled companies use to fight one another, this translates to: What Amazon is doing is trivial and adopting it might cause huge problems!

    "If you want to move those workloads or simply run additional instances in a region with no AWS presence, an outsourcer, another cloud provider, or your own data center, you may find that the cost and complexity associated with migration or a new deployment is too much," Wolf points out. "The service stack would likely be bound to proprietary APIs, and all or most of the third party management and operational software will have to be replaced. You will be burdened with new QA challenges and likely will need to reengage with the procurement teams."

    He then goes on to list some of the perceived main drawbacks of AWS's vCenter plug-in. "There is no easy way to move workloads back to one of your data centers, or to another cloud provider ... you cannot use your existing software licenses ... you cannot automate and orchestrate across private and public clouds ... you cannot enforce policy governance across multi-clouds ... you lose all of the seamless third party integrations deployed through the VMware Solution Exchange," Wolf writes.

    "Anyone who has been in IT long enough knows how easy it is for a tactical Band-Aid to unexpectedly become a permanent solution. In the cloud era more than ever, you must think strategically about management. To date, proprietary service provider tools have created management silos that drive up total cost of ownership while increasing provider lock-in. There is a better way," he explains.

    That better way is, inevitably, VMware.

    It was only a few years ago that VMware was in the position Amazon is now as it rumbled into enterprise data centers causing people to wring their hands about the dangers of locking themselves into its ESX hypervisor. People adapted the software en masse while other companies like Google (KVM) and Amazon (Xen) and Microsoft (Hyper-V) developed or adopted their own hypervisors as a hedge against VMware's dominance.

    Now those virtual chickens have come home to roost on VMware's bottom line. Amazon has the makings of a scrappy new company, and as before it's likely that companies will trade a little bit of lock-in for a significant amount of utility from the upstart.

    Then, as Gartner recently pointed out, Amazon will itself be assaulted from rivals such as Google or Microsoft – or even VMware with its own vCHS cloud.

    One thing is for certain: at this stage it's Amazon that is piling into the territory of other incumbent companies with new tech, and not the other way around
    http://www.theregister.co.uk/2014/06...ter_marketing/

Permissões de Postagem

  • Você não pode iniciar novos tópicos
  • Você não pode enviar respostas
  • Você não pode enviar anexos
  • Você não pode editar suas mensagens
  •