<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Flugel.it on Medium]]></title>
        <description><![CDATA[Stories by Flugel.it on Medium]]></description>
        <link>https://medium.com/@flugel-it?source=rss-93c7cc9b1d4------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*TWdMpj0GiI_5qVKmkHk6VA.png</url>
            <title>Stories by Flugel.it on Medium</title>
            <link>https://medium.com/@flugel-it?source=rss-93c7cc9b1d4------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:45:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@flugel-it/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The Differences between Compliance vs. Security]]></title>
            <link>https://flugel-it.medium.com/the-differences-between-compliance-vs-security-7e1fb86015be?source=rss-93c7cc9b1d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e1fb86015be</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[security-and-compliance]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[b2b]]></category>
            <category><![CDATA[saas]]></category>
            <dc:creator><![CDATA[Flugel.it]]></dc:creator>
            <pubDate>Fri, 12 Feb 2021 20:07:14 GMT</pubDate>
            <atom:updated>2021-02-12T20:07:14.538Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v2-HM9Py0JAaYLQ4QtYDhQ.png" /></figure><h3>Did you know that Security and Compliance are two very different things?</h3><p>Before explaining the main differences, it is important to be focused on basic concepts:</p><p>Compliance: Mainly focused on alignment with regulations, standards and/or best practices.</p><p>For example, let’s think about companies on the Stock Market that are required to be in compliance with NASDAQ regulations… or,manufacturing companies which are required to be compliant to ISO Standards.</p><p>Security: Related to a set of measures tools and processes put in place in order to protect company assets.</p><p>A good example of the security concept is an Antivirus protecting the system’s availability and performance; encryption protecting systems or in transit information from unauthorized access.</p><h3>Now, what do we basically mean by that?</h3><p>Information Security teams are usually responsible for managing and operating security tools, such as Antivirus, Data Leak Prevention Tools; also working with Identity and access management, syslog logs audits, Intrusion detection and prevention systems Besides, they work with firewalls and web application firewalls, penetration tests and most of the tools that an organization can and should use to proactively protect and avoid working reactively as counter measures to contain damages in terms of IT.<br>They are also responsible for defining rules and standards within the organization to minimize IT security risk.<br>The goal of this team is to avoid and contain security breaches.</p><p>On the other hand, Compliance Teams are usually controlling on regular terms, if you have in place processes and tools to avoid most of the well known risks.<br>Their main focus is to tackle the 80/20, 80% of the risk that takes the 20% of the effort to avoid.<br>Being in compliance with a standard, regulation or best practices is not a warranty against attacks; instead, it is considered to be a statement which shows to your organization, your business partners, vendors and customers that you have a certain level of quality leading to a low level of risk.</p><h3>Conclusion</h3><p>Compliance and Security are complementary, while compliance will avoid your organization to fall into well known issues, security will be focused on your specific environment risks and how to treat them.</p><p>Credits<br>Written by : Gaston Valdes, CISO<br>English language corrections: Jesica Greco</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e1fb86015be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How automating cloud deployments saves you money (a lot)]]></title>
            <link>https://flugel-it.medium.com/how-automating-cloud-deployments-saves-you-money-a-lot-6b98de8ea480?source=rss-93c7cc9b1d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/6b98de8ea480</guid>
            <category><![CDATA[deployment-automation]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[managed-it-services]]></category>
            <dc:creator><![CDATA[Flugel.it]]></dc:creator>
            <pubDate>Fri, 12 Feb 2021 20:04:45 GMT</pubDate>
            <atom:updated>2021-02-12T20:04:45.216Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1pHxZMN9EQiINVt8V-lW6Q.png" /></figure><p>Throughout our hundreds — possibly thousands — of conversations with IT professionals and managers, clients and prospects, many, many of them had made conscious decisions to delay investing in automation of one process or another — or avoid it altogether.</p><p>The reason behind this decision was usually the belief that the expense will outweigh the benefits. While that might be the case with other processes, when it comes to deployments, that is absolutely not the case. There are many, many benefits derived from automating the deployment process versus performing it manually — consistency, speed and the minimizing of rework, to name just a few. In today’s article we’re going to focus mainly on the cost benefits.</p><p>Time to market and opportunity cost</p><p>To start with, by automating deployments, implementation time is dramatically reduced.</p><p>Getting a product released typically requires several iterations before it’s ready; having an automated, and therefore agile, deployment process enables companies to design, test and implement faster, so getting more quickly to market. Consequently, products (infrastructure, applications, or features) are available to their intended users (customers, prospects, sales teams, QA, developers, etc.) much faster and more reliably than if the same deployment had been manually performed. Often, being able to quickly fill a gap in the market makes all the difference; we can all think of several products that are not technically the best solution, yet they lead their market sheerly by having been first.</p><p>A real-life case</p><p>One of our customers, a 10-person start-up, releases no fewer than 400 changes, updates, and / or features to their apps each year. They had been performing them manually, requiring an average of five people-hours each. Doing some math, one calculates that they dedicated two thousand people-hours every year for deployments.</p><p>If we consider that the rate for the person performing these deployments was $30/hr, we get that the total cost of these deployments was $60,000 per year, not an insignificant amount for a start-up. This means that the company had to budget and pre-plan for any deployment, since they had to allocate limited dollars among infrastructure improvements, developing new features, or deployments.</p><p>After Flugel.it automated their deployments, the expenditure per deployment dropped to $15 or so per month. Remember that it had been $60,000 / year previously. The payback on the automation project investment was a matter of a few months.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OVnUyhaRLVSBxfnb.png" /></figure><p>In addition, once the company had their deployments automated they were able to deploy as often as they wanted to; no longer restricted by resource availability or expense, they increased the number of deployments each year many times over.</p><p>Another interesting benefit through the course of automating that’s worth noting: tension between the infrastructure and dev teams diminished significantly. Among other reasons, they were finally able to test a long backlog of features that had been ready as much as six months ago, and do it at any time they wanted to, without needing to coordinate with the infrastructure team.</p><p>Even though we’ve just scratched the surface of the many benefits of using automation, we hope this article started to give you a sense of how it can save significant amounts of money and frustration for team members.</p><p>We will continue discussing in future articles the ways that automation benefits organizations; make sure to subscribe to our newsletter so you don’t miss them!</p><p>Thanks</p><p>Written by: Luis Vinay and Gabriel Gusmaroli</p><p>English Translation &amp; Proofreading: Jesica Greco</p><p>English Editing &amp; Proofreading: Rebekah Wildman</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6b98de8ea480" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 Very different things when working in China’s Internet]]></title>
            <link>https://flugel-it.medium.com/3-very-different-things-when-working-in-chinas-internet-e2a98bf86691?source=rss-93c7cc9b1d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e2a98bf86691</guid>
            <category><![CDATA[dev]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[web-development]]></category>
            <dc:creator><![CDATA[Flugel.it]]></dc:creator>
            <pubDate>Mon, 30 Nov 2020 20:50:25 GMT</pubDate>
            <atom:updated>2020-11-30T20:50:25.110Z</atom:updated>
            <content:encoded><![CDATA[<p>Most of us know that internet laws and regulations are different in China than in most other countries. Though other governments around the world also want to be able to inspect any (or all) internet traffic, China’s government is “open” about that fact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WxWydvtrg51bVbKNkbrYCg.png" /></figure><h4>DISCLAIMER</h4><p>This is not an opinion article; we don’t judge the decisions made by the Chinese government. We respect the laws of the country in which we’re operating, just like other companies doing business in China.</p><p>With that out of the way, let’s continue.</p><p>Since we have been serving customers in mainland China for some time now, we thought it would be interesting to share some of the unique traits we’ve observed.</p><p>(As a bit of context, one of our clients, for example, provides e-commerce services to global brands that operate in mainland China. We deploy and manage GCP clusters for them.)</p><h3>#1: Encryption is a no-go</h3><p>If you have been creating infrastructure for more than a week, you already know that encryption is not optional — communications and traffic on the open internet need to be encrypted, right?. What would you say if I told you that you’re wrong?.</p><p>Well… at least in China, the moment you enable encryption, your traffic plummets, and all communication stops. This doesn’t mean that all Internet traffic in China has to be plain text; you’re allowed to encrypt traffic. There are just some restrictions.</p><h3>#2: You can’t sign your own TLS certificates</h3><p>This is the fundamental restriction alluded to in <em>Number 1 </em>above: you can use TLS encryption in China, but you must buy the certificates from a state-approved provider. Compared to certificates from other, non-state-approved providers, these can be very expensive and can’t be obtained in an automated way.</p><h3>#3: You must use someone else’s DNS service</h3><p>This is the restriction that shocked us the most: you cannot administer public-facing DNS records.Though we’re not completely sure of the reason behind this, we assume it’s to ensure traceability.</p><p>This is maybe the most annoying problem from an operations standpoint, since it renders automatic deployment of environments more or less out of the question.</p><h3>Final thoughts</h3><p>The Internet landscape in China is so, so different from what you see in other countries, there’s no doubt about that.</p><p>There’s something that kinda shocked me: knowing that you can’t encrypt traffic might lead you to think that China is a very fertile hacker hunting ground. Well… it’s not. From what we’ve seen, being such a controlled place, doing silly things on China’s internet can get you into trouble with the authorities.</p><p>Again, this is not a political analysis — it’s just our understanding of the situation. In all the time that we’ve been operating in China, we have yet to experience any type of security-related incident.</p><p>As a closing comment, working in China’s internet is a very interesting experience, one that forced us to think outside of the box in order to achieve the results our cya lo pingueeustomer was looking for.</p><p>Credits</p><p>Written by : Gabriel Vasquez &amp; Luis Vinay</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e2a98bf86691" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is “Serverless”?]]></title>
            <link>https://flugel-it.medium.com/what-is-serverless-e1a7fb5d4ae5?source=rss-93c7cc9b1d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/e1a7fb5d4ae5</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[serverless]]></category>
            <category><![CDATA[cloud-infrastructure]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[aws]]></category>
            <dc:creator><![CDATA[Flugel.it]]></dc:creator>
            <pubDate>Tue, 27 Oct 2020 19:26:55 GMT</pubDate>
            <atom:updated>2020-11-02T18:44:21.752Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Buxr23LUiV2-A-7Cj8bEug.png" /></figure><p>In some cases, <strong>serverless is wrongly related to a context in which a server does not exist</strong>. However, a server does exist, but no management tasks on a server will be performed; its maintenance and execution is be done by a vendor.</p><p>In other words, <strong>having a “serverless” architecture involves avoiding server management and as any other cloud resource, you only pay for what you use.</strong></p><h3>The most important benefits of leveraging a serverless infrastructure are:</h3><ul><li><strong>Ease of deployment.</strong></li><li><strong>Flexible</strong> and quick to deploy and does not generate long-term commitments.</li><li><strong>Cost-effective</strong> because idle resources do not cause any additional cost.</li><li><strong>Friendly</strong> since it gets along with micro services.</li><li>It will<strong> decrease the time to get into the market</strong>, helping the software to be launched faster.</li></ul><p>Nevertheless, not all that glitters is gold talking about going serverless. There are some challenges that might prevent its adoption.</p><p>These are some of them:</p><ul><li><strong>Lack of tools</strong> because developers depend on vendors for debugging and monitoring of tools.</li><li><strong>Complex</strong> <strong>architecture</strong> since it gets difficult to manage too many functions.</li><li><strong>Integration and “serverless” applications are complex.</strong></li></ul><h3>Conclusion</h3><p>Serverless is an innovative and growing technology. Therefore, many companies are benefiting from it since they avoid spending resources on servers’ management while helping them to keep the focus on what drives money to the business.</p><p>Credits<br>Written by : Jesica Greco<br>General corrections and edition: Luis Vinay &amp; Diego Woitasen</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e1a7fb5d4ae5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What is immutable infrastructure?]]></title>
            <link>https://flugel-it.medium.com/what-is-immutable-infrastructure-c93126889e5b?source=rss-93c7cc9b1d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/c93126889e5b</guid>
            <category><![CDATA[immutable-infrastructure]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[cloudinfra]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-infrastructure]]></category>
            <dc:creator><![CDATA[Flugel.it]]></dc:creator>
            <pubDate>Tue, 27 Oct 2020 19:23:42 GMT</pubDate>
            <atom:updated>2020-11-02T18:45:22.662Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iSWsviW8uvXp-RO8vv57Tw.png" /><figcaption>Immutable Infrastructure</figcaption></figure><p>Within the <strong>Cloud infrastructure</strong> space, <strong>there are several approaches on how to manage infrastructure.</strong> From: old-fashion manual creation and pray, to: everything automated, self-healing, self-scaling and pretty much self-managing.</p><p>Within the second group, <strong>there are several approaches</strong> as well; you can have your <strong>infrastructure automated</strong> provisioned with <strong>Terraform</strong> and use<strong> Ansible</strong> for the configuration management, or you can also use things like Packer to manage Compute instance images.<strong>There are combinations as people that manage infrastructure.</strong></p><p>Even when there is nothing wrong with using for example: Terraform + Ansible, if your application is Cloud-native, <strong>there are better technologies that you can leverage, like containers, Kubernetes and the Immutable Infrastructure model. Today, we will be focusing on this last one.</strong></p><p>Now, yes, what is immutable infrastructure? Basically, <strong>immutable infrastructure</strong> involves an infrastructure paradigm within servers or services<strong> that will be never changed after their implementation or installation.</strong></p><p>Immutable infrastructure is considered to be formed by unchangeable components, and they are able to be replaced one by one.</p><p>Based on this immutable infrastructure paradigm, servers or services are not changed; whenever an update is needed, the server or service will be replaced by a new version.</p><p>Finally, it is worth pointing out that old versions will continue to be available if a rollback is needed.</p><p><strong>Living in a world in which Cloud technologies are mainly adopted, immutable infrastructure has gained ground.</strong></p><p>It is highly important to emphasize that there are certain tools which can be used on an immutable infrastructure environment, <strong>such as Docker, Kubernetes, AWS, GCP, and Azure.</strong></p><p><strong>CONCLUSION</strong></p><p><strong>There is a current tendency moving forward immutable infrastructure</strong>. This is happening mainly since this is a way to simplify platforms’ management.</p><p><strong>Immutable infrastructure paradigm is suitable for Cloud infrastructures, together with applications to images containing data and the service in only one image.</strong></p><p>Credits<br>Written by : Luis Vinay &amp; Jesica Greco<br>General corrections and edition: Luis Vinay &amp; Diego Woitasen</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c93126889e5b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[5 Infrastructure-related problems that most scale-ups have]]></title>
            <link>https://flugel-it.medium.com/5-infrastructure-related-problems-that-most-scale-ups-have-5e39567123bd?source=rss-93c7cc9b1d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/5e39567123bd</guid>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[managed-cloud-services]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[terraform]]></category>
            <category><![CDATA[automation]]></category>
            <dc:creator><![CDATA[Flugel.it]]></dc:creator>
            <pubDate>Tue, 13 Oct 2020 13:08:14 GMT</pubDate>
            <atom:updated>2020-10-13T13:08:14.063Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JOFQ7yruoKWKAoF_JKjQjA.png" /></figure><p>Once your startup grows, it’s no longer a startup but a scale-up, and when that happens, a new set of challenges arises.</p><p>This is a list of (some) common challenges scale-ups face when growing into a more mature business; the challenge now is not knowing what to do — but being consistently good at it.</p><p><strong>1: You learn about problems from… your clients</strong></p><p>How many times have you gotten a call from a client informing you about a problem in your infrastructure and you know nothing about it?<br>We’ve all been there, and we know how frustrating and embarrassing it can be, not to mention damaging to your reputation; if a client learns that you didn’t know about an issue, you’ve lost that client’s confidence.</p><p><strong>2: You don’t fully own your infrastructure</strong></p><p>You found a great freelancer to build it some time ago, and he got the job done!</p><p>Now… what would happen if he leaves? You’re in deep trouble.</p><p>You don’t fully own your infrastructure if you don’t have complete control over it and own the knowledge you would need to rebuild it from the ground up.</p><p><strong>3: What’s going on with your infrastructure</strong></p><p>Related to the previous point, you have no idea how good or bad the application’s health is, besides “it’s running ok” or “it’s as slow as a snail”; worst of all, when it goes down, you don’t know about it until a customer lets you know.</p><p><strong>4: Releasing to production is a “journey into the unknown”</strong></p><p>Every time you want to put a new version in production is “<em>to boldly go where no man has gone before</em>“: more often than not, a new version means a lot of manual labor, delays, eternal rollbacks and lots of headaches. All this means that your costs skyrocket and your time to market goes through the window.</p><p><strong>5: Your infrastructure is anything but reliable</strong></p><p>Everything “runs”, but as soon as you change even just a single component of the infrastructure, the rest falls apart like a house of cards. Of course you know how to put it back together, but you become more and more reluctant to change, and sooner or later, you stop innovating due the fear of “breaking everything”.</p><p>If you can relate to some (or all!) of the situations above, fear not — there’s a silver lining to all this. These are mostly technical problems, and if twenty-plus years of experience in IT has taught us anything, it’s that technical problems are the easiest kind to fix.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5e39567123bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[An Important Part of Cloud Migrations: Testing People]]></title>
            <link>https://flugel-it.medium.com/an-important-part-of-cloud-migrations-testing-people-3b52d7d12df6?source=rss-93c7cc9b1d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b52d7d12df6</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[cloud-infrastructure]]></category>
            <category><![CDATA[vms-software]]></category>
            <category><![CDATA[amazon-web-serices]]></category>
            <category><![CDATA[chefs]]></category>
            <dc:creator><![CDATA[Flugel.it]]></dc:creator>
            <pubDate>Tue, 13 Oct 2020 13:05:07 GMT</pubDate>
            <atom:updated>2020-10-13T13:05:07.877Z</atom:updated>
            <content:encoded><![CDATA[<p>Probably we all understand that any migration should be preceded by simulations in order to provide the best possible opportunity for success. What is often missed or underestimated, however, is the importance of including people in this process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kc-eSAkA0QIuIItGt5ejdg.png" /></figure><p>A successful simulation without the parties responsible for the real migration, those who must execute, coordinate and communicate throughout that process, may provide a false sense of preparedness. How can we know that a successful simulation can be replicated, after all, when the whole team was not involved in the process?</p><h3>The Problem</h3><p>Consider the scenario we at Flugel faced a while back. A client required the migration of his microservices-based application to AWS, using containers. The application was running on-site, using legacy DevOps tooling, Xen VMs, Chef, and some scripting.</p><p>So what, exactly, was the problem?</p><p>There were network limitations and security concerns that made progressive migration almost impossible. The only component that could be duplicated and synchronized was the database. There were third-party API limitations that complicated the move.</p><p>This migration required a temporary halt on all on-site microservices, leading to some downtime with no guarantee of successful migration.</p><h3>The Proposed Solution</h3><p>A good solution needed to reduce downtime to as near zero as possible while ensuring successful migration, preferably on the first attempt.</p><p>There were three important parts of this process: automation, communication, and testing.</p><p>First, the automation or infrastructure code: All deployment to the cloud was fully automated, from network layout to application deployment in each instance.</p><p>Second, communication (and coordination): Authority to proceed with this migration was not invested in a single team but shared by several teams. These teams, therefore, needed to coordinate and communicate effectively if migration were to be successful.</p><p>Third and most important, testing: The application and infrastructure would need to be tested, of course. But because a successful migration hinged on the cooperative functioning of the company’s various teams, testing had to include these teams. We had to verify that these teams would be in sync throughout the migration process.</p><p>We also needed to test the rollback in the event that something went wrong.</p><h3>The Migration</h3><p>Migration was scheduled for January. We hoped to do at least two simulations before that time.</p><p>The first simulation ran in a pre-production environment in November. It involved QA (for manual testing), network team (for DNS changes), developers, infrastructure engineers, and project managers. The November test failed because there was a communication issue, and QA was not ready to verify on time.</p><p>The second simulation, which ran in the same environment at the end of December, was successful. January’s successful production migration ran as expected, with less than one hour of downtime.</p><h3>Testing People, Not Just Software</h3><p>While, in facing a complex and critical migration like the one discussed here, the focus seems naturally to fall on technologies, but we should recognize that human factors are equally important. In this particular case, and based on our first (unsuccessful) simulation, the faultlines revolved around the client’s various teams.</p><p>Testing the application and infrastructure, while important, is inadequate. The success of such testing shows an incomplete picture. Failure to rehearse the various teams would have led us to a false assumption of readiness, leading to failure of the real migration, when it mattered most. Without testing the people part of the process, we would have been left wondering what, exactly, had gone wrong.</p><p>Recognizing that people are an important part of advance testing contributed a great deal toward our happy, less-than-one-hour downtime migration. Through the simulations, the client migration team came to understand their responsibilities and their importance to migration success.</p><p>At the end, all the technical problems are people problems.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b52d7d12df6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reducing costs by leveraging GKE Optimizations and GCP Preemptible VMs]]></title>
            <link>https://flugel-it.medium.com/reducing-costs-by-leveraging-gke-optimizations-and-gcp-preemptible-vms-5b8f02b158dd?source=rss-93c7cc9b1d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/5b8f02b158dd</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[google-cloud-platform]]></category>
            <category><![CDATA[virtual-machine]]></category>
            <dc:creator><![CDATA[Flugel.it]]></dc:creator>
            <pubDate>Tue, 08 Sep 2020 17:14:20 GMT</pubDate>
            <atom:updated>2020-09-08T17:14:20.462Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article we will show an example of how the thought process works when we tackle the resource optimization problem.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KxPWza2geTNob6Vm7tS4uA.png" /></figure><p>First, let’s address what is Kubernetes: Kubernetes is the world’s most popular container orchestration tool; it’s an open-source system for automating deployment, scaling, and management of containerized applications.</p><p>Nowadays, all major public-cloud providers offer a managed version of Kubernetes, such as Google Kubernetes Engine (GKE) or Amazon’s Elastic Kubernetes Service (EKS), to name just a few. GKE is very flexible and a great platform where to deploy (almost) any type of application, but where it really shines is with containerized cloud-native and/or micro-service centric applications.</p><p>What we did?</p><p>At Flugel.it , we have been using Preemptible VMs within several clients. Today, we’ll talk about the experience with one of them, in the Ecommerce SaaS space. Before the optimization process, during a busy week, our nodes could easily exceed 100 vCPU occupation and 300 GB of total memory, but the application was not able to completely use the resources available to it in every instance of the Kubernetes cluster. This caused the cluster to over-provision more than what is optimal, which became an unnecessarycost overhead.</p><p>What we noticed was that on each node (VM Instance), after deploying all the Pods that fitted, there were some leftover resources, so we adjusted the memory size and after deploying all Pods, there was no leftover memory. Even with this dramatically reduced infrastructure expenditure, our goal was to reduce it evenfurther.</p><p>Once the size optimization path was exhausted, we started to look to more innovative approaches. One potential solution we found was to implement Preemptible VMs since, at least in theory, it was possible to use Preemptive VMs to compose the Kubernetes clusters (GKE), either completely or a good part of them. But, before we continue, let’s address what Preemptible VMs are and their limitations:</p><p>What is a Preemptible VM?</p><p>A Preemptible VM is a type of instance that can be created and run at a much lower cost, up to 70% less cost than on-demand nodes.</p><p>Do Preemptible VMs have cons or limitations?</p><p>For most purposes, Preemptible VMs function like normal instances, but yes, they have cons and limitations:</p><p>● Preemptible VMs can be terminated (preempted) by the Compute Engine if it requires use of those resources for other (on-demand) instances.<br>● Preemptible VMs might not always be available because they are to “fill” exceeding Compute Engine capacity, so their availability changes with its usage.<br>● Compute Engine might terminate Preemptible VMs , at any time, due to system events. The probability that Compute Engine will terminate a Preemptible VMs for a system event is generally low, but it may change from day to day and from zone to zone depending on current conditions.<br>● Compute Engine always terminates Preemptible VMs after 24 hours from its creation, which said some actions can be taken to reset this 24-hour counter.<br>● Preemptible VMs are finite Compute Engine resources, so they might not always be available.<br>● Preemptible VMs can’t be migrated to a regular VM instance.<br>● Preemptible VMs can’t be set to automatically restart when there is a maintenance event.<br>● Google Cloud Free Tier credits for Compute Engine do not apply to Preemptible VMs.</p><p>Due to the above limitations, Preemptible VMs are not covered by any Service Level Agreement (and they are excluded from the Compute Engine SLA).</p><p>The final solution</p><p>We used Preemptible VMs in other production environments during the past so we knew it might be a viable option. We only needed to confirm that the application could withstand the sudden elimination of a complete cluster node.</p><p>During the course of few days, we did exhaustive tests to finally determine that the application was good to go with Preemptible VMs ; therefore, we progressively implemented the new solution in more and more critical environments getting more confident that, in this particular case, there was no undesirable behaviour from the application.</p><p>Conclusion</p><p>Even though we are not in the freedom of showing the actual numbers, we can confidently say that the investment cost to investigate, validate and implement both the adjustment of the VM size and latter Preemptive VMs paid-off, and will continue to do so massively to our client. Before this optimization, we have not been using around 15% of the memory deployed in each VM instance and by leveraging Preemptive VMs. We reduced the average cost of each Kubernetes cluster by over 60%.</p><p>At Flugel.it, we strive to lower bill costs for all our clients, sometimes by means of leveraging tools and resources like GKE Preemptible VMs or AWS Spot Instances, but most times by iterating over current infrastructure, sometimes by replacing old solutions with newer more refined versions. In spite of the fact that not all applications are eligible for implementing Preemptible VMs , this is a great tool to reduce costs when applicable.</p><p>It is important to point out that GCP Preemptible Instances are in a production-ready state and we have been successfully using them in live production environments. A second article will be published with a more in depth technical description on how we achieved this solution. If you find this or other of our blog articles interesting, please subscribe to our Blog and Newsletter so you’ll get notified when we release a new piece.</p><p>Thanks for reading, and have a great day!</p><p>Credits<br>Written by : Gabriel Vasquez<br>English language corrections: Jesica Greco and Rebekah Wildman<br>General corrections and edition: Luis Vinay</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5b8f02b158dd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Automation is not (only) about speed]]></title>
            <link>https://flugel-it.medium.com/automation-is-not-only-about-speed-972e5c4e23d9?source=rss-93c7cc9b1d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/972e5c4e23d9</guid>
            <category><![CDATA[kubernetes]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[infrastructure-automation]]></category>
            <category><![CDATA[infrastructure-as-code]]></category>
            <category><![CDATA[docker]]></category>
            <dc:creator><![CDATA[Flugel.it]]></dc:creator>
            <pubDate>Mon, 03 Aug 2020 13:10:31 GMT</pubDate>
            <atom:updated>2020-08-03T13:10:31.147Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AmaLrezPhsCDC25CUOQ_gQ.png" /></figure><p>Everything we do at Flugel.it revolves around infrastructure automation — it is our core business.</p><p>What do we mean exactly by infrastructure automation?</p><p><em>Infrastructure Automation</em> is a process used to apply the same configuration to one or thousands of nodes/instances/VMs with the same effort. To achieve this, we leverage technologies that allow us to describe infrastructure via some machine-readable language.</p><p>With it, we can describe the desired configuration, state or even how different components interact with each other. This includes both software and hardware, including but not limited to: VMs, databases, networking equipment (virtual or physical), databases, etc.</p><p>It can be also used to automate tasks related to the build process of software running on such infrastructure, such as: integration tests, coverage, syntax, etc.</p><p>DEVELOPMENT:</p><p>A transition from classic infrastructure to automated infrastructure may be challenging, since it involves a huge change in how the infrastructure is conceived.</p><p>Some questions may arise through this process, such as, “Why should I automate something which is only deployed every 5 years? Or, “In my case, the speed that automation provides is not worth the effort .” The counterargument to these two questions is, “Can you actually trust a manual procedure which is performed only every five years? Are you willing to risk manual errors?</p><p>Beyond speed, which is generally obtained by automating processes, it is even more important that we consistently get the same results. Therefore, the error percentage and rework required with manual processes are dramatically reduced.</p><p>Another benefit of automation is the small amount of overhead needed to periodically monitor that it’s operating correctly.</p><p>Using the example detailed above, even if you need the automation only once every five years, you can test it as frequently as once a week, which would be very challenging and cost-prohibitive to do manually. Regularly testing this automated process provides a high level of certainty that if you need to deploy that infrastructure at any point in the future, you would be able to without any issues.</p><p>In addition, automation can serve as a disaster recovery process. Often, a failed infrastructure may be quicker, easier, and more reliable to regenerate from the ground up by means of automation, rather than troubleshooting it and applying a manual fix.</p><p>At Flugel.it, we’re Subject Matter Experts (SMEs) on pretty much every automation tool, such as Cloudformation, Terraform, Ansible, Chef, Puppet, and Saltstack, to name just a few.</p><p>CONCLUSION:</p><p>Most repetitive operational tasks benefit from automation because it reduces dependencies among different work teams, allowing for faster development times. Traditional operational teams do not have proper automation processes in place; therefore, they have higher workloads and / or lack sufficient time to learn new technologies or embark on new projects that could add value to their organization.</p><p>For all these reasons and more, automation is not just more speed when deploying or testing. Maybe, the most important benefits provided by automation are reliability and consistency, while at the same time, making processes faster without neglecting process compliance.</p><p>There are more benefits that will be discussed in future articles.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=972e5c4e23d9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Our experience working during the COVID19 pandemic]]></title>
            <link>https://flugel-it.medium.com/our-experience-working-during-the-covid19-pandemic-cb2c4a0bdcd8?source=rss-93c7cc9b1d4------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb2c4a0bdcd8</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[working-remotely]]></category>
            <category><![CDATA[agile-methodology]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[kubernetes]]></category>
            <dc:creator><![CDATA[Flugel.it]]></dc:creator>
            <pubDate>Mon, 29 Jun 2020 14:47:40 GMT</pubDate>
            <atom:updated>2020-06-29T14:48:36.734Z</atom:updated>
            <content:encoded><![CDATA[<p>Flugel.it was born as — and continues to be — a company that works 100% remotely, distributed in over a dozen geographical locations. Our team members and our clients are separated by thousands of kilometers; this makes working remotely an integral part of our organization.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MEF4Eq7qN9boftgqCeyLjQ.png" /></figure><p>From the beginning, we have relied on agile work methodologies, which value communication and are essential when articulating the efforts of our teams with clients. That’s why today, communication and coordination are not an issue: over the life of the company we have applied, tested, and re-evaluated our methodologies many times until we found what worked for us.</p><p>After so much time working remotely, we were able to identify and generate our own set of processes that compensate for the lack of face-to-face contact and adjust to our unique way of doing things.</p><p>In Flugel.it’s particular case, since we can’t just “pop in” to a colleague’s office, the tools we use help us stay in communication with one another.. Some of those technologies include Zoom, Slack, Jira, Confluence, Google Docs, and Calendly, among others. Since most of the tools were designed to be used specifically for collaborative, distributed work, they fit our way of working remotely very well.</p><p>The selection of each of these tools was the result of trial and error, time, and experience. As one example, Slack was not our first choice of collaboration tool, but rather the third. Our entire team now uses it on a daily basis to communicate with and stay closely connected to clients and each other.</p><p>This pandemic hasn’t caused any disruption to our work, workflows or capacity to continue serving our clients. We’ve been working as a distributed company for many years, something we recognize that many companies are just now learning how to do. Keep in mind it’s a process — one that requires an honest look at your company and its needs. Along with a little patience.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb2c4a0bdcd8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>