This is a snippet of the transcript, sign up to read more.
When I arrived at Inditex there was no cloud; there was nothing. My boss looked through deploying Azure and GCP and said, we want to build automation. We don't want to build stuff manually, because it's going to get super difficult to manage. I suggested a stack, like increasing Terraform, Packer, different products for automation, as we use in batch, in Unix with PowerShell for Windows. We started with the open-source version and I started, basically, writing some of the first pieces of code to automate, and then we get involved with Microsoft. We get Cloud Center of Excellence with Microsoft, and they brought Terraform code, with something they called, Landing Zone, which is basically a package with lot of code with which they built the whole environment.
This is a snippet of the transcript, sign up to read more.
Usually, I would say that everything starts with the DevOps architect. In my case that we have a small architect team, there are four people. We start architecting the solution. I start building these little blocks, but when the environment grows, we established a DevOps team and the DevOps team was in charge of deployments using Terraform. I will say that the biggest problem for me – I saw this in Inditex, I saw this in Dubai Expo and I saw this in a lot of my previous AWS customers – is to find a way for the developers with no DevOps experience, to deploy Terraform Cloud. This is where I've been working on this tool – I hope I can release in a couple of months – but the problem is there is not really a good orchestrator that can help you to go through this.
This is a snippet of the transcript, sign up to read more.
At the beginning, yes, because I was concerned about the money, but then we started looking into the future. We got access to the Enterprise. I started looking for what the benefit was. The first one was obviously Sentinel. The second one was the integration with single sign on, which is very good to control access and execution and stuff like that. Then the workspace is basically when you separate and segregate the piece of code and it's easy to manage.
This is a snippet of the transcript, sign up to read more.
This document may not be reproduced, distributed, or transmitted in any form or by any means including resale of any part, unauthorised distribution to a third party or other electronic methods, without the prior written permission of IP 1 Ltd.
IP 1 Ltd, trading as In Practise (herein referred to as "IP") is a company registered in England and Wales and is not a registered investment advisor or broker-dealer, and is not licensed nor qualified to provide investment advice.
In Practise reserves all copyright, intellectual and other property rights in the Content. The information published in this transcript (“Content”) is for information purposes only and should not be used as the sole basis for making any investment decision. Information provided by IP is to be used as an educational tool and nothing in this Content shall be construed as an offer, recommendation or solicitation regarding any financial product, service or management of investments or securities. The views of the executive expressed in the Content are those of the expert and they are not endorsed by, nor do they represent the opinion of In Practise. In Practise makes no representations and accepts no liability for the Content or for any errors, omissions, or inaccuracies will in no way be held liable for any potential or actual violations of laws, including without limitation any securities laws, based on Information sent to you by In Practise.
© 2024 IP 1 Ltd. All rights reserved.
Subscribe to access hundreds of interviews and primary research